BSS Command Reference

68P02901W23-P GMR-0168P02901W23-P GMR-01 GSM Manual Revision dated 23 Feb 2004 Motorola manual affected This Manual Revision is applicable only to the manual number and version listed below: 68P02901W23-P Technical Description: BSS Command Reference GSM Software Release 7 Service requests This revision provides a fix to the following service requests: • SR1064153 • SR1065717 • SR1076367 • SR1081742 • SR1091037 Reason for revision This revision provides additional and updated information as follows: Chap 2: Device id range for GBL and DS devices; chg_hop_parameters; copy_cell, chg_audit_sched; chg_cell_element; disp_cell; disp_cell_status; disp_options; disp_rtf_channel; equip AXCDR; equip DPROC; equip RTF; sysgen_mode. Chap 4: chg_stat_prop; disp_enable_stat; disp_stats; stat_mode. Chap 5: allow_32k_trau; bss_msc_overload_allowed; gprs_ts_config_alg; init_ul_cs; init_dl_cs; inner_zone_alg; local_maintenance; max_tx_bts; min_gprs_ts_per_carrier; n_avg_i; pkt_radio_type; use_bcch_for_gprs; zone_pingpong_count; zone_pingpong_disable_win; zone_pingpong_enable_win; zone_pingpong_preferred_zone. Chap 6: bep_period; bep_period2. 68P02901W23-P 23 Feb 2004 1 GMR-01 68P02901W23-P GMR-01 Action Remove and replace pages in the Manual as follows: Remove Insert All pages between the clear acetate front sheet and the blank backing sheet, remove from binder. All pages of the GMR between the front sheet and the blank backing sheet, insert into binder. Obsolete pages Destroy all obsolete pages. Do not destroy this page. Completion On completion of the Manual Revision, insert this Manual Revision sheet in the front or back of the manual, for future reference. Motorola service web The Motorola Service Web at url: http://mynetworksupport.motorola.com/mysupport.asp is updated to coincide with printed release of this GMR. CD-ROM The Motorola documentation CD-ROM that contains this manual will be updated to include this GMR at the next issue after the printed release. 2 GMR-01 68P02901W23-P 23 Feb 2004 Technical Description BSS Command Reference © 1994 - 2004 Motorola, Inc. All Rights Reserved GMR-01 68P02901W23-P 23 Feb 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. GMR-01 23 Feb 2004 Table of Contents Contents Technical Description BSS Command Reference Issue status of this manual General information . . . Reporting safety issues . Warnings and cautions . . General warnings . . . . General cautions . . . . Devices sensitive to static Motorola manual set . . . GMR amendment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 7 10 11 13 17 18 19 20 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2 1-5 1-6 1-7 1-8 1-9 1-11 1-20 1-23 1-26 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2 2-3 2-8 2-14 2-15 2-16 2-17 2-19 2-21 2-33 2-35 2-43 2-45 2-47 2-49 Chapter 1: Introduction to commands BSS MMI functions . . . . . . . . . . . . Command/database parameter security levels Command/database parameter types . . . . Commands to be used with caution . . . . . Parameters to be used with caution . . . . . Entering MMI commands . . . . . . . . . MMI command availability . . . . . . . . GSM cell ID format . . . . . . . . . . . . Indices . . . . . . . . . . . . . . . . . . SYSGEN mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Chapter 2: Device/function related commands Command reference presentation . Device related commands . . . . Device identifiers . . . . . . . . Function related commands . . . Function identifiers . . . . . . . Slots . . . . . . . . . . . . . . equip/unequip command matrix . Alarm devices. . . . . . . . . . add_cell . . . . . . . . . . . . add_conn . . . . . . . . . . . . add_neighbor . . . . . . . . . . add_nsvc . . . . . . . . . . . . add_rtf_path . . . . . . . . . . alarm_mode. . . . . . . . . . . assess. . . . . . . . . . . . . . 68P02901W23-P 23 Feb 2004 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . i GMR-01 Contents cage_audit . . . cell_name. . . . chg_acs_params. chg_a5_alg_pr . chg_audit_sched chg_cell_element chg_cell_id . . . chg_csfp . . . . chg_dte . . . . . chg_eas_alarm . chg_element . . chg_hop_params chg_ksw_config. chg_level . . . . chg_password . . chg_rtf_freq. . . chg_severity . . chg_smscb_msg. chg_throttle . . . chg_time . . . . chg_ts_usage . . chg_x25config . clear_cal_data. . clear_database . clear_gclk_avgs . configure_csfp . connection_code copy_cell . . . . copy_path . . . del_act_alarm . . del_cell . . . . . del_conn . . . . del_neighbor . . del_nsvc . . . . del_rtf_path . . . del_smscb_msg . device_audit . . diagnose_device. disp_a5_alg_pr . disp_acs . . . . disp_act_alarm . disp_bss . . . . disp_cal_data . . disp_cbch_state . disp_cell . . . . disp_cell_map. . disp_cell_status . disp_conn. . . . disp_csfp . . . . disp_csfp_status. disp_dte . . . . disp_element . . disp_equipment . disp_exp_config. disp_flash. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ii GMR-01 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-54 2-58 2-61 2-69 2-72 2-77 2-80 2-84 2-87 2-91 2-94 2-101 2-110 2-114 2-116 2-119 2-124 2-126 2-132 2-134 2-137 2-143 2-146 2-148 2-150 2-152 2-154 2-156 2-162 2-165 2-168 2-171 2-173 2-177 2-179 2-181 2-184 2-189 2-191 2-193 2-195 2-198 2-200 2-202 2-205 2-210 2-213 2-223 2-225 2-227 2-229 2-231 2-234 2-244 2-246 68P02901W23-P 23 Feb 2004 Technical Description BSS Command Reference disp_gclk_avgs . . disp_gclk_cal . . . disp_gsm_cells . . disp_hdlc . . . . . disp_hopping . . . disp_level. . . . . disp_link . . . . . disp_link_usage . . disp_mms_ts_usage disp_neighbor . . . disp_nsvc . . . . . disp_options . . . disp_processor . . disp_relay_contact disp_rtf_channel . disp_rtf_path . . . disp_severity . . . disp_site . . . . . disp_throttle . . . disp_time . . . . . disp_trace_call . . disp_traffic . . . . disp_transcoding . disp_version . . . disp_x25config . . download_ltu . . . equip . . . . . . . freq_types_allowed gclk_cal_mode . . ins_device . . . . lock_device . . . . mod_conn . . . . mod_nsvc. . . . . modify_neighbor . modify_value . . . page . . . . . . . query_audits . . . reassign. . . . . . reattempt_pl . . . reset_device. . . . reset_ltu . . . . . reset_site . . . . . set_full_power . . set_relay_contact . shutdown_device . site_audit . . . . . soft_reset . . . . . state . . . . . . . status_mode. . . . store_cal_data. . . swap_devices . . . sysgen_mode . . . time_stamp . . . . trace_call . . . . . trace_connection . 68P02901W23-P 23 Feb 2004 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-248 2-250 2-253 2-256 2-259 2-264 2-265 2-267 2-269 2-281 2-287 2-290 2-294 2-298 2-300 2-305 2-308 2-310 2-311 2-313 2-315 2-318 2-321 2-323 2-324 2-326 2-327 2-376 2-379 2-380 2-385 2-390 2-393 2-395 2-402 2-405 2-407 2-411 2-414 2-416 2-421 2-422 2-427 2-431 2-433 2-438 2-442 2-445 2-457 2-461 2-463 2-466 2-472 2-474 2-483 iii GMR-01 Contents trace_stop. . . . unconfigure_csfp unequip. . . . . unlock_device. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-486 2-489 2-491 2-501 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2 3-4 3-6 3-8 3-10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2 4-5 4-11 4-15 4-17 4-22 4-28 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2 5-5 5-6 5-7 5-8 5-9 5-11 5-12 5-13 5-14 5-15 5-16 5-17 5-18 5-19 5-20 5-21 5-23 5-26 5-27 5-28 5-29 5-30 5-31 5-32 5-33 5-35 5-37 5-38 5-39 5-40 Chapter 3: UNIX commands alias . help . history man . unalias . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Chapter 4: Statistics commands Statistical operations and information . chg_stat_prop . . . . . . . . . . . . disp_enable_stat. . . . . . . . . . . disp_interval . . . . . . . . . . . . disp_stat_prop . . . . . . . . . . . disp_stats . . . . . . . . . . . . . . stat_mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . Chapter 5: CM database parameters CM database parameters presentation . aci_error_clr_thresh . . . . . . . . . aci_error_gen_thresh . . . . . . . . aci_error_inc . . . . . . . . . . . . adap_ho_alt_trigger_rxqual . . . . . adap_ho_pbgt . . . . . . . . . . . . adap_ho_rxlev . . . . . . . . . . . adap_ho_rxqual . . . . . . . . . . . adap_trigger_hop_rxqual_dl . . . . . adap_trigger_hop_rxqual_ul . . . . . adap_trigger_pbgt . . . . . . . . . . adap_trigger_pbgt_nbr. . . . . . . . adap_trigger_rxlev_dl . . . . . . . . adap_trigger_rxlev_ul . . . . . . . . adap_trigger_rxqual_dl . . . . . . . adap_trigger_rxqual_ul . . . . . . . allow_8k_trau. . . . . . . . . . . . alt_qual_proc . . . . . . . . . . . . amr_bss_full_rate_enabled . . . . . . amr_bss_half_rate_enabled . . . . . amr_dl_la_mode_chg_min . . . . . . amr_dl_thresh_adjust . . . . . . . . amr_force_hr_usage . . . . . . . . . amr_fr_dl_la_enabled . . . . . . . . amr_fr_ul_la_enabled . . . . . . . . amr_full_rate_enabled . . . . . . . . amr_half_rate_enabled. . . . . . . . amr_hop_count . . . . . . . . . . . amr_hr_dl_la_enabled . . . . . . . . amr_hr_ul_la_enabled . . . . . . . . amr_hr_intracell_ho_allowed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iv GMR-01 68P02901W23-P 23 Feb 2004 Technical Description BSS Command Reference amr_hr_res_ts . . . . . . . amr_inner_hr_usage_thres . amr_ms_high_cmr . . . . amr_ms_high_rxqual . . . amr_ms_low_cmr . . . . . amr_ms_low_rxqual . . . . amr_ms_monitor_period . . amr_new_calls_hr . . . . . amr_reconfig_fr_to_hr. . . attach_detach . . . . . . . auto_rf_loss_trace . . . . . ba_alloc_proc . . . . . . . band_preference. . . . . . band_preference_mode . . ber_loss_daily. . . . . . . ber_loss_hourly . . . . . . bounce_protect_margin . . bs_ag_blks_res . . . . . . bs_pa_mfrms . . . . . . . bs_pag_blks_res. . . . . . bs_pbcch_blks . . . . . . bs_pcc_chans . . . . . . . bs_prach_blks. . . . . . . bsc_type . . . . . . . . . bsic . . . . . . . . . . . bss_egsm_alm_allowed . . bss_msc_overload_allowed bssgp_block_retries . . . . bssgp_cbl_bit . . . . . . . bssgp_racap_retries . . . . bssgp_reset_retries . . . . bssgp_unblock_retries . . . bts_p_con_ack . . . . . . bts_p_con_interval . . . . bts_power_control_allowed bts_txpwr_max_inner . . . bts_type . . . . . . . . . bvci . . . . . . . . . . . call_trace_options . . . . . called_pci. . . . . . . . . calling_pci . . . . . . . . carrier_disable_time . . . . carriers_ins_pwr_fail . . . cbc_fast_select . . . . . . cbc_intface_vers . . . . . cbc_vbind_cntr . . . . . . cbch_enabled . . . . . . . cbs_outage_cntr . . . . . . ccch_conf. . . . . . . . . ccch_load_period . . . . . cell_bar_access_class . . . cell_bar_access_switch . . cell_bar_qualify . . . . . . cell_reselect_hysteresis . . cell_reselect_offset . . . . 68P02901W23-P 23 Feb 2004 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-42 5-43 5-44 5-45 5-46 5-47 5-48 5-49 5-50 5-51 5-53 5-55 5-57 5-59 5-62 5-63 5-64 5-65 5-67 5-69 5-71 5-73 5-74 5-75 5-77 5-80 5-81 5-82 5-83 5-85 5-86 5-87 5-88 5-90 5-92 5-94 5-99 5-101 5-103 5-105 5-106 5-107 5-108 5-110 5-112 5-113 5-114 5-115 5-116 5-119 5-121 5-124 5-126 5-128 5-130 v GMR-01 Contents cell_reselect_param_ind . . . . . chan_alloc_priority . . . . . . . channel_reconfiguration_switch . cic_block_thresh . . . . . . . . cic_error_clr_thresh . . . . . . . cic_error_gen_thresh . . . . . . cic_error_inc . . . . . . . . . . cic_unblock_thresh . . . . . . . cic_validation . . . . . . . . . . ciph_mode_rej_allowed . . . . . clk_src_fail_reset_period . . . . coincident_cell . . . . . . . . . coincident_mb . . . . . . . . . coincident_offset . . . . . . . . confusion_msg_allowed . . . . . congest_at_source . . . . . . . . congest_at_target . . . . . . . . congest_ho_margin . . . . . . . cp_option_reset_ckt . . . . . . . cp_option_rr_status . . . . . . . cr_calling . . . . . . . . . . . . ct_flow_control_hi_level . . . . ct_flow_control_lo_level . . . . ct_flow_control_msc_trace. . . . c31_hyst . . . . . . . . . . . . c32_qual . . . . . . . . . . . . data_qual_enabled. . . . . . . . ddtr_ctrl_enabled . . . . . . . . decision_1_dl_rxlev_av_h . . . . decision_1_dl_rxlev_av_ih. . . . decision_1_dl_rxqual_av_p . . . decision_1_dl_rxqual_av_h . . . decision_1_dl_rxqual_av_p . . . decision_1_n1/decision_1_p1 . . decision_1_n2/decision_1_p2 . . decision_1_n3/decision_1_p3 . . decision_1_n4/decision_1_p4 . . decision_1_n5/decision_1_p5 . . decision_1_n6/decision_1_p6 . . decision_1_n7/decision_1_p7 . . decision_1_n8/decision_1_p8 . . decision_1_ncell_rxlev_av_h_calc decision_1_p_bgt_rxlev_av_h . . decision_1_tim_adv_av_alg . . . decision_1_ul_rxlev_av_h . . . . decision_1_ul_rxlev_av_ih. . . . decision_1_ul_rxlev_av_p . . . . decision_1_ul_rxqual_av_h . . . decision_1_ul_rxqual_av_p . . . decision_alg_type . . . . . . . . delay_ul_rel_dur . . . . . . . . direct_inner_zone_threshold . . . disuse_cnt_hreqave . . . . . . . dl_audio_lev_offset . . . . . . . dl_dtx_voice_data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vi GMR-01 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-132 5-134 5-135 5-137 5-139 5-140 5-141 5-142 5-144 5-145 5-146 5-147 5-149 5-151 5-152 5-154 5-156 5-157 5-158 5-159 5-160 5-161 5-162 5-163 5-164 5-166 5-168 5-170 5-171 5-172 5-173 5-174 5-175 5-176 5-178 5-180 5-182 5-184 5-186 5-188 5-190 5-192 5-193 5-194 5-195 5-196 5-197 5-198 5-199 5-200 5-202 5-203 5-204 5-205 5-207 68P02901W23-P 23 Feb 2004 Technical Description BSS Command Reference dl_rxlev_ho_allowed . . . . dl_rxqual_ho_allowed . . . . dnlk_vad_dtx . . . . . . . . dpc . . . . . . . . . . . . . dr_allowed . . . . . . . . . dr_chan_mode_modify . . . dr_ho_during_assign . . . . dr_preference . . . . . . . . dr_standard_congest . . . . . dtx_required . . . . . . . . dual_band_offset . . . . . . dyn_step_adj . . . . . . . . dyn_step_adj_fmpr . . . . . dynet_tchs_reserved . . . . . eac_mode. . . . . . . . . . early_classmark_sending . . eas_alarm . . . . . . . . . . eas_alarm_type . . . . . . . eas_report_opto . . . . . . . eas_severity. . . . . . . . . efr_enabled . . . . . . . . . egprs_init_dl_cs. . . . . . . egprs_init_ul_cs. . . . . . . egsm_bcch_sd . . . . . . . egsm_handover_threshold . . emergency_class_switch . . . en_incom_ho . . . . . . . . enhanced_relief . . . . . . . eop_enabled . . . . . . . . erc_ta_priority . . . . . . . ext_range_cell . . . . . . . extended_paging_active . . . fdd_qmin . . . . . . . . . . fdd_qoffset . . . . . . . . . frequency_type . . . . . . . full_pwr_rfloss . . . . . . . gci_error_clr_thresh . . . . . gci_error_gen_thresh . . . . gci_error_inc . . . . . . . . gclk_qwarm_flag . . . . . . global_reset_repetitions . . . gproc_slots . . . . . . . . . gprs_alarm_time . . . . . . gprs_bs_cv_max . . . . . . gprs_cell_cgt_thr . . . . . . gprs_cell_reselect_hysteresis . gprs_com_ms_class . . . . . gprs_cr_margin . . . . . . . gprs_dl_pwr_mode . . . . . gprs_drx_timer_max. . . . . gprs_enabled . . . . . . . . gprs_intraho_allwd . . . . . gprs_mac_mode. . . . . . . gprs_max_ul_ts . . . . . . . gprs_min_prr_blks . . . . . 68P02901W23-P 23 Feb 2004 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-208 5-210 5-212 5-214 5-216 5-217 5-219 5-221 5-223 5-225 5-227 5-228 5-229 5-230 5-232 5-234 5-236 5-237 5-238 5-239 5-241 5-243 5-245 5-247 5-249 5-251 5-253 5-255 5-256 5-257 5-258 5-260 5-262 5-263 5-264 5-266 5-267 5-268 5-269 5-270 5-271 5-273 5-275 5-276 5-277 5-279 5-281 5-282 5-284 5-286 5-288 5-290 5-292 5-293 5-294 vii GMR-01 Contents gprs_ms_pan_dec . . . . . . . . gprs_ms_pan_inc . . . . . . . . gprs_ms_pan_max . . . . . . . gprs_ms_txpwr_max_cch . . . . gprs_network_operation_mode . . gprs_num_pmrs . . . . . . . . . gprs_pb. . . . . . . . . . . . . gprs_pc_alpha. . . . . . . . . . gprs_pc_meas_chan . . . . . . . gprs_reconfig_thresh_idle_tch . . gprs_reselect_offset . . . . . . . gprs_rxlev_access_min . . . . . gprs_sched_beta. . . . . . . . . gprs_sig_bvci . . . . . . . . . . gprs_temporary_offset . . . . . . gprs_ts_config_alg . . . . . . . gprs_ul_dl_bias . . . . . . . . . group_block_unblock_allowed . . gsl_lcf_mapping . . . . . . . . gsm_cell_id_format . . . . . . . handover_power_level. . . . . . handover_required_curr_ch . . . handover_required_reject_switch . handover_required_sp_ver_used . hcs_thr . . . . . . . . . . . . . hdsl_losw_oos . . . . . . . . . hdsl_losw_restore . . . . . . . . hdsl_snr_daily . . . . . . . . . hdsl_snr_daily_mon_period . . . hdsl_snr_hourly . . . . . . . . . hdsl_snr_hourly_mon_period . . hdsl_snr_oos . . . . . . . . . . hdsl_snr_restore. . . . . . . . . ho_exist_congest . . . . . . . . ho_margin_def . . . . . . . . . ho_margin_type5 . . . . . . . . ho_margin_usage_flag . . . . . . ho_only_max_pwr . . . . . . . ho_pwr_level_inner . . . . . . . hop_count . . . . . . . . . . . hop_qual_enabled . . . . . . . . hopping_support . . . . . . . . hopping_systems_enabled . . . . hopping_systems_hsn . . . . . . hopping_systems_mobile_alloc . illegal_circuit_id . . . . . . . . immediate_assign_mode . . . . . inc_prp_cap_ena . . . . . . . . init_dl_cs . . . . . . . . . . . . init_ul_cs . . . . . . . . . . . . inner_zone_alg . . . . . . . . . intave. . . . . . . . . . . . . . inter_cell_handover_allowed . . . inter_rat_enabled . . . . . . . . interband_ho_allowed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viii GMR-01 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-295 5-297 5-299 5-301 5-304 5-306 5-308 5-309 5-310 5-312 5-313 5-315 5-317 5-318 5-319 5-321 5-323 5-324 5-326 5-328 5-330 5-333 5-335 5-337 5-338 5-340 5-341 5-342 5-344 5-345 5-347 5-348 5-350 5-352 5-354 5-356 5-357 5-359 5-361 5-363 5-364 5-366 5-368 5-370 5-372 5-374 5-375 5-377 5-379 5-381 5-383 5-386 5-388 5-390 5-392 68P02901W23-P 23 Feb 2004 Technical Description BSS Command Reference interfer_bands. . . . . . . . . intra_cell_handover_allowed . . ksw_config . . . . . . . . . . l_rxlev_dl_h . . . . . . . . . l_rxlev_dl_p . . . . . . . . . l_rxlev_ul_h . . . . . . . . . l_rxlev_ul_p . . . . . . . . . l_rxqual_dl_h . . . . . . . . . l_rxqual_dl_h_amr_fr . . . . . l_rxqual_dl_h_amr_hr . . . . . l_rxqual_dl_h_data . . . . . . l_rxqual_dl_h_hopping . . . . l_rxqual_dl_h_hopping_amr_fr. l_rxqual_dl_h_hopping_amr_hr l_rxqual_dl_p . . . . . . . . . l_rxqual_dl_p_amr_fr . . . . . l_rxqual_dl_p_amr_hr . . . . . l_rxqual_dl_p_data . . . . . . l_rxqual_dl_p_hopping . . . . l_rxqual_dl_p_hopping_amr_fr. l_rxqual_dl_p_hopping_amr_hr l_rxqual_ul_h . . . . . . . . . l_rxqual_ul_h_amr_fr . . . . . l_rxqual_ul_h_amr_hr . . . . . l_rxqual_ul_h_data . . . . . . l_rxqual_ul_h_hopping . . . . l_rxqual_ul_h_hopping_amr_fr. l_rxqual_ul_h_hopping_amr_hr l_rxqual_ul_p . . . . . . . . . l_rxqual_ul_p_amr_fr . . . . . l_rxqual_ul_p_amr_hr . . . . . l_rxqual_ul_p_data . . . . . . l_rxqual_ul_p_hopping . . . . l_rxqual_ul_p_hopping_amr_fr. l_rxqual_ul_p_hopping_amr_hr land_layer1_mode . . . . . . . layer_number . . . . . . . . . lb_int_called_pci . . . . . . . lb_int_calling_pci . . . . . . . lb_int_cr_calling . . . . . . . lb_int_dpc . . . . . . . . . . lb_int_global_reset_repetitions . lcs_mode . . . . . . . . . . . link_about_to_fail . . . . . . . link_fail . . . . . . . . . . . lmtl_loadshare_granularity . . . local_maintenance. . . . . . . low_sig_thresh . . . . . . . . lta_alarm_range . . . . . . . . max_gprs_ts_per_carrier . . . . max_ms_dl_buffer . . . . . . max_ms_dl_rate. . . . . . . . max_mtls . . . . . . . . . . . max_number_of_sdcchs . . . . max_q_length_channel . . . . 68P02901W23-P 23 Feb 2004 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-394 5-396 5-398 5-400 5-402 5-404 5-406 5-408 5-410 5-411 5-412 5-414 5-416 5-418 5-420 5-422 5-423 5-424 5-426 5-428 5-430 5-432 5-434 5-435 5-436 5-438 5-440 5-442 5-444 5-446 5-447 5-448 5-450 5-452 5-454 5-456 5-458 5-459 5-460 5-461 5-462 5-463 5-464 5-467 5-469 5-471 5-472 5-475 5-476 5-477 5-478 5-480 5-481 5-483 5-485 ix GMR-01 Contents max_q_length_sdcch . . . max_retran . . . . . . . . max_rst_ckt_timer_exps . . max_tx_bts . . . . . . . . max_tx_ms . . . . . . . . mb_preference . . . . . . mb_tch_congest_thres . . . missing_rpt . . . . . . . . mmi_cell_id_format . . . . mms_cat_enable . . . . . mms_config_type . . . . . ms_distance_allowed . . . ms_max_range . . . . . . ms_p_con_ack . . . . . . ms_p_con_interval . . . . ms_power_control_allowed ms_power_offset . . . . . ms_txpwr_max_cch . . . . ms_txpwr_max_cell . . . . ms_txpwr_max_def . . . . ms_txpwr_max_inner . . . msc_preference . . . . . . msc_qt . . . . . . . . . . msc_release . . . . . . . . mspwr_alg . . . . . . . . mtl_loadshare_granularity . multiband_reporting . . . . n_avg_i. . . . . . . . . . ncc_of_plmn_allowed . . . nccr_enabled . . . . . . . nccrOpt. . . . . . . . . . neighbor_journal . . . . . network_control_order. . . ni . . . . . . . . . . . . ns_alive_retries . . . . . . ns_block_retries. . . . . . ns_unblock_retries . . . . nsei . . . . . . . . . . . num_audit_retries . . . . . num_emerg_access . . . . num_emerg_rejected . . . num_emerg_tch_kill. . . . num_emerg_term_sdcch . . num_gbl_dl_thrput_samples num_gbl_ul_thrput_samples number_of_preferred_cells. number_sdcchs_preferred . opc . . . . . . . . . . . . option_alg_a5_1 . . . . . option_alg_a5_2 . . . . . option_alg_a5_3 . . . . . option_alg_a5_4 . . . . . option_alg_a5_5 . . . . . option_alg_a5_6 . . . . . option_alg_a5_7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . x GMR-01 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-487 5-488 5-490 5-491 5-497 5-499 5-500 5-501 5-502 5-503 5-505 5-507 5-509 5-511 5-513 5-515 5-517 5-518 5-521 5-523 5-525 5-526 5-528 5-530 5-531 5-532 5-533 5-535 5-536 5-538 5-539 5-540 5-542 5-544 5-546 5-547 5-548 5-549 5-550 5-551 5-552 5-553 5-554 5-555 5-556 5-557 5-559 5-561 5-563 5-564 5-565 5-566 5-567 5-568 5-569 68P02901W23-P 23 Feb 2004 Technical Description BSS Command Reference option_emergency_preempt . . . outer_zone_usage_level . . . . . override_intra_bss_pre_transfer . override_speech_version . . . . . pbgt_mode . . . . . . . . . . . pccch_enabled . . . . . . . . . pccchOpt . . . . . . . . . . . . pcr_enable . . . . . . . . . . . pcr_n1 . . . . . . . . . . . . . pcr_n2 . . . . . . . . . . . . . pcu_redundancy. . . . . . . . . percent_traf_cs . . . . . . . . . persistence_level . . . . . . . . phase_lock_gclk . . . . . . . . phase_lock_retry . . . . . . . . phase2_classmark_allowed. . . . phase2_resource_ind_allowed . . pic_error_clr_thresh . . . . . . . pic_error_gen_thresh . . . . . . pic_error_inc . . . . . . . . . . pkt_radio_type . . . . . . . . . pool_gproc_preemption . . . . . poor_initial_assignment . . . . . pow_inc_step_size_dl . . . . . . pow_inc_step_size_ul . . . . . . pow_red_step_size_dl . . . . . . pow_red_step_size_ul . . . . . . prach_max_retran . . . . . . . . prach_s . . . . . . . . . . . . . prach_tx_int . . . . . . . . . . primary_pcu . . . . . . . . . . prioritize_microcell . . . . . . . priority_class . . . . . . . . . . protect_last_ts. . . . . . . . . . prp_capacity_opt . . . . . . . . prr_aggr_factor . . . . . . . . . pwr_handover_allowed . . . . . pwrc . . . . . . . . . . . . . . queue_management_information . qsearch_c_initial . . . . . . . . qsearch_i . . . . . . . . . . . . qsearch_p . . . . . . . . . . . . ra_colour . . . . . . . . . . . . ra_reselect_hysteresis . . . . . . rac . . . . . . . . . . . . . . . rach_load_period . . . . . . . . rach_load_threshold . . . . . . . rach_load_type . . . . . . . . . radio_link_timeout . . . . . . . rapid_pwr_down . . . . . . . . rci_error_clr_thresh . . . . . . . rci_error_gen_thresh. . . . . . . rci_error_inc . . . . . . . . . . red_loss_daily. . . . . . . . . . red_loss_hourly . . . . . . . . . 68P02901W23-P 23 Feb 2004 Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-570 5-572 5-573 5-574 5-575 5-576 5-578 5-579 5-580 5-581 5-582 5-584 5-585 5-587 5-588 5-589 5-590 5-591 5-592 5-593 5-594 5-598 5-599 5-600 5-602 5-604 5-606 5-608 5-609 5-611 5-613 5-615 5-616 5-617 5-619 5-620 5-621 5-623 5-625 5-627 5-628 5-629 5-631 5-633 5-635 5-637 5-639 5-641 5-642 5-644 5-646 5-647 5-648 5-649 5-650 xi GMR-01 Contents red_loss_oos . . . . . . . . . . . . . red_loss_restore . . . . . . . . . . . . red_time_oos . . . . . . . . . . . . . red_time_restore . . . . . . . . . . . reestablish_allowed . . . . . . . . . . rel_tim_adv . . . . . . . . . . . . . . remote_loss_daily . . . . . . . . . . . remote_loss_hourly . . . . . . . . . . remote_loss_oos . . . . . . . . . . . remote_loss_restore . . . . . . . . . . remote_time_oos . . . . . . . . . . . remote_time_restore . . . . . . . . . . report_resource_tch_f_high_water_mark report_resource_tch_f_low_water_mark res_gprs_pdchs . . . . . . . . . . . . res_ts_less_one_carrier . . . . . . . . rf_res_ind_period . . . . . . . . . . . rpd_offset. . . . . . . . . . . . . . . rpd_period . . . . . . . . . . . . . . rpd_trigger . . . . . . . . . . . . . . rpt_bad_qual_no_mr. . . . . . . . . . rtf_path_enable . . . . . . . . . . . . rxlev_access_min . . . . . . . . . . . rxlev_dl_ho . . . . . . . . . . . . . . rxlev_dl_pc . . . . . . . . . . . . . . rxlev_dl_zone . . . . . . . . . . . . . rxlev_min_def . . . . . . . . . . . . rxlev_ul_ho . . . . . . . . . . . . . . rxlev_ul_pc . . . . . . . . . . . . . . rxlev_ul_zone . . . . . . . . . . . . . rxqual_dl_ho . . . . . . . . . . . . . rxqual_dl_pc . . . . . . . . . . . . . rxqual_ul_ho . . . . . . . . . . . . . rxqual_ul_pc . . . . . . . . . . . . . sap_audit_type . . . . . . . . . . . . sap_device_type. . . . . . . . . . . . sap_end_time . . . . . . . . . . . . . sap_interval . . . . . . . . . . . . . . sap_start_time. . . . . . . . . . . . . sccp_bssap_mgt . . . . . . . . . . . . scr_enabled . . . . . . . . . . . . . . sdcch_ho . . . . . . . . . . . . . . . sdcch_need_high_water_mark . . . . . sdcch_need_low_water_mark . . . . . sdcch_tch_band_reassign_delay . . . . sdcch_timer_ho . . . . . . . . . . . . search_prio_3g . . . . . . . . . . . . second_asgnmnt. . . . . . . . . . . . secondary_freq_type. . . . . . . . . . sgsn_release . . . . . . . . . . . . . slip_loss_daily . . . . . . . . . . . . slip_loss_hourly. . . . . . . . . . . . slip_loss_oos . . . . . . . . . . . . . slip_loss_restore . . . . . . . . . . . smg_gb_vers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xii GMR-01 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-651 5-652 5-653 5-654 5-655 5-657 5-659 5-660 5-661 5-662 5-663 5-664 5-665 5-667 5-669 5-671 5-673 5-674 5-675 5-676 5-678 5-680 5-681 5-683 5-685 5-687 5-689 5-691 5-693 5-695 5-697 5-699 5-701 5-703 5-705 5-706 5-707 5-708 5-710 5-712 5-714 5-716 5-718 5-720 5-722 5-723 5-725 5-726 5-728 5-730 5-731 5-732 5-734 5-735 5-736 68P02901W23-P 23 Feb 2004 Technical Description BSS Command Reference sms_dl_allowed . . . . . . . . sms_tch_chan . . . . . . . . . sms_ul_allowed . . . . . . . . ss7_mode . . . . . . . . . . . ssm_critical_overload_threshold ssm_normal_overload_threshold ssp_burst_delay . . . . . . . . ssp_burst_limit . . . . . . . . stat_interval. . . . . . . . . . surround_cell . . . . . . . . . sw_ts_less_one_carrier . . . . swfm_enable . . . . . . . . . switch_gprs_pdchs . . . . . . sync_loss_daily . . . . . . . . sync_loss_hourly . . . . . . . sync_loss_oos. . . . . . . . . sync_loss_restore . . . . . . . sync_time_oos . . . . . . . . sync_time_restore . . . . . . . t_avg_t . . . . . . . . . . . . t_avg_w . . . . . . . . . . . tch_busy_critical_threshold . . tch_busy_norm_threshold . . . tch_congest_prevent_thres . . . tch_flow_control . . . . . . . tch_full_need_low_water_mark temporary_offset . . . . . . . threshold . . . . . . . . . . . timing_advance_period . . . . tlli_blk_coding . . . . . . . . trace_msgs_after_ho. . . . . . trace_msgs_before_ho . . . . . trans_capability . . . . . . . . trunk_critical_threshold . . . . trunk_major_threshold. . . . . ts_alloc_flag . . . . . . . . . ts_in_usf_active . . . . . . . . tsc_update_method . . . . . . tx_integer . . . . . . . . . . . tx_power_cap . . . . . . . . . u_rxlev_dl_ih . . . . . . . . . u_rxlev_dl_p . . . . . . . . . u_rxlev_ul_ih . . . . . . . . . u_rxlev_ul_p . . . . . . . . . u_rxqual_dl_p. . . . . . . . . u_rxqual_dl_p_amr_hr. . . . . u_rxqual_ul_p. . . . . . . . . u_rxqual_ul_p_amr_hr. . . . . ul_audio_lev_offset . . . . . . ul_rxlev_ho_allowed . . . . . ul_rxqual_ho_allowed . . . . . unequipped_circuit_allowed . . use_derived_ho_power . . . . use_neighbor_pbgt_hreqave . . volume_control_type . . . . . 68P02901W23-P 23 Feb 2004 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-737 5-738 5-740 5-741 5-743 5-745 5-746 5-747 5-748 5-749 5-751 5-753 5-754 5-756 5-757 5-758 5-759 5-760 5-761 5-762 5-763 5-764 5-765 5-766 5-767 5-769 5-771 5-773 5-774 5-776 5-777 5-778 5-779 5-781 5-782 5-783 5-784 5-785 5-787 5-789 5-791 5-793 5-795 5-797 5-799 5-801 5-802 5-804 5-805 5-806 5-808 5-810 5-812 5-813 5-814 xiii GMR-01 Contents wait_for_reselection . . . . . . wait_indication_parameters . . worse_neighbor_ho . . . . . . zone_ho_hyst . . . . . . . . . zone_pingpong_count . . . . . zone_pingpong_disable_win . . zone_pingpong_enable_win . . zone_pingpong_preferred_zone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-816 5-817 5-819 5-820 5-822 5-823 5-824 5-825 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2 6-3 6-5 6-6 6-8 6-10 6-11 6-12 6-13 6-14 6-15 6-17 6-19 6-21 6-22 6-24 6-26 6-28 6-29 6-30 6-32 6-34 6-36 6-38 6-40 6-41 6-42 6-44 6-45 6-46 6-47 6-49 6-50 6-52 6-54 6-55 6-56 6-58 6-60 6-61 6-63 6-65 6-66 6-68 Chapter 6: Timer parameters add_access_class . . . . assign_successful . . . . auto_dl_dur . . . . . . . bcch_info . . . . . . . . bep_period . . . . . . . bep_period2. . . . . . . bounce_protect_cong_tmr bounce_protect_qual_tmr bsc_audit . . . . . . . . bsc_audit_response . . . bssgp_fc_period_c . . . bssgp_t1_timer . . . . . bssgp_t2_timer . . . . . bssmap_t1 . . . . . . . bssmap_t10 . . . . . . . bssmap_t11 . . . . . . . bssmap_t13 . . . . . . . bssmap_t19 . . . . . . . bssmap_t20 . . . . . . . bssmap_t4 . . . . . . . bssmap_t7 . . . . . . . bssmap_t8 . . . . . . . bssmap_tqho . . . . . . bts_audit . . . . . . . . bts_audit_response . . . bts_escalation . . . . . . carrier_free_immediate . cbch_1 . . . . . . . . . cbch_2 . . . . . . . . . cbch_3 . . . . . . . . . channel_act . . . . . . . channel_teardown . . . . cipher_comp_ms . . . . ciphering_successful. . . circuit_reset_ack . . . . clear_cmd_ext_ho . . . . clear_command . . . . . dealloc_inact . . . . . . delay_dl_rel_dur . . . . downlink_sync_timer . . dynet_retry_time . . . . early_classmark_delay. . emerg_reserved . . . . . ext_ho_allocation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiv GMR-01 68P02901W23-P 23 Feb 2004 Technical Description BSS Command Reference ext_rtry_cand_prd . . . . . . flow_control_t1 . . . . . . . flow_control_t2 . . . . . . . gbl_thrput_period . . . . . . gprs_penalty_time . . . . . . gprs_smg30_t3192 . . . . . gprs_t3168 . . . . . . . . . gprs_t3192 . . . . . . . . . handover_recognized_period . ho_ack . . . . . . . . . . . ho_allocation . . . . . . . . ho_complete . . . . . . . . ho_request . . . . . . . . . ho_successful . . . . . . . . hop_count_timer . . . . . . initial_sync_timer . . . . . . lb_int_bssmap_t13 . . . . . lb_int_bssmap_t4 . . . . . . lb_int_clear_command. . . . lb_int_sccp_released. . . . . lb_int_sccp_tconn_est . . . . lb_int_sccp_tiar . . . . . . . lb_int_sccp_tias . . . . . . . lb_int_sccp_trel . . . . . . . lb_int_spi . . . . . . . . . . lb_int_ss7_l2_t1. . . . . . . lb_int_ss7_l2_t2. . . . . . . lb_int_ss7_l2_t3. . . . . . . lb_int_ss7_l2_t4. . . . . . . lb_int_ss7_l2_t5. . . . . . . lb_int_ss7_l2_t6. . . . . . . lb_int_ss7_l2_t7. . . . . . . lb_int_ss7_l3_t1. . . . . . . lb_int_ss7_l3_t12 . . . . . . lb_int_ss7_l3_t13 . . . . . . lb_int_ss7_l3_t14 . . . . . . lb_int_ss7_l3_t17 . . . . . . lb_int_ss7_l3_t2. . . . . . . lb_int_ss7_l3_t22 . . . . . . lb_int_ss7_l3_t23 . . . . . . lb_int_ss7_l3_t4. . . . . . . lb_int_ss7_l3_t5. . . . . . . lb_int_ss7_slt_t1 . . . . . . lb_int_t_stat_info . . . . . . lcs_perf_location . . . . . . lcs_segmentation . . . . . . lcs_supervision . . . . . . . mode_modify . . . . . . . . mode_rr_modify_ack . . . . ms_sapi3_est . . . . . . . . nc_non_drx_period . . . . . nc_reporting_period_i . . . . nc_reporting_period_t . . . . neighbor_report_timer . . . . ns_alive_timer . . . . . . . 68P02901W23-P 23 Feb 2004 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-69 6-70 6-72 6-74 6-75 6-77 6-78 6-79 6-80 6-82 6-84 6-85 6-87 6-88 6-89 6-90 6-92 6-93 6-94 6-95 6-96 6-97 6-98 6-99 6-100 6-101 6-102 6-103 6-104 6-105 6-106 6-107 6-108 6-109 6-110 6-111 6-112 6-113 6-114 6-116 6-118 6-119 6-120 6-121 6-122 6-123 6-124 6-125 6-127 6-129 6-131 6-133 6-134 6-136 6-137 xv GMR-01 Contents ns_block_timer . . . . ns_reset_period . . . . ns_reset_timer . . . . ns_test_timer . . . . . pccch_drx_timer_max . penalty_time . . . . . phase_lock_duration. . psi1_repeat_period . . radio_chan_released . . register_exp. . . . . . rf_chan_rel_ack . . . . rr_ny1_rep . . . . . . rr_t3101 . . . . . . . rr_t3103 . . . . . . . rr_t3105 . . . . . . . rr_t3109 . . . . . . . rr_t3111_sd . . . . . . rr_t3111_tch . . . . . rr_t3212 . . . . . . . rtry_cand_prd . . . . . sacch_info . . . . . . sccp_released . . . . . sccp_tconn_est . . . . sccp_tiar . . . . . . . sccp_tias . . . . . . . sccp_trel . . . . . . . sm_audit_response . . spi . . . . . . . . . . ss7_l2_t1 . . . . . . . ss7_l2_t2 . . . . . . . ss7_l2_t3 . . . . . . . ss7_l2_t4 . . . . . . . ss7_l2_t5 . . . . . . . ss7_l2_t6 . . . . . . . ss7_l2_t7 . . . . . . . ss7_l3_t1 . . . . . . . ss7_l3_t12 . . . . . . ss7_l3_t13 . . . . . . ss7_l3_t14 . . . . . . ss7_l3_t17 . . . . . . ss7_l3_t2 . . . . . . . ss7_l3_t22 . . . . . . ss7_l3_t23 . . . . . . ss7_l3_t4 . . . . . . . ss7_l3_t5 . . . . . . . ss7_slt_t1 . . . . . . . start_ack . . . . . . . static_sync_timer . . . t_stat_info . . . . . . uplink_sync_timer. . . valid_candidate_period . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-138 6-139 6-140 6-141 6-142 6-144 6-146 6-147 6-149 6-151 6-152 6-154 6-156 6-158 6-160 6-162 6-164 6-166 6-168 6-170 6-172 6-174 6-175 6-176 6-178 6-180 6-181 6-182 6-184 6-186 6-188 6-190 6-191 6-192 6-194 6-195 6-196 6-197 6-198 6-199 6-200 6-201 6-203 6-205 6-206 6-207 6-208 6-209 6-211 6-212 6-214 Device and function database parameters presentation . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2 Chapter 7: Device/function parameters xvi GMR-01 68P02901W23-P 23 Feb 2004 Contents antenna_select . . . . . ber_oos_mon_period . . ber_restore_mon_period . bsc_cbc_operator . . . . cabinet_type . . . . . . cavity. . . . . . . . . . cbc_operator . . . . . . cell_zone . . . . . . . . chan_alloc_priority . . . cic_validation . . . . . . clkx0 . . . . . . . . . . clkx1 . . . . . . . . . . clkx2 . . . . . . . . . . combiner_address . . . . combiner_id . . . . . . combining_type . . . . . dri_density . . . . . . . ext_timeslots . . . . . . fm_cell_type . . . . . . frequency_type . . . . . hdsl_modem_setting. . . hdsl_oos_mon_period . . hdsl_restore_mon_period ias_connected . . . . . . int_antenna . . . . . . . int_hdsl_modem . . . . lapd_k . . . . . . . . . lapd_n200 . . . . . . . lapd_t200_timer. . . . . max_cbls . . . . . . . . max_dris . . . . . . . . max_gsls . . . . . . . . max_mtls . . . . . . . . mms_priority . . . . . . msc_mms_id . . . . . . msi_type . . . . . . . . n391 . . . . . . . . . . n392 . . . . . . . . . . n393 . . . . . . . . . . nbit. . . . . . . . . . . ne_id . . . . . . . . . . opto_reporting . . . . . pref_rtf_id . . . . . . . rsl_rate . . . . . . . . . sd_load . . . . . . . . . sd_priority . . . . . . . shared_timeslots . . . . slot . . . . . . . . . . . start_ts . . . . . . . . . t391 . . . . . . . . . . t392 . . . . . . . . . . tcu_port . . . . . . . . transcoding_capability . . tru_id. . . . . . . . . . trx_pwr_red. . . . . . . 68P02901W23-P 23 Feb 2004 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-5 7-7 7-9 7-11 7-12 7-15 7-16 7-17 7-19 7-20 7-21 7-23 7-25 7-27 7-28 7-29 7-31 7-32 7-34 7-36 7-38 7-40 7-42 7-44 7-45 7-46 7-47 7-49 7-51 7-53 7-54 7-56 7-57 7-59 7-61 7-62 7-64 7-65 7-66 7-67 7-68 7-69 7-71 7-72 7-73 7-75 7-77 7-78 7-79 7-80 7-82 7-83 7-85 7-86 7-87 xvii GMR-01 Contents This page intentionally left blank. xviii GMR-01 68P02901W23-P 23 Feb 2004 List of Figures List of Figures Figure 2-1: Figure 2-2: Figure 2-3: Figure 2-4: Remote Transcoder (RXCDR) devices and functions BSC and InCell BTS . . . . . . . . . . . . . . . In-Cell and Horizonmacro equipage hierarchy chart GPRS PCU devices and functions . . . . . . . . . 68P02901W23-P 23 Feb 2004 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-332 2-333 2-334 2-335 xix GMR-01 List of Figures This page intentionally left blank. xx GMR-01 68P02901W23-P 23 Feb 2004 List of Tables List of Tables Table 1: Manual version history . . . . . . . . . . . . . . . . . . . . Table 2: Service requests resolved in this manual . . . . . . . . . . . . Table 1-1: MMI command availability by location . . . . . . . . . . . . Table 1-2: MMI command availability by SYSGEN mode . . . . . . . . Table 1-3: Device Indices . . . . . . . . . . . . . . . . . . . . . . . Table 1-4: Alarm Severities . . . . . . . . . . . . . . . . . . . . . . Table 2-1: Device literals and descriptions . . . . . . . . . . . . . . . Table 2-2: Device and command relationship . . . . . . . . . . . . . . Table 2-3: Device ID requirements . . . . . . . . . . . . . . . . . . . Table 2-4: Function related commands . . . . . . . . . . . . . . . . . Table 2-5: Function ID requirements . . . . . . . . . . . . . . . . . . Table 2-6: Valid slots . . . . . . . . . . . . . . . . . . . . . . . . . Table 2-7: Equip/Unequip command matrix . . . . . . . . . . . . . . . Table 2-8: Alarm devices . . . . . . . . . . . . . . . . . . . . . . . Table 2-9: add_cell command prompts . . . . . . . . . . . . . . . . . Table 2-10: add_conn valid ranges . . . . . . . . . . . . . . . . . . . Table 2-11: Neighbour Frequency and number with EGSM source cell . . Table 2-12: Neighbour Frequency and number with DCS1800 source cell . Table 2-13: add_neighbor command prompts. . . . . . . . . . . . . . Table 2-14: Codec Mode Values / Rates. . . . . . . . . . . . . . . . . Table 2-15: Full Rate attribute values for chg_acs_params command. . . Table 2-16: Half Rate attribute values for chg_acs_params command . . Table 2-17: Full Rate prompts for the chg_acs_params command . . . . Table 2-18: Half Rate prompts for chg_acs_params command . . . . . . Table 2-19: Device scheduling defaults . . . . . . . . . . . . . . . . . Table 2-20: RXCDR default DTE addresses . . . . . . . . . . . . . . . Table 2-21: BSC default DTE addresses . . . . . . . . . . . . . . . . Table 2-22: EAS default alarm strings . . . . . . . . . . . . . . . . . Table 2-23: Baseband and Synthesizer frequency hopping restrictions. . . Table 2-24: chg_hop_params prompts . . . . . . . . . . . . . . . . . Table 2-25: Cell frequencies/mobile allocation . . . . . . . . . . . . . Table 2-26: Restrictions on related commands . . . . . . . . . . . . . . Table 2-27: SMS special characters . . . . . . . . . . . . . . . . . . . Table 2-28: copy_path command prompts . . . . . . . . . . . . . . . Table 2-29: mod_conn valid ranges . . . . . . . . . . . . . . . . . . Table 2-30: Operational states . . . . . . . . . . . . . . . . . . . . . Table 2-31: Administrative states . . . . . . . . . . . . . . . . . . . . Table 2-32: Device states . . . . . . . . . . . . . . . . . . . . . . . Table 2-33: Reason codes . . . . . . . . . . . . . . . . . . . . . . . Table 2-34: trace_call prompts and values . . . . . . . . . . . . . . . Table 4-1: Counter and gauge statistic type prompts . . . . . . . . . . . Table 4-2: Normal and weighted distribution statistic type prompts . . . . 68P02901W23-P 23 Feb 2004 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 3 1-11 1-15 1-23 1-25 2-3 2-4 2-8 2-14 2-15 2-16 2-17 2-19 2-25 2-34 2-35 2-36 2-40 2-62 2-63 2-64 2-65 2-66 2-74 2-87 2-87 2-92 2-104 2-107 2-108 2-109 2-131 2-163 2-391 2-454 2-454 2-455 2-455 2-480 4-9 4-9 xxi GMR-01 List of Tables Table 5-1: alt_qual_proc=0 parameter values . . . . . . . . . . . . . . . . . . . Table 5-2: alt_qual_proc=1 parameter values . . . . . . . . . . . . . . . . . . . Table 5-3: Base Station Identity Code - Hexadecimal Values . . . . . . . . . . . . Table 5-4: Base Station Identity Code - Decimal Values . . . . . . . . . . . . . . Table 5-5: CTU2 values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 5-6: Cabinet antenna connector maximum output power (Watts) . . . . . . . Table 5-7: Values for PGSM, EGSM, DCS1800 and PCS1900 M-Cellmicro,etc. sites Table 5-8: Values for DCS1800 and M-Cellaccess, sites . . . . . . . . . . . . . . Table 5-9: Sample output power . . . . . . . . . . . . . . . . . . . . . . . . . Table 5-10: Values for barring classes. . . . . . . . . . . . . . . . . . . . . . . Table 5-11: Maximum mobile power level for PGSM, EGSM and GSM850 cells . . Table 5-12: Maximum mobile power level for DCS1800 cells . . . . . . . . . . . Table 5-13: Maximum mobile power level for PCS1900 cells . . . . . . . . . . . Table 5-14: Modes for gprs_network_operation_mode . . . . . . . . . . . . . . Table 5-15: Max MS power level for PGSM and EGSM . . . . . . . . . . . . . . Table 5-16: Max MS power level for DCS1800 and PCS1900 cells . . . . . . . . . Table 5-17: Max MS power level for class 3 mobiles . . . . . . . . . . . . . . . Table 5-18: Max MS power level for PGSM and EGSM cells . . . . . . . . . . . Table 5-19: Max MS power level for DCS1800 and PCS1900 cells . . . . . . . . . Table 5-20: Max MS level for class 3 mobiles . . . . . . . . . . . . . . . . . . . Table 5-21: Prompted parameters for Dual Band Cell use . . . . . . . . . . . . . Table 5-22: CTU2 values . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 5-23: Cabinet antenna connector maximum output power (Watts) . . . . . . . Table 5-24: Values for PGSM, EGSM, DCS1800 and PCS1900, etc. sites . . . . . . Table 5-25: Values for DCS1800 and M-Cellaccess sites . . . . . . . . . . . . . . Table 5-26: Sample output power. . . . . . . . . . . . . . . . . . . . . . . . . Table 5-27: Value interpolation . . . . . . . . . . . . . . . . . . . . . . . . . . Table 5-28: ms_max_range values for normal cells . . . . . . . . . . . . . . . . Table 5-29: ms_max_range values for Extended Range cells. . . . . . . . . . . . Table 5-30: Maximum mobile power level for PGSM and EGSM cells . . . . . . . Table 5-31: Maximum mobile power level for DCS1800 cells . . . . . . . . . . . Table 5-32: Maximum mobile power level for PCS1900 cells . . . . . . . . . . . Table 5-33: Bit mapping of ncc_of_plmn_allowed . . . . . . . . . . . . . . . . Table 5-34: Configurations for network_control_order . . . . . . . . . . . . . . Table 5-35: EGPRS backport and backfill guideline . . . . . . . . . . . . . . . . Table 5-36: pkt_radio_type translation . . . . . . . . . . . . . . . . . . . . . . Table 5-37: Values for prach_tx_int representing number of frame slots . . . . . . Table 5-38: qsearch_p attribute values below threshold . . . . . . . . . . . . . . Table 5-39: qsearch_p attribute values above threshold . . . . . . . . . . . . . . Table 5-40: Example cell configurations for rach_load_threshold . . . . . . . . . Table 6-1: Impermissible combinations of psi1_repeat_period and bs_pbcch_blks . Table 7-1: Cabinets/Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 7-2: Values for PGSM, EGSM and PCS 1900 sites . . . . . . . . . . . . . . Table 7-3: Values for DCS 1800 sites . . . . . . . . . . . . . . . . . . . . . . . Table 7-4: Values for PGSM and EGSM M-Cellmicro sites. . . . . . . . . . . . . Table 7-5: Values for DCS 1800 and PCS 1900 M-Cellmicro sites . . . . . . . . . xxii GMR-01 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-23 5-24 5-79 5-79 5-95 5-96 5-96 5-97 5-97 5-121 5-302 5-302 5-302 5-304 5-331 5-331 5-331 5-362 5-362 5-362 5-385 5-492 5-493 5-493 5-494 5-494 5-495 5-510 5-510 5-519 5-519 5-520 5-537 5-542 5-595 5-595 5-612 5-630 5-630 5-639 6-148 7-12 7-88 7-88 7-89 7-89 68P02901W23-P 23 Feb 2004 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-P 23 Feb 2004 1 GMR-01 Issue status of this manual Issue status of this manual The following shows the issue status of this manual since it was first released. Version information The following table lists the versions of this manual in order of issue: Table 1 Manual version history Manual issue Remarks Date of issue O 3 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 2 GMR-01 68P02901W23-P 23 Feb 2004 Issue status of this manual Resolution of Service Requests The following Service Requests are now resolved in this manual: Table 2 Service requests resolved in this manual Service Request GMR 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 thechg_audit_sched command description. SR1065717 GMR 01 Added four new zone_pingpong parameters. (This is a partial fix for BSC MMI only) 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. SR1069401 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. SR1076366 N/A Inserted missing unit (seconds) for the gprs_drx_timer_max parameter value. SR1076367 N/A Added “as the BCCH carrier.” to dependencies of use_bcch_for_gprs parameter. NOTE: Functionality of use_bcch_for_gprs parameter replaced by pkt_radio_type. GMR 01 Remarks 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. SR1091037 GMR 01 Amended bss_msc_overload_allowed parameter description. 68P02901W23-P 23 Feb 2004 3 GMR-01 Issue status of this manual Version updates MMI commands and parameters that are new, modified or deleted as a result of the introduction of software release GSR7, are listed below as: • New commands and parameters shown in bold emphasis. • Modified commands and parameters shown in normal type. • Deleted commands and parameters shown in italics. New, modified and deleted commands introduced by GSR7 add_cell disp_mms_ts_usage add_nsvc disp_options alarm_mode disp_processor assess disp_rtf_channel cage_audit disp_stats chg_acs_params download_ltu chg_audit_sched equip chg_cell_element ins_device chg_element lock_device chg_hop_params mod_nsvc chg_rtf_freq modify_value copy_cell page del_act_alarm query_audits del_nsvc reassign device_audit reset_device diagnose_device reset_ltu disp_acs reset_site disp_act_alarm site_audit disp_bss soft_reset disp_cell_map state disp_cell_status sysgen_mode disp_element unequip disp_equipment unlock_device 4 GMR-01 68P02901W23-P 23 Feb 2004 Issue status of this manual New, modified and deleted database parameters introduced by GSR7 allow_8k_trau gprs_temporary_offset allow_32k trau (see note) gprs_ul_dl_bias amr_bss_full_rate_enabled gsl_lcf_mapping amr_bss_half_rate_enabled hcs_thr amr_dl_la_mode_chg_min inc_prp_cap_ena amr_dl_thresh_adjust init_dl_cs amr_force_hr_usage init_ul_cs amr_fr_dl_la_enabled inter_rat_enabled amr_fr_ul_la_enabled l_rxqual_dl_h_amr_fr amr_full_rate_enabled l_rxqual_dl_h_amr_hr amr_half_rate_enable l_rxqual_dl_h_hopping_amr_fr amr_hop_count l_rxqual_dl_h_hopping_amr_hr amr_hr_dl_la_enabled l_rxqual_dl_p_amr_fr amr_hr_ul_la_enabled l_rxqual_dl_p_amr_hr amr_hr_intracell_ho_allowed l_rxqual_dl_p_hopping_amr_fr amr_hr_res_ts l_rxqual_dl_p_hopping_amr_hr amr_inner_hr_usage_thres l_rxqual_ul_h_amr_fr amr_ms_high_cmr l_rxqual_ul_h_amr_hr amr_ms_high_rxqual l_rxqual_ul_h_hopping_amr_fr amr_ms_low_cmr l_rxqual_ul_h_hopping_amr_hr amr_ms_low_rxqual l_rxqual_ul_p_amr_fr amr_ms_monitor_period l_rxqual_ul_p_amr_hr amr_new_calls_hr l_rxqual_ul_p_hopping_amr_fr amr_reconfig_fr_to_hr l_rxqual_ul_p_hopping_amr_hr bep_period max_mtls bep_period2 max_q_length_channel bs_pag_blks_res min_gprs_ts_per_carrier bs_pbcch_blks msi_type bs_pcc_chans network_control_order bs_prach_blks nsei bssgp_cbl_bit override_speech_version ccch_conf pccch_drx_timer_max cic_block_thresh pccch_enabled cic_unblock_thresh pccchOpt c31_hyst pcu_redundancy 68P02901W23-P 23 Feb 2004 5 GMR-01 Issue status of this manual c32_qual percent_traf_cs ddtr_ctrl_enabled persistence_level delay_ul_rel_dur pkt_radio_type (see note) eac_mode prach_max_retran egprs_init_dl_cs prach_s egprs_init_ul_cs prach_tx_intc ext_range_cell primary_pcu fdd_gprs_qoffset priority_class gproc_slots prp_capacity_opt gprs_cell_cgt_thr prr_aggr_factor gprs_cell_reselect_hysteresis psi1_repeat_period gprs_com_ms_class qsearch_p gprs_cr_margin ra_reselect_hysteresis gprs_dl_pwr_mode scr_enabled gprs_enabled search_prio_3g gprs_mac_mode sgsn_release gprs_max_ul_ts tlli_blk_coding gprs_min_prr_blks trans_capability gprs_ms_txpwr_max_cch u_rxqual_dl_p_amr_hr gprs_network_operation_mode u_rxqual_ul_p_amr_hr gprs_num_pmrs use_bcch_for_gprs (see note) gprs_penalty_time zone_pingpong_count gprs_reselect_offset zone_pingpong_disable_win gprs_rxlev_access_min zone_pingpong_enable_win gprs_sched_beta zone_pingpong_preferred_zone The pkt_radio_type parameter replaces the functionality of allow_32k_trau and use_bcch_for_gprs parameters. 6 GMR-01 68P02901W23-P 23 Feb 2004 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. 68P02901W23-P 23 Feb 2004 7 GMR-01 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 displays (in special fonts). On a separate line immediately above the affected item. For a list of Roadmap numbers and the RDB or RDP numbers of the features included in this software release, refer to the 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. 8 GMR-01 68P02901W23-P 23 Feb 2004 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. 68P02901W23-P 23 Feb 2004 9 GMR-01 4 Collect evidence from the equipment under the guidance of the Customer Network Resolution Centre. Swindon +44 (0)1793 430987 or China +86 10 68423633 (fax). Ensure that all site personnel are familiar with this procedure. 2 Make no further attempt to adjust or rectify the equipment. for example by removing power. carry out the following procedure in all instances. Swindon +44 (0)1793 565444 or China +86 10 88417733 (telephone) and follow up with a written report by fax. 3 Report the problem directly to the Customer Network Resolution Centre. 10 GMR-01 68P02901W23-P 23 Feb 2004 .Reporting safety issues Reporting safety issues Whenever a safety issue arises. Procedure Whenever a safety issue arises: Procedure 1 Safety issue reporting 1 Make the equipment concerned safe. or with specific warnings elsewhere in the Motorola manuals. Failure to comply with these warnings. physical injury. violates safety standards of design. manufacture and intended use of the equipment. or on the equipment itself. Motorola assumes no liability for the customer’s failure to comply with these requirements. Failure to comply with warnings Observe all warnings during all phases of operation. Laser radiation can come from either the data in/out connectors or unterminated fibre optic cables connected to data in/out connectors. Example and format Do not look directly into fibre optic cables or data in/out connectors. 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. for example. Cautions A definition and example follow below: 68P02901W23-P 23 Feb 2004 11 GMR-01 . as well as those inherent in the equipment.Warnings and cautions Warnings and cautions The following describes how warnings and cautions are used in this manual and in all manuals of this Motorola manual set. installation and maintenance of the equipment described in the Motorola manuals. the use of adhesives and solvents. This includes hazards introduced during maintenance. or ill health. Warnings and cautions Definition of Caution A caution means that there is a possibility of damage to systems. However. arrange for calibration to be carried out. Example and format Do not use test equipment that is beyond its due calibration date. software or individual items of equipment within a system. 12 GMR-01 68P02901W23-P 23 Feb 2004 . this presents no danger to personnel. Failure to comply with these warnings. and will be incorporated into procedures as applicable. or with specific warnings elsewhere in the Motorola manuals. manufacture and intended use of the equipment. in the illustrations and on the equipment. • Battery supplies. • Lithium batteries. painted over or obscured in any way. • Laser radiation. These must be observed by all personnel at all times when working with the equipment. Warning labels must not be removed. • Parts substitution.General warnings General warnings Observe the following specific warnings during all phases of operation. • RF radiation. installation and maintenance of the equipment described in the Motorola manuals: • Potentially hazardous voltage. • Heavy equipment. Specific warnings Specific warnings used throughout the GSM manual set are shown below. violates safety standards of design. Warning labels Warnings particularly applicable to the equipment are positioned on the equipment. 68P02901W23-P 23 Feb 2004 13 GMR-01 . • Electric shock. as must any other warnings given in text. Personnel working with or operating Motorola equipment must comply with any warning labels fitted to the equipment. Motorola assumes no liability for the customer’s failure to comply with these requirements. until trained first aid or medical assistance arrives.c. three phase supply.c. the a. When working with electrical equipment. 14 GMR-01 68P02901W23-P 23 Feb 2004 . supply. RF radiation High RF potentials and electromagnetic fields are present in this equipment when in operation. flood the affected area with cold water to cool.General warnings Potentially hazardous voltage This equipment operates from a potentially hazardous voltage of 230 V a. Switch off.c. and even the heart. protect yourself with dry insulating material and pull or push the victim clear of the conductor. to stop. ALWAYS send for trained first aid or medical assistance IMMEDIATELY. or to the relevant electricity at work legislation for the country in which the equipment is used. If this is not possible. Motorola GSM equipment does not utilise high voltages. To achieve isolation of the equipment from the a. serious injuries and even death. Electric shock Do not touch the victim with your bare hands until the electric circuit is broken. reference must be made to the Electricity at Work Regulations 1989 (UK). single phase or 415 V a. input isolator must be set to off and locked. It can also cause skin burns at the points of entry and exit of the current. ALWAYS send for trained first aid or medical assistance IMMEDIATELY. Ensure that all transmitters are switched off when any antenna connections have to be changed. In cases of low voltage electric shock (including public supply voltages). If the casualty is also suffering from burns. may result. Do not key transmitters connected to unterminated cavities or feeders.c. In the event of an electric shock it may be necessary to carry out artificial respiration. Direct electrical contact can stun a casualty causing breathing. or removing or replacing equipment. Laser radiation can come from either the data in/out connectors or unterminated fibre optic cables connected to data in/out connectors. 3 kHz to 300 GHz • CENELEC 95 ENV 50166-2.General warnings Relevant standards (USA and EC). Parts substitution Do not install substitute parts or perform any unauthorized modification of equipment. When dismantling heavy assemblies. When equipment has to be manhandled. Where provided. because of the danger of introducing additional hazards. to which regard should be paid when working with RF equipment are: • ANSI IEEE C95. lifting frames must be used for these operations. Laser radiation Do not look directly into fibre optic cables or optical data in/out connectors. Contact Motorola if in doubt to ensure that safety features are maintained. or removing or replacing equipment. Human Exposure to Electromagnetic Fields High Frequency (10 kHz to 300 GHz). Where provided. Lifting equipment When dismantling heavy assemblies. 68P02901W23-P 23 Feb 2004 15 GMR-01 . IEEE Standard for Safety Levels with Respect to Human Exposure to Radio Frequency Electromagnetic Fields. a competent responsible person must ensure that adequate lifting facilities are available. lifting frames must be used for these operations. the competent responsible person must ensure that adequate lifting facilities are available.1-1991. 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. Any boards containing defective lithium batteries must be returned to Motorola for repair.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. 16 GMR-01 68P02901W23-P 23 Feb 2004 . Contact your local Motorola office for how to return defective lithium batteries. may burst and ignite. Defective lithium batteries must not be removed or replaced. Static discharge Motorola equipment contains CMOS devices. These must be observed by all personnel at all times when working with the equipment. painted over or obscured in any way. Specific cautions Cautions particularly applicable to the equipment are positioned within the text of this manual. These metal oxide semiconductor (MOS) devices are susceptible to damage from electrostatic charge. 68P02901W23-P 23 Feb 2004 17 GMR-01 . on the illustrations and on the equipment. Failure to comply with these cautions or with specific cautions elsewhere in the Motorola manuals may result in damage to the equipment. Fibre optics Fibre optic cables must not be bent in a radius of less than 30 mm. Caution labels must not be removed. Motorola assumes no liability for the customer’s failure to comply with these requirements. See the section Devices sensitive to static in the preface of this manual for further information. as must any other cautions given in text. Caution labels Personnel working with or operating Motorola equipment must comply with any caution labels fitted to the equipment.General cautions General cautions Observe the following cautions during operation. installation and maintenance of the equipment described in the Motorola manuals. MOS devices are normally less susceptible to electrostatic damage. It may be necessary to replace the conductive foam by a piece of wire to enable the device to be fitted. 18 GMR-01 68P02901W23-P 23 Feb 2004 . wire strapping. When mounted onto printed circuit boards (PCBs). Special handling techniques In the event of one of these devices having to be replaced. preferably by their edges and not by their tracks and pins. Wipe insulated plastic work surfaces with an anti-static cloth before starting the operation. • Take care when removing components connected to electrostatic sensitive devices. or by inserting the leads into conductive plastic foam. • If possible work on an earthed metal surface or anti-static mat. • Leave the short circuit on the leads until the last moment. by pushing the hands into high insulation packing material or by use of unearthed soldering irons. by metal foil eyelets.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. they should be transferred directly from their packing to the equipment (or the other way around) and never left exposed on the workbench. However PCBs should be handled with care. for example. MOS devices are normally despatched from the manufacturers with the leads short circuited together. 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. Such a charge applied to the leads of the device could cause irreparable damage. • All metal tools should be used and when not in use they should be placed on an earthed surface. by friction. • Do not wear outer clothing made of nylon or similar man made material. Provided the leads are short circuited it is safe to handle the device. A cotton overall is preferable. These components may be providing protection to the device. These charges can be built up on nylon overalls. The CD-ROM does not include Release Notes or documentation supporting specialist products such as MARS or COP. install and maintain the Motorola equipment. Ordering manuals and CD-ROMs Use the Motorola 68Pxxxxxxxx order (catalogue) number to order hard copy manuals or CD-ROMs. CD-ROM produced in support of a major system software release. together with current versions of appropriate hardware manuals.com/index. Each CD-ROM includes all manuals related to a specified main GSM. though it will not be updated in line with subsequent point releases. GPRS or UMTS software release. • Electronic. as fully navigable PDF files on: The Motorola customer support web site at: (https://mynetworksupport. and has additional navigation facilities.asp). Manuals for the GSM. 68P02901W23-P 23 Feb 2004 19 GMR-01 . A snapshot copy of on-line documentation is also included. All orders must be placed with your Motorola Local Office or Representative. GPRS and UMTS products are available on the following media: • Printed hard copy.motorola.Motorola manual set Motorola manual set The Motorola manual sets provide the information needed to operate. Complete replacement content or loose leaf pages with amendment list. GMR instructions When a GMR is inserted in this manual. Retain the instruction sheet that accompanies each GMR and insert it in a suitable place in this manual for future reference. the amendment record below is completed to record the GMR. • CD-ROM . Remove and replace pages in this manual.GMR amendment GMR amendment Changes to a manual that occur after the printing date are incorporated into the manual using General Manual Revisions (GMRs). A GMR has the same identity as the target manual. GMRs are issued to correct Motorola manuals as and when required. as detailed on the GMR instruction sheet.Updated periodically as required. 20 GMR-01 68P02901W23-P 23 Feb 2004 . GMR availability GMRs are published as follows: • Printed hard copy .Updated at the same time as hard copies. Each GMR is identified by a number in a sequence that starts at 01 for each manual at each issue. • Motorola service web . GMR amendment GMR amendment record Record the insertion of GMRs in this manual in the following table: GMR number 01 Incorporated by (signature) Incorporated (this GMR) Date 23 Feb 2004 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 68P02901W23-P 23 Feb 2004 21 GMR-01 . 22 GMR-01 68P02901W23-P 23 Feb 2004 .GMR amendment This page intentionally left blank. The following topics are contained in this chapter: 68P02901W23-P 23 Feb 2004 • Overview of BSS MMI functions. commands and parameters including SYSGEN modes of operation. • List of commands that cause a device to cycle and must be used with caution. • Guidelines on entering MMI commands and use of the correct syntax. including data array location. alarm thresholds and EAS alarm table. • List of parameters that cause a device to cycle and must be used with caution. • Description of the two types of GSM cell ID format. • Description of command/database parameter classification.Chapter 1 Introduction to commands This chapter provides an introduction to the Base Station System (BSS) Man Machine Interface (MMI) functions. • Description of SYSGEN modes of working. • Description of command/database access security levels. bin numbers. • Lists of MMI command availability by location and by SYSGEN mode. • Descriptions of indices for devices. 1-1 GMR-01 . MMI commands are responsible for these activities: • BSS Initialization Process (IP). • LAN connection to a personal computer (PC). the existing code is damaged.BSS MMI functions Chapter 1: Introduction to commands BSS MMI functions In the GSM system. BSS Initialization Process The Initialization Process (IP) may load code from three sources: • GPROC. code is loaded on the BSS. • Security management. • Operation and Maintenance Centre (OMC-R). or a new version of code exists. 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). • Call Processing maintenance. • System change control or Configuration Management (CM). Initialization occurs when the BSS is reset. 1-2 GMR-01 68P02901W23-P 23 Feb 2004 . Upon initialization. • Miscellaneous. such as controlling system access. • Central statistics processing. Man-Machine Interface (MMI) commands are part of the Network Management function. • Maintenance or Fault Management (FM). Alarms are one example of this type of control. access to a security level is denied. • Modify the CM database. Fault Management Fault Management commands are used to display and modify the administrative state of devices or functions. 1-3 GMR-01 . These ensure that only authorized persons have access and establish a system/command permission level commensurate with the person. • Display information from the CM database. Early interaction is only permitted with CM process commands. A password may be changed in accordance with the parameters shown in the chg_level and chg_password command descriptions. Configuration Management Configuration Management commands are used to: 68P02901W23-P 23 Feb 2004 • Configure the Base Station System. • Populate the database during SYSGEN.Technical Description BSS Command Reference BSS MMI functions Early MMI interaction The MMI prompt is presented before the initialization process is complete. Security management Passwords are required to access the system. If an incorrect password is entered. • Perform miscellaneous procedures. • Display/Modify statistics for devices or cells. either by call rate. • Clear database contents. • Modify statistics time interval for system. Central statistics processing Statistics commands are used to: • Enable/Disable statistics. ROM checksum. 1-4 GMR-01 68P02901W23-P 23 Feb 2004 . These commands are used to: • Begin/End a SYSGEN session. via random trace. Miscellaneous commands Miscellaneous commands are those that do not conveniently fit into the categories already outlined. • Display/Modify time function (time-stamp). • Monitor active (enabled) statistics for system. and so on. The total data resulting from the call progress events can be collected for later analysis. or SCCP connection number. such as displaying the DTE link address. • Display version of a software load.BSS MMI functions Chapter 1: Introduction to commands Call processing Call processing commands are used to trace the progress of a specified call. • Reset the entire BSS. • Report statistics data. 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. 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. This security level also permits the operator to change passwords for both Level 1 and Level 2 users. Each command in the system is assigned a security level. including the ability to change the system database. Level 1 This level permits the display of system parameters. 68P02901W23-P 23 Feb 2004 1-5 GMR-01 . Access to each level is controlled using passwords. 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. Access is restricted primarily to system monitoring commands. Level 2 This level permits access to all system commands. Refer to the command description for a specific command security level. Type A commands and parameters No special user action is required to enter a Type A command or change a Type A database parameter. 1-6 GMR-01 68P02901W23-P 23 Feb 2004 . Specific required actions are listed in the Operator actions section of each command and database parameter description.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 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. 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-P 23 Feb 2004 1-7 GMR-01 .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. 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 GMR-01 68P02901W23-P 23 Feb 2004 .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. this is made clear in the text. Where there are exceptions to this rule. 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). • Command names are case sensitive and may not be entered as mixed upper and lower case characters in a command string. • An underscore character _ must be used between command keywords. Command syntax The following guidelines must be followed when entering MMI commands. For example: [<start_time_hour>] or [dri].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). For example: dri • A character sequence enclosed in [ ] indicates that the parameter is optional. Example BSS PROMPT-->add_rtf_path MMI command 3 2 1 1 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: 68P02901W23-P 23 Feb 2004 is: bsic element_name 1 value 0 location 5 4 3 2 1 61986 34944 cell_desc 1-9 GMR-01 . • A character sequence in bold serif type such as example represents a mandatory parameter that must be entered as is. For example:<start_time_hour> is entered as an hour between00 and23 . • A space character is used between parameters as a command separator. for example add_cell. Ambiguous command response If the command name is entered incorrectly. type: 0ffh 1-10 GMR-01 68P02901W23-P 23 Feb 2004 . For example. and the following message displays: COMMAND REJECTED: No response to prompt. the command or response is rejected. • Type an h at the end of the value. 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. the hex equivalent for 255 is ff. the system displays a message stating that the entered command was ambiguous and lists commands with similar command names. To specify this hex value.Entering MMI commands Chapter 1: Introduction to commands System response COMMAND ACCEPTED Timeouts If a response is not entered within 60 seconds. To specify a hex value: • Lead the value with a 0 (zero). 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. Table 1-1 MMI command availability by location Command MMI ROM Locations Allowed BSC BTS RXCDR add_cell X add_conn 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 chg_cell_element X chg_cell_id X chg_csfp X X chg_dte X X chg_eas_alarm X X X X chg_element X (1) chg_hop_params X chg_ksw_config X chg_level X X chg_password X chg_rtf_freq X chg_severity X chg_smscb_msg X 68P02901W23-P 23 Feb 2004 X X X X X X X 1-11 GMR-01 . Command availability by location Table 1-1 indicates the sites at which commands can be entered. not the location string availability for command execution. MMI command availability Chapter 1: Introduction to commands Table 1-1 MMI command availability by location (Continued) Command MMI ROM Locations Allowed BSC BTS RXCDR chg_stat_prop X X chg_throttle X X chg_time X chg_ts_usage X X X X X chg_x25config 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 del_cell X del_conn X X X X X del_channel del_neighbor X del_nsvc X del_rtf_path X del_smscb_msg X device_audit X X disp_a5_alg_pr X X disp_act_alarm 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 disp_csfp X X X disp_csfp_status X X X disp_dte X disp_element X (1) disp_enable_stat 1-12 GMR-01 X X X X X X X X X X 68P02901W23-P 23 Feb 2004 . Technical Description BSS Command Reference Table 1-1 MMI command availability MMI command availability by location (Continued) Command MMI ROM Locations Allowed 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 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 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 X X X X equip X X freq_types_allowed X disp_x25config X (2) X gclk_cal_mode help X X X history X X X 68P02901W23-P 23 Feb 2004 1-13 GMR-01 . MMI command availability Chapter 1: Introduction to commands Table 1-1 MMI command availability by location (Continued) Command MMI ROM Locations Allowed 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 page X X X query_audits X X X reassign 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 state X X X status_mode X X X store_cal_data X sysgen_mode 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 unconfigure_csfp X X unequip X X 1-14 GMR-01 X X X X X 68P02901W23-P 23 Feb 2004 . Technical Description BSS Command Reference Table 1-1 MMI command availability MMI command availability by location (Continued) Command Locations Allowed MMI ROM unlock_device BSC BTS RXCDR X X X 1. Also note that these commands do not accept the location or cell parameters used in the RAM version of these commands. These commands are not available for MMI ROM processes running on TCU boards. Command availability by SYSGEN mode Table 1-2 shows the availability of commands in the various SYSGEN modes. These commands are only available for MMI ROM processes running on GPROC boards. 2. Table 1-2 MMI command availability by SYSGEN mode Command SYSGEN MODE ON SYSGEN MODE OFF 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 X alarm_mode 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 68P02901W23-P 23 Feb 2004 X X X 1-15 GMR-01 . MMI command availability Chapter 1: Introduction to commands Table 1-2 MMI command availability by SYSGEN mode (Continued) Command SYSGEN MODE ON SYSGEN MODE OFF MMI READY CM READY SITE READY 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 X clear_cal_data X clear_database X clear_gclk_avgs configure_csfp X connection_code X X copy_cell X X copy_path X X X del_act_alarm 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 X disp_a5_alg_pr X X disp_act_alarm X disp_bss X X disp_conn X X X disp_cal_data disp_cbch_state X disp_cell X X X X X disp_cell_status 1-16 GMR-01 68P02901W23-P 23 Feb 2004 . Technical Description BSS Command Reference Table 1-2 MMI command availability MMI command availability by SYSGEN mode (Continued) Command disp_csfp SYSGEN MODE ON SYSGEN MODE OFF MMI READY X CM READY SITE READY X X X disp_csfp_status 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 X disp_interval disp_level X X X disp_link X X X X X disp_link_usage 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 X disp_stats disp_stat_prop X X X disp_throttle X X X disp_time X X X X disp_trace_call disp_traffic X X X disp_version 68P02901W23-P 23 Feb 2004 1-17 GMR-01 . MMI command availability Chapter 1: Introduction to commands Table 1-2 MMI command availability by SYSGEN mode (Continued) Command SYSGEN MODE ON SYSGEN MODE OFF MMI READY CM READY SITE READY X X disp_x25config X equip X X freq_types_allowed X X X gclk_cal_mode help X X X X history X X X X ins_device X lock_device X man 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 X X query_audits X reassign X reattempt_pl X reset_device X X reset_site 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 sysgen_mode X time_stamp X 1-18 GMR-01 X X X X X X 68P02901W23-P 23 Feb 2004 . Technical Description BSS Command Reference Table 1-2 MMI command availability MMI command availability by SYSGEN mode (Continued) Command SYSGEN MODE ON SYSGEN MODE OFF MMI READY CM READY X trace_call trace_connection X X trace_stop X unalias X unconfigure_csfp X unequip X X X X X X unlock_device 68P02901W23-P 23 Feb 2004 SITE READY 1-19 GMR-01 . 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.GSM cell ID format Chapter 1: Introduction to commands GSM cell ID format Cell IDs are required parameter entries for many commands. • CI . 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 GMR-01 68P02901W23-P 23 Feb 2004 . seven elements or four elements.Cell Identity.Mobile Country Code. depending on the command. Input format Two types of GSM cell ID input format. can be used.Location Area Code.Mobile Network Code. The format is set with the mmi_cell_id_format parameter. • LAC . The GSM cell ID format consists of four fields: • MCC . • MNC . Four-element format The system uses the four-element format when the mmi_cell_id_format parameter = 1. the MNC must be entered as 001. EGSM and DCS 1800 systems. it may be omitted from the input. It may be used for PGSM. the system interprets the entry as MNC=01. 68P02901W23-P 23 Feb 2004 1-21 GMR-01 .Technical Description BSS Command Reference Where: GSM cell ID format 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. EGSM. If the MNC is entered as 01 or 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. if the MNC = 001 and the third MNC digit is required. DCS 1800 and PCS 1900 systems. which would be incorrect. For example. If the first and/or second digit of the MCC is a zero. all three MNC digits must be entered. 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. It is valid for PGSM. 1-22 GMR-01 68P02901W23-P 23 Feb 2004 . 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.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 command string disp_element sap_start_time. Device indices Device indices are used with the disp_element command for displaying information associated with the System Audit Process (SAP). Data array location An index is used to identify the location of information in a data array. Table 1-3 Device Indices Device type Index KSW 0 KSW (internal loopback tests) 1 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. Table 1-3 lists the device types and associated indices.12 0 displays the audit start time for BSPs (index 12) at location 0.Technical Description BSS Command Reference Indices Indices Indices are used to display information or locate information in a data array. 68P02901W23-P 23 Feb 2004 1-23 GMR-01 . 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....0 1 cell=0 0 1 0 1 1 1 Two index numbers Some statistical elements require two index numbers. 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.0 bin_num index The following example shows the command string that would be used to display the contents of a bin. . the command string disp_element sap_audit_type. the command string disp_element invalid_frames_rx.1 0 cell_number=2 6 2 0 2 2868 3100 rxlev_dl_ho = alg_num: 1 alg_data: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 8 6 0 0 0 0 0 0 0 0 0 0 0 0 0 Thresholds Gauge and some counter statistics may be assigned thresholds. 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. column 1 of a multi-row data array. The severity of the alarm associated with a statistical parameter may be displayed using the disp_element command using an index value of 1. . 31] 31] 31] 31] The following example shows the command string that would be used to assign or change the value of the rxlev_ul_ho parameter. When a command uses bin numbers to specify the row in a data array. The following represents an array with four bins with 32 elements in each bin: bin bin bin bin 0 1 2 3 [0 [0 [0 [0 1 1 1 1 2 2 2 2 .1 0 displays the severity of the alarm associated with the invalid_frames_rx statistical parameter invalid_frames_rx = 2 1-24 GMR-01 68P02901W23-P 23 Feb 2004 ... .0.1 0 displays the value of the sap_audit_type parameter located in row 0. For example. 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). The second index number is the position of the element in the row. An alarm is sent to the OMC-R when the threshold is exceeded. The first index number is the row number.. Bins A single row of a data array may be referred to as a bin. in an interfer_bands parameter: disp_element interfer_bands... the index number specifies the position of the data element in the bin. For example. Both the text and severity level are assigned when the EAS alarm table is initialized using the chg_eas_alarm command. 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. The severity level may be modified independently using the chg_element eas_severity command. After initialization.Technical Description BSS Command Reference Indices Table 1-4 lists the alarm severities. Each pair includes a severity level and up to 24 text characters. 68P02901W23-P 23 Feb 2004 1-25 GMR-01 . the text and severity level can be displayed independently using the disp_element eas_alarm or the disp_element eas_severity commands respectively. *******VERIFYING DATABASE BEFORE COMPLETING SYSGEN******* Frequency hopping verification in progress. the system prompts the user to reinitialize the site. Do NOT enter the sysgen_mode on or the sysgen_mode off commands at the OMC-R. 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. 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. SITE 0 Verification. After the system initializes. If the system is in the SYSGEN OFF mode and the sysgen_mode off command is entered. 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. COMMAND ACCEPTED. any changes made to the database are checked. it is in the SYSGEN OFF mode. If the system is in the SYSGEN OFF mode and the sysgen_mode on command is entered. The sysgen_mode off command places the system in the SYSGEN OFF mode. changes may be entered into the database without being checked until the system is returned to its normal mode of operation. If the system is in the SYSGEN ON mode and the sysgen_mode off command is entered.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. the command is rejected and the following message displays: 1-26 GMR-01 68P02901W23-P 23 Feb 2004 . DB Verification passed. If the changes to be made while the BSC is in SYSGEN ON mode are to be retained. This is done at the OMC-R. The initial SYSGEN mode is used to load the CM database using a script. 68P02901W23-P 23 Feb 2004 1-27 GMR-01 . Initial SYSGEN mode The initial SYSGEN mode occurs when the system is placed in the SYSGEN ON mode without a Configuration Management (CM) database. Database changes in SYSGEN ON mode In a network the BSC connects to an OMC-R. upload the modified database from the BSC to the OMC-R. Any changes made while the BSC was in the SYSGEN ON mode are overwritten by the download from the OMC-R.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. the OMC-R automatically downloads a copy of the database in its memory to the BSC. When a difference is detected between the database load in the OMC-R and the BSC. 6 After the system has returned to service. 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. 5 Enter the sysgen_mode off command at the BSC. the system resets. 7 Re-enable downloads for network elements at the OMC-R. 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. 2 Enter the sysgen_mode on command at the BSC 3 Enter the reset_site 0 command. 4 After the system has reset. A copy of the BSC database is stored at the OMC-R. If the timer expires. 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. For example. If activity is detected before the timer expires. if the script to be loaded is for an RXCDR. The timer is started when no activity is detected from the TTY terminal. 1-28 GMR-01 68P02901W23-P 23 Feb 2004 . SYSGEN safety features Automatic GPROC addition If the initial SYSGEN mode is entered from a GPROC which is not included in the script. the script has to be corrected and reloaded before the system is able to return to its normal operating state. the GPROC is reset with a Global Kill SWFM. the system does not return to the SYSGEN OFF mode. It is recommended that the initial SYSGEN mode be entered from the same type of system for which the database is being loaded. Safety timer While the system is in the SYSGEN ON mode. After the database is loaded using a script.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. This permits large amounts of information to be loaded efficiently onto the system. a GPROC is added automatically to the slot from which the initial SYSGEN mode was entered. a message includes a textual description that the timer expired. If errors are detected. When this occurs. the initial SYSGEN mode should be entered from the master slot of a BSC (0115h). A script is loaded in the initial SYSGEN mode. a timer is used to insure that a GPROC cannot be left in the SYSGEN ON mode indefinitely. the system must be returned to the SYSGEN OFF mode to verify the script contents. Within the SWFM. the timer is reset to its initial value and restarted. • Call Processing. 68P02901W23-P 23 Feb 2004 2-1 GMR-01 . 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).Chapter 2 Device/function related commands Device/function commands are commands that can be entered at the MMI to create. Statistical commands are described in Chapter 4: Statistics commands. display. • System Change Control (Configuration Management). delete devices and functions within the BSS. • Miscellaneous. modify. Input parameters . and in the contents and the index of this manual.whether or not the command is supported at the OMC-R GUI. 2-2 GMR-01 68P02901W23-P 23 Feb 2004 . this field is not shown.the actual command reference which appears at the head of the page. Command type .includes the input command: Syntax .conditions that must be met or exist for the command to be accepted. Examples . Related commands . Format .provides various examples of command input and the expected response. specific responses.descriptions of each command input parameter. If no actions are required. Operator actions .includes where appropriate: Related information . Supported by OMC-R GUI . Prerequisites .whether type A (no operator actions) or type B.actions required by the operator for type B commands.the access security level for the command.any relevant information. such as command prompts.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 structure of the command and input parameter string. References . Description .any commands that are related.provides a description of the MMI command function and includes: Security level . 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 {4354} Generic Processor 3 GSL GPRS Signalling Link (GPRS) KSW Kilo-port Switch LAN Local Area Network 68P02901W23-P 23 Feb 2004 2-3 GMR-01 .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. disp_equipment Valid for BSC and InCell BTS 2-4 GMR-01 68P02901W23-P 23 Feb 2004 . state. reset_device Cause a hard reset of the device. reset_device Cause a hard reset of the device. unequip.048 Mbit/s link on an MSI board MPRT 1. disp_equipment.048 Mbit/s Port MSI 1. device_audit disp_equipment includes HVN lock_device. state.Device related commands Chapter 2: Device/function related commands Table 2-1 Device literals and descriptions (Continued) Literal Description MMS 1.544/2. device_audit disp_equipment includes Hardware Version Number (HVN) lock_device. CAB equip. disp_equipment CAB(PCU) state Valid for GPRS only CAGE equip.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. unequip. equip. ins_device. ins_device. disp_equipment. unlock_device. state.544/2. state. unlock_device. Table 2-2 Device and command relationship Device BSP BTP Commands Affected Notes equip.544/2. unlock_device. lock_device. unequip. ins_device. lock_device. reset_device. unlock_device. disp_equipment. swap_devices CSFP state. unequip. reset_device Valid for GPRS only GCLK equip. ins_device. disp_equipment.Technical Description BSS Command Reference Device related commands Table 2-2 Device and command relationship (Continued) Device Commands Affected Notes CAGE (PCU) equip. device_audit. unlock_device. unequip. disp_equipment. reset_device Valid for BSC only CBUS state Valid for BSC and InCell BTS CELL state CIC equip. unequip. reset_device. reset_device. state. state. unequip. unlock_device. unequip. lock_device. unequip. lock_device. reset_device. reset_device GBL equip. state. unequip. ins_device. disp_equipment Valid for BSC only EAS equip. unlock_device. unequip. unequip. unlock_device. swap_devices. device_audit Valid for BSC and InCell BTS. state. lock_device. shutdown_device disp_equipment includes HVN DYNET equip Valid for BSC and InCell BTS unequip. device_audit Valid for BSC and InCell BTS disp_equipment includes HVN DPROC equip. disp_equipment. device_audit Valid for GPRS only DRI equip. ins_device. state. state. disp_equipment. lock_device. reset_device. lock_device. reset_device Valid for GPRS only 68P02901W23-P 23 Feb 2004 2-5 GMR-01 . unlock_device. reset_device. disp_equipment. unlock_device. unlock_device. lock_device. disp_equipment. ins_device. ins_device. lock_device. disp_equipment. lock_device. disp_equipment includes HVN GDS equip. ins_device. cage_audit Valid for GPRS only CBL equip. disp_equipment. state. state. disp_equipment Valid for BSC only equip. ins_device. unlock_device. lock_device. unequip. unlock_device. device_audit. disp_equipment. state. shutdown_device COMB equip. ins_device. state. disp_equipment. ins_device. state. ins_device. reset_device Valid for BSC and InCell BTS DHP equip. disp_equipment. equip. disp_equipment includes HVN lock_device. unequip. lock_device. ins_device Valid for BSC and InCell BTS. unlock_device. state. unlock_device. unequip. ins_device. 2-6 GMR-01 68P02901W23-P 23 Feb 2004 . reset_device Valid for BSC and InCell BTS. LAN state. disp_equipment includes HVN lock_device. device_audit disp_equipment includes HVN reset_device Causes a hard reset of the device. device_audit Valid for BSC and InCell BTS. ins_device. device_audit. disp_equipment. disp_equipment. swap_devices Valid for BSC and InCell BTS MMS lock_device. disp_equipment. reset_device Valid for BSC and InCell BTS. disp_equipment. unequip. disp_equipment includes HVN lock_device. reset_device GPRS only KSW equip. state. unequip. Cause a hard reset of the device. state. reset_device Valid for BSC and InCell BTS. reset_device Valid for BSC and InCell BTS. state. lock_device. reset_device MPRT shutdown_device Valid for BSC only MSI equip. GPROC3{4354} equip. unlock_device. unlock_device. disp_equipment. unlock_device. ins_device. Cause a hard reset of the device. Cause a hard reset of the device. device_audit Valid for BSC and InCell BTS. unlock_device. state. disp_equipment. unequip. ins_device. ins_device.Device related commands Table 2-2 Chapter 2: Device/function related commands Device and command relationship (Continued) Device GPROC GPROC2 Commands Affected Notes equip. state. device_audit Valid for BSC and InCell BTS. state. Cause a hard reset of the device. GSL equip. disp_equipment includes HVN lock_device. unlock_device. ins_device. unequip. state. lock_device.Technical Description BSS Command Reference Device related commands Table 2-2 Device and command relationship (Continued) Device Commands Affected Notes MTL equip. reset_device PCU equip. device_audit Valid for BSC and InCell BTS XBL equip. state. lock_device. swap_devices. lock_device. reset_device Valid for BSC only PBUS state Valid for BSC and InCell BTS PCHN state. ins_device. unequip Valid for GPRS only RSL lock_device. unlock_device. unlock_device. state. lock_device. disp_equipment. shutdown_device Valid for BSC only OML equip. disp_equipment. ins_device. unequip. ins_device. state. unequip Valid for BSC only SBUS state Valid for BSC and InCell BTS SITE equip. disp_equipment. unlock_device. unlock_device. ins_device. unequip. reset_device Valid for BSC only PATH equip. ins_device. device_audit. unlock_device. disp_equipment. unlock_device. reset_device site_audit Valid for GPRS only PSP equip. ins_device. unequip. disp_equipment. ins_device. unequip. disp_equipment. disp_equipment. unlock_device. reset_device. state. unequip. reset_device Valid for BSC only 68P02901W23-P 23 Feb 2004 2-7 GMR-01 . state. ins_device. lock_device. state. lock_device. lock_device. unlock_device. reset_device RSL equip. state. unequip. disp_equipment. reset_device Valid for BSC only TBUS state Valid for BSC and InCell BTS TDM state. Table 2-3 Device ID requirements Device Names/IDs Range ABSS Definition Associated Base Station Processor device ID 1 0 to 128 device ID 2 0 Serves as place holder device ID 3 0 Serves as place holder AXCDR Corresponds to the BSS network entity that this device represents Associated XCDR device ID 1 0 to 128 device ID 2 0 Serves as place holder device ID 3 0 Serves as place holder BCUP Corresponds to the RXCDR network entity that this device represents 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) device ID 3 0 BSP Serves as place holder Base Site Processor. BTS 2-8 GMR-01 68P02901W23-P 23 Feb 2004 . BSC device ID 1 0 or 1 device ID 2 0 Serves as place holder device ID 3 0 Serves as place holder BSS Identifies which BSP board is active and which is redundant (standby) (None at a BTS) Base Station System device ID 1 0 to 50 device ID 2 0 Serves as place holder device ID 3 0 Serves as place holder BTP Identifies BSS Base Transceiver Processor. However. For devices that have only one or two device identifiers. not all devices have three device IDs. Device ID requirements Table 2-3 lists and defines the device ID requirements. zero(s) must be entered for the remaining device identifier parameter(s) as place holders.Device identifiers Chapter 2: Device/function related commands Device identifiers A device is specified in the system by three identifiers. (None at an RXCDR) 2-9 GMR-01 . automatically equipped/unequipped.Technical Description BSS Command Reference Table 2-3 Device identifiers Device ID requirements (Continued) Device Names/IDs Range device ID 1 1 Identifies which BTP board is active and which is redundant (standby) (None at a BSC or RXCDR) device ID 2 0 Serves as place holder device ID 3 0 Serves as place holder CAB CABinet device ID 1 0 to 20 device ID 2 0 Serves as place holder device ID 3 0 Serves as place holder CAGE device ID 1 Identifies cabinet number CAGE 0 to Identifies the value at which the LANX card. BTS 0 to 5 {4471} Identifies a digital module shelf (cage number) in a specific cabinet. device ID 2 0 Serves as place holder device ID 3 0 Serves as place holder DHP device ID 1 68P02901W23-P 23 Feb 2004 Definition Digital radio Host Processor.not M-CellM-cell. 15{4471} device ID 2 0 Serves as place holder device ID 3 0 Serves as place holder CBL Cell Broadcast Link device ID 1 0 Optional entry (None at a BTS or RXCDR) device ID 2 0 Serves as place holder device ID 3 0 Serves as place holder CBUS Clock BUS device ID 1 0 to 15 Identifies the cage where a specific GCLK is located device ID 2 0 or 1 Identifies the GCLK device ID 3 0 COMB Serves as place holder COMBiner device ID 1 0 to 13 Identifies specific combiner cavities (13 active. dial is set. 13 standby) (None at an RXCDR) device ID 2 0 or 1 Identifies each individual processor in a combiner unit (of the two present within a redundant pair) device ID 3 0 CSFP Serves as place holder Code Storage Facility Processor device ID 1 10 CSFP identifier (Only at a BSC) . automatically equipped/unequipped.slot 5 1=B side GCLK (slot B controls) .not M-Cell M-Cell Gb Link (GPRS) device ID 1 0 to 11 device ID 2 0 Serves as place holder device ID 3 0 Serves as place holder GCLK device ID 1 Identifies a specific GBL link General CLocK 0 or 1 Identifies which GCLK board is active and which is redundant (standby). 0 device ID 2 0 Serves as place holder device ID 3 0 Serves as place holder GDS GPRS Data Stream (GPRS) 2-10 GMR-01 68P02901W23-P 23 Feb 2004 .slot 3 M-cell.Device identifiers Chapter 2: Device/function related commands Table 2-3 Device ID requirements (Continued) Device Names/IDs Range device ID 2 0 to 7 device ID 3 0 DPROC Definition Identifies which DHP board is active and which is redundant (standby) Serves as place holder Digital Processor (GPRS) device ID 1 1 to 6 or 11 to 16 device ID 2 0 Serves as place holder device ID 3 0 Serves as place holder DRI device ID 1 Identifies a specific DPROC Board Digital Radio Interface 0 to 5 Identifies a user-defined DRI group within a site. (None at an RXCDR) {4471} device ID 2 0 to 11 {4471} device ID 3 0 DYNET device ID 1 Identifies a specific DRI board Serves as place holder Dynamic Network of BTSs 0 to 19 device ID 2 0 to 2 device ID 3 0 EAS Identifies the DYNET group (None at a BTS or RXCDR) The unique device within the DYNET group Serves as place holder External Alarm System device ID 1 0 to 7 0 to 15 device ID 2 0 Serves as place holder device ID 3 0 Serves as place holder GBL Identifies a specific PIX card at a site . 0=A side GCLK (slot A controls) . The DRIs which belong to this group must be allocated to the same cell and must be connected to the same antenna. device ID 2 0 or 1 Identifies which KSW board (highway. The E1/T1 Mbit/s line on a Multiple Serial Interface board 9 3 1 0 68P02901W23-P 23 Feb 2004 Definition Matches the first id of the host MSI with which it is associated (BSC or RXCDR) BTS only: not M-Cell BTS only: M-Cell6 BTS only: M-Cell2 BTS only: M-Cellmicro Identifies a specific MMS Serves as place holder Multiple Serial Interface board 2-11 GMR-01 . (0 is slot 27. device used for functions device ID 1 0 to 111 device ID 2 0 Serves as place holder device ID 3 0 Serves as place holder GSL Identifies a specific GPROC board GPRS Signalling Link (GPRS) device ID 1 0 to 11 device ID 2 0 Serves as place holder device ID 3 0 Serves as place holder KSW Identifies a specific GPRS signalling link Kiloport SWitch device ID 1 0 to 3 Identifies a section (timeslot) of TDM highway. A side or B side) is active and which is redundant (standby). 1 is slot 1) device ID 3 0 LAN Serves as place holder Local Area Network device ID 1 0 or 1 device ID 2 0 Serves as place holder device ID 3 0 Serves as place holder MMS device ID 1 0 to 55 device ID 2 0 or 1 device ID 3 0 MSI Identifies which LAN board (A side or B side) is active and which is redundant (standby).Technical Description BSS Command Reference Table 2-3 Device identifiers Device ID requirements (Continued) Device Names/IDs Range device ID 1 0 to 37 device ID 2 0 Serves as place holder device ID 3 0 Serves as place holder GPROC Identifies a specific GPRS data stream Generic PROCessor. M-Cell not applicable. Device identifiers Chapter 2: Device/function related commands Table 2-3 Device ID requirements (Continued) Device Names/IDs Range device ID 1 0 to 55 0 to 71 9 3 1 0 Definition Identifies a specific MSI board: BSC RXCDR BTS only: not M-Cell BTS only: M-Cell6 BTS only: M-Cell2 BTS only: M-Cellmicro device ID 2 0 Serves as place holder device ID 3 0 Serves as place holder MTL Message Transfer Link device ID 1 0 to 15 device ID 2 0 Serves as place holder device ID 3 0 Serves as place holder OML Identifies a specific MTP link (per ITU-TSS spec.) Operations and Maintenance Link device ID 1 0 to 3 device ID 2 0 Serves as place holder device ID 3 0 Serves as place holder Identifies a specific connection (link) between the BSC and the OMC-R (BSC or RXCDR) PATH device ID 1 1 to 100 device ID 2 0 to 9 device ID 3 0 PBUS Identifies the terminating site (BSC only) Identifies a unique PATH ID Serves as place holder 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) device ID 3 0 RSL Serves as place holder Radio System Link device ID 1 1 to 100 device ID 2 0 to 7 5 1 device ID 3 0 RTF Identifies the site to which the RSL is connecting (BSC only) Identifies a specific link set (not M-Cell) M-Cell2 and M-Cell6 M-Cellmicro Serves as place holder Receive Transmit Function device ID 1 0 to 5 {4471} Identifies the cell group device ID 2 0 to 11 Identifies a unique function within the cell group 2-12 GMR-01 68P02901W23-P 23 Feb 2004 . Technical Description BSS Command Reference Table 2-3 Device identifiers Device ID requirements (Continued) Device Names/IDs Range device ID 3 0 RXCDR Serves as place holder Remote transcoder device ID 1 0 to 128 device ID 2 0 Serves as place holder device ID 3 0 Serves as place holder SITE BTS SITE device ID 1 0 to 100 device ID 2 0 Serves as place holder device ID 3 0 Serves as place holder SBUS Identifies the site for which commands are being executed Serial BUS device ID 1 0 to 15 Identifies the cage at that location device ID 2 0 or 1 Identifies which SBUS ( A side or B side) is active and which is redundant (standby) device ID 3 0 TBUS Serves as place holder TDM BUS device ID 1 0 to 15 Identifies the cage at that location device ID 2 0 or 1 Identifies which TBUS ( A side or B side) is active and which is redundant (standby) TDM Time Division Multiplex Highway device ID 1 0 or 1 device ID 2 0 Serves as place holder device ID 3 0 Serves as place holder XBL 68P02901W23-P 23 Feb 2004 Definition Identifies which side ( A side or B side) of the TDM highway is active and which is redundant (standby) RXCDR to BSC Fault Management Link device ID 1 0 to 9 Identifies a specific connection (link) between the RXCDR and the BSC device ID 2 0 Serves as place holder device ID 3 0 Serves as place holder 2-13 GMR-01 . • The first column gives the function literal. BSC X X X X OMF Operation and Maintenance Function. Table 2-4 Literal Function related commands Device name / description Commands unequip equip state disp_equipment DYnamic NETwork of BTSs X X X X LCF Link Control Function. • The remaining columns show the commands that are supported for each function. BSC X X X X RTF Receive Transmit Function X X X X RXF Receive Function X TXF Transmit Function X DYNET 2-14 GMR-01 68P02901W23-P 23 Feb 2004 .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 second column gives the function name. Function ID requirements Table 2-5 lists and defines the Function ID requirements. not all functions have three device IDs. Table 2-5 Function ID requirements Device Names / IDs Range BTF Definition Base Transceiver Function (BTS only) function ID 1 0 to 2 1 Identifies maximum number of DRIs supported by this BTF (not M-Cell) M-Cell only function ID 2 0 Serves as a place holder function ID 3 0 Serves as a place holder OMF Operation and Maintenance Function (BSC and RXCDR only) function ID 1 None Identifies the OMF (BSC or BSS sites where BSC type is 2) function ID 2 0 Serves as a place holder function ID 3 0 Serves as a place holder LCF Link Control Function (BSC only) function ID 1 0 to 24 Identifies specific control links to the MSC and/or the BTS function ID 2 0 Serves as a place holder function ID 3 0 Serves as a place holder RTF Receive Transmit Function (BSC and BTS only) function ID 1 0 to 29 {4471} Identifies the RTF group to which the RTF belongs function ID 2 0 to 24 Identifies a specific RTF function function ID 3 0 Serves as a place holder 68P02901W23-P 23 Feb 2004 2-15 GMR-01 . zero(s) must be entered for the remaining function identifier(s) as place holders. however.Technical Description BSS Command Reference Function identifiers Function identifiers A function is identified in the system by up to three identifiers. For functions that have only one or two device identifiers. 255 (slot = N/A) {4471} MSI type = 0 slot = 6 to 10 or MSI type = 1. 255 slot = 6 to 24 GPROC MSI 2-16 GMR-01 68P02901W23-P 23 Feb 2004 .15 N/A DRI 7. 17 N/A 7. 13. 17 N/A EAS 15 to 18 (daughter slots) 15 to 18 (daughter slots) 15 to 18 (daughter slots) {4471} 15 to 18 (daughter slots) GCLK device_id1 = 0 slot = 5 or device_id1 = 1 slot = 3 device_id = 0 slot = 5 or device_id1 = 1 slot = 3 device_id1 = 0 slot = 5 or device_id1 = 1 slot = 3 device_id1 = 0 slot = 5 or device_id1 = 1 slot = 3 18 to 25 cage 0 to 13 18 to 25 cage 0 to 13 18 to 25 cage 2 to 15 25 or 26 cage 0 to 13 6 to 17 6 to 17 MSI type = 0 slot = 6 to 17 or MSI type = 1.Slots Chapter 2: Device/function related commands Slots Cage slots are allocated to devices dependent on the site function. 9. 15. 11. 11. 9. Table 2-6 Valid slots Device BSS BSC BTS RXCDR BSP cage = 0 slot = 20 or 24 or cage = 1 slot = 20 cage = 0 slot = 20 or 24 or cage = 1 slot = 20 N/A cage = 0 slot = 25 or 26 or cage = 1 slot = 25 BTP N/A N/A cage = 15 slot = 20 or 24 or cage = 14 slot = 20 N/A CSFP 18 to 25 cage 0 to 13 18 to 25 cage 0 to 13 18 to 25 cage 2 to 15 25 or 26 cage 0 to 13 DHP 18 to 25 cage 0 to 13 N/A 18 to 25 cage 2 . Valid slots table Table 2-6 lists the cage slots that are valid for the software supported devices. 15. 13. Supported Supported Note: MSIs of type NIU2 (that is. a MSI at a Horizon II site) are not supported by the equip/unequip commands. Table 2-7 Equip/Unequip command matrix Device/ Function Equip in SYSGEN Equip outside SYSGEN Unequip in SYSGEN Unequip outside 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 the site before entering the equip or unequip commands Unsupported Unsupported CAGE Supported Type B command: lock the site before entering the equip or unequip commands Unsupported Unsupported 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 MSI Supported Supported Unequip LCF is only supported if no sites exist on the LCF. 68P02901W23-P 23 Feb 2004 MTL Supported Unsupported Supported Supported OMF Supported Supported Supported Unsupported OML Supported Unsupported Supported Supported PATH Supported Supported Supported Supported 2-17 GMR-01 .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. equip/unequip command matrix Table 2-7 Chapter 2: Device/function related commands Equip/Unequip command matrix (Continued) Device/ Function Equip in SYSGEN Equip outside SYSGEN Unequip in SYSGEN Unequip outside SYSGEN RSL Supported Supported Supported Supported RTF Supported Supported Supported Supported SITE Supported Supported Supported Supported XBL Supported Supported Supported Supported 2-18 GMR-01 68P02901W23-P 23 Feb 2004 . 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 68P02901W23-P 23 Feb 2004 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 2-19 GMR-01 .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. 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 GMR-01 68P02901W23-P 23 Feb 2004 . Only one cell is permitted at an M-Cellcity. Format Syntax add_cell <gsm_cell_id> <location> [cell_name] 68P02901W23-P 23 Feb 2004 2-21 GMR-01 . After the command is entered. The add_cell command is invoked with the location and gsm_cell_id parameters. the default value is used by the system. Contact the OMC-R for help. The system rejects the add_cell command if it is entered for a site where six cells already exist. The prompted parameters are described in the Related Information at the end of this section. If the database parameter does not have a default value and no value or a value outside the parameter valid range is entered. This command will not work at a BTS site. This command can be abandoned at any time by entering done in response to any prompt. losing any previously entered parameters. the system rejects the add_cell command if it is entered for one of these sites. a series of prompts to define the cell are displayed. 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. where a cell already exists. Operator actions Reply to prompts as displayed. If a database parameter has a default value and a value outside of the parameter valid range is typed. If a database parameter has a default. Different sites can be equipped with various numbers of cells. Horizonmicro or Horizoncompact site. the default value can be entered by pressing the Return key. the command is abandoned. directly or in a script. {4471}Sites can have up to six cells. Enter this command at the BSC only.Technical Description BSS Command Reference add_cell add_cell Description The add_cell command adds a cell to the CM database. 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. EGSM. 2-22 GMR-01 68P02901W23-P 23 Feb 2004 .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. 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. If no value is entered for this parameter. 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. The cell name must be entered inside double quotation marks. The cell name may be from one to 31 alphanumeric characters. 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. 68P02901W23-P 23 Feb 2004 2-23 GMR-01 . 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. The dash character may be used as a separator. the current cell name displays. Example 2 In this example. location Specifies the location of the cell: 1 to 120 BTS cell_name The name to be assigned to the Cell ID.Technical Description BSS Command Reference add_cell A cell_name as defined by the cell_name command is not valid in add_cell commands. There is a time limit of 30 seconds in which to enter a responses to a prompt. If a parameter does not have a default value and the response to the prompt is not correct. If a parameter has a default value. the default value may be entered for the parameter by pressing the Return key. To abort the command manually. 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. the word even indicates that only even values are accepted.add_cell Chapter 2: Device/function related commands 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 Prompts are displayed for the parameters to define the cell. type done after any prompt. Similarly. Example 3 In this example. or the contents of the input column of add_cell command prompts table exactly as presented. where x is the parameter value. This example shows the four-parameter GSM cell ID format. add_cell 543 721 61986 34944 0 Where: is: 543 721 61986 34944 GSM cell ID 0 location System response Prompts are displayed for the parameters to define the cell. or if no response to the prompt is entered. Parameters are assigned by entering the parameter value only. For example. If a proper response is not entered within the time limit. References Related information Table 2-9 lists the prompts for the add_cell command. the command aborts and all values entered up to that point are lost. 2-24 GMR-01 68P02901W23-P 23 Feb 2004 . a PCS1900 cell with GSM Cell ID 5 4 3 7 2 1 61986 34944 is added to the CM database. 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. the system aborts the add_cell command and displays the system prompt. 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. Technical Description BSS Command Reference add_cell The copy_cell command description includes two alphabetical listings of which parameters are included for that command and which are not included. 2. 8 to 48 (if ccch_conf1) 8 Enter enable incoming handover: en_incom_ho=x 0 or 1 1 Enter intra cell handover allowed: intra_cell_handover_allowed=x 0 to 2 1 Enter inter cell handover allowed: inter_cell_handover_allowed=x 0 to 3 1 Enter number of preferred cells: number_of_preferred_cells=x 1 to 16 16 Enter handover margin default: ho_margin_def=x -63 to 63 8 Enter handover recognized period: handover_recognized_period=x 2 to 64 2 68P02901W23-P 23 Feb 2004 2-25 GMR-01 . 4. or 6 0 Enter blocks reserved for access grant: bs_ag_blks_res=x 0 to 7 0 Enter multiframes between transmissions of paging messages: bs_pa_mfrms=x 0 to 7 0 Enter extended paging active: extended_paging_active=x 0 or 1 0 Enter number of SDCCHs preferred: number_sdcchs_preferred=x 4 to 44 (if ccch_conf=1). None Enter wait indication parameters: wait_indication_parameters=x 0 to 255 5 Enter common control channel configuration: ccch_conf=x 0. 1. Table 2-9 add_cell command prompts Prompt Input Range Default Enter base station identity code: bsic=x 0 to 63 None Enter the Frequency Type: frequency_type=x 1 (pgsm) 2 (egsm) 4 (dcs1800) 8 (pcs1900) 16 (gsm850) Use numeric values or text string. add_cell Chapter 2: Device/function related commands Table 2-9 add_cell command prompts (Continued) Prompt Input Range Default Enter uplink rxqual handover allowed: ul_rxqual_ho_allowed=x 0 or 1 1 Enter downlink rxqual handover allowed: dl_rxqual_ho_allowed=x 0 or 1 1 Enter uplink rxlev handover allowed ul_rxlev_ho_allowed=x 0 or 1 1 Enter downlink rxlev handover allowed: dl_rxlev_ho_allowed=x 0 or 1 1 Enter alternate flag for SDCCH handover: sdcch_ho=x 0 or 1 1 Enter alternate SDCCH handover timer value: sdcch_timer_ho=x 1 to 31 1 Enter interference handover allowed: interfer_ho_allowed=x 0 or 1 1 Enter power handover allowed: pwr_handover_allowed=x 0 or 1 1 Enter MS distance allowed: ms_distance_allowed=x 0 or 1 0 Enter alternate flag for MS power control processing: mspwr_alg=x 0 or 1 0 Enter handover power level: handover_power_level=x 2 to 19 None Enter power control indicator for hopping through BCCH: pwrc=x 0 or 1 1 Enter interference measurement averaging period (intave): intave=x 1 to 31 8 Enter timing advance period: timing_advance_period=x 1 to 31 4 Enter MS power control period: ms_p_con_interval=x 0 to 31 2 Enter MS timeout for MS power control: ms_p_con_ack=x 0 to 31 2 Enter MS power control allowed: ms_power_control_allowed=x 0 or 1 1 Enter BTS power control interval: bts_p_con_interval=x 0 to 31 2 Enter BTS timeout for BTS power control: bts_p_con_ack=x 0 to 31 1 Enter BTS power control allowed: bts_power_control_allowed=x 0 or 1 (0 for M-Cellmicro) 0 2-26 GMR-01 68P02901W23-P 23 Feb 2004 . Technical Description BSS Command Reference Table 2-9 add_cell add_cell command prompts (Continued) Prompt Input Range Default Enter power increment step size for uplink: pow_inc_step_size_ul=x 2 to 14 EVEN 2 Enter power increment step size for downlink: pow_inc_step_size_dl=x 2 to 14 EVEN 2 Enter power reduction step size for uplink: pow_red_step_size_ul=x 2 to 4 EVEN 2 Enter power reduction step size for downlink: pow_red_step_size_dl=x 2 to 4 EVEN 2 Enter dynamic step adjust algorithm: dyn_step_adj=x 0 or 1 0 Enter factor of maximum power reduction: dyn_step_adj_fmpr=x 0 to 10 10 Enter maximum BTS transmit power: max_tx_bts=x 0 to 21 (0 to 6 for M-Cellmicro) 0 Enter maximum transmit MS: max_tx_ms=x 5 to 39 odd only (PGSM or EGSM) 0 to 36 even only (DCS1800). and 33 (PCS1900) 393633 Enter decision algorithm number: decision_alg_type=x 0 to 31 0 Enter decision alg 1 dl rxlev avg h: decision_1_dl_rxlev_av_h=x 0 to 3 0 Enter decision alg 1 dl rxlev avg ih: decision_1_dl_rxlev_av_ih=x 0 to 3 0 Enter decision alg 1 dl rxlev avg p: decision_1_dl_rxlev_av_p=x 0 to 3 0 Enter decision alg 1 dl rxqual avg h: decision_1_dl_rxqual_av_h=x 0 to 3 0 Enter decision alg 1 dl rxqual avg p: decision_1_dl_rxqual_av_p=x 0 to 3 0 68P02901W23-P 23 Feb 2004 2-27 GMR-01 . and 33 (PCS1900). 0 to 32 even only. 39 36 33 Enter receive level minimum default: rxlev_min_def=x 0 to 63 15 Enter MS transmit power maximum default: ms_txpwr_max_def=x 5 to 39 odd only (PGSM or EGSM) 0 to 36 even only (DCS1800) 0 to 32 even only. add_cell Chapter 2: Device/function related commands Table 2-9 add_cell command prompts (Continued) Prompt Input Range Default Enter decision alg 1 n1: decision_1_n1=x 1 to 31 1 Enter decision alg 1 n2: decision_1_n2=x 1 to 31 1 Enter decision alg 1 n3: decision_1_n3=x 1 to 31 1 Enter decision alg 1 n4: decision_1_n4=x 1 to 31 1 Enter decision alg 1 n5: decision_1_n5=x 1 to 31 1 Enter RSS decision alg 1 n6: decision_1_n6=x 1 to 31 1 Enter RSS decision alg 1 n7: decision_1_n7=x 1 to 31 1 Enter RSS decision alg 1 n8: decision_1_n8=x 1 to 31 1 Enter decision alg 1 ncell rxlev avg h calc: decision_1_ncell_rxlev_av_h_ calc=x 0 to 3 0 Enter decision alg 1 p1: decision_1_p1=x 1 to 31 1 Enter decision alg 1 p2: decision_1_p2=x 1 to 31 1 Enter decision alg 1 p3: decision_1_p3=x 1 to 31 1 Enter decision alg 1 p4: decision_1_p4=x 1 to 31 1 Enter decision alg 1 p5: decision_1_p5=x 1 to 31 1 Enter decision alg 1 p6: decision_1_p6=x 1 to 31 1 Enter decision alg 1 p7: decision_1_p7=x 1 to 31 1 Enter decision alg 1 p8: decision_1_p8=x 1 to 31 1 Enter decision alg 1 power budget rxlev: decision_1_p_bgt_rxlev_av_h=x 0 to 3 0 Enter decision alg 1 timing advance alg: decision_1_tim_adv_av_alg=x 0 to 3 0 Enter decision alg 1 ul rxlev avg h: decision_1_ul_rxlev_av_h=x 0 to 3 0 Enter decision alg 1 ul rxlev avg ih: decision_1_ul_rxlev_av_ih=x 0 to 3 0 2-28 GMR-01 68P02901W23-P 23 Feb 2004 . 0 to 1810 If alt_qual_proc = 1. 0 to 7 28 BER or 1 QBand Enter power control threshold u_rxqual_dl_p: u_rxqual_dl_p=x If alt_qual_proc = 0. 0 to 7 453 BER or 5 QBand Enter handover threshold l_rxqual_dl_h: l_rxqual_dl_h=x If alt_qual_proc = 0. 0 to 7 453 BER or 5 QBand Enter handover threshold l_rxlev_ul_h: l_rxlev_ul_h=x 0 to 63 10 Enter handover threshold l_rxlev_dl_h: l_rxlev_dl_h=x 0 to 63 1 Enter handover threshold u_rxlev_ul_ih: u_rxlev_ul_ih=x 0 to 63 45 Enter handover threshold u_rxlev_dl_ih: u_rxlev_dl_ih=x 0 to 63 45 68P02901W23-P 23 Feb 2004 2-29 GMR-01 . 0 to 1810 If alt_qual_proc = 1.Technical Description BSS Command Reference Table 2-9 add_cell add_cell command prompts (Continued) Prompt Input Range Default Enter decision alg 1 ul rxlev avg p: decision_1_ul_rxlev_av_p=x 0 to 3 0 Enter decision alg 1 ul rxqual avg h: decision_1_ul_rxqual_av_h=x 0 to 3 0 Enter decision alg 1 ul rxqual avg p: decision_1_ul_rxqual_av_p=x 0 to 3 0 Enter quality band processing allowed: alt_qual_proc=x 0 or 1 0 Enter power control threshold l_rxqual_ul_p: l_rxqual_ul_p=x If alt_qual_proc = 0. 0 to 7 226 BER or 4 QBand Enter power control threshold l_rxqual_dl_p: l_rxqual_dl_p=x If alt_qual_proc = 0. 0 to 1810 If alt_qual_proc = 1. 0 to 1810 If alt_qual_proc = 1. 0 to 7 226 BER or 4 QBand Enter power control threshold u_rxqual_ul_p: u_rxqual_ul_p=x If alt_qual_proc = 0. 0 to 7 28 BER or 1 QBand Enter handover threshold l_rxqual_ul_h: l_rxqual_ul_h=x If alt_qual_proc = 0. 0 to 1810 If alt_qual_proc = 1. 0 to 1810 If alt_qual_proc = 1. Enter receive level access minimum: rxlev_access_min=x 2-30 GMR-01 0 to 63 None 68P02901W23-P 23 Feb 2004 .add_cell Chapter 2: Device/function related commands Table 2-9 add_cell command prompts (Continued) Prompt Input Range Default Enter handover threshold mobile max range: ms_max_range=x 0 to 63 (only if ext_range_cell=0) 0 to 219 (if ext_range_cell=1) None Enter power control threshold l_rxlev_ul_p: l_rxlev_ul_p=x 0 to 63 30 Enter power control threshold l_rxlev_dl_p: l_rxlev_dl_p=x 0 to 63 30 Enter power control threshold u_rxlev_ul_p: u_rxlev_ul_p=x 0 to 63 40 Enter power control threshold u_rxlev_dl_p: u_rxlev_dl_p=x 0 to 63 40 Enter Alternate flag for missing report: missing_rpt=x 0 or 1 0 Enter Alternate flag for BA allocating process: ba_alloc_proc=x 0 or 1 0 Enter RSS link fail: link_fail=x 0 to 15 4 Enter link about to fail: link_about_to_fail=x 0 to 15 2 Enter Alternate flag for full power RF loss: full_pwr_rfloss=x 0 or 1 0 Enter cell bar access switch: cell_bar_access_switch=x 0 or 1 0 Enter cell bar access class: cell_bar_access_class=x 0 to 65535 0 Enter emergency class switch: emergency_class_switch=x 0 or 1 0 Enter report resource TCH full high water mark: report_resource_tch_f_high_ water_mark=x 0 to 255 2 Enter report resource TCH full low water mark: report_resource_tch_f_low_ water_mark=x 0 to 255 12 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. and 33 (PCS1900) 2 Enter tx_integer for RACH retransmit spacing: tx_integer=x 0 to 15 4 Enter radio link timeout: radio_link_timeout=x 0 to 15 4 Enter MS reestablish allowed: reestablish_allowed=x 0 or 1 0 Enter cell reselect hysteresis: cell_reselect_hysteresis=x 0 to 7 None Enter C2 cell reselection parameter indicator: cell_reselect_param_ind=x 0 or 1 0 Enter C2 cell bar qualify: cell_bar_qualify=x 0 or 1 0 Enter C2 cell reselection offset: cell_reselect_offset=x 0 to 63 0 Enter C2 temporary offset: temporary_offset=x 0 to 7 0 Enter C2 penalty time: penalty_time=x 0 to 31 0 Enter rapid power down procedure active: rapid_pwr_down=x 0 or 1 0 Enter rapid power down trigger threshold: rpd_trigger=x 0 to 63 45 Enter rapid power down level offset: rpd_offset=x 0 to 63 8 Enter rapid power down averaging period: rpd_period=x 1 to 32 2 68P02901W23-P 23 Feb 2004 2-31 GMR-01 .Technical Description BSS Command Reference Table 2-9 add_cell add_cell command prompts (Continued) Prompt Input Range Default Enter uplink dtx preference: dtx_required=x 0 to 2 2 Enter IMSI attach detach: attach_detach=x 0 or 1 0 Enter NCC of PLMN allowed: ncc_of_plmn_allowed=x 0 to 255 255 Enter maximum retransmissions on RACH: max_retran=x 0 to 3 0 Enter maximum mobile transmit power on CCCH: ms_txpwr_max_cch=x 5 to 39 odd only (PGSM and EGSM) 0 to 36 even only (DCS1800) 0 to 32 even only. "disp_gsm_cells" on page 2-253. "freq_types_allowed" on page 2-376. 2-32 GMR-01 68P02901W23-P 23 Feb 2004 . "del_cell" on page 2-168.add_cell Chapter 2: Device/function related commands Related commands "copy_cell" on page 2-156. "disp_cell" on page 2-205. 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. network_entity_id The AXCDR or ABSS device identifier that represents the actual RXCDR or BSS with which this MMS is communicating.Technical Description BSS Command Reference add_conn add_conn Description The add_conn command adds MMS connectivity between the RXCDR and the BSS. The term “remote site" refers to the site to which the local site is being connected. remote_mms_id_2 68P02901W23-P 23 Feb 2004 2-33 GMR-01 . 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. local_mms_id_2 Second identifier of the MMS at the local site. remote_mms_id_1 First identifier of the MMS at the remote site. The term “local site" refers to the site where the command is being entered. Connectivity may be added for a maximum of 21 MMSs at a BSC or RXCDR regardless of how many RXCDRs or BSSs are connected. "disp_conn" on page 2-223. which is represented by equipped device AXCDR 3. 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.add_conn Chapter 2: Device/function related commands Second identifier of the MMS at the remote site. Table 2-10 shows the ranges for several input parameters dependant on where the command is executed. The add_conn command can be executed from either the BSC or RXCDR. "mod_conn" on page 2-390 2-34 GMR-01 68P02901W23-P 23 Feb 2004 . 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-171. that is: 0. 975 to 1023 50 if source frequency is in the EGSM frequency. Table 2-11 Neighbour Frequency and number with EGSM source cell Neighbour frequency range Maximum number of neighbours 1 to 124 64 975 to 1023 49 0. • If a PCS1900 neighbour exists in a neighbour list. 975 to 1023 64 if source frequency is not zero. no PCS1900 neighbours may be added. 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. • If a DCS1800 neighbour exists in a neighbour list. 975-1023 17 if source frequency is in the PGSM frequency. that is: 1-124 1 to 124. a neighbour may not have a frequency type of PCS1900. A maximum of 64 neighbours can be added to a 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. 64 . Table 2-11 lists the frequency range and maximum number of neighbours for an EGSM source cell. 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.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 32 neighbours may be added to the BA_SACCH list. 68P02901W23-P 23 Feb 2004 2-35 GMR-01 .e if source frequency is 0.If the source frequency type is PCS1900.1 to 124 64 0. see Table 2-12 for the limitations on the maximum neighbours that can be added to the DCS1800 frequency type source cell. where e (the number of EGSM frequencies) is less than or equal to 16. a neighbour may not have a frequency type of DCS1800. 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. no DCS1800 neighbours may be added. this command supports the UMTS UTRAN cell identity format. a series of prompts are presented where parameters defining the neighbour cell are entered. A total of 64 neighbours can be created but a maximum of 32 can be on the BA_BCCH list only.e if source frequency is in the PGSM frequency range. Table 2-12 lists the frequency range and maximum number of neighbours for a DCS 1800 source cell. The required input parameters depend on whether or not the neighbour cell is internal to the BSS or external to the BSS. 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. The prompted parameters are described in the Related Information at the end of this section. where e (the number of EGSM frequencies) is less than or equal to 16. 975 to 1023 64 . 975 to 1023 17 1 to 124 and 975 to 1023 16 0.e if source frequency is in the EGSM frequency range. where e (the number of PGSM frequencies) is less than or equal to 17. 1 to 124 and 975 to 1023 17 The BA_SACCH list can have up to 32 neighbours. 1 to 124 17 0.add_neighbor Chapter 2: Device/function related commands Table 2-11 Neighbour Frequency and number with EGSM source cell (Continued) Neighbour frequency range Maximum number of neighbours 0. If the Inter_RAT (Radio Access Technology) handover feature is unrestricted. Security level 2 Supported by OMC-R GUI Yes Command type B (operator actions required) 2-36 GMR-01 68P02901W23-P 23 Feb 2004 . 1 to 124 64 . This command permits neighbour BCCH frequencies in the GSM Extension band provided the egsm_bcch_sd parameter is enabled. After the command is entered. The format for the GSM Cell ID depends on: • The system being used (PGSM. it must be placed inside double quotation marks. PCS1900. Contact the OMC-R for help. Input parameters source_cell_id GSM Cell ID of the cell to to which a neighbour cell is to be assigned.Technical Description BSS Command Reference add_neighbor Prerequisites To be on the Neighbour Cell List. The name of the cell created using the cell_name command may be entered in place of the cell_id. This command does not work at a BTS site. For a PGSM or EGSM site. and 975 to 1023. only external neighbour cells with BCCH ARFCNs in the following ranges may be added: 0 to 124. the Inter-RAT handover option must be unrestricted. 128 to 251. 512 to 885. only external neighbour cells with BCCH ARFCNs in the range 1 to 124 may be added. DCS1800. For handovers to UMTS UTRAN cells. a cell must be the destination of handovers from the Neighbour List owner. For a GSM 850 site. Operator action Reply to prompts as displayed. When the cell name is entered. directly or in a script. Enter this command at the BSC only. 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. GSM 850) • Whether the seven parameter GSM cell ID format or the four parameter GSM cell id format has been enabled. 68P02901W23-P 23 Feb 2004 2-37 GMR-01 . EGSM. Only PCS1900 and GSM 850 systems can use a three digit MNC. • Whether the cell is a UMTS UTRAN cell. Synchronized handovers are allowed only between cells that are at the same site. neighbor_cell_id GSM Cell ID of the cell being assigned as a neighbour cell. and shares the same BSS of the src_gsm_cell_id. it must be placed inside double quotation marks. Example 2 In this example. the MMI prompts for the required parameters to describe the neighbour cell being added (see Related information). The example demonstrates adding a cell to the Neighbour Cell List that is internal to that neighbour cell. If they are incompatible. 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 word. external follows the second cell ID indicating that the cell being added is external to. Only PCS1900 and GSM 850 systems can use a three digit MNC. and does not share the BSS of the src_gsm_cell_id. the system rejects the command. This permits test neighbours to be added to the BA_SACCH and/or BA_BCCH lists. The word. 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 string test <num> may be entered for this field where <num> is a value from 1 to 64. When a test neighbour is added.add_neighbor Chapter 2: Device/function related commands The name of the cell created using the cell_name command may be entered in place of the cell_id. See the descriptions for "bsic" on page 5-77 and "ncc_of_plmn_allowed" on page 5-536 for more information. When the cell name is entered. 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. 2-38 GMR-01 68P02901W23-P 23 Feb 2004 . the value entered in the placement field is ignored and the frequency is the only prompted parameter. 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. internal follows the second cell ID indicating that the cell being added is internal to. Examples Example 1 In this example. The cell_name may only be entered in place of the neighbor_cell_id for internal neighbour cells. The example demonstrates adding a cell to the Neighbour Cell List that is external to that neighbour cell. The system checks the BSIC of the neighbour cell against the ncc_of_plmn value of the source cell. Example 3 In this example. the MMI prompts for the required parameters to describe the neighbour cell being added (see Related information). Example 4 In this example. 68P02901W23-P 23 Feb 2004 2-39 GMR-01 . the MMI prompts for the required parameters to describe the neighbour cell being added (see Related information). 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 After verification of the command.Technical Description BSS Command Reference add_neighbor add_neighbor 5 4 3 2 1 71543 12444 5 4 3 2 1 61986 34944 external Where: is: 5 4 3 2 1 71543 12444 source_cell_id 5 4 3 2 1 61986 34944 neighbor_cell_id external placement System response COMMAND ACCEPTED After verification of the command. 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 After verification of the command. the MMI prompts for the required parameters to describe the neighbour cell being added (see Related information). for PCS1900 39 for PGSM and EGSM 36 for DCS180033 for PCS1900 N/A for internal neighbours Enter neighbor receive level minimum: 0 to 63 rxlev_min_def Required for external of neighbour neighbours cell 2-40 GMR-01 These three prompts appear only if the Network Controlled Cell Reselection feature (NCCR) is unrestricted. If a proper response is not entered within the time limit.add_neighbor Chapter 2: Device/function related commands References Related information There is a time limit of 30 seconds in which to enter responses to the parameter prompts that are presented. Enable synchronization: 1 (Yes) 0 (No) 0 N/A for external neighbours Enter the BCCH frequency number: 1 to 124 for PGSM 0. the command is abandoned and all values entered up to that point are lost. 68P02901W23-P 23 Feb 2004 . A value MUST be entered at this prompt. 1 to 124. 975 to 1023 for EGSM 512 to 885 for DCS1800 512 to 810 for PCS1900 None. Table 2-13 add_neighbor command prompts Prompt Range Default Notes Add neighbor to the BA BCCH list (yes/no)? yes no yes Add neighbor to the BA SACCH list (yes/no)? yes no yes Add neighbor to the BAGPRS list (yes/no)? yes no yes Enter the neighbor cell frequency type: pgsmegsmdcs 1800pcs 1900gsm 850 None N/A for internal neighbours. N/A for internal neighbours Enter MS transmit power maximum: 5 to 39 (odd values only) for PGSM and EGSM 0 to 36 (even values only) for DCS1800 0 to 32 (even values only) and 33. A value MUST be entered at this prompt. Table 2-13 lists the command prompts for the add_neighbor command. Enter base station identity code (bsic): 0 to 63 None. N/A for internal neighbours EGSM BCCH frequencies 0. 975 to 1023 are not available when the egsm_bcch_sd parameter is disabled. A value MUST be entered at this prompt. N/A if Microcell is not purchased and pbgt_alg_type 0 5 Enter the delay time: 0 to 255 0 SACCH periods N/A if Microcell is not purchased and pbgt_alg_type 0 6 Enter the handover static offset: 0 to 127 0 N/A if Microcell is not purchased and pbgt_alg_type 0 6 Enter the handover dynamic offset: 0 to 127 0 N/A if Microcell is not purchased and pbgt_alg_type 0 6 68P02901W23-P 23 Feb 2004 Required for external neighbours Refer to the description of the ho_margin_def parameter. Enter the uplink receive level threshold of the serving cell: 0 to 255 None. A value MUST be entered at this prompt. N/A if Microcell is not purchased and pbgt_alg_type 0 3 Enter the downlink receive level threshold of the serving cell: 0 to 255 None N/A if Microcell is not purchased and pbgt_alg_type 0 3 Enter the qualifying time threshold: 0 to 255 0 SACCH periods N/A if Microcell is not purchased and pbgt_alg_type 0 4 Enter the qualifying delay time: 0 to 255 0 SACCH periods N/A if Microcell is not purchased and pbgt_alg_type 0 5 Enter the neighbor cell receive level threshold: 0 to 63 None.Technical Description BSS Command Reference Table 2-13 add_neighbor add_neighbor command prompts (Continued) Prompt Range Default Notes Enter neighbor handover margin: -63 to 63 ho_margin_def of neighbour cell Enter the power budget surrounding cell hreqave: 1 to 31 8 Enable adjacent channel interference avoidance test?: 1 (Yes) 0 (No) 0 (No) NA if Microcell is not purchased Enter rxlev difference for adjacent channel interference avoidance test: -63 to 63 0 NA if Microcell is not purchased This prompt only applies if the previous answer was 1 Enter the power budget algorithm type: 1 to 7 1 N/A if Microcell is not purchased Enter the adjacent channel interference detection handover margin: -63 to 63 ho_margin_cell This prompt only appears if pbgt_alg_type=7. 2-41 GMR-01 . and the neighbour is being added to the SACCH list Enter the threshold for inner zone handover: 0 to 63 0 Only prompted if “Does the neighbor have a carrier with an interfering frequency?" = 1 (yes). "copy_cell" on page 2-156. Enter the range of the neighbor cell: normal extended Normal This prompt is only presented if the Extended Range Cells feature is unrestricted. 2-42 GMR-01 68P02901W23-P 23 Feb 2004 . Does this neighbor have a carrier with an interfering frequency? 1 (Yes) 0 (No) 0 Only prompted if inner_zone_alg for the source cell is set to 2. set the value to 63 ho_margin_cell of neighbour cell Value should be less than or equal to the ho_margin_cell of the neighbour cell. "disp_cell" on page 2-205. Enter the margin for inner zone handover: 0 to 63 0 Only prompted if “Does the neighbor have a carrier with an interfering frequency?" = 1 (yes).add_neighbor Chapter 2: Device/function related commands Table 2-13 add_neighbor command prompts (Continued) Prompt Range Default Notes Enter neighbor congestion handover margin: -63 to 63To disable congestion handovers to this neighbour. Related commands "add_cell" on page 2-21. "disp_gsm_cells" on page 2-253. "disp_neighbor" on page 2-281. "modify_neighbor" on page 2-395. This prompt is only presented if directed retry or congestion relief is purchased. "del_cell" on page 2-168. Is directed retry allowed at this external neighbor cell?: 1 (Yes) 0 (No) 1 N/A when adding internal neighbours This prompt is only presented if directed retry or congestion relief is purchased. "del_neighbor" on page 2-173. Format Syntax {4040} add_nsvc <pcu_n> <ns_vci> <gbl_id> <dlci> Input parameters pcu_n pcu. gbl_id 0 to 3 Object identifier of the GBL dlci 16 to 991 Local identifier for a virtual connection on a GBL. {4040} ns_vci 0 to 65535 The virtual connection on a GLB: Unique identifier of the NSVCI mapping.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 Supported by OMC-R GUI Yes Command type A (no operator action) Prerequisites The GPRS feature must be unrestricted. pcu_0 to pcu_2 The PCU at which the NSVCI or DLCI are to be mapped to the specific 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 {4040} on PCU 1: 68P02901W23-P 23 Feb 2004 2-43 GMR-01 . and identifier of the object. 2-44 GMR-01 68P02901W23-P 23 Feb 2004 . "mod_nsvc" on page 2-393.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-177. This command does not work at a BTS site. RTFs automatically use the PATH(s) defined for these types of sites. Format Syntax add_rtf_path <location> <1st_RTF_identifier> <2nd_RTF_identifier> <unique_PATH_identifier> Input parameters location Indicates the number of the BTS where the RTF is located. Security level 2 Supported by OMC-R GUI Yes Command type A (no operator action) Prerequisites This command can only be executed at the BSC. RTFs do not use PATH(s) equipped by the operator for these types of sites. Contact the OMC-R for help. The system rejects attempts to modify the PATHs used by RTFs at sites that use dynamic allocation. Enter this command at the BSC only. 68P02901W23-P 23 Feb 2004 2-45 GMR-01 . Adding a redundant path that is shorter than the current path causes a switch to the shorter path. PATHs for such sites are defined by the equip DYNET command. 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 range of values is 1 to 120. then first equip any necessary MSI before equipping the PATH. The parameters that identify a particular PATH are location and Unique_PATH_identifier. If no redundant PATH is equipped.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. 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-162. Example This example adds a redundant RTF PATH to site 3. RTF identifiers 2 1. "del_rtf_path" on page 2-179. "disp_traffic" on page 2-318. The range of values is 0 to 9. 0 or 1 for M-Cell. The range of values is: 0 to 11 for InCell.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. unique_PATH_identifier Specifies the unique PATH to a particular site. 2-46 GMR-01 68P02901W23-P 23 Feb 2004 . "disp_rtf_path" on page 2-305. pcu_0 to pcu_2 {4040} 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-P 23 Feb 2004 2-47 GMR-01 . If the location is specified as all from a BSC.] [<mode>] Input parameters location Specifies the site location: 0 or bsc BSC 1 to 120 BTS pcu. Security level 1 Supported by OMC-R GUI No Command type A (no operator action) Prerequisites The GPRS must be unrestricted in order to assess a PCU site. this command displays whether alarms are enabled or disabled.Technical Description BSS Command Reference alarm_mode alarm_mode Description The alarm_mode command registers or deregisters the MMI to receive device.<location>. and statistical alarm reports for the specified sites.. Format Syntax alarm_mode <location>[.<location>. or disabled). alarms for all sites are affected (either displayed. If no mode is specified. non-reconfiguration type. enabled.. alarm_mode Chapter 2: Device/function related commands System response SITE ----0 MODE ----------------------Alarm reporting enabled Example 2 {4040} Specifies alarm mode as Off for PCU site 0 and PCU site 1: alarm_mode pcu_0 pcu_1 off System response SITE ----pcu_0 pcu_1 MODE -----------------------Alarm reporting disabled Alarm reporting disabled 2-48 GMR-01 68P02901W23-P 23 Feb 2004 . OOS Devices Affecting Functional Unit: The Alarm Device is the primary alarm for the reconfiguration. Complete device IDs are not listed. When multiple devices and/or functions have gone OOS (Out Of Service) as part of separate reconfigurations. depending on whether a SITE or device is specified as follows: SITE When a site is specified. Device reports are displayed in the following format: Alarm Device: of : Cause: Outcome: Functional Unit: -. one report is generated for each active reconfiguration that satisfies the request. with wild cards. 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. The FU statuses are defined as: MAJOR = Loss of Capacity. or (c) both active alarms and OOS devices. or for all sites. or (b) one or more devices still OOS. Once all devices are restored to an in service state. 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. Device A device may be specified individually. Only the FUs and device types which have non-CLEAR status are listed. the functions should be assigned to the appropriate devices and cease to impact the FUs. but instead the message No Primary Alarm for this Reconfiguration is displayed. If multiple reports are generated as part of a single assess command. MINOR = Loss of Redundancy. The information is presented in a concise format that indicates where problems are and what should be done. CRITICAL = Loss of Service.Status: Current Status: -. information on the status of Functional Units (FUs) and which device types contribute to that status is reported. An alarm and the alarm device is not displayed for a reconfiguration that does not have an active alarm yet has OOS devices. “active" means any reconfiguration with: (a) one or more alarms active against it.Technical Description BSS Command Reference assess assess Description The assess command displays different types of information. The alarm is displayed even though it may have cleared already. multiple reports are generated. Functions are not displayed as an OOS device because there is no maintenance action to perform on a function. 68P02901W23-P 23 Feb 2004 2-49 GMR-01 . For the purposes of this command. Security level 1 Supported by OMC-R GUI No Command type A (no operator action) Prerequisites The GPRS feature must be unrestricted to assess a PCU site. displays when devices are OOS and are still associated with this reconfiguration. the device ID and state are listed. 2-50 GMR-01 68P02901W23-P 23 Feb 2004 . The system accepts the wildcard character (*) for the device or function ID.assess Chapter 2: Device/function related commands The line OOS Devices Affecting Functional Unit. The line No devices remain OOS as a result of this configuration. This information can be displayed with either the state or disp_act_alarm command. 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. For each device impacting the listed FU. pcu_0 to pcu_2 {4040} PCU all All active sites dev/func name Specifies the device or function. dev/func id Specifies the ID for the device or function. Format Syntax assess <location> [all] [<dev/func name> <dev/func id> <dev/func id>] [*] Input parameters location Specifies the site location: 0 or bsc BSC 1 to 120 BTS pcu. one per line. In this particular scenario. the operator is concerned about the OMLs contributing to the severity of MAJOR.Status: MAJOR Current Status: MAJOR -.OOS Devices Affecting Functional Unit: OML 0 0 0 DISABLED UNLOCKED MMS Not In Service OML 1 0 0 DISABLED UNLOCKED MMS Not In Service 68P02901W23-P 23 Feb 2004 2-51 GMR-01 . 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 -. 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 -----------------------SITE 0 DEVICE/FUNCTION --------------BSP OML CBUS SITE 3 RSL CELL 001 01 1 2 DRI SEVERITY -------------------------MAJOR (Loss of Capacity) MAJOR (Loss of Capacity) MAJOR (Loss of Capacity) MINOR (Loss of Redundancy) MAJOR (Loss of Capacity) MAJOR (Loss of Capacity) MINOR (Loss of Redundancy) MINOR (Loss of Redundancy) Example 2 In the following example.Technical Description BSS Command Reference assess Examples Example 1 In the following example. BSC has just been initialized. assess Chapter 2: Device/function related commands Functional Unit: SITE 3 -. the operator is concerned about the RSLs which are impacting SITE 3. In this case.OOS Devices Affecting Functional Unit: DRI 1 4 0 DISABLED UNLOCKED DRI Not Detected ASSESS REPORT COMPLETE Example 3 In the following example.Status: MAJOR Current Status: MAJOR -.Status: MAJOR Current Status: MAJOR -.No devices remain OOS as a result of this configuration Functional Unit: CELL 001 01 1 2 -. 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 (242) Device(s) OOS due to action on this device Alarm Device: RSL 3 0 0 LOCK of RSL: 3 0 0 Cause: OMC REQUEST Outcome: Alarm Functional Unit: SITE 3 -.OOS Devices Affecting Functional Unit: RSL 3 1 0 DISABLED UNLOCKED NO REASON No Primary Alarm for this Reconfiguration UNLOCK of RSL 3 1 Cause: OMC REQUEST Outcome: Alarm Functional Unit: SITE 3 -.OOS Devices Affecting Functional Unit: RSL 3 0 0 DISABLED UNLOCKED NO REASON (242) Device(s) OOS due to action on this device Alarm Device: RSL 3 1 0 LOCK of RSL: 3 1 0 Cause: OMC REQUEST Outcome: Alarm Functional Unit: SITE 3 -.Status: MINOR Current Status: MAJOR -.Status: MAJOR Current Status: MAJOR -.OOS Devices Affecting Functional Unit: RSL 3 1 0 DISABLED UNLOCKED No Link 2-52 GMR-01 68P02901W23-P 23 Feb 2004 .Status: MAJOR Current Status: MINOR -. Technical Description BSS Command Reference assess ASSESS REPORT COMPLETE Example 4 {4040} The following example shows an assess display for PCU site 0: assess pcu_0 Where: is: pcu_0 location System response SITE / CELL ----------------------------------PCU 0 DEVICE/FUNCTION --------------GBL GSL DPROC MSI SEVERITY --------CRITICAL CRITICAL MAJOR MAJOR MAJOR COMMAND ACCEPTED Example 5 {4040} 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-P 23 Feb 2004 2-53 GMR-01 . The second permits the suspension/resumption of all audits at a specific site. Security level 2 Supported by OMC-R GUI Yes Command type A (no operator actions) Prerequisites None This command does not work at an M-Cell site. The first allows the execution of safe tests or all audits for all devices within a specific cage. There are only two possible System Responses to a cage_audit command: • The display of results. • ERROR.cage_audit Chapter 2: Device/function related commands cage_audit Description The cage_audit command performs two different functions. Devices listed within the CAGE can also generate messages specific to the device. Format Syntax cage_audit <location> <audit_type> <cage_number> cage_audit <location> <control> <cage_number> Input parameters location 2-54 GMR-01 68P02901W23-P 23 Feb 2004 . The ERROR response is due to a non-device related cause and is followed by a display of the error description. Contact the OMC-R for help. off Suspends all site audits within a cage at a specific site.Technical Description BSS Command Reference cage_audit Specifies the audit location: 0 or bsc BSC 1 to 120 BTS pcu. all Initiates all audits. 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 Audit Type: SAFE Result: PASS Device: KSW Device id: 0 0 0 Year: 1994 Month: 11 Day: 12 68P02901W23-P 23 Feb 2004 Hour: 0 Min: Hour: 0 in: 26 Sec: 26 Sec: 26 MSec: 27 MSec: 495 860 2-55 GMR-01 . control Specifies the audit status: on Resumes all site audits within a cage at a specific site. pcu_0 to pcu_2 {4040} PCU audit_type Specifies the type of audit: safe Initiates safe tests. audits turned off for cage. 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 Year: 1998 Month: 10 Day: 12 Hour: Audit Type: SAFE Result: ERROR 14 Min: 10 Sec: 22 MSec: 930 ERROR: Audit not available. Example 4 This example executes safe audits for all devices for cage 0 at the PCU (GPRS): 2-56 GMR-01 68P02901W23-P 23 Feb 2004 .cage_audit Chapter 2: Device/function related commands Audit Device: Year: Audit Device: Year: Audit Device: Year: Audit Device: Year: Audit Type: INT LPBK Result: PASS MSI Device id: 3 0 0 1994 Month: 11 Day: 12 Hour: Type: SAFE Result: PASS MSI Device id: 1 0 0 1994 Month: 11 Day: 12 Hour: Type: SAFE Result: PASS DRI Device id: 0 1 0 1994 Month: 11 Day: 12 Hour: Type: SAFE Result: PASS GPROC Device id: 1 0 0 1994 Month: 11 Day: 12 Hour: Type: SAFE Result: ERROR 0 Min: 26 Sec: 28 MSec: 630 0 Min: 26 Sec: 29 MSec: 665 0 Min: 26 Sec: 29 MSec: 665 0 Min: 26 Sec: 31 MSec: 595 ERROR: Audit not available for this device. "query_audits" on page 2-407. "device_audit" on page 2-184. 68P02901W23-P 23 Feb 2004 2-57 GMR-01 . "site_audit" on page 2-438.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 Audit Type: SAFE Result: PASS Device: DPROC Device id: 2 0 0 Year: 1998 Month: 1 Day: 12 Hour: 16 Audit Type: SAFE Result: PASS Device: DPROC Device id: 7 0 0 Year: 1998 Month: 1 Day: 12 Hour: 16 Audit Type: SAFE Result: PASS Device: MSI Device id: 3 0 0 Year: 1998 Month: 1 Day: 12 Hour: Audit Type: SAFE Result: PASS Min: 22 Sec: 26 MSec:495 Min: 22 Sec: 27 MSec:860 Min: 22 Sec: 28 MSec:630 16 Min: 22 Sec: 29 MSec:665 Example 5 {4040} 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. or modified. 2-58 GMR-01 68P02901W23-P 23 Feb 2004 . Enter this command at the BSC only. DCS1800. • Whether the seven parameter GSM Cell ID format or the four parameter GSM cell ID format has been enabled. The name may be a text string up to 31 alphanumeric characters in length. Contact the OMC-R for help. cell_name The name to be assigned to the Cell ID. The cell name must be entered inside double quotation marks. including dash characters used for separation. The format for the GSM Cell ID depends on is: • The system used (PGSM. EGSM. displayed. renames a cell. or displays the name assigned to a Cell ID. This command does not work at a BTS site. 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.cell_name Chapter 2: Device/function related commands cell_name Description The cell_name command assigns a unique name to a Cell ID. Security level 2 Supported by OMC-R GUI Yes Command type A (no operator actions) Prerequisites A security level of 2 is required to create or modify a cell name. The system does not permit duplicate cell names to be entered. PCS1900). 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. 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. 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. The underscore character may not be used as part of the name or as a separator.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 Cell ID 5 4 3 2 1 61986 34944 is assign the cell name “london-west". Double quotation marks may not be used as part of a cell name. the system response is: “No textual name exists for this cell. 68P02901W23-P 23 Feb 2004 2-59 GMR-01 . the cell name assigned to Cell ID 5 4 3 2 1 61986 34944 displays. Examples Example 1 In this example. The cell_name displays inside double quotes. If no value is entered for this parameter. the current cell name displays. the PCS1900 Cell ID 543 721 61986 34944 is assigned the name “london-west".cell_name Chapter 2: Device/function related commands Example 3 In this example. 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 GMR-01 68P02901W23-P 23 Feb 2004 . 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 existing cell name “london-west" is removed. The threshold is used as the lower decision threshold for switching between the codec modes. or both. 68P02901W23-P 23 Feb 2004 2-61 GMR-01 . and the uplink and downlink adaptation threshold and hysteresis values for Full Rate (FR). the codec may operate at various combinations of speech and channel coding (codec mode) bit-rate for each channel mode. one for downlink codec mode adaptation and one for uplink codec mode adaptation. The sum of the threshold and the hysteresis constitutes the upper threshold between the codec modes. The ACS is configured by the operator on a per cell basis. The site must be an AMR-capable BTS. There are two sets of thresholds and hysteresis per ACS.4 kbits/s (Half-Rate) and at 22. Security level 3 Supported by OMC-R GUI No Command type A (no operator actions) Prerequisites The AMR feature must be unrestricted.8 kbits/s (Full Rate) over the air interface. Parameters can be set before or after AMR is enabled in the cell. 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.Technical Description BSS Command Reference chg_acs_params chg_acs_params {4322} Description The chg_acs_params command specifies up to four codec modes to be used in the Active Codec Set (ACS). 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). There is a separate ACS for Full Rate and Half Rate. Half Rate (HR). Dependencies Either AMR Full-Rate or Half-Rate must be enabled in the cell for the AMR parameters to come into effect. the initial codec mode. Plus. The term “Adaptive Multi-Rate codec" refers to the speech and channel codec capable of operating at gross bit-rates of 11. Only PCS1900 systems can use a three digit MNC.15 kbit/s Full Rate attribute values for the chg_acs_params command are listed in Table 2-15. DCS1800.90 kbit/s 6 5.chg_acs_params Chapter 2: Device/function related commands The sum of the values for threshold and hysteresis must be less than 63.40 kbit/s 4 6.20 kbit/s 1 10. EGSM.20 kbit/s 2 7. 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. 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.70 kbit/s 5 5. • Whether the seven parameter GSM Cell ID format or the four parameter GSM Cell ID format has been enabled. and the Half Rate attribute values are listed in Table 2-16 2-62 GMR-01 68P02901W23-P 23 Feb 2004 .95 kbit/s 3 7. The format for the GSM Cell ID depends on: • The system used (PGSM. PCS1900). If one mode is entered for the Full Rate ACS. 1. 1. 3. amr_fr_uplink_hysteresis3 amr_fr_uplink_hysteresis2 amr_fr_uplink_hysteresis1 0 to 15 0 to 15 0 to 15 111 The sum of the associated threshold and hysteresis is used as the upper decision threshold for switching the codec mode. 1. amr_fr_uplink_threshold3 amr_fr_uplink_threshold2 amr_fr_uplink_threshold1 0 to 63 0 to 63 0 to 63 20149 Lower Full Rate uplink decision threshold for switching from one mode to another. amr_fr_downlink_threshold3_hopping amr_fr_downlink_threshold2_hopping amr_fr_downlink_threshold1_hopping 0 to 63 0 to 63 0 to 63 262114 Downlink switching thresholds applied to frequency hopping channels. amr_fr_uplink_threshold3_hopping amr_fr_uplink_threshold2_hopping amr_fr_uplink_threshold1_hopping 0 to 63 0 to 63 0 to 63 16114 Uplink switching thresholds applied to frequency hopping channels. amr_fr_initial_codec_mode 0.Technical Description BSS Command Reference Table 2-15 chg_acs_params Full Rate attribute values for chg_acs_params command Attribute Range Default Notes amr_fr_acs 0. 3. 3. amr_fr_uplink_hysteresis3_hopping amr_fr_uplink_hysteresis2_hopping amr_fr_uplink_hysteresis1_hopping 0 to 15 0 to 15 0 to 15 111 Uplink hysteresis applied to frequency hopping channels. 6 1 Codec mode used at the beginning of a call. 68P02901W23-P 23 Feb 2004 2-63 GMR-01 . then the Full Rate Initial Codec Mode defaults to this (if valid). amr_fr_downlink_threshold3 amr_fr_downlink_threshold2 amr_fr_downlink_threshold1 0 to 63 0 to 63 0 to 63 302419 Lower Full Rate downlink decision threshold for switching from one mode to another. 4. 6 Up to four AMR codec modes which can be used for any given voice call in the uplink or downlink direction. 6 0. 4. amr_fr_downlink_hysteresis3_hopping amr_fr_downlink_hysteresis2_hopping amr_fr_downlink_hysteresis1_hopping 0 to 15 0 to 15 0 to 15 111 Downlink hysteresis applied to frequency hopping channels. amr_fr_downlink_threshold3 amr_fr_downlink_threshold2 amr_fr_downlink_threshold1 0 to 15 0 to 15 0 to 15 111 The sum of the associated threshold and hysteresis is used as the upper decision threshold for switching the codec mode. 4. amr_hr_downlink_threshold3 amr_hr_downlink_threshold2 amr_hr_downlink_threshold1 0 to 15 0 to 15 0 to 15 11 The sum of the associated threshold and hysteresis is used as the upper decision threshold for switching the codec mode. 5. amr_hr_uplink_threshold3_hopping amr_hr_uplink_threshold2_hopping amr_hr_uplink_threshold1_hopping 0 to 63 0 to 63 0 to 63 2821 Uplink switching thresholds applied to frequency hopping channels. 5. If one mode is entered for the Half Rate ACS. 5. 3. amr_hr_uplink_hysteresis3_hopping amr_hr_uplink_hysteresis2_hopping amr_hr_uplink_hysteresis1_hopping 0 to 15 0 to 15 0 to 15 11 Uplink hysteresis applied to frequency hopping channels. 68P02901W23-P 23 Feb 2004 . 6 4 Codec mode used at the beginning of a call.chg_acs_params Chapter 2: Device/function related commands Table 2-16 Half Rate attribute values for chg_acs_params command Attribute Range Default amr_hr_acs 2. amr_hr_downlink_threshold3 amr_hr_downlink_threshold2 amr_hr_downlink_threshold1 0 to 63 0 to 63 0 to 63 30 24 Lower Half Rate downlink decision threshold for switching from one mode to another. amr_hr_uplink_hysteresis3 amr_hr_uplink_hysteresis2 amr_hr_uplink_hysteresis1 0 to 15 0 to 15 0 to 15 11 The sum of the associated threshold and hysteresis is used as the upper decision threshold for switching the codec mode. amr_hr_downlink_hysteresis3_hopping amr_hr_downlink_hysteresis2_hopping amr_hr_downlink_hysteresis1_hopping 0 to 15 0 to 15 0 to 15 11 Downlink hysteresis applied to frequency hopping channels. 6 4. amr_hr_uplink_threshold3 amr_hr_uplink_threshold2 amr_hr_uplink_threshold1 0 to 63 0 to 63 0 to 63 28 22 Lower Half Rate uplink decision threshold for switching from one mode to another. 4. 2-64 GMR-01 Notes Up to four AMR codec modes which can be used for any given voice call in the uplink or downlink direction. 3. then the Half Rate Initial Codec Mode defaults to this (if valid). 6 amr_hr_initial_codec_mode 2. amr_hr_downlink_threshold3_hopping amr_hr_downlink_threshold2_hopping amr_hr_downlink_threshold1_hopping 0 to 63 0 to 63 0 to 63 3023 Downlink switching thresholds applied to frequency hopping channels. Enter AMR Full Rate uplink adaptation hysteresis: Yes Enter up to three uplink hysteresis values. One value for each adjacent pair of codec modes in ACS. Enter AMR Full Rate uplink adaptation thresholds: Yes Enter up to three uplink threshold values in order of descending C/I estimation. Prompt displays if the ACS contains more than one codec mode. One value for each adjacent pair of codec modes in ACS. Prompt displays if the ACS contains more than one codec mode. see Table 2-14). Prompt displays if the ACS contains more than one codec mode. Enter AMR Full Rate uplink adaptation hysteresis for frequency hopping: Yes Enter up to three values. Prompt displays if the ACS contains more than one codec mode. Prompt displays if the AMR feature is unrestricted. Enter AMR Full Rate downlink adaptation hysteresis: Yes Enter up to three downlink hysteresis values. 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 Rate active codec set: Yes Up to four codec mode values (codec rates) are entered in order of descending bit-rate (ascending field value 0 to 7. Prompt displays if the ACS contains more than one codec mode.Technical Description BSS Command Reference chg_acs_params Full Rate prompts for the chg_acs_params command are listed in Table 2-17. One downlink value for each adjacent pair of codec modes in ACS. One uplink value for each adjacent pair of codec modes in ACS. One downlink value for each adjacent pair of codec modes in ACS. 68P02901W23-P 23 Feb 2004 2-65 GMR-01 . the BTS type is AMR-capable. Prompt displays if the ACS contains more than one codec mode. Enter AMR Full Rate downlink adaptation thresholds: Yes Enter up to three downlink threshold values in order of descending C/I estimation. Enter AMR Full Rate uplink adaptation thresholds for frequency hopping: Yes Enter up to three values. One uplink value for each adjacent pair of codec modes in ACS. Enter AMR Full Rate initial codec mode: Yes The value must be one of the rates included in the Active Codec Set. Prompt displays if the ACS contains more than one codec mode. and the mode specified is 0 or 2. Enter AMR Full Rate downlink adaptation hysteresis for frequency hopping: Yes Enter up to three values.chg_acs_params Chapter 2: Device/function related commands Table 2-17 Full Rate prompts for the chg_acs_params command (Continued) Prompt Required Enter AMR Full Rate downlink adaptation thresholds for frequency hopping: Yes Enter up to three values. Prompt displays if the ACS contains more than one codec mode. Prompt displays if the ACS contains more than one codec mode. see Table 2-14) Prompt displays if the AMR feature is unrestricted. One value for each adjacent pair of codec modes in ACS. Prompt displays if the ACS contains more than one codec mode. the BTS type is AMR-capable. Prompt displays if the ACS contains more than one codec mode. One downlink value for each adjacent pair of codec modes in ACS. Prompt displays if the ACS contains more than one codec mode. One downlink value for each adjacent pair of codec modes in ACS. One value for each adjacent pair of codec modes in ACS. Enter AMR Half Rate uplink adaptation thresholds: Yes Enter up to three uplink threshold values in order of descending C/I estimation. Enter AMR Half Rate downlink adaptation thresholds: Yes Enter up to three downlink threshold values in order of descending C/I estimation. Prompt displays if the ACS contains more than one codec mode. One uplink value for each adjacent pair of codec modes in ACS. Enter AMR Half Rate uplink adaptation hysteresis: Yes Enter up to three uplink hysteresis values. 2-66 GMR-01 68P02901W23-P 23 Feb 2004 . One uplink value for each adjacent pair of codec modes in ACS. Enter AMR Half Rate initial codec mode: Yes The value must be one of the rates included in the Active Codec Set. Table 2-18 Value Definition Conditions Half Rate prompts for chg_acs_params command Prompt Required Value Definition Conditions Enter AMR Half Rate active codec set: Yes Up to four codec mode values (codec rates) are entered in order of descending bit-rate (ascending field value 0 to 7. Enter AMR Half Rate downlink adaptation hysteresis: Yes Enter up to three downlink hysteresis values. Prompt displays if the ACS contains more than one codec mode. and the mode specified is 0 or 2. Prompt displays if the ACS contains more than one codec mode. One value for each adjacent pair of codec modes in ACS. 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 AMR AMR AMR AMR AMR AMR AMR AMR AMR 68P02901W23-P 23 Feb 2004 Half Half Half Half Half Half Half Half Half Half Rate Rate Rate Rate Rate Rate Rate Rate Rate Rate active codec set:2 3 4 5 intial codec mode:1 uplink adaptation thresholds:40 30 20 uplink adaptation hysteresis:5 8 8 downlink adaptation thresholds:41 31 21 downlink adaptation hysteresis:4 4 4 uplink adaptation thresholds for frequency hopping:38 28 21 uplink adaptation hysteresis for frequency hopping:1 1 1 downlink adaptation thresholds for frequency hopping:40 30 20 downlink adaptation hysteresis for frequency hopping:1 1 1 2-67 GMR-01 . Prompt displays if the ACS contains more than one codec mode. Enter AMR Half Rate uplink adaptation hysteresis for frequency hopping: Yes Enter up to three values. One value for each adjacent pair of codec modes in ACS. Value Definition Conditions 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. Enter AMR Half Rate downlink adaptation thresholds for frequency hopping: Yes Enter up to three values. One value for each adjacent pair of codec modes in ACS. Prompt displays if the ACS contains more than one codec mode.Technical Description BSS Command Reference Table 2-18 chg_acs_params Half Rate prompts for chg_acs_params command (Continued) Prompt Required Enter AMR Half Rate uplink adaptation thresholds for frequency hopping: Yes Enter up to three values. Prompt displays if the ACS contains more than one codec mode. Enter AMR Half Rate downlink adaptation hysteresis for frequency hopping: Yes Enter up to three values. One value for each adjacent pair of codec modes in ACS. chg_acs_params Chapter 2: Device/function related commands Enter AMR Half Rate active codec set: 4 COMMAND ACCEPTED References Related commands "disp_acs" on page 2-193. 2-68 GMR-01 68P02901W23-P 23 Feb 2004 . 1 A5/1 2 A5/2 3 A5/3 2-69 GMR-01 . Security level 2 Supported by OMC-R GUI Yes Command type B (operator actions required) Prerequisites The encryption feature must be unrestricted. 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: 68P02901W23-P 23 Feb 2004 Value GSM Algorithm 0 No encryption. Operator actions The encryption feature must be activated first. To include an algorithm in the priority list. This command does not work at a BTS site. Enter this command at the BSC only. any algorithms listed after 0 are ignored.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. Contact the OMC-R for help. it must be enabled with the associated database parameter (option_alg_a5_1 through option_alg_a5_7). the algorithms ordered as follows: A5/1. A5/2: 2-70 GMR-01 68P02901W23-P 23 Feb 2004 .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. 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. 68P02901W23-P 23 Feb 2004 2-71 GMR-01 . "chg_element" on page 2-94. 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-191. Contact the OMC-R for help. Security level 2 Supported by OMC-R GUI Yes Command type A (no operator actions) Prerequisites A user at the OMC-R must rlogin to a site before an audit can be scheduled. • Audits of similar devices run sequentially. • Audits of different devices run in parallel. the audit of one device must end before the second device audit can begin. For example.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. the system audits all GPROCs at a site sequentially. 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 GMR-01 68P02901W23-P 23 Feb 2004 . This command does not work at a BTS site. If a log exists from a previous audit. Only one audit may be run at a time. Audits can run in parallel or in series. That is. For example. That is. the system can audit different devices at the same time. Enter this command only at the BSC. Use the device_audit command to turn the audits off. audits of the DRI and GCLK would run in parallel. it is overwritten with the log created by the current audit. {4040} or a specified PCU at a GPRS site. 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-P 23 Feb 2004 2-73 GMR-01 . 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. pcu_0 to pcu_2 {4040} PCU device_name Name that uniquely identifies the device. BTS.Technical Description BSS Command Reference chg_audit_sched Specifies the audit location: 0 or bsc BSC 1 to 120 BTS pcu. and PCU int_lpbk Internal loopback KSW self_test all RXCDR at a remote transcoding BSC All BSC and BTS only start_time_hour Start time hour (00 to 23) start_time_min Start time minutes (00 to 59). Alternatively multiple disp_element commands can be used as listed below. 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 DHP safe test audit TDM safe test audit continuously every 10 minutes once a day at 1:00 am BSP safe test audit BTP safe test audit continuously every 10 minutes MSI safe test audit continuously every 1 minute DRI safe test audit continuously every 30 minutes SITE safe test audit AXCDR safe test audit continuously every 10 minutes 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.chg_audit_sched Chapter 2: Device/function related commands 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. The start_time and end_time must not 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. Device scheduling defaults Table 2-19 lists the device scheduling defaults. 2-74 GMR-01 68P02901W23-P 23 Feb 2004 . <index> <location> Refer to the description of the sap_audit_type parameter. 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. Examples Example 1 In this example.<index> <location> Refer to the description of the sap_end_time parameter. The following command string format displays the device_type scheduled for a device: disp_element sap_device_type. The following command string format displays the start_time_hour and start_time_min scheduled for a device: disp_element sap_start_time. 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. 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-P 23 Feb 2004 2-75 GMR-01 .<index> <location> Refer to the description of the sap_start_time.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_device_type parameter. "device_audit" on page 2-184. "query_audits" on page 2-407.chg_audit_sched Chapter 2: Device/function related commands 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. 2-76 GMR-01 68P02901W23-P 23 Feb 2004 . "site_audit" on page 2-438. This is an example of GPRS range scheduling: {4040} chg_audit_sched pcu_0 msi safe 9 0 17 30 0 45 Where: is: pcu_0 {4040} 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. Prerequisites None Operator actions Respond to the dependent parameter prompts associated with the cell element being modified. This then changes the value of the specified element for all available cells in the system. Enter this command at the BSC only. Contact the OMC-R for help. Prompts are presented for dependent cell parameters where necessary.<index>] <value> <cell_desc> chg_cell_element <location> <element> [. element The cell parameter to be changed 68P02901W23-P 23 Feb 2004 2-77 GMR-01 . Format Syntax chg_cell_element [<location>] <element> [. Security level 2 Supported by OMC-R GUI Yes Command type Dependent upon the database parameter being changed.<index>] <value> all Input parameters location The location can also be entered as all.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 does not work at a BTS site. This command supports only non-statistical cell elements. If this is used <location> or all must also be used for the site. PCS1900). The cell_desc can also be a cell name created using the cell_name command. . if any. cell_desc The GSM Cell ID of the affected cell. value The value being assigned to the element. DCS1800. it must be placed inside double quotation marks. Only PCS1900 systems can use a three digit MNC. EGSM. When the cell name is entered. index The index of the element being changed.chg_cell_element Chapter 2: Device/function related commands The all option does not work for the coincident_mb parameter. Examples Example 1 {4322} In this example. With some parameters all may be entered. The format for the GSM Cell ID depends on: • The system used (PGSM. See the individual parameter descriptions. This can optionally be preceded by cell_name=. the alt_qual_proc parameter is changed: chg_cell_element alt_qual_proc 0 5 4 3 2 1 61986 34944 Where: is: alt_qual_proc 2-78 GMR-01 cell element being changed 68P02901W23-P 23 Feb 2004 . • Whether the seven parameter GSM Cell ID format or the four parameter GSM cell id format has been enabled. This command responds to the shortened input parameter cell= allowing entry of either the cell_number or the cell_name without further definition. This can optionally be preceded by cell_number=. Technical Description BSS Command Reference chg_cell_element Where: is: 0 new value for alt_qual_proc 5 4 3 2 1 61986 34944 cell_desc System response Enter Enter Enter Enter Enter Enter Enter Enter Enter Enter Enter Enter Enter Enter Enter Enter Enter Enter RSS RSS RSS RSS RSS RSS RSS RSS RSS RSS RSS RSS RSS RSS RSS RSS RSS RSS handover handover handover handover handover handover handover handover handover handover handover handover handover handover handover handover handover handover threshold threshold threshold threshold threshold threshold threshold threshold threshold threshold threshold threshold threshold threshold threshold threshold threshold threshold l_rxqual_ul_p_amr_fr: 200 l_rxqual_ul_h_amr_fr: 200 l_rxqual_dl_p_amr_fr: 200 l_rxqual_dl_h_amr_fr: 200 l_rxqual_ul_p_amr_hr: 200 l_rxqual_ul_h_amr_hr: 200 u_rxqual_ul_p_amr_hr: 150 l_rxqual_dl_p_amr_hr: 200 u_rxqual_dl_h_amr_hr: 200 l_rxqual_ul_p_amr_hr: 150 l_rxqual_ul_h_hopping_amr_fr: l_rxqual_ul_p_hopping_amr_fr: l_rxqual_dl_h_hopping_amr_fr: l_rxqual_dl_p_hopping_amr_fr: l_rxqual_ul_h_hopping_amr_hr: l_rxqual_ul_p_hopping_amr_hr: l_rxqual_dl_h_hopping_amr_hr: l_rxqual_dl_p_hopping_amr_hr: 500 250 500 500 500 500 500 500 COMMAND ACCEPTED 68P02901W23-P 23 Feb 2004 2-79 GMR-01 . The format for the GSM Cell ID depends on: • The system used (PGSM. PCS1900) • Whether the seven parameter GSM Cell ID format or the four parameter GSM Cell ID format has been enabled. DCS1800. 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. below. PGSM and DCS1800 systems still use the 2 digit MNC. d either: • the second digit of the PCS1900 MNC • the first digit of the PGSM. EGSM or DCS1800 MNC Only PCS1900 systems use a three digit MNC. Only PCS1900 systems can use a three digit MNC. EGSM. The format to enter PGSM. 68P02901W23-P 23 Feb 2004 .chg_cell_id Chapter 2: Device/function related commands chg_cell_id Description The chg_cell_id command changes the GSM Cell ID of a specified cell. beginning with d. EGSM or DCS1800 MNC either: e 2-80 GMR-01 • the third digit of the MNC • the third digit of the PCS1900 MNC • the second digit of the PGSM. A warning message is presented when this command is successfully entered. Security level 2 Supported by OMC-R GUI Yes Command type A (no operator actions) Prerequisites None Enter this command at the BSC only. DCS1800. The format for the GSM Cell ID depends on: • The system used (PGSM. new_cell_desc New GSM Cell ID of the cell. PCS1900) • Whether the seven parameter GSM Cell ID format or the four parameter GSM Cell ID format has been enabled. When the cell name is entered. Only PCS1900 systems can use a three digit MNC. it must be placed inside double quotation marks. EGSM. This command does not work at a BTS site. 68P02901W23-P 23 Feb 2004 2-81 GMR-01 . The old_cell_desc can also be a cell name created using the cell_name command.Technical Description BSS Command Reference chg_cell_id Where: is: f the LAC (Local Area Code) g the CI (Cell Identity) When the GSM Cell ID is changed using this command. Contact the OMC-R for help. it is not propagated throughout the CM database. Format Syntax chg_cell_id <old_cell_desc> <new_cell_desc> Input parameters old_cell_desc Original Cell ID of the cell. the affected cell is identified using the cell_name “london-north": chg_cell_id "london-north" 5 4 3 2 1 61985 37982 Where: is: london-north old_cell_desc (using cell name) 5 4 3 2 1 61985 37982 new_cell_desc System response WARNING: Verify OML state to ensure change propagated to all neighbors. 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. 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 WARNING: Verify OML state to ensure change propagated to all neighbors. COMMAND ACCEPTED 2-82 GMR-01 68P02901W23-P 23 Feb 2004 . COMMAND ACCEPTED Example 2 In this example. COMMAND ACCEPTED Example 3 In this example.chg_cell_id Chapter 2: Device/function related commands Examples Example 1 In this example. 68P02901W23-P 23 Feb 2004 2-83 GMR-01 . "disp_cell" on page 2-205. "cell_name" on page 2-58. "copy_cell" on page 2-156.Technical Description BSS Command Reference chg_cell_id References Related commands "add_cell" on page 2-21. "del_cell" on page 2-168. 2-84 GMR-01 68P02901W23-P 23 Feb 2004 . flow_control Selects the CSFP flow control value. The location values that may be entered for this element are 0 (or bsc) to 120. only that CSFP downloads can proceed at the maximum throughput rate. The location values that may be entered for this element are 1 to 120. The CSFP algorithm selects the CSFP algorithm method used when configuring CSFPs via the configure_csfp command or via the OMC-R. This command does not work at a BTS site. A value of 100 does not mean the link will be 100% utilized during the download. Format Syntax chg_csfp <element> <value> <location> Input parameters element Two selections are available: algorithm Selects the CSFP algorithm method. 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. Contact the OMC-R for help. Security level 2 Supported by OMC GUI Yes Command type A (no operator actions) Prerequisites None Enter this command at the BSC only.chg_csfp Chapter 2: Device/function related commands chg_csfp Description The chg_csfp command changes the CSFP algorithm or flow control values. location Specifies the element location.Technical Description BSS Command Reference chg_csfp value Either an algorithm or a flow control value may be entered but not both. 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 flow_control 10 3 Where: 68P02901W23-P 23 Feb 2004 is: flow_control element 10 flow control percentage 3 location 2-85 GMR-01 . This is the default value for this algorithm. 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%. Selectable in a range from 10 to 100 in steps of 10. The value that may be used is dependent upon the selected element: algorithm flow_control 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. The default value is 10%. chg_csfp Chapter 2: Device/function related commands System response COMMAND ACCEPTED References Related command "disp_csfp" on page 2-225 2-86 GMR-01 68P02901W23-P 23 Feb 2004 . Technical Description BSS Command Reference chg_dte chg_dte Description The chg_dte command assigns the DTE addresses to allow connections between the BSC and the OMC-R or CBC. Contact the OMC-R for help. 68P02901W23-P 23 Feb 2004 2-87 GMR-01 . 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 Supported by OMC-R GUI Yes Command type B (Operator actions required) Prerequisites The OML link affected by this command must be reset for the changes to take effect. Enter this command at the BSC only. Operator actions Reset the OML after changes have been entered with this command. 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. This command does not work at a BTS site. the DTE address of the 3rd BSC is changed to 12345: 2-88 GMR-01 68P02901W23-P 23 Feb 2004 . address_length The number of valid address bytes that are added to the list. 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.chg_dte Chapter 2: Device/function related commands Format Syntax chg_dte <link> [<link_num>] <address_length> [<address_byte>] . address_byte The value of a particular address byte. An address_byte value is not required when the address_length is zero. Examples Example 1 In this example. omcr OMC-R cbc CBC bcs_cbc The communication link between the BSC and CBC. . The range of values is 0 to 9. A link_num is required for cbc and bsc_cbc if the address_length is 0. The number of address bytes entered must equal the number entered for the address_length parameter. The range of values is 0 to14. [<address_byte>] Input parameters link Specifies the link location: bsc The communication link between the BSC and the OMC-R. . Technical Description BSS Command Reference chg_dte 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 Address Address Address Address addresses: #0: 23466811570001 #1: 41224643654225 #2: 31777619565738 #3: 12345 OMCR DTE addresses: Address #0: 23466823020041 Address #1: 24885902667864 Address #2: 38959620015151 Address #3: 122876465567 Address #4: 2301 Address #5: 6811570001 Address #6: Zero length address Address #7: Zero length address COMMAND ACCEPTED 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 Address Address Address Address addresses: #0: 23466811570001 #1: 41224643654225 #2: 31777619565738 #3: 12345 OMCR DTE addresses: Address #0: 23466823020041 Address #1: 24885902667864 Address #2: Zero length address Address #3: 122876465567 Address #4: 2301 Address #5: 6811570001 68P02901W23-P 23 Feb 2004 2-89 GMR-01 . chg_dte Chapter 2: Device/function related commands Address #6: Address #7: Zero length address Zero length address COMMAND ACCEPTED References Related command "disp_dte" on page 2-229. 2-90 GMR-01 68P02901W23-P 23 Feb 2004 . Each pair includes a severity level and up to 24 text characters for each BSS. Valid values are: 0 investigate 1 critical 68P02901W23-P 23 Feb 2004 2-91 GMR-01 . This command does not work at a BTS site. alarm_severity_level Specifies the alarm level for a specific alarm string. The range of values is 0 to 33. Security level 2 Supported by OMC-R GUI Yes Command type A (no operator actions) Prerequisites The EAS device must be equipped before a severity level and text characters can be assigned. Enter this command at the BSC only. The EAS alarm table contains 34 indexed pairs. Each pair corresponds to the output of an equipped EAS/PIX module. This command permits individual EAS alarms to be reported as text strings. Contact the OMC-R for help.Technical Description BSS Command Reference chg_eas_alarm chg_eas_alarm Description The chg_eas_alarm command initializes and modifies the EAS (External Alarm System) alarm table. 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. Example In this example. The alarm text string may be a maximum of 24 characters. including spaces. an alarm string of door open is assigned to the first index (1) of the alarm string table. This text string contains nine characters. 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 2-92 GMR-01 68P02901W23-P 23 Feb 2004 .chg_eas_alarm Chapter 2: Device/function related commands 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. 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. The alarm string must be entered inside double quotation marks. the alarm is classified minor (3). "disp_element" on page 2-231.Technical Description BSS Command Reference Table 2-22 chg_eas_alarm 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 32 TDU Customer Defined 2 33 TDU Customer Defined 3 Related commands "chg_element" on page 2-94. 68P02901W23-P 23 Feb 2004 2-93 GMR-01 . Format Syntax chg_element <element_name> [.chg_element Chapter 2: Device/function related commands chg_element Description The chg_element command modifies database parameters in the CM database. Security level 2 Supported by OMC-R GUI Yes Command type Dependent on the database parameter being changed. 2-94 GMR-01 68P02901W23-P 23 Feb 2004 . index1 Some database parameters require an index. This command does not work at a BTS site. A comma is required before the index number.<index2>] <element_value> <location> [<cell_desc>] chg_element <element_name> [.<index1>][.<index1>][.<index2>] <element_value> all chg_element <element_name> [. Prerequisites None Operator actions Operator actions depend on the database parameter being changed.<index1>][. They are highlighted with an asterisk in the table in the Related Information section. Enter this command at the BSC only.<index2>] <element_value> <location> all Input parameters element_name String identifying the database parameter in the CM database. Details are given in the "CM database parameters presentation" on page 5-2. Contact the OMC-R for help. A comma is required before the index number. value New value for the element_name.Technical Description BSS Command Reference chg_element index2 Database parameters requiring a second index are highlighted in the table shown in the Related Information section. • Not allowed outside of SYSGEN mode for type B elements. preceded by cell_number=. 2-95 GMR-01 . it must be placed inside double quotation marks. pcu_0 to pcu_2 {4040} PCU all Specifies all sites. and be preceded by cell_name=. When the cell name is entered. Only PCS1900 systems can use a three digit MNC. EGSM. This command responds to the shortened input parameter cell= allowing entry of either the cell_number or the cell_name without further definition. Restrictions on the use of all locations are: • Allowed outside of SYSGEN mode only for type A elements. location Specifies the site location: 0 or bsc BSC 1 to 120 BTS pcu. The value all is also a valid input for the cell_desc. Restrictions on the use of all cells are: • 68P02901W23-P 23 Feb 2004 Not allowed for elements that cause the site to reset. • Allowed for BY_CELL and BY_SITE elements only. which changes element_name to value for all cells at the specified location. DCS1800. cell_desc GSM Cell ID of the cell to be changed. The format for the GSM Cell ID depends on: • The system used (PGSM. The name of the cell created using the cell_name command may be entered in place of the cell_number. Normal and Weighted Distribution statistical database parameter names require the use of index2. No other parameters require it. index2 may only be used with statistical database parameter names. PCS1900) • Whether the seven parameter GSM Cell ID format or the four parameter GSM Cell ID format has been enabled. Refer to the appropriate documentation for detailed explanations of these procedures. Examples The following examples only demonstrate how specific parameters are changed using the chg_element command. Selecting n or N causes the system to abandon the command without changing the parameter. 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 2-96 GMR-01 68P02901W23-P 23 Feb 2004 . 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. the bsic value is changed to 1 for site number 0. the maximum number of retransmissions (max_retran) value is changed to 3 for site number 0. • Sites that are not equipped are not affected.n=no)? y COMMAND ACCEPTED Selecting y or Y causes the system to make the change and reset.chg_element Chapter 2: Device/function related commands • Not allowed outside of SYSGEN mode. • Allowed for BY_CELL and BY_SITE elements only. Example 2 In the next example. Example 1 In this example. The examples shown may be part of a larger procedure. 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 68P02901W23-P 23 Feb 2004 element_name 2-97 GMR-01 . the severity of EAS alarm 6 at location 0 is changed to level 2: chg_element eas_severity.Technical Description BSS Command Reference chg_element 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. chg_element Chapter 2: Device/function related commands Where: is: 0 value 0 location System response COMMAND ACCEPTED Example 6 In this example. the following text is displayed: COMMAND ACCEPTED Example 7 In this example. 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 BSC must be reset to initiate the change. 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 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 2-98 GMR-01 68P02901W23-P 23 Feb 2004 . the affected cell is identified using the cell_name “london-north": chg_element bsic 1 1 cell "london-north" Where: 68P02901W23-P 23 Feb 2004 is: bsic element_name 1 value 1 location london-north cell_name 2-99 GMR-01 . the local_maintenance parameter is enabled to permit local interaction with the BSS. chg_element local_maintenance 1 0 Where: is: local_maintenance element_name 1 value 0 location System response COMMAND ACCEPTED Example 10 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 system must be in the SYSGEN ON mode to change the local_maintenance parameter. interaction with the system is available only from the OMC.Technical Description BSS Command Reference chg_element Example 8 In this example. When the local_maintenance parameter is disabled. Selecting n or N causes the system to abandon the command without changing the parameter. 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-231. 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 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. Example 11 In this example. Selecting n or N causes the system to abandon the command without changing the parameter.n=no)? y COMMAND ACCEPTED Selecting y or Y causes the system to make the change and reset.n=no)? y COMMAND ACCEPTED Selecting y or Y causes the system to make the change and reset. the base station identity code (bsic) value is changed to 1 for PCS 1900 site number 0.chg_element Chapter 2: Device/function related commands 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. 2-100 GMR-01 68P02901W23-P 23 Feb 2004 . Hopping verification is run by this command on all cells in the specified site. Each cell takes about 90 seconds to finish the hopping reconfiguration. an error message displays. disabled or changed an enabled hopping system which is synthesizer hopping through the BCCH RTF. provided that all FHIs for the cell are disabled. It is also possible to mix non-hopping cells and hopping cells at the same site. or from no hopping to synthesizer hopping. The operator can change hopping support from no hopping to baseband hopping. When the system accepts the chg_hop_params command for a particular cell.Technical Description BSS Command Reference chg_hop_params chg_hop_params Description The chg_hop_params command permits changing multiple hopping parameters for a site at one time. Synthesizer hopping and baseband hopping can be enabled in different cells at the same site. If this warning message occurs. 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. A warning message is presented if duplicated frequencies are entered. it does not allow both at the same time. 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. If this is attempted. The system ignores the duplicated frequencies. the command must be re-entered without the duplication. or vice versa. even if the cells in the site are not specifically modified. The operator can abort the command to prevent a site reset. The changes are verified outside of SYSGEN and when exiting SYSGEN mode. the system rejects other chg_hop_params commands until the system reconfiguration due to the first command is complete. {23658} An EGPRS RTF cannot baseband hop in the same FHIs as non-EGPRS RTFs Security level 2 Supported by OMC-R GUI Yes 68P02901W23-P 23 Feb 2004 2-101 GMR-01 . If the range is less than 112. To change multiple hopping parameters at a BTS site. there is a limit of 18 frequencies when the frequency range is set to more than 256. This command can be entered only at the BSC. In a GSM 850 cell. contact the OMC-R for help. • Synthesizer Frequency Hopping systems in Extended Range cells must have the FHIs for the the BCCH carrier timeslots set to “0xffh" (255). the ARFCN range is 128 to 251. 2-102 GMR-01 68P02901W23-P 23 Feb 2004 . If the range is more than 112. 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. only 29 frequencies are allowed. {23658} The master cabinet at the site must be a Horizon II macro in order for an EGPRS RTF to baseband hop. only 64 frequencies are allowed. The system does not verify hopping systems inside SYSGEN until SYSGEN is off. 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. Synthesizer hopping is not allowed in a cell if a Remotely Tuneable Combiner is equipped at the cell.chg_hop_params Chapter 2: Device/function related commands Command type A (no operator actions) Prerequisites If hopping_systems verification fails the system rejects this command outside of SYSGEN. The system rejects this command for microsites that are not equipped with Horizonmicro or Horizoncompact cabinets. • Baseband and synthesizer hopping systems can only be configured among timeslots of the same type (such as Extended or Normal). The cell_desc can also be a cell name created using the cell_name command. This can optionally be preceded by cell_number=. If neither is entered. 68P02901W23-P 23 Feb 2004 2-103 GMR-01 . The numbers in the columns refer to the notes that follow. EGSM. Table 2-23 shows the baseband and synthesizer frequency hopping restrictions on the setting of the chg_hop_params command. The format for the GSM Cell ID depends on: • The system used (PGSM. it must be placed inside double quotation marks. all cells at the location will be assumed. Only PCS1900 systems can use a three digit MNC. DCS1800. location Specifies the site location: 0 or bsc BSC 1 to 120 BTS cell_desc The GSM Cell ID of the affected cell. This command responds to the shortened input parameter cell= allowing entry of either the cell_number or the cell_name without further definition.Technical Description BSS Command Reference chg_hop_params 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. PCS1900) • Whether the seven parameter GSM Cell ID format or the four parameter GSM Cell ID format has been enabled. This can optionally be preceded by cell_name=. When the cell name is entered. 3 Yes Yes2. The reference to the Frequency Hopping Indicator (FHI)) is only to that FHI assigned to the BCCH RTF. 3. Performs hopping verification.3. 5. 2. All other FHIs in the cell are treated like the SFH column. Causes the affected site to be reset.chg_hop_params Chapter 2: Device/function related commands Table 2-23 Baseband and Synthesizer frequency hopping restrictions FHI state Snythesizer Frequency (SFH) Baseband E = Enabled D = Disabled E D E SFH through BCCH D E D Enable FHI Yes Yes2. 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. 4.4 Disable FHI Yes3 Yes Yes3 Yes Yes4 Yes Change MA No5 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. 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 Mobile allocation (ARFCNs) for FHI 3: 20 60 90 HSN for FHI 3: Hopping systems (FHIs) to be modified in cell 0 0 1 2 3 1 12 2-104 GMR-01 68P02901W23-P 23 Feb 2004 . Notifies the Cell Resource Machine (CRM) of the changes made.5 Yes2 Yes2.3 Yes Yes2. System response Hopping systems (FHIs) to be modified in cell 0 0 1 0 1 1 (0x0001) 3 (0x0003) (RETURN=no change for this cell):0 Hopping support:0 FHI 0 status (enable/disable): Mobile allocation (ARFCNs) for FHI 0: HSN for FHI 0: WARNING: The site will be reset if the operator enabled. n=no) ? HOPPING VERIFICATION RESULTS 68P02901W23-P 23 Feb 2004 2-105 GMR-01 . disabled or changed an enabled hopping system which is synthesizer hopping through the BCCH RTF. n=no) ?" Responding n to the Are you sure? prompt aborts the command. 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. 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 Hopping systems (FHIs) to be modified in cell 0 0 1 0 1 1 21 “cellname3" (RETURN=no change for this cell): 2 0 Hopping support: 2 FHI 2 status (enable/disable): 0 Mobile allocation (ARFCNs) for FHI 2: HSN for FHI 2: WARNING: The site will be reset if the operator enabled. Are you sure (y=yes.Technical Description BSS Command Reference "cellname1" chg_hop_params (RETURN=no change for this cell): Hopping systems (FHIs) to be modified in cell 0 0 1 3 2 1 1 (RETURN=no change for this cell): 2 0 Hopping support: 2 FHI 0 status (enable/disable): 1 Mobile allocation (ARFCNs) for FHI 0: 21 31 71 HSN for FHI 0: 1 FHI 2 status (enable/disable): 1 Mobile allocation (ARFCNs) for FHI 2: 21 61 91 HSN for FHI 2: "WARNING: The site will be reset if the operator enabled. disabled or changed an enabled hopping system which is synthesizer hopping through the BCCH RTF. Are you sure (y=yes. Are you sure (y=yes. n=no) ? Example 3 In this example. disabled or changed an enabled hopping system which is synthesizer hopping through the BCCH RTF. 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.chg_hop_params Chapter 2: Device/function related commands ============================ 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. disabled or changed an enabled hopping system which is synthesizer hopping through the BCCH RTF. 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 Hopping systems (FHIs) to be modified in cell 0 0 1 0 1 1 (0001h) 1021 (03FDh) (RETURN=no change for this cell):1 2 Hopping support: 2 FHI 1 status (enable/disable): enable Mobile allocation (ARFCNs) for FHI 1: HSN for FHI 1: FHI 2status (enable/disable): enable 2-106 GMR-01 68P02901W23-P 23 Feb 2004 . n=no) ? y HOPPING VERIFICATION RESULTS ============================ 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. Are you sure (y=yes. COMMAND REJECTED Example 5 {23658} In this example. 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 FHI 1 status (enable/disable): Mobile allocation (ARFCNs) for FHI 1: HSN for FHI 1: WARNING: The site will be reset if the operator enabled. COMMAND REJECTED Example 4 {23658} In this example. “x" indicates a value supplied by the system. COMMAND REJECTED References Related information Table 2-24 lists the prompts for the chg_hop_params command. Are you sure (y=yes. n=no) ? y HOPPING VERIFICATION RESULTS ============================ Site 1: GSM Cell: 001 01 1 (0001h) 1021 (03FDh) -------------------------------------------------ERROR: EGPRS and non-EGPRS carriers cannot have the same FHI. Table 2-24 chg_hop_params prompts Prompt Range Default Hopping support: 0 to 2 where: 0 = No hopping in this cell 1 = Synthesizer hopping 2 = Baseband hopping See Note below. 0 FHI x status (enable/disable): 0 or 1 where: 0 = disable the hopping system 1 = enable the hopping system 0 68P02901W23-P 23 Feb 2004 2-107 GMR-01 .Technical Description BSS Command Reference chg_hop_params 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. chg_hop_params Chapter 2: Device/function related commands Table 2-24 chg_hop_params prompts (Continued) Prompt Range Mobile allocation (ARFCNs) for FHI x: Default ARFCN depends on the frequency type for the cell. 0). or • 975 to 1023 Current value If using EGSM. If the cell is PCS1900 the range is 512 to 810. 957 to 1023 17 0. If the cell is PGSM the range is 1 to 124. Table 2-25 Cell frequencies/mobile allocation Frequencies of the cell (ARFCNs used) Maximum number of frequencies in the mobile allocation 1 to 124 64 975 to 1023 49 1 to 124. 1 to 124. The system rejects the chg_hop_params command if: (1) hopping support: = 1 and the Synthesizer Hopping feature is restricted. 2-108 GMR-01 68P02901W23-P 23 Feb 2004 . If the cell is DCS1800. For GSM850. the ARFCN range is 128 to 251.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. 1 to 124 17 0.08 Specification Annex J and Cell Channel Description. and 1 to 63 is random Current value Hopping support may not be 0 if any FHIs are enabled. If the cell is EGSM the range is either: • 1 to 124. 975 to 1023 17 Related command "disp_hopping" on page 2-259. all of the specified ARFCNs must be in the lower range (1 to 124) or the higher range (975 to 1023. the range is 512 to 885. HSN for FHI x: 0 to 63 where: 0 is cyclic. 975 to 1023 16 0. FHI must be disabled before changing hopping support Synthesizer hopping FHI is disabled Command allowed Command allowed Command allowed Command allowed Command allowed Synthesizer through BCCH hopping FHI is enabled Command allowed. will reset the site Command allowed Command allowed. will reset the site Command rejected. FHI must be disabled before changing hopping support Baseband hopping FHI is disabled Command allowed Command allowed. Table 2-26 Restrictions on related commands Current hopping support and FHI status chg_hop_params command change HSN change hopping support disable FHI enable FHI change MA Baseband hopping FHI is enabled Command allowed Command allowed Command rejected. Command rejected. MA can change so long as the new MA contains all the ARFCNs of the equipped RTFs in the hopping system. will reset the site Command allowed Command allowed Command allowed 68P02901W23-P 23 Feb 2004 2-109 GMR-01 . Command allowed Command allowed Command allowed Synthesizer hopping FHI is enabled Command allowed Command allowed Command Command allowed allowed. Disable the FHI and equip the RTF before changing the MA Command allowed. Command rejected. cannot change MA of an enabled FHI. FHI must be disabled before changing hopping support Synthesizer through BCCH hopping FHI is disabled Command allowed Command allowed.Technical Description BSS Command Reference chg_hop_params Table 2-26 lists the restrictions on related commands. will reset the site Command allowed. KSW 0 1. KSW 1 0. The KSWX cards for TDM 1 are located in slots U9. Each portion is handled by a different KSW pair. from which the operator can abort the command. The KSWX in slot U7 mirrors the connections of the KSWX in slot U23. The KSWX cards are required in each cage with a KSW pair. The command may only be issued for InCell sites. TDM 0 and TDM 1. Highway Portion 3 TDM timeslots 3072 to 4095 handled by KSW pair 3. The first identifier of a KSW is the portion of the TDM highway handled by that KSW. Two TDM highways are supported. Only one command is required per KSW pair because the fibre optic connections for TDM 0 and TDM 1 match. A warning displays when coming out of SYSGEN mode if each set of TDM highway identifiers are not unique in each cage. Security level 2 Supported by OMC-R GUI Yes Command type B (operator actions required) Prerequisites See the Service Manual BSC/RXCDR (68P02901W38) for information regarding the hardware layout of the KSW pairs. The KSWX fiber optic connections for TDM 1 must match the KSWX fiber optic connections for TDM 0. U22. The chg_ksw_config command specifies the fibre optic connections between the KSWX cards. U8. One TDM highway is active and the other is a redundant standby. The KSWX cards for TDM 0 are located in slots U21. KSWs are connected through the EXP KSWX cards to form a larger switching network. KSW 2 0. The highway portions are defined as: Highway Portion 0 TDM timeslots 0 to 1023 handled by KSW pair 0. The KSWX in slot U8 mirrors the connections of the KSWX in slot U22. and U23. KSW 1 1. The KSWX in slot U9 mirrors the connections of the KSWX in slot U21. and KSW 3 0 may be interconnected to form TDM 0. and U7. The command does not apply to M-Cell sites. Highway Portion 2 TDM timeslots 2048 to 3071 handled by KSW pair 2. The TDM highway of a site may consist of up to four portions. Expansion KSW (KSWX) cards are used to interconnect the KSW pairs. A chg_ksw_config command is required for each KSW pair equipped at the site when more than one KSW pair is equipped. A warning prompt displays when this command is entered. and KSW 3 1 may be interconnected to form TDM 1. KSW 0 0.chg_ksw_config Chapter 2: Device/function related commands chg_ksw_config Description The chg_ksw_config command indicates how KSWs are physically connected when two or more KSW pairs are equipped at a site. The second KSW identifier indicates to which TDM highway the KSW belongs. Highway Portion 1 TDM timeslots 1024 to 2047 handled by KSW pair 1. 2-110 GMR-01 68P02901W23-P 23 Feb 2004 . KSW 2 1. kswx_connected_to_hwy_1 The KSWX pair that connects this KSW pair to highway portion 1.Technical Description BSS Command Reference Operator actions chg_ksw_config Check the information regarding the hardware layout of the KSW pairs. and 3 are not equipped. Valid values are 0 to 3. 3 KSWX cards in slots U23 (EXP KSWX A2) and U7 (EXP KSWX B2). The KSWX pair is in the same cage as the KSW pair being configured. 1 KSWX cards in slots U21 (EXP KSWX A0) and U9 (EXP KSWX B0). The KSWX pair is in the same cage as 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 1 KSW pair 1 corresponds to KSW 1 0 and KSW 1 1 2 KSW pair 2 corresponds to KSW 2 0 and KSW 2 1 3 KSW pair 3 corresponds to KSW 3 0 and KSW 3 1 kswx_connected_to_hwy_0 The KSWX pair that connects this KSW pair to highway portion 0. This parameter is not required if KSW pairs 1. 2 KSWX cards in slots U22 (EXP KSWX A1) and U8 (EXP KSWX B1). 2. 68P02901W23-P 23 Feb 2004 2-111 GMR-01 . KSWX pairs are defined as: 0 The highway portion is the same as the KSW pair being configured. This command may be executed in or out of SYSGEN mode. Respond to the warning prompt after entry of the command. Valid values are 0 to 3. 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 chg_ksw_config commands for configuring the following expanded setup are described.chg_ksw_config Chapter 2: Device/function related commands kswx_connected_to_hwy_2 The KSWX pair that connects this KSW pair to highway portion 2. Valid values are 0 to 3. CAGE 0: KSW 0 0 and KSW 0 1 (KSW Pair 0) are equipped in CAGE 0 KSWX in slot U21 is connected to KSWX in cage 1 slot U21 KSWX in slot U22 is connected to KSWX in cage 2 slot U21 KSWX in slot U23 is connected to KSWX in cage 3 slot U21 KSWX in slot U9 is connected to KSWX in cage 1 slot U9 KSWX in slot U8 is connected to KSWX in cage 2 slot U9 KSWX in slot U7 is connected to KSWX in cage 3 slot U9 CAGE 1: KSW 1 0 and KSW 1 1 (KSW pair 1) are equipped in CAGE 1 KSWX in slot U21 is connected to KSWX in cage 0 slot U21 KSWX in slot U22 is connected to KSWX in cage 2 slot U22 KSWX in slot U23 is connected to KSWX in cage 3 slot U22 KSWX in slot U9 is connected to KSWX in cage 0 slot U9 KSWX in slot U8 is connected to KSWX in cage 2 slot U8 KSWX in slot U7 is connected to KSWX in cage 3 slot U8 CAGE 2: KSW 2 0 and KSW 2 1 (KSW pair 2) are equipped in CAGE 2 KSWX in slot U21 is connected to KSWX in cage 0 slot U22 KSWX in slot U22 is connected to KSWX in cage 1 slot U22 KSWX in slot U23 is connected to KSWX in cage 3 slot U23 KSWX in slot U9 is connected to KSWX in cage 0 slot U8 KSWX in slot U8 is connected to KSWX in cage 1 slot U8 KSWX in slot U7 is connected to KSWX in cage 3 slot U7 CAGE 3: KSW 3 0 and KSWX in slot KSWX in slot KSWX in slot KSW 3 1 (KSW pair 3) are U21 is connected to KSWX U22 is connected to KSWX U23 is connected to KSWX 2-112 GMR-01 equipped in CAGE 3 in cage 0 slot U23 in cage 1 slot U23 in cage 2 slot U23 68P02901W23-P 23 Feb 2004 . Valid values are 0 to 3. kswx_connected_to_hwy_3 The KSWX pair that connects this KSW pair to highway portion 3. The KSWX pair is in the same cage as the KSW pair being configured. This parameter is not required if KSW pairs 2 and 3 are not equipped. The KSWX pair is in the same cage as the KSW pair being configured. Examples Example 1 This example describes the KSWX fiber optic connections for a standard 4 cage expanded BSC with redundancy. This parameter is not required if KSW pair 3 is not equipped. References Related command "disp_element" on page 2-231. kswx_connected_to_hwy_2 0 indicates that the highway number is the same as the KSW pair number. 68P02901W23-P 23 Feb 2004 2-113 GMR-01 . 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. kswx_connected_to_hwy_3 3 indicates that the KSWXs in slot U23 and U7 in the cage with KSW pair 2 connect to the cage with KSW pair 3. the BSC checks to see if a CLKX card has been equipped in the slot. In this example.Technical Description BSS Command Reference chg_ksw_config KSWX in slot U9 is connected to KSWX in cage 0 slot U7 KSWX in slot U8 is connected to KSWX in cage 1 slot U7 KSWX in slot U7 is connected to KSWX in cage 2 slot U7 The commands for configuring the expansion are: chg_ksw_config chg_ksw_config chg_ksw_config chg_ksw_config 0 0 0 0 0 1 2 3 0 1 1 1 1 0 2 2 2 2 0 3 3 3 3 0 For example. 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. If a chg_ksw_config command applies to slot U7. 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. Example 2 Slot U7 can contain a CLKX card or a KSWX card. ksw_pair 2 indicates that this is for KSW pair 2 which is in cage 2. CLKX slot utilization is specified in the GCLK equip command. kswx_connected_to_hwy_1 2 indicates that the KSWXs in slot U22 and U8 in the cage with KSW pair 2 connect to the cage with KSW pair 1. Security level passwords are case sensitive and require 4 to 16 characters. Security level 1 Supported by OMC-R GUI No Command type A (no operator actions) Prerequisites None Format Syntax chg_level Input parameters There are no input parameters since the command is interactive. A security level 2 password is not assigned when the system is initially loaded. 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. 2-114 GMR-01 68P02901W23-P 23 Feb 2004 . Examples Example 1 In the following example.chg_level Chapter 2: Device/function related commands chg_level Description The chg_level command changes the current security level. the security level is changed from level 1 to level 2. A level 2 password may be assigned to limit access to security level 2 commands. Any password longer than 16 characters is truncated at the 16th character. The password is not displayed when entered. Example 3 In the following example. 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.Technical Description BSS Command Reference chg_level Example 2 In the following example. the security level is not changed. 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> Current security level is 3. the security level is changed from level 1 to level 3. 68P02901W23-P 23 Feb 2004 2-115 GMR-01 . References Related command "disp_level" on page 2-264. The new password must contain four or more characters that are different from the ones in the old password. For example. A second test. If the new password is four or more characters longer or shorter than the old password. After the command is entered. The password is not displayed when entered.chg_password Chapter 2: Device/function related commands chg_password Description The chg_password command changes the password for a specific security level. prompts to change the password display. if both passwords are four characters in length. To change a password. Passwords are case sensitive and may be 1 to 16 characters in length. Security level 2 or 3 Supported by OMC-R GUI No Command type A (no operator actions) Prerequisites None Format Syntax chg_password <level> Input parameter level The level for which the password is to be changed must be entered. The new password must be significantly different than the old password. no characters may be common to both passwords for the new password to be considered significantly different. an operator must enter the password associated with the security level to be changed. the chg_password command may be used to change the level 3 passwords. Passwords that are entered with more than 16 characters will be truncated at the 16th character. 2-116 GMR-01 68P02901W23-P 23 Feb 2004 . The value for this parameter is 2 or 3. it is considered significantly different and is accepted immediately. This is determined by first comparing the lengths of the two passwords. examines each character in the two passwords. If the Optional Level 3 Password feature is unrestricted. if required. chg_password System response Enter password: ninety Enter new password: forty Verify new password: fourthly New password and verification password not equal 68P02901W23-P 23 Feb 2004 2-117 GMR-01 . This requires the purchase and implementation of the Level 3 Password feature. 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 passwords would not actually be displayed when entered. the password is changed. 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. The passwords would not actually be displayed when entered.Technical Description BSS Command Reference chg_password Examples Example 1 In the following example. The old and new passwords in this example are for information purposes only. the password is not changed because the verification password was entered incorrectly. The passwords would not actually be displayed when entered. The old and new passwords are shown in this example for information purposes only. The old and new passwords are shown in this example for information purposes only. chg_password Chapter 2: Device/function related commands If the verification password in the example had been entered correctly. "disp_level" on page 2-264. 2-118 GMR-01 68P02901W23-P 23 Feb 2004 . there would have only been a difference of three characters and the command would have failed. 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". References Related commands "chg_level" on page 2-114. Security level 2 Supported by OMC-R GUI Yes Command type B (operator actions required) 68P02901W23-P 23 Feb 2004 2-119 GMR-01 .Technical Description BSS Command Reference chg_rtf_freq chg_rtf_freq Description The chg_rtf_freq command changes the absolute radio frequency channel for a particular RTF. The operator may abort the command at the warning. A long warning prompt is presented when this command is invoked. This operation may cause a carrier to be taken out of service. Calls may be lost if no other carrier is available. • To have different DRI/RTF group identifiers. 2-120 GMR-01 68P02901W23-P 23 Feb 2004 .chg_rtf_freq Chapter 2: Device/function related commands Prerequisites In a synthesizer hopping system: • When hopping is enabled. • 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. the frequency type is managed on a per zone basis. • 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. 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. the ARFCN range for an inner zone RTF is determined by the frequency type as defined by the secondary band. • When the inner_zone_alg parameter is set to 3 (specifying Dual Band). the BSS requires DRI/RTFs within a cell to have different frequency types. 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. • The primary and secondary band frequency types must be allowed by the cabinet(s) to which the DRI(s) in each zone are equipped. • The new frequency may be added when hopping is disabled regardless of whether the frequency is already a hopping frequency. In a Dual Band system: • When the Dual Band Cells option is enabled. • It is not allowed for BCCH RTFs if FHIs are enabled. In a baseband hopping system: • This command is rejected outside SYSGEN ON mode if the RTF has hopping FHIs and any FHIs are enabled. an error message is printed and the command is rejected. Primary band carriers are configured in the outer zone and secondary band carriers are configured in the inner zone. 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. Concentric Cell feature enabled and the power based use algorithm used). 710. 1 to 224. 587. 612. the frequency entered may be limited by the the maximum transmit power (max_tx_bts). 735. Block edges are 512. 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. 685. 610. If the frequency is a block edge ARFCN. 737. Enter this command at the BSC only. and the block edge frequency is defined to be an inner zone carrier with a maximum transmit power level less that 36 dBm. 712. 687. This command does not work at a BTS site. Contact the OMC-R for help. • The inner_zone_alg parameter is set in a chg_cell_element command to value 1 (that is. 585. Respond to the warning prompt presented when this command is entered. 975 to 1023 (EGSM) 512 to 885 (DCS1800) 512 to 810 (PCS1900) 128 to 251 (GSM850) 68P02901W23-P 23 Feb 2004 2-121 GMR-01 . ARFCNs 512 and 810 are always limited. and 810. The range of values is: 1 to 224 (PGSM) 0.Technical Description BSS Command Reference Dependencies Operator actions chg_rtf_freq In PCS 1900 systems. Are you sure (y=yes. 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. location Specifies the radio frequency channel location: 0 or bsc BSC 1 to 120 BTS rtf_id1 First device identifier.n=no)? COMMAND ACCEPTED y Example 2 This example changes the frequency channel to 3 for RTF 0 1 at the BSC: 2-122 GMR-01 68P02901W23-P 23 Feb 2004 . The range of values is 0 to 11.chg_rtf_freq Chapter 2: Device/function related commands The EGSM values are available only if the egsm_bcch_sd parameter is enabled. Loss of calls depends on the availability of other carriers. The range of values is 0 to 5. rtf_id2 Second device identifier. n=no)? COMMAND ACCEPTED y References Related information The range of values for GSM Phase 2 is: PGSM EGSM DCS1800 PCS1900 RTF_BCCH 1 to 124 RTF_NON_BCCH 1 to 124 RTF_BCCH 1 to 124 RTF_NON_BCCH 1 to 124 or 0. "disp_rtf_path" on page 2-305. Are you sure (y=yes. 68P02901W23-P 23 Feb 2004 2-123 GMR-01 .Technical Description BSS Command Reference chg_rtf_freq 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. "del_rtf_path" on page 2-179. "copy_path" on page 2-162. 975 to 1023 RTF_BCCH 512 to 885 RTF_NON_BCCH 512 to 885 RTF_BCCH 512 to 810 RTF_NON_BCCH 512 to 810 Related commands "add_rtf_path" on page 2-45. The number of alarms that can be modified is limited to 100. alarm code The decimal number identifying the alarm code for the device to be modified. Contact the OMC-R for help. Format Syntax chg_severity <device_name> <alarm_code> <severity> Input parameters device_name The name of the device. Security level 2 Supported by OMC-R GUI Yes Command type A (no operator actions) Prerequisites None Enter this command at the BSC only.chg_severity Chapter 2: Device/function related commands chg_severity Description The chg_severity command changes the severity of device and non-reconfiguration alarms. to be modified. This command does not work at a BTS site. such as GPROC. MSI or DRI. • Refer to "Alarm devices" on page 2-19 for the ranges of alarm codes for each device. severity 2-124 GMR-01 68P02901W23-P 23 Feb 2004 . • 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. Technical Description BSS Command Reference chg_severity 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-308. 68P02901W23-P 23 Feb 2004 2-125 GMR-01 . Note that the \ must not separate a hexadecimal character otherwise the two parts will be read as two separate ASCII characters. Enter this command at the BSC only. and terminated by pressing the RETURN key. This command does not work at a BTS site. 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. A message can be truncated anywhere by keying \ followed by RETURN. to form strings shorter than the length of one line. When the command is entered. 2-126 GMR-01 68P02901W23-P 23 Feb 2004 . Enter the CBCH background message after the MMI prompt. Security level 2 Supported by OMC-R GUI Yes Command type A (no operator actions) Prerequisites Short Message Service (SMS) is a purchasable option which must be installed on the system. The background message in all cells at all sites connected to the BSC may be modified. the MMI responds with an Enter the message prompt. Background messages are uniquely identified by message number. it is recommended that messages longer than one line are truncated explicitly by the operator. The GSM standard message can consist of up to 93 characters. The ASCII & hexadecimal methods of input can be interspersed in the same message. entered in hexadecimal or ASCII notation. The message created using this command may be displayed using the disp_cbch_state command.chg_smscb_msg Chapter 2: Device/function related commands chg_smscb_msg Description The chg_smscb_msg command changes a selected CBCH background message and the language in which it is presented. Contact the OMC-R for help. The chg_element cbch_enabled command must be used before the chg_smscb_msg command may be successfully used. PLMN Wide 2 Normal.Italian 9 . Cell Wide msg_code The ITU standard message code.Danish 14 . update_number This is the number of an update to an existing message. message_id The ITU standard identifier for the background message. The range of values is 0 to 15.Norwegian 68P02901W23-P 23 Feb 2004 2-127 GMR-01 . As an input parameter it now allows the operator to specify a particular update.Technical Description BSS Command Reference chg_smscb_msg Format Syntax chg_smscb_msg <msg_num> <message_id> <gs> <msg_code> <update_number> <data_coding_scheme> <cell_desc> chg_smscb_msg <msg_num> <message_id> <gs> <msg_code> <update_number> <data_coding_scheme> all Input parameters msg_num Uniquely identifies the number of the message for a given cell. data_coding_scheme This parameter determines the language for the CBCH background message.Polish 1 .Finnish 3 .French 10 . for example. The range of values is 0 to 3. The range of values is 0 to 3. Location Area Wide 3 Normal. This used to be automatically incremented for each update to a message. gs Geographical scope. used to differentiate between messages of the same source and type. Cell Wide 1 Normal.German 7 .Portuguese 32 .Czech 2 . The range of values is 0 to 1023. The range of values is 0 to 65535. where: 0 Immediate.English 8 . This indicates the area over which the message is unique. it might be required to use the same update of a message in a new cell as is being used in existing cells. The following languages are available: 0 . Swedish 13 . When the cell name is entered. it must be placed inside double quotation marks and be preceded by cell_name=.chg_smscb_msg Chapter 2: Device/function related commands 4 . EGSM.Greek 5 . The value all is a valid input for cell_desc. this value changes the specified message(s) for all cells at the BSS.Turkish 6 . preceded by cell_number=.Spanish 11 . and a language ID of 1: chg_smscb_msg 0 1234 2 0 0 1 cell_number=5 4 3 2 1 61986 34944 Where: is: 0 message_number 1234 message_id 2-128 GMR-01 68P02901W23-P 23 Feb 2004 . a message ID of 1234. This command responds to the shortened input parameter cell= allowing entry of either the cell_number or the cell_name without further definition. DCS1800. a geographical scope of 2. The name of the cell created using the cell_name command may be entered in place of the cell_number. 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. GSM Cell ID of the cell to be modified. an update number of 0. PCS1900) • Whether the seven parameter GSM Cell ID format or the four parameter GSM Cell ID format is enabled. cell_desc The GSM cell identifier (either the cell name or cell number) for the cell being modified. a message code of 0.Dutch 12 . Only the languages listed above are currently available. The format for the GSM Cell ID depends on: • The system used (PGSM.Hungarian The values of 15 to 31 and 33 to 255 are unspecified for the data_coding_scheme. .> 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 2 geographical_scope 0 message_code 0 update_number 1 data_coding_scheme all cell_desc. . the affected cell is identified using the cell_name “london-north": chg_smscb_msg 1 1234 1 546 1 1 cell_name="london-north" Where: 68P02901W23-P 23 Feb 2004 is: 1 message_number 1234 message_id 2-129 GMR-01 . indicates changes to all cells System response Enter the Message: <This is the only line of the message. .Technical Description BSS Command Reference Where: chg_smscb_msg is: 2 geographical_scope 0 message_code 0 update_number 1 data_coding_scheme cell_number=5 4 3 2 1 61986 34944 cell_desc System response Enter the Message: <This is the first line of the message.> COMMAND ACCEPTED Example 3 In this example. . This is the last line of the message. . a geographical scope of 2. and a language ID of 1. . . This is the last line of the message.> COMMAND ACCEPTED 2-130 GMR-01 68P02901W23-P 23 Feb 2004 . chg_smscb_msg 0 1234 2 0 0 1 cell_number=543 721 61986 34944 Where: is: 0 message_number 1234 message_id 2 geographical_scope 0 message_code 0 update_number 1 data_coding_scheme cell_number=543 721 61986 34944 cell_desc System response Enter the Message: <This is the first line of the message. . . a message ID of 1234. .> 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.chg_smscb_msg Chapter 2: Device/function related commands Where: is: 1 geographical_scope 546 message_code 1 update_number 1 data_coding_scheme cell_name="london-north" cell_desc System response Enter the Message: <This is the first line of the message. a message code of 0. an update number of 0. This is the last line of the message. K Ä k ä C ø Æ . The first character is a number from 0 to 7. For example. The second character is a hexadecimal value (0 to F) corresponding to the row in the table.Technical Description BSS Command Reference chg_smscb_msg References Related information Table 2-27 lists SMS special characters. Related commands "del_smscb_msg" on page 2-181. 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.38. 68P02901W23-P 23 Feb 2004 2-131 GMR-01 . < L Ö l ö D Carriage Return æ - = M Ñ m ñ E Å ß . "disp_cbch_state" on page 2-202. 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 Space 0 ¡ P ¿ p ! 1 A Q a q 0 @ 1 £ 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 + . > N Ü n ü F å É / ? O § o à _ GSM technical specification The permitted alphabet is defined in 03. This command does not work at a BTS site. The range of values is 0 to 1440. throttle_count Specifies the new throttle count in minutes. Security level 2 Supported by OMC-R GUI Yes Command type A (no operator actions) Prerequisites None Enter this command at the BSC only. A value of 0 means throttling is disabled. alarm_code Identifies the alarm to be throttled. Format Syntax chg_throttle <device_name> <alarm_code> <throttle_count> Input parameters device_name Name that uniquely identifies the device.chg_throttle Chapter 2: Device/function related commands chg_throttle Description The chg_throttle command changes the throttle period for an intermittent alarm. Contact the OMC-R for help. the range is 0 to 254. 2-132 GMR-01 68P02901W23-P 23 Feb 2004 . 68P02901W23-P 23 Feb 2004 2-133 GMR-01 .Technical Description BSS Command Reference chg_throttle 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-311. The relative change is useful for changing the clock for daylight savings time. This value can also be used to specify the number of hours to be added or subtracted to the current system time. The range of values is 1 to 12. The range of values is 1 to 31. Security level 2 Supported by OMC-R GUI No Command type A (no operator actions) Prerequisites None Format Syntax chg_time <year> <month> <day> <hour> <minute> <second> or chg_time <+/-> <hours> <minutes> Input parameters year Value identifying the year. day Value identifying the day of the month. minute 2-134 GMR-01 68P02901W23-P 23 Feb 2004 . The range of values is 0 to 23.chg_time Chapter 2: Device/function related commands chg_time Description The chg_time command sets the real-time system clock. hour Value identifying the hour. The year is entered in the four-digit format. as the first argument. The range of values is 1980 to 2100. month Value identifying the month. <+/-> A plus or minus. adds or subtracts the specified number of hours and minutes from the current time on the system clock. The clock may be set to a specific date and time of day or changed relative to the current time of day. 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 68P02901W23-P 23 Feb 2004 2-135 GMR-01 . Examples Example 1 In this example. This value can also be used to specify the number of minutes to be added or subtracted to the current system time. 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. The range of values is 0 to 59. day (12th). the system clock is set to year (1993).Technical Description BSS Command Reference chg_time Value identifying the minute. The range of values is 0 to 59. month (November). second Value identifying the second. 2-136 GMR-01 68P02901W23-P 23 Feb 2004 . "time_stamp" on page 2-472.chg_time Chapter 2: Device/function related commands References Related commands "disp_time" on page 2-313. • Frees reserved timeslots. Timeslots freed using this operation become unused and can be used for any connections.Technical Description BSS Command Reference chg_ts_usage chg_ts_usage Description The chg_ts_usage command does the following: • Reserves timeslots. NAIL This operation establishes a nailed connection between two timeslots at the same site. The system rejects a chg_ts_usage nail_path command when the path contains a ts_switch. • Nails timeslots. Timeslots freed using this operation become unused and can be used for normal connections. 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. It does not free timeslots that have been nailed using the NAIL_PATH operation. • Frees nailed timeslots. FREE_PATH or NAIL_PATH is restricted to 1 on HDSL links where only 16 timeslots are available. FREE_PATH This operation frees the timeslots of a NAIL_PATH nailed connection between different sites. A timeslot can not be used for any connections when it is reserved. NAIL_PATH This operation is establishes a nailed connection between two timeslots at different sites. FREE This operation frees timeslots that have been reserved or nailed using the the NAIL or RESERVE operations. 68P02901W23-P 23 Feb 2004 2-137 GMR-01 . The number of timeslots that can be RESERVE. NAIL. The following operations are supported by the chg_ts_usage command: RESERVE This operation reserves timeslots. chg_ts_usage Chapter 2: Device/function related commands As of software release GSR5. the add_link and delete_link commands are removed. Security level 2 Supported by OMC-R GUI No Command type A (no operator actions) Prerequisites MSIs must be equipped before timeslots can be nailed or reserved using the chg_ts_usage command. The functionality of these commands to nail and free timeslots is provided by the chg_ts_usage command. Enter this command at the BSC only.The system rejects the chg_ts_usage command when a 16 kbit/s XBL link is equipped on the timeslot. Contact the OMC-R for help. Refer to the parameter descriptions for function and valid values. 2-138 GMR-01 68P02901W23-P 23 Feb 2004 . 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. This command does not work at a BTS site. Technical Description BSS Command Reference chg_ts_usage operation The type of action to be performed. RESERVE. nail_path Establish a nailed connection between two timeslots at different sites. This field may be entered as upper or lower case characters. 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. free_path Free the timeslots of a nailed connection between different sites. 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. site Specifies the location of the MMS at one end of the T1/E1 Mbit/s link for FREE. and NAIL operations only. mms1_ts The timeslot number to be nailed at MMS1 using the NAIL operation only. reserve Reserve timeslots. 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 or 1. free Free timeslots that have been reserved or nailed using the the NAIL or RESERVE operations. 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. 68P02901W23-P 23 Feb 2004 2-139 GMR-01 . Values are 0 or 1. nail Establish a nailed connection between two timeslots at the same site. 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: 1 to 24 For 1.544 Mbit/s T1 Links 1 to 31 For 2.544 Mbit/s T1 Links 1 to 31 For 2.544 Mbit/s T1 Links 1 to 31 For 2. path_id2 represents the unique path among paths that are sharing the same terminating site.048 Mbit/s E1 Links. 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 9 Unique path number at shared Remote BTS or BSC 2-140 GMR-01 68P02901W23-P 23 Feb 2004 . path_id1 represents the terminating site of the path. Values are: 1 to 24 For 1. 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.chg_ts_usage Chapter 2: Device/function related commands mms2_ts The timeslot number to be nailed at MMS2 using the NAIL operation only. 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: 0 to 100 BSC or BTS path_id2 The PATH to be nailed or freed using the NAIL_PATH or FREE_PATH operations only.048 Mbit/s E1 Links site_1 The start 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. 048 Mbit/s E1 Links end_ts The last of the contiguous timeslots to be reserved or freed using the RESERVE or FREE operations only. Values are: 1 to 24 For 1. the contiguous timeslots between 16 and 31 at BTS 26 for MMS 1 0 are reserved: chg_ts_usage Enter Enter Enter Enter Enter action: RESERVE Site Identifier: 26 MMS Identifiers: 1 0 Starting Timeslot: 16 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 Enter Enter Enter Enter Enter Enter Action: NAIL Site Identifier: 26 MMS 1 Identifiers: 1 0 Starting Timeslot for MMS 1: 5 MMS 2 Identifiers: 0 1 Starting Timeslot for MMS 2: 13 Number of Timeslots Requested: 3 Example 3 In this example. including a 32/16 timeslot HDSL link Examples Example 1 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 68P02901W23-P 23 Feb 2004 2-141 GMR-01 .Technical Description BSS Command Reference chg_ts_usage num_ts The number of contiguous timeslots to be nailed using the NAIL or NAIL_PATH operations or freed using the FREE_PATH operation.048 Mbit/s E1 Links.544 Mbit/s T1 Links 1 to 31 For 2. Values are: 1 to 24 For 1.544 Mbit/s T1 Links 1 to 31 For 2. 2-142 GMR-01 68P02901W23-P 23 Feb 2004 .chg_ts_usage Chapter 2: Device/function related commands Enter Enter Enter Enter Enter Enter Enter Enter Enter action: NAIL_PATH Path Identifiers: 1 Start Site: 1 MMS 1 Identifiers: 0 0 Starting Timeslot for MMS 1: 7 End Site: 3 MMS 2 Identifiers: 1 0 Starting Timeslot for MMS 2: 6 Number of Timeslots Requested: 3 References Related command "disp_mms_ts_usage" on page 2-269. 25 link parameters. OML parameters cannot be changed.Technical Description BSS Command Reference chg_x25config chg_x25config Description The chg_x25config command changes the X. This command does not work at a BTS site.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. Format Syntax chg_x25config <link type> <x25_parameter> <value> Input parameters link type Specifies the type of X. Security level 2 Supported by OMC-R GUI Yes Command type A (no operator actions) Prerequisites None Enter this command at the BSC only. they are not stored in the database. Therefore. Contact the OMC-R for help. 68P02901W23-P 23 Feb 2004 2-143 GMR-01 . 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.chg_x25config Chapter 2: Device/function related commands x25_parameter Specifies the type of X.25 link: packet_size 128.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. 512 window_size 2 to 7 Examples Example 1 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 2-144 GMR-01 68P02901W23-P 23 Feb 2004 . 256. value Specifies the new value of the X. 68P02901W23-P 23 Feb 2004 2-145 GMR-01 .Technical Description BSS Command Reference chg_x25config References Related command "disp_x25config" on page 2-324. The range is 0 to 11.clear_cal_data Chapter 2: Device/function related commands 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. Security level 2 Supported by OMC-R GUI No Command type B (operator action required) Prerequisites This command is not available while in SYSGEN ON mode. dev_id The second device identifier. dev_id The third device identifier. 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.The DRI device must be locked. 2-146 GMR-01 68P02901W23-P 23 Feb 2004 . When this command is entered. Operator actions Respond to the warning prompt. This command may not be entered at a BT S. a warning that the calibration data for the specified transceiver will be cleared displays. dev_id The first device identifier. This value defaults to 0 if no value is entered. The range is 0 to 5. 68P02901W23-P 23 Feb 2004 2-147 GMR-01 .Technical Description BSS Command Reference clear_cal_data Example The following example clears the calibration data for DRI 5 3 0 at site 21: clear_cal_data 21 dri 5 3 0 Where: is: 21 site dri dri device 5 first dev_id 3 second dev_id 0 third dev_id System response Warning: This will clear the calibration data for this transceiver Are you sure (y=yes. "store_cal_data" on page 2-461.n=no)? y COMMAND ACCEPTED References Related commands "disp_cal_data" on page 2-200. clear_database Chapter 2: Device/function related commands clear_database Description The clear_database command deletes the contents of the CM database. The system is placed in the initial SYSGEN mode when this command is entered. Format Syntax clear_database Input parameters There are no input parameters associated with this command. Enter this command at the BSC only. Security level 2 Supported by OMC-R GUI Yes Command type B (operator actions required) Prerequisites This command can only be entered in the SYSGEN ON mode. 2-148 GMR-01 68P02901W23-P 23 Feb 2004 . Refer to "SYSGEN mode" on page 1-26. Operator actions Place the system in the SYSGEN ON mode before entering this command. This command should be used only by personnel who are fully aware of the consequences. This command does not work at a BTS site. Contact the OMC-R for help. the CM database is cleared: clear_database System response COMMAND ACCEPTED Example 2 In this example.Technical Description BSS Command Reference clear_database Examples Example 1 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 68P02901W23-P 23 Feb 2004 2-149 GMR-01 . Security level 2 Supported by OMC-R GUI No Command type A (no operator actions) Prerequisites This command is not allowed while in the SYSGEN ON mode. a prompt for a MMS ID displays. • The GCLK is recalibrated. Format Syntax clear_gclk_avgs <location> Input parameter location Specifies the location of the device: 0 or bsc BSC 1 to 120 BTS 2-150 GMR-01 68P02901W23-P 23 Feb 2004 . the LTA value is set to 80h and the frequency register readings are cleared. If this command is entered. • If this command is entered at an InCell site. • The uplink site does not provide a stable clock source. a prompt for a GCLK ID displays. The LTA values may need to be cleared under the following circumstances: • The GCLK is replaced.clear_gclk_avgs Chapter 2: Device/function related commands 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 at a non-InCell site. "disp_gclk_cal" on page 2-250. 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: COMMAND ACCEPTED 0 0 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. Related commands "disp_gclk_avgs" on page 2-248. 68P02901W23-P 23 Feb 2004 2-151 GMR-01 . This average is the Long Term Average (LTA).Technical Description BSS Command Reference clear_gclk_avgs Examples Example 1 In this example. A rolling average for each GCLK is calculated from up to 48 clock frequency register readings. 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: COMMAND ACCEPTED 1 Example 2 In this example. 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. NOTE Format Syntax configure_csfp Input parameters There are no input parameters associated with this command. Refer to the OMC-R for help. or pool GPROC device.configure_csfp Chapter 2: Device/function related commands configure_csfp Description The configure_csfp command configures CSFP (Code Storage Facility Processor) devices to sites in the BSS network. Security level 2 Supported by OMC-R GUI Yes Command type B (Operator actions required) Prerequisites This command can only be executed when the system is SYSGEN ON mode Operator actions Put the system into SYSGEN ON mode before executing this command. Enter this command at the BSC only. This command selects a BSP. dependent on the CSFP algorithm setting for that site. BTP. This command does not work at a BTS site. configure_csfp 2-152 GMR-01 68P02901W23-P 23 Feb 2004 . and converts the selected device to a CSFP device. Example This example shows the input required to configure the CSFP devices to sites in the BSS network. POOL For either BSC or remote BTS locations. If there is only one GPROC in the second cage.Technical Description BSS Command Reference configure_csfp System response COMMAND ACCEPTED References Related information Depending on the CSFP stealing algorithm (set using the chg_csfp command). an equipped GPROC is chosen first instead of choosing the redundant BSP or BTP device. If location is a remote BTS and two BTPs are equipped then one is configured as CSFP. 68P02901W23-P 23 Feb 2004 2-153 GMR-01 . "disp_csfp" on page 2-225. If the algorithm is set to “any" (the default value). "unconfigure_csfp" on page 2-489. The location does not matter. ANY is the default algorithm. the device stolen to become the CSFP can vary. ANY First the POOL algorithm is applied and then the STBY algorithm is applied. STBY If location is BSC and two BSPs are equipped then one will be configured as CSFP. an equipped GPROC is configured as CSFP. Algorithm set NONE No CSFPs are configured at the site. it cannot be chosen as a configured CSFP.NOTE Related Commands "chg_csfp" on page 2-84. connection_code Chapter 2: Device/function related commands 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. Security level 1 (to view). • To display the current value of operator-defined code. 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: 2-154 GMR-01 68P02901W23-P 23 Feb 2004 . 2 (to change) Supported by OMC-R GUI No Command type A (no operator action required) Prerequisites The GPRS must be unrestricted in order to assess a PCU site. • To turn the Call Connectivity Trace feature off. Technical Description BSS Command Reference connection_code 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". 68P02901W23-P 23 Feb 2004 2-155 GMR-01 . Horizonmicro or Horizoncompact site where a cell already exists. Contact the OMC-R for help Format Syntax copy_cell <source_cell_id> <dest_gsm_cell_id> <dest_location> <dest_bsic> ["cell_name"] 2-156 GMR-01 68P02901W23-P 23 Feb 2004 . Security level 2 Supported by OMC-R GUI Yes Command type B (operator actions required) Prerequisites None Operator actions Respond to the warning prompt presented when this command is entered. If dynamic allocation is in use at the source cell. Enter this command at the BSC only. and the coincident_mb to 0 at the new cell. If used on a coincident cell. The value of dynet_tchs_reserved does not change at the source cell. the cell bsic is not copied and a new bsic must be entered for the cell being created (destination cell). regardless of the setting in the source cell.copy_cell Chapter 2: Device/function related commands copy_cell Description The copy_cell command creates a new cell by copying the information in an existing cell. Also. This command does not work at a BTS site. the system sets the value of the dynet_tchs_reserved parameter to the default (0). the copy_cell command sets the coincident cell to an invalid value. This command is rejected if it is entered for an M-Cellcity. Only one cell is permitted at these sites. This command can not copy a cell source or neighbour information. An extended source cell is copied as an extended destination cell. The value of the dynet_tchs_reserved parameter at the destination cell is always defaulted to 0. dest_gsm_cell_id GSM Cell ID of the new cell to be created. The full format is given in the cell_name parameter description.Technical Description BSS Command Reference copy_cell Input parameters source_cell_id GSM Cell ID of the existing cell being copied. The cell name created using the cell_name command may be entered in place of the source_cell_id. This cell name must be placed inside double quotation marks. PCS1900 or GSM850). it must be placed inside double quotation marks. DCS1800. When the cell name is entered. as if created using the cell_name command. PCS1900 or GSM850). DCS1800. Inclusions The following parameters are copied when the copy_cell command is executed: alt_qual_proc decision_1_tim_adv_av_alg ms_p_con_interval attach_detach decision_1_ul_rxlev_av_h ms_power_control_allowed ba_alloc_proc decision_1_ul_rxlev_av_ih ms_txpwr_max_cch bs_ag_blks_res decision_1_ul_rxlev_av_p ms_txpwr_max_def bs_pa_mfrms decision_1_ul_rxqual_av_h mspwr_alg {23658}bep_period decision_1_ul_rxqual_av_p ncc_of_plmn_allowed {23658}bep_period2 dl_rxlev_ho_allowed number_of_preferred_cells 68P02901W23-P 23 Feb 2004 2-157 GMR-01 . The format for the GSM Cell ID depends on: • The system used (PGSM. Values are: 0 or bsc BSC 1 to 120 BTS dest_bsic Specifies the BSIC of the new cell. EGSM. • Whether the seven parameter GSM Cell ID format or the four parameter GSM Cell ID format has been enabled. The range of values for the bsic is 0 to 63. The format for the GSM Cell ID depends on: • The system used (PGSM. cell_name A cell name can be specified for the dest_gsm_cell_id. dest_location Specifies the location of the new cell. EGSM. • Whether the seven parameter GSM cell ID format or the four parameter GSM Cell ID format has been enabled. A cell name may not be entered for the destination Cell ID. copy_cell Chapter 2: Device/function related commands bsic dl_rxqual_ho_allowed number_sdcchs_preferred bts_p_con_ack dtx_required penalty_time bts_p_con_interval dyn_step_adj pow_inc_step_size_dl bts_power_control_allowed dyn_step_adj_fmpr pow_red_step_size_dl ccch_conf {23658}egprs_init_dl_cs pow_inc_step_size_ul cell_bar_access_class {23658}egprs_init_ul_cs pow_red_step_size_ul cell_bar_access_switch emergency_class_switch pwr_handover_allowed cell_bar_qualify en_incom_ho pwrc cell_reselect_hysteresis extended_paging_active radio_link_timeout cell_reselect_offset frequency_type rapid_pwr_down cell_reselect_param_ind full_pwr_rfloss reestablish_allowed decision_1_dl_rxlev_av_h handover_power_level report_resource_tch_f_high_ water_mark decision_1_dl_rxlev_av_ih handover_recognized_period report_resource_tch_f_low_ water_mark decision_1_dl_rxlev_av_p ho_margin_def rpd_offset decision_1_dl_rxqual_av_h intave rpd_period decision_1_dl_rxqual_av_p inter_cell_handover_allowed rpd_trigger decision_1_n1 interfer_ho_allowed rxlev_access_min decision_1_n2 intr_cell_handover_allowed rxlev_min_def decision_1_n3 l_rxlev_dl_h sdcch_ho decision_1_n4 l_rxlev_dl_p sdcch_timer_ho decision_1_n5 l_rxlev_ul_h temporary_offset decision_1_n6 l_rxlev_ul_p timing_advance_period decision_1_n7 l_rxqual_dl_h {23658}tlli_blk_coding decision_1_n8 l_rxqual_dl_p tx_integer decision_1_ncell_rxlev_ av_h_calc l_rxqual_ul_h u_rxlev_dl_ih decision_1_p_bgt_rxlev_av_h l_rxqual_ul_p u_rxlev_dl_p decision_1_p1 link_about_to_fail ul_rxlev_ho_allowed decision_1_p2 link_fail u_rxlev_ul_ih decision_1_p3 max_retran u_rxlev_ul_p decision_1_p4 max_tx_bts u_rxqual_dl_p decision_1_p5 max_ts_ms ul_rxqual_ho_allowed decision_1_p6 missing_rpt u_rxqual_ul_p decision_1_p7 ms_distance_allowed wait_indication_parameters decision_1_p8 ms_p_con_ack 2-158 GMR-01 68P02901W23-P 23 Feb 2004 . 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: 68P02901W23-P 23 Feb 2004 2-159 GMR-01 . fdd_qoffset. qsearch_c_initial.num_carriers hopping_support Note that neighbor definitions also are not copied.Technical Description BSS Command Reference copy_cell If the Inter-RAT handover option is unrestricted. and inter_rat_enabled. If the GPRS feature is unrestricted. the GPRS elements at a cell are copied by the copy_cell command. qsearch_i. Exceptions The following is a list of parameters that are not copied (default values are used) when the copy_cell command is executed: bsic inner_zone_alg bcch_frequency inter_rat_enable cbch_enabled ms_max_range cell_name multiband_reporting coincident_index res_ts_less_one_carrier coincident_mb source_cells dynet_tchs_reserved sw_ts_less_one_carrier equipment_share_table_pointer switch_gprs_pdchs ext_range_cell thresholds freq_share_table_pointer tx_power_cap gsm_cell_id trx_pwr_carriers. except for the following: bvci ra_colour gprs_enabled Example Example 1 In this example. the following parameters will be defaulted in the new cell: fdd_qmin. and UMTS UTRAN cells are copied with copy_cell. with the cell name of “paris": copy_cell 543 721 61986 34944 543 721 61986 34945 0 6 "paris" Where: is: 543 721 61986 34944 source_cell_id 543 721 61986 34945 dest_gsm_cell_id 0 dest_location 6 dest_bsic paris cell_name System response COMMAND ACCEPTED 2-160 GMR-01 68P02901W23-P 23 Feb 2004 .copy_cell Chapter 2: Device/function related commands 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. 68P02901W23-P 23 Feb 2004 2-161 GMR-01 .Technical Description BSS Command Reference copy_cell 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. "disp_cell" on page 2-205. "del_cell" on page 2-168. and this path can be copied or extended to the next BTS. 2-162 GMR-01 68P02901W23-P 23 Feb 2004 .copy_path Chapter 2: Device/function related commands copy_path Description The copy_path command equips a new PATH device by copying an existing path and extending it to a new site. The single exception to this rule is when the system cannot check master/slave settings because the HDSL link consists of two external modems. 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. This command does not work at a BTS site. Security level 2 Supported by OMC-R GUI Yes Command type A (no operator actions) Prerequisites None Enter this command at the BSC only. identical link protocol types and HDSL modems that are in a master/slave configuration. Contact the OMC-R for help. The first path to the first BTS can be configured when a path is created using the equip command. This facility is useful when adding paths to the network or creating a long branch. 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. 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 Enter the new terminating site id: Example This example shows a typical dialogue: copy_path System response Enter the terminating SITE id to be copied: 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 4 References Related information The figure below illustrates that “downstream" always refers to the direction from the BSC to the BTS. if the terminating BTS does not use dynamic allocation. below) none Note: If the terminating BTS uses dynamic allocation. 68P02901W23-P 23 Feb 2004 2-163 GMR-01 . the range is 6 to 9. while “upstream" always describes the direction from the BTS to the BSC.Technical Description BSS Command Reference copy_path Table 2-28 copy_path command prompts Prompt Enter the terminating SITE id to be copied: Enter the Unique PATH id to be copied: Range Default 1 to 120 none 0 to 9 6 to 9 (see Note. the range is 0 to 9. "disp_rtf_path" on page 2-305. "chg_rtf_freq" on page 2-119.copy_path Chapter 2: Device/function related commands Site 5 UPSTREAM Site 0 UPSTREAM BSC BTS DOWNSTREAM MMS 30 Site 6 BTS DOWNSTREAM MMS 31 MMS 27 Related commands "add_rtf_path" on page 2-45. 2-164 GMR-01 68P02901W23-P 23 Feb 2004 . "del_rtf_path" on page 2-179. Security level 2 Supported by OMC-R GUI Yes Command type A (no operator actions) Prerequisites None. pcu_0 to pcu_2 {4040} PCU device_name Device name that uniquely identifies the device. 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 pcu. See "disp_act_alarm" on page 2-195 The disp_act_alarm command displays the alarms that can be deleted by the operator. dev_id1 68P02901W23-P 23 Feb 2004 2-165 GMR-01 .Technical Description BSS Command Reference del_act_alarm del_act_alarm Description The del_act_alarm command deletes an active operator clearable alarm. 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 2-166 GMR-01 68P02901W23-P 23 Feb 2004 . 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 {4040} This example deletes an active alarm for PSP 0. alarm code 2. The range of values is 1 to 128. Example 1 This example deletes an active alarm for KSW 1 0 0. The range of values is 0 to 99. dev_id3 Third device identifier.del_act_alarm Chapter 2: Device/function related commands First device identifier. alarm_code Alarm to be deleted. dev_id2 Second device identifier. The range of values is 0 to 99. The range of values is 0 to 254. alarm code 1. Technical Description BSS Command Reference Where: del_act_alarm is: 0 dev_id3 1 alarm_code System response COMMAND ACCEPTED References Related commands "disp_act_alarm" on page 2-195. 68P02901W23-P 23 Feb 2004 2-167 GMR-01 . del_cell Chapter 2: Device/function related commands del_cell Description The del_cell command deletes a cell from the CM database. 2-168 GMR-01 68P02901W23-P 23 Feb 2004 . Format Syntax del_cell <cell_id> Input parameter cell_id GSM Cell ID of the cell to be deleted. Security level 2 Supported by OMC-R GUI Yes Command type A (no operator actions) Prerequisites A cell may not be removed if it is currently in a DRI descriptor. Contact the OMC-R for help. DCS1800. This command does not work at a BTS site. When the cell name is entered. To remove a cell that is included in a DRI descriptor. Enter this command at the BSC only. the DRI must be unequipped first. The name of the cell created using the cell_name command may be entered in place of the cell_id. 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. EGSM. PCS1900) • Whether the seven parameter GSM cell ID format or the four parameter GSM Cell ID format has been enabled. The format for the GSM Cell ID depends on: • The system being used (PGSM. it must be placed inside double quotation marks. Technical Description BSS Command Reference del_cell Examples Example 1 In this example. the cell with cell_number 987 654 12345 67809 (using the four parameter format) at site number 0 is deleted from the CM database: del_cell 987 654 12345 67809 Where: is: 987 654 12345 67809 cell_id System response COMMAND ACCEPTED Example 3 In this example. the affected cell is identified using the cell_name “london-south". del_cell "london-south" Where: is: london-south cell_name System response COMMAND ACCEPTED 68P02901W23-P 23 Feb 2004 2-169 GMR-01 . 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. "disp_gsm_cells" on page 2-253.del_cell Chapter 2: Device/function related commands References Related commands "add_cell" on page 2-21. 2-170 GMR-01 68P02901W23-P 23 Feb 2004 . "copy_cell" on page 2-156. "disp_cell" on page 2-205. The range is 0 to 123 when executed from an RXCDR. This command may only be entered at the BSC or RXCDR 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. This only applies to remote transcoding BSC and RXCDR sites. Examples Example 1 This example shows connectivity information deleted for MMS 4 0 at the BSC: 68P02901W23-P 23 Feb 2004 2-171 GMR-01 . local_mms_id_2 Second identifier of the MMS at the local site. 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. 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.Technical Description BSS Command Reference del_conn 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. Values are 0 or 1. Security level 2 Supported by OMC-R GUI Yes Command type A (no operator actions) Prerequisites All CICs and XBLs must be unequipped before deleting MMS connectivity information. "mod_conn" on page 2-390. 2-172 GMR-01 68P02901W23-P 23 Feb 2004 . "disp_conn" on page 2-223.del_conn Chapter 2: Device/function related commands 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. and contains any coincident cells. If all is entered in place of the first Cell ID. then every neighbour in the specified cell’s neighbour list is deleted. 68P02901W23-P 23 Feb 2004 2-173 GMR-01 . Enter this command at the BSC only. For handovers to UMTS UTRAN cells. Security level 2 Supported by OMC-R GUI Yes Command type A (no operator actions) Prerequisites To be on a Neighbour Cell List. This command does not work at a BTS site. this command supports the UMTS UTRAN cell identity format. a cell must be the destination of handovers from the Neighbour List owner. If all is entered for a BTS at which the Coincident MultiBand Handover option is enabled. Contact the OMC-R for help. If all is entered in place of the second cell ID. the command is rejected. the second Cell ID is removed from the first cell neighbour list. If the Inter_RAT (Radio Access Technology) handover feature is unrestricted.Technical Description BSS Command Reference del_neighbor del_neighbor Description The del_neighbor command deletes neighbour cells from a cell neighbour list. then the cell is deleted from all associated neighbour lists. the Inter-RAT handover option must be unrestricted. If two Cell IDs are entered. GSM Cell ID of the cell specified to be removed from the Neighbour List. it must be placed inside double quotation marks. The format for the GSM Cell ID depends on: • The system being used (PGSM. The string test <num> may be entered for this field where <num> is a value from 1 to 64. DCS1800. When the cell name is entered. The name of the cell created using the cell_name command may be entered in place of the cell_id. GSM Cell ID of the Neighbour List owner. PCS1900) • Whether the seven parameter GSM cell id format or the four parameter GSM Cell ID format has been enabled. EGSM. neighbor_cell_id GSM or UTRAN Cell ID of the cell specified to be removed from the Neighbour List. PCS1900) • Whether the seven parameter GSM cell id format or the four parameter GSM Cell ID format has been enabled. it must be placed inside double quotation marks. 2-174 GMR-01 68P02901W23-P 23 Feb 2004 . This permits test neighbours to be removed from the BA_SACCH and/or BA_BCCH lists. DCS1800. all <neighbor_cell_id> This syntax removes the neighbour cell from all source cell neighbour lists. The format for the GSM Cell ID depends on: • The system being used (PGSM.del_neighbor Chapter 2: Device/function related commands 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. EGSM. 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. <source_cell_id> all This syntax removes all neighbour cells from the source cell neighbour list. Technical Description BSS Command Reference del_neighbor 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: 68P02901W23-P 23 Feb 2004 2-175 GMR-01 . del_neighbor Chapter 2: Device/function related commands 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. "disp_neighbor" on page 2-281. "disp_gsm_cells" on page 2-253. 2-176 GMR-01 68P02901W23-P 23 Feb 2004 . "disp_cell" on page 2-205. "del_cell" on page 2-168. "copy_cell" on page 2-156. "add_neighbor" on page 2-35. Data Link Connection Identifier (DLCI) and a GBL {4040} at a specific PCU... ns_vci_1 Specifies the unique identifier of the first NSVCI mapping and identifier of the object. range = 0 to 65535. Security level 2 Supported by OMC-R GUI Yes Command type A (no operator actions) Prerequisites The GPRS feature must be unrestricted. ns_vci_8 Specifies the unique identifiers of subsequent NSVCI mapping and the objects (up to 8). Example The following example deletes NSVCI 580 {4040} at the first equipped PCU.. Format Syntax {4040} del_nsvc <pcu_id> <ns_vci_1> [<ns_vci_2> .. ns_vci_2 . range = 0 to 65535.Technical Description BSS Command Reference del_nsvc del_nsvc Description The del_nsvc command enables the user to remove one or more mappings between a Network Service Virtual Connection Identifier (NSVCI). <ns_vci_8>] Input parameter(s): {4040} pcu_id Specifies the specific PCU. pcu_1 or pcu_2. pcu_0. as pcu. 68P02901W23-P 23 Feb 2004 2-177 GMR-01 . 2-178 GMR-01 68P02901W23-P 23 Feb 2004 .del_nsvc Chapter 2: Device/function related commands 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-393. The range of values is 0 to 5. The system rejects attempts to modify the PATHs used by RTFs at sites that use dynamic allocation. Format Syntax del_rtf_path <location> <1st_RTF_identifier> <2nd_RTF_identifier> <unique_PATH_identifier> Input parameters location The number of the BTS where the RTF is located. RTFs do not use PATH(s) equipped by the operator for these types of sites. 2nd_RTF_identifier The 2nd RTF identifier from which the path will be removed. 68P02901W23-P 23 Feb 2004 2-179 GMR-01 . Contact the OMC-R for help.Technical Description BSS Command Reference del_rtf_path 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. RTFs automatically use the PATH(s) defined for these types of sites. The range of values is 0 to 11. Security level 2 Supported by OMC-R GUI Yes Command type A (no operator actions) Prerequisites None Enter this command at the BSC only. 1st_RTF_identifier The 1st RTF identifier from which the path will be removed. PATHs for such sites are defined by the equip DYNET command. The range of values is 1 to 120. This command does not work at a BTS site. "chg_rtf_freq" on page 2-119. "disp_rtf_path" on page 2-305. 2-180 GMR-01 68P02901W23-P 23 Feb 2004 . Example This example deletes a redundant RTF PATH from site 36. Related commands "add_rtf_path" on page 2-45. The range of values is 0 to 9. When deleting a redundant path. "copy_path" on page 2-162. the path is automatically switched over to the remaining paths. the command is rejected. Are you sure? (y=yes. 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. n=no)?y COMMAND ACCEPTED References Related information If a redundant path does not exist. RTF identifiers 5 20.del_rtf_path Chapter 2: Device/function related commands unique_PATH_identifier The unique PATH to be removed. The value all is also a valid input for the msg_num to specify all messages at the specified cell(s). This command may be used to delete: • A single message at a single cell. cell_desc 68P02901W23-P 23 Feb 2004 2-181 GMR-01 . Security level 2 Supported by OMC-R GUI Yes Command type A (no operator actions) Prerequisites None Enter this command at the BSC only. Contact the OMC-R for help. This command does not work at a BTS site.Technical Description BSS Command Reference del_smscb_msg del_smscb_msg Description The del_smscb_msg command deletes the CBCH background message. 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. • All messages at a single cell. • All messages at all cells in the BSS. • A single message at all cells in the BSS. PCS1900) • Whether the seven parameter GSM cell ID format or the four parameter GSM Cell ID format has been enabled. EGSM. 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) 2-182 GMR-01 68P02901W23-P 23 Feb 2004 . This command responds to the shortened input parameter cell= allowing entry of either the cell_number or the cell_name without further definition. DCS1800. The value all is also a valid input for the cell_desc. The format for the GSM Cell ID depends on: • The system used (PGSM. it must be placed inside double quotation marks. When the cell name is entered. The name of the cell created using the cell_name command may be entered in place of the cell_number. and be preceded by cell_name=. to delete the specified message(s) at all cells at the BSS. preceded by cell_number=.del_smscb_msg Chapter 2: Device/function related commands This parameter is the GSM Cell ID of the cell at which messages are to be deleted. the affected cell is identified using the cell_name “london-south".Technical Description BSS Command Reference del_smscb_msg System response COMMAND ACCEPTED Example 3 In this example. 68P02901W23-P 23 Feb 2004 2-183 GMR-01 . 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-126. "disp_cbch_state" on page 2-202. This command is also used to execute a specific test on a specific device.device_audit Chapter 2: Device/function related commands device_audit Description The device_audit command suspends or resumes audits at a specific site. A user at the OMC-R must rlogin to a site before an audit can be performed. 2-184 GMR-01 68P02901W23-P 23 Feb 2004 . 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 Specifies the audit location: 0 or bsc BSC 1 to 120 BTS pcu. the BSC performs an audit. off Suspends all site audits within a cage at a specific site. Security level 2 Supported by OMC-R GUI Yes Command type A (no operator action) Prerequisites This command is not allowed while in SYSGEN ON mode. When this command is used to execute an audit at the BSC for a RXCDR that is in the BUSY-UNLOCKED state. pcu_0 to pcu_2 {4040} PCU control Site audit status: on Resumes all site audits within a cage at a specific site. Identifier value is dependent upon the device. Given these conditions. It is only possible to audit the device that are actually equipped at the site. device_id3 Third device identifier. device_id2 Second device identifier.Technical Description BSS Command Reference device_audit audit_type Type of audit: safe Initiates safe tests. 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. The format for each of the additional devices is the same as it is for the first device. 68P02901W23-P 23 Feb 2004 2-185 GMR-01 . Identifier value is dependent upon the device. device_name Name that uniquely identifies the device. Identifier value is dependent upon the device. self Initiates self tests. Not all devices can be audited at all site types. Multiple devices can be audited if all is entered as the control parameter value. all Initiates all audits. the response is: COMMAND REJECTED: Audits already turned off for this device.device_audit Chapter 2: Device/function related commands Examples Example 1 The following example executes the safe audits for KSW device ID 0 0 0: device_audit bsc safe ksw 0 0 0 Where: is: bsc location safe audit_type ksw device_name 0 device_id1 0 device_id2 0 device_id3 System response Device: KSW Device id: 0 0 0 Year: 1994 Month: 11 Day: 12 Hour: Audit Type: SAFE Result: PASS 0 Min: 26 Sec: 29 MSec: 665 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. Example 3 The following example resumes audits for a KSW device with ID 1 0 0 at site 4: 2-186 GMR-01 68P02901W23-P 23 Feb 2004 . Technical Description BSS Command Reference device_audit 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 {4040} 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 Device: MSI Device id: 2 0 0 Year:1999 Month:1 Day:22 Hour:17 Min:56 Sec:12 MSec:470 Audit Type: SAFE Result: PASS 68P02901W23-P 23 Feb 2004 2-187 GMR-01 . "query_audits" on page 2-407.device_audit Chapter 2: Device/function related commands References Related commands "cage_audit" on page 2-54. 2-188 GMR-01 68P02901W23-P 23 Feb 2004 . "chg_audit_sched" on page 2-72. "site_audit" on page 2-438. all standby DRIs must be locked before using this command. The range is 0 to 255. id2 Specifies the third identifier. The range is 0 to 255.Technical Description BSS Command Reference diagnose_device diagnose_device Description The diagnose_device command performs the specified diagnostic on the specified device. id0 Specifies the first identifier. The range is 0 to 255. Only DRI devices at {4471} Horizonmacro sites are supported. 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. 68P02901W23-P 23 Feb 2004 2-189 GMR-01 . Security level 2 Supported by OMC-R GUI No Command type B (operator actions required) Prerequisites This command is supported only in the SYSGEN OFF mode. Operator actions The operator must lock the DRI before using this command. For there to be free RTFs for DRI diagnostics. id1 Specifies the second identifier. the Receive Preamplifier Input Loopback test fails. 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 RX preamp Input Loopback RXLEV (Branch 1): -50 dBm RX preamp Input Loopback RXLEV (Branch 2): -50 dBm RCU Output Loopback: NOT RUN RCU Output Loopback RXLEV (Branch 1): N/A RCU Output Loopback RXLEV (Branch 2): N/A END OF REPORT 2-190 GMR-01 68P02901W23-P 23 Feb 2004 . but RCU Output Loopback passes (indicating a possible problem with the receive front-end). diagnose_device 1 DRI 0 0 0 System response Diagnostic Type: rf_loopback REPORT FOR DRI 0 0 0 AT SITE 1 ------------------------------------------RELATED RTF: RTF 0 0 0 (ARFCN 60) RX preamp input loopback: FAIL RX preamp Input Loopback RXLEV (Branch 1): -128 dBm RX preamp Input Loopback RXLEV (Branch 2): -128 dBm RCU Output Loopback: PASS RCU Output Loopback RXLEV (Branch 1): 50 dBm RCU Output Loopback RXLEV (Branch 2): 50 dBm END OF REPORT Example 2 In this example. the Receive Preamplifier Input Loopback test passes.diagnose_device Chapter 2: Device/function related commands Prompted parameter After specifying the input parameters listed above. indicating that the diagnostic passes (RCU Output Loopback is not run). The following types are available: Device Diagnostic DRI rf_loopback vswr_test Examples Example 1 In this example. the operator is prompted for the type of diagnostic to be performed. disp_a5_alg_pr 68P02901W23-P 23 Feb 2004 2-191 GMR-01 . Security level Any Supported by OMC-R GUI Yes Command type A (no operator actions) Prerequisites None Format Syntax disp_a5_alg_pr Input parameters There are no input parameters associated with this command.Technical Description BSS Command Reference disp_a5_alg_pr disp_a5_alg_pr Description The disp_a5_alg_pr command displays the current list of prioritized encryption algorithms. 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. "page" on page 2-405. 2-192 GMR-01 68P02901W23-P 23 Feb 2004 .disp_a5_alg_pr Chapter 2: Device/function related commands System response Ciphering Algorithms are prioritized as follows: 0 References Related commands "chg_a5_alg_pr" on page 2-69. PCS1900) • Whether the seven parameter GSM Cell ID format or the four parameter GSM Cell ID format has been enabled. Only PCS1900 systems can use a three digit MNC. The format for the GSM Cell ID depends on: • The system used (PGSM. The site must be an AMR-capable BTS. it must be placed inside double quotation marks. EGSM. The Cell ID or the “cell_name" must be entered directly without any preceding qualifier. This command responds to the shortened input parameter cell= allowing entry of either the cell_number or the cell_name without further definition. 68P02901W23-P 23 Feb 2004 2-193 GMR-01 . The name of the cell created using the cell_name command may be entered in place of the Cell ID.Technical Description BSS Command Reference disp_acs disp_acs {4322} Description The disp_acs command displays the Active Codec Set and associated parameters. Security level 1 Supported by OMC-R GUI Yes Command type A (no operator actions) Prerequisites The AMR feature must be unrestricted. Format disp_acs <cell_id> Input parameters cell_id GSM Cell ID or cell name of the cell to be changed. DCS1800. When the cell name is entered. disp_acs Chapter 2: Device/function related commands 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 AMR AMR AMR AMR AMR AMR AMR AMR AMR AMR AMR AMR AMR AMR AMR AMR AMR AMR AMR Full Full Full Full Full Full Full Full Full Full Half Half Half Half Half Half Half Half Half Half Rate Rate Rate Rate Rate Rate Rate Rate Rate Rate Rate Rate Rate Rate Rate Rate Rate Rate Rate Rate active codec set: 0 1 3 4 intial codec mode: 1 uplink adaptation thresholds: 40 30 20 uplink adaptation hysteresis: 1 1 2 downlink adaptation thresholds: 45 35 25 downlink adaptation hysteresis: 1 1 2 uplink adaptation thresholds for frequency hopping: 16 11 4 uplink adaptation hysteresis for frequency hopping: 1 1 1 downlink adaptation thresholds for frequency hopping: 27 22 14 downlink adaptation hysteresis for frequency hopping: 1 1 1 active codec set: 3 4 5 intial codec mode: 3 uplink adaptation thresholds: 30 20 uplink adaptation hysteresis: 1 1 downlink adaptation thresholds: 31 21 downlink adaptation hysteresis: 1 1 uplink adaptation thresholds for frequency hopping: 28 21 uplink adaptation hysteresis for frequency hopping: 1 1 downlink adaptation thresholds for frequency hopping: 30 23 downlink adaptation hysteresis for frequency hopping: 1 1 References Related command "chg_acs_params" on page 2-61 2-194 GMR-01 68P02901W23-P 23 Feb 2004 . only the first 200 are displayed and monitored.Technical Description BSS Command Reference disp_act_alarm 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. 68P02901W23-P 23 Feb 2004 2-195 GMR-01 . The output of this command displays up to 200 alarms for each device in the site. dev_id1 First device identifier. The range of values is 0 to 99. Those alarms that have been designated as Intermittent do not appear in the active alarm list. device_name Device name that uniquely identifies the device. 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 pcu. pcu_0 to pcu_2 {4040} PCU all Specifies all sites. Security level 1 Supported by OMC-R GUI No Command type A (no operator actions) Prerequisites This command is not allowed while in SYSGEN ON mode. This does not affect the number of alarms displayed after entering disp_act_alarm <location>. If there are more than 200 active alarms on the device. Each device has an active alarm list limit of 200. since any uncleared intermittent alarm would be considered an active alarm. and Fault Management alarms for DRI 1 0 0 at the BSC. The range of values is 0 to 99. 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 2-196 GMR-01 68P02901W23-P 23 Feb 2004 . dev_id3 Third device identifier. The command does not show all active alarms. Examples Example 1 This example displays all active Operator Initiated Clear. The range of values is 0 to 99.disp_act_alarm Chapter 2: Device/function related commands dev_id2 Second device identifier. Technical Description BSS Command Reference disp_act_alarm 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: {4040} 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>. 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. 68P02901W23-P 23 Feb 2004 2-197 GMR-01 . There are no active alarms on that device. {4040} This includes the PCUs. Read the Functional Unit Status across the display. Site 0 is in Critical status. • Broadcast Control Channel (BCCH) frequency for each of the cells. Format Syntax disp_bss 2-198 GMR-01 68P02901W23-P 23 Feb 2004 . Cell 4. or 1 if site is OMNI.indicates normal operations. • Number of sectors. • Major . which is associated with Site 0 is in Clear status. if any have been equipped. The status information shows the following: • Sites that are equipped and their status.disp_bss Chapter 2: Device/function related commands disp_bss Description The disp_bss command displays specific status information for all sites in a BSS or a Remote Transcoder (RXCDR) site. The possible values are: • Critical . Security level 1 Supported by OMC-R GUI Yes Command type A (no operator actions) Prerequisites This command is not allowed while in SYSGEN ON mode.indicates a loss of capacity. • Clear .indicates a loss of service. In the example below. The BSS or RXCDR device identifier where the command is entered will be included in the output. • GSM Cell IDs that are equipped for each site. The functional Unit Status shows the status of the BSC sites or of the associated cells. and Cell 5 is in Critical status. a line containing GPRS information appears in the output. • Minor . If the GPRS feature is unrestricted. and values of the RAC and BVCI associated with each cell.indicates a loss of redundancy. Technical Description BSS Command Reference disp_bss Input parameters There are no input parameters associated with this command.---------------------------0 B-U CRITICAL CRITICAL 496 01 1 (0001h) 4 (0004h) CRITICAL 496 01 1 (0001h) 2 (0002h) PCU_0 B-U CRITICAL PCU_1 B-U CRITICAL 1 D-U UNAVAILABLE UNAVAILABLE 496 01 1 (0001h) 1 (0001h) UNAVAILABLE 496 01 1 (0001h) 6 (0006h) FREQ BCCH RAC TYPE FREQ --. 68P02901W23-P 23 Feb 2004 2-199 GMR-01 .----------. Example This example shows the format of a typical output of the disp_bss command.----.---2 5 PGSM PGSM 40 60 19 NA PGSM PGSM 87 75 References Related command "assess" on page 2-49.---. disp_bss System response OPER STATES: ADMIN STATES: D:Disabled E:Enabled L:Locked U:Unlocked B:Busy E:Equipped NE:Not Equipped S:Shutdown Status for BSS 22: {4040} SITE FUNCTIONAL # OF GSM CELL ID SITE STATE UNIT STATUS MCC MNC LAC CI ---. 16 values are displayed. This command is not available at an RXCDR. This value defaults to 0 if no value is entered. then all 22 values are displayed. 2-200 GMR-01 68P02901W23-P 23 Feb 2004 . Security level 1 Supported by OMC-R GUI No Command type A (no operator actions) Prerequisites This command is not allowed while in SYSGEN ON mode. dev_id1 The first device identifier. If the BSC and BTS are set for PGSM operation. dev_id3 The third device identifier. The first six are for EGSM and the next 16 are for PGSM. 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.disp_cal_data Chapter 2: Device/function related commands 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 system is set so that the frequency_type parameter is EGSM. dev_id2 The second device identifier. 81. 6F. 60. References Related commands "clear_cal_data" on page 2-146. 66. 6F. 56. 5F. 54. 77. 5D. 5D. 5D. 78. 5F. 4D. 64. 61. In the example above the information is read from the transceiver. 77. 6C. 67. "store_cal_data" on page 2-461. 5F. 74. 74. 5B. 67. 54. 76. 66. 56. 81. 6D. 6C. 4F. 70. 55. 66. 4E. 71. 65. 5F. 4A. 62. 56. 66. 9D. 70. 66.Technical Description BSS Command Reference disp_cal_data 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. 45. 60. 44. 68. 55. 44. 65. 80. 66. 66. 68P02901W23-P 23 Feb 2004 2-201 GMR-01 . 69. 65. 6D. 6D. 6D. 44. 56. 44. 7E. 43. 57. 67. 4D. 6F. 74. 64. 5A. 60. 66. Note that the second line of the system response indicates whether the data is read from the transceiver or the database. 6D. 77. 55. 87. 64. 5F. 77. 54. 83. 55. 68. 5A. 55. 55. 67. 60. 77. 81. 66. disp_cbch_state Chapter 2: Device/function related commands disp_cbch_state Description The disp_cbch_state command displays the value of the cbch_enabled field for a specific cell. 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 frequency hopping index (fhi) for the CBCH timeslot is also displayed. The range of values is 0 to 3. cell_desc The GSM Cell ID of the cell to be displayed. 2-202 GMR-01 68P02901W23-P 23 Feb 2004 . PCS1900). If the all option is selected for the message number parameter. If the CBCH is hopping. DCS1800. In addition. the specified background message in a cell is presented. Security level 1 Supported by OMC-R GUI Yes Command type B (operator actions required) Prerequisites The background message feature must be purchased. Operator actions The Background Message feature must be unrestricted. all background messages associated with the indicated cell display. preceded by cell_number=. EGSM. The format for the GSM Cell ID depends on: • The system used (PGSM. and activated for this command to be successfully executed. installed. 68P02901W23-P 23 Feb 2004 2-203 GMR-01 . The name of the cell created using the cell_name command may be entered in place of the cell_number.Technical Description BSS Command Reference • disp_cbch_state Whether the seven parameter GSM Cell ID format or the four parameter GSM Cell ID format has been 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 CBCH for cell 5 4 3 2 1 61986 3494 is not enabled. When the cell name is entered. The CBCH for cell 5 4 3 2 1 61986 3494 is not enabled. The cell_number parameter uses the seven parameter format. The cell_number parameter uses the four parameter format. it must be placed inside double quotation marks and be preceded by cell_name=. disp_cbch_state 3 cell_number=543 21 61986 3494 Where: is: 3 msg_num 543 21 61986 3494 cell_number System response Message Number 3 is not defined for the CBCH. 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. 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. This command responds to the shortened input parameter cell= allowing entry of either the cell_number or the cell_name without further definition. "del_smscb_msg" on page 2-181. The CBCH for cell 5 4 3 2 1 61986 3494 is not enabled.disp_cbch_state Chapter 2: Device/function related commands 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. References Related commands "chg_smscb_msg" on page 2-126. disp_cbch_state 3 cell_name="london-south" Where: is: 3 msg_num london-south cell_name System response Message Number 3 is not defined for the CBCH.PLMN Wide). The CBCH for cell 5 4 3 2 1 61986 3494 is active. update number is 0. Language Identifier is 3 (French). the affected cell is identified using the cell_name “london-south". The channel description is: Channel Type: SDCCH/4 Subchannel number 2 Timeslot Number = 0 ARFCN = 107 (BCCH Carrier) Example 4 In this example. Non alphabetic characters are displayed in their escape format The The The The The Message Identifier is 1009 Geographical Scope is 1 (Normal . Message Code is 0. 2-204 GMR-01 68P02901W23-P 23 Feb 2004 . If the disp_cell command is used with the cell description and the optional “full" parameter. Security level 1 Supported by OMC-R GUI Yes Command type A (no operator actions) Prerequisites None Format Syntax disp_cell <cell_desc> ["full"] Input parameters cell_desc GSM Cell number of the cell to be displayed. it must be placed inside double quotation marks and preceded by cell_name=. 68P02901W23-P 23 Feb 2004 2-205 GMR-01 .Technical Description BSS Command Reference disp_cell disp_cell Description The disp_cell command reads back and displays all programmable database parameters for a specified cell. If the disp_cell command is used with the cell_description only. • Whether the seven parameter GSM Cell ID format or the four parameter GSM Cell ID format has been enabled. When the cell name is entered. EGSM. PCS1900). the system displays all cell-related elements. The name of the cell created using the cell_name command may be entered in place of the cell_desc preceded by cell_number=. The format for the GSM Cell ID depends on: • The system used (PGSM. the system displays the elements used in the add_cell command. DCS1800. 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. 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 system displays the elements with non-indexed parameters first. followed by the indexed parameters also in alphabetical order. using the cell_number 543 721 62259 08736: 2-206 GMR-01 68P02901W23-P 23 Feb 2004 . in alphabetical order. “full" This optional parameter displays all elements related to the cell.disp_cell Chapter 2: Device/function related commands This command responds to the shortened input parameter cell= allowing entry of either the cell_number or the cell_name without further definition. the cell 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. the cell is identified in the four parameter format. 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 68P02901W23-P 23 Feb 2004 2-207 GMR-01 . This information differs from cell to cell. the system displays the cell information. if the disp_cell command is entered correctly.Technical Description BSS Command Reference disp_cell disp_cell 543 721 62259 08736 Where: is: 543 721 62259 08736 cell_desc System response In every case. all cell elements are displayed. If the parameter “full” is included. disp_cell Chapter 2: Device/function related commands 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 2-208 GMR-01 68P02901W23-P 23 Feb 2004 . "del_cell" on page 2-168. 68P02901W23-P 23 Feb 2004 2-209 GMR-01 . "copy_cell" on page 2-156. "disp_gsm_cells" on page 2-253.Technical Description BSS Command Reference disp_cell 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. Examples Example 1 Display cell mapping at PCUs 1 and 2: 2-210 GMR-01 68P02901W23-P 23 Feb 2004 . {23658}The displayed information includes EGPRS availability. Security level 1 Supported by OMC-R GUI Yes Command type A (no operator actions) Prerequisites This command is not allowed while in SYSGEN ON mode. Format Syntax disp_cell_map all|location|cell_id Input parameters all Displays cell mapping at all equipped PCUs. location pcu. The disp_cell_status command shows the status details of the PCU that is currently serving a cell.disp_cell_map Chapter 2: Device/function related commands disp_cell_map {4040} Description Because of the dynamic cell migration in case of failure and recovery. a cell can be mapped to any equipped PCU site. cell_id Identifier of cell for which mapping to a PCU is required. The disp_cell_map command displays the current cell mapping information to a particular PCU. pcu_0 to pcu_2. Technical Description BSS Command Reference disp_cell_map disp_cell_map pcu_1 pcu_2 System response PCU Site 1: CELL ID -------------------------001 01 1 (0001h) 4 (0004h) 001 01 1 (0001h) 5 (0005h) GPRS STATUS -------------------Barred Unbarred PCU Site 2: CELL ID -------------------------001 01 1 (0001h) 7 (0007h) 001 01 1 (0001h) 8 (0008h) GPRS STATUS -------------------Barred 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 -------------------------001 01 1 (0001h) 4 (0004h) 001 01 1 (0001h) 5 (0005h) GPRS STATUS -------------------Barred Unbarred PCU Site 1: CELL ID -------------------------001 01 1 (0001h) 7 (0007h) 001 01 1 (0001h) 8 (0008h) GPRS STATUS -------------------Barred Unbarred PCU Site 2: CELL ID -------------------------001 01 1 (0001h) 1 (0001h) 001 01 1 (0001h) 2 (0002h) 68P02901W23-P 23 Feb 2004 GPRS STATUS -------------------Barred Unbarred 2-211 GMR-01 . EGPRS Unavail END OF REPORT 2-212 GMR-01 68P02901W23-P 23 Feb 2004 . EGPRS Avail Unbarred.disp_cell_map Chapter 2: Device/function related commands END OF REPORT Example 4 {23658}This example displays cell mapping at a PCU when EGPRS feature is unrestricted: disp_cell_map pcu System response PCU Site 0: CELL ID ---------------------------001 01 666 (029Ah) 3 (0003h) 001 01 666 (029Ah) 30 (001Eh) 001 01 666 (029Ah) 40 (0028h) 001 01 666 (029Ah) 41 (0029h) 001 01 666 (029Ah) 1 (0001h) GPRS STATUS -------------------GSM cell OOS GPRS Disabled Barred Unbarred. 68P02901W23-P 23 Feb 2004 2-213 GMR-01 . The format for the GSM Cell ID depends on: • The system being used (PGSM. Security level 1 Supported by OMC-R GUI Yes Command type A (no operator actions) Prerequisites This command is not allowed while in SYSGEN ON mode. the information on the first two cells displays. a cell can be mapped to any equipped PCU site. EGSM. it must be placed inside double quotation marks and be preceded by cell_name=. When the cell name is entered. {4040} Because of the dynamic cell migration in case of failure and recovery.Technical Description BSS Command Reference disp_cell_status disp_cell_status Description The disp_cell_status command displays information and channel counters of a single GSM cell or all GSM cells at a specific site. When the status of all the cells at a location with more than three cells is requested. then a prompt to continue. preceded by cell_number=. 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. PCS1900 or GSM850) • Whether the seven parameter GSM cell ID format or the four parameter GSM Cell ID format has been enabled. The cell_name is not included when all of the cells at a site are to be displayed. the cell_name is included in the command output. The name of the cell created using the cell_name command may be entered in place of the cell_number. DCS1800. When the status of a single cell is requested. The system displays an error message if the BTF is not in service for any reason. The disp_cell_status command includes the information on the cell active PCU. The cell is barred while an SPI is in progress.An SPI (Signalling Point Inaccessibility) is in progress. Status • Barred . • No . • No .A MS may not access the cell.A reset is not in progress.disp_cell_status Chapter 2: Device/function related commands This command responds to the shortened input parameter cell= allowing entry of either the cell_number or the cell_name without further definition. the value of this element is not relevant to the status of the cell.The BSS BSSAP (Base Station System Application Part) Prohibited flag is set to true. • NA . Reset In Progress • Yes .Not applicable.An SPI is not in progress.The BSS BSSAP Prohibited flag is not set to true. • No . BSS BSSAP Prhb • Yes . MSC BSSAP Prhb 2-214 GMR-01 68P02901W23-P 23 Feb 2004 . • Unbarred . 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). GPRS Status {23658}This field shows the status of a GPRS cell (barred/unbarred) and (when unbarred) whether EGPRS is available. The cell is barred while a reset is in progress. The cell will be barred while the BSS BSSAP Prohibited flag is true. PDCH Status This field shows the GPRS Packet Data traffic channel status. GPRS Reset in Prog This field shows whether a PCU is currently undergoing a Reset.A MS may access the cell.A reset is in progress. SPI in Progress • Yes . Not applicable. The cell is barred while the SPI/MSC BSSAP Prohibited flag is true. Full Power Mode This field indicates if the cell is in the full power mode. 68P02901W23-P 23 Feb 2004 2-215 GMR-01 . Any timeslot which is unavailable due to being locked or out of service is counted as an unavailable TCH (not SDCCH). Norm Outer TCH/F: FREE. SPI/MSC SCCP Prhb • Yes . Norm Inner TCH/F: FREE. • NA . {23658} EGPRS Chan Req This field indicate if 11-bit EGPRS one-phase access is supported in the cell. the value of this element is not relevant to the status of the cell. in use or unavailable. • No . SDCCH: FREE. this field contains Nonewhen all access classes have been unbarred. INUSE. UNAVL These fields specify the number of Full Rate Traffic Channels (TCH/H) in the outer zone concentric cell that are currently free.The SPI/MSC BSSAP Prohibited flag is not set to true. If the cell is barred or OOS. • No . Ext Range Mode This field shows whether the Extended Range Feature is enabled (on) or disabled (off).The MSC BSSAP Prohibited flag is not set to true. the value of this element is not relevant to the status of the cell. in use or unavailable. GPRS AccClass Bar This field shows any access class barring of GPRS cells. The cell is barred while the MSC BSSAP Prohibited flag is true.The MSC BSSAP Prohibited flag is set to true. INUSE. in use or unavailable. in use or unavailable. Norm Outer TCH/F: FREE. INUSE. that are currently free. this field will contain NA. • NA . AccCLASS Bar This field specifies the access class(es) of MSs that are barred from the cell. EPCR is only available in the cell if the BCCH RTF is mapped to a CTU II radio. If the cell is unbarred. This does not include entire carriers which are out of service. UNAVL These fields specify the number of Full Rate Traffic Channels (TCH/F) in the outer zone concentric cell that are currently free. The UNAVL field includes timeslots that are locked or out of service due to a fault condition. separated by commas. The access class is presented as a decimal value. UNAVL These fields specify the number of Full Rate Traffic Channels (TCH/F) in the inner zone concentric cell that are currently free.Not applicable. INUSE.The SPI/MSC BSSAP Prohibited flag is set to true. UNAVL These fields specify the number of Standalone Dedicated Control Channels (SDCCH) in the cell.Technical Description BSS Command Reference disp_cell_status • Yes . Norm Inner TCH/G: FREE. UNAVL These fields specify the number of Generic Traffic Channels (TCH/G) in the inner zone concentric cell that are currently free. 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 System response GSM CELL ID MCC 543 MNC 21 LAC CI (dec) 61986 34944 (hex) f222h 8880h (name) london-south 2-216 GMR-01 68P02901W23-P 23 Feb 2004 .disp_cell_status Chapter 2: Device/function related commands Ext Outer TCH/F: FREE. in use or unavailable. {23658} EGPRS PD CHANNEL This field shows the EGPRS Packet Data traffic channels currently free. UNAVL These fields specify the number of Generic Traffic Channels (TCH/G) in the outer zone concentric cell that are currently free. Norm Outer TCH/G: FREE. RES PDCH Requested This field shows the RES PDCH requested. in use or unavailable. SW PDCH Requested This field shows the SW PDCH requested. UNAVL These fields specify the number of Full Rate Traffic Channels (TCH/F) in the extended outer concentric cell that are currently free. in use or unavailable. UNAVL These fields specify the number of Half Rate Traffic Channels (TCH/H) in the inner zone concentric cell that are currently free. in use or unavailable. Norm Inner TCH/H: FREE. in use or unavailable. INUSE. INUSE. INUSE. in use or unavailable. PD CHANNEL This field shows the GPRS Packet Data traffic channels currently free. INUSE. Technical Description BSS Command Reference disp_cell_status -------------------------------------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 SDCCH Norm Outer TCH/F Norm Inner TCH/F Ext Outer TCH/F FREE ----0 0 0 0 INUSE ----0 0 0 0 UNAVL ----0 0 0 0 End of Report. Example 2 This example identifies the cell using the cell_name “london-south": disp_cell_status cell_name="london-south" Where: is: london-south cell_name System response GSM CELL ID MCC 543 MNC 21 LAC CI (dec) 61986 34944 (hex) f222h 8880h (name) london-south -----------------------------------Status Barred Reset In Prog No SPI in Prog Yes BSS BSSAP Prhb Yes MSC BSSAP Prhb No SPI/MSC SCCP Prhb No AccCLASS Bar NA Ext Range Mode OFF SDCCH Norm Outer TCH/F Norm Inner TCH/F Ext Outer TCH/F FREE ----0 0 0 0 INUSE ----0 0 0 0 UNAVL ----0 0 0 0 End of Report 68P02901W23-P 23 Feb 2004 2-217 GMR-01 . disp_cell_status Chapter 2: Device/function related commands Example 3 This example shows the display for a cell where the Concentric Cells feature is enabled: disp_cell_status 0 Where: is: 0 cell_number System response Start of report for LOCATION 39: GSM CELL ID MCC 001 MNC 01 LAC CI (dec) 1 39001 (hex) 0001h 9859h -------------------------------------Frequency Type PGSM BCCH Frequency 62 -------------------------------------Status Unbarred Reset in Prog No SPI in Prog No BSS BSSAP Prhb NA MSC BSSAP Prhb NA SPI/MSC SCCP Prhb NA AccClass Bar None SDCCH Norm Outer TCH/F Norm Inner TCH/F Ext Outer TCH/F FREE ----0 0 0 0 INUSE ----0 0 0 0 UNAVL ----0 0 0 0 End of Report. Example 4 This example displays the status of a BTS site: disp_cell_status 30 Where: is: 30 location System response Start of report for LOCATION 30: GSM CELL ID MCC MNC LAC CI RAC 001 01 17 31 NA (0011h) (001Fh) 2-218 GMR-01 001 01 17 33 NA (0011h) (0021h) 68P02901W23-P 23 Feb 2004 . ----8 0 0 0 0 0 0 0 0 0 0 0 0 0 0 6 NA 0 0 NA 0 NA NA NA End of Report.----.Technical Description BSS Command Reference disp_cell_status -----------------------------------------------------------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 SDCCH Norm Outer Ext Outer Norm Outer Norm Inner Norm Outer Norm Inner PD CHANNEL TCH/F TCH/F TCH/H TCH/H TCH/G TCH/G FREE INUSE UNAVL ----.----. Example 5 This example shows the display when a location is entered and the GPRS feature is unrestricted: disp_cell_status bsc Where: is: bsc location System response {4040} Start of report for LOCATION 0: GSM CELL ID MCC 001 001 MNC 01 01 LAC 1 (0001h) 1 (0001h) CI 1 (0001h) 6 (0006h) RAC 8 (0008h) NA ------------------------------------------------------------Primary Freq Type PGSM PGSM Secondary Freq Type N/A N/A 68P02901W23-P 23 Feb 2004 2-219 GMR-01 .----8 0 0 0 0 0 0 0 0 0 0 0 0 0 0 14 NA 0 0 NA 0 NA NA NA FREE INUSE UNAVL ----. ----.----.----.disp_cell_status Chapter 2: Device/function related commands 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 SDCCH Norm Outer TCH/F Norm Inner TCH/F Ext Outer TCH/F PD CHANNEL FREE INUSE UNAVL FREE INUSE UNAVL ----. disp_cell_status cell_number=4 9 6 0 1 1 1 Where: is: 4960111 cell_number 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 2-220 GMR-01 68P02901W23-P 23 Feb 2004 .----.----4 0 0 0 0 0 7 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 8 0 0 NA NA NA End of Report Example 6 {4322} This example displays the status of Cell ID 4 9 6 0 1 1 1 with the parameter amr_half_rate_enabled set to enabled. Technical Description BSS Command Reference disp_cell_status Reset in Prog GPRS Reset in Prog SPI in Prog BSS BSSAP Prhb MSC BSSAP Prhb SPI/MSC SCCP Prhb AccClass Bar GPRS AccClass Bar Full Power Mode Ext Range Mode No No No NA NA NA NA NA OFF OFF SDCCH Norm Outer Norm Inner Norm Outer Norm Inner Norm Outer Norm Inner PD CHANNEL FREE ----0 0 0 0 0 0 0 NA TCH/F TCH/F TCH/H TCH/H TCH/G TCH/G INUSE ----0 0 0 0 0 NA NA NA UNAVL ----0 0 0 0 0 0 0 NA End of Report Example 7 {23658}This example displays the status of an in-service cell capable of EGPRS and GPRS: disp_cell_status 3 System response Start of report for LOCATION 3: 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 ---------------------------------------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 68P02901W23-P 23 Feb 2004 2-221 GMR-01 . ----. 2-222 GMR-01 68P02901W23-P 23 Feb 2004 .disp_cell_status Chapter 2: Device/function related commands Full Power Mode Ext Range Mode Active PCU Site OFF OFF 0 SDCCH Norm Outer TCH/F Norm Inner TCH/F Ext Outer TCH/F Norm Outer TCH/H Norm Inner TCH/H Norm Outer TCH/G Norm Inner TCH/G PD CHANNEL EGPRS PD CHANNEL FREE INUSE UNAVL ----.----8 0 0 14 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 NA 0 0 NA 0 1 6 0 6 2 0 End of Report. The range is 1 to 123 when this command is executed from a BSC. Format Syntax disp_conn [<remote_entity_id>] Input parameters remote_entity_id The network identity of the remote site.Technical Description BSS Command Reference disp_conn disp_conn Description The disp_conn command displays the MSS connectivity between the RXCDR and the BSS sites connected to it. The term “local site" refers to the site at which the command is executed. disp_conn 68P02901W23-P 23 Feb 2004 2-223 GMR-01 . The range is 1 to 55 when executed from an RXCDR. and are specified by equipped AXCDR devices at the BSC. the term “remote site" refers to the site to which the local site is connected. Examples Example 1 Display all the MMS connectivity between the BSS and all RXCDRs which are connected to it. Security level 2 Supported by OMC-R GUI No Command type A (no operator actions) Prerequisites This command is only available at a BSC or RXCDR site. disp_conn Chapter 2: Device/function related commands System response The BSS to RXCDR connectivity is as follows : BSS MMS id 0 1 is connected to RXCDR 4 .MMS id 4 0 Finished displaying BSS to RXCDR connectivity Example 2 Display the MMS connectivity between the BSS and RXCDR 5.MMS id 9 0 BSS MMS id 1 1 is connected to RXCDR 5 .MMS id 4 0 Finished displaying BSS to RXCDR connectivity 2-224 GMR-01 68P02901W23-P 23 Feb 2004 . disp_conn 5 System response The BSS to RXCDR connectivity is as follows : BSS MMS id 1 1 is connected to RXCDR 5 . which is represented by equipped device AXCDR 5 at the BSC. Security level 1 Supported by OMC-R GUI Yes Command type A (no operator actions) Prerequisites None Format disp_csfp <location> [<element>] Input parameters location Specifies the element location: 0 or bsc BSC 1 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: 68P02901W23-P 23 Feb 2004 2-225 GMR-01 .Technical Description BSS Command Reference disp_csfp disp_csfp Description The disp_csfp command displays the per site CSFP algorithm or flow control values. 2-226 GMR-01 68P02901W23-P 23 Feb 2004 .disp_csfp Chapter 2: Device/function related commands disp_csfp bsc algorithm Where: is: bsc location algorithm element System response Site ---0 Algorithm --------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 ---3 Flow Control -----------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 ---7 Flow Control -----------10 Algorithm --------ANY References Related command "chg_csfp" on page 2-84. and the device does not contain a valid software instance. DEVICE LOCKED The CSFP device is locked. or is currently being downloaded with code. AWAITING CODE The CSFP device is enabled-unlocked. NOT EQUIPPED The CSFP equipment is not installed. Format Syntax disp_csfp_status 68P02901W23-P 23 Feb 2004 2-227 GMR-01 . Security level 1 Supported by OMC-R GUI Yes Command type A (no operator actions) Prerequisites This command is not allowed while in SYSGEN ON mode. NO CODE The CSFP device is disabled-unlocked. and the device is in a queue to be loaded. 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. and the device is code loaded. CSFP OOS The CSFP device is out of service. CODE LOADED The CSFP device is busy-unlocked.Technical Description BSS Command Reference disp_csfp_status disp_csfp_status Description The disp_csfp_status command displays the status of all CSFPs equipped in the BSS network. SITE/LINK OOS Link is out of service. 2-228 GMR-01 68P02901W23-P 23 Feb 2004 .ID 0. disp_csfp_status System response SITE.0 CSFP EQUIP NO STATUS * References Related command "chg_csfp" on page 2-84. disp_csfp_status System response SITE.ID 0.0 CSFP EQUIP YES STATUS 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 Chapter 2: Device/function related commands 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. Security level 1 Supported by OMC-R GUI Yes Command type A (no operator actions) Prerequisites None Format Syntax disp_dte [<link> <link_number>] If no input parameters are specified.Technical Description BSS Command Reference disp_dte disp_dte Description The disp_dte command displays DTE addresses. This command is primarily for use by field technicians or installers. 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 68P02901W23-P 23 Feb 2004 2-229 GMR-01 . disp_dte Chapter 2: Device/function related commands Examples Example 1 In this example. the DTE link addresses are displayed (in binary coded decimal) when the command is entered: disp_dte System response BSS DTE Address Address Address Address addresses: #0: 31070863210701 #1: 31070863210701 #2: 31070863210701 #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-87. 2-230 GMR-01 68P02901W23-P 23 Feb 2004 . the row (bin_num) is entered as the index1 value. When the disp_element command is used to display the values of parameters modified using the chg_cell_element command. Database parameters modified using the chg_cell_element command are stored in a four row data array. The syntax required to display each of the CM database parameters is included in the parameter description in Chapter 5.Technical Description BSS Command Reference disp_element disp_element Description The disp_element command displays the value of a database parameter in the CM database.<index1>][. Individual database parameter values modified using the chg_cell_element command may not be displayed using the disp_element command. An example is included at the end of the description of this command.<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. All 32 values located in the entered row number are displayed. Security level 1 Supported by OMC-R GUI Yes Command type A (no operator actions) Prerequisites None Format Syntax disp_element <database_parameter>[. the index value must be entered immediately after the database parameter name separated by a comma. 68P02901W23-P 23 Feb 2004 2-231 GMR-01 . The rows in the data array are specified as bins in the chg_cell_element command. preceded by cell_number=. 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 2-232 GMR-01 68P02901W23-P 23 Feb 2004 . pcu_0 to pcu_2 PCU all Specifies all sites. This command responds to the shortened input parameter cell= allowing entry of either the cell_number or the cell_name without further definition. DCS1800. The cell_desc can also be specified as all. The format for the GSM Cell ID depends on: • The system used (PGSM. cell_desc GSM Cell ID 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_number.disp_element Chapter 2: Device/function related commands location Specifies the site location: 0 or bsc BSC 1 to 120 BTS {4040} pcu. it must be placed inside double quotation marks and be preceded by cell_name=. Examples Example 1 In this example. When the cell name is entered. EGSM. PCS1900) • Whether the seven parameter GSM Cell ID format or the four parameter GSM Cell ID format has been enabled. 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.Technical Description BSS Command Reference disp_element Example 2 In this example.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.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 34944 cell_desc This example could have been entered as: disp_element rxlev_dl_ho. Related commands "chg_element" on page 2-94. refer to "CM database parameters presentation" on page 5-2. 68P02901W23-P 23 Feb 2004 2-233 GMR-01 . disp_element rxlev_dl_ho. System response rxlev_dl_ho[0] = alg_num: 0 alg_data: 8 References Related information For detailed information on database parameters. MEM 0238 . Equipment configurations typically vary by location. 2-234 GMR-01 68P02901W23-P 23 Feb 2004 . REV 0 This numerical value represents the current revision level of the most recent change. Information displayed includes the parameters entered for a specific device or function using the equip command. Kit numbers are incremented in response to either a hardware or firmware change. This hardware information includes the hardware version number (hvn) displayed as a numerical value. B This is the hardware version of the printed circuit board represented as an alphabetical value. More than one firmware version may exist for any given hardware version of a printed circuit board. 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. This can then be followed by further information.BIT ERROR RATE TEST This is additional descriptive information related to the last revision to the printed circuit board. A This is the firmware version of the printed circuit board. In later releases. therefore. A single hvn may represent one or more kit numbers for a specific printed circuit board.disp_equipment Chapter 2: Device/function related commands disp_equipment Description The disp_equipment command displays the software and hardware information of equipped devices and functions. a kit number will be displayed in place of an hvn. This command may be used to identify the site equipment configuration using location as the only command argument. The relationship of the hvn to the kit number is dependent on the equipment configuration. The full option permits hardware information to be displayed in addition to the equipment parameters. the devices and functions available for display will vary from site to site. dependent on the particular hardware and its revision level. A kit number includes the current hardware and firmware revisions of the printed circuit board. Kit numbers use the following format: SLN7133BA Where: is: SLN7133 This is a unique value identifying a specific printed circuit board. pcu_0 to pcu_2 {4040} PCU dev/func name Literal that uniquely identifies the device or function id1 First identifier or the wild card character “*". Security level 1 Supported by OMC-R GUI Yes Command type A (no operator actions) Prerequisites None. 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. the output is a table which includes kit and serial numbers. 68P02901W23-P 23 Feb 2004 2-235 GMR-01 . id3 Third identifier or the wild card character “*".Technical Description BSS Command Reference disp_equipment The hvns for half size boards are not reported by the disp_equipment command. 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 pcu. The full option is not allowed while in SYSGEN ON mode. id2 Second identifier or the wild card character “*". When this option is used to display all of the equipment at a site. cic_num1 First CIC device number. timeslot2 Second timeslot. or last in a range if TO is used. group2 Second group. * Indicates all CICs on the MMSs specified in the timeslot. 2-236 GMR-01 68P02901W23-P 23 Feb 2004 . cic_num2 Last CIC device number in a range. mms_id2 Second MMS identifier. timeslot1 First timeslot. mms_id1 First MMS identifier. regardless of group. or last in a range if TO is used. group1 First group. 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 Specifies the location of the device: 0 or bsc BSC 1 to 120 BTS CIC Literal that uniquely identifies the CIC device.disp_equipment Chapter 2: Device/function related commands CIC syntax Because the Circuit Identity Code (CIC) device can be specified in different ways. Technical Description BSS Command Reference disp_equipment 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 {4415} Device --------------GPROC 2 0 0 GPROC 3 0 0 GPROC 1 0 0 BSP 0 0 0 CSFP 0 0 0 MSI 0 0 0 MMS 0 0 0 MMS 0 0 0 MTL 0 0 0 RSL 2 0 0 RSL 3 0 0 SITE 3 0 0 SITE 4 0 0 PATH 1 0 0 BSS 1 0 0 LCF 1 0 0 FRU ---------------GPROC2 Unavailable GPROC2 GPROC2 Unavailable MSII Unavailable Unavailable Unavailable Unavailable Unavailable Unavailable Unavailable Unavailable Not Applicable Not Applicable Kit Number --------------Not Applicable Unavailable Not Applicable Not Applicable Unavailable Not Applicable Unavailable Unavailable Unavailable Unavailable Unavailable Unavailable Unavailable Unavailable Serial Number --------------Not Applicable Unavailable Not Applicable Not Applicable Unavailable Not Applicable Unavailable Unavailable Unavailable Unavailable Unavailable Unavailable Unavailable Unavailable HVN --4 255 4 4 255 4 255 255 255 255 255 255 255 255 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: 68P02901W23-P 23 Feb 2004 is: 0 location kswx device/function name *** 1st, 2nd, and 3rd identifier wild cards full full option 2-237 GMR-01 disp_equipment Chapter 2: Device/function related commands 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 2-238 GMR-01 68P02901W23-P 23 Feb 2004 Technical Description BSS Command Reference Where: disp_equipment 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: 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 3 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. 68P02901W23-P 23 Feb 2004 2-239 GMR-01 disp_equipment Chapter 2: Device/function related commands 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 BSC MMS identifiers are: 0 0 SITE identifier is: 1 Upstream MMS identifiers are: 0 Downstream MMS identifiers are: SITE identifier is: 2 Upstream MMS identifiers are: 0 Downstream MMS identifiers are: SITE identifier is: 3 2-240 GMR-01 DYNET usage is: 20 0 0 1 0 0 1 68P02901W23-P 23 Feb 2004 Technical Description BSS Command Reference disp_equipment Upstream MMS identifiers are: 0 Downstream MMS identifiers are: Upstream MMS identifiers are: 0 Downstream MMS identifiers are: SITE identifier is: 5 Upstream MMS identifiers are: 0 Downstream MMS identifiers are: SITE identifier is: BSC Upstream MMS identifiers are: 0 0 0 1 0 0 1 0 0 1 1 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: 68P02901W23-P 23 Feb 2004 2-241 GMR-01 disp_equipment Chapter 2: Device/function related commands 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 2-242 GMR-01 68P02901W23-P 23 Feb 2004 Technical Description BSS Command Reference disp_equipment 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 {4040} 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-327, "modify_value" on page 2-402. 68P02901W23-P 23 Feb 2004 2-243 GMR-01 disp_exp_config Chapter 2: Device/function related commands 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 Supported by OMC-R GUI Yes Command type A (no operator actions) Prerequisites None Format Syntax disp_exp_config <location> Input parameters location Specifies the location of the site. Values are: 0 or bsc BSC 1 to 120 BTS Example The following example displays the TDM highway configuration of the BSC: disp_exp_config 0 Where: is: 0 the location 2-244 GMR-01 68P02901W23-P 23 Feb 2004 Technical Description BSS Command Reference disp_exp_config System response Highway 0 (CAGE 0) ----------------Connected to highway 1 by EXP 0 (U21 U9) Connected to highway 2 by EXP 1 (U22 U8) Connected to highway 3 by EXP 2 (U23 U7) Highway 1 (CAGE 1) ----------------Connected to highway 0 by EXP 0 (U21 U9) Connected to highway 2 by EXP 1 (U22 U8) Connected to highway 3 by EXP 2 (U23 U7) Highway 2 (CAGE 2) ----------------Connected to highway 0 by EXP 0 (U21 U9) Connected to highway 1 by EXP 1 (U22 U8) Connected to highway 3 by EXP 2 (U23 U7) Highway 3 (CAGE 3) ----------------Connected to highway 0 by EXP 0 (U21 U9) Connected to highway 1 by EXP 1 (U22 U8) Connected to highway 2 by EXP 2 (U23 U7) 68P02901W23-P 23 Feb 2004 2-245 GMR-01 disp_flash Chapter 2: Device/function related commands disp_flash Description The disp_flash command displays the version information of the current flash EEPROM load. Use this command to view the software version number, EEPROM creation date, checksum and size. Security level 1 Supported by OMC-R GUI Yes Command type A (no operator actions) Prerequisites None Format Syntax disp_flash Input parameters There are no input parameters associated with this command. Example The following example shows the version information of the flash EEPROM: disp_flash System response Version : Date : Checksum: Size : 1.5.0.0.8 01/04/97 23:51 0x3D691A2 838702 Bytes Where: is: Version the version of the software the system is currently running. 2-246 GMR-01 68P02901W23-P 23 Feb 2004 Technical Description BSS Command Reference Where: 68P02901W23-P 23 Feb 2004 disp_flash 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-247 GMR-01 disp_gclk_avgs Chapter 2: Device/function related commands disp_gclk_avgs Description The disp_gclk_avgs command displays the Long Term Average (LTA) values for a specific GCLK. The system reads the clock frequency register of each GCLK once every half hour after synchronization if the GCLK is phase locked. A rolling average for each GCLK is calculated of up to 48 clock frequency register readings. This average is the LTA. Security level 1 Supported by OMC-R GUI No Command type A (no operator actions) Prerequisites This command is not allowed while in SYSGEN ON mode. This command is not allowed for M-Cell sites. Format Syntax disp_gclk_avgs <location> <gclk_id> Input parameters location Specifies the location of the GCLK. Values are: 0 or bsc BSC 1 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: 2-248 GMR-01 68P02901W23-P 23 Feb 2004 Technical Description BSS Command Reference disp_gclk_avgs 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-150. 68P02901W23-P 23 Feb 2004 2-249 GMR-01 disp_gclk_cal Chapter 2: Device/function related commands 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 Command type A (no operator actions) Prerequisites This command is not allowed while in the SYSGEN ON mode. This command is not allowed for M-Cell sites. Format Syntax disp_gclk_cal <location> <gclk_id> Input parameters location 2-250 GMR-01 68P02901W23-P 23 Feb 2004 Technical Description BSS Command Reference disp_gclk_cal 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). 68P02901W23-P 23 Feb 2004 2-251 GMR-01 disp_gclk_cal Chapter 2: Device/function related commands 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-150, "disp_gclk_avgs" on page 2-248. 2-252 GMR-01 68P02901W23-P 23 Feb 2004 Technical Description BSS Command Reference disp_gsm_cells 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 Command type A (no operator actions) Prerequisites None Format Syntax disp_gsm_cells <location> Input parameter location Specifies the site for which associated GSM cells are to be displayed: 0 or bsc BSC 1 to 120 BTS Examples Example 1 In this example, no GSM cells are associated with the BSC: disp_gsm_cells 0 Where: is: 0 68P02901W23-P 23 Feb 2004 location 2-253 GMR-01 disp_gsm_cells Chapter 2: Device/function related commands 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 MCC --543 543 543 MNC --21 21 21 LAC --------------61713 (0xF111h) 61713 (0xF111h) 61713 (0xF111h) Number of Sectors: CI Local -------------- ----4368 (0x1110h) 0 8736 (0x2220h) 1 13114 (ox222Ah) 2 Freq Type ------EGSM EGSM EGSM Cell Name ------------london-south london-north bexley-west 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 2-254 GMR-01 68P02901W23-P 23 Feb 2004 Technical Description BSS Command Reference disp_gsm_cells References Related commands "add_cell" on page 2-21, "copy_cell" on page 2-156, "del_cell" on page 2-168, "disp_cell" on page 2-205. 68P02901W23-P 23 Feb 2004 2-255 GMR-01 disp_hdlc Chapter 2: Device/function related commands disp_hdlc Description The disp_hdlc command displays the HDLC channel assignment types of an in-service GPROC device or function. This command permits retrieval of: • Device, function and CPU values. • The channel configuration and status for every HDLC channel on a GPROC device. • The total number of LAPD devices (RSLs or XBLs) equipped on a GPROC device. • An indication whether the current HDLC layout matches the current database settings. • Channels allocated to GSLs when the GPRS feature is unrestricted at the site. Security level 1 Supported by OMC-R GUI No Command type A (no operator actions) Prerequisites The disp_hdlc command cannot be used for CSPF GPROCs or M-Cell sites. Format Syntax disp_hdlc <location> <device/function name> <dev_func_id_1> <dev_func_id_2> <dev_func_id_3> Input parameters location Specifies the equipment location: 0 or bsc BSC 1 to 120 BTS all All sites dev/func name 2-256 GMR-01 68P02901W23-P 23 Feb 2004 Technical Description BSS Command Reference disp_hdlc 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 0 device / function ID 0 device / function ID System response Device: BSP 0 0 0 (CPU ID: 0x0115) Function: N/A Number of LAPD Static Links (RSLs/XBLs) allocated to current board: HDLC Channel Range -----------00-03 04-07 08-11 12-15 1 HDLC Channel Offset 0 1 2 3 ---------------------------------------------------Test Free OML 0 0 0 OML Free OML Free OML Free XBL 0 0 0 RSL Free RSL Free RSL Free RSL Free RSL Free RSL Free 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: 68P02901W23-P 23 Feb 2004 2-257 GMR-01 disp_hdlc Chapter 2: Device/function related commands disp_hdlc bsc LCF 0 0 0 Where: is: bsc location LCF device / function ID 0 device / function ID 0 device / function ID 0 device / function ID System response Device: GPROC 0 0 0 (CPU ID: 0x0114) Function: LCF 0 0 0 Number of LAPD Legend: G/RSL HDLC Channel Range -----------00-03 04-07 08-11 12-15 Static Links (RSLs/XBLs) allocated to current board: 4 - Free channel configured for a GSL or RSL HDLC Channel Offset 0 1 2 3 ----------------------------------------------------Test Free MTL 0 0 0 RSL 32 0 0 RSL Free RSL Free RSL Free RSL Free RSL Free RSL Free RSL Free RSL Free RSL Free RSL Free RSL Free RSL Free 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 0 device / function ID 0 device / function ID 0 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: HDLC Channel Range -----------00-03 04-07 08-11 12-15 4 HDLC Channel Offset 0 1 2 3 -----------------------------------------------------Test Free MTL 0 0 0 RSL 32 0 0 RSL Free RSL Free RSL Free RSL Free RSL Free RSL Free RSL Free RSL Free RSL Free RSL Free RSL Free RSL Free RSL Free 2-258 GMR-01 68P02901W23-P 23 Feb 2004 Technical Description BSS Command Reference disp_hopping 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 Supported by OMC-R GUI Yes Command type B (operator actions required) Prerequisites This command is not allowed while in SYSGEN ON mode when the “active" option is used. Operator actions Place the system in the SYSGEN OFF mode if the “active" option is used before entering this command. 68P02901W23-P 23 Feb 2004 2-259 GMR-01 disp_hopping Chapter 2: Device/function related commands 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=. The format for the GSM Cell ID depends on: • The system used (PGSM, EGSM, DCS1800, PCS1900) • Whether the seven parameter GSM Cell ID format or the four parameter GSM Cell ID format has been enabled. The name of the cell created using the cell_name command may be entered in place of the cell_number. When the cell name is entered, it must be placed inside double quotation marks and 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. fhi Frequency hopping indicator. active The active option displays the currently active hopping systems. 2-260 GMR-01 68P02901W23-P 23 Feb 2004 Technical Description BSS Command Reference disp_hopping Examples Example 1 In this example, only the GSM Cell ID in seven parameter format is entered and the related hopping information for the cell is displayed. disp_hopping cell_number=5 4 3 2 1 61986 34944 Where: is: 5 4 3 2 1 61986 34944 cell_desc The example below shows the same cell number in four parameter format: disp_hopping cell_number=543 21 61986 34944 Where: is: 543 21 61986 34944 cell_desc System response GSM CELL: 543 21 61986 (f222h) 34944 (8880h) Baseband (BBH) Hopping FHI: 0 HSN = 0 MA = 12 30 45 FHI: 1 HSN = 7 MA = 31 37 50 FHI: 2 HSN = 9 MA = 31 32 33 34 45 46 FHI: 3 HSN = 12 MA = 33 76 91 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) Carrier arfcn: 33 Timeslots: Carrier arfcn: 76 Timeslots: Carrier arfcn: 91 Timeslots: 34944 (8880h) 0 1 1 2 3 5 7 0 1 2 3 4 5 6 7 Example 3 In this example, there are no associated hopping systems. 68P02901W23-P 23 Feb 2004 2-261 GMR-01 disp_hopping Chapter 2: Device/function related commands 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: FHI: 1 (Disabled) HSN: 0 MA: FHI: 2 (Disabled) HSN: 0 MA: FHI: 3 (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. 2-262 GMR-01 68P02901W23-P 23 Feb 2004 Technical Description BSS Command Reference disp_hopping References Related command "chg_element" on page 2-94. 68P02901W23-P 23 Feb 2004 2-263 GMR-01 disp_level Chapter 2: Device/function related commands disp_level Description The disp_level command displays the current security level. Security level 1 Supported by OMC-R GUI No Command type A (no operator actions) Prerequisites None Format Syntax disp_level Input parameters There are no input parameters associated with this command. 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-114, "sysgen_mode" on page 2-466. 2-264 GMR-01 68P02901W23-P 23 Feb 2004 Technical Description BSS Command Reference disp_link 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 Supported by OMC-R GUI No Command type A (no operator actions) Prerequisites This command is only available on an RXCDR. Format Syntax disp_link Input parameters There are no input parameters associated with this command. 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 Incoming incoming incoming incoming incoming incoming incoming incoming incoming 68P02901W23-P 23 Feb 2004 nailed connections are as follows:mms id: 0 0 Timeslot: 16 Outgoing mms id: 0 0 Timeslot: 17 Outgoing mms id: 0 0 Timeslot: 18 Outgoing mms id: 0 0 Timeslot: 19 Outgoing mms id: 0 0 Timeslot: 20 Outgoing mms id: 0 0 Timeslot: 21 Outgoing mms id: 0 0 Timeslot: 22 Outgoing mms id: 0 0 Timeslot: 23 Outgoing mms id: 0 0 Timeslot: 24 Outgoing MMS MMS MMS MMS MMS MMS MMS MMS MMS Id Id Id Id Id Id Id Id Id 1 1 1 1 1 1 1 1 1 0 0 0 0 0 0 0 0 0 Timeslot: Timeslot: Timeslot: Timeslot: Timeslot: Timeslot: Timeslot: Timeslot: Timeslot: 16 17 18 19 20 21 22 23 24 2-265 GMR-01 disp_link Chapter 2: Device/function related commands incoming mms id: 0 0 Timeslot: 25 Outgoing MMS Id 1 0 Timeslot: 25 Finished displaying all nailed connections 2-266 GMR-01 68P02901W23-P 23 Feb 2004 Technical Description BSS Command Reference disp_link_usage disp_link_usage Description The disp_link_usage command displays all PATH devices equipped through a particular MSI/MMS combination at a site. The output from this command is system configuration dependent. Security level 1 Supported by OMC-R GUI Yes Command type A (no operator actions) Prerequisites An MSI and an MMS must be equipped at the site_device. Format Syntax disp_link_usage <location> <MSI_identifier> <MMS_identifier> Input parameters location Specifies the location of PATH device: 0 or bsc Indicates that the MSI/MMS combination is at the BSC 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. 68P02901W23-P 23 Feb 2004 2-267 GMR-01 disp_link_usage Chapter 2: Device/function related commands 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 PATH PATH PATH PATH PATH PATH PATH PATH 1 2 3 4 5 6 7 8 9 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 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 2-268 GMR-01 68P02901W23-P 23 Feb 2004 Technical Description BSS Command Reference disp_mms_ts_usage 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. 68P02901W23-P 23 Feb 2004 2-269 GMR-01 disp_mms_ts_usage Chapter 2: Device/function related commands The display includes the device or function identifiers and the site where the device or function is equipped. Security level Any Supported by OMC-R GUI Yes Command type A (no operator actions) Prerequisites To display timeslot usage at a PCU, the GPRS feature must be unrestricted. Format Syntax disp_mms_ts_usage <location> <mms_id1> <mms_id2> Input parameters location Specifies the location of the device: 0 or bsc BSC 1 to 120 BTS pcu, pcu_0 to pcu_2 {4040} PCU mms_id1 Specifies the 1st digit of the MMS identifier, accordingly: 0 to 5: 0 to 1 is valid for MMS range for MCell-2 0 to 3 is valid for MMS range for MCell-6 0 is valid for MMS for MCell micro mms_id2 Specifies the 2nd digit of the MMS identifier. The header in the display depends on where the MMS is being viewed. • If the MMS is viewed from a BSC and RXCDR, the header looks like this: TS Port Size Usage State RTF Site RTF • TS Group Device ID TS Type Site CIC If the MMS is viewed from a BTS, the header looks like this: Usage Device ID Type 2-270 GMR-01 Site TS 68P02901W23-P 23 Feb 2004 Technical Description BSS Command Reference • disp_mms_ts_usage Site: If the MMS is for an HDSL link, only the top line of the display changes slightly to look like this: 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 0 1 2 3 68P02901W23-P 23 Feb 2004 Port Size 0-1 2-3 4-5 6-7 0-1 2-3 4-5 6-7 0-1 2-3 4-5 Usage Device ID Type Site UNAVAILABLE Ater* Ater* Ater* Ater* Ater* Ater* Ater* Ater* Ater Ater Ater CIC 1 2 3 4 5 6 7 8 9 10 State RTF Site RTF TS IDLE IDLE IDLE IDLE IDLE IDLE IDLE IDLE IDLE IDLE IDLE 2-271 GMR-01 Example 2 This example displays the output on a RXCDR MMS showing the status of Ater channels. the Ater channel status.disp_mms_ts_usage Chapter 2: Device/function related commands 6-7 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 0-7 0-1 2-3 4-5 6-7 0-7 0-7 0-7 0-7 0-7 0-7 0-7 0-7 0-7 0-7 0-7 0-7 0-7 0-7 0-7 0-7 0-7 0-7 0-7 0-7 0-7 0-7 0-7 0-7 Ater*: Ater 64K_XBL Ater Ater Ater Ater Ater Ater Ater Ater Ater Ater Ater Ater Ater Ater Ater Ater MTL Ater Ater Ater Ater Ater Ater Ater Ater Ater Ater Ater Ater Ater IDLE 128 0 0 64K 0 IDLE IDLE IDLE IDLE IDLE IDLE IDLE IDLE IDLE IDLE IDLE IDLE IDLE IDLE IDLE IDLE 0 0 0 0 IDLE IDLE IDLE IDLE IDLE IDLE IDLE IDLE IDLE IDLE IDLE IDLE IDLE Timeslot is an Ater but has CIC(s) equipped on it. and CICs assigned to the Ater channels: disp_mms_ts_usage 0 0 0 Where: is: 0 location 0 1st digit of MMS identifier 0 2nd digit of MMS identifier System response Start of Report: Site: 0 MMS: 0 0 Timeslot Group 0 0 1 2 3 Usage Ater State STATIC MISMATCH INUSE IDLE 2-272 GMR-01 CIC 58 60 62 70 MMS 1 0 1 0 1 0 1 0 Timeslot 9 10 11 12 Group 68P02901W23-P 23 Feb 2004 . End of Report. 68P02901W23-P 23 Feb 2004 Type 16 64 Site CIC 0 0 Group Group CIC State RTF Site RTF TS TS 3 2-273 GMR-01 . Example 3 This example displays a BSC MMS for an RTF at a dynamic site: disp_mms_ts_usage 0 0 0 Where: is: 0 location 0 1st digit of MMS identifier 0 2nd digit of MMS identifier System response Start of Report: Site: 0 MMS: 0 0 General Timeslot Usage: TS Usage Device ID 0 UNAVAILABLE 4 UNUSED 5 UNUSED 6 UNUSED 7 UNUSED 8 XBL 1 0 0 9 XBL 2 0 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.Technical Description BSS Command Reference 1 0 1 2 3 disp_mms_ts_usage Ater IDLE IDLE IDLE IDLE 71 72 73 74 1 1 1 1 0 0 0 0 13 14 15 17 End of Report. with a 16 kbit/s XBL equipped on timeslot 8. disp_mms_ts_usage 0 0 0 Where: is: 0 location 0 1st digit of MMS identifier 0 2nd digit of MMS identifier System response: Site: 0 MMS: 0 0 General Timeslot Usage: TS Usage Device ID 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 UNAVAILABLE CIC CIC CIC CIC CIC CIC CIC CIC CIC NAILED UNUSED UNUSED RESERVED CIC CIC CIC XBL XBL UNUSED UNUSED UNUSED UNUSED UNUSED UNUSED MTL NAILED UNUSED UNUSED UNUSED UNUSED UNUSED UNUSED UNUSED UNUSED UNUSED UNUSED UNUSED UNUSED Type Site CIC 60 61 62 63 64 65 66 67 68 Group Group 0 1 2 3 0 1 2 3 0 CIC State RTF Site TS TS IDLE IDLE IDLE IDLE IDLE IDLE IDLE IDLE IDLE 0 1 0 11 64 65 66 1 0 0 2 0 0 RTF 16 64 3 0 0 1 0 0 0 0 0 1 2 3 IDLE IDLE IDLE 0 17 2-274 GMR-01 68P02901W23-P 23 Feb 2004 .disp_mms_ts_usage Chapter 2: Device/function related commands Example 4 The following example displays the timeslot utilization on MMS 0 0 at the BSC. group 3 and a 64 kbit/s XBL equipped on timeslot 9. disp_mms_ts_usage 0 0 0 Where: is: 0 location 0 1st digit of MMS identifier 0 2nd digit of MMS identifier Start of Report: Site: 0 MMS: 0 0 General Timeslot Usage: TS Usage 0 1 UNAVAILABLE RSL 0 0 0 16K DYN RES 0 0 0 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 68P02901W23-P 23 Feb 2004 Device ID UNUSED RSL 0 3 0 16K DYN RES 0 2 0 UNUSED UNUSED UNUSED UNUSED UNUSED UNUSED UNUSED UNUSED UNUSED UNUSED UNUSED UNUSED UNUSED UNUSED UNUSED UNUSED UNUSED UNUSED UNUSED UNUSED UNUSED UNUSED UNUSED RSL DYNET 0 0 0 0 0 0 Type 16K 16K 64K Site CIC Group Group CIC RTF State TS Site RTF TS 1 1 2 3 1 None 1 1 2 3 1 None 1 0 None 0 0 0 2 0 0 0 4 0 0 0 5 0 0 0 7 1 3 2-275 GMR-01 .Technical Description BSS Command Reference disp_mms_ts_usage 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. disp_mms_ts_usage Chapter 2: Device/function related commands 1 2 29 30 31 End RSL RTF RTF of Report. 0 0 0 0 0 0 0 0 0 64K FULL FULL None None 3 None 2 2 2 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 6 1st digit of MMS identifier 0 2nd digit of MMS identifier System response Start of Report: Site: PCU_0 MMS: 6 0 General Timeslot Usage: TS 0 1 5 6 4 5 6 7 8 9 10 11 12 13 14 15 17 18 19 20 21 22 23 24 25 26 27 28 29 30 Usage Device ID UNAVAILABLE GSL 0 0 0 UNUSED UNUSED UNUSED UNUSED UNUSED UNUSED XBL 1 0 0 XBL 2 0 0 UNUSED UNUSED UNUSED UNUSED UNUSED UNUSED UNUSED UNUSED UNUSED UNUSED UNUSED UNUSED UNUSED UNUSED UNUSED UNUSED UNUSED UNUSED UNUSED UNUSED Type Site CIC Group Group CIC State RTF Site RTF TS TS PCU_0 16 64 2-276 GMR-01 0 0 3 68P02901W23-P 23 Feb 2004 . Technical Description BSS Command Reference 31 disp_mms_ts_usage UNUSED Remote Transcoder Timeslot Usage: Timeslot Group Usage 1 0 ADD_CHANNEL 1 2 3 2 0 ADD_CHANNEL 1 2 3 3 0 ADD_CHANNEL 8 0 ADD_CHANNEL 1 2 16 RXCDR LINK MMS Timeslot Group 1 0 9 10 11 12 1 0 13 14 15 17 1 0 18 1 0 20 21 22 16 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 End of Report. Example 7 {4040} 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 6 1st digit of MMS identifier 0 2nd digit of MMS identifier System response Start of Report: Site: PCU_0 MMS: 6 0 General Timeslot Usage: TS Usage Device ID 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 68P02901W23-P 23 Feb 2004 UNAVAILABLE UNUSED GBL GBL GBL GBL GBL GBL GBL GBL GBL GBL UNUSED UNUSED UNUSED UNUSED 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 Site PCU_0 PCU_0 PCU_0 PCU_0 PCU_0 PCU_0 PCU_0 PCU_0 PCU_0 PCU_0 2-277 GMR-01 . MMS 1 0 where RTF 0 2 0 is a Half-Rate carrier. Example 8 {4322} This example displays a timeslot usage on a span at site 3. disp_mms_ts_usage 3 1 0 Where: is: 3 location 1 1st digit of MMS identifier 0 2nd digit of MMS identifier System Response Start of Report: Site: 3 MMS: 1 0 General Timeslot Usage: TS Group 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 Usage UNAVAILABLE 64K_RSL UNUSED UNUSED UNUSED UNUSED UNUSED UNUSED UNUSED UNUSED NAILED NAILED NAILED NAILED NAILED NAILED NAILED UNUSED Device ID Type Site 0 0 0 64K 3 3 3 3 3 3 3 3 0 0 0 0 0 0 0 0 0 0 0 0 0 0 2-278 GMR-01 TS 7 8 9 10 11 12 13 68P02901W23-P 23 Feb 2004 .disp_mms_ts_usage Chapter 2: Device/function related commands 16 UNUSED 17 UNUSED 18 UNUSED 19 UNUSED 20 UNUSED 21 UNUSED 22 UNUSED 23 UNUSED 24 UNUSED 25 UNUSED 26 UNUSED 27 UNUSED 28 UNUSED 29 UNUSED 30 UNUSED 31 UNUSED End of Report. where non-BCCH RTF 0 0 has 64k channels allocated.0 at site 1. and RTF 2 0 has 32k channels allocated: disp_mms_ts_usage 1 0 0 Where: is: 1 location 0 1st digit of MMS identifier 0 2nd digit of MMS identifier System Response Start of Report: Site: 1 MMS: 0 0 General Timeslot Usage: TS Group 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 68P02901W23-P 23 Feb 2004 Usage UNAVAILABLE 64K_RSL UNUSED UNUSED UNUSED UNUSED UNUSED UNUSED UNUSED UNUSED UNUSED UNUSED UNUSED UNUSED UNUSED UNUSED UNUSED UNUSED RTF RTF Device ID 1 0 0 2 0 0 2 0 0 Type 64K FULL FULL Site TS 1 1 1 2-279 GMR-01 .Technical Description BSS Command Reference 18 UNUSED 20 UNUSED 21 UNUSED 22 UNUSED 23 UNUSED 24 RTF 25 RTF 26 RTF 27 RTF 28 RTF 29 RTF 30 RTF 31 RTF End of Report disp_mms_ts_usage 0 0 0 0 0 0 0 0 3 3 2 2 2 2 1 1 0 0 0 0 0 0 0 0 FULL FULL FULL FULL FULL FULL FULL FULL 3 3 3 3 3 3 3 3 Example 9 {23658} This example displays a timeslot usage of MMS 0. RTF 1 0 has 16k channels allocated. disp_mms_ts_usage Chapter 2: Device/function related commands 20 RTF 21 RTF 22 RTF 23 RTF 24 RTF 25 RTF 26 RTF 27 RTF 28 RTF 29 RTF 30 RTF 31 RTF End of Report 2 2 1 1 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 0 0 FULL FULL FULL FULL FULL FULL FULL FULL FULL FULL FULL FULL 1 1 1 1 1 1 1 1 1 1 1 1 References Related information The timeslots states display as UNKNOWN due to SM not running. Related command "chg_ts_usage" on page 2-137. 2-280 GMR-01 68P02901W23-P 23 Feb 2004 . A state of UNEQUIPPED indicates no circuits are equipped on the timeslot. The cell_name for an external neighbour cell will not be displayed. PCS1900) 2-281 GMR-01 . An internal neighbour cell is inside the BSS in which the source cell is located. the Inter-RAT handover feature must be unrestricted.Technical Description BSS Command Reference disp_neighbor disp_neighbor Description The disp_neighbor command displays information of a specific neighbour cell or all neighbour cells. If a cell_name has not been assigned to a neighbor_cell_id. 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. EGSM. the cell_name for each of the internal neighbour cells will be displayed immediately after the neighbor_cell_id. When the all option is used. GSM or UTRAN Cell ID of the neighbour list owner cell to be displayed. No Name Defined will be presented in the Neighbour cell name field. 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. this command supports the UMTS UTRAN cell identity format. The format for the GSM Cell ID depends on: • 68P02901W23-P 23 Feb 2004 The system used (PGSM. DCS1800. If a neighbour cell is an external cell. Security level 1 Supported by OMC-R GUI Yes Command type A (no operator actions) Prerequisites For handovers to UMTS UTRAN cells. N/A. If the Inter_RAT (Radio Access Technology) handover feature is unrestricted. will be presented in the Neighbour cell name field. A cell_name may not be used to specify an external neighbour cell. An external neighbour cell is outside of the BSS in which the source cell is located. A neighbour cell may be internal or external. A cell_name may also be used to specify an internal neighbour cell in place of the neighbor_cell_id. The name of the cell created using the cell_name command may be entered in place of the cell_number. and a test cell number (1 to 64). When the cell name is entered. Examples The examples below are possible displays. a cell has no neighbour cells.disp_neighbor Chapter 2: Device/function related commands • Whether the seven parameter GSM Cell ID format or the four parameter GSM cell ID format has been enabled. DCS1800. This argument is entered using the string TEST. 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. a space. 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 2-282 GMR-01 68P02901W23-P 23 Feb 2004 . 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. Refer to the description of the add_neighbor command for the prompted power budget parameter values. When the cell name is entered. it must be placed inside double quotation marks. An asterisk character (*) may be used in place of a test cell number to indicate all test neighbours. PCS1900) • Whether the seven parameter GSM Cell ID format or the four parameter GSM cell id format has been enabled. The format for the GSM Cell ID depends on: • The system used (PGSM. Example 1 In this example. test neighbor_cell_desc A test cell may be created to be used for testing. the system will present additional prompts. it must be placed inside double quotation marks. EGSM. disp_neighbor "london-north" all Where: 68P02901W23-P 23 Feb 2004 is: london-north cell_name all all internal neighbour cells 2-283 GMR-01 .Technical Description BSS Command Reference disp_neighbor System response There are no associated neighbor cells Example 2 In this example. The cell name “london-north” is used in place of the src_cell_desc. 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: Neighbor cell name: Neighbor cell frequency type: Placement: Synchronization enabled: Frequency in the ba_sacch list: Frequency in the ba_bcch list: BCCH frequency number: Base station identity code: MS transmit power maximum: Neighbor receive level minimum: Neighbor handover margin: Power budget surrounding cell hreqave: Receive quality handover margin: Receive level handover margin: Neighbor type 5 handover margin: Neighbor adaptive handover pbgt trigger: Adjacent channel interference test enabled: Power budget algorithm type: Neighbor congestion handover margin: Range of the neighbor cell: 001 01 1 (0001h) 1 (0001h) N/A PGSM External N/A 1 (yes) 1 (yes) 60 16 37 15 8 8 -63 -63 63 40 0 (no) 1 8 Normal End of report Example 3 In this example. the information describing all of the neighbour cells displays. disp_neighbor Chapter 2: Device/function related commands System response Neighbor cell id: Neighbor cell name: Placement: Synchronization enabled: Frequency in the ba_sacch list: Frequency in the ba_bcch list: BCCH frequency number: Base station identity code (bsic): MS transmit power maximum: Neighbor receive level minimum: Neighbor handover margin: Power budget surrounding cell hreqave: Adjacent channel interference test enabled: Power budget algorithm type: Adjacent channel intf detection ho margin: Neighbor congestion handover margin: 5 4 3 2 1 633 347 london-south Internal 1 1 0 60 16 37 15 8 9 0 (no) 7 -5 -8 Neighbor cell id: Neighbor cell name: Placement: Synchronization enabled: Frequency in the ba_sacch list: Frequency in the ba_bcch list: BCCH frequency number: Base station identity code (bsic): MS transmit power maximum: Neighbor receive level minimum: Neighbor handover margin: Power budget surrounding cell hreqave: Adjacent channel interference test enabled: Power budget algorithm type: Adjacent channel intf detection ho margin: Neighbor congestion handover margin: 5 4 3 2 1 633 348 No Name Defined Internal 1 1 0 60 16 37 15 8 9 0 (no) 7 -5 -8 Neighbor cell id: Neighbor cell name: Placement: Synchronization enabled: Frequency in the ba_sacch list: Frequency in the ba_bcch list: BCCH frequency number: Base station identity code (bsic): MS transmit power maximum: Neighbor receive level minimum: Neighbor handover margin: Power budget surrounding cell hreqave: Adjacent channel interference test enabled: Power budget algorithm type: Adjacent channel intf detection ho margin: 5 4 3 2 1 633 349 N/A External N/A 1 0 100 50 37 15 8 9 0 (no) 7 -5 Example 4 This example displays the information for all test cells. 2-284 GMR-01 68P02901W23-P 23 Feb 2004 . Technical Description BSS Command Reference disp_neighbor 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 MCC MNC LAC CI -------------------------------TEST 7 TEST 12 LOC --N/A N/A SYNC ---N/A N/A BA SACCH ----NO YES BA BCCH ---YES YES BCCH FREQ ---91 101 BSIC ---N/A 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: 0010111 src_cell_desc 0010112 neighbor_cell_desc System response Neighbor cell id: Neighbor cell name: Neighbor cell frequency type: Placement: Synchronization enabled: Frequency in the ba_sacch list: Frequency in the ba_bcch list: BCCH frequency number: Base station identity code: MS transmit power maximum: Neighbor receive level minimum: Neighbor handover margin: Power budget surrounding cell hreqave: Receive quality handover margin: Receive level handover margin: Neighbor type 5 handover margin: Neighbor adaptive handover pbgt trigger: Adjacent channel interference test enabled: Power budget algorithm type: Neighbor congestion handover margin: Range of the neighbor cell: 001 01 1 (0001h) 2 (0002h) N/A PGSM Internal 0 (no) 1 (yes) 1 (yes) 60 16 37 15 8 8 -63 -63 63 40 0 (no) 1 8 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. 68P02901W23-P 23 Feb 2004 2-285 GMR-01 . ------001 01 1 (0001h) 6 (0006h) INT NO X X X 001 01 1 (0001h) 3 (0003h) INT NO X X X 001 01 1 (0001h) 33 (0021h) INT NO X X X 001 01 1 (0001h) 41 (0029h) INT NO X X X 001 01 1 (0001h) 11 (000Bh) EXT N/A X X X 001 01 1 (0001h) 90 (005Ah) EXT N/A X X X FREQ BCCH TYPE FREQ BSIC ------. "disp_gsm_cells" on page 2-253.---. "copy_cell" on page 2-156. "disp_cell" on page 2-205. "add_neighbor" on page 2-35. "del_cell" on page 2-168.---.--. 2-286 GMR-01 68P02901W23-P 23 Feb 2004 .---PGSM 75 16 PGSM 30 16 PGSM 10 16 PGSM 90 16 EGSM 80 16 PGSM 17 16 End of report References Related commands "add_cell" on page 2-21.disp_neighbor Chapter 2: Device/function related commands disp_neighbor 0 0 1 0 1 1 1 Where: is: 0010111 src_cell_desc System response Start of neighbor report: S A B G C C P GSM CELL ID C C R MCC MNC LAC CI LOC SYNC H H S ---------------------------------. pcu_1 or pcu_2 at which the GBL is defined. Examples Example 1 The following example displays NSVCI 68: 68P02901W23-P 23 Feb 2004 2-287 GMR-01 . the display still shows the headings. GBL Specifies the GBL as defined by value. pcu_id {4040} Specifies the pcu.) Format Syntax {4040} disp_nsvc <NS_VCI> <value>|<pcu_id> <GBL> <value> Input parameters NS_VCI Specifies the NSVCI as defined by value. pcu_0. value Varies according to the option chosen above. Security level 1 Supported by OMC-R GUI Yes Command type A (no operator action) Prerequisites None (If GPRS is restricted.Technical Description BSS Command Reference disp_nsvc disp_nsvc Description The disp_nsvc command displays the requested NSVCs and their configurations. ---.---64 64 64 64 End of Report.--15 0 0 16 1 0 STATUS ---------GBL OOS Unblocked DLCI ----22 22 BC ---0 0 BE CIR ---.---.--15 0 0 16 1 0 STATUS ---------Unblocked Unblocked DLCI ----22 22 BC ---0 0 BE ---64 64 CIR ---64 64 End of Report. Example 3 {4040} 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 2-288 GMR-01 68P02901W23-P 23 Feb 2004 . 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 {4040} Start of Report: NS-VCI -----68 68 NSEI PCU GBL ---.disp_nsvc Chapter 2: Device/function related commands disp_nsvc NS_VCI 68 Where: is: NS_VCI NSVCI 68 NSVCI ID System response {4040} Start of Report: NS-VCI -----68 68 NSEI PCU GBL ---. 68P02901W23-P 23 Feb 2004 2-289 GMR-01 . "del_nsvc" on page 2-177. References Related commands "add_nsvc" on page 2-43.Technical Description BSS Command Reference disp_nsvc System response Start of Report: Site: PCU_1 NS Access Rate: GBL --0 NS-VCI ------68 27 102 198 10 23 21 78 69 64 STATUS ---------PCU OOS PCU OOS PCU OOS PCU OOS PCU OOS PCU OOS PCU OOS PCU OOS PCU OOS DLCI ----22 239 91 240 16 200 204 119 213 BC ---0 0 0 0 0 0 0 0 0 BE ---64 64 64 64 64 64 64 64 64 CIR ---64 64 64 64 64 64 64 64 64 End of Report. only the unrestricted options are displayed. only the unrestricted options are displayed.disp_options Chapter 2: Device/function related commands disp_options Description The disp_options command displays the unrestricted and restricted optional features. Security level 1 Supported by OMC-R GUI Yes Command type A (no operator actions) Prerequisites None Format Syntax disp_options [all] Input parameter all Displays both the unrestricted and restricted options. 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 2-290 GMR-01 68P02901W23-P 23 Feb 2004 . If this parameter is not entered. Examples Example 1 In this example. Technical Description BSS Command Reference 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 47 48 49 50 51 52 53 54 55 56 57 58 59 disp_options Reserved Timeslots SMS Cell Broadcast (Multiple Background Messages) SMS Point to Point Preventative Cyclic Retransmission Microcell Extended GSM 900 SMS Cell Broadcast (CBC Support) Add Nail Connections Directed Retry Alternative Congestion Relief Level 3 Password A5_1 Encryption A5_2 Encryption A5_3 Encryption A5_4 Encryption A5_5 Encryption A5_6 Encryption A5_7 Encryption RTF-PATH Fault Containment Sub-Equipped RTF 16Kbps LAPD RSL 16Kbps LAPD XBL Infrastructure sharing Homogeneous Cabinet Infrastructure Sharing Heterogeneous Cabinet MultiBand Inter-Cell Handover Concentric Cells Aggregate Abis Extended Range Cells Downloadable Transcoder Volume Control (Uplink and Downlink) Enhanced Full Rate Fast GCLK Warmup Integrated M-Cell HDSL Interface BTS Concentration General Packet Radio Service Dual Band Cells 900/1800 Horizonmicro2 / Horizoncompact2 Enhanced Circuit Error Rate Monitor Network Controlled Cell Reselection LoCation Services Coding Scheme 3&4 Enabled Enhanced One Phase Access Enhanced Capacity BSC InterRAT Handover 2G>3G Cell Relocation 3G>2G Dedicated Mode Adaptive Multi-Rate AMR Using Enhanced GDP {3723} PBCCH/PCCCH {4449} Seamless Cell Reselection AMR Enhanced Capacity TCU-A Support for AMR TCU-B Support for AMR {4441} Prp Capacity {23658} Enhanced General Packet Radio Service Example 2 In this example. both the unrestricted and restricted options are displayed. 68P02901W23-P 23 Feb 2004 2-291 GMR-01 . 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 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 2-292 GMR-01 68P02901W23-P 23 Feb 2004 .disp_options Chapter 2: Device/function related commands disp_options all Where: is: all all options System response The following optional features have unrestricted use: -------------------------------------------------------------------1 A & Um Interface . GSM Phase 2 .. disp_options all Where: is: all all options The following optional features have unrestricted use: --------------------------------------------------------------------1 A & Um Interface .GSM Phase 2 . .. 43 Enhanced Circuit Error Rate Monitor . 59 {23658} Enhanced General Packet Radio Service The following optional features have restricted use: --------------------------------------------------------------------- 68P02901W23-P 23 Feb 2004 2-293 GMR-01 . .... disp_options all Where: is: all all options The following optional features have unrestricted use: --------------------------------------------------------------------1 A & Um Interface ... . . the operator performs the disp_options command when only the Enhanced Circuit Error Rate Monitor feature is restricted..... .Technical Description BSS Command Reference 52 53 54 55 56 57 58 59 disp_options AMR Using Enhanced GDP {3723} PBCCH/PCCCH {4449} Seamless Cell Reselection AMR Enhanced Capacity TCU-A Support for AMR TCU-B Support for AMR {4441} Prp Capacity {23658} Enhanced General Packet Radio Service The following optional features have restricted use: --------------------------------------------------------------------46 ALM for EGSM carriers Example 3 In this example. 59 {23658} Enhanced General Packet Radio Service The following optional features have restricted use: --------------------------------------------------------------------43 Enhanced Circuit Error Rate Monitor Example 4 In this example... the operator performs the disp_options command when no features are restricted.... pcu_0 to pcu_2 {4040} PCU all All locations 2-294 GMR-01 68P02901W23-P 23 Feb 2004 .disp_processor Chapter 2: Device/function related commands disp_processor Description The disp_processor command displays the status of all processor boards at a specific site or all sites. At M-Cell and Horizonmacro sites. The Related Device and Related Function columns are not applicable to M-Cell sites. DRI IDs. At InCell sites. CPU numbers. and associated RTFs (if any). Format Syntax disp_processor <location> Input parameter location Indicates the number of the BTS or the BSC where the processor(s) are located. this command also displays the related devices and functions associated with the processors. Security level 1 Supported by OMC-R GUI Yes Command type A (no operator actions) Prerequisites This command is not allowed while in SYSGEN ON mode or during site initialization. 0 or bsc BSC 1 to 120 BTS pcu. If a DRI is not detected at the MCU ASIC. this command displays transceivers. the Off LAN value displays. the No Sync value displays. If a GPROC is not detected on the LAN in InCell sites. disp_processor 1 Where: is: 1 an M-Cell site id System response PROCESSOR STATUS INFORMATION FOR LOCATION 1: OPER STATES: D:Disabled E:Enabled B:Busy ADMIN STATES: L:Locked U:Unlocked E:Equipped NE: Not Equipped Related 68P02901W23-P 23 Feb 2004 Related 2-295 GMR-01 .--------1015 BTP 0 0 B-U NO REASON DRI 0 1 DRI 0 0 1019 CSFP 0 0 (Off LAN) D-U NO REASON N/A Related Function -------RTF 0 0 RTF 0 1 N/A END OF STATUS REPORT Example 2 In this example.----------------.--------------------.Technical Description BSS Command Reference disp_processor Examples Example 1 In this example. the status of all processor boards at all InCell sites displays.----. the status of all processor boards at an M-Cell site displays. disp_processor all Where: is: all all sites System response PROCESSOR STATUS INFORMATION FOR LOCATION 0: OPER STATES: D:Disabled E:Enabled B:Busy ADMIN STATES: L:Locked U:Unlocked E:Equipped NE:Not Equipped CPU# ---0115 0117 0118 011a Related Device --------N/A N/A N/A SITE 1 0 Processor Name -------------------BSP 0 0 CSFP 0 0 GPROC 2 0 (Off LAN) GPROC 1 0 (LCF 0) State ----B-U D-U D-U B-U Reason ----------------NO REASON NO CODE GPROC Not On LAN NO REASON PROCESSOR STATUS INFORMATION FOR LOCATION 2: OPER STATES: D:Disabled E:Enabled B:Busy ADMIN STATES: L:Locked U:Unlocked E:Equipped Related Function -------N/A N/A N/A N/A NE:Not Equipped Related CPU# Processor Name State Reason Device ---. Up to six TRAU GDS devices can be listed under a single DPROC (PICP).-------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 2-296 GMR-01 68P02901W23-P 23 Feb 2004 .-------. System response {4040} MMI-RAM 0115 -> disp_proc pcu_0 PROCESSOR STATUS INFORMATION FOR LOCATION PCU 0: OPER STATES: D:Disabled E:Enabled B:Busy ADMIN STATES: L:Locked U:Unlocked E:Equipped NC: NE:Not Equipped Not Connected CPU# Processor Name State Reason Related Related Device Function ---. the statuses of the GPRS PCU processor boards are displayed.-----.-----------------.disp_processor Chapter 2: Device/function related commands CPU# Processor Name State Reason Device Function --------------------------------------------------------------------1015 BTP 0 0 B-U NO REASON N/A N/A 2001 DRI 0 0 (RTF 0 0) B-U COMB Controller N/A N/A 2002 DRI 0 1 (RTF 0 2) B-U NO REASON N/A N/A 2003 DRI 0 2 (RTF 0 3) B-U NO REASON N/A N/A 2004 DRI 0 3 (RTF 0 1) B-U NO REASON N/A N/A 2005 DRI 0 4 E-L NO REASON N/A N/A 2006 DRI 0 5 (No Sync) D-L NO REASON N/A N/A END OF STATUS REPORT Example 3 In this example.-----------------. {4040} disp_processor pcu_0 Where: is: pcu_0 the first equipped PCU. Technical Description BSS Command Reference disp_processor 1103 DPROC (PICP) 3 0 B-U NO REASON 1104 DPROC (PRP) 4 0 B-U NO REASON 1105 DPROC (PRP) 5 0 B-U NO REASON 1106 DPROC (PRP) 6 0 B-U NO REASON 110b DPROC (PICP) 11 0 B-U NO REASON 110c DPROC (PRP) 12 0 B-U NO REASON 110d DPROC (PRP) 13 0 B-U NO REASON 110e DPROC (PRP) 14 0 B-U NO REASON 110f DPROC (PRP) 15 0 B-U NO REASON 1110 DPROC (PRP) 16 0 B-U NO REASON GDS MSI GDS MSI GBL GBL (GDS (GDS (GDS MSI GDS MSI GDS MSI GDS MSI GDS MSI GDS MSI GDS MSI GDS GSL GSL GSL GSL GSL GSL MSI GBL (GDS (GDS (GDS MSI GDS MSI GDS MSI GDS MSI GDS MSI GDS MSI GDS MSI GDS MSI GDS MSI GDS MSI GDS 2 0 14 0 11 0 4 0 2 0 3 0 4 0) 7 0) 3 0) 6 0 3 0 15 0 12 0 7 0 4 0 16 0 13 0 8 0 5 0 17 0 14 0 2 0 1 0 1 0 3 0 5 0 7 0 9 0 11 0 3 0 1 0 8 0) 2 0) 6 0) 9 0 6 0 18 0 15 0 10 0 7 0 19 0 16 0 11 0 8 0 20 0 17 0 12 0 9 0 21 0 18 0 13 0 10 0 22 0 19 0 N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A END OF STATUS REPORT 68P02901W23-P 23 Feb 2004 2-297 GMR-01 . The relays are in the deactivated state. 0 to 7 InCell sites 0 to 15 M-Cell and Horizonmacro sites Example This example displays the relay contacts for all EAS devices: 2-298 GMR-01 68P02901W23-P 23 Feb 2004 . Security level 1 Supported by OMC-R GUI Yes Command type A (no operator actions) Prerequisites The EAS device must be equipped and the EAS device parameters established using the equip command. See "equip" on page 2-327. Format Syntax disp_relay_contact <location> <device_id> Input parameters location Specifies the location of the device: 0 or bsc BSC 1 to 120 BTS device_id Specifies the device ID of the specific PIX card associated with an EAS device.disp_relay_contact Chapter 2: Device/function related commands disp_relay_contact Description The disp_relay_contact command displays the relay state (open or closed circuit) for an EAS device when the device is Busy-Unlocked. as defined during equip EAS. when the EAS is not Busy-Unlocked. Technical Description BSS Command Reference disp_relay_contact disp_relay_contact System response Relay Relay Relay Relay 1: 2: 3: 4: Closed Open Open Closed References Related command "equip" on page 2-327 68P02901W23-P 23 Feb 2004 2-299 GMR-01 . The range of values is 0 to 11. and if capable of supporting EGPRS Security level 1 Supported by OMC-R GUI No Command type A (no operator actions) Prerequisites This command is not allowed while in SYSGEN ON mode. The range of values is 0 to 5. {23658}The display output indicates whether or not the RTF is equipped for GPRS and EGPRS. the word “Extended" is appended to the timeslot number. timeslot_number Specifies the timeslot number. rtf_id_2 The second identifier of the RTF.disp_rtf_channel Chapter 2: Device/function related commands disp_rtf_channel Description The disp_rtf_channel command displays the status of all timeslots or a single timeslot on a carrier. The range of values is 0 to 7. Format Syntax disp_rtf_channel <location> <rtf_id_1> <rtf_id_2> [<timeslot_number>] Input parameter location Specifies the location: 0 or bsc BSC 1 to 120 BTS rtf_id_1 The first identifier of the RTF. When an Extended Range timeslot number is displayed. 2-300 GMR-01 68P02901W23-P 23 Feb 2004 . or from unavailable to active.the timeslot is out of service.Technical Description BSS Command Reference disp_rtf_channel Carrier states The carrier states that can be displayed include: • ACTIVE . • UNAVAILABLE (IBAND) . • RESERVED . • UNAVAILABLE (OPERATOR) .the GPRS timeslot is reserved. • UNAVAILABLE (TERRESTRIAL) .the timeslot is in transition: from active to idle.the timeslot is idle.the operator has subequipped an RTF.the GPRS timeslot is switchable.the timeslot is active. The GPRS types that can be displayed include: • SWITCHABLE . • IDLE .the carrier is unavailable due to a problem with a terrestrial link. or from idle to active. The state of a Packet Data Traffic CHannel (PDTCH) timeslot is always displayed as “N/A". • UNAVAILABLE (HOPPING) . • INTRANS .the timeslot is unavailable due to a poor interference band (Iband).the timeslot is unavailable due to hopping reconfiguration. Examples Example 1 {23658}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: 68P02901W23-P 23 Feb 2004 is: 1 location 0 rtf_id_1 2 rtf_id_2 2-301 GMR-01 . • OOS . but the RTF is currently assigned to a DRI unable to support EGPRS: disp_rtf_channel 1 0 2 Where: is: 1 location 0 rtf_id_1 2 rtf_id_2 2-302 GMR-01 68P02901W23-P 23 Feb 2004 . a single density CTU2): disp_rtf_channel 1 0 0 Where: is: 1 location 0 rtf_id_1 0 rtf_id_2 System response Start of report for RTF 0 0 at location 1: Packet Radio Capabilities: 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 2 (TCH/F) N/A 0 ACTIVE 3 (64k PDTCH) Switchable 0 N/A 4 (64k PDTCH) Reserved 0 N/A 5 (64k PDTCH) Reserved 0 N/A 6 (64k PDTCH) Reserved 0 N/A 7 (64k PDTCH) Reserved 0 N/A Example 3 {23658}This example displays the status of RTF 0 2 at Site 1 when the RTF is equipped to support EGPRS.disp_rtf_channel Chapter 2: Device/function related commands System response Start of report for RTF 0 2 at location 1: TIMESLOT SUB-CHAN STATE ------------------------------------------------------0 (TCH/F) 0 ACTIVE 1 (TCH/F) 0 ACTIVE 2 (TCH/F) 0 ACTIVE 3 (TCH/F) 0 ACTIVE 4 (TCH/F) 0 ACTIVE 5 (TCH/F) 0 ACTIVE 6 (TCH/F) 0 ACTIVE 7 (TCH/F) 0 ACTIVE Example 2 {23658}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. when the RTF is not configured for EGPRS.Technical Description BSS Command Reference disp_rtf_channel System response Start of report for RTF 0 2 at location 1: Packet Radio Capabilities: 64k RTF currently capable of supporting EGPRS?: NO TIMESLOT GPRS TYPE SUB-CHAN STATE ---------------------------------------------------------------0 (TCH/F) N/A 0 ACTIVE 1 (TCH/F) N/A 0 ACTIVE 2 (TCH/F) N/A 0 ACTIVE 3 (TCH/F) N/A 0 ACTIVE 4 (TCH/F) N/A 0 ACTIVE 5 (TCH/F) N/A 0 ACTIVE 6 (TCH/F) N/A 0 ACTIVE 7 (TCH/F) N/A 0 ACTIVE Example 4 {23658}This example displays the status of RTF 0 2 at Site 1 when EGPRS is restricted and GPRS is unrestricted: 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: Packet Radio Capabilities: none TIMESLOT GPRS TYPE SUB-CHAN STATE ---------------------------------------------------------------0 (TCH/F) N/A 0 ACTIVE 1 (TCH/F) N/A 0 ACTIVE 2 (TCH/F) N/A 0 ACTIVE 3 (TCH/F) N/A 0 ACTIVE 4 (TCH/F) N/A 0 ACTIVE 5 (TCH/F) N/A 0 ACTIVE 6 (TCH/F) N/A 0 ACTIVE 7 (TCH/F) N/A 0 ACTIVE Example 5 This example displays the status of RTF 0 1at site 1. disp_rtf_channel 1 0 0 Where: 68P02901W23-P 23 Feb 2004 is: 1 location 0 rtf_id_1 1 rtf_id_2 2-303 GMR-01 . disp_rtf_channel Chapter 2: Device/function related commands System response Start of report for RTF 0 1 at location 1: Packet Radio Capabilities: none RTF currently capable of supporting EGPRS?: NO TIMESLOT GPRS TYPE SUB-CHAN STATE ---------------------------------------------------------------0 (TCH/F) N/A 0 IDLE 1 (TCH/F) N/A 0 IDLE 2 (TCH/F) N/A 0 ACTIVE 3 (TCH/F) N/A 0 ACTIVE 4 (TCH/F) N/A 0 ACTIVE 5 (TCH/F) N/A 0 ACTIVE 6 (TCH/F) N/A 0 ACTIVE 7 (TCH/F) N/A 0 ACTIVE End of Report. 2-304 GMR-01 68P02901W23-P 23 Feb 2004 . Example 6 This example displays the status of RTF 1 0 at BTS location 12: disp_rtf_channel 12 1 0 Where: is: 12 location 1 rtf_id_1 0 rtf_id_2 System response Start of report for RTF 1 0 at location 12: Packet Radio Capabilities: 16k TIMESLOT GPRS TYPE SUB-CHAN STATE ---------------------------------------------------------------0 (BCCH + SDCCH/4) N/A BCCH ACTIVE 0 IDLE 1 IDLE 2 IDLE 3 IDLE 1 (TCH/F) N/A 0 IDLE 2 (TCH/F) N/A 0 IDLE 3 (TCH/F) N/A 0 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. 68P02901W23-P 23 Feb 2004 2-305 GMR-01 . Security level 1 Supported by OMC-R GUI Yes Command type A (no operator actions) Prerequisites This command is available only on RTF functions that are equipped on a remote BTS. The status of the RTF is shown as Connected or Redundant. All PATHs which could be used to carry the RTF to the BSC are displayed. rtf_id_1 Specifies the 1st RTF identifier. The system shows whether a site supports dynamic allocation. redundant PATHs exist for each DYNET equipped. The range of values is 0 to 11. For closed loop daisy chain configurations. no redundant PATHs exist.Technical Description BSS Command Reference disp_rtf_path disp_rtf_path Description The disp_rtf_path command displays all PATH devices to which the RTF is assigned. The range of values is 0 to 5. including the status of the RTF on that PATH. rtf_id_2 Specifies the 2nd RTF identifier. The range of values is 1 to 120. The PATH status includes the designation of SHARED in addition to the CONNECTED and REDUNDANT status. For spoke and daisy chain configurations. 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. 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 : 2nd RTF Identifier : 0 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 PATH 1 3 0 Status : SHARED CONNECTED Busy Unlocked 2-306 GMR-01 68P02901W23-P 23 Feb 2004 .disp_rtf_path Chapter 2: Device/function related commands 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 : 2nd RTF Identifier : PATH 12 0 0 Status: 0 0 CONNECTED Busy Unlocked End of Report Example This example displays the PATH devices assigned to RTF 0 0 at BTS 1. 68P02901W23-P 23 Feb 2004 2-307 GMR-01 .Technical Description BSS Command Reference disp_rtf_path PATH 1 4 0 Status : SHARED CONNECTED Busy Unlocked 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-119. "del_rtf_path" on page 2-179. "copy_path" on page 2-162. 2-308 GMR-01 68P02901W23-P 23 Feb 2004 . • 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. Security level 1 Supported by OMC-R GUI No Command type A (no operator actions) Prerequisites None Format Syntax disp_severity <device_name> <alarm_code> Input parameters device_name The name of the device. alarm_code The decimal number or range that identifies the alarm code or codes for the device that is being modified. • Refer to "Alarm devices" on page 2-19 for the ranges of alarm codes for each device. Example This example shows how to display the severity of GPROC alarm code 8. such as GPROC.disp_severity Chapter 2: Device/function related commands disp_severity Description Use the disp_severity command to view the current severity level for device alarms and non-reconfiguration alarms. The alarm code is is defined by all valid numeric values in the range 0 to 254. that is being modified. Technical Description BSS Command Reference disp_severity disp_severity gproc 8 Where: is: gproc device_name 8 alarm_code System response GPROC Alarm code 8 severity: 68P02901W23-P 23 Feb 2004 Investigate 2-309 GMR-01 . with which the operator is interacting. 2-310 GMR-01 68P02901W23-P 23 Feb 2004 . BSC or BTS. Security level 1 Supported by OMC-R GUI No Command type A (no operator actions) Prerequisites None Format Syntax disp_site Input parameters There are no input parameters associated with this command.disp_site Chapter 2: Device/function related commands disp_site Description The disp_site command displays the site. Example This example displays the current site: disp_site System response Current site number is 6 References Related command "equip" on page 2-327. Security level 1 Supported by OMC-R GUI Yes Command type A (no operator actions) Prerequisites None Format Syntax disp_throttle [<device_name> <alarm_code>] Input parameters device_name Device name that uniquely identifies the device. the command is executed with no input parameters. alarm_code Identifies the alarm to be throttled. alarm code 66: 68P02901W23-P 23 Feb 2004 2-311 GMR-01 . Examples Example 1 This example displays the throttle period for device DRI. The range of values for the alarm_code is 0 to 254. To display the throttle time period for all intermittent alarms.Technical Description BSS Command Reference disp_throttle disp_throttle Description The disp_throttle command displays the throttle period for an intermittent alarm. 2-312 GMR-01 68P02901W23-P 23 Feb 2004 . Alarm Code -----0 1 4 1 Throttle Time --------15 1 1 10 Alarm Description ------------------------------------Synch Loss Daily Threshold Exceeded Synch Loss Hourly Threshold Exceeded Remote Alarm Daily Threshold Exceeded Bad Host Message References Related command "chg_throttle" on page 2-132...disp_throttle Chapter 2: Device/function related commands disp_throttle dri 66 Where: is: dri device_name 66 alarm_code System response Alarm Source -----DRI Alarm Code ----66 Throttle Time -------5 Alarm Description ----------------------------------Superframe Counter Error Example 2 This example displays the throttle period for all of the intermittent alarms: disp_throttle System response Alarm Source -------MMS MMS MMS .... DRI .. Example In this example. disp_time 68P02901W23-P 23 Feb 2004 2-313 GMR-01 .Technical Description BSS Command Reference disp_time disp_time Description The disp_time command displays the current real time of the system. the system time is displayed. The format of the real time is: • Day of the week • Month • Day of the month • Hour • Minutes • Seconds • Year Security level 1 Supported by OMC-R GUI No Command type A (no operator actions) Prerequisites None Format Syntax disp_time Input parameters There are no input parameters associated with this command. disp_time Chapter 2: Device/function related commands System response Fri Nov 12 14:13:48 2002 References Related commands "chg_time" on page 2-134. 2-314 GMR-01 68P02901W23-P 23 Feb 2004 . "time_stamp" on page 2-472. If the reference number is not used. handover. Examples Example 1 The following example shows the input required to display all instances that exist in the system. value. and trace data currently enabled in the BSS and the destination of the trace report. RSS No 2-315 GMR-01 . Format Syntax disp_trace_call [reference_number] Input parameter reference_number A number that identifies a particular trace reference. or any call) Basic. the system displays all call traces. Using a reference number is optional. The number can range from 0 to 4294967295. Security level 1 Supported by OMC-R GUI No Command type A (no operator actions) Prerequisites This command is not allowed when in SYSGEN ON mode. disp_trace_call System response Start of Trace Report Trace Reference: Scope: Trigger Event: Trace Data: Data during handover only: 68P02901W23-P 23 Feb 2004 c0270002h site=2 RTF 0 1 All (call origination.Technical Description BSS Command Reference disp_trace_call disp_trace_call Description The disp_trace_call command displays the mode. RSS. End of Report Example 2 The following is an example of the specified call trace instance currently active in the BSS. OMC Yes Currently tracing ----------------2 Automatic Flow Control: Automatic Flow Control: Automatic Flow Control: End of Report Total calls traced -----------------10 Not Halted for this BSS. disp_trace_call 2Fh System response Start of Trace Report Trace Reference: Scope: Trigger Event: Trace Data: Event: Data during handover only: Interval (x480ms): Mode: Max. De-Activated by OMC. or any call) Basic. simultaneous: Total calls to be traced: Trace beyond scope: Destination of trace data: Triggering enabled: Number of calls -------------Trace Reference --------------2fh 2fh BSS wide All (call origination. 2-316 GMR-01 68P02901W23-P 23 Feb 2004 . Automatic Flow Control: Activated by OMC.------c0270002h 0 Call Trace Flow Control Status -----------------------------Automatic Flow Control: Halted for this BSS. Activated bu BSS. handover. Automatic Flow Control: Activated by BSS. DTAP No 2 Nth call=4 5 20 No MMI.disp_trace_call Chapter 2: Device/function related commands Interval (x480ms): Mode: Max simultaneous: Trigger enabled time: Total calls to be traced: Trace beyond scope: Destination of trace data: Triggering enabled: 8 Nth call=7 4 10:23 to 11:00 Not specified Yes MMI No Total calls currently traced ---------------------------Trace Reference Count --------------. 68P02901W23-P 23 Feb 2004 2-317 GMR-01 .Technical Description BSS Command Reference disp_trace_call References Related commands "trace_call" on page 2-474. "trace_stop" on page 2-486. The range of values is 0 to 11. Security level 1 Supported by OMC-R GUI Yes Command type A (no operator actions) Prerequisites The GPRS feature must be unrestricted to display PCU data.disp_traffic Chapter 2: Device/function related commands disp_traffic Description The disp_traffic command displays all RSL and RTFs equipped to a particular PATH at a BTS or all GSLs equipped to a GDS at a PCU. Format Syntax disp_traffic <location> <unique_PATH_identifier> Input parameters location Specifies the equipment location: pcu PCU 1 to 120 BTS unique_PATH_identifier Specifies the unique PATH to a particular BTS. Examples Example 1 This example displays the RSL devices and RTF functions equipped on unique PATH 3 at site 1: disp_traffic 1 3 2-318 GMR-01 68P02901W23-P 23 Feb 2004 . Technical Description BSS Command Reference disp_traffic System response Start of Report: SITE ID: Unique PATH ID: RSL RTF RTF RTF 1 0 0 0 0 0 1 2 1 3 0 0 0 0 End of Report Example 2 This example displays the PCU data: disp_traffic pcu 0 System response Start of Report: SITE ID: Unique GDS ID: PCU 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: Unique GDS ID: PCU 0 GSL 1 0 0 GSL 2 0 0 GSL 3 0 0 GPRS DATA End of Report 68P02901W23-P 23 Feb 2004 2-319 GMR-01 . disp_traffic Chapter 2: Device/function related commands References Related command "add_rtf_path" on page 2-45. 2-320 GMR-01 68P02901W23-P 23 Feb 2004 . 2. 4. 9. 3. 6. 10 4 0 4 0 No CICs associated to this GDP/XCDR < ------- 68P02901W23-P 23 Feb 2004 2-321 GMR-01 . 7.Technical Description BSS Command Reference disp_transcoding disp_transcoding Description The disp_transcoding command displays which Circuit Identifier Codes (CICs) are using the transcoding resources of which GDPs and XCDRs. 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 ------1 0 Transcoding Board ----------------1 0 CIC IDs ------1. Security level 1 Supported by OMC-R GUI Yes Command type A (no operator actions) Prerequisites The enhanced GDP provisioning feature must be unrestricted. 8. 5. disp_transcoding Chapter 2: Device/function related commands n/a : not applicable N-E : not equipped 2-322 GMR-01 68P02901W23-P 23 Feb 2004 . Example To display the version and revision information: disp_version System response BSP Code Version: BSP Database Level Number: CSFP Code Version: CSFP Database Level Number: 68P02901W23-P 23 Feb 2004 5.Technical Description BSS Command Reference disp_version disp_version Description The disp_version command displays the version and revision numbers of the current software load.0. Security level 1 Supported by OMC-R GUI Yes Command type A (no operator actions) Prerequisites This command is not allowed while in SYSGEN ON mode.0.8 35F2 5.0. Format Syntax disp_version Input parameters There are no input parameters associated with this command.8 35E5 2-323 GMR-01 .0. disp_x25config Chapter 2: Device/function related commands disp_x25config Description The disp_x25config command displays the X.25 settings for all BSS OMLs.25 Window Size: 128 2 2-324 GMR-01 68P02901W23-P 23 Feb 2004 . Security level 1 Supported by OMC-R GUI Yes Command type A (no operator actions) Prerequisites None Format Syntax disp_x25config <link type> Input parameter link type Specifies the type of X.25 configuration for all the CBLs or OMLs at a BSS.25 Packet Size: X. cbl displays parameters for all CBLs in the BSS. Example The following example displays the X. Must be used out of SYSGEN.25 link: oml displays parameters for all OMLs in the BSS. disp_x25 oml Where: is: oml link type System response: X. Technical Description BSS Command Reference disp_x25config References Related command "chg_x25config" on page 2-143. 68P02901W23-P 23 Feb 2004 2-325 GMR-01 . 2-326 GMR-01 68P02901W23-P 23 Feb 2004 .download_ltu Chapter 2: Device/function related commands download_ltu Description {4471}.This command and all references have been deleted for software release GSR7. Operator actions Refer to the instructions included with each device or function for specific actions to be taken when using this command. This command does not work at a BTS site. To equip or modify some devices. (Details of the command prompts and restrictions for equipping the devices and functions are provided in the Related Information section of this command reference. Some devices require the site to be locked. Since each device and function has specific parameters. there is a corresponding set of prompts for each. Charts showing equipage hierarchy are also included.) Some devices and functions require the system to be in the SYSGEN ON mode. there is no need to enter data. The equip command can be exited at any time by entering done in response to any prompt. enter the sysgen_mode on command. To unlock the site. Security level 2 Supported by OMC-R GUI Yes Command type B (operator actions required) Prerequisites Some devices and functions can be equipped only after other device(s) have been equipped. enter the lock command. it first must be set as allowable with the freq_types_allowed command. To exit this mode. To enter this mode. simply press the ENTER key at the prompt. Contact the OMC-R for help in setting up a BTS site.Technical Description BSS Command Reference equip equip Description The equip command adds devices and functions to the Fault Management portion of the CM database.The LMTL can be equipped only if the Location Services support feature is unrestricted and the BSS can support a BSS-based SMLC. To lock the site.GPRS devices can be equipped on ly if the GPRS feature is unrestricted. enter the unlock command.Some devices require the site to be loc ked. The equip command can be entered only at the BSC. If a device or function parameter is optional. 68P02901W23-P 23 Feb 2004 2-327 GMR-01 . Each device and function also has specific restrictions for equipage. use the sysgen_mode off command. the system must be in the SYSGEN ON mod e.To equip a device or function with a frequency. equip Chapter 2: Device/function related commands Format Syntax equip <location> <dev/func_name> Input parameters location {4040} Specifies the location of the device: 0 or bsc BSC 1 to 120 BTS pcu. 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. No more than three PCUs may be equipped per BSC. a CAGE is being equipped at the BSC: 2-328 GMR-01 68P02901W23-P 23 Feb 2004 . A BSC of type 1 or 2 must equip remote sites with an LCF. pcu_0 to pcu_2 PCU A BSC of type 0 must equip remote sites with a BSP. dev/func_name Identifies the device or function being equipped. Enter the BSC MSI identifier: Enter the BSC MMS identifier: Where: 0 0 is: 0.0 Enter the SITE identifier: Where: The uplink MSI and MMS identifiers from the BSC to the next site in the path (BTS 1). All of the prompts that define the path are included in this example: equip 0 path Where: is: 0 The location. 2 2-329 GMR-01 . 1 is: 1 Enter the upstream MSI identifier: 68P02901W23-P 23 Feb 2004 The site ID of the site (BTS 1) linked to the BSC. Enter the terminating SITE id: Where: 2 is: 2 The site where the path terminates. Refer to the description of the CAGE prompts in the Related information section. path The device being equipped. Enter the Unique PATH identifier: Where: 0 is: 0 The unique path identifier. Example 2 In this example.Technical Description BSS Command Reference equip equip bsc cage Where: is: bsc location cage device being equipped System response A series of prompts associated with the CAGE device are presented. a path with two links is equipped. 2 1 Enter the downstream MSI identifier: Enter the downstream MMS identifier: Where: is: 2. "unequip" on page 2-491.0 The downlink MSI and MMS identifiers from BTS 1 to the BSC. Related information The following related information covers the order and conditions in which devices and functions can be equipped. Prompts for downstream MSI and MMS identifiers are not presented. Enter the SITE identifier: 2 Where: is: 2 The site ID of the site (BTS 2) linked to the BTS 1. "freq_types_allowed" on page 2-376. "modify_value" on page 2-402. and lists the prompts that are generated during the execution of the equip command. "lock_device" on page 2-385. "state" on page 2-445.1 The downlink MSI and MMS identifiers from BTS 2 to the BTS 1. "unlock_device" on page 2-501.1 The uplink MSI and MMS identifiers from the BTS 1 to the next site in the path (BTS 2). The site identifier equals the terminating site identifier.equip Chapter 2: Device/function related commands 0 Enter the upstream MMS identifier: Where: is: 2. "shutdown_device" on page 2-433. System response COMMAND ACCEPTED References Related commands "disp_equipment" on page 2-234. "reassign" on page 2-411. Enter the upstream MSI identifier: Enter the upstream MMS identifier: Where: 2 1 is: 2. 2-330 GMR-01 68P02901W23-P 23 Feb 2004 . For example. Equipage hierarchy charts show the order in which devices and functions are equipped in the following systems: 68P02901W23-P 23 Feb 2004 • RXCDR. • M-Cell and Horizonmacro.Technical Description BSS Command Reference equip Equipage hierarchy Some devices and functions can only be equipped after other device(s) have been equipped. • GPRS. Other devices are automatically equipped. a CAGE must be equipped before an BTP can be equipped. For example. 2-331 GMR-01 . a MMS is equipped automatically when equipping a MSI. • InCell. Figure 2-1 Remote Transcoder (RXCDR) devices and functions RXCDR ABSS CAB Conn_Link CAGE KSW GCLK MSI BSP MMS * (See Note below) OML CBL CIC XBL NOTE: * indicates an automatically equipped device 2-332 GMR-01 68P02901W23-P 23 Feb 2004 . A MMS is automatically equipped when a MSI is equipped.equip Chapter 2: Device/function related commands RXCDR Figure 2-1 shows the device and function hierarchy for RXCDR devices and functions. Technical Description BSS Command Reference equip InCell Figure 2-2 shows the device and function hierarchy for InCell systems. Figure 2-2 BSC and InCell BTS BSS SITE (BSC) CAB AXCDR DYNET PCU Conn_Link CAGE KSW GCLK BSP GPROC LCF CSFP EAS MSI OMF MMS * (See Note below) RF_Unit GSL MTL OML LMTL CIC CBL XBL NOTE: * indicates an automatically equipped device 68P02901W23-P 23 Feb 2004 2-333 GMR-01 . A MMS is automatically equipped when a MSI is equipped. Figure 2-3 In-Cell and Horizonmacro equipage hierarchy chart 2-334 GMR-01 68P02901W23-P 23 Feb 2004 .equip Chapter 2: Device/function related commands 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. A MMS is automatically equipped when a MSI is equipped. CAB and CAGE are automatically equipped when a PCU is equipped.Technical Description BSS Command Reference equip GPRS Figure 2-4 shows the device and function hierarchy for the PCU device in a GPRS system. Figure 2-4 68P02901W23-P 23 Feb 2004 GPRS PCU devices and functions 2-335 GMR-01 . The BSS-RXCDR connectivity table is created using the add_conn command. and the lists the equip command prompts that occur with each device.equip Chapter 2: Device/function related commands Equipping devices This section references conditional information for the rules on equipping the various devices. {4415} Enter the CIC unblocking threshold: N 2-336 GMR-01 1 to 225 68P02901W23-P 23 Feb 2004 . 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 mode and it is to be the standby device. Place the system in the SYSGEN ON mode using the sysgen_mode on command. use the sysgen_mode off command. The maximum number of ABBSs that can be equipped at an RXCDR site is 10. Perform the CIC validation?: N yes or no none CIC validation must be enabled to set eac_mode to 1 (enabled) Enable Enhanced Auto-Connect Mode: N 0 or 1 0 The eac_mode can only be set to 1 (enabled) if the AMR Enhanced Capacity feature is unrestricted. An ABSS device can only be equipped at a RXCDR site. Prompt Enter the ABSS device id: Optional Range Default N 1 to 128 none Comments This value corresponds to the BSS network entity that this device represents. 0 A prompt for this value is presented only if the eac_mode is enabled. Prompt Optional Range Default Comments Enter the AXCDR device id: N 1 to 128 none This value corresponds to the RXCDR network entity that this device represents. An ABSS device may not be unequipped if it is specifically referenced in the BSS-RXCDR connectivity table. The maximum number of AXCDRs that can be equipped at a BSC site is 10. This device may also be equipped when the system is outside the SYSGEN ON mode and it is to be the standby device. The AXCDR can be equipped only at a BSC that is set to remote transcoding. Enter the CIC blocking threshhold: N 0 to 245 0 A prompt for this value is presented only if the eac_mode is enabled. ABSS The Associated Base Station Subsystem (ABSS) may be equipped with the system in SYSGEN ON mode. The AXCDR may not be unequipped if it is specifically referenced in the BSS-RXCDR connectivity table. To leave the SYSGEN ON mode. cage 0. This device may be equipped only at a BTS site. This device also may be equipped when the system is outside the SYSGEN ON mode and it is to be the standby device. slot 25 BTS sites: not allowed This prompt is not presented if the equip command is entered at an RXCDR. slots 25. 68P02901W23-P 23 Feb 2004 2-337 GMR-01 . BSS The Base Station Subsystem (BSS) should be the first device equipped by the operator during SYSGEN mode at a BSS site.cage 0. Prompt Optional Range Default Enter the BSP identifier: N 0 or 1 none Enter the cage number: N 0 or 1 none Enter the slot number: N 20. For a bts_type of 0. 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. slots 20. 24. 24 -cage1. 26 none Enter maximum MTLs this BSP may manage: N 0 or 1 none Comments BSPs may be only GPROCs with the following Cage and Slot restrictions based on site type: BSC and BSS sites: . Prompt Optional Range Default Enter the BSS identifier: N 1 to 128 none Is local transcoding performed at the BSC (yes/no): N yes or no none Comments BTP The Base Transceiver Processor (BTP) may be equipped with the system in SYSGEN ON mode. no more than two radios should be equipped.cage 1. slot 20 RXCDR sites: . 25. BTP 0 must be the first BTP equipped.Technical Description BSS Command Reference equip BSP The Base Station Processor (BSP) may be equipped with the system in SYSGEN ON mode. For a Horizon II macro controlling cabinet. The BSP may also be equipped when the system is outside the SYSGEN ON mode and it is to be the standby device. 26 . When equipping BTPs to M-Cell sites. equip Chapter 2: Device/function related commands The following prompts do not display for all installations. 24 cage 14. and • The cabinet_type = 10. slots 20. slot 20 Enter maximum DRIs supported by this BTP: N 0 to 6 none Comments If the BTS type is 0. 15. This device also may be equipped when the system is outside the SYSGEN ON mode and it is to be the standby device. 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). 16 or 20. 68P02901W23-P 23 Feb 2004 . The system does not prompt for values set automatically. Some devices set certain parameters automatically. 14. Prompt Optional Range Default Enter the CABINET identifier: N 0 to 15 none Enter the cabinet type: N 0 to 25 none 2-338 GMR-01 Comments M-Cell and transceiver cabinets cannot be equipped at an InCell site. • InCell cabinets cannot be equipped at an M-Cell site. Prompt Optional Range Default 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 Enter the slot number: N 20 or 24 none BTPs may only be GPROCs with the following Cage and Slot restrictions based on site type: BSC. InCell cabinets cannot be equipped at an M-Cell site. The CAB is automatically equipped when the PCU is equipped. the maximum number of DRIs may not be 0. The system rejects the command if: • The bts_type not = 0. BSS and RXCDR sites: not allowed BTS sites: age 15. CAB The cabinet (CAB) may be equipped with the system in SYSGEN ON mode. 11. The system rejects the equip CAB command if the CAB is equipped for GPRS. • M-Cell and transceiver cabinets cannot be equipped at an InCell site. Technical Description BSS Command Reference Prompt Optional equip Range Default Comments This value may be entered by number or as a string: No 68P02901W23-P 23 Feb 2004 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 15 m_cellcity 16 m_cellarena 17 N/A 18 horizonmacro 19 horizonmacro_ext Horizonmacro extention cabinet 20 m_cellarena_macro M-Cellarena macro BTS (Horizoncompact) 22 horizonmicro2 Horizonmicro2 BTS 23 horizoncompact2 horizoncompact2 BTS 24 horizonmacro2 HorizonIImacro cabinet 25 horizonmacro2_ext HorizonIImacro extention cabinet M-Cellmicro M-Cellcity M-Cellarena N/A Horizonmacro master cabinet 2-339 GMR-01 . 2-340 GMR-01 68P02901W23-P 23 Feb 2004 . • A comma must separate different frequency types. 4 Is an internal HDSL modem present?: Y yes or no none This prompt is only displayed if the site type is M-Cellcity. pcs1900 11 pgsm. cage 0 and 1 for BSS. egsm. dcs1800 6 egsm. BSC. dcs1800. pcs1900 10 egsm.equip Chapter 2: Device/function related commands Prompt Optional N Enter the frequency type: Range 1 to 15 Default none Comments This value may be entered by number or as a string. pcs1900 Combinations of frequency types may also be entered: • Numbers and strings may be combined in a single command. dcs1800. egsm. pcs1900 13 pgsm. This device may be equipped with the system in SYSGEN ON mode. dcs1800. No String 1 pgsm 2 egsm 3 pgsm. For this reason. dcs1800 7 pgsm. or RXCDR type sites and cage 14 and/or 15 must be equipped at BTS type sites. pcs1900 14 egsm. egsm 4 dcs1800 5 pgsm. pcs1900 12 dcs1800. like this: pgsm. BSC. and RXCDR sites and in cages 14 and 15 for BTS sites. dcs1800 8 pcs1900 9 pgsm. pcs1900 15 pgsm. egsm. Horizonmicro or Horizoncompact Is an internal integrated antenna present?: Y yes or no none This prompt is only displayed if the site type is M-Cellcity or Horizonmicro CAGE The master slots are contained in cages 0 and 1 for BSS. 2. the CAGE cannot be equipped. Valid identifiers for a BTS cage are 2 to 15. The system rejects the equip CAGE command if the cage is equipped for GPRS. The CBL may not be equipped at an RXCDR site. Prompt Enter the device ID for the CBL: 68P02901W23-P 23 Feb 2004 Optional Range Default Y 0 0 Comments 2-341 GMR-01 . Prompt Optional Range Default Comments The cage number (ID) must be equal to the setting on the LANX card. The cage is automatically equipped when the first BTP at a site is equipped. Enter the device identification for the cage: N 0 to 15 none Enter the KSW pair that manages the cage: N 0 to 3 none Enter the KSWX connecting cage to KSW for TDM 0: Y 0 to 4 none Enter KSWX connecting cage to KSW for TDM 1: Y 0 to 4 none Enter the cabinet to which the cage belongs: N 0 to 23 none Is an IAS connected?: Y yes or no yes Slots U2 through U7 can contain CLKX cards or KSWX cards. The system rejects the change if the new card would occupy a slot that is already occupied. or RXCDR Cage are 0 to 13. CBL The Cell Broadcast Link (CBL) may be equipped with the system in either the SYSGEN ON or SYSGEN OFF mode. The CBL may be equipped only at a BSC (site 0). The CBL may not be equipped on an HDSL link. Valid identifiers for a BSS. BSC. The system checks the contents of these slots any time a change implies the existence of a new CLKX.Technical Description BSS Command Reference equip This device also may be equipped when the system is outside the SYSGEN ON mode and it is to be the standby device. At M-Cell sites. The cage is automatically equipped when the PCU is equipped. EXP KSWX or remote KSWX card. The CIC may be equipped only at a BSC or RXCDR (site 0). the CIC is blocked. Equipping CICs at a BSC When equipping a CIC at a remote transcoding BSC. In autoconnect (non-static) mode. If the CIC is equipped in this way and the BSC is in backwards compatibility (static) mode. If one or more CICs cannot be equipped.equip Chapter 2: Device/function related commands Prompt Optional Range Default Enter the first MMS identifier for this device: N 0 to 55 none Enter the second MMS identifier for this device: N 0 or 1 none Enter the timeslot on MMS where this device appears: N 1 to 24 for T1 links 1 to 31 for E1 links none Enter the BSS Operator: N up to 20 alphabetic characters none The BSS operator must be in quotation marks. This is not required if the BSC is operating in static mode. Enter the CBC Operator: N up to 20 alphabetic characters none The CBC operator must be in quotation marks. the CICs that cannot be equipped are listed in a display with the reason that each could not be equipped. When equipping a range of CICs. the equip CIC command is accepted if all CICs in the range can be equipped. The parent MMS must be equipped before equipping the CIC. If none of the CICs in a range can be equipped. the command is still accepted. The CIC may not be equipped on an HDSL link. A single CIC or a range of unique CICs may be equipped for each MMS. the command is rejected and the reason displayed. all TRAU circuits must be equipped to GDP boards when efr_enabled is set to 1 (enabled) for the BSS. Usually. 2-342 GMR-01 68P02901W23-P 23 Feb 2004 . However. the equip CIC command is rejected. In this case. The equip CIC command is rejected if the CIC is not unique or if the timeslot/group is not available. the RXCDR providing the TRAU for the CIC must be specified. the CIC is blocked. the static MMS is not required. The operator also is prompted for a static MMS timeslot to the RXCDR. Comments CIC The Circuit Identity Code (CIC) may be equipped with the system in either SYSGEN ON or SYSGEN OFF mode. If the MMS on which the CIC is to be equipped does not appear in the CM Database. A CIC equipped at an RXCDR may be used for multiple BSSs. the CIC is blocked. In this case. The operator also is prompted for a static MMS timeslot to the BSS. the BSS managing the CIC must be specified. On the BSC. Prompt Optional Range Default Comments Enter the CIC(s): N 0 to 65535 none No more than 128 CICs may be equipped at a time (for remote transcoding). resource(s): N 1 to 128 none This prompt only appears for remote transcoding BSC sites only.Technical Description BSS Command Reference equip The call downgrade feature is an exception. the efr_enabled is set to 1. Enter the MMS ID to the RXCDR: Y none This prompt only appears for remote transcoding BSC sites only. allowing Enhanced Full rate calls on the second CIC and Full rate calls on first CIC. Which BSS is managing the CIC(s): N 1 to 128 none This prompt only appears for RXCDR sites only. Equipping CICs at a RXCDR When equipping a CIC at an RXCDR. Enter the MMS ID to the BSS: Y none This prompt only appears for RXCDR sites only. only 30 CICs may be equipped. The TRAU circuits do not need to be equipped to GDP just because efr_enabled is enabled. For example. For RXCDR and local transcoder BSS. 255 to 286). This is not required if the BSC is operating in static mode. Multiple CICs may be entered using the format: CIC# to CIC# (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). Enter starting subgroup: N 0 to 3 none This prompt appears only if there is remote transcoding and an MMS is specified. Enter starting timeslot: N 1 to 24 (T1 links) 1 to 31 (E1 links) none This prompt appears only if a MMS ID is specified. Which RXCDR is providing the TRAU 68P02901W23-P 23 Feb 2004 2-343 GMR-01 . slots 18 to 25 RXCDR sites: cages 0 to13. slots 25 and 26{4471} N See Comments none BSS sites: cages 0 to 13. Enter starting timeslot: N 0 to 31 (E1 links) none This prompt appears for RXCDR sites and local transcodings only. instead the CSFP is automatically equipped when the first BTP at a site is equipped. Enter the cage number N See Comments none BSS sites: cages 0 to 13. the command is rejected. the CSFP cannot be explicitly equipped by the user. slots 18 to 25 BSC sites: cages 0 to 13. slots 18 to 25 BSC sites: cages 0 to 13. If the COMB address is not unique. slots 25 and 26 : Enter the slot number: Comments DHP The Digital Radio Host Processor (DHP) may be equipped with the system in either the SYSGEN ON or SYSGEN OFF mode. 2-344 GMR-01 68P02901W23-P 23 Feb 2004 . slots 18 to 25 BTS sites: cages 2 to15. CSFP The Code Storage Facility Processor (CSFP) may be equipped with the system in either the SYSGEN ON or SYSGEN OFF mode.equip Chapter 2: Device/function related commands Prompt Optional Range Default Comments Enter the MMS ID to MSC: N 1 to 24 (T1 links) none This prompt appears for RXCDR sites and local transcodings only. COMB The Combiner (COMB) may be equipped with the system in either the SYSGEN ON or SYSGEN OFF mode. slots 18 to 25 BTS sites: cages 2 to15. At an M-Cell site. Prompt Optional Range Default Enter the CSFP identifier: N 0 or 1 none This prompt only appears at a BSC. slots 18 to 25 RXCDR sites: cages 0 to 13. Prompt Optional Range Enter the first COMBiner identifier: N 0 to 13 none Enter the COMBiner address: N 0 to 255 none Default Comments The COMB address must be unique at the same site. A maximum of eight GPROCs can exist in a single cage. The DPROC can be equipped only if the GPRS feature is unrestricted. Enter the maximum number of DRIs supported by this DHP: N 1 to 6 none The modify_value parameter max_dris is automatically set to 6. There can be a maximum of 10 PRP DPROCs equipped per PCU DPROCs are not redundant.Technical Description BSS Command Reference equip The DHP may be equipped only at a BSS or a BTS site. A PICP DPROC can support from 0–2 LAPD GDS devices. Enter the unique DHP number in this cage (identifier 2): N 0 to 7 none Enter the slot number: N 18 to 25 none BSS sites: cages 0 to 13: slots 18 to 25. At least one PRP and one PICP DPROC are required per PCU. The underlying GPROC may not have to be equipped to equip a DHP. Prompt Optional Range Default Comments Enter the cage number for this DHP (identifier 1): N 0 to 15 none This identifier must be equal to the cage number where the DHP is to reside. The DPROC may be equipped only at a GPRS PCU site. DPROC The Data Processor (DPROC) may be equipped with the system in either the SYSGEN ON or SYSGEN OFF mode. The DHP may not be equipped at an M-Cell site. BTS sites:cages 2 to 15: slots 18 to 25. 68P02901W23-P 23 Feb 2004 2-345 GMR-01 . which is the maximum number of DRIs supported by a DHP. {23658}A PRP DPROC can support from 0–4 TRAU GDS devices. 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). Enter the TRU identifier: Y 0 to 6 0 This prompt is presented only if the entered board type is DRIM. The equip cabinet command allows the secondary and primary band frequency types in each zone to which the DRIs are equipped. 2-346 GMR-01 68P02901W23-P 23 Feb 2004 . The equip RTF command allows two group identifiers for a cell only if the cell is dual band. Odd values only. DRIs/RTFs within a dual band cell with different frequency types must have different DRI/RTF group identifiers. If an RTF device ID is to be entered for a DRI. Enter the cabinet identifier: N 0 to 15 none If the cabinet ID does not exist in the database the system rejects the command. Prompt Optional Range Default Comments Enter the 1st and 2nd DRI id: N 1st: 0 to 52nd: 0 to 11 none This identifier indicates a user-defined redundancy group within a cell. The DRI may be equipped with the system in either the SYSGEN ON or SYSGEN OFF mode. Prompt Optional Range Default Enter the DPROC id: N 1 to 6 or 11 to 16 none Enter the DPROC type: N PICP or PRP none DRI (InCell sites) The Digital Radio Interface (DRI) for a InCell site may only be equipped at a BSS or a BTS site. Enter the slot number: N 7 to 17 none This prompt is presented only if the entered board type is DRIM. No entry or a zero entered for this field represents a non-Top Cell Radio Unit (TRU). The equip DRI command is rejected if the Cell IDs are different. If a DRI is being added to an existing group (same first identifier). the RTF must be equipped before the DRI. Enter the DRI board type: N drim or 0 none Enter the cage number: N 0 to 15 none This prompt is presented only if the entered board type is DRIM. the GSM Cell ID of the new DRI must be the same as the other DRIs in the group. Also. a DRI must be connected to the same antenna as the rest of the group.equip Chapter 2: Device/function related commands A DPROC can be equipped only if the PCU is equipped. To qualify a redundancy group. the DRI must be using the same portion of the TDM highway. This prompt is displayed only if COMB ID is entered for the previous prompt. The equip command is rejected if the Cell IDs are different. 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. If the RTF is already preferred by another DRI. the RTF must be equipped before the DRI. the system rejects the command. The DRI may be equipped with the system in either the SYSGEN ON or SYSGEN OFF mode. Enter the GSM cell ID where the DRI appears: N GSM cell ID or cell_name none The cell number may be in either seven parameter format or four parameter format. 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 RTF cannot be preferred by more than one DRI. Enter antenna select number for this cell: N 1 to 6 none Enter COMB 1st and 2nd id: Y 0 to 13 0 or 1 none Enter cavity number: Y 0 to 5 Enter the diversity flag for this DRI: N 0 or 1 none Does this DRI use tuneable combining: Y yes or no yes Enter the tuneable combining type: Y 0. or 2 0 Prompted only when DRI uses tuneable combining 0 = none 1 = non-controlling 2 = controlling Enter the COMB identifier: N 0 to 13 none Prompted only when DRI uses tuneable combining Enter the cavity number for this COMB: N 0 to 5 none Prompted only when DRI uses tuneable combining Enter the fm cell type: N 0 to 4 none 0 = non-diversity 1 = 120 degree cell (not currently supported) 2 = 60 degree cell (not currently supported) 3 = shared diversity (not currently supported) 4 = full diversity COMB must be separately equipped. If an RTF device id is to be entered for a DRI being equipped. 1. 68P02901W23-P 23 Feb 2004 2-347 GMR-01 .Technical Description BSS Command Reference equip Prompt Optional Range Default Comments Enter the 1st and 2nd RTF id: Y 0 to 5 0 to 11 none The RTF entered in this field must be equipped. the DRI must be using the same portion of the TDM highway. Enter the cabinet identifier: N 0 to 15 none The system rejects attempts to equip a DRI in DCS1800 Horizonmacro cabinet if tx_power_cap= 0 Enter the type of connection to the BTP: N 0 or fox (0 or master for Horizonmacro master cabinets) 1 or fmux0 2 or fmux1 3 or fmux2 4 or direct none This value may be entered as a number or its associated character string. Neither DRI has a higher precedence than the other in the DRI pair. Enter the Port to which the TCU is connected: N 0 to 5 none The maximum value is 1 if the entry in to the previous prompt is 4 or “direct. Also. Enter the GSM cell id where the DRI appears: N GSM Cell ID or cell_name none The cell number may be in either seven parameter format or four parameter format. 2-348 GMR-01 68P02901W23-P 23 Feb 2004 . An FMUX can be used only if the BTP resides in an M-Cell6 cabinet." Enter the 1st and 2nd RTF id: Y 0 to 5 0 to 11 none The RTF entered in this field must be equipped. To qualify a redundancy group. the user is not prompted for tuneable combining.equip Chapter 2: Device/function related commands Two DRI devices can be associated with each other (double density). Enter the density of this DRI: N 1 (single) or 2 (double) 1 (single) When double density is specified. Prompt Optional Range Default Comments Enter the 1st and 2nd DRI id: N 0 to 5 0 to 11 none This identifier is used to identify a user-defined redundancy group within a cell. a DRI must be connected to the same antenna as the rest of the group. Enter the 2nd DRI id of the associated DRI: Y 0 to 11 none This parameter specifies the DRI identifier to be used for the auto-equipped DRI in a DRI pair. If the antenna_select number is entered incorrectly. set the antenna_select to 3. set the antenna_select number to 1. the wrong receive antenna will be connected to the transceiver. set the antenna_select number to 2 If the receive antenna is connected to the Rx ANT 2A/2B in the cabinet supporting the CTU. set the antenna_select number to 2. 2-349 GMR-01 .Technical Description BSS Command Reference Prompt Enter antenna select number for this cell: equip Optional Range Default Comments N 1 to 3 none This number configures the Integrated Antenna Distribution Unit (IADU) If the receive antenna is connected to DLNB 0 in the cabinet supporting the transceiver.) Enter COMB 1st and 2nd id: Y 0 to 13 0 or 1 Enter cavity number: Y 0 to 5 68P02901W23-P 23 Feb 2004 none COMB must be separately equipped. For the Horizonmacro: This number configures the 1800 Sectorized Universal Receive Filter (SURF). If the receive antenna is connected to the Rx ANT 900 0A/0B in the cabinet supporting the CTU. (Note this is the default value and will not work with any other selection. set the antenna_select number to 3. If the receive antenna is connected to DLNB 1. If the receive antenna is connected to DLNB 2. set the antenna_select number to 1. If the receive antenna is connected to the Rx ANT 1A/1B in the cabinet supporting the CTU. If the receive antenna is connected to the Rx ANT 0A/0B in the cabinet supporting the CTU. set the antenna_select to 2. This prompt displays only if COMB ID is entered for the previous prompt. while limiting the configuration to simplify sharing. Also. these DYNETs must have different E1/T1 links used by the BTSs within the BTS network. The system does not verify whether this feature is available when a DYNET is equipped. A closed loop DYNET has two PATHs automatically equipped. The identifier of the second PATH is equal to the identifier of the DYNET multiplied by 2 and with 1 added. An open loop DYNET has an automatically equipped PATH for an open loop daisy chain. The automatically equipped PATH in closed loop daisy chains has a second identifier one greater than second identifier of the first PATH automatically equipped. All DYNETs that share the same first identifier must have exactly the same BTSs or timeslot switching sites in the same order. the command is rejected. The network may include timeslot switching sites. 68P02901W23-P 23 Feb 2004 .equip Chapter 2: Device/function related commands Prompt Optional Range Default Does this DRI use tuneable combining: Y yes or no none Enter the tuneable combining type: Y 0 or 1 none Enter the COMB identifier: N 0 to 13 none Enter the cavity number for this COMB: N 0 to 5 none Enter the diversity flag for this DRI: N 0 or 1 none Enter the fm cell type: N 0 to 4 none Comments 0 = none 1 = non-controlling 2 = controlling 0 = non-diversity 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. These limitations allow definition of multiple link BTS networks for sharing purposes. Prompt Optional Range Default Enter 1st and 2nd unique DYNET identifiers: N 1st identifier: 0 to 19 2nd identifier: 0 to 2 none 2-350 GMR-01 Comments If the ID already exists in the database. 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. with a second identifier equal to the second identifier of the DYNET times two. The identifier of the first PATH is equal to the identifier of the DYNET multiplied by 2. 2-351 GMR-01 . This prompt requires two values: • The first value is the MSI at the BTS where the MMS resides. BTS6. • The second value is the MMS for the BTS network definition. BTS6. BTS5. timeslot switching site.Technical Description BSS Command Reference Enter BSC MMS identifier: equip N 0 to 890 or 1 none This prompt requires two values: • The first value is the MSI at the BSC where the MMS resides. Enter SITE identifier: N 0 . Prompt Optional Range Default Enter the first device ID for the EAS: N 0 to 7 none Enter the cage where the PIX is connected: N 0 to 15 none Enter the daughter slot where the PIX is located: N 15 to 18 none 68P02901W23-P 23 Feb 2004 Comments If the ID already exists in the database the command is rejected. • The second value is the MMS for the BSC network definition.100. BSC none The TS site number. or the BSC Enter the upstream MMS identifiers: N For BTS4. • The second value is the MMS for the BTS network definition. BTS5. 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. ts_switch. This prompt can be left blank. TopCell and ExCell: 0 to 9 0 or 1 For M-Cell2: 0 to 1 0 to 1 For M-Cell6: 0 to 3 0 to 1 none Enter the downstream MMS identifiers: Y • The first value is the MSI at the BTS where the MMS resides. TopCell and ExCell: 0 to 9 0 or 1 For M-Cell2: 0 to 1 0 to 1 For M-Cell6: 0 to 3 0 to 1 none This prompt requires two values: For BTS4. Whether the relay is open or closed when deactivated must also be specified. 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.equip Chapter 2: Device/function related commands Prompt Optional Range Default Comments Enter the initial setting of the 4 relays: N 0 or 1 none Enter four values. Enter each opto whose state changes are to be reported: N 1 to 8 none Enter eight values. A prompt is displayed for each reporting optocoupler specified in the previous prompt. the physical wiring of each relay must be specified. If no value is entered in the range prompt. each separated by a space.closed. separate values with either a space or a comma. The operator also has the option of entering “all" and of entering a range of optos. Enter the user defined alarm index for the 8 optos: N 0 to 33 none Enter eight values. Enter the string “mpf" in place of one of the integers to indicate which opto is used for the EAS Mail Power Failure alarm. When equipping the EAS. 2-352 GMR-01 68P02901W23-P 23 Feb 2004 . The text string “mpf" is interpreted as the value 128. each separated by a space. 1 open): N 0 or 1 none Enter eight values. each separated by a space. then no state changes are reported for any optocoupler. Enter each opto whose state changes are to be reported: Y 1 to 8 for InCell sites 1 to 16 for M-Cell sites none Operator may enter up to 8 values for an InCell site and up to 16 values for an M-Cell site. No default is accepted for this prompt. each separated by a space. The values may be entered in any order. Enter the user defined alarm index for opto n: Y 0 to 33 and 128 none The operator must enter one value indicating the index of the user defined alarm string for the optocoupler specified by ’n’. Enter the no alarm condition for the 8 optos (0 . First GBL timeslot on the span. each separated by a space. Prompt Optional Range Default Enter the first device ID (Cabinet ID) for the EAS: N 0 to 15 none Cabinet identifier. Comments GBL {23658} The Gb Link (GBL) is the communication link between the PCU cabinet and the SGSN. Enter the user defined alarm index for the 16 optos: N 0 to 33 none Enter 16 values. Enter the string “mpf" in place of one of the integers to indicate which opto is used for the EAS Mail Power Failure alarm. each separated by a space. Prompt Optional Range Default Enter the GBL identifier: N {23658}0 to 11 none Unique identifier of the GBL. Enter each opto whose state changes are to be reported: N 1 to 16 none Enter 16 values. This device may be equipped with the system in either SYSGEN ON or SYSGEN OFF mode.closed. Enter the initial setting of the 4 relays: N 0 or 1 none 0 = deactivate the relay 1 = activate the relay Enter four values. Enter the ending timeslot: N 1 to 31 none Element name end_ts. each separated by a space. when a default GSL has not already been equipped. The GBL can be equipped only if the GPRS feature is unrestricted. 68P02901W23-P 23 Feb 2004 Comments 2-353 GMR-01 . {23658} To support EGPRS the GBL bandwidth between the PCU and the SGSN has been increased. each separated by a space. 0 to 1 none A GBL must be equipped on a DPROC PICP MSI at a PCU. The amount of bandwidth necessary for a maximally configured PCU is 12 E1s of GBL and for a maximally configured BSS is 20 E1s. Once the EAS is Busy-Unlocked. Enter the starting timeslot: N 1 to 31 none Element name start_ts. the relay state can be controlled by use of the set_relay_contact command. Last GBL timeslot on the span. 1 open): N 0 or 1 none Enter 16 values. Enter the no alarm condition for the 16 optos (0 . A GBL must not be equipped to an MMS on the last PICP MSI which is designated for code download. This maximum number of GBLs can be configured independent of whether EGPRS is restricted or not.Technical Description BSS Command Reference equip All relays are deactivated during site initialization. Enter the 1st and 2nd MMS identifier: N 0 to 23. This device is automatically equipped when a BTP is equipped. GCLK The Generic Clock (GCLK) may be equipped with the system in either the SYSGEN ON or SYSGEN OFF mode. then defaulted to this value. Value of the Frame Relay default Link Integrity Verification Polling Timer in seconds. Value of the Frame Relay default Polling Verification Timer in seconds. Enter the n393 counter: Y 1 to 10 6 Element name n393. the system may not always display all of the prompts below. Enter the n391 counter: Y 1 to 255 6 Element name n391. as number of errors. the GCLK is assigned to slot 3. the GCLK is assigned to slot 5. Enter the n392 counter: Y 1 to 10 3 Element name n392. 68P02901W23-P 23 Feb 2004 . Frame Relay default value for Error Threshold Counter. as number of events. Frame Relay default Full Status Polling Counter. Some devices do not require all of the prompts. Therefore. The GCLK may not be explicitly equipped at M-Cell sites. Enter the t392 timer: Y 6 to 30 15 Element name t392. Frame Relay default value for Monitored Events Counter.equip Chapter 2: Device/function related commands Prompt Optional Range Default Enter the t391 timer: Y 5 to 29 10 Element name t391. The slot number displayed in the prompt depends on the GCLK ID. as number of polling cycles. If the device ID is set to 1. Prompt Optional Range Default Enter the device identification for the GCLK: N 0 or 1 none Enter the cage number: N 0 to 15 none Is CLKX 0 (slot U7) present? Y yes or no no 2-354 GMR-01 Comments The GCLK slot is assigned based on the device ID: If the device ID is set to 0. Comments 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. The BSS rejects an attempt to equip a GDS to a MMS at the BSC where the mms_priority of the MMS is a non-zero value. This device may be equipped with the system in either the SYSGEN ON or SYSGEN OFF mode. The system checks the contents of these slots any time a change implies the existence of a new CLKX. Default Comments Slots U2 through U7 can contain CLKX cards or KSWX cards. {23658} 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. A GDS must not be unequipped until all GSLs on that GDS have been unequipped. 68P02901W23-P 23 Feb 2004 2-355 GMR-01 . The system rejects the change if the new card would occupy a slot that is already occupied. GDS The GPRS Data Stream (GDS) can be equipped only if the GPRS feature is unrestricted. Prompt Optional Range Default Enter the GDS identifier: N {23658} 0 to 37 none Enter the BSC MMS identifier: N 0 to 55 0 to 1 none Enter the PCU MMS identifier: N 0 to 23 0 to 1 none Enter the GDS type: N 0 to 1 TRAULAPD none Notes Unique identifer of the GDS BSC MMSs which are equipped to GDS devices cannot be selected as clock sources.Technical Description BSS Command Reference Prompt equip Optional Range Is CLKX 1 (slot U6) present? Y yes or no no The slot number displayed in the prompt depends on the GCLK ID. EXP KSWX or remote KSWX card. The number of LAPD GDS devices is two per PCU and six per BSS. Is CLKX 2 (slot U5) present? Y yes or no no The slot number displayed in the prompt depends on the GCLK ID. unlock the GSL at either the OMC-R or MMI prompt. {4040}30 GSLs can be equipped to a LAPD GDS. The equip GSL command fails if the total max_gsls for all LCFs becomes less than the total number of equipped GSLs. BSS and BTS sites: slots 18 to 25 RXCDR sites: slots 25 to 26 Comments GSL The GPRS Signalling Link (GSL) can be equipped only if the GPRS feature is unrestricted. Prompt Optional Range Default Enter the GPROC identifier: N 1 to 111 none Enter the cage number: N See Comments none Valid cage numbers are 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 number: N See Comments none Valid slot numbers are dependent on the site: BSC. This device may not be equipped at M-Cell sites. 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. To bring the GSL in service.equip Chapter 2: Device/function related commands GPROC The Generic Processor (GPROC) may be equipped with the system in either the SYSGEN ON or SYSGEN OFF mode. Prompt Optional Range Default Enter the GSL identifier: N 0 to 29 none Enter the unique GDS identifier: N 0 to 19 none 2-356 GMR-01 Notes 68P02901W23-P 23 Feb 2004 . The GSL may be equipped with the system in either SYSGEN ON or SYSGEN OFF mode. All 60 could be equipped to one DPROC that has two GDSs equipped on it. The Location Services feature must be unrestricted. If the second device ID is set to 1. If the second device ID is set to 0. the KSW is assigned to slot 1. the BSC must be configured to support a BSS-based SMLC. The system checks the contents of these slots any time a change implies the existence of a new CLKX. LMTL The LMTL device applies only to the BSC (location 0). The system rejects the change if the new card would occupy a slot that is already occupied. 2-357 GMR-01 . Enter TDM identifier (identifier 2): N 0 or 1 none The KSW slot is assigned based on the second device ID. the KSW is assigned to slot 27. EXP KSWX or remote KSWX card. For LMTLs to be equipped. Prompt Optional Range Default Comments Enter Portion of TDM Highway Managed (identifier 1): N 0 to 3 none The first device ID for the KSW must match the KSW pair in the cage where the KSW is being equipped. The KSW may not be equipped at M-Cell sites. Prompt Optional Range Default Enter the device identification for this LMTL: N 0 to 15 none Enter the first MMS identifier for this device: N 0 or 55 none 68P02901W23-P 23 Feb 2004 Comments Location Services must be unrestricted.Technical Description BSS Command Reference equip KSW The Kiloport Switch (KSW) may be equipped with the system in either the SYSGEN ON or SYSGEN OFF mode. Enter the cage number: N 0 to 15 none Are DRIs allowed on highway managed by this KSW: N Y or N none Slots U2 through U7 can contain CLKX cards or KSWX cards. MSI types xcdr or gdp are only allowed at sites where transcoding occurs. a warning message displays indicating a conflict in MMS timeslot usage.equip Chapter 2: Device/function related commands Prompt Optional Range Default Enter the second MMS identifier for this device: N 0 to 1 none Enter the timeslot on MMS where this device appears: N 31 (E1) 24 (T1) none Comments When an LMTL is equipped on an MMS that hosts other non-Lb-interface links. and the msi_type is niu_hdsl. Prompt Optional Range Default Enter the device identification for the MSI: N BSC: 0 to 55 RXCDR: 0 to 123 BTS: 0 to 9 (InCell) none Enter the cage number: N 0 to 15 none Prompt appears only if the Integrated MCell HDSL feature is enabled. 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. or msi_ext_hdsl. 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. niu_ext_hdsl. Enter the slot number: N BSS & BSC sites: 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 none Valid slot numbers are based on site type and MSI type 2-358 GMR-01 Comments 68P02901W23-P 23 Feb 2004 . and the msi_type is niu_hdsl. or msi_ext_hdsl. Enter MMS1 protocol type: Y E1 or HDSL HDSL Prompt appears only if the Integrated MCell HDSL feature is enabled. Enter the number of timeslots supported on MMS0: Y 16 or 32 32 Prompt appears only if the Integrated MCell HDSL feature is enabled. the protocol is HDSL. 68P02901W23-P 23 Feb 2004 Comments The input can be the numeric value or the text string. or msi_ext_hdsl. and the msi_type is niu_hdsl. and the MSI type is niu_hdsl. with a protocol type of HDSL for this MMS. Enter MMS1 m:odem setting: Y master or slave none Prompt appears only if the Integrated MCell HDSL feature is enabled. (The value of 5 is reserved. and the protocol type is HDSL Enter MMS0 modem setting Y master or slave none Prompt appears only if the Integrated MCell HDSL feature is enabled.Technical Description BSS Command Reference Prompt equip Optional Range Default Enter the MSI type: N 0 or msi 1 or xcdr 2 or gdp 7 or msi_ext_hdsl 12 or RF_unit {4415}20 or gdp2 none Enter MMS0 protocol type: Y E1 or HDSL HDSL Prompt appears only if the Integrated MCell HDSL feature is enabled. and the MSI type is niu_hdsl. niu_ext_hdsl. niu_ext_hdsl. the protocol is HDSL.) 2-359 GMR-01 . and the MSI type is niu_hdsl. Enter the number of timeslots supported on MMS1: Y 16 or 32 32 Prompt appears only if the Integrated MCell HDSL feature is enabled. and the msi_type is msi_ext_hdsl. niu_ext_hdsl. or msi_ext_hdsl. Read-Write (can only be set when the MSI device is created). • A warning will be issued if the protocol types of both MMSs of a MSI. Enter the MSI ID to the MSC: 0 Enter the transcoding capability: N 0 or Basic 1 or Enhanced 2 or GDP_2E1 The default values in the table above apply only if nothing is entered at the prompts. M-Cell6. • The msi_type of niu_hdsl is only supported at M-Cellcity.equip Chapter 2: Device/function related commands Prompt Optional Range Default Comments Y BSC: 0 to 55 RXCDR: 0 to 123 Value of GDPs own MSDI ID MSI identifier of GDP with MMS available for routing the transcoding circuits of a secondary GDP towards the MSC. 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. Read-Write (can be set only when the MSI device is created). Horizon micro or Horizon compact site. That is why the system prompts refer to the NIU. M-Cellmicro. Horizon micro or Horizon compact sites. The MSI function is performed by the Network Interface Unit (NIU) in an M-Cell2 or M-Cell6 cabinet. MSC MMS always zero because MSIs cannot provide MSC MMSs. M-Cellcity. Prompt appears only if MSI type entered as 2 or gdp. with an msi_type of niu_hdsl at an M-Cellcity. M-Cellcity. • 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. 2-360 GMR-01 68P02901W23-P 23 Feb 2004 . • The msi_type of niu_ext_hdsl is supported at M-Cell2. or as 20 or gdp2. M-Cellmicro. M-Cell sites do not use MSI boards. Horizon micro and Horizon compact sites. none Prompt appears only if MSI type entered as 2 or gdp. Horizon micro or Horizon compact site. are entered as E1. • 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. M-Cellmicro. and the msi_type is niu_hdsl or niu_ext_hdsl.Technical Description BSS Command Reference • equip When equipping an HDSL NIU. and the msi_type is niu_hdsl with a protocol type of HDSL for this MMS. Prompt Optional Range Default Enter the device identification for the MSI: N See comments none M-Cell 2 BTS: 0 or 1 M-Cell 6 BTS: 0 to 3 M-Cellmicro: 0 Enter the MCU card frame in which the NIU exits: N 0 or 1(see Comments) none 0 is the only valid value for this field if equipping to M-Cellmicro. the new hdsl_oos_mon_period and hdsl_restore_mon_period durations will default to known software values. and the msi_type is niu_hdsl. 68P02901W23-P 23 Feb 2004 Comments 2-361 GMR-01 . Enter MMS0 modem setting: Y master or slave master Only appears if the Integrated MCell HDSL feature is enabled. Enter the MSI type: N 3 or niu 8 or niu_hdsl 9 or niu_ext_hdsl niu The input can be either the numeric value or the text string. Enter the NIU slot number: N 0 or 1(see Comments) none 0 is the only valid value for this field if equipping to M-Cellmicro and M-Cell2. with a protocol type of HDSL for this MMS. Enter the MMS1 protocol type: Y E1 or HDSL HDSL Only appears if the Integrated MCell HDSL feature is enabled. or niu_ext_hdsl. Enter the MMS0 protocol type: Y E1 or HDSL HDSL Only appears if the Integrated MCell HDSL feature is enabled. and the msi_type is niu_hdsl or niu_ext_hdsl. The default values in the following table apply only if nothing is entered at the prompts. Enter the number of timeslots supported on MMS0: Y 16 or 32 32 Only appears if the Integrated MCell HDSL feature is enabled. 68P02901W23-P 23 Feb 2004 .equip Chapter 2: Device/function related commands Prompt Optional Range Default Comments Enter the number of timeslots supported on MMS1: Y 16 or 32 32 Only appears if the Integrated MCell HDSL feature is enabled. Prompt Enter the MSI identifier: Optional Range Default N 0 to 23 none 2-362 GMR-01 Comments The MSI identifier. and the msi_type is niu_hdsl with a protocol type of HDSL for this MMS. Two MMS devices are automatically equipped with each PCU MSI equip. Place the system in the SYSGEN ON mode using the sysgen_mode on command. The BSS supports equipage of a GDS to a HDSL MSI when the child MMS of the MSI is of type E1. A DPROC board must be equipped before a MSI may be equipped to the same DPROC. and the msi_type is niu_hdsl or niu_ext_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. The BSS supports equipage of a GDS at the PCU. Enter MMS1 modem setting: Y master or slave slave Only appears if the Integrated MCell HDSL feature is enabled. A modified MSI device is used to describe the serial interface device which can be equipped to DPROC boards. To leave the SYSGEN ON mode. This device may also be equipped when the system is outside the SYSGEN ON mode. An MSI must be equipped in PMC socket 1 of a DPROC in either slot 1 or slot 2. The BSS supports equipage of a GBL to a PICP MMS. It is a child class of PCU. The GPRS MSI type is not available when the GPRS feature is restricted. The site does not have to be locked when this device is equipped outside SYSGEN ON mode. use the sysgen_mode off command. The BSS does not support the modification of the msi_type for a MSI. The PCU supports a unique identifier for each MSI equipped within the PCU. All MMSs on the same MSI must be configured for the same destination: BSC or SGSN. The BSS supports equipage of up to two MSIs per DPROC board. The MTL cannot be equipped on an HDSL link. Only appears if the MMS ID to the MSC was not entered.Technical Description BSS Command Reference equip Prompt Optional Range Default Comments Enter the DPROC id: N 1 or 6 11 to 16 none The identifier of the DPROC in the PCU cabinet on which the MSI resides. MTL The Message Transfer Links (MTL) is not allowed at a RXCDR site and may be equipped only at site 0. Enter the DPROC socket: N 1 or 2 none PMC module identifier on the DPROC board to which the MSI is being equipped. Conflicting usage exists when at least one timeslot provides connectivity to a BTS and another connected to a different type of device (that is. OML The Operations and Maintenance Link (OML) cannot be equipped on an HDSL link. the system generates the following warning: COMMAND ACCEPTED: WARNING: Conflict in MMS usage. Prompt Optional Range Default Enter the device identification for this MTL: N 0 to 15 none Enter the first MMS description for this device: N 0 to 123 none Enter the second MMS description for this device: N 0 or 1 none Enter timeslot on MMS where this device appears: N 1 to 31 (E1) 1 to 24 (T1) none If an MMS has another timeslot that conflicts when equipping an MTL. The MTL can equipped only at the BSC. OML. and so on). Prompt Optional Range Default Enter the device id for the OML: N 0 to 3 none Enter the first MMS description for this device: N BSC: 0 to 55 RXCDR: 0 to 123 none 68P02901W23-P 23 Feb 2004 2-363 GMR-01 . The OML may be equipped only at site 0. display timeslot usage to verify. or was the same as the MSI device identifier of the device being equipped. RXCDR. Enter SITE identifier: N 1 to 120. PATH Prompts to equip a path are presented for each link in the path.equip Chapter 2: Device/function related commands Prompt Optional Range Default Enter the second MMS description for this device: N 0 or 1 none Enter timeslot on MMS where this device appears: N none E1: 1 to 31 T1: 1 to 24 If an MMS has another timeslot that conflict when equipping an OML.no dynamic allocation: 0 to 9 . or ts_switch (see Comments) none If the Aggregate Abis feature is enabled the system accepts ts_switch as the site ID. MMS id 2 is 0 to 1. the system generates the following warning: COMMAND ACCEPTED: WARNING: Conflict in MMS usage. the first value is the MSI ID. the second value is the MMS ID. The PATH may be equipped when the system is in either the SYSGEN ON or SYSGEN OFF mode. downstream MSI and downstream MMS identifiers. and HDSL modems that are in a master/slave configuration. separated by a space. Conflicting usage exists when at least one timeslot provides connectivity to a BTS and another connected to a different type of device (that is. The single exception to this rule is when the system cannot check master/slave settings because the HDSL link consists of two external modems. OML. The system rejects the equip path command if one of the MSIs is msi_type RF_Unit. If ts_switch is used. 2-364 GMR-01 Comments 68P02901W23-P 23 Feb 2004 . and so on). display timeslot usage to verify. the system will not prompt for upstream MSI. Prompt Optional Range Default Enter terminating SITE id: N 1 to 120 none Enter the Unique PATH identifier: N See Comments none The availability of a PATH identifier depends on whether or not the terminating site uses dynamic allocation: . A path for an HDSL link must have the same number of timeslots. identical link protocol types. RXCDR.dynamic allocation: 6 to 9 Enter the BSC MMS identifier: N 0 to 55 (MSI) 0 or 1 (MMS) none Type two values. upstream MMS. Enter the upstream MMS identifier: N BSC:0 to 55 BTS: 0 to 9 (In-Cell) 0 to 3 (M-Cell6) 0 to 1 (M-Cell2) none The upstream MMS identifier may not correspond to an RF_Unit MSI. display timeslot usage to verify. A PCU may also be equipped when the system is in the SYSGEN OFF mode and it is to be the standby device. and downstream MMS identifiers. When a PCU is equipped. the system generates the following warning: COMMAND ACCEPTED: WARNING: Conflict in MMS usage. a corresponding cabinet and cage are automatically equipped. the system does not prompt for upstream MSI. A PCU may be equipped with the system in SYSGEN ON mode. Enter the upstream MMS identifier: N BSC to 55 BTS: 0 to 9 (InCell) 0 to 3 (M-Cell6) 0 to 1 (M-Cell2) none The range for the MMS id 2 is 0 to 1. downstream MSI. upstream MMS. Conflicting usage is when at least one timeslot provides connectivity to a BTS and another type of device (such as. Comments If an MMS has another timeslot that conflicts when equipping a PATH. 68P02901W23-P 23 Feb 2004 2-365 GMR-01 .Technical Description BSS Command Reference equip The following sequence of prompts repeats until the specified site identifier matches the terminating site (maximum of nine sequences): Prompt Optional Range Default Enter the downstream MMS identifier: N BSC:0 to 55 BTS: 0 to 9 (InCell) 0 to 3 (M-Cell6) 0 to 1 (M-Cell2) none Enter the SITE identifier: N 1 to 120. The upstream MMS ID may not correspond to an RF_Unit MSI. an RXCDR). If ts_switch is used. or ts_switch (see Comments) none If the Aggregate Abis feature is enabled the system accepts ts_switch as the site ID. A PCU can be equipped only if parameter land_layer1_mode is set to E1. PCU {4040} Up to three Packet Control Units (PCUs) can be equipped at a BSS to provide the functionality for the GPRS feature. Two PSPs can be installed in each PCU.0. 2-366 GMR-01 68P02901W23-P 23 Feb 2004 .0.255. The site does not have to be locked when this device is equipped outside the SYSGEN ON mode.equip Chapter 2: Device/function related commands {4040} Any PCU prompt for which a response is not made will use the default value.255.0.255.0.255.0.0. The PSPs must be physically installed before code download can start to the PCU.2) PCU_1 1509949442 (90.0.0.2 {4040} Enter the PCU subnet mask: Y Enter the PCU router IP address: Y Enter the NSEI value: N 255.0 {4040} 90.65535 none {4040} Example {4040} Equip PCU site 1 at the BSC: equip 0 PCU Enter the PCU identifier (default 0): 1 Enter the PCU IP address: 127. The PSPs are auto-equipped.1 0 .2) PCU_2 1509949442 (90.0. The PSPs can only be fitted at a PCU.2 Enter the PCU subnet mask: 255.0. or the IP address entered is already assigned to another PCU.0. PSP The PCU System Processors (PSPs) are equipped only when the GPRS feature is unrestricted.0 Enter the PCU router IP address: 127. The system Configuration Management (CM) software will allocate default IP addresses to the PCUs as follows: PCU_0 1509949442 (90.0.0.0.1 Enter the NSEI value: 5047 COMMAND ACCEPTED The COMMAND ACCEPTED message wiil be replaced by an error message if a PCU with the same id already exists at the BSC.2) Prompt Enter the PCU identifier: Optional Range Default Y 0-2 0 Comments Up to three PCUs per BSC {4040} Y Enter the PCU IP address: {4040} 90. Only one RSL can be equipped to an NIU in slot 1 of an M-Cell terminating site. therefore. the user is not prompted. 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. the number of RSL devices supported on an NIU and an E1 span were the same. M-Cell 2/6 BTS: 0 to 5. Prompt Optional Range Default Enter the 1st device ID for the RSL: N 1 to 120 none Enter the 2nd device ID for the RSL: N 0 to 7 See Comments none Enter the Unique PATH id: N 0 to 9 none Enter LAPD T200 Timer value: Y 1400 to 5000 2500 Enter LAPD N200 value: Y 1 to 5 3 Enter LAPD K value: Y 1 to 10 7 Comments The range depends on the site type: InCell: 0 to 7.Technical Description BSS Command Reference equip The system uses a default value for the PSP slot. Only four RSL devices can be enabled per E1 span. If a RXCDR device is equipped at a BSS site. RSL The location for the Radio System Link (RSL) must be the BSC (site 0). it is actually an Associate RXCDR device. 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. RXCDR The Remote Transcoder (RXCDR) must be the first device equipped by the operator in the SYSGEN ON mode at a RXCDR site. Previously. Prompt Enter the RXCDR id: 68P02901W23-P 23 Feb 2004 Optional Range Default N 1 to 128 none Comments 2-367 GMR-01 . Values must be in multiples of 50. 2-368 GMR-01 68P02901W23-P 23 Feb 2004 . This value specifies the RXCDR device with which the XBL will be communicating. Enter the device ID for the XBL: N 0 to 9 none XBLs may not be equipped at BTS sites or at BSC transcoding sites. This value is valid for XBLs equipped at a BSS.the site being equipped is a BTS. Does the site use dynamic allocation of terrestrial backing resources?: N Y or N none This prompt only appears if:the Dynamic Allocation feature is unrestricted. 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. The LCF site capacity equals gproc_slots minus 1 (for the test channel). Enter the AXCDR device id for the XBL: N 1 to 128 none This prompt is only displayed at a BSC site. Prompt Optional Range Default Comments Enter the device identifier for the site: N 0 to 120 none 0 is the only valid value for a RXCDR site type. Enter the second device id for the XBL: N 0 to 9 none The is the value for the XBL device. This value specifies the ABSS device with which this XBL will be communicating. Prompt Optional Range Default Comments Enter the ABSS device id for the XBL: N 1 to 128 none This prompt is displayed only at an RXCDR site. The maximum number of XBLs that can be equipped at a BSC or an RXCDR site is 20. XBL The RXCDR to BSC Fault Management Link (XBL) cannot be equipped on an HDSL link.. This value is valid for XBLs equipped at an RXCDR. Enter the function identifier for the LCF: N 0 or 1 (BSP) 0 to 24 (LCF) none This prompt only appears if equipping a Remote BTS (RBTS).equip Chapter 2: Device/function related commands SITE The system rejects the equip site command if the new site exceeds the site capacity of the LCF. Enter the type of BSP or LCF: N BSP or LCF none This prompt only appears if equipping a Remote BTS (RBTS). LCF The Link Control Function (LCF) may only be equipped at BSC site types where the BSC type is not zero. Equipping functions This section provides conditional information for the rules on equipping the various functions. This prompt appears only if the XBL data rate is set to 16. Prompted only if the 16kbit/s option is unrestricted and the XBL data rate is set to 16kbit/s. The sum of all GSLs (GPRS) specified by the equipped LCFs must be greater than or equal to the total number of equipped GSLs. and lists the equip command prompts that occur with each function.Technical Description BSS Command Reference equip Prompt Optional Range Enter the data rate for the XBL (16/64kbps): Y 16 or 64 Enter the first MMS description for this device: N BSC: 0 to 55 RXCDR: 0 to 123 none Enter the second MMS description for this device: N 0 or 1 none Enter the timeslot on MMS where this device appears: N E1: 1 to 31 T1: 1 to 24 none Enter the group of the timeslot where this device appears: Y 0 to 3 Enter LAPD T200 time value for the device: Y 1400 to 5000 2500 Enter LAPD N200 value: Y 1 to 5 3 Enter LAPD K value: Y 1 to 127 7 Default Comments Prompted only if the 16kbit/s option is unrestricted. the system generates the following warning: COMMAND ACCEPTED: WARNING: Conflict in MMS usage. RXCDR. and so on). OML. If an MMS has another timeslot that conflict when equipping an XBL. Conflicting usage exists when at least one timeslot provides connectivity to a BTS and another connected to a different type of device (that is. Values must be in multiples of 50. Prompt Optional Range Default Enter the function indentifier for the LCF: N 0 to 24 none Enter the number of MTLs the LCF can manage: N 0 to 2 none 68P02901W23-P 23 Feb 2004 Comments 2-369 GMR-01 . At least one LCF must have a max_mtls value greater than zero. display timeslot usage to verify. If one or more PCS1900 frequency blocks are available to the BSS and an ARFCN is entered which is one of the block edges.equip Chapter 2: Device/function related commands Prompt Optional Range Default Enter the number of LMTLs the LCF can manage: N 0 to 2 none Enter the number of CBLs the LCF can manage: N 0 or 1 none Enter the number of GSLs the LCF can manage: N 0 to 6 none Comments Prompted only when the GPRS feature is unrestricted. The site does not have to be locked when this function is equipped outside SYSGEN ON mode. The RTF hops through one or more timeslots which cause frequency collisions. • An RTF may not be equipped to a site using dynamic allocation if the site is not in a DYNET. 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: 2-370 GMR-01 68P02901W23-P 23 Feb 2004 . RTF The Radio Transceiver Function (RTF) may be equipped with the system in either SYSGEN ON or SYSGEN OFF mode. This function may be equipped with the system in SYSGEN ON mode or outside the SYSGEN ON mode. OMF No parameter prompts are displayed when equipping the Operations and Maintenance Facility (OMF). 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. 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). An LCF cannot simultaneously manage both MTLs and LMTLs. When equipping the RTF. OMFs may only be equipped at BSC or BSS site types where the BSC type is set to 2. 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 mutually exclusive options are 16 kbit/s.Technical Description BSS Command Reference equip • The frequency at the assigned cell does not include PCS1900. 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. 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. • 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 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. 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. 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. The equip RTF command allows two group identifiers for a cell only if the cell is dual band. For a dual band cell an attempt to equip RTF for a BCCH RTF in the inner zone is rejected. When the Dual Band Cells option is enabled. refer to Chapter 5. The valid range for the ARFCN of an RTF configured for the inner zone is defined by frequency type of the secondary band. 68P02901W23-P 23 Feb 2004 2-371 GMR-01 . 64 kbit/s and none. • The Concentric Cells feature is enabled. 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. {23658}The pkt_radio_type parameter specifies the terrestrial resource capability of an RTF. the frequency type is managed on a zone basis. For a complete description of this parameter. 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 specified FHIs may contain only the frequencies in the band of the RTF. equip RTF for the secondary band in a dual band cell does not prompt for TRX power reduction. 32 kbit/s. When equipping an RTF to a dual band cell. The equip cabinet command allows the secondary and primary band frequency types in each zone to which the DRIs are equipped. 2-372 GMR-01 68P02901W23-P 23 Feb 2004 . 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. • If a non-zero value of extended range timeslots is entered for an RTF with 64 kbit/s packet radio capabilities: COMMAND REJECTED: Extended range timeslots are not allowed for EGPRS carriers. COMMAND REJECTED: Horizonmacro or Horizon II macro family of cabinets required for EGPRS. The DRI should be BUSY_UNLOCKED.equip Chapter 2: Device/function related commands When the equip RTF is completed. If the DRI is not in service (DU INHIBITED) use the MMI to place the DRI in service. outside of Sysgen mode. check the DRI that supports the new RTF. check the state of the RTF. If the RTF is not in the BUSY_ENABLED state. • 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. 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. • 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. • Either with 32 kbit/s packet radio capabilities when the Coding Scheme 3&4 feature is restricted. {23658}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. • With a valid FHI. Enter the optional 2nd identifier for the associated RSL: Y Micro: 0 to 1 MCell: 0 to 5 InCell: 0 to 7 none This prompt does not display if the RTF is equipped to a BTS using dynamic allocation. Otherwise. This prompt will not display if the RTF is equipped to a BTS using dynamic allocation. .if the sub-equipped RTF feature is not available.if the RTF is equipped to a BTS using dynamic allocation. This prompt does not display if the RTF is equipped to a BTS using dynamic allocation. Enter the GSM cell to which this carrier is assigned: N GSM Cell ID or cell_name none The cell number may be in either seven parameter format or four parameter format. 68P02901W23-P 23 Feb 2004 2-373 GMR-01 .Technical Description BSS Command Reference Prompt equip Optional Range Enter capacity of carrier: N FULL or SUB Enter type of carrier: N bcch or non_bcch none Enter the 1st and 2nd RTF id:Enter the 1st and 2nd RTF id: N Valid first RTF IDs: 0 to 5 {4471} Valid second RTF IDs: 0 to 11 0 to 1 for M-Cell none Enter the primary Unique PATH id: N 0 to 9 none Default Comments This prompt will not display . proceed with the Enter the optional secondary Unique Path id prompt. the system displays the next prompt. Enter the optional secondary Unique Path id: Y 0 to 9 none This prompt is provided for only RTFs at remote BTS sites. This prompt is only provided for RTFs at remote BTS sites. If the BTS type is 16k RSL. Enter the 2nd identifier for the associated RSL: N Micro: 0 to 1 MCell: 0 to 5 InCell: 0 to 7 none This prompt does not display if the RTF is equipped to a BTS using dynamic allocation. PGSMBCCH (not extended) 1-124 NON_BCCH (not extended)1-124 EGSM BCCH (extended) 0. 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. 1-124. Enter the 8 carrier training sequence codes: N 0 to 7 none The 8 carrier training sequence codes are entered on a single line with one space separating each value. as set in the MA (Mobile Allocation). The input for this value must include all 8 values or no values.equip Chapter 2: Device/function related commands Prompt Optional Range Default Comments Enter carrier absolute radio freq. Enter TRX transmit power reduction: Y same value as max_tx_bts 2-374 GMR-01 Only prompted when Concentric Cells feature is enabled. which defines the channel from which the MS is to hop. Enter KSW pair that manages this carrier: N 0 to 3 none This prompt does not appear when equipping the RTF to an M-Cell site. none The first channel from which to hop. A value of 255 is required for all M-Cellcity sites. A value of 255 means no hopping. 68P02901W23-P 23 Feb 2004 . Used to set the MA index offset. channel: N See Comments. or 975-1023 NON_BCCH (extended) 0. Only prompted for inner zone carriers. 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 frequency hopping indicators: N 0 to 3 and 255 255 The 8 frequency hopping indicators are entered on a single line with one space separating each value. 32k.Technical Description BSS Command Reference Prompt equip Optional Range Enter the number of extended range timeslots allowed: Y 0 to 4 Only prompted for outer zone carriers. 0 or 1 0 This prompt only occurs at an AMR capable BTS such as M-Cell2. For a complete description of this parameter. M-Cell6. Enter SDCCH placement priority: Y 0 to 250 The system displays this prompt if: for outer zone carriers (cell_zone = 0) only. 2-375 GMR-01 . 64k Y 0 or 1 0 The AMR feature must be unrestricted. refer to Chapter 5. and sdcch_load is not set to 0 ( 0). Enter channel allocation priority: Y 0 to 250 {23658} N 0 to 3. M-Cell6. Only prompted when the Extended Range Cell feature is unrestricted. or none. Enter SDCCH load Y 0 to 2 The system displays this prompt for outer zone carriers (cell_zone = 0) only. 16k. Horizonmacro and Horizon II macro Y or N Y This prompt only occurs at an AMR capable BTS such as M-Cell2. Horizonmacro and Horizon II macro Enter the packet radio capability: {4322} Default 0 (none) Enable AMR half rate?: Enter the value for AMR half-rate enabled: Is 8kbps TRAU allowed (yes/no): 68P02901W23-P 23 Feb 2004 Y Comments This prompt only occurs if the GPRS feature is unrestricted and if it is an outer zone carrier. This command does not work at a BTS site. 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. 2-376 GMR-01 68P02901W23-P 23 Feb 2004 . 1 to 124. the system deletes that frequency block or type from the list of allowed types. EGSM. Enter this command at the BSC only. • 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. DCS1800. Contact the OMC-R for help. and an existing frequency block or type is not entered. the system does not allow modifying the frequency types if an existing frequency type or frequency block is not entered.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. PCS1900 systems). If the system is in SYSGEN ON mode. If the system is in SYSGEN OFF mode. 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) Supported by OMC-R GUI Yes Command type B (operator actions required) Prerequisites None Dependencies The frequency types of extended neighbour cells must be allowed at the BSS. pcs1900 15 pgsm. dcs1800 7 pgsm. Prompted parameters The prompt for PCS 1900 frequency blocks appear only if “all" . The value may be entered as: a text string. dcs1800 6 egsm. Possible values are: 68P02901W23-P 23 Feb 2004 a Frequency block A Channels 512 to 585 b Frequency block B Channels 612 to 685 c Frequency block C Channels 737 to 810 2-377 GMR-01 . below. dcs1800 8 pcs1900 9 pgsm. If no values are entered. “pcs1900" or the number 8 is specified in the command line. pcs1900 12 dcs1800. At least one frequency block must be entered if the prompt appears. the command displays the frequency types that are currently available. pcs1900 More than one frequency type can be entered. egsm. pcs1900 10 egsm. a number. dcs1800.egsm 4 dcs1800 5 pgsm. Possible values and text strings are: Numeric value Text string 1 pgsm 2 egsm 3 pgsm. or a list of text strings and numbers. pcs1900 11 pgsm. The string “all" specifies all frequency types. egsm. dcs1800. pcs1900 13 pgsm.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 . egsm. dcs1800. See Example 2. pcs1900 14 egsm. 124) Example 2 This example modifies the frequency types allowed to include PGSM when DCS 1800 is already allowed: freq_types_allowed pgsm.c. freq_types_allowed System response: Frequency Blocks Allowed: PGSM (1 . below.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).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. Examples Example 1 This example displays the allowed frequency types.f 68P02901W23-P 23 Feb 2004 . for an example of the prompts.d. System response: Enter PCS 1900 frequency blocks: COMMAND ACCEPTED 2-378 GMR-01 a. A prompt displays describing the results of entering the command. the GCLK calibration at the local site is started: gclk_cal_mode System response Site <local site number> starting GCLK CALIBRATION MODE. Security level 2 Supported by OMC-R GUI No Command type A (no operator actions) Prerequisites This command is not allowed when in the SYSGEN ON mode. Example In this example. If this is a two MCU site. the site will be down until the redundant MCU takes over. No call processing can occur involving this MCU during the calibration mode. the site will be down until calibration is complete. This command can be executed only at M-Cell sites.n=no)? 68P02901W23-P 23 Feb 2004 2-379 GMR-01 .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. The prompt must be acknowledged with a y (yes) to begin the calibration. Format Syntax gclk_cal_mode Input parameters There are no input parameters associated with this command. If this a single MCU site. Are you sure (y=yes. The MCU resets when the calibration is complete. 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. If the ins_device command is applied to an active GCLK. A standby KSW must be available to use this command on a KSW. 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. No other extension cabinet types are supported. 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 Supported by OMC-R GUI Yes Command type B (operator actions required) 2-380 GMR-01 68P02901W23-P 23 Feb 2004 . and the standby GCLK is phase locking. and HORIZONMACRO_EXT. 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. the system displays an additional warning message. Only a standby PSP can be brought into service using this command. TCU_6. AXCDR.Technical Description BSS Command Reference ins_device Prerequisites This command is not allowed while in SYSGEN ON mode. BTP. device_id2 Second device identifier. pcu_0 to pcu_2 {4040} PCU device_name Literal that uniquely identifies the device. Operator actions Respond to the verification request prompt for an ABSS. device_id1 First device identifier. Respond to the verification request prompt for an MSI or MMS equipped with an OML. BSP. The following CIC syntax apply to local transcoding: ins_device ins_device ins_device ins_device ins_device 68P02901W23-P 23 Feb 2004 <location> <location> <location> <location> <location> CIC CIC CIC CIC CIC <cic_num1> <cic_num1> TO <cic_num2> <mms_id1> <mms_id2> <mms_id1> <mms_id2> <timeslot1> <mms_id1> <mms_id2> <timeslot1> TO <timeslot2> 2-381 GMR-01 . This definition varies with each device. DHP. GPROC or RSL. device_id3 Third device identifier. CIC syntax A form of syntax is available for each method of specifying a CIC. This command may be entered whether the device is locked or unlocked. This definition varies with each device. Format General syntax ins_device <location> <device_name> <device_id1> <device_id2> <device_id3> Input parameters location Specifies the location of the device: 0 or bsc BSC 1 to 120 BTS pcu. This definition varies with each device. 2-382 GMR-01 68P02901W23-P 23 Feb 2004 . mms_id2 Second MMS identifier. cic_num2 Last CIC device number in a range. or last in a range if TO is used. pcu_0 to pcu_2 {4040} PCU CIC Literal that uniquely identifies the CIC device. or last in a range if TO is used. mms_id1 First MMS identifier. timeslot1 First timeslot. timeslot2 Second timeslot. cic_num1 First CIC device number. group1 First group. 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 Specifies the location of the device: 0 or bsc BSC 1 to 120 BTS pcu.ins_device Chapter 2: Device/function related commands The following CIC syntax apply to remote transcoding: For remote transcoding BSC sites. the range is specified by their MMS. regardless of group. ins_device bsc cic 2 1 3 1 TO 5 1 Where: 68P02901W23-P 23 Feb 2004 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 2-383 GMR-01 . 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.Technical Description BSS Command Reference ins_device group2 Second group. * Indicates all CICs on the MMSs specified in the timeslot. TS and group. ins_device Chapter 2: Device/function related commands System response COMMAND ACCEPTED Example 3 {4040} 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-385. "reset_device" on page 2-416. 2-384 GMR-01 68P02901W23-P 23 Feb 2004 . "unlock_device" on page 2-501. MSI) can also be locked as a location. {4040} A PCU or a PCU device (for example. pcu_0 to pcu_2 {4040} PCU The location must be bsc or 0 when specifying the device SITE. 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-P 23 Feb 2004 2-385 GMR-01 . Format General syntax lock_device <location> <device_name> <device_id1> <device_id2> [<device_id3>] Input parameters location Specifies the location of the device: 0 or bsc BSC 1 to 120 BTS pcu. This command is only valid when the device is in the UNLOCKED state. device_name Device name that uniquely identifies the device.Technical Description BSS Command Reference lock_device lock_device Description The lock_device command locks a specified device. Security level 2 Supported by OMC-R GUI Yes Command type A (no operator actions) Prerequisites This command is not allowed while in SYSGEN ON mode. This value varies with each device. Normal call processing resumes when the KSW is unlocked.lock_device Chapter 2: Device/function related commands The shutdown_device command is available for non-intrusive locking of CIC. When locking an ABSS or AXCDR. Locking the link between an RXCDR and the BSC MMS makes the associated XBL go out of service (OOS). all calls currently on the KSW are lost. the XBL on the second link will block the circuits. A PCU or PCU device (for example MSI) can also be locked as a location. When a KSW is locked. CIC syntax A form of syntax is available for each method of specifying a CIC. TCU_6. however. and the XBL on the first link is locked. MPRT and MTL devices. and HORIZONMACRO_EXT. the system presents a warning prompt and a verification prompt. device_id3 Third device identifier. and the standby GCLK is This command is rejected for a KSW if no standby KSW is available. Any traffic circuits carried on this 2 Mbit/s link will be blocked. If the lock_device command is applied to an active GCLK. The lock_device command supports the locking of extension cabinets only of type TCU_2. If locking the MTL or OML is necessary. the XBL on the first link will go OOS. 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. This value varies with each device. No other cabinet types are supported. the PCU identifier must be entered as device_id1. This prevents any inadvertently locking devices at the RXCDR. DRIs and EASs equipped to the cabinet are disabled. {4040} If the specified device is a PCU. If XBLs are equipped on the first and second links. where their existence on a 2 Mbit/s link is not visible. device_id2 Second device identifier. Phase locking the system displays an additional warning message. they should be addressed as individual devices. A hard reset executes when this command is entered for the following devices: BSP DHP BTP GPROC device_id1 First device identifier. This means that XBL will not block the circuits. CICs may not be locked on a per-MMS basis when the BSC is operating in the dynamic allocation mode. The following CIC syntax apply to local transcoding: 2-386 GMR-01 68P02901W23-P 23 Feb 2004 . This value varies with each device. 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. For remote transcoding BSC sites. DRI. mms_id1 First MMS identifier. group1 First group. or last in a range if TO is used. timeslot1 First timeslot. cic_num1 First CIC device number. cic_num2 Last CIC device number in a range. timeslot2 Second timeslot. mms_id2 Second MMS identifier. or last in a range if TO is used. group2 68P02901W23-P 23 Feb 2004 2-387 GMR-01 .Technical Description BSS Command Reference lock_device lock_device lock_device lock_device lock_device lock_device <location> <location> <location> <location> <location> CIC CIC CIC CIC CIC <cic_num1> <cic_num1> TO <cic_num2> <mms_id1> <mms_id2> <mms_id1> <mms_id2> <timeslot1> <mms_id1> <mms_id2> <timeslot1> TO <timeslot2> The following CIC syntax apply to remote transcoding: lock_device lock_device lock_device lock_device lock_device lock_device <group1> TO <location> CIC <cic_num1> <location> CIC <cic_num1> TO <cic_num2> <location> CIC <mms_id1> <mms_id2> <location> CIC <mms_id1> <mms_id2> <timeslot1> <group> <location> CIC <mms_id1> <mms_id2> <timeslot1> * <location> CIC <mms_id1> <mms_id2> <timeslot1> <timeslot2> <group2> Input parameters location Specifies the location of the device: 0 or bsc BSC 1 to 120 BTS CIC Literal that uniquely identifies the CIC device. 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-388 GMR-01 68P02901W23-P 23 Feb 2004 . * Indicates all CICs on the MMSs specified in the timeslot. 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.lock_device Chapter 2: Device/function related commands Second group. the range is specified by their MMS. regardless of group. "unlock_device" on page 2-501. Are you sure (y=yes. 68P02901W23-P 23 Feb 2004 2-389 GMR-01 . "shutdown_device" on page 2-433. n=no)? y COMMAND ACCEPTED References Related commands "disp_equipment" on page 2-234. n=no)? y COMMAND ACCEPTED Example 4 {4040} 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. "reset_device" on page 2-416. "state" on page 2-445. "unequip" on page 2-491. "equip" on page 2-327.Technical Description BSS Command Reference lock_device Example 3 {4040} 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. The local MMS must be locked before the connectivity may be modified. Operator actions Change the security level to 2. This connectivity information must be specified for each E1/T1 link connecting to an RXCDR. 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. Lock the local MMS before modifying the connectivity. network_entity_id The AXCDR or ABSS device identifier that represents the actual RXCDR or BSS with which this MMS is communicating.mod_conn Chapter 2: Device/function related commands mod_conn Description The mod_conn command modifies MMS connectivity between the RXCDR and the BSS. Security level 2 Supported by OMC-R GUI Yes Command type B (operator actions required) Prerequisites The AXCDR or ABSS device specified in the command must be equipped in the BSS database. No XBL devices may be equipped that use the local MMS when changing the BSS or RXCDR network entity identifier. 2-390 GMR-01 68P02901W23-P 23 Feb 2004 . 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. Technical Description BSS Command Reference mod_conn remote_mms_id_1 First identifier of the MMS at the remote site. The ranges for several input parameters depends on where the command is executed. The mod_conn command can be executed from either the BSC or RXCDR. which is represented by equipped device AXCDR 3. 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. 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-P 23 Feb 2004 2-391 GMR-01 . 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. mod_conn Chapter 2: Device/function related commands References Related commands "add_conn" on page 2-33. "del_conn" on page 2-171. "disp_conn" on page 2-223 2-392 GMR-01 68P02901W23-P 23 Feb 2004 . The second specifies the frame relay burst size ns_burst_size (0 to 1984). Operator action The operator must answer the prompts. Format Syntax {4040} mod_nsvc <pcu_id> <ns_vci> Input parameter pcu_id Specifies the unique identifier of the PCU. There is no default.Virtual Connection Identifier (NSVCI). The range is 0 to 65535.Technical Description BSS Command Reference mod_nsvc mod_nsvc Description The mod_nsvc command modifies the frame relay committed information rate. pcu_1 or pcu_2. Security level 2 Supported by OMC-R GUI Yes Command type B (operator actions required) Prerequisites The GPRS feature must be unrestricted. as pcu_0. ns_vci Specifies the unique identifier of the NSVC mapping and identifier of the object. There is no default. 68P02901W23-P 23 Feb 2004 2-393 GMR-01 . The third specifies the frame relay burst excess ns_burst_excess (0 to 1984). There is no default. 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). the frame relay burst size. and the frame relay burst excess for a specified Network Service . {4040} at a specific PCU. the frame relay burst size. n=no) ? y COMMAND ACCEPTED References Related commands "del_nsvc" on page 2-177. "add_nsvc" on page 2-43. 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. 2-394 GMR-01 68P02901W23-P 23 Feb 2004 . Are you sure (y=yes. {4040} at PCU_2 site. and the frame relay burst excess for NSVCI 6.mod_nsvc Chapter 2: Device/function related commands ns_burst_size and ns_burst_excess must not both be 0. both must be 0.If either ns_commit_info_rate or ns_burst_size is 0. Example The following example modifies the frame relay committed information rate. Contact the OMC-R for help. This command does not work at a BTS site. If the neighbour is a UMTS UTRAN cell. Format Syntax modify_neighbor <source_cell_id> <neighbor_cell_id> <parameter> <value> Input parameters source_cell_id Cell identity of the source cell. The changing of the ba_bcch parameter is only allowed for test neighbours which are on the BA_SACCH list of the cell. 68P02901W23-P 23 Feb 2004 2-395 GMR-01 . use the del_neighbor command. The neighbor_cell_id may be a test cell neighbour. use the add_neighbor command. If the Inter-RAT handover feature is unrestricted.Technical Description BSS Command Reference modify_neighbor modify_neighbor Description The modify_neighbor command modifies the value of a neighbour cell parameter. handovers can be to UMTS UTRAN cells. Security level 2 Supported by OMC-R GUI Yes Command type A (no operator actions) Prerequisites The changing of the synchronized parameter is only allowed for neighbours at the site of the source cell. 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. To remove a neighbour from the BA_BCCH list which is not on the BA_SACCH list. Enter this command at the BSC only. To add a neighbour to the BA_BCCH list without adding to the BA_SACCH list. When pgbt_mode is set to 1. the Inter-RAT handover feature must be unrestricted. ho_margin_cell Changes handover margin of a neighbour cell. EGSM. EGSM. This attribute is only valid for SACCH neighbours. PCS1900 or GSM850) • Whether the seven parameter GSM Cell ID format or the four parameter GSM Cell ID format has been enabled. For an internal neighbour cell only. it must be placed inside double quotation marks. ba_gprs Adds or deletes a neighbour cell from the BA_GPRS list. neighbor_cell_id Cell identity of the neighbour cell whose parameter value is being changed. • Whether the cell is a UMTS UTRAN cell. it must be placed inside double quotation marks. When the cell name is entered. A cell_name may not be used to specify an external neighbour cell. If the directed retry feature is not enabled. The format for the GSM Cell ID depends on: • The system used (PGSM. parameter Neighbour cell parameter to be changed: Parameter Action adap_trigger_pbgt_nbr Specifies the cumulative area for the adaptive handover power budget algorithm. An external handover may only be initiated if either the dr_standard_congest or dr_ho_during_assign parameter is enabled. the cell_id can also be a cell name created using the cell_name command. DCS1800. 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. 2-396 GMR-01 68P02901W23-P 23 Feb 2004 . dr_allowed Allows a directed retry to an external neighbour during the assignment procedure. 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. The system does not prompt for the congest_ho_margin value if the Directed Retry option was not purchased. The cell_id can also be a cell name created using the cell_name command. When the cell name is entered. DCS1800. congest_ho_margin Determines the hand over margin to be used in the event of congestion. PCS1900 or GSM850) • Whether the seven parameter GSM Cell ID format or the four parameter GSM Cell ID format has been enabled. • Whether the cell is a UMTS UTRAN cell. the value defaults to the value of the ho_margin_cell of the neighbour. This value may only be changed when either the Directed Retry or alternate congestion relief feature is enabled.modify_neighbor Chapter 2: Device/function related commands The format for the GSM Cell ID depends on: • The system used (PGSM. 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).Technical Description BSS Command Reference modify_neighbor 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). ms_txpwr_max_cell Changes the maximum MS transmitted power for a neighbour cell. synchronized Allows synchronized handovers for neighbour cells. This parameter also interacts with the bounce_protect_mar to prevent reverse handovers due to power budget reasons. This is allowed only if both: • The Concentric Cells feature is enabled. If the power budget value minus the ho_margin_rxqual is less than 0 for a cell. neighboring_range Changes which range the neighbour borders on in an extended cell. 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. Refer to the bounce_protect_mar description. pbgt_alg_type Changes the power budget algorithm type. This parameter also interacts with the bounce_protect_mar to prevent reverse handovers due to power budget reasons. the system displays the inner_zone_threshold and inner_zone_margin prompts. that cell is excluded from the neighbour list. • The inner_zone_alg is set to 2. If the power budget value minus the ho_margin_rxlev is less than 0 for a cell. rxlev_min_cell Changes minimum receive level for a neighbour cell. 68P02901W23-P 23 Feb 2004 2-397 GMR-01 . If the interfering_nbr parameter is enabled. fdd_arfcn Indicates the frequency of a UMTS UTRAN cell. interfering_nbr Enables or disables the interference algorithm for the inner zone for this neighbour. that cell is excluded from the neighbour list. pbgt_hreqave Changes the power budget hreqave. additional prompts display. diversity_enabled Indicates whether diversity is applied in a UMTS UTRAN cell. 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.modify_neighbor Chapter 2: Device/function related commands Parameter Action scr_code Indicates the primary scrambling code of a UMTS UTRAN cell. value The new value of the selected neighbour cell parameter. 2-398 GMR-01 68P02901W23-P 23 Feb 2004 . Parameter Value adap_trigger_pbgt_nbr 0 to 255. adj_chan_intf_test or interfering_nbr is modified by this command. Refer to the description of the add_neighbor command for the prompted parameter values. Values for this field are dependent upon the selected parameter. modify_neighbor 5 4 3 2 1 667 865 5 4 3 2 1 344 975 pbgt_alg_type 3 Where: 68P02901W23-P 23 Feb 2004 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 2-399 GMR-01 . This example shows interaction associated with the M-Cellmicro option.Technical Description BSS Command Reference modify_neighbor 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. modify_neighbor Chapter 2: Device/function related commands 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-400 GMR-01 68P02901W23-P 23 Feb 2004 . "disp_gsm_cells" on page 2-253. "copy_cell" on page 2-156.Technical Description BSS Command Reference modify_neighbor References Related commands "add_cell" on page 2-21. "disp_neighbor" on page 2-281 68P02901W23-P 23 Feb 2004 2-401 GMR-01 . "del_neighbor" on page 2-173. "disp_cell" on page 2-205. "add_neighbor" on page 2-35. "del_cell" on page 2-168. Individual prerequisites are given for modify_value parameters as relevant.modify_value Chapter 2: Device/function related commands modify_value Description The modify_value command modifies parameter values for equipped devices or functions. The GPRS PICP MSI type is not supported by this command. Operator act ions To use all as the location parameter. These values can be displayed using the disp_equipment command. Prerequisites The modify_value command can only be entered at the BSC. place the system in the SYSGEN ON mode before entering the command. Enter this command at the BSC only. Security level 2 Supported by OMC-R GUI Yes Command type The type is dependent on the parameter being modified. Refer to the descriptions of individual parameters for additional operator actions that may be required. This command does not work at a BTS site. Format Syntax modify_value <location> <value_name> <new_value> <dev_func> <dev_func_id1> <dev_func_id2> <dev_func_id3> Input parameters location 2-402 GMR-01 68P02901W23-P 23 Feb 2004 . Contact the OMC-R for help. GCLK. RSL. as relevant to the value_name parameter. "Device/function parameters. Values are: 0 or bsc BSC 1 to 120 BTS {4040}pcu. dev_func_id2 and dev_func_id3 are not required. Examples Example 1 In this example.Technical Description BSS Command Reference modify_value Specifies the location of the device. SITE. new_value The value to be assigned to the named parameter. dev_func This value identifies the device or function affected by the modified parameter." for valid values. dev_func_id1 Values are dependent on the device/function type. See Chapter 7. "Device/function parameters. When changing certain cabinet types with this command. dev_func_id3 Values are dependent on the device/function type. If all is entered. value_name Refer to the individual parameter listing in Chapter 7. and XBL. the maximum number of DRIs on DHP 4 2 0 at site 7 is changed to 5: 68P02901W23-P 23 Feb 2004 2-403 GMR-01 . This value is only applicable during SYSGEN ON mode. pcu_0 to pcu_2 PCU all Every equipped device or function of the specified type. BSP." for descriptions and valid values of these parameters. the parameters dev_func_id1. Refer to the individual parameter descriptions in Chapter 7. Only applicable to MMS. dev_func_id2 Values are dependent on the device/function type. the following message is displayed: Cannot change to new cab type as bts power control is enabled. For example. "reassign" on page 2-411. "equip" on page 2-327. 2-404 GMR-01 68P02901W23-P 23 Feb 2004 .modify_value Chapter 2: Device/function related commands 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 References Related commands "disp_equipment" on page 2-234. Setting it from a TTY MMI login does not affect any other TTY MMI logins or OMC-R rlogins. Setting it from an OMC-R rlogin does not affect any other OMC-R rlogins or TTY MMI logins. or {4354} GPROC3). <lines per page> Enables pagination and sets the number of lines displayed per page Any numeric value between 20 and 255. At every new login. GPROC2. none Displays current page setting Not applicable 68P02901W23-P 23 Feb 2004 2-405 GMR-01 . The page command applies only to the current session and the current processor board (GPROC. it is reset to off. Security level 1 Supported by OMC-R GUI No Command type A (no operator actions) Prerequisites None Format Syntax page <input> Input parameter input Valid input formats are as follows: Input Action Range off Disables pagination No range. This is the default value. The page command can also specify the number of lines displayed per page for display commands.Technical Description BSS Command Reference page page Description The page command enables or disables pagination for display commands. "disp_cbch_state" on page 2-202. "disp_mms_ts_usage" on page 2-269. page 25 References Related commands The page command affects the output from the following commands. "disp_gsm_cells" on page 2-253. "disp_rtf_channel" on page 2-300.page Chapter 2: Device/function related commands Examples Example 1 This example shows that pagination has been enabled. "disp_csfp_status" on page 2-227. "disp_processor" on page 2-294. "disp_cell" on page 2-205."disp_csfp" on page 2-225. "disp_neighbor" on page 2-281. 2-406 GMR-01 68P02901W23-P 23 Feb 2004 . "disp_enable_stat" on page 4-11. "disp_options" on page 2-290. "state" on page 2-445. "disp_hdlc" on page 2-256. "disp_dte" on page 2-229. "disp_rtf_path" on page 2-305. "site_audit" on page 2-438. The current setting is displayed. "disp_cal_data" on page 2-200. "assess" on page 2-49. "disp_trace_call" on page 2-315. "man" on page 3-8. "disp_stats" on page 4-22. "disp_link" on page 2-265. "disp_equipment" on page 2-234. "disp_throttle" on page 2-311. "status_mode" on page 2-457. "disp_traffic" on page 2-318. "disp_bss" on page 2-198. and displays will display 30 lines per page. page 30 Example 2 This example shows that pagination has been disabled. "disp_link_usage" on page 2-267. "disp_stat_prop" on page 4-17. page off Example 3 This example shows no line number entered."disp_act_alarm" on page 2-195. "disp_hopping" on page 2-259. "disp_cell_status" on page 2-213. Technical Description BSS Command Reference query_audits query_audits Description The query_audits command performs two different functions. with the reason (for example. Format Syntax query_audits <location> <audit_type> <device_name> <device_id1> <device_id2> <device_id3> Input parameters location 68P02901W23-P 23 Feb 2004 2-407 GMR-01 . The “long" option displays the information for all of the audits for a specific device at the site. the GPRS feature must be unrestricted. There are only three possible System Responses to a query_audits command: • The display of results. To audit a PCU site. • A COMMAND REJECTED message. • ERROR. The ERROR response is followed by a display of the error description from the following list: Audit not available for unequipped devices Audit can only be executed on expanded TDM configuration Security level 1 Supported by OMC-R GUI Yes Command type A (no operator actions) Prerequisites A user at the OMC-R must rlogin to a site before an audit can be performed. 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 first is to provide a list of all information for all audits for a specific device at the customer site. the device is not in the database). The information includes the state and schedule information. 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.query_audits Chapter 2: Device/function related commands Specifies the audit location: 0 or bsc BSC 1 to 120 BTS pcu. Examples Example 1 In the following example. device_name The name that uniquely identifies the device. pcu_0 to pcu_2 {4040} PCU audit_type Specifies the amount of information required. device_id3 Third device identifier. 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 First device identifier. The range of values is 0 to 99. The range of values is 0 to 99. 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-408 GMR-01 68P02901W23-P 23 Feb 2004 . The range of values is 0 to 99. device_id2 Second device identifier. Technical Description BSS Command Reference Where: query_audits 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: Device: KSW Device id : 0 0 0 Start Time: 02:00 End Time: 04:00 Interval: 00:15 Audit Type: INT_LPBK Idle/Active State: IDLE On/Off State: Site Audit: ON Cage Audit: ON Device Audit: ON ON Example 2 The following example lists the audits in progress on the PCU MSI device: query_audits PCU short MSI 0 Where: is: PCU location short audit_type MSI device_name 0 device_id1 System response Device: MSI Device id: 0 0 0 Audit Type: SAFE Idle/Active State: IDLE On/Off State: Site Audit: ON Cage Audit: ON Device Audit: ON Example 3 {4040} 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: 68P02901W23-P 23 Feb 2004 is: PCU_0 location (PCU site 0) long audit_type MSI device_name 0 device_id1 2-409 GMR-01 . query_audits Chapter 2: Device/function related commands System response Device: MSI Device id: 0 0 0 Start Time: 00:00 End Time: 00:00 Interval: 00:10 Audit Type:SAFE Idle/Active State:IDLE On/Off State: Site audit:ON Cage audit:ON Device audit:ON References Related commands "cage_audit" on page 2-54. 2-410 GMR-01 68P02901W23-P 23 Feb 2004 . "site_audit" on page 2-438. "chg_audit_sched" on page 2-72. "device_audit" on page 2-184. BTP. If the DRI is locked after it has been reassigned. the DRI is assigned to the least loaded GPROC when the DRI is unlocked. A site device may be reassigned whether in Sysgen mode or not in Sysgen mode. For example. a DRI can be reassigned from one DHP. All GPROCs at the BSC (including the BSP) must be stable for at least five consecutive minutes since any GPROC has been transitioned. BTP. or BTF. All other devices must be reassigned when not in Sysgen mode. 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.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. or BTF to another DHP. The values are: 0 or bsc BSC 1 to 120 BTS pcu. The reassign command removes the device from service until the command is accepted. Security level 2 Supported by OMC-R GUI Yes Command type A (no operator actions) Prerequisites DRIs can only be assigned to GPROCs in the same cage as the DRI. pcu_0 to pcu_2 {4040} PCU 68P02901W23-P 23 Feb 2004 2-411 GMR-01 . Values are in the range 0 to 5.reassign Chapter 2: Device/function related commands child_name Literal that uniquely identifies the device. parent_func_name The literal that defines where the device or function is reassigned. to Optional text that may be entered to make the command more readable. parent_func_id_3 Values are dependent on the device or function type. child_dev_id_3 The third child device identifier. parent_func_id_2 Values are dependent on the device or function type. Example In this example. Values are in the range 0 to 24. child_dev_id_2 The second child device identifier. 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-412 GMR-01 68P02901W23-P 23 Feb 2004 . Valid value is 0. Current values are: DRI CBL MTL GSL SITE child_dev_id_1 The first chlid device identifier. 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. The RTF remains associated with the DRI after reassignment to another GPROC.Technical Description BSS Command Reference Where: reassign 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. BTF. Where no standby DRIs are available and a BCCH RTF is free. and should one be available. the RTF will be freed. The main reasons for failure to reassign a DRI: • The destination BTP. which has the least number of BCCH carrier-implementing DRIs assigned to it. In circumstances where the reassignment fails due to catastrophic events. BTF. or DHP has reached the maximum number of supportable DRIs. "equip" on page 2-327. a search will be made for a DRI which is assigned to the GPROC. • The DRI cannot be configured due to catastrophic hardware failure. such as hardware failure. 68P02901W23-P 23 Feb 2004 2-413 GMR-01 . another transceiver will be found. or DHP. "modify_value" on page 2-402. "disp_processor" on page 2-294. Related commands "disp_equipment" on page 2-234. • 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. reattempt_pl Chapter 2: Device/function related commands reattempt_pl Description The reattempt_pl command causes the GCLK to reattempt phase lock. 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 GCLK 0 will be forced to attempt phase lock. The valid values are 0 or 1. Example In this example. 2-414 GMR-01 68P02901W23-P 23 Feb 2004 . Security level 1 Supported by OMC-R GUI No Command type A (no operator actions) Prerequisites This command is not allowed while in SYSGEN ON mode. This is permitted only if the GCLK has previously failed to phase lock. 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 "chg_element" on page 2-94. 68P02901W23-P 23 Feb 2004 2-415 GMR-01 . This action swaps the GCLKs. and the standby GCLK is phase locking. 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. No other extension cabinet types are supported. and HORIZONMACRO_EXT. the system will display an additional warning message. If the reset_device command is applied to an active GCLK. 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. the system displays a COMMAND REJECTED: System still initializing message. 2-416 GMR-01 68P02901W23-P 23 Feb 2004 . 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. and can cause alarms on other devices. Additionally. a hard reset is performed if the device supports a hard reset. The system also displays a warning message if the reset_device command is applied to the GCLK. If the reset_site command is attempted while the system is initializing.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. a warning and a verification request is presented. Normal call processing will resume when the KSW is brought back into service. TCU_6. When this command is entered for an ABSS or AXCDR. CIC syntax A form of syntax is available for each method of specifying a CIC. device_id3 Third device identifier. This definition varies with each device. Format General syntax reset_device <location> <device_name> <device_id1> <device_id2> <device_id3> Input parameters location Specifies the location of the device to have a hard reset performed or toggled to the locked state: 0 or bsc BSC 1 to 120 BTS pcu. The following CIC syntax apply to local transcoding: 68P02901W23-P 23 Feb 2004 2-417 GMR-01 . CICs may not be reset on a per-MMS basis when the BSC is operating in the dynamic allocation mode. Security level 2 Supported by OMC-R GUI Yes Command type B (operator actions required) Prerequisites This command may be invoked whether the device is locked or unlocked. device_id2 Second device identifier. This definition varies with each device.Technical Description BSS Command Reference reset_device For remote transcoding BSC sites. device_id1 First device identifier. Operator actions Respond to the verification prompt that is presented if this command is used to reset an MSI or MMS with an OML. This definition varies with each device. pcu_0 to pcu_2 {4040} PCU device_name Literal that uniquely identifies the device. group1 First group. cic_num2 Last CIC device number in a range. or last in a range if TO is used. cic_num1 First CIC device number. 2-418 GMR-01 68P02901W23-P 23 Feb 2004 .reset_device Chapter 2: Device/function related commands reset_device <location> CIC reset_device <location> CIC reset_device <location> CIC reset_device <location> CIC reset_device <location> CIC <timeslot1> TO <timeslot2> <cic_num1> <cic_num1> TO <cic_num2> <mms_id1> <mms_id2> <mms_id1> <mms_id2> <timeslot1> <mms_id1> <mms_id2> The following CIC syntax apply to local transcoding: reset_device <location> reset_device <location> reset_device <location> reset_device <location> reset_device <location> reset_device <location> <group1> TO <timeslot2> CIC <cic_num1> CIC <cic_num1> TO <cic_num2> CIC <mms_id1> <mms_id2> CIC <mms_id1> <mms_id2> <timeslot1> <group> CIC <mms_id1> <mms_id2> <timeslot1> * CIC <mms_id1> <mms_id2> <timeslot1> <group2> Input parameters location Specifies the location of the device: 0 or bsc BSC 1 to 120 BTS CIC Literal that uniquely identifies the CIC device. group2 Second group. or last in a range if TO is used. timeslot1 First timeslot. timeslot2 Second timeslot. mms_id1 First MMS identifier. mms_id2 Second MMS identifier. specifying them by their MMS. TS and group. Are you sure (y=yes. reset_device bsc MSI 1 Where: is: bsc location MSI device_name 1 dev_id System response COMMAND ACCEPTED Example 2 In this example. This may cause alarms on other devices. regardless of group. 68P02901W23-P 23 Feb 2004 2-419 GMR-01 .n=no)? y COMMAND ACCEPTED Example 3 This example resets a range of CICs devices.Technical Description BSS Command Reference reset_device * Indicates all CICs on the MMSs specified in the timeslot. 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. When the reset_device command is invoked. a hard reset of an MSI device with ID=1 at the BSC is performed. Examples Example 1 In this example. the MSI device is locked before the command is invoked. "lock_device" on page 2-385. "unlock_device" on page 2-501. 2-420 GMR-01 68P02901W23-P 23 Feb 2004 .reset_device Chapter 2: Device/function related commands 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-380. 68P02901W23-P 23 Feb 2004 2-421 GMR-01 .Technical Description BSS Command Reference reset_ltu reset_ltu Description {4471}This command and all references have been deleted for software release GSR7. 2-422 GMR-01 68P02901W23-P 23 Feb 2004 . all_bts. The reset occurs even if the terminal is not connected to the affected site.reset_site Chapter 2: Device/function related commands reset_site Description The reset_site command selectively reboots available sites without rlogin. If a site other than the BSC is reset. Note that the system does not permit resetting all_sites. • Single site. Typical scenarios for selective rebooting include the following: • All sites including BSC. the terminal being used to enter the command must be attached to that site GPROC to view the outputs generated during a reset. Commands must be entered within 10 minutes after the MMI-RAM -> prompt displays. Security level 2 Supported by OMC-R GUI Yes Command type B (operator actions required) Prerequisites None Operator actions Place the system in the SYSGEN ON mode before entering this command. • Multiple sites. The all_sites. or a list of site options in SYSGEN ON mode. If a command is not entered. all_bts. • All sites excluding BSC. and list of site options are only allowed at the BSC and outside SYSGEN ON mode. the system resets. n=no)? WARNING: Command will REBOOT the following site(s):18 21 24 Are you sure (y=yes. n=no)? WARNING: Command will REBOOT site 0 (BSC or RXCDR) Are you sure (y=yes. 1 to 120 BTS pcu_0 to pcu_2 {4040} PCU (Note that pcu or PCU entered without a number will result in a syntax error. The specific message depends on the value of the location parameter.Technical Description BSS Command Reference reset_site Format Syntax reset_site [<location>] Input parameter location Specifies the site(s) to be reset. 1 to 100 BSC and multiple sites (1 to 100). Are you sure (y=yes. If bsc is included but is not the first item. the command is rejected. only the local site is reset. The bsc string must be entered as the first item in a list of sites.) When in SYSGEN ON mode. Valid values are: all_sites all sites including BSC all_bts all sites excluding BSC bsc BSC (site 0) bsc. n=no)? WARNING: Command will REBOOT all BTS sites. WARNING: Command will REBOOT the entire BSS. Are you sure (y=yes. Verification messages One of the following verification messages issues prior to execution. n=no)? 68P02901W23-P 23 Feb 2004 2-423 GMR-01 . n=no)?y SITE ____ 5 7 9 10 11 15 20 25 30 40 REBOOT STATUS ______ ______ OUT OF SERVICE: reset_site request RESET REQUEST IS IN PROGRESS RESET REQUEST IS IN PROGRESS OUT OF SERVICE: reset_site request OUT OF SERVICE: reset_site request OUT OF SERVICE: reset_site request RESET REQUEST IS IN PROGRESS RESET REQUEST IS IN PROGRESS RESET REQUEST IS IN PROGRESS RESET REQUEST IS IN PROGRESS is discarded is discarded is discarded is discarded Example 3 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): Are you sure (y=yes. Are you sure (y=yes. all active BTS sites are reset: reset_site all_bts Where: is: all_bts location System response WARNING: Command will REBOOT all BTS sites.reset_site Chapter 2: Device/function related commands Examples Example 1 In this example. an attempt is made to reset the BSC (site) using the 0 option: 2-424 GMR-01 68P02901W23-P 23 Feb 2004 . n=no)? y 2 COMMAND ACCEPTED: WARNING REBOOT SITE: site 2 will reboot now!! Example 2 In this example. Technical Description BSS Command Reference reset_site reset_site 0 Where: is: 0 location System response COMMAND REJECTED: The “0" option is not allowed while resetting BSC. 2 BSC reset_site 1 BSC or site 1 reset_site bsc. on success. Log-in to BSC. References Related information If the user is logged in to a non-BSC site and attempts to reset other site(s). 25. 0. you should enter “bsc".17.0 BSC reset_site BSC or local site The MMI TTY displays.21.3. one of the following statuses for each site requested: 68P02901W23-P 23 Feb 2004 • 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-425 GMR-01 . the command aborts and the following error message displays: COMMAND REJECTED: current site is not authorized to reboot other site(s). 5. 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. reset_site Chapter 2: Device/function related commands Related command "sysgen_mode" on page 2-466 2-426 GMR-01 68P02901W23-P 23 Feb 2004 . PCS1900).Technical Description BSS Command Reference set_full_power set_full_power Description The set_full_power command turns the Full Power mode on or off for a single cell or all cells in a site. The format for the GSM Cell ID depends on: • The system being used (PGSM. • Whether the seven parameter GSM Cell ID format or the four parameter GSM Cell ID format has been enabled. DCS1800. it must be placed inside double quotation marks and be preceded by cell_name=. Security level 2 Supported by OMC-R GUI No Command type A (no operator actions) Prerequisites None Format Syntax set_full_power [<cell_desc>] on <minutes> set_full_power [<cell_desc>] off set_full_power <location> on <minutes> set_full_power <location> off Input parameters cell_desc The GSM Cell ID of the cell at which full power is to be set preceded by cell_number=. EGSM. 68P02901W23-P 23 Feb 2004 2-427 GMR-01 . 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. When the cell name is entered. The name of the cell created using the cell_name command may be entered in place of the cell_number. set_full_power Chapter 2: Device/function related commands location Specifies the location. The ID number is in the seven parameter format. The valid range is 1 to 1440. minutes The length of time for the specified cell or location to operate at full power. 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. 0 or bsc BSC 1 to 120 BTS on/off Select turning on and off Full Power mode. 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 The example below shows the same cell number in four parameter format: set_full_power cell_number=543 21 31967 45988 on 45 Where: is: 543 21 31967 45988 cell_number on Turn Full Power mode on 45 Length of time Full Power mode will be 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: 2-428 GMR-01 68P02901W23-P 23 Feb 2004 . Technical Description BSS Command Reference set_full_power set_full_power cell_number=5 4 3 2 1 31967 45988 off Where: is: 5 4 3 2 1 31967 45988 cell_number off Turn Full Power mode off System response COMMAND ACCEPTED Example 3 The following example turns on the Full Power mode for all cells at site 5 for 45 minutes: set_full_power 5 on 45 Where: is: 5 location on Turn Full Power mode on 45 Length of time Full Power mode will be 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": 68P02901W23-P 23 Feb 2004 2-429 GMR-01 . set_full_power Chapter 2: Device/function related commands set_full_power cell_name="london-south" on 45 Where: is: london-south cell_name on Turn Full Power mode on 45 Length of time Full Power mode will be turned on System response COMMAND ACCEPTED 2-430 GMR-01 68P02901W23-P 23 Feb 2004 . All relays are deactivated on site initialization. Security level 2 Supported by OMC-R GUI Yes Command type A (no operator actions) Prerequisites The EAS device must be equipped. The physical EAS switches must be manually set to match the software settings specified. Format Syntax set_relay_contact <location> <device_id> <relay_number> <contact_setting> Input parameters location Specifies the location of the device: 0 or bsc BSC 1 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). the relay state can be controlled by use of the set_relay_contact command. 68P02901W23-P 23 Feb 2004 2-431 GMR-01 .Technical Description BSS Command Reference set_relay_contact set_relay_contact Description The set_relay_contact command specifies the relay state for an EAS device when the device is Busy-Unlocked. Once the EAS device is Busy-Unlocked. the physical wiring of each relay must be specified. These specifications describe whether the relay is open or closed when the relay is deactivated. When equipping an EAS device. 2-432 GMR-01 68P02901W23-P 23 Feb 2004 . 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-327.set_relay_contact Chapter 2: Device/function related commands contact_setting open or 0 open the relay closed or 1 close the relay Examples Example 1 For EAS 0 located at the BSC. and calls are forced to move to another carrier in the same cell only. If there are active calls. CICs may not be shutdown on a per-MMS basis when the BSC is operating in the dynamic allocation mode. Security level 2 Supported by OMC-R GUI Yes Command type B (operator actions required) Prerequisites This command is not allowed while in SYSGEN ON mode. the time parameter is ignored and the device is locked immediately. This command has no effect on an already locked device. The following devices can be shut down with this command: DRI CIC MPRT MTL The effect of this command is different for each type of specified device: • For DRIs. the call is dropped. • For MTLs. This command is only valid when the device is in the UNLOCKED state. If there are no free carriers in the cell. the resource is freed. but no calls are handed off until the shutdown timer expires. the device is locked when the specified time expires. the shutdown_device command locks the DRI immediately. If there are no active calls on the DRI. At this time. no new calls are allowed on the DRI. Format General syntax shutdown_device <location> <device_name> <device_id1> <device_id2><device_id3> <seconds> [wait <seconds>] Input parameters location 68P02901W23-P 23 Feb 2004 2-433 GMR-01 . • For remote transcoding BSC sites.Technical Description BSS Command Reference shutdown_device shutdown_device Description The shutdown_device command non-intrusively locks a specific device from further use. Operator actions Unlock the device to be shutdown before entering this command. device_id3 Third device identifier. This parameter is device dependent. CIC syntax A form of syntax is available for each method of specifying a CIC. wait The period the system should wait before blocking a busy device.shutdown_device Chapter 2: Device/function related commands Specifies the location of the device: 0 or bsc BSC 1 to 120 BTS device_name Literal that uniquely identifies the device. The wait parameter is optional for all devices except the CIC. This parameter is device dependent. seconds The time limit on the transition in seconds. The maximum time limit cannot exceed 900 seconds (15 minutes). The following CIC syntax apply to local transcoding: shutdown_device <location> shutdown_device <location> shutdown_device <location> shutdown_device <location> <mms_id2> <timeslot1> wait shutdown_device <location> <timeslot1> TO <timeslot2> CIC <cic_num1> wait <seconds> CIC <cic_num1> TO <cic_num2> wait <seconds> CIC <mms_id1> <mms_id2> wait <seconds> CIC <mms_id1> <seconds> CIC <mms_id1> <mms_id2> wait <seconds> The following CIC syntax apply to remote transcoding: shutdown_device <location> CIC <cic_num1> wait <seconds> shutdown_device <location> CIC <cic_num1> TO <cic_num2> wait <seconds> shutdown_device <location> CIC <mms_id1> <mms_id2> wait <seconds> shutdown_device <location> CIC <mms_id1> <mms_id2> <timeslot1> <group> wait <seconds> shutdown_device <location> CIC <mms_id1> 2-434 GMR-01 68P02901W23-P 23 Feb 2004 . This parameter is device dependent. It is required for the CIC device. device_id1 First device identifier. This parameter is device dependent. device_id2 Second device identifier. wait The period the system should wait before blocking a busy device. 68P02901W23-P 23 Feb 2004 2-435 GMR-01 . mms_id1 First MMS identifier. or last in a range if TO is used. timeslot1 First timeslot. group2 Second group. regardless of group. cic_num1 First CIC device number.Technical Description BSS Command Reference shutdown_device <mms_id2> <timeslot1> * wait <seconds> shutdown_device <location> CIC <mms_id1> <mms_id2> <timeslot1> <group1> TO <timeslot2> <group2> wait <seconds> Input parameters location Specifies the location of the device: 0 or bsc BSC 1 to 120 BTS CIC Literal that uniquely identifies the CIC device. timeslot2 Second timeslot. cic_num2 Last CIC device number in a range. or last in a range if TO is used. mms_id2 Second MMS identifier. group1 First group. * Indicates all CICs on the MMSs specified in the timeslot. specifying them by their MMS. 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 2-436 GMR-01 68P02901W23-P 23 Feb 2004 .shutdown_device Chapter 2: Device/function related commands 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) . TS and group. "unlock_device" on page 2-501.Technical Description BSS Command Reference shutdown_device System response COMMAND ACCEPTED References Related commands "disp_equipment" on page 2-234. "equip" on page 2-327. "lock_device" on page 2-385. 68P02901W23-P 23 Feb 2004 2-437 GMR-01 . "state" on page 2-445. "state" on page 2-445. Using the site_audit off command suspends all audits. It also allows the suspension or resumption of all audits at a specific site. Audits already turned on for this site. SAP internal error. see device_audit. 2-438 GMR-01 68P02901W23-P 23 Feb 2004 . Devices listed within the SITE can also generate messages specific to the device. Audits already turned off for this site. If the GPRS feature is unrestricted. The error messages listed above are those specific to a SITE. This command is not allowed while in SYSGEN ON mode. this command supports a GPRS PCU. • ERROR.site_audit Chapter 2: Device/function related commands site_audit Description The site_audit command initiates all audits for all devices at the customer site. There are only two possible System Responses to a site_audit command: • The display of results. The ERROR response is followed by a display of the error description from the following list: Audit not available. Using the site_audit on command resumes all audits. For a list of these messages. audits turned off for site. Security level 2 Supported by OMC-R GUI Yes Command type A (no operator actions) Prerequisites A user at the OMC-R must rlogin to a site before an audit can be performed. Only one audit may be run at a time. Technical Description BSS Command Reference site_audit Format Syntax site_audit <location> [<control>] Input parameters location Specifies the audit location: 0 or bsc BSC 1 to 120 BTS pcu. pcu_0 to pcu_2 {4040} PCU control Audit status on Resumes all audits at a specific site. off Suspends all audits at a specific site. Examples Example 1 The following example executes audits for all devices at the BSC: site_audit 0 Where: is: 0 location System response Device: KSW Year: 1994 Audit Type: Device: KSW Year: 1994 Audit Type: Device: MSI Year: 1994 Audit Type: Device: DRI Year: 1994 Audit Type: Device: DRI 68P02901W23-P 23 Feb 2004 Device id: 0 0 0 Month: 11 Day: SAFE Result: Device id: 0 0 0 Month: 11 Day: INT_LPBK Result: Device id: 1 0 0 Month: 11 Day: SAFE Result: Device id: 0 1 0 Month: 11 Day: SAFE Result: Device id: 0 0 0 12 Hour: 1 Min: 22 Sec: 55 AUDIT NOT SUPPORTED/AVAILABLE MSec: 10 12 Hour: 1 Min: 22 Sec: 55 AUDIT NOT SUPPORTED/AVAILABLE MSec: 30 12 Hour: PASS 1 Min: 22 Sec: 55 MSec: 40 12 Hour: PASS 1 Min: 22 Sec: 55 MSec: 40 2-439 GMR-01 . 2-440 GMR-01 68P02901W23-P 23 Feb 2004 .site_audit Chapter 2: Device/function related commands Year: 1994 Month: 11 Day: 12 Hour: Audit Type: SAFE Result: PASS Device: GCLK Device id: 0 0 0 Year: 1994 Month: 11 Day: 12 Hour: Audit Type: SAFE Result: PASS Device: GPROC Device id: 0 0 0 Year: 1994 Month: 11 Day: 12 Hour: Audit Type: SAFE Result: PASS Device: GPROC Device id: 1 0 0 Year: 1994 Month: 11 Day: 12 Hour: Audit Type: SAFE Result: ERROR 1 Min: 22 Sec: 55 MSec: 100 1 Min: 22 Sec: 55 MSec: 100 1 Min: 22 Sec: 55 MSec: 280 1 Min: 22 Sec: 55 MSec: 420 ERROR: Audit not available for this device. It should be run only during periods of low traffic. 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. Calls interrupted by this command must be re-established after the audit(s) are completed. 68P02901W23-P 23 Feb 2004 2-441 GMR-01 .Technical Description BSS Command Reference site_audit Related commands "cage_audit" on page 2-54. "query_audits" on page 2-407. "chg_audit_sched" on page 2-72. "device_audit" on page 2-184. site_id> After entering one of the above commands. Each site to be reset is separated by a space: soft_reset <site_id site_id site_id. the user is prompted with a warning and must enter “y" or “Y" (for yes) for the command to execute. Operator actions Respond to the verification prompt that is presented. A user logged in to a BTS can only restart the local site. 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. The command is abandoned if any response other than y or Y is received.soft_reset Chapter 2: Device/function related commands soft_reset Description The soft_reset command restarts the processes at one or more sites. Security level 2 Supported by OMC-R GUI Yes Command type B (operator actions required) Prerequisites Site(s) must be installed to enter this command.. 2-442 GMR-01 68P02901W23-P 23 Feb 2004 . Only a user logged in to the BSC can restart sites other than the local site.. the system displays the following verification prompt: WARNING: Command will RESTART all processes at site <site_id> Are you sure (y=yes. all This parameter specifies all of the sites at the BSC. the system displays one of the following verification prompts: WARNING: Command will RESTART all processes at all BTS sites. n=no)? When the command is entered to reset a single site. The range of values is 1 to 120. site_id This parameter specifies the site to be reset. n=no)? WARNING: Command will RESTART all processes at the following sites: <a listing of sites will follow> Are you sure (y=yes. Are you sure (y=yes. n=no)? If y is entered and the command is accepted for a single site.Technical Description BSS Command Reference soft_reset Input parameters {4040} 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. Verification prompts When the command is entered to reset multiple sites. the following warning message displays: COMMAND ACCEPTED: WARNING REBOOT SITE: site (site_id) will reboot now!!! 68P02901W23-P 23 Feb 2004 2-443 GMR-01 . Are you sure (y=yes. RESET REQUEST IS IN PROGRESS The site_reset request is in progress. site 1. The reset_site request is discarded. n=no)? y 1 OUT OF SERVICE 2 RESET REQUEST IN PROGRESS 3 RESET REQUEST IN PROGRESS 4 NOT M-CELL Example 2 In the following example. all of the sites are reset from the BSC: soft_reset all Where: is: all All sites in the BSS are specified. OUT OF SERVICE The site is OOS. System response WARNING: Command will RESTART all processes at all BTS sites.soft_reset Chapter 2: Device/function related commands Status displays One of the following statuses display for each requested site: Reboot status Description TIMEOUT The request timed out while waiting to receive ACK message from this site. Examples Example 1 In the following example. NOT EQUIPPED The site is not equipped. The reset_site request is discarded. System response WARNING: Command will RESTART all processes at the following sites: 1 4 9 Are you sure (y=yes. 4. and 9 are reset: soft_reset 1 4 9 Where: is: 149 Sites to be reset. n=no)? y 1 RESET REQUEST IN PROGRESS 4 NOT EQUIPPED 9 TIMEOUT 2-444 GMR-01 68P02901W23-P 23 Feb 2004 . 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 length of time a device has been in its current state is also displayed.Technical Description BSS Command Reference state state Description The state command displays the current status of devices or functions in the system. The following devices can be investigated with this command: ABSS AXCDR BSP BTP CAB 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 Supported by OMC-R GUI Yes Command type A (no operator actions) Prerequisites Not available on an RXCDR. This command is not available while in SYSGEN ON mode. Format Syntax state <location> [<filter>] [<dev/func_name> <dev/func id> <dev/func id> <dev/func id>] [<option1>] [option2] 68P02901W23-P 23 Feb 2004 2-445 GMR-01 . 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. including when it last changed states. dev/func name Literal that uniquely identifies the device or function. all maybe entered to specify all devices and functions. In a GPRS system. This definition varies with each device or function. There are two options: • Enter tags to display the configuration tags. 2-446 GMR-01 68P02901W23-P 23 Feb 2004 . * is used instead of all. option1 option2 The option parameter displays the configuration tag(s) and the device subtypes for the specified device(s) or function(s). dev/func id Second device/function identifier.state Chapter 2: Device/function related commands Input parameters location Specifies the location: 0 or bsc BSC 1 to 120 BTS all Specifies all sites pcu. This value is not valid when all is specified for the dev/func argument. dev/func id Third device/function identifier. • Enter subtypes to display the device subtypes. This value is not valid when all is specified for the dev/func argument. pcu_0 to pcu_2 {4040} PCU filter Optional text string used to select devices or functions in a specific state. dev/func id First device/function identifier. Valid values are: busy enabled-unlocked ins locked oos unlocked For a CIC or range of CICs. This definition varies with each device or function. Configuration tags are described in Operating Information: GSM System Operation (68P02901W14). This value is not valid when all is specified for the dev/func argument. filter is not available. This definition varies with each device or function. separate them with a space. CIC syntax A form of syntax is available for each method of specifying a CIC. lower. the state command may not be used for CICs devices when the BSC is operating in the dynamic allocation mode.Technical Description BSS Command Reference state The character string for the option may be entered in upper. 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> <group1> TO <timeslot2> <group2> 68P02901W23-P 23 Feb 2004 2-447 GMR-01 . The following CIC syntax apply to local transcoding: state <location> CIC <cic_num1> state <location> CIC <cic_num1> TO <cic_num2> The following three state commands are valid only in BC mode. If both parameters are entered together. The following CIC syntax apply to remote transcoding: state <location> CIC <cic_num1> state <location> CIC <cic_num1> TO <cic_num2> The following four state commands are valid only in BC mode. or mixed case letters. 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. 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. timeslot1. regardless of group. group2 Second group.state Chapter 2: Device/function related commands Input parameters location Specifies the location of the device: 0 or bsc BSC 1 to 120 BTS CIC Literal that uniquely identifies the CIC device. and group2 are valid only in BC mode. 2-448 GMR-01 68P02901W23-P 23 Feb 2004 . mms_id2 Second MMS identifier. mms_id1 First MMS identifier. cic_num1 First CIC device number. mms_id2. or last in a range if TO is used. timeslot1 First timeslot. mms_id1. group1. cic_num2 Last CIC device number in a range. timeslot2 Second timeslot. group1 First group. * Indicates all CICs on the MMSs specified in the timeslot. or last in a range if TO is used. neither filter nor option are available.Technical Description BSS Command Reference state For a CIC or range of CICs. 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: OPER STATES: D:Disabled E:Enabled B:Busy ADMIN STATES: L:Locked U:Unlocked E:Equipped Last 68P02901W23-P 23 Feb 2004 Transition S:Shutdown Config 2-449 GMR-01 . Examples Example 1 In this example. the status of the CAB device is displayed: state 7 cab 0 Where: is: 7 location cab dev/func name 0 dev/func ID System response STATUS INFORMATION: Device: CAB 0 0 0 Administration state: UNLOCKED Operational State: BUSY Reason code: NO REASON Time of last transition: Fri Apr 8 00:01:39 1994 Related Device/Function: None END OF STATUS REPORT Example 2 In this example. the status of all devices and functions at location 7 are displayed: state 7 Where: is: 7 location System response DEVICE STATUS INFORMATION FOR LOCATION 7: OPER STATES: D:Disabled E:Enabled B:Busy ADMIN STATES: L:Locked U:Unlocked E:Equipped Device ---------CSFP 0 0 0 BTP 0 0 0 DRI 0 0 0 MSI 1 0 0 MMS 1 0 0 RSL 0 0 0 State ----B-U B-U B-U B-U B-U D-U Reason -------------NO REASON NO REASON NO REASON NO REASON NO REASON RAM LINK 2-450 GMR-01 S:Shutdown Last Transition Related dd/mm hh:mm:ss Function ------------------------14/01 10:36:57 None 14/01 08:02:31 None 14/01 08:03:55 RTF 0 0 0 14/01 08:02:49 None 14/01 08:06:30 None 16/01 08:46:52 None 68P02901W23-P 23 Feb 2004 .state Chapter 2: Device/function related commands Device -----------KSW 0 0 0 State ----B-U Reason -----None dd/mm hh:mm:ss ----------------14/ 01 10:36:57 Tag (hex) --------00000004 Example 3 In this example. the status of all of the KSW devices at the BSC is displayed using wildcards: state bsc ksw * * * Where: is: bsc location ksw dev/func name * dev/func ID * dev/func ID * dev/func ID System response DEVICE STATUS INFORMATION FOR LOCATION 0: OPER STATES: D:Disabled E:Enabled B:Busy ADMIN STATES: L:Locked U:Unlocked E:Equipped Device --------KSW 0 0 0 KSW 1 0 0 State ----B-U B-U Reason --------------NO REASON NO REASON S:Shutdown Last Transition Related dd/mm hh:mm:ss Function -------------------------14/01 10:36:57 None 14/01 08:02:31 None Example 4 In this example. the status information for a single MSI. including device subtypes and configuration tags are displayed: state 0 msi 3 subtypes tags Where: is: 0 location msi dev/func name 3 dev/func ID subtypes option1 tags option2 System response STATUS INFORMATION: Device: MSI 3 0 0 (MSI) Administration state: LOCKED Operational state: ENABLED Reason code: NO REASON time of last transition: SAT JAN 5 12:55:18 1980 Related Device/Function: None Config Tag (hex): 00000006 END OF STATUS REPORT Example 6 In this example..--------------. including device subtypes.. .----.-------------------------RTF 0 0 0 B-E None 14/01 08:03:43 GPROC 0 0 0 Example 5 In this example.Technical Description BSS Command Reference state .. are displayed: state 0 msi * subtypes Where: 68P02901W23-P 23 Feb 2004 is: 0 location msi dev/func name 2-451 GMR-01 . TBUS 0 0 0 CAGE 0 0 0 CAB 0 0 0 SITE 0 0 0 PATH 0 0 0 PATH 0 0 0 D-U B-U B-U B-U D-U B-U NO NO NO NO NO NO REASON REASON REASON REASON REASON REASON 14/01 14/01 14/01 14/01 14/01 14/01 08:02:50 08:02:21 08:02:23 08:04:51 08:46:51 08:55:18 None None None None None None FUNCTION STATUS INFORMATION FOR LOCATION 7: OPER STATES: E:Enabled B:Busy ADMIN STATES: E:Equipped Last Transition Related Function State Reason dd/mm hh:mm:ss Device --------. the status information for all MSIs at site 0.... . -----.-----------------------. 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 DEVICE STATUS INFORMATION FOR LOCATION 2: OPER STATES: D:Disabled E:Enabled B:Busy ADMIN STATES: L:Locked U:Unlocked E:Equipped S:Shutdown Last Transition Related Device State Reason dd/mm hh:mm:ss Function ----------.--------------.state Chapter 2: Device/function related commands Where: is: * wildcard character for dev/func ID subtypes option1 System response DEVICE STATUS INFORMATION FOR LOCATION 0: OPER STATES: D:Disabled E:Enabled B:Busy ADMIN STATES: L:Locked U:Unlocked E:Equipped S:Shutdown Last Transition Related Device State Reason dd/mm hh:mm:ss Function -----------.-------------------------.--------------.-------MSI 0 0 0 B-U NO REASON 05/01 12:44:16 None (MSI) MSI 1 0 0 B-U NO REASON 05/01 12:44:23 None (XCDR) MSI 2 0 0 B-U NO REASON 05/01 12:44:16 None (MSI) MSI 3 0 0 E-L NO REASON 05/01 12:55:18 None (MSI) END OF STATUS REPORT Example 7 In this example.-------MMS 0 0 0 MMS 0 1 0 D-U B-U HDSL Modem bad or missing No Reason 13/01 13/01 17:18:03 None 17:18:03 None END OF STATUS REPORT 2-452 GMR-01 68P02901W23-P 23 Feb 2004 . 68P02901W23-P 23 Feb 2004 2-453 GMR-01 .Technical Description BSS Command Reference state Example 8 {4040} 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 Administration state: UNLOCKED Operational state: BUSY Reason code: NO REASON Time of last transition: Tue Jan 3 05:00:30 Related Device/Function: None END OF STATUS REPORT 1999 Example 9 {4040} This command displays the status of PCU site 1 at BSC 0: state 0 pcu 1 Where: is: 0 location pcu device name 1 PCU identifier System response STATUS INFORMATION: Device: PCU 1 0 0 Administration state: UNLOCKED Operational state: BUSY Reason code: NO REASON Time of last transition: Sun Jan 6 01:37:49 Related device/Function: None END OF STATUS REPORT 2002 Example 10 {4040} Displays the status of all MSIs at PCU site 1. BSP. Busy Device is available for use and is carrying traffic. Enabled FM has made the device available for use but it is not carrying traffic.state Chapter 2: Device/function related commands state PCU_1 MSI * Where: is: PCU_1 location MSI device name * all MSIs System response DEVICE STATUS INFORMATION FOR LOCATION PCU site 1: OPER STATES: D:Disabled E:Enabled B:Busy ADMIN STATES: L:Locked U:Unlocked E:Equipped S:Shutdown Last Transition Related Device State Reason dd/mm hh:mm:ss Function ----------. Unlocked The operator has made the device available for service. or BTP. 2-454 GMR-01 68P02901W23-P 23 Feb 2004 .----. or BTP). Table 2-32 lists the device states.----------------------. Table 2-31 lists the administrative states.----------------------MSI 1 0 0 B-U NO REASON 03/01 05:00:30 None MSI 2 0 0 B-U NO REASON 03/01 06:00:00 None END OF STATUS REPORT References Transference of device status When a GPROC card is equipped as a DHP. all references to the state of the GPROC card should use the equipped name (such as DHP. BSP. 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. Table 2-31 Administrative states Admin state Description Locked The operator has taken the device out of service. Equipped The device exists in the system. FAIL_ACT 3 The device failed to activate. Enabled Locked FM finds the device serviceable but the operator does not want it in service. Shutting Down The device is between the LOCKED and UNLOCKED states. Indicate progress made by BSC initializing a remote site NO_LINK 9 The RSL link to the BTS has not been established. 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. Enabled Unlocked FM finds the device serviceable and the operator wants it in service. 68P02901W23-P 23 Feb 2004 2-455 GMR-01 . Table 2-33 lists the reason codes. ROM_LINK 12 The site informs RSL it is a ROM link. BTS is in ROM. FREED_FUNCTION 8 The function has been removed from the device. RAM_LINK 11 The BTS jumped to RAM without problems. WAIT 7 The device is waiting for an event. The system is waiting until all processes using the device have terminated before putting the device into the LOCKED state. Busy Unlocked The device is in use. ROM_TO_RAM 10 The default link to BTS is active.Technical Description BSS Command Reference state Table 2-32 Device states Device state Description Not Equipped The device does not exist in the system. PARENT_OOS 2 The parent device is out of service. BAD_DB_CONFIG 4 The device is incorrectly configured in the database. NO_GPROC 5 There is no available GPROC to assign the device. The remaining states LOCKED and NOT EQUIPPED in Table 2-32 cannot exist with any operational component. Disabled Unlocked FM finds the device unserviceable but the operator wants it in service. INHIBITED 6 The device is inhibited from being used. The system may periodically audit the device (the operator can force audits) to determine if the device may be UNLOCKED. Disabled Locked FM and the operator find the device unserviceable. "shutdown_device" on page 2-433.state Chapter 2: Device/function related commands Table 2-33 Reason codes (Continued) Value Reason Codes Explanation Applicable to combiners COMBINER_CONTROLLER 14 Indicates which transceiver is controlling a particular combiner. "state" on page 2-445. 2-456 GMR-01 68P02901W23-P 23 Feb 2004 . "equip" on page 2-327. "unlock_device" on page 2-501. Related commands "disp_equipment" on page 2-234. "lock_device" on page 2-385. All sites may be disabled by entering all for the location. If no mode is entered. Security level 1 Supported by OMC-R GUI Yes Command type A (no operator actions) Prerequisites To display the status mode for the PCU. the GPRS feature must be unrestricted. If the status mode is turned off. Only the BSC can display status notification for remote sites. no notification is provided when a device experiences a state change. 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. This command permits efficient adjustment of the current system configuration where necessary. the current status is displayed. If the status_mode command is entered. The status notification occurs only at the local MMI at which the command was invoked. When the status mode is turned on. Location all is only allowed at the BSC. a notification containing both the old and the new status for a device displays immediately when a state change occurs. 68P02901W23-P 23 Feb 2004 2-457 GMR-01 .Technical Description BSS Command Reference status_mode 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. the current alarm status mode displays. status_mode Chapter 2: Device/function related commands Format Syntax status_mode <location> [<location> .. 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. 2-458 GMR-01 68P02901W23-P 23 Feb 2004 . note the output due to the state change that has occurred: status_mode 0 on Where: is: 0 location on mode System response SITE ---0 STATUS ---------------Status notification turned ON Example 2 This example shows the command string required to display the status mode for an entire BSC..<location>] [<mode>] Input parameters location Specifies the location of the device: 0 or bsc BSC 1 to 120 BTS pcu. When a device is locked. <reason> * -.New State: <op state> .<admin state> .Old State: <op state> . 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 -. the msi 1 0 0 is being locked. <admin state> . In this example.Technical Description BSS Command Reference status_mode status_mode all Where: is: all all sites in the BSC System response Site ---0 4 5 Status ---------------Status mode is OFF Status mode is ON 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 ---0 STATUS ---------------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.Tag(hex): <config_tag) * <entity type & ID> (<subtype>) Site: <site> Time: <time> * -. <reason> * -.Transition Number: <sequence #> 68P02901W23-P 23 Feb 2004 2-459 GMR-01 . status_mode Chapter 2: Device/function related commands This output occurs due to the state change of the device. 2-460 GMR-01 68P02901W23-P 23 Feb 2004 . References Related information Refer to the Maintenance Information: Alarm Handling at the OMC-R (68P02901W26) for a description of the displayed alarm message. Make sure that all DRIs are unlocked before using the store_cal_data command to store the transceiver calibration data. Enter this command at the BSC only. This command is unavailable at a BTS site. Contact the OMC-R for help. This command only works for DRIs that are in busy_unlocked state.Technical Description BSS Command Reference store_cal_data store_cal_data Description The store_cal_data command enables storing of the transceiver calibration data of 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 68P02901W23-P 23 Feb 2004 2-461 GMR-01 . Transceiver calibration data storage for all sites in the current BSS may be enabled by using all for the location value. Security level 2 Supported by OMC-R GUI No Command type A (no operator actions) Prerequisites This command is not allowed while in SYSGEN ON mode. 2-462 GMR-01 68P02901W23-P 23 Feb 2004 .store_cal_data Chapter 2: Device/function related commands Examples Example 1 The following example stores transceiver calibration data at the BSC: store_cal_data 0 Where: is: 0 location System response SITE ---0 CALIBRATION STATUS -----------------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 ---0 22 28 33 CALIBRATION STATUS -----------------RCU CALIBRATION REQUEST IS IN PROGRESS NOT EQUIPPED: RCU Calibration request is discarded OUT OF SERVICE: Please retry command later TIMEOUT: Please retry command later References Related commands "clear_cal_data" on page 2-146. "disp_cal_data" on page 2-200. Operator actions Unlock the standby device to be swapped. • The CIC device can not be locked by location when the BSS is operating in dynamic mode. • The standby device must be in the UNLOCKED state.Technical Description BSS Command Reference swap_devices swap_devices Description The swap_devices command swaps the specified standby device with the specified active device. The following restrictions apply: • The standby and active devices must be the same type. Format Syntax swap_devices <location> <active_device_name> [<std_device_id1>] 68P02901W23-P 23 Feb 2004 2-463 GMR-01 . a CIC can be locked by specifying the CIC ID only. this command swaps the active links and the controlling DRIs. Security level 2 Supported by OMC-R GUI Yes Command type B (operator actions required) Prerequisites This command is not allowed while in SYSGEN ON mode. • For a COMB device. In the dynamic mode. • The system does not permit swapping between two GCLKs that are phase locking. The following devices may be swapped by this command: BTP COMB GCLK LAN TDM Swapping a BTP device causes a site reset. swap_devices Chapter 2: Device/function related commands Input parameters location Specifies the location of the device: 0 or bsc BSC 1 to 120 BTS active_device_name Literal that identifies the active device. std_device_id1 Standby device identifier. 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 2-464 GMR-01 68P02901W23-P 23 Feb 2004 . required only for the COMB. "unequip" on page 2-491.Technical Description BSS Command Reference swap_devices 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 "disp_equipment" on page 2-234. "unlock_device" on page 2-501 68P02901W23-P 23 Feb 2004 2-465 GMR-01 . "lock_device" on page 2-385. "equip" on page 2-327. "state" on page 2-445. and the database is broadcast to the other sites. The checksum is then calculated. When the sysgen_mode on command is entered. 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 OFF mode from the SYSGEN ON mode by entering the sysgen_mode off command string then resetting the site. Command execution can occur without system delays. the database is not checked when a change is made. 2-466 GMR-01 68P02901W23-P 23 Feb 2004 . The checksum is not recalculated and the database is not broadcast to the other sites. the security level resets to Level 1 for all users.sysgen_mode Chapter 2: Device/function related commands sysgen_mode Description The sysgen_mode command places the system in the SYSGEN ON or SYSGEN OFF mode. SYSGEN OFF mode When the system is in the SYSGEN OFF mode. SYSGEN ON mode When the system is in the SYSGEN ON mode. the site must be reinitialized to place the system in the SYSGEN ON mode. Refer to the reset_site command. This command is not intended for general use at the OMC-R. When the sysgen_mode off command is entered. This command also displays the current mode of operation. There is no interaction with other processes. {23658}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. 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 database is verified each time a change is made. the system is placed in the SYSGEN OFF mode of operation: 68P02901W23-P 23 Feb 2004 2-467 GMR-01 . 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. Format Syntax sysgen_mode [<value>] Input parameter value Specifies the status of SYSGEN: on Places the system in the SYSGEN ON mode.Technical Description BSS Command Reference sysgen_mode After a system reset a command must be entered within 10 minutes after the MMI-RAM-> prompt is presented. Security level 1 Supported by OMC-R GUI No Command type B (operator actions required) Prerequisites None. Examples Example 1 In this example. off Places the system in the SYSGEN OFF mode. the system resets. Operator actions Reset the system to change the SYSGEN mode after entering this command. If a command is not entered. DB Verification passed. COMMAND ACCEPTED. System response COMMAND ACCEPTED: You must re-init the site to start SYSGEN Example 3 In the following example. 2-468 GMR-01 68P02901W23-P 23 Feb 2004 . System response *******VERIFYING DATABASE BEFORE COMPLETING SYSGEN******* Frequency hopping verification in progress. SITE 0 Verification. SITE 0 Verification. sysgen_mode System response Current Sysgen mode: ON Sysgen mode upon next restart: OFF Example 4 {23658}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..sysgen_mode Chapter 2: Device/function related commands sysgen_mode off Where: is: off The SYSGEN mode in which the system is placed after the next reinitialization. the current SYSGEN mode is displayed and the mode into which the system is placed after the next restart. 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.. Site 1: GSM Cell: 001 01 1 (0001h) 1 (0001h) --------------------------------------------------------ERROR: EGPRS and non-EGPRS carriers cannot have the same FHI. Example 2 In this example. Requested bsc_type not supported. At least one LCF MUST be equipped at site 0 when bsc_type is not 0. REJECTING SYSGEN_OFF REQUEST Database errors A database error causes the sysgen_mode off command to be rejected and a database is not created.10. an error message displays. At least one LCF MUST have max_mtls greater than zero for this site type. REJECTING SYSGEN_OFF REQUEST Example 5 {23658}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. No LCF found in CM database. All error messages are preceded with the DB VERIFY ERROR: string... Site <site_id> does note have a BTP equipped. Errors were found in the database. No slots available on LCF. SITE 0 Verification. Site <site_id> does not have a GCLK equipped RRSM Timer. General database errors The BSC MUST have an OMF equipped if bsc_type is 2.Technical Description BSS Command Reference sysgen_mode Errors were found in the database.8 value at site <site_id> must be less than SSM Timer. No slots available on BSP. bsc_type MUST be zero for site type RXCDR. The BSC MUST have at least one BSP equipped. Site 1: GSM Cell: 001 01 1 (0001h) 1 (0001h) --------------------------------------------------------ERROR: Master cabinet must be Horizonmacro2 for EGPRS RTFs to hop in baseband hoppping. No BSP found in CM database. INVALID DATA IN BIN <bin>: decision_1_dl_rxqual_av_h error in cell id <cell_number> INVALID DATA IN BIN <bin>: decision_1_dl_rxlev_av_h error in cell id <cell_number> INVALID DATA IN BIN <bin>: decision_1_dl_rxlev_av_ih in cell id <cell_number> INVALID DATA IN BIN <bin>: decision_1_p_bgt_rxlev_av_h in cell id <cell_number> (rxlev_dl_ho) INVALID DATA IN BIN <bin>: decision_1_p_bgt_rxlev_av_h in cell id <cell_number> (surround_cell) INVALID DATA IN BIN <bin>: decision_1_dl_rxqual_av_p in cell id <cell_number> INVALID DATA IN BIN <bin>: decision_1_dl_rxlev_av_p in cell id <cell_number> INVALID DATA IN BIN <bin>: decision_1_ncell_rxlev_av_h_calc in cell id <cell_number> INVALID DATA IN BIN <bin>: decision_1_tim_adv_av_alg in cell id <cell_number> 68P02901W23-P 23 Feb 2004 2-469 GMR-01 . There is no default RSL equipped to BTS site <site_id> on any PATH. For Cell: <cell_number> Timeslot: <timeslot> with FHI: <fhi > mismatches Timeslot: <timeslot> with FHI: <fhi> There are fewer frequencies than carriers for fhi: <fhi> in timeslot: <timeslot>. The number of carriers is: <number of carriers>. 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. Thus. Baseband hopping errors arfcn: <arfcn> should be in the mobile allocation for fhi: <fhi> timeslot: <timeslot> Within a cell. 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.sysgen_mode Chapter 2: Device/function related commands INVALID INVALID INVALID INVALID INVALID DATA DATA DATA DATA DATA IN IN IN IN IN BIN BIN BIN BIN BIN <bin>: <bin>: <bin>: <bin>: <bin>: decision_1_ul_rxqual_av_h in cell id <cell_number> decision_1_ul_rxlev_av_h in cell id <cell_number> decision_1_ul_rxlev_av_ih in cell id <cell_number> decision_1_ul_rxqual_av_p in cell id <cell_number> 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. Hopping timeslots exist in cell <cell_number> but not on the BCCH carrier. all carriers having their arfcns in the same MA must have identical fhi values for the same timeslot. Synthesizer hopping errors The BCCH carrier isn’t in any MA.) The NON-BCCH carrier with arfcn: <arfcn> in cell: <cell_number> has the BCCH frequency in its mobile allocation for FHI timeslot: <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. The number of frequencies is: <number of frequencies>.. ts: <timeslot> fhi: <fhi> The arfcn of the carrier must be part of the MA for its FHI. 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. bcch_freq: <bcch_freq> fhi_ts: <fhi_ts> FHI values must be identical within the BCCH carrier timeslots. carrier arfcn: <arfcn> timeslot: <timeslot> fhi: <fhi> cell: <cell_number> {23658}Master cabinet must be Horizonmacro2 for EGPRS to hop in baseband hopping EGPRS and non-EGPRS carriers cannot have the same FHI 2-470 GMR-01 68P02901W23-P 23 Feb 2004 .. (frequency: <frequency>. 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. Related commands "chg_level" on page 2-114. "reset_site" on page 2-422. References Related information When exiting the SYSGEN mode or completion of a database using the SYSGEN or DATAGEN tools. If errors are detected. Number of functions exceeds number of POOL GPROCs at site <site number>. All warning messages are preceded with the DB VERIFY WARNING: string.Technical Description BSS Command Reference sysgen_mode Database warnings A database warning causes the sysgen_mode off command to be rejected and a database is not created. a warning message displays. 68P02901W23-P 23 Feb 2004 2-471 GMR-01 . a database error or database warning may be generated. Site <site number> is bts_type 1 but does not have a DHP equipped. the database is verified for sanity. max_dris of Primary and Redundant BTPs do not match at site <site number>. General database warnings Maximum MTLs should be the same value for all BSPs. "disp_level" on page 2-264. sd_load is zero for all carriers in local cell <cell number>. This will cause one or more LCFs or OMFs to not come in service. This function adds a time and date before the MMI command prompt. off Turns time_stamp off. Examples Example 1 In this example.time_stamp Chapter 2: Device/function related commands time_stamp Description The time_stamp command enables or disables the time-stamping function. the time stamp is turned on: time_stamp on System response [11/12/93 01:03:30] MMI-RAM 0115-> 2-472 GMR-01 68P02901W23-P 23 Feb 2004 . Security level 1 Supported by OMC-R GUI No Command type A (no operator actions) Prerequisites None Format Syntax time_stamp <value> Input parameter value Specifies the status of time_stamp: on Turns time_stamp on. 68P02901W23-P 23 Feb 2004 2-473 GMR-01 . the time stamp is turned off: time_stamp off System response MMI-RAM 0115-> References Related commands "chg_time" on page 2-134.Technical Description BSS Command Reference time_stamp Example 2 In this example. "disp_time" on page 2-313. the BSS does not have complete knowledge of subscriber or equipment IDs. RR and RSS data may also be specified for inclusion in the basic call trace data. This increase. OMC-R reporting Each set of call trace criteria created using the trace_call command is reported to the OMC-R. may cause some call trace data for the OMC-R to be lost. 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. or OMC-R performance. BSSMAP. DTAP. 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. it can trace subscribers and equipment. Any combination of Abis. The trace_call command is primarily intended for tracing calls with unspecified subscriber and equipment IDs. Due to GSM architectural restraints. An instance is a set of criteria that defines a trace. BSS. 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. This permits the OMC-R to determine when the maximum number of traces has been reached in the BSS. MSC initiated traces are run immediately because the trace is for a call that is already in progress. together with “normal" OML traffic (such as alarms and uploads/downloads). The maximum number of traces that may be run simultaneously is 16 per LCF. Call trace data A basic set of call trace data is included in the reports generated by this command. 2-474 GMR-01 68P02901W23-P 23 Feb 2004 . this command can not reliably trace by subscriber or equipment. including MSC initiated traces. For example. no additional traces could run on that LCF even if the call is handed over to a cell controlled by another LCF. This percentage is specified using the call_trace_options parameter. the OML traffic may increase. For example. Therefore. a maximum of eight instances may be created using the trace_call command. The trace_call command creates a set of trace call criteria in the BSS that can trigger traces on calls. If a large number of call traces are initiated on multiple BSSs connected to a single OMC-R. if 50% of the traces are reserved for initiation from the MSC. however. refer to the “Notes" for the call selector prompt in the Related Information subsection. An MSC initiated trace affects the capacity of the LCF where the call originated.trace_call Chapter 2: Device/function related commands trace_call Description The trace_call command creates a call trace instance in the BSS. For the exact restraints. With limitations. MS_POWER_CONTROL. A maximum of 16 instances may exist on a BSS. 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. Use of the trace_call command may impact OML. After the command is entered.Technical Description BSS Command Reference trace_call Reports generated by this command include a set of basic call trace data. may cause some call_trace data to be lost. a large number of call traces initiated on multiple BSSs connected to a single OMC-R may increase the OML traffic. 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. MS_POWER_CONTROL. Implementing trace_call increases the amount of data passing over the OML. BSSMAP. This is the only valid input. together with “normal" OML traffic (such as alarms and uploads/downloads). Refer to the ct_flow_control_hi_level and ct_flow_control_lo_level parameters for more information. The prompted parameters are described under Related information at the end of this section. For example. RR and RSS data may also be specified for inclusion in the basic call trace data. rtf The name for the radio transmit function. Call Trace Flow Control reduces. Security level 2 Supported by OMC-R GUI No Command type A (no operator actions) Prerequisites This command is not allowed in SYSGEN mode. BSS. this from occuring. DTAP. Any combination of Abis. do not use rtf in the command syntax. This increase. This feature may impact OML. or OMC-R performance. 68P02901W23-P 23 Feb 2004 2-475 GMR-01 . the system displays a series of prompts. and may eliminate. • The system traces any call identified by SCCP number 747B6C (hexadecimal). EGSM. Do not combine these parameters in a single command. Examples Refer to the Related information subsection for a description of the prompts displayed in the following examples. DCS1800. PCS1900) • Whether the seven parameter GSM Cell ID format or the four parameter GSM Cell ID format has been enabled. • Output is directed to the MMI. id3 The third function identifier. cell_desc GSM Cell ID of the cell to be traced. cell_number or cell_name. The name of the cell created using the cell_name command may be entered in place of the cell_number. The format for the GSM Cell ID depends on: • The system used (PGSM. • Only one call is traced. When the cell name is entered. The system accepts only one of the following inputs: location. id2 The second function identifier. including a call already in progress. • Any trigger events may start a trace. DTAP and Abis data. 2-476 GMR-01 68P02901W23-P 23 Feb 2004 . including BASIC. Example 1 This example shows a BSS-wide trace to capture multiple data record types. it must be placed inside double quotation marks. preceded by cell_number=.trace_call Chapter 2: Device/function related commands id1 The first function identifier. BSSMAP. and be preceded by cell_name=. 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.Technical Description BSS Command Reference trace_call trace_call all Where: is: all location System response Enter trigger event: all Enter additional data types (Basic is always included): 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 bssmap. • Output is directed to the MMI and the OMC-R. abis COMMAND ACCEPTED If the response to the Enter additional data types prompt includes more than one data type. • The system traces any call involving the mobile unit identified by a specific IMEISV number. as shown in Example 1. trace_call cell_name="Trafalgar_Square" Where: is: Trafalgar_Square cell_name System response Enter trigger event: handover Enter additional data types (Basic is always included): Enter call selector type and value: imeisv="0010167890123021" Trigger enabled time: Enter total number of calls to be traced: Trace calls beyond scope?: no Enter destination for trace data: both COMMAND ACCEPTED 68P02901W23-P 23 Feb 2004 2-477 GMR-01 . • Tracing discontinues if the call leaves the scope. dtap. above. • This trace collects BASIC data only. each type must be separated by a comma and a space. • This trace collects BASIC and RSS data only. • The RSS reports Measurement Report data every eight intervals (one interval = 480ms). • No more that two calls will be traced simultaneously. including a call already in progress. • Any trigger event may start a trace. • Tracing is enabled at 9:00 pm. • Once a call triggers a trace. • Tracing discontinues if the call leaves the scope. • This trace collects BASIC and MS_POWER data only. RTF 0 0. 2-478 GMR-01 68P02901W23-P 23 Feb 2004 . trace_call 2 rtf 0 0 Where: is: 2 BTS location rtf rtf 0 id1 0 id2 System response Enter trigger event: all Enter additional data types (Basic is always included): Enter call selector type and value: nth=4 Enter maximum simultaneous calls traced per LCF: 2 Trigger enabled time: Enter total number of calls to be traced: 11 Trace calls beyond scope?: Enter destination for trace data: omc ms_power COMMAND ACCEPTED Example 4 This example shows a trace on RTF 0 1 at BTS site 4. • The system traces every fourth call. • The tracing continues until eleven calls have been traced. • The system traces every seventh call. including a call already in progress.trace_call Chapter 2: Device/function related commands Example 3 This example shows a trace on BTS location 2. • Output is directed to the OMC-R. • Any trigger event may start a trace. • No more that four calls can be traced simultaneously. all trace data of the specified types is collected. References Related information Prompts preceded by an * in Table 2-34 are only displayed under the conditions described in the Notes column.Technical Description BSS Command Reference trace_call • Tracing is disabled at 10:00 pm. 68P02901W23-P 23 Feb 2004 2-479 GMR-01 . • Output is directed to the MMI by default. • Tracing continues if the call leaves the scope. trace_call 4 rtf 0 1 Where: is: 4 BTS location rtf rtf 0 id1 1 id2 System response Enter trigger event: all Enter additional data types (Basic is always included): 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: rss COMMAND ACCEPTED The “Enter Measurement Report interval (X480ms)" prompt displays only if the operator enters “no" to the previous prompt. Motorola recommends using larger values. Multiple data record types can also be listed. This parameter specifies the number of 480ms periods to wait before collecting another measurement report. 68P02901W23-P 23 Feb 2004 . Using a value of 3 or less can overload the OML with measurement data. upon criteria created on entering of any daily triggering period. the system prompts for an additional parameter. rss Collect during handover only?: yes no 1 0 * Enter Measurement Report interval (X480ms): Any value between 1 and 255 2-480 GMR-01 If RSS is entered as a data type. If the user specifies data only during handovers. 10 (4. like this: dtap. If multiple data types are used. Abis and/or MS_Power call trace data. all includes tracing calls that are already in progress.trace_call Chapter 2: Device/function related commands Table 2-34 trace_call prompts and values Prompt Valid range or values Default Notes Enter trigger event: setup handover all all If a particular mobile or SCCP number has been specified. Measurement reports are produced every 480 ms. then this parameter defaults to one. 0 or no means that the system collects all of the specified types of trace data when they are available. only if specified. and only before and after a handover has occurred. The user need not collect all measurement reports. the “Measurement Report Interval. Abis and/or MS_Power data types are specified.8 seconds) The system displays this prompt if the RSS data type is specified in the preceding prompt and the user did not specify data only during handovers. Enter additional data types (Basic is included): abis bssmap dtap ms_power rr rss all Basic Basic data is always sent. 1 or yes means the system will collect RSS. The number of messages collected is determined by the trace_msgs_before_ho and trace_msgs_after_ho data base parameters." No The system only prompts for this parameter if the RSS. separate them with a comma and space. If a time is specified. Also. If Nth call is specified. using a 24 hour clock. The larger the value set. the operator must either: 68P02901W23-P 23 Feb 2004 • specify a total number of calls to trace. A valid value is required. the more it will overload the OML. Enter call selector type and value: IMSI=“msid" TMSI=“msid" IMEI=“msid" IMEISV=“msid" SCCP=0 to FAFFFFh Nth= 1 to 255 * Enter maximum simultaneous calls traced per LCF: Any value between 1 through 16 Triggered enabled time: A time between Midnight (00 00) and 23 59. Enter the time without using a colon. Instead use the MSC to trace more reliably by IMEI or IMEISV.Technical Description BSS Command Reference Table 2-34 trace_call trace_call prompts and values (Continued) Prompt Valid range or values Default Notes None Mobile station identifier (“msid") is a number that identifies a specific mobile unit or subscriber. and the setting of the measurement report interval (above). the system prompts for the “maximum simultaneous calls traced per LCF. 1 The system displays this prompt if the call selector type is Nth call. Once enabled. the trace begins immediately and no trace period is used. 8 25 PM would be: 20 25 Immediate start If no time is specified. reliable IMSI tracing requires the MSC to page by IMSI instead of TMSI. The signalling connection control part (SCCP) number identifies a particular call. For example. To delete the trace. For example. 2-481 GMR-01 . Motorola recommends using smaller values. or • delete the trace manually. 8 25 PM would be: 20 25 None The system displays this prompt if a trigger enabled time is specified." 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. the trace must still be triggered according to the specified trigger event before data will be collected. Enter the time without using a colon. it is suspended until the trigger enabled time the following day. * Trigger disabled time A time between Midnight (00 00) and 23 59. the system prompts for the “trigger disable time." “Time" is the time of day. Do not put quotation marks around a SCCP number or an Nth call number. The trace is not deleted at the trigger disabled time. depending also on how broad the scope. It must be enclosed in double quotation marks. 16 is the maximum number of simultaneous traces per LCF. mmi Trace reports may be directed to the MMI. the OMC-R. If a value is specified. or both. 2-482 GMR-01 68P02901W23-P 23 Feb 2004 . no limit) the trace will exist until the trace is deleted manually by an operator. that is. Related commands "disp_trace_call" on page 2-315.trace until deleted manually If no value is specified. or until it leaves the current BSS. Yes or 1 means that once a call triggers a trace. the trace will be deleted automatically after the specified number of calls have been traced. "trace_stop" on page 2-486.trace_call Chapter 2: Device/function related commands Table 2-34 trace_call prompts and values (Continued) Prompt Valid range or values Enter total number of calls to be traced: Any value between 1 through 255 Trace calls beyond scope? yes or no 1 or 0 Enter destination for trace data: mmi omc both Default Notes None . no No or 0 means trace data is no longer collected if the call hands out of the specified scope. it will be traced beyond the scope until the call is completed. and the MMSs through which the connectivity path passes. the user is prompted for the MMS timeslot. The information includes the Site ID. If the requested trace is for an MMS. Security level 2 Supported by OMC-R GUI No Command type A (no operator actions) 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. MMS ID. MMS timeslot numbers for all sites. <id1><id2><id3> 68P02901W23-P 23 Feb 2004 2-483 GMR-01 . the user is prompted to enter the MMS timeslot number.Technical Description BSS Command Reference trace_connection trace_connection Description The trace_connection command displays the timeslot connectivity information for a specified device. trace_connection Chapter 2: Device/function related commands 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: 0 the location (the BSC) rsl 4 1 the device System response Start of Report Path Id: 4 1 Site MMS BSC downlink BTS 1 uplink downlink BTS 4 uplink End of Report 2 0 1 0 Timeslot(s) 0 16 0 16 1 2 1 2 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: 2-484 GMR-01 68P02901W23-P 23 Feb 2004 . Technical Description BSS Command Reference trace_connection trace_conn 0 mms 2 0 Where: is: 0 the location (the BSC) mms 2 0 the device System response Enter the timeslot: 3 Start of Report Timeslot Usage: RSL 0 0 Site MMS Timeslot(s) BSC downlink 2 0 16 TS_SWITCH N/A N/A BTS 4 uplink 0 0 16 End of Report 68P02901W23-P 23 Feb 2004 2-485 GMR-01 . sccp between 0 and 0FAFFFFh ref between 0 and 0FFFFFFFFh The hexadecimal number input requires a 0 prefix and an h suffix. 2-486 GMR-01 68P02901W23-P 23 Feb 2004 . sccp SCCP number. value The hexadecimal value for the sccp or reference number. all All traces. ref Trace reference number.trace_stop Chapter 2: Device/function related commands trace_stop Description The trace_stop command deletes an existing trace or stops tracing a specified call. Security level 2 Supported by OMC-R GUI Yes Command type A (no operator actions) Prerequisites This command is not allowed in SYSGEN mode. This input requires a <value>. This input does not require or allow a <value>.. Then the valid range is. Format Syntax trace_stop <type> [=<value> <extent>] Input parameters type The reference type for the trace. This input requires a <value>.... If the type is. and the specified instance should be deleted once all previously triggered traces are completed. 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. the system defaults to all. the trace instance will be deleted from the database. all All traces should be stopped and the specified instance should be deleted immediately. new No new traces are to be started. When the current traces are completed. 68P02901W23-P 23 Feb 2004 2-487 GMR-01 . If no extent is set. 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. extent is not valid when type is set to sccp.Technical Description BSS Command Reference trace_stop extent The extent to which traces should stop. Examples Example 1 This example stops tracing a call with SCCP = 047BC6h. while continuing any current call traces. trace_stop Chapter 2: Device/function related commands trace_stop ref=080270001h new Where: is: ref type 080270001h value new extent System response COMMAND ACCEPTED 2-488 GMR-01 68P02901W23-P 23 Feb 2004 . BTP. This command returns the CSFP device back to a BSP. Example In this example. or pooled GPROC device depending on the original acquired device. Security Level 2 Supported by OMC-R GUI Yes Command Type B (operator actions required) Prerequisites The system must be in SYSGEN mode to execute this command. Operator actions Put the system into SYSGEN mode. Format Syntax unconfigure_csfp Input parameters There are no input parameters associated with this command.Technical Description BSS Command Reference unconfigure_csfp unconfigure_csfp Description The unconfigure_csfp command unconfigures CSFP devices from sites in the BSS network. all of the CSFP devices in the network are unconfigured. Enter this command at the BSC only. This command does not work at a BTS site. unconfigure_csfp 68P02901W23-P 23 Feb 2004 2-489 GMR-01 . Contact the OMC-R for help. 2-490 GMR-01 68P02901W23-P 23 Feb 2004 .unconfigure_csfp Chapter 2: Device/function related commands System response COMMAND ACCEPTED References Related commands "chg_csfp" on page 2-84. "configure_csfp" on page 2-152. "disp_csfp" on page 2-225. This command does not work at a BTS site. SYSGEN states Place the system in the SYSGEN ON mode using the sysgen_mode on command. No child dependencies may exist for the specified device or function to be unequipped.Technical Description BSS Command Reference unequip unequip Description The unequip command deletes a device or function from the FM portion of the CM database. Place the system in the SYSGEN ON mode if an CBL. See SYSGEN states below for further information Operator actions Lock the device or function to be unequipped. the unequip command will be rejected. Contact the OMC-R for help. use the sysgen_mode off command. or OML is to be unequipped using this command. Security level 2 Supported by OMC-R GUI Yes Command type B (operator actions required) Prerequisites The unequip command is only allowed for a locked device or function. Enter this command at the BSC only. The unequip command is rejected if any child dependencies exist for the specified device or function. OMF. To leave the SYSGEN ON mode. If a dependency is detected. MTL. 68P02901W23-P 23 Feb 2004 2-491 GMR-01 . unequip Chapter 2: Device/function related commands 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. 2-492 GMR-01 68P02901W23-P 23 Feb 2004 . CICs must be equipped on a pre-MMS basis when the BSC operates in the dynamic allocation mode. • CSFP (InCell) • DHP (InCell) The unequip command is not available for DHP devices at a Horizonmicro. • COMB (not M-Cellmicro) All affected COMB devices must be OOS before using the unequip command. • DRI • DPROC DPROC performed at site PCU. 68P02901W23-P 23 Feb 2004 • MTL • OML • PATH 2-493 GMR-01 .Technical Description BSS Command Reference • unequip 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. 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. lock it at either the OMC-R or at the MMI prompt. or (2) It causes the total terrestrial backing resources for a BTS network to be less than the total reserved cell capacity. • EAS (not M-Cellmicro) • GBL • GCLK (InCell) • GDS • GPROC (InCell) • GSL To bring the GSL out of service. 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. An MSI cannot be unequipped if the device is referenced in the BSS-RXCDR connectivity table. An RTF cannot be unequipped if the resulting reduced number of available timeslots or carriers is not sufficient to maintain current or less-one GPRS configurations.unequip Chapter 2: Device/function related commands • PCU {4040} Up to three PCUs can be equipped. • SITE The unequip command for a SITE device at a Horizonmicro BTS automatically unequips any DGP devices that exist at that BTS site. A warning message is generated if an attempt is made to unequip an RTF with a non-zero sd_load value. and (2) one or more of the FHIs associated with the RTF are enabled. • XBL • AXCDR • ABSS 2-494 GMR-01 68P02901W23-P 23 Feb 2004 . PCU_1 and PCU_2. and therefore unequipped as PCU_0. The unequip command will automatically unequip the additional 16K RSL when a 16K RSL is being unequipped as part of a closed loop DYNET. • 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. • RTF An RTF cannot be unequipped if both of the following conditions are true: (1) The cell is baseband hopping. These devices may be unequipped with the system in or out of the SYSGEN ON mode. 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. {4420}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. pcu_0 to pcu_2 {4040} PCU dev/func_name Literal that uniquely identifies the device or function. • BSP • BTP When unequipping BTPs from M-Cell sites. The LCF may be unequipped with the system in or out of the SYSGEN mode.Technical Description BSS Command Reference unequip Standby devices The following devices or functions may only be unequipped using the unequip command if they are standby devices. 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 pcu. BTP 0 must be the last BTP unequipped. The following devices and functions may be entered: 68P02901W23-P 23 Feb 2004 bsp dri omf btp dynet oml cab eas path 2-495 GMR-01 . The last KSW in a system may not be unequipped using the unequip command. The system does not have to be locked when the LCF is unequipped outside the SYSGEN ON mode. The SITE must be unequipped using the unequip command to remove the last KSW from the database. specify the BSC for the location. that is. No other cabinet types are supported. When unequipping an EAS. MSI. except for GDS and GSL. Child dependency may exist when unequipping the PCU. only the first identifier is required. and NSVC may exist when the PCU is unequipped. HORIZONMACRO_EXT. This definition varies with each device or function. The following ranges of values may be entered: 0 to 7 InCell sites 0 to 15 M-Cell sites id2 Second identifier. except for the PCU itself. and Horizon II macro provided the cabinet is locked and no DRIs or EASs are equipped to the cabinet. TCU_6.unequip Chapter 2: Device/function related commands 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. This definition varies with each device or function. DPROC. id1 First identifier. To unequip the PCU. GBL. 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 2-496 GMR-01 68P02901W23-P 23 Feb 2004 . When unequipping an PATH. the range varies depending on whether the BTS uses dynamic allocation. The following GPRS devices can be used with this command: dproc gds gbl gsl pcu The PCU location must be specifed when unequipping the GPRS devices. mms_id1 First MMS identifier. group2 Second group. mms_id2 Second MMS identifier. cic_num1 First CIC device number. 68P02901W23-P 23 Feb 2004 2-497 GMR-01 . or last in a range if TO is used. timeslot1 First timeslot. CIC syntax A form of syntax is available for each method of specifying a CIC. group1 First group. timeslot2 Second timeslot. The following CIC syntax apply to local transcoding: unequip unequip unequip unequip unequip <location> <location> <location> <location> <location> CIC CIC CIC CIC CIC <cic_num1> <cic_num1> TO <cic_num2> <mms_id1> <mms_id2> <mms_id1> <mms_id2> <timeslot1> <mms_id1> <mms_id2> <timeslot1> TO <timeslot2> The following CIC syntax apply to remote transcoding: unequip <location> CIC <cic_num1> unequip <location> CIC <cic_num1> TO <cic_num2> unequip <location> CIC <mms_id1> <mms_id2> unequip <location> CIC <mms_id1> <mms_id2> <timeslot1> <group> unequip <location> CIC <mms_id1> <mms_id2> <timeslot1> * unequip <location> CIC <mms_id1> <mms_id2> <timeslot1> <group1> TO <timeslot2> <group2> CIC Literal that uniquely identifies the CIC device. cic_num2 Last CIC device number in a range. or last in a range if TO is used. This definition varies with each device or function.Technical Description BSS Command Reference unequip id3 Third identifier. 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. 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.unequip Chapter 2: Device/function related commands * Indicates all CICs on the MMSs specified in the timeslot. the system blocks unequipping the RSL because the reserved cell capacity would exceed the total terrestrial backing resources for the BTS network: 2-498 GMR-01 68P02901W23-P 23 Feb 2004 . Examples Example 1 In this example. regardless of group. Example 4 This example unequips a range of CICs. 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. unequip 50 cab 1 0 0 Where: is: 50 location cab device_name 1 id1 0 id2 0 id3 System response COMMAND ACCEPTED 68P02901W23-P 23 Feb 2004 2-499 GMR-01 . or HORIZONMACRO_EXT with the cabinet locked and no DRIs or EASs equipped to the cabinet.Technical Description BSS Command Reference unequip 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. specifying them by their MMS. TS and group. TCU_6. unequip Chapter 2: Device/function related commands Example 6 {4040} This example unequips PCU 0 from a BSC. "equip" on page 2-327. "lock_device" on page 2-385. "shutdown_device" on page 2-433. unequip 0 pcu 0 Where: is: 0 location pcu device_name 0 id1 References Related commands "disp_equipment" on page 2-234. "unlock_device" on page 2-501 2-500 GMR-01 68P02901W23-P 23 Feb 2004 . "state" on page 2-445. pcu_0 to pcu_2 {4040} PCU device_name Literal that uniquely identifies the device.Technical Description BSS Command Reference unlock_device unlock_device Description The unlock_device command unlocks a specified device to free it for use. To unlock a PCU device. or pcu if unlocking a GPRS device. {4040} Also the PCU device identifier must be specified. Security level 2 Supported by OMC-R GUI Yes Command type B (operator actions required) Prerequisites This command is not allowed while in SYSGEN ON mode. the GPRS feature must be unrestricted. 68P02901W23-P 23 Feb 2004 2-501 GMR-01 . Format Syntax unlock_device <location> <device_name> <device_id1> <device_id2> <device_id3> Input parameters location Specifies the location of the device: 0 or bsc BSC 1 to 120 BTS pcu. The location must be bsc or 0 when specifying the device. Operator actions Lock the device before entering this command. This command is only valid when the device is in the LOCKED state. and HORIZONMACRO_EXT. device_id3 Third device identifier. The following GPRS only devices may be unlocked at the PCU using this command: DPROC GBL GDS GSL PCU device_id1 First device identifier. device_id2 Second device identifier. No other cabinet types are supported.unlock_device Chapter 2: Device/function related commands The following devices can be unlocked using this command: ABSS AXCDR BSP BTP CAB CBL CIC COMB CSFP DHP 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. This definition varies with each device. TCU_6. This definition varies with each device. This definition varies with each device. The following CIC syntax apply to local transcoding: unlock_device <location> CIC unlock_device <location> CIC unlock_device <location> CIC unlock_device <location> CIC unlock_device <location> CIC <timeslot1> TO <timeslot2> <cic_num1> <cic_num1> TO <cic_num2> <mms_id1> <mms_id2> <mms_id1> <mms_id2> <timeslot1> <mms_id1> <mms_id2> The following CIC syntax apply to remote transcoding: unlock_device <location> CIC <cic_num1> unlock_device <location> CIC <cic_num1> TO <cic_num2> unlock_device <location> CIC <mms_id1> <mms_id2> unlock_device <location> CIC <mms_id1> <mms_id2> <timeslot1> <group> unlock_device <location> CIC <mms_id1> <mms_id2> <timeslot1> * unlock_device <location> CIC <mms_id1> <mms_id2> <timeslot1> <group1> TO <timeslot2> <group2> 2-502 GMR-01 68P02901W23-P 23 Feb 2004 . CIC syntax A form of syntax is available for each method of specifying a CIC. an MMS with the ID 0 at the BSC is unlocked: unlock_device bsc mms 0 0 0 Where: 68P02901W23-P 23 Feb 2004 is: bsc location mms device_name 0 device_id1 0 device_id2 0 device_id3 2-503 GMR-01 . mms_id2 Second MMS identifier. or last in a range if TO is used. timeslot2 Second timeslot. cic_num2 Last CIC device number in a range. cic_num1 First CIC device number. group1 First group. Examples Example 1 In this example. mms_id1 First MMS identifier. group2 Second group. regardless of group. * Indicates all CICs on the MMSs specified in the timeslot.Technical Description BSS Command Reference unlock_device CIC Literal that uniquely identifies the CIC device. or last in a range if TO is used. timeslot1 First timeslot. TS and group. "state" on page 2-445. "lock_device" on page 2-385. 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-234. 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 {4040} This example unlocks a GPRS PICP MSI at the first PCU. "equip" on page 2-327. "unequip" on page 2-491. 2-504 GMR-01 68P02901W23-P 23 Feb 2004 .unlock_device Chapter 2: Device/function related commands System response COMMAND ACCEPTED Example 2 This example unlocks a range of CICs (remote transcoder) specifying them by their MMS. References . whether supported by OMC-R GUI. 68P02901W23-P 23 Feb 2004 3-1 GMR-01 . Description .Chapter 3 UNIX commands Selected UNIX commands provide a useful addition to MMI commands.giving the command line syntax and descriptions of the command parameters.the actual command reference. Examples .providing a description of the command operation. the type of command. and the prerequisites for the command to be accepted by the system. 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 . This chapter describes several UNIX commands that may be used from the MMI.giving any related commands. Format .providing specific examples of command input and the resulting system response. and including information on the command security level. The alias applies only to the GPROC for which it is set. This includes the command name (alias) and the alias name. The maximum length which can be entered is 256 characters. Example This example creates an alias called “list" which executes the command string disp_equipment bsc: 3-2 GMR-01 68P02901W23-P 23 Feb 2004 . alias_text Any valid MMI command. A login to a different GPROC will not recognise the alias. This can be just the command name or a command and parameters. Security level Any Supported by OMC-R GUI No Command type A (no operator actions) Prerequisites None Format Syntax alias [<alias_name>’<alias_text>’] Input parameters alias_name Name of the alias. If no parameters are entered.alias Chapter 3: UNIX commands alias Description The alias command creates an alias for an MMI command. a list of active aliases are displayed. The alias_text must be enclosed in single quotes. 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-P 23 Feb 2004 3-3 GMR-01 . help Chapter 3: UNIX commands help Description The help command displays help information about the specified command. Additional online information may be displayed by using the man command. If no command is specified. a list of all available commands is displayed. 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 GMR-01 68P02901W23-P 23 Feb 2004 . Security level Any Supported by OMC-R GUI No Command type A (no operator actions) Prerequisites None Format Syntax help [<command>] Input parameter command String specifying an MMI command. Technical Description BSS Command Reference help References Related command "man" on page 3-8. 68P02901W23-P 23 Feb 2004 3-5 GMR-01 . Examples Example 1 This example lists the last three commands that were entered: 3-6 GMR-01 68P02901W23-P 23 Feb 2004 . If this parameter is not entered. the last 23 commands are displayed. This command may also be used to repeat one of the commands displayed in the listing. The default is 23. Security level Any Supported by OMC-R GUI No Command type A (no operator actions) Prerequisites None Format Syntax history [<num_commands>] or !<num_commands> or !! Input parameter num_commands The number of previously entered commands to display.history Chapter 3: UNIX commands history Description The history command displays a numbered list of previously entered MMI commands. 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. it is the disp_dte command. the following command string will execute the statement contained in command number 13 shown in the command history list: !13 In this case. The command string !! executes the last command again. 68P02901W23-P 23 Feb 2004 3-7 GMR-01 . Create an alias for an MMI command. 3-8 GMR-01 68P02901W23-P 23 Feb 2004 .man Chapter 3: UNIX commands man Description The man command is used to display detailed help information about the specified command. a list of active aliases are displayed. 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: Function : Can be executed from any security level. If no parameters are entered. Security level Any Supported by OMC-R GUI No Command type A (no operator actions) Prerequisites None Format Syntax man <command> Input parameter command String specifying an MMI command. or a command and parameters. This MUST be enclosed in single quotes. <alias_text> Any valid MMI command. 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.Technical Description BSS Command Reference man <alias_name> The name of the alias. This can be just the command name. 68P02901W23-P 23 Feb 2004 3-9 GMR-01 . Example This example removes the alias named “list".unalias Chapter 3: UNIX commands unalias Description The unalias command removes the alias <alias_name> from the specific GPROC at which it was set. unalias list Where: is: list alias_name System response COMMAND ACCEPTED 3-10 GMR-01 68P02901W23-P 23 Feb 2004 . Security level Any Supported by OMC-R GUI No Command type A (no operator actions) Prerequisites None Format Syntax unalias <alias_name> Input parameter alias_name The name of the alias to be removed. 68P02901W23-P 23 Feb 2004 3-11 GMR-01 .Technical Description BSS Command Reference unalias References Related command "alias" on page 3-2. 3-12 GMR-01 68P02901W23-P 23 Feb 2004 .unalias Chapter 3: UNIX commands This page intentionally left blank. whether supported by OMC-R GUI. Description . References .Chapter 4 Statistics commands Statistics commands are MMI commands used to perform statistical operations and obtain statistical information.providing specific examples of command input and the resulting system response. 68P02901W23-P 23 Feb 2004 4-1 GMR-01 .providing a description of the command operation. and the prerequisites for the command to be accepted by the system. and provides reference information for each MMI statistical command. Examples .the actual command reference.giving any related information or related commands. and including information on the command security level. Format .giving the command line syntax and descriptions of the command parameters. Descriptions of individual statistics are described in the Maintenance Information: GSM Statistics Application (68P02901W56) manual. the type of command. This chapter describes the statistical operations and different types of statistical information that can be obtained using MMI statistics commands. The statistics commands are described separately in alphabetical order using the following command reference layout: Command title . • System installation and commissioning.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). • Duration statistics. • Monitor active (enabled) system statistics. • stat_mode (see "stat_mode" on page 4-28). Statistical operations The statistical commands perform the following statistical operations: • Enable/disable statistics. Statistical information Statistical information is generated by the system and can be used by system operators for: • Monitoring the quality of service. • Fault finding. • Network planning.(see "disp_stats" on page 4-22). • disp_interval (see "disp_interval" on page 4-15). • disp_stat_prop (see "disp_stat_prop" on page 4-17). • Monitor system statistics over specified time intervals. 4-2 GMR-01 68P02901W23-P 23 Feb 2004 . Statistical information is gathered in the form of: • Counter statistics. • disp_stats. • Optimize system performance. • Report statistical data. • disp_enable_stat (see "disp_enable_stat" on page 4-11). • Display/modify statistics for devices or cells. normal and weighted. The event to be monitored is specified as the database parameter in the chg_element command. • Distribution statistics. Gauge statistics Gauge statistics report the maximum and mean values of a statistic for an interval. Threshold event reporting An alarm threshold may be specified for gauge statistics. and if the result is a negative number. the cumulative value may not be a negative value. The resulting statistics express the total amount of time a particular event occurred. the alarm is reported to the OMC-R. The mean and maximum gauge statistic values at the interval expiry are saved and reset to 0 at the interval expiry.Technical Description BSS Command Reference • Gauge statistics. are used to record all events or state changes reported by some application processes. and mean durations (in milliseconds). The event data are recorded for statistical analysis. Distribution statistics Two types of distribution statistics. Duration statistics Duration (or total time) statistics involve the use of a timer to collect a cumulative time value. While a gauge statistic may result in the report of a reported negative value. If a threshold is reached. an alarm is sent to the OMC-R. Counter statistics may only be enabled and disabled. Certain counter statistics have associated alarms. the mean value is set to zero. 68P02901W23-P 23 Feb 2004 4-3 GMR-01 . Interval expiry Interval expiry is the end of a statistic interval. Statistical operations and information Counter statistics Counter statistics represent the number of occurrences of an event. If a threshold is reached. maximum. as well as minimum. Duration statistics may only be enabled and disabled. The timer starts when an event begins and stops when it ceases. A check is performed before calculating the mean value. The IDLE_TCH_INTF_BAND0 statistic is an example of a gauge statistic. if the range of a bin is 10 to 20. The statistical value displayed is the cumulative time of the events occurring within that range of a bin. the statistical value is 3. 4-4 GMR-01 68P02901W23-P 23 Feb 2004 . if the range of a bin is 10 to 20. and the application process reports a value of 15 three times. For example. Statistics descriptions Refer to the Maintenance Information: GSM Statistics Application (68P02901W56) for detailed information on each statistical parameter. The range of a bin is determined by the size of the upper and lower bins in which the data is collected. Weighted distribution statistics record the length of time (in milliseconds) that an element is at a specific value. and the application process reports six events with a value of 15 lasting 12 milliseconds each. the statistical value is 72. For example.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 specific properties that may be changed depend on the statistic type. and duration statistics if an alarm is associated with the statistic. Security level 2 Supported by OMC-R GUI Yes Command type A (no operator actions) Prerequisites The GPRS feature must be unrestricted to display PCU statistics. Contact the OMC-R for help. • The alarm threshold may be changed for counter. • Bin ranges may be changed for normal and weighted statistics. When the chg_stat_prop command is entered the system displays a series of prompts. gauge. Refer to References/Related information for explanations of the prompts associated with each statistic. {23658} The EGPRS feature must be unrestricted to display EGPRS associated statistics. This command does not work at a BTS site.Technical Description BSS Command Reference chg_stat_prop chg_stat_prop Description The chg_stat_prop command changes the properties of statistics. The specific prompts depend on the statistic type. • Properties may not be changed for duration ("total time") or counter array statistics. Enter this command only at the BSC. Format Syntax chg_stat_prop <meas_type> [location] [<cell_desc>] chg_stat_prop <meas_type> all Input parameters meas_type 68P02901W23-P 23 Feb 2004 4-5 GMR-01 . The format for the GSM Cell ID depends on: • The system used (PGSM.chg_stat_prop Chapter 4: Statistics commands Specifies the name of the statistic. This command responds to the shortened input parameter cell= allowing entry of either the cell_number or the cell_name without further definition. PCS1900). DCS1800. If entered. The value all is also a valid input for the cell_desc. 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 GMR-01 68P02901W23-P 23 Feb 2004 . preceded by cell_number=. it must be placed inside double quotation marks and be preceded by cell_name=. location Specifies the site 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. the mode for the statistic changes for all cells at the specified site. • Whether the seven parameter GSM Cell ID format or the four parameter GSM Cell ID format has been enabled. EGSM. 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. 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 Enter Enter Enter Enter the the the the the bin min max min max number(s): 0.Technical Description BSS Command Reference chg_stat_prop 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. 1 value for bin 0: value for bin 0: value for bin 1: value for bin 1: 0 5 carriage return 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: 68P02901W23-P 23 Feb 2004 is: out_ho_cause_atmpt meas_type 1 location all all cells at the specified site 4-7 GMR-01 . 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. 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 {23658} 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 4-8 GMR-01 68P02901W23-P 23 Feb 2004 . chg_stat_prop tch_congestion 1 all Where: is: tch_congestion meas_type 1 location all all cells at the specified site System response COMMAND REJECTED: Threshold cannot be set for non-alarming statistics. 68P02901W23-P 23 Feb 2004 4-9 GMR-01 .Technical Description BSS Command Reference chg_stat_prop System response COMMAND REJECTED: Received a request to modify a restricted optional parameter. the command is rejected and this prompt is not presented. If an alarm is not associated with the specified statistic. Table 4-2 lists the normal and weighted distribution statistic type prompts. If a <carriage return> is entered in response to the first prompt. Enter the max value for bin n: The maximum value that may be entered is 2147483647 This prompt repeats for each bin number (n) entered in response to the first prompt. References Related information Table 4-1 lists the counter and gauge statistic type prompts. Enter the min value for bin n: The minimum value that may be entered is 0 This prompt repeats for each bin number (n) entered in response to the first prompt. the current value does not change. Table 4-1 Counter and gauge statistic type prompts Prompt Enter the alarm threshold Valid range 0 to 2147483647 Description If a <carriage return> is entered in response to this prompt. If a <carriage return> is entered in response to the first prompt the current value is not changed. 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. Table 4-2 Normal and weighted distribution statistic type prompts Prompt Valid range Description Enter the bin number(s): 0 to 9 Multiple bin numbers may be entered by separating each bin number with a space or comma. chg_stat_prop Chapter 4: Statistics commands Related commands "disp_element" on page 2-231. "disp_interval" on page 4-15. "disp_enable_stat" on page 4-11. 4-10 GMR-01 68P02901W23-P 23 Feb 2004 . "disp_stats" on page 4-22. Security level 1 Supported by OMC-R GUI Yes Command type A (no operator actions) Prerequisites None Format Syntax disp_enable_stat disp_enable_stat <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. A cell_desc is specified only for per cell. Specific listings generated by this command depend on the argument entered with the command. 68P02901W23-P 23 Feb 2004 4-11 GMR-01 . per neighbour cell. preceded by cell_number=. the command displays the GSM Cell ID of the cells which have the statistic enabled.Technical Description BSS Command Reference disp_enable_stat disp_enable_stat Description The disp_enable_stat command displays the status of statistics. If “bss" is entered with the command. If a Location ID is entered with the command. a listing of the enabled statistics in the BSS displays. a listing of enabled statistics at the specified cell displays. If a Cell ID (or name) is entered with the command. a listing showing all of the enabled statistics displays. If no arguments are entered with the command. and per timeslot statistics. the command displays the state of the statistic. When the name of a BSS-wide statistic is entered. a listing of the enabled statistics at the specified location displays. When the name of a per-cell statistic is entered. A specific statistic may be entered as the meas_type. disp_enable_stat Chapter 4: Statistics commands The format for the GSM Cell ID depends on: • The system used (PGSM, EGSM, DCS1800, PCS1900). • Whether the seven parameter GSM Cell ID format or the four parameter GSM Cell ID format has been enabled. The name of the cell created using the cell_name command may be entered in place of the cell_number. When the cell name is entered, it must be placed inside double quotation marks and 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. bss Specifies the BSS. location Specifies the site location: 0 or bsc BSC 1 to 120 BTS meas_type Specifies the name of the statistic. Examples Example 1 In this example, an abbreviated list of all the enabled statistics is displayed when the disp_enable_stat command is entered with no arguments. Actual output from the system shows all statistics. The output includes all non-cell and individual cell statistics. disp_enable_stat The text that follows shows part of a typical display. Such a display continues until all of the enabled statistics have been displayed. 4-12 GMR-01 68P02901W23-P 23 Feb 2004 Technical Description BSS Command Reference disp_enable_stat 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 {23658} 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 68P02901W23-P 23 Feb 2004 4-13 GMR-01 disp_enable_stat Chapter 4: Statistics commands busy_sdcch ber 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 Statistic total_calls enabled for the following cells at site 30 ---------------------------------------------------------------543 21 F333h 2128h Statistic total_calls enabled for the following cells at site 31 ---------------------------------------------------------------543 21 F333h 0031h Statistic total_calls enabled for the following cells at site 32 ---------------------------------------------------------------543 21 F333h 2127h Statistic total_calls enabled for the following cells at site 36 ---------------------------------------------------------------543 21 F333h 2124h 543 21 F333h 2125h 543 21 F333h 2126h Example 3 This example shows 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-231, "stat_mode" on page 4-28, "disp_interval" on page 4-15, "disp_stats" on page 4-22. 4-14 GMR-01 68P02901W23-P 23 Feb 2004 Technical Description BSS Command Reference disp_interval disp_interval Description The disp_interval command displays the start times associated with each of the system statistics intervals. Security level 1 Supported by OMC-R GUI Yes Command type A (no operator actions) Prerequisites This command is not allowed in SYSGEN ON mode. Format Syntax disp_interval Input parameters There are no input parameters associated with this command. Example This example shows a sample of the display the system produces when the disp_interval command is entered: disp_interval System response Interval -------0 1 2 3 4 5 6 7 8 68P02901W23-P 23 Feb 2004 Start Time (HH:MM:SS) --------------------09:08:48 09:29:59 10:00:00 10:30:00 11:00:00 11:30:00 12:00:00 12:30:00 13:00:00 4-15 GMR-01 disp_interval Chapter 4: Statistics commands 9 10 11 13:30:00 14:00:00 14:30:00 References Related commands "disp_element" on page 2-231, "disp_enable_stat" on page 4-11, "stat_mode" on page 4-28, "disp_stats" on page 4-22. 4-16 GMR-01 68P02901W23-P 23 Feb 2004 Technical Description BSS Command Reference disp_stat_prop 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 Supported by OMC-R GUI Yes Command type A (no operator actions) 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 68P02901W23-P 23 Feb 2004 4-17 GMR-01 disp_stat_prop Chapter 4: Statistics commands Specifies the site location: 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=. The format for the GSM Cell ID depends on: • The system used (PGSM, EGSM, DCS1800, PCS1900). • Whether the seven parameter GSM Cell ID format or the four parameter GSM Cell ID format has been enabled. The name of the cell created using the cell_name command may be entered in place of the cell_number. When the cell name is entered, it must be placed inside double quotation marks and 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. The value all is also a valid input for the cell_desc. If entered, the mode for the statistic changes for all cells at the specified site. Examples Example 1 This example displays the properties 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: total_calls meas_type 5 4 3 2 1 61698 34776 cell_desc System response STATISTIC: TOTAL_CALLS TYPE: PER CELL SITE: 1 OBJECT: COUNTER ALARM CELL# MODE ------------------------------------- ---------543 21 61698 (f102h) 34776 (87d8h) ENABLED 4-18 GMR-01 ALARM SEVERITY THRESHOLD ---------- --------NO ALARM N/A 68P02901W23-P 23 Feb 2004 Technical Description BSS Command Reference disp_stat_prop 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: total_calls meas_type 1 location all all cells at the specified location. System response STATISTIC: TOTAL_CALLS TYPE: PER CELL SITE: 1 OBJECT: COUNTER ALARM ALARM CELL# MODE SEVERITY THRESHOLD ------------------------------------- ---------- ---------- --------543 543 543 543 543 21 21 21 21 21 61698 61698 61698 61698 61698 (f102h) (f102h) (f102h) (f102h) (f102h) 34776 34777 34778 34779 34780 (87d8h) (87d9h) (87dah) (87dbh) (87dch) ENABLED ENABLED ENABLED ENABLED ENABLED NO NO NO NO NO ALARM ALARM ALARM ALARM ALARM N/A N/A N/A N/A 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 TYPE: OTHER SITE: 1 OBJECT: COUNTER ALARM ALARM CELL# MODE SEVERITY THRESHOLD ------------------------------------- ---------- ---------- --------N/A SITE: 0 CELL #: LAC = f222h MEAS_TYPE : CHANNELS_DISABLED Gauge Value: 5 Max.: 5 ENABLED CI = 8880h WARNING 2147836 Example 4 This example displays the properties associated with the BUSY_TCH statistic for cell number 5 4 3 2 1 61698 34776. 68P02901W23-P 23 Feb 2004 4-19 GMR-01 disp_stat_prop Chapter 4: Statistics commands 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 TYPE: PER CELL SITE: 1 OBJECT: DISTRIB CELL# MODE BIN# MIN MAX ----------------------------------- -------- ---- ---------- ----------- 543 21 61698 (f10h) 34776 (87d8h) ENABLED 0 1 2 3 4 5 6 7 8 9 0 2 4 6 8 10 12 14 16 214174833 1 3 5 7 9 11 13 15 147174832 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 TYPE: PER CELL SITE: 1 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: 4-20 GMR-01 68P02901W23-P 23 Feb 2004 Technical Description BSS Command Reference disp_stat_prop disp_stat_prop out_ho_cause_atmpt cell_number= 1 5 4 3 2 1 61698 34776 Where: is: out_ho_cause_atmpt meas_type 5 4 3 2 1 61698 34776 cell_desc System response STATISTIC: OUT_HO_CAUSE_ATMPT TYPE: PER CELL 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 SITE: 1 OBJECT: COUNTER References Related commands "disp_element" on page 2-231, "stat_mode" on page 4-28, "disp_enable_stat" on page 4-11, "disp_interval" on page 4-15, "disp_stats" on page 4-22. 68P02901W23-P 23 Feb 2004 4-21 GMR-01 disp_stats Chapter 4: Statistics commands disp_stats Description The disp_stats command displays statistics associated with an individual cell or board for a valid interval. Security level 1 Supported by OMC-R GUI No Command type A (no operator actions) Prerequisites This command is not allowed while in SYSGEN ON mode. The GPRS feature must be unrestricted to display PCU statistics. {23658} The EGPRS feature must be unrestricted to display EGPRS associated statistics. 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 Specifies the name of the statistic. 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. The format for the GSM Cell ID depends on: • The system used (PGSM, EGSM, DCS1800, PCS1900 or GSM850). 4-22 GMR-01 68P02901W23-P 23 Feb 2004 Technical Description BSS Command Reference • disp_stats Whether the seven parameter GSM Cell ID format or the four parameter GSM Cell ID format has been enabled. The name of the cell created using the cell_name command may be entered in place of the cell_number. When the cell name is entered, it must be placed inside double quotation marks and 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. 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 out_ho_cause_atmpt meas_type 5 4 3 2 1 61986 34944 cell_desc The example below shows the same cell number in four parameter format: disp_cell_status 543 21 61986 34944 System response SITE: 0 CELL #: LAC = f222h CI = 8880h MEAS_TYPE : OUT_HO_CAUSE_ATMPT Total: 110 Uplink Quality Uplink Level Downlink Quality Downlink Level Distance Uplink Interference Downlink Interference Power Budget 68P02901W23-P 23 Feb 2004 : : : : : : : : 10 20 10 10 10 10 10 10 4-23 GMR-01 disp_stats Chapter 4: Statistics commands Congestion Adjacent Channel Interference Band Re-assignment : 10 : 10 : 0 Example 2 {23658} The following example displays the EGPRS_64K_NOT_AVAIL counter statistic that requires a cell_desc: disp_stats 1 egprs_64k_not_avail cell_number= 5 4 3 2 1 61986 34944 Where: is: 1 interval egprs_64k_not_avail meas_type 5 4 3 2 1 61986 34944 cell_desc System response SITE: 1 CELL #: LAC = f222h CI = 8880h MEAS_TYPE : EGPRS_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 SITE: 0 CELL #: LAC = f222h CI = 8880h MEAS_TYPE : BUSY_TCH Distribution Mean : 0 Distribution Max : 1 Distribution Min : 0 Bin : 82260 217730 0 0 0 0 0 0 0 0 Example 4 The following example displays the AVAILABLE_TCH gauge statistic that requires a cell_desc: 4-24 GMR-01 68P02901W23-P 23 Feb 2004 Technical Description BSS Command Reference disp_stats disp_stats 4 available_tch cell_number= 5 4 3 2 1 61986 34944 Where: is: 4 interval available_tch meas_type 5 4 3 2 1 61986 34944 cell_desc System response SITE: 0 CELL #: LAC = f222h MEAS_TYPE : AVAILABLE_TCH Gauge Value : 5 Max. : 5 CI = 8880h 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 RTF ID: 1 1 CI = 0006h SITE:1 CELL #:LAC = 0001h CI = 0006h TIMESLOT: 1 RTF ID = 1 1 MEAS_TYPE : BER Distribution Mean : 0 Distribution Max : 0 Distribution Min : 0 Bin : 0 0 0 0 0 0 0 0 0 0 SITE:1 CELL #:LAC = 0001h CI = 0006h TIMESLOT: 5 RTF ID = 1 1 MEAS_TYPE : BER Distribution Mean : 0 Distribution Max : 0 Distribution Min : 0 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: 68P02901W23-P 23 Feb 2004 4-25 GMR-01 disp_stats Chapter 4: Statistics commands 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 DCS1800 only PCS1900 only PGSM and EGSM PGSM and DCS1800 PGSM, EGSM, and DCS1800 PGSM and PCS1900 PGSM, EGSM, and PCS1900 : : : : : : : : 0 0 0 0 0 0 0 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_channels_switched meas_type 1234567 cell_desc System response SITE : 5 CELL #: LAC = 6 CI = 7 MEAS_TYPE : GPRS_32K_CHANNELS_SWITCHED GPRS_CHANNELS_SWITCHED: 13 Example 8 {4040} Displaying statistics for PRP_LOAD also displays the statistics information from the two other PCUs equipped at the BSC: 4-26 GMR-01 68P02901W23-P 23 Feb 2004 Technical Description BSS Command Reference disp_stats disp_stats 3 prp_load Where: is: 3 interval prp_load meas_type System response PCU : 0 DPROC Board # : 4356 MEAS_TYPE : PRP_LOAD Distribution Mean : 0 Distribution Max : 0 Distribution Min : 0 Bin : 0 0 0 0 0 0 0 0 0 0 (ox1104) PCU : 1 DPROC Board # : 4356 MEAS_TYPE : PRP_LOAD Distribution Mean : 0 Distribution Max : 0 Distribution Min : 0 Bin : 0 0 0 0 0 0 0 0 0 0 (ox1104) PCU : 2 DPROC Board # : 4356 MEAS_TYPE : PRP_LOAD Distribution Mean : 0 Distribution Max : 0 Distribution Min : 0 Bin : 0 0 0 0 0 0 0 0 0 0 (ox1104) References Related commands "disp_element" on page 2-231, "stat_mode" on page 4-28, "disp_enable_stat" on page 4-11, "disp_interval" on page 4-15. 68P02901W23-P 23 Feb 2004 4-27 GMR-01 stat_mode Chapter 4: Statistics commands stat_mode Description The stat_mode command enables or disables individual statistics in the CM database. The statistical applications of the stat_mode command permit multiple interactions with the same database element to define the statistical data. This permits flexibility in the definition of the parameters. 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 Supported by OMC-R GUI Yes Command type A (no operator actions) Prerequisites {23658} The GPRS feature must be unrestricted to enable GPRS associated statistics. The EGPRS feature must be unrestricted to enable EGPRS associated statistics. Enter this command at the BSC only. This command does not work at a BTS site. Contact the OMC-R for help. Format Syntax stat_mode <meas_type> <mode> [<location>] [<cell_desc>] stat_mode <meas_type> <mode> all stat_mode <meas_type> <mode> <location> all 4-28 GMR-01 68P02901W23-P 23 Feb 2004 Technical Description BSS Command Reference stat_mode Input parameters meas_type Specifies the name of the statistic. mode Specifies the mode of the statistic: on Enable off Disable location Specifies the site location: 0 or bsc BSC 1 to 120 BTS all All sites cell_desc The GSM Cell ID of the cell to be modified, preceded by cell_number=. The format for the GSM Cell ID depends on: • The system used (PGSM, EGSM, DCS1800, PCS1900). • Whether the seven parameter GSM Cell ID format or the four parameter GSM Cell ID format has been enabled. The name of the cell created using the cell_name command may be entered in place of the cell_number. When the cell name is entered, it must be placed inside double quotation marks and 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. 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 enables the TOTAL_CALLS statistic for cell number 5 4 3 2 1 61698 34776 at site 1: 68P02901W23-P 23 Feb 2004 4-29 GMR-01 stat_mode Chapter 4: Statistics commands stat_mode total_calls on 1 cell_number= 5 4 3 2 1 61698 34776 Where: is: total_calls meas_type 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: total_calls meas_type off set the enable type 1 location all all cells at the specified site 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 on set the enable type 1 location 1234567 cell_desc System response COMMAND ACCEPTED Example 4 {23658} 4-30 GMR-01 68P02901W23-P 23 Feb 2004 Technical Description BSS Command Reference stat_mode This example attempts to enable the EGPRS_DL_ASGN_PCCCH statistic for the cell at site 1 when EGPRS is restricted: 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 on set the enable 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-231, "disp_enable_stat" on page 4-11, "disp_interval" on page 4-15, "disp_stats" on page 4-22. 68P02901W23-P 23 Feb 2004 4-31 GMR-01 stat_mode Chapter 4: Statistics commands This page intentionally left blank. 4-32 GMR-01 68P02901W23-P 23 Feb 2004 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-P 23 Feb 2004 5-1 GMR-01 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 GMR-01 68P02901W23-P 23 Feb 2004 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-P 23 Feb 2004 5-3 GMR-01 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 GMR-01 68P02901W23-P 23 Feb 2004 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) Supported by OMC-R GUI Yes Cell description required No Dependencies The ECERM feature must be unrestricted. Two successful calls are required to clear an alarm within this threshold. (One call 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-P 23 Feb 2004 5-5 GMR-01 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). Type A (no operator actions) Supported by OMC-R GUI Yes Cell description required No Dependencies The ECERM feature must be unrestricted. This parameter can be set only at a BSC. If the threshold is reduced during operation, any existing counts between the new and the old threshold does not cause an alarm. (aci_error_gen_thresh - aci_error_clr_thresh) >= 2. Syntax Change command string chg_element aci_error_gen_thresh <value> 0 Display command string disp_element aci_error_gen_thresh 0 Values Value type Integer Valid range 2 to 255 Default value 6 5-6 GMR-01 68P02901W23-P 23 Feb 2004 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. Type A (no operator actions) Supported by OMC-R GUI Yes Cell description required No Dependencies The ECERM feature must be unrestricted. This parameter applies only to the BSC. Syntax Change command string chg_element aci_error_inc <value> 0 Display command string disp_element aci_error_inc 0 Values Value type Integer Valid range 0 ACI alarms not raised 1 to 255 ACI alarms raised 0 If ECERM feature is restricted 1 If ECERM feature is not restricted Default value 68P02901W23-P 23 Feb 2004 5-7 GMR-01 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. Type A (no operator actions) Supported by OMC-R GUI Yes Cell description required Yes Dependencies None Syntax Change command strings chg_element adap_ho_alt_trigger_rxqual <value> <location> <cell_desc> chg_cell_element adap_ho_alt_trigger_rxqual <value> <cell_desc> Display command strings disp_cell <cell_desc> ["full"] disp_element adap_ho_alt_trigger_rxqual <location> <cell_desc> Values Value type Boolean Valid range 0 or 1 Default value 0 Do not use hopping specific thresholds. 1 Use hopping specific thresholds. 0 5-8 GMR-01 68P02901W23-P 23 Feb 2004 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. Type A (no operator actions) Supported by OMC-R GUI Yes Cell description required Yes Dependencies None Syntax Change command strings chg_element adap_ho_pbgt <value> <location> <cell_desc> chg_cell_element adap_ho_pbgt <value> <cell_desc> Display command strings disp_cell <cell_desc> ["full"] disp_element adap_ho_pbgt <location> <cell_desc> Values Value type Integer Valid range 0 to 2 68P02901W23-P 23 Feb 2004 0 Disables adaptive power budget handovers at the location. 1 Enables adaptive power budget handovers at the location using per cell cumulative area. 5-9 GMR-01 adap_ho_pbgt Chapter 5: CM database parameters 2 Default value Enables adaptive power budget handovers at the location using per neighbor cumulative area. 0 5-10 GMR-01 68P02901W23-P 23 Feb 2004 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. Type A (no operator actions) Supported by OMC-R GUI Yes Cell description required Yes Dependencies None Syntax Change command strings chg_element adap_ho_rxlev <value> <location> <cell_desc> chg_cell_element adap_ho_rxlev <value> <cell_desc> Display command strings disp_cell <cell_desc> ["full"] disp_element adap_ho_rxlev <location> <cell_desc> Values Value type Boolean Valid range 0 or 1 Default value 68P02901W23-P 23 Feb 2004 0 Disables adaptive receive level handovers at the location. 1 Enables adaptive receive level handovers at the location. 0 5-11 GMR-01 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. Type A (no operator actions) Supported by OMC-R GUI Yes Cell description required Yes Dependencies None Syntax Change command strings chg_element adap_ho_rxqual <value> <location> <cell_desc> chg_cell_element adap_ho_rxqual <value> <cell_desc> Display command strings disp_cell <cell_desc> ["full"] disp_element adap_ho_rxqual <location> <cell_desc> Values Value type Boolean Valid range 0 or 1 Default value 0 Disables adaptive quality handovers at the location. 1 Enables adaptive quality handovers at the location. 0 5-12 GMR-01 68P02901W23-P 23 Feb 2004 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. Type A (no operator actions) Supported by OMC-R GUI Yes Cell description required Yes Dependencies None Syntax Change command strings chg_element adap_trigger_hop_rxqual_dl <value> <location> <cell_desc> chg_cell_element adap_trigger_hop_rxqual_dl <value> <cell_desc> Display command strings disp_cell <cell_desc> ["full"] disp_element adap_trigger_hop_rxqual_dl <location> <cell_desc> Values Value type Integer Valid range 0 to 65535 Default value 0 68P02901W23-P 23 Feb 2004 5-13 GMR-01 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. Type A (no operator actions) Supported by OMC-R GUI Yes Cell description required Yes Dependencies None Syntax Change command strings chg_element adap_trigger_hop_rxqual_ul <value> <location> <cell_desc> chg_cell_element adap_trigger_hop_rxqual_ul <value> <cell_desc> Display command strings disp_cell <cell_desc> ["full"] disp_element adap_trigger_hop_rxqual_ul <location> <cell_desc> Values Value type Integer Valid range 0 to 65535 Default value 0 5-14 GMR-01 68P02901W23-P 23 Feb 2004 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. Type A (no operator actions) Supported by OMC-R GUI Yes Cell description required Yes Dependencies None Syntax Change command strings chg_element adap_trigger_pbgt <value> <location> <cell_desc> chg_cell_element adap_trigger_pbgt <value> <cell_desc> Display command strings disp_cell <cell_desc> ["full"] disp_element adap_trigger_pbgt <location> <cell_desc> Values Value type Integer Valid range 0 to 255 Default value 0 68P02901W23-P 23 Feb 2004 5-15 GMR-01 . the system triggers a handover to a better cell. When the threshold set by adap_trigger_pbgt is exceeded. the system triggers a handover to a better cell. Syntax Change command string modify_neighbor <src_cell_id> <neighbor_cell_id> adap_trigger_pbgt_nbr <value> Display command string disp_neighbor <src_cell_id> [<neighbor_cell_id>|all] Values Value type Integer Valid range 0 to 255 Default value 40 (the value of 40 corresponds to a hreqave of 8 and a handover margin of 5) 5-16 GMR-01 68P02901W23-P 23 Feb 2004 .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. Type A (no operator actions) Supported by OMC-R GUI Yes Cell description required No Dependencies This parameter is invalid when ba_type is ba_bcch or ba_gprs. the system performs a downlink strength handover. When the threshold set by this parameter is exceeded.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. Type A (no operator actions) Supported by OMC-R GUI Yes Cell description required Yes Dependencies None Syntax Change command strings chg_element adap_trigger_rxlev_dl <value> <location> <cell_desc> chg_cell_element adap_trigger_rxlev_dl <value> <cell_desc> Display command strings disp_cell <cell_desc> ["full"] disp_element adap_trigger_rxlev_dl <location> <cell_desc> Values Value type Integer Valid range 0 to 255 Default value 0 68P02901W23-P 23 Feb 2004 5-17 GMR-01 . the system performs an uplink strength handover.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. Type A (no operator actions) Supported by OMC-R GUI Yes Cell description required Yes Dependencies None Syntax Change command strings chg_element adap_trigger_rxlev_ul <value> <location> <cell_desc> chg_cell_element adap_trigger_rxlev_ul <value> <cell_desc> Display command strings disp_cell <cell_desc> ["full"] disp_element adap_trigger_rxlev_ul <location> <cell_desc> Values Value type Integer Valid range 0 to 255 Default value 0 5-18 GMR-01 68P02901W23-P 23 Feb 2004 . When the threshold set by this parameter is exceeded. the system performs a downlink quality handover. When the threshold set by this parameter is exceeded. Type A (no operator actions) Supported by OMC-R GUI Yes Cell description required Yes Dependencies None Syntax Change command strings chg_element adap_trigger_rxqual_dl <value> <location> <cell_desc> chg_cell_element adap_trigger_rxqual_dl <value> <cell_desc> Display command strings disp_cell <cell_desc> ["full"] disp_element adap_trigger_rxqual_dl <location> <cell_desc> Values Value type Integer Valid range 0 to 65535 Default value 0 68P02901W23-P 23 Feb 2004 5-19 GMR-01 .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. 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. Type A (no operator actions) Supported by OMC-R GUI Yes Cell description required Yes Dependencies None Syntax Change command strings chg_element adap_trigger_rxqual_ul <value> <location> <cell_desc> chg_cell_element adap_trigger_rxqual_ul <value> <cell_desc> Display command strings disp_cell <cell_desc> ["full"] disp_element adap_trigger_rxqual_ul <location> <cell_desc> Values Value type Integer Valid range 0 to 65535 Default value 0 5-20 GMR-01 68P02901W23-P 23 Feb 2004 . the system performs an uplink quality handover. When the threshold set by this parameter is exceeded. 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).Technical Description BSS Command Reference allow_8k_trau allow_8k_trau {4415} Description The allow_8k_trau parameter enables or disables 8 kbit/s backhaul. For a TCU-A or TCU-B radio platform. the TCU-A/TCU-B feature must be unrestricted. Syntax Change command string equip <site_id> RTF After entering this command. Type A (no operator actions) Supported by OMC-R GUI Yes Cell description required No Dependencies The AMR Enhanced Capability feature must be unrestricted. The amr_half_rate_enabled parameter must be enabled. Display command string disp_equipment 68P02901W23-P 23 Feb 2004 5-21 GMR-01 .95 kbit/s codec mode must not be part of the AMR Half-Rate Active Codec Set. A timeslot or smaller portions within a timeslot may represent a port on the switch. The BTS must be capable of AMR. otherwise. 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 user is prompted to enable or disable the allow_8k_trau parameter (and other RTF parameters). A port on the KSW can be a minimum of two bits that equates to four independent 16 kbit/s portions within each timeslot. only CTU supports AMR. The 7. allow_8k_trau Chapter 5: CM database parameters Values Value type Boolean Valid range no or yes Default value no Disabled yes Enabled yes 5-22 GMR-01 68P02901W23-P 23 Feb 2004 . additional prompts are presented for the dependent parameters. and default values for the dependent parameters. Table 5-1 lists the range of values and defaults for the dependent parameters if a value of 0 is entered for the alt_qual_proc parameter. Default values may be entered by pressing return at the prompt. The command is abandoned if an invalid value is entered. 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 for a cell may be changed using the chg_cell_element command. 68P02901W23-P 23 Feb 2004 5-23 GMR-01 . When the chg_cell_element command is used to change the value of the alt_qual_proc parameter. The value that is entered for the alt_qual_proc parameter determines the type of values. range of values.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 alt_qual_proc parameter value is initially assigned using the add_cell command. 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 Table 5-2 lists the range of values and defaults for the dependent parameters if a value of 1 is entered for the alt_qual_proc parameter. the range of values. 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. and the default values for the dependent parameters.alt_qual_proc Chapter 5: CM database parameters Table 5-2 alt_qual_proc=1 parameter values Dependent parameter Range Default l_rxqual_ul_p 0 to 7 4 l_rxqual_dl_p 0 to 7 4 u_rxqual_ul_p 0 to 7 1 u_rxqual_dl_p 0 to 7 1 l_rxqual_ul_h 0 to 7 5 l_rxqual_dl_h 0 to 7 5 l_rxqual_dl_h_hopping 0 to 7 4 l_rxqual_ul_h_hopping 0 to 7 4 l_rxqual_dl_p_hopping 0 to 7 4 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 Type B (operator actions required) Supported by OMC-R GUI Yes Cell numbers required Yes Dependencies The value that is entered for the alt_qual_proc parameter determines the type of values. Syntax Change command strings add_cell <gsm_cell_id> <location> chg_cell_element alt_qual_proc <value> <cell_desc> Display command strings disp_cell <cell_desc> ["full"] disp_element alt_qual_proc <location> <cell_desc> 5-24 GMR-01 68P02901W23-P 23 Feb 2004 . Technical Description BSS Command Reference alt_qual_proc Values Value type Boolean Valid range 0 or 1 Default value 68P02901W23-P 23 Feb 2004 0 BER Units 1 Qband units 0 5-25 GMR-01 . Syntax Add/Change command strings chg_element amr_bss_full_rate_enabled <value> 0 Display command strings disp_element amr_bss_full_rate_enabled 0 Values Value type Boolean Valid range 0 or 1 Default value 0 Disabled 1 Enabled 0 5-26 GMR-01 68P02901W23-P 23 Feb 2004 . at least one AXCDR must have CIC validation enabled. This parameter applies only to the BSC. The handover_required_sp_ver_used parameter must be enabled. In the case of remote transcoding.amr_bss_full_rate_enabled Chapter 5: CM database parameters amr_bss_full_rate_enabled {4322} Description The amr_bss_full_rate_enabled parameter enables or disables the Adaptive Multi-Rate (AMR) Full Rate at the BSS. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required No Dependencies The AMR feature must be unrestricted. In the case of remote transcoding. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required Yes Dependencies The AMR feature must be unrestricted.Technical Description BSS Command Reference amr_bss_half_rate_enabled amr_bss_half_rate_enabled {4322} Description The amr_bss_half_rate_enabled parameter enables or disables the Adaptive Multi-Rate (AMR) Half Rate at the BSS. at least one AXCDR must have CIC validation enabled. This parameter applies only to the BSC. The handover_required_sp_ver_used parameter must be enabled. Syntax Add/Change command strings chg_element amr_bss_half_rate_enabled <value> 0 Display command strings disp_element amr_bss_half_rate_enabled 0 Values Value type Boolean Valid range 0 or 1 Default value 68P02901W23-P 23 Feb 2004 0 Disabled 1 Enabled 0 5-27 GMR-01 . When the parameter is set to a value greater than the inherent delay in the adaptation process. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required Yes Dependencies The AMR feature must be unrestricted. Syntax Add/Change command strings chg_element amr_dl_la_mode_chg_min <value> <location> <cell_desc> Display command strings disp_element amr_dl_la_mode_chg_min <location> <cell_desc> Values Value type Integer (ms) Valid range 0 to 255 Default value 100 5-28 GMR-01 68P02901W23-P 23 Feb 2004 .amr_dl_la_mode_chg_min Chapter 5: CM database parameters amr_dl_la_mode_chg_min {4322} Description The amr_dl_la_mode_chg_min parameter specifies the minimum time periods between initiating changes in the downlink codec mode. a wait period is added to slow down the adaptation. Syntax Add/Change command strings chg_element amr_dl_thresh_adjust <value> <location> Display command strings disp_element amr_dl_thresh_adjust <location> Values Value type dB Valid range 1 to 7 Default value 3 68P02901W23-P 23 Feb 2004 5-29 GMR-01 .Technical Description BSS Command Reference amr_dl_thresh_adjust amr_dl_thresh_adjust {4322} Description The amr_dl_thresh_adjust parameter specifies the compensation for the Carrier to Interference (C/I) adaptation thresholds. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required Yes Dependencies The AMR feature must be unrestricted. This covers both initial setup and handover.amr_force_hr_usage Chapter 5: CM database parameters amr_force_hr_usage {4322} Description The amr_force_hr_usage parameter enables or disables the capacity to override MSC provided preference and force AMR Half Rate usage for all AMR Half Rate capable calls within a BSS. Syntax Add/Change command string chg_element amr_force_hr_usage <value> <location> Display command string disp_element amr_force_hr_usage <location> Values Value type Boolean Valid range 0 or 1 Default value 0 Disabled 1 Enabled 0 5-30 GMR-01 68P02901W23-P 23 Feb 2004 . Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required Yes Dependencies The AMR feature must be unrestricted. Technical Description BSS Command Reference amr_fr_dl_la_enabled amr_fr_dl_la_enabled {4322} Description The amr_fr_dl_la_enabled parameter enables or disables Full Rate Downlink Codec Mode Adaptation on a per cell basis. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required Yes Dependencies The AMR feature must be unrestricted. Syntax Add/Change command strings chg_element amr_fr_dl_la_enabled <value> <location> <cell_desc> chg_cell_element amr_fr_dl_la_enabled <value> <cell_desc> Display command strings disp_cell <cell_desc> "full" disp_element amr_fr_dl_la_enabled <location> <cell_desc> Values Value type Boolean Valid range 0 or 1 Default value 68P02901W23-P 23 Feb 2004 0 Disabled 1 Enabled 1 5-31 GMR-01 . Syntax Add/Change command strings chg_element amr_fr_ul_la_enabled <value> <location> <cell_desc> chg_cell_element amr_fr_ul_la_enabled <value> <cell_desc> Display command strings disp_cell <cell_desc> "full" disp_element amr_fr_ul_la_enabled <location> <cell_desc> Values Value type Boolean Valid range 0 or 1 Default value 0 Disabled 1 Enabled 1 5-32 GMR-01 68P02901W23-P 23 Feb 2004 . Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required Yes Dependencies The AMR feature must be unrestricted.amr_fr_ul_la_enabled Chapter 5: CM database parameters amr_fr_ul_la_enabled {4322} Description The amr_fr_ul_la_enabled parameter enables or disables Full Rate Uplink Codec Mode Adaptation on a per cell basis. Technical Description BSS Command Reference amr_full_rate_enabled amr_full_rate_enabled {4322} Description The amr_full_rate_enabled parameter enables or disables the AMR Full Rate at a cell. Syntax Change command strings 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. a site without a colocated BTS). This parameter does not apply to a standalone BSC site (that is. This parameter does not apply to a remote transcorder (RXCDR). Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required Yes Dependencies The AMR feature must be unrestricted. Display command strings disp_cell <cell_desc> ["full"] disp_element amr_full_rate_enabled <location> <cell_desc> 68P02901W23-P 23 Feb 2004 5-33 GMR-01 . Values Value type Boolean Valid range 0 or 1 Default value 0 Disabled 1 Enabled 0 5-34 GMR-01 68P02901W23-P 23 Feb 2004 .amr_full_rate_enabled Chapter 5: CM database parameters The copy_cell command sets this parameter to disabled. Syntax Add/Change command strings chg_element amr_half_rate_enabled <value> <location> <cell_desc> chg_cell_element amr_half_rate_enabled <value> <cell_desc> Display command strings disp_element amr_half_rate_enabled <location> <cell_desc> disp_cell <cell_desc> full disp_equipment <location> rtf <rtf_id1> <rtf_id2> 68P02901W23-P 23 Feb 2004 5-35 GMR-01 . Only the amr_half_rate_enabled cell element parameter can be modified using the chg_element or chg_cell_element command. This RTF parameter cannot be set for a sub-equipped RTF. {4415} The amr_half_rate_enabled cell and RTF parameter can be modified at an M-Cell2/6 site only if the TCU-A/TCU-B optional features are unrestricted. The amr_half_rate_enabled RTF parameter can only be modified by unequipping and re-equipping the RTF. The RTF parameter is displayed using the disp_equipment command.Technical Description BSS Command Reference amr_half_rate_enabled amr_half_rate_enabled {4322} Description The amr_half_rate_enabled parameter enables or disables the AMR Half Rate at a cell or RTF. and displayed with the disp_cell full command. The amr_half_rate_enabled RTF parameter is only prompted for during the equipage of an RTF. The amr_half_rate_enabled parameter can only be modified or set at a BTS site comprised solely of M-Cell2/6 or Horizonmacro cabinets or a mixture of both. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required Yes Dependencies The AMR feature must be unrestricted. amr_half_rate_enabled Chapter 5: CM database parameters The copy_cell command sets the cell element parameter to disabled. Values Value type Boolean Valid range 0 or 1 Default value 0 Disabled 1 Enabled 0 5-36 GMR-01 68P02901W23-P 23 Feb 2004 . Syntax Add/Change command strings chg_element amr_hop_count <value> <location> <cell_desc> chg_cell_element amr_hop_count <value> <cell_desc> Display command strings disp_cell <cell_desc> "full" disp_element amr_hop_count <location> <cell_desc> Values Value type Integer Valid range 0 to 255 Default value 1 68P02901W23-P 23 Feb 2004 5-37 GMR-01 . Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required Yes Dependencies The AMR feature must be unrestricted.Technical Description BSS Command Reference amr_hop_count amr_hop_count {4322} Description The amr_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. The value of this parameter must not exceed the value of hop_count. Syntax Add/Change command strings chg_element amr_hr_dl_la_enabled <value> <location> <cell_desc> chg_cell_element amr_hr_dl_la_enabled <value> <cell_desc> Display command strings disp_cell <cell_desc> "full" disp_element amr_hr_dl_la_enabled <location> <cell_desc> Values Value type Boolean Valid range 0 or 1 Default value 0 Disabled 1 Enabled 1 5-38 GMR-01 68P02901W23-P 23 Feb 2004 .amr_hr_dl_la_enabled Chapter 5: CM database parameters amr_hr_dl_la_enabled {4322} Description The amr_hr_dl_la_enabled parameter enables or disables Half Rate Downlink Codec Mode Adaptation on a per cell basis. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required Yes Dependencies The AMR feature must be unrestricted. Technical Description BSS Command Reference amr_hr_ul_la_enabled amr_hr_ul_la_enabled {4322} Description The amr_hr_ul_la_enabled parameter enables or disables Half Rate Uplink Codec Mode Adaptation on a per cell basis. Syntax Add/Change command strings chg_element amr_hr_ul_la_enabled <value> <location> <cell_desc> chg_cell_element amr_hr_ul_la_enabled <value> <cell_desc> Display command strings disp_cell <cell_desc> "full" disp_element amr_hr_ul_la_enabled <location> <cell_desc> Values Value type Boolean Valid range 0 or 1 Default value 68P02901W23-P 23 Feb 2004 0 Disabled 1 Enabled 1 5-39 GMR-01 . Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required Yes Dependencies The AMR feature must be unrestricted. 1 Half-rate intra-cell quality handovers are disabled. 2 Half-rate intra-cell quality handovers are enabled.amr_hr_intracell_ho_allowed Chapter 5: CM database parameters amr_hr_intracell_ho_allowed {4322} Description The amr_hr_intracell_ho_allowed parameter enables or disables the support for Intra-Cell quality handovers for half-rate channels within a cell. Full-rate only is allowed. 5-40 GMR-01 68P02901W23-P 23 Feb 2004 . Handover Required is not sent to MSC. Syntax Add/Change command strings chg_element amr_hr_intracell_ho_allowed <value> <location> <cell_desc> chg_cell_element amr_hr_intracell_ho_allowed <value> <cell_desc> Display command strings disp_cell <cell_desc> "full" disp_element amr_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. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required Yes Dependencies The AMR feature must be unrestricted. Handover Required is sent to MSC. 3 5-41 GMR-01 . Half-rate and Full-rate are allowed.Technical Description BSS Command Reference amr_hr_intracell_ho_allowed 3 Default value 68P02901W23-P 23 Feb 2004 Half-rate intra-cell quality handovers are enabled. amr_hr_res_ts Chapter 5: CM database parameters amr_hr_res_ts {4322} Description The amr_hr_res_ts parameter specifies the maximum number of half-rate capable timeslots to be reserved within each zone of the cell. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required Yes Dependencies The AMR feature must be unrestricted. Syntax Add/Change command strings chg_element amr_hr_res_ts <value> <location> <cell_desc> chg_cell_element amr_hr_res_ts <value> <cell_desc> Display command strings disp_cell <cell_desc> "full" disp_element amr_hr_res_ts <location> <cell_desc> Values Value type Integer Valid range 0 to 255 Default value 2 5-42 GMR-01 68P02901W23-P 23 Feb 2004 . Technical Description BSS Command Reference amr_inner_hr_usage_thres amr_inner_hr_usage_thres {4322} Description The amr_inner_hr_usage_thres parameter specifies the congestion threshold for the following: (a) reconfiguration of half-rate capable full rate calls to AMR half-rate calls to the inner zone. (b) the assignment of new calls on half-rate channels establishing in the inner zone. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required Yes Dependencies The AMR feature must be unrestricted. Syntax Add/Change command strings chg_element amr_inner_hr_usage_thres <value> <location> <cell_desc> chg_cell_element amr_inner_hr_usage_thres <value> <cell_desc> Display command strings disp_cell <cell_desc> "full" disp_element amr_inner_hr_usage_thres <location> <cell_desc> Values Value type Integer Valid range 0 to 101 Default value 101 68P02901W23-P 23 Feb 2004 5-43 GMR-01 . Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required No Dependencies The AMR feature must be unrestricted.amr_ms_high_cmr Chapter 5: CM database parameters amr_ms_high_cmr {4322} 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> Display command string disp_element amr_ms_high_cmr <location> Values Value type Percentages Valid range 50 to 100 Default value 95 5-44 GMR-01 68P02901W23-P 23 Feb 2004 . Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required No Dependencies The AMR feature must be unrestricted.Technical Description BSS Command Reference amr_ms_high_rxqual amr_ms_high_rxqual {4322} Description The amr_ms_high_rxqual parameter specifies the threshold for monitoring AMR MSs continually requesting the highest codec mode at a BSS.5% BER or RXQUAL 4) 68P02901W23-P 23 Feb 2004 5-45 GMR-01 . Syntax Add/Change command strings chg_element amr_ms_high_rxqual <value> <location> Display command strings disp_element amr_ms_high_rxqual <location> Values Value type QBand units Valid range 0 to 7 Default value 4 (2. amr_ms_low_cmr Chapter 5: CM database parameters amr_ms_low_cmr {4322} Description The amr_ms_high_cmr parameter specifies the percentages for monitoring AMR MSs continually requesting the lowest codec mode at a BSS. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required No Dependencies The AMR feature must be unrestricted. Syntax Add/Change command strings chg_element amr_ms_low_cmr <value> <location> Display command strings disp_element amr_ms_low_cmr <location> Values Value type Percentages Valid range 50 to 100 Default value 99 5-46 GMR-01 68P02901W23-P 23 Feb 2004 . Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required No Dependencies The AMR feature must be unrestricted.Technical Description BSS Command Reference amr_ms_low_rxqual amr_ms_low_rxqual {4322} Description The amr_ms_high_rxqual parameter specifies the threshold for monitoring MSs continually requesting the lowest mode at a BSS.5% BER or RXQUAL 2 5-47 GMR-01 . Syntax Add/Change command strings chg_element amr_ms_low_rxqual <value> <location> Display command strings disp_element amr_ms_low_rxqual <location> Values Value type QBand units Valid range 0 to 7 Default value 2 68P02901W23-P 23 Feb 2004 0. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required No Dependencies The AMR feature must be unrestricted. Syntax Add/Change command strings chg_element amr_ms_monitor_period <value> <location> Display command strings disp_element amr_ms_monitor_period <location> Values Value type SACCH periods Valid range 10 to 1200 Default value 40 Disable parameter 5-48 GMR-01 68P02901W23-P 23 Feb 2004 .amr_ms_monitor_period Chapter 5: CM database parameters amr_ms_monitor_period {4322} Description The amr_ms_monitor_period parameter is used for detecting MSs continually requesting the highest or lowest modes at a BSS. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required Yes Dependencies The AMR feature must be unrestricted. A limitation exists based on the number of idle half-rate channels and free generic traffic channels in the cell. Syntax Add/Change command strings chg_element amr_new_calls_hr <value> <location> <cell_desc> chg_cell_element amr_new_calls_hr <value> <cell_desc> Display command strings disp_cell <cell_desc> ["full"] disp_element amr_new_calls_hr <location> <cell_desc> Values Value type Percentage Valid range 0 to 101 Default value 101 68P02901W23-P 23 Feb 2004 101 disables this parameter 5-49 GMR-01 .Technical Description BSS Command Reference amr_new_calls_hr amr_new_calls_hr {4322} Description The amr_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 half-rate calls. Syntax Add/Change command strings chg_element amr_reconfig_fr_to_hr <value> <location> <cell_desc> chg_cell_element amr_reconfig_fr_to_hr <value> <cell_desc> Display command strings disp_cell <cell_desc> ["full"] disp_element amr_reconfig_fr_to_hr <location> <cell_desc> Values Value type Percentage Valid range 0 to 101 101 Default value disables this parameter 101 5-50 GMR-01 68P02901W23-P 23 Feb 2004 .amr_reconfig_fr_to_hr Chapter 5: CM database parameters amr_reconfig_fr_to_hr {4322} Description The amr_reconfig_fr_to_hr parameter specifies the congestion level threshold. then any existing “Half-Rate Capable" Full-Rate calls are reassigned to Half-Rate traffic channels. If this level is exceeded at the target cell. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required Yes Dependencies The AMR feature must be unrestricted. Idle half-rate channels and free generic traffic channels in the cell must be available. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required Yes Dependencies None Syntax Add/Change command strings add_cell <gsm_cell_id> <location> chg_element attach_detach <value> <location> <cell_desc> chg_cell_element attach_detach <value> <cell_desc> Display command strings disp_cell <cell_desc> ["full] disp_element attach_detach <location> <cell_desc> Values Value type Boolean Valid range 0 or 1 Default value 68P02901W23-P 23 Feb 2004 0 Disabled 1 Enabled 0 5-51 GMR-01 .Technical Description BSS Command Reference attach_detach attach_detach Description The attach_detach parameter enables and disables the mandatory International Mobile Subscriber Identity (IMSI) attach/detach for the MS. 4.08 .detach 4.allow IMSI Attach Detach 5-52 GMR-01 68P02901W23-P 23 Feb 2004 .1.3 .10.9.31 12.attach_detach Chapter 5: CM database parameters References GSM parameter ATT GSM technical specification 4.08 .8 config CCH .attach 4.8 4.4.3.5.8.2.08 .2.4 .5.08 .20 .4. 690 TMSI=00050603 0002h Yes * * * * * RSS Data: Time: 01/03/1980 08:04:33. a measurement report is sent to the MMI and is displayed in the same format as the output for the trace_call command. **** START OF RF LOSS REPORT **** * * * * * * * * * * * Sequence Number SCCP Number Scope Carrier Channel Trace Status Time Stamp Call Duration Mobile ID CIC Call Lost 0 0018c0h 001 01 1 (0001h) 1 (0001h) site=1 RTF 0 0 0e 00 0a RF Loss .Loss of uplink SACCH 01/03/1980 08:04:33. 68P02901W23-P 23 Feb 2004 5-53 GMR-01 . 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.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) Supported by OMC-R GUI Yes Cell numbers required Yes Dependencies The auto_rf_loss_trace parameter is valid for any GPROC except the CSFP. 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.Technical Description BSS Command Reference auto_rf_loss_trace auto_rf_loss_trace Description The auto_rf_loss_trace parameter enables and disables automatic RF Loss tracing for a cell.745 00:00:48. 22 5-54 GMR-01 68P02901W23-P 23 Feb 2004 . section 9.auto_rf_loss_trace Chapter 5: CM database parameters Syntax Change command strings chg_element auto_rf_loss_trace <value> <location> <cell_desc> chg_cell_element auto_rf_loss_trace <value> <cell_desc> Display command string disp_element auto_rf_loss_trace <location> <cell_desc> Values Value type Integer Valid range 0 to 2 Default value 0 Automatic RF loss tracing disabled for this cell 1 Automatic RF loss tracing enabled for this cell. RLM cause values are defined in TS GSM 08. send measurement reports to MMI and OMC-R 2 Automatic RF loss tracing enabled for this cell. send measurement reports to OMC-R only 0 References GSM parameter None GSM technical specification This is a Motorola parameter.3.58. Technical Description BSS Command Reference ba_alloc_proc ba_alloc_proc Description The ba_alloc_proc parameter enables and disables the reinitialization of the active block following a change in the broadcast control channel allocation (BA) and the suspension of subsequent measurements until the new BA is reported. Type A (no operator actions) Supported by OMC-R GUI Yes Cell description required Yes Dependencies None Syntax Add/Change command strings add_cell <gsm_cell_id> <location> chg_element ba_alloc_proc <value> <location> <cell_desc> chg_cell_element ba_alloc_proc <value> <cell_desc> Display command strings disp_cell <cell_desc> ["full"] disp_element ba_alloc_proc <location> <cell_desc> Values Value type Boolean Valid range 0 or 1 Default value 68P02901W23-P 23 Feb 2004 0 Reinitialization disabled 1 Reinitialization enabled 0 5-55 GMR-01 . ba_alloc_proc Chapter 5: CM database parameters References GSM parameter None GSM technical specification This is a Motorola parameter. 5-56 GMR-01 68P02901W23-P 23 Feb 2004 . 68P02901W23-P 23 Feb 2004 5-57 GMR-01 . Syntax Change command strings chg_element band_preference <value> <location> <cell_desc> chg_cell_element band_preference <value> <cell_desc> Display command string 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). This parameter has no meaning if band_preference_mode = 0 for this cell. Type A (No operator action) Supported by OMC-R GUI Yes Cell description required Yes Dependencies The Multiband Inter-cell handover feature must be enabled.Technical Description BSS Command Reference band_preference 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. 5-58 GMR-01 68P02901W23-P 23 Feb 2004 .band_preference Chapter 5: CM database parameters References GSM parameter None GSM technical specification This is a Motorola parameter. Type A (no operator actions) Supported by OMC-R GUI Yes Cell description required Yes Dependencies The Multiband Inter-cell handover feature must be unrestricted.Technical Description BSS Command Reference band_preference_mode 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. 5-59 GMR-01 . Syntax Change command strings chg_element band_preference_mode <value> <location> <cell_desc> chg_cell_element band_preference_mode <value> <cell_desc> Display command string disp_element band_preference_mode <location> <cell_desc> Values Value type Integer Valid range 0 to 60 68P02901W23-P 23 Feb 2004 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. the BSS enters a mode of continually monitoring for qualified preferred-band neighbours reported by the MS in order to hand over the MS. 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.band_preference_mode Chapter 5: CM database parameters 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. Handovers for normal radio resource reasons may occur during the monitoring mode. Mode 1 is restricted to mobiles that are fast enough to provide guilty measurement reports. 2. 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. The BSS will stay in this mode until it finds a neighbour TCH in the preferred band. and these handovers will be to the strongest preferred band neighbour reported by the MS. 4 The BSS continually attempts to hand a Multiband MS over to a preferred band TCH immediately after initial assignment. Handovers for normal radio resource reasons may occur during the monitoring mode. If this assignment is not possible. and these handovers will be to the strongest preferred band neighbour reported by the MS. The BSS always hands the MS over to the strongest MS-reported neighbour when a handover is required for normal radio resource reasons. 5 The BSS attempts to assign a Multiband MS to the strongest preferred-band neighbour reported by the MS at the time of SDCCH-to-TCH assignment. The BSS will stay in this mode until it finds a neighbour TCH in the preferred band for the current serving cell. 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. 3 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. The BSS will not attempt to allocate a TCH in the preferred band for this MS at the time of SDCCH-to-TCH assignment. and 4. This value combines the functions of values 1 and 2. This value combines the functions of values 1. 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. 5-60 GMR-01 68P02901W23-P 23 Feb 2004 . 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. 0 References GSM parameter None GSM technical specification This is a Motorola parameter. 68P02901W23-P 23 Feb 2004 5-61 GMR-01 . If this assignment is not possible. This type should be used in order to activate the multiband congestion threshold verification. except it is only triggered when the cell is congested. the BSS enters a mode of continually monitoring for qualified preferred-band neighbours reported by the MS in order to hand over the MS. This value functions identically to value 5. Handovers for normal radio resource reasons may occur during the monitoring mode.Technical Description BSS Command Reference band_preference_mode 6 Default value The BSS attempts to assign a Multiband MS to the strongest preferred band neighbour reported by the MS only after a cell has become congested. and these handovers will be to the strongest preferred band neighbour reported by the MS. The BSS will stay in this mode until it finds a neighbour TCH in the preferred band. ber_loss_daily Chapter 5: CM database parameters ber_loss_daily Description The ber_loss_daily parameter specifies the daily Bit Error Rate (BER) alarm threshold. 3 would be the exponent value of 103. For example. 5-62 GMR-01 68P02901W23-P 23 Feb 2004 . An alarm is generated if the BER exceeds this threshold in a given 24 hour period. This parameter represents the exponent of threshold BER. Type A (no operator actions) Supported by OMC-R GUI Yes Cell description required No Dependencies None Syntax Change command string chg_element ber_loss_daily <value> <location> Display command string disp_element ber_loss_daily <location> Values Value type Integer Valid range 3 to 6 Default value 5 References GSM parameter None GSM technical specification This is a Motorola parameter. indicating 1 bit error in 1000 bits. Technical Description BSS Command Reference ber_loss_hourly ber_loss_hourly Description The ber_loss_hourly parameter specifies the hourly Bit Error Rate (BER) alarm threshold. 3 would be the exponent value of 103. An alarm is generated if the BER exceeds this threshold in a given 60 minute period. This parameter represents the exponent of threshold BER. indicating 1 bit error in 1000 bits. Type A (no operator actions) Supported by OMC-R GUI Yes Cell description required No Dependencies None Syntax Change command string chg_element ber_loss_hourly <value> <location> <cell_desc> Display command string disp_element ber_loss_hourly <location> <cell_desc> Values Value type Integer Valid range 3 to 6 Default value 4 References GSM parameter None GSM technical specification This is a Motorola parameter. 68P02901W23-P 23 Feb 2004 5-63 GMR-01 . For example. the system applies the bounce_protect_margin value for the number of SACCH periods set by the bounce_protect_cong_tmr timer. specifies the level by which a target cell must exceed the serving cell. Syntax Change command strings chg_element bounce_protect_margin <value> <location> <cell_desc> chg_cell_element bounce_protect_margin <value> <cell_desc> Display command string disp_element bounce_protect_margin <location> <cell_desc> Values Value type Integer (decibels) Valid range 0 to 127 Default value 0 5-64 GMR-01 68P02901W23-P 23 Feb 2004 . Type A (no operator actions) Supported by OMC-R GUI Yes Cell description required Yes Dependencies After a RXQUAL handover.bounce_protect_margin Chapter 5: CM database parameters bounce_protect_margin Description The bounce_protect_margin parameter. This parameter prevents continuous handover bouncing between cells due to RXQUAL level and congestion reasons. in conjunction with the ho_margin_cell parameter. 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 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. Syntax Add/Change command strings add_cell <gsm_cell_id> <location> 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. 68P02901W23-P 23 Feb 2004 5-65 GMR-01 . PCH and AGCH share the same TDMA mapping when combined onto a basic physical channel. The number of blocks reserved starting with (and including) block 0 are broadcast in the BCCH. Channels are shared on a block by block basis.Technical Description BSS Command Reference bs_ag_blks_res bs_ag_blks_res Description The bs_ag_blks_res parameter specifies the number of blocks reserved for access grant per 51-multiframes. If no AGCH is reserved in a non-combined cell (bs_ag_blks_res = 0) and ccch_conf is other than 1). Resetting the site generates several alarms. Type B (operator actions required) Supported by OMC-R GUI Yes Cell description required Yes Dependencies ccch_conf Operator actions Reset the site after changing the bs_ag_blks_res value. However. these alarms are blocked by the system. enabling of CBCH is not permitted (cbch_enabled = 1). 20 .8 .21 4.2.3.2.5.27.2. and section 7 table 5 4.02 .5.6.10.08 . 10.8.14: page mode information element 12.bs_ag_blks_res Chapter 5: CM database parameters Display command strings disp_cell <cell_desc> ["full"] 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: Default value 0 to 2 blocks reserved for ccch_conf = 1 0 to 7 blocks reserved for ccch_conf 01 0 References GSM parameter BS_AG_BLKS_RES GSM technical specification 5.no of blocks for access grant message 5-66 GMR-01 68P02901W23-P 23 Feb 2004 .1.config CCH .08 . figure 10.2.5.5.8.3. and table 10. Display command strings disp_cell <cell_desc> ["full"] disp_element bs_pa_mfrms <location> <cell_desc> 68P02901W23-P 23 Feb 2004 5-67 GMR-01 . Syntax Add/Change command strings add_cell <gsm_cell_id> <location> chg_element bs_pa_mfrms <value> <location> <cell_desc> chg_cell_element bs_pa_mfrms <value> <cell_desc> A site reset is required when the value of bs_pa_mfrms is changed. Operator actions Reset the site after changing the bs_pa_mfrms. Type B (operator actions required) Supported by OMC-R GUI Yes Cell description required Yes Dependencies The value chosen for this field depends on the size of the location area and the ratio of mobile originated to mobile terminated calls. Although resetting the site generates several alarms.Technical Description BSS Command Reference bs_pa_mfrms bs_pa_mfrms Description The bs_pa_mfrms parameter specifies the number of multiframes between transmissions of paging messages to MSs of the same paging group. these alarms are blocked by the system. The number of paging blocks available (per CCCH) are those available (on a specific CCCH) multiplied by (bs_pa_mfrms). 0 1 2 3 4 5 6 7 2 multiframes 3 multiframes 4 multiframes 5 multiframes 6 multiframes 7 multiframes 8 multiframes 9 multiframes Default value 0 References GSM parameter BS_PA_MFRMS GSM technical specification 4.8.5: downlink signalling failure 12.configCCH 5-68 GMR-01 68P02901W23-P 23 Feb 2004 .8.6. 10.5.2.08 .10.2.6. fig.04 .7: table 5 5.27.20 .bs_pa_mfrms Chapter 5: CM database parameters Values Value type Integer (multiframes) Valid range 0 to 7 Represents the multiframes period for the transmission of PAGING REQUEST messages to the same paging group.8 .02 .5.02 .1 5.21 5. and table 10.5. Syntax Add/Change command strings chg_element bs_pag_blks_res <value> <location> <cell_desc> chg_cell_element bs_pag_blks_res <value> <cell_desc> Display command strings disp_cell <cell_desc> "full" disp_element bs_pag_blks_res <location> <cell_desc> Values Value type Integer Valid range 0 to 4 Default value 2 68P02901W23-P 23 Feb 2004 Number of PAGCH blocks per 52-frame multiframe 5-69 GMR-01 .Technical Description BSS Command Reference bs_pag_blks_res bs_pag_blks_res {3723} Description The bs_pag_blks_res specifies the number of Packet Access Grant Channel (PAGCH) blocks per 52-frame multiframe on a per cell basis. Type A (no operator actions) Supported by OMC-R GUI Yes Cell description required Yes Dependencies The PBCCH/PCCCH optional feature must be unrestricted. The sum of the values set for this parameter and for bs_pbcch_blks must be between 1 and 11. bs_pag_blks_res Chapter 5: CM database parameters The sum of the values set for this parameter and for bs_pbcch_blks must be between 1 and 11. 5-70 GMR-01 68P02901W23-P 23 Feb 2004 . Type A (no operator actions) Supported by OMC-R GUI Yes Cell description required Yes Dependencies The PBCCH/PCCCH optional feature must be unrestricted. The sum of the values set for this parameter and for bs_pag_blks_res must be between 1 and 11.Technical Description BSS Command Reference bs_pbcch_blks bs_pbcch_blks {3723} Description The bs_pbcch_blks specifies the number of Packet Broadcast Control Channel (PBCCH) blocks per 52-frame multiframe on a per cell basis. This parameter must be set to 1 or 2 when psi1_repeat_period is 1. Syntax Add/Change command strings chg_element bs_pbcch_blks <value> <location> <cell_desc> chg_cell_element bs_pbcch_blks <value> <cell_desc> Display command strings disp_cell <cell_desc> "full" disp_element bs_pbcch_blks <location> <cell_desc> Values Value type Integer Valid range 1 to 4 Default value 2 68P02901W23-P 23 Feb 2004 Number of PBCCH blocks per 52-frame multiframe 5-71 GMR-01 . 5-72 GMR-01 68P02901W23-P 23 Feb 2004 .bs_pbcch_blks Chapter 5: CM database parameters The sum of the values set for this parameter and for bs_pag_blks_res must be between 1 and 11. Technical Description BSS Command Reference bs_pcc_chans bs_pcc_chans {3723} Description The bs_pcc_chans specifies the number of Packet Common Control Channel (PCCCH) timeslots on a per cell basis. Type A (no operator actions) Supported by OMC-R GUI Yes Cell description required Yes Dependencies The PBCCH/PCCCH optional feature must be unrestricted. Syntax Add/Change command strings chg_element bs_pcc_chans <value> <location> <cell_desc> chg_cell_element bs_pcc_chans <value> <cell_desc> Display command strings disp_cell <cell_desc> "full" disp_element bs_pcc_chans <location> <cell_desc> Values Value type Integer Valid range 1 Default value 1 68P02901W23-P 23 Feb 2004 Number of physical channels with PCCCHs 5-73 GMR-01 . The value indicates the number of physical channels carrying PCCCHs including the physical channel carrying the PBCCH. Type A (no operator actions) Supported by OMC-R GUI Yes Cell description required Yes Dependencies The PBCCH/PCCCH optional feature must be unrestricted.bs_prach_blks Chapter 5: CM database parameters bs_prach_blks {3723} Description The bs_prach_blks specifies the number of Packet Random Access Channel (PRACH) blocks per 52-frame multiframe on a per cell basis. Syntax Add/Change command strings chg_element bs_prach_blks <value> <location> <cell_desc> chg_cell_element bs_prach_blks <value> <cell_desc> Display command strings disp_cell <cell_desc> "full" disp_element bs_prach_blks <location> <cell_desc> Values Value type Integer Valid range 1 to 11 Default value 4 Number of PRACH blocks per 52-frame multiframe. 5-74 GMR-01 68P02901W23-P 23 Feb 2004 . When the clear_database command is entered. Type B (operator actions required) Supported by OMC-R GUI Yes Cell description required No Dependencies The value of this parameter can only be changed while in the initial SYSGEN mode. Operator actions Place the system in the initial SYSGEN mode then delete the existing database using the clear_database command. calls in progress may be lost. Syntax Change command string chg_element bsc_type <value> 0 Display command string disp_element bsc_type 0 Values Value type Integer Valid range 0 to 3 68P02901W23-P 23 Feb 2004 5-75 GMR-01 . the system does not process calls. When this occurs.Technical Description BSS Command Reference bsc_type bsc_type Description The bsc_type parameter specifies the BSC configuration type. the CM database is deleted. This command is only available for the BSC. bsc_type Chapter 5: CM database parameters Default value 0 Non Abis. Type 0 None References GSM parameter None GSM technical specification This is a Motorola parameter. Type 2 3 Abis. 5-76 GMR-01 68P02901W23-P 23 Feb 2004 . Type 0 1 Non Abis. Type 1 2 Non Abis. A BSIC for a PLMN may have one of eight values. Subsystem/Process MULT Type B (operator actions required) Supported by OMC-R GUI Yes Cell description required Yes Dependencies None Operator actions Respond to the warning prompt which are displayed after the chg_cell_element or chg_element command is used to modify this parameter. but it is important that neighbour cells do not share the same BSIC and the same BCCH RF carrier. A BSIC may be reused.n=no)? 68P02901W23-P 23 Feb 2004 5-77 GMR-01 . The BSIC is calculated using Table 5-3 and Table 5-4 in this description. The chg_element command can change the BSIC within an operational site. 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. where _ _ are unused.Technical Description BSS Command Reference bsic bsic Description The bsic parameter specifies the Base Station Identity Code (BSIC). 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. 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 warning prompt says: WARNING: Changing this element will reset all DRIs associated with this cell Are you sure (y=yes. • Base station Colour Code (BCC). The BCC is also three bits. There is no requirement to unequip the RTF before making this change. bsic Chapter 5: CM database parameters Syntax Add/Change command strings add_cell <gsm_cell_id> <location> add_neighbor <src_gsm_cell_id> <neighbor_gsm_cell_id> <placement> [<list_type>] chg_element bsic <value> <location> <cell_desc> chg_cell_element bsic <value> <cell_desc> Changing the bsic value may cause the system to take a carrier out of service. Display command strings disp_cell <cell_desc> ["full"] disp_element bsic <location> <cell_desc> disp_neighbor <src_gsm_cell_id> Values Value type Integer Valid range Hex = 00h to 3Fh Decimal = 0 to 63 Default value None (See Table 5-3) (See Table 5-4) Table 5-3 lists the hexadecimal values for the base station identity codes. Calls on this carrier may be lost. 5-78 GMR-01 68P02901W23-P 23 Feb 2004 . If the carrier is baseband hopping the system removes it from the active hopping system until the next site reset. depending on the availability of other carriers and timeslots not affected by the out-of-service carrier. The system displays the following warning: WARNING: Changing this element will reset all DRIs associated with this cell. Are you sure (y=yes. n=no)? A “Y" answer resets all the DRIs. Hexadecimal Values BCC 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.Technical Description BSS Command Reference Table 5-3 NCC bsic Base Station Identity Code .20 .2.2. Table 5-4 Base Station Identity Code .8.2 3.2 12.03 .5.5.03 . BSIC_NC(n) GSM technical specification 3.7 68P02901W23-P 23 Feb 2004 5-79 GMR-01 .Decimal Values NCC BCC 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.4.20 .2.Annex A 12.8. Type A (no operator actions) Supported by OMC-R GUI Yes Cell description required No Dependencies This parameter is valid only at a BSC.bss_egsm_alm_allowed Chapter 5: CM database parameters 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. Syntax Change command string chg_element bss_egsm_alm_allowed <value> 0 Display command string disp_element bss_egsm_alm_allowed 0 Values Value type Boolean Valid range 0 Disabled 1 Enabled Default value 0 5-80 GMR-01 68P02901W23-P 23 Feb 2004 . The EGSM feature must be unrestricted. This parameter is allowed only at password level 3. Technical Description BSS Command Reference bss_msc_overload_allowed bss_msc_overload_allowed Description The bss_msc_overload_allowed parameter determines whether or not a MSC overload is allowed. the BSS bars one access class at a time if it receives an OVERLOAD message. When this parameter is enabled. Type A (no operator actions) Supported by OMC-R GUI No Cell numbers required No Dependencies None Syntax Change command string chg_element bss_msc_overload_allowed <value> Display command string disp_element bss_msc_overload_allowed Values Value type Boolean Valid range 0 Disabled 1 Enabled Default value 68P02901W23-P 23 Feb 2004 0 5-81 GMR-01 . BSS software processes using this parameter are not notified when the change is made. Syntax Change command string chg_element bssgp_block_retries <value> <location> Display command string disp_element bssgp_block_retries <location> Values Value type Integer (retries) Valid range 1 to 3 Default value 3 5-82 GMR-01 68P02901W23-P 23 Feb 2004 . Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required No Dependencies This parameter can be used only if the GPRS feature is unrestricted.bssgp_block_retries Chapter 5: CM database parameters 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. BSS software processes using this parameter are notified immediately the change is made. Operator actions: None This is a Motorola proprietary parameter. This parameter can be set in or out of SYSGEN mode. Syntax Change command string chg_element bssgp_cbl_bit <value> <location> Display command string disp_element bssgp_cbl_bit <location> 68P02901W23-P 23 Feb 2004 5-83 GMR-01 .Technical Description BSS Command Reference bssgp_cbl_bit bssgp_cbl_bit {4449} Description The bssgp_cbl_bit parameter specifies whether the CBL (Current Bucket Level) feature is available at the PCU or not. that is. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required No Dependencies This parameter can be used only if the GPRS feature is unrestricted. whether the CBL bit is set or not. bssgp_cbl_bit Chapter 5: CM database parameters Values Value type Boolean Valid range 0 or 101 Default value 0 CBL procedures not supported (CBL bit not set) CBL procedures supported (CBL bit set) 5-84 GMR-01 68P02901W23-P 23 Feb 2004 . Syntax Change command string chg_element bssgp_racap_retries <value> <location> Display command string disp_element bssgp_racap_retries <location> Values Value type Integer (retries) Valid range 1 to 3 Default value 3 68P02901W23-P 23 Feb 2004 5-85 GMR-01 . Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required No Dependencies The GPRS feature must be unrestricted. Operator actions None BSS software processes using this parameter are not notified when the change is made.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. Operator actions None BSS software processes using this parameter are not notified when the change is made.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 Change command string chg_element bssgp_reset_retries <value> <location> Display command string disp_element bssgp_reset_retries <location> Values Value type Integer (retries) Valid range 1 to 3 Default value 3 5-86 GMR-01 68P02901W23-P 23 Feb 2004 . Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required No Dependencies The GPRS feature must be unrestricted. Syntax Change command string chg_element bssgp_unblock_retries <value> <location> Display command string disp_element bssgp_unblock_retries <location> Values Value type Integer (retries) Valid range 1 to 3 Default value 3 68P02901W23-P 23 Feb 2004 5-87 GMR-01 . Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required No Dependencies The GPRS feature must be unrestricted. Operator actions None BSS software processes using this parameter are not notified when the change is made.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. 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.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. Type A (no operator actions) Supported by OMC-R GUI Yes Cell description required Yes Dependencies decision_alg_type = 1 Syntax Add/Change command strings add_cell <gsm_cell_id> <location> chg_element bts_p_con_ack <value> <location> <cell_desc> chg_cell_element bts_p_con_ack <value> <cell_desc> Display command strings disp_cell <cell_desc> ["full"] disp_element bts_p_con_ack <location> <cell_desc> Values Value type Integer (1 Step = 2 multiframes) Valid range 0 to 31 5-88 GMR-01 68P02901W23-P 23 Feb 2004 . Technical Description BSS Command Reference bts_p_con_ack 0 1 2 . 62 SACCH multiframes 1 (equals 2 SACCH multiframes) References GSM parameter P_CON_ACK GSM technical specification None 68P02901W23-P 23 Feb 2004 5-89 GMR-01 ... 31 Default value 0 SACCH multiframes 2 SACCH multiframes 4 SACCH multiframes ... px + 1) hreqave / 2 Where: • x equals 1 (lower threshold of RXLEV). 3 (lower threshold of RXQUAL). hreqave bts_p_con_ack decision_1_n1 through decision_1_n4 decision_1_p1 through decision_1_p4 5-90 GMR-01 68P02901W23-P 23 Feb 2004 . • n equals the values assigned for decision_1_ny where y is a value from 1 to 4.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. Type A (no operator actions) Supported by OMC-R GUI Yes Cell description required Yes Dependencies This parameter will not work if the specified location is the BSC (location = 0). 2 (upper threshold of RXLEV). • p equals the values assigned for decision_1_py where y is a value from 1 to 4. or 4 (upper threshold of RXQUAL). • hreqave is the number of measurements from the MS that are used in calculating one average. The time period is greater than or equal to (nx . ... 31 Default value 0 SACCH multiframes 2 SACCH multiframes 4 SACCH multiframes . 62 SACCH multiframes 2 (equals 4 SACCH multiframes) References GSM parameter P_CON_INTERVAL GSM technical specification 5.Table 1 68P02901W23-P 23 Feb 2004 5-91 GMR-01 .Technical Description BSS Command Reference bts_p_con_interval Syntax Add/Change command strings add_cell <gsm_cell_id> <location> chg_element bts_p_con_interval <value> <location> <cell_desc> chg_cell_element bts_p_con_interval <value> <cell_desc> Display command strings disp_cell <cell_desc> ["full"] disp_element bts_p_con_interval <location> <cell_desc> Values Value type Integer (1 Step = 2 multiframes) Valid range 0 to 31 0 1 2 .08 ..Appendix A . When enabled.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. the BSS uses up to 15 power control levels. Type A (no operator actions) Supported by OMC-R GUI Yes Cell description required Yes Dependencies None Syntax Add/Change command strings add_cell <gsm_cell_id> <location> chg_element bts_power_control_allowed <value> <location> <cell_desc> chg_cell_element bts_power_control_allowed <value> <cell_desc> Display command strings disp_cell <cell_desc> ["full"] disp_element bts_power_control_allowed <location> <cell_desc> Values Value type Boolean Valid range 0 or 1 Default value 0 BTS power control disabled 1 BTS power control enabled 0 5-92 GMR-01 68P02901W23-P 23 Feb 2004 . Technical Description BSS Command Reference bts_power_control_allowed The value 0 is the only valid value at M-Cellcity sites.2 68P02901W23-P 23 Feb 2004 5-93 GMR-01 .05 .1. both 0 and 1 values are permitted at Horizonmicro2 and Horizoncompact2 sites.4. References GSM parameter EN_BS_PC GSM technical specification 5. and M-Cellcompact sites Default value 0 5-94 GMR-01 68P02901W23-P 23 Feb 2004 . M-Cellaccess. Type A (no operator actions) Supported by OMC-R GUI Yes Cell description required Yes Dependencies This parameter may be modified only when the Dual Band Cells feature is unrestricted (inner_zone_alg set to 3). Syntax Change command strings chg_element bts_txpwr_max_inner <value> <location> <cell_desc> chg_cell_element bts_txpwr_max_inner <value> <cell_desc> Display command string disp_element bts_txpwr_max_inner <location> <cell_desc> Values Value type Integer (1 step = 2 dBm) Same as those for max_tx_bts except based on secondary_freq_type. not frequency_type. EGSM.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. for M-Cellmicro. and DCS1800. Valid range -1 to 21 0 to 6 for PGSM. external. Table 5-5 lists the values for CTU2 (SD-SCM. Table 5-8.Technical Description BSS Command Reference bts_txpwr_max_inner Refer to Table 5-5. internal. Table 5-6 also specifies the types of combing in used: none. DD-DCM). The combining types are defined as follows: 68P02901W23-P 23 Feb 2004 5-95 GMR-01 . and Table 5-9 for additional information about the values for this parameter. and both internal and external. The power specified is the cabinet antenna connector maximum output power. Table 5-6. The values represent the calibrated output power at the top of the cabinet with one stage of combining. Table 5-7. All figures are ±2 dB. 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. bts_txpwr_max_inner Chapter 5: CM database parameters • 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. M-Cellarena and M-Cellarenamacro sites. this would allow two CTU2 in DD-DCM to be combined to create a four-carrier sector. 5-96 GMR-01 68P02901W23-P 23 Feb 2004 . Table 5-6 Cabinet antenna connector maximum output power (Watts) Horizonmacro XCVR Type CTU CTU2 SD-SCM CTU2 DD-DCM Combining Horizon II EGSM900 DCS1800 EGSM900 DCS1800 None 40 32 N/A N/A External 20 16 N/A N/A None 40 32 63 50 External 20 16 28 22 Internal 10 10 20 16 Internal and external 4. DCS1800 and PCS1900 M-Cellmicro. For example.5 9 7 Table 5-7 lists the values for PGSM.5 4. Hence the power figure for internal combining represents two carriers at this transmit power for a CTU2 in DD-DCM. EGSM. • External (to the XCVR): The output of the XCVR is connected via a single stage of external hybrid combining to the antenna. sites Valid Input PGSM and EGSM M-Cellmicro values DCS1800 and PCS1900 M-Cellmicro values M-Cellarenamacrovalues 0 31 dBm 30 dBm 40 dBm 1 29 dBm 28 dBm 38 dBm 2 27 dBm 26 dBm 36 dBm 3 25 dBm 24 dBm 34 dBm 4 23 dBm 22 dBm 32 dBm 5 21 dBm 20 dBm 30 dBm 6 19 dBm 18 dBm 28 dBm Table 5-8 lists the values for DCS1800 and M-Cellaccess sites. DCS1800 and PCS1900 M-Cellmicro. M-Cellcity. • Internal and external: External hybrid combining is used on a CTU2 in DDM. Note that the internal combining is still present when the CTU2 is used in DD-SCM. • 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.etc. a two-carrier sector is required from two SDX or two CTU2-SD. EGSM. Table 5-7 Values for PGSM. For example. 30 dBm ExCell 4 BTS4. of some Motorola cabinets with different combinations of RCUs and combiners.79 dBm duplexer ” 4 13. Table 5-9 Sample output power Type of combining Number of radios Output power (as calibrated) hybrid 2 20W [Symbol_approximate] 43.5W [Symbol_approximate] 41.98 dBm hybrid 2 20W [Symbol_approximate] 43. Table 5-9 lists sample output power. BTS6 cavity (2 neighbouring cabinets) M-Cell2 or M-Cell6 6 68P02901W23-P 23 Feb 2004 5-97 GMR-01 . EGSM and M-Cellaccess values DCS1800 M-Cellaccess values 0 12 dBm 17 dBm 1 10 dBm 15 dBm 2 8 dBm 13 dBm 3 6 dBm 11 dBm 4 4 dBm 9 dBm 5 2 dBm 7 dBm 6 0 dBm 5 dBm The actual output power of a cabinet depends on the type of combining that is used.Technical Description BSS Command Reference bts_txpwr_max_inner Table 5-8 Values for DCS1800 and M-Cellaccess.01 dBm cavity (1 cabinet) ” 6 19W [Symbol_approximate] 42. sites Valid Input PGSM.01 dBm cavity (1 cabinet) ” 5 25W [Symbol_approximate] 43. measured at the top of the cabinet.5W [Symbol_approximate] 43. BTS5.14 dBm hybrid 2 17.01 dBm cavity (1 cabinet) ” 4 25W [Symbol_approximate] 43.98 dBm ” 10 13W [Symbol_approximate] 41. 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-98 GMR-01 68P02901W23-P 23 Feb 2004 . and for 800 kHz minimum channel distance with cavity combining.bts_txpwr_max_inner Chapter 5: CM database parameters The listed power is valid for 600 kHz minimum channel distance. It is valid only for sites 1 to 120. Horizoncompact and Horizonmacro cabinets. This parameter must be set to 0 for M-Cell 2. or if max_dris is set to 0.Technical Description BSS Command Reference bts_type bts_type Description The bts_type parameter specifies the BTS configuration type. M-Cellcity. Type A (no operator actions) Supported by OMC-R GUI Yes Cell description required No Dependencies This parameter may not be changed to 0 if DHPs exist at the site. M-Cell6. Syntax Change command string chg_element bts_type <value> <location> Display command string disp_element bts_type <location> Values Value type Integer Valid range 0 or 1 Default value 68P02901W23-P 23 Feb 2004 0 BTP 1 BTP and DHP None 5-99 GMR-01 . Horizonmicro. 5-100 GMR-01 68P02901W23-P 23 Feb 2004 .bts_type Chapter 5: CM database parameters References GSM parameter None GSM technical specification This is a Motorola parameter. There must be one BVCI per cell and one signalling BVCI per BSS. BSS software processes using this parameter are not notified when the change is made. Only one BVCI can be mapped to a single cell.Technical Description BSS Command Reference bvci bvci Description The bvci parameter specifies a BSSGP Virtual Connection Identifier (BVCI). Syntax Add/Change command strings add_cell <gsm_cell_id> <location> chg_element bvci <value> <location> <cell_desc> chg_cell_element bvci <value> <cell_desc> Display command strings disp_cell <cell_desc> ["full"] disp_element bvci <location> <cell_desc> 68P02901W23-P 23 Feb 2004 5-101 GMR-01 . A BVCI cannot be modified if gprs_enabled is set for the cell. this parameter can be modified without a reset to a particular device or function. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required Yes Dependencies This parameter can be used only if the GPRS feature is unrestricted. Restrictions All BVCIs must be unique. and one BVCI must be allocated as the BSSGP signalling BVCI. BVCIs are automatically generated by the BSS on creation of a cell. That is. bvci Chapter 5: CM database parameters Values Value type Integer Valid range 2 to 65535 Default value None 5-102 GMR-01 68P02901W23-P 23 Feb 2004 . 5-103 GMR-01 . a maximum of eight instances may be created using the trace_call command. the system ignores call trace requests from the MSC. no traces are exclusively reserved for MSC initiated traces. MSC initiated traces are still allowed. This permits a maximum of 16 instances to be created using the trace_call command. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required No Dependencies None Syntax Change command string chg_element call_trace_options <value> <location> Display command string disp_element call_trace_options <location> Values Value type Integer Valid range 0 to 100. and 255 0 to 100 68P02901W23-P 23 Feb 2004 The percentage of traces reserved for MSC initiated traces on a per LCF basis. If the call_trace_options element is set to 0. This percentage is specified using the call_trace_options element. This would permit a maximum of 16 instances to be created using the trace_call command. The number of call trace instances that may be created is affected by the percentage of traces reserved exclusively for MSC initiated traces. It also specifies the percentage of traces exclusively reserved for MSC initiated call traces. For example. If the call_trace_options element is set to 255.Technical Description BSS Command Reference call_trace_options call_trace_options Description The call_trace_options parameter enables or disables MSC initiated traces. if 50% of the traces are reserved for initiation from the MSC. 0 5-104 GMR-01 68P02901W23-P 23 Feb 2004 .call_trace_options Chapter 5: CM database parameters 255 Default value MSC invoked call traces disabled. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required No Dependencies This parameter is valid only at the BSC.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.713This is a Motorola defined parameter. Syntax Change command string chg_element called_pci <value> 0 Display command string disp_element called_pci 0 Values Value type Boolean Valid range 0 or 1 Default value 0 Point code is not included 1 Point code is included None References GSM specification 68P02901W23-P 23 Feb 2004 CCITT Q. 5-105 GMR-01 . Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required No Dependencies This parameter is valid only at the BSC. Syntax Change command string chg_element calling_pci <value> 0 Display command string disp_element calling_pci 0 Values Value type Boolean Valid range 0 or 1 Default value 0 Disabled 1 Enabled None References GSM specification CCITT Q.713 This is a Motorola defined parameter.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. 5-106 GMR-01 68P02901W23-P 23 Feb 2004 . 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.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. Then the system waits for the same period of time before placing the next carrier into battery conservation mode. For example. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required No Dependencies None Syntax Change command string chg_element carrier_disable_time <value> <location> Display command string disp_element carrier_disable_time <location> Values Value type Integer (seconds) Valid range 120 to 65535 Default value 120 68P02901W23-P 23 Feb 2004 5-107 GMR-01 . 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-107). The BCCH carrier will continue to transmit after the battery conservation feature has taken the carrier out of service. during a main power failure). Although the BCCH carrier is disabled.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. When the value of 0 is selected. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required No Dependencies None Syntax Change command string chg_element carriers_ins_pwr_fail <value> <location> Display command string disp_element carriers_ins_pwr_fail <location> 5-108 GMR-01 68P02901W23-P 23 Feb 2004 . Non BCCH carriers are taken out of service before the BCCH carrier. 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. Technical Description BSS Command Reference carriers_ins_pwr_fail Values Value type Integer Valid range 0 to 30 0 Default value 68P02901W23-P 23 Feb 2004 All carriers are taken out of service. 30 5-109 GMR-01 . The fast connect function supports X. Syntax Change command strings chg_element cbc_fast_select <value> 0 A site reset is required when the value of cbc_fast_select is changed. Display command strings disp_element cbc_fast_select 0 Values Value type Boolean Valid range 0 or 1 Default value 0 Disabled 1 Enabled 0 5-110 GMR-01 68P02901W23-P 23 Feb 2004 . Resetting the site generates several alarms. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required No Dependencies This parameter is valid only for the BSC.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. However. these alarms are blocked by the system.25 networks that do not support user data in connect and disconnect requests. 49 This is a Motorola defined parameter.Technical Description BSS Command Reference cbc_fast_select References GSM specification 68P02901W23-P 23 Feb 2004 03.4103. 5-111 GMR-01 . cbc_intface_vers Chapter 5: CM database parameters cbc_intface_vers Description The cbc_intface_vers parameter selects the interface for each BSC site. Syntax Change command strings chg_element cbc_intface_vers <value> 0 Display command strings disp_element cbc_intface_vers 0 Values Value type Boolean Valid range 0 or 1 Default value 0 Standard interface 1 Interface with the repetition rate interpretation and CBCH loading fields 0 5-112 GMR-01 68P02901W23-P 23 Feb 2004 . Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required No Dependencies This parameter is only valid for the BSC. The available interfaces are either the standard interface or the interface with the repetition rate interpretation and CBCH loading fields. Syntax Change command strings chg_element cbc_vbind_cntr <value> 0 Display command strings disp_element cbc_vbind_cntr 0 Values Value type Integer (number of VBINDs) Valid range 0 to 255 Default value 0 68P02901W23-P 23 Feb 2004 5-113 GMR-01 .Technical Description BSS Command Reference cbc_vbind_cntr cbc_vbind_cntr Description The cbc_vbind_cntr parameter sets the number of successful VBINDs sent by the BSS to the CBC before a negotiate must take place within the next VBIND sent. This parameter is effective on a per BSC basis. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required No Dependencies This parameter is only valid for the BSC. The CBCH is used with the Short Message Service (SMS) Cell Broadcast feature. Syntax Change command strings chg_element cbch_enabled <value> <location> <cell_desc> chg_cell_element cbch_enabled <value> <cell_desc> Display command string disp_element cbch_enabled <location> <cell_desc> Values Value type Boolean Valid range 0 or 1 Default value 0 Disabled 1 Enabled None 5-114 GMR-01 68P02901W23-P 23 Feb 2004 . An operator defined message or set of background messages may be transmitted on the CBCH when the cbch_enabled parameter is enabled. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required Yes Dependencies Enabling of CBCH is not permitted if no AGCH is reserved in a non-combined cell (bs_ag_blks_res = 0 and ccch_conf is other than 1).cbch_enabled Chapter 5: CM database parameters cbch_enabled Description The cbch_enabled parameter enables the Cell Broadcast Channel (CBCH) option in a cell. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required No Dependencies This parameter is only valid for a BTS site. This parameter is effective on a per BTS site basis.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. Syntax Change command string chg_element cbs_outage_cntr <value> <location> Display command string disp_element cbs_outage_cntr <location> Values Value type Integer (number of broadcast slots) Valid range 0 to 255 Default value 0 68P02901W23-P 23 Feb 2004 5-115 GMR-01 . all calls on an in-service carrier will be lost. The value depends on the size of the cell and on the number of access attempts expected on the cell. 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. and max_number_of_sdcchs parameters may also need to be changed. the bs_ag_blks_res.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. Are you sure (y=yes. If this is not done. the site may not boot properly and will never reach the busy state. all calls on an in-service carrier will be lost and hopping for this carrier will be disabled until the site is reset. This field defines whether the CCCHs are combined with SDCCH and SACCH onto the same basic physical channel. Type B (operation actions required) Supported by OMC-R GUI Yes Cell numbers required Yes 5-116 GMR-01 68P02901W23-P 23 Feb 2004 . Loss of calls depends on the availability of other carriers. If synthesizer hopping. This has the following effects: If baseband hopping. The system rejects this command if it is attempted for all sites. number_sdcch_preferred. n=no)? Enter Enter Enter Enter Enter CRM maximum number of SDCCHs: CRM SDCCH low water mark: CRM SDCCH high water mark: number of SDCCHs preferred: 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. 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. When the chg_cell_element command is used to change the value of this parameter. When the value of this parameter is changed. min_number_of_sdcchs. 0. four PDCHs are supported for a BCCH carrier.. • Set to 2.. 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.. • Set to 1. 4. seven PDCHs are supported for a BCCH carrier.. 16. with an offset of 4 (that is. • 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). • max_number_of_sdcchs must be a multiple of 8 (+4). 2. Operator actions 68P02901W23-P 23 Feb 2004 Respond to the prompts presented after entering the chg_cell_element command. • max_number_of_sdcchs must be divisible by 8. This parameter can be used with the GPRS feature unrestricted as follows: • Set to 0.12. The GPRS timeslots on the GPRS carrier must have the same FHI. • Set to 4.. {3723} Because the PBCCH/PCCCH timeslots are configured on the BCCH carrier. values for the following parameters must meet specific criteria: • number_sdcchs_preferred must be in multiples of 8. results in a warning to the operator when pccch_enabled is set to 1.48) • number_sdcchs_preferred must be less than or equal to sdcch_need_low_water_mark. If GPRS is unrestricted for a cell. • Set to 6. with the PBCCH/PCCCH optional feature unrestricted. 5-117 GMR-01 ... • The minimum number of sdcchs must be divisible by 8. attempts to modify ccch_conf are rejected if the required timeslots are configured as GPRS timeslots.44 ) • The minimum number of sdcchs must be a multiple of 8 (+4).4. any attempt to change ccch_conf. GPRS channels must have the same training sequence codes. five PDCHs are supported for a BCCH carrier. six PDCHs are supported for a BCCH carrier. 0. 8. seven PDCHs are supported for a BCCH carrier. or 6.Technical Description BSS Command Reference Dependencies ccch_conf If ccch_conf = 0. • 0 v bs_ag_blks_res v 7 If ccch_conf = 1.. 6 0 (0 CCH timeslots used.5.4 0. these alarms are blocked by the system. non-combined) References GSM parameters CCCH_CONF. combined or non-combined) Valid range 0.3.6. Display command strings disp_cell <cell_number> disp_element ccch_conf <location> <cell_desc> Values Value type Integer (CCH timeslots used. 4. chg_cell_element ccch_conf <value> <cell_desc> A site reset is required when the value of ccch_conf is changed. However.2: organisation of common control channels 5. CCCH_SDCCH_COMB GSM specifications 5.4: allowable channel configurations 4.6.02 .08 .5.2: organisation of common control channels 5.ccch_conf Chapter 5: CM database parameters Syntax Add/Change command string add_cell <gsm_cell_id> <location> The system rejects this command if it is attempted when location = all.7: table 5 4.4: BS_CCCH_SDCCH_COMB 5-118 GMR-01 68P02901W23-P 23 Feb 2004 .03 . 2.3. and 6 Default value Non-combined Combined Non-combined Non-combined Non-combined 0 1 2 4 6 0 0 0.02 .1 and 6. BS_CCCH_SDCCH_COMB 5. Resetting the site generates several alarms. 2 . 1. 2 0.1: BS_CC_CHANS.02 . 4. 2.02 .6. Refer to rach_load_period. ssm_critical_overload_threshold or tch_flow_control.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. rach_overload_threshold. Syntax Change command string chg_element ccch_load_period <value> <location> <cell_desc> chg_cell_element ccch_load_period <value> <cell_desc> Display command strings disp_cell <cell_desc> ["full"] disp_element ccch_load_period <location> <cell_desc> 68P02901W23-P 23 Feb 2004 5-119 GMR-01 . ssm_normal_overload_threshold. Other parameters can affect flow control. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required Yes Dependencies This parameter must be greater than or equal to the rach_load_period. 5.1.2.ccch_load_period Chapter 5: CM database parameters Values Value type Integer (1 Step = 1 TDMA multiframe) Valid range 1 to 1020 Default value 40 References GSM parameter CCCH_LOAD_IND_PERIOD GSM specification 5.1 .08.3 5-120 GMR-01 68P02901W23-P 23 Feb 2004 . as illustrated in the diagram below. For example. Table 5-10 lists the values for barring classes. 3 7 and 9. Table 5-10 68P02901W23-P 23 Feb 2004 Values for barring classes 5-121 GMR-01 . A channel request is initiated only when the access class of a mobile is “not barred". divided into four groups. The list of authorized access classes is broadcast on the BCCH by way of SYSTEM INFORMATION messages. There are 16 cell access classes. Also broadcast are the classes that have access to emergency calls. 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. 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 Z = Y = X = W= Y X W 0000 (0h) 0010 (2h) 1000 (8h) 1100 (Ch) To bar access classes 2. 3. if access classes 2.Fh) controls access classes 11 though 8 X (0 . 7 and 9 were to be barred.Fh) controls access classes 15 through 12 Y (0 .Fh) controls access classes 7 though 4 W (0 .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. The hexadecimal value for cell_bar_access_class can be determined from the diagram below. See also the emergency_class_switch parameter. 15 14 13 12 11 10 Z 9 8 7 5 6 Y 4 3 2 X 1 0 W 0 = unbarred 1 = barred The The The The value value value value of of of of Z (0 .Fh) controls access classes 3 through 0. 1 and 2 8 bar class 15 bar class 11 bar class 7 bar class 3 9 bar classes 12 and 15 bar classes 8 and 11 bar classes 4 and 7 bar classes 0 and 3 a bar classes 13 and 15 bar classes 9 and 11 bar classes 5 and 7 bar classes 1 and 3 b bar classes 12. 9 10 and 11 bar classes 4. 5 6. 9 and 11 bar classes 4. 5 and 7 bar classes 0. 14 and 15 bar classes 9. and 7 bar classes 0.cell_bar_access_class Chapter 5: CM database parameters Hexadecimal value Z Y X W 0 No barring No barring No barring No barring 1 bar class 12 bar class 8 bar class 4 bar class 0 2 bar class 13 bar class 9 bar class 5 bar class 1 3 bar classes 12 and 13 bar classes 8 and 9 bar classes 4 and 5 bar classes 0 and 1 4 bar class 14 bar class 10 bar class 6 bar class 2 5 bar classes 12 and 14 bar classes 8 and 10 bar classes 4 and 6 bar classes 0 and 2 6 bar classes 13 and 14 bar classes 9 and 10 bar classes 5 and 6 bar classes 1 and 2 7 bar classes 12. 10 and 11 bar classes 5. 10 and 11 bar classes 4. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required Yes Dependencies cell_bar_access_switch 5-122 GMR-01 68P02901W23-P 23 Feb 2004 . 13 and 15 bar classes 8. 2 and 3 e bar classes 13. 14 and 15 bar classes 8. 13 and 14 bar classes 8. 6 and 7 bar classes 0. 2 and 3 When entering a hexadecimal value. the suffix “h" is required. 14 and 15 bar classes 8. 6 and 7 bar classes 1.2 and 3 f bar classes 12. 13. 1. 1 and 3 c bar classes 14 and 15 bar classes 10 and 11 bar classes 6 and 7 bar classes 2 and 3 d bar classes 12. 5 and 6 bar classes 0. 9 and 10 bar classes 4. 08 . 4.1.3.3.08 .3.1 68P02901W23-P 23 Feb 2004 5-123 GMR-01 .Technical Description BSS Command Reference cell_bar_access_class Syntax Add/Change command strings add_cell <gsm_cell_id> <location> chg_element cell_bar_access_class <value> <location> <cell_desc> chg_cell_element cell_bar_access_class <value> <cell_desc> Display command strings disp_cell <cell_desc> ["full"] disp_element cell_bar_access_class <location> <cell_desc> Values Value type Integer Valid range 0 to 65535 Default value 0 References GSM parameter AC_CN GSM specification 4.1.3. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required Yes Dependencies None Syntax Add/Change command strings add_cell <gsm_cell_id> <location> chg_element cell_bar_access_switch <value> <location> <cell_desc> chg_cell_element cell_bar_access_switch <value> <cell_desc> Display command strings disp_cell <cell_desc> ["full"] disp_element cell_bar_access_switch <location> <cell_desc> Values Value type Boolean Valid range 0 or 1 0 Cell is not barred 5-124 GMR-01 68P02901W23-P 23 Feb 2004 . A MS decodes the BCCH data to determine if it is allowed access to the system.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. BCCH data includes information which indicates that the cell transmitting the data is part of the selected PLMN (unbarred) or not (barred). barred. and cannot be. 5. 10.22 .cell description .5.2 5.36.1 68P02901W23-P 23 Feb 2004 5-125 GMR-01 .7: .30 5.2.8.10.3.08 .5.Technical Description BSS Command Reference cell_bar_access_switch 1 Default value Cell is barred 0 References GSM parameter CELL_BAR_ACCESS GSM specifications 4.17.6.08 .6.2.08 . figure.20 . table 10.cell bar access 03.4: C1 equation 12. Syntax Add/Change command strings add_cell <gsm_cell_id> <location> chg_element cell_bar_qualify <value> <location> <cell_desc> chg_cell_element cell_bar_qualify <value> <cell_desc> Display command strings disp_cell <cell_desc> ["full"] disp_element cell_bar_qualify <location> <cell_desc> Values Value type Boolean Valid range 0 or 1 Default value 0 Normal priority cell 1 Low priority cell 0 5-126 GMR-01 68P02901W23-P 23 Feb 2004 .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. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required Yes Dependencies This parameter cannot be changed if the cell_reselect_param_ind parameter does not equal 1. 08 Table 1a in section 9.5.2.35 5.Technical Description BSS Command Reference cell_bar_qualify References GSM specification 68P02901W23-P 23 Feb 2004 3.08 Table 10.22 4.32 in section 10. This is a Motorola defined parameter. 5-127 GMR-01 . Differences in received signal levels from 0 to 14 dB (in 2 dB increments) are used for cell reselection. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required Yes Dependencies C1 (path loss criterion) Syntax Add/Change command strings add_cell <gsm_cell_id> <location> chg_element cell_reselect_hysteresis <value> <location> <cell_desc> chg_cell_element cell_reselect_hysteresis <value> <cell_desc> Display command strings disp_cell <cell_desc> ["full"] 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-128 GMR-01 68P02901W23-P 23 Feb 2004 .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. 8.6.08 .2 4.23.cell reselect hysteresis 68P02901W23-P 23 Feb 2004 5-129 GMR-01 .5. figure 10.4.2.radio link ctl dl .10.20 .2.5.08 . and table 10.12 .6.17 12.Technical Description BSS Command Reference Default value cell_reselect_hysteresis 2 4 dB 3 6 dB 4 8 dB 5 10 dB 6 12 dB 7 14 dB None References GSM parameter CE_RE_HYS GSM specifications 5. Higher values encourage MSs to reselect a specific cell. Syntax Add/Change command strings add_cell <gsm_cell_id> <location> chg_element cell_reselect_offset <value> <location> <cell_desc> chg_cell_element cell_reselect_offset <value> <cell_desc> Display command strings disp_cell <cell_desc> ["full"] 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-130 GMR-01 68P02901W23-P 23 Feb 2004 . Lower C2 values discourage fast moving MSs from selecting a specific cell. When more than one cell is available for reselection. the MS reselects the cell with the highest C2 value. C2 is the reselection priority assigned to a cell which can be broadcast on the BCCH of each cell. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required Yes Dependencies This parameter may not be changed if the cell_reselect_parm_ind parameter is not equal to 1.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. 22 4.2.5.Technical Description BSS Command Reference 2 cell_reselect_offset 4 dB .08 68P02901W23-P 23 Feb 2004 5-131 GMR-01 .32a in section 10. .08 table 10.35 5. 63 Default value 126 dB 0 References GSM parameter CELL_RESELECT_OFFSET GSM specifications 3. . and penalty_time) are broadcast to the MS by the network in the system information messages. temporary_offset. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required Yes Dependencies None Syntax Add/Change command strings add_cell <gsm_cell_id> <location> chg_element cell_reselect_param_ind <value> <location> <cell_desc> chg_cell_element cell_reselect_param_ind <value> <cell_desc> Display command strings disp_cell <cell_desc> ["full"] disp_element cell_reselect_param_ind <location> <cell_desc> Values Value type Boolean Valid range 0 or 1 Default value 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 0 5-132 GMR-01 68P02901W23-P 23 Feb 2004 .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. 2. 68P02901W23-P 23 Feb 2004 5-133 GMR-01 .08 This parameter is not used at the present time.5.Technical Description BSS Command Reference cell_reselect_param_ind References GSM parameter CELL_RESELECT_PARAM_IND GSM specifications 4. C2 parameters are not used at the present time since they are dependent on this parameter being enabled.355.08 table 10.32a in section 10. Type A (no operator actions) Supported by OMC-R GUI Yes Cell description required No Dependencies None Syntax Add/Change command strings equip <location> rtf modify_value <location> chan_alloc_priority <new_value> rtf <rtf_id1> <rtf_id2> <rtf_id3> Display command string disp_equipment <location> rtf <rtf_id1> <rtf_id2> <rtf_id3> Values Value type Integer (representing the channel allocation for an RTF) Valid range 0 to 250 Default value 0 Highest priority 250 Lowest priority 0 5-134 GMR-01 68P02901W23-P 23 Feb 2004 . A channel from the highest priority carrier matching the requested interference band is allocated to a channel request.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. The reconfiguration process continues until the number of idle SDCCHs reaches the sdcch_need_high_water_mark value. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required Yes Dependencies None Syntax Change command strings chg_element channel_reconfiguration_switch <value> <location> <cell_desc> chg_cell_element channel_reconfiguration_switch <value> <cell_desc> Display command strings disp_cell <cell_desc> ["full"] disp_element channel_reconfiguration_switch <location> <cell_desc> Values Value type Boolean Valid range 0 or 1 0 68P02901W23-P 23 Feb 2004 Disabled 5-135 GMR-01 . 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.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. channel_reconfiguration_switch Chapter 5: CM database parameters 1 Default value Enabled 0 References GSM specification Figure 3 5.02 . 5-136 GMR-01 68P02901W23-P 23 Feb 2004 .4: permitted channel combinations of logical channels This is a Motorola defined parameter.6. The cic_block_thresh parameter must be less than the cic_unblock_thresh parameter except when both parameters are 0.Technical Description BSS Command Reference cic_block_thresh cic_block_thresh {4415} Description The cic_block_thresh parameter specifies the threshold for blocking Circuit Identity Codes (CICs) according to the availability of idle Aters. The eac_mode parameter must be enabled. An AXCDR device cannot be in Enhanced Auto-Connect mode if CIC validation is disabled. Syntax Change command strings modify_value 0 cic_block_thresh <value> AXCDR <axcdr_id> equip 0 AXCDR 68P02901W23-P 23 Feb 2004 5-137 GMR-01 . The AMR Enhanced Capacity feature must be unrestricted. Type A (no operator actions) Supported by OMC-R GUI Yes Cell description required No Dependencies This parameter can be modified inside and outside Sysgen mode. the user is prompted for following parameters: • device ID. Display command string disp_equipment 0 AXCDR <axcdr_id> Values Value type Integer Valid range 0 to 245 Default value 0 5-138 GMR-01 68P02901W23-P 23 Feb 2004 . the user is prompted for the following parameters: • CIC blocking threshold. • CIC validation. • EAC mode.cic_block_thresh Chapter 5: CM database parameters After entering the equip AXCDR command. When eac_mode is enabled. • CIC unblocking threshold. ) This parameter can be set only at a BSC. (One successful call might be too short for the Channel Coder Unit (CCU) to send an error indication. Syntax Change command strings chg_element cic_error_clr_thresh <value> 0 Display command strings disp_element cic_error_clr_thresh 0 Values Value type Integer Valid range 0 to 253 Default value 0 68P02901W23-P 23 Feb 2004 5-139 GMR-01 . If the threshold is increased during operation.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). thus clearing the alarm prematurely. Type A (no operator actions) Supported by OMC-R GUI Yes Cell description required No Dependencies Two successful calls are required on a resource before an alarm can be cleared within this threshold. any existing counts between the new and the old threshold does not clear an alarm until another successful call is made on the CIC. Syntax Change command strings chg_element cic_error_gen_thresh <value> 0 Display command strings disp_element cic_error_gen_thresh 0 Values Value type Integer Valid range 2 to 255 Default value 6 5-140 GMR-01 68P02901W23-P 23 Feb 2004 . no immediate alarm occurs.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). The new threshold takes effect only when the CIC error count changes. Type A (no operator actions) Supported by OMC-R GUI Yes Cell description required No Dependencies This parameter can be set only at a BSC. If the threshold is changed during operation. Type A (no operator actions) Supported by OMC-R GUI Yes Cell description required No Dependencies This parameter can be set only at a BSC.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 Change command strings chg_element cic_error_inc <value> 0 Display command string disp_element cic_error_inc 0 Values Value type Integer Valid range 0 CIC alarms not raised 1 to 255 CIC alarms raised Default value 68P02901W23-P 23 Feb 2004 1 5-141 GMR-01 . The eac_mode parameter must be enabled.cic_unblock_thresh Chapter 5: CM database parameters cic_unblock_thresh {4415} Description The cic_unblock_thresh parameter specifies the threshold for unblocking Circuit Identity Codes (CICs) according to the availability of idle Aters. An AXCDR device cannot be in enhanced auto-connect mode if CIC validation is disabled. Syntax Change command strings modify_value 0 cic_unblock_thresh <value> AXCDR <axcdr_id> equip 0 AXCDR 5-142 GMR-01 68P02901W23-P 23 Feb 2004 . The AMR Enhanced Capacity feature must be unrestricted. The cic_block_thresh parameter must be less than the cic_unblock_thresh parameter except when both parameters are 0. Type A (no operator actions) Supported by OMC-R GUI Yes Cell description required No Dependencies This parameter can be modified inside and outside sysgen mode. • EAC mode. the user is prompted for the following parameters: • CIC blocking threshold. the user is prompted for following parameters: • device ID. 5-143 GMR-01 . • CIC validation. Display command string disp_equipment 0 AXCDR <axcdr_id> Values Value type Integer Valid range 11 to 255 Default value 0 68P02901W23-P 23 Feb 2004 Disables this parameter. When eac_mode is enabled.Technical Description BSS Command Reference cic_unblock_thresh After entering the equip AXCDR command. • CIC unblocking threshold. 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. Syntax Change command string modify_value <location> cic_validation <value> AXCDR <axcdr_id> Display command string disp_equipment <location> AXCDR <axcdr_id> Values Value type Boolean Valid range no or yes Default value no Disabled yes Enabled None 5-144 GMR-01 68P02901W23-P 23 Feb 2004 . cycle (reset) the BSC to re-initialize all BSC mapping. (2) After executing the modify_value command. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required No Dependencies The cic_validation parameter should be enabled or disabled by one of the following methods: (1) In Sysgen mode (by updating the database through DataGen or by using the sysgen_on command at the MMI). This message generates when the Cipher Mode Command message from the MSC specifies ciphering that the BSS or MS cannot perform. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required No Dependencies This parameter only applies to the BSC. 5-145 GMR-01 .08 This is a Motorola defined parameter.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. Syntax Change command string chg_element ciph_mode_rej_allowed <value> 0 Display command string disp_element ciph_mode_rej_allowed 0 Values Value type Boolean Valid range 0 or 1 Default value 0 Disabled 1 Enabled 0 References GSM specification 68P02901W23-P 23 Feb 2004 TS GSM 08. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required No Dependencies None Syntax Change command string chg_element clk_src_fail_reset_period <value> <location> Display command string disp_element clk_src_fail_reset_period <location> Values Value type Integer (hours) Valid range 1 to 255 Default value 24 5-146 GMR-01 68P02901W23-P 23 Feb 2004 .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. the MMS with the lowest OOS count is selected. At the end of the reset period. The OOS counts are used in the selection process for an MMS as a reference clock for GCLK synchronization. all of the MMS OOS counts are reset to zero. If several MMSs have the same value assigned to the mms_priority parameter. A cell cannot be coincident to itself. Syntax Change command string chg_cell_element coincident_cell <value> <cell_desc> The system prompts for the cell number for the coincident_cell. If coincident_mb is set to 1 or 2. If coincident_mb is set to 2. the command is rejected. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required Yes Dependencies This parameter may only be changed if the Coincident MultiBand Handover option is unrestricted. and the bsic settings must be the same. both cells must be at the same site.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. the cells must be neighbours of each other. 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. Display command strings disp_cell <cell_desc> ["full"] disp_element coincident_cell <location> <cell_desc> 68P02901W23-P 23 Feb 2004 5-147 GMR-01 . both cells must be SACCH neighbours of each other. coincident_cell Chapter 5: CM database parameters Values Value type Integer Valid range The GSM Cell ID number Default value None 5-148 GMR-01 68P02901W23-P 23 Feb 2004 . If a coincident cell has not been selected. both cells must be SACCH neighbours of each other.Technical Description BSS Command Reference coincident_mb coincident_mb Description The coincident_mb parameter specifies the ability of a BTS to execute the Coincident MultiBand Handover option. If coincident_mb is set to 2. the value of coincident_mb must equal 0. Type A (no operator actions) Supported by OMC-R GUI Yes Cell description required Yes Dependencies This parameter may only be changed if the Coincident MultiBand Handover option is enabled. and the coincident_mb to 0 at the new cell. both cells must be at the same site. The copy_cell command sets the coincident cell to an invalid value. This parameter must be disabled when inner_zone_alg is set to indicate Dual Band Cells. If all is entered for the del_neighbor command for a BTS at which the Coincident MultiBand Handover option is enabled. A cell cannot be coincident to itself. If coincident_mb is set to 1 or 2. the command is rejected. 68P02901W23-P 23 Feb 2004 5-149 GMR-01 . Syntax Change command string chg_cell_element coincident_mb <value> <cell_desc> The system prompts for the cell number for the coincident_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. the cells must be neighbours of each other. and contains any coincident cells. and the bsic settings must be the same. coincident_mb Chapter 5: CM database parameters Display command strings disp_cell <cell_desc> ["full"] disp_element coincident_mb <location> <cell_desc> Values Value type Integer Valid range 0 to 3 Default value 0 Coincident Multiband is disabled at the cell. but for inter BSC handovers the call is targeted at the primary cell. 0 5-150 GMR-01 68P02901W23-P 23 Feb 2004 . 2 Coincident cell handovers and coincident cell redirections are enabled. 1 Coincident cell handovers are enabled. 3 Intra BSC handovers behave the same as when coincident_mb=2. Syntax Change command strings 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.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. Type A (no operator actions) Supported by OMC-R GUI Yes Cell description required Yes Dependencies This parameter may only be changed if the Coincident MultiBand Handover option is enabled. See Prompt field values in the description of "chg_cell_element" on page 2-77. The system uses the coincident_offset value when a handover from a MultiBand MS is based on the receive level for the serving cell. • The low signal threshold. Display command string disp_element coincident_offset <location> <cell_desc> Values Value type Integer (dB) Valid range -63 to 63 Default value 0 68P02901W23-P 23 Feb 2004 5-151 GMR-01 . If this parameter is not enabled. This parameter only applies to the BSC. the system generates an alarm instead of sending a message to the MSC.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. Syntax Change command string chg_element confusion_msg_allowed <value> 0 Display command string disp_element confusion_msg_allowed 0 Values Value type Boolean Valid range 0 or 1 Default value 0 Disabled 1 Enabled 0 5-152 GMR-01 68P02901W23-P 23 Feb 2004 . Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required No Dependencies This parameter does not apply to RXCDR sites. Technical Description BSS Command Reference confusion_msg_allowed References GSM specification 68P02901W23-P 23 Feb 2004 TS GSM 8.08 This is a Motorola defined parameter. 5-153 GMR-01 . 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. Target cells that are in the process of Congestion Relief may become available for handovers more quickly than those that are not. Type A (no operator actions) Supported by OMC-R GUI Yes Cell number required Yes Dependencies The parameter can be set only if the Congestion Relief feature is unrestricted. 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. Syntax Change command strings chg_element congest_at_source <value> <location> <cell_desc> chg_cell_element congest_at_source <value> <cell_desc> Display command string disp_element congest_at_source <location> <cell_desc> Values Value type Boolean Valid range 0 or 1 5-154 GMR-01 68P02901W23-P 23 Feb 2004 . 1 The source cell immediately retries target cells which were in the process of congestion relief. 0 Refer to the congest_at_target parameter to see when a target cell performs congestion relief procedures. 68P02901W23-P 23 Feb 2004 5-155 GMR-01 .Technical Description BSS Command Reference Default value congest_at_source 0 The source cell treats all target cells equally as candidates for imperative handovers. Syntax Change command strings chg_element congest_at_target <value> <location> <cell_desc> chg_cell_element congest_at_target <value> <cell_desc> Display command string disp_element congest_at_target <location> <cell_desc> Values Value type Boolean Valid range 0 or 1 Default value 0 The system takes no action if the Cell rejects a handover request. 0 5-156 GMR-01 68P02901W23-P 23 Feb 2004 . Type A (no operator actions) Supported by OMC-R GUI Yes Cell number required Yes Dependencies The parameter can be set only if the Congestion Relief feature is unrestricted.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. 1 The system invokes Congestion Relief procedures if this Cell rejects a handover request. Syntax Change command string modify_neighbor <source_cell_id> <neighbor_cell_id> congest_ho_margin <value> Display command string disp_neighbor congest_ho_margin Values Value type Integer (each step equals 1 dB) Valid range -63 to 63 Default value None 68P02901W23-P 23 Feb 2004 5-157 GMR-01 .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. set the congestion handover margin to the maximum value. this parameter value should be less that the value of the handover margin(s). To disable congestion handovers to this neighbour. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required No 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. 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. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required No Dependencies None Syntax Change command string chg_element cp_option_reset_ckt <value> <location> Display command string disp_element cp_option_reset_ckt <location> Values Value type Boolean Valid range 0 or 1 Default value 0 Disabled 1 Enabled 0 5-158 GMR-01 68P02901W23-P 23 Feb 2004 . Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required No Dependencies None Syntax Change command string chg_element cp_option_rr_status <value> <location> Display command string disp_element cp_option_rr_status <location> Values Value type Boolean Valid range 0 or 1 Default value 68P02901W23-P 23 Feb 2004 0 Disabled 1 Enabled 0 5-159 GMR-01 . If this is enabled. the BSS can generate the 4.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.08 radio resource status message to the MS. 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 Change command string chg_element cr_calling <value> 0 Display command string disp_element cr_calling 0 Values Value type Boolean Valid range 0 or 1 Default value 0 Disabled 1 Enabled 0 5-160 GMR-01 68P02901W23-P 23 Feb 2004 . Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required No Dependencies This parameter only applies to the BSC. Type A (no operator actions) Supported by OMC-R GUI Yes Cell description required No Dependencies ct_flow_control_hi_level must be greater than ct_flow_control_lo_level plus 20. (This level is not used to disable flow control. When this limit is reached. the BSS parameter ct_flow_control_bss_enabled is set to 1.) Setting this parameter to 100 disables flow control. Syntax Change command string chg_element ct_flow_control_hi_level <value> <location> Display command string disp_element ct_flow_control_hi_level <location> Values Value type Integer Valid range 20 to 100 Default value 60 68P02901W23-P 23 Feb 2004 5-161 GMR-01 .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. Syntax Change command string chg_element ct_flow_control_lo_level <value> <location> Display command string disp_element ct_flow_control_lo_level <location> Values Value type Integer Valid range 0 to 80 Default value 20 5-162 GMR-01 68P02901W23-P 23 Feb 2004 . the BSS parameter ct_flow_control_bss_enabled is set to 0.) Type A (no operator actions) Supported by OMC-R GUI Yes Cell description required No Dependencies ct_flow_control_lo_level must be less than ct_flow_control_hi_level minus 20.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. (This level is not used to disable flow control. When this limit is reached. 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. 1 MSC traces are not allowed while flow is restricted. Type A (no operator actions) Supported by OMC-R GUI Yes Cell description required No Dependencies None Syntax Change command string chg_element ct_flow_control_msc_trace <value> <location> Display command string disp_element ct_flow_control_msc_trace <location> Values Value type Integer Valid range 0 or 1 Default value 68P02901W23-P 23 Feb 2004 0 MSC traces are allowed while flow is restricted. 0 5-163 GMR-01 . BSS software processes using this parameter are immediately notified when the change is made. Syntax Change command string chg_cell_element c31_hyst <value> <cell-desc> chg_cell_element <location> c31_hyst <value> all chg_element c31_hyst <value> <location> <cell_desc> Display command string disp_cell <cell_desc> "full" disp_element c31_hyst <location> <cell-desc> disp_element c31_hyst <location> all 5-164 GMR-01 68P02901W23-P 23 Feb 2004 . Type A (No operator actions required) Supported by OMC-R GUI Yes Cell numbers required Yes Dependencies The PBCCH/PCCCH optional feature must be unrestricted.c31_hyst Chapter 5: CM database parameters c31_hyst {3723} Description The c31_hyst parameter is a flag specifying whether or not hysteresis is applied to C31. Technical Description BSS Command Reference c31_hyst Values Value type Integer Valid range 0 or 1 Default value 68P02901W23-P 23 Feb 2004 0 Hysteresis not applied 1 Hysteresis applied 0 5-165 GMR-01 . c32_qual Chapter 5: CM database parameters c32_qual {3723} Description The c32_qual parameter is a flag specifying whether the exception rule is allowed with the gprs_reselect_offset parameter at a cell. Type A (No operator actions required) Supported by OMC-R GUI Yes Cell numbers required Yes Dependencies The PBCCH/PCCCH optional feature must be unrestricted. Syntax Change command string chg_cell_element c32_qual <value> <cell-desc> chg_cell_element <location> c32_qual <value> all chg_element c32_qual <value> <location> <cell_desc> Display command string disp_cell <cell_desc> "full" disp_element c32_qual <location> <cell-desc> disp_element c32_qual <location> all 5-166 GMR-01 68P02901W23-P 23 Feb 2004 . BSS software processes using this parameter are immediately notified when the change is made. Technical Description BSS Command Reference c32_qual Values Value type Integer Valid range 0 or 1 Default value 68P02901W23-P 23 Feb 2004 0 Exception not allowed 1 Exception allowed 0 5-167 GMR-01 . specific rxqual thresholds may be configured to trigger data call handovers. the system uses the rxqual data parameters set with the chg_cell_element command. Therefore. 5-168 GMR-01 68P02901W23-P 23 Feb 2004 . Type A (no operator actions) Supported by OMC-R GUI Yes Cell description required Yes Dependencies alt_qual_proc Syntax Change command strings chg_cell_element data_qual_enabled <value> <cell_desc> 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-408. A data call is one that involves the transmission of computer data.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. If the data_qual_enabled parameter is enabled and a data call is in progress. the data_qual_enabled parameter takes precedence in conditions where both apply. data transmission in a hopping call. that is. such as a modem-to-modem call. These types of calls are very sensitive to bit errors. • "l_rxqual_dl_p" on page 5-420. as listed in Syntax below. • "l_rxqual_ul_h" on page 5-432. 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. Display command strings disp_cell <cell_desc> ["full"] disp_element data_qual_enabled <location> <cell_desc> Values Value type Integer Valid range 0 or 1 Default value 68P02901W23-P 23 Feb 2004 0 Disabled 1 Enabled 0 5-169 GMR-01 .Technical Description BSS Command Reference • data_qual_enabled "l_rxqual_ul_p" on page 5-444. Syntax Add/Change command strings chg_element ddtr_ctrl_enabled <value> <location> Display command strings disp_element ddtr_ctrl_enabled <location> Values Value type Boolean Valid range 0 or 1 Default value 0 Disabled 1 Enabled 0 (disabled) 5-170 GMR-01 68P02901W23-P 23 Feb 2004 .ddtr_ctrl_enabled Chapter 5: CM database parameters ddtr_ctrl_enabled {4445} 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 Supported by OMC-R GUI Yes Cell description required No Dependencies None Operator actions None. This parameter may not be changed to a bin which does not contain valid handover algorithm data.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. Type A (no operator actions) Supported by OMC-R GUI Yes Cell description required Yes Dependencies rxlev_dl_ho Syntax Add/Change command strings add_cell <gsm_cell_id> <location> chg_element decision_1_dl_rxlev_av_h <value> <location> <cell_desc> chg_cell_element decision_1_dl_rxlev_av_h <value> <cell_desc> Display command strings disp_cell <cell_desc> ["full"] disp_element decision_1_dl_rxlev_av_h <location> <cell_desc> Values Value type Integer Valid range 0 or 1 Default value 0 68P02901W23-P 23 Feb 2004 5-171 GMR-01 . Type A (no operator actions) Supported by OMC-R GUI Yes Cell description required Yes Dependencies rxlev_dl_ho Syntax Add/Change command strings add_cell <gsm_cell_id> <location> chg_element decision_1_dl_rxlev_av_ih <value> <location> <cell_desc> chg_cell_element decision_1_dl_rxlev_av_ih <value> <cell_desc> Display command strings disp_cell <cell_desc> ["full"] disp_element decision_1_dl_rxlev_av_ih <location> <cell_desc> Values Value type Integer Valid range 0 to 1 Default value 0 5-172 GMR-01 68P02901W23-P 23 Feb 2004 . This parameter may not be changed to a bin which does not contain valid handover data.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. Type A (no operator actions) Supported by OMC-R GUI Yes Cell description required Yes Dependencies rxqual_dl_pc Syntax Add/Change command strings add_cell <gsm_cell_id> <location> chg_element decision_1_dl_rxqual_av_p <value> <location> <cell_desc> chg_cell_element decision_1_rxqual_av_p <value> <cell_desc> Display command strings disp_cell <cell_desc> ["full"] disp_element decision_1_dl_rxqual_av_p <location> <cell_desc> Values Value type Integer Valid range 0 to 1 Default value 0 68P02901W23-P 23 Feb 2004 5-173 GMR-01 . This parameter may not be changed to a bin which does not contain valid power control data.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). 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). This parameter may not be changed to a bin which does not contain valid handover data. Type A (no operator actions) Supported by OMC-R GUI Yes Cell description required Yes Dependencies rxqual_dl_ho Syntax Add/Change command strings add_cell <gsm_cell_id> <location> chg_element decision_1_dl_rxqual_av_h <value> <location> <cell_desc> chg_cell_element decision_1_dl_rxqual_av_h <value> <cell_desc> Display command strings disp_cell <cell_desc> ["full"] disp_element decision_1_dl_rxqual_av_h <location> <cell_desc> Values Value type Integer Valid range 0 to 1 Default value 0 5-174 GMR-01 68P02901W23-P 23 Feb 2004 . Type A (no operator actions) Supported by OMC-R GUI Yes Cell description required Yes Dependencies rxqual_dl_pc Syntax Add/Change command strings add_cell <gsm_cell_id> <location> chg_element decision_1_dl_rxqual_av_p <value> <location> <cell_desc> chg_cell_element decision_1_rxqual_av_p <value> <cell_desc> Display command strings disp_cell <cell_desc> ["full"] disp_element decision_1_dl_rxqual_av_p <location> <cell_desc> Values Value type Integer Valid range 0 to 1 Default value 0 68P02901W23-P 23 Feb 2004 5-175 GMR-01 .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. N1 is the number of samples in the threshold comparison process used in decisions to increase uplink and downlink power.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. Type A (no operator actions) Supported by OMC-R GUI Yes Cell description required Yes Dependencies N1 must be greater than or equal to P1. 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. Syntax Add/Change command strings add_cell <gsm_cell_id> <location> chg_element decision_1_n1 <value> <location> <cell_desc> chg_cell_element decision_1_n1 <value> <cell_desc> chg_cell_element decision_1_p1 <value> <cell_desc> Display command strings disp_cell <cell_desc> ["full"] disp_element decision_1_n1 <location> <cell_desc> disp_element decision_1_p1 <location> <cell_desc> 5-176 GMR-01 68P02901W23-P 23 Feb 2004 . 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. P1 is the number of samples in the processed measurement (process) relative to the (averaging) algorithm in place. Appendix A .5.2. P1 GSM specification 5.20 .8. and Table 1 12.3.26: Signal Strength Serving Cell 68P02901W23-P 23 Feb 2004 5-177 GMR-01 .08 .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.2. Type A (no operator actions) Supported by OMC-R GUI Yes Cell description required Yes Dependencies N2 must be greater than or equal to P2. N2 is the number of samples in the threshold comparison process used in decisions to decrease uplink and downlink power. Syntax Add/Change command strings add_cell <gsm_cell_id> <location> chg_element decision_1_n2 <value> <location> <cell_desc> chg_cell_element decision_1_n2 <value> <cell_desc> chg_element decision_1_p2 <value> <location> <cell_desc> chg_cell_element decision_1_p2 <value> <cell_desc> Display command strings disp_cell <cell_desc> ["full"] disp_element decision_1_n2 <location> <cell_desc> disp_element decision_1_p2 <location> <cell_desc> 5-178 GMR-01 68P02901W23-P 23 Feb 2004 . 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).decision_1_n2/decision_1_p2 Chapter 5: CM database parameters decision_1_n2/decision_1_p2 Description These parameters specify N2 and P2 in the decision algorithm used in the BSS. P2 is the number of samples in the processed measurement (process) relative to the (averaging) algorithm in place. N2 must be less than or equal to the hreqt value set using chg_act_alg_data command for rxlev_dl_pc and rxlev_ul_pc. the corresponding uplink or downlink transmit power (txpwr) must be decreased. 08 .3.2.2. P2 GSM specification 5.Technical Description BSS Command Reference decision_1_n2/decision_1_p2 Values Value type Integer (1 step = 1 peg) Valid range 1 to 31 Default value 1 References GSM parameter N2.26: Signal Strength Serving Cell 68P02901W23-P 23 Feb 2004 5-179 GMR-01 . and Table 1 12.8.5.20 .Appendix A . 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. Syntax Add/Change command strings add_cell <gsm_cell_id> <location> chg_element decision_1_n3 <value> <location> <cell_desc> chg_cell_element decision_1_n3 <value> <cell_desc> chg_element decision_1_p3 <value> <location> <cell_desc> chg_cell_element decision_1_p3 <value> <cell_desc> Display command strings disp_cell <cell_desc> ["full"] disp_element decision_1_n3 <location> <cell_desc> disp_element decision_1_p3 <location> <cell_desc> 5-180 GMR-01 68P02901W23-P 23 Feb 2004 . N3 must be less than or equal to the hreqt value set using chg_act_alg_data command for rxqual_dl_pc and rxqual_ul_pc.decision_1_n3/decision_1_p3 Chapter 5: CM database parameters decision_1_n3/decision_1_p3 Description These parameters specify N3 and P3 in the decision algorithm used in the BSS. Type A (no operator actions) Supported by OMC-R GUI Yes Cell description required Yes Dependencies N3 must be greater than or equal to P3. the corresponding uplink or downlink transmit power (txpwr) must be increased. 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). 5.8.Appendix A . P3 GSM specification 5.2.25: Signal Quality Serving Cell 68P02901W23-P 23 Feb 2004 5-181 GMR-01 .3.08 .2.Technical Description BSS Command Reference decision_1_n3/decision_1_p3 Values Value type Integer (1 step = 1 peg) Valid range 1 to 31 Default value 1 References GSM parameter N3. and Table 1 12.20 . Type A (no operator actions) Supported by OMC-R GUI Yes Cell description required Yes Dependencies N4 must be greater than or equal to P4. the corresponding uplink or downlink transmit power (txpwr) must be decreased. 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). Syntax Add/Change command strings add_cell <gsm_cell_id> <location> chg_element decision_1_n4 <value> <location> <cell_desc> chg_cell_element decision_1_n4 <value> <cell_desc> chg_element decision_1_p4 <value> <location> <cell_desc> chg_cell_element decision_1_p4 <value> <cell_desc> Display command strings disp_cell <cell_desc> ["full"] disp_element decision_1_n4 <location> <cell_desc> disp_element decision_1_p4 <location> <cell_desc> 5-182 GMR-01 68P02901W23-P 23 Feb 2004 .decision_1_n4/decision_1_p4 Chapter 5: CM database parameters decision_1_n4/decision_1_p4 Description These parameters specify N4 and P4 in the decision algorithm used in the BSS. N4 is the number of samples in the threshold comparison process used in decisions to decrease uplink and downlink power. P4 is the number of samples in the processed measurement (process) relative to the (averaging) algorithm in place. N4 must be less than or equal to the hreqt value set using chg_act_alg_data command for rxqual_dl_pc and rxqual_ul_pc. Appendix A .25: Signal Quality Serving Cell 68P02901W23-P 23 Feb 2004 5-183 GMR-01 .3.8.08 .5.20 .Technical Description BSS Command Reference decision_1_n4/decision_1_p4 Values Value type Integer (1 step = 1 peg) Valid range 1 to 31 Default value 1 References GSM parameter N4. P4 GSM specification 5.2. and Table 1 12.2. Type A (no operator actions) Supported by OMC-R GUI Yes Cell description required Yes Dependencies N5 must be greater than or equal to P5. N5 must be less than or equal to the hreqt value set using chg_act_alg_data command for rxlev_dl_ho and rxlev_ul_ho. Syntax Add/Change command strings add_cell <gsm_cell_id> <location> chg_element decision_1_n5 <value> <location> <cell_desc> chg_cell_element decision_1_n5 <value> <cell_desc> chg_element decision_1_p5 <value> <location> <cell_desc> chg_cell_element decision_1_p5 <value> <cell_desc> Display command strings disp_cell <cell_desc> ["full"] disp_element decision_1_n5 <location> <cell_desc> disp_element decision_1_p5 <location> <cell_desc> 5-184 GMR-01 68P02901W23-P 23 Feb 2004 . 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).decision_1_n5/decision_1_p5 Chapter 5: CM database parameters decision_1_n5/decision_1_p5 Description These parameters specify N5 and P5 in the decision algorithm used in the BSS. P5 is the number of samples in the processed measurement (process) relative to the (averaging) algorithm in place. N5 is the number of samples in the threshold comparison process used in handover decisions. a handover might be required. 2.20 .19: Handover Control Thresholds 68P02901W23-P 23 Feb 2004 5-185 GMR-01 .Appendix A . and Table 1 12.08 .2.Technical Description BSS Command Reference decision_1_n5/decision_1_p5 Values Value type Integer (1 step = 1 peg) Valid range 1 to 31 Default value 1 References GSM parameter N5. P5 GSM specification 5.8.3.5. 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). N6 is the number of samples in the threshold comparison process used in handover decisions. a handover may be needed. Syntax Add/Change command strings add_cell <gsm_cell_id> <location> chg_element decision_1_n6 <value> <location> <cell_desc> chg_cell_element decision_1_n6 <value> <cell_desc> chg_element decision_1_p6 <value> <location> <cell_desc> chg_cell_element decision_1_p6 <value> <cell_desc> Display command strings disp_cell <cell_desc> ["full"] disp_element decision_1_n6 <location> <cell_desc> disp_element decision_1_p6 <location> <cell_desc> 5-186 GMR-01 68P02901W23-P 23 Feb 2004 . Type A (no operator actions) Supported by OMC-R GUI Yes Cell description required Yes Dependencies N6 must be greater than or equal to P6. N6 must be less than or equal to the hreqt value set using chg_act_alg_data command for rxqual_dl_ho and rxqual_ul_ho.decision_1_n6/decision_1_p6 Chapter 5: CM database parameters decision_1_n6/decision_1_p6 Description These parameters specify N6 and P6 in the decision algorithm used in the BSS. Technical Description BSS Command Reference decision_1_n6/decision_1_p6 Values Value type Integer (1 step = 1 peg) Valid range 1 to 31 Default value 1 References GSM parameter N6.8.19: Handover Control Thresholds 68P02901W23-P 23 Feb 2004 5-187 GMR-01 . and Table 1 12.3.2. P6 GSM specification 5.5.08 .2.Appendix A .20 . N7 must be less than or equal to the hreqt value set using chg_act_alg_data command for rxlev_dl_ho and rxlev_ul_ho. an internal handover might be required if rxqual_ul/dl is also greater than l_rxqual_ul/dl_h.decision_1_n7/decision_1_p7 Chapter 5: CM database parameters decision_1_n7/decision_1_p7 Description These parameters specify N7 and P7 in the decision algorithm used in the BSS. P7 is the number of samples in the processed measurement (process) relative to the (averaging) algorithm in place. N7 is the number of samples in the threshold comparison process. Type A (no operator actions) Supported by OMC-R GUI Yes Cell description required Yes Dependencies N7 must be greater than or equal to P7. Syntax Add/Change command strings add_cell <gsm_cell_id> <location> chg_element decision_1_n7 <value> <location> <cell_desc> chg_cell_element decision_1_n7 <value> <cell_desc> chg_element decision_1_p7 <value> <location> <cell_desc> chg_cell_element decision_1_p7 <value> <cell_desc> Display command strings disp_cell <cell_desc> ["full"] disp_element decision_1_n7 <location> <cell_desc> disp_element decision_1_p7 <location> <cell_desc> 5-188 GMR-01 68P02901W23-P 23 Feb 2004 . 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). Technical Description BSS Command Reference decision_1_n7/decision_1_p7 Values Value type Integer (1 step = 1 peg) Valid range 1 to 31 Default value 1 References GSM parameter N7, P7 GSM specification 5.08 - Appendix A - 3.2, and Table 1 12.20 - 5.2.8.19: Handover Control Thresholds 68P02901W23-P 23 Feb 2004 5-189 GMR-01 decision_1_n8/decision_1_p8 Chapter 5: CM database parameters decision_1_n8/decision_1_p8 Description These parameters specify N8 and P8 in the decision algorithm used in the BSS. N8 is the number of samples in the threshold comparison process. P8 is the number of samples in the processed measurement (process) relative to the (averaging) algorithm in place. If at least P8 averages out of N8 averages are greater than RSS handover threshold ms_range_max, a handover might be required due to distance. Type A (no operator actions) Supported by OMC-R GUI Yes Cell description required Yes Dependencies N8 must be greater than or equal to P8. N8 must be less than or equal to the Hreqt value set for rel_tim_adv. Syntax Add/Change command strings add_cell <gsm_cell_id> <location> chg_element decision_1_n8 <value> <location> <cell_desc> chg_cell_element decision_1_n8 <value> <cell_desc> chg_element decision_1_p8 <value> <location> <cell_desc> chg_cell_element decision_1_p8 <value> <cell_desc> Display command strings disp_cell <cell_desc> ["full"] disp_element decision_1_n8 <location> <cell_desc> disp_element decision_1_p8 <location> <cell_desc> 5-190 GMR-01 68P02901W23-P 23 Feb 2004 Technical Description BSS Command Reference decision_1_n8/decision_1_p8 Values Value type Integer (1 step = 1 peg) Valid range 1 to 31 Default value 1 References GSM parameter N8, P8 GSM specification 5.08 - Appendix A - 3.2, and Table 1 12.20 - 5.2.8.21: ms Distance Average 68P02901W23-P 23 Feb 2004 5-191 GMR-01 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. This parameter may not be changed to a bin which does not contain valid handover data. Type A (no operator actions) Supported by OMC-R GUI Yes Cell description required Yes Dependencies surround_cell Syntax Add/Change command strings add_cell <gsm_cell_id> <location> chg_element decision_1_ncell_rxlev_av_h_calc <value> <location> <cell_desc> chg_cell_element decision_1_ncell_rxlev_av_h_calc <value> <cell_desc> Display command strings disp_cell <cell_desc> ["full"] 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-192 GMR-01 68P02901W23-P 23 Feb 2004 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. This parameter may not be changed to a bin which does not contain valid power control data. Type A (no operator actions) Supported by OMC-R GUI Yes Cell description required Yes Dependencies None Syntax Add/Change command strings add_cell <gsm_cell_id> <location> chg_element decision_1_p_bgt_rxlev_av_h <value> <location> <cell_desc> chg_cell_element decision_1_p_bgt_rxlev_av_h <value> <cell_desc> Display command strings disp_cell <cell_desc> ["full"] 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-P 23 Feb 2004 5-193 GMR-01 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. This parameter may not be changed to a bin which does not contain valid handover data. Type A (no operator actions) Supported by OMC-R GUI Yes Cell description required Yes Dependencies rel_tim_adv Syntax Add/Change command strings add_cell <gsm_cell_id> <location> chg_element decision_1_tim_adv_av_alg <value> <location> <cell_desc> chg_cell_element decision_1_tim_adv_av_alg <value> <cell_desc> Display command strings disp_cell <cell_desc> ["full"] disp_element decision_1_tim_adv_av_alg <location> <cell_desc> Values Value type Integer Valid range 0 or 1 Default value 0 5-194 GMR-01 68P02901W23-P 23 Feb 2004 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. This parameter may not be changed to a bin which does not contain valid handover data. Type A (no operator actions) Supported by OMC-R GUI Yes Cell description required Yes Dependencies rxlev_ul_ho Syntax Add/Change command strings add_cell <gsm_cell_id> <location> chg_element decision_1_ul_rxlev_av_h <value> <location> <cell_desc> chg_cell_element decision_1_ul_rxlev_av_h <value> <cell_desc> Display command strings disp_cell <cell_desc> ["full"] disp_element decision_1_ul_rxlev_av_h <location> <cell_desc> Values Value type Integer Valid range 0 or 1 Default value 0 68P02901W23-P 23 Feb 2004 5-195 GMR-01 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. This parameter may not be changed to a bin which does not contain valid handover data. Type A (no operator actions) Supported by OMC-R GUI Yes Cell description required Yes Dependencies rxlev_ul_ho Syntax Add/Change command strings add_cell <gsm_cell_id> <location> chg_element decision_1_ul_rxlev_av_ih <value> <location> <cell_desc> chg_cell_element decision_1_ul_rxlev_av_ih <value> <cell_desc> Display command strings disp_cell <cell_desc> ["full"] disp_element decision_1_ul_rxlev_av_ih <location> <cell_desc> Values Value type Integer Valid range 0 or 1 Default value 0 5-196 GMR-01 68P02901W23-P 23 Feb 2004 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. This parameter may not be changed to a bin which does not contain valid power control data. Type A (no operator actions) Supported by OMC-R GUI Yes Cell description required Yes Dependencies rxlev_ul_pc Syntax Add/Change command strings add_cell <gsm_cell_id> <location> chg_element decision_1_ul_rxlev_av_p <value> <location> <cell_desc> chg_cell_element decision_1_ul_rxlev_av_p <value> <cell_desc> Display command strings disp_cell <cell_desc> ["full"] disp_element decision_1_ul_rxlev_av_p <location> <cell_desc> Values Value type Integer Valid range 0 or 1 Default value 0 68P02901W23-P 23 Feb 2004 5-197 GMR-01 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. This parameter may not be changed to a bin which does not contain valid handover data. Type A (no operator actions) Supported by OMC-R GUI Yes Cell description required Yes Dependencies rxqual_ul_ho Syntax Add/Change command strings add_cell <gsm_cell_id> <location> chg_element decision_1_ul_rxqual_av_h <value> <location> <cell_desc> chg_cell_element decision_1_ul_rxqual_av_h <value> <cell_desc> Display command strings disp_cell <cell_desc> ["full"] disp_element decision_1_ul_rxqual_av_h <location> <cell_desc> Values Value type Integer Valid range 0 or 1 Default value 0 5-198 GMR-01 68P02901W23-P 23 Feb 2004 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. This parameter may not be changed to a bin which does not contain valid power control data. Type A (no operator actions) Supported by OMC-R GUI Yes Cell description required Yes Dependencies rxqual_ul_pc Syntax Add/Change command strings add_cell <gsm_cell_id> <location> chg_element decision_1_ul_rxqual_av_p <value> <location> <cell_desc> chg_cell_element decision_1_ul_rxqual_av_p <value> <cell_desc> Display command strings disp_cell <cell_desc> ["full"] disp_element decision_1_ul_rxqual_av_p <location> <cell_desc> Values Value type Integer Valid range 0 or 1 Default value 0 68P02901W23-P 23 Feb 2004 5-199 GMR-01 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. Type A (no operator actions) Supported by OMC-R GUI Yes Cell description required Yes Dependencies None Syntax Add/Change command strings add_cell <gsm_cell_id> <location> chg_element decision_alg_type <value> <location> <cell_desc> chg_cell_element decision_alg_type <value> <cell_desc> Display command strings disp_cell <cell_desc> ["full"] 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-200 GMR-01 68P02901W23-P 23 Feb 2004 Technical Description BSS Command Reference 1 Default value 68P02901W23-P 23 Feb 2004 decision_alg_type Power control algorithm number 2 (enables the use of p_con_ack timers) 0 5-201 GMR-01 delay_ul_rel_dur Chapter 5: CM database parameters delay_ul_rel_dur {4445} Description The delay_ul_rel_dur parameter is used to configure the delayed uplink Temporary Block Flow (TBF) release duration. The delay_ul_rel_dur parameter is configurable on a per BSS basis. Type A Supported by OMC-R GUI Yes Cell description required No Dependencies GPRS must be unrestricted. Operator actions None Syntax Add/Change command strings chg_element delay_ul_rel_dur <value> <location> Display command strings disp_element delay_ul_rel_dur <location> Values Value type Integer 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-202 GMR-01 68P02901W23-P 23 Feb 2004 Technical Description BSS Command Reference direct_inner_zone_threshold direct_inner_zone_threshold Description The direct_inner_zone_threshold parameter specifies the rxlev threshold that must be exceeded by the MS reported rxlev for the call to qualify for accelerated allocation of an inner zone resource. Type A (no operator action) Supported by OMC-R GUI Yes Cell description required Yes Dependencies The Concentric Cells feature must be enabled in order to set this parameter. Operator actions None Syntax Change command strings chg_element direct_inner_zone_threshold <value> <location> <cell_desc> chg_cell_element direct_inner_zone_threshold <value> <cell_desc> Display command string disp_element direct_inner_zone_threshold <location> <cell_desc> Values Value type Integer Valid range 0 to 63 Default value 63 68P02901W23-P 23 Feb 2004 5-203 GMR-01 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. Type A (no operator actions) Supported by OMC-R GUI Yes Cell description required Yes Dependencies None Syntax Change command strings chg_element disuse_cnt_hreqave <value> <location> <cell_desc> chg_cell_element disuse_cnt_hreqave <value> <location> <cell_desc> Display command string disp_element disuse_cnt_hreqave <location> <cell_desc> Values Value type Boolean Valid range 0 or 1 Default value 0 Disabled 1 Enabled 0 5-204 GMR-01 68P02901W23-P 23 Feb 2004 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. Type A (no operator actions) Supported by OMC-R GUI Yes Cell description required No Dependencies The volume_control_type parameter controls the dl_audio_lev_offset application. If volume_control_type = 1, then the dl_audio_lev_offset parameter only applies to sites equipped with GDP boards. The GDP firmware controls the volume level by converting the audio level bits for the entered offset. Syntax Change command string chg_element dl_audi_lev_offset <value> <location> Display command string disp_element dl_audio_lev_offset 0 68P02901W23-P 23 Feb 2004 5-205 GMR-01 dl_audio_lev_offset Chapter 5: CM database parameters Values Value type Integer (1 Step = 1 dB) Valid range -15 to +15 Default value 0 5-206 GMR-01 68P02901W23-P 23 Feb 2004 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. Type A (no operator actions) Supported by OMC-R GUI Yes Cell description required Yes Dependencies The dl_dtx_voice_data parameter affects speech only if dnlk_vad_dtx is enabled. Syntax Change command strings chg_element dl_dtx_voice_data <value> <location> <cell_desc> chg_cell_element dl_dtx_voice_data <value> <cell_desc> Display command string disp_element dl_dtx_voice_data <location> <cell_desc> Values Value type Value range Default value 68P02901W23-P 23 Feb 2004 Integer 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 0 5-207 GMR-01 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). Type A (no operator actions) Supported by OMC-R GUI Yes Cell description required Yes Dependencies None Syntax Add/Change command strings add_cell <gsm_cell_id> <location> chg_element dl_rxlev_ho_allowed <value> <location> <cell_desc> chg_cell_element dl_rxlev_ho_allowed <value> <cell_desc> Display command strings disp_cell <cell_desc> ["full"] disp_element dl_rxlev_ho_allowed <location> <cell_desc> Values Value type Boolean Valid range 0 or 1 0 1 Default value disabled enabled 1 5-208 GMR-01 68P02901W23-P 23 Feb 2004 Technical Description BSS Command Reference dl_rxlev_ho_allowed References Internal name EN_RXLEV_HO This is a Motorola parameter. 68P02901W23-P 23 Feb 2004 5-209 GMR-01 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). Type A (no operator actions) Supported by OMC-R GUI Yes Cell description required Yes Dependencies None Syntax Add/Change command strings add_cell <gsm_cell_id> <location> chg_element dl_rxqual_ho_allowed <value> <location> <cell_desc> chg_cell_element dl_rxqual_ho_allowed <value> <cell_desc> Display command strings disp_cell <cell_desc> ["full"] disp_element dl_rxqual_ho_allowed <location> <cell_desc> Values Value type Boolean Valid range 0 or 1 0 1 Default value disabled enabled 1 5-210 GMR-01 68P02901W23-P 23 Feb 2004 Technical Description BSS Command Reference dl_rxqual_ho_allowed References Internal name EN_RXQUAL_HO This is a Motorola parameter. 68P02901W23-P 23 Feb 2004 5-211 GMR-01 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. Type A (no operator actions) Supported by OMC-R GUI Yes Cell description required No Dependencies Must be executed in SYSGEN mode. This parameter can be displayed or changed only at sites where transcoding is enabled (RXCDR or local transcoding BSC). When enabled, the dnlk_vad_dtx parameter makes the dl_dtx_voice_data parameter alive. Syntax Change command string chg_element dnlk_vad_dtx <value> <location> Display command string disp_element dnlk_vad_dtx <location> Values Value type Boolean Valid range 0 or 1 0 Enabled 5-212 GMR-01 68P02901W23-P 23 Feb 2004 Technical Description BSS Command Reference dnlk_vad_dtx 1 Default value 68P02901W23-P 23 Feb 2004 Disabled None 5-213 GMR-01 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-561) and ss7_mode (see "ss7_mode" on page 5-741) variables and compares them to the value for ss7_mode. If the ranges are not compatible, the system rejects the changes and displays the following message: COMMAND ACCEPTED: WARNING: When opc equals dpc, communication with MSC is impossible. Type A (no operator actions) Supported by OMC-R GUI Yes Cell description required No Dependencies This parameter is only valid at the BSC. Syntax Change command string chg_element dpc <value> <location> Display command string disp_element dpc <location> Values Value type Integer Valid range 0 to 16383 If ss7_mode = 0 (CCITT) 0 to 16777215 If ss7_mode =1 (Bellcore) Default value None 5-214 GMR-01 68P02901W23-P 23 Feb 2004 Technical Description BSS Command Reference dpc References GSM parameter DPC GSM specification CCITT Q.708 68P02901W23-P 23 Feb 2004 5-215 GMR-01 dr_allowed Chapter 5: CM database parameters dr_allowed Description The dr_allowed parameter enables or disables the Directed Retry feature. Type A (no operator actions) Supported by OMC-R GUI Yes Cell description required No Dependencies This parameter can be modified only if all the following conditions are met: • the Directed Retry feature is available, • the neighbour is placed on the SACCH list, and • the neighbour is external. Syntax Change command strings modify_neighbor <src_cell_id> <neighbor_cell_id> dr_allowed <value> Display command string disp_neighbor <src_cell_id> all Values Value type Boolean Valid range 0 or 1 Default value 0 Disabled 1 Enabled None 5-216 GMR-01 68P02901W23-P 23 Feb 2004 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. Type A (no operator actions) Supported by OMC-R GUI Yes Cell description required No Dependencies The Directed Retry feature must be unrestricted. This parameter can be changed only at the BSC. Syntax Change command string chg_element dr_chan_mode_modify <value> 0 Display command string disp_element dr_chan_mode_modify 0 Values Value type Boolean Valid range 0 or 1 Default value 68P02901W23-P 23 Feb 2004 0 Disabled 1 Enabled 0 5-217 GMR-01 dr_chan_mode_modify Chapter 5: CM database parameters References GSM specification TS GSM 08.08 ETR 09.94 This is a Motorola defined parameter. 5-218 GMR-01 68P02901W23-P 23 Feb 2004 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. Type A (no operator actions) Supported by OMC-R GUI Yes Cell description required Yes Dependencies The MSC may need to increase the timer waiting for the Assignment Complete message from the BSS when this database parameter is enabled. The BSS does not initiate an external handover due to the Directed Retry procedure if the msc_preference parameter indicates that directed retry is supported only within the BSS (not across the A-interface) when the dr_standard_congest parameter is enabled. The Directed Retry feature must be unrestricted. This parameter requires that dr_preference be enabled. Syntax Change command strings chg_element dr_ho_during_assign <value> <location> <cell_desc> chg_cell_element dr_ho_during_assign <value> <cell_desc> Display command string disp_element dr_ho_during_assign <location> <cell_desc> 68P02901W23-P 23 Feb 2004 5-219 GMR-01 dr_ho_during_assign Chapter 5: CM database parameters Values Value type Boolean Valid range 0 or 1 Default value 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. 0 References GSM specification TS GSM 08.08 This is a Motorola defined parameter. 5-220 GMR-01 68P02901W23-P 23 Feb 2004 Technical Description BSS Command Reference dr_preference dr_preference Description The dr_preference parameter enables or disables the Directed Retry procedures. Type A (no operator actions) Supported by OMC-R GUI Yes Cell description required No Dependencies dr_standard_congest dr_ho_during_assign The Directed Retry feature must be unrestricted. This parameter can only be changed at the BSC. Syntax Change command string chg_element dr_preference <value> 0 Display command string disp_element dr_preference 0 Values Value type Integer Valid range 0 or 1 Default value 68P02901W23-P 23 Feb 2004 0 Disabled 1 Enabled 0 5-221 GMR-01 dr_preference Chapter 5: CM database parameters References GSM specification TS GSM 08.08 This is a Motorola defined parameter. 5-222 GMR-01 68P02901W23-P 23 Feb 2004 Technical Description BSS Command Reference dr_standard_congest dr_standard_congest Description The dr_standard_congest parameter enables or disables the standard Directed Retry congestion procedure in a cell. The procedure initiates a handover if possible for a call needing a TCH in the case of congestion. This parameter is copied if the copy_cell command is used. Type A (no operator actions) Supported by OMC-R GUI Yes Cell description required Yes Dependencies The Directed Retry feature must be unrestricted. The dr_preference parameter must not be set to zero. The MSC may need to increase the timer waiting for the Assignment Complete message from the BSS when this database parameter is enabled. The BSS does not initiate an external handover due to the Directed Retry procedure if the msc_preference parameter indicates that directed retry is supported within the BSS (not across the A-interface) when the dr_standard_congest parameter is enabled. Syntax Change command strings chg_element dr_standard_congest <value> <location> <cell_desc> chg_cell_element dr_standard_congest <value> <cell_desc> Display command string disp_element dr_standard_congest <location> <cell_desc> Values Value type Boolean Valid range 0 or 1 0 68P02901W23-P 23 Feb 2004 Disabled 5-223 GMR-01 5-224 GMR-01 68P02901W23-P 23 Feb 2004 .08 This is a Motorola defined parameter.dr_standard_congest Chapter 5: CM database parameters 1 Default value Enabled 0 References GSM specification TS GSM 08. Enabling this feature helps to reduce interference and prolong battery life. Type A (no operator actions) Supported by OMC-R GUI Yes Cell description required Yes Dependencies None Syntax Add/Change command strings add_cell <gsm_cell_id> <location> chg_element dtx_required <value> <location> <cell_desc> chg_cell_element dtx_required <value> <cell_desc> Display command strings disp_cell <cell_desc> ["full"] disp_element dtx_required <location> <cell_desc> Values Value type Integer Valid range 0 to 2 Default value 68P02901W23-P 23 Feb 2004 0 Permitted (MS may use DTX) 1 Required (MS must use DTX) 2 Disallowed (MS must not use DTX) 2 5-225 GMR-01 .Technical Description BSS Command Reference dtx_required dtx_required Description The dtx_required parameter specifies the MS capability to use discontinuous transmission (DTX). table 10.5.08 .16 5-226 GMR-01 68P02901W23-P 23 Feb 2004 .3.22.10. figure 10.dtx_required Chapter 5: CM database parameters References GSM parameter DTX GSM specification 4.2. 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. Syntax Change command string chg_cell_element <location> dual_band_offset <value> Display command string disp_element dual_band_offset <location> <cell_desc> Values Value type Integer Valid range -63 to 63 Default value 0 68P02901W23-P 23 Feb 2004 5-227 GMR-01 . Plus. The dual_band_offset is applied to power budget handover calculations from the inner zone to cells of any frequency type. it is used to evaluate the criteria for the inter zone handovers within a cell. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required Yes Dependencies This parameter may be modified only when the Dual Band Cells feature is unrestricted. the calculation of step size can include or exclude dynamic power reduction caused by the level being above the upper level threshold. When enabled. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required Yes Dependencies None Syntax Change command strings add_cell <gsm_cell_id> <location> chg_element dyn_step_adj <value> <location> <cell_desc> chg_cell_element dyn_step_adj <value> <cell_desc> Display command strings disp_cell <cell_desc> ["full"] disp_element dyn_step_adj <location> <cell_desc> Values Value type Integer Valid range 0 to 2 Default value 0 Disabled 1 Enabled (excludes power reduction) 2 Enabled (includes power reduction) 0 5-228 GMR-01 68P02901W23-P 23 Feb 2004 .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. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required Yes Dependencies None Syntax Change command strings add_cell <gsm_cell_id> <location> chg_element dyn_step_adj_fmpr <value> <location> <cell_desc> chg_cell_element dyn_step_adj_fmpr <value> <cell_desc> Display command strings disp_cell <cell_desc> ["full"] disp_element dyn_step_adj_fmpr <location> <cell_desc> Values Value type Integer Valid range 0 to 10 Default value 10 68P02901W23-P 23 Feb 2004 5-229 GMR-01 .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. it is set at zero. 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 system will reject the command if the cell_desc equals all. The Dynamic Allocation feature must be in operation. If this total is less than zero.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 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. • 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. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required Yes Dependencies This parameter is not available unless the containing site is configured to support dynamic allocation. Syntax Change command string chg_element dynet_tchs_reserved <value> <location> <cell_desc> Display command string disp_element dynet_tchs_reserved <location> <cell_desc> 5-230 GMR-01 68P02901W23-P 23 Feb 2004 . The parameter is invalid for the BSC (location 0). 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. 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-P 23 Feb 2004 5-231 GMR-01 . the BSC-RXCDR interface allocates 8 kbit/s Aters where appropriate. When this mode is enabled. except when both thresholds are set to 0 (disabled). Syntax Change command strings modify_value 0 eac_mode <value> AXCDR <axcdr_id> equip 0 AXCDR 5-232 GMR-01 68P02901W23-P 23 Feb 2004 .eac_mode Chapter 5: CM database parameters eac_mode {4415} Description The eac_mode parameter enables or disables the Enhanced Auto-Connect (EAC) mode. Type A (no operator actions) Supported by OMC-R GUI Yes Cell description required No Dependencies This parameter can be modified inside and outside sysgen mode. An AXCDR device cannot be in EAC mode if any KSW is in B-U state in the RXCDR or BSC. An AXCDR device cannot be in EAC mode if CIC validation is disabled. The cic_block_thresh parameter must be less than the cic_unblock_thresh parameter by a value of not less than 10. The AMR Enhanced Capacity feature must be unrestricted. • CIC validation.Technical Description BSS Command Reference eac_mode After entering the equip AXCDR command. the user is prompted for the following parameters: • CIC blocking threshold. When eac_mode is enabled. the user is prompted for following parameters: • device ID. • EAC mode. Display command string disp_equipment 0 AXCDR <axcdr_id> Values Value type Boolean Valid range 0 or 1 0 1 Default value 68P02901W23-P 23 Feb 2004 Disabled Enabled 0 5-233 GMR-01 . • CIC unblocking threshold. This dependency is also checked during database verification (see lcs_mode section). disabled on Air-interface 5-234 GMR-01 68P02901W23-P 23 Feb 2004 . Type A (no operator actions) Supported by OMC-R GUI Yes Cell description required No Dependencies The Multiband Inter-cell Handover feature must be enabled. This parameter can only be changed at the BSC. but it can be viewed at any site within a specified BSS. • Whether an MS is allowed to send an early Classmark Change message.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. 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. Syntax Change command string chg_element early_classmark_sending <value> 0 Display command string 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. the command is rejected. Technical Description BSS Command Reference Default value early_classmark_sending 2 Disabled on A-interface. section 10. ‘References GSM specification 68P02901W23-P 23 Feb 2004 TS GSM 04. neighbours are reported by the BSS to the MS as follows: Handover from GSM900 to GSM900 .2. However. the MSC can still make solicited requests for classmark updates by sending a Classmark Request message to the BSS. the frequency capabilities of the MS are based on the target cell frequency when multiband handovers are being performed. Therefore.08.only the GSM1800 neighbours Handover from GSM1800 to GSM900 . after an external handover. enabled on Air-interface 3 Enabled across both the A-interface and the Air-interface 0 When early_classmark_sending is set to 2.5.only the GSM1800 neighbours. the BSS does not forward classmark update messages to the MSC.34 This is a Motorola defined parameter.only the GSM900 neighbours Handover from GSM1800 to GSM1800 . 5-235 GMR-01 . External multiband capabilities will be limited. If this is not done. and subsequent handovers to GSM1800 cells are therefore not possible.only the GSM900 neighbours Handover from GSM900 to GSM1800 . This means that the MSC does not obtain any information about the MS capabilities. Index values are 0 to 33. 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. Type A (no operator actions) Supported by OMC-R GUI Yes Cell description required No Dependencies None Syntax Change command string chg_eas_alarm <alarm_table_index> <alarm_severity_level> "<eas_alarm_text>" Display command string disp_element eas_alarm.<index> <location> Values Value type Text Valid range Up to 24 alphanumeric characters (including spaces) Default value None 5-236 GMR-01 68P02901W23-P 23 Feb 2004 .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 text component and severity level are assigned when the EAS alarm table is initialized using the chg_eas_alarm command. Index numbers are required to specify which of the 34 pairs to display. The EAS alarm table consists of 34 indexed pairs consisting of a text component and a severity level. The eas_alarm_type value corresponds to the index number identifying the location of a text and severity level pair.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. 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. Type A (no operator actions) Supported by OMC-R GUI No Cell description required No Dependencies None Syntax Add/Change command strings equip <location> eas map_eas_opto <location> <device_id> [<opt_#1> <alarm_table_index>] . 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.<index> <location> Values Value type Integer Valid range 0 to 33 Default value None 68P02901W23-P 23 Feb 2004 5-237 GMR-01 ...[<opt_#8> <alarm_table_index>] Display command string disp_element eas_alarm_type. Index numbers are required to specify which of the 34 pairs to display. . 2.[<opto_#n>] ] [ off = [opto_#1>].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 used to identify the desired EAS device.[<opto_#n>] ] Display command string disp_element eas_report_opto. 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. Type A (no operator actions) Supported by OMC-R GUI No Cell description required No Dependencies None Syntax Change command string chg_eas_report <location> <device_id> [ on = [<opto_#1>]. Index values are assigned during installation. 7. Index numbers are required. and 8 report state changes but 3 and 5 do not.. 6.<index> <location> Values Value type Boolean Valid range 0 or 1 Default value 0 Disabled 1 Enabled None 5-238 GMR-01 68P02901W23-P 23 Feb 2004 .. 4. 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. 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. “Clear" is a valid alarm condition. but it is not a valid alarm severity setting. Type A (no operator actions) Supported by OMC-R GUI Yes Cell description required No Dependencies None Syntax Change command strings chg_eas_alarm <alarm_table_index> <alarm_severity_level> "<new_alarm_string>" chg_element eas_severity. If the chg_eas_alarm command is used.<index> <location> Values Value type Integer Valid range 0 to 4 0 68P02901W23-P 23 Feb 2004 Investigate 5-239 GMR-01 . The text component and severity level are assigned when the EAS alarm table is initialized using the chg_eas_alarm command.<index> <value> <location> Display command string disp_element eas_severity.Technical Description BSS Command Reference eas_severity eas_severity Description The eas_severity parameter specifies the severity level component of the EAS (External Alarm System) alarm table. The severity component may be changed using either the chg_element or the chg_eas_alarm command. it permits the alarm text to be changed at the same time. eas_severity Chapter 5: CM database parameters Default value 1 Critical 2 Major 3 Minor 4 Warning None 5-240 GMR-01 68P02901W23-P 23 Feb 2004 . Technical Description BSS Command Reference efr_enabled efr_enabled Description The efr_enabled parameter enables or disables the Enhanced Full Rate (EFR). Type A (no operator actions) Supported by OMC-R GUI Yes Cell description required No Dependencies The EFR feature must be unrestricted. This parameter cannot be enabled if the handover_required_sp_ver_used parameter is disabled. This parameter is only valid at a BSC location. Syntax Change command string modify_value efr_enabled <value> 0 Display command string disp_element efr_enabled 0 Values Value type Boolean Valid range 0 or 1 Default value 68P02901W23-P 23 Feb 2004 0 Disabled 1 Enabled 0 5-241 GMR-01 . TS GSM 08. 5-242 GMR-01 68P02901W23-P 23 Feb 2004 .08 [2].08 [3]. TS GSM 08.058 [4] This is a Motorola defined parameter.efr_enabled Chapter 5: CM database parameters References GSM specification TS GSM 04. Syntax Change command strings chg_element egprs_init_dl_cs <value> <location> <cell_desc> chg_cell_element egprs_init_dl_cs <value> <cell_desc> Display command strings disp_cell <cell_desc> ["full"] disp_element egprs_init_dl_cs <location> <cell_desc> Values Value type Integer Valid range 0 to 8 68P02901W23-P 23 Feb 2004 0 MCS1 is applied to start on downlink TBF for this cell 1 MCS2 is applied to start on downlink TBF for this cell 2 MCS3 is applied to start on downlink TBF for this cell 3 MCS4 is applied to start on downlink TBF for this cell 4 MCS5 is applied to start on downlink TBF for this cell 5-243 GMR-01 .Technical Description BSS Command Reference egprs_init_dl_cs egprs_init_dl_cs {23658} Description The egprs_init_dl_cs parameter specifies the initial downlink coding scheme to be used for an EGPRS TBF in a cell. Type A (no operator actions) Supported by OMC-R GUI Yes Cell description required Yes Dependencies {23658} The EGPRS feature must be unrestricted. egprs_init_dl_cs Chapter 5: CM database parameters Default value 5 MCS6 is applied to start on downlink TBF for this cell 6 MCS7 is applied to start on downlink TBF for this cell 7 MCS8 is applied to start on downlink TBF for this cell 8 MCS9 is applied to start on downlink TBF for this cell 2 The default value is 2 because MCS3 is considered to be safe to start the downlink transfer for all mobiles. regardless of where they are in the cell. 5-244 GMR-01 68P02901W23-P 23 Feb 2004 . when there is no prior information of a mobiles RF channel quality. Syntax Change command strings chg_element egprs_init_ul_cs <value> <location> <cell_desc> chg_cell_element egprs_init_ul_cs <value> <cell_desc> Display command strings disp_cell <cell_desc> ["full"] disp_element egprs_init_ul_cs <location> <cell_desc> Values Value type Integer Valid range 0 to 8 68P02901W23-P 23 Feb 2004 0 MCS1 is applied to start on uplink TBF for this cell 1 MCS2 is applied to start on uplink TBF for this cell 2 MCS3 is applied to start on uplink TBF for this cell 3 MCS4 is applied to start on uplink TBF for this cell 4 MCS5 is applied to start on uplink TBF for this cell 5-245 GMR-01 .Technical Description BSS Command Reference egprs_init_ul_cs egprs_init_ul_cs {23658} Description The egprs_init_ul_cs parameter specifies the initial uplink coding scheme to be used for an EGPRS TBF in the cell Type A (no operator actions) Supported by OMC-R GUI Yes Cell description required Yes Dependencies {23658} The EGPRS feature must be unrestricted. when there is no prior information of a mobiles RF channel quality. regardless of where they are in the cell.egprs_init_ul_cs Chapter 5: CM database parameters Default value 5 MCS6 is applied to start on uplink TBF for this cell 6 MCS7 is applied to start on uplink TBF for this cell 7 MCS8 is applied to start on uplink TBF for this cell 8 MCS9 is applied to start on uplink TBF for this cell 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. 5-246 GMR-01 68P02901W23-P 23 Feb 2004 . 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. • The hopping systems do not contain a combination of PGSM and GSM extension band frequencies. The egsm_bcch_sd parameter can be enabled only if the cell is an EGSM frequency cell. • The sd_load parameter is 0 for all carriers in the Cell. Syntax Change command strings chg_element egsm_bcch_sd <value> <location> <cell_desc> chg_cell_element egsm_bcch_sd <value> <cell_desc> Display command strings disp_cell <cell_desc> ["full"] disp_element egsm_bcch_sd <location> <cell_desc> 68P02901W23-P 23 Feb 2004 5-247 GMR-01 . • The neighbour BCCH frequencies are not in the GSM extension band. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required Yes Dependencies The egsm_bcch_sd parameter can be disabled only if: • The BCCH carrier is not in the GSM Extension band. egsm_bcch_sd Chapter 5: CM database parameters Values Value type Boolean Valid range 0 or 1 Default value 0 Disabled 1 Enabled 0 5-248 GMR-01 68P02901W23-P 23 Feb 2004 . which are considered best quality resources. 2 Forced handovers to interference bands 1 to 2 extended resource are allowed. Syntax Change command strings chg_element egsm_handover_threshold <value> <location> <cell_desc> chg_cell_element egsm_handover_threshold <value> <cell_desc> Display command string disp_element egsm_handover_threshold <location> <cell_desc> Values Value type Integer Valid range 0 to 5 68P02901W23-P 23 Feb 2004 0 Forced handovers are not allowed. 3 Forced handovers to interference bands 1 to 3 extended resource are allowed. 5-249 GMR-01 . Forced handovers may be disallowed by disabling the egsm_handover_threshold parameter. Type A (no operator actions) Supported by OMC-R GUI Yes Cell description required Yes Dependencies This parameter may only be changed on EGSM systems. Allowed interference bands are those above or meeting a specified threshold. 1 Forced handovers to interference band 1 extended resource are allowed.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. 0 5-250 GMR-01 68P02901W23-P 23 Feb 2004 .egsm_handover_threshold Default value Chapter 5: CM database parameters 4 Forced handovers to interference bands 1 to 4 extended resource are allowed. 5 Forced handovers to interference bands 1 to 5 extended resource are allowed. all emergency calls are allowed. When enabled.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. only emergency calls from classes 11 to 15 are allowed. Type A (no operator actions) Supported by OMC-R GUI Yes Cell description required Yes Dependencies cell_bar_access_class Syntax Add/Change command strings add_cell <gsm_cell_id> <location> chg_element emergency_class_switch <value> <location> <cell_desc> chg_cell_element emergency_class_switch <value> <cell_desc> Display command strings disp_cell <cell_desc> ["full"] disp_element emergency_class_switch <location> <cell_desc> Values Value type Boolean Valid range 0 or 1 Default value 68P02901W23-P 23 Feb 2004 0 Disabled 1 Enabled 0 5-251 GMR-01 . When disabled. and table 10.Emergency Call Not Allowed 2.17.30 12.2.1: radio resource connection establishment initiated by the MS 4.1.5.8.4: access class definitions 5-252 GMR-01 68P02901W23-P 23 Feb 2004 .11 .2: emergency call establishment 4.7 .08 .2.2.emergency_class_switch Chapter 5: CM database parameters References GSM parameter EC GSM specifications 4.10.Cell Description .08 .08 .5.3.5.3.20 . Type A (no operator actions) Supported by OMC-R GUI Yes Cell description required Yes Dependencies None Syntax Add/Change command strings add_cell <gsm_cell_id> <location> chg_element en_incom_ho <value> <location> <cell_desc> chg_cell_element en_incom_ho <value> <cell_desc> Display command strings disp_cell <cell_desc> ["full"] disp_element en_incom_ho <location> <cell_desc> Values Value type Boolean Valid range 0 or 1 Default value 68P02901W23-P 23 Feb 2004 0 Disabled 1 Enabled 0 5-253 GMR-01 .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. en_incom_ho Chapter 5: CM database parameters References GSM specification GSM TS 03.22 section 3.5. 5-254 GMR-01 68P02901W23-P 23 Feb 2004 .1 This is a Motorola defined parameter. Technical Description BSS Command Reference enhanced_relief enhanced_relief Description The enhanced_relief parameter enables or disables the Intelligent Congestion Relief feature. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required Yes Dependencies The Congestion Relief feature must be unrestricted. Syntax Change command string chg_element enhanced_relief <value> <location> <cell_desc> Display command string disp_element enhanced_relief <location> <cell_desc> Values Value type Boolean Valid range 0 or 1 Default value 68P02901W23-P 23 Feb 2004 0 Disabled 1 Enabled 0 5-255 GMR-01 . Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required No Dependencies To enable One Phase Access. Syntax Change command string chg_element eop_enabled <value> <location> Display command string disp_element eop_enabled <location> Values Value type Boolean Valid range 0 or 1 0 1 Default value EOP disabled EOP enabled 0 5-256 GMR-01 68P02901W23-P 23 Feb 2004 .eop_enabled Chapter 5: CM database parameters eop_enabled Description The eop_enabled parameter enables or disables the One Phase Access feature. this feature must be unrestricted. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required Yes Dependencies None Syntax Change command string chg_element erc_ta_priority <value> <location> <cell_desc> Display command string disp_element erc_ta_priority <location> <cell_desc> Values Value type Integer Valid range 0 to 63 Default value 50 68P02901W23-P 23 Feb 2004 5-257 GMR-01 . the ERC neighbours are appended to the end of the list of candidates. If the absolute timing advance is greater than the priority threshold. Otherwise.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. the ERC neighbours are placed at the top of the list of sorted handover candidates. If ext_range_cell is enabled. CCCH. max_number_sdcchs must be less than or equal to 20 when Extended Range is enabled. Type B (Operator actions required) Supported by OMC-R GUI Yes Cell description required Yes Dependencies The ext_range_cell parameter cannot be changed if the Extended Range Cells feature is restricted.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. 0xff). and SDCCH channels as these channels are always extended. such as extended or normal. Syntax Change command string chg_cell_element ext_range_cell <value> <cell_desc> The system displays the following prompt: Enter handover threshold mobile max range: Display command string disp_element ext_range_cell <location> <cell_desc> 5-258 GMR-01 68P02901W23-P 23 Feb 2004 . Baseband hopping systems can only be configured among timeslots of the same type. all frequency hopping indicators for the timeslots in the BCCH carrier should be set to “255" (in hexadecimal. Operator actions Lock the associated DRIs to change this parameter. ms_max_range must be less than or equal to 63 for a normal range cell.{3723} 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. Horizonmicro or Horizoncompact sites. If frequency hopping systems is enabled in an Extended Range Cell. the maximum value of ms_max_range increases to 219. This parameter is not available at M-Cellcity. Technical Description BSS Command Reference ext_range_cell Values Value type Integer Valid range 0 to 2 Default value 68P02901W23-P 23 Feb 2004 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) 0 5-259 GMR-01 . extended page is not allowed.extended_paging_active Chapter 5: CM database parameters extended_paging_active Description The extended_paging_active parameter enables or disables extended paging. Type A (no operator actions) Supported by OMC-R GUI Yes Cell description required Yes Dependencies None Syntax Add/Change command strings add_cell <gsm_cell_id> <location> chg_element extended_paging_active <value> <location> <cell_desc> chg_cell_element extended_paging_active <value> <cell_desc> Display command strings disp_cell <cell_desc> ["full"] disp_element extended_paging_active <location> <cell_desc> Values Value type Boolean Valid range 0 or 1 0 Disabled 5-260 GMR-01 68P02901W23-P 23 Feb 2004 . 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. b.3. paging_group.6. paging multiframe.1 (iii) to (vi): ccch groups. paging block index 5.2.3.02 .08 . c: ccch_conf. This is a Motorola defined parameter.5.02 .2a.6.3.3: determination of ccch_group. bs_cc_chans.02 .1 . 6. example of TDMA frame mapping for control channels. 5-261 GMR-01 .02 .5.Figure 8.5.3.2.2.5. bs_ccch_comb 5. 10.Technical Description BSS Command Reference extended_paging_active 1 Default value Enabled 0 References GSM specifications 68P02901W23-P 23 Feb 2004 4. paging groups 5.26 5. 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. Type A (no operator actions) Supported by OMC-R GUI Yes Cell description required Yes Dependencies The BSS Inter-RAT feature must be unrestricted. Syntax Change command strings chg_element fdd_qmin <value> <location> <cell_desc> chg_cell_element fdd_qmin <value> <cell_desc> Display command strings disp_cell <cell_desc> ["full"] disp_element fdd_qmin <location> <cell_desc> Values Value type Integer Valid range 0 to 7 Default value 0 5-262 GMR-01 68P02901W23-P 23 Feb 2004 . 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. Syntax Change command strings chg_element fdd_qoffset <value> <location> <cell_desc> chg_cell_element fdd_qoffset <value> <cell_desc> Display command strings disp_cell <cell_desc> ["full"] disp_element fdd_qoffset <location> <cell_desc> Values Value type Integer Valid range 0 to 15 Default value 8 68P02901W23-P 23 Feb 2004 5-263 GMR-01 . The fdd_qoffset parameter is configurable on a per cell basis. Type A (no operator actions) Supported by OMC-R GUI Yes Cell description required Yes Dependencies The BSS Inter-RAT feature must be unrestricted. the cells at a site may have different frequency types and cabinets may support multiple frequency types.frequency_type Chapter 5: CM database parameters frequency_type Description The frequency_type parameter specifies the frequency type of a cell. 5-264 GMR-01 68P02901W23-P 23 Feb 2004 . If the value of tx_power_cap is set to 0 (indicating a low power cell). If inner_zone_alg is set to indicate Dual Band Cells. Type B (operator actions required) Supported by OMC-R GUI Yes Cell description required Yes Dependencies If the Infrastructure Sharing Homogeneous Cabinet feature is not enabled. and radios have already been associated with the cell. The frequency_type of a cell may be changed to PCS1900 inside Sysgen mode. the frequency_type may be set only to DCS1800. (2) if secondary_freq_type is DCS1800. Cell and cabinet frequency types must be allowed at the BSS as per the freq_types_allowed command. If both the Infrastructure Sharing Homogeneous Cabinet feature and the Infrastructure Sharing Heterogeneous feature are enabled. but the Infrastructure Sharing Heterogeneous feature is disabled. frequency_type may be set only to PGSM or EGSM. the cell frequency must be supported by the cabinet the cell is correlated to. If the Infrastructure Sharing Homogeneous Cabinet feature is enabled. However. the frequency_type for every cabinet and cell at a site must be the same. the following two dependencies are enforced: (1) if secondary_freq_type is set to EGSM or PGSM. the cells at a site must have the same single frequency type as the cabinet they correlate to. 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. However. Operator actions Put the system into SYSGEN mode to change the frequency_type parameter. the cabinets at the site may be of different frequency types. a warning message is issued to the operator. Display command strings disp_cell <cell_desc> ["full"] disp_element frequency_type <location> <cell_desc> Values Value type Integer Text Valid range 1 pgsm 2 egsm 4 dcs1800 8 pcs1900 Default value 68P02901W23-P 23 Feb 2004 None 5-265 GMR-01 .Technical Description BSS Command Reference frequency_type Syntax Add/Change command strings add_cell <gsm_cell_desc> <location The add_cell command accepts either numeric values or text strings for frequency_type. chg_cell_element frequency_type <value> <cell_desc> The chg_cell_element command accepts only numeric values for frequency_type. full_pwr_rfloss Chapter 5: CM database parameters full_pwr_rfloss Description The full_pwr_rfloss parameter enables or disables the ability of the BSS power control to fully power up the MS and BTS at the point where the RF connection appears to be lost. Type A (no operator actions) Supported by OMC-R GUI Yes Cell description required Yes Dependencies None Syntax Add/Change command strings add_cell <gsm_cell_id> chg_element full_pwr_rfloss <value> <location> <cell_desc> chg_cell_element full_pwr_rfloss <value> <cell_desc> Display command strings disp_cell <cell_desc> ["full"] disp_element full_pwr_rfloss <location> <cell_desc> Values Value type Boolean Valid range 0 or 1 Default value 0 Disabled 1 Enabled 0 5-266 GMR-01 68P02901W23-P 23 Feb 2004 . When enabled. the transition to full power occurs when the threshold set by link_about_to_fail is reached in the link_fail procedure. (One successful GPRS alarm increment time period might be too short for the Channel Coder Unit (CCU) to send an error indication. any existing counts between the new and the old threshold does not clear an alarm until the next successful time period occurs. Type A (no operator actions) Supported by OMC-R GUI Yes Cell description required No Dependencies The GPRS and ECERM features must be unrestricted.Technical Description BSS Command Reference gci_error_clr_thresh gci_error_clr_thresh Description The gci_error_clr_thresh parameter specifies the error count threshold (equal to or less than) for an alarm to be cleared for a GPRS Circuit Identifier (GCI). Syntax Change command string chg_element gci_error_clr_thresh <value> 0 Display command string disp_element gci_error_clr_thresh 0 Values Value type Integer Valid range 0 to 253 Default value 0 68P02901W23-P 23 Feb 2004 5-267 GMR-01 . If the threshold is increased during operation. Two successful GPRS alarm increment time periods must elapse without a sync loss error to clear an alarm within this threshold. thus clearing the alarm prematurely.) This parameter can be set only at a BSC. no immediate alarm occurs. This parameter can be set only at a BSC. The new threshold takes effect only when the GCI error count changes. Syntax Change command string chg_element gci_error_gen_thresh <value> 0 Display command string disp_element gci_error_gen_thresh 0 Values Value type Integer Valid range 2 to 255 Default value 6 5-268 GMR-01 68P02901W23-P 23 Feb 2004 . Type A (no operator actions) Supported by OMC-R GUI Yes Cell description required No Dependencies The GPRS and ECERM features must be unrestricted.gci_error_gen_thresh Chapter 5: CM database parameters gci_error_gen_thresh Description The gci_error_gen_thresh parameter specifies the error count threshold (equal to or greater than) for an alarm to be generated for a GPRS Circuit Identifier (GCI). If the threshold is changed during operation. This parameter can be set only at a BSC. Type A (no operator actions) Supported by OMC-R GUI Yes Cell description required No Dependencies The GPRS and ECERM features must be unrestricted. Syntax Change command string chg_element gci_error_inc <value> 0 Display command string disp_element gci_error_inc 0 Values Value type Integer Valid range 0 GCI alarms not raised 1 to 255 GCI alarms raised 0 If ECERM feature is restricted 1 If ECERM feature is not restricted Default value 68P02901W23-P 23 Feb 2004 5-269 GMR-01 .Technical Description BSS Command Reference gci_error_inc gci_error_inc Description The gci_error_inc parameter specifies the error count increment when the Enhanced Circuit Error Rate Monitor (ECERM) feature is in use for GPRS Circuit Identifiers (GCIs) on a per BSC basis. It has no effect on the standby GCLK. the active GCLK requires 30 minutes.gclk_qwarm_flag Chapter 5: CM database parameters gclk_qwarm_flag Description The gclk_qwarm_flag parameter specifies the amount of time required by the active GCLK to warm up. This parameter is only valid for GCLK boards. This time period begins when the site is initialized. If this parameter is disabled. The GCLK version must be V9 or later. 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. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required No Dependencies The Fast GCLK Warmup feature must be unrestricted. Syntax Change command string chg_element gclk_qwarm_flag <value> <location> Display command string disp_element gclk_qwarm_flag <location> Values Value type Boolean Valid range 0 or 1 Default value 0 Disabled 1 Enabled 0 5-270 GMR-01 68P02901W23-P 23 Feb 2004 . an alarm is generated. the global reset message repeats continuously until a Reset Ack is received. After the fixed number of repetitions. Type A (no operator actions) Supported by OMC-R GUI Yes Cell description required No Dependencies This parameter does not apply to RXCDR sites. The global reset procedure repeats is only if the MSC fails to acknowledge the BSS. the global reset message repeats the number of times entered and the alarm: No MSC Acknowledgement for Global Reset is generated. or stops sending the “Reset" message after a fixed number of repetitions.Technical Description BSS Command Reference global_reset_repetitions global_reset_repetitions Description The global_reset_repetitions parameter allows the “Reset" message to be sent indefinitely if Reset Ack is not received. If the value is set to 0. Syntax Change command string chg_element global_reset_repetitions <value> 0 Display command string disp_element global_reset_repetitions 0 Values Value type Integer (number of repetitions) Valid range 0 to 255 Default value 0 68P02901W23-P 23 Feb 2004 5-271 GMR-01 . This parameter applies to only BSC sites. If the value is set to a value greater than 0. 5-272 GMR-01 68P02901W23-P 23 Feb 2004 .global_reset_repetitions Chapter 5: CM database parameters References GSM specification TS GSM 8.08 This is a Motorola defined parameter. If set to 24. It is possible to configure different functions on each of the 32 channels. BTP. or MSI is equipped.Technical Description BSS Command Reference gproc_slots gproc_slots Description The gproc_slots parameter specifies the number of timeslots to be allocated to all GPROCs for the TDM highway. The system supports 16 or 32 timeslots for assignment to the TDM highway. Type B (operator actions required) Supported by OMC-R GUI No Cell description required No Dependencies This parameter may not be modified if any BSP. 24 {4040} or 32 68P02901W23-P 23 Feb 2004 16 16 TDM timeslots 24 {4040} 24 TDM timeslots (BSC only) 5-273 GMR-01 . at least one GPROC should be equipped after all the MSIs are equipped. {4040} The BSS supports a value of 24 for this parameter on the BSC. DHP. Operator actions This parameter may only be modified in initial SYSGEN mode. Syntax Change command string chg_element gproc_slots <value> <location> Display command string disp_element gproc_slots <location> Values Value type Integer Valid range 16. so that 12 MSIs and 8 GPROCs can be brought into service This parameter is not allowed at M-Cell sites. GPROC. " 5-274 GMR-01 68P02901W23-P 23 Feb 2004 . the system displays the following warning: “COMMAND ACCEPTED: WARNING: Specified value requires GPROC2 {4354} or GPROC3 boards.gproc_slots Chapter 5: CM database parameters 32 Default value 32 TDM timeslots (only valid with GPROC2 {4354} and GPROC3 boards) 16 If gproc_slots is greater than 16. Type A (no operator actions) Supported by OMC-R GUI Yes Cell description required No Dependencies The GPRS and ECERM features must be unrestricted. 60 If GPRS and ECERM features are unrestricted. 5 to 240 If GPRS and ECERM features are unrestricted. or decremented if no error indication is received.Technical Description BSS Command Reference gprs_alarm_time 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). Syntax Change command string chg_element gprs_alarm_time <value> 0 Display command string disp_element gprs_alarm_time 0 Values Value type Integer Valid ranges 0 If GPRS or ECERM are restricted (effectively equivalent to gprs_alarm_time parameter turned off). Default values 68P02901W23-P 23 Feb 2004 5-275 GMR-01 . This parameter applies to only BSC sites. 0 If GPRS or ECERM are restricted. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required Yes Dependencies The GPRS feature must be unrestricted. Syntax Change command strings chg_element gprs_bs_cv_max <value> <location> <cell_desc> chg_cell_element gprs_bs_cv_max <value> <cell_desc> Display command string disp_element gprs_bs_cv_max <location> <cell_desc> Values Value type Integer (blocks) Valid range 0 to 15 Default value 6 5-276 GMR-01 68P02901W23-P 23 Feb 2004 . 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. The MS sends a count down value in each uplink RLC data block starting gprs_bs_cv_max blocks from the last block. BSS software processes using this parameter are notified immediately after the change is made.gprs_bs_cv_max Chapter 5: CM database parameters gprs_bs_cv_max Description The gprs_bs_cv_max specifies the maximum count down value a mobile can use for uplink RLC data transfer. PCU software processes using this parameter are notified immediately after the change is made. Settings are copied by the copy_cell command. as a number of MSs per timeslot in the cell.Technical Description BSS Command Reference gprs_cell_cgt_thr gprs_cell_cgt_thr {4449} Description The gprs_cell_cgt_thr parameter specifies the threshold at which the PCU attempts congestion relief for a cell. The parameter can be changed in or out of SYSGEN mode. Syntax Change command string chg_element gprs_cell_cgt_thr <value> <location> <cell_id> chg_cell_element gprs_cell_cgt_thr <value> <cell_id> Display command string disp_element gprs_cell_cgt_thr <location> [<cell_id>] disp_cell <cell_id> "full" 68P02901W23-P 23 Feb 2004 5-277 GMR-01 . Type A (no operator actions) Supported by OMC-R GUI Yes Cell description required Yes Dependencies The Network Controlled Cell Reselection (NCCR) feature must be unrestricted. 5-278 GMR-01 68P02901W23-P 23 Feb 2004 . This is a Motorola defined parameter. References GSM parameter None.gprs_cell_cgt_thr Chapter 5: CM database parameters Values Value type Integer Valid ranges 1 to 4 Default values 2 MS(s) per timeslot in the cell. Differences in received signal levels from 0 to 14 dB (in 2 dB increments) are used for cell reselection.Technical Description BSS Command Reference gprs_cell_reselect_hysteresis gprs_cell_reselect_hysteresis {3723} 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). Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required Yes Dependencies The PBCCH/PCCCH optional feature must be unrestricted. Syntax Add/Change command strings chg_element gprs_cell_reselect_hysteresis <value> <location> <cell_desc> chg_cell_element gprs_cell_reselect_hysteresis <value> <cell_desc> Display command strings 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 68P02901W23-P 23 Feb 2004 5-279 GMR-01 . gprs_cell_reselect_hysteresis Default value Chapter 5: CM database parameters 4 8 dB 5 10 dB 6 12 dB 7 14 dB 0 (0 dB) 5-280 GMR-01 68P02901W23-P 23 Feb 2004 . 4.multislot class 4. 6. Syntax Change command strings chg_element gprs_com_ms_class <value> <location> Display command strings disp_element gprs_com_ms_class <location> Values Value type Integer Valid range 1.multislot class 8 to 29. 5.multislot class 1. 3. 7. 8 . 4 .multislot class 2. 2 . The four possible values represent the following: 1 . 8 Default value 8 68P02901W23-P 23 Feb 2004 5-281 GMR-01 .Technical Description BSS Command Reference gprs_com_ms_class gprs_com_ms_class {4441} Description The gprs_com_ms_class parameter specifies the Most Common Multislot Class of GPRS mobiles. Type A (no operator actions) Supported by OMC-R GUI Yes Cell description required No Dependencies The GPRS feature must be unrestricted. 2. The parameter can be changed in or out of SYSGEN mode. Syntax Change command string chg_element gprs_cr_margin <value> <location> <cell_id> chg_cell_element gprs_cr_margin <value> <cell_id> Display command string disp_element gprs_cr_margin <location> [<cell_id>] disp_cell <cell_id> "full" 5-282 GMR-01 68P02901W23-P 23 Feb 2004 . 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. Settings are copied by the copy_cell command. Type A (no operator actions) Supported by OMC-R GUI Yes Cell description required Yes Dependencies The Network Controlled Cell Reselection (NCCR) feature must be unrestricted.gprs_cr_margin Chapter 5: CM database parameters gprs_cr_margin {4449} 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. PCU software processes using this parameter are notified immediately after the change is made. 5-283 GMR-01 . This is a Motorola defined parameter.Technical Description BSS Command Reference gprs_cr_margin Values Value type Integer Valid ranges 5 to 40 dB Default values 30 dB References GSM parameter 68P02901W23-P 23 Feb 2004 None. 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). BSS software processes using this parameter are notified immediately after the change is made.gprs_dl_pwr_mode Chapter 5: CM database parameters gprs_dl_pwr_mode Description {4040} The gprs_dl_pwr_mode parameter specifies the downlink power control mode that the PCUs use to broadcast data blocks to the MS. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required No Dependencies The GPRS feature must be unrestricted. Syntax Change command strings {4040} chg_element gprs_dl_pwr_mode <value> bsc Display command string {4040} disp_element gprs_dl_pwr_mode bsc Values Value type Integer Valid range 0 to 2 5-284 GMR-01 68P02901W23-P 23 Feb 2004 . It is a per BSC parameter. Technical Description BSS Command Reference Default value 68P02901W23-P 23 Feb 2004 gprs_dl_pwr_mode 0 No power mode 1 Mode A 2 Mode B 1 5-285 GMR-01 . BSS software processes using this parameter are notified immediately after the change is made. Syntax Change command strings chg_element gprs_drx_timer_max <value> <location> <cell_desc> chg_cell_element gprs_drx_timer_max <value> <cell_desc> Display command strings disp_cell <cell_desc> "full" disp_element gprs_drx_timer_max <location> <cell_desc> 5-286 GMR-01 68P02901W23-P 23 Feb 2004 . Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required Yes Dependencies The GPRS feature must be unrestricted.gprs_drx_timer_max Chapter 5: CM database parameters gprs_drx_timer_max Description The gprs_drx_timer_max parameter specifies the maximum timer value allowed for the MS to request for non-DRX mode after packet transfer mode. Technical Description BSS Command Reference gprs_drx_timer_max Values Value type Integer (seconds) Valid range 0 to 3 Default value 0 68P02901W23-P 23 Feb 2004 5-287 GMR-01 . see the ra_colour parameter in"ra_colour" on page 5-631 description. Type B (operator actions required) Supported by OMC-R GUI Yes Cell numbers required Yes Dependencies The GPRS feature must be unrestricted. A routing area colour must have been configured for the cell. max_gprs_pdch must be set to a non-zero-value. {4040} At least one PCU must be equipped. There must be at least one. the command will be rejected if there is no reserved Packet Data Channel (PDCH) timeslot in the same cell. At least one nsvc must be associated with a GBL. 5-288 GMR-01 68P02901W23-P 23 Feb 2004 .gprs_enabled Chapter 5: CM database parameters gprs_enabled Description The gprs_enabled parameter specifies whether or not GPRS is unrestricted at a cell. BSS software processes using this parameter are immediately notified when the change is made. The nsei parameter must be configured by the operator. {3723} If pccch_enabled is set to 1 (enabled) and the operator attempts to set gprs_enabled to 1. A prompt will request the primary PCU id. Operator actions Before this parameter can be set. The gprs_supported broadcast parameter describes the GPRS configuration of a cell. the operator must have set gprs_sig_bvci parameter (see "gprs_sig_bvci" on page 5-318) using the chg_element command. The BSS implements this as two cell elements: gprs_enabled and pcch_alloc. {4040} A PSP and the default GSL must be equipped at the PCU/s. The RAC parameter must be set. Technical Description BSS Command Reference gprs_enabled Syntax Change command string chg_cell_element gprs_enabled <value> <cell-desc> chg_cell_element <location> gprs_enabled <value> all Display command string disp_element gprs_enabled <location> <cell-desc> disp_element gprs_enabled <location> all Values Value type Boolean Valid range 0 or 1 Default value 68P02901W23-P 23 Feb 2004 0 Disabled 1 Enabled 0 5-289 GMR-01 . Such handovers recover PDTCHs which have been switched to TCHs.gprs_intraho_allwd Chapter 5: CM database parameters 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. 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. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required Yes Dependencies The GPRS feature must be unrestricted. Syntax Change command strings chg_element gprs_intraho_allwd <value> <location> <cell_desc> chg_cell_element gprs_intraho_allwd <value> <cell_desc> Display command strings disp_cell <cell_desc> <"full"> disp_element gprs_intraho_allwd <location> <cell_desc> 5-290 GMR-01 68P02901W23-P 23 Feb 2004 . BSS software processes using this parameter are notified immediately after the change is made. Technical Description BSS Command Reference gprs_intraho_allwd Values Value type Integer Valid range 0 or 1 Default value 68P02901W23-P 23 Feb 2004 0 Disabled 1 Enabled 1 5-291 GMR-01 . Syntax Change command strings {4040} chg_element gprs_mac_mode <value> bsc Display command string {4040} disp_element gprs_mac_mode bsc Values Value type Boolean Valid range 1 Dynamic mode 5-292 GMR-01 68P02901W23-P 23 Feb 2004 . Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required No Dependencies The GPRS feature must be unrestricted. Only the dynamic access mode is available. BSS software processes using this parameter are notified immediately after the change is made.gprs_mac_mode Chapter 5: CM database parameters gprs_mac_mode Description {4040} The gprs_mac_mode parameter specifies the medium access mode to be used by the PCUs. Type A (no operator actions) Supported by OMC-R GUI Yes Cell description required No Dependencies GPRS must be unrestricted.Technical Description BSS Command Reference gprs_max_ul_ts gprs_max_ul_ts {4441} 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 Change command strings chg_element gprs_max_ul_ts <value> <location> Display command strings disp_element gprs_max_ul_ts <location> Values Value type Integer Valid range 1 to 2 Default value 2 68P02901W23-P 23 Feb 2004 5-293 GMR-01 . gprs_min_prr_blks Chapter 5: CM database parameters gprs_min_prr_blks {4441} Description The gprs_min_prr_blks parameter specifies the minimum number of dynamic PRR blocks created per cell and measured over four multiframes. Type A (no operator actions) Supported by OMC-R GUI Yes Cell description required Yes Dependencies Modification of gprs_min_prr_blks has no effect for cells that have the pccch_enabled parameter enabled. Syntax Change command strings chg_element gprs_min_prr_blks <value> <location> <cell_desc> chg_cell_element gprs_min_prr_blks <value> <cell_desc> Display command strings disp_cell <cell_desc> "full" disp_element gprs_min_prr_blks <location> <cell_desc> Values Value type Integer Valid range 0 to 24 Default value 0 5-294 GMR-01 68P02901W23-P 23 Feb 2004 . GPRS must be unrestricted. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required Yes Dependencies The GPRS feature must be unrestricted. n3102 never exceeds gprs_ms_pan_max. When an uplink ack/nack is received. The MS counter n3102 counts the number of uplink acks/nacks received by the MS. BSS software processes using this parameter are notified immediately after the change is made. Syntax Change command strings chg_element gprs_ms_pan_dec <value> <location> <cell_desc> chg_cell_element gprs_ms_pan_dec <value> <cell_desc> Display command strings disp_cell <cell_desc> "full" disp_element gprs_ms_pan_dec <location> <cell_desc> 68P02901W23-P 23 Feb 2004 5-295 GMR-01 . Each time the preset internal timer T3182 expires. n3102 is decremented by gprs_ms_pan_dec. n3102 is incremented by gprs_ms_pan_inc. 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.Technical Description BSS Command Reference gprs_ms_pan_dec gprs_ms_pan_dec Description The gprs_ms_pan_dec parameter specifies the amount by which to decrement the MS counter n3102. GSM technical specification 04.60 5-296 GMR-01 68P02901W23-P 23 Feb 2004 . This is a Motorola defined parameter.gprs_ms_pan_dec Chapter 5: CM database parameters Values Value type Integer Valid range 0 to 7 Default value 1 References GSM parameter None. Technical Description BSS Command Reference gprs_ms_pan_inc gprs_ms_pan_inc Description The gprs_ms_pan_inc parameter specifies the amount by which to increment the MS counter n3102. T3182 defines how long the mobile waits for an uplink ack/nack. The MS counter n3102 counts the number of uplink acks/nacks received by the MS. n3102 is incremented by gprs_ms_pan_inc. then the MS performs an abnormal cell reselection procedure as defined in the GSM standard referred to in this description. n3102 never exceeds gprs_ms_pan_max. BSS software processes using this parameter are notified immediately after the change is made. Syntax Change command strings chg_element gprs_ms_pan_inc <value> <location> <cell_desc> chg_cell_element gprs_ms_pan_inc <value> <cell_desc> Display command strings disp_cell <cell_desc> "full" disp_element gprs_ms_pan_inc <location> <cell_desc> 68P02901W23-P 23 Feb 2004 5-297 GMR-01 . Each time the preset internal timer T3182 expires. If n3102 decrements to zero. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required Yes Dependencies The GPRS feature must be unrestricted. When an uplink ack/nack is received. n3102 is decremented by gprs_ms_pan_dec. 60 5-298 GMR-01 68P02901W23-P 23 Feb 2004 .gprs_ms_pan_inc Chapter 5: CM database parameters Values Value type Integer Valid range 0 to 7 Default value 1 References GSM parameter None. This is a Motorola defined parameter. GSM specification 04. T3182 defines how long the mobile waits for an uplink ack/nack. When an uplink ack/nack is received. BSS software processes using this parameter are notified immediately after the change is made. then the MS performs an abnormal cell reselection procedure as defined in the GSM standard referred to in this description.Technical Description BSS Command Reference gprs_ms_pan_max gprs_ms_pan_max Description The gprs_ms_pan_max parameter specifies the maximum value of the MS counter n3102. Each time the preset internal timer T3182 expires. n3102 never exceeds gprs_ms_pan_max. If n3102 decrements to zero. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required Yes Dependencies The GPRS feature must be unrestricted. n3102 is decremented by gprs_ms_pan_dec. n3102 is incremented by gprs_ms_pan_inc. Syntax Change command strings chg_element gprs_ms_pan_max <value> <location> <cell_desc> chg_cell_element gprs_ms_pan_max <value> <cell_desc> Display command strings disp_cell <cell_desc> "full" disp_element gprs_ms_pan_max <location> <cell_desc> 68P02901W23-P 23 Feb 2004 5-299 GMR-01 . The MS counter n3102 counts the number of uplink acks/nacks received by the MS. This is a Motorola defined parameter.gprs_ms_pan_max Chapter 5: CM database parameters Values Value type Integer Valid range 0 to 7 Default value 3 References GSM parameter None.60 5-300 GMR-01 68P02901W23-P 23 Feb 2004 . GSM technical specification 04. EGSM and GSM850 cells in 2 dBm steps as shown in Table 5-11: 5-301 GMR-01 . Syntax Add/Change command strings chg_element gprs_ms_txpwr_max_cch <value> <location> <cell_desc> chg_cell_element gprs_ms_txpwr_max_cch <value> <cell_desc> Display command strings disp_cell <cell_desc> “full" disp_element gprs_ms_txpwr_max_cch <location> <cell_desc> Values Value type Integer Valid range 0 to 31 68P02901W23-P 23 Feb 2004 For PGSM. This parameter is expressed as a power level value. 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. The PBCCH/PCCCH optional feature must be unrestricted. the MS uses one of two possible power levels. Before accessing a cell on the PRACH and before receiving the first power command during a communication on a BCCH (or TCH). Type A (no operator actions) Supported by OMC-R GUI Yes Cell description required Yes Dependencies The cell frequency_type.Technical Description BSS Command Reference gprs_ms_txpwr_max_cch gprs_ms_txpwr_max_cch {3723} 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. 31 For PCS1900 cells as shown in Table 5-13: 2 (For PGSM. 30 (For PCS1900 cells). 30. Table 5-11 Maximum mobile power level for PGSM. 0 (For DCS1800 cells).gprs_ms_txpwr_max_cch Chapter 5: CM database parameters Default value 2 to 28 For DCS1800 cells in 2 dBm steps as shown in Table 5-12: 0 to 15. EGSM and GSM850 cells). 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 Value Power level Value Power level 0 30 dBm 8 14 dBm 1 28 dBm 9 12 dBm 2 26 dBm 10 10 dBm 3 24 dBm 11 8 dBm 4 22 dBm 12 6 dBm 5 20 dBm 13 4 dBm 6 18 dBm 14 2 dBm 7 16 dBm 15 to 28 0 dBm Table 5-13 Maximum mobile power level for PCS1900 cells Value Power level Value Power level 30 33 dBm 7 16 dBm 31 32 dBm 8 14 dBm 0 30 dBm 9 12 dBm 1 28 dBm 10 10 dBm 5-302 GMR-01 68P02901W23-P 23 Feb 2004 . Technical Description BSS Command Reference Table 5-13 68P02901W23-P 23 Feb 2004 gprs_ms_txpwr_max_cch Maximum mobile power level for PCS1900 cells (Continued) Value Power level Value Power level 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 5-303 GMR-01 . Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required No Dependencies The GPRS feature must be unrestricted. or on a GPRS PDTCH. No paging coordination is done by the network. 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. {3723} Table 5-14 shows the two permissible modes.gprs_network_operation_mode Chapter 5: CM database parameters gprs_network_operation_mode Description The gprs_network_operation_mode parameter specifies whether a GPRS is present between the MSC and the SGSN. 3 The network sends CS pages for a GPRS attached MS on the CCCH and PS pages of the PCCCH. {4040} It is a per BSC parameter. Syntax Change command string {4040} 5-304 GMR-01 68P02901W23-P 23 Feb 2004 . BSS software processes using this parameter are notified immediately the change is made. {3723} Network Operation Mode 2 is not supported by the BSS. if allocated. 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. which is the PCH or the PPCH depending on whether there is a PCCCH in the cell. This means that a MS must monitor both the CCH for CS pages and PCCH for PS pages. Technical Description BSS Command Reference gprs_network_operation_mode chg_element gprs_ network_operation_mode <value> bsc Display command string {4040} disp_element gprs_network_operation_mode bsc Values Value type Integer Valid range 1 or 3 Default value 68P02901W23-P 23 Feb 2004 1 Mode 1 3 Mode 3 2 5-305 GMR-01 . Syntax Change command string chg_element gprs_num_pmrs <value> <location> <cell_id> chg_cell_element gprs_num_pmrs <value> <cell_id> Display command string disp_element gprs_num_pmrs <location> [<cell_id>] disp_cell gprs_num_pmrs <cell_id> "full" 5-306 GMR-01 68P02901W23-P 23 Feb 2004 . The parameter can be changed in or out of SYSGEN mode. Settings are copied by the copy_cell command.gprs_num_pmrs Chapter 5: CM database parameters gprs_num_pmrs {4449} Description The gprs_num_pmrs parameter specifies the number of bad Packet Measurement Reports (PMRs) from the MS at which the PCU performs network controlled cell reselection. Type A (no operator actions) Supported by OMC-R GUI Yes Cell description required Yes Dependencies The Network Controlled Cell Reselection (NCCR) feature must be unrestricted. PCU software processes using this parameter are notified immediately after the change is made. This is a Motorola defined parameter.Technical Description BSS Command Reference gprs_num_pmrs Values Value type Integer Valid ranges 1 to 10 Default values 3 Number of bad PMRs. References GSM parameter 68P02901W23-P 23 Feb 2004 None. 5-307 GMR-01 . gprs_pb Chapter 5: CM database parameters gprs_pb Description The gprs_pb parameter specifies the power reduction used by the BTS on the BCCH blocks. Syntax Change command strings chg_element gprs_pb <value> <location> <cell_desc> chg_cell_element gprs_pb <value> <cell_desc> Display command strings disp_cell <cell_desc> "full" disp_element gprs_pb <location> <cell_desc> Values Value type Integer Valid range 0 to 16 Default value 1 5-308 GMR-01 68P02901W23-P 23 Feb 2004 . BSS software processes using this parameter are notified immediately after the change is made. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required Yes Dependencies The GPRS feature must be unrestricted. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required Yes Dependencies The GPRS feature must be unrestricted. It is used as a multiplier of the power offset in power control calculations. that is. The actual multiplying factor is one tenth of the value set in this parameter. Syntax Change command strings chg_element gprs_pc_alpha <value> <location> <cell_desc> chg_cell_element gprs_pc_alpha <value> <cell_desc> Display command strings disp_cell <cell_desc> "full" disp_element gprs_pc_alpha <location> <cell_desc> Values Value type Integer (Power offset is multiplied by one tenth of this value) Valid range 0 to 10 Default value 0 68P02901W23-P 23 Feb 2004 5-309 GMR-01 .Technical Description BSS Command Reference gprs_pc_alpha gprs_pc_alpha Description The gprs_pc_alpha is the system parameter broadcast on the BCCH. if N is the value of this parameter. the multiplying factor is N/10. BSS software processes using this parameter are notified immediately after the change is made. gprs_pc_meas_chan Chapter 5: CM database parameters 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. BSS software processes using this parameter are notified immediately after the change is made. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required Yes Dependencies The GPRS feature must be unrestricted. Syntax Change command strings chg_element gprs_pc_meas_chan <value> <location> <cell_desc> chg_cell_element gprs_pc_meas_chan <value> <cell_desc> Display command strings disp_cell <cell_desc> "full" disp_element gprs_pc_meas_chan <location> <cell_desc> Values Value type Integer Valid range 0 or 1 0 BCCH 5-310 GMR-01 68P02901W23-P 23 Feb 2004 . Technical Description BSS Command Reference gprs_pc_meas_chan 1 Default value 68P02901W23-P 23 Feb 2004 PDCH 0 5-311 GMR-01 . Syntax Change command strings chg_element gprs_reconfig_thresh_idle_tch <value> <location> <cell_desc> chg_cell_element gprs_reconfig_thresh_idle_tch <value> <cell_desc> Display command strings disp_cell <cell_desc> "full" disp_element gprs_reconfig_thresh_idle_tch <location> <cell_desc> Values Value type Integer Valid range 0 to 5 Default value 1 5-312 GMR-01 68P02901W23-P 23 Feb 2004 .gprs_reconfig_thresh_idle_tch Chapter 5: CM database parameters gprs_reconfig_thresh_idle_tch Description The gprs_reconfig_thresh_idle_tch parameter specifies the number of idle circuit switched resources on the GPRS cell that must be exceeded before a switchable timeslot is reconfigured as a Packet Data Traffic Channel (PDTCH). BSS software processes using this parameter are notified immediately after the change is made. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required Yes Dependencies The GPRS feature must be unrestricted. 11 -8 dB 12 -4 dB 68P02901W23-P 23 Feb 2004 5-313 GMR-01 .Technical Description BSS Command Reference gprs_reselect_offset gprs_reselect_offset {3723} Description The gprs_reselect_offset parameter specifies a positive or negative offset with hysteresis to the GPRS cell reselection criterion. for use by the MS... Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required Yes Dependencies The PBCCH/PCCCH feature must be unrestricted.. .. Syntax Add/Change command strings chg_element gprs_reselect_offset <value> <location> <cell_desc> chg_cell_element gprs_reselect_offset <value> <cell_desc> Display command strings disp_cell <cell_number> “full" 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 . 16 0 dB .. .... 31 +48 dB 16 (0 dB) 5-314 GMR-01 68P02901W23-P 23 Feb 2004 .. ....... 20 +4 dB 21 +8 dB ..gprs_reselect_offset Default value Chapter 5: CM database parameters . . Syntax Add/Change command strings chg_element gprs_rxlev_access_min <value> <location> <cell_desc> chg_cell_element gprs_rxlev_access_min <value> <cell_desc> Display command strings disp_cell <cell_desc> “full" 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 68P02901W23-P 23 Feb 2004 5-315 GMR-01 . C1. 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.Technical Description BSS Command Reference gprs_rxlev_access_min gprs_rxlev_access_min {3723} Description The gprs_rxlev_access_min parameter specifies the minimum received signal level (dBm) required for an MS to access the system. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required Yes Dependencies The PBCCH/PCCCH optional feature must be unrestricted. This should be set to a value corresponding to a signal level at which a call can be maintained in a particular environment. .gprs_rxlev_access_min Default value Chapter 5: CM database parameters .... 63 -47 dBm and higher 0 5-316 GMR-01 68P02901W23-P 23 Feb 2004 . . Each MS transfers the same number of blocks as every other mobile. 2 .A MS with a higher coding scheme is preferred. {4445} This parameter is only available at the BSC. Syntax Change command string chg_element gprs_sched_beta <value> 0 Display command string disp_element gprs_sched_beta 0 Value Value type Integer Valid range 0 to 2 Default value 68P02901W23-P 23 Feb 2004 0 Each MS throughput in bit/s is the same.Technical Description BSS Command Reference gprs_sched_beta gprs_sched_beta Description The gprs_sched_beta parameter sets the scheduling beta algorithm at the BSS. 1 5-317 GMR-01 . 1 Each MS transfers the same number of blocks as every other mobile. 2 MS with higher coding scheme is preferred.Each MS throughput in bits per second (bit/s) is the same 1 . Type A (no operator actions) Supported by OMC-R GUI Yes (Read-Write) Cell description required No Dependencies The GPRS feature must be unrestricted. The possible algorithms are: 0 . Syntax Change command string chg_element gprs_sig_bvci <value> pcu Display command string disp_element gprs_sig_bvci pcu Values Value type Integer Valid range 0 to 65535 Default value 0 5-318 GMR-01 68P02901W23-P 23 Feb 2004 .gprs_sig_bvci Chapter 5: CM database parameters gprs_sig_bvci Description The gprs_sig_bvci parameter specifies the BVCI of the signalling source used with GBLs. BSS software processes using this parameter are notified immediately after the change is made. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required No Dependencies The GPRS feature must be unrestricted. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required Yes Dependencies The PBCCH/PCCCH optional feature must be unrestricted. When more than one cell is available for reselection. the MS reselects the cell with the highest C32 value. C32 is the reselection priority assigned to a cell which can be broadcast on the BCCH of each cell. Syntax Add/Change command strings chg_element gprs_temporary_offset <value> <location> <cell_desc> chg_cell_element gprs_temporary_offset <value> <cell_desc> Display command strings disp_cell <cell_number> “full" disp_element gprs_temporary_offset <location> <cell_desc> Values Value type Integer Valid range 0 to 7 68P02901W23-P 23 Feb 2004 0 0 dB 1 10 dB 2 20 dB 5-319 GMR-01 . It is used to apply a negative offset to C32 for the duration of the gprs_penalty_time parameter.Technical Description BSS Command Reference gprs_temporary_offset gprs_temporary_offset {3723} 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. gprs_temporary_offset Default value Chapter 5: CM database parameters 3 30 dB 4 40 dB 5 50 dB 6 60 dB 7 Infinity 0 5-320 GMR-01 68P02901W23-P 23 Feb 2004 . • Customer specified algorithm .GPRS resources configured for performance by the PCU. 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.Technical Description BSS Command Reference gprs_ts_config_alg gprs_ts_config_alg Description The gprs_ts_config_alg parameter specifies the algorithm used to allocate switchable and reserved GPRS timeslots. To set this parameter at a TTY terminal. GPRS must first be disabled and then enabled. Enough timeslots must be available on all of the GPRS cell carriers. BSS software processes using this parameter are notified immediately after the change is made. There are two options: • PCU performance algorithm . GPRS must first be disabled.operator can configure GPRS resources on a per cell basis. Syntax Change command strings chg_element gprs_ts_config_alg <value> <location> <cell_desc> chg_cell_element gprs_ts_config_alg <value> <cell_desc> 68P02901W23-P 23 Feb 2004 5-321 GMR-01 . Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required Yes Dependencies The GPRS feature must be unrestricted. gprs_ts_config_alg Chapter 5: CM database parameters Display command strings disp_cell <cell_desc> "full" disp_element gprs_ts_config_alg <location> <cell_desc> Values Value type Integer Valid range 0 or 1 Default value 0 PCU performance algorithm 1 Customer specified algorithm 0 5-322 GMR-01 68P02901W23-P 23 Feb 2004 . Technical Description BSS Command Reference gprs_ul_dl_bias gprs_ul_dl_bias {4441} 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 Change command strings chg_element gprs_ul_dl_bias <value> <location> Display command strings disp_element gprs_ul_dl_bias <location> Values Value type Integer Valid range 0 to 1 Default value 68P02901W23-P 23 Feb 2004 0 UL bias 1 DL bias 1 5-323 GMR-01 . Type A (no operator actions) Supported by OMC-R GUI Yes Cell description required No Dependencies GPRS must be unrestricted. by enabling support of the group blocking/unblocking procedure. Syntax Change command string chg_element group_block_unblock_allowed <value> 0 Display command string disp_element group_block_unblock_allowed 0 Values Value type Boolean Valid range 0 or 1 5-324 GMR-01 68P02901W23-P 23 Feb 2004 . the following ‘single circuit block’ messages are sent to the MSC: • Block • Unblock Type A (no operator actions) Supported by OMC-R GUI Yes Cell description required No Dependencies This parameter is only valid at the BSC.group_block_unblock_allowed Chapter 5: CM database parameters group_block_unblock_allowed Description The group_block_unblock_allowed parameter allows the operator to make the A interface more efficient. the following ‘group block’ messages are sent to the MSC: • Circuit Group Block • Circuit Group Unblock If this parameter is disabled. If this parameter is enabled. This parameter does not apply to RXCDR sites. if MSC supports circuit group block and unblock messages. Technical Description BSS Command Reference Default value group_block_unblock_allowed 0 Disabled .BSS sends only ‘single circuit block/unblock’ messages to the MSC. 1 Enabled . None References GSM specification 68P02901W23-P 23 Feb 2004 TS GSM 8.08 This is a Motorola defined parameter. 5-325 GMR-01 .BSS sends only ‘group block/unblock’ messages to the MSC. BSS software processes using this parameter are notified immediately after the change is made.gsl_lcf_mapping Chapter 5: CM database parameters gsl_lcf_mapping {4040} 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. Syntax Change command strings chg_element gsl_lcf_mapping <value> bsc Display command string disp_element gsl_lcf_mapping bsc Values Value type Boolean Valid range 0 or 1 0 Manual mode 1 Auto mode 5-326 GMR-01 68P02901W23-P 23 Feb 2004 . Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required No Dependencies The GPRS feature must be unrestricted. the operator is prompted to specify the LCF during equipage of a GSL. The system must be in SYSGEN mode. 0 cannot be set) 0 Outside SYSGEN (Manual mode) 5-327 GMR-01 .Technical Description BSS Command Reference Default value 68P02901W23-P 23 Feb 2004 gsl_lcf_mapping 1 Inside SYSGEN (Auto mode . gsm_cell_id_format Chapter 5: CM database parameters gsm_cell_id_format Description The gsm_cell_id_format parameter specifies the format of the GSM Cell Identification sent by the Call Processor (CP) to the switch. Syntax Change command string chg_element gsm_cell_id_format <value> 0 Display command string disp_element gsm_cell_id_format 0 Values Value type Integer Valid range 0 to 2 Default value 0 Whole Cell Global Identification (CGI) 1 Location Area Code (LAC). Type A (no operator actions) Supported by OMC-R GUI Yes Cell description required No Dependencies This parameter can be set only at the BSC. and Cell Identity (CI) 2 Cell Identity (CI) 1 5-328 GMR-01 68P02901W23-P 23 Feb 2004 . 5-329 GMR-01 .Radio Network Controller Identity.Cell Identity.2. UTRAN Cell IDs are required parameter entries for these commands. del_neighbor and disp_neighbor. • CI . The UTRAN cell ID format consists of five fields: • MCC .Location Area Code. • RNC .Mobile Network Code. This is set up using the neighbour commands: add_neighbor.08 . • LAC . modify_neighbor. • MNC .3.Mobile Country Code.27 This is a Motorola defined parameter.2.Technical Description BSS Command Reference gsm_cell_id_format UTRAN Cell Identifier It is possible to hand over calls to 3G UMTS UTRAN cells. 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 68P02901W23-P 23 Feb 2004 GSM TS 8. The maximum value for a DCS1800 system is 15. 5-330 GMR-01 68P02901W23-P 23 Feb 2004 .handover_power_level Chapter 5: CM database parameters handover_power_level Description The handover_power_level parameter defines the power control level to be used by an MS during a handover to a different cell. Syntax Add/Change command strings add_cell <gsm_cell_id> <location> chg_element handover_power_level <value> <location> <cell_desc> chg_cell_element <location> handover_power_level <value> <cell_desc> Display command strings disp_cell <cell_desc> ["full"] 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. Type A (no operator actions) Supported by OMC-R GUI Yes Cell description required Yes Dependencies The maximum value for a PGSM or EGSM system is 19. Technical Description BSS Command Reference Table 5-15 handover_power_level Max MS power level for PGSM and EGSM Value Power level Value Power level 2 39 dBm 11 21 dBm 3 37 dBm 12 19 dBm 4 35 dBm 13 17 dBm 5 33 dBm 14 15 dBm 6 31 dBm 15 13 dBm 7 29 dBm 16 11 dBm 8 27 dBm 17 9 dBm 9 25 dBm 18 7 dBm 10 23 dBm 19 5 dBm Table 5-16 lists the maximum mobile power level for DCS1800 and PCS1900 cells. Table 5-17 Max MS power level for class 3 mobiles Value Power level Value Power level 29 36 dBm 31 32 dBm 30 34 dBm Default value 68P02901W23-P 23 Feb 2004 2 5-331 GMR-01 . Table 5-16 Max MS power level for DCS1800 and PCS1900 cells Value Power level Value Power level 0 30 dBm 8 14 dBm 1 28 dBm 9 12 dBm 2 26 dBm 10 10 dBm 3 24 dBm 11 8 dBm 4 22 dBm 12 6 dBm 5 20 dBm 13 4 dBm 6 18 dBm 14 2 dBm 7 16 dBm 15 0 dBm Table 5-17 lists the maximum mobile power level for DCS1800 and PCS1900 cells for class 3 mobiles. 5-332 GMR-01 68P02901W23-P 23 Feb 2004 .1.05 .4.1 This is a Motorola defined parameter.handover_power_level Chapter 5: CM database parameters References GSM specification 5. This parameter should conform to the MSC capabilities.Technical Description BSS Command Reference handover_required_curr_ch 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. Syntax Change command string chg_element handover_required_curr_ch <value> 0 Display command string disp_element handover_required_curr_ch 0 Values Value type Boolean Valid range 0 or 1 Default value 68P02901W23-P 23 Feb 2004 0 Not included 1 Included 1 5-333 GMR-01 . Type A (no operator actions) Supported by OMC-R GUI Yes Cell description required No Dependencies This parameter only applies to the BSC. 08 This is a Motorola defined parameter. 5-334 GMR-01 68P02901W23-P 23 Feb 2004 .handover_required_curr_ch Chapter 5: CM database parameters References GSM specification TS GSM 08. 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. the BSS expects to receive a Handover Required Reject message from the switch. Syntax Change command string chg_element handover_required_reject_switch <value> 0 Display command string disp_element handover_required_reject_switch 0 Values Value type Boolean Valid range 0 or 1 Default value 68P02901W23-P 23 Feb 2004 0 Disabled (reject message not required) 1 Enabled (reject message required) 0 5-335 GMR-01 .Technical Description BSS Command Reference handover_required_reject_switch 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. Type A (no operator actions) Supported by OMC-R GUI Yes Cell description required No Dependencies This parameter only applies to the BSC. 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 enabled (set to 1). If the handover_required_reject_switch is disabled (set to 0). Any internal cells that are candidates for the handover will not be included in the Handover Required message. 5.2.1.08 .5. 8.5: Hand Req Reject 5-336 GMR-01 68P02901W23-P 23 Feb 2004 .7.1.08 .1: Response request in a HANDOVER REQUIRED.3.Figures 4 and 5.handover_required_reject_switch Chapter 5: CM database parameters References GSM parameter HAND_REQ_REJECT GSM specification 8. 12.20 . 5-337 GMR-01 .Technical Description BSS Command Reference handover_required_sp_ver_used 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. References GSM specification 68P02901W23-P 23 Feb 2004 TS GSM 8. Enabled (built in speech version).08 This is a Motorola defined parameter. Syntax Change command string chg_element handover_required_sp_ver_used <value> 0 Display command string disp_element handover_required_sp_ver_used 0 Values Value type Boolean Valid range 0 1 Default value 0 Disabled (no speech version). Type A (no operator actions) Supported by OMC-R GUI Yes Cell description required No Dependencies The handover_required_sp_ver_used parameter cannot be disabled (0) if efr_enabled is enabled (1). This parameter applies only to the BSC. Syntax Add/Change command strings chg_element hcs_thr <value> <location> <cell_desc> chg_cell_element hcs_thr <value> <cell_desc> Display command strings disp_cell <cell_desc> "full" disp_element hcs_thr <location> <cell_desc> Values Value type Integer Valid range 0 to 31 Represents signal strength threshold in 2 dBm steps: 0 -110 dBm 1 -108 dBm .hcs_thr Chapter 5: CM database parameters hcs_thr {3723} Description The hcs_thr parameter specifies the Hierarchical Cell Structure (HCS) signal strength threshold for a cell. ... If the local_maintenance flag is disabled.. Type A (no operator actions) Supported by OMC-R GUI Yes Cell description required Yes Dependencies The PBCCH/PCCCH feature must be unrestricted. 5-338 GMR-01 68P02901W23-P 23 Feb 2004 . The signal strength threshold can be changed in 2 dBm steps.. the MMI is prevented from changing this item. Technical Description BSS Command Reference 31 Default value 68P02901W23-P 23 Feb 2004 hcs_thr -48 dBm 0 5-339 GMR-01 . Type A (no operator actions) Supported by OMC-R GUI Yes Cell description required No Dependencies This parameter may only be changed if the HDSL feature is unrestricted. Horizonmicro or Horizoncompact site. Syntax Change command string chg_element hdsl_losw_oos <value> <location> Display command string disp_element hdsl_losw_oos <location> Values Value type Integer (seconds) Valid range 0 to 3598 Default value 6 5-340 GMR-01 68P02901W23-P 23 Feb 2004 . Changing this parameter affects all master modems equipped as msi_type niu_hdsl at the local M-Cell site. This parameter may only be changed at an M-Cellcity. The system takes the HDSL link out of service if the sync word is not received for the hdsl_losw_oos period.hdsl_losw_oos Chapter 5: CM database parameters hdsl_losw_oos Description The hdsl_losw_oos parameter specifies the HDSL Loss of Sync Word (LOSW) out of service (OOS) alarm period. All slave modem alarm thresholds are identical to the master modem alarm thresholds. Technical Description BSS Command Reference hdsl_losw_restore hdsl_losw_restore Description The hdsl_losw_restore parameter defines the HDSL Loss of Sync Word (LOSW) restoration period. Changing this parameter affects all master modems equipped as msi_type niu_hdsl at the local M-Cell site. If the sync word is received for the hdsl_losw_restore_period. Syntax Change command string chg_element hdsl_losw_restore <value> <location> Display command string disp_element hdsl_losw_restore <location> Values Value type Integer (seconds) Valid range 0 to 65534 Default value 6 68P02901W23-P 23 Feb 2004 5-341 GMR-01 . the system restores the HDSL link back into service (INS). This parameter may only be changed at an M-Cellcity. All slave modem alarm thresholds are identical to the master modem alarm thresholds. Horizonmicro or Horizoncompact site. Type A (no operator actions) Supported by OMC-R GUI Yes Cell description required No Dependencies This parameter may only be changed if the HDSL option is unrestricted. Changing this parameter affects all master modems equipped as msi_type niu_hdsl at the local M-Cell site.5 dB steps) 6 to 44 Represents 3 dB to 22 dB. This parameter may only be changed at an M-Cellcity. as shown below: 6 3 dB 7 3. 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. Syntax Change command string chg_element hdsl_snr_daily <value> <location> Display command string disp_element hdsl_snr_daily <location> Values Value type Valid range Integer (representing 0. Type A (no operator actions) Supported by OMC-R GUI Yes Cell description required No Dependencies This parameter may only be changed if the HDSL option is unrestricted.hdsl_snr_daily Chapter 5: CM database parameters hdsl_snr_daily Description The hdsl_snr_daily parameter defines the HDSL Signal to Noise Ratio (SNR) daily alarm level. a daily alarm is generated.5 dB 8 4 dB 5-342 GMR-01 68P02901W23-P 23 Feb 2004 . Horizonmicro or Horizoncompact site. All slave modem alarm thresholds are identical to the master modem alarm thresholds. .. . .....Technical Description BSS Command Reference Default value 68P02901W23-P 23 Feb 2004 hdsl_snr_daily .... ... 44 22 dB 16 (8 dB) 5-343 GMR-01 . .. . This parameter may only be changed at an M-Cellcity. Syntax Change command string chg_element hdsl_snr_daily_mon_period <value> <location> Display command string disp_element hdsl_snr_daily_mon_period <location> Values Value type Integer (seconds) Valid range 0 to 65534 Default value 20 5-344 GMR-01 68P02901W23-P 23 Feb 2004 . All slave modem alarm thresholds are identical to the master modem alarm thresholds. 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.hdsl_snr_daily_mon_period Chapter 5: CM database parameters 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). Horizonmicro or Horizoncompact site. Type A (no operator actions) Supported by OMC-R GUI Yes Cell description required No Dependencies This parameter may only be changed if the HDSL option is unrestricted. Changing this parameter affects all master modems equipped as msi_type niu_hdsl at the local M-Cell site. a daily alarm is generated. All slave modem alarm thresholds are identical to the master modem alarm thresholds. Changing this parameter affects all master modems equipped as msi_type niu_hdsl at the local M-Cell site. Type A (no operator actions) Supported by OMC-R GUI Yes Cell description required No Dependencies This parameter may only be changed if the HDSL option is unrestricted. 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. Horizonmicro or Horizoncompact site. as shown below: 8 4 dB 9 4. Syntax Change command string chg_element hdsl_snr_hourly <value> <location> Display command string disp_element hdsl_snr_hourly <location> Values Value type Integer (representing 0. This parameter may only be changed at an M-Cellcity.Technical Description BSS Command Reference hdsl_snr_hourly hdsl_snr_hourly Description The hdsl_snr_hourly parameter sets the threshold period for the hourly signal to noise ratio (SNR).5 dB 10 5 dB 68P02901W23-P 23 Feb 2004 5-345 GMR-01 .5dB steps) Valid range 8 to 44 Represents 4 dB to 22 dB. an hourly alarm is generated. . .. .. .hdsl_snr_hourly Chapter 5: CM database parameters Default value . 44 22 dB 18 (9 dB) 5-346 GMR-01 68P02901W23-P 23 Feb 2004 .. ..... ..... This parameter may only be changed at an M-Cellcity. an hourly alarm is generated.Technical Description BSS Command Reference hdsl_snr_hourly_mon_period 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). All slave modem alarm thresholds are identical to the master modem alarm thresholds. Horizonmicro or Horizoncompact site. Syntax Change command string chg_element hdsl_snr_hourly_mon_period <value> <location> Display command string disp_element hdsl_snr_hourly_mon_period <location> Values Value type Integer (seconds) Valid range 0 to 3598 Default value 20 68P02901W23-P 23 Feb 2004 5-347 GMR-01 . 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. Type A (no operator actions) Supported by OMC-R GUI Yes Cell description required No Dependencies This parameter may only be changed if the HDSL option is unrestricted. Changing this parameter affects all master modems equipped as msi_type niu_hdsl at the local M-Cellcity or Horizonmicro site. If the SNR level drops below the hdsl_snr_oos threshold for more than hdsl_oos_mon_period. The SNL level is continuously monitored by the system. Syntax Change command string chg_element hdsl_snr_oos <value> <location> Display command string disp_element hdsl_snr_oos <location> 5-348 GMR-01 68P02901W23-P 23 Feb 2004 . Changing this parameter affects all master modems equipped as msi_type niu_hdsl at the local M-Cell site. The hdsl_snr_oos threshold must be lower than the hdsl_snr_restore threshold. Horizonmicro or Horizoncompact site. All slave modem alarm thresholds are identical to the master modem alarm thresholds. This parameter may be changed only at an M-Cellcity. the HDSL link is taken Out Of Service (OOS).hdsl_snr_oos Chapter 5: CM database parameters hdsl_snr_oos Description The hdsl_snr_oos parameter specifies the SNR threshold level for the HDSL Signal to Noise Ratio (SNR). Type A (no operator actions) Supported by OMC-R GUI Yes Cell description required No Dependencies This parameter may be changed only if the HDSL option is unrestricted. ..... . .5dB steps) 6 to 44 Represents 3 dB to 22 dB. .. 44 22 dB 14 (7 dB) 14 (7 dB) 5-349 GMR-01 . ...Technical Description BSS Command Reference hdsl_snr_oos Values Value type Valid range Default value Default value 68P02901W23-P 23 Feb 2004 Integer (0. as shown below: 6 3 dB 7 3. .5 dB 8 4 dB ..... Syntax Change command string chg_element hdsl_snr_restore <value> <location> Display command string disp_element hdsl_snr_restore <location> 5-350 GMR-01 68P02901W23-P 23 Feb 2004 . the HDSL link is restored to service. All slave modem alarm thresholds are identical to the master modem alarm thresholds. If the SNR level rises above the hdsl_snr_restore threshold for more than hdsl_oos_mon_period. This parameter may be changed only at an M-Cellcity. Horizonmicro or Horizoncompact site. The hdsl_snr_oos threshold must be lower than the hdsl_snr_restore threshold. Type A (no operator actions) Supported by OMC-R GUI Yes Cell description required No Dependencies This parameter may only be changed if the HDSL option is unrestricted. The SNL level is continuously monitored by the system.hdsl_snr_restore Chapter 5: CM database parameters hdsl_snr_restore Description The hdsl_snr_restore parameter specifies the SNR threshold level for the HDSL Signal to Noise Ratio (SNR). Changing this parameter affects all master modems equipped as msi_type niu_hdsl at the local M-Cell site. ..5dB steps) 6 to 44 Represents 3 dB to 22 dB.. .. as shown below: 6 3 dB 7 3.Technical Description BSS Command Reference hdsl_snr_restore Values Value type Valid range Default value 68P02901W23-P 23 Feb 2004 Integer (0.. . .... 44 22 dB 16 (8 dB) 5-351 GMR-01 . ....5 dB 8 4 dB .. . The available options are: Attempt to handover as many calls as the number of queued assignment requests.ho_exist_congest Chapter 5: CM database parameters 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. No handover attempts (for this condition). The MSC may need to increase the timer waiting for the Assignment Complete message from the BSS when this database parameter is enabled. Type A (no operator actions) Supported by OMC-R GUI Yes Cell description required Yes Dependencies Congestion Relief feature is required. Attempt to handover as many calls as meet the congestion handover criteria. Syntax Change command strings chg_element ho_exist_congest <value> <location> <cell_desc> chg_cell_element ho_exist_congest <value> <cell_desc> Display command strings disp_cell <cell_desc> "full" disp_element ho_exist_congest <location> <cell_desc> 5-352 GMR-01 68P02901W23-P 23 Feb 2004 . This parameter will be copied if the copy_cell command is used. 5-353 GMR-01 .Technical Description BSS Command Reference ho_exist_congest Values Value type Integer Valid range 0 to 2 Default value 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 0 References GSM specification 68P02901W23-P 23 Feb 2004 TS GSM 08.08 This is a Motorola defined parameter. the following equation must be true: If PBGT(n) > ho_margin(n) then a handover may be required. The neighbour handover margin is set using the add_neighbor command and changed using the modify_neighbor command. Type A (no operator actions) Supported by OMC-R GUI Yes Cell description required Yes Dependencies None Syntax Add/Change command strings add_cell <gsm_cell_id> <location> chg_element ho_margin_def <value> <location> <cell_desc> chg_cell_element ho_margin_def <value> <cell_desc> Display command strings disp_cell <cell_desc> ["full"] disp_element ho_margin_def <location> <cell_desc> Values Value type Integer (dB) Valid range -63 to +63 Default value 8 5-354 GMR-01 68P02901W23-P 23 Feb 2004 .ho_margin_def Chapter 5: CM database parameters 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 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. Appendix A .8.2.5.08 . 3.ho Margin Celln 12.20 . and section 3.20 .4 adjacent Cell Handover .5.Technical Description BSS Command Reference ho_margin_def References GSM parameter HO_MARGIN_DEF GSM specification 5. 5.8.Appendix A.20 .1f: PBGT(n) .2e.8.2.2 68P02901W23-P 23 Feb 2004 5-355 GMR-01 .2.08 .2.5.4 adjacent Cell Handover .ho Margin Default 12.Table 1 12. Type A (no operator action) Supported by OMC-R GUI Yes Cell description required Yes Dependencies None Syntax Change command string modify_neighbor <src_cell_id> <neighbor_cell_id> ho_margin_type5 <value> Display command strings disp_neighbor <src_cell_desc> [<neighbor_cell_id>|“all"] disp_neighbor "<source cell_name>" ["<internal neighbour cell_name>"] disp_neighbor <src_cell_desc> [TEST <test neighbor_cell_id>] Values Value type Integer (dBm) Valid range -63 to +63 Default value 63 5-356 GMR-01 68P02901W23-P 23 Feb 2004 .ho_margin_type5 Chapter 5: CM database parameters ho_margin_type5 Description The ho_margin_type5 parameter sets the power budget type 5 handover margin. Technical Description BSS Command Reference ho_margin_usage_flag ho_margin_usage_flag Description The ho_margin_usage_flag parameter determines which sorting algorithm the system uses to sort the neighbour list. • All other handover causes that have neighbours are sorted using ho_margin_cell value. 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]. If ho_margin_usage_flag is disabled. Type A (no operator action) Supported by OMC-R GUI Yes Cell description required Yes Dependencies None Syntax Add/Change command strings chg_element ho_margin_usage_flag <value> <location> <cell_desc> chg_cell_element ho_margin_usage_flag <value> <cell_desc> Display command strings disp_cell <cell_desc> "full" disp_element ho_margin_usage_flag <location> <cell_desc> Values Value type Integer Valid range 0 or 1 68P02901W23-P 23 Feb 2004 5-357 GMR-01 . handover candidates are always sorted using ho_margin_cell. ho_margin_usage_flag Default value Chapter 5: CM database parameters 0 Disabled 1 Enabled 0 5-358 GMR-01 68P02901W23-P 23 Feb 2004 . If this option is enabled: • The MS must be at full power for an uplink handover. to allow the MS or BTS to reach full power. the decision_alg_type parameter must equal 1. Type A (no operator actions) Supported by OMC-R GUI Yes Cell description required Yes Dependencies To use the ho_only_max_pwr parameter. • The BTS must be at full power for a downlink handover.Technical Description BSS Command Reference ho_only_max_pwr 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. Syntax Change command strings chg_element ho_only_max_pwr <value> <location> <cell_desc> chg_cell_element ho_only_max_pwr <value> <cell_desc> Display command strings disp_cell <cell_desc> "full" disp_element ho_only_max_pwr <location> <cell_desc> Values Value type Boolean Valid range 0 or 1 0 68P02901W23-P 23 Feb 2004 Disabled 5-359 GMR-01 . ho_only_max_pwr Chapter 5: CM database parameters 1 Default value Enabled 0 5-360 GMR-01 68P02901W23-P 23 Feb 2004 . Type A (no operator action) Supported by OMC-R GUI Yes Cell description required Yes Dependencies The Dual Band Cells feature must be unrestricted. The element handover_power_level does not apply to intra-cell handovers. The valid range for this parameter depends on the frequency of the inner zone. 68P02901W23-P 23 Feb 2004 5-361 GMR-01 . Syntax Change command strings chg_element ho_pwr_level_inner <value> <location> <cell_desc> chg_cell_element ho_pwr_level_inner <value> <cell_desc> Display command strings disp_cell <cell_desc> "full" 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.Technical Description BSS Command Reference ho_pwr_level_inner ho_pwr_level_inner Description The ho_pwr_level_inner parameter specifies the handover power level for the inner zone of a Dual Band cell for an inter-cell handover. ho_pwr_level_inner Chapter 5: CM database parameters Table 5-18 Max MS power level for PGSM and EGSM cells Value Power level Value Power level 2 39 dBm 11 21 dBm 3 37 dBm 12 19 dBm 4 35 dBm 13 17 dBm 5 33 dBm 14 15 dBm 6 31 dBm 15 13 dBm 7 29 dBm 16 11 dBm 8 27 dBm 17 9 dBm 9 25 dBm 18 7 dBm 10 23 dBm 19 5 dBm Table 5-19 the maximum mobile power level for DCS1800 and PCS1900 cells. Table 5-19 Max MS power level for DCS1800 and PCS1900 cells Value Power level Value Power level 0 30 dBm 8 14 dBm 1 28 dBm 9 12 dBm 2 26 dBm 10 10 dBm 3 24 dBm 11 8 dBm 4 22 dBm 12 6 dBm 5 20 dBm 13 4 dBm 6 18 dBm 14 2 dBm 7 16 dBm 15 0 dBm Table 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 Value Power level Value Power level 29 36 dBm 31 32 dBm 30 34 dBm Default value 2 5-362 GMR-01 68P02901W23-P 23 Feb 2004 . combined with the hop_count_timer parameter. If the number of handovers defined by the hop_count parameter occur within the time set by the hop_count_timer. limits the number of intra-cell interference handovers for a call. The hop_count parameter sets the number of handovers.Technical Description BSS Command Reference hop_count hop_count Description The hop_count parameter. the system escalates the handover to a RXQUAL handover to another cell. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required Yes Dependencies None Syntax Change command strings chg_element hop_count <value> <location> <cell_desc> chg_cell_element hop_count <value> <cell_desc> Display command strings disp_cell <cell_desc> "full" disp_element hop_count <location> <cell_desc> Values Value type Integer (quantity of intra-cell interference handovers) Valid range 0 to 255 (0 disables intra-cell interference handovers) Default value 255 68P02901W23-P 23 Feb 2004 5-363 GMR-01 . If hop_qual_enabled is enabled and a hopping call is in progress. whereas hopping calls can provide the same quality of service with the reported rxqual value at 6 or 7. Type A (no operator action required) Supported by OMC-R GUI Yes Cell description required Yes Dependencies alt_qual_proc Syntax Change command string chg_cell_element hop_qual_enabled <value> <cell_desc> 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-408 • "l_rxqual_ul_h" on page 5-432 • "l_rxqual_dl_p" on page 5-420 5-364 GMR-01 68P02901W23-P 23 Feb 2004 . Trials have shown that non-hopping calls can show poor quality of service when the reported rxqual value is around 5.hop_qual_enabled Chapter 5: CM database parameters hop_qual_enabled Description The hop_qual_enabled parameter enables or disables the use of specific rxqual thresholds for hopping call handovers. If hop_qual_enabled is disabled. If both hop_qual_enabled and data_qual_enabled are enabled. the system uses the rxqual values set with the chg_cell_element command (see Syntax below). the normal rxqual values set with the add_cell command are used. data_qual_enabled takes precedence for data transmission in a hopping call. Technical Description BSS Command Reference • hop_qual_enabled "l_rxqual_ul_p" on page 5-444 Display command strings disp_cell <cell_desc> "full" disp_element hop_qual_enabled <location> <cell_desc> Values Value type Integer Valid range 0 to 1 Default value 68P02901W23-P 23 Feb 2004 0 Disabled 1 Enabled 0 5-365 GMR-01 . The combination losses associated with this technique must be acceptable. Synthesizer Frequency Hopping This is accomplished by the high speed switching of the transmit and receive frequency synthesizers of the individual transceivers. Using the chg_hop_params (see "chg_hop_params" on page 2-101) command to change the hopping system does not require SYSGEN ON. As a result of the dynamic nature of the transmit frequency. The frequency hopping set (mobile allocation. Baseband Frequency Hopping This is accomplished by routing the traffic channel data through fixed frequency transceivers via the TDM highway on a timeslot basis.hopping_support Chapter 5: CM database parameters hopping_support Description The hopping_support parameter defines the frequency hopping in a cell. or hybrid combiners. Syntax Change command strings chg_element hopping_support <value> <location> <cell_desc> chg_cell_element hopping_support <value> <cell_desc> 5-366 GMR-01 68P02901W23-P 23 Feb 2004 . In this case. Two methods of achieving frequency hopping are available. broadband (hybrid) combining of the transmitters is necessary. The frequency hopping technique employed is dependent upon the losses specific cells can tolerate in their transmit paths. the transceiver would have fixed tuned transmitters combined either in low loss tuned combiners. and the number of transceivers associated with specific cells. Type B (operator action required) Supported by OMC-R GUI Yes Cell description required Yes Dependencies None Operator actions Place the system in the SYSGEN ON mode before using the chg_element or chg_cell_element commands to change this parameter. MA) is limited to the number of transceivers equipped at a specific site. Technical Description BSS Command Reference hopping_support Display command strings disp_cell <cell_desc> "full" disp_element hopping_support <location> <cell_desc> Values Value type Integer Valid range 0 to 2 Default value 0 No hopping in this cell 1 Synthesizer hopping 2 Baseband hopping 0 References GSM specification 68P02901W23-P 23 Feb 2004 Motorola GSM B1 document .2.4.01 .1 5. 5-367 GMR-01 .6 This is a Motorola defined parameter. Type B (operator action required) Supported by OMC-R GUI Yes Cell description required Yes Dependencies None Operator actions The system must be in SYSGEN ON mode to change this parameter with the chg_element or chg_cell_element commands. Syntax Change command strings chg_element hopping_systems_enabled.<index> <value> <cell_desc> Display command strings disp_cell <cell_desc> <"full"> disp_element hopping_systems_enabled. Using the chg_hop_params (see "chg_hop_params" on page 2-101) command to change the hopping system does not require SYSGEN ON.<index> <location> <cell_desc> disp_hopping <cell_desc> [<fhi> | "active"] 5-368 GMR-01 68P02901W23-P 23 Feb 2004 . An index number (fhi) is required.<index> <value> <location> <cell_desc> chg_cell_element hopping_systems_enabled. The range of values. The frequency hopping indicator (fhi) value specifies which hopping system is affected.hopping_systems_enabled Chapter 5: CM database parameters hopping_systems_enabled Description The hopping_systems_enabled parameter enables or disables a frequency hopping system. entered as <index> is 0 to 3. 5-369 GMR-01 .01 .Technical Description BSS Command Reference hopping_systems_enabled Values Value type Boolean Valid range 0 or 1 Default value 0 Disabled 1 Enabled None References GSM specification 68P02901W23-P 23 Feb 2004 5.6 This is a Motorola defined parameter. The frequency hopping indicator (fhi) value specifies which hopping system is affected. An index number (fhi) is required. The range of values. HSN is one of seven parameters that defines a particular physical channel in a BTS. Type B (operator action required) Supported by OMC-R GUI Yes Cell description required Yes Dependencies None Operator actions Respond to the SITE reset prompt which will be displayed after the chg_element command is entered to modify this parameter. Syntax Change command strings chg_element hopping_systems_hsn. entered as <index> is 0 to 3.hopping_systems_hsn Chapter 5: CM database parameters hopping_systems_hsn Description The hopping_systems_hsn parameter specifies the hopping sequence (generator) number (HSN) to be used by the frequency hopping system.<index> <location> <cell_desc> disp_hopping <cell_desc> [<fhi> | "active"] Values Value type Integer Valid range 0 to 63 5-370 GMR-01 68P02901W23-P 23 Feb 2004 .<index> <value> <location> <cell_desc> chg_cell_element hopping_systems_hsn <value> <cell_desc> Display command strings disp_cell <cell_desc> "full" disp_element hopping_systems_hsn. 6 68P02901W23-P 23 Feb 2004 5-371 GMR-01 . None References GSM parameter HSN GSM specification 5.02 .02 .2. 6.2.6. 5.3 5.2. 1 to 63 Random hopping.Technical Description BSS Command Reference Default value hopping_systems_hsn 0 Cyclic hopping.01 . HSN and MA are entries to the algorithm table 6 of GSM Rec.02. and then the cycle repeats. 6.5.3. The MA is hopped through lowest to highest magnitude.table 6: hopping algorithm 5. <index2> <location> <cell_desc> 5-372 GMR-01 68P02901W23-P 23 Feb 2004 .<index1>. The system does not check for errors when changes are made in SYSGEN ON mode. chg_hopping must be executed in SYSGEN_ON mode. Dependencies Refer to the descriptions for the chg_hop_params command (see "chg_hop_params" on page 2-101) for restrictions on changing the hopping parameters. Required for disp_cell and disp_element commands. Display command strings disp_cell <cell_desc> "full" disp_element hopping_systems_mobile_alloc. however. Syntax Change command strings chg_hop_params <location> chg_hop_params <cell_desc> chg_hop_params can be used in SYSGEN or out of SYSGEN. When SYSGEN is turned off. Type A (no operator actions) Supported by OMC-R GUI Yes Cell description required Not required for chg_hop_params command. and may reject the command. the system does check for errors.hopping_systems_mobile_alloc Chapter 5: CM database parameters hopping_systems_mobile_alloc Description The hopping_systems_mobile_alloc parameter allocates the Absolute Radio Frequency Channel Number (ARFCN) frequencies for hopping (either baseband hopping or synthesizer hopping). For PGSM. the range is 1 through 124. 975 to 1023. the range is either: 1 to 124. References GSM specification 68P02901W23-P 23 Feb 2004 5.Technical Description BSS Command Reference hopping_systems_mobile_alloc disp_hopping <site> ["active"] disp_hopping <cell_desc> [<fhi> | “active"] Values Value type Integer Valid range Variable Default value None ARFCN depends on the frequency type for the cell. or 0. For PCS1900 the range is 512 to 810. For DCS1800.01 . For EGSM. 5-373 GMR-01 . the range is 512 to 885.6 This is a Motorola defined parameter. If the value is not changed. Syntax Change command string chg_element illegal_circuit_id <value> 0 Display command string disp_element illegal_circuit_id 0 Values Value type Integer Valid range 0 to 65535 Default value 0 5-374 GMR-01 68P02901W23-P 23 Feb 2004 . The value may be changed to permit a customer to specify the circuit ID to be used as the illegal_circuit_id. Type A (no operator actions) Supported by OMC-R GUI Yes Cell description required No Dependencies This parameter only applies to the BSC. a Motorola specified illegal_circuit_id is assigned.illegal_circuit_id Chapter 5: CM database parameters illegal_circuit_id Description The illegal_circuit_id parameter is used as an internal place holder in call processing to show that no circuit has been assigned to a call. If all TCHs are busy. For emergency calls. If this parameter is set to disabled. If this parameter is enabled. Type A (no operator actions) Supported by OMC-R GUI Yes Cell description required Yes Dependencies None Syntax Change command strings chg_element immediate_assign_mode <value> <location> <cell_desc> chg_cell_element immediate_assign_mode <value> <cell_desc> Display command strings disp_cell <cell_desc> "full" disp_element immediate_assign_mode <location> <cell_desc> 68P02901W23-P 23 Feb 2004 5-375 GMR-01 . This parameter also determines the type of channel that is assigned to immediate channel requests for emergency calls. If this parameter is set to 2. TSCs are not allocated for a location update. TSCs are allocated for any reason. immediate channel requests are either rejected or discarded if there is no SDCCH available for both normal and emergency calls. idle TCH is searched and allocated for immediate channel requests after all SDCCHs are busy for normal calls. a TCH is allocated if one is idle. an SDCCH is allocated for the emergency call.Technical Description BSS Command Reference immediate_assign_mode immediate_assign_mode Description The immediate_assign_mode parameter specifies how the system responds when no Standalone Dedicated Control Channels (SDCCHs) are available. If this parameter is set to 1. immediate_assign_mode Chapter 5: CM database parameters Values Value type Integer Valid range 0 to 255 Default value 0 Disabled 1 Allocate TSC for any reason 2 Do not allocate TCH for location update 0 5-376 GMR-01 68P02901W23-P 23 Feb 2004 . Technical Description BSS Command Reference inc_prp_cap_ena inc_prp_cap_ena {4441} Description The inc_prp_cap_ena parameter enables or disables Increase Packet Resource Processor (PRP) Capacity. the BSS does not support the Increase PRP Capacity feature. Syntax Change command strings chg_element inc_prp_cap_ena <value> <location> Display command strings disp_element inc_prp_cap_ena <location> 68P02901W23-P 23 Feb 2004 5-377 GMR-01 . When enabled. This parameter is retained for future development. inc_prp_cap_ena is permanently disabled even though the PRP Capacity feature is unrestricted. When disabled. Type A (no operator actions) Supported by OMC-R GUI Yes Cell description required No Dependencies The Increase PRP Capacity feature must be unrestricted. the BSS does not support the Increase PRP Capacity feature. 0 functionality according to requirement 4253–001–6 [6]) 0 5-378 GMR-01 68P02901W23-P 23 Feb 2004 .inc_prp_cap_ena Chapter 5: CM database parameters Values Value type Integer Valid range 0 or 1 Default value 0 Disabled 1 Disabled (BSS supports GSR6. Syntax Add/Change command strings chg_element init_dl_cs <value> <location> <cell_desc> chg_cell_element init_dl_cs <value> <cell_desc> Display command strings disp_cell <cell_number> “full" disp_element init_dl_cs <location> <cell_desc> Values Value type Integer Valid range 0 to 3 0 68P02901W23-P 23 Feb 2004 Downlink TBF starts with CS1. Type A (no operator actions) Supported by OMC-R GUI Yes Cell description required Yes Dependencies EGPRS must be restricted. 5-379 GMR-01 .Technical Description BSS Command Reference init_dl_cs init_dl_cs {4445} 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. To use coding scheme 3 and 4. 32 kbit/s TRAU must be enabled for at least one RTF in a given cell. GPRS must be unrestricted. {23658} This parameter is used for GPRS and can not be used for EGPRS (see egprs_init_dl_cs). 1 5-380 GMR-01 68P02901W23-P 23 Feb 2004 .init_dl_cs Chapter 5: CM database parameters Default value 1 Downlink TBF starts with CS2. 3 Downlink TBF starts with CS4. 2 Downlink TBF starts with CS3. 1 Downlink TBF starts with CS2. The init_ul_cs parameter is configurable on a per cell basis. 32 kbit/s TRAU must be enabled for at least one RTF in a given cell. Type A (no operator actions) Supported by OMC-R GUI Yes Cell description required Yes Dependencies EGPRS must be restricted. To use coding scheme 3 and 4. GPRS must be unrestricted.Technical Description BSS Command Reference init_ul_cs init_ul_cs {4445} Description The init_ul_cs parameter is used to specify the initial uplink Coding Scheme (CS) configuration information for a cell. 5-381 GMR-01 . {23658} This parameter is used for GPRS and can not used for EGPRS (see egprs_init_ul_cs). Syntax Add/Change command strings chg_element init_ul_cs <value> <location> <cell_desc> chg_cell_element init_ul_cs <value> <cell_desc> Display command strings disp_cell <cell_number> “full" disp_element init_ul_cs <location> <cell_desc> Values Valid range 68P02901W23-P 23 Feb 2004 0 to 3 0 Downlink TBF starts with CS1. init_ul_cs Chapter 5: CM database parameters Default value 2 Downlink TBF starts with CS3. 1 5-382 GMR-01 68P02901W23-P 23 Feb 2004 . 3 Downlink TBF starts with CS4. 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. 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).Technical Description BSS Command Reference inner_zone_alg inner_zone_alg Description The inner_zone_alg parameter specifies the use algorithm and the associated parameters for the inner zone of the cell. Operator actions Change the security level to 2 or above before using this parameter. The Coincident Multiband feature and the Dual Band Cells feature must not be set at the same time. so coincident_mb must be 0. Cannot set this parameter to dual band cells for PCS1900 cells. Type B (operator actions required) Supported by OMC-R GUI Yes Cell description required Yes Dependencies The Concentric Cells feature must be unrestricted to use the inner_zone_alg parameter. Syntax Change command string chg_cell_element inner_zone_alg <value> <cell_desc> Display command strings disp_cell <cell_desc> "full" disp_element inner_zone_alg <location> <cell_desc> 68P02901W23-P 23 Feb 2004 5-383 GMR-01 . 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. Valid range: 0 to 30 Default value:0 • rxlev_dl_zone Valid range: 0 to 63 Default value: 63 • rxlev_ul_zone Valid range: 0 to 63 Default value: 63 Interference based use algorithm. 0 Table 5-21 shows the prompted parameters when 3 is entered for inner_zone_alg. 1 Power based use algorithm.inner_zone_alg Chapter 5: CM database parameters Values Value type Integer Valid range 0 to 3 0 Disable inner zone. 5-384 GMR-01 68P02901W23-P 23 Feb 2004 . The system displays prompts for: • ms_txpwr_max_inner Valid range: PGSM and EGSM: 5 to 39 dBm (odd values only. The system prompts for: • 3 Default value neighbor_report_timer Valid range: 0 to 255 SACCH periods Default value: 10 Dual Band Cell use. value must be less than or equal to max_tx_ms) Default value: max_tx ms 2 • zone_ho_hyst. The system displays prompts as shown in Table 5-21. Default: 0. If cell primary frequency is PGSM or EGSM. based on secondary frequency type. 68P02901W23-P 23 Feb 2004 5-385 GMR-01 . 0 to 63 Default: 63. based on secondary frequency type. must be DCS1800. EGSM or Required. Enter inner zone handover hysteresis: zone_ho_hyst Optional. As defined for max_tx_bts . Enter handover power level for the inner zone: ho_pwr_level_inner Optional. As defined for handover_power_level. DCS1800 Inner zone frequency type for dual band cell. can be PGSM or EGSM. Enter downlink receive level threshold for the inner zone: rxlev_dl_zone Optional. Enter uplink receive level threshold for the inner zone: rxlev_ul_zone Optional. -63 to +63 Default: 0. Enter maximum MS transmit power for the inner zone: ms_txpwr_max_inner Required. 0 to 63 Default: 63. Default: 2. If cell primary frequency is DCS1800. -63 to +63 Default: 0. Enter maximum base transmit power for the inner zone: bts_txpwr_max_inner Optional.Technical Description BSS Command Reference Table 5-21 inner_zone_alg Prompted parameters for Dual Band Cell use Prompt Parameter name Notes Range Enter secondary frequency type: secondary_freq_type PGSM. Enter dual band offset: dual_band_offset Optional. As defined for max_tx_ms. The valid range of values for intave is 1 to 31. Type A (no operator actions) Supported by OMC-R GUI Yes Cell description required Yes Dependencies None Syntax Add/Change command strings add_cell <gsm_cell_id> <location> chg_element intave <value> <location> <cell_desc> chg_cell_element intave <value> <cell_desc> Display command strings disp_cell <cell_desc> ["full"] disp_element intave <location> <cell_desc> 5-386 GMR-01 68P02901W23-P 23 Feb 2004 .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. If a value greater then 31 is entered. undetermined results may occur affecting service. ... . .Technical Description BSS Command Reference intave Values Value type Integer (1 step = 2 SACCH multiframes) Valid range 1 to 31 Default value 1 2 SACCH multiframes 2 4 SACCH multiframes .......08 This is a Motorola defined parameter.. 31 62 SACCH multiframes 8 References GSM specification 68P02901W23-P 23 Feb 2004 Used to specify the Intave parameter as described in 5... . . 5-387 GMR-01 .. 1 Outgoing Inter-cell handover is enabled. Type A (no operator actions) Supported by OMC-R GUI Yes Cell description required Yes Dependencies None Syntax Add/Change command strings add_cell <gsm_cell_id> <location> chg_element inter_cell_handover_allowed <value> <location> <cell_desc> chg_cell_element inter_cell_handover_allowed <value> <cell_desc> Display command strings disp_cell <cell_desc> ["full"] 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. External inter-cell handovers are defined as handovers between cells in different BSSs. The Handover Required message is sent to the MSC. 5-388 GMR-01 68P02901W23-P 23 Feb 2004 .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. 5: handover definitions 12. 3 Outgoing Inter-cell and external handovers are disabled and the Handover Required message is not sent to the MSC.20 .8. The Handover Required message is not sent to the MSC.enable Intercell Handover 68P02901W23-P 23 Feb 2004 5-389 GMR-01 . 1 References GSM parameter EN_INTER_HO GSM specification 8.3.5.08 .1.7 8.18 enable BSS Handover Control .2.Technical Description BSS Command Reference Default value inter_cell_handover_allowed 2 Outgoing internal Inter-cell handover is disabled.08 . an attempt to set inter_rat_enabled to 1 . Three modes are available on a per cell basis: • Enabled.Idle will be rejected. • Combined.Enabled. Syntax Add/Change command strings chg_element inter_rat_enabled <value> <location> <cell_desc> chg_cell_element inter_rat_enabled <value> <cell_desc> Display command strings disp_cell <cell_desc> "full" disp_element inter_rat_enabled <location> <cell_desc> Values Value type Integer Valid range 0 to 3 5-390 GMR-01 68P02901W23-P 23 Feb 2004 . {3723} If pccch_enabled is set to 1 . 3 or 4. Type A (no operator actions) Supported by OMC-R GUI Yes Cell description required Yes Dependencies The BSS Inter-RAT feature must be unrestricted. 2.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. • Disabled. and the network_control_order parameter is set to any of the values 1. Technical Description BSS Command Reference Default value 68P02901W23-P 23 Feb 2004 inter_rat_enabled 0 Off 1 2-3G idle 2 3-2G dedicated 3 2-3G idle / 3-2G dedicated 0 5-391 GMR-01 . interband_ho_allowed Chapter 5: CM database parameters interband_ho_allowed Description The interband_ho_allowed parameter specifies the handover frequencies for a cell. Syntax Change command string chg_element interband_ho_allowed <value> <location> <cell_desc> chg_cell_element interband_ho_allowed <value> <cell_desc> Display command strings disp_cell <cell_desc> "full" disp_element interband_ho_allowed <location> <cell_desc> Values Value type Integer Valid range 1 to 11 5-392 GMR-01 68P02901W23-P 23 Feb 2004 . For example. the frequency type for the cell. then the interband_ho_allowed parameter must include pgsm as a possible destination frequency band for handovers. This parameter must include. if the cell has a frequency_type of pgsm. Type A (no operator action required) Supported by OMC-R GUI Yes Cell description required Yes Dependencies This parameter is not available unless the Multiband Inter-cell Handover feature is enabled. at a minimum. and DCS1800 PCS1900 PGSM and PCS1900 EGSM and PCS1900 PGSM.Technical Description BSS Command Reference interband_ho_allowed 1 2 3 4 5 6 7 8 9 10 11 Default value 68P02901W23-P 23 Feb 2004 PGSM EGSM PGSM and EGSM DCS1800 PGSM and DCS1800 EGSM and DCS1800 PGSM. EGSM. and PCS1900 If the Multiband Inter-cell Handover feature is enabled: 3 for PGSM and EGSM cells 4 for DCS1800 cells 8 for PCS1900 cells 5-393 GMR-01 . EGSM. 3 must be less than or equal to interfer_bands. The averaged results are then mapped into five interference categories whose limits are adjusted.<index> <location> <cell_desc> 5-394 GMR-01 68P02901W23-P 23 Feb 2004 . 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.1 interfer_bands.2 interfer_bands.<index> <value> <cell_desc> Display command strings disp_cell <cell_desc> "full" disp_element interfer_bands.1 must be less than or equal to interfer_bands.3 interfer_bands.4 Syntax Change command strings chg_element interfer_bands. Type A (no operator actions) Supported by OMC-R GUI Yes Cell description required Yes Dependencies interfer_bands. Index values 0 to 4 correspond to bands X1 to X5.<index> <value> <location> <cell_desc> chg_cell_element interfer_bands.0 must be less than or equal to interfer_bands. An index number is required.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).2 must be less than or equal to interfer_bands. .thresholds 8.. as shown below: 0 -110 dBm 1 -109 dBm 2 -108 dBm ..20 .0-X5 12.Appendix A 5.08 68P02901W23-P 23 Feb 2004 5-395 GMR-01 . References GSM parameter INT_BOUND_X1.. 63 -47 dBm Default value 63 The system displays a warning message if interfer_bands..08 . INT_BOUND_X2.2.08 .4 is changed to a value less than 63.. INT_BOUND_X4. ...Interference Averaging Process ...8.. . INT_BOUND_X5 GSM specification 5. .10 .Technical Description BSS Command Reference interfer_bands Values Value type Integer Valid range 0 to 63 Represents -110 dBm to -47 dBm.5... INT_BOUND_X3. . 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. it is initiated by sending a Handover Required message. These calls are included as target cells in a Handover Required message to the MSC. 5-396 GMR-01 68P02901W23-P 23 Feb 2004 . BSS support is optional. If the BSS does not support an internal intra-cell handover. Type A (no operator actions) Supported by OMC-R GUI Yes Cell description required Yes Dependencies None Syntax Add/Change command strings add_cell <gsm_cell_id> <location> chg_element intra_cell_handover_allowed <value> <location> <cell_desc> chg_cell_element intra_cell_handover_allowed <value> <cell_desc> Display command strings disp_cell <cell_desc> ["full"] 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. Technical Description BSS Command Reference Default value intra_cell_handover_allowed 1 The BSS performs Intra-cell handovers. 1 References GSM parameter EN_INTRA_HO.5.2.6 8.5: handover definitions 12. 2 Intra-cell handovers are disabled and the Handover Required message is not sent to the MSC. The MSC is notified with a Handover Performed message. EN_INCOM_HO GSM specification 5.08 .Appendix A .8.1 and 4.4.1.3.08 .08 .18 enable BSS Handover Control .20 .enable Intracell Handover 68P02901W23-P 23 Feb 2004 5-397 GMR-01 .2 8. Do not change the values for this parameter unless a KSW is added or removed. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required No Dependencies Changing this parameter is not allowed at M-Cell sites. When there are no more timeslots available. Syntax Change command string chg_ksw_config <location> <ksw_pair> <highway1> <highway2> <highway3> <highway4> Display command string disp_element ksw_config. 5-398 GMR-01 68P02901W23-P 23 Feb 2004 .<index> <location> For more information. Each KSW pair provides 1024 timeslots. 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. refer to the chg_ksw_config descriptions and examples in Chapter 2.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. the system borrows timeslots from neighbouring cages. The range of index values is 0 to 3. Technical Description BSS Command Reference ksw_config Values Value type Integer Valid range 0 to 3 Default value None 68P02901W23-P 23 Feb 2004 5-399 GMR-01 . . This threshold is checked to determine if a handover condition exists. .. ...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... as shown below: 0 -110 dBm and lower 1 -109 dBm 2 -108 dBm .. . Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required Yes Dependencies None Syntax Add/Change command strings add_cell <gsm_cell_id> <location> chg_element l_rxlev_dl_h <value> <location> <cell_desc> chg_cell_element l_rxlev_dl_h <value> <cell_desc> Display command strings disp_cell <cell_desc> ["full"] disp_element l_rxlev_dl_h <location> <cell_desc> Values Value type Integer (1 step = 1 dBm) Valid range 0 to 63 Represents -110 dBm to -47 dBm.. 5-400 GMR-01 68P02901W23-P 23 Feb 2004 . .Technical Description BSS Command Reference Default value l_rxlev_dl_h . ..Table 1 68P02901W23-P 23 Feb 2004 5-401 GMR-01 ..Appendix A . 63 -47 dBm and higher 10 References GSM parameter L_RXLEV_DL_H GSM specification 5..08 . .. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required Yes Dependencies Must be less than u_rxlev_dl_p Syntax Add/Change command strings add_cell <gsm_cell_id> <location> chg_element l_rxlev_dl_p <value> <location> <cell_desc> chg_cell_element l_rxlev_dl_p <value> <cell_desc> Display command strings disp_cell <cell_desc> ["full"] disp_element l_rxlev_dl_p <location> <cell_desc> Values Value type Integer (1 step = 1 dBm) Valid range 0 to 63 Represents -110 dBm to -47 dBm.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. as shown below: 0 -110 dBm and lower 1 -109 dBm 2 -108 dBm ..... . . 5-402 GMR-01 68P02901W23-P 23 Feb 2004 .. .. 63 -47 dBm and higher 30 References GSM parameter L_RXLEV_DL_P GSM specification 5.Technical Description BSS Command Reference Default value l_rxlev_dl_p ...Appendix A .08 .Table 1 68P02901W23-P 23 Feb 2004 5-403 GMR-01 .. .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.. 5-404 GMR-01 68P02901W23-P 23 Feb 2004 . . as shown below: 0 -110 dBm and lower 1 -109 dBm 2 -108 dBm . Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required Yes Dependencies None Syntax Add/Change command strings add_cell <gsm_cell_id> <location> chg_element l_rxlev_ul_h <value> <location> <cell_desc> chg_cell_element l_rxlev_ul_h <value> <cell_desc> Display command strings disp_cell <cell_desc> ["full"] disp_element l_rxlev_ul_h <location> <cell_desc> Values Value type Integer (1 step = 1 dBm) Valid range 0 to 63 Represents -110 dBm to -47 dBm.... . .Technical Description BSS Command Reference Default value l_rxlev_ul_h .08 .. 63 -47 dBm and higher 10 References GSM parameter L_RXLEV_UL_H GSM specification 5.Table 1 68P02901W23-P 23 Feb 2004 5-405 GMR-01 ...Appendix A . . 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. as shown below: 0 -110 dBm and lower 1 -109 dBm 2 -108 dBm 5-406 GMR-01 68P02901W23-P 23 Feb 2004 . Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required Yes Dependencies Must be less than u_rxlev_ul_p Syntax Add/Change command strings add_cell <gsm_cell_id> <location> chg_element l_rxlev_ul_p <value> <location> <cell_desc> chg_cell_element l_rxlev_ul_p <value> <cell_desc> Display command strings disp_cell <cell_desc> ["full"] disp_element l_rxlev_ul_p <location> <cell_desc> Values Value type Integer (1 step = 1 dBm) Valid range 0 to 63 Represents -110 dBm to -47 dBm. .Table 1 68P02901W23-P 23 Feb 2004 5-407 GMR-01 .. 63 -47 dBm and higher 30 References GSM parameter L_RXLEV_UL_P GSM specification 5. .Appendix A . .. ...Technical Description BSS Command Reference Default value l_rxlev_ul_p ..08 . ..... ... This threshold is checked to determine if a handover condition exists. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required Yes Dependencies alt_qual_proc. The type of unit is specified by the alt_qual_proc parameter.See also data_qual_enabled. hop_qual _enabled.01% bit error rate) If alt_qual_proc = 0 0 to 7 QBand units If alt_qual_proc = 1 5-408 GMR-01 68P02901W23-P 23 Feb 2004 .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. Receive quality processing is measured using Bit Error Rate (BER) values or Quality Band (QBand) units. Syntax Add/Change command strings add_cell <gsm_cell_id> <location> chg_element l_rxqual_dl_h <value> <location> <cell_desc> chg_cell_element l_rxqual_dl_h <value> <cell_desc> Display command strings disp_cell <cell_desc> ["full"] disp_element l_rxqual_dl_h <location> <cell_desc> Values Value type Integer Valid range 0 to 1810 BER (1 step = 0. Table 1 68P02901W23-P 23 Feb 2004 5-409 GMR-01 .Appendix A .Technical Description BSS Command Reference Default value l_rxqual_dl_h 453 453 BER if alt_qual_proc = 0 5 5 QBand units if alt_qual_proc = 1 References GSM parameter L_RXQUAL_DL_H GSM specification 5.08 . This parameter is prompted when alt_qual_proc is changed. Syntax Add/Change command strings chg_element l_rxqual_dl_h_amr_fr <value> <location> <cell_desc> chg_cell_element l_rxqual_dl_h_amr_fr <value> <cell_desc> Display command strings disp_cell <cell_desc> ["full"] disp_element l_rxqual_dl_h_amr_fr <location> <cell_desc> Values Value type Integer Valid range 0 to 1810 BER (1 step = 0. This parameter can be changed only at an AMR-capable BTS site. This threshold is checked to determine if a handover condition existis.01% bit error rate) if alt_qual_proc = 0 0 to 7 QBand units if alt_qual_proc = 1 226 226 BER if alt_qual_proc = 0 4 4 QBand units if alt_qual_proc = 1 Default value 5-410 GMR-01 68P02901W23-P 23 Feb 2004 .l_rxqual_dl_h_amr_fr Chapter 5: CM database parameters l_rxqual_dl_h_amr_fr {4322} Description The l_rxqual_dl_h_amr_fr parameter specifies the handover control threshold for the full-rate lower received quality (rxqual) downlink. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required Yes Dependencies The AMR feature must be unrestricted. This threshold is checked to determine if a handover condition existis. Syntax Add/Change command strings chg_element l_rxqual_dl_h_amr_hr <value> <location> <cell_desc> chg_cell_element l_rxqual_dl_h_amr_hr <value> <cell_desc> Display command strings disp_cell <cell_desc> ["full"] disp_element l_rxqual_dl_h_amr_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 113 113 BER if alt_qual_proc = 0 3 3 QBand units if alt_qual_proc = 1 Default value 68P02901W23-P 23 Feb 2004 5-411 GMR-01 . This parameter can be changed only at an AMR-capable BTS site.Technical Description BSS Command Reference l_rxqual_dl_h_amr_hr l_rxqual_dl_h_amr_hr {4322} Description The l_rxqual_dl_h_amr_hr parameter specifies the handover control threshold for the half-rate lower received quality (rxqual) downlink. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required Yes Dependencies The AMR feature must be unrestricted. This parameter is prompted when alt_qual_proc is changed. l_rxqual_dl_h_data Chapter 5: CM database parameters 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). Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required Yes Dependencies alt_qual_proc Syntax Change command strings chg_element l_rxqual_dl_h_data <value> <location> <cell_desc> chg_cell_element l_rxqual_dl_h_data <value> <cell_desc> Display command strings disp_cell <cell_desc> ["full"] disp_element l_rxqual_dl_h_data <location> <cell_desc> Values Value type Integer Valid range 0 to 1810 BER (1 step = 0. The type of unit is specified by the alt_qual_proc parameter. 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. This threshold is checked to determine if a handover condition exists. as set in the add_cell command. Receive quality processing is measured using Bit Error Rate (BER) values or Quality Band (QBand) units. This threshold is enabled and set to be used when data is being transmitted.01% bit error rate) If alt_qual_proc = 0 0 to 7 QBand units If alt_qual_proc = 1 5-412 GMR-01 68P02901W23-P 23 Feb 2004 . Technical Description BSS Command Reference Default value l_rxqual_dl_h_data 0 0 BER if alt_qual_proc = 0 4 4 QBand units if alt_qual_proc = 1 References GSM parameter L_RXQUAL_DL_H GSM specification 5.08 .Table 1 68P02901W23-P 23 Feb 2004 5-413 GMR-01 .Appendix A . This threshold is enabled and set to be used for hopping calls.l_rxqual_dl_h_hopping Chapter 5: CM database parameters 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. as set in the add_cell command. for hopping calls only. Receive quality processing is measured using Bit Error Rate (BER) values or Quality Band (QBand) units.01% bit error rate) If alt_qual_proc = 0 0 to 7 QBand units If alt_qual_proc = 1 5-414 GMR-01 68P02901W23-P 23 Feb 2004 . The type of unit is specified by the alt_qual_proc parameter. In this situation it is used instead of the l_rxqual_dl_h threshold value. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required Yes Dependencies alt_qual_proc Syntax Change command strings chg_element l_rxqual_dl_h_hopping <value> <location> <cell_desc> chg_cell_element l_rxqual_dl_h_hopping <value> <cell_desc> Display command strings disp_cell <cell_desc> ["full"] disp_element l_rxqual_dl_h_hopping <location> <cell_desc> Values Value type Integer Valid range 0 to 1810 BER (1 step = 0. This threshold is checked to determine if a handover condition exists. by use of the hop_qual_enabled parameter in a chg_cell_element command. 08 .Table 1 68P02901W23-P 23 Feb 2004 5-415 GMR-01 .Technical Description BSS Command Reference Default value l_rxqual_dl_h_hopping 0 0 BER if alt_qual_proc = 0 4 4 QBand units if alt_qual_proc = 1 References GSM parameter L_RXQUAL_DL_H GSM specification 5.Appendix A . This parameter is prompted when alt_qual_proc is changed.l_rxqual_dl_h_hopping_amr_fr Chapter 5: CM database parameters l_rxqual_dl_h_hopping_amr_fr {4322} Description The l_rxqual_dl_h_hopping_amr_fr parameter specifies the handover control threshold for the lower Received (Rx) quality downlink. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required Yes Dependencies The AMR feature must be unrestricted. Syntax Add/Change command strings chg_element l_rxqual_dl_h_hopping_amr_fr <value> <location> <cell_desc> chg_cell_element l_rxqual_dl_h_hopping_amr_fr <value> <cell_desc> Display command strings disp_cell <cell_desc> ["full"] disp_element l_rxqual_dl_h_hopping_amr_fr <location> <cell_desc> 5-416 GMR-01 68P02901W23-P 23 Feb 2004 . for hopping calls only. This threshold is enabled and set to be used for hopping calls with the chg_cell_element command and the hop_qual_enabled parameter. This threshold is checked to determine if a handover condition exists. This parameter can be changed only at an AMR-capable BTS site. Technical Description BSS Command Reference l_rxqual_dl_h_hopping_amr_fr 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 0 0 BER if alt_qual_proc = 0 0 0 QBand units if alt_qual_proc = 1 Default value 68P02901W23-P 23 Feb 2004 5-417 GMR-01 . 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 Add/Change command strings chg_element l_rxqual_dl_h_hopping_amr_hr <value> <location> <cell_desc> chg_cell_element l_rxqual_dl_h_hopping_amr_hr <value> <cell_desc> Display command strings disp_cell <cell_desc> ["full"] disp_element l_rxqual_dl_h_hopping_amr_hr <location> <cell_desc> 5-418 GMR-01 68P02901W23-P 23 Feb 2004 . Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required Yes Dependencies The AMR feature must be unrestricted.l_rxqual_dl_h_hopping_amr_hr Chapter 5: CM database parameters l_rxqual_dl_h_hopping_amr_hr {4322} Description The l_rxqual_dl_h_hopping_amr_hr parameter specifies the handover control threshold for the lower Received (Rx) quality downlink. This parameter can be changed only at an AMR-capable BTS site. This parameter is prompted when alt_qual_proc is changed. 01% bit error rate) if alt_qual_proc = 0 0 to 7 QBand units if alt_qual_proc = 1 0 0 BER if alt_qual_proc = 0 0 0 QBand units if alt_qual_proc = 1 Default value 68P02901W23-P 23 Feb 2004 5-419 GMR-01 .Technical Description BSS Command Reference l_rxqual_dl_h_hopping_amr_hr Values Value type Integer Valid range 0 to 1810 BER (1 step = 0. Receive quality processing is measured using Bit Error Rate (BER) values or Quality Band (QBand) units. This threshold is checked to determine if BTS power should be increased.01% bit error rate) If alt_qual_proc = 0 0 to 7 QBand units If alt_qual_proc = 1 5-420 GMR-01 68P02901W23-P 23 Feb 2004 . Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required Yes Dependencies alt_qual_procMust be greater than u_rxqual_dl_pSee also data_qual_enabled. hop_qual_enabled Syntax Add/Change command strings add_cell <gsm_cell_id> <location> chg_element l_rxqual_dl_p <value> <location> <cell_desc> chg_cell_element l_rxqual_dl_p <value> <cell_desc> Display command strings disp_cell <cell_desc> ["full"] disp_element l_rxqual_dl_p <location> <cell_desc> Values Value type Integer Valid range 0 to 1810 BER (1 step = 0. The type of unit is specified by the alt_qual_proc parameter.l_rxqual_dl_p Chapter 5: CM database parameters l_rxqual_dl_p Description The l_rxqual_dl_p parameter specifies the lower downlink limit for the signal quality of the serving cell. 08 .Technical Description BSS Command Reference Default value l_rxqual_dl_p 256 256 BER if alt_qual_proc = 0 4 4 QBand units if alt_qual_proc = 1 References GSM parameter L_RXQUAL_DL_P GSM specification 5.Table 1 68P02901W23-P 23 Feb 2004 5-421 GMR-01 .Appendix A . l_rxqual_dl_p_amr_fr Chapter 5: CM database parameters l_rxqual_dl_p_amr_fr {4322} Description The l_rxqual_dl_p_amr_fr parameter specifies the lower downlink limit for the signal quality of the serving cell. This threshold is checked to determine if the BTS power should be increased. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required Yes Dependencies The AMR feature must be unrestricted.01% bit error rate) if alt_qual_proc = 0 0 to 7 QBand units if alt_qual_proc = 1 113 113 BER if alt_qual_proc = 0 3 3 QBand units if alt_qual_proc = 1 Default value 5-422 GMR-01 68P02901W23-P 23 Feb 2004 . This parameter is prompted when alt_qual_proc is changed. This parameter must be greater than u_rxqual_dl_p. This parameter can be changed only at an AMR-capable BTS site. Syntax Add/Change command strings chg_element l_rxqual_dl_p_amr_fr <value> <location> <cell_desc> chg_cell_element l_rxqual_dl_p_amr_fr <value> <cell_desc> Display command strings disp_cell <cell_desc> ["full"] disp_element l_rxqual_dl_p_amr_fr <location> <cell_desc> Values Value type Integer Valid range 0 to 1810 BER (1 step = 0. This parameter can be changed only at an AMR-capable BTS site. This parameter is prompted when alt_qual_proc is changed.Technical Description BSS Command Reference l_rxqual_dl_p_amr_hr l_rxqual_dl_p_amr_hr {4322} Description The l_rxqual_dl_p_amr_hr parameter specifies the lower downlink limit for the signal quality of the serving cell. This threshold is checked to determine if the BTS power should be increased. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required Yes Dependencies The AMR feature must be unrestricted. This parameter must be greater than u_rxqual_dl_p_amr_hr. Syntax Add/Change command strings chg_element l_rxqual_dl_p_amr_hr <value> <location> <cell_desc> chg_cell_element l_rxqual_dl_p_amr_hr <value> <cell_desc> Display command strings disp_cell <cell_desc> ["full"] disp_element l_rxqual_dl_p_amr_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 57 57 BER if alt_qual_proc = 0 2 2 QBand units if alt_qual_proc = 1 Default value 68P02901W23-P 23 Feb 2004 5-423 GMR-01 . Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required Yes Dependencies alt_qual_proc Syntax Change command strings chg_element l_rxqual_dl_p_data <value> <location> <cell_desc> chg_cell_element l_rxqual_dl_p_data <value> <cell_desc> Display command strings disp_cell <cell_desc> ["full"] disp_element l_rxqual_dl_p_data <location> <cell_desc> Values Value type Integer Valid range 0 to 1810 BER (1 step = 0. as set in the add_cell command. This threshold is checked to determine if BTS power should be increased. In this situation it is used instead of the l_rxqual_dl_p threshold value.01% bit error rate) If alt_qual_proc = 0 0 to 7 QBand units If alt_qual_proc = 1 5-424 GMR-01 68P02901W23-P 23 Feb 2004 . for data transmissions only (for example modem-to-modem calls). The type of unit is specified by the alt_qual_proc parameter. This threshold is enabled and set to be used when data is being transmitted. Receive quality processing is measured using Bit Error Rate (BER) values or Quality Band (QBand) units.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. by use of the data_qual_enabled parameter in a chg_cell_element command. Table 1 68P02901W23-P 23 Feb 2004 5-425 GMR-01 .Technical Description BSS Command Reference Default value l_rxqual_dl_p_data 0 0 BER if alt_qual_proc = 0 4 4 QBand units if alt_qual_proc = 1 References GSM parameter L_RXQUAL_DL_P GSM specification 5.08 .Appendix A . as set in the add_cell command.01% bit error rate) If alt_qual_proc = 0 0 to 7 QBand units If alt_qual_proc = 1 5-426 GMR-01 68P02901W23-P 23 Feb 2004 . Receive quality processing is measured using Bit Error Rate (BER) values or Quality Band (QBand) units. This threshold is checked to determine if BTS power should be increased. The type of unit is specified by the alt_qual_proc parameter. In this situation it is used instead of the l_rxqual_dl_p threshold value. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required Yes Dependencies alt_qual_proc Syntax Change command strings chg_element l_rxqual_dl_p_hopping <value> <location> <cell_desc> chg_cell_element l_rxqual_dl_p_hopping <value> <cell_desc> Display command strings disp_cell <cell_desc> ["full"] disp_element l_rxqual_dl_p_hopping <location> <cell_desc> Values Value type Integer Valid range 0 to 1810 BER (1 step = 0.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. by use of the hop_qual_enabled parameter in a chg_cell_element command. for hopping calls only. This threshold is enabled and set to be used for hopping calls. Appendix A .Table 1 68P02901W23-P 23 Feb 2004 5-427 GMR-01 .Technical Description BSS Command Reference Default value l_rxqual_dl_p_hopping 0 0 BER if alt_qual_proc = 0 4 4 QBand units if alt_qual_proc = 1 References GSM parameter L_RXQUAL_DL_P GSM specification 5.08 . l_rxqual_dl_p_hopping_amr_fr Chapter 5: CM database parameters l_rxqual_dl_p_hopping_amr_fr {4322} Description The l_rxqual_dl_p_hopping_amr_fr parameter specifies the lower downlink limit for the signal quality of the serving cell. This parameter can be changed only at an AMR-capable BTS site. for hopping cells only. Syntax Add/Change command strings chg_element l_rxqual_dl_p_hopping_amr_fr <value> <location> <cell_desc> chg_cell_element l_rxqual_dl_p_hopping_amr_fr <value> <cell_desc> Display command strings disp_cell <cell_desc> ["full"] disp_element l_rxqual_dl_p_hopping_amr_fr <location> <cell_desc> 5-428 GMR-01 68P02901W23-P 23 Feb 2004 . This threshold is checked to determine if BTS power should be increased. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required Yes Dependencies The AMR feature must be unrestricted. This threshold is enabled and set to be used for hopping calls with the chg_cell_element command and the hop_qual_enabled parameter. This parameter is prompted when alt_qual_proc is changed. 01% bit error rate) if alt_qual_proc = 0 0 to 7 QBand units if alt_qual_proc = 1 0 0 BER if alt_qual_proc = 0 0 0 QBand units if alt_qual_proc = 1 Default value 68P02901W23-P 23 Feb 2004 5-429 GMR-01 .Technical Description BSS Command Reference l_rxqual_dl_p_hopping_amr_fr Values Value type Integer Valid range 0 to 1810 BER (1 step = 0. This threshold is checked to determine if BTS power should be increased. Syntax Add/Change command strings chg_element l_rxqual_dl_p_hopping_amr_hr <value> <location> <cell_desc> chg_cell_element l_rxqual_dl_p_hopping_amr_hr <value> <cell_desc> Display command strings disp_cell <cell_desc> ["full"] disp_element l_rxqual_dl_p_hopping_amr_hr <location> <cell_desc> 5-430 GMR-01 68P02901W23-P 23 Feb 2004 . This threshold is enabled and set to be used for hopping calls with the chg_cell_element command and the hop_qual_enabled parameter. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required Yes Dependencies The AMR feature must be unrestricted. for hopping cells only. This parameter can be changed only at an AMR-capable BTS site. This parameter is prompted when alt_qual_proc is changed.l_rxqual_dl_p_hopping_amr_hr Chapter 5: CM database parameters l_rxqual_dl_p_hopping_amr_hr {4322} Description The l_rxqual_dl_p_hopping_amr_hr parameter specifies the lower downlink limit for the signal quality of the serving cell. 01% bit error rate) if alt_qual_proc = 0 0 to 7 QBand units if alt_qual_proc = 1 0 0 BER if alt_qual_proc = 0 0 0 QBand units if alt_qual_proc = 1 Default value 68P02901W23-P 23 Feb 2004 5-431 GMR-01 .Technical Description BSS Command Reference l_rxqual_dl_p_hopping_amr_hr Values Value type Integer Valid range 0 to 1810 BER (1 step = 0. 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.01% bit error rate) If alt_qual_proc = 0 0 to 7 QBand units If alt_qual_proc = 1 5-432 GMR-01 68P02901W23-P 23 Feb 2004 . hop_qual_enabled Syntax Add/Change command strings add_cell <gsm_cell_id> <location> chg_element l_rxqual_ul_h <value> <location> <cell_desc> chg_cell_element l_rxqual_ul_h <value> <cell_desc> Display command strings disp_cell <cell_desc> ["full"] disp_element l_rxqual_ul_h <location> <cell_desc> Values Value type Integer Valid range 0 to 1810 BER (1 step = 0. 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. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required Yes Dependencies alt_qual_proc See also: data_qual_enabled. The type of unit is specified by the alt_qual_proc parameter. Appendix A .08 .Technical Description BSS Command Reference Default value l_rxqual_ul_h 453 453 BER if alt_qual_proc = 0 5 5 QBand units if alt_qual_proc = 1 References GSM parameter L_RXQUAL_UL_H GSM specification 5.Table 1 68P02901W23-P 23 Feb 2004 5-433 GMR-01 . This parameter is prompted when alt_qual_proc is changed. This parameter can be changed only at an AMR-capable BTS site. Syntax Add/Change command strings chg_element l_rxqual_ul_h_amr_fr <value> <location> <cell_desc> chg_cell_element l_rxqual_ul_h_amr_fr <value> <cell_desc> Display command strings disp_cell <cell_desc> ["full"] disp_element l_rxqual_ul_h_amr_fr <location> <cell_desc> Values Value type Integer Valid range 0 to 1810 BER (1 step = 0. This threshold is checked to determine if a handover condition exists.l_rxqual_ul_h_amr_fr Chapter 5: CM database parameters l_rxqual_ul_h_amr_fr {4322} Description The l_rxqual_ul_h_amr_fr parameter specifies the handover control threshold for the receive quality (rxqual) uplink.01% bit error rate) if alt_qual_proc = 0 0 to 7 QBand units if alt_qual_proc = 1 453 453 BER if alt_qual_proc = 0 5 5 QBand units if alt_qual_proc = 1 Default value 5-434 GMR-01 68P02901W23-P 23 Feb 2004 . Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required Yes Dependencies The AMR feature must be unrestricted. 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 Add/Change command strings chg_element l_rxqual_ul_h_amr_hr <value> <location> <cell_desc> chg_cell_element l_rxqual_ul_h_amr_hr <value> <cell_desc> Display command strings disp_cell <cell_desc> ["full"] disp_element l_rxqual_ul_h_amr_hr <location> <cell_desc> Values Value type Integer Valid range 0 to 1810 BER (1 step = 0.Technical Description BSS Command Reference l_rxqual_ul_h_amr_hr l_rxqual_ul_h_amr_hr {4322} Description The l_rxqual_ul_h_amr_hr parameter specifies the handover control threshold for the lower Received (Rx) quality downlink. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required Yes Dependencies The AMR feature must be unrestricted.01% bit error rate) if alt_qual_proc = 0 0 to 7 QBand units if alt_qual_proc = 1 113 113 BER if alt_qual_proc = 0 3 3 QBand units if alt_qual_proc = 1 Default value 68P02901W23-P 23 Feb 2004 5-435 GMR-01 . 01% bit error rate) If alt_qual_proc = 0 0 to 7 QBand units If alt_qual_proc = 1 5-436 GMR-01 68P02901W23-P 23 Feb 2004 .l_rxqual_ul_h_data Chapter 5: CM database parameters 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). as set in the add_cell command. This threshold is enabled and set to be used when data is being transmitted. The type of unit is specified by the alt_qual_proc parameter. Receive quality processing is measured using Bit Error Rate (BER) values or Quality Band (QBand) units. This threshold is checked to determine if a handover condition exists. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required Yes Dependencies alt_qual_proc Syntax Change command strings chg_element l_rxqual_ul_h_data <value> <location> <cell_desc> chg_cell_element l_rxqual_ul_h_data <value> <cell_desc> Display command strings disp_cell <cell_desc> ["full"] disp_element l_rxqual_ul_h_data <location> <cell_desc> Values Value type Integer Valid range 0 to 1810 BER (1 step = 0. In this situation it is used instead of the l_rxqual_ul_h threshold value. by use of the data_qual_enabled parameter in a chg_cell_element command. Table 1 68P02901W23-P 23 Feb 2004 5-437 GMR-01 .Appendix A .08 .Technical Description BSS Command Reference Default value l_rxqual_ul_h_data 0 0 BER if alt_qual_proc = 0 5 5 QBand units if alt_qual_proc = 1 References GSM parameter L_RXQUAL_UL_H GSM specification 5. The type of unit is specified by the alt_qual_proc parameter. Receive quality processing is measured using Bit Error Rate (BER) values or Quality Band (QBand) units. for hopping calls only. as set in the add_cell command. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required Yes Dependencies alt_qual_proc Syntax Change command string chg_element l_rxqual_ul_h_hopping <value> <location> <cell_desc> chg_cell_element l_rxqual_ul_h_hopping <value> <cell_desc> Display command strings disp_cell <cell_desc> ["full"] disp_element l_rxqual_ul_h_hopping <location> <cell_desc> Values Value type Integer Valid range 0 to 1810 BER (1 step = 0.l_rxqual_ul_h_hopping Chapter 5: CM database parameters 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. This threshold is enabled and set to be used for hopping calls.01% bit error rate) if alt_qual_proc = 0 0 to 7 QBand units if alt_qual_proc = 1 5-438 GMR-01 68P02901W23-P 23 Feb 2004 . This threshold is checked to determine if a handover condition exists. In this situation it is used instead of the l_rxqual_ul_h threshold value. by use of the hop_qual_enabled parameter in a chg_cell_element command. Appendix A .Technical Description BSS Command Reference Default value l_rxqual_ul_h_hopping 0 0 BER if alt_qual_proc = 0 5 5 QBand units if alt_qual_proc = 1 References GSM parameter L_RXQUAL_UL_H GSM specification 5.08 .Table 1 68P02901W23-P 23 Feb 2004 5-439 GMR-01 . Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required Yes Dependencies The AMR feature must be unrestricted. This threshold is enabled and set to be used for hopping calls with the chg_cell_element command and the hop_qual_enabled parameter. for hopping calls only. This parameter is prompted when alt_qual_proc is changed.l_rxqual_ul_h_hopping_amr_fr Chapter 5: CM database parameters l_rxqual_ul_h_hopping_amr_fr {4322} Description The l_rxqual_ul_h_hopping_amr_fr parameter specifies the handover control threshold for the lower received quality (rxqual) downlink. This threshold is checked to determine if a handover condition exists. Syntax Add/Change command strings chg_element l_rxqual_ul_h_hopping_amr_fr <value> <location> <cell_desc> chg_cell_element l_rxqual_ul_h_hopping_amr_fr <value> <cell_desc> Display command strings disp_cell <cell_desc> ["full"] disp_element l_rxqual_ul_h_hopping_amr_fr <location> <cell_desc> 5-440 GMR-01 68P02901W23-P 23 Feb 2004 . This parameter can be changed only at an AMR-capable BTS site. 01% bit error rate) if alt_qual_proc = 0 0 to 7 QBand units if alt_qual_proc = 1 0 0 BER if alt_qual_proc = 0 0 0 QBand units if alt_qual_proc = 1 Default value 68P02901W23-P 23 Feb 2004 5-441 GMR-01 .Technical Description BSS Command Reference l_rxqual_ul_h_hopping_amr_fr Values Value type Integer Valid range 0 to 1810 BER (1 step = 0. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required Yes Dependencies The AMR feature must be unrestricted. 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. This parameter is prompted when alt_qual_proc is changed. for hopping calls only. This parameter can be changed only at an AMR-capable BTS site. Syntax Add/Change command strings chg_element l_rxqual_ul_h_hopping_amr_hr <value> <location> <cell_desc> chg_cell_element l_rxqual_ul_h_hopping_amr_hr <value> <cell_desc> Display command strings disp_cell <cell_desc> ["full"] disp_element l_rxqual_ul_h_hopping_amr_hr <location> <cell_desc> 5-442 GMR-01 68P02901W23-P 23 Feb 2004 .l_rxqual_ul_h_hopping_amr_hr Chapter 5: CM database parameters l_rxqual_ul_h_hopping_amr_hr {4322} Description The l_rxqual_ul_h_hopping_amr_hr parameter specifies the handover control threshold for the lower received quality (rxqual) downlink. Technical Description BSS Command Reference l_rxqual_ul_h_hopping_amr_hr 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 0 0 BER if alt_qual_proc = 0 0 0 QBand units if alt_qual_proc = 1 Default value 68P02901W23-P 23 Feb 2004 5-443 GMR-01 . Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required Yes Dependencies alt_qual_procMust be greater than u_rxqual_ul_pSee also data_qual_enabled. Receive quality processing is measured using Bit Error Rate (BER) values or Quality Band (QBand) units. This threshold is checked to determine if MS power should be increased.01% bit error rate) if alt_qual_proc = 0 0 to 7 QBand units if alt_qual_proc = 1 5-444 GMR-01 68P02901W23-P 23 Feb 2004 . The type of unit is specified by the alt_qual_proc parameter.l_rxqual_ul_p Chapter 5: CM database parameters l_rxqual_ul_p Description The l_rxqual_ul_p parameter specifies the lower uplink limit of the signal quality of the MS. hop_qual_enabled Syntax Add/Change command strings add_cell <gsm_cell_id> <location> chg_element l_rxqual_ul_p <value> <location> <cell_desc> chg_cell_element l_rxqual_ul_p <value> <cell_desc> Display command strings disp_cell <cell_desc> ["full"] disp_element l_rxqual_ul_p <location> <cell_desc> Values Value type Integer Valid range 0 to 1810 BER (1 step = 0. Table 1 68P02901W23-P 23 Feb 2004 5-445 GMR-01 .08 .Technical Description BSS Command Reference Default value l_rxqual_ul_p 226 226 BER if alt_qual_proc = 0 4 4 QBand units if alt_qual_proc = 1 References GSM parameter L_RXQUAL_UL_P GSM specification 5.Appendix A . Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required Yes Dependencies The AMR feature must be unrestricted. Syntax Add/Change command strings chg_element l_rxqual_ul_p_amr_fr <value> <location> <cell_desc> chg_cell_element l_rxqual_ul_p_amr_fr <value> <cell_desc> Display command strings disp_cell <cell_desc> ["full"] disp_element l_rxqual_ul_p_amr_fr <location> <cell_desc> Values Value type Integer Valid range 0 to 1810 BER (1 step = 0.01% bit error rate) if alt_qual_proc = 0 0 to 7 QBand units if alt_qual_proc = 1 226 226 BER if alt_qual_proc = 0 4 4 QBand units if alt_qual_proc = 1 Default value 5-446 GMR-01 68P02901W23-P 23 Feb 2004 .l_rxqual_ul_p_amr_fr Chapter 5: CM database parameters l_rxqual_ul_p_amr_fr {4322} Description The l_rxqual_ul_p_amr_fr parameter specifies the lower uplink limit of the signal quality of the MS. This parameter can be changed only at an AMR-capable BTS site. This threshold is checked to determine if MS power should be increased. This parameter must be greater than u_rxqual_ul_p. This parameter is prompted when alt_qual_proc is changed. 01% bit error rate) if alt_qual_proc = 0 0 to 7 QBand units if alt_qual_proc = 1 57 57 BER if alt_qual_proc = 0 2 2 QBand units if alt_qual_proc = 1 Default value 68P02901W23-P 23 Feb 2004 5-447 GMR-01 . This parameter can be changed only at an AMR-capable BTS site. Syntax Add/Change command strings chg_element l_rxqual_ul_p_amr_hr <value> <location> <cell_desc> chg_cell_element l_rxqual_ul_p_amr_hr <value> <cell_desc> Display command strings disp_cell <cell_desc> ["full"] disp_element l_rxqual_ul_p_amr_hr <location> <cell_desc> Values Value type Integer Valid range 0 to 1810 BER (1 step = 0.Technical Description BSS Command Reference l_rxqual_ul_p_amr_hr l_rxqual_ul_p_amr_hr {4322} Description The l_rxqual_ul_p_amr_hr parameter specifies the lower uplink limit of the signal quality of the MS. This parameter is prompted when alt_qual_proc is changed. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required Yes Dependencies The AMR feature must be unrestricted. This threshold is checked to determine if MS power should be increased. This parameter must be greater than u_rxqual_ul_p_amr_hr. by use of the data_qual_enabled parameter in a chg_cell_element command. This threshold is checked to determine if MS power should be increased. In this situation it is used instead of the l_rxqual_ul_p threshold value.01% bit error rate) if alt_qual_proc = 0 0 to 7 QBand units if alt_qual_proc = 1 5-448 GMR-01 68P02901W23-P 23 Feb 2004 . for data transmissions only (for example modem-to-modem calls). The type of unit is specified by the alt_qual_proc parameter. This threshold is enabled and set to be used when data is being transmitted.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. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required Yes Dependencies alt_qual_proc Syntax Change command strings chg_element l_rxqual_ul_p_data <value> <location> <cell_desc> chg_cell_element l_rxqual_ul_p_data <value> <cell_desc> Display command strings disp_cell <cell_desc> ["full"] disp_element l_rxqual_ul_p_data <location> <cell_desc> Values Value type Integer Valid range 0 to 1810 BER (1 step = 0. Receive quality processing is measured using Bit Error Rate (BER) values or Quality Band (QBand) units. as set in the add_cell command. 08 .Table 1 68P02901W23-P 23 Feb 2004 5-449 GMR-01 .Technical Description BSS Command Reference Default value l_rxqual_ul_p_data 0 0 BER if alt_qual_proc = 0 5 5 QBand units if alt_qual_proc = 1 References GSM parameter L_RXQUAL_UL_P GSM specification 5.Appendix A . 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. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required Yes Dependencies alt_qual_proc Syntax Change command strings chg_element l_rxqual_ul_p_hopping <value> <location> <cell_desc> chg_cell_element l_rxqual_ul_p_hopping <value> <cell_desc> Display command strings disp_cell <cell_desc> ["full"] disp_element l_rxqual_ul_p_hopping <location> <cell_desc> Values Value type Integer Valid range 0 to 1810 BER (1 step = 0. This threshold is enabled and set to be used for hopping calls. This threshold is checked to determine if MS power should be increased. as set in the add_cell command. by use of the hop_qual_enabled parameter in a chg_cell_element command. for hopping calls only.01% bit error rate) if alt_qual_proc = 0 0 to 7 QBand units if alt_qual_proc = 1 5-450 GMR-01 68P02901W23-P 23 Feb 2004 . The type of unit is specified by the alt_qual_proc parameter. Receive quality processing is measured using Bit Error Rate (BER) values or Quality Band (QBand) units. In this situation it is used instead of the l_rxqual_dl_p threshold value. Appendix A .Technical Description BSS Command Reference Default value l_rxqual_ul_p_hopping 0 0 BER if alt_qual_proc = 0 5 5 QBand units if alt_qual_proc = 1 References GSM parameter L_RXQUAL_UL_P GSM specification 5.08 .Table 1 68P02901W23-P 23 Feb 2004 5-451 GMR-01 . This threshold is checked to determine if BTS power should be increased. This parameter is prompted when alt_qual_proc is changed. This parameter can be changed only at an AMR-capable BTS site. Syntax Add/Change command strings chg_element l_rxqual_ul_p_hopping_amr_fr <value> <location> <cell_desc> chg_cell_element l_rxqual_ul_p_hopping_amr_fr <value> <cell_desc> Display command strings disp_cell <cell_desc> ["full"] disp_element l_rxqual_ul_p_hopping_amr_fr <location> <cell_desc> 5-452 GMR-01 68P02901W23-P 23 Feb 2004 . Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required Yes Dependencies The AMR feature must be unrestricted.l_rxqual_ul_p_hopping_amr_fr Chapter 5: CM database parameters l_rxqual_ul_p_hopping_amr_fr {4322} Description The l_rxqual_ul_p_hopping_amr_fr parameter specifies the lower uplink limit for the signal quality of the serving cell. This threshold is enabled and set to be used for hopping calls with the chg_cell_element command and the hop_qual_enabled parameter. for hopping calls only. 01% bit error rate) if alt_qual_proc = 0 0 to 7 QBand units if alt_qual_proc = 1 0 0 BER if alt_qual_proc = 0 0 0 QBand units if alt_qual_proc = 1 Default value 68P02901W23-P 23 Feb 2004 5-453 GMR-01 .Technical Description BSS Command Reference l_rxqual_ul_p_hopping_amr_fr Values Value type Integer Valid range 0 to 1810 BER (1 step = 0. l_rxqual_ul_p_hopping_amr_hr Chapter 5: CM database parameters l_rxqual_ul_p_hopping_amr_hr {4322} Description The l_rxqual_ul_p_hopping_amr_hr parameter specifies the lower uplink limit for the signal quality of the serving cell. This parameter is prompted when alt_qual_proc is changed. This threshold is checked to determine if BTS power should be increased. This parameter can be changed only at an AMR-capable BTS site. This threshold is enabled and set to be used for hopping calls with the chg_cell_element command and the hop_qual_enabled parameter. for hopping calls only. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required Yes Dependencies The AMR feature must be unrestricted. Syntax Add/Change command strings chg_element l_rxqual_ul_p_hopping_amr_hr <value> <location> <cell_desc> chg_cell_element l_rxqual_ul_p_hopping_amr_hr <value> <cell_desc> Display command strings disp_cell <cell_desc> ["full"] disp_element l_rxqual_ul_p_hopping_amr_hr <location> <cell_desc> 5-454 GMR-01 68P02901W23-P 23 Feb 2004 . 01% bit error rate) if alt_qual_proc = 0 0 to 7 QBand units if alt_qual_proc = 1 0 0 BER if alt_qual_proc = 0 0 0 QBand units if alt_qual_proc = 1 Default value 68P02901W23-P 23 Feb 2004 5-455 GMR-01 .Technical Description BSS Command Reference l_rxqual_ul_p_hopping_amr_hr Values Value type Integer Valid range 0 to 1810 BER (1 step = 0. Type B (operator actions required) Supported by OMC-R GUI Yes Cell numbers required No Dependencies The value of this parameter may be specified for the BSC (site 0) only while in the initial SYSGEN mode. All BTS site values are set to the BSC value. Only the 2. Syntax Change command string chg_element land_layer1_mode <value> <location> Display command string disp_element land_layer1_mode <location> Values Value type Boolean Valid range 0 or 1 0 2. 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. All BTS site values are set to BSC (site 0) value when the database is loaded initially.CEPT format (E1) 5-456 GMR-01 68P02901W23-P 23 Feb 2004 .048 Mbit/s . this parameter must be set to 0 (E1).land_layer1_mode cannot be changed to 1 (T1) unless mms_config_type = 0.048 Mbit/s . The value of this parameter may not be changed if any MSIs or BTS sites are equipped. If the GPRS feature is unrestricted and a PCU is equipped.CEPT format is currently supported. This parameter may be set only while in the initial SYSGEN mode.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. Technical Description BSS Command Reference 1 Default value 68P02901W23-P 23 Feb 2004 land_layer1_mode 1.T1 link 0 5-457 GMR-01 .544 Mbit/s . or picocell. When an RXQUAL handover condition exists. This parameter specifies the layer for a cell. Syntax Change command strings chg_element layer_number <value> <location> <cell_desc> chg_cell_element layer_number <value> <cell_desc> Display command string disp_element layer_number <location> <cell_desc> Values Value type Integer Valid range 0 to 2 Default value 0 Macrocell 1 Microcell 2 Picocell 0 5-458 GMR-01 68P02901W23-P 23 Feb 2004 . microcell. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required Yes Dependencies This parameter is unavailable if the Microcellular option has not been purchased.layer_number Chapter 5: CM database parameters layer_number Description The layer_number parameter specifies the serving cell as being a macrocell. the system attempts to handover a call in the microcell layer to another cell in the microcell layer. 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. Syntax Change command string chg_element lb_int_called_pci <value> <location> Display command string disp_element lb_int_called_pci <location> Values Value type Integer Valid range 0 or 1 0 1 Default value 68P02901W23-P 23 Feb 2004 DCP not included. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required No Dependencies The Location Services feature must be unrestricted. DCP included None 5-459 GMR-01 . None 5-460 GMR-01 68P02901W23-P 23 Feb 2004 . Point code included. Syntax Change command string chg_element lb_int_calling_pci <value> <location> Display command string disp_element lb_int_calling_pci <location> Values Value type Integer Valid range 0 or 1 0 1 Default value Point code not included.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. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required No Dependencies The Location Services feature must be unrestricted. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required No Dependencies The Location Services feature must be unrestricted.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. 0 5-461 GMR-01 . Syntax Change command string chg_element lb_int_cr_calling <value> <location> Display command string disp_element lb_int_cr_calling <location> Values Value type Integer (milliseconds) Valid range 0 or 1 0 1 Default value 68P02901W23-P 23 Feb 2004 Not included. Included. Syntax Change command string chg_element lb_int_dpc <value> <location> Display command string disp_element lb_int_dpc <location> Values Value type Integer Valid range ss7_mode = 0: 0 to 16383ss7_mode = 1: 0 to 16777215 Default value None 5-462 GMR-01 68P02901W23-P 23 Feb 2004 . For the ss7_mode element to be modified from ANSI to CCITT. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required No Dependencies The Location Services feature must be unrestricted. the lb_int_dpc parameter must be within range for the CCITT ss7_mode setting.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. The valid values for this element are dependent upon the value of the ss7_mode element. For a live system. the lb_int_dpc must not be the same value as the opc. Syntax Change command string chg_element lb_int_global_reset_repetitions <value> <location> Display command string disp_element lb_int_global_reset_repetitions <location> Values Value type Integer Valid range 0 to 255 Default value 0 References GSM specification 68P02901W23-P 23 Feb 2004 TS GSM 8. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required No Dependencies The Location Services feature must be unrestricted.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.08 5-463 GMR-01 . Dependencies checked during database verification 1. and the following error message is displayed: ERROR: LCS requires phase2_classmark_allowed to be configured to support multiband. the database is not created. 2. Errors were found in the database. Errors were found in the database. Errors were found in the database. and the following error message is displayed: ERROR: For setups with no BSS-based SMLC support. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required No Dependencies See Dependencies checked during database verification list and Dependencies checked during lcs_mode modification list for the dependencies of this parameter. 5-464 GMR-01 68P02901W23-P 23 Feb 2004 . 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. the database is not created. LMTLs cannot exist and LCFs cannot manage LMTLs. If database verification determines that the BSS is not configured to support a BSS-based SMLC and one or more LMTL devices are equipped. If database verification determines that the location services feature is enabled and phase2_classmark_allowed is not configured to support multiband. REJECTING SYSGEN_OFF REQUEST. 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. REJECTING SYSGEN_OFF REQUEST. This parameter can be modified only when the system is in the SYSGEN ON mode. REJECTING SYSGEN_OFF REQUEST. 3.lcs_mode Chapter 5: CM database parameters lcs_mode Description The lcs_mode parameter specifies the Location Services mode of the BSS. 1 or 2. and the following error message is displayed: ERROR: For setups with no BSS-based SMLC support.Technical Description BSS Command Reference 4. Errors were found in the database. and one or more LMTLs are equipped. the database is not created. LMTLs cannot exist and LCFs cannot manage LMTLs. 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 the location services feature is restricted. 5. LMTLs cannot exist and LCFs cannot manage LMTLs. and one or more LCFs are configured to manage LMTLs. and the following error message is displayed: ERROR: When LCS is restricted lcs_mode must be 0. REJECTING SYSGEN_OFF REQUEST. the command is rejected. and the following error message is displayed: ERROR: For setups with no BSS-based SMLC support. and the following message is displayed: ERROR: When LCS is restricted lcs_mode must be 0. the database is not created. lcs_mode 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. REJECTING SYSGEN_OFF REQUEST. 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. COMMAND REJECTED Syntax Change command string chg_element lcs_mode <value> <location> Display command string disp_element lcs_mode <location> 68P02901W23-P 23 Feb 2004 5-465 GMR-01 . and the following error message is displayed: ERROR: For setups with no BSS based SMLC support. Errors were found in the database. 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 command is rejected. If an operator attempts to change the LCS mode element to an LCS enabled setting. the command is rejected. COMMAND REJECTED 2. Dependencies checked during lcs_mode modification 1. LMTLs cannot exist and LCFs cannot manage LMTLs. COMMAND REJECTED 3. BSC supports an NSS-based SMLC 2 Location services enabled. SMLC not supported 1 Location services enabled. BSC supports an BSS-based SMLC Default value 0 5-466 GMR-01 68P02901W23-P 23 Feb 2004 .lcs_mode Chapter 5: CM database parameters Values Value type Integer Valid range 0 Location services disabled. Full power is specified by the max_tx_bts parameter for the downlink 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. the BSS and MS are increased to full power when 20 undecoded SACCH frames are received. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required Yes Dependencies link_about_to_fail must be less than link_fail Syntax Change command strings chg_element link_about_to_fail <value> <location> <cell_desc> chg_cell_element link_about_to_fail <value> <cell_desc> Display command strings disp_cell <cell_desc> ["full"] disp_element link_about_to_fail <location> <cell_desc> 68P02901W23-P 23 Feb 2004 5-467 GMR-01 . and max_tx_ms or max power capability of the MS for uplink 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. if link_fail is set to 5 (24 SACCH frames) and link_about_to_fail is set to 1 (4 SACCH frames).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. For example. ... 15 60 SACCH frames Default value 2 References Internal name THRES_PC_RLF This is a Motorola defined parameter.... . . .. .....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 .. 5-468 GMR-01 68P02901W23-P 23 Feb 2004 .. If the BSS is unable to decode a SACCH message. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required Yes Dependencies link_fail must be greater than or equal to link_about_to_fail Syntax Change command strings chg_element link_fail <value> <location> <cell_desc> chg_cell_element link_fail <value> <cell_desc> Display command strings disp_cell <cell_desc> ["full"] disp_element link_fail <location> <cell_desc> 68P02901W23-P 23 Feb 2004 5-469 GMR-01 . This parameter is also known as the T100_TIMER. the count in S is decremented by 1.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. The BSS continues transmitting on the downlink until S reaches 0. S is set to the value specified for link_fail. 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 radio link failure criterion is based on the radio link counter S. ... . .. 5-470 GMR-01 68P02901W23-P 23 Feb 2004 ....link_fail Chapter 5: CM database parameters Values Value type Integer (1 step = 4 SACCH multiframes) Valid range 0 to 15 Represents the number of SACCH multiframes as shown below: 0 4 SACCH frames 1 8 SACCH frames 2 12 SACCH frames .. .. 15 64 SACCH frames Default value 4 (20 SACCH frames) References Internal name RADIO_LINK_TIMEOUT(BS) This is a Motorola defined parameter.. .... all LMTLs must be in the locked state in order for the modification to take effect. This parameter cannot be modified or displayed at a RXCDR site. Operator actions Set element state Syntax Change command string chg_element lmtl_loadshare_granularity <value> <location> Display command string disp_element lmtl_loadshare_granularity <location> Values Value type Integer Valid range 0 Corresponds to granularity of 16 1 Corresponds to granularity of 64 Default value 68P02901W23-P 23 Feb 2004 0 5-471 GMR-01 .Technical Description BSS Command Reference lmtl_loadshare_granularity lmtl_loadshare_granularity Description The lmtl_loadshare_granularity parameter specifies the level of granularity for LMTL load sharing. Type B (operator actions required) Supported by OMC-R GUI Yes Cell numbers required No Dependencies If this parameter is modified outside SYSGEN mode. 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. This is used to synchronize the database in the BSS and the data modelled in the OMC-R MIB. 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 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_cell_id del_cell add_neighbor chg_csfp del_neighbor add_rtf_path chg_eas_alarm del_rtf_path add_xbl_conn chg_element del_smscb_msg 5-472 GMR-01 68P02901W23-P 23 Feb 2004 . When this parameter is disabled. 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.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. 68P02901W23-P 23 Feb 2004 5-473 GMR-01 .Technical Description BSS Command Reference local_maintenance {23658}bep_period chg_hopping del_xbl_conn {23658}bep_period2 chg_ksw_config equip cell_name chg_rtf_freq modify_neighbor chg_a5_alg_pr chg_rxcdr_gbu modify_value chg_act_alg_data chg_smscb_msg {23658}tlli_blk_coding chg_audit_sched copy_cell unequip chg_cell_element copy_path 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 Type B (operator actions required) Supported by OMC-R GUI Yes Cell numbers required No Dependencies None Operator actions Place the system in the SYSGEN ON mode before using the chg_element command to change this parameter. local_maintenance Chapter 5: CM database parameters Syntax Change command string chg_element local_maintenance <value> <location> Display command string disp_element local_maintenance <location> Values Value type Boolean Valid range 0 or 1 Default value 0 Disabled 1 Enabled 1 5-474 GMR-01 68P02901W23-P 23 Feb 2004 . the handover takes place to the coincident cell. and a handover is triggered to a cell with a coincident cell. using a MultiBand MS. When a call. if the measured receive level from the target cell exceeds this parameter value.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. is on any cell. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required Yes Dependencies None Syntax Change command strings chg_element low_sig_thresh <value> <location> <cell_desc> chg_cell_element low_sig_thresh <value> <cell_desc> Display command string disp_element low_sig_thresh <location> <cell_desc> Values Value type Integer Valid range 0 to 63 Default value 0 68P02901W23-P 23 Feb 2004 5-475 GMR-01 . 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. 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. Temperature changes can cause the frequency generated by the VCXO (Voltage Controlled Crystal Oscillator) to vary. Syntax Change command string chg_element lta_alarm_range <value> <location> Display command string disp_element lta_alarm_range <location> Values Value type Integer Valid range 1 to 255 Default value 7 5-476 GMR-01 68P02901W23-P 23 Feb 2004 . This value should not be changed unless it is known that the MMS or uplink clock is faulty. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required No Dependencies This parameter is not valid at an M-Cell site. The register centre value is 80h. Up to 48 clock frequency readings are stored. These stored readings are used to calculate the LTA. The CLKFREQ register is used to maintain the correct frequency generated by the VCXO (Voltage Controlled Crystal Oscillator). The default range (7) is sufficient to compensate for normal day to day variations in temperature.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. 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> Display command string disp_element max_gprs_ts_per_carrier <location> <cell_desc> Values Value type Integer Valid range 1 to 8 Default value 8 68P02901W23-P 23 Feb 2004 5-477 GMR-01 . Enough timeslots must be available on all of the GPRS cell carriers.Technical Description BSS Command Reference max_gprs_ts_per_carrier max_gprs_ts_per_carrier Description The max_gprs_ts_per_carrier parameter specifies the maximum number of timeslots (switchable and reserved) that the BSS should allocate to an RTF. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required Yes Dependencies The GPRS feature must be unrestricted and the gprs_ts_config_alg must be set to 1. 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.) 5-478 GMR-01 68P02901W23-P 23 Feb 2004 .2 bytes. BSS software processes using this parameter are notified immediately the change is made. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required Yes Dependencies The GPRS feature must be unrestricted. Syntax Change command strings chg_element max_ms_dl_buffer <value> <location> <cell_desc> chg_cell_element max_ms_dl_buffer <value> <cell_desc> Display command string disp_element max_ms_dl_buffer <location> [<cell_desc>] Values Value type Integer Valid range 1600 to 20000 (one step = 3. . ... 64000 bytes 12000 (equivalent to 38400 bytes) Each step adds 3. .Technical Description BSS Command Reference 1600 . .. 68P02901W23-P 23 Feb 2004 5-479 GMR-01 . setting max_ml_dl_buffer to 1603 defines a buffer size of 5129 bytes.... ..2 bytes of buffer length with fractions of bytes being ignored... 20000 Default value max_ms_dl_buffer 5120 bytes .. For example.. 5-480 GMR-01 68P02901W23-P 23 Feb 2004 .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 Change command strings chg_element max_ms_dl_rate <value> <location> <cell_desc> chg_cell_element max_ms_dl_rate <value> <cell_desc> Display command string disp_element max_ms_dl_rate <location> <cell_desc> Values Value type Integer (100 bits per second) Valid range 1 to 900 Default value 900 (equivalent to 90000 bits per second) The units for this parameter is 100 bits per second. The equivalent range in bits per second is 100 to 90000. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required Yes Dependencies The GPRS feature must be unrestricted. When the value is set to 2.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. the system displays a warning message and accepts the command. LCF Type B (no operator actions) Supported by OMC-R GUI Yes Cell description required No Dependencies Change the security level to 2 to modify this parameter. non-RXCDR system. This parameter must be set to 1 for all BSPs on a bsc_type 0. Device/Function BSP. This parameter must be set to 1 for at least one LCF on a BSC site where the BSC type is not zero. Use of all locations option No Syntax Add/Change command strings modify_value <location> max_mtls <value> bsp <dev_fun_id1> <dev_fun_id2> <dev_fun_id3> modify_value <location> max_mtls <value> lcf <dev_fun_id1> <dev_fun_id2> <dev_fun_id3> equip <location> bsp equip <location> lcf Display command strings disp_equipment <location> bsp <id1> <id2> <id3> disp_equipment <location> lcf <id1> <id2> <id3> 68P02901W23-P 23 Feb 2004 5-481 GMR-01 . Set this parameter to 2 for GPROC2 {4354} and GPROC3 boards. max_mtls Chapter 5: CM database parameters Values Value type Integer Valid range 0 to 2 Default value None 5-482 GMR-01 68P02901W23-P 23 Feb 2004 . 48). 20.. 12. Syntax Change command string chg_element max_number_of_sdcchs <value> <location> <cell_desc> Display command strings disp_cell <cell_desc> ["full"] 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. For non-combined channel configurations. 16.. 24. the values must be in multiples of 8 with an offset of 4 (such as 0.. 4.44). It determines the maximum limit of the SDCCHs that the CRM will maintain. Default value 68P02901W23-P 23 Feb 2004 None 5-483 GMR-01 . 8.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. 16. If ccch_conf  1.. 32 SDs. 28 SDs... the values can be 8. Type A (no operator actions) Supported by OMC-R GUI Yes Cell description required Yes Dependencies For combined channel configurations. the values can be 4.. 12. the values must be in multiples of 8 with an offset of 0 (such as 0. 02 .4 This is a Motorola defined parameter.6.max_number_of_sdcchs Chapter 5: CM database parameters References GSM specification 5. 5-484 GMR-01 68P02901W23-P 23 Feb 2004 . queuing is not allowed. Syntax Change command strings {4322} chg_element max_q_length_channel <value> <location> <cell_desc> chg_cell_element max_q_length_channel <value> <cell_desc> Display command string {4322} disp_element max_q_length_channel <location> <cell_desc> 68P02901W23-P 23 Feb 2004 5-485 GMR-01 . the network may place the traffic channel request in queue. If the queue length is 0. If an idle traffic channel is not available at the channel assignment instant.Technical Description BSS Command Reference max_q_length_channel max_q_length_channel Description {4322}The max_q_length_channel parameter specifies the maximum number of MSs that may wait in queue for a full rate channel assignment. Before GSR7. this parameter was named {4322}max_q_length_full_rate_channel. Type A (no operator actions) Supported by OMC-R GUI Yes Cell description required Yes Dependencies The sum of {4322} max_q_length_channel + max_q_length_sdcch must be less than or equal to queue_management_information. 01: conditions to apply call queuing This is a Motorola defined parameter.2.5.1.1.max_q_length_channel Chapter 5: CM database parameters Values Value type Integer (representing the number of MSs in the queue) Valid range 0 to 50 Default value 0 References GSM specification 4.08 .10 3. 5-486 GMR-01 68P02901W23-P 23 Feb 2004 . Technical Description BSS Command Reference max_q_length_sdcch max_q_length_sdcch Description The max_q_length_sdcch parameter specifies the maximum length of the queue for Stand-alone Dedicated Control Channel (SDCCH) requests. Type A (no operator actions) Supported by OMC-R GUI Yes Cell description required Yes Dependencies The sum of max_q_length_full_rate_channel + max_q_length_sdcch must be less than or equal to queue_management_information. Syntax Change command string chg_element max_q_length_sdcch <value> <location> <cell_desc> chg_cell_element max_q_length_sdcch <value> <cell_desc> Display command string disp_element max_q_length_sdcch <location> <cell_desc> Values Value type Integer (represents the number of requests) Valid range 0 to 50 Default value None 68P02901W23-P 23 Feb 2004 5-487 GMR-01 . max_retran Chapter 5: CM database parameters max_retran Description The max_retran parameter specifies the maximum channel request retransmission value for MSs. Type A (no operator actions) Supported by OMC-R GUI Yes Cell description required Yes Dependencies None Syntax Add/Change command strings add_cell <gsm_cell_id> <location> chg_element max_retran <value> <location> <cell_desc>chg_cell_element max_retran <value> <cell_desc> Display command strings disp_cell <cell_desc> ["full"] disp_element max_retran <location> <cell_desc> Values Value type Integer Valid range 0 to 3 Default value 0 Maximum [1] retransmission 1 Maximum [2] retransmissions 2 Maximum [4] retransmissions 3 Maximum [7] retransmissions 0 5-488 GMR-01 68P02901W23-P 23 Feb 2004 . 08 .08 .1: request for resources by the MS 4.08 . fig.17.20 .3. table 10.6.1.max Number Retransmission 68P02901W23-P 23 Feb 2004 5-489 GMR-01 .5.5.7 cell Description .3.2: cell reselection 12.8.Technical Description BSS Command Reference max_retran References GSM parameter MAX_RETRANS GSM specification 4.10. 10.2.6.30 5.2.36. Syntax Change command string chg_element max_rst_ckt_timer_exps <value> 0 Display command string disp_element max_rst_ckt_timer_exps 0 Values Value type Integer (represents the number of repeats) Valid range 0 to 100 The value 0 means the system keeps sending the “Reset Circuit" message indefinitely. Type A (no operator actions) Supported by OMC-R GUI Yes Cell description required No Dependencies This parameter only applies to the BSC.max_rst_ckt_timer_exps Chapter 5: CM database parameters max_rst_ckt_timer_exps Description The max_rst_ckt_timer_exps parameter specifies the number of times that the Reset Circuit message is repeated if there is no answer from the MSC. Default value 1 5-490 GMR-01 68P02901W23-P 23 Feb 2004 . and DCS1800. and DCS1800. Type A (no operator actions) Supported by OMC-R GUI Yes Cell description required Yes Dependencies frequency_type Syntax Change command strings chg_element max_tx_bts <value> <location> <cell_desc> chg_cell_element max_tx_bts <value> <cell_desc> Display command strings disp_cell <cell_desc> ["full"] disp_element max_tx_bts <location> <cell_desc> Values Value type Integer (1 step = 2 dBm) Valid range -1 to 21 0 to 6 Default value None 68P02901W23-P 23 Feb 2004 For PGSM. M-Cellaccess and Horizoncompact. This can be used to establish a cell boundary. For M-Cellmicro. The range is 7 steps of 2 dBm per step for M-Cellmicro. A BTS is capable of reducing its power in a range of 23 steps of 2 dBm per step for PGSM. EGSM. M-Cellaccess and Horizoncompact.Technical Description BSS Command Reference max_tx_bts max_tx_bts Description The max_tx_bts parameter specifies the maximum output power for a BTS within its power class. 5-491 GMR-01 . EGSM. external. Table 5-22 lists the values for the CTU2. Table 5-23 also specifies the types of combing used: none.max_tx_bts Chapter 5: CM database parameters Refer to Table 5-22. The values represent the calibrated output power at the top of the cabinet with one stage of combining. All figures are ± 2 dB. and both internal and external. The power specified is the cabinet antenna connector maximum output power. Table 5-25. The combining types are defined as follows: 5-492 GMR-01 68P02901W23-P 23 Feb 2004 . Table 5-24. 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. internal. and Table 5-26 for additional information about the values for this parameter. Table 5-23. etc. Hence the power firgure internal combining represents two carriers at this transmit power for a CTU2 in DD-DCM. EGSM. • External (to the XCVR): The output of the XCVR is connected via a single stage of external hybrid combining to the antenna. 68P02901W23-P 23 Feb 2004 5-493 GMR-01 . Note that the internal combining is still present when the CTU2 is used in DD-SCM. Table 5-24 Values for PGSM. DCS1800 and PCS1900. Table 5-23 Cabinet antenna connector maximum output power (Watts) XCVR Type CTU CTU2 SD-SCM CTU2 DD-DCM Combining Horizonmacro Horizon II macro EGSM900 DCS1800 EGSM900 DCS1800 None 40 32 N/A N/A External 20 16 N/A N/A None 40 32 63 50 External 20 16 28 22 Internal 10 10 20 16 Internal and external 4. M-Cellcity.5 4. this would allow two CTU2 in DD-DCM to be combined to create a four-carrier sector.Technical Description BSS Command Reference max_tx_bts • None: The output power of the XCVR is connected directly to the antenna. For example. This is not applicable for a DDM as it always uses a single stage of internal combining within the XCVR itself. and M-Cellaccess sites. a two-carrier sector is required from two SDX or two CTU2-SD. Horizonmicro (M-Cellarena) and Horizoncompact (M-Cellarenamacro) sites.5 9 7 Table 5-24 lists the values for PGSM. sites Valid Input PGSM and EGSM M-Cellmicro values DCS1800 and PCS1900 M-Cellmicro values Horizoncompact (M-Cellarenamacro) values 0 31 dBm 30 dBm 40 dBm 1 29 dBm 28 dBm 38 dBm 2 27 dBm 26 dBm 36 dBm 3 25 dBm 24 dBm 34 dBm 4 23 dBm 22 dBm 32 dBm 5 21 dBm 20 dBm 30 dBm 6 19 dBm 18 dBm 28 dBm Table 5-25 lists the values for DCS1800. • Internal and external: External hybrid combining is used on a CTU2 in DDM. DCS1800 and PCS1900 M-Cellmicro. For example. EGSM. • 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. BTS6 6 M-Cell2 or M-Cell6 6 The listed power is valid for 600 kHz minimum channel distance. and M-Cellaccess values DCS1800 M-Cellaccess values 0 12 dBm 17 dBm 1 10 dBm 15 dBm 2 8 dBm 13 dBm 3 6 dBm 11 dBm 4 4 dBm 9 dBm 5 2 dBm 7 dBm 6 0 dBm 5 dBm The actual output power of a cabinet depends on the type of combining that is used.max_tx_bts Chapter 5: CM database parameters Table 5-25 Values for DCS1800 and M-Cellaccess sites Valid Input PGSM.5W [Symbol_approximate] 43.14 dBm hybrid 2 17.01 dBm cavity (1 cabinet) ” 6 19W [Symbol_approximate] 42. BTS5. of some Motorola cabinets with different combinations of radios and combiners. measured at the top of the cabinet. Table 5-26 lists sample output power.98 dBm cavity (2 neighbouring cabinets) ” 10 13W [Symbol_approximate] 41.5W [Symbol_approximate] 41. Table 5-26 Sample output power Type of combining Number of radios Output power (as calibrated) hybrid 2 20W [Symbol_approximate] 43.79 dBm duplexer ” 4 13.01 dBm cavity (1 cabinet) ” 5 25W [Symbol_approximate] 43.30 dBm BTS4. and for 800 kHz minimum channel distance with cavity combining. EGSM. 5-494 GMR-01 68P02901W23-P 23 Feb 2004 . 68P02901W23-P 23 Feb 2004 5-495 GMR-01 . Table 5-27 Value interpolation max_tx_bts input Maximum output power of a BTS in relation to the combining configuration –1 45 dBm 44 dBm 43 dBm 42 dBm 41 dBm 0 44 dBm 43 dBm 42 dBm 41 dBm 40 dBm 1 42 dBm 41 dBm 40 dBm 39 dBm 38 dBm 2 40 dBm 39 dBm 38 dBm 37 dBm 36 dBm 3 38 dBm 37 dBm 36 dBm 35 dBm 34 dBm 4 36 dBm 35 dBm 34 dBm 33 dBm 32 dBm 5 34 dBm 33 dBm 32 dBm 31 dBm 30 dBm 6 32 dBm 31 dBm 30 dBm 29 dBm 28 dBm 7 30 dBm 29 dBm 28 dBm 27 dBm 26 dBm 8 28 dBm 27 dBm 26 dBm 25 dBm 24 dBm 9 26 dBm 25 dBm 24 dBm 23 dBm 22 dBm 10 24 dBm 23 dBm 22 dBm 21 dBm 20 dBm 11 22 dBm 21 dBm 20 dBm 19 dBm 18 dBm 12 20 dBm 19 dBm 18 dBm 17 dBm 16 dBm 13 18 dBm 17 dBm 16 dBm 15 dBm 14 dBm 14 16 dBm 15 dBm 14 dBm 13 dBm 12 dBm 15 14 dBm 13 dBm 12 dBm 11 dBm 10 dBm 16 12 dBm 11 dBm 10 dBm 9 dBm 8 dBm 17 10 dBm 9 dBm 8 dBm 7 dBm 6 dBm 18 8 dBm 7 dBm 6 dBm 5 dBm 4 dBm 19 6 dBm 5 dBm 4 dBm 3 dBm 2 dBm 20 4 dBm 3 dBm 2 dBm 1 dBm 0 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.Technical Description BSS Command Reference max_tx_bts Interpolation table Table 5-27 can be used to interpolate the values between the specified settings. 2 . 5.4. 5.2.5.max_tx_bts Chapter 5: CM database parameters References GSM parameter BS_TXPWR_RED GSM specification For MAX see GSM Rec.20 . 12.BS Tx Pwr Max 12.1.Tx power 5-496 GMR-01 68P02901W23-P 23 Feb 2004 .8.2 Rec.power Ctrl BTS .20 .23 .05 .5.2.8.08-BS_TXPWR_MAX. mstxpwr_max_inner must also be updated. This parameter is also used in the power budget calculation. Regardless of the power class of the MS. The value should be chosen to balance the up and down links in a cell.Technical Description BSS Command Reference max_tx_ms max_tx_ms Description The max_tx_ms parameter specifies the maximum MS (Mobile Station) output power. the MS is not told to use a higher output power. If the range or default value of max_ts_ms changes. Type A (no operator actions) Supported by OMC-R GUI Yes Cell description required Yes Dependencies The range and default values of ms_txpwr_max_inner depends on this parameter. to a value less than or equal to max_ts_ms. Syntax Add/Change command strings add_cell <gsm_cell_id> <location> chg_element max_tx_ms <value> <location> <cell_desc> chg_cell_element max_tx_ms <value> <cell_desc> Display command strings disp_cell <cell_desc> ["full"] disp_element max_tx_ms <location> <cell_desc> Values Value type Integer (dBm) Valid range 5 to 39 PGSM and EGSM (Odd values only) 0 to 36 DCS1800 (Even values only) 68P02901W23-P 23 Feb 2004 5-497 GMR-01 . 08 .33 Default value PCS1900 (Even values only and value 33) Highest allowed value References GSM parameter MS_TXPWR_MAX GSM specification 5.4.3 5.1 5-498 GMR-01 68P02901W23-P 23 Feb 2004 .05 .max_tx_ms Chapter 5: CM database parameters 0 to 32.4. Technical Description BSS Command Reference mb_preference mb_preference Description The mb_preference parameter enables or disables the Multiband Inter-cell Handover feature. Syntax Change command string chg_element mb_preference <value> <location> Display command string disp_element mb_preference <location> Values Value type Boolean Valid range 0 or 1 Default value 68P02901W23-P 23 Feb 2004 0 Disabled 1 Enabled 0 5-499 GMR-01 . Type A (no operator actions) Supported by OMC-R GUI Yes Cell description required No Dependencies This parameter is unavailable if the Multiband Inter-Cell Handover feature is restricted. This parameter may not be disabled when inner_zone_alg is set to indicate Dual Band Cells for any cell in the BSS. ) Valid range 1 to 101 The value 101 indicates there are no resources left to allocate). • mb_preference element must be enabled. The parameter is expressed as a percentage. Syntax Change command string chg_element mb_tch_congest_thres <value> <location> <cell_desc> Display command string disp_element mb_tch_congest_thres <location> <cell_desc> Values Value type Integer (representing a percentage.mb_tch_congest_thres Chapter 5: CM database parameters mb_tch_congest_thres Description The mb_tch_congest_thres parameter specifies the level of overall TCH utilization by any MS in a given Cell. • mb_tch_congest_thres must be less than or equal to tch_congest_prevent_thres. Type A (no operator actions) Supported by OMC-R GUI Yes Cell number required Yes Dependencies The parameter can be set only if • the Congestion Relief feature is unrestricted (ho_exist_congest element must be enabled). Default value 100 The value 100 indicates an attempt to use the last resource. 5-500 GMR-01 68P02901W23-P 23 Feb 2004 . at which a MultiBand MS is redirected to the preferred band (as set by band_preference). • band_preference_mode must be set to 6 (the mode which triggers when a Cell is congested). averaging. and processing of downlink power control and handovers. Type A (no operator actions) Supported by OMC-R GUI Yes Cell description required Yes Dependencies None Syntax Add/Change command strings chg_element missing_rpt <value> <location> <cell_desc> chg_cell_element missing_rpt <value> <cell_desc> Display command strings disp_cell <cell_desc> ["full"] disp_element missing_rpt <location> <cell_desc> Values Value type Boolean Valid range 0 or 1 Default value 68P02901W23-P 23 Feb 2004 0 Disabled 1 Enabled None 5-501 GMR-01 .Technical Description BSS Command Reference missing_rpt missing_rpt Description The missing_rpt parameter enables or disables the suspension of the storing. This parameter is valid only at the BSC. Operator actions Place the system in SYSGEN ON mode Syntax Change command string chg_element mmi_cell_id_format <value> 0 Display command string disp_element mmi_cell_id_format 0 Values Value type Boolean Valid range 0 or 1 Default value 0 7-parameter format 1 4-parameter format 0 5-502 GMR-01 68P02901W23-P 23 Feb 2004 . The formats available are: 4-parameter and 7-parameter. Type B (operator actions required) Supported by OMC-R GUI No Cell description required No Dependencies The system must be in SYSGEN ON mode to modify this parameter. PCS1900 systems accept only the 4-parameter cell number format.mmi_cell_id_format Chapter 5: CM database parameters mmi_cell_id_format Description The mmi_cell_id_format parameter specifies the format that the MMI command line accepts for the GSM Cell Identification number. the MMS is brought back into service automatically. This action is taken because the MMS is showing signs of instability. and the Critical Alarm Threshold Exceeded alarm is reported against the MMS device. When mms_cat_enable is enabled. A lock/unlock of the MMS overrides this periodic auditing and brings the MMS into service immediately. after the 10th clear the MMS stays OOS even though the alarm is cleared. and the Critical alarm Threshold Exceeded alarm is cleared. Type A (no operator actions) Supported by OMC-R GUI No Cell description required No Dependencies None Syntax Change command string chg_element mms_cat_enable <value> <location> Display command string disp_element mms_cat_enable <location> Values Value type Boolean Valid range 0 or 1 0 68P02901W23-P 23 Feb 2004 Disabled 5-503 GMR-01 . 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 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.Technical Description BSS Command Reference mms_cat_enable mms_cat_enable Description The mms_cat_enable parameter enables or disables the MMS Critical Alarm Threshold (CAT) for MMS stability testing. When this happens 10 times in 10 minutes. When mms_cat_enable is disabled. the MMS remains in service even if the MMS CAT is met or exceeded. mms_cat_enable Chapter 5: CM database parameters 1 Default value Enabled 0 5-504 GMR-01 68P02901W23-P 23 Feb 2004 . the value of this parameter can be changed at any time for any site. • mms_config_type cannot be changed to 1 if land_layer1_mode = 1 (T1). where: • For E1 systems (land_layer1_mode =0). For T1 systems. E1 or T1. a warning message saying the MMSs must be reset to have the change take effect at that site will display.Technical Description BSS Command Reference mms_config_type mms_config_type Description The mms_config_type parameter specifies the signalling type for all MMSs. Syntax Change command string chg_element mms_config_type <value> <location> 68P02901W23-P 23 Feb 2004 5-505 GMR-01 . If executed outside SYSGEN mode. The signalling type depends on the carrier type being used. Operator actions For E1 systems. delete the existing database using the clear_database command then place the system in the initial SYSGEN mode. 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. reset the MSIs for a change to this parameter to take effect. The value of mms_config_type must be the same at the BSC and the PCU sites. Type B (operator actions required) Supported by OMC-R GUI Yes Cell description required No Dependencies The value of the land_layer1_mode parameter. mms_config_type Chapter 5: CM database parameters 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. Display command string 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 Default value ESF 0 5-506 GMR-01 68P02901W23-P 23 Feb 2004 . Type A (no operator actions) Supported by OMC-R GUI Yes Cell description required Yes Dependencies ms_max_range Syntax Add/Change command strings add_cell <gsm_cell_id> <location> chg_element ms_distance_allowed <value> <location> <cell_desc> chg_cell_element ms_distance_allowed <value> <cell_desc> Display command strings disp_cell <cell_desc> ["full"] disp_element ms_distance_allowed <location> <cell_desc> Values Value type Boolean Valid range 0 or 1 Default value 68P02901W23-P 23 Feb 2004 0 Disabled 1 Enabled 0 5-507 GMR-01 . If this parameter is 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.Technical Description BSS Command Reference ms_distance_allowed ms_distance_allowed Description The ms_distance_allowed parameter disables or enables the distance comparison process for handovers. When enabled. the value chosen for ms_max_range needs careful optimization. 3.2.enable MS Distance Process This is a Motorola defined parameter.18 .08 .2d . 5-508 GMR-01 68P02901W23-P 23 Feb 2004 .enable BSS Handover Control .Appendix A.2.8.1 (f): PBGT(n) .ms_distance_allowed Chapter 5: CM database parameters References GSM specification 5.20 . 3. 3d 12.5. 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. Type A (no operator actions) Supported by OMC-R GUI Yes Cell description required Yes Dependencies The range for the ms_max_range parameter depends on whether the Extended Range feature is enabled or disabled. 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.Technical Description BSS Command Reference ms_max_range ms_max_range Description The ms_max_range parameter specifies the MS maximum range for the handover algorithm. Syntax Add/Change command strings add_cell <gsm_cell_id> <location> chg_element ms_max_range <value> <location> <cell_desc> chg_cell_element ms_max_range <value> <cell_desc> Display command strings disp_cell <cell_desc> ["full"] disp_element ms_max_range <location> <cell_desc> 68P02901W23-P 23 Feb 2004 5-509 GMR-01 . the maximum value of ms_max_range increases to 219. This parameter must be programmed in terms of timing advance bits. 62 63 468..75 0 0..75 0 0..75 464.75 405.ms_max_range Chapter 5: CM database parameters Values Value type Integer Valid range 0 to 63 for normal cells (see Table 5-28). . Table 5-29 ms_max_range values for Extended Range cells Timing advance bits Bit periods delayed Distance of MS to BSS (km) 0 1 2 3 4 .Appendix A ..75 . 218 219 468..215 . .75 465.75 466. 34.554 1. 406...8 5-510 GMR-01 68P02901W23-P 23 Feb 2004 .108 1.. .75 ... the maximum value of ms_max_range increases to 219.75 464. .772 121...326 References GSM parameter MS_RANGE_MAX GSM specification 5. 0 to 219 for Extended Range cells (see Table 5-29)..10 .662 2.75 466..08 .662 2...75 467..108 1. .Table 1: MS_RANGE_MAX 5.....338 34.892 If the Extended Range Feature is unrestricted and Extended Range is enabled in the cell.. 250.. 120.215 ..5. 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 1 2 3 4 .75 467.75 465.75 249. .554 1. . 5-511 GMR-01 .. This parameter is effective only if the decision_alg_num equals 1. Type A (no operator actions) Supported by OMC-R GUI Yes Cell description required Yes Dependencies decision_alg_num = 1 Syntax Add/Change command strings add_cell <gsm_cell_id> <location> chg_element ms_p_con_ack <value> <location> <cell_desc> chg_cell_element ms_p_con_ack <value> <cell_desc> Display command strings disp_cell <cell_desc> ["full"] disp_element ms_p_con_ack <location> <cell_desc> Values Value type Integer (1 step = 2 SACCH multiframes) Valid range 0 to 31 68P02901W23-P 23 Feb 2004 0 0 SACCH multiframes 1 2 SACCH multiframes 2 4 SACCH multiframes .. .Technical Description BSS Command Reference ms_p_con_ack 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.. . . 31 62 SACCH multiframes 2 References Internal name P_CON_ACK This is a Motorola defined parameter. ... 5-512 GMR-01 68P02901W23-P 23 Feb 2004 .......ms_p_con_ack Chapter 5: CM database parameters Default value . then the minimum recommended value for ms_p_con_interval equals 2 plus hreqave divided by 2 (2+hreqave/2). • If decision_alg_num = 1. Type A (no operator actions) Supported by OMC-R GUI Yes Cell description required Yes Dependencies hreqave Syntax Add/Change command strings add_cell <gsm_cell_id> <location> chg_element ms_p_con_interval <value> <location> <cell_desc> chg_cell_element ms_p_con_interval <value> <cell_desc> Display command strings disp_cell <cell_desc> ["full"] disp_element ms_p_con_interval <location> <cell_desc> Values Value type Integer (1 step = 2 SACCH multiframes) Valid range 0 to 31 68P02901W23-P 23 Feb 2004 5-513 GMR-01 . This value depends on the value for the decision_alg_num parameter. • If decision_alg_num = 0. then the recommended value for ms_p_con_interval equals hreqave divided by 2 (hreqave/2).Technical Description BSS Command Reference ms_p_con_interval 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. .ms_p_con_interval Chapter 5: CM database parameters Default value 0 0 SACCH multiframes 1 2 SACCH multiframes 2 4 SACCH multiframes . ..... 31 62 SACCH multiframes 2 References Internal name P_CON_INTERVAL This is a Motorola defined parameter.. . 5-514 GMR-01 68P02901W23-P 23 Feb 2004 .. .. Type A (no operator actions) Supported by OMC-R GUI Yes Cell description required Yes Dependencies None Syntax Add/Change command strings add_cell <gsm_cell_id> <location> chg_element ms_power_control_allowed <value> <location> <cell_desc> chg_cell_element ms_power_control_allowed <value> <cell_desc> Display command strings disp_cell <cell_desc> ["full"] disp_element ms_power_control_allowed <location> <cell_desc> Values Value type Boolean Valid range 0 or 1 Default value 68P02901W23-P 23 Feb 2004 0 Disabled 1 Enabled 1 5-515 GMR-01 . Enabling this feature helps to reduce interference.Technical Description BSS Command Reference ms_power_control_allowed ms_power_control_allowed Description The ms_power_control_allowed parameter enables or disables MS power control. 5-516 GMR-01 68P02901W23-P 23 Feb 2004 .ms_power_control_allowed Chapter 5: CM database parameters References Internal name EN_MS_PC This is a Motorola defined parameter. Syntax Change command strings chg_element ms_power_offset <value> <location> <cell_desc> chg_cell_element ms_power_offset <value> <cell_desc> Display command strings disp_cell <cell_desc> ["full"] disp_element ms_power_offset <location> <cell_desc> Values Value type Integer (1 step = 2 dB) Valid range 0 to 3 Default value 68P02901W23-P 23 Feb 2004 0 0 dB 1 2 dB 2 4 dB 3 6 dB 0 5-517 GMR-01 .Technical Description BSS Command Reference ms_power_offset 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. Type A (no operator actions) Supported by OMC-R GUI Yes Cell description required Yes Dependencies If the cell is not a type 3 MS cell. The value is a positive power offset from the value set by ms_txpwr_max_cch. 0 is the only value allowed. the MS uses one of two possible power levels. This parameter is expressed as a power level value. The MS uses the lower power level of the two available: either the ms_txpwr_max_cch broadcast on the BCCH or the maximum transmit power as defined by the power class of the MS. Type A (no operator actions) Supported by OMC-R GUI Yes Cell description required Yes Dependencies frequency_type Syntax Add/Change command strings add_cell <gsm_cell_id> <location> chg_element ms_txpwr_max_cch <value> <location> <cell_desc> chg_cell_element ms_txpwr_max_cch <value> <cell_desc> Display command strings disp_cell <cell_desc> ["full"] disp_element ms_txpwr_max_cch <location> <cell_desc> Values Value type Integer (1 step = 2 dBm) 5-518 GMR-01 68P02901W23-P 23 Feb 2004 .ms_txpwr_max_cch Chapter 5: CM database parameters 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. Before accessing a cell on the RACH and before receiving the first power command during a communication on a DCCH (or TCH). 30.Technical Description BSS Command Reference ms_txpwr_max_cch 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-31 Maximum mobile power level for DCS1800 cells 68P02901W23-P 23 Feb 2004 Value Range Value Range 29 36 dBm 7 16 dBm 30 34 dBm 8 14 dBm 31 32 dBm 9 12 dBm 0 30 dBm 10 10 dBm 1 28 dBm 11 8 dBm 2 26 dBm 12 6 dBm 3 24 dBm 13 4 dBm 4 22 dBm 14 2 dBm 5 20 dBm 15 0 dBm 6 18 dBm 5-519 GMR-01 . 31 for DCS1800 cells) Table 5-31 lists the maximum mobile power level for DCS1800 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. 2: ms_txpwr_max_cch 5.4.ms_txpwr_max_cch Chapter 5: CM database parameters Valid range (0 to 15.4: ms_txpwr_max_cch 5-520 GMR-01 68P02901W23-P 23 Feb 2004 . 30. 31 for PCS1900 cells) Table 5-32 lists the maximum mobile power level for PCS1900 cells.6. Table 5-32 Maximum mobile power level for PCS1900 cells Value Range Value Range 30 33 dBm 7 16 dBm 31 32 dBm 8 14 dBm 0 30 dBm 9 12 dBm 1 28 dBm 10 10 dBm 2 26 dBm 11 8 dBm 3 24 dBm 12 6 dBm 4 22 dBm 13 4 dBm 5 20 dBm 14 2 dBm 6 18 dBm 15 0 dBm Default value 2 References GSM parameter MS_TXPWR_MAX_CCH GSM specification 5.08 .08 . Type A (no operator actions) Supported by OMC-R GUI Yes Cell description required Yes Dependencies ms_txpwr_max_def Syntax Add/Change command strings 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> Display command strings disp_neighbor <src_gsm_cell_id> Values Value type Integer (dBm) Valid range 5 to 39 (Odd values only) PGSM and EGSM 0 to 36 (Even values only) DCS1800 0 to 32. 33 (Even values only and value 33) PCS1900 Default value 68P02901W23-P 23 Feb 2004 None 5-521 GMR-01 .Technical Description BSS Command Reference ms_txpwr_max_cell ms_txpwr_max_cell Description The ms_txpwr_max_cell parameter specifies the maximum MS transmit power in each neighbour cell. Table 1 5-522 GMR-01 68P02901W23-P 23 Feb 2004 .2. 3.ms_txpwr_max_cell Chapter 5: CM database parameters References GSM parameter MS_TXPWR_MAX(n) GSM specification 5.2e.1f: PBGT(n) . 5.08 .08 .Appendix A.Appendix A . and section 3. Technical Description BSS Command Reference ms_txpwr_max_def 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. 33 (Even values only and value 33) PCS1900 Default value 68P02901W23-P 23 Feb 2004 None 5-523 GMR-01 . Type A (no operator actions) Supported by OMC-R GUI Yes Cell description required Yes Dependencies ms_txpwr_max_cell Syntax Add/Change command strings add_cell <gsm_cell_id> <location> chg_element ms_txpwr_max_def <value> <location> <cell_desc> chg_cell_element ms_txpwr_max_def <value> <cell_desc> Display command strings disp_cell <cell_desc> ["full"] disp_element ms_txpwr_max_def <location> <cell_desc> Values Value type Integer (dBm) Valid range 5 to 39 (Odd values only) PGSM and EGSM 0 to 36 (Even values only) DCS1800 0 to 32. and section 3.Table 1 5-524 GMR-01 68P02901W23-P 23 Feb 2004 .1f: PBGT(n) .ms_txpwr_max_def Chapter 5: CM database parameters References GSM parameter MS_TXPWR_MAX_DEF GSM specification 5.2e.Appendix A .2. 5.08 .08 .Appendix A. 3. Technical Description BSS Command Reference ms_txpwr_max_inner ms_txpwr_max_inner Description The ms_txpwr_max_inner parameter specifies the maximum power an MS can use in the inner zone of a concentric cell. Type A (no operator actions) Supported by OMC-R GUI Yes Cell description required Yes Dependencies ms_txpwr_max_inner must be less than or equal to max_tx_ms if the value for inner_zone_alg equals 1 (Dual Band Cells). Syntax Change command strings chg_element ms_txpwr_max_inner <value> <location> <cell_desc> chg_cell_element ms_txpwr_max_inner <value> <cell_desc> Display command string disp_element ms_txpwr_max_inner <location> <cell_desc> Values Value type Integer (dBm) Valid range Depends on the system: Default value 68P02901W23-P 23 Feb 2004 5 to 39 (odd values only) PGSM/EGSM 0 to 30 (even values only) DCS1800 0 to 30 (even values only) PCS1900 Same value as max_ts_ms 5-525 GMR-01 . 5-526 GMR-01 68P02901W23-P 23 Feb 2004 . Type A (no operator actions) Supported by OMC-R GUI Yes Cell description required Yes Dependencies The Directed Retry or Multiband Inter-cell Handover feature must be unrestricted. Syntax Change command strings chg_element msc_preference <value> <location> <cell_desc> chg_cell_element msc_preference <value> <cell_desc> Display command string disp_element msc_preference <location> <cell_desc> Values Value type Integer Valid range 0 to 7 0 Directed Retry is supported within the BSS. which contains the optional Cell ID if the Cell ID changes during the assignment. This parameter is copied if the copy_cell command is used. but not across the A-interface. The cause value sent to the MSC can be set according to whether directed retry is supported by the MSC.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. The only A-interface impact is the Assignment Complete message. 1 Directed Retry is supported within the BSS. This parameter should align with the MSC implementation which may depend on whether queuing is enabled in the cell. Technical Description BSS Command Reference Default value msc_preference 2 The BSS sends the Handover Required message with the cause “directed retry" to the MSC.08 This is a Motorola defined parameter. 7 The BSS sends a Handover Required message with the cause of the handover (for example. Better Cell). 0 References GSM specification 68P02901W23-P 23 Feb 2004 TS GSM 08. 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-527 GMR-01 . 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. 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. Better Cell) and then sends an Assignment Failure message with cause “directed retry" to the MSC. Better Cell). 3 The BSS sends the Handover Required message with the cause of the handover to the MSC (for example. 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. This parameter must correspond to the MSC value for an idle PCM sample on the A interface. 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. In the uplink. The idle pattern should be 01010100. This parameter is not related to DTX. The binary pattern 01010100 corresponds to decimal 84 which is the default value of this parameter. Operator actions Place the system in SYSGEN ON mode Syntax Change command strings chg_element msc_qt <value> 0 chg_element msc_qt <value> xcdr 5-528 GMR-01 68P02901W23-P 23 Feb 2004 . When the XCDR receives this value from the MSC in all PCM samples in its 20 ms frame.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. Type B (operator actions required) Supported by OMC-R GUI No Cell description required No Dependencies This parameter only applies to the XCDR (location = 0). it outputs a TRAU idle speech frame. and on every timeslot of a channel that is not allocated to a call. it does not require any further changes. Technical Description BSS Command Reference msc_qt Display command strings disp_element msc_qt 0 disp_element msc_qt xcdr Values Value type Integer (decimal) Valid range 0 to 255 (representing bit patterns 00000000 to 11111111) Default value 84 (representing bit pattern 01010100) 68P02901W23-P 23 Feb 2004 5-529 GMR-01 . 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. Type A (no operator actions) Supported by OMC-R GUI Yes Cell description required No Dependencies None Syntax Change command string chg_element msc_release <value> <location> Display command string disp_element msc_release <location> Values Value type Integer Valid range 0 or 1 Default value 0 MSC is a Release 1998 or older 1 MSC is a Release 1999 or newer 0 5-530 GMR-01 68P02901W23-P 23 Feb 2004 . 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. Type A (no operator actions) Supported by OMC-R GUI Yes Cell description required Yes Dependencies None Syntax Add/Change command strings add_cell <gsm_cell_id> <location> chg_element mspwr_alg <value> <location> <cell_desc> chg_cell_element mspwr_alg <value> <cell_desc> Display command strings disp_cell <cell_desc> ["full"] disp_element mspwr_alg <location> <cell_desc> Values Value type Boolean Valid range 0 or 1 Default value 68P02901W23-P 23 Feb 2004 0 Disabled 1 Enabled 0 5-531 GMR-01 . the change takes effect immediately. Syntax Change command string chg_element mtl_loadshare_granularity <value> 0 Display command string disp_element mtl_loadshare_granularity 0 Values Value type Boolean Valid range 0 or 1 Default value 0 16 virtual circuits (regular granularity) 1 64 virtual circuits (enhanced granularity) 0 5-532 GMR-01 68P02901W23-P 23 Feb 2004 . Changes take effect only when all MTLs are locked. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required No Dependencies If the element is changed in SYSGEN ON mode.mtl_loadshare_granularity Chapter 5: CM database parameters mtl_loadshare_granularity Description The mtl_loadshare_granularity parameter sets the loadshare granularity across MTL links. 1 Report the strongest neighbour cell. Syntax Change command strings chg_element multiband_reporting <value> <location> <cell_desc> chg_cell_element multiband_reporting <value> <cell_desc> Display command string disp_element multiband_reporting <location> <cell_desc> Values Value type Integer Valid range 0 to 3 68P02901W23-P 23 Feb 2004 0 Normal reporting of the six strongest neighbour cells with known and allowed NCC part of the BSIC. with known and allowed NCC part of BSIC.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. Type A (no operator actions) Supported by OMC-R GUI Yes Cell description required Yes Dependencies The Multiband Inter-cell Handover feature must be enabled. The remaining positions in the measurement report shall be used for reporting Cells in the band of the serving Cell. excluding the frequency band of the serving cell. 5-533 GMR-01 . irrespective of the band used. in each of the frequency bands in the neighbour cell list. Any still remaining positions will be used to report the next strongest identified neighbours in other bands irrespective of the band used. The remaining positions in the measurement report shall be used for reporting Cells in the band of the serving Cell. in each of the frequency bands in the neighbour cell list. 3 Report the three strongest cells. Any still remaining positions will be used to report the next strongest identified neighbours in other bands irrespective of the band used. The remaining positions in the measurement report shall be used for reporting Cells in the band of the serving Cell.5.multiband_reporting Default value Chapter 5: CM database parameters 2 Report the two strongest cells.2. with known and allowed NCC part of BSIC. 0 References GSM specification TS GSM 04. 5-534 GMR-01 68P02901W23-P 23 Feb 2004 . in each of the frequency bands in the neighbour cell list. with known and allowed NCC part of BSIC. Any still remaining positions will be used to report the next strongest identified neighbours in other bands irrespective of the band used. excluding the frequency band of the serving cell. excluding the frequency band of the serving cell.08 section 10.22 This is a Motorola defined parameter. BSS software processes using this parameter are notified immediately the change is made. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required Yes Dependencies This parameter can be used only if the GPRS feature is unrestricted. Syntax Change command strings chg_element n_avg_i <value> <location> <cell_desc> chg_cell_element n_avg_i <value> <cell_desc> Display command string 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-P 23 Feb 2004 5-535 GMR-01 . and t_avg_w when in Packet Wait (idle) mode.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. PLMN operators serving a border area may agree to use NCCs of 0 and 4. and sixth bits are set which would allow NCC values of 0. fifth. the ncc_of_plmn_allowed value of 51 would bit map as: 00110011 The first. a bilateral agreement is required to determine the NCC values to be broadcast.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). Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required Yes Dependencies None Syntax Add/Change command strings add_cell <gsm_cell_id> <location> chg_element ncc_of_plmn_allowed <value> <location> <cell_desc> chg_cell_element ncc_of_plmn_allowed <value> <cell_desc> Display command strings disp_cell <cell_desc> ["full"] disp_element ncc_of_plmn_allowed <location> <cell_desc> 5-536 GMR-01 68P02901W23-P 23 Feb 2004 . and 6 to be broadcast on BCCH carriers. 1. second. In border areas where two PLMN operators provide overlapping service. 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. 5. For example. 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. For example. The selected values would be specified by entering a value that would bit map to the desired NCC. the corresponding NCC will not be allowed.08-9: PLMN_PERMITTED 68P02901W23-P 23 Feb 2004 5-537 GMR-01 .08-10.20-5.03-Annex A.34 and table 10. 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. When a bit is set to 1.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. the corresponding NCC will be allowed.2.5. figure 10.7 cell Description-plmn-permitting 4.8. When a bit is set to 0.28 5. NCCs per country 12.15.2. NCC GSM specification 3. 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. The PCU must be equipped. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required No Dependencies The GPRS and NCCR features must be unrestricted. Syntax Change command string chg_element nccr_enabled 1 0 Display command string disp_element nccr_enabled 0 Values Value type Boolean Valid range 0 or 1 Default value 0 Disabled 1 Enabled 0 5-538 GMR-01 68P02901W23-P 23 Feb 2004 . any attempt to access the other NCCR parameters is rejected. If restricted.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. Syntax Display command string disp_options Values Value type Boolean Valid range 0 or 1 Default value 68P02901W23-P 23 Feb 2004 0 Restricted 1 Unrestricted None 5-539 GMR-01 . Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required No Dependencies The GPRS and NCCR features must be unrestricted to provide their associated functionality. All neighbor information is padded with 0’s. If journaling is disabled: • There is a warmup period of the surround cell hreqave before power budget calculations begin. Averaging and power budget calculations will begin immediately. • Disuse count must reach 8 before being removed from the list of cell candidates for handover. • If a previously reported neighbor is missing in the measurement report.neighbor_journal Chapter 5: CM database parameters neighbor_journal Description The neighbor_journal parameter enables or disables neighbour journaling. • Disuse count must reach the cell list HREQAVE before being removed fro the list of cell candidates for handover. Type A (no operator actions) Supported by OMC-R GUI Yes Cell description required Yes Dependencies None Syntax Change command strings chg_element neighbor_journal <value> <location> <cell_desc> chg_cell_element neighbor_journal <value> <cell_desc> Display command string disp_element neighbor_journal <location> <cell_desc> 5-540 GMR-01 68P02901W23-P 23 Feb 2004 . • The last received rxlev for the unreported neighbor is used. a 0 rxlev is used for the neighbor. If journaling is enabled: • There is no warm up period for neighbours. Technical Description BSS Command Reference neighbor_journal Values Value type Boolean Valid range 0 or 1 Default value 68P02901W23-P 23 Feb 2004 0 Disabled 1 Enabled 0 5-541 GMR-01 . NC1 MS control GPRS mobile control with measurement reports. Table 5-34 list the available configurations. and pccch_enabled is set to 1 . any attempt to set the network_control_order parameter to any of the values 1.Enabled. BSS sends cell reselection commands and instructs mobile to perform cell reselection Enhanced NC0 MS control All functionality in NC0 mode. MS sends measurement reports to BSS. The PCU must be equipped. Table 5-34 Configurations for network_control_order Mode Responsible element NC0 MS control Normal GPRS mobile control. 5-542 GMR-01 68P02901W23-P 23 Feb 2004 . GPRS MS sends measurement reports to BSS.network_control_order Chapter 5: CM database parameters network_control_order Description The network_control_order parameter specifies the GPRS Cell Reselection order. BSS sends cell reselection command to GPRS mobile to change cell reselection mode Type A (no operator actions) Supported by OMC-R GUI Yes Cell description required Yes Dependencies The GPRS and NCCR features must be unrestricted. 2. 3 or 4. {3723} If inter_rat_enabled is set to 1 .Idle. will be rejected. MS performs autonomous cell re-selection NC2 MS control Network control. BSS sends reselection commands to GPRS. MS to change cell reselection mode Enhanced NC1 Network control Functionality All functionality in NC1 mode. Technical Description BSS Command Reference network_control_order Syntax Change command strings chg_element network_control_order <value> <location> <cell_desc> chg_cell_element network_control_order <value> <cell_desc> Display command string disp_element network_control_order <location> <cell_desc> Values Value type Integer Valid range 0 to 4 (mode values) Default value 68P02901W23-P 23 Feb 2004 0 NC0 1 NC1 2 NC2 3 Enhanced NC0 4 Enhanced NC1 0 5-543 GMR-01 . Syntax Change command string chg_element ni <value> 0 Display command string disp_element ni 0 Values Value type Integer Valid range 0 to 3 Default value 0 International Network 1 Spare (for international use only) 2 National Network 3 Reserved for national use None 5-544 GMR-01 68P02901W23-P 23 Feb 2004 .ni Chapter 5: CM database parameters 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. Type B (operator actions required) Supported by OMC-R GUI Yes Cell numbers required No Dependencies This parameter only applies to the BSC. TSS Q. 5-545 GMR-01 .708 This is a Motorola defined parameter.Technical Description BSS Command Reference ni References GSM specification 68P02901W23-P 23 Feb 2004 ITU . ns_alive_retries Chapter 5: CM database parameters ns_alive_retries Description The ns_alive_retries parameter specifies the number of retries generated to establish if a NSVC is alive. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required No Dependencies The GPRS feature must be unrestricted. Syntax Change command string chg_element ns_alive_retries <value> <location> Display command string disp_element ns_alive_retries <location> Values Value type Integer (number of retries) Valid range 1 to 10 Default value 3 5-546 GMR-01 68P02901W23-P 23 Feb 2004 . BSS software processes using this parameter are not notified when this parameter is changed. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required No Dependencies The GPRS feature must be unrestricted.Technical Description BSS Command Reference ns_block_retries ns_block_retries Description The ns_block_retries parameter specifies the number of retries generated to block a NSVC. BSS software processes using this parameter are not notified when this parameter is changed. Syntax Change command string chg_element ns_block_retries <value> <location> Display command string disp_element ns_block_retries <location> Values Value type Integer (number of retries) Valid range 1 to 3 Default value 3 68P02901W23-P 23 Feb 2004 5-547 GMR-01 . Syntax Change command string chg_element ns_unblock_retries <value> <location> Display command string disp_element ns_unblock_retries <location> Values Value type Integer (number of retries) Valid range 1 to 3 Default value 3 5-548 GMR-01 68P02901W23-P 23 Feb 2004 . Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required No Dependencies The GPRS feature must be unrestricted. BSS software processes using this parameter are not notified when this parameter is changed.ns_unblock_retries Chapter 5: CM database parameters ns_unblock_retries Description The ns_unblock_retires parameter specifies the number of retries generated to unblock a NSVC. The nsei parameter cannot be modified until all GBLs have been locked.Technical Description BSS Command Reference nsei nsei Description The nsei parameter specifies the Network Service Entity Identifier (NSEI) used by the {4040} PCUs over the Gb interface. Syntax Change command string {4040} chg_element nsei <value> <pcu_n> Display command string {4040} disp_element nsei <pcu_n> Values Value type Integer Valid range 0 to 65535 Default value none 68P02901W23-P 23 Feb 2004 5-549 GMR-01 . Operator actions The operator must lock all GBLs in the BSS before this element is changed. Sysgen mode cannot be left until the nsei parameter has been configured by the operator. There can be only one NSEI associated with each PCU. Type B (operator actions required) Supported by OMC-R GUI Yes Cell numbers required No Dependencies The GPRS feature must be unrestricted. it repeats up to the value specified by num_audit_retries. If an audit fails.num_audit_retries Chapter 5: CM database parameters 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. This parameter provides a means of differentiating between glitches on a link and a complete link failure. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required No Dependencies None Syntax Change command string chg_element num_audit_retries <value> <location> Display command string disp_element num_audit_retries <location> Values Value type Integer (represents the number of repeat audits) Valid range 0 to 5 Default value 1 5-550 GMR-01 68P02901W23-P 23 Feb 2004 . before a particular call is cleared by the auditing process. Technical Description BSS Command Reference num_emerg_access 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. Type A (no operator actions) Supported by OMC-R GUI No Cell numbers required Yes Dependencies None Syntax Change command string stat_mode num_emerg_access <value> <cell_desc> Display command strings disp_stat_prop num_emerg_access <cell_desc> Values Value type Boolean Valid range off or on Default value 68P02901W23-P 23 Feb 2004 off Disabled on Enabled off 5-551 GMR-01 . num_emerg_rejected Chapter 5: CM database parameters 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. Type A (no operator actions) Supported by OMC-R GUI No Cell numbers required Yes Dependencies None Syntax Change command string stat_mode num_emerg_rejected <value> <cell_desc> Display command strings disp_stat_prop num_emerg_rejected <cell_desc> Values Value type Boolean Valid range off or on Default value off Disabled on Enabled off 5-552 GMR-01 68P02901W23-P 23 Feb 2004 . An index value of 0 must be used for this element. Technical Description BSS Command Reference num_emerg_tch_kill 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. Type A (no operator actions) Supported by OMC-R GUI No Cell numbers required Yes Dependencies None Syntax Change command string stat_mode num_emerg_tch_kill <value> <cell_desc> Display command strings disp_stat_prop num_emerg_tch_kill <cell_desc> Values Value type Boolean Valid range off or on Default value 68P02901W23-P 23 Feb 2004 off Disabled on Enabled off 5-553 GMR-01 . An index value of 0 must be used for this element. num_emerg_term_sdcch Chapter 5: CM database parameters 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. An index value of 0 must be used for this element. Type A (no operator actions) Supported by OMC-R GUI No Cell numbers required Yes Dependencies None Syntax Change command string stat_prop num_emerg_term_sdcch <value> <cell_desc> Display command string disp_stat_prop num_emerg_term_sdcch <cell_desc> Values Value type Boolean Valid range off or on Default value off Disabled on Enabled off 5-554 GMR-01 68P02901W23-P 23 Feb 2004 . BSS software processes using this parameter are not notified when the change is made. Type A (no operator actions) Supported by OMC-R GUI No Cell numbers required Yes Dependencies The GPRS feature must be unrestricted.Technical Description BSS Command Reference num_gbl_dl_thrput_samples 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 Change command string chg_element gbl_dl_thrput_samples <value> <location> <cell_desc> Display command string disp_element gbl_dl_thrput_samples <location> <cell_desc> Values Value type Integer (number of samples) Valid range 1 to 10 Default value 10 68P02901W23-P 23 Feb 2004 5-555 GMR-01 . Type A (no operator actions) Supported by OMC-R GUI No Cell numbers required Yes Dependencies The GPRS feature must be unrestricted. BSS software processes using this parameter are not notified when the change is made.num_gbl_ul_thrput_samples Chapter 5: CM database parameters 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 Change command string chg_element gbl_ul_thrput_samples <value> <location> <cell_desc> Display command string disp_element gbl_ul_thrput_samples <location> <cell_desc> Values Value type Integer (number of samples) Valid range 1 to 10 Default value 10 5-556 GMR-01 68P02901W23-P 23 Feb 2004 . Technical Description BSS Command Reference number_of_preferred_cells 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. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required Yes Dependencies None Syntax Add/Change command strings add_cell <gsm_cell_id> <location> chg_element number_of_preferred_cells <value> <location> <cell_desc> chg_cell_element number_of_preferred_cells <value> <cell_desc> Display command strings disp_cell <cell_desc> ["full"] disp_element number_of_preferred_cells <location> <cell_desc> Values Value type Integer (represents preferred cells) Valid range 1 to 16 Default value 16 68P02901W23-P 23 Feb 2004 5-557 GMR-01 . The preferred list of target cells is a mandatory BSS field. The number of preferred cells is given in order of predicted best performance. 1 This is a Motorola defined parameter.5.3.08 .number_of_preferred_cells Chapter 5: CM database parameters References GSM specification 8.1.1. 5-558 GMR-01 68P02901W23-P 23 Feb 2004 . Syntax Add/Change command strings add_cell <gsm_cell_id> <location> chg_element number_sdcchs_preferred <value> <location> <cell_desc> chg_cell_element number_sdcchs_preferred <value> <cell_desc> Display command strings disp_cell <cell_desc> ["full"] disp_element number_sdcchs_preferred <location> <cell_desc> 68P02901W23-P 23 Feb 2004 5-559 GMR-01 . This value must be less than or equal to the max_number_of_sdcchs. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required Yes Dependencies This valid range for this parameter depends on ccch_conf. 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.Technical Description BSS Command Reference number_sdcchs_preferred 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. 4 This is a Motorola defined parameter. .. 12. 20. 24.... 5-560 GMR-01 68P02901W23-P 23 Feb 2004 .number_sdcchs_preferred Chapter 5: CM database parameters Values Value type Integer (SDCCHs) Valid range 4 to 44 If ccch_conf = 1.. 8 if ccch_conf is not equal to 1 References GSM specification 5. the values must be in multiples of 8 with an offset of 0 (such as 8. Default value 4 if ccch_conf = 1.44) 8 to 48 If ccch_conf = 0. the values must be in multiples of 8 with an offset of 4 (such as 4.6.02 . 16..48). communication with the BSS-based SMLC is impossible.Technical Description BSS Command Reference opc opc Description The opc parameter specifies the Originating Point Code (OPC). the system issues a warning: COMMAND ACCEPTED: WARNING: When opc equals dpc. the system issues a warning: COMMAND ACCEPTED: WARNING: When lb_int_dpc is equal to the opc. Syntax Change command string chg_element opc <value> 0 Display command string disp_element opc 0 68P02901W23-P 23 Feb 2004 5-561 GMR-01 . If the opc parameter is set to equal the dpc. communication with MSC is impossible. but not equal to lb_int_dpc. the system issues a warning: COMMAND ACCEPTED: WARNING: dpc and lb_int_dpc should not be equal to opc. If the opc parameter is set to equal the lb_int_dpc and equal to dpc. and lcs_mode is 2. Type A (no operator actions) Supported by OMC-R GUI Yes Cell description required No Dependencies The range of opc depends on the values for the "ss7_mode" on page 5-741. This parameter only applies to the BSC. but not equal to dpc. If the opc parameter is set to equal the lb_int_dpc and lcs_mode is 2. The values for the OPC are stored as a 14-bit binary code for non-ASNI and 24-bit binary code for ASNI. 708 This is a Motorola defined parameter.opc Chapter 5: CM database parameters 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. 5-562 GMR-01 68P02901W23-P 23 Feb 2004 . The Multiple Encryption feature must be unrestricted. Type A (no operator actions) Supported by OMC-R GUI Yes Cell description required No Dependencies This parameter applies only to the BSC or RXCDR. 5-563 GMR-01 .Technical Description BSS Command Reference option_alg_a5_1 option_alg_a5_1 Description The option_alg_a5_1 parameter enables or disables the encryption algorithm A5/1.08 This is a Motorola defined parameter. Syntax Change command string chg_element option_alg_a5_1 <value> 0 Display command string disp_element option_alg_a5_1 0 Values Value type Boolean Valid range 0 or 1 Default value 0 Disabled 1 Enabled 0 References GSM specification 68P02901W23-P 23 Feb 2004 8. 08 This is a Motorola defined parameter. Syntax Change command string chg_element option_alg_a5_2 <value> 0 Display command string disp_element option_alg_a5_2 0 Values Value type Boolean Valid range 0 or 1 Default value 0 Disabled 1 Enabled 0 References GSM specification 8. The Multiple Encryption feature must be unrestricted. 5-564 GMR-01 68P02901W23-P 23 Feb 2004 .option_alg_a5_2 Chapter 5: CM database parameters option_alg_a5_2 Description The option_alg_a5_2 parameter enables or disables the encryption algorithm A5/2. Type A (no operator actions) Supported by OMC-R GUI Yes Cell description required No Dependencies This parameter only applies to the BSC or RXCDR. The Multiple Encryption feature must be unrestricted.08 This is a Motorola defined parameter.Technical Description BSS Command Reference option_alg_a5_3 option_alg_a5_3 Description The option_alg_a5_3 parameter enables or disables the encryption algorithm A5/3. Syntax Add/Change command string chg_element option_alg_a5_3 <value> 0 Display command string disp_element option_alg_a5_3 0 Values Value type Boolean Valid range 0 or 1 Default value 0 Disabled 1 Enabled 0 References GSM specification 68P02901W23-P 23 Feb 2004 8. 5-565 GMR-01 . Type A (no operator actions) Supported by OMC-R GUI Yes Cell description required No Dependencies This parameter only applies to the BSC or the RXCDR. option_alg_a5_4 Chapter 5: CM database parameters option_alg_a5_4 Description The option_alg_a5_4 parameter enables or disables the encryption algorithm A5/4. 5-566 GMR-01 68P02901W23-P 23 Feb 2004 .08 This is a Motorola defined parameter. Syntax Add/Change command string chg_element option_alg_a5_4 <value> 0 Display command string disp_element option_alg_a5_4 0 Values Value type Boolean Valid range 0 or 1 Default value 0 Disabled 1 Enabled 0 References GSM specification 8. Type A (no operator actions) Supported by OMC-R GUI Yes Cell description required No Dependencies This parameter only applies to the BSC or the RXCDR. The Multiple Encryption feature must be unrestricted. Syntax Add/Change command string chg_element option_alg_a5_5 <value> 0 Display command string disp_element option_alg_a5_5 0 Values Value type Boolean Valid range 0 or 1 Default value 0 Disabled 1 Enabled 0 References GSM specification 68P02901W23-P 23 Feb 2004 8.Technical Description BSS Command Reference option_alg_a5_5 option_alg_a5_5 Description The option_alg_a5_5 parameter enables or disables the encryption algorithm A5/5. The Multiple Encryption feature must be unrestricted. 5-567 GMR-01 . Type A (no operator actions) Supported by OMC-R GUI Yes Cell description required No Dependencies This parameter only applies to the BSC or the RXCDR.08 This is a Motorola defined parameter. Type A (no operator actions) Supported by OMC-R GUI Yes Cell description required No Dependencies This parameter only applies to the BSC or the RXCDR.option_alg_a5_6 Chapter 5: CM database parameters option_alg_a5_6 Description The option_alg_a5_6 parameter enables or disables the encryption algorithm A5/6.08 This is a Motorola defined parameter. 5-568 GMR-01 68P02901W23-P 23 Feb 2004 . Syntax Add/Change command string chg_element option_alg_a5_6 <value> 0 Display command string disp_element option_alg_a5_6 0 Values Value type Boolean Valid range 0 or 1 Default value 0 Disabled 1 Enabled 0 References GSM specification 8. The Multiple Encryption feature must be unrestricted. The Multiple Encryption feature must be unrestricted. Type A (no operator actions) Supported by OMC-R GUI Yes Cell description required No Dependencies This parameter only applies to the BSC or the RXCDR.Technical Description BSS Command Reference option_alg_a5_7 option_alg_a5_7 Description The option_alg_a5_7 parameter enables or disables the encryption algorithm A5/7. Syntax Add/Change command string chg_element option_alg_a5_7 <value> 0 Display command string disp_element option_alg_a5_7 0 Values Value type Boolean Valid range 0 or 1 Default value 0 Disabled 1 Enabled 0 References GSM specification 68P02901W23-P 23 Feb 2004 8.08 This is a Motorola defined parameter. 5-569 GMR-01 . Syntax Change command string chg_element option_emergency_preempt <value> 0 Display command string disp_element option_emergency_preempt 0 Values Value type Boolean Valid range 0 or 1 Default value 0 Disabled 1 Enabled 0 5-570 GMR-01 68P02901W23-P 23 Feb 2004 . An emergency call is identified in the RACH burst from the MS. The emergency call preemption feature enables the BSS to provide access for emergency calls regardless of other traffic currently on the BSS.option_emergency_preempt Chapter 5: CM database parameters option_emergency_preempt Description The option_emergency_preempt parameter enables or disables the emergency call preemption option. Type A (no operator actions) Supported by OMC-R GUI Yes Cell description required No Dependencies This parameter applies only to the BSC or RXCDR. 08. Service Accessibility.5. functions related to MS in idle Mode. version 4.8.0 [3] 04.22.0[7] This is a Motorola defined parameter. version 4. Mobile Radio Interface Layer 3 Specification.0[1] 03.11. 5-571 GMR-01 . version 4.5.Technical Description BSS Command Reference option_emergency_preempt References GSM specification 68P02901W23-P 23 Feb 2004 02. 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. Syntax Change command strings chg_element outer_zone_usage_level <value> <location> <cell_desc> chg_cell_element outer_zone_usage_level <value> <cell_desc> Display command strings disp_cell <cell_desc> <"full"> disp_element outer_zone_usage_level <location> <cell_desc> Values Value type Integer (indicating the percentage of outer zone TCH usage) Valid range 0 to 100 Default value 0 5-572 GMR-01 68P02901W23-P 23 Feb 2004 . If this parameter is set to 0. If this parameter is set to any other value.outer_zone_usage_level Chapter 5: CM database parameters outer_zone_usage_level Description The outer_zone_usage_level parameter specifies the percentage level of outer cell traffic channel (TCH) usage. channels in the inner zone is used whenever an MS is qualified to use those resources. Type A (no operator actions) Supported by OMC-R GUI Yes Cell description required Yes Dependencies The Concentric Cells feature must be enabled. 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 only applies to intra-BSS inter-cell handovers. This parameter also determines which method of audio connection is used for the BTS concentration resource optimization for the handovers feature. Call processing sends the pre-transfer request to the switch manager.Technical Description BSS Command Reference override_intra_bss_pre_transfer 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. Syntax Change command string chg_element override_intra_bss_pre_transfer <value> 0 Display command string disp_element override_intra_bss_pre_transfer 0 Values Value type Boolean Valid range 0 or 1 Default value 68P02901W23-P 23 Feb 2004 0 Send pre-transfer request to SM 1 Do not send pre-transfer request to SM 0 5-573 GMR-01 . Type A (no operator actions) Supported by OMC-R GUI Yes Cell description required No Dependencies This parameter applies only to the BSC or RXCDR. 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. 5-574 GMR-01 68P02901W23-P 23 Feb 2004 .override_speech_version Chapter 5: CM database parameters override_speech_version Description {4322}This parameter and all references have been deleted for GSR7. 0 5-575 GMR-01 . 0 Disabled – A neighbour equipped as above is unequipped. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required Yes Dependencies The Dual Band Cells feature must be unrestricted. This autocreated neighbour can not be deleted by the user and it can only be deleted by changing this parameter back to 0.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. Syntax Change command strings chg_element pbgt_mode <value> <location> <cell_desc> chg_cell_element pbgt_mode <value> <cell_desc> Display command strings disp_cell <cell_desc> <"full"> disp_element pbgt_mode <location> <cell_desc> Values Value type Integer Valid range 0 or 1 Default value 68P02901W23-P 23 Feb 2004 1 Enabled – A new neighbour is auto-equipped with BCCH frequency set to that of the serving cell. Changing this parameter to 1 adds this cell to its own neighbour list. gprs_enabled must be set to 0.disable pccch_enabled must be set to 1 . The BSS must have configured the BCCH carrier of the cell to non-hopping. Operator actions In order to enable PBCCH/PCCCH for a cell. ts_sharing must be set to 0 at the same cell site. gprs_enabled must be set to 0 . Type B (Operator actions required) Supported by OMC-R GUI Yes Cell numbers required Yes Dependencies The PBCCH/PCCCH optional feature must be unrestricted.enable gprs_enabled must be set to 1 .enable. The cell must be a normal range cell. Syntax Change command string chg_element pccch_enabled <value> <location> <cell_desc> chg_cell_element pccch_enabled <value> <cell-desc> chg_cell_element <location> pccch_enabled <value> all Display command string disp_cell <cell_desc> “full" disp_element pccch_enabled <location> <cell-desc> disp_element pccch_enabled <location> all 5-576 GMR-01 68P02901W23-P 23 Feb 2004 . This feature supports GPRS Network Operation Modes I and III for normal range cell.pccch_enabled Chapter 5: CM database parameters pccch_enabled {3723} Description The pccch_enabled parameter specifies whether or not the PBCCH/PCCCH optional feature is unrestricted at a cell. Technical Description BSS Command Reference pccch_enabled Values Value type Integer Valid range 0 or 1 Default value 68P02901W23-P 23 Feb 2004 0 Disabled 1 Enabled 0 5-577 GMR-01 . Syntax Display command string disp_options Values Value type Boolean Valid range 0 or 1 Default value 0 Restricted 1 Unrestricted None 5-578 GMR-01 68P02901W23-P 23 Feb 2004 . Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required No Dependencies The PBCCH/PCCCH features must be unrestricted to provide their associated functionality.pccchOpt Chapter 5: CM database parameters pccchOpt {3723} 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. If PCR is enabled. • ss7_l3_t2 > 1400 milliseconds. This method is used when transferring messages between the MSC and the BSC (via the A interface). Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required No Dependencies This parameter only applies to the BSC. You must reset the BSC when changing this parameter for the change to take effect. Syntax Change command string chg_element pcr_enable <value> 0 Display command string disp_element pcr_enable 0 Values Value type Boolean Valid range 0 or 1 Default value 68P02901W23-P 23 Feb 2004 0 Disabled 1 Enabled 0 5-579 GMR-01 .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. then: • ss7_l2_t7 > 800 milliseconds. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required No Dependencies This parameter only applies to the BSC. Syntax Change command string chg_element pcr_n1 <value> 0 Display command string disp_element pcr_n1 0 Values Value type Integer (message signal units) Valid range 32 to 127 Default value 127 5-580 GMR-01 68P02901W23-P 23 Feb 2004 .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. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required No Dependencies This parameter only applies to the BSC.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 Change command string chg_element pcr_n2 <value> 0 Display command string disp_element pcr_n2 0 Values Value type Integer (message octets) Valid range 950 to 3750 Default value 3750 68P02901W23-P 23 Feb 2004 5-581 GMR-01 . When only one PCU is equipped. six more parameters are then prompted to specify the mapping order. Syntax Change command string chg_element pcu_redundancy <value> bsc Display command string disp_element pcu_redundancy bsc Values Value type Boolean Valid range 0 PCU redundancy Off 1 PCU redundancy On Default value 1 5-582 GMR-01 68P02901W23-P 23 Feb 2004 . pcu_redundancy does not prompt for redundant PCU. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required No Dependencies This parameter applies only to the BSC (location = 0).pcu_redundancy Chapter 5: CM database parameters pcu_redundancy {4040} Description The pcu_redundancy parameter specifies whether the BSS supports PCU redundancy or not. If entered to support redundancy. 1 or 2 No redundancy <pcu_red_map_12> 0. If the prompts are not answered. including the current PCU itself. 1 or 2 No redundancy If the parameter pcu_redundancy value is set to 1 (True or On).Technical Description BSS Command Reference pcu_redundancy Prompts If the value is set to 1 (PCU redundancy On) the following prompts are displayed: Please Please Please Please Please Please specify specify specify specify specify specify first redundant for PCU 0: <pcu_red_map_01> second redundant for PCU 0: <pcu_red_map_02> first redundant for PCU 1: <pcu_red_map_11> second redundant for PCU 1: <pcu_red_map_12> first redundant for PCU 2: <pcu_red_map_21> second redundant for PCU 2: <pcu_red_map_22> The table below shows the possible entries and their meanings: Parameter Valid Input Default <pcu_red_map_01> 0. 1 or 2 No redundancy <pcu_red_map_11> 0. 1 or 2 No redundancy <pcu_red_map_21> 0. Example display An example of pcu_redundancy follows: disp_element pcu_redundancy bsc pcu_redundancy =TRUE PCU id -----0 1 2 68P02901W23-P 23 Feb 2004 1st redundant ------------1 2 NA 2nd redundant ------------NA NA NA 5-583 GMR-01 . 1 or 2 No redundancy <pcu_red_map_02> 0. 1 or 2 No redundancy <pcu_red_map_22> 0. redundancy can be set to any of the available PCUs. in answer to the prompts. default is no redundancy. percent_traf_cs Chapter 5: CM database parameters percent_traf_cs {4441} Description The percent_traf_cs parameter specifies the percentage of RSL Reserved for CS. Syntax Change command string chg_element percent_traf_cs <value> <location> Display command string disp_element percent_traf_cs <location> Values Value type Integer Valid range 0 to 90 Default value 55 5-584 GMR-01 68P02901W23-P 23 Feb 2004 . Type A (no operator actions) Supported by OMC-R GUI Yes Cell description required No Dependencies The GPRS feature must be unrestricted. Syntax Change command string chg_element persistence_level.Technical Description BSS Command Reference persistence_level persistence_level {3723} Description The persistence_level parameter specifies values for the access persistence level for each radio priority on a per cell basis.i <value> <cell_desc> Display command string disp_cell <cell_desc> “full" disp_element persistence_level.i <value> <location> <cell_desc> chg_cell_element persistence_level. This parameter is always attached with a radio priority (i) of 0 to 4. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required Yes Dependencies The PBCCH/PCCCH optional feature must be unrestricted.i <location> <cell_desc> 68P02901W23-P 23 Feb 2004 5-585 GMR-01 . persistence_level Chapter 5: CM database parameters Values Value type Integer Valid range 0 to 15 representing the access persistence level: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 persistence level 0 persistence level 1 persistence level 2 persistence level 3 persistence level 4 persistence level 5 persistence level 6 persistence level 7 persistence level 8 persistence level 9 persistence level 10 persistence level 11 persistence level 12 persistence level 13 persistence level 14 persistence level 16 Default value 4 5-586 GMR-01 68P02901W23-P 23 Feb 2004 . Phase locking means the GCLK board is synchronized with the clock of the MMS selected as determined by the mms_priority value. The mms_priority value is specified using the modify_value command. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required No Dependencies None Syntax Change command string chg_element phase_lock_gclk <value> <location> Display command string disp_element phase_lock_gclk <location> Values Value type Boolean Valid range 0 or 1 Default value 68P02901W23-P 23 Feb 2004 0 Disabled 1 Enabled 0 5-587 GMR-01 .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_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. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required No Dependencies None Syntax Change command string chg_element phase_lock_retry <value> <location> Display command string disp_element phase_lock_retry <location> Values Value type Integer (minutes) Valid range 0 to 255 Default value 0 Immediate phase_lock_retry 1 to 254 Time period for retrying phase locking 255 No phase_lock_retry 255 5-588 GMR-01 68P02901W23-P 23 Feb 2004 . 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.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. Syntax Change command string chg_element phase2_classmark_allowed <value> 0 Display command string disp_element phase2_classmark_allowed 0 Values Value type Integer Valid range 0 to 2 Default value 68P02901W23-P 23 Feb 2004 0 Formatted for Phase 1 1 Formatted for Phase 2 2 Formatted for Phase 2 with Multiband 0 5-589 GMR-01 . Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required No Dependencies This parameter applies only to BSC sites. This parameter does not apply to RXCDR sites. the command is rejected. This dependency is also checked during database verification (see the lcs_mode section). the BSS sends the messages in the GSM Phase 1 format. Syntax Change command string chg_element phase2_resource_ind_allowed <value> 0 Display command string disp_element phase2_resource_ind_allowed 0 Values Value type Integer Valid range 0 or 1 Default value 0 GSM Phase 1 format 1 GSM Phase 2 format 0 5-590 GMR-01 68P02901W23-P 23 Feb 2004 . the BSS sends the messages in the GSM Phase 2 format. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required No Dependencies This parameter applies only to BSC sites.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 1. This parameter does not apply to RXCDR sites. If this parameter is set to 0. If the threshold is increased during operation. any existing counts between the new and the old threshold does not clear an alarm until another successful call is made or the next successful GPRS time period occurs on the PIC.) This parameter can be set only at a BSC. Two successful calls are required to clear an alarm within this threshold. (pic_error_gen_thresh pic_error_clr_thresh) must be greater than or equal to 2.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). (One call might be too short for the Channel Coder Unit (CCU) to send an error indication. Type A (no operator actions) Supported by OMC-R GUI Yes Cell description required No Dependencies The ECERM feature must be unrestricted. Syntax Change command string chg_element pic_error_clr_thresh <value> 0 Display command string disp_element pic_error_clr_thresh 0 Values Value type Integer Valid range 0 to 253 Default value 0 68P02901W23-P 23 Feb 2004 5-591 GMR-01 . With the ECERM feature unrestricted. thus clearing the alarm prematurely. (pic_error_gen_thresh pic_error_clr_thresh) must be greater than or equal to 2. If the threshold is reduced during operation. Syntax Change command string chg_element pic_error_gen_thresh <value> 0 Display command string disp_element pic_error_gen_thresh 0 Values Value type Integer Valid range 2 to 255 Default value 6 5-592 GMR-01 68P02901W23-P 23 Feb 2004 .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). Type A (no operator actions) Supported by OMC-R GUI Yes Cell description required No Dependencies The ECERM feature must be unrestricted. This parameter can be set only at a BSC. With the ECERM feature unrestricted. any existing counts between the new and the old threshold will not cause an alarm. Type A (no operator actions) Supported by OMC-R GUI Yes Cell description required No Dependencies The ECERM feature must be unrestricted.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. This parameter can be set only at a BSC. Syntax Change command string chg_element pic_error_inc <value> 0 Display command string disp_element pic_error_inc 0 Values Value type Integer Valid range 0 PIC alarms not raised 1 to 255 PIC alarms raised 0 If ECERM feature is restricted 1 If ECERM feature is not restricted Default value 68P02901W23-P 23 Feb 2004 5-593 GMR-01 . For baseband hopping only. The pkt_radio_type parameter provides the ability to specify whether or not a BCCH RTF should be used for data. The pkt_radio_type parameter replaces and enhances the allow_32k_trau parameter which is no longer supported. A BSS software process is notified whenever the pkt_radio_type element value is changed. and 64 kbit/s. 5-594 GMR-01 68P02901W23-P 23 Feb 2004 . 32 kbit/s. 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. The mutually exclusive options are: none.pkt_radio_type Chapter 5: CM database parameters pkt_radio_type {23658} Description The pkt_radio_type parameter specifies the terrestrial resource capability of an RTF. EGPRS RTFs with associated RSLs can not be equipped. based on the pre-GSR7 parameters use_bcch_for_gprs (for the BCCH RTF) and allow_32k_trau. 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. 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. 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. pkt_radio_type. Table 5-35 provides a guideline to backport and backfill the EGPRS database element. 16 kbit/s. Sub-equipped EGPRS RTFs can not be equipped. The use_bcch_for_gprs parameter is not supported for EGPRS. then 32 kbit/s packet radio must be configured on the BCCH RTF.Technical Description BSS Command Reference Table 5-35 pkt_radio_type EGPRS backport and backfill guideline allow_32k_trau (original GSR7 element) pkt_radio_type for non-BCCH RTF (GSR7 EGPRS element) Meaning 0 0 . 2 CS1 to CS4 68P02901W23-P 23 Feb 2004 No packet radio possible on this RTF pkt_radio_type for BCCH RTF Coding schemes 0 0 if GPRS restricted. then 32 kbit/s packet radio must be configured on the BCCH RTF. 1 if GPRS unrestricted NA CS1 and CS2 5-595 GMR-01 .GPRS unrestricted and RTF in outer zone 16 kbit/s packet radio possible on this RTF CS1 and CS2 1 2 32 kbit/s packet radio possible on this RTF CS1 to CS4 NA 3 64 kbit/s packet radio possible on this RTF MCS1 to MCS9 and CS1 to CS4 Coding schemes 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. Table 5-36 pkt_radio_type translation Original GSR7 parameters Meaning GSR7 EGPRS parameter use_bcch_ for_gprs allow_32k _trau 0 don’t care 1 0 16 kbit/s packet radio possible on BCCH 1 1 If any 32K packet radio is configured in the cell. 2 CS1 to CS4 2 0 16 kbit/s packet radio possible on BCCH 1 CS1 and CS2 2 1 If any 32K packet radio is configured in the cell.If GPRS restricted or RTF in inner zone No packet radio possible on this RTF NA 1 . EGPRS-capable RTFs must be explicitly equipped. An RTF can not be equipped with 32 kbit/s packet radio type if the Coding Schemes 3 and 4 feature is restricted. An RTF can not be equipped with 64 kbit/s packet radio type if there is an associated RSL. An RTF can not be equipped when sharing a baseband hopping system with a non-EGPRS RTF. An RTF can not be equipped with 16 kbit/s packet radio type if the GPRS feature is restricted. 5-596 GMR-01 68P02901W23-P 23 Feb 2004 . and the Coding Schemes 3 and 4 (CS3/4) feature and GPRS feature also to be unrestricted. 64 kbit/s and 32 kbit/s can not be equipped at a BTS concentration site.pkt_radio_type Chapter 5: CM database parameters Type A (no operator actions) Supported by OMC-R GUI Yes Cell description required No 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. 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. An RTF can not be equipped with 64 kbit/s packet radio type if there are no Horizonmacro or Horizon II macro family of cabinets at the site. A sub-equipped RTF can not be equipped with 64 kbit/s or 32 kbit/s packet radio type. An RTF can not be equipped with 64 kbit/s packet radio type if extended range timeslots are configured. EGPRS RTFs can baseband hop only if the master cabinet at the site is a Horizon II. An RTF can not be equipped with a non-zero packet radio type in the inner zone of a cell. Display command string disp_equipment <location> rtf <dev_func_id1> <dev_func_id2> Values Value type Numeric Text Valid range 0 to 3 none. When changing the pkt_radio_type element value a warning is displayed indicating that the RTF will be cycled. 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) 0 If GPRS is restricted or the RTF is in the inner zone. 16k.Technical Description BSS Command Reference pkt_radio_type Syntax Change command strings Changing this parameter causes the RTF to go out of service and then back into service. Default value 68P02901W23-P 23 Feb 2004 5-597 GMR-01 . Use the modify_value command to change its value. 32k. equip <location> rtf modify_value <location> pkt_radio_type <value> rtf <dev_func_id1> <dev_func_id2> Use the equip command to initiate this functionality. 1 If GPRS is unrestricted and the RTF is in the outer zone. the INS pool GPROCs can be searched for a lower priority function. When a pool GPROC running a function goes OOS and there are no available pool GPROCs. This parameter can not be set at an RXCDR Syntax Change command string chg_element pool_gproc_preemption <value> 0 Display command string disp_element pool_gproc_preemption 0 Values Value type Integer Valid range 0 to 2 Default value 0 No replacement 1 Replacement based on function priority 2 Replacement based on function and intra-function priorities 1 5-598 GMR-01 68P02901W23-P 23 Feb 2004 . If such a function is found. it is “bumped" from its GPROC by the higher priority function.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. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required No Dependencies This parameter can be set only at a BSC. this indicates that there has been a poor initial assignment. If the RACH is too far away. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required No Dependencies None Syntax Change command string chg_element poor_initial_assignment <value> <location> Display command string disp_element poor_initial_assignment <location> Values Value type Boolean Valid range 0 or 1 Default value 68P02901W23-P 23 Feb 2004 0 Disabled 1 Enabled 0 5-599 GMR-01 .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). and therefore the RACH is discarded. 8. 4. Syntax Add/Change command strings add_cell <gsm_cell_id> <location> chg_element pow_inc_step_size_dl <value> <location> <cell_desc> chg_cell_element pow_inc_step_size_dl <value> <cell_desc> Display command strings disp_cell <cell_desc> ["full"] disp_element pow_inc_step_size_dl <location> <cell_desc> Values Value type Integer (dB) Valid range 2. 10. 12 or 14 Default value 2 5-600 GMR-01 68P02901W23-P 23 Feb 2004 . 6. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required Yes Dependencies This parameter must be greater than or equal to pow_red_step_size_dl.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. 2.Technical Description BSS Command Reference pow_inc_step_size_dl References GSM parameter POW_INC_STEP_SIZE_DL GSM specification 12.8.5.power Ctrl BTS .20 .pow Incr Step Size 68P02901W23-P 23 Feb 2004 5-601 GMR-01 .23 . Syntax Add/Change command strings add_cell <gsm_cell_id> <location> chg_element pow_inc_step_size_ul <value> <location> <cell_desc> chg_cell_element pow_inc_step_size_ul <value> <cell_desc> Display command strings disp_cell <cell_desc> ["full"] disp_element pow_inc_step_size_ul <location> <cell_desc> Values Value type Integer (dB) Valid range 2.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. 8. 4. 6 . Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required Yes Dependencies This parameter must be greater than or equal to pow_red_step_size_ul. 10 12 or 14 Default value 2 5-602 GMR-01 68P02901W23-P 23 Feb 2004 . 2.Technical Description BSS Command Reference pow_inc_step_size_ul References GSM parameter POW_INC_STEP_SIZE_UL GSM specification 12.20 .8.5.pow Incr Step Size 68P02901W23-P 23 Feb 2004 5-603 GMR-01 .23 .power Ctrl BTS . Syntax Add/Change command strings add_cell <gsm_cell_id> <location> chg_element pow_red_step_size_dl <value> <location> <cell_desc> chg_cell_element pow_red_step_size_dl <value> <cell_desc> Display command strings disp_cell <cell_desc> ["full"] disp_element pow_red_step_size_dl <location> <cell_desc> Values Value type Integer (dB) Valid range 2 or 4 Default value 2 5-604 GMR-01 68P02901W23-P 23 Feb 2004 . Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required Yes Dependencies This parameter must be less than or equal to pow_inc_step_size_dl.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. pow Red Step Size 68P02901W23-P 23 Feb 2004 5-605 GMR-01 .2.Technical Description BSS Command Reference pow_red_step_size_dl References GSM parameter POW_RED_STEP_SIZE_DL GSM specification 12.23 .5.8.power Ctrl BTS .20 . Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required Yes Dependencies Must be less than or equal to pow_inc_step_size_ul.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. Syntax Add/Change command strings add_cell <gsm_cell_id> <location> chg_element pow_red_step_size_ul <value> <location> <cell_desc> chg_cell_element pow_red_step_size_ul <value> <cell_desc> Display command strings disp_cell <cell_desc> ["full"] disp_element pow_red_step_size_ul <location> <cell_desc> Values Value type Integer (dB) Valid range 2 or 4 Default value 2 5-606 GMR-01 68P02901W23-P 23 Feb 2004 . 2.pow Red Step Size 68P02901W23-P 23 Feb 2004 5-607 GMR-01 .8.Technical Description BSS Command Reference pow_red_step_size_ul References GSM parameter POW_RED_STEP_SIZE_UL GSM specification 12.5.23 .20 .power Ctrl BTS . i <value> <location> <cell_desc> chg_cell_element prach_max_retran.prach_max_retran Chapter 5: CM database parameters prach_max_retran {3723} Description The prach_max_retran parameter specifies the maximum number of retransmissions allowed for each radio priority level (i) on a per cell basis.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 2 (4 retransmissions) Default value 5-608 GMR-01 68P02901W23-P 23 Feb 2004 . Syntax Change command string chg_element prach_max_retran. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required Yes Dependencies The PBCCH/PCCCH optional feature must be unrestricted. This parameter is always attached with a radio priority (i) of 0 to 4.i <value> <cell_desc> Display command string disp_cell <cell_desc> “full" disp_element prach_max_retran. Syntax Change command string chg_element prach_s <value> <location> <cell_desc> chg_cell_element prach_s <value> <cell_desc> Display command string disp_cell <cell_desc> “full" 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 68P02901W23-P 23 Feb 2004 5-609 GMR-01 . It is actually the number of slots between two successive Packet Channel request messages on a per cell basis. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required Yes Dependencies The PBCCH/PCCCH optional feature must be unrestricted.Technical Description BSS Command Reference prach_s prach_s {3723} Description The prach_s parameter specifies the minimum number of frames between two successive Packet Channel request messages. prach_s Chapter 5: CM database parameters Valid range 4 S = 41 5 S = 55 6 S = 76 7 S = 109 8 S = 163 9 S = 217 8 (S =163) 5-610 GMR-01 68P02901W23-P 23 Feb 2004 . Syntax Change command string chg_element prach_tx_int <value> <location> <cell_desc> chg_cell_element prach_tx_int <value> <cell_desc> Display command string disp_cell <cell_desc> “full" 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-P 23 Feb 2004 5-611 GMR-01 .Technical Description BSS Command Reference prach_tx_int prach_tx_int {3723} Description The prach_tx_int parameter specifies the number of frame slots to spread the transmission of the random access. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required Yes Dependencies The PBCCH/PCCCH optional feature must be unrestricted. 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 1 3 slots 9 12 slots 2 4 slots 10 14 slots 3 5 slots 11 16 slots 4 6 slots 12 20 slots 5 7 slots 13 25 slots 6 8 slots 14 32 slots 7 9 slots 15 50 slots 5-612 GMR-01 68P02901W23-P 23 Feb 2004 . Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required Yes Dependencies The GPRS feature must be unrestricted. 1 or 2 68P02901W23-P 23 Feb 2004 -1 No primary PCU 0 PCU_0 1 PCU_1 5-613 GMR-01 . the cell is assigned to the next redundant PCU (see pcu_redundancy parameter).Technical Description BSS Command Reference primary_pcu primary_pcu {4040} Description The primary_pcu parameter maps a cell to a specific PCU. If the primary PCU for a cell goes Out Of Service. If the primary PCU for a cell then returns In Service. Syntax Change command strings chg_cell_element <location> primary_pcu <value> <cell_desc> chg_element primary_pcu <value> location [<cell_desc>] Display command strings disp_element primary_pcu <location> <cell_desc> Values Value type Integer Valid range -1. the cell is remapped to the primary PCU. which then becomes the primary PCU. when more than one PCU is equipped at the BSC. 0. primary_pcu Chapter 5: CM database parameters 2 Default value PCU_2 -1 5-614 GMR-01 68P02901W23-P 23 Feb 2004 . Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required Yes Dependencies The Microcell feature must be unrestricted Syntax Change command strings chg_element prioritize_microcell <value> <location> <cell_desc> chg_cell_element prioritize_microcell <value> <cell_desc> Display command strings disp_cell <cell_desc> <"full"> disp_element prioritize_microcell <location> <cell_desc> Values Value type Integer Valid range 0 or 1 Default value 68P02901W23-P 23 Feb 2004 0 No impact on sorting 1 Impact on sorting 1 5-615 GMR-01 . If prioritize_microcell is set to 0.Technical Description BSS Command Reference prioritize_microcell 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 1. the Handovers (HO) level of the service cell does not impact sorting of the candidate list. the level of the serving cell impacts the sorting of the candidate list. Type A (no operator actions) Supported by OMC-R GUI Yes Cell description required Yes Dependencies The PBCCH/PCCCH optional feature must be unrestricted. Syntax Add/Change command strings chg_element priority_class <value> <location> <cell_desc> chg_cell_element priority_class <value> <cell_desc> Display command strings disp_cell <cell_desc> “full" disp_element priority_class <location> <cell_desc> Values Value type Integer Valid range 0 to 7 Default value 0 lowest priority 7 highest priority 0 5-616 GMR-01 68P02901W23-P 23 Feb 2004 .priority_class Chapter 5: CM database parameters priority_class {3723} Description The priority_class specifies the Hierarchical Cell Structure (HCS) for a cell. if this is not done.Technical Description BSS Command Reference protect_last_ts protect_last_ts Description The protect_last_ts parameter specifies the switchability of PDTCH when there is one (and only one) switchable PDTCH on a carrier and none are reserved. the last timeslot acts like a reserved timeslot. Queuing must be enabled and the priority sent from the MSC in the assignment request must be a value between 1 and 14. 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. 5-617 GMR-01 . Syntax Change command strings chg_element protect_last_ts <value> <location> <cell_desc> chg_cell_element protect_last_ts <value> <cell_desc> Display command strings disp_cell <cell_desc> <"full"> disp_element protect_last_ts <location> <cell_desc> Values Value type Integer Valid range 0 or 1 0 68P02901W23-P 23 Feb 2004 Last timeslot is not protected. there is no restriction and the last remaining switchable PDTCH can be taken for a voice call. When protect_last_ts is set to 0. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required Yes Dependencies The GPRS feature must be unrestricted. 0 5-618 GMR-01 68P02901W23-P 23 Feb 2004 .protect_last_ts Chapter 5: CM database parameters 1 Default value Last timeslot is protected. Type A (no operator actions) Supported by OMC-R GUI Yes Cell description required No Dependencies The GPRS feature must be unrestricted. any attempt to access the other Enhanced Scheduling parameters is rejected.Technical Description BSS Command Reference prp_capacity_opt prp_capacity_opt {4441} Description The prp_capacity_opt parameter indicates whether the Packet Resource Processor (PRP) capacity is unrestricted in the BSS software as delivered from Motorola. Syntax Display command string disp_options Values Value type Integer Valid range 0 or 1 Default value 68P02901W23-P 23 Feb 2004 0 Restricted 1 Unrestricted None 5-619 GMR-01 . If restricted. prr_aggr_factor Chapter 5: CM database parameters prr_aggr_factor {4441} Description The prr_aggr_factor parameter represents a coefficient for a linear function to dynamically allocate or deallocate reserved PRR blocks. Syntax Change command strings chg_element prr_aggr_factor <value> <location> Display command strings disp_element prr_aggr_factor <location> Values Value type Integer Valid range 0 to 4 Default value 3 5-620 GMR-01 68P02901W23-P 23 Feb 2004 . Type A (no operator actions) Supported by OMC-R GUI Yes Cell description required No Dependencies Modification of prr_aggr_factor has no effect for cells that have the pccch_enabled parameter enabled. The aggressive factor of 0 specifies that each cell in the BSS system has gprs_min_prr_blks number of PRR blocks allocated. ho_margin(n) > 0. a handover to cell “n" might be required if: PBGT(n) .Technical Description BSS Command Reference pwr_handover_allowed pwr_handover_allowed Description The pwr_handover_allowed parameter enables or disables the power budget assessment for handovers. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required Yes Dependencies None Syntax Add/Change command strings add_cell <gsm_cell_id> <location> chg_element pwr_handover_allowed <value> <location> <cell_desc> chg_cell_element pwr_handover_allowed <value> <cell_desc> Display command strings disp_cell <cell_desc> ["full"] disp_element pwr_handover_allowed <location> <cell_desc> Values Value type Boolean Valid range 0 or 1 Default value 68P02901W23-P 23 Feb 2004 0 Disabled 1 Enabled 1 5-621 GMR-01 . 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. When enabled. enable BSS Handover Control .enable Pwr Budget Handover 5-622 GMR-01 68P02901W23-P 23 Feb 2004 .20 .5.08 .18 .Appendix A.1f: PBGT(N) 12.8.2. 3.pwr_handover_allowed Chapter 5: CM database parameters References GSM parameter EN_PBGT_HO GSM specification 5. Technical Description BSS Command Reference pwrc pwrc Description The pwrc parameter specifies whether or not the Broadcast Control Channels (BCCH) measurement are included in the averaged value of hopping frequencies. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required Yes Dependencies None Syntax Add/Change command strings add_cell <gsm_cell_id> <location> chg_element pwrc <value> <location> <cell_desc> chg_cell_element pwrc <value> <cell_desc> Display command strings disp_cell <cell_desc> ["full"] disp_element pwrc <location> <cell_desc> Values Value type Boolean Valid range 0 or 1 Default value 68P02901W23-P 23 Feb 2004 0 Include BCCH measurement 1 Do not include BCCH measurement 1 5-623 GMR-01 . pwrc Chapter 5: CM database parameters References GSM parameter PWRC GSM specification GSM 4.08 5.08 5-624 GMR-01 68P02901W23-P 23 Feb 2004 . Technical Description BSS Command Reference queue_management_information queue_management_information Description The queue_management_information parameter specifies the maximum number of MSs that may wait in a queue for channel assignment. Type A (no operation action) Supported by OMC-R GUI Yes Cell numbers required Yes Dependencies The sum of (max_q_length_full_rate_channel + max_q_length_sdcch) must be less than or equal to queue_management_information. A value of 0 indicates that queuing is not allowed. Syntax Change command strings chg_element queue_management_information <value> <location> <cell_desc> chg_cell_element queue_management_information <value> <cell_desc> Display command strings disp_cell <cell_desc> <"full"> disp_element queue_management_information <location> <cell_desc> Values Value type Integer (representing the maximum number of MSs) Valid range 0 to 50 Default value 50 68P02901W23-P 23 Feb 2004 5-625 GMR-01 . queue_management_information Chapter 5: CM database parameters References Internal name EN_Q_ALLOWED This is a Motorola parameter. 5-626 GMR-01 68P02901W23-P 23 Feb 2004 . or whether the MS should always search. Syntax Change command strings chg_element qsearch_c_initial <value> <location> <cell_desc> chg_cell_element qsearch_c_initial <value> <cell_desc> Display command strings disp_cell <cell_desc> "full" disp_element qsearch_c_initial <location> <cell_desc> Values Value type Integer Valid range 0 The MS uses qsearch_i until qsearch_c is reached. The qsearch_c_initial parameter is configurable on a per cell basis.Technical Description BSS Command Reference qsearch_c_initial qsearch_c_initial Description The qsearch_c_initial parameter is broadcast on the BCCH using the SYSTEM INFORMATION TYPE 2 quarter message to control the multi-RAT MS 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. Type A (no operator actions) Supported by OMC-R GUI Yes Cell description required Yes Dependencies The BSS Inter-RAT feature must be unrestricted. 1 The MS always searches irrespective of qsearch_i (MS always measures the strength of the neighbour cells) Default value 68P02901W23-P 23 Feb 2004 0 5-627 GMR-01 . qsearch_i Chapter 5: CM database parameters qsearch_i Description The multi-RAT MS uses the qsearch_i parameter to decide when to start measurement of a UTRAN neighbour cell. The qsearch_i parameter is configurable on a per cell basis. 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. Type A (no operator actions) Supported by OMC-R GUI Yes Cell description required Yes Dependencies The BSS Inter-RAT feature must be unrestricted. Syntax Change command strings chg_element qsearch_i <value> <location> <cell_desc> chg_cell_element qsearch_i <value> <cell_desc> Display command strings disp_cell <cell_desc> <"full"> disp_element qsearch_i <location> <cell_desc> Values Value type Integer Valid range 0 to 15 Default value 15 5-628 GMR-01 68P02901W23-P 23 Feb 2004 . Syntax Add/Change command strings chg_element qsearch_p <value> <location> <cell_desc> chg_cell_element qsearch_p <value> <cell_desc> Display command strings disp_cell <cell_desc> “full" disp_element qsearch_p <location> <cell_desc> Values Value type Integer (1 step = 4 dBm) Valid range 0 to 7 for signal strengths below the threshold see Table 5-38 8 to 15 for signal strengths above the threshold see Table 5-39 Default value 68P02901W23-P 23 Feb 2004 0 5-629 GMR-01 .Technical Description BSS Command Reference qsearch_p qsearch_p {3723} Description The qsearch_p parameter specifies the threshold below which a multi-RAT MS searches for 3G cells. Type A (no operator actions) Supported by OMC-R GUI Yes Cell description required Yes Dependencies The PBCCH/PCCCH optional feature must be unrestricted. qsearch_p Chapter 5: CM database parameters Table 5-38 Table 5-39 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) 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) 5-630 GMR-01 68P02901W23-P 23 Feb 2004 . The ra_colour parameter applies only to GPRS cells. Operator actions This parameter can not be displayed until its value has been set. therefore.Technical Description BSS Command Reference ra_colour ra_colour Description The ra_colour parameter specifies the routing area colour used in System Information messages for a specific cell and. this parameter can be modified without a reset to a particular device or function. it can not be unset. If the local_maintenance flag is disabled. Syntax Change command strings chg_element ra_colour <value> <location> <cell_desc> chg_cell_element ra_colour <value> <cell_desc> Display command strings disp_cell <cell_desc> <"full"> disp_element ra_colour <location> <cell_desc> 68P02901W23-P 23 Feb 2004 5-631 GMR-01 . indicates that GPRS is supported in the cell. Type B (operator actions required) Supported by OMC-R GUI Yes Cell numbers required Yes Dependencies The GPRS feature must be unrestricted. BSS software processes using this parameter are not notified when the change is made. this parameter cannot be changed through the MMI. That is. Once the value of ra_colour has been set. ra_colour Chapter 5: CM database parameters Values Value type Integer (routing area colour for a cell) Valid range 0 to 7 Default value None 5-632 GMR-01 68P02901W23-P 23 Feb 2004 . Differences in received signal levels from 0 to 14 dB (in 2 dB increments) are used for cell reselection. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required Yes Dependencies The PBCCH/PCCCH optional feature must be unrestricted. Syntax Add/Change command strings chg_element ra_reselect_hysteresis <value> <location> <cell_desc> chg_cell_element ra_reselect_hysteresis <value> <cell_desc> Display command strings disp_cell <cell_desc> “full" 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 68P02901W23-P 23 Feb 2004 5-633 GMR-01 .Technical Description BSS Command Reference ra_reselect_hysteresis ra_reselect_hysteresis {3723} Description The ra_reselect_hysteresis parameter specifies the additional hysteresis that applies when selecting a cell in a new Routing Area (RA). ra_reselect_hysteresis Default value Chapter 5: CM database parameters 4 8 dB 5 10 dB 6 12 dB 7 14 dB None 5-634 GMR-01 68P02901W23-P 23 Feb 2004 . That is. Syntax Change command strings chg_element rac <value> <location> <cell_desc> chg_cell_element rac <value> <cell_desc> Display command strings disp_cell <cell_desc> <"full"> disp_element rac <location> <cell_desc> The RAC cannot be displayed if the value has not been previously configured or modified by the operator.Technical Description BSS Command Reference rac rac Description The rac parameter specifies the routing area code (RAC) which is part of the cell identifier for GPRS cells. it can not be unset. 68P02901W23-P 23 Feb 2004 5-635 GMR-01 . Type B (operator actions required) Supported by OMC-R GUI Yes Cell numbers required Yes Dependencies This parameter applies only to GPRS cells. Once this value has been set. this parameter can be modified without a reset to a particular device or function. The GPRS feature must be unrestricted. BSS software processes using this parameter are not notified when the change is made. Operator actions This parameter can not be displayed until value has been set. rac Chapter 5: CM database parameters Values Value type Integer (RAC for a cell) Valid range 0 to 255 Default value None 5-636 GMR-01 Null = unmodified 68P02901W23-P 23 Feb 2004 . rach_overload_threshold. Other parameters can affect flow control. ssm_normal_overload_threshold or tch_flow_control. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required Yes Dependencies This parameter must be less than or equal to ccch_load_period. Refer to ccch_load_period. Syntax Change command strings chg_element rach_load_period <value> <location> <cell_desc> chg_cell_element rach_load_period <value> <cell_desc> Display command strings disp_cell <cell_desc> <"full"> disp_element rach_load_period <location> <cell_desc> Values Value type Integer Valid range 1 to 1020 Default value 16 68P02901W23-P 23 Feb 2004 5-637 GMR-01 .Technical Description BSS Command Reference rach_load_period 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. ssm_normal_overload_threshold. 5-638 GMR-01 68P02901W23-P 23 Feb 2004 .rach_load_period Chapter 5: CM database parameters References Internal name RACH_MEAS_PERIOD This is a Motorola parameter. Refer to ccch_load_period. once the cell runs out of available traffic channels. The RACH load may be calculated in one of two ways based on the value of the rach_load_type parameter. the system will gradually prevent subscribers from entering the system as soon as the cell runs out of free traffic and standalone control channels. Let T_SD_CHANNEL be the number of available traffic and standalone control (SDCCH) channels. If the RACH load threshold is set to a value in the neighbourhood of T_SD_CHANNELS/MAX_RACH. an overload condition is signalled and an access class is barred at the cell where the overload is occurring. ssm_normal_overload_threshold.8% Other parameters can affect flow control. If the RACH load exceeds rach_load_threshold. This number is determined by the cell configuration. Let MAX_RACH be the number of possible RACH accesses per load period.18% C 3 16 20 2 No 08. In the case the RACH load threshold is set to a number higher than T_SD_CHANNELS/MAX_RACH. rach_load_period. ssm_normal_overload_threshold or tch_flow_control.Technical Description BSS Command Reference rach_load_threshold rach_load_threshold Description The rach_load_threshold parameter specifies the threshold for RACH load. an overload indication is sent to Call Processing which may result in an access class being barred. The number of correct RACH accesses can exceed the number of calls the cell can handle (T_SD_CHANNELS). MAX_RACH has a value of 204 for pure RACH (non-combined). 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. MSs will not be barred until the RACH load threshold is met.1% B 1 4 7 1 Yes 10. Type A (no operator actions) Supported by OMC-R GUI Yes 68P02901W23-P 23 Feb 2004 5-639 GMR-01 . In both cases the net effect is that calls are not completed. and 108 for combined RACH channels. RACH loading is expressed as the ratio of correct RACH accesses to the number of possible RACH accesses. Table 5-40 lists example cell configurations and their corresponding rach_load_threshold values. but in the mean time attempted calls will get rejected. If the calculated RACH load exceeds this threshold. then the units for this parameter are (# correct RACH access/# possible RACH accesses).rach_load_threshold Chapter 5: CM database parameters Cell numbers required Yes Dependencies If rach_load_type is 1. Syntax Change command strings chg_element rach_load_threshold <value> <location> <cell_desc> chg_cell_element rach_load_threshold <value> <cell_desc> Display command strings disp_cell <cell_desc> <"full"> disp_element rach_load_threshold <location> <cell_desc> Values Value type Integer Valid range 0 to 1000 Default value 1000 (Disables flow control) References Internal name RACH_BUSY_THRES This is a Motorola parameter. If rach_load_type is 0. 5-640 GMR-01 68P02901W23-P 23 Feb 2004 . then the units for this parameter are (# correct RACH access/# incorrect RACH accesses). Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required No Dependencies None Syntax Change command string chg_element rach_load_type <value> <location> Display command string disp_element rach_load_type <location> Values Value type Integer Valid range 0 or 1 Default value 68P02901W23-P 23 Feb 2004 0 Percentage of RACH opportunities used 1 Percentage of total RACHs which are incorrect (collisions) None 5-641 GMR-01 .Technical Description BSS Command Reference rach_load_type rach_load_type Description The rach_load_type parameter specifies the RACH loading calculation method. radio_link_timeout Chapter 5: CM database parameters 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. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required Yes Dependencies None Syntax Add/Change command strings add_cell <cell_desc> <location> chg_element radio_link_timeout <value> <location> <cell_desc> chg_cell_element radio_link_timeout <value> <cell_desc> Display command strings disp_cell <cell_desc> ["full"] 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 5-642 GMR-01 68P02901W23-P 23 Feb 2004 . 15 64 SACCH frames 4 References GSM parameter RADIO_LINK_TIMEOUT(MS) GSM specification 3..3 ..Technical Description BSS Command Reference Default value radio_link_timeout .5..2.2 to 3.10..fig.2. .5..2: radio link failure.16 68P02901W23-P 23 Feb 2004 5-643 GMR-01 . . table 10. ..08 ..5.22. mobile side and network side 4... ... 10. .. The rapid power down procedure will be initiated when the calculated value is greater than the value specified for the rpd_trigger parameter.rapid_pwr_down Chapter 5: CM database parameters rapid_pwr_down Description The rapid_pwr_down parameter enables or disables the rapid power down procedure. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required Yes Dependencies None Syntax Add/Change command strings add_cell <cell_desc> <location> chg_element rapid_pwr_down <value> <location> <cell_desc> chg_cell_element rapid_pwr_down <value> <cell_desc> Display command strings disp_cell <cell_desc> ["full"] disp_element rapid_pwr_down <location> <cell_desc> Values Value type Boolean Valid range 0 or 1 0 Disabled 5-644 GMR-01 68P02901W23-P 23 Feb 2004 . Detected MS power levels are averaged over the number of SACCH periods specified by the rpd_period parameter. 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. This average is compared to the value specified for the rpd_trigger value. Technical Description BSS Command Reference rapid_pwr_down 1 Default value 68P02901W23-P 23 Feb 2004 Enabled 0 5-645 GMR-01 . rci_error_clr_thresh) must be greater than or equal to 2.rci_error_clr_thresh Chapter 5: CM database parameters rci_error_clr_thresh Description The rci_error_clr_thresh parameter specifies the error count threshold (equal to or less than) for an alarm to be cleared for a Radio Channel Identifier (RCI). Type A (no operator actions) Supported by OMC-R GUI Yes Cell description required No Dependencies Two successful calls are required on a resource before an alarm can be cleared within this threshold. If the threshold is increased during operation. (rci_error_gen_thresh . any existing counts between the new and the old threshold does not clear an alarm until another successful call is made or the next successful time period occurs on the CIC. This parameter can be set only at a BSC. One successful call might be too short for the Channel Coder Unit (CCU) to send an error indication. thus clearing the alarm prematurely. Syntax Change command string chg_element rci_error_clr_thresh <value> 0 Display command string disp_element rci_error_clr_thresh 0 Values Value type Integer Valid range 0 to 253 Default value 0 5-646 GMR-01 68P02901W23-P 23 Feb 2004 . The new threshold takes effect only when the RCI error count changes. Type A (no operator actions) Supported by OMC-R GUI Yes Cell description required No Dependencies This parameter can be set only at a BSC.rci_error_clr_thresh) must be greater than or equal to 2. no immediate alarm occurs. If the threshold is changed during operation.Technical Description BSS Command Reference rci_error_gen_thresh rci_error_gen_thresh Description The rci_error_gen_thresh parameter specifies the error count threshold (equal to or greater than) for an alarm to be generated for a Radio Channel Identifier (RCI). (rci_error_gen_thresh . Syntax Change command string chg_element rci_error_gen_thresh <value> 0 Display command string disp_element rci_error_gen_thresh 0 Values Value type Integer Valid range 2 to 255 Default value 6 68P02901W23-P 23 Feb 2004 5-647 GMR-01 . Type A (no operator actions) Supported by OMC-R GUI Yes Cell description required No Dependencies The ECERM feature must be unrestricted. This parameter applies only to the BSC. Syntax Change command string chg_element rci_error_inc <value> 0 Display command string disp_element rci_error_inc 0 Values Value type Integer Valid range 0 RCI alarms not raised 1 to 255 RCI alarms raised 0 If ECERM feature is restricted 1 If ECERM feature is not restricted Default value 5-648 GMR-01 68P02901W23-P 23 Feb 2004 .rci_error_inc Chapter 5: CM database parameters rci_error_inc Description The rci_error_inc parameter specifies the error count increment when the Enhanced Circuit Error Rate Monitor (ECERM) feature is in use for Radio Channel Identifiers (RCIs) on a per BSC basis. 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.Technical Description BSS Command Reference red_loss_daily red_loss_daily Description The red_loss_daily parameter specifies the synchronization loss. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required No Dependencies None Syntax Change command string chg_element red_loss_daily <value> <location> Display command string disp_element red_loss_daily <location> Values Value type Integer (number of alarms) Valid range 0 to 65535 Default value 16 68P02901W23-P 23 Feb 2004 5-649 GMR-01 . hourly alarm level count on a T1 link. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required No Dependencies None Syntax Change command string chg_element red_loss_hourly <value> <location> Display command string disp_element red_loss_hourly <location> Values Value type Integer (number of alarms) Valid range 0 to 65535 Default value 20 5-650 GMR-01 68P02901W23-P 23 Feb 2004 .red_loss_hourly Chapter 5: CM database parameters red_loss_hourly Description The red_loss_hourly parameter specifies the synchronization loss. An alarm generates if the synchronization loss meets or exceeds the threshold in a given 60 minute period. 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. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required No Dependencies None Syntax Change command string chg_element red_loss_oos <value> <location> Display command string disp_element red_loss_oos <location> Values Value type Integer (number of alarms) Valid range 0 to 65535 Default value 511 68P02901W23-P 23 Feb 2004 5-651 GMR-01 . .. the T1 circuit is brought back in service. 6000 600 seconds . Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required No Dependencies None Syntax Change command string chg_element red_loss_restore <value> <location> Display command string disp_element red_loss_restore <location> Values Valid type Integer (1 step = 100 milliseconds) Valid range 0 to 65535 Default value 0 0 seconds 0 milliseconds 1 0. If a synchronization loss error does not occur within this period of time. 65535 6553.5 seconds 600000 milliseconds 6553500 milliseconds 6000 5-652 GMR-01 68P02901W23-P 23 Feb 2004 . The synchronization loss is controlled by the value assigned to the red_loss_oos parameter. ...red_loss_restore Chapter 5: CM database parameters red_loss_restore Description The red_loss_restore parameter specifies the synchronization loss.1 seconds 100 milliseconds 2 0... restorable time limit for a T1 circuit.2 seconds 200 milliseconds ... . Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required No Dependencies None Syntax Change command string chg_element red_time_oos <value> <location> Display command string disp_element red_time_oos <location> Values Valid type Integer (1 step = 100 milliseconds) Valid range 0 to 65535 Default value 68P02901W23-P 23 Feb 2004 0 0 seconds 0 milliseconds 1 0..2 seconds 200 milliseconds .5 seconds . the T1 circuit is taken Out Of Service (OOS).... 65535 6553....1 seconds 100 milliseconds 2 0. .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.5 seconds 2500 milliseconds 6553500 milliseconds 25 5-653 GMR-01 .. If synchronization is lost for this period of time. . 25 2. 1 seconds 100 milliseconds 2 0.. ..2 seconds 200 milliseconds . 65535 6553.. the T1 link returns to service.5 seconds 60000 milliseconds 6553500 milliseconds 600 5-654 GMR-01 68P02901W23-P 23 Feb 2004 .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.... ... Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required No Dependencies None Syntax Change command string chg_element red_time_restore <value> <location> Display command string disp_element red_time_restore <location> Values Valid type Integer (1 step = 100 milliseconds) Valid range 0 to 65535 Default value 0 0 seconds 0 milliseconds 1 0. 600 60 seconds . If synchronization loss does not occur within this period of time. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required Yes Dependencies None Syntax Add/Change command strings add_cell <cell_desc> <location> chg_element reestablish_allowed <value> <location> <cell_desc> chg_cell_element reestablish_allowed <value> <cell_desc> Display command strings disp_cell <cell_desc> ["full"] disp_element reestablish_allowed <location> <cell_desc> Values Value type Boolean Valid range 0 or 1 0 68P02901W23-P 23 Feb 2004 Enabled 5-655 GMR-01 . the MS executes the GSM call reestablishment algorithm to determine which cell to use for the attempt to reestablish the call.Technical Description BSS Command Reference reestablish_allowed reestablish_allowed Description The reestablish_allowed parameter enables or disables call establishment. a radio link failure occurs. When enabled. 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). 2.30: cell description .2.2: radio link failure.2 to 3.5.5.reestablish_allowed Chapter 5: CM database parameters 1 Default value Disabled 0 References GSM parameter RE GSM specification 5.6. fig.call reestablishment allowed 5-656 GMR-01 68P02901W23-P 23 Feb 2004 .3.2.20 .2: Call reestablishment algorithm.5. mobile side and network side. 4.08 . 10.7.17.10. and 12.7.5.8.08 . 408 .36. table 10. <bin_num> <alg_num> <cell_desc> Display command string disp_cell <cell_desc> <"full"> disp_element rel_tim_adv. A bin_num must be specified with this command to indicate the location of the parameters to be modified. Type B (operator actions required) Supported by OMC-R GUI Yes Cell numbers required Yes Dependencies When alg_num is set to 255. A alg_num must be also specified to indicate the averaging algorithm as unweighted (0).<bin_num> <location> <cell_desc> 68P02901W23-P 23 Feb 2004 5-657 GMR-01 . a bin_num must be specified to identify the location of the parameters to be displayed. bin_num can not be set equal to decision_1_tim_adv_av_alg Operator actions Respond to the prompts after entering this command.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. the bin is considered to contain invalid data. After entering the chg_cell_element command for this parameter. Only 0 or 1 may be specified for the bin_num. If a value of 255 is entered for the alg_num. Syntax Change command string chg_cell_element rel_tim_adv. the following prompts are displayed and values must be entered: Enter hreqave: Enter hreqt: When entering disp_element rel_tim_adv. 5-658 GMR-01 68P02901W23-P 23 Feb 2004 .08 This is a Motorola defined parameter.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 GSM specification 5. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required No Dependencies remote_loss_daily should be always less than remote_loss_hourly. Syntax Change command string chg_element remote_loss_daily <value> <location> Display command string disp_element remote_loss_daily <location> Values Value type Integer (represents the number of alarms) Valid range 0 to 65535 Default value 16 68P02901W23-P 23 Feb 2004 5-659 GMR-01 . An alarm generates if this threshold is met or exceeded during a 24 hour period.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. 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. Syntax Change command string chg_element remote_loss_hourly <value> <location> Display command string disp_element remote_loss_hourly <location> Values Value type Integer (represents the number of alarms) Valid range 0 to 65535 Default value 20 5-660 GMR-01 68P02901W23-P 23 Feb 2004 . An alarm generates if this threshold is met or exceeded during a 60 minute period. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required No Dependencies remote_loss_daily should be always less than remote_loss_hourly. 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. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required No Dependencies None Syntax Change command string chg_element remote_loss_oos <value> <location> Display command string disp_element remote_loss_oos <location> Values Value type Integer (represents the number of alarms) Valid range 0 to 65535 Default value 511 68P02901W23-P 23 Feb 2004 5-661 GMR-01 . the 2 Mbit/s circuit is taken OOS. 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.. 600 60 seconds .5 seconds 60000 milliseconds 6553500 milliseconds 600 5-662 GMR-01 68P02901W23-P 23 Feb 2004 .. ... ..2 seconds 200 milliseconds . Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required No Dependencies None Syntax Change command string chg_element remote_loss_restore <value> <location> Display command string disp_element remote_loss_restore <location> Values Valid type Integer (1 step = 100 milliseconds) Valid range 0 to 65535 Default value 0 0 seconds 0 milliseconds 1 0. If no remote alarm indication errors are detected during this wait time. the 2 Mbit/s circuit returns to service.1 seconds 100 milliseconds 2 0.. 65535 6553... .2 seconds 200 milliseconds ..5 seconds .. 25 2. 65535 6553. . If a remote alarm exists for this amount of time... Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required No Dependencies None Syntax Change command string chg_element remote_time_oos <value> <location> Display command string disp_element remote_time_oos <location> Values Valid type Integer (1 step = 100 milliseconds) Valid range 0 to 65535 Default value 68P02901W23-P 23 Feb 2004 0 0 seconds 0 milliseconds 1 0.1 seconds 100 milliseconds 2 0..Technical Description BSS Command Reference remote_time_oos remote_time_oos Description The remote_time_oos parameter specifies the remote alarm time period. the 2 Mbit/s circuit is taken Out Of Service (OOS)... .5 seconds 2500 milliseconds 6553500 milliseconds 25 5-663 GMR-01 . remote_time_restore Chapter 5: CM database parameters remote_time_restore Description The remote_time_restore parameter sets the remote alarm restorable time.5 seconds 60000 milliseconds 6553500 milliseconds 600 5-664 GMR-01 68P02901W23-P 23 Feb 2004 . .1 seconds 100 milliseconds 2 0. 65535 6553.2 seconds 200 milliseconds ...... Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required No Dependencies None Syntax Change command string chg_element remote_time_restore <value> <location> Display command string disp_element remote_time_restore <location> Values Valid type Integer (1 step = 100 milliseconds) Valid range 0 to 65535 Default value 0 0 seconds 0 milliseconds 1 0. .. If the remote alarm ceases for this period of time... 600 60 seconds . the 2 Mbit/s circuit returns to service. That is. 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. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required Yes Dependencies Must be less than report_resource_tch_f_low_water_mark Syntax Add/Change command strings add_cell <cell_desc> <location> chg_element report_resource_tch_f_high_water_mark <value> <location> <cell_desc> chg_cell_element report_resource_tch_f_high_water_mark <value> <cell_desc> Display command strings disp_cell <cell_desc> ["full"] disp_element report_resource_tch_f_high_water_mark <location> <cell_desc> Values Value type Integer (represents the number of TCHs) Valid range 0 to 254 Default value 2 68P02901W23-P 23 Feb 2004 5-665 GMR-01 .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. the Resource Request message received from the MSC is indicating a spontaneous mode. 2.report_resource_tch_f_high_water_mark Chapter 5: CM database parameters References GSM specification 8.08 . 5-666 GMR-01 68P02901W23-P 23 Feb 2004 .4: reported message format This is a Motorola parameter.3.2. That is. the internal resource indication timer stops (if it is running). Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required Yes Dependencies Must be greater than report_resource_tch_f_high_water_mark Syntax Add/Change command strings add_cell <cell_desc> <location> chg_element report_resource_tch_f_low_water_mark <value> <location> <cell_desc> chg_cell_element report_resource_tch_f_low_water_mark <value> <cell_desc> Display command strings disp_cell <cell_desc> ["full"] disp_element report_resource_tch_f_low_water_mark <location> <cell_desc> Values Value type Integer (number of TCHs) Valid range 1 to 255 Default value 12 68P02901W23-P 23 Feb 2004 5-667 GMR-01 .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. the Resource Request message received from the MSC is indicating a spontaneous mode. When the number of available (idle) full rate TCHs rises above this threshold. 5-668 GMR-01 68P02901W23-P 23 Feb 2004 .2.3.2.08 .4: reported message format This is a Motorola parameter.report_resource_tch_f_low_water_mark Chapter 5: CM database parameters References GSM specification 8. 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. The value of the res_gprs_pdchs parameter cannot be higher than the total number of timeslots available in the cell. The equip RTF parameter with the same name is now obsolete. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required Yes Dependencies The GPRS feature must be unrestricted. and cannot be higher than the total number of timeslots in the cell.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. Syntax Change command strings chg_element res_gprs_pdchs <value> <location> <cell_desc> chg_cell_element res_gprs_pdchs <value> <cell_desc> Display command strings disp_cell <cell_desc> <"full"> disp_element res_gprs_pdchs <location> <cell_desc> 68P02901W23-P 23 Feb 2004 5-669 GMR-01 . 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-670 GMR-01 68P02901W23-P 23 Feb 2004 . and that the combined total does not exceed 30. 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. RTFs must be equipped in the database. Syntax Change command strings chg_element res_ts_less_one_carrier <value> <location> <cell_desc> chg_cell_element res_ts_less_one_carrier <value> <cell_desc> Display command strings disp_cell <cell_desc> <"full"> disp_element res_ts_less_one_carrier <location> <cell_desc> 68P02901W23-P 23 Feb 2004 5-671 GMR-01 . Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required Yes Dependencies The GPRS feature must be unrestricted. 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. BSS software processes using this parameter are notified immediately after the change is made.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. assumes the value of res_gprs_pdchs 5-672 GMR-01 68P02901W23-P 23 Feb 2004 .res_ts_less_one_carrier Chapter 5: CM database parameters Values Value type Integer (timeslots) Valid range 0 to 30 Default value Until set. The idle channel categories are: X1. and X5. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required No Dependencies None Syntax Change command string chg_element rf_res_ind_period <value> <location> Display command string disp_element rf_res_ind_period <location> Values Value type Integer (1 Step = 1 SACCH multiframe) Valid range 1 to 127 Default value 10 References Internal name RF_RES_IND_PERIOD This is a Motorola parameter. the idle channel is categorized. The idle channel categories are reported to the CRM by the RSS. During this period.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. X3. X4. X2. 68P02901W23-P 23 Feb 2004 5-673 GMR-01 . The parameter rapid_pwr_down must be enabled. Syntax Add/Change command strings add_cell <cell_desc> <location> chg_element rpd_offset <value> <location> <cell_desc> chg_cell_element rpd_offset <value> <cell_desc> Display command strings disp_cell <cell_desc> ["full"] disp_element rpd_offset <location> <cell_desc> Values Value type Integer (1 dBm) Valid range 0 to 63 Default value 8 5-674 GMR-01 68P02901W23-P 23 Feb 2004 .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. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required Yes Dependencies This parameter must be less than rpd_trigger. This average is compared to the value specified for the rpd_trigger value. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required Yes Dependencies The parameter rapid_pwr_down must be enabled. The rapid power down procedure initiates when the calculated value is greater than the value specified for the rpd_trigger parameter.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. Syntax Add/Change command strings add_cell <cell_desc> <location> chg_element rpd_period <value> <location> <cell_desc> chg_cell_element rpd_period <value> <cell_desc> Display command strings disp_cell <cell_desc> ["full"] disp_element rpd_period <location> <cell_desc> Values Value type Integer (SACCH periods) Valid range 1 to 32 Default value 2 68P02901W23-P 23 Feb 2004 5-675 GMR-01 . Detected MS power levels are averaged over the number of SACCH periods specified by the rpd_period parameter. Syntax Add/Change command strings add_cell <cell_desc> <location> chg_element rpd_trigger <value> <location> <cell_desc> chg_cell_element rpd_trigger <value> <cell_desc> Display command strings disp_cell <cell_desc> ["full"] disp_element rpd_trigger <location> <cell_desc> 5-676 GMR-01 68P02901W23-P 23 Feb 2004 . This average is compared to the value specified for the rpd_trigger value. The receive uplink power level is equal to rpd_trigger minus rpd_offset. This parameter must be greater than rpd_offset. The rapid power down procedure initiates when the calculated value is greater than the value specified for the rpd_trigger parameter. The parameter rapid_pwr_down must be enabled. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required Yes Dependencies This parameter must be greater than l_rxlev_ul_p.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. .. from -110 dBm to -47 dBm... ..65 dBm) 5-677 GMR-01 ..... ...Technical Description BSS Command Reference rpd_trigger Values Value type Integer Valid range 0 to 63 Each step represents an increase of 1 dBm. as shown below: Default value 68P02901W23-P 23 Feb 2004 0 -110 dBm and lower 1 -109 dBm 2 -108 dBm . . . 63 -47 dBm and higher 45 (.. . When rpt_bad_qual_no_mr is set to 0. the previous value of RXQUAL is used to signify the RXQUAL measurement if the rxqual measurement is lost in the measurement report from the BSS. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required Yes Dependencies None Syntax Change command strings chg_element rpt_bad_qual_no_mr <value> <location> <cell_desc> chg_cell_element rpt_bad_qual_no_mr <value> <cell_desc> Display command strings 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-678 GMR-01 68P02901W23-P 23 Feb 2004 . is used to signify the RXQUAL measurement if the rxqual measurement is lost in the measurement report from the BSS. 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 2.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 1. RXQUAL 7. the worst quality value. 1 The worst quality value. RXQUAL 7. 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 0 5-679 GMR-01 .Technical Description BSS Command Reference Default value 68P02901W23-P 23 Feb 2004 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). is used to signify the RXQUAL measurement if the rxqual measurement is lost in the measurement report from the BSS. Operator actions Put the system into SYSGEN ON mode. Syntax Change command string chg_element rtf_path_enable <value> 0 Display command string disp_element rtf_path_enable 0 Values Value type Integer Valid range 0 or 1 Default value 0 Disabled 1 Enabled 0 5-680 GMR-01 68P02901W23-P 23 Feb 2004 . This parameter can be used only at the BSC. Type B (operator actions required) Supported by OMC-R GUI Yes Cell numbers required No Dependencies The RTF Fault Containment feature must be unrestricted.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. from -110 dBm to -47 dBm. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required Yes Dependencies None Syntax Add/Change command strings add_cell <cell_desc> <location> chg_element rxlev_access_min <value> <location> <cell_desc> chg_cell_element rxlev_access_min <value> <cell_desc> Display command strings disp_cell <cell_desc> ["full"] 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. as shown below: 0 -110 dBm and lower 1 -109 dBm 68P02901W23-P 23 Feb 2004 5-681 GMR-01 . 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.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. This should be set to a value corresponding to a signal level at which a call can be maintained in a particular environment. .4: C1 equation 12..20 .8. .08 .5.23.110 dBm) References GSM parameter RXLEV_ACCESS_MIN GSM specification 4. table 10.2 5-682 GMR-01 68P02901W23-P 23 Feb 2004 ..8..2: conditions for MS camping on a cell 5.. . ...17 5.. 63 -47 dBm and higher 0 (..5..rxlev_access_min Chapter 5: CM database parameters Default value 2 -108 dBm .10.2. .6.rx Lev Access Min 12.radio Link Ctl DL .2.5. .12 .20 .08 .4.2.. fig.6..08 . 10. A alg_num must be also specified to indicate the averaging algorithm as unweighted (0). Syntax Change command string chg_cell_element rxlev_dl_ho. If a value of 255 is entered for the alg_num. After entering the chg_cell_element command for this parameter. <bin_num> <alg_num> <cell_desc> Display command strings dis_cell <cell_desc> <"full"> disp_element rxlev_dl_ho. the following prompts are displayed and values must be entered: Enter hreqave: Enter hreqt: A bin_num is used with the disp_element rxlev_dl_ho command to identify the location of the parameters to be displayed. A bin_num must be specified with this command to indicate the location of the parameters to be modified.<bin_num> <location> <cell_desc> 68P02901W23-P 23 Feb 2004 5-683 GMR-01 . 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 Operator actions Respond to the prompts after entering this command. the bin is considered to contain invalid data.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. Type B (operator actions required) Supported by OMC-R GUI Yes Cell numbers required Yes Dependencies When alg_num is set to 255. 08 5-684 GMR-01 68P02901W23-P 23 Feb 2004 . A_PBGT_HO GSM specification 5.rxlev_dl_ho 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 GSM parameter A_LEV_HO. a bin_num must be specified to identify the location of the parameters to be displayed. the following prompts are displayed and values must be entered: Enter hreqave: Enter hreqt: When entering disp_element rxlev_dl_pc. After entering the chg_cell_element command for this parameter.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.<bin_num> <location> <cell_desc> 68P02901W23-P 23 Feb 2004 5-685 GMR-01 . A alg_num must be also specified to indicate the averaging algorithm as unweighted (0). the bin is considered to contain invalid data. Syntax Change command string chg_cell_element rxlev_dl_pc. If a value of 255 is entered for the alg_num. <bin_num> <alg_num> <cell_desc> Display command strings disp_cell <cell_desc> <"full"> disp_element rxlev_dl_pc. bin_num can not be set equal to decision_1_dl_rxlev_av_p. Type B (operator actions required) Supported by OMC-R GUI Yes Cell numbers required Yes Dependencies When alg_num is set to 255. A bin_num must be specified with this command to indicate the location of the parameters to be modified. Operator actions Respond to the prompts after entering this command. 08 5-686 GMR-01 68P02901W23-P 23 Feb 2004 .rxlev_dl_pc 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 GSM parameter A_LEV_PC GSM specification 5. 5-687 GMR-01 ...Technical Description BSS Command Reference rxlev_dl_zone rxlev_dl_zone Description The rxlev_dl_zone parameter specifies the downlink receive level threshold that must be crossed for a handover to take place between the outer zone and the inner zone. Type A (no operator actions) Supported by OMC-R GUI Yes Cell description required Yes Dependencies The Concentric Cells feature must be enabled and the inner_zone_alg type must be set to 1.. from -110 dBm to -47 dBm. . as shown below: 68P02901W23-P 23 Feb 2004 0 -110 dBm and lower 1 -109 dBm 2 -108 dBm .. Syntax Change command strings chg_element rxlev_dl_zone <value> <location> <cell_desc> chg_cell_element rxlev_dl_zone <value> <cell_desc> Display command strings disp_cell <cell_desc> <"full"> disp_element rxlev_dl_zone <location> <cell_desc> Values Value type Integer Valid range 0 to 63 Each step represents an increase of 1 dBm. .... .47 dBm) 5-688 GMR-01 68P02901W23-P 23 Feb 2004 ...rxlev_dl_zone Chapter 5: CM database parameters Default value . 63 -47 dBm and higher 63 (.... . from -110 dBm to -47 dBm.. as shown below: 68P02901W23-P 23 Feb 2004 0 -110 dBm and lower 1 -109 dBm 2 -108 dBm . Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required Yes Dependencies None Syntax Add/Change command strings add_cell <cell_desc> <location> chg_element rxlev_min_def <value> <location> <cell_desc> chg_cell_element rxlev_min_def <value> <cell_desc> Display command strings disp_cell <cell_desc> ["full"] disp_element rxlev_min_def <location> <cell_desc> Values Value type Integer Valid range 0 to 63 Each step represents an increase of 1 dBm.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.. ... 5-689 GMR-01 . . . 63 -47 dBm and higher 15 (-95 dBm) References GSM specification 5.08 . 5-690 GMR-01 68P02901W23-P 23 Feb 2004 . .Table 1 This is a Motorola defined parameter.....rxlev_min_def Chapter 5: CM database parameters Default value .Appendix A .. ... 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. A bin_num must be specified with this command to indicate the location of the parameters to be modified. bin_num can not be set equal to decision_1_ul_rxlev_av_h or decision_1_ul_rxlev_av_ih. the bin is considered to contain invalid data. After entering the chg_cell_element command for this parameter.<bin_num> <location> <cell_desc> 68P02901W23-P 23 Feb 2004 5-691 GMR-01 . a bin_num must be specified to identify the location of the parameters to be displayed. the following prompts are displayed and values must be entered: Enter hreqave: Enter hreqt: When entering disp_element rxlev_ul_ho. <bin_num> <alg_num> <cell_desc> Display command strings disp_cell <cell_desc> <"full"> disp_element rxlev_ul_ho. If a value of 255 is entered for the alg_num. Type B (operator actions required) Supported by OMC-R GUI Yes Cell numbers required Yes Dependencies When alg_num is set to 255. Operator actions Respond to the prompts after entering this command. A alg_num must be also specified to indicate the averaging algorithm as unweighted (0). Syntax Change command string chg_cell_element rxlev_ul_ho. rxlev_ul_ho 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 GSM parameter A_LEV_HO GSM specification 5.08 5-692 GMR-01 68P02901W23-P 23 Feb 2004 . 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. If a value of 255 is entered for the alg_num.<bin_num> <location> <cell_desc> 68P02901W23-P 23 Feb 2004 5-693 GMR-01 . bin_num can not be set equal to decision_1_ul_rxlev_av_p. Operator actions Respond to the prompts after entering this command. A alg_num must be also specified to indicate the averaging algorithm as unweighted (0). a bin_num must be specified to identify the location of the parameters to be displayed. Type B (operator actions required) Supported by OMC-R GUI Yes Cell numbers required Yes Dependencies When alg_num is set to 255. the following prompts are displayed and values must be entered: Enter hreqave: Enter hreqt: When entering disp_element rxlev_ul_pc. 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. <bin_num> <alg_num> <cell_desc> Display command strings disp_cell <cell_desc> <"full"> disp_element rxlev_ul_pc. the bin is considered to contain invalid data. Syntax Change command string chg_cell_element rxlev_ul_pc. 08 5-694 GMR-01 68P02901W23-P 23 Feb 2004 .rxlev_ul_pc 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 GSM parameter A_LEV_PC GSM specification 5. . as shown below: 68P02901W23-P 23 Feb 2004 0 -110 dBm and lower 1 -109 dBm 2 -108 dBm . Type A (no operator actions) Supported by OMC-R GUI Yes Cell description required Yes Dependencies The Concentric Cells Option must be enabled and the inner_zone_alg parameter must be set to 1. 5-695 GMR-01 ..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. . from -110 dBm to -47 dBm... Syntax Change command strings chg_element rxlev_ul_zone <value> <location> <cell_desc> chg_cell_element rxlev_ul_zone <value> <cell_desc> Display command strings disp_cell <cell_desc> <"full"> disp_element rxlev_ul_zone <location> <cell_desc> Values Value type Integer Valid range 0 to 63 Each step represents an increase of 1 dBm. .. ...rxlev_ul_zone Chapter 5: CM database parameters Default value .. 63 -47 dBm and higher 63 (-47 dBm) 5-696 GMR-01 68P02901W23-P 23 Feb 2004 .. ... . 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. Syntax Change command string chg_cell_element rxqual_dl_ho. <bin_num> <alg_num> <cell_desc> Display command strings disp_cell <cell_desc> <"full"> disp_element rxqual_dl_ho.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. After entering the chg_cell_element command for this parameter. the following prompts are displayed and values must be entered: Enter hreqave: Enter hreqt: Enter w_qual: When entering disp_element rxqual_dl_ho. A bin_num must be specified with this command to indicate the location of the parameters to be modified. bin_num can not be set equal to decision_1_dl_rxqual_av_h. Operator actions Respond to the prompts after entering this command.<bin_num> <location> <cell_desc> 68P02901W23-P 23 Feb 2004 5-697 GMR-01 . Type B (operator actions required) Supported by OMC-R GUI Yes Cell numbers required Yes Dependencies When alg_num is set to 255. a bin_num must be specified to identify the location of the parameters to be displayed. rxqual_dl_ho 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 Qual_weight 0 to 255 1 References GSM parameter A_QUAL_HO GSM specification 5.08 5-698 GMR-01 68P02901W23-P 23 Feb 2004 . If a value of 255 is entered for the alg_num.<bin_num> <location> <cell_desc> 68P02901W23-P 23 Feb 2004 5-699 GMR-01 . <bin_num> <alg_num> <cell_desc> Display command strings disp_cell <cell_desc> <"full"> disp_element rxqual_dl_pc. Type B (operator actions required) Supported by OMC-R GUI Yes Cell numbers required Yes Dependencies When alg_num is set to 255. the bin is considered to contain invalid data. a bin_num must be specified to identify the location of the parameters to be displayed. bin_num can not be set equal to decision_1_dl_rxqual_av_p Operator actions Respond to the prompts after entering this command. A alg_num must be also specified to indicate the averaging algorithm as unweighted (0). After entering the chg_cell_element command for this parameter. Syntax Change command string chg_cell_element rxqual_dl_pc. A bin_num must be specified with this command to indicate the location of the parameters to be modified.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. the following prompts are displayed and values must be entered: Enter hreqave: Enter hreqt: Enter w_qual: When entering disp_element rxqual_dl_pc. 08 This is a Motorola defined parameter.rxqual_dl_pc 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 Qual_weight 0 to 255 1 References GSM specification 5. 5-700 GMR-01 68P02901W23-P 23 Feb 2004 . 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. After entering the chg_cell_element command for this parameter. If a value of 255 is entered for the alg_num. Type B (operator actions required) Supported by OMC-R GUI Yes Cell numbers required Yes Dependencies When alg_num is set to 255. the bin is considered to contain invalid data. A alg_num must be also specified to indicate the averaging algorithm as unweighted (0). Operator actions Respond to the prompts after entering this command.<bin_num> <location> <cell_desc> 68P02901W23-P 23 Feb 2004 5-701 GMR-01 . <bin_num> <alg_num> <cell_desc> Display command strings disp_cell <cell_desc> <"full"> disp_element rxqual_ul_ho. a bin_num must be specified to identify the location of the parameters to be displayed. Syntax Change command string chg_cell_element rxqual_ul_ho. bin_num can not be set equal to decision_1_ul_rxqual_av_h. A bin_num must be specified with this command to indicate the location of the parameters to be modified. the following prompts are displayed and values must be entered: Enter hreqave: Enter hreqt: Enter w_qual: When entering disp_element rxqual_ul_ho. 08 5-702 GMR-01 68P02901W23-P 23 Feb 2004 .rxqual_ul_ho 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 Qual_weight 0 to 255 1 References GSM parameter A_QUAL_HO GSM specification 5. a bin_num must be specified to identify the location of the parameters to be displayed. After entering the chg_cell_element command for this parameter. the bin is considered to contain invalid data. If a value of 255 is entered for the alg_num.<bin_num> <location> <cell_desc> 68P02901W23-P 23 Feb 2004 5-703 GMR-01 . Syntax Change command string chg_cell_element rxqual_ul_pc. bin_num can not be set equal to decision_1_ul_rxqual_av_p. A bin_num must be specified with this command to indicate the location of the parameters to be modified. Operator actions Respond to the prompts after entering this command. the following prompts are displayed and values must be entered: Enter hreqave: Enter hreqt: Enter w_qual: When entering disp_element rxqual_ul_pc.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. Type B (operator actions required) Supported by OMC-R GUI Yes Cell numbers required Yes Dependencies When alg_num is set to 255. <bin_num> <alg_num> <cell_desc> Display command strings disp_cell <cell_desc> <"full"> disp_element rxqual_ul_pc. A alg_num must be also specified to indicate the averaging algorithm as unweighted (0). rxqual_ul_pc 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 Qual_weight 0 to 255 1 References GSM parameter A_QUAL_PC GSM specification 5.08 5-704 GMR-01 68P02901W23-P 23 Feb 2004 . When this parameter is displayed using the disp_element command.<index> <location> Values Value type Integer Valid range 0 to 2.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. Type A (no operator actions) Supported by OMC-R GUI No Cell numbers required No Dependencies None Syntax Change command string This parameter can not be modified from the MMI. The index values available for use are described under "Indices" on page 1-23. The device is specified as an index value when entering 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). 255 Default value 68P02901W23-P 23 Feb 2004 0 Safe (Safe Tests) 1 int_lpbk (Internal Loopback Tests) 2 Self test 255 No audit 255 5-705 GMR-01 . Display command string disp_element sap_audit_type. The device is specified as an index value when entering the disp_element command.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.<index> <location> Values Value type Text Valid range N/A Default value None 5-706 GMR-01 68P02901W23-P 23 Feb 2004 . the device type is displayed as an alphabetic character string (such as sap_device_type = DRI). Type A (no operator actions) Supported by OMC-R GUI No Cell numbers required No Dependencies None Syntax Change command strings This parameter can not be modified from the MMI. When this parameter is displayed using the disp_element command. The index values available for use are described under "Indices" on page 1-23. Display command string disp_element sap_device_type. <index> <location> Values Value type Integer Valid range Hours 0 to 23 Minutes 0 to 59 Default value 68P02901W23-P 23 Feb 2004 None 5-707 GMR-01 . The index values available for use are described under "Indices" on page 1-23. Type A (no operator actions) Supported by OMC-R GUI No Cell numbers required No Dependencies None Syntax Change command strings chg_audit_sched <location> <device_name> <audit_type> <start_time_hour> <start_time_min> <end_time_hour> <end_time_min> <interval_hour> <interval_min> Display command string disp_element sap_end_time.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). 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. Type A (no operator actions) Supported by OMC-R GUI No Cell numbers required No Dependencies None Syntax Change command strings chg_audit_sched <location> <device_name> <audit_type> <start_time_hour> <start_time_min> <end_time_hour> <end_time_min> <interval_hour> <interval_min> Display command string disp_element sap_interval. When this parameter is displayed using the disp_element command. The device is specified as an index value when entering the disp_element command.sap_interval Chapter 5: CM database parameters sap_interval Description The sap_interval parameter specifies the interval for a device audit. the time is presented in military standard time or GMT (such as sap_interval = 13:45).<index> <location> sap_interval = interval_hour:interval_min Values Value type Integer Valid range Hours 0 to 23 5-708 GMR-01 68P02901W23-P 23 Feb 2004 . Technical Description BSS Command Reference Minutes Default value 68P02901W23-P 23 Feb 2004 sap_interval 0 to 59 None 5-709 GMR-01 . <index> <location> sap_interval = interval_hour:interval_min Values Value type Integer Valid range Hours 0 to 23 5-710 GMR-01 68P02901W23-P 23 Feb 2004 . 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. the time is presented in military standard time or GMT (such as sap_end_time = 13:45). When this parameter is displayed using the disp_element command.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. Type A (no operator actions) Supported by OMC-R GUI No Cell numbers required No Dependencies None Syntax Change command strings chg_audit_sched <location> <device_name> <audit_type> <start_time_hour> <start_time_min> <end_time_hour> <end_time_min> <interval_hour> <interval_min> Display command string disp_element sap_start_time. Technical Description BSS Command Reference sap_start_time Minutes Default value 68P02901W23-P 23 Feb 2004 0 to 59 None 5-711 GMR-01 . Operator actions Place the system in the SYSGEN ON mode before using the chg_element command to change this parameter. and Subsystem Test (SST). the BSS detects Signalling Point Inaccessible and loss of BSSAP subsystem. (Use with Ericsson MSC) When disabled. Type B (operator actions required) Supported by OMC-R GUI No Cell numbers required No Dependencies This parameter applies only to the BSC. The BSS also handles the following messages: User Part Unavailable (UPU). Subsystem Allowed (SSA).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 always responds to an SST with an SSA message. Syntax Change command string chg_element sccp_bssap_mgt <value> 0 Display command string disp_element sccp_bssap_mgt 0 Values Value type Boolean Valid range 0 or 1 0 Disabled 5-712 GMR-01 68P02901W23-P 23 Feb 2004 . 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. Subsystem prohibited (SSP). Technical Description BSS Command Reference sccp_bssap_mgt 1 Default value 68P02901W23-P 23 Feb 2004 Enabled 1 5-713 GMR-01 . Syntax Change command string chg_element scr_enabled <value> <location> Display command string disp_element scr_enabled <location> Values Value type Boolean Valid range 0 or 1 5-714 GMR-01 68P02901W23-P 23 Feb 2004 . BSS software processes using this parameter are notified immediately the change is made. or not. This parameter can be set in or out of SYSGEN mode. None Operator actions: This is a Motorola proprietary parameter. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required No Dependencies The Seamless Cell Reselection feature must be available before it can be enabled with this parameter.scr_enabled Chapter 5: CM database parameters scr_enabled {4449} Description The scr_enabled parameter specifies whether the Seamless Cell Reselection feature is enabled at a BSC. Technical Description BSS Command Reference Default value 68P02901W23-P 23 Feb 2004 scr_enabled 0 Seamless cell reselection is not enabled (off) 1 Seamless cell reselection is enabled (on) 0 5-715 GMR-01 . the sdcch_ho parameter must be enabled and the sdcch_timer_ho parameter set to its minimum value of 1. To allow handovers on the SDCCH with a minimum delay. When enabled. Syntax Add/Change command strings add_cell <gsm_cell_id> <location> chg_element sdcch_ho <value> <location> <cell_desc> chg_cell_element sdcch_ho <value> <cell_desc> Display command strings disp_cell <cell_desc> ["full"] disp_element sdcch_ho <location> <cell_desc> 5-716 GMR-01 68P02901W23-P 23 Feb 2004 . Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required Yes Dependencies External SDCCH handover must be enabled at and supported by the MSC The handover_required_curr_ch parameter must be set to 1 so as to include the information element in the handover required message to the MSC. handovers are not allowed until at least (sdcch_timer_ho * 2) measurement report periods have elapsed.sdcch_ho Chapter 5: CM database parameters sdcch_ho Description The sdcch_ho parameter enables or disables handovers on the SDCCH. Technical Description BSS Command Reference sdcch_ho Values Value type Boolean Valid range 0 or 1 Default value 0 Disabled 1 Enabled 1 References Internal name 68P02901W23-P 23 Feb 2004 EN_SDCCH_HO 5-717 GMR-01 . 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 difference between the values for sdcch_need_high_water_mark and sdcch_need_low_water_mark must be greater than or equal to 9. The total number of SDCCHs can not exceed the value of the max_number_of_sdcchs parameter. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required Yes Syntax Change command strings chg_element sdcch_need_high_water_mark <value> <location> <cell_desc> chg_cell_element sdcch_need_high_water_mark <value> <cell_desc> Display command strings disp_cell <cell_desc> ["full"] disp_element sdcch_need_high_water_mark <location> <cell_desc> 5-718 GMR-01 68P02901W23-P 23 Feb 2004 . For stable operation of the channel reconfiguration process. the CRM tries to reconfigure TCHs in order to make more SDCCHs.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. 6.02 . 5-719 GMR-01 .4 This is a Motorola defined parameter.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 GSM specification 68P02901W23-P 23 Feb 2004 5. For stable operation of the channel reconfiguration process. It is triggered when the first reconfiguration is complete and an SDCCH is released. reconfiguration is not triggered.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. Once the number of idle SDCCHs is greater than the low water mark. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required Yes Syntax Change command strings chg_element sdcch_need_low_water_mark <value> <location> <cell_desc> chg_cell_element sdcch_need_low_water_mark <value> <cell_desc> Display command strings disp_cell <cell_desc> ["full"] disp_element sdcch_need_low_water_mark <location> <cell_desc> 5-720 GMR-01 68P02901W23-P 23 Feb 2004 . When dynamic channel reconfiguration is enabled. If CRM is reconfiguring an SDCCH to TCH and the low water mark is passed again. 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. 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. SDCCH to TCH reconfiguration is triggered. Note that the low water mark is checked only when an SDCCH is released. and when the number of idle SDCCHs available goes above the sdcch_need_low_water_mark value. 4 This is a Motorola defined parameter. 5-721 GMR-01 .6.Technical Description BSS Command Reference sdcch_need_low_water_mark Values Value type Integer (number SDCCHs) Valid range 10 to 48 Default value 12 References GSM specification 68P02901W23-P 23 Feb 2004 5.02 . 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. Use of this parameter may cause a delay in call setup of up to two seconds. This parameter applies to multiband MSs only. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required Yes Dependencies The Multiband Inter-cell Handover feature must be unrestricted. Syntax Change command strings chg_element sdcch_tch_band_reassign_delay <value> <location> <cell_desc> chg_cell_element sdcch_tch_band_reassign_delay <value> <cell_desc> Display command strings disp_cell <cell_desc> ["full"] disp_element sdcch_tch_band_reassign_delay <location> <cell_desc> Values Value type Integer (number of measurement report periods) Valid range 0 to 4 Default value 0 5-722 GMR-01 68P02901W23-P 23 Feb 2004 . .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. 5-723 GMR-01 ..) Syntax Add/Change command strings add_cell <gsm_cell_id> <location> chg_element sdcch_timer_ho <value> <location> <cell_desc> chg_cell_element sdcch_timer_ho <value> <cell_desc> Display command strings disp_cell <cell_desc> ["full"] disp_element sdcch_timer_ho <location> <cell_desc> Values Value type Integer (1 Step = 2 SACCH multiframes) Valid range 1 to 31 68P02901W23-P 23 Feb 2004 1 2 SACCH multiframes 2 4 SACCH multiframes 3 6 SACCH multiframes .. (This is not monitored by the system.. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required Yes Dependencies The sdcch_ho parameter must be enabled. . .. . 5-724 GMR-01 68P02901W23-P 23 Feb 2004 . 31 62 SACCH multiframes 1 References GSM parameter T_SDCCH_HO_ALLOWED This is a Motorola parameter.... ..sdcch_timer_ho Chapter 5: CM database parameters Default value . ... 1 5-725 GMR-01 . 3G cells are searched when BSIC coding is required.Technical Description BSS Command Reference search_prio_3g search_prio_3g {3723} Description The search_prio_3g parameter specifies whether 3G cells are searched when BSIC coding is required. Type A (no operator actions) Supported by OMC-R GUI Yes Cell description required Yes Dependencies The PBCCH/PCCCH feature must be unrestricted for this parameter to change. Syntax Add/Change command strings chg_element search_prio_3g <value> <location> <cell_desc> chg_cell_element search_prio_3g <value> <cell_desc> Display command strings disp_cell <cell_desc> “full" disp_element search_prio_3g <location> <cell_desc> Values Value type Integer Valid range 0 or 1 0 1 Default value 68P02901W23-P 23 Feb 2004 3G cells are not searched when BSIC coding is required. the cause values are not used. • The BSS does not trigger Directed Retry procedures if the cell is congested (that is. • An extended range TCH from a different carrier is assigned to an extended range MS during the second assignment. The purpose of this parameter is to improve overall TCH assignment success and call set-up success. rather than RF failure. To ensure that the true cause of initial assignment is not masked. starting from the outer most zone. • An extended range TCH from a different carrier is assigned to a normal range MS if there are no normal range channels available. • The BSS attempts to assign a TCH from a different carrier. In situations where first TCH assignment fails and the MS successfully recovers to the SDCCH. • Increased SDCCH utilization for those call set-ups which fail first assignment. The following lists the impacts when this parameter is enabled: • Enabled on a per BSS basis. This assignment starts from the outer most zone. no resources are available) when a second assignment is initiated for a call. until an available channel is found. 5-726 GMR-01 68P02901W23-P 23 Feb 2004 . assignments from the zone’s interior are not made to the qualified zone of the MS. • MSC Assignment Complete Timer. With this parameter enabled. the RRSM initiates a second assignment procedure if it receives an assignment failure from the MS for the first assignment. Even if the second assignment failure is a result of a lack of resources or equipment failure. • Initiated only for MSC assignments (not for intra-cell handovers). • The BSS does not pre-empt a call during the second assignment attempt for an emergency call when there are no resources available. However. this parameter enables a second TCH assignment attempt. a second attempt failure results in an unsuccessful assignment message being sent to the SSM. • 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. • Additional statistics pegging on analysis software.second_asgnmnt Chapter 5: CM database parameters second_asgnmnt Description The second_asgnmnt parameter enables or disables the Second Assignment procedure. Type A (no operator actions) Supported by OMC-R GUI No Cell numbers required No Dependencies None Syntax Change command strings chg_element second_asgnmnt <value> 0 Display command strings disp_element second_asgnmnt 0 Values Value type Boolean Valid range 0 or 1 Default value 68P02901W23-P 23 Feb 2004 0 Disabled 1 Enabled 0 5-727 GMR-01 .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. Type A (no operator actions) Supported by OMC-R GUI No Cell numbers required No Dependencies This parameter is set to the primary frequency type when a cell is not configured as a Dual Band cell. At non-Dual Band cells. the secondary_freq_type can only be set to DCS1800. the secondary_freq_type is set to the primary frequency type. This parameter may be modified only when changing inner_zone_alg to 3 with the chg_cell_element command. Syntax Change command string chg_cell_element <location> secondary_freq_type <value> <location> Display command string disp_element secondary_freq_type <location> Values Value type Integer Valid range 1 to 8 binary values as shown below: 1 PGSM 5-728 GMR-01 68P02901W23-P 23 Feb 2004 .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. • When the Cell frequency is set to DCS1800. the secondary_freq_type can only be set to PGSM or EGSM. At Dual Band Cells: • When the Cell frequency type is set to PGSM or EGSM. Technical Description BSS Command Reference Default value 68P02901W23-P 23 Feb 2004 secondary_freq_type 2 EGSM 4 DCS1800 8 PCS 1900 None 5-729 GMR-01 . 1 SGSN is compliant with 3GPP Release 1999 or newer. Syntax Change command string chg_element sgsn_release <value> 0 Display command string disp_element sgsn_release 0 Values Value type Integer (number of frames) Valid range 0 or 1 Default value 0 SGSN is compliant with 3GPP Release 1998 or older. is 1999 or later.sgsn_release Chapter 5: CM database parameters sgsn_release {3723} Description The sgsn_release parameter specifies whether the release version (year of release) of the Serving GPRS Support Node (SGSN) for the BSS. 0 5-730 GMR-01 68P02901W23-P 23 Feb 2004 . Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required No Dependencies The PBCCH/PCCCH optional feature must be unrestricted. the daily alarm triggers. For example. Syntax Change command string chg_element slip_loss_daily <value> <location> Display command string disp_element slip_loss_daily <location> Values Value type Integer Valid range {4415} 0 to 65534 Default value 4 68P02901W23-P 23 Feb 2004 5-731 GMR-01 . Type A (no operator actions) Supported by OMC-R GUI No Cell numbers required No Dependencies This parameter must be less than slip_loss_hourly. The hourly alarm triggers only if 25 alarms occur within the hour.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. Consider slip_loss_daily as the first level of notification of slip loss. and 20 slip loss problems occur during the day. and slip_loss_hourly alarm as a higher level indicating a more serious problem. An alarm generates if the count of frame slips meets or exceeds this threshold in a 24 hour period. if slip_loss_daily is set to 20 and slip_loss_hourly to 25. which would indicate a much more serious problem. if slip_loss_daily is set to 20 and slip_loss_hourly to 25. Syntax Change command string chg_element slip_loss_hourly <value> <location> Display command string disp_element slip_loss_hourly <location> Values Value type Integer Valid range {4415} 1 to 65535 Default value 10 5-732 GMR-01 68P02901W23-P 23 Feb 2004 . the daily alarm triggers. Type A (no operator actions) Supported by OMC-R GUI No Cell numbers required No Dependencies This parameter must be greater than slip_loss_daily. and 20 slip loss problems occur during the day. For example. The hourly alarm triggers only if 25 alarms occur within the hour. and slip_loss_hourly alarm as a higher level indicating a more serious problem.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. which would indicate a much more serious problem. However. 68P02901W23-P 23 Feb 2004 5-733 GMR-01 .Technical Description BSS Command Reference slip_loss_hourly MSI-2 boards default to a value of 20 on power-up. when MSI-2 boards are brought in-service they default to whatever value is set in the database. The 2 Mbit/s circuit is taken out of service if the number of frame slips exceeds this threshold during a 24 hour period.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. Type A (no operator actions) Supported by OMC-R GUI No Cell numbers required No Dependencies None Syntax Change command string chg_element slip_loss_oos <value> <location> Display command string disp_element slip_loss_oos <location> Values Value type Integers Valid range 0 to 65535 Default value 255 5-734 GMR-01 68P02901W23-P 23 Feb 2004 . .. the 2 Mbit/s circuit is brought back into service...2 seconds 200 milliseconds ..Technical Description BSS Command Reference slip_loss_restore slip_loss_restore Description The slip_loss_restore parameter specifies the frame slip restorable time period.. 600 60 seconds ..5 seconds 6553500 milliseconds 600 60 seconds 60000 milliseconds 60000 milliseconds 5-735 GMR-01 .1 seconds 100 milliseconds 2 0. Type A (no operator actions) Supported by OMC-R GUI No Cell numbers required No Dependencies None Syntax Change command string chg_element slip_loss_restore <value> <location> <cell_desc> Display command string disp_element slip_loss_restore <location> <cell_desc> Values Value type Integer (1 step = 100 milliseconds Valid range 0 to 65535 Default value 68P02901W23-P 23 Feb 2004 0 0 seconds 0 milliseconds 1 0.. 65535 6553. If no errors occur during this period. . . Type B (operator actions required) Supported by OMC-R GUI Yes Cell numbers required No Dependencies The GPRS feature must be unrestricted.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 Change command string chg_element smg_gb_vers <value> 0 Display command string disp_element smg_gb_vers <value> 0 Values Value type Integer Valid range 24 to 31 Default value 31 5-736 GMR-01 68P02901W23-P 23 Feb 2004 . 5-737 GMR-01 . Syntax Change command string chg_element sms_dl_allowed <value> <location> Display command string disp_element sms_dl_allowed <location> Values Value type Boolean Valid range 0 or 1 Default value 0 Disabled 1 Enabled 0 References GSM specification 68P02901W23-P 23 Feb 2004 3.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).04 This is a Motorola defined parameter. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required No Dependencies The SMS Point to Point feature must be unrestricted. If the current radio channel is an SDCCH. The FACCH is tried first. The timing constraints on the SACCH allow a block to be transferred every 208 frames. the SACCH is used. and if this fails. Type A (no operator actions) Supported by OMC-R GUI No Cell numbers required No Dependencies The SMS Point to Point feature must be unrestricted. Syntax Change command string chg_element sms_tch_chan <value> <location> Display command string disp_element sms_tch_chan <location> 5-738 GMR-01 68P02901W23-P 23 Feb 2004 . Stealing frames on the FACCH would be more noticeable as the size of the short message increases. SMS on the FACCH is not covered in the GSM specifications and may not be supported by mobile stations. The disadvantage of the FACCH channel is that frames are stolen. while the FACCH allows a block to be delivered every 8 frames. the SDCCH will be used.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. with injurious effects on the audio quality or data transmission. Choosing to provide an SMS on the FACCH provides more opportunity to deliver the message. but using the SACCH for larger short messages means longer delivery times. Technical Description BSS Command Reference sms_tch_chan Values Value type Integer Valid range 0 to 2 Default value 0 BSS_ALGORITHM 1 FACCH always used 2 SACCH always used 2 References GSM specification 68P02901W23-P 23 Feb 2004 3.04 This is a Motorola defined parameter. 5-739 GMR-01 . 04 This is a Motorola defined parameter. Syntax Change command string chg_element sms_ul_allowed <value> <location> Display command string disp_element sms_ul_allowed <location> Values Value type Boolean Valid range 0 or 1 Default value 0 Disabled 1 Enabled 0 References GSM specification 3.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). 5-740 GMR-01 68P02901W23-P 23 Feb 2004 . Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required No Dependencies The SMS Point to Point feature must be unrestricted. The ANSI version is used to support PCS1900 applications in the United States." 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 error message displays only if lcs_mode is 2 and lb_int_dpc is in range. If the three variables are not compatible. Operator actions Place the system in the SYSGEN ON mode to change this parameter. If the ranges are not compatible. This parameter can be changed only when the user is in SYSGEN ON mode. The ITU C7 version is consistent with the GSM specifications. to be out of range. the system rejects the change and displays an error message.Technical Description BSS Command Reference ss7_mode ss7_mode Description The ss7_mode parameter specifies the type of SS#7 for the BSC. Type B (operator actions required) Supported by OMC-R GUI No Cell numbers required No Dependencies The system checks the values of the opc (see "opc" on page 5-561) and dpc (see "dpc" on page 5-214) variables and compares them to the value of ss7_mode. Syntax Change command strings chg_element ss7_mode <value> <location> Display command strings disp_element ss7_mode <location> 68P02901W23-P 23 Feb 2004 5-741 GMR-01 . It can only be changed for site 0. This parameter requires a location value of “0" or “bsc. or both. the command is rejected. opc. This parameter permits the ITU or ANSI version to be selected. If the operator attempts to change the SS7 mode element to a value which would cause the Lb-interface DPC and either the dpc. or if lcs_mode is not 2. the system rejects the changes. When the ss7_mode parameter is changed. the system compares the value to the settings for dpc and opc. All BTS site values are set to the same value assigned to site 0. the command is rejected. ss7_mode Chapter 5: CM database parameters Values Value type Boolean Valid range 0 or 1 Default value 0 ITU version 1 ANSI version 0 5-742 GMR-01 68P02901W23-P 23 Feb 2004 . Syntax Change command string chg_element ssm_critical_overload_threshold <value> 0 Display command string disp_element ssm_critical_overload_threshold 0 68P02901W23-P 23 Feb 2004 5-743 GMR-01 . The remaining SSM resources are used to accommodate handover of existing calls. This parameter applies only to the BSC. Every time the usage meets or exceeds this threshold. rach_load_threshold. This number has to be greater than the ssm_normal_overload_threshold parameter. two access classes are barred. Type A (no operator actions) Supported by OMC-R GUI No Cell numbers required No Dependencies Must be greater than the ssm_normal_overload_threshold parameter. no MS originated calls are allowed. ssm_normal_overload_threshold or tch_flow_control.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. rach_load_period. as expressed by the ratio of the number of active calls to the maximum number of calls the SSM can handle (400). Refer to ccch_load_period. Other parameters can affect flow control. After this threshold has been met or exceeded. ssm_critical_overload_threshold Chapter 5: CM database parameters Values Value type Integer (percent of call information blocks in use) Valid range 0 to 100 Default value 80 5-744 GMR-01 68P02901W23-P 23 Feb 2004 . 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. Syntax Change command string chg_element ssm_normal_overload_threshold <value> 0 Display command string disp_element ssm_normal_overload_threshold 0 Values Value type Integer (percent of call information blocks in use) Valid range 0 to 100 Default value 70 68P02901W23-P 23 Feb 2004 5-745 GMR-01 . rach_load_threshold. ssm_critical_overload_threshold or tch_flow_control. Other parameters can affect flow control. Every time the usage equals or exceeds this threshold. one access class will be barred. Type A (no operator actions) Supported by OMC-R GUI No Cell numbers required No Dependencies Must be less than the ssm_critical_overload_threshold parameter. This parameter applies only to the BSC. rach_load_period. Refer to ccch_load_period. 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. Statistical information is forwarded from the Site Statistics Process (SSP) to the Central Statistics Process (CSP) in bursts. The number of messages in each burst are specified by the ssp_burst_limit parameter. Type A (no operator actions) Supported by OMC-R GUI No Cell numbers required No Dependencies None Syntax Change command string chg_element ssp_burst_delay <value> <location> Display command string disp_element ssp_burst_delay <location> Values Value type Integer (milliseconds) Valid range 0 to 2500 Default value 200 5-746 GMR-01 68P02901W23-P 23 Feb 2004 . 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. Type A (no operator actions) Supported by OMC-R GUI No Cell numbers required No Dependencies None Syntax Change command string chg_element ssp_burst_limit <value> <location> Display command string disp_element ssp_burst_limit <location> Values Value type Integer (number of messages) Valid range 1 to 65535 Default value 10 68P02901W23-P 23 Feb 2004 5-747 GMR-01 . Statistical information is forwarded from the Site Statistical Process (SSP) to the Central Statistical Process (CSP) in bursts. The length of time between bursts is specified by the ssp_burst_delay parameter. If the operator fails to reset the interval to 30 minutes. the OMC-R only parses uploaded statistics files if this attribute is set to 30 or 60 minutes. the OMC-R calculations of the Key Statistics and Health Indicators are interrupted for the entire period until the interval is reset. Type A (no operator actions) Supported by OMC-R GUI No Cell numbers required No Dependencies Must be set to 30 or 60 minutes to align with the OMC-R.stat_interval Chapter 5: CM database parameters stat_interval Description The stat_interval parameter sets the time. Syntax Change command string chg_element stat_interval <value> 0 Display command string disp_element stat_interval 0 Values Value type Integer (minutes) Valid range 5 to 60 Default value 30 Although any value between 5 and 60 minutes is valid. 5-748 GMR-01 68P02901W23-P 23 Feb 2004 . that the statistics file is reported to the OMC-R. in minutes. If a value of 255 is entered for the alg_num. After entering the chg_cell_element command for this parameter. A bin_num must be specified with this command to indicate the location of the parameters to be modified. a bin_num must be specified to identify the location of the parameters to be displayed. Syntax Change command string chg_cell_element surround_cell. bin_num can not be set equal to decision_1_pbgt_rxlev_av_h. Operator actions Respond to the prompts after entering this command. the following prompts are displayed and values must be entered: Enter hreqave: Enter hreqt: When entering disp_element surround_cell. The system uses this parameter to determine which neighbour cell to hand off to.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. <bin_num> <alg_num> <cell_desc> Display command string disp_cell <cell_desc> <"full"> disp_element surround_cell. A alg_num must be also specified to indicate the averaging algorithm as unweighted (0).<bin_num> <location> <cell_desc> 68P02901W23-P 23 Feb 2004 5-749 GMR-01 . the bin is considered to contain invalid data. Type B (operator actions required) Supported by OMC-R GUI Yes Cell numbers required Yes Dependencies When alg_num is set to 255. 08 5-750 GMR-01 68P02901W23-P 23 Feb 2004 .surround_cell Chapter 5: CM database parameters Values Value type Integer Valid range 0 to 255 Default value None References GSM parameter A_PBGT_HO GSM specification 5. 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. RTFs must be equipped in the database. 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. Syntax Change command strings chg_element sw_ts_less_one_carrier <value> <location> <cell_desc> chg_cell_element sw_ts_less_one_carrier <value> <cell_desc> Display command strings disp_element sw_ts_less_one_carrier <location> <cell_desc> 68P02901W23-P 23 Feb 2004 5-751 GMR-01 .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). Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required Yes Dependencies The GPRS feature must be unrestricted. BSS software processes using this parameter are notified immediately after the change is made. assumes the value of switch_gprs_pdchs 5-752 GMR-01 68P02901W23-P 23 Feb 2004 .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. This parameter affects the entire BSS. Syntax Change command string chg_element swfm_enable <value> 0 Display command string disp_element swfm_enable 0 Values Value type Boolean Valid range 0 or 1 Default value 68P02901W23-P 23 Feb 2004 0 Disabled 1 Enabled 0 5-753 GMR-01 .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. Type A (no operator actions) Supported by OMC-R GUI No Cell numbers required No Dependencies This parameter applies only to a BSC. 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-312.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. must be exceeded. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required Yes Dependencies The GPRS feature must be unrestricted. BSS software processes using this parameter are notified immediately after the change is made. Syntax Change command strings chg_element switch_gprs_pdchs <value> <location> <cell_desc> chg_cell_element switch_gprs_pdchs <value> <cell_desc> Display command string disp_element switch_gprs_pdchs <location> <cell_desc> 5-754 GMR-01 68P02901W23-P 23 Feb 2004 . Technical Description BSS Command Reference switch_gprs_pdchs Values Value type Integer (number of timeslots) Valid range 0 to 30 Default value 0 68P02901W23-P 23 Feb 2004 5-755 GMR-01 . An alarm generates if the number of synchronization loss alarms meets or exceeds this threshold during a 24 hour period. Type A (no operator actions) Supported by OMC-R GUI No Cell numbers required No Dependencies This parameter must be less than sync_loss_hourly. Syntax Change command string chg_element sync_loss_daily <value> <location> Display command string disp_element sync_loss_daily <location> Values Value type Integer Valid range 0 to 65535 Default value 16 5-756 GMR-01 68P02901W23-P 23 Feb 2004 .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. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required No Dependencies This parameter must be greater than sync_loss_daily. Syntax Change command string chg_element sync_loss_hourly <value> <location> Display command string disp_element sync_loss_hourly <location> Values Value type Integer Valid range 0 to 65535 Default value 20 68P02901W23-P 23 Feb 2004 5-757 GMR-01 .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. 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.sync_loss_oos Chapter 5: CM database parameters sync_loss_oos Description The sync_loss_oos parameter specifies the threshold for the synchronization loss. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required No Dependencies None Syntax Change command string chg_element sync_loss_oos <value> <location> Display command string disp_element sync_loss_oos <location> Values Value type Integer Valid range 0 to 65535 Default value 511 5-758 GMR-01 68P02901W23-P 23 Feb 2004 . Out Of Service (OOS) daily alarm level count. . . . . .1 second 100 milliseconds . If a synchronization loss alarm does not occur within this period. . 25 2. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required No Dependencies None Syntax Change command string chg_element sync_loss_restore <value> <location> <cell_desc> Display command string disp_element sync_loss_restore <location> <cell_desc> Values Value type Integer (1 step = 100 milliseconds) Valid range 0 to 65535 Default value 68P02901W23-P 23 Feb 2004 0 0 seconds 0 milliseconds 1 0. .5 seconds 6553500 milliseconds 600 60 seconds 60000 milliseconds 5-759 GMR-01 . .. the 2 Mbit/s circuit is brought back in service.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.. .5 seconds 2500 milliseconds . 65535 6553.. ... . . 65535 6553. . If synchronization is lost for this period. . ... .sync_time_oos Chapter 5: CM database parameters sync_time_oos Description The sync_time_oos parameter specifies the synchronization loss time period. . Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required No Dependencies None Syntax Change command string chg_element sync_time_oos <value> <location> Display command string disp_element sync_time_oos <location> Values Value type Integer (1 step = 100 milliseconds) Valid range 0 to 65535 Default value 0 0 seconds 0 milliseconds 1 0.5 seconds 2500 milliseconds .5 seconds 2500 milliseconds 5-760 GMR-01 68P02901W23-P 23 Feb 2004 .1 second 100 milliseconds .. 25 2. .5 seconds 6553500 milliseconds 25 2. . .. . . the 2 Mbit/s circuit is taken Out Of Service (OOS).. Technical Description BSS Command Reference sync_time_restore sync_time_restore Description The sync_time_restore parameter specifies the synchronization loss restorable time period. 60 seconds .5 seconds 0 milliseconds 100 milliseconds 200 milliseconds 600 60 seconds 60000 milliseconds 60000 milliseconds 6553500 milliseconds 5-761 GMR-01 ...... the 2 Mbit/s circuit is brought back in service.. 600 .. 65535 0 seconds 0.. 6553.2 seconds . If synchronization returns for this period. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required No Dependencies None Syntax Change command string chg_element sync_time_restore <value> <location> <cell_desc> Display command string disp_element sync_time_restore <location> <cell_desc> Values Value type Integer (1 step = 100 milliseconds) Valid range 00 to 65535 Default value 68P02901W23-P 23 Feb 2004 0 1 2 .1 seconds 0. Operator actions None BSS software processes using this parameter are notified immediately the change is made. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required Yes Dependencies The GPRS feature must be unrestricted.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 Change command strings chg_element t_avg_t <value> <location> <cell_desc> chg_cell_element t_avg_t <value> <cell_desc> Display command string disp_element t_avg_t <location> <cell_desc> Values Value type Integer (multiframes) Valid range 0 to 25 Default value 10 5-762 GMR-01 68P02901W23-P 23 Feb 2004 . Syntax Change command strings chg_element t_avg_w <value> <location> <cell_desc> chg_cell_element t_avg_w <value> <cell_desc> Display command string disp_element t_avg_w <location> <cell_desc> Values Value type Integer (multiframes) Valid range 0 to 25 Default value 10 68P02901W23-P 23 Feb 2004 5-763 GMR-01 . Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required Yes Dependencies The GPRS feature must be unrestricted.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). Operator actions: None BSS software processes using this parameter are notified immediately the change is made. Type A (no operator actions) Supported by OMC-R GUI No Cell numbers required No Dependencies This parameter must be greater than or equal to tch_busy_norm_threshold. This parameter is expressed as a percentage. The flow control procedure initiates when the percentage of busy TCHs is equal to or greater than the value entered for this parameter. Syntax Change command string chg_element tch_busy_critical_threshold <value> <location> Display command string disp_element tch_busy_critical_threshold <location> Values Value type Integer (percent of busy TCHs) Valid range 81 to 100 Default value 100 5-764 GMR-01 68P02901W23-P 23 Feb 2004 . The two classes that are barred are selected randomly.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. Syntax Change command string chg_element tch_busy_norm_threshold <value> <location> Display command string disp_element tch_busy_norm_threshold <location> Values Value type Integer (percent of busy TCHs) Valid range 0 to 100 Default value 100 68P02901W23-P 23 Feb 2004 5-765 GMR-01 . Type A (no operator actions) Supported by OMC-R GUI No Cell numbers required No Dependencies This parameter must be less than or equal to tch_busy_critical_threshold. This parameter is expressed as a percentage. The class that is barred is selected randomly.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 flow control procedure initiates when the percentage of busy TCHs is equal to or greater than the value entered for this parameter. at which the Congestion Relief procedure is initiated. Syntax Change command string chg_element tch_congest_prevent_thres <value> <location> <cell_desc> Display command string disp_element tch_congest_prevent_thres <location> <cell_desc> Values Value type Integer (percent) Valid range 1 to 101 (The value 101 indicates there are no resources left to allocate). This parameter is expressed as a percentage.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. 5-766 GMR-01 68P02901W23-P 23 Feb 2004 . Default value 100 (The value 100 indicates an attempt to use the last resource). This parameter must be greater than or equal to mb_tch_congest_thres. Type A (no operation actions) Supported by OMC-R GUI Yes Cell description required Yes Dependencies The Congestion Relief feature must be enabled. or ssm_normal_overload_threshold. Other parameters can affect flow control. 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. Refer to ccch_load_period. rach_load_period. rach_load_threshold. ssm_critical_overload_threshold. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required Yes Dependencies None Syntax Change command strings chg_element tch_flow_control <value> <location> <cell_desc> chg_cell_element tch_flow_control <value> <cell_desc> Display command string disp_element tch_flow_control <location> <cell_desc> Values Value type Boolean Valid range 0 or 1 68P02901W23-P 23 Feb 2004 5-767 GMR-01 .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 reduction in traffic is achieved by barring access classes and manipulating the tx_integer and max_retran parameters. tch_flow_control Chapter 5: CM database parameters Default value 0 Disabled 1 Enabled 0 5-768 GMR-01 68P02901W23-P 23 Feb 2004 . Syntax Change command strings chg_element tch_full_need_low_water_mark <value> <location> <cell_desc> chg_cell_element tch_full_need_low_water_mark <value> <cell_desc> Display command strings disp_cell <cell_desc> ["full"] disp_element tch_full_need_low_water_mark <location> <cell_desc> 68P02901W23-P 23 Feb 2004 5-769 GMR-01 . For a TCH to be reconfigured.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. If the total number of idle SDCCHs falls below the value of the sdcch_need_low_water_mark. This parameter specifies the minimum number of TCHs the system attempts to maintain when dynamic reconfiguration is enabled. the CRM tries to reconfigure TCHs in order to make more SDCCHs. the number of TCHs must be greater than the value of the tch_full_need_low_water_mark parameter. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required Yes Dependencies channel_reconfiguration_switch feature must be enabled. tch_full_need_low_water_mark Chapter 5: CM database parameters Values Value type Integer (number of channels) Valid range 0 to 255 Default value 255 5-770 GMR-01 68P02901W23-P 23 Feb 2004 . the MS reselects the cell with the highest C2 value. C2 is the reselection priority assigned to a cell which can be broadcast on the BCCH of each cell.08. Syntax Add/Change command strings add_cell <gsm_cell_id> <location> chg_element temporary_offset <value> <location> <cell_desc> chg_cell_element temporary_offset <value> <cell_desc> Display command strings disp_cell <cell_desc> ["full"] disp_element temporary_offset <location> <cell_desc> Values Value type Integer (1 Step = 10 dB) Valid range 0 to 7 Default value 0 68P02901W23-P 23 Feb 2004 5-771 GMR-01 . It is used to apply a negative offset to C2 for the duration of the penalty_time timer parameter. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required Yes Dependencies The cell_reselect_param_ind parameter must be enabled. When more than one cell is available for reselection.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 5-772 GMR-01 68P02901W23-P 23 Feb 2004 .08 Table 10.temporary_offset Chapter 5: CM database parameters References GSM parameter C2 GSM specification TS GSM 4.5.2.32a section 10.35 TS GSM 5. ) Valid range 0 to 255 Default value 7 68P02901W23-P 23 Feb 2004 5-773 GMR-01 .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. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required Yes Dependencies None Syntax Change command strings chg_element threshold <value> <location> <cell_desc> chg_cell_element threshold <value> <cell_desc> Display command strings disp_cell <cell_desc> ["full"] disp_element threshold <location> <cell_desc> Values Value type Integer (number of assign attempts. The interval should be greater than or equal to (n8 . Where: • x equals: 1 (lower threshold of RXLEV). or 4 (upper threshold of RXQUAL).p8 + 1) x hreqavex/2. 2 (upper threshold of RXLEV). • p equals the values assigned for decision_1_py where y is a value from 1 to 4. 3 (lower threshold of RXQUAL). n8. p8 Syntax Add/Change command strings add_cell <gsm_cell_id> <location> chg_element timing_advance_period <value> <location> <cell_desc> chg_cell_element timing_advance_period <value> <cell_desc> 5-774 GMR-01 68P02901W23-P 23 Feb 2004 . • hreqave is the number of measurements from the MS that are used in calculating one average.timing_advance_period Chapter 5: CM database parameters timing_advance_period Description The timing_advance_period parameter specifies the interval between timing advance changes. • n equals the values assigned for decision_1_ny where y is a value from 1 to 4. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required Yes Dependencies hreqave. Technical Description BSS Command Reference timing_advance_period Display command strings disp_cell <cell_desc> ["full"] disp_element timing_advance_period <location> <cell_desc> Values Value type Integer Valid range 0 to 31 Mapped to SACCH multiframes: 0 1 2 ... ... 31 0 SACCH multiframes 2 SACCH multiframes 4 SACCH multiframes .. 62 SACCH multiframes 4 8 SACCH multiframes Default value 68P02901W23-P 23 Feb 2004 5-775 GMR-01 ... ..... . .. 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. 1 Use the commanded coding scheme for all blocks.tlli_blk_coding Chapter 5: CM database parameters tlli_blk_coding {23658} 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). and MCS1 for EGPRS TBFs for TLLI blocks. Type A (no operator actions) Supported by OMC-R GUI Yes Cell description required Yes Dependencies The GPRS feature must be unrestricted. Default value 5-776 GMR-01 68P02901W23-P 23 Feb 2004 . Syntax Change command strings chg_element tlli_blk_coding <value> <location> <cell_desc> chg_cell_element tlli_blk_coding <value> <cell_desc> Display command strings disp_cell <cell_desc> ["full"] disp_element <location> <cell_desc> Values Value type Boolean Valid range 0 Always use CS1 for GPRS TBFs for TLLI blocks. Abis and/or MS Power control data are specified. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required No Dependencies This parameter is used only when handover records are requested and RSS.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. Syntax Change command strings chg_element trace_msgs_after_ho <value> 0 Display command string disp_element trace_msgs_after_ho 0 Values Value type Integer (number of messages to be collected after a handover) Valid range 0 to 8 Default value 5 68P02901W23-P 23 Feb 2004 5-777 GMR-01 . This parameter applies only to the BSC. 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. Abis and/or MS Power control data are specified. This parameter applies only to the BSC. Syntax Change command strings chg_element trace_msgs_before_ho <value> 0 Display command string disp_element trace_msgs_before_ho 0 Values Value type Integer (number of messages to be collected before a handover) Valid range 0 to 8 Default value 5 5-778 GMR-01 68P02901W23-P 23 Feb 2004 . Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required No Dependencies This parameter is used only when handover records are requested and RSS. When equipping an MSI GDP. the user also has the option of equipping it as GDP_2E1. • Cage number. the user is prompted for the following parameters: • First MSI identifier. • Transcoding capability. Display command string disp_equipment 0 MSI <msi_id> 68P02901W23-P 23 Feb 2004 5-779 GMR-01 . A GDP2 with transcoding capability of GDP_2E1 has two MMS. Syntax Change command strings modify_value 0 trans_capability <value> MSI <msi_id> equip 0 MSI After entering the equip MSI command. • MSI ID to the MSC.Technical Description BSS Command Reference trans_capability trans_capability {4415} Description The trans_capability parameter specifies the transcoding capability of an MSI type GDP or GDP2. • MSI type. Type A (no operator actions) Supported by OMC-R GUI Yes Cell description required No Dependencies A GDP2 is required for the transcoding capability of GDP_2E1. the user is prompted to equip it as either basic or enhanced. • Slot number. When equipping an MSI GDP2. trans_capability Chapter 5: CM database parameters Values Value type Integer Valid range 0 to 2 Default value 0 Basic 1 Enhanced 2 GDP-2E1 None 5-780 GMR-01 68P02901W23-P 23 Feb 2004 . The value of this parameter is a percentage of total trunk capacity. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required No Dependencies This parameter must be greater than the value assigned to the trunk_major_threshold parameter unless both values are set to 0.Technical Description BSS Command Reference trunk_critical_threshold trunk_critical_threshold Description The trunk_critical_threshold parameter specifies the severity assignment of certain alarms. 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. This parameter applies only to the BSC. A trunk_critical_threshold value of 0 insures that Critical is always the severity assignment if there is any capacity loss. A critical alarm is assigned when the percentage of trunk capacity loss exceeds the trunk_critical_threshold parameter value. Syntax Change command string chg_element trunk_critical_threshold <value> 0 Display command string disp_element trunk_critical_threshold 0 Values Value type Integer (percent of trunk capacity) Valid range 0 to 100 Default value 50 68P02901W23-P 23 Feb 2004 5-781 GMR-01 . The value of this parameter is a percentage of total trunk capacity. This parameter applies only to the BSC. A minor alarm is assigned when the percentage of trunk capacity loss is less than the trunk_major_threshold parameter value.trunk_major_threshold Chapter 5: CM database parameters trunk_major_threshold Description The trunk_major_threshold parameter specifies the severity assignment of certain alarms. 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. Syntax Change command string chg_element trunk_major_threshold <value> 0 Display command string disp_element trunk_major_threshold 0 Values Value type Integer (percent of trunk capacity) Valid range 0 to 99 Default value 10 5-782 GMR-01 68P02901W23-P 23 Feb 2004 . Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required No Dependencies This parameter must be less than the value assigned to the trunk_critical_threshold parameter unless both values are set to 0. it affects the way timeslots are allocated for subsequently equipped devices. This parameter applies only to the BSC. 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.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). Syntax Change command string chg_element ts_alloc_flag <value> 0 Whenever the ts_alloc_flag is modified the system displays this message: COMMAND ACCEPTED: WARNING: This element only has effect on links to a TS_SWITCH Display command string disp_element ts_alloc_flag 0 Values Value type Boolean Valid range 0 or 1 Default value 68P02901W23-P 23 Feb 2004 0 Use existing algorithm 1 Use new algorithm 0 5-783 GMR-01 . Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required No Dependencies This parameter cannot be altered unless the Aggregate Abis feature is enabled. Syntax Change command strings chg_element ts_in_usf_active <value> <location> <cell_desc> chg_cell_element ts_in_usf_active <value> <cell_desc> Display command strings disp_element ts_in_usf_active <location> <cell_desc> Values Value type Integer (number of non-BCCH timeslots) Valid range 0 to 3 Default value 1 5-784 GMR-01 68P02901W23-P 23 Feb 2004 . The number of non-BCCH timeslots that will broadcast continuously at full power even when no mobile is active on that timeslot. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required Yes Dependencies The EOP feature must be unrestricted.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. Syntax Change command string chg_element tsc_update_method <value> 0 Display command string disp_element tsc_update_method 0 Values Value type Integer Valid range 0 to 2 68P02901W23-P 23 Feb 2004 0 Update the BCCH/CCCH timeslots 1 Update all timeslots on the BCCH carrier 5-785 GMR-01 . • Update all timeslots on the BCCH carrier. This parameter applies only to the BSC. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required No Dependencies No RTS are equipped (tsc_update_method must first be set before RTFs can be equipped in the script).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. Equip RTF verifies the TSC values based on this setting. The available methods are: • Update the BCCH/CCCH timeslots. • Update all timeslots on all carriers of cell. tsc_update_method Chapter 5: CM database parameters 2 Default value Update all timeslots on all carriers of cell 0 5-786 GMR-01 68P02901W23-P 23 Feb 2004 . Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required Yes Dependencies None Syntax Add/Change command strings add_cell <gsm_cell_id> <location> chg_element tx_integer <value> <location> <cell_desc> chg_cell_element tx_integer <value> <cell_desc> Display command strings disp_cell <cell_desc> ["full"] disp_element tx_integer <location> <cell_desc> 68P02901W23-P 23 Feb 2004 5-787 GMR-01 .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. 2.2.36.8.17 .08 .5. 10.7 cell description . and table 10.1: request for resources by the MS 4.20 .10.tx_integer Chapter 5: CM database parameters Values Value type Integer Valid range 0 to 15 Represents RACH slots as shown below: Default value 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 4 References GSM parameter TX_INTEGER GSM specification 4.1.3.number of slots spread trans 5-788 GMR-01 68P02901W23-P 23 Feb 2004 .08 .fig.30 12.5.3. Operator actions Lock the associated DRIs before attempting to change this parameter. the frequency must be DCS1800. and PCS1900 provided that the cell is a Dual Band Cell.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. EGSM. there can be no DRIs equipped for that cell. All DCS1800 DRI devices in Horizon II macro or Horizon II macro extension cabinets are forced to operate in high power mode (32 watts). Syntax Change command strings chg_element tx_power_cap <value> <location> <cell_desc> chg_cell_element tx_power_cap <value> <cell_desc> Display command strings disp_cell <cell_desc> ["full"] disp_element tx_power_cap <location> <cell_desc> 68P02901W23-P 23 Feb 2004 5-789 GMR-01 . For a PCS 1900 cell residing on a Horizonmacro or Horizonmacro extension cabinet. This parameter is valid only at DCS1800 and PCS1900 sites. The system does not accept this parameter if the associated DRIs are unlocked. Type B (operator actions required) Supported by OMC-R GUI Yes Cell description required Yes Dependencies This parameter is valid only if the transceivers at the site are inactive. If the cell is not. or PCS1900 to change tx_power_cap. If a DRI has already been equipped. any change of that element is disallowed. 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. DCS1800. tx_power_cap Chapter 5: CM database parameters Values Value type Boolean Valid range 0 or 1 Default value 0 Low power 1 High power 0 5-790 GMR-01 68P02901W23-P 23 Feb 2004 . as shown below: 5-791 GMR-01 . Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required Yes Dependencies This parameter is used by the BSS only when interfer_ho_allowed = 1. Syntax Add/Change command strings add_cell <gsm_cell_id> <location> chg_element u_rxlev_dl_ih <value> <location> <cell_desc> chg_cell_element u_rxlev_dl_ih <value> <cell_desc> Display command strings disp_cell <cell_desc> ["full"] disp_element u_rxlev_dl_ih <location> <cell_desc> Values Value type Integer (1 step = 1 dBm) Valid range 0 to 63 68P02901W23-P 23 Feb 2004 Represents -110 dBm to -47 dBm.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. .. -47 dBm 45 -65 dBm References GSM parameter RXLEV_DL_IH GSM specification 5. 63 -110 dBm -109 dBm -108 dBm ......Table 1 5-792 GMR-01 68P02901W23-P 23 Feb 2004 .08 .Appendix A .u_rxlev_dl_ih Chapter 5: CM database parameters Default value 0 1 2 ..... . . . .. as shown below: 5-793 GMR-01 . Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required Yes Dependencies None Syntax Add/Change command strings add_cell <gsm_cell_id> <location> chg_element u_rxlev_dl_p <value> <location> <cell_desc> chg_cell_element u_rxlev_dl_p <value> <cell_desc> Display command strings disp_cell <cell_desc> ["full"] disp_element u_rxlev_dl_p <location> <cell_desc> Values Value type Integer (1 step = 1 dBm) Valid range 0 to 63 68P02901W23-P 23 Feb 2004 Represents -110 dBm to -47 dBm.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. .. .... 63 -110 dBm or lower -109 dBm -108 dBm ...... .u_rxlev_dl_p Chapter 5: CM database parameters Default value 0 1 2 . -47 dBm or higher 40 -70 dBm References GSM parameter U_RXLEV_DL_P GSM specification 5.. ..Appendix A .Table 1 5-794 GMR-01 68P02901W23-P 23 Feb 2004 .08 .. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required Yes Dependencies This parameter is used by the BSS only when interfer_ho_allowed is 1. Syntax Add/Change command strings add_cell <gsm_cell_id> <location> chg_element u_rxlev_ul_ih <value> <location> <cell_desc> chg_cell_element u_rxlev_ul_ih <value> <cell_desc> Display command strings disp_cell <cell_desc> ["full"] disp_element u_rxlev_ul_ih <location> <cell_desc> Values Value type Integer (1 step = 1 dBm) Valid range 0 to 63 68P02901W23-P 23 Feb 2004 Represents -110 dBm to -47 dBm.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. as shown below: 5-795 GMR-01 . .08 .Appendix A . 63 -110 dBm or lower -109 dBm -108 dBm ... .Table 1 5-796 GMR-01 68P02901W23-P 23 Feb 2004 ... ... .. ... -47 dBm or higher 45 -65 dBm References GSM parameter RXLEV_UL_IH GSM specification 5.u_rxlev_ul_ih Chapter 5: CM database parameters Default value 0 1 2 ... as shown below: 5-797 GMR-01 .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. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required Yes Dependencies None Syntax Add/Change command strings add_cell <gsm_cell_id> <location> chg_element u_rxlev_ul_p <value> <location> <cell_desc> chg_cell_element u_rxlev_ul_p <value> <cell_desc> Display command strings disp_cell <cell_desc> ["full"] disp_element u_rxlev_ul_p <location> <cell_desc> Values Value type Integer (1 step = 1 dBm) Valid range 0 to 63 68P02901W23-P 23 Feb 2004 Represents -110 dBm to -47 dBm. Mobile transmit power may be reduced if the MS transmit signal strength is greater than this value. .08 ...Appendix A . . .......u_rxlev_ul_p Chapter 5: CM database parameters Default value 0 1 2 .. 63 -110 dBm or lower -109 dBm -108 dBm ..Table 1 5-798 GMR-01 68P02901W23-P 23 Feb 2004 . -47 dBm or higher 40 -70 dBm References GSM parameter U_RXLEV_UL_P GSM specification 5.. .. Receive quality processing is measured using Bit Error Rate (BER) values or Quality Band (QBand) units. 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.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 type of unit is specified by the alt_qual_proc parameter. u_rxqual_dl_p should be less than l_rxqual_dl_p. Syntax Add/Change command strings add_cell <gsm_cell_id> <location> chg_element u_rxqual_dl_p <value> <location> <cell_desc> chg_cell_element u_rxqual_dl_p <value> <cell_desc> Display command strings disp_cell <cell_desc> ["full"] disp_element u_rxqual_dl_p <location> <cell_desc> 68P02901W23-P 23 Feb 2004 5-799 GMR-01 . The valid range and default values for this parameter are dependent on the type of unit that is selected. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required Yes Dependencies alt_qual_procSince better rxqual corresponds to a lower bit error rate. 01% bit error rate) If alt_qual_proc = 0 0 to 7 QBand units If alt_qual_proc = 1 28 BER If alt_qual_proc = 0 1 QBand units If alt_qual_proc = 1 Default value References GSM parameter U_RXQUAL_DL_P GSM specification 5.u_rxqual_dl_p Chapter 5: CM database parameters Values Value type Integer Valid range 0 to 1810 BER (1 step = 0.08 .Table 1 5-800 GMR-01 68P02901W23-P 23 Feb 2004 .Appendix A . If alt_qual_proc = 0 0 QBand units. If alt_qual_proc = 1 14 BER. This parameter is prompted when alt_qual_proc is changed.Technical Description BSS Command Reference u_rxqual_dl_p_amr_hr u_rxqual_dl_p_amr_hr {4322} Description The u_rxqual_dl_p_amr_hr parameter specifies the power control threshold for the best allowed downlink received quality (rxqual). This parameter can be changed only at an AMR-capable BTS site. If alt_qual_proc = 1 Default value 68P02901W23-P 23 Feb 2004 5-801 GMR-01 .01% bit error rate). Syntax Add/Change command strings chg_element u_rxqual_dl_p_amr_hr <value> <location> <cell_desc> chg_cell_element u_rxqual_dl_p_amr_hr <value> <cell_desc> Display command strings disp_cell <cell_desc> "full" disp_element u_rxqual_dl_p_amr_hr <location> <cell_desc> Values Value type Integer Valid range 0 to 1810 BER (1 step = 0. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required Yes Dependencies The AMR feature must be unrestricted. If alt_qual_proc = 0 0 to 7 QBand units. An Rxqual value better (lower BER rate) than what is specified by the u_rxqual_ul_p parameter may result the reduction of MS power. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required Yes Dependencies alt_qual_procSince better rxqual corresponds to a lower bit error rate.u_rxqual_ul_p Chapter 5: CM database parameters u_rxqual_ul_p Description The u_rxqual_ul_p parameter sets the power control threshold for the best allowed uplink receive quality (rxqual). u_rxqual_ul_p must be less than l_rxqual_ul_p. Syntax Add/Change command strings add_cell <gsm_cell_id> <location> chg_element u_rxqual_ul_p <value> <location> <cell_desc> chg_cell_element u_rxqual_ul_p <value> <cell_desc> Display command strings disp_cell <cell_desc> ["full"] disp_element u_rxqual_ul_p <location> <cell_desc> Values Value type Integer Valid range 0 to 1810 BER (1 step = 0.01% bit error rate) 5-802 GMR-01 If alt_qual_proc = 0 68P02901W23-P 23 Feb 2004 . The type of unit is specified by the alt_qual_proc parameter. Receive quality processing is measured using Bit Error Rate (BER) values or Quality Band (QBand) units. The valid range and default values for this parameter are dependent on the type of unit that is selected. Appendix A .08 .Table 1 68P02901W23-P 23 Feb 2004 5-803 GMR-01 .Technical Description BSS Command Reference Default value u_rxqual_ul_p 0 to 7 QBand units If alt_qual_proc = 1 28 BER If alt_qual_proc = 0 1 QBand units If alt_qual_proc = 1 References GSM parameter U_RXQUAL_UL_P GSM specification 5. If alt_qual_proc = 0 0 to 7 QBand units. If alt_qual_proc = 1 14 BER. This parameter is prompted when alt_qual_proc is changed. Syntax Add/Change command strings chg_element u_rxqual_ul_p_amr_hr <value> <location> <cell_desc> chg_cell_element u_rxqual_ul_p_amr_hr <value> <cell_desc> Display command strings disp_cell <cell_desc> "full" disp_element u_rxqual_ul_p_amr_hr <location> <cell_desc> Values Value type Integer Valid range 0 to 1810 BER (1 step = 0. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required Yes Dependencies The AMR feature must be unrestricted.u_rxqual_ul_p_amr_hr Chapter 5: CM database parameters u_rxqual_ul_p_amr_hr {4322} Description The u_rxqual_ul_p_amr_hr parameter specifies the power control threshold for the best allowed uplink received quality (rxqual). If alt_qual_proc = 1 Default value 5-804 GMR-01 68P02901W23-P 23 Feb 2004 . This parameter can be changed only at an AMR-capable BTS site. If alt_qual_proc = 0 0 QBand units.01% bit error rate). The GDP firmware controls the volume level by converting the audio level bits for the entered offset. Changes take effect immediately (including active calls). This parameter applies only to the BSC. The offset is in 1 dB steps with a maximum increase or decrease of 30 dB (between -15 dB and 15 dB). Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required No Dependencies The volume_control_type parameter controls the ul_audio_lev_offset application. The audio level parameters affect background and comfort noise. Syntax Change command string chg_element ul_audio_lev_offset <value> 0 Display command strings disp_element ul_audio_lev_offset 0 Values Value type Integer (1 Step = 1 dB) Valid range -15 to +15 Default value 0 68P02901W23-P 23 Feb 2004 5-805 GMR-01 . If volume_control_type = 1. The audio level parameters do not affect data.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. then the ul_audio_lev_offset parameter only applies to sites equipped with GDP boards. 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). Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required Yes Dependencies None Syntax Add/Change command strings add_cell <gsm_cell_id> <location> chg_element ul_rxlev_ho_allowed <value> <location> <cell_desc> chg_cell_element ul_rxlev_ho_allowed <value> <cell_desc> Display command strings disp_cell <cell_desc> ["full"] disp_element ul_rxlev_ho_allowed <location> <cell_desc> Values Value type Boolean Valid range 0 or 1 Default value 0 Disabled 1 Enabled 1 5-806 GMR-01 68P02901W23-P 23 Feb 2004 . 68P02901W23-P 23 Feb 2004 5-807 GMR-01 .Technical Description BSS Command Reference ul_rxlev_ho_allowed References Internal name EN_RXLEV_HO This is a Motorola parameter. 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). Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required Yes Dependencies None Syntax Add/Change command strings add_cell <gsm_cell_id> <location> chg_element ul_rxqual_ho_allowed <value> <location> <cell_desc> chg_cell_element ul_rxqual_ho_allowed <value> <cell_desc> Display command strings disp_cell <cell_desc> ["full"] disp_element ul_rxqual_ho_allowed <location> <cell_desc> Values Value type Boolean Valid range 0 or 1 Default value 0 Disabled 1 Enabled 1 5-808 GMR-01 68P02901W23-P 23 Feb 2004 . 68P02901W23-P 23 Feb 2004 5-809 GMR-01 .Technical Description BSS Command Reference ul_rxqual_ho_allowed References Internal name EN_RXQUAL_HO This is a Motorola parameter. • Sending both an alarm to the OMC-R and an “unequipped circuit" message to the MSC. Type A (no operator actions) Supported by OMC-R GUI No Cell numbers required No Dependencies This parameter does not apply to RXCDR sites. • Sending an “unequipped circuit" message to the MSC. The options are: • Sending an alarm to the OMC-R. The Phase 2 feature must be unrestricted.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. Syntax Change command string chg_element unequipped_circuit_allowed <value> 0 Display command string disp_element unequipped_circuit_allowed 0 Values Value type Integer Valid range 0 to 2 Default value 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 0 5-810 GMR-01 68P02901W23-P 23 Feb 2004 . 08 This is a Motorola defined parameter. 5-811 GMR-01 .Technical Description BSS Command Reference unequipped_circuit_allowed References GSM specification 68P02901W23-P 23 Feb 2004 TS GSM 8. these handovers use a power level derived from the rxlev reported by the MS for the target cell. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required Yes Dependencies None Syntax Change command strings chg_element use_derived_ho_power <value> <location> <cell_desc> chg_cell_element use_derived_ho_power <value> <cell_desc> Display command string disp_element use_derived_ho_power <location> <cell_desc> Values Value type Boolean Valid range 0 or 1 Default value 0 Disabled 1 Enabled 0 5-812 GMR-01 68P02901W23-P 23 Feb 2004 . When disabled. When enabled. these handovers use the power level in the database.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. 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. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required Yes Dependencies None Syntax Change command strings chg_element use_neighbor_pbgt_hreqave <value> <location> <cell_desc> chg_cell_element use_neighbor_pbgt_hreqave <value> <cell_desc> Display command string disp_element use_neighbor_pbgt_hreqave <location> <cell_desc> Values Value type Boolean Valid range 0 or 1 Default value 68P02901W23-P 23 Feb 2004 0 per cell hreqave is used 1 per neighbour hreqave is used 0 5-813 GMR-01 . when RXCDR must contain a GDP board to serve the BSS. The effect depends on the equipment configuration (GDPs or DRIs equipped). by setting the parameter to 0 at the BSC and at the RXCDR.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. Syntax Change command string chg_element volume_control_type <value> 0 Display command string disp_element volume_control_type 0 5-814 GMR-01 68P02901W23-P 23 Feb 2004 . (There are no DRIs at the RXCDR). CCDSP (Channel Coding Digital Signal Processor) volume control cannot be directly initiated from an RXCDR. If volume_control_type is set to 1. 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. CCDSP (DRI) volume control is used in this BSS. the BSS must be equipped with GDP boards. Type B (operator actions required) Supported by OMC-R GUI Yes Cell numbers required No Dependencies The Generic DSP Processor (GDP) Volume Control feature must be available. This parameter applies only to the BSC. The volume can be changed at either an RXCDR or at a BSC. and the value of volume_control_type to use DRIs (0) or GDP volume control (1). The parameters ul_audio_lev_offset and dl_audio_lev_offset must be set to 0 before changing volume_control_type. However. unless remote transcoding. Values Value type Boolean Valid range 0 or 1 Default value 68P02901W23-P 23 Feb 2004 0 CCDSP Volume Control 1 GDP Volume Control 0 5-815 GMR-01 .Technical Description BSS Command Reference volume_control_type The bss_id parameter is required in both the above commands only at the RXCDR. 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. Type A (no operator actions) Supported by OMC-R GUI No Cell numbers required No Dependencies None Syntax Change command string chg_element wait_for_reselection <value> <location> Display command string disp_element wait_for_reselection <location> <location> Values Value type Integer (seconds) Valid range 0 to 86400 Default value 10 5-816 GMR-01 68P02901W23-P 23 Feb 2004 . 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 MS does not make a new request in the same cell until the timer expires. The message contains the request reference and a wait indication. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required Yes Dependencies None Syntax Add/Change command strings add_cell <gsm_cell_id> <location> chg_element wait_indication_parameters <value> <location> <cell_desc> chg_cell_element wait_indication_parameters <value> <cell_desc> Display command strings disp_cell <cell_desc> ["full"] disp_element wait_indication_parameters <location> <cell_desc> Values Value type Integer (seconds) Valid range 0 to 255 Default value 5 68P02901W23-P 23 Feb 2004 5-817 GMR-01 . 2: assignment rejection 4.3.37 4. and table 10. .08 .7.5.2.7 .10.08 .1: 12.3.1. figure 10.5.24.1.Wait Indication This is a Motorola defined parameter.43.wait_indication_parameters Chapter 5: CM database parameters References GSM specification 4.2.11.20 . 5-818 GMR-01 68P02901W23-P 23 Feb 2004 .2.08. This parameter affects only handovers due to downlink receive level.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. Type A (no operator actions) Supported by OMC-R GUI Yes Cell description required Yes Dependencies None Syntax Change command strings chg_element worse_neighbor_ho <value> <location> <cell_desc> chg_cell_element worse_neighbor_ho <value> <cell_desc> Display command string disp_element worse_neighbor_ho <location> <cell_desc> Values Value type Boolean Valid range 0 or 1 Default value 68P02901W23-P 23 Feb 2004 0 Handover disabled 1 Handover enabled 0 5-819 GMR-01 . • Not Dual Band: 0 to 30.BS_TXPWR_MAX_INNER) or (RXLEV_UL > RXLEV_UL_ZONE + ZONE_HO_HYST + (MS_TXPWR .MS_TXPWR_MAX_INNER)). 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 . Type A (No operator actions required) Supported by OMC-R GUI Yes Cell description required Yes Dependencies The Concentric Cells feature must be unrestricted. The range depends on the value of inner_zone_alg: • Dual Band Cell: -63 to 63. The system uses this value to determine whether an outer-zone to inner-zone handover should take place. Syntax Change command strings chg_element zone_ho_hyst <value> <location> <cell_desc> chg_cell_element <location> zone_ho_hyst <value> <cell_desc> Display command strings disp_cell <cell_desc> ["full"] disp_element zone_ho_hyst <location> <cell_desc> 5-820 GMR-01 68P02901W23-P 23 Feb 2004 .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. 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-P 23 Feb 2004 5-821 GMR-01 . This parameter can only be modified at the BSC. Type A (No operator actions required) Supported by OMC-R GUI No Cell description required No Dependencies None Syntax Change command strings chg_element zone_pingpong_count <value> 0 Display command strings disp_element zone_pingpong_count 0 Values Value type Integer Valid range 0 to 255 Default value 3 5-822 GMR-01 68P02901W23-P 23 Feb 2004 . This parameter can be changed when the user is in RAM or Sysgen mode.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_pingpong_enable_win parameter. Type A (No operator actions required) Supported by OMC-R GUI No Cell description required No Dependencies None Syntax Change command strings chg_element zone_pingpong_disable_win <value> 0 Display command strings disp_element zone_pingpong_disable_win 0 Values Value type Integer Valid range 0 to 255 Default value 30 68P02901W23-P 23 Feb 2004 5-823 GMR-01 .Technical Description BSS Command Reference zone_pingpong_disable_win zone_pingpong_disable_win Description The zone_pingpong_disable_win parameter sets the time window in which ping-pong handovers between zones are not allowed. This parameter can be changed when the user is in RAM or Sysgen mode. This parameter can only be modified at the BSC. zone_pingpong_enable_win Chapter 5: CM database parameters zone_pingpong_enable_win Description The zone_pingpong_enable_win parameter sets the time window in which ping-pong handovers between zones are continuously allowed. This parameter can be changed when the user is in RAM or Sysgen mode. Type A (No operator actions required) Supported by OMC-R GUI No Cell description required No Dependencies None Syntax Change command strings chg_element zone_pingpong_enable_win <value> 0 Display command strings disp_element zone_pingpong_enable_win 0 Values Value type Integer Valid range 0 to 255 Default value 30 5-824 GMR-01 68P02901W23-P 23 Feb 2004 . This parameter can only be modified at the BSC. This parameter can only be modified at the BSC.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. 1 or 255 Default value 255 68P02901W23-P 23 Feb 2004 5-825 GMR-01 . This parameter can be changed when the user is in RAM or Sysgen mode. Type A (No operator actions required) Supported by OMC-R GUI No Cell description required No Dependencies None Syntax Change command strings chg_element zone_pingpong_preferred_zone <value> 0 Display command strings disp_element zone_pingpong_preferred_zone 0 Values Value type Integer Valid range 0. 5-826 GMR-01 68P02901W23-P 23 Feb 2004 .zone_pingpong_preferred_zone Chapter 5: CM database parameters This page intentionally left blank. whether supported by OMC-R GUI. Values .giving the change command and display command strings using the particular timer parameter. and listing any dependencies affecting the timer.Chapter 6 Timer parameters Timer parameters are BSS parameters that can be displayed and changed using MMI commands. For more information about BSS timers. The timer descriptions are in alphabetical order as listed in the Contents section of this manual. and indicates the command syntaax used to modify or display the parameter. This chapter contains descriptions of the timer parameters used in the BSS . Description .providing a description of the timer operation. The timers are used to monitor and set timer guards for the various software processes in the BSS.giving any related information such as internal name. refer to the Maintenance Information: BSS Timers (68P02901W58) manual.giving the value type. Each timer parameter is described separately using the following presentation layout: Parameter reference . References . whether cell numbers are required. valid range and the default value for the particular timer parameter. and including information on the parameter type. GSM name and ITU/GSM specification where applicable.showing the timer parameter reference title. 68P02901W23-P 23 Feb 2004 6-1 GMR-01 . Syntax . 6-2 GMR-01 68P02901W23-P 23 Feb 2004 .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. Type A (no operator actions) Supported by OMC-R GUI No Cell numbers required No Dependencies None Syntax Change command string chg_element add_access_class <value> <location> Display command string disp_element add_access_class <location> Values Value type Integer (milliseconds) Valid range 0 to 1000000 Default value 60000 References Internal name MTCRM_ADD_ACC_CLASS This is a Motorola defined timer. In all cases. If this timer expires. The reason for this is that the assignment procedure fails when the assign_successful timer expires. This timer starts when the BSC sends an assignment command to the BTS. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required No Dependencies None Syntax Change command string chg_element assign_successful <value> <location> Display command string disp_element assign_successful <location> Values Value type Integer (milliseconds) Valid range 0 to 1000000 Default value 30000 68P02901W23-P 23 Feb 2004 6-3 GMR-01 . the bssmap_t11 timer must be less than the assign_successful timer.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. the call terminates. The bssmap_t11 timer controls how long a call remains queued when waiting for a resource. 6-4 GMR-01 68P02901W23-P 23 Feb 2004 .assign_successful Chapter 6: Timer parameters References Internal name SSM_MTN This is a Mororola defined timer. This TBF is created through the auto downlink mechanism which is waiting for new downlink data to arrive. One block period equals 20 ms. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required No Dependencies The GPRS feature must be unrestricted.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. Syntax Change command string chg_element auto_dl_dur <value> <location> Display command string disp_element auto_dl_dur <location> Values Value type Integer (20 ms block periods) Valid range 15 to 250 Default value 50 68P02901W23-P 23 Feb 2004 6-5 GMR-01 . 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. Type A (no operator actions) Supported by OMC-R GUI No Cell numbers required No Dependencies None Syntax Change command string chg_element bcch_info <value> <location> Display command string disp_element bcch_info <location> Values Value type Integer (milliseconds) Valid range 0 to 10000 Default value 2000 6-6 GMR-01 68P02901W23-P 23 Feb 2004 . The information message is sent immediately if all necessary BCCH system information messages are received depending on the mode being used. 08 .section 9.34 .1.Technical Description BSS Command Reference bcch_info References Internal name TM_BCCH_INFO GSM specification TS GSM 04. This is a Motorola defined timer 68P02901W23-P 23 Feb 2004 6-7 GMR-01 . Type A (no operator actions) Supported by OMC-R GUI Yes Cell description required Yes Dependencies The EGPRS feature must be unrestricted. Syntax Change command strings chg_element bep_period <value> <location> <cell_desc> chg_cell_element bep_period <value> <cel_desc> Display command strings disp_cell <cell_desc> ["full"] disp_element bep_period <location> <cell_desc> 6-8 GMR-01 68P02901W23-P 23 Feb 2004 . A BSS software process is notified whenever the bep_period element value is changed.bep_period Chapter 6: Timer parameters bep_period {23658} 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. 6-9 GMR-01 .Technical Description BSS Command Reference bep_period Values Value type Integer (BEP filter averaging period) Valid range 0 to 10 Default value 0 68P02901W23-P 23 Feb 2004 Eliminates forgetting factor ’e’ from channel quality measurement algorithms executed by the MS. This parameter. if sent. or the mobile station leaves the cell or the MS enters packet idle mode. Type A (no operator actions) Supported by OMC-R GUI Yes Cell description required Yes Dependencies The EGPRS feature must be unrestricted. is used by the mobile station in the cell. until a new bep_period2 is received by the mobile station in the same cell. Syntax Change command strings chg_element bep_period2 <value> <location> <cell_desc> chg_cell_element bep_period2 <value> <cel_desc> Display command strings disp_cell <cell_desc> ["full"] disp_element bep_period2 <location> <cell_desc> Values Value type Integer (Secondary BEP filter averaging period) Valid range 0 to 15 Default value 15 Allows normal filtering 6-10 GMR-01 68P02901W23-P 23 Feb 2004 . The bep_period2 parameter is a forgetting factor for the mobile station to use when filtering the Bit Error Probability.bep_period2 Chapter 6: Timer parameters bep_period2 {23658} 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. Type A (no operator actions) Supported by OMC-R GUI Yes Cell description required Yes Dependencies None Syntax Change command strings chg_element bounce_protect_cong_tmr <value> <location> <cell_desc>chg_cell_element bounce_protect_cong_tmr <value> <cell_desc> Display command string disp_element bounce_protect_cong_tmr <location> <cell_desc> Values Value type Integer (SACCH periods) Valid range 0 to 255 Default value 68P02901W23-P 23 Feb 2004 0 Disabled 1 to 255 SACCH periods 0 6-11 GMR-01 .Technical Description BSS Command Reference bounce_protect_cong_tmr bounce_protect_cong_tmr Description The bounce_protect_cong_tmr timer specifies the number of SACCH periods after a congestion handover that the system applies the bounce_protect_margin value. This timer helps to prevent continuous handover bouncing between cells due to congestion. Type A (no operator actions) Supported by OMC-R GUI Yes Cell description required Yes Dependencies None Syntax Change command strings chg_element bounce_protect_qual_tmr <value> <location> <cell_desc> chg_cell_element bounce_protect_qual_tmr <value> <cell_desc> Display command string disp_element bounce_protect_qual_tmr <location> <cell_desc> Values Value type Integer (representing SACCH periods) Valid range 0 to 127 Default value 0 disabled 1 to 127 SACCH periods 0 6-12 GMR-01 68P02901W23-P 23 Feb 2004 .bounce_protect_qual_tmr Chapter 6: Timer parameters 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. Technical Description BSS Command Reference bsc_audit 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. 68P02901W23-P 23 Feb 2004 6-13 GMR-01 . the BSC sends an audit message to the BTS. Type A (no operator actions) Supported by OMC-R GUI No Cell numbers required No Dependencies Must be greater than bts_audit Syntax Change command string chg_element bsc_audit <value> <location> Display command string disp_element bsc_audit <location> Values Value type Integer (milliseconds) Valid range 0 to 1000000 Default value 120000 References Internal name SSM_MTV This is a Motorola defined parameter. If this timer expires. This timer starts when the BSC sends an audit message to the BTS. Type A (no operator actions) Supported by OMC-R GUI No Cell numbers required No Dependencies None Syntax Change command string chg_element bsc_audit_response <value> <location> Display command string disp_element bsc_audit_response <location> Values Value type Integer (milliseconds) Valid range 0 to 1000000 Default value 30000 References Internal name SSMAUDIT_TIMER This is a Motorola defined parameter.bsc_audit_response Chapter 6: Timer parameters bsc_audit_response Description The bsc_audit_response timer specifies the wait time for audit ssm call response from RRSM timer. 6-14 GMR-01 68P02901W23-P 23 Feb 2004 . If the bsc_audit_response timer expires a specified number of times in a row without receiving a response from the BTS. The num_audit_retries parameter specifies the number of timer expirations. the BSC clears the call. the BSS may violate the repetition rate defined by the C value. 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. When the timer expires. Type A (no operator actions) Supported by OMC-R GUI No Cell numbers required No Dependencies The GPRS feature must be unrestricted.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. 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. this parameter can be modified without a reset to a particular device or function. the BSS may send another Flow Control PDU if the condition which caused the sending of the PDU still exists. Syntax Change command string chg_element bssgp_fc_period_c <value> <location> Display command string disp_element bssgp_fc_period_c <location> 68P02901W23-P 23 Feb 2004 6-15 GMR-01 . In this case. That is. BSS software processes using this parameter are not notified when the change is made. The BSS may send a new Flow Control PDU every C seconds. 6-16 GMR-01 68P02901W23-P 23 Feb 2004 .bssgp_fc_period_c Chapter 6: Timer parameters Values Value type Integer (tenths of a second) Valid range 1 to 1000 1 0.3.2.18 .1 seconds 100 milliseconds 10 1 second 1000 milliseconds 1000 100 seconds 100000 milliseconds Default value 10 (1 second) References GSM specification TS GSM 08.Section 8.4 This is a Motorola defined timer. This timer is set when the BSS sends a BVC-BLOCK or BVC-UNBLOCK PDU to the SGSN. That is.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. BSS software processes using this parameter are not notified when the change is made. the BVC Blocking or Unblocking procedure is repeated a maximum number of bssgp_block_retries attempts. This timer is cleared when the BVC-BLOCK or BVC-UNBLOCK-ACK PDU is received by the BSS from the SGSN. Syntax Change command string chg_element bssgp_t1_timer <value> <location> Display command string disp_element bssgp_t1_timer <location> Values Value type Integer (seconds) Valid range 1 to 120 Default value 3 68P02901W23-P 23 Feb 2004 6-17 GMR-01 . the BVC remains unblocked. After the maximum attempts fail. Type A (no operator actions) Supported by OMC-R GUI No Cell numbers required No Dependencies The GPRS feature must be unrestricted. If the timer expires before an ACK is received. this parameter can be modified without a reset to a particular device or function. 3 This is a Motorola defined timer. 6-18 GMR-01 68P02901W23-P 23 Feb 2004 .18 .bssgp_t1_timer Chapter 6: Timer parameters References Internal name BSSGP T1 GSM specification TS GSM 08.Section 8. This timer is cleared when the BVC-RESET-ACK is received by the BSS from the SGSN. the BVC Reset procedure is repeated a maximum number of bssgp_reset_retries attempts. BSS software processes using this parameter are not notified when the change is made. Type A (no operator actions) Supported by OMC-R GUI No Cell numbers required No Dependencies The GPRS feature must be unrestricted. After the maximum attempts fail. this parameter can be modified without a reset to a particular device or function. This timer is set when the BSS sends a BVC-RESET to the SGSN. That is. If the timer expires before an ACK is received.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. Syntax Change command string chg_element bssgp_t2_timer <value> <location> Display command string disp_element bssgp_t2_timer <location> Values Value type Integer (seconds) Valid range 1 to 120 Default value 60 68P02901W23-P 23 Feb 2004 6-19 GMR-01 . the BVC remains blocked. Section 8.4 This is a Motorola defined timer. 6-20 GMR-01 68P02901W23-P 23 Feb 2004 .bssgp_t2_timer Chapter 6: Timer parameters References GSM specification TS GSM 08.18 . 08 .08 .3.2.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.2 8. even if the MSC is not in a state to respond immediately. A typical value for this timer is 1000 milliseconds.3. Type A (no operator actions) Supported by OMC-R GUI No Cell numbers required No Dependencies None Syntax Change command string chg_element bssmap_t1 <value> <location> Display command string disp_element bssmap_t1 <location> Values Value type Integer (milliseconds) Valid range 0 to 1000000 Default value 30000 References Internal name CLM_T1 GSM name T1 GSM specification 8. The value set must allow enough time for the MSC to respond to a Block/Unblock.3: BSSMAP timers 68P02901W23-P 23 Feb 2004 6-21 GMR-01 .1. If this timer expires. Type A (no operator actions) Supported by OMC-R GUI No Cell numbers required No Dependencies None Syntax Change command string chg_element bssmap_t10 <value> <location> Display command string disp_element bssmap_t10 <location> Values Value type Integer (milliseconds) Valid range 0 to 1000000 Default value 28000 6-22 GMR-01 68P02901W23-P 23 Feb 2004 . This timer starts when the BTS sends an Assignment Command to the MS. The recommended value is 13000 milliseconds.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. the call is terminated. it is considered to be a timer in cascade and its value corresponds to the lowest assigned value. 3.08 .4.2. section 3.3: all RRSM timers.3.08 . 68P02901W23-P 23 Feb 2004 6-23 GMR-01 .3.08. Motorola implementation of RRSM_T10 is aligned with the implementation of T3107 as specified in TS GSM 04.Technical Description BSS Command Reference bssmap_t10 References Internal name RRSM_T10 GSM name T10 GSM specification 4.Section 11 8. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required No Dependencies Should be less than assign_successful Syntax Change command string chg_element bssmap_t11 <value> <location> Display command string disp_element bssmap_t11 <location> Values Value type Integer (milliseconds) Valid range 0 to 1000000 Default value 28000 6-24 GMR-01 68P02901W23-P 23 Feb 2004 . the call terminates. the call queues for the length of time specified by the assign_successful timer. A Clear Request message is sent to the MSC when the assign_successful timer expires.bssmap_t11 Chapter 6: Timer parameters bssmap_t11 Description The bssmap_t11 timer specifies the wait time for a queued resource request. If this timer expires. If this timer is greater than the assign_successful timer. This timer starts when the BTS attempts to queue an Assignment Request. This timer must be less than the assign_successful timer. Technical Description BSS Command Reference bssmap_t11 References Internal name RRSM_T11 GSM name T11 GSM specification 4.Section 11 8.3.08 .08 .3: all RRSM timers 68P02901W23-P 23 Feb 2004 6-25 GMR-01 .2. If this timer expires. A typical value for this timer is 1000 milliseconds. 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. Type A (no operator actions) Supported by OMC-R GUI No Cell numbers required No Dependencies None Syntax Change command string chg_element bssmap_t13 <value> <location> Display command string disp_element bssmap_t13 <location> Values Value type Integer (milliseconds) Valid range 0 to 1000000 Default value 40000 6-26 GMR-01 68P02901W23-P 23 Feb 2004 . the BSS responds to the MSC with a Reset Acknowledgement. This timer starts when the Reset message from the MSC is received at the BSS.bssmap_t13 Chapter 6: Timer parameters bssmap_t13 Description The bssmap_t13 timer specifies the wait time for the reset guard period at the BSS. 08 .3: BSSMAP timers 68P02901W23-P 23 Feb 2004 6-27 GMR-01 .2.3.Technical Description BSS Command Reference bssmap_t13 References Internal name CLM_T13 GSM parameter T13 GSM specification 8. Type A (no operator actions) Supported by OMC-R GUI No Cell numbers required No Dependencies None Syntax Change command string chg_element bssmap_t19 <value> <location> Display command string disp_element bssmap_t19 <location> Values Value type Integer (milliseconds) Valid range 0 to 1000000 Default value 30000 References Internal name CLM_T19 GSM name T19 GSM specification GSM 8. 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.08 6-28 GMR-01 68P02901W23-P 23 Feb 2004 .bssmap_t19 Chapter 6: Timer parameters bssmap_t19 Description The bssmap_t19 timer specifies the wait time for a Reset Circuit Acknowledge from the MSC. A typical value for this timer is 1000 milliseconds.08 68P02901W23-P 23 Feb 2004 6-29 GMR-01 .Technical Description BSS Command Reference bssmap_t20 bssmap_t20 Description The bssmap_t20 timer specifies the wait time for Circuit Group Blocking Ack or Circuit Group Unblocking Ack from MSC. Type A (no operator actions) Supported by OMC-R GUI No Cell numbers required No Dependencies None Syntax Change command string chg_element bssmap_t20 <value> <location> Display command string disp_element bssmap_t20 <location> Values Value type Integer (milliseconds) Valid range 0 to 1000000 Default value 30000 References Internal name CLM_T20 GSM name T20 GSM specification GSM 8. A typical value for this timer is 1000 milliseconds. it sends a Circuit Reset message and restarts the timer based on a database parameter value. Type A (no operator actions) Supported by OMC-R GUI No Cell numbers required No Dependencies None Syntax Change command string chg_element bssmap_t4 <value> <location> Display command string disp_element bssmap_t4 <location> Values Value type Integer (milliseconds) Valid range 0 to 1000000 Default value 50000 6-30 GMR-01 68P02901W23-P 23 Feb 2004 . This timer must be set to allow enough time for the BSS to recover from a global reset.bssmap_t4 Chapter 6: Timer parameters bssmap_t4 Description The bssmap_t4 timer specifies the wait time for return of the Reset Acknowledgement from MSC. If this timer expires. 3.3: BSSMAP timers 8.1.3.Technical Description BSS Command Reference bssmap_t4 References Internal name CLM_T4 GSM name T4 GSM specification 8.1: T4 68P02901W23-P 23 Feb 2004 6-31 GMR-01 .08 .2.08 .3.4.1. Type A (no operator actions) Supported by OMC-R GUI No Cell numbers required No Dependencies None Syntax Change command string chg_element bssmap_t7 <value> <location> Display command string disp_element bssmap_t7 <location> Values Value type Integer (milliseconds) Valid range 0 to 1000000 Default value 30000 6-32 GMR-01 68P02901W23-P 23 Feb 2004 . the BSC (SSM) timer bssmap_t7 guards against something going wrong at the MSC with the handover that the BSC has triggered. 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).bssmap_t7 Chapter 6: Timer parameters bssmap_t7 Description In an inter-BSS (external) handover. The BSC responds to the MSC and sets the timer to guard against non-receipt of the MSC approval to proceed with the handover. 68P02901W23-P 23 Feb 2004 6-33 GMR-01 .1: T7.3: all BSSMAP timers 8.1.5.3.2.08 .5.Technical Description BSS Command Reference bssmap_t7 References Internal name SSM_T7 GSM name T7 GSM specification 8.3.1.1. 3.08 . 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 this timer expires. This timer starts at the source BTS when it is informed of an inter-cell handover. if necessary. the BTS deallocates the old channel at the source cell.bssmap_t8 Chapter 6: Timer parameters bssmap_t8 Description The bssmap_t8 timer specifies the wait time for the receipt of a successful handover. Type A (no operator actions) Supported by OMC-R GUI No Cell numbers required No Dependencies None Syntax Change command string chg_element bssmap_t8 <value> <location> Display command string disp_element bssmap_t8 <location> Values Value type Integer (milliseconds) Valid range 0 to 1000000 Default value 28000 6-34 GMR-01 68P02901W23-P 23 Feb 2004 . 3.2.2 bss Map Timer In Bsc .7.Technical Description BSS Command Reference bssmap_t8 References Internal name RRSM_T8 GSM name T8 GSM specification 12.3: all RRSM timers 68P02901W23-P 23 Feb 2004 6-35 GMR-01 .08 .5.08 .20 .2.Section 11 8.bss Map T8: 4. bssmap_tqho Chapter 6: Timer parameters bssmap_tqho Description The bssmap_tqho timer specifies the maximum allowed queuing time for a handover request. the system starts the MTB1 timer to wait for another handover request. If this timer expires. This timer starts when the BSC queues the Handover Request. Type A (no operator actions) Supported by OMC-R GUI No Cell numbers required No Dependencies None Syntax Change command string chg_element bssmap_tqho <value> <location> Display command string disp_element bssmap_tqho <location> Values Value type Integer (milliseconds) Valid range 0 to 1000000 Default value 30000 6-36 GMR-01 68P02901W23-P 23 Feb 2004 . Technical Description BSS Command Reference bssmap_tqho References Internal name SSM_TQHO GSM name T_qho GSM technical specification GSM 8.008 68P02901W23-P 23 Feb 2004 6-37 GMR-01 . If this timer expires. Type A (no operator actions) Supported by OMC-R GUI No Cell numbers required No Dependencies This parameter must be less than bsc_audit. Syntax Change command string chg_element bts_audit <value> <location> Display command string disp_element bts_audit <location> Values Value type Integer (milliseconds) Valid range 0 to 1000000 Default value The lesser value of 60000 or the bsc_audit timer minus 1 6-38 GMR-01 68P02901W23-P 23 Feb 2004 .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. the BTS initiates the audit. This timer starts when the call is not performing any connection related processes at the BTS. 08 .2.3.08 .3: all RRSM timers This is a Motorola defined timer.Technical Description BSS Command Reference bts_audit References Internal name RRSM_MTW GSM specification 4.Section 11 8. 68P02901W23-P 23 Feb 2004 6-39 GMR-01 . 3.3: all RRSM timers 8.3.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).Section 11 8. 6-40 GMR-01 68P02901W23-P 23 Feb 2004 .08 .2.08 .1 This is a Motorola defined parameter. Type A (no operator actions) Supported by OMC-R GUI No Cell numbers required No Dependencies None Syntax Change command string chg_element bts_audit_response <value> <location> Display command string disp_element bts_audit_response <location> Values Value type Integer (milliseconds) Valid range 0 to 100000 Default value 30000 References Internal name RRSM_AUDIT_TIMER GSM specification 4.08 . Type A (no operator actions) Supported by OMC-R GUI No Cell numbers required No Dependencies The parameter is only valid for a remote BTS site. and 30 to 360 Default value 60 68P02901W23-P 23 Feb 2004 (0 indicates that the BTS does not reset due to loss of communication with the BSC) 6-41 GMR-01 .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. Syntax Change command string chg_element bts_escalation <value> <location> Display command string disp_element bts_escalation <location> Values Value type Integer (minutes) Valid range 0. the BTS deallocates the carrier. Type A (no operator actions) Supported by OMC-R GUI No Cell numbers required No Dependencies None Syntax Change command string chg_element carrier_free_immediate <value> <location> Display command string disp_element carrier_free_immediate <location> Values Value type Integer (milliseconds) Valid range 0 to 1000000 Default value 120000 6-42 GMR-01 68P02901W23-P 23 Feb 2004 . This value should be eight times greater than the value needed to free a single timeslot. If the timer expires.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 timer starts when the BTS attempts to deactivate a carrier. The timer stops when carrier deactivation is completed. 68P02901W23-P 23 Feb 2004 6-43 GMR-01 .Technical Description BSS Command Reference carrier_free_immediate References Internal name MTCRM_CARRIER_FREE_IMMEDIATE This is a Motorola defined timer. 6-44 GMR-01 68P02901W23-P 23 Feb 2004 .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. Type A (no operator actions) Supported by OMC-R GUI No Cell numbers required No Dependencies None Syntax Change command string chg_element cbch_1 <value> <location> Display command string disp_element cbch_1 <location> Values Value type Integer (milliseconds) Valid range 0 to 1000000 Default value 30000 References Internal name MTCRM_CBT1 This is a Motorola defined timer. 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. 68P02901W23-P 23 Feb 2004 6-45 GMR-01 . Type A (no operator actions) Supported by OMC-R GUI No Cell numbers required No Dependencies None Syntax Change command string chg_element cbch_2 <value> <location> Display command string disp_element cbch_2 <location> Values Value type Integer (milliseconds) Valid range 0 to 1000000 Default value 30000 References Internal name MTCRM_CBT2 This is a Motorola defined timer. Type A (no operator actions) Supported by OMC-R GUI No Cell numbers required No Dependencies None Syntax Change command string chg_element cbch_3 <value> <location> Display command string disp_element cbch_3 <location> Values Value type Integer (milliseconds) Valid range 0 to 1000000 Default value 35000 References Internal name MTCRM_CBT3 This is a Motorola defined timer.cbch_3 Chapter 6: Timer parameters cbch_3 Description The cbch_3 timer specifies the wait time for the CBCH activation acknowledgement from RCI. 6-46 GMR-01 68P02901W23-P 23 Feb 2004 . A typical channel activation can take up to 5 seconds. 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. depending on the activity at a BTS.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. Type A (no operator actions) Supported by OMC-R GUI No Cell numbers required No Dependencies None Syntax Change command string chg_element channel_act <value> <location> Display command string disp_element channel_act <location> Values Value type Integer (milliseconds) Valid range 0 to 10000 Default value 10000 68P02901W23-P 23 Feb 2004 6-47 GMR-01 . channel_act Chapter 6: Timer parameters References Internal name TM_CHANNEL_ACT This is a Motorola defined parameter. 6-48 GMR-01 68P02901W23-P 23 Feb 2004 . 2. .08 .08 .Section 11 8. This is a Motorola defined parameter.3: all RRSM timers. 68P02901W23-P 23 Feb 2004 6-49 GMR-01 . Type A (no operator actions) Supported by OMC-R GUI No Cell numbers required No Dependencies None Syntax Change command string chg_element channel_teardown <value> <location> Display command string disp_element channel_teardown <location> Values Value type Integer (milliseconds) Valid range 0 to 1000000 Default value 28000 References Internal name RRSM_MTQ GSM technical specification 4.Technical Description BSS Command Reference channel_teardown channel_teardown Description The channel_teardown timer specifies the wait time for channel teardown.3. it is sent to the SSM. the cipher_comp_ms timer is stopped and a “ciphering successful" message is sent to the SSM. When the RRSM receives the “ciphering request". Syntax Change command string chg_element cipher_comp_ms <value> <location> Display command string disp_element cipher_comp_ms <location> 6-50 GMR-01 68P02901W23-P 23 Feb 2004 . it sends a cipher mode command to the MS.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. the resources associated with the call are released. it stops the ciphering_successful timer and sends the “Cipher Mode Complete" message to the MSC. The SSM picks the encryption algorithm and sends it in a “ciphering request" to the RRSM. 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 then starts the ciphering_successful timer. When the MS returns the “Ciphering Mode Complete" message to the RRSM. however. If the timer expires. When the SSM receives the “ciphering successful" message. It then starts the cipher_comp_ms timer. the call terminates. Type A (no operator actions) Supported by OMC-R GUI No Cell numbers required No Dependencies The ciphering_successful parameter value must be greater than the cipher_comp_ms parameter value. If an expected message is not received within the specified time. 3.Section 11 8. .2. This is a Motorola defined parameter.3: all RRSM timers. 68P02901W23-P 23 Feb 2004 6-51 GMR-01 .08 .Technical Description BSS Command Reference cipher_comp_ms Values Value type Integer (milliseconds) Valid range 0 to 1000000 Default value 28000 References Internal name RRSM_MTA GSM technical specification 4.08 . When the MS returns the “Ciphering Mode Complete" message to the RRSM. When the MSC sends the cipher mode command to the BSC. Type A (no operator actions) Supported by OMC-R GUI No Cell numbers required No Dependencies The ciphering_successful parameter value must be greater than the cipher_comp_ms parameter value. the resources associated with the call are released. When the RRSM receives the “ciphering request". it is sent to the SSM. it sends a ciphering mode command to the MS. It then starts the ciphering_successful timer. It then starts the cipher_comp_ms timer.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. the cipher_comp_ms timer is stopped and a “ciphering successful" message is sent to the SSM. Syntax Change command string chg_element ciphering_successful <value> <location> Display command string disp_element ciphering_successful <location> 6-52 GMR-01 68P02901W23-P 23 Feb 2004 . If an expected message is not received within the specified time. When the SSM receives the “ciphering successful" message. The SSM picks the encryption algorithm and sends it in a “ciphering request" to the RRSM. it stops the ciphering_successful timer and sends the “Cipher Mode Complete" message to the MSC. 68P02901W23-P 23 Feb 2004 6-53 GMR-01 .Technical Description BSS Command Reference ciphering_successful Values Value type Integer (milliseconds) Valid range 0 to 1000000 Default value 30000 References Internal name SSM_MTI This is a Motorola defined parameter. 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. 6-54 GMR-01 68P02901W23-P 23 Feb 2004 . Type A (no operator actions) Supported by OMC-R GUI No Cell numbers required No Dependencies None Syntax Change command string chg_element circuit_reset_ack <value> <location> Display command string disp_element circuit_reset_ack <location> Values Value type Integer (milliseconds) Valid range 0 to 1000000 Default value 70000 References Internal name CLM_MTA1 This is a Motorola defined timer. the MS can recover to the old channel (longer than bssmap_t8). Syntax Change command string chg_element clear_cmd_ext_ho <value> 0 Display command string disp_element clear_cmd_ext_ho 0 Values Value type Integer (milliseconds) Valid range 0 to 1000000 Default value 30000 68P02901W23-P 23 Feb 2004 6-55 GMR-01 . to recover back to the source cell. the BSC (SSM) timer clear_cmd_ext_ho guards for the original channel being released by the MSC after a successful handover.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. 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. attempt to access the target cell. 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. and in failure. or a lost MS during handover. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required No Dependencies This timer is valid only for the BSC. In an external (inter-BSS) handover. Type A (no operator actions) Supported by OMC-R GUI No Cell numbers required No Dependencies None Syntax Change command string chg_element clear_command <value> <location> Display command string disp_element clear_command <location> Values Value type Integer (milliseconds) Valid range 0 to 1000000 Default value 30000 6-56 GMR-01 68P02901W23-P 23 Feb 2004 . the call terminates.clear_command Chapter 6: Timer parameters clear_command Description The clear_command timer specifies the wait time for the clear command from the MSC. If the timer expires. the clear_command timer has no relationship with the bssmap_t8 timer. Since the introduction of the clear_cmd_ext_ho timer. This timer starts when the BSC sends the Clear request. Technical Description BSS Command Reference clear_command References Internal name SSM_MTG This is a Motorola defined parameter. 68P02901W23-P 23 Feb 2004 6-57 GMR-01 . The channel is held for the specified time in case the connection recovers. Type A (no operator actions) Supported by OMC-R GUI No Cell numbers required Yes Dependencies None Syntax Change command strings chg_element dealloc_inact <value> <location> <cell_desc> chg_cell_element dealloc_inact <value> <cell_desc> Display command strings disp_cell <cell_desc> ["full"] disp_element dealloc_inact <location> <cell_desc> Values Value type Integer (milliseconds) Valid range 0 to 1000000 Default value None 6-58 GMR-01 68P02901W23-P 23 Feb 2004 .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. 68P02901W23-P 23 Feb 2004 6-59 GMR-01 .Technical Description BSS Command Reference dealloc_inact References Internal name MTCRM_DEALLOC_INACT This is a Motorola defined timer. One block period equals 20 ms. Syntax Change command strings chg_element delay_dl_rel_dur <value> <location> Display command strings disp_element delay_dl_rel_dur <location> Values Value type Integer (20ms block periods) Valid range 15 to 600 Default value 15 Min 600 Max 50 6-60 GMR-01 68P02901W23-P 23 Feb 2004 . sets the number of block periods for which the network delays the release of a downlink TBF. Type A (no operator actions) Supported by OMC-R GUI Yes (Read-Write) Cell description required No Dependencies The GPRS feature must be unrestricted. delay_dl_rel_dur.delay_dl_rel_dur Chapter 6: Timer parameters delay_dl_rel_dur Description The delayed downlink TBF release duration BSS parameter. gci_error_clr_threshold and static sync timer parameters. It can be used at a BTS. 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.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. downlink_sync_timer. Syntax Change command string 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. Display command string disp_element downlink_sync_timer <location> 68P02901W23-P 23 Feb 2004 6-61 GMR-01 . these alarms are blocked by the system. 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. gci_error_gen_threshold. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required No Dependencies This parameter is not allowed at a stand-alone BSC or a stand-alone RXCDR. gci_error_inc. downlink_sync_timer Chapter 6: Timer parameters Values Value type Integer (milliseconds) Valid range 1000 to 3000 Default value 1000 6-62 GMR-01 68P02901W23-P 23 Feb 2004 . 05 seconds before the BTS stops attempting to allocate resources. The BTS makes three requests for a terrestrial backing resource.35 seconds for the retry time requires 4. Syntax Change command string chg_element dynet_retry_time <value> <location> <cell_desc> Display command string disp_element dynet_retry_time <location> <cell_desc> 68P02901W23-P 23 Feb 2004 6-63 GMR-01 . a setting of 1. • Systems that do not use satellites should use the minimum retry value of 150 milliseconds. • Satellite systems should use a value 1. The retry value affects call setup and handover times. Type A (no operator actions) Supported by OMC-R GUI No Cell numbers required Yes Dependencies This parameter is not available unless the containing site is configured to support Dynamic Allocation and this option is in operation. the BTS cannot allocate a TCH due to the lack of a terrestrial backing resource. The value for this timer depends on whether satellites are used to connect the BSC to the BTS. Hence.35 seconds. Satellites introduce a one way delay of 600 milliseconds.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. At that point.2 seconds greater. such as 1. The parameter is invalid for the BSC (location 0). dynet_retry_time Chapter 6: Timer parameters Values Value type Integer (milliseconds) Valid range 150 to 3000 Default value 150 6-64 GMR-01 68P02901W23-P 23 Feb 2004 . This is a Motorola defined parameter 68P02901W23-P 23 Feb 2004 6-65 GMR-01 .1. This parameter can only be viewed at the BSC. Type A (no operator actions) Supported by OMC-R GUI Yes Cell description required No Dependencies The Multiband Inter-cell Handover feature must be enabled.08 Section 3.13. Syntax Change command string chg_element early_classmark_delay <value> 0 Display command string disp_element early_classmark_delay 0 Values Value type Integer (milliseconds) Valid range 0 to 100000 Default value 0 References GSM specification GSM TS 8.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. . existing normal calls may be torn down to make TCHs available for the emergency calls. Type A (no operator actions) Supported by OMC-R GUI No Cell numbers required No Dependencies None Syntax Change command string chg_element emerg_reserved <value> <location> Display command string disp_element emerg_reserved <location> Values Value type Integer (milliseconds) Valid range 0 to 1000000 Default value 120000 6-66 GMR-01 68P02901W23-P 23 Feb 2004 . traffic channels are reserved for emergency calls waiting on SDCCHs. If idle channels are not available. 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.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. Technical Description BSS Command Reference emerg_reserved References Internal name MTCRM_EMERG_RESERVED This is a Motorola defined timer. 68P02901W23-P 23 Feb 2004 6-67 GMR-01 . If this timer expires.ext_ho_allocation Chapter 6: Timer parameters ext_ho_allocation Description The ext_ho_allocation timer specifies the wait time for handover allocation. 6-68 GMR-01 68P02901W23-P 23 Feb 2004 . Type A (no operator actions) Supported by OMC-R GUI No Cell numbers required No Dependencies None Syntax Change command string chg_element ext_ho_allocation <value> <location> Display command string disp_element ext_ho_allocation <location> Values Value type Integer (milliseconds) Valid range 0 to 1000000 Default value 30000 References Internal name SSM_MTC1 This is a Motorola defined parameter. This timer starts when the MSC sends a Handover Request to the BSC. the handover terminates. The inter_cell_handover_allowed parameter must be enabled for ECR functionality to work properly. 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.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. Syntax Change command strings chg_element ext_rtry_cand_prd <value> <location> <cell_desc> chg_cell_element ext_rtry_cand_prd <value> <cell_desc> Display command string disp_element ext_rtry_cand_prd <location> <cell_desc> Values Value type Integer (milliseconds) Valid range 0 to 1000000 Default value 4000 68P02901W23-P 23 Feb 2004 6-69 GMR-01 . Type A (no operator actions) Supported by OMC-R GUI No Cell numbers required Yes Dependencies The Congestion Relief feature must be enabled. When a handover is rejected because of congestion. Type A (no operator actions) Supported by OMC-R GUI No Cell numbers required Yes Dependencies The flow_control_t1 value must be at least 1000 milliseconds less than the flow_control_t2 value. Syntax Change command strings chg_element flow_control_t1 <value> <location> <cell_desc> chg_cell_element flow_control_t1 <value> <cell_desc> Display command string disp_element flow_control_t1 <location> <cell_desc> Values Value type Integer (milliseconds) Valid range 0 to 1000000 Default value 20000 6-70 GMR-01 68P02901W23-P 23 Feb 2004 .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. 3 68P02901W23-P 23 Feb 2004 6-71 GMR-01 .Technical Description BSS Command Reference flow_control_t1 References Internal name MTCRM_FC_T1 GSM name FC_T1 GSM specification 8.6.58 . Type A (no operator actions) Supported by OMC-R GUI No Cell numbers required Yes Dependencies The flow_control_t1 value must be at least 1000 milliseconds less than the flow_control_t2 value.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. Syntax Change command strings chg_element flow_control_t2 <value> <location> <cell_desc> chg_cell_element flow_control_t2 <value> <cell_desc> Display command string disp_element flow_control_t2 <location> <cell_desc> Values Value type Integer (milliseconds) Valid range 0 to 1000000 Default value 30000 6-72 GMR-01 68P02901W23-P 23 Feb 2004 . 3 68P02901W23-P 23 Feb 2004 6-73 GMR-01 .6.58 .Technical Description BSS Command Reference flow_control_t2 References Internal name MTCRM_FC_T2 GSM name FC_T2 GSM specification 8. BSS software processes using this parameter are not notified when the change is made. These statistics indicate the throughput of a GBL uplink and downlink. Syntax Change command string chg_element gbl_thrput_period <value> PCU Display command string disp_element gbl_thrput_period PCU Values Value type Integer (tenths of a second) Valid range 1 to 255 Default value 50 6-74 GMR-01 68P02901W23-P 23 Feb 2004 . That is. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required No Dependencies The GPRS feature must be unrestricted. this parameter can be modified without a reset to a particular device or function.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. ..Technical Description BSS Command Reference gprs_penalty_time gprs_penalty_time {3723} Description The gprs_penalty_time timer specifies the length of time for which the parameter gprs_temporary_offset is active for a cell. 29 300 seconds 6-75 GMR-01 . . Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required Yes Dependencies The PBCCH/PCCH feature must be unrestricted.. Syntax Change command strings chg_cell_element gprs_penalty_time <value> <location> <cell_desc> chg_element gprs_penalty_time <value> <cell_desc> Display command strings disp_cell <cell_desc> “full" disp_element gprs_penalty_time <cell_desc> Values Value type Integer Valid range 0 to 31 68P02901W23-P 23 Feb 2004 0 10 seconds 1 20 seconds 2 30 seconds .. gprs_penalty_time Chapter 6: Timer parameters Default value 30 310 seconds 31 320 seconds 0 10 seconds 6-76 GMR-01 68P02901W23-P 23 Feb 2004 . 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. Otherwise. Syntax Change command strings chg_element gprs_smg30_t3192 <value> <location> <cell_desc> chg_cell_element gprs_smg30_t3192 <value> <cell_desc> Display command string disp_cell_element gprs_smg30_t3192 <cell_desc> Values Value type Select integer (milliseconds) Valid range 500. then it is used. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required Yes Dependencies The GPRS feature must be unrestricted. 1000. 2000. and 4000 Default value 500 68P02901W23-P 23 Feb 2004 6-77 GMR-01 . gprs_t3192 is used. 2000.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. 1000. Syntax Change command strings chg_element gprs_t3168 <value> <location> <cell_desc> chg_cell_element gprs_t3168 <value> <cell_desc> Display command string disp_element gprs_t3168 <location> <cell_desc> Values Value type Select integer (milliseconds) Valid range 500. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required Yes Dependencies The GPRS feature must be unrestricted. and 4000 Default value 4000 6-78 GMR-01 68P02901W23-P 23 Feb 2004 . This parameter specifies the wait time for the MS waits to get a Packet Uplink Assignment after sending a Packet Resource Request. 160. 1000. 80. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required Yes Dependencies The GPRS feature must be unrestricted. Syntax Change command strings chg_element gprs_t3192 <value> <location> cell_desc> chg_cell_element gprs_t3192 <value> <cell_desc> Display command string disp_element gprs_t3192 <location> <cell_desc> Values Value type Select integer (milliseconds) Valid range 0. 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.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. 120. 500. and 1500 Default value 500 68P02901W23-P 23 Feb 2004 6-79 GMR-01 . 200. MSC h_interval < handover_recognized_period Syntax Add/Change command strings add_cell <gsm_cell_desc> <location> chg_element handover_recognized_period <value> <location> <cell_desc> chg_cell_element handover_recognized_period <value> <cell_desc> Display command strings disp_cell <cell_desc> ["full"] disp_element handover_recognized_period <location> <cell_desc> 6-80 GMR-01 68P02901W23-P 23 Feb 2004 . 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). 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. 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. The MSC timer T_hand_rqd has the same function as handover_recognized_period.handover_recognized_period Chapter 6: Timer parameters handover_recognized_period Description In an inter-BSS (external) handover. Type A (no operator actions) Supported by OMC-R GUI Yes Cell description required Yes Dependencies Call queueing must be enabled. The MSC parameter h_interval specifies how long a handover request message remains queued by the MSC. To set this threshold. 17. 68P02901W23-P 23 Feb 2004 6-81 GMR-01 .8.08 .3.2 .20 .Appendix A .2.Adjacent Cell Handover .t_hand_rqd.5. and 3.6 8.1.3: Tqho 12.08 .4 .2.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. the handover attempt fails. the ho_ack timer specifies the wait time for the BTS/BSC assignment of the target handover channel. and a new handover procedure has to start.ho_ack Chapter 6: Timer parameters ho_ack Description In an intra-cell handover. the newly assigned channel is freed. If this timer expires before this assignment. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required Yes Dependencies None Syntax Change command strings chg_element ho_ack <value> <location> <cell_desc> chg_cell_element ho_ack <value> <cell_desc> Display command strings disp_cell <cell_desc> ["full"] disp_element ho_ack <location> <cell_desc> Values Value type Integer (milliseconds) Valid range 0 to 1000000 Default value 5000 6-82 GMR-01 68P02901W23-P 23 Feb 2004 . Technical Description BSS Command Reference ho_ack References Internal name MTCRM_HANDOVER_ACK This is a Motorola defined timer. 68P02901W23-P 23 Feb 2004 6-83 GMR-01 . Type A (no operator actions) Supported by OMC-R GUI No Cell numbers required No Dependencies None Syntax Change command string chg_element ho_allocation <value> <location> Display command string disp_element ho_allocation <location> Values Value type Integer (milliseconds) Valid range 0 to 1000000 Default value 30000 References Internal name SSM_MTK This is a Motorola defined timer. the handover terminates. 6-84 GMR-01 68P02901W23-P 23 Feb 2004 . If this timer expires. The system starts this timer when when the BSC requests a resource from the BTS to perform an intra-BSS handover.ho_allocation Chapter 6: Timer parameters ho_allocation Description The ho_allocation timer specifies the wait time for handover allocation from destination cell RRSM. This timer starts when the BTS attempts to assign a channel for a handover. Type A (no operator actions) Supported by OMC-R GUI No Cell numbers required No Dependencies None Syntax Change command string chg_element ho_complete <value> <location> Display command string disp_element ho_complete <location> Values Value type Integer (milliseconds) Valid range 0 to 1000000 Default value 28000 68P02901W23-P 23 Feb 2004 6-85 GMR-01 .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. the handover terminates. If this timer expires. 6-86 GMR-01 68P02901W23-P 23 Feb 2004 .3.08 .2.08 .3: all RRSM timers This is a Motorola defined timer.ho_complete Chapter 6: Timer parameters References Internal name RRSM_MTD GSM specification 4.Section 11 8. 68P02901W23-P 23 Feb 2004 6-87 GMR-01 . Type A (no operator actions) Supported by OMC-R GUI No Cell numbers required No Dependencies None Syntax Change command string chg_element ho_request <value> <location> Display command string disp_element ho_request <location> Values Value type Integer (milliseconds) Valid range 0 to 1000000 Default value 30000 References Internal name SSM_MTB1 This is a Motorola defined timer.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. the handover terminates. If this timer expires. This timer starts when the MSC sends an empty CR to the BTS and the BTS informs the BSC. The system starts this timer when the handover_request_ack message is sent to the MSC. Type A (no operator actions) Supported by OMC-R GUI No Cell numbers required No Dependencies None Syntax Change command string chg_element ho_successful <value> <location> Display command string disp_element ho_successful <location> Values Value type Integer (milliseconds) Valid range 0 to 1000000 Default value 30000 References Internal name SSM_MTJ This is a Motorola defined timer.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). If this timer expires. 6-88 GMR-01 68P02901W23-P 23 Feb 2004 . the call terminates. 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. 6-89 GMR-01 . Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required Yes Dependencies None Syntax Change command strings chg_element hop_count_timer <value> <cell_desc> chg_cell_element hop_count_timer <value> <cell_desc> Display command string disp_element hop_count_timer <cell_desc> Values Value type Integer (SACCH periods) Valid range 0 to 255 Default value 0 68P02901W23-P 23 Feb 2004 A value of 0 disables this feature. 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.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 system will keep the mobile on the FR channel if it is a candidate for FR to HR reconfiguration due to congestion. gci_error_clr_threshold and static sync timer parameters. gci_error_inc. It can be used at a BTS. The GPRS feature restricts the modifications of the gprs_alarm_time period. The BSS allows the values of the initial_sync_timer. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required No Dependencies This timer is not allowed at a stand-alone BSC or RXCDR. The initial_sync_timer is valid only at BTS sites. gci_error_gen_threshold.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. downlink_sync_timer. these alarms are blocked by the system. uplink_sync_timer and static_sync_timer to be modified so that only one site reset is required for all to be changed. However. A site reset occurs when the value of initial_sync_timer is changed in SYSGEN OFF mode. Syntax Change command string chg_element initial_sync_timer <value> <location> Display command string disp_element initial_sync_timer <location> 6-90 GMR-01 68P02901W23-P 23 Feb 2004 . Resetting the site generates several alarms. Technical Description BSS Command Reference initial_sync_timer Values Value type Integer (1 step = 1 millisecond) Valid range 1500 to 7000 Default value 4000 (4 seconds) 68P02901W23-P 23 Feb 2004 6-91 GMR-01 . 08-3.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.2. Syntax Change command string chg_element lb_int_bssmap_t13 <value> <location> Display command string disp_element lb_int_bssmap_t13 <location> Values Value type Integer (milliseconds) Valid range 0 to 1000000 Default value 40000 References GSM specification GSM 8. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required No Dependencies The Location Services feature must be unrestricted.3 6-92 GMR-01 68P02901W23-P 23 Feb 2004 . Syntax Change command string chg_element lb_int_bssmap_t4 <value> <location> Display command string disp_element lb_int_bssmap_t4 <location> Values Value type Integer (milliseconds) Valid range 0 to 1000000 Default value 50000 68P02901W23-P 23 Feb 2004 6-93 GMR-01 .Technical Description BSS Command Reference lb_int_bssmap_t4 lb_int_bssmap_t4 Description The lb_int_bssmap_t4 (Lb-interface BSSMAP T4) timer guards the time allowed for the BSS-based SMLC to respond to a RESET message with a RESET ACKNOWLEDGE message. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required No Dependencies The Location Services feature must be unrestricted. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required No Dependencies The Location Services feature must be unrestricted. Syntax Change command string chg_element lb_int_clear_command <value> <location> Display command string disp_element lb_int_clear_command <location> Values Value type Integer (milliseconds) Valid range 0 to 1000000 Default value 30000 6-94 GMR-01 68P02901W23-P 23 Feb 2004 .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. 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. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required No Dependencies The Location Services feature must be unrestricted. Syntax Change timer chg_element lb_int_sccp_released <value> <location> Display timer disp_element lb_int_sccp_released <location> Values Value type Integer (millisecond) Valid range 0 to 1000000 Default value 30000 68P02901W23-P 23 Feb 2004 6-95 GMR-01 . Syntax Change command string chg_element lb_int_sccp_tconn_est <value> <location> Display command string disp_element lb_int_sccp_tconn_est <location> Values Value type Integer (milliseconds) Valid range 0 to 1000000 Default value 30000 6-96 GMR-01 68P02901W23-P 23 Feb 2004 .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. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required No Dependencies The Location Services feature must be unrestricted. 23 6-97 GMR-01 . Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required No Dependencies The Location Services feature must be unrestricted.08-3. The value of this parameter should be greater than the lb_int_sccp_tias parameter value. The value of this parameter should be greater than the value of the sccp_tiar at the BSS-based SMLC Syntax Change command string chg_element lb_int_sccp_tiar <value> <location> Display command string disp_element lb_int_sccp_tiar <location> Values Value type Integer (milliseconds) Valid range 0 to 1000000 Default value 30000 References GSM specification 68P02901W23-P 23 Feb 2004 GSM 8.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 less than the lb_int_sccp_tiar parameter value. Syntax Change command string chg_element lb_int_sccp_tias <value> <location> Display command string disp_element lb_int_sccp_tias <location> Values Value type Integer (milliseconds) Valid range 0 to 1000000 Default value 30000 References GSM specification GSM 8.08-3. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required No Dependencies The Location Services feature must be unrestricted.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.23 6-98 GMR-01 68P02901W23-P 23 Feb 2004 . 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 Change command string chg_element lb_int_sccp_trel <value> <location> Display command string disp_element lb_int_sccp_trel <location> Values Value type Integer (milliseconds) Valid range 4000 to 15000 Default value 10000 References GSM specification 68P02901W23-P 23 Feb 2004 This is a Motorola defined timer. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required No Dependencies The Location Services feature must be unrestricted. 6-99 GMR-01 . 15 This is a Motorola defined timer. 6-100 GMR-01 68P02901W23-P 23 Feb 2004 .3. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required No Dependencies The Location Services feature must be unrestricted.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.1.08 . Syntax Change command string chg_element lb_int_spi <value> <location> Display command string disp_element lb_int_spi <location> Values Value type Integer (milliseconds) Valid range 10000 to 1000000 Default value 60000 References GSM specification GSM 8. Syntax Change command string chg_element lb_int_ss7_l2_t1 <value> <location> Display command string disp_element lb_int_ss7_l2_t1 <location> Values Value type Integer (milliseconds) Valid range ss7_mode = 0: 40000 to 50000 ss7_mode = 1: 13000 to 30000 Default value ss7_mode = 0: 50000 ss7_mode =1: 13000 References ITU specification 68P02901W23-P 23 Feb 2004 CCITT Q.703 6-101 GMR-01 . Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required No Dependencies The Location Services feature must be unrestricted. The valid ranges for this element are dependent upon the value of the ss7_mode.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. 703 6-102 GMR-01 68P02901W23-P 23 Feb 2004 .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. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required No Dependencies The Location Services feature must be unrestricted. The valid ranges for this element are dependent upon the value of the ss7_mode. Syntax Change command string chg_element lb_int_ss7_l2_t2 <value> <location> Display command string disp_element lb_int_ss7_l2_t2 <location> Values Value type Integer (millisecond) Valid range ss7_mode = 0: 5000 to 150000 ss7_mode = 1: 5000 to 30000 Default value ss7_mode = 0: 25000 ss7_mode =1: 23000 References ITU specification CCITT Q. 703 6-103 GMR-01 . The valid ranges for this element are dependent upon the value of the ss7_mode.Technical Description BSS Command Reference lb_int_ss7_l2_t3 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. Syntax Change command string chg_element lb_int_ss7_l2_t3 <value> <location> Display command string disp_element lb_int_ss7_l2_t3 <location> Values Value type Integer (milliseconds) Valid range ss7_mode = 0: 1000 to 1500 ss7_mode = 1: 5000 to 14000 Default value ss7_mode = 0: 1400 ss7_mode =1: 11500 References ITU specification 68P02901W23-P 23 Feb 2004 CCITT Q. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required No Dependencies The Location Services feature must be unrestricted. 703 6-104 GMR-01 68P02901W23-P 23 Feb 2004 . Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required No Dependencies The Location Services feature must be unrestricted. Syntax Change command string chg_element lb_int_ss7_l2_t4 <value> <location> Display command string disp_element lb_int_ss7_l2_t4 <location> Values Value type Integer (milliseconds) Valid range 400 to 600 Default value 600 References ITU specification CCITT Q.lb_int_ss7_l2_t4 Chapter 6: Timer parameters lb_int_ss7_l2_t4 Description The lb_int_ss7_l2_t4 (Lb-interface MTP layer 2 T4) timer is the emergency proving period timer associated with the Lb-interface. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required No Dependencies The Location Services feature must be unrestricted.703 6-105 GMR-01 .Technical Description BSS Command Reference lb_int_ss7_l2_t5 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 Change command string chg_element lb_int_ss7_l2_t5 <value> <location> Display command string disp_element lb_int_ss7_l2_t5 <location> Values Value type Integer (milliseconds) Valid range 80 to 120 Default value 100 References ITU specification 68P02901W23-P 23 Feb 2004 CCITT Q. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required No Dependencies The Location Services feature must be unrestricted. The valid ranges for this element are dependent upon the value of the ss7_mode.703 6-106 GMR-01 68P02901W23-P 23 Feb 2004 . Syntax Change command string chg_element lb_int_ss7_l2_t6 <value> <location> Display command string disp_element lb_int_ss7_l2_t6 <location> Values Value type Integer (millisecond) Valid range ss7_mode = 0: 3000 to 6000ss7_mode = 1: 1000 to 6000 Default value ss7_mode = 0: 5000ss7_mode =1: 5000 References ITU specification ITU Q.lb_int_ss7_l2_t6 Chapter 6: Timer parameters 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. 703 6-107 GMR-01 . The valid ranges for this element are dependent upon the value of the ss7_mode.Technical Description BSS Command Reference lb_int_ss7_l2_t7 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. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required No Dependencies The Location Services feature must be unrestricted. Syntax Change command string chg_element lb_int_ss7_l2_t7 <value> <location> Display command string disp_element lb_int_ss7_l2_t7 <location> Values Value type Integer (milliseconds) Valid range 500 to 2000 Default value 1000 References ITU specification 68P02901W23-P 23 Feb 2004 CCITT Q. lb_int_ss7_l3_t1 Chapter 6: Timer parameters 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.704 6-108 GMR-01 68P02901W23-P 23 Feb 2004 . Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required No Dependencies The Location Services feature must be unrestricted. Syntax Change command string chg_element lb_int_ss7_l3_t1 <value> <location> Display command string disp_element lb_int_ss7_l3_t1 <location> Values Value type Integer (milliseconds) Valid range 500 to 1200 Default value 850 References ITU specification CCITT Q. Syntax Change command string chg_element lb_int_ss7_l3_t12 <value> <location> Display command string disp_element lb_int_ss7_l3_t12 <location> Values Value type Integer (milliseconds) Valid range 800 to 1500 Default value 1150 References ITU specification 68P02901W23-P 23 Feb 2004 CCITT Q.704 6-109 GMR-01 .Technical Description BSS Command Reference lb_int_ss7_l3_t12 lb_int_ss7_l3_t12 Description The lb_int_ss7_l3_t12 (Lb-interface MTP layer 3 T12) timer is the waiting for uninhibit acknowledgement timer associated with the Lb-interface. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required No Dependencies The Location Services feature must be unrestricted. 704 6-110 GMR-01 68P02901W23-P 23 Feb 2004 . Syntax Change command string chg_element lb_int_ss7_l3_t13 <value> <location> Display command string disp_element lb_int_ss7_l3_t13 <location> Values Value type Integer (milliseconds) Valid range 800 to 1500 Default value 1150 References ITU specification CCITT Q.lb_int_ss7_l3_t13 Chapter 6: Timer parameters lb_int_ss7_l3_t13 Description The lb_int_ss7_l3_t13 (Lb-interface MTP layer 3 T13) timer is the waiting for force uninhibit timer associated with the Lb-interface. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required No Dependencies The Location Services feature must be unrestricted. Syntax Change command string chg_element lb_int_ss7_l3_t14 <value> <location> Display command string disp_element lb_int_ss7_l3_t14 <location> Values Value type Integer (milliseconds) Valid range 2000 to 3000 Default value 2500 References ITU specification 68P02901W23-P 23 Feb 2004 CCITT Q.704 6-111 GMR-01 . Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required No Dependencies The Location Services feature must be unrestricted.Technical Description BSS Command Reference lb_int_ss7_l3_t14 lb_int_ss7_l3_t14 Description The lb_int_ss7_l3_t14 (Lb-interface MTP layer 3 T14) timer is the waiting for inhibition acknowledgement timer associated with the Lb-interface. Syntax Change command string chg_element lb_int_ss7_l3_t17 <value> <location> Display command string disp_element lb_int_ss7_l3_t17 <location> Values Value type Integer (milliseconds) Valid range 800 to 1500 Default value 1150 References ITU specification CCITT Q.lb_int_ss7_l3_t17 Chapter 6: Timer parameters lb_int_ss7_l3_t17 Description The lb_int_ss7_l3_t17 (Lb-interface MTP layer 3 T17) timer is the delay to avoid oscillation of initial alignment failure and link restart timer associated with the Lb-interface.704 6-112 GMR-01 68P02901W23-P 23 Feb 2004 . Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required No Dependencies The Location Services feature must be unrestricted. 704 6-113 GMR-01 . Syntax Change command string chg_element lb_int_ss7_l3_t2 <value> <location> Display command string disp_element lb_int_ss7_l3_t2 <location> Values Value type Integer (milliseconds) Valid range 700 to 2000 Default value 1400 References ITU specification 68P02901W23-P 23 Feb 2004 CCITT Q.Technical Description BSS Command Reference lb_int_ss7_l3_t2 lb_int_ss7_l3_t2 Description The lb_int_ss7_l3_t2 (Lb-interface MTP layer 3 T2) timer is the waiting for changeover acknowledgement timer associated with the Lb-interface. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required No Dependencies The Location Services feature must be unrestricted. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required No Dependencies The Location Services feature must be unrestricted. The valid values for this element are dependent upon the value of the ss7_mode element. The ss7_mode dependent parameters are set to the appropriate defaults when the ss7_mode is changed. Syntax Change command string chg_element lb_int_ss7_l3_t22 <value> <location> Display command string disp_element lb_int_ss7_l3_t22 <location> Values Value type Integer (milliseconds) Valid range ss7_mode = 0: 180000 to 360000 ss7_mode = 1: 90000 to 120000 Default value ss7_mode = 0: 270000 ss7_mode =1: 90000 6-114 GMR-01 68P02901W23-P 23 Feb 2004 .lb_int_ss7_l3_t22 Chapter 6: Timer parameters 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. References ITU specification 68P02901W23-P 23 Feb 2004 CCITT Q.Technical Description BSS Command Reference lb_int_ss7_l3_t22 The ss7_mode dependent parameters are set to the appropriate defaults when the ss7_mode is changed.704 6-115 GMR-01 . The valid values for this element are dependent upon the value of the ss7_mode element.lb_int_ss7_l3_t23 Chapter 6: Timer parameters 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. Syntax Change command string chg_element lb_int_ss7_l3_t23 <value> <location> Display command string disp_element lb_int_ss7_l3_t23 <location> Values Value type Integer (milliseconds) Valid range ss7_mode = 0: 180000 to 360000 ss7_mode = 1: 90000 to 120000 Default value ss7_mode = 0: 270000 ss7_mode =1: 90000 6-116 GMR-01 68P02901W23-P 23 Feb 2004 . This parameter is automatically changed to the appropriate default value if the ss7_mode element is changed. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required No Dependencies The Location Services feature must be unrestricted. Technical Description BSS Command Reference lb_int_ss7_l3_t23 References ITU specification 68P02901W23-P 23 Feb 2004 CCITT Q.704 6-117 GMR-01 . 704 6-118 GMR-01 68P02901W23-P 23 Feb 2004 . Syntax Change command string chg_element lb_int_ss7_l3_t4 <value> <location> Display command string disp_element lb_int_ss7_l3_t4 <location> Values Value type Integer (milliseconds) Valid range 500 to 1200 Default value 850 References ITU specification CCITT Q.lb_int_ss7_l3_t4 Chapter 6: Timer parameters 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. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required No Dependencies The Location Services feature must be unrestricted. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required No Dependencies The Location Services feature must be unrestricted. Syntax Change command string chg_element lb_int_ss7_l3_t5 <value> <location> Display command string disp_element lb_int_ss7_l3_t5 <location> Values Value type Integer (milliseconds) Valid range 500 to 1200 Default value 850 References ITU specification 68P02901W23-P 23 Feb 2004 CCITT Q.704 6-119 GMR-01 .Technical Description BSS Command Reference lb_int_ss7_l3_t5 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 Change command string chg_element lb_int_ss7_slt_t1 <value> <location> Display command string disp_element lb_int_ss7_slt_t1 <location> Values Value type Integer (milliseconds) Valid range 4000 to 12000 Default value 8000 References ITU specification CCITT Q.707 6-120 GMR-01 68P02901W23-P 23 Feb 2004 .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. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required No Dependencies The Location Services feature must be unrestricted. Syntax Change command string chg_element lb_int_t_stat_info <value> <location> Display command string disp_element lb_int_t_stat_info <location> Values Value type Integer (millisecond) Valid range 0 to 1000000 Default value 90000 68P02901W23-P 23 Feb 2004 6-121 GMR-01 . Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required No Dependencies The Location Services feature must be unrestricted.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. 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. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required No Dependencies The Location Services feature must be unrestricted. Syntax Change command string chg_element lcs_perf_location <value> <location> Display command string disp_element lcs_perf_location <location> Values Value type Integer (millisecond) Valid range 0 to 1000000 Default value 300000 6-122 GMR-01 68P02901W23-P 23 Feb 2004 . Syntax Change command string chg_element lcs_segmentation <value> <location> Display command string disp_element lcs_segmentation <location> Values Value type Integer (millisecond) Valid range 0 to 1000000 Default value 10000 68P02901W23-P 23 Feb 2004 6-123 GMR-01 . Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required No Dependencies The Location Services feature must be unrestricted. The value of this parameter should be less than the value of the lcs_supervision timer.Technical Description BSS Command Reference lcs_segmentation lcs_segmentation Description The lcs_segmentation timer is used for supervising a Location Services segmentation operation. 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 Change command string chg_element lcs_supervision <value> <location> Display command string disp_element lcs_supervision <location> Values Value type Integer (millisecond) Valid range 0 to 1000000 Default value 30000 6-124 GMR-01 68P02901W23-P 23 Feb 2004 . Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required No Dependencies The Location Services feature must be unrestricted. Syntax Change command string chg_element mode_modify <value> <location> Display command string disp_element mode_modify <location> Values Value type Integer (milliseconds) Valid range 0 to 10000 Default value 10000 68P02901W23-P 23 Feb 2004 6-125 GMR-01 . 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.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. Type A (no operator actions) Supported by OMC-R GUI No Cell numbers required No Dependencies The value of the mode_modify_ack CP timer must be greater than or equal to the RSS timers + 10 ms. mode_modify Chapter 6: Timer parameters References Internal name TM_MODE_MODIFY This is a Motorola defined timer. 6-126 GMR-01 68P02901W23-P 23 Feb 2004 . 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. When this timer expires. the BTS aborts the mode modification. Type A (no operator actions) Supported by OMC-R GUI No Cell numbers required No Dependencies None Syntax Change command string chg_element mode_rr_modify_ack <value> <location> Display command string disp_element mode_rr_modify_ack <location> Values Value type Integer (milliseconds) Valid range 0 to 1000000 Default value 28000 68P02901W23-P 23 Feb 2004 6-127 GMR-01 . This timer starts when the BTS receives confirmation on modification of the channel mode. 3: all RRSM timers. 6-128 GMR-01 68P02901W23-P 23 Feb 2004 .Section 11 8. This is a Motorola defined timer.2.08 .08 .mode_rr_modify_ack Chapter 6: Timer parameters References Internal name RRSM_MTY GSM technical specification 4.3. Type A (no operator actions) Supported by OMC-R GUI No Cell numbers required No Dependencies None Syntax Change command string chg_element ms_sapi3_est <value> <location> Display command string disp_element ms_sapi3_est <location> Values Value type Integer (milliseconds) Valid range 0 to 1000000 Default value 28000 68P02901W23-P 23 Feb 2004 6-129 GMR-01 . This is an internal timer dealing with SAPI3 connection procedures.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. 2.08 .08 . 6-130 GMR-01 68P02901W23-P 23 Feb 2004 .5.2.7.20 . This is a Motorola defined timer.3.08 .3: all RRSM timers 8.Section 11 8.ms_sapi3_est Chapter 6: Timer parameters References Internal name RRSM_MTE1 GSM specification 12.3.1 .2 BSS Map Timer In BSC 4. 48 seconds 3 0. BSS software processes using this parameter are immediately notified when the change is made.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.72 seconds 6-131 GMR-01 . Syntax Change command string chg_element nc_non_drx_period <value> <location> Display command string disp_element nc_non_drx_period <location> Values Value type Integer Valid range 0 to 7 68P02901W23-P 23 Feb 2004 0 No non_drx_period set 1 0. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required No Dependencies The GPRS and NCCR features must be unrestricted.24 seconds 2 0. The PCU must be equipped. 96 seconds 2 (0.48 seconds) 6-132 GMR-01 68P02901W23-P 23 Feb 2004 .20 seconds 6 1.96 seconds 5 1.nc_non_drx_period Default value Chapter 6: Timer parameters 4 0.44 seconds 7 1. The PCU must be equipped.36 seconds 5 30.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. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required No Dependencies The GPRS and NCCR features must be unrestricted. Syntax Change command string chg_element nc_reporting_period_i <value> <location> Display command string disp_element nc_reporting_period_i <location> Values Value type Integer Valid range 4 to 6 Default value 68P02901W23-P 23 Feb 2004 4 15.72 seconds 6 61.44 seconds 6 6-133 GMR-01 . BSS software processes using this parameter are immediately notified when the change is made. 92 seconds 2 3.84 seconds 3 7.68 seconds 6-134 GMR-01 68P02901W23-P 23 Feb 2004 .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. BSS software processes using this parameter are immediately notified when the change is made. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required No Dependencies The GPRS and NCCR features must be unrestricted. Syntax Change command string chg_element nc_reporting_period_t <value> <location> Display command string disp_element nc_reporting_period_t <location> Values Value type Integer Valid range 0 or 6 0 0. The PCU must be equipped.96 seconds 1 1. 72 seconds 6 61.Technical Description BSS Command Reference Default value 68P02901W23-P 23 Feb 2004 nc_reporting_period_t 4 15.36 seconds 5 30.44 seconds 2 6-135 GMR-01 . Syntax Change command strings chg_element neighbor_report_timer <value> <location> <cell_desc> chg_cell_element neighbor_report_timer <value> <cell_desc> Display command string disp_element neighbor_report_timer <location> <cell_desc> Values Value type Integer (SACCH periods) Valid range 0 to 255 Default value 10 6-136 GMR-01 68P02901W23-P 23 Feb 2004 .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. Type A (no operator actions) Supported by OMC-R GUI Yes Cell description required Yes Dependencies The Concentric Cells feature must be unrestricted the inner_zone_alg element must be set to 2. Type A (no operator actions) Supported by OMC-R GUI No Cell numbers required No Dependencies The GPRS feature must be unrestricted. the NS Test Procedure is stopped and the NSVC is marked dead and blocked. After the maximum number of attempts fail. This timer is cleared when the NS-ALIVE-ACK is received by the BSS from the SGSN. Syntax Change command string chg_element ns_alive_timer <value> <location> Display command string disp_element ns_alive_timer <location> Values Value type Integer (seconds) Valid range 1 to 30 Default value 3 68P02901W23-P 23 Feb 2004 6-137 GMR-01 .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. That is. BSS software processes using this parameter are not notified when the change is made. the NS Test Procedure is repeated a maximum of ns_alive_retries attempts. If the timer expires before teh ACK is received. this parameter can be modified without a reset to a particular device or function. This timer is set when the BSS sends an NS-ALIVE-ACK 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. That is. This timer is set when the BSS sends an NS-BLOCK or NS-UNBLOCK PDU to the SGSN. BSS software processes using this parameter are not notified when the change is made. Syntax Change command string chg_element ns_block_timer <value> <location> Display command string disp_element ns_block_timer <location> Values Value type Integer (seconds) Valid range 1 to 30 Default value 3 6-138 GMR-01 68P02901W23-P 23 Feb 2004 . this parameter can be modified without a reset to a particular device or function. Type A (no operator actions) Supported by OMC-R GUI No Cell numbers required No Dependencies The GPRS feature must be unrestricted.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. the NS Blocking or Unblocking procedure is repeated a maximum of ns_block_retries attempts. After the maximum attempts fail. the NSVC remains unblocked. If the timer expires before an ACK is received. 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. BSS software processes using this parameter are not notified when the change is made. This timer is set when the BSS initiates the NS Reset Procedure. Type A (no operator actions) Supported by OMC-R GUI No Cell numbers required No Dependencies The GPRS feature must be unrestricted. If the NS Reset Procedure is not successful before the ns_reseet_period expires. Syntax Change command string chg_element ns_reset_period <value> <location> Display command string disp_element ns_reset_period <location> Values Value type Integer (seconds) Valid range 1 to 250 Default value 125 68P02901W23-P 23 Feb 2004 6-139 GMR-01 . this parameter can be modified without a reset to a particular device or function.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. the NSVC remains unblocked. That is. That is. the NSVC remains blocked.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. the NS Reset Procedure is repeated until the ns_reset_period expires. 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. BSS software processes using this parameter are not notified when the change is made. If the timer expires before the ACK is received. If the NS Reset Procedure is not successful before the ns_reset_period expires. this parameter can be modified without a reset to a particular device or function. Syntax Change command string chg_element ns_reset_timer <value> <location> Display command string disp_element ns_reset_timer <location> Values Value type Integer (seconds) Valid range 1 to 120 Default value 40 6-140 GMR-01 68P02901W23-P 23 Feb 2004 . Type A (no operator actions) Supported by OMC-R GUI No Cell numbers required No Dependencies This parameter can be used only if the GPRS feature is unrestricted. Type A (no operator actions) Supported by OMC-R GUI No Cell numbers required No Dependencies This parameter can be used only if the GPRS feature is unrestricted.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 BSS initiates the NS Test Procedure. Upon successful completion of the NS Test Procedure. this parameter can be modified without a reset to a particular device or function. the timer is started again. The procedure is repeated each time the timer expires. Upon expiry of the timer. The NSVC is tested every ns_test_timer seconds This timer is set upon successful completion of the NS Test Procedure. BSS software processes using this parameter are not notified when the change is made. Syntax Change command string chg_element ns_test_timer <value> <location> Display command string disp_element ns_test_timer <location> Values Value type Integer (seconds) Valid range 1 to 60 Default value 30 68P02901W23-P 23 Feb 2004 6-141 GMR-01 . That is. BSS software processes using this parameter are notified immediately after the change is made. The value of this parameter is the binary representation of the standard parameter DRX_TIMER_MAX. Syntax Change command strings 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 Display command string disp_cell <cell_desc> “full" disp_element pccch_drx_timer_max <location> <cell-desc> disp_element pccch_drx_timer_max <location> all 6-142 GMR-01 68P02901W23-P 23 Feb 2004 . It is given as two taken to the power of the binary value minus one (2 (bv-1)) in units of one second. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required Yes Dependencies The PCCCH/PBCCH feature must be unrestricted.pccch_drx_timer_max Chapter 6: Timer parameters pccch_drx_timer_max {3723} 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). Technical Description BSS Command Reference pccch_drx_timer_max Values Value type Integer Valid range 0 to 7 Default value 68P02901W23-P 23 Feb 2004 0 0 seconds 1 1 second 2 2 seconds 3 4 seconds 4 8 seconds 5 16 seconds 6 32 seconds 7 64 seconds 3 (4 seconds) 6-143 GMR-01 . This timer starts when the MS places the cell on the list of strongest cells for reselection. When more than one cell is available for reselection.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. For the duration of this timer. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required Yes Dependencies temporary_offset Syntax Add/Change command strings add_cell <gsm_cell_id> <location> chg_element penalty_time <value> <location> <cell_desc> chg_cell_element penalty_time <value> <cell_desc> Display command strings disp_cell <cell_desc> ["full"] disp_element penalty_time <location> <cell_desc> 6-144 GMR-01 68P02901W23-P 23 Feb 2004 . This timer resets when the cell is taken off the list. the C2 parameter is given a negative value. C2 is the reselection priority assigned to a cell which can be broadcast on the BCCH of each cell. This discourages fast moving MSs from selecting the cell. the MS reselects the cell with the highest C2 value. .08 Table 10.2...32a Section 10.22 68P02901W23-P 23 Feb 2004 6-145 GMR-01 . 620 seconds 0 A value of 31 is reserved to indicate that cell_reselect_offset is subtracted from C2 and temporary_offset is ignored.Technical Description BSS Command Reference penalty_time Values Value type Integer (1 Step = 20 seconds) Valid range 0 to 31 0 1 2 ..08 TSGSM 3.35 TSGSM 5.5. 30 Default value 20 seconds 40 seconds 60 seconds . References GSM parameter PENALTY_TIME GSM specification TSGSM 4. 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. Syntax Change command strings modify_value <location> phase_lock_duration <new_value> mms <dev_fun_id1> <dev_fun_id2> <dev_fun_id3> Display command string disp_equipment <location> mms <id1> <id2> <id3> Values Value type Integer (seconds) Valid range 0 to 3600 Default value 0 50 (M-Cell only) 6-146 GMR-01 68P02901W23-P 23 Feb 2004 . Type A (no operator actions) Supported by OMC-R GUI Yes Cell description required No Dependencies This parameter cannot be modified for a GPRS PCU MMS. Technical Description BSS Command Reference psi1_repeat_period psi1_repeat_period {3723} 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. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required Yes Dependencies The PBCCH/PCCCH otional feature must be unrestricted. Syntax Change command string chg_element psi1_repeat_period <value> <location> <cell_desc> chg_cell_element psi1_repeat_period <value> <cell_desc> Display command string disp_cell <cell_desc> “full" disp_element psi1_repeat_period <location> <cell_desc> Values Value type Integer Valid range 0 to 16 68P02901W23-P 23 Feb 2004 6-147 GMR-01 . That is. this parameter can be modified without a reset to a particular device or function. BSS software processes using this parameter are not notified when the change is made. 1 to 16 Frequency of PSI1 in a 52-frame multiframe 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 GMR-01 68P02901W23-P 23 Feb 2004 .psi1_repeat_period Chapter 6: Timer parameters Default value 0 Period calculated by algorithm (based on bs_pbcch_blks and number of PSI instances in low repetition rate group). Type A (no operator actions) Supported by OMC-R GUI No Cell description required No Dependencies None Syntax Change command string chg_element radio_chan_released <value> <location> Display command string disp_element radio_chan_released <location> Values Value type Integer (milliseconds) Valid range 0 to 1000000 Default value 30000 68P02901W23-P 23 Feb 2004 6-149 GMR-01 . 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.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. radio_chan_released Chapter 6: Timer parameters References Internal name SSM_MTH This is a Motorola defined timer. 6-150 GMR-01 68P02901W23-P 23 Feb 2004 . Technical Description BSS Command Reference register_exp register_exp Description The register_exp timer specifies the wait time for the CRM to initiate registration with the BSC. Type A (no operator actions) Supported by OMC-R GUI No Cell description required No Dependencies None Syntax Change command string chg_element register_exp <value> <location> Display command string disp_element register_exp <location> Values Value type Integer (milliseconds) Valid range 0 to 1000000 Default value 120000 References Internal name MTCRM_REGISTER_EXP This is a Motorola defined timer. 68P02901W23-P 23 Feb 2004 6-151 GMR-01 . Type A (no operator actions) Supported by OMC-R GUI Yes Cell description required Yes Dependencies None Syntax Change command strings chg_element rf_chan_rel_ack <value> <location> <cell_desc> chg_cell_element rf_chan_rel_ack <value> <cell_desc> Display command strings disp_cell <cell_desc> ["full"] disp_element rf_chan_rel_ack <location> <cell_desc> Values Value type Integer (milliseconds) Valid range 0 to 1000000 Default value 5000 6-152 GMR-01 68P02901W23-P 23 Feb 2004 .rf_chan_rel_ack Chapter 6: Timer parameters 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). Technical Description BSS Command Reference rf_chan_rel_ack References Internal name MTCRM_RF_CHAN_REL_ACK This is a Motorola defined timer. 68P02901W23-P 23 Feb 2004 6-153 GMR-01 . rr_ny1_rep Chapter 6: Timer parameters 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. Type A (no operator actions) Supported by OMC-R GUI Yes Cell description required Yes Dependencies rr_t3105 Syntax Change command strings chg_element rr_ny1_rep <value> <location> <cell_desc> chg_cell_element rr_ny1_rep <value> <cell_desc> Display command strings disp_cell <cell_desc> ["full"] disp_element rr_ny1_rep <location> <cell_desc> Values Value type Integer (the amount of repetitions) Valid range 0 to 200 Default value 20 6-154 GMR-01 68P02901W23-P 23 Feb 2004 . 2: NY1 12.3.4.4.Technical Description BSS Command Reference rr_ny1_rep References Internal name TM_HO_NY1_REP GSM specification 4.2 4.8.20 .4.3.3.5. This is a Motorola defined timer.08 .4.11: NY1.08 . 68P02901W23-P 23 Feb 2004 6-155 GMR-01 .2. Syntax Change command strings chg_element rr_t3101 <value> <location> <cell_desc> chg_cell_element rr_t3101 <value> <cell_desc> Display command strings disp_cell <cell_desc> ["full"] disp_element rr_t3101 <location> <cell_desc> Values Value type Integer (milliseconds) Valid range 0 to 1000000 Default value 5000 (add_cell default) 6-156 GMR-01 68P02901W23-P 23 Feb 2004 .rr_t3101 Chapter 6: Timer parameters 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. Type A (no operator actions) Supported by OMC-R GUI Yes Cell description required Yes Dependencies The rr_t3101 value must be greater than the maximum length of time it takes for a Layer 2 establishment attempt. 68P02901W23-P 23 Feb 2004 6-157 GMR-01 .Technical Description BSS Command Reference rr_t3101 References GSM name T3101 GSM specification 4.08. 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.rr_t3103 Chapter 6: Timer parameters rr_t3103 Description The rr_t3103 timer specifies how long the BSS waits for an internal handover to complete. Type A (no operator actions) Supported by OMC-R GUI Yes Cell description required Yes Dependencies None Syntax Change command strings chg_element rr_t3103 <value> <location> <cell_desc> chg_cell_element rr_t3103 <value> <cell_desc> Display command strings disp_cell <cell_desc> ["full"] disp_element rr_t3103 <location> <cell_desc> Values Value type Integer (milliseconds) Valid range 0 to 1000000 Default value 30000 6-158 GMR-01 68P02901W23-P 23 Feb 2004 . 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. 1.08 .3.4 4.11.Technical Description BSS Command Reference rr_t3103 References GSM name T3103 GSM specification 4.2 68P02901W23-P 23 Feb 2004 6-159 GMR-01 .08 .4. The RSS uses this value to calculate the number of blocks to skip. only multiples of 20 are significant. If a value is entered that is not a 20 millisecond increment. Although the system accepts any value between 0 and 200. Values for this parameter should be entered in increments of 20 milliseconds. the BSS rounds the entered value to the nearest multiple of 20 that is less than the value entered.rr_t3105 Chapter 6: Timer parameters rr_t3105 Description The rr_t3105 parameter specifies the repetition between transmissions of the Physical Information messages during the handover procedure. This value is sent to the DRI. Type A (no operator actions) Supported by OMC-R GUI Yes Cell description required Yes Dependencies None Syntax Change command strings chg_element rr_t3105 <value> <location> <cell_desc> chg_cell_element rr_t3105 <value> <cell_desc> Display command strings disp_cell <cell_desc> ["full"] disp_element rr_t3105 <location> <cell_desc> Values Value type Select integer (milliseconds in 20 millisecond increments) Valid range 0 to 200 Default value 60 6-160 GMR-01 68P02901W23-P 23 Feb 2004 . 08 .3.2 12.5: T3105 68P02901W23-P 23 Feb 2004 6-161 GMR-01 .Technical Description BSS Command Reference rr_t3105 References Internal name TM_HO_T3105 GSM name T3105 GSM specification 4.8.2.5.4.20 .4. When the timer expires. Type A (no operator actions) Supported by OMC-R GUI No Cell description required No Dependencies The rr_t3109 value must be greater than the rr_t3111_sd and the rr_t3111_tch values. To ensure that the network does not put two MSs on the same dedicated channel. the CRM sends an RF channel release message to the RSS. Syntax Change command strings chg_element rr_t3109 <value> <location> chg_cell_element rr_t3109 <value> Display command strings disp_cell <cell_desc> ["full"] disp_element rr_t3109 <location> <cell_desc> 6-162 GMR-01 68P02901W23-P 23 Feb 2004 . The rr_t3109 timer must be set to a higher value than the CRM radio_link_timeout parameter (T100). The recommended rr_t3109 value is four 96-SACCH blocks (1. the network must hold onto a channel that has lost radio link long enough for the MS to release it.5 times the radio_link_timeout parameter value).rr_t3109 Chapter 6: Timer parameters rr_t3109 Description The rr_t3109 timer is used during the channel release procedure in case of a radio link timeout. 4.08 .2.08 .20 .5 : T3109.2 12.5 bts air timer .11. 11.Technical Description BSS Command Reference rr_t3109 Values Value type Integer (milliseconds) Valid range 0 to 1000000 Default value 14400 References GSM name T3109 GSM specification 4.air int BTS T4: T3109 68P02901W23-P 23 Feb 2004 6-163 GMR-01 .8.2.1.3.5. rr_t3111_sd Chapter 6: Timer parameters 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. This timer stops when the procedure completes. Syntax Change command strings chg_element rr_t3111_sd <value> <location> <cell_desc> chg_cell_element rr_t3111_sd <value> <cell_desc> Display command strings disp_cell <cell_desc> ["full"] disp_element rr_t3111_sd <location> <cell_desc> 6-164 GMR-01 68P02901W23-P 23 Feb 2004 . The rr_t3111_sd and rr_t3111_tch timers replace the rr_t3111 timer beginning in GRS4. The purpose is to allow some time for the possible repetition of the disconnection of the main signalling link. 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 value must be set equal to the value of T3110. The rr_t3111_sd timer causes the BSS to wait before the channel in question is allocated to another connection. Type A (no operator actions) Supported by OMC-R GUI Yes Cell description required Yes Dependencies The rr_t3111_sd value must be less than the rr_t3109 value. This timer starts whenever the BTS attempts to configure a hopping timeslot. air int BTS T5: T3111 68P02901W23-P 23 Feb 2004 6-165 GMR-01 .8.5 bts air timer .5 : T3111 4.11.5.20 .Technical Description BSS Command Reference rr_t3111_sd Values Value type Integer (milliseconds) Valid range 0 to 1000000 Default value 1500 References GSM name T3111 GSM specification 4. 11.2.3.2 12.2.08 .1.08 . The rr_t3111_tch timer causes the BSS to wait before the channel in question is allocated another connection. The rr_t3111_tch value must be set equal to the value of T3110. 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.rr_t3111_tch Chapter 6: Timer parameters 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. This timer stops when the procedure completes. The rr_t3111_sd and rr_t3111_tch timers replace the rr_t3111 timer beginning in GRS4. 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). Syntax Change command strings chg_element rr_t3111_tch <value> <location> <cell_desc> chg_cell_element rr_t3111_tch <value> <cell_desc> Display command strings disp_cell <cell_desc> ["full"] disp_element rr_t3111_tch <location> <cell_desc> 6-166 GMR-01 68P02901W23-P 23 Feb 2004 . Type A (no operator actions) Supported by OMC-R GUI Yes Cell description required Yes Dependencies The rr_t3111_tch value must be less than the rr_t3109 value. 5.air int BTS T5: T3111 68P02901W23-P 23 Feb 2004 6-167 GMR-01 .11.3.Technical Description BSS Command Reference rr_t3111_tch Values Value type Integer (milliseconds) Valid range 0 to 1000000 Default value 1500 References GSM parameter T3111 GSM technical specification 4.2.20 .5 : T3111 4.5 bts air timer .2.08 .08 .1. 11.8.2 12. rr_t3212 Chapter 6: Timer parameters 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 Type A (no operator actions) Supported by OMC-R GUI Yes Cell description required Yes Dependencies None Syntax Change command strings chg_element rr_t3212 <value> <location> <cell_desc> chg_cell_element rr_t3212 <value> <cell_desc> Display command strings disp_cell <cell_desc> ["full"] disp_element rr_t3212 <location> <cell_desc> Values Value type Integer (1 step = 6 minutes) Valid range 0 to 255 6-168 GMR-01 68P02901W23-P 23 Feb 2004 Technical Description BSS Command Reference 0 1 2 ... ... 255 Default value rr_t3212 0 minutes 6 minutes 12 minutes ... ... 1530 minutes (25.5 hours) 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 68P02901W23-P 23 Feb 2004 6-169 GMR-01 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. Type A (no operator actions) Supported by OMC-R GUI Yes Cell description required Yes 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 Change command strings chg_element rtry_cand_prd <timer length> <location> <cell_desc> chg_cell_element rtry_cand_prd <timer length> <cell_desc> Display command string disp_element rtry_cand_prd <location> <cell_desc> 6-170 GMR-01 68P02901W23-P 23 Feb 2004 Technical Description BSS Command Reference rtry_cand_prd Values Value type Integer (milliseconds) Valid range 0 to 1000000 Default value 4000 68P02901W23-P 23 Feb 2004 6-171 GMR-01 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. Type A (no operator actions) Supported by OMC-R GUI No Cell numbers required No Dependencies None Syntax Change command string chg_element sacch_info <value> <location> Display command string disp_element sacch_info <location> Values Value type Integer (milliseconds) Valid range 0 to 10000 Default value 2000 6-172 GMR-01 68P02901W23-P 23 Feb 2004 Technical Description BSS Command Reference sacch_info References Internal name TM_SACCH_INFO GSM specification 08.58 - 4.12 and 8.4.20 This is a Motorola defined timer. 68P02901W23-P 23 Feb 2004 6-173 GMR-01 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. Type A (no operator actions) Supported by OMC-R GUI No Cell numbers required No Dependencies None Syntax Change command string chg_element sccp_released <value> <location> Display command string disp_element sccp_released <location> Values Value type Integer (milliseconds) Valid range 0 to 1000000 Default value 30000 References Internal name SSM_MTL This is a Motorola defined timer. 6-174 GMR-01 68P02901W23-P 23 Feb 2004 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. Type A (no operator actions) Supported by OMC-R GUI No Cell numbers required No Dependencies None Syntax Change command string chg_element sccp_tconn_est <value> <location> Display command string disp_element sccp_tconn_est <location> Values Value type Integer (milliseconds) Valid range 0 to 1000000 Default value 30000 References Internal name TCONN_EST This is a Motorola defined timer. 68P02901W23-P 23 Feb 2004 6-175 GMR-01 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. If this timer expires, the call terminates. Type A (no operator actions) Supported by OMC-R GUI No Cell numbers required No 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 Change command string chg_element sccp_tiar <value> <location> Display command string disp_element sccp_tiar <location> Values Value type Integer (milliseconds) Valid range 0 to 1000000 Default value 30000 6-176 GMR-01 68P02901W23-P 23 Feb 2004 Technical Description BSS Command Reference sccp_tiar References Internal name SSM_TIAR GSM specification 8.08 - 3.2.3: all BSSMAP timers ITU-TSS (blue book) Q.714: TIAS, TIAR This is a Motorola defined timer. 68P02901W23-P 23 Feb 2004 6-177 GMR-01 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. Type A (no operator actions) Supported by OMC-R GUI No Cell numbers required No Dependencies The sccp_tias timer value must be less than the sccp_tiar timer value. Syntax Change command string chg_element sccp_tias <value> <location> Display command string disp_element sccp_tias <location> Values Value type Integer (milliseconds) Valid range 0 to 1000000 Default value 30000 6-178 GMR-01 68P02901W23-P 23 Feb 2004 Technical Description BSS Command Reference sccp_tias References Internal name SSM_TIAS GSM specification 8.08 - 3.2.3: all BSSMAP timers ITU-TSS (blue book) Q.714: TIAS, TIAR. This is a Motorola defined timer. 68P02901W23-P 23 Feb 2004 6-179 GMR-01 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. If this timer expires, the call terminates. Type A (no operator actions) Supported by OMC-R GUI No Cell numbers required No Dependencies None Syntax Change command string chg_element sccp_trel <value> <location> Display command string disp_element sccp_trel <location> Values Value type Integer (milliseconds) Valid range 4000 to 15000 Default value 10000 References GSM parameter TREL This is a Motorola defined parameter. 6-180 GMR-01 68P02901W23-P 23 Feb 2004 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. If this timer expires, the call terminates. Type A (no operator actions) Supported by OMC-R GUI No Cell numbers required No Dependencies None Syntax Change command string chg_element sm_audit_response <value> <location> Display command string disp_element sm_audit_response <location> Values Value type Integer (milliseconds) Valid range 0 to 1000000 Default value 30000 References Internal name SSM_MTX This is a Motorola defined parameter. 68P02901W23-P 23 Feb 2004 6-181 GMR-01 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. Type A (no operator actions) Supported by OMC-R GUI No Cell numbers required No Dependencies None Syntax Change command string chg_element spi <value> <location> Display command string disp_element spi <location> Values Value type Integer (milliseconds) Valid range 10000 to 1000000 Default value 60000 6-182 GMR-01 68P02901W23-P 23 Feb 2004 Technical Description BSS Command Reference spi References Internal name CLM_SPI_TIMER GSM name SPI GSM specification 8.08 section 3.1.15 This is a Motorola defined timer. 68P02901W23-P 23 Feb 2004 6-183 GMR-01 ss7_l2_t1 Chapter 6: Timer parameters ss7_l2_t1 Description The ss7_l2_t1 timer specifies the alignment ready timer. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required No Dependencies ss7_mode Syntax Change command string chg_element ss7_l2_t1 <value> <location> Display command string disp_element ss7_l2_t1 <location> Values Value type Integer (milliseconds) Valid range The range of values is dependent upon the value of the ss7_mode parameter Default value 40000 to 50000 If ss7_mode = 0 (ITU) 13000 to 30000 If ss7_mode = 1 (ANSI) 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-184 GMR-01 68P02901W23-P 23 Feb 2004 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-P 23 Feb 2004 6-185 GMR-01 ss7_l2_t2 Chapter 6: Timer parameters ss7_l2_t2 Description The ss7_l2_t2 timer specifies the not aligned timer. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required No Dependencies ss7_mode Syntax Change command string chg_element ss7_l2_t2 <value> <location> Display command string disp_element ss7_l2_t2 <location> Values Value type Integer (milliseconds) Valid range The range of values is dependent upon the value of the ss7_mode parameter Default value 5000 to 150000 If ss7_mode = 0 (ITU) 5000 to 30000 If ss7_mode = 1 (ANSI) The default value is dependent upon the value of the ss7_mode parameter. 25000 If ss7_mode = 0 (ITU) 23000 If ss7_mode = 1 (ANSI) 6-186 GMR-01 68P02901W23-P 23 Feb 2004 Technical Description BSS Command Reference ss7_l2_t2 The default value is set when the ss7_mode parameter value is changed. References Internal name T2 (ITU) GSM name T2 GSM specification ITU (blue book) Q.703 pg 72. 68P02901W23-P 23 Feb 2004 6-187 GMR-01 ss7_l2_t3 Chapter 6: Timer parameters ss7_l2_t3 Description The ss7_l2_t3 timer specifies the aligned timer. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required No Dependencies ss7_mode Syntax Change command string chg_element ss7_l2_t3 <value> <location> Display command string disp_element ss7_l2_t3 <location> Values Value type Integer (milliseconds) Valid range The range of values is dependent upon the value of the ss7_mode parameter Default value 1000 to 1500 If ss7_mode = 0 (ITU) 5000 to 14000 If ss7_mode = 1 (ANSI) The default value is dependent upon the value of the ss7_mode parameter. 1400 If ss7_mode = 0 (ITU) 11500 If ss7_mode = 1 (ANSI) 6-188 GMR-01 68P02901W23-P 23 Feb 2004 Technical Description BSS Command Reference ss7_l2_t3 The default value is set when the ss7_mode parameter value is changed. References Internal name T3 (ITU) GSM parameter T3 GSM technical specification ITU (blue book) Q.703 pg 72 68P02901W23-P 23 Feb 2004 6-189 GMR-01 ss7_l2_t4 Chapter 6: Timer parameters ss7_l2_t4 Description The ss7_l2_t4 timer specifies the emergency proving period timer. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required No Dependencies None Syntax Change command string chg_element ss7_l2_t4 <value> <location> Display command string disp_element ss7_l2_t4 <location> Values Value type Integer (milliseconds in increments of 5 milliseconds) Valid range 400 to 600 Default value 600 References Internal name T4 (ITU) GSM parameter T4 GSM technical specification ITU (blue book) Q.703 pg 72. 6-190 GMR-01 68P02901W23-P 23 Feb 2004 Technical Description BSS Command Reference ss7_l2_t5 ss7_l2_t5 Description The ss7_l2_t5 timer specifies the sending SIB timer. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required No Dependencies None Syntax Change command string chg_element ss7_l2_t5 <value> <location> Display command string disp_element ss7_l2_t5 <location> Values Value type Integer (milliseconds in increments of 5 milliseconds) Valid range 80 to 120 Default value 100 References Internal name T5 (ITU) GSM name T5 GSM technical specification ITU (blue book) Q.703 pg 72. 68P02901W23-P 23 Feb 2004 6-191 GMR-01 ss7_l2_t6 Chapter 6: Timer parameters ss7_l2_t6 Description The ss7_l2_t6 timer specifies the remote congestion timer. Type A (no operator action) Supported by OMC-R GUI Yes Cell numbers required No Dependencies ss7_mode Syntax Change command string chg_element ss7_l2_t6 <value> <location> Display command string disp_element ss7_l2_t6 <location> Values Value type Integer (milliseconds) Valid range The range of values is dependent upon the value of the ss7_mode parameter Default value 3000 to 6000 If ss7_mode = 0 (ITU) 1000 to 6000 If ss7_mode = 1 (ANSI) The default value is dependent upon the value of the ss7_mode parameter. 5000 If ss7_mode = 0 (ITU) 5000 If ss7_mode = 1 (ANSI) 6-192 GMR-01 68P02901W23-P 23 Feb 2004 Technical Description BSS Command Reference ss7_l2_t6 References Internal name T6 (ITU) GSM parameter T6 GSM technical specification ITU (blue book) Q.703 pg 72. 68P02901W23-P 23 Feb 2004 6-193 GMR-01 ss7_l2_t7 Chapter 6: Timer parameters 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. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required No Dependencies If pcr_enable is “on", ss7_l2_t7 must be greater than or equal to 800 milliseconds. Syntax Change command string chg_element ss7_l2_t7 <value> <location> Display command string disp_element ss7_l2_t7 <location> Values Value type Integer (milliseconds) Valid range 500 to 2000 Default value 1000 References Internal name T7 (ITU) GSM parameter T7 GSM technical specification ITU (blue book) Q.703 pg 72. 6-194 GMR-01 68P02901W23-P 23 Feb 2004 Technical Description BSS Command Reference ss7_l3_t1 ss7_l3_t1 Description The ss7_l3_t3 timer specifies the delay to avoid mis-sequencing on changeover timer. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required No Dependencies None Syntax Change command string chg_element ss7_l3_t1 <value> <location> Display command string disp_element ss7_l3_t1 <location> 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-P 23 Feb 2004 6-195 GMR-01 ss7_l3_t12 Chapter 6: Timer parameters ss7_l3_t12 Description The ss7_l3_t12 timer specifies the uninhibit acknowledgement timer. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required No Dependencies None Syntax Change command string chg_element ss7_l3_t12 <value> <location> Display command string disp_element ss7_l3_t12 <location> Values Value type Integer (milliseconds in 5 millisecond increments) Valid range 800 to 1500 Default value 1150 References Internal name T12_TIMER (ITU) GSM parameter T12 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 ) 6-196 GMR-01 68P02901W23-P 23 Feb 2004 Technical Description BSS Command Reference ss7_l3_t13 ss7_l3_t13 Description The ss7_l3_t13 timer specifies the force uninhibit timer. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required No Dependencies None Syntax Change command string chg_element ss7_l3_t13 <value> <location> Display command string disp_element ss7_l3_t13 <location> Values Value type Integer (milliseconds in 5 millisecond increments) Valid range 800 to 1500 Default value 1150 References Internal name T13_timer (ITU) GSM parameter T13 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-P 23 Feb 2004 6-197 GMR-01 ss7_l3_t14 Chapter 6: Timer parameters ss7_l3_t14 Description The ss7_l3_t14 timer sets the inhibition acknowledgement timer. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required No Dependencies None Syntax Change command string chg_element ss7_l3_t14 <value> <location> Display command string disp_element ss7_l3_t14 <location> Values Value type Integer (milliseconds in 5 millisecond increments) Valid range 2000 to 3000 Default value 2500 References Internal name T14_TIMER (ITU) GSM name T14 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 ) 6-198 GMR-01 68P02901W23-P 23 Feb 2004 Technical Description BSS Command Reference ss7_l3_t17 ss7_l3_t17 Description The ss7_l3_t17 timer specifies the time to wait to avoid oscillation of initial alignment failure and link restart timer. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required No Dependencies None Syntax Change command string chg_element ss7_l3_t17 <value> <location> Display command string disp_element ss7_l3_t17 <location> Values Value type Integer (milliseconds in 5 millisecond increments) Valid range 800 to 1500 Default value 1150 References Internal name T17_TIMER GSM parameter T17 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-P 23 Feb 2004 6-199 GMR-01 ss7_l3_t2 Chapter 6: Timer parameters ss7_l3_t2 Description The ss7_l3_t2 timer specifies the wait time for changeover acknowledgement timer. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required No Dependencies If pcr_enable is “on", ss7_l3_t2 must be greater than or equal to 1400 milliseconds. Syntax Change command string chg_element ss7_l3_t2 <value> <location> Display command string disp_element ss7_l3_t2 <location> Values Value type Integer (milliseconds in 5 millisecond increments) Valid range 700 to 2000 Default value 1400 References Internal name T2_TIMER GSM name T2 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 ) 6-200 GMR-01 68P02901W23-P 23 Feb 2004 Technical Description BSS Command Reference ss7_l3_t22 ss7_l3_t22 Description The ss7_l3_t22 timer specifies the local inhibit test timer. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required No Dependencies ss7_mode Syntax Change command string chg_element ss7_l3_t22 <value> <location> Display command string disp_element ss7_l3_t22 <location> Values Value type Integer (milliseconds in 5 millisecond increments) Valid range The range of values is dependent upon the value of the ss7_mode parameter. Default value 68P02901W23-P 23 Feb 2004 180000 to 360000 If ss7_mode = 0 (ITU) 90000 to 120000 If ss7_mode = 1 (ANSI) The default value is dependent upon the value of the ss7_mode parameter. 270000 If ss7_mode = 0 (ITU) 90000 If ss7_mode = 1 (ANSI) 6-201 GMR-01 ss7_l3_t22 Chapter 6: Timer parameters The default value is set when the ss7_mode parameter value is changed. References Internal name T22_TIMER GSM name T22 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 ) 6-202 GMR-01 68P02901W23-P 23 Feb 2004 Default value 68P02901W23-P 23 Feb 2004 180000 to 360000 If ss7_mode = 0 (ITU) 90000 to 120000 If ss7_mode = 1 (ANSI) The default value is dependent upon the value of the ss7_mode parameter. 270000 If ss7_mode = 0 (ITU) 90000 If ss7_mode = 1 (ANSI) 6-203 GMR-01 . Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required No Dependencies ss7_mode Syntax Change command string chg_element ss7_l3_t23 <value> <location> Display command string disp_element ss7_l3_t23 <location> Values Value type Integer (milliseconds in 5 millisecond increments) Valid range The range of values is dependent upon the value of the ss7_mode parameter.Technical Description BSS Command Reference ss7_l3_t23 ss7_l3_t23 Description The ss7_l3_t23 timer specifies the remote inhibit test timer. T2 (SLT_T1.704 pgs 196 -197 ITU (blue book) Q.ss7_l3_t23 Chapter 6: Timer parameters The default value is set when the ss7_mode parameter value is changed. SLT_T2 ) 6-204 GMR-01 68P02901W23-P 23 Feb 2004 .707 pg 349: supervision timers T1. References Internal name T23_TIMER GSM parameter T23 GSM technical specification ITU (blue book) Q. SLT_T2 ) 68P02901W23-P 23 Feb 2004 6-205 GMR-01 . Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required No Dependencies None Syntax Change command string chg_element ss7_l3_t4 <value> <location> Display command string disp_element ss7_l3_t4 <location> Values Value type Integer (milliseconds in 5 millisecond increments) Valid range 500 to 1200 Default value 850 References Internal name T4_TIMER GSM name T4 GSM technical specification ITU (blue book) Q.707 pg 349: supervision timers T1.704 pgs 196-197 ITU (blue book) Q.Technical Description BSS Command Reference ss7_l3_t4 ss7_l3_t4 Description The ss7_l3_t4 timer specifies the waiting for changeback acknowledgement (first attempt) timer. T2 (SLT_T1. ss7_l3_t5 Chapter 6: Timer parameters ss7_l3_t5 Description The ss7_l3_t5 timer specifies the waiting for changeback acknowledgement (second attempt) timer. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required No Dependencies None Syntax Change command string chg_element ss7_l3_t5 <value> <location> Display command string disp_element ss7_l3_t5 <location> Values Value type Integer (milliseconds in 5 millisecond increment) Valid range 500 to 1200 Default value 850 References Internal name T5_TIMER GSM parameter T5 GSM technical specification ITU (blue book) Q.707 pg 349: supervision timers T1.704 pgs 196-197 ITU (blue book) Q. SLT_T2 ) 6-206 GMR-01 68P02901W23-P 23 Feb 2004 . T2 (SLT_T1. 707 pg 349: supervision timers T1. T2 (SLT_T1.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. SLT_T2 ) 68P02901W23-P 23 Feb 2004 6-207 GMR-01 .704 pgs 196-197 ITU (blue book) Q. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required No Dependencies None Syntax Change command string chg_element ss7_slt_t1 <value> <location> Display command string disp_element ss7_slt_t1 <location> Values Value type Integer (milliseconds in 5 millisecond increments) Valid range 4000 to 12000 Default value 8000 References Internal name SLT_T1_TIMER GSM name T1 GSM technical specification ITU (blue book) Q. 6-208 GMR-01 68P02901W23-P 23 Feb 2004 . The typical value for this timer is 1000 milliseconds. The value selected must give the CRM enough time to answer a request from the CLM when the system is coming out of reset.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. Type A (no operator actions) Supported by OMC-R GUI No Cell numbers required No Dependencies None Syntax Change command string chg_element start_ack <value> <location> Display command string disp_element start_ack <location> Values Value type Integer (milliseconds) Valid range 0 to 1000000 Default value 30000 References Internal name CLM_MTJ1 This is a Motorola defined timer. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required No Dependencies The GPRS feature must be unrestricted.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. Syntax Change command string chg_element static_sync_timer <value> <location> Display command string disp_element static_sync_timer <location> 68P02901W23-P 23 Feb 2004 6-209 GMR-01 . GCI error clear threshold and Static Sync Timer parameters. Uplink Sync Timer and Static Sync Timer to be modified so that one site reset is required for all to be changed. The BSS allows the values of the Initial Sync Timer. Downlink Sync Timer. The GPRS feature restricts the modifications of the GPRS Alarm Increment/Decrement Time Period. Static time alignment is necessary before the channel coder can process data. GCI error generation threshold. GCI error increment. BSS software processes using this parameter are not notified when this parameter is changed. 001 second . 65... 12000 .... 12 seconds .. 65535 Default value 0 seconds 0.535 seconds 0 milliseconds 1 millisecond 12000 milliseconds 65535 milliseconds 12000 6-210 GMR-01 68P02901W23-P 23 Feb 2004 .static_sync_timer Chapter 6: Timer parameters Values Value type Integer (milliseconds) Valid range 1 to 65535 0 1 ... 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.714. This is a Motorola defined timer.2. 68P02901W23-P 23 Feb 2004 6-211 GMR-01 . This timer is also known as clm_t_stat_info in some Motorola documentation.4. Section 5.3. Type A (no operator action) Supported by OMC-R GUI Cell numbers required No Dependencies None Syntax Change command string chg_element t_stat_info <value> <location> Display command string disp_element t_stat_info <location> Values Value type Integer (milliseconds) Valid range 0 to 1000000 Default value 900000 References GSM specification Q. Resetting the site generates several alarms. The BSS allows the values of the initial_sync_timer. gci_error_gen_threshold. However. 6-212 GMR-01 68P02901W23-P 23 Feb 2004 . gci_error_inc. gci_error_clr_threshold and static sync timer parameters. these alarms are blocked by the system. 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. It can be used at a BTS. The GPRS feature restricts the modifications of the gprs_alarm_time period.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. Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required No Dependencies This parameter is not allowed at a stand-alone BSC or RXCDR. 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. Display command string disp_element uplink_sync_timer <location> This parameter can be used at a BTS. Syntax Change command string chg_element uplink_sync_timer <value> <location> A site reset occurs when the value of uplink_sync_timer is changed in SYSGEN OFF mode. Technical Description BSS Command Reference uplink_sync_timer Values Value type Integer (milliseconds) Valid range 1000 to 3000 Default value 1000 68P02901W23-P 23 Feb 2004 6-213 GMR-01 . Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required Yes Dependencies The ho_exist_congest parameter must be enabled.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. Syntax Change command strings chg_element valid_candidate_period <value> <location> <cell_desc> chg_cell_element valid_candidate_period <value> <cell_desc> Display command string disp_element valid_candidate_period <location> <cell_desc> Values Value type Integer (milliseconds) Valid range 1 to 1000000 Default value 4000 6-214 GMR-01 68P02901W23-P 23 Feb 2004 . using the presentation layout as detailed in the Device and function database parameters presentation section at the start of this chapter.Chapter 7 Device/function parameters Device and function database parameters are BSS parameters. associated with equipped devices and functions. 68P02901W23-P 23 Feb 2004 7-1 GMR-01 . refer to the command description under "modify_value" on page 2-402. In this chapter the device/function database parameters are described in alphabetical order. that can be modified. For detailed information on the modify_value command. The modify_value command is used to modify parameters on devices and functions that have been equipped using the equip command. Parameter reference The actual parameter reference appears at the head of the page containing the reference information. 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 CBL Cell Broadcast Link COMB COMBiner DHP Digital Host Processor DRI Digital Radio Interface DYNET Dynamic Network EAS External Alarm System GBL Gb Link GCLK Generic CLocK board LCF Link Control Function MMS Multiple serial interface link 7-2 GMR-01 68P02901W23-P 23 Feb 2004 . 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 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. Device/Function This sub-section indicates the devices or functions from the following list. and is reproduced in the contents and the index of this manual. The specific action required is described in the Operator actions field. Operator actions This sub-section lists specific actions required when changing Type B parameters. using a PC connected to the master GPROC. Dependencies This sub-section describes any database internal or external dependencies which may affect value assignments of the database parameter.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. Syntax This section provides the syntax of the change and display command strings for the particular device/function database parameter. If a value is not supported via the OMC-R GUI. OMC-R GUI support This sub-section indicates whether the database element value may be changed via the OMC-R GUI (Graphics User Interface). and includes any precautions that are appropriate. 68P02901W23-P 23 Feb 2004 7-3 GMR-01 . 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. 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. These dependencies must be considered when changes are made to the parameter. it can be changed by performing a remote login (rlogin) from the OMC-R. or at the site. 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. the parameter name. The original value of the parameter remains unchanged. and the location affected are included in the command syntax. indices (if required). indices (if required). Boolean. text or alphanumeric and. The command name. Display command strings This sub-section contains the disp_equipment command syntax used to display the database element value. This default value may only be displayed by using the disp_equipment command before the database parameter is changed for the first time. if required. the parameter name. Values This section lists the value types and valid ranges for the database values for the particular parameter. the new element value. The command name. Some parameters are assigned default values when the database is initially loaded. Value type This sub-section indicates whether the parameter database value is an integer. • equip command syntax which is included where an element is initially assigned using the equip command and modified using the modify_value command. 7-4 GMR-01 68P02901W23-P 23 Feb 2004 .Device and function database parameters presentation Chapter 7: Device/function parameters Change command strings 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. If an invalid value is entered when using the modify_value command. Value range This sub-section indicates the range of the parameter database value. the command is abandoned and an error message presented. and the location are included in the command syntax. what the value represents. The default value may be changed by using the appropriate modify_value command. The individual equip command prompts are listed in the equip command description "equip" on page 2-327. Device/Function DRI Type B (operator actions required) Supported by OMC-R GUI Yes Cell numbers required No Dependencies The transceiver must be locked when modifying this parameter. Use of all locations option No Syntax Change command strings modify_value <location> antenna_select <value> dri <dev_fun_id1> <dev_fun_id2> <dev_fun_id3> equip <location> dri Display command string disp_equipment <location> dri <id1> <id2> <id3> Values Value type Integer Valid range 1 to 6 Default value None 68P02901W23-P 23 Feb 2004 7-5 GMR-01 .Technical Description BSS Command Reference antenna_select antenna_select Description The antenna_select parameter specifies the first antenna attached to a transceiver. Operator actions Lock the transceiver before modifying this parameter. 7-6 GMR-01 68P02901W23-P 23 Feb 2004 .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. Device/Function MMS Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required No Dependencies None Use of all locations option Yes Syntax Change command string modify_value <location> ber_oos_mon_period <value> mms <dev_fun_id1> <dev_fun_id2> <dev_fun_id3> Display command string disp_equipment <location> mms <id1> <id2> <id3> An additional check is performed while displaying an MMS. The default value for this parameter is assigned when MMSs are equipped automatically on the equipping of an MSI.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). This parameter is available for MMSs equipped from GPRS PMC MSIs. 68P02901W23-P 23 Feb 2004 7-7 GMR-01 . If the MSI type of the MMS is RF_UNIT. ber_oos_mon_period is not displayed. ber_oos_mon_period Chapter 7: Device/function parameters Values Value type Integer (seconds) Valid range 1 to 60 Default value 8 7-8 GMR-01 68P02901W23-P 23 Feb 2004 . 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. 68P02901W23-P 23 Feb 2004 7-9 GMR-01 . This parameter is available for MMSs equipped from GPRS PMC MSIs. Device/Function MMS Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required No Dependencies None Use of all locations option Yes Syntax Change command string modify_value <location> ber_restore_mon_period <value> mms <dev_fun_id1> <dev_fun_id2> <dev_fun_id3> Display command string disp_equipment <location> mms <id1> <id2> <id3> An additional check is performed while displaying an MMS.000001 Bit Error Rate (BER) before it is put in service. ber_restore_mon_period is not displayed. If the MSI type of the MMS is RF_UNIT. The default value for this parameter is assigned when MMSs are equipped automatically on the equipping of an MSI. ber_restore_mon_period Chapter 7: Device/function parameters Values Value type Integer (100 milliseconds) Valid range 0 to 18000 Default value 600 7-10 GMR-01 68P02901W23-P 23 Feb 2004 . 68P02901W23-P 23 Feb 2004 7-11 GMR-01 .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 Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required No Dependencies This parameter only applies to the BSC. Syntax Change command strings modify_value 0 bsc_cbc_operator "<value>" cbl <dev_fun_id1> <dev_fun_id2> <dev_fun_id3> equip <location> cbl Display command string 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. 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 Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required No 7-12 GMR-01 68P02901W23-P 23 Feb 2004 . Horizonmicro (M-Cellarena) or Horizoncompact (M-Cellarenamacro) to M-Cellmicro if any MSIs of type niu_hdsl are equipped at the M-Cellcity. If a cabinet type of Horizonmicro (M-Cellarena) or Horizoncompact (M-Cellarenamacro) is entered during CAB device equipage.Technical Description BSS Command Reference Dependencies cabinet_type When changing the cabinet type. or if there are any MSI devices with a first device id greater than 1. then the CAB ID entered must be 0 if CAB device 0 does not yet exist. to M-Cellcity or M-Cellmicro if frequency hopping is enabled at the site. The bts_type per SITE element is set to 1 upon equipage of a slave Horizon micro or Horizoncompact CAB device. The cabinet type may not be modified to M-Cell2 if there are any MSI devices equipped in slots other than 0. If a modify_value command from M-Cellcity. Syntax Change command strings equip <location> cab modify_value <location> cabinet_type <value> cab <dev_fun_id1> <dev_fun_id2> <dev_fun_id3> Display command string disp_equipment <location> cab <id1> <id2> <id3> 68P02901W23-P 23 Feb 2004 7-13 GMR-01 . Horizoncompact (M-Cellarenamacro). A DRI that uses an FMUX as the TCU connection type cannot be equipped to a TCU_2 cabinet. Horizonmicro (M-Cellarena) or Horizoncompact (M-Cellarenamacro) to M-Cellmicro is accepted. The valid CAB ID range at a Horizonmicro BTS site is 0 to 2. Horizonmicro (M-Cellarena) or Horizoncompact (M-Cellarenamacro) sites. A mismatch during a hard reset causes the BTS to remain OOS. The system rejects an attempt to alter the cabinet type from M-Cellcity. When modifying this parameter ensure that the cabinet_type is compatible with the hardware board type. the new cabinet type must be in the same cabinet group as the old cabinet type. The system rejects the modify_value cabinet_type command if the change is from TCU_6 to TCU_2. all the hdsl parameters initially set by the chg_element command are set to their defaults. and the cabinet has at least one DRI equipped via the FMUX. The cabinet type may not be modified from Horizonmicro (M-Cellarena). without any delimiters) Valid range 0 to 25 Default value 0 bts4d_48v 1 bts4d_27v 2 bssc_48v 3 bssc_27v 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 None 7-14 GMR-01 68P02901W23-P 23 Feb 2004 .cabinet_type Chapter 7: Device/function parameters Values Value type Integer or alphanumeric (entered as an alphanumeric string. 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. the combiner_id and cavity number are required and will be prompted. the existing values can be used as defaults. Device/Function DRI Type A (no operator actions) Supported by OMC-R GUI No Cell numbers required No Dependencies If the combining_type is 0. If these values have already been specified. the combiner_id and cavity values are considered invalid and no modifications are allowed. Syntax Change command strings modify_value <location> cavity <value> dri <dev_fun_id1> <dev_fun_id2> equip <location> dri Display command string disp_equipment <location> dri <id1> <id2> Values Value type Integer Valid range 0 to 5 Default value None 68P02901W23-P 23 Feb 2004 7-15 GMR-01 . All affected devices must be locked. If the combining_type is 1 or 2. cbc_operator Chapter 7: Device/function parameters cbc_operator Description The cbc_operator parameter specifies the CBC operator. 7-16 GMR-01 68P02901W23-P 23 Feb 2004 . Device/Function CBL Type A (no operator actions) Supported by OMC-R GUI No Cell numbers required No Dependencies This parameter only applies to the BSC. Use of all locations option No Syntax Change command strings modify_value 0 cbc_operator "<value>" cbl <dev_fun_id1> <dev_fun_id2> <dev_fun_id3> equip 0 cbl Display command string 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. Only non-BCCH carriers can be configured in the inner zone.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. The RTF cycles if the change is made in SYSGEN OFF mode. Display command string disp_equipment <location> rtf <id1> <id2> <id3> 68P02901W23-P 23 Feb 2004 7-17 GMR-01 . If the inner_zone_alg is disabled in a cell and a carrier is equipped in the inner zone. Device/Function RTF Type A (no operator actions) Supported by OMC-R GUI Yes Cell description required No Dependencies The Concentric Cells feature must be enabled and inner_zone_alg must be set to other than 0. If the GPRS feature is in use. or changed to the inner zone. the system displays a warning message. GPRS carriers must be in the outer zone of a concentric cell. Use of all locations option Yes Syntax Change command strings modify_value <location> cell_zone <value> rtf <dev_fun_id1> <dev_fun_id2> <dev_fun_id3> equip <location> rtf The system displays a warning message if the cell_zone value for an RTF is changed in SYSGEN OFF mode. cell_zone Chapter 7: Device/function parameters Values Value type Boolean Valid range 0 or 1 Default value 0 Outer zone 1 Inner zone 0 7-18 GMR-01 68P02901W23-P 23 Feb 2004 . A channel from the highest priority carrier matching the requested interference band is allocated to a channel request. Device/Function RTF Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required No Dependencies None Use of all locations option No Syntax Change command strings modify_value <location> chan_alloc_priority <value> rtf <dev_fun_id1> <dev_fun_id2> <dev_fun_id3> equip <location> rtf Display command string disp_equipment <location> rtf <id1> <id2> <id3> Values Value type Integer Valid range 0 to 250 Default value 68P02901W23-P 23 Feb 2004 0 Highest priority 250 Lowest priority 0 7-19 GMR-01 .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. Device/Function AXCDR Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required No Dependencies None Use of all locations option No Syntax Change command strings modify_value <location> cic_validation <value> AXCDR <axcdr_id> equip <location> axcdr Display command string disp_equipment <location> axcdr <cic_id> Values Value type Text Valid range yes or no Default value yes Enabled no Disabled no 7-20 GMR-01 68P02901W23-P 23 Feb 2004 .cic_validation Chapter 7: Device/function parameters cic_validation Description The cic_validation parameter enables or disables CIC validation. Syntax Change command strings modify_value <location> clkx0 <value> gclk <gclk_id> equip <location> gclk Display command string disp_equipment <location> gclk <id1> 68P02901W23-P 23 Feb 2004 7-21 GMR-01 . EXP KSWX or remote KSWX card. the CLKX board should be in slot U4. For GCLK 0. For GCLK 1. Device/Function GCLK Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required No Dependencies None Use of all locations option No 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. the CLKX board should be in slot U7. The system rejects the change if the new card would occupy a slot that is already occupied.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. clkx0 Chapter 7: Device/function parameters Values Value type Text Valid range yes or no Default value yes Present no Not present no 7-22 GMR-01 68P02901W23-P 23 Feb 2004 . For GCLK 0. the CLKX board should be in slot U6. Syntax Change command strings modify_value <location> clkx1 <value> gclk gclk_id> equip <location> gclk Display command string disp_equipment <location> gclk <id1> 68P02901W23-P 23 Feb 2004 7-23 GMR-01 . The system checks the contents of these slots every time a change implies the existence of a new CLKX.Technical Description BSS Command Reference clkx1 clkx1 Description The clkx1 parameter specifies whether or not a CLKX (Clock Extender) half-size board is present for this GCLK (Generic Clock) board. Device/Function GCLK Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required No Dependencies None Operator actions None Use of all locations option No Slots U2 through U7 can contain CLKX cards or KSWX cards. the CLKX board should be in slot U3. The system rejects the change if the new card would occupy a slot that is already occupied. EXP KSWX or remote KSWX card. For GCLK 1. clkx1 Chapter 7: Device/function parameters Values Value type Text Valid range yes or no Default value yes Present no Not present no 7-24 GMR-01 68P02901W23-P 23 Feb 2004 . Technical Description BSS Command Reference clkx2 clkx2 Description The clkx2 parameter specifies whether or not a CLKX (Clock Extender) half-size board is present for this GCLK (Generic Clock) board. EXP KSWX or remote KSWX card. The system checks the contents of these slots every time a change implies the existence of a new CLKX. the CLKX board should be in slot U5. For GCLK 0. the CLKX board should be in slot U2. Syntax Change command strings modify_value <location> clkx2 <value> gclk <gclk_id> equip <location> gclk Display command string disp_equipment <location> gclk <id1> 68P02901W23-P 23 Feb 2004 7-25 GMR-01 . Device/Function GCLK Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required No Dependencies None Use of all locations option No Slots U2 through U7 can contain CLKX cards or KSWX cards. For GCLK 1. The system rejects the change if the new card would occupy a slot that is already occupied. clkx2 Chapter 7: Device/function parameters Values Value type Text Valid range yes or no Default value yes Present no Not present no 7-26 GMR-01 68P02901W23-P 23 Feb 2004 . Technical Description BSS Command Reference combiner_address combiner_address Description The combiner_address parameter specifies the message routing address for the Combiner (COMB). Use of all locations option No Syntax Change command strings modify_value <location> combiner_address <value> comb <dev_fun_id1> <dev_fun_id2> equip <location> comb Display command string disp_equipment <location> comb <id1> <id2> Values Value type Integer Valid range 0 to 255 Default value None 68P02901W23-P 23 Feb 2004 7-27 GMR-01 . All affected devices must be locked. Device/Function COMB Type A (no operator actions) Supported by OMC-R GUI No Cell numbers required No Dependencies The address must be unique within a site. All affected devices must be locked. the combiner_id and cavity number are required and will be prompted.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. the combiner_id and cavity values are considered invalid and no modifications are allowed. If the combining_type is 1 or 2. Use of all locations option No Syntax Change command strings modify_value <location> combiner_id <value> dri <dev_fun_id1> <dev_fun_id2> equip <location> dri Display command string disp_equipment <location> dri <id1> <id2> Values Value type Integer Valid range 0 to 13 Default value None 7-28 GMR-01 68P02901W23-P 23 Feb 2004 . Device/Function DRI Type A (no operator actions) Supported by OMC-R GUI No Cell numbers required No Dependencies If the combining_type is 0. If these values have already been specified. the existing values can be used as defaults. Technical Description BSS Command Reference combining_type combining_type Description The combining_type parameter specifies what type of combining is associated with each DRI. All affected devices must be locked. the combiner_id and cavity number are required and will be prompted. If the combining_type is 1 or 2. If these values have already been specified. Use of all locations option No Syntax Change command strings modify_value <location> combining_type <value> dri <dev_fun_id1> <dev_fun_id2> equip <location> dri Display command string disp_equipment <location> dri <id1> <id2> Values Value type Integer Valid range 0 to 2 68P02901W23-P 23 Feb 2004 7-29 GMR-01 . the combiner_id and cavity values are considered invalid and no modifications are allowed. the existing values can be used as defaults. Device/Function DRI Type A (no operator actions) Supported by OMC-R GUI No Cell numbers required No Dependencies If the combining_type is 0. combining_type Chapter 7: Device/function parameters 0 1 2 Default value None Non-controlling Controlling 0 7-30 GMR-01 68P02901W23-P 23 Feb 2004 . “single" or “double" Default value 68P02901W23-P 23 Feb 2004 1 or “single" single density mode 2 or “double" double density mode None 7-31 GMR-01 . Device/Function DRI Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required No Dependencies A number of existing parameters that can be modified under the DRI device are affected by the double density DRI devices. Syntax Change command strings equip <location> dri modify_value <location> dri_density <value> dri <dev_fun_id1> <dev_fun_id2> <dev_fun_id3> Display command string disp_equipment <location> dri <id1> <id2> <id3> Values Value type Integer or text Valid range 1 or 2. 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.Technical Description BSS Command Reference dri_density dri_density Description The dri_density parameter specifies the density mode (single or double). Use of all locations option No Syntax Change command strings 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. 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.ext_timeslots Chapter 7: Device/function parameters ext_timeslots Description The ext_timeslots parameter specifies the number of extended range timeslots for an RTF. Display command string disp_equipment <location> rtf <id1> <id2> [<id3>] 7-32 GMR-01 68P02901W23-P 23 Feb 2004 . the number of extended range timeslots for the BCCH RTF must support the number of configured BCCH. The RTF cycles when the ext_timeslots value is modified in SYSGEN OFF mode . Device/Function RTF Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required No Dependencies The number of extended range timeslots can be changed only if the Extended Range Cells feature is unrestricted. and SDCCH channels. The number of extended range timeslots cannot be modified for inner-zone carriers. CCCH. Technical Description BSS Command Reference ext_timeslots Values Value type Integer Valid range 0 to 4 Default value 0 68P02901W23-P 23 Feb 2004 7-33 GMR-01 . Use of all locations option No Syntax Change command strings modify_value <location> fm_cell_type <value> dri <dev_fun_id1> <dev_fun_id2> <dev_fun_id3> equip <location> dri Display command string disp_equipment <location> dri <id1> <id2> <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 GMR-01 68P02901W23-P 23 Feb 2004 .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. Operator actions Lock the DRI/RCU before modifying this parameter. See the table of values below. Device/Function DRI Type B (operator actions required) Supported by OMC-R GUI Yes Cell numbers required No Dependencies Setting of this parameter depends on the setting of diversity_flag . 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-P 23 Feb 2004 7-35 GMR-01 . Valid frequency types at a BSS can be modified or displayed by the freq_types_allowed command.frequency_type Chapter 7: Device/function parameters frequency_type Description The frequency_type parameter specifies the frequencies allowed for a cabinet. Operator actions To delete a frequency type. the system must first be put in SYSGEN ON mode. Device/Function CAB Type A (but see Operator actions below) Supported by OMC-R GUI Yes Cell numbers required No Dependencies If any of the frequency types specified are not valid at the BSS. the system rejects the modify_value command. • Frequencies can be added but not deleted in SYSGEN OFF mode. • Frequency_types can be added and deleted in SYSGEN ON mode. Use of all locations option Yes Syntax Change command string modify_value <location> frequency_type <freq_type> cab <id1> [<id2>] [<id3>] Display command string disp_equipment <location> cab <id1> [<id2>] [<id3>] 7-36 GMR-01 68P02901W23-P 23 Feb 2004 . as follows: Valid range 1 to 15 Default value 68P02901W23-P 23 Feb 2004 1 PGSM 2 EGSM 3 PGSM and EGSM 4 DCS1800 5 PGSM and DCS1800 6 EGSM and DCS1800 7 PGSM. DCS1800 and PCS1900 14 EGSM.Technical Description BSS Command Reference frequency_type Values Value type Integer representing one or more frequency types. DCS1800 and PCS1900 None 7-37 GMR-01 . EGSM and PCS1900 12 DCS1800 and PCS1900 13 PGSM. EGSM. EGSM and DCS1800 8 PCS1900 9 PGSM and PCS1900 10 EGSM and PCS1900 11 PGSM. DCS1800 and PCS1900 15 PGSM. The hdsl_modem_setting value cannot be modified for a GPRS PCU MMS.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 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. then equipping the PATH devices. This parameter may only be changed on MMS devices with a protocol type of HDSL equipped as msi_type of niu_hdsl. This parameter may only be changed at an M-Cellcity. Device/Function MMS Type B (operator actions required) Supported by OMC-R GUI Yes Cell numbers required No Dependencies This parameter may only be changed if the HDSL option is unrestricted. Changing this parameter updates the MCU FLASH memory values. Operator actions MMS must be locked. Horizonmicro or Horizoncompact site. Use of all locations option No Syntax Change command strings modify_value <location> hdsl_modem_setting <value> mms <mms_id1> <mms_id2> equip <location> msi Display command string disp_equipment <location> mms <mms_id1> <mms_id2> 7-38 GMR-01 68P02901W23-P 23 Feb 2004 . The possible settings are slave and master. altering the values. Technical Description BSS Command Reference hdsl_modem_setting Values Value type Text Valid range slave or master Default value master 68P02901W23-P 23 Feb 2004 7-39 GMR-01 . and equipped on an msi_type of niu_hdsl. the HDSL link is taken out of service. All slave modem alarm thresholds are identical to the master modem alarm thresholds. The default value for this parameter is automatically assigned when the MSI is equipped. If the SNR level falls below this threshold for more than the period specified by the hdsl_oos_mon_period device parameter. Device/Function MMS Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required No Dependencies This parameter may only be changed if the HDSL option is unrestricted. This parameter may only be changed on MMS devices with a protocol type of HDSL. Use of all locations opt ion No Syntax Change command string modify_value <location> hdsl_oos_mon_period <value> mms <dev_fun_id1> <dev_fun_id2> <dev_fun_id3> Display command string disp_equipment <location> mms <id1> <id2> <id3> 7-40 GMR-01 68P02901W23-P 23 Feb 2004 . This parameter may only be changed at an M-Cellcity. The hdsl_oos_mon_period value cannot be modified for a GPRS PCU MMS. a modem setting of master. Horizonmicro or Horizoncompact site.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. Technical Description BSS Command Reference hdsl_oos_mon_period Values Value type Integer (seconds) Valid range 0 to 3598 Default value 20 68P02901W23-P 23 Feb 2004 7-41 GMR-01 . If the SNR level is maintained above this threshold for more than the period specified by the hdsl_restore_mon_period device parameter. This parameter may only be changed on MMS devices with a protocol type of HDSL. All slave modem alarm thresholds are identical to the master modem alarm thresholds. and equipped on an msi_type of niu_hdsl. The hdsl_restore_mon_period value cannot be modified for a GPRS PCU MMS. Device/Function MMS Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required No Dependencies This parameter may only be changed if the HDSL option is unrestricted. The default value for this parameter is automatically assigned when the MSI is equipped. the HDSL link is brought back into service.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. a modem setting of master. Use of all locations option No Syntax Change command string modify_value <location> hdsl_restore_mon_period <value> mms <dev_fun_id1> <dev_fun_id2> <dev_fun_id3> Display command string disp_equipment <location> mms <id1> <id2> <id3> 7-42 GMR-01 68P02901W23-P 23 Feb 2004 . Horizonmicro or Horizoncompact site. This parameter may only be changed at an M-Cellcity. Technical Description BSS Command Reference hdsl_restore_mon_period Values Value type Integer (seconds) Valid range 0 to 65534 Default value 20 68P02901W23-P 23 Feb 2004 7-43 GMR-01 . ias_connected Chapter 7: Device/function parameters ias_connected Description The ias_connected parameter enables or disables internal alarms system (IAS). Device/Function CAGE Type A (no operator actions) Supported by OMC-R GUI Yes Cell description required No Dependencies None Use of all locations option No Syntax Change command strings modify_value <location> ias_connected <value> cage <id1> equip <location> cage Display command string disp_equipment <location> cage <id1> <id2> <id3> Values Value type Text Valid range yes or no Default value yes Enabled no Disabled None 7-44 GMR-01 68P02901W23-P 23 Feb 2004 . None 7-45 GMR-01 . Use of all locations option No Syntax Change command strings modify_value <location> int_antenna <value> cab <dev_fun_id1> <dev_fun_id2> <dev_fun_id3> equip <location> cab Display command string disp_equipment <location> cab <id1> <id2> <id3> Values Value type Text Valid range yes or no Default value 68P02901W23-P 23 Feb 2004 yes Internal antenna is present and should be used. and Horizonmicro cabinets.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 Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required No Dependencies This parameter is only allowed for M-Cellcity M-Cellarena. no Internal antenna is not present. 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. M-Cellarena. Horizonmicro and Horizoncompact cabinets. Device/Function CAB Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required No Dependencies This parameter is only allowed for M-Cellcity. Use of all locations option No Syntax Change command strings modify_value <location> int_hdsl_modem <value> cab <dev_fun_id1> <dev_fun_id2> <dev_fun_id3> equip <location> cab Display command string disp_equipment <location> cab <id1> <id2> <id3> Values Value type Text Valid range yes or no Default value yes Present no Not present None 7-46 GMR-01 68P02901W23-P 23 Feb 2004 . XBL Type B (operator actions required) Supported by OMC-R GUI Yes Cell description required No Dependencies None Operator actions The operator needs to cycle (lock and then unlock) the device for the change to take effect. Device/Function RSL. Both ends of the link reinitialize when this value is modified for RSL.Technical Description BSS Command Reference lapd_k lapd_k Description The lapd_k parameter specifies the maximum number of unacknowledged LAPD information frames. Use of all locations option Yes Syntax Add/Change command strings modify_value <location> lapd_k <value> rsl <dev_fun_id1> <dev_fun_id2> <dev_fun_id3> modify_value <location> lapd_k <value> xbl <dev_fun_id1> <dev_fun_id2> <dev_fun_id3> equip <location> rsl equip <location> xbl Display command strings disp_equipment <location> rsl <id1> <id2> <id3> disp_equipment <location> xbl <id1> <id2> <id3> 68P02901W23-P 23 Feb 2004 7-47 GMR-01 . lapd_k Chapter 7: Device/function parameters Values Value type Integer Valid range 1 to 10 Default value 7 7-48 GMR-01 68P02901W23-P 23 Feb 2004 . XBL Type B (operator actions required) Supported by OMC-R GUI Yes Cell description required No Dependencies None Operator actions The operator needs to cycle (lock and then unlock) the device for the change to take effect. Use of all locations option Yes Syntax Add/Change command strings modify_value <location> lapd_n200 <value> rsl <dev_fun_id1> <dev_fun_id2> <dev_fun_id3> modify_value <location> lapd_n200 <value> xbl <dev_fun_id1> <dev_fun_id2> <dev_fun_id3> equip <location> rsl equip <location> xbl Display command strings disp_equipment <location> rsl <id1> <id2> <id3> disp_equipment <location> xbl <id1> <id2> <id3> 68P02901W23-P 23 Feb 2004 7-49 GMR-01 . Device/Function RSL. Both ends of the link reinitialize when this value is modified for RSL.Technical Description BSS Command Reference lapd_n200 lapd_n200 Description The lapd_n200 parameter specifies the maximum number of retransmissions of a frame. lapd_n200 Chapter 7: Device/function parameters Values Value type Integer Valid range 1 to 5 Default value 3 7-50 GMR-01 68P02901W23-P 23 Feb 2004 . Both ends of the link reinitialize when this value is modified for RSL. XBL Type B (operator actions required) Supported by OMC-R GUI Yes Cell description required No Dependencies The minimum value for this parameter should be 800 milliseconds when using satellite links. The LAPD T200 timer is used to time the acknowledgement of a transmitted frame. Operator actions The operator needs to cycle (lock and then unlock) the device for the change to take effect. Device/Function RSL. Use of all locations option Yes Syntax Add/Change command strings 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> equip <location> rsl equip <location> xbl Display command strings disp_equipment <location> rsl <id1> <id2> <id3> disp_equipment <location> xbl <id1> <id2> <id3> 68P02901W23-P 23 Feb 2004 7-51 GMR-01 .Technical Description BSS Command Reference lapd_t200_timer lapd_t200_timer Description The lapd_t200_timer parameter specifies the LAPD T200 timer. lapd_t200_timer Chapter 7: Device/function parameters Values Value type Integer (milliseconds) Valid range 1400 to 5000 (in 50 millisecond increments) Default value 2500 7-52 GMR-01 68P02901W23-P 23 Feb 2004 . 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 Type A (no operator actions) Supported by OMC-R GUI No Cell description required No Dependencies None Use of all locations option Yes Syntax Add/Change command strings modify_value <location> max_cbls <value> lcf <dev_fun_id1> <dev_fun_id2> <dev_fun_id3> equip <location> lcf Display command string disp_equipment <location> lcf <id1> <id2> <id3> Values Value type Boolean Valid range 0 or 1 Default value None 68P02901W23-P 23 Feb 2004 7-53 GMR-01 . the value is immediately used. DHP Type B (operator actions required) Supported by OMC-R GUI Yes Cell description required No Dependencies None Use of all locations option No Syntax Add/Change command strings modify_value <location> max_dris <value> btp <dev_fun_id1> <dev_fun_id2> <dev_fun_id3> 7-54 GMR-01 68P02901W23-P 23 Feb 2004 . DRIs can be reassigned to other GPROCs within a cage. if a DRI assigned to the GPROC is taken Out Of Service (OOS). There is no automatic redistribution of DRIs from the specified GPROC. it cannot be brought back into service until the number of DRIs assigned to the GPROC is less than the value of max_dris. DRIs that are already in service are not affected while they are still in service. max_dris cannot be modified for a BTP equipped to an M-Cell site (MCU). should the modified threshold fall below the number of DRIs already assigned. A value of 0 may not be specified for this parameter if the BTS type is 0. to bring the number of DRIs below the modified threshold. If the new threshold is greater than the number of DRIs already assigned to the GPROC. Device/Function BTP.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. However. Technical Description BSS Command Reference max_dris modify_value <location> max_dris <value> dhp <dev_fun_id1> <dev_fun_id2> <dev_fun_id3> equip <location> btp equip <location> dhp Display command strings 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 68P02901W23-P 23 Feb 2004 None 7-55 GMR-01 . Device/Function LCF Type A (no operator actions) Supported by OMC-R GUI No Cell numbers required No Dependencies This parameter can be used only if the GPRS feature is unrestricted.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. The sum of all max_gsls specified by the equipped LCFs must be greater than or equal to the total number of GSLs equipped. Syntax Add/Change command strings modify_value <location> max_gsls <value> <dev_func> <dev_fun_id1> <dev_fun_id2> equip <location> lcf Display command string disp_equipment <location> lcf <id1> <id2> Values Value type Integer Valid range 0 to 6 Default value 0 7-56 GMR-01 68P02901W23-P 23 Feb 2004 . The value for max_gsls must not exceed the available LCF HDLC channel capacity. non-RXCDR system. When the value is set to 2. Set this parameter to 2 for GPROC-2 boards. the system displays a warning message and accepts the command. LCF Type B (no operator actions) Supported by OMC-R GUI Yes Cell description required No Dependencies Change the security level to 2 to modify this parameter. Device/Function BSP. This parameter must be set to 1 for at least one LCF on a BSC site where the BSC type is not zero. Use of all locations option No Syntax Add/Change command strings modify_value <location> max_mtls <value> bsp <dev_fun_id1> <dev_fun_id2> <dev_fun_id3> modify_value <location> max_mtls <value> lcf <dev_fun_id1> <dev_fun_id2> <dev_fun_id3> equip <location> bsp equip <location> lcf Display command strings disp_equipment <location> bsp <id1> <id2> <id3> disp_equipment <location> lcf <id1> <id2> <id3> 68P02901W23-P 23 Feb 2004 7-57 GMR-01 . This parameter must be set to 1 for all BSPs on a bsc_type 0.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. max_mtls Chapter 7: Device/function parameters Values Value type Integer Valid range 0 to 2 Default value None 7-58 GMR-01 68P02901W23-P 23 Feb 2004 . If the priority ratings for all MMs are set 0. It determines its possible use as a reference source to which the GCLK may phase lock. The higher the priority value. 1 Lowest priority 7-59 GMR-01 . Device/Function MMS Type A (no operator actions) Supported by OMC-R GUI Yes Cell description required No Dependencies None Use of all locations option No Syntax Change command string modify_value <location> mms_priority <value> mms <mms_id1> <mms_id2> <mms_id3> Display command string disp_equipment <location> mms <mms_id1> <mms_id2> <mms_id3> Values Value type Integer Valid range 0 to 255 68P02901W23-P 23 Feb 2004 0 MMS is not used as a clock extraction source. the more likely the MMS is to be used as a reference source to which the GCLK device will frequency lock.Technical Description BSS Command Reference mms_priority mms_priority Description The mms_priority parameter sets the priority rating for an MMS. a non-zero value for mms_priority is not permitted for a PCU MMS or an MMS which is part of a GDS. In a GPRS system. the GCLK is placed in the set frequency mode. mms_priority Chapter 7: Device/function parameters 255 Default value Highest priority None 7-60 GMR-01 68P02901W23-P 23 Feb 2004 . The MSC MMS consists of two identifiers: msc_msi_id and msc_mms_id. The msc_mms_id parameter is always zero because MSIs are not allowed to be used to provide MSC MMSs. Device/Function MSI Type A (no operator actions) Supported by OMC-R GUI Yes Cell description required No Dependencies This parameter may be modified only when the MSI type is GDP.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. Use of all locations option No Syntax Change command string modify_value <location> msc_mms_id <value> msi [<msi_id1>] [<msi_id2>] [<msi_id3>] Display command string disp_equipment <location> msi [<msi_id1>] [<msi_id2>] [<msi_id3>] Values Value Integer Valid range 0 Default value 0 68P02901W23-P 23 Feb 2004 7-61 GMR-01 . 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 msi_type parameter also specifies modification between transcoder (XCDR) boards and {4415} Generic Digital Processor (GDP) boards and GDP Version 2 (GDP2) and Multiple Serial Interface (MSI) boards and secondary GDP boards. {4415} The MSI type cannot be changed from GDP or GDP2 to XCDR when the trans_capability is Enhanced or GDP_2E1. Use of all locations option No Syntax Change command strings modify_value <location> msi_type <value> msi [<dev_fun_id1>] [<dev_fun_id2>] [<dev_fun_id3>] equip <location> msi Display command string disp_equipment <location> msi [<dev_fun_id1>] [<dev_fun_id2>] [<dev_fun_id3>] 7-62 GMR-01 68P02901W23-P 23 Feb 2004 . Device/Function MSI Type B (operator actions required) Supported by OMC-R GUI Yes Cell description required No 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. Operator actions Change to security level 2 to change this parameter.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. 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) {4415} 20 (gdp2) {4415} 21 (H2sc_niu2) Default value None 68P02901W23-P 23 Feb 2004 7-63 GMR-01 . n391 Chapter 7: Device/function parameters n391 Description The n391 parameter specifies the value for the frame relay default full status polling counter. Syntax Add/Change command strings modify_value pcu n391 <value> gbl <dev_fun_id1> <dev_fun_id2> <dev_fun_id3> equip pcu gbl Display command string disp_equipment pcu gbl <id1> <id2> <id3> Values Value type Integer (number of polling cycles) Valid range 1 to 255 Default value 6 7-64 GMR-01 68P02901W23-P 23 Feb 2004 . Device/Function GBL Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required No Dependencies The GPRS feature must be unrestricted. Device/Function GBL Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required No Dependencies The GPRS feature must be unrestricted.Technical Description BSS Command Reference n392 n392 Description The n392 parameter specifies the frame relay default value for error threshold counter. Syntax Add/Change command strings modify_value pcu n392 <value> gbl <dev_fun_id1> <dev_fun_id2> <dev_fun_id3> equip pcu gbl Display command string disp_equipment pcu gbl <id1> <id2> <id3> Values Value type Integer (number of errors) Valid range 1 to 10 Default value 3 68P02901W23-P 23 Feb 2004 7-65 GMR-01 . This parameter must be less than or equal to the value of n393. Device/Function GBL Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required No Dependencies The GPRS feature must be unrestricted.n393 Chapter 7: Device/function parameters n393 Description The n393 parameter specifies the frame relay default value for monitored events counter. Syntax Add/Change command strings modify_value pcu n393 <value> gbl <dev_fun_id1> <dev_fun_id2> <dev_fun_id3> equip pcu gbl Display command strings disp_equipment pcu gbl <id1> <id2> <id3> Values Value type Integer (number of events) Valid range 1 to 10 Default value 4 7-66 GMR-01 68P02901W23-P 23 Feb 2004 . The value of this parameter must be greater than or equal to the value of n392 . This parameter is available for MMSs equipped from GPRS PMC MSIs. Device/Function MMS Type B (operator actions required) Supported by OMC-R GUI Yes Cell numbers required No Dependencies The MMS must be locked when modifying this parameter. The default value for this parameter is automatically assigned when the MSI is equipped.Technical Description BSS Command Reference nbit nbit Description The nbit parameter enables and disables the second remote alarm bit (nbit). Operator actions Lock the MMS before modifying this parameter Use of all locations option Yes Syntax Change command string modify_value <location> nbit <value> mms <dev_fun_id1> <dev_fun_id2> <dev_fun_id3> Display command string disp_equipment <location> mms <id1> <id2> <id3> Values Value type Boolean Valid range 0 or 1 Default value 68P02901W23-P 23 Feb 2004 0 Disabled 1 Enabled 0 7-67 GMR-01 . Device/Function BSS. RXCDR Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required No Dependencies Changing the ne_id causes all AXCDR or ABSS devices to be cycled.ne_id Chapter 7: Device/function parameters ne_id Description The ne_id parameter specifies the network identity. Use of all locations option No Syntax Change command string modify_value 0 ne_id <value> bss|rxcdr <id1> Display command strings To list the IDs for the bss/rxcdrs in the database. resulting in the loss of all active calls managed by the associated device. enter the following command: disp_equipment 0 bss|rxcdr <id1> Values Value type Integer Valid range 1 to 128 Default value None 7-68 GMR-01 68P02901W23-P 23 Feb 2004 . enter the following command: disp_equipment 0 bss|rxcdr * To display information about a specific bss/rxcdr. there is no default value. When enabling opto_reporting for a DRI. The values may be entered in any order.) When disabling opto_reporting for an EAS. Device/Function DRI/EAS Type A (No operator actions) Supported by OMC-R GUI Yes Cell numbers required No Dependencies None The affected device must be locked. When enabling opto_reporting for an EAS. the operator is also prompted for the user defined alarm index. (The text string “mpf" is equivalent to a value of 128. up to 16 values may be entered for an M-Cell site. the operator is prompted for the index of the user defined alarm string for the optocoupler. The range of values is 0 to 33.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. The range of values is 0 to 33 and 128. there is no default value. The value “all" may be specified. A range of values may be specified. A range of values may be specified. The value “all" may be specified. the operator may enter up to eight values (separated by a comma or a space) for an EAS at an InCell site. The values may be entered in any order. Up to eight values (separated by a comma or a space) may be entered for an EAS at an InCell site. the operator is first prompted for the optocoupler(s) whose state should be reported. The operator must enter one value indicating the index of the alarm string for each optocoupler specified in the previous prompt. up to 16 values may be entered for an M-Cell site. Use of all locations option Yes Syntax Change command string modify_value <location> opto_reporting <value> <device> <id1> <id2> <id3> 68P02901W23-P 23 Feb 2004 7-69 GMR-01 . When enabling opto_reporting for an EAS. depending on the device specified. (See description above for details. additional prompts are displayed.) Display command string disp_equipment <location> <device> <id1> <id2> <id3> Values Value type Boolean Valid range off or on Default value off Disabled on Enabled None 7-70 GMR-01 68P02901W23-P 23 Feb 2004 .opto_reporting Chapter 7: Device/function parameters After this command string is entered. Device/Function DRI Type A (No operator actions) Supported by OMC-R GUI Yes Cell numbers required No Dependencies This parameter must be an RTF unique identifier or “null" for resetting to no preferred RTF. or “null" Default value None 68P02901W23-P 23 Feb 2004 7-71 GMR-01 . 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. Use of all locations option No Syntax Change command string modify_value <location> pref_rtf_id <value> dri <id1> <id2> Display command string disp_equipment <location> dri <id1> <id2> <id3> Values Value type Integer or string Valid range 0 to 11. This allows at least one carrier unit per cabinet that is able to provide GPRS feature service.Technical Description BSS Command Reference pref_rtf_id pref_rtf_id Description The pref_rtf_id specifies a preferred RTF identifier. The user is prompted for each opto that is enabled. The RSL cannot be changed if RSLs are already equipped for this site. The RSL rate cannot be changed for the BSC (site 0). Use of all locations option No Syntax Change command string modify_value 0 rsl_rate <value> site <site number> Display command string disp_equipment 0 site <id1> <id2> <id3> Values Value type Integer (rate in kbit/s) Valid range 1664 Default value None 7-72 GMR-01 68P02901W23-P 23 Feb 2004 .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 Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required No Dependencies The 16 kbit/s RSL option must be available. The RSL cannot be changed if the site uses dynamic allocation. Changing the sd_load parameter may cause a channel reconfiguration to make the new values effective. up to their SDCCH load. Device/Function RTF Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required No Dependencies None Use of all locations option No Syntax Add/Change command strings modify_value <location> sd_load <value> rtf <rtf_id1> <rtf_id2> equip <location> rtf Display command string disp_equipment <location> rtf <id1> <id2> <id3> Values Value type Integer Valid range 0 to 2 68P02901W23-P 23 Feb 2004 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 7-73 GMR-01 . The BSS configures the SDCCHs on the carriers with the highest priority.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 reconfiguration occurs as channels become idle. sd_load Chapter 7: Device/function parameters Default value 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 None 7-74 GMR-01 68P02901W23-P 23 Feb 2004 . The BSS configures the SDCCHs on the carriers with the highest priority. Use of all locations option No Syntax Add/Change command strings modify_value <location> sd_priority <valid range> rtf <id1> <id2> equip <location> rtf Display command string disp_equipment <location> rtf <id1> <id2> Values Value type Integer Valid range 0 to 250 0 68P02901W23-P 23 Feb 2004 highest priority 7-75 GMR-01 . Changing the sd_load parameter may cause a channel reconfiguration to make the new values effective. Extended Range Cell. Device/Function RTF Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required No Dependencies The sd_priority element cannot be changed for an EGSM. The reconfiguration occurs as channels become idle. up to their SDCCH load.Technical Description BSS Command Reference sd_priority sd_priority Description The sd_priority parameter specifies the SDCCH placement priority for an RTF. or inner zone carrier. sd_priority Chapter 7: Device/function parameters 250 Default value lowest priority Non-BCCH default = 0 BCCH default = 0 7-76 GMR-01 68P02901W23-P 23 Feb 2004 . 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 Type A (no operator actions) Supported by OMC GUI No Cell numbers required No Dependencies DYNET must be equipped. The site must be a BSC (Location = 0). Use of all locations option No Syntax Add/Change command strings modify_value <location> shared_timeslots <value> dynet <id1> <id2> equip <location> dynet Display command strings disp_equipment <location> dynet <id1> <id2> Values Value type Integer Valid range 0 to 31 Default value 68P02901W23-P 23 Feb 2004 0 to 31 E1 link 0 to 23 T1 link 0 (no timeslots reserved) 7-77 GMR-01 . When the slot parameter is modified outside SYSGEN mode. Device/Function DRI Type A (no operator actions) Supported by OMC-R GUI No Cell numbers required No Dependencies None Use of all locations option No Syntax Add/Change command strings modify_value <location> slot <value> dri <dev_fun_id1> <dev_fun_id2> <dev_fun_id3> equip <location> dri Display command string disp_equipment <location> dri <id1> <id2> <id3> Values Value type Integer Valid range 7 to 17 (odd values only) Default value None 7-78 GMR-01 68P02901W23-P 23 Feb 2004 . 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.slot Chapter 7: Device/function parameters slot Description The slot parameter specifies the slot in which the DRI device is fitted. Device/Function GBL Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required No Dependencies The GPRS feature must be unrestricted.Technical Description BSS Command Reference start_ts start_ts Description The start_ts parameter specifies the first GBL timeslot on the E1/T1 link. Syntax Add/Change command strings modify_value pcu start_ts <value> gbl <dev_fun_id1> <dev_fun_id2> <dev_fun_id3> equip pcu gbl Display command string disp_equipment pcu gbl <id1> <id2> <id3> Values Value type Integer (first GBL timeslot) Valid range 1 to 31 Default value None 68P02901W23-P 23 Feb 2004 7-79 GMR-01 . Syntax Add/Change command strings modify_value pcu t391 <value> gbl <dev_fun_id1> <dev_fun_id2> <dev_fun_id3> equip pcu gbl Display command string disp_equipment pcu gbl <id1> <id2> <id3> 7-80 GMR-01 68P02901W23-P 23 Feb 2004 . In GSR6. If this is also unsuccessful. a new timer is added to improve the speed of getting GBL B-U.t391 Chapter 7: Device/function parameters t391 Description The t391 parameter specifies the frame relay default link integrity verification polling timer. Device/Function GBL Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required No Dependencies The GPRS feature must be unrestricted. then the GBL notifies pCA of the status. If not. it waits for the expiry of the original t391 * n391 timer value and re-attempts to connect the GBL. This timer attempts to bring the GBL B-U after t391 plus 1 second. Technical Description BSS Command Reference t391 Values Value type Integer (seconds) Valid range 5 to 29 Default value 10 68P02901W23-P 23 Feb 2004 7-81 GMR-01 . Device/Function GBL Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required No Dependencies The GPRS feature must be unrestricted. Syntax Add/Change command strings modify_value pcu t392 <value> gbl <dev_fun_id1> <dev_fun_id2> <dev_fun_id3> equip pcu gbl Display command string disp_equipment pcu gbl <id1> <id2> <id3> Values Value type Integer (seconds) Valid range 6 to 30 Default value 15 7-82 GMR-01 68P02901W23-P 23 Feb 2004 .t392 Chapter 7: Device/function parameters t392 Description The t392 parameter is the frame relay default polling verification timer. A prompt is included that enables the operator to chose to continue or abort the change.Technical Description BSS Command Reference tcu_port tcu_port Description The tcu_port parameter specifies the port to which a TCU is connected. a warning message is displayed that the specified DRI is about to be cycled (locked then unlocked). When the tcu_port parameter is modified outside SYSGEN mode. Device/Function DRI Type A (no operator actions) Supported by OMC-R GUI No Cell numbers required No Dependencies None Use of all locations option No Syntax Add/Change command strings modify_value <location> tcu_port <value> dri <dev_fun_id1> <dev_fun_id2> <dev_fun_id3> equip <location> dri Display command string disp_equipment <location> dri <id1> <id2> <id3> Values Value type Integer Valid range 0 to 5 Default value None 68P02901W23-P 23 Feb 2004 7-83 GMR-01 . 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 GMR-01 68P02901W23-P 23 Feb 2004 . Device/Function MSI Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required No Dependencies None Use of all locations option No Syntax Change command string modify_value <location> transcoding_capability <value> msi [<msi_id1>] [<msi_id2>] [<msi_id3>] Display command string 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 68P02901W23-P 23 Feb 2004 0 7-85 GMR-01 . Basic and enhanced functionality are available.Technical Description BSS Command Reference transcoding_capability transcoding_capability Description The transcoding_capability parameter specifies the functionality provided by a GDP board. When the tru_id parameter is modified outside SYSGEN mode. Device/Function DRI Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required No Dependencies None Use of all locations option No Syntax Change command string modify_value <location> tru_id <value> dri <dev_fun_id1> <dev_fun_id2> <dev_fun_id3> Display command string disp_equipment <location> dri <id1> <id2> <id3> Values Value type Integer Valid range 0 to 6 Default value 0 Non-TopCell unit 1 to 6 TopCell ID None 7-86 GMR-01 68P02901W23-P 23 Feb 2004 . A prompt is included that enables the operator to chose to continue or abort the change. A value of 0 indicates this is a non-TopCell site.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 warning message is displayed that the specified DRI is about to be cycled (locked then unlocked). Use of all locations option Yes Syntax Add/Change command strings modify_value <location> trx_pwr_red <value> rtf <id1> <id2> <id3> equip <location> rtf Display command string disp_equipment <location> rtf [<id1> [<id2>] [<id3>]] [full] 68P02901W23-P 23 Feb 2004 7-87 GMR-01 . 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). Device/Function RTF Type A (no operator actions) Supported by OMC-R GUI Yes Cell numbers required No 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 Concentric Cells option must be unrestricted.Technical Description BSS Command Reference trx_pwr_red trx_pwr_red Description The trx_pwr_red parameter specifies the TRX transmit power reduction value. Table 7-2 lists values for PGSM. EGSM and PCS 1900 sites.trx_pwr_red Chapter 7: Device/function parameters Values Value type Integer (1 step = 2 dBm) Valid range -1 to 21 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-4. EGSM. Table 7-3 Values for DCS 1800 sites Value Power Value Power -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 GMR-01 68P02901W23-P 23 Feb 2004 . and DCS1800 0 to 6 for M-Cellmicro sites Default value None Refer to Table 7-2. Table 7-3. Table 7-2 Values for PGSM. and Table 7-5 for additional information about the values for this parameter. Table 7-4 Values for PGSM and EGSM M-Cellmicro sites Value Power Value Power 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.Technical Description BSS Command Reference Table 7-3 trx_pwr_red Values for DCS 1800 sites (Continued) Value Power Value Power 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-5 68P02901W23-P 23 Feb 2004 Values for DCS 1800 and PCS 1900 M-Cellmicro sites Value Power Value Power 0 30 dBm 4 22 dBm 1 28 dBm 5 20 dBm 2 26 dBm 6 18 dBm 3 24 dBm 7-89 GMR-01 . trx_pwr_red Chapter 7: Device/function parameters This page intentionally left blank. 7-90 GMR-01 68P02901W23-P 23 Feb 2004 . . 5-750 5-698. 3-2 . . . . . . 5-5 . . . adap_ho_pbgt . . . . . . . . add_conn . . . . . . . . . 5-9 . adap_trigger_hop_rxqual_ul. . . . . . adap_ho_rxlev . . . . . amr_hr_res_ts . . . . . . . . . . 5-20 . . . . . . . . . . . . . . . . . . . . . . . . . . 5-694 5-684. . . . . . . . . . . 5-19 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-21 alt_qual_proc . . . . . A_PBGT_HO . . . . . 2-47 . . . . . alarm_mode . . . . . . . . . amr_ms_high_cmr . . A_QUAL_HO . . 5-7 . . . . . . adap_trigger_pbgt_nbr . adap_trigger_rxlev_ul . . . . . . . . . . . . . . . . . . . add_rtf_path . . 5-11 . . . adap_trigger_rxqual_ul . . . . . . . . . . . . . . . . . . aci_error_gen_thresh . adap_trigger_rxqual_dl . .Index Index A A_LEV_HO . 5-16 . . amr_inner_hr_usage_thres . . . . . . . . . . . . 5-18 . . . . . . . . . 6-2 . amr_fr_ul_la_enabled. . . . . . 5-123 . ATT . . . . 5-8 . . . . . . . . . . . . . . . . amr_ms_low_rxqual . add_neighbor . . . . . . . . . . antenna_select . . . 2-35 . . . . . . . . . amr_dl_thresh_adjust . . . 5-12 . . . . 2-21 . 5-17 . . . 5-15 2-396. . adj_chan_intf_test . . . . . . . . . . . . . . . . . . . . . . . amr_hr_dl_la_enabled . . . . . . . . adap_ho_rxqual . . . . . . . . . . . . . . . . . . . adap_trigger_rxlev_dl . . . . . . . . . . . . . 5-704 . . . . . . . . . . . . . . . amr_new_calls_hr . . . . . . . . . . . . . . A_QUAL_PC . . . . . . . . . . . auto_rf_loss_trace . . . . . . amr_reconfig_fr_to_hr . . . . . . . . . . . . . . . . . . adap_trigger_hop_rxqual_dl. . adap_ho_alt_trigger_rxqual . . . . . . adap_trigger_pbgt . . . . . . . . . . . . . . . 68P02901W23-P 23 Feb 2004 . amr_hr_intracell_ho_allowed . . . . . . . . . . . . . amr_hop_count. . . . . . alias . . . . . . . amr_full_rate_enabled . . . . . . . . . . . add_access_class . . . . . . . attach_detach . . . . . . . . aci_error_clr_thresh . . . . . . . amr_dl_la_mode_chg_min . . . . . . . 2-43 . . . . . . . . . . . . . . 5-13 . . assess . . . . . . 2-33 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-19 . . . . . . . . . . . . . . . . . . . . . . . . . . . amr_fr_dl_la_enabled. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-702 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . amr_bss_half_rate_enabled . . . . . . . . . . . . . amr_hr_ul_la_enabled . . . . . aci_error_inc . . . . . . . . . . assign_successful. . . . 2-45 . . . . amr_ms_monitor_period . . . . . AC_CN . 5-23 1-10 5-26 5-27 5-28 5-29 5-30 5-31 5-32 5-33 5-35 5-37 5-38 5-40 5-42 5-39 5-43 5-44 5-45 5-46 5-47 5-48 5-49 5-50 7-5 2-49 6-3 5-52 5-51 6-5 5-53 IX-1 GMR-01 . . . . . . . . . . . . . . . . . . . . . . add_cell . . . . . . . . . . . . . . . . . amr_force_hr_usage . . . ambiguous command response amr_bss_full_rate_enabled . . . . . . . . . . . add_nsvc . auto_dl_dur . . . . . . . . . 5-6 . . . . . . . . . . . . . 5-692 5-686. A_LEV_PC . . . . . amr_ms_high_rxqual . . . . . amr_ms_low_cmr . 5-684. alarm devices . . . . . . . . . . . allow_8k_trau . . . . 5-14 . . . . . . . . . . . . . . . . . . . . 2-396 . . . . . . . . amr_half_rate_enabled . . . . . . . . . . . . . . bep_period . bssgp_reset_retries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ber_restore_mon_period . 5-59 . bssmap_t8 . . . . . . bts_audit_response . . . .Index B ba_alloc_proc . bcch_info . . . . . . bs_pbcch_blks . . . . . . 5-71 . BSP max_mtls . . . . . . . . . . . . . . . . . . . . . . . . . . 6-40 . . . . . . . . . . . 7-9 . . . 6-12 . . . band_preference_mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . bssmap_t4 . . . 5-69 . . . BS_PA_MFRMS . . . 6-6 . . . . . . . . . . . . . 5-90 . . . . . . 5-75 . . . . . bsc_audit_response . . . . . . . . . . . . . . . . . . . 5-57 . . . . . . . . . . bts_p_con_ack . . 5-77 . . . . . . . . . . . . . . . . . . . 6-41 . . . . . . . . . . . . 5-79 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-67 . . . . . . 5-55 2-396 2-396 . . . . . . bsc_cbc_operator . . . . . . . . . . . bssgp_racap_retries. . . . . ba_gprs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . bts_p_con_interval . . . . . 7-11 . . . . . . . BSSGP T1 . . . . . bts_audit. bs_prach_blks . . . bssmap_t20 . . . . . . . . . . . . . . . . . . . . . 5-64 . 1-2 5-80 5-81 6-18 5-82 5-83 6-15 5-85 5-86 6-17 6-19 5-87 6-21 6-22 6-24 6-26 6-28 6-29 6-30 6-32 6-34 6-36 . . . . . . . . . . . . . . . . . . 5-65 . . . . . . . . . bss_egsm_alm_allowed . . . . . . . bsc_audit . . . . . bssmap_t19 . . BSIC_NC(n) . . . . 5-92 5-94. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ba_bcch . . . . . . . . . . 5-68 . . . . . . . . . . band_preference . . . BSS ne_id . . . . . . . . . . . . . . . . . . . . bssgp_unblock_retries . . . . . . . . . bvci . . . . . . . . . . ber_oos_mon_period . . . . . . . . . . . . . . . . . . . . . . . bsc_type . . . . . . . . . . . . . . . . . . . 5-73 . . . . bssmap_t10 . . . . . . . . . . . . . . ber_loss_hourly . . . . . . . . . . . . . . . . . . BSIC . 7-54 . . . . . . . . . . . . . . . . 5-74 5-496 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . bssmap_tqh0 . . . . . . . . . . . . . . . . . 5-385 . . . BS_TXPWR_RED . . . . . . . bts_power_control_allowed . . . . . . . . . bsic . . . . . . . 5-79 5-481. . . . . . . . . . . . . . . . . . . bssgp_t2_timer . . . . . . . . . . . . . . . 5-88 . . . . . . . . . . bts_type . . . . . . . . . . . . . 6-13 . . . . . . . . . . 5-63 . . . . . . . . . . . . . . . . . . bs_pcc_chans . . bssgp_t1_timer . BS_AG_BLKS_RES . . . . . . . 6-38 . . . . bssmap_t7 . . . . . . . . . . . . . . . . . . . . . . . bs_ag_blks_res . . . . . . 6-10 . . . . . . . . . . BTP max_dris . . . . 6-8 . . . . . . bounce_protect_qual_tmr . . . . bss_msc_overload_allowed . . . . . . . . . . . . . . . bssmap_t11 . . . . . . . . . . . bssgp_cbl_bit . . . bssmap_t1 . . bep_period2 . 7-68 IX-2 GMR-01 68P02901W23-P 23 Feb 2004 . . . . . . . . . . . . . . . . . bs_pag_blks_res . . 7-57 BSS Initialization Process about . . . . . . . . . . . . bssmap_t13 . . . . . . . . . . 7-7 . . bounce_protect_margin . . . . . . . . . . . . . bs_pa_mfrms. . . . 5-62 . . . . . 5-101 . . . . . . . . . 5-99 . . . . . . . . . . bts_escalation . . . . . . . . . . . . . . . . . . . . . bssgp_fc_period_c . . . . . . . . . bounce_protect_cong_tmr. . . ber_loss_daily . . . . 6-14 . 5-66 . . . . . . . . . . . . . . . . . . 6-11 . . . . . . . bts_txpwr_max_inner. . . . . . . bssgp_block_retries. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-772 5-164 5-166 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . chg_time. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ccch_conf . ciph_mode_rej_allowed. . cell_bar_access_switch . . . . . . chg_severity . 2-69 . . 1-8 . . . . . . . . . . . . . . . . . . . . . . . . . . . cbc_operator . . . . . . 5-115 . . . . . . . . . . . . . . . . 2-116 . . . . . parameters Parameters to be used with caution cavity . 5-329 . . . . . . . . . . carriers_ins_pwr_fail . . . chg_smscb_msg . cab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . cic_error_inc . . . . . bs_ag_blks_res dependency. . . . . . . CBL bsc_cbc_operator . . . . 2-119 . . . . 5-130 . . . . . . . . 6-211 IX-3 GMR-01 . . . . . . . . . . . . . . . . . . . . . . . . cabinet_type . . . . cic_error_gen_thresh . . . . . . . . . . 7-19 . chg_stat_prop . . . . . . . . . . . . . . . 6-49 . . . . . channel_teardown . . . . . 4-5 . . . . 5-120 . . . . carrier_disable_time . . cbch_2. calling_pci . . c32_qual. . . . . . . . . . . . . . . . . 5-65 . . . . . . . . . . . . . . . . . . . . cbch_enabled . . . . . chg_a5_alg_pr . . . . . . . . . . . . . . . . . . 7-16 . . . . . . . . . . . . . . . . . . chg_dte . . . . chg_rtf_freq . . . . . . . . . . . . . . . . chg_element . . . . . . . . . . . . . . . . . . . clkx0 . . . . . . . . cbc_vbind_cntr. 2-87 . . . . . 7-23 . CCITT Q. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . clm_t_stat_info. . . 2-134 . . cell_bar_qualify . . . . . . 5-137 . cic_validation . . . . . 5-106 . . . . 2-61 . . . . . . . . . . 2-91 . . . . . . . 7-15 5-110 5-112 . . . . . . . . . . 2-77 . . . . . . . 5-107 . . carrier_free_immediate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-208 . 5-108 . . . . 6-54 . . clkx2 . . . 5-121 . . . . . . . . . . . . . . . . . 5-105 . 5-140 . . circuit_reset_ack . . . . CLM_MTJ1 . . 5-124 . . . . . . . . . 5-118 . CELL_RESELECT_OFFSET . . . . chg_cell_id . . . . . . . . . . 7-45 . . 2-94 . . . . . . . . . . . . . . . . . . . int_antenna . . . . . . 5-105 . . . . . . . . . 5-135 . . . . . . . . . . . . . 7-16 5-113 . . . 5-141 . . . . . . . . . . . 6-47 . . chg_acs_params . . . . Caution. . . . CCCH_SDCCH_COMB . . chg_throttle . . . . . chg_cell_element. . . . . . . . 2-146 . . . . 2-101 . . . . . . . . . . . . . . . commands Commands to be used with caution Caution. 5-133 . . . . . cbc_fast_select . . . . . . . . . . . . . . . . . 2-58 5-128. . 2-127 . . . . . . . . . . 4-28 . . . . . . . . . . . . 6-52 . . . . . . CLM_MTA1 . . . . . . . . . . . . . . . . . . . . 5-144 . . . . CCCH_CONF . . . . . . chg_ksw_config . cell identity UTRAN . 7-25 . . . . . . . . . . . . . . cbch_1. clear_command . chan_alloc_priority . . . . 6-183 . . . . . . . . 7-46 . . . . . . . . . . . . . . . . . . . . CLM_SPI_TIMER . . . . . . . . 2-110 . . . . . . . 5-132 CELL_RESELECT_PARAM_IND cell_zone . . . . . . c31_hyst . . . . . . . . . . . 68P02901W23-P 23 Feb 2004 . . . . 2-126 . . . . . . . chg_x25config . cipher_comp_ms . . . . . . . . . . . . . . . . . . . . . . 6-46 5-114 . . . . channel_ack . . . call_trace_options . . . . . . . 5-129 . . . . . . . . . . . . 5-118 . . . . . 7-12 . . . . . . . 5-142 . . . 5-146 . . . . . . . chg_eas_alarm . . . . . . . . . . . . . . 2-124 . . . chg_ts_usage. . . . . 7-17 5-134. 1-7 . . . 5-279 . . . . . . . . . . . . . . . . . . . . cbc_operator. . . channel_reconfiguration_switch . . . . . called_pci . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-103 . . . . . chg_level . . cbs_outage_cntr . . . chg_csfp . . . . . . . . . . . . . cic_block_thresh . . chg_audit_sched . . . . . . cell_reselect_param_ind . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-56 . . . . . 5-116 . . . . . . cic_error_clr_thresh . . . . . clear_gclk_avgs . . . . . . CELL_BAR_ACCESS . . . . . . . . . . . . . . . . . clear_database . . . . . . . . . . . cell_reselect_offset . . . . . 5-125 . . . . 2-150 . . . . . cic_unblock_thresh . . . . . . .Technical Description BSS Command Reference Index C C2. . . . . . . . . . . cell_bar_access_class . . . 2-132 . . . . . . . . . . . . . . . . . . . . . CE_RE_HYS . . . . . . . . . 7-11 . . . . . . . . . . . cbc_intface_vers . 5-126 . . . . . . CCCH_LOAD_IND_PERIOD . . . . ccch_load_period. . . . . . clear_cal_data . . . . 6-50 . . . 2-148 . . . . data_coding_scheme . . . . . . . . . . . . . . . . 7-21 . . . . . . int_hdsl_modem . . . . . . . . . . . 5-119 . . cell_reselect_hysteresis . .713 . . . 6-54 . . . . . . . . . . . Call Processing about . . . 5-145 . . . . . . . . . . . cage_audit . . . . . . . 2-80 . . . . 5-131 . . . . . 2-72 . . . . . . . . . . . . . 5-139 . . . . . . . 1-4 . . cell_name . . clk_src_fail_reset_period . . . . . . . . . 6-44 . . . . . . 2-54 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . chg_password . . chg_element (statistics application) chg_hop_params . . . 2-114 . . . . . . . 6-42 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-45 . . . . . . . 7-12 . . . . . . . . . . . . . . . . . . . . 2-143 . . 2-84 . . . 2-137 . . . . . clkx1 . . . . . . . . . ciphering_successful . . . . . . cbch_3. . . . . . . . . . . . . . . . . . 5-182 . . . . . . . . . . . . decision_1_p6 . 6-28 . . . . . . CLM_T19 . combining_type . . . . . . . . . . . . . 2-143 config_window_size (contd. 5-203 . . . . . . decision_1_p1 . Counter statistics . . . . . . 5-184 . . . . . . . . . . . . . . . . 7-28 . . . . . . . . . . . . 2-154 . . . . . . . . . . . . copy_cell . . cr_calling . 5-180 . . . . . . . . . . . . . . . . . . . . . . . 2-3 2-184 . . . . . . . . . . . . . . . . . . . . ct_flow_control_msc_trace . . . . . . 1-6 . . . . . . . . . . decision_1_p2 . . disp_cell_status . . . . . . . . . 5-198 5-199 5-200 2-165 2-168 2-171 2-173 2-177 2-179 2-181 . 5-156 2-396. . . . . . . . . . . . . . . . . . . . . 5-152 . . . . . 5-190 . . . . . . . 5-174 5-173. 5-154 . . . disp_cal_data . . 1-6 . . . . . . . . . . . . . . . . . . . . . . . . . 5-188 . . . . . . . . . . . . . 1-5 . . . . . . . . . . . . . . . . . 5-176 . . copy_path . 1-23 . . disp_acs . delay_dl_rel_dur . direct_inner_zone_threshold disp_a5_alg_pr . . . . . . . . 5-195 . 2-152 . . . 5-157 . . . . . . . . decision_1_n3 . . . . . . . . 2-189 . . . . . . . . . . . . device IDs . . . . . . . . . coincident_mb . . . decision_1_n5 . . . . . . . . . . . . . . . . . . . . . concentric cells inner_zone_alg . . . . . . . . dealloc_inact . . . . . . . . . . . . . . . . . . . decision_1_p3 . . . . . . . . . . . . . . . . . . . 2-205 . . . . 2-200 . cp_option_rr_status. . . . . . . . . . . . del_nsvc . . . . . . . . . . . . . . . . . . diagnose_device . . . . 5-194 . . .Index CLM_T1 . . . . . . . . . . . . . . . . . . . . . . . 2-213 . . . . 5-159 . 5-171 . . . . command response ambiguous. . . ct_flow_control_hi_level . . . . . 5-178 . . . CLM_T4 . . . . . . . Command Security Levels . . . . 5-192 . . . 5-196 . . . . . del_neighbor . . . . . . . . . . . . . . . . . . . . . disp_cell_map . . . . . decision_1_ul_rxlev_av_ih . . . . . . . . . . . . . . . . . . . 2-210 . . . . . . . . . . . 2-156 . . . . . . . . . . . . . . . . . . 4-3 . . . . . . . decision_1_dl_rxqual_av_h . . . . . . . . . . . . . . . . . . . . . . . 5-149 . 6-60 . . CLM_T13 . . . 68P02901W23-P 23 Feb 2004 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . congest_ho_margin . . . . . . . . . . . . . . 5-186 . . . . . 1-10 . . 5-188 . . . . . 2-223 . . . . disp_bss . . . . . . decision_1_dl_rxqual_av_p . 5-151 . . . . del_act_alarm . . . . . . . . . . . . . . . . . . . . CRM rr_t3111_sd . . . . 7-29 . . . . 7-54 . . . 5-180 . . . . . . . . device related commands . . 7-27 . . . . . . congest_at_target . . coincident_cell . . . . . . . 2-162 . disp_csfp . . . . . . . . . . . . . . . . . . . . . ct_flow_control_lo_level . . . data_qual_enabled . . . . . . . . . . . . . . . . CLM_T20 . coincident_offset . 5-197 IX-4 GMR-01 decision_1_ul_rxqual_av_h . decision_1_p7 . . . . . . . . . . 6-29 . . . decision_1_p8 . . 6-31 5-147. congest_at_source . . confusion_msg_allowed . . . . . . . 5-160 . . . 5-182 . . . . . . . . . . . . . . . 2-193 . . . . . . 6-58 . . 5-383 . . . . . DHP max_dris . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . decision_1_p5 . decision_1_ul_rxlev_av_h . . . . . . . . . . . . . . decision_1_n1 . . . . . . . . . . . decision_1_dl_rxlev_av_ih . . . . . . . . . . . . . . . . . . . . . . . . . . 5-172 . . decision_1_n4 . . 6-164 6-168 5-161 5-162 5-163 . . . . . . . . . . 2-8 . rr_t3212 . . . . . . disp_conn . . . . . . 5-175 . . . . . . decision_1_ul_rxlev_av_p . . . . . . . . . 2-198 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . disp_cbch_state . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . cp_option_reset_ckt . . . . combiner_address . . . . . . . . . . . . . . . . . disp_act_alarm . . . 5-168 . . . . . . . decision_1_n2 . . . . . . . . decision_1_n6 . decision_1_p4 . . . . . 2-127 . . del_smscb_msg . . . . . . . . . . . . . . . . del_cell . . . . 5-149 . . . . . . . . . . . . . . . . . . . 2-225 D data_coding_scheme . . . . . . . . . . . . 6-21 . 2-143 . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-190 . . . . . . . . . . . . . decision_1_ncell_rxlev_av_h_calc. . . . . . combiner_id . . . . . . decision_alg_type . . . . . . . . . . . . . . . . . . . . . . . . 5-186 . . . . . . . . 5-184 . . . . . . disp_cell . . . . . . . del_rtf_path . . . . . . . . . . . . . . . . . . . . decision_1_tim_adv_av_alg . . . . device indices . . . . . . . . . . . . . . . . . . . . . . decision_1_p_bgt_rxlev_av_h . . connection_code . . . . . . . .) in BSS View at OMC GUI configure_csfp . . . . . . . . . 2-202 . 2-191 . . . . . decision_1_dl_rxlev_av_h . . . . . . . . 2-195 . . . . . . . . 6-27 . . . . . . . . . . . . . . . . command types . decision_1_ul_rxqual_av_p . . . . . . 5-193 . decision_1_n8 . . . . . . . device_audit . 5-178 . . . . . . . . . 5-176 . . . . . . . decision_1_n7 . . . . . . . . . . . . config_packet_size in BSS View at OMC GUI config_window_size . . . . . . . . . . 5-158 . . . database parameter types . . del_conn. . . . . . . 6-63 . . . . . . . . . . . 5-221 . . . . . . . . . . . . . . . . . en_incom_ho. . . . . . . 5-204 . . . . . . . 6-61 . . . . . . . . . . . . . . . . . EN_MS_PC . . . . . . . . . . . . . disp_dte . . . disp_hdlc . . . . . . . . . . . . Duration statistics . EC . . EN_Q_OWED . . . tcu_port . . . . . disp_gclk_cal . . . . . . . . . 7-45 to 7-46 . 4-3 . disp_gsm_cells . . disp_flash . . . . . . . . . 5-237 . . . . 5-230 E eac_mode . . . . . . 5-226 . . . . . . 5-228 . . . . . . . . . . . . . . . disuse_cnt_hreqave . . . . . . . 6-66 . . . . . . . disp_link. . . . . . 7-29 7-12. . . . . . . . . . . . . . . dr_ho_during_assign . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-236 . . . . . . . . . . 7-86 . . EN_INTRA_HO . . . . . . . . . . . . . egsm_handover_threshold emerg_reserved . . . . early_classmark_sending EAS disp_relay_contact . . . . . . . . . . . . . . . early_classmark_delay . . . . . . . . . . . . . . . 5-223 . . . . dl_rxlev_ho_allowed . . . . . 5-215 2-396. . . . . . dynet_tchs_reserved . . . . 7-5. . . dl_audio_lev_offset. . . . . . . . . . . . . . 5-217 . . . . . . . . . . . 7-71 . . . . . . . . . 6-65 . . . . . disp_transcoding . . 7-83 . . . dynet_retry_time . . . . . . . . . . . 5-93 . . . disp_exp_config . . . . . . disp_site . . . disp_equipment . . . . . 5-208 . . 4-3 . . . . . . . . . . . . . . . . . . . . . 5-234 . . . . . . . . . . . . . . . . efr_enabled . . . . . . . . . . . opto_reporting . . . . . . 5-389 . disp_gclk_avgs. . . . . . . . . . . . . . . . . . . . . . . . . 5-205 . . . . . . . . . . . disp_x25config. . . 7-15 . . . . DTX . . . . . . . . . . . . . . . . . . . . . . . . . . emergency_class_switch . . dyn_step_adj_fmpr . dnlk_vad_dtx . . opto_reporting . . . . . . . . . . . disp_trace_call . . . . . 5-252 . eas_alarm_type. disp_stat_prop . dual_band_offset . . 4-15 2-264 2-265 2-267 2-269 2-281 2-287 2-290 2-294 2-298 2-300 2-305 2-308 2-310 . . . . . 7-69 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-397 . . . . 5-622 . . . . . . . . . . . EN_BS_PC . . . . . . . . . . 4-17 . . . . . . . . . . . Distribution statistics . . 5-210 . . . . . . . . . . . . eas_report_opto . . . . . . . dyn_step_adj . 7-31 . . 1-3 . . . . . . . . . 5-249 . . . . . . . . . 68P02901W23-P 23 Feb 2004 . . . . . . . . . . . . . . . . . . . . . . . disp_processor . . . 4-22 2-311 2-313 2-315 2-318 2-321 2-323 2-324 . . eas_alarm . . dri_density . . . disp_mms_ts_usage disp_neighbor . . . . 5-239 . . . . . . . . . . . disp_time . . . . . DYNET shared_timeslots . . . . . . . . disp_version . . . . . . . . . . . . . . . . . . . . . disp_element . . . disp_throttle . . . . . . . . . . . . disp_traffic. . . . . . . . . . . cab . . . . . fm_cell_type. . dl_dtx_voice_data . . . . . . . . 7-77 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-243 egprs_init_ul_cs . . . . . . . . . . . 5-232 . . . . . . . . . . egsm_bcch_sd . . . . . 5-214 . . . . EN_PBGT_HO . . . . 4-11 2-234 2-244 2-246 2-248 2-250 2-253 2-256 2-259 . . . . . . . tru_id . . . . . . 5-241 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-227 2-229 2-231 . . . . . . . . . . . . . . . disp_severity . . . . . . disp_enable_stat . . . . .Technical Description BSS Command Reference disp_csfp_status . . . . . . . . . . . . . 7-31. . . . . . . . . . . . . 5-229 . . . . . . . . disp_hopping. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-34 . . . . . . . . . . . . dr_chan_mode_modify . . . . . . Index . . . . . . . disp_link_usage . 5-245 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-516 . . . . . . . . . . . DRI antenna_select . . . . 5-225 . . . . . . . . . . . . . . . . . 2-298 . . . . . . . . . . . . . . . . downlink_sync_timer . . . . . . . . . . . EN_INCOM_HO. . . . . . . . . . . . 5-238 . . . . . . . . . disp_nsvc . . . . . . . . . . . . . . . . . . DPC . . . . . . . . . . . . . . . . . . . . 5-219 . . . . . . . . . . . . . . 5-212 . . . . . dr_preference . . . eas_severity . . disp_interval . . . . disp_rtf_channel . . . . . . . . . . . . . . . . . . . . . . . 5-397 . 7-69. . . . . . . . . . . . . . . . . . . . . . . . . 5-247 . . . 5-207 . . . . . disp_level . . . . . disp_rtf_path . . . . . 5-216 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . disp_relay_contact . . . . . . 2-326 . . . . . . . . . . . 5-253 . . . . . . dr_allowed . . 5-251 . . egprs_init_dl_cs . . dtx_required . . disp_options . . . . . . . . . . . . . . . 5-227 . . EN_INTER_HO . . . . Dual Band Cells feature. . . . . . . . . . . . . . . . . . . 2-371 . . . Early MMI interaction . . . . . . . . . . . . . . . . . . . . dpc . . . . . . . . . . . dr_standard_congest . . . . download_ltu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . slot . . . . . disp_stats . . . . . . . . . . . . . . . . . . . . . . . . . . . cavity . . . . . . . . . . . . . . . . . . . . . . . . . . 7-78 . dl_rxqual_ho_allowed . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-626 IX-5 GMR-01 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-336 AXCDR . . . . . . 2-334 MSI . . . . . . 2-279. . . . . . . . . 2-364 . . . . . . . . . . . . . . . FC_T2. . . . . . . . . 2-357 M-Cell and Horizonmacro equipage chart . . . .) OML . . 2-356 GPRS equipage chart. . . . . . . . . . . . . . . . . . . . . 2-345 DRI (InCell sites) . . . . . . . . . . . . . . . . . . . . 2-368 . . . . . . . . . . . . . . . . . . . 2-367 . . . 2-344 DPROC . . . . . . . . . 2-370 2-332. . . . . . . . . . . . . . . . . . . . 2-327 ABSS . . . . 2-369 LMTL. . . . . . 2-338 CAGE. .) EN_RXLEV_HO. . . 2-336 DHP . . . . . 2-336 BSP . . 6-71 . . . . . 6-68 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-357 LCF. . 2-352 equipage hierachy charts . . . . . . . . . . . . . . . . . . . . 2-212. . . 5-211. . . . . . . . . . . . . . . 5-209. . . . . . extended_paging_active . . . ext_ho_allocation . . . . . . . . . . . . . . . . fdd_arfcn fdd_qmin . . . . ext_rtry_cand_prd . . . . . . 2-157 to 2-158. . . . . . . . . . . . . . . . 2-345. . . 5-717 enhanced_relief . . . 5-262. . . . . . 2-350 EAS (InCell sites) . 5-263 feature 23658 . . . . 5-809 EN_SDCCH_HO. . . . . . . . . . . . . . . . . . . . . 2-337 BSS . . . . . 1-10 eop_enabled . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-355 GPROC . . . . equip/unequip matrix . . 2-337 BTP. . . . . . . . . . . . . . . . . . . . . . . . . . 2-363 OMF . . 5-379. . . . . 2-341 CIC . . . . . . . . . . . . . 2-293. . . . . . RTF . . . . . . . PSP . . . . . . . . . . . . . 2-368 . . 2-106. . . . . . . . . . . . . . . 2-353 GCLK. . . . . . . . . . . . . . . erc_ta_priority . . . . . . . . . . . . . . . . . . . . . . .Index equip (contd. . . 2-335 GSL. . . . . . . . . 2-366 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SITE . . . . . . . . . . . 2-214 to 2-216. . . . . . . . . . . 2-300 to 2-303. . . . . . . . . . . . . . . . . . . 2-356 InCell equipage chart. . . . 6-69 . . . . . . . . RSL. . . 2-210. . . . . 2-17 . . . . . . . . . . . . . . . 2-340 CBL . . . PATH . . . . . . . . . . . . . . . . . . 2-351 EAS (M-Cell sites) . . . . . . . . . . . . . . . . 2-397 to 2-398 . . . . . . . . . . . . . . . 2-365 . . . . . . . . . XBL . . . . . . 2-354 GDS . . . . . PCU . . . . . . . . . . . . 2-333 KSW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-362 MTL . . . . . . 5-807 EN_RXQUAL_HO. . . . . . . . . . . . . . . . . . . . . 2-360 MSI (PCU only) . . . . . . . . . . . . . . . . . . . . . . . . . 2-367 . . . . . . . . 5-255 entering hexadecimal values ambiguous. . . 68P02901W23-P 23 Feb 2004 . . . . . . . . . . . . . . . . . . . . . . . ext_timeslots . . . . 2-331 Functions . . . . . . . 5-170. . . . . 2-101 to 2-102. . . . . . . . . . . . . . . . . . . . 2-344 CSFP . . . . . . . . . . . . 5-258 . . . . . . . . . ext_range_cell . . . . . . . . . . . . . . . . . . . . . . . . 2-342 COMB . . . . . . . . . 2-346 DRI (M-Cell and Horizonmacro sites) . . . . . . . . 2-363 . . . . . . . . 5-260 F FC_T1. . 2-347 DYNET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-73 . . 2-337 CAB . . . . 2-344 Devices . . . . . . . . . 5-257 . . . . . 2-360 MSI (M-Cell Sites Only) . . . . . . . . . . . . 5-256 equip . . . . . . . 7-32 . . . . . . . . . . . . . . RXCDR . . . . . . . . . . . . . . . . . . . 2-369 GBL . . 2-358. . . . . . . . . 5-381 IX-6 GMR-01 fdd_qoffset. 2-370 equip (contd. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-221. . . . . . . . . . . 6-72 . . . . . 2-293. . 2-375. 2-326. . . . . . . . 5-313. gprs_access_min . 5-430. . . . . 5-338. . . . . . 7-64 . . . . . . 5-295 . . . . 5-292. . . . 5-379. . . frequency_type. . . . . 5-434 to 5-435. . 5-594. 5-485. . . . . . 5-288. . . . . gprs_ms_pan_dec . 5-323. . . . . . . . . 5-117. . . . . . . . . . . . . 2-55. . 5-35. . 5-292 . 6-142. . 2-294. . . gprs_max_ul_ts . . . 2-235. . 2-243. . . . . . gci_error_clr_thresh . 6-74 . . . . 5-273 . . 2-95. . fm_cell_type . . . 5-293 to 5-294. . . . . 5-582. . . 4-30. 2-381 to 2-382. . 2-15 . . 5-725. . . . . cabinet. . . . 2-466. . 2-21. . . . . . . 5-274. . gci_error_gen_thresh . 4-8. . . . . . . . 7-36 5-264 2-376 5-266 . . . 2-359. . . . . . . . . . 5-326. . gprs_com_ms_class . . . 5-304. . . . . . . . . . . . 5-202. . . . . . . gprs_cr_margin . . 2-411. 5-245. . gprs_alarm_time . 5-418. . . . . . . . . . . . . . . . 5-288. . . 2-277. . 2-287 to 2-288. . . 5-232. . . 2-293. . . 2-393 to 2-394. cell . 2-344. . . 2-379 . . 5-315 . . . . . . . . . . . . 2-15 to 2-16. . 2-375. . 5-37 to 5-40. . . . . 5-381. . . . 5-26 to 5-33. . 5-284 . . 2-219. 6-10 3723 . . . . 7-66 . . . 5-613 4322 . t393 . . . . . 2-47 to 2-48. . 2-76. . . . . . . 2-270. . . . 4-28. . . . . . . . . . . gclk_qwarm_flag. . 5-390. gbl_thrput_period . . . . 68P02901W23-P 23 Feb 2004 . . . . . . 5-783 . . 5-269 . . . . . 5-271 . . . . . . 5-629. . . 5-290 . . . . . . . . . . gprs_drx_timer_max . 5-578. . . start_ts . 5-416. . . 5-801. . . . . . 7-62 to 7-63 4441 . . . . . . . . 5-275 . . 6-8. . . . . 5-315. 5-284. . . . . . . . . 6-70 flow_control_t2 . . 2-384 to 2-386. . . . 5-273. 5-379. . . . 2-365 to 2-366. . . . frequency_type. . . Interval expiry . 2-373 nsei . 5-71. . 5-574. . . . 5-608 to 5-609. . . 5-619 to 5-620 4445 . 5-446 to 5-447. . . gprs_dl_pwr_mode . 2-197 to 2-199. . 2-443. . 6-75. 5-542. . 2-220. . . gprs_min_prr_blks . gprs_intra_ho_allowed gprs_mac_mode . 5-633. . . . . 5-137. . 2-184. 2-57. . . . 2-336. . . . . . . . . . 5-585. . . . . . . . . . . . 5-282 . . . . . . . . . . . . 5-776. . . . . 5-576 . . . . . . 2-504. 5-281 . 5-35. . . . . . . . . . . 5-170. . . . . . . 5-293 . 5-286 5-288. . . gprs_bs_cv_max . . 5-454. . . . . . . . . 5-282. 2-210. . 5-549 flow_control_t1 . 4-5. . 2-423. . . . . 2-195. 5-42 to 5-50. . 5-611. 2-389. . . 4-3 4-3 4-3 . t391 . . 5-301. . . . . . . . . . 5-294 . 5-481 4415 . 2-421. . 2-50. . . 2-177. 2-53. . . 2-439. . 5-779. 2-355. 5-381 4449 . 5-616. . . . 2-408 to 2-409. 2-3. 2-6. . . 5-452. 5-268 . . . . 5-277 . function related commands . . . . . . 2-403. . 5-422 to 5-423. . . 5-21. 4-24. . . global_reset_repetitions. . . . . . 5-73 to 5-74. 5-442. . 5-142. . . . . 2-494. . . 5-576. . . . . 5-440. . . . . . 2-213. .) 2-353. 7-82 . 4-26. . . . . 2-72 to 2-73. . . . 5-69. . function ids requirements . . . . 2-14 G Gauge statistics . . . 5-83. 5-306. . . . . . 5-317. . . . . . . 5-473. . . . . . 2-468. gclk_cal_mode . . . gproc_slots . 5-267 . 5-279. . . 2-232. . . . . . 2-165 to 2-166. . . . . . . . 5-258. frequency_types_allowed . 5-277. . 5-243. . . . . . . . . 2-328. . 2-500 to 2-501. . 2-193. . 7-80 7-65. . . . . . . . . .Technical Description BSS Command Reference Index feature (contd. 5-297 IX-7 GMR-01 . GBL n391 . 5-276 . . gci_error_inc. 2-78. 2-43. . . . . . gprs_enabled . . . . . 2-446. 5-319. . . 5-377. . . 5-804 4354 . . . . . . . . . t392 . . . . . 2-356. . 5-410 to 5-411. . . . 2-187. . . . . . . . . 5-428. . 2-293. . . Threshold event reporting. . . . 5-270 . . . . . . . . . . . . . . 2-371 to 2-372. gprs_ms_pan_inc. . . . 7-34 . . . . . . . . . . . . . 4-22. . . . . 5-304 to 5-305. . full_pwr_rfloss . . . . 2-453. . . . . . . . 5-714 4471 . . . . . . 2-405. . 2-417. . . . . . 2-278. . 2-189. . 5-164. . 6-147 4040 . . . . . . . gprs_cell_cgt_thr . 5-730. 5-166. . . . 7-79 . . . FM ts_alloc_flag . . 2-296. . . . 2-61. . . . . . . . . .Index gprs_ms_pan_max . . . . . . . 6-11 5-64 6-12 6-89 5-458 5-615 5-617 5-341 . . . . ho_only_max_pwr . . . . . . . . . . . . . 5-371 68P02901W23-P 23 Feb 2004 . . . . hdsl_snr_hourly . . . hdsl_oos_mon_period . . . . . . . . . . ho_successful . . . . . . . hcs_thr . . . . . . . . . . . . 5-301 . hopping_systems_mobile_alloc HSN. . . . . . . . . . . . . gprs_reconfig_thresh_idle_tch. 3-6 . . . . . . . 5-370 . . . . . . . ho_margin_rxlev . . . hdsl_snr_daily . . 5-337 5-338 . . 6-85 . . . 6-88 . . . . . . . . . . . . . . . . . . . . . . . . . 6-89 . . 6-79 . . . ho_exist_congest . . . . . . . . hop_count_timer . protect_last_ts . . . . . . . . . . . . . hopping_systems_enabled . . . . . . . . . . . . HO_MARGIN_DEF . . . . . 5-355 . . . gsm cell id . . . . . . . . . . . . . . . . . . . . . . . . . hop_count_timer . 5-313 . . gprs_ul_dl_bias . . . . . . . . . . . . . . . . . 6-87 . . . . . . . . . . . . . . . hop_count . . . . . . . . . . . . 5-333 . . . . . gprs_pb . . . . hdsl_snr_losw . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-80 . . . 5-306 . . . . 2-397 . . . . . . . . . hdsl_losw_restore . 5-310 . . . . . . . . . . . . . . . . . . . . . . . 7-40 . . . . . . . . . . 5-364 . . . . . . gprs_t3192 . . . . . handover_required_current_ch . . . . . . ho_ack. . . . . . . . . 5-335 . . . . . . . . . . . . . . . . . . . . . . . . hexadecimal values . . . . . . . . . . . . . . . . . . gprs_ts_config_alg . . . . . . hdsl_snr_oos . . . . . . . . . . . . . . . . 5-299 . . . . . . . . . . . . . . bounce_protect_margin. ho_allocation. . . . . . . . 5-354 . . group_block_unblock_allowed gsl_lcf_mapping . . . . . . ho_margin_def . . 2-396 . . . . . 5-372 . gprs_ms_txpwr_max_cch . . . . . . hopping_systems_hsn. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . gprs_sig_bvci . 5-522 5-328 H HAND_REQ_REJECT . . . . . . . . . . . . . . . 6-82 . 7-38 . . . . . . . . . . . . . . . 6-84 . . GSM Parameter MS_TXPWR_MAX(n) . . . . . . ho_margin_rxqual . . . . . . . . . . . . . . . . . . . . . . history . . . . . . 5-308 . 2-397 . . . . . . . . . . . . handover_required_reject_switch handover_required_sp_ver_used UTRAN . . hdsl_snr_restore . . . . . gprs_penalty_time . . . . . . . . . . . . . . . . 5-317 . . hdsl_snr_daily_mon_period . . . . . 1-10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . hop_qual_enabled . 5-326 2-22. . . . . . 5-352 . . . . . . . . . . . 5-324 . . . ho_margin_type5 . . . . 6-78 . . . . bounce_protect_qual_tmr . . . 6-75 . . 5-368 . . . . . . . . . . . . . . . . gprs_pc_alpha . . . . . . . . ho_margin_cell. . . . . layer_number . . hdsl_snr_hourly_mon_period . . . . . . . . . . . 5-323 . . . ho_complete . . . . . . . . . . . . . 5-318 gprs_smg30_t3192 . . . . . . . . . . 5-385 . . . . gprs_reselect_offset . HDPC bounce_protect_cong_tmr . . . . ho_request . . . . . . . hdsl_modem_setting . . prioritize_microcell . . . . . . . . . . . . . . . . . . . . . 6-77 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-309 . . . . . . . . . . . . gsm_cell_id_format . . . . . . . . . . . . . . gprs_pc_meas_chan . . . . . 5-304 . . . . . . . . . . . . . . . . . . . . 7-42 5-342 5-344 5-345 5-347 5-340 5-348 5-350 IX-8 GMR-01 . . . . . . . . . . 3-4 . . . . . . . gprs_t3168 . 5-359 5-361. . . handover_power_level . . hdsl_restore_mon_period . . . . . . gprs_sched_beta . . . . . . . . . . . . . . . . . 5-336 . . . . . . . . . hopping_support . 5-366 . . . . . . . 5-321 . . . . gprs_network_operation_mode gprs_num_pmrs . . . . . handover_recognized_period . . 5-363 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-330 . 5-312 . . . . 5-356 . . help . . . . . . 6-80 . . . . . . . . . . . . . . ho_margin_usage_flag . . . . . . . . . . . . . . . . . . . 5-357 . . . ho_pwr_level_inner . . . . . . . . . . . . . . . . . . . . . 5-433. . . . . . 5-454 . . 5-395 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . immediate_assign_mode inc_prp_cap_ena . . intra_cell_handover_allowed . . . . . 5-406 L_RXLEV_UL_P . . 5-440 . . . . . 5-451 . . . index1 . . . 7-45 5-395 5-395 INT_BOUND_X3 . . . index2 . . . . . . . . . . . 5-415. . . . . . . . 5-444 5-445. . . . . . . . . . . . . lb_int_cr_calling . . . . . . . 5-432 L_RXQUAL_UL_H . 7-44 5-374 5-375 5-377 . . . . . . . . . . . . . . . . l_rxqual_ul_p_data . . . . . . . . . . . . . . . . . . . ins_device . . . . . . lb_int_global_reset_repetitions lb_int_sccp_released . . . . . 1-27 . . . 5-426 l_rxqual_dl_p_hopping_amr_fr . . . . . . . . . . . lb_int_dpc . . . . l_rxqual_ul_h_data . . . . . . . . . . . 5-434 l_rxqual_ul_h_amr_hr . 5-413. . . . . . . . . . . . . . . . . . . . . . l_rxqual_ul_p_hopping . . . . . . . . . . . . . . . . . . . . . . . . . . 7-49 . . . . . . . . . 5-386 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Technical Description BSS Command Reference Index I ias_connected . l_rxqual_ul_p_amr_hr . . . . . . . . . . . . . . . . INT_BOUND_X2 . . . . . . . . . . . . 5-410 l_rxqual_dl_h_amr_hr . . . . . . . . . . . . . . . . . . . . . . . inner_zone_alg . . . . . . . . . . . . . 5-442 . . . . . . . . interference based use algorithm. . . . . . . . . . 7-51 5-458 . . . . . . . . . . . . . . . . . . . . . l_rxqual_ul_h_hopping . . . . lapd_t200_timer . . . . . . 5-438 . . . . . . 6-95 IX-9 GMR-01 . . . . . . . 5-403 l_rxlev_ul_h . . l_rxqual_ul_h_hopping_amr_fr l_rxqual_ul_h_hopping_amr_hr l_rxqual_ul_p . . . . . . . . . . . . . . 5-456 . . . . . 7-46 . . . 5-395 . . . . . . . 5-400 L_RXLEV_DL_H . . . . . . . . . interband_ho_allowed . 7-47 . . . . . . . . . . . . . . . . . . . . . . . . inter_rat_enabled 4225 . . . . . . . . . . . 5-404 L_RXLEV_UL_H . . . . . . . L_RXQUAL_UL_P . . 5-422 l_rxqual_dl_p_amr_hr . . . . . . . . . . . . . . . . . . . 2-94 . interfer_bands . . . . . . 2-127 . . . . . . . . . . . initial_sync_timer . . . . . . . 5-407 l_rxqual_dl_h . 5-449. . . . . . . . . l_rxqual_ul_p_amr_fr. . . . . . . . . . . 6-93 5-459 5-460 . . . . . . . . . . . . . . . lapd_k . . . interfering_nbr . . . . . . . . . 5-408 L_RXQUAL_DL_H . . . . . . . . . . . . . . . . . . . . lb_int_calling_pci . . . . 5-430 l_rxqual_ul_h . . . . . . . layer_number . . . . . . 5-427 l_rxqual_dl_p_amr_fr. . . . . . . . . . . . . . . 6-90 5-383 2-380 . . . . . . . . . . . . . . . . . . . . . . . . 5-412 l_rxqual_dl_h_hopping . . . . . . intave . . 5-446 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . language_id see: data_coding_scheme . . . . 5-450 . . 5-390 5-392 5-394 5-384 2-397 5-396 K ksw_config . 6-92 . . . . . . . . . 5-439 l_rxqual_dl_h_amr_fr. . . . . . . . . . . 5-395 . . . . . . 5-402 L_RXLEV_DL_P . . . . . . . . . . . . . . . . . . . . . . . . . 5-420 L_RXQUAL_DL_P . . . . . . . . . . . . . . . . . . . . . Initial SYSGEN mode . . lb_int_bssmap_t4. . . . . . . . . . . . . . . . lb_int_bssmap_t13 . . . . 5-398 L l_rxlev_dl_h . . illegal_circuit_id . . . . . . . . . . lb_int_called_pci . . . . . . 5-421. . . . . . . . . . . . lapd_n200 . . . . . . . . . . . . . . 5-409. . 5-423 l_rxqual_dl_p_data . . . 5-416 l_rxqual_dl_h_hopping_amr_hr . . . 5-401 l_rxlev_dl_p . . . l_rxqual_ul_p_hopping_amr_fr l_rxqual_ul_p_hopping_amr_hr land_layer1_mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . lb_int_clear_command . . . . . . . . . . 5-388 . . inter_cell_handover_allowed . . . . . INT_BOUND_X5 . . . . . . . . . . . . INT_BOUND_X4 . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-95 . . . . . . . . . . . . . 5-448 . . 5-425. . . . . 5-452 . . . 5-405 l_rxlev_ul_p . . . . . . . . . . int_hdsl_modem . . . . . 5-435 68P02901W23-P 23 Feb 2004 . . . . . . . . 5-418 l_rxqual_dl_p . . 5-424 l_rxqual_dl_p_hopping . . . . . . . 5-411 l_rxqual_dl_h_data . . . . . . . . . 5-436 . . . . . INT_BOUND_X1 . 5-437 l_rxqual_ul_h_amr_fr. . . . . 6-94 5-461 5-462 5-463 . . . . . . . . . . . . . . 5-447 . int_antenna . . . . . . . . . . . . . . . . 5-414 l_rxqual_dl_h_hopping_amr_fr . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-428 l_rxqual_dl_p_hopping_amr_hr . . . . . max_q_length_sdcch . . . . . . . . 5-502 IX-10 GMR-01 MMS (contd. . . . . . . . . . mb_tch_congest_thres . . . . 5-483 . . . . . . . . . . . . . . . . . . . . . . . . . . . . man . . . . . . . . . mb_preference . . . . . . . . lb_int_ss7_l3_t14 . . . . . 2-397 . . . . . . . . . . missing_rpt . . . . . 7-67 . . . . . . . . . . . . . . . . . . 2-393 . . lb_int_ss7_slt_t1 . . . . lb_int_ss7_l2_t5 . . . . . . . . . . . lb_int_ss7_l2_t4 . . . . . . lb_int_ss7_l3_t23 . . . . . . . . . . . . . . . . . . . . . . . . . . . . ba_bcch . . . . 5-475 . . . . . . . . LCF max_cbls . . 2-390 . . . . . . . . max_ms_dl_buffer . . . . . . . . . . lb_int_ss7_l2_t6 . . . . . . . 2-397 . lmtl_loadshare_granularity local_maintenance . . . . . . . . mode_modify . . . . . . . 5-487 . . . . . . . . . . . 1-11 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-503 . . . . . . . . . . . . . . . . . . . . . modify_neighbor . . . . . . . . . . . . . . . . . . . . . . . . . 2-397 . . . lb_int_ss7_l3_t1 . . 5-505 . . . . . 2-398 . . . . . . . . . . . . . . . . . . MMI commands availability by location . . . . . . lcs_perf_location . . . . . . . . . . . max_ms_dl_rate . . . . . . . . . . . . . . . 1-11 . . . . . . . . . . . . . . . . 5-489 . . . . . . . . . mmi_cell_id_format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ho_margin_rxqual . . 6-122 . . . . . . . . . . . . lb_int_ss7_l2_t3 . . . 7-54 . . 3-8 . . . . . . . MAX_RETRANS . . . . . max_rst_ckt_timer_exps . . . . . . . . . . . . . . mms_priority . . . . . . . . 5-501 . . . . . . . . . pbgt_hreqave . . . . . . . . . . . . . . . . . . . . mode_rr_modify_ack . . . . . 5-497 . . . . . . ms_txpwr_max . . . . . . . . . . 7-53 . . . . . . . . . . . . . . . . . . . . 5-488 . mms_priority. . . . . . . . . . . . . . . . . . . 5-476 . . . . . . . . . . max_number_of_sdcchs . max_gsls . . . . . . . . . . . lb_int_ss7_l2_t2 . . . . . . . . . . . . . . 2-398 68P02901W23-P 23 Feb 2004 . . . . . . . max_cbls . . . . . . . 5-500 . . . . . . . . . lcs_segmentation . . 2-396 . . max_dris. . . . . . . MMI command list . . . . . . . . 5-491 . . . . . . . 2-397 . . . . lb_int_sccp_tias . . . . . 5-469 . . . . . . . . . . . . . . . . . 1-15 . . 7-57 . . . . . . . . . . . . . diversity_enabled . . .Index lb_int_sccp_tconn_est lb_int_sccp_tiar . ba_gprs . . . . . . 2-397 . . . . . . . . 2-397 . . . . rxlev_min_cell. . . 6-125 . . . . . . . 7-53 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-11 . . . . . . . max_q_length_channel . . . . . . . 5-480 5-481. max_tx_ms . . . . . . . . . . . . . . . mms_config_type . . . . . . . dr_allowed . . . . . . 7-59 . . . . . . . . . . . . . . . 5-464 . . . . . lb_int_ss7_l2_t7 . . . . lb_int_ss7_l3_t13 . . . . . . . . . . . 7-57 . . . . . 2-397 . . 7-9 . . . . . . . . . . . . . . . . ho_margin_cell . . . . . . . . . . . . . . . . . . 7-56 5-481. . . . . . . . . 2-395 . . . . . . . lcs_mode . . . . . . . . . . . . . . . . . 6-118 6-119 6-120 6-121 . . . . . . . . . . . . . . . . . . 2-385 . link_about_to_fail . . . . . . . 2-396 . . . . . . adap_trigger_pbgt_nbr adj_chan_intf_test . . M Maintenance (Fault Management) about . . . . . . . . . . 2-397 . max_tx_bts . . . . . . . . . . . . . . . . . . . . . . . max_retran. . . . . . . . . . . . . 2-396 . . . . . 5-471 . . . mod_nsvc . . . . 5-490 . lb_int_ss7_l3_t17 . . . . mod_conn . . . . . . lock_device . . Miscellaneous Commands about . . . scr_code. . . . . . . . . . . . . . . . 6-96 6-97 6-98 6-99 6-100 6-101 6-102 6-103 6-104 6-105 6-106 6-107 6-108 6-109 6-110 6-111 6-112 6-113 6-114 6-116 . . . . . . . . 1-4 . . . . . . interfering_nbr . . . . . link_fail . . . 7-7. . . . . . . . 1-3 . . . . . . . . . . . . . . . . . . . . . . . lb_int_ss7_l3_t4 . . . . . . . . . lb_int_t_stat_info. neighboring_range . max_mtls . . . . . . . . . . . . . . . . . . . . . . lb_int_ss7_l3_t2 . . . max_gsla . . .) ber_oos_mon_period . . . . . . 2-396 . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-478 . . . . . . . . . . . . . availability by SYSGEN mode conventions . . . . . . . . . . . . 6-124 . . . . . . . . . . . . lb_int_sccp_trel . . MMS . . . List of MMI commands . . . . . fdd_arfcn . . . . . . . . . . . . . . . . . . . . . . . . lb_int_ss7_l3_t5 . . . 2-397 . . . . . . . . . . . . . . . . . . . 7-59 . . . . . . 7-56 . . . . . . . lb_int_ss7_l2_t1 . . . 6-127 . . lb_int_ss7_l3_t12 . . . 5-499 . . . . . 6-123 . . . 5-485 . . . . . congest_ho_margin . . . . . . . . . . . . . . . . 2-396 . . 5-477 . . . . . . . . lcs_supervision. . . . . . . . . . . . lb_int_spi . . . . . nbit . . . . . . . . . . . . . max_mtls . . . . 1-9 . . . . . mms_cat_enable . . . . . . . . . . . . . . . max_gprs_ts_per_carrier . . . low_sig_thresh . . . . . . . . . . . . . . . lta_alarm_range . . . . ho_margin_rxlev . . . pbgt_alg_type . . . . . . 5-467 . . 5-472 . . . . . 2-396 . . . 2-396 . . . . . . . . . . . . . . lb_int_ss7_l3_t22 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-183 . . . . ns_block_timer. . . . . . . . . . . . . . . . . nc_reporting_period_i nc_reporting_period_t NCC . . . . . . . . . . . . . . . . . . . . 6-46 . . . . . . . . . . . . . . ms_max_range . . . . . . . . . . ns_burst_size mod_nsvc command . . . 2-402 . N5 . . . . 6-45 . . . . . . . . . . . . . . . . ns_test_timer. . . 6-67 . . . . . . . . . . nsei . . . 5-536 . . . . . . . . . . . . . . . ms_sapi3_est. . . . . . . . ncc_of_plmn_allowed nccr_enabled . . . . . N1 . . . . . . . MS_TXPWR_MAX_DEF . . ns_commit_info_rate mod_nsvc command . . . . 5-185 . 2-393 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . msc_qt. . . . . . . . . . ms_power_offset . . . . . . . . . . . . . . . . . . . . 5-510 . . . . . MS_RANGE_MAX . . . . 5-528 . . . . . ms_txpwr_max_inner. . . . . . . . . . 5-525 . . . . num_emerg_rejected . n391. . . . . . . msc_release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-59 . 7-68 . . . . . . . . 2-397 . . . . . . . . . . . . . . . . 5-509 . . . 5-540 . . . . . . . . . . . 5-498 . . . . . . . . . . . . . . . . mspwr_alg . . . . . . . . . . 5-578 . . . . . . . . . . . 5-515 . . . . . . . . . . . . . . transcoding-capability . . 6-73 . . . . . . . . . . . . . . . . . . ms_txpwr_max_def. . . . . . 5-520 . . . . . . . . . . network_control_order ni . . 6-136 . . ms_p_con_ack . . 2-393 . . . . 5-517 . . . . . . . . . . . . . . . . . ns_block_retries . . . . MTCRM_ADD_ACC_CLASS . . . . . . . . MTCRM_HANDOVER_ACK . . . . . . . . . . . 6-44 . . . . . . . . . . . . . . nc_non_drx_period . . . . . . 2-397 . . . . . . ns_unblock_retries . . . . . . . . 2-360 5-546 6-137 5-547 6-138 . . . . . 5-530 . . . 7-61 . . . . . . . . . . . . . . . . . . . . . . . . . . 7-66 . . . . . . . 5-526 . . . . . . . . . . . . . ns_alive_timer . . . . . . N3 . . . . . . msc_preference . . . . . . . . . . . . num_emerg_tch_kill . . . . num_emerg_access . . . . . . . . 5-179 . . . . . . . 7-64 . . . . . . . . . . . . . . . . . . . . . . . . N4 . . MTCRM_REGISTER_EXP. . . . 6-43 . . . . . . .) synchronized . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . modify_value . . . . . . . . . . MSI msc_mms_id . . . . . . . . 68P02901W23-P 23 Feb 2004 . . . . . . . . . . . . . . . . . . . MTCRM_CBT3 . . . . ms_txpwr_max_cell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-133 . . . . . . . . nccrOpt . . 5-523 . . . . . msi_type. . . . . . . . . msi_type . . . ms_txpwr_max_cch . Index . . . . . . . . . . 6-71 . . . . mtl_loadshare_granularity . . . 5-533 N n_avg_i . . . . . . . . . . . 5-542 . . . . . . . . . . . . . . . . . . . . . . . 6-134 . MTCRM_EMERG_RESERVED . . . . . n392. . . . . . . . . . . . . . . . . . . . . . . . . . . 5-77 . . . ms_distance_allowed . . . neighbor_journal . 6-131 . . . . . . . . . . . . . . ns_alive_retries . . . . 6-2 . . . . . . . . . . . . ns_reset_timer . . . . . . 5-538 5-539. . . ns_burst_excess mod_nsvc command . MULT bsic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . n393. . . . . . . . . num_emerg_term_sdcch . . . 7-67 . . . . . . . . . . 5-511 . . . . . . . . . 5-513 . . . . . . . . . . 2-397 . . . . . IX-11 GMR-01 . . . . . . . . . ms_p_con_interval . 6-129 . 5-181 . . . . . . . . . . . . . . N6 . . . . . . . . . . . . 5-189 . . . . . . . . . . . . . . . . . . . . . . 7-61 7-62 7-85 7-62 5-531 . . . . . . N8 . . . . . . MTCRM_FC_T2. . . . . . . . . . . num_audit_retires . MTCRM_CARRIER_FREE_IMMEDIATE MTCRM_CBT1 . . MS_TXPWR_MAX . . . . . . . . . 5-507 . . . 6-83 6-151 6-153 5-532 . 5-191 . . . . . . . . . . . . . . . . . . . . . . . . . . multiband_reporting . . . . . . . . MTCRM_DEOC_INTACT . . 5-177 . . . . . . . . . . MS_TXPWR_MAX_CCH . . . . 5-535 . . MTCRM_FC_T1. . . . . . . . . 2-393 6-139 6-140 6-141 5-548 5-549 5-550 5-551 5-552 5-553 5-554 5-555 5-556 5-557 5-559 . . N2 . . . . . . . . num_gbl_dl_thrput_samples num_gbl_ul_thrput_samples number_of_preferred_cells . . . . . . . . . . . . . . . . . . . . . . . . . . ne_id . . . . . . . . . . . 5-518 . . . . ms_txpwr_max. . . . . . . . . . . . . . 5-537 . . . 5-521 . . . . . . ns_reset_period . . . . . 5-187 . . . . . . . . neighbor_report_timer neighboring_range . . 7-65 . . . . . . . . . ms_power_control_allowed . . . . . . . . . . . . MTCRM_RF_CHAN_REL_ACK . . . . . . . . . . . . . number_sdcchs_preferred . . . . . . . . . . . . . . . . . . MTCRM_CBT2 . . . . . . . . . . . . . . 5-524 5-385. . . . . . . . . . . . . . nbit . . . . . . . 5-544 NIU equip command . . . . . . . . . . N7 . . . . . . . . . . . .Technical Description BSS Command Reference modify_neighbor (contd. . . msc_mms_id . . . . . . . . packet_size . . P6 . . . . . . . . . . . . . . . . 5-611 . . percent_traf_cs . . phase_lock_retry . . . . . . . 2-143 . . . . . . 5-606 . . . . . . . . . . . . . . . . . . . 6-145 . . . 5-583 . 5-616 . . . . . . . . . . . . . pic_error_inc. . . . . . . . 5-582 . power based use algorithm . . 7-71 . pccch_drx_timer_max pcr_enable . . . . . . . . . P1 . . . . pcu_red_map_01 . . . . . . . . . . . . . . 5-581 . . phase2_resource_ind_allowed . 5-177 . . . . opto_reporting . . . 5-185 . . . . . . . 5-609 . parameter defaults . . . . . . . . . . . . . . . . . . . . . . 6-142 . 5-599 5-601. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-146 . P3 . . . . . pcr_n2 . . . . . . . . . . . . . . PENALTY_TIME . . . . . 5-572 . . . . . . . . . . . . . . . . . . . . . POW_INC_STEP_SIZE . . . . . . . pow_inc_step_size_ul . . . . . . . . . . 5-585 . . pkt_radio_type . . . . . . . . . 5-594 . . . . . . . . . . . . . . . . . 5-592 5-593. . . . . . . . . . . . prp_capacity_opt feature . . . . . . . . . . . . . . 5-77 . . . . . . . . . . . . . . . . . . pcr_n1 . . . . . . . . . . . . . . . . . . . . . . . . . primary_pcu . . . 5-598 . . poor_initial_assignment. . . . . . . . . . . . . . . . . . . . . pic_error_clr_thresh . . . . . . . . 5-580 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-587 . . . . . . . . . . . . 5-570 . . . . . . . . . . . . 5-569 . . . . . . . . 5-583 . . . . . . . . . . . . . . . . . . override_intra_bss_pre_transfer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-183 . . . . . . . . . . . . . . . 5-181 . . . . . . . . . . . . . . 5-648 . . . . . . . . . . . . . penalty_time . . . . . . pbgt_alg_type . . 5-537 . . . . . . . . . pow_red_step_size_dl . . pref_rtf_id . . . . . . . . . . . . 5-607 . . . . . . . . . 2-397 . . . . . . P P_CON_ACK . . . . . . . . . . . . . . page . . . . . . . . . . . . priority_class. . 5-191 . . . . . . . . . prach_max_retran . . . . . . . . . . passwords . . 5-579 . . . . . . . . . . . PLMN_PERMITTED . . . . P5 . . . . . . . . . . . . . . . . . . . . . . . . . . 5-617 . . . . option_emergency_preempt . P7 . . . . . . option_alg_a5_7 . . . . . . . . . . . . . . pwr_handover_allowed . . . . . pcu_red_map_22 . PWRC. . . . . . . . P4 . . . . . . prach_tx_int . . . . . . . . . . . . . . 5-568 . . . . . . . . . . . . . . . . pbgt_hreqave. . . . . . . option_alg_a5_1 option_alg_a5_2 option_alg_a5_3 option_alg_a5_4 option_alg_a5_5 . . . . P_CON_INTERVAL . . . . . . . . . . . . . . . . . pow_inc_step_size_dl . . . . . . . . . 5-603 . psi1_repeat_period . . 5-514 . . . . P2 . . . . . . . . . . . . . . . . . . . . . 2-397 . . 5-589 . . . . . P8 . . 2-405 . phase_lock_duration . PICP equip command . . . 5-583 . . . . . . . . . . . . . . . prioritize_microcell. . . . . . . . . . . . . 2-362 . 5-583 . . . . . . . . 5-384 . . . . . . . pwrc. . . phase_lock_gclk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-588 IX-12 GMR-01 . . . . . 5-619 5-620 6-147 5-621 5-623 5-624 68P02901W23-P 23 Feb 2004 . . . . . . . . . . . . . . . . . 7-69 . . . .Index O opc . . . . pool_gproc_preemption. . . . . outer_zone_usage_level. . . . . . . . . . . . . . . . . . . prr_aggr_factor. . . . . . . . . . . . . pic_error_gen_thresh . . . . . . . . . . . . . . pcu_red_map_21 . . . . . . 5-600 . . . . 5-590 . . . . PLMN . 5-583 . . . . . . . . . . . . . . . . . . . . . . . . . protect_last_ts . . . . . . . . 5-591 . . . . . . . . . . . . . . . . 1-3 . 5-604 . . . . . . . . . . . pcu_red_map_12 . . . . . . . . . prach_s . . . . . . . . . pcu_red_map_02 . pcu_redundancy . . pbgt_mode. 5-608 . . . . . 5-615 . . . . . . . . . . . . . 5-512 5-91. . . . . . . . pow_red_step_size_ul . . . . . . . . . . . . . . . . . . . . 2-24 . 5-561 5-563 5-564 5-565 5-566 5-567 option_alg_a5_6 . 5-583 . . . . . . . . . . . . . . pcu_red_map_11 . 6-144 . . POW_RED_STEP_SIZE . . . . . . . 5-584 . . . 5-613 . . . . 5-602 5-605. . . . . . 5-189 . . . . . . . 5-187 . 5-575 . . . . 5-89. . . . . . . . 5-573 phase2_classmark_allowed . . . . . . . . . . . . . . . . . . . . . . persistence_level . . . . . . . . . . . . . 5-179 . . . . . . . . . . . . . . red_loss_hourly . . . . . . . . . . . . . . . . . . rpd_period . . . . . . . . . . . . . . . . RADIO_LINK_TIMEOUT(BS) . . rr_t3212 . . 5-792 . . . . . . . . . . . . . . reattempt_pl . . . . . . . . . . . . . . . . RACH_BUSY_THRES. . . rxlev_dl_zone . 5-470 . . . . . . . . . . . . . 5-641 . . . . . . . . . . . . . . . . . . rach_load_type . . . . . . . . . .Technical Description BSS Command Reference Index Q qsearch_c_initial qsearch_i . . . . . . rf_chan_rel_ack . . . . . . . . . . . . ra_reselect_hysteresis. . . . . . rtry_cand_prd . . . . . . . . . . . . . . . . . . . . remote_loss_oos . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-683 . . . . . . . . . . res_ts_less_one_carrier . . . . . . . . . . . . remote_loss_daily . . 7-68 . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-640 5-119. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-75 . 6-25 . . . . . . . . rr_t3111_tch . . . . . . . rach_load_period . . . . . 5-646 . . . . RSL lapd_k. . . . . . RAC . . . . . . . . . . . . . . . . qsearch_p . . . . . . . . . 5-631 . 5-644 . . . . retry_candidate_period . . . . RF_RES_IND_PERIOD rpd_offset . . . 6-40 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-39 6-128 . . . . . . . . . . . . . . 5-638 . . . rr_t3105 . . . . remote_loss_restore . . . . . . . . . 5-656 2-411 2-414 5-649 5-650 5-651 5-652 5-653 5-654 5-655 6-151 5-657 5-659 5-660 5-661 5-662 5-663 5-664 5-665 5-667 5-669 5-671 2-416 2-421 2-422 6-170 6-152 rf_res_ind_period . . . 6-86 6-130 . . . . . sd_priority. . . . . lapd_t200_timer . . 5-637 . . . . . . . . . RRSM_MTD . . . . . . . 6-149 . . . . rach_load_threshold . . . . . . . . . . . . . . . . . . red_loss_daily . . 6-35 . . . . . . . . . . . . . . . . . . 5-685 5-385. . . . . . . . . . . . . . . radio_link_timeout . . . . . . . . rtf_path_enable. . . . . . . . . . . . . . . . . . . . remote_time_oos . rel_tim_adv . . . . . . . . . . . . . . . . . . . . . . . . . . . . rsl_rate . . . 5-647 . . . rci_error_clr_thresh. . . . 6-170 . . . . . . . . . . 5-627 5-628 5-629 2-407 5-625 R ra_colour . rxlev_dl_pc . . . rxlev_access_min . . . . . . . . . . . . . . . . . . . report_resource_tch_f_low_water_mark . . . . . . . . . . . . . . . . . . . . . RRSM_MTY . . . . . . . . red_time_oos. . . . . . . . . . . . . . . . . . . . . . . . 6-23 . . . . . . . . 5-680 . . . . . . . . . . . . . . . . . . . . . . 6-49 . . . . . . . . . . . . . . . . . 5-639 . . . . . trx_pwr_red . . RRSM_T11 . . . . 5-673 5-673 5-674 5-675 5-676 5-678 6-154 6-156 6-158 6-160 6-162 6-164 6-166 6-168 . . . . lapd_n200 . . . . . . . . . . . . . . . . . . . . . . reset_device . . . . . . . . red_loss_oos . . . . . . . . . rr_t3109 . . . 7-73 . . . . . . . . . . . . . 5-643 . . . . 6-51 . . . . . . . . . RXLEV_ACCESS_MIN rxlev_dl_ho . . . . . rr_t3101 . . . . . . . . . . . . . . . . . . . . . rapid_pwr_down . queue_management_information . . . . . RRSM_MTE1 . 7-87 . . . . 5-635 . . . . . . res_gprs_pdchs. . reset_site . . . . . . . . . . . . . 5-633 . . . . . . RXCDR ne_id . remote_loss_hourly. . . . . . . . . . . . . . 68P02901W23-P 23 Feb 2004 . . . . . . . RE reestablish allowed . . . . . . . . . . . . . . . . . . . . . . . RTF sd_load . rpd_trigger . rr_ny1_rep . . . . . . . . . . . . . . . . . . rxlev_min_cell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . reestablish_allowed. . . . . . . . . . . . . . . . . . . RRSM_T10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . rr_t3103 . RRSM_T8 . . . . . . . . . . . . . . . . . . . . . . . RRSM_MTQ . . . . . . red_time_restore . . . . . . . . . . . . . . 5-687 . RACH_MEAS_PERIOD . . . . red_loss_restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . rpt_bad_qual_no_mr . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . RRSM_MTW . . . . . . 5-635 . . . . . . . . . . . . . . . . 5-642 . . . . . . . . . . . . . . . . . . . rr_t3111_sd . . . . . . . . . . . . . . . 7-47 7-49 7-51 7-72 . . . . . . . . . . . . . . . . . . . . . . . 5-681 . . . . . . . . . . . . . . 2-397 IX-13 GMR-01 . . . . . . . . . . . reassign . . . . query_audits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . remote_time_restore . . . . . . . . . RRSM_AUDIT_TIMER RRSM_MTA. report_resource_tch_f_high_water_mark . . . . . . . . . . . . . . rac parameter . . . . . . . . . . . . . . . . RXLEV_DL_IH . . . . . . . . . . 5-682 . . RADIO_LINK_TIMEOUT(MS) . . radio_chan_released . . rci_error_gen_thresh . . . . . register_exp . . . reset_ltu . . . . . . . . . . . 5-732 . . . . . . . . . . ss7_l2_t7 . . . 6-176 . . Security Management about . . . . . . . . . . . . . . . . . . . . . . . 5-722 . . . . . . . . . . . . . . . . . sd_load . .Index rxlev_min_def . . . . . . ssm_timer_value. . . . . . . . . . . . . . . . . . . . . . . . . 6-84 6-174 . . . . . . . second_asgnmnt . . . . . . . . . . . . . . . . . . sdcch_timer_ho . . . . . . . site_audit . . . . . . . . . . . smg_gb_vers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . sdcch_need_low_water_mark . . . . . . . . . . . . . 5-735 . . . . . . . . . . . . . . . . . . . . ss7_l3_t12 . . . . . . . 6-57 6-150 . . . sms_ul_allowed . . . . . . . . . . . . . . . . . . . . . . . rxqual_ul_ho . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SSM_MTL . . . . . . . . . . . . . 7-79 5-748 S sacch_info . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SSMAUDIT_TIMER . 2-433 . . ss7_l2_t5 . . . . . . . . . 5-714 . . . . . . . . . . . . . . . . . . . . ss7_l3_t22 . . . . . . . SSM_MTH . . sccp_tconn_est . . . . . . 7-73 . . 6-13 6-181 5-745 . . . . . . . . . . . . . . . . . . . . . 6-181 . stat_interval . . . . . . . SSM_MTC . . . . . . . . . . . . . . . . . ssp_burst_limit . . . . . . . . . 2-431 . . . . . . . . . . . . . . . . . . . 5-707 . 6-178 . 5-723 . . . . . . . . . . . . . . . 6-14 5-746 5-747 6-208 . . . . 5-693 5-385. . . . . . . . . . . . . . . 5-737 . SITE rsl_rate . . . . . . . sccp_tiar . . . . . . . . . . . . slip_loss_oos. . . . . . . . . . . . . . SPI . SSM_MTN . . . ssp_burst_delay . . . . . . . . . . . . . . . . . . . . . ss7_l3_t14 . . . . . . . . . . . . . . . . . . 5-689 . . . . . . . . . . soft_reset . . . . . 5-718 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . sdcch_need_high_water_mark. . 5-712 . . . . ssm_critical_overload_threshold. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-705 . . . . . . . . ss7_mode . 5-740 . rxlev_ul_ho . . . . . . . . . . . . . . . . . . . . . . 5-728 . . . . . . . . . . . . . . . . . . . . . . . . . . 2-438 . . . . . . ss7_slt_t1 . 6-33 6-177 6-179 . . . . . . . . . . . . . . . . . slip_loss_hourly . . sms_dl_allowed . . . . SSM_MTX . sap_interval . . sdcch_tch_band_reassign_delay . . . . . 6-88 . . . . . . . . . . . . . . . . . . SSM_TQHO . . . SLT_T1_TIMER . . 6-4 . slip_loss_restore . . . . . . . . . . . . . . . . . . . . . . . . . ss7_l2_t6 . . . . . . . . . . . . . . set_relay_contact . . . . . . . . . . . . . . . . . . . . . . . . . . ss7_l3_t17 . . . . . . . . . . . 6-13 . . . . . 2-427 . . . . . 7-75 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SSM_MTI . . . . . 6-174 . . . . . . . ssm_normal_overload_threshold SSM_T7 . . . . . . . . . . . . sgsn_release . . . rxqual_ul_pc . 5-695 . . . sap_end_time . . . . . . slot . . . . . . . . . . . . . . sccp_trel . . . 2-442 IX-14 GMR-01 68P02901W23-P 23 Feb 2004 . . . . . . . . . . sap_device_type . . . . . . . ss7_l3_t4 . . . . . . . SSM_TIAR . . . . . . . . . . . . . . . . . . . . 6-37 . . . . . . . 6-87 . . . 5-720 . . 5-691 . . . SSM_MTG . . . . . . . . . . . . . . . 5-710 . . . . . . 5-726 5-385. . . . 6-180 . . . . . . . . 5-731 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-207 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . start_ack . . . 6-175 . . . . . sap_audit_type . . . . . . . . . . . . . rxqual_dl_pc . . . . . 6-172 . . . . . . sccp_bssap_mgt . . . . . . . . .10 . . . . . . . search_prio_3g . . . . . . . . . . . . . . . ss7_l3_t2 . . . . . . . . . . . . . . . . . . . . . . sccp_tias. . . 5-734 . . 7-78 . . . . . . sccp_released . . . . . . 5-738 . . . . . start_ts. . . . . . . . ss7_l2_t4 . . . 6-53 . . . . . . . . . set_full_power . . . . . . . . RXLEV_UL_IH rxlev_ul_pc . . . . . . 7-77 . . . . . 5-725 . . . . . SSM_TIAS . . . . 6-182 6-183 6-184 6-186 6-188 6-190 6-191 6-192 6-194 6-195 6-196 6-197 6-198 6-199 6-200 6-201 6-203 6-205 6-206 5-741 6-207 5-743 . . ss7_l3_t1 . . . . . . . . . . . . . . . . SSM_MTB1 . . . . . . . . . . . . . . . . . . . . . . . . 5-730 . . . . . . . ss7_l2_t2 . . . . . . . . SSM_MTK . . . . . . SSM_MTV . . . . . . . . . . . . . . . . . . . . . . . . . . ss7_l3_t13 . . . . . . . . . . . . . . . . . . . . . . . . . 5-706 . . . . . . . . . . . . . . . . . SSM_MTJ . . . scr_enabled . . . . . . . . . . 1-3 . . . . . . . . . . . . . . . . . 5-708 . . . . . sap_start_time . . 5-716 . . . . sms_tch_chan . . . slip_loss_daily . . . . . 5-697 5-699 5-701 5-703 spi. . . . . . . . . . . ss7_l2_t3 . . . . . . . . . . . . . . rxqual_dl_ho . . . . . . . . . . . . ss7_l2_t1 . shared_timeslots . shutdown_device . . . . . . . . . . . . . . . . . sd_priority . 5-736 . 6-68 . . . . . . . . . . . . . . . . . . . . . rxlev_ul_zone . . . . . . . . . . . . . . . . . . ss7_l3_t23 . . . . . . . . sdcch_ho . . . . . . . secondary_freq_type . . . . 7-72 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ss7_l3_t5 . . . . . . sm_audit_response . . . . . . . . . . 5-796 . . . . . . . . . . . . . . 6-167 . . . . . T2 (CCITT) . . . . . . . . . . . . . . . . . . . . . . . 6-155 . . . . . . . 5-763 . . Gauge statistics . 5-764 . . . . . . . . . . . . . . . . . . . . . tch_congest_prevent_thres . . 6-48 . . 5-753 . . . . . 5-778 . . . . . . . . Distribution statistics . . . . . . . . . . . . . . . . . . . . . . trace_call command . . 5-468 . 7-85 . . . . . . . . . . . . . . . . . . . . . 2-397 Syntax command syntax . . . . . . . surround_cell . . . . . . . . . . 1-4 . 6-185 . . . . . . . 5-758 sync_loss_restore. . . . . . . . . 2-461 . . . . . . . . . . . . . . . . 5-779 . . . . . . . . . . . 5-771 . . swfm_enable . . . 5-773 . T12_TIMER . . . . . . . . . . T17_TIMER . . . . . . . . . . . . . T1_TIMER . . . . . . . . . . . . . . . . . . . . . Timers . . . . . . . . . 6-169 . 6-198 . T3109 . . . . . . . . . . . . . . . . . . . . trunk_critical_threshold. 5-782 . . . . . T5 (CCITT) . . . . . . . . 5-781 . . . T1 (CCITT) . 7-83 5-319. . . . . . . . . . . . . . . . . . . . . . . . . . . 5-767 . . . 1-27 sysgen_mode on . . . 7-82 . . . . . . . . . 6-157 . . . . . . . . . . . . . . . . . . . . . . . . 2-463 . . . . . . . . . . . . . 6-195 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . T_SDCCH_HO_OWED . . . . . . . . . . . . . . . . . . . . . . . . . . Duration statistics . . . . . . . . . . . . . . 7-87 . . . . . . 6-159 . . . 68P02901W23-P 23 Feb 2004 . . . . . . . . . timeouts . . . . . . T3105 . . . T6 (CCITT) . . . . . . . . . . . . . . . . . . TM_HO_T3105 . . . . . . . . . . . . . . . . . . . . . . 1-9 SYSGEN OFF mode . t_stat_info . . . . . . . . . . trace_msgs_after_ho . . . . . . . . . . . . . . . . . . . . . . . . timing_advance_period . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-474 . . . . . . . . . . . . . . 5-754 T t_avg_t . . . . . . . . . . . . . . . . . . . . . 5-756 sync_loss_hourly . . . . . . . . . . . . tch_busy_norm_threshold . 6-161 . 6-126 . . . trace_stop . . . . T7 (CCITT) . . . . . . . . . . 6-204 . . . . . . . 6-81 . . . . . . . TM_HO_NY1_REP . . . . 6-197 . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-199 . . . . . . . . . . . . . . . . . . . T14_TIMER . . tch_full_need_low_water_mark TCONN_EST . . TM_MODE_MODIFY . . TREL . . . 5-783 IX-15 GMR-01 . . . . T3111 . . . . . . . . 2-445 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-483 . . . . . . . . . . . . . . . . . . . . .Technical Description BSS Command Reference stat_mode . T22_TIMER . . . . . . . . . . . . . . . . . . . . T_HAND_RQD . . . . . 5-774 . . . threshold. . . . . . . . . . . trans_capability . . . . . Index sync_loss_daily . 6-202 . . . . . . 2-457 . . . . . . . . . . . . . . . . . . . . . . . . 5-757 sync_loss_oos . . . . . . 6-211 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-205 . . . . trace_msgs_before_ho . . . . . . . . . . . . . trace_connection . . . . trace call_trace_options . . . . . . . . . . . . . . 2-466 sysgen_mode off . . . . . . . . . 6-196 . . . . 1-26 SYSGEN ON mode . . . . . . . 5-724 . . . . . . . . . . . . . t_avg_w . . . . . 7-80 . . . . T5_TIMER . . . . . . . . . . . . . . . . . . . . . . . . . 6-194 . . . . . . . . . 6-209 . . . . . Statistical applications Counter statistics. . . . . 6-200 . . . . . . . . . . . . . . . . . 6-161 . . . . . 6-206 . . 6-173 . . swap_devices . 2-472 . . . . . . . . . . . . . T23_TIMER . . . . . . . 5-766 tch_flow_control . . T4 (CCITT) . . . . . . 6-180 . 6-187 . . . . . . . . . . 4-3 4-3 4-3 4-3 . 6-190 . . . . . . . . . . . trx_pwr_red . 6-37 . . . . . 2-486 . . . . . . . . . . . . T3103 . . . . . . . . . . . . . . 6-191 . . . . . . . . . . . . . . . switch_gprs_pdchs . . . tch_busy_critical_threshold . . sw_ts_less_one_carrier . . . . . . . . . . . . . . . . . . . . Statistics about . 5-765 . . . . . . . . T3. . . . . . . . . . . . . . TM_SAACH_INFO . . . . . . . T4_TIMER . . . . . . . . . . . 5-761 synchronized . . . . . . . . . . . . . . . . status_mode . . tru_id . time_stamp . . . . . . . . . . t391 . . . . . tlli_blk_coding . . . . . . . . . . . . . . tcu_port . . . . . . . . . . . . . . . . . . . . . 5-762 . . . . . . . . . . ts_alloc_flag . . 6-175 . . . . . . . . . . . . . . . . . . . . 1-26 sysgen_mode. store_cal_data . . . . . . . . 5-769 . . . 5-777 . . . . . THRES_PC_RLF . . . 6-1 . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-760 sync_time_restore . . . . . static_sync_timer. . 1-27 System Change Control (Configuration Management) about . 1-10 . . 4-28 . . . . . . . . . . . . . 5-749 . trunk_major_threshold . . . . . . . 5-776 . . . . . T3212 . . . . . T3101 . . . . . . . T2_TIMER . . . . 5-103 . 6-189 . . transcoding_capability . . . . TM_CHANNEL_ACT . . . t392 . . . . . . temporary_offset . . . . . . 1-3 . . . . . . . . . . . . . Tqho . . . . . . . . 6-193 . . . . . 6-163 6-165. . . . 7-86 . . . . . . . . . 5-759 sync_time_oos . . . state . . . . . . . . . . . . . . . . . . . . . . . . . T13_TIMER . . . . . . . . . . . . . 5-751 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . zone_pingpong_preferred_zone . . . . . . . use_neighbor_pbgt_hreqave. . . . . . . . . . 5-789 Type A commands and parameters. unconfigure_csfp . . . . . 5-212 Z zone_ho_hyst . uplink_sync_timer . . . . . . . 5-822 zone_pingpong_disable_win . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-816 5-817 X XBL lapd_k. . . . . . . . . . . . . . . unequip . . . . . . . . . 5-329 . . . . . . . u_rxlev_ul_p . . . . 5-820 zone_pingpong_count . . . . . . . . . . 5-808 . . . . . . . . . . . . u_rxqual_dl_p . . . . 5-810 . . . . . . . . . . . . . 5-814 window_size . . . . . tsc_update_method . . . TX_INTEGER . . . . . 5-791 5-793 5-794 5-795 5-797 5-798 5-799 5-800 5-801 5-802 5-803 5-804 . . . . . . . . . 5-806 . . . u_rxlev_dl_p . U_RXLEV_DL_P . . . . . . . . . . . . . . . . 5-823 IX-16 GMR-01 zone_pingpong_enable_win . . . . . . . . . . . . . . . . . . . . . . U_RXLEV_UL_P . . 5-812 . . . . . . . . . . . . . . . . . . 5-784 5-785 5-787 5-788 tx_power_cap . . . u_rxqual_ul_p_amr_hr . . . . . . . . . . . . . . . . . . unalias. . . 1-6 Type B commands and parameters . . . . . . . . . . . . . . . . . . . . . 5-824 5-825 68P02901W23-P 23 Feb 2004 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ul_rxqual_ho_allowed . 2-489 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-16 valid_candidate_period . . . . . . . 2-501 . . . . . . . ul_audio_lev_offset. . . u_rxqual_dl_p_amr_hr u_rxqual_ul_p . . . 6-212 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . U_RXQUAL_UL_P . . . . . . . . . . . . . . . . . . . . . 2-491 . . . . . . . . . . . . 2-143 5-819 W wait_for_reselection . . . . 5-385. . . . . . . . . . . . . . . . u_rxlev_ul_h . . . . . 5-805 . . . . . . . . use_derived_ho_power . . . . . . . . . . . tx_integer . 7-49 XBL (contd. . . .) lapd_t200_timer . . unequipped_circuit_allowed. . . . . . ul_rxlev_ho_allowed . . . . . . wait_indication_parameters . . U_RXQUAL_DL_P . . . . . . . . . . . . 6-214 volume_control_type . . . . . . UMTS UTRAN Cell ID. . . . . . . . . . . . . . . . . 7-51 xcdr_d_vad_dtx . . . . . . . . . . . . . worse_neighbor_ho. . . . . . . . . . . 1-6 U u_rxlev_dl_ih . unlock_device . . . . . .Index ts_in_usf_active . . . . . . . . . . . . . . . . . . . . 5-813 V valid card slots . . . . . . 7-47 lapd_n200 . . . . . . . . . . . . 3-10 . .