0% found this document useful (0 votes)

533 views2,054 pages

Motorola Bss Command Reference

Motorola Commands

Uploaded by

Sipho M Kgama

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as PDF, TXT or read online on Scribd

0% found this document useful (0 votes)

533 views2,054 pages

Motorola Bss Command Reference

Motorola Commands

Uploaded by

Sipho M Kgama

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as PDF, TXT or read online on Scribd

You are on page 1/ 2054

BSS Command Reference

Technical Description

GSR9
68P02901W23-S

2009 Motorola, Inc. All Rights Reserved.

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

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

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

Nov 2009

Table of Contents

Contents

Technical Description: BSS Command Reference

Revision history . . . . . . . . . . General information . . . . . . . . Contacting Motorola . . . . . . . . Security advice. . . . . . . . . . . Warnings, cautions, and notes . . . Safety . . . . . . . . . . . . . . . CMM labeling and disclosure table Caring for the environment . . . . Motorola document set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 4 6 7 8 9 10 11 13

Chapter 1: Introduction to commands

Version updates due to this software release. . GSR9 new/modified parameters user reference BSS MMI functions . . . . . . . . . . . . . . BSS task-oriented command usage. . . . . . . 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 . . . . . . . . . . . . . . . . . . . . form . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2 1-10 1-15 1-18 1-22 1-23 1-24 1-25 1-26 1-28 1-37 1-40 1-43

Chapter 2: Equipping the CM database

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

Chapter 3: Device/function related commands

Command reference presentation Device-related commands . . . . Device identifiers . . . . . . . . Function related commands . . . Function identifiers . . . . . . . Slots . . . . . . . . . . . . . . . 68P02901W23-S Nov 2009 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2 3-3 3-9 3-15 3-16 3-17 i

Chapter 5: Statistics commands

Statistical operations and information chg_stat_prop . . . . . . . . . . . . disp_enable_stat . . . . . . . . . . . disp_interval . . . . . . . . . . . . . disp_stat_prop . . . . . . . . . . . . disp_stats . . . . . . . . . . . . . . stat_mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2 5-5 5-12 5-22 5-24 5-34 5-48

Chapter 6: CM database parameters

CM database parameters presentation. _bss_data,2. . . . . . . . . . . . . . . _cell_data,20 . . . . . . . . . . . . . . _site_data, 5 . . . . . . . . . . . . . . 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. . . . . . . . . allow_8k_trau . . . . . . . . . . . . . alt_qual_proc. . . . . . . . . . . . . . amr_bss_half_rate_enabled. . . . . . . amr_bss_full_rate_enabled . . . . . . . amr_dl_la_mode_chg_min . . . . . . . amr_dl_thresh_adjust . . . . . . . . . amr_fr_dl_la_enabled. . . . . . . . . . amr_fr_ul_la_enabled. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2 6-5 6-6 6-8 6-9 6-10 6-11 6-12 6-13 6-15 6-16 6-17 6-18 6-19 6-20 6-21 6-22 6-23 6-24 6-26 6-30 6-31 6-32 6-33 6-34 6-35

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Contents

amr_full_rate_enabled . . . amr_half_rate_enabled . . . amr_hr_dl_la_enabled . . . amr_hr_ul_la_enabled . . . amr_ms_high_cmr . . . . . amr_ms_high_rxqual . . . . amr_ms_low_cmr. . . . . . amr_ms_low_rxqual . . . . amr_ms_monitor_period . . arp_bg_1 . . . . . . . . . . arp_bg_2 . . . . . . . . . . arp_bg_3 . . . . . . . . . . arp_i_be_1 . . . . . . . . . arp_i_be_2 . . . . . . . . . arp_i_be_3 . . . . . . . . . arp_streaming_1 . . . . . . arp_streaming_2 . . . . . . arp_streaming_3 . . . . . . asym_edge_enabled . . . . attach_detach . . . . . . . auto_rf_loss_trace . . . . . ba_alloc_proc . . . . . . . band_preference . . . . . . band_preference_mode . . base_ip_address . . . . . . ber_loss_daily . . . . . . . ber_loss_hourly . . . . . . blind_search_preference . . 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 . . . . . . . . . . . . bsp_overload_protection . . bss_egsm_alm_allowed . . . bss_msc_overload_allowed . bssgp_block_retries . . . . bssgp_cbl_bit. . . . . . . . bssgp_dwnld_retry . . . . . bssgp_pfc_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 . . . .

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

6-36 6-38 6-40 6-41 6-42 6-43 6-44 6-45 6-46 6-47 6-49 6-51 6-53 6-55 6-57 6-59 6-61 6-63 6-65 6-66 6-68 6-70 6-72 6-74 6-77 6-79 6-80 6-81 6-82 6-83 6-85 6-87 6-88 6-89 6-90 6-91 6-93 6-96 6-97 6-98 6-99 6-100 6-102 6-103 6-105 6-106 6-107 6-108 6-110 6-112 6-114 6-118 6-120 6-122 6-124 6-125 6-126 6-127

68P02901W23-S Nov 2009

xiii

Contents

surround_cell . . . . . . . . . sw_pdtch_priority . . . . . . . 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 . tch_usage_threshold . . . . . . tdd_qoffset . . . . . . . . . . . td_enabled . . . . . . . . . . . tdm_switch. . . . . . . . . . . tdm_ts_blocks . . . . . . . . . temporary_offset . . . . . . . . thp_be_weight . . . . . . . . . thp_bg_weight . . . . . . . . . thp_i2_weight . . . . . . . . . thp_i3_weight . . . . . . . . . thp_stream_weight . . . . . . . threshold. . . . . . . . . . . . timing_advance_period. . . . . tlli_blk_coding . . . . . . . . . trace_msgs_after_ho . . . . . . trace_msgs_before_ho . . . . . 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_hr . . . . . . . . u_rxqual_ul_p . . . . . . . . . u_rxqual_ul_p_hr . . . . . . . . ul_audio_lev_offset . . . . . . . ul_rxlev_ho_allowed . . . . . . ul_rxqual_ho_allowed . . . . . umts_band_preferred . . . . . umts_cpich_ec_no_min . . . . . umts_cpich_rscp_min . . . . . unequipped_circuit_allowed . . use_bcch_for_gprs . . . . . . . use_derived_ho_power . . . . .

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

6-827 6-829 6-830 6-832 6-833 6-835 6-836 6-837 6-838 6-839 6-840 6-841 6-842 6-844 6-845 6-846 6-847 6-849 6-850 6-851 6-852 6-853 6-854 6-855 6-857 6-858 6-859 6-860 6-861 6-862 6-863 6-865 6-866 6-867 6-868 6-869 6-870 6-872 6-873 6-875 6-877 6-879 6-881 6-883 6-885 6-887 6-889 6-891 6-893 6-895 6-896 6-898 6-900 6-901 6-902 6-903 6-905 6-906

xiv

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Contents

use_neighbor_pbgt_hreqave . . volume_control_type . . . . . . wait_for_reselection . . . . . . wait_indication_parameters . . worse_neighbor_ho . . . . . . zone_ho_hyst . . . . . . . . . . zone_pingpong_count . . . . . zone_pingpong_preferred_zone

. . . . . . . .

6-907 6-908 6-910 6-911 6-913 6-914 6-916 6-917

Chapter 7: 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 . . . bss_overload_control . . . bssgp_fc_period_c . . . . bssgp_t1_timer . . . . . . bssgp_t2_timer . . . . . . bssgp_t4_timer . . . . . . bssgp_t5_timer . . . . . . bssgp_t6_timer . . . . . . bssgp_t8_timer . . . . . . bssmap_t1 . . . . . . . . bssmap_t4 . . . . . . . . bssmap_t7 . . . . . . . . bssmap_t8 . . . . . . . . bssmap_t10 . . . . . . . bssmap_t11 . . . . . . . bssmap_t13 . . . . . . . bssmap_t19 . . . . . . . bssmap_t20 . . . . . . . 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 . . . . . delay_ul_rel_dur . . . . . downlink_sync_timer . . . dynet_retry_time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2 7-3 7-5 7-6 7-7 7-8 7-9 7-10 7-11 7-12 7-13 7-14 7-16 7-18 7-20 7-22 7-23 7-24 7-25 7-26 7-28 7-30 7-32 7-34 7-36 7-38 7-39 7-40 7-41 7-42 7-43 7-44 7-45 7-46 7-47 7-48 7-49 7-50 7-52 7-54 7-55 7-56 7-57 7-58 7-59 7-60 7-62

68P02901W23-S Nov 2009

Contents

early_classmark_delay . . . . emerg_reserved . . . . . . . ext_ho_allocation. . . . . . . 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_t4 . . . . . . . lb_int_bssmap_t13 . . . . . . 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_t2 . . . . . . . lb_int_ss7_l3_t4 . . . . . . . lb_int_ss7_l3_t5 . . . . . . . lb_int_ss7_l3_t12 . . . . . . . lb_int_ss7_l3_t13 . . . . . . . lb_int_ss7_l3_t14 . . . . . . . lb_int_ss7_l3_t17 . . . . . . . lb_int_ss7_l3_t22 . . . . . . . lb_int_ss7_l3_t23 . . . . . . . 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 . . . . . . . .

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

7-64 7-65 7-66 7-67 7-68 7-69 7-70 7-71 7-72 7-73 7-74 7-75 7-77 7-78 7-79 7-80 7-81 7-82 7-83 7-85 7-86 7-87 7-88 7-89 7-90 7-91 7-92 7-93 7-94 7-95 7-96 7-97 7-98 7-99 7-100 7-101 7-102 7-103 7-104 7-105 7-106 7-107 7-108 7-109 7-111 7-112 7-113 7-114 7-115 7-116 7-117 7-118 7-120 7-122 7-124 7-125 7-127 7-128

xvi

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

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 . . . . red_psp_audit_tmr . . . . . register_exp . . . . . . . . rf_chan_rel_ack . . . . . . rr_ny1_rep . . . . . . . . . rr_t3103 . . . . . . . . . . rr_t3101 . . . . . . . . . . rr_t3105 . . . . . . . . . . rr_t3109 . . . . . . . . . . rr_t3111_sd . . . . . . . . rr_t3111_tch . . . . . . . . rr_t3212 . . . . . . . . . . rsl_congestion_alarm_timer rtry_cand_prd . . . . . . . sacch_info . . . . . . . . . sccp_released . . . . . . . sccp_tconn_est . . . . . . . sccp_tiar . . . . . . . . . . sccp_tias . . . . . . . . . . sccp_trel . . . . . . . . . . sm_audit_response . . . . . spi . . . . . . . . . . . . . ss7_l2_t1 . . . . . . . . . . ss7_hsp_l2_t1 . . . . . . . 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_t2 . . . . . . . . . . ss7_l3_t4 . . . . . . . . . . ss7_l3_t5 . . . . . . . . . . ss7_l3_t12 . . . . . . . . . ss7_l3_t13 . . . . . . . . . ss7_l3_t14 . . . . . . . . . ss7_l3_t17 . . . . . . . . . ss7_l3_t22 . . . . . . . . . ss7_l3_t23 . . . . . . . . . ss7_slt_t1 . . . . . . . . . start_ack . . . . . . . . . . static_sync_timer. . . . . . stop_dri_tx_time . . . . . . t_stat_info . . . . . . . . . uplink_sync_timer . . . . . valid_candidate_period. . . zone_pingpong_disable_win zone_pingpong_enable_win

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

7-129 7-130 7-132 7-133 7-135 7-137 7-139 7-140 7-142 7-143 7-144 7-145 7-146 7-148 7-150 7-151 7-153 7-155 7-157 7-159 7-161 7-162 7-164 7-166 7-167 7-168 7-170 7-171 7-172 7-173 7-175 7-177 7-179 7-181 7-183 7-185 7-186 7-187 7-189 7-190 7-191 7-192 7-193 7-194 7-195 7-196 7-197 7-198 7-200 7-202 7-203 7-204 7-206 7-207 7-208 7-210 7-211 7-212

68P02901W23-S Nov 2009

xvii

Contents

Chapter 8: Device/Function parameters

Device and function database parameters antenna_select . . . . . . . . . . . . . . ber_oos_mon_period . . . . . . . . . . . ber_restore_mon_period . . . . . . . . . bsc_cbc_operator . . . . . . . . . . . . cabinet_type . . . . . . . . . . . . . . . cavity . . . . . . . . . . . . . . . . . . cbc_operator . . . . . . . . . . . . . . . cell_zone . . . . . . . . . . . . . . . . . chan_alloc_priority . . . . . . . . . . . . cic_block_thresh . . . . . . . . . . . . . clkx0 . . . . . . . . . . . . . . . . . . . clkx1 . . . . . . . . . . . . . . . . . . . clkx2 . . . . . . . . . . . . . . . . . . . combiner_address . . . . . . . . . . . . combiner_id . . . . . . . . . . . . . . . combining_type . . . . . . . . . . . . . dri_density . . . . . . . . . . . . . . . . ext_pdchs . . . . . . . . . . . . . . . . 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 . . . . . . . . . . . . . . pkt_radio_type . . . . . . . . . . . . . . pref_rtf_id . . . . . . . . . . . . . . . . rsl_rate. . . . . . . . . . . . . . . . . . rtf_ds0_count . . . . . . . . . . . . . . sd_load. . . . . . . . . . . . . . . . . . sd_priority . . . . . . . . . . . . . . . . shared_timeslots . . . . . . . . . . . . . slot . . . . . . . . . . . . . . . . . . . . start_ts . . . . . . . . . . . . . . . . . . t391 . . . . . . . . . . . . . . . . . . . t392 . . . . . . . . . . . . . . . . . . . tcu_port . . . . . . . . . . . . . . . . . presentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-2 8-6 8-8 8-10 8-12 8-13 8-17 8-18 8-19 8-21 8-22 8-24 8-26 8-28 8-30 8-31 8-32 8-34 8-36 8-38 8-40 8-42 8-44 8-46 8-48 8-50 8-51 8-52 8-53 8-55 8-57 8-59 8-60 8-62 8-63 8-65 8-66 8-67 8-69 8-70 8-71 8-72 8-73 8-74 8-76 8-79 8-80 8-81 8-83 8-85 8-86 8-87 8-88 8-89 8-90 8-91

xviii

68P02901W23-S Nov 2009

Contents

tdOpt. . . . . . . . . . transcoding_capability . tru_id . . . . . . . . . trx_pwr_red . . . . . .

. . . .

8-93 8-94 8-95 8-96

68P02901W23-S Nov 2009

xix

Contents

68P02901W23-S Nov 2009

List of Figures

Figure Figure Figure Figure

2-1: 2-2: 2-3: 2-4:

Table 5-2: Normal and weighted distribution statistic type prompts . . . . . . . . . . . . . . Table 6-1: alt_qual_proc=0 parameter values. . . . . . . . . . . . . . . . . . . . . . . . . Table 6-2: alt_qual_proc=1 parameter values. . . . . . . . . . . . . . . . . . . . . . . . . Table 6-3: Base Station Identity Code - Hexadecimal Values . . . . . . . . . . . . . . . . . . Table 6-4: Base Station Identity Code - Decimal Values . . . . . . . . . . . . . . . . . . . . Table 6-5: CTU2 values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 6-6: Cabinet antenna connector maximum output power (Watts) . . . . . . . . . . . . Table 6-7: Values for PGSM, EGSM, DCS1800 and PCS1900 M-Cellmicro sites . . . . . . . . Table 6-8: Values for DCS1800 and M-Cellaccess, sites . . . . . . . . . . . . . . . . . . . . Table 6-9: Sample output power . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 6-10: Values for barring classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 6-11: Maximum mobile power level for PGSM, EGSM and GSM850 cells . . . . . . . . Table 6-12: Maximum mobile power level for DCS1800 cells . . . . . . . . . . . . . . . . . Table 6-13: Maximum mobile power level for PCS1900 cells. . . . . . . . . . . . . . . . . . Table 6-14: Modes for gprs_network_operation_mode . . . . . . . . . . . . . . . . . . . Table 6-15: Max MS power level for PGSM and EGSM. . . . . . . . . . . . . . . . . . . . . Table 6-16: Max MS power level for DCS1800 and PCS1900 cells . . . . . . . . . . . . . . . Table 6-17: Max MS power level for class 3 mobiles . . . . . . . . . . . . . . . . . . . . . . Table 6-18: Max MS power level for PGSM and EGSM cells . . . . . . . . . . . . . . . . . . Table 6-19: Max MS power level for DCS1800 and PCS1900 cells . . . . . . . . . . . . . . . Table 6-20: Max MS level for class 3 mobiles . . . . . . . . . . . . . . . . . . . . . . . . . Table 6-21: Prompted parameters for Dual Band Cell use . . . . . . . . . . . . . . . . . . . Table 6-22: CTU2 values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 6-23: Cabinet antenna connector maximum output power (Watts) . . . . . . . . . . . . Table 6-24: Values for PGSM, EGSM, DCS1800 and PCS1900 sites . . . . . . . . . . . . . . Table 6-25: ms_max_range values for normal cells . . . . . . . . . . . . . . . . . . . . . . Table 6-26: ms_max_range values for Extended Range cells . . . . . . . . . . . . . . . . . Table 6-27: Maximum mobile power level for PGSM and EGSM cells . . . . . . . . . . . . . Table 6-28: Maximum mobile power level for DCS1800 cells . . . . . . . . . . . . . . . . . Table 6-29: Maximum mobile power level for PCS1900 cells. . . . . . . . . . . . . . . . . . Table 6-30: Bit mapping of ncc_of_plmn_allowed. . . . . . . . . . . . . . . . . . . . . . . Table 6-31: Configurations for network_control_order . . . . . . . . . . . . . . . . . . . . Table 6-32: Values for prach_tx_int representing number of frame slots . . . . . . . . . . . Table 6-33: qsearch_p attribute values below threshold. . . . . . . . . . . . . . . . . . . . Table 6-34: qsearch_p attribute values above threshold. . . . . . . . . . . . . . . . . . . . Table 6-35: Example cell configurations for rach_load_threshold . . . . . . . . . . . . . . Table 7-1: Impermissible combinations of psi1_repeat_period and bs_pbcch_blks . . . . . Table 8-1: Cabinets/Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 8-2: Permitted CAB modifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 8-3: Values for PGSM, EGSM and PCS 1900 sites . . . . . . . . . . . . . . . . . . . . Table 8-4: Values for DCS 1800 sites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 8-5: Values for PGSM and EGSM M-Cellmicro sites . . . . . . . . . . . . . . . . . . . Table 8-6: Values for DCS 1800 for M-CELL6, HorizonMacro, HorizonMacro2, Horizon2micro and Horizon2mini sites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 8-7: Values for DCS 1800 and PCS 1900 M-Cellmicro sites . . . . . . . . . . . . . . .

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

5-11 6-26 6-27 6-95 6-95 6-115 6-116 6-116 6-117 6-117 6-141 6-333 6-333 6-334 6-335 6-370 6-370 6-370 6-399 6-399 6-399 6-438 6-550 6-551 6-551 6-566 6-566 6-575 6-575 6-576 6-596 6-601 6-670 6-705 6-705 6-715 7-141 8-13 8-15 8-97 8-98 8-99 8-99 8-100

xxiv

68P02901W23-S Nov 2009

About This Manual

Technical Description: BSS Command Reference

What is covered in this manual?

This manual is a reference document containing descriptions of the Man-Machine Interface (MMI) commands and parameters used within the Motorola GSM system. This document supports the following Motorola BSS equipment: BTS4, BTS5, BTS6, BSSC, BSSC2, ExCell 4, ExCell 6, TopCell, M-Cell TM2, M-Cell6, M-Cellmicro, M-Cellcity, Horizonmicro, Horizoncompact, M-Cellaccess, Horizonmacro, Horizon II macro, Horizonmicro2, Horizoncompact2, Horizon II mini and Packet Control Unit (PCU). The BSS Command Reference manual is presented in three volumes: Volume 1: contains Chapters 1 to 5 providing descriptions of BSS Commands. Volume 2: contains Chapter 6 providing descriptions of CM parameters used with BSS Commands. Volume 3: contains Chapters 7 and 8 providing descriptions of Timer parameters and Device/Function parameters used with BSS Commands.

Each volume contains a full Contents list and an Index for the whole of the manual.

Background information
Lists of the additions, changes, and deletions to commands and parameters introduced by the particular software release version in this issue of the BSS Command Reference manual, is provided in Version updates due to this software release on page 1-2 of Volume 1. A customer reference form for recording local settings of new/modified GSR9 parameters is provided in GSR9 new/modified parameters user reference form on page 1-10 also of Volume 1.

68P02901W23-S Nov 2009

Revision history

The following sections show the revision status of this document.

Version information
The following table lists the supported versions of this manual in order of issue: Issue Q R S S Date of issue Sep 2004 Nov 2006 Apr 2008 Nov 2009 Remarks GSM Software Release 7 Half Rate GSM Software Release 8 GMR-02 GSM Software Release 9 GSM Software Release FP 1

Resolution of Service Requests

The following Service Requests are resolved in this document: Service Request 2208880 2206085 2217478 2212460 2248104 2288107 2287328 2308545 2315460 2322765 CMBP Number Remarks Amended valid range of bssgp_cbl_bit parameter. Modified the default value range in Table 62. Added text under Values for band_preference_mode parameter. Added Note to rci_error_gen_thresh parameter. Modified default value for rtf_ds0_count parameter. Amended Command Prompts Table for XBL device in Chapter 2. Updated add_neighbor command in Chapter 3. Updated the EMON commands information in Chapter 6. Updated the Values section in handover_required_reject_switch parameter. Updated max_tx_bts parameter in Chapter 6.

68P02901W23-S Nov 2009

Incorporation of Change Notices

The following Change Notices (CN) are incorporated in this document: CN Date NA CN Number NA Title NA

68P02901W23-S Nov 2009

General information

Purpose
Motorola documents are intended to instruct and assist personnel in the operation, installation, and maintenance of the Motorola equipment and ancillary devices. It is recommended that all personnel engaged in such activities be properly trained by Motorola. Motorola disclaims all liability whatsoever, implied or expressed, for any risk of damage, loss or reduction in system performance arising directly or indirectly out of the failure of the customer, or anyone acting on the customer's behalf, to abide by the instructions, system parameters, or recommendations made in this document. These documents are not intended to replace the system and equipment training offered by Motorola. They can be used to supplement and enhance the knowledge gained through such training.

NOTE
If this document was obtained when attending a Motorola training course, it is not updated or amended by Motorola. It is intended for TRAINING PURPOSES ONLY. If it was supplied under normal operational circumstances, to support a major software release, then Motorola automatically supplies corrections and posts on the Motorola customer website.

Cross references
References made to external publications are shown in italics. Other cross references, emphasized in blue text in electronic versions, are active links to the references. This document is divided into numbered chapters that are divided into sections. Sections are not numbered, but are individually named at the top of each page, and are listed in the table of contents.

68P02901W23-S Nov 2009

Text conventions

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

Input
Characters typed in at the keyboard are shown like this sentence. Items of interest within a command appear like this sentence.

Output
Messages, prompts, file listings, directories, utilities, and environmental variables that appear on the screen are shown like this sentence. Items of interest within a screen display appear like this sentence.

Special key sequences

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

68P02901W23-S Nov 2009

Contacting Motorola

Motorola appreciates feedback from the users of our documents.

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

Questions and comments

Send questions and comments regarding user documentation to the email address: [email protected].

Errors
To report a documentation error, call the CNRC (Customer Network Resolution Center) and provide the following information to enable CNRC to open an SR (Service Request): The document type The document title, part number, and revision character The page number with the error A detailed description of the error and if possible the proposed solution

68P02901W23-S Nov 2009

Security advice

Motorola systems and equipment provide security parameters that the operator configures based on their particular operating environment. Motorola recommends setting and using these parameters following industry recognized security practices. Consider protecting the confidentiality, integrity, and availability of information and assets. Assets include the ability to communicate, information about the nature of the communications, and information about the parties involved. In certain instances, Motorola makes specific recommendations regarding security practices. The implementation of these recommendations and final responsibility for the security of the system lies with the operator of the system. Contact the Customer Network Resolution Center (CNRC) for assistance. The 24hour telephone numbers are listed at https://mynetworksupport.motorola.com. Select Customer Network Resolution Center contact information, from the menu located to the left of the Login box. Alternatively if you do not have access to CNRC or the internet, contact the Local Motorola Office.

68P02901W23-S Nov 2009

Warnings, cautions, and notes

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

Warnings
Warnings precede instructions that contain potentially hazardous situations. Warnings are used to alert the reader to possible hazards that could cause loss of life or physical injury. A warning has the following format:

WARNING
Warning text and consequence for not following the instructions in the warning.

Cautions
Cautions precede instructions and are used when there is a possibility of damage to systems, software, or individual items of equipment within a system. However, this damage presents no danger to personnel. A caution has the following format:

CAUTION
Caution text and consequence for not following the instructions in the caution.

Notes
A note means that there is a possibility of an undesirable situation or provides additional information to help the reader understand a topic or concept. A note has the following format:

NOTE
Note text.

68P02901W23-S Nov 2009

Safety

General safety
The following general safety guidelines apply to Motorola equipment: The power jack and mating plug of the power cable must meet International Electrotechnical Commission (IEC) safety standards.

NOTE
Refer to Grounding Guideline for Cellular Radio Installations 68P81150E62.

Power down or unplug the equipment before servicing. Using non-Motorola parts for repair could damage the equipment or void warranty. Contact Motorola Warranty and Repair for service and repair instructions. Portions of Motorola equipment may be damaged from exposure to electrostatic discharge. Use precautions to prevent damage.

Electromagnetic energy
Relevant standards (USA and EC) applicable when working with RF equipment are:

ANSI IEEE C95.1-1991, IEEE Standard for Safety Levels with Respect to Human Exposure to Radio Frequency Electromagnetic Fields, 3 kHz to 300 GHz.
Council recommendation of 12 July 1999 on the limitation of exposure of the general public to electromagnetic fields (0 Hz to 300 GHz) (1999/519/EC) and respective national regulations.

Directive 2004/40/EC of the European Parliament and of the Council of 29 April 2004 on the minimum health and safety requirements regarding the exposure of workers to the risks arising from physical agents (electromagnetic fields) (18th individual Directive within the meaning of Article 16(1) of Directive 89/391/EEC).

68P02901W23-S Nov 2009

CMM labeling and disclosure table

The Peoples Republic of China requires that our products comply with China Management Methods (CMM) environmental regulations. (China Management Methods refers to the regulation Management Methods for Controlling Pollution by Electronic Information Products.) Two items are used to demonstrate compliance; the label and the disclosure table. The label is placed in a customer visible position on the product. Logo 1 means the product contains no substances in excess of the maximum concentration value for materials identified in the China Management Methods regulation. Logo 2 means that the product may contain substances in excess of the maximum concentration value for materials identified in the China Management Methods regulation, and has an Environmental Friendly Use Period (EFUP) in years. The example shown uses 50 years.

Logo 1

Logo 2

The Environmental Friendly Use Period (EFUP) is the period (in years) during which the Toxic and Hazardous Substances (T&HS) contained in the Electronic Information Product (EIP) will not leak or mutate causing environmental pollution or bodily injury from the use of the EIP . The EFUP indicated by the Logo 2 label applies to a product and all its parts. Certain field-replaceable parts, such as battery modules, can have a different EFUP and are marked separately. The Disclosure table is intended only to communicate compliance with China requirements. It is not intended to communicate compliance with EU RoHS or any other environmental requirements.

68P02901W23-S Nov 2009

Caring for the environment

The following information describes national or regional requirements for the disposal of Motorola supplied equipment and for the approved disposal of surplus packaging. Contact the Customer Network Resolution Center (CNRC) for assistance. The 24hour telephone numbers are listed at https://mynetworksupport.motorola.com. Select Customer Network Resolution Center contact information. Alternatively if you do not have access to CNRC or the internet, contact the Local Motorola Office.

EU countries
The following information is provided to enable regulatory compliance with the European Union (EU) directives and any amendments to these directives when using Motorola equipment in EU countries.

Disposal of Motorola equipment

European Union (EU) Directive 2002/96/EC Waste Electrical and Electronic Equipment (WEEE)
Do not dispose of Motorola equipment in landfill sites. In the EU, Motorola in conjunction with a recycling partner ensures that equipment is collected and recycled according to the requirements of EU environmental law.

Disposal of surplus packaging

European Parliament and Council Directive 94/62/EC Packaging and Packaging Waste
Do not dispose of surplus packaging in landfill sites. In the EU, it is the individual recipients responsibility to ensure that packaging materials are collected and recycled according to the requirements of EU environmental law.

Non-EU countries
In non-EU countries, dispose of Motorola equipment and all surplus packaging in accordance with national and regional regulations.

68P02901W23-S Nov 2009

Non-EU countries

Turkey
Article 7 of the European Union (EU) Directive 2002/96/EC Waste Electrical and Electronic

Equipment (WEEE)
The Government of Turkey requests a statement of conformity with the EEE regulation be provided with all electrical and electronic equipment. This statement of EEE conformity (in Turkish) is: EEE Ynetmeliine Uygundur.

68P02901W23-S Nov 2009

Motorola document set

The Motorola document sets provide the information to operate, install, and maintain the Motorola equipment.

Ordering documents and CD-ROMs

With internet access available, to view, download, or order documents (original or revised), visit the Motorola Lifecycles Customer web page at https://mynetworksupport.motorola.com, or contact your Motorola account representative. Without internet access available, order hard-copy documents or CD-ROMs from your Motorola Local Office or Representative. If Motorola changes the content of a document after the original printing date, Motorola publishes a new version with the same part number but a different revision character.

Document banner definitions

A banner indicates that some information contained in the document is not yet approved for general customer use. A banner is oversized text on the bottom of the page, for example, PRELIMINARY UNDER DEVELOPMENT.

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

68P02901W23-S Nov 2009

Data encryption

68P02901W23-S Nov 2009

Chapter

1
Introduction to commands

This chapter provides an introduction to the Base Station System (BSS), Man Machine Interface (MMI) functions, commands, and parameters including SYSGEN modes of operation. The following topics are contained in this chapter: Version updates due to this software release on page 1-2: lists the commands and parameters that are created, changed, and deleted by this software release. GSR9 new/modified parameters user reference form on page 1-10: provides a customer reference form for recording local settings of GSR9 parameters. BSS MMI functions on page 1-15: provides an overview of BSS MMI functions for managing the network. BSS task-oriented command usage on page 1-18: lists the MMI commands for performing BSS function related tasks. Command/database parameter security levels on page 1-22: describes the command/database access security levels. Command/database parameter types on page 1-23: describes the command/database parameter classification. Commands to be used with caution on page 1-24: lists commands that cause a device to cycle and must be used with caution. Parameters to be used with caution on page 1-25: lists parameters that cause a device to cycle and must be used with caution. Entering MMI commands on page 1-26: provides guidelines on entering MMI commands and use of the correct syntax. MMI command availability on page 1-28: lists MMI command availability by location and by SYSGEN mode. GSM cell ID format on page 1-37: describes the two types of GSM cell ID format. Indices on page 1-40: describes the indices for devices, including data array location, bin numbers, alarm thresholds, and EAS alarm table. SYSGEN mode on page 1-43: describes the SYSGEN modes of working.

68P02901W23-S Nov 2009

1-1

Version updates due to this software release

Chapter 1: Introduction to commands

Version updates due to this software release

MMI commands and parameters that are new, modified, deleted, or renamed as a result of the introduction of software release GSR 9, are listed separately. For information about the features included in this software release, refer to Motorola manual System Information: GSM Overview (68P02901W01).

New, modified and deleted commands

Table 1-1
Feature {27508}

Commands status
Command chg_cmd_level on page 3-94 chg_level on page 3-142 Login on page 3-438 Logout on page 3-441 Status New New New New Modified Modified Modified Modified Modified Modified Modified Modified Modified Modified Modified Modified Modified Modified Modified Modified Modified Modified Modified Continued

{27955A}

add_nsvc on page 3-48 alarm_mode on page 3-52 assess on page 3-54 cage_audit on page 3-58 chg_audit_sched on page 3-76 chg_element on page 3-106 del_act_alarm on page 3-190 del_nsvc on page 3-202 device_audit on page 3-210 disp_bss on page 3-229 disp_element on page 3-272 disp_equipment on page 3-283 disp_mms_ts_usage on page 3-330 disp_nsvc on page 3-353 disp_processor on page 3-367 disp_traffic on page 3-394 equip on page 3-403 ins_device on page 3-423 lock_device on page 3-429

1-2

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

New, modified and deleted commands

Table 1-1
Feature {27955A}

Commands status (Continued)

Command mod_nsvc on page 3-445 modify_value on page 3-456 query_audits on page 3-472 reset_device on page 3-485 reset_site on page 3-492 site_audit on page 3-507 soft_reset on page 3-511 state on page 3-515 status_mode on page 3-530 unequip on page 3-570 unlock_device on page 3-581 Status Modified Modified Modified Modified Modified Modified Modified Modified Modified Modified Modified Modified Modified Modified Modified Modified Modified Modified Modified Modified Modified Modified

{22168}

ins_device on page 3-423 reset_device on page 3-485

{22169}

add_conn on page 3-33 del_conn on page 3-195 mod_conn on page 3-442

{22266}

chg_stat_prop on page 5-5 disp_enable_stat on page 5-12 disp_stat_prop on page 5-24 disp_stats on page 5-34 stat_mode on page 5-48

{25423}

disp_version on page 3-399 disp_options on page 3-356

{25424}

chg_csfp on page 3-95 disp_csfp on page 3-263

Modified Modified Modified Modified Modified Modified Modified Modified Modified Modified Modified Continued

{25867}

disp_stat_prop on page 5-24 stat_mode on page 5-48

{26481}

disp_equipment on page 3-283 equip on page 3-403 modify_value on page 3-456 unequip on page 3-570

{26811} {27236}

copy_cell on page 3-179 diagnose_device on page 3-217 disp_cal_data on page 3-233

68P02901W23-S

1-3 Nov 2009

New, modified and deleted commands

Chapter 1: Introduction to commands

Table 1-1
Feature

Commands status (Continued)

Command equip on page 3-403 Status Modified Modified Modified Modified Modified Modified Modified Modified Modified Modified Modified Modified Modified Modified Modified Modified Modified Modified Modified Modified Modified Modified Modified Modified Modified Modified Modified Modified Modified Modified Modified Modified Modified Modified Continued

{27703A}

chg_element on page 3-106 stat_mode on page 5-48 disp_options on page 3-356 disp_rtf_channel on page 3-375

{28351}

disp_equipment on page 3-283 disp_processor on page 3-367 equip on page 3-403 lock_device on page 3-429 modify_value on page 3-456 state on page 3-515 disp_stats on page 5-34 stat_mode on page 5-48

{30828} {23306}

disp_options on page 3-356 chg_element on page 3-106 disp_element on page 3-272

{25002}

cage_audit on page 3-58 chg_audit_sched on page 3-76 chg_element on page 3-106 device_audit on page 3-210 query_audits on page 3-472

{26740}

chg_audit_sched on page 3-76 chg_element on page 3-106 device_audit on page 3-210 disp_element on page 3-272 disp_equipment on page 3-283 disp_traffic on page 3-394 equip on page 3-403 ins_device on page 3-423 unequip on page 3-570 unlock_device on page 3-581

{27508}

disp_mms_ts_usage on page 3-330 chg_element on page 3-106 chg_level on page 3-142

1-4

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

New, modified and deleted commands

Table 1-1
Feature {28000}

Commands status (Continued)

Command chg_element on page 3-106 disp_element on page 3-272 Status Modified Modified Modified Modified Modified Modified Modified Modified Modified Modified Modified Modified Modified Modified Modified Modified Modified Modified Modified Modified Modified Modified Modified Modified Modified Modified Modified Modified Modified Modified Modified Modified Modified Modified Continued

` {28000} {28337}

equip on page 3-403 chg_element on page 3-106 chg_stat_prop on page 5-5 disp_element on page 3-272 disp_enable_stat on page 5-12 disp_equipment on page 3-283 disp_hdlc on page 3-317 disp_mms_ts_usage on page 3-330 disp_stat_prop on page 5-24 disp_stats on page 5-34 equip on page 3-403 modify_value on page 3-456 reassign on page 3-477 stat_mode on page 5-48

{31400}

add_neighbor on page 3-35 chg_element on page 3-106 disp_element on page 3-272 disp_neighbor on page 3-343 disp_options on page 3-356 modify_neighbor on page 3-447

{32340}

chg_element on page 3-106 disp_element on page 3-272

{33863}

chg_stat_prop on page 5-5 disp_enable_stat on page 5-12 stat_mode on page 5-48

{23292}

chg_element on page 3-106 disp_stat_prop on page 5-24 disp_stats on page 5-34 stat_mode on page 5-48

{26881}

chg_cell_element on page 3-84 chg_element on page 3-106 chg_stat_prop on page 5-5

68P02901W23-S

1-5 Nov 2009

New, modified and deleted commands

Chapter 1: Introduction to commands

Table 1-1
Feature

Commands status (Continued)

Command disp_cell on page 3-241 disp_element on page 3-272 Status Modified Modified Modified Modified Modified Modified Modified Modified Modified Modified Modified Modified Modified Modified Modified Modified Modified Modified Modified Modified Modified Modified Modified Modified Modified Modified Modified Modified Modified Modified Modified Modified Modified Modified Continued

{26881}

disp_options on page 3-356 disp_stat_prop on page 5-24

{31565}

chg_cell_element on page 3-84 chg_element on page 3-106 chg_stat_prop on page 5-5 disp_element on page 3-272 disp_enable_stat on page 5-12 disp_stats on page 5-34 disp_stat_prop on page 5-24 stat_mode on page 5-48

{33397}

chg_stat_prop on page 5-5 disp_enable_stat on page 5-12 disp_stats on page 5-34 disp_stat_prop on page 5-24 stat_mode on page 5-48

{34144} {34145} {29693A}

disp_cell_status on page 3-247 disp_equipment on page 3-283 chg_element on page 3-106 disp_element on page 3-272

{33780}

chg_stat_prop on page 5-5 disp_enable_stat on page 5-12 stat_mode on page 5-48

{34164}

chg_cell_element on page 3-84 chg_element on page 3-106 disp_element on page 3-272

{33812} {34320G}

add_neighbor on page 3-35 chg_element on page 3-106 disp_element on page 3-272 disp_options on page 3-356

{34303}

chg_element on page 3-106 disp_element on page 3-272

{28938}

disp_options on page 3-356

1-6

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

New, modified and deleted commands

Table 1-1
Feature {23311A}

Commands status (Continued)

Command chg_cell_element on page 3-84 chg_element on page 3-106 chg_hop_params on page 3-128 disp_cell_status on page 3-247 disp_equipment on page 3-283 disp_options on page 3-356 disp_rtf_channel on page 3-375 equip on page 3-403 modify_value on page 3-456 unequip on page 3-570 Status Modified Modified Modified Modified Modified Modified Modified Modified Modified Modified

68P02901W23-S

1-7 Nov 2009

New, modified and deleted database parameters

Chapter 1: Introduction to commands

New, modified and deleted database parameters

Table 1-2
Feature {27717} {27703A}

Database parameters status

Parameter bssgp_t4_timer on page 7-20 arp_bg_1 on page 6-47 arp_bg_2 on page 6-49 arp_bg_3 on page 6-51 arp_i_be_1 on page 6-53 arp_i_be_2 on page 6-55 arp_i_be_3 on page 6-57 arp_streaming_1 on page 6-59 arp_streaming_2 on page 6-61 arp_streaming_3 on page 6-63 mtbr_downgrade_enabled on page 6-589 Status New New New New New New New New New New New New New New New New Modified New New New New New New New New New New New New New New Continued

{27703A}

pfm_sig_enabled on page 6-646 qos_mbr_enabled on page 6-688 streaming_enabled on page 6-826 sgsn_release on page 6-803 thp_stream_weight on page 6-861

{26481} {28000}

cabinet_type on page 8-13 prp_fanout_mode on page 6-678 prpThptOpt on page 6-679

{28337} {28938} {28351} {26740}

ss7_hsp_l2_t1 on page 7-177 IncellOpt on page 6-428 base_ip_address on page 6-77 eth_rx_errors_threshold on page 6-279 eth_tx_errors_threshold on page 6-280 dsp_error_clr_thresh on page 6-239 dsp_error_gen_thresh on page 6-241 dsp_error_inc on page 6-242 psi_trau_fill_frames_threshold on page 6-681

{26740} {30830}

tdm_ts_blocks on page 6-854 asym_edge_enabled on page 6-65 ctu2d_asym_opt on page 6-178

1-8

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

New, modified and deleted database parameters

Table 1-2
Feature {32340} {30828} {27508} {30340}

Database parameters status (Continued)

Parameter cell_barred_delay on page 6-147 ctu2d_cap_opt on page 6-179 fieldeng_always _enabled on page 6-296 stp_pc on page 6-823 stp_pc_enabled on page 6-824 Status New New New New New New New New New New New New Modified Modified New New New New New New New New

{31400}

tdOpt on page 8-93 tdd_qoffset on page 6-851 td_enabled on page 6-852

{25002} {26881}

tdm_switch on page 6-853 ext_ul_dur on page 6-283 ext_utbf_nodata on page 6-284 extuplinkOpt on page 6-288 ddtr_ctrl_enabled on page 6-186

{26881} {31565} {29693A} {34320G}

gprs_bs_cv_max on page 6-311 _cell_data,20 on page 6-6 fer_meas_period on page 6-295 power_save_enable on page 6-665 Pw_Save_SwitchOpt on page 6-682

{34303} {23306} {23311A}

_site_data, 5 on page 6-8 bsp_overload_protection on page 6-96 ercgprsOpt on page 6-277 ext_pdchs on page 8-36

68P02901W23-S

1-9 Nov 2009

GSR9 new/modified parameters user reference form

Chapter 1: Introduction to commands

GSR9 new/modified parameters user reference form

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

Required editing software

Adobe Reader 7.0 is required to enter data on this form electronically. Adobe Reader 7.0 can be installed from the CD-ROM for this manual or downloaded for free from http://www.adobe.com.

Using the form

To use this form, enter customer values for the GSR9 new/modified parameters in the Local Setting column either by: Printing the form and entering the local value of the parameter manually, or, Clicking in the appropriate cell in the Local Setting column and typing the local value for the parameter. Then printing the completed form for further use (see NOTE).

NOTE
Adobe Reader 7.0 does not allow completed/amended forms to be printed. To print the completed/amended form requires the full Adobe Acrobat 7.0 Professional.

Storing an image of the completed form

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

1-10

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

GSR9 new/modified parameters reference form

Parameter bssgp_t4_timer Status New Feature Support of RESUME at Intra-BSC level {27717} Software support for High Bandwidth {27955A} BSC Signaling Link Set Capacity and Flexibility Enhancement {28337} GSR9 QoS {27703A} GSR9 QoS {27703A} GSR9 QoS {27703A} GSR9 QoS {27703A} GSR9 QoS {27703A} GSR9 QoS {27703A} GSR9 QoS {27703A} GSR9 QoS {27703A} GSR9 QoS {27703A} GSR9 QoS {27703A} GSR9 QoS {27703A} Valid range 100 to 10000 Default value 800 Local value

pcu_n

New

pcu or pcu_0

pcu

ss7_hsp_l2_t1

New

25000 to 350000

300000

arp_bg_1

New

4 to 123

93 (pci - 1, priority level 7, pvi - 1) 97 (pci - 1, priority level 8, pvi - 1) 101 (pci - 1, priority level - 9, pvi - 1) 49 (pci=0, priority level=12, pvi=1) 53 (pci=0, priority level=13, pvi=1) 73 (pci=1, priority level=2, pvi=1) 49 (pci=0, priority level=12, pvi=1) 53 (pci=0, priority level=13, pvi=1) 77 (pci- 1, priority level 3, pvi - 1) 1 0

arp_bg_2

New

4 to 123

arp_bg_3

New

4 to 123

arp_i_be_1

New

4 to 123

arp_i_be_2

New

4 to 123

arp_i_be_3

New

4 to 123

arp_streaming_1

New

4 to 123

arp_streaming_2

New

4 to 123

arp_streaming_3

New

4 to 123

pfm_sig_enabled qos_mbr_enabled

New New

0 or 1 0 or 1

Continued

68P02901W23-S

1-11 Nov 2009

GSR9 new/modified parameters reference form

Chapter 1: Introduction to commands

Parameter sgsn_release stream_downgrade _enabled streaming_enabled thp_stream_weight prpThptOpt

Status Modified New New New New

Feature GSR9 QoS {27703A} GSR9 QoS {27703A} GSR9 QoS {27703A} GSR9 QoS {27703A} Increase throughput of PRP {28000} Support of InCell as an Optional Feature {28938} Support for Horizon II Micro cabinet identifier {26481} GSR9 QoS {27703A} Increase throughput of PRP {28000} Addition of new BSC/PCU hardware to increase GPRS capacity {28351} High Bandwidth inter-connection between BSC and PCU {26740} High Bandwidth inter-connection between BSC and PCU {26740} High Bandwidth inter-connection between BSC and PCU {26740} High Bandwidth inter-connection between BSC and PCU {26740}

Valid range 0 to 2 0 or 1 0 or 1 10 to 40 0 to 1

Default value 0 1 0 40 N/A

Local value

IncellOpt

New

0 to 1

N/A

cabinet_type

New

0 to 29

N/A

mtbr_downgrade _enable prp_fanout_mode

New New

0 or 1 1 or 2

1 1

base_ip_address

New

1.0.0.1 (minimum) 223.255.255.231 (maximum) 0 to 100

10.0.0.1

eth_rx_errors _threshold

New

eth_tx_errors _threshold

New

0 to 100

dsp_error_clr_thresh

New

0 to 253

dsp_error_gen_thresh New

2 to 255

Continued

1-12

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

GSR9 new/modified parameters reference form

Parameter dsp_error_inc

Status New

Feature High Bandwidth inter-connection between BSC and PCU {26740}

Valid range 0 to 255

Default value 0 (ECERM feature restricted) 1 (ECERM feature unrestricted)

Local value

psi_trau_fill_frames _threshold

New

High Bandwidth inter-connection between BSC and PCU {26740} High Bandwidth inter-connection between BSC and PCU {26740} Asymmetric EDGE {30830} Asymmetric EDGE {30830} Cell OOS Enhancement feature {32340} CTU2-D Base on GSR9 {30828} BSS User Security Management {27508} Supports MTP routing {30340} Supports MTP routing {30340} TD-SCDMA and GSM interworking feature {31400}

0 to 100

tdm_ts_blocks

New

2 to 10

asym_edge_enabled ctu2d_asym_opt cell_barred_delay

New New New

0 or 1 0 or 1 0 to 180

0 N/A 0

ctu2d_cap_opt fieldeng_always _enabled stp_pc stp_pc_enabled tdOpt

New New

0 or 1 0 or 1

N/A 1

New New New

0 to 16383 0 or 1 0 (TD-SCDMA inter-working restricted.) 1 (TD-SCDMA inter-working unrestricted.)

0 0 N/A

tdd_qoffset

New

TD-SCDMA and GSM interworking feature {31400}

0 (TD-SCDMA inter-working OFF.) 1 (TD-SCDMA inter-working ON.)

td_enabled

New

TD-SCDMA and GSM interworking feature {31400} Continued

68P02901W23-S

1-13 Nov 2009

GSR9 new/modified parameters reference form

Chapter 1: Introduction to commands

Parameter tdm_switch

Status New

Feature TDM Availability Enhancements {25002}

Valid range 0 (Switch closed.) 1 (Switch open.) 0 or 24 - 250

Default value 0

Local value

ext_ul_dur

New

Support for Release 4 based Extended Uplink TBF mode {26881} Support for Release 4 based Extended Uplink TBF mode {26881} Support for Release 4 based Extended Uplink TBF mode {26881} Support for Release 4 based Extended Uplink TBF mode {26881} Support for Release 4 based Extended Uplink TBF mode {26881} Support a switch and additional stats for AGCH flow control {31565} Adjustable FER Bins {29693A} SW enabler PA bias switch on/off on CTU2D {34320G} SW enabler PA bias switch on/off on CTU2D {34320G} Dual Abis Aware BTS {34303} Extended Range Cell (ERC) for Data {23311A} Extended Range Cell (ERC) for Data {23311A}

ext_utbf_nodata

New

0 or 1

extuplinkOpt

New

0 or 1

ddtr_ctrl_enabled

Modified

0 or 1

gprs_bs_cv_max

Modified

0 to 15

_cell_data,20

New

0 to 2

fer_meas_period Pw_Save_SwitchOpt

New New

0 to 255 0 or 1

0 N/A

power_save_enable

New

0 or 1

_site_data, 5

New

0 Minimum 2 Maximum 0 or 1

ercgprsOpt

New

N/A

ext_pdchs

New

0 to 4

1-14

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

BSS MMI functions

In the GSM system, Man-Machine Interface (MMI) commands are part of the Network Management function. The Network Management function can be subdivided into task-orientated categories. On a Base Station System (BSS), MMI commands are responsible for these activities: BSS Initialization Process (IP). Security management, such as controlling system access. Maintenance or Fault Management (FM). System change control or Configuration Management (CM). Call Processing maintenance. Central statistics processing. Miscellaneous.

BSS Initialization Process

The Initialization Process (IP) load codes from three sources: GPROC. Operation and Maintenance Centre (OMC-R). LAN connection to a personal computer (PC).

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

Early MMI interaction

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

Security management
Passwords are required to access the system. These passwords ensure that only authorized persons have access and establish a system/command permission level commensurate with the person. If an incorrect password is entered, access to a security level is denied.

68P02901W23-S

1-15 Nov 2009

Fault Management

Chapter 1: Introduction to commands

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

Configuration Management
Configuration Management commands are used to: Configure the Base Station System. Populate the database during SYSGEN. Modify the CM database. Display information from the CM database.

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

Central statistics processing

Statistics commands are used to: Enable/Disable statistics. Display/Modify statistics for devices or cells. Modify statistics time interval for system. Monitor active (enabled) statistics for system. Report statistics data.

1-16

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Miscellaneous commands

Miscellaneous commands
Miscellaneous commands do not conveniently fit into the categories already outlined. These commands are used to: Begin/End a SYSGEN session. Reset the entire BSS. Clear database contents. Display/Modify time function (time-stamp). Display version of a software load. Perform miscellaneous procedures, such as displaying the DTE link address, ROM checksum, and so on.

68P02901W23-S

1-17 Nov 2009

BSS task-oriented command usage

Chapter 1: Introduction to commands

BSS task-oriented command usage

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

Table 1-3

Task oriented MMI commands

Task Related commands Maintenance (Fault Management) commands:

Display the administrative state of devices or functions. Modify the administrative state of devices and associated functions. Enable, modify, disable, and display alarms.

disp_processor on page 3-367, ins_device on page 3-423, unlock_device on page 3-581, alarm_mode on page 3-52, chg_eas_alarm on page 3-102, chg_throttle on page 3-156, disp_act_alarm on page 3-225, disp_throttle on page 3-386,

state on page 3-515.

lock_device on page 3-429.

assess on page 3-54, chg_severity on page 3-148, del_act_alarm on page 3-190, disp_severity on page 3-383.

System change control (Configuration Management Database) commands: Configure the BSS. add_cell on page 3-22, add_neighbor on page 3-35, add_rtf_path on page 3-50, configure_csfp on page 3-175, reassign on page 3-477, set_full_power on page 3-496, soft_reset on page 3-511, chg_a5_alg_pr on page 3-73, chg_audit_sched on page 3-76, chg_cell_id on page 3-90, chg_dte on page 3-98, chg_hop_params on page 3-128, chg_rtf_freq on page 3-144, chg_x25config on page 3-166, copy_path on page 3-187, add_cell on page 3-22, add_nsvc on page 3-48, cell_name on page 3-62, equip on page 3-403, reset_device on page 3-485, shutdown_device on page 3-502.

Modify the CM database.

chg_acs_params on page 3-65, chg_cell_element on page 3-84, chg_csfp on page 3-95, chg_element on page 3-106, chg_ksw_config on page 3-136, chg_ts_usage on page 3-161, copy_cell on page 3-179, del_cell on page 3-192,

Continued

1-18

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

BSS task-oriented command usage

Table 1-3

Task oriented MMI commands (Continued)

Task Related commands del_conn on page 3-195, del_nsvc on page 3-202, modify_value on page 3-456, unconfigure_csfp on page 3-568, del_neighbor on page 3-197, modify_neighbor on page 3-447,set_relay_contact on page 3-500, unequip on page 3-570.

Populate the database during SYSGEN ON.

All MMI commands except the following: alarm_mode, cage_audit, clear_gclk_avgs, device_audit, disp_act_alarm, disp_cal_data, disp_csfp_status, disp_gclk_cal, disp_interval, disp_processor, disp_rtf_channel, disp_trace_call, enable_alarm, ins_device, query_audits, reset_device, set_relay_contact, site_audit, status_mode, swap_devices, trace_stop, assess, clear_cal_data, del_act_alarm, diagnose_device disp_bss, disp_cell_status, disp_gclk_avgs, disp_hdlc, disp_link_usage, disp_relay_contact, disp_stats, disp_version, gclk_cal_mode, lock_device, reattempt_pl, set_full_power, shutdown_device, state, store_cal_data, trace_call, unlock_devices. disp_a5_alg_pr on page 3-221, disp_bss on page 3-229, disp_cell_map on page 3-244, disp_conn on page 3-261, disp_csfp_status on page 3-267, disp_equipment on page 3-283, disp_gsm_cells on page 3-314, disp_hopping on page 3-320, disp_link_usage on page 3-328, disp_neighbor on page 3-343, disp_options on page 3-356,

Display information from the CM database.

cage_audit on page 3-58, disp_acs on page 3-223, disp_cell on page 3-241, disp_cell_status on page 3-247, disp_csfp on page 3-263, disp_element on page 3-272, disp_exp_config on page 3-305, disp_hdlc on page 3-317, disp_link on page 3-326, disp_mms_ts_usage on page 3-330, disp_nsvc on page 3-353, disp_relay_contact on page 3-373, disp_rtf_path on page 3-381, disp_transcoding on page 3-397,

Continued

68P02901W23-S

1-19 Nov 2009

BSS task-oriented command usage

Chapter 1: Introduction to commands

Table 1-3

Task oriented MMI commands (Continued)

Task Related commands freq_types_allowed on page 3-417, site_audit on page 3-507, disp_rtf_channel on page 3-375, disp_traffic on page 3-394, disp_x25config on page 3-401, query_audits on page 3-472.

Call processing (Database) commands: Trace the progress of a specified call by random trace (by call rate). Trace the progress of a specified call by random trace (by SCCP connection number). Report call processing data. Stop an existing trace or a specified call disp_trace_call on page 3-390, trace_call on page 3-550. trace_call on page 3-550.

trace_connection on page 3-562. trace_stop on page 3-564.

Statistics (Central Statistics Processing Database) commands: Enable/disable statistics. Display/modify statistics for devices or cells. Modify statistics time interval for system. Monitor active (enabled) statistics for system. Report statistics data. stat_mode on page 5-48. chg_stat_prop on page 5-5, disp_interval on page 5-22. disp_enable_stat on page 5-12. disp_stat_prop on page 5-24. Miscellaneous commands: Begin/end a SYSGEN session (see SYSGEN mode on page 1-43). Reset the entire BSS. Clear database contents. sysgen_mode on page 3-540. disp_stats on page 5-34.

reset_site on page 3-492. clear_cal_data on page 3-169, clear_gclk_avgs on page 3-173. chg_time on page 3-158, disp_version on page 3-399. clear_database on page 3-171,

Modify/display time function (time-stamp). Display version of software load

chg_throttle on page 3-156.

Continued

1-20

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

BSS task-oriented command usage

Table 1-3

Task oriented MMI commands (Continued)

Task Related commands chg_level on page 3-142, chg_smscb_msg on page 3-150, del_smscb_msg on page 3-206, diagnose_device on page 3-217, disp_cbch_state on page 3-237, disp_flash on page 3-307, disp_gclk_cal on page 3-311, disp_site on page 3-385, page on page 3-470, status_mode on page 3-530, swap_devices on page 3-537, connection_code on page 3-177, device_audit on page 3-210, disp_cal_data on page 3-233, disp_dte on page 3-269, disp_gclk_avgs on page 3-309, disp_level on page 3-325, gclk_cal_mode on page 3-421, reattempt_pl on page 3-483, store_cal_data on page 3-534, time_stamp on page 3-548.

Perform miscellaneous tasks (display DTE link, ROM checksum, and so on).

68P02901W23-S

1-21 Nov 2009

Command/database parameter security levels

Chapter 1: Introduction to commands

Command/database parameter security levels

Four security levels are provided in the system to control command and database access. Access to each level is controlled using passwords. Each command in the system is assigned a security level. Refer to the command description for a specific command security level.

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

Level 2
This level permits access to all system commands, including the ability to change the system database. This security level also permits the operator to change passwords for both Level 1 and Level 2 users.

Level 3
This level provides all of the features accessible in security Level 2 plus the executive monitor. Two passwords are required to access security Level 3. The passwords for this level cannot be changed unless the Optional Level 3 Password Feature is purchased. This feature enhances BSS security by allowing the Level 3 passwords to be changed in the event the Level 3 passwords are compromised.

Level 4
{27508} This level provides all the features accessible in security Level 3 plus the executive monitor. Two passwords are required to access security Level 4. The passwords for this level cannot be changed unless the Optional Level 4 Password Feature is purchased.

1-22

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Command/database parameter types

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

Type A commands and parameters

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

Type B commands and parameters

The operator is required to perform one or more actions when entering a Type B command or changing a Type B database parameter. Operator actions are required before or after the command entry or database change. Specific required actions are listed in the Operator actions section of each command and database parameter description.

68P02901W23-S

1-23 Nov 2009

Commands to be used with caution

Chapter 1: Introduction to commands

Commands to be used with caution

The following commands cause a device to cycle. Before the device is cycled, a prompt is displayed and must be acknowledged. add_cell add_nsvc add_rtf_path chg_a5_alg_pr chg_cell_element (depends on parameter) chg_dte chg_element (depends on parameter) chg_level ksw_config chg_rtf_f clear_cal_datareq clear_database configure_csfp copy_cell diagnose_device disp_a5_alg_pr disp_act_alarm disp_hdsl_settings disp_severity disp_cbch_state disp_gclk_cal disp_hopping equip freq_types_allowed ins_device mod_conn mod_nsvc modify_value (depends on parameter) reset_device reset_site set_full_power shutdown_device soft_reset swap_devices sysgen_mode unconfigure_csfp unequip unlock_device

1-24

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Parameters to be used with caution

The following parameters cause a device to cycle. Before the device is cycled, a prompt is displayed and must be acknowledged. bsic bs_ag_blks_res bs_pa_mfrms cbc_fast_select ccch_conf downlink_sync_timer initial_sync_timer smg_gb_vers swfm_enable uplink_sync_timer

68P02901W23-S

1-25 Nov 2009

Entering MMI commands

Chapter 1: Introduction to commands

Entering MMI commands

Commands are entered by typing the command string followed by pressing the Return key (or its equivalent). The following conventions are used to present command strings: A character sequence that is enclosed in angle brackets <> represents a mandatory parameter. Wherein a specific variable (value or character string) replaces the string. For example:<start_time_hour> is entered as an hour between 00 and23. A character sequence in bold serif type such as example represents a mandatory parameter that must be entered as is. For example: dri A character sequence enclosed in [ ] indicates that the parameter is optional. For example: [<start_time_hour>] or [dri].

Command syntax
The following guidelines must be followed when entering MMI commands. Command names are case-sensitive and cannot be entered as mixed upper and lower case characters in a command string. Exceptions to this rule are made clear in the text. An underscore character _ must be used between command keywords, for example add_cell. A space character is used between parameters as a command separator.

Example
BSS PROMPT --> add_rtf_path 3 2 1 1

MMI Command

First Command Parameter

Space separating Command Parameter

ti-gsm-entering_00018-ai-sw

1-26

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Timeouts

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

System response
COMMAND ACCEPTED

Timeouts
If a response is not entered within 60 sec, the command or response is rejected, and the following message displays: COMMAND REJECTED: No response to prompt.

Ambiguous command response

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

Example:
MMI-RAM 0115 -> disp_rtf disp_rtf: Command ambiguous with: disp_rtf_calls disp_rtf_channel disp_rtf_path

Entering hexadecimal values

Some fields accept hexadecimal (hex) values. To specify a hex value: Lead the value with a 0 (zero). Type an h at the end of the value.

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

68P02901W23-S

1-27 Nov 2009

MMI command availability

Chapter 1: Introduction to commands

MMI command availability

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

Command availability by SYSGEN mode

Chapter 1: Introduction to commands

Table 1-4

MMI command availability by location (Continued)

MMI ROM Locations Allowed BSC X X X X X BTS X RXCDR X X X X

Command unalias unconfigure_csfp unequip unlock_device

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

Technical Description: BSS Command Reference

GSM cell ID format

Cell ids are required parameter entries for many commands. The GSM cell ID format consists of four fields: MCC - Mobile Country Code MNC - Mobile Network Code LAC - Location Area Code CI - Cell Identity

The GSM cell ID is typically displayed in the following format: 543 021 61986 (F222h) 34944 (8880h) Where: 543 021 61986 34944 is: MCC MNC LAC CI

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

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

68P02901W23-S

1-37 Nov 2009

Input format

Chapter 1: Introduction to commands

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: 5 4 3 2 1 61986 34944 is: first digit of MCC second digit of MCC third digit of MCC first digit of MNC second digit of MNC LAC CI

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

Four-element format
The system uses the four-element format when the mmi_cell_id_format parameter = 1. cell=543 021 61986 34944 Where: 5 4 3 0 2 1 61986 34944 is: first digit of MCC second digit of MCC third digit of MCC first digit MNC second digit of MNC third digit of MNC LAC CI

This format must be used if the optional third MNC digit is necessary. It can be used for PGSM, EGSM, and DCS 1800 systems. If the first and/or second digit of the MCC is a zero, it can be omitted from the input. The system recognizes both of the following examples as valid format: 001 011 98765 543211 011 98765 54321

1-38

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Cell name

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

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

68P02901W23-S

1-39 Nov 2009

Indices

Chapter 1: Introduction to commands

Indices

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

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

Table 1-6

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

For example, the command string disp_element sap_start_time,12 0 displays the audit start time for BSPs (index 12) at location 0.

1-40

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Data array location

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

Single index number

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

Two index numbers

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

Bins
A single row of a data array can be referred to as a bin. If a command uses bin numbers to specify the row in a data array, the index number specifies the position of the data element in the bin. The following represents an array with four bins with 32 elements in each bin: bin 0 [0 1 2 ... 31] bin 1 [0 1 2 ... 31] bin 2 [0 1 2 ... 31] bin 3 [0 1 2 ... 31] The following example shows the command string that is used to assign or change the value of the rxlev_ul_ho parameter. The value of the parameter is located in the first column (index = 0) of the second bin (bin_num = 1): chg_cell_element rxlev_ul_ho 2 6 2 0 2 2868 3100 1 0 8,0 The following example shows the command string that is used to display the contents of a bin. The index value used with the disp_element command is the bin number used when assigning or changing the value of one of the elements of the parameter: disp_element rxlev_dl_ho,1 0 cell_number=2 6 2 0 2 2868 3100 rxlev_dl_ho = alg_num: 1 alg_data: 8 6 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

68P02901W23-S

1-41 Nov 2009

Thresholds

Chapter 1: Introduction to commands

Thresholds
Gauge and some counter statistics can be assigned thresholds. An alarm is sent to the OMC-R when the threshold is exceeded. The severity of the alarm associated with a statistical parameter can be displayed using the disp_element command using an index value of 1. For example, the command string disp_element invalid_frames_rx,1 0 displays the severity of the alarm associated with the invalid_frames_rx statistical parameter: invalid_frames_rx = 2 Table 1-7 lists the alarm severities.

Table 1-7

Alarm Severities
Alarm Number 0 1 2 3 4 5 Severity Investigate Critical Major Minor Warning Clear

EAS alarm table

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

1-42

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

SYSGEN mode

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

SYSGEN OFF
The SYSGEN OFF mode is the normal system mode of operation. The sysgen_mode off command places the system in the SYSGEN OFF mode. If the system is in the SYSGEN ON mode and the sysgen_mode off command is entered, any changes made to the database are checked and the following displayed: *******VERIFYING DATABASE BEFORE COMPLETING SYSGEN******* Frequency hopping verification in progress. SITE 0 Verification. DB Verification passed. COMMAND ACCEPTED. After the system initializes, it is in the SYSGEN OFF mode. If the system is in the SYSGEN OFF mode and the sysgen_mode off command is entered, the command is rejected and the following message displays: COMMAND REJECTED: sysgen mode is already off

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

CAUTION
Do NOT enter the sysgen_mode on or the sysgen_mode off commands at the OMC-R. If the system is in the SYSGEN OFF mode and the sysgen_mode on command is entered, the system prompts the user to reinitialize the site: COMMAND ACCEPTED: You must re-init the site to start SYSGEN

68P02901W23-S

1-43 Nov 2009

Database changes in SYSGEN ON mode

Chapter 1: Introduction to commands

If the system is in the SYSGEN ON mode and the sysgen_mode on command is entered, the command is rejected and the following message displays: COMMAND REJECTED: sysgen mode is already on The system rejects the sysgen_mode command if it is entered at a GPROC that is not acting as the master GPROC: COMMAND REJECTED: Command only allowed at active BSP.

Database changes in SYSGEN ON mode

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

Procedure 1-1
1 2 3 4

Retain database changes made in SYSGEN ON mode

Disable downloads for network elements at the OMC-R. Enter the sysgen_mode on command at the BSC Enter the reset_site 0 command. After the system has reset, modify or enter the commands to the database as necessary.

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

1-44

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Initial SYSGEN mode

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

CAUTION
Personnel who fully understand the consequences must use the clear_database command. The system is placed in the initial SYSGEN mode by placing the system in the SYSGEN ON mode then entering the clear_database command.

Scripts
A script is a file that contains a series of commands which load the CM database into the system. A script is loaded in the initial SYSGEN mode and permits large amounts of information to be loaded efficiently onto the system. After the database is loaded using a script, the system must be returned to the SYSGEN OFF mode to verify the script contents. If errors are detected, the system does not return to the SYSGEN OFF mode. Correct the script and reload before the system returns to its normal operating state.

SYSGEN safety features

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

Safety timer
If the system is in the SYSGEN ON mode, a timer is used to ensure that a GPROC cannot be left in the SYSGEN ON mode indefinitely. The timer is started when no activity is detected from the TTY terminal. If activity is detected before the timer expires, the timer is reset to its initial value and restarted. If the timer expires, the GPROC is reset with a Global Kill SWFM. Within the SWFM, a message includes a textual description that the timer expired.

68P02901W23-S Nov 2009

1-45

SYSGEN safety features

Chapter 1: Introduction to commands

1-46

68P02901W23-S Nov 2009

Chapter

2
Equipping the CM database

This chapter provides information on equipping the CM database at a site. The following topics are in this chapter: Introduction to equipping the CM database on page 2-2: introducing the equip command, and listing prerequisites for equipping the database, restrictions on equipping a site, and equip related commands. Using the equip command on page 2-5: providing information on the format and usage of the equip command at the MMI. Equipage hierarchy on page 2-6: containing information and hierarchical charts for equipping devices and functions in different systems. Information for equipping devices on page 2-11: detailing the conditions, rules, and command prompts for each device that can be equipped in the CM database. Information for equipping functions on page 2-57: detailing the conditions, rules, and command prompts for each function that can be equipped in the CM database.

68P02901W23-S Nov 2009

2-1

Introduction to equipping the CM database

Chapter 2: Equipping the CM database

Introduction to equipping the CM database

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

Devices and functions that can be equipped

The following devices and functions can be equipped in the CM database using the equip command: Devices ABSS BTP CIC DPROC GBL GSL MTL PCU RXCDR AXCDR CAB COMB DRI GCLK KSW OML PSP SITE BSP CAGE CSFP DYNET GDS LMTL OPL PSI XBL BSS CBL DHP EAS GPROC MSI PATH RSL ETH

Functions LCF OMF RTF

Prerequisites for equipage tasks

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

2-2

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Equippage restrictions

Some devices and functions can be equipped only after other devices have been equipped. Refer to Equipage hierarchy on page 2-6 for further information. GPRS devices can be equipped only if the GPRS feature is unrestricted. The LMTL can be equipped only if the Location Services support feature is unrestricted and the BSS can support a BSS-based SMLC. To equip a device or function with a frequency, it first must be set as allowable with the freq_types_allowed command (see freq_types_allowed on page 3-417).

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

Equippage restrictions
The following restrictions apply at the BSC when equipping the CM database: A BSC of type 1 or 2 must equip remote sites with an LCF. No more than three PCUs can be equipped per BSC.

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

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

Equip related commands

The following MMI commands are related to equipping devices and functions: disp_equipment on page 3-283: Used to display equipped devices and functions. freq_types_allowed on page 3-417: Used to set the frequency types and blocks available at the BSS. lock_device on page 3-429: Used to lock a site to equip certain devices. modify_value on page 3-456: Used to modify the parameter values of an equipped device or function. reassign on page 3-477: Used to reassign a child device from its current parent function to a new parent function. shutdown_device on page 3-502: Used to shut down a device before modifying or unequipping the device.

68P02901W23-S

2-3 Nov 2009

Equip related commands

Chapter 2: Equipping the CM database

state on page 3-515: Used to display the current status of devices and functions in the system. unequip on page 3-570: Used to unequip an equipped device or function. unlock_device on page 3-581: Used to unlock a site after equipping certain devices.

2-4

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Using the equip command

Enter the equip command at the MMI. Specify the site location and the name of the particular device or function to be added to the CM database. The equip command can be entered only at the BSC. It does not work at a BTS. The system responds with a series of command prompts for further operator input. The information requested is dependent on the particular device or function being equipped. If a device or function parameter is optional, there is no need to enter data, simply press the ENTER key at the prompt. The equip command can be exited at any time by entering done in response to any prompt.

Format of equip command

The format of the equip command entered at the MMI prompt is: equip <location> <dev/func_name> Where: location is: The location of the device or function, one of: 0 or bsc 0 - 140 pcu or pcu_0 dev/funcc_name for a BSC. for a BTS. for a PCU.

The name of the device or function being equipped.

System response
The system responds with an appropriate set of prompts for the particular device or function being equipped. Enter the correct information in response to the prompts and conditions for equipping the particular device or function. The system indicates execution with COMMAND ACCEPTED message which can be accompanied with a WARNING message. If incorrect information is entered or the particular equip conditions are not met, a COMMAND REJECTED with reason message is issued. Equip conditions and system prompts are provided in: Information for equipping devices on page 2-11. Information for equipping functions on page 2-57.

68P02901W23-S

2-5 Nov 2009

Equipage hierarchy

Chapter 2: Equipping the CM database

Equipage hierarchy

Devices and functions have a hierarchical structure which can differ between systems. Some devices and functions can only be equipped after other devices have been equipped. For example, a CAGE must be equipped before a BTP can be equipped. Other devices are automatically equipped. For example, an MMS is equipped automatically when equipping an MSI. Equipage hierarchy charts in this section show the order in which devices and functions are equipped for the following systems: RXCDR InCell M-Cell and Horizonmacro GPRS

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

2-6

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

RXCDR

Figure 2-1

Remote Transcoder (RXCDR) devices and functions

NOTE
* indicates an automatically equipped device.

68P02901W23-S

2-7 Nov 2009

InCell

Chapter 2: Equipping the CM database

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

Figure 2-2

BSC and InCell BTS

BSS SITE (BSC) CAB PCU DYNET AXCDR Conn_Link CAGE

PSI KSW GCLK BSP

GPROC CSFP

EAS

MSI

ETH

LCF

OMF MMS*

RF_Unit GDS (LAPD_TR AU) GSL MTL OML GSL LMTL CBL

CIC XBL

ti-GSM-BSC Incell BTS-00015-eps-sw

NOTE
* indicates an automatically equipped device.

2-8

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

M-Cell and Horizonmacro

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

Figure 2-3

M-Cell and Horizonmacro equipage hierarchy chart

NOTE
* indicates an automatically equipped device.

68P02901W23-S

2-9 Nov 2009

GPRS

Chapter 2: Equipping the CM database

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

Figure 2-4

GPRS PCU devices and functions

BSS SITE (BSC)

PCU

CAB*

CAGE*

MPROC (PSP*)

DPROC (PICP)

DPROC (PRP)

DPROC (PXP)

PPROC* MSI (PMC) MMS* MSI (PMC) MMS* MSI (PMC) MMS*

ETH

MSI *

GDS* (LAPD_TRAU)

MMS*

GBL

GDS (LAPD) GSL

GDS (TRAU) GSL*

GBL*

ti-GSM-PCU_devices_and_functions-00017-eps-sw

NOTE
* indicates an automatically equipped device.

2-10

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Information for equipping devices

This section references conditional information for the rules on equipping various devices, and the equip command prompts that occur with each of the following devices: ABSS on page 2-11 BSS on page 2-13 CAGE on page 2-18 COMB on page 2-21 DPROC on page 2-24 AXCDR on page 2-12 BTP on page 2-14 CBL on page 2-19 CSFP on page 2-22 DRI (InCell sites) on page 2-25 EAS (InCell sites) on page 2-32 GCLK on page 2-36 GSL on page 2-38 MSI (InCell, BSC, and RXCDR sites) on page 2-40 MTL on page 2-46 PATH on page 2-48 PSP on page 2-52 SITE on page 2-54 BSP on page 2-13 CAB on page 2-15 CIC on page 2-19 DHP on page 2-23 DRI (M-Cell and Horizonmacro sites) on page 2-27 EAS (M-Cell sites) on page 2-33 GDS on page 2-37 KSW on page 2-39 MSI (M-Cell sites) on page 2-42 OML on page 2-47 PCU on page 2-51 RSL on page 2-53 XBL on page 2-55

DYNET on page 2-30 GBL on page 2-34 GPROC on page 2-38 LMTL on page 2-39 MSI (PCU only) on page 2-45 OPL on page 2-47 PSI on page 2-51 RXCDR on page 2-53

ABSS
Equip conditions
The Associated Base Station Subsystem (ABSS) can be equipped with the system in SYSGEN ON mode. This device can also be equipped when the system is outside the SYSGEN ON mode and it is to be the standby device. An ABSS device can only be equipped at an RXCDR site. The maximum number of ABBSs that can be equipped at an RXCDR site is 10. If an ABSS device is referenced in the BSS-RXCDR connectivity table, it cannot be unequipped. The BSS-RXCDR connectivity table is created using the add_conn command.

68P02901W23-S

2-11 Nov 2009

AXCDR

Chapter 2: Equipping the CM database

Command prompts
Prompt Enter the ABSS device ID: Optional N Range 1 - 254 Default None Comments This value corresponds to the BSS network entity that this device represents.

AXCDR
Equip conditions
The Associated RXCDR (AXCDR) can be equipped with the system in SYSGEN ON mode. This device also can be equipped when the system is outside the SYSGEN ON mode and it is the standby device. The AXCDR can be equipped only at a BSC that is set to remote transcoding. The maximum number of AXCDRs that can be equipped at a BSC site is 10. The AXCDR cannot be unequipped if it is referenced in the BSS-RXCDR connectivity table.

Command prompts
Prompt Enter the AXCDR device ID: Perform CIC validation?: Enable Enhanced Auto-Connect Mode: Optional N Range 1 - 254 Default None Comments This value corresponds to the RXCDR network entity that this device represents. CIC validation must be enabled to set eac_mode to 1 (enabled). The eac_mode can only be set to 1 (enabled) if the AMR Enhanced Capacity feature and/or the GSM Half Rate feature is unrestricted. A prompt for this value is presented only if the eac_mode is enabled. A prompt for this value is presented only if the eac_mode is enabled.

yes or no 0 or 1

None 0

Enter the CIC blocking threshold: Enter the CIC unblocking threshold:

0 - 245

1 - 225

2-12

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

BSP

BSP
Equip conditions
The Base Station Processor (BSP) can be equipped with the system in SYSGEN ON mode. The BSP can also be equipped when the system is outside the SYSGEN ON mode and it is to be the standby device.

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

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

Command prompts
Prompt Enter the BSS identifier: Is local transcoding performed at the BSC (yes/no): Optional N N Range 1 - 254 yes or no Default None None Comments

68P02901W23-S

2-13 Nov 2009

BTP

Chapter 2: Equipping the CM database

BTP
Equip conditions
The Base Transceiver Processor (BTP) can be equipped with the system in SYSGEN ON mode. This device also can be equipped when the system is outside the SYSGEN ON mode and it is to be the standby device. When equipping BTPs to M-Cell sites, BTP 0 must be the first BTP equipped. This device can be equipped only at a BTS site. For a bts_type of 0, no more than two radios must be equipped. For a Horizon II macro controlling cabinet, the BTP manages the auto-equip (and auto-unequip) of the MSI device 0 0 0 (with three associated MMS devices) at the BTS site. Only one BTP can be equipped at a site with a Horizon II mini master cabinet.

Command prompts
The following prompts do not display for all installations. Some devices set certain parameters automatically. The system does not prompt for values set automatically. Prompt Enter BTP identifier: Optional N Range 0 or 1 Default None Comments For M-Cell2 and M-Cell6 sites, this prompt has the following meaning: 0 = card frame 0, 1 = card frame 1. BTPs can only be GPROCs with the following Cage and Slot restrictions based on site type: BSC, BSS, and RXCDR sites: not allowed BTS sites: - cage 15, slots 20, 24, - cage 14, slot 20. If the BTS type is 0, the maximum number of DRIs cannot be 0.

Enter the cage number: Enter the slot number:

N N

14 or 15 20 or 24

None None

Enter maximum DRIs supported by this BTP:

0 - 6

None

2-14

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

CAB

CAB
Equip conditions
The Cabinet (CAB) can be equipped with the system in SYSGEN ON mode. This device also can be equipped when the system is outside the SYSGEN ON mode and it is to be the standby device. If the CAB is equipped for GPRS, the system rejects the equip CAB command. The CAB is automatically equipped when the PCU is equipped. If the frequency_type is not supported for the cab_type, the system rejects the equip CAB command. The following dependencies govern what type of cabinets can be equipped at different sites: M-Cell and transceiver cabinets cannot be equipped at site 0 (BSC). M-Cell and transceiver cabinets cannot be equipped at an InCell site. InCell cabinets cannot be equipped at an M-Cell site. Horizon II macro and Horizon II macro extension cabinets can be combined with the following at a BTS site: M-Cell6 TCU_6 Horizon macro Horizon macro extension cabinets

Command prompts
Prompt Enter the CABINET identifier: Enter the cabinet type: Optional N Range 0 - 15 Default None Comments

N 0 - 27

None M-Cell and transceiver cabinets cannot be equipped at an InCell site. InCell cabinets cannot be equipped at an M-Cell site. The system rejects the command if: The bts_type is not 0, and The cabinet_type = 10, 11, 14, 15, 16 or 20.

Enter this value either as a number or string: Continued

68P02901W23-S

2-15 Nov 2009

CAB

Chapter 2: Equipping the CM database

Prompt

Optional

Range

Default No 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 18 19 20 String bts4d_48v bts4d_27v bssc_48v bssc_27v bts_dab bssc_dab excell_4 excell_6 topcell bts_5 m_cell_2 m_cell_6 tcu_2 tcu_6 m_cellmicro m_cellcity m_cellarena

Comments Cabinet type BTS4D 48 volt BTS4D +27 volt BSSC 48 volt BSSC +27 volt BTS with DAB BSSC with DAB ExCell 4 ExCell 6 TopCell BTS 5 M-Cell 2 M-Cell 6 TCU-2 TCU-6 M-Cellmicro M-Cellcity M-Cellarena Horizonmacro master cabinet Horizonmacro extention cabinet M-Cellarena macro BTS (Horizoncompact) Horizonmicro2 BTS horizoncompact2 BTS HorizonIImacro cabinet HorizonIImacro extention cabinet HorizonII mini / HorizonII micro HorizonII mini extension / HorizonII micro extension Continued

horizonmacro horizonmacro_ext m_cell arena_macro horizon micro2 horizon compact2 horizonmacro2 horizonmacro2_ext horizon2mini/ horizon2micro horizon2mini_ext horizon2 micro_ext

22 23 24 25 26 27

2-16

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

CAB

Prompt Enter the frequency type:

Optional N

Range 1 to 15

Default

Comments

None This value can be entered by number or as a string: No 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 pgsm egsm pgsm, egsm dcs1800 pgsm, dcs1800 egsm, dcs1800 pgsm, egsm, dcs1800 pcs1900 pgsm, pcs1900 egsm, pcs1900 pgsm, egsm, pcs1900 dcs1800, pcs1900 pgsm, dcs1800, pcs1900 egsm, dcs1800, pcs1900 pgsm, egsm, dcs1800, pcs1900 String

Combinations of frequency types can also be entered: Numbers and strings can be combined in a single command. A comma must separate different frequency types, for example: pgsm, 2, 4

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

yes or no

None This prompt is only displayed if the site type is M-Cellcity or Horizonmicro.

68P02901W23-S

2-17 Nov 2009

CAGE

Chapter 2: Equipping the CM database

CAGE
Equip conditions
A Cage (CAGE) can be equipped with the system in SYSGEN ON mode. This device also can be equipped when the system is outside the SYSGEN ON mode and it is to be the standby device. The master slots are contained in cages 0 and 1 for BSS, BSC, and RXCDR sites and in cages 14 and 15 for BTS sites. For this reason, cage 0 and/or 1 for BSS, BSC, or RXCDR type sites and cage 14 and/or 15 must be equipped at BTS type sites. If the cage is equipped for GPRS, the system rejects the equip CAGE command. The cage is automatically equipped when the PCU is equipped. At M-Cell sites, the CAGE device cannot be equipped. The cage is automatically equipped when the first BTP at a site is equipped.

Command prompts
Prompt Enter the device identification for the cage: Optional N Range 0 - 15 Default None Comments The cage number (ID) must be equal to the setting on the LANX card. Valid identifiers for a BSS, BSC, or RXCDR Cage are 0 to 13. Valid identifiers for a BTS cage are 2 to 15. See NOTE.

Enter the KSW pair that manages the cage: Enter the KSWX connecting cage to KSW for TDM 0: Enter KSWX connecting cage to KSW for TDM 1: Enter the cabinet to which the cage belongs: Is an IAS connected?:

0 - 3

None

0 - 4

None

See NOTE.

0 - 4

None

See NOTE.

0 - 23

None

Chapter 2: Equipping the CM database

The parent MMS must be equipped before equipping the CIC. If the MMS on which the CIC is to be equipped does not appear in the CM Database, the equip CIC command is rejected. The equip CIC command is rejected if the CIC is not unique or if the timeslot/group is not available. The CIC can be equipped only at a BSC or RXCDR (site 0). The CIC cannot be equipped on an HDSL link.

Equipping CICs at a BSC

When equipping a CIC at a remote transcoding BSC, the RXCDR providing the TRAU for the CIC must be specified. The operator is also prompted for a static MMS timeslot to the RXCDR. However, if the BSC is operating in static mode, it is not required. In this case, the CIC is blocked. In autoconnect (non-static) mode, the static MMS is not required. If the CIC is equipped in this way and the BSC is in backwards compatibility (static) mode, the CIC is blocked. Usually, all TRAU circuits must be equipped to GDP boards when efr_enabled is set to 1 (enabled) for the BSS.

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

Equipping CICs at an RXCDR

When equipping a CIC at an RXCDR, the BSS managing the CIC must be specified. The operator also is prompted for a static MMS timeslot to the BSS. However, if the BSC is operating in static mode, it is not required. In this case, the CIC is blocked. The same CIC identifier can be equipped multiple times at an RXCDR as it can be used for multiple BSSs.

2-20

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

COMB

Command prompts
Prompt Enter the CIC(s): Optional N Range 0 - 65535 Default None Comments No more than 128 CICs can be equipped at a time (for remote transcoding). For RXCDR and local transcoder BSS, only 30 CICs can be equipped. Multiple CICs can be entered using the format: CIC# to CIC# (for example, 255 - 286). This prompt only appears for remote transcoding BSC sites only. This prompt only appears for RXCDR sites only. This prompt only appears for remote transcoding BSC sites only. This prompt only appears for RXCDR sites only. This prompt appears only if an MMS ID is specified. This prompt appears only if there is remote transcoding and an MMS is specified. This prompt appears for RXCDR sites and local transcodings only. This prompt appears for RXCDR sites and local transcodings only.

Which RXCDR is providing the TRAU resource(s): Which BSS is managing the CIC(s): Enter the MMS ID to the RXCDR: Enter the MMS ID to the BSS: Enter starting timeslot: Enter starting subgroup: Enter the MMS ID to MSC: Enter starting timeslot:

1 - 128

None

1 - 128

None

Y N N 1 - 31 (E1 links) 0 - 3

None None None

N N 1 - 31 (E1 links)

None None

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

68P02901W23-S

2-21 Nov 2009

CSFP

Chapter 2: Equipping the CM database

Command prompts
Prompt Enter the first COMBiner identifier: Enter the COMBiner address: Optional N Range 0 - 13 Default None Comments

0 - 255

None

The COMB address must be unique at the same site. If the COMB address is not unique, the command is rejected.

CSFP
Equip conditions
The Code Storage Facility Processor (CSFP) can be equipped with the system in either the SYSGEN ON or SYSGEN OFF mode. At an M-Cell site, the operator cannot explicitly equip the CSFP . Instead the CSFP is automatically equipped when the first BTP at a site is equipped.

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

Enter the slot number:

See Comments

None

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

2-22

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

DHP

DHP
Equip conditions
The Digital Radio Host Processor (DHP) can be equipped with the system in either the SYSGEN ON or SYSGEN OFF mode. The DHP can be equipped only at a BSS or a BTS site. The DHP cannot be equipped at an M-Cell site. The underlying GPROC need not be equipped to equip a DHP .

Command prompts
Prompt Enter the cage number for this DHP (identifier 1): Optional N Range 0 - 15 Default None Comments This identifier must be equal to the cage number where the DHP is to reside. A maximum of eight GPROCs can exist in a single cage. BSS sites: cages 0 to 13: slots 18 to 25. BTS sites: cages 2 to 15: slots 18 to 25.

Enter the unique DHP number in this cage (identifier 2): Enter the slot number: Enter the maximum number of DRIs supported by this DHP:

0 - 7

None

N N

18 - 25 1 - 6

None None

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

68P02901W23-S

2-23 Nov 2009

DPROC

Chapter 2: Equipping the CM database

DPROC
Equip conditions
The Data Processor (DPROC) can be equipped with the system in either the SYSGEN ON or SYSGEN OFF mode. The DPROC can be equipped only if the GPRS feature is unrestricted. The DPROC can be equipped only at a GPRS PCU site. A DPROC can be equipped in the PCU cabinet to be used as a Packet Interface Control Processor (PICP) or a Packet Resource Processor (PRP) or a processor with PRP and PICP function (PXP).. At least one PRP and one PICP DPROC are required per PCU. A PICP DPROC can support 0 to 2 LAPD GDS devices. A PRP DPROC can support from 0 to 4 TRAU GDS devices. There can be a maximum of 10 PRP DPROCs equipped per PCU DPROCs are not redundant.

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

Command prompts
Prompt Enter the DPROC ID: Enter the DPROC type: Optional N N Range 1 - 6 or 11 - 16 PICP or PRP or PXP Default None None

2-24

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

DRI (InCell sites)

Equip conditions
The Digital Radio Interface (DRI) for a InCell site can only be equipped at a BSS or a BTS site. The DRI can be equipped with the system in either the SYSGEN ON or SYSGEN OFF mode. If an RTF device ID is to be entered for a DRI, the RTF must be equipped before the DRI. If a DRI is added to an existing group (same first identifier), the GSM cell ID of the new DRI must be like the other DRIs in the group. If the Cell ID is different, the equip DRI command is rejected. DRIs/RTFs within a dual band cell with different frequency types must have different DRI/RTF group identifiers. The equip RTF command allows two group identifiers for a cell only if the cell is dual band. The equip cabinet command allows the secondary and primary band frequency types in each zone to which the DRIs are equipped. A DRI can be equipped to a Horizon II mini cabinet using antenna_select values of 1 or 2 only. A Horizon II mini cabinet supports a maximum of two CTU2s and two cells. Thus, dependent on whether the CTU2s are single or double density equipped, 1 to 4 DRIs are allowed. That is, 1 DRI per single density CTU2, and 2 DRI per double density CTU2.

Command prompts
Prompt Enter the 1st and 2nd DRI ID: Optional N Range First: 0 - 5, Second: 0 - 11 Default None Comments This identifier indicates a user-defined redundancy group within a cell. To qualify a redundancy group, a DRI must be connected to the same antenna as the rest of the group. Also, the DRI must be using the same portion of the TDM highway. If the cabinet ID does not exist in the database the system rejects the command.

Enter the cabinet identifier: Enter the DRI board type: Enter the cage number: Enter the slot number:

0 - 15

None

N N

drim or 0 0 - 15

None None This prompt is presented only if the entered board type is DRIM. This prompt is presented only if the entered board type is DRIM. Odd values only. Continued

7 - 17

None

68P02901W23-S

2-25 Nov 2009

DRI (InCell sites)

COMB must be separately equipped. This prompt is displayed only if COMB ID is entered for the previous prompt.

{27236} 0 - 2

None

{27236} 0 = no rx diversity 1 = 2 branch rx diversity 2 = 4 branch rx diversity

yes or no

yes

0, 1, or 2

Prompted only when DRI uses tuneable combining. 0 = none 1 = non-controlling 2 = controlling Prompted only when DRI uses tuneable combining. Prompted only when DRI uses tuneable combining. 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

Enter the COMB identifier: Enter the cavity number for this COMB: Enter the fm cell type:

N N

0 - 13 0 - 5

None None

0 - 4

None

2-26

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

DRI (M-Cell and Horizonmacro sites)

Equip conditions
The Digital Radio Interface (DRI) for an M-Cell or a Horizonmacro site can be equipped only at a BSS or a BTS site. The DRI can be equipped with the system in either the SYSGEN ON or SYSGEN OFF mode. If an RTF device ID is to be entered for a DRI being equipped, the RTF must be equipped before the DRI. If a DRI is added to an existing group (same first identifier), the GSM cell ID of the new DRI must be like the other DRIs in the group. If the Cell ID is different, the equip command is rejected. Two DRI devices can be associated with each other (double density). Neither DRI has a higher precedence than the other in the DRI pair. When equipping DRIs in a single Horizon II macro cabinet for a Dual Band configuration, the system checks for the correct Dual Band cabinet setup. That is, all 900 MHz radios in either slots 02 or 35, with the 1800 MHz radios being equipped in the other three slots. A Horizon II macro cabinet with frequency_type supporting Dual Band can be equipped with radios supporting a single frequency. {27236} For enabling the 4 Branch Receive Diversity, the DRIs must be equipped in a single Horizon II macro cabinet for single band configuration.

Command prompts
Prompt Enter the 1st and 2nd DRI ID: Optional N Range 0 - 5, 0 - 11 Default None Comments This identifier is used to identify a user-defined redundancy group within a cell. To qualify a redundancy group, a DRI must be connected to the same antenna as the rest of the group. Also, the DRI must be using the same portion of the TDM highway. When double density is specified, the operator is not prompted for tuneable combining. This parameter specifies the DRI identifier to be used for the auto-equipped DRI in a DRI pair. The system rejects attempts to equip a DRI in DCS1800 Horizonmacro cabinet if tx_power_cap= 0. Continued

Enter the density of this DRI: Enter the 2nd DRI ID of the associated DRI: Enter the cabinet identifier:

1 (single) or 2 (double) 0 - 11

1 (single)

None

0 - 15

None

68P02901W23-S

2-27 Nov 2009

DRI (M-Cell and Horizonmacro sites)

Chapter 2: Equipping the CM database

Prompt Enter the type of connection to the BTP:

Optional N

Range

Default

Comments This value can be entered as a number or its associated character string. An FMUX can be used only if the BTP resides in an M-Cell6 cabinet.

None 0 or fox (0 or master for Horizonmacro master cabinets) 1 or fmux0 2 or fmux1 3 or fmux2 4 or direct 0 - 5 None

Enter the Port to which the TCU is connected:

If the entry to the previous prompt is 4 or direct, the maximum value is 1. If cabinet type is Horizonmacro II, a check is made for valid Dual Band DRI configuration. The tcu_port value is restricted to 0 or 1 for a Horizon II mini cabinet type. The RTF entered in this field must be equipped. The cell number can be in either seven parameter format or four parameter format. This number configures the Integrated Antenna Distribution Unit (IADU): If the receive antenna is connected to DLNB 0 in the cabinet supporting the transceiver, set the antenna_select number to 1. If the receive antenna is connected to DLNB 1, set the antenna_select to 2. If the receive antenna is connected to DLNB 2, set the antenna_select to 3. If the antenna_select number is entered incorrectly, the wrong receive antenna is connected to the transceiver. Continued

Enter the 1st and 2nd RTF ID: Enter the GSM cell ID where the DRI appears: Enter antenna select number for this cell:

Y N

0 - 5, 0 - 11 GSM cell ID or cell_name 1 - 3

None None

None

2-28

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

DRI (M-Cell and Horizonmacro sites)

Prompt

Optional

Range

Default

Comments For the Horizonmacro, this number configures the 1800 Sectorized Universal Receive Filter (SURF): If the receive antenna is connected to the Rx ANT 0A/0B in the cabinet supporting the CTU, 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, 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 3. If the receive antenna is connected to the Rx ANT 900 0A/0B in the cabinet supporting the CTU, set the antenna_select number to 2.

NOTE
2 is the default value and does not work with any other selection The antenna_select value is restricted to 1 or 2 for a Horizon II mini cabinet type. Enter COMB 1st and 2nd ID: Enter cavity number: Does this DRI use tuneable combining: Y Y 0 - 13, 0 or 1 0 - 5 None COMB must be separately equipped. This prompt displays only if COMB ID is entered for the previous prompt. None If the DRI is equipped to the following cabinets, the system does not prompt for combiner information: HORIZONMACRO2, HORIZONMACRO2_EXT, HORIZON2MINI, or HORIZON2MINI_EXT. 0 = none 1 = non-controlling 2 = controlling Continued

yes or no

Enter the tuneable combining type:

0, 1 or 2

None

68P02901W23-S

2-29 Nov 2009

DYNET

Chapter 2: Equipping the CM database

Prompt Enter the COMB identifier: Enter the cavity number for this COMB: Enter the diversity flag for this DRI: Enter the fm cell type:

Optional N N

Range 0 - 13 0 - 5

Default None None

Comments

{27236} 0 - 2

None

{27236} 0 = no rx diversity 1 = 2 branch rx diversity 2 = 4 branch rx diversity 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

0 - 4

None

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

Equip conditions
All DYNETs that share the same first identifier must have the same BTSs or timeslot switching sites in the same order. Also, these DYNETs must have different E1 links used by the BTSs within the BTS network. These limitations allow definition of multiple link BTS networks for sharing purposes, while limiting the configuration to simplify sharing. An open loop DYNET has an automatically equipped PATH for an open loop daisy chain, with a second identifier equal to the second identifier of the DYNET times two. A closed loop DYNET has two PATHs automatically equipped. The identifier of the first PATH is equal to the identifier of the DYNET multiplied by 2. The identifier of the second PATH is equal to the identifier of the DYNET multiplied by 2 and with 1 added. The automatically equipped PATH in closed loop daisy chains has a second identifier one greater than second identifier of the first PATH automatically equipped. The identifiers of the PATHs that can be automatically equipped when a DYNET is equipped are not allowed when equipping or unequipping the PATH device. The system does not verify whether this feature is available when a DYNET is equipped.

2-30

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

DYNET

Command prompts
Prompt Enter 1st and 2nd unique DYNET identifiers: Optional N Range First identifier: 0 - 19, Second identifier: 0 - 2 0 - 890 or 1 Default None Comments If the ID exists in the database, the command is rejected.

Enter BSC MMS identifier:

None

This prompt requires two values: The first value is the MSI at the BSC where the MMS resides. The second value is the MMS for the BSC network definition.

Enter SITE identifier: Enter the upstream MMS identifiers:

0 - 140 ts_switch, BSC For BTS4, BTS5, BTS6, TopCell, and ExCell: 0 - 9, 0 or 1. For M-Cell2: 0 - 1, 0 - 1. For M-Cell6: 0 - 3, 0 - 1. For BTS4, BTS5, BTS6, TopCell, and ExCell: 0 - 9, 0 or 1. For M-Cell2: 0 - 1, 0 - 1. For M-Cell6: 0 - 3, 0 - 1.

None

The TS site number, timeslot switching site, or the BSC. This prompt requires two values: The first value is the MSI at the BTS where the MMS resides. The second value is the MMS for the BTS network definition.

None

Enter the downstream MMS identifiers:

None

This prompt requires two values: The first value is the MSI at the BTS where the MMS resides. The second value is the MMS for the BTS network definition.

This prompt can be left blank.

68P02901W23-S

2-31 Nov 2009

EAS (InCell sites)

Chapter 2: Equipping the CM database

EAS (InCell sites)

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

Command prompts
Prompt Enter the first device ID for the EAS: Enter the cage where the PIX is connected: Enter the daughter slot where the PIX is located: Enter the relay wiring of the 4 relays: Enter the no alarm condition for the 8 optos (0 - closed, 1 - open): Enter each opto whose state changes are to be reported: Enter the user defined alarm index for the 8 optos: Optional N Range 0 - 7 Default None Comments If the ID exists in the database the command is rejected.

0 - 15

None

15 - 18

None

0 or 1

None

Enter four values, each separated by a space. Enter eight values, each separated by a space.

0 or 1

None

1 - 8

None

Enter eight values, each separated by a space. Enter eight values, each separated by a space. Enter the string mpf in place of one of the integers to indicate which opto is used for the EAS Mail Power Failure alarm. Operator can enter up to 8 values for an InCell site and up to 16 values for an M-Cell site. Separate values with either a space or a comma. If no value is entered in the range prompt, then no state changes are reported for any optocoupler. The values can be entered in any order. The operator also has the option of entering all and of entering a range of optos. Continued

0 - 33

None

Enter each opto whose state changes are to be reported:

1 - 8 for InCell sites. 1 - 16 for M-Cell sites.

None

2-32

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

EAS (M-Cell sites)

Prompt Enter the user defined alarm index for opto n:

Optional Y

Range 0 - 33 and 128

Default None

Comments The operator must enter one value indicating the index of the user-defined alarm string for the optocoupler specified by 'n'. The text string mpf is interpreted as the value 128. No default is accepted for this prompt. A prompt is displayed for each reporting optocoupler specified in the previous prompt.

EAS (M-Cell sites)

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

68P02901W23-S

2-33 Nov 2009

GBL

Chapter 2: Equipping the CM database

Command prompts
Prompt Enter the first device ID (Cabinet ID) for the EAS: Enter the relay wiring of the 4 relays: Enter the no alarm condition for the 16 optos (0 closed, 1 - open): Enter each opto whose state changes are to be reported: Enter the user defined alarm index for the 16 optos: Optional N Range 0 - 15 Default None Comments Cabinet identifier.

0 or 1

None

0 = deactivate the relay 1 = activate the relay Enter four values, each separated by a space. Enter 16 values, each separated by a space. Only 12 optos are available for Horizon II mini. Enter 16 values, each separated by a space. Only 12 optos are available for Horizon II mini. Enter 16 values, each separated by a space. Enter the string mpf in place of one of the integers to indicate which opto is used for the EAS Mail Power Failure alarm. Only 12 optos are available for Horizon II mini.

0 or 1

None

1 - 16

None

0 - 33

None

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

Equip conditions
This device can be equipped with the system in either SYSGEN ON or SYSGEN OFF mode. The GBL can be equipped only if the GPRS feature is unrestricted. To support EGPRS the GBL bandwidth between the PCU and the SGSN has been increased. The amount of bandwidth necessary for a maximal configured PCU is 12 E1s of GBL, and for a maximal configured BSS is 20 E1s. This maximum number of GBLs can be configured independent of whether EGPRS is restricted or not.

2-34

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

GBL

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

Enter the starting timeslot: Enter the ending timeslot: Enter the t391 timer:

N N Y

1 - 31 1 - 31 5 - 29

None None 10

Enter the t392 timer: Enter the n391 counter:

6 - 30

1 - 255

Enter the n392 counter:

1 - 10

Enter the n393 counter:

1 - 10

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

68P02901W23-S

2-35 Nov 2009

GCLK

Chapter 2: Equipping the CM database

GCLK
Equip conditions
The Generic Clock (GCLK) can be equipped with the system in either the SYSGEN ON or SYSGEN OFF mode. The GCLK cannot be explicitly equipped at M-Cell sites. This device is automatically equipped when a BTP is equipped. Some devices do not require all the prompts. Therefore, the system cannot always display all the prompts provided in the next section.

Command prompts
Prompt Enter the device identification for the GCLK: Optional N Range 0 or 1 Default None Comments The GCLK slot is assigned based on the device ID: If the device ID is set to 0, the GCLK is assigned to slot 5. If the device ID is set to 1, the GCLK is assigned to slot 3.

Enter the cage number: Is CLKX 0 (slot U7) present?

N Y

0 - 15 yes or no

None no The slot number displayed in the prompt depends on the GCLK ID. The alternate slot number for GLKX 0 is U4. (See also NOTE.) The slot number displayed in the prompt depends on the GCLK ID. The alternate slot number for GLKX 1 is U3. (See also NOTE.) The slot number displayed in the prompt depends on the GCLK ID. The alternate slot number for GLKX 2 is U2. (See also NOTE.)

Is CLKX 1 (slot U6) present?

yes or no

Is CLKX 2 (slot U5) present?

yes or no

2-36

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

GDS

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

NOTE
Locking the GDS causes the GSLs to go OOS. This differs from pre-GSR9 behavior where there was no hierarchal relationship between the GDS and the GSL. The BSS rejects an attempt to equip a GDS to an MMS at the BSC where the mms_priority of the MMS is a non-zero value. The GDS device allows a maximum of 72 E1 links to be configured as TRAU GDS per BSS. The device also allows a maximum of 36 E1 links to be configured as TRAU GDS per PCU. The maximum number of TRAU GDSs that can be configured is independent of whether EGPRS is restricted or not. The number of LAPD GDS devices is two per PCU and six per BSS.

Command prompts
Prompt Enter the GDS identifier: Enter the GDS connectivity: Optional N N Range 0 - 37 E1 or ETHERNET Default None None Notes Unique identifier of the GDS.

When GDS connectivity is equal to ETHERNET, the following will be prompted: Enter the BSC ETH identifier: Enter the PCU ETH identifier: N N None None

When GDS connectivity is equal to E1, the following will be prompted: Enter the BSC MMS identifier: Enter the PCU MMS identifier: Enter the GDS type: N N N 0 - 95, 0 - 1 0 - 23, 0 - 1 TRAU or LAPD None None None

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

68P02901W23-S

2-37 Nov 2009

GPROC

Chapter 2: Equipping the CM database

GPROC
Equip conditions
The Generic Processor (GPROC) can be equipped with the system in either the SYSGEN ON or SYSGEN OFF mode. This device cannot be equipped at M-Cell sites.

Command prompts
Prompt Enter the GPROC identifier: Enter the cage number: Optional N N Range 1 - 111 See Comments Default None 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. Valid slot numbers are dependent on the site: BSC, BSS, and BTS sites: slots 18 to 25. RXCDR sites: slots 25 to 26. Comments

Enter the slot number:

See Comments

None

GSL
Equip conditions
The GPRS Signaling Link (GSL) can be equipped only if the GPRS feature is unrestricted. The GSL can be equipped with the system in either SYSGEN ON or SYSGEN OFF mode. The equipage of a GSL is allowed only if the remaining GDS timeslot resources available to the PCU are sufficient to support the GPRS timeslot resources for cells for which GPRS is enabled. The GSL is allowed only on an LAPD GDS. 30 GSLs can be equipped to a LAPD GDS. All 60 could be equipped to one DPROC that has two GDSs equipped on it. However, for redundancy, two DPROCs are required each with a LAPD GDS equipped with 30 GSLs. To bring the GSL in service, unlock the GSL at either the OMC-R or MMI prompt.

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

2-38

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

KSW

Command prompts
Prompt Enter the GSL identifier: Enter the unique GDS identifier: Optional N N Range 0 - 59 0 - 37 Default None None Notes

KSW
Equip conditions
The Kiloport Switch (KSW) can be equipped with the system in either the SYSGEN ON or SYSGEN OFF mode. The KSW cannot be equipped at M-Cell sites.

Command prompts
Prompt Enter Portion of TDM Highway Managed (identifier 1): Enter TDM identifier (identifier 2): Optional N Range 0 - 3 Default None Comments The first device ID for the KSW must match the KSW pair in the cage where the KSW is being equipped. The KSW slot is assigned based on the second device ID; If the second device ID is set to 0, the KSW is assigned to slot 27. If the second device ID is set to 1, the KSW is assigned to slot 1.

0 or 1

None

Enter the cage number: Are DRIs allowed on highway managed by this KSW:

N N

0 - 15 Y or N

None None This prompt does not occur at a BSC.

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

68P02901W23-S

2-39 Nov 2009

MSI (InCell, BSC, and RXCDR sites)

Chapter 2: Equipping the CM database

Equip conditions
The Location Services feature must be unrestricted. For LMTLs to be equipped, the BSC must be configured to support a BSS-based SMLC. When an LMTL is equipped on an MMS that hosts other non-Lb-interface links, a warning message displays indicating a conflict in MMS timeslot usage.

Command prompts
Prompt Enter the device identification for this LMTL: Enter the first MMS identifier for this device: Enter the second MMS identifier for this device: Enter the timeslot on MMS where this device appears: Optional N Range 0 - 15 Default None Comments Location Services must be unrestricted.

0 or 95

None

0 - 1

None

31 (E1)

None

MSI (InCell, BSC, and RXCDR sites)

Equip conditions
The Multiport Serial Interface (MSI) for InCell, BSC, or RXCDR sites can be equipped with the system in either the SYSGEN ON or SYSGEN OFF mode. An MSI with msi_type of msi_ext_hdsl cannot be equipped with the protocol types of both MMSs entered as E1 at a BSC or an InCell BTS site.

Command prompts
Prompt Enter the device identification for the MSI: Optional N Range {22169} BSC: 0 - 95 RXCDR: 0 123 BTS: 0 - 9 (InCell) 0 - 15 Default None Comments

Enter the cage number:

None

Continued

2-40

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

MSI (InCell, BSC, and RXCDR sites)

Prompt Enter the slot number:

Optional N

Range BSS and BSC sites: All MSI type slots 6 - 17. BTS sites: MSI type 0 slots 6 - 17, MSI type 1 or 2 not allowed. RXCDR sites MSI type 0 slots 6 - 10, MSI type 1 or 2 slots 6-24 0 or msi, 1 or xcdr, 2 or gdp, 7 or msi_ext_hdsl, 12 or RF_unit, 20 or gdp2. E1 or HDSL

Default None

Comments Valid slot numbers are based on site type and MSI type.

Enter the MSI type:

None

The input can be the numeric value or the text string. (The value of 5 is reserved.) MSI types xcdr or gdp are only allowed at sites where transcoding occurs.

Enter MMS0 protocol type:

HDSL

Prompt appears only if the Integrated MCell HDSL feature is enabled, and the msi_type is niu_hdsl, niu_ext_hdsl, or msi_ext_hdsl. Prompt appears only if the Integrated MCell HDSL feature is enabled, and the MSI type is niu_hdsl, niu_ext_hdsl, or msi_ext_hdsl, and the protocol type is HDSL. Prompt appears only if the Integrated MCell HDSL feature is enabled, the protocol is HDSL, and the MSI type is niu_hdsl. Prompt appears only if the Integrated MCell HDSL feature is enabled, and the MSI type is niu_hdsl, niu_ext_hdsl, or msi_ext_hdsl. Continued

Enter the number of timeslots supported on MMS0:

16 or 32

Enter MMS0 modem setting:

master or slave

None

Enter MMS1 protocol type:

E1 or HDSL

HDSL

68P02901W23-S

2-41 Nov 2009

MSI (M-Cell sites)

Chapter 2: Equipping the CM database

Prompt Enter the number of timeslots supported on MMS1:

Optional Y

Range 16 or 32

Default 32

Comments Prompt appears only if the Integrated MCell HDSL feature is enabled, and the msi_type is msi_ext_hdsl, with a protocol type of HDSL for this MMS. Prompt appears only if the Integrated MCell HDSL feature is enabled, the protocol is HDSL, and the msi_type is niu_hdsl. MSI identifier of GDP with MMS available for routing the transcoding circuits of a secondary GDP towards the MSC. Read-Write (can be set only when the MSI device is created). MSC MMS always zero because MSIs cannot provide MSC MMSs. Read-Write (can only be set when the MSI device is created). Prompt appears only if MSI type entered as 2 or gdp. Prompt appears only if MSI type entered as 2 or gdp, or as 20 or gdp2.

Enter MMS1 modem setting:

master or slave

None

Enter the MSI ID to the MSC:

{22169} BSC: 0 - 95 RXCDR: 0 123

Value of GDPs own MSDI ID

Value of GDPs own second ID

Enter the transcoding capability:

0 or Basic, 1 or Enhanced, 2 or GDP_2E1.

None

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

MSI (M-Cell sites)

Equip conditions
The Multiport Serial Interface (MSI) for M-Cell sites can be equipped with the system in either the SYSGEN ON or SYSGEN OFF mode. M-Cell sites do not use MSI boards. The Network Interface Unit (NIU) performs the MSI function in an M-Cell2 or M-Cell6 cabinet. That is why the system prompts refer to the NIU.

2-42

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

MSI (M-Cell sites)

The msi_type of niu_hdsl is only supported at M-Cellcity, Horizon micro or Horizon compact sites. The msi_type of niu_ext_hdsl is supported at M-Cell2, M-Cell6, M-Cellcity, M-Cellmicro, Horizon micro, and Horizon compact sites. A warning is issued if the protocol types of both MMSs of an MSI, with an msi_type of niu_hdsl at an M-Cellcity, M-Cellmicro, Horizon micro, or Horizon compact site, are entered as E1. An MSI with msi_type of niu_ext_hdsl cannot be equipped with the protocol types of both MMSs entered as E1 at an M-Cell2, M-Cell6, M-Cellmicro, M-Cellcity, Horizon micro or Horizon compact site. The msi_type niu_ext_hdsl can be equipped in slot 1 of a card frame (at an M-Cell6 site) only if the protocol type of MMS0 is entered as HDSL. When equipping an HDSL NIU, the new hdsl_oos_mon_period and hdsl_restore_mon_period durations default to known software values.

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

Command prompts
Prompt Enter the device identification for the MSI: Enter the MCU card frame in which the NIU exits: Enter the NIU slot number: Enter the MSI type: Optional N Range See comments 0 or 1 (See comments) 0 or 1 (See comments) 3 or niu, 8 or niu_hdsl, 9 or niu_ext_hdsl E1 or HDSL Default None Comments M-Cell 2 BTS: 0 or 1 M-Cell 6 BTS: 0 to 3 M-Cellmicro: 0 0 is the only valid value for this field if equipping to M-Cellmicro. 0 is the only valid value for this field if equipping to M-Cellmicro and M-Cell2. The input can be either the numeric value or the text string.

None

niu

Enter the MMS0 protocol type:

HDSL

If the Integrated MCell HDSL feature is enabled, and the msi_type is niu_hdsl or niu_ext_hdsl, the prompt appears. Continued

68P02901W23-S

2-43 Nov 2009

MSI (M-Cell sites)

Chapter 2: Equipping the CM database

Prompt Enter the number of timeslots supported on MMS0:

Optional Y

Range 16 or 32

Default 32

Comments If the Integrated MCell HDSL feature is enabled, and the msi_type is niu_hdsl or niu_ext_hdsl, with a protocol type of HDSL for this MMS, the prompt appears. If the Integrated MCell HDSL feature is enabled, and the msi_type is niu_hdsl with a protocol type of HDSL for this MMS, the prompt appears If the Integrated MCell HDSL feature is enabled, and the msi_type is niu_hdsl, or niu_ext_hdsl, the prompt appears. If the Integrated MCell HDSL feature is enabled, and the msi_type is niu_hdsl or niu_ext_hdsl with a protocol type of HDSL for this MMS, the prompt appears. If the Integrated MCell HDSL feature is enabled, and the msi_type is niu_hdsl with a protocol type of HDSL for this MMS, the prompt appears.

Enter MMS0 modem setting:

master or slave

master

Enter the MMS1 protocol type:

E1 or HDSL

HDSL

Enter the number of timeslots supported on MMS1:

16 or 32

Enter MMS1 modem setting:

master or slave

slave

2-44

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

MSI (PCU only)

Equip conditions
The Multiport Serial Interface (MSI) for PCU sites can be equipped with the system in SYSGEN ON mode. This device can also be equipped when the system is outside the SYSGEN ON mode. The site must not be locked when this device is equipped outside SYSGEN ON mode. A modified MSI device is used to describe the serial interface device which can be equipped to DPROC boards. It is a child class of PCU. The GPRS MSI type is not available when the GPRS feature is restricted. The BSS supports equipage of a GBL to a PICP MMS. The BSS supports equipage of a GDS at the PCU. The BSS supports equipage of a GDS to an HDSL MSI when the child MMS of the MSI is of type E1. The BSS does not support the modification of the msi_type for an MSI. The BSS supports equipage of up to two MSIs per DPROC board. A DPROC board must be equipped before an MSI can be equipped to the same DPROC. The PCU supports a unique identifier for each MSI equipped within the PCU. Two MMS devices are automatically equipped with each PCU MSI equip. All MMSs on the same MSI must be configured for the same destination: BSC or SGSN. If only one MSI is available, then the MSI must be equipped in PMC socket 1 of a DPROC in either slot 1 or slot 2.

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

Enter the DPROC socket:

1 or 2

None

68P02901W23-S

2-45 Nov 2009

MTL

Chapter 2: Equipping the CM database

MTL
Equip conditions
The Message Transfer Links (MTL) is not allowed at an RXCDR site and can be equipped only at site 0. The MTL cannot be equipped on an HDSL link. The MTL can be equipped only at the BSC.

Command prompts
Prompt Enter the device identification for this MTL: {28337} Enter the number of DSO channels for this MTL: Optional N N* Range 0 - 15 1: 64 kbps MTL 31: HSP MTL Other values reserved 0 - 123 0 or 1 1 - 31 (E1) Default None 1

Enter the first MMS description for this device: Enter the second MMS description for this device: Enter timeslot on MMS where this device appears:

N N N**

None None None

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

If an MMS has another timeslot that conflicts when equipping an MTL, the system generates the following warning: COMMAND ACCEPTED: WARNING: Conflict in MMS usage, display timeslot usage to verify. Conflicting usage exists when at least one timeslot provides connectivity to a BTS and another is connected to a different type of device. That is, RXCDR, OML, and so on.

2-46

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

OML

OML
Equip conditions
The Operations and Maintenance Link (OML) cannot be equipped on an HDSL link. The OML can be equipped only at site 0.

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

N N

None None

If an MMS has another timeslot that conflicts when equipping an OML, the system generates the following warning:COMMAND ACCEPTED: WARNING: Conflict in MMS usage, display timeslot usage to verify. Conflicting usage exists when at least one timeslot provides connectivity to a BTS and another is connected to a different type of device. That is, RXCDR, OML, and so on.

OPL
Equip conditions
The Optimization Link (OPL) is used to carry measurement report data out of the BSC. The link is a dedicated 64 kbit/s link HDLC link between the BSC and the IOS platform equipped to a E1 timeslot on an existing MMS. To equip the OPL follow the given steps: 1. 2. Select the least utilized LCF on BSC. Modify the selected LCF to support OPL using the command modify_value bsc max_opls 1 lcf <id1> <id2> <id3> 3. Equip OPL on the desired timeslot.

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

68P02901W23-S

2-47 Nov 2009

PATH

Chapter 2: Equipping the CM database

Command prompts
Prompt Enter the device ID for the OPL Enter the first MMS identifier for this device Enter the second MMS identifier for this device Enter the timeslot on MMS where this device appears Optional N N Range 0 - 3 BSC: 0 - 95 RXCDR: 0 - 123 0 or 1 Default None None

None

E1: 1 - 31

None

PATH
Equip conditions
The Path (PATH) can be equipped when the system is in either the SYSGEN ON or SYSGEN OFF mode. Prompts to equip a path are presented for each link in the path. If one of the MSIs is msi_type RF_Unit, the system rejects the equip path command. A path for an HDSL link must have the same number of timeslots, identical link protocol types, and HDSL modems that are in a master/slave configuration. The single exception to this rule is when the system cannot check master/slave settings because the HDSL link consists of two external modems.

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

2-48

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

PATH

Prompt Enter the BSC MMS identifier:

Optional N

Range {22169} 0 - 95 (MSI), 0 or 1 (MMS)

Default None

Comments Type two values, separated by a space; the first value is the MSI ID; the second value is the MMS ID. If the Aggregate Abis feature is enabled the system accepts ts_switch as the site ID. If ts_switch is used, the system does not prompt for upstream MSI, upstream MMS, downstream MSI and downstream MMS identifiers. The upstream MMS identifier cannot correspond to an RF_Unit MSI. MMS ID 2 is 0 - 1.

Enter SITE identifier:

0 - 140, or ts_switch (See comments)

None

Enter the upstream MMS identifier:

{22169} BSC: 0 - 95, BTS: 0 (Horizon II Macro, Horizon II Mini, 0 - 9 (In-Cell, Horizon Macro), 0 - 3 (M-Cell6), 0 - 1 (M-Cell2).

None

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

68P02901W23-S

2-49 Nov 2009

PATH

Chapter 2: Equipping the CM database

Prompt Enter the downstream MMS identifier:

Optional N

Range {22169} BSC: 0 - 95, BTS: 0 - 9 (InCell), 0 - 3 (M-Cell6), 0 - 1 (M-Cell2). 0 - 140, or ts_switch (See comments)

Default None

Comments

Enter the SITE identifier:

None

If the Aggregate Abis feature is enabled the system accepts ts_switch as the site ID. If ts_switch is used, the system does not prompt for upstream MSI, upstream MMS, downstream MSI, and downstream MMS identifiers. The range for the MMS ID 2 is 0 - 1.

Enter the upstream MMS identifier:

{22169} BSC: 0 - 95, BTS: 0 - 9 (InCell), 0 - 3 (M-Cell6), 0 - 1 (M-Cell2).

None

If an MMS has another timeslot that conflicts when equipping a PATH, the system generates the following warning: COMMAND ACCEPTED: WARNING: Conflict in MMS usage, display timeslot usage to verify. Conflicting usage is when at least one timeslot provides connectivity to a BTS and another type of device (such as, an RXCDR).

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

2-50

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

PCU

PCU
Equip conditions
The Packet Control Unit (PCU) can be equipped with the system in SYSGEN ON mode. With the enhanced PCU (ePCU) in GSR9, 3xPCU configuration is not required to achieve the target GPRS capacity. That is, supporting 3240 PDTCH (810 active, 2430 standby). 3xPCU configuration is disabled in GSR9. When a PCU is equipped, a corresponding CAB device and CAGE device are automatically equipped. A PCU can be equipped only if parameter land_layer1_mode is set to E1.

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

PSI
Equip conditions
The PSI (Packet Subrate Interface) is designed to be a generic interface to an external packet network through the Ethernet. The primary function of the PSI card is to terminate GPRS TRAU and transfer the TRAU payload to the PCU over Ethernet. The PSI device is equipped inside or outside SYSGEN mode. The PSI device is equipped only at a BSS or BSC sites. The BSC supports a maximum of 4 PSIs per cage.

68P02901W23-S

2-51 Nov 2009

PSP

Chapter 2: Equipping the CM database

Command prompts
Prompt Enter the PSI Identifier: Enter the cage number Identifier: Enter the slot number: Enter the number of TDM timeslot blocks: Enter the maximum number of GSLs on this PSI: Enter the base IP address for the PSI: Optional N N N Y Y N Range 0 - 11 0 - 13 6 - 13 2 - 10 0 - 30 1.0.0.1 223.255.255 .237 Default None None None 2 0 None The base IP address is used for the MCU. 17 contiguous addresses are available after the base address for the DSPs. The IP address is entered in dotted quad notation. Valid slot number is 6, 7, 12 and 13. Comments

Enter the subnet mask: Enter the router IP address:

Y Y

128.0.0.0 255.255. 255.255.255.0 255.0 0.0.0.0 255.255.255 .254 0.0.0.0 The IP address of the router. The value of 0.0.0.0 means that no router is in use.

PSP
Equip conditions
The PCU System Processors (PSPs) are equipped only when the GPRS feature is unrestricted. The PSPs can only be fitted at a PCU. Two PSPs can be installed in each PCU. The PSPs must be physically installed before code download can start to the PCU. The site must not be locked when this device is equipped outside the SYSGEN ON mode. The PSPs are auto-equipped. The system uses a default value for the PSP slot; therefore, the operator is not prompted.

2-52

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

RSL

RSL
Equip conditions
The location for the Radio System Link (RSL) must be the BSC (site 0). Only one RSL can be equipped to an NIU in slot 1 of an M-Cell terminating site. Only four RSL devices can be enabled per E1 span. Previously, the number of RSL devices supported on an NIU and an E1 span were the same.

Command prompts
Prompt Enter the 1st device ID for the RSL: Enter the 2nd device ID for the RSL: Optional N N Range 0 - 140 0 - 7 See Comments 0 - 9 1400 - 5000 1 - 5 1 - 10 Default None None The range depends on the site type: InCell: 0 - 7. M-Cell 2/6 BTS: 0 - 5. Comments

Enter the Unique PATH ID: Enter LAPD T200 Timer value: Enter LAPD N200 value: Enter LAPD K value:

N Y Y Y

None 2500 3 7 Values must be in multiples of 50.

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

RXCDR
Equip conditions
The Remote Transcoder (RXCDR) must be the first device equipped by the operator in the SYSGEN ON mode at an RXCDR site. If an RXCDR device is equipped at a BSS site, it is actually an Associate RXCDR (AXCDR) device (see AXCDR on page 2-12).

68P02901W23-S

2-53 Nov 2009

None

Continued

68P02901W23-S

2-55 Nov 2009

XBL

Chapter 2: Equipping the CM database

Prompt Enter the timeslot on MMS where this device appears: Enter the group of the timeslot where this device appears: Enter LAPD T200 time value for the device: Enter LAPD N200 value: Enter LAPD K value:

Optional N

Range E1: 1 - 31. 0 - 3

Default None

Comments

Prompted only if the 16 kbit/s option is unrestricted and the XBL data rate is set to 16 kbit/s. 2500 3 7 Values must be in multiples of 50.

Y Y Y

1400 5000 1 - 5 1 - 127

If an MMS has another timeslot that conflicts when equipping an XBL, the system generates the following warning: COMMAND ACCEPTED: WARNING: Conflict in MMS usage, display timeslot usage to verify. Conflicting usage exists when at least one timeslot provides connectivity to a BTS and another is connected to a different type of device. That is, RXCDR, OML, and so on.

2-56

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Information for equipping functions

This section provides conditional information for the rules on equipping the following functions, and lists the equip command prompts that occur with each function: LCF on page 2-57 OMF on page 2-58 RTF on page 2-58

LCF
Equip conditions
The Link Control Function (LCF) can only be equipped at BSC site types where the BSC type is not zero. At least one LCF must have a max_mtls value greater than zero. The sum of all GSLs (GPRS) specified by the equipped LCFs must be greater than or equal to the total number of equipped GSLs.

Command prompts
{28337} Prompt Enter the function identifier for the LCF: Enter the number of DSO channels the LCF can manage as MTLs: Enter the number of LMTLs the LCF can manage: Enter the number of CBLs the LCF can manage: Enter the number of GSLs the LCF can manage: Optional N N Range 0 - 24 0, 1, 2, 31* 0 - 2 Default None None Comments

Y**

None

Y** Y**

0 - 1 0 - 12

None None Prompted only when the GPRS feature is unrestricted.

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

OMF

Chapter 2: Equipping the CM database

OMF
Equip conditions
The Operation and Maintenance Function (OMF) can only be equipped at BSC or BSS site types where the BSC type is set to 2. This function can be equipped with the system in SYSGEN ON mode or outside the SYSGEN ON mode. The site must not be locked when this function is equipped outside SYSGEN ON mode.

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

RTF
Equip conditions
The Radio Transceiver Function (RTF) can be equipped with the system in either SYSGEN ON or SYSGEN OFF mode. When equipping the RTF, the system enforces the following dependencies: An RTF cannot be equipped in SYSGEN OFF mode if: All the RTF timeslots are non-hopping (255); and other non-hopping RTFs or enabled frequency hopping systems in the cell are already using the maximum number of frequencies. The RTF hops through one or more timeslots which cause frequency collisions. A frequency collision occurs when two enabled FHIs hop through the same ARFCN and one RTF uses one FHI in the same timeslot and another RTF uses the other FHI. If the site is not in a DYNET, an RTF cannot be equipped to a site using dynamic allocation. Due to the restrictions imposed by the BSS, Base Band Hopping (BBH) is not supported on 64 kbit/s RTF, of which carrier A is EGPRS capable, when it is equipped on a double density CTU2.

When an attempt is made to equip a new RTF in and out of Sysgen mode, and the requested PDTCHs exceed the GDS or PMC capacity on the PCU, the BSS accepts the request. It also issues a warning to indicate that there is not enough GDS or PMC resource available. If one or more PCS1900 frequency blocks are available to the BSS and an ARFCN is entered which is one of the block edges, the max_tx_bts for the cell assigned to this RTF cannot be less than or equal to 3 (which corresponds to greater than 36 dBm).

2-58

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

RTF

The channel numbers at the block edges are: 512 585 587 610 612 685 687 710 712 735 737 810

These channel numbers do not apply if: The frequency at the assigned cell does not include PCS1900. The available frequency blocks for the BSS are contiguous (such as A and D) and the ARFCN is on the adjacent border of the selected blocks. The Concentric Cells feature is enabled, the power based use algorithm is used and the block edge frequency is defined to be an inner zone carrier with a maximum transmit power level (tx_pwr_red) less than 36 dBm.

When the Dual Band Cells option is enabled, the frequency type is managed on a zone basis. Primary band carriers are configured in the outer zone and secondary band carriers are configured in the inner zone. DRIs/RTFs within a dual band cell with different frequency types must have different DRI/RTF group identifiers. The equip RTF command allows two group identifiers for a cell only if the cell is dual band. The equip cabinet command allows the secondary and primary band frequency types in each zone to which the DRIs are equipped. The frequency type of the secondary band defines the valid range for the ARFCN of an RTF configured for the inner zone. equip RTF for the secondary band in a dual band cell does not prompt for TRX power reduction. For a dual band cell, an attempt to equip RTF for a BCCH RTF in the inner zone is rejected. When equipping an RTF to a dual band cell, the specified FHIs can contain only the frequencies in the band of the RTF. The pkt_radio_type parameter specifies the terrestrial resource capability of an RTF. The mutually exclusive options are 16 kbit/s, 32 kbit/s, 64 kbit/s, and none. An EGPRS-capable RTF can carry EGPRS PDTCHs and can allocate 64 kbit/s terrestrial channels to support the EGPRS coding schemes on the air timeslots. For a complete description of this parameter, refer to pkt_radio_type on page 8-76.

Warning messages
The following warning message displays when an attempt is made to equip a new RTF and the requested PDTCHs exceed the GDS or PMC capacity on the PCU: COMMAND ACCEPTED: WARNING: Insufficient GDS resources available for all PDTCHs on the PCU. The following warning message displays if a frequency is specified that is already in use at the site: COMMAND ACCEPTED: WARNING: Specified ARFCN already exists at specified site. The following warning message displays if a frequency is specified that is already used at a cell: COMMAND ACCEPTED: WARNING: Specified ARFCN already exists in this cell.

68P02901W23-S

2-59 Nov 2009

RTF

Chapter 2: Equipping the CM database

Reject messages
The following message displays if the max_tx_bts for the cell must be reduced before an RTF can use the specified ARFCN: COMMAND REJECTED: Block edge ARFCN not allowed for max_tx_bts level of the cell The following message displays if the ARFCN specified for the RTF is not valid for the cell: COMMAND REJECTED: An out of range frequency was entered for this frequency. The following message displays if the trx_pwr_red for the carrier must be reduced before the RTF can use a specified ARFCN: COMMAND REJECTED: Power level is not allowed for a Carrier with a PCS block edge ARFCN.

Error messages
The following error messages occur when attempting to equip an RTF for EGPRS: For a site which has no Horizonmacro, Horizonmacro2 or Mcell family of cabinets equipped: COMMAND REJECTED: Horizonmacro, Horizonmacro2 or Mcell family of cabinets required for EGPRS. With 32 kbit/s packet radio capabilities, when the Coding Scheme 3 and 4 feature is restricted: COMMAND REJECTED: Received a request to modify a restricted optional feature. With 64 kbit/s packet radio capabilities, when the EGPRS feature is restricted: COMMAND REJECTED: Received a request to modify a restricted optional feature. Which is baseband hopping through other non-EGPRS RTFs: COMMAND REJECTED: EGPRS and non-EGPRS carriers cannot have the same FHI That is subequipped: COMMAND REJECTED: 32 kbit/s / 64 kbit/s TRAU rate is not allowed for sub-equipped RTFs With an associated RSL: COMMAND REJECTED: Multiplexed RSL is not allowed with 64 K RTFs At a site that supports dynamic allocation: COMMAND REJECTED: 32 kbit/s / 64 kbit/s TRAU rate is not allowed at sites using dynamic allocation. If a non-zero value of extended range timeslots is entered for an RTF with 64 kbit/s packet radio capabilities: COMMAND REJECTED: Extended range timeslots are not allowed for EGPRS carriers.

2-60

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

RTF

With a valid FHI, outside Sysgen mode: If the RTF is at a site whose master cabinet is not a Horizon II macro. If the hopping system is set to baseband hopping. COMMAND REJECTED: Master cabinet must be Horizonmacro2 for EGPRS RTFs to hop in baseband hoppping.

To be in the inner zone of a concentric cell: COMMAND REJECTED: EGPRS/GPRS carriers must be in the outer zone of a concentric cell.

Command prompts
Prompt Enter capacity of carrier: Optional N Range FULL or SUB Default Comments This prompt does not display if: - the RTF is equipped to a BTS using dynamic allocation. - the subequipped RTF feature is not available. None None

Enter type of carrier: Enter the 1st and 2nd RTF ID:

N N

bcch or non_bcch Valid first RTF ID: 0 - 5. Valid second RTF ID: 0 - 11, 0 - 1 for M-Cell. 0 - 9

Enter the primary Unique PATH ID:

None

If the BTS type is 16 k RSL, the system displays the next prompt. Otherwise, proceed with the Enter the optional secondary Unique Path ID prompt. This prompt will not display if the RTF is equipped to a BTS using dynamic allocation. If the RTF is equipped to a BTS using dynamic allocation, this prompt does not display. Continued

Enter the optional 2nd identifier for the associated RSL:

Micro: 0 - 1. MCell: 0 - 5. InCell: 0 - 7.

None

68P02901W23-S

2-61 Nov 2009

RTF

Chapter 2: Equipping the CM database

Prompt Enter the optional secondary Unique Path ID:

Optional Y

Range 0 - 9

Default None

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

Enter the GSM cell to which this carrier is assigned: Enter carrier absolute radio freq. channel:

GSM cell ID or cell_name See Comments.

None

Enter the 8 carrier frequency hopping indicators:

0 - 3 and 255

255

2-62

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

RTF

Prompt Enter the 8 carrier training sequence codes:

Optional N

Range 0 - 7

Default None

Comments The eight carrier training sequence codes are entered on a single line with one space separating each value. This prompt does not appear when equipping the RTF to an M-Cell site. 0 = Outer zone 1 = Inner zone This prompt appears only for NON-BCCH carriers and only if the Concentric Cells feature is unrestricted. Only prompted when Concentric Cells feature is enabled. Only prompted for inner zone carriers. Only prompted for outer zone carriers. Only prompted when the Extended Range Cell feature is unrestricted. The system displays this prompt for outer zone carriers (cell_zone = 0) only. The system displays this prompt if: for outer zone carriers (cell_zone = 0) only, and sdcch_load is not set to 0 ( 0).

Enter KSW pair that manages this carrier: Enter cell zone:

0 - 3

None

0 or 1

Enter TRX transmit power reduction:

same value as max_tx_bts 0 - 4

Enter the number of extended range timeslots allowed:

Enter SDCCH load

0 - 2

Enter SDCCH placement priority:

0 - 250

Enter channel allocation priority: Enter the packet radio capability:

Y N

0 - 250 0 - 3, or None, 16 K, 32 K, 64 K 0 (None) This prompt only occurs if the GPRS feature is unrestricted and if it is an outer zone carrier. For a complete description of this parameter, refer to Chapter 8 Device/Function parameters. This prompt only occurs if the VersaTRAU (VT) feature is unrestricted. Continued

Enter the rtf_ds0_count:

3 - 8

68P02901W23-S

2-63 Nov 2009

RTF

Chapter 2: Equipping the CM database

Prompt Enter the value for Half Rate enabled:

Optional

Range 0 or 1

Default 0

Comments This prompt only occurs at Half Rate capable BTSs such as M-Cell2, M-Cell6, Horizonmacro and Horizon II macro, if AMR and/or GSM HR are/is unrestricted. This prompt only occurs at Half Rate capable BTSs such as M-Cell2, M-Cell6, Horizonmacro, and Horizon II macro when half_rate_enabled is set to 1.

Is 8 kbit/s TRAU allowed (yes/no):

Y or N

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

2-64

68P02901W23-S Nov 2009

Chapter

3
Device/function related commands

Device/function commands are commands that can be entered at the MMI to create, modify, display, delete devices and functions within the BSS. This chapter contains relevant information on device related and function related commands, together with individual descriptions for the following types of Man Machine Interface (MMI) commands: Maintenance (Fault Management) System Change Control (Configuration Management) Call Processing Miscellaneous

NOTE
Statistical commands are described in Chapter 5 Statistics commands.

68P02901W23-S Nov 2009

3-1

Command reference presentation

Chapter 3: Device/function related commands

Command reference presentation

The individual MMI command descriptions are presented in alphabetical order in the following command reference layout: Command title - the actual command reference which appears at the head of the page, and in the contents and the index of this manual. Description - provides a description of the MMI command function and includes: Security level - the access security level for the command. Supported by OMC-R GUI - whether the command is supported at the OMC-R GUI. Command type - whether type A (no operator actions) or type B. Prerequisites - conditions that must be met or exist for the command to be accepted. Operator actions - actions required by the operator for type B commands. If no actions are required, this field is not shown. Format - includes the input command: Syntax - the structure of the command and input parameter string. Input parameters - descriptions of each command input parameter. Examples - provides various examples of command input and the expected response. References - includes where appropriate: Related information - any relevant information, such as command prompts, specific responses. Related commands - any commands that are related.

3-2

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Device-related commands

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

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

Table 3-1
Literal ABSS AXCDR BSS BSP BTP CAB CAGE CBL CBUS CELL CIC COMB CSFP DHP DPROC DRI DYNET EAS

Device literals and descriptions

Description Associated Base Station Substation Associated RXCDR Base Station Substation Base Site Processor (at BSC) Base Transceiver Processor (at BTS) Cabinet Cage Cell Broadcast Link Clock Bus Cell Circuit Identity Code Combiner Code Storage Facility Processor (at BSC or BTS) Digital radio Host Processor Data Processor board (GPRS) Digital Radio Interface Dynamic Network of BTSs External Alarm System Ethernet port Gb Link (GPRS) Generic Clock GPRS Data Stream (GPRS) Generic Processor Continued

{26740/28351} ETH GBL GCLK GDS GPROC

68P02901W23-S

3-3 Nov 2009

Devices and commands

Chapter 3: Device/function related commands

Table 3-1
Literal GPROC2 GPROC3 GSL KSW LAN LMTL MMS MPRT MSI MTL OML OPL PATH PBUS PCHN PCU

Device literals and descriptions (Continued)

Description Generic Processor 2 Generic Processor 3 GPRS Signaling Link (GPRS) Kilo-port Switch Local Area Network Location Message Transfer Link 1.544/2.048 Mbit/s link on an MSI board 1.544/2.048 Mbit/s Port 1.544/2.048 Mbit/s Interface board Message Transfer Link Operations and Maintenance Link OPtimization Link Path Processor (MCAP) Bus Physical Channel PCU Device (GPRS) Packet Subrate Interface PCU System Processor (GPRS) Radio System Link (Abis) Serial Bus BSC or BTS TDM Bus Time Division Multiplex RXCDR to BSC fault management Link

{26740} PSI PSP RSL SBUS SITE TBUS TDM XBL

Devices and commands

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

3-4

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Devices and commands

Table 3-2
Device BSP

Device and command relationship

Commands Affected equip, unequip, unlock_device, state, disp_equipment, device_audit lock_device, ins_device, reset_device Notes disp_equipment includes Hardware Version Number (HVN). Cause a hard reset of the device. disp_equipment includes HVN. Cause a hard reset of the device.

BTP

equip, unequip, unlock_device, state, disp_equipment, device_audit lock_device, ins_device, reset_device

CAB CAB(PCU) CAGE CAGE (PCU) CBL

equip, state, disp_equipment state equip, state, disp_equipment equip, state, disp_equipment, device_audit, cage_audit equip, unequip, lock_device, unlock_device, state, disp_equipment, ins_device, reset_device state state equip, unequip, lock_device, unlock_device, state, disp_equipment, ins_device, reset_device, shutdown_device equip, unequip, lock_device, unlock_device, state, disp_equipment, ins_device, reset_device, swap_devices state, disp_equipment equip, unequip, lock_device, unlock_device, ins_device, reset_device Valid for BSC and InCell BTS. Valid for BSC and InCell BTS disp_equipment includes HVN. Valid for GPRS only. Valid for BSC only. Valid for GPRS only. Valid for BSC and InCell BTS. Valid for GPRS only. Valid for BSC only.

CBUS CELL CIC

Valid for BSC and InCell BTS.

COMB

CSFP

DHP

equip, unequip, lock_device, unlock_device, state, disp_equipment, ins_device, reset_device, device_audit equip, unequip, lock_device, unlock_device, state, disp_equipment, ins_device, reset_device, device_audit equip, unequip, lock_device, unlock_device, state, disp_equipment, ins_device, reset_device, device_audit, shutdown_device

DPROC

DRI

disp_equipment includes HVN.

Continued

68P02901W23-S

3-5 Nov 2009

Devices and commands

Chapter 3: Device/function related commands

Table 3-2
Device EAS

Device and command relationship (Continued)

Commands Affected equip, unequip, lock_device, unlock_device, state, disp_equipment, ins_device, reset_device lock_device, unlock_device, state, disp_equipment, ins_device equip, unequip, lock_device, unlock_device, state, disp_equipment, ins_device, reset_device equip, unequip, lock_device, unlock_device, state, disp_equipment, ins_device, reset_device, swap_devices, device_audit equip, unequip, lock_device, unlock_device, state, disp_equipment, ins_device, reset_device equip, unequip, unlock_device, state, disp_equipment, device_audit Valid for GPRS only. Notes

{26740/28351} ETH GBL

GCLK

Valid for BSC and InCell BTS. disp_equipment includes HVN. Valid for GPRS only.

GDS

GPROC

Valid for BSC and InCell BTS. disp_equipment includes HVN. Valid for BSC and InCell BTS. Cause a hard reset of the device. Valid for BSC and InCell BTS. disp_equipment includes HVN. Valid for BSC and InCell BTS. Cause a hard reset of the device. Valid for BSC and InCell BTS. disp_equipment includes HVN. Valid for BSC and InCell BTS. Cause a hard reset of the device. GPRS only.

lock_device, ins_device, reset_device

GPROC2

equip, unequip, unlock_device, state, disp_equipment, device_audit

lock_device, ins_device, reset_device

GPROC3

equip, unequip, unlock_device, state, disp_equipment, device_audit

lock_device, ins_device, reset_device

GSL

equip, unequip, lock_device, unlock_device, state, disp_equipment, ins_device, reset_device

Continued

3-6

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Devices and commands

Table 3-2
Device KSW

Device and command relationship (Continued)

Commands Affected equip, unequip, unlock_device, state, disp_equipment, device_audit, ins_device Notes Valid for BSC and InCell BTS. disp_equipment includes HVN. Valid for BSC and InCell BTS. Cause a hard reset of the device. Valid for BSC and InCell BTS.

lock_device, reset_device

LAN MMS MPRT MSI

state, swap_devices lock_device, unlock_device, state, disp_equipment, ins_device, reset_device shutdown_device equip, unequip, lock_device, unlock_device, state, disp_equipment, ins_device, device_audit reset_device

Valid for BSC only. disp_equipment includes HVN. Causes a hard reset of the device. Valid for BSC only.

MTL

equip, unequip, lock_device, unlock_device, state, disp_equipment, ins_device, reset_device, shutdown_device equip, unequip, lock_device, unlock_device, state, disp_equipment, ins_device, reset_device equip, unequip, lock_device, unlock_device, state, disp_equipment, ins_device, reset_device equip, unequip, lock_device, unlock_device, state, disp_equipment, ins_device, reset_device state state, lock_device, unlock_device, ins_device, reset_device equip, unequip, lock_device, unlock_device, state, disp_equipment, ins_device, reset_device site_audit, base_ip_address lock_device, unlock_device, state, disp_equipment, reset_device, base_ip_address equip, unequip, lock_device, unlock_device, state, disp_equipment, reset_device, ins_device, device_audit, chg_audit_sched, modify_value, query_audits, tdm_ts_blocks

OML

Valid for BSC only.

OPL

Valid for BSC only.

PATH

Valid for BSC only.

PBUS PCHN PCU

Valid for BSC and InCell BTS.

Valid for GPRS only.

{26740/28351} PPROC {26740} PSI

Continued

68P02901W23-S

3-7 Nov 2009

Devices and commands

Chapter 3: Device/function related commands

Table 3-2
Device PSP RSL RSL SBUS SITE

Device and command relationship (Continued)

Commands Affected equip, state, disp_equipment, device_audit, unequip lock_device, unlock_device, state, disp_equipment, ins_device, reset_device equip, unequip state equip, unequip, lock_device, unlock_device, state, disp_equipment, ins_device, reset_device state state, swap_devices, device_audit equip, unequip, lock_device, unlock_device, state, disp_equipment, ins_device, reset_device Valid for BSC only. Valid for BSC and InCell BTS. Valid for BSC only. Notes Valid for GPRS only.

TBUS TDM XBL

Valid for BSC and InCell BTS. Valid for BSC and InCell BTS. Valid for BSC only.

3-8

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Device identifiers

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

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

Table 3-3

Device ID requirements
Range Definition Associated Base Station Processor 0 - 254 0 0 Corresponds to the BSS network entity that this device represents. Serves as place holder. Serves as place holder. Associated XCDR 0 - 254 0 0 Corresponds to the RXCDR network entity that this device represents. Serves as place holder. Serves as place holder. BSS Controller Unit Power Supply per cage. 0 - 15 0 - 2 0 Identifies the cage number. Identifies which power supply (of the three possible per cage). Serves as place holder. Base Site Processor, BSC 0 or 1 0 0 Identifies which BSP board is active and which is redundant (standby). (None at a BTS.) Serves as place holder. Serves as place holder. Base Station System 0 - 254 0 0 Identifies BSS. Serves as place holder. Serves as place holder. Base Transceiver Processor, BTS Continued

Device Names/IDs ABSS device ID 1 device ID 2 device ID 3 AXCDR device ID 1 device ID 2 device ID 3 BCUP device ID 1 device ID 2 device ID 3 BSP device ID 1 device ID 2 device ID 3 BSS device ID 1 device ID 2 device ID 3 BTP

68P02901W23-S

3-9 Nov 2009

Device ID requirements

Chapter 3: Device/function related commands

Table 3-3

Device ID requirements (Continued)

Range 1 0 0 Definition Identifies which BTP board is active and which is redundant (standby). (None at a BSC or RXCDR.) Serves as place holder. Serves as place holder. CABinet 0 - 20 0 0 Identifies cabinet number. Serves as place holder. Serves as place holder. CAGE 0 - 15 0 0 Identifies the value at which the LANX card, dial is set. Serves as place holder. Serves as place holder. Cell Broadcast Link 0 0 0 Optional entry. (None at a BTS or RXCDR.) Serves as place holder. Serves as place holder. Clock BUS 0 - 15 0 or 1 0 Identifies the cage where a specific GCLK is located. Identifies the GCLK. Serves as place holder. COMBiner 0 - 13 0 or 1 0 Identifies specific combiner cavities (13 active, 13 standby). (None at an RXCDR.) Identifies each individual processor in a combiner unit (of the two present within a redundant pair). Serves as place holder. Code Storage Facility Processor 10 0 0 CSFP identifier (only at a BSC) - not M-Cell, automatically equipped/unequipped. Serves as place holder. Serves as place holder. Digital radio Host Processor, BTS 0 - 5 Identifies a digital module shelf (cage number) in a specific cabinet. (None at an RXCDR.) Continued

Device Names/IDs device ID 1 device ID 2 device ID 3 CAB device ID 1 device ID 2 device ID 3 CAGE device ID 1 device ID 2 device ID 3 CBL device ID 1 device ID 2 device ID 3 CBUS device ID 1 device ID 2 device ID 3 COMB device ID 1 device ID 2 device ID 3 CSFP device ID 1 device ID 2 device ID 3 DHP device ID 1

3-10

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Device ID requirements

Table 3-3

Device ID requirements (Continued)

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

Device Names/IDs device ID 2 device ID 3 DPROC device ID 1 device ID 2 device ID 3 DRI device ID 1

device ID 2 device ID 3 EAS device ID 1 device ID 2 device ID 3 GBL device ID 1 device ID 2 device ID 3 GCLK device ID 1

0 - 11 0

0 device ID 2 device ID 3 GDS device ID 1 device ID 2 device ID 3 GPROC 0 0

68P02901W23-S

3-11 Nov 2009

Device ID requirements

Chapter 3: Device/function related commands

Table 3-3

Device ID requirements (Continued)

Range 0 - 111 0 0 Definition Identifies a specific GPROC board. Serves as place holder. Serves as place holder. GPRS Signaling Link (GPRS) 0 - 59 0 0 Identifies a specific GPRS signaling link. Serves as place holder. Serves as place holder. Kiloport SWitch 0 - 3 0 or 1 0 Identifies a section (timeslot) of TDM highway. M-Cell not applicable. Identifies which KSW board (highway, A side, or B side) is active and which is redundant (standby). (0 is slot 27 and 1 is slot 1.) Serves as place holder. Local Area Network 0 or 1 0 0 Identifies which LAN board (A side or B side) is active and which is redundant (standby). Serves as place holder. Serves as place holder. The E1 Mbit/s line on a Multiple Serial Interface board. {22169} 0 - 95 9 3 1 0 0 or 1 0 Matches the first ID of the host MSI with 0 - 95 for BSC and 0 - 123 for 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 Identifies a specific MSI board: BSC RXCDR BTS only: not M-Cell BTS only: M-Cell6 BTS only: M-Cell2 BTS only: M-Cellmicro Serves as place holder. Serves as place holder. Message Transfer Link Continued

Device Names/IDs device ID 1 device ID 2 device ID 3 GSL device ID 1 device ID 2 device ID 3 KSW device ID 1 device ID 2 device ID 3 LAN device ID 1 device ID 2 device ID 3 MMS device ID 1

device ID 2 device ID 3 MSI device ID 1

0 - 95 0 - 71 9 3 1 0 device ID 2 device ID 3 MTL 0 0

3-12

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Device ID requirements

Table 3-3

Device ID requirements (Continued)

Range 0 - 15 0 0 Definition Identifies a specific MTP link (per ITU-TSS spec). Serves as place holder. Serves as place holder. Operations and Maintenance Link 0 - 3 0 0 Identifies a specific connection (link) between the BSC and the OMC-R (BSC or RXCDR). Serves as place holder. Serves as place holder. OPtimization Link 0 - 3 0 0 Identifies a specific connection (link) between the BSC and the IOS platform. Serves as place holder. Serves as place holder.

Device Names/IDs device ID 1 device ID 2 device ID 3 OML device ID 1 device ID 2 device ID 3 OPL device ID 1 device ID 2 device ID 3 PATH device ID 1 device ID 2 device ID 3 PBUS device ID 1 device ID 2 device ID 3 RSL device ID 1 device ID 2

0 - 140 0 - 9 0

Identifies the terminating site (BSC only). Identifies a unique PATH ID. Serves as place holder. Processor (MCAP) BUS

0 - 15 0 or 1 0

Identifies the cage at that location. Identifies which PBUS (A side or B side) is active and which is redundant (standby). Serves as place holder. Radio System Link

0 - 140 0 - 7 5 1 0

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 3 RTF device ID 1 device ID 2 device ID 3 RXCDR device ID 1 device ID 2

0 - 5 0 - 11 0

Identifies the cell group. Identifies a unique function within the cell group. Serves as place holder. Remote transcoder

0 - 254 0 Serves as place holder. Continued

68P02901W23-S

3-13 Nov 2009

Device ID requirements

Chapter 3: Device/function related commands

Table 3-3

Device ID requirements (Continued)

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

Device Names/IDs device ID 3 SITE device ID 1 device ID 2 device ID 3 SBUS device ID 1 device ID 2 device ID 3 TBUS device ID 1 device ID 2 TDM device ID 1 device ID 2 device ID 3 XBL device ID 1 device ID 2 device ID 3

3-14

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Function related commands

The function-related commands that affect the functions are listed in Table 3-4. The first column gives the function literal. The second column gives the function name. The remaining columns show the commands that are supported for each function.

Table 3-4
Literal LCF OMF

Function related commands

Device name / description Link Control Function, BSC Operation and Maintenance Function, BSC Receive Transmit Function Receive Function Transmit Function Commands unequip X X equip X X state X X disp_equipment X X

RTF RXF TXF

X X X

68P02901W23-S

3-15 Nov 2009

Function identifiers

Chapter 3: Device/function related commands

Function identifiers

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

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

Table 3-5
Device Names / IDs BTF

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

function ID 1

function ID 2 function ID 3 LCF function ID 1 function ID 2 function ID 3 OMF function ID 1 function ID 2 function ID 3 RTF function ID 1 function ID 2 function ID 3

3-16

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Slots

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

Valid slots table

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

Table 3-6
Device BSP

Valid slots
BSS cage = 0 slot = 20 or 24 or cage = 1 slot = 20 N/A BSC cage = 0 slot = 20 or 24 or cage = 1 slot = 20 N/A BTS N/A RXCDR cage = 0 slot = 25 or 26 or cage = 1 slot = 25 N/A

BTP

cage = 15 slot = 20 or 24 or cage = 14 slot = 20 18 - 25 cage 2 - 15 18 - 25 cage 2 - 15 7, 9, 11, 13, 15, 17 15 - 18 (daughter slots) device_id1 = 0 slot = 5 or device_id1 = 1 slot = 3 18 - 25 cage 2 - 15 MSI type = 0 slot = 6 - 17 or MSI type = 1, 255 (slot = N/A)

CSFP DHP DRI EAS GCLK

18 - 25 cage 0 - 13 18 - 25 cage 0 - 13 7, 9, 11, 13, 15, 17 15 - 18 (daughter slots) device_id1 = 0 slot = 5 or device_id1 = 1 slot = 3 18 - 25 cage 0 - 13 6 - 17

18 - 25 cage 0 - 13 N/A N/A 15 - 18 (daughter slots) device_id1 = 0 slot = 5 or device_id1 = 1 slot = 3 18 - 25 cage 0 - 13 6 - 17

25 or 26 cage 0 - 13 N/A N/A 15 - 18 (daughter slots) device_id1 = 0 slot = 5 or device_id1 = 1 slot = 3 25 or 26 cage 0 - 13 MSI type = 0 slot = 6 - 10 or MSI type = 1, 255 slot = 6 - 24

GPROC MSI

68P02901W23-S

3-17 Nov 2009

equip/unequip command matrix

Chapter 3: Device/function related commands

equip/unequip command matrix

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

Table 3-7
Device/ Function BSP BTP CAB

Equip/Unequip command matrix

Equip in SYSGEN Supported Supported Supported Equip outside SYSGEN Supported Supported Type B command: lock the site before entering the equip or unequip commands. Type B command: lock the site before entering the equip or unequip commands. Supported Supported Supported Supported Supported Supported Supported Supported Supported Supported Supported Unequip in SYSGEN Supported Supported Unsupported Unequip outside SYSGEN Supported only if standby device. Supported only standby device. Unsupported

CAGE

Supported

Unsupported

CBL COMB CSFP DHP DRI EAS GCLK GPROC KSW LCF MSI

Supported Supported Supported Supported Supported Supported Supported Supported Supported Supported Supported

Supported Supported Supported Supported Supported Supported Supported Supported Supported

Unequip LCF is only supported if no sites exist on the LCF. Supported Supported

NOTE
The equip/unequip commands do not support the MSIs of type NIU2 (that is, an MSI at a Horizon II site). MTL OMF OML Supported Supported Supported Unsupported Supported Unsupported Supported Supported Supported Supported Unsupported Supported Continued 3-18 68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

equip/unequip command matrix

Table 3-7
Device/ Function OPL PATH {26740} PSI RSL RTF SITE XBL

Equip/Unequip command matrix (Continued)

Equip in SYSGEN Supported Supported Supported Supported Supported Supported Supported Equip outside SYSGEN Unsupported Supported Supported Supported Supported Supported Supported Unequip in SYSGEN Supported Supported Supported Supported Supported Supported Supported Unequip outside SYSGEN Supported Supported Supported Supported Supported Supported Supported

68P02901W23-S

3-19 Nov 2009

Alarm devices

Chapter 3: Device/function related commands

Alarm devices

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

Table 3-8

Alarm devices
Valid Alarm Reporting Device YES YES YES YES NO YES YES YES YES YES NO YES YES YES YES YES YES YES YES YES YES YES YES YES YES YES YES YES Valid Alarm Throttle Device NO YES YES YES NO YES NO NO NO NO NO NO YES NO YES YES NO YES NO YES YES YES NO NO NO NO NO YES Continued

Device Name BCUP BSP BSS BTP CAB CAGE CBL CBUS CELL COMB CSFP DHP DRI EAS GCLK GPROC IAS KSW LAN MMS MSI MTL OMC OML OPL PATH PBUS RSL

3-20

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Alarm devices

Table 3-8

Alarm devices (Continued)

Valid Alarm Reporting Device YES YES YES YES YES YES YES YES Valid Alarm Throttle Device NO NO NO NO NO NO YES YES

Device Name SBUS SITE TBUS TDM TRU TSLOT XBL XCDR

68P02901W23-S

3-21 Nov 2009

add_cell

Chapter 3: Device/function related commands

add_cell

Description
The add_cell command adds a cell to the CM database. The add_cell command is invoked with the location and gsm_cell_idparameters. After the command is entered, a series of prompts to define the cell are displayed. The prompted parameters are described in Related information on page 3-25. Different sites can be equipped with various numbers of cells. Only one cell is permitted at an M-Cellcity, Horizonmicro or Horizoncompact site. The system rejects the add_cell command if it is entered for one of these sites, where a cell exists. Sites can have up to six cells. The system rejects the add_cell command if it is entered for a site where six cells exist. This command can be abandoned at any time by entering done in response to any prompt. If a database parameter has a default, the default value can be entered by pressing the RETURN key. If a database parameter has a default value and a value outside the parameter valid range is typed, the system uses the default value. If the database parameter does not have a default value and no value or a value outside the parameter valid range is entered, the command is abandoned, losing any previously entered parameters. Security level Supported by OMC-R GUI Command type Prerequisites Operator actions 4 Yes B (operator actions required) The add_cell command is not allowed at an RXCDR. Reply to prompts as displayed, directly or in a script.

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

Format
Syntax
add_cell <gsm_cell_id> <location> [cell_name]

3-22

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Format

Input parameters
gsm_cell_id Specifies the GSM cell ID for the cell to be added. The format for the GSM cell ID depends on: The system being used (PGSM, EGSM, DCS1800, PCS1900, or GSM850) Whether the seven parameter GSM cell ID format or the four parameter GSM cell ID format has been enabled: Seven parameter format: a b c d e f g Where: a b c d e f g Four parameter format: abc zde f g Where: a b c z d e f g is: first digit of the MCC (Mobile Country Code). second digit of the MCC. third digit of the MCC. first digit of the MNC (Mobile Network Code). second digit of the MNC. third digit of the MNC. LAC (Local Area Code). CI (Cell Identity). is: first digit of the MCC (Mobile Country Code). second digit of the MCC. third digit of the MCC. first digit of the MNC (Mobile Network Code). second digit of the MNC. LAC (Local Area Code). CI (Cell Identity).

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

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

68P02901W23-S

3-23 Nov 2009

Examples

Chapter 3: Device/function related commands

location Specifies the location of the cell: 0 - 140 cell_name The name to be assigned to the Cell ID. The cell name must be entered inside double quotation marks. The cell name can be from one to 31 alphanumeric characters. The dash character can be used as a separator. The underscore character cannot be used as part of the name or as a separator. Double quotation marks cannot be used as part of a cell name. Cell names cannot be equivalent to the following character strings in upper or lower case: all no name defined name not available Entering two consecutive double quotation marks removes the current cell name. If no value is entered for this parameter, the current cell name displays. BTS

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: 5 4 3 2 1 61986 34944 0 is: GSM cell ID. location.

System response
Prompts are displayed for the parameters to define the cell.

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

3-24

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

References

System response
Prompts are displayed for the parameters to define the cell.

Example 3
In this example, a PCS1900 cell with GSM cell ID 5 4 3 7 2 1 61986 34944 is added to the CM database. This example shows the four-parameter GSM cell ID format. add_cell 543 721 61986 34944 0 Where: 543 721 61986 34944 0 is: GSM cell ID. location.

System response
Prompts are displayed for the parameters to define the cell.

References
Related information
Table 3-9 lists the prompts for the add_cell command. Parameters are assigned by entering the parameter value only, or the contents of the input column of the add_cell command prompts table exactly as presented, where x is the parameter value. For example, a CRM wait indication parameter value of 5 can be assigned by entering the following at the prompt: wait_indication_parameters=5 The word odd in the Range column indicates that only odd values are accepted. Similarly, the word even indicates that only even values are accepted. If a parameter has a default value, the default value can be entered for the parameter by pressing the RETURN key. If the parameter has a default value and an invalid value is entered, an error message is presented and the parameter is assigned the default value. If a parameter does not have a default value and the response to the prompt is not correct, or if no response to the prompt is entered, the system aborts the add_cell command and displays the system prompt. All values entered to that point are lost and must be re-entered if the cell is to be added using the add_cell command. There is a time limit of 30 seconds in which to enter a response to a prompt. If a proper response is not entered within the time limit, the command aborts and all values entered up to that point are lost. To abort the command manually, type done after any prompt.

68P02901W23-S

3-25 Nov 2009

References

Chapter 3: Device/function related commands

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

Table 3-9

add_cell command prompts

Prompt Input bsic=x frequency_type=x Range 0 - 63 1 (pgsm) 2 (egsm) 4 (dcs1800) 8 (pcs1900) 16 (gsm850) Use numeric values or text string. 0 - 255 0, 1, 2, 4, or 6 0 - 7 0 - 7 Default None None

Enter base station identity code: Enter the Frequency Type:

Enter wait indication parameters: Enter common control channel configuration: Enter blocks reserved for access grant: Enter multiframes between transmissions of paging messages: Enter extended paging active: Enter number of SDCCHs preferred:

wait_indication_parameters=x ccch_conf=x bs_ag_blks_res=x bs_pa_mfrms=x

5 0 0 0

extended_paging_active=x number_sdcchs_preferred=x

0 or 1 4 - 44 (if ccch_conf=1) 8 - 48 (if ccch_conf1) 0 or 1 0 - 2 0 - 3 1 - 16 -63 to 63 2 - 64

0 8

Enter enable incoming handover: Enter intra cell handover allowed: Enter inter cell handover allowed: Enter number of preferred cells: Enter handover margin default: Enter handover recognized period:

en_incom_ho=x intra_cell_handover_allowed=x inter_cell_handover_allowed=x number_of_preferred_cells=x ho_margin_def=x handover_recognized_period=x

1 1 1 16 8 2

Continued

3-26

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

References

Table 3-9

add_cell command prompts (Continued)

Prompt Input ul_rxqual_ho_allowed=x dl_rxqual_ho_allowed=x ul_rxlev_ho_allowed=x dl_rxlev_ho_allowed=x sdcch_ho=x sdcch_timer_ho=x interfer_ho_allowed=x pwr_handover_allowed=x ms_distance_allowed=x mspwr_alg=x Range 0 or 1 0 or 1 0 or 1 0 or 1 0 or 1 1 - 31 0 or 1 0 or 1 0 or 1 0 or 1 Default 1 1 1 1 1 1 1 1 0 0

Enter uplink rxqual handover allowed: Enter downlink rxqual handover allowed: Enter uplink rxlev handover allowed Enter downlink rxlev handover allowed: Enter alternate flag for SDCCH handover: Enter alternate SDCCH handover timer value: Enter interference handover allowed: Enter power handover allowed: Enter MS distance allowed: Enter alternate flag for MS power control processing: Enter handover power level: Enter power control indicator for hopping through BCCH: Enter interference measurement averaging period (intave): Enter timing advance period: Enter MS power control period: Enter MS timeout for MS power control: Enter MS power control allowed: Enter BTS power control interval: Enter BTS timeout for BTS power control: Enter BTS power control allowed:

handover_power_level=x pwrc=x

2 - 19 0 or 1

None 1

intave=x

1 - 31

timing_advance_period=x ms_p_con_interval=x ms_p_con_ack=x ms_power_control_allowed=x bts_p_con_interval=x bts_p_con_ack=x bts_power_control_allowed=x

1 - 31 0 - 31 0 - 31 0 or 1 0 - 31 0 - 31 0 or 1 (0 for M-Cellmicro)

4 2 2 1 2 1 0

Continued

68P02901W23-S

3-27 Nov 2009

References

Chapter 3: Device/function related commands

Table 3-9

add_cell command prompts (Continued)

Prompt Input pow_inc_step_size_ul=x pow_inc_step_size_dl=x pow_red_step_size_ul=x pow_red_step_size_dl=x dyn_step_adj=x dyn_step_adj_fmpr=x max_tx_bts=x Range 2 - 14 EVEN 2 - 14 EVEN 2 - 4 EVEN 2 - 4 EVEN 0 or 1 0 - 10 0 - 21 (0 - 6 for M-Cellmicro) 5 - 39 odd only (PGSM or EGSM). 0 - 36 even only (DCS1800). 0 - 32 even only, and 33 (PCS1900). 0 - 63 5 - 39 odd only (PGSM or EGSM). 0 - 36 even only (DCS1800). 0 - 32 even only, and 33 (PCS1900). 0 - 31 0 - 3 0 - 3 0 - 3 0 - 3 0 - 3 1 - 31 1 - 31 Default 2 2 2 2 0 10 0

Enter power increment step size for uplink: Enter power increment step size for downlink: Enter power reduction step size for uplink: Enter power reduction step size for downlink: Enter dynamic step adjust algorithm: Enter factor of maximum power reduction: Enter maximum BTS transmit power: Enter maximum transmit MS:

max_tx_ms=x

39 36 33

Enter receive level minimum default: Enter MS transmit power maximum default:

rxlev_min_def=x ms_txpwr_max_def=x

15 39 36 33

Enter decision algorithm number: Enter decision alg 1 dl rxlev avg h: Enter decision alg 1 dl rxlev avg ih: Enter decision alg 1 dl rxlev avg p: Enter decision alg 1 dl rxqual avg h: Enter decision alg 1 dl rxqual avg p: Enter decision alg 1 n1: Enter decision alg 1 n2:

decision_alg_type=x decision_1_dl_rxlev_av_h =x decision_1_dl_rxlev_av_ih =x decision_1_dl_rxlev_av_p =x decision_1_dl_rxqual_av_h =x decision_1_dl_rxqual_av_p =x decision_1_n1=x decision_1_n2=x

0 0 0 0 0 0 1 1 Continued

3-28

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

References

Table 3-9

add_cell command prompts (Continued)

Prompt Input decision_1_n3=x decision_1_n4=x decision_1_n5=x decision_1_n6=x decision_1_n7=x decision_1_n8=x decision_1_ncell_rxlev_av_h_calc =x decision_1_p1=x decision_1_p2=x decision_1_p3=x decision_1_p4=x decision_1_p5=x decision_1_p6=x decision_1_p7=x decision_1_p8=x decision_1_p_bgt_rxlev_av_h =x decision_1_tim_adv_av_alg =x decision_1_ul_rxlev_av_h =x decision_1_ul_rxlev_av_ih =x decision_1_ul_rxlev_av_p =x decision_1_ul_rxqual_av_h =x decision_1_ul_rxqual_av_p =x alt_qual_proc=x Range 1 - 31 1 - 31 1 - 31 1 - 31 1 - 31 1 - 31 0 - 3 1 - 31 1 - 31 1 - 31 1 - 31 1 - 31 1 - 31 1 - 31 1 - 31 0 - 3 0 - 3 0 - 3 0 - 3 0 - 3 0 - 3 0 - 3 0 or 1 Default 1 1 1 1 1 1 0 1 1 1 1 1 1 1 1 0 0 0 0 0 0 0 0

Enter decision alg 1 n3: Enter decision alg 1 n4: Enter decision alg 1 n5: Enter RSS decision alg 1 n6: Enter RSS decision alg 1 n7: Enter RSS decision alg 1 n8: Enter decision alg 1 ncell rxlev avg h calc: Enter decision alg 1 p1: Enter decision alg 1 p2: Enter decision alg 1 p3: Enter decision alg 1 p4: Enter decision alg 1 p5: Enter decision alg 1 p6: Enter decision alg 1 p7: Enter decision alg 1 p8: Enter decision alg 1 power budget rxlev: Enter decision alg 1 timing advance alg: Enter decision alg 1 ul rxlev avg h: Enter decision alg 1 ul rxlev avg ih: Enter decision alg 1 ul rxlev avg p: Enter decision alg 1 ul rxqual avg h: Enter decision alg 1 ul rxqual avg p: Enter quality band processing allowed:

Continued

68P02901W23-S

3-29 Nov 2009

References

Chapter 3: Device/function related commands

Table 3-9

add_cell command prompts (Continued)

Prompt Input l_rxqual_ul_p=x Range If alt_qual_proc = 0, 0 - 1810. If alt_qual_proc = 1, 0 - 7. If alt_qual_proc = 0, 0 - 1810. If alt_qual_proc = 1, 0 - 7. If alt_qual_proc = 0, 0 - 1810. If alt_qual_proc = 1, 0 - 7. If alt_qual_proc = 0, 0 - 1810. If alt_qual_proc = 1, 0 - 7. If alt_qual_proc = 0, 0 - 1810. If alt_qual_proc = 1, 0 - 7. If alt_qual_proc = 0, 0 - 1810. If alt_qual_proc = 1, 0 - 7. 0 - 63 0 - 63 0 - 63 0 - 63 Default 226 BER or 4 QBand

Enter power control threshold l_rxqual_ul_p:

Enter power control threshold l_rxqual_dl_p:

l_rxqual_dl_p=x

226 BER or 4 QBand

Enter power control threshold u_rxqual_ul_p:

u_rxqual_ul_p=x

28 BER or 1 QBand

Enter power control threshold u_rxqual_dl_p:

u_rxqual_dl_p=x

28 BER or 1 QBand

Enter handover threshold l_rxqual_ul_h:

l_rxqual_ul_h=x

453 BER or 5 QBand

Enter handover threshold l_rxqual_dl_h:

l_rxqual_dl_h=x

453 BER or 5 QBand

Enter handover threshold l_rxlev_ul_h: Enter handover threshold l_rxlev_dl_h: Enter handover threshold u_rxlev_ul_ih: Enter handover threshold u_rxlev_dl_ih:

l_rxlev_ul_h=x l_rxlev_dl_h=x u_rxlev_ul_ih=x u_rxlev_dl_ih=x

10 1 45 45

Continued

3-30

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

References

Table 3-9

add_cell command prompts (Continued)

Prompt Input ms_max_range=x Range 0 - 63 (only if ext_range_cell=0). 0 - 219 (if ext_range_cell=1). 0 - 63 0 - 63 0 - 63 0 - 63 0 or 1 0 or 1 0 - 15 0 - 15 0 or 1 0 or 1 0 - 65535 0 or 1 0 - 255 0 - 255 Default None

Enter handover threshold mobile max range:

Enter power control threshold l_rxlev_ul_p: Enter power control threshold l_rxlev_dl_p: Enter power control threshold u_rxlev_ul_p: Enter power control threshold u_rxlev_dl_p: Enter Alternate flag for missing report: Enter Alternate flag for BA allocating process: Enter RSS link fail: Enter link about to fail: Enter Alternate flag for full power RF loss: Enter cell bar access switch: Enter cell bar access class: Enter emergency class switch: Enter report resource TCH full high water mark: Enter report resource TCH full low water mark:

l_rxlev_ul_p=x l_rxlev_dl_p=x u_rxlev_ul_p=x u_rxlev_dl_p=x missing_rpt=x ba_alloc_proc=x link_fail=x link_about_to_fail=x full_pwr_rfloss=x cell_bar_access_switch=x cell_bar_access_class=x emergency_class_switch=x report_resource_tch_f_high_ water_mark=x report_resource_tch_f_low_ water_mark=x

30 30 40 40 0 0 4 2 0 0 0 0 2 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. If report_resource_tch_f_high_water_mark, is greater than report_resource_tch_f_low_water_mark the system rejects the add_cell command. Enter receive level access minimum: Enter uplink dtx preference: Enter IMSI attach detach: rxlev_access_min=x dtx_required=x attach_detach=x 0 - 63 0 - 2 0 or 1 None 2 0 Continued

68P02901W23-S

3-31 Nov 2009

References

Chapter 3: Device/function related commands

Table 3-9

add_cell command prompts (Continued)

Prompt Input ncc_of_plmn_allowed=x max_retran=x ms_txpwr_max_cch=x Range 0 - 255 0 - 3 5 - 39 odd only (PGSM and EGSM). 0 - 36 even only (DCS1800). 0 - 32 even only, and 33 (PCS1900). 0 - 15 0 - 15 0 or 1 0 - 7 0 or 1 0 or 1 0 - 63 0 - 7 0 - 31 0 or 1 0 - 63 0 - 63 1 - 32 Default 255 0 2

Enter NCC of PLMN allowed: Enter maximum retransmissions on RACH: Enter maximum mobile transmit power on CCCH:

Enter tx_integer for RACH retransmit spacing: Enter radio link timeout: Enter MS reestablish allowed: Enter cell reselect hysteresis: EnterC2 cell reselection parameter indicator: Enter C2 cell bar qualify: Enter C2 cell reselection offset: Enter C2 temporary offset: Enter C2 penalty time: Enter rapid power down procedure active: Enter rapid power down trigger threshold: Enter rapid power down level offset: Enter rapid power down averaging period:

tx_integer=x radio_link_timeout=x reestablish_allowed=x cell_reselect_hysteresis=x cell_reselect_param_ind=x cell_bar_qualify=x cell_reselect_offset=x temporary_offset=x penalty_time=x rapid_pwr_down=x rpd_trigger=x rpd_offset=x rpd_period=x

4 4 0 None 0 0 0 0 0 0 45 8 2

Related commands
copy_cell on page 3-179 disp_gsm_cells on page 3-314 del_cell on page 3-192 freq_types_allowed on page 3-417 disp_cell on page 3-241

3-32

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

add_conn

Description
The add_conn command adds MMS connectivity between the RXCDR and the BSS. Connectivity can be added for a maximum of 21 MMSs at a BSC or RXCDR regardless of how many RXCDRs or BSSs are connected. This command allows the operator to specify the E1 connectivity information identifying which RXCDR is associated with the E1 link and the device identity within the RXCDR to which the E1 link is connected. This connectivity information must be specified for each E1 link connecting to an RXCDR. Security level Supported by OMC-R GUI Command type Prerequisites 4 Yes A (no operator action) Enter this command at the BSC or RXCDR only.

Format
Syntax
add_conn <local_mms_id_1> <local_mms_id_2> <network_entity_id> <remote_mms_id_1><remote_mms_id_2>

Input parameters
local_mms_id_1 First identifier of the MMS at the local site. The term local site refers to the site where the command is being entered. local_mms_id_2 Second identifier of the MMS at the local site. network_entity_id The AXCDR or ABSS device identifier that represents the actual RXCDR or BSS with which this MMS is communicating. remote_mms_id_1 First identifier of the MMS at the remote site. The term remote site refers to the site to which the local site is being connected.

68P02901W23-S

3-33 Nov 2009

Example

Chapter 3: Device/function related commands

remote_mms_id_2 Second identifier of the MMS at the remote site. The add_conn command can be executed from either the BSC or RXCDR. Table 3-10 shows the ranges for several input parameters dependent on where the command is executed.

Table 3-10

add_conn valid ranges

Execution location BSC {22169} 0 - 95 0 or 1 1 - 254 0 - 123 0 or 1 RXCDR 0 - 123 0 or 1 1 - 254 {22169} 0 - 95 0 or 1

Input parameter local_mms_id_1 local_mms_id_2 network_entity_id remote_mms_id_1 remote_mms_id_2

Example
This example adds MMS connectivity between BSC MMS 4 1 and RXCDR MMS 9 0 of RXCDR 3, represented by the equipped device AXCDR 3. add_conn 4 1 3 9 0 Where: 4 1 3 9 0 is: local_mms_id_1 local_mms_id_2 network_entity_id remote_mms_id_1 remote_mms_id_2

System response
COMMAND ACCEPTED

References
Related commands
del_conn on page 3-195 disp_conn on page 3-261 mod_conn on page 3-442

3-34

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

add_neighbor

Description
The add_neighbor command adds a GSM or UTRAN neighbor to an existing cell Neighbor Cell List. {31400} Addition of TD-SCDMA neighbor cells is only allowed when TD-SCDMA and GSM interworking feature is enabled (td_enabled set to 1). {33812} The maximum number of TD-SCDMA neighbors per GSM cell is increased from 16 to 32. A GSM cell can have up to 64 GSM neighbors. A maximum of 64 GSM neighbors can be in the BA_BCCH list but only 32 can be effective. A maximum of 32 GSM neighbors can be in the BA_SACCH list and a maximum of 32 GSM neighbors can be in the BA_GPRS list. The neighbor frequency can change from one range to another (with respect to Table 3-11 and Table 3-12) when adding or deleting a neighbor for a particular source cell. Hence the maximum number of neighbors that can be added to a source cell can change depending upon the frequency range of the neighbor cells: If the source frequency type is DCS1800, a neighbor cannot have a frequency type of PCS1900. If the source frequency type is PCS1900, a neighbor cannot have a frequency type of DCS1800. If a DCS1800 neighbor exists in a neighbor list, no PCS1900 neighbors can be added. If a PCS1900 neighbor exists in a neighbor list, no DCS1800 neighbors can be added.

Table 3-11 lists the frequency range and maximum number of neighbors for an EGSM or PGSM source cell.

68P02901W23-S

3-35 Nov 2009

Description

Chapter 3: Device/function related commands

Table 3-11

Neighbor frequency and number with an EGSM or PGSM source cell

Maximum number of neighbors 64 49 64 50 if the source frequency is in the EGSM frequency, that is: 0, 975 1023 17 if the source frequency is in the PGSM frequency, that is: 1 - 124 64 if the source frequency is zero, where the number of EGSM neighbors is less than or equal to 16. 64 if the source frequency is in the EGSM frequency range, where the number of EGSM neighbors is less than or equal to 16. 64 if the source frequency is in the PGSM frequency range, where the number of EGSM frequencies is less than or equal to 17. 64

Neighbor frequency range 1 - 124 975 - 1023 0, 1 - 124 0, 975 - 1023

1 - 124, 975 - 1023 0, 1 - 124, 975 - 1023

512 - 885

Table 3-12 lists the frequency range and maximum number of neighbors for a DCS 1800 source cell.

Table 3-12

Neighbor frequency and number with DCS1800 source cell

Maximum number of neighbors 64 49 17 17 16 17 64

Neighbor frequency range 1 - 124 975 - 1023 0, 1 - 124 0, 975 - 1023 1 - 124 and 975 - 1023 0, 1 - 124 and 975 - 1023 512 - 885

3-36

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Description

The system updates the maximum number of GSM neighbor cells (refer Table 3-11 and Table 3-12). Then check the maximum number of GSM neighbor cells based on the BA_BCCH list and BA_SACCH list options provided in the following table. One or more UTRAN neighbor exists (Yes/No)? Add neighbor to the BA BCCH list (Yes/No)? Yes No No Yes Yes Yes No Yes Add neighbor to the BA SACCH list (Yes/No)? No Yes Yes No Yes Yes Max no. of neighbor cells that can be equipped for BA BCCH list 64 31 31 31 62 Max no. of neighbor cells that can be equipped for BA SACCH list 32 32 64 Max no. of GSM neighbor cells that can be equipped

NOTE
If there are no UTRAN BCCH neighbors, a maximum of 64 BCCH neighbors can be equipped for GSM. Aternatively, if there are one or more UTRAN BCCH neighbors, a maximum of 31 BCCH neighbors can be equipped for GSM. If there are no UTRAN SACCH neighbors, a maximum of 32 SACCH neighbors can be equipped for GSM. Aternatively, if there are one or more UTRAN SACCH neighbors, a maximum of 31 SACCH neighbors can be equipped for GSM.

For UTRAN neighbor cells, when the Enhanced 2G/3G Handover feature is unrestricted, up to 32 UTRAN BCCH neighbors, 32 UTRAN SACCH neighbors and eight Blind Search neighbors can be added per cell. A total of 64 UTRAN neighbors can be created but a maximum of 32 can be on the UTRAN BA_BCCH list only. After the add_neighbor command is entered, a series of prompts are presented where parameters defining the GSM or UTRAN neighbor are entered. The prompted parameters are described in the Related information on page 3-43. The required input parameters depend on whether the neighbor cell is internal to the BSS or external to the BSS. The parameters also depend on whether the neighbor is a GSM, UTRAN, or Blind Search cell. When the source cell is a PGSM or EGSM cell, the maximum number of EGSM and PGSM band neighbor cells allowed is restrained (refer Table 3-11). When the source cell is a DCS1800 or PCS1900 cell, the maximum number of EGSM and PGSM band neighbor cells allowed is restrained (refer Table 3-12).

68P02901W23-S

3-37 Nov 2009

Format

Chapter 3: Device/function related commands

If the Inter_RAT (Radio Access Technology) Handover feature and/or Enhanced 2G/3G Handover feature is unrestricted, this command supports the UTRAN cell identity format. Security level Supported by OMC-R GUI Command type Prerequisites 4 Yes B (operator actions required) To be on the Neighbor Cell List, a cell must be the destination of handovers from the Neighbor List owner. Synchronized handovers are allowed only between cells that are at the same site. For a PGSM or EGSM site, only external neighbor cells with BCCH ARFCNs in the 1 - 124 can be added. For a GSM 850 site, only external neighbor cells with BCCH ARFCNs in the following ranges can be added: 0 - 124 128 - 251 512 - 885, and 975 - 1023. For handovers to UTRAN cells, the Inter-RAT Handover feature and/or the Enhanced 2G/3G Handover feature must be unrestricted. Reply to prompts as displayed, directly or in a script.

Operator action

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

Format
Syntax
add_neighbor <source_cell_id> <neighbor_cell_id> <placement> The cell_name can be used for the neighbor when the neighbor is internal.

Input parameters
source_cell_id GSM cell ID of the cell to which a neighbor cell is to be assigned. The format for the GSM cell ID depends on: The system being used (PGSM, EGSM, DCS1800, PCS1900, GSM 850) Whether the seven parameter GSM cell ID format or the four parameter GSM cell ID format has been enabled. Whether the cell is a UTRAN cell.

The name of the cell created using the cell_name command can be entered in place of the cell_id. When the cell name is entered, insert within double quotation marks.

3-38

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Format

Only PCS1900 and GSM 850 systems can use a three digit MNC. neighbor_cell_id GSM cell ID of the cell being assigned as a neighbor cell. The name of the cell created using the cell_name command can be entered in place of the cell_id. When the cell name is entered, insert within double quotation marks. The cell_name can only be entered in place of the neighbor_cell_id for internal neighbor cells. Only PCS1900 and GSM 850 systems can use a three digit MNC. The string test <num> can be entered for this field where <num> is a value from 1 to 64. This permits test neighbors to be added to the BA_SACCH and/or BA_BCCH lists. When a test neighbor is added, the value entered in the placement field is ignored and the frequency is the only prompted parameter. The system checks the BSIC of the neighbor cell against the ncc_of_plmn value of the source cell. If they are incompatible, the system rejects the command. See the descriptions for bsic on page 6-93 and ncc_of_plmn_allowed on page 6-595 for more information.

NOTE
A cell_name cannot be associated with UMTS neighbor.

placement internal external umts_fdd umts_fdd_blind {31400} umts_tdd The neighbor cell to be added is inside the BSS. The neighbor cell to be added is outside the BSS. The neighbor cell to be added is a UTRAN BCCH or SACCH neighbor. The neighbor cell is a UTRAN Blind Search neighbor. Specifies that the new neighbor is a TD-SCDMA neighbor.

68P02901W23-S

3-39 Nov 2009

Examples

Chapter 3: Device/function related commands

Table 3-13

Prompted Parameters for TD-SCDMA Neighbors

Required Yes Value Definition/Range/Default 10054 - 10121

Prompt {31400} Enter the UTRAN Absolute Radio Freq Chan Number: {31400} Enter the TD-SCDMA cell parameter: {31400} Enter the Time Switched Transmit Diversity Flag: {31400} Enter the Space Code Transmit Diversity Flag:

Yes No

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

Examples
Example 1
In this example, a cell with ID 5 4 3 2 1 61986 34945 is added to the Neighbor Cell List of a cell with ID 5 4 3 2 1 61986 34944. The example demonstrates adding a cell to the Neighbor Cell List that is internal to that neighbor cell. The word, internal follows the second cell ID indicating that the cell being added is internal to, and shares the same BSS of the src_gsm_cell_id. add_neighbor 5 4 3 2 1 61986 34944 5 4 3 2 1 61986 34945 internal Where: 5 4 3 2 1 61986 34944 5 4 3 2 1 61986 34945 internal is: source_cell_id neighbor_cell_id placement

System response
COMMAND ACCEPTED After verification of the command, the MMI prompts for the required parameters to describe the neighbor cell being added (see Table 3-14 in Related information).

3-40

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Examples

Example 2
In this example, a cell with ID 5 4 3 2 1 61986 34944 is added to the Neighbor Cell List of a cell with ID 5 4 3 2 1 71543 12444. The example demonstrates adding a cell to the Neighbor Cell List that is external to that neighbor cell. The word, external follows the second cell ID indicating that the cell being added is external to, and does not share the BSS of the src_gsm_cell_id. add_neighbor 5 4 3 2 1 71543 12444 5 4 3 2 1 61986 34944 external Where: 5 4 3 2 1 71543 12444 5 4 3 2 1 61986 34944 external is: source_cell_id neighbor_cell_id placement

System response
COMMAND ACCEPTED After verification of the command, the MMI prompts for the required parameters to describe the neighbor cell being added (see Table 3-14 in Related information).

Example 3
In this example, a cell with ID 5 4 3 2 1 61986 34945 is added to the internal Neighbor Cell List of a cell with the cell name north-london: add_neighbor north-london 5 4 3 2 1 61986 34945 internal Where: north-london 5 4 3 2 1 61986 34945 internal is: source_cell_name neighbor_id placement

System response
COMMAND ACCEPTED After verification of the command, the MMI prompts for the required parameters to describe the neighbor cell being added (see Table 3-14 in Related information).

68P02901W23-S

3-41 Nov 2009

Examples

Chapter 3: Device/function related commands

Example 4
In this example, a PCS1900 cell with ID 543 721 61986 34945 is added to the internal Neighbor Cell List of a cell with ID 543 721 61986 34944: add_neighbor 543 721 61986 34944 543 721 61986 34945 internal Where: 543 721 61986 34944 543 7211 61986 34945 internal is: source_cell_id neighbor_cell_id placement

System response
COMMAND ACCEPTED After verification of the command, the MMI prompts for the required parameters to describe the neighbor cell being added (see Table 3-14 in Related information).

Example 5
In this example, UTRAN cell ID 4 9 6 2 3 1 1 1 1 is specified as a neighbor of GSM cell ID 0 0 1 0 1 1 4 with all values entered for all parameters. add_neighbor 0 0 1 0 1 1 4 4 9 6 2 3 1 1 1 1 umts_fdd Where: 0010114 496231111 umts_fdd is: GSM cell ID neighbor cell ID placement

System response
Add neighbor to UTRAN BCCH list (Yes/No)? Yes Add neighbor to UTRAN SACCH list (Yes/No)? Yes Enter the UTRAN Absolute Radio Freq Chan Number: 10762 Enter the Scrambling Code: 200 Enter the Diversity Enabled Flag: 1 Enter the UMTS measurement margin: 15 Enter the neighbor measurement avg period: 10 COMMAND ACCEPTED

3-42

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

References

Example 6
In this example, the FDD_ARFCN 10755 is specified as a UTRAN Blind Search neighbor of GSM cell 0 0 1 0 1 1 4. add_neighbor 0 0 1 0 1 1 4 umts_fdd_blind Where: 0010114 umts_fdd_blind is: GSM cell ID placement type

System response
Enter the UTRAN Absolute Radio Freq Chan Number: COMMAND ACCEPTED 10755

Example 7
{31400} This example specifies TD-SCDMA cell 4 9 6 3 2 1 1 1 1 as a neighbor of GSM cell 0 0 1 0 1 1 4 with all values entered for all parameters when TD-SCDMA inter-working is enabled. add_neighbor 0 0 1 0 1 1 4 4 9 6 2 3 1 1 1 1 umts_tdd Where: 0010114 496231111 umts_tdd is: GSM cell ID neighbor cell ID placement type

System response
Enter the UTRAN Absolute Radio Freq Chan Number: 10110 Enter the TD-SCDMA cell parameter: 100 Enter the Time Switched Transmit Diversity Flag: 1 Enter the Space Code Transmit Diversity Flag: 1 COMMAND ACCEPTED

References
Related information
There is a time limit of 30 seconds in which to enter responses to the parameter prompts that are presented. If a proper response is not entered within the time limit, the command is abandoned and all values entered up to that point are lost. 68P02901W23-S 3-43 Nov 2009

References

Chapter 3: Device/function related commands

Table 3-14 lists the add_neighbor command prompts for GSM BA BCCH and SACCH neighbors.

Table 3-14 neighbors.

Prompt

add_neighbor command prompts for GSM BA BCCH and SACCH

Range yes no yes no yes no pgsm, egsm, dcs1800, pcs1900, gsm850. 1 (Yes) 0 (No) 1 - 124 for PGSM, 0 1 - 124, 975 - 1023 for EGSM, 512 - 885 for DCS1800, 512 - 810 for PCS1900. 0 - 63 Default yes yes yes None These three prompts appear only if the Network Controlled Cell Reselection feature (NCCR) is unrestricted. N/A for internal neighbors. Notes

Add neighbor to the BA BCCH list (yes/no)? Add neighbor to the BA SACCH list (yes/no)? Add neighbor to the BAGPRS list (yes/no)? Enter the neighbor cell frequency type:

Enable synchronization: Enter the BCCH frequency number:

0 None A value MUST be entered at this prompt.

N/A for external neighbors N/A for internal neighbors. EGSM BCCH frequencies 0, 975 - 1023 are not available when the egsm_bcch_sd parameter is disabled.

Enter base station identity code (bsic):

None A value MUST be entered at this prompt. 39 for PGSM and EGSM. 36 for DCS1800 33 for PCS1900.

N/A for internal neighbors

Enter MS transmit power maximum:

5 - 39 (odd values only) for PGSM and EGSM, 0 - 36 (even values only) for DCS1800, 0 - 32 (even values only) and 33, for PCS1900. 0 - 63

N/A for internal neighbors

Enter neighbor receive level minimum: Enter neighbor handover margin:

rxlev_min_def of neighbor cell

Required for external neighbors

-63 to 63

ho_margin_def Required for external neighbors. of neighbor Refer to the description cell of the ho_margin_def parameter. Continued

3-44

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

References

Table 3-14 add_neighbor command prompts for GSM BA BCCH and SACCH neighbors. (Continued)
Prompt Enter the power budget surrounding cell hreqave: Enable adjacent channel interference avoidance test?: Enter rxlev difference for adjacent channel interference avoidance test: Enter the power budget algorithm type: Enter the adjacent channel interference detection handover margin: Enter the uplink receive level threshold of the serving cell: Enter the downlink receive level threshold of the serving cell: Enter the qualifying time threshold: Enter the qualifying delay time: Enter the neighbor cell receive level threshold: Range 1 - 31 1 (Yes) 0 (No) -63 to 63 Default 8 0 (No) N/A if Microcell is not purchased. N/A if Microcell is not purchased. This prompt applies if previous answer is 1 N/A if Microcell is not purchased. Notes

1-7 -63 to 63

ho_margin_cell This prompt only appears if pbgt_alg_type=7.

0 - 255

None A value MUST be entered at this prompt. None

N/A if Microcell is not purchased and pbgt_alg_type 0 3 N/A if Microcell is not purchased and pbgt_alg_type 0 3 N/A if Microcell is not purchased and pbgt_alg_type 0 4 N/A if Microcell is not purchased and pbgt_alg_type 0 5 N/A if Microcell is not purchased and pbgt_alg_type 0 5 N/A if Microcell is not purchased and pbgt_alg_type 0 6 N/A if Microcell is not purchased and pbgt_alg_type 0 6 N/A if Microcell is not purchased and pbgt_alg_type 0 6 Continued

0 - 255

0 SACCH periods 0 SACCH periods None A value MUST be entered at this prompt. 0 SACCH periods 0

0 - 255

0 - 63

Enter the delay time:

0 - 255

Enter the handover static offset: Enter the handover dynamic offset:

0 - 127

68P02901W23-S

3-45 Nov 2009

References

Chapter 3: Device/function related commands

Table 3-14 add_neighbor command prompts for GSM BA BCCH and SACCH neighbors. (Continued)
Prompt Enter neighbor congestion handover margin: Range -63 to 63 To disable congestion handovers to this neighbor, set the value to 63 1 (Yes) 0 (No) Default None. A value MUST be entered at this prompt. Notes Value must be less than or equal to the ho_margin_cell of the neighbor cell. This prompt is only presented if directed retry or congestion relief is purchased. N/A when adding internal neighbors. This prompt is only presented if directed retry or congestion relief is purchased. Only prompted if inner_zone_alg for the source cell is set to 2, and the neighbor is being added to the SACCH list. Only prompted if Does the neighbor have a carrier with an interfering frequency? = 1 (yes). Only prompted if Does the neighbor have a carrier with an interfering frequency? = 1 (yes). This prompt is only presented if the Extended Range Cells feature is unrestricted.

Is directed retry allowed at this external neighbor cell?:

Does this neighbor have a carrier with an interfering frequency?

1 (Yes) 0 (No)

Enter the threshold for inner zone handover:

0 - 63

Enter the margin for inner zone handover:

0 - 63

Enter the range of the neighbor cell:

normal extended

Normal

Table 3-15 lists the add_neighbor command prompted parameters for UTRAN BCCH and SACCH neighbors. If the Enhanced 2G-3G feature is restricted, these parameters are not prompted.

Table 3-15 neighbors

Prompt

add_neighbor command prompts for UTRAN BCCH and SACCH

Range Yes or No Yes or No Default Yes Yes Notes The values of the BCCH and SACCH prompts determine the value of the umts_ba_type attribute where: BCCH/SACCH is Yes/No 1, BCCH/SACCH is No/Yes 2, BCCH/SACCH is Yes/Yes 3. Continued

Add neighbor to UTRAN BCCH list (Yes/No)? Add neighbor to UTRAN SACCH list (Yes/No)?

3-46

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

References

Table 3-15 add_neighbor command prompts for UTRAN BCCH and SACCH neighbors (Continued)
Prompt Enter the UTRAN Absolute Radio Freq Chan Number: Enter the Scrambling Code: Range 10562 - 10838 0 - 511 Default None None Notes This sets the fdd_arfcn attribute. This sets the scr_code attribute that indicates the primary scrambling code of the UTRAN neighbor.

Enter the Diversity Enabled Flag: Enter the UMTS measurement margin:

0 or 1 0 - 20

0 3 This sets the umts_meas_margin parameter used by the handover algorithm. This sets the UTRAN neighbor cell measurement averaging period umts_ncell_avg_period attribute.

Enter the neighbor measurement avg period:

1 - 12

Table 3-16 lists the add_neighbor command prompted parameters for Blind Search neighbors.

Table 3-16
Prompt

add_neighbor command prompts for Blind Search neighbors.

Range 10562 - 10838 Default None Notes This sets the bs_fdd_arfcn blind search neighbor attribute. This is not prompted for if the Enhanced 2G-3G feature is restricted.

Enter the UTRAN Absolute Radio Freq Chan Number

When adding UTRAN neighbors, checks are made to ensure the maximum number of UTRAN BCCH and SACCH neighbors has not been reached, the maximum number of UTRAN BCCH and SACCH neighbors per FDD_ARFCN has not been reached and the maximum number of FDD-ARFCN per GSM cell has not been reached.

Related commands
add_cell on page 3-22 del_neighbor on page 3-197 disp_neighbor on page 3-343 copy_cell on page 3-179 disp_cell on page 3-241 modify_neighbor on page 3-447 del_cell on page 3-192 disp_gsm_cells on page 3-314

68P02901W23-S

3-47 Nov 2009

add_nsvc

Chapter 3: Device/function related commands

add_nsvc

Description
The add_nsvc command enables the operator to map a Network Service-Virtual Connection Identifier (NSVCI) and Data Link Connection Identifier (DLCI) to a specific GBL. Security level Supported by OMC-R GUI Command type Prerequisites 4 Yes A (no operator action) The GPRS feature must be unrestricted.

Format
Syntax
add_nsvc <pcu_n> <ns_vci> <gbl_id> <dlci>

Input parameters
pcu_n ns_vci {27955A} pcu or pcu_0 0 - 65535 The PCU at which the NSVCI or DLCI is to be mapped to the specific GBL. The virtual connection on a GBL Unique identifier of the NSVCI mapping and identifier of the object. Object identifier of the GBL Local identifier for a virtual connection on a GBL.

gbl_id dlci

0 - 35 16 - 991

Prompts are then displayed as follows: Enter the Committed Information rate: Enter the Committed Burst Size: Enter the Burst Excess:

3-48

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Example

Example
The following example adds NSVCI 10 to GBL 0 with a DLCI of 50 on PCU 0: add_nsvc pcu_0 10 0 50 Where: pcu_0 10 0 50 is: PCU 0 NSVC GBL ID 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 3-202 mod_nsvc on page 3-445

68P02901W23-S

3-49 Nov 2009

add_rtf_path

Chapter 3: Device/function related commands

add_rtf_path

Description
The add_rtf_path command allows the addition of a redundant PATH device to an equipped RTF function in the CM database. The parameters that identify a particular PATH are location and Unique_PATH_identifier. Adding a redundant path that is shorter than the current path causes a switch to the shorter path. If an RTF path is being added to an RTF with multiplexed 16 k RSLs the system prompts for the identifier of the associated RSL. The system rejects attempts to modify the PATHs used by RTFs at sites that use dynamic allocation. RTFs automatically use the PATHs defined for these types of sites. RTFs do not use PATHs equipped by the operator for these types of sites. Security level Supported by OMC-R GUI Command type Prerequisites 4 Yes A (no operator action) This command can only be executed at the BSC. If no redundant PATH is equipped, then first equip any necessary MSI before equipping the PATH.

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

Format
Syntax
add_rtf_path <location> <1st_RTF_identifier> <2nd_RTF_identifier> <unique_PATH_identifier>

3-50

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Example

Input parameters
location Indicates the number of the BTS where the RTF is located. The range of values is 0 to 140. 1st_RTF_identifier Specifies the first RTF identifier. The range of values is: 2nd_RTF_identifier Specifies the second RTF identifier. The range of values is: 0 to 11 for InCell. 0 or 1 for M-Cell. unique_PATH_identifier Specifies the unique PATH to a particular site. The range of values is 0 to 9.

Example
This example adds a redundant RTF PATH to site 3, RTF identifiers 2 1, unique PATH identifier 1. add_rtf_path 3 2 1 1 Where: 3 2 1 1 is: location 1st_RTF_identifier 2nd_RTF_identifier unique_PATH_identifier

System response
COMMAND ACCEPTED

References
Related commands
copy_path on page 3-187 disp_traffic on page 3-394 del_rtf_path on page 3-204 disp_rtf_path on page 3-381

68P02901W23-S

3-51 Nov 2009

alarm_mode

Chapter 3: Device/function related commands

alarm_mode

Description
The alarm_mode command registers or deregisters the MMI to receive device, non-reconfiguration type, and statistical alarm reports for the specified sites. If no mode is specified, this command displays whether alarms are enabled or disabled. If the location is specified as all from a BSC, alarms for all sites are affected (either displayed, enabled, or disabled). Security level Supported by OMC-R GUI Command type Prerequisites 1 No A (no operator action) The GPRS must be unrestricted to assess a PCU site.

Format
Syntax
alarm_mode <location>[<location>,<location>] [<mode>]

Input parameters
location Specifies the site location: 0 or bsc 0 - 140 {27955A} pcu or pcu_0 mode on off alarm reporting activated alarm reporting deactivated BSC BTS PCU

3-52

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Examples

Examples
Example 1
Specifies alarm mode as On for BSC 0: alarm_mode 0 on

System response
SITE ----0 MODE ----------------------Alarm reporting enabled

Example 2
Specifies alarm mode as Off for PCU site 0: alarm_mode pcu_0 off

System response
SITE ----pcu_0 MODE -----------------------Alarm reporting disabled

68P02901W23-S

3-53 Nov 2009

assess

Chapter 3: Device/function related commands

assess

Description
The assess command displays different types of information, depending on whether a SITE or device is specified, as follows: SITE When a site is specified, information on the status of Functional Units (FUs) and which device types contribute to that status is reported. The information is presented in a concise format that indicates where problems are and what must be done. Only the FUs and device types which have non-CLEAR status are listed. Complete device IDs are not listed. The FU statuses are defined as: MAJOR = Loss of Capacity. MINOR = Loss of Redundancy. CRITICAL = Loss of Service. Device A device can be specified individually, with wild cards, or for all sites. When multiple devices and/or functions have gone OOS (Out Of Service) as part of separate reconfigurations, multiple reports are generated. If multiple reports are generated as part of a single assess command, one report is generated for each active reconfiguration that satisfies the request. For the purposes of this command, active means any reconfiguration with: One or more alarms active against it. One or more devices still OOS. Both active alarms and OOS devices.

Only one report is displayed if wild cards are used and all devices that match the wild cards go OOS as part of the same reconfiguration. Functions are not displayed as an OOS device because there is no maintenance action to perform on a function. Once all devices are restored to an in-service state, the functions must be assigned to the appropriate devices and cease to affect the FUs. Device reports are displayed in the following format: Alarm Device: of Cause: Functional Unit: -- Status: Current Status: -- OOS Devices Affecting Functional Unit: : Outcome:

3-54

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Format

The Alarm Device is the primary alarm for the reconfiguration. The alarm is displayed even if it has been cleared already. An alarm and the alarm device are not displayed for a reconfiguration that does not have an active alarm yet has OOS devices. However, the message No Primary Alarm for this Reconfiguration is displayed. A Functional Unit (and its status) is displayed for each FU which is impacted by the reconfiguration and has a non-CLEAR status at the end of the reconfiguration. The line, OOS Devices Affecting Functional Unit, displays when devices are OOS and are still associated with this reconfiguration. For each device impacting the listed FU, the device ID and state are listed one per line. If the FU no longer has any OOS devices impacting it, the line, No devices remain OOS as a result of this configuration is displayed instead of the previous line.

NOTE
This report does not list a config_tag or a time stamp. This information can be displayed with either the state or disp_act_alarm command.

Security level Supported by OMC-R GUI Command type Prerequisites

1 No A (no operator action) The GPRS feature must be unrestricted to assess a PCU site.

Format
Syntax
assess <location> [all] [<dev/func name> <dev/func id> <dev/func id>] [*]

Input parameters
location Specifies the site location: 0 or bsc 0 - 140 {27955A} pcu or pcu_0 all BSC BTS PCU All active sites

68P02901W23-S

3-55 Nov 2009

Examples

Chapter 3: Device/function related commands

dev/func name Specifies the device or function. dev/func id Specifies the ID for the device or function. The system accepts the wildcard character (*) for the device or function ID.

Examples
Example 1
In the following example, BSC has been initialized. The operator wishes to see if there are any problems at the BSC: assess 0 Where: 0 is: location

System response
SITE / CELL -----------------------SITE 0 BSP OML CBUS SITE 3 RSL CELL 001 01 1 2 DRI DEVICE/FUNCTION --------------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, the operator is concerned about the OMLs contributing to the severity of MAJOR. In this particular scenario, both OMLs have been OOS since site initialization: assess 0 oml 0 Where: 0 oml 0 is: location device name device ID

3-56

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Examples

System response
ASSESS REPORT BEGIN (242) Device(s) OOS due to action on this device Alarm Device: SITE 0 0 0 ENABLE of SITE: 0 0 0 Cause: INITIALIZATION Outcome: Alarm Functional Unit: SITE 0 -- Status: MAJOR OML 0 0 0 OML 0 0 0 -- Status: MINOR Current Status: MAJOR DISABLED UNLOCKED DISABLED UNLOCKED Current Status: MAJOR MMS Not In Service MMS Not In Service -- OOS Devices Affecting Functional Unit:

Functional Unit: SITE 3 -- No devices remain OOS as a result of this configuration Functional Unit: CELL 001 01 1 2 -- Status: MAJOR DRI 1 4 0 ASSESS REPORT COMPLETE Current Status: MINOR DISABLED UNLOCKED DRI Not Detected -- OOS Devices Affecting Functional Unit:

Example 3
The following example shows an assess display for PCU site 0: assess pcu_0 Where: pcu_0 is: location

System response
SITE / CELL ------------------------------------PCU 0 GBL GSL DPROC MSI COMMAND ACCEPTED DEVICE/FUNCTION --------------SEVERITY --------CRITICAL CRITICAL MAJOR MAJOR MAJOR

68P02901W23-S

3-57 Nov 2009

cage_audit

Chapter 3: Device/function related commands

cage_audit

Description
The cage_audit command performs two different functions. The first function allows the execution of safe tests or all audits for all the devices within a specific cage. The second function permits the suspension or resumption of all audits at a specific site. There are only two possible System Responses to a cage_audit command: The display of results. ERROR.

The ERROR response is due to a non-device related cause. An error description is also displayed. Devices listed within the CAGE can also generate messages specific to the device. Security level Supported by OMC-R GUI Command type Prerequisites 4 Yes A (no operator actions) None

NOTE
This command does not work at an M-Cell site. Contact the OMC-R for help.

Format
Syntax
cage_audit <location> <audit_type> <cage_number> cage_audit <location> <control> <cage_number>

3-58

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Examples

Input parameters
location Specifies the audit location: 0 or bsc 0 - 140 {27955A} pcu or pcu_0 audit_type Specifies the type of audit: safe All control Specifies the audit status: on off cage_number Specifies the cage number: 0 - 13 2 - 15 for a BSC for a BTS Resumes all site audits within a cage at a specific site. Suspends all site audits within a cage at a specific site. initiates safe tests initiates all audits BSC BTS PCU

Examples
Example 1
This example executes all audits for all devices for cage 0 at site 0. cage_audit 0 all 0 Where: 0 all 0 is: location audit_type cage_number

68P02901W23-S

3-59 Nov 2009

Examples

Chapter 3: Device/function related commands

System response
Device: KSW Device id: 0 0 0 Month: 11 Day: 12 Hour: 0 Min: 26 Sec: 26 MSec: 495 Result: PASS Day: 12 Hour: 0 in: 26 Sec: 27 MSec: 860

Year: 1994 Device: KSW

Audit Type: SAFE Year: 1994 Device: MSI

Device id: 0 0 0 Month: 11 Result: PASS Day: 12 Hour: 0 Min: 26 Sec: 28 MSec: 630

Audit Type: INT LPBK Year: 1994 Device: MSI Month: 11

Device id: 3 0 0 Result: PASS Day: 12 Hour: 0 Min: 26 Sec: 29 MSec: 665

Audit Type: SAFE Year: 1994 Device: DRI

Device id: 1 0 0 Month: 11 Result: PASS Day: 12 Hour: 0 Min: 26 Sec: 29 MSec: 665

Audit Type: SAFE Year: 1994 Device: GPROC Year: 1994

Device id: 0 1 0 Month: 11 Result: PASS Day: 12 Hour: 0 Min: 26 Sec: 31 MSec: 595

Audit Type: SAFE

Device id: 1 0 0 Month: 11 Result: ERROR

Audit Type: SAFE

ERROR: Audit not available for this device.

Example 2
The following example suspends audits for all devices in cage 9 at site 4: cage_audit 4 off 9 Where: 4 off 9 is: location control cage_number

System response
COMMAND ACCEPTED

3-60

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

References

References
Related commands
chg_audit_sched on page 3-76 site_audit on page 3-507 device_audit on page 3-210 query_audits on page 3-472

68P02901W23-S

3-61 Nov 2009

cell_name

Chapter 3: Device/function related commands

cell_name

Description
The cell_name command assigns a unique name to a Cell ID, renames a cell, or displays the name assigned to a Cell ID. The name can be a text string up to 31 alphanumeric characters in length, including dash characters used for separation. The system does not permit duplicate cell names to be entered. Security level Supported by OMC-R GUI Command type Prerequisites 4 Yes A (no operator actions) A security level of 2 is required to create or modify a cell name.

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

Format
Syntax
cell_name <gsm_cell_id> [<cell_name>]

Input parameters
gsm_cell_id The GSM cell ID of the cell for which the cell name is to be created, displayed, or modified. The format for the GSM cell ID depends on is: The system used (PGSM, EGSM, DCS1800, PCS1900). Whether the seven parameter GSM cell ID format or the four parameter GSM cell ID format has been enabled.

3-62

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Examples

cell_name The name to be assigned to the Cell ID. The cell name must be entered inside double quotation marks. The cell name can be from one to 31 alphanumeric characters. The dash character can be used as a separator. The underscore character cannot be used as part of the name or as a separator. Double quotation marks cannot be used as part of a cell name. Cell names must not be equivalent to the following character strings in upper or lower case: all no name defined name not available

Entering two consecutive double quotation marks removes the current cell name. If no value is entered for this parameter, the current cell name displays.

Examples
Example 1
In this example, the Cell ID 5 4 3 2 1 61986 34944 is assigned the cell name london-west. cell_name 5 4 3 2 1 61986 34944 london-west Where: 5 4 3 2 1 61986 34944 london-west is: cell_number cell_name

System response
COMMAND ACCEPTED:

Example 2
In this example, the cell name assigned to Cell ID 5 4 3 2 1 61986 34944 displays. The cell_name displays inside double quotes. cell_name 5 4 3 2 1 61986 34944 Where: 5 4 3 2 1 61986 34944 is: cell_number

68P02901W23-S

3-63 Nov 2009

Examples

Chapter 3: Device/function related commands

System response
GSM Cell [ 5 4 3 2 1 61986 (f222h) 34944 (8880h) ] = london-west

NOTE
If there is no cell name, the system response is: No textual name exists for this cell

Example 3
In this example, the existing cell name london-west is removed. cell_name 5 4 3 2 1 61986 34944 Where: 5 4 3 2 1 61986 34944 is: cell_number cell_name

System response
COMMAND ACCEPTED

Example 4
In this example, the PCS1900 Cell ID 543 721 61986 34944 is assigned the name london-west. cell_name 543 721 61986 34944 london-west Where: 543 721 61986 34944 london-west is: cell_number cell_name

System response
COMMAND ACCEPTED

3-64

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

chg_acs_params

Description
The chg_acs_params command specifies up to four codec modes to be used in the Active Codec Set (ACS), the initial codec mode, and the uplink and downlink adaptation threshold, and hysteresis values for Full Rate (FR), Half Rate (HR), or both. The term Active Codec Set refers to the set of up to four Adaptive Multi-Rate (AMR) code modes and related thresholds, and hysteresis that can be used for any given voice call in the uplink and downlink directions. The operator configures the ACS on a per cell basis. There are two sets of thresholds and hysteresis per ACS; one for downlink codec mode adaptation and one for uplink codec mode adaptation. The threshold is used as the lower decision threshold for switching between the codec modes. The sum of the threshold and the hysteresis constitutes the upper threshold between the codec modes. There is a separate ACS for Full Rate and Half Rate. The term Adaptive Multi-Rate codec refers to the speech and channel codec capable of operating at gross bit-rates of 11.4 kbits/s (Half-Rate) and at 22.8 kbits/s (Full Rate) over the air interface. Plus, the codec can operate at various combinations of speech and channel coding (codec mode) bit-rate for each channel mode. Security level Supported by OMC-R GUI Command type Prerequisites Dependencies 4 No A (no operator actions) The AMR feature must be unrestricted. The site must be an AMR-capable BTS. Either AMR Full-Rate or Half-Rate must be enabled in the cell for the AMR parameters to come into effect. Parameters can be set before or after the AMR is enabled in the cell. Thus performance is optimized for calls initiated in the cell.

68P02901W23-S

3-65 Nov 2009

Format

Chapter 3: Device/function related commands

Format
Syntax
chg_acs_params <mode> <cell_number=> The system responds with a series of prompts for threshold and hysteresis values (see Table 3-20 and Table 3-21).

NOTE
The sum of the values for threshold and hysteresis must be less than 63.

Input parameters
mode This parameter specifies the rate where: 0 = Full Rate 1 = Half Rate 2 = Both Rates cell_number= This parameter is the GSM cell ID of the cell to be changed. The format for the GSM cell ID depends on: The system used (PGSM, EGSM, DCS1800, PCS1900). Whether the seven parameter GSM cell ID format or the four parameter GSM cell ID format has been enabled.

Only PCS1900 systems can use a three digit MNC. The codec mode values and associated rates are listed in Table 3-17:

Table 3-17

Codec Mode Values / Rates

Codec Mode Value 0 1 2 3 4 5 6 Associated Rate 12.20 kbit/s 10.20 kbit/s 7.95 kbit/s 7.40 kbit/s 6.70 kbit/s 5.90 kbit/s 5.15 kbit/s

3-66

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Format

Full Rate attribute values for the chg_acs_params command are listed in Table 3-18, and the Half Rate attribute values are listed in Table 3-19.

NOTE
The range values 0 - 63 and 0 - 15 in Table 3-18 and Table 3-19 are in steps of 0.5 dB.

Table 3-18

Full Rate attribute values for chg_acs_params command

Attribute Range 0, 1, 3, 4, 6 Default 0, 1, 3, 6 Notes Up to four AMR codec modes which can be used for any given voice call in the uplink or downlink direction. Codec mode used at the beginning of a call. If one mode is entered for the Full Rate ACS, then the Full Rate Initial Codec Mode defaults to this value (if valid). Lower Full Rate uplink decision threshold for switching from one mode to another. The sum of the associated threshold and hysteresis is used as the upper decision threshold for switching the codec mode. Lower Full Rate downlink decision threshold for switching from one mode to another. The sum of the associated threshold and hysteresis is used as the upper decision threshold for switching the codec mode. Uplink switching thresholds applied to frequency hopping channels. Uplink hysteresis applied to frequency hopping channels. Downlink switching thresholds applied to frequency hopping channels. Downlink hysteresis applied to frequency hopping channels.

amr_fr_acs

amr_fr_initial_codec_mode

0, 1, 3, 4, 6

amr_fr_uplink_threshold3 amr_fr_uplink_threshold2 amr_fr_uplink_threshold1 amr_fr_uplink_hysteresis3 amr_fr_uplink_hysteresis2 amr_fr_uplink_hysteresis1

0 - 63 0 - 63 0 - 63 0 - 15 0 - 15 0 - 15

26 20 14 1 1 1

amr_fr_downlink_threshold3 amr_fr_downlink_threshold2 amr_fr_downlink_threshold1 amr_fr_downlink_threshold3 amr_fr_downlink_threshold2 amr_fr_downlink_threshold1

0 - 63 0 - 63 0 - 63 0 - 15 0 - 15 0 - 15

30 24 19 1 1 1

amr_fr_uplink_threshold3_hopping amr_fr_uplink_threshold2_hopping amr_fr_uplink_threshold1_hopping amr_fr_uplink_hysteresis3_hopping amr_fr_uplink_hysteresis2_hopping amr_fr_uplink_hysteresis1_hopping amr_fr_downlink_threshold3_hopping amr_fr_downlink_threshold2_hopping amr_fr_downlink_threshold1_hopping amr_fr_downlink_hysteresis3_hopping amr_fr_downlink_hysteresis2_hopping amr_fr_downlink_hysteresis1_hopping

0 - 63 0 - 63 0 - 63 0 - 15 0 - 15 0 - 15 0 - 63 0 - 63 0 - 63 0 - 15 0 - 15 0 - 15

26 20 14 1 1 1 26 21 14 1 1 1

68P02901W23-S

3-67 Nov 2009

Format

Chapter 3: Device/function related commands

Table 3-19

Half Rate attribute values for chg_acs_params command

Attribute Range 2, 3, 4, 5, 6 Default 3, 5, 6 Notes Up to four AMR codec modes which can be used for any given voice call in the uplink or downlink direction. Codec mode used at the beginning of a call. If one mode is entered for the Half Rate ACS, then the Half Rate Initial Codec Mode defaults to this value (if valid). Lower Half Rate uplink decision threshold for switching from one mode to another. The sum of the associated threshold and hysteresis is used as the upper decision threshold for switching the codec mode. Lower Half Rate downlink decision threshold for switching from one mode to another. The sum of the associated threshold and hysteresis is used as the upper decision threshold for switching the codec mode. Uplink switching thresholds applied to frequency hopping channels. Uplink hysteresis applied to frequency hopping channels. Downlink switching thresholds applied to frequency hopping channels. Downlink hysteresis applied to frequency hopping channels.

amr_hr_acs

amr_hr_initial_codec_mode

2, 3, 4, 5, 6

amr_hr_uplink_threshold3 amr_hr_uplink_threshold2 amr_hr_uplink_threshold1 amr_hr_uplink_hysteresis3 amr_hr_uplink_hysteresis2 amr_hr_uplink_hysteresis1

0 - 63 0 - 63 0 - 63 0 - 15 0 - 15 0 - 15

28 22

1 1

amr_hr_downlink_threshold3 amr_hr_downlink_threshold2 amr_hr_downlink_threshold1 amr_hr_downlink_threshold3 amr_hr_downlink_threshold2 amr_hr_downlink_threshold1

0 - 63 0 - 63 0 - 63 0 - 15 0 - 15 0 - 15

30 24

1 1

amr_hr_uplink_threshold3_hopping amr_hr_uplink_threshold2_hopping amr_hr_uplink_threshold1_hopping amr_hr_uplink_hysteresis3_hopping amr_hr_uplink_hysteresis2_hopping amr_hr_uplink_hysteresis1_hopping amr_hr_downlink_threshold3_hopping amr_hr_downlink_threshold2_hopping amr_hr_downlink_threshold1_hopping amr_hr_downlink_hysteresis3_hopping amr_hr_downlink_hysteresis2_hopping amr_hr_downlink_hysteresis1_hopping

0 - 63 0 - 63 0 - 63 0 - 15 0 - 15 0 - 15 0 - 63 0 - 63 0 - 63 0 - 15 0 - 15 0 - 15

28 22 1 1 30 23 1 1

Full Rate prompts for the chg_acs_params command are listed in Table 3-20, and the Half Rate prompts are listed in Table 3-21.

3-68

68P02901W23-S Nov 2009

Enter up to three downlink threshold values in order of descending C/I estimation. Enter up to three downlink hysteresis values.

Enter AMR Full Rate downlink adaptation hysteresis:

Yes

Enter AMR Full Rate uplink adaptation thresholds for frequency hopping: Enter AMR Full Rate uplink adaptation hysteresis for frequency hopping: Enter AMR Full Rate downlink adaptation thresholds for frequency hopping:

Chapter 3: Device/function related commands

References
Related commands
disp_acs on page 3-223.

3-72

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

chg_a5_alg_pr

Description
The chg_a5_alg_pr command specifies the A5 encryption algorithms in the order in which the BSS uses them. Security level Supported by OMC-R GUI Command type Prerequisites 4 Yes B (operator actions required) The encryption feature must be unrestricted. To include an algorithm in the priority list, it must be enabled with the associated database parameter (option_alg_a5_1 through option_alg_a5_7). The encryption feature must be activated first.

Operator actions

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

Format
Syntax
chg_a5_alg_pr <first_alg> [<second_alg>] [<third_alg>] [<fourth_alg>] [<fifth_alg>] [<sixth_alg>] [<seventh_alg>] [<eighth_alg>]

68P02901W23-S

3-73 Nov 2009

Format

Chapter 3: Device/function related commands

Input parameters
The following values specify the GSM encryption algorithm: Value 0 1 2 3 4 5 6 7 first_alg first algorithm choice (0 - 7) second_alg second algorithm choice (0 - 7) GSM Algorithm No encryption; any algorithms listed after 0 are ignored. A5/1 A5/2 A5/3 A5/4 A5/5 A5/6 A5/7

NOTE
The system uses only the first and second algorithm choices. Values entered for the remaining parameters are ignored.

third_alg third algorithm choice (0 - 7) fourth_alg fourth algorithm choice (0 - 7) fifth_alg fifth algorithm choice (0 - 7) sixth_alg sixth algorithm choice (0 - 7) seventh_alg seventh algorithm choice (0 - 7) eighth_alg eighth algorithm choice (0 - 7)

3-74

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Examples

Examples
Example 1
In this example, the algorithms ordered as follows: A5/1, A5/2: chg_a5_alg_pr 1 2 Where: 1 2 is: A5/1 Algorithm A5/2 Algorithm

System response
COMMAND ACCEPTED

Example 2
In this example, no encryption is used: chg_a5_alg_pr 0 Where: 0 is: no encryption

System response
COMMAND ACCEPTED

References
Related commands
disp_a5_alg_pr on page 3-221 chg_element on page 3-106

68P02901W23-S

3-75 Nov 2009

chg_audit_sched

Chapter 3: Device/function related commands

chg_audit_sched

Description
The chg_audit_sched command schedules audits of selected devices at specified site based on device type and audit type. {25002} The chg_audit_sched is modified to support the swap_test type audit on the TDM device at site 0 (BSC or RXCDR). Audits can run in parallel or in series. Audits of different devices run in parallel, that is, the system can audit different devices at the same time. For example, audits of the DRI and GCLK run in parallel. Audits of similar devices run sequentially that is, the audit of one device must end before the second device audit can begin. For example, the system audits all GPROCs at a site sequentially.

Use the device_audit command to turn off the audits. Security level Supported by OMC-R GUI Command type Prerequisites 4 Yes A (no operator actions) An operator at the OMC-R must rlogin to a site before an audit can be scheduled. Only one audit can be run at a time. If a log exists from a previous audit, it is overwritten with the log created by the current audit.

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

Format
Syntax
{25002} chg_audit_sched <location> <device_name> <audit_type> <start_time_hour> <start_time_min> <end_time_hour> <end_time_min> <interval_hour> <interval_min>

3-76

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Format

Input parameters
location Specifies the audit location: 0 or bsc 1 - 140 {27955A} pcu or pcu_0 device_name Name that uniquely identifies the device. The following devices can be audited at InCell sites using this command: BSP GPROC BTP KSW DHP MSI DRI SITE GCLK TDM BSC BTS PCU

The following devices can be audited at M-Cell sites using this command: BTP DRI MSI SITE

The following devices can be audited at a PCU using this command: DPROC audit_type Type of audit all safe int_lpbk self_test swap_test start_time_hour Start time hour (00 to 23) start_time_min Start time minutes (00 to 59) end_time_hour End time hour (00 to 23) end_time_min End time minutes (00 to 59) interval_hour Value 0 1 2 3 4 Safe tests Internal loopback All Tests Available Locations BSC, BTS, and PCU KSW RXCDR at a remote transcoding BSC BSC and BTS only Expanded cage MSI PSP

68P02901W23-S

3-77 Nov 2009

Format

Chapter 3: Device/function related commands

The interval hour (00 to 23) interval_min The interval minutes (00 to 59)

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 interval time is 0. If the end_time is greater than the start_time, the system schedules the range audits. The interval time is 0.

Range Scheduling

Once-Per-Day Scheduling

The system schedules range audits if: The start_time equals the end_time. The interval time is 00:00.

Device scheduling defaults

Table 3-22 lists the device scheduling defaults.

Table 3-22

Device scheduling defaults

Default schedule continuously every hour from 2:00 am to 4:00 am every 15 minutes continuously every hour continuously every 10 minutes once a day at 1:00 am continuously every 10 minutes continuously every 1 minute continuously every 30 minutes continuously every 10 minutes

Device KSW safe test audit KSW internal loopback audit GCLK safe test audit GPROC safe test audit DHP safe test audit TDM safe test audit BSP safe test audit BTP safe test audit MSI safe test audit DRI safe test audit SITE safe test audit AXCDR safe test audit

3-78

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Format

Query Audit information

The following command string format can be used to display an audit scheduled for devices: query_audits <location> <audit_type> <device_name> <device_id1> <device_id2><device_id3> Refer to the description of the query_audits parameter. Alternatively multiple disp_element commands can be used as listed in the following section.

Display information
The following command string format can be used to display the audit_type scheduled for a device: disp_element sap_audit_type,<index> <location> Refer to the description of the sap_audit_type parameter. The following command string format displays the device_type scheduled for a device: disp_element sap_device_type,<index> <location> Refer to the description of the sap_device_type parameter. The following command string format displays the start_time_hour and start_time_min scheduled for a device: disp_element sap_start_time,<index> <location> Refer to the description of the sap_start_time. The following command string format can be used to display the end_time_hour and end_time_min scheduled for a device: disp_element sap_end_time,<index> <location> Refer to the description of the sap_end_time parameter. The following command string format displays the interval_hour and interval_min scheduled for a device: disp_element sap_interval,<index> <location> Refer to the description of the sap_interval parameter.

68P02901W23-S

3-79 Nov 2009

Examples

Chapter 3: Device/function related commands

Examples
Example 1
In this example of range scheduling, the audit schedule is changed so that the DRI is audited for safe tests every 15 minutes from 9:30 am until 10:30 pm: chg_audit_sched bsc dri safe 9 30 22 30 0 15 Where: bsc dri safe 9 30 22 30 0 15 is: location device_name audit_type start_time end_time interval

System response
COMMAND ACCEPTED

Example 2
In this example of GPRS range scheduling, the audit schedule is changed so that the PICP MSI 0 is audited for safe tests every 45 minutes from 9 am until 5:30 pm: chg_audit_sched pcu_0 msi safe 9 0 17 30 0 45 Where: pcu_0 msi safe 9 00 17 30 0 45 is: location device_name audit_type start_time end_time interval

System response
COMMAND ACCEPTED

3-80

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Examples

Example 3
{26740} In this example, the audit is scheduled for the PSI device from 9:30 am to 10:30 pm with an interval of 15 minutes. chg_audit_sched bsc psi safe 9 30 22 30 0 15 Where: bsc psi safe 9 30 22 30 0 15 is: location device_name audit_type start_time end_time interval

System response
COMMAND ACCEPTED

Example 4
{25002} In this example, the audit is scheduled for the tdm device at 3:00 am daily. chg_audit_sched 0 tdm swap_test 3 0 3 0 0 0 Where: 0 tdm swap_test 30 30 00 is: location device_name audit_type start_time end_time interval

System Response
COMMAND ACCEPTED

68P02901W23-S

3-81 Nov 2009

Examples

Chapter 3: Device/function related commands

Example 5
{25002} This example reschedules safe audit execution for DRI devices at location 1. The audit starts at 09:30 and ends at 22:30 and runs every 15 minutes. chg_audit_sched 1 DRI safe 9 30 22 30 0 15 Where: 1 DRI safe 9 30 22 30 0 15 is: location device_name audit_type start_time end_time interval

System response
COMMAND ACCEPTED

Example 6
{25002} This example causes the swap test to occur at 2:50 am every day. chg_audit_sched 0 tdm swap_test 2 50 5 0 0 0 Where: 0 tdm swap_test 2 50 50 00 is: location device_name audit_type start_time end_time interval

System response
COMMAND ACCEPTED

3-82

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

References

References
Related commands
cage_audit on page 3-58 site_audit on page 3-507 device_audit on page 3-210 query_audits on page 3-472

68P02901W23-S

3-83 Nov 2009

chg_cell_element

Chapter 3: Device/function related commands

chg_cell_element

Description
The chg_cell_element command changes the value of cell-related parameters. This command supports only non-statistical cell elements. Prompts are presented for dependent cell parameters where necessary. Security level Supported by OMC-R GUI Command type Prerequisites Operator actions 4 Yes. Dependent upon the database parameter being changed. None Respond to the dependent parameter prompts associated with the cell element being modified.

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

Format
Syntax
chg_cell_element [<location>] <element> [,<index>] <value> <cell_desc_opt> chg_cell_element <location> <element> [,<index>] <value> all

NOTE
When an attempt is made to change cell elements ccch_conf, gprs_enabled, gprs_ts_config_alg, max_gprs_ts_per_carrier, primary_pcu, res_gprs_pdchs, res_ts_less_one_carrier, switch_gprs_pdchs, or sw_ts_less_one_carrier, and the requested PDTCHs exceed the GDS or PMC capacity on the PCU, the BSS accepts the request and issues a warning to indicate that sufficient GDS or PMC resource is not available.

3-84

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Format

Input parameters
location The location can also be entered as all to change the value of the specified element for all available cells in the system. element The cell parameter to be changed

NOTE
The all option does not work for the coincident_mb parameter.

index The index of the element being changed, if any. value The value being assigned to the element. cell_desc_opt The GSM cell ID of the affected cell. cell_number=. can precede the GSM cell ID (optional). The format for the GSM cell ID depends on: The system used (PGSM, EGSM, DCS1800, PCS1900). Whether the seven parameter GSM cell ID format or the four parameter GSM cell ID format has been enabled.

Only PCS1900 systems can use a three digit MNC. The cell_desc can also be a cell name created using the cell_name command. When the cell name is entered, it must be placed inside double quotation marks. cell_name= can precede the cell name (optional).

NOTE
This command responds to the shortened input parameter cell= allowing entry of either the cell_number or the cell_name without further definition. With some parameters, all can be entered. If this command is used, <location> or all must also be used for the site. See the individual parameter descriptions.

68P02901W23-S

3-85 Nov 2009

Examples

Chapter 3: Device/function related commands

Examples
Example 1
In this example, the hop_qual_enabled parameter is changed to 1 for a cell with GSM Half Rate enabled: chg_cell_element hop_qual_enabled 0 cell number =0 0 1 0 1 98 75 Where: hop_qual_enabled 1 cell=0 0 1 0 1 98 75 is: cell element being changed. new element value. cell description.

System response
Enter RSS handover threshold l_rxqual_dl_h_hopping: 250 Enter RSS handover threshold l_rxqual_ul_h_hopping: 250 Enter RSS handover threshold l_rxqual_dl_p_hopping: 250 Enter RSS handover threshold l_rxqual_ul_p_hopping: 250 Enter RSS handover threshold l_rxqual_ul_h_hopping_hr: 250 Enter RSS handover threshold l_rxqual_ul_p_hopping_hr: 250 Enter RSS handover threshold l_rxqual_dl_h_hopping_hr: 200 Enter RSS handover threshold l_rxqual_dl_p_hopping_hr: 200 COMMAND ACCEPTED

NOTE
The following AMR Full Rate HDPC parameters are only prompted for if AMR is unrestricted.

Enter RSS handover threshold l_rxqual_ul_h_hopping_amr_fr: Enter RSS handover threshold l_rxqual_ul_p_hopping_amr_fr: Enter RSS handover threshold l_rxqual_dl_h_hopping_amr_fr: Enter RSS handover threshold l_rxqual_dl_p_hopping_amr_fr:

3-86

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Examples

Example 2
This example turns on IMRM band_preference for a cell using the numeric value 16, and set all weighting parameters to 0. chg_cell_element band_preference 16 cell number=0 0 1 0 1 1 12 Where: band_prefernce 16 cell=0 0 1 0 1 1 12 is: element being changed. new element value. cell number.

System response
Enter the weighting for PGSM: 0 Enter the weighting for EGSM: 0 Enter the weighting for DCS1800: Enter the weighting for UMTS: 0 COMMAND ACCEPTED: WARNING: All IMRM band weights set to unsupported. shall apply internal defaults in the IMRM band selection algorithm The BSS 0

Example 3
{26881} This example changes the value of the database element ext_utbf_nodata to 1 for cell 0 0 1 0 1 1 4. chg_cell_element ext_utbf_nodata 1 cell 0 0 1 0 1 1 4 Where: ext_utbf_nodata 1 0010114 is: cell element being changed. new element value. cell number.

System response
COMMAND ACCEPTED

68P02901W23-S

3-87 Nov 2009

Examples

Chapter 3: Device/function related commands

Example 4
{31565} This example enables the functionality of AGCH flow control, any one of the triggers associated with IA and IAR can trigger AGCH overload. chg_cell_element _cell_data,20 1 cell_number=5 4 3 2 1 61986 34944 Where: _cell_data,20 1 5 4 3 2 1 61986 34944 is: element being changed. new element value. cell number.

System Response
COMMAND ACCEPTED

Example 5
{34164} This example modifies the value of _cell_data,21 from 0 to 1 to enable the 5 minute statistics uploading for cell 4 6 0 0 0 23 1101 under site 11. chg_cell_element _cell_data,21 1 cell=4 6 0 0 0 23 1101 Where: _cell_data,21 1 4 6 0 0 0 23 1101 is: element being changed new element value cell number

System Response
COMMAND ACCEPTED

Example 6
{23311A} This example attempts to disable the Extended Range Cell for GSM (ext_range_cell = 0) when ext_pdchs is set to non-zero for any RTF in the cell. chg_cell_ele ext_range_cell 0 cell 0 0 1 0 1 1 18 Where: ext_range_cell 0 0 0 1 0 1 1 18 is: element being changed new element value cell number

3-88

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Examples

System Response
COMMAND REJECTED: Value of ext_pdchs shall be 0 when ext_range_cell is disabled for the cell

Example 7
{23311A} This example attempts to enable baseband hopping (hopping_support = 2) when ext_pdchs in any RTF of the cell > 0. chg_cell_ele hopping_support 2 cell 0 0 1 0 1 1 18 Where: hopping_support 2 0 0 1 0 1 1 18 is: element being changed new element value cell number

System Response
COMMAND REJECTED: Value of ext_pdchs shall be 0 when Baseband hopping is enabled for the cell

68P02901W23-S

3-89 Nov 2009

chg_cell_id

Chapter 3: Device/function related commands

chg_cell_id

Description
The chg_cell_id command changes the GSM cell ID of a specified cell. The format for the GSM cell ID depends on: The system used (PGSM, EGSM, DCS1800, PCS1900) Whether the seven parameter GSM cell ID format or the four parameter GSM cell ID format has been enabled.

Only PCS1900 systems can use a three digit MNC. The format to enter PGSM, EGSM, or DCS1800 Cell ID is: a b c d e f g The format to enter a PCS1900 Cell ID is: abc zde f g Where: a b c z is: the first digit of the MCC (Mobile Country Code). the second digit of the MCC. the third digit of the MCC. the first digit of the MNC (Mobile Network Code) for PCS1900 systems. This digit only applies to PCS1900 systems. EGSM, PGSM, and DCS1800 systems still use the two digit MNC, beginning with d, shown in the next row. either: e the second digit of the PCS1900 MNC, or the first digit of the PGSM, EGSM, or DCS1800 MNC.

either: the third digit of the MNC, or the third digit of the PCS1900 MNC, or the second digit of the PGSM, EGSM or DCS1800 MNC, or Only PCS1900 systems use a three digit MNC.

f g

the LAC (Local Area Code). the CI (Cell Identity).

3-90

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Format

When the GSM cell ID is changed using this command, it is not propagated throughout the CM database. A warning message is presented when this command is successfully entered. Security level Supported by OMC-R GUI Command type Prerequisites 4 Yes A (no operator actions) None

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

Format
Syntax
chg_cell_id <old_cell_desc> <new_cell_desc>

Input parameters
old_cell_desc Original Cell ID of the cell. The format for the GSM cell ID depends on: The system used (PGSM, EGSM, DCS1800, PCS1900) Whether the seven parameter GSM cell ID format or the four parameter GSM cell ID format has been enabled. Only PCS1900 systems can use a three digit MNC. The old_cell_desc can also be a cell name created using the cell_name command. When the cell name is entered, it must be placed inside double quotation marks. new_cell_desc New GSM cell ID of the cell.

68P02901W23-S

3-91 Nov 2009

Examples

Chapter 3: Device/function related commands

Examples
Example 1
In this example, the GSM cell ID is changed: chg_cell_id 5 4 3 2 1 61986 34944 5 4 3 2 1 61985 37982 Where: 5 4 3 2 1 61986 34944 5 4 3 2 1 61985 37982 is: old_cell_desc new_cell_desc

System response
WARNING: Verify OML state to ensure change propagated to all neighbors. COMMAND ACCEPTED

Example 2
In this example, the affected cell is identified using the cell_name london-north: chg_cell_id london-north 5 4 3 2 1 61985 37982 Where: london-north 5 4 3 2 1 61985 37982 is: old_cell_desc (using cell name) new_cell_desc

System response
WARNING: Verify OML state to ensure change propagated to all neighbors. COMMAND ACCEPTED

Example 3
In this example, the GSM cell ID is changed for a PCS1900 cell: chg_cell_id 543 021 61986 34944 543 021 61985 37982 Where: 543 021 61986 34944 543 021 61985 37982 is: old_cell_desc new_cell_desc

3-92

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

References

System response
WARNING: Verify OML state to ensure change propagated to all neighbors. COMMAND ACCEPTED

References
Related commands
add_cell on page 3-22 del_cell on page 3-192 cell_name on page 3-62 disp_cell on page 3-241 copy_cell on page 3-179

68P02901W23-S

3-93 Nov 2009

chg_cmd_level

Chapter 3: Device/function related commands

chg_cmd_level

{27508}

Description
The chg_cmd_level command modifies the current level of MMI command to a certain security level. Security level Supported by OMC GUI Command type Prerequisites 4 Yes A (no operator actions) None

Format
Syntax
chg_cmd_level <command> <level you want the command to change>

Example
Example 1
This example modifies the level of disp_equipment to 2. chg_cmd_level disp_equipment 2 Where: disp_equipment 2 is: command level

System response
COMMAND ACCEPTED

3-94

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

chg_csfp

Description
The chg_csfp command changes the CSFP algorithm or flow control values. The CSFP algorithm selects the CSFP algorithm method used when configuring CSFPs using the configure_csfp command or through the OMC-R. The flow_control selects the CSFP flow control value that controls the amount of RSL link utilization that a CSFP download from BSC to BTS can use. A value of 100 does not mean that the link is 100% utilized during the download. Only the CSFP downloads can proceed at the maximum throughput rate. Security level Supported by OMC GUI Command type Prerequisites 4 Yes A (no operator actions) None

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

Format
Syntax
chg_csfp <element> <value> <location>

68P02901W23-S

3-95 Nov 2009

Examples

Chapter 3: Device/function related commands

Input parameters
element Two selections are available: algorithm flow_control Selects the CSFP algorithm method. The location values that can be entered for this element are 0 (or bsc) to 140. Selects the CSFP flow control value. The location values that can be entered for this element are 1 - 140.

value Either an algorithm or a flow control value can be entered but not both. The value that can be used is dependent upon the selected element: algorithm none stby pool any flow_control location Specifies the element location. 0 or bsc 1 - 140 pcu BSC BTS PCU (4) (2) (3) (1) No CSFP device is to be configured at this site Select only standby BSP/BTP GPROCs Select only pool GPROCs Select POOL GPROCs first followed by STBY GPROCs. Default value for this algorithm.

Selectable in a range from 10 to 100 in steps of 10. The default value is 10%.

Examples
Example 1
This example shows the inputs required to update the CSFP algorithm at the BSC to be only pool GPROCs. chg_csfp algorithm pool bsc Where: algorithm pool bsc is: element Only pool GPROCs location

3-96

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

References

System response
COMMAND ACCEPTED

Example 2
This example shows the inputs required to update the CSFP flow control at site 3 to be 10%. chg_csfp flow_control 10 3 Where: flow_control 10 3 is: element flow control percentage location

System response
COMMAND ACCEPTED

Example 3
{25424} This example updates the csfp flow control value of PCU. chg_csfp flow_control 40 pcu Where: flow_control 40 pcu is: element flow control percentage location

System response
COMMAND ACCEPTED

References
Related command
disp_csfp on page 3-263

68P02901W23-S

3-97 Nov 2009

chg_dte

Chapter 3: Device/function related commands

chg_dte

Description
The chg_dte command assigns the DTE addresses to allow connections between the BSC and the OMC-R or CBC. The mapping of DTE addresses used and the default timeslots to contact the OMC while the network is in ROM are shown in Table 3-23 for the RXCDR and in Table 3-24 for the BSC.

Table 3-23
Cage 0 0 0 1

RXCDR default DTE addresses

MSI slot 10 10 8 10 MMS 0 1 0 0 Default timeslot 1 1 1 1 RXCDR DTE address 0 1 2 3

Table 3-24
Cage 0 0 0 1

BSC default DTE addresses

MSI slot 16 16 14 16 3 Yes B (Operator actions required) The OML link affected by this command must be reset for the changes to take effect. Reset the OML after changes have been entered with this command. MMS 0 1 0 0 Default timeslot 1 1 1 1 RXCDR DTE address 0 1 2 3

Security level Supported by OMC-R GUI Command type Prerequisites Operator actions

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

3-98

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Format

Format
Syntax
chg_dte <link> [<link_num>] <address_length> [<address_byte>] . [<address_byte>] . .

Input parameters
link Specifies the link location: bsc omcr cbc bcs_cbc link_num The link location type determines the range of values: 0-3 0-7 0 bsc omcr bsc_cbc or cbc. If the address_length is 0, a link_num is required for cbc and bsc_cbc. The communication link between the BSC and the OMC-R. OMC-R CBC The communication link between the BSC and CBC.

address_length The number of valid address bytes that are added to the list. The range of values is 0 - 14. address_byte The value of a particular address byte. The range of values is 0 - 9. The number of address bytes entered must equal the number entered for the address_length parameter. An address_byte value is not required when the address_length is zero.

68P02901W23-S

3-99 Nov 2009

Examples

Chapter 3: Device/function related commands

Examples
Example 1
In this example, the DTE address of the third BSC is changed to 12345: chg_dte bsc 3 5 1 2 3 4 5 Where: bsc 3 5 12345 is: location link_num address_length address_byte (5 bytes)

System response
BSS DTE addresses: Address #0: Address #1: Address #2: Address #3: 23466811570001 41224643654225 31777619565738 12345

OMCR DTE addresses: Address #0: Address #1: Address #2: Address #3: Address #4: Address #5: 23466823020041 24885902667864 38959620015151 122876465567 2301 6811570001

Address #6: Zero length address Address #7: Zero length address

COMMAND ACCEPTED

3-100

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

References

Example 2
In this example, a zero length DTE address is created: chg_dte omcr 2 0 Where: omcr 2 0 is: location link_num address_length

System response
BSS DTE addresses: Address #0: Address #1: Address #2: Address #3: 23466811570001 41224643654225 31777619565738 12345

OMCR DTE addresses: Address #0: Address #1: Address #2: Address #3: Address #4: Address #5: Address #5: 23466823020041 24885902667864 Zero length address 122876465567 2301 6811570001 6811570001

Address #6: Zero length address Address #7: Zero length address

COMMAND ACCEPTED

References
Related command
disp_dte on page 3-269.

68P02901W23-S

3-101 Nov 2009

chg_eas_alarm

Chapter 3: Device/function related commands

chg_eas_alarm

Description
The chg_eas_alarm command initializes and modifies the EAS (External Alarm System) alarm table. The EAS alarm table contains 34 indexed pairs. Each pair includes a severity level and up to 24 text characters for each BSS. Each pair corresponds to the output of an equipped EAS/PIX module. This command permits individual EAS alarms to be reported as text strings. Security level Supported by OMC-R GUI Command type Prerequisites 4 Yes A (no operator actions) The EAS device must be equipped before a severity level and text characters can be assigned.

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

Format
Syntax
chg_eas_alarm <alarm_table_index> <alarm_severity_level> <new_alarm_string>

3-102

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Example

Input parameters
alarm_table_index Specifies the index number assigned to a user-defined alarm text string in the EAS Alarm Table on the following page. The range of values is 0 - 33. alarm_severity_level Specifies the alarm level for a specific alarm string. Valid values are: 0 1 2 3 4 new_alarm_string Assigns the alarm text string that corresponds to an alarm_table_index value in the EAS Alarm Table. The alarm string must be entered inside double quotation marks. The alarm text string can be a maximum of 24 characters, including spaces. investigate critical major minor warning

Example
In this example, an alarm string of door open is assigned to the first index (1) of the alarm string table. This text string contains nine characters; the alarm is classified minor (3); and the string signifies that a cabinet door is open: chg_eas_alarm 1 3 cabinet door open Where: 1 3 cabinet_door_open is: alarm_table_index alarm_severity_level new_alarm_string

System response
COMMAND ACCEPTED

68P02901W23-S

3-103 Nov 2009

References

Chapter 3: Device/function related commands

References
Related information
Table 3-25 lists the EAS default alarm strings.

Table 3-25

EAS default alarm strings

alarm_table_index 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 Default alarm string Burglar Door Open Fire High Temperature Low Temperature High Humidity Low Humidity Tower Beacon Outage Surge Arrester Failure Microwave Trans. Failure AC Power Failure Generator Running Generator Failed PSU Rectifier PSU Battery PSU Fuse Personnel on Site General Alarm 1 General Alarm 2 General Alarm 3 PCU Over Temperature PCU Customer Defined 1 PCU Door Open PCU DC Fail PCU Circuit Breaker PCU AC Fail PCU Comms Equipment Continued

3-104

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

References

Table 3-25

EAS default alarm strings (Continued)

alarm_table_index 27 28 29 30 31 32 33 Default alarm string TDU Over Temperature TDU Door Open TDU Circuit Breaker TDU Battery TDU Customer Defined 1 TDU Customer Defined 2 TDU Customer Defined 3

Related commands
chg_element on page 3-106 disp_element on page 3-272

68P02901W23-S

3-105 Nov 2009

chg_element

Chapter 3: Device/function related commands

chg_element

Description
The chg_element command modifies database parameters in the CM database. Security level Supported by OMC-R GUI Command type Prerequisites Operator actions 4 Yes Dependent on the database parameter being changed. None Respond to the dependent parameter prompts associated with the cell element being modified.

NOTE
Only the chg_ele phase_lock_gclk parameter is moved to security level 3. Enter this command at the BSC only. This command does not work at a BTS site. Contact the OMC-R for help.

Format
Syntax
chg_element <element_name> [,<index1>][,<index2>] <element_value> <location>[<cell_desc>] chg_element <element_name> [,<index1>][,<index2>] <element_value> all chg_element <element_name> [,<index1>][,<index2>] <element_value> <location>all

NOTE
When an attempt is made to change cell elements ccch_conf, gprs_enabled, gprs_ts_config_alg, max_gprs_ts_per_carrier, primary_pcu, res_gprs_pdchs, res_ts_less_one_carrier, sw_ts_less_one_carrier, or switch_gprs_pdchs, and the requested PDTCHs exceed the GDS or PMC capacity on the PCU, the BSS accepts the request and issues a warning to indicate that enough GDS or PMC resource is not available.

3-106

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Format

Input parameters
element_name String identifying the database parameter in the CM database. index1 Some database parameters require an index. They are highlighted with an asterisk in the table in the Related Information section. A comma is required before the index number. index2 Database parameters requiring a second index are highlighted in the table shown in the Related Information section. A comma is required before the index number. index2 is used only with statistical database parameter names normal and weighted distribution statistical database parameter names require the use of index2. value New value for the element_name. location Specifies the site location: 0 or bsc 1 - 140 {27955A} pcu or pcu_0 all BSC BTS PCU Specifies all sites. Restrictions on the use of all locations are: cell_desc GSM cell ID of the cell to be changed, preceded by cell_number= The format for the GSM cell ID depends on: The system used (PGSM, EGSM, DCS1800, PCS1900). Whether the seven parameter GSM cell ID format or the four parameter GSM cell ID format has been enabled. Only PCS1900 systems can use a three digit MNC. The name of the cell created using the cell_name command can be entered in place of the cell_number. When the cell name is entered, it must be placed inside double quotation marks, and cell_name= must precede it. Allowed outside SYSGEN mode only for type A elements. Not allowed outside SYSGEN mode for type B elements. Allowed for BY_CELL and BY_SITE elements only.

NOTE
This command responds to the shortened input parameter cell= allowing entry of either the cell_number or the cell_name without further definition. 68P02901W23-S 3-107 Nov 2009

Examples

Chapter 3: Device/function related commands

The value all is also a valid input for the cell_desc, which changes element_name to value for all cells at the specified location. Restrictions on the use of all cells are: Not allowed for elements that cause the site to reset. Not allowed outside SYSGEN mode. Allowed for BY_CELL and BY_SITE elements only. Sites that are not equipped are not affected.

Examples
The following examples only demonstrate how specific parameters are changed using the chg_element command. The examples shown can be part of a larger procedure. Refer to the appropriate documentation for detailed explanations of these procedures.

Example 1
In this example, the bsic value is changed to 1 for site number 1, cell_number=5 4 3 2 1 61986 34944: chg_element bsic 1 1 cell_number=5 4 3 2 1 61986 34944 Where: bsic 1 1 5 4 3 2 1 61986 34944 is: element name value location cell description

System response
WARNING: Changing this element will reset all DRIs associated with this cell and will not be propagated through out the neighbor list Are you sure (y=yes,n=no)? COMMAND ACCEPTED Selecting y or Y causes the system to make the change and reset. Selecting n or N causes the system to abandon the command without changing the parameter. y

3-108

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Examples

Example 2
In this example, the database parameter transcoder_location is changed to a value of 1 for site number 0: chg_element transcoder_location 1 0 Where: transcoder_location 1 0 is: element name value location

System response
COMMAND ACCEPTED

NOTE
Example 2 works only at site 0 in SYSGEN ON mode.

Example 3
In this example, the severity of EAS alarm 6 at location 0 is changed to level 2: chg_element eas_severity,6 2 0 Where: eas_severity 6 2 0 is: element name index value location

System response
COMMAND ACCEPTED

68P02901W23-S

3-109 Nov 2009

Examples

Chapter 3: Device/function related commands

Example 4
In this example, the affected cell is identified using the cell_name london-north: chg_element bsic 1 1 cell name= london-north Where: bsic 1 1 london-north is: element name value location cell name

Example 5
In this example, the base station identity code (bsic) value is changed to 1 for PCS 1900 site number 0, cell_desc=543 721 61986 34944: chg_element bsic 1 1 cell number= 543 721 61986 34944 Where: bsic 1 1 543 721 61986 34944 is: element name value location cell description

3-110

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Examples

Example 6
This example attempts to change primary_pcu from 1 to 0 when PCU 0 does not have enough PMC resources for the Cell. chg_element primary_pcu 0 1 cell number= 0 0 1 0 1 1 1 Where: primary_pcu 0 1 0010111 is: element name value location cell description

System response
WARNING: GPRS traffic may be disrupted while GPRS timeslots are being reconfigured Are you sure (y=yes,n=no)? COMMAND ACCEPTED WARNING: Insufficient PMC resources available for all PDTCHs on the PCU. y

Example 7
In this example, the value of improve_ts_enabled is changed to 0 when the improved timeslot sharing feature is unrestricted. chg_element improve_ts_enabled 0 bsc Where: improve_ts_enabled 0 bsc is: element name value location

System Response
WARNING: B-U DD CTU2 DRIs must be cycled to deactivate ITS at specific sites or reset BTS site. COMMAND ACCEPTED

68P02901W23-S

3-111 Nov 2009

Examples

Chapter 3: Device/function related commands

Example 8
{28337} In this example, the value of the database element ss7_hsp_12_t1 is modified to 255000 when the increased network capacity feature is unrestricted. chg_element ss7_hsp_12_t1 255000 0 Where: ss7_hsp_12_t1 255000 0 is: element name value location

System response
COMMAND ACCEPTED

Example 9
{28000} This example enables the rolling blackout mechanism on PCU. The PRP throughput increase feature is deactivated. chg_element prp_fanout_mode 1 pcu Where: prp_fanout_mode 1 pcu is: element name value location

System response
WARNING: Changing prp_fanout_mode will cycle device PCU. Are you sure (y=yes,n=no)?

3-112

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Examples

Example 10
{27703A} This example modifies the value of streaming_enabled to 1 to enable support of streaming when the QoS phase 2 feature is unrestricted. chg_element streaming_enabled 1 0 Where: streaming_enabled 1 0 is: element name value location

System response
COMMAND ACCEPTED

Example 11
{31400} In this example, the value of td_enabled is changed to 0, when RDB 4225 Inter-RAT feature (InterRatOpt) and Enhanced Inter-RAT handover feature (EnhancedInterRatOpt) are both restricted, and TD-SCDMA inter-working feature (tdOpt) is unrestricted. chg_element td_enabled 0 0 Where: td_enabled 0 0 is: element name value location

System response
WARNING: TD-SCDMA inter-working function will be disabled, if the operator changes td_enabled element. Are you sure (y=yes, n=no)? y COMMAND ACCEPTED

68P02901W23-S

3-113 Nov 2009

Examples

Chapter 3: Device/function related commands

Example 12
{27508} This example modifies the fieldeng_always_enabled parameter to 1. chg_ele fieldeng_always_enabled 1 0 Where: fieldeng_always_enabled 1 0 is: element name value location

System response
COMMAND ACCEPTED

Example 13
{32340} This example allows the operator to change the value of cell barred delay to 180 seconds. chg_element cell_barred_delay 180 0 Where: cell_barred_delay 180 0 is: element name value location

System response
COMMAND ACCEPTED

3-114

Examples

Chapter 3: Device/function related commands

Example 21
{34164} This example modifies the value of _bss_data,1 from 0 to 1 to enable the 5 minute statistics uploading. chg_element _bss_data,1 1 0 Where: _bss_data,1 1 0 is: element name value location

System Response
COMMAND ACCEPTED

Example 22
{34164} This example modifies the value of _cell_data,21 from 0 to 1 to enable the 5 minute statistics uploading for cell 0 0 1 0 1 99 72 under site 114. chg_element _cell_data,21 1 114 cell 0 0 1 0 1 99 72 Where: _cell_data,21 1 114 0 0 1 0 1 99 72 is: element name value location cell description

System Response
COMMAND ACCEPTED

3-118

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Examples

Example 23
{34320G} This example modifies the value of power_save_enable to 1 on site 1 when FR 34320G is enabled. chg_element power_save_enable 1 1 Where: power_save_enable 1 1 is: element name value location

System Response
COMMAND ACCEPTED

Example 24
{34320G} This example attempts to modify power_save_enable on site 15 when the BTS is not a Horizon II cabinet. chg_element power_save_enable 1 15 Where: power_save_enable 1 15 is: element name value location

System Response
ERROR: The site location is not a power saving capable BTS type. COMMAND REJECTED

68P02901W23-S

3-119 Nov 2009

Examples

Chapter 3: Device/function related commands

Example 25
{34303} This example attempts to modify the value of the Abis status element to 0 to disable the Abis connection for H1 site (Site id = 1) when the Dual Abis Aware feature is enabled. chg_element _site_data, 5 0 1 Where: _site_data, 5 0 1 is: element name value location

System Response
COMMAND ACCEPTED

Example 26
{34303} This example attempts to modify the value of the Abis status element to 1 to enable the Abis connection for H1 site (Site id = 1). The site 1 is the relay node of a route to the BSC and its downstream node (Site 2) can only connect to the BSC through site 1. chg_element _site_data, 5 1 1 Where: _site_data, 5 1 1 is: element name value location

System Response
WARNING: Migrate this site may cause its downstream node sites to be isolated. Are you sure (y=yes, n=no)? Y COMMAND ACCEPTED

3-120

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Examples

Example 27
{34303} This example attempts to modify the value of the Abis status element to 1 to enable the Abis connection for the Horizonmacro site (Site id = 1) with a Horizon II mini expansion when the Dual Abis Aware feature is enabled. chg_element _site_data, 5 1 1 Where: _site_data, 5 1 1 is: element name value location

System Response
Error: Unsupported combination of cabinets for migration. COMMAND REJECTED

Example 28
{34303} This example attempts to enable the Abis connections of all the BTS sites of the BSC when the Dual Abis Aware feature is enabled. Ensure that each of the sites has a direct route to the BSC. chg_element _site_data, 5 1 all Where: _site_data, 5 1 all is: element name value location

68P02901W23-S

3-121 Nov 2009

Examples

Chapter 3: Device/function related commands

System Response
WARNING: Enable Abis status for all the BTS sites under BSC? Are you sure (y=yes, n=no)? Y Site 0: ----------COMMAND REJECTED: Unallowable BTS type. Site 10: ----------COMMAND REJECTED: BTS is not B-U. Site 11: ----------COMMAND REJECTED: Unallowable BTS type. COMMAND ACCEPTED: WARNING: Not all sites were updated; errors occurred.

Example 29
{23306} This example changes the value of the bsp_overload_protection parameter to 0. chg_element bsp_overload_protection 0 bsc Where: bsp_overload_protection 0 bsc is: element name value location

System response
COMMAND ACCEPTED

3-122

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Examples

Example 30
{23306} This example attempts to change the value of the bsp_overload_protection parameter to 2. chg_element bsp_overload_protection 2 bsc Where: bsp_overload_protection 2 bsc is: element name value location

System response
ERROR: Range Error, parameter number: 2 COMMAND REJECTED

Example 31
{28337} This example modifies the value of ss7_hsp_l2_t1 to 255000 when the increased network capacity feature is enabled. chg_element ss7_hsp_l2_t1 255000 0 Where: ss7_hsp_l2_t1 255000 0 is: element name value location

System response
COMMAND ACCEPTED

68P02901W23-S

3-123 Nov 2009

Examples

Chapter 3: Device/function related commands

Example 32
{25002} This example changes the value of tdm_switch to 1. chg_element tdm_switch 1 0 Where: tdm_switch 1 0 is: element name value location

System response
COMMAND ACCEPTED

Example 33
{25002} This example changes the value of tdm_switch to 0. chg_element tdm_switch 0 0 Where: tdm_switch 0 0 is: element name value location

System response
WARNING: TDM Availability Enhancements function will be disabled, if the operator changes tdm_switch element. Are you sure (y=yes, n=no)? y COMMAND ACCEPTED

3-124

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Examples

Example 34
{23311A} This example attempts to enable baseband hopping (hopping_support = 2) when ext_pdchs in any RTF of the cell > 0. chg_element hopping_support 2 16 Where: hopping_support 2 16 is: element name value location

System Response
COMMAND REJECTED: Value of ext_pdchs shall be 0 when Baseband hopping is enabled for the cell. COMMAND ACCEPTED

Example 35
{23311A} This example attempts to enable asym_edge_enabled = 1 when ext_pdchs > 0 for any RTF in the site. chg_element asym_edge_enabled 1 16 Where: asym_edge_enabled 1 16 is: element name value location

System Response
COMMAND REJECTED: Value of ext_pdchs shall be 0 when ASYM feature is enabled for the site COMMAND ACCEPTED

68P02901W23-S

3-125 Nov 2009

Examples

Chapter 3: Device/function related commands

Example 36
{34321} This example modifies the value of _bss_data,10 from 0 to 1 to enable the cage management feature. chg_element _bss_data,10 1 0 Where: _bss_data,10 1 0 is: element name value location

System Response
COMMAND ACCEPTED

Example 37
{34900} When the TD-SCDMA inter-working feature (tdOpt) is unrestricted, change the value of _bss_data,6 to 1 when the TD-SCDMA inter-working feature is disabled (td_enabled = 0). chg_element _bss_data,6 1 0 Where: _bss_data,6 1 0 is: element name value location

System Response
COMMAND ACCEPTED

3-126

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

References

Example 38
This example modifies the value of nacc_nc2_enabled from 0 to 1 to enable the NC2 mode of NACC. chg_element nacc_nc2_enabled 1 0 Where: nacc_nc2_enabled 1 0 is: element name value location

System response
COMMAND ACCEPTED

References
Related information
Details of the database parameters that can be changed using this command are given in the relevant parameter descriptions in Chapter 6 CM database parameters of this manual.

Related command
chg_element on page 3-106.

68P02901W23-S

3-127 Nov 2009

chg_hop_params

Chapter 3: Device/function related commands

chg_hop_params

Description
The chg_hop_params command permits changing multiple hopping parameters for a site at one time. The changes are verified outside SYSGEN and when exiting SYSGEN mode. Synthesizer hopping and baseband hopping can be enabled in different cells at the same site. It is also possible to mix non-hopping cells and hopping cells at the same site. When the system accepts the chg_hop_params command for a particular cell, the system rejects other chg_hop_params commands until the system reconfiguration due to the first command is complete. Once the system accepts the chg_hop_params command, the system displays a warning message. If the system operator has enabled, disabled, or changed an enabled hopping system which is synthesizer hopping through the BCCH RTF, the warning message states that the site resets. The operator can abort the command to prevent a site reset. If all FHIs for the cell are disabled, the operator can change hopping support from no hopping to baseband hopping, or from no hopping to synthesizer hopping. Although the chg_hop_params parameter allows a hopping system corresponding to a Dual Band Cell to contain frequencies from either the primary or the secondary frequency band, it does not allow both at the same time. If this is attempted, an error message displays. Each cell takes about 90 seconds to finish the hopping reconfiguration. If duplicated frequencies are entered, a warning message is presented. The system ignores the duplicated frequencies. If this warning message occurs, the command must be re-entered without the duplication. This command runs the hopping verification on all cells in the specified site, even if the cells in the site are not modified. An EGPRS RTF cannot baseband hop in the same FHIs as non-EGPRS RTFs. Security level Supported by OMC-R GUI Command type Prerequisites 4 Yes A (no operator actions) If hopping_systems verification fails, the system rejects this command outside SYSGEN. The system does not verify hopping systems inside SYSGEN until SYSGEN is off. If the Extended Range feature is unrestricted: Both timeslots in the Extended Range timeslot pair must have the same FHI if they are part of a hopping system.

3-128

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Format

Baseband and synthesizer hopping systems can only be configured among timeslots of the same type (such as Extended or Normal). Synthesizer Frequency Hopping systems in Extended Range cells must have the FHIs for the BCCH carrier timeslots set to 0xffh (255).

If a Remotely Tuneable Combiner is equipped at the cell, synthesizer hopping is not allowed in a cell. The system rejects this command for microsites that are not equipped with Horizonmicro or Horizoncompact cabinets. The same chg_hop_params command cannot be used to change hopping support to 0 and disable an enabled FHI simultaneously. When using SFH with GSM 1800, there is a limit of 18 frequencies when the frequency range is set to more than 256. If the range is more than 112, only 29 frequencies are allowed. If the range is less than 112, only 64 frequencies are allowed. In a GSM 850 cell, the ARFCN range is 128 - 251. The master cabinet at the site must be a Horizon II macro in order for an EGPRS RTF to baseband hop.

NOTE
This command can be entered only at the BSC. To change multiple hopping parameters at a BTS site, contact the OMC-R for help.

Format
Syntax
chg_hop_params [<location>] chg_hop_params [<cell_desc_opt>]

Input parameters
The location parameter and the cell_desc parameter cannot be used together in the chg_hop_params command. If neither is entered, all cells at the location are assumed. location Specifies the site location: 0 or bsc 1 - 140 cell_desc_opt BSC BTS

68P02901W23-S

3-129 Nov 2009

Format

Chapter 3: Device/function related commands

The GSM cell ID of the affected cell. cell_number= can precede the GSM cell ID. The format for the GSM cell ID depends on: The system used (PGSM, EGSM, DCS1800, PCS1900) Whether the seven parameter GSM cell ID format or the four parameter GSM cell ID format has been enabled. Only PCS1900 systems can use a three digit MNC. The cell_desc_opt can also be a cell name created using the cell_name command. When the cell name is entered, it must be placed inside double quotation marks. cell_number= can precede the cell name.

NOTE
This command responds to the shortened input parameter cell= allowing entry of either the cell_number or the cell_name without further definition. Table 3-26 shows the baseband and synthesizer frequency hopping restrictions on the setting of the chg_hop_params command. The numbers in the columns refer to the notes that follow.

Table 3-26

Baseband and Synthesizer frequency hopping restrictions

Baseband E Yes Yes3 No5 Yes3 No Yes No D Yes2,3 Yes Yes2 Yes Yes Yes No Synthesizer Frequency (SFH) E Yes Yes3 Yes2,3,5 Yes3 No No Yes D Yes2,3 Yes Yes2 Yes Yes No Yes SFH through BCCH E Yes Yes4 Yes2,4 Yes4 No No Yes D Yes2,4 Yes Yes Yes Yes No Yes

FHI state E = Enabled D = Disabled Enable FHI Disable FHI Change MA Change HSN Change to no hopping Change to baseband Change to synthesizer 1.

The reference to the Frequency Hopping Indicator (FHI) is only to that FHI assigned to the BCCH RTF. All other FHIs in the cell are treated like the SFH column. Performs hopping verification. Notifies the Cell Resource Machine (CRM) of the changes made. Causes the affected site to be reset. 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.

2. 3. 4. 5.

3-130

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Examples

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: 2 is: BTS site 2

System response
Hopping systems (FHIs) to be modified in cell 5 4 3 2 1 62259 (0xF333) 8736 (0x2220) (RETURN=no change for this cell): 3 2 Hopping support: 2 FHI 2 status (enable/disable): Mobile allocation (ARFCNs) for FHI 3: 20 60 90 Mobile allocation (ARFCNs) for FHI 2: 20 30 70 HSN for FHI 2: 25 FHI 3 status (enable/disable): disable HSN for FHI 3: Hopping systems (FHIs) to be modified in cell 0 0 1 3 2 1 1 (RETURN=no change for this cell): 2 0 Hopping support: 2 FHI 0 status (enable/disable): 1 Mobile allocation (ARFCNs) for FHI 0: 21 31 71 HSN for FHI 0: 1 FHI 2 status (enable/disable): 1 Mobile allocation (ARFCNs) for FHI 2: 21 61 91 HSN for FHI 2: WARNING: The site will be reset if the operator enabled, disabled or changed an enabled hopping system which is synthesizer hopping through the BCCH RTF Are you sure (y=yes, n=no) ? y Responding n to the Are you sure? prompt aborts the command.

Example 2
In this example, hopping system 2 is disabled for cell 0 0 1 0 1 1 21 at site 7: chg_hop_params cell_number=0 0 1 0 1 1 21

68P02901W23-S

3-131 Nov 2009

Examples

Chapter 3: Device/function related commands

System response
Hopping systems (FHIs) to be modified in cell 0 0 1 0 1 1 21 cellname3 (RETURN=no change for this cell): 2 0 Hopping support: 2 FHI 2 status (enable/disable): 0 Mobile allocation (ARFCNs) for FHI 2: HSN for FHI 2: WARNING: The site will be reset if the operator enabled, disabled or changed an enabled hopping system which is synthesizer hopping through the BCCH RTF Are you sure (y=yes, n=no) ? y

NOTE
If PBCCH/PCCCH is enabled, hopping cannot be enabled on TS0 (legacy) and TS1 (restriction added with this feature) of the BCCH carrier. The WARNING is a legacy output and is printed even if the hopping system in use is baseband hopping.

Example 3
{23311A} This example attempts to enable baseband hopping (hopping_support = 2) when ext_pdchs in any RTF of the cell > 0. chg_hop_params 0 0 1 0 1 1 21 Where: 0 0 1 0 1 1 21 is: cell description

System response
Hopping systems (FHIs) to be modified in cell 0 0 1 0 1 1 21 cellname3 (RETURN=no change for this cell): 2 Hopping support: 2 FHI 2 status (enable/disable):0 Mobile allocation (ARFCNs) for FHI 2: HSN for FHI 2: WARNING: The site will be reset if the operator enabled, disabled or changed an enabled hopping system which is synthesizer hopping through the BCCH RTF Are you sure (y=yes, n=no) ? y COMMAND REJECTED: Value of ext_pdchs shall be 0 when Baseband hopping is enabled for the cell.

3-132

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

References

References
Related information
Table 3-27 lists the prompts for the chg_hop_params command; x indicates a value supplied by the system.

Table 3-27

chg_hop_params prompts
Range 0-2 where: 0 = No hopping in this cell 1 = Synthesizer hopping 2 = Baseband hopping See NOTE. 0 or 1 where: 0 = disable the hopping system 1 = enable the hopping system ARFCN depends on the frequency type for the cell. If the cell is PGSM the range is 1 - 124. If the cell is EGSM the range is either: 1 to 124, or 975 to 1023 Default 0

Prompt Hopping support:

FHI x status (enable/disable):

Mobile allocation (ARFCNs) for FHI x:

Current value

If using EGSM, all of the specified ARFCNs must be in the lower range (1 - 124) or the higher range (975 - 1023, 0). If the cell is DCS1800, the range is 512 - 885. If the cell is PCS1900 the range is 512 - 810. For GSM850, the ARFCN range is 128 - 251. HSN for FHI x: 0 - 63 where: 0 is cyclic, and 1 - 63 is random Current value

NOTE
If any FHIs are enabled, hopping support cannot be 0. The system rejects the chg_hop_params command if: (1) hopping support: = 1 and the Synthesizer Hopping feature is restricted or (2) hopping support: = 2 and the Baseband Hopping feature is restricted.

68P02901W23-S

3-133 Nov 2009

References

Chapter 3: Device/function related commands

Table 3-28 lists the maximum number of frequencies in the mobile allocation. The table also provides the frequency range of the cell (which includes a combination of PGSM and GSM Extension band frequencies) as determined by System Information Type 1 size limitations in the GSM 04.08 Specification Annex J and Cell Channel Description.

Table 3-28

Cell frequencies/mobile allocation

Maximum number of frequencies in the mobile allocation 64 49 16 17 17 17

Frequencies of the cell (ARFCNs used) 1 - 124 975 - 1023 1 - 124, 975 - 1023 0, 1 - 124 0, 957 - 1023 0, 1 - 124, 975 - 1023

Related command
disp_hopping on page 3-320. Table 3-29 lists the restrictions on related commands.

Table 3-29

Restrictions on related commands

chg_hop_params command disable FHI Command allowed enable FHI Command allowed change MA Command rejected; cannot change MA of an enabled FHI. Disable the FHI and equip the RTF before changing the MA Command allowed change HSN Command allowed. change hopping support Command rejected. FHI must be disabled before changing hopping support

Current hopping support and FHI status Baseband hopping FHI is enabled

Baseband hopping FHI is disabled

Command allowed

Command allowed.

Command allowed

Continued

3-134

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

References

Table 3-29

Restrictions on related commands (Continued)

chg_hop_params command disable FHI Command allowed enable FHI Command allowed change MA Command allowed. MA can change so long as the new MA contains all the ARFCNs of the equipped RTFs in the hopping system. Command allowed Command allowed; resets the site change HSN Command allowed change hopping support Command rejected. FHI must be disabled before changing hopping support

chg_ksw_config

Description
The chg_ksw_config command indicates how KSWs are physically connected when two or more KSW pairs are equipped at a site. KSWs are connected through the EXP KSWX cards to form a larger switching network. The TDM highway of a site can consist of up to four portions. A different KSW pair handles each portion. The first identifier of a KSW is the portion of the TDM highway handled by that KSW. The highway portions are defined as: Highway Portion 0 Highway Portion 1 Highway Portion 2 Highway Portion 3 TDM timeslots 0 - 1023 handled by KSW pair 0. TDM timeslots 1024 - 2047 handled by KSW pair 1. TDM timeslots 2048 - 3071 handled by KSW pair 2. TDM timeslots 3072 - 4095 handled by KSW pair 3.

Two TDM highways are supported, TDM 0 and TDM 1. One TDM highway is active and the other is a redundant standby. KSW 0 0, KSW 1 0, KSW 2 0, and KSW 3 0 can be interconnected to form TDM 0. KSW 0 1, KSW 1 1, KSW 2 1, and KSW 3 1 can be interconnected to form TDM 1. The second KSW identifier indicates to which TDM highway the KSW belongs. Expansion KSW (KSWX) cards are used to interconnect the KSW pairs. The KSWX cards are required in each cage with a KSW pair. The chg_ksw_config command specifies the fiber optic connections between the KSWX cards. The KSWX cards for TDM 0 are located in slots U21, U22, and U23. The KSWX cards for TDM 1 are located in slots U9, U8, and U7. The KSWX fiber optic connections for TDM 1 must match the KSWX fiber optic connections for TDM 0. The KSWX in slot U9 mirrors the connections of the KSWX in slot U21. The KSWX in slot U8 mirrors the connections of the KSWX in slot U22. The KSWX in slot U7 mirrors the connections of the KSWX in slot U23. A chg_ksw_config command is required for each KSW pair equipped at the site when more than one KSW pair is equipped. Only one command is required per KSW pair because the fiber optic connections for TDM 0 and TDM 1 match. A warning prompt displays when this command is entered, from which the operator can abort the command. A warning displays when coming out of SYSGEN mode if each set of TDM highway identifiers are not unique in each cage.

3-136

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Format

The command is only issued for InCell sites. The command does not apply to M-Cell sites. Security level Supported by OMC-R GUI Command type Prerequisites 4 Yes B (operator actions required) See the Service Manual BSC/RXCDR (68P02901W38) for information regarding the hardware layout of the KSW pairs. Check the information regarding the hardware layout of the KSW pairs. Respond to the warning prompt after entry of the command. This command is executed in or out of SYSGEN mode.

Operator actions

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 1 - 140 ksw_pair The KSW pair being configured. The range of values is 0 - 3: 0 1 2 3 KSW pair 0 corresponds to KSW 0 0 and KSW 0 1 KSW pair 1 corresponds to KSW 1 0 and KSW 1 1 KSW pair 2 corresponds to KSW 2 0 and KSW 2 1 KSW pair 3 corresponds to KSW 3 0 and KSW 3 1 BSC or RXCDR BTS

kswx_connected_to_hwy_0 The KSWX pair that connects this KSW pair to highway portion 0. The KSWX pair is in the same cage as the KSW pair being configured. Valid values are 0 - 3.

68P02901W23-S

3-137 Nov 2009

Examples

Chapter 3: Device/function related commands

KSWX pairs are defined as: 0 1 2 3 The highway portion is the same as the KSW pair being configured. KSWX cards in slots U21 (EXP KSWX A0) and U9 (EXP KSWX B0). KSWX cards in slots U22 (EXP KSWX A1) and U8 (EXP KSWX B1). KSWX cards in slots U23 (EXP KSWX A2) and U7 (EXP KSWX B2).

kswx_connected_to_hwy_1 The KSWX pair that connects this KSW pair to highway portion 1. The KSWX pair is in the same cage as the KSW pair being configured. This parameter is not required if KSW pairs 1, 2, and 3 are not equipped. Valid values are 0 - 3. kswx_connected_to_hwy_2 The KSWX pair that connects this KSW pair to highway portion 2. The KSWX pair is in the same cage as the KSW pair being configured. This parameter is not required if KSW pairs 2 and 3 are not equipped. Valid values are 0 - 3. kswx_connected_to_hwy_3 The KSWX pair that connects this KSW pair to highway portion 3. The KSWX pair is in the same cage as the KSW pair being configured. This parameter is not required if KSW pair 3 is not equipped. Valid values are 0 - 3.

Examples
Example 1
This example describes the KSWX fiber optic connections for a standard 4 cage expanded BSC with redundancy. The chg_ksw_config commands for configuring the following expanded setup are described. CAGE 0: KSW 0 0 and KSW 0 1 (KSW Pair 0) are equipped in CAGE 0 KSWX in slot U21 is connected to KSWX in cage 1 slot U21 KSWX in slot U22 is connected to KSWX in cage 2 slot U21 KSWX in slot U23 is connected to KSWX in cage 3 slot U21 KSWX in slot U9 is connected to KSWX in cage 1 slot U9 KSWX in slot U8 is connected to KSWX in cage 2 slot U9 KSWX in slot U7 is connected to KSWX in cage 3 slot U9 CAGE 1: KSW 1 0 and KSW 1 1 (KSW pair 1) are equipped in CAGE 1 KSWX in slot U21 is connected to KSWX in cage 0 slot U21 KSWX in slot U22 is connected to KSWX in cage 2 slot U22

3-138

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Examples

KSWX in slot U23 is connected to KSWX in cage 3 slot U22 KSWX in slot U9 is connected to KSWX in cage 0 slot U9 KSWX in slot U8 is connected to KSWX in cage 2 slot U8 KSWX in slot U7 is connected to KSWX in cage 3 slot U8 CAGE 2: KSW 2 0 and KSW 2 1 (KSW pair 2) are equipped in CAGE 2 KSWX in slot U21 is connected to KSWX in cage 0 slot U22 KSWX in slot U22 is connected to KSWX in cage 1 slot U22 KSWX in slot U23 is connected to KSWX in cage 3 slot U23 KSWX in slot U9 is connected to KSWX in cage 0 slot U8 KSWX in slot U8 is connected to KSWX in cage 1 slot U8 KSWX in slot U7 is connected to KSWX in cage 3 slot U7 CAGE 3: KSW 3 0 and KSW 3 1 (KSW pair 3) are equipped in CAGE 3 KSWX in slot U21 is connected to KSWX in cage 0 slot U23 KSWX in slot U22 is connected to KSWX in cage 1 slot U23 KSWX in slot U23 is connected to KSWX in cage 2 slot U23 KSWX in slot U9 is connected to KSWX in cage 0 slot U7 KSWX in slot U8 is connected to KSWX in cage 1 slot U7 KSWX in slot U7 is connected to KSWX in cage 2 slot U7 The commands for configuring the expansion are: chg_ksw_config 0 0 0 1 2 3 chg_ksw_config 0 1 1 0 2 3 chg_ksw_config 0 2 1 2 0 3 chg_ksw_config 0 3 1 2 3 0

68P02901W23-S

3-139 Nov 2009

Examples

Chapter 3: Device/function related commands

For example, in the command chg_ksw_config 0 2 1 2 0 3 for KSW pair 2: Parameter... location ksw_pair kswx_connected_to_hwy_0 with value... 0 2 1 indicates that... this parameter is the BSC. this parameter is for the KSW pair 2 which is in cage 2. the KSWXs in slot U21 and U9 in the cage with KSW pair 2, connect to the cage with KSW pair 0. the KSWXs in slot U22 and U8 in the cage with KSW pair 2, connect to the cage with KSW pair 1. the highway number is the same as the KSW pair number. the KSWXs in slot U23 and U7 in the cage with KSW pair 2, connect to the cage with KSW pair 3.

kswx_connected_to_hwy_1

kswx_connected_to_hwy_2 kswx_connected_to_hwy_3

0 3

Example 2
Slot U7 can contain a CLKX card or a KSWX card. If a chg_ksw_config command applies to slot U7, the BSC checks to see if a CLKX card has been equipped in the slot. CLKX slot utilization is specified in the GCLK equip command. In this example, the BSC rejects a change because a CLKX has been equipped in slot U7: equip 0 gclk

System response
Enter the device identifier for the GCLK: 0 Enter the cage number: 0 Is CLKX 0 (slot U7) present?: yes Is CLKX 1 (slot U6) present?: no Is CLKX 2 (slot U5) present?: no COMMAND ACCEPTED MMI-RAM 0115 -> chg_ksw_config bsc 0 0 3 2 1 COMMAND REJECTED: Slot U7 is in use by a CLKX card.

3-140

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

References

References
Related command
disp_element on page 3-272.

68P02901W23-S

3-141 Nov 2009

chg_level

Chapter 3: Device/function related commands

chg_level

{27508}

Description
The chg_level command is a dummy command provided to support legacy customer scripts which require this command to change to a different security level. Security level Supported by OMC-R GUI Command type Prerequisites 1 No A (no operator actions) None

Format
Syntax
chg_level

Input parameters
There are no input parameters since the command is interactive.

Examples
Example 1
In the following example, the security level is not changed. The password is not displayed when entered: chg_level

System response
Enter password for security level you wish to access: 3stooges Enter password for security level you wish to access: 4beatles Current security level is unchanged

3-142

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

References

Example 2
In the following example, the security level is not changed. The password is not displayed when entered: chg_level

System response
Enter password for security level you wish to access: anything Enter password for security level you wish to access: random Current security level is unchanged

References
Related command
disp_level on page 3-325.

68P02901W23-S

3-143 Nov 2009

chg_rtf_freq

Chapter 3: Device/function related commands

chg_rtf_freq

Description
The chg_rtf_freq command changes the absolute radio frequency channel for a particular RTF. This operation causes a carrier to be taken out of service. Calls are lost if no other carrier is available. A long warning prompt is presented when this command is invoked. The operator aborts the command at the warning. Security level Supported by OMC-R GUI Command type Prerequisites 4 Yes B (operator actions required) In a synthesizer hopping system: If the frequency is already defined as hopping in all the RTF hopping systems, a new frequency is added when hopping is enabled. Applicable for non-BCCH RTF only. If FHIs are enabled, it is not allowed for BCCH RTFs. The new frequency is added when hopping is disabled regardless of whether the frequency is already a hopping frequency.

In a baseband hopping system: This command is rejected outside SYSGEN ON mode if the RTF has hopping FHIs and any FHIs are enabled. This command automatically updates the frequency in the mobile allocation if all associated FHIs are disabled and the original frequency is already in the MA list.

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

3-144

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Description

To have different DRI/RTF group identifiers, the BSS requires DRI/RTFs within a cell to have different frequency types. When the inner_zone_alg parameter is set to 3 (specifying Dual Band), the frequency type as defined by the secondary band determines the ARFCN range for an inner zone RTF. The BSS requires primary and secondary band RTFs in a Dual Band Cell to be configured with the DRI/RTF group identifier associated with their band. If there is an attempt to use the same DRI/RTF group identifier for RTFs in both the primary and secondary bands of a Dual Band Cell, an error message is printed and the command is rejected. The cabinets to which the DRIs in each zone are equipped must allow the primary and secondary band frequency types.

Dependencies

In PCS 1900 systems, the maximum transmit power (max_tx_bts) limits the frequency entered. If the frequency is a block edge ARFCN, the max_tx_bts must be greater than or equal to 4 (less than 36 dBm) unless one of the following are true: The block edge ARFCN is between the adjacent frequency blocks that are available to the BTS. ARFCNs 512 and 810 are always limited. The inner_zone_alg parameter is set in a chg_cell_element command to value 1. That is, Concentric Cell feature enabled and the power based use algorithm used. The block edge frequency is defined to be an inner zone carrier with a maximum transmit power level less that 36 dBm. Block edges are 512, 585, 587, 610, 612, 685, 687, 710, 712, 735, 737, and 810.

Operator actions

Respond to the warning prompt presented when this command is entered.

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

68P02901W23-S

3-145 Nov 2009

Format

Chapter 3: Device/function related commands

Format
Syntax
chg_rtf_freq <frequency> <location> <rtf_id1> <rtf_id2>

Input parameters
frequency Identifies the absolute radio frequency channel. The range of valid values varies by frequency type. The range of values is: 1 - 124 (PGSM) 0, 1 - 124, 975 - 1023 (EGSM) 512 - 885 (DCS1800) 512 - 810 (PCS1900) 128 - 251 (GSM850)

NOTE
The EGSM values are available only if the egsm_bcch_sd parameter is enabled.

location Specifies the radio frequency channel location: 0 or bsc 1 - 140 rtf_id1 First device identifier. The range of values is 0 - 5. rtf_id2 Second device identifier. The range of values is 0 - 11. BSC BTS

Example
This example changes the frequency channel to 99 for RTF 5 11 at BTS 40.

3-146

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

References

chg_rtf_freq 99 40 5 11 Where: 99 40 5 11 is: frequency location rtf_id1 rtf_id2

System response
WARNING: This operation may cause a carrier to be taken out of service and calls affected by this carrier may be lost. Loss of calls depends on the availability of other carriers. Are you sure (y=yes,n=no)? y COMMAND ACCEPTED

References
Related information
The range of values for GSM Phase 2 is: PGSM RTF_BCCH RTF_NON_BCCH EGSM RTF_BCCH RTF_NON_BCCH DCS1800 RTF_BCCH RTF_NON_BCCH PCS1900 RTF_BCCH RTF_NON_BCCH 1 - 124 1 - 124 1 - 124 1 - 124 or 0, 975 - 1023 512 - 885 512 - 885 512 - 810 512 - 810

Related commands
add_rtf_path on page 3-50 disp_rtf_path on page 3-381 copy_path on page 3-187 del_rtf_path on page 3-204

68P02901W23-S

3-147 Nov 2009

chg_severity

Chapter 3: Device/function related commands

chg_severity

Description
The chg_severity command changes the severity of device and non-reconfiguration alarms. The number of alarms that can be modified is limited to 100. Security level Supported by OMC-R GUI Command type Prerequisites 4 Yes A (no operator actions) None

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

Format
Syntax
chg_severity <device_name> <alarm_code> <severity>

Input parameters
device_name The name of the device, such as GPROC, MSI or DRI, to be modified. alarm code The decimal number identifying the alarm code for the device to be modified. Refer to Alarm devices on page 3-20 for the ranges of alarm codes for each device. Refer to the Maintenance Information: Alarm Handling at the OMC-R (68P02901W26) manual for a list of all alarms and the corresponding alarm codes for each device.

3-148

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Example

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: gproc 8 critical is: device_name alarm_code severity

System response
COMMAND ACCEPTED

References
Related command
disp_severity on page 3-383.

68P02901W23-S

3-149 Nov 2009

chg_smscb_msg

Chapter 3: Device/function related commands

chg_smscb_msg

Description
The chg_smscb_msg command changes a selected CBCH background message and the language in which it is presented. Message numbers uniquely identify the background messages. The background message in all cells at all sites connected to the BSC can be modified. When the command is entered, the MMI responds with an Enter the message prompt. Enter the CBCH background message after the MMI prompt. The GSM standard message can consist of up to 93 characters, entered in hexadecimal or ASCII notation, and terminated by pressing the RETURN key. The ASCII and hexadecimal methods of input can be interspersed in the same message. The following two messages are equivalent: Motorola Cellular \4d\6f\74\6f\72\6f\6c\61 \43\65\6c\6c\75\6c\61\72 Because terminals handle automatic truncation in different ways, it is recommended that messages longer than one line are truncated explicitly by the operator, to form strings shorter than the length of one line. A message can be truncated anywhere by keying \ followed by RETURN. The \ must not separate a hexadecimal character otherwise the two parts read as two separate ASCII characters. The message created using this command is displayed using the disp_cbch_state command. Security level Supported by OMC-R GUI Command type Prerequisites 4 Yes A (no operator actions) Short Message Service (SMS) is a purchasable option which must be installed on the system. The chg_element cbch_enabled command must be used before the chg_smscb_msg command is successfully used.

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

3-150

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Format

Format
Syntax
chg_smscb_msg <msg_num> <message_id> <gs> <msg_code> <update_number> <data_coding_scheme><cell_desc> chg_smscb_msg <msg_num> <message_id> <gs> <msg_code> <update_number> <data_coding_scheme>all

Input parameters
msg_num Uniquely identifies the number of the message for a given cell. The range of values is 0 - 3. message_id The ITU standard identifier for the background message. The range of values is 0 - 65535. gs Geographical scope. This parameter indicates the area over which the message is unique. The range of values is 0 - 3, where: 0 1 2 3 msg_code The ITU standard message code; used to differentiate between messages of the same source and type. The range of values is 0 - 1023. update_number Refers to the number of an update to an existing message. The range of values is 0 - 15. This number used to be automatically incremented for each update to a message. As an input parameter, it now allows the operator to specify a particular update. For example, the same update of a message in a new cell is used as in the existing cells. Immediate, Cell Wide Normal, PLMN Wide Normal, Location Area Wide Normal, Cell Wide

68P02901W23-S

3-151 Nov 2009

Format

Chapter 3: Device/function related commands

data_coding_scheme This parameter determines the language for the CBCH background message. The following languages are available: 0 - German 1 - English 2 - Italian 3 - French 4 - Spanish 5 - Dutch 6 - Swedish 7 - Danish 8 - Portuguese 9 - Finnish 10 - Norwegian 11 - Greek 12 - Turkish 13 - Hungarian 14 - Polish 32 - Czech

NOTE
The values of 15 - 31 and 33 - 255 are not specified for the data_coding_scheme. Only the listed languages are currently available.

cell_desc The GSM cell identifier (either the cell name or cell number) for the cell being modified. GSM cell ID of the cell to be modified, preceded by cell_number=. The format for the GSM cell ID depends on: The system used (PGSM, EGSM, DCS1800, PCS1900) Whether the seven parameter GSM cell ID format or the four parameter GSM cell ID format is enabled.

The name of the cell created using the cell_name command is entered in place of the cell_number. When the cell name is entered, it must be placed inside double quotation marks and cell_name= must precede it. The value all is a valid input for cell_desc; this value changes the specified messages for all cells at the BSS.

NOTE
This command responds to the shortened input parameter cell= allowing entry of either the cell_number or the cell_name without further definition.

3-152

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Examples

Examples
Example 1
This example changes the CBCH background message for cell_desc=5 4 3 2 1 61986 34944 to have a message number of 0, a message ID of 1234, a geographical scope of 2, a message code of 0, an update number of 0, and a language ID of 1. chg_smscb_msg 0 1234 2 0 0 1 cell_number=5 4 3 2 1 61986 34944 Where: 0 1234 2 0 0 1 cell_number=5 4 3 2 1 61986 34944 is: message_number message_id geographical_scope message_code update_number data_coding_scheme cell_desc

System response
Enter the Message: <This is the first line of the message . . . .

This is the last line of the message.> COMMAND ACCEPTED

68P02901W23-S

3-153 Nov 2009

References

Chapter 3: Device/function related commands

Example 2
This example changes the CBCH background message for all cells to have a message ID of 1234 and a language ID of 1. chg_smscb_msg 0 1234 2 0 0 1 all Where: 0 1234 2 0 0 1 all is: message_number message_id geographical_scope message_code update_number data_coding_scheme cell_desc; indicates changes to all cells

System response
Enter the Message: <This is the only line of the message.> COMMAND ACCEPTED

References
Related information
Table 3-30 lists SMS special characters. Alphabetical characters that cannot be directly entered from the keyboard are included in messages by using the backslash (\) character followed by a two character value. The first character is a number from 0 to 7. The second character is a hexadecimal value (0 to F) corresponding to the row in the table. For example, the city of Kln could be included in a message by entering K\7Cln.

Table 3-30
0 0 1 2 3 4 @ $

SMS special characters

1 _ 2 Space ! # 3 0 1 2 3 4 4 A B C D 5 P Q R S T 6 a b c d 7 p q r s t Continued

3-154

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

References

Table 3-30
0 5 6 7 8 9 A B C D E F

SMS special characters (Continued)

1 Not Used 2 % & ' ( ) * + , . / 3 5 6 7 8 9 : ; < = > ? 4 E F G H I J K L M N O 5 U V W X Y Z 6 e f g h i j k l m n o 7 u v w x y z

Line Feed Carriage Return

GSM technical specification

The permitted alphabet is defined in 03.38.

Related commands
del_smscb_msg on page 3-206 disp_cbch_state on page 3-237

68P02901W23-S

3-155 Nov 2009

chg_throttle

Chapter 3: Device/function related commands

chg_throttle

Description
The chg_throttle command changes the throttle period for an intermittent alarm. Security level Supported by OMC-R GUI Command type Prerequisites 4 Yes A (no operator actions) None

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

Format
Syntax
chg_throttle <device_name> <alarm_code> <throttle_count>

Input parameters
device_name Name that uniquely identifies the device. alarm_code Identifies the alarm to be throttled; the range is 0 - 254. Some of the codes are obsolete, refer to the manual Maintenance Information: Alarm handling at the OMC-R (68P02901W26) for usable alarm codes. throttle_count Specifies the new throttle count in minutes. A value of 0 means throttling is disabled. The range of values is 0 - 1440.

3-156

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Example

Example
This example changes the throttle period for alarm code 1 of an MMS to 10 minutes. chg_throttle mms 1 10 Where: mms 1 10 is: device_name alarm_code throttle_count

System response
COMMAND ACCEPTED

References
Related command
disp_throttle on page 3-386.

68P02901W23-S

3-157 Nov 2009

chg_time

Chapter 3: Device/function related commands

chg_time

Description
The chg_time command sets the real-time system clock. The clock can be set to a specific date and time of day or changed relative to the current time of day. The relative change is useful for changing the clock for daylight savings time. Security level Supported by OMC-R GUI Command type Prerequisites 4 No A (no operator actions) None

Format
Syntax
chg_time <year> <month> <day> <hour> <minute> <second> or chg_time <+/-> <hours> <minutes>

Input parameters
year Value identifying the year. The year is entered in the four-digit format. The range of values is 1980 - 2100. month Value identifying the month. The range of values is 1 - 12. day Value identifying the day of the month. The range of values is 1 - 31.

3-158

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Examples

<+/-> A plus or minus, as the first argument, adds or subtracts the specified number of hours and minutes from the current time on the system clock. hour Value identifying the hour. The range of values is 0 - 23. This value can also be used to specify the number of hours to be added or subtracted to the current system time. minute Value identifying the minute. The range of values is 0 - 59. This value can also be used to specify the number of minutes to be added or subtracted to the current system time. second Value identifying the second. The range of values is 0 - 59.

Examples
Example 1
In this example, the system clock is set to year (1993), month (November), day (12th), and time (09:23:00): chg_time 1993 11 12 9 23 0 Where: 1993 11 12 9 23 0 is: year month day hour minute second

System response
Mon Nov 12 09:23:00 1993

68P02901W23-S

3-159 Nov 2009

References

Chapter 3: Device/function related commands

Example 2
In this example, one hour is added to the current time for daylight savings time: chg_time + 1 0 Where: + 1 0 is: add to the system clock time. hours to be added. minutes to be added.

System response
Mon Nov 12 10:23:00 1995

References
Related commands
chg_throttle on page 3-156 time_stamp on page 3-548

3-160

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

chg_ts_usage

Description
The chg_ts_usage command does the following: Reserves timeslots Nails timeslots Frees reserved timeslots Frees nailed timeslots

The chg_ts_usage command supports the following operations: RESERVE FREE This operation reserves timeslots. A timeslot cannot be used for any connections when it is reserved. This operation frees timeslots that have been reserved or nailed using the NAIL or RESERVE operations. It does not free timeslots that have been nailed using the NAIL_PATH operation. Timeslots freed using this operation become unused and can be used for any connections. This operation frees the timeslots of a NAIL_PATH nailed connection between different sites. Timeslots freed using this operation become unused and can be used for normal connections. This operation establishes a nailed connection between two timeslots at the same site. This operation establishes a nailed connection between two timeslots at different sites.

FREE_PATH

NAIL NAIL_PATH

The E1 timeslot mapping on an HDSL link that supports 16 E1 timeslots restricts the timeslots available to a number within the range 0 - 31. The number of timeslots that can be RESERVE, NAIL, FREE_PATH, or NAIL_PATH is restricted to 1 on HDSL links where only 16 timeslots are available. The system rejects a chg_ts_usage nail_path command when the path contains a ts_switch. Security level Supported by OMC-R GUI Command type Prerequisites 4 No B (operator actions) MSIs must be equipped before timeslots can be nailed or reserved using the chg_ts_usage command. The system rejects the chg_ts_usage command when a 16 kbit/s XBL link is equipped on the timeslot. Respond to command prompts.

Operator actions

68P02901W23-S

3-161 Nov 2009

Format

Chapter 3: Device/function related commands

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

Format
Syntax
chg_ts_usage The system responds with a series of prompts for input parameters dependent on the action requested.

Input parameters
The parameters used with this command are prompted for in the system response and are dependent upon the specified operation. Refer to the descriptions for function and valid values of the input parameter prompts: Enter Action: The type of operation to be performed. This field is entered as upper or lower case characters with one of: RESERVE FREE NAIL FREE_PATH NAIL_PATH Reserve timeslots. Free timeslots that have been reserved or nailed using the NAIL or RESERVE operations. Establish a nailed connection between two timeslots at the same site. Free the timeslots of a nailed connection between different sites. Establish a nailed connection between two timeslots at different sites.

Enter Site Identifier: Specifies the location of the MMS at one end of the E1 Mbit/s link for FREE, RESERVE, and NAIL operations only. Values are: 0 or bsc 1 to 140 BSC BTS

Enter MMS 1 Identifiers: First and second identifiers of the MMS at one end of the E1 link. Values are:

3-162

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Format

First identifier: 0 to 55 0 to 123 0 to 9 Second identifier: 0 or 1 0 to 5 for Horizon II site. BSC RXCDR BTS

Enter MMS 2 Identifiers: First and second identifiers of the MMS at the other end of the E1 link. Values are: First identifier: 0 to 55 0 to 123 0 to 9 Second identifier: 0 or 1 0 to 5 for Horizon II site. BSC RXCDR BTS

Enter Starting Timeslot: First of the contiguous timeslots to be reserved or freed using the RESERVE or FREE operations only. Values are: 1 to 31 For 2.048 Mbit/s E1 Links, including a 32/16 timeslot HDSL link

Enter Starting Timeslot for MMS 1: Start timeslot number for MMS1 used with the NAIL, NAIL_PATH, or FREE_PATH operations only. Values are: 1 to 31 For 2.048 Mbit/s E1 Links

Enter Starting Timeslot for MMS 2: Start timeslot number for MMS2 used with the Nail, NAIL_PATH, or FREE_PATH operations only. Values are: 1 to 31 For 2.048 Mbit/s E1 Links

Enter Start Site:

68P02901W23-S

3-163 Nov 2009

Examples

Chapter 3: Device/function related commands

The start SITE to be nailed or freed using the NAIL_PATH or FREE_PATH operations only. Values are: 0 to 100 BSC or BTS

Enter End Site: The end SITE to be nailed or freed using the NAIL_PATH or FREE_PATH operations only. Values are: 0 to 100 BTS or BSC

Enter Path Identifiers The PATH to be nailed or freed using the NAIL_PATH or FREE_PATH operations only. This represents the terminating site of the path. Values are: 0 to 100 BSC or BTS

Enter Number of Timeslots Requested: The number of contiguous timeslots to be reserved, nailed, or freed. Values are: 1 to 31 For 2.048 Mbit/s E1 Links

Examples
Example 1
In this example, the contiguous timeslots from 16 through 31 at BTS 26 for MMS 1 0 are reserved: chg_ts_usage

System response
Enter action: RESERVE 26 1 0 16 16

Enter Site Identifier: Enter MMS Identifiers:

Enter Starting Timeslot:

Enter Number of Timeslots Requested:

3-164

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

References

Example 2
In this example, a PATH is nailed from timeslot 5 of MMS 1 0 to timeslot 7 of MMS 0 1 at BTS 26: chg_ts_usage

System response
Enter Action: NAIL 26 1 0 5

Enter Site Identifier:

Enter MMS 1 Identifiers:

Enter Starting Timeslot for MMS 1: Enter MMS 2 Identifiers: 0 1

Enter Starting Timeslot for MMS 2:

7 3

Enter Number of Timeslots Requested:

Example 3
In this example, the PATH identifier is 1 1 and timeslot 5 of site 1 is nailed to timeslot 6 of site 2: chg_ts_usage

System response
Enter action: NAIL_PATH 1 1

Enter Path Identifiers: Enter Start Site: 1

Enter MMS 1 Identifiers:

0 0 5

Enter Starting Timeslot for MMS 1: Enter End Site: 2 1 0

Enter MMS 2 Identifiers:

Enter Starting Timeslot for MMS 2: Enter Number of Timeslots Requested:

6 3

References
Related command
disp_mms_ts_usage on page 3-330.

68P02901W23-S

3-165 Nov 2009

chg_x25config

Chapter 3: Device/function related commands

chg_x25config

Description
The chg_x25config command changes the X.25 link parameters. Security level Supported by OMC-R GUI Command type Prerequisites 4 Yes A (no operator actions) None

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

Format
Syntax
chg_x25config <link type> <x25_parameter> <value>

Input parameters
link type Specifies the type of X.25 link: oml cbl change parameters for all OMLs in the BSS change parameters for all CBLs in the BSS

NOTE
OML parameters are stored in NVRAM on the GPROCs at the BSC; they are not stored in the database. Therefore, OML parameters cannot be changed.

3-166

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Examples

x25_parameter Specifies the type of X.25 parameter being changed for all OMLs or CBLs: packet_size window_size The type of X.25 parameter is shown in the OMC GUI window in BSS View as config_packet_size and config_window_size respectively. value Specifies the new value of the X.25 link: packet_size window_size 128, 256, 512 2-7

Examples
Example 1
The following example changes the X.25 settings for all BSS OMLs: chg_x25 oml window_size 6 Where: oml window_size 6 is: link type x25_parameter value

System response:
COMMAND ACCEPTED

Example 2
The following example changes the X.25 settings for all BSS CBLs: chg_x25 cbl packet_size 256 Where: cbl packet_size 256 is: link type x25_parameter value

68P02901W23-S

3-167 Nov 2009

References

Chapter 3: Device/function related commands

System response
COMMAND ACCEPTED

References
Related command
disp_x25config on page 3-401.

3-168

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

clear_cal_data

Description
The clear_cal_data command clears calibration data previously stored (at the BSC) for a specified radio unit on a per DRI basis. When this command is entered, a warning is displayed that the calibration data for the specified transceiver is cleared. Security level Supported by OMC-R GUI Command type Prerequisites 3 No B (operator action required) This command is not available while in SYSGEN ON mode. This command is not entered at a BTS. The DRI device must be locked. Respond to the warning prompt.

Operator actions

Format
Syntax
clear_cal_data <location> dri <dev_id> <dev_id> [<dev_id>]

Input parameters
location 0 or bsc dri The DRI is the only device permitted for this command. dev_id The first device identifier. The range is 0 - 5. dev_id The second device identifier. The range is 0 - 11. BSC

68P02901W23-S

3-169 Nov 2009

Example

Chapter 3: Device/function related commands

dev_id The third device identifier. This value defaults to 0 if no value is entered.

Example
The following example clears the calibration data for DRI 5 3 0 at site 21: clear_cal_data 21 dri 5 3 0 Where: 21 dri 5 3 0 is: site dri device first dev_id second dev_id third dev_id

System response
Warning: This will clear the calibration data for this transceiver Are you sure (y=yes,n=no)? y COMMAND ACCEPTED

References
Related commands
disp_cal_data on page 3-233 store_cal_data on page 3-534

3-170

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

clear_database

Description
The clear_database command deletes the contents of the CM database.

CAUTION
This command must be used only by personnel who fully understand the consequences. The system is placed in the initial SYSGEN mode when this command is entered. Refer to SYSGEN mode on page 1-43. Security level Supported by OMC-R GUI Command type Prerequisites Operator actions 4 Yes B (operator actions required) This command can only be entered in the SYSGEN ON mode. Place the system in the SYSGEN ON mode before entering this command.

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

Format
Syntax
clear_database

Input parameters
There are no input parameters associated with this command.

68P02901W23-S

3-171 Nov 2009

Example

Chapter 3: Device/function related commands

Example
In this example, the CM database is cleared with the system in SYSGEN ON mode: clear_database

System response
COMMAND ACCEPTED

3-172

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

clear_gclk_avgs

Description
The clear_gclk_avgs command clears the stored LTA values and the stored samples for a specified GCLK or MMS. If this command is entered, the LTA value is set to 80 h and the frequency register readings are cleared. If this command is entered at an InCell site, a prompt for a GCLK ID displays. If this command is entered at a non-InCell site, a prompt for an MMS ID displays.

Clear the LTA values under the following circumstances: The GCLK is replaced. The GCLK is recalibrated. The uplink site does not provide a stable clock source. 3 No A (no operator actions) This command is not allowed while in the SYSGEN ON mode.

Security level Supported by OMC-R GUI Command type Prerequisites

Format
Syntax
clear_gclk_avgs <location>

Input parameter
location Specifies the location of the device: 0 or bsc 1 - 140 BSC BTS

68P02901W23-S

3-173 Nov 2009

Example

Chapter 3: Device/function related commands

Example
In this example, the LTA values for GCLK 1 at InCell SITE 0 are cleared: clear_gclk_avgs 0 Where: 0 is: location

System response
Enter the gclk_id: 1

COMMAND ACCEPTED

References
Related information
The system reads the clock frequency register of each GCLK once every half hour after synchronization when the GCLK is in phase_locked mode. A rolling average for each GCLK is calculated from up to 48 clock frequency register readings. This average is the Long Term Average (LTA). An alarm is generated if 25% or more of the stored clock frequency readings differ from the calculated LTA by more than the value that the lta_alarm_range parameter defines.

Related commands
disp_gclk_avgs on page 3-309 disp_gclk_cal on page 3-311

3-174

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

configure_csfp

Description
The configure_csfp command configures CSFP (Code Storage Facility Processor) devices to sites in the BSS network. This command selects a BSP , BTP , or pool GPROC device, dependent on the CSFP algorithm setting for that site, and converts the selected device to a CSFP device. Security level Supported by OMC-R GUI Command type Prerequisites Operator actions 4 Yes B (Operator actions required) This command can only be executed when the system is SYSGEN ON mode Put the system into SYSGEN ON mode before executing this command.

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

Format
Syntax
configure_csfp

Input parameters
There are no input parameters associated with this command.

Example
This example shows the input required to configure the CSFP devices to sites in the BSS network. configure_csfp

68P02901W23-S

3-175 Nov 2009

References

Chapter 3: Device/function related commands

System response
COMMAND ACCEPTED

References
Related information
Depending on the CSFP stealing algorithm (set using the chg_csfp command), the device stolen to become the CSFP can vary. If the algorithm is set to any (the default value), an equipped GPROC is chosen first instead of choosing the redundant BSP or BTP device.

Algorithm set
NONE STBY No CSFPs are configured at the site. The location does not matter. If location is BSC and two BSPs are equipped then one is configured as CSFP . If location is a remote BTS and two BTPs are equipped then one is configured as CSFP . For either BSC or remote BTS locations, an equipped GPROC is configured as CSFP . First the POOL algorithm is applied and then the STBY algorithm is applied. ANY is the default algorithm.

POOL ANY

NOTE
If there is only one GPROC in the second cage, it cannot be chosen as a configured CSFP .NOTE.

Related Commands
chg_csfp on page 3-95 disp_csfp on page 3-263 unconfigure_csfp on page 3-568

3-176

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

connection_code

Description
The connection_code command is used for the following: To change operator-defined code that triggers the resource trace of a call. To turn the Call Connectivity Trace feature off. To display the current value of operator-defined code. 2 No A (no operator action required) The GPRS must be unrestricted to assess a PCU site.

Security level Supported by OMC-R GUI Command type Prerequisites

Format
Syntax
connection_code [<operator-defined code>]

Input parameter
operator-defined code Six-digit number; each digit can be from 0 to 9.

Examples
Example 1
The following example changes the value of the operator-defined code to 123456: connection_code 123456 Where: 123456 is: the operator-defined code.

68P02901W23-S

3-177 Nov 2009

Examples

Chapter 3: Device/function related commands

System response
COMMAND ACCEPTED

Example 2
The following example turns off the Call Connectivity Trace feature: connection_code

System response
COMMAND ACCEPTED

Example 3
The following example displays the current value for the operator-defined code: connection_code

System response
Connection code is: 123456

NOTE
If there is no connection code, the system response is: No Connection code exists.

3-178

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

copy_cell

Description
The copy_cell command creates a cell by copying the information in an existing cell. This command cannot copy a cell source or neighbor information. Also, the cell BSIC is not copied and a new BSIC must be entered for the cell being created (destination cell). If dynamic allocation is in use at the source cell, the system sets the value of the dynet_tchs_reserved parameter to the default (0), regardless of the setting in the source cell. The value of dynet_tchs_reserved does not change at the source cell. The value of the dynet_tchs_reserved parameter at the destination cell is always defaulted to 0. This command is rejected if it is entered for an M-Cellcity, Horizonmicro or Horizoncompact site where a cell exists. Only one cell is permitted at these sites. An extended source cell is copied as an extended destination cell. If used on a coincident cell, the copy_cell command sets the coincident cell to an invalid value, and the coincident_mb to 0 at the new cell. Security level Supported by OMC-R GUI Command type Prerequisites Operator actions 4 Yes B (operator actions required) None Respond to the warning prompt presented when this command is entered.

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

Format
Syntax
copy_cell <source_cell_id> <dest_gsm_cell_id> <dest_location> <dest_bsic>[cell_name]

68P02901W23-S

3-179 Nov 2009

Format

Chapter 3: Device/function related commands

Input parameters
source_cell_id GSM cell ID of the existing cell being copied. The format for the GSM cell ID depends on: The system used (PGSM, EGSM, DCS1800, PCS1900, or GSM850). Whether the seven parameter GSM cell ID format or the four parameter GSM cell ID format has been enabled.

The cell name created using the cell_name command is entered in place of the source_cell_id. When the cell name is entered, it must be placed inside double quotation marks. dest_gsm_cell_id GSM cell ID of the new cell to be created. A cell name is not entered for the destination Cell ID. The format for the GSM cell ID depends on: The system used (PGSM, EGSM, DCS1800, PCS1900, or GSM850). Whether the seven parameter GSM cell ID format or the four parameter GSM cell ID format has been enabled.

dest_location Specifies the location of the new cell. Values are: 0 or bsc 1 - 140 dest_bsic Specifies the BSIC of the new cell. The range of values for the bsic is 0 - 63. cell_name A cell name can be specified for the dest_gsm_cell_id, as if created using the cell_name command. This cell name must be placed inside double quotation marks. The full format is given in the cell_name parameter description. BSC BTS

Inclusions
The following parameters are copied when the copy_cell command is executed: alt_qual_proc attach_detach en_incom_ho extended_paging_active ms_txpwr_max_cch ms_txpwr_max_def

3-180

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Format

ba_alloc_proc bs_ag_blks_res bs_pa_mfrms bep_period bep_period2 bsic bts_p_con_ack bts_p_con_interval bts_power_control_allowed ccch_conf cell_bar_access_class cell_bar_access_switch cell_bar_qualify cell_reselect_hysteresis cell_reselect_offset cell_reselect_param_ind decision_1_dl_rxlev_av_h decision_1_dl_rxlev_av_ih decision_1_dl_rxlev_av_p decision_1_dl_rxqual_av_h decision_1_dl_rxqual_av_p decision_1_n1 decision_1_n2 decision_1_n3 decision_1_n4 decision_1_n5 decision_1_n6 decision_1_n7 decision_1_n8 decision_1_ncell_rxlev_ av_h_calc

frequency_type full_pwr_rfloss gprs_par_wait_ind handover_power_level handover_recognized_period ho_margin_def hr_fr_hop_count hr_intracell_ho_allowed hr_res_ts imrm_dcs1800_weight imrm_egsm_weight imrm_force_recalc imrm_pgsm_weight imrm_umts_weight inner_hr_usage_thres intave inter_cell_handover_allowed interfer_ho_allowed intr_cell_handover_allowed l_rxlev_dl_h l_rxlev_dl_p l_rxlev_ul_h l_rxlev_ul_p l_rxqual_dl_h l_rxqual_dl_h_hopping_hr l_rxqual_dl_h_hr l_rxqual_dl_p l_rxqual_dl_p_hopping_hr l_rxqual_dl_p_hr l_rxqual_ul_h

mspwr_alg ncc_of_plmn_allowed new_calls_hr number_of_preferred_cells number_sdcchs_preferred penalty_time pfc_be_arp pow_inc_step_size_dl

pow_red_step_size_dl pow_inc_step_size_ul pwr_handover_allowed pwrc qos_mtbr_be_dl qos_mtbr_be_ul qos_mtbr_bg_dl qos_mtbr_bg_ul qos_mtbr_i1_dl qos_mtbr_i1_ul qos_mtbr_i2_dl qos_mtbr_i2_ul qos_mtbr_i3_dl qos_mtbr_i3_ul radio_link_timeout rapid_pwr_down reconfig_fr_to_hr

reestablish_allowed report_resource_tch_f_high_ water_mark report_resource_tch_f_low_ water_mark rpd_offset rpd_period rpd_trigger

decision_1_p_bgt_rxlev_av_h l_rxqual_ul_h_hopping_hr decision_1_p1 decision_1_p2 l_rxqual_ul_h_hr l_rxqual_ul_p

68P02901W23-S

3-181 Nov 2009

Format

Chapter 3: Device/function related commands

decision_1_p3 decision_1_p4 decision_1_p5 decision_1_p6 decision_1_p7 alt_qual_proc attach_detach ba_alloc_proc bs_ag_blks_res bs_pa_mfrms bep_period bep_period2 bsic bts_p_con_ack bts_p_con_interval bts_power_control_allowed ccch_conf cell_bar_access_class cell_bar_access_switch cell_bar_qualify cell_reselect_hysteresis cell_reselect_offset cell_reselect_param_ind decision_1_dl_rxlev_av_h decision_1_dl_rxlev_av_ih decision_1_dl_rxlev_av_p decision_1_dl_rxqual_av_h decision_1_dl_rxqual_av_p decision_1_n1 decision_1_n2 decision_1_n3 decision_1_n4 decision_1_n5

l_rxqual_ul_p_hopping_hr l_rxqual_ul_p_hr l_rxqual_ul_p_amr_fr l_rxqual_dl_p_amr_fr en_incom_ho extended_paging_active frequency_type full_pwr_rfloss gprs_par_wait_ind handover_power_level handover_recognized_period ho_margin_def hr_fr_hop_count hr_intracell_ho_allowed hr_res_ts imrm_dcs1800_weight imrm_egsm_weight imrm_force_recalc imrm_pgsm_weight imrm_umts_weight inner_hr_usage_thres intave inter_cell_handover_allowed interfer_ho_allowed intr_cell_handover_allowed l_rxlev_dl_h l_rxlev_dl_p l_rxlev_ul_h l_rxlev_ul_p l_rxqual_dl_h l_rxqual_dl_h_hopping_hr l_rxqual_dl_h_hr l_rxqual_dl_p

rxlev_access_min rxlev_min_def sdcch_ho ms_txpwr_max_cch ms_txpwr_max_def mspwr_alg ncc_of_plmn_allowed new_calls_hr number_of_preferred_cells number_sdcchs_preferred penalty_time pfc_be_arp pow_inc_step_size_dl pow_red_step_size_dl pow_inc_step_size_ul pwr_handover_allowed pwrc qos_mtbr_be_dl qos_mtbr_be_ul qos_mtbr_bg_dl qos_mtbr_bg_ul qos_mtbr_i1_dl qos_mtbr_i1_ul qos_mtbr_i2_dl qos_mtbr_i2_ul qos_mtbr_i3_dl qos_mtbr_i3_ul radio_link_timeout rapid_pwr_down reconfig_fr_to_hr reestablish_allowed report_resource_tch_f_high_ water_mark report_resource_tch_f_low_ water_mark

3-182

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Format

decision_1_n6 decision_1_n7 decision_1_n8 decision_1_ncell_rxlev_ av_h_calc

l_rxqual_dl_p_hopping_hr l_rxqual_dl_p_hr l_rxqual_ul_h l_rxqual_ul_h_hopping_hr

rpd_offset rpd_period rpd_trigger rxlev_access_min rxlev_min_def sdcch_ho sdcch_timer_ho temporary_offset timing_advance_period tlli_blk_coding tx_integer u_rxlev_dl_ih

decision_1_p_bgt_rxlev_av_h l_rxqual_ul_h_hr decision_1_p1 decision_1_p2 decision_1_p3 decision_1_p4 decision_1_p5 decision_1_p6 decision_1_p7 decision_1_p8 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 dl_rxlev_ho_allowed dl_rxqual_ho_allowed dtx_required dyn_step_adj dyn_step_adj_fmpr egprs_init_dl_cs egprs_init_ul_cs emergency_class_switch {26811} ext_ul_no_dat l_rxqual_ul_p l_rxqual_ul_p_hopping_hr l_rxqual_ul_p_hr l_rxqual_ul_p_amr_fr l_rxqual_dl_p_amr_fr l_rxqual_ul_h_amr_fr l_rxqual_dl_h_amr_fr

l_rxqual_dl_h_hopping_amr_fr u_rxlev_dl_p l_rxqual_ul_h_hopping_amr_fr ul_rxlev_ho_allowed l_rxqual_dl_p_hopping_amr_fr u_rxlev_ul_ih l_rxqual_ul_p_hopping_amr_fr u_rxlev_ul_p link_about_to_fail link_fail max_retran max_tx_bts max_tx_ms missing_rpt ms_distance_allowed ms_p_con_ack ms_p_con_interval ms_power_control_allowed u_rxqual_dl_p ul_rxqual_ho_allowed u_rxqual_ul_p u_rxqual_dl_p_hr u_rxqual_ul_p_hr wait_indication_parameters

NOTE
If the Inter-RAT handover option is unrestricted, and UTRAN cells are copied with copy_cell, the following parameters are defaulted in the new cell: fdd_qmin, fdd_qoffset, qsearch_c_initial, qsearch_i, and inter_rat_enabled.

68P02901W23-S

3-183 Nov 2009

Examples

Chapter 3: Device/function related commands

Exceptions
The following is a list of parameters that are not copied, and instead the parameter default values are used when the copy_cell command is executed: bsic bcch_frequency fdd_multirat_reporting fdd_rep_quant freq_share_table_pointer blind_search_preference cbch_enabled cell_name coincident_index coincident_mb dynet_tchs_reserved gsm_cell_id gsm_half_rate_enabled hopping_support inner_zone_alg inter_rat_enable ms_max_range res_ts_less_one_carrier source_cells sw_ts_less_one_carrier serving_band_reporting switch_gprs_pdchs tch_usage_threshold thresholds tx_power_cap trx_pwr_carriers.num_carriers umts_band_preferred umts_cpich_ec_no_min umts_cpich_rscp_min The neighbor definitions also are not copied. If the GPRS feature is unrestricted, the copy_cell command copies the GPRS elements at a cell, except for the following: bvci gprs_enabled ra_colour

equipment_share_table_pointer multiband_reporting ext_range_cell qsearch_c

Examples
Example 1
In this example, information from a cell with cell_number=5 4 3 2 1 61986 34944 is copied to create a cell with cell_number=5 4 3 2 1 61986 34945 at site 0: copy_cell 5 4 3 2 1 61986 34944 5 4 3 2 1 61986 34945 0 6 Where: 5 4 3 2 1 61986 34944 5 4 3 2 1 61986 34945 0 6 is: source_cell_id dest_gsm_cell_id dest_location dest_bsic

System response
COMMAND ACCEPTED

3-184

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Examples

Example 2
In this example, the source cell is identified using the cell_name london-south. copy_cell london-south 5 4 3 2 1 61986 34945 0 6 Where: london-south 5 4 3 2 1 61986 34945 0 6 is: cell_name dest_gsm_cell_id dest_location dest_bsic

System response
COMMAND ACCEPTED

Example 3
In this example, information from a PCS1900 cell with cell_number=543 721 61986 34944 is copied to create a cell with cell_number=543 721 61986 34945 at site 0, with the cell name of paris: copy_cell 543 721 61986 34944 543 721 61986 34945 0 6 paris Where: 543 721 61986 34944 543 721 61986 34945 0 6 paris is: source_cell_id dest_gsm_cell_id dest_location dest_bsic cell_name

System response
COMMAND ACCEPTED

68P02901W23-S

3-185 Nov 2009

References

Chapter 3: Device/function related commands

Example 4
In this example, gsm_half_rate_enabled is set to 1 in the source cell and a new cell is created using the command copy_cell. copy_cell 0 0 1 0 1 1 3 0 0 1 0 1 1 44 2 7 Where: 0010113 0 0 1 0 1 1 44 2 7 is: source_cell_id dest_gsm_cell_id dest_location dest_bsic

System response
COMMAND ACCEPTED: WARNING: The GSM half rate per cell enable parameter has been modified

References
Related information
The GSM cell ID entry format is: a b c d e f g Where: a b c d e f g is: the first digit of the MCC (Mobile Country Code). the second digit of the MCC. the third digit of the MCC. the first digit of the MNC (Mobile Network Code). the second digit of the MNC. the LAC (Local Area Code). the CI (Cell Identity).

Related commands
add_cell on page 3-22 del_cell on page 3-192 disp_cell on page 3-241

3-186

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

copy_path

Description
The copy_path command equips a new PATH device by copying an existing path and extending it to a new site. This facility is useful when adding paths to the network or creating a long branch. The first path to the first BTS can be configured when a path is created using the equip command. This path can be copied or extended to the next BTS. The process can then be repeated to construct paths to all BTS sites on the branch. This command ensures that an HDSL link is only copied between MMSs that support the same number of timeslots, identical link protocol types and HDSL modems that are in a master/slave configuration. The single exception to this rule is when the system cannot check master/slave settings because the HDSL link consists of two external modems. Security level Supported by OMC-R GUI Command type Prerequisites 4 Yes A (no operator actions) None

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

Format
Syntax
copy_path

Input parameters
There are no input parameters since this command is interactive. Table 3-31 lists the prompts and values that must be entered.

68P02901W23-S

3-187 Nov 2009

Example

Chapter 3: Device/function related commands

Table 3-31

copy_path command prompts

Prompt Range 0 - 140 0 - 9 6 - 9 (see NOTE) Default None None

Enter the terminating SITE id to be copied: Enter the Unique PATH id to be copied:

NOTE
If the terminating BTS uses dynamic allocation, the range is 6 - 9. If the terminating BTS does not use dynamic allocation, the range is 0 - 9. Enter the new terminating site id: Enter the unique PATH id: Enter the downstream MSI identifier: Enter the downstream MMS identifier: Enter the upstream MSI identifier: Enter the upstream MMS identifier: 0 - 140 0 - 9 0 - 9 0 or 1 0 - 9 0 or 1 None None None None None None

Example
This example shows a typical dialogue. copy_path

System response
Enter the terminating SITE id to be copied: 4 Enter the Unique PATH id to be copied: 0 Enter the new terminating SITE id: 5 Enter the new Unique PATH id: 0 Enter the downstream MSI identifier: 3 Enter the downstream MMS identifier: 0 Enter the upstream MSI identifier: 3 Enter the upstream MMS identifier: 1 COMMAND ACCEPTED

3-188

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

References

References
Related information
The following figure illustrates that downstream always refers to the direction from the BSC to the BTS. The upstream always describes the direction from the BTS to the BSC.

Related commands
add_rtf_path on page 3-50 disp_rtf_path on page 3-381 chg_rtf_freq on page 3-144 del_rtf_path on page 3-204

68P02901W23-S

3-189 Nov 2009

del_act_alarm

Chapter 3: Device/function related commands

del_act_alarm

Description
The del_act_alarm command deletes an alarm that an active operator can clear.

NOTE
The disp_act_alarm command displays the alarms that the operator can delete. See disp_act_alarm on page 3-225.

Security level Supported by OMC-R GUI Command type Prerequisites

4 Yes A (no operator actions) None

Format
Syntax
del_act_alarm <location> <device_name> <dev_id1> <dev_id2> <dev_id3> <alarm_code>

Input parameters
location Specifies the alarm location: 0 or bsc 1 - 140 {27955A} pcu or pcu_0 BSC BTS PCU

3-190

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Example

device_name Device name that uniquely identifies the device. dev_id1 First device identifier. The range of values is 1 - 128. dev_id2 Second device identifier. The range of values is 0 - 99. dev_id3 Third device identifier. The range of values is 0 - 99. alarm_code Alarm to be deleted. The range of values is 0 - 254.

Example
This example deletes an active alarm for KSW 1 0 0, alarm code 2, at the BSC. del_act_alarm 0 ksw 1 0 0 2 Where: 0 ksw 1 0 0 2 is: location device_name dev_id1 dev_id2 dev_id3 alarm_code

System response
COMMAND ACCEPTED

References
Related commands
disp_act_alarm on page 3-225.

68P02901W23-S

3-191 Nov 2009

del_cell

Chapter 3: Device/function related commands

del_cell

Description
The del_cell command deletes a cell from the CM database. The del_cell command is rejected if the cell specified for deletion is a coincident cell of any other cell at a site that has the Coincident Multiband Handover option enabled. The command is also rejected if any Trace Criteria is with scope as the specified cell. Security level Supported by OMC-R GUI Command type Prerequisites 4 Yes A (no operator actions) If a cell is currently in a DRI descriptor, it cannot be removed. To remove a cell that is included in a DRI descriptor, the DRI must be unequipped first. All trace criteria with scope as the specified cell must be deleted.

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

Format
Syntax
del_cell <cell_id>

Input parameter
cell_id GSM cell ID of the cell to be deleted. The format for the GSM cell ID depends on: The system being used (PGSM, EGSM, DCS1800, PCS1900) Whether the seven parameter GSM cell ID format or the four parameter GSM cell ID format has been enabled.

3-192

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Examples

The name of the cell created using the cell_name command is entered in place of the cell_id. When the cell name is entered, it must be placed inside double quotation marks.

Examples
Example 1
In this example, the cell with cell_number 5 4 3 2 1 61986 34944 (using the seven parameter format) at site number 0 is deleted from the CM database: del_cell 5 4 3 2 1 61986 34944 Where: 5 4 3 2 1 61986 34944 is: cell_id

System response
COMMAND ACCEPTED

Example 2
In this example, the cell with cell_number 987 654 12345 67809 (using the four parameter format) at site number 0 is deleted from the CM database: del_cell 987 654 12345 67809 Where: 987 654 12345 67809 is: 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: london-south is: cell_name

68P02901W23-S

3-193 Nov 2009

References

Chapter 3: Device/function related commands

System response
COMMAND ACCEPTED

Example 4
In this example, an attempt is made to delete cell 5 4 3 2 1 61986 34944 which has trace criteria with scope as the specified cell. del_cell 5 4 3 2 1 61986 34944 Where: 5 4 3 2 1 61986 34944 is: cell_id

System response
COMMAND REJECTED: Delete all Trace Criteria with scope as the specified cell/RTF/site.

References
Related commands
add_cell on page 3-22 disp_gsm_cells on page 3-314 copy_cell on page 3-179 disp_cell on page 3-241

3-194

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

del_conn

Description
The del_conn command updates the BSS database to delete a particular connection between an MMS at the BSC and an MMS at the RXCDR. If the BSC is operating in static mode and CICs are statically assigned to that MMS pair, connectivity cannot be removed for an MMS pair. This only applies to remote transcoding BSC and RXCDR sites. Security level Supported by OMC-R GUI Command type Prerequisites 4 Yes A (no operator actions) All CICs and XBLs must be unequipped before deleting MMS connectivity information. This command can only be entered at the BSC or RXCDR site.

Format
Syntax
del_conn <local_mms_id_1> <local_mms_id_2>

Input parameters
local_mms_id_1 First identifier of the MMS at the local site. The term local site refers to the site where the command is entered. The range of values vary from {22169} 0 - 95 when this command is executed from a BSC. The range varies from 0 to 123 when executed from an RXCDR. local_mms_id_2 Second identifier of the MMS at the local site. Values are 0 or 1.

68P02901W23-S

3-195 Nov 2009

Example

Chapter 3: Device/function related commands

Example
This example shows connectivity information deleted for MMS 4 0 at the BSC. del_conn 4 0 Where: 4 0 is: local_mms_id_1 local_mms_id_2

System response
COMMAND ACCEPTED

References
Related commands
add_conn on page 3-33 disp_conn on page 3-261 mod_conn on page 3-442

3-196

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

del_neighbor

Description
The del_neighbor command deletes neighbor cells, including Blind Search Neighbors, from a cell neighbor list. If two Cell IDs are entered, the second Cell ID is removed from the first cell neighbor list. If all is entered in place of the second cell ID, then every neighbor in the specified cell neighbor list is deleted. If all is entered in place of the first Cell ID, then the cell is deleted from all associated neighbor lists. If the Inter_RAT (Radio Access Technology) Handover feature and/or the Enhanced 2G/3G Handover feature is unrestricted, this command supports the UTRAN cell identity format.

NOTE
If all is entered for a BTS at which the Coincident MultiBand Handover option is enabled, and contains any coincident cells, the command is rejected.

Security level Supported by OMC-R GUI Command type Prerequisites

4 Yes A (no operator actions) To be on a Neighbor Cell List, a cell must be the destination of handovers from the Neighbor List owner. For handovers to UTRAN cells, the Inter-RAT Handover feature and/or the Enhanced 2G/3G Handover feature must be unrestricted. The specified UMTS cell identifier must exist as a neighbor cell of the GSM source cell. The GSM source cell must exist.

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

68P02901W23-S

3-197 Nov 2009

Format

Chapter 3: Device/function related commands

Format
Syntax
del_neighbor <source_cell_id> [<neighbor_cell_id>] <placement> [<FDD-ARFCN>] del_neighbor <source_cell_id> all del_neighbor all <neighbor_cell_id>

Input parameters
source_cell_id GSM or UTRAN Cell ID of the Neighbor List owner. GSM cell ID of the Neighbor List owner. The format for the GSM cell ID depends on: The system being used (PGSM, EGSM, DCS1800, PCS1900) Whether the seven parameter GSM cell ID format or the four parameter GSM cell ID format has been enabled.

The name of the cell created using the cell_name command is entered in place of the cell_id. When the cell name is entered, it must be placed inside double quotation marks.

NOTE
A cell_name cannot be associated with a UMTS neighbor.

neighbor_cell_id GSM or UTRAN Cell ID of the cell specified to be removed from the Neighbor List. GSM cell ID of the cell specified to be removed from the Neighbor List. This attribute is NOT allowed for Blind Search neighbors. The format for the GSM cell ID depends on: The system being used (PGSM, EGSM, DCS1800, PCS1900) Whether the seven parameter GSM cell ID format or the four parameter GSM cell ID format has been enabled.

The name of the cell created using the cell_name command is entered in place of the cell_id. When the cell name is entered, it must be placed inside double quotation marks. The string test <num> is entered for this field where <num> is a value from 1 to 64. This permits test neighbors to be removed from the BA_SACCH and/or BA_BCCH lists. placement

3-198

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Examples

Defines the placement type where umts_fdd_blind specifies that the neighbor is a Blind Search neighbor. This parameter is not allowed if the Enhanced 2G/3G Handover feature is restricted. FDD-ARFCN Specifies the FDD-ARFCN of the neighbor to be deleted. This parameter is not allowed if the Enhanced 2G/3G Handover feature is restricted. <source_cell_id>all This syntax removes all neighbor cells from the source cell neighbor list. all <neighbor_cell_id> This syntax removes the neighbor cell from all source cell neighbor lists.

Examples
Example 1
In this example, cell_id 5 4 3 2 1 61986 34945 is removed from the neighbor list of cell_id 5 4 3 2 161986 34944: del_neighbor 5 4 3 2 1 61986 34944 5 4 3 2 1 61986 34945 Where: 5 4 3 2 1 61986 34944 5 4 3 2 1 61986 34945 is: source_cell_id neighbor_cell_id

System response
COMMAND ACCEPTED

Example 2
In this example, all neighbor cells are removed from the neighbor list of cell_id 5 4 3 2 1 61986 34944: del_neighbor 5 4 3 2 1 61986 34944 all Where: 5 4 3 2 1 61986 34944 all is: source_cell_id neighbor_cell_id

68P02901W23-S

3-199 Nov 2009

Examples

Chapter 3: Device/function related commands

System response
COMMAND ACCEPTED

Example 3
In this example, cell_id 5 4 3 2 1 61986 34944 is removed from all neighbor lists: del_neighbor all 5 4 3 2 1 61986 34944 Where: all 5 4 3 2 1 61986 34944 is: source_cell_id neighbor_cell_id

System response
COMMAND ACCEPTED

Example 4
In this example, cell_id 987 654 12345 34567 (using the four parameter format) is removed from all neighbor lists: del_neighbor all 987 654 12345 34567 Where: all 987 654 12345 34567 is: source_cell_id neighbor_cell_id

System response
COMMAND ACCEPTED

Example 5
In this example, FDD-ARFCN cell ID 10762 is removed from the neighbor list of source cell ID 0 0 1 0 1 1 4. where 10762 is the last blind search neighbor of this cell and blind search preference is on. del_neighbor 0 0 1 0 1 1 4 umts_fdd_blind 10762 Where: 0010114 10762 is: source_cell_id FDD-ARFCN

3-200

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

References

System response
COMMAND ACCEPTED WARNING: The last Blind Search neighbor has been deleted for this cell.

References
Related commands
add_cell on page 3-22 del_cell on page 3-192 disp_neighbor on page 3-343 add_neighbor on page 3-35 disp_cell on page 3-241 copy_cell on page 3-179 disp_gsm_cells on page 3-314

68P02901W23-S

3-201 Nov 2009

del_nsvc

Chapter 3: Device/function related commands

del_nsvc

Description
The del_nsvc command enables the operator to remove one or more mappings between a Network Service-Virtual Connection Identifier (NSVCI), Data Link Connection Identifier (DLCI) and a GBL at a specific PCU. Security level Supported by OMC-R GUI Command type Prerequisites 4 Yes A (no operator actions) The GPRS feature must be unrestricted.

Format
Syntax
del_nsvc <pcu_id> <ns_vci_1> [<ns_vci_2> ... <ns_vci_8>]

Input parameters:
pcu_id {27955A} Specifies the specific PCU, as pcu or pcu_0. ns_vci_1 Specifies the unique identifier of the first NSVCI mapping and identifier of the object. Range = 0 - 65535. ns_vci_2 ... ns_vci_8

Specifies the unique identifiers of subsequent NSVCI mapping and the objects (up to 8). Range= 0 - 65535.

3-202

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Example

Example
The following example deletes NSVCI 580 at the first equipped PCU. del_nsvc pcu_0 580 Where: pcu_0 580 is: PCU identifier (first equipped) NSVC identifier

System response:
COMMAND ACCEPTED

References
Related commands
add_nsvc on page 3-48 mod_nsvc on page 3-445

68P02901W23-S

3-203 Nov 2009

del_rtf_path

Chapter 3: Device/function related commands

del_rtf_path

Description
The del_rtf_path command deletes a redundant PATH device from an equipped RTF function in the Configuration Management (CM) database. The system rejects attempts to modify the PATHs used by RTFs at sites that use dynamic allocation. RTFs automatically use the PATHs defined for these types of sites. RTFs do not use PATHs equipped by the operator for these types of sites. Security level Supported by OMC-R GUI Command type Prerequisites 4 Yes A (no operator actions) None

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

Format
Syntax
del_rtf_path <location> <1st_RTF_identifier> <2nd_RTF_identifier> <unique_PATH_identifier>

Input parameters
location The number of the BTS where the RTF is located. The range of values is 0 - 140. 1st_RTF_identifier The first RTF identifier from which the path is removed. The range of values is 0 - 5. 2nd_RTF_identifier The second RTF identifier from which the path is removed. The range of values is 0 - 11. unique_PATH_identifier The unique PATH to be removed. The range of values is 0 - 9.

3-204

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Example

Example
This example deletes a redundant RTF PATH from site 36, RTF identifiers 5 20, unique PATH identifier 8. del_rtf_path 36 5 20 8 Where: 36 5 20 8 is: location 1st_RTF_identifier 2nd_RTF_identifier unique_PATH_identifier

System response
This may reduce the number of Traffic Channels available. Are you sure? (y=yes, n=no)?y COMMAND ACCEPTED

References
Related information
If a redundant path does not exist, the command is rejected. When deleting a redundant path, the path is automatically switched over to the remaining paths.

Related commands
add_rtf_path on page 3-50 copy_path on page 3-187 chg_rtf_freq on page 3-144 disp_rtf_path on page 3-381

68P02901W23-S

3-205 Nov 2009

del_smscb_msg

Chapter 3: Device/function related commands

del_smscb_msg

Description
The del_smscb_msg command deletes the CBCH background message. This command is used to delete: A single message at a single cell. A single message at all cells in the BSS. All messages at a single cell. All messages at all cells in the BSS. 4 Yes A (no operator actions) None

Security level Supported by OMC-R GUI Command type Prerequisites

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

Format
Syntax
del_smscb_msg <msg_num|all> <cell_desc|all>

Input parameters
msg_num A number that uniquely identifies the message to be deleted. The value all is also a valid input for the msg_num to specify all messages at the specified cells.

3-206

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Examples

cell_desc This parameter is the GSM cell ID of the cell at which messages are to be deleted, preceded by cell_number=. The format for the GSM cell ID depends on: The system used (PGSM, EGSM, DCS1800, PCS1900) Whether the seven parameter GSM cell ID format or the four parameter GSM cell ID format has been enabled.

The name of the cell created using the cell_name command is entered in place of the cell_number. When the cell name is entered, it must be placed inside double quotation marks, and cell_name=. must precede it.

NOTE
This command responds to the shortened input parameter cell= allowing entry of either the cell_number or the cell_name without further definition. The value all is also a valid input for the cell_desc, to delete the specified messages at all cells at the BSS.

Examples
Example 1
This example deletes CBCH background message number 4 for cell_number=5 4 3 2 1 61986 34944. del_smscb_msg 3 cell_number=5 4 3 2 1 61986 34944 Where: 3 cell_number=5 4 3 2 1 61986 34944 is: msg_num cell_desc

System response
COMMAND ACCEPTED

68P02901W23-S

3-207 Nov 2009

Examples

Chapter 3: Device/function related commands

Example 2
This example deletes all CBCH background messages for all cells. del_smscb_msg all all Where: all all is: all background messages cell_desc (all cells)

System response
COMMAND ACCEPTED

Example 3
In this example, the affected cell is identified using the cell_name london-south. del_smscb_msg 3 cell_name=london-south Where: 3 cell_name=london-south is: msg_num cell_desc

System response
COMMAND ACCEPTED

Example 4
This example deletes CBCH background message number 4 for cell_number=987 654 13579 24689 (using the four parameter format). del_smscb_msg 3 cell_number=987 654 13579 24689 Where: 3 cell_number=987 654 13579 24689 is: msg_num cell_desc

System response
COMMAND ACCEPTED

3-208

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

References

References
Related commands
chg_smscb_msg on page 3-150 disp_cbch_state on page 3-237

68P02901W23-S

3-209 Nov 2009

device_audit

Chapter 3: Device/function related commands

device_audit

Description
The device_audit command suspends or resumes audits at a specific site. This command is also used to execute a specific test on a specific device. The device_audit supports display of swap_type on the TDM device at location 0 (BSC or RXCDR). When this command is used to execute an audit at the BSC for an RXCDR that is in the BUSY-UNLOCKED state, the BSC performs an audit. Security level Supported by OMC-R GUI Command type Prerequisites 4 Yes A (no operator action) This command is not allowed while in SYSGEN ON mode. The operator at the OMC-R must rlogin to a site before an audit can be performed.

Format
Syntax
device_audit <location> <control> <audit type> <device_name> <device_id1> <device_id2> <device_id3> device_audit <location> <audit type> <device_name> <device_id1> <device_id2> <device_id3>

Input parameters
location Specifies the audit location: 0 or bsc 1 - 140 {27955A} pcu or pcu_0 pcu_1 pcu_2 BSC BTS PCU Specifies the PCU site 1. Specifies the PCU site 2.

3-210

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Format

control Site audit status: on off audit_type Type of audit: Specifies the type of audit: Resumes all site audits within a cage at a specific site. Suspends all site audits within a cage at a specific site.

0 1 2 3 4

All audits Safe audits Internal loopback audit Self audits Swap_test

NOTE
If all is entered as the control parameter value, multiple devices can be audited. The format for each of the additional devices is the same as it is for the first device. {25002} The SWAP_TEST audit only applies to the expanded cage. The SWAP_TEST audit is done at 2:50 every day.

device_name Name that uniquely identifies the device. Not all devices can be audited at all site types. It is only possible to audit the device that are equipped at the site. Given these conditions, the following devices can be audited with this command: BSP BTP DHP DRI GPROC KSW MSI RXCDR SBUS TDM AXCDR

The following devices can be audited at M-Cell sites using this command: BTP DRI MSI

The following devices can be audited at PCU using this command: MSI DPROC PSP

68P02901W23-S

3-211 Nov 2009

Examples

Chapter 3: Device/function related commands

device_id1 First device identifier. Identifier value is dependent upon the device. device_id2 Second device identifier. Identifier value is dependent upon the device. device_id3 Third device identifier. Identifier value is dependent upon the device.

Examples
Example 1
The following example executes the safe audits for KSW device ID 0 0 0: device_audit bsc safe ksw 0 0 0 Where: bsc safe ksw 0 0 0 is: location audit_type device_name device_id1 device_id2 device_id3

System response
Device: KSW Year:1994 Device id: 0 0 0 Month:11 Day:12 Hour:0 Min:26 Sec:29 MSec:665 Result: PASS

Audit Type: SAFE

3-212

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Examples

Example 2
The following example suspends audits for a KSW device with ID 1 0 0 at site 4: device_audit 4 off ksw 1 0 0 Where: 4 off ksw 1 0 0 is: location control device_name device_id1 device_id2 device_id3

System response
COMMAND ACCEPTED If audits for the device is already turned off, the response is: COMMAND REJECTED: Audits already turned off for this device.

Example 3
The following example resumes audits for a KSW device with ID 1 0 0 at site 4: device_audit 4 on KSW 1 0 0 Where: 4 on ksw 1 0 0 is: location control device_name device_id1 device_id2 device_id3

System response
COMMAND ACCEPTED

68P02901W23-S

3-213 Nov 2009

Examples

Chapter 3: Device/function related commands

Example 4
The following example performs a device audit at RXCDR 14 where CIC mismatches are found: device_audit 0 all RXCDR 14 Where: 0 all RXCDR 14 is: location audit_type device_name device_id1

System response
Device: MSI Device id: 2 0 0 Year:1999 Month:1 Day:22 Hour:17 Min:56 Sec:12 MSec:470 Audit Type: SAFE Result: PASS

Example 5
{26740} The following example performs a device audit to execute a safe audit on a PSI device. device_audit 1 safe PSI 1 0 Where: 1 safe PSI 1 0 is: location audit_type device_name device_id1 device_id2

System response
Device: PSI Device id: 1 0 0 Year: 1999 Month: 1 Day: 22 Audit Type: SAFE Hour: 17 Min: 56 Sec: 12 MSec: 470 Result: PASS

3-214

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Examples

Example 6
{25002} The following example executes audits for the swap_test device ID 1. device_audit 0 swap_test tdm 1 Where: 0 swap_test tdm 1 is: location audit_type device_name device_id1

System Response
WARNING: The Swap_test audit will take about 2 minutes. Are you sure (y=yes,n=no)? yes Device: TDM Year: 2007 Device id: 1 0 0 Month: 1 Day: 30 Hour: 15 Min: 0 Sec: 44 MSec: 0 Result: PASS

Audit Type: SWAP_TEST

Example 7
{25002} The following example attempts to execute the audits for the swap_test device. device_audit 0 swap_test tdm 0 Where: 0 swap_test tdm 0 is: location audit_type device_name device_id1

System response
WARNING: The Swap_test audit will take about 2 minutes. Are you sure (y=yes,n=no)? yes Device: TDM Year: 2007 Device id: 0 0 0 Month: 1 Day: 30 Hour: 15 Min: 0 Sec: 15 MSec: 665 Result: ERROR

Audit Type: SWAP_TEST

68P02901W23-S

3-215 Nov 2009

References

Chapter 3: Device/function related commands

Example 8
{25002} In this example, device audit cannot be executed on the standby TDM bus. device_audit 0 all tdm 1 Where: 0 all tdm 1 is: location audit_type device_name device_id1

System response
WARNING: Both Safe audit and Swap_test audit will be executed.It will take about 2 minutes. Are you sure (y=yes,n=no)? yes Device: TDM Year: 2007 Device id: 1 0 0 Month: 6 Day: 21 Hour: 16 Min: 54 Sec: 13 MSec: 800 Result: ERROR

Audit Type: SAFE Device: TDM Year: 2007 Device id: 1 0 0 Month: 6 Day: 21

ERROR: Device not in auditable state Hour: 16 Min: 54 Sec: 13 MSec: 800

Audit Type: SWAP_TEST

Result: ERROR

ERROR: Device not in auditable state.

References
Related commands
cage_audit on page 3-58 site_audit on page 3-507 chg_audit_sched on page 3-76 query_audits on page 3-472

3-216

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

diagnose_device

Description
The diagnose_device command performs the specified diagnostic on the specified device. Security level Supported by OMC-R GUI Command type Prerequisites 4 No B (operator actions required) This command is supported only in the SYSGEN OFF mode. For there to be free RTFs for DRI diagnostics, all standby DRIs must be locked before using this command. Only DRI devices at Horizonmacro sites are supported. The operator must lock the DRI before using this command. The RTF cannot be in the active Mobile Allocation List.

Operator actions

Format
Syntax
diagnose_device <location> <device> <id0> <id1> <id2>

Input parameters
location Specifies the device location: 1 - 140 device Specifies the ASCII device name. The only available device is the DRI. id0 Specifies the first identifier. The range is 0 - 255. id1 Specifies the second identifier. The range is 0 - 255. id2 Specifies the third identifier. The range is 0 - 255. BTS

68P02901W23-S

3-217 Nov 2009

Examples

Chapter 3: Device/function related commands

Prompted parameter
After specifying the input parameters, the operator is prompted for the type of diagnostic to be performed. The following types are available: Device DRI Diagnostic rf_loopback vswr_test

Examples
Example 1
In this example, the Receive Preamplifier Input Loopback test fails, but RCU Output Loopback passes (indicating a possible problem with the receive front end). diagnose_device 1 DRI 0 0 0

System response
Diagnostic Type: rf_loopback REPORT FOR DRI 0 0 0 AT SITE 1 ------------------------------------------RELATED RTF: RX preamp input loopback: RTF 0 0 0 (ARFCN 60) FAIL

RX preamp Input Loopback RXLEV (Branch 1): -128 dBm RX preamp Input Loopback RXLEV (Branch 2): -128 dBm RCU Output Loopback: PASS RCU Output Loopback RXLEV (Branch 1): 50 dBm RCU Output Loopback RXLEV (Branch 2): 50 dBm END OF REPORT

Example 2
In this example, the Receive Preamplifier Input Loopback test passes, indicating that the diagnostic passes (RCU Output Loopback is not run). diagnose_device 1 DRI 0 0 0

3-218

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Examples

System response
Diagnostic Type: rf_loopback REPORT FOR DRI 0 0 0 AT SITE 1 ------------------------------------------RELATED RTF: RX Preamp input loopback: RTF 0 0 0 (ARFCN 60) PASS

RX preamp Input Loopback RXLEV (Branch 1): -50 dBm RX preamp Input Loopback RXLEV (Branch 2): -50 dBm RCU Output Loopback: NOT RUN RCU Output Loopback RXLEV (Branch 1): N/A RCU Output Loopback RXLEV (Branch 2): N/A END OF REPORT

Example 3
{27236} In this example, with the 4 branch diversity feature enabled, the Receive Preamplifier Input Loopback test and the RCU Output Loopback test passes, indicating that the diagnostic passes. diagnose_device 6 DRI 1 0 0

System response
diagnose_device 6 DRI 0 0 0 Diagnostic Type: rf_loopback Report for DRI 1 0 0 at SITE 6 ------------------------------------------Related RTF: RX Preamp Input Loopback (Branch 1): RX Preamp Input Loopback (Branch 2): RX Preamp Input Loopback (Branch 3): RX Preamp Input Loopback (Branch 4): RX Preamp Input Loopback RXLEV (Branch 1): RX Preamp Input Loopback RXLEV (Branch 2): RX Preamp Input Loopback RXLEV (Branch 3): RTF 1 0 0 (ARFCN 2) PASS PASS PASS PASS -74 dBm -74 dBm -74 dBm

68P02901W23-S

3-219 Nov 2009

Examples

Chapter 3: Device/function related commands

RX Preamp Input Loopback RXLEV (Branch 4): RCU Output Loopback (Branch 1): RCU Output Loopback (Branch 2): RCU Output Loopback (Branch 3): RCU Output Loopback (Branch 4): RCU Output Loopback RXLEV (Branch 1): RCU Output Loopback RXLEV (Branch 2): RCU Output Loopback RXLEV (Branch 3): RCU Output Loopback RXLEV (Branch 4): End of Report

-74 dBm PASS PASS PASS PASS -75 dBm -75 dBm -75 dBm -75 dBm

3-220

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

disp_a5_alg_pr

Description
The disp_a5_alg_pr command displays the current list of prioritized encryption algorithms. Security level Supported by OMC-R GUI Command type Prerequisites 1 {27508} Yes A (no operator actions) None

Format
Syntax
disp_a5_alg_pr

Input parameters
There are no input parameters associated with this command.

Examples
Example 1
This example shows the order in which two ciphering algorithms were used. disp_a5_alg_pr

System response
Ciphering Algorithms are prioritized as follows: 2 1 0

Example 2
This example shows that no ciphering algorithms were used. disp_a5_alg_pr

68P02901W23-S

3-221 Nov 2009

References

Chapter 3: Device/function related commands

System response
Ciphering Algorithms are prioritized as follows: 0

References
Related commands
chg_a5_alg_pr on page 3-73 page on page 3-470

3-222

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

disp_acs

Description
The disp_acs command displays the Active Codec Set and associated parameters. Security level Supported by OMC-R GUI Command type Prerequisites 1 Yes A (no operator actions) The AMR feature must be unrestricted. The site must be an AMR-capable BTS.

Format
disp_acs <cell_id>

Input parameters
cell_id GSM cell ID or cell name of the cell to be changed. The format for the GSM cell ID depends on: The system used (PGSM, EGSM, DCS1800, PCS1900) Whether the seven parameter GSM cell ID format or the four parameter GSM cell ID format has been enabled.

Only PCS1900 systems can use a three digit MNC. The name of the cell created using the cell_name command is entered in place of the Cell ID. When the cell name is entered, it must be placed inside double quotation marks. The Cell ID or the cell_name must be entered directly without any preceding qualifier.

NOTE
This command responds to the shortened input parameter cell= allowing entry of either the cell_number or the cell_name without further definition.

Example
This example displays the codec modes for a given cell.

68P02901W23-S

3-223 Nov 2009

References

Chapter 3: Device/function related commands

disp_acs 4 9 6 0 1 1 1 Where: 4960111 is: cell_id

System response
AMR Full Rate active codec set: 0 1 3 6 1 26 20 14 1 1 1 30 24 19 1 1 1 26 20 14 1 1 1 26 21 14 1 1 1

AMR Full Rate initial codec mode:

AMR Full Rate uplink adaptation thresholds: AMR Full Rate uplink adaptation hysteresis:

AMR Full Rate downlink adaptation thresholds: AMR Full Rate downlink adaptation hysteresis:

AMR Full Rate uplink adaptation thresholds for frequency hopping: AMR Full Rate uplink adaptation hysteresis for frequency hopping:

AMR Full Rate downlink adaptation thresholds for frequency hopping: AMR Full Rate downlink adaptation hysteresis for frequency hopping: AMR Half Rate active codec set: 3 5 6 5 28 22 1 1 30 24 1 1

AMR Half Rate initial codec mode:

AMR Half Rate uplink adaptation thresholds: AMR Half Rate uplink adaptation hysteresis:

AMR Half Rate downlink adaptation thresholds: AMR Half Rate downlink adaptation hysteresis:

AMR Half Rate uplink adaptation thresholds for frequency hopping: AMR Half Rate uplink adaptation hysteresis for frequency hopping:

28 22 1 1 30 23 1 1

A MR Half Rate downlink adaptation thresholds for frequency hopping: AMR Half Rate downlink adaptation hysteresis for frequency hopping:

References
Related command
chg_acs_params on page 3-65

3-224

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

disp_act_alarm

Description
The disp_act_alarm command displays the active Operator Initiated Clear (OIC) alarms and the active Fault Management Initiated Clear (FMIC) alarms only. Those alarms that have been designated as Intermittent do not appear in the active alarm list. Each device has an active alarm list limit of 200. If there are more than 200 active alarms on the device, only the first 200 are displayed and monitored. The number of alarms displayed after entering disp_act_alarm <location> does not get affected. The output of this command displays up to 200 alarms for each device in the site. Security level 1

Supported by OMC-R GUI Command type Prerequisites

No A (no operator actions) This command is not allowed while in SYSGEN ON mode.

Format
Syntax
disp_act_alarm <location> [<device_name> <dev_id1><dev_id2> <dev_id3>] disp_act_alarm <location>

Input parameters
location Specifies the alarm location: 0 or bsc 1 - 140 pcu or pcu_0 all BSC BTS PCU Specifies all sites.

68P02901W23-S

3-225 Nov 2009

Examples

Chapter 3: Device/function related commands

device_name Device name that uniquely identifies the device. dev_id1 First device identifier. The range of values is 0 to 99. dev_id2 Second device identifier. The range of values is 0 to 99. dev_id3 Third device identifier. The range of values is 0 to 99.

Examples
Example 1
This example displays all active Operator Initiated Clear, and Fault Management alarms for DRI 1 0 0 at the BSC. The command does not show all active alarms, since any uncleared intermittent alarm is considered an active alarm, but it cannot appear on any list using the disp_act_alarm command: disp_act_alarm bsc dri 1 0 0 Where: bsc dri 1 0 0 is: location device_name dev_id1 dev_id2 dev_id3

3-226

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Examples

System response
COMMAND ACCEPTED Site: BSC Alarm Device (Subtype) --------------------------------------------------------------------Code Clear Type Tag(hex) Date/Time Description

MMS 0 0 0 (XCDR) DRI 1 0 0 (DRIM) DRI 1 0 0 (DRIM)

12 5 1

N Y N

Bit Error Daily Threshold Exceeded MPH Error: Counter Mismatch: Uplink Bad Host Message

Example 2
This example displays the output when there are no active alarms at site 2. disp_act_alarm 2 Where: 2 is: location

System response
There are no active alarms at site 2.

68P02901W23-S

3-227 Nov 2009

References

Chapter 3: Device/function related commands

References
Related information
The following responses are received when the disp_act_alarm command is entered: There are no active alarms at site <location>. There are no active alarms on that device. Unknown alarm device Unknown alarm code Error: Could not retrieve alarm description UNKNOWN INVALID CELL If the GPRS option is unrestricted the response is: There are no active alarms at the PCU.

3-228

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

disp_bss

Description
The disp_bss command displays specific status information for all sites in a BSS site. The BSS device identifier where the command is entered is included in the output. The status information shows the following: Sites that are equipped and their status. Number of sectors, or 1 if the site is OMNI. The GSM cell ID that is equipped for each site. Broadcast Control Channel (BCCH) frequency for each of the cells.

The functional Unit Status shows the status of the BSC sites or of the associated cells. The possible values are: Critical - indicates a loss of service. Major - indicates a loss of capacity. Minor - indicates a loss of redundancy. Clear - indicates normal operations.

Read the Functional Unit Status across the display. In the example, Site 0 is in Critical status. Cell 4, which is associated with Site 0 is in Clear status, and Cell 5 is in Critical status. If the GPRS feature is unrestricted, a line containing GPRS information appears in the output. {27955A} This includes the (pcu or pcu_0) PCU, if it is equipped, and values of the RAC and BVCI associated with each cell. Security level Supported by OMC-R GUI Command type Prerequisites 1 Yes A (no operator actions) This command is not allowed while in SYSGEN ON mode.

Format
Syntax
disp_bss

68P02901W23-S

3-229 Nov 2009

Example

Chapter 3: Device/function related commands

Input parameters
There are no input parameters associated with this command.

Example
This example shows the format of a typical output of the disp_bss command. disp_bss

System response
OPER STATES: D:Disabled E:Enabled L:Locked U:Unlocked B:Busy E:Equipped NE:Not Equipped S:Shutdown FREQ CI LCI RAC TYPE BCCH FREQ

ADMIN STATES: SITE SITE STATE 0 1 B-U D-U

Status for BSS 1: FU STATUS LOSS OF Service Capacity UNAVAILABLE UNAVAILABLE UNAVAILABLE 2 B-U Capacity Capacity CLEAR 3 4 D-U D-U UNAVAILABLE UNAVAILABLE UNAVAILABLE UNAVAILABLE 001 01 1 (0001h) 18 (0012h) 4 N/A DCS1800 570 001 01 1 (0001h) 33 (0001h) 3 4 PGSM 10 001 01 001 01 1 (0001h) 1 (0001h) 3 (0001h) 8 (0006h) 2 5 4 4 PGSM PGSM 30 31 001 01 001 01 1 (0001h) 1 (0001h) 1 (0001h) 6 (0006h) 0 1 N/A 4 PGSM PGSM 26 75 MCC MNC GSM CELL id LAC

---- ----- ------------- ----------------------------- --- ---- ------- -----PCU_0 B-U

References
Related command
assess on page 3-54.

3-230

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

disp_bssgp_f_bmap

Description
The disp_bssgp_f_bmap command prints out the database values and SGSN negotiated values of BSSGP features. It prints out values of bssgp_cbl_bit. If the QoS is unrestricted, the command also prints out values of bssgp_pfc_bit. Security level Supported by OMC-R GUI Command type Prerequisites 1 Yes A (no operator actions) The GPRS feature must be unrestricted. This command is only available at the BSC, when sysgen mode is off.

Format
Syntax
disp_bssgp_f_bmap <all> <PCU_id>

Input parameters
<all> Displays cell mapping at all equipped PCUs. <PCU_id> Specifies the specific PCU, as pcu, pcu_0

Example
disp_bssgp_f_bmap PCU_1 Where: PCU_1 is: PCU ID

68P02901W23-S

3-231 Nov 2009

Example

Chapter 3: Device/function related commands

System response
PCU Site 1: Feature-bit CBL PFC END OF REPORT DB value 0 (bssgp_cbl_bit) 0 (bssgp_pfc_bit) Negotiated Value 0 (CBL feature at PCU disabled) 0 (QoS feature at PCU disabled)

3-232

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

disp_cal_data

Description
The disp_cal_data command displays the transceiver calibration data stored on the transceiver or in the BSC database on a per DRI basis. If the BSC and BTS are set for PGSM operation, 16 values are displayed. If the system is set so that the frequency_type parameter is EGSM, then all 22 values are displayed. The first six are for EGSM and the next 16 are for PGSM. Security level Supported by OMC-R GUI Command type Prerequisites 1 No A (no operator actions) This command is not allowed while in SYSGEN ON mode. This command is not available at an RXCDR.

Format
Syntax
disp_cal_data <location> dri <dev_id1> <dev_id2> [<dev_id3>]

Input parameters
location 0 or bsc 1 - 140 dri The DRI is the only device permitted for this command. dev_id1 The first device identifier. dev_id2 The second device identifier. BSC BTS

68P02901W23-S

3-233 Nov 2009

Example 1

Chapter 3: Device/function related commands

dev_id3 The third device identifier. This value defaults to 0 if no value is entered.

Example 1
The following example displays the calibration data for transceiver 5 3 0 at site 21: disp_cal_data 21 dri 5 3 0 Where: 21 dri 5 3 0 is: site dri device first dev_id second dev_id third dev_id

System response
DRI ID 5 3 0 Data read from transceiver Store Calibration Data: enabled Calibration data (All values in Hex): Transmit Power Offsets = 0 Receiver System Data:

Antenna Number

1 2 f00,

3 4 5 6 1100, 114d, 1100, 1066, 1066,

-------------------------------------------------10cd, 1100, 1033, 1100, 104d, 104d, 1100, 1100, 1033, 1100, 1033, 1033, 10e6, 1100, 1033, 1100, 101a, 101a, 10cd, 10cd, 1000, 10cd, 1000, 1000, 10b3, 10b3, 1000, 10b3, fcd, 10cd, 10cd, f66, 1033, 10cd, f9a, 10cd, fe6, 10cd, fcd, fcd, fe6, fcd,

3-234

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Example 1

1066, 10cd, fcd, 1066, 10cd, fcd, 1033, 10b3, f9a, 1066, 10b3, fcd, 1066, 109a, fb3, c9a, f9a, f9a, 1066, db3, 1066, ecd, 1000, ecd,

10cd, fcd, 10cd, f9a, 10b3, f66, 10b3, f9a, 109a, f66, 1066, f80, 1066, f33, 1000, eb3,

fcd, f9a, f66, f9a, f66, f80, f33, eb3,

NOTE
The second line of the system response indicates whether the data is read from the transceiver or the database. In example 1, the information is read from the transceiver.

Example 2
{27236} The following example displays the calibration data for a DRI that has 4 Branch Receive Diversity enabled. disp_cal_data 40 dri 0 0 0 Where: 40 dri 0 0 0 is: site dri device first dev_id second dev_id third dev_id

68P02901W23-S

3-235 Nov 2009

References

Chapter 3: Device/function related commands

System response
DRI ID: 0 0 0 Data read from transceiver Store Calibration Data:disabled Calibration Data (All values in Hex): Transmit Power Offsets = 12 Receiver System Data: AntennaNumber 1 2 3 4 5 6 7 8 9 10 11 12 b89, e80, e80, c4e, e80, e80, b89, e80, e80, c4e, e80, e80, b7f, e80, e80, ca2, e80, e80, b7f, e80, e80, ca2, e80, e80, b8d, e80, e80, c74, e80, e80, b8d, e80, e80, c74, e80, e80, b8d, e80, e80, c9d, e80, e80, b8d, e80, e80, c9d, e80, e80, b61, e80, e80, c65, e80, e80, b61, e80, e80, c65, e80, e80, b19, e80, e80, c0c, e80, e80, b19, e80, e80, c0c, e80, e80, aff, e80, e80, bd3, e80, e80, aff, e80, e80, bd3, e80, e80, b1d, e80, e80, b54, e80, e80, b1d, e80, e80, b54, e80, e80, b4b, e80, e80, b9f, e80, e80, b4b, e80, e80, b9f, e80, e80, b5b, e80, e80, b85, e80, e80, b5b, e80, e80, b85, e80, e80, b4f, e80, e80, b53, e80, e80, b4f, e80, e80, b53, e80, e80, b4a, e80, e80, b71, e80, e80, b4a, e80, e80, b71, e80, e80, b2d, e80, e80, b59, e80, e80, b2d, e80, e80, b59, e80, e80, b1e, e80, e80, b29, e80, e80, b1e, e80, e80, b29, e80, e80, b08, e80, e80, aab, e80, e80, b08, e80, e80, aab, e80, e80, a8f, e80, e80, a9f, e80, e80, a8f, e80, e80, a9f, e80, e80,

References
Related commands
clear_cal_data on page 3-169 store_cal_data on page 3-534

3-236

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

disp_cbch_state

Description
The disp_cbch_state command displays the value of the cbch_enabled field for a specific cell. In addition, the specified background message in a cell is presented. If the CBCH is hopping, the frequency hopping index (fhi) for the CBCH timeslot is also displayed. If the all option is selected for the message number parameter, all background messages associated with the indicated cell display. Security level Supported by OMC-R GUI Command type Prerequisites Operator actions 1 Yes B (operator actions required) To successfully execute this command, purchase, install, and activate the background message feature. The Background Message feature must be unrestricted.

Format
Syntax
disp_cbch_state <msg_num> <cell_desc> disp_cbch_state all <cell_desc>

Input parameters
msg_num Uniquely identifies the number of the message for a given cell by sequence received (up to 4). The range of values is 0 to 3. cell_desc The GSM cell ID of the cell preceded by cell_number=. The format for the GSM cell ID depends on: The system used (PGSM, EGSM, DCS1800, PCS1900). Whether the seven parameter GSM cell ID format or the four parameter GSM cell ID format has been enabled.

68P02901W23-S

3-237 Nov 2009

Examples

Chapter 3: Device/function related commands

The name of the cell created using the cell_name command is entered in place of the cell_number. When the cell name is entered, place it inside double quotation marks and preceded by cell_name=.

NOTE
This command responds to the shortened input parameter cell= allowing entry of either the cell_number or the cell_name without further definition.

Examples
Example 1
This example displays the output where the CBCH is not enabled and no background message is defined for the specified msg_num. The cell_number parameter uses the seven parameter format. disp_cbch_state 3 cell_number=5 4 3 2 1 61986 3494 Where: 3 5 4 3 2 1 61986 3494 is: msg_num cell_number

System response
Message Number 3 is not defined for the CBCH. The CBCH for cell 5 4 3 2 1 61986 3494 is not enabled.

Example 2
This example displays the output where the CBCH is not enabled and no background message is defined for the specified msg_num. The cell_number parameter uses the four parameter format. disp_cbch_state 3 cell_number=543 21 61986 3494 Where: 3 543 21 61986 3494 is: msg_num cell_number

System response
Message Number 3 is not defined for the CBCH. The CBCH for cell 5 4 3 2 1 61986 3494 is not enabled.

3-238

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Examples

Example 3
In this example, the affected cell is identified using the cell_name london-south. disp_cbch_state 3 cell_name=london-south Where: 3 london-south is: msg_num cell_name

System response
Message Number 3 is not defined for the CBCH. The CBCH for cell 5 4 3 2 1 61986 3494 is not enabled.

Example 4
This is an example of the command succeeding if the CBCH is active and hopping with a background message defined: disp_cbch_state 2 cell_number=5 4 3 2 1 61986 3494 Where: 2 5 4 3 2 1 61986 3494 is: msg_num cell_number

System response
Message Number 2 for the CBCH is: This is the background message. their escape format The Message Identifier is 1009 The Geographical Scope is 1 (Normal - PLMN Wide). The Message Code is 0. The update number is 0. The Language Identifier is 3 (French). The CBCH for cell 5 4 3 2 1 61986 3494 is active. The channel description is: Channel Type: SDCCH/4 Subchannel number 2 Non alphabetic characters are displayed in

Timeslot Number = 0 ARFCN = 107 (BCCH Carrier)

68P02901W23-S

3-239 Nov 2009

References

Chapter 3: Device/function related commands

References
Related commands
chg_smscb_msg on page 3-150 del_smscb_msg on page 3-206

3-240

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

disp_cell

Description
The disp_cell command reads back and displays all programmable database parameters for a specified cell. If the disp_cell command is used with the cell description and the optional full parameter, the system displays all cell-related elements. If the disp_cell command is used with the cell_description only, the system displays the elements used in theadd_cell command. Security level Supported by OMC-R GUI Command type Prerequisites 1 Yes A (no operator actions) None

Format
Syntax
disp_cell <cell_id> [full]

Input parameters
cell_desc GSM cell number of the cell to be displayed. The format for the GSM cell ID depends on: The system used (PGSM, EGSM, DCS1800, PCS1900). Whether the seven parameter GSM cell ID format or the four parameter GSM cell ID format has been enabled.

cell_id is an invalid parameter. The operator cannot input the cell_number or cell_name preceded by the GSM cell ID or GSM cell name. BSS system responds input error. full This optional parameter displays all elements related to the cell. The system displays the elements with non-indexed parameters first, in alphabetical order, followed by the indexed parameters also in alphabetical order.

68P02901W23-S

3-241 Nov 2009

Examples

Chapter 3: Device/function related commands

Examples
Example 1
This example displays the programmable database parameters for a GSM cell with a Cell ID of 5 4 3 2 1 61986 34944. disp_cell 5 4 3 2 1 61986 34944 Where: 5 4 3 2 1 61986 34944 is: cell_id

System response
The system displays the cell information specified in the add_cell command at creation of cell 5 4 3 2 1 61986 34944.

Example 2
In this example, the cell is identified using the cell_name london-south: disp_cell london-south Where: london-south is: cell_id

System response
The system displays the cell information specified in the add_cell command at creation of cell london-south.

Example 3
In this example, the cell is identified in the four parameter format, using the cell_number 543 721 62259 08736: disp_cell 543 721 62259 08736 Where: 543 721 62259 08736 is: cell_id

System response
The system displays the cell information specified in the add_cell command at creation of cell 543 721 62259 08736.

3-242

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

References

Example 4
In this example, all cell-related elements for cell 0 0 1 0 1 1 2 are displayed by using the parameter full. disp_cell 0 0 1 0 1 1 2 full Where: 0010112 full is: cell_id full option (display all cell-related elements).

System response
The system displays a complete list of all elements related to cell 0 0 1 0 1 1 2. Non-indexed parameters are displayed first, in alphabetical order, followed by the indexed parameters also in alphabetical order.

Example 5
{26881} This example displays the cell information about cell 0 0 1 0 1 1 4. disp_cell 0 0 1 0 1 1 4 FULL Where: 0010114 full is: cell_id full option (display all cell-related elements).

System response
The system displays a complete list of all elements related to cell 0 0 1 0 1 1 4.

References
Related commands
add_cell on page 3-22 disp_gsm_cells on page 3-314 copy_cell on page 3-179 del_cell on page 3-192

68P02901W23-S

3-243 Nov 2009

disp_cell_map

Chapter 3: Device/function related commands

disp_cell_map

Description
Because of the dynamic cell migration in case of failure and recovery, a cell can be mapped to any equipped PCU site. The disp_cell_map command displays the current cell mapping information to a particular PCU. The displayed information includes EGPRS availability.

NOTE
The disp_cell_status command shows the status details of the PCU that is currently serving a cell.

Security level Supported by OMC-R GUI Command type Prerequisites

1 Yes A (no operator actions) This command is not allowed while in SYSGEN ON mode.

Format
Syntax
disp_cell_map all|location|cell_id

Input parameters
all location cell_id Displays cell mapping at all equipped PCUs. pcu, pcu_0 to pcu_2. Identifier of cell for which mapping to a PCU is required.

3-244

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Examples

Examples
Example 1
Display cell mapping at PCUs 1 and 2: disp_cell_map pcu_1 pcu_2 Where: pcu_1 pcu_2 is: location (site 1) location (site 2)

System response
PCU Site 1: CELL ID -------------------------001 01 1 (0001h) 4 (0004h) 001 01 1 (0001h) 5 (0005h) PCU Site 2: CELL ID -------------------------001 01 1 (0001h) 7 (0007h) 001 01 1 (0001h) 8 (0008h) END OF REPORT GPRS STATUS -------------------Barred Unbarred GPRS STATUS -------------------Barred Unbarred

Example 2
Display current PCU mapping of cell 0 0 1 0 1 1 4: disp_cell_map 0 0 1 0 1 1 4 Where: 0010114 is: cell_desc

System response
Current PCU site: PCU_1

68P02901W23-S

3-245 Nov 2009

Examples

Chapter 3: Device/function related commands

Example 3
Display cell mapping at all PCUs: disp_cell_map all Where: all is: all option (display cell mapping at all equipped PCUs).

System response
PCU Site 0: CELL ID -------------------------001 01 1 (0001h) 4 (0004h) 001 01 1 (0001h) 5 (0005h) PCU Site 1: CELL ID -------------------------001 01 1 (0001h) 7 (0007h) 001 01 1 (0001h) 8 (0008h) PCU Site 2: CELL ID -------------------------001 01 1 (0001h) 1 (0001h) 001 01 1 (0001h) 2 (0002h) END OF REPORT GPRS STATUS -------------------Barred Unbarred GPRS STATUS -------------------Barred Unbarred GPRS STATUS -------------------Barred Unbarred

3-246

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

disp_cell_status

Description
The disp_cell_status command displays information and channel counters of a single GSM cell or all GSM cells at a specific site. Because of the dynamic cell migration in case of failure and recovery, a cell can be mapped to any equipped PCU site. The disp_cell_status command includes the information on the cell active PCU. When the status of a single cell is requested, the cell_name is included in the command output. When the status of all the cells at a location with more than three cells is requested, the information on the first two cells displays, followed with a prompt to continue. The cell_name is not included when all the cells at a site are displayed. If the BTF is not in service for any reason, the system displays an error message. If both the GSM and AMR Half Rate modes are disabled either at the BSS or Cell level for a given cell, the BSS when generating the disp_cell_status command, regards: Free generic traffic timeslots in that cell as free full-rate traffic channels. Unavailable generic traffic timeslots in that cell as unavailable full-rate traffic channels.

Security level Supported by OMC-R GUI Command type Prerequisites

1 Yes A (no operator actions) This command is not allowed while in SYSGEN ON mode.

Format
Syntax
disp_cell_status <cell_desc> disp_cell_status <location> disp_cell_status <location> <high>

68P02901W23-S

3-247 Nov 2009

Format

Chapter 3: Device/function related commands

Input parameters
cell_desc The GSM cell ID of the cell to be displayed, preceded by cell_number=. The format for the GSM cell ID depends on: The system being used (PGSM, EGSM, DCS1800, PCS1900, or GSM850) Whether the seven parameter GSM cell ID format or the four parameter GSM cell ID format has been enabled.

The name of the cell created using the cell_name command is entered in place of the cell_number. When the cell name is entered, place it inside double quotation marks and precede by cell_name=.

NOTE
This command responds to the shortened input parameter cell= allowing entry of either the cell_number or the cell_name without further definition.

location Specifies the element location: 0 or bsc 1 - 140 high Indicate that this command is executed in high priority mode which implies that disp_cell_status is handled by BTS and PCU with high priority. BSC BTS

Output fields
RAC This field shows the Routing Area Code (part of the cell identifier for GPRS cells). Status Barred - A MS cannot access the cell. Unbarred - A MS can access the cell.

GPRS Status This field shows the status of a GPRS cell (barred/unbarred) and (when unbarred) whether EGPRS is available. {34144} GPRS Congestion Status

3-248

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Format

This field shows the cell GPRS congestion status (TRUE / FALSE / NA) when the GPRS/EDGE feature is unrestricted. TRUE - Indicates that the cell GPRS cell utilization has reached the higher threshold without dropping below the lower threshold. The additional switchable PDTCH is allocated during this status. FALSE - Indicates that the cell GPRS cell utilization does not reach the higher threshold. No additional switchable PDTCH is allocated during this status. NA - Indicates that the status is not applicable.

PDCH Status This field shows the GPRS Packet Data traffic channel status. Reset In Progress Yes - A reset is in progress. The cell is barred while a reset is in progress. No - A reset is not in progress.

GPRS Reset in Prog This field shows whether a PCU is currently undergoing a Reset. SPI in Progress Yes - An SPI (Signaling Point Inaccessibility) is in progress. The cell is barred while an SPI is in progress. No - An SPI is not in progress.

BSS BSSAP Prhb Yes - The BSS BSSAP (Base Station System Application Part) Prohibited flag is set to true. The cell is barred while the BSS BSSAP Prohibited flag is true. No - The BSS BSSAP Prohibited flag is not set to true. N/A - Not applicable; the value of this element is not relevant to the status of the cell.

MSC BSSAP Prhb Yes - The MSC BSSAP Prohibited flag is set to true. The cell is barred while the MSC BSSAP Prohibited flag is true. No - The MSC BSSAP Prohibited flag is not set to true. N/A - Not applicable; the value of this element is not relevant to the status of the cell.

SPI/MSC SCCP Prhb

68P02901W23-S

3-249 Nov 2009

Format

Chapter 3: Device/function related commands

Yes - The SPI/MSC BSSAP Prohibited flag is set to true. The cell is barred while the SPI/MSC BSSAP Prohibited flag is true. No - The SPI/MSC BSSAP Prohibited flag is not set to true. N/A - Not applicable; the value of this element is not relevant to the status of the cell.

AccCLASS Bar This field specifies the access classes of MSs that are barred from the cell. The access class is presented as a decimal value, separated by commas. If the cell is barred or OOS, this field contains N/A. If the cell is unbarred, this field contains None when all access classes have been unbarred. GPRS AccClass Bar This field shows any access class barring of GPRS cells. EGPRS Chan Req This field indicates if 11-bit EGPRS one-phase access is supported in the cell. EPCR is only available in the cell if the BCCH RTF is mapped to a CTU II radio. Full Power Mode This field indicates if the cell is in the full power mode. Ext Range Mode This field shows whether the Extended Range Feature is enabled (on) or disabled (off). SDCCH: FREE; INUSE; UNAVL These fields specify the number of Standalone Dedicated Control Channels (SDCCH) in the cell, that are currently free, in use or unavailable. Norm Outer TCH/F: FREE; INUSE; UNAVL These fields specify the number of Full Rate Traffic Channels (TCH/F) in the outer zone concentric cell that are currently free, in use or unavailable. The UNAVL field includes timeslots that are locked or out of service due to a fault condition. Any timeslot which is unavailable due to being locked or out of service is counted as an unavailable TCH (not SDCCH). This field does not include entire carriers which are out of service. Norm Outer TCH/F: FREE; INUSE; UNAVL These fields specify the number of Full Rate Traffic Channels (TCH/H) in the outer zone concentric cell that are currently free, in use or unavailable. Norm Inner TCH/F: FREE; INUSE; UNAVL These fields specify the number of Full Rate Traffic Channels (TCH/F) in the inner zone concentric cell that are currently free, in use or unavailable.

3-250

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Examples

Ext Outer TCH/F: FREE; INUSE; UNAVL These fields specify the number of Full Rate Traffic Channels (TCH/F) in the extended outer concentric cell that are currently free, in use or unavailable. Norm Inner TCH/H: FREE; INUSE; UNAVL These fields specify the number of Half Rate Traffic Channels (TCH/H) in the inner zone concentric cell that are currently free, in use or unavailable. Norm Outer TCH/G: FREE; INUSE; UNAVL These fields specify the number of Generic Traffic Channels (TCH/G) in the outer zone concentric cell that are currently free, in use or unavailable. Norm Inner TCH/G: FREE; INUSE; UNAVL These fields specify the number of Generic Traffic Channels (TCH/G) in the inner zone concentric cell that are currently free, in use or unavailable. PD CHANNEL This field shows the GPRS Packet Data traffic channels currently free, in use or unavailable.

EGPRS PD CHANNEL This field shows the EGPRS Packet Data traffic channels currently free, in use or unavailable. RES PDCH Requested This field shows the RES PDCH requested. SW PDCH Requested This field shows the SW PDCH requested.

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: 5 4 3 2 1 61986 34944 is: cell_number

68P02901W23-S

3-251 Nov 2009

Examples

Chapter 3: Device/function related commands

System response
GSM CELL ID LAC (dec) (hex) (name) MCC 543 CI MNC 21

61986 34944 f222h 8880h london-south

-------------------------------------Frequency Type BCCH Frequency PGSM 100

-------------------------------------Status Reset in Prog SPI in Prog BSS BSSAP Prhb MSC BSSAP Prhb SPI/MSC SCCP Prhb AccClass Bar Full Power Mode Extend Range Mode OOS No Yes Yes Yes Yes NA OFF OFF FREE INUSE UNAVL

----- ----- ----SDCCH Norm Outer TCH/F Norm Inner TCH/F Ext Outer TCH/F 0 0 0 0 0 0 0 0 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: london-south is: cell_name

3-252

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Examples

System response
GSM CELL ID LAC (dec) (hex) (name) MCC 543 MNC 21 CI

61986 34944 f222h 8880h london-south

-----------------------------------Status Reset In Prog SPI in Prog BSS BSSAP Prhb MSC BSSAP Prhb SPI/MSC SCCP Prhb AccCLASS Bar Ext Range Mode Barred No Yes Yes No No NA OFF FREE INUSE UNAVL

----- ----- ----SDCCH Norm Outer TCH/F Norm Inner TCH/F Ext Outer TCH/F 0 0 0 0 0 0 0 0 0 0 0 0

End of Report

Example 3
This example shows the display for a cell where the Concentric Cells feature is enabled. disp_cell_status 0 Where: 0 is: cell_number

68P02901W23-S

3-253 Nov 2009

Examples

Chapter 3: Device/function related commands

System response
Start of report for LOCATION 39: GSM CELL ID MCC 001 MNC 01 CI 39001 9859h

LAC (dec) (hex) 1 0001h

-------------------------------------Frequency Type BCCH Frequency PGSM 62

-------------------------------------Status Reset in Prog SPI in Prog BSS BSSAP Prhb MSC BSSAP Prhb SPI/MSC SCCP Prhb AccClass Bar Unbarred No No NA NA NA None FREE INUSE UNAVL

----- ----- ----SDCCH Norm Outer TCH/F Norm Inner TCH/F Ext Outer TCH/F 0 0 0 0 0 0 0 0 0 0 0 0

End of Report.

Example 4
This example displays the status of a BTS site. disp_cell_status 30 Where: 30 is: location

3-254

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Examples

System response
Start of report for LOCATION 30: GSM CELL ID MCC MNC LAC CI RAC 001 01 17 31 NA (0011h) (001Fh) 001 01 17 33 NA (0011h) (0021h)

-----------------------------------------------------------Primary Freq Type EGSM EGSM N/A 64

Secondary Freq Type N/A BCCH Frequency 5

-----------------------------------------------------------Status GPRS Status PDCH Status RES PDCH Requested SW PCDH Requested 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 Active PCU site Unbarred NA Unknown NA NA No NA No NA NA NA None NA OFF OFF NA FREE INUSE UNAVL Unbarred NA Unknown NA NA No NA No NA NA NA None NA OFF OFF NA FREE INUSE UNAVL

----- ----- ----SDCCH 8 0 0

----- ----- ----8 0 0

68P02901W23-S

3-255 Nov 2009

Examples

Chapter 3: Device/function related commands

Norm Outer TCH/F Ext Outer TCH/F

0 0 0 0 14 0 NA

0 0 0 0 NA NA NA

0 0 0 0 0 0 NA

0 0 0 0 6 0 NA

0 0 0 0 NA NA NA

0 0 0 0 0 0 NA

Norm Outer TCH/H Norm Inner TCH/H Norm Outer TCH/G Norm Inner TCH/G PD CHANNEL End of Report.

Example 5
This example shows the display when a location is entered and the GPRS feature is unrestricted. disp_cell_status bsc Where: bsc is: location

System response
Start of report for LOCATION 0: GSM CELL ID MCC MNC LAC CI RAC 001 01 1 1 8 (0001h) (0001h) (0008h) 001 01 1 6 NA (0001h) (0006h)

------------------------------------------------------------Primary Freq Type PGSM PGSM N/A 85

Secondary Freq Type N/A BCCH Frequency 65

------------------------------------------------------------Status GPRS Status PDCH Status RES PDCH Requested SW PDCH Requested Unbarred Unbarred PD Available 3 5 Barred Barred Unknown NA NA

3-256

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Examples

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 Active PCU site

No No No NA NA NA None 4 OFF OFF 1 FREE

No No No NA NA NA NA NA OFF OFF N/A INUSE UNAVL FREE INUSE UNAVL

----- ----- ----- ----- ----- ----SDCCH Norm Outer TCH/F Norm Inner TCH/F Ext Outer TCH/F 4 7 0 0 8 0 0 0 0 0 0 0 0 0 0 0 0 0 0 NA 0 0 0 0 NA 0 0 0 0 NA

PD CHANNEL End of Report

Example 6
{34144} This example displays the status of an in-service cell when the GPRS status is unbarred and congestion status is TRUE from the PCU, irrelevant of EGPRS in ON or OFF status. The EGPRS status is displayed in the field. disp_cell_s 3 Where: 3 is: location

System response
Start of report for LOCATION 3: GSM CELL ID MCC MNC 001 01

68P02901W23-S

3-257 Nov 2009

Examples

Chapter 3: Device/function related commands

LAC CI RAC Primary Freq Type EGSM

1 1 NA

(0001h) (0028h)

Secondary Freq Type N/A BCCH Frequency Status GPRS Status GPRS Congestion PDCH Status RES PDCH Requested SW PDCH Requested 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 EGPRS Chan Req Full Power Mode Ext Range Mode Active PCU Site 14 Unbarred Unbarred TRUE PD Available 10 5 No No No No No No NA 4 Avail OFF OFF 0 EGPRS Avail

FREE 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 End of Report. 8 14 0 0 0 0 0 0 1 6

INUSE 0 0 0 0 0 0 NA NA 6 2

UNAVL 0 0 0 0 0 0 0 0 0 0

3-258

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Examples

Example 7
{23311A} This example displays the cell status with both the Extended Range Cell for Data feature (ercgprsOpt) and EGPRS feature (egprsOpt) unrestricted. disp_cell_s 3 Where: 3 is: location

System response
Start of report for LOCATION 3: GSM CELL ID MCC MNC LAC CI RAC Primary Freq Type Secondary Freq Type BCCH Frequency Status GPRS Status PDCH Status RES PDCH Requested SW PDCH Requested 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 EGPRS Chan Req Full Power Mode Ext Range Mode Active PCU Site FREE 001 01 1 40 N/A EGSM N/A 14 Unbarred Unbarred, EGPRS Avail PD Available 10 5 No No No No No No N/A 4 Avail OFF ON 0 INUSE UNAVL (0001h) (0028h)

----- ----- -----

68P02901W23-S

3-259 Nov 2009

Examples

Chapter 3: Device/function related commands

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 Ext PD CHANNEL Ext EGPRS PD CHANNEL End of Report.

8 14 0 0 0 0 0 0 1 2 2 2

0 0 0 0 0 0 NA NA 6 2 0 0

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

Example 7
This example runs the disp_cell_status in high priority mode, BTS times out. disp_cell_status 15 high Where: 15 high is: location high priority

System response
COMMAND REJECTED: The BTS is very busy, please try again later.

3-260

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

disp_conn

Description
The disp_conn command displays the MSS connectivity between the RXCDR and the BSS sites connected to it. Security level Supported by OMC-R GUI Command type Prerequisites 1 No A (no operator actions) This command is only available at a BSC or RXCDR site.

NOTE
The term local site refers to the site at which the command is executed; the term remote site refers to the site to which the local site is connected.

Format
Syntax
disp_conn [<remote_entity_id>]

Input parameters
remote_entity_id The network identity of the remote site. The valid range is 1 to 254.

Examples
Example 1
Display all the MMS connectivity between the BSS and all RXCDRs which are connected to it, and are specified by equipped AXCDR devices at the BSC. disp_conn

68P02901W23-S

3-261 Nov 2009

Examples

Chapter 3: 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 9 0 BSS MMS id 1 1 is connected to RXCDR 5 - MMS id 4 0 Finished displaying BSS to RXCDR connectivity

Example 2
Display the MMS connectivity between the BSS and RXCDR 5, which is represented by equipped device AXCDR 5 at the BSC. disp_conn 5 Where: 5 is: remote entity ID.

System response
The BSS to RXCDR connectivity is as follows: BSS MMS id 1 1 is connected to RXCDR 5 - MMS id 4 0 Finished displaying BSS to RXCDR connectivity

3-262

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

disp_csfp

Description
The disp_csfp command displays the per site CSFP algorithm or flow control values. Security level Supported by OMC-R GUI Command type Prerequisites 1 Yes A (no operator actions) None

Format
disp_csfp <location> [<element>]

Input parameters
location Specifies the element location: 0 or bsc 1 - 140 pcu element algorithm flow_control Selects the CSFP algorithm method Selects the flow control value BSC BTS PCU

68P02901W23-S

3-263 Nov 2009

Examples

Chapter 3: Device/function related commands

Examples
Example 1
This example shows the inputs required to display the CSFP algorithm at the BSC. disp_csfp bsc algorithm Where: bsc algorithm is: location element

System response
Site 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: 3 flow_control is: location element

System response
Site Flow Control

----

------------

3-264

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Examples

Example 3
This example shows the required inputs required to display all elements at site 7. disp_csfp 7 Where: 7 is: location

System response
Site Flow Control Algorithm

---7

-----------10

--------ANY

Example 4
{25424} This example displays the csfp flow control value of PCU. disp_csfp pcu flow_control Where: pcu is: location

System response
Site Flow Control Algorithm

---PCU

-----------10

--------N/A

Example 5
{25424} This example displays the status of PCU CSFP . disp_csfp_status

68P02901W23-S

3-265 Nov 2009

References

Chapter 3: Device/function related commands

System response
SITE, ID 0,0 0,1 1,0 3,0 ... ... PCU,0 CSFP EQUIP YES * NO CODE LOADED YES SITE/LINK OOS YES ... ... YES ... ... CODE LOADED STATUS CODE LOADED

References
Related command
chg_csfp on page 3-95.

3-266

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

disp_csfp_status

Description
The disp_csfp_status command displays the status of all CSFPs equipped in the BSS network. The output generated by this command is a three column listing with the following information: SITE ID CSFP EQUIP STATUS Where: * NOT EQUIPPED DEVICE LOCKED CODE LOADED AWAITING CODE The site number Equipped indicator (YES or NO) The status of the CSFP device as shown below: is: printed only with unequipped indicator. the CSFP equipment is not installed. the CSFP device is locked. the CSFP device is busy-unlocked, and the device is code loaded. the CSFP device is enabled-unlocked, and the device is in a queue to be loaded, or is currently being downloaded with code. the CSFP device is out of service. the CSFP device is disabled-unlocked, and the device does not contain a valid software instance. link is out of service. 1 Yes A (no operator actions) This command is not allowed while in SYSGEN ON mode.

CSFP OOS NO CODE SITE/LINK OOS Security level Supported by OMC-R GUI Command type Prerequisites

Format
Syntax
disp_csfp_status

68P02901W23-S

3-267 Nov 2009

Example

Chapter 3: Device/function related commands

Input parameters
There are no input parameters with this command.

Example
This example shows the input required to display the status of the CSFP devices in the BSS network and the output when only one device is equipped and is loaded with code. disp_csfp_status

System response
SITE,ID 0,0 CSFP EQUIP YES STATUS CODE LOADED

References
Related command
chg_csfp on page 3-95.

3-268

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

disp_dte

Description
The disp_dte command displays DTE addresses. This command is primarily for use by field technicians or installers. Security level Supported by OMC-R GUI Command type Prerequisites 1 Yes A (no operator actions) None

Format
Syntax
disp_dte [<link> <link_number>] If no input parameters are specified, all BSS and OMC-R DTE addresses are displayed.

Input parameters
link The location of the link: bsc omcr cbc bsc_cbc link_num The link number range: 0 to 3 0 to 7 0 link at BSC link at OMC-R link at CBC or BSC_CBC BSC OMC-R Cell Broadcast Centre (CBC) BSC DTE Address for the CBC

68P02901W23-S

3-269 Nov 2009

Examples

Chapter 3: Device/function related commands

Examples
Example 1
In this example, the DTE link addresses are displayed (in binary coded decimal) when the command is entered: disp_dte

System response
BSS DTE addresses: Address #0: Address #1: Address #2: Address #3: 31070863210701 31070863210701 31070863210701 31070863210701

OMCR DTE addresses: Address #0: Address #1: Address #2: Address #3: Address #4: Address #5: Address #6: Address #7: 31031263245610 31031263245620 31031263245630 31031263245640 31031263245650 31031263245660 31031263245670 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: bsc 2 is: location link_num

System response
Address #2: 31070863210701

3-270

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

References

References
Related command
chg_dte on page 3-98.

68P02901W23-S

3-271 Nov 2009

disp_element

Chapter 3: Device/function related commands

disp_element

Description
The disp_element command displays the value of a database parameter in the CM database.

NOTE
The syntax required to display each CM database parameter is included in the parameter description in Chapter 6 CM database parameters.

Security level

Supported by OMC-R GUI Command type Prerequisites

Yes A (no operator actions) None

Format
Syntax
disp_element <database_parameter>[,<index1>][,<index2>] <location> [<cell_desc>]

Input parameters
database_parameter String identifying the database parameter in the CM database. index1 If a database parameter value to be displayed requires an index, the index value must be entered immediately after the database parameter name separated by a comma. Database parameters modified using the chg_cell_element command are stored in a four row data array. The rows in the data array are specified as bins in the chg_cell_element command. Individual database parameter values modified using the chg_cell_element command cannot be displayed using the disp_element command. When the disp_element command is used to display the values of parameters modified using the chg_cell_element command, the row (bin_num) is entered as the index1 value. All 32 values located in the entered row number are displayed. An example is included at the end of the description of this command.

3-272

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Examples

location Specifies the site location: 0 or bsc 1 - 140 {27955A} pcu or pcu_0 BSC BTS PCU

all cell_desc

Specifies all sites.

GSM cell ID of the cell to be displayed, preceded by cell_number=. The format for the GSM cell ID depends on: The system used (PGSM, EGSM, DCS1800, PCS1900). Whether the seven parameter GSM cell ID format or the four parameter GSM cell ID format has been enabled.

The name of the cell created using the cell_name command is entered in place of the cell_number. When the cell name is entered, it must be placed inside double quotation marks and be preceded by cell_name=.

NOTE
This command responds to the shortened input parameter cell= allowing entry of either the cell_number or the cell_name without further definition. The cell_desc can also be specified as all.

Examples
Example 1
In this example, the bit error rate loss threshold per day is 16 for site number 0: disp_element ber_loss_daily 0 Where: ber_loss_daily 0 is: database_parameter location

System response
ber_loss_daily = 16

68P02901W23-S

3-273 Nov 2009

Examples

Chapter 3: Device/function related commands

Example 2
In this example, the values of a database element modified using the chg_cell_element command are displayed. The bin number (0) is entered as the index value. disp_element rxlev_dl_ho,0 1 cell_number=5 4 3 2 1 61986 34944 Where: rxlev_dl_ho 0 1 5 4 3 2 1 61986 34944 is: database_parameter index (bin num) location cell_desc

NOTE
This example could have been entered as: disp_element rxlev_dl_ho,0 1 cell_name=london-south where the command cell_name had been used to assign the name london-south to the cell with ID = 5 4 3 2 1 61986 34944.

System response
rxlev_dl_ho[0] = alg_num: 0 alg_data: 8

Example 3
{28337} In this example, the value of the database element ss7_hsp_12_t1 is displayed. disp_element ss7_hsp_l2_t1 0 Where: ss7_hsp_12_t1 0 is: database_parameter location

System response
ss7_hsp_l2_t1 = 300000

3-274

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Examples

Example 4
{28000} This example displays the prp_fanout_mode parameter. disp_element prp_fanout_mode pcu Where: prp_fanout_mode pcu is: database_parameter location

System response
prp_fanout_mode = 1

Example 5
{31400} This example displays the value of td_enabled element. disp_element td_enabled 0 Where: td_enabled 0 is: database_parameter location

System response
td_enabled = 0

Example 6
{27508} This example displays the fieldeng_always_enabled element. disp_element fieldeng_always_enabled 0 Where: is: fieldeng_always_enabled 0 database_parameter location

68P02901W23-S

3-275 Nov 2009

Examples

Chapter 3: Device/function related commands

System response
fieldeng_always_enabled = 1

Example 7
{32340} This example allows the operator to display the value of cell barred delay (in seconds). disp_element cell_barred_delay 0 Where: cell_barred_delay 0 is: database_parameter location

System response
cell_barred_delay = 180 COMMAND ACCEPTED

Example 8
{26740} This example displays the value of dsp_error_inc element. disp_element dsp_error_inc 0 Where: dsp_error_inc 0 is: database_parameter location

System response
dsp_error_inc = 30

3-276

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Examples

Example 9
{26881} This example displays the value of ext_ul_dur. disp_element ext_ul_dur 0 Where: ext_ul_dur 0 is: database_parameter location

System response
ext_ul_dur = 24

Example 10
{31565} This example displays the status of the switch for AGCH flow control. disp_element _cell_data,20 1 cell_number=5 4 3 2 1 61986 34944 Where: _cell_data,20 1 5 4 3 2 1 61986 34944 is: database_parameter location cell description

System Response
_cell_data = 1

Example 11
This example displays the value of sig_lnk_tst_allow. disp_elem sig_lnk_tst_allow 0 Where: sig_lnk_tst_allow 0 is: database_parameter location

System Response
sig_lnk_tst_allow = 1

68P02901W23-S

3-277 Nov 2009

Examples

Chapter 3: Device/function related commands

Example 12
This example displays the value of sig_lnk_tst_allow. disp_elem sig_lnk_tst_allow 0 Where: sig_lnk_tst_allow 0 is: database_parameter location

System Response
sig_lnk_tst_allow = 0

Example 13
{29693A} This example displays the fer_meas_period value. disp_element fer_meas_period 0 Where: fer_meas_period 0 is: database_parameter location

System Response
fer_meas_period = 1

Example 14
{34164} This example displays the _bss_data,1 value. disp_element _bss_data,1 0 Where: _bss_data,1 0 is: database_parameter location

System Response
_bss_data,1 = 1

3-278

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Examples

Example 15
{34164} This example displays the _cell_data,21 value of cell 0 0 1 0 1 99 72 under site 114. disp_element _cell_data,21 114 cell 0 0 1 0 1 99 72 Where: _cell_data,21 114 0 0 1 0 1 99 72 is: database_parameter location cell description

System Response
_cell_data,21 = 1

Example 16
{34320G} This example displays the status of the PA Bias feature at site 2 with the feature enabled. disp_element power_save_enable 2 Where: power_save_enable 2 is: element name location

System Response
power_save_enable = 1

Example 17
{34303} This example displays the value of the Abis status element for H1 BTS (Site id = 1) when the Dual Abis Aware feature is enabled. disp_element _site_data,5 1 Where: _site_data, 5 1 is: database_parameter location

68P02901W23-S

3-279 Nov 2009

Examples

Chapter 3: Device/function related commands

System Response
_site_data,5 = 0

Example 18
{34303} This example displays the value of the Abis status element for all the BTS sites when the Dual Abis Aware feature is enabled. disp_element _site_data, 5 all Where: _site_data, 5 all is: database_parameter location

System Response
ELEMENT: _site_data SITE ---0 11 12 ELEMENT VALUE ------------0 1 0

Example 19
{23306} This example displays the value of the bsp_overload_protection parameter. disp_element bsp_overload_protection bsc Where: bsp_overload_protection bsc is: database_parameter location

System response
bsp_overload_protection = 0

3-280

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Examples

Example 20
{34321} This example displays the _bss_data,10 value. disp_element _bss_data,10 0 Where: _bss_data,10 0 is: element name location

System Response
_bss_data,10 = 1

Example 21
{34900} This example displays the value of _bss_data,6. disp_element _bss_data,6 0 Where: _bss_data,6 0 is: element name location

System Response
_bss_data,6 = 0

Example 22
This example displays the nacc_nc2_enabled value. disp_element nacc_nc2_enabled 0 Where: nacc_nc2_enabled 0 is: element name location

68P02901W23-S

3-281 Nov 2009

References

Chapter 3: Device/function related commands

System Response
nacc_nc2_enabled = 1

References
Related information
For detailed information on database parameters, refer to CM database parameters presentation on page 6-2.

Related commands
chg_element on page 3-106.

3-282

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

disp_equipment

Description
The disp_equipment command displays the software and hardware information of equipped devices and functions. Information displayed includes the parameters entered for a specific device or function using the equip command. {34145} The disp_equipment command displays the actual cell GPRS configuration information per PCU and PRP/PXP level along with the existing equipment information. Equipment configurations typically vary by location, therefore, the devices and functions available for display vary from site to site. This command is used to identify the site equipment configuration using location as the only command argument. The full option permits hardware information to be displayed in addition to the equipment parameters. This hardware information includes the hardware version number (hvn) displayed as a numerical value. A single hvn represents one or more kit numbers for a specific printed circuit board. The relationship of the hvn to the kit number is dependent on the equipment configuration. In later releases, a kit number is displayed in place of a hvn. A kit number includes the current hardware and firmware revisions of the printed circuit board. Kit numbers are incremented in response to either a hardware or firmware change. More than one firmware version can exist for any given hardware version of a printed circuit board. Kit numbers use the following format: SLN7133BA Where: SLN7133 B A is: a unique value identifying a specific printed circuit board. the hardware version of the printed circuit board represented as an alphabetical value. the firmware version of the printed circuit board.

This can then be followed by further information, dependent on the particular hardware and its revision level, such as: EFGH Each letter corresponds to a miscellaneous change made to the printed circuit board in the manufacturing process that did not require new hardware or firmware. This numerical value represents the current revision level of the most recent change. This is additional descriptive information related to the last revision to the printed circuit board.

REV 0 MEM 0238 - BIT ERROR RATE TEST

68P02901W23-S

3-283 Nov 2009

Format

Chapter 3: Device/function related commands

The disp_equipment command does not report the hvns for half size boards. Security level Supported by OMC-R GUI Command type Prerequisites 1 Yes A (no operator actions) None

Format
Syntax
disp_equipment <location> [<dev/func name> <id1> [<id2>] [<id3>]] [full]

Input parameters
location Specifies the equipment location: 0 or bsc 1 - 140 {27955A} pcu or pcu_0 dev/func name Literal that uniquely identifies the device or function id1 First identifier or the wild-card character *. id2 Second identifier or the wild-card character *. id3 Third identifier or the wild-card character *. full This is an optional parameter that is used to display the hardware-specific information for a device in addition to the configuration information entered when the device is equipped. When this option is used to display all of the equipment at a site, the output is a table which includes kit and serial numbers. BSC BTS PCU

NOTE
The full option is not allowed while in SYSGEN ON mode.

3-284

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Format

CIC syntax
Because the Circuit Identity Code (CIC) device can be specified in different ways, the different forms of syntax are detailed as follows: Valid for local transcoding: disp_equipment <location> CIC <cic_num1> Valid for remote transcoding: disp_equipment <location> CIC <cic_num1> disp_equipment <location> CIC <mms_id1> <mms_id2> <timeslot1>

Input parameters
location Specifies the location of the device: 0 or bsc 1 - 140 CIC Literal that uniquely identifies the CIC device. cic_num1 First CIC device number. cic_num2 Last CIC device number in a range. mms_id1 First MMS identifier. mms_id2 Second MMS identifier, or last in a range if TO is used. timeslot1 First timeslot. timeslot2 Second timeslot, or last in a range if TO is used. group1 First group. group2 Second group. BSC BTS

68P02901W23-S

3-285 Nov 2009

Examples

Chapter 3: Device/function related commands

* Indicates all CICs on the MMSs specified in the timeslot, regardless of group.

Examples
Example 1
In the following example, all equipment at location 0 are displayed: disp_equipment 0 full Where: 0 full is: location full option

System response
Device FRU Kit Number Serial Number HVN

---------------- -------------- ----------------- --------------- ---GPROC GPROC GPROC BSP CSFP MSI MMS MMS MTL RSL RSL SITE SITE PATH 2 3 1 0 0 0 0 0 0 2 3 3 4 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 GPROC2 Unavailable GPROC2 GPROC2 Unavailable MSII Unavailable Unavailable Unavailable Unavailable Unavailable Unavailable Unavailable Unavailable Not Applicable Unavailable Not Applicable Not Applicable Unavailable Not Applicable Unavailable Unavailable Unavailable Unavailable Unavailable Unavailable Unavailable Unavailable Not Applicable Unavailable Not Applicable Not Applicable Unavailable Not Applicable Unavailable Unavailable Unavailable Unavailable Unavailable Unavailable Unavailable Unavailable 4 255 4 4 255 4 255 255 255 255 255 255 255 255

3-286

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Examples

BSS LCF Type

1 1

0 0

Not Applicable Not Applicable Slot HVN

Cage

------- -------- -------- ----KSWX 0 21 48

Example 2
In the following example, only KSWX at location 0 are displayed: disp_equipment 0 kswx * * * full Where: 0 kswx *** full is: location device/function name 1st, 2nd, and 3rd identifier wild cards. full option

System response
Type Cage Slot HVN

----- -------- -------- -------KSWX 0 21 48

Example 3
This example shows the values entered when RTF 0 1 at location 2 was equipped. disp_equipment 2 rtf 0 1 Where: 2 rtf 0 1 is: location device/func name first identifier second identifier

68P02901W23-S

3-287 Nov 2009

Examples

Chapter 3: Device/function related commands

System response
Capacity of carrier: Type of carrier: RTF identifier: FULL

NON_BCCH 0 1 0 262 01 510 211

The primary Unique PATH id is:

GSM cell to which this carrier is assigned: Carrier absolute radio freq. channel: 61

Carrier frequency hopping indicators: Carrier training sequence codes:

0 0 0 0 0 0 0 0

5 5 5 5 5 5 5 5 0

KSW pair that manages this carrier: Cell zone: 0

Number of extended range timeslots allowed: SDCCH load: 2 2 2 4 2

SDCCH placement priority:

Channel allocation priority: The maximum number of PDCHs: The number of reserved PDCHs: 32 kbps GPRS TRAU allowed:

yes

Example 4
This example displays information for PCU 0 (3 TRAU GDS and 2 PMCs equipped on 2 PRPs, 8 64 K air PDTCHs, 81 16 K air PDTCHs) when EGPRS is unrestricted. disp_equipment 0 PCU 0 Where: 0 PCU 0 is: location device/func name PCU identifier

3-288

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Examples

System response
PCU identifier: 0 127.0.0.1 255.255.255.255 127.0.0.1

PCU IP Address[ip_address]:

PCU Subnet Mask[subnet_mask]:

PCU Router IP Address[router_ip_address]: NSEI: 27 Primary Cells: 001 01 1 1 001 01 1 6 001 01 1 3 001 01 1 33 001 01 1 18 Provisioned

Requested

------------------------Usable PRP PDTCHs: 240 89 113 or 32 K ---75 or 16 K ---151

Usable 16 K GDS Resources: 372 64 K --Max Configurable PDTCHs: 64

Example 5
{28337} This example displays information for HSP MTL. disp_equipment 0 mtl 1 0 Where: 0 mtl 1 0 is: location device/func name first identifier second identifier

68P02901W23-S

3-289 Nov 2009

Examples

Chapter 3: Device/function related commands

System response
Device ID for the MTL: 1 DS0 channels for this MTL: 31 First MMS identifier for this device: 0 Second MMS identifier for this device: 1 Timeslot on MMS where this device appears: 1

Example 6
{28337} This example displays information for 64 k MTL. disp_equipment 0 mtl 10 0 Where: 0 mtl 10 0 is: location device/func name first identifier second identifier

System response
Device identification for this MTL: 10 DS0 channels for this MTL: 1 First MMS identifier for this device: 1 Second MMS identifier for this device: 0 Timeslot on MMS where this device appears: 8

Example 7
{28337} This example displays an MTL LCF handling the HSP MTL. disp_eq 0 lcf 1 Where: 0 lcf 1 is: location device/func name first identifier

3-290

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Examples

System response
Function ID for the LCF: 1 Number of DS0 channels the LCF can manage as MTLs [max_mtls]: 31 Number of CBLs the LCF can manage[max_cbls]: 0 Number of GSLs the LCF can manage[max_gsls]: 0

Example 8
{28351} This example displays the PXP DPROC with the FULL option. disp_equipment pcu_0 dproc 4 0 full Where: pcu_0 dproc 4 0 full is: location device/function name first identifier second identifier option

System response
DPROC id: 4 DPROC type: PXP Hardware Information: PCI Vendor Id: 1223h PCI Device Id: 0048h PCI Revision Id: 1h PCI Type: UNKNOWN HSC Type: UNKNOWN IP Address Information: DPROC (750): 10.0.130.1 Current Cell Mapping: GSM CELL ID SITE MCC MNC LAC CI LCI ---- ------------------------------------ --11 001 01 403 (0193h) 11 (000Bh) 0

68P02901W23-S

3-291 Nov 2009

Examples

Chapter 3: Device/function related commands

Example 9
{28351} The example displays a PXP DPROC. disp_equipment PCU DPROC 1 Where: PCU DPROC 1 is: location device/function name first identifier

System response
DPROC id: 1 DPROC type: PXP

Example 10
{26740} This example displays the ETH device. disp_equipment bsc eth 1 0 0 Where: bsc eth 1 0 0 is: location device/function name first identifier second identifier third identifier

System response
PSI identifier: 1 Ethernet port id: 0

3-292

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Examples

Example 11
{26481} This example displays Horizon II micro cabinet at site 5. disp_equip 5 CAB 15 0 0 Where: 5 CAB 15 0 0 is: location device/function name first identifier second identifier third identifier

System response
CABINET identifier: 15 Cabinet type: HORIZON2MINI_EXT Frequency type: PGSM

Example 12
{34145} This example displays the information for PCU 0 without full option. disp_equipment 0 PCU 0 Where: 0 PCU 0 is: location device/function name first identifier

68P02901W23-S

3-293 Nov 2009

Examples

Chapter 3: Device/function related commands

System response
PCU identifier: 0 127.0.0.1 255.255.255.255 127.0.0.1

PCU IP Address[ip_address]:

PCU Subnet Mask[subnet_mask]:

PCU Router IP Address[router_ip_address]: NSEI: 27 PRP Fanout Mode: GSM CELL ID MCC MNC LAC CI LCI 1

--- --- --- --- --001 01 001 01 001 01 001 01 696 696 696 696 26 27 16 72 0 2 1 3 Provisioned Requested

------------------------Usable PRP PDTCHs: 240 89 113 or 32 K ---75 or 16 K ---151

Usable 16 K GDS Resources: 372 64 K --Max Configurable PDTCHs: 64

Example 13
{34145} This example displays the information for PCU 0 with full option. disp_equipment 0 PCU 0 full Where: 0 PCU 0 full is: location device/function name first identifier option

3-294

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Examples

System response
PCU identifier: 0 127.0.0.1 255.255.255.255 127.0.0.1

PCU IP Address[ip_address]:

PCU Subnet Mask[subnet_mask]:

PCU Router IP Address[router_ip_address]: NSEI: 27 PRP Fanout Mode: GSM CELL ID MCC MNC LAC CI LCI 1

--- --- --- --- --001 01 001 01 001 01 001 01 696 696 696 696 26 27 16 72 0 2 1 3 Provisioned Requested

------------------------Usable PRP PDTCHs: 240 89 113 or 32 K ---75 or 16 K ---151

Usable 16 K GDS Resources: 372 64 K --Max Configurable PDTCHs: 64

Hardware Information: Not Applicable Configured SITE 1 10 10 1 LCI 0 2 1 3 PRP 1 1 2 2 16/32/64k 6/0/6 0/12/0 2/0/6 5/0/3 13 24 56 Database GDS RES/SW 8/4 8/4 7/4 4/4 93 RCIs: 13 RCIs: 12 RCIs: 15 16/32/64k -- 6/0/6 0/12/0 2/0/6 5/0/2 All PD Configured -- Yes Yes No Yes

---- ------------------------------------

NUMBER OF ACTUAL CONNECTED GCIs: NUMBER OF ACTUAL 16K GCIs: NUMBER OF ACTUAL 32K GCIs: NUMBER OF ACTUAL 64K GCIs: NUMBER OF FREE DS0: 7

NUMBER OF ACTUAL FREE GCI COUNT: 31

68P02901W23-S

3-295 Nov 2009

Examples

Chapter 3: Device/function related commands

Example 14
{34145} This example displays the information for PRP DPROC 4 0 0 on PCU 0. disp_equipment pcu DPROC 4 0 0 FULL Where: PCU DPROC 4 0 0 FULL is: location device/function name first identifier second identifier third identifier option

System response
DPROC id: 4 DPROC type: PRP Hardware Information: PCI Vendor Id: 1146h PCI Device Id: 6750h PCI Revision Id: 1h PCI Type: UNKNOWN HSC Type: UNKNOWN Current Cell Mapping: GSM CELL ID SITE 1 10 10 1 MCC 001 001 001 001 MNC 01 01 01 01 LAC 696 696 696 696 CI 26 27 16 72 LCI 0 2 1 3 13 24 56 Configured 16/32/64k 6/0/6 0/12/0 2/0/6 5/0/3 93 RCIs: 13 RCIs: 12 RCIs: 15 Database GDS RES/SW -- 8/4 8/4 7/4 4/4 16/32/64k -- 6/0/6 0/12/0 2/0/6 2/0/2 All PD Configured -- Yes Yes No Yes

---- ------------------------------------

NUMBER OF ACTUAL CONNECTED GCIs: NUMBER OF ACTUAL 16K GCIs: NUMBER OF ACTUAL 32K GCIs: NUMBER OF ACTUAL 64K GCIs:

The output is explained as follows: PRP: indicates the PRP device ID. (PXP PPROC Device ID equals to PXP DPROC Device ID plus 16.)

3-296

68P02901W23-S Nov 2009

Examples

Example 17
{34145} This example attempts to display information for PRP DPROC 4 0 0 on PCU 0 with full option which is rejected due to the same query being performed by the other MMI session.

NOTE
The rejection output is similar for the simultaneous PCU, PXP DPROC and PPROC query by several MMI sessions.

disp_equipment pcu DPROC 4 0 0 FULL Where: PCU DPROC 4 0 0 FULL is: location device/function name first identifier second identifier third identifier option

---- -----------------------------------Command Rejected: System Busy.

68P02901W23-S

3-301 Nov 2009

Examples

Chapter 3: Device/function related commands

Example 18
{30365} In this example, the BSS supports the display of disp_eq CAB with full information for high power Horizon II micro with FRU type as H2MICRO_HIGH_PWR. disp_eq 4 cab 1 0 full Where: 4 cab 1 0 FULL is: location device/function name first identifier second identifier option

System response
CABINET identifier: 1 Cabinet type[cabinet_type]: HORIZON2MICRO_EXT Frequency Type[frequency_type]: DCS1800 [4] Hardware Information: FRU: H2MICRO_HIGH_PWR Kit Number: Not Applicable Serial Number: Not Applicable Hardware Version Number: Unavailable PSU: M14 +27 DC Kit Number: Not Applicable Serial Number: Not Applicable Hardware Version Number: Unavailable PSU: No Battery Kit Number: Not Applicable Serial Number: Not Applicable Hardware Version Number: Unavailable

3-302

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Examples

Example 19
{23311A} This example displays RTF when the Extended Range Cell for Data feature is unrestricted (ercgprsOpt = 1), and also ext_timeslots and ext_pdchs are displayed.

NOTE
ext_pdchs is not displayed if the Extended Range Cell for Data feature is restricted (ercgprsOpt = 0).

disp_eq 62 rtf 2 0 Where: 62 rtf 2 0 is: location device/function name first identifier second identifier

System response
Capacity of carrier: FULL Type of carrier: NON_BCCH RTF identifier: 2 0 Primary Unique PATH id is: 0 GSM cell to which this carrier is assigned: 001 01 Carrier absolute radio freq. channel: 647 Carrier frequency hopping indicators: 255 255 255 255 255 255 255 255 Carrier training sequence codes: 0 0 0 0 0 0 0 0 Number of extended range timeslots allowed[ext_timeslots]: 0 Number of extended range PDCHs allowed[ext_pdchs]: 0 SDCCH load[sd_load]: 4 SDCCH placement priority[sd_priority]: 0 Channel allocation priority[chan_alloc_priority]: 0 Packet Radio Capability[pkt_radio_type]: 32K Half Rate enabled: 0 allow_8k_trau: Yes 105 6202

68P02901W23-S

3-303 Nov 2009

References

Chapter 3: Device/function related commands

References
Related information
The hardware requirements and revision levels are given in Release Notes specific to each software release.

Related commands
equip on page 3-403 modify_value on page 3-456

3-304

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

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 Supported by OMC-R GUI Command type Prerequisites 1 Yes A (no operator actions) None

Format
Syntax
disp_exp_config <location>

Input parameters
location Specifies the location of the site. Values are: 0 or bsc 1 - 140 BSC BTS

Example
The following example displays the TDM highway configuration of the BSC: disp_exp_config 0 Where: 0 is: the location

68P02901W23-S

3-305 Nov 2009

Example

Chapter 3: Device/function related commands

System response
Highway 0 (CAGE 0) ----------------Connected to highway 1 by EXP 0 (U21 U9) Connected to highway 2 by EXP 1 (U22 U8) Connected to highway 3 by EXP 2 (U23 U7) Highway 1 (CAGE 1) ----------------Connected to highway 0 by EXP 0 (U21 U9) Connected to highway 2 by EXP 1 (U22 U8) Connected to highway 3 by EXP 2 (U23 U7) Highway 2 (CAGE 2) ----------------Connected to highway 0 by EXP 0 (U21 U9) Connected to highway 1 by EXP 1 (U22 U8) Connected to highway 3 by EXP 2 (U23 U7) Highway 3 (CAGE 3) ----------------Connected to highway 0 by EXP 0 (U21 U9) Connected to highway 1 by EXP 1 (U22 U8) Connected to highway 2 by EXP 2 (U23 U7)

3-306

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

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 Supported by OMC-R GUI Command type Prerequisites 1 Yes A (no operator actions) None

Format
Syntax
disp_flash

Input parameters
There are no input parameters associated with this command.

Example
The following example shows the version information of the flash EEPROM: disp_flash

68P02901W23-S

3-307 Nov 2009

Example

Chapter 3: Device/function related commands

System response
Version : Date 1.5.0.0.8 23:51

: 01/04/97

Checksum: Size Where:

0x3D691A2

: 838702 Bytes is: Version Date the version of the software the system is currently running. the date and time the current Flash EEPROM load was created. The date is in date/month/year format. the checksum value of the current Flash EEPROM load. the size of the current EEPROM load, measured in bytes.

Checksum Size

3-308

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

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 Supported by OMC-R GUI Command type Prerequisites 1 No A (no operator actions) 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 1 - 140 gclk_id Identifier for GCLK. Values are 0 or 1. BSC BTS

68P02901W23-S

3-309 Nov 2009

Example

Chapter 3: Device/function related commands

Example
In this example, the LTA values for GCLK 1 at BSC 0 are displayed: disp_gclk_avgs 0 1 Where: 0 1 is: location gclk ID

System response
The GCLK 1 0 0 Frequency Register values at Site 0 are:

80 80 80 80 8F 8F

Long Term Average = 80 Since the system reads the frequency every 30 minutes, these six samples represent 3 hours. The first value in the display is the oldest. 80 is the value of a GCLK calibrated to 16.384 MHz.

References
Related information
An alarm is generated if 25% or more of the stored clock frequency readings differ from the calculated LTA by more than the value that is defined by the lta_alarm_range parameter.

Related command
clear_gclk_avgs on page 3-173.

3-310

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

disp_gclk_cal

Description
The disp_gclk_cal command displays the contents of the clock frequency register when the GCLK is in the phase-lock mode. The clock frequency register gives an indication of the calibration status of the GCLK. When the command is entered the system displays a value in hexadecimal figures. A perfectly calibrated clock displays a reading of 80. Any value more than or less than 80 indicates the degree the GCLK calibration has drifted. As the GCLK ages the value shown in the clock frequency register drifts towards the upper or lower level GCLK calibration limits. If the upper or lower calibration thresholds are met or exceeded, the system generates a recalibration alarm. Using the clock frequency register value can give an estimate of how far the GCLK has drifted from its original calibration and how long it is until the GCLK requires recalibration. Since each GCLK has different aging characteristics, this estimate is not exact. The upper level of all GCLKs is E9 (hexadecimal). The lower level is 38 (hex) for revisions 0 through 8. The lower level is 1a (hex) for revision 9.

Use the disp_hardware_version command to view the revision number. This command also reports if the clock is not in phase lock. Security level Supported by OMC GUI-R Command type Prerequisites 1 No A (no operator actions) This command is not allowed while in the SYSGEN ON mode. This command is not allowed for M-Cell sites.

Format
Syntax
disp_gclk_cal <location> <gclk_id>

68P02901W23-S

3-311 Nov 2009

Examples

Chapter 3: Device/function related commands

Input parameters
location Specifies the location of the GCLK: 0 or bsc 1 - 140 gclk_id Specifies the identity of the GCLK. Values are 0 or 1. BSC BTS

Examples
Example 1
In this example, GCLK 0 at BSC 0 is not in phase lock mode: disp_gclk_cal 0 0 Where: 0 0 is: location 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: 0 0 is: location gclk_id

System response
GCLK 0 Clock frequency register value = 99

3-312

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

References

References
Related information
The system reads the clock frequency register of each GCLK once every half hour after synchronization after the GCLK has phase_locked. A rolling average for each GCLK is calculated of up to 48 clock frequency register readings. This average is the Long Term Average (LTA). An alarm generates if 25% or more of the stored clock frequency readings differ from the calculated LTA by more than the value that is defined by the lta_alarm_range parameter.

Related commands
clear_gclk_avgs on page 3-173 disp_gclk_avgs on page 3-309

68P02901W23-S

3-313 Nov 2009

disp_gsm_cells

Chapter 3: Device/function related commands

disp_gsm_cells

Description
The disp_gsm_cells command displays the GSM cells associated with a specific site (BTS or BSC). Both primary and secondary frequencies are displayed for Dual Band Cells. Primary and secondary frequency types are displayed for dual band cells. Security level Command type Prerequisites 1 A (no operator actions) 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 1 - 140 BSC BTS

Examples
Example 1
In this example, no GSM cells are associated with the BSC: disp_gsm_cells 0 Where: 0 is: location

3-314

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Examples

System response
There are no associated GSM cells

Example 2
In this example, the GSM cells associated with a BTS are displayed: disp_gsm_cells 11 Where: 11 is: location

System response
Associated GSM cells: GSM CELL ID Freq MCC --543 MNC --21 8 LAC --------------61713 (0xF111h) (0x8h) BVCI: CI -------------4368 (0x1110h) N/A 8736 (0x2220h) N/A 13114 (0x222Ah) 2 EGSM bexley-west 1 EGSM london-north LCI Type Cell Name

--- ----- ---------------0 EGSM london-south

RAC: 543 21

61713 (0xF111h) 96 (0x60h) BVCI:

RAC: 543 21

61713 (0xF111h) N/A BVCI: N/A 3

RAC:

Number of Sectors:

68P02901W23-S

3-315 Nov 2009

References

Chapter 3: Device/function related commands

References
Related commands
add_cell on page 3-22 disp_cell on page 3-241 copy_cell on page 3-179 del_cell on page 3-192

3-316

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

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. 1 No A (no operator actions) The disp_hdlc command cannot be used for CSPF GPROCs or M-Cell sites.

Security level Supported by OMC-R GUI Command type Prerequisites

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 1 - 140 all BSC BTS All sites

68P02901W23-S

3-317 Nov 2009

Example

Chapter 3: Device/function related commands

dev/func name Literal that uniquely identifies the device or function dev/func_id_1 First device or function identifier. dev_func_id_2 Second device or function identifier. dev_func_id_3 Third device or function identifier.

Example
Example 1
This example shows how to display the HDLC channel assignments for BSP 0 0 0 at the BSC. disp_hdlc bsc BSP 0 0 0 Where: bsc BSP 0 0 0 is: location device / function name device / function ID device / function ID 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 0 HDLC Channel Offset 1 2 3 1

---------------------------------------------------Test Free OML Free RSL Free RSL Free OML 0 0 0 XBL 0 0 0 RSL Free RSL Free OML Free RSL Free RSL Free RSL Free OML Free RSL Free RSL Free RSL Free

3-318

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Example

Example 2
{28337} This example displays the HDLC channel assignments for LCF 2 0 which has HSP MTL. disp_hdlc 0 lcf 2 Where: 0 lcf 2 is: location device/function name device/function ID

System response
Device: GPROC 5 0 0 (CPU ID: 0x0114)

Function: LCF 2 0 0

Number of static LAPD Links (RSLs/XBLs) allocated to current board: N/A

Legend: G/RSL = Free channel configured for a GSL or RSL.

HDLC Channel

HDLC Channel Offset

Range

------------

----------------------------------------------------------------

00-03 04-07 08-11 12-15 16-19 20-23 24-27 28-31

Test Free MTL 1 0 0 MTL 1 0 0 MTL 1 0 0 MTL 1 0 0 MTL 1 0 0 MTL 1 0 0 MTL 1 0 0

MTL 1 0 0 MTL 1 0 0 MTL 1 0 0 MTL 1 0 0 MTL 1 0 0 MTL 1 0 0 MTL 1 0 0 MTL 1 0 0

68P02901W23-S

3-319 Nov 2009

disp_hopping

Chapter 3: Device/function related commands

disp_hopping

Description
The disp_hopping command displays the hopping information for a cell (identified by cell_desc), based on the arguments entered with the command.

cell_desc only
If the cell_desc only is entered, the command displays hopping systems for the specific cell. The following information is displayed: Frequency hopping indicators (fhi). Hopping sequence numbers. Mobile allocations.

cell_desc and fhi

If the fhi is entered along with the cell_desc, a more detailed output of the particular hopping systems is provided. The following information is displayed: Carriers that are using the specified hopping system. Timeslots that are using the specified hopping system.

cell_desc and active string

If the string active is entered together with the cell_desc, all of the currently active hopping systems for the cell are displayed. The following information is displayed: Active hopping systems on a carrier and timeslot basis. Frequency hopping indicators (FHIs). Hopping sequence numbers (HSNs) for each FHI. Mobile allocations.

3-320

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Format

Security level Supported by OMC-R GUI Command type Prerequisites Operator actions

1 Yes B (operator actions required) This command is not allowed while in SYSGEN ON mode when the active option is used. Place the system in the SYSGEN OFF mode if the active option is used before entering this command.

Format
Syntax
disp_hopping <site> [active] disp_hopping <cell_desc> [<fhi> | active]

Input parameters
site Specifies the location: 0 or bsc 1 - 140 BSC 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.

68P02901W23-S

3-321 Nov 2009

Examples

Chapter 3: Device/function related commands

NOTE
This command responds to the shortened input parameter cell= allowing entry of either the cell_number or the cell_name without further definition.

fhi Frequency hopping indicator. active The active option displays the currently active hopping systems.

Examples
Example 1
In this example, only the GSM cell ID in seven parameter format is entered and the related hopping information for the cell is displayed. disp_hopping cell_number=5 4 3 2 1 61986 34944 Where: 5 4 3 2 1 61986 34944 is: cell_desc

The example below shows the same cell number in four parameter format: disp_hopping cell_number=543 21 61986 34944 Where: 543 21 61986 34944 is: cell_desc

System response
GSM CELL: 543 21 61986 (f222h) 34944 (8880h) Baseband (BBH) Hopping FHI: 0 FHI: 1 FHI: 2 FHI: 3 HSN = 0 HSN = 7 HSN = 9 HSN = 12 MA = 12 30 45 MA = 31 37 50 MA = 31 32 33 34 45 46 MA = 33 76 91

3-322

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Examples

Example 2
In this example, the fhi is entered together with the GSM cell ID. The output contains the carriers using the hopping system number in addition to all of the timeslots for each carrier. disp_hopping cell_number=5 4 3 2 1 61986 34944 1 Where: 5 4 3 2 1 61986 34944 1 is: cell_desc fhi

System response
GSM CELL: 543 21 61986 (f222h) 34944 (8880h) Carrier arfcn: Carrier arfcn: Carrier arfcn: 33 Timeslots: 76 Timeslots: 91 Timeslots: 0 1 1 2 3 5 7 0 1 2 3 4 5 6 7

Example 3
In this example, the active string is entered together with the GSM cell Id. disp_hopping cell_number=5 4 3 2 1 61986 34944 active Where: 5 4 3 2 1 61986 34944 active is: cell_desc active string

System response
GSM CELL: 543 21 61986 (f222h) 34944 (8880h)

Active Hopping Systems:

Carrier arfcn: 33

Timeslot: 0

FHI: 3

HSN: 0

MA: 33 76 91

Timeslot: 1

FHI: 3

HSN: 0

MA: 33 76 91

Timeslot: 2

FHI: 0xFF

HSN: 0

MA: (no MA)

68P02901W23-S

3-323 Nov 2009

References

Chapter 3: Device/function related commands

References
Related command
chg_element on page 3-106.

3-324

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

disp_level

Description
The disp_level command displays the current security level. Security level Supported by OMC-R GUI Command type Prerequisites 4 No A (no operator actions) None

Format
Syntax
disp_level

Input parameters
There are no input parameters associated with this command.

Example
This example displays the output of the disp_level command. disp_level

System response
Current security level is 1

References
Related commands
chg_level on page 3-142 sysgen_mode on page 3-540

68P02901W23-S

3-325 Nov 2009

disp_link

Chapter 3: Device/function related commands

disp_link

Description
The disp_link command displays RXCDR, OML, MTL, and CBL links between two sites. The sites are the BSC) and either the MSC, the OMC, or the Cell Broadcast Centre, when an RXCDR is being used. Security level Supported by OMC-R GUI Command type Prerequisites 1 No A (no operator actions) This command is only available on an RXCDR.

Format
Syntax
disp_link

Input parameters
There are no input parameters associated with this command.

Example
In this example, the RXCDR OML and RXCDR MTL links between the BSC and the MSC are displayed: disp_link

3-326

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Example

System response
The CEPT nailed connections are as follows:-

Incoming mms id: 0 0 Timeslot: 16 Outgoing MMS Id 1 0 Timeslot: 16

incoming mms id: 0 0 Timeslot: 17 Outgoing MMS Id 1 0 Timeslot: 17

incoming mms id: 0 0 Timeslot: 18 Outgoing MMS Id 1 0 Timeslot: 18

incoming mms id: 0 0 Timeslot: 19 Outgoing MMS Id 1 0 Timeslot: 19

incoming mms id: 0 0 Timeslot: 20 Outgoing MMS Id 1 0 Timeslot: 20

incoming mms id: 0 0 Timeslot: 21 Outgoing MMS Id 1 0 Timeslot: 21

incoming mms id: 0 0 Timeslot: 22 Outgoing MMS Id 1 0 Timeslot: 22

incoming mms id: 0 0 Timeslot: 23 Outgoing MMS Id 1 0 Timeslot: 23

incoming mms id: 0 0 Timeslot: 24 Outgoing MMS Id 1 0 Timeslot: 24

incoming mms id: 0 0 Timeslot: 25 Outgoing MMS Id 1 0 Timeslot: 25

Finished displaying all nailed connections

68P02901W23-S

3-327 Nov 2009

disp_link_usage

Chapter 3: Device/function related commands

disp_link_usage

Description
The disp_link_usage command displays all PATH devices equipped through a particular MSI/MMS combination at a site. The output from this command is system configuration dependent. Security level Supported by OMC-R GUI Command type Prerequisites 1 Yes A (no operator actions) 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 0 to 140 Indicates that the MSI/MMS combination is at the BSC 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. {22169} 0 to 95 0 to 9 MMS_identifier Specifies the MMS identifier to be displayed. Values are 0 or 1. the MSI is at the BSC. the MSI is at a BTS.

3-328

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Example

Example
This example displays the PATH devices equipped on MSI/MMS combination 1 0 at site 1. disp_link_usage 1 1 0 Where: 1 1 0 is: location MSI_identifier MMS_identifier

System response
Start of Report: SITE ID : 1 MSI ID MMS ID : 1 : 0 End of Report

PATH 1 0 0 PATH 2 0 0 PATH 3 0 0 PATH 4 0 0 PATH 5 0 0 PATH 6 0 0 PATH 7 0 0 PATH 8 0 0 PATH 9 0 0

68P02901W23-S

3-329 Nov 2009

disp_mms_ts_usage

Chapter 3: Device/function related commands

disp_mms_ts_usage

Description
The disp_mms_ts_usage command displays the timeslot usage on any MMS link. The output gives the status of each timeslot in the form of: Unavailable for use (UNAVAILABLE) Unallocated (UNUSED) Allocated to RSL (RSL) Allocated to RTF (RTF) Allocated to GBL (GBL) Allocated to GSL (GSL) Allocated to GDS (GPRS_DATA) Allocated to XBL (XBL) Allocated to OML (OML) Allocated to MTL (MTL) Allocated to terrestrial circuit (CIC) Allocated to CBL (CBL) Allocated to RXCDR link (RXCDR_LINK) Reserved (RESERVED) Nailed (NAILED) Nailed on a path (NAILED PATH Timeslot Usage)

It also displays the timeslots that are reserved for dynamic allocation.

NOTE
16K_DYN_RSL always falls under a 16 K RSL timeslot as the first group. It indicates that 3 extra timeslots are reserved for dynamic allocation.

3-330

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Format

10 11 12 13 14 15 16 17 19 20 21 22 23 24 25 26 27 28 29 30 31

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

IDLE IDLE IDLE IDLE IDLE IDLE IDLE IDLE IDLE IDLE IDLE IDLE IDLE IDLE IDLE IDLE IDLE IDLE IDLE IDLE IDLE

Ater*: Timeslot is an Ater but has CIC(s) equipped on it.

3-334

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Examples

End of Report.

Example 2
This example displays the output on an RXCDR MMS showing the status of Ater channels, the Ater channel status, and CICs assigned to the Ater channels. disp_mms_ts_usage 0 18 0 Where: 0 18 0 is: location 1st digit of MMS identifier 2nd digit of MMS identifier

System response
Start of Report: Site: 0 MMS: 18 0

General Timeslot Usage: A S S O C I A T E D TS Port Usage Size 0 1 0-1 2-3 4-5 6-7 2 3 0-1 2-3 UNAVAILABLE Ater Ater* Ater* Ater 64 K_XBL Ater* Ater* 2 1 0 64 K UNKNOWN UNKNOWN UNKNOWN UNKNOWN 0 UNKNOWN UNKNOWN 36 35 4 0 4 0 4 3 63 62 4 0 4 0 31 30 Device ID Type BSS State CIC MMS TS Port Size

68P02901W23-S

3-335 Nov 2009

Examples

Chapter 3: Device/function related commands

4-5 6-7 4 0-1 2-3 Ater*:

Ater* Ater* Ater* Ater*

UNKNOWN UNKNOWN UNKNOWN UNKNOWN

34 33 40 39

4 0 4 0 4 0 4 0

2 1 8 7

Timeslot is an Ater but has CIC(s) equipped on it.

End of Report.

Example 3
The following example displays the timeslot utilization on MMS 0 0 at the BSC, with a 16 kbit/s XBL equipped on timeslot 8, group 3 and a 64 kbit/s XBL equipped on timeslot 9. disp_mms_ts_usage 0 0 0 Where: 0 0 0 is: location 1st digit of MMS identifier 2nd digit of MMS identifier

System response:
Site: 0 MMS: 0 0

General Timeslot Usage: TS Usage Device ID Type Site CIC Group CIC State TS Group TS Usage Device ID Type Site CIC Group CIC State TS Group 0 1 UNAVAILABLE CIC CIC CIC 60 61 62 0 1 2 IDLE IDLE IDLE RTF Site RTF TS RTF Site RTF TS

3-336

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Examples

CIC 2 CIC CIC CIC CIC 3 4 5 6 7 8 CIC NAILED UNUSED UNUSED RESERVED CIC CIC CIC XBL 9 XBL 1 0 0 2 0 0 16 64 0 0 0 1 0

63 64 65 66 67 68

3 0 1 2 3 0

IDLE IDLE IDLE IDLE IDLE IDLE 11

64 65 66

0 1 2 3

IDLE IDLE IDLE

10 UNUSED 11 UNUSED 12 UNUSED 13 UNUSED 14 UNUSED 15 UNUSED 16 MTL 3 0 0 0

68P02901W23-S

3-337 Nov 2009

Examples

Chapter 3: Device/function related commands

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

1 0 0

Example 4
This example displays the timeslot usage for an E1 link supporting a GBL. The link runs from a PICP MMS in PCU 0 cabinet to the SGSN. disp_mms_ts_usage pcu_0 6 0 Where: pcu_0 6 0 is: location 1st digit of MMS identifier 2nd digit of MMS identifier

3-338

References

Chapter 3: Device/function related commands

14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31

MTL MTL MTL MTL MTL MTL MTL MTL MTL MTL MTL MTL MTL MTL MTL MTL MTL MTL

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

End of Report.

References
Related information
The timeslots states display as UNKNOWN when running in sysgen mode.

Related command
chg_ts_usage on page 3-161.

3-342

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

disp_neighbor

Description
The disp_neighbor command displays information of a specific neighbor cell or all neighbor cells. It also displays additional information for UTRAN and Blind Search neighbor cells. A neighbor cell can be internal or external. An internal neighbor cell is inside the BSS in which the source cell is located. An external neighbor cell is outside of the BSS in which the source cell is located. The cell_name created using the cell_name command is used to specify the source cell in place of the src_gsm_cell_id. A cell_name is also used to specify an internal neighbor cell in place of the neighbor_cell_id. A cell_name cannot be used to specify an external neighbor cell. When the all option is used, the cell_name for each of the internal neighbor cells is displayed immediately after the neighbor_cell_id. If a cell_name has not been assigned to a neighbor_cell_id, No Name Defined is presented in the Neighbor cell name field. The cell_name for an external neighbor cell is not displayed. If a neighbor cell is an external cell, N/A. is presented in the Neighbor cell name field. If the Inter_RAT (Radio Access Technology) Handover and/or the Enhanced 2G/3G Handover features are unrestricted, this command supports the UTRAN cell identity format. Security level Supported by OMC-R GUI Command type Prerequisites 1 Yes A (no operator actions) For handovers to UTRAN cells, the Inter-RAT handover feature and/or the Enhanced 2G/3G Handover feature must be unrestricted.

Format
Syntax
disp_neighbor <src_cell_desc> [<neighbor_cell_desc>|all] disp_neighbor <src_cell_desc> [TEST <test neighbor_cell_desc>]

68P02901W23-S

3-343 Nov 2009

Examples

Chapter 3: Device/function related commands

Input parameters
src_cell_desc GSM cell ID of the neighbor list owner cell to be displayed. GSM or UTRAN Cell ID of the neighbor list owner cell to be displayed. The format for the GSM cell ID depends on: The system used (PGSM, EGSM, DCS1800, PCS1900) Whether the seven parameter GSM cell ID format or the four parameter GSM cell ID format has been enabled.

The name of the cell created using the cell_name command is entered in place of the cell_number. When the cell name is entered, it must be placed inside double quotation marks. neighbor_cell_desc GSM cell ID of a neighbor cell. The format for the GSM cell ID depends on: The system used (PGSM, EGSM, DCS1800, PCS1900) Whether the seven parameter GSM cell ID format or the four parameter GSM cell ID format has been enabled.

The name of the cell created using the cell_name command is entered in place of the cell_number. When the cell name is entered, it must be placed inside double quotation marks. test neighbor_cell_desc A test cell can be created to be used for testing. This argument is entered using the string TEST, a space, and a test cell number (1 to 64). An asterisk character (*) is used in place of a test cell number to indicate all test neighbors.

Examples
The examples below are possible displays. If the pbgt_alg_type for a cell is any number between 3 and 7 or the adj_chan_intf_test for a cell equals yes or 1, the system presents additional prompts. Refer to the description of the add_neighbor command for the prompted power budget parameter values.

3-344

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Examples

Example 1
In this example, a cell has no neighbor cells. This example uses the seven parameter format for the cell number. disp_neighbor 5 4 3 2 1 61986 34944 all Where: 5 4 3 2 1 61986 34944 all is: src_cell_desc all neighbor cells

The example below shows the same cell number in the four parameter format: disp_neighbor 543 21 61986 34944 all Where: 543 21 61986 34944 all is: src_cell_desc all neighbor cells

System response
There are no associated neighbor cells

Example 2
In this example, the information describing a neighbor cell is displayed. disp_neighbor 0 0 1 0 1 1 4 0 0 1 0 1 1 1 Where: 0010114 0010111 is: src_cell_desc 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: 00101 1 (0001h) 1 (0001h) N/A PGSM External N/A 1(yes) 1(yes)

68P02901W23-S

3-345 Nov 2009

Examples

Chapter 3: Device/function related commands

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: End of report

60 16 37 15 8 8 -63 -63 63 40 0 (no) 1 8 Normal

Example 3
In this example, the information describing all of the neighbor cells is displayed. The cell name london-north is used in place of the src_cell_desc. disp_neighbor london-north all Where: london-north all is: cell_name all internal neighbor cells

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: 54 3 2 1 633 347 london-south Internal 1 1 0 60 16 37 15 8 9

Adjacent channel interference test enabled: 0 (no)

3-346

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Examples

Power budget algorithm type: Adjacent channel intf detection ho margin: Neighbor congestion handover margin: 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: Power budget algorithm type: Adjacent channel intf detection ho margin: Neighbor congestion handover margin: 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: Power budget algorithm type: Adjacent channel intf detection ho margin:

7 -5 -8 54 3 2 1 633 348 No Name Defined Internal 1 1 0 60 16 37 15 8 9 7 -5 -8 5 4 3 2 1 633 349 N/A External N/A 1 0 100 50 37 15 8 9 7 -5

Adjacent channel interference test enabled: 0 (no)

68P02901W23-S

3-347 Nov 2009

Examples

Chapter 3: Device/function related commands

Example 4
This example displays the information for all test cells. disp_neighbor 5 4 3 2 1 619 394 TEST * Where: 5 4 3 2 1 619 394 TEST * is: src_cell_desc all test cells

System response
MCC MNC LAC CI LOC SYNC SACCH ------N/A N/A GSM CELL ID N/A N/A ----NO YES BCCH ---YES YES BA_ FREQ ---91 101 BCCH BSIC ---N/A N/A

-------------------------------TEST 7 TEST 12

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: 0010111 0010112 is: src_cell_desc 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: 00101 1 (0001h) 2 (0002h)

N/A PGSM Internal 0(no) 1(yes) 1(yes) 60 16

3-348

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Examples

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:

37 15 8 8 -63 -63 63 40 0 (no) 1 8 Normal

Example 6
This example displays the information for all neighbor cells associated with a cell when the Network Controlled cell reselection feature is enabled. disp_neighbor 0 0 1 0 1 1 1 Where: 0010111 is: src_cell_desc

System response
Start of neighbor report: S A C GSM CELL ID MCC MNC 001 01 001 01 001 01 001 01 001 01 001 01 LAC 1 (0001h) 1 (0001h) 1 (0001h) 1 (0001h) 1 (0001h) 1 (0001h) 6 3 CI (0006h) (0003h) LOC SYNC INT NO INT NO INT NO INT NO EXT N/A EXT N/A ---------------------------------- --- ---C H X X X X X X B C C H X X X X X X G P R S X X X X X X FREQ TYPE PGSM PGSM PGSM PGSM EGSM PGSM BCCH FREQ BSIC 75 30 10 90 80 17 16 16 16 16 16 16

-------

------- ---- ----

33 (0021h) 41 (0029h) 11 (000Bh) 90 (005Ah)

End of report

68P02901W23-S

3-349 Nov 2009

Examples

Chapter 3: Device/function related commands

Example 7
This example displays UTRAN cell 4 9 6 2 3 1 1 1 1 as a neighbor of GSM cell 0 0 1 0 1 1 4. disp_neighbor 0 0 1 0 1 1 4 4 9 6 2 3 1 1 1 1 Where: 0010114 496231111 is: src_cell_desc neighbor_cell_desc

System response
Start of neighbor report: UTRAN cell id: UTRAN BCCH Neighbor: UTRAN SACCH Neighbor: FDD-ARFCN: Scrambling code: Diversity enabled: UMTS measurement margin: Neighbor measurement avg period: End of report 496 231 1 (0001h) 1 (0001h) 1 (0001h) Yes Yes 10762 200 0 (no) 3 6

Example 8
This example displays neighbors of GSM cell 0 0 1 0 1 1 4, which has two GSM neighbors, two UTRAN neighbors and two Blind Search neighbors. disp_neighbor 0 0 1 0 1 1 4 Where: 0010114 is: src_cell_desc

System response
Start of neighbor report: S A C UTRAN CELL ID C C B C

3-350

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Examples

MCC MNC 496 231 496 231

LAC 1 (0001h) 1 (0001h)

RNC id 1 (0001h) 2 (0001h)

CI 1 (0001h) 1 (0001h)

H X X

ARFCN SC 10762 200 10762 201

DF 1 0

---------------------------------------------

-----

----- --- --

Blind Search FDD-ARFCN ---------------------10765 10786 S A C GSM CELL ID MCC MNC 001 01 001 01 LAC 1 (0001h) 1 (0001h) CI 106 (006Ah) 103 (0067h) C C R H X X H X X LOC SYNC INT NO INT NO B C G P BCCH TYPE PGSM PGSM FREQ BSIC 75 30 16 16 ------- ---- ---S X X

FREQ -------

------------------------------------ --- ----

End of report

Example 9
{31400} This example displays TD-SCDMA cell 4 9 6 2 3 1 1 1 1 as a neighbor of GSM cell 0 0 1 0 1 1 4. disp_neighbor 0 0 1 0 1 1 4 4 9 6 2 3 1 1 1 1 Where: 0010114 496231111 is: src_cell_desc neighbor_cell_desc

System response
Start of neighbor report: S A C UTRAN CELL ID MCC MNC 496 231 LAC 1 (0001h) RNC id 1 (0001h) CI 1 (0001h) --------------------------------------------End of report C H X B C C H ARFCN 10110 Param 100 TSTD 0 SCTD 0 ----- --- --

-----

68P02901W23-S

3-351 Nov 2009

References

Chapter 3: Device/function related commands

References
Related commands
add_cell on page 3-22 del_cell on page 3-192 add_neighbor on page 3-35 disp_cell on page 3-241 copy_cell on page 3-179 disp_gsm_cells on page 3-314

3-352

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

disp_nsvc

Description
The disp_nsvc command displays the requested NSVCs and their configurations. Security level Supported by OMC-R GUI Command type Prerequisites 1 Yes A (no operator action) None (If GPRS is restricted, the display still shows the headings.)

Format
Syntax
disp_nsvc <NS_VCI> <value>|<pcu_id> <GBL> <value>

Input parameters
NS_VCI Specifies the NSVCI as defined by value. pcu_id {27955A} Specifies the pcu or pcu_0 at which the GBL is defined. GBL Specifies the GBL as defined by value. value Varies according to the option chosen.

68P02901W23-S

3-353 Nov 2009

Examples

Chapter 3: Device/function related commands

Examples
Example 1
The following example displays NSVCI 68: disp_nsvc NS_VCI 68 Where: NS_VCI 68 is: NSVCI NSVCI ID

System response
Start of Report: NS-VCI -----68 68 NSEI 15 16 PCU GBL 0 1 0 0 STATUS ---------Unblocked Unblocked DLCI ----22 22 BC ---0 0 BE ---64 64 CIR ---64 64 ---- ---- ---

End of Report.

Example 2
The following example displays all the NSVCIs associated with GBL 0 at PCU site 0 during SYSGEN: disp_nsvc pcu_0 GBL 0 Where: pcu_0 GBL 0 is: PCU (second equipped) GBL GBL 0

3-354

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

References

System response
Start of Report: Site: PCU_0 NS Access Rate: 64 GBL --0 NS-VCI ------68 27 102 198 10 23 21 78 69 End of Report. 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

References
Related commands
add_nsvc on page 3-48 del_nsvc on page 3-202

68P02901W23-S

3-355 Nov 2009

disp_options

Chapter 3: Device/function related commands

disp_options

Description
The disp_options command displays the unrestricted and restricted optional features. Security level Supported by OMC-R GUI Command type Prerequisites 1 Yes A (no operator actions) None

Format
Syntax
disp_options [all]

Input parameter
all Displays both the unrestricted and restricted options. If this parameter is not entered, only the unrestricted options are displayed.

Examples
Example 1
In this example, only the unrestricted options are displayed. disp_options

System response
The following optional features have unrestricted use: --------------------------------------------------------------------1 2 A & Um Interface - GSM Phase 2 Daisy Chaining

3-356

68P02901W23-S Nov 2009

Chapter 3: Device/function related commands

41 42 43 44 45 46 47 48 49 50 51 52 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70

Dual Band Cells 900/1800 Horizonmicro2 / Horizoncompact2 Enhanced Circuit Error Rate Monitor Network Controlled Cell Reselection Location Services ALM for EGSM carriers 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 Seamless Cell Reselection AMR Enhanced Capacity TCU-A Support for AMR TCU-B Support for AMR Prp Capacity Enhanced General Packet Radio Service GSM Half Rate MMSs at Horizonmacro2 SDCCH Increase Network Assisted Cell Change Quality Of Service GPRS Trace Fast Call Setup Enhanced 2G/3G Handover and Cell Reselection Enhanced Multi-level Precedence and Pre-emption Service Intelligent Multi-layer Resource Management VersaTRAU

The following optional features have restricted use: --------------------------------------------------------------------39 72 BTS Concentration Reserved option

Improved Timeslot Sharing

--------------------------------------------------------------------

3-360

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Examples

Example 3
In this example, the operator performs the disp_options command when only the Enhanced Circuit Error Rate Monitor feature is restricted. disp_options all Where: all is: all options

System response
The following optional features have unrestricted use: --------------------------------------------------------------------1 A & Um Interface - GSM Phase 2 . . . . . . 59 60 61 62 63 64 65 66 67 68 69 70 73 74 Enhanced General Packet Radio Service GSM Half Rate MMSs at Horizonmacro2 SDCCH Increase Network Assisted Cell Change Quality Of Service GPRS Trace Fast Call Setup Enhanced 2G/3G Handover and Cell Reselection Enhanced Multi-level Precedence and Pre-emption Service Intelligent Multi-layer Resource Management VersaTRAU Improved Timeslot Sharing Restricted

The following optional features have restricted use: --------------------------------------------------------------------43 Enhanced Circuit Error Rate Monitor

68P02901W23-S

3-361 Nov 2009

Examples

Chapter 3: Device/function related commands

Example 4
In this example, the operator performs the disp_options command when no features are restricted. disp_options all Where: all is: options

System response
The following optional features have unrestricted use: --------------------------------------------------------------------1 A & Um Interface - GSM Phase 2 . . . . . . 39 BTS Concentration . . . . . . 43 Enhanced Circuit Error Rate Monitor . . . . . . 59 60 61 62 63 64 65 66 67 68 69 70 73 74 Enhanced General Packet Radio Service GSM Half Rate MMSs at Horizonmacro2 SDCCH Increase Network Assisted Cell Change Quality Of Service GPRS Trace Fast Call Setup Enhanced 2G/3G Handover and Cell Reselection Enhanced Multi-level Precedence and Pre-emption Service Intelligent Multi-layer Resource Management VersaTRAU Improved Timeslot Sharing Restricted

3-362

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Examples

Example 5
{26881} This example displays the status of an extended uplink TBF feature when its status is restricted. disp_options all Where: all is: options

System response
The following optional features have unrestricted use: --------------------------------------------------------------------1 2 A & Um Interface - GSM Phase 2 Daisy Chaining

. . . . . . 56 TCU-A support for AMR 57 TCU-B support for AMR 58 Prp Capacity The following optional features have restricted use: --------------------------------------------------------------------46 ALM for EGSM Carriers 60 Extended Uplink TBF

Example 6
{34320G} This example displays the list of unrestricted features at the BSS. The SW enabler for PA bias switch on/off on the CTU2D feature is displayed in this list if the feature is enabled. disp_options

68P02901W23-S

3-363 Nov 2009

Examples

Chapter 3: Device/function related commands

System response
The following optional features have unrestricted use: --------------------------------------------------------------------1 2 . . 59 60 61 Quality Of Service Network Assisted Cell Change SW enabler for PA bias switch on/off on CTU2D A & Um Interface - GSM Phase 2 Daisy Chaining

Example 7
{28938} This example displays the list of unrestricted features at the BSS. disp_options

System response
The following optional features have unrestricted use: --------------------------------------------------------------------1 2 . . 62 63 64 65 . . 74 Incell Support Quality Of Service GPRS Trace VersaTrau Dual Transfer Mode A & Um Interface - GSM Phase 2 Daisy Chaining

Example 8
{25423} This example displays the list of unrestricted features at the BSS. disp_options all

3-364

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Examples

System response
WARNING: The feature option information object will not be downloaded to NE for "Set NE Patch Level" on OMC. So the old version before the operation will be displayed. PCU objects only upgrade and Patch only upgrade do not require BSC reset, so that any feature option changes will not take effect and they are not recommended in case of feature option changes upgrade. UK_Motorola_Swindon_NPI options for BSGSM-1.9.0.0.15-t1 (26/04/07) The following optional features have unrestricted use: --------------------------------------------------------------------1 2 A & Um Interface - GSM Phase 2 Daisy Chaining

Example 9
{23311A} This example verifies if the Extended Range Cell support for GPRS feature is unrestricted at the BSS. disp_options

System response
The following optional features are unrestricted: --------------------------------------------------------------------1 2 . . 56 57 58 59 60 61 TCU-A support for AMR TCU-B support for AMR Prp Capacity Enhanced 2G/3G Handover and Cell Reselection Extended Uplink TBF Extended Range Cell Support for GPRS A & Um Interface - GSM Phase 2 Daisy Chaining

NOTE
The actual output of this command depends on the delivery of other new restricted features.

68P02901W23-S

3-365 Nov 2009

Examples

Chapter 3: Device/function related commands

Example 10
{23311A} This example displays the status of the Extended Range Cell support for the GPRS feature when its status is restricted. disp_options all Where: all is: all options

System response
The following optional features have unrestricted use: --------------------------------------------------------------------1 2 . . 56 57 58 TCU-A support for AMR TCU-B support for AMR Prp Capacity A & Um Interface - GSM Phase 2 Daisy Chaining

The following optional features have restricted use: --------------------------------------------------------------------46 60 61 ALM for EGSM Carriers Extended Uplink TBF Extended Range Cell Support for GPRS

NOTE
The actual output of this command depends on the delivery of other new restricted features.

3-366

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

disp_processor

Description
The disp_processor command displays the status of all processor boards at a specific site or all sites. At InCell sites, this command also displays the related devices and functions associated with the processors. If a GPROC is not detected on the LAN in InCell sites, the Off LAN value displays. At M-Cell and Horizonmacro sites, this command displays transceivers, CPU numbers, DRI IDs, and associated RTFs (if any). The Related Device and Related Function columns are not applicable to M-Cell sites. If a DRI is not detected at the MCU ASIC, the No Sync value displays. Security level Supported by OMC-R GUI Command type Prerequisites 1 Yes A (no operator actions) This command is not allowed while in SYSGEN ON mode or during site initialization.

Format
Syntax
disp_processor <location>

Input parameter
location Indicates the number of the BTS or the BSC where the processors are located. 0 or bsc 1 - 140 {27955A} pcu or pcu_0 all BSC BTS PCU All locations

68P02901W23-S

3-367 Nov 2009

Examples

Chapter 3: Device/function related commands

Examples
Example 1
In this example, the status of all processor boards at all InCell sites displays. disp_processor all Where: all is: all sites

System response
PROCESSOR STATUS INFORMATION FOR LOCATION 0:END OF STATUS REPORT OPER STATES: D:Disabled L:Locked E:Enabled U:Unlocked B:Busy E:Equipped NE:Not Equipped Related CPU# ---0115 0117 0118 011a OPER Processor Name BSP 0 0 CSFP 0 0 GPROC 2 0 (Off LAN) GPROC 1 0 (LCF 0) STATES: D:Disabled L:Locked State Reason B-U D-U D-U B-U NO REASON NO CODE GPROC Not On LAN NO REASON B:Busy E:Equipped NE:Not Equipped Related CPU# Processor Name 1015 BTP 0 0 1019 CSFP 0 0 (Off LAN) State Reason B-U D-U NO REASON NO REASON Device DRI 0 1 DRI 0 0 N/A Related Function RTF 0 0 RTF 0 1 N/A Device N/A N/A N/A SITE 1 0 Related Function N/A N/A N/A N/A ADMIN STATES:

-------------------- ----- ----------------- --------- --------

PROCESSOR STATUS INFORMATION FOR LOCATION 2: E:Enabled U:Unlocked ADMIN STATES:

---- --------------------- ----- ----------------- --------- --------

Example 2
In this example, the status of all processor boards at an M-Cell site displays. disp_processor 1 Where: 1 is: an M-Cell site ID.

3-368

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Examples

System response
PROCESSOR STATUS INFORMATION FOR LOCATION 1: OPER STATES: ADMIN STATES: D:Disabled L:Locked E:Enabled U:Unlocked B:Busy E:Equipped NE: Not Equipped Related CPU# Processor Name 1015 BTP 0 0 2001 DRI 0 0 (RTF 0 0) 2002 DRI 0 1 (RTF 0 2) 2003 DRI 0 2 (RTF 0 3) 2004 DRI 0 3 (RTF 0 1) 2005 DRI 0 4 2006 DRI 0 5 (No Sync) END OF STATUS REPORT State Reason B-U B-U B-U B-U B-U E-L D-L NO REASON COMB Controller NO REASON NO REASON NO REASON NO REASON NO REASON Device N/A N/A N/A N/A N/A N/A N/A Related Function N/A N/A N/A N/A N/A N/A N/A

---------------------------------------------------------------------

Example 3
In this example, the status of the GPRS PCU processor boards are displayed. A single DPROC (PICP) configuration provides support up to 20 TRAU GDS links. disp_processor pcu_0 Where: pcu_0 is: the first equipped PCU.

System response
MMI-RAM 0115 -> disp_proc pcu_0 NC: Not Connected State Reason B:Busy E:Equipped NE:Not Equipped Device 1107 PSP 0 0 1109 PSP 1 0 (NC) 1101 DPROC (PICP) 1 0 B-U D-U B-U NO REASON Bad or Missing Board NO REASON N/A N/A GDS 0 0 GSL 0 0 MSI 0 0 Function N/A N/A N/A N/A N/A Related Related CPU# Processor Name OPER STATES: ADMIN STATES:

PROCESSOR STATUS INFORMATION FOR LOCATION PCU 0: D:Disabled L:Locked E:Enabled U:Unlocked

---- ------------------ ------ ------------------ -------- --------

68P02901W23-S

3-369 Nov 2009

Examples

Chapter 3: Device/function related commands

GSL 2 0 GSL 4 0 GSL 6 0 GSL 10 0 GSL 8 0 MSI 1 0 GBL 0 0 (GDS 5 0) (GDS 10 0) (GDS 11 0) (GDS 12 0) (GDS 14 0) (GDS 16 0) 1102 DPROC (PRP) 2 0 B-U NO REASON MSI 5 0 GDS 2 0 MSI 14 0 GDS 11 0 1103 DPROC (PICP) 3 0 B-U NO REASON MSI 4 0 GBL 2 0 GBL 3 0 (GDS 4 0) (GDS 7 0) (GDS 3 0) 1104 DPROC (PRP) 4 0 B-U NO REASON MSI 6 0 GDS 3 0 MSI 15 0 GDS 12 0 1105 DPROC (PRP) 5 0 B-U NO REASON MSI 7 0 GDS 4 0 MSI 16 0 GDS 13 0 1106 DPROC (PRP) 6 0 B-U NO REASON MSI 8 0 GDS 5 0 MSI 17 0 GDS 14 0 110b DPROC (PICP) 11 0 B-U NO REASON MSI 2 0 GDS 1 0 GSL 1 0 GSL 3 0 GSL 5 0 GSL 7 0 GSL 9 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

3-370

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Examples

GSL 11 0 MSI 3 0 GBL 1 0 (GDS 8 0) (GDS 2 0) (GDS 6 0) 110c DPROC (PRP) 12 0 B-U NO REASON MSI 9 0 GDS 6 0 MSI 18 0 GDS 15 0 110d DPROC (PRP) 13 0 B-U NO REASON MSI 10 0 GDS 7 0 MSI 19 0 GDS 16 0 110e DPROC (PRP) 14 0 B-U NO REASON MSI 11 0 GDS 8 0 MSI 20 0 GDS 17 0 110f DPROC (PRP) 15 0 B-U NO REASON MSI 12 0 GDS 9 0 MSI 21 0 GDS 18 0 1110 DPROC (PRP) 16 0 B-U NO REASON MSI 13 0 GDS 10 0 MSI 22 0 GDS 19 0 END OF STATUS REPORT

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

Example 4
{28351} In this example, the BSC modifies the disp_processor command to support a PXP DPROC. disp_processor pcu Where: pcu is: the equipped PCU.

68P02901W23-S

3-371 Nov 2009

Examples

Chapter 3: Device/function related commands

System response
PROCESSOR STATUS INFORMATION FOR LOCATION PCU 0: OPER NC: STATES: D:Disabled L:Locked E:Enabled U:Unlocked B:Busy E:Equipped NE:Not Equipped Related CPU# Processor Name 1107 PSP 0 0 1109 PSP 1 0 (NC) 1101 DPROC (PICP) 1 0 State Reason B-U D-U B-U NO REASON Bad or Missing Board NO REASON Device N/A N/A MSI 1 0 GDS 1 0 GSL 0 1 1102 DPROC (PICP) 2 0 1103 DPROC (PXP) 3 0 B-U B-U NO REASON No GDS in service MSI 2 0 Unknown device found MSI 3 0 GBL 0 0 GDS 3 0 GSL 0 3 1104 DPROC (PRP) 4 0 B-U NO REASON MSI 4 0 GDS 4 0 1105 DPROC (PXP) 5 0 B-U NO REASON MSI 5 0 Unknown device found N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A Related Function N/A N/A N/A ADMIN STATES:

Not Connected

---- ---------------------- ----- ------------------------- ----- --------

Unknown device found

NOTE
CA queries pCA. PPROC is displayed only when U-DPROC2 is configured as PXP . roglin command is used for querying when the board is configured as PXP .

3-372

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

disp_relay_contact

Description
The disp_relay_contact command displays the relay state (open or closed circuit) for an EAS device when the device is Busy-Unlocked. The relays are in the deactivated state, as defined during equip EAS, when the EAS is not Busy-Unlocked. Security level Supported by OMC-R GUI Command type Prerequisites 1 Yes A (no operator actions) The EAS device must be equipped and the EAS device parameters established using the equip eas command. Seeequip on page 3-403.

Format
Syntax
disp_relay_contact <location> <device_id>

Input parameters
location Specifies the location of the device: 0 or bsc 1 - 140 device_id Specifies the device ID of the specific PIX card associated with an EAS device. 0 to 7 0 to 15 InCell sites M-Cell and Horizonmacro sites BSC BTS

68P02901W23-S

3-373 Nov 2009

Example

Chapter 3: Device/function related commands

Example
This example displays the relay contacts for all EAS devices. disp_relay_contact

System response
Relay 1: Closed

Relay 2: Open Relay 3: Open Relay 4: Closed

References
Related command
equip on page 3-403

3-374

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

disp_rtf_channel

Description
The disp_rtf_channel command displays the status of all timeslots or a single timeslot on a carrier. The display output indicates whether the RTF is equipped for GPRS and EGPRS, and if capable of supporting EGPRS If either AMR or GSM Half Rate channel mode is enabled at both the BSS level and the Cell level for a given cell, the BSS user interface displays generic traffic channels as TCH/G in the output when the disp_rtf_channel command is executed for a half rate RTF in that cell. Security level Supported by OMC-R GUI Command type Prerequisites 1 No A (no operator actions) This command is not allowed while in SYSGEN ON mode.

Format
Syntax
disp_rtf_channel <location> <rtf_id_1> <rtf_id_2> [<timeslot_number>]

Input parameter
location Specifies the location: 0 or bsc 1 - 140 rtf_id_1 The first identifier of the RTF. The range of values is 0 to 5. rtf_id_2 The second identifier of the RTF. The range of values is 0 to 11. timeslot_number Specifies the timeslot number. The range of values is 0 to 7. When an Extended Range timeslot number is displayed, the word Extended is appended to the timeslot number. BSC BTS

68P02901W23-S

3-375 Nov 2009

Examples

Chapter 3: Device/function related commands

Carrier states
The carrier states that can be displayed include: ACTIVE - the timeslot is active. IDLE - the timeslot is idle. INTRANS - the timeslot is in transition: from active to idle, or from idle to active, or from unavailable to active. OOS - the timeslot is out of service. Due to EGPRS PDs on double density CTU2 carrier A, the paired timeslots on carrier B is blanked out and displayed as OOS. UNAVAILABLE (HOPPING) - the timeslot is unavailable due to hopping reconfiguration. UNAVAILABLE (IBAND) - the timeslot is unavailable due to a poor interference band (Iband). UNAVAILABLE (OPERATOR) - the operator has subequipped an RTF. UNAVAILABLE (TERRESTRIAL) - the carrier is unavailable due to a problem with a terrestrial link. N/A - for a PDTCH, the timeslot is not configured for GPRS.

The GPRS types that can be displayed include: SWITCHABLE - the GPRS timeslot is switchable. RESERVED - the GPRS timeslot is reserved.

Examples
Example 1
This example displays the status of RTF 0 2 at Site 1 when both EGPRS and GPRS are restricted. disp_rtf_channel 1 0 2 Where: 1 0 2 is: location rtf_id_1 rtf_id_2

3-376

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Examples

System response
Start of report for RTF 0 2 at location 1:

TIMESLOT 0 (TCH/F) 1 (TCH/F) 2 (TCH/F) 3 (TCH/F) 4 (TCH/F) 5 (TCH/F) 6 (TCH/F) 7 (TCH/F)

SUB-CHAN 0 0 0 0 0 0 0 0

STATE ACTIVE ACTIVE ACTIVE ACTIVE ACTIVE ACTIVE ACTIVE ACTIVE

-------------------------------------------------------

Example 2
This example displays the status of RTF 0 0 at Site 1 when the RTF is configured for EGPRS and is assigned to a DRI capable of supporting EGPRS (that is, a single density CTU2). disp_rtf_channel 1 0 0 Where: 1 0 0 is: location rtf_id_1 rtf_id_2

System response
Start of report for RTF 0 0 at location 1:

Packet Radio Capabilities: 64 K RTF currently capable of supporting EGPRS?: YES TIMESLOT 0 (BCCH) 1 (TCH/F) GPRS TYPE N/A N/A SUB-CHAN 0 0 STATE ACTIVE ACTIVE ----------------------------------------------------------------

68P02901W23-S

3-377 Nov 2009

Examples

Chapter 3: Device/function related commands

2 (TCH/F) 3 (64 K PDTCH) 4 (64 K PDTCH) 5 (64 K PDTCH) 6 (64 K PDTCH) 7 (64 K PDTCH)

N/A Switchable Reserved Reserved Reserved Reserved

0 0 0 0 0 0

ACTIVE N/A N/A N/A N/A N/A

Example 3
This example displays the carrier states of RTF 1 0, timeslot 5 (a generic traffic channel) at site 1 with half_rate_enabled element set to 1 (enabled). disp_rtf_channel 1 1 0 5 Where: 1 1 0 5 is: location rtf_id_1 rtf_id_2 timeslot

System response
TIMESLOT SUB-CHAN STATE.

------------------------------------5 (TCH/G) End of Report 0 IDLE

Example 4
This example displays the timeslot status of Carrier B when Carrier A has three EGPRS PDs on timeslots 5 to 7. disp_rtf_channel 1 0 2 Where: 1 0 2 5 is: location rtf_id_1 rtf_id_2 timeslot

3-378

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Examples

System Response
Start of report for RTF 0 2 at location 1 Packet Radio Capabilities: None RTF currently capable of supporting EGPRS? No TIMESLOT GPRS TYPE SUB-CHAN STATE 0 (TCH/F) N/A 0 ACTIVE 1 (TCH/F) N/A 0 ACTIVE 2 (TCH/F) N/A 0 ACTIVE 3 (TCH/F) N/A 0 ACTIVE 4 (TCH/F) N/A 0 ACTIVE 5 (TCH/F) N/A 0 OOS 6 (TCH/F) N/A 0 OOS 7 (TCH/F) N/A 0 OOS

Example 5
{23311A} This example displays the carrier status of all the timeslots for an RTF channel with extended timeslots pair (2,3), configured as extended PDCHs. disp_rtf_channel 1 0 0 Where: 1 0 0 is: location rtf_id_1 rtf_id_2

68P02901W23-S

3-379 Nov 2009

Examples

Chapter 3: Device/function related commands

System response
Start of report for RTF 0 0 at location 1: Packet Radio Capabilities: 64k RTF currently capable of supporting EGPRS?: YES TIMESLOT 0 (TCH/F) 1 (Extended) 2 (64k PDTCH) 3 (Extended) 4 (64k PDTCH) 5 (64k PDTCH) 6 (64k PDTCH) 7 (64k PDTCH) Reserved Reserved Reserved Reserved 0 0 0 0 N/A N/A N/A N/A Reserved 0 N/A GPRS TYPE N/A SUB-CHAN 0 STATE ACTIVE ----------------------------------------------------------------

3-380

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

disp_rtf_path

Description
The disp_rtf_path command displays all PATH devices to which the RTF is assigned, including the status of the RTF on that PATH. The status of the RTF is shown as Connected or Redundant. The system shows whether a site supports dynamic allocation. The PATH status includes the designation of SHARED in addition to the CONNECTED and REDUNDANT status. All PATHs which could be used to carry the RTF to the BSC are displayed. For spoke and daisy chain configurations, no redundant PATHs exist. Security level Supported by OMC-R GUI Command type Prerequisites 1 Yes A (no operator actions) This command is available only on RTF functions that are equipped on a remote BTS.

Format
Syntax
disp_rtf_path <location> <rtf_id_1> <rtf_id_2>

Input parameters
location Specifies the number of the BTS where the RTF is located. The range of values is 0 to 140. rtf_id_1 Specifies the 1st RTF identifier. The range of values is 0 to 5. rtf_id_2 Specifies the 2nd RTF identifier. The range of values is 0 to 11.

68P02901W23-S

3-381 Nov 2009

Example

Chapter 3: Device/function related commands

Example
This example displays all the PATH devices assigned to RTF 0 0 at BTS 12. disp_rtf_path 12 0 0 Where: 12 0 0 is: location rtf_id_1 rtf_id_2

System response
Start of Report:

SITE ID:

1st RTF Identifier: 0 2nd RTF Identifier: 0 PATH 12 0 0 Status: CONNECTED End of Report Busy Unlocked

References
Related commands
add_rtf_path on page 3-50 del_rtf_path on page 3-204 chg_rtf_freq on page 3-144 copy_path on page 3-187

3-382

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

disp_severity

Description
Use the disp_severity command to view the current severity level for device alarms and non-reconfiguration alarms. Security level Supported by OMC-R GUI Command type Prerequisites 1 No A (no operator actions) None

Format
Syntax
disp_severity <device_name> <alarm_code>

Input parameters
device_name The name of the device, such as GPROC, that is being modified. alarm_code The decimal number or range that identifies the alarm code or codes for the device that is being modified. The alarm code is defined by all valid numeric values in the range 0 to 254. Refer to Alarm devices on page 3-20 for the ranges of alarm codes for each device. Refer to the Maintenance Information: Alarm Handling at the OMC-R (68P02901W26) manual for a list of all alarms and the corresponding alarm codes for each device.

68P02901W23-S

3-383 Nov 2009

Example

Chapter 3: Device/function related commands

Example
This example shows how to display the severity of GPROC alarm code 8. disp_severity gproc 8 Where: gproc 8 is: device_name alarm_code

System response
GPROC Alarm code 8 severity: Investigate

3-384

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

disp_site

Description
The disp_site command displays the site, BSC, or BTS, with which the operator is interacting. Security level Supported by OMC-R GUI Command type Prerequisites 1 No A (no operator actions) None

Format
Syntax
disp_site

Input parameters
There are no input parameters associated with this command.

Example
This example displays the current site. disp_site

System response
Current site number is 6

References
Related command
equip on page 3-403.

68P02901W23-S

3-385 Nov 2009

disp_throttle

Chapter 3: Device/function related commands

disp_throttle

Description
The disp_throttle command displays the throttle period for an intermittent alarm. To display the throttle time period for all intermittent alarms, the command is executed with no input parameters. Security level Supported by OMC-R GUI Command type Prerequisites 1 Yes A (no operator actions) None

Format
Syntax
disp_throttle [<device_name> <alarm_code>]

Input parameters
device_name Device name that uniquely identifies the device. alarm_code Identifies the alarm to be throttled. The range of values for the alarm_code is 0 to 254.

Examples
Example 1
This example displays the throttle period for device DRI, alarm code 66. disp_throttle dri 66 Where: dri 66 is: device_name alarm_code

3-386

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

References

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 .... 1 10 Bad Host Message Alarm Code -----0 1 4 Throttle Time --------15 1 1 Alarm Description ------------------------------------Synch Loss Daily Threshold Exceeded Synch Loss Hourly Threshold Exceeded Remote Alarm Daily Threshold Exceeded

References
Related command
chg_throttle on page 3-156.

68P02901W23-S

3-387 Nov 2009

disp_time

Chapter 3: Device/function related commands

disp_time

Description
The disp_time command displays the current real time of the system. The format of the real time is: Day of the week Month Day of the month Hour Minutes Seconds Year 1 No A (no operator actions) None

Security level Supported by OMC-R GUI Command type Prerequisites

Format
Syntax
disp_time

Input parameters
There are no input parameters associated with this command.

Example
In this example, the system time is displayed. disp_time

3-388

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

References

System response
Fri Nov 12 14:13:48 2002

References
Related commands
chg_time on page 3-158 time_stamp on page 3-548

68P02901W23-S

3-389 Nov 2009

disp_trace_call

Chapter 3: Device/function related commands

disp_trace_call

Description
The disp_trace_cell command displays the mode, value, and trace data currently enabled in the BSS and the destination of the trace report. Security level Supported by OMC-R GUI Command type Prerequisites 1 No A (no operator actions) This command is not allowed when in SYSGEN ON mode.

Format
Syntax
disp_trace_call [reference_number]

Input parameter
reference_number A number that identifies a particular trace reference. The number can range from 0 to 4294967295. Using a reference number is optional. If the reference number is not used, the system displays all call traces.

Examples
Example 1
The following example displays the Call/GPRS Trace criteria that are currently at the BSS. disp_trace_call

System response
Start of Trace Report Trace Reference: 1h

3-390

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Examples

Scope: Trigger Event: Trace Data: GPRS trace Data: Trigger Enabled Time: Data during handover only: Mode Total calls to be traced: Trace beyond scope: Destination of Trace data: Triggering enabled: Trace Reference: Scope: Trigger Event: GPRS Trace Data: Data during handover only: Mode Trigger Enabled Time: Total calls to be traced: Trace beyond scope: Destination of Trace data: Triggering enabled: Total mobiles currently traced Trace Reference ----------------1h 67A67h Count ----8 5

0 0 1 0 1 1(0001h) 4(0004h) combined_all (All Call Trace and GPRS Trace) Basic, DTAP, Abis Basic, LLC, BSSGP Not Specified No IMSI=003456789012345 20 No OMC No 67A67h BSS wide gprs (GPRS Trace) Basic, LLC, BSSGP No TLLI=c0010329h Not Specified 20 No OMC No

Total calls currently traced Trace Reference ----------------1h Automatic Flow Control: Count ----3 Not Halted for this BSS.

Automatic Flow Control: Activated by BSS.

68P02901W23-S

3-391 Nov 2009

Examples

Chapter 3: Device/function related commands

Automatic Flow Control:

De-activated by OMC.

Example 2
The following is an example of the specified call trace instance (trace reference 067A67h) currently active in the BSS. disp_trace_call 067A67h Where: 067A67h is: reference_number

System response
Start of Trace Report Trace Reference: Scope: Trigger Event: GPRS Trace Data: Interval (x480msec): Data during handover only: Mode Trigger Enabled time Total calls to be traced: Trace beyond scope: Destination of Trace data: Trigger enabled: Total mobiles currently traced Trace Reference --------------067A67h Count ----5 067A67h BSS wide gprs (GPRS Trace) Basic, LLC, BSSGP, PMRs 20 No NthGPRSmobile=5 Not specified 20 No OMC No

Total calls currently being traced Trace Reference --------------Automatic Flow Control: Automatic Flow Control: Automatic Flow Control: Count ----Not Halted for this BSS. Activated by BSS. De-activated by OMC.

3-392

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

References

References
Related commands
trace_call on page 3-550 trace_stop on page 3-564

68P02901W23-S

3-393 Nov 2009

disp_traffic

Chapter 3: Device/function related commands

disp_traffic

Description
The disp_traffic command displays all RSL and RTFs equipped to a particular PATH at a BTS or all GSLs equipped to a GDS at a PCU. Security level Supported by OMC-R GUI Command type Prerequisites 1 Yes A (no operator actions) The GPRS feature must be unrestricted to display PCU data.

Format
Syntax
disp_traffic <location> <unique_PATH_identifier>

Input parameters
location Specifies the equipment location: {27955A} pcu or pcu_0 1 - 140 unique_PATH_identifier Specifies the unique PATH to a particular BTS. The range of values is 0 to 11. PCU BTS

3-394

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Examples

Examples
Example 1
This example displays the RSL devices and RTF functions equipped on unique PATH 3 at site 1. disp_traffic 1 3 Where: 1 3 is: location unique_PATH_identifier

System response
Start of Report:

SITE ID: Unique PATH ID: RSL 1 0 0 RTF 0 0 0 RTF 0 1 0 RTF 0 2 0 End of Report

1 3

Example 2
This example displays the PCU data. disp_traffic pcu 0 Where: pcu 0 is: location unique_PATH_identifier

System response
Start of Report: SITE ID: Unique GDS ID: GPRS End of Report PCU 0

68P02901W23-S

3-395 Nov 2009

68P02901W23-S

3-401 Nov 2009

References

Chapter 3: Device/function related commands

System response:
X.25 Packet Size: X.25 Window Size: 128 2

References
Related command
chg_x25config on page 3-166.

3-402

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

equip

Description
The equip command adds devices and functions to the Fault Management portion of the CM database. Since each device and function has specific parameters, there is a corresponding set of prompts. Each device and function also has specific restrictions for equipage. Details of the command prompts and restrictions for equipping the devices and functions are provided in Chapter 2 Equipping the CM database, which also includes charts showing equipage hierarchy. Some devices and functions require the system to be in the SYSGEN ON mode. To enter this mode, enter the sysgen_mode on command. To exit this mode, use the sysgen_mode off command. Some devices require the site to be locked. To lock the site, enter the lock command. To unlock the site, enter the unlock command. If a device or function parameter is optional, there is no need to enter data. Press the ENTER key at the prompt. The equip command can be exited at any time by entering done in response to any prompt.

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

Security level Supported by OMC-R GUI Command type Prerequisites

4 Yes B (operator actions required) Some devices and functions can be equipped only after other devices have been equipped. To equip or modify some devices, the system must be in the SYSGEN ON mode. Some devices require the site to be locked. To equip a device or function with a frequency, it must be first set as allowable with the freq_types_allowed command. The LMTL can be equipped only if the Location Services support feature is unrestricted and the BSS can support a BSS-based SMLC. GPRS devices can be equipped only if the GPRS feature is unrestricted. {28337} HSP MTL can be equipped only when the increased network capacity feature is enabled.

68P02901W23-S

3-403 Nov 2009

Format

Chapter 3: Device/function related commands

Operator actions

Refer to the instructions included with each device or function for specific actions to be taken when using this command (see Chapter 2 Equipping the CM database).

Format
Syntax
equip <location> <dev/func_name>

Input parameters
location Specifies the location of the device: 0 or bsc 1 - 140 {27955A} pcu or pcu_0 BSC BTS PCU

NOTE
A BSC of type 1 or 2 must equip remote sites with an LCF.

dev/func_name Identifies the device or function being equipped. The following devices can be equipped with this command: ABSS CAGE DPROC GDS MTL RSL AXCDR CBL DRI GPROC OML RXCDR BSP CIC DYNET GSL OPL SITE BSS COMB EAS KSW PATH XBL BTP CSFP GBL LMTL PCU CAB DHP GCLK MSI PSP

3-404

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Examples

The following functions can be equipped with this command: LCF OMF RTF

NOTE
The system responds with a series of command prompts for further input which is dependent on the particular device/function being equipped (see Chapter 2 Equipping the CM database for equipage rules/conditions and system command prompts).

Examples
Example 1
In this example, a second CAGE is being equipped at the BSC using expansion: equip bsc cage Where: bsc cage is: location. device being equipped.

System response
Enter the device identification for the cage: 1 Enter the KSW pair that manages the cage: 1 Enter the KSWX connecting cage to KSW for TDM 0: Enter KSWX connecting cage to KSW for TDM 1: Enter the cabinet to which the cage belongs: 1 Is an IAS connected?: Y COMMAND ACCEPTED

Example 2
In this example, a path with two links is equipped to site 2. All the prompts that define the path are included in this example. equip 0 path Where: 0 path is: location. the device being equipped.

68P02901W23-S

3-405 Nov 2009

Examples

Chapter 3: Device/function related commands

System response
Enter the terminating SITE id: 2 Enter the Unique PATH identifier: 0 Enter the BSC MSI identifier: 0 0 Enter the SITE identifier: 1 Enter the upstream MSI identifier: 2 0 Enter the downstream MSI identifier: 2 1 Enter the SITE identifier: 2 Enter the upstream MSI identifier: 2 1 COMMAND ACCEPTED

Example 3
This example equips a 64 K RTF at BTS site 2 with a warning that not enough GDS resources are available to handle PDTCHs. equip 2 rtf Where: 2 is: location

System response
Enter capacity of carrier: FULL Enter type of carrier: NON_BCCH Enter the 1st and 2nd RTF id: 0 5 Enter primary Unique PATH id: 1 Enter the optional secondary Unique PATH id: Enter the GSM cell to which this carrier is assigned: 0 0 1 0 1 1 3 Enter carrier absolute radio freq. channel: 620 Enter the 8 carrier frequency hopping indicators: 255 255 255 255 255 255 255 255 Enter the 8 carrier training sequence codes: 0 0 0 0 0 0 0 0 Enter cell zone: 0 Enter the number of extended range timeslots allowed: 0 Enter SDCCH load: 0 Enter channel allocation priority: 0 Enter the packet radio capability (NONE/16 K/32 K/64 K)?: 64K Enter the value for AMR half-rate enabled = 0 COMMAND ACCEPTED: WARNING: Insufficient GDS resources available for all PDTCHs on the PCU.

3-406

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Examples

Example 4
In this example, a PCU site 0 is equipped at the BSC: equip 0 PCU Where: 0 is: location

System response
Enter the PCU identifier (default 0): 0 Enter the PCU IP address: 127.0.0.2 Enter the PCU subnet mask: 255.255.255.0 Enter the PCU router IP address: 127.0.0.1 Enter the NSEI value: 5047 COMMAND ACCEPTED The COMMAND ACCEPTED message is replaced by an error message if a PCU with the same ID exists at the BSC, or the IP address entered is already assigned to another PCU.

Example 5
{27955A} This example attempts to equip pcu_0 as the pcu identifier. equip 0 PCU Where: 0 is: location

System response
Enter the PCU Identifier: 1 Enter the PCU base GDS IP Address: 10.15.255.222 Enter the PCU GDS Subnet Mask: 255.255.255.248 Enter the PCU GDS Router IP Address: 25.134.15.33 Enter the WebMMI IP address: 127.0.0.2 Enter the WebMMI subnet mask: 255.255.255.0 Enter the WebMMI router IP address: 127.0.0.1 Enter the NSEI value: 5047 COMMAND REJECTED ERROR: Range Error, parameter number: 1.

68P02901W23-S

3-407 Nov 2009

Examples

Chapter 3: Device/function related commands

Example 6
{28337} In this example, a 64 k MTL is equipped successfully when the increased network capacity feature is unrestricted. equip 0 mtl Where: 0 mtl is: location. device being equipped.

System response
Enter the device identification for this MTL: 4 Enter the number of DS0 channels for this MTL: 1 Enter the first MMS description for this device: 10 Enter the second MMS description for this device: 0 Enter start timeslot on MMS where this device appears: 15 COMMAND ACCEPTED

Example 7
{28337} This example equips an LCF which manages an HSP MTL. equip 0 lcf Where: 0 lcf is: location. device being equipped.

System response
Enter the function identification for the LCF: 1 Enter the number of DS0 channels the LCF can manage as MTLs: 31 WARNING: HSP LCF equipage may trigger GPROC preemption. Are you sure (y=yes,n=no)? y COMMAND ACCEPTED

3-408

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Examples

Example 8
{28337} This example attempts to equip an LCF when the gproc_slot does not equal 32. equip 0 lcf Where: 0 lcf is: location. device being equipped.

Example 9
{26740} In this example, the PCU is equipped when the increase in the throughput of PRP is restricted. equip 0 pcu Where: 0 pcu is: location. device being equipped.

System response
Enter the PCU Identifier: 0 Enter the PCU base GDS IP Address: 10.15.255.222 Enter the PCU GDS Subnet Mask: 255.255.255.0 Enter the WebMMI IP address: 127.0.0.2 Enter the WebMMI subnet mask: equip Enter the WebMMI router IP address: 127.0.0.1 Enter the NSEI value:equip COMMAND ACCEPTED

68P02901W23-S

3-409 Nov 2009

Examples

Chapter 3: Device/function related commands

Example 10
{28351} In this example, two MSI devices of type E1_PMC is supported by the BSC on PXP DPROC. equip pcu msi Where: pcu msi is: device being equipped. dev_name

System response
Enter the MSI Identifier: 1 Enter the DPROC id: 5 Enter the DPROC socket: 1 COMMAND ACCEPTED

Example 11
{26740} In this example, a PSI device is equipped at the BSC.

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

equip bsc psi Where: bsc psi is: device being equipped. dev_name

System response
Enter the PSI Identifier: 1 Enter the cage number: 0 Enter the slot number: 6 Enter the number of TDM timeslot blocks: 3 Enter the maximum number of GSLs on this PSI: 5 Enter the base IP address for the PSI: 10.0.16.4 Enter the subnet mask: 255.255.255.0 COMMAND ACCEPTED 3-410 68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Examples

Example 12
{26740} The BSC rejects the equip command for a PSI device if the slot number is not 6, 7, 12 or 13.

NOTE
The BSC rejects the equip command for a PSI device if it is unable to allocate the specified number of timeslot blocks on the TDM highway.

equip bsc psi Where: bsc psi is: device being equipped. dev_name

System response
Enter the PSI Identifier: 3 Enter the cage number: 0 Enter the slot number: 8 Enter the number of TDM timeslot blocks: 3 Enter the maximum number of GSLs on this PSI: 5 Enter the base IP address for the PSI: 10.3.16.4 Enter the subnet mask: 255.255.255.0 COMMAND REJECTED: Received a request for an invalid slot

Example 13
{28000} In this example, pcu is equipped when Increase PRP Throughput feature is unrestricted. equip 0 pcu Where: 0 pcu is: device being equipped. dev_name

68P02901W23-S

3-411 Nov 2009

Examples

Chapter 3: Device/function related commands

System response
Enter the PCU Identifier: 0 Enter the PCU base GDS IP Address: 10.15.255.222 Enter the PCU GDS Subnet Mask: 255.255.255.248 Enter the PCU GDS Router IP Address: 10.15.255.221 Enter the WebMMI IP address: 127.0.0.2 Enter the WebMMI subnet mask: 255.255.255.0 Enter the WebMMI router IP address: 127.0.0.1 Enter the NSEI value: 5047 Enter the PRP Fanout Mode: 1 COMMAND ACCEPTED

Example 14
{26481} In this example, the operator attempts to enable the opto alarm (out of range 1-6) for EAS equipped to H2micro cabinet 0 0 0. equip 8 eas Where: 8 eas is: device being equipped. dev_name

System response
Enter the first device ID (Cabinet ID) for the EAS: 0 Enter the relay wiring of the 3 relays (0 - N/O, 1 - N/C): 1 1 1 Enter the no alarm condition for the 6 optos(0 - closed, 1 - open): 1 1 0 0 1 1 0 0 1 ERROR: Extra Parameters, received: 9.

3-412

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Examples

Example 15
{26481} This example equips a H2micro extension cabinet to site 12, that is, HORIZONMACRO master cab. equip 12 CAB Where: 12 CAB is: device being equipped. dev_name

System response
Enter the CABINET identifier: 1 Enter the cabinet type: HORIZON2MICRO_EXT Enter the frequency type: DCS1800 COMMAND ACCEPTED

Example 16
{27236} This example equips a DRI in double density capacity mode to site 7, resulting in DRI devices 0 0 0 and 0 1 0 being equipped when CTU2-D capacity feature is enabled. equip 7 DRI Where: 7 dri is: device being equipped. dev_name

68P02901W23-S

3-413 Nov 2009

Examples

Chapter 3: Device/function related commands

System response
Enter the 1st and 2nd DRI id: 0 0 Enter the density of this DRI: CAPACITY Enter the 2nd DRI id of the associated DRI: 1 Enter the cabinet type identifier: 0 Enter the type of connection to the BTP: direct Enter the port to which the TCU is connected: 0 Enter the 1st and 2nd RTF id: Enter the GSM cell ID where the DRI appears: 0 0 1 0 1 1 1 Enter the antenna select number for this cell: 0 Enter diversity flag for this DRI: 0 Enter the fm cell type: 0 COMMAND ACCEPTED

Example 17
{30828} This example equips a DRI in double density capacity mode to site 7, resulting in DRI devices 0 0 0 and 0 1 0 equipage being rejected when the CTU2-D capacity feature is restricted. equip 7 DRI Where: 7 dri is: device being equipped. dev_name

3-414

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

References

Example 18
{23311A} This example attempts to set ext_pdchs when the Extended Range Cell for Data feature is restricted (ercgprsOpt = 0), ext_pdchs is not prompted, and BSC is internally set ext_pdchs = 0. equip 0 RTF Where: 0 RTF is: device being equipped. dev_name.

System response
Enter type of carrier: NON_BCCH Enter the 1st and 2nd RTF identifier: 5 11 Enter the GSM cell assigned to this carrier: 0 0 1 0 1 1 18 Enter carrier absolute radio freq. channel: 70 Enter the 8 carrier frequency hopping indicators: 0 0 0 0 0 0 0 0 Enter the 8 carrier training sequence codes: 0 0 0 0 0 0 0 0 Enter KSW pair that manages this carrier: 0 Enter the number of extended range timeslots allowed: 2 Enter SDCCH load: 0 Enter the packet radio capability: 32k Enter the value for AMR half-rate enabled = 1 Is 8kbps TRAU allowed (yes/no)?: yes COMMAND ACCEPTED

References
Related commands
disp_equipment on page 3-283 modify_value on page 3-456 state on page 3-515 freq_types_allowed on page 3-417 reassign on page 3-477 unequip on page 3-570 lock_device on page 3-429 shutdown_device on page 3-502 unlock_device on page 3-581

68P02901W23-S

3-415 Nov 2009

Related information

Chapter 3: Device/function related commands

Related information
The order and conditions in which devices and functions can be equipped, and the corresponding command prompts that are generated during the execution of the equip command are provided in Chapter 2 Equipping the CM database.

3-416

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

freq_types_allowed

Description
The freq_types_allowed command specifies the following: The frequency types available to the BSS (PGSM, EGSM, DCS1800, PCS1900 systems). The PCS1900 frequency blocks available at the BSS (PCS1900 systems only).

The following are valid frequency types: PGSM systems (default value) EGSM systems DCS1800 systems PCS1900 systems Security level Supported by OMC-R GUI Command type Prerequisites Dependencies Operator actions Channels 1 to 124 Channels 0, 1 to 124, 975 to 1023 Channels 512 to 885 Channels 512 to 810 4 Yes B (operator actions required) None The frequency types of extended neighbor cells must be allowed at the BSS. All existing types and blocks must be entered when specifying a frequency type or frequency block (unless all types or blocks are specified). If the system is in SYSGEN OFF mode, the system does not allow modifying the frequency types if an existing frequency type or frequency block is not entered. If the system is in SYSGEN ON mode, and an existing frequency block or type is not entered, the system deletes that frequency block or type from the list of allowed types.

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

68P02901W23-S

3-417 Nov 2009

Format

Chapter 3: Device/function related commands

Format
Syntax
freq_types_allowed [<types>]

Input parameter
types Specifies the frequency types available to the BSS. The value is entered as: a text string, a number, or a list of text strings and numbers. The string all specifies all frequency types. Possible values and text strings are: Numeric value 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 Text string pgsm egsm pgsm,egsm dcs1800 pgsm, dcs1800 egsm, dcs1800 pgsm, egsm, dcs1800 pcs1900 pgsm, pcs1900 egsm, pcs1900 pgsm, egsm, pcs1900 dcs1800, pcs1900 pgsm, dcs1800, pcs1900 egsm, dcs1800, pcs1900 pgsm, egsm, dcs1800, pcs1900

More than one frequency type can be entered. See Example 2, below. If no values are entered, the command displays the frequency types that are currently available.

3-418

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Examples

Prompted parameters
The prompt for PCS 1900 frequency blocks appear only if all, pcs1900 or the number 8 is specified in the command line. If the prompt appears, enter at least one frequency block. Possible values are: a b c d e f all Frequency block A Frequency block B Frequency block C Frequency block D Frequency block E Frequency block F Channels 512 to 585 Channels 612 to 685 Channels 737 to 810 Channels 587 to 610 Channels 687 to 710 Channels 712 to 735

all PCS1900 frequency blocks allowed in the BSS

See Example 3, below, for an example of the prompts.

Examples
Example 1
This example displays the allowed frequency types. freq_types_allowed

System response:
Frequency Blocks Allowed: PGSM (1 - 124)

Example 2
This example modifies the frequency types allowed to include PGSM when DCS 1800 is already allowed. freq_types_allowed pgsm,dcs1800 Where: pgsm dcs1800 is: frequency type for PGSM frequencies. frequency type for DCS1800 frequencies.

68P02901W23-S

3-419 Nov 2009

Examples

Chapter 3: Device/function related commands

System response:
COMMAND ACCEPTED

Example 3
This example modifies the allowed frequency blocks to include A and D when blocks C and F are already allowed. freq_types_allowed pcs1900 Where: 8 is: frequency type for PCS1900 frequencies.

System response:
Enter PCS 1900 frequency blocks: a,c,d,f COMMAND ACCEPTED

3-420

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

gclk_cal_mode

Description
The gclk_cal_mode command specifies the synchronization function and MCU (Main Control Unit) software that a calibration is to be performed. A prompt displays describing the results of entering the command. The prompt must be acknowledged with a y (yes) to begin the calibration. No call processing can occur involving this MCU during the calibration mode. The MCU resets when the calibration is complete. Security level Supported by OMC-R GUI Command type Prerequisites 2 No A (no operator actions) This command is not allowed when in the SYSGEN ON mode. This command can be executed only at M-Cell sites.

Format
Syntax
gclk_cal_mode

Input parameters
There are no input parameters associated with this command.

Example
In this example, the GCLK calibration at the local site is started: gclk_cal_mode

68P02901W23-S

3-421 Nov 2009

Example

Chapter 3: Device/function related commands

System response
Site <local site number> starting GCLK CALIBRATION MODE. single MCU site, the site will be down until calibration is complete. If this is a two MCU site, the site will be down until the redundant MCU takes over. If this a Are you sure (y=yes,n=no)? y COMMAND ACCEPTED

3-422

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

ins_device

Description
The ins_device command brings a device into service by locking and then unlocking the device. The following devices are supported: ABSS {34321}CAGE DHP KSW OPL SITE AXCDR CBL DRI MMS PATH XBL BSP CIC EAS MSI PCHN TDM BTP COMB GCLK MTL {26740} PSI CAB CSFP GPROC OML RSL

The ins_device command supports only extension cabinets of type TCU_2, TCU_6, and HORIZONMACRO_EXT. No other extension cabinet types are supported. A standby KSW must be available to use this command on a KSW. {22168} When the BSC is operating in enhanced capacity mode, if a redundant DSW is swapped and replaced by a KSW, then the BSS SW at a BSS rejects an attempt to ins a KSW device, the system displays COMMAND REJECTED: KSW transition not allowed in Dual Mode configuration message. If the BSC with the KSW in the cage is reset, the BSC initializes in single rate mode. If the ins_device command is applied to an active GCLK, and the standby GCLK is phase locking, the system displays an additional warning message. The following GPRS devices are supported if the GPRS feature is unrestricted: {28351} ETH {28351} GSL DPROC PCU GBL {28351} GDS

The following warning message is displayed when the TS1 of the BCCH carrier of a cell is INSed and PBCCH/PCCCH is enabled. WARNING: PBCCH/PCCCH timeslot would be lost which can cause GPRS traffic to be disrupted. Are you sure (y=yes, n=no)?. The following device is brought into service at a PCU using this command: MSI

68P02901W23-S

3-423 Nov 2009

Format

Chapter 3: Device/function related commands

A hard reset occurs when this command is entered for the following devices: BSP Security level Supported by OMC-R GUI Command type Prerequisites BTP 2 Yes B (operator actions required) This command is not allowed while in SYSGEN ON mode. This command can be entered irrespective of whether the device is locked or unlocked. Respond to the verification request prompt for an ABSS, AXCDR, BSP , BTP , DHP , GPROC or RSL. Respond to the verification request prompt for an MSI or MMS equipped with an OML. DHP GPROC

Operator actions

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 0 to 140 {27955A} pcu or pcu_0 device_name Literal that uniquely identifies the device. device_id1 First device identifier. This definition varies with each device. device_id2 Second device identifier. This definition varies with each device. device_id3 Third device identifier. This definition varies with each device. BSC BTS PCU

3-424

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Format

CIC syntax
A form of syntax is available for each method of specifying a CIC. The following CIC syntax applies to local transcoding: ins_device <location> CIC <cic_num1> ins_device <location> CIC <cic_num1> TO <cic_num2> ins_device <location> CIC <mms_id1> <mms_id2> ins_device <location> CIC <mms_id1> <mms_id2> <timeslot1> ins_device <location> CIC <mms_id1> <mms_id2> <timeslot1> TO <timeslot2> The following CIC syntax applies to remote transcoding:

NOTE
For remote transcoding BSC sites, the ins_device command cannot be used for CICs on a per-MMS basis when the BSC is operating in the dynamic allocation mode.

ins_device <location> CIC <cic_num1> ins_device <location> CIC <cic_num1> TO <cic_num2> ins_device <location> CIC <mms_id1> <mms_id2> ins_device <location> CIC <mms_id1> <mms_id2> <timeslot1> <group> ins_device <location> CIC <mms_id1> <mms_id2> <timeslot1> * ins_device <location> CIC <mms_id1> <mms_id2> <timeslot1> <group1> TO <timeslot2> <group2>

Input parameters
location Specifies the location of the device: 0 or bsc 0 to 140 pcu, pcu_0 to pcu_2 BSC BTS PCU

CIC Literal that uniquely identifies the CIC device. cic_num1 First CIC device number.

68P02901W23-S

3-425 Nov 2009

Examples

Chapter 3: Device/function related commands

cic_num2 Last CIC device number in a range. mms_id1 First MMS identifier. mms_id2 Second MMS identifier, or last in a range if TO is used. timeslot1 First timeslot. timeslot2 Second timeslot, or last in a range if TO is used. group1 First group. group2 Second group. * Indicates all CICs on the MMSs specified in the timeslot, regardless of the group.

Examples
Example 1
This example brings an MSI into service with ID 1 0 at the BSC. ins_device bsc msi 1 0 0 Where: bsc msi 1 0 0 is: location device_name device_id1 device_id2 device_id3

System response
COMMAND ACCEPTED

3-426

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Examples

Example 2
This example brings a range of CICs (remote transcoder) into service; the range is specified by their MMS, TS, and group. ins_device bsc cic 2 1 3 1 TO 5 1 Where: bsc cic 2 1 3 1 5 1 is: location CIC (device_name) mms_id1 mms_id2 timeslot 3 group 1 timeslot 5 group 1

System response
COMMAND ACCEPTED

Example 3
{22168} This example attempts to bring a KSW into service if the BSC is under enhanced capacity mode. ins 0 KSW 1 0 Where: 0 KSW 1 0 is: location device_name device_id1 device_id2

System Response
COMMAND REJECTED: KSW transition not allowed in Dual Mode configuration.

68P02901W23-S

3-427 Nov 2009

References

Chapter 3: Device/function related commands

Example 4
{34321} This example brings a cage into service and displays a confirmed command. A warning about the cage INS is displayed. ins_device bsc cage 3 0 Where: bsc cage 3 0 is: location device_name device_id1 device_id2

System response
CAGE 3 This will affect all devices in this CAGE and any associated

Extension CAGEs. Are you sure (y=yes,n=no)? yes COMMAND ACCEPTED

References
Related commands
lock_device on page 3-429 reset_device on page 3-485 unlock_device on page 3-581

3-428

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

lock_device

Description
The lock_device command locks a specified device. Security level Supported by OMC-R GUI 2 Yes

Command type Prerequisites

A (no operator actions) This command is not allowed while in SYSGEN ON mode. This command is only valid when the device is in the UNLOCKED state.

Format
General syntax
lock_device <location> <device_name> <device_id1> <device_id2> [<device_id3>]

Input parameters
location Specifies the location of the device: 0 or bsc 1 - 140 {27955A} pcu or pcu_0 BSC BTS PCU

The location must be bsc or 0 when specifying the device SITE. A PCU or a PCU device (for example, MSI) can also be locked. device_name Device name that uniquely identifies the device. The following devices can be locked using this command:

68P02901W23-S

3-429 Nov 2009

Format

Chapter 3: Device/function related commands

ABSS COMB GDS OPL

AXCDR CSFP GPROC PATH

BSP DHP GSL PCHN

BTP DRI KSW PCU

CAB DPROC MMS RSL

{34321} CAGE EAS MSI SITE

CBL GBL MTL XBL

CIC GCLK OML

The shutdown_device command is available for non-intrusive locking of CIC, DRI, MPRT, and MTL devices. If an MMS at an RXCDR is locked, it does not lock any OMLs or MTLs that are carried on its associated 2 Mbit/s link. However, any traffic circuit carried on this 2 Mbit/s link is blocked. This prevents any inadvertently locking devices at the RXCDR, where their existence on a 2 Mbit/s link is not visible. If locking the MTL or OML is necessary, they should be addressed as individual devices. Entering the lock_device command where the MSI or MMS carries an OML causes the system to display a verification request before actually locking the device. Locking the link between an RXCDR and the BSC MMS makes the associated XBL go out of service (OOS). This means that XBL does not block the circuits. When locking an ABSS or AXCDR, the system presents a warning prompt and a verification prompt. If XBLs are equipped on the first and second links, and the XBL on the first link is locked, the XBL on the first link goes OOS; the XBL on the second link blocks the circuits. If the lock_device command is applied to an active GCLK, and the standby GCLK is phase locked, the system displays an additional warning message. This command is rejected for a KSW if no standby KSW is available. When a KSW is locked, all calls currently on the KSW are lost. Normal call processing resumes when the KSW is unlocked. For remote transcoding BSC sites, CICs cannot be locked on a per-MMS basis when the BSC is operating in the dynamic allocation mode. The lock_device command supports the following extension cabinets: TCU_2, TCU_6, Horizonmacro_EXT, Horizon2macro_ext, Horizon2micro_ext, and Horizon2mini_ext. DRIs and EASs equipped to the cabinet are disabled. No other cabinet types are supported. The following warning message is displayed when the TS1 of the BCCH carrier of a cell is locked and PBCCH/PCCCH is enabled. WARNING: PBCCH/PCCCH timeslot would be lost which can cause GPRS traffic to be disrupted. Are you sure (y=yes, n=no)? A hard reset occurs when this command is entered for the following devices: BSP BTP device_id1 First device identifier. This value varies with each device. device_id2 Second device identifier. This value varies with each device. DHP GPROC

3-430

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Format

device_id3 Third device identifier. This value varies with each device. If the specified device is a PCU, the PCU identifier must be entered as device_id1. A PCU or PCU device (for example MSI) can also be locked as a location.

CIC syntax
A form of syntax is available for each method of specifying a CIC. The following CIC syntax applies to local transcoding: lock_device <location> CIC <cic_num1> lock_device <location> CIC <cic_num1> TO <cic_num2> lock_device <location> CIC <mms_id1> <mms_id2> lock_device <location> CIC <mms_id1> <mms_id2> <timeslot1> lock_device <location> CIC <mms_id1> <mms_id2> <timeslot1> TO <timeslot2> The following CIC syntax applies to remote transcoding: lock_device <location> CIC <cic_num1> lock_device <location> CIC <cic_num1> TO <cic_num2> lock_device <location> CIC <mms_id1> <mms_id2> lock_device <location> CIC <mms_id1> <mms_id2> <timeslot1> <group> lock_device <location> CIC <mms_id1> <mms_id2> <timeslot1> * lock_device <location> CIC <mms_id1> <mms_id2> <timeslot1> <group1> TO <timeslot2> <group2>

68P02901W23-S

3-431 Nov 2009

Examples

Chapter 3: Device/function related commands

mms_id1 First MMS identifier. mms_id2 Second MMS identifier, or last in a range if TO is used. timeslot1 First timeslot. timeslot2 Second timeslot, or last in a range if TO is used. group1 First group. group2 Second group. * Indicates all CICs on the MMSs specified in the timeslot, regardless of group.

Examples
Example 1
This example locks an MSI with ID 1 at the BSC from further use. lock_device bsc msi 1 0 0 Where: bsc msi 1 0 0 is: location device_name device_id1 device_id2 device_id3

System response
COMMAND ACCEPTED

3-432

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Examples

Example 2
This example locks a range of CICs; the range is specified by their MMS, TS, and group. lock_device bsc cic 2 1 3 1 TO 5 1 Where: BSC CIC 2 1 3 1 5 1 is: location device_name mms_id1 mms_id2 timeslot 3 group 1 timeslot 5 group 1

System response
COMMAND ACCEPTED

Example 3
{28351} This example displays PXP DPROC information. lock pcu_0 dproc 4 0 Where: pcu_0 dproc 4 0 is: location device_name mms_id1 mms_id2

68P02901W23-S

3-433 Nov 2009

Examples

Chapter 3: Device/function related commands

System response
This command will affect the following link devices --------------------------------------------------GDS 4 The GDS carries GPRS data traffic between the BSC and the PCU Loss of a GDS device will reduce GPRS traffic capacity between the BSC and the PCU. A PXP or PRP DPROC with no GDSs in service will not be able to schedule any GPRS traffic. GSL 0 0 The GSL carries signaling traffic between the BSC and the PCU. If there are no B-U GSL devices, the PCU will go out of service. GSL 0 2 The GSL carries signaling traffic between the BSC and the PCU. If there are no B-U GSL devices, the PCU will go out of service. Are you sure (y=yes,n=no)?

Example 4
{34321} This example locks a cage and displays a confirmed command. A warning about the cage lock is issued. lock_device bsc cage 1 0 Where: bsc cage 1 0 is: location device_name device_id1 device_id2

System response
CAGE 1 This will affect all devices in this CAGE and any associated

Extension CAGEs. Are you sure (y=yes,n=no)? yes COMMAND ACCEPTED

3-434

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Examples

Example 5
{34321} This example locks a cage when the lock command action results in the standby BSP going out of service. lock_device bsc cage 1 0 Where: bsc cage 1 0 is: location device_name device_id1 device_id2

System response
CAGE 1 This will affect all devices in this CAGE and any associated

Extension CAGEs. WARNING: This will result in the loss of the standby BSP at this BSC. Are you sure (y=yes,n=no)? yes COMMAND ACCEPTED

Example 6
{34321} This example displays warning about links impacted by a cage transition. lock_device 0 cage 1 0 0 Where: 0 cage 1 0 0 is: location device_name device_id1 device_id2 device_id3

68P02901W23-S

3-435 Nov 2009

Examples

Chapter 3: Device/function related commands

System response
CAGE 1 This will affect all devices in this CAGE and any associated

Extension CAGEs. This command will affect the following link devices: ---------------------------------------------------OML 1 The OML carries operations and maintenance traffic between the BSS and the OMC. If there are no B-U OML devices, the OMC will not be able to manage the BSS. The MTL carries signaling traffic between the BSS and the MSC. If there are no B-U MTL devices, all cells in the BSS will become blocked. The MTL carries signaling traffic between the BSS and the MSC. If there are no B-U MTL devices, all cells in the BSS will become blocked. This command may affect service to the BTS. Use the state command to verify if this is the last RSL to the BTS. The RSL carries signaling traffic between the BSC and a BTS. If there are no B-U RSL devices to a given BTS, all access to the site will be lost. This command may affect service to the BTS. Use the state command to verify if this is the last RSL to the BTS. The RSL carries signaling traffic between the BSC and a BTS. If there are no B-U RSL devices to a given BTS, all access to the site will be lost. This command may affect service to the BTS. Use the state command to verify if this is the last RSL to the BTS. The RSL carries signaling traffic between the BSC and a BTS. If there are no B-U RSL devices to a given BTS, all access to the site will be lost.

MTL 0

MTL 2

RSL 7 0

RSL 7 1

RSL 11 0

RSL 12 0

This command may affect service to the BTS. Use the state command to verify if this is the last RSL to the BTS. The RSL carries signaling traffic between the BSC and a BTS. If there are no B-U RSL devices to a given BTS, all access to the site will be lost.

Are you sure (y=yes,n=no)? yes COMMAND ACCEPTED

3-436

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

References

References
Related commands
disp_equipment on page 3-283 shutdown_device on page 3-502 unlock_device on page 3-581 equip on page 3-403 state on page 3-515 reset_device on page 3-485 unequip on page 3-570

68P02901W23-S

3-437 Nov 2009

Chapter 3: Device/function related commands

{27508}

Description
The login command authenticates a qcomm user of certain access level. Security level 1

Supported by OMC-R GUI Command type Prerequisites

No B (operator actions required) None

Format
Syntax
login

Example

NOTE
BSS does not support login command to be executed twice without logout. The password shown in this example is only for information. The passwords are not displayed when entered.

Example 1
This example authenticates an operator to log in with the unix account information or field engineer user information. login

3-438

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Example

System response
Please input your UNIX account information. Login: abcdef Password: abcdef COMMAND ACCEPTED

Example 2
{27508} In this example, the OML link is up and fieldeng_always_enabled is set to 0 login

System response
Please input your UNIX account information. Login: abcdef Password: abcdef COMMAND ACCEPTED

Example 3
{27508} In this example, the OML link is down and fieldeng_always_enabled is set to 0 login

68P02901W23-S

3-439 Nov 2009

Example

Chapter 3: Device/function related commands

System response
Please input your Field Engineer account information. Login: abcd Password: abcdef WARNING: Login incorrect Please input your Field Engineer account information. Login: abcd Password: abcdef WARNING: Login incorrect Please input your Field Engineer account information. Login: abcd Password: abcdef WARNING: Login incorrect COMMAND REJECTED: Login Blocked.

3-440

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Logout

{27508}

Description
The logout command terminates all the activities of the current operator. Security level Supported by OMC-R GUI Command type Prerequisites 1 No B (operator actions required) None

Format
Syntax
logout

68P02901W23-S

3-441 Nov 2009

mod_conn

Chapter 3: Device/function related commands

mod_conn

Description
The mod_conn command modifies the MMS connectivity between the RXCDR and the BSS. This command allows the operator to change the E1 connectivity information identifying which RXCDR is associated with the E1 link and the device identity within the RXCDR to which the E1 link is connected. This connectivity information must be specified for each E1 link connecting to an RXCDR. Security level Supported by OMC-R GUI Command type Prerequisites 4 Yes B (operator actions required) The AXCDR or ABSS device specified in the command must be equipped in the BSS database. No XBL devices can be equipped that use the local MMS when changing the BSS or RXCDR network entity identifier. The local MMS must be locked before the connectivity is modified. Change the security level to 2. Lock the local MMS before modifying the connectivity.

Operator actions

Format
Syntax
mod_conn <local_mms_id_1> <local_mms_id_2> <network_entity_id> <remote_mms_id_1><remote_mms_id_2>

3-442

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Example

network_entity_id The AXCDR or ABSS device identifier that represents the actual RXCDR or BSS with which this MMS is communicating. remote_mms_id_1 First identifier of the MMS at the remote site. The term remote site refers to the site to which the local site is connected. remote_mms_id_2 Second identifier of the MMS at the remote site. The mod_conn command can be executed from either the BSC or the RXCDR. The ranges for several input parameters depend on where the command is executed, as shown in Table 3-32.

Table 3-32

mod_conn valid ranges

Execution location BSC {22169} 0 to 95 0 or 1 1 to 254 0 to 123 0 or 1 RXCDR 0 to 123 0 or 1 1 to 254 {22169} 0 to 95 0 or 1

Input parameter local_mms_id_1 local_mms_id_2 network_entity_id remote_mms_id_1 remote_mms_id_2

Example
This example changes MMS connectivity between BSC MMS 4 1 and RXCDR MMS 9 0 of RXCDR 3, which is represented by equipped device AXCDR 3. mod_conn 4 1 3 9 0 Where: 4 1 3 9 0 is: local_mms_id_1 local_mms_id_2 network_entity_id remote_mms_id_1 remote_mms_id_2

System response:
COMMAND ACCEPTED

68P02901W23-S

3-443 Nov 2009

References

Chapter 3: Device/function related commands

References
Related commands
add_conn on page 3-33 del_conn on page 3-195 disp_conn on page 3-261

3-444

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

mod_nsvc

Description
The mod_nsvc command modifies the frame relay committed information rate, the frame relay burst size, and the frame relay burst excess for a specified Network Service - Virtual Connection Identifier (NSVCI), at a specific PCU. Security level Supported by OMC-R GUI Command type Prerequisites Operator action 4 Yes B (operator actions required) The GPRS feature must be unrestricted. The operator must answer the prompts.

Format
Syntax
mod_nsvc <pcu_id> <ns_vci>

Input parameter
pcu_id {27955A} Specifies the unique identifier of the PCU, as pcu or pcu_0. ns_vci Specifies the unique identifier of the NSVC mapping and identifier of the object. The range is 0 to 65535. Prompts are then displayed as follows: Enter the Committed Information rate: Enter the Committed Burst Size: Enter the Burst Excess: The first prompt specifies the frame relay committed information rate ns_commit_info_rate (0 to 1984). There is no default. The second specifies the frame relay burst size ns_burst_size (0 to 1984). There is no default.

68P02901W23-S

3-445 Nov 2009

Example

Chapter 3: Device/function related commands

The third specifies the frame relay burst excess ns_burst_excess (0 to 1984). There is no default.

NOTE
ns_burst_size and ns_burst_excess, both must not be 0. If either ns_commit_info_rate or ns_burst_size is 0, then both must be 0.

Example
The following example modifies the frame relay committed information rate, the frame relay burst size, and the frame relay burst excess for NSVCI 6, at PCU_2 site. mod_nsvc pcu_2 6 Where: pcu_2 6 is: PCU site 2 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.

Are you sure (y=yes, n=no) ? y

COMMAND ACCEPTED

References
Related commands
del_nsvc on page 3-202 add_nsvc on page 3-48

3-446

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

modify_neighbor

Description
The modify_neighbor command modifies the value of a GSM or UTRAN neighbor cell parameter. The neighbor_cell_id can be a test cell neighbor. The changing of the ba_bcch parameter is only allowed for test neighbors which are on the BA_SACCH list of the cell. To add a neighbor to the BA_BCCH list without adding to the BA_SACCH list, use the add_neighbor command. To remove a neighbor from the BA_BCCH list which is not on the BA_SACCH list, use the del_neighbor command. When pgbt_mode is set to 1, a new neighbor is auto-equipped with its BCCH frequency set to the BCCH frequency of the serving cell. This neighbor cell cannot be modified by the modify_neighbor command. If the Inter-RAT handover feature or Enhanced 2G/3G handover feature (which includes Enhanced Inter-RAT handover) is unrestricted, handovers can be made to UTRAN cells. Security level Supported by OMC-R GUI Command type Prerequisites 4 Yes A (no operator actions) The changing of the synchronized parameter is only allowed for neighbors at the site of the source cell. If the neighbor is a UTRAN cell, the Inter-RAT handover feature must be unrestricted. A UTRAN neighbor specific parameter cannot be modified for a GSM neighbor cell. A GSM neighbor specific parameter cannot be modified for a UTRAN neighbor cell. The specified UTRAN cell identifier must exist as a neighbor cell of the GSM source cell. If the neighbor is a UTRAN cell, the Inter-RAT handover feature or Enhanced 2G/3G handover feature must be unrestricted.

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

68P02901W23-S

3-447 Nov 2009

Format

Chapter 3: Device/function related commands

Format
Syntax
modify_neighbor <source_cell_id> <neighbor_cell_id> <parameter> <value>

Input parameters
source_cell_id Cell identity of the source cell. neighbor_cell_id Cell identity of the neighbor cell whose parameter value is being changed. The format for the GSM cell ID depends on: The system used (PGSM, EGSM, DCS1800, PCS1900, or GSM850). Whether the seven parameter GSM cell ID format or the four parameter GSM cell ID format has been enabled. Whether the cell is a UTRAN cell. The cell_id can also be a cell name created using the cell_name command. When the cell name is entered, it must be placed inside double quotation marks.

For an internal neighbor cell only, the cell_id can also be a cell name created using the cell_name command. A cell_name cannot be used to specify an external neighbor cell. When the cell name is entered, it must be placed inside double quotation marks. parameter Neighbor cell parameter to be changed, one of: Parameter adap_trigger_pbgt_nbr Action Specifies the cumulative area for the adaptive handover power budget algorithm; valid only for SACCH and SACCH/BCCH neighbors. Turns adjacent channel interference on or off. Adds or deletes a neighbor cell from the BA_BCCH list. Adds or deletes a neighbor cell from the BA_GPRS list. Determines the hand over margin to be used in the event of congestion. This value is only changed when either the Directed Retry or alternate congestion relief feature is enabled. This attribute is only valid for SACCH neighbors. If the directed retry feature is not enabled, the value defaults to the value of the ho_margin_cell of the neighbor. The system does not prompt for the congest_ho_margin value if the Directed Retry option was not purchased. Continued

adj_chan_intf_test ba_bcch ba_gprs congest_ho_margin

3-448

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Format

Parameter dr_allowed

Action Allows a directed retry to an external neighbor during the assignment procedure. An external handover is only initiated if either the dr_standard_congest or dr_ho_during_assign parameter is enabled. This attribute is only valid for SACCH neighbors. The system does not prompt for the dr_allowed value if the Directed Retry option was not purchased. Changes handover margin of a neighbor cell. Sets the value to be applied to the power budget calculation when calls are handed over due to transmission levels (rxlev). If the power budget value minus the ho_margin_rxlev is less than 0 for a cell, that cell is excluded from the neighbor list. This parameter also interacts with the bounce_protect_mar to prevent reverse handovers due to power budget reasons. Refer to the bounce_protect_mar description. Sets the value to be applied to the power budget calculation when calls are handed over due to transmission quality levels (rxqual). If the power budget value minus the ho_margin_rxqual is less than 0 for a cell, that cell is excluded from the neighbor list. This parameter also interacts with the bounce_protect_mar to prevent reverse handovers due to power budget reasons. Refer to the bounce_protect_mar description. Enables or disables the interference algorithm for the inner zone for this neighbor. This is allowed only if both: The Concentric Cells feature is enabled. The inner_zone_alg is set to 2. If the interfering_nbr parameter is enabled, the system displays the inner_zone_threshold and inner_zone_margin prompts. Pressing the Return (Enter) key without entering new values for the inner_zone_threshold and the inner_zone_margin prompts will keep any existing values.

ho_margin_cell ho_margin_rxlev

ho_margin_rxqual

interfering_nbr

ms_txpwr_max_cell neighboring_range pbgt_alg_type pbgt_hreqave rxlev_min_cell synchronized fdd_arfcn

Changes the maximum MS transmitted power for a neighbor cell. Changes which range the neighbor borders on in an extended cell. Changes the power budget algorithm type. Changes the power budget hreqave. Changes minimum receive level for a neighbor cell. Allows synchronized handovers for neighbor cells. Indicates the frequency of a UTRAN cell. Continued

68P02901W23-S

3-449 Nov 2009

Format

Chapter 3: Device/function related commands

Parameter scr_code diversity_enabled umts_meas_margin umts_ncell_avg_period umts_ba_bcch {31400} tdd_arfcn

Action Indicates the primary scrambling code of a UTRAN cell. Indicates whether diversity is applied in a UTRAN cell. Defines the per neighbor handover threshold. Only valid when a UTRAN BCCH or SACCH neighbor cell is specified. Defines the per neighbor averaging period. Only valid when a UTRAN BCCH or SACCH neighbor cell is specified. Adds or deletes a UTRAN BCCH neighbor from the UMTS_BA_BCCH list. Indicates the TD-SCDMA frequency. This is a Read-Write attribute of the UTRAN Neighbor Cell. When tdOpt is restricted, this parameter cannot be modified. Indicates the TD-SCDMA cell parameter as defined in TS25.223. This is a Read-Write attribute of the UTRAN Neighbor Cell. When tdOpt is restricted, this parameter cannot be modified. Indicates the TD-SCDMA Time Switched Transmit Diversity mode. This is a Read-Write attribute of the UTRAN Neighbor Cell. When tdOpt is restricted, this parameter cannot be modified. Indicates the TD-SCDMA cell diversity capability (Space Code Transmit Diversity). This is a Read-Write attribute of the UTRAN Neighbor Cell.

{31400} tdd_cell_param

{31400} tdd_tstd_mode

{31400} tdd_sctd_mode

value The new value of the selected neighbor cell parameter. Values for this field are dependent upon the selected parameter. Parameter adap_trigger_pbgt_nbr adj_chan_intf_test ba_bcch congest_ho_margin dr_allowed ho_margin_cell ho_margin_rxlev ho_margin_rxqual ho_margin_type5 interfering_nbr ms_txpwr_max_cell Value 0 to 255; default is 40 (the value of 40 corresponds to a hreqave of 8 and a handover margin of 5) 0 (no) or 1 (yes) add or delete -63 to 63 0 (no) or 1 (yes) -63 to 63 -63 to 63 -63 to 63 -63 to 63 0 (no) or 1 (yes) PGSM or EGSM: 5 to 39 (odd values only) DCS1800: 0 to 30 (even values only) PCS1900: 0 to 30 (even values only) GSM850: 5 to 39 (odd values only) Continued 3-450 68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Examples

Parameter neighboring_range pbgt_alg_type pbgt_hreqave rxlev_min_cell synchronized fdd_arfcn scr_code diversity_enabled umts_meas_margin umts_ncell_avg_period umts_ba_bcch {31400} tdd_arfcn {31400} tdd_cell_param {31400} tdd_tstd_mode {31400} tdd_sctd_mode

Value normal (neighbor is a normal range cell) extended (neighbor is an extended range cell) 1 to 6 1 to 31 0 to 63 yes or no 10562 to 10838 0 to 511 0 or 1 0 to 20 dB; default is 3 dB (for UTRAN BCCH or UTRAN SACCH neighbors if 2G/3G Handover feature is unrestricted) 1 to 12; default is 6 (for UTRAN BCCH or UTRAN SACCH neighbors if 2G/3G Handover feature is unrestricted) Add or delete (for UTRAN BCCH neighbors only) 10054 to 10121 0 to 127 0 (Disabled) or 1(Enabled); default is 0 0 (Disabled) or 1(Enabled); default is 0

NOTE
If the pbgt_alg_type, adj_chan_intf_test or interfering_nbr is modified by this command, additional prompts display. Refer to the description of the add_neighbor command for the prompted parameter values.

Examples
Example 1
This example adds the frequency of neighbor cell 5 4 3 2 1 4344 9755 to the BA_BCCH list of source cell 5 4 3 2 1 676 8645. The cell numbers are in seven parameter format. modify_neighbor 5 4 3 2 1 676 8645 5 4 3 2 1 4344 9755 ba_bcch add Where: 5 4 3 2 1 676 8645 5 4 3 2 1 4344 9755 ba_bcch add is: src_cell_id neighbor_cell_id the parameter to be modified. the parameter value.

68P02901W23-S

3-451 Nov 2009

Examples

Chapter 3: Device/function related commands

System response
COMMAND ACCEPTED

Example 2
The example below shows the same cell numbers in four parameter format: modify_neighbor 543 21 676 8645 543 21 4344 9755 ba_bcch add Where: 543 21 676 8645 543 21 4344 9755 ba_bcch add is: src_cell_id neighbor_cell_id the parameter to be modified. the parameter value.

System response
COMMAND ACCEPTED

Example 3
This example changes the power budget algorithm to 3 for neighbor cell 5 4 3 2 1 344 975 of src_cell 5 4 3 2 1 667 865. Additional prompts display.

NOTE
This example shows interaction associated with the M-Cellmicro option.

modify_neighbor 5 4 3 2 1 667 865 5 4 3 2 1 344 975 pbgt_alg_type 3 Where: 5 4 3 2 1 667 865 5 4 3 2 1 344 975 pbgt_alg_type 3 is: src_cell_id neighbor_cell_id the parameter to be modified. the parameter value.

System response
Enter the uplink receive level threshold of the serving cell: 25 COMMAND ACCEPTED Enter the downlink receive level threshold of the serving cell: 25 3-452 68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Examples

Example 4
This example sets the interfering_nbr to 1 (yes). modify_neighbor 5 4 3 2 1 667 865 5 4 3 2 1 344 975 interfering_nbr 1 Where: 5 4 3 2 1 667 865 5 4 3 2 1 344 975 interfering_nbr 1 is: src_cell_id neighbor_cell_id the parameter to be modified. the parameter value.

System response
Enter the threshold for inner zone handover: 1

Enter the margin for inner zone handover: 1

COMMAND ACCEPTED

Example 5
This example modifies the scr_code element of UTRAN neighbor cell 4 9 6 2 3 1 1 1 1 to a value of 5 as a neighbor of source GSM cell 0 0 1 0 1 1 4. modify_neighbor 0 0 1 0 1 1 4 4 9 6 2 3 1 1 1 1 scr_code 5 Where: 0010114 496231111 scr_code 5 is: src_cell_id (GSM) neighbor_cell_id (UTRAN) the parameter to be modified. the parameter value.

System response
COMMAND ACCEPTED

68P02901W23-S

3-453 Nov 2009

Examples

Chapter 3: Device/function related commands

Example 6
This example modifies the umts_ba_type for UTRAN BCCH neighbor l 4 9 6 2 3 1 1 1 1 of GSM cell 0 0 1 0 1 1 4 to include it in the UTRAN BCCH neighbor list. modify_neighbor 0 0 1 0 1 1 4 4 9 6 2 3 1 1 1 1 umts_ba_bcch add Where: 0010114 496231111 umts_ba_bcch add is: src_cell_id (GSM) neighbor_cell_id (UTRAN) the parameter to be modified. the parameter value.

System response
COMMAND ACCEPTED

Example 7
{31400} This example modifies the tdd_cell_param attribute to a value of 100 for TD-SCDMA cell 4 9 6 2 3 1 1 1 1 as a neighbor of GSM cell 0 0 1 0 1 1 4. modify_nieghbor 0 0 1 0 1 1 4 4 9 6 2 3 1 1 1 1 tdd_cell_parameter 100 Where: 0010114 496231111 tdd_cell_param 100 is: src_cell_id (GSM) neighbor_cell_id (UTRAN) the parameter to be modified. the parameter value.

System response
COMMAND ACCEPTED

NOTE
This response is also applied for tdd_arfcn, tstd_mode, and tdd_diversity_enabled for TD-SCDMA neighbor cell attributes.

3-454

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

References

References
Related commands
add_cell on page 3-22 del_cell on page 3-192 disp_gsm_cells on page 3-314 add_neighbor on page 3-35 del_neighbor on page 3-197 disp_neighbor on page 3-343 copy_cell on page 3-179 disp_cell on page 3-241

68P02901W23-S

3-455 Nov 2009

modify_value

Chapter 3: Device/function related commands

modify_value

Description
The modify_value command modifies parameter values for equipped devices or functions. These values can be displayed using the disp_equipment command. This command is rejected if a dual band Horizon II macro cabinet contains an invalid HorizonII Dual Band DRI setup.

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

Security level Supported by OMC-R GUI Command type Prerequisites

4 Yes The type is dependent on the parameter being modified. The modify_value command can only be entered at the BSC. Individual prerequisites are given for modify_value parameters as relevant. The GPRS PICP MSI type is not supported by this command. To use all as the location parameter, place the system in the SYSGEN ON mode before entering the command.

Operator actions

NOTE
Refer to the descriptions of individual parameters for additional operator actions.

Format
Syntax
modify_value <location> <value_name> <new_value> <dev_func> <dev_func_id1><dev_func_id2> <dev_func_id3>

Input parameters
location

3-456

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Format

Specifies the location of the device. Values are: 0 or bsc 1 - 140 {27955A} pcu or pcu_0 all BSC BTS PCU Every equipped device or function of the specified type. Only applicable to MMS, RSL, and XBL. This value is only applicable during SYSGEN ON mode. If all is entered, the parameters dev_func_id1, dev_func_id2 and dev_func_id3 are not required. value_name The device or function parameter name. Refer to the individual parameter listing in Chapter 8 Device/Function parameters for descriptions and valid values of these parameters. new_value The value to be assigned to the named parameter. Refer to the individual parameter descriptions in Chapter 8 Device/Function parameters for valid values. dev_func This value identifies the device or function affected by the modified parameter. For example, BSP , GCLK, SITE, as relevant to the value_name parameter. See Chapter 8 Device/Function parameters. dev_func_id1 Values are dependent on the device or function type. dev_func_id2 Values are dependent on the device or function type. dev_func_id3 Values are dependent on the device or function type.

NOTE
When changing certain cabinet types with this command, the following message is displayed: Cannot change to new cab type as bts power control is enabled. When an attempt is made to modify ext_timeslots, or pkt_radio_type, and the requested PDTCHs exceed the GDS or PMC capacity on the PCU, the BSS accepts the request and issues a warning to indicate that there is not enough GDS or PMC resource available.

68P02901W23-S

3-457 Nov 2009

Examples

Chapter 3: Device/function related commands

Examples
Example 1
In this example, the maximum number of DRIs on DHP 4 2 0 at site 7 is changed to 5: modify_value 7 max_dris 5 dhp 4 2 0 Where: 7 max_dris 5 dhp 4 2 0 is: location value_name new_value dev_func dev_func_id1 dev_func_id2 dev_func_id3

System response
COMMAND ACCEPTED

Example 2
This example modifies the value of cic_unblock_thresh when eac_mode is enabled and AMR or GSM HR is unrestricted for an AXCDR at site 0. modify_value 0 cic_unblock_thresh 250 AXCDR 1 2 8 Where: 0 cic_unblock_thresh 250 AXCDR 1 2 8 is: location value_name new_value dev_func dev_func_id1 dev_func_id2 dev_func_id3

System response
COMMAND ACCEPTED

3-458

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Examples

Example 3
This example disables eac_mode whether AMR HR or GSM HR is enabled or not for an AXCDR at site 0. modify_value 0 eac_mode no AXCDR 1 2 8 Where: 0 eac_mode no AXCDR 1 2 8 is: location value_name new_value dev_func dev_func_id1 dev_func_id2 dev_func_id3

System response
WARNING: Disabling enhanced auto connect mode will terminate all active calls through this Associated RXCDR from the BSC, and configure the CIC Ater assignments as for Auto Connect mode Are you sure (y/n) y COMMAND ACCEPTED

Example 4
This example enables eac_mode with cic_validation enabled and amr_bss_half_rate_enabled and gsm_bss_half_rate_enabled disabled for an AXCDR at site 0. modify_value 0 eac_mode yes AXCDR 1 2 8 Where: 0 eac_mode yes AXCDR 1 2 8 is: location value_name new_value dev_func dev_func_id1 dev_func_id2 dev_func_id3

68P02901W23-S

3-459 Nov 2009

Examples

Chapter 3: Device/function related commands

System response
WARNING: AMR and GSM Half Rate is currently disabled at this BSC. COMMAND ACCEPTED

Example 5
In this example, the frequency_type for a Horizon II macro cabinet is modified from EGSM90000 to EGSM900 and DCS1800 for Dual band on a single cabinet: modify_value 7 frequency_type 6 CAB 0 0 0 Where: 7 frequency_type 6 CAB 0 0 0 is: location value_name new_value dev_func dev_func_id1 dev_func_id2 dev_func_id3

System response
COMMAND ACCEPTED

Example 6
This example modifies the type of cabinet 15 0 0 from Horizon macro extension to Horizon II mini extension, where the current cabinet has no dependent devices. modify_value 5 cabinet_type 27 CAB 15 0 0 Where: 5 cabinet_type 27 CAB 15 0 0 is: location value_name new_value dev_func dev_func_id1 dev_func_id2 dev_func_id3

3-460

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Examples

System response
COMMAND ACCEPTED

Example 7
This example modifies pkt_radio_type from 1 to 3 with a warning that not enough GDS resources handle PDTCHs. modify_value 1 pkt_radio_type 3 rtf 1 1 Where: 1 pkt_radio_type 3 rtf 1 1 is: location value_name new_value dev_func dev_func_id1 dev_func_id2

System response
Enter the rtf_ds0_count: 6 WARNING: This operation may cause a carrier to be taken out of service and calls affected by this carrier may be lost. Loss of calls depends on the availability of other carriers. Are you sure (y=yes, n=no)? y COMMAND ACCEPTED: WARNING: Insufficient GDS resources available for all PDTCHs on the PCU.

68P02901W23-S

3-461 Nov 2009

Examples

Chapter 3: Device/function related commands

Example 8
{28337} This example modifies max_mtls values to 31 on GPROC3-2. modify_value 0 max_mtls 31 LCF 0 0 0 Where: 0 max_mtls 31 LCF 0 0 0 is: location value_name new_value dev_func dev_func_id1 dev_func_id2 dev_func_id3

System response
WARNING: HSP LCF equipage may trigger GPROC preemption. Are you sure (y=yes,n=no)? y COMMAND ACCEPTED. WARNING: Resources are not currently available. Parent entity must be manually reset before change takes effect.

Example 9
{28337} This example attempts to modify the max_mtls value to 31 on GPROC3. modify_value 0 max_mtls 31 LCF 1 0 0 Where: 0 max_mtls 31 LCF 1 0 0 is: location value_name new_value dev_func dev_func_id1 dev_func_id2 dev_func_id3

3-462

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Examples

Example 10
{28337} This example attempts to increase the max_gsls value from 0 on LCF which has already managed HSP MTL. modify_value 0 max_gsls 1 LCF 1 0 0 Where: 0 max_mtls 1 LCF 1 0 0 is: location value_name new_value dev_func dev_func_id1 dev_func_id2 dev_func_id3

System response
COMMAND REJECTED: Insufficient GPROC timeslots available

68P02901W23-S

3-463 Nov 2009

Examples

Chapter 3: Device/function related commands

Example 11
{28337} This example attempts to increase the max_cbls value from 0 on LCF which has already managed HSP MTL. modify_value 0 max_cbls 1 LCF 1 0 0 Where: 0 max_cbls 1 LCF 1 0 0 is: location value_name new_value dev_func dev_func_id1 dev_func_id2 dev_func_id3

System response
COMMAND REJECTED: Insufficient GPROC timeslots available

Example 12
{28337} This example attempts to increase the max_opls value from 0 on LCF which has already managed HSP MTL. modify_value 0 max_opls 1 LCF 1 0 0 Where: 0 max_opls 1 LCF 1 0 0 is: location value_name new_value dev_func dev_func_id1 dev_func_id2 dev_func_id3

System response
COMMAND REJECTED: Insufficient GPROC timeslots available

3-464

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Examples

Example 13
{28351} This example modifies the base IP address of the PCU. modify_value 0 base_ip_address 10.3.16.36 pcu 0 Where: 0 base_ip_address 10.3.16.36 pcu 0 is: location value_name new_value dev_func dev_func_id1

System response
Enter the GDS subnet mask: 255.255.192.0 WARNING: Changing base_ip_address will cycle device PCU. Are you sure (y=yes,n=no)? y COMMAND ACCEPTED

Example 14
{28351} This example modifies the subnet mask of the PCU. modify_value 0 gds_subnet_mask 255.255.255.22 pcu 0 Where: 0 gds_subnet_mask 255.255.255.22 pcu 0 is: location value_name new_value dev_func dev_func_id1

System response
WARNING: Changing gds_subnet_mask will cycle device PCU. Are you sure (y=yes,n=no)? y COMMAND ACCEPTED

68P02901W23-S

3-465 Nov 2009

Examples

Chapter 3: Device/function related commands

Example 15
{26481} In this example, the operator attempts to enable opto alarm (out of range 1-6) through modify_val for EAS equipped to H2micro cabinet. modify_value 8 opto_reporting on eas 0 0 0 Where: 8 opto_reporting on eas 0 0 0 is: location value_name new_value dev_func dev_func_id1 dev_func_id2 dev_func_id3

System response
Enter the opto(s) whose state changes should now be reported: 3 6 9 ERROR: Range Error, parameter number: 3.

Example 16
{28351} This example modifies the base IP address of the PSI. modify_value 0 base_ip_address 10.3.16.36 psi 1 Where: 0 base_ip_address 10.3.16.36 psi 1 is: location value_name new_value dev_func dev_func_id1

System response
Enter the subnet mask: 255.255.255.0 WARNING: Changing base IP address, subnet mask will cycle device ETH. Are you sure (y=yes,n=no)? y COMMAND ACCEPTED

3-466

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Examples

Example 17
{23311A} This example sets the number of extended PDCHs to 3 for RTF 5,11 in site 3. modify_val 3 ext_pdchs 3 rtf 5 11 Where: 3 ext_pdchs 3 rtf 5 11 is: location value_name new_value dev_func dev_func_id1 dev_func_id2

System response
COMMAND ACCEPTED

Example 18
{23311A} This example attempts to set ext_timeslots for the RTF (5,11) to 2 when RTF 5,11 is configured for Extended GPRS and ext_pdchs is set to 3. modify_value 5 ext_timeslots 2 rtf 5 11 Where: 5 ext_timeslots 2 rtf 5 11 is: location value_name new_value dev_func dev_func_id1 dev_func_id2

System response
COMMAND REJECTED: Value of ext_timeslots shall be >= ext_pdchs for ERC GPRS RTF

68P02901W23-S

3-467 Nov 2009

References

Chapter 3: Device/function related commands

Example 19
{23311A} This example attempts to change pkt_radio_type = None for the RTF (5,11) when ext_pdchs in the RTF is set to 3. modify_value 5 pkt_radio_type None rtf 5 11 Where: 5 pkt_radio_type None rtf 5 11 is: location value_name new_value dev_func dev_func_id1 dev_func_id2

System response
COMMAND REJECTED: Value of ext_pdchs shall be 0 when pkt_radio_type = NONE for the RTF

References
Related commands
disp_equipment on page 3-283 equip on page 3-403 reassign on page 3-477

3-468

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

nacc_nc2_enabled

Description
The per-BSS element nacc_nc2_enabled allows the customer to enable or disable the NC2 mode of NACC. This element can be accessed and updated both in and out of Sysgen mode. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) No No None

Syntax
Change command string
chg_element nacc_nc2_enabled <value> <location>

Display command string

disp_element nacc_nc2_enabled <location>

Values
Value type Valid range Boolean 0 to 1 0 1 Default value 0 Disables the NC2 mode of NACC. Enables the NC2 mode of NACC.

68P02901W23-S

3-469 Nov 2009

page

Chapter 3: Device/function related commands

page

Description
The page command enables or disables pagination for display commands. The page command can also specify the number of lines displayed per page for display commands.

NOTE
The page command applies only to the current session and the current processor board (GPROC, GPROC2, or GPROC3). Setting it from an OMC-R rlogin does not affect any other OMC-R rlogins or TTY MMI logins. Setting it from a TTY MMI login does not affect any other TTY MMI logins or OMC-R rlogins. At every new login, it is reset to off.

Security level Supported by OMC-R GUI Command type Prerequisites

1 No A (no operator actions) None

Format
Syntax
page <input>

Input parameter
input Valid input formats are as follows: Input off <lines per page> none Action Disables pagination. Enables pagination and sets the number of lines displayed per page. Displays current page setting. Range No range. This is the default value. Any numeric value between 20 and 255. Not applicable.

3-470

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Examples

Examples
Example 1
This example shows that pagination has been enabled, and displays show 30 lines per page. page 30

Example 2
This example shows that pagination has been disabled. page off

Example 3
This example shows no line number entered. The current setting is displayed. page 25

References
Related commands
The page command affects the output from the following commands. assess on page 3-54 disp_cal_data on page 3-233 disp_cell_status on page 3-247 disp_dte on page 3-269 disp_gsm_cells on page 3-314 disp_link on page 3-326 disp_neighbor on page 3-343 disp_rtf_channel on page 3-375 disp_stat_prop on page 5-24 disp_traffic on page 3-394 state on page 3-515 disp_act_alarm on page 3-225 disp_cbch_state on page 3-237 disp_csfp on page 3-263 disp_enable_stat on page 5-12 disp_hdlc on page 3-317 disp_link_usage on page 3-328 disp_options on page 3-356 disp_rtf_path on page 3-381 disp_throttle on page 3-386 man on page 4-8 status_mode on page 3-530 disp_bss on page 3-229 disp_cell on page 3-241 disp_csfp_status on page 3-267 disp_equipment on page 3-283 disp_hopping on page 3-320 disp_mms_ts_usage on page 3-330 disp_processor on page 3-367 disp_stats on page 5-34 disp_trace_call on page 3-390 site_audit on page 3-507

68P02901W23-S

3-471 Nov 2009

query_audits

Chapter 3: Device/function related commands

query_audits

Description
The query_audits command performs two different functions. The first is to provide a list of all information for all audits for a specific device at the customer site. The second function provides a list of the audits in progress for a specific device at the customer site. {25002} The query_audits supports display of swap_type on TDM devices at location 0 (BSC or RXCDR). The short option displays the state of all audits for a specific device at a site. The long option displays the information for all of the audits for a specific device at the site. The information includes the state and schedule information. There are only three possible System Responses to a query_audits command: The display of results. A COMMAND REJECTED message, with the reason (for example, the device is not in the database). ERROR.

The ERROR response is followed by a display of the error description from the following list: Audit not available for unequipped devices. Audit can only be executed on expanded TDM configuration. Security level Supported by OMC-R GUI Command type Prerequisites 1 Yes A (no operator actions) An operator at the OMC-R must rlogin to a site before an audit can be performed. To audit a PCU site, the GPRS feature must be unrestricted.

Format
Syntax
query_audits <location> <audit_type> <device_name> <device_id1> <device_id2> <device_id3>

3-472

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Format

Input parameters
location Specifies the audit location: 0 or bsc 1 - 140 {27955A} pcu or pcu_0 audit_type Specifies the amount of information required. short long Displays all the audits in progress for a specific device at a customer site. Lists the state and schedule information for all the audits for the specified device. BSC BTS PCU

device_name The name that uniquely identifies the device. The valid device names are: BSP BTP DHP DRI GCLK GPROC KSW MSI TDM

The following device can be audited at a PCU site using this command: DPROC device_id1 First device identifier. The range of values is 0 to 99. device_id2 Second device identifier. The range of values is 0 to 99. device_id3 Third device identifier. The range of values is 0 to 99. MSI PSP

NOTE
Not all devices require all three device IDs.

68P02901W23-S

3-473 Nov 2009

Examples

Chapter 3: Device/function related commands

Examples
Example 1
In the following example, the query lists an audit that is idle for a KSW device at the BSC with ID 0 0 0: query_audits 0 long ksw 0 0 0 Where: 0 long ksw 0 0 0 is: location audit_type device_name device_id1 device_id2 device_id3

System response
Device: KSW Device id: 0 0 0 End Time: 00:00 Interval: 01:00 Device Audit: ON Idle/Active State: IDLE Cage Audit: ON

Start Time: 00:00 Audit Type: SAFE On/Off State:

Site Audit: ON

Device: KSW

Device id: 0 0 0 Interval: 00:15 Device Audit: ON Idle/Active State: IDLE Cage Audit: ON

Start Time: 02:00 End Time: 04:00 Audit Type: INT_LPBK On/Off State: Site Audit: ON

Example 2
The following example lists the audits in progress on the PCU MSI device: query_audits PCU short MSI 0 Where: PCU short MSI 0 is: location audit_type device_name device_id1

3-474

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Examples

System response
Device: MSI Device id: 0 0 0 Idle/Active State: IDLE Cage Audit: ON Device Audit: ON Site Audit: ON

Audit Type: SAFE On/Off State:

Example 3
The following example lists in long format, the audits in progress on the MSI device at the first PCU: query_audits PCU_0 long MSI 0 Where: PCU_0 long MSI 0 is: location (PCU site 0) audit_type device_name device_id1

System response
Device: MSI Device id: 0 0 0 End Time: 00:00 Interval: 00:10 Device audit:ON Idle/Active State:IDLE Cage audit:ON

Start Time: 00:00 Audit Type:SAFE

On/Off State: Site audit:ON

Example 4
{25002} The following example lists in long format, the audits in progress on the tdm device: query_audit 0 long tdm 0 Where: 0 long tdm 0 is: location audit_type device_name device_id1

68P02901W23-S

3-475 Nov 2009

References

Chapter 3: Device/function related commands

System Response
Device: TDM Device id : 0 0 0 End Time: 01:00 Interval: 00:00 Device Audit: ON Idle/Active State: IDLE Cage Audit: ON

Start Time: 01:00 Audit Type: SAFE On/Off State:

Site Audit: ON

Device: TDM

Device id : 0 0 0 End Time: 03:00 Interval: 00:00 Device Audit: ON Idle/Active State: IDLE Cage Audit: ON

Start Time: 03:00 On/Off State:

Audit Type: SWAP_TEST Site Audit: ON

References
Related commands
cage_audit on page 3-58 site_audit on page 3-507 chg_audit_sched on page 3-76 device_audit on page 3-210

3-476

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

reassign

Description
The reassign command changes the assignment of a child_dev device from its current parent_func to a new parent_func. For example, a DRI can be reassigned from one DHP , BTP , or BTF to another DHP , BTP , or BTF. The reassign command removes the device from service until the command is accepted. If the DRI is locked after it has been reassigned, the DRI is assigned to the least loaded GPROC when the DRI is unlocked. Security level Supported by OMC-R GUI Command type Prerequisites 4 Yes A (no operator actions) DRIs can only be assigned to GPROCs in the same cage as the DRI. A site device can be reassigned whether in Sysgen mode or not in Sysgen mode. All other devices must be reassigned when not in Sysgen mode. All GPROCs at the BSC (including the BSP) must be stable for at least five consecutive minutes since any GPROC has been transitioned. No BTS sites can be in the process of code loading.

Format
Syntax
reassign <location> <child_dev_name> <child_dev_id_1> <child_dev_id_2><child_dev_id_3> [<to>] <parent_func_name> <parent_func_id_1><parent_func_id_2> <parent_func_id_3>

68P02901W23-S

3-477 Nov 2009

Format

Chapter 3: Device/function related commands

Input parameters
location Specifies the location of the GPROC from which control of a DRI is to be moved. The values are: 0 or bsc 1 - 140 pcu, pcu_0 to pcu_2 child_name Literal that uniquely identifies the device. Current values are: CBL child_dev_id_1 The first child device identifier. Values are in the range 0 to 5. child_dev_id_2 The second child device identifier. Values are in the range 0 to 24. child_dev_id_3 The third child device identifier. Valid value is 0. to Optional text that can be entered to make the command more readable. parent_func_name The literal that defines where the device or function is reassigned. Current values are: BTP BTF DHP LCF Applies to: CBL, GSL, MTL, SITE Apply to DRIs DRI GSL MTL SITE BSC BTS PCU

parent_func_id_1 Values are dependent on the device or function type. parent_func_id_2 Values are dependent on the device or function type. parent_func_id_3 Values are dependent on the device or function type.

3-478

References

Chapter 3: Device/function related commands

References
Related information
The reassign command does not free the RTF associated with the BUSY-UNLOCKED DRI. The RTF remains associated with the DRI after reassignment to another GPROC. In circumstances where the reassignment fails due to catastrophic events, such as hardware failure, the RTF is freed, one transceiver is available and another is found. Where no standby DRIs are available and a BCCH RTF is free, a search is made for a DRI which is assigned to the GPROC, which has the least number of BCCH carrier-implementing DRIs assigned to it. The main reasons for failure to reassign a DRI: The destination BTP , BTF, or DHP has reached the maximum number of supportable DRIs. The DRI or GPROC type is not present or it is in an invalid state. The DRI is not in the same cage as the destination BTP , BTF, or DHP . The DRI is not configured due to catastrophic hardware failure.

Related commands
disp_equipment on page 3-283 disp_processor on page 3-367 equip on page 3-403 modify_value on page 3-456

3-482

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

reattempt_pl

Description
The reattempt_pl command causes the GCLK to reattempt phase lock. This is permitted only if the GCLK has previously failed to phase lock. Security level Supported by OMC-R GUI Command type Prerequisites 3 No A (no operator actions) This command is not allowed while in SYSGEN ON mode.

Format
Syntax
reattempt_pl <location> <gclk_id1>

Input parameters
location Specifies the location of the GPROC from which control of a DRI is to be moved: 0 or bsc 1 - 140 gclk_id The GCLK identifier. The valid values are 0 or 1. BSC BTS

Example
In this example, the GCLK 0 is forced to attempt phase lock. reattempt_pl bsc 0 Where: bsc 0 is: location gclk_id

68P02901W23-S

3-483 Nov 2009

References

Chapter 3: Device/function related commands

System response
COMMAND ACCEPTED

References
Related command
chg_element on page 3-106.

3-484

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

reset_device

Description
The reset_device command brings a device into service by locking and then unlocking the device. Additionally, a hard reset is performed if the device supports it. The following devices support soft resets: ABSS COMB GSL PCU AXCDR CSFP MMS RSL CAB DPROC MTL SITE {34321} CAGE EAS OML XBL CBL GBL OPL TDM CIC GCLK PATH

NOTE
The reset_device command supports the resetting of extension cabinets of type TCU_2, TCU_6, and HORIZONMACRO_EXT. No other extension cabinet types are supported. The following devices support hard reset: BSP BTP DHP DRI GPROC KSW MSI

NOTE
When a KSW is reset, all calls currently in progress are dropped. Normal call processing resumes when the KSW is brought back into service. When this command is entered where an MSI or MMS has an OML, a warning, and a verification request is presented. When this command is entered for an ABSS or AXCDR, a warning, and a verification request is presented. If the reset_device command is applied to an active GCLK, and the standby GCLK is phase locked, the system displays an additional warning message. The system also displays a warning message if the reset_device command is applied to the GCLK. This action swaps the GCLKs and can cause alarms on other devices. If the reset_site command is attempted while the system is initializing, the system displays a COMMAND REJECTED: System still initializing message. {22168} The BSS SW at a BSS enables enhanced capacity mode through reset_device command if the detected hardware contains only the master and redundant DSW2/DSWXs and not KSW/KSWX.

68P02901W23-S

3-485 Nov 2009

Format

Chapter 3: Device/function related commands

For remote transcoding BSC sites, CICs are not reset on a per-MMS basis when the BSC is operating in the dynamic allocation mode. Security level Supported by OMC-R GUI Command type Prerequisites Operator actions 2 Yes B (operator actions required) This command is invoked irrespective of whether the device is locked or unlocked. Respond to the verification prompt that is presented if this command is used to reset an MSI or MMS with an OML.

Format
General syntax
reset_device <location> <device_name> <device_id1> <device_id2> <device_id3>

Input parameters
location Specifies the location of the device to have a hard reset performed or toggled to the locked state: 0 or bsc 1 - 140 {27955A} pcu or pcu_0 device_name Literal that uniquely identifies the device. device_id1 First device identifier. This definition varies with each device. device_id2 Second device identifier. This definition varies with each device. device_id3 Third device identifier. This definition varies with each device. BSC BTS PCU

3-486

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Format

CIC syntax
A form of syntax is available for each method of specifying a CIC. The following CIC syntax applies to local transcoding: reset_device <location> CIC <cic_num1> reset_device <location> CIC <cic_num1> TO <cic_num2> reset_device <location> CIC <mms_id1> <mms_id2> reset_device <location> CIC <mms_id1> <mms_id2> <timeslot1> reset_device <location> CIC <mms_id1> <mms_id2> <timeslot1> TO <timeslot2> The following CIC syntax applies to remote transcoding: reset_device <location> CIC <cic_num1> reset_device <location> CIC <cic_num1> TO <cic_num2> reset_device <location> CIC <mms_id1> <mms_id2> reset_device <location> CIC <mms_id1> <mms_id2> <timeslot1> <group> reset_device <location> CIC <mms_id1> <mms_id2> <timeslot1> * reset_device <location> CIC <mms_id1> <mms_id2> <timeslot1> <group1> TO <timeslot2> <group2>

68P02901W23-S

3-487 Nov 2009

Examples

Chapter 3: Device/function related commands

mms_id2 Second MMS identifier, or last in a range if TO is used. timeslot1 First timeslot. timeslot2 Second timeslot, or last in a range if TO is used. group1 First group. group2 Second group. * Indicates all CICs on the MMSs specified in the timeslot, regardless of group.

Examples
Example 1
In this example, the MSI device is locked before the command is invoked. When the reset_device command is invoked, a hard reset of an MSI device with ID=1 at the BSC is performed. reset_device bsc MSI 1 Where: bsc MSI 1 is: location device_name dev_id

System response
COMMAND ACCEPTED

3-488

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Examples

Example 2
In this example, the GCLK is being reset. This example shows the warning message and the prompt the system displays whenever the GCLK is reset. reset_device 0 gclk 0 Where: 0 gclk 0 is: location device_name dev_id

System Response
This command will cause a swap of the GCLKs. This may cause alarms on other devices. Are you sure (y=yes,n=no)? y COMMAND ACCEPTED

Example 3
This example resets a range of CICs devices, specifying them by their MMS, TS, and group. reset_device bsc cic 2 1 3 1 TO 5 1 Where: BSC CIC 2 1 3 1 5 1 is: location CIC (device_name) mms_ id1 mms_ id2 timeslot 3 group 1 timeslot 5 group 1

System response
COMMAND ACCEPTED

68P02901W23-S

3-489 Nov 2009

Examples

Chapter 3: Device/function related commands

Example 4
{22168} This example enables enhanced capacity mode if the master and redundant DSW2/DSWXs are present. reset_device 0 TDM 1 0 0 Where: 0 TDM 1 0 0 is: location device_name dev_id1 dev_id2 dev_id3

System response
COMMAND ACCEPTED

Example 5
{22168} This example attempts to enable the enhanced capacity mode if the master and redundant DSW/DSWX are present. reset_device 0 TDM Where: 0 TDM is: location device_name

System response
COMMAND ACCEPTED

3-490

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

References

Example 6
{22168} This example attempts to enable the enhanced capacity mode if the KSW/KSWX is present. reset_device 0 TDM Where: 0 TDM is: location device_name

System response
COMMAND REJECTED: Wrong Hardware configuration detected in the site.

Example 7
{34321} This example attempts to reset a cage and display a confirmed command. A warning about the cage reset_device is displayed. reset_device bsc cage 1 0 Where: bsc cage 1 0 is: location device_name device_id1 device_id2

System response
CAGE 1 This will affect all devices in this CAGE and any associated

Extension CAGEs. Are you sure (y=yes,n=no)? yes COMMAND ACCEPTED

References
Related commands
ins_device on page 3-423 lock_device on page 3-429 unlock_device on page 3-581

68P02901W23-S

3-491 Nov 2009

reset_site

Chapter 3: Device/function related commands

reset_site

Description
The reset_site command selectively reboots available sites without rlogin. Typical scenarios for selective rebooting include the following: All sites including BSC. All sites excluding BSC. Multiple sites. Single site.

NOTE
The all_sites, all_bts, and list of site options are only allowed at the BSC and outside SYSGEN ON mode.

If a site other than the BSC is reset, the terminal being used to enter the command must be attached to that site GPROC to view the outputs generated during a reset. The reset occurs even if the terminal is not connected to the affected site.

CAUTION
Commands must be entered within 10 minutes after the MMI-RAM -> prompt displays. If a command is not entered, the system resets. Security level Supported by OMC-R GUI Command type Prerequisites Operator actions 3 Yes B (operator actions required) None Place the system in the SYSGEN ON mode before entering this command. The system does not permit resetting all_sites, all_bts or a list of site options in SYSGEN ON mode.

Format
Syntax
reset_site [<location>]

3-492

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Examples

Input parameter
location Specifies the sites to be reset. Valid values are: all_sites all_bts bsc bsc, 1 - 100 all sites including BSC all sites excluding BSC BSC (site 0) BSC and multiple sites (1 to 100). The bsc string must be entered as the first item in a list of sites. If bsc is included but is not the first item, the command is rejected. BTS PCU

1 - 140 {27955A} pcu or pcu_0

NOTE
When in SYSGEN ON mode, only the local site is reset. The command is rejected if 0 is entered for a BSC.

Verification messages
One of the following verification messages issues before execution. The specific message depends on the value of the location parameter. WARNING: Command will REBOOT the entire BSS. Are you sure (y=yes, n=no)? WARNING: Command will REBOOT all BTS sites. Are you sure (y=yes, n=no)? WARNING: Command will REBOOT the following site(s):18 21 24 Are you sure (y=yes, n=no)? WARNING: Command will REBOOT site 0 (BSC or RXCDR) Are you sure (y=yes, n=no)?

Examples
Example 1
In this example, a single site is reset: reset_site 2

68P02901W23-S

3-493 Nov 2009

Examples

Chapter 3: Device/function related commands

Where: 2

is: location

System response
WARNING: Command will REBOOT the following site(s): 2 Are you sure (y=yes, n=no)? y COMMAND ACCEPTED: WARNING REBOOT SITE: site 2 will reboot now!!

Example 2
In this example, all active BTS sites are reset: reset_site all_bts Where: all_bts is: location

System response
WARNING: Command will REBOOT all BTS sites. Are you sure (y=yes, n=no)?y SITE REBOOT STATUS ---- ------ -----5 7 9 10 11 15 20 25 30 40 OUT OF SERVICE: reset_site request is discarded RESET REQUEST IS IN PROGRESS RESET REQUEST IS IN PROGRESS OUT OF SERVICE: reset_site request is discarded OUT OF SERVICE: reset_site request is discarded OUT OF SERVICE: reset_site request is discarded RESET REQUEST IS IN PROGRESS RESET REQUEST IS IN PROGRESS RESET REQUEST IS IN PROGRESS RESET REQUEST IS IN PROGRESS

3-494

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

References

References
Related information
If the operator is logged in to a non-BSC site and attempts to reset other sites, the command aborts and the following error message displays: COMMAND REJECTED: current site is not authorized to reboot other site(s). to BSC. Log-in

The following command examples show various command entry formats and the location from where the commands must be entered: Command syntax reset_site all_sites reset_site all_bts reset_site bsc reset_site 15 5 25 0 2 reset_site 15, 5, 25, 0, 2 reset_site 1 reset_site bsc,21,17,3,0 reset_site Site BSC BSC BSC BSC BSC BSC or site 1 BSC BSC or local site

The MMI TTY displays, on success, one of the following statuses for each site requested: BSC (20 seconds) TIMEOUT: while waiting to receive ACK message from this site OUT OF SERVICE: reset_site request is discarded NOT EQUIPPED: reset_site request is discarded RESET REQUEST IS IN PROGRESS OUT OF RANGE: currently this site is not supported by CM Database

Related command
sysgen_mode on page 3-540

68P02901W23-S

3-495 Nov 2009

set_full_power

Chapter 3: Device/function related commands

set_full_power

Description
The set_full_power command turns the Full Power mode on or off for a single cell or all cells in a site. The Full Power mode directs a specified cell or all cells at a site to operate at the system's maximum power for a specified length of time. If a site is specified when the set_full_power command is entered, a status listing of all of the cells affected by the command are displayed. Security level Supported by OMC-R GUI Command type Prerequisites 4 No A (no operator actions) None

Format
Syntax
set_full_power [<cell_desc>] on <minutes> set_full_power [<cell_desc>] off set_full_power <location> on <minutes> set_full_power <location> off

Input parameters
cell_desc The GSM cell ID of the cell at which full power is to be set preceded by cell_number=. The format for the GSM cell ID depends on: The system being used (PGSM, EGSM, DCS1800, PCS1900). Whether the seven parameter GSM cell ID format or the four parameter GSM cell ID format has been enabled.

3-496

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Examples

The name of the cell created using the cell_name command is entered in place of the cell_number. When the cell name is entered, it must be preceded by cell_name= and be placed inside double quotation marks. location Specifies the location. 0 or bsc 1 - 140 on/off Select turning on and off Full Power mode. minutes The length of time for the specified cell or location to operate at full power. The valid range is 1 to 1440. BSC BTS

Examples
Example 1
The following example turns on the Full Power mode for GSM cell ID 5 4 3 2 1 31967 45988 for 45 minutes. The ID number is in the seven parameter format. set_full_power cell_number=5 4 3 2 1 31967 45988 on 45 Where: 5 4 3 2 1 31967 45988 on 45 is: cell_number turn Full Power mode on. length of time Full Power mode is turned on.

The example below shows the same cell number in four parameter format: set_full_power cell_number=543 21 31967 45988 on 45 Where: 543 21 31967 45988 on 45 is: cell_number turn Full Power mode on. length of time Full Power mode is turned on.

System response
COMMAND ACCEPTED

68P02901W23-S

3-497 Nov 2009

Examples

Chapter 3: Device/function related commands

Example 2
The following example turns off the Full Power mode for GSM cell ID 5 4 3 2 1 31967 45988: set_full_power cell_number=5 4 3 2 1 31967 45988 off Where: 5 4 3 2 1 31967 45988 off is: cell_number. 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: 5 on 45 is: location. turn Full Power mode on. length of time the Full Power mode is turned on.

System response
Full Power mode set ON for CELL ID = 5 4 3 2 1 31987 45977 Full Power mode set ON for CELL ID = 5 4 3 2 1 31987 45978

Example 4
The following example turns off the Full Power mode for all cells at site 5. set_full_power 5 off Where: 5 off is: location turn Full Power mode off.

3-498

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Examples

System response
Full Power mode set OFF for CELL ID = 5 4 3 2 1 31987 45977 Full Power mode set OFF for CELL ID = 5 4 3 2 1 31987 45978

Example 5
In this example, the affected cell is identified using the cell_name london-south: set_full_power cell_name=london-south on 45 Where: london-south on 45 is: cell_name turn Full Power mode on. length of time Full Power mode is turned on.

System response
COMMAND ACCEPTED

68P02901W23-S

3-499 Nov 2009

set_relay_contact

Chapter 3: Device/function related commands

set_relay_contact

Description
The set_relay_contact command specifies the relay state for an EAS device when the device is Busy-Unlocked. When equipping an EAS device, the physical wiring of each relay must be specified. These specifications describe whether the relay is open or closed when the relay is deactivated. All relays are deactivated on site initialization. Once the EAS device is Busy-Unlocked, the relay state can be controlled by use of the set_relay_contact command. Security level Supported by OMC-R GUI Command type Prerequisites 4 Yes A (no operator actions) 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 1 - 140 device_id Specifies the device ID of the specific PIX card associated with an EAS device: 0 to 7 0 to 15 InCell sites M-Cell sites BSC BTS

3-500

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Examples

relay_number Specifies the physical relay number to be set (1 to 4). contact_setting open or 0 closed or 1 open the relay close the relay

Examples
Example 1
For EAS 0 located at the BSC, set relay 4 to be closed circuit: set_relay_contact bsc 0 4 closed Where: bsc 0 4 closed is: location device_id relay_number 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: bsc 0 2 0 is: location device_id relay_number contact_setting

References
Related command
equip on page 3-403.

68P02901W23-S

3-501 Nov 2009

shutdown_device

Chapter 3: Device/function related commands

shutdown_device

Description
The shutdown_device command non-intrusively locks a specific device from further use. The following devices can be shut down with this command: CIC DRI MPRT MTL

The effect of this command is different for each type of specified device: For DRIs, the device is locked when the specified time expires. If there are no active calls on the DRI, the shutdown_device command locks the DRI immediately. If there are active calls, no new calls are allowed on the DRI, but no calls are handed off until the shutdown timer expires. At this time, the resource is freed, and calls are forced to move to another carrier in the same cell only. If there are no free carriers in the cell, the call is dropped. For MTLs, the time parameter is ignored and the device is locked immediately. For remote transcoding BSC sites, CICs are not shutdown on a per-MMS basis when the BSC is operating in the dynamic allocation mode. 3 Yes B (operator actions required) This command is not allowed while in SYSGEN ON mode. This command is only valid when the device is in the UNLOCKED state. This command has no effect on an already locked device. Unlock the device to be shutdown before entering this command.

Security level Supported by OMC-R GUI Command type Prerequisites

Operator actions

Format
General syntax
shutdown_device <location> <device_name> <device_id1> <device_id2> <device_id3><seconds> [wait <seconds>]

3-502

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Format

Input parameters
location Specifies the location of the device: 0 or bsc 1 - 140 device_name Literal that uniquely identifies the device. device_id1 First device identifier. This parameter is device dependent. device_id2 Second device identifier. This parameter is device dependent. device_id3 Third device identifier. This parameter is device dependent. seconds The time limit on the transition in seconds. This parameter is device dependent. The maximum time limit cannot exceed 900 seconds (15 minutes). wait The period the system should wait before blocking a busy device. BSC BTS

NOTE
The wait parameter is optional for all devices except the CIC. It is required for the CIC device.

CIC syntax
A form of syntax is available for each method of specifying a CIC. The following CIC syntax applies to local transcoding: shutdown_device <location> CIC <cic_num1> wait <seconds> shutdown_device <location> CIC <cic_num1> TO <cic_num2> wait <seconds> shutdown_device <location> CIC <mms_id1> <mms_id2> wait <seconds> shutdown_device <location> CIC <mms_id1> <mms_id2> <timeslot1> wait <seconds> shutdown_device <location> CIC <mms_id1> <mms_id2> <timeslot1> TO <timeslot2>wait <seconds>

68P02901W23-S

3-503 Nov 2009

Format

Chapter 3: Device/function related commands

The following CIC syntax applies to remote transcoding: shutdown_device <location> CIC <cic_num1> wait <seconds> shutdown_device <location> CIC <cic_num1> TO <cic_num2> wait <seconds> shutdown_device <location> CIC <mms_id1> <mms_id2> wait <seconds> shutdown_device <location> CIC <mms_id1> <mms_id2> <timeslot1> <group> wait <seconds> shutdown_device <location> CIC <mms_id1> <mms_id2> <timeslot1> * wait <seconds> shutdown_device <location> CIC <mms_id1> <mms_id2> <timeslot1> <group1> TO <timeslot2> <group2> wait <seconds>

3-504

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Examples

* Indicates all CICs on the MMSs specified in the timeslot, regardless of group. wait The period the system should wait before blocking a busy device.

NOTE
The wait parameter is always required for the CIC device.

Examples
Example 1
The following example locks a DRI with the IDs 1 2 at site 3 with a time limit of 20 seconds: shutdown_device 3 dri 1 2 0 20 Where: 3 dri 1 2 0 20 is: location device_name device_id1 device_id2 device_id3 seconds

System response
COMMAND ACCEPTED

68P02901W23-S

3-505 Nov 2009

References

Chapter 3: Device/function related commands

Example 2
This example shuts down a range of CICs (remote transcoding), specifying them by their MMS, TS, and group, and waiting 5 seconds before blocking a busy device. shutdown_device bsc cic 2 1 3 1 TO 5 1 wait 5 Where: BSC CIC 2 1 3 1 5 1 wait 5 is: location device_name First MMS id Second MMS id Timeslot 3 Group 1 Timeslot 5 Group 1 Mandatary for CIC wait period

System response
COMMAND ACCEPTED

References
Related commands
disp_equipment on page 3-283 state on page 3-515 equip on page 3-403 state on page 3-515 lock_device on page 3-429 unlock_device on page 3-581

3-506

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

site_audit

Description
The site_audit command initiates all audits for all devices at the customer site. It also allows the suspension or resumption of all audits at a specific site. If the GPRS feature is unrestricted, this command supports a GPRS PCU. Using the site_audit off command suspends all audits. Using the site_audit on command resumes all audits. There are only two possible System Responses to a site_audit command: The display of results. ERROR.

The ERROR response is followed by a display of the error description from the following list: Audit not available, audits turned off for site. Audits already turned on for this site. Audits already turned off for this site. SAP internal error.

NOTE
The error messages listed are specific to a SITE. Devices listed within the SITE can also generate messages specific to the device. For a list of these messages, see device_audit. Only one audit is run at a time.

Security level Supported by OMC-R GUI Command type Prerequisites

4 Yes A (no operator actions) An operator at the OMC-R must rlogin to a site before an audit can be performed. This command is not allowed while in SYSGEN ON mode.

Format
Syntax
site_audit <location> [<control>]

68P02901W23-S

3-507 Nov 2009

Examples

Chapter 3: Device/function related commands

Input parameters
location Specifies the audit location: 0 or bsc 1 - 140 {27955A} pcu or pcu_0 control Audit status on off Resumes all audits at a specific site. Suspends all audits at a specific site. BSC BTS PCU

Examples
Example 1
The following example executes audits for all devices at the BSC: site_audit 0 Where: 0 is: location

System response
Device: KSW Year: 1994 Device: KSW Year: 1994 Device: MSI Device id: 0 0 0 Month: 11 Day: 12 Result: Day: 12 Result: Hour: 1 Min: 22 Sec: 55 MSec: 10 AUDIT NOT SUPPORTED/AVAILABLE Hour: 1 Min: 22 Sec: 55 MSec: 30

Audit Type: SAFE Month: 11

Device id: 0 0 0, AUDIT NOT SUPPORTED/AVAILABLE

Audit Type: INT_LPBK

Device id: 1 0 0

3-508

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Examples

Year: 1994 Device: DRI Year: 1994 Device: DRI Year: 1994 Device: GCLK Year: 1994 Device: GPROC Year: 1994 Device: GPROC Year: 1994

Month: 11

Day: 12 Result: Day: 12 Result: Day: 12 Result: Day: 12 Result: Day: 12 Result: Day: 12 Result:

Hour: 1 PASS Hour: 1 PASS Hour: 1 PASS Hour: 1 PASS Hour: 1 PASS Hour: 1 ERROR

Min: 22

Sec: 55

MSec: 40

Audit Type: SAFE Month: 11

Device id: 0 1 0 Min: 22 Sec: 55 MSec: 40

Audit Type: SAFE Month: 11

Device id: 0 0 0 Min: 22 Sec:55 MSec: 100

Audit Type: SAFE Month: 11

Device id: 0 0 0 Min: 22 Sec: 55 MSec: 100

Audit Type: SAFE Month: 11

Device id: 0 0 0 Min: 22 Sec: 55 MSec: 280

Audit Type: SAFE Month: 11

Device id: 1 0 0 Min: 22 Sec: 55 MSec: 420

Audit Type: SAFE

ERROR: Audit not available for this device.

Example 2
The following example resumes all of the audits at site 0: site_audit 0 on Where: 0 on is: location control

System response
COMMAND ACCEPTED

Example 3
The following example suspends all of the audits at site 0: site_audit 0 off Where: 0 off is: location control

68P02901W23-S

3-509 Nov 2009

References

Chapter 3: Device/function related commands

System response
COMMAND ACCEPTED

References
Related information
The KSW internal loopback test interrupts calls. It should be run only during periods of low traffic. Calls interrupted by this command must be re-established after the audits are completed.

Related commands
cage_audit on page 3-58 query_audits on page 3-472 chg_audit_sched on page 3-76 device_audit on page 3-210

3-510

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

soft_reset

Description
The soft_reset command restarts the processes at one or more sites. An operator logged in to a BTS can restart only the local site. Only an operator logged in to the BSC can restart sites other than the local site. Security level Supported by OMC-R GUI Command type Prerequisites 4 Yes B (operator actions required) Sites must be installed to enter this command. The command is abandoned if any response other than y or Y is received. Respond to the verification prompt that is presented. This format is used to reset the local site only.

Operator actions

Format
Syntax
The following format is used to reset the local site: soft_reset The following format is used to restart processes at a specified PCU site: soft_reset pcu_n The following format is used to reset all of the sites from the BSC: soft_reset all The following format is used to reset one or more sites identified by site_id. Each site to be reset is separated by a space: soft_reset <site_id site_id site_id... site_id>

NOTE
After entering one of the commands, the operator is prompted with a warning and must enter y or Y (for yes) for the command to execute.

68P02901W23-S

3-511 Nov 2009

Format

Chapter 3: Device/function related commands

Input parameters
pcu_n This parameter specifies a PCU for reset: Where: {27955A} pcu or pcu_0 all This parameter specifies all of the sites at the BSC. site_id This parameter specifies the site to be reset. The range of values is 0 to 100. is: PCU site 0 (or the only PCU) at the BSC.

NOTE
Specifying 0 causes the BSC to reset.

Verification prompts
When the command is entered to reset multiple sites, the system displays one of the following verification prompts: Are you sure (y=yes, n=no)? WARNING: Command will RESTART all processes at all BTS sites. WARNING: Command will RESTART all processes at the following sites: <a listing of sites will follow> Are you sure (y=yes, n=no)? When the command is entered to reset a single site, the system displays the following verification prompt: WARNING: Command will RESTART all processes at site <site_id> Are you sure (y=yes, n=no)? If y is entered and the command is accepted for a single site, the following warning message displays: COMMAND ACCEPTED: WARNING REBOOT SITE: site (site_id) will reboot now!!!

3-512

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Examples

Status displays
One of the following statuses display for each requested site: Reboot status TIMEOUT OUT OF SERVICE NOT EQUIPPED RESET REQUEST IN PROGRESS Description The request timed out while waiting to receive ACK message from this site. The site is OOS. The reset_site request is discarded. The site is not equipped. The reset_site request is discarded. The site_reset request is in progress.

Examples
Example 1
In the following example, all of the sites are reset from the BSC: soft_reset all Where: all is: all sites in the BSS are specified.

System response
WARNING: Command will RESTART all processes at all BTS sites. Are you sure (y=yes, n=no)? y 1 2 3 4 OUT OF SERVICE RESET REQUEST IN PROGRESS RESET REQUEST IN PROGRESS NOT M-CELL

Example 2
In the following example sites 1, 4, and 9 are reset: soft_reset 1 4 9 Where: 149 is: sites to be reset.

68P02901W23-S

3-513 Nov 2009

Examples

Chapter 3: Device/function related commands

System response
WARNING: Command will RESTART all processes at the following sites: 1 4 9 Are you sure (y=yes, n=no)? y 1 4 9 RESET REQUEST IN PROGRESS NOT EQUIPPED TIMEOUT

3-514

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

state

Description
The state command displays the current status of devices or functions in the system, including when it last changed states. The length of time a device has been in its current state is also displayed. The state command can display specific devices or functions at one or all of the locations in the system based on operating states and identifiers. It can also display all the devices at all of the locations in the system by entering the state all or state all all command.

NOTE
The state command does not display the IAS device. The following devices can be investigated with this command: ABSS CAGE COMB {28351} ETH LAN PATH RSL TDM AXCDR CBL CSFP GCLK MMS PBUS RXCDR XBL BSP CELL DHP {28351} GDS MSI PCHN SBUS BTP CBUS DRI GPROC MTL {28351} PSI SITE CAB CIC EAS KSW OML {28351} PPROC TBUS

The following GPRS only devices can be investigated with this command if the GPRS feature is unrestricted: DPROC GSL Security level Supported by OMC-R GUI Command type Prerequisites GBL PCU 1 Yes A (no operator actions) Not available on an RXCDR. This command is not available while in SYSGEN ON mode. GDS PSP

68P02901W23-S

3-515 Nov 2009

Format

Chapter 3: Device/function related commands

Format
Syntax
state <location> [<filter>] [<dev/func_name> <dev/func id> <dev/func id> <dev/func id>] [<option1>] [option2]

Input parameters
location Specifies the location: 0 or bsc 1 - 140 all {27955A} pcu or pcu_0 filter Optional text string used to select devices or functions in a specific state. Valid values are: busy ins oos enabled-unlocked locked unlocked BSC BTS Specifies all sites PCU

NOTE
For a CIC or range of CICs, filter is not available.

dev/func name Literal that uniquely identifies the device or function. all is entered to specify all devices and functions. In a GPRS system, * is used instead of all. dev/func id First device/function identifier. This definition varies with each device or function. This value is not valid when all is specified for the dev/func argument. dev/func id Second device/function identifier. This definition varies with each device or function. This value is not valid when all is specified for the dev/func argument. dev/func id Third device/function identifier. This definition varies with each device or function. This value is not valid when all is specified for the dev/func argument. option1 option2

3-516

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Format

The option parameter displays the configuration tags and the device subtypes for the specified devices or functions. There are two options: Enter tags to display the configuration tags. Configuration tags are described in OMC-R

Online Help, Network Operations.

Enter subtypes to display the device subtypes.

The character string for the option can be entered in upper, lower, or mixed case letters. If both parameters are entered together, separate them with a space. When the tags option is entered and multiple devices or functions are specified, the displayed Related Function or Related Device column is replaced with the Config Tag (hex) column.

CIC syntax
A form of syntax is available for each method of specifying a CIC. The following CIC syntax applies to local transcoding: state <location> CIC <cic_num1> state <location> CIC <cic_num1> TO <cic_num2>

NOTE
The following three state commands are valid only in BC mode.

state <location> CIC <mms_id1> <mms_id2> state <location> CIC <mms_id1> <mms_id2> <timeslot1> state <location> CIC <mms_id1> <mms_id2> <timeslot1> TO <timeslot2>

NOTE
For remote transcoding BSC sites, the state command cannot be used for CICs when the BSC is operating in the dynamic allocation mode. The following CIC syntax applies to remote transcoding: state <location> CIC <cic_num1> state <location> CIC <cic_num1> TO <cic_num2>

68P02901W23-S

3-517 Nov 2009

Format

Chapter 3: Device/function related commands

NOTE
mms_id1, mms_id2, timeslot1, group1, and group2 are valid only in BC mode.

NOTE
For a CIC or range of CICs, neither filter nor option are available.

3-518

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Examples

Examples
Example 1
In this example, the status of the CAB device is displayed: state 7 cab 0 Where: 7 cab 0 is: location dev/func name dev/func ID

System response
STATUS INFORMATION: Device: CAB 0 0 0 Administration state: UNLOCKED Operational State: BUSY Reason code: NO REASON Time of last transition: Fri Apr 8 00:01:39 1994 Related Device/Function: None END OF STATUS REPORT

Example 2
In this example, the status of all of the KSW devices at the BSC is displayed using wildcards and the tags option: state bsc ksw * * * tags Where: bsc ksw * * * tags is: location dev/func name dev/func ID dev/func ID dev/func ID tags option

68P02901W23-S

3-519 Nov 2009

Examples

Chapter 3: Device/function related commands

System response
DEVICE STATUS INFORMATION FOR LOCATION 0: OPER STATES: D:Disabled E:Enabled U:Unlocked dd/mm B:Busy E:Equipped S:Shutdown Config Tag (hex) --------00000004 ADMIN STATES: L:Locked Device -----------KSW 0 0 0 State ----B-U

Last Transition Reason -----None hh:mm:ss ---------------14/01 10:36:57

Example 3
In this example, the status of all of the KSW devices at the BSC is displayed using wildcards: state bsc ksw * * * Where: bsc ksw * * * is: location 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 U:Unlocked B:Busy E:Equipped S:Shutdown Related Last Transition Device --------KSW 0 0 0 KSW 1 0 0 State ----B-U B-U Reason --------------NO REASON NO REASON dd/mm 14/01 14/01 ADMIN STATES: L:Locked

hh:mm:ss Function 10:36:57 None 08:02:31 None

---------------- ---------

3-520

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Examples

Example 4
In this example, the status of all devices and functions at location 7 are displayed: state 7 Where: 7 is: location

System response
DEVICE STATUS INFORMATION FOR LOCATION 7: OPER STATES: D:Disabled L:Locked E:Enabled U:Unlocked B:Busy E:Equipped hh:mm:ss 10:36:57 08:02:31 08:03:55 08:02:49 08:06:30 08:46:52 S:Shutdown Related Function None None RTF 0 0 0 None None None ADMIN STATES: 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 ... ... ... 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 REASON NO REASON NO REASON NO REASON NO REASON NO REASON B:Busy 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

Last Transition State Reason ----- -------------B-U B-U B-U B-U B-U D-U NO REASON NO REASON NO REASON NO REASON NO REASON RAM LINK dd/mm 14/01 14/01 14/01 14/01 14/01 16/01

---------------- ---------

FUNCTION STATUS INFORMATION FOR LOCATION 7: OPER STATES: E:Enabled Function --------RTF 0 0 0 State Reason ----- --------------B-E None ADMIN STATES: E:Equipped Last Transition dd/mm hh:mm:ss Related Device GPROC 0 0 0

---------------- ---------14/01 08:03:43

68P02901W23-S

3-521 Nov 2009

Examples

Chapter 3: Device/function related commands

Example 5
In this example, the status information for a single MSI, including device subtypes and configuration tags are displayed: state 0 msi 3 subtypes tags Where: 0 msi 3 subtypes tags is: location dev/func name dev/func ID option1 option2

System response
STATUS INFORMATION: Device: MSI 3 0 0 (MSI) Administration state: Reason code: NO REASON time of last transition: Related Device/Function: Config Tag (hex): END OF STATUS REPORT SAT JAN 5 12:55:18 1980 None LOCKED Operational state: ENABLED

00000006

Example 6
In this example, the status information for all MSIs at site 0, including device subtypes, are displayed: state 0 msi * subtypes Where: 0 msi * subtypes is: location dev/func name wildcard character for dev/func ID option1

3-522

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Examples

System response
DEVICE STATUS INFORMATION FOR LOCATION 0: OPER STATES: D:Disabled L:Locked Reason NO REASON NO REASON NO REASON NO REASON E:Enabled U:Unlocked B:Busy E:Equipped dd/mm 05/01 05/01 05/01 05/01 S:Shutdown Related Function -------None None None None hh:mm:ss 12:44:16 12:44:23 12:44:16 12:55:18 Last Transition Device MSI 0 0 0 (MSI) MSI 1 0 0 (XCDR) MSI 2 0 0 (MSI) MSI 3 0 0 (MSI) END OF STATUS REPORT E-L B-U B-U State B-U ------------ ------ ------------------------ ---------------

ADMIN STATES:

Example 7
In this example, the status information for an MMS at site 2 is displayed; there is a failed HDSL modem: state 2 mms * * * Where: 2 mms * * * is: location dev/func name wildcard character for dev/func ID option1 option2

68P02901W23-S

3-523 Nov 2009

Examples

Chapter 3: Device/function related commands

System response
DEVICE STATUS INFORMATION FOR LOCATION 2: OPER STATES: D:Disabled L:Locked Reason HDSL Modem bad or missing No Reason E:Enabled U:Unlocked B:Busy E:Equipped S:Shutdown Related Function None None hh:mm:ss 17:18:03 17:18:03 Last Transition Device MMS 0 0 0 MMS 0 1 0 State D-U B-U dd/mm 13/01 13/01 ADMIN STATES:

----------- ------ -------------------------- ---------------- --------

END OF STATUS REPORT

Example 8
This command displays the status of the CAGE device at PCU site 0: state pcu_0 cage 0 Where: pcu_0 cage 0 is: location dev/func name 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

3-524

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Examples

Example 9
This command displays the status of PCU site 1 at BSC 0: state 0 pcu 1 Where: 0 pcu 1 is: location device name 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
Displays the status of all MSIs at PCU site 0. state PCU_0 MSI * Where: PCU_0 MSI * is: location device name all MSIs

System response
DEVICE STATUS INFORMATION FOR LOCATION PCU site 0: OPER STATES: ADMIN STATES: Device MSI 1 0 0 MSI 2 0 0 D:Disabled L:Locked E:Enabled U:Unlocked B:Busy E:Equipped S:Shutdown Related Function None None hh:mm:ss 05:00:30 06:00:00 Last Transition State B-U B-U Reason NO REASON NO REASON dd/mm 03/01 03/01

END OF STATUS REPORT

68P02901W23-S

3-525 Nov 2009

Examples

Chapter 3: Device/function related commands

Example 11
{28351} Displays the status of all DPROC devices. state PCU DPROC * Where: PCU DPROC * is: location device name all DPROCs

System response
DEVICE STATUS INFORMATION FOR LOCATION 0: OPER STATES: D:Disabled L:Locked E:Enabled U:Unlocked B:Busy E:Equipped S:Shutdown

ADMIN STATES:

Last Transition Related Device ------------DPROC DPROC DPROC 1 0 0 2 0 0 3 0 0 State ----B-U B-U B-U Reason --------NO REASON NO REASON NO REASON dd/mm ----08/01 08/01 08/01 hh:mm:ss -------06:59:17 07:00:04 07:00:04 Function -------None None None

END OF STATUS REPORT

Example 11
{34321} Displays the status information of the cage device. state bsc cage 1 Where: bsc cage 1 is: location device name CAGE identifier

3-526

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

References

System Response
STATUS INFORMATION: Device: CAGE 1 0 0 Administration state: UNLOCKED Operational state: BUSY Reason code: NO REASON Time of last transition: Wed May 7 16:42:03 1980 Related Device/Function: None END OF STATUS REPORT

References
Transference of device status
When a GPROC card is equipped as a DHP , BSP , or BTP , all references to the state of the GPROC card should use the equipped name (such as DHP , BSP , or BTP). Table 3-33 lists the operational states.

Table 3-33
Operational states Disabled Enabled Busy

Operational states
Description FM has found the device unserviceable and has taken it out of service. FM has made the device available for use but it is not carrying traffic. Device is available for use and is carrying traffic.

Table 3-34 lists the administrative states.

Table 3-34
Admin state Locked Unlocked Equipped

Administrative states
Description The operator has taken the device out of service. The operator has made the device available for service. The device exists in the system.

Table 3-35 lists the device states.

68P02901W23-S

3-527 Nov 2009

References

Chapter 3: Device/function related commands

Table 3-35
Device state Not Equipped

Device states
Description The device does not exist in the system. FM and the operator find the device unserviceable. FM finds the device serviceable but the operator does not want it in service. FM finds the device unserviceable but the operator wants it in service. The system can periodically audit the device (the operator can force audits) to determine if the device is UNLOCKED. FM finds the device serviceable and the operator wants it in service. The device is in use. The device is between the LOCKED and UNLOCKED states. The system is waiting until all processes using the device have terminated before putting the device into the LOCKED state.

Disabled Locked Enabled Locked Disabled Unlocked Enabled Unlocked Busy Unlocked Shutting Down

NOTE
The remaining states LOCKED and NOT EQUIPPED in Table 3-35 cannot exist with any operational component. Table 3-36 lists the reason codes.

3-528

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

References

Table 3-36
Reason Codes

Reason codes
Value Explanation

Applicable to any device NO_REASON NO_INIT PARENT_OOS FAIL_ACT BAD_DB_CONFIG NO_GPROC INHIBITED WAIT FREED_FUNCTION 0 1 2 3 4 5 6 7 8 No reason. The device is not initialized. The parent device is out of service. The device failed to activate. The device is incorrectly configured in the database. There is no available GPROC to assign the device. The device is inhibited from being used. The device is waiting for an event. The function has been removed from the device.

Indicate progress made by BSC initializing a remote site NO_LINK ROM_TO_RAM RAM_LINK ROM_LINK Applicable to combiners COMBINER_CONTROLLER 14 Indicates which transceiver is controlling a particular combiner. 9 10 11 12 The RSL link to the BTS has not been established. The default link to BTS is active. BTS is in ROM. The BTS jumped to RAM without problems. The site informs RSL it is a ROM link.

Related commands
disp_equipment on page 3-283 unlock_device on page 3-581 equip on page 3-403 shutdown_device on page 3-502 lock_device on page 3-429

68P02901W23-S

3-529 Nov 2009

status_mode

Chapter 3: Device/function related commands

status_mode

Description
The status_mode command turns the state change notification on or off for the devices at a site that can be equipped. When the status mode is turned on, a notification containing both the old and the new status for a device displays immediately when a state change occurs. The status notification occurs only at the local MMI at which the command was invoked. Only the BSC can display status notification for remote sites. If the status mode is turned off, no notification is provided when a device experiences a state change. This command permits efficient adjustment of the current system configuration where necessary. If no mode is entered, the current alarm status mode displays. If the status_mode command is entered, the current status is displayed. One of the following status messages is displayed: Status notification is ON. Status notification is OFF. Site unequipped. Site unavailable. Status notification is already ON. Status notification is already OFF.

Multiple sites are disabled using the same command line by entering the site IDs separated by a space. All sites can be disabled by entering all for the location.

NOTE
Location all is only allowed at the BSC.

Security level Supported by OMC-R GUI Command type Prerequisites

3 Yes A (no operator actions) To display the status mode for the PCU, the GPRS feature must be unrestricted.

3-530

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Format

Format
Syntax
status_mode <location> [<location> ...<location>] [<mode>]

Input parameters
location Specifies the location of the device: 0 or bsc 1 - 140 {27955A} pcu or pcu_0 all mode Specifies the state change notification condition: on off state change notification on state change notification off BSC BTS PCU All sites

Examples
Example 1
This example turns on the CA device state-change notification at the BSC. When a device is locked, note the output due to the state change that has occurred. status_mode 0 on Where: 0 on is: location mode

System response
SITE ---0 STATUS ---------------Status notification turned ON

68P02901W23-S

3-531 Nov 2009

Examples

Chapter 3: Device/function related commands

Example 2
This example shows the command string required to display the status mode for an entire BSC. status_mode all Where: all is: 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 off the CA device state change notification at location 6. status_mode 6 off Where: 6 off is: location mode

System response
SITE ---0 STATUS ---------------Status notification turned OFF

3-532

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

References

Example 4
This example shows the effect of the status mode being turned on when the state of a device changes. In this example, the msi 1 0 0 is being locked. lock_device bsc msi 1 0 0 Where: bsc msi 1 0 0 is: location device_name device_id1 device_id2 device_id3

System response
* STATUS NOTIFICATION -- Tag(hex): * <entity type & ID> (<subtype>) * -- Old State: * -- New State: <config_tag) <site> Time: <time>

Site:

* -- Transition Number:

This output occurs due to the state change of the device.

References
Related information
Refer to the Maintenance Information: Alarm Handling at the OMC-R (68P02901W26) for a description of the displayed alarm message.

68P02901W23-S

3-533 Nov 2009

store_cal_data

Chapter 3: Device/function related commands

store_cal_data

Description
The store_cal_data command enables storing of the transceiver calibration data of a BTS. Transceiver calibration data storage for all sites in the current BSS can be enabled by using all for the location value.

NOTE
This command only works for DRIs that are in busy_unlocked state. Make sure that all DRIs are unlocked before using the store_cal_data command to store the transceiver calibration data.

Security level Supported by OMC-R GUI Command type Prerequisites

3 No A (no operator actions) This command is not allowed while in SYSGEN ON mode.

NOTE
Enter this command at the BSC only. This command is unavailable at a BTS site. Contact the OMC-R for help.

Format
Syntax
store_cal_data <location>

3-534

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Examples

Input parameter
location Specifies the site for storing transceiver calibration data: 1 - 140 all BTS All sites in the current BSS.

Examples
Example 1
The following example stores transceiver calibration data at the BSC: store_cal_data 0 Where: 0 is: 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: all is: 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

68P02901W23-S

3-535 Nov 2009

References

Chapter 3: Device/function related commands

References
Related commands
clear_cal_data on page 3-169 disp_cal_data on page 3-233

3-536

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

swap_devices

Description
The swap_devices command swaps the specified standby device with the specified active device. The following devices can be swapped by this command: BTP COMB GCLK LAN TDM

NOTE
Swapping a BTP device causes a site reset. The following restrictions apply: The standby and active devices must be the same type. The standby device must be in the UNLOCKED state. The CIC device cannot be locked by location when the BSS is operating in dynamic mode. In the dynamic mode, a CIC can be locked by specifying the CIC ID only. For a COMB device, this command swaps the active links and the controlling DRIs. The system does not permit swapping between two GCLKs that are phase locking. 4 Yes B (operator actions required) This command is not allowed while in SYSGEN ON mode. Unlock the standby device to be swapped.

Security level Supported by OMC-R GUI Command type Prerequisites Operator actions

Format
Syntax
swap_devices <location> <active_device_name> [<std_device_id1>]

68P02901W23-S

3-537 Nov 2009

Examples

Chapter 3: Device/function related commands

Input parameters
location Specifies the location of the device: 0 or bsc 1 - 140 active_device_name Literal that identifies the active device. std_device_id1 Standby device identifier; required only for the COMB. BSC BTS

Examples
Example 1
This example swaps the active comb with the standby comb 0 at BTS site 1. swap_devices 1 comb 0 Where: 1 comb 0 is: location active_device_name 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: 0 lan is: location active_device_name

3-538

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

References

System response
COMMAND ACCEPTED

References
Related commands
disp_equipment on page 3-283 state on page 3-515 equip on page 3-403 unequip on page 3-570 lock_device on page 3-429 unlock_device on page 3-581

68P02901W23-S

3-539 Nov 2009

sysgen_mode

Chapter 3: Device/function related commands

sysgen_mode

Description
The sysgen_mode command places the system in the SYSGEN ON or SYSGEN OFF mode. This command also displays the current mode of operation.

NOTE
This command is not intended for general use at the OMC-R. The current SYSGEN mode and the SYSGEN mode after the next restart can be displayed by entering the sysgen_mode command without input parameters. The system is placed in the SYSGEN ON mode from the SYSGEN OFF mode by entering the sysgen_mode on command string then resetting the site. The system is placed in the SYSGEN OFF mode from the SYSGEN ON mode by entering the sysgen_mode off command string then resetting the site. The sysgen_mode off command is rejected if: An EGPRS RTF has a valid FHI in baseband hopping and the master cabinet at the site is not a Horizon II macro. An EGPRS RTF has the same FHI as a non-EGPRS RTF in a baseband hopping system.

Sysgen_mode off performs a check on GSM HR capability. An attempt to exit Sysgen with GSM Half Rate enabled but with CIC validation disabled for an AXCDR generates a warning indicating that AXCDR CIC validation must be enabled for AMR/GSM HR.

SYSGEN OFF mode

When the system is in the SYSGEN OFF mode, the database is verified each time a change is made. The checksum is then calculated, and the database is broadcast to the other sites. When the sysgen_mode off command is entered, the security level resets to Level 1 for all operators.

3-540

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Format

SYSGEN ON mode
When the system is in the SYSGEN ON mode, the database is not checked when a change is made. The checksum is not recalculated and the database is not broadcast to the other sites. When the sysgen_mode on command is entered, the site must be reinitialized to place the system in the SYSGEN ON mode. Refer to the reset_site command. Command execution can occur without system delays. There is no interaction with other processes.

CAUTION
After a system reset a command must be entered within 10 minutes after the MMI-RAM-> prompt is presented. If a command is not entered, the system resets.

Initial SYSGEN mode

The system can be placed in the initial SYSGEN mode by placing the system in the SYSGEN ON mode after the database has been deleted using the clear_database command. Security level Supported by OMC-R GUI Command type Prerequisites Operator actions 4 No B (operator actions required) None Reset the system to change the SYSGEN mode after entering this command.

Format
Syntax
sysgen_mode [<value>]

Input parameter
value Specifies the status of SYSGEN: on off Places the system in the SYSGEN ON mode. Places the system in the SYSGEN OFF mode.

68P02901W23-S

3-541 Nov 2009

Examples

Chapter 3: Device/function related commands

Examples
Example 1
In this example, the system is placed in the SYSGEN OFF mode of operation: sysgen_mode off Where: off is: the SYSGEN mode in which the system is placed after the next reinitialization.

System response
******* VERIFYING DATABASE BEFORE COMPLETING SYSGEN ******* Frequency hopping verification in progress. SITE 0 Verification. DB Verification passed. COMMAND ACCEPTED.

Example 2
In this example, the system is placed in the SYSGEN ON mode of operation: sysgen_mode on Where: on is: the SYSGEN mode in which the system is placed after the next reinitialization.

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

Example 3
In the following example, the current SYSGEN mode is displayed and the mode into which the system is placed after the next restart. sysgen_mode

3-542

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Examples

System response
Current Sysgen mode: ON Sysgen mode upon next restart: OFF

Example 4
This example attempts to turn off SYSGEN mode with GSM Half Rate enabled but with CIC validation disabled for an AXCDR. sysgen_mode off

System response
WARNING: AXCDR CIC validation must be enabled for AMR or GSM HR.

Example 5
In this example SYSGEN mode is turned off when PCU 0 does not have enough GDS resources, and PCU 1 does not have enough PMC resources for res_gprs_pdchs and switch_gprs_pdchs. sysgen_mode off

System response
********** VERIFYING DATABASE BEFORE COMPLETING SYSGEN ********** PCU 0: ----------------------------------------------------------------------WARNING: Insufficient GDS resources available for all PDTCHs on the PCU. PCU 1: ----------------------------------------------------------------------WARNING: Insufficient PMC resources available for all PDTCHs on the PCU. Sysgen OFF warnings were detected. If accepted, this database may cause some loss of service. Still leave sysgen mode? Are you sure (y=yes,n=no)? y

Example 6
In this example SYSGEN mode is turned off when PCU 0 does not have enough GDS resources and PCU 1 does not have enough PMC resources for res_ts_less_one_carrier and sw_ts_less_one_carrier. sysgen_mode off

68P02901W23-S

3-543 Nov 2009

Database errors

Chapter 3: Device/function related commands

System response
********** VERIFYING DATABASE BEFORE COMPLETING SYSGEN ********** PCU 0: ----------------------------------------------------------------------WARNING: Insufficient GDS resources avail for all PDs on the PCU (less one carrier). PCU 1: ----------------------------------------------------------------------WARNING: Insufficient PMC resources avail for all PDs on the PCU (less one carrier). Sysgen OFF warnings were detected. If accepted, this database may cause some loss of service. Still leave sysgen mode? Are you sure (y=yes,n=no)? y

Database errors
A database error causes the sysgen_mode off command to be rejected and a database is not created; an error message displays. All error messages are preceded with the DB VERIFY ERROR: string.

General database errors

The BSC MUST have an OMF equipped if bsc_type is 2. bsc_type MUST be zero for site type RXCDR. At least one LCF MUST be equipped at site 0 when bsc_type is not 0. At least one LCF MUST have max_mtls greater than zero for this site type. The BSC MUST have at least one BSP equipped. Site <site_id> does note have a BTP equipped. Site <site_id> does not have a GCLK equipped. RRSM Timer,8 value at site <site_id> must be less than SSM Timer,10. No slots available on BSP. No BSP found in CM database. Requested bsc_type not supported. No slots available on LCF. No LCF found in CM database. There is no default RSL equipped to BTS site <site_id> on any PATH. INVALID DATA IN BIN <bin>: decision_1_dl_rxqual_av_h error in cell id

3-544

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Database errors

<cell_number> INVALID DATA IN BIN <bin>: decision_1_dl_rxlev_av_h error in cell id <cell_number> INVALID DATA IN BIN <bin>: decision_1_dl_rxlev_av_ih in cell id <cell_number> INVALID DATA IN BIN <bin>: decision_1_p_bgt_rxlev_av_h in cell id <cell_number> (rxlev_dl_ho) INVALID DATA IN BIN <bin>: decision_1_p_bgt_rxlev_av_h in cell id <cell_number> (surround_cell) INVALID DATA IN BIN <bin>: decision_1_dl_rxqual_av_p in cell id <cell_number> INVALID DATA IN BIN <bin>: decision_1_dl_rxlev_av_p in cell id <cell_number> INVALID DATA IN BIN <bin>: decision_1_ncell_rxlev_av_h_calc in cell id <cell_number> INVALID DATA IN BIN <bin>: decision_1_tim_adv_av_alg in cell id <cell_number> INVALID DATA IN BIN <bin>: decision_1_ul_rxqual_av_h in cell id <cell_number> INVALID DATA IN BIN <bin>: decision_1_ul_rxlev_av_h in cell id <cell_number> INVALID DATA IN BIN <bin>: decision_1_ul_rxlev_av_ih in cell id <cell_number> INVALID DATA IN BIN <bin>: decision_1_ul_rxqual_av_p in cell id <cell_number> INVALID DATA IN BIN <bin>: decision_1_ul_rxlev_av_p in cell id <cell_number>

General hopping errors

Can't have baseband and synthesizer hopping_support values at same site. BCCH frequency cannot have BCCH timeslots which hop. cell = <cell_number> frequency = <frequency> timeslot = <timeslot> Too many frequencies were defined for the frequency range Unable to format cell-channel description with this many frequencies Cell: <cell_number> defined> Number Freqs defined: <number of frequencies Max Freqs allowed: <maximum number of frequencies allowed>

Timeslot: <timeslot> for fhi: <fhi> doesn't hop. Thus, arfcn: <arfcn> can't appear in the MA for the same TS for arfcn: <arfcn> FHI: <fhi> of carrier: <carrier> and FHI: <fhi> of carrier: <carrier number> in timeslot: <timeslot> in cell: <cell_number> have intersecting frequencies in its mobile allocation. (frequency: <frequency>) The NON-BCCH carrier with arfcn: <arfcn> in cell: <cell_number> has the BCCH frequency in its mobile allocation for FHI timeslot: <timeslot>. site: <site_id> site: <site_id> ... cell: <cell_number> cell: <cell_number> hopping_support: <hopping_support> hopping_support: <hopping_support>

68P02901W23-S

3-545 Nov 2009

Database warnings

Chapter 3: Device/function related commands

Synthesizer hopping errors

The BCCH carrier isn't in any MA. Hopping timeslots exist in

cell <cell_number> but not on the BCCH carrier. All timeslots for BCCH carrier (frequency): <bcch_freq> set to non-hopping (255) NON-BCCH TS's on BCCH carrier must have same FHI as NON-BCCH TS's when hopping through BCCH frequency. bcch_freq: <bcch_freq> FHI values must be identical within the BCCH carrier timeslots. For Cell: <cell_number> Timeslot: <timeslot> with FHI: <fhi > mismatches Timeslot:<timeslot> with FHI: <fhi> There are fewer frequencies than carriers for fhi: <fhi> in timeslot:<timeslot>. The number of frequencies is: <number of frequencies>. The number of carriers is: <number of carriers>. fhi_ts: <fhi_ts>

Baseband hopping errors

arfcn: <arfcn> should be in the mobile allocation for fhi: <fhi> <timeslot> EGPRS and non-EGPRS carriers cannot have the same FHI Within a cell, all carriers having their arfcns in the same MA must have identical fhi values for the same timeslot. Mismatch between carrier arfcn: <arfcn> and carrier arfcn: <arfcn> to any carrier. ts: <timeslot> fhi_value:<fhi> ts: <timeslot> fhi_value:<fhi> timeslot:

The arfcn: <arfcn> in the MA of carrier: <carrier number> has not been assigned ts: <timeslot> fhi: <fhi> fhi: <fhi> cell: <cell_number> The arfcn of the carrier must be part of the MA for its FHI. carrier arfcn: <arfcn> timeslot: <timeslot> Master cabinet must be Horizonmacro2 for EGPRS to hop in baseband hopping

Database warnings
A database warning causes the sysgen_mode off command to be rejected and a database is not created; a warning message is displayed. All warning messages are preceded with the DB VERIFY WARNING: string.

3-546

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

References

General database warnings

Maximum MTLs should be the same value for all BSPs. sd_load is zero for all carriers in local cell <cell number>. max_dris of Primary and Redundant BTPs do not match at site <site number>. Site <site number> is bts_type 1 but does not have a DHP equipped. Number of functions exceeds number of POOL GPROCs at site <site number>. This will cause one or more LCFs or OMFs to not come in service.

References
Related information
When exiting the SYSGEN mode or completion of a database using the SYSGEN or DATAGEN tools, the database is verified for sanity. If errors are detected, a database error or database warning is generated.

Related commands
chg_level on page 3-142 disp_level on page 3-325 reset_site on page 3-492

68P02901W23-S

3-547 Nov 2009

time_stamp

Chapter 3: Device/function related commands

time_stamp

Description
The time_stamp command enables or disables the time-stamping function. This function adds a time and date before the MMI command prompt. Security level Supported by OMC-R GUI Command type Prerequisites 1 No A (no operator actions) None

Format
Syntax
time_stamp <value>

Input parameter
value Specifies the status of time_stamp: on off Turns time_stamp on. Turns time_stamp off.

Examples
Example 1
In this example, the time stamp is turned on: time_stamp on

System response
[11/12/93 01:03:30] MMI-RAM 0115->

3-548

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

References

Example 2
In this example, the time stamp is turned off: time_stamp off

System response
MMI-RAM 0115->

References
Related commands
chg_time on page 3-158 chg_throttle on page 3-156

68P02901W23-S

3-549 Nov 2009

trace_call

Chapter 3: Device/function related commands

trace_call

Description
The trace_call command creates a Call/GPRS Trace instance in the BSS. An instance is a set of criteria that defines a trace. A maximum of 16 instances can exist on a BSS. The number of call trace instances that can be created using the trace_call command is affected by the percentage of traces reserved exclusively for MSC initiated traces. This percentage is specified using the call_trace_options parameter. For example, if 50% of the traces are reserved for initiation from the MSC, a maximum of eight instances can be created using the trace_call command. The trace_call command is primarily intended for tracing calls and GPRS data transfer with unspecified subscriber and equipment IDs. With limitations, it can trace subscribers and equipment. Due to GSM architectural restraints, however, the BSS does not have complete knowledge of subscriber or equipment IDs. Therefore, this command cannot reliably trace by subscriber or equipment. For the exact restraints, refer to the Notes for the call selector prompt in the Related Information subsection.

Maximum number of traces

Traces can be initiated from the MSC or when a call meets the criteria specified in an instance on the BSS. The maximum number of traces that can be run simultaneously is 16 per LCF, including MSC initiated traces. MSC initiated traces are run immediately because the trace is for a call that is already in progress. An MSC initiated trace affects the capacity of the LCF where the call originated. This is because the same LCF controls a call for the duration of the call even if the call is handed over to a cell controlled by another LCF. For example, if there are 15 traces currently running on an LCF and the MSC initiates a trace for a call that originated on the same LCF, no additional traces could run on that LCF even if the call is handed over to a cell controlled by another LCF.

Call trace data

A basic set of call trace data is included in the reports generated by this command. Any combination of Abis, BSSMAP , DTAP , MS_POWER_CONTROL, RR, SS GSM call data types and LCC, BSSG, RLC_MAC, PC&CS, PMRs, RLC_MAC_PDAKs, GPRS data transfer types can also be specified for inclusion in the basic call trace data. The GPRS Trace optional feature must be unrestricted to trace GPRS call criteria.

3-550

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Format

OMC-R reporting
Each set of call trace criteria created using the trace_call command is reported to the OMC-R. This permits the OMC-R to determine when the maximum number of traces has been reached in the BSS. Use of the trace_call command impacts OML, BSS, or OMC-R performance. If a large number of call traces are initiated on multiple BSSs connected to a single OMC-R, the OML traffic increases. This increase, together with normal OML traffic (such as alarms and uploads/downloads), can cause some call trace data for the OMC-R to be lost. The trace_call command creates a set of trace call criteria in the BSS that can trigger traces on calls. Reports generated by this command include a set of basic call trace data. Any combination of GSM and GPRS data can also be specified for inclusion in the basic call trace data. After the command is entered, the system displays a series of prompts. The prompted parameters are described under Related information at the end of this section. Implementing trace_call increases the amount of data passing over the OML. This feature impacts OML, BSS, or OMC-R performance. For example, a large number of call traces initiated on multiple BSSs connected to a single OMC-R can increase the OML traffic. This increase, together with normal OML traffic (such as alarms and uploads/downloads), can cause some call_trace data to be lost. Call Trace Flow Control reduces, and can eliminate, this from occurring. Refer to the ct_flow_control_hi_level and ct_flow_control_lo_level parameters for more information. Security level Supported by OMC-R GUI Command type Prerequisites 3 No A (no operator actions) This command is not allowed in SYSGEN mode. GPRS Trace feature must be unrestricted to trace GPRS data transfer.

Format
Syntax
trace_call <location> [rtf <id1> <id2> <id3>] trace_call <cell_desc> trace_call all

68P02901W23-S

3-551 Nov 2009

Format

Chapter 3: Device/function related commands

Input parameters
location The location of the equipment: 1 - 140 all BTS all locations

NOTE
If the location = all, do not use rtf in the command syntax.

rtf The name for the radio transmit function. This is the only valid input. id1 The first function identifier. id2 The second function identifier. id3 The third function identifier. cell_desc GSM cell ID of the cell to be traced, preceded by cell_number=. The format for the GSM cell ID depends on: The system used (PGSM, EGSM, DCS1800, PCS1900) Whether the seven parameter GSM cell ID format or the four parameter GSM cell ID format has been enabled.

The name of the cell created using the cell_name command can be entered in place of the cell_number. When the cell name is entered, it must be placed inside double quotation marks, and be preceded by cell_name=.

NOTE
The system accepts only one of the following inputs: location, cell_number or cell_name. Do not combine these parameters in a single command.

3-552

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Examples

Examples
Refer to the Related information subsection for a description of the prompts displayed in the following examples.

Example 1
This example shows a BSS-wide trace to capture multiple data record types, including BASIC, BSSMAP , DTAP , and Abis data, where: Any trigger event can start a trace, including a call already in progress. The system traces any call identified by SCCP number 747B6C (hexadecimal). Only one call is traced. Output is directed to the MMI. trace_call all Where: all is: location

System response
Enter trigger event: all Enter additional data types (Basic is always included): bssmap, dtap, abis Collect during handover only?: no Enter call selector type and value: sccp=747B6Ch Trigger enabled time: Enter total number of calls to be traced per LCF/PRP: 1 Enter destination for trace data: mmi

COMMAND ACCEPTED

NOTE
If the response to the Enter additional data types prompt includes more than one data type, each type must be separated by a comma and a space, as shown in Example 1.

68P02901W23-S

3-553 Nov 2009

Examples

Chapter 3: Device/function related commands

Example 2
This example shows a trace on a specified MS whenever it hands over into the specified cell, where: The tracing continues until stopped by an operator. This trace collects BASIC data only. The system traces any call involving the mobile unit identified by a specific IMEISV number. Tracing discontinues if the call leaves the scope. Output is directed to the MMI and the OMC-R. trace_call cell_name=Trafalgar_Square Where: Trafalgar_Square is: cell_name

System response
Enter trigger event: handover Enter additional data types (Basic is always included): Enter call selector type and value: imeisv=0010167890123021 Trigger enabled time: Enter total number of calls to be traced per LCF/PRP: Trace calls beyond scope?: no Enter destination for trace data: both

COMMAND ACCEPTED

Example 3
This example shows a trace on BTS location 2, RTF 0 0, where: Any trigger event can start a trace, including a call already in progress. This trace collects BASIC and MS_POWER data only. The system traces every fourth call. No more that two calls are traced simultaneously. The tracing continues until eleven calls have been traced. Tracing discontinues if the call leaves the scope. Output is directed to the OMC-R.

3-554

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Examples

trace_call 2 rtf 0 0 Where: 2 rtf 0 0 is: BTS location rtf id1 id2

System response
Enter trigger event: all Enter additional data types (Basic is always included): ms_power Enter call selector type and value: nth=4 Enter maximum simultaneous calls traced per LCF: 2 Trigger enabled time: Enter total number of calls to be traced per LCF/PRP: 11 Trace calls beyond scope?: Enter destination for trace data: omc

COMMAND ACCEPTED

Example 4
This example shows a trace on RTF 0 1 at BTS site 4, where: Any trigger event can start a trace, including a call already in progress. This trace collects BASIC and RSS data only. Once a call triggers a trace, all trace data of the specified types is collected. The RSS reports Measurement Report data every eight intervals (one interval = 480 ms). The system traces every seventh call. No more that four calls are traced simultaneously. Tracing is enabled at 9:00 pm. Tracing is disabled at 10:00 pm. Tracing continues if the call leaves the scope. Output is directed to the MMI by default.

68P02901W23-S

3-555 Nov 2009

Examples

Chapter 3: Device/function related commands

trace_call 4 rtf 0 1 Where: 4 rtf 0 1 is: BTS location rtf id1 id2

System response
Enter trigger event: all Enter additional data types (Basic is always included): rss Collect during handover only?: no Enter Measurement Report interval (X480ms): 8 Enter call selector type and value: nth=7 Enter maximum simultaneous calls traced per LCF: 4 Trigger enabled time: 21 00 Trigger disabled time: 22 00 Enter total number of calls to be traced per LCF/PRP: Trace calls beyond scope?: yes Enter destination for trace data:

COMMAND ACCEPTED

NOTE
The Enter Measurement Report interval (X480ms) prompt displays only if the operator enters no to the previous prompt.

Example 5
In this example, a BSS-wide trace is set on the specified IMSI for GPRS Data Transfer or GSM calls capturing all types of data. The trace can only be triggered between 8:00 pm to 10:00 pm each day, and continues until deleted by the operator. There is no limit on the number of calls that are traced. Calls are not traced beyond scope. Trace reports are sent to OMC-R. trace call

3-556

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Examples

System response
Enter trigger event: combined_all Enter additional data types(Basic is included): combined_all Collect during handover only?: no Enter Measurement Report interval (x480ms): 20 Enter call selector type and value: imsi=001010000000911 Trigger enabled time: 20 00 Trigger disable time: 22 00 Enter total number of traces to be traced per LCF/PRP: Trace calls beyond scope?: Enter destination for trace data: omc

COMMAND ACCEPTED

Example 6
This example attempts to create a GPRS trace when GPRS Trace option is restricted. trace_call

System response
Enter trigger event: handover gprs Enter additional data types(Basic is included): combined_all Collect during handover only?: no Enter Measurement Report interval (x480ms): 20 Enter call selector type and value: imsi=001010000000911 Trigger enabled time: 20 00 Trigger disable time: 22 00 Enter total number of traces to be traced per LCF/PRP: Trace calls beyond scope?: Enter destination for trace data: omc

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

68P02901W23-S

3-557 Nov 2009

References

Chapter 3: Device/function related commands

References
Related information
Prompts preceded by an asterisk (*) Table 3-37 are only displayed under the conditions described in the Notes column.

Table 3-37

trace_call prompts and values for a GSM Trace and GPRS Trace.
Valid range or values setup handover all gprs combined_all Default all Notes If the trigger event is specified as: all, it refers to a GSM Trace (handover and setup). gprs, it refers to a GPRS Data Transfer. combined_all, it refers to GPRS and GSM Trace.

Prompt Enter trigger event:

Any or all of the trigger event types can be selected. Enter additional data types (Basic is included): Only basic Abis, data is BSSMAP, sent DTAP, MS_power, RR, RSS, all, LLC, BSSGP, RLC_MAC, PMRs, RLC_MAC_PDAKs, GPRS_all, PC&CS, Combined_all. If the trigger_event is specified as setup, handover or all, the valid values for data types are DTAP, BSSMAP, Abis, RR, RSS, MS_power and all. If nothing is entered then the record type is basic. If trigger_event is specified as gprs the valid values for data type are LLC, BSSGP, RLC_MAC, PMRs, RLC_MAC_PDAKs, PC&CS and GPRS_all. The Combined_all data type can only be specified if the trigger_event is Combined_all or gprs with setup, handover or all. If RSS is entered as a data type, the system prompts for an additional parameter, the Measurement Report Interval. The RSS Data displays Reported 3G Neighbor Info when it is available. Continued

3-558

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

References

Table 3-37 (Continued)

trace_call prompts and values for a GSM Trace and GPRS Trace.
Valid range or values yes (1) no (0) Not applicable for GPRS Trace criteria.

Prompt * Collect during handover only?:

Default No

Notes The prompt is displayed only if the RSS, Abis and/or MS_Power data types are specified, and the trigger event is setup, handover, all or combined_all. no or 0 means that once a call triggers a trace, all trace data of the specified types is collected. yes or 1 means that the RSS, Abis, and/or MS power data, if specified, is collected immediately before and after a handover has occurred. The number of messages collected is determined by trace_msgs_before_ho and trace_msgs_after_ho data base parameters. This parameter specifies the number of 480 ms periods to wait before collecting another measurement report. The prompt is displayed if the data type specified is: RSS and the operator did not specify collect during handover only. PC&CS. (The report interval applies to UL/DL Measurement Data.) PMRs. Specifies roughly the rate at which the network requests PMRs from a mobile in NC1 mode. The specified rate is mapped to the valid reporting period rate as defined in 3GPP 44.060 [2] Continued

* Enter Measurement Report interval (x480ms):

Any value between 1 and 255

10 (4.8 seconds)

68P02901W23-S

3-559 Nov 2009

References

Chapter 3: Device/function related commands

Table 3-37 (Continued)

trace_call prompts and values for a GSM Trace and GPRS Trace.
Valid range or values

Prompt Enter call selector type and value:

Default

Notes Mobile station identifier (msid) is a number that identifies a specific mobile unit or subscriber. It must be enclosed in double quotation marks. If Nth call or NthGPRSmobile is specified, the operator is prompted for the maximum simultaneous calls traced. If trigger_event is only gprs, the call selector can be IMSI, TLLI or NthGPRSMobile. If trigger_event is gprs and setup or handover, or combined_all, the call selector can only be IMSI. If trigger_event is not gprs, then call selector can be IMSI, TMSI, IMEI, IMEISV, SCCP or Nth. The is displayed only if the call selector type is Nth or NthGPRSmobile. If call selector is NthGPRSmobile only values 1-6 are valid for this prompt. If no time is specified, the trace begins immediately and no trace period is used. Once enabled, the trace must still be triggered according to the specified trigger event before data is collected. Time is the time of day, using a 24 hour clock. The prompt is displayed only if a trigger enabled time is specified. A valid value is required. The trace is not deleted at the trigger disabled time, it is suspended until the trigger enabled time the following day. To delete the trace, the operator must either specify a total number of calls to trace, or delete the trace manually. Continued

None IMSI=msid TMSI=msid IMEI=msid IMEISV=msid SCCP=0 to FAFFFFh Nth= 1 to 255 TLLI= 02h to 0FFFFFFFFh or 2 to 4294967295 NthGPRSmobile=1 to 255

* Enter maximum simultaneous calls traced per LCF/PRP:

Any value between 1 through 16

Trigger enabled time:

A time between Midnight (00 00) and 23 59. (Enter the time without using a colon. For example, 8 25 is 20 25). A time between Midnight (00 00) and 23 59. (Enter the time without using a colon. For example, 8 25 pm is 20 25).

Immediate start

* Trigger disabled time

None

3-560

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

References

Table 3-37 (Continued)

trace_call prompts and values for a GSM Trace and GPRS Trace.
Valid range or values Any value between 1 through 255

Prompt Enter total number of calls to be traced per LCF/PRP:

Default None trace until deleted manually

Notes If no value is specified there is no limit, and the trace exists until the trace is deleted manually by an operator. If a value is specified, the trace is deleted automatically after the specified number of calls have been traced. The prompt is not displayed if the trigger_event is specified as only gprs. No or 0 means that trace data is no longer collected if the call hands out of the specified scope. Yes or 1 means that once a call triggers a trace, it is traced until the call is completed, or until it leaves the current BSS. The value entered for this prompt does not apply to GPRS data transfer when trigger event is a combination of Call trace and GPRS Data transfer. Trace reports are directed to the MMI, the OMC, or both. The prompt is not displayed if the trigger_event is specified as only gprs. GPRS Trace records go to the OMC only. The value entered for this prompt does not apply to GPRS data transfer when trigger event is a combination of Call trace and GPRS Data transfer.

* Trace calls beyond scope:

yes (1) or no (0)

* Enter destination for trace data:

mmi omc both

mmi

Related commands
disp_trace_call on page 3-390 trace_stop on page 3-564

68P02901W23-S

3-561 Nov 2009

trace_connection

Chapter 3: Device/function related commands

trace_connection

Description
The trace_connection command displays the timeslot connectivity information for a specified device. The information includes the Site ID, MMS ID, MMS timeslot numbers for all sites, and the MMSs through which the connectivity path passes. If the requested trace is for an MMS, the operator is prompted to enter the MMS timeslot number. Security level Supported by OMC-R GUI Command type Prerequisites 3 No A (no operator actions) This command is not allowed in SYSGEN mode.

Format
Syntax
trace_connection <location> <device/function> <id1> [<id2> <id3>]

Input parameters
location bsc or 0 device/function The following devices and functions can be specified: MMS RSL XBL OML GSL OPL MTL

3-562

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Example

NOTE
When the MMS is specified, the operator is prompted for the MMS timeslot.

<id1><id2><id3> Device identifiers

Example
This example displays the connectivity information for timeslot 1 of MMS 2 0. trace_connection 0 mms 2 0 Where: 0 mms 2 0 is: the location (the BSC) the device

System response
Enter the timeslot: 1 Start of Report Timeslot Usage: 16 K_RSL 1 0 Path Id: 1 0 Site BSC BTS 1 MMS downlink 2 0 uplink 0 0 Timeslot(s) 1 1

End of Report

68P02901W23-S

3-563 Nov 2009

trace_stop

Chapter 3: Device/function related commands

trace_stop

Description
The trace_stop command deletes existing trace criteria, stops triggering new traces on existing criteria, or stops traces on specified calls. Security level Supported by OMC-R GUI Command type Prerequisites 3 Yes A (no operator actions) This command is not allowed in SYSGEN mode.

Format
Syntax
trace_stop <type>[=<value>] [<extent>]

Input parameters
type The reference type for the trace. One of: sccp ref TLLI all value The hexadecimal value for the sccp or reference number. If the type is... sccp ref TLLI Then the valid range is... between 0 and FAFFFFh between 0 and FFFFFFFFh between 2 and FFFFFFFFh SCCP number. This input requires a <value>. Trace reference number. This input requires a <value>. The temporary logical link identity. This input requires a <value>. All traces. This input does not require or allow a <value>.

3-564

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Examples

NOTE
The hexadecimal number input requires a 0 prefix and an h suffix.

extent The extent to which traces should stop. extent is not valid when type is set to sccp. One of: all All traces are stopped and the specified instance deleted immediately. If no extent is set, the system defaults to all. No new traces are to be started, and the specified instance is deleted once all previously triggered traces are completed. Prevents the system defaulting to all.

new none

Examples
Example 1
This example stops tracing a call with SCCP = 047BC6h. trace_stop sccp=047BC6h Where: sccp 047BC6h is: type value

System response
COMMAND ACCEPTED

Example 2
This example deactivates the trace for reference number hex C027010A and stops tracing any calls triggered by this instance. trace_stop ref=0C027010Ah all Where: ref 0C027010Ah all is: type value extent

68P02901W23-S

3-565 Nov 2009

Examples

Chapter 3: Device/function related commands

System response
COMMAND ACCEPTED

Example 3
This example disables the triggers for the trace with reference number hex 80270001, while continuing any current call traces. When the current traces are completed, the trace instance is deleted from the database. trace_stop ref=080270001h new Where: ref 080270001h new is: type value extent

System response
COMMAND ACCEPTED

Example 4
This example stops triggering on all call trace criteria. trace_stop all new Where: all new is: extent

System response
COMMAND ACCEPTED

Example 5
This example deletes all call trace criteria. trace_stop all Where: all is: type

3-566

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Examples

System response
COMMAND ACCEPTED

68P02901W23-S

3-567 Nov 2009

unconfigure_csfp

Chapter 3: Device/function related commands

unconfigure_csfp

Description
The unconfigure_csfp command unconfigures CSFP devices from sites in the BSS network. This command returns the CSFP device back to a BSP , BTP , or pooled GPROC device depending on the original acquired device. Security Level Supported by OMC-R GUI Command Type Prerequisites Operator actions 4 Yes B (operator actions required) The system must be in SYSGEN mode to execute this command. Put the system into SYSGEN mode.

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

Format
Syntax
unconfigure_csfp

Input parameters
There are no input parameters associated with this command.

Example
In this example, all of the CSFP devices in the network are non configured. unconfigure_csfp

3-568

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

References

System response
COMMAND ACCEPTED

References
Related commands
chg_csfp on page 3-95 configure_csfp on page 3-175 disp_csfp on page 3-263

68P02901W23-S

3-569 Nov 2009

unequip

Chapter 3: Device/function related commands

unequip

Description
The unequip command deletes a device or function from the FM portion of the CM database. The unequip command is rejected if any child dependencies exist for the specified device or function. Also the command is rejected for an RTF or SITE if any Trace criteria exists with scope as the specified RTF or SITE. Security level Supported by OMC-R GUI Command type Prerequisites 4 Yes B (operator actions required) The unequip command is only allowed for a locked device or function. No child dependencies exist for the specified device or function to be unequipped. If a dependency is detected, the unequip command is rejected. See SYSGEN states below for further information. All Trace Criteria with scope as the specified RTF or SITE must be deleted before an RTF or SITE can be unequipped. Lock the device or function to be unequipped. Place the system in the SYSGEN ON mode if an CBL, MTL, OMF or OML is to be unequipped using this command.

Operator actions

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

SYSGEN states
Place the system in the SYSGEN ON mode using the sysgen_mode on command. To leave the SYSGEN ON mode, use the sysgen_mode off command.

3-570

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

SYSGEN states

In or out of SYSGEN
The following devices and functions can be unequipped using the unequip command with the system in or out of the SYSGEN ON mode. CAB CBL CIC

NOTE
For remote transcoding BSC sites, CICs must be equipped on a pre-MMS basis when the BSC operates in the dynamic allocation mode.

COMB (not M-Cellmicro)

NOTE
All affected COMB devices must be OOS before using the unequip command.

CSFP (InCell) DHP (InCell)

NOTE
The unequip command is not available for DHP devices at a Horizonmicro.

DRI DPROC

NOTE
DPROC performed at site PCU.

68P02901W23-S

3-571 Nov 2009

SYSGEN states

Chapter 3: Device/function related commands

DYNET

NOTE
A DYNET cannot be unequipped if: It is the last DYNET containing a site using dynamic allocation and that site still has equipped RTFs or, It causes the total terrestrial backing resources for a BTS network to be less than the total reserved cell capacity.

The total terrestrial backing resources for a BTS network is the sum of the terrestrial backing resources reserved on the DYNETs for the BTS network. EAS (not M-Cellmicro) GBL GCLK (InCell) GDS

NOTE
When an attempt is made to unequip a TRAU GDS, and the requested PDTCHs exceed the GDS or PMC capacity on the PCU, the BSS accepts the request and issues a warning to indicate that GDS or PMC resource are not available.

GPROC (InCell) GSL

NOTE
To bring the GSL out of service, lock it at either the OMC-R or at the MMI prompt. The GSL is performed at site PCU.

KSW (InCell) LCF MSI

NOTE
An RF_Unit MSI cannot be unequipped if DRIs are equipped that use LTU connectors controlled by the RF_Unit MSI. An MSI cannot be unequipped if the device is referenced in the BSS-RXCDR connectivity table.

3-572

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

SYSGEN states

MTL OML PATH PCU RTF

NOTE
An RTF cannot be unequipped if both the following conditions are true: The cell is baseband hopping. One or more of the FHIs associated with the RTF are enabled.

A warning message is generated if an attempt is made to unequip an RTF with a non-zero sd_load value. An RTF cannot be unequipped if the resulting reduced number of available timeslots or carriers is not sufficient to maintain current or one less than the current GPRS configurations. An RTF cannot be unequipped if there exist Trace Criteria with scope as the specified RTF.

RSL

NOTE
The unequip command does not allow unequipping an RSL from a 16 kbit/s site using dynamic allocation if it causes the reserved cell capacity to exceed the total terrestrial backing resources for the BTS network. The unequip command automatically unequips the additional 16 K RSL when a 16 K RSL is being unequipped as part of a closed loop DYNET.

SITE

NOTE
The unequip command for a SITE device at a Horizonmicro BTS automatically unequips any DGP devices that exist at that BTS site. A SITE cannot be unequipped if Trace Criteria with scope as the specified SITE exists.

XBL AXCDR ABSS

68P02901W23-S

3-573 Nov 2009

Format

Chapter 3: Device/function related commands

Standby devices
The following devices or functions can only be unequipped using the unequip command if they are standby devices. These devices can be unequipped with the system in or out of the SYSGEN ON mode. BSP BTP

When unequipping BTPs from M-Cell sites, BTP 0 must be the last BTP unequipped. The BTP device (a processor card within a BTS site) manages the auto-unequip (and auto-equip) of the MSI device 0 0 0 (with six associated MMS devices) at a BTS site with a Horizon II controlling cabinet.

SYSGEN on mode
The following devices or functions can only be unequipped using the unequip command when the system is in the SYSGEN ON mode: OMF (BSC only)

The LCF can be unequipped using the unequip command if no sites exist on the LCF. The LCF is unequipped with the system in or out of the SYSGEN mode. The system does not have to be locked when the LCF is unequipped outside the SYSGEN ON mode. The last KSW in a system cannot be unequipped using the unequip command. The SITE must be unequipped using the unequip command to remove the last KSW from the database.

Format
Syntax
unequip <location> <dev/func_name> <id1> <id2> <id3>

Input parameters
location Specifies the location of the device or function: 0 or bsc 1 - 140 {27955A} pcu or pcu_0 dev/func_name Literal that uniquely identifies the device or function. BSC BTS PCU

3-574

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Format

The following devices and functions are entered: AXCDR ABSS BSP BTP CAB CBL CIC COMB OPL CSFP DHP DPROC DRI DYNET EAS GBL GCLK GDS GPROC GSL KSW LCF MSI MTL OMF OML PATH PCU RSL RTF SITE XBL {26740}PSI

NOTE
The unequip command supports the unequipping of extension cabinets of type TCU_2, TCU_6, HORIZONMACRO_EXT, and Horizon II macro provided the cabinet is locked and no DRIs or EASs are equipped to the cabinet. No other cabinet types are supported. The following GPRS devices can be used with this command: DPROC GBL GDS GSL PCU

NOTE
The PCU location must be specified when unequipping the GPRS devices, except for the PCU itself. To unequip the PCU, specify the BSC for the location. Child dependency can exist when unequipping the PCU, except for GDS and GSL; that is, GBL, DPROC, MSI, and NSVC can exist when the PCU is unequipped.

id1 First identifier. This definition varies with each device or function. When unequipping an EAS, only the first identifier is required. The following ranges of values are entered: 0 to 7 0 to 15 id2 Second identifier. This definition varies with each device or function. When unequipping a PATH, the range varies depending on whether the BTS uses dynamic allocation. The following ranges of values are entered: InCell sites M-Cell sites

68P02901W23-S

3-575 Nov 2009

Format

Chapter 3: Device/function related commands

0 to 9 6 to 9 id3

valid values if the terminating BTS does not use dynamic allocation valid values if the terminating BTS uses dynamic allocation

Third identifier. This definition varies with each device or function.

CIC syntax
A form of syntax is available for each method of specifying a CIC. The following CIC syntax applies to local transcoding: unequip <location> CIC <cic_num1> unequip <location> CIC <cic_num1> TO <cic_num2> unequip <location> CIC <mms_id1> <mms_id2> unequip <location> CIC <mms_id1> <mms_id2> <timeslot1> unequip <location> CIC <mms_id1> <mms_id2> <timeslot1> TO <timeslot2> The following CIC syntax applies to remote transcoding: unequip <location> CIC <cic_num1> unequip <location> CIC <cic_num1> TO <cic_num2> unequip <location> CIC <mms_id1> <mms_id2> unequip <location> CIC <mms_id1> <mms_id2> <timeslot1> <group> unequip <location> CIC <mms_id1> <mms_id2> <timeslot1> * unequip <location> CIC <mms_id1> <mms_id2> <timeslot1> <group1> TO <timeslot2> <group2> CIC Literal that uniquely identifies the CIC device. cic_num1 First CIC device number. cic_num2 Last CIC device number in a range. mms_id1 First MMS identifier. mms_id2 Second MMS identifier, or last in a range if TO is used. timeslot1 First timeslot. timeslot2

3-576

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Examples

Second timeslot, or last in a range if TO is used. group1 First group. group2 Second group. * Indicates all CICs on the MMSs specified in the timeslot, regardless of group.

Examples
Example 1
In this example, an MSI is deleted from the CM database: unequip 2 msi 2 0 0 Where: 2 msi 2 0 0 is: location dev/func_name id1 id2 id3

System response
COMMAND ACCEPTED

Example 2
This example unequips PCU 0 from a BSC. unequip 0 pcu 0 Where: 0 pcu 0 is: location device_name id1

68P02901W23-S

3-577 Nov 2009

Examples

Chapter 3: Device/function related commands

System response
COMMAND ACCEPTED

Example 3
This example unequips a GDS with a warning that there are not enough GDS resources to handle PDTCHs. unequip pcu GDS 1 Where: pcu GDS 1 is: location device_name id1

System response
COMMAND ACCEPTED WARNING: Insufficient GDS resources available for all PDTCHs on the PCU.

Example 4
{26740} This example unequips a PSI device.

NOTE
The PSI device has to be locked before unequipage. Unequip the GDS device associated with the PSI before unequipping the PSI device.

unequip bsc psi 1 Where: bsc psi 1 is: location device_name id1

System response
COMMAND ACCEPTED

3-578

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Examples

Example 5
{26481} In this example, the operator attempts to unequip H2micro extension cabinet 15 0 0 which is unlocked. unequip 5 CAB 15 0 0 Where: 5 CAB 15 0 0 is: location device_name id1 id2 id3

System response
COMMAND REJECTED: Device is not locked and cannot be unequipped

Example 6
{23311A} This example unequips RTF with ext_pdchs >0, when gprs_enabled = 1 in the cell. unequip 62 rtf 2 0 Where: 62 rtf 2 0 is: location device_name id1 id2

System response
COMMAND REJECTED: gprs_enabled shall be disabled before unequip RTF with ext_pdchs >0.

68P02901W23-S

3-579 Nov 2009

References

Chapter 3: Device/function related commands

References
Related commands
disp_equipment on page 3-283 shutdown_device on page 3-502 equip on page 3-403 state on page 3-515 lock_device on page 3-429 unlock_device on page 3-581

3-580

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

unlock_device

Description
The unlock_device command unlocks a specified device to free it for use. Security level Supported by OMC-R GUI Command type Prerequisites 2 Yes B (operator actions required) This command is not allowed while in SYSGEN ON mode. This command is only valid when the device is in the LOCKED state. The location must be bsc or 0 when specifying the device, or pcu if unlocking a GPRS device. Lock the device before entering this command. To unlock a PCU device, the GPRS feature must be unrestricted. Also the PCU device identifier must be specified.

Operator actions

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 1 - 140 {27955A} pcu or pcu_0 device_name Literal that uniquely identifies the device. BSC BTS PCU

68P02901W23-S

3-581 Nov 2009

Format

Chapter 3: Device/function related commands

The following devices can be unlocked using this command: ABSS {34321}CAGE DHP GCLK MMS PATH XBL AXCDR CBL DPROC GDS MSI PCU BSP CIC DRI GPROC MTL RSL BTP COMB EAS GSL OML SBUS CAB CSFP GBL KSW OPL SITE

NOTE
The unlock command supports the unlocking of extension cabinets of type TCU_2, TCU_6, and HORIZONMACRO_EXT. No other cabinet types are supported. The following GPRS only devices can be unlocked at the PCU using this command: DPROC device_id1 First device identifier. This definition varies with each device. device_id2 Second device identifier. This definition varies with each device. device_id3 Third device identifier. This definition varies with each device. GBL GDS GSL PCU

CIC syntax
A form of syntax is available for each method of specifying a CIC. The following CIC syntax applies to local transcoding: unlock_device <location> CIC <cic_num1> unlock_device <location> CIC <cic_num1> TO <cic_num2> unlock_device <location> CIC <mms_id1> <mms_id2> unlock_device <location> CIC <mms_id1> <mms_id2> <timeslot1> unlock_device <location> CIC <mms_id1> <mms_id2> <timeslot1> TO <timeslot2> The following CIC syntax applies to remote transcoding: unlock_device <location> CIC <cic_num1> unlock_device <location> CIC <cic_num1> TO <cic_num2> unlock_device <location> CIC <mms_id1> <mms_id2>

3-582

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Format

unlock_device <location> CIC <mms_id1> <mms_id2> <timeslot1> <group> unlock_device <location> CIC <mms_id1> <mms_id2> <timeslot1> * unlock_device <location> CIC <mms_id1> <mms_id2> <timeslot1> <group1> TO <timeslot2> <group2> CIC Literal that uniquely identifies the CIC device. cic_num1 First CIC device number. cic_num2 Last CIC device number in a range. mms_id1 First MMS identifier. mms_id2 Second MMS identifier, or last in a range if TO is used. timeslot1 First timeslot. timeslot2 Second timeslot, or last in a range if TO is used. group1 First group. group2 Second group. * Indicates all CICs on the MMSs specified in the timeslot, regardless of group.

68P02901W23-S

3-583 Nov 2009

Examples

Chapter 3: Device/function related commands

Examples
Example 1
In this example, an MMS with the ID 0 at the BSC is unlocked: unlock_device bsc mms 0 0 0 Where: bsc mms 0 0 0 is: location device_name device_id1 device_id2 device_id3

System response
COMMAND ACCEPTED

Example 2
This example unlocks a range of CICs (remote transcoder) specifying them by their MMS, TS, and group. unlock_device bsc cic 2 1 3 1 TO 5 1 Where: BSC CIC 2 1 3 1 5 1 is: location device_name first MMS ID second MMS ID timeslot 3 group 1 timeslot 5 group 1

System response
COMMAND ACCEPTED

3-584

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Examples

Example 3
This example unlocks a GPRS PICP MSI at the first PCU. unlock_device pcu_0 msi 3 Where: pcu_0 MSI 3 is: location device_name first MSI ID

System response
COMMAND ACCEPTED

Example 4
{26740} This example unlocks the ETH device. unlock_device pcu_0 eth 2 0 0 Where: pcu_0 ETH 2 0 0 is: location device_name first ETH ID second ETH ID third ETH ID

System response
COMMAND ACCEPTED

68P02901W23-S

3-585 Nov 2009

References

Chapter 3: Device/function related commands

Example 5
{34321} This example unlocks a cage. No warning is displayed. unlock_device bsc cage 2 0 Where: bsc cage 2 0 is: location device_name device_id1 device_id2

System response
COMMAND ACCEPTED

References
Related commands
disp_equipment on page 3-283 state on page 3-515 equip on page 3-403 unequip on page 3-570 lock_device on page 3-429

3-586

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

_bss_data,6

Description
The new per BSS element, _bss_data,6 indicates whether the system information 2quater for TD-SCDMA neighbors are built in standard or workaround mode. This parameter may be changed inside and outside SYSGEN mode without warning. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) No No This parameter is modified only when the TD-SCDMA interworking feature is unrestricted (tdOpt) and disabled (td_enabled = 0).

Syntax
Change command string
chg_element _bss_data,6 <value> <location>

Display command string

disp_element _bss_data,6 <location>

Values
Value type Valid range Boolean 0 to 1 0 1 Default value 0 Using standard TD-SCDMA SI2quater message Using workaround TD-SCDMA SI2quater message

68P02901W23-S

3-587 Nov 2009

_bss_data,10

Chapter 3: Device/function related commands

_bss_data,10

{34321}

Description
The _bss_data,10 parameter enables and disables the function of the cage management feature. This parameter can be accessed and updated both in and out of SYSGEN mode. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) No No None

Syntax
Change command string
chg_element _bss_data,10 <value> <location>

Display command string

disp_element _bss_data,10 <location>

Values
Value type Valid range Boolean 0 to 1 0 1 Default value 0 Disabled Enabled

3-588

68P02901W23-S Nov 2009

Chapter

4
UNIX commands

Selected UNIX commands provide a useful addition to MMI commands. This chapter describes several UNIX commands that may be used from the MMI. The following UNIX commands are described: alias help history man unalias

Each UNIX command is described separately using the following command reference layout: Command title - the actual command reference. Description - providing a description of the command operation, including information on the command security level, whether supported by OMC-R GUI, the type of command, and the prerequisites for the command that the system accepts. Format - giving the command line syntax and descriptions of the command parameters. Examples - providing specific examples of command input and the resulting system response. References - giving any related commands.

68P02901W23-S Nov 2009

4-1

alias

Chapter 4: UNIX commands

alias

Description
The alias command creates an alias for an MMI command. If no parameters are entered, a list of active aliases is displayed. The maximum length which can be entered is 256 characters. These characters include the command name (alias) and the alias name. The alias applies only to the GPROC for which it is set. A login to a different GPROC does not recognize the alias. Security level Supported by OMC-R GUI Command type Prerequisites Any No A (no operator actions) None

Format
Syntax
alias [<alias_name>'<alias_text>']

Input parameters
alias_name Name of the alias. alias_text Any valid MMI command which can be just the command name or a command and parameters. Enclose the alias_text in single quotes.

4-2

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Example

Example
This example creates an alias called list which executes the command string.disp_equipment bsc: alias list 'disp_equipment bsc' Where: list disp_equipment bsc is: alias_name alias_text

System response:
COMMAND ACCEPTED

References
Related commands
unalias on page 4-10.

68P02901W23-S

4-3 Nov 2009

help

Chapter 4: UNIX commands

help

Description
The help command displays help information about the specified command. If no command is specified, a list of all available commands is displayed. Additional online information may be displayed by using the man command. Security level Supported by OMC-R GUI Command type Prerequisites 1 No A (no operator actions) None

Format
Syntax
help [<command>]

Input parameter
command String specifying an MMI command.

Example
This example displays help for the chg_level command. help chg_level Where: chg_level is: command

System response
chg_level: Changes the current security level

4-4

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

References

References
Related command
man on page 4-8.

68P02901W23-S

4-5 Nov 2009

history

Chapter 4: UNIX commands

history

Description
The history command displays a numbered list of previously entered MMI commands. This command may also be used to repeat one of the commands displayed in the listing. Security level Supported by OMC-R GUI Command type Prerequisites Any No A (no operator actions) None

Format
Syntax
history [<num_commands>] or !<num_commands> or !!

Input parameter
num_commands The number of previously entered commands to display. The default is 23. If this parameter is not entered, the last 23 commands are displayed.

4-6

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Examples

Examples
Example 1
This example lists the last three commands that were entered. history 3 Where: 3 is: number of commands.

System response
11 disp_level 12 shg_level 13 disp_dte

Example 2
Using the output of the history command from the previous example, the following command string executes the statement contained in command number 13 shown in the command history list: !13 In this case, it is the disp_dte command. The command string !! executes the last command again.

68P02901W23-S

4-7 Nov 2009

man

Chapter 4: UNIX commands

man

Description
The man command is used to display detailed help information about the specified command. Security level Supported by OMC-R GUI Command type Prerequisites 1 No A (no operator actions) None

Format
Syntax
man <command>

Input parameter
command String specifying an MMI command.

Example
This example shows the manual text presented with the alias command. man alias Where: alias is: command

4-8

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

References

System response
Command: alias [<alias_name> '<alias_text>'] Can be executed from any security level. If no

Security Level: Function:

Create an alias for an MMI command.

parameters are entered, a list of active aliases are displayed. <alias_name> The name of the alias. <alias_text> Any valid MMI command. This can be just the

command name, or a command and parameters. This MUST be enclosed in single quotes. Example 1: Create an alias called list which executes disp_equipment bsc: alias list 'disp_equipment bsc' Example 2: List all active aliases: alias

References
Related command
help on page 4-4.

68P02901W23-S

4-9 Nov 2009

unalias

Chapter 4: UNIX commands

unalias

Description
The unalias command removes the alias <alias_name> from the specific GPROC at which it was set. Security level Supported by OMC-R GUI Command type Prerequisites Any No A (no operator actions) None

Format
Syntax
unalias <alias_name>

Input parameter
alias_name Remove the name of the alias.

Example
This example removes the alias named list. unalias list Where: list is: alias_name

System response
COMMAND ACCEPTED

4-10

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

References

Statistical operations and information

The following MMI commands are used to obtain statistical information and perform statistical operations: chg_stat_prop (see chg_stat_prop on page 5-5). disp_enable_stat (see disp_enable_stat on page 5-12). disp_interval (see disp_interval on page 5-22). disp_stat_prop (see disp_stat_prop on page 5-24). disp_stats (see disp_stats on page 5-34). stat_mode (see stat_mode on page 5-48).

Statistical operations
The statistical commands perform the following statistical operations: Enable/disable statistics. Display/modify statistics for devices or cells. Monitor system statistics over specified time intervals. Monitor active (enabled) system statistics. Report statistical data.

Statistical information
The system generates the statistical information. The system operators use the information for: Monitoring the quality of service. Fault finding. Optimize system performance. Network planning. System installation and commissioning.

5-2

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Counter statistics

Statistical information is gathered in the form of: Counter statistics. Duration statistics. Gauge statistics. Distribution statistics.

Counter statistics
Counter statistics represent the number of occurrences of an event. The monitored event is specified as the database parameter in the chg_element command. Counter statistics may only be enabled and disabled. Certain counter statistics have associated alarms. If a threshold is reached, an alarm is sent to the OMC-R.

Duration statistics
Duration (or total time) statistics involve the use of a timer to collect a cumulative time value. The timer starts when an event begins and stops when it ceases. The event data are recorded for statistical analysis. The resulting statistics express the total amount of time a particular event occurred, as well as minimum, maximum, and mean durations (in milliseconds). Duration statistics may only be enabled and disabled.

Gauge statistics
Gauge statistics report the maximum and mean values of a statistic for an interval. The IDLE_TCH_INTF_BAND0 statistic is an example of a gauge statistic. While a gauge statistic may result in the report of a reported negative value, the cumulative value may not be a negative value. A check is performed before calculating the mean value, and if the result is a negative number, the mean value is set to zero.

Threshold event reporting

An alarm threshold may be specified for gauge statistics. If a threshold is reached, the alarm is reported to the OMC-R.

Interval expiry
Interval expiry is the end of a statistic interval. The mean and maximum gauge statistic values at the interval expiry are saved and reset to 0 at the interval expiry.

68P02901W23-S

5-3 Nov 2009

Distribution statistics

Chapter 5: Statistics commands

Distribution statistics
Two types of distribution statistics, normal and weighted, are used to record all events or state changes reported by some application processes. Normal distribution statistics represent the number of times the value of an event or state change occurs within the range of a specific bin. The size of the upper and lower bins in which the data is collected determines the range of a bin. For example, if the range of a bin is 10 to 20, and the application process reports a value of 15 three times, the statistical value is 3. Weighted distribution statistics record the length of time (in milliseconds) that an element is at a specific value. The statistical value displayed is the cumulative time of the events occurring within that range of a bin. For example, if the range of a bin is 10 to 20, and the application process reports six events with a value of 15 lasting 12 milliseconds each, the statistical value is 72.

Statistics descriptions
Refer to the Maintenance Information: GSM Statistics Application (68P02901W56) for detailed information on each statistical parameter.

5-4

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

chg_stat_prop

Description
The chg_stat_prop command changes the properties of statistics. The specific properties that may be changed depend on the statistic type. If an alarm is associated with the statistic, the alarm threshold may be changed for counter, counter array, and gauge statistics. Bin ranges may be changed for normal and weighted statistics. Properties may not be changed for duration (total time) statistics.

When the chg_stat_prop command is entered the system displays a series of prompts. The specific prompts depend on the statistic type. Refer to References/Related information for explanations of the prompts associated with each statistic. Security level Supported by OMC-R GUI Command type Prerequisites 4 Yes A (no operator actions) The GPRS feature must be unrestricted to display PCU statistics. The EGPRS feature must be unrestricted to display EGPRS associated statistics.

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

Format
Syntax
chg_stat_prop <meas_type> [location] [<cell_desc>] chg_stat_prop <meas_type> all

68P02901W23-S

5-5 Nov 2009

Examples

Chapter 5: Statistics commands

Input parameters
meas_type Specifies the name of the statistic. location Specifies the site location: 0 or bsc 1 - 140 all cell_desc The GSM cell ID of the cell for which statistics properties are to be modified, preceded by cell_number=. The format for the GSM cell ID depends on: The system used (PGSM, EGSM, DCS1800, PCS1900). Whether the seven parameter GSM cell ID format or the four parameter GSM cell ID format has been enabled. BSC BTS All sites

The name of the cell created using the cell_name command may be entered in place of the cell_number. When the cell name is entered, place it inside double quotation marks and precede by cell_name=.

NOTE
This command responds to the shortened input parameter cell= allowing entry of either the cell_number or the cell_name without further definition. The value all is also a valid input for the cell_desc. If entered, the mode for the statistic changes for all cells at the specified site.

Examples
Example 1
This example changes the alarm threshold for the RF_LOSSES_TCH statistic for cell number 5 4 3 2 1 61698 34776 at site 1. chg_stat_prop rf_losses_tch 1 cell_number= 5 4 3 2 1 61698 34776 Where: rf_losses_tch 1 5 4 3 2 1 61698 34776 is: meas_type location cell_desc

5-6

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Examples

System response
Enter the threshold for total value: 2 COMMAND ACCEPTED

Example 2
This example changes minimum and maximum values for two bins of the BUSY_TCH statistic for all cells at site 1. chg_stat_prop busy_tch 1 all Where: busy_tch 1 all is: meas_type location all cells at the specified site.

System response
Enter the bin number(s): 0,1 Enter the min value for bin 0: 0 Enter the max value for bin 0: 5 Enter the min value for bin 1: carriage return Enter the max value for bin 1: 7

COMMAND ACCEPTED

Example 3
This example changes the alarm threshold for the RF_LOSSES_TCH statistic for PCS1900 cell number 543 721 61698 34776 at site 1. chg_stat_prop rf_losses_tch 1 cell_number= 543 721 61698 34776 Where: rf_losses_tch 1 543 721 61698 34776 is: meas_type location cell_desc

68P02901W23-S

5-7 Nov 2009

Examples

Chapter 5: Statistics commands

System response
Enter the threshold for total value: 2 COMMAND ACCEPTED

Example 4
{28337} This example changes the threshold of MTP_SL_ERROR_RATE_HSP BSS statistics. chg_stat_prop MTP_SL_ERROR_RATE_HSP

System response
Enter the threshold for total value: 2 COMMAND ACCEPTED

Example 5
{22266} This example changes the properties of the link statistic RSL_TX_OCTETS. chg_stat_prop RSL_TX_OCTETS

System response
COMMAND REJECTED: Threshold cannot be set for non-alarming statistics.

Example 6
{33863} This example changes the properties of the cell statistic UL_RLC_STALLED_BLKS when the GPRS feature is unrestricted/restricted. chg_stat_prop UL_RLC_STALLED_BLKS cell 0 0 1 0 1 1 1 Where: UL_RLC_STALLED_BLKS 0010111 is: meas_type cell_desc

5-8

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Examples

System response
COMMAND REJECTED: Threshold cannot be set for non-alarming statistics.

Example 7
{26881} This example changes the properties of the cell statistic: EXT_UL_USF_USAGE or EXT_UL_EXITS when Extended Uplink TBF feature is unrestricted. chg_stat_prop EXT_UL_USF_USAGE cell 0 0 1 0 1 1 1 Where: EXT_UL_USF_USAGE 0010111 is: meas_type cell_desc

System response
COMMAND REJECTED: Threshold cannot be set for non-alarming statistics.

Example 8
{31565} This example changes the properties of the cell statistic IA_IAR_MSGS_PER_AGCH. chg_stat_prop IA_IAR_MSGS_PER_AGCH cell_number= 0 0 1 0 1 1 1 Where: IA_IAR_MSGS_PER_AGCH 0010111 is: meas_type cell_desc

System response
COMMAND REJECTED: Threshold cannot be set for non-alarming statistics.

68P02901W23-S

5-9 Nov 2009

References

Chapter 5: Statistics commands

Example 9
{33397} This example changes the properties of the cell statistic CS_PAGING_MSGS_FROM_MSC. chg_stat_prop CS_PAGING_MSGS_FROM_MSC cell_number= 0 0 1 0 1 1 1 Where: CS_PAGING_MSGS_FROM_MSC 0010111 is: meas_type cell_desc

System response
COMMAND REJECTED: Threshold cannot be set for non-alarming statistics.

Example 10
{33780} This example changes the properties of the cell statistic UL_LLC_TRANS_TIME when GPRS feature is unrestricted or restricted. chg_stat_prop UL_LLC_TRANS_TIME cell 0 0 1 0 1 1 1 Where: UL_LLC_TRANS_TIME 0010111 is: meas_type cell_desc

System response
COMMAND REJECTED: Threshold cannot be set for non-alarming statistics.

References
Related information
Table 5-1 lists the counter and gauge statistic type prompts for changing the alarm threshold.

5-10

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

References

Table 5-1

Counter and gauge statistic type prompts

Valid range 0 to 2147483647 Description If a <carriage return> is entered in response to this prompt, the current value does not change. If an alarm is not associated with the specified statistic, the command is rejected and this prompt is not presented.

Prompt Enter the alarm threshold

Table 5-2 lists the normal and weighted distribution statistic type prompts for changing bin value.

Table 5-2

Normal and weighted distribution statistic type prompts

Valid range 0 to 9 Description Multiple bin numbers may be entered by separating each bin number with a space or comma. This prompt repeats for each bin number (n) entered in response to the first prompt. If a <carriage return> is entered in response to the first prompt, the current value is not changed. This prompt repeats for each bin number (n) entered in response to the first prompt. If a <carriage return> is entered in response to the first prompt the current value is not changed.

Prompt Enter the bin number(s): Enter the min value for bin n:

The minimum value that may be entered is 0

Enter the max value for bin n:

The maximum value that may be entered is 2147483647

NOTE
The system rejects the command if the minimum bin value is greater than the maximum bin value for a distribution statistic.

Related commands
disp_element on page 3-272 disp_enable_stat on page 5-12 disp_interval on page 5-22 disp_stats on page 5-34

68P02901W23-S

5-11 Nov 2009

disp_enable_stat

Chapter 5: Statistics commands

disp_enable_stat

Description
The disp_enable_stat command displays the status of statistics. Specific listings generated by this command depend on the argument entered with the command. {28337} This command displays enabled statistics by cell, location, or all statistics in the system. If no arguments are entered with the command, a listing showing all of the enabled statistics is displayed. If a Cell ID (or name) is entered with the command, a listing of enabled statistics at the specified cell is displayed. If bss is entered with the command, a listing of the enabled statistics in the BSS is displayed. A specific statistic may be entered as the meas_type. When the name of a BSS-wide statistic is entered, the command displays the state of the statistic. When the name of a per-cell statistic is entered, the command displays the GSM cell ID of the cells which have the statistic enabled. If a Location ID is entered with the command, a listing of the enabled statistics at the specified location is displayed. Security level Supported by OMC-R GUI Command type Prerequisites 1 Yes A (no operator actions) None

Format
Syntax
disp_enable_stat disp_enable_stat <bss> disp_enable_stat <location> disp_enable_stat <meas_type>

5-12

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Examples

Input parameters
cell_desc The GSM cell ID of the cell for which the enabled statistics are displayed, preceded by cell_number=. A cell_desc is specified only for per cell, per neighbor cell, and per timeslot statistics. The format for the GSM cell ID depends on: The system used (PGSM, EGSM, DCS1800, PCS1900). Whether the seven parameter GSM cell ID format or the four parameter GSM cell ID format has been enabled.

The name of the cell created using the cell_name command may be entered in place of the cell_number. When the cell name is entered, place inside double quotation marks and precede by cell_name=.

NOTE
This command responds to the shortened input parameter cell= allowing entry of either the cell_number or the cell_name without further definition.

bss Specifies the BSS. location Specifies the site location: 0 or bsc 1 - 140 meas_type Specifies the name of the statistic. BSC BTS

Examples
Example 1
In this example, an abbreviated list of all the enabled statistics is displayed when the disp_enable_stat command is entered with no arguments. Actual output from the system shows all statistics. The output includes all non-cell and individual cell statistics. disp_enable_stat

NOTE
The text that follows shows part of a typical display. Such a display continues until all of the enabled statistics have been displayed.

68P02901W23-S

5-13 Nov 2009

Examples

Chapter 5: Statistics commands

System response
Enabled Non-Cell Statistics ma_req_from_msc_fail page_req_from_msc_fail ho_req_msc_proto mtp_sl_fail mtp_sl_fibr mtp_sl_ack ... ... mtp_msu_tx mtp_msu_rx sl_congestion sl_stop_congestion msu_disgarded congestion_lost_msu sif_sio_rx_opc sif_sio_tx_dpc sif_sio_type routing_syntax routing_unknown sccp_msgs sccp_msgs_tx sccp_msgs_rx invalid_frames_rx i_frames_rx i_frames_tx sabm_tx_frmr n2_expiry mtp_link_ins mtp_unavailable mtp_local_mgt mtp_remote_mgt

5-14

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Examples

mtp_linkfail mtp_remote_proc mtp_local_busy mtp_congestion cpu_usage ... ... PRP_PD_DEMAND GCI_FOR_16 KPD_DEMAND GCI_FOR_32 KPD_DEMAND GCI_FOR_64 KPD_DEMAND TOTAL_GCI_FOR_PD_DEMAND ... ... EnabledStatistics for Cell 0 0 1 0 1 1 2 egprs_avail_pdtch rf_losses_tch rf_losses_sd intra_cell_ho in_inter_ho out_inter_ho intra_bss_ho access_per_rach ... ... ACCESS_PER_PCH ALLOC_SDCCH ... NUM_CELL_RESEL_CELL NUM_CELL_RESEL_CELL_PCCN NUM_CELL_RESEL_CELL_SUCC NUM_CELL_RESEL_NEI NUM_CELL_RESEL_NEI_PCCN

68P02901W23-S

5-15 Nov 2009

Examples

Chapter 5: Statistics commands

NUM_CELL_RESEL_NEI_SUCC ... RF_LOSSES_SD RF_LOSSES_TCH TCH_Q_REMOVED ... ... PACKET_SYSINFO_REQ PACKET_SYSINFO_RESP ... ... SDCCH HO (see NOTE) SMS_INIT_ON_SDCCH_HO_OUT ... ... tch_delay intf_on_idle busy_tch busy_sdcch ber

Example 2
This example displays the sites and related cells for which the CELL statistic total calls is enabled. disp_enable_stat total_calls

5-16

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Examples

System response
Statistic total_calls enabled for the following cells at site 18 ---------------------------------------------------------------543 21 F333h 028Ah 543 21 F333h 028Bh 54321 F333h 028Ch Statistic total_calls enabled for the following cells at site 30 ---------------------------------------------------------------543 21 F333h 2128h Statistic total_calls enabled for the following cells at site 31 ---------------------------------------------------------------543 21 F333h 0031h Statistic total_calls enabled for the following cells at site 32 ---------------------------------------------------------------543 21 F333h 2127h Statistic total_calls enabled for the following cells at site 36 ---------------------------------------------------------------543 21 F333h 2124h 543 21 F333h 2125h 543 21 F333h 2126h

Example 3
This example shows the cells at site 1 for which the GPRS_CELL_CONGESTION statistic is enabled. disp_enabled_stat GPRS_CELL_CONGESTION cell=0 0 1 0 0 1 1

System response
Statistics GPRS_CELL_CONGESTION enabled for the following cells at site 1 ------------------------------------------------------------------------0 0 1 0 0 0001h 0001h

Example 4
{28337} This example displays the enabled SS7 link MTP_SL_ERROR_RATE_HSP statistics. disp_enable_stat

68P02901W23-S

5-17 Nov 2009

Examples

Chapter 5: Statistics commands

System response
Enabled Non-Cell Statistics ma_req_from_msc_fail page_req_from_msc_fail ho_req_msc_proto mtp_sl_error_rate_hsp mtp_sl_error_rate mtp_sl_ack mtp_sl_error_rate mtp_sl_congestion mtp_sl_alignment mtp_su_error mtp_neg_acks mtp_changeover mtp_changeback

Example 5
{22266} This example displays all statistics enabled under BSS. disp_enable_stat BSS

System response
RSL_RX_OCTETS RSL_TX_OCTETS RSL_LINK_INS . .

Example 6
{33863} This example displays all the enabled statistics for all the cells at site 1. disp_enable_stat 1

5-18

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Examples

System response
Enabled statistics for Cell 0 0 1 01 0001h 0001h ... UL_RLC_STALLED_BLKS UL_RLC_NACK_BLKS ...

Example 7
{31565} This example displays all the enabled statistics for all the cells at site 1. disp_enable_stat 1

System response
. . Enabled Statistics for Cell 0 0 1 0 1 1 2 rf_losses_tch rf_losses_sd rf_losses_tch_hr intra_cell_ho in_inter_ho out_inter_ho intra_bss_ho access_per_rach IA_IAR_MSGS_PER_AGCH . . .

Example 8
{33397} This example displays all the enabled statistics for all the cells at site 1. disp_enable_stat 1

68P02901W23-S

5-19 Nov 2009

Examples

Chapter 5: Statistics commands

Example 9
{33780} This example displays all the enabled statistics for all the cells at site 1. disp_enable_stat 1

System response
Enabled statistics for Cell 0 0 1 01 0001h 0001h . . . UL_LLC_DATA_VOLUME DL_LLC_DATA_VOLUME UL_LLC_TRANS_TIME DL_LLC_TRANS_TIME . . .

5-20

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

References

References
Related commands
disp_element on page 3-272 stat_mode on page 5-48 disp_interval on page 5-22 disp_stats on page 5-34

68P02901W23-S

5-21 Nov 2009

disp_interval

Chapter 5: Statistics commands

disp_interval

Description
The disp_interval command displays the start times associated with each of the system statistics intervals. Security level Supported by OMC-R GUI Command type Prerequisites 1 Yes A (no operator actions) This command is not allowed in SYSGEN ON mode.

Format
Syntax
disp_interval

Input parameters
There are no input parameters associated with this command.

Example
This example shows a sample of the display the system produces when the disp_interval command is entered. disp_interval

5-22

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

References

System response
Interval -------0 1 2 3 4 5 6 7 8 9 10 11 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 13:30:00 14:00:00 14:30:00

References
Related commands
disp_element on page 3-272 disp_enable_stat on page 5-12 chg_element on page 3-106 disp_stats on page 5-34

68P02901W23-S

5-23 Nov 2009

disp_stat_prop

Chapter 5: Statistics commands

disp_stat_prop

Description
The disp_stat_prop command displays the following properties associated with a statistic: Mode (enabled/disabled). Type (per link, per timeslot, per cell, and so on). Object type.

The statistic type determines the additional information displayed using the disp_stat_prop command: Alarm severity and threshold values display for counter and gauge statistics. Bin ranges display for normal and weighted distribution statistics. The statistical basis display for percent statistics. Duration values for duration statistics.

If the output generated by this command is large, it is paginated. Security level Supported by OMC-R GUI Command type Prerequisites 1 Yes A (no operator actions) None

Format
Syntax
disp_stat_prop <meas_type> [<cell_desc>] disp_stat_prop <meas_type> <location> [<cell_desc>] disp_stat_prop <meas_type> <location> all

5-24

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Examples

Input parameters
meas_type The name of the statistic. location Specifies the site location: 1 - 140 all cell_desc The GSM cell ID of the cell for which statistics properties are displayed, preceded by cell_number=. The format for the GSM cell ID depends on: The system used (PGSM, EGSM, DCS1800, PCS1900). Whether the seven parameter GSM cell ID format or the four parameter GSM cell ID format has been enabled. BTS All sites

The name of the cell created using the cell_name command may be entered in place of the cell_number . When the cell name is entered, place inside double quotation marks and precede by cell_name=.

NOTE
This command responds to the shortened input parameter cell= allowing entry of either the cell_number or the cell_name without further definition. The value all is also a valid input for the cell_desc. If entered, the mode for the statistic changes for all cells at the specified site.

Examples
Example 1
This example displays the properties of the gauge statistic PRP_PD_DEMAND. disp_stat_prop PRP_PD_DEMAND Where: PRP_PD_DEMAND is: meas_type

68P02901W23-S

5-25 Nov 2009

Examples

Chapter 5: Statistics commands

System response
STATISTIC: PRP_PD_DEMAND TYPE: PER DPROC CELL# N/A MODE ENABLED SITE: 0 OBJECT: GAUGE ALARM SEVERITY NO ALARM ALARM THRESHOLD N/A

------------------------------------- ---------- ---------- ---------

Example 2
This example displays the properties associated with the TOTAL_CALLS counter statistic for cell number 5 4 3 2 1 61698 34776 at site 1. disp_stat_prop total_calls cell_number= 5 4 3 2 1 61698 34776 Where: total_calls 5 4 3 2 1 61698 34776 is: meas_type cell_desc

System response
STATISTIC: TOTAL_CALLS TYPE: PER CELL CELL# 543 21 61698 (f102h) 34776 (87d8h) MODE ENABLED SITE: 1 OBJECT: COUNTER ALARM SEVERITY NO ALARM ALARM THRESHOLD N/A

------------------------------------- ---------- ---------- ---------

Example 3
This example shows the properties associated with the ROUTING_UNKNOWN counter statistic for site 1. disp_stat_prop routing_unknown 1 Where: routing_unknown 1 is: meas_type location

5-26

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Examples

System response
STATISTIC: ROUTING_UNKNOWN N/A SITE: 0 CELL #: LAC = f222h Max.: 5 OBJECT: COUNTER ALARM CELL# MODE SEVERITY ALARM THRESHOLD MEAS_TYPE: CHANNELS_DISABLED Gauge Value: 5 TYPE: OTHER ENABLED CI = 8880h SITE: 1 WARNING 2147836

------------------------------------- ---------- ---------- ---------

Example 4
This example displays the properties associated with the TOTAL_CALLS counter statistic for all cells at site 1. disp_stat_prop total_calls 1 all Where: total_calls 1 all is: meas_type location all cells at the specified location.

System response
STATISTIC: TOTAL_CALLS TYPE: PER CELL CELL# 543 21 543 21 543 21 543 21 543 21 61698 (f102h) 34776 (87d8h) 61698 (f102h) 34777 (87d9h) 61698 (f102h) 34778 (87dah) 61698 (f102h) 34779 (87dbh) 61698 (f102h) 34780 (87dch) MODE ENABLED ENABLED ENABLED ENABLED ENABLED SITE: 1 OBJECT: COUNTER ALARM SEVERITY NO ALARM NO ALARM NO ALARM NO ALARM NO ALARM ALARM THRESHOLD N/A N/A N/A N/A N/A

------------------------------------- ---------- ---------- ---------

68P02901W23-S

5-27 Nov 2009

Examples

Chapter 5: Statistics commands

Example 5
This example displays the properties of the GPRS_CELL_CONGESTION counter array statistic. disp_stat_prop GPRS_CELL_CONGESTION cell 0 0 1 0 0 1 1 Where: GPRS_CELL_CONGESTION 0010011 is: meas_type cell_desc

System response
STATISTIC: GPRS_CELL_CONGESTION TYPE: PER CELL BIN# ---0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 CELL# 0 0 1 0 0 1 1 CAUSE ----->=0, >=25, >=35, >=40, >=50, >=55, >=65, >=70, >=80, >=85, <25% <30% <40% <45% <55% <60% <70% <75% <85% <90% SITE: 1 OBJECT: COUNTER ARRAY

>=30%, <35%

>=45%, <50%

>=60%, <65%

>=75%, <80%

>=90%, <95% >=95%, <=100% MODE DISABLED ALARM SEVERITY NO ALARM ALARM THRESHOLD N/A

------------------------------------------------------------------------

Example 6
{28337} This example displays the properties of the BSS MTP_SL_ERROR_RATE_HSP statistics. disp_stat_prop MTP_SL_ERROR_RATE_HSP

5-28

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Examples

System response
STATISTIC: MTP_SL_ERROR_RATE_HSP SITE: 0 TYPE: PER Link CELL# OBJECT: COUNTER MODE ALARM SEVERITY ALARM THRESHOLD

------------------------------------------------------------N/A ENABLED MAJOR 50

Example 7
{22266} This example displays the properties of the link statistic: RSL_TX_OCTETS. disp_stat_prop RSL_TX_OCTETS

System response
STATISTIC: RSL_TX_OCTETS TYPE: PER Link CELL# SITE: 0 OBJECT: COUNTER MODE ALARM SEVERITY ALARM THRESHOLD

------------------------------------------------------------N/A ENABLED NO ALARM N/A

Example 8
{25867} This example displays the properties of the timeslot statistic. disp_stats 10 RF_LOSSES_TCH cell_number=0 0 1 0 1 1 1 Where: rf_losses_tch 10 0010111 is: stat_name location cell_desc

68P02901W23-S

5-29 Nov 2009

Examples

Chapter 5: Statistics commands

System response
STATISTIC: RF_LOSSES_TCH SITE: 11 RTF ID: 0 0 SITE: 11 TIMESLOT: 0 CELL #: LAC=0001h CI=000Bh RTF ID = 0 0 SITE: 1

CELL #: LAC=0001h CI=000Bh

MEAS_TYPE: RF_LOSSES_TCH Total Count: 0 RX quality in uplink direction RX quality in downlink direction RX level in uplink direction RX level in downlink direction Timing Advance Sharp decrease of signal level Other : 0 : 0 : 0 : 0 : 0 : 0 : 0

Example 9
{23292} This example displays the properties of the UL_TBF_TIME_8PSK_3_TS cell statistic. disp_stat_prop UL_TBF_TIME_8PSK_3_TS cell 0 0 1 0 1 1 1 Where: UL_TBF_TIME_8PSK_3_TS 0010111 is: meas_type cell_desc

System response
STATISTIC: UL_TBF_TIME_8PSK_3_TS TYPE: PER CELL CELL# SITE: 1 OBJECT: COUNTER MODE ALARM SEVERITY ALARM THRESHOLD

----------------------------------------------------------------001 01 1 (0001h) 1 (0001h) ENABLED NO ALARM N/A

5-30

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Examples

Example 10
{26881} This examples displays the properties of the cell statistic: EXT_UL_USF_USAGE. disp_stat_prop EXT_UL_USF_USAGE cell 0 0 1 0 1 1 1 Where: ext_ul_usf_usage 0010111 is: stat_name cell_desc

System response
STATISTIC: EXT_UL_USF_USAGE TYPE: PER CELL CELL# SITE: 1 OBJECT: SMALL COUNTER ARRAY MODE ALARM SEVERITY ALARM THRESHOLD

------------------------------------------------------------------001 01 1 (0001h) 1 (0001h) ENABLED NO ALARM N/A

Example 11
{31565} This example displays the properties of the cell statistic IA_IAR_MSGS_PER_AGCH. disp_stat_prop IA_IAR_MSGS_PER_AGCH cell 0 0 1 0 1 1 1 Where: IA_IAR_MSGS_PER_AGCH 0010111 is: meas_type cell_desc

68P02901W23-S

5-31 Nov 2009

Examples

Chapter 5: Statistics commands

System response
STATISTIC: IA_IAR_MSGS_PER_AGCH TYPE: PER CELL BIN# 0 1 2 3 4 5 6 7 CELL# CAUSE IA CS messages sent over CCCH IA PS messages sent over CCCH IAR CS messages sent over CCCH IAR PS messages sent over CCCH IA CS messages discarded IA PS messages discarded IAR CS messages discarded IAR PS messages discarded MODE ALARM SEVERITY ALARM THRESHOLD SITE: 1 OBJECT: COUNTER ARRAY

------------------------------------------------------------------------------

-----------------------------------------------------------------------------001 01 1(0001h) 1(0001h) DISABLED NO ALARM N/A

Example 12
{33397} This example displays the properties of the cell statistic CS_PAGING_MSGS_FROM_MSC. disp_stat_prop CS_PAGING_MSGS_FROM_MSC cell 0 0 1 0 1 1 1 Where: CS_PAGING_MSGS_FROM_MSC 0010111 is: meas_type cell_desc

5-32

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

References

System response
STATISTIC: CS_PAGING_MSGS_FROM_MSC TYPE: PER CELL BIN# 0 1 2 3 4 5 6 CELL# ----001 01 1 (0001h) 1 (0001h) CAUSE Received paging messages on SCCP_Pre MTL-LCF Received paging messages on SCCP_Pre RSL-LCF Received paging messages on RRSM Received paging messages on RSS Abis Received paging messages on RSS L1 Discarded paging messages on SCCP_Pre RSL-LCF due to Cell OOS Discarded paging messages exceed max_pagenum_per_sec MODE ----ENABLED ALARM BIN ----N/A ALARM SEVERITY ----N/A ALARM THRESHOLD ----N/A SITE: 1 OBJECT: COUNTER ARRAY

References
Related commands
disp_element on page 3-272 stat_mode on page 5-48 disp_enable_stat on page 5-12 disp_interval on page 5-22 disp_stats on page 5-34

68P02901W23-S

5-33 Nov 2009

disp_stats

Chapter 5: Statistics commands

disp_stats

Description
The disp_stats command displays statistics associated with an individual cell or board for a valid interval. Security level Supported by OMC-R GUI Command type Prerequisites 1 No A (no operator actions) This command is not allowed while in SYSGEN ON mode. The GPRS feature must be unrestricted to display PCU statistics. The EGPRS feature must be unrestricted to display EGPRS associated statistics.

Format
Syntax
disp_stats <meas_type> disp_stats <interval> <meas_type> [<cell_desc>] disp_stats <interval> <meas_type> [board_id=<board_id>]

Input parameters
interval This value must be a completed statistical interval. The current interval may not be entered for this parameter. Statistical intervals are time periods measured from the system startup. Statistical intervals are numbered sequentially from 0 to 11. The interval length is changed using the chg_element command and displayed using the disp_element command. The first interval at start-up is 0 with a default length of 30 minutes. The disp_interval command displays the completed and current intervals. meas_type Specifies the name of the statistic.

5-34

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Examples

cell_desc The GSM cell ID indicating from which cell to display statistics, preceded by cell_number=. The cell_desc is specified only for a per cell, per timeslot, or per neighbor cell statistic. The format for the GSM cell ID depends on: The system used (PGSM, EGSM, DCS1800, PCS1900, or GSM850). Whether the seven parameter GSM cell ID format or the four parameter GSM cell ID format has been enabled.

The name of the cell created using the cell_name command may be entered in place of the cell_number. When the cell name is entered, place inside double quotation marks and precede by cell_name=.

NOTE
This command responds to the shortened input parameter cell= allowing entry of either the cell_number or the cell_name without further definition.

board_id Specifies the GPROC for statistics collection. The board_id is specified only for a per link statistic. When using disp_stats to display a per link statistic, the output generated reports all links for a specified board.

Examples
Example 1
The following example shows the display of a counter array statistic for a cell number in seven parameter format: disp_stats 5 out_ho_cause_atmpt cell_number= 5 4 3 2 1 61986 34944 Where: 5 out_ho_cause_atmpt 5 4 3 2 1 61986 34944 is: interval meas_type cell_desc

The following example shows the same cell number in four parameter format: disp_stats 5 out_ho_cause_atmpt 543 21 61986 34944

68P02901W23-S

5-35 Nov 2009

Examples

Chapter 5: Statistics commands

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 Congestion Adjacent Channel Interference Band Re-assignment : 10 : 20 : 10 : 10 : 10 : 10 : 10 : 10 : 10 : 10 : 0

Example 2
The following example displays the EGPRS_64K_NOT_AVAIL counter statistic that requires a cell_desc: disp_stats 1 egprs_64k_not_avail cell_number= 5 4 3 2 1 61986 34944 Where: 1 egprs_64k_not_avail 5 4 3 2 1 61986 34944 is: interval meas_type cell_desc

System response
SITE: 1 CELL #: LAC = f222h CI = 8880h

MEAS_TYPE : EGPRS_64 K_NOT_AVAIL Counter : 100

5-36

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Examples

Example 3
The following example displays a weighted distribution statistic that requires a cell_desc: disp_stats 1 busy_tch cell_number= 5 4 3 2 1 61986 34944 Where: 1 busy_tch 5 4 3 2 1 61986 34944 is: interval meas_type cell_desc

Values represented in the bins are time values expressed in milliseconds

System response
SITE: 0 CELL #: LAC = f222h CI = 8880h

MEAS_TYPE : BUSY_TCH Distribution Mean : 0 Distribution Max Distribution Min : 1 : 0

Bin : 82260 217730 0 0 0 0 0 0 0 0

Example 4
The following example displays the AVAILABLE_TCH gauge statistic that requires a cell_desc: disp_stats 4 available_tch cell_number= 5 4 3 2 1 61986 34944 Where: 4 available_tch 5 4 3 2 1 61986 34944 is: interval meas_type cell_desc

System response
SITE: 0 CELL #: LAC = f222h Max. : 5 CI = 8880h

MEAS_TYPE : AVAILABLE_TCH Gauge Value : 5

68P02901W23-S

5-37 Nov 2009

Examples

Chapter 5: Statistics commands

Example 5
The following example displays a normal distribution statistic that requires a cell_desc because it is a timeslot statistic: disp_stats 0 ber cell_number= 0 0 1 0 1 1 6 Where: 0 ber 0010116 is: interval meas_type 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 SITE:1 CELL #:LAC = 0001h CI = 0006h Distribution Min CELL #:LAC = 0001h CI = 0006h : 0

RTF ID: 1 1 TIMESLOT: 1 RTF ID = 1 1 MEAS_TYPE : BER Distribution Mean : 0 Distribution Max Distribution Min SITE:1 : 0 : 0

Bin : 0 0 0 0 0 0 0 0 0 0 CELL #:LAC = 0001h CI = 0006h TIMESLOT: 5 RTF ID = 1 1 MEAS_TYPE: BER Distribution Mean : 0 Distribution Max : 0 Bin : 0 0 0 0 0 0 0 0 0 0

Example 6
The following example displays a related statistic when CS-3, CS-4, and 32 kbit/s GPRS TRAU are enabled: disp_stats 1 gprs_32k_channels_switched cell_number= 1 2 3 4 5 6 7 Where: 1 gprs_32k_channels_switched 1234567 is: interval meas_type cell_desc

5-38

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Examples

System response
SITE: 5 CELL #: LAC = 6 13 CI= 7

MEAS_TYPE:

GPRS_32 K_CHANNELS_SWITCHED

GPRS_CHANNELS_SWITCHED:

Example 7
This example displays statistics for PRP_LOAD for all PCUs equipped at the BSC. disp_stats 3 prp_load Where: 3 prp_load is: interval meas_type

System response
PCU: 0 DPROC Board #: 4356 (ox1104)

MEAS_TYPE: PRP_LOAD Distribution Mean : 0 Distribution Max Distribution Min Bin PCU: 1 : 0 : 0 (ox1104)

: 0 0 0 0 0 0 0 0 0 0 DPROC Board #: 4356

MEAS_TYPE: PRP_LOAD Distribution Mean : 0 Distribution Max Distribution Min Bin PCU : 2 : 0 : 0 (ox1104)

: 0 0 0 0 0 0 0 0 0 0 DPROC Board #: 4356

MEAS_TYPE: PRP_LOAD Distribution Mean : 0 Distribution Max Distribution Min Bin : 0 : 0

: 0 0 0 0 0 0 0 0 0 0

68P02901W23-S

5-39 Nov 2009

Examples

Chapter 5: Statistics commands

Example 8
This example displays the PDU_DISCARD_FR counter statistic for the PCU 0 GBL link. disp_stat PDU_DISCARD_FR Where: PDU_DISCARD_FR is: meas_type

System response
PCU: 0 GBL Link #: 0

MEAS_TYPE: PDU_DISCARD_FR Counter: 0

Example 9
This example displays PFC_ADMISSION_OTHER statistics for the first interval after system start up at a cell. disp_stats 0 PFC_ADMISSION_OTHER cell 0 0 1 0 1 1 1 Where: 0 PFC_ADMISSION_OTHER 0010111 is: interval meas_type cell_desc

System response
SITE: 1 CELL #: LAC=0001h CI=0001h MEAS_TYPE: PFC_ADMISSION_OTHER Total Count: 6 Admission successful SMS Admission successful Signaling Admission successful PFC_unaware : 1 : 2 : 3

5-40

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Examples

Example 10
This example displays the PACKET_SYSINFO_REQ statistics for the second interval after system start at a cell. disp_stats 1 PACKET_SYSINFO_REQ cell 0 0 1 0 1 1 1 Where: 1 PACKET_SYSINFO_REQ 0010111 is: interval meas_type cell_desc

System response
SITE: 1 CELL #: LAC-0001h CI-0001h MEAS TYPE: PACKET_SYSINFO_REQ Total Count: 9 Valid Request Normal Request for Sys Info: 8 Invalid/Unexpected Request for System Information: 0 Request for System Information Discarded Resource Limit: 0 Valid Request Request for Sys Info Change Marks: 1

Example 11
This example displays the PRP_PD_DEMAND statistics for sixth interval after system startup. disp_stats 5 PRP_PD_DEMAND Where: 5 PRP_PD_DEMAND is: interval meas_type

68P02901W23-S

5-41 Nov 2009

Examples

Chapter 5: Statistics commands

System response
PCU : 0 Gauge Mean : 80 Gauge Max. : 118 PCU : 0 Gauge Mean : 67 Gauge Max. : 110 PCU : 1 Gauge Mean : 80 Gauge Max. : 111 DPROC Board # : 4356 (0x1104) MEAS_TYPE : PRP_PD_DEMAND DPROC Board # : 4356 (0x1104) MEAS_TYPE : PRP_PD_DEMAND DPROC Board # : 4355 (0x1103)

MEAS_TYPE : PRP_PD_DEMAND

Example 12
{28337} The following example displays the value of the BSS MTP_SL_ERROR_RATE_HSP statistic. disp_stats 6 mtp_sl_error_rate_hsp board_id 0113h Where: 6 mtp_sl_error_rate_hsp 0113h is: interval meas_type board description

System response
SITE:0 SITE:0 MEAS_TYPE: Counter: 0 GPROC Board # : 275 (0x0113) MTL Link # : 1 MTP_SL_ERROR_RATE_HSP

5-42

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Examples

Example 13
{28351} The following example displays the value of the BSS: PSI_TRAU_FILL_FRAME_TX statistic. disp_stats 0 PSI_TRAU_FILL_FRAME_TX Where: 0 psi_trau_fill_frame_tx is: interval meas_type

System response
SITE: 0 PSI Board #: 0107 ETH Port #: 0 MEAS TYPE: PSI_TRAU_FILL_FRAME_TX Counter: 145

Example 14
{22266} The following example displays the link statistic: RSL_TX_OCTETS. disp_stats 0 RSL_TX_OCTETS board_id=0118h Where: 0 rsl_tx_octets 0118h is: interval meas_type board_id

System response
SITE: 0 GPROC Board#: 280 (0x0118)

SITE: 62 RSL Link # :0 MEAS TYPE: RSL_TX_OCTETS Counter: 100

68P02901W23-S

5-43 Nov 2009

Examples

Chapter 5: Statistics commands

Example 15
{23292} The following example displays the UL_TBF_TIME_GMSK_3_TS cell statistics. disp_stats 1 UL_TBF_TIME_GMSK_3_TS cell 0 0 1 0 1 1 1 Where: 1 ul_tbf_time_gmsk_3_ts 0010111 is: interval meas_type cell_desc

System response
SITE: 1 Counter: CELL #: LAC=0001h CI=0001h 100

MEAS TYPE: UL_TBF_TIME_GMSK_3_TS

Example 16
{23292} This example displays the properties of the UL_RADIO_BLKS_GMSK_3_TS cell statistics. disp_stats 1 UL_RADIO_BLKS_GMSK_3_TS 0 0 1 0 1 1 1 Where: 1 ul_radio_blks_gmsk_3_ts 0010111 is: interval meas_type cell_desc

5-44

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Examples

System response
SITE: 1 CELL #: LAC=0001h CI=0001h

MEAS TYPE: UL_RADIO_BLKS_GMSK_3_TS Total count: 3175 GPRS coding scheme 1 GPRS coding scheme 2 GPRS coding scheme 3 GPRS coding scheme 4 EGPRS modulation and coding scheme 1 EGPRS modulation and coding scheme 2 EGPRS modulation and coding scheme 3 EGPRS modulation and coding scheme 4 :0 :2 :1 :3172 :0 :0 :0 :0

Example 17
{31565} The following example displays the cell statistic IA_IAR_MSGS_PER_AGCH. disp_stats 1 IA_IAR_MSGS_PER_AGCH cell_number= 0 0 1 0 1 1 1 Where: 1 IA_IAR_MSGS_PER_AGCH 0010111 is: interval meas_type cell_desc

68P02901W23-S

5-45 Nov 2009

Examples

Chapter 5: Statistics commands

System response
SITE: 1 CELL #: LAC-0001h CI-0001h 8 Sub-Counter Value 1 1 1 1 1 1 1 1

MEAS TYPE: IA_IAR_MSGS_PER_AGCH Total counter: BIN# Cause

0 1 2 3 4 5 6 7

IA CS messages sent over CCCH IA PS messages sent over CCCH IAR CS messages sent over CCCH IAR PS messages sent over CCCH IA CS messages discarded IA PS messages discarded IAR CS messages discarded IAR PS messages discarded

Example 18
{33397} The following example displays the cell statistic CS_PAGING_MSGS_FROM_MSC. disp_stats 1 CS_PAGING_MSGS_FROM_MSC cell_number= 0 0 1 0 1 1 1 Where: 1 CS_PAGING_MSGS_FROM_MSC 0010111 is: interval meas_type cell_desc

5-46

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

References

System response
SITE: 0 CELL #: LAC-0001h CI-0001h 7 Sub-Counter Value MTL-LCF RSL-LCF 1 1 1 1 1 RSL-LCF due 1

MEAS TYPE: CS_PAGING_MSGS_FROM_MSC Total counter: BIN# Cause

0 1 2 3 4 5

received paging messages on SCCP_Pre received paging messages on SCCP_Pre received paging messages on RRSM received paging messages on RSS Abis received paging messages on RSS L1 discarded paging messages on SCCP_Pre to Cell OOS

discarded paging messages exceeds max_pagenum_per_sec

References
Related commands
disp_element on page 3-272 stat_mode on page 5-48 disp_enable_stat on page 5-12 disp_interval on page 5-22

68P02901W23-S

5-47 Nov 2009

stat_mode

Chapter 5: Statistics commands

stat_mode

Description
The stat_mode command enables or disables individual statistics in the CM database. The statistical applications of the stat_mode command permit multiple interactions with the same database element to define the statistical data. This permits flexibility in the definition of the parameters.

NOTE
The stat_mode command replaces the chg_element command for enabling or disabling statistics. The chg_stat_prop command replaces the chg_element for modifying a statistic.

Security level Supported by OMC-R GUI Command type Prerequisites

4 Yes A (no operator actions) The GPRS feature must be unrestricted to enable GPRS associated statistics. The EGPRS feature must be unrestricted to enable EGPRS associated statistics.

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

Format
Syntax
stat_mode <meas_type> <mode> [<location>] [<cell_desc>] stat_mode <meas_type> <mode> all stat_mode <meas_type> <mode> <location> all

5-48

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Format

Input parameters
meas_type Specifies the name of the statistic. mode Specifies the mode of the statistic: on off location Specifies the site location: 0 or bsc 1 - 140 all 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. BSC BTS All sites Enable Disable

The name of the cell created using the cell_name command may be entered in place of the cell_number. When the cell name is entered, place inside double quotation marks and precede by cell_name=.

NOTE
This command responds to the shortened input parameter cell= allowing entry of either the cell_number or the cell_name without further definition. The value all is also a valid input for the cell_desc. If entered, the mode for the statistic changes for all cells at the specified site.

68P02901W23-S

5-49 Nov 2009

Examples

Chapter 5: Statistics commands

Examples
Example 1
This example enables the TBF_SESSIONS statistic. stat_mode TBF_SESSIONS on Where: TBF_SESSIONS on is: meas_type mode

System response
COMMAND ACCEPTED

Example 2
This example enables the TIMER_EXP_PAP_CONV statistic for cell 0 0 1 0 1 1 1. stat_mode TIMER_EXP_PAP_CONV on cell 0 0 1 0 1 1 1 Where: TIMER_EXP_PAP_CONV on 0010111 is: meas_type mode cell_desc

System response
COMMAND ACCEPTED

Example 3
This example enables the TOTAL_CALLS statistic for cell number 5 4 3 2 1 61698 34776 at site 1. stat_mode total_calls on 1 cell_number= 5 4 3 2 1 61698 34776 Where: total_calls on 1 5 4 3 2 1 61698 34776 is: meas_type mode location cell_desc

5-50

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Examples

System response
COMMAND ACCEPTED

Example 4
This example enables all CELL statistic for all cells except NCELL stats at site 1. stat_mode all on 1 all Where: all on 1 all is: meas_type mode location cell_desc

System response
COMMAND ACCEPTED

Example 5
This example enables all BSS statistic. stat_mode all on Where: all on is: meas_type mode

System response
COMMAND ACCEPTED

68P02901W23-S

5-51 Nov 2009

Examples

Chapter 5: Statistics commands

Example 6
This example disables the TOTAL_CALLS statistic for all cells at site 1. stat_mode total_calls off 1 all Where: total_calls off 1 all is: meas_type mode location all cells at the specified site

System response
COMMAND ACCEPTED

Example 7
This example enables the GPRS_32K_CHANNELS_SWITCHED statistic for all cells at site 1. stat_mode gprs_32k_channels_switched on 1 all Where: gprs_32k_channels_switched on 1 all is: meas_type mode location cell_desc

System response
COMMAND ACCEPTED

Example 8
{28337} This example disables the SS7 link MTP_SL_ERROR_RATE_HSP statistic. stat_mode MTP_SL_ERROR_RATE_HSP on Where: mtp_sl_error_rate_hsp on is: meas_type mode

5-52

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Examples

System response
COMMAND ACCEPTED

Example 9
{28351} This example enables the BSS PSI_TRAU_FILL_FRAME_TX statistic. stat_mode PSI_TRAU_FILL_FRAME_TX on Where: psi_trau_fill_frame_tx on is: meas_type mode

System response
COMMAND ACCEPTED

Example 10
{22266} This example enables or disables individual statistics. stat_mode RSL_TX_OCTETS on Where: rsl_tx_octets on is: meas_type mode

System response
COMMAND ACCEPTED

68P02901W23-S

5-53 Nov 2009

Examples

Chapter 5: Statistics commands

Example 11
{25867} This example enables the timeslot statistic RF_LOSSES_TCH. stat_mode RF_LOSSES_TCH on 1 cell_number=0 0 1 0 1 1 1 Where: rf_losses_tch on 1 0010111 is: meas_type mode location cell_desc

System response
COMMAND ACCEPTED

Example 12
{27703A} This example enables the statistics for cell 0 0 1 0 1 1 1 when QoS feature is unrestricted. stat_mode PFC_ADMISSION_TRAFFIC_CLASS on cell 0 0 1 0 1 1 1 Where: PFC_ADMISSION_TRAFFIC_CLASS on 0010111 is: meas_type mode cell_desc

System response
COMMAND ACCEPTED

5-54

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Examples

Example 13
{33863} This example enables the CELL statistic UL_RLC_STALLED_BLKS when GPRS features are unrestricted. stat_mode UL_RLC_STALLED_BLKS on cell 0 0 1 0 1 1 1 Where: UL_RLC_STALLED_BLKS on 0010111 is: meas_type mode cell_desc

System response
COMMAND ACCEPTED

Example 14
{23292} This example enables the cell statistic UL_RADIO_BLKS_8PSK_3_TS when EDA and EGPRS feature is unrestricted. stat_mode UL_RADIO_BLKS_8PSK_3_TS on cell 0 0 1 0 1 1 1 Where: ul_radio_blks_8psk_3_ts on 0010111 is: meas_type mode cell_desc

System response
COMMAND ACCEPTED

68P02901W23-S

5-55 Nov 2009

Examples

Chapter 5: Statistics commands

Example 15
{31565} This example enables the BSS statistic IA_IAR_MSGS_PER_AGCH. stat_mode IA_IAR_MSGS_PER_AGCH on 1 cell_number=0 0 1 0 1 1 1 Where: IA_IAR_MSGS_PER_AGCH on 1 0010111 is: meas_type mode location cell_desc

System response
COMMAND ACCEPTED

Example 16
{33397} This example enables the cell statistic CS_PAGING_MSGS_FROM_MSC. stat_mode CS_PAGING_MSGS_FROM_MSC on cell_number=0 0 1 0 1 1 1 Where: CS_PAGING_MSGS_FROM_MSC on 0010111 is: meas_type mode cell_desc

System response
COMMAND ACCEPTED

5-56

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

References

Example 17
{33780} This example enables the cell statistic UL_LLC_DATA_VOLUME when GPRS features are unrestricted. stat_mode UL_LLC_DATA_VOLUME on cell 0 0 1 0 1 1 1 Where: UL_LLC_DATA_VOLUME on 0010111 is: meas_type mode cell_desc

System response
COMMAND ACCEPTED

References
Related commands
disp_element on page 3-272 disp_enable_stat on page 5-12 disp_interval on page 5-22 disp_stats on page 5-34

68P02901W23-S Nov 2009

5-57

References

Chapter 5: Statistics commands

5-58

68P02901W23-S Nov 2009

Chapter

6
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-S Nov 2009

6-1

CM database parameters presentation

Chapter 6: CM database parameters

CM database parameters presentation

The layout of the CM database parameters reference information is explained in the following section.

Parameter reference
The actual CM database parameter reference appears at the head of the page, and is reproduced in the contents and the index of this manual.

Description
The function of the CM database parameter is described briefly. Dependencies on other database elements and system functions are included in the description.

Type
CM database parameters are classified as Type A or Type B where: Type A parameters do not require additional operator actions when the parameter value is changed. Type B parameters require additional operator actions when the parameter value is changed. The specific action required is described in the Operator actions field.

OMC-R GUI support

Indicates if a database parameter can be changed using the OMC-R GUI (Graphics User Interface). If a value is not supported through the OMC-R GUI, it can be changed by performing a remote login (rlogin) from the OMC-R or at the site using a PC connected to the master GPROC.

Cell description required

Indicates whether the CM database parameter affects specific cells and requires the GSM cell ID numbers to be included in the command syntax when the parameter is displayed or changed.

Dependencies
Describes any database internal or external dependencies which may affect value assignments of the database parameter. Consider these dependencies when changes are made to the parameter.

6-2

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Syntax

Operator actions
The specific actions required when changing Type B parameters are listed, including any precautions that are appropriate.

Syntax
Add/change command strings
The command syntax used to assign or change values to a parameter is provided to assist the operator in entering the command. The command name, the parameter name, indices (if required), the new element value, and the location affected are included in the command syntax. The add_name command is included where an element is initially assigned using the add_cell command and modified using other commands. The individual add_cell command prompts are listed in the description of the add_cell command.

Display command strings

The command syntax used to display the database element value is provided to assist the operator in entering the command. The command name, the parameter name, indices (if required), and the location are included in the command syntax.

Values
The value types and valid ranges for the database values are listed for each parameter. Values for some elements are expressed as steps representing incremental values.

Default values
Default values are available for some parameters. The add_cell command default values are selected by typing the parameter name and the equal sign than pressing the return key in response to a parameter prompt. Some parameters are assigned default values when the database is initially loaded. This default value may only be displayed by using the disp_element command before the database parameter is changed for the first time. The default value may be changed by using the appropriate change command.

Invalid value
If an invalid value is entered while using the add_cell command, the MMI uses the default value if there is one present. If there is no default value, the MMI displays an error message then abandons the add_cell command. If an invalid value is entered when using the chg_element command, the command is abandoned and an error message presented. The original value of the parameter remains unchanged.

68P02901W23-S

6-3 Nov 2009

References

Chapter 6: CM database parameters

References
The following information is given when required.

GSM parameter
Where a parameter is assigned a name that is different from the name assigned in the GSM Technical Specifications, the name assigned to the parameter by the GSM Technical Specifications is listed as a cross reference.

GSM technical specifications

The source GSM document used to define the parameter is listed as a reference.

6-4

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

_bss_data,2

Description
The _bss_data,2 parameter is used to enable the MMS Lock Persistency feature.

NOTE
The NVRAM MMS Lock data is always stored and updated. However, the data can be used only when the MMS Lock Persistency feature is enabled using the _bss_data,2 parameter. If BSP/GPROC is pulled out from the site for several months and placed in storage, then care should be taken with MMS Lock Persistency.

Type Supported by OMC-R GUI Cell description required Dependencies

A (no operator actions) No No None

Syntax
Change command string
chg_element _bss_data,2 <value> <location>

Display command string

disp_element _bss_data,2 <location>

Values
Value type Valid range Boolean 0 or 1 0 1 Default value 0 Disabled Enabled

68P02901W23-S

6-5 Nov 2009

_cell_data,20

Chapter 6: CM database parameters

_cell_data,20

{31565}

Description
The _cell_data,20 parameter indicates whether the functionality of the AGCH flow control is enabled. The parameter also indicates the triggers associated with IA or IAR that can trigger AGCH overload. This parameter may be changed inside and outside SYSGEN mode without warning. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) No No None

Syntax
Change command string
chg_element _cell_data,20 <element-value> <location>

Display command string

disp_element _cell_data,20 <location>

6-6

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Values

Values
Value type Valid range Integer 0 to 2 0 1 AGCH flow control function is disabled. AGCH flow control function is enabled, any one of the triggers associated with IA and IAR can trigger AGCH overload. AGCH flow control function is enabled, while only the trigger associated with IA can trigger AGCH overload.

Default value

68P02901W23-S

6-7 Nov 2009

_site_data, 5

Chapter 6: CM database parameters

_site_data, 5

{34303}

Description
The _site_data, 5 parameter is used to enable or disable the Horizon I or Horizon II BTS to connect to the Abis interface. For other BTS types, this element is always set to Abis_Disable. This parameter may be changed outside SYSGEN mode. Type Supported by OMC-R GUI Cell description required Dependencies B (operator actions required) No No This parameter can only be modified if the Dual Abis Aware BTS feature is enabled.

Values
Value type Valid range Integer 0 2 Default value 0 Minimum Maximum

NOTE
0 = Abis_Disable Disables the Abis connection to the BSC6. 1 = Abis_Enable_Conv Enables the Abis connection control for the BTS. 2 = Abis_Enable_CSFP Enables the Abis connection control for the BTS when the BTS has the CSFP download the full Abis load from the BSC2.

6-8

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

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 Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No The ECERM feature must be enabled. Two successful calls are required to clear an alarm within this threshold. (One call can be too short for the Channel Coder Unit (CCU) to send an error indication, thus clearing the alarm prematurely.) This parameter can be set only at a BSC. If the threshold is increased during operation, any existing counts between the new and the old threshold do not clear an alarm until another successful call is made on the ACI. (aci_error_gen_thresh - aci_error_clr_threshold) >= 2

Syntax
Change command string
chg_element aci_error_clr_thresh <value> 0

Display command string

disp_element aci_error_clr_thresh 0

Values
Value type Valid range Default value Integer 0 to 253 0

68P02901W23-S

6-9 Nov 2009

aci_error_gen_thresh

Chapter 6: 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 Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No The ECERM feature must be enabled. This parameter can be set only at a BSC. If the threshold is reduced during operation, any existing counts between the new and the old threshold does not cause an alarm. (aci_error_gen_thresh - aci_error_clr_thresh) >= 2.

Syntax
Change command string
chg_element aci_error_gen_thresh <value> 0

Display command string

disp_element aci_error_gen_thresh 0

Values
Value type Valid range Default value Integer 2 to 255 6

6-10

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

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 Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No The ECERM feature must be enabled. This parameter applies only to the BSC.

Syntax
Change command string
chg_element aci_error_inc <value> 0

Display command string

disp_element aci_error_inc 0

Values
Value type Valid range Integer 0 1 to 255 Default value 0 1 ACI alarms not raised. ACI alarms raised. If ECERM feature is disabled. If ECERM feature is enabled.

68P02901W23-S

6-11 Nov 2009

adap_ho_alt_trigger_rxqual

Chapter 6: 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 Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes None

Syntax
Change command strings
chg_element adap_ho_alt_trigger_rxqual <value> <location> <cell_desc> chg_cell_element adap_ho_alt_trigger_rxqual <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full] disp_element adap_ho_alt_trigger_rxqual <location> <cell_desc>

Values
Value type Valid range Boolean 0 or 1 0 1 Default value 0 Do not use hopping specific thresholds. Use hopping specific thresholds.

6-12

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

adap_ho_pbgt

Description
The adap_ho_pbgt parameter specifies whether the system allows adaptive power budget handovers. The cumulative area for the adaptive power budget handovers can be defined as per cell or per neighbor. At each measurement report, the cumulative area are updated and compared to a cumulative trigger. If the area is greater than the cumulative power budget trigger (pbgt), a need for a handover is recognized. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes None

Syntax
Change command strings
chg_element adap_ho_pbgt <value> <location> <cell_desc> chg_cell_element adap_ho_pbgt <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full] disp_element adap_ho_pbgt <location> <cell_desc>

68P02901W23-S

6-13 Nov 2009

Values

Chapter 6: CM database parameters

Values
Value type Valid range Integer 0 to 2 0 1 2 Default value 0 Disables adaptive power budget handovers at the location. Enables adaptive power budget handovers at the location using per cell cumulative area. Enables adaptive power budget handovers at the location using per neighbor cumulative area.

6-14

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

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 Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes None

Syntax
Change command strings
chg_element adap_ho_rxlev <value> <location> <cell_desc> chg_cell_element adap_ho_rxlev <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full] disp_element adap_ho_rxlev <location> <cell_desc>

Values
Value type Valid range Boolean 0 or 1 0 1 Default value 0 Disables adaptive receive level handovers at the location. Enables adaptive receive level handovers at the location.

68P02901W23-S

6-15 Nov 2009

adap_ho_rxqual

Chapter 6: 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 Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes None

Syntax
Change command strings
chg_element adap_ho_rxqual <value> <location> <cell_desc> chg_cell_element adap_ho_rxqual <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full] disp_element adap_ho_rxqual <location> <cell_desc>

Values
Value type Valid range Boolean 0 or 1 0 1 Default value 0 Disables adaptive quality handovers at the location. Enables adaptive quality handovers at the location.

6-16

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

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 Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes None

Syntax
Change command strings
chg_element adap_trigger_hop_rxqual_dl <value> <location> <cell_desc> chg_cell_element adap_trigger_hop_rxqual_dl <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full] disp_element adap_trigger_hop_rxqual_dl <location> <cell_desc>

Values
Value type Valid range Default value Integer 0 to 65535 0

68P02901W23-S

6-17 Nov 2009

adap_trigger_hop_rxqual_ul

Chapter 6: 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 Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes None

Syntax
Change command strings
chg_element adap_trigger_hop_rxqual_ul <value> <location> <cell_desc> chg_cell_element adap_trigger_hop_rxqual_ul <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full] disp_element adap_trigger_hop_rxqual_ul <location> <cell_desc>

Values
Value type Valid range Default value Integer 0 to 65535 0

6-18

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

adap_trigger_pbgt

Description
The adap_trigger_pbgt parameter specifies the cumulative trigger level for adaptive power budget handovers. When the threshold set by adap_trigger_pbgt is exceeded, the system triggers a handover to a better cell. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes None

Syntax
Change command strings
chg_element adap_trigger_pbgt <value> <location> <cell_desc> chg_cell_element adap_trigger_pbgt <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full] disp_element adap_trigger_pbgt <location> <cell_desc>

Values
Value type Valid range Default value Integer 0 to 255 0

68P02901W23-S

6-19 Nov 2009

adap_trigger_pbgt_nbr

Chapter 6: 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 set by adap_trigger_pbgt_nbr is exceeded, the system triggers a handover to a better cell. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No This parameter is invalid when ba_type is ba_bcch or ba_gprs.

Syntax
Change command string
modify_neighbor <src_cell_id> <neighbor_cell_id> adap_trigger_pbgt_nbr <value>

Display command string

disp_neighbor <src_cell_id> [<neighbor_cell_id>|all]

Values
Value type Valid range Default value Integer 0 to 255 40 (the value of 40 corresponds to a hreqave of 8 and a handover margin of 5)

6-20

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

adap_trigger_rxlev_dl

Description
The adap_trigger_rxqual_dl parameter specifies the cumulative trigger level for adaptive receive level downlink handovers. When the threshold set by this parameter is exceeded, the system performs a downlink strength handover. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes None

Syntax
Change command strings
chg_element adap_trigger_rxlev_dl <value> <location> <cell_desc> chg_cell_element adap_trigger_rxlev_dl <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full] disp_element adap_trigger_rxlev_dl <location> <cell_desc>

Values
Value type Valid range Default value Integer 0 to 255 0

68P02901W23-S

6-21 Nov 2009

adap_trigger_rxlev_ul

Chapter 6: CM database parameters

adap_trigger_rxlev_ul

Description
The adap_trigger_rxlev_ul parameter specifies the cumulative trigger level for adaptive receive level uplink handovers. When the threshold set by this parameter is exceeded, the system performs an uplink strength handover. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes None

Syntax
Change command strings
chg_element adap_trigger_rxlev_ul <value> <location> <cell_desc> chg_cell_element adap_trigger_rxlev_ul <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full] disp_element adap_trigger_rxlev_ul <location> <cell_desc>

Values
Value type Valid range Default value Integer 0 to 255 0

6-22

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

adap_trigger_rxqual_dl

Description
The adap_trigger_rxqual_dl parameter specifies the cumulative trigger level for adaptive rxqual downlink handovers. When the threshold set by this parameter is exceeded, the system performs a downlink quality handover. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes None

Syntax
Change command strings
chg_element adap_trigger_rxqual_dl <value> <location> <cell_desc> chg_cell_element adap_trigger_rxqual_dl <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full] disp_element adap_trigger_rxqual_dl <location> <cell_desc>

Values
Value type Valid range Default value Integer 0 to 65535 0

68P02901W23-S

6-23 Nov 2009

allow_8k_trau

Chapter 6: CM database parameters

allow_8k_trau

Description
The allow_8k_trau parameter enables or disables 8 kbit/s backhaul. A timeslot or smaller portions within a timeslot may represent a port on the switch. A port on the KSW can be a minimum of two bits that equates to four independent 16 kbit/s portions within each timeslot. The KSW can operate in a sub-rate switching mode where each timeslot can independently switch a 16 kbit/s subgroup (one-quarter of a timeslot). The DSW can operate in a sub-rate switching mode where each timeslot can independently switch an 8 kbit/s sub-group (one-eighth of a timeslot). Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No The AMR Enhanced Capability feature and/or GSM Half Rate feature must be enabled. The half_rate_enabled parameter must be enabled. The BTS must be AMR/GSM Half Rate capable. The 7.95 kbit/s codec mode must not be part of the AMR Half-Rate Active Codec Set.

Syntax
Change command string
equip <site_id> RTF

NOTE
After entering this command, the operator is prompted to enable or disable the allow_8k_trau parameter (and other RTF parameters).

Display command string

disp_equipment

6-24

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Values

Values
Value type Valid range Boolean no or yes no yes Default value yes Disabled Enabled

68P02901W23-S

6-25 Nov 2009

alt_qual_proc

Chapter 6: CM database parameters

alt_qual_proc

Description
The alt_qual_proc parameter specifies whether receive quality processing is performed using Bit Error Rate (BER) values or Quality Band (QBand) units. The value assigned to the alt_qual_proc parameter determines the type of values and the range of values of six parameters. The alt_qual_proc parameter value is initially assigned using the add_cell command. The alt_qual_proc parameter for a cell may be changed using the chg_cell_element command. When the chg_cell_element command is used to change the value of the alt_qual_proc parameter, additional prompts are presented for the dependent parameters. Default values may be entered by pressing return at the prompt. If an invalid value is entered, the command is abandoned. The AMR/GSM Half Rate Rxqual Handover and Power Control (HDPC) specific parameters are prompted for when changing the value of alt_qual_proc parameter when AMR and/or GSM Half Rate are unrestricted. AMR Full Rate HDPC parameters are prompted for only when AMR is unrestricted The value that is entered for the alt_qual_proc parameter determines the type of values, range of values, and default values for the dependent cell parameters. If a value of 0 is entered for the alt_qual_proc parameter, the range of values and defaults for the dependent cell parameters is listed in Table 6-1 .

Table 6-1

alt_qual_proc=0 parameter values

Range 0 to 1810 0 to 1810 0 to 1810 0 to 1810 0 to 1810 0 to 1810 0 to 1810 0 to 1810 0 to 1810 0 to 1810 0 to 1810 0 to 1810 Default 226 226 28 28 453 453 0 0 0 0 0 0 Continued

Dependent parameter l_rxqual_ul_p l_rxqual_dl_p u_rxqual_ul_p u_rxqual_dl_p l_rxqual_ul_h l_rxqual_dl_h l_rxqual_dl_h_hopping l_rxqual_ul_h_hopping l_rxqual_dl_p_hopping l_rxqual_ul_p_hopping l_rxqual_dl_h_data l_rxqual_ul_h_data

6-26

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Description

Table 6-1

alt_qual_proc=0 parameter values (Continued)

Range 0 to 1810 0 to 1810 0 to 1810 0 to 1810 0 to 1810 0 to 1810 0 to 1810 0 to 1810 0 to 1810 0 to 1810 0 to 1810 0 to 1810 0 to 1810 0 to 1810 0 to 1810 0 to 1810 0 to 1810 0 to 1810 0 to 1810 0 to 1810 Default 0 0 226 113 453 226 0 0 0 0 57 57 14 14 113 113 113 113 57 57

Dependent parameter l_rxqual_dl_p_data l_rxqual_ul_p_data l_rxqual_ul_p_amr_fr l_rxqual_dl_p_amr_fr l_rxqual_ul_h_amr_fr l_rxqual_dl_h_amr_fr l_rxqual_dl_h_hopping_amr_fr l_rxqual_ul_h_hopping_amr_fr l_rxqual_dl_p_hopping_amr_fr l_rxqual_ul_p_hopping_amr_fr l_rxqual_ul_p_hr l_rxqual_dl_p_hr u_rxqual_ul_p_hr u_rxqual_dl_p_hr l_rxqual_ul_h_hr l_rxqual_dl_h_hr l_rxqual_dl_h_hopping_hr l_rxqual_ul_h_hopping_hr l_rxqual_dl_p_hopping_hr l_rxqual_ul_p_hopping_hr

Table 6-2 lists the range of values and defaults for the dependent parameters if a value of 1 is entered for thealt_qual_proc parameter.

Table 6-2

alt_qual_proc=1 parameter values

Range 0 to 7 0 to 7 0 to 7 0 to 7 0 to 7 0 to 7 0 to 7 0 to 7 0 to 7 Default 4 4 1 1 5 5 4 4 4 Continued

Dependent parameter l_rxqual_ul_p l_rxqual_dl_p u_rxqual_ul_p u_rxqual_dl_p l_rxqual_ul_h l_rxqual_dl_h l_rxqual_dl_h_hopping l_rxqual_ul_h_hopping l_rxqual_dl_p_hopping

68P02901W23-S

6-27 Nov 2009

Description

Chapter 6: CM database parameters

Table 6-2

alt_qual_proc=1 parameter values (Continued)

Range 0 to 7 0 to 7 0 to 7 0 to 7 0 to 7 0 to 7 0 to 7 0 to 7 0 to 7 0 to 7 0 to 7 0 to 7 0 to 7 0 to 7 0 to 7 0 to 7 0 to 7 0 to 7 0 to 7 0 to 7 0 to 7 0 to 7 0 to 7 B (operator actions required) Yes Yes The value that is entered for the alt_qual_proc parameter determines the type of values, the range of values, and the default values for the dependent parameters. Respond to the parameters that are presented when the chg_cell_element command is used to change the value of the alt_qual_proc parameter. Default 4 4 4 4 4 4 3 5 4 5 6 4 5 2 2 0 0 3 3 3 3 2 2

Dependent parameter l_rxqual_ul_p_hopping l_rxqual_dl_h_data l_rxqual_ul_h_data l_rxqual_dl_p_data l_rxqual_ul_p_data l_rxqual_ul_p_amr_fr l_rxqual_dl_p_amr_fr l_rxqual_ul_h_amr_fr l_rxqual_dl_h_amr_fr l_rxqual_dl_h_hopping_amr_fr l_rxqual_ul_h_hopping_amr_fr l_rxqual_dl_p_hopping_amr_fr l_rxqual_ul_p_hopping_amr_fr l_rxqual_ul_p_hr l_rxqual_dl_p_hr u_rxqual_ul_p_hr u_rxqual_dl_p_hr l_rxqual_ul_h_hr l_rxqual_dl_h_hr l_rxqual_dl_h_hopping_hr l_rxqual_ul_h_hopping_hr l_rxqual_dl_p_hopping_hr l_rxqual_ul_p_hopping_hr Type Supported by OMC-R GUI Cell description required Dependencies

Operator actions

6-28

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Syntax

Syntax
Change command strings
add_cell <gsm_cell_id> <location> chg_cell_element alt_qual_proc <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> full disp_element alt_qual_proc <location> <cell_desc>

Values
Value type Valid range Boolean 0 or 1 0 1 Default value 0 BER units Qb and units

68P02901W23-S

6-29 Nov 2009

amr_bss_half_rate_enabled

Chapter 6: CM database parameters

amr_bss_half_rate_enabled

Description
The amr_bss_half_rate_enabled parameter enables or disables the Adaptive Multi-Rate (AMR) Half Rate at the BSS. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes The AMR feature must be unrestricted. In the case of remote transcoding, at least one AXCDR must have CIC validation enabled. The handover_required_sp_ver_used parameter must be enabled. This parameter applies only to the BSC.

Syntax
Add/Change command strings
chg_element amr_bss_half_rate_enabled <value> 0

Display command strings

disp_element amr_bss_half_rate_enabled 0

Values
Value type Valid range Boolean 0 or 1 0 1 Default value 0 Disabled Enabled

6-30

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

amr_bss_full_rate_enabled

Description
The amr_bss_full_rate_enabled parameter enables or disables the Adaptive Multi-Rate (AMR) Full Rate at the BSS. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No The AMR feature must be unrestricted. In the case of remote transcoding, at least one AXCDR must have CIC validation enabled. The handover_required_sp_ver_used parameter must be enabled. This parameter applies only to the BSC.

Syntax
Add/Change command strings
chg_element amr_bss_full_rate_enabled <value> 0

Display command strings

disp_element amr_bss_full_rate_enabled 0

Values
Value type Valid range Boolean 0 or 1 0 1 Default value 0 Disabled Enabled

68P02901W23-S

6-31 Nov 2009

amr_dl_la_mode_chg_min

Chapter 6: CM database parameters

amr_dl_la_mode_chg_min

Description
The amr_dl_la_mode_chg_min parameter specifies the minimum network allowed time period between consecutive changes in the downlink codec mode. The downlink adaptation process possesses an inherent round-trip delay whose typical value (negligible E1 transmission delay is assumed) is 10 to 12 speech frame periods (20 ms each). This delay begins with the MS issuance of a new CMR to the network and terminates with the MS reception of the matching CMI. Setting this parameter to any value less than the inherent delay results in the same system behavior, namely an adaptation period equal to the inherent delay. When the parameter is set to a value greater than the inherent delay, a wait period is added to slow down the adaptation process, that is, the time between consecutive codec changes to the period specified by the parameter. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes 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 Valid range Default value Integer (number of 20 ms periods) 0 to 63 5

6-32

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

amr_dl_thresh_adjust

Description
The amr_dl_thresh_adjust parameter specifies the compensation for the Carrier to Interference (C/I) adaptation thresholds. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes The AMR feature must be unrestricted.

Syntax
Add/Change command strings
chg_element amr_dl_thresh_adjust <value> <location>

Display command strings

disp_element amr_dl_thresh_adjust <location>

Values
Value type Valid range Default value dB 1 to 7 3

68P02901W23-S

6-33 Nov 2009

amr_fr_dl_la_enabled

Chapter 6: CM database parameters

amr_fr_dl_la_enabled

Description
The amr_fr_dl_la_enabled parameter enables or disables Full Rate Downlink Codec Mode Adaptation on a per cell basis. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes The AMR feature must be unrestricted.

Syntax
Add/Change command strings
chg_element amr_fr_dl_la_enabled <value> <location> <cell_desc> chg_cell_element amr_fr_dl_la_enabled <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> full disp_element amr_fr_dl_la_enabled <location> <cell_desc>

Values
Value type Valid range Boolean 0 or 1 0 1 Default value 1 Disabled Enabled

6-34

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

amr_fr_ul_la_enabled

Description
The amr_fr_ul_la_enabled parameter enables or disables Full Rate Uplink Codec Mode Adaptation on a per cell basis. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes The AMR feature must be unrestricted.

Syntax
Add/Change command strings
chg_element amr_fr_ul_la_enabled <value> <location> <cell_desc> chg_cell_element amr_fr_ul_la_enabled <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> full disp_element amr_fr_ul_la_enabled <location> <cell_desc>

Values
Value type Valid range Boolean 0 or 1 0 1 Default value 1 Disabled Enabled

68P02901W23-S

6-35 Nov 2009

amr_full_rate_enabled

Chapter 6: CM database parameters

amr_full_rate_enabled

Description
The amr_full_rate_enabled parameter enables or disables the AMR Full Rate at a cell. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes The AMR feature must be unrestricted. This parameter does not apply to a remote transcoder (RXCDR). This parameter does not apply to a standalone BSC site (that is, a site without a collocated BTS).

Syntax
Change command strings
chg_element amr_full_rate_enabled <value> <location> <cell_desc> chg_cell_element amr_full_rate_enabled <value> <cell_desc_opt>

NOTE
The chg_cell_element command cannot be used to change this parameter unless the site is an AMR-capable BTS.

Display command strings

disp_cell <cell_id> [full] disp_element amr_full_rate_enabled <location> <cell_desc>

NOTE
The copy_cell command sets this parameter to disabled.

6-36

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Values

Values
Value type Valid range Boolean 0 or 1 0 1 Default value 0 Disabled Enabled

68P02901W23-S

6-37 Nov 2009

amr_half_rate_enabled

Chapter 6: CM database parameters

amr_half_rate_enabled

Description
The amr_half_rate_enabled parameter enables or disables the AMR Half Rate at a cell. The amr_half_rate_enabled cell element parameter can be modified using the chg_element or chg_cell_element command, and displayed with the disp_cell full command.

NOTE
The amr_half_rate_enabled RTF element parameter has been renamed half_rate_enabled (see half_rate_enabled on page 6-368).

Type Supported by OMC-R GUI Cell description required Dependencies

A (no operator actions) Yes Yes The AMR feature must be unrestricted. The amr_half_rate_enabled cell parameter can only be modified or set at a BTS site comprised solely of M-Cell2/6 or Horizonmacro cabinets or a mixture of both. The amr_half_rate_enabled cell parameter can be modified or set at an M-Cell2/6 site only if the TCU-A/TCU-B optional features are unrestricted.

Syntax
Add/Change command strings
chg_element amr_half_rate_enabled <value> <location> <cell_desc> chg_cell_element amr_half_rate_enabled <value> <cell_desc_opt>

Display command strings

disp_element amr_half_rate_enabled <location> <cell_desc> disp_cell <cell_id> full

NOTE
The copy_cell command sets the cell element parameter to disabled.

6-38

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Values

Values
Value type Valid range Boolean 0 or 1 0 1 Default value 0 Disabled Enabled

68P02901W23-S

6-39 Nov 2009

amr_hr_dl_la_enabled

Chapter 6: CM database parameters

amr_hr_dl_la_enabled

Description
The amr_hr_dl_la_enabled parameter enables or disables Half Rate Downlink Codec Mode Adaptation on a per cell basis. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes The AMR feature must be unrestricted.

Syntax
Add/Change command strings
chg_element amr_hr_dl_la_enabled <value> <location> <cell_desc> chg_cell_element amr_hr_dl_la_enabled <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> full disp_element amr_hr_dl_la_enabled <location> <cell_desc>

Values
Value type Valid range Boolean 0 or 1 0 1 Default value 1 Disabled Enabled

6-40

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

amr_hr_ul_la_enabled

Description
The amr_hr_ul_la_enabled parameter enables or disables Half Rate Uplink Codec Mode Adaptation on a per cell basis. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes The AMR feature must be unrestricted.

Syntax
Add/Change command strings
chg_element amr_hr_ul_la_enabled <value> <location> <cell_desc> chg_cell_element amr_hr_ul_la_enabled <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> full disp_element amr_hr_ul_la_enabled <location> <cell_desc>

Values
Value type Valid range Boolean 0 or 1 0 1 Default value 1 Disabled Enabled

68P02901W23-S

6-41 Nov 2009

amr_ms_high_cmr

Chapter 6: CM database parameters

amr_ms_high_cmr

Description
The amr_ms_high_cmr parameter specifies the percentages for monitoring AMR MSs continually requesting the highest codec mode at a BSS. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No The AMR feature must be unrestricted.

Syntax
Add/Change command string
chg_element amr_ms_high_cmr <value> <location>

Display command string

disp_element amr_ms_high_cmr <location>

Values
Value type Valid range Default value Percentages 50 to 100 95

6-42

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

amr_ms_high_rxqual

Description
The amr_ms_high_rxqual parameter specifies the threshold for monitoring AMR MSs continually requesting the highest codec mode at a BSS. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No The AMR feature must be unrestricted.

Syntax
Add/Change command strings
chg_element amr_ms_high_rxqual <value> <location>

Display command strings

disp_element amr_ms_high_rxqual <location>

Values
Value type Valid range Default value QBand units 0 to 7 4 (2.5% BER or RXQUAL 4)

68P02901W23-S

6-43 Nov 2009

amr_ms_low_cmr

Chapter 6: CM database parameters

amr_ms_low_cmr

Description
The amr_ms_high_cmr parameter specifies the percentages for monitoring AMR MSs continually requesting the lowest codec mode at a BSS. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No 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 Valid range Default value Percentages 50 to 100 99

6-44

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

amr_ms_low_rxqual

Description
The amr_ms_high_rxqual parameter specifies the threshold for monitoring MSs continually requesting the lowest mode at a BSS. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No The AMR feature must be unrestricted.

Syntax
Add/Change command strings
chg_element amr_ms_low_rxqual <value> <location>

Display command strings

disp_element amr_ms_low_rxqual <location>

Values
Value type Valid range Default value QBand units 0 to 7 2 0.5% BER or RXQUAL 2

68P02901W23-S

6-45 Nov 2009

amr_ms_monitor_period

Chapter 6: CM database parameters

amr_ms_monitor_period

Description
The amr_ms_monitor_period parameter is used for detecting MSs continually requesting the highest or lowest modes at a BSS. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No 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 Valid range Integer (SACCH periods) 10 to 120 0 Default value 40 SACCH periods Disable parameter

6-46

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

arp_bg_1

{27703A}

Description
The arp_bg_1 parameter specifies the Allocation and Retention Priority (ARP) value of background traffic class, precedence class 1. The system will interpret the decimal value into decimal value of 4 parts, according to ARP IE structure: qa priority level/ arp value pci pvi

This ARP information is used during the admission control and retention of PFC when they can not be derived from SGSN. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No The arp_bg_1 parameter can only be modified if the Quality of Service feature (qosOpt)is unrestricted. The priority level value of arp_bg_1 is less than or equal to those of arp_bg_2 and arp_bg_3. The arp_bg_1 parameter may be accessed/ updated both in and out of sysgen mode.

Syntax
Change command strings
chg_element arp_bg_1 <value> <location>

Display command strings

disp_element arp_bg_1 <location>

68P02901W23-S

6-47 Nov 2009

Values

Chapter 6: CM database parameters

Values
Value type Valid range Integer 4 to 59 68 to 123 Default value 49 (pci=0, priority level=12, pvi=0)

The value of this attribute is converted to binary and the bits are interpreted as follows to obtain, the pci, pvi and the priority level/arp value. 8 spare 7 pci 6 5 4 3 2 qa 1 pvi

priority level

NOTE
The value of qa bit is not used in GSR9.

6-48

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

arp_bg_2

{27703A}

Description
The arp_bg_2 parameter specifies the Allocation and Retention Priority (ARP) value of background class, precedence class 2. This ARP information is used during the admission control and retention of PFC when they can not be derived from SGSN. qa priority level/ arp value pci pvi

This ARP information is used during the admission control and retention of PFC when they cannot be derived from SGSN. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No The arp_bg_2 parameter can only be modified if the Quality of Service feature (qosOpt) is restricted. The priority level value of arp_bg_2 is less than or equal to that of arp_bg_3 and greater than or equal to that of arp_bg_1. The arp_bg_2 parameter may be accessed/ updated both in and out of sysgen mode.

Syntax
Change command strings

chg_element arp_bg_2 <value> <location>

Display command strings

disp_element arp_bg_2 <location>

68P02901W23-S

6-49 Nov 2009

Values

Chapter 6: CM database parameters

Values
Value type Valid range Integer 4 to 59 68 to 123 Default value 53 (pci=0, priority level=13, pvi=1)

The value of this attribute is converted to binary and the bits are interpreted as follows to obtain, the pci, pvi and the priority level/arp value. 8 spare 7 pci 6 5 4 3 2 qa 1 pvi

priority level

NOTE
The value of qa bit is not used in GSR9.

6-50

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

arp_bg_3

{27703A}

Description
The arp_bg_3 parameter specifies the Allocation and Retention Priority (ARP) value of background class, precedence class 3. The system will interpret the decimal value of 4 parts, according to ARP IE structure. qa priority level/ arp level pci pvi

This ARP information is used during the admission control and retention of PFC when they cannot be derived from SGSN. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No The arp_bg_3parameter can only be modified if the Quality of Service (qosOpt) feature is unrestricted. The priority level value of arp_bg_3 is greater than or equal to those of arp_bg_1 and arp_bg_2. The arp_bg_3 parameter may be accessed/ updated both in and out of sysgen mode.

Syntax
Change command strings
chg_element arp_bg_3 <value> <location>

Display command strings

disp_element arp_bg_3 <location>

68P02901W23-S

6-51 Nov 2009

Values

Chapter 6: CM database parameters

Values
Value type Valid range Integer 4 to 59 68 to 123 Default value 57 (pci=0, priority level=14, pvi=1)

The value of this attribute is converted to binary and the bits are interpreted as follows to obtain, the pci, pvi and the priority level/arp value. 8 7 6 5 4 3 2 qa 1 pvi

spare pci

priority level

NOTE
The value of qa bit is not used in GSR9.

6-52

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

arp_i_be_1

{27703A}

Description
The arp_i_be_1 parameter specifies the Allocation and Retention Priority (ARP) value of Interactive or Best Effort traffic class, precedence class 1. The system will interpret the decimal value into decimal value of 4 parts, according to ARP IE structure: qa priority level/arp value pci pvi

This ARP information is used during the admission control and retention of PFC when they can not be derived from SGSN. Type Supported by OMC-R GUI Cell numbers required Dependencies A (no operator actions) Yes No The arp_i_be_1 parameter can only be modified if the Quality of Service feature (qosOpt) is not restricted. The priority level value of arp_i_be_1 is less than or equal to those of arp_i_be_2 and arp_i_be_3. The arp_i_be_1 parameter may be accessed/ updated both in and out of sysgen mode.

Syntax
Change command strings
chg_element arp_i_be_1 BSC

Display command strings

disp_element arp_i_be_1 <location>

68P02901W23-S

6-53 Nov 2009

Values

Chapter 6: CM database parameters

Values
Value type Valid range Integer 4 to 59 68 to 123 Default value 93 (pci=1, priority level=7, pvi=1)

The value of this attribute is converted to binary and the bits are interpreted as follows to obtain, the pci, pvi and the priority level/arp value. 8 spare 7 pci 6 5 4 3 2 qa 1 pvi

priority level

NOTE
The value of qa bit is not used in GSR9.

6-54

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

arp_i_be_2

{27703A}

Description
The arp_i_be_2 parameter specifies the Allocation and Retention Priority (ARP) value of Interactive or Best Effort traffic class, precedence class 2. The system will interpret the decimal value into decimal value of 4 parts, according to ARP IE structure: qa priority level/ arp value pci pvi

This ARP information is used during the admission control and retention of PFC when they can not be derived from SGSN. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No The arp_i_be_2 parameter can only be modified if the Quality of Service feature (qosOpt) is unrestricted. The priority level value of arp_i_be_2 is less than or equal to that of arp_i_be_3 and greater than or equal to that of arp_i_be_1. The arp_i_be_2 parameter may be accessed/ updated both in and out of sysgen mode.

Syntax
Change command strings
chg_element arp_i_be_2 BSC

Display command strings

disp_element arp_i_be_2 <location>

68P02901W23-S

6-55 Nov 2009

Values

Chapter 6: CM database parameters

Values
Value type Valid range Integer 4 to 59 68 to 123 Default value 97 (pci=1, priority level=8, pvi=1)

The value of this attribute is converted to binary and the bits are interpreted as follows to obtain, the pci, pvi and the priority level/arp value. 8 7 6 5 4 3 2 qa 1 pvi

spare pci

priority level

NOTE
The value of qa bit is not used in GSR9.

6-56

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

arp_i_be_3

{27703A}

Description
The arp_i_be_3 parameter specifies the Allocation and Retention Priority (ARP) value of Interactive or Best Effort traffic class, precedence class 3. The system will interpret the decimal value into decimal value of 4 parts, according to ARP IE structure: qa priority level/ arp value pci pvi

This ARP information is used during the admission control and retention of PFC when they can not be derived from SGSN. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No The arp_i_be_3 parameter can only be modified if the Quality of Service feature (qosOpt) is unrestricted. The priority level value of arp_i_be_3 is greater than or equal to those of arp_i_be_1 and arp_i_be_2. The arp_i_be_3 parameter may be accessed/ updated both in and out of sysgen mode.

Syntax
Change command strings
chg_element arp_i_be_3 BSC

Display command strings

disp_element arp_i_be_3 <location>

68P02901W23-S

6-57 Nov 2009

Values

Chapter 6: CM database parameters

Values
Value type Valid range Integer 4 to 59 68 to 123 Default value 101 (pci=1, priority level=9, pvi=1)

The value of this attribute is converted to binary and the bits are interpreted as follows to obtain, the pci, pvi and the priority level/arp value. 8 spare 7 pci 6 5 4 3 2 qa 1 pvi

priority level

NOTE
The value of qa bit is not used in GSR9.

6-58

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

arp_streaming_1

{27703A}

Description
The arp_streaming_1 parameter specifies the Allocation and Retention Priority (ARP) value of streaming traffic class, precedence class 1. The system will interpret the decimal value into decimal value of 4 parts, according to ARP IE structure: qa priority level/ arp value pci pvi

This ARP information is used during the admission control and retention of PFC when they can not be derived from SGSN. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No The arp_streaming_1 parameter can be modified only if the QoS Phase 2 feature (qosOpt) is unrestrictedThe arp_streaming_1 feature requires the QoS Phase 2 feature to be enabled. The priority level value of arp_streaming_1 is less than or equal to those of arp_streaming_2 and arp_streaming_3. The arp_streaming_1 parameter may be accessed/ updated both in and out of sysgen mode.

Syntax
Change command strings
chg_element arp_streaming_1 <value> <location>

Display command strings

disp_element arp_streaming_1 <location>

68P02901W23-S

6-59 Nov 2009

Values

Chapter 6: CM database parameters

Values
Value type Valid range Integer 4 to 59 68 to 123 Default value 68 (pci=1, priority level=1, pvi=0)

NOTE
The value of this attribute is converted to binary and the bits are interpreted as follows to obtain, the pci, pvi and the priority level/arp value.

8 spare

7 pci

2 qa

1 pvi

priority level

NOTE
The value of qa bit is not used in GSR9.

6-60

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

arp_streaming_2

{27703A}

Description
The arp_streaming_2 parameter specifies the Allocation and Retention Priority (ARP) value of streaming traffic class, precedence class 2. The system will interpret the decimal value into decimal value of 4 parts, according to ARP IE structure: qa priority level/ arp value pci pvi

This ARP information is used during the admission control and retention of PFC when they can not be derived from SGSN. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No The arp_streaming_2 parameter can be modified only if the QoS Phase 2 feature (qosOpt) is not restricted. The priority level value of arp_streaming_2 is less than or equal to that of arp_streaming_3 and greater than or equal to that of arp_streaming_1. The arp_streaming_2 parameter may be accessed/ updated both in and out of sysgen mode.

Syntax
Change command strings
chg_element arp_streaming_2 <value> <location>

Display command strings

disp_element arp_streaming_2 <location>

68P02901W23-S

6-61 Nov 2009

Values

Chapter 6: CM database parameters

Values
Value type Valid range Integer 4 to 59 68 to 123 Default value 73 (pci=1, priority level=2, pvi=1)

The value of this attribute is converted to binary and the bits are interpreted as follows to obtain, the pci, pvi and the priority level/arp value. 8 spare 7 pci 6 5 4 3 2 qa 1 pvi

priority level

NOTE
The value of qa bit is not used in GSR9.

6-62

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

arp_streaming_3

{27703A}

Description
The arp_streaming_3 parameter specifies the Allocation and Retention Priority (ARP) value of streaming traffic class, precedence class 3. The system will interpret the decimal value into decimal value of 4 parts, according to ARP IE structure: qa priority level/ arp value pci pvi

This ARP information is used during the admission control and retention of PFC when they cannot be derived from SGSN. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No The arp_streaming_3 parameter can be modified only if the QoS Phase 2 feature (qosOpt) is unrestricted. The priority level value of arp_streaming_3 is greater than or equal to those of arp_streaming_1 and arp_streaming_2. The arp_streaming_3 parameter may be accessed/updated both in and out of sysgen mode.

Syntax
Change command strings
chg_element arp_streaming_3 <value> <location>

Display command strings

disp_element arp_streaming_3 <location>

68P02901W23-S

6-63 Nov 2009

Values

Chapter 6: CM database parameters

Values
Value type Valid range Integer 4 to 59 68 to 123 Default value 77 (pci=1, priority level=3, pvi=1)

The value of this attribute is converted to binary and the bits are interpreted as follows to obtain, the pci, pvi and the priority level/arp value. 8 7 6 5 4 3 2 qa 1 pvi

spare pci

priority level

NOTE
The value of qa bit is not used in GSR9.

6-64

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

asym_edge_enabled

{30830}

Description
The asym_edge_enabled element enables or disables support of asymmetric EGPRS for CTU2-D on per SITE basis. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes The asym_edge_enabled parameter is modified only if CTU2-D asymmetric feature is unrestricted. It is enabled at sites where the master SITE cabinet is a member of the HII family (HII macro, HII mini and HII micro).

Syntax
Change command strings
chg_element asym_edge_enabled <value> <location>

Display command strings

disp_element asym_edge_enabled <location>

Values
Value type Valid range Boolean 0 or 1 0 1 Default value 0 Disabled Enabled

68P02901W23-S

6-65 Nov 2009

attach_detach

Chapter 6: CM database parameters

attach_detach

Description
The attach_detach parameter enables and disables the mandatory International Mobile Subscriber Identity (IMSI) attach/detach for the MS. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes None

Syntax
Add/Change command strings
add_cell <gsm_cell_id> <location> chg_element attach_detach <value> <location> <cell_desc> chg_cell_element attach_detach <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full] disp_element attach_detach <location> <cell_desc>

Values
Value type Valid range Boolean 0 or 1 0 1 Default value 0 Disabled Enabled

6-66

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

References

References
GSM parameter GSM technical specification ATT 4.08 4.08 4.08 4.08 12.20 4.4.3 - attach 4.3.4 - detach 10.5.2.8 9.1.31 - 5.2.8.8 config CCH - allow IMSI Attach Detach

68P02901W23-S

6-67 Nov 2009

auto_rf_loss_trace

Chapter 6: CM database parameters

auto_rf_loss_trace

Description
The auto_rf_loss_trace parameter enables and disables automatic RF Loss tracing for a cell. The destination for RF loss measurement reports is also specified when RF loss tracing is enabled. If the auto_rf_loss_trace parameter is enabled for a cell with the destination set for the MMI and an RF loss occurs in the cell, a measurement report is sent to the MMI and is displayed in the same format as the output for the trace_call command. An RLM cause for the RF loss is included in the additional trace status field when the RF loss trace generates the measurement report. **** START OF RF LOSS REPORT **** * Sequence Number * SCCP Number * Scope * Carrier * Channel * Trace Status * Time Stamp * Call Duration * Mobile ID * CIC * Call Lost * RSS Data: Time: 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.745

00:00:48.690 TMSI=00050603 0002h Yes 01/03/1980 08:04:33.745

* 1b 37 19 03 00 00 1b 04 14 0a 10 04 * Measurement result info: * Neighbor: 01 1e 10 00 c9 00 00 01 00 00 00 00 07 07

* Timing Advance Info:

END OF RF LOSS REPORT

6-68

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Syntax

Type Supported by OMC-R GUI Cell description required Dependencies

A (no operator action) Yes Yes The auto_rf_loss_trace parameter is valid for any GPROC except the CSFP .

Syntax
Change command strings
chg_element auto_rf_loss_trace <value> <location> <cell_desc> chg_cell_element auto_rf_loss_trace <value> <cell_desc_opt>

Display command string

disp_element auto_rf_loss_trace <location> <cell_desc>

Values
Value type Valid range Integer 0 to 2 0 1 2 Default value 0 Automatic RF loss tracing disabled for this cell. Automatic RF loss tracing enabled for this cell; send measurement reports to MMI and OMC-R. Automatic RF loss tracing enabled for this cell; send measurement reports to OMC-R only.

References
GSM parameter GSM technical specification None This is a Motorola parameter. RLM cause values are defined in TS GSM 08.58, section 9.3.22

68P02901W23-S

6-69 Nov 2009

ba_alloc_proc

Chapter 6: CM database parameters

ba_alloc_proc

Description
The ba_alloc_proc parameter enables and disables the reinitialization of the active block following a change in the broadcast control channel allocation (BA) and the suspension of subsequent measurements until the new BA is reported. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes None

Syntax
Add/Change command strings
add_cell <gsm_cell_id> <location> chg_element ba_alloc_proc <value> <location> <cell_desc> chg_cell_element ba_alloc_proc <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full] disp_element ba_alloc_proc <location> <cell_desc>

Values
Value type Valid range Boolean 0 or 1 0 1 Default value 0 Reinitialization disabled Reinitialization enabled

6-70

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

References

References
GSM parameter GSM technical specification None This is a Motorola parameter.

68P02901W23-S

6-71 Nov 2009

band_preference

Chapter 6: CM database parameters

band_preference

Description
The band_preference parameter displays the frequency band that the cell prefers to use for handovers and specifies the destination frequency band for inter-cell handovers. Setting the value of band_preference to 16 (Dynamic) enables Intelligent Multi-layer Resource Management (IMRM) within the cell only if the IMRM feature is unrestricted. When setting this parameter to 16 the BSS prompts for the band weightings for PGSM, EGSM, DCS 1800, and, if the 2G/3G feature is unrestricted, UMTS. Setting all supported IMRM band weights to 0 raises a Warning indicating that the BSS shall apply internal defaults in the IMRM band selection algorithm. The change command is rejected if more than one IMRM weight is set to the maximum value of 100. Type Supported by OMC-R GUI Cell description required Dependencies A (No operator action) Yes Yes The Multiband Inter-cell handover feature must be enabled. This parameter has no meaning if band_preference_mode = 0 for this cell. If BPM=1, then the BSS attempts to assign a Multiband MS to the strongest preferred band neighbor that the MS reported at the time of SDCCH to TCH assignment. The IMRM feature must be unrestricted to support the setting of this parameter to 16 (Dynamic). The 2G/3G feature must be unrestricted to set the IMRM weighing for UMTS.

Syntax
Change command strings
chg_cell_element band_preference <value> <cell_desc_opt>

Display command string

disp_element band_preference <location> <cell_desc>

6-72

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Values

Values
Value type Valid range 1 to 16 1 2 4 8 16 Default value (PGSM) (EGSM) (DCS1800) (PCS1900) (DYNAMIC) Select integer

The frequency type of the cell (as set by frequency_type).

References
GSM parameter GSM technical specification None This is a Motorola parameter.

68P02901W23-S

6-73 Nov 2009

band_preference_mode

Chapter 6: CM database parameters

band_preference_mode

Description
The band_preference_mode parameter specifies the method the system uses to program a Multiband MS with the preferred frequency band for a given cell in the BSS. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes The Multiband Inter-cell handover feature must be unrestricted.

Syntax
Change command strings
chg_element band_preference_mode <value> <location> <cell_desc> chg_cell_element band_preference_mode <value> <cell_desc_opt>

Display command string

disp_element band_preference_mode <location> <cell_desc>

Values
Value type Valid range Integer 0 to 6 0 The BSS attempts to hand a Multiband MS over to the strongest neighbor that the MS reported when a handover is required for normal radio resource reasons.

6-74

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Values

The BSS attempts to assign a multiband MS to the preferred band within the cell at the time of SDCCH to TCH assignment. If the preferred band is the secondary band and no secondary resource is available within the cell or the MS does not meet the inner zone criteria, the BSS attempts to assign the MS to the strongest MS reported neighbor with a BCCH in the preferred band or non-preferred neighbor with a resource in the preferred band. If that is not possible, a resource is assigned from the serving cells non-preferred band. If the preferred band is the primary band and no primary resource is available within the cell, the call cannot be assigned. The BSS attempts to hand over a multiband MS to the strongest MS reported neighbor with a BCCH in the preferred band or non-preferred neighbor with resource in the preferred band when a handover is required for normal radio resource reasons. The BSS places preferred band neighbors ahead of non-preferred band neighbors in order to attempt to assign a channel from the preferred band for the MS. At the time of SDCCH to TCH assignment, if the preferred band is the secondary band and the MS provides sufficient Measurement Reports, a resource is provided from the cell inner zone. If the preferred band is not the secondary band or the MS fails to provide enough Measurement Reports, the resource is assigned from the cell outer zone. This value combines the functions of values 1 and 2. The BSS attempts to assign a multiband MS to the preferred band within the cell at the time of SDCCH to TCH assignment. If the preferred band is the secondary band and no secondary resource is available within the cell or the MS does not meet the inner zone criteria, the BSS attempts to assign the MS to the strongest MS reported neighbor with a BCCH in the preferred band or non-preferred neighbor with a resource in the preferred band. If that is not possible, a resource is assigned from the serving cells non-preferred band. The BSS attempts to hand over a multiband MS to the strongest MS reported neighbor with a BCCH in the preferred band or non-preferred neighbor with resource in the preferred band when a handover is required for normal radio resource reasons. The BSS continually attempts to hand a Multiband MS over to a preferred band TCH immediately after initial assignment. The BSS does not attempt to allocate a TCH in the preferred band for this MS at the time of SDCCH-to-TCH assignment. The BSS enters a mode of continually monitoring for qualified preferred-band neighbors reported by the MS in order to hand the MS over. The BSS stays in this mode until it finds a neighbor TCH in the preferred band for the current serving cell. Handovers for normal radio resource reasons may occur during the monitoring mode, and these handovers will be to the strongest preferred band neighbor reported by the MS.

68P02901W23-S

6-75 Nov 2009

References

Chapter 6: CM database parameters

The BSS attempts to assign a Multiband MS to the strongest preferred-band neighbor reported by the MS at the time of SDCCH-to-TCH assignment. If this assignment is not possible, the BSS enters a mode of continually monitoring for qualified preferred-band neighbors reported by the MS in order to hand over the MS. The BSS stays in this mode until it finds a neighbor TCH in the preferred band. Handovers for normal radio resource reasons may occur during the monitoring mode, and these handovers will be to the strongest preferred band neighbor reported by the MS. This value combines the functions of values 1, 2, and 4. The BSS attempts to assign a Multiband MS to the strongest preferred band neighbor reported by the MS only after a cell has become congested. If this assignment is not possible, the BSS enters a mode of continually monitoring for qualified preferred-band neighbors reported by the MS in order to hand over the MS. The BSS stays in this mode until it finds a neighbor TCH in the preferred band. Handovers for normal radio resource reasons may occur during the monitoring mode, and these handovers will be to the strongest preferred band neighbor reported by the MS. This type should be used in order to activate the multiband congestion threshold verification. This value functions identically to value 5, except it is triggered only when the cell is congested.

Default value

NOTE
In IMRM cells, band_preference_mode setting of 6, designed to limit multiband activity based on utilization, is overridden and handled as for a band_preference_mode setting of 5.

References
GSM parameter GSM technical specification None This is a Motorola parameter.

6-76

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

base_ip_address

{28351}

Description
The base IP address is used for the PCU and PSI. For PCU, there must be 24 contiguous addresses available after the IP address. For PSI, there must be 17 contiguous addresses available after the IP address. The Base IP address is entered in dotted quad notation. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No None

Syntax
modify_value

Values
Value type Valid range Integer For PCU 1.0.0.1 (minimum) 223.255.255.231 (maximum) For PSI 1.0.0.1 (minimum) 223.255.255.237 (maximum) Default value For PCU 10.0.0.1 For PSI None

68P02901W23-S

6-77 Nov 2009

Values

Chapter 6: CM database parameters

NOTE
If the ePCU fails to boot up in the DD2 mode, there is a PCU base_ip_address mismatch between the BSC database and the new MPROC default IP address configured during the manufacture. Use the following EMON commands on the master MPROC to check and modify: cage_ip create: Creates a new config file. Every parameter value is set by default. cage_ip read: read base_ip, netmask and the router address. cage_ip write <item> <value>: set base ip netmask and the router address <item>: base_ip netmask router <value>: ip address value

The following examples show the usage of the commands: PCU:emon_1107 % cage_ip create Emon create BASE IP suc ! base_ip 0 .0 .0 .0 , subnet_mask 255 .255 .255 .0 ,router_addr 0 .0 .0 .0 PCU:emon_1107 % cage_ip read Emon Got BASE IP suc ! base_ip 0 .0 .0 .0 , subnet_mask 255 .255 .255 .0 ,router_addr 0 .0 .0 .0 PCU:emon_1107 % cage_ip write base_ip "10.1.1.71" Emon Set BASE IP suc ! base_ip 10 .1 .1 .71 PCU:emon_1107 % cage_ip write router "255.255.0.0" Emon Set router suc ! router 255.255.0.0 PCU:emon_1107 % cage_ip read Emon Got BASE IP suc ! base_ip 10 .1 .1 .71 , subnet_mask 255 .255 .255 .0 ,router_addr 255.255.0.0

6-78

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

ber_loss_daily

Description
The ber_loss_daily parameter specifies the daily Bit Error Rate (BER) alarm threshold. An alarm is generated if the BER exceeds this threshold in a given 24 hour period. This parameter represents the exponent of threshold BER. For example, 3 is the exponent value of 103, indicating 1 bit error in 1000 bits. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No None

Syntax
Change command string
chg_element ber_loss_daily <value> <location>

Display command string

disp_element ber_loss_daily <location>

Values
Value type Valid range Default value Integer 3 to 6 5

References
GSM parameter GSM technical specification None This is a Motorola parameter.

68P02901W23-S

6-79 Nov 2009

ber_loss_hourly

Chapter 6: CM database parameters

ber_loss_hourly

Description
The ber_loss_hourly parameter specifies the hourly Bit Error Rate (BER) alarm threshold. This parameter represents the exponent of threshold BER. For example, 3 is the exponent value of 103, indicating 1 bit error in 1000 bits. An alarm is generated if the BER exceeds this threshold in a given 60 minute period. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No None

Syntax
Change command string
chg_element ber_loss_hourly <value> <location>

Display command string

disp_element ber_loss_hourly <location>

Values
Value type Valid range Default value Integer 3 to 6 4

References
GSM parameter GSM technical specification None This is a Motorola parameter.

6-80

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

blind_search_preference

Description
The blind_search_preference parameter indicates preference for blind search in idle mode. Blind search allows the BSS to just broadcast the FDD-ARFCN by itself without any cells specified. This reduces the size of neighbor list broadcast to the MS. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes The Enhanced 2G/3G Handover feature must be unrestricted to modify this parameter.

Syntax
Change command string
chg_element blind_search_preference <value> <location> chg_cell_element blind_search_preference <value> <cell_desc_opt>

Display command string

disp_cell <cell_id> [full] disp_element blind_search_preference <location>

Values
Value type Valid range Boolean 0 to 1 0 1 Default value 0 No blind search in idle mode. Blind search in idle mode.

68P02901W23-S

6-81 Nov 2009

bounce_protect_margin

Chapter 6: CM database parameters

bounce_protect_margin

Description
The bounce_protect_margin parameter, in conjunction with the ho_margin_cell parameter, specifies the level by which a target cell must exceed the serving cell. This parameter prevents continuous handover bouncing between cells due to RXQUAL level and congestion reasons. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes After a RXQUAL handover, the system applies the bounce_protect_margin value for the number of SACCH periods set by the bounce_protect_qual_tmr timer. After a congestion handover, the system applies the bounce_protect_margin value for the number of SACCH periods set by the bounce_protect_cong_tmr timer.

Syntax
Change command strings
chg_element bounce_protect_margin <value> <location> <cell_desc> chg_cell_element bounce_protect_margin <value> <cell_desc_opt>

Display command string

disp_element bounce_protect_margin <location> <cell_desc>

Values
Value type Valid range Default value Integer (decibels) 0 to 127 0

6-82

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

bs_ag_blks_res

Description
The bs_ag_blks_res parameter specifies the number of blocks reserved for access grant per 51-multiframes. The number of blocks reserved starting with (and including) block 0 are broadcast in the BCCH. The number of blocks reserved for access grant messages reduces the number of paging blocks available. The ratio of MS-originated calls to MS-terminated calls determines the choice of value. PCH and AGCH share the same TDMA mapping when combined onto a basic physical channel. Channels are shared on a block by block basis. Type Supported by OMC-R GUI Cell description required Dependencies B (operator actions required) Yes Yes If no AGCH is reserved in a non-combined cell (bs_ag_blks_res = 0) and ccch_conf is other than 1), enabling of CBCH is not permitted (cbch_enabled = 1). Reset the site after changing the bs_ag_blks_res value.

Operator actions

Syntax
Add/Change command strings
chg_element bs_ag_blks_res <value> <location> <cell_desc> chg_cell_element bs_ag_blks_res <value> <cell_desc_opt>

NOTE
A site reset is required when the value of bs_ag_blks_res is changed. Resetting the site generates several alarms. However, the system blocks these alarms.

Display command strings

disp_element bs_ag_blks_res <location> <cell_desc>

68P02901W23-S

6-83 Nov 2009

Values

Chapter 6: CM database parameters

Values
Value type Valid range Integer The range of values depends on the value of the ccch_conf parameter: 0 to 2 0 to 7 Default value 0 blocks reserved for ccch_conf = 1 blocks reserved for ccch_conf = 0

References
GSM parameter GSM technical specification BS_AG_BLKS_RES 5.02 - 6.5, and section 7 table 5 4.08 - 10.5.2.8, figure 10.27, and table 10.21 4.08 - 3.3.2.1, 10.5.2.14: page mode information element 12.20 - 5.2.8.8 - config CCH - no of blocks for access grant message

6-84

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

bs_pa_mfrms

Description
The bs_pa_mfrms parameter specifies the number of multiframes between transmissions of paging messages to MSs of the same paging group. The number of paging blocks available (per CCCH) are those available (on a specific CCCH) multiplied by (bs_pa_mfrms). Type Supported by OMC-R GUI Cell description required Dependencies B (operator actions required) Yes Yes The value chosen for this field depends on the size of the location area and the ratio of mobile originated to mobile terminated calls. Reset the site after changing the bs_pa_mfrms.

Operator actions

Syntax
Add/Change command strings
add_cell <gsm_cell_id> <location> chg_element bs_pa_mfrms <value> <location> <cell_desc> chg_cell_element bs_pa_mfrms <value> <cell_desc_opt>

NOTE
A site reset is required when the value of bs_pa_mfrms is changed. Although resetting the site generates several alarms, the system blocks these alarms.

Display command strings

disp_cell <cell_id> [full] disp_element bs_pa_mfrms <location> <cell_desc>

68P02901W23-S

6-85 Nov 2009

Values

Chapter 6: CM database parameters

Values
Value type Valid range Integer 0 to 7 0 1 2 3 4 5 6 7 Default value 0 (multiframes) Represents the multiframes period for the transmission of PAGING REQUEST messages to the same paging group. 2 3 4 5 6 7 8 9 multiframes multiframes multiframes multiframes multiframes multiframes multiframes multiframes

References
GSM parameter GSM technical specification BS_PA_MFRMS 4.04 5.02 5.02 5.08 12.20 10.5.2.8, fig. 10.27, and table 10.21 6.5.1 7: table 5 6.5: downlink signaling failure - 5.2.8.8 - configCCH

6-86

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

bs_pag_blks_res

Description
The bs_pag_blks_res specifies the number of Packet Access Grant Channel (PAGCH) blocks per 52-frame multiframe on a per cell basis. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes The PBCCH/PCCCH optional feature must be unrestricted. The sum of the values set for this parameter and for bs_pbcch_blks must be between 1 and 11.

Syntax
Add/Change command strings
chg_element bs_pag_blks_res <value> <location> <cell_desc> chg_cell_element bs_pag_blks_res <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> full disp_element bs_pag_blks_res <location> <cell_desc>

Values
Value type Valid range Default value Integer 0 to 4 2 Number of PAGCH blocks per 52-frame multiframe.

NOTE
The sum of the values set for this parameter and for bs_pbcch_blks must be between 1 and 11.

68P02901W23-S

6-87 Nov 2009

bs_pbcch_blks

Chapter 6: CM database parameters

bs_pbcch_blks

Description
The bs_pbcch_blks specifies the number of Packet Broadcast Control Channel (PBCCH) blocks per 52-frame multiframe on a per cell basis. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes The PBCCH/PCCCH optional feature must be unrestricted. The sum of the values set for this parameter and for bs_pag_blks_res must be between 1 and 11. This parameter must not be set to 1 or 2 when psi1_repeat_period is 1.

Syntax
Add/Change command strings
chg_element bs_pbcch_blks <value> <location> <cell_desc> chg_cell_element bs_pbcch_blks <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> full disp_element bs_pbcch_blks <location> <cell_desc>

Values
Value type Valid range Default value Integer 1 to 4 2 Number of PBCCH blocks per 52-frame multiframe.

NOTE
The sum of the values set for this parameter and for bs_pag_blks_res must be between 1 and 11.

6-88

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

bs_pcc_chans

Description
The bs_pcc_chans specifies the number of Packet Common Control Channel (PCCCH) timeslots on a per cell basis. The value indicates the number of physical channels carrying PCCCHs including the physical channel carrying the PBCCH. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes The PBCCH/PCCCH optional feature must be unrestricted.

Syntax
Add/Change command strings
chg_element bs_pcc_chans <value> <location> <cell_desc> chg_cell_element bs_pcc_chans <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> full disp_element bs_pcc_chans <location> <cell_desc>

Values
Value type Valid range Default value Integer 1 1 Number of physical channels with PCCCHs.

68P02901W23-S

6-89 Nov 2009

bs_prach_blks

Chapter 6: CM database parameters

bs_prach_blks

Description
The bs_prach_blks specifies the number of Packet Random Access Channel (PRACH) blocks per 52-frame multiframe on a per cell basis. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes The PBCCH/PCCCH optional feature must be unrestricted.

Syntax
Add/Change command strings
chg_element bs_prach_blks <value> <location> <cell_desc> chg_cell_element bs_prach_blks <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> full disp_element bs_prach_blks <location> <cell_desc>

Values
Value type Valid range Default value Integer 1 to 11 4 Number of PRACH blocks per 52-frame multiframe.

6-90

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

bsc_type

Description
The bsc_type parameter specifies the BSC configuration type. Type Supported by OMC-R GUI Cell description required Dependencies B (operator actions required) Yes No The value of this parameter can only be changed while in the initial SYSGEN mode. This command is only available for the BSC. Place the system in the initial SYSGEN mode then delete the existing database using the clear_database command.

Operator actions

CAUTION
When the clear_database command is entered, the CM database is deleted. When this occurs, the system does not process calls; calls in progress may be lost.

Syntax
Change command string
chg_element bsc_type <value> 0

Display command string

disp_element bsc_type 0

68P02901W23-S

6-91 Nov 2009

Values

Chapter 6: CM database parameters

Values
Value type Valid range Integer 0 to 3 0 1 2 3 Default value None Non Abis, Type 0 Non Abis, Type 1 Non Abis, Type 2 Abis, Type 0

NOTE
Type 2 supports the upload of PCU GDBP data to OMC-R and implies that an OMF GPROC must be present.

References
GSM parameter GSM technical specification None This is a Motorola parameter.

6-92

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

bsic

Description
The bsic parameter specifies the Base Station Identity Code (BSIC). The BSIC is a local color code that allows an MS to distinguish between different neighboring base stations. The BSIC is encoded on the Synchronization Channel. The size of the BSIC is one octet made up of two values: Network Color Code (NCC). The NCC is three bits and is the same as the Public land mobile network (PLMN) Color Code. Base station Color Code (BCC). The BCC is also three bits.

The values for the NCC and BCC may range from 000 to 111. The structure of the BSIC octet is _ _ N C C B C C, where _ _ are unused. The BSIC is calculated using Table 6-3 and Table 6-4 in this description. A BSIC for a PLMN may have one of eight values. A BSIC may be reused, but it is important that neighbor cells do not share the same BSIC and the same BCCH RF carrier.

NOTE
The chg_element command can change the BSIC within an operational site. There is no requirement to unequip the RTF before making this change.

Subsystem/Process Type Supported by OMC-R GUI Cell description required Dependencies Operator actions

MULT B (operator actions required) Yes Yes None Respond to the warning prompt which are displayed after the chg_cell_element or chg_element command is used to modify this parameter. The warning prompt says:

WARNING: Changing this element will reset all DRIs associated with this cell Are you sure (y=yes, n=no)?

68P02901W23-S

6-93 Nov 2009

Syntax

Chapter 6: CM database parameters

Syntax
Add/Change command strings
add_cell <gsm_cell_id> <location> add_neighbor <src_gsm_cell_id> <neighbor_gsm_cell_id> <placement> [<list_type>] chg_element bsic <value> <location> <cell_desc> chg_cell_element bsic <value> <cell_desc_opt>

NOTE
Changing the bsic value may cause the system to take a carrier out of service. Calls on this carrier may be lost, depending on the availability of other carriers and timeslots not affected by the out-of-service carrier. If the carrier is baseband hopping the system removes it from the active hopping system until the next site reset. The system displays the following warning: WARNING: Changing this element will reset all DRIs associated with this cell. Are you sure (y=yes, n=no)? A Y answer resets all the DRIs.

Display command strings

disp_cell <cell_id> [full] disp_element bsic <location> <cell_desc> disp_neighbor <src_gsm_cell_id>

Values
Value type Valid range Default value Integer Hex = 00h to 3Fh Decimal = 0 to 63 None (See Table 6-3) (See Table 6-4)

Table 6-3 lists the hexadecimal values for the base station identity codes.

6-94

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

References

Table 6-3
NCC 0 1 2 3 4 5 6 7

Base Station Identity Code - Hexadecimal Values

BCC 0 0 8 10 18 20 28 30 38 1 1 9 11 19 21 29 31 39 2 2 A 12 1A 22 2A 32 3A 3 3 B 13 1B 23 2B 33 3B 4 4 C 14 1C 24 2C 34 3C 5 5 D 15 1D 25 2D 35 3D 6 6 E 16 1E 26 2E 36 3E 7 7 F 17 1F 27 2F 37 3F

Table 6-4 lists the decimal values for the base station identity codes.

Table 6-4
NCC 0 1 2 3 4 5 6 7

Base Station Identity Code - Decimal Values

BCC 0 0 8 16 24 32 40 48 56 1 1 9 17 25 33 41 49 57 2 2 10 18 26 34 42 50 58 3 3 11 19 27 35 43 51 59 4 4 12 20 28 36 44 52 60 5 5 13 21 29 37 45 53 61 6 6 14 22 30 38 46 54 62 7 7 15 23 31 39 47 55 63

References
GSM parameter GSM technical specification BSIC, BSIC_NC(n) 3.03 - 4.2.2 3.03 - Annex A 12.20 - 5.2.8.2 12.20 - 5.2.8.7

68P02901W23-S

6-95 Nov 2009

bsp_overload_protection

Chapter 6: CM database parameters

bsp_overload_protection

{23306}

Description
The BSS element bsp_overload_protection specifies whether the BSP CPU overload protection is enabled. This parameter may be changed inside and outside SYSGEN mode. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) No No None

Syntax
Change command string
chg_element bsp_overload_protection <value> <location>

Display command string

disp_element bsp_overload_protection <location>

Values
Value type Valid range Boolean 0 1 Default value 0 Disabled Enabled

6-96

bssgp_cbl_bit

Chapter 6: CM database parameters

bssgp_cbl_bit

Description
The bssgp_cbl_bit parameter specifies whether the CBL (Current Bucket Level) feature is available at the PCU or not, that is, whether the CBL bit is set or not. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No This parameter can be used only if the GPRS feature is unrestricted. This parameter can be set in or out of SYSGEN mode. Operator actions: None

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

Syntax
Change command string
chg_element bssgp_cbl_bit <value> <location>

Display command string

disp_element bssgp_cbl_bit <location>

6-100

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Values

Values
Value type Valid range Default value Boolean 0 or 1 0 CBL procedures not supported (CBL bit not set). CBL procedures supported (CBL bit set).

68P02901W23-S

6-101 Nov 2009

bssgp_dwnld_retry

Chapter 6: CM database parameters

bssgp_dwnld_retry

Description
The bssgp_dwnld_retry parameter indicates the maximum number of retries for PFC Download. Type Supported by OMC-R GUI Cell description required Dependencies Operator actions A (no operator actions) Yes No The QoS feature must be unrestricted. None

Syntax
Change command string
chg_element bssgp_dwnld_retry <value> <location>

Display command string

disp_element bssgp_dwnld_retry <location>

Values
Value type Valid range Default value Integer 1 to 3 3

6-102

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

bssgp_pfc_bit

Description
The bssgp_pfc_bit parameter specifies if Packet Flow Management (PFM) procedures are enabled. Type Supported by OMC-R GUI Cell description required Dependencies Operator actions A (no operator actions) Yes No The QoS feature must be unrestricted. The NACC feature must be enabled. None

NOTE
BSS software processes using this parameter are not notified when the change is made.

Syntax
Change command string
chg_element bssgp_pfc_bit <value> <location>

Display command string

disp_element bssgp_pfc_bit <location>

68P02901W23-S

6-103 Nov 2009

Values

Chapter 6: CM database parameters

Values
Value type Valid range Boolean 0 to 1 0 1 Default value 0 Disabled Enabled

6-104

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

bssgp_racap_retries

Description
The bssgp_racap_retries parameter specifies the number of retries generated by the BSS for RA-Capability-Update messages to the SGSN. Type Supported by OMC-R GUI Cell description required Dependencies Operator actions A (no operator actions) Yes No The GPRS feature must be unrestricted. None

NOTE
BSS software processes using this parameter are not notified when the change is made.

Syntax
Change command string
chg_element bssgp_racap_retries <value> <location>

Display command string

disp_element bssgp_racap_retries <location>

Values
Value type Valid range Default value Integer (retries) 1 to 3 3

68P02901W23-S

6-105 Nov 2009

bssgp_reset_retries

Chapter 6: CM database parameters

bssgp_reset_retries

Description
The bssgp_reset_retries parameter specifies the number of retries generated by the BSS for Reset messages to the SGSN. Type Supported by OMC-R GUI Cell description required Dependencies Operator actions A (no operator actions) Yes No The GPRS feature must be unrestricted. None

NOTE
BSS software processes using this parameter are not notified when the change is made.

Syntax
Change command string
chg_element bssgp_reset_retries <value> <location>

Display command string

disp_element bssgp_reset_retries <location>

Values
Value type Valid range Default value Integer (retries) 1 to 3 3

6-106

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

bssgp_unblock_retries

Description
The bssgp_unblock_retries parameter specifies the number of retries generated by the BSS for cell Unblock messages to the SGSN. Type Supported by OMC-R GUI Cell description required Dependencies Operator actions A (no operator actions) Yes No The GPRS feature must be unrestricted. None

NOTE
BSS software processes using this parameter are not notified when the change is made.

Syntax
Change command string
chg_element bssgp_unblock_retries <value> <location>

Display command string

disp_element bssgp_unblock_retries <location>

Values
Value type Valid range Default value Integer (retries) 1 to 3 3

68P02901W23-S

6-107 Nov 2009

bts_p_con_ack

Chapter 6: CM database parameters

bts_p_con_ack

Description
The bts_p_con_ack parameter specifies the maximum amount of time to wait for RF power change acknowledgments to the BSS. This allows a repeat of the BTS power control message if the BTS power has not been confirmed. This is effective only if the decision_alg_num equals 1. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes decision_alg_type = 1

Syntax
Add/Change command strings
add_cell <gsm_cell_id> <location> chg_element bts_p_con_ack <value> <location> <cell_desc> chg_cell_element bts_p_con_ack <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full] disp_element bts_p_con_ack <location> <cell_desc>

Values
Value type Valid range Integer (1 Step = 2 multiframes) 0 to 31 0 1 2 ... 31 Default value 0 SACCH multiframes 2 SACCH multiframes 4 SACCH multiframes ... 62 SACCH multiframes

1 (equals 2 SACCH multiframes)

6-108

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

References

References
GSM parameter GSM technical specification P_CON_ACK None

68P02901W23-S

6-109 Nov 2009

bts_p_con_interval

Chapter 6: CM database parameters

bts_p_con_interval

Description
The bts_p_con_interval parameter specifies the minimum amount of time in multiples of two SACCH multiframes between successive RF power change orders to the BSS. The time period is greater than or equal to (nx - px + 1) hreqave / 2 Where: x equals 1 (lower threshold of RXLEV), 2 (upper threshold of RXLEV), 3 (lower threshold of RXQUAL), or 4 (upper threshold of RXQUAL). n equals the values assigned for decision_1_ny where y is a value from 1 to 4. p equals the values assigned for decision_1_py where y is a value from 1 to 4. hreqave is the number of measurements from the MS that are used in calculating one average. A (no operator actions) Yes Yes This parameter does not work if the specified location is the BSC (location = 0). hreqave bts_p_con_ack decision_1_n1 through decision_1_n4 decision_1_p1 through decision_1_p4

Type Supported by OMC-R GUI Cell description required Dependencies

Syntax
Add/Change command strings
add_cell <gsm_cell_id> <location> chg_element bts_p_con_interval <value> <location> <cell_desc> chg_cell_element bts_p_con_interval <value> <cell_desc_opt>

6-110

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Values

Display command strings

disp_cell <cell_id> [full] disp_element bts_p_con_interval <location> <cell_desc>

Values
Value type Valid range Integer (1 Step = 2 multiframes) 0 to 31 0 1 2 ... 31 Default value 0 SACCH multiframes 2 SACCH multiframes 4 SACCH multiframes ... 62 SACCH multiframes

2 (equals 4 SACCH multiframes)

References
GSM parameter GSM technical specification P_CON_INTERVAL 5.08 - Appendix A - Table 1

68P02901W23-S

6-111 Nov 2009

bts_power_control_allowed

Chapter 6: CM database parameters

bts_power_control_allowed

Description
The bts_power_control_allowed parameter enables or disables the downlink RF power control for the BSS. When enabled, the BSS uses up to 15 power control levels. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes None

Syntax
Add/Change command strings
add_cell <gsm_cell_id> <location> chg_element bts_power_control_allowed <value> <location> <cell_desc> chg_cell_element bts_power_control_allowed <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full] disp_element bts_power_control_allowed <location> <cell_desc>

Values
Value type Valid range Boolean 0 or 1 0 1 Default value 0 BTS power control disabled. BTS power control enabled.

NOTE
The value 0 is the only valid value at M-Cellcity sites; both 0 and 1 values are permitted at Horizonmicro2 and Horizoncompact2 sites.

6-112

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

References

References
GSM parameter GSM technical specification EN_BS_PC 5.05 - 4.1.2

68P02901W23-S

6-113 Nov 2009

bts_txpwr_max_inner

Chapter 6: CM database parameters

bts_txpwr_max_inner

Description
The bts_txpwr_max_inner parameter specifies the maximum transmit power BTS inner zone for Dual Band cells. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes This parameter may be modified only when the Dual Band Cells feature is unrestricted (inner_zone_alg set to 3).

Syntax
Change command strings
chg_element bts_txpwr_max_inner <value> <location> <cell_desc> chg_cell_element bts_txpwr_max_inner <value> <cell_desc_opt>

Display command string

disp_element bts_txpwr_max_inner <location> <cell_desc>

Values
Value type Valid range Default value Integer -1 to 21 0 to 6 0 (1 step = 2 dBm) Same as those for max_tx_bts except based on secondary_freq_type, not frequency_type. for PGSM, EGSM, and DCS1800. for M-Cellmicro, M-Cellaccess, and M-Cellcompact sites

NOTE
Refer to Table 6-5, Table 6-6, Table 6-7, Table 6-8, and Table 6-9 for additional information about the values for this parameter. Table 6-5 lists the values for CTU2 (SD-SCM, DD-DCM). The values represent the calibrated output power at the top of the cabinet with one stage of combining. 6-114 68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Values

Table 6-5

CTU2 values
Valid Input -1 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 CTU2 values 44 dBm 42 dBm 40 dBm 38 dBm 36 dBm 34 dBm 32 dBm 30 dBm 28 dBm 26 dBm 24 dBm 22 dBm 20 dBm 18 dBm 16 dBm 14 dBm 12 dBm 10 dBm 8 dBm 6 dBm 4 dBm 2 dBm 0 dBm

NOTE
Value -1 is only valid for single density CTU2 DRI. Table 6-6 identifies the transmit power capabilities of the different XCVR types in specific frequency bands and cabinet types. The power specified is the cabinet antenna connector maximum output power. All figures are 2 dB.

68P02901W23-S

6-115 Nov 2009

Values

Chapter 6: CM database parameters

Table 6-6 also specifies the types of combing in used: none, external, internal, and both internal and external. The combining types are defined as follows: None: The output power of the XCVR is connected directly to the antenna. This is not applicable for a DDM as it always uses a single stage of internal combining within the XCVR itself. External (to the XCVR): The output of the XCVR is connected through a single stage of external hybrid combining to the antenna. For example, a two-carrier sector is required from two SDX or two CTU2-SD. Internal (to the XCVR): When a CTU2 is configured in Double Density mode the two outputs from the two XCVR devices on the CTU2 are combined before leaving the XCVR. Hence the power figure for internal combining represents two carriers at this transmit power for a CTU2 in DD-DCM. Ensure that the internal combining is still present when the CTU2 is used in DD-SCM. Internal and external: External hybrid combining is used on a CTU2 in DDM. For example, this allows two CTU2 in DD-DCM to be combined to create a four-carrier sector.

Table 6-6

Cabinet antenna connector maximum output power (Watts)

Horizonmacro Horizon II EGSM900 N/A N/A 63 28 20 9 DCS1800 N/A N/A 50 22 16 7

XCVR Type CTU

Combining None External

EGSM900 40 20 40 20 10 4.5

DCS1800 32 16 32 16 10 4.5

CTU2 SD-SCM CTU2 DD-DCM

None External Internal Internal and external

Table 6-7 lists the values for PGSM, EGSM, DCS1800 and PCS1900 M-Cellmicro, M-Cellcity, M-Cellarena and M-Cellarenamacro sites.

Table 6-7
Valid Input 0 1 2 3 4 5 6

Values for PGSM, EGSM, DCS1800 and PCS1900 M-Cellmicro sites

PGSM and EGSM M-Cellmicro values 31 dBm 29 dBm 27 dBm 25 dBm 23 dBm 21 dBm 19 dBm DCS1800 and PCS1900 M-Cellmicro values 30 dBm 28 dBm 26 dBm 24 dBm 22 dBm 20 dBm 18 dBm M-Cellarenamacrovalues 40 dBm 38 dBm 36 dBm 34 dBm 32 dBm 30 dBm 28 dBm

Table 6-8 lists the values for DCS1800 and M-Cellaccess sites.

6-116

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Values

Table 6-8
Valid Input 0 1 2 3 4 5 6

Values for DCS1800 and M-Cellaccess, sites

PGSM, EGSM and M-Cellaccess values 12 dBm 10 dBm 8 dBm 6 dBm 4 dBm 2 dBm 0 dBm DCS1800 M-Cellaccess values 17 dBm 15 dBm 13 dBm 11 dBm 9 dBm 7 dBm 5 dBm

The actual output power of a cabinet depends on the type of combining that is used. Table 6-9 lists sample output power, measured at the top of the cabinet, of some Motorola cabinets with different combinations of RCUs and combiners.

Table 6-9

Sample output power

Number of radios Output power (as calibrated)

Type of combining ExCell 4 hybrid cavity (1 cabinet) BTS4, BTS5, BTS6 hybrid cavity (1 cabinet) cavity (2 neighboring cabinets) M-Cell2 or M-Cell6 6 hybrid cavity (1 cabinet) duplexer

2 4

20 W [Symbol_approximate] 43.01 dBm 25 W [Symbol_approximate] 43.98 dBm

2 5 10

20 W [Symbol_approximate] 43.01 dBm 25 W [Symbol_approximate] 43.98 dBm 13 W [Symbol_approximate] 41.14 dBm

2 6 4

17.5 W [Symbol_approximate] 43.01 dBm 19 W [Symbol_approximate] 42.79 dBm 13.5 W [Symbol_approximate] 41.30 dBm

NOTE
The listed power is valid for 600 kHz minimum channel distance, and for 800 kHz minimum channel distance with cavity combining. The chg_element command does not allow a power level greater than 36 dBm for any carrier for the cell that has an ARFCN on a PCS block edge frequency.

68P02901W23-S

6-117 Nov 2009

bts_type

Chapter 6: CM database parameters

bts_type

Description
The bts_type parameter specifies the BTS configuration type. It is valid only for sites 1 to 10. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No This parameter may not be changed to 0 if DHPs exist at the site, or if max_dris is set to 0. This parameter must be set to 0 for M-Cell2, M-Cell6, M-Cellcity, Horizonmicro, Horizoncompact2, Horizonmacro, Horizon II macro, and Horizon II mini cabinets.

Syntax
Change command string
chg_element bts_type <value> <location>

Display command string

disp_element bts_type <location>

Values
Value type Valid range Boolean 0 or 1 0 1 Default value None BTP BTP and DHP

6-118

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

References

References
GSM parameter GSM technical specification None This is a Motorola parameter.

68P02901W23-S

6-119 Nov 2009

bvci

Chapter 6: CM database parameters

bvci

Description
The bvci parameter specifies a BSSGP Virtual Connection Identifier (BVCI). There must be one BVCI per cell and one signaling BVCI per BSS. BVCIs are automatically generated by the BSS on creation of a cell. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes This parameter can be used only if the GPRS feature is unrestricted. A BVCI cannot be modified if gprs_enabled is set for the cell. All BVCIs must be unique. Only one BVCI can be mapped to a single cell, and one BVCI must be allocated as the BSSGP signaling BVCI.

Restrictions

NOTE
BSS software processes using this parameter are not notified when the change is made. That is, this parameter can be modified without a reset to a particular device or function.

Syntax
Add/Change command strings
add_cell <gsm_cell_id> <location> chg_element bvci <value> <location> <cell_desc> chg_cell_element bvci <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full] disp_element bvci <location> <cell_desc>

6-120

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Values

Values
Value type Valid range Default value Integer 2 to 65535 None

68P02901W23-S

6-121 Nov 2009

call_trace_options

Chapter 6: CM database parameters

call_trace_options

Description
The call_trace_options parameter enables or disables MSC initiated traces. It also specifies the percentage of traces exclusively reserved for MSC initiated call traces. The percentage of traces reserved exclusively for MSC initiated traces affects the number of call trace instances that may be created. This percentage is specified using the call_trace_options element. For example, if 50% of the traces are reserved for initiation from the MSC, a maximum of eight instances may be created using the trace_call command. If the call_trace_options element is set to 0, no traces are exclusively reserved for MSC initiated traces. MSC initiated traces are still allowed. This permits a maximum of 16 instances to be created using the trace_call command. If the call_trace_options element is set to 255, the system ignores call trace requests from the MSC. This permits a maximum of 16 instances to be created using the trace_call command. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No None

Syntax
Change command string
chg_element call_trace_options <value> <location>

Display command string

disp_element call_trace_options <location>

6-122

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Values

Values
Value type Valid range Integer 0 to 100, and 255 0 to 100 255 Default value 0 The percentage of traces reserved for MSC initiated traces on a per LCF basis. MSC invoked call traces disabled.

68P02901W23-S

6-123 Nov 2009

called_pci

Chapter 6: CM database parameters

called_pci

Description
The called_pci parameter specifies whether point code is included in the called party address in the SCCP messages. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No This parameter is valid only at the BSC.

Syntax
Change command string
chg_element called_pci <value> 0

Display command string

disp_element called_pci 0

Values
Value type Valid range Boolean 0 or 1 0 1 Default value None Point code is not included. Point code is included.

References
GSM specification CCITT Q.713 This is a Motorola defined parameter.

6-124

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

calling_pci

Description
The calling_pci parameter enables or disables point code inclusion for the calling party address in the SCCP messages. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No 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 Valid range Boolean 0 or 1 0 1 Default value None Disabled Enabled

References
GSM specification CCITT Q.713 This is a Motorola defined parameter.

68P02901W23-S

6-125 Nov 2009

carrier_disable_time

Chapter 6: CM database parameters

carrier_disable_time

Description
The carrier_disable_time parameter specifies the time delay between putting individual carriers into battery conservation mode after a main power failure is reported. For example, when a main power failure is first reported the system waits for the period of time specified by the carrier_disable_time parameter before placing the first carrier into battery conservation mode. Then the system waits for the same period of time before placing the next carrier into battery conservation mode. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No None

Syntax
Change command string
chg_element carrier_disable_time <value> <location>

Display command string

disp_element carrier_disable_time <location>

Values
Value type Valid range Default value Integer (seconds) 120 to 65535 120

6-126

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

carriers_ins_pwr_fail

Description
The carriers_ins_pwr_fail parameter specifies the number of carriers left up in the maintenance power state when emergency battery power starts (that is, during a main power failure). When the value of 0 is selected, all of the carriers are taken out of service in turn on the expiry of the specified carriers_ins_pwr_fail parameter (see carrier_disable_time on page 6-126). Non BCCH carriers are taken out of service before the BCCH carrier.

NOTE
The BCCH carrier continues to transmit after the battery conservation feature has taken the carrier out of service. Although the BCCH carrier is disabled, it continues to transmit since it is the carrier resources that are disabled and not the physical carriers. This enables quick recovery of all carriers when the main power is restored. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No None

Syntax
Change command string
chg_element carriers_ins_pwr_fail <value> <location>

Display command string

disp_element carriers_ins_pwr_fail <location>

68P02901W23-S

6-127 Nov 2009

Values

Chapter 6: CM database parameters

Values
Value type Valid range Integer 0 to 30 0 Default value 30 All carriers are taken out of service.

6-128

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

cbc_fast_select

Description
The cbc_fast_select parameter enables and disables the fast connect function for the BSC. The fast connect function supports X.25 networks that do not support user data in connect and disconnect requests. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No This parameter is valid only for the BSC.

Syntax
Change command strings
chg_element cbc_fast_select <value> 0

NOTE
A site reset is required when the value of cbc_fast_select is changed. Resetting the site generates several alarms. However, the system blocks these alarms.

Display command strings

disp_element cbc_fast_select 0

Values
Value type Valid range Boolean 0 or 1 0 1 Default value 0 Disabled Enabled

68P02901W23-S

6-129 Nov 2009

References

Chapter 6: CM database parameters

References
GSM specification 03.4103.49 This is a Motorola defined parameter.

6-130

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

cbc_intface_vers

Description
The cbc_intface_vers parameter selects the interface for each BSC site. The available interfaces are either the standard interface or the interface with the repetition rate interpretation and CBCH loading fields. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No This parameter is only valid for the BSC.

Syntax
Change command strings
chg_element cbc_intface_vers <value> 0

Display command strings

disp_element cbc_intface_vers 0

Values
Value type Valid range Boolean 0 or 1 0 1 Default value 0 Standard interface Interface with the repetition rate interpretation and CBCH loading fields.

68P02901W23-S

6-131 Nov 2009

cbc_vbind_cntr

Chapter 6: CM database parameters

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 Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No This parameter is only valid for the BSC.

Syntax
Change command strings
chg_element cbc_vbind_cntr <value> 0

Display command strings

disp_element cbc_vbind_cntr 0

Values
Value type Valid range Default value Integer (number of VBINDs) 0 to 255 0

6-132

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

cbch_enabled

Description
The cbch_enabled parameter enables the Cell Broadcast Channel (CBCH) option in a cell. The CBCH is used with the Short Message Service (SMS) Cell Broadcast feature. An operator defined message or set of background messages may be transmitted on the CBCH when the cbch_enabled parameter is enabled. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes Enabling of CBCH is not permitted if no AGCH is reserved in a non-combined cell (bs_ag_blks_res = 0 and ccch_conf is other than 1).

Syntax
Change command strings
chg_element cbch_enabled <value> <location> <cell_desc> chg_cell_element cbch_enabled <value> <cell_desc_opt>

Display command string

disp_element cbch_enabled <location> <cell_desc>

Values
Value type Valid range Boolean 0 or 1 0 1 Default value None Disabled Enabled

68P02901W23-S

6-133 Nov 2009

cbs_outage_cntr

Chapter 6: CM database parameters

cbs_outage_cntr

Description
The cbs_outage_cntr parameter introduces a delay between an outage occurring and the CBS halting transmission of CBC originated messages. This parameter is effective on a per BTS site basis. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No This parameter is only valid for a BTS site.

Syntax
Change command string
chg_element cbs_outage_cntr <value> <location>

Display command string

disp_element cbs_outage_cntr <location>

Values
Value type Valid range Default value Integer (number of broadcast slots) 0 to 255 0

6-134

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

ccch_conf

Description
The ccch_conf parameter specifies the organization of the Common Control Channels (CCCH) on the BCCH. This field defines whether the CCCHs are combined with SDCCH and SACCH onto the same basic physical channel. The value depends on the size of the cell and on the number of access attempts expected on the cell.

NOTE
When an attempt is made to change ccch_conf, and the requested PDTCHs exceed the GDS or PMC capacity on the PCU, the BSS accepts the request and issues a warning to indicate that there is not enough GDS or PMC resource available. If the chg_cell_element command is used to change the value of this parameter and the change allows hopping on a BCCH timeslot, the system rejects the command. The system rejects this command if it is attempted for all sites. Type Supported by OMC-R GUI B (operator actions required) Yes

Cell description required Dependencies

Yes If ccch_conf = 0, 2, 4, or 6, values for the following parameters must meet specific criteria: number_sdcchs_preferred must be in multiples of 8 starting at 8 with no offset (that is 8, 16, 24...128) The minimum number of sdcchs must be divisible by 8. max_number_of_sdcchs must be divisible by 8. bs_ag_blks_res = 0 to 7

If ccch_conf = 1, values for the following parameters must meet specific criteria: number_sdcchs_preferred must be in multiples of 8, with an offset of 4 (that is 4, 12, 20...128) The minimum number of sdcchs must be a multiple of 8 (+4).

68P02901W23-S

6-135 Nov 2009

Syntax

Chapter 6: CM database parameters

max_number_of_sdcchs must be a multiple of 8 (+4). bs_ag_blks_res = 0 to 2

Enabling of CBCH is not permitted (cbch-enabled = 1) if no AGCH is reserved in a non-combined cell (bs-ag-blks-res = 0 and ccch-conf is other than 1). This parameter can be used with the GPRS feature unrestricted as follows: Set to 0, seven PDCHs are supported for a BCCH carrier. Set to 1, seven PDCHs are supported for a BCCH carrier. Set to 2, six PDCHs are supported for a BCCH carrier. Set to 4, five PDCHs are supported for a BCCH carrier. Set to 6, four PDCHs are supported for a BCCH carrier.

The GPRS timeslots on the GPRS carrier must have the same FHI. GPRS channels must have the same training sequence codes. If GPRS is unrestricted for a cell, attempts to modify ccch_conf are rejected if the required timeslots are configured as GPRS timeslots. Because the PBCCH/PCCCH timeslots are configured on the BCCH carrier, any attempt to change ccch_conf, with the PBCCH/PCCCH optional feature unrestricted, results in a warning to the operator when pccch_enabled is set to 1. Operator actions Respond to the prompts presented after entering the chg_cell_element command.

Syntax
Add/Change command string
The system rejects this command if it is attempted when location = all. chg_cell_element ccch_conf <value> <cell_desc_opt>

NOTE
A site reset is required when the value of ccch_conf is changed. Resetting the site generates several alarms. However, the system blocks these alarms.

Display command strings

disp_element ccch_conf <location> <cell_desc>

6-136

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Values

Values
Value type Valid range Integer (CCH timeslots used; combined or non-combined) 0, 1, 2, 4, and 6 0 1 2 4 6 Default value 0 0 0 0, 2 0, 2, 4 0, 2, 4, 6 Non-combined Combined Non-combined Non-combined Non-combined

(0 CCH timeslots used; non-combined)

References
GSM parameters GSM specifications CCCH_CONF, CCCH_SDCCH_COMB 5.02 - 3.3.2: organization of common control channels 5.02 - 6.4: allowable channel configurations 4.03 - 5.1 and 6.2: organization of common control channels 5.02 - 6.5.1: BS_CC_CHANS, BS_CCCH_SDCCH_COMB 5.02 - 7: table 5 4.08 - 6.4: BS_CCCH_SDCCH_COMB

68P02901W23-S

6-137 Nov 2009

ccch_load_period

Chapter 6: CM database parameters

ccch_load_period

Description
The ccch_load_period parameter specifies the number of TDMA multiframes between successive calculations of the RACH load during overload conditions.

NOTE
Other parameters can affect flow control. Refer to rach_load_period, rach_overload_threshold, ssm_normal_overload_threshold, ssm_critical_overload_threshold or tch_flow_control.

Type Supported by OMC-R GUI Cell description required Dependencies

A (no operator actions) Yes Yes This parameter must be greater than or equal to the rach_load_period.

Syntax
Change command string
chg_element ccch_load_period <value> <location> <cell_desc> chg_cell_element ccch_load_period <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full] disp_element ccch_load_period <location> <cell_desc>

6-138

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Values

Values
Value type Valid range Default value Integer (1 Step = 1 TDMA multiframe) 1 to 1020 40

References
GSM parameter GSM specification CCCH_LOAD_IND_PERIOD 5.08.1.1 - 5.2.3

68P02901W23-S

6-139 Nov 2009

cell_bar_access_class

Chapter 6: CM database parameters

cell_bar_access_class

Description
The cell_bar_access_class parameter specifies access classes that are barred (or not barred) access to the PLMN. A channel request is initiated only when the access class of a mobile is not barred. The list of authorized access classes is broadcast on the BCCH by way of SYSTEM INFORMATION messages. Also broadcast are the classes that have access to emergency calls. There are 16 cell access classes, divided into four groups, as illustrated in the following diagram. 15 14 Z 0 = unbarred 1 = barred The value of Z (0 - Fh) controls access classes 15 through 12. The value of Y (0 - Fh) controls access classes 11 though 8. The value of X (0 - Fh) controls access classes 7 though 4. The value of W (0 - Fh) controls access classes 3 through 0. The hexadecimal value for cell_bar_access_class can be determined from the following diagram. For example, if access classes 2, 3, 7 and 9 were to be barred, the following are true: 15 0 14 0 Z Z = 0000 (0h) Y = 0010 (2h) X = 1000 (8h) W = 1100 (Ch) To bar access classes 2, 3 7 and 9, the set cell_bar_access_class=028Ch Access Class 10 (emergency access) cannot be barred. Setting bit 10 in this field does not bar the emergency access class. See also the emergency_class_switch parameter. Table 6-10 lists the values for barring classes. 13 0 12 0 11 0 10 0 Y 9 1 8 0 7 1 6 0 X 5 0 4 0 3 1 2 1 W 1 0 0 0 13 12 11 10 Y 9 8 7 6 X 5 4 3 2 W 1 0

6-140

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Description

Table 6-10
Hexadecimal value 0 1 2 3 4 5 6 7 8 9 a b c d e f

Values for barring classes

Z No barring bar class 12 bar class 13 bar classes 12 and 13 bar class 14 bar classes 12 and 14 bar classes 13 and 14 bar classes 12, 13 and 14 bar class 15 bar classes 12 and 15 bar classes 13 and 15 bar classes 12, 13 and 15 bar classes 14 and 15 bar classes 12, 14 and 15 bar classes 13, 14 and 15 bar classes 12, 13, 14 and 15 Y No barring bar class 8 bar class 9 bar classes 8 and 9 bar class 10 bar classes 8 and 10 bar classes 9 and 10 bar classes 8, 9 and 10 bar class 11 bar classes 8 and 11 bar classes 9 and 11 bar classes 8, 9 and 11 bar classes 10 and 11 bar classes 8, 10 and 11 bar classes 9, 10 and 11 bar classes 8, 9 10 and 11 X No barring bar class 4 bar class 5 bar classes 4 and 5 bar class 6 bar classes 4 and 6 bar classes 5 and 6 bar classes 4, 5 and 6 bar class 7 bar classes 4 and 7 bar classes 5 and 7 bar classes 4, 5 and 7 bar classes 6 and 7 bar classes 4, 6 and 7 bar classes 5, 6 and 7 bar classes 4, 5 6, and 7 W No barring bar class 0 bar class 1 bar classes 0 and 1 bar class 2 bar classes 0 and 2 bar classes 1 and 2 bar classes 0, 1 and 2 bar class 3 bar classes 0 and 3 bar classes 1 and 3 bar classes 0, 1 and 3 bar classes 2 and 3 bar classes 0, 2 and 3 bar classes 1,2 and 3 bar classes 0, 1, 2 and 3

NOTE
When entering a hexadecimal value, the suffix h is required.

Type Supported by OMC-R GUI Cell description required Dependencies

A (no operator actions) Yes Yes cell_bar_access_switch

68P02901W23-S

6-141 Nov 2009

Syntax

Chapter 6: CM database parameters

Syntax
Add/Change command strings
add_cell <gsm_cell_id> <location> chg_element cell_bar_access_class <value> <location> <cell_desc> chg_cell_element cell_bar_access_class <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full] disp_element cell_bar_access_class <location> <cell_desc>

Values
Value type Valid range Default value Integer 0 to 65535 0

References
GSM parameter GSM specification AC_CN 4.08 - 3.3.1. 4.08 - 3.3.1.1

6-142

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

cell_bar_access_switch

Description
The cell_bar_access_switch parameter specifies whether subscribers are barred access to a cell in idle mode. Emergency calls (user class 10) are not, and cannot be, barred. A MS decodes the BCCH data to determine if it is allowed access to the system. BCCH data includes information which indicates that the cell transmitting the data is part of the selected PLMN (unbarred) or not (barred). Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes None

Syntax
Add/Change command strings
add_cell <gsm_cell_id> <location> chg_element cell_bar_access_switch <value> <location> <cell_desc> chg_cell_element cell_bar_access_switch <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full] disp_element cell_bar_access_switch <location> <cell_desc>

68P02901W23-S

6-143 Nov 2009

Values

Chapter 6: CM database parameters

Values
Value type Valid range Boolean 0 or 1 0 1 Default value 0 Cell is not barred. Cell is barred.

References
GSM parameter GSM specifications CELL_BAR_ACCESS 4.08 - 10.5.2.17, figure. 10.36, table 10.30 5.08 - 6.2 5.08 - 6.4: C1 equation 12.20 - 5.2.8.7: - cell description - cell bar access 03.22 - 3.5.1

6-144

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

cell_bar_qualify

Description
The network uses the cell_bar_qualify parameter to control MS cell selection. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes This parameter cannot be changed if the cell_reselect_param_ind parameter does not equal 1.

Syntax
Add/Change command strings
add_cell <gsm_cell_id> <location> chg_element cell_bar_qualify <value> <location> <cell_desc> chg_cell_element cell_bar_qualify <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full] disp_element cell_bar_qualify <location> <cell_desc>

Values
Value type Valid range Boolean 0 or 1 0 1 Default value 0 Normal priority cell Low priority cell

68P02901W23-S

6-145 Nov 2009

References

Chapter 6: CM database parameters

References
GSM specification 3.22 4.08 Table 10.32 in section 10.5.2.35 5.08 Table 1a in section 9. This is a Motorola defined parameter.

6-146

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

cell_barred_delay

{32340}

Description
The cell_barred_delay parameter specifies the period the BSS delays sending SystemInformationUpdate message for SI 1, 2, 2bis to the MS during global reset procedure. This parameter can be updated both in and out of sysgen mode. Device/Function Type Supported by OMC-R GUI Cell description required Dependencies BSS A (no operator actions) Yes Yes None

Syntax
Change command strings
chg_element cell_barred_delay <new_value> 0

Display command strings

disp_element cell_barred_delay <location>

Values
Value type Valid range Default value Integer (seconds) 0 to 180 0

68P02901W23-S

6-147 Nov 2009

cell_reselect_hysteresis

Chapter 6: CM database parameters

cell_reselect_hysteresis

Description
The cell_reselect_hysteresis parameter specifies the hysteresis level for cell reselection into a different location area. The new cell is selected only if the path loss criterion parameter (C1) on the new cell exceeds C1 on the old cell by a minimum of value assigned to the cell_reselect_hysteresis parameter. Differences in received signal levels from 0 dB to 14 dB (in 2 dB increments) are used for cell reselection. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes C1 (path loss criterion)

Syntax
Add/Change command strings
add_cell <gsm_cell_id> <location> chg_element cell_reselect_hysteresis <value> <location> <cell_desc> chg_cell_element cell_reselect_hysteresis <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full] disp_element cell_reselect_hysteresis <location> <cell_desc>

6-148

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Values

Values
Value type Valid range Integer 0 to 7 Represents the signal level differences as shown below: 0 1 2 3 4 5 6 7 Default value None 0 dB 2 dB 4 dB 6 dB 8 dB 10 dB 12 dB 14 dB

References
GSM parameter GSM specifications CE_RE_HYS 5.08 - 6.6.2 4.08 - 10.5.2.4, figure 10.23, and table 10.17 12.20 - 5.2.8.12 - radio link ctl dl - cell reselect hysteresis

68P02901W23-S

6-149 Nov 2009

cell_reselect_offset

Chapter 6: CM database parameters

cell_reselect_offset

Description
The cell_reselect_offset parameter specifies a C2 offset value for the MS. C2 is the reselection priority assigned to a cell which can be broadcast on the BCCH of each cell. When more than one cell is available for reselection, the MS reselects the cell with the highest C2 value. Lower C2 values discourage fast moving MSs from selecting a specific cell. Higher values encourage MSs to reselect a specific cell. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes This parameter may not be changed if the cell_reselect_parm_ind parameter is not equal to 1.

Syntax
Add/Change command strings
add_cell <gsm_cell_id> <location> chg_element cell_reselect_offset <value> <location> <cell_desc> chg_cell_element cell_reselect_offset <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full] disp_element cell_reselect_offset <location> <cell_desc>

6-150

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Values

Values
Value type Valid range Integer (1 Step = 2 dB) 0 to 63 0 1 2 . . . 63 Default value 0 126 dB 0 dB 2 dB 4 dB

References
GSM parameter GSM specifications CELL_RESELECT_OFFSET 3.22 4.08 table 10.32a in section 10.5.2.35 5.08

68P02901W23-S

6-151 Nov 2009

cell_reselect_param_ind

Chapter 6: CM database parameters

cell_reselect_param_ind

Description
The cell_reselect_parameter_ind parameter specifies whether the C2 parameters (cell_bar_qualify, cell_reselect_offset, temporary_offset, and penalty_time) are broadcast to the MS by the network in the system information messages. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes None

Syntax
Add/Change command strings
add_cell <gsm_cell_id> <location> chg_element cell_reselect_param_ind <value> <location> <cell_desc> chg_cell_element cell_reselect_param_ind <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full] disp_element cell_reselect_param_ind <location> <cell_desc>

Values
Value type Valid range Boolean 0 or 1 0 1 Default value 0 Do not broadcast C2 cell reselection parameters on the BCCH of the cell. Broadcast C2 cell reselection parameters on the BCCH of the cell.

6-152

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

References

References
GSM parameter GSM specifications CELL_RESELECT_PARAM_IND 4.08 table 10.32a in section 10.5.2.355.08 This parameter is not used at the present time. C2 parameters are not used at the present time since they are dependent on this parameter being enabled.

68P02901W23-S

6-153 Nov 2009

channel_reconfiguration_switch

Chapter 6: CM database parameters

channel_reconfiguration_switch

Description
The channel_reconfiguration_switch parameter enables and disables dynamic channel reconfiguration (reassignment) of traffic channels to Standalone Dedicated Control Channels (SDCCHs). The Cell Resource Manager (CRM) may attempt to reconfigure an idle TCH into an SDCCH if a high proportion of SDCCHs is in use and additional SDCCH requests are received. The reconfiguration process continues until the number of idle SDCCHs reaches the sdcch_need_high_water_mark value. The reconfiguration process stops when the number of idle TCHs goes below the tch_full_need_low_water_mark value or when the total number of SDCCHs configured reaches the max_number_of_sdcchs value. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes None

Syntax
Change command strings
chg_element channel_reconfiguration_switch <value> <location> <cell_desc> chg_cell_element channel_reconfiguration_switch <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full] disp_element channel_reconfiguration_switch <location> <cell_desc>

6-154

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Values

Values
Value type Valid range Boolean 0 or 1 0 1 Default value 0 Disabled Enabled

References
GSM specification Figure 3 5.02 - 6.4: permitted channel combinations of logical channels This is a Motorola defined parameter.

68P02901W23-S

6-155 Nov 2009

cic_error_clr_thresh

Chapter 6: CM database parameters

cic_error_clr_thresh

Description
The cic_error_clr_thresh parameter specifies the error count threshold (equal to or less than) for an alarm to be cleared for a Circuit Identity Code (CIC). Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No Two successful calls are required on a resource before an alarm can be cleared within this threshold. (One successful call may be too short for the Channel Coder Unit (CCU) to send an error indication, thus clearing the alarm prematurely.) This parameter can be set only at a BSC. If the threshold is increased during operation, any existing counts between the new and the old threshold does not clear an alarm until another successful call is made on the CIC.

Syntax
Change command strings
chg_element cic_error_clr_thresh <value> 0

Display command strings

disp_element cic_error_clr_thresh 0

Values
Value type Valid range Default value Integer 0 to 253 0

6-156

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

cic_error_gen_thresh

Description
The cic_error_gen_thresh parameter specifies the error count threshold (equal to or greater than) for an alarm to be generated for a Circuit Identity Code (CIC). Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No This parameter can be set only at a BSC. If the threshold is changed during operation, no immediate alarm occurs. The new threshold takes effect only when the CIC error count changes.

Syntax
Change command strings
chg_element cic_error_gen_thresh <value> 0

Display command strings

disp_element cic_error_gen_thresh 0

Values
Value type Valid range Default value Integer 2 to 255 6

68P02901W23-S

6-157 Nov 2009

cic_error_inc

Chapter 6: CM database parameters

cic_error_inc

Description
The cic_error_inc parameter specifies the error count increment when the Circuit Error Rate Monitor (CERM) feature is in use for Circuit Identity Codes (CICs) on a per BSC basis. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No This parameter can be set only at a BSC.

Syntax
Change command strings
chg_element cic_error_inc <value> 0

Display command string

disp_element cic_error_inc 0

Values
Value type Valid range Integer 0 1 to 255 Default value 1 CIC alarms not raised. CIC alarms raised.

6-158

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

cic_validation

Description
The cic_validation parameter enables or disables the Circuit Identity Code (CIC) validation for an RXCDR. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No The cic_validation parameter should be enabled or disabled by one of the following methods: (1) In Sysgen mode (by updating the database through DataGen or by using the sysgen_on command at the MMI). (2) After executing the modify_value command, cycle (reset) the BSC to re-initialize all BSC mapping.

Syntax
Change command string
modify_value <location> cic_validation <value> AXCDR <axcdr_id>

Display command string

disp_equipment <location> AXCDR <axcdr_id>

Values
Value type Valid range Boolean No or Yes No Yes Default value None Disabled Enabled

68P02901W23-S

6-159 Nov 2009

ciph_mode_rej_allowed

Chapter 6: CM database parameters

ciph_mode_rej_allowed

Description
The ciph_mode_rej_allowed parameter enables or disables the Cipher Mode Reject message to be sent to the MSC. This message generates when the Cipher Mode Command message from the MSC specifies ciphering that the BSS or MS cannot perform. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No This parameter only applies to the BSC.

Syntax
Change command string
chg_element ciph_mode_rej_allowed <value> 0

Display command string

disp_element ciph_mode_rej_allowed 0

Values
Value type Valid range Boolean 0 or 1 0 1 Default value 0 Disabled Enabled

References
GSM specification TS GSM 08.08 This is a Motorola defined parameter.

6-160

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

clk_src_fail_reset_period

Description
The clk_src_fail_reset_period parameter specifies the length of time for which the OOS count is kept for the MMSs at a site. At the end of the reset period, all of the MMS OOS counts are reset to zero. The OOS counts are used in the selection process for an MMS as a reference clock for GCLK synchronization. If several MMSs have the same value assigned to the mms_priority parameter, the MMS with the lowest OOS count is selected. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No 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 Valid range Default value Integer (hours) 1 to 255 24

68P02901W23-S

6-161 Nov 2009

coincident_cell

Chapter 6: CM database parameters

coincident_cell

Description
The coincident_cell parameter specifies the cell that is coincident to the cell specified in the chg_cell_element coincident_mb prompt or the disp_cell command. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes This parameter may only be changed if the Coincident MultiBand Handover option is unrestricted. If coincident_mb is set to 1 or 2, both cells must be SACCH neighbors of each other. If coincident_mb is set to 2, both cells must be at the same site, the cells must be neighbors of each other, and the bsic settings must be the same. A cell cannot be coincident to itself.

NOTE
If all is entered for the del_neighbor command for a BTS at which the Coincident MultiBand Handover option is enabled and contains any coincident cells, the command is rejected.

Syntax
Change command string
chg_cell_element coincident_cell <value> <cell_desc_opt> The system prompts for the cell number for the coincident_cell.

Display command strings

disp_cell <cell_id> [full] disp_element coincident_cell <location> <cell_desc>

6-162

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Values

Values
Value type Valid range Default value Integer The GSM cell ID number. None

68P02901W23-S

6-163 Nov 2009

coincident_offset

Chapter 6: CM database parameters

coincident_offset

Description
The coincident_offset parameter enables and disables the configuration of an additional offset to the ho_margin value between a cell and its coincident cell. The system uses the coincident_offset value when a handover from a MultiBand MS is based on the receive level for the serving cell. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes This parameter may only be changed if the Coincident MultiBand Handover option is enabled.

Syntax
Change command strings
chg_element coincident_offset <value> <location> <cell_desc> chg_cell_element coincident_offset <value> <cell_desc_opt> The system prompts for: The cell number for the coincident cell. The low signal threshold. See Prompt field values in the description of chg_cell_element on page 3-84.

Display command string

disp_element coincident_offset <location> <cell_desc>

Values
Value type Valid range Default value Integer (dB) -63 to 63 0

6-164

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

coincident_mb

Description
The coincident_mb parameter specifies the ability of a BTS to execute the Coincident MultiBand Handover option. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes This parameter may only be changed if the Coincident MultiBand Handover option is enabled. If coincident_mb is set to 1 or 2, both cells must be SACCH neighbors of each other. If coincident_mb is set to 2, both cells must be at the same site, the cells must be neighbors of each other, and the bsic settings must be the same. If a coincident cell has not been selected, the value of coincident_mb must equal 0. A cell cannot be coincident to itself. This parameter must be disabled when inner_zone_alg is set to indicate Dual Band Cells. The copy_cell command sets the coincident cell to an invalid value, and the coincident_mb to 0 at the new cell. The delete_cell command is rejected if the cell specified for deletion is a coincident cell of any other cell at a site that has the Coincident Multiband Handover option enabled. If all is entered for the del_neighbor command for a BTS at which the Coincident MultiBand Handover option is enabled, and contains any coincident cells, the command is rejected.

Syntax
Change command string
chg_cell_element coincident_mb <value> <cell_desc_opt> The system prompts for the cell number for the coincident_cell.

68P02901W23-S

6-165 Nov 2009

Values

Chapter 6: CM database parameters

Display command strings

disp_cell <cell_id> [full] disp_element coincident_mb <location> <cell_desc>

Values
Value type Valid range Integer 0 to 3 0 1 2 3 Coincident Multiband is disabled at the cell. Coincident cell handovers are enabled. Coincident cell handovers and coincident cell redirections are enabled. Intra BSC handovers behave the same as when coincident_mb=2, but for inter BSC handovers the call is targeted at the primary cell.

Default value

6-166

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

confusion_msg_allowed

Description
The confusion_msg_allowed parameter enables and disables the BSS to send Confusion messages over the A-interface when an erroneous message is received from the MSC. If this parameter is not enabled, the system generates an alarm instead of sending a message to the MSC. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No This parameter does not apply to RXCDR sites. This parameter only applies to the BSC.

Syntax
Change command string
chg_element confusion_msg_allowed <value> 0

Display command string

disp_element confusion_msg_allowed 0

Values
Value type Valid range Boolean 0 or 1 0 1 Default value 0 Disabled Enabled

References
GSM specification TS GSM 8.08 This is a Motorola defined parameter.

68P02901W23-S

6-167 Nov 2009

congest_at_source

Chapter 6: CM database parameters

congest_at_source

Description
The congest_at_source parameter specifies how a specified source cell treats target cells when trying to find candidates for an imperative handover. The specified source cell may be enabled to: (a) treat all target cells equally or (b) immediately retry target cells which were in the process of congestion relief.

NOTE
Target cells that are in the process of Congestion Relief may become available for handovers more quickly than those that are not.

Type Supported by OMC-R GUI Cell number required Dependencies

A (no operator actions) Yes Yes The parameter can be set only if the Congestion Relief feature is unrestricted.

Syntax
Change command strings
chg_element congest_at_source <value> <location> <cell_desc> chg_cell_element congest_at_source <value> <cell_desc_opt>

Display command string

disp_element congest_at_source <location> <cell_desc>

6-168

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Values

Values
Value type Valid range Boolean 0 or 1 0 1 Default value 0 The source cell treats all target cells equally as candidates for imperative handovers. The source cell immediately retries target cells which were in the process of congestion relief.

NOTE
Refer to the congest_at_target parameter to see when a target cell performs congestion relief procedures.

68P02901W23-S

6-169 Nov 2009

congest_at_target

Chapter 6: CM database parameters

congest_at_target

Description
The congest_at_target parameter specifies how a specified cell behaves if it rejects a handover request. Type Supported by OMC-R GUI Cell number required Dependencies A (no operator actions) Yes Yes The parameter can be set only if the Congestion Relief feature is unrestricted.

Syntax
Change command strings
chg_element congest_at_target <value> <location> <cell_desc> chg_cell_element congest_at_target <value> <cell_desc_opt>

Display command string

disp_element congest_at_target <location> <cell_desc>

Values
Value type Valid range Boolean 0 or 1 0 1 Default value 0 The system takes no action if the Cell rejects a handover request. The system invokes Congestion Relief procedures if this Cell rejects a handover request.

6-170

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

congest_ho_margin

Description
The congest_ho_margin parameter specifies the margin of a congestion handover. To make it easier to hand over to this neighbor in the case of congestion in the current cell, this parameter value should be less that the value of the handover margin. To disable congestion handovers to this neighbor, set the congestion handover margin to the maximum value. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No This parameter can only be modified if: either the Directed Retry or Alternate Congestion Relief options are available, and the neighbor is placed on the SACCH list.

Syntax
Change command string
modify_neighbor <source_cell_id> <neighbor_cell_id> congest_ho_margin <value>

Display command string

disp_neighbor <src_cell_id> [<neighbor_cell_id>|all] disp_neighbor <source cell_name> [<internal neighbor cell_name>] disp_neighbor <src_cell_id> ["test" <test neighbor_cell_id>]]

Values
Value type Valid range Default value Integer (each step equals 1 dB) -63 to 63 None

68P02901W23-S

6-171 Nov 2009

cp_option_reset_ckt

Chapter 6: CM database parameters

cp_option_reset_ckt

Description
The cp_option_reset_ckt parameter enables and disables the reset circuit feature. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No 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 Valid range Boolean 0 or 1 0 1 Default value 0 Disabled Enabled

6-172

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

cp_option_rr_status

Description
The cp_option_rr_status parameter enables and disables the radio resource status. If radio resource status is enabled, the BSS can generate the 4.08 radio resource status message to the MS. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No 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 Valid range Boolean 0 or 1 0 1 Default value 0 Disabled Enabled

68P02901W23-S

6-173 Nov 2009

cr_calling

Chapter 6: CM database parameters

cr_calling

Description
The cr_calling parameter enables or disables the calling party address being included in the SCCP message Connection Request. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No This parameter only applies to the BSC.

Syntax
Change command string
chg_element cr_calling <value> 0

Display command string

disp_element cr_calling 0

Values
Value type Valid range Boolean 0 or 1 0 1 Default value 0 Disabled Enabled

6-174

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

ct_flow_control_hi_level

Description
The ct_flow_control_hi_level parameter specifies the percentage of call trace OML buffer space that may be used before flow control is enabled. When this limit is reached, the BSS parameter ct_flow_control_bss_enabled is set to 1. (This level is not used to disable flow control.) Setting this parameter to 100 disables flow control. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No ct_flow_control_hi_level must be greater than ct_flow_control_lo_level plus 20.

Syntax
Change command string
chg_element ct_flow_control_hi_level <value> <location>

Display command string

disp_element ct_flow_control_hi_level <location>

Values
Value type Valid range Default value Integer 20 to 100 60

68P02901W23-S

6-175 Nov 2009

ct_flow_control_lo_level

Chapter 6: CM database parameters

ct_flow_control_lo_level

Description
The ct_flow_control_lo_level parameter specifies the percentage of call trace OML buffer space that may be used before flow control is enabled. When this limit is reached, the BSS parameter ct_flow_control_bss_enabled is set to 0. (This level is not used to disable flow control.) Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No ct_flow_control_lo_level must be less than ct_flow_control_hi_level minus 20.

Syntax
Change command string
chg_element ct_flow_control_lo_level <value> <location>

Display command string

disp_element ct_flow_control_lo_level <location>

Values
Value type Valid range Default value Integer 0 to 80 20

6-176

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

ct_flow_control_msc_trace

Description
The ct_flow_control_msc_trace parameter specifies whether MSC traces are allowed when flow control is enabled. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No 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 Valid range Boolean 0 or 1 0 1 Default value 0 MSC traces are allowed while flow is restricted. MSC traces are not allowed while flow is restricted.

68P02901W23-S

6-177 Nov 2009

ctu2d_asym_opt

Chapter 6: CM database parameters

ctu2d_asym_opt

{30830}

Description
The ctu2d_asym_Opt parameter indicates whether the CTU2-D asymmetric feature functionality is restricted or unrestricted in the BSS software. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes The CTU2-D asymmetric feature requires EGPRS and Capacity to be unrestricted.

Syntax
Display command strings
disp_options all

Values
Value type Valid range Boolean 0 or 1 0 1 Default value N/A Disabled Enabled

6-178

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

ctu2d_cap_opt

{30828}

Description
The ctu2d_cap_Opt parameter indicates whether the CTU2-D capacity feature functionality is restricted or unrestricted in the BSS software. Type Supported by OMC-R GUI Cell description required Dependencies A (No operator actions required) Yes Yes The CTU2-D capacity feature requires the EGPRS feature to be unrestricted.

Syntax
Display command string
disp_options all

Values
Value type Valid range Boolean 0 or 1 0 1 Default value N/A Disabled Enabled

68P02901W23-S

6-179 Nov 2009

c31_hyst

Chapter 6: CM database parameters

c31_hyst

Description
The c31_hyst parameter is a flag specifying whether hysteresis is applied to C31. Type Supported by OMC-R GUI Cell description required Dependencies A (No operator actions required) Yes Yes The PBCCH/PCCCH optional feature must be unrestricted.

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

Syntax
Change command string
chg_cell_element c31_hyst <value> <cell_desc_opt> chg_cell_element <location> c31_hyst <value> all chg_element c31_hyst <value> <location> <cell_desc>

Display command string

disp_cell <cell_id> full disp_element c31_hyst <location> <cell-desc> disp_element c31_hyst <location> all

6-180

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Values

Values
Value type Valid range Boolean 0 or 1 0 1 Default value 0 Hysteresis not applied. Hysteresis applied.

68P02901W23-S

6-181 Nov 2009

c32_qual

Chapter 6: CM database parameters

c32_qual

Description
The c32_qual parameter is a flag specifying whether the exception rule is allowed with the gprs_reselect_offset parameter at a cell. Type Supported by OMC-R GUI Cell description required Dependencies A (No operator actions required) Yes Yes The PBCCH/PCCCH optional feature must be unrestricted.

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

Syntax
Change command string
chg_cell_element c32_qual <value> <cell_desc_opt> chg_cell_element <location> c32_qual <value> all chg_element c32_qual <value> <location> <cell_desc>

Display command string

disp_cell <cell_id> full disp_element c32_qual <location> <cell-desc> disp_element c32_qual <location> all

6-182

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Values

Values
Value type Valid range Boolean 0 or 1 0 1 Default value 0 Exception not allowed. Exception allowed.

68P02901W23-S

6-183 Nov 2009

data_qual_enabled

Chapter 6: CM database parameters

data_qual_enabled

Description
The data_qual_enabled parameter enables or disables the use of specific rxqual thresholds for data call handovers. A data call is one that involves the transmission of computer data, such as a modem-to-modem call. These types of calls are sensitive to bit errors. Therefore, specific rxqual thresholds may be configured to trigger data call handovers. If the data_qual_enabled parameter is enabled and a data call is in progress, the system uses the rxqual data parameters set with the chg_cell_element command, as listed in Syntax, instead of the normal rxqual values set with the add_cell command.

NOTE
If both the data_qual_enabled and the hop_qual_enabled parameters are ON, the data_qual_enabled parameter takes precedence in conditions where both apply, that is, data transmission in a hopping call.

Type Supported by OMC-R GUI Cell description required Dependencies

A (no operator actions) Yes Yes alt_qual_proc

Syntax
Change command strings
chg_cell_element data_qual_enabled <value> <cell_desc_opt> If the value is 1 (enabled) the system prompts for the data threshold values as the following parameters: l_rxqual_dl_h on page 6-462. l_rxqual_dl_p on page 6-474. l_rxqual_ul_h on page 6-488. l_rxqual_ul_p on page 6-500.

6-184

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Values

Display command strings

disp_cell <cell_id> [full] disp_element data_qual_enabled <location> <cell_desc>

Values
Value type Valid range Boolean 0 or 1 0 1 Default value 0 Disabled Enabled

68P02901W23-S

6-185 Nov 2009

ddtr_ctrl_enabled

Chapter 6: CM database parameters

ddtr_ctrl_enabled

Description
The ddtr_ctrl_enabled parameter is used to enable and disable the delayed downlink Temporary Block Flow (TBF) release duration and extended uplink TBF duration, as a function of cell availability. The ddtr_ctrl_enabled parameter is configurable on a per BSS basis. Type Supported by OMC-R GUI Cell description required Dependencies Operator actions A Yes No {26881} The GPRS and increased PRP capacity features must be unrestricted. None

Syntax
Add/Change command strings
chg_element ddtr_ctrl_enabled <value> <location>

Display command strings

disp_element ddtr_ctrl_enabled <location>

Values
Value type Valid range Boolean 0 or 1 0 1 Default value 0 Disabled Enabled (Disabled)

6-186

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

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 Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes surround_cell

Syntax
Add/Change command strings
add_cell <gsm_cell_id> <location> chg_element decision_1_ncell_rxlev_av_h_calc <value> <location> <cell_desc>

Display command strings

disp_cell <cell_id> [full] disp_element decision_1_ncell_rxlev_av_h_calc <location> <cell_desc>

Values
Value type Valid range Default value Boolean 0 or 1 0

68P02901W23-S

6-187 Nov 2009

decision_1_dl_rxlev_av_ih

Chapter 6: CM database parameters

decision_1_dl_rxlev_av_ih

Description
The decision_1_dl_rxlev_av_ihparameter specifies the bin number containing the measurement averaging algorithm data used to make handover decisions for downlink signal interference. This parameter may not be changed to a bin which does not contain valid handover data. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes rxlev_dl_ho

Syntax
Add/Change command strings
add_cell <gsm_cell_id> <location> chg_element decision_1_dl_rxlev_av_ih <value> <location> <cell_desc> chg_cell_element decision_1_dl_rxlev_av_ih <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full] disp_element decision_1_dl_rxlev_av_ih <location> <cell_desc>

Values
Value type Valid range Default value Boolean 0 to 1 0

6-188

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

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 Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes rxqual_dl_ho

Syntax
Add/Change command strings
add_cell <gsm_cell_id> <location> chg_element decision_1_dl_rxqual_av_h <value> <location> <cell_desc> chg_cell_element decision_1_dl_rxqual_av_h <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full] disp_element decision_1_dl_rxqual_av_h <location> <cell_desc>

Values
Value type Valid range Default value Boolean 0 to 1 0

68P02901W23-S

6-189 Nov 2009

decision_1_dl_rxqual_av_p

Chapter 6: CM database parameters

Values
Value type Valid range Default value Boolean 0 or 1 0

68P02901W23-S

6-207 Nov 2009

decision_1_tim_adv_av_alg

Chapter 6: 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 Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes rel_tim_adv

Syntax
Add/Change command strings
add_cell <gsm_cell_id> <location> chg_element decision_1_tim_adv_av_alg <value> <location> <cell_desc> chg_cell_element decision_1_tim_adv_av_alg <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full] disp_element decision_1_tim_adv_av_alg <location> <cell_desc>

Values
Value type Valid range Default value Boolean 0 or 1 0

6-208

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

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 Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes rxlev_ul_ho

Syntax
Add/Change command strings
add_cell <gsm_cell_id> <location> chg_element decision_1_ul_rxlev_av_h <value> <location> <cell_desc> chg_cell_element decision_1_ul_rxlev_av_h <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full] disp_element decision_1_ul_rxlev_av_h <location> <cell_desc>

Values
Value type Valid range Default value Boolean 0 or 1 0

68P02901W23-S

6-209 Nov 2009

decision_1_ul_rxlev_av_ih

Chapter 6: 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 Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes rxlev_ul_ho

Syntax
Add/Change command strings
add_cell <gsm_cell_id> <location> chg_element decision_1_ul_rxlev_av_ih <value> <location> <cell_desc> chg_cell_element decision_1_ul_rxlev_av_ih <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full] disp_element decision_1_ul_rxlev_av_ih <location> <cell_desc>

Values
Value type Valid range Default value Boolean 0 or 1 0

6-210

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

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 Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes rxlev_ul_pc

Syntax
Add/Change command strings
add_cell <gsm_cell_id> <location> chg_element decision_1_ul_rxlev_av_p <value> <location> <cell_desc> chg_cell_element decision_1_ul_rxlev_av_p <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full] disp_element decision_1_ul_rxlev_av_p <location> <cell_desc>

Values
Value type Valid range Default value Boolean 0 or 1 0

68P02901W23-S

6-211 Nov 2009

decision_1_ul_rxqual_av_h

Chapter 6: 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 Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes rxqual_ul_ho

Syntax
Add/Change command strings
add_cell <gsm_cell_id> <location> chg_element decision_1_ul_rxqual_av_h <value> <location> <cell_desc> chg_cell_element decision_1_ul_rxqual_av_h <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full] disp_element decision_1_ul_rxqual_av_h <location> <cell_desc>

Values
Value type Valid range Default value Boolean 0 or 1 0

6-212

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

decision_1_ul_rxqual_av_p

Description
The decision_1_ul_rxqual_av_p parameter specifies the bin number containing the measurement averaging algorithm data used to generate power control changes due to the uplink receive quality. This parameter may not be changed to a bin which does not contain valid power control data. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes rxqual_ul_pc

Syntax
Add/Change command strings
add_cell <gsm_cell_id> <location> chg_element decision_1_ul_rxqual_av_p <value> <location> <cell_desc> chg_cell_element decision_1_ul_rxqual_av_p <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full] disp_element decision_1_ul_rxqual_av_p <location> <cell_desc>

Values
Value type Valid range Default value Boolean 0 or 1 0

68P02901W23-S

6-213 Nov 2009

decision_alg_type

Chapter 6: 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 Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes None

Syntax
Add/Change command strings
add_cell <gsm_cell_id> <location> chg_element decision_alg_type <value> <location> <cell_desc> chg_cell_element decision_alg_type <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full] disp_element decision_alg_type <location> <cell_desc>

6-214

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Values

Values
Value type Valid range Boolean (algorithms) 0 or 1 0 1 Default value 0 Power control algorithm number 1. Power control algorithm number 2 (enables the use of p_con_ack timers).

68P02901W23-S

6-215 Nov 2009

direct_inner_zone_threshold

Chapter 6: CM database parameters

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 Supported by OMC-R GUI Cell description required Dependencies Operator actions A (no operator action) Yes Yes The Concentric Cells feature must be enabled in order to set this parameter. None

Syntax
Change command strings
chg_element direct_inner_zone_threshold <value> <location> <cell_desc> chg_cell_element direct_inner_zone_threshold <value> <cell_desc_opt>

Display command string

disp_element direct_inner_zone_threshold <location> <cell_desc>

Values
Value type Valid range Default value Integer 0 to 63 63

6-216

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

disuse_cnt_hreqave

Description
The disuse_cnt_hreqave determines the maximum disuse count for neighbor cells to be valid candidates for handover. Disuse count is the number of consecutive measurement reports a previously reported neighbor is not reported by the mobile station. If the neighbor is reported before the maximum disuse count is reached, the disuse count is reset to 0 and the neighbor remains a valid candidate. When the disuse_cnt_hreqave parameter is enabled, the surrounding cell hreqave defines the maximum disuse count (this can be different for each neighbor). Neighbor cells with a disuse count less than or equal to the maximum disuse count are still valid candidates for handovers. When the disuse_cnt_hreqave parameter is disabled, the maximum disuse count is set to 8. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes None

Syntax
Change command strings
chg_element disuse_cnt_hreqave <value> <location> <cell_desc> chg_cell_element disuse_cnt_hreqave <value> <location> <cell_desc_opt>

Display command string

disp_element disuse_cnt_hreqave <location> <cell_desc>

68P02901W23-S

6-217 Nov 2009

Values

Chapter 6: CM database parameters

Values
Value type Valid range Boolean 0 or 1 0 1 Default value 0 Disabled Maximum disuse count is set to 8. Enabled Maximum disuse count is defined by the surrounding cell hreqave.

6-218

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

dl_audio_lev_offset

Description
The dl_audio_lev_offset parameter specifies the downlink volume control offset on a per BSS basis. The offset is in 1 dB steps with a maximum increase or decrease of 30 dB (between -15 dB and 15 dB). The audio level parameters affect background and comfort noise. The audio level parameters do not affect data.

NOTE
Changes to this parameter take effect immediately. This includes active calls.

NOTE
For the BSC side, turn the parameter on with a chg_ele command. chg_ele ul/dl_audio_lev_offset <value> = 0 where <value> is the audio level offset +15 to -15 in steps of 1dB. To change these values at the RXCDR, use the modify_values command on the ABSS device.

Type Supported by OMC-R GUI Cell description required Dependencies

A (no operator actions) Yes No 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.

68P02901W23-S

6-219 Nov 2009

Syntax

Chapter 6: CM database parameters

Syntax
Change command string
chg_element dl_audi_lev_offset <value> <location>

Display command string

disp_element dl_audio_lev_offset 0

Values
Value type Valid range Default value Integer (1 Step = 1 dB) -15 to +15 0

6-220

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

dl_dtx_voice_data

Description
The dl_dtx_voice_data parameter specifies the option for downlink discontinuous transmission (DTX) for speech and voice. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes The dl_dtx_voice_data parameter affects speech only if dnlk_vad_dtx is enabled.

Syntax
Change command strings
chg_element dl_dtx_voice_data <value> <location> <cell_desc> chg_cell_element dl_dtx_voice_data <value> <cell_desc_opt>

Display command string

disp_element dl_dtx_voice_data <location> <cell_desc>

Values
Value type Value range Integer 0 to 3 0 1 2 3 Default value DTX enabled for speech / disabled for non-transparent data. DTX disabled for speech / disabled for non-transparent data. DTX disabled for speech / enabled for non-transparent data. DTX enabled for speech / enabled for non-transparent data. 0

68P02901W23-S

6-221 Nov 2009

dl_rxlev_ho_allowed

Chapter 6: 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 Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes None

Syntax
Add/Change command strings
add_cell <gsm_cell_id> <location> chg_element dl_rxlev_ho_allowed <value> <location> <cell_desc> chg_cell_element dl_rxlev_ho_allowed <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full] disp_element dl_rxlev_ho_allowed <location> <cell_desc>

Values
Value type Valid range Boolean 0 or 1 0 1 Default value 1 Disabled Enabled

6-222

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

References

References
Internal name EN_RXLEV_HO This is a Motorola parameter.

68P02901W23-S

6-223 Nov 2009

dl_rxqual_ho_allowed

Chapter 6: 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 Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes None

Syntax
Add/Change command strings
add_cell <gsm_cell_id> <location> chg_element dl_rxqual_ho_allowed <value> <location> <cell_desc> chg_cell_element dl_rxqual_ho_allowed <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full] disp_element dl_rxqual_ho_allowed <location> <cell_desc>

Values
Value type Valid range Boolean 0 or 1 0 1 Default value 1 Disabled Enabled

6-224

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

References

References
Internal name EN_RXQUAL_HO This is a Motorola parameter.

68P02901W23-S

6-225 Nov 2009

dnlk_vad_dtx

Chapter 6: 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. The downlink DTX is supported only on the non-BCCH carrier. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No 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 Valid range Boolean 0 or 1 0 1 Default value None Enabled Disabled

6-226

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

dpc

Description
The dpc parameter specifies the Destination Point Code (DPC). The range of values depends on the setting of the parameter. The system checks the value of the opc (see opc on page 6-621) and ss7_mode (see ss7_mode on page 6-814) 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 Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No 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 Valid range Integer 0 to 16383 0 to 16777215 Default value None If ss7_mode = 0 (CCITT) If ss7_mode =1 (Bellcore)

68P02901W23-S

6-227 Nov 2009

References

Chapter 6: CM database parameters

References
GSM parameter GSM specification DPC CCITT Q.708

6-228

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

dr_allowed

Description
The dr_allowed parameter enables or disables the Directed Retry feature. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No This parameter can be modified only if all the following conditions are met: the Directed Retry feature is available, the neighbor is placed on the SACCH list, and the neighbor is external.

Syntax
Change command strings
modify_neighbor <src_cell_id> <neighbor_cell_id> dr_allowed <value>

Display command string

disp_neighbor <src_cell_id> all

Values
Value type Valid range Boolean 0 or 1 0 1 Default value None Disabled Enabled

68P02901W23-S

6-229 Nov 2009

dr_chan_mode_modify

Chapter 6: CM database parameters

dr_chan_mode_modify

Description
The dr_chan_mode_modify parameter determines if the channel mode modify procedure follows a successful handover of a Phase 1 MS in which the channel mode changed to full rate speech. The BSS reads this parameter only in the case of a successful handover in which the channel mode changed, the MS is Phase 1, and the new channel mode is full rate speech. Changing the channel mode during a handover occurs only during a Directed Retry procedure. For this to occur, either an external Directed Retry handover has successfully completed to this BSS or an intra-BSS Directed Retry handover has successfully completed and either the database parameter dr_standard_congest or dr_ho_during_assign is enabled in the source cell. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No 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 Valid range Boolean 0 or 1 0 1 Default value 0 Disabled Enabled

6-230

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

References

References
GSM specification TS GSM 08.08 ETR 09.94 This is a Motorola defined parameter.

68P02901W23-S

6-231 Nov 2009

dr_ho_during_assign

Chapter 6: CM database parameters

dr_ho_during_assign

Description
The dr_ho_during_assign parameter determines if a handover is handled during an assignment procedure. This parameter can only be changed at the BSC. This parameter is copied if the copy_cell command is used. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes The MSC may need to increase the timer waiting for the Assignment Complete message from the BSS when this database parameter is enabled. The BSS does not initiate an external handover due to the Directed Retry procedure if the msc_preference parameter indicates that directed retry is supported only within the BSS (not across the A-interface) when the dr_standard_congest parameter is enabled. The Directed Retry feature must be unrestricted. This parameter requires that dr_preference be enabled.

Syntax
Change command strings
chg_element dr_ho_during_assign <value> <location> <cell_desc> chg_cell_element dr_ho_during_assign <value> <cell_desc_opt>

Display command string

disp_element dr_ho_during_assign <location> <cell_desc>

6-232

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Values

Values
Value type Valid range Boolean 0 or 1 0 1 Default value 0 Ignore the need of a handover until the assignment procedure is complete. Act on the need for a handover during the assignment procedure.

References
GSM specification TS GSM 08.08 This is a Motorola defined parameter.

68P02901W23-S

6-233 Nov 2009

dr_preference

Chapter 6: CM database parameters

dr_preference

Description
The dr_preference parameter enables or disables the Directed Retry procedures. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No 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 Valid range Boolean 0 or 1 0 1 Default value 0 Disabled Enabled

References
GSM specification TS GSM 08.08 This is a Motorola defined parameter.

6-234

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

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 Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes The Directed Retry feature must be unrestricted. The dr_preference parameter must not be set to zero. The MSC may need to increase the timer waiting for the Assignment Complete message from the BSS when this database parameter is enabled. The BSS does not initiate an external handover due to the Directed Retry procedure if the msc_preference parameter indicates that directed retry is supported within the BSS (not across the A-interface) when the dr_standard_congest parameter is enabled.

Syntax
Change command strings
chg_element dr_standard_congest <value> <location> <cell_desc> chg_cell_element dr_standard_congest <value> <cell_desc_opt>

Display command string

disp_element dr_standard_congest <location> <cell_desc>

68P02901W23-S

6-235 Nov 2009

Values

Chapter 6: CM database parameters

Values
Value type Valid range Boolean 0 or 1 0 1 Default value 0 Disabled Enabled

References
GSM specification TS GSM 08.08 This is a Motorola defined parameter.

6-236

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

dri_density

Description
The dri_density parameter specifies the density mode (single, double or {30828} double density capacity). {30828} The range of this parameter is extended to a third allowed value: Capacity (double density without time slot blanking on the non-EDGE carrier). Type A (no operator actions)

Supported by OMC-R GUI Cell description required Dependencies

Yes No A number of existing parameters that can be modified under the DRI device are affected by the double density DRI devices. Modifications of tcu_port and antenna_select are propagated to the associated DRI device if the DRI being modified is in double density mode. The parameter combining_type is not valid to be modified for double density DRI devices. The extended range for this attribute (value 3) is valid only when: The configured DRI is in a Horizon II family (Horizon macro, Horizon II mini and Horizon II micro including extension) cabinet. The master SITE cabinet is a Horizon II family cabinet. (Horizon II macro, Horizon II mini and Horizon II micro). CTU2-D capacity feature (ctu2dcapOpt) is Enabled at the BSS.

{27236} To enable 4 Branch Receive Diversity, the DRIs should be equipped in a single band Horizon II macro cabinet and the DRI is modified to single density mode.

68P02901W23-S

6-237 Nov 2009

Syntax

Chapter 6: CM database parameters

Syntax
Modify/Change command strings
equip <location> dri modify_value <location> dri_density <value> dri <dev_fun_id1> <dev_fun_id2> <dev_fun_id3>

Display command strings

disp_equipment <location> dri <id1> <id2> <id3>

Values
Value type Valid range Integer 1 to 3 1 2 3 Default value None Single density Double density Double density capacity

6-238

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

dsp_error_clr_thresh

{26740}

Description
The dsp_error_clr_thres parameter identifies the value for which the error count must be equal or less than for an alarm to be cleared for a DSP . Always satisfy the condition (dsp_error_gen_thresh - dsp_error_clr_thresh) >=2. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No The dsp_error_clr_thresh parameter is restricted by the Enhanced Circuit Error Rate Monitor restrictable feature. The parameter is restricted so that at least two GPRS Alarm Increment Time Periods can pass without a sync loss error occurring on a resource before an alarm is cleared. It is necessary to look for sufficient successes to avoid clearing the alarm on one or more successful GPRS Alarm Increment Time Period that had too short a duration for the CCU to time out and send an error indication.

Syntax
Modify/Change command strings
chg_element dsp_error_clr_thres <value> <location>

Display command strings

disp_element dsp_error_clr_thres <location>

68P02901W23-S

6-239 Nov 2009

Values

Chapter 6: CM database parameters

Values
Value type Valid range Default value Integer 0 to 253 0

6-240

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

dsp_error_gen_thresh

{26740}

Description
The dsp_error_gen_thresh parameter identifies the value where the error count must be equal to or greater than for an alarm to be generated for a DSP . Always satisfy the condition (dsp_error_gen_thresh - dsp_error_clr_thresh) >=2. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No The dsp_error_gen_thresh parameter is restricted by the Enhanced Circuit Error Rate Monitor restrictable feature. The parameter is restricted so that at least two GPRS Alarm Increment/Decrement Time Periods can pass without a sync loss error occurring on a resource before an alarm can be cleared. It is necessary to look for sufficient successes to avoid clearing the alarm on one or more successful GPRS Alarm Increment/Decrement Time Period that had too short a duration for the CCU to time out and send an error indication.

Syntax
Modify/Change command strings
chg_element dsp_error_gen_thresh <value> <location>

Display command strings

disp_element dsp_error_gen_thresh <location>

Values
Value type Valid range Default value Integer 2 to 255 6

68P02901W23-S

6-241 Nov 2009

dsp_error_inc

Chapter 6: CM database parameters

dsp_error_inc

{26740}

Description
The dsp_error_inc parameter identifies the value by which the error count is incremented if an error indication is received for a DSP during a GPRS Alarm Increment Time Period. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No The dsp_error_inc parameter is restricted by the Enhanced Circuit Error Rate Monitor restrictable feature. When the dsp_error_inc parameter is set to 0 outside the sysgen mode, the operator is warned that the DSP alarms may be prevented from being generated.

Syntax
Modify/Change command strings
chg_element dsp_error_inc <value> <location>

Display command strings

disp_element dsp_error_inc <location>

Values
Value type Valid range Default value Integer 0 to 255 1 0 This parameter is defaulted to 1 when the ECERM feature is unrestricted. This parameter is defaulted to 0 (feature turned off) if the ECERM feature is restricted.

6-242

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

dtx_required

Description
The dtx_required parameter specifies the MS capability to use discontinuous transmission (DTX). Enabling this feature helps to reduce interference and prolong battery life. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes None

Syntax
Add/Change command strings
add_cell <gsm_cell_id> <location> chg_element dtx_required <value> <location> <cell_desc> chg_cell_element dtx_required <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full] disp_element dtx_required <location> <cell_desc>

Values
Value type Valid range Integer 0 to 2 0 1 2 Default value 2 Permitted (MS may use DTX) Required (MS must use DTX) Disallowed (MS must not use DTX)

68P02901W23-S

6-243 Nov 2009

References

Chapter 6: CM database parameters

References
GSM parameter GSM specification DTX 4.08 - 10.5.2.3, figure 10.22, table 10.16

6-244

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

dual_band_offset

Description
The dual_band_offset parameter estimates the effects of the power level differences that occur when comparing signal strengths from different zones. The dual_band_offset is applied to power budget handover calculations from the inner zone to cells of any frequency type. Plus, it is used to evaluate the criteria for the inter zone handovers within a cell. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes This parameter may be modified only when the Dual Band Cells feature is unrestricted.

Syntax
Change command string
chg_cell_element <location> dual_band_offset <value>

Display command string

disp_element dual_band_offset <location> <cell_desc>

Values
Value type Valid range Default value Integer -63 to 63 0

68P02901W23-S

6-245 Nov 2009

dyn_step_adj

Chapter 6: CM database parameters

dyn_step_adj

Description
The dyn_step_adj parameter enables or disables the uplink and downlink dynamic step adjustment algorithm for the step size. When enabled, the calculation of step size can include or exclude dynamic power reduction caused by the level being above the upper level threshold. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes None

Syntax
Change command strings
add_cell <gsm_cell_id> <location> chg_element dyn_step_adj <value> <location> <cell_desc> chg_cell_element dyn_step_adj <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full] disp_element dyn_step_adj <location> <cell_desc>

Values
Value type Valid range Integer 0 to 2 0 1 2 Default value 0 Disabled Enabled (excludes power reduction) Enabled (includes power reduction)

6-246

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

dyn_step_adj_fmpr

Description
The dyn_step_adj_fmpr parameter specifies the percentage power reduction used in the dynamic power reduction calculation. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes None

Syntax
Change command strings
add_cell <gsm_cell_id> <location> chg_element dyn_step_adj_fmpr <value> <location> <cell_desc> chg_cell_element dyn_step_adj_fmpr <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full] disp_element dyn_step_adj_fmpr <location> <cell_desc>

Values
Value type Valid range Default value Integer 0 to 10 10

68P02901W23-S

6-247 Nov 2009

dynet_tchs_reserved

Chapter 6: CM database parameters

dynet_tchs_reserved

Description
The dynet_tchs_reserved parameter specifies the amount of terrestrial backing resources reserved for a changing cell when dynamic allocation is enabled for the site containing the cell. The system rejects this parameter if the new value causes the total terrestrial backing resources for a BTS network to be less than the total reserved cell capacity. The total terrestrial backing resources for a BTS network is the sum of the terrestrial backing resources reserved on the DYNETs for the BTS network. The total reserved cell capacity for a site is the sum of the reserved capacity for all of the cells at the site minus the dedicated resources for the site. If this total is less than zero, it is set at zero. The total reserved cell capacity for a BTS networks is then the sum of the total reserved cell capacity of the dynamic allocation BTSs in the BTS network. A (no operator actions) Yes Yes This parameter is not available unless the containing site is configured to support dynamic allocation. The parameter is invalid for the BSC (location 0). The system rejects the command if the cell_desc equals all. The Dynamic Allocation feature must be in operation.

Type Supported by OMC-R GUI Cell description required Dependencies

Syntax
Change command string
chg_element dynet_tchs_reserved <value> <location> <cell_desc>

Display command string

disp_element dynet_tchs_reserved <location> <cell_desc>

6-248

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Values

Values
Value type Valid range Default value Integer (representing the number of reserved TCHs) 0 to 32 0

68P02901W23-S

6-249 Nov 2009

early_classmark_sending

Chapter 6: CM database parameters

early_classmark_sending

Description
The early_classmark_sending parameter specifies the following: Whether the BSS suppresses the early sending of the Classmark Update message to the MSC. Whether an MS is allowed to send an early Classmark Change message.

If this parameter is changed to 0 or 1, and inter_rat_enabled is equal to 4, 5, 6 or 7 for any cell in that BSS, the BSS issues the following warning: Warning: 2G/3G. Type Supported by OMC-R GUI Cell description required Dependencies early_classmark_sending must be enabled on Air Interface for Enhanced A (no operator actions) Yes No The Multiband Inter-cell Handover feature must be enabled. If the Location Services feature is enabled and the operator attempts to change the early_classmark_sending element to a value which does not support early classmark sending on both the A-interface and the Air-interface, the command is rejected. This dependency is also checked during database verification (see lcs_mode section). This parameter can only be changed at the BSC, but it can be viewed at any site within a specified BSS.

Syntax
Change command string
chg_element early_classmark_sending <value> 0

Display command string

disp_element early_classmark_sending 0

6-250

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Values

Values
Value type Valid range Integer 0 to 3 0 1 2 3 Default value 0 Disabled across both the A-interface and the Air-interface. Enabled on A-interface, disabled on Air-interface. Disabled on A-interface, enabled on Air-interface. Enabled across both the A-interface and the Air-interface.

When early_classmark_sending is set to 2, the BSS does not forward classmark update messages to the MSC. This means that the MSC does not obtain any information about the MS capabilities. However, the MSC can still make solicited requests for classmark updates by sending a Classmark Request message to the BSS. If this is not done, the frequency capabilities of the MS are based on the target cell frequency when multiband handovers are being performed. Therefore, after an external handover, the BSS reports the neighbors to the MS as follows: Hand over from GSM900 to GSM900 - only the GSM900 neighbors Hand over from GSM900 to GSM1800 - only the GSM1800 neighbors Hand over from GSM1800 to GSM900 - only the GSM900 neighbors Hand over from GSM1800 to GSM1800 - only the GSM1800 neighbors. External multiband capabilities are limited, and subsequent handovers to GSM1800 cells are therefore not possible.

References
GSM specification TS GSM 04.08, section 10.5.2.34 This is a Motorola defined parameter.

68P02901W23-S

6-251 Nov 2009

eas_alarm

Chapter 6: CM database parameters

eas_alarm

Description
The eas_alarm parameter is the text component of the EAS (External Alarm System) alarm table. The EAS alarm table consists of 34 indexed pairs consisting of a text component and a severity level. The text component and severity level are assigned when the EAS alarm table is initialized using the chg_eas_alarm command. The text component of an indexed pair may only be changed using the chg_eas_alarm command. The index number uniquely identifies each text and severity pair in the EAS alarm table. Index numbers are required to specify which of the 34 pairs to display. Index values are 0 to 33. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No 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 Valid range Default value Text Up to 24 alphanumeric characters (including spaces). None

6-252

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

eas_alarm_type

Description
The eas_alarm_type parameter specifies one of the EAS (External Alarm System) alarm table elements to one of eight optocouplers of an addressed PIX card. The eas_alarm_type value corresponds to the index number identifying the location of a text and severity level pair. Index numbers are required to specify which of the 34 pairs to display. Index values are 0 to 33. The disp_element command displays the optocouplers and indexed alarm text and severity pairs assigned with the map_eas_opto command. The output of the disp_element command appears in the form: eas_alarm_type = x y x y x y x y x y where each x corresponds to an opto # and each y corresponds to an alarm text and severity pair. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) No No None

Syntax
Add/Change command strings
equip <location> eas map_eas_opto <location> <device_id> [<opt_#1> <alarm_table_index>] ...[<opt_#8><alarm_table_index>]

Display command string

disp_element eas_alarm_type,<index> <location>

68P02901W23-S

6-253 Nov 2009

Values

Chapter 6: CM database parameters

Values
Value type Valid range Default value Integer 0 to 33 None

6-254

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

eas_report_opto

Description
The eas_report_opto parameter specifies whether each of the eight optocouplers (optos) on a specific PIX card reports state changes. Index numbers are required. Index numbers are used to identify the desired EAS device. Index values are assigned during installation. The output of the disp_element command appears in the form: eas_report_opto = 1 = ON 2 = ON 3 = OFF 4 = ON 5 = OFF 6 = ON 7 = ON 8 = ON where 1, 2, 4, 6, 7, and 8 report state changes but 3 and 5 do not. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) No No None

Syntax
Change command string
chg_eas_report <location> <device_id> [ on = [<opto_#1>]...[<opto_#n>] ] [ off = [opto_#1>]...[<opto_#n>] ]

Display command string

disp_element eas_report_opto,<index> <location>

Values
Value type Valid range Boolean 0 or 1 0 1 Default value None Disabled Enabled

68P02901W23-S

6-255 Nov 2009

eas_severity

Chapter 6: CM database parameters

eas_severity

Description
The eas_severity parameter specifies the severity level component of the EAS (External Alarm System) alarm table. The index number uniquely identifies each text and severity pair in the EAS alarm table. The EAS alarm table consists of 34 indexed pairs consisting of a text component and a severity level. The text component and severity level are assigned when the EAS alarm table is initialized using the chg_eas_alarm command. The severity component may be changed using either the chg_element or the chg_eas_alarm command. If the chg_eas_alarm command is used, it permits the alarm text to be changed at the same time. Clear is a valid alarm condition, but it is not a valid alarm severity setting. All alarms of severity levels 0 to 4 can receive a clear indication for the original pegging of an alarm when a system is running. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No None

Syntax
Change command strings
chg_eas_alarm <alarm_table_index> <alarm_severity_level> <new_alarm_string> chg_element eas_severity,<index> <value> <location>

Display command string

disp_element eas_severity,<index> <location>

6-256

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Values

Values
Value type Valid range Integer 0 to 4 0 1 2 3 4 Default value None Investigate Critical Major Minor Warning

68P02901W23-S

6-257 Nov 2009

efr_enabled

Chapter 6: CM database parameters

efr_enabled

Description
The efr_enabled parameter enables or disables the Enhanced Full Rate (EFR). Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No The EFR feature must be unrestricted. This parameter cannot be enabled if the handover_required_sp_ver_used parameter is disabled. This parameter is only valid at a BSC location.

Syntax
Change command string
chg_element efr_enabled <value> 0

Display command string

Syntax
Change command strings
chg_element egsm_bcch_sd <value> <location> <cell_desc> chg_cell_element egsm_bcch_sd <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full] disp_element egsm_bcch_sd <location> <cell_desc>

6-264

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Values

Values
Value type Valid range Boolean 0 or 1 0 1 Default value 0 Disabled Enabled

68P02901W23-S

6-265 Nov 2009

egsm_handover_threshold

Chapter 6: CM database parameters

egsm_handover_threshold

Description
The egsm_handover_threshold parameter specifies the range of interference bands allowed for handing over an extended GSM MS using a primary resource which is needed by a primary MS. Allowed interference bands are those above or meeting a specified threshold, which are considered best quality resources. Forced handovers may be disallowed by disabling the egsm_handover_threshold parameter. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes This parameter may only be changed on EGSM systems.

Syntax
Change command strings
chg_element egsm_handover_threshold <value> <location> <cell_desc> chg_cell_element egsm_handover_threshold <value> <cell_desc_opt>

Display command string

disp_element egsm_handover_threshold <location> <cell_desc>

6-266

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Values

Values
Value type Valid range Integer 0 to 5 0 1 2 Forced handovers are not allowed. Forced handovers to interference band 1 extended resource are allowed. Forced handovers to interference bands 1 to 2 extended resource are allowed. Forced handovers to interference bands 1 to 3 extended resource are allowed. Forced handovers to interference bands 1 to 4 extended resource are allowed. Forced handovers to interference bands 1 to 5 extended resource are allowed.

3 4 5 Default value 0

68P02901W23-S

6-267 Nov 2009

emergency_class_switch

Chapter 6: CM database parameters

emergency_class_switch

Description
The emergency_class_switch parameter enables or disables emergency calls by access class. When disabled, all emergency calls are allowed. When enabled, only emergency calls from classes 11 to 15 are allowed. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes cell_bar_access_class

Syntax
Add/Change command strings
add_cell <gsm_cell_id> <location> chg_element emergency_class_switch <value> <location> <cell_desc> chg_cell_element emergency_class_switch <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full] disp_element emergency_class_switch <location> <cell_desc>

Values
Value type Valid range Boolean 0 or 1 0 1 Default value 0 Disabled Enabled

6-268

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

References

References
GSM parameter GSM specifications EC 4.08 - 3.3.1: radio resource connection establishment initiated by the MS 4.08 - 5.2.1.2: emergency call establishment 4.08 - 10.5.2.17, and table 10.30 12.20 - 5.2.8.7 - Cell Description - Emergency Call Not Allowed 2.11 - 4: access class definitions

68P02901W23-S

6-269 Nov 2009

emergency_group_priority

Chapter 6: CM database parameters

emergency_group_priority

Description
The emergency_group_priority attribute defines a priority level threshold for calls. Any call with priority level value less than or equal to the value of emergency_group_priority is exempted from certain BSS congestion mechanisms when the eMLPP feature is unrestricted. The highest priority level value is 1. Less than means numerically lower, that is, 2 is less than 3 but is a higher priority. Thus, for example, when emergency_group_priority is set to 3, calls with priority levels 1 to 3 are exempt from the congestion mechanisms. Setting emergency_group_priority to a value of 0 disables this functionality. The exempted BSS congestion mechanisms are: FR to HR congestion handovers. Standard congestion handovers. Multi-band congestion handovers. Multi-band congestion handovers on assignment. Direct assignment to inner zone in dual band cells. A (no operator actions) Yes Yes The eMLPP feature must be unrestricted

Type Supported by OMC-R GUI Cell description required Dependencies

Syntax
Add/Change command strings
chg_element emergency_group_priority <value> <location>

Display command strings

disp_element emergency_group_priority <location>

6-270

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Values

Values
Value type Valid range Integer 0 to 14 0 14 Default value 0 No calls are exempted from congestion mechanisms. All calls are considered in the congestion mechanisms.

68P02901W23-S

6-271 Nov 2009

en_incom_ho

Chapter 6: CM database parameters

en_incom_ho

Description
The en_incom_ho parameter enables or disables incoming handovers based on whether the cell is barred. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes None

Syntax
Add/Change command strings
add_cell <gsm_cell_id> <location> chg_element en_incom_ho <value> <location> <cell_desc> chg_cell_element en_incom_ho <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full] disp_element en_incom_ho <location> <cell_desc>

Values
Value type Valid range Boolean 0 or 1 0 1 Default value 0 Disabled Enabled

6-272

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

References

References
GSM specification GSM TS 03.22 section 3.5.1 This is a Motorola defined parameter.

68P02901W23-S

6-273 Nov 2009

enhanced_relief

Chapter 6: CM database parameters

enhanced_relief

Description
The enhanced_relief parameter enables or disables the Intelligent Congestion Relief feature. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes 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 Valid range Boolean 0 or 1 0 1 Default value 0 Disabled Enabled

6-274

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

eop_enabled

Description
The eop_enabled parameter enables or disables the Enhanced One Phase Access feature. The system issues the following warning if eop_enabled is changed outside Sysgen when the QoS feature is unrestricted and bssgp_pfc_bit equals 1: WARNING: Changes to this element are overridden while QoS is enabled. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No To enable Enhanced One Phase Access, this feature must be unrestricted. When QoS feature is enabled, this parameter is set to 0 (disabled) for a PCU.

NOTE
If QoS is enabled, the PCU overrides the database value of eop_enabled with an internal value of 0; that is, EOP functionality is disabled for that PCU.

Syntax
Change command string
chg_element eop_enabled <value> <location>

Display command string

disp_element eop_enabled <location>

68P02901W23-S

6-275 Nov 2009

Values

Chapter 6: CM database parameters

Values
Value type Valid range Boolean 0 or 1 0 1 Default value 0 EOP disabled EOP enabled

6-276

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

ercgprsOpt

{23311A}

Description
The ercgprsOpt parameter indicates whether the Extended Range Cell support for the data feature functionality is unrestricted in the BSS software. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes If the ercgprsOpt flag indicates that the extended range for the data feature is restricted, attempts to change the Extended Range Cell for data specific database parameters is rejected. Only if both the GPRS feature (gprsOpt) and ERC feature (ercOpt) are unrestricted, can Extended Range Cell for the data feature be unrestricted. If this parameter indicates that Extended Range Cell for the data feature is unrestricted, and if either the GPRS optional features (gprsOpt) or ERC optional features (ercOpt) are restricted, then the options object for the Extended Range Cell for Data feature cannot be created. The tool used to create the options object for the BSS handles this dependency.

Values
Value type Valid range Boolean 0 or 1 0 1 Default value N/A Restricted Unrestricted

68P02901W23-S

6-277 Nov 2009

erc_ta_priority

Chapter 6: CM database parameters

erc_ta_priority

Description
The erc_ta_priority parameter specifies the priority threshold for extended range cell neighbor. If the absolute timing advance is greater than the priority threshold, the ERC neighbors are placed at the top of the list of sorted handover candidates. Otherwise, the ERC neighbors are appended to the end of the list of candidates. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes 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 Valid range Default value Integer 0 to 63 50

6-278

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

eth_rx_errors_threshold

{26740}

Description
The eth_rx_errors_threshold parameter specifies the maximum allowable percentage of Ethernet frames received in error of all frames received. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No None

Syntax
Change command string
chg_element eth_rx_errors_threshold <value> <location>

Display command string

disp_element eth_rx_errors_threshold <location>

Values
Value type Valid range Default value Integer 0 to 100 10

68P02901W23-S

6-279 Nov 2009

eth_tx_errors_threshold

Chapter 6: CM database parameters

eth_tx_errors_threshold

{26740}

Description
The eth_tx_errors_threshold parameter specifies the maximum allowable percentage of Ethernet transmit errors of all frames transmitted. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No None

Syntax
Change command string
chg_element eth_tx_errors_threshold <value> <location>

Display command string

disp_element eth_tx_errors_threshold <location>

Values
Value type Valid range Default value Integer 0 to 100 10

6-280

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

ext_range_cell

Description
The ext_range_cell parameter enables or disables the Extended Range Cell feature at a Cell. Type Supported by OMC-R GUI Cell description required Dependencies B (Operator actions required) Yes Yes The ext_range_cell parameter cannot be changed if the Extended Range Cells feature is restricted. This parameter cannot be set to a non-zero value when pccch_enabled is 1. The number of extended range timeslots on the BCCH RTF must support the BCCH, CCCH, and SDCCH channels as these channels are always extended. ms_max_range must be less than or equal to 63 for a normal range cell. If ext_range_cell is enabled, the maximum value of ms_max_range increases to 219. max_number_sdcchs must be less than or equal to 20 when Extended Range is enabled. Baseband hopping systems can only be configured among timeslots of the same type, such as extended or normal. This parameter is not available at M-Cellcity, Horizonmicro or Horizoncompact sites. If frequency hopping systems is enabled in an Extended Range Cell, all frequency hopping indicators for the timeslots in the BCCH carrier should be set to 255 (in hexadecimal, 0xff). Lock the associated DRIs to change this parameter.

Operator actions

Syntax
Change command string
chg_cell_element ext_range_cell <value> <cell_desc_opt> The system displays the following prompt: Enter handover threshold mobile max range:

Display command string

disp_element ext_range_cell <location> <cell_desc>

68P02901W23-S

6-281 Nov 2009

Values

Chapter 6: CM database parameters

Values
Value type Valid range Integer 0 to 2 0 1 2 Default value 0 Extended Range disabled for the cell. Extended Range is enabled as a boundary cell. Extended Range is enabled as an isolated cell (rural area).

6-282

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

ext_ul_dur

{26881}

Description
The new per BSS element ext_ul_dur (Extended Uplink Duration) is the maximum duration in block periods for which the uplink TBF operates in an extended mode without getting any new real RLC data block. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No Modification of ext_ul_dur is allowed only when the Extended Uplink feature is unrestricted.

Syntax
Change command string
chg_element ext_ul_dur <value> <location>

Display command string

disp_element ext_ul_dur <location>

Values
Value type Valid range Integer 0 or 24 - 250 0 24 - 250 Default value 0 Extended uplink feature is disabled. Extended uplink feature is enabled.

NOTE
The values are in block periods (1 bp = 20 millisecond).

68P02901W23-S

6-283 Nov 2009

ext_utbf_nodata

Chapter 6: CM database parameters

ext_utbf_nodata

{26881}

Description
The ext_utbf_nodata parameter indicates to the mobile station during the extended uplink TBF mode whether to send any PACKET UPLINK DUMMY CONTROL BLOCK message, when there is no other RLC/MAC block ready to send for this TBF. This parameter is broadcasted to the MS in (PACKET) SYSTEM INFORMATION message. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes Modification of this element is not allowed when Extended Uplink TBF feature is restricted.

Syntax
Change command string
chg_element ext_utbf_nodata <value> <location> <cell_desc> chg_cell_element ext_utbf_nodata <value> <cell_desc_opt>

Display command string

disp_cell ext_utbf_nodata <cell_id> [full] disp_element ext_utbf_nodata <location> <cell_desc>

Copy command strings

copy_cell <source_cell_id> <dest_gsm_cell_id> <dest_location> <dest_bsic> [cell_name]

6-284

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Values

Values
Value type Valid range Boolean 0 or 1 0 1 Default value 0 The mobile station sends a PACKET UPLINK DUMMY CONTROL BLOCK during extended uplink mode. The mobile station refrains sending a PACKET UPLINK DUMMY CONTROL BLOCK during extended uplink mode.

68P02901W23-S

6-285 Nov 2009

extended_paging_active

Chapter 6: CM database parameters

extended_paging_active

Description
The extended_paging_active parameter enables or disables extended paging. When enabled, the BTS sends pages to an MS in its extended page group when all pages could not be transmitted in the designated page group for the MS. The MS must receive and analyze messages for its paging group and the group two paging blocks later. When disabled, extended page is not allowed. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes None

Syntax
Add/Change command strings
add_cell <gsm_cell_id> <location> chg_element extended_paging_active <value> <location> <cell_desc> chg_cell_element extended_paging_active <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full] disp_element extended_paging_active <location> <cell_desc>

Values
Value type Valid range Boolean 0 or 1 0 1 Default value 0 Disabled Enabled

6-286

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

References

References
GSM specifications 4.08 - 3.3.2.1; 10.5.2.26 5.02 - 3.3.2a, b, c: ccch_conf, bs_cc_chans, bs_ccch_comb 5.02 - 6.5.1 (iii) to (vi): ccch groups, paging groups 5.02 - 6.5.2, 6.5.3: determination of ccch_group, paging_group, paging multiframe, paging block index 5.02 - Figure 8, example of TDMA frame mapping for control channels. This is a Motorola defined parameter.

68P02901W23-S

6-287 Nov 2009

extuplinkOpt

Chapter 6: CM database parameters

extuplinkOpt

{26881}

Description
The extuplinkOpt parameter indicates whether the Extended Uplink TBF feature functionality is unrestricted in the BSS software. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes The extuplinkOpt flag is unrestricted only if GPRS is unrestricted.

NOTE
The extuplinkOpt parameter is a flag, and so is read-only and cannot be modified.

Values
Value type Valid range Boolean 0 or 1 0 1 Default value N/A Restricted Unrestricted

6-288

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

fdd_multirat_reporting

Description
The fdd_multirat_reporting parameter specifies the number of UTRAN Frequency Division Duplex (FDD) cells that is included in the list of strongest cells in the measurement report. The fdd_multirat_reporting parameter is sent to a mobile in the Measurement Information message. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes The Enhanced 2G/3G Handover feature must be unrestricted to modify this parameter.

Syntax
Change command strings
chg_element fdd_multirat_reporting <value> <location> <cell_desc> chg_cell_element fdd_multirat_reporting <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full] disp_element fdd_multirat_reporting <location> <cell_desc>

Values
Value type Valid range Default value Integer 0 to 3 1

68P02901W23-S

6-289 Nov 2009

fdd_gprs_qoffset

Chapter 6: CM database parameters

fdd_gprs_qoffset

Description
The fdd_gprs_qoffset parameter specifies an offset to RLA_P for cell reselection to access technology/mode FDD. The fdd_gprs _qoffset parameter is configurable on a per cell basis. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes The PBCCH/PCCCH feature must be unrestricted. If the local_maintenance flag is disabled the MMI is prevented from changing this item

Syntax
Change command strings
chg_element fdd_gprs_qoffset <value> <location> <cell_desc> chg_cell_element fdd_gprs_qoffset <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full] disp_element fdd_gprs_qoffset <location> <cell_desc>

6-290

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Values

Values
Value type Valid range Integer 0 to 15 0 1 ... 8 ... 15 Default value 8 infinity (always select a cell if acceptable) 28 dB ... 0 dB ... 28 dB (1 step =4 dB)

68P02901W23-S

6-291 Nov 2009

fdd_qmin

Chapter 6: 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 Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes The BSS Inter-RAT feature must be unrestricted.

Syntax
Change command strings
chg_element fdd_qmin <value> <location> <cell_desc> chg_cell_element fdd_qmin <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full] disp_element fdd_qmin <location> <cell_desc>

Values
Value type Valid range Default value Integer 0 to 7 7

6-292

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

fdd_qoffset

Description
The fdd_qoffset parameter is followed by the multi-RAT MS in the cell reselection algorithm that it follows. The fdd_qoffset parameter is configurable on a per cell basis. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes The BSS Inter-RAT feature must be unrestricted.

Syntax
Change command strings
chg_element fdd_qoffset <value> <location> <cell_desc> chg_cell_element fdd_qoffset <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full] disp_element fdd_qoffset <location> <cell_desc>

Values
Value type Valid range Default value Integer 0 to 15 8

68P02901W23-S

6-293 Nov 2009

fdd_rep_quant

Chapter 6: CM database parameters

fdd_rep_quant

Description
The fdd_rep_quant parameter defines the reporting quantity of the UTRAN Frequency Division Duplex (FDD) neighbor in the uplink measurement report. The fdd_rep_quant parameter is sent to a mobile in the Measurement Information message. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes The Enhanced 2G/3G Handover feature must be unrestricted to modify this parameter.

Syntax
Change command strings
chg_element fdd_rep_quant <value> <location> <cell_desc> chg_cell_element fdd_rep_quant <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full] disp_element fdd_rep_quant <location> <cell_desc>

Values
Value type Valid range Boolean 0 or 1 0 1 Default value 1 RSCP (Received Signal Code Power) Ec/No (Ratio of Chip Energy to Power Spectral Density)

6-294

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

fer_meas_period

{29693A}

Description
The fer_meas_period parameter allows the customer to configure the FER measuring period parameter. The value indicates the multiple of 24 speech frames that is used as the measuring period of FER family statistics. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No None

Syntax
Change command strings
chg_element fer_meas_period <value> <location>

Display command strings

disp_element fer_meas_period <location>

Values
Value type Valid range Integer 0 to 255 0 To disable the feature, use 24 speech frames as the measuring period of FER family statistics. Multiple of 24 speech frames used as the measuring period of FER family statistics.

1~255 Default value 0

68P02901W23-S

6-295 Nov 2009

fieldeng_always _enabled

Chapter 6: CM database parameters

fieldeng_always _enabled

{27508}

Description
The fieldeng_always_enabled parameter specifies whether the field engineering accounts can be used when the OML link is up and down or only when the OML link is down. Essentially it indicates if field engineering accounts can be used for login when the OML link is up. This element can be accessed and updated both in and out of sysgen mode. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No None

Syntax
Add/Change command string
chg_element fieldeng_always_enabled <value> 0

Display command string

disp_element fieldeng_always_enabled 0

Values
Value type Valid range Boolean 0 or 1 0 1 Default value 1 fieldengX accounts can be used only when the OML link is down. fieldengX accounts can be used when the OML link is up or down.

6-296

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

force_hr_usage

Description
The force_hr_usage parameter enables or disables the capacity to override MSC provided preference and force Half Rate usage for all Half Rate capable calls within a BSS. This covers both initial setup and handover. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No The AMR feature and/or the GSM Half Rate feature must be unrestricted.

Syntax
Add/Change command string
chg_element force_hr_usage <value> <location>

Display command string

disp_element force_hr_usage <location>

Values
Value type Valid range Boolean 0 or 1 0 1 Default value 0 Disabled Enabled

68P02901W23-S

6-297 Nov 2009

free_run_enabled

Chapter 6: CM database parameters

free_run_enabled

Description
The free_run_enabled parameter enables or disables the hardware configuration Free Run Mode. Type Supported by OMC-R GUI Cell description required Dependencies Operator actions B (operator actions required) Yes No No All the DRI's in this site are affected when the free_run_enabled parameter is enabled. This parameter cannot be displayed and changed on RXCDR site.

Syntax
Add/Change command string
chg_element free_run_enabled <value> <location>

Display command string

disp_element free_run_enabled <location>

Values
Value type Valid range Boolean 0 or 1 0 1 Default value 0 Disabled Enabled

NOTE
Manually reset the DRIs to disable Free Run Mode.

6-298

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

frequency_type

Description
The frequency_type parameter specifies the frequency type of a cell. Type Supported by OMC-R GUI Cell description required Dependencies B (operator actions required) Yes Yes If the Infrastructure Sharing Homogeneous Cabinet feature is not enabled, the frequency_type for every cabinet and cell at a site must be the same. If the Infrastructure Sharing Homogeneous Cabinet feature is enabled, but the Infrastructure Sharing Heterogeneous feature is disabled, the cells at a site must have the same single frequency type as the cabinet they correlate to. However, the cabinets at the site may be of different frequency types. If both the Infrastructure Sharing Homogeneous Cabinet feature and the Infrastructure Sharing Heterogeneous feature are enabled, the cells at a site may have different frequency types and cabinets may support multiple frequency types. However, the cell frequency must be supported by the cabinet the cell is correlated to. If inner_zone_alg is set to indicate Dual Band Cells, the following two dependencies are enforced: (1) if secondary_freq_type is set to EGSM or PGSM, the frequency_type may be set only to DCS1800; (2) if secondary_freq_type is DCS1800, frequency_type may be set only to PGSM or EGSM. Cell and cabinet frequency types must be allowed at the BSS as per the freq_types_allowed command. The frequency_type of a cell may be changed to PCS1900 inside Sysgen mode. If the value of tx_power_cap is set to 0 (indicating a low power cell), and radios have already been associated with the cell, a warning message is issued to the operator. {27236} The cabinet frequency_type database parameter must specify a single band for the 4 branch receive density feature. The BSS rejects an attempt to leave Sysgen mode when the value of the tx_power_cap parameter is 0 for cells residing on a Horizonmacro or Horizonmacro extension cabinet which have a frequency type of PCS1900 and have no radio resources allocated to the cell. Put the system into SYSGEN mode to change the frequency_type parameter.

Operator actions

68P02901W23-S

6-299 Nov 2009

Syntax

Chapter 6: CM database parameters

Syntax
Add/Change command strings
add_cell <gsm_cell_desc> <location The add_cell command accepts either numeric values or text strings for frequency_type. chg_cell_element frequency_type <value> <cell_desc_opt> The chg_cell_element command accepts only numeric values for frequency_type.

Display command strings

disp_cell <cell_id> [full] disp_element frequency_type <location> <cell_desc>

Values
Value type Valid range Integer 1 2 4 8 Default value None Text pgsm egsm dcs1800 pcs1900

NOTE
Horizon II and Horizon II extension cabinets support frequency types 1, 2, 4 and 6.

6-300

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

full_pwr_rfloss

Description
The full_pwr_rfloss parameter enables or disables the ability of the BSS power control to fully power up the MS and BTS at the point where the RF connection appears to be lost. When enabled, the transition to full power occurs when the threshold set by link_about_to_fail is reached in the link_fail procedure. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes None

Syntax
Add/Change command strings
add_cell <gsm_cell_id> chg_element full_pwr_rfloss <value> <location> <cell_desc> chg_cell_element full_pwr_rfloss <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full] disp_element full_pwr_rfloss <location> <cell_desc>

Values
Value type Valid range Boolean 0 or 1 0 1 Default value 0 Disabled Enabled

68P02901W23-S

6-301 Nov 2009

gci_error_clr_thresh

Chapter 6: CM database parameters

gci_error_clr_thresh

Description
The gci_error_clr_thresh parameter specifies the error count threshold (equal to or less than) for an alarm to be cleared for a GPRS Circuit Identifier (GCI). Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No The GPRS and ECERM features must be unrestricted. Two successful GPRS alarm increment time periods must elapse without a sync loss error to clear an alarm within this threshold. (One successful GPRS alarm increment time period may be too short for the Channel Coder Unit (CCU) to send an error indication, thus clearing the alarm prematurely.) This parameter can be set only at a BSC. If the threshold is increased during operation, any existing counts between the new and the old threshold does not clear an alarm until the next successful time period occurs.

Syntax
Change command string
chg_element gci_error_clr_thresh <value> 0

Display command string

disp_element gci_error_clr_thresh 0

Values
Value type Valid range Default value Integer 0 to 253 0

6-302

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

gci_error_gen_thresh

Description
The gci_error_gen_thresh parameter specifies the error count threshold (equal to or greater than) for an alarm to be generated for a GPRS Circuit Identifier (GCI). Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No The GPRS and ECERM features must be unrestricted. This parameter can be set only at a BSC. If the threshold is changed during operation, no immediate alarm occurs. The new threshold takes effect only when the GCI error count changes.

Syntax
Change command string
chg_element gci_error_gen_thresh <value> 0

Display command string

disp_element gci_error_gen_thresh 0

Values
Value type Valid range Default value Integer 2 to 255 6

68P02901W23-S

6-303 Nov 2009

gci_error_inc

Chapter 6: CM database parameters

gci_error_inc

Description
The gci_error_inc parameter specifies the error count increment when the Enhanced Circuit Error Rate Monitor (ECERM) feature is in use for GPRS Circuit Identifiers (GCIs) on a per BSC basis. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No The GPRS and ECERM features must be unrestricted. This parameter can be set only at a BSC.

Syntax
Change command string
chg_element gci_error_inc <value> 0

Display command string

disp_element gci_error_inc 0

Values
Value type Valid range Integer 0 1 to 255 Default value 0 1 GCI alarms not raised. GCI alarms raised. If ECERM feature is restricted. If ECERM feature is not restricted.

6-304

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

gclk_qwarm_flag

Description
The gclk_qwarm_flag parameter specifies the amount of time required by the active GCLK to warm up. It has no effect on the standby GCLK. If this parameter is disabled, the active GCLK requires 30 minutes. If this parameter is enabled and the active GCLK is of version 9 or later, the software overrides the hardware timer on the active GCLK and brings it into services after 15 minutes. This time period begins when the site is initialized. This parameter is only valid for GCLK boards. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No The Fast GCLK Warmup feature must be unrestricted. The GCLK version must be V9 or later.

Syntax
Change command string
chg_element gclk_qwarm_flag <value> <location>

Display command string

disp_element gclk_qwarm_flag <location>

Values
Value type Valid range Boolean 0 or 1 0 1 Default value 0 Disabled Enabled

68P02901W23-S

6-305 Nov 2009

global_reset_repetitions

Chapter 6: CM database parameters

global_reset_repetitions

Description
The global_reset_repetitions parameter allows the Reset message to be sent indefinitely if Reset Ack is not received, or stops sending the Reset message after a fixed number of repetitions. The global reset procedure repeats is only if the MSC fails to acknowledge the BSS. After the fixed number of repetitions, an alarm is generated. If the value is set to 0, the global reset message repeats continuously until a Reset Ack is received. If the value is set to a value greater than 0, the global reset message repeats the number of times entered and the alarm: No MSC Acknowledgment for Global Reset is generated. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No This parameter does not apply to RXCDR sites. This parameter applies to only BSC sites.

Syntax
Change command string
chg_element global_reset_repetitions <value> 0

Display command string

disp_element global_reset_repetitions 0

Values
Value type Valid range Default value Integer (number of repetitions) 0 to 255 0

6-306

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

References

References
GSM specification TS GSM 8.08 This is a Motorola defined parameter.

68P02901W23-S

6-307 Nov 2009

gproc_slots

Chapter 6: CM database parameters

gproc_slots

Description
The gproc_slots parameter specifies the number of timeslots to be allocated to all GPROCs for the TDM highway. It is possible to configure different functions on each of the 32 channels. The system supports 16 or 32 timeslots for assignment to the TDM highway. The BSS supports a value of 24 for this parameter on the BSC. If set to 24, at least one GPROC is equipped after all the MSIs are equipped, so that 12 MSIs and 8 GPROCs can be brought into service. This parameter is not allowed at M-Cell sites. Type Supported by OMC-R GUI Cell description required Dependencies Operator actions B (operator actions required) No No This parameter may not be modified if any BSP , BTP , DHP , GPROC, or MSI is equipped. This parameter may only be modified in initial SYSGEN mode.

Syntax
Change command string
chg_element gproc_slots <value> <location>

Display command string

disp_element gproc_slots <location>

6-308

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Values

Values
Value type Valid range Integer 16, 24 or 32 16 24 32 Default value 16 16 TDM timeslots 24 TDM timeslots (BSC only) 32 TDM timeslots (only valid with GPROC2 and GPROC3 boards)

NOTE
If gproc_slots is greater than 16, the system displays the following warning: COMMAND ACCEPTED: WARNING: Specified value requires GPROC2 or GPROC3 boards.

68P02901W23-S

6-309 Nov 2009

gprs_alarm_time

Chapter 6: CM database parameters

gprs_alarm_time

Description
The gprs_alarm_time parameter identifies the time period in which error counters are either: incremented if an error indication is received for a GPRS Circuit Identifier (GCI), or decremented if no error indication is received. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No The GPRS and ECERM features must be unrestricted. This parameter applies to only BSC sites.

Syntax
Change command string
chg_element gprs_alarm_time <value> 0

Display command string

disp_element gprs_alarm_time 0

Values
Value type Valid ranges Integer 0 5 to 240 Default values 0 60 If GPRS or ECERM is restricted (effectively equivalent to gprs_alarm_time parameter turned off). If GPRS and ECERM features are unrestricted. If GPRS or ECERM are restricted. If GPRS and ECERM features are unrestricted.

6-310

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

gprs_bs_cv_max

Description
The gprs_bs_cv_max specifies the maximum count down value a mobile can use for uplink RLC data transfer. The MS sends a count down value in each uplink RLC data block starting gprs_bs_cv_max blocks from the last block. The value sent is decremented by one in each subsequent block. This allows the network to identify the last RLC block in the uplink TBF. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes The GPRS feature must be unrestricted.

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

Syntax
Change command strings
chg_element gprs_bs_cv_max <value> <location> <cell_desc> chg_cell_element gprs_bs_cv_max <value> <cell_desc_opt>

Display command string

disp_element gprs_bs_cv_max <location> <cell_desc>

Values
Value type Valid range Default value Integer (blocks) 0 to 15 {26881} 8

68P02901W23-S

6-311 Nov 2009

gprs_cell_reselect_hysteresis

Chapter 6: CM database parameters

gprs_cell_reselect_hysteresis

Description
The gprs_cell_reselect_hysteresis parameter specifies the additional hysteresis level that applies in the ready state for cells in the same Routing Area (RA). Differences in received signal levels from 0 dB to 14 dB (in 2 dB increments) are used for cell reselection. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes The PBCCH/PCCCH optional feature must be unrestricted.

Syntax
Add/Change command strings
chg_element gprs_cell_reselect_hysteresis <value> <location> <cell_desc> chg_cell_element gprs_cell_reselect_hysteresis <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> full disp_element gprs_cell_reselect_hysteresis <location> <cell_desc>

6-312

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Values

Values
Value type Valid range Integer 0 to 7 0 1 2 3 4 5 6 7 Default value 0 Represents the signal level differences: 0 dB 2 dB 4 dB 6 dB 8 dB 10 dB 12 dB 14 dB (0 dB)

68P02901W23-S

6-313 Nov 2009

gprs_com_ms_class

Chapter 6: CM database parameters

gprs_com_ms_class

Description
The gprs_com_ms_class parameter specifies the Most Common Multislot Class of GPRS mobiles. The four possible values represent the following: 1 - multislot class 1. 2 - multislot class 2, 3, 5. 4 - multislot class 4, 6, 7. 8 - multislot class 8 to 29. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No The GPRS feature must be unrestricted.

Syntax
Change command strings
chg_element gprs_com_ms_class <value> <location>

Display command strings

disp_element gprs_com_ms_class <location>

Values
Value type Valid range Default value Integer 1, 2, 4 and 8 8

6-314

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

gprs_cr_margin

Description
The gprs_cr_margin parameter specifies the threshold at which a Packet Measurement Report (PMR) received from the MS is considered as bad by the network. A bad PMR is one in which the difference between the serving cells rxlev and the serving cells value of rxlev_access_min is less than the gprs_cr_margin. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes The Network Controlled Cell Reselection (NCCR) feature must be unrestricted. The parameter can be changed in or out of SYSGEN mode. Settings are copied by the copy_cell command.

NOTE
PCU software processes using this parameter are notified immediately after the change is made.

Syntax
Change command string
chg_element gprs_cr_margin <value> <location> <cell_desc> chg_cell_element gprs_cr_margin <value> <cell_desc_opt>

Display command string

disp_element gprs_cr_margin <location> [<cell_id>] disp_cell <cell_id> full

68P02901W23-S

6-315 Nov 2009

Values

Chapter 6: CM database parameters

Values
Value type Valid ranges Default values Integer 5 to 40 30 dB dB

References
GSM parameter None This is a Motorola defined parameter.

6-316

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

gprs_dl_pwr_mode

Description
The gprs_dl_pwr_mode parameter specifies the downlink power control mode that the PCUs use to broadcast data blocks to the MS. It is a per BSC parameter. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No The GPRS feature must be unrestricted. This parameter can be set to a value of 1 (mode A). This parameter cannot be set to 2 (mode B) when gprs_mac_mode is set to 1 (dynamic mode).

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

Syntax
Change command strings
chg_element gprs_dl_pwr_mode <value> bsc

Display command string

disp_element gprs_dl_pwr_mode bsc

68P02901W23-S

6-317 Nov 2009

Values

Chapter 6: CM database parameters

Values
Value type Valid range Integer 0 to 2 0 1 2 Default value 1 No power mode Mode A Mode B

6-318

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

gprs_drx_timer_max

Description
The gprs_drx_timer_max parameter specifies the maximum timer value allowed for the MS to request for non-DRX mode after packet transfer mode. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes The GPRS feature must be unrestricted.

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

Syntax
Change command strings
chg_element gprs_drx_timer_max <value> <location> <cell_desc> chg_cell_element gprs_drx_timer_max <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> full disp_element gprs_drx_timer_max <location> <cell_desc>

Values
Value type Valid range Default value Integer (seconds) 0 to 3 0

68P02901W23-S

6-319 Nov 2009

gprs_enabled

Chapter 6: CM database parameters

gprs_enabled

Description
The gprs_enabled parameter specifies whether GPRS is unrestricted at a cell. The gprs_supported broadcast parameter describes the GPRS configuration of a cell. The BSS implements this as two cell elements: gprs_enabled and pcch_alloc. Type Supported by OMC-R GUI Cell description required Dependencies B (operator actions required) Yes Yes The GPRS feature must be unrestricted. At least one PCU must be equipped. A prompt requests the primary PCU ID. max_gprs_pdch must be set to a non-zero-value. At least one nsvc must be associated with a GBL. The nsei parameter must be configured by the operator. A PSP and the default GSL must be equipped at the PCU/s. A routing area color must have been configured for the cell; see the ra_color parameter in ra_color on page 6-707 description. The RAC parameter must be set. If pccch_enabled is set to 1 (enabled) and the operator attempts to set gprs_enabled to 1, the command is rejected if there is no reserved Packet Data Channel (PDCH) timeslot in the same cell. There must be at least one. Before this parameter can be set, the operator must have set gprs_sig_bvci parameter (see gprs_sig_bvci on page 6-351) using the chg_element command.

Operator actions

NOTE
BSS software processes using this parameter are immediately notified when the change is made. When an attempt is made to change gprs_enabled, and the requested PDTCHs exceed the GDS or PMC capacity on the PCU, the BSS accepts the request and issues a warning to indicate that there is not enough GDS or PMC resource available.

6-320

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Syntax

Syntax
Change command string
chg_cell_element gprs_enabled <value> <cell-desc_opt> chg_cell_element <location> gprs_enabled <value> all

Display command string

disp_element gprs_enabled <location> <cell-desc> disp_element gprs_enabled <location> all

Values
Value type Valid range Boolean 0 or 1 0 1 Default value 0 Disabled Enabled

68P02901W23-S

6-321 Nov 2009

gprs_intraho_allwd

Chapter 6: CM database parameters

gprs_intraho_allwd

Description
The gprs_intraho_allwd parameter specifies whether the BSS performs intra-cell handovers to free GPRS timeslots currently in use for circuit traffic. Such handovers recover PDTCHs which have been switched to TCHs. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes The GPRS feature must be unrestricted. An intra-cell handover is performed only if the number of idle TCHs (including circuit switch and switchable TCHs) is greater than the value set for the gprs_reconfig_thresh_idle_tch parameter.

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

Syntax
Change command strings
chg_element gprs_intraho_allwd <value> <location> <cell_desc> chg_cell_element gprs_intraho_allwd <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> <full> disp_element gprs_intraho_allwd <location> <cell_desc>

6-322

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Values

Values
Value type Valid range Boolean 0 or 1 0 1 Default value 1 Disabled Enabled

68P02901W23-S

6-323 Nov 2009

gprs_mac_mode

Chapter 6: CM database parameters

gprs_mac_mode

Description
The gprs_mac_mode parameter specifies the medium access mode to be used by the PCUs. Only the dynamic access mode is available. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No The GPRS feature must be unrestricted.

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

Syntax
Change command strings
chg_element gprs_mac_mode <value> bsc

Display command string

disp_element gprs_mac_mode bsc

Values
Value type Valid range Boolean 1 2 Default 1 Dynamic mode Extended dynamic allocation

6-324

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

gprs_min_prr_blks

Description
The gprs_min_prr_blks parameter specifies the minimum number of dynamic PRR blocks created per cell and measured over four multiframes. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes Modification of gprs_min_prr_blks has no effect for cells that have the pccch_enabled parameter enabled. GPRS must be unrestricted.

Syntax
Change command strings
chg_element gprs_min_prr_blks <value> <location> <cell_desc> chg_cell_element gprs_min_prr_blks <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> full disp_element gprs_min_prr_blks <location> <cell_desc>

Values
Value type Valid range Default value Integer 0 to 24 0

68P02901W23-S

6-325 Nov 2009

gprs_ms_pan_dec

Chapter 6: CM database parameters

gprs_ms_pan_dec

Description
The gprs_ms_pan_dec parameter specifies the amount by which to decrement the MS counter n3102. The MS counter n3102 counts the number of uplink acks/nacks received by the MS. When an uplink ack/nack is received, n3102 is incremented by gprs_ms_pan_inc. n3102 never exceeds gprs_ms_pan_max. Each time the preset internal timer T3182 expires, n3102 is decremented by gprs_ms_pan_dec. T3182 defines how long the mobile waits for an uplink ack/nack. If n3102 decrements to zero, then the MS performs an abnormal cell reselection procedure as defined in the GSM standard referred to in this description. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes The GPRS feature must be unrestricted.

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

Syntax
Change command strings
chg_element gprs_ms_pan_dec <value> <location> <cell_desc> chg_cell_element gprs_ms_pan_dec <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> full disp_element gprs_ms_pan_dec <location> <cell_desc>

6-326

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Values

Values
Value type Valid range Default value Integer 0 to 7 1

References
GSM parameter GSM technical specification None This is a Motorola defined parameter. 04.60

68P02901W23-S

6-327 Nov 2009

gprs_ms_pan_inc

Chapter 6: CM database parameters

gprs_ms_pan_inc

Description
The gprs_ms_pan_inc parameter specifies the amount by which to increment the MS counter n3102. The MS counter n3102 counts the number of uplink acks/nacks received by the MS. When an uplink ack/nack is received, n3102 is incremented by gprs_ms_pan_inc. n3102 never exceeds gprs_ms_pan_max. Each time the preset internal timer T3182 expires, n3102 is decremented by gprs_ms_pan_dec. T3182 defines how long the mobile waits for an uplink ack/nack. If n3102 decrements to zero, then the MS performs an abnormal cell reselection procedure as defined in the GSM standard referred to in this description. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes The GPRS feature must be unrestricted.

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

Syntax
Change command strings
chg_element gprs_ms_pan_inc <value> <location> <cell_desc> chg_cell_element gprs_ms_pan_inc <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> full disp_element gprs_ms_pan_inc <location> <cell_desc>

6-328

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Values

Values
Value type Valid range Default value Integer 0 to 7 1

References
GSM parameter GSM specification None This is a Motorola defined parameter. 04.60

68P02901W23-S

6-329 Nov 2009

gprs_ms_pan_max

Chapter 6: CM database parameters

gprs_ms_pan_max

Description
The gprs_ms_pan_max parameter specifies the maximum value of the MS counter n3102. The MS counter n3102 counts the number of uplink acks/nacks received by the MS. When an uplink ack/nack is received, n3102 is incremented by gprs_ms_pan_inc. n3102 never exceeds gprs_ms_pan_max. Each time the preset internal timer T3182 expires, n3102 is decremented by gprs_ms_pan_dec. T3182 defines how long the mobile waits for an uplink ack/nack. If n3102 decrements to zero, then the MS performs an abnormal cell reselection procedure as defined in the GSM standard referred to in this description. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes The GPRS feature must be unrestricted.

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

Syntax
Change command strings
chg_element gprs_ms_pan_max <value> <location> <cell_desc> chg_cell_element gprs_ms_pan_max <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> full disp_element gprs_ms_pan_max <location> <cell_desc>

6-330

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Values

Values
Value type Valid range Default value Integer 0 to 7 3

References
GSM parameter GSM technical specification None This is a Motorola defined parameter. 04.60

68P02901W23-S

6-331 Nov 2009

gprs_ms_txpwr_max_cch

Chapter 6: CM database parameters

gprs_ms_txpwr_max_cch

Description
The gprs_ms_txpwr_max_cch parameter specifies the maximum random access power available for an MS on a packet control channel (pccch or pbcch) in a cell. This parameter is expressed as a power level value. Before accessing a cell on the PRACH and before receiving the first power command during a communication on a BCCH (or TCH), the MS uses one of two possible power levels. The MS uses the lower power level of the two available: either the gprs_ms_txpwr_max_cch broadcast on the BCCH or the maximum transmit power as defined by the power class of the MS. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes The cell frequency_type. The PBCCH/PCCCH optional feature must be unrestricted.

Syntax
Add/Change command strings
chg_element gprs_ms_txpwr_max_cch <value> <location> <cell_desc> chg_cell_element gprs_ms_txpwr_max_cch <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> full disp_element gprs_ms_txpwr_max_cch <location> <cell_desc>

6-332

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Values

Values
Value type Valid range Integer 0 to 31 2 to 28 0 to 15, 30 and 31 Default value 2 0 30 For PGSM, EGSM and GSM850 cells in 2 dBm steps as shown in Table 6-11: For DCS1800 cells in 2 dBm steps as shown in Table 6-12: For PCS1900 cells as shown in Table 6-13: (For PGSM, EGSM and GSM850 cells). (For DCS1800 cells). (For PCS1900 cells).

Table 6-11
Value 0 to 2 3 4 5 6 7 8 9 10

Maximum mobile power level for PGSM, EGSM and GSM850 cells
Power level 39 dBm 37 dBm 35 dBm 33 dBm 31 dBm 29 dBm 27 dBm 25 dBm 23 dBm Value 11 12 13 14 15 16 17 18 19 to 31 Power level 21 dBm 19 dBm 17 dBm 15 dBm 13 dBm 11 dBm 9 dBm 7 dBm 5 dBm

Table 6-12
Value 0 1 2 3 4 5 6 7

Maximum mobile power level for DCS1800 cells

Power level 30 dBm 28 dBm 26 dBm 24 dBm 22 dBm 20 dBm 18 dBm 16 dBm Value 8 9 10 11 12 13 14 15 to 28 Power level 14 dBm 12 dBm 10 dBm 8 dBm 6 dBm 4 dBm 2 dBm 0 dBm

68P02901W23-S

6-333 Nov 2009

Values

Chapter 6: CM database parameters

Table 6-13
Value 30 31 0 1 2 3 4 5 6

Maximum mobile power level for PCS1900 cells

Power level 33 dBm 32 dBm 30 dBm 28 dBm 26 dBm 24 dBm 22 dBm 20 dBm 18 dBm Value 7 8 9 10 11 12 13 14 15 Power level 16 dBm 14 dBm 12 dBm 10 dBm 8 dBm 6 dBm 4 dBm 2 dBm 0 dBm

6-334

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

gprs_network_operation_mode

Description
The gprs_network_operation_mode parameter specifies whether a GPRS is present between the MSC and the SGSN. It is a per BSC parameter. Table 6-14 shows the two permissible modes.

Table 6-14
Mode 1

Modes for gprs_network_operation_mode

Description The network sends a CS paging message for a GPRS attached mobile on the GPRS paging channel, which is the PCH or the PPCH depending on whether there is a PCCCH in the cell, or on a GPRS PDTCH. This means that the MS need only monitor one paging channel and that it receives CS pages on a PDTCH when it is in transfer mode. The network sends CS pages for a GPRS attached MS on the CCCH and PS pages of the PCCCH, if allocated. This means that a MS must monitor both the CCH for CS pages and PCCH for PS pages. No paging coordination is done by the network.

NOTE
The gprs_network_operation_mode can be set to either 1 or 3. When set to 3, the actual value of corresponding SYS13 (PSYS13) field depends on PCCCH being enabled or not. If not, the system broadcasts Network Mode Operation 2.

Type Supported by OMC-R GUI Cell description required Dependencies

A (no operator actions) Yes No The GPRS feature must be unrestricted.

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

68P02901W23-S

6-335 Nov 2009

Syntax

Chapter 6: CM database parameters

Syntax
Change command string
chg_element gprs_ network_operation_mode <value> bsc

Display command string

disp_element gprs_network_operation_mode bsc

Values
Value type Valid range Integer 1 or 3 1 3 Default value 3 Mode 1 Mode 3

6-336

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

gprs_num_pmrs

Description
The gprs_num_pmrs parameter specifies the number of bad Packet Measurement Reports (PMRs) from the MS at which the PCU performs network controlled cell reselection. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes The Network Controlled Cell Reselection (NCCR) feature must be unrestricted. The parameter can be changed in or out of SYSGEN mode. Settings are copied by the copy_cell command.

NOTE
PCU software processes using this parameter are notified immediately after the change is made.

Syntax
Change command string
chg_element gprs_num_pmrs <value> <location> <cell_desc> chg_cell_element gprs_num_pmrs <value> <cell_desc_opt>

Display command string

disp_element gprs_num_pmrs <location> [<cell_id>] disp_cell gprs_num_pmrs <cell_id> full

68P02901W23-S

6-337 Nov 2009

Values

Chapter 6: CM database parameters

Values
Value type Valid ranges Default values Integer 1 to 10 3 Number of bad PMRs.

References
GSM parameter None This is a Motorola defined parameter.

6-338

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

gprs_par_wait_ind

Description
The gprs_par_wait_ind parameter specifies the GPRS Packet Access Reject (PAR) period of a cell, that is, how long the mobile needs to wait before re-RACHing into the cell. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes The GPRS must be unrestricted.

NOTE
PCU software processes using this parameter are notified immediately after the change is made.

Syntax
Change command strings
chg_element gprs_par_wait_ind <value> <location> <cell_desc> chg_cell_element gprs_par_wait_ind <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> full disp_element gprs_par_wait_ind <location> <cell_desc>

Values
Value type Valid range Default value Integer (20ms block period) 100 to 750 150

68P02901W23-S

6-339 Nov 2009

gprs_pb

Chapter 6: CM database parameters

gprs_pb

Description
The gprs_pb parameter specifies the power reduction used by the BTS on the BCCH blocks. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes The GPRS feature must be unrestricted.

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

Syntax
Change command strings
chg_element gprs_pb <value> <location> <cell_desc> chg_cell_element gprs_pb <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> full disp_element gprs_pb <location> <cell_desc>

Values
Value type Valid range Default value Integer 0 to 16 1

6-340

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

gprs_pc_alpha

Description
The gprs_pc_alpha is the system parameter broadcast on the BCCH. It is used as a multiplier of the power offset in power control calculations. The actual multiplying factor is one-tenth of the value set in this parameter; that is, if N is the value of this parameter, the multiplying factor is N/10. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes The GPRS feature must be unrestricted.

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

Syntax
Change command strings
chg_element gprs_pc_alpha <value> <location> <cell_desc> chg_cell_element gprs_pc_alpha <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> full disp_element gprs_pc_alpha <location> <cell_desc>

Values
Value type Valid range Default value Integer (Power offset is multiplied by one tenth of this value) 0 to 10 0

68P02901W23-S

6-341 Nov 2009

gprs_pc_meas_chan

Chapter 6: 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 to control the uplink power. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes The GPRS feature must be unrestricted.

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

Syntax
Change command strings
chg_element gprs_pc_meas_chan <value> <location> <cell_desc> chg_cell_element gprs_pc_meas_chan <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> full disp_element gprs_pc_meas_chan <location> <cell_desc>

Values
Value type Valid range Boolean 0 or 1 0 1 Default value 0 BCCH PDCH

6-342

68P02901W23-S Nov 2009

6-350

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

gprs_sig_bvci

Description
The gprs_sig_bvci parameter specifies the BVCI of the signaling source used with GBLs. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No The GPRS feature must be unrestricted.

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

Syntax
Change command string
chg_element gprs_sig_bvci <value> pcu

Display command string

disp_element gprs_sig_bvci pcu

Values
Value type Valid range Default value Integer 0 to 65535 0

68P02901W23-S

6-351 Nov 2009

gprs_temporary_offset

Chapter 6: CM database parameters

gprs_temporary_offset

Description
The gprs_temporary_offset parameter specifies a value used by the MS as part of its calculation of C32 for the cell reselection process. It is used to apply a negative offset to C32 for the duration of the gprs_penalty_time parameter. C32 is the reselection priority assigned to a cell which can be broadcast on the BCCH of each cell. When more than one cell is available for reselection, the MS reselects the cell with the highest C32 value. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes The PBCCH/PCCCH optional feature must be unrestricted.

Syntax
Add/Change command strings
chg_element gprs_temporary_offset <value> <location> <cell_desc> chg_cell_element gprs_temporary_offset <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> full disp_element gprs_temporary_offset <location> <cell_desc>

6-352

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Values

Values
Value type Valid range Integer 0 to 7 0 1 2 3 4 5 6 7 Default value 0 0 dB 10 dB 20 dB 30 dB 40 dB 50 dB 60 dB Infinity

68P02901W23-S

6-353 Nov 2009

gprs_type5_alg

Chapter 6: CM database parameters

gprs_type5_alg

Description
The gprs_type5_alg parameter indicates whether the GPRS type-5 microcellular algorithm is turned on or not. The following error is displayed and the command rejected if an attempt is made to enable this parameter when nccr_enabled is disabled: ERROR: nccr_enabled must be set to 1 before enabling gprs_type5_alg. COMMAND REJECTED Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No Modification is only allowed when all of the following conditions are satisfied: NACC Optional feature is unrestricted NCCR optional feature is unrestricted Microcellular optional feature is unrestricted

gprs_type5_alg cannot be set to 1 (enabled) when nccr_enabled is 0 (disabled).

NOTE
PCU software processes using this parameter are notified immediately after the change is made.

Syntax
Change command strings
chg_element gprs_type5_alg <value> <location>

6-354

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Values

Display command strings

disp_element gprs_type5_alg <location>

Values
Value type Valid range Boolean 0 to 1 0 1 Default value 0 Disabled Enabled

68P02901W23-S

6-355 Nov 2009

gprs_ts_config_alg

Chapter 6: CM database parameters

gprs_ts_config_alg

Description
The gprs_ts_config_alg parameter specifies the algorithm used to allocate switchable and reserved GPRS timeslots. There are two options: PCU performance algorithm - GPRS resources configured for performance by the PCU. Customer specified algorithm - operator can configure GPRS resources on a per cell basis.

NOTE
BSS software processes using this parameter are notified immediately after the change is made. When an attempt is made to change gprs_ts_config_alg, and the requested PDTCHs exceed the GDS or PMC capacity on the PCU, the BSS accepts the request and issues a warning to indicate that there is not enough GDS or PMC resource available.

Type Supported by OMC-R GUI Cell description required Dependencies

A (no operator actions) Yes Yes The GPRS feature must be unrestricted. Enough timeslots must be available on all of the GPRS cell carriers. This parameter can be changed only when GPRS is either disabled or changed from disabled to enabled.

NOTE
To set this parameter at the OMC-R GUI, GPRS must first be disabled and then enabled. To set this parameter at a TTY terminal, GPRS must first be disabled.

6-356

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Syntax

Syntax
Change command strings
chg_element gprs_ts_config_alg <value> <location> <cell_desc> chg_cell_element gprs_ts_config_alg <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> full disp_element gprs_ts_config_alg <location> <cell_desc>

Values
Value type Valid range Boolean 0 or 1 0 1 Default value 0 PCU performance algorithm Customer specified algorithm

68P02901W23-S

6-357 Nov 2009

gprs_ul_dl_bias

Chapter 6: CM database parameters

gprs_ul_dl_bias

Description
The gprs_ul_dl_bias parameter enables a second uplink to be allocated to mobiles initially with multislot class 6 or 10 and any multislot class that maps to class 6 or 10. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No GPRS must be unrestricted.

Syntax
Change command strings
chg_element gprs_ul_dl_bias <value> <location>

Display command strings

disp_element gprs_ul_dl_bias <location>

Values
Value type Valid range Boolean 0 to 1 0 1 Default value 1 UL bias DL bias

6-358

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

group_block_unblock_allowed

Description
The group_block_unblock_allowed parameter allows the operator to make the A-interface more efficient, by enabling support of the group blocking/unblocking procedure, if MSC supports circuit group block and unblock messages. If this parameter is enabled, the following group block' messages are sent to the MSC: Circuit Group Block Circuit Group Unblock

If this parameter is disabled, the following single circuit block' messages are sent to the MSC: Block Unblock A (no operator actions) Yes No This parameter is only valid at the BSC. This parameter does not apply to RXCDR sites.

Type Supported by OMC-R GUI Cell description required Dependencies

Syntax
Change command string
chg_element group_block_unblock_allowed <value> 0

Display command string

disp_element group_block_unblock_allowed 0

68P02901W23-S

6-359 Nov 2009

Values

Chapter 6: CM database parameters

Values
Value type Valid range Boolean 0 or 1 0 1 Default value None Disabled - BSS sends only single circuit block/unblock' messages to the MSC. Enabled - BSS sends only group block/unblock' messages to the MSC.

References
GSM specification TS GSM 8.08 This is a Motorola defined parameter.

6-360

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

gsl_lcf_mapping

Description
The gsl_lcf_mapping parameter provides an operator with the option of automatic or manual modes for equipage of GSLs inside SYSGEN mode. In automatic mode, the system distributes the equipped GSLs to usable LCFs. In manual mode, the operator is prompted to specify the LCF during equipage of a GSL. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No The GPRS feature must be unrestricted. The system must be in SYSGEN mode.

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

Syntax
Change command strings
chg_element gsl_lcf_mapping <value> bsc

Display command string

disp_element gsl_lcf_mapping bsc

68P02901W23-S

6-361 Nov 2009

Values

Chapter 6: CM database parameters

Values
Value type Valid range Boolean 0 or 1 0 1 Default value 1 0 Manual mode Auto mode Inside SYSGEN (Auto mode - 0 cannot be set) Outside SYSGEN (Manual mode)

6-362

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

gsm_bss_half_rate_enabled

Description
The gsm_bss_half_rate_enabled parameter enables or disables the GSM Half Rate feature at the BSS. A warning is displayed if an attempt is made to enable GSM HR outside Sysgen mode when there is no AXCDR device with CIC validation enabled. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No The GSM Half Rate feature must be unrestricted. handover_required_sp_ver_used must be enabled.

Syntax
Add/Change command strings
chg_element gsm_bss_half_rate_enabled <value> <location>

NOTE
The following warning is displayed if an attempt is made to disable gsm_bss_half_rate_enabled when either CIC validation or eac_mode is enabled for the AXCDR: WARNING: AXCDR CIC validation and/or enhanced auto connect mode are currently enabled. The following warning is displayed if an attempt is made to disable CIC validation for the AXCDR when GSM HR is enabled: WARNING: The AXCDR will not support AMR/GSM HR when CIC Validation is disabled.

Display command strings

disp_element gsm_bss_half_rate_enabled <location>

68P02901W23-S

6-363 Nov 2009

Values

Chapter 6: CM database parameters

Values
Value type Valid range Boolean 0 or 1 0 1 Default value 0 Disabled Enabled Disabled

6-364

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

gsm_cell_id_format

Description
The gsm_cell_id_format parameter specifies the format of the GSM cell Identification sent by the Call Processor (CP) to the switch. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No This parameter can be set only at the BSC.

Syntax
Change command string
chg_element gsm_cell_id_format <value> 0

Display command string

disp_element gsm_cell_id_format 0

Values
Value type Valid range Integer 0 to 2 0 1 2 Default value 1 Whole Cell Global Identification (CGI) Location Area Code (LAC), and Cell Identity (CI) Cell Identity (CI)

68P02901W23-S

6-365 Nov 2009

UTRAN Cell Identifier

Chapter 6: CM database parameters

UTRAN Cell Identifier

It is possible to hand over calls to 3G UTRAN cells. This is set up using the neighbor commands: add_neighbor, modify_neighbor, anddel_neighbor disp_neighbor. UTRAN Cell IDs are required parameter entries for these commands. The UTRAN cell ID format consists of five fields: MCC - Mobile Country Code. MNC - Mobile Network Code. LAC - Location Area Code. RNC - Radio Network Controller Identity. CI - Cell Identity.

UTRAN cell IDs are typically displayed in the following format: 543 21 61986 (F222h) 34944 (8880h) 4011 Where: 543 21 61986 349444011 is: MCC MNC LAC RNCICI

References
GSM specification GSM TS 8.08 - 3.2.2.27 This is a Motorola defined parameter.

6-366

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

gsm_half_rate_enabled

Description
The gsm_half_rate_enabled parameter enables or disables the GSM Half Rate (HR) feature at a cell. Executing the copy_cell command sets this parameter to the default value in the new cell and displays a warning indicating that the parameter has been modified. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes The GSM Half Rate feature must be unrestricted. The BTS site for the cell must be solely comprised of Horizonmacro family of cabinets, M-Cell2 or M-Cell6 cabinets, or a mixture of Horizonmacro and M-Cell2/6 cabinets.

Syntax
Add/Change command strings
chg_element gsm_half_rate_enabled <value> <location> <cell_desc> chg_cell_element gsm_half_rate_enabled <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> full disp_element gsm_half_rate_enabled <location> <cell_desc>

Values
Value type Valid range Boolean 0 or 1 0 1 Default value 0 Disabled Enabled Disabled

68P02901W23-S

6-367 Nov 2009

half_rate_enabled

Chapter 6: CM database parameters

half_rate_enabled

Description
The half_rate_enabled parameter enables or disables Half Rate at an RTF. The half_rate_enabled RTF parameter can only be modified by unequipping and re-equipping the RTF. This RTF parameter cannot be set for a sub-equipped RTF. The RTF parameter is displayed using the disp_equipment command. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No The AMR feature and/or GSM Half Rate feature must be unrestricted. The half_rate_enabled parameter is only applicable at a BTS site comprised solely of Horizonmacro cabinets, M-Cell2 or M-Cell6 cabinets, or a mixture of Horizonmacro, Horizonmacro2 and M-Cell6 cabinets. The half_rate_enabled RTF parameter is only prompted for during the equipage of an RTF.

Syntax
Add/Change command strings
equip <location> rtf

Display command strings

disp_equipment <location> rtf <rtf_id1> <rtf_id2>

Values
Value type Valid range Boolean 0 or 1 0 1 Default value 0 Disabled Enabled

6-368

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

handover_power_level

Description
The handover_power_level parameter defines the power control level to be used by an MS during a handover to a different cell. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes The maximum value for a PGSM or EGSM system is 19. The maximum value for a DCS1800 system is 15.

Syntax
Add/Change command strings
add_cell <gsm_cell_id> <location> chg_element handover_power_level <value> <location> <cell_desc> chg_cell_element <location> handover_power_level <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full] disp_element handover_power_level <location> <cell_desc>

Values
Value type Valid ranges Integer See Table 6-15, Table 6-16 nd Table 6-17.

68P02901W23-S

6-369 Nov 2009

Values

Chapter 6: CM database parameters

Table 6-15 lists the maximum MS power level for PGSM and EGSM cells.

Table 6-15
Value

Max MS power level for PGSM and EGSM

Power level Value Power level

2 3 4 5 6 7 8 9 10

39 dBm 37 dBm 35 dBm 33 dBm 31 dBm 29 dBm 27 dBm 25 dBm 23 dBm

11 12 13 14 15 16 17 18 19

21 dBm 19 dBm 17 dBm 15 dBm 13 dBm 11 dBm 9 dBm 7 dBm 5 dBm

Table 6-16 lists the maximum mobile power level for DCS1800 and PCS1900 cells.

Table 6-16
Value 0 1 2 3 4 5 6 7

Max MS power level for DCS1800 and PCS1900 cells

Power level 30 dBm 28 dBm 26 dBm 24 dBm 22 dBm 20 dBm 18 dBm 16 dBm Value 8 9 10 11 12 13 14 15 Power level 14 dBm 12 dBm 10 dBm 8 dBm 6 dBm 4 dBm 2 dBm 0 dBm

Table 6-17 lists the maximum mobile power level for DCS1800 and PCS1900 cells for class 3 mobiles.

Table 6-17
Value 29 30

Max MS power level for class 3 mobiles

Power level 36 dBm 34 dBm 2 Value 31 Power level 32 dBm

Default value

6-370

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

References

References
GSM specification 5.05 - 4.1.1 This is a Motorola defined parameter.

68P02901W23-S

6-371 Nov 2009

Syntax
Add/Change command strings
chg_element hcs_thr <value> <location> <cell_desc> chg_cell_element hcs_thr <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> full disp_element hcs_thr <location> <cell_desc>

Values
Value type Valid range Integer 0 to 31 0 1 ... 31 Default value 0 Represents signal strength threshold in 2 dBm steps: -110 dBm -108 dBm ... -48 dBm

68P02901W23-S

6-377 Nov 2009

hdsl_losw_oos

Chapter 6: 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. The system takes the HDSL link out of service if the sync word is not received for the hdsl_losw_oos period. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No This parameter may only be changed if the HDSL feature is unrestricted. This parameter may only be changed at an M-Cellcity, Horizonmicro or Horizoncompact site. Changing this parameter affects all master modems equipped as msi_type niu_hdsl at the local M-Cell site. All slave modem alarm thresholds are identical to the master modem alarm thresholds.

Syntax
Change command string
chg_element hdsl_losw_oos <value> <location>

Display command string

disp_element hdsl_losw_oos <location>

Values
Value type Valid range Default value Integer (seconds) 0 to 3598 6

6-378

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

hdsl_losw_restore

Description
The hdsl_losw_restore parameter defines the HDSL Loss of Sync Word (LOSW) restoration period. If the sync word is received for the hdsl_losw_restore_period, the system restores the HDSL link back into service (INS). Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No This parameter may only be changed if the HDSL option is unrestricted. This parameter may only be changed at an M-Cellcity, Horizonmicro or Horizoncompact site. Changing this parameter affects all master modems equipped as msi_type niu_hdsl at the local M-Cell site. All slave modem alarm thresholds are identical to the master modem alarm thresholds.

Syntax
Change command string
chg_element hdsl_losw_restore <value> <location>

Display command string

disp_element hdsl_losw_restore <location>

Values
Value type Valid range Default value Integer (seconds) 0 to 65534 6

68P02901W23-S

6-379 Nov 2009

hdsl_snr_daily

Chapter 6: CM database parameters

hdsl_snr_daily

Description
The hdsl_snr_daily parameter defines the HDSL Signal to Noise Ratio (SNR) daily alarm level. If the SNR alarm level drops below the hdsl_snr_daily threshold for an accumulated period of hdsl_snr_daily_mon_period within a given 24 hour period, a daily alarm is generated. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No This parameter may only be changed if the HDSL option is unrestricted. This parameter may only be changed at an M-Cellcity, Horizonmicro or Horizoncompact site. Changing this parameter affects all master modems equipped as msi_type niu_hdsl at the local M-Cell site. All slave modem alarm thresholds are identical to the master modem alarm thresholds.

Syntax
Change command string
chg_element hdsl_snr_daily <value> <location>

Display command string

disp_element hdsl_snr_daily <location>

6-380

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Values

Values
Value type Valid range Integer (representing 0.5 dB steps) 6 to 44 6 7 8 ... ... ... 44 Default value 16 (8 dB) Represents 3 dB to 22 dB, as shown below: 3 dB 3.5 dB 4 dB ... ... ... 22 dB

68P02901W23-S

6-381 Nov 2009

hdsl_snr_daily_mon_period

Chapter 6: 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). If the SNR level drops below the hdsl_snr_daily threshold for an accumulated period of hdsl_snr_daily_mon_period within a given 24 hour period, a daily alarm is generated. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No This parameter may only be changed if the HDSL option is unrestricted. This parameter may only be changed at an M-Cellcity, Horizonmicro or Horizoncompact site. Changing this parameter affects all master modems equipped as msi_type niu_hdsl at the local M-Cell site. All slave modem alarm thresholds are identical to the master modem alarm thresholds.

Syntax
Change command string
chg_element hdsl_snr_daily_mon_period <value> <location>

Display command string

disp_element hdsl_snr_daily_mon_period <location>

Values
Value type Valid range Default value Integer (seconds) 0 to 65534 20

6-382

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

hdsl_snr_hourly

Description
The hdsl_snr_hourly parameter sets the threshold period for the hourly signal to noise ratio (SNR). If the SNR level drops below the hdsl_snr_hourly threshold for an accumulated period of hdsl_snr_hourly_mon_period within a given 60 minute period, an hourly alarm is generated. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No This parameter may only be changed if the HDSL option is unrestricted. This parameter may only be changed at an M-Cellcity, Horizonmicro or Horizoncompact site. Changing this parameter affects all master modems equipped as msi_type niu_hdsl at the local M-Cell site. All slave modem alarm thresholds are identical to the master modem alarm thresholds.

Syntax
Change command string
chg_element hdsl_snr_hourly <value> <location>

Display command string

disp_element hdsl_snr_hourly <location>

68P02901W23-S

6-383 Nov 2009

Values

Chapter 6: CM database parameters

Values
Value type Valid range Integer (representing 0.5 dB steps) 8 to 44 8 9 10 ... ... ... 44 Default value 18 (9 dB) Represents 4 dB to 22 dB, as shown below: 4 dB 4.5 dB 5 dB ... ... ... 22 dB

6-384

68P02901W23-S Nov 2009

Syntax
Change command strings
chg_element ho_exist_congest <value> <location> <cell_desc> chg_cell_element ho_exist_congest <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> full disp_element ho_exist_congest <location> <cell_desc>

6-390

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Values

Values
Value type Valid range Integer 0 to 2 0 1 2 Default value 0 No hand over attempts (for this condition). Attempt to hand over as many calls as the number of queued assignment requests. Attempt to hand over as many calls as meet the congestion handover criteria.

References
GSM specification TS GSM 08.08 This is a Motorola defined parameter.

68P02901W23-S

6-391 Nov 2009

ho_margin_def

Chapter 6: CM database parameters

ho_margin_def

Description
The ho_margin_def parameter sets the default value for the neighbor handover margin (ho_margin_cell) attribute of the source cell. The neighbor handover margin is set using the add_neighbor command and changed using the modify_neighbor command. The handover margin is the amount by which the neighboring cell received signal strength must exceed the source cell received signal to request a handover. In the context of the power budget process, the following equation must be true: IfPBGT(n) > ho_margin(n) then a handover may be required. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes None

Syntax
Add/Change command strings
add_cell <gsm_cell_id> <location> chg_element ho_margin_def <value> <location> <cell_desc> chg_cell_element ho_margin_def <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full] disp_element ho_margin_def <location> <cell_desc>

Values
Value type Valid range Default value Integer (dB) -63 to +63 8

6-392

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

References

References
GSM parameter GSM specification HO_MARGIN_DEF 5.08 - Appendix A, 3.1f: PBGT(n), and section 3.2.2e. 5.08 - Appendix A - Table 1 12.20 - 5.2.8.4 adjacent Cell Handover - ho Margin Default 12.20 - 5.2.8.4 adjacent Cell Handover - ho Margin Cell 12.20 - 5.2.8.2

68P02901W23-S

6-393 Nov 2009

ho_margin_type5

Chapter 6: CM database parameters

ho_margin_type5

Description
The ho_margin_type5 parameter sets the power budget type 5 handover margin. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator action) Yes Yes None

Syntax
Change command string
modify_neighbor <src_cell_id> <neighbor_cell_id> ho_margin_type5 <value>

Display command strings

disp_neighbor <src_cell_desc> [<neighbor_cell_id>|all] disp_neighbor <source cell_name> [<internal neighbor cell_name>] disp_neighbor <src_cell_desc> [TEST <test neighbor_cell_id>]

Values
Value type Valid range Default value Integer (dBm) -63 to +63 63

6-394

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

ho_margin_usage_flag

Description
The ho_margin_usage_flag parameter determines which sorting algorithm the system uses to sort the neighbor list. If ho_margin_usage_flag is disabled, handover candidates are always sorted using ho_margin_cell. If ho_margin_usage_flag is enabled: Handover candidates for RXLEV handovers are sorted using ho_margin_rxlev [n]. Handover candidates for RXQUAL handovers are sorted using ho_margin_rxqual [n]. All other handover causes that have neighbors are sorted using ho_margin_cell value. A (no operator action) Yes Yes None

Type Supported by OMC-R GUI Cell description required Dependencies

Syntax
Add/Change command strings
chg_element ho_margin_usage_flag <value> <location> <cell_desc> chg_cell_element ho_margin_usage_flag <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> full disp_element ho_margin_usage_flag <location> <cell_desc>

68P02901W23-S

6-395 Nov 2009

Values

Chapter 6: CM database parameters

Values
Value type Valid range Boolean 0 or 1 0 1 Default value 0 Disabled Enabled

6-396

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

ho_only_max_pwr

Description
The ho_only_max_pwr parameter specifies whether the MS or the BTS must be at full power before a rxlev or rxqual handover can take place. If this option is enabled: The MS must be at full power for an uplink handover. The BTS must be at full power for a downlink handover. A (no operator actions) Yes Yes To use the ho_only_max_pwr parameter, the decision_alg_type parameter must equal 1, to allow the MS or BTS to reach full power.

Type Supported by OMC-R GUI Cell description required Dependencies

Syntax
Change command strings
chg_element ho_only_max_pwr <value> <location> <cell_desc> chg_cell_element ho_only_max_pwr <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> full disp_element ho_only_max_pwr <location> <cell_desc>

Values
Value type Valid range Boolean 0 or 1 0 1 Default value 0 Disabled Enabled

68P02901W23-S

6-397 Nov 2009

ho_pwr_level_inner

Chapter 6: CM database parameters

ho_pwr_level_inner

Description
The ho_pwr_level_inner parameter specifies the handover power level for the inner zone of a Dual Band cell for an inter-cell handover. The valid range for this parameter depends on the frequency of the inner zone. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator action) Yes Yes The Dual Band Cells feature must be unrestricted.

NOTE
The element handover_power_level does not apply to intra-cell handovers.

Syntax
Change command strings
chg_element ho_pwr_level_inner <value> <location> <cell_desc> chg_cell_element ho_pwr_level_inner <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> full disp_element ho_pwr_level_inner <location> <cell_desc>

Values
Value type Valid ranges Integer See Table 6-18, Table 6-19 and Table 6-20.

6-398

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Values

Table 6-18 lists the maximum MS power level for PGSM and EGSM cells.

Table 6-18
Value 2 3 4 5 6 7 8 9 10

Max MS power level for PGSM and EGSM cells

Power level 39 dBm 37 dBm 35 dBm 33 dBm 31 dBm 29 dBm 27 dBm 25 dBm 23 dBm Value 11 12 13 14 15 16 17 18 19 Power level 21 dBm 19 dBm 17 dBm 15 dBm 13 dBm 11 dBm 9 dBm 7 dBm 5 dBm

Table 6-19 the maximum mobile power level for DCS1800 and PCS1900 cells.

Table 6-19
Value 0 1 2 3 4 5 6 7

Max MS power level for DCS1800 and PCS1900 cells

Power level 30 dBm 28 dBm 26 dBm 24 dBm 22 dBm 20 dBm 18 dBm 16 dBm Value 8 9 10 11 12 13 14 15 Power level 14 dBm 12 dBm 10 dBm 8 dBm 6 dBm 4 dBm 2 dBm 0 dBm

Table 6-20 lists the maximum mobile power level for DCS1800 and PCS1900 cells for class 3 mobiles.

Table 6-20
Value 29 30

Max MS level for class 3 mobiles

Power level 36 dBm 34 dBm 2 Value 31 Power level 32 dBm

Default value

68P02901W23-S

6-399 Nov 2009

hop_count

Chapter 6: CM database parameters

hop_count

Description
The hop_count parameter, combined with the hop_count_timer parameter, limits the number of intra-cell interference handovers for a call. The hop_count parameter sets the number of handovers. If the number of handovers defined by the hop_count parameter occur within the time set by the hop_count_timer, the system escalates the handover to an RXQUAL handover to another cell. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes None

Syntax
Change command strings
chg_element hop_count <value> <location> <cell_desc> chg_cell_element hop_count <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> full disp_element hop_count <location> <cell_desc>

Values
Value type Valid range Default value Integer (quantity of intra-cell interference handovers) 0 to 255 (0 disables intra-cell interference handovers) 255

6-400

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

hop_qual_enabled

Description
The hop_qual_enabled parameter enables or disables the use of specific rxqual thresholds for hopping call handovers. Trials have shown that non-hopping calls can show poor quality of service when the reported rxqual value is around 5, whereas hopping calls can provide the same quality of service with the reported rxqual value at 6 or 7. If hop_qual_enabled is enabled and a hopping call is in progress, the system uses the rxqual values set with the chg_cell_element command (see Syntax). If hop_qual_enabled is disabled, the normal rxqual values set with the add_cell command are used.

NOTE
If both hop_qual_enabled and data_qual_enabled are enabled, data_qual_enabled takes precedence for data transmission in a hopping call.

Type Supported by OMC-R GUI Cell description required Dependencies

A (no operator action required) Yes Yes alt_qual_proc

Syntax
Change command string
chg_cell_element hop_qual_enabled <value> <cell_desc_opt> If the value is 1 (enabled), the system prompts for the hopping threshold values of the following parameters: l_rxqual_dl_h_hopping on page 6-467 l_rxqual_ul_p_hopping on page 6-506

68P02901W23-S

6-401 Nov 2009

Values

Chapter 6: CM database parameters

l_rxqual_dl_p_hopping on page 6-480 l_rxqual_ul_h_hopping on page 6-493 If Half Rate is enabled, l_rxqual_dl_h_hopping_hr on page 6-471 If Half Rate is enabled, l_rxqual_ul_p_hopping_hr on page 6-510

Display command strings

disp_cell <cell_id> full disp_element hop_qual_enabled <location> <cell_desc>

Values
Value type Valid range Boolean 0 to 1 0 1 Default value 0 Disabled Enabled

6-402

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

hopping_support

Description
The hopping_support parameter defines the frequency hopping in a cell. Two methods of achieving frequency hopping are available.

Synthesizer Frequency Hopping

This is accomplished by the high speed switching of the transmit and receive frequency synthesizers of the individual transceivers. As a result of the dynamic nature of the transmit frequency, broadband (hybrid) combining of the transmitters is necessary. The combination losses associated with this technique must be acceptable.

Baseband Frequency Hopping

This is accomplished by routing the traffic channel data through fixed frequency transceivers through the TDM highway on a timeslot basis. In this case, the transceiver would have fixed tuned transmitters combined either in low loss tuned combiners, or hybrid combiners. The frequency hopping set (mobile allocation, MA) is limited to the number of transceivers equipped at a specific site. The frequency hopping technique employed is dependent upon the losses, specific cells can tolerate in their transmit paths, and the number of transceivers associated with specific cells. BTS restricts the baseband hopping capabilities on double density CTU2 DRIs, of which carrier A is EGPRS capable. Carrier A and carrier B are the two DD CTU2 radios on the Horizon II cabinet. Type Supported by OMC-R GUI Cell description required Dependencies Operator actions B (operator action required) Yes Yes None Place the system in the SYSGEN ON mode before using the chg_element or chg_cell_element commands to change this parameter. Using the chg_hop_params (see chg_hop_params on page 3-128) command to change the hopping system does not require SYSGEN ON.

68P02901W23-S

6-403 Nov 2009

Syntax

Chapter 6: CM database parameters

Syntax
Change command strings
chg_element hopping_support <value> <location> <cell_desc> chg_cell_element hopping_support <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> full disp_element hopping_support <location> <cell_desc>

Values
Value type Valid range Integer 0 to 2 0 1 2 Default value 0 No hopping in this cell Synthesizer hopping Baseband hopping

References
GSM specification Motorola GSM B1 document - 4.2.1 5.01 - 6 This is a Motorola defined parameter.

6-404

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

hopping_systems_enabled

Description
The hopping_systems_enabled parameter enables or disables a frequency hopping system. An index number (fhi) is required. The frequency hopping indicator (fhi) value specifies which hopping system is affected. The range of values, entered as <index> is 0 to 3. Type Supported by OMC-R GUI Cell description required Dependencies Operator actions B (operator action required) Yes Yes None The system must be in SYSGEN ON mode to change this parameter with the chg_element or chg_cell_element commands. Using the chg_hop_params (see chg_hop_params on page 3-128) command to change the hopping system does not require SYSGEN ON.

Syntax
Change command strings
chg_element hopping_systems_enabled,<index> <value> <location> <cell_desc> chg_cell_element hopping_systems_enabled,<index> <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> <full> disp_cell <cell_id> <full>disp_element hopping_systems_enabled,<index><location> <cell_desc> disp_hopping <cell_desc> [<fhi> | active]

68P02901W23-S

6-405 Nov 2009

Values

Chapter 6: CM database parameters

Values
Value type Valid range Boolean 0 or 1 0 1 Default value None Disabled Enabled

References
GSM specification 5.01 - 6 This is a Motorola defined parameter.

6-406

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

hopping_systems_hsn

Description
The hopping_systems_hsn parameter specifies the hopping sequence (generator) number (HSN) to be used by the frequency hopping system. HSN is one of seven parameters that defines a particular physical channel in a BTS. An index number (fhi) is required. The frequency hopping indicator (fhi) value specifies which hopping system is affected. The range of values, entered as <index> is 0 to 3. Type Supported by OMC-R GUI Cell description required Dependencies Operator actions B (operator action required) Yes Yes None Respond to the SITE reset prompt which will be displayed after the chg_element command is entered to modify this parameter.

Syntax
Change command strings
chg_element hopping_systems_hsn,<index> <value> <location> <cell_desc> chg_cell_element hopping_systems_hsn <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> full disp_element hopping_systems_hsn,<index> <location> <cell_desc> disp_hopping <cell_desc> [<fhi> | active]

68P02901W23-S

6-407 Nov 2009

Values

Chapter 6: CM database parameters

Values
Value type Valid range Integer 0 to 63 0 1 to 63 Default value None Cyclic hopping. The MA is hopped through lowest to highest magnitude, and then the cycle repeats. Random hopping. HSN and MA are entries to the algorithm table 6 of GSM Rec. 5.02.

References
GSM parameter GSM specification HSN 5.02 - 5.6.3, 6.2.2, 6.2.3 5.02 - table 6: hopping algorithm 5.01 - 6

6-408

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

hopping_systems_mobile_alloc

Description
The hopping_systems_mobile_alloc parameter allocates the Absolute Radio Frequency Channel Number (ARFCN) frequencies for hopping (either baseband hopping or synthesizer hopping). Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Not required for chg_hop_params command. Required for disp_cell and disp_element commands. Refer to the descriptions for the chg_hop_params command (see chg_hop_params on page 3-128) for restrictions on changing the hopping parameters. The system does not check for errors when changes are made in SYSGEN ON mode. When SYSGEN is turned off, however, the system does check for errors, and may reject the command.

Syntax
Change command strings
chg_hop_params <location> chg_hop_params <cell_desc>

NOTE
chg_hop_params can be used in SYSGEN or out of SYSGEN. chg_hopping must be executed in SYSGEN_ON mode.

68P02901W23-S

6-409 Nov 2009

Values

Chapter 6: CM database parameters

Display command strings

disp_cell <cell_id> full disp_element hopping_systems_mobile_alloc,<index1>,<index2> <location> <cell_desc> disp_hopping <site> [active] disp_hopping <cell_desc> [<fhi> | active]

Values
Value type Valid range Integer Variable ARFCN depends on the frequency type for the cell. For PGSM, the range is 1 through 124. For EGSM, the range is either: 1 to 124, 975 to 1023, or 0. For DCS1800, the range is 512 to 885. For PCS1900 the range is 512 to 810.

Default value

None

References
GSM specification 5.01 - 6 This is a Motorola defined parameter.

6-410

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

hr_fr_hop_count

Description
The hr_fr_hop_count parameter specifies the number of Intra-Cell quality handovers from half-rate channels to full rate channels for a call on a per cell basis. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes The AMR feature and/or the GSM Half Rate feature must be unrestricted. The value of this parameter must not exceed the value of hop_count.

Syntax
Add/Change command strings
chg_element hr_fr_hop_count <value> <location> <cell_desc> chg_cell_element hr_fr_hop_count <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> full disp_element hr_fr_hop_count <location> <cell_desc>

Values
Value type Valid range Default value Integer 0 to 255 1

68P02901W23-S

6-411 Nov 2009

hr_intracell_ho_allowed

Chapter 6: CM database parameters

hr_intracell_ho_allowed

Description
The parameter enables or disables the support for Intra-Cell quality handovers for half-rate channels within a cell. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes The AMR feature and/or the GSM Half Rate feature must be unrestricted.

Syntax
Add/Change command strings
chg_element hr_intracell_ho_allowed <value> <location> <cell_desc> chg_cell_element hr_intracell_ho_allowed <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> full disp_element hr_intracell_ho_allowed <location> <cell_desc>

6-412

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Values

Values
Value type Valid range Integer 0 to 3 0 1 2 3 Half-rate intra-cell quality handovers are not initiated by the BSS. Handover Required is sent to MSC. Half-rate intra-cell quality handovers are disabled. Handover Required is not sent to MSC. Half-rate intra-cell quality handovers are enabled. Full-rate only is allowed. Half-rate intra-cell quality handovers are enabled. Half-rate and Full-rate are allowed for interference based handover, full rate only for quality based handover.

Default value

68P02901W23-S

6-413 Nov 2009

hr_res_ts

Chapter 6: CM database parameters

hr_res_ts

Description
The hr_res_ts parameter specifies the maximum number of half-rate capable timeslots to be reserved within each zone of the cell. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes The AMR feature and/or the GSM Half Rate feature must be unrestricted.

Syntax
Add/Change command strings
chg_element hr_res_ts <value> <location> <cell_desc> chg_cell_element hr_res_ts <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> full disp_element hr_res_ts <location> <cell_desc>

Values
Value type Valid range Default value Integer (timeslot) 0 to 255 2 In steps of 1 timeslot

6-414

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

illegal_circuit_id

Description
The illegal_circuit_id parameter is used as an internal place holder in call processing to show that no circuit has been assigned to a call. The value may be changed to permit a customer to specify the circuit ID to be used as the illegal_circuit_id. If the value is not changed, a Motorola specified illegal_circuit_id is assigned. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No This parameter only applies to the BSC.

Syntax
Change command string
chg_element illegal_circuit_id <value> 0

Display command string

disp_element illegal_circuit_id 0

Values
Value type Valid range Default value Integer 0 to 65535 0

68P02901W23-S

6-415 Nov 2009

Improve_ts_enabled

Chapter 6: CM database parameters

Improve_ts_enabled

Description
The Improve_ts_enabled parameter specifies the enable or disable status of the improved timeslot sharing feature at the BSS. This parameter can be changed inside and outside SYSGEN mode. Type Supported by OMC-R GUI Cell description required Dependencies A (No operator actions) Yes No The Improved timeslot sharing optional feature is unrestricted.

Syntax
Display command strings
disp_element improve_ts_enabled <location>

Change command strings

chg_element improve_ts_enabled <value> <location>

Input parameters
location Indicates the site location. 0 or bsc BSC

6-416

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Example

Example
Example 1
chg_element improve_ts_enabled 1 bsc Where: 1 bsc is: specifies the enable status of the improved timeslot sharing feature. location of the processors.

System response
WARNING: B-U DD CTU2 DRIs must be cycled to activate ITS at specific sites or reset BTS site COMMAND ACCEPTED

Example 2
chg_element improve_ts_enabled 0 bsc Where: 0 bsc is: specifies the disable status of the improved timeslot sharing feature. location of the processors.

System response
WARNING: B-U DD CTU2 DRIs must be cycled to deactivate ITS at specific sites or reset BTS site COMMAND ACCEPTED

Example 3
chg_element improve_ts_enabled 2 bsc

System response
ERROR: Range Error, parameter number: 2.

68P02901W23-S

6-417 Nov 2009

Values

Chapter 6: CM database parameters

Values
Value type Valid range Boolean 0 or 1 0 1 Default value 0 Disabled Enabled

6-418

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

imrm_dcs1800_weight

Description
The imrm_dcs1800_weight parameter specifies the weighting for the dcs1800 frequency. A value of 0 specifies no support; a value of 100 specifies most preferred. The BSS rejects an attempt to modify this parameter to 100 if any of the other supported band weights have a setting of 100. Type Supported by OMC-R GUI Cell description required Dependencies A (No operator actions) Yes Yes None

Syntax
Change command strings
chg_element imrm_dcs1800_weight <value> <location> <cell_desc> chg_cell_element imrm_dcs1800_weight <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> full disp_element imrm_dcs1800_weight <location> <cell_desc>

Values
Value type Valid range Default value Integer 0 to 100 0

68P02901W23-S

6-419 Nov 2009

imrm_egsm_weight

Chapter 6: CM database parameters

Chapter 6: CM database parameters

IncellOpt

{28938}

Description
The IncellOpt parameter indicates whether the Incell Support feature functionality is unrestricted in the BSS software. Command Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No If the IncellOpt flag indicates that Incell Support is restricted, attempts to change Incell Support specific database parameter is rejected.

Syntax
Change command strings
chg_element IncellOpt <value> <location>

Display command strings

disp_element IncellOpt <location> disp_options

Values
Value type Valid range Boolean 0 or 1 0 1 Default value N/A restricted unrestricted

6-428

68P02901W23-S Nov 2009

Chapter 6: CM database parameters

Values
Valid range 0 to 3 0 1 2 3 Default value 1 Downlink TBF starts with CS1. Downlink TBF starts with CS2. Downlink TBF starts with CS3. Downlink TBF starts with CS4.

6-434

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

inner_hr_usage_thres

Description
The inner_hr_usage_thres parameter specifies the congestion threshold for the following: Reconfiguration of half-rate capable full rate calls to AMR/GSM half-rate calls to the inner zone. The assignment of new calls on half-rate channels establishing in the inner zone. A (no operator actions) Yes Yes The AMR feature and/or the GSM Half Rate feature must be unrestricted.

Type Supported by OMC-R GUI Cell description required Dependencies

Syntax
Add/Change command strings
chg_element inner_hr_usage_thres <value> <location> <cell_desc> chg_cell_element inner_hr_usage_thres <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> full disp_element inner_hr_usage_thres <location> <cell_desc>

Values
Value type Valid range Default value Integer (percentage) 0 to 101 101

68P02901W23-S

6-435 Nov 2009

inner_zone_alg

Chapter 6: CM database parameters

inner_zone_alg

Description
The inner_zone_alg parameter specifies the use algorithm and the associated parameters for the inner zone of the cell. Type Supported by OMC-R GUI Cell description required Dependencies B (operator actions required) Yes Yes The Concentric Cells feature must be unrestricted to use the inner_zone_alg parameter. Cannot set this parameter to dual band cells for PCS1900 cells. Before this parameter can be set to Dual Band (3) the following dependencies must be met: The Dual Band Cells feature must be unrestricted in order to set inner_zone_alg to 3. The Coincident Multiband feature and the Dual Band Cells feature must not be set at the same time, so coincident_mb must be 0. RTFs must not be equipped for the inner zone. The Multiband Inter-Cell Handover feature must be enabled to change inner_zone_alg to 3 (mb_preference parameter must not be 0). Change the security level to 2 or more before using this parameter.

Operator actions

Syntax
Change command string
chg_cell_element inner_zone_alg <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> full disp_element inner_zone_alg <location> <cell_desc>

6-436

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Values

Values
Value type Valid range Integer 0 to 3 0 1 Disable inner zone. Power based use algorithm. The system displays prompts for: ms_txpwr_max_inner Valid range: PGSM and EGSM: 5 to 39 dBm (odd values only; value must be less than or equal to max_tx_ms) Default value: max_tx ms DCS1800 and PCS1900: 0 to 30 dBm (even values only; value must be less than or equal to max_tx_ms) Default value: max_tx ms zone_ho_hyst, Valid range: 0 to 30 Default value: 0 rxlev_dl_zone Valid range: 0 to 63 Default value: 63 rxlev_ul_zone Valid range: 0 to 63 Default value: 63

Interference based use algorithm. The system prompts for: neighbor_report_timer Valid range: 0 to 255 SACCH periods Default value: 10

Dual Band Cell use. The system displays prompts as shown in Table 6-21.

Default value

Table 6-21 shows the prompted parameters when 3 is entered for inner_zone_alg.

68P02901W23-S

6-437 Nov 2009

Values

Chapter 6: CM database parameters

Table 6-21

Prompted parameters for Dual Band Cell use

Parameter name secondary_freq_type Notes Required. Inner zone frequency type for dual band cell. If cell primary frequency is PGSM or EGSM, must be DCS1800. If cell primary frequency is DCS1800, can be PGSM or EGSM. Optional. Range PGSM, EGSM or DCS1800

Prompt Enter secondary frequency type:

Enter maximum base transmit power for the inner zone: Enter maximum MS transmit power for the inner zone:

bts_txpwr_max_inner

As defined for max_tx_bts Default: 0. As defined for max_tx_ms, based on secondary frequency type. As defined for handover_power_level, based on secondary frequency type. Default: 2. -63 to +63 Default: 0. 0 to 63 Default: 63. 0 to 63 Default: 63. -63 to +63 Default: 0.

ms_txpwr_max_inner

Required.

Enter handover power level for the inner zone:

ho_pwr_level_inner

Optional.

Enter inner zone handover hysteresis: Enter downlink receive level threshold for the inner zone: Enter uplink receive level threshold for the inner zone: Enter dual band offset:

zone_ho_hyst rxlev_dl_zone

Optional. Optional.

rxlev_ul_zone

Optional.

dual_band_offset

Optional.

6-438

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

intave

Description
The intave parameter specifies the algorithm data needed for performing interference band averaging and classification during idle channel interference processing.

CAUTION
The valid range of values for intave is 1 to 31. If a value greater then 31 is entered, undetermined results may occur affecting service. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes None

Syntax
Add/Change command strings
add_cell <gsm_cell_id> <location> chg_element intave <value> <location> <cell_desc> chg_cell_element intave <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full] disp_element intave <location> <cell_desc>

68P02901W23-S

6-439 Nov 2009

Values

Chapter 6: CM database parameters

Values
Value type Valid range Integer (1 step = 2 SACCH multiframes) 1 to 31 1 2 ... ... ... 31 Default value 8 2 SACCH multiframes 4 SACCH multiframes ... ... ... 62 SACCH multiframes

References
GSM specification Used to specify the Intave parameter as described in 5.08 This is a Motorola defined parameter.

6-440

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

inter_cell_handover_allowed

Description
The inter_cell_handover_allowed parameter specifies how internal and external inter-cell handovers are managed at the BSC. Internal inter-cell handovers are defined as handovers between cells in the same BSS. External inter-cell handovers are defined as handovers between cells in different BSSs. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes None

Syntax
Add/Change command strings
add_cell <gsm_cell_id> <location> achg_element inter_cell_handover_allowed <value> <location> <cell_desc> chg_cell_element inter_cell_handover_allowed <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full] disp_element inter_cell_handover_allowed <location> <cell_desc>

68P02901W23-S

6-441 Nov 2009

Values

Chapter 6: CM database parameters

Values
Value type Valid range Integer 0 to 3 0 1 2 3 Default value 1 Outgoing Inter-cell handover is not enabled. The Handover Required message is sent to the MSC. Outgoing Inter-cell handover is enabled. Outgoing internal Inter-cell handover is disabled. The Handover Required message is not sent to the MSC. Outgoing internal and external handovers are disabled and the Handover Required message is not sent to the MSC.

References
GSM parameter GSM specification EN_INTER_HO 8.08 - 3.1.7 8.08 - 5: handover definitions 12.20 - 5.2.8.18 enable BSS Handover Control - enable Intercell Handover

6-442

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

inter_rat_enabled

Description
The inter_rat_enabled parameter selects the mode for the BSS Inter-RAT handover feature. Three modes are available on a per cell basis: Idle. Dedicated. Combination of Idle and Dedicated. A (no operator actions) Yes Yes The BSS Inter-RAT feature must be unrestricted. Values 4 7 are only allowed when Enhanced 2G/3G Handover feature is unrestricted. early_classmark_sending must be set to 2 or 3. phase2_classmark_allowed must be set to 2.

Type Supported by OMC-R GUI Cell description required Dependencies

Syntax
Add/Change command strings
chg_element inter_rat_enabled <value> <location> <cell_desc> chg_cell_element inter_rat_enabled <value> <cell_desc_opt>

NOTE
When changing this parameter to 4, 5, 6 or 7, a warning is issued if early_classmark_sending is set to 0 or 1, or phase2_classmark_allowed is not equal to 2.

68P02901W23-S

6-443 Nov 2009

Values

Chapter 6: CM database parameters

Display command strings

disp_cell <cell_id> [full] disp_element inter_rat_enabled <location> <cell_desc> copy_cell inter_rat_enabled

Values
Value type Valid range Integer 0 to 7 0 1 2 3 4 5 6 7 Default value 0 Off 2G-3G idle 3G-2G dedicated 2G-3G idle and 3G-2G dedicated 2G-3G dedicated 2G-3G idle and 2G-3G dedicated. 3G-2G dedicated and 2G-3G dedicated Idle and bi-directional dedicated

6-444

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

interband_ho_allowed

Description
The interband_ho_allowed parameter specifies the handover frequencies for a cell. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator action required) Yes Yes This parameter is not available unless the Multiband Inter-cell Handover feature is enabled. This parameter must include, at a minimum, the frequency type for the cell. For example, if the cell has a frequency_type of pgsm, then the interband_ho_allowed parameter must include pgsm as a possible destination frequency band for handovers.

Syntax
Change command string
chg_element interband_ho_allowed <value> <location> <cell_desc> chg_cell_element interband_ho_allowed <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> <full> disp_element interband_ho_allowed <location> <cell_desc>

68P02901W23-S

6-445 Nov 2009

Values

Chapter 6: CM database parameters

Values
Value type Valid range Integer 1 to 11 1 2 3 4 5 6 7 8 9 10 11 Default value PGSM EGSM PGSM and EGSM DCS1800 PGSM and DCS1800 EGSM and DCS1800 PGSM, EGSM, and DCS1800 PCS1900 PGSM and PCS1900 EGSM and PCS1900 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

6-446

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

interfer_bands

Description
The interfer_bands parameter specifies the limits for the interference categories (bands) whose limit 0 to X5 is adjusted by Operations and Maintenance (O & M). The bands are: Band 1 Band 2 Band 3 Band 4 Band 5 0 to X1 X1 to X2 X2 to X3 X3 to X4 X4 to X5

The BSS averages the interference level in unallocated timeslots as defined by the intave parameter. The averaged results are then mapped into five interference categories whose limits are adjusted. An index number is required. Index values 0 to 4 correspond to bands X1 to X5. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes interfer_bands,0 interfer_bands,1 interfer_bands,1 interfer_bands,2 interfer_bands,2 interfer_bands,3 interfer_bands,3 interfer_bands,4 must be less than or equal to must be less than or equal to must be less than or equal to must be less than or equal to

Syntax
Change command strings
chg_element interfer_bands,<index> <value> <location> <cell_desc> chg_cell_element interfer_bands,<index> <value> <cell_desc>

68P02901W23-S

6-447 Nov 2009

Values

Chapter 6: CM database parameters

Display command strings

disp_cell <cell_id> full disp_element interfer_bands,<index> <location> <cell_desc>

Values
Value type Valid range Integer 0 to 63 0 1 2 ... ... ... 63 Default value 63 Represents -110 dBm to -47 dBm, as shown below: -110 dBm -109 dBm -108 dBm ... ... ... -47 dBm

NOTE
The system displays a warning message if interfer_bands,4 is changed to a value less than 63.

References
GSM parameter GSM specification INT_BOUND_X1, INT_BOUND_X2, INT_BOUND_X3, INT_BOUND_X4, INT_BOUND_X5 5.08 - Appendix A 5.08 - 0-X5 12.20 - 5.2.8.10 - Interference Averaging Process thresholds 8.08

6-448

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

interfer_ho_allowed

Description
The interfer_ho_allowed parameter disables or enables handovers due to interference. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator action required) Yes Yes None

Syntax
Change command string
add_cell <gsm_cell_id> <location> chg_element interfer_ho_allowed <value> <location> <cell_desc> chg_cell_element interfer_ho_allowed <value><cell_desc>

Display command strings

disp_cell <cell_id> [full] disp_element interfer_ho_allowed <location> <cell_desc>

Values
Value type Valid range Boolean 0 or 1 0 1 Default value 1 Disabled Enabled

68P02901W23-S

6-449 Nov 2009

intra_cell_handover_allowed

Chapter 6: CM database parameters

intra_cell_handover_allowed

Description
This parameter disables or enables intra-cell handovers under two conditions: to begin the handover or to begin the handover when co-channel interference is suspected. Intra-cell handovers are defined as handovers within the same cell. BSS support is optional. If the BSS does not support an internal intra-cell handover, it is initiated by sending a Handover Required message. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes None

Syntax
Add/Change command strings
add_cell <gsm_cell_id> <location> chg_element intra_cell_handover_allowed <value> <location> <cell_desc> chg_cell_element intra_cell_handover_allowed <value> <cell_desc>

Display command strings

disp_cell <cell_id> [full] disp_element intra_cell_handover_allowed <location> <cell_desc>

6-450

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Values

Values
Value type Valid range Integer 0 to 2 0 Intra-cell handovers are performed by the BSS. These calls are included as target cells in a Handover Required message to the MSC. The BSS performs Intra-cell handovers. The MSC is notified with a Handover Performed message. Intra-cell handovers are disabled and the Handover Required message is not sent to the MSC.

1 2 Default value 1

References
GSM parameter GSM specification EN_INTRA_HO, EN_INCOM_HO 5.08 - Appendix A - 4.1 and 4.2 8.08 - 3.1.6 8.08 - 5: handover definitions 12.20 - 5.2.8.18 enable BSS Handover Control - enable Intracell Handover

68P02901W23-S

6-451 Nov 2009

ksw_config

Chapter 6: CM database parameters

ksw_config

Description
The ksw_config parameter specifies the timeslot portion (1024 timeslots) of the dual redundant TDM highway controlled by a KSW pair. The switch fabric can be extended in 1024 timeslot increments to a maximum of 4096 timeslots by adding KSW pairs. To provide 4096 timeslots requires four KSW pairs with each KSW pair handling a 1024 timeslot portion of the TDM highway. Index numbers are used to specify the four highway portions. The index values are set when the system is installed. The range of index values is 0 to 3.

CAUTION
Do not change the values for this parameter unless a KSW is added or removed. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No Changing this parameter is not allowed at M-Cell sites.

Syntax
Change command string
chg_ksw_config <location> <ksw_pair> <highway1> <highway2> <highway3> <highway4>

Display command string

disp_element ksw_config,<index> <location>

NOTE
For more information, refer to the chg_ksw_config descriptions and examples in Chapter 3 Device/function related commands.

6-452

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Values

Values
Value type Valid range Integer (Index number) 0 to 3 0 1 2 3 Default value None Highway portion 0 (0-1023 timeslots) Highway portion 1 (1024-2047 timeslots) Highway portion 2 (2048-3071 timeslots) Highway portion 3 (3072-4095 timeslots)

68P02901W23-S

6-453 Nov 2009

l_rxlev_dl_h

Chapter 6: CM database parameters

l_rxlev_dl_h

Description
The l_rxlev_dl_h parameter specifies the handover thresholds for the lower receive level (rxlev) downlink. This threshold is checked to determine if a handover condition exists. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes None

Syntax
Add/Change command strings
add_cell <gsm_cell_id> <location> chg_element l_rxlev_dl_h <value> <location> <cell_desc> chg_cell_element l_rxlev_dl_h <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full] disp_element l_rxlev_dl_h <location> <cell_desc>

6-454

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Values

Values
Value type Valid range Integer (1 step = 1 dBm) 0 to 63 0 1 2 ... ... ... 63 Default value 10 Represents -110 dBm to -47 dBm, as shown below: -110 dBm and lower -109 dBm -108 dBm ... ... ... -47 dBm and higher

References
GSM parameter GSM specification L_RXLEV_DL_H 5.08 - Appendix A - Table 1

68P02901W23-S

6-455 Nov 2009

l_rxlev_dl_p

Chapter 6: CM database parameters

l_rxlev_dl_p

Description
The l_rxlev_dl_p parameter specifies the lower downlink limit for the signal strength of the serving cell. This threshold is checked to determine if BTS power should be increased. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes Must be less than u_rxlev_dl_p

Syntax
Add/Change command strings
add_cell <gsm_cell_id> <location> chg_element l_rxlev_dl_p <value> <location> <cell_desc> chg_cell_element l_rxlev_dl_p <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full] disp_element l_rxlev_dl_p <location> <cell_desc>

6-456

68P02901W23-S Nov 2009

6-462

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

References

References
GSM parameter GSM specification L_RXQUAL_DL_H 5.08 - Appendix A - Table 1

68P02901W23-S

6-463 Nov 2009

l_rxqual_dl_h_amr_fr

Chapter 6: CM database parameters

l_rxqual_dl_h_amr_fr

Description
The l_rxqual_dl_h_amr_fr parameter specifies the handover control threshold for the full-rate lower received quality (rxqual) downlink. This threshold is checked to determine if a handover condition exists. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes The AMR feature must be unrestricted. This parameter can be changed only at an AMR-capable BTS site. This parameter is prompted when alt_qual_proc is changed.

Syntax
Add/Change command strings
chg_element l_rxqual_dl_h_amr_fr <value> <location> <cell_desc> chg_cell_element l_rxqual_dl_h_amr_fr <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full] disp_element l_rxqual_dl_h_amr_fr <location> <cell_desc>

Values
Value type Valid range Integer 0 to 1810 0 to 7 Default value 226 4 BER (1 step = 0.01% bit error rate) if alt_qual_proc = 0 QBand units if alt_qual_proc = 1 226 BER if alt_qual_proc = 0 4 QBand units if alt_qual_proc = 1

6-464

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

l_rxqual_dl_h_data

Description
The l_rxqual_dl_h_data parameter specifies the handover control threshold for the lower Received (Rx) quality downlink, for data transmissions only (for example modem-to-modem calls). This threshold is checked to determine if a handover condition exists. This threshold is enabled and set to be used when data is being transmitted, by use of the data_qual_enabled parameter in a chg_cell_element command. In this situation it is used instead of the l_rxqual_dl_h threshold value, as set in the add_cell command. Receive quality processing is measured using Bit Error Rate (BER) values or Quality Band (QBand) units. The alt_qual_proc parameter specifies the type of unit. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes alt_qual_proc

Syntax
Change command strings
chg_element l_rxqual_dl_h_data <value> <location> <cell_desc> chg_cell_element l_rxqual_dl_h_data <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full] disp_element l_rxqual_dl_h_data <location> <cell_desc>

Values
Value type Integer

Valid range

0 to 1810 0 to 7

BER (1 step = 0.01% bit error rate) If alt_qual_proc = 0 QBand units If alt_qual_proc = 1 Continued

68P02901W23-S

6-465 Nov 2009

References

Chapter 6: CM database parameters

Default value

0 4

0 BER if alt_qual_proc = 0 4 QBand units if alt_qual_proc = 1

References
GSM parameter GSM specification L_RXQUAL_DL_H 5.08 - Appendix A - Table 1

6-466

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

l_rxqual_dl_h_hopping

Description
The l_rxqual_dl_h_hopping parameter specifies the handover control threshold for the lower Received (Rx) quality downlink, for hopping calls only. This threshold is checked to determine if a handover condition exists. This threshold is enabled and set to be used for hopping calls, by use of the hop_qual_enabled parameter in a chg_cell_element command. In this situation it is used instead of the l_rxqual_dl_h threshold value, as set in the add_cell command. Receive quality processing is measured using Bit Error Rate (BER) values or Quality Band (QBand) units. The alt_qual_proc parameter specifies the type of unit. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes alt_qual_proc

Syntax
Change command strings
chg_element l_rxqual_dl_h_hopping <value> <location> <cell_desc> chg_cell_element l_rxqual_dl_h_hopping <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full] disp_element l_rxqual_dl_h_hopping <location> <cell_desc>

Values
Value type Valid range Integer 0 to 1810 0 to 7 Default value 0 4 BER (1 step = 0.01% bit error rate) If alt_qual_proc = 0 QBand units If alt_qual_proc = 1 0 BER if alt_qual_proc = 0 4 QBand units if alt_qual_proc = 1

68P02901W23-S

6-467 Nov 2009

References

Chapter 6: CM database parameters

References
GSM parameter GSM specification L_RXQUAL_DL_H 5.08 - Appendix A - Table 1

6-468

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

l_rxqual_dl_h_hopping_amr_fr

Description
The l_rxqual_dl_h_hopping_amr_fr parameter specifies the handover control threshold for the lower Received (Rx) quality downlink, for hopping calls only. This threshold is checked to determine if a handover condition exists.

NOTE
This threshold is enabled and set to be used for hopping calls with the chg_cell_element command and the hop_qual_enabled parameter.

Type Supported by OMC-R GUI Cell description required Dependencies

A (no operator actions) Yes Yes The AMR feature must be unrestricted. This parameter can be changed only at an AMR-capable BTS site. This parameter is prompted when alt_qual_proc is changed.

Syntax
Add/Change command strings
chg_element l_rxqual_dl_h_hopping_amr_fr <value> <location> <cell_desc> chg_cell_element l_rxqual_dl_h_hopping_amr_fr <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full] disp_element l_rxqual_dl_h_hopping_amr_fr <location> <cell_desc>

68P02901W23-S

6-469 Nov 2009

Values

Chapter 6: CM database parameters

Values
Value type Valid range Integer 0 to 1810 0 to 7 Default value 0 0 BER (1 step = 0.01% bit error rate) if alt_qual_proc = 0 QBand units if alt_qual_proc = 1 0 BER if alt_qual_proc = 0 0 QBand units if alt_qual_proc = 1

6-470

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

l_rxqual_dl_h_hopping_hr

Description
The l_rxqual_dl_h_hopping_hr parameter specifies the handover control threshold for the lower Received (Rx) quality downlink, for hopping calls only. This threshold is checked to determine if a handover condition exists.

NOTE
This threshold is enabled and set to be used for hopping calls with the chg_cell_element command and the hop_qual_enabled parameter.

Type Supported by OMC-R GUI Cell description required Dependencies

A (no operator actions) Yes Yes The AMR feature and/or the GSM Half Rate feature must be unrestricted. This parameter can be changed [22064] at any AMR/GSM HR capable BTS site. This parameter is prompted when alt_qual_proc is changed.

Syntax
Add/Change command strings
chg_element l_rxqual_dl_h_hopping_hr <value> <location> <cell_desc> chg_cell_element l_rxqual_dl_h_hopping_hr <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> full disp_element l_rxqual_dl_h_hopping_hr <location> <cell_desc>

68P02901W23-S

6-471 Nov 2009

Values

Chapter 6: CM database parameters

Values
Value type Valid range Integer 0 to 1810 0 to 7 Default value 113 3 BER (1 step = 0.01% bit error rate) if alt_qual_proc = 0 QBand units if alt_qual_proc = 1 BER if alt_qual_proc = 0 QBand units if alt_qual_proc = 1

6-472

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

l_rxqual_dl_h_hr

Description
The l_rxqual_dl_h_hr parameter specifies the handover control threshold for the half-rate lower received quality (rxqual) downlink. This threshold is checked to determine if a handover condition exists. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes The AMR feature and/or the GSM Half Rate feature must be unrestricted. This parameter can be changed [22064] at any AMR/GSM HR capable BTS site. This parameter is prompted when alt_qual_proc is changed.

Syntax
Add/Change command strings
chg_element l_rxqual_dl_h_hr <value> <location> <cell_desc> chg_cell_element l_rxqual_dl_h_hr <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> full disp_element l_rxqual_dl_h_hr <location> <cell_desc>

68P02901W23-S

6-473 Nov 2009

l_rxqual_dl_p

Chapter 6: CM database parameters

l_rxqual_dl_p

Description
The l_rxqual_dl_p parameter specifies the lower downlink limit for the signal quality of the serving cell. This threshold is checked to determine if BTS power should be increased. Receive quality processing is measured using Bit Error Rate (BER) values or Quality Band (QBand) units. The alt_qual_proc parameter specifies the type of unit. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes alt_qual_proc Must be greater than u_rxqual_dl_p See also data_qual_enabled, hop_qual_enabled

Syntax
Add/Change command strings
add_cell <gsm_cell_id> <location> chg_element l_rxqual_dl_p <value> <location> <cell_desc> chg_cell_element l_rxqual_dl_p <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full] disp_element l_rxqual_dl_p <location> <cell_desc>

6-474

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Values

Values
Value type Valid range Integer 0 to 1810 0 to 7 Default value 256 4 BER (1 step = 0.01% bit error rate) If alt_qual_proc = 0 QBand units If alt_qual_proc = 1 256 BER if alt_qual_proc = 0 4 QBand units if alt_qual_proc = 1

NOTE
Dependencies affect the actual range , thus range is never set to 0.

References
GSM parameter GSM specification L_RXQUAL_DL_P 5.08 - Appendix A - Table 1

68P02901W23-S

6-475 Nov 2009

l_rxqual_dl_p_amr_fr

Chapter 6: CM database parameters

l_rxqual_dl_p_amr_fr

Description
The l_rxqual_dl_p_amr_fr parameter specifies the lower downlink limit for the signal quality of the serving cell. This threshold is checked to determine if the BTS power should be increased. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes The AMR feature must be unrestricted. This parameter can be changed only at an AMR-capable BTS site. This parameter is prompted when alt_qual_proc is changed. This parameter must be greater than u_rxqual_dl_p.

Syntax
Add/Change command strings
chg_element l_rxqual_dl_p_amr_fr <value> <location> <cell_desc> chg_cell_element l_rxqual_dl_p_amr_fr <value> <cell_desc_opt>

Display command strings

Type Supported by OMC-R GUI Cell description required Dependencies

A (no operator actions) Yes Yes The AMR feature must be unrestricted. This parameter can be changed only at an AMR-capable BTS site. This parameter is prompted when alt_qual_proc is changed.

Syntax
Add/Change command strings
chg_element l_rxqual_dl_p_hopping_amr_fr <value> <location> <cell_desc> chg_cell_element l_rxqual_dl_p_hopping_amr_fr <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full] disp_element l_rxqual_dl_p_hopping_amr_fr <location> <cell_desc>

6-482

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Values

68P02901W23-S

6-483 Nov 2009

l_rxqual_dl_p_hopping_hr

Chapter 6: CM database parameters

l_rxqual_dl_p_hopping_hr

Description
The l_rxqual_dl_p_hopping_hr parameter specifies the lower downlink limit for the signal quality of the serving cell, for hopping cells only. This threshold is checked to determine if BTS power should be increased.

l_rxqual_ul_h_amr_fr

Description
The l_rxqual_ul_h_amr_fr parameter specifies the handover control threshold for the receive quality (rxqual) uplink. This threshold is checked to determine if a handover condition exists. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes The AMR feature must be unrestricted. This parameter can be changed only at an AMR-capable BTS site. This parameter is prompted when alt_qual_proc is changed.

Syntax
Add/Change command strings
chg_element l_rxqual_ul_h_amr_fr <value> <location> <cell_desc> chg_cell_element l_rxqual_ul_h_amr_fr <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full] disp_element l_rxqual_ul_h_amr_fr <location> <cell_desc>

Values
Value type Valid range Integer 0 to 1810 0 to 7 Default value 453 5 BER (1 step = 0.01% bit error rate) if alt_qual_proc = 0 QBand units if alt_qual_proc = 1 453 BER if alt_qual_proc = 0 5 QBand units if alt_qual_proc = 1

6-490

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

l_rxqual_ul_h_data

Description
The l_rxqual_ul_h_data parameter specifies the handover control threshold for the lower received quality (rxqual) uplink, for data transmissions only (for example modem-to-modem calls). This threshold is checked to determine if a handover condition exists. This threshold is enabled and set to be used when data is being transmitted, by use of the data_qual_enabled parameter in a chg_cell_element command. In this situation it is used instead of the l_rxqual_ul_h threshold value, as set in the add_cell command. Receive quality processing is measured using Bit Error Rate (BER) values or Quality Band (QBand) units. The alt_qual_proc parameter specifies the type of unit. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes alt_qual_proc

Syntax
Change command strings
chg_element l_rxqual_ul_h_data <value> <location> <cell_desc> chg_cell_element l_rxqual_ul_h_data <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full] disp_element l_rxqual_ul_h_data <location> <cell_desc>

Values
Value type Valid range Integer 0 to 1810 0 to 7 Default value 0 5 BER (1 step = 0.01% bit error rate) If alt_qual_proc = 0 QBand units If alt_qual_proc = 1 0 BER if alt_qual_proc = 0 5 QBand units if alt_qual_proc = 1

68P02901W23-S

6-491 Nov 2009

References

Chapter 6: CM database parameters

References
GSM parameter GSM specification L_RXQUAL_UL_H 5.08 - Appendix A - Table 1

6-492

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

l_rxqual_ul_h_hopping

Description
The l_rxqual_ul_h_hopping parameter specifies the handover control threshold for the lower received quality (rxqual) uplink, for hopping calls only. This threshold is checked to determine if a handover condition exists. This threshold is enabled and set to be used for hopping calls, by use of the hop_qual_enabled parameter in a chg_cell_element command. In this situation it is used instead of the l_rxqual_ul_h threshold value, as set in the add_cell command. Receive quality processing is measured using Bit Error Rate (BER) values or Quality Band (QBand) units. The alt_qual_proc parameter specifies the type of unit. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes alt_qual_proc

Syntax
Change command string
chg_element l_rxqual_ul_h_hopping <value> <location> <cell_desc> chg_cell_element l_rxqual_ul_h_hopping <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full] disp_element l_rxqual_ul_h_hopping <location> <cell_desc>

Values
Value type Valid range Integer 0 to 1810 0 to 7 Default value 0 5 BER (1 step = 0.01% bit error rate) if alt_qual_proc = 0 QBand units if alt_qual_proc = 1 0 BER if alt_qual_proc = 0 5 QBand units if alt_qual_proc = 1

68P02901W23-S

6-493 Nov 2009

References

Chapter 6: CM database parameters

References
GSM parameter GSM specification L_RXQUAL_UL_H 5.08 - Appendix A - Table 1

6-494

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

l_rxqual_ul_h_hopping_amr_fr

Description
The l_rxqual_ul_h_hopping_amr_fr parameter specifies the handover control threshold for the lower received quality (rxqual) uplink, for hopping calls only. This threshold is checked to determine if a handover condition exists.

NOTE
This threshold is enabled and set to be used for hopping calls with the chg_cell_element command and the hop_qual_enabled parameter.

Type Supported by OMC-R GUI Cell description required Dependencies

A (no operator actions) Yes Yes The AMR feature must be unrestricted. This parameter can be changed only at an AMR-capable BTS site. This parameter is prompted when alt_qual_proc is changed.

Syntax
Add/Change command strings
chg_element l_rxqual_ul_h_hopping_amr_fr <value> <location> <cell_desc> chg_cell_element l_rxqual_ul_h_hopping_amr_fr <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full] disp_element l_rxqual_ul_h_hopping_amr_fr <location> <cell_desc>

68P02901W23-S

6-495 Nov 2009

Values

Chapter 6: CM database parameters

6-496

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

l_rxqual_ul_h_hopping_hr

Description
The l_rxqual_ul_h_hopping_hr parameter specifies the handover control threshold for the lower received quality (rxqual) uplink, for hopping calls only. This threshold is checked to determine if a handover condition exists.

NOTE
This threshold is enabled and set to be used for hopping calls with the chg_cell_element command and the hop_qual_enabled parameter.

Type Supported by OMC-R GUI Cell description required Dependencies

A (no operator actions) Yes Yes The AMR feature and/or the GSM Half Rate feature must be unrestricted. This parameter can be changed at [22064] any AMR/GSM HR capable BTS site. This parameter is prompted when alt_qual_proc is changed.

Syntax
Add/Change command strings
chg_element l_rxqual_ul_h_hopping_hr <value> <location> <cell_desc> chg_cell_element l_rxqual_ul_h_hopping_hr <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> full disp_element l_rxqual_ul_h_hopping_hr <location> <cell_desc>

68P02901W23-S

6-497 Nov 2009

Values

Chapter 6: CM database parameters

6-498

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

l_rxqual_ul_h_hr

Description
The l_rxqual_ul_h_hr parameter specifies the handover control threshold for the lower Received (Rx) quality uplink. This threshold is checked to determine if a handover condition exists. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes The AMR feature and/or the GSM Half Rate feature must be unrestricted. This parameter can be changed [22064] at any AMR/GSM HR capable BTS site. This parameter is prompted when alt_qual_proc is changed.

Syntax
Add/Change command strings
chg_element l_rxqual_ul_h_hr <value> <location> <cell_desc> chg_cell_element l_rxqual_ul_h_hr <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> full disp_element l_rxqual_ul_h_hr <location> <cell_desc>

68P02901W23-S

6-499 Nov 2009

l_rxqual_ul_p

Chapter 6: CM database parameters

l_rxqual_ul_p

Description
The l_rxqual_ul_p parameter specifies the lower uplink limit of the signal quality of the MS. Check this threshold to determine if increase in MS power is required. Receive quality processing is measured using Bit Error Rate (BER) values or Quality Band (QBand) units. The alt_qual_proc parameter specifies the type of unit. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes alt_qual_proc Must be greater than u_rxqual_ul_p See also data_qual_enabled, hop_qual_enabled

Syntax
Add/Change command strings
add_cell <gsm_cell_id> <location> chg_cell_element l_rxqual_ul_p <value> <cell_desc> chg_element l_rxqual_ul_p <value> <location> <cell_desc>

Display command strings

disp_cell <cell_id> [full] disp_element l_rxqual_ul_p <location> <cell_desc>

6-500

68P02901W23-S Nov 2009

Display command strings

disp_cell <cell_id> [full] disp_element l_rxqual_ul_p_hopping_amr_fr <location> <cell_desc>

6-508

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Values

68P02901W23-S

6-509 Nov 2009

l_rxqual_ul_p_hopping_hr

Chapter 6: CM database parameters

l_rxqual_ul_p_hopping_hr

Description
The l_rxqual_ul_p_hopping_hr parameter specifies the lower uplink limit for the signal quality of the serving cell, for hopping calls only. This threshold is checked to determine if BTS power should be increased.

NOTE
This threshold is enabled and set to be used for hopping calls with the chg_cell_element command and the hop_qual_enabled parameter.

Type Supported by OMC-R GUI Cell description required Dependencies

Syntax
Add/Change command strings
chg_element l_rxqual_ul_p_hopping_hr <value> <location> <cell_desc> chg_cell_element l_rxqual_ul_p_hopping_hr <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> full

6-510

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Values

68P02901W23-S

6-511 Nov 2009

l_rxqual_ul_p_hr

Chapter 6: CM database parameters

l_rxqual_ul_p_hr

Description
The l_rxqual_ul_p_hr parameter specifies the lower uplink limit of the signal quality of the MS. Check this threshold to determine if increase in MS power is required. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes The AMR feature and/or the GSM Half Rate feature must be unrestricted. This parameter can be changed [22064] at any AMR/GSM HR capable BTS site. This parameter is prompted for when alt_qual_proc is changed. This parameter must be greater than u_rxqual_ul_p_hr.

Syntax
Add/Change command strings
chg_element l_rxqual_ul_p_hr <value> <location> <cell_desc> chg_cell_element l_rxqual_ul_p_hr <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> full disp_element l_rxqual_ul_p_hr <location> <cell_desc>

6-512

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Values

NOTE
Dependencies affect the actual range, thus range is never set to 0.

68P02901W23-S

6-513 Nov 2009

land_layer1_mode

Chapter 6: CM database parameters

land_layer1_mode

Description
The land_layer1_mode parameter specifies the layer 1 mode of the land network TELCO connection type. Only the 2.048 Mbit/s - CEPT format is currently supported. All BTS site values are set to the BSC value. This parameter may be set only while in the initial SYSGEN mode. All BTS site values are set to BSC (site 0) value when the database is loaded initially. Type Supported by OMC-R GUI Cell description required Dependencies B (operator actions required) Yes No The value of this parameter may be specified for the BSC (site 0) only while in the initial SYSGEN mode. The value of this parameter may not be changed if any MSIs or BTS sites are equipped. If the GPRS feature is unrestricted and a PCU is equipped, this parameter must be set to 0 (E1). Place the system in the initial SYSGEN ON mode and clear the database before using the chg_element command to change this parameter.

Operator actions

Syntax
Change command string
chg_element land_layer1_mode <value> <location>

Display command string

disp_element land_layer1_mode <location>

Values
Value type Valid range Boolean 0 or 1 0 Default value 0 2.048 Mbit/s - CEPT format (E1)

6-514

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

layer_number

Description
The layer_number parameter specifies the serving cell as being a macrocell, microcell, or picocell. When an RXQUAL handover condition exists, the system attempts to hand over a call in the microcell layer to another cell in the microcell layer. This parameter specifies the layer for a cell. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes This parameter is unavailable if the Microcellular option has not been purchased.

Syntax
Change command strings
chg_element layer_number <value> <location> <cell_desc> chg_cell_element layer_number <value> <cell_desc_opt>

Display command string

disp_element layer_number <location> <cell_desc>

Values
Value type Valid range Integer 0 to 2 0 1 2 Default value 0 Macrocell Microcell Picocell

68P02901W23-S

6-515 Nov 2009

lb_int_called_pci

Chapter 6: CM database parameters

lb_int_called_pci

Description
The lb_int_called_pci (Lb-interface PC included called party) flag specifies if the point code is included in the called party address in the SCCP messages that travel over the Lb-interface. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No The Location Services feature must be unrestricted.

Syntax
Change command string
chg_element lb_int_called_pci <value> <location>

Display command string

disp_element lb_int_called_pci <location>

Values
Value type Valid range Boolean 0 or 1 0 1 Default value None DCP not included DCP included

6-516

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

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 Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No The Location Services feature must be unrestricted.

Syntax
Change command string
chg_element lb_int_calling_pci <value> <location>

Display command string

disp_element lb_int_calling_pci <location>

Values
Value type Valid range Boolean 0 or 1 0 1 Default value None Point code not included Point code included

68P02901W23-S

6-517 Nov 2009

lb_int_cr_calling

Chapter 6: CM database parameters

lb_int_cr_calling

Description
The lb_int_cr_calling parameter specifies if the calling party address is included in the SCCP connection request messages that travel over the Lb-interface. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No The Location Services feature must be unrestricted.

Syntax
Change command string
chg_element lb_int_cr_calling <value> <location>

Display command string

disp_element lb_int_cr_calling <location>

Values
Value type Valid range Boolean (milliseconds) 0 or 1 0 1 Default value 0 Not included Included

6-518

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

lb_int_dpc

Description
The lb_int_dpc (Lb-interface DPC) is the point code of a BSS-based SMLC. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No The Location Services feature must be unrestricted. For a live system, the lb_int_dpc must not be the same value as the opc. For the ss7_mode element to be modified from ANSI to CCITT, the lb_int_dpc parameter must be within range for the CCITT ss7_mode setting. The valid values for this element are dependent upon the value of the ss7_mode element.

Syntax
Change command string
chg_element lb_int_dpc <value> <location>

Display command string

disp_element lb_int_dpc <location>

Values
Value type Valid range Default value Integer ss7_mode = 0: 0 to 16383 ss7_mode = 1: 0 to 16777215 None

68P02901W23-S

6-519 Nov 2009

lb_int_global_reset_repetitions

Chapter 6: CM database parameters

lb_int_global_reset_repetitions

Description
The lb_int_global_reset_repetitions parameter specifies the number of times the global reset procedure on the Lb-interface is allowed to repeat before an alarm is generated. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No The Location Services feature must be unrestricted.

Syntax
Change command string
chg_element lb_int_global_reset_repetitions <value> <location>

Display command string

disp_element lb_int_global_reset_repetitions <location>

Values
Value type Valid range Default value Integer 0 to 255 0

References
GSM specification TS GSM 8.08

6-520

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

lcs_mode

Description
The lcs_mode parameter specifies the Location Services mode of the BSS.

NOTE
This parameter can be modified only when the system is in the SYSGEN ON mode.

Type Supported by OMC-R GUI Cell description required Dependencies

A (no operator actions) Yes No See Dependencies checked during database verification list and Dependencies checked during lcs_mode modification list for the dependencies of this parameter.

Dependencies checked during database verification If database verification determines that the location services feature is enabled and early_classmark_sending is not enabled across both the A-interface and the Air-interface, the database is not created, and the following error message is displayed: ERROR: LCS requires early_classmark_sending to be enabled across both the A and Air Interfaces. Errors were found in the database. REJECTING SYSGEN_OFF REQUEST. If database verification determines that the location services feature is enabled and phase2_classmark_allowed is not configured to support multiband, the database is not created, and the following error message is displayed: ERROR: LCS requires phase2_classmark_allowed to be configured to support multiband. Errors were found in the database. REJECTING SYSGEN_OFF REQUEST.

68P02901W23-S

6-521 Nov 2009

Description

Chapter 6: CM database parameters

If database verification determines that the BSS is not configured to support a BSS-based SMLC and one or more LMTL devices are equipped, the database is not created, and the following error message is displayed: ERROR: For setups with no BSS-based SMLC support, LMTLs cannot exist and LCFs cannot manage LMTLs. Errors were found in the database. REJECTING SYSGEN_OFF REQUEST.

If database verification determines that the BSS is not configured to support a BSS-based SMLC and one or more LCFs are configured to manage LMTL devices, the database is not created, and the following error message is displayed: ERROR: For setups with no BSS based SMLC support, LMTLs cannot exist and LCFs cannot manage LMTLs. Errors were found in the database. REJECTING SYSGEN_OFF REQUEST.

If database verification determines that the location services feature is restricted and the LCS mode element indicates that the location services feature is enabled, the database is not created, and the following error message is displayed: ERROR: When LCS is restricted lcs_mode must be 0. Errors were found in the database. REJECTING SYSGEN_OFF REQUEST.

Dependencies checked during lcs_mode modification

6-522

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Syntax

If the operator attempts to change the LCS mode element from a BSS-based SMLC configuration to either an NSS-based SMLC configuration or an LCS-disabled configuration, and one or more LMTLs are equipped, the command is rejected, and the following error message is displayed: ERROR: For setups with no BSS-based SMLC support, LMTLs cannot exist and LCFs cannot manage LMTLs. COMMAND REJECTED

If an operator attempts to change the LCS mode element from a BSS-based SMLC configuration to either an NSS-based SMLC configuration or an LCS disabled configuration, and one or more LCFs are configured to manage LMTLs, the command is rejected, and the following error message is displayed: ERROR: For setups with no BSS-based SMLC support, LMTLs cannot exist and LCFs cannot manage LMTLs. COMMAND REJECTED

If an operator attempts to change the LCS mode element to an LCS enabled setting, 1 or 2, and the location services feature is restricted, the command is rejected, and the following message is displayed: ERROR: When LCS is restricted lcs_mode must be 0. COMMAND REJECTED

Syntax
Change command string
chg_element lcs_mode <value> <location>

Display command string

disp_element lcs_mode <location>

Values
Value type Valid range Integer 0 1 2 Default value 0 Location services disabled; SMLC not supported. Location services enabled; BSC supports an NSS-based SMLC. Location services enabled; BSC supports an BSS-based SMLC.

68P02901W23-S

6-523 Nov 2009

link_about_to_fail

Chapter 6: CM database parameters

link_about_to_fail

Description
The link_about_to_fail parameter specifies the number of undecoded SACCH frames before the BSS and MS are increased to full power. The number of SACCH frames is calculated by subtracting the number of undecoded SACCH frames represented by the value entered for this parameter from the number of undecoded SACCH frames represented by the link_fail parameter. For example, if link_fail is set to 5 (24 SACCH frames) and link_about_to_fail is set to 1 (4 SACCH frames), the BSS and MS are increased to full power when 20 undecoded SACCH frames are received. Full power is specified by the max_tx_bts parameter for the downlink power; and max_tx_ms or max power capability of the MS for uplink power. This provides a method for improving the quality of a call by increasing the power of the signal transmitted by the BSS to an MS. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes link_about_to_fail must be less than link_fail

Syntax
Change command strings
chg_element link_about_to_fail <value> <location> <cell_desc> chg_cell_element link_about_to_fail <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full] disp_element link_about_to_fail <location> <cell_desc>

6-524

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Values

Values
Value type Valid range Integer (1 step = 4 SACCH frames) 0 to 15 0 1 2 ... ... ... 15 Default value 2 Represents the number of SACCH frames as shown below: 0 SACCH frames 4 SACCH frames 8 SACCH frames ... ... ... 60 SACCH frames

References
Internal name THRES_PC_RLF This is a Motorola defined parameter.

68P02901W23-S

6-525 Nov 2009

link_fail

Chapter 6: CM database parameters

link_fail

Description
The link_fail parameter specifies the number of lost SACCH multiframes before a loss of SACCH is reported to Abis. This parameter is also known as the T100_TIMER. The radio link failure criterion is based on the radio link counter S. S is set to the value specified for link_fail. If the BSS is unable to decode a SACCH message, the count in S is decremented by 1. When the BSS successfully decodes a SACCH message, the count in S is incremented by 2 up to the value of the link_fail parameter. A radio link failure occurs when S equals 0. The BSS continues transmitting on the downlink until S reaches 0. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes link_fail must be greater than or equal to link_about_to_fail

Syntax
Change command strings
chg_element link_fail <value> <location> <cell_desc> chg_cell_element link_fail <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full] disp_element link_fail <location> <cell_desc>

6-526

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Values

Values
Value type Valid range Integer (1 step = 4 SACCH multiframes) 0 to 15 0 1 2 ... ... ... 15 Default value Represents the number of SACCH multiframes as shown below: 4 SACCH frames 8 SACCH frames 12 SACCH frames ... ... ... 64 SACCH frames

4 (20 SACCH frames)

References
Internal name RADIO_LINK_TIMEOUT(BS) This is a Motorola defined parameter.

68P02901W23-S

6-527 Nov 2009

lmtl_loadshare_granularity

Chapter 6: CM database parameters

lmtl_loadshare_granularity

Description
The lmtl_loadshare_granularity parameter specifies the level of granularity for LMTL load sharing. Type Supported by OMC-R GUI Cell description required Dependencies B (operator actions required) Yes No If this parameter is modified outside SYSGEN mode, all LMTLs must be in the locked state in order for the modification to take effect. This parameter cannot be modified or displayed at a RXCDR site. Set element state

Operator actions

Syntax
Change command string
chg_element lmtl_loadshare_granularity <value> <location>

Display command string

disp_element lmtl_loadshare_granularity <location>

Values
Value type Valid range Integer 0 1 Default value 0 Corresponds to granularity of 16. Corresponds to granularity of 64.

6-528

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

local_maintenance

Description
The local_maintenance parameter specifies whether database elements that can be configured through the OMC-R interface, can be modified from a local maintenance terminal or from a rlogin. This is used to synchronize the database in the BSS and the data modeled in the OMC-R MIB. When this parameter is disabled, the BSS blocks attempts to modify database elements that are configurable through the OMC-R interface at a local maintenance terminal or from a rlogin. When this parameter is enabled, the BSS allows modification of database elements that are configurable through the OMC-R interface at a local maintenance terminal or from a rlogin. The local_maintenance parameter is also used to determine whether BSS commands supported through the OMC-R interface may be entered from a local maintenance terminal or from a rlogin. {31400} If the local_maintenance flag is disabled, the MMI is prevented from creating, modifying or deleting the TD-SCDMA neighbor. The OMC-R GUI supports the following commands or functionalities and may be entered from the local maintenance terminal or rlogin regardless of the value of the local_maintenance parameter: cage_audit chg_dte chg_throttle configure_csfp copy_cell device_audit disp_a5_alg_pr disp_cbch_state disp_cell disp_cell_status disp_csfp disp_csfp_status disp_dte disp_element disp_enable_stat disp_equipment disp_flash disp_hdlc disp_hopping disp_level disp_neighbor disp_options disp_processor disp_rcu_id disp_rtf_path disp_rxcdr_gbu disp_throttle disp_version disp_xbl_options ins_device lock_device query_audits reassign reset_device reset_site shutdown_device site_audit soft_reset state status_mode swap_devices unlock_device

68P02901W23-S

6-529 Nov 2009

Description

Chapter 6: CM database parameters

The OMC-R GUI supports the following commands or functionalities and may not be entered from the local maintenance terminal or a rlogin when the local_maintenance parameter is set to 0: add_cell add_neighbor add_rtf_path add_conn cell_name chg_a5_alg_pr chg_acs_params chg_audit_sched chg_cell_element chg_cell_id The OMC-R GUI does not support the following commands or functionalities and may be entered from the local maintenance terminal or rlogin regardless of the value of the local_maintenance parameter: add_channel add_rxcdr_link alias chg_level chg_time chg_ts_usage clear_cal_data clear_database clear_gclk_avgs del_act_alarm del_channel del_link disable_alarm disp_act_alarm disp_alarm_sites disp_bss disp_cal_data disp_channel disp_gclk_avgs disp_gclk_cal disp_gsm_cells disp_level disp_link_usage disp_links disp_mms_ts_usage disp_mobile_optimize disp_rtf_calls disp_rtf_channel disp_site disp_throttle disp_trace_call disp_traffic enable_alarm gclk_cal_mode help history man reattempt_pl set_full_power store_cal_data swfm_enable sysgen_mode time_stamp trace_call unalias chg_csfp chg_eas_alarm chg_element chg_hop_params chg_ksw_config chg_rtf_freq chg_smscb_msg copy_cell copy_path del_cell del_neighbor del_rtf_path del_smscb_msg del_conn equip modify_neighbor modify_value unequip

Type Supported by OMC-R GUI Cell description required Dependencies Operator actions

B (operator actions required) Yes No None Place the system in the SYSGEN ON mode before using the chg_element command to change this parameter.

6-530

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Syntax

Syntax
Change command string
chg_element local_maintenance <value> <location>

Display command string

disp_element local_maintenance <location>

Values
Value type Valid range Boolean 0 or 1 0 1 Default value 1 Disabled Enabled

68P02901W23-S

6-531 Nov 2009

low_sig_thresh

Chapter 6: CM database parameters

low_sig_thresh

Description
The low_sig_thresh parameter specifies the minimum receive level for redirected handovers. When a call, using a MultiBand MS, is on any cell, and a handover is triggered to a cell with a coincident cell, the handover takes place to the coincident cell, if the measured receive level from the target cell exceeds this parameter value. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes None

Syntax
Change command strings
chg_element low_sig_thresh <value> <location> <cell_desc> chg_cell_element low_sig_thresh <value> <cell_desc_opt>

Display command string

disp_element low_sig_thresh <location> <cell_desc>

Values
Value type Valid range Default value Integer 0 to 63 0

6-532

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

lta_alarm_range

Description
The lta_alarm_range parameter specifies the alarm range on the allowed Long Term Average (LTA) variation. Temperature changes can cause the frequency generated by the VCXO (Voltage Controlled Crystal Oscillator) to vary. The default range (7) is sufficient to compensate for normal day to day variations in temperature. This value should not be changed unless it is known that the MMS or uplink clock is faulty. The LTA is a rolling average of the values read from the clock frequency register (CLKFREQ) of each GCLK once every half hour after synchronization if the GCLK is phase locked. Up to 48 clock frequency readings are stored. These stored readings are used to calculate the LTA. An alarm is generated if 25% or more of the stored readings differ from the calculated LTA by more than the value that is specified by the lta_alarm_range parameter. The CLKFREQ register is used to maintain the correct frequency generated by the VCXO (Voltage Controlled Crystal Oscillator). The register center value is 80 h. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No This parameter is not valid at an M-Cell site.

Syntax
Change command string
chg_element lta_alarm_range <value> <location>

Display command string

disp_element lta_alarm_range <location>

Values
Value type Valid range Default value Integer 1 to 255 7

68P02901W23-S

6-533 Nov 2009

max_gprs_ts_per_carrier

Chapter 6: CM database parameters

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 Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes The GPRS feature must be unrestricted and the gprs_ts_config_alg must be set to 1. Enough timeslots must be available on all of the GPRS cell carriers.

NOTE
When an attempt is made to change max_gprs_ts_per_carrier and the requested PDTCHs exceed the GDS or PMC capacity on the PCU, the BSS accepts the request and issues a warning to indicate that there is not enough GDS or PMC resource available.

Syntax
Change command strings
chg_element max_gprs_ts_per_carrier <value> <location> <cell_desc> chg_cell_element max_gprs_ts_per_carrier <value> <cell_desc_opt>

Display command string

disp_element max_gprs_ts_per_carrier <location> <cell_desc>

6-534

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Values

Values
Value type Valid range Default value Integer 1 to 8 8

68P02901W23-S

6-535 Nov 2009

max_ms_dl_buffer

Chapter 6: 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. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes The GPRS feature must be unrestricted.

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

Syntax
Change command strings
chg_element max_ms_dl_buffer <value> <location> <cell_desc> chg_cell_element max_ms_dl_buffer <value> <cell_desc_opt>

Display command string

disp_element max_ms_dl_buffer <location> [<cell_desc>]

6-536

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Values

Values
Value type Valid range Integer 5120 to 64000 5120 ... ... ... 64000 Default value 38400 bytes bytes ... ... ... bytes (bytes.)

68P02901W23-S

6-537 Nov 2009

max_ms_dl_rate

Chapter 6: 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. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes The GPRS feature must be unrestricted.

Syntax
Change command strings
chg_element max_ms_dl_rate <value> <location> <cell_desc> chg_cell_element max_ms_dl_rate <value> <cell_desc_opt>

Display command string

disp_element max_ms_dl_rate <location> <cell_desc>

Values
Value type Valid range Default value Integer (100 bits per second) 1 to 900 900 (equivalent to 90000 bits per second)

NOTE
The units for this parameter are 100 bits per second. The equivalent range in bits per second is 100 to 90000.

6-538

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

max_number_of_sdcchs

Description
The max_number_of_sdcchs parameter specifies the maximum number (limit) of SDCCHs that may be reached with the reconfiguration process. It determines the maximum limit of the SDCCHs that the CRM maintains. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes For combined channel configurations, the values can be 12, 20, 28 SDs. For non-combined channel configurations, the values can be 16, 24, 32 SDs. Valid values for this parameter depend on the value of ccch_conf.

Syntax
Change command string
chg_element max_number_of_sdcchs <value> <location> <cell_desc>

Display command strings

disp_cell <cell_id> [full]

68P02901W23-S

6-539 Nov 2009

Values

Chapter 6: CM database parameters

Values
Value type Valid range Integer If feature SDCCH increase is unrestricted, then 12 to 124 16 to 128 If ccch_conf = 1. If ccch_conf = 0.

If feature SDCCH increase is restricted, then 12 to 44 16 to 48 Default value None If ccch_conf = 1. If ccch_conf = 0.

References
GSM specification 5.02 - 6.4 This is a Motorola defined parameter.

6-540

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

max_pagenum_per_sec

Description
The max_pagenum_per_sec parameter defines the maximum number of Page messages from the BSC to each BTS allowed in one second. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No None

Syntax
Add/Change command strings
chg_element max_pagenum_per_sec <value> bsc

Display command strings

disp_element max_pagenum_per_sec bsc

Values
Value type Valid range Default value Integer (number of Page messages) 70 to 65535 65535

68P02901W23-S

6-541 Nov 2009

max_q_length_channel

Chapter 6: CM database parameters

max_q_length_channel

Description
The max_q_length_channel parameter specifies the maximum number of MSs that may wait in queue for a full rate channel assignment. If an idle traffic channel is not available at the channel assignment instant, the network may place the traffic channel request in queue. If the queue length is 0, queuing is not allowed. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes The sum of max_q_length_channel and max_q_length_sdcch must be less than or equal to queue_management_information.

Syntax
Change command strings
chg_element max_q_length_channel <value> <location> <cell_desc> chg_cell_element max_q_length_channel <value> <cell_desc_opt>

Display command string

disp_element max_q_length_channel <location> <cell_desc>

6-542

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Values

Values
Value type Valid range Default value Integer (representing the number of MSs in the queue) 0 to 50 0

References
GSM specification 4.08 - 5.2.1.1.10 3.01: conditions to apply call queuing This is a Motorola defined parameter.

68P02901W23-S

6-543 Nov 2009

max_q_length_sdcch

Chapter 6: CM database parameters

max_q_length_sdcch

Description
The max_q_length_sdcch parameter specifies the maximum length of the queue for Stand-alone Dedicated Control Channel (SDCCH) requests. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes The sum of max_q_length_channel and max_q_length_sdcch must be less than or equal to queue_management_information.

Syntax
Change command string
chg_element max_q_length_sdcch <value> <location> <cell_desc> chg_cell_element max_q_length_sdcch <value> <cell_desc_opt>

Display command string

disp_element max_q_length_sdcch <location> <cell_desc>

Values
Value type Valid range Default value Integer (represents the number of requests) 0 to 50 None

6-544

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

max_retran

Description
The max_retran parameter specifies the maximum channel request retransmission value for MSs. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes None

Syntax
Add/Change command strings
add_cell <gsm_cell_id> <location> chg_element max_retran <value> <location> <cell_desc> chg_cell_element max_retran <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full] disp_element max_retran <location> <cell_desc>

Values
Value type Valid range Integer 0 to 3 0 1 2 3 Default value 0 Maximum [1] retransmission Maximum [2] retransmissions Maximum [4] retransmissions Maximum [7] retransmissions

68P02901W23-S

6-545 Nov 2009

References

Chapter 6: CM database parameters

References
GSM parameter GSM specification MAX_RETRANS 4.08 - 3.3.1.1: request for resources by the MS 4.08 - 10.5.2.17, fig. 10.36, table 10.30 5.08 - 6.6.2: cell reselection 12.20 - 5.2.8.7 cell Description - max Number Retransmission

6-546

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

max_rst_ckt_timer_exps

Description
The max_rst_ckt_timer_exps parameter specifies the number of times that the Reset Circuit message is repeated if there is no answer from the MSC. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No This parameter only applies to the BSC.

Syntax
Change command string
chg_element max_rst_ckt_timer_exps <value> 0

Display command string

disp_element max_rst_ckt_timer_exps 0

Values
Value type Valid range Integer (represents the number of repeats) 0 to 100 The value 0 means the system keeps sending the Reset Circuit message indefinitely. Default value 1

68P02901W23-S

6-547 Nov 2009

max_tx_bts

Chapter 6: CM database parameters

max_tx_bts

Description
The max_tx_bts parameter specifies the maximum output power for a cell in 2 dB steps of attenuation from the calibrated cell site power of the radios in the cell. For macro BTS platforms, max_tx_bts supports a range of 23 steps of 2 dB giving a range of 46 dB. For micro BTS platforms, max_tx_bts supports a range of 7 steps giving a range of 14 dB.

NOTE
The true transmit power of the cell is dependent on the value of the cell site power selected for the cell with the max_tx_bts parameter. For example: Consider an EGSM 900 cell calibrated for 20 Watts (43 dBm) at the top of the cabinet with max_tx_bts equal to 2 (4 dB of attenuation). Calibrated power at the top of the cabinet = 43 dBm Attenuation applied by max_tx_bts = 4 dB Actual cell maximum output power = 43 dBm - 4 dB = 39 dBm (8 Watts) Consider an EGSM 900 cell calibrated for 40 W (46 dBm) at the top of the cabinet with max_tx_bts equal to 3 (6 dB of attenuation). This would be equivalent to a CTU using a TDF RF block or a CTU2 in single density mode. Calibrated power at the top of the cabinet = 46 dBm Attenuation applied by max_tx_bts = 6 dB Actual cell maximum output power = 40 dBm - 6 dB = 40 dBm (10 Watts) Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes frequency_type

6-548

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Syntax

Syntax
Change command strings
chg_element max_tx_bts <value> <location> <cell_desc> chg_cell_element max_tx_bts <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full] disp_element max_tx_bts <location> <cell_desc>

Values
Value type Valid range Default value Integer (1 step = 2 dBm) -1 to 21 0 to 6 None For PGSM, EGSM, and DCS1800. For M-Cellmicro, M-Cellaccess and Horizoncompact.

NOTE
Refer to Table 6-22, Table 6-23, and Table 6-24 for additional information about the values for this parameter. Table 6-22 lists the values used in the BSS software for the CTU2 when using this parameter for the purposes of calculating path balance. The values assumed represent the calibrated output power at the top of the cabinet with one stage of combining as this is the most common configuration.

NOTE
The true actual power of the cell is dependent on the physical combining used and the calibrated cell site power. Care should be taken when evaluating path balance results for non standard cell combining configurations. The CTU2 values for 900 MHz represent the calibrated output power after reducing the combining loss of 3 dB due to single stage of combining. The BSS software always assumes a single stage of combining even when there is no combining physically present. For example, for the valid input -1 for 900 MHz, the calibrated output power with one stage of combining = 48 dBm - 3 dB = 45 dBm. This assumes that the single density CTU2 will be combined externally with another radio therefore bringing the actual top of the cabinet output power down by 3 dB.

68P02901W23-S

6-549 Nov 2009

Values

Chapter 6: CM database parameters

Table 6-22

CTU2 values
1800 Mhz 44 dBm 42 dBm 40 dBm 38 dBm 36 dBm 34 dBm 32 dBm 30 dBm 28 dBm 26 dBm 24 dBm 22 dBm 20 dBm 18 dBm 16 dBm 14 dBm 12 dBm 10 dBm 8 dBm 6 dBm 4 dBm 2 dBm 0 dBm 900 Mhz 45 dBm 43 dBm 41 dBm 39 dBm 37 dBm 35 dBm 33 dBm 31 dBm 29 dBm 27 dBm 25 dBm 23 dBm 21 dBm 19 dBm 17 dBm 15 dBm 13 dBm 11 dBm 9 dBm 7 dBm 5 dBm 3 dBm 1 dBm

Valid Input -1 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21

NOTE
Value -1 is only valid for single density CTU2 DRI. Table 6-23 identifies the transmit power capabilities of the different XCVR types in specific frequency bands and cabinet types. The power specified is the cabinet antenna connector maximum output power. All figures are 2 dB.

6-550

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Values

Table 6-23 also specifies the types of combing used: none, external, internal, and both internal and external. The combining types are defined as follows: None: The output power of the XCVR is connected directly to the antenna. This is not applicable for a DDM as it always uses a single stage of internal combining within the XCVR itself. External (to the XCVR): The output of the XCVR is connected through a single stage of external hybrid combining to the antenna. For example, a two-carrier sector is required from two SDX or two CTU2-SD. Internal (to the XCVR): When a CTU2 is configured in Double Density mode the two outputs from the two XCVR devices on the CTU2 are combined before leaving the XCVR. Hence the power figure internal combining represents two carriers at this transmit power for a CTU2 in DD-DCM. Ensure that the internal combining is still present when the CTU2 is used in DD-SCM. Internal and external: External hybrid combining is used on a CTU2 in DDM. For example, this allows two CTU2 in DD-DCM to be combined to create a four-carrier sector.

Table 6-23
XCVR Type CTU

Cabinet antenna connector maximum output power (Watts)

Combining None External Horizonmacro EGSM900 40 20 40 20 10 4.5 DCS1800 32 16 32 16 10 4.5 Horizon II macro EGSM900 N/A N/A 63 28 20 9 DCS1800 N/A N/A 50 22 16 7

CTU2 SD-SCM CTU2 DD-DCM

None External Internal Internal and external

Table 6-24 lists the values for PGSM, EGSM, DCS1800 and PCS1900 M-Cellmicro, M-Cellcity, Horizonmicro (M-Cellarena) and Horizoncompact (M-Cellarenamacro) sites.

Table 6-24
Valid Input 0 1 2 3 4 5 6

Values for PGSM, EGSM, DCS1800 and PCS1900 sites

PGSM and EGSM M-Cellmicro values 31 dBm 29 dBm 27 dBm 25 dBm 23 dBm 21 dBm 19 dBm DCS1800 and PCS1900 M-Cellmicro values 30 dBm 28 dBm 26 dBm 24 dBm 22 dBm 20 dBm 18 dBm Horizoncompact (M-Cellarenamacro) values 40 dBm 38 dBm 36 dBm 34 dBm 32 dBm 30 dBm 28 dBm

68P02901W23-S

6-551 Nov 2009

References

Chapter 6: CM database parameters

References
GSM parameter GSM specification BS_TXPWR_RED For MAX see GSM Rec. 5.05 - 4.1.2 Rec. 5.08-BS_TXPWR_MAX, 12.20 - 5.2.8.23 - power Ctrl BTS - BS Tx Pwr Max 12.20 - 5.2.8.2 - Tx power

6-552

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

max_tx_ms

Description
The max_tx_ms parameter specifies the maximum MS (Mobile Station) output power. Regardless of the power class of the MS, the MS is not told to use a higher output power. Select the value to balance the up and down links in a cell. This parameter is also used in the power budget calculation. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes The range and default values of ms_txpwr_max_inner depends on this parameter. If the range or default value of max_tx_ms changes, mstxpwr_max_inner must also be updated, to a value less than or equal to max_tx_ms.

Syntax
Add/Change command strings
add_cell <gsm_cell_id> <location> chg_element max_tx_ms <value> <location> <cell_desc> chg_cell_element max_tx_ms <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full] disp_element max_tx_ms <location> <cell_desc>

68P02901W23-S

6-553 Nov 2009

Values

Chapter 6: CM database parameters

Values
Value type Valid range Integer (dBm) 5 to 39 0 to 36 0 to 32,33 Default value PGSM and EGSM (Odd values only) DCS1800 (Even values only) PCS1900 (Even values only and value 33)

Highest allowed value

References
GSM parameter GSM specification MS_TXPWR_MAX 5.08 - 4.3 5.05 - 4.1

6-554

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

mb_preference

Description
The mb_preference parameter enables or disables the Multiband Inter-cell Handover feature. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No This parameter is unavailable if the Multiband Inter-Cell Handover feature is restricted. This parameter may not be disabled when inner_zone_alg is set to indicate Dual Band Cells for any cell in the BSS.

Syntax
Change command string
chg_element mb_preference <value> <location>

Display command string

disp_element mb_preference <location>

Values
Value type Valid range Boolean 0 or 1 0 1 Default value 0 Disabled Enabled

68P02901W23-S

6-555 Nov 2009

mb_tch_congest_thres

Chapter 6: CM database parameters

mb_tch_congest_thres

Description
The mb_tch_congest_thres parameter specifies the level of overall TCH utilization by any MS in a given Cell, at which a MultiBand MS is redirected to the preferred band (as set by band_preference). The parameter is expressed as a percentage. Type Supported by OMC-R GUI Cell number required Dependencies A (no operator actions) Yes Yes The parameter can be set only if the Congestion Relief feature is unrestricted (ho_exist_congest element must be enabled). mb_preference element must be enabled. band_preference_modemust be set to 6 (the mode which triggers when a Cell is congested). mb_tch_congest_thres must be less than or equal to tch_congest_prevent_thres.

Syntax
Change command string
chg_element mb_tch_congest_thres <value> <location> <cell_desc>

Display command string

disp_element mb_tch_congest_thres <location> <cell_desc>

Values
Value type Valid range Default value Integer (representing a percentage.) 1 to 101 100 The value 101 indicates there are no resources left to allocate). The value 100 indicates an attempt to use the last resource.

6-556

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

missing_rpt

Description
The missing_rpt parameter enables or disables the suspension of the storing, averaging, and processing of downlink power control and handovers. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes None

Syntax
Add/Change command strings
chg_element missing_rpt <value> <location> <cell_desc> chg_cell_element missing_rpt <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full] disp_element missing_rpt <location> <cell_desc>

Values
Value type Valid range Boolean 0 or 1 0 1 Default value None Disabled Enabled

68P02901W23-S

6-557 Nov 2009

mmi_cell_id_format

Chapter 6: CM database parameters

mmi_cell_id_format

Description
The mmi_cell_id_format parameter specifies the format that the MMI command line accepts for the GSM cell Identification number. The formats available are: 4-parameter and 7-parameter. Type Supported by OMC-R GUI Cell description required Dependencies B (operator actions required) No No The system must be in SYSGEN ON mode to modify this parameter. PCS1900 systems accept only the 4-parameter cell number format. This parameter is valid only at the BSC. Place the system in SYSGEN ON mode

Operator actions

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 Valid range Boolean 0 or 1 0 1 Default value 0 7-parameter format 4-parameter format

6-558

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

mms_cat_enable

Description
The mms_cat_enable parameter enables or disables the MMS Critical Alarm Threshold (CAT) for MMS stability testing. When mms_cat_enable is enabled, the system monitors how often an MMS goes Out Of Service (OOS) and then back into service due to an alarm (such as Synchronization Loss OOS Timer Expired) occurring and clearing in the last 10 minutes. When this happens 10 times in 10 minutes, after the tenth clear the MMS stays OOS even though the alarm is cleared, and the Critical Alarm Threshold Exceeded alarm is reported against the MMS device. This action is taken because the MMS is showing signs of instability. The system continues to monitor how many times alarms and clears have occurred in the latest 10 minute period. As soon as the number is less than 10, the MMS is brought back into service automatically, and the Critical alarm Threshold Exceeded alarm is cleared. A lock/unlock of the MMS overrides this periodic auditing and brings the MMS into service immediately. When mms_cat_enable is disabled, the MMS remains in service even if the MMS CAT is met or exceeded. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) No No None

Syntax
Change command string
chg_element mms_cat_enable <value> <location>

Display command string

disp_element mms_cat_enable <location>

68P02901W23-S

6-559 Nov 2009

Values

Chapter 6: CM database parameters

Values
Value type Valid range Boolean 0 or 1 0 1 Default value 0 Disabled Enabled

6-560

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

mms_config_type

Description
The mms_config_type parameter specifies the signaling type for all MMSs. The signaling type depends on the carrier type being used, E1. All BTS site or PCU values are set to the value assigned to the BSC (site 0) or PCU (pcu) when the database is initially loaded. Type Supported by OMC-R GUI Cell description required Dependencies B (operator actions required) Yes No The value of the land_layer1_mode parameter, where: For E1 systems (land_layer1_mode =0), the value of this parameter can be changed at any time for any site. If executed outside SYSGEN mode, a warning message saying the MMSs must be reset to have the change take effect at that site will display. The value of mms_config_type must be the same at the BSC and the PCU sites. For E1 systems, reset the MSIs for a change to this parameter to take effect.

Operator actions

Syntax
Change command string
chg_element mms_config_type <value> <location>

NOTE
The value can be changed using the chg_cell_element command but the incorrect value is used until the MSI or BSI is reset and the change becomes active.

Display command string

disp_element mms_config_type <location>

68P02901W23-S

6-561 Nov 2009

Values

Chapter 6: CM database parameters

Values
Value type Valid range Boolean 0 or 1 If land_layer1_mode = 0 (2.048 Mbit/s E1 link) then: 0 1 Default value 0 CRC-4 No CRC-4

6-562

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

ms_distance_allowed

Description
The ms_distance_allowed parameter disables or enables the distance comparison process for handovers. When enabled, the distance comparison process can cause a handover if the distance between the MS and the BSS is greater than the ms_max_range. If this parameter is enabled, the value chosen for ms_max_range needs careful optimization. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes ms_max_range

Syntax
Add/Change command strings
add_cell <gsm_cell_id> <location> chg_element ms_distance_allowed <value> <location> <cell_desc> chg_cell_element ms_distance_allowed <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full] disp_element ms_distance_allowed <location> <cell_desc>

Values
Value type Valid range Boolean 0 or 1 0 1 Default value 0 Disabled Enabled

68P02901W23-S

6-563 Nov 2009

References

Chapter 6: CM database parameters

References
GSM specification 5.08 - Appendix A, 3.1 (f): PBGT(n); 3.2.2d; 3d 12.20 - 5.2.8.18 - enable BSS Handover Control - enable MS Distance Process This is a Motorola defined parameter.

6-564

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

ms_max_range

Description
The ms_max_range parameter specifies the MS maximum range for the handover algorithm. Programme this parameter in terms of timing advance bits. The following equation shows the relationship between distance and timing advance: (timing advance) (bit period) (propagation velocity) = 2 (distance from MS to BSS) Value 0 corresponds to no timing advance. Values 1 to 63 represent the bit periods that the MS transmission (to the BSS) are delayed. If The Extended Range Feature is unrestricted and Extended Range is enabled in the cell, the maximum value of ms_max_range increases to 219. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes The range for the ms_max_range parameter depends on whether the Extended Range feature is enabled or disabled.

Syntax
Add/Change command strings
add_cell <gsm_cell_id> <location> add_cell <gsm_cell_id> <location>chg_element ms_max_range <value> <location><cell_desc> chg_cell_element ms_max_range <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full] disp_element ms_max_range <location> <cell_desc>

68P02901W23-S

6-565 Nov 2009

Values

Chapter 6: CM database parameters

Values
Value type Valid range Default value Integer 0 to 63 for normal cells (see ). 0 to 219 for Extended Range cells (see Table 6-26). 63

Table 6-25

ms_max_range values for normal cells

Bit periods delayed 468.75 467.75 466.75 465.75 464.75 ... ... 406.75 405.75 Distance of MS to BSS (kilometer) 0 0.554 1.108 1.662 2.215 ... ... 34.338 34.892

Timing advance bits 0 1 2 3 4 ... ... 62 63

If the Extended Range Feature is unrestricted and Extended Range is enabled in the cell, the maximum value of ms_max_range increases to 219.

Table 6-26

ms_max_range values for Extended Range cells

Bit periods delayed 468.75 467.75 466.75 465.75 464.75 ... ... 250.75 249.75 Distance of MS to BSS (km) 0 0.554 1.108 1.662 2.215 ... ... 120.772 121.326

Timing advance bits 0 1 2 3 4 ... ... 218 219

References
GSM parameter GSM specification MS_RANGE_MAX 5.08 - Appendix A - Table 1: MS_RANGE_MAX 5.10 - 5.8

6-566

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

ms_p_con_ack

Description
The ms_p_con_ack parameter specifies the time for which power control can be resumed if power change acknowledgment is not received from the MS. This parameter is effective only if the decision_alg_num equals 1. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes decision_alg_num = 1

Syntax
Add/Change command strings
add_cell <gsm_cell_id> <location> chg_element ms_p_con_ack <value> <location> <cell_desc> chg_cell_element ms_p_con_ack <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full] disp_element ms_p_con_ack <location> <cell_desc>

68P02901W23-S

6-567 Nov 2009

Values

Chapter 6: CM database parameters

Values
Value type Valid range Integer (1 step = 2 SACCH multiframes) 0 to 31 0 1 2 ... ... ... 31 Default value 2 0 SACCH multiframes 2 SACCH multiframes 4 SACCH multiframes ... ... ... 62 SACCH multiframes

References
Internal name P_CON_ACK This is a Motorola defined parameter.

6-568

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

ms_p_con_interval

Description
The ms_p_con_interval parameter specifies the minimum amount of time in multiples of two SACCH multiframes between successive RF power change orders to the MS. This value depends on the value for the decision_alg_num parameter. If decision_alg_num = 1, then the recommended value for ms_p_con_interval equals hreqave divided by 2 (hreqave/2). If decision_alg_num = 0, then the minimum recommended value for ms_p_con_interval equals 2 plus hreqave divided by 2 (2+hreqave/2). A (no operator actions) Yes Yes hreqave

Type Supported by OMC-R GUI Cell description required Dependencies

Syntax
Add/Change command strings
add_cell <gsm_cell_id> <location> chg_element ms_p_con_interval <value> <location> <cell_desc> chg_cell_element ms_p_con_interval <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full] disp_element ms_p_con_interval <location> <cell_desc>

68P02901W23-S

6-569 Nov 2009

Values

Chapter 6: CM database parameters

Values
Value type Valid range Integer (1 step = 2 SACCH multiframes) 0 to 31 0 1 2 ... ... 31 Default value 2 0 SACCH multiframes 2 SACCH multiframes 4 SACCH multiframes ... ... 62 SACCH multiframes

References
Internal name P_CON_INTERVAL This is a Motorola defined parameter.

6-570

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

ms_power_control_allowed

Description
The ms_power_control_allowed parameter enables or disables MS power control. Enabling this feature helps to reduce interference. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes None

Syntax
Add/Change command strings
add_cell <gsm_cell_id> <location> chg_element ms_power_control_allowed <value> <location> <cell_desc> chg_cell_element ms_power_control_allowed <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full] disp_element ms_power_control_allowed <location> <cell_desc>

Values
Value type Valid range Boolean 0 or 1 0 1 Default value 1 Disabled Enabled

68P02901W23-S

6-571 Nov 2009

References

Chapter 6: CM database parameters

References
Internal name EN_MS_PC This is a Motorola defined parameter.

6-572

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

ms_power_offset

Description
The ms_power_offset parameter specifies the power offset value sent out in the BCCH system information which utilizes the additional power capabilities of a class 3 DCS1800 MS that is accessing on the RACH. The value is a positive power offset from the value set by ms_txpwr_max_cch. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes If the cell is not a type 3 MS cell, 0 is the only value allowed.

Syntax
Change command strings
chg_element ms_power_offset <value> <location> <cell_desc> chg_cell_element ms_power_offset <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full] disp_element ms_power_offset <location> <cell_desc>

Values
Value type Valid range Integer (1 step = 2 dB) 0 to 3 0 1 2 3 Default value 0 0 dB 2 dB 4 dB 6 dB

68P02901W23-S

6-573 Nov 2009

ms_txpwr_max_cch

Chapter 6: CM database parameters

ms_txpwr_max_cch

Description
The ms_txpwr_max_cch parameter specifies the maximum random access power available for an MS on a control channel (CCCH) in a cell. This parameter is expressed as a power level value. Before accessing a cell on the RACH and before receiving the first power command during a communication on a DCCH (or TCH), the MS uses one of two possible power levels. The MS uses the lower power level of the two available: either the ms_txpwr_max_cch broadcast on the BCCH or the maximum transmit power as defined by the power class of the MS. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes frequency_type

Syntax
Add/Change command strings
add_cell <gsm_cell_id> <location> chg_element ms_txpwr_max_cch <value> <location> <cell_desc> chg_cell_element ms_txpwr_max_cch <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full] disp_element ms_txpwr_max_cch <location> <cell_desc>

Values
Value type
Integer (1 step = 2 dBm)

6-574

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Values

Valid range (2 to 19 for PGSM and EGSM cells)

Table 6-27 lists the maximum mobile power level for PGSM and EGSM cells.

Table 6-27
Value 2 3 4 5 6 7 8 9 10

Maximum mobile power level for PGSM and EGSM cells

Range 39 dBm 37 dBm 35 dBm 33 dBm 31 dBm 29 dBm 27 dBm 25 dBm 23 dBm Value 11 12 13 14 15 16 17 18 19 Range 21 dBm 19 dBm 17 dBm 15 dBm 13 dBm 11 dBm 9 dBm 7 dBm 5 dBm

Valid range (0 to 15, 29, 30, 31 for DCS1800 cells)

Table 6-28 lists the maximum mobile power level for DCS1800 cells.

Table 6-28
Value 29 30 31 0 1 2 3 4 5 6

Maximum mobile power level for DCS1800 cells

Range 36 dBm 34 dBm 32 dBm 30 dBm 28 dBm 26 dBm 24 dBm 22 dBm 20 dBm 18 dBm Value 7 8 9 10 11 12 13 14 15 Range 16 dBm 14 dBm 12 dBm 10 dBm 8 dBm 6 dBm 4 dBm 2 dBm 0 dBm

68P02901W23-S

6-575 Nov 2009

References

Chapter 6: CM database parameters

Valid range (0 to 15, 30, 31 for PCS1900 cells)

Values
Value type Valid range Integer (dBm) Depends on the system: 5 to 39 0 to 36 0 to 32, 33 Default value (odd values only) PGSM/EGSM (even values only) DCS1800 (even values only and value 33) PCS1900

Same value as max_tx_ms

68P02901W23-S

6-581 Nov 2009

msc_bss_overload_allowed

Chapter 6: CM database parameters

msc_bss_overload_allowed

Description
The msc_bss_overload_allowed parameter is an RSL Congestion Control (RCC) element which enables or disables the BSC to send BSS Overload messages to the MSC during RSL congestion. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No None

Syntax
Add/Change command strings
chg_element msc_bss_overload_allowed <value> bsc

Display command strings

disp_element msc_bss_overload_allowed bsc

Values
Value type Valid range Boolean 0 or 1 0 1 Default value 0 Disabled Enabled

6-582

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

msc_preference

Description
The msc_preference parameter specifies A-interface messaging if an external handover is needed during an assignment procedure. This parameter should align with the MSC implementation which may depend on whether queuing is enabled in the cell. The cause value sent to the MSC can be set according to whether directed retry is supported by the MSC. This parameter is copied if the copy_cell command is used. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes The Directed Retry or Multiband Inter-cell Handover feature must be unrestricted.

Syntax
Change command strings
chg_element msc_preference <value> <location> <cell_desc> chg_cell_element msc_preference <value> <cell_desc_opt>

Display command string

disp_element msc_preference <location> <cell_desc>

68P02901W23-S

6-583 Nov 2009

Values

Chapter 6: CM database parameters

Values
Value type Valid range Integer 0 to 7 0 1 Directed Retry is supported within the BSS, but not across the A-interface. Directed Retry is supported within the BSS. The only A-interface impact is the Assignment Complete message, which contains the optional Cell ID if the Cell ID changes during the assignment. The BSS sends the Handover Required message with the cause directed retry to the MSC. The BSS sends the Handover Required message with the cause of the handover to the MSC (for example, Better Cell). 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. The BSS sends an Assignment Failure message with the cause directed retry and then sends a Handover Required message with the cause of the handover to the MSC (for example, Better Cell). 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. The BSS sends a Handover Required message with the cause of the handover (for example, Better Cell) and then sends an Assignment Failure message with cause directed retry to the MSC.

2 3 4

Default value

References
GSM specification TS GSM 08.08 This is a Motorola defined parameter.

6-584

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

msc_qt

Description
The msc_qt parameter specifies a defined idle bit pattern for use by the Transcoder Rate Adaptation Unit (TRAU) and the MSC. The idle pattern is defined in the GSM specification as: The idle pattern must be transmitted on every timeslot that is not assigned to a channel, and on every timeslot of a channel that is not allocated to a call. The idle pattern should be 01010100.

The binary pattern 01010100 corresponds to decimal 84 which is the default value of this parameter. This parameter must correspond to the MSC value for an idle PCM sample on the A-interface. When the XCDR receives this value from the MSC in all PCM samples in its 20 ms frame, it outputs a TRAU idle speech frame. In the uplink, this parameter sets the value of PCM that the XCDR outputs to the MSC before the XCDR has achieved TRAU sync with the CCU in the DRI. Once this value has been set to match the MSC idle pattern, it does not require any further changes.

NOTE
This parameter is not related to DTX.

Type Supported by OMC-R GUI Cell description required Dependencies Operator actions

B (operator actions required) No No This parameter only applies to the XCDR (location = 0). Place the system in SYSGEN ON mode

Syntax
Change command strings
chg_element msc_qt <value> 0 chg_element msc_qt <value> xcdr

68P02901W23-S

6-585 Nov 2009

Values

Chapter 6: CM database parameters

Display command strings

disp_element msc_qt 0 disp_element msc_qt xcdr

Values
Value type Valid range Default value Integer (decimal) 0 to 255 (representing bit patterns 00000000 to 11111111) 84 (representing bit pattern 01010100)

6-586

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

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 Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No None

Syntax
Change command string
chg_element msc_release <value> <location>

Display command string

disp_element msc_release <location>

Values
Value type Valid range Boolean 0 or 1 0 1 Default value 0 MSC is a Release 1998 or older. MSC is a Release 1999 or newer.

68P02901W23-S

6-587 Nov 2009

mspwr_alg

Chapter 6: CM database parameters

mspwr_alg

Description
The mspwr_alg parameter enables or disables the enhanced power control algorithm. The enhanced power control algorithm is used to prevent oscillation for MS power control where power is reduced for RXQUAL reasons and later increased for RXLEV reasons. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes None

Syntax
Add/Change command strings
add_cell <gsm_cell_id> <location> achg_element mspwr_alg <value> <location> <cell_desc> chg_cell_element mspwr_alg <value> <cell_desc_opt>

Display command strings

disp_cell mspwr_alg <cell_id> [full] disp_element mspwr_alg <location> <cell_desc>

Values
Value type Valid range Boolean 0 or 1 0 1 Default value 0 Disabled Enabled

6-588

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

mtbr_downgrade_enabled

{27703A}

Description
The mtbr_downgrade_enabled parameter enables or disables negotiating the MTBR of an admitted PFC during future retention procedures to a lower value than initially committed. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes The mtbr_downgrade_enabled is modified only if Qos is enabled or unrestricted at the OMC.

Syntax
Change command strings
chg_element mtbr_downgrade_enabled <value> <location>

Display command strings

disp_element mtbr_downgrade_enabled <location>

Values
Value type Valid range Integer 0 or 1 0 1 Default value 1 Not allowed to set MTBR to a lower value than committed. Allowed to set the MTBR to a lower value than committed.

68P02901W23-S

6-589 Nov 2009

mtl_loadshare_granularity

Chapter 6: CM database parameters

mtl_loadshare_granularity

Description
The mtl_loadshare_granularity parameter sets the loadshare granularity across MTL links. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No If the element is changed in SYSGEN ON mode, the change takes effect immediately.

NOTE
Changes take effect only when all MTLs are locked.

Syntax
Change command string
chg_element mtl_loadshare_granularity <value> 0

Display command string

disp_element mtl_loadshare_granularity 0

Values
Value type Valid range Boolean 0 or 1 0 1 Default value 0 16 virtual circuits (regular granularity) 64 virtual circuits (enhanced granularity)

6-590

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

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 Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes The Multiband Inter-cell Handover feature must be enabled.

Syntax
Change command strings
chg_element multiband_reporting <value> <location> <cell_desc> chg_cell_element multiband_reporting <value> <cell_desc_opt>

Display command string

disp_element multiband_reporting <location> <cell_desc>

Values
Value type Valid range Integer 0 to 3 0 Normal reporting of the six strongest neighbor cells with known and allowed NCC part of the BSIC, irrespective of the band used.

68P02901W23-S

6-591 Nov 2009

References

Chapter 6: CM database parameters

Report the strongest neighbor cell, with known and allowed NCC part of BSIC, in each of the frequency bands in the neighbor cell list, excluding the frequency band of the serving cell. The remaining positions in the measurement report shall be used for reporting Cells in the band of the serving Cell. Any still remaining positions will be used to report the next strongest identified neighbors in other bands irrespective of the band used. Report the two strongest cells, with known and allowed NCC part of BSIC, in each of the frequency bands in the neighbor cell list, excluding the frequency band of the serving cell. The remaining positions in the measurement report shall be used for reporting Cells in the band of the serving Cell. Any still remaining positions will be used to report the next strongest identified neighbors in other bands irrespective of the band used. Report the three strongest cells, with known and allowed NCC part of BSIC, in each of the frequency bands in the neighbor cell list, excluding the frequency band of the serving cell. The remaining positions in the measurement report shall be used for reporting Cells in the band of the serving Cell. Any still remaining positions will be used to report the next strongest identified neighbors in other bands irrespective of the band used.

Default value

References
GSM specification TS GSM 04.08 section 10.5.2.22 This is a Motorola defined parameter.

6-592

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

nacc_enabled

Description
The nacc_enabled parameter indicates whether the Change Cell Notification (CNN) is enabled or not. Type Supported by OMC-R GUI Cell number required Dependencies A (No operator actions) Yes No The Network Assisted Cell Change (NACC) feature must be unrestricted nacc_enabled cannot be set to 0 (disabled) if the QoS feature is enabled.

Syntax
Add/Change command strings
chg_element nacc_enabled <value> <location>

Display command strings

disp_element nacc_enabled <location>

Values
Value type Valid range Integer 0 to 1 0 1 Default value 0 NACC is off NACC is on

68P02901W23-S

6-593 Nov 2009

n_avg_i

Chapter 6: CM database parameters

n_avg_i

Description
The n_avg_i parameter specifies the number of signal strength measurements that is made for each filtered interference signal strength sample. n_avg_i is the number of radio blocks that the signal strength is computed on over a period of t_avg_t when in Packet Transfer mode, and t_avg_w when in Packet Wait (idle) mode. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes This parameter can be used only if the GPRS feature is unrestricted.

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

Syntax
Change command strings
chg_element n_avg_i <value> <location> <cell_desc> chg_cell_element n_avg_i <value> <cell_desc_opt>

Display command string

disp_element n_avg_i <location> <cell_desc>

Values
Value type Valid range Default value Integer (number of radio blocks) 0 to 15 2

6-594

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

ncc_of_plmn_allowed

Description
The ncc_of_plmn_allowed parameter is a bit mapped value which specifies which Network Color Codes (NCCs) are allowed on specific broadcast control channels (BCCH carriers). In border areas where two PLMN operators provide overlapping service, a bilateral agreement is required to determine the NCC values to be broadcast. The selected values are specified by entering a value that can bit map to the desired NCC. For example, PLMN operators serving a border area may agree to use NCCs of 0 and 4. A value of 17 is entered for the ncc_of_plmn_allowed which bit maps as: 00010001 The first and fifth bits are set which allow the NCC value of 0 and 4 to be broadcast on BCCH carriers. Two or more NCCs may be assigned in non border areas by specifying ncc_of_plmn_allowed values that bit maps to the desired NCCs. For example, the ncc_of_plmn_allowed value of 51 bit maps as: 00110011 The first, second, fifth, and sixth bits are set which allows NCC values of 0, 1, 4, and 5 to be broadcast on BCCH carriers. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes None

Syntax
Add/Change command strings
add_cell <gsm_cell_id> <location> chg_element ncc_of_plmn_allowed <value> <location> <cell_desc> chg_cell_element ncc_of_plmn_allowed <value> <cell_desc_opt>

68P02901W23-S

6-595 Nov 2009

Values

Chapter 6: CM database parameters

Display command strings

disp_cell <cell_id> [full] disp_element ncc_of_plmn_allowed <location> <cell_desc>

Values
Value type Valid range Integer 0 to 255 (or 0 to FFh in Hex)

Default

255

Table 6-30 is a representation of the bit mapping of the ncc_of_plmn_allowed parameter. When a bit is set to 1, the corresponding NCC is allowed. When a bit is set to 0, the corresponding NCC is not allowed.

Table 6-30
Bit position NCC values

Bit mapping of ncc_of_plmn_allowed

128 7 64 6 32 5 16 4 8 3 4 2 2 1 1 0

References
GSM parameter GSM specification PLMN_PERMITTED, NCC 3.03-Annex A, NCCs per country 12.20-5.2.8.7 cell Description-plmn-permitting 4.08-10.5.2.15, figure 10.34 and table 10.28 5.08-9: PLMN_PERMITTED

6-596

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

nccr_enabled

Description
The nccr_enabled parameter specifies whether Network Controlled Cell Reselection (NCCR) is enabled at a BSS. The following error message is displayed and the command rejected if an attempt is made to disable this parameter when gprs_type5_alg is enabled: ERROR: gprs_type5_alg must be disabled before disabling nccr_enabled. COMMAND REJECTED Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No The GPRS and NCCR features must be unrestricted. The PCU must be equipped. When nccr_enabled parameter is set to 0 (disabled), gprs_type5_alg cannot be set to 1 (enabled). gprs_type5_alg must be set to 0 (disabled) before the nccr_enabled parameter can be set to 0 (disabled).

Syntax
Change command string
chg_element nccr_enabled 1 0

Display command string

disp_element nccr_enabled 0

Values
Value type Valid range Boolean 0 or 1 0 1 Default value 0 Disabled Enabled

68P02901W23-S

6-597 Nov 2009

nccrOpt

Chapter 6: CM database parameters

nccrOpt

Description
The nccrOpt parameter indicates whether the Network Controlled Cell Reselection (NCCR) option is unrestricted in the BSS software. If restricted, any attempt to access the other NCCR parameters is rejected. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No The GPRS and NCCR features must be unrestricted to provide their associated functionality.

Syntax
Display command string
disp_options

Values
Value type Valid range Boolean 0 or 1 0 1 Default value None Restricted Unrestricted

6-598

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

neighbor_journal

Description
The neighbor_journal parameter enables or disables neighbor journaling. If journaling is enabled: There is no warm-up period for neighbors. All neighbor information is padded with 0's. Averaging and power budget calculations begin immediately. If a previously reported neighbor is missing in the measurement report, a 0 rxlev is used for the neighbor.

If journaling is disabled: There is a warm-up period of the surround cell hreqave before power budget calculations begin. The last received rxlev for the unreported neighbor is used. A (no operator actions) Yes Yes None

Type Supported by OMC-R GUI Cell description required Dependencies

Syntax
Change command strings
chg_element neighbor_journal <value> <location> <cell_desc> chg_cell_element neighbor_journal <value> <cell_desc_opt>

Display command string

disp_element neighbor_journal <location> <cell_desc>

68P02901W23-S

6-599 Nov 2009

Values

Chapter 6: CM database parameters

Values
Value type Valid range Boolean 0 or 1 0 1 Default value 0 Disabled Enabled

6-600

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

network_control_order

Description
The network_control_order parameter specifies the GPRS Cell Reselection order. Table 6-31 list the available configurations.

Table 6-31
Mode NC0 NC1

Configurations for network_control_order

Responsible element MS control MS control Functionality Normal GPRS mobile control. GPRS mobile control with measurement reports. MS sends measurement reports to BSS. MS performs autonomous cell re-selection Network control. GPRS MS sends measurement reports to BSS. BSS sends cell reselection commands and instructs mobile to perform cell reselection All functionality in NC0 mode. BSS sends reselection commands to GPRS. MS to change cell reselection mode All functionality in NC1 mode. BSS sends cell reselection command to GPRS mobile to change cell reselection mode A (no operator actions) Yes Yes The GPRS and NCCR features must be unrestricted. The PCU must be equipped.

NC2

Network control

Enhanced NC0 Enhanced NC1

MS control

MS Control

Type Supported by OMC-R GUI Cell description required Dependencies

Syntax
Change command strings
chg_element network_control_order <value> <location> <cell_desc> chg_cell_element network_control_order <value> <cell_desc_opt>

68P02901W23-S

6-601 Nov 2009

Values

Chapter 6: CM database parameters

Display command string

disp_element network_control_order <location> <cell_desc>

Values
Value type Valid range Integer 0 to 4 (mode values) 0 1 2 3 4 Default value 0 NC0 NC1 NC2 Enhanced NC0 Enhanced NC1

6-602

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

new_calls_hr

Description
The new_calls_hr parameter specifies the congestion threshold to indicate at what congestion level the BSS should start assigning new half-rate capable calls as AMR/GSM half-rate calls. A limitation exists based on the number of idle half-rate channels and free generic traffic channels in the cell. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes The AMR feature and/or GSM Half Rate feature must be unrestricted. The new_calls_hr congestion threshold is ignored if the AMR/GSM HR mode is not enabled at the BSS level or at the Cell level.

Syntax
Add/Change command strings
chg_element new_calls_hr <value> <location> <cell_desc> chg_cell_element new_calls_hr <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> full disp_element new_calls_hr <location> <cell_desc>

Values
Value type Valid range Default value Integer (in steps of 1%) 0 to 101 101 101 disables this parameter.

68P02901W23-S

6-603 Nov 2009

Chapter 6: CM database parameters

Description
The ni parameter specifies the Network Indicator (NI) that establishes a method of differentiation between international and national messages. Type Supported by OMC-R GUI Cell description required Dependencies Operator actions B (operator actions required) Yes No This parameter only applies to the BSC. The MTL must be locked then unlocked for the change to take effect.

Syntax
Change command string
chg_element ni <value> 0

Display command string

disp_element ni 0

Values
Value type Valid range Integer 0 to 3 0 1 2 3 Default value None International Network Spare (for international use only) National Network Reserved for national use

6-604

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

References

References
GSM specification ITU - TSS Q.708 This is a Motorola defined parameter.

68P02901W23-S

6-605 Nov 2009

ns_alive_retries

Chapter 6: CM database parameters

ns_alive_retries

Description
The ns_alive_retries parameter specifies the number of retries generated to establish if an NSVC is alive. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No The GPRS feature must be unrestricted.

NOTE
BSS software processes using this parameter are not notified when this parameter is changed.

Syntax
Change command string
chg_element ns_alive_retries <value> <location>

Display command string

disp_element ns_alive_retries <location>

Values
Value type Valid range Default value Integer (number of retries) 1 to 10 3

6-606

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

ns_block_retries

Description
The ns_block_retries parameter specifies the number of retries generated to block an NSVC. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No The GPRS feature must be unrestricted.

NOTE
BSS software processes using this parameter are not notified when this parameter is changed.

Syntax
Change command string
chg_element ns_block_retries <value> <location>

Display command string

disp_element ns_block_retries <location>

Values
Value type Valid range Default value Integer (number of retries) 1 to 3 3

68P02901W23-S

6-607 Nov 2009

ns_unblock_retries

Chapter 6: CM database parameters

num_emerg_access

Description
The num_emerg_access parameter enables or disables the collection of statistics in relation to the number of active TCH calls terminated to allow an emergency call to take the specified GSM cell. Use an index value of 0 for this element. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) No Yes 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 Valid range Boolean off or on off on Default value off Disabled Enabled

68P02901W23-S

6-611 Nov 2009

num_emerg_rejected

Chapter 6: 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. Use an index value of 0 for this element. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) No Yes 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 Valid range Boolean off or on off on Default value off Disabled Enabled

6-612

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

num_emerg_tch_kill

Description
The num_emerg_tch_kill parameter enables or disables the collection of statistics in relation to the number of active TCH calls terminated to allow an emergency call to the channel on the specified GSM cell. Use an index value of 0 for this element. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) No Yes 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 Valid range Boolean off or on off on Default value off Disabled Enabled

68P02901W23-S

6-613 Nov 2009

num_emerg_term_sdcch

Chapter 6: 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 an SDCCH but could not be allocated a TCH for the specified GSM cell. Use an index value of 0 for this element. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) No Yes 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 Valid range Boolean off or on off on Default value off Disabled Enabled

6-614

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

num_gbl_dl_thrput_samples

Description
The num_gbl_dl_thrput_samples parameter specifies the number of samples used to compute the gbl_dl_data_thrput statistic. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) No Yes The GPRS feature must be unrestricted.

NOTE
BSS software processes using this parameter are not notified when the change is made.

Syntax
Change command string
chg_element gbl_dl_thrput_samples <value> <location> <cell_desc>

Display command string

disp_element gbl_dl_thrput_samples <location> <cell_desc>

Values
Value type Valid range Default value Integer (number of samples) 1 to 10 10

68P02901W23-S

6-615 Nov 2009

num_gbl_ul_thrput_samples

Chapter 6: 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. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) No Yes The GPRS feature must be unrestricted.

NOTE
BSS software processes using this parameter are not notified when the change is made.

Syntax
Change command string
chg_element gbl_ul_thrput_samples <value> <location> <cell_desc>

Display command string

disp_element gbl_ul_thrput_samples <location> <cell_desc>

Values
Value type Valid range Default value Integer (number of samples) 1 to 10 10

6-616

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

number_of_preferred_cells

Description
The number_of_preferred_cells parameter specifies the maximum number of target cells to be included in a Handover Required message. The preferred list of target cells is a mandatory BSS field. The number of preferred cells is given in order of predicted best performance. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes None

Syntax
Add/Change command strings
add_cell <gsm_cell_id> <location> chg_element number_of_preferred_cells <value> <location> <cell_desc> chg_cell_element number_of_preferred_cells <value> <cell_desc_opt>

Display command strings

disp_cell <cell_desc> [full] disp_element number_of_preferred_cells <location> <cell_desc>

Values
Value type Valid range Default value Integer (represents preferred cells) 1 to 16 16

68P02901W23-S

6-617 Nov 2009

References

Chapter 6: CM database parameters

References
GSM specification 8.08 - 3.1.5.1.1 This is a Motorola defined parameter.

6-618

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

number_sdcchs_preferred

Description
The number_sdcchs_preferred parameter specifies the preferred number of Standalone Dedicated Control Channels (SDCCHs) that the reconfiguration algorithm tries to maintain. When channel reconfiguration is enabled, the CRM attempts to maintain the preferred number of SDCCHs for Immediate Assignments. The reconfiguration either of consist idle TCHs being converted to SDCCHs or free SDCCHs being converted to TCHs. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes The valid range for this parameter depends on ccch_conf. The value must be less than or equal to the max_number_of_sdcchs.

NOTE
To maximize the PDCHs configuration on the carrier A, the BTS Cell Resource Manager (CRM) avoids configuring SDCCHs to the double density CTU2 EGPRS carrier A and its paired carrier B.

Syntax
Add/Change command strings
add_cell <gsm_cell_id> <location> chg_element number_sdcchs_preferred <value> <location> <cell_desc> chg_cell_element number_sdcchs_preferred <value> <cell_desc_opt>

68P02901W23-S

6-619 Nov 2009

Values

Chapter 6: CM database parameters

Display command strings

disp_cell <cell_id> [full] disp_element number_sdcchs_preferred <location> <cell_desc>

Values
Value type Valid range Integer (number of SDCCHs) If feature SDCCH increase is unrestricted, then 4 to 124 8 to 128 If ccch_conf = 1. If ccch_conf = 0.

If feature SDCCH increase is restricted, then 4 to 44 8 to 48 Default value If ccch_conf = 1. If ccch_conf = 0.

12 if ccch_conf = 1, 16 if ccch_conf is not equal to 1

References
GSM specification 5.02 - 6.4 This is a Motorola defined parameter.

6-620

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

opc

Description
The opc parameter specifies the Originating Point Code (OPC). The values for the OPC are stored as a 14-bit binary code for non-ANSI and 24-bit binary code for ANSI. If the opc parameter is set to equal the dpc, but not equal to lb_int_dpc, the system issues a warning: COMMAND ACCEPTED: WARNING: When opc equals dpc, communication with MSC is impossible. If the opc parameter is set to equal the lb_int_dpc and lcs_mode is 2, but not equal to dpc, the system issues a warning: COMMAND ACCEPTED: WARNING: When lb_int_dpc is equal to the opc, communication with the BSS-based SMLC is impossible. If the opc parameter is set to equal the lb_int_dpc and equal to dpc, and lcs_mode is 2, the system issues a warning: COMMAND ACCEPTED: WARNING: dpc and lb_int_dpc should not be equal to opc. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No The range of opc depends on the values for the ss7_mode on page 6-814. This parameter only applies to the BSC.

Syntax
Change command string
chg_element opc <value> 0

Display command string

disp_element opc 0

68P02901W23-S

6-621 Nov 2009

Values

Chapter 6: CM database parameters

Values
Value type Valid range Integer 0 to 16383 0 to 16777215 Default value None If ss7_mode = 0 (ITU-TSS) If ss7_mode = 1 (ANSI)

References
GSM specification ITU-TSS Q.708 This is a Motorola defined parameter.

6-622

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

option_alg_a5_1

Description
The option_alg_a5_1 parameter enables or disables the encryption algorithm A5/1. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No This parameter applies only to the BSC. The A5/1 feature must be unrestricted.

Syntax
Change command string
chg_element option_alg_a5_1 <value> 0

Display command string

disp_element option_alg_a5_1 0

Values
Value type Valid range Boolean 0 or 1 0 1 Default value 0 Disabled Enabled

References
GSM specification 8.08 This is a Motorola defined parameter.

68P02901W23-S

6-623 Nov 2009

option_alg_a5_2

Chapter 6: CM database parameters

option_alg_a5_2

Description
The option_alg_a5_2 parameter enables or disables the encryption algorithm A5/2. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No This parameter only applies to the BSC. The A5/2 feature must be unrestricted.

Syntax
Change command string
chg_element option_alg_a5_2 <value> 0

Display command string

disp_element option_alg_a5_2 0

Values
Value type Valid range Boolean 0 or 1 0 1 Default value 0 Disabled Enabled

References
GSM specification 8.08 This is a Motorola defined parameter.

6-624

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

option_alg_a5_3

Description
The option_alg_a5_3 parameter enables or disables the encryption algorithm A5/3. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No This parameter only applies to the BSC. The A5/3 feature must be unrestricted.

Syntax
Add/Change command string
chg_element option_alg_a5_3 <value> 0

Display command string

disp_element option_alg_a5_3 0

Values
Value type Valid range Boolean 0 or 1 0 1 Default value 0 Disabled Enabled

References
GSM specification 8.08 This is a Motorola defined parameter.

68P02901W23-S

6-625 Nov 2009

option_alg_a5_4

Chapter 6: CM database parameters

option_alg_a5_4

Description
The option_alg_a5_4 parameter enables or disables the encryption algorithm A5/4. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No This parameter only applies to the BSC. The A5/4 feature must be unrestricted.

Syntax
Add/Change command string
chg_element option_alg_a5_4 <value> 0

Display command string

disp_element option_alg_a5_4 0

Values
Value type Valid range Boolean 0 or 1 0 1 Default value 0 Disabled Enabled

References
GSM specification 8.08 This is a Motorola defined parameter.

6-626

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

option_alg_a5_5

Description
The option_alg_a5_5 parameter enables or disables the encryption algorithm A5/5. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No This parameter only applies to the BSC. The A5/5 feature must be unrestricted.

Syntax
Add/Change command string
chg_element option_alg_a5_5 <value> 0

Display command string

disp_element option_alg_a5_5 0

Values
Value type Valid range Boolean 0 or 1 0 1 Default value 0 Disabled Enabled

References
GSM specification 8.08 This is a Motorola defined parameter.

68P02901W23-S

6-627 Nov 2009

option_alg_a5_6

Chapter 6: CM database parameters

option_alg_a5_6

Description
The option_alg_a5_6 parameter enables or disables the encryption algorithm A5/6. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No This parameter only applies to the BSC. The A5/6 feature must be unrestricted.

Syntax
Add/Change command string
chg_element option_alg_a5_6 <value> 0

Display command string

disp_element option_alg_a5_6 0

Values
Value type Valid range Boolean 0 or 1 0 1 Default value 0 Disabled Enabled

References
GSM specification 8.08 This is a Motorola defined parameter.

6-628

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

option_alg_a5_7

Description
The option_alg_a5_7 parameter enables or disables the encryption algorithm A5/7. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No This parameter only applies to the BSC. The A5/7 feature must be unrestricted.

Syntax
Add/Change command string
chg_element option_alg_a5_7 <value> 0

Display command string

disp_element option_alg_a5_7 0

Values
Value type Valid range Boolean 0 or 1 0 1 Default value 0 Disabled Enabled

References
GSM specification 8.08 This is a Motorola defined parameter.

68P02901W23-S

6-629 Nov 2009

option_preempt

Chapter 6: CM database parameters

option_preempt

Description
The option_preempt parameter enables or disables the Emergency Call Preemption (ECP) feature and/or the Enhanced Multi-level Precedence and Preemption (eMLPP) feature.

NOTE
This renamed parameter was formerly named option_emergency_preempt. The ECP feature enables the BSS to provide access for emergency calls regardless of other traffic currently on the BSS. An emergency call is identified in the RACH burst from the MS, or the service type is Emergency call establishment in the CM Service Request message. The eMLPP feature allows calls to be allocated a precedence depending on their function. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No This parameter applies only at the BSC. The eMLPP feature must be unrestricted for values 0 to 3, otherwise the range is 0 to 1.

Syntax
Change command string
chg_element option_preempt <value> 0

Display command string

disp_element option_preempt 0

6-630

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Values

Values
Value type Valid range 0 to 3 0 1 2 3 Default value 0 ECP and eMLPP are both disabled. ECP enabled. eMLPP enabled. ECP and eMLPP are both enabled. Integer

References
GSM specification 02.11, Service Accessibility, version 4.5.0 [3] 04.08, Mobile Radio Interface Layer 3 Specification, version 4.8.0[1] 03.22, functions related to MS in idle Mode, version 4.5.0[7] This is a Motorola defined parameter.

68P02901W23-S

6-631 Nov 2009

outer_zone_usage_level

Chapter 6: 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. If this parameter is set to 0, channels in the inner zone are used whenever an MS is qualified to use those resources. If this parameter is set to any other value, the inner zone resources are allocated only when an MS is qualified and at least the specified percentage of outer zone TCHs is in use. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes The Concentric Cells feature must be enabled.

Syntax
Change command strings
chg_element outer_zone_usage_level <value> <location> <cell_desc> chg_cell_element outer_zone_usage_level <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> <full> disp_element outer_zone_usage_level <location> <cell_desc>

Values
Value type Valid range Default value Integer (indicating the percentage of outer zone TCH usage) 0 to 100 0

6-632

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

override_intra_bss_pre_transfer

Description
The override_intra_bss_pre_transfer parameter specifies whether a pre-transfer request is sent to SM (Switch Manager) when the handover allocation message is received during an inter-cell handover. This parameter only applies to intra-BSS inter-cell handovers. Call processing sends the pre-transfer request to the switch manager, to make a connection in the downlink direction from the active CIC to the new radio channel at the time of the new radio channel assignment. This puts voice traffic on the new radio channel that the mobile is being handed off to earlier than when the pre-transfer function is disabled. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No This parameter applies only to the BSC or RXCDR.

Syntax
Change command string
chg_element override_intra_bss_pre_transfer <value> 0

Display command string

disp_element override_intra_bss_pre_transfer 0

Values
Value type Valid range Boolean 0 or 1 0 1 Default value 0 Send pre-transfer request to SM. Do not send pre-transfer request to SM.

68P02901W23-S

6-633 Nov 2009

pbgt_mode

Chapter 6: CM database parameters

pbgt_mode

Description
The pbgt_mode parameter enables the operator to select the preferred method of compensating for a mismatch in frequency types between the serving channel and the neighbor cell BCCH when calculating power budget. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes The Dual Band Cells feature must be unrestricted. Changing this parameter to 1 adds this cell to its own neighbor list. This autocreated neighbor cannot be deleted by the operator and it can only be deleted by changing this parameter back to 0.

Syntax
Change command strings
chg_element pbgt_mode <value> <location> <cell_desc> chg_cell_element pbgt_mode <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> <full> disp_element pbgt_mode <location> <cell_desc>

Values
Value type Valid range Boolean 0 or 1 1 0 Default value 0 Enabled A new neighbor is auto-equipped with BCCH frequency set to that of the serving cell. Disabled An equipped neighbor is unequipped.

6-634

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

pccch_enabled

Description
The pccch_enabled parameter specifies whether the PBCCH/PCCCH optional feature is unrestricted at a cell. This feature supports GPRS Network Operation Modes I and III for normal range cell. Type Supported by OMC-R GUI Cell description required Dependencies B (Operator actions required) Yes Yes The PBCCH/PCCCH optional feature must be unrestricted. gprs_enabled must be set to 0. The BSS must have configured the BCCH carrier of the cell to non-hopping. The cell must be a normal range cell. In order to enable PBCCH/PCCCH for a cell, gprs_enabled must be set to 0 - disable pccch_enabled must be set to 1 - enable gprs_enabled must be set to 1 - enable.

Operator actions

Syntax
Change command string
chg_element pccch_enabled <value> <location> <cell_desc> chg_cell_element pccch_enabled <value> <cell-desc_opt> chg_cell_element <location> pccch_enabled <value> all

Display command string

disp_cell <cell_id> full disp_element pccch_enabled <location> <cell-desc> disp_element pccch_enabled <location> all

68P02901W23-S

6-635 Nov 2009

Values

Chapter 6: CM database parameters

Values
Value type Valid range Boolean 0 or 1 0 1 Default value 0 Disabled Enabled

6-636

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

pccchOpt

Description
The pccchOpt parameter indicates whether the Packet Broadcast Control Channel/Packet Common Control Channel (PBCCH/PCCCH) feature option is unrestricted in the BSS software. If restricted, any attempt to access the other PBCCH/PCCCH parameters is rejected. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No The PBCCH/PCCCH features must be unrestricted to provide their associated functionality.

Syntax
Display command string
disp_options

Values
Value type Valid range Boolean 0 or 1 0 1 Default value None Restricted Unrestricted

68P02901W23-S

6-637 Nov 2009

pcr_enable

Chapter 6: CM database parameters

pcr_enable

Description
The pcr_enable parameter enables or disables the Preventative Cyclic Retransmission (PCR) error correction method. This method is used when transferring messages between the MSC and the BSC (through the A-interface). If PCR is enabled, then: ss7_l2_t7 > 800 milliseconds. ss7_l3_t2 > 1400 milliseconds. A (no operator actions) Yes No This parameter only applies to the BSC. You must reset the BSC when changing this parameter for the change to take effect.

Type Supported by OMC-R GUI Cell description required Dependencies

Syntax
Change command string
chg_element pcr_enable <value> 0

Display command string

disp_element pcr_enable 0

Values
Value type Valid range Boolean 0 or 1 0 1 Default value 0 Disabled Enabled

6-638

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

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 Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No 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 Valid range Default value Integer (message signal units) 32 to 127 127

68P02901W23-S

6-639 Nov 2009

pcr_n2

Chapter 6: CM database parameters

pcr_n2

Description
The pcr_n2 parameter specifies the maximum number of message signal unit octets to be retained for retransmission for the PCR Error Correction method. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No This parameter only applies to the BSC.

Syntax
Change command string
chg_element pcr_n2 <value> 0

Display command string

disp_element pcr_n2 0

Values
Value type Valid range Default value Integer (message octets) 950 to 3750 3750

6-640

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

pcu_redundancy

Description
The pcu_redundancy parameter specifies whether the BSS supports PCU redundancy or not. If entered to support redundancy, six more parameters are then prompted to specify the mapping order. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No This parameter applies only to the BSC (location = 0). When only one PCU is equipped, pcu_redundancy does not prompt for redundant PCU.

Syntax
Change command string
chg_element pcu_redundancy <value> bsc

Display command string

disp_element pcu_redundancy bsc

Values
Value type Valid range Boolean 0 1 Default value {27955} 0 PCU redundancy Off PCU redundancy On

68P02901W23-S

6-641 Nov 2009

Prompts

Chapter 6: CM database parameters

Prompts
If the value is set to 1 (PCU redundancy On) the following prompts are displayed: Please specify first redundant for PCU 0: <pcu_red_map_01> Please specify second redundant for PCU 0: <pcu_red_map_02> Please specify first redundant for PCU 1: <pcu_red_map_11> Please specify second redundant for PCU 1: <pcu_red_map_12> Please specify first redundant for PCU 2: <pcu_red_map_21> Please specify second redundant for PCU 2: <pcu_red_map_22> The following table shows the possible entries and their meanings: Parameter <pcu_red_map_01> <pcu_red_map_02> <pcu_red_map_11> <pcu_red_map_12> <pcu_red_map_21> <pcu_red_map_22> Valid Input 0, 1 or 2 0, 1 or 2 0, 1 or 2 0, 1 or 2 0, 1 or 2 0, 1 or 2 Default No redundancy No redundancy No redundancy No redundancy No redundancy No redundancy

If the parameter pcu_redundancy value is set to 1 (True or On), redundancy can be set to any of the available PCUs, including the current PCU itself, in answer to the prompts. If the prompts are not answered, default is no redundancy.

Example display
An example of pcu_redundancy follows: disp_element pcu_redundancy bsc pcu_redundancy =TRUE PCU id -----0 1 2 1st redundant ------------1 2 NA 2nd redundant ------------NA NA NA

6-642

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

percent_traf_cs

Description
The percent_traf_cs parameter specifies the percentage of RSL Reserved for CS. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No The GPRS feature must be unrestricted.

Syntax
Change command string
chg_element percent_traf_cs <value> <location>

Display command string

disp_element percent_traf_cs <location>

Values
Value type Valid range Default value Integer 0 to 90 55

68P02901W23-S

6-643 Nov 2009

persistence_level

Chapter 6: CM database parameters

persistence_level

Description
The persistence_level parameter specifies values for the access persistence level for each radio priority on a per cell basis. This parameter is always attached with a radio priority (i) of 0 to 3. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes The PBCCH/PCCCH optional feature must be unrestricted.

Syntax
Change command string
chg_element persistence_level,i <value> <location> <cell_desc> chg_cell_element persistence_level,i <value> <cell_desc_opt>

Display command string

disp_cell <cell_id> full disp_element persistence_level,i <location> <cell_desc>

6-644

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Values

Values
Value type Valid range Integer 0 to 15 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 Default value 4 representing the access persistence level: persistence persistence persistence persistence persistence persistence persistence persistence persistence persistence persistence persistence persistence persistence persistence persistence level 0 level 1 level 2 level 3 level 4 level 5 level 6 level 7 level 8 level 9 level 10 level 11 level 12 level 13 level 14 level 16

68P02901W23-S

6-645 Nov 2009

pfm_sig_enabled

Chapter 6: CM database parameters

pfm_sig_enabled

{27703A}

Description
The pfm_sig_enabled parameter enables or disables support of PFC modification signaling to C-SGSN when there is downgrade or upgrade for non-real time PFC on a per BSS basis. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No The pfm_sig_enabled attribute is modified only if Qos is enabled or unrestricted at the OMC.

Syntax
Change command string
chg_element pfm_sig_enabled <value> <location>

Display command string

disp_element pfm_sig_enabled <location>

Values
Value type Valid range Boolean 0 or 1 0 No PFC modification message sent to C-SGSN when there is a upgrade or downgrade for non realtime PFC. PFC modification message will be sent to SGSN when there is a upgrade or downgrade for non realtime PFC.

Default value

6-646

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Values

NOTE
pfm_sig_enabled parameter is not checked when Max SDU size is re-negotiated.

68P02901W23-S

6-647 Nov 2009

phase_lock_gclk

Chapter 6: CM database parameters

phase_lock_gclk

Description
The phase_lock_gclk parameter enables or disables phase locking for the GCLK board at a site. Phase locking means the GCLK board is synchronized with the clock of the MMS selected as determined by the mms_priority value. The mms_priority value is specified using the modify_value command. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No None

Syntax
Change command string
chg_element phase_lock_gclk <value> <location>

Display command string

disp_element phase_lock_gclk <location>

Values
Value type Valid range Boolean 0 or 1 0 1 Default value 0 Disabled Enabled

6-648

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

phase_lock_retry

Description
The phase_lock_retry parameter specifies the time in minutes during which phase locking is automatically retried after failure. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No None

Syntax
Change command string
chg_element phase_lock_retry <value> <location>

Display command string

disp_element phase_lock_retry <location>

Values
Value type Valid range Integer (minutes) 0 to 255 0 1 to 254 255 Default value 255 Immediate phase_lock_retry. Time period for retrying phase locking. No phase_lock_retry.

68P02901W23-S

6-649 Nov 2009

phase2_classmark_allowed

Chapter 6: CM database parameters

phase2_classmark_allowed

Description
The phase2_classmark_allowed parameter defines the format of the classmark parameter sent to the MSC based on GSM phases. If this parameter is changed from 2 to any other value, and inter_rat_enabled is equal to 4, 5, 6 or 7 for any cell in that BSS, the BSS issues the following warning: Warning: phase2_classmark_allowed must support multiband for Enhanced 2G/3G. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No This parameter applies only to BSC sites. This parameter does not apply to RXCDR sites. If the Location Services feature is enabled and the operator attempts to change the phase2_classmark_allowed parameter to a value which does not support multiband, the command is rejected. This dependency is also checked during database verification (see the lcs_mode section).

Syntax
Change command string
chg_element phase2_classmark_allowed <value> 0

Display command string

disp_element phase2_classmark_allowed 0

6-650

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Values

Values
Value type Valid range Integer 0 to 2 0 1 2 Default value 0 Formatted for Phase 1 Formatted for Phase 2 Formatted for Phase 2 with Multiband

68P02901W23-S

6-651 Nov 2009

phase2_resource_ind_allowed

Chapter 6: CM database parameters

phase2_resource_ind_allowed

Description
The phase2_resource_ind_allowed parameter specifies the GSM Phase format the BSS uses to send Resource Request messages to the MSC. If this parameter is set to 0, the BSS sends the messages in the GSM Phase 1 format. If this parameter is set to 1, the BSS sends the messages in the GSM Phase 2 format. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No This parameter applies only to BSC sites. This parameter does not apply to RXCDR sites.

Syntax
Change command string
chg_element phase2_resource_ind_allowed <value> 0

Display command string

disp_element phase2_resource_ind_allowed 0

Values
Value type Valid range Boolean 0 or 1 0 1 Default value 0 GSM Phase 1 format GSM Phase 2 format

6-652

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

pic_error_clr_thresh

Description
The pic_error_clr_thresh parameter specifies the error count threshold (equal to or less than) for an alarm to be cleared for a Path Identity Code (PIC). Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No The ECERM feature must be unrestricted. Two successful calls are required to clear an alarm within this threshold. (One call may be too short for the Channel Coder Unit (CCU) to send an error indication, thus clearing the alarm prematurely.) This parameter can be set only at a BSC. If the threshold is increased during operation, any existing counts between the new and the old threshold does not clear an alarm until another successful call is made or the next successful GPRS time period occurs on the PIC. With the ECERM feature unrestricted, (pic_error_gen_thresh - pic_error_clr_thresh) must be greater than or equal to 2.

Syntax
Change command string
chg_element pic_error_clr_thresh <value> 0

Display command string

disp_element pic_error_clr_thresh 0

Values
Value type Valid range Default value Integer 0 to 253 0

68P02901W23-S

6-653 Nov 2009

pic_error_gen_thresh

Chapter 6: 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 Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No The ECERM feature must be unrestricted. This parameter can be set only at a BSC. If the threshold is reduced during operation, any existing counts between the new and the old threshold will not cause an alarm. With the ECERM feature unrestricted, (pic_error_gen_thresh - pic_error_clr_thresh) must be greater than or equal to 2.

Syntax
Change command string
chg_element pic_error_gen_thresh <value> 0

Display command string

disp_element pic_error_gen_thresh 0

Values
Value type Valid range Default value Integer 2 to 255 6

6-654

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

pic_error_inc

Description
The pic_error_inc parameter specifies the error count increment when the Enhanced Circuit Error Rate Monitor (ECERM) feature is in use for Path Identity Codes (PICs) on a per BSC basis. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No The ECERM feature must be unrestricted. This parameter can be set only at a BSC.

Syntax
Change command string
chg_element pic_error_inc <value> 0

Display command string

disp_element pic_error_inc 0

Values
Value type Valid range Integer 0 1 to 255 Default value 0 1 PIC alarms not raised. PIC alarms raised. If ECERM feature is restricted. If ECERM feature is not restricted

68P02901W23-S

6-655 Nov 2009

pool_gproc_preemption

Chapter 6: CM database parameters

pool_gproc_preemption

Description
The pool_gproc_preemption parameter specifies what type of preemption to use for pool GPROCs. When a pool GPROC running a function goes OOS and there are no available pool GPROCs, the INS pool GPROCs can be searched for a lower priority function. If such a function is found, it is bumped from its GPROC by the higher priority function. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No This parameter can be set only at a BSC. This parameter cannot be set at an RXCDR

Syntax
Change command string
chg_element pool_gproc_preemption <value> 0

Display command string

disp_element pool_gproc_preemption 0

Values
Value type Valid range Integer 0 to 2 0 1 2 Default value 1 No replacement Replacement based on function priority Replacement based on function and intra-function priorities

6-656

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

poor_initial_assignment

Description
The poor_initial_assignment parameter enables or disables checking the timing advance on a Random Access Channel (RACH). If the RACH is greater than ms_max_range, this indicates that there has been a poor initial assignment, and therefore the RACH is discarded. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No ms_max_range

Syntax
Change command string
chg_element poor_initial_assignment <value> <location>

Display command string

disp_element poor_initial_assignment <location>

Values
Value type Valid range Boolean 0 or 1 0 1 Default value 0 Disabled Enabled

68P02901W23-S

6-657 Nov 2009

pow_inc_step_size_dl

Chapter 6: 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. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes This parameter must be greater than or equal to pow_red_step_size_dl.

Syntax
Add/Change command strings
add_cell <gsm_cell_id> <location> chg_element pow_inc_step_size_dl <value> <location> <cell_desc> chg_cell_element pow_inc_step_size_dl <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full] disp_element pow_inc_step_size_dl <location> <cell_desc>

Values
Value type Valid range Default value Integer (dB) 2, 4, 6, 8, 10, 12 or 14 2

6-658

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

References

References
GSM parameter GSM specification POW_INC_STEP_SIZE_DL 12.20 - 5.2.8.23 - power Ctrl BTS - pow Incr Step Size

68P02901W23-S

6-659 Nov 2009

pow_inc_step_size_ul

Chapter 6: 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. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes This parameter must be greater than or equal to pow_red_step_size_ul.

Syntax
Add/Change command strings
add_cell <gsm_cell_id> <location> chg_element pow_inc_step_size_ul <value> <location> <cell_desc> chg_cell_element pow_inc_step_size_ul <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full] disp_element pow_inc_step_size_ul <location> <cell_desc>

Values
Value type Valid range Default value Integer (dB) 2, 4, 6, 8, 10 12 or 14 2

6-660

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

References

References
GSM parameter GSM specification POW_INC_STEP_SIZE_UL 12.20 - 5.2.8.23 - power Ctrl BTS - pow Incr Step Size

68P02901W23-S

6-661 Nov 2009

pow_red_step_size_dl

Chapter 6: 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. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes This parameter must be less than or equal to pow_inc_step_size_dl.

Syntax
Add/Change command strings
add_cell <gsm_cell_id> <location> chg_element pow_red_step_size_dl <value> <location> <cell_desc> chg_cell_element pow_red_step_size_dl <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full] disp_element pow_red_step_size_dl <location> <cell_desc>

Values
Value type Valid range Default value Integer (dB) 2 or 4 2

6-662

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

References

References
GSM parameter GSM specification POW_RED_STEP_SIZE_DL 12.20 - 5.2.8.23 - power Ctrl BTS - pow Red Step Size

68P02901W23-S

6-663 Nov 2009

pow_red_step_size_ul

Chapter 6: 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. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes Must be less than or equal to pow_inc_step_size_ul.

Syntax
Add/Change command strings
add_cell <gsm_cell_id> <location> chg_element pow_red_step_size_ul <value> <location> <cell_desc> chg_cell_element pow_red_step_size_ul <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full] disp_element pow_red_step_size_ul <location> <cell_desc>

Values
Value type Valid range Default value Integer (dB) 2 or 4 2

References
GSM parameter GSM specification POW_RED_STEP_SIZE_UL 12.20 - 5.2.8.23 - power Ctrl BTS - pow Red Step Size

6-664

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

power_save_enable

{34320G}

Description
The power_save_enable parameter enables or disables FR 34320G (SW enabler for PA bias switch on/off on CTU2D feature) on a per SITE basis. This parameter can be accessed and updated both in and out of sysgen mode. Type Supported by OMC-R GUI Cell description required Dependencies B (operator actions required) Yes No The value of this parameter can be set to 1 if the FR 34320G is enabled at the BSS. This parameter can only be enabled or disabled on Horizon II sites.

Syntax
Change command string
chg_element power_save_enable <value> <location>

Display command strings

disp_element power_save_enable <location>

Values
Value type Valid range Boolean 0 or 1 0 1 Default value 0 Disabled Enabled

68P02901W23-S

6-665 Nov 2009

prach_max_retran

Chapter 6: CM database parameters

prach_max_retran

Description
The prach_max_retran parameter specifies the maximum number of retransmissions allowed for each radio priority level (i) on a per cell basis. This parameter is always attached with a radio priority (i) of 0 to 3. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes The PBCCH/PCCCH optional feature must be unrestricted.

Syntax
Change command string
chg_element prach_max_retran,i <value> <location> <cell_desc> chg_cell_element prach_max_retran,i <value> <cell_desc_opt>

Display command string

disp_cell <cell_id> full disp_element prach_max_retran,i <location> <cell_desc>

Values
Value type Valid range Integer 0 to 3 0 1 2 3 Default value 2 Representing the number of retransmissions: 1 retransmission 2 retransmissions 4 retransmissions 7 retransmissions (4 retransmissions)

6-666

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

prach_s

Description
The prach_s parameter specifies the minimum number of frames between two successive Packet Channel request messages. It is actually the number of slots between two successive Packet Channel request messages on a per cell basis. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes The PBCCH/PCCCH optional feature must be unrestricted.

Syntax
Change command string
chg_element prach_s <value> <location> <cell_desc> chg_cell_element prach_s <value> <cell_desc_opt>

Display command string

disp_cell <cell_id> full disp_element prach_s <location>

68P02901W23-S

6-667 Nov 2009

Values

Chapter 6: CM database parameters

Values
Value type Valid range Integer (number of frames) 0 to 9 0 1 2 3 4 5 6 7 8 9 Valid range 8 representing the number of slots S: S = 12 S = 15 S = 20 S = 30 S = 41 S = 55 S = 76 S = 109 S = 163 S = 217 (S =163)

6-668

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

prach_tx_int

Description
The prach_tx_int parameter specifies the number of frame slots to spread the transmission of the random access. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes The PBCCH/PCCCH optional feature must be unrestricted.

Syntax
Change command string
chg_element prach_tx_int <value> <location> <cell_desc> chg_cell_element prach_tx_int <value> <cell_desc_opt>

Display command string

disp_cell <cell_id> full disp_element prach_tx_int <location> <cell_desc>

Values
Value type Valid range Default value Integer 0 to 15 14 number of frame slots (see Table 6-32) (32 slots)

68P02901W23-S

6-669 Nov 2009

Values

Chapter 6: CM database parameters

Table 6-32
Value 0 1 2 3 4 5 6 7

Values for prach_tx_int representing number of frame slots

Number of slots 2 slots 3 slots 4 slots 5 slots 6 slots 7 slots 8 slots 9 slots Value 8 9 10 11 12 13 14 15 Number of slots 10 slots 12 slots 14 slots 16 slots 20 slots 25 slots 32 slots 50 slots

6-670

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

primary_pcu

Description
The primary_pcu parameter maps a cell to a specific PCU, which then becomes the primary PCU, when more than one PCU is equipped at the BSC. If the primary PCU for a cell goes Out Of Service, the cell is assigned to the next redundant PCU (see pcu_redundancy parameter). If the primary PCU for a cell then returns In Service, the cell is remapped to the primary PCU. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes The GPRS feature must be unrestricted.

NOTE
When an attempt is made to change primary_pcu, and the requested PDTCHs exceed the GDS or PMC capacity on the PCU, the BSS accepts the request and issues a warning to indicate that there is not enough GDS or PMC resource available.

Syntax
Change command strings
chg_cell_element <location> primary_pcu <value> <cell_desc_opt> chg_element primary_pcu <value> location [<cell_desc>]

Display command strings

disp_element primary_pcu <location> <cell_desc>

68P02901W23-S

6-671 Nov 2009

Values

Chapter 6: CM database parameters

Values
Value type Valid range Integer {27955} -1or 0 -1 0 Default value -1 No primary PCU PCU_0 is the cell primary PCU

6-672

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

prioritize_microcell

Description
The prioritize_microcell parameter specifies whether the level (micro or macro) of the serving cell affects the sorting of the candidate list. If prioritize_microcell is set to 0, the Handovers (HO) level of the service cell does not affect sorting of the candidate list. If prioritize_microcell is set to 1, the level of the serving cell affects the sorting of the candidate list. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes The Microcell feature must be unrestricted.

Syntax
Change command strings
chg_element prioritize_microcell <value> <location> <cell_desc> chg_cell_element prioritize_microcell <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> <full> disp_element prioritize_microcell <location> <cell_desc>

Values
Value type Valid range Boolean 0 or 1 0 1 Default value 1 No impact on sorting Impact on sorting

68P02901W23-S

6-673 Nov 2009

priority_class

Chapter 6: CM database parameters

priority_class

Description
The priority_class specifies the Hierarchical Cell Structure (HCS) for a cell. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes The PBCCH/PCCCH optional feature must be unrestricted.

Syntax
Add/Change command strings
chg_element priority_class <value> <location> <cell_desc> chg_cell_element priority_class <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> full disp_element priority_class <location> <cell_desc>

Values
Value type Valid range Integer 0 to 7 0 7 Default value 0 lowest priority highest priority

6-674

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

protect_last_ts

Description
The protect_last_ts parameter specifies the switchability of PDTCH when there is one (and only one) switchable PDTCH on a carrier and none are reserved. When protect_last_ts is set to 1, the PDTCH may not be allocated to a voice call unless there is no data flowing or queued for that timeslot. Incoming handover may not be allocated to this timeslot. However, new calls may be allocated to the timeslot provided no data flow exists. When protect_last_ts is set to 0, there is no restriction and the last remaining switchable PDTCH can be taken for a voice call. The last timeslot available cannot be occupied by a CS call which is being handed-over to the cell when the cell has protect_last_ts enabled. For a CS handover to the last non-reserved PDTCH, there is a hand shake between CS and PS which takes too long for the handover to complete. It still works for non-handover usage. This is only an issue when there are no reserved PDTCHs. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes The GPRS feature must be unrestricted. Queuing must be enabled and the priority sent from the MSC in the assignment request must be a value between 1 and 14; if this is not done, the last timeslot acts like a reserved timeslot.

Syntax
Change command strings
chg_element protect_last_ts <value> <location> <cell_desc> chg_cell_element protect_last_ts <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> <full> disp_element protect_last_ts <location> <cell_desc>

68P02901W23-S

6-675 Nov 2009

Values

Chapter 6: CM database parameters

Values
Value type Valid range Boolean 0 or 1 0 1 Default value 0 Last timeslot is not protected. Last timeslot is protected.

6-676

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

prp_capacity_opt

Description
The prp_capacity_opt parameter indicates whether the Packet Resource Processor (PRP) capacity is unrestricted in the BSS software. If restricted, any attempt to access the other Enhanced Scheduling parameters is rejected. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No The GPRS feature must be unrestricted.

Syntax
Display command string
disp_options

Values
Value type Valid range Boolean 0 or 1 0 1 Default value None Restricted Unrestricted

68P02901W23-S

6-677 Nov 2009

prp_fanout_mode

Chapter 6: CM database parameters

prp_fanout_mode

{28000}

Description
The prp_fanout_mode parameter indicates the PDCHs fanout mode of the PRP in the PCU. The fanout mode of the PRP provides the preference of more PDCH capacity or higher throughput of the PRP . Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No Increase the Throughput of PRP with PCU optional feature must be unrestricted.

Syntax
Change command strings
chg_element prp_fanout_mode <value> <location>

Display command strings

disp_element prp_fanout_mode <location>

Values
Value type Valid range Integer 1 or 2 1 2 Default value 1 The rolling blackout mechanism is enabled on PCU. The PRP throughput increase feature is deactivated. The rolling blackout mechanism is disabled on PCU. The PRP throughput increase feature is activated.

6-678

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

prpThptOpt

{28000}

Description
The prpThptOpt parameter indicates whether the Increase PRP Throughput with PCU feature is unrestricted or not in the BSS software. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No If the prpThptOpt flag indicates that Increase the Throughput of PRP with PCU is restricted, attempts to change this feature specific database parameters will be rejected.

Syntax
Display command strings
disp_options

Values
Value type Valid range Default value Integer 0 to 1 N/A

68P02901W23-S

6-679 Nov 2009

prr_aggr_factor

Chapter 6: CM database parameters

prr_aggr_factor

Description
The prr_aggr_factor parameter represents a coefficient for a linear function to dynamically allocate or deallocate reserved PRR blocks. The aggressive factor of 0 specifies that each cell in the BSS system has gprs_min_prr_blks number of PRR blocks allocated. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No Modification of prr_aggr_factor has no effect for cells that have the pccch_enabled parameter enabled.

Syntax
Change command strings
chg_element prr_aggr_factor <value> <location>

Display command strings

disp_element prr_aggr_factor <location>

Values
Value type Valid range Default value Integer 0 to 4 3

6-680

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

psi_trau_fill_frames_threshold

Description
The new per BSS element psi_trau_fill_frames_threshold specifies the maximum allowable percentage of all TRAU frames transmitted that can be fill frames. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No None

Syntax
Change command strings
chg_element psi_trau_fill_frames_threshold <value> <location>

Display command strings

disp_element psi_trau_fill_frames_threshold <location>

Values
Value type Valid range Default value Integer 0 to 100 10

68P02901W23-S

6-681 Nov 2009

Pw_Save_SwitchOpt

Chapter 6: CM database parameters

Pw_Save_SwitchOpt

{34320G}

Description
The Pw_Save_SwitchOpt parameter indicates whether FR 34320G (SW enabler for PA bias switch on/off on CTU2D feature) is disabled or enabled at the BSS. Type Supported by OMC-R GUI Cell description required Dependencies B (operator actions required) Yes No None

Syntax
Display command strings
disp_options

Values
Value type Valid range Boolean 0 or 1 0 1 Default value N/A Disabled Enabled

6-682

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

pwr_handover_allowed

Description
The pwr_handover_allowed parameter enables or disables the power budget assessment for handovers. When enabled, a handover to cell n may be required if: PBGT(n) - ho_margin(n) > 0. This comparison ensures that the MS is always linked to the cell with the minimum path loss even though the quality and level thresholds may not have been exceeded. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes None

Syntax
Add/Change command strings
add_cell <gsm_cell_id> <location> chg_element pwr_handover_allowed <value> <location> <cell_desc> chg_cell_element pwr_handover_allowed <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full] disp_element pwr_handover_allowed <location> <cell_desc>

Values
Value type Valid range Boolean 0 or 1 0 1 Default value 1 Disabled Enabled

68P02901W23-S

6-683 Nov 2009

References

Chapter 6: CM database parameters

References
GSM parameter GSM specification EN_PBGT_HO 5.08 - Appendix A, 3.1f: PBGT(N) 12.20 - 5.2.8.18 - enable BSS Handover Control - enable Pwr Budget Handover

6-684

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

pwrc

Description
The pwrc parameter specifies whether the Broadcast Control Channels (BCCH) measurement are included in the averaged value of hopping frequencies. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes None

Syntax
Add/Change command strings
add_cell <gsm_cell_id> <location> chg_element pwrc <value> <location> <cell_desc> chg_cell_element pwrc <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full] disp_element pwrc <location> <cell_desc>

Values
Value type Valid range Boolean 0 or 1 0 1 Default value 1 Include BCCH measurement Do not include BCCH measurement

68P02901W23-S

6-685 Nov 2009

References

Chapter 6: CM database parameters

References
GSM parameter GSM specification PWRC GSM 4.08 5.08

6-686

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

qosP2Opt

{27703A}

Description
The qosP2Opt parameter indicates whether the Qos Phase 2 feature is Enabled/Disabled in the BSS. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes The QoS Phase 2 feature requires the QoS feature to be enabled.

Syntax
Display command strings
disp_options [all]

Values
Value type Valid range Boolean 0 or 1 0 1 Default value N/A Disabled Enabled

68P02901W23-S

6-687 Nov 2009

qos_mbr_enabled

Chapter 6: CM database parameters

qos_mbr_enabled

{27703A}

Description
The qos_mbr_enabled parameter enables or disables support of Max Bit Rate or Peak Bit Rate enforcement on a per BSS basis. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes The qos_mbr_enabled attribute is modified only if Qos Phase II is enabled/unrestricted at the OMC.

Syntax
Change command strings
chg_element qos_mbr_enabled <value> <location>

Display command strings

disp_element qos_mbr_enabled <location>

Values
Value type Valid range Boolean 0 or 1 0 1 Default value 0 Disabled Enabled

6-688

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

qos_mtbr_be_dl

Description
The qos_mtbr_be_dl parameter specifies the downlink Minimum Throughput Budget Requirement (in kbit/s) ranging from 2 to 6 for the Best Effort traffic class. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes The QoS feature must be unrestricted. The value of this parameter cannot be changed when bssgp_pfc_bit equals 1.

Syntax
Change command strings
chg_element qos_mtbr_be_dl <location> <cell_desc> chg_cell_element qos_mtbr_be_dl <location> <cell_desc_opt>

Display command strings

disp_cell <cell_id> <full> disp_element qos_mtbr_be_dl <location> <cell_desc>

Values
Value type Valid range Default value Integer 2 to 6 2

68P02901W23-S

6-689 Nov 2009

qos_mtbr_be_ul

Chapter 6: CM database parameters

qos_mtbr_be_ul

Description
The qos_mtbr_be_ul parameter the uplink Minimum Throughput Budget Requirement (in kbit/s) ranging from 2 to 6 for the Best Effort traffic class. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes The QoS feature must be unrestricted. The value of this parameter cannot be changed when bssgp_pfc_bit equals 1.

Syntax
Change command strings
chg_element qos_mtbr_be_ul <location> <cell_desc> chg_cell_element qos_mtbr_be_ul <location> <cell_desc_opt>

Display command strings

disp_cell <cell_id> <full> disp_element qos_mtbr_be_ul <location> <cell_desc>

Values
Value type Valid range Default value Integer 2 to 6 2

6-690

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

qos_mtbr_bg_dl

Description
The qos_mtbr_bg_dl parameter the downlink Minimum Throughput Budget Requirement (in kbit/s) ranging from 2 to 6 for the Background traffic class. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes The QoS feature must be unrestricted. The value of this parameter cannot be changed when bssgp_pfc_bit equals 1.

Syntax
Change command strings
chg_element qos_mtbr_bg_dl <location> <cell_desc> chg_cell_element qos_mtbr_bg_dl <location> <cell_desc_opt>

Display command strings

disp_cell <cell_id> <full> disp_element qos_mtbr_bg_dl <location> <cell_desc>

Values
Value type Valid range Default value Integer 2 to 6 2

68P02901W23-S

6-691 Nov 2009

qos_mtbr_bg_ul

Chapter 6: CM database parameters

qos_mtbr_bg_ul

Description
The qos_mtbr_bg_ul parameter the uplink Minimum Throughput Budget Requirement (in kbit/s) ranging from 2-6 for the Background traffic class. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes The QoS feature must be unrestricted. The value of this parameter cannot be changed when bssgp_pfc_bit equals 1.

Syntax
Change command strings
chg_element qos_mtbr_bg_ul <location> <cell_desc> chg_cell_element qos_mtbr_bg_ul <location> <cell_desc_opt>

Display command strings

disp_cell <cell_id> <full> disp_element qos_mtbr_bg_ul <location> <cell_desc>

Values
Value type Valid range Default value Integer 2 to 6 2

6-692

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

qos_mtbr_i1_dl

Description
The qos_mtbr_i1_dl parameter specifies the downlink Minimum Throughput Budget Requirement (in kbit/s) ranges from 2 to 24 for Interactive traffic class, traffic handling priority 1. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes The QoS feature must be unrestricted. The value of this parameter cannot be changed when bssgp_pfc_bit equals 1. The value of qos_mtbr_i1_dl must be greater than or equal to qos_mtbr_i2_dl.

Syntax
Change command strings
chg_element qos_mtbr_i1_dl <location> <cell_desc> chg_cell_element qos_mtbr_i1_dl <location> <cell_desc_opt>

Display command strings

disp_cell <cell_id> <full> disp_element qos_mtbr_i1_dl <location> <cell_desc>

Values
Value type Valid range Default value Integer 2 to 24 2

68P02901W23-S

6-693 Nov 2009

qos_mtbr_i1_ul

Chapter 6: CM database parameters

qos_mtbr_i1_ul

Description
The qos_mtbr_i1_ul parameter specifies the uplink Minimum Throughput Budget Requirement (in kbit/s) ranges from 2 to 6 for Interactive traffic class, traffic handling priority 1. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes The QoS feature must be unrestricted. The value of this parameter cannot be changed when bssgp_pfc_bit equals 1. The value of qos_mtbr_i1_ul must be greater than or equal to qos_mtbr_i2_ul.

Syntax
Change command strings
chg_element qos_mtbr_i1_ul <location> <cell_desc> chg_cell_element qos_mtbr_i1_ul <location> <cell_desc_opt>

Display command strings

disp_cell <cell_id> <full> disp_element qos_mtbr_i1_ul <location> <cell_desc>

Values
Value type Valid range Default value Integer 2 to 6 2

6-694

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

qos_mtbr_i2_dl

Description
The qos_mtbr_i2_dl parameter specifies the downlink Minimum Throughput Budget Requirement (in kbit/s) ranges from 2 to 24 for Interactive traffic class, traffic handling priority 2. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes The QoS feature must be unrestricted. The value of this parameter cannot be changed when bssgp_pfc_bit equals 1. The value of qos_mtbr_i2_dl must be less than or equal to the value of qos_mtbr_i1_dl for the same cell. The value of qos_mtbr_i2_dl must be greater than or equal to the value of qos_mtbr_i3_dl.

Syntax
Change command strings
chg_element qos_mtbr_i2_dl <location> <cell_desc> chg_cell_element qos_mtbr_i2_dl <location> <cell_desc_opt>

Display command strings

disp_cell <cell_id> <full> disp_element qos_mtbr_i2_dl <location> <cell_desc>

Values
Value type Valid range Default value Integer 2 to 24 2

68P02901W23-S

6-695 Nov 2009

qos_mtbr_i2_ul

Chapter 6: CM database parameters

qos_mtbr_i2_ul

Description
The qos_mtbr_i2_ul parameter specifies the uplink Minimum Throughput Budget Requirement (in kbit/s) ranges from 2 to 6 for Interactive traffic class, traffic handling priority 2. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes The QoS feature must be unrestricted. The value of this parameter cannot be changed when bssgp_pfc_bit equals 1. The value of qos_mtbr_i2_ul must be less than or equal to the value of qos_mtbr_i1_ul for the same cell. The value of qos_mtbr_i2_ul must be greater than or equal to the value of qos_mtbr_i3_ul.

Syntax
Change command strings
chg_element qos_mtbr_i2_ul <location> <cell_desc> chg_cell_element qos_mtbr_i2_ul <location> <cell_desc_opt>

Display command strings

disp_cell <cell_id> <full> disp_element qos_mtbr_i2_ul <location> <cell_desc>

Values
Value type Valid range Default value Integer 2 to 6 2

6-696

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

qos_mtbr_i3_dl

Description
The qos_mtbr_i3_dl parameter specifies the downlink Minimum Throughput Budget Requirement (in kbit/s) ranges from 2 to 6 for Interactive traffic class, traffic handling priority 3. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes The QoS feature must be unrestricted. The value of this parameter cannot be changed when bssgp_pfc_bit equals 1. The value of qos_mtbr_i3_dl must be less than or equal to the value of qos_mtbr_i2_dl for the same cell.

Syntax
Change command strings
chg_element qos_mtbr_i3_dl <location> <cell_desc> chg_cell_element qos_mtbr_i3_dl <location> <cell_desc_opt>

Display command strings

disp_cell <cell_id> <full> disp_element qos_mtbr_i3_dl <location> <cell_desc>

Values
Value type Valid range Default value Integer 2 to 6 2

68P02901W23-S

6-697 Nov 2009

qos_mtbr_i3_ul

Chapter 6: CM database parameters

qos_mtbr_i3_ul

Description
The qos_mtbr_i3_ul parameter specifies the uplink Minimum Throughput Budget Requirement (in kbit/s) ranges from 2 to 6 for Interactive traffic class, traffic handling priority 3. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes The QoS feature must be unrestricted. The value of this parameter cannot be changed when bssgp_pfc_bit equals 1. The value of qos_mtbr_i3_ul must be less than or equal to the value of qos_mtbr_i2_ul for the same cell.

Syntax
Change command strings
chg_element qos_mtbr_i3_ul <location> <cell_desc> chg_cell_element qos_mtbr_i3_ul <location> <cell_desc_opt>

Display command strings

disp_cell qos_mtbr_i3_ul <cell_id> <full> disp_element qos_mtbr_i3_ul <location> <cell_desc>

Values
Value type Valid range Default value Integer 2 to 6 2

6-698

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

qsearch_c

Description
The qsearch_c is like qsearch_i in idle mode. It defines a threshold and also indicates whether the MS shall measure a 3G neighbor cell or not when RXLEV of the serving GSM cell is below or above this threshold. The qsearch_c parameter is sent to a mobile in the Measurement Information message. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes The Enhanced 2G/3G Handover feature must be unrestricted.

Syntax
Change command strings
chg_element qsearch_c <value> <location> <cell_desc> chg_cell_element qsearch_c <value> <cell_desc_opt> copy_cell qsearch_c

Display command strings

disp_cell <cell_id> [full] disp_element qsearch_c <location> <cell_desc>

Values
Value type Valid range Default value Integer 0 to 15 15

68P02901W23-S

6-699 Nov 2009

qsearch_c_initial

Chapter 6: CM database parameters

qsearch_c_initial

Description
The qsearch_c_initial parameter is broadcast on the BCCH using the SYSTEM INFORMATION TYPE 2 quarter message to control the multi-RAT MS behavior in circuit switched dedicated mode. The parameter specifies whether qsearch_i is used by the MS in dedicated mode after a certain number of Measurement Information messages are received, or whether the MS should always search. The qsearch_c_initial parameter is configurable on a per cell basis. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes {31400} The BSS Inter-RAT feature or TD-SCDMA and GSM interworking feature must be unrestricted.

Syntax
Change command strings
chg_element qsearch_c_initial <value> <location> <cell_desc> chg_cell_element qsearch_c_initial <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> full disp_element qsearch_c_initial <location> <cell_desc>

6-700

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Values

Values
Value type Valid range Boolean 0 The MS uses qsearch_i until qsearch_c is reached.

1 Default value 0

The MS always searches irrespective of qsearch_i (MS always measures the strength of the neighbor cells)

68P02901W23-S

6-701 Nov 2009

qsearch_i

Chapter 6: CM database parameters

qsearch_i

Description
The multi-RAT MS uses the qsearch_i parameter to decide when to start measurement of a UTRAN neighbor cell. Measurement of a UTRAN neighbor cell starts when the received RF signal level of the serving GSM cell BCCH carrier is above or below the threshold defined by qsearch_i. The qsearch_i parameter is configurable on a per cell basis. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes {31400} The BSS Inter-RAT feature or TD-SCDMA and GSM interworking feature must be unrestricted.

Syntax
Change command strings
chg_element qsearch_i <value> <location> <cell_desc> chg_cell_element qsearch_i <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> <full> disp_element qsearch_i <location> <cell_desc>

6-702

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Values

Values
Value type Valid range Integer 0 to 15 Search for 3G cells if signal level is below (0 7) or above (8 15) threshold 0 = - 98 dBm 1 = - 94 dBm ... ... 6 = - 74 dBm 7 = (always) 8 = - 78 dBm 9 = - 74 dBm ... ... 14 = - 54 dBm 15 = (never)

Default value

68P02901W23-S

6-703 Nov 2009

qsearch_p

Chapter 6: CM database parameters

qsearch_p

Description
The qsearch_p parameter specifies the threshold below which a multi-RAT MS searches for 3G cells. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes The PBCCH/PCCCH optional feature must be unrestricted.

Syntax
Add/Change command strings
chg_element qsearch_p <value> <location> <cell_desc> chg_cell_element qsearch_p <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> full disp_element qsearch_p <location> <cell_desc>

Values
Value type Valid range Integer (1 step = 4 dBm) 0 to 7 8 to 15 Default value 0 For signal strengths below the threshold see Table 6-33 For signal strengths above the threshold see Table 6-34

6-704

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Values

Table 6-33

qsearch_p attribute values below threshold

Value 0 1 2 3 4 5 6 7 Range -98 dBm -94 dBm -90 dBm -86 dBm -82 dBm -78 dBm -74 dBm Infinity (always search for 3G cells)

Table 6-34

qsearch_p attribute values above threshold

Value 8 9 10 11 12 13 14 15 Range -78 dBm -74 dBm -70 dBm -66 dBm -62 dBm -58 dBm -54 dBm Infinity (never search for 3G cells)

68P02901W23-S

6-705 Nov 2009

queue_management_information

Chapter 6: CM database parameters

queue_management_information

Description
The queue_management_information parameter specifies the maximum number of MSs that may wait in a queue for channel assignment. A value of 0 indicates that queuing is not allowed. Type Supported by OMC-R GUI Cell description required Dependencies A (no operation action) Yes Yes The sum of (max_q_length_channel + max_q_length_sdcch) must be less than or equal to queue_management_information.

Syntax
Change command strings
chg_element queue_management_information <value> <location> <cell_desc> chg_cell_element queue_management_information <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> <full> disp_element queue_management_information <location> <cell_desc>

Values
Value type Valid range Default value Integer (representing the maximum number of MSs) 0 to 50 50

References
Internal name EN_Q_ALLOWED This is a Motorola parameter.

6-706

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

ra_color

Description
The ra_color parameter specifies the routing area color used in System Information messages for a specific cell and, therefore, indicates that GPRS is supported in the cell. Type Supported by OMC-R GUI Cell description required Dependencies B (operator actions required) Yes Yes The GPRS feature must be unrestricted. The ra_color parameter applies only to GPRS cells. If the local_maintenance flag is disabled, this parameter cannot be changed through the MMI. This parameter cannot be displayed until its value has been set. Once the value of ra_color has been set, it cannot be unset.

Operator actions

NOTE
BSS software processes using this parameter are not notified when the change is made. That is, this parameter can be modified without a reset to a particular device or function.

Syntax
Change command strings
chg_element ra_color <value> <location> <cell_desc> chg_cell_element ra_color <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> <full> disp_element ra_color <location> <cell_desc>

68P02901W23-S

6-707 Nov 2009

Values

Chapter 6: CM database parameters

Values
Value type Valid range Default value Integer (routing area color for a cell) 0 to 7 None

6-708

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

ra_reselect_hysteresis

Description
The ra_reselect_hysteresis parameter specifies the additional hysteresis that applies when selecting a cell in a new Routing Area (RA). Differences in received signal levels from 0 dB to 14 dB (in 2 dB increments) are used for cell reselection. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes The PBCCH/PCCCH optional feature must be unrestricted.

Syntax
Add/Change command strings
chg_element ra_reselect_hysteresis <value> <location> <cell_desc> chg_cell_element ra_reselect_hysteresis <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> full disp_element ra_reselect_hysteresis <location> <cell_desc>

68P02901W23-S

6-709 Nov 2009

Values

Chapter 6: CM database parameters

Values
Value type Valid range Integer 0 to 7 0 1 2 3 4 5 6 7 Default value None Represents the signal level differences: 0 dB 2 dB 4 dB 6 dB 8 dB 10 dB 12 dB 14 dB

6-710

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

rac

Description
The rac parameter specifies the routing area code (RAC) which is part of the cell identifier for GPRS cells. Type Supported by OMC-R GUI Cell description required Dependencies Operator actions B (operator actions required) Yes Yes This parameter applies only to GPRS cells. The GPRS feature must be unrestricted. This parameter cannot be displayed until value has been set. Once this value has been set, it cannot be unset.

NOTE
BSS software processes using this parameter are not notified when the change is made. That is, this parameter can be modified without a reset to a particular device or function.

Syntax
Change command strings
chg_element rac <value> <location> <cell_desc> chg_cell_element rac <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> <full> disp_element rac <location> <cell_desc>

NOTE
The RAC cannot be displayed if the operator has not previously configured or modified the value .

68P02901W23-S

6-711 Nov 2009

Values

Chapter 6: CM database parameters

Values
Value type Valid range Default value Integer (RAC for a cell) 0 to 255 None Null = unmodified

6-712

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

rach_load_period

Description
The rach_load_period parameter indicates how often to check for the RACH overload condition when the cell is not in RACH overload.

NOTE
Other parameters can affect flow control. Refer to ccch_load_period, rach_overload_threshold, ssm_normal_overload_threshold, ssm_normal_overload_threshold or tch_flow_control.

Type Supported by OMC-R GUI Cell description required Dependencies

A (no operator actions) Yes Yes This parameter must be less than or equal to ccch_load_period.

Syntax
Change command strings
chg_element rach_load_period <value> <location> <cell_desc> chg_cell_element rach_load_period <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> <full> disp_element rach_load_period <location> <cell_desc>

68P02901W23-S

6-713 Nov 2009

Values

Chapter 6: CM database parameters

Values
Value type Valid range Default value Integer 1 to 1020 16

References
Internal name RACH_MEAS_PERIOD This is a Motorola parameter.

6-714

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

rach_load_threshold

Description
The rach_load_threshold parameter specifies the threshold for RACH load. If the calculated RACH load exceeds this threshold, an overload condition is signaled and an access class is barred at the cell where the overload is occurring. If the RACH load exceeds rach_load_threshold, an overload indication is sent to Call Processing which may result in an access class being barred. The RACH load may be calculated in one of two ways based on the value of the rach_load_type parameter. RACH loading is expressed as the ratio of correct RACH accesses to the number of possible RACH accesses. Let T_SD_CHANNEL be the number of available traffic and standalone control (SDCCH) channels. The cell configuration determines this number. Let MAX_RACH be the number of possible RACH accesses per load period. MAX_RACH has a value of 204 for pure RACH (non-combined), and 108 for combined RACH channels. The number of correct RACH accesses can exceed the number of calls the cell can handle (T_SD_CHANNELS). In the case the RACH load threshold is set to a number higher than T_SD_CHANNELS/MAX_RACH, MSs are not barred until the RACH load threshold is met, but in the mean time attempted calls get rejected, once the cell runs out of available traffic channels. If the RACH load threshold is set to a value in the neighborhood of T_SD_CHANNELS/MAX_RACH, the system gradually prevents subscribers from entering the system as soon as the cell runs out of free traffic and standalone control channels. In both cases, the net effect is that calls are not completed. Table 6-35 lists example cell configurations and their corresponding rach_load_threshold values.

Table 6-35
Conf A B C

Example cell configurations for rach_load_threshold

Carriers 3 1 3 SDCCH 16 4 16 TCH 21 7 20 CCCH 1 1 2 Combined No Yes No T_SDM_R 18.1% 10.18% 08.8%

NOTE
Other parameters can affect flow control. Refer to ccch_load_period, rach_load_period, ssm_normal_overload_threshold, ssm_normal_overload_threshold or tch_flow_control.

68P02901W23-S

6-715 Nov 2009

Syntax

Chapter 6: CM database parameters

Type Supported by OMC-R GUI Cell description required Dependencies

A (no operator actions) Yes Yes If rach_load_type is 1, then the units for this parameter are (# correct RACH access/# incorrect RACH accesses). If rach_load_type is 0, then the units for this parameter are (# correct RACH access/# possible RACH accesses).

Syntax
Change command strings
chg_element rach_load_threshold <value> <location> <cell_desc> chg_cell_element rach_load_threshold <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> <full> disp_element rach_load_threshold <location> <cell_desc>

Values
Value type Valid range Default value Integer 0 to 1000 1000 (Disables flow control)

References
Internal name RACH_BUSY_THRES This is a Motorola parameter.

6-716

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

rach_load_type

Description
The rach_load_type parameter specifies the RACH loading calculation method. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No None

Syntax
Change command string
chg_element rach_load_type <value> <location>

Display command string

disp_element rach_load_type <location>

Values
Value type Valid range Boolean 0 or 1 0 1 Default value None Percentage of RACH opportunities used Percentage of total RACHs which are incorrect (collisions)

68P02901W23-S

6-717 Nov 2009

radio_link_timeout

Chapter 6: 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 an operator could reasonably be expected to hold while experiencing loss of audio. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes None

Syntax
Add/Change command strings
add_cell <cell_desc> <location> chg_element radio_link_timeout <value> <location> <cell_desc> chg_cell_element radio_link_timeout <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full] disp_element radio_link_timeout <location> <cell_desc>

6-718

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Values

Values
Value type Valid range Integer (1 step = 4 SACCH frames) 0 to 15 Represents the number of SACCH frames as shown below: 0 1 2 ... ... ... 15 Default value 4 4 SACCH frames 8 SACCH frames 12 SACCH frames ... ... ... 64 SACCH frames

References
GSM parameter GSM specification RADIO_LINK_TIMEOUT(MS) 3.5.2 to 3.5.2.2: radio link failure, mobile side and network side 4.08 - 10.5.2.3 - fig. 10.22, table 10.16

68P02901W23-S

6-719 Nov 2009

rapid_pwr_down

Chapter 6: CM database parameters

rapid_pwr_down

Description
The rapid_pwr_down parameter enables or disables the rapid power down procedure. The rapid power down procedure bypasses the pow_red_step_size values set in the database in an effort to bring the power of the MS to an acceptable level quickly. Detected MS power levels are averaged over the number of SACCH periods specified by the rpd_period parameter. This average is compared to the value specified for the rpd_trigger value. The rapid power down procedure is initiated when the calculated value is greater than the value specified for the rpd_trigger parameter. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes None

Syntax
Add/Change command strings
add_cell <cell_desc> <location> chg_element rapid_pwr_down <value> <location> <cell_desc> chg_cell_element rapid_pwr_down <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full] disp_element rapid_pwr_down <location> <cell_desc>

Values
Value type Valid range Boolean 0 or 1 0 1 Default value 0 Disabled Enabled

6-720

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

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 Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No Two successful calls are required on a resource before an alarm can be cleared within this threshold. One successful call may be too short for the Channel Coder Unit (CCU) to send an error indication, thus clearing the alarm prematurely. This parameter can be set only at a BSC. If the threshold is increased during operation, any existing counts between the new and the old threshold does not clear an alarm until another successful call is made or the next successful time period occurs on the CIC. (rci_error_gen_thresh - rci_error_clr_thresh) must be greater than or equal to 2.

Syntax
Change command string
chg_element rci_error_clr_thresh <value> 0

Display command string

disp_element rci_error_clr_thresh 0

Values
Value type Valid range Default value Integer 0 to 253 0

68P02901W23-S

6-721 Nov 2009

rci_error_gen_thresh

Chapter 6: CM database parameters

rci_error_gen_thresh

Description
The rci_error_gen_thresh parameter specifies the error count threshold (equal to or greater than) for an alarm to be generated for a Radio Channel Identifier (RCI). Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No This parameter can be set only at a BSC. If the threshold is changed during operation, no immediate alarm occurs. The new threshold takes effect only when the RCI error count changes. (rci_error_gen_thresh - rci_error_clr_thresh) must be greater than or equal to 2.

Syntax
Change command string
chg_element rci_error_gen_thresh <value> 0

Display command string

disp_element rci_error_gen_thresh 0

Values
Value type Valid range Default value Integer 2 to 255 6

WARNING
The BSS system is designed to accept values less than 6 for the rci_error_gen_thresh parameter for debug purposes only. It is not recommended to set thresholds lower than 6 during the normal operation.

6-722

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

rci_error_inc

Description
The rci_error_inc parameter specifies the error count increment when the Enhanced Circuit Error Rate Monitor (ECERM) feature is in use for Radio Channel Identifiers (RCIs) on a per BSC basis. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No 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 Valid range Integer 0 1 to 255 Default value 0 1 RCI alarms not raised RCI alarms raised If ECERM feature is restricted If ECERM feature is not restricted

68P02901W23-S

6-723 Nov 2009

reconfig_fr_to_hr

Chapter 6: CM database parameters

reconfig_fr_to_hr

Description
The reconfig_fr_to_hr parameter specifies the congestion level threshold. If this level is exceeded at the serving cell, then any existing half-rate capable Full-Rate calls are reassigned to Half-Rate traffic channels. Idle half-rate channels and free generic traffic channels in the cell must be available. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes The AMR feature and/or GSM Half Rate feature must be unrestricted.

Syntax
Add/Change command strings
chg_element reconfig_fr_to_hr <value> <location> <cell_desc> chg_cell_element reconfig_fr_to_hr <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> full disp_element reconfig_fr_to_hr <location> <cell_desc>

Values
Value type Valid range Percentage 0 to 101 101 Default value 101 Disables this parameter

6-724

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

red_loss_daily

Description
The red_loss_daily parameter specifies the synchronization loss, daily alarm level count on a T1 link. An alarm generates if the synchronization loss meets or exceeds the threshold in a given 24 hour period. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No None

Syntax
Change command string
chg_element red_loss_daily <value> <location>

Display command string

disp_element red_loss_daily <location>

Values
Value type Valid range Default value Integer (number of alarms) 0 to 65535 16

68P02901W23-S

6-725 Nov 2009

red_loss_oos

Chapter 6: CM database parameters

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 Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No None

Syntax
Change command string
chg_element red_loss_oos <value> <location>

Display command string

disp_element red_loss_oos <location>

Values
Value type Valid range Default value Integer (number of alarms) 0 to 65535 511

6-726

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

red_loss_hourly

Description
The red_loss_hourly parameter specifies the synchronization loss, hourly alarm level count on a T1 link. An alarm generates if the synchronization loss meets or exceeds the threshold in a given 60 minute period. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No None

Syntax
Change command string
chg_element red_loss_hourly <value> <location>

Display command string

disp_element red_loss_hourly <location>

Values
Value type Valid range Default value Integer (number of alarms) 0 to 65535 20

68P02901W23-S

6-727 Nov 2009

red_time_oos

Chapter 6: CM database parameters

red_time_oos

Description
The red_time_oos parameter specifies the synchronization loss time for a T1 circuit. If synchronization is lost for this period of time, the T1 circuit is taken Out Of Service (OOS). Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No None

Syntax
Change command string
chg_element red_time_oos <value> <location>

Display command string

disp_element red_time_oos <location>

Values
Valid type Valid range Integer (1 step = 100 milliseconds) 0 to 65535 0 1 2 ... 25 ... 65535 Default value 25 0 seconds 0.1 seconds 0.2 seconds ... 2.5 seconds ... 6553.5 seconds 6553500 milliseconds 2500 milliseconds 0 milliseconds 100 milliseconds 200 milliseconds

6-728

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

red_loss_restore

Description
The red_loss_restore parameter specifies the synchronization loss, restorable time limit for a T1 circuit. If a synchronization loss error does not occur within this period of time, the T1 circuit is brought back in service. The synchronization loss is controlled by the value assigned to the red_loss_oos parameter. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No None

Syntax
Change command string
chg_element red_loss_restore <value> <location>

Display command string

disp_element red_loss_restore <location>

Values
Valid type Valid range Integer (1 step = 100 milliseconds) 0 to 65535 0 1 2 ... 6000 ... 65535 Default value 600 0 seconds 0.1 seconds 0.2 seconds ... 600 seconds ... 6553.5 seconds 6553500 milliseconds 600000 milliseconds 0 milliseconds 100 milliseconds 200 milliseconds

68P02901W23-S

6-729 Nov 2009

reestablish_allowed

Chapter 6: CM database parameters

reestablish_allowed

Description
The reestablish_allowed parameter enables or disables call establishment. If a BTS detects that an MS has not sent up any measurement reports for n number of SACCH periods (where n is defined by the parameter radio_link_timeout), a radio link failure occurs. When enabled, the MS executes the GSM call re-establishment algorithm to determine which cell to use for the attempt to re-establish the call. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes None

Syntax
Add/Change command strings
add_cell <cell_desc> <location> chg_element reestablish_allowed <value> <location> <cell_desc> chg_cell_element reestablish_allowed <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full] disp_element reestablish_allowed <location> <cell_desc>

Values
Value type Valid range Boolean 0 or 1 0 1 Default value 0 Enabled Disabled

6-730

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

References

References
GSM parameter GSM specification RE 5.08 - 6.7.2: Call re-establishment algorithm. 408 - 3.5.2 to 3.5.2.2: radio link failure, mobile side and network side. 4.08 - 10.5.2.17, fig. 10.36, and 12.20 - 5.2.8.7, table 10.30: cell description - call reestablishment allowed

68P02901W23-S

6-731 Nov 2009

rel_tim_adv

Chapter 6: CM database parameters

rel_tim_adv

Description
The rel_tim_adv parameter is the relative timing advance value used in HDPC averaging processing. A bin_num must be specified with this command to indicate the location of the parameters to be modified. Only 0 or 1 may be specified for the bin_num. A alg_num must be also specified to indicate the averaging algorithm as unweighted (0). If a value of 255 is entered for the alg_num, the bin is considered to contain invalid data. After entering the chg_cell_element command for this parameter, the following prompts are displayed and values must be entered: Enter hreqave: Enter hreqt: When entering disp_element rel_tim_adv, a bin_num must be specified to identify the location of the parameters to be displayed. Type Supported by OMC-R GUI Cell description required Dependencies Operator actions B (operator actions required) Yes Yes When alg_num is set to 255, bin_num cannot be set equal to decision_1_tim_adv_av_alg Respond to the prompts after entering this command.

Syntax
Change command string
chg_cell_element rel_tim_adv, <bin_num> <alg_num> <cell_desc_opt>

Display command string

disp_cell <cell_id> <full> disp_element rel_tim_adv,<bin_num> <location> <cell_desc>

6-732

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Values

Values
Value type Valid range Integer alg_num value depends on different attributes: Attribute Hreqave Hreqt Permissible range 1 to 31 1 to 31 Default value 4 1

References
GSM specification 5.08 This is a Motorola defined parameter.

68P02901W23-S

6-733 Nov 2009

remote_loss_daily

Chapter 6: CM database parameters

remote_loss_daily

Description
The remote_loss_daily parameter specifies the threshold for the daily count of remote alarms. An alarm generates if this threshold is met or exceeded during a 24 hour period. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No 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 Valid range Default value Integer (represents the number of alarms) 0 to 65535 16

6-734

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

remote_loss_hourly

Description
The remote_loss_hourly parameter specifies the threshold for the hourly count of remote alarms. An alarm generates if this threshold is met or exceeded during a 60 minute period. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No remote_loss_daily should be always less than remote_loss_hourly.

Syntax
Change command string
chg_element remote_loss_hourly <value> <location>

Display command string

disp_element remote_loss_hourly <location>

Values
Value type Valid range Default value Integer (represents the number of alarms) 0 to 65535 20

68P02901W23-S

6-735 Nov 2009

remote_loss_oos

Chapter 6: CM database parameters

remote_loss_oos

Description
The remote_loss_oos parameter specifies the Out Of Service (OOS) threshold for the remote alarm. When this threshold is met or exceeded, the 2 Mbit/s circuit is taken OOS. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No None

Syntax
Change command string
chg_element remote_loss_oos <value> <location>

Display command string

disp_element remote_loss_oos <location>

Values
Value type Valid range Default value Integer (represents the number of alarms) 0 to 65535 511

6-736

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

remote_loss_restore

Description
The remote_loss_restore parameter specifies the wait time for restoring the 2 Mbit/s circuit to service. If no remote alarm indication errors are detected during this wait time, the 2 Mbit/s circuit returns to service. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No None

Syntax
Change command string
chg_element remote_loss_restore <value> <location>

Display command string

disp_element remote_loss_restore <location>

Values
Valid type Valid range Integer (1 step = 100 milliseconds) 0 to 65535 0 1 2 ... 600 ... 65535 Default value 600 0 seconds 0.1 seconds 0.2 seconds ... 60 seconds ... 6553.5 seconds 6553500 milliseconds 60000 milliseconds 0 milliseconds 100 milliseconds 200 milliseconds

68P02901W23-S

6-737 Nov 2009

remote_time_oos

Chapter 6: CM database parameters

remote_time_oos

Description
The remote_time_oos parameter specifies the remote alarm time period. If a remote alarm exists for this amount of time, the 2 Mbit/s circuit is taken Out Of Service (OOS). Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No None

Syntax
Change command string
chg_element remote_time_oos <value> <location>

Display command string

disp_element remote_time_oos <location>

6-738

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

red_time_restore

Description
The red_time_restore parameter specifies the synchronization loss restart time for a T1 link. If synchronization loss does not occur within this period of time, the T1 link returns to service. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No None

Syntax
Change command string
chg_element red_time_restore <value> <location>

Display command string

disp_element red_time_restore <location>

68P02901W23-S

6-739 Nov 2009

report_resource_tch_f_high_water_mark

Chapter 6: CM database parameters

report_resource_tch_f_high_water_mark

Description
The report_resource_tch_f_high_water_mark parameter specifies the high need threshold of a full rate traffic channel (TCH) for the resource indication procedure. When the number of available (idle) full rate TCHs falls below this threshold, the internal resource indication timer starts and the resource indication message is sent to the MSC. That is, the Resource Request message received from the MSC is indicating a spontaneous mode. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes Must be less than report_resource_tch_f_low_water_mark

Syntax
Add/Change command strings
add_cell <cell_desc> <location> chg_element report_resource_tch_f_high_water_mark <value> <location> <cell_desc> chg_cell_element report_resource_tch_f_high_water_mark <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full] disp_element report_resource_tch_f_high_water_mark <location> <cell_desc>

Values
Value type Valid range Default value Integer (represents the number of TCHs) 0 to 254 2

6-740

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

References

References
GSM specification 8.08 - 3.2.2.4: reported message format This is a Motorola parameter.

68P02901W23-S

6-741 Nov 2009

report_resource_tch_f_low_water_mark

Chapter 6: CM database parameters

report_resource_tch_f_low_water_mark

Description
The report_resource_tch_f_low_water_mark parameter specifies the low need threshold of a full rate traffic channel (TCH) for the resource indication procedure. When the number of available (idle) full rate TCHs rises above this threshold, the internal resource indication timer stops (if it is running). That is, the Resource Request message received from the MSC is indicating a spontaneous mode. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes Must be greater than report_resource_tch_f_high_water_mark

Syntax
Add/Change command strings
add_cell <cell_desc> <location> chg_element report_resource_tch_f_low_water_mark <value> <location> <cell_desc> chg_cell_element report_resource_tch_f_low_water_mark <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full] disp_element report_resource_tch_f_low_water_mark <location> <cell_desc>

Values
Value type Valid range Default value Integer (number of TCHs) 1 to 255 12

6-742

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

References

References
GSM specification 8.08 - 3.2.2.4: reported message format This is a Motorola parameter.

68P02901W23-S

6-743 Nov 2009

res_gprs_pdchs

Chapter 6: CM database parameters

res_gprs_pdchs

Description
The res_gprs_pdchs parameter specifies the number of PDCH timeslots reserved in a cell.

NOTE
The equip RTF parameter with the same name is now obsolete.

Type Supported by OMC-R GUI Cell description required Dependencies

A (no operator actions) Yes Yes The GPRS feature must be unrestricted. The value of the res_gprs_pdchs parameter cannot be higher than the total number of timeslots available in the cell. The sum of the res_gprs_pdchs and switch_gprs_pdchs parameters must be greater than or equal to 0 and less than or equal to 30, and cannot be higher than the total number of timeslots in the cell. The primary PCU must be specified.

NOTE
When an attempt is made to change res_gprs_pdchs, and the requested PDTCHs exceed the GDS or PMC capacity on the PCU, the BSS accepts the request and issues a warning to indicate that there is not enough GDS or PMC resource available.

Syntax
Change command strings
chg_element res_gprs_pdchs <value> <location> <cell_desc> chg_cell_element res_gprs_pdchs <value> <cell_desc_opt>

6-744

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Values

Display command strings

disp_cell <cell_id> <full> disp_element res_gprs_pdchs <location> <cell_desc>

Values
Value type Valid range Default value Integer (represents the number of PDCHs) 0 to 30 0

68P02901W23-S

6-745 Nov 2009

res_ts_less_one_carrier

Chapter 6: CM database parameters

res_ts_less_one_carrier

Description
The res_ts_less_one_carrier parameter specifies the maximum number of timeslots that the BSS can allocate as reserved Packet Data Channels (PDCHs) in a cell when one of the GPRS carriers in the cell goes Out Of Service. The value of (res_gprs_pdchs minus res_ts_less_one_carrier) is subtracted from res_ts_less_one_carrier for each additional carrier that is lost. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes The GPRS feature must be unrestricted. RTFs must be equipped in the database. The BSS verifies whether there are enough carriers equipped in the database to support the value set by this parameter and the sw_ts_less_one_carrier parameter, and that the combined total does not exceed 30. The primary PCU must be specified.

NOTE
BSS software processes using this parameter are notified immediately after the change is made. When an attempt is made to change res_ts_less_one_carrier, and the requested PDTCHs exceed the GDS or PMC capacity on the PCU, the BSS accepts the request and issues a warning to indicate that there is not enough GDS or PMC resource available.

Syntax
Change command strings
chg_element res_ts_less_one_carrier <value> <location> <cell_desc> chg_cell_element res_ts_less_one_carrier <value> <cell_desc_opt>

6-746

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Values

Display command strings

disp_cell <cell_id> <full> disp_element res_ts_less_one_carrier <location> <cell_desc>

Values
Value type Valid range Default value Integer (timeslots) 0 to 30 Until set, assumes the value of res_gprs_pdchs

68P02901W23-S

6-747 Nov 2009

rf_res_ind_period

Chapter 6: CM database parameters

rf_res_ind_period

Description
The rf_res_ind_period parameter specifies the RF resource indication period. During this period, the idle channel is categorized. The idle channel categories are reported to the CRM by the RSS. The idle channel categories are: X1, X2, X3, X4, and X5. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No 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 Valid range Default value Integer (1 Step = 1 SACCH multiframe) 1 to 127 10

References
Internal name RF_RES_IND_PERIOD This is a Motorola parameter.

6-748

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

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 Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes This parameter must be less than rpd_trigger. The parameter rapid_pwr_down must be enabled.

Syntax
Add/Change command strings
add_cell <cell_desc> <location> chg_element rpd_offset <value> <location> <cell_desc> chg_cell_element rpd_offset <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full] disp_element rpd_offset <location> <cell_desc>

Values
Value type Valid range Default value Integer (1 dBm) 0 to 63 8

68P02901W23-S

6-749 Nov 2009

rpd_period

Chapter 6: CM database parameters

rpd_period

Description
The rpd_period parameter specifies the number of SACCH frames used to calculate a rolling average of uplink rxlev values. Detected MS power levels are averaged over the number of SACCH periods specified by the rpd_period parameter. This average is compared to the value specified for the rpd_trigger value. The rapid power down procedure initiates when the calculated value is greater than the value specified for the rpd_trigger parameter. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes The parameter rapid_pwr_down must be enabled.

Syntax
Add/Change command strings
add_cell <cell_desc> <location> chg_element rpd_period <value> <location> <cell_desc> chg_cell_element rpd_period <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full] disp_element rpd_period <location> <cell_desc>

Values
Value type Valid range Default value Integer (SACCH periods) 1 to 32 2

6-750

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

rpd_trigger

Description
The rpd_trigger parameter specifies the threshold used to initiate the rapid power down procedure. Detected MS power levels are averaged over the number of SACCH periods specified by the rpd_period parameter. This average is compared to the value specified for the rpd_trigger value. The rapid power down procedure initiates when the calculated value is greater than the value specified for the rpd_trigger parameter. The receive uplink power level is equal to rpd_trigger minus rpd_offset. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes This parameter must be greater than l_rxlev_ul_p. This parameter must be greater than rpd_offset. The parameter rapid_pwr_down must be enabled.

Syntax
Add/Change command strings
add_cell <cell_desc> <location> chg_element rpd_trigger <value> <location> <cell_desc> chg_cell_element rpd_trigger <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full] disp_element rpd_trigger <location> <cell_desc>

68P02901W23-S

6-751 Nov 2009

Values

Chapter 6: CM database parameters

Values
Value type Valid range Integer 0 to 63 Each step represents an increase of 1 dBm, from -110 dBm to -47 dBm, as shown below: 0 1 2 ... ... ... 63 Default value 45 -110 dBm and lower -109 dBm -108 dBm ... ... ... -47 dBm and higher (- 65 dBm)

6-752

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

rpt_bad_qual_no_mr

Description
The rpt_bad_qual_no_mr parameter specifies how to signify the RXQUAL measurement when the rxqual measurement report is lost in the measurement report from the BSS. When rpt_bad_qual_no_mr is set to 0, the missed RXQUAL measurement report is left blank and it is not used to signify the RXQUAL measurement. When rpt_bad_qual_no_mr is set to 1, the worst quality value, RXQUAL 7, is used to signify the RXQUAL measurement if the rxqual measurement is lost in the measurement report from the BSS. When rpt_bad_qual_no_mr is set to 2, the previous value of RXQUAL is used to signify the RXQUAL measurement if the rxqual measurement is lost in the measurement report from the BSS. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes None

Syntax
Change command strings
chg_element rpt_bad_qual_no_mr <value> <location> <cell_desc> chg_cell_element rpt_bad_qual_no_mr <value> <cell_desc_opt>

Display command strings

disp_cell <desc_id> <full> disp_element rpt_bad_qual_no_mr <location> <cell_desc>

68P02901W23-S

6-753 Nov 2009

Values

Chapter 6: CM database parameters

Values
Value type Valid range Integer 0 to 2 0 1 The missed RXQUAL measurement report is left blank and it is not used to signify the RXQUAL measurement. The worst quality value, RXQUAL 7, is used to signify the RXQUAL measurement if the rxqual measurement is lost in the measurement report from the BSS. The previous value of RXQUAL is used to signify the RXQUAL measurement if the rxqual measurement is lost in the measurement report from the BSS

Default value

6-754

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

rsl_lcf_congestion_thi

Description
The rsl_lcf_congestion_thi parameter specifies the RSL Congestion Control (RCC) high congestion threshold at which an RSL-LCF board is in congestion status, so that MTL-LCF can stop sending paging message to the board. The RCC high congestion threshold represents a percentage of the total number of RSLs that the RSL-LCF board services. The board is in congestion status when it detects the percentage number of congested RSLs is more than or equal to the high congestion threshold value. The system responds with an error message and rejects the value of rsl_lcf_congestion_thi if set to a value which is less than the current value of rsl_lcf_congestion_tlow parameter (see rsl_lcf_congestion_tlow on page 6-756). Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No The rsl_lcf_congestion_thi parameter must be greater than rsl_lcf_congestion_tlow parameter.

Syntax
Add/Change command strings
chg_element rsl_lcf_congestion_thi <value> bsc

Display command strings

disp_element rsl_lcf_congestion_thi bsc

Values
Value type Valid range 1 to 100 Default value 60 Integer (in steps of 1%)

68P02901W23-S

6-755 Nov 2009

rsl_lcf_congestion_tlow

Chapter 6: CM database parameters

rsl_lcf_congestion_tlow

Description
The rsl_lcf_congestion_tlow parameter specifies the RSL Congestion Control (RCC) low congestion threshold at which an RSL-LCF board is out of congestion status, so that MTL-LCF can resume sending paging message to the board. The RCC low congestion threshold represents a percentage of the total number of RSLs that the RSL-LCF board services. The board is out of congestion status when it detects the percentage number of congested RSLs is less than or equal to the low congestion threshold value. The system responds with an error message and rejects any value of rsl_lcf_congestion_tlow parameter if set to a value which is equal to or greater than the current value of rsl_lcf_congestion_thi parameter (see rsl_lcf_congestion_thi on page 6-755). Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No The rsl_lcf_congestion_tlow parameter must be less than rsl_lcf_congestion_thi parameter.

Syntax
Add/Change command strings
chg_element rsl_lcf_congestion_tlow <value> bsc

Display command strings

disp_element rsl_lcf_congestion_tlow bsc

Values
Value type Valid range Default value Integer (in steps of 1%) 0 to 99 25

6-756

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

rtf_path_enable

Description
The rtf_path_enable parameter enables or disables the RTF Fault Containment feature. Type Supported by OMC-R GUI Cell description required Dependencies Operator actions B (operator actions required) Yes No The RTF Fault Containment feature must be unrestricted. This parameter can be used only at the BSC. 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 Valid range Boolean 0 or 1 0 1 Default value 0 Disabled Enabled

68P02901W23-S

6-757 Nov 2009

rxlev_access_min

Chapter 6: CM database parameters

rxlev_access_min

Description
The rxlev_access_min parameter specifies the minimum received signal level (dBm) required for an MS to access the system. The range -110 dBm to -47 dBm is used to set the minimum received signal level which in turn is used in path loss criterion parameter, C1. Set to a value corresponding to a signal level at which a call can be maintained in a particular environment. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes None

Syntax
Add/Change command strings
add_cell <cell_desc> <location> chg_element rxlev_access_min <value> <location> <cell_desc> chg_cell_element rxlev_access_min <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full] disp_element rxlev_access_min <location> <cell_desc>

6-758

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Values

Values
Value type Valid range Integer 0 to 63 0 1 2 ... ... ... 63 Default value 0 Each step represents an increase of 1 dBm, from -110 dBm to -47 dBm, as shown below: -110 dBm and lower -109 dBm -108 dBm ... ... ... -47 dBm and higher (- 110 dBm)

References
GSM parameter GSM specification RXLEV_ACCESS_MIN 4.08 - 10.5.2.4, fig. 10.23, table 10.17 5.08 - 6.2: conditions for MS camping on a cell 5.08 - 6.4: C1 equation 12.20 - 5.2.8.12 - radio Link Ctl DL - rx Lev Access Min 12.20 - 5.2.8.2

68P02901W23-S

6-759 Nov 2009

rxlev_dl_ho

Chapter 6: CM database parameters

rxlev_dl_ho

Description
The rxlev_dl_ho parameter specifies the averaging algorithm data for making handover decisions for the downlink receive signal level. Specify a bin_num with this command to indicate the location of the parameters to be modified. Specify a alg_num to indicate the averaging algorithm as unweighted (0). If a value of 255 is entered for the alg_num, the bin is considered to contain invalid data. After entering the chg_cell_element command for this parameter, the following prompts are displayed and values must be entered: Enter hreqave: Enter hreqt: A bin_num is used with the disp_element rxlev_dl_ho command to identify the location of the parameters to be displayed. Type Supported by OMC-R GUI Cell description required Dependencies B (operator actions required) Yes Yes When alg_num is set to 255, bin_num cannot be set to equal one of the following parameters: decision_1_dl_rxlev_av_h decision_1_dl_rxlev_av_ih decision_1_p_bgt_rxlev_av_h Respond to the prompts after entering this command.

Operator actions

Syntax
Change command string
chg_cell_element rxlev_dl_ho, <bin_num> <alg_num> <cell_desc_opt>

Display command strings

dis_cell <cell_desc> <full> disp_element rxlev_dl_ho,<bin_num> <location> <cell_desc>

6-760

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Values

Values
Value type Valid range Integer alg_num value depends on different attributes: Attribute Hreqave Hreqt Permissible range 1 to 31 1 to 31 Default value 4 1

References
GSM parameter GSM specification A_LEV_HO, A_PBGT_HO 5.08

68P02901W23-S

6-761 Nov 2009

rxlev_dl_pc

Chapter 6: CM database parameters

rxlev_dl_pc

Description
The rxlev_dl_pc parameter specifies the averaging parameters for making power control decisions for the downlink receive signal level. Specify a bin_num with this command to indicate the location of the parameters to be modified. Specify a alg_num to indicate the averaging algorithm as unweighted (0). If a value of 255 is entered for the alg_num, the bin is considered to contain invalid data. After entering the chg_cell_element command for this parameter, the following prompts are displayed and values must be entered: Enter hreqave: Enter hreqt: When entering disp_element rxlev_dl_pc, specify bin_num to identify the location of the parameters to be displayed. Type Supported by OMC-R GUI Cell description required Dependencies Operator actions B (operator actions required) Yes Yes When alg_num is set to 255, bin_num cannot be set equal to decision_1_dl_rxlev_av_p. Respond to the prompts after entering this command.

Syntax
Change command string
chg_cell_element rxlev_dl_pc, <bin_num> <alg_num> <cell_desc_opt>

Display command strings

disp_cell <cell_id> <full> disp_element rxlev_dl_pc,<bin_num> <location> <cell_desc>

6-762

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Values

Values
Value type Valid range Integer alg_num value depends on different attributes: Attribute Hreqave Hreqt Permissible range 1 to 31 1 to 31 Default value 4 1

References
GSM parameter GSM specification A_LEV_PC 5.08

68P02901W23-S

6-763 Nov 2009

rxlev_dl_zone

Chapter 6: CM database parameters

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 Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes The Concentric Cells feature must be enabled and the inner_zone_alg type must be set to 1.

Syntax
Change command strings
chg_element rxlev_dl_zone <value> <location> <cell_desc> chg_cell_element rxlev_dl_zone <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> <full> disp_element rxlev_dl_zone <location> <cell_desc>

6-764

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Values

Values
Value type Valid range Integer 0 to 63 Each step represents an increase of 1 dBm, from -110 dBm to -47 dBm, as shown below: 0 1 2 ... ... ... 63 Default value 63 -110 dBm and lower -109 dBm -108 dBm ... ... ... -47 dBm and higher (- 47 dBm)

68P02901W23-S

6-765 Nov 2009

rxlev_min_def

Chapter 6: CM database parameters

rxlev_min_def

Description
The rxlev_min_def parameter specifies the default value for rxlev_min_cell. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes None

Syntax
Add/Change command strings
add_cell <cell_desc> <location> chg_element rxlev_min_def <value> <location> <cell_desc> chg_cell_element rxlev_min_def <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full] disp_element rxlev_min_def <location> <cell_desc>

6-766

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Values

Values
Value type Valid range Integer 0 to 63 Each step represents an increase of 1 dBm, from -110 dBm to -47 dBm, as shown below: 0 1 2 ... ... ... 63 Default value 15 -110 dBm and lower -109 dBm -108 dBm ... ... ... -47 dBm and higher (-95 dBm)

References
GSM specification 5.08 - Appendix A - Table 1 This is a Motorola defined parameter.

68P02901W23-S

6-767 Nov 2009

rxlev_ul_ho

Chapter 6: CM database parameters

rxlev_ul_ho

Description
The rxlev_ul_ho parameter specifies the averaging parameters for making handover decisions for the uplink receive signal level. Specify a bin_num with this command to indicate the location of the parameters to be modified. Specify a alg_num to indicate the averaging algorithm as unweighted (0). If a value of 255 is entered for the alg_num, the bin is considered to contain invalid data. After entering the chg_cell_element command for this parameter, the following prompts are displayed and values must be entered: Enter hreqave: Enter hreqt: When entering disp_element rxlev_ul_ho, specify bin_num to identify the location of the parameters to be displayed. Type Supported by OMC-R GUI Cell description required Dependencies Operator actions B (operator actions required) Yes Yes When alg_num is set to 255, bin_num cannot be set equal to decision_1_ul_rxlev_av_h or decision_1_ul_rxlev_av_ih. Respond to the prompts after entering this command.

Syntax
Change command string
chg_cell_element rxlev_ul_ho, <bin_num> <alg_num> <cell_desc_opt>

Display command strings

disp_cell <cell_id> <full> disp_element rxlev_ul_ho,<bin_num> <location> <cell_desc>

6-768

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Values

Values
Value type Valid range Integer alg_num value depends on different attributes: Attribute Hreqave Hreqt Permissible range 1 to 31 1 to 31 Default value 4 1

The range of the product of hreqave and hreqt is 1 to 32.

References
GSM parameter GSM specification A_LEV_HO 5.08

68P02901W23-S

6-769 Nov 2009

remote_time_restore

Chapter 6: CM database parameters

remote_time_restore

Description
The remote_time_restore parameter sets the remote alarm restorable time. If the remote alarm ceases for this period of time, the 2 Mbit/s circuit returns to service. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No None

Syntax
Change command string
chg_element remote_time_restore <value> <location>

Display command string

disp_element remote_time_restore <location>

6-770

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

rxlev_ul_zone

Description
The rxlev_ul_zone parameter specifies the uplink receive level threshold that must be crossed for a handover to take place between the inner zone and the outer zone. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes The Concentric Cells Option must be enabled and the inner_zone_alg parameter must be set to 1.

Syntax
Change command strings
chg_element rxlev_ul_zone <value> <location> <cell_desc> chg_cell_element rxlev_ul_zone <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> <full> disp_element rxlev_ul_zone <location> <cell_desc>

Values

Chapter 6: CM database parameters

Values
Value type Valid range Integer alg_num value depends on different attributes: Attribute Hreqave Hreqt Qual_weight Permissible range 1 to 31 1 to 31 0 to 255 Default value 4 1 1

References
GSM parameter GSM specification A_QUAL_PC 5.08

6-780

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

sap_audit_type

Description
The sap_audit_type parameter specifies the type of audit to be run on a device at a specific site. When this parameter is displayed using the disp_element command, a numeric value is presented which corresponds to the values shown in the Valid range field (such as sap_audit_type = 0). The device is specified as an index value when entering the disp_element command. The index values available for use are described under Indices on page 1-40. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) No No None

Syntax
Change command string
This parameter cannot be modified from the MMI.

Display command string

disp_element sap_audit_type,<index> <location>

Values
Value type Valid range Integer 0 to 2, 255 0 1 2 255 Default value 255 Safe (Safe Tests) int_lpbk (Internal Loopback Tests) Self test No audit

68P02901W23-S

6-781 Nov 2009

sap_device_type

Chapter 6: CM database parameters

sap_device_type

Description
The sap_device_type parameter specifies the type of device on which an audit runs at a specific site. When this parameter is displayed using the disp_element command, the device type is displayed as an alphabetic character string (such as sap_device_type = DRI). The device is specified as an index value when entering the disp_element command. The index values available for use are described under Indices on page 1-40. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) No No None

Syntax
Change command strings
This parameter cannot be modified from the MMI.

Display command string

disp_element sap_device_type,<index> <location>

Values
Value type Valid range Default value Text N/A None

6-782

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

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-40. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) No No None

Syntax
Change command strings
chg_audit_sched <location> <device_name> <audit_type> <start_time_hour> <start_time_min><end_time_hour> <end_time_min> <interval_hour> <interval_min>

Display command string

disp_element sap_end_time,<index> <location>

Values
Value type Valid range Integer Hours Minutes Default value None 0 to 23 0 to 59

68P02901W23-S

6-783 Nov 2009

sap_interval

Chapter 6: CM database parameters

sap_interval

Description
The sap_interval parameter specifies the interval for a device audit. When this parameter is displayed using the disp_element command, the time is presented in military standard time or GMT (such as sap_interval = 13:45). The device is specified as an index value when entering the disp_element command. The index values available for use are described under Indices on page 1-40. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) No No None

Syntax
Change command strings
chg_audit_sched <location> <device_name> <audit_type> <start_time_hour> <start_time_min><end_time_hour> <end_time_min> <interval_hour> <interval_min>

Display command string

disp_element sap_interval,<index> <location>

NOTE
sap_interval = interval_hour:interval_min

Values
Value type Valid range Integer Hours Minutes Default value None 0 to 23 0 to 59

6-784

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

sap_start_time

Description
The sap_start_time parameter specifies the start time for a device audit. When this parameter is displayed using the disp_element command, the time is presented in military standard time or GMT (such as sap_end_time = 13:45). The device is specified as an index value when entering the disp_element command. The index values available for use are described under Indices on page 1-40. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) No No None

Syntax
Change command strings
chg_audit_sched <location> <device_name> <audit_type> <start_time_hour> <start_time_min><end_time_hour> <end_time_min> <interval_hour> <interval_min>

Display command string

disp_element sap_start_time,<index> <location>

NOTE
sap_interval = interval_hour:interval_min

Values
Value type Valid range Integer Hours Minutes Default value None 0 to 23 0 to 59

68P02901W23-S

6-785 Nov 2009

sccp_bssap_mgt

Chapter 6: CM database parameters

sccp_bssap_mgt

Description
The sccp_bssap_mgt parameter enables or disables ITU-TSS SCCP Management. When enabled, the BSS detects Signaling Point Inaccessible and loss of BSSAP subsystem. The BSS also handles the following messages: User Part Unavailable (UPU), Subsystem prohibited (SSP), Subsystem Allowed (SSA), and Subsystem Test (SST). (Use with Ericsson MSC). When disabled, the BSS always responds to an SST with an SSA message. Set this flag only if the MSC does ITU-TSS SCCP Management. All BTS site values are set to the same value assigned to site 0. Type Supported by OMC-R GUI Cell description required Dependencies Operator actions B (operator actions required) No No This parameter applies only to the BSC. Place the system in the SYSGEN ON mode before using the chg_element command to change this parameter.

Syntax
Change command string
chg_element sccp_bssap_mgt <value> 0

Display command string

disp_element sccp_bssap_mgt 0

Values
Value type Valid range Boolean 0 or 1 0 1 Default value 1 Disabled Enabled

6-786

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

scr_enabled

Description
The scr_enabled parameter specifies whether the Seamless Cell Reselection feature is enabled at a BSC, or not. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No The Seamless Cell Reselection feature must be available before it can be enabled with this parameter. This parameter can be set in or out of SYSGEN mode. Operator actions: None

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

Syntax
Change command string
chg_element scr_enabled <value> <location>

Display command string

disp_element scr_enabled <location>

Values
Value type Valid range Boolean 0 or 1 0 1 Default value 0 Seamless cell reselection is not enabled (off) Seamless cell reselection is enabled (on)

68P02901W23-S

6-787 Nov 2009

sdcch_ho

Chapter 6: CM database parameters

sdcch_ho

Description
The sdcch_ho parameter enables or disables handovers on the SDCCH. When enabled, handovers are not allowed until at least (sdcch_timer_ho * 2) measurement report periods have elapsed. To allow handovers on the SDCCH with a minimum delay, the sdcch_ho parameter must be enabled and the sdcch_timer_ho parameter set to its minimum value of 1. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes External SDCCH handover must be enabled at and supported by the MSC The handover_required_curr_ch parameter must be set to 1 so as to include the information element in the handover required message to the MSC.

Syntax
Add/Change command strings
add_cell <gsm_cell_id> <location> chg_element sdcch_ho <value> <location> <cell_desc> chg_cell_element sdcch_ho <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full] disp_element sdcch_ho <location> <cell_desc>

6-788

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Values

Values
Value type Valid range Boolean 0 or 1 0 1 Default value 1 Disabled Enabled

References
Internal name EN_SDCCH_HO

68P02901W23-S

6-789 Nov 2009

sdcch_need_high_water_mark

Chapter 6: CM database parameters

sdcch_need_high_water_mark

Description
The sdcch_need_high_water_mark parameter specifies the number of idle SDCCHs to trigger reconfiguration of traffic channels to SDCCHs. If dynamic reconfiguration is enabled and the total number of idle SDCCHs is less than the value of the sdcch_need_high_water_mark, the CRM tries to reconfigure TCHs to make more SDCCHs. The total number of SDCCHs cannot exceed the value of the max_number_of_sdcchs parameter.

NOTE
For stable operation of the channel reconfiguration process, the difference between the values for sdcch_need_high_water_mark and sdcch_need_low_water_mark must be greater than or equal to 9.

Type Supported by OMC-R GUI Cell description required

A (no operator actions) Yes Yes

Syntax
Change command strings
chg_element sdcch_need_high_water_mark <value> <location> <cell_desc> chg_cell_element sdcch_need_high_water_mark <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full] disp_element sdcch_need_high_water_mark <location> <cell_desc>

6-790

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Values

Values
Value type Valid range Default value Integer (representing the number of idle SDCCHs) 1 to 119 2

References
GSM specification 5.02 - 6.4 This is a Motorola defined parameter.

68P02901W23-S

6-791 Nov 2009

sdcch_need_low_water_mark

Chapter 6: CM database parameters

sdcch_need_low_water_mark

Description
The sdcch_need_low_water_mark parameter specifies the number of idle SDCCHs to trigger reconfiguration of SDCCHs (from previous TCH to SDCCH reconfigurations) back to TCHs. When dynamic channel reconfiguration is enabled, and when the number of idle SDCCHs available goes above the sdcch_need_low_water_mark value, reconfiguration of SDCCHs to TCHs is triggered as long as the total number of SDCCHs after reconfiguration stays above the number_sdcchs_preferred value. Ensure that the low water mark is checked only when an SDCCH is released. Once the number of idle SDCCHs is greater than the low water mark, SDCCH to TCH reconfiguration is triggered. If CRM is reconfiguring an SDCCH to TCH and the low water mark is passed again, reconfiguration is not triggered. It is triggered when the first reconfiguration is complete and an SDCCH is released.

NOTE
For stable operation of the channel reconfiguration process, the difference between the values for sdcch_need_high_water_mark and sdcch_need_low_water_mark must be greater than or equal to 9.

Type Supported by OMC-R GUI Cell description required

A (no operator actions) Yes Yes

Syntax
Change command strings
chg_element sdcch_need_low_water_mark <value> <location> <cell_desc> chg_cell_element sdcch_need_low_water_mark <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full] disp_element sdcch_need_low_water_mark <location> <cell_desc>

6-792

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Values

Values
Value type Valid range Default value Integer (number of SDCCHs) 10 to 128 12

References
GSM specification 5.02 - 6.4 This is a Motorola defined parameter.

68P02901W23-S

6-793 Nov 2009

sdcch_tch_band_reassign_delay

Chapter 6: 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 neighbor. This parameter applies to multiband MSs only. Use of this parameter may cause a delay in call setup of up to two seconds. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes The Multiband Inter-cell Handover feature must be unrestricted.

Syntax
Change command strings
chg_element sdcch_tch_band_reassign_delay <value> <location> <cell_desc> chg_cell_element sdcch_tch_band_reassign_delay <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full] disp_element sdcch_tch_band_reassign_delay <location> <cell_desc>

Values
Value type Valid range Default value Integer (number of measurement report periods) 0 to 4 0

6-794

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

sdcch_timer_ho

Description
The sdcch_timer_ho parameter specifies the wait time (measured in SACCH multiframes) before a handover on the SDCCH may occur. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes The sdcch_ho parameter must be enabled. (This is not monitored by the system.)

Syntax
Add/Change command strings
add_cell <gsm_cell_id> <location> chg_element sdcch_timer_ho <value> <location> <cell_desc> chg_cell_element sdcch_timer_ho <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full] disp_element sdcch_timer_ho <location> <cell_desc>

68P02901W23-S

6-795 Nov 2009

Values

Chapter 6: CM database parameters

Values
Value type Valid range Integer (1 Step = 2 SACCH multiframes) 1 to 31 1 2 3 ... ... ... 31 Default value 1 2 SACCH multiframes 4 SACCH multiframes 6 SACCH multiframes ... ... ... 62 SACCH multiframes

References
GSM parameter T_SDCCH_HO_ALLOWED This is a Motorola parameter.

6-796

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

search_prio_3g

Description
The search_prio_3g parameter specifies whether 3G cells are searched when BSIC coding is required. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes The PBCCH/PCCCH feature must be unrestricted for this parameter to change.

Syntax
Add/Change command strings
chg_element search_prio_3g <value> <location> <cell_desc> chg_cell_element search_prio_3g <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> full disp_element search_prio_3g <location> <cell_desc>

Values
Value type Valid range Boolean 0 or 1 0 1 Default value 1 3G cells are not searched when BSIC coding is required. 3G cells are searched when BSIC coding is required.

68P02901W23-S

6-797 Nov 2009

second_asgnmnt

Chapter 6: CM database parameters

second_asgnmnt

Description
The second_asgnmnt parameter enables or disables the Second Assignment procedure. With this parameter enabled, the RRSM initiates a second assignment procedure if it receives an assignment failure from the MS for the first assignment. In situations where first TCH assignment fails and the MS successfully recovers to the SDCCH, this parameter enables a second TCH assignment attempt. The purpose of this parameter is to improve overall TCH assignment success and call set-up success. To ensure that the true cause of initial assignment is not masked, a second attempt failure results in an unsuccessful assignment message being sent to the SSM. Even if the second assignment failure is a result of a lack of resources or equipment failure, rather than RF failure, the cause values are not used. The following lists the impacts when this parameter is enabled: Enabled on a per BSS basis. Initiated only for MSC assignments (not for intra-cell handovers). Increased SDCCH utilization for those call set-ups which fail first assignment. MSC Assignment Complete Timer. Additional statistics pegging on analysis software. The BSS does not preempt a call during the second assignment attempt for an emergency call when there are no resources available. The BSS does not trigger Directed Retry procedures if the cell is congested (that is, no resources are available) when a second assignment is initiated for a call. The BSS attempts to assign a TCH from a different carrier, starting from the outer most zone, until an available channel is found. However, assignments from the zone's interior are not made to the qualified zone of the MS. The BSS attempts to assign a different TCH within the requested band on the same carrier if a TCH from a different carrier is not available. An extended range TCH from a different carrier is assigned to an extended range MS during the second assignment.

6-798

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Syntax

An extended range TCH from a different carrier is assigned to a normal range MS if there are no normal range channels available. This assignment starts from the outer most zone. The BSS does not attempt a multiband handover during the second assignment if the MS is multiband capable. A (no operator actions) No No None

Type Supported by OMC-R GUI Cell description required Dependencies

Syntax
Change command strings
chg_element second_asgnmnt <value> 0

Display command strings

disp_element second_asgnmnt 0

Values
Value type Valid range Boolean 0 or 1 0 1 Default value 0 Disabled Enabled

68P02901W23-S

6-799 Nov 2009

secondary_freq_type

Chapter 6: 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. This parameter is set as the primary frequency type when a cell is not configured as a Dual Band cell. Type Supported by OMC-R GUI Cell description required Dependencies This parameter may be modified only when changing inner_zone_alg to 3 with the chg_cell_element command. At Dual Band Cells: When the Cell frequency type is set to PGSM or EGSM, the secondary_freq_type can only be set to DCS1800. When the Cell frequency is set to DCS1800, the secondary_freq_type can only be set to PGSM or EGSM. A (no operator actions) No No

At non-Dual Band cells, the secondary_freq_type is set to the primary frequency type.

Syntax
Change command string
chg_cell_element =secondary_freq_type <value> <location>

Display command string

disp_element secondary_freq_type <location>

6-800

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Values

Values
Value type Valid range Integer 1 to 8 1 2 4 8 Default value None binary values as shown below: PGSM EGSM DCS1800 PCS 1900

68P02901W23-S

6-801 Nov 2009

serving_band_reporting

Chapter 6: CM database parameters

serving_band_reporting

Description
The serving_band_reporting parameter indicates the number of cells report from the frequency band to which the serving GSM cell belongs. The serving_band_reporting parameter is sent to a mobile in the Measurement Information message. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes The Enhanced 2G/3G Handover feature must be unrestricted to modify this parameter.

Syntax
Change command string
chg_element serving_band_reporting <location> <cell_desc> chg_cell_element serving_band_reporting <location> <cell_desc_opt>

Display command string

disp_cell <cell_id> [full] disp_element serving_band_reporting <location> <cell_desc>

Values
Value type Valid range Default value Integer 0 to 3 3

6-802

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

sgsn_release

Description
The sgsn_release parameter specifies whether the release version (year of release) of the Serving GPRS Support Node (SGSN) for the BSS, is 1999 or later. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No The GPRS optional feature must be unrestricted.

Syntax
Change command string
chg_element sgsn_release <value> 0

Display command string

disp_element sgsn_release 0

Values
Value type Valid range Integer (number of frames) {27703A} 0 to 2 0 1 {27703A} 2 Default value 0 SGSN is compliant with 3GPP Release 1998 or older. SGSN is compliant with 3GPP Release 1999 to any version before Release 6. SGSN is compliant with 3GPP Release 6 to newer.

68P02901W23-S

6-803 Nov 2009

sig_lnk_tst_allow

Chapter 6: CM database parameters

sig_lnk_tst_allow

Description
The sig_lnk_tst_allow parameter specifies whether a Signaling Link Test Message (SLTM) is allowed to be sent to the remote MTP L3. When this parameter is enabled, the BSS sends the SLTM to the remote MTP L3 if the MTL initial alignment procedure is successful. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No None

Syntax
Change command string
chg_element sig_lnk_tst_allow <value> <location>

Display command string

disp_element sig_lnk_tst_allow <location>

Values
Value type Valid range Default value Boolean 0 or 1 1

6-804

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

slip_loss_daily

Description
The slip_loss_daily parameter specifies the threshold for the frame slip daily alarm count. An alarm generates if the count of frame slips meets or exceeds this threshold in a 24 hour period. Consider slip_loss_daily as the first level of notification of slip loss, and slip_loss_hourly alarm as a higher level indicating a more serious problem. For example, if slip_loss_daily is set to 20 and slip_loss_hourly to 25, and 20 slip loss problems occur during the day, the daily alarm triggers. The hourly alarm triggers only if 25 alarms occur within the hour, which indicates a much more serious problem. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) No No This parameter must be less than slip_loss_hourly.

Syntax
Change command string
chg_element slip_loss_daily <value> <location>

Display command string

disp_element slip_loss_daily <location>

Values
Value type Valid range Default value Integer 0 to 65534 4

68P02901W23-S

6-805 Nov 2009

slip_loss_hourly

Chapter 6: CM database parameters

slip_loss_hourly

Description
The slip_loss_hourly parameter specifies the threshold for the frame slip hourly alarm level count. An alarm generated if the count of frame slips exceeds this threshold in a 60 minute period. Consider slip_loss_daily as the first level of notification of slip loss, and slip_loss_hourly alarm as a higher level indicating a more serious problem. For example, if slip_loss_daily is set to 20 and slip_loss_hourly to 25, and 20 slip loss problems occur during the day, the daily alarm triggers. The hourly alarm triggers only if 25 alarms occur within the hour, which indicates a much more serious problem. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) No No This parameter must be greater than slip_loss_daily.

Syntax
Change command string
chg_element slip_loss_hourly <value> <location>

Display command string

disp_element slip_loss_hourly <location>

Values
Value type Valid range Default value Integer 1 to 65535 10

NOTE
MSI-2 boards default to a value of 20 on power-up. However, when MSI-2 boards are brought in-service they default to whatever value is set in the database.

6-806

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

slip_loss_oos

Description
The slip_loss_oos parameter specifies the threshold for the frame slip out of service (OOS) alarm level count. The 2 Mbit/s circuit is taken out of service if the number of frame slips exceeds this threshold during a 24 hour period. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) No No None

Syntax
Change command string
chg_element slip_loss_oos <value> <location>

Display command string

disp_element slip_loss_oos <location>

Values
Value type Valid range Default value Integers 0 to 65535 255

68P02901W23-S

6-807 Nov 2009

slip_loss_restore

Chapter 6: CM database parameters

slip_loss_restore

Description
The slip_loss_restore parameter specifies the frame slip restorable time period. If no errors occur during this period, the 2 Mbit/s circuit is brought back into service. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) No No 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 Valid range Integer (1 step = 100 milliseconds 0 to 65535 0 1 2 ... 600 ... 65535 Default value 600 0 seconds 0.1 seconds 0.2 seconds ... 60 seconds ... 6553.5 seconds 60 seconds 6553500 milliseconds 60000 milliseconds 60000 milliseconds 0 milliseconds 100 milliseconds 200 milliseconds

6-808

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

smg_gb_vers

Description
The smg_gb_vers parameter specifies the SMG version being adopted by the BSS over the Gb interface. Type Supported by OMC-R GUI Cell description required Dependencies Operator actions B (operator actions required) Yes No The GPRS feature must be unrestricted. 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 Valid range Default value Integer 24 to 31 31

68P02901W23-S

6-809 Nov 2009

sms_dl_allowed

Chapter 6: CM database parameters

sms_dl_allowed

Description
The sms_dl_allowed parameter enables or disables downlink (MS terminated) Short Message Service (SMS). Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No The SMS Point to Point feature must be unrestricted.

Syntax
Change command string
chg_element sms_dl_allowed <value> <location>

Display command string

disp_element sms_dl_allowed <location>

Values
Value type Valid range Boolean 0 or 1 0 1 Default value 0 Disabled Enabled

References
GSM specification 3.04 This is a Motorola defined parameter.

6-810

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

sms_tch_chan

Description
The sms_tch_chan parameter specifies the logical radio channel for the Short Message Service (SMS) transfer in the event of a call being present on a traffic channel. The FACCH is tried first, and if this fails, the SACCH is used. If the current radio channel is an SDCCH, the SDCCH is used. Choosing to provide an SMS on the FACCH provides more opportunity to deliver the message. The timing constraints on the SACCH allow a block to be transferred every 208 frames, while the FACCH allows a block to be delivered every 8 frames. The disadvantage of the FACCH channel is that frames are stolen, with injurious effects on the audio quality or data transmission. Stealing frames on the FACCH is more noticeable as the size of the short message increases, but using the SACCH for larger short messages means longer delivery times.

NOTE
SMS on the FACCH is not covered in the GSM specifications and may not be supported by mobile stations.

Type Supported by OMC-R GUI Cell description required Dependencies

A (no operator actions) No No 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>

68P02901W23-S

6-811 Nov 2009

Values

Chapter 6: CM database parameters

Values
Value type Valid range Integer 0 to 2 0 1 2 Default value 2 BSS_ALGORITHM FACCH always used SACCH always used

References
GSM specification 3.04 This is a Motorola defined parameter.

6-812

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

sms_ul_allowed

Description
The sms_ul_allowed parameter enables or disables uplink (MS originated) Short Message Service (SMS). Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No The SMS Point to Point feature must be unrestricted.

Syntax
Change command string
chg_element sms_ul_allowed <value> <location>

Display command string

disp_element sms_ul_allowed <location>

Values
Value type Valid range Boolean 0 or 1 0 1 Default value 0 Disabled Enabled

References
GSM specification 3.04 This is a Motorola defined parameter.

68P02901W23-S

6-813 Nov 2009

ss7_mode

Chapter 6: CM database parameters

ss7_mode

Description
The ss7_mode parameter specifies the type of SS7 for the BSC. This parameter permits the ITU or ANSI version to be selected. The ITU C7 version is consistent with the GSM specifications. The ANSI version is used to support PCS1900 applications in the United States. This parameter can be changed only when the operator is in SYSGEN ON mode. It can only be changed for site 0. All BTS site values are set to the same value assigned to site 0. When the ss7_mode parameter is changed, the system compares the value to the settings for dpc and opc. If the three variables are not compatible, the system rejects the change and displays an error message. The error message displays only if lcs_mode is 2 and lb_int_dpc is in range, or if lcs_mode is not 2. Type Supported by OMC-R GUI Cell description required Dependencies B (operator actions required) No No The system checks the values of the opc (see opc on page 6-621) and dpc (see dpc on page 6-227) variables and compares them to the value of ss7_mode. If the ranges are not compatible, the system rejects the changes. This parameter requires a location value of 0 or bsc. If the operator attempts to change the SS7 mode element to a value which causes the Lb-interface DPC to be out of range, the command is rejected. If the operator attempts to change the SS7 mode element to a value which causes the Lb-interface DPC and either the dpc, opc, or both, to be out of range, the command is rejected. Place the system in the SYSGEN ON mode to change this parameter.

Operator actions

Syntax
Change command strings
chg_element ss7_mode <value> <location>

6-814

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Values

Display command strings

disp_element ss7_mode <location>

Values
Value type Valid range Boolean 0 or 1 0 1 Default value 0 ITU version ANSI version

68P02901W23-S

6-815 Nov 2009

ssm_critical_overload_threshold

Chapter 6: CM database parameters

ssm_critical_overload_threshold

Description
The ssm_critical_overload_threshold parameter specifies the usage of call information blocks, as expressed by the ratio of the number of active calls to the maximum number of calls the SSM can handle (which is 800 for GPROC2 and GPROC3, and 400 for GPROC1). After this threshold has been met or exceeded, no MS originated calls are allowed. The remaining SSM resources are used to accommodate handover of existing calls. Every time the usage meets or exceeds this threshold, two access classes are barred. This number has to be greater than the ssm_normal_overload_threshold parameter.

NOTE
Other parameters can affect flow control. Refer to ccch_load_period, rach_load_period, rach_load_threshold, ssm_normal_overload_threshold or tch_flow_control.

Type Supported by OMC-R GUI Cell description required Dependencies

A (no operator actions) No No Must be greater than the ssm_normal_overload_threshold parameter. This parameter applies only to the BSC.

Syntax
Change command string
chg_element ssm_critical_overload_threshold <value> 0

Display command string

disp_element ssm_critical_overload_threshold 0

6-816

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Values

Values
Value type Valid range Default value Integer (percent of call information blocks in use) 0 to 100 80

68P02901W23-S

6-817 Nov 2009

ssm_normal_overload_threshold

Chapter 6: CM database parameters

ssm_normal_overload_threshold

Description
The ssm_normal_overload_threshold parameter specifies the usage of call information blocks, as expressed by the ratio of the number of active calls to the maximum number of calls the SSM can handle (which is 800 for GPROC2 and GPROC3, and 400 for GPROC1). Every time the usage equals or exceeds this threshold, one access class is barred.

NOTE
Other parameters can affect flow control. Refer to ccch_load_period, rach_load_period, rach_load_threshold, ssm_critical_overload_threshold or tch_flow_control.

Type Supported by OMC-R GUI Cell description required Dependencies

A (no operator actions) No No Must be less than the ssm_critical_overload_threshold parameter. This parameter applies only to the BSC.

Syntax
Change command string
chg_element ssm_normal_overload_threshold <value> 0

Display command string

disp_element ssm_normal_overload_threshold 0

Values
Value type Valid range Default value Integer (percent of call information blocks in use) 0 to 100 70

6-818

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

ssp_burst_delay

Description
The ssp_burst_delay parameter specifies the length of time between the bursts of data. The ssp_burst_limit parameter specifies the number of messages in each burst. Statistical information is forwarded from the Site Statistics Process (SSP) to the Central Statistics Process (CSP) in bursts. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) No No None

Syntax
Change command string
chg_element ssp_burst_delay <value> <location>

Display command string

disp_element ssp_burst_delay <location>

Values
Value type Valid range Default value Integer (milliseconds) 0 to 2500 200

68P02901W23-S

6-819 Nov 2009

ssp_burst_limit

Chapter 6: CM database parameters

ssp_burst_limit

Description
The ssp_burst_limit parameter specifies the number of messages included in each burst. The ssp_burst_delay parameter specifies the length of time between bursts. Statistical information is forwarded from the Site Statistical Process (SSP) to the Central Statistical Process (CSP) in bursts. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) No No None

Syntax
Change command string
chg_element ssp_burst_limit <value> <location>

Display command string

disp_element ssp_burst_limit <location>

Values
Value type Valid range Default value Integer (number of messages) 1 to 65535 10

6-820

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

stat_interval

Description
The stat_interval parameter sets the time, in minutes, that the statistics file is reported to the OMC-R. If the operator fails to reset the interval to 30 minutes, the OMC-R calculations of the Key Statistics and Health Indicators are interrupted for the entire period until the interval is reset. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) No No Must be set to 30 or 60 minutes to align with the OMC-R.

Syntax
Change command string
chg_element stat_interval <value> 0

Display command string

disp_element stat_interval 0

Values
Value type Valid range Default value Integer (minutes) 5 to 60 30

NOTE
Any value between 5 minutes and 60 minutes is valid, the OMC-R only parses uploaded statistics files if this attribute is set to 30 minutes or 60 minutes.

68P02901W23-S

6-821 Nov 2009

stop_dri_tx_enable

Chapter 6: CM database parameters

stop_dri_tx_enable

Description
The stop_dri_tx_enable parameter enables/disables the Stop Tx when CELL OOS feature that allows the operator the option to adjust the period of time between a CELL going OOS, and the radios to stop transmitting. The operator can adjust this value at any time, but changes do not have effect for any Cell transitioning at that time. Type Supported by OMC-R GUI Security level Cell description required Dependencies Operator actions A (no operator actions) Yes 3 No This parameter is only valid at the BSC. None

Syntax

Change command string

chg_element stop_dri_tx_enable <value> 0

Display command string

disp_element stop_dri_tx_enable <location>

Values
Value type Valid range Boolean 0 to 1 0 1 If set to No (0), the DRIs do not stop transmitting when the cell goes OOS. If set to Yes (1), the DRIs continue transmitting for the length of time specified in stop_dri_tx_time before transitioning to the D-U: CELL OOS state.

Default value

6-822

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

stp_pc

{30340}

Description
The stp_pc parameter is the point code of the adjacent signaling point (STP). Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No The existing element dpc should be set to the point code of the MSC.

Syntax
Change command strings
chg_ele stp_pc <value> 0

Display command strings

disp_ele stp_pc 0

Values
Value type Valid range Default value Integer 0 to 16383 0

68P02901W23-S

6-823 Nov 2009

stp_pc_enabled

Chapter 6: CM database parameters

stp_pc_enabled

{30340}

Description
The stp_pc_enabled parameter enables the BSS to connect MTL through STP . Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No None

Syntax
Change command strings
chg_ele stp_pc_enabled <value> 0

Display command strings

disp_ele stp_pc_enabled 0

Values
Value type Valid range Boolean 0 or 1 0 1 Default value 0 Disabled Enabled

6-824

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

stream_downgrade_enabled

{27703A}

Description
The stream_downgrade_enabled parameter enables or disables the downgrading of GBR and Transfer Delay of an admitted PFC during future retention procedures to a lower value than the initially committed. stream_downgrade_enabled controls negotiation of GBR, TD, MaxSDUsize, besides RT-nRT downgrade. Type Supported by OMC-R GUI Cell description required Dependencies B (operator actions required) Yes Yes This attribute can only be modified only if Qos Phase II is enabled or unrestricted at the OMC

Syntax
Change command strings
chg_element stream_downgrade_enabled <value> <location>

Display command strings

disp_element stream_downgrade_enabled <location>

Values
Value type Valid range Boolean 0 or 1 0 1 Default value 1 Not allowed to set the GBR to a lower value than committed Allowed to set the GBR to a lower value than committed

68P02901W23-S

6-825 Nov 2009

streaming_enabled

Chapter 6: CM database parameters

streaming_enabled

{27703A}

Description
The streaming_enabled parameter provides streaming support per BSS when enabled and if the operator disables the attribute, then the support for all streaming traffic class, all existing streaming or conversational PFCs are deleted by the BSS. Type Supported by OMC-R GUI Cell description required Dependencies B (operator actions required) Yes Yes This attribute can only be modified only if Qos Phase II is enabled or unrestricted at the OMC

Syntax
Change command strings
chg_element streaming_enabled <value> <location>

Display command strings

disp_element streaming_enabled <location>

Values
Value type Valid range Boolean 0 or 1 0 1 Default value 0 Disabled Enabled

6-826

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

surround_cell

Description
The surround_cell parameter specifies the averaging parameter for a serving cell's neighbor cells. The system uses this parameter to determine which neighbor cell to hand off to. Specify a bin_num with this command to indicate the location of the parameters to be modified. Specify a alg_num to indicate the averaging algorithm as unweighted (0). If a value of 255 is entered for the alg_num, the bin is considered to contain invalid data. After entering the chg_cell_element command for this parameter, the following prompts are displayed and values must be entered: Enter hreqave: Enter hreqt: When entering disp_element surround_cell, specify bin_num to identify the location of the parameters to be displayed. Type Supported by OMC-R GUI Cell description required Dependencies Operator actions B (operator actions required) Yes Yes When alg_num is set to 255, bin_num cannot be set equal to decision_1_pbgt_rxlev_av_h. Respond to the prompts after entering this command.

Syntax
Change command string
chg_cell_element surround_cell, <bin_num> <alg_num> <cell_desc_opt>

Display command string

disp_cell <cell_id> <full> disp_element surround_cell,<bin_num> <location> <cell_desc>

68P02901W23-S

6-827 Nov 2009

Values

Chapter 6: CM database parameters

Values
Value type Valid range Default value Integer 0 to 255 None

References
GSM parameter GSM specification A_PBGT_HO 5.08

6-828

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

sw_pdtch_priority

Description
The sw_pdtch_priority defines the priority level of switchable PDTCH resources. This prevents calls with priority level greater than the PDTCH priority level from stealing PDTCH resources when the eMLPP feature is unrestricted. The highest priority is 1. Greater than means numerically greater, that is, 4 is greater than 3 but is a lower priority. Therefore, calls with priority 4 to 14 cannot steal switchable PDTCH when sw_pdtch_priority is set to 3. Setting sw_pdtch_priority to 14 disables priority protection and allows all calls to allocate switchable PDTCH resources. Type Supported by OMC-R GUI Cell description required Dependencies A (No operator actions) Yes Yes The eMLPP feature must be unrestricted.

Syntax
Change command string
chg_element sw_pdtch_priority <value> 0

Display command string

disp_element sw_pdtch_priority <location>

Values
Value type Valid range Default value Integer 1 to 14 14

68P02901W23-S

6-829 Nov 2009

sw_ts_less_one_carrier

Chapter 6: CM database parameters

sw_ts_less_one_carrier

Description
The sw_ts_less_one_carrier parameter specifies the number of timeslots that the BSS should allocate as switchable between (Traffic) TCH and (Packet Data) PDCH in a cell when one of the carriers in the cell goes Out Of Service (OOS). The value of (switch_gprs_pdchs minus sw_ts_less_one_carrier) is subtracted from sw_ts_less_one carrier for each additional carrier that is lost. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes The GPRS feature must be unrestricted. RTFs must be equipped in the database. The BSS verifies whether there are enough carriers equipped in the database to support the value set by this parameter and the res_ts_less_one_carrier parameter and that the combined total does not exceed 30. The primary PCU must be specified.

NOTE
BSS software processes using this parameter are notified immediately after the change is made. When an attempt is made to change sw_ts_less_one_carrier, and the requested PDTCHs exceed the GDS or PMC capacity on the PCU, the BSS accepts the request and issues a warning to indicate that there is not enough GDS or PMC resource available.

Syntax
Change command strings
chg_element sw_ts_less_one_carrier <value> <location> <cell_desc> chg_cell_element sw_ts_less_one_carrier <value> <cell_desc_opt>

6-830

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Values

Display command strings

disp_element sw_ts_less_one_carrier <location> <cell_desc>

Values
Value type Valid range Default value Integer (number of timeslots) 0 to 30 Until set, assumes the value of switch_gprs_pdchs

68P02901W23-S

6-831 Nov 2009

swfm_enable

Chapter 6: CM database parameters

swfm_enable

Description
The swfm_enable parameter enables or disables Software Fault Management (SWFM) alarm messages to be reported to all local MMI terminals that have alarm reporting enabled. This parameter affects the entire BSS. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) No No This parameter applies only to a BSC.

Syntax
Change command string
chg_element swfm_enable <value> 0

Display command string

disp_element swfm_enable 0

Values
Value type Valid range Boolean 0 or 1 0 1 Default value 0 Disabled Enabled

6-832

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

switch_gprs_pdchs

Description
The switch_gprs_pdchs parameter specifies the number of timeslots that the BSS should allocate as switchable (Traffic) TCH and (Packet Data) PDCH in the cell. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes The GPRS feature must be unrestricted. Enough timeslots must be available on all of the GPRS cell carriers. The number of idle circuit switched resources on the GPRS cell specified by gprs_reconfig_thresh_idle_tch parameter (see gprs_reconfig_thresh_idle_tch on page 6-343, must be exceeded. The primary PCU must be specified.

NOTE
BSS software processes using this parameter are notified immediately after the change is made. When an attempt is made to change switch_gprs_pdchs, and the requested PDTCHs exceed the GDS or PMC capacity on the PCU, the BSS accepts the request and issues a warning to indicate that there is not enough GDS or PMC resource available.

Syntax
Change command strings
chg_element switch_gprs_pdchs <value> <location> <cell_desc> chg_cell_element switch_gprs_pdchs <value> <cell_desc_opt>

Display command string

disp_element switch_gprs_pdchs <location> <cell_desc>

68P02901W23-S

6-833 Nov 2009

Values

Chapter 6: CM database parameters

Values
Value type Valid range Default value Integer (number of timeslots) 0 to 30 0

6-834

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

sync_loss_daily

Description
The sync_loss_daily parameter specifies the threshold for the synchronization loss daily alarm level count. An alarm generates if the number of synchronization loss alarms meets or exceeds this threshold during a 24 hour period. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) No No 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 Valid range Default value Integer 0 to 65535 16

68P02901W23-S

6-835 Nov 2009

sync_loss_hourly

Chapter 6: CM database parameters

sync_loss_hourly

Description
The sync_loss_hourly parameter specifies the threshold for the synchronization loss hourly alarm level count. An alarm generates if the number of sync loss alarms meets or exceeds this threshold during a 60 minute period. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No 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 Valid range Default value Integer 0 to 65535 20

6-836

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

sync_loss_oos

Description
The sync_loss_oos parameter specifies the threshold for the synchronization loss, Out Of Service (OOS) daily alarm level count. The 2 Mbit/s circuit is taken out of service if the number of sync loss alarms meets or exceeds this threshold during a 24 hour period. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No None

Syntax
Change command string
chg_element sync_loss_oos <value> <location>

Display command string

disp_element sync_loss_oos <location>

Values
Value type Valid range Default value Integer 0 to 65535 511

68P02901W23-S

6-837 Nov 2009

sync_loss_restore

Chapter 6: CM database parameters

sync_loss_restore

Description
The sync_loss_restore parameter specifies the synchronization loss restorable time period for a sync_loss_oos_alarm. If a synchronization loss alarm does not occur within this period, the 2 Mbit/s circuit is brought back in service. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No None

Syntax
Change command string
chg_element sync_loss_restore <value> <location>

Display command string

disp_element sync_loss_restore <location>

Values
Value type Valid range Integer (1 step = 100 milliseconds) 0 to 65535 0 1 .. . 25 .. . 65535 Default value 600 0 seconds 0.1 second .. . 2.5 seconds .. . 6553.5 seconds 60 seconds 0 milliseconds 100 milliseconds .. . 2500 milliseconds .. . 6553500 milliseconds 60000 milliseconds

6-838

t_avg_w

Chapter 6: CM database parameters

t_avg_w

Description
The t_avg_w parameter specifies the number of multiframes for C averaging in the Packet Wait mode. Type Supported by OMC-R GUI Cell description required Dependencies Operator actions: A (no operator actions) Yes Yes The GPRS feature must be unrestricted. None

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

Syntax
Change command strings
chg_element t_avg_w <value> <location> <cell_desc> chg_cell_element t_avg_w <value> <cell_desc_opt>

Display command string

disp_element t_avg_w <location> <cell_desc>

6-842

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Values

Values
Value type Valid range Default value Integer (multiframes) 0 to 25 10

NOTE
Values greater than 25 are interpreted as 25 by the mobile station (MS).

68P02901W23-S

6-843 Nov 2009

tch_busy_critical_threshold

Chapter 6: CM database parameters

tch_busy_critical_threshold

Description
The tch_busy_critical_threshold parameter specifies the threshold for initiating the flow control procedure barring two of the access classes 0 to 9 from making calls due to TCH congestion. The two classes that are barred are selected randomly. The flow control procedure initiates when the percentage of busy TCHs is equal to or greater than the value entered for this parameter. This parameter is expressed as a percentage. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) No No This parameter must be greater than or equal to tch_busy_norm_threshold.

Syntax
Change command string
chg_element tch_busy_critical_threshold <value> <location>

Display command string

disp_element tch_busy_critical_threshold <location>

Values
Value type Valid range Default value Integer (percent of busy TCHs) 81 to 100 100

6-844

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

tch_busy_norm_threshold

Description
The tch_busy_norm_threshold parameter specifies the threshold for initiating the flow control procedure to bar a single access class 0 through 9 from making a call due to TCH congestion. The class that is barred is selected randomly. The flow control procedure initiates when the percentage of busy TCHs is equal to or greater than the value entered for this parameter. This parameter is expressed as a percentage. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) No No This parameter must be less than or equal to tch_busy_critical_threshold.

Syntax
Change command string
chg_element tch_busy_norm_threshold <value> <location>

Display command string

disp_element tch_busy_norm_threshold <location>

Values
Value type Valid range Default value Integer (percent of busy TCHs) 0 to 100 100

68P02901W23-S

6-845 Nov 2009

tch_congest_prevent_thres

Chapter 6: CM database parameters

tch_congest_prevent_thres

Description
The tch_congest_prevent_thres parameter specifies the level of overall TCH utilization by any MS in a given Cell, at which the Congestion Relief procedure is initiated. This parameter is expressed as a percentage. Type Supported by OMC-R GUI Cell description required Dependencies A (no operation actions) Yes Yes The Congestion Relief feature must be enabled. This parameter must be greater than or equal to mb_tch_congest_thres.

Syntax
Change command string
chg_element tch_congest_prevent_thres <value> <location> <cell_desc>

Display command string

disp_element tch_congest_prevent_thres <location> <cell_desc>

Values
Value type Valid range Default value Integer (percent) 1 to 101 (The value 101 indicates there are no resources left to allocate). 100 (The value 100 indicates an attempt to use the last resource).

6-846

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

tch_flow_control

Description
The tch_flow_control parameter enable or disables the TCH flow control option. The flow control procedure tries to reduce the load on the system when the TCH usage goes above thresholds determined by the tch_busy_norm_threshold and tch_busy_critical_threshold parameters. The reduction in traffic is achieved by barring access classes and manipulating the tx_integer and max_retran parameters.

NOTE
Other parameters can affect flow control. Refer to ccch_load_period, rach_load_period, rach_load_threshold, ssm_critical_overload_threshold, or ssm_normal_overload_threshold.

Type Supported by OMC-R GUI Cell description required Dependencies

A (no operator actions) Yes Yes None

Syntax
Change command strings
chg_element tch_flow_control <value> <location> <cell_desc> chg_cell_element tch_flow_control <value> <cell_desc_opt>

Display command string

disp_element tch_flow_control <location> <cell_desc>

68P02901W23-S

6-847 Nov 2009

Values

Chapter 6: CM database parameters

Values
Value type Valid range Boolean 0 or 1 0 1 Default value 0 Disabled Enabled

6-848

td_enabled

Chapter 6: CM database parameters

td_enabled

{31400}

Description
The td_enabled BSS element specifies whether TD-SCDMA inter-working function is enabled or disabled. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No Modification of td_enabled is allowed only when TD-SCDMA inter-working feature (tdOpt) is unrestricted. Modification of td_enabled from 0 to 1 is allowed only when Inter-RAT handover feature is restricted. If the local_maintenance flag is disabled, the MMI is prevented from switching TD-SCDMA inter-working function on or off.

Syntax
Add/Change command strings
chg_element td_enabled <value> <location>

Display command string

disp_element td_enabled <location>

Values
Value type Valid range Boolean 0 1 Default value 0 TD-SCDMA inter-working is off. TD-SCDMA inter-working is on.

6-852

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

tdm_switch

{25002}

Description
The tdm_switch parameter specifies if the TDM availability enhancements function is enabled. This parameter may be changed inside and outside SYSGEN mode. There is no warning when it is changed inside SYSGEN. Outside sysgen, the warning is only printed when tdm_switch is changed to 0. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes None

Syntax
Add/Change command strings
chg_element tdm_switch <value> <location>

Display command strings

disp_element tdm_switch <location>

Values
Value type Valid range Binary 0 1 Default value 0 Switch is closed Switch is open

68P02901W23-S

6-853 Nov 2009

tdm_ts_blocks

Chapter 6: CM database parameters

tdm_ts_blocks

{26740}

Description
The tdm_ts_blocks parameter identifies the number of TDM 32-timeslot blocks reserved for the PSI. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No None

Syntax
modify_value

Values
Value type Valid range Default value Integer 2 to 10 2

6-854

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

temporary_offset

Description
The temporary_offset parameter specifies a value used by the MS as part of its calculation of C2 for the cell reselection process described in TSGSM 5.08. It is used to apply a negative offset to C2 for the duration of the penalty_time timer parameter. C2 is the reselection priority assigned to a cell which can be broadcast on the BCCH of each cell. When more than one cell is available for reselection, the MS reselects the cell with the highest C2 value. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes The cell_reselect_param_ind parameter must be enabled.

Syntax
Add/Change command strings
add_cell <gsm_cell_id> <location> chg_element temporary_offset <value> <location> <cell_desc> chg_cell_element temporary_offset <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full] disp_element temporary_offset <location> <cell_desc>

68P02901W23-S

6-855 Nov 2009

Values

Chapter 6: CM database parameters

Values
Value type Valid range Default value Integer (1 Step = 10 dB) 0 to 7 0

References
GSM parameter GSM specification C2 TS GSM 4.08 Table 10.32a section 10.5.2.35 TS GSM 5.08

6-856

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

thp_be_weight

Description
The thp_be_weight parameter specifies the Traffic Handling Priority (THP) weight of Best Effort class. THP controls relative throughput of Packet Flow Contexts (PFCs) by assigning a weighting factor for Best Effort class. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes The QoS feature must be unrestricted. The value of thp_be_weight cannot be changed if bssgp_pfc_bit is set to 1. The value of thp_bg_weight and thp_be_weight must be less than or equal to thp_i3_weight.

Syntax
Change command strings
chg_element thp_be_weight <value> <location>

Display command strings

disp_element thp_be_weight <location>

Values
Value type Valid range Default value Integer (weighting factor) 0 to 40 40

68P02901W23-S

6-857 Nov 2009

thp_bg_weight

Chapter 6: CM database parameters

thp_bg_weight

Description
The thp_bg_weight parameter specifies the Traffic Handling Priority (THP) weight of Background class. THP controls relative throughput of Packet Flow Contexts (PFCs) by assigning a weighting factor for Background class. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes The QoS feature must be unrestricted. The value of thp_be_weight cannot be changed if bssgp_pfc_bit is set to 1. The value of thp_bg_weight and thp_be_weight must be less than or equal to thp_i3_weight.

Syntax
Change command strings
chg_element thp_bg_weight <value> <location>

Display command strings

disp_element thp_bg_weight <location>

Values
Value type Valid range Default value Integer (weighting factor) 10 to 40 40

6-858

Technical Description: BSS Command Reference

timing_advance_period

Description
The timing_advance_period parameter specifies the interval between timing advance changes. The interval should be greater than or equal to hreqavex * decision_1_n8. Where: hreqave is the number of measurements from the MS that are used in calculating one average. x equals: 1 (lower threshold of RXLEV), 2 (upper threshold of RXLEV), 3 (lower threshold of RXQUAL), or 4 (upper threshold of RXQUAL). decision_1_n8 is the number of samples in the threshold comparison process. A (no operator actions) Yes Yes hreqave, decision_1_n8.

Type Supported by OMC-R GUI Cell description required Dependencies

Syntax
Add/Change command strings
add_cell <gsm_cell_id> <location> chg_element timing_advance_period <value> <location> <cell_desc> chg_cell_element timing_advance_period <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full] disp_element timing_advance_period <location> <cell_desc>

68P02901W23-S

6-863 Nov 2009

Values

Chapter 6: CM database parameters

Values
Value type Valid range Integer 0 to 31 0 1 2 ... ... ... 31 Default value 4 Mapped to SACCH multiframes: 0 SACCH multiframes 2 SACCH multiframes 4 SACCH multiframes ... ... ... 62 SACCH multiframes 8 SACCH multiframes

6-864

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

tlli_blk_coding

Description
The tlli_blk_coding parameter is used to request the mobile station to use the coding scheme commanded for the Temporary Block Flow (TBF) even for RLC blocks containing the contention resolution Temporary Logical Link Identifier (TLLI). Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes The GPRS feature must be unrestricted.

Syntax
Change command strings
chg_element tlli_blk_coding <value> <location> <cell_desc> chg_cell_element tlli_blk_coding <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full] disp_element <location> <cell_desc>

Values
Value type Valid range Boolean 0 1 Default value 0 Always use CS1 for GPRS TBFs for TLLI blocks, and MCS1 for EGPRS TBFs for TLLI blocks. Use the commanded coding scheme for all blocks. 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.

68P02901W23-S

6-865 Nov 2009

trace_msgs_after_ho

Chapter 6: CM database parameters

trace_msgs_after_ho

Description
The trace_msgs_after_ho parameter specifies the number of messages that the system collects immediately after a handover occurs. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No This parameter is used only when handover records are requested and RSS, Abis and/or MS Power control data are specified. This parameter applies only to the BSC.

Syntax
Change command strings
chg_element trace_msgs_after_ho <value> 0

Display command string

disp_element trace_msgs_after_ho 0

Values
Value type Valid range Default value Integer (number of messages to be collected after a handover) 0 to 8 5

6-866

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

trace_msgs_before_ho

Description
The trace_msgs_before_ho parameter specifies the number of messages that the system collects immediately before a handover occurs. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No This parameter is used only when handover records are requested and RSS, Abis and/or MS Power control data are specified. This parameter applies only to the BSC.

Syntax
Change command strings
chg_element trace_msgs_before_ho <value> 0

Display command string

disp_element trace_msgs_before_ho 0

Values
Value type Valid range Default value Integer (number of messages to be collected before a handover) 0 to 8 5

68P02901W23-S

6-867 Nov 2009

trunk_critical_threshold

Chapter 6: CM database parameters

trunk_critical_threshold

Description
The trunk_critical_threshold parameter specifies the severity assignment of certain alarms. The value of this parameter is a percentage of total trunk capacity. A critical alarm is assigned when the percentage of trunk capacity loss exceeds the trunk_critical_threshold parameter value. A major alarm is assigned when the percentage of trunk capacity loss is greater than or equal to the trunk_major_threshold parameter value but is less than the trunk_critical_threshold parameter value. A trunk_critical_threshold value of 0 insures that Critical is always the severity assignment if there is any capacity loss. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No This parameter must be greater than the value assigned to the trunk_major_threshold parameter unless both values are set to 0. This parameter applies only to the BSC.

Syntax
Change command string
chg_element trunk_critical_threshold <value> 0

Display command string

disp_element trunk_critical_threshold 0

Values
Value type Valid range Default value Integer (percent of trunk capacity) 0 to 100 50

6-868

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

trunk_major_threshold

Description
The trunk_major_threshold parameter specifies the severity assignment of certain alarms. The value of this parameter is a percentage of total trunk capacity. A major alarm is assigned when the percentage of trunk capacity loss exceeds the trunk_major_threshold parameter value but is less than the trunk_critical_threshold parameter value. A minor alarm is assigned when the percentage of trunk capacity loss is less than the trunk_major_threshold parameter value. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No This parameter must be less than the value assigned to the trunk_critical_threshold parameter unless both values are set to 0. This parameter applies only to the BSC.

Syntax
Change command string
chg_element trunk_major_threshold <value> 0

Display command string

disp_element trunk_major_threshold 0

Values
Value type Valid range Default value Integer (percent of trunk capacity) 0 to 99 10

68P02901W23-S

6-869 Nov 2009

ts_alloc_flag

Chapter 6: CM database parameters

ts_alloc_flag

Description
The ts_alloc_flag parameter alters the E1 timeslot allocation on links that are adjacent to a ts_switch (pseudo site). This parameter is only used when RSL or RTF devices are equipped. Changing this parameter does not alter the timeslot mapping of RSLs and RTFs that are already equipped; it affects the way timeslots are allocated for later equipped devices. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No This parameter cannot be altered unless the Aggregate Abis feature is enabled. This parameter applies only to the BSC.

Syntax
Change command string
chg_element ts_alloc_flag <value> 0 Whenever the ts_alloc_flag is modified the system displays this message: COMMAND ACCEPTED: WARNING: This element only has effect on links to a TS_SWITCH

Display command string

disp_element ts_alloc_flag 0

6-870

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Values

Values
Value type Valid range Boolean 0 or 1 0 1 Default value 0 Use existing algorithm Use new algorithm

68P02901W23-S

6-871 Nov 2009

ts_in_usf_active

Chapter 6: 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. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes The EOP feature must be unrestricted. The number of non-BCCH timeslots that broadcasts continuously at full power even when no mobile is active on that timeslot.

Syntax
Change command strings
chg_element ts_in_usf_active <value> <location> <cell_desc> chg_cell_element ts_in_usf_active <value> <cell_desc_opt>

Display command strings

disp_element ts_in_usf_active <location> <cell_desc>

Values
Value type Valid range Default value Integer (number of non-BCCH timeslots) 0 to 3 1

6-872

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

tsc_update_method

Description
The tsc_update_method parameter specifies the method for updating timeslots when the BSIC is changed. The available methods are: Update the BCCH/CCCH timeslots. Update all timeslots on the BCCH carrier. Update all timeslots on all carriers of cell. A (no operator actions) Yes No No RTS are equipped (tsc_update_method must first be set before RTFs can be equipped in the script). Equip RTF verifies the TSC values based on this setting. This parameter applies only to the BSC.

Type Supported by OMC-R GUI Cell description required Dependencies

Syntax
Change command string
chg_element tsc_update_method <value> 0

Display command string

disp_element tsc_update_method 0

68P02901W23-S

6-873 Nov 2009

Values

Chapter 6: CM database parameters

Values
Value type Valid range Integer 0 to 2 0 1 2 Default value 0 Update the BCCH/CCCH timeslots Update all timeslots on the BCCH carrier Update all timeslots on all carriers of cell

6-874

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

tx_integer

Description
The tx_integer parameter specifies the number of Random Access Channel (RACH) slots between the access retry transmission on the RACH. Timer T3126 is used when an MS sends a Channel Request message. From 3 to 50 RACH slots are used to spread the transmission. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes None

Syntax
Add/Change command strings
add_cell <gsm_cell_id> <location> chg_element tx_integer <value> <location> <cell_desc> chg_cell_element tx_integer <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full] disp_element tx_integer <location> <cell_desc>

68P02901W23-S

6-875 Nov 2009

Values

Chapter 6: CM database parameters

Values
Value type Valid range Integer 0 to 15 Represents RACH slots as shown below: 0 1 2 3 4 5 6 7 Default value 4 3 RACH 4 RACH 5 RACH 6 RACH 7 RACH 8 RACH 9 RACH 10 RACH 8 9 10 11 12 13 14 15 11 RACH 12 RACH 14 RACH 16 RACH 20 RACH 25 RACH 32 RACH 50 RACH

References
GSM parameter GSM specification TX_INTEGER 4.08 - 3.3.1.1: request for resources by the MS 4.08 - 10.5.2.17 - fig. 10.36, and table 10.30 12.20 - 5.2.8.7 cell description - number of slots spread trans

6-876

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

tx_power_cap

Description
The tx_power_cap parameter specifies all cells within a site to be either low transmitting power capable or high transmitting power capable. This parameter is valid only at DCS1800 and PCS1900 sites, it is not valid for micro sites (although it is valid at Horizon II micro sites). This parameter can be set when the primary outer zone frequency type of the cell is PGSM, EGSM, DCS1800, and PCS1900 if the cell is a Dual Band Cell. If the cell is not, the frequency must be DCS1800, or PCS1900 to change tx_power_cap. For a PCS 1900 cell residing on a Horizonmacro or Horizonmacro extension cabinet, there can be no DRIs equipped for that cell. If a DRI has already been equipped, any change of that element is disallowed. All DCS1800 DRI devices in Horizonmacro, Horizon II macro, Horizon II mini and Horizon II micro master or extension cabinets are forced to operate in high power-capable mode (32 watts). Type Supported by OMC-R GUI Cell description required Dependencies B (operator actions required) Yes Yes This parameter is valid only if the transceivers at the site are inactive. The system does not accept this parameter if the associated DRIs are unlocked. Lock the associated DRIs before attempting to change this parameter.

Operator actions

Syntax
Change command strings
chg_element tx_power_cap <value> <location> <cell_desc> chg_cell_element tx_power_cap <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full] disp_element tx_power_cap <location> <cell_desc>

68P02901W23-S

6-877 Nov 2009

Values

Chapter 6: CM database parameters

Values
Value type Valid range Boolean 0 or 1 0 1 Default value 0 Low power High power

6-878

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

u_rxlev_dl_ih

Description
The u_rxlev_dl_ih parameter specifies the intra-cell control thresholds for the Receive (Rx) level downlink. This parameter is evaluated in conjunction with the l_rxqual_dl_h to determine whether an inter-cell or intra-cell is being requested. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes This parameter is used by the BSS only when interfer_ho_allowed = 1.

Syntax
Add/Change command strings
add_cell <gsm_cell_id> <location> chg_element u_rxlev_dl_ih <value> <location> <cell_desc> chg_cell_element u_rxlev_dl_ih <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full] disp_element u_rxlev_dl_ih <location> <cell_desc>

Values
Value type Valid range Integer (1 step = 1 dBm) 0 to 63 0 1 2 ... ... Represents -110 dBm to -47 dBm, as shown below: -110 dBm -109 dBm -108 dBm ... ... Continued

68P02901W23-S

6-879 Nov 2009

References

Chapter 6: CM database parameters

... 63 Default value 45

... -47 dBm -65 dBm

References
GSM parameter GSM specification RXLEV_DL_IH 5.08 - Appendix A - Table 1

6-880

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

u_rxlev_dl_p

Description
The u_rxlev_dl_p parameter specifies the signal strength for the upper downlink limit of the serving cell. BTS transmit power may be reduced if the MS signal strength is greater than this value. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes None

Syntax
Add/Change command strings
add_cell <gsm_cell_id> <location> chg_element u_rxlev_dl_p <value> <location> <cell_desc> chg_cell_element u_rxlev_dl_p <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full] disp_element u_rxlev_dl_p <location> <cell_desc>

Values
Value type Valid range Integer (1 step = 1 dBm) 0 to 63 0 1 2 ... ... Represents -110 dBm to -47 dBm, as shown below: -110 dBm or lower -109 dBm -108 dBm ... ... Continued

68P02901W23-S

6-881 Nov 2009

References

Chapter 6: CM database parameters

... 63 Default value 40

... -47 dBm or higher -70 dBm

References
GSM parameter GSM specification U_RXLEV_DL_P 5.08 - Appendix A - Table 1

6-882

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

u_rxlev_ul_ih

Description
The u_rxlev_ul_ih parameter specifies the intra-cell control thresholds for the upper Receive (Rx) level uplink. This parameter is evaluated in conjunction with the l_rxqual_ul_h to determine whether an inter-cell or intra-cell is being requested. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes This parameter is used by the BSS only when interfer_ho_allowed is 1.

Syntax
Add/Change command strings
add_cell <gsm_cell_id> <location> chg_element u_rxlev_ul_ih <value> <location> <cell_desc> chg_cell_element u_rxlev_ul_ih <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full] disp_element u_rxlev_ul_ih <location> <cell_desc>

Values
Value type Valid range Integer (1 step = 1 dBm) 0 to 63 0 1 2 ... ... Represents -110 dBm to -47 dBm, as shown below: -110 dBm or lower -109 dBm -108 dBm ... ... Continued

68P02901W23-S

6-883 Nov 2009

References

Chapter 6: CM database parameters

... 63 Default value 45

... -47 dBm or higher -65 dBm

References
GSM parameter GSM specification RXLEV_UL_IH 5.08 - Appendix A - Table 1

6-884

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

u_rxlev_ul_p

Description
This parameter specifies the signal strength for the upper uplink limit of the serving cell. Mobile transmit power may be reduced if the MS transmit signal strength is greater than this value. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes None

Syntax
Add/Change command strings
add_cell <gsm_cell_id> <location> chg_element u_rxlev_ul_p <value> <location> <cell_desc> chg_cell_element u_rxlev_ul_p <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full] disp_element u_rxlev_ul_p <location> <cell_desc>

Values
Value type Valid range Integer (1 step = 1 dBm) 0 to 63 0 1 2 ... ... Represents -110 dBm to -47 dBm, as shown below: -110 dBm or lower -109 dBm -108 dBm ... ... Continued

68P02901W23-S

6-885 Nov 2009

References

Chapter 6: CM database parameters

... 63 Default value 40

... -47 dBm or higher -70 dBm

References
GSM parameter GSM specification U_RXLEV_UL_P 5.08 - Appendix A - Table 1

6-886

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

u_rxqual_dl_p

Description
The u_rxqual_dl_p parameter specifies the power control threshold for the best allowed downlink receive quality (rxqual). The valid range and default values for this parameter are dependent on the type of unit that is selected. Receive quality processing is measured using Bit Error Rate (BER) values or Quality Band (QBand) units. The alt_qual_proc parameter specifies the type of unit. An Rxqual value better (lower BER rate) than what is specified by the u_rxqual_ul_p parameter may result the reduction of downlink power. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes alt_qual_proc Since better rxqual corresponds to a lower bit error rate, u_rxqual_dl_p should be less than l_rxqual_dl_p. u_rxqual_dl_p must be less than l_rxqual_dl_p_amr_fr.

Syntax
Add/Change command strings
add_cell <gsm_cell_id> <location> chg_element u_rxqual_dl_p <value> <location> <cell_desc> chg_cell_element u_rxqual_dl_p <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full] disp_element u_rxqual_dl_p <location> <cell_desc>

68P02901W23-S

6-887 Nov 2009

Values

Chapter 6: CM database parameters

Values
Value type Valid range Integer 0 to 1810 BER (1 step = 0.01% bit error rate) 0 to 7 QBand units Default value 28 BER 1 QBand units If alt_qual_proc = 0

If alt_qual_proc = 1 If alt_qual_proc = 0 If alt_qual_proc = 1

NOTE
Dependencies affect the actual range, thus range is never set to 1810 BER (or 7 QBand).

References
GSM parameter GSM specification U_RXQUAL_DL_P 5.08 - Appendix A - Table 1

6-888

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

u_rxqual_dl_p_hr

Description
The u_rxqual_dl_p_hr parameter specifies the power control threshold for the best allowed downlink received quality (rxqual). Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes The AMR feature and/or the GSM Half Rate feature must be unrestricted. This parameter can be changed [22064] at any AMR/GSM HR capable BTS site. This parameter is prompted when alt_qual_proc is changed. This parameter must be greater than u_rxqual_dl_p_hr.

Syntax
Add/Change command strings
chg_element u_rxqual_dl_p_hr <value> <location> <cell_desc> chg_cell_element u_rxqual_dl_p_hr <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> full disp_element u_rxqual_dl_p_hr <location> <cell_desc>

68P02901W23-S

6-889 Nov 2009

Values

Chapter 6: CM database parameters

Values
Value type Valid range Integer 0 to 1810 0 to 7 Default value 14 0 BER (1 step = 0.01% bit error rate). If alt_qual_proc = 0 QBand units. If alt_qual_proc = 1 BER. If alt_qual_proc = 0 QBand units. If alt_qual_proc = 1

NOTE
Dependencies affect the actual range, thus range is never set to 1810 BER (or 7 QBand).

6-890

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

u_rxqual_ul_p

Description
The u_rxqual_ul_p parameter sets the power control threshold for the best allowed uplink receive quality (rxqual). The valid range and default values for this parameter are dependent on the type of unit that is selected. Receive quality processing is measured using Bit Error Rate (BER) values or Quality Band (QBand) units. The alt_qual_proc parameter specifies the type of unit. An Rxqual value better (lower BER rate) than what is specified by the u_rxqual_ul_p parameter may result the reduction of MS power. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes alt_qual_proc Since better rxqual corresponds to a lower bit error rate, u_rxqual_ul_p must be less than l_rxqual_ul_p. u_rxqual_ul_p must be less than l_rxqual_ul_p_amr_fr.

Syntax
Add/Change command strings
add_cell <gsm_cell_id> <location> chg_element u_rxqual_ul_p <value> <location> <cell_desc> chg_cell_element u_rxqual_ul_p <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full] disp_element u_rxqual_ul_p <location> <cell_desc>

68P02901W23-S

6-891 Nov 2009

Values

Chapter 6: CM database parameters

Values
Value type Valid range Integer 0 to 1810 BER (1 step = 0.01% bit error rate) 0 to 7 QBand units Default value 28 BER 1 QBand units If alt_qual_proc = 0

If alt_qual_proc = 1 If alt_qual_proc = 0 If alt_qual_proc = 1

NOTE
Dependencies affect the actual range, thus range is never set to 1810 BER (or 7 QBand).

References
GSM parameter GSM specification U_RXQUAL_UL_P 5.08 - Appendix A - Table 1

6-892

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

u_rxqual_ul_p_hr

Description
The u_rxqual_ul_p_hr parameter specifies the power control threshold for the best allowed uplink received quality (rxqual). Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes The AMR feature and/or the GSM Half Rate feature must be unrestricted. This parameter can be changed [22064] at any AMR/GSM HR capable BTS site. This parameter is prompted when alt_qual_proc is changed. This parameter must be less than u_rxqual_ul_p_hr.

Syntax
Add/Change command strings
chg_element u_rxqual_ul_p_hr <value> <location> <cell_desc> chg_cell_element u_rxqual_ul_p_hr <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> full disp_element u_rxqual_ul_p_hr <location> <cell_desc>

68P02901W23-S

6-893 Nov 2009

Values

Chapter 6: CM database parameters

NOTE
Dependencies affect the actual range, thus range is never set to 1810 BER (or 7 QBand).

6-894

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

ul_audio_lev_offset

Description
The ul_audio_lev_offset parameter specifies the uplink volume control offset on a per BSS basis. The offset is in 1 dB steps with a maximum increase or decrease of 30 dB (between -15 dB and 15 dB). Changes take effect immediately (including active calls). The audio level parameters affect background and comfort noise. The audio level parameters do not affect data. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No The volume_control_type parameter controls the ul_audio_lev_offset application. If volume_control_type = 1, then the ul_audio_lev_offset parameter only applies to sites equipped with GDP boards. The GDP firmware controls the volume level by converting the audio level bits for the entered offset. This parameter applies only to the BSC.

Syntax
Change command string
chg_element ul_audio_lev_offset <value> 0

Display command strings

disp_element ul_audio_lev_offset 0

Values
Value type Valid range Default value Integer (1 Step = 1 dB) -15 to +15 0

68P02901W23-S

6-895 Nov 2009

ul_rxlev_ho_allowed

Chapter 6: CM database parameters

ul_rxlev_ho_allowed

Description
The ul_rxlev_ho_allowed parameter enables or disables handovers due to the uplink receive level (rxlev). Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes None

Syntax
Add/Change command strings
add_cell <gsm_cell_id> <location> chg_element ul_rxlev_ho_allowed <value> <location> <cell_desc> chg_cell_element ul_rxlev_ho_allowed <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full] disp_element ul_rxlev_ho_allowed <location> <cell_desc>

Values
Value type Valid range Boolean 0 or 1 0 1 Default value 1 Disabled Enabled

6-896

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

References

References
Internal name EN_RXLEV_HO This is a Motorola parameter.

68P02901W23-S

6-897 Nov 2009

ul_rxqual_ho_allowed

Chapter 6: 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 Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes None

Syntax
Add/Change command strings
add_cell <gsm_cell_id> <location> chg_element ul_rxqual_ho_allowed <value> <location> <cell_desc> chg_cell_element ul_rxqual_ho_allowed <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full] disp_element ul_rxqual_ho_allowed <location> <cell_desc>

Values
Value type Valid range Boolean 0 or 1 0 1 Default value 1 Disabled Enabled

6-898

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

References

References
Internal name EN_RXQUAL_HO This is a Motorola parameter.

68P02901W23-S

6-899 Nov 2009

umts_band_preferred

Chapter 6: CM database parameters

umts_band_preferred

Description
The umts_band_preferred parameter indicates whether hand over to UTRAN band is preferred or not. When set to 1, UTRAN band is preferred over any GSM band for the handover. When set to 0, GSM band is preferred over any UTRAN band for the handover. Type Supported by OMC-R GUI Cell description required Dependencies A (No operator actions) Yes Yes The Enhanced 2G/3G Handover feature must be unrestricted to modify this parameter.

Syntax
Add/Change command strings
chg_element umts_band_preferred <value> <location> <cell_desc> chg_cell_element umts_band_preferred <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full] disp_element umts_band_preferred <location> <cell_desc>

Values
Value type Valid range Boolean 0 to 1 0 1 Default value 0 GSM band preferred UMTS band preferred

6-900

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

umts_cpich_ec_no_min

Description
The umts_cpich_ec_no_min parameter is a threshold parameter used by the handover algorithm when the fdd_rep_quant parameter is set to Ratio of Chip Energy to Power Spectral Density (Ec/No). Type Supported by OMC-R GUI Cell description required Dependencies A (No operator actions) Yes Yes The Enhanced 2G/3G Handover feature must be unrestricted to modify this parameter. The fdd_rep_quant parameter must be set to 1 (Ec/No).

Syntax
Add/Change command strings
chg_element umts_cpich_ec_no_min <value> <location> <cell_desc> chg_cell_element umts_cpich_ec_no_min <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full] disp_element umts_cpich_ec_no_min <location> <cell_desc>

Values
Value type Valid range Default value Integer (dBm) -20 to 0 -15

68P02901W23-S

6-901 Nov 2009

umts_cpich_rscp_min

Chapter 6: CM database parameters

umts_cpich_rscp_min

Description
The umts_cpich_rscp_min parameter is a threshold parameter that is used by the handover algorithm when the fdd_rep_quant parameter is set to Received Signal Code Power (RSCP). Type Supported by OMC-R GUI Cell description required Dependencies A (No operator actions) Yes Yes The Enhanced 2G/3G Handover feature must be unrestricted to modify this parameter. The fdd_rep_quant parameter must be set to 0 (RSCP).

Syntax
Add/Change command strings
chg_element umts_cpich_rscp_min <value> <location> <cell_desc> chg_cell_element umts_cpich_rscp_min <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full] disp_element umts_cpich_rscp_min <location> <cell_desc>

Values
Value type Valid range Default value Integer (dBm) -115 to -53 -90

6-902

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

unequipped_circuit_allowed

Description
The unequipped_circuit_allowed parameter specifies the system response when a terrestrial circuit becomes unequipped. The options are: Sending an alarm to the OMC-R. Sending an unequipped circuit message to the MSC. Sending both an alarm to the OMC-R and an unequipped circuit message to the MSC. A (no operator actions) No No This parameter does not apply to RXCDR sites. The Phase 2 feature must be unrestricted.

Type Supported by OMC-R GUI Cell description required Dependencies

Syntax
Change command string
chg_element unequipped_circuit_allowed <value> 0

Display command string

disp_element unequipped_circuit_allowed 0

Values
Value type Valid range Integer 0 to 2 0 1 2 Default value 0 Send alarm to the OMC-R Send unequipped circuit message to the MSC Send alarm to the OMC-R and send unequipped circuit message to the MSC

68P02901W23-S

6-903 Nov 2009

References

Chapter 6: CM database parameters

References
GSM specification TS GSM 8.08 This is a Motorola defined parameter.

6-904

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

use_bcch_for_gprs

Description
The use_bcch_for_gprs parameter specifies whether reserved and switchable GPRS timeslots are allocated on a BCCH carrier. The system prompts for this parameter when the gprs_enabled per-cell parameter is changed to 1. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes The GPRS feature must be unrestricted.

Syntax
Change command string
chg_cell_element use_bcch_for_gprs <value> <cell_desc_opt>

Display command string

disp_element use_bcch_for_gprs <cell_desc>

Values
Value type Valid range Boolean 0 to 1 0 1 Default value 1 Use BCCH Carrier for PDs as the last priority. Use BCCH Carrier for PDs as the first priority.

68P02901W23-S

6-905 Nov 2009

use_derived_ho_power

Chapter 6: CM database parameters

use_derived_ho_power

Description
The use_derived_ho_power parameter specifies how the system manages the derived handover power level for internal inter-cell handovers. When kbit/s, these handovers use the power level in the database. When enabled, these handovers use a power level derived from the rxlev reported by the MS for the target cell. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes None

Syntax
Change command strings
chg_element use_derived_ho_power <value> <location> <cell_desc> chg_cell_element use_derived_ho_power <value> <cell_desc_opt>

Display command string

disp_element use_derived_ho_power <location> <cell_desc>

Values
Value type Valid range Boolean 0 or 1 0 1 Default value 0 Disabled Enabled

6-906

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

use_neighbor_pbgt_hreqave

Description
The use_neighbor_pbgt_hreqave parameter indicates whether the per cell or per neighbor hreqave is used for the pbgt>ho_margin trigger assignment. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes None

Syntax
Change command strings
chg_element use_neighbor_pbgt_hreqave <value> <location> <cell_desc> chg_cell_element use_neighbor_pbgt_hreqave <value> <cell_desc_opt>

Display command string

disp_element use_neighbor_pbgt_hreqave <location> <cell_desc>

Values
Value type Valid range Boolean 0 or 1 0 1 Default value 0 Per cell hreqave is used Per neighbor hreqave is used

68P02901W23-S

6-907 Nov 2009

volume_control_type

Chapter 6: CM database parameters

volume_control_type

Description
The volume_control_type parameter enables or disables uplink and downlink Volume Control. The volume can be changed at either an RXCDR or at a BSC. The effect depends on the equipment configuration (GDPs or DRIs equipped), and the value of volume_control_type to use DRIs (0) or GDP volume control (1). Type Supported by OMC-R GUI Cell description required Dependencies B (operator actions required) Yes No The Generic DSP Processor (GDP) Volume Control feature must be available. If volume_control_type is set to 1, the BSS must be equipped with GDP boards, unless remote transcoding, when RXCDR must contain a GDP board to serve the BSS. CCDSP (Channel Coding Digital Signal Processor) volume control cannot be directly initiated from an RXCDR. (There are no DRIs at the RXCDR). However, by setting the parameter to 0 at the BSC and at the RXCDR, CCDSP (DRI) volume control is used in this BSS. The parameters ul_audio_lev_offset and dl_audio_lev_offset must be set to 0 before changing volume_control_type. This parameter applies only to the BSC. It is the responsibility of the network operator to synchronize the values of volume_control_type between the RXCDR and the BSC for the desired control.

Operator actions

NOTE
For the BSC side, turn the parameter on with a chg_ele command. chg_ele volume_control_type <value> = 0 where <value> is used to select CCDSP volume control = 0 or GDP Volume control = 1. To change these values at the RXCDR, use the modify_values command on the ABSS device.

6-908

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Syntax

Syntax
Change command string
chg_element volume_control_type <value> 0

Display command string

disp_element volume_control_type 0

NOTE
The bss_id parameter is required in both the commands only at the RXCDR.

Values
Value type Valid range Boolean 0 or 1 0 1 Default value 0 CCDSP Volume Control GDP Volume Control

68P02901W23-S

6-909 Nov 2009

wait_for_reselection

Chapter 6: 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 Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) No No 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 Valid range Default value Integer (seconds) 0 to 86400 10

6-910

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

wait_indication_parameters

Description
The wait_indication_parameters parameter specifies the MS timer (T3122). For an MS origination with no channel available, the MS is sent an IMMEDIATE ASSIGNMENT REJECT message in an unacknowledged mode on the CCCH. The message contains the request reference and a wait indication. The MS does not make a new request in the same cell until the timer expires. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes None

Syntax
Add/Change command strings
add_cell <gsm_cell_id> <location> chg_element wait_indication_parameters <value> <location> <cell_desc> chg_cell_element wait_indication_parameters <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full] disp_element wait_indication_parameters <location> <cell_desc>

Values
Value type Valid range Default value Integer (seconds) 0 to 255 5

68P02901W23-S

6-911 Nov 2009

References

Chapter 6: CM database parameters

References
GSM specification 4.08 - 3.3.1.2.2: assignment rejection 4.08, - 10.5.2.24, figure 10.43, and table 10.37 4.08 - 11.1.1: 12.20 - 5.2.7.7 - Wait Indication This is a Motorola defined parameter.

6-912

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

worse_neighbor_ho

Description
The worse_neighbor_ho parameter specifies whether a call can be handed over to a neighbor cell due to the downlink receive level even when the neighbor cell receive level is lower than the serving cell receive level. This parameter affects only handovers due to downlink receive level. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes None

Syntax
Change command strings
chg_element worse_neighbor_ho <value> <location> <cell_desc> chg_cell_element worse_neighbor_ho <value> <cell_desc_opt>

Display command string

disp_element worse_neighbor_ho <location> <cell_desc>

Values
Value type Valid range Boolean 0 or 1 0 1 Default value 0 Handover disabled Handover enabled

68P02901W23-S

6-913 Nov 2009

zone_ho_hyst

Chapter 6: CM database parameters

zone_ho_hyst

Description
The zone_ho_hyst parameter specifies the margin for the inner zone handover hysteresis. The system uses this value to determine whether an outer-zone to inner-zone handover should take place. A handover initiates when both the uplink and the downlink receive level averages are greater than the sum of the respective uplink or downlink threshold defined for the inner zone plus the per cell hysteresis for inter-zone handover plus the difference between the current uplink/downlink transmit power and the maximum uplink/downlink transmit power of the inner zone carrier: RXLEV_DL > RXLEV_DL_ZONE + ZONE_HO_HYST + (BS_TXPWR - BS_TXPWR_MAX_INNER) or (RXLEV_UL > RXLEV_UL_ZONE + ZONE_HO_HYST + (MS_TXPWR - MS_TXPWR_MAX_INNER)). Type Supported by OMC-R GUI Cell description required Dependencies A (No operator actions required) Yes Yes The Concentric Cells feature must be unrestricted. The range depends on the value of inner_zone_alg: Dual Band Cell: -63 to 63. Not Dual Band: 0 to 30.

Syntax
Change command strings
chg_element zone_ho_hyst <value> <location> <cell_desc> chg_cell_element zone_ho_hyst <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full] disp_element zone_ho_hyst <location> <cell_desc>

6-914

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Values

Values
Value type Valid range Default value Integer 0 to 30 (Not Dual Band Cell) -63 to 63 (Dual Band Cell) 0

68P02901W23-S

6-915 Nov 2009

zone_pingpong_count

Chapter 6: 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 (see zone_pingpong_enable_win on page 7-212). This parameter can be changed when the operator is in RAM or Sysgen mode. This parameter can only be modified at the BSC. Type Supported by OMC-R GUI Cell description required Dependencies A (No operator actions required) Yes No None

Syntax
Change command strings
chg_element zone_pingpong_count <value> 0

Display command strings

disp_element zone_pingpong_count 0

Values
Value type Valid range Default value Integer (insteps of 1) 0 to 255 3

6-916

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

zone_pingpong_preferred_zone

Description
The zone_pingpong_preferred_zone parameter indicates which zone is preferred as a hop target zone. This parameter can be changed when the operator is in RAM or Sysgen mode. This parameter can only be modified at the BSC. Type Supported by OMC-R GUI Cell description required Dependencies A (No operator actions required) Yes No 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 Valid range Integer 0, 1 or 255 0 1 255 Default value 255 Outer zone preferred Inner zone preferred Current zone (no preferred zone)

68P02901W23-S Nov 2009

6-917

Values

Chapter 6: CM database parameters

6-918

68P02901W23-S Nov 2009

Chapter

7
Timer parameters

Timer parameters are BSS parameters that can be displayed and changed using MMI commands. The timers are used to monitor and set timer guards for the various software processes in the BSS. This chapter contains descriptions of the timer parameters used in the BSS, and indicates the command syntax used to modify or display the parameter. The timer descriptions are in alphabetical order as listed in the Contents section of this manual. Each timer parameter is described separately using the following presentation layout: Parameter reference - showing the timer parameter reference title. Description - providing a description of the timer operation, and including information on the parameter type, whether supported by OMC-R GUI, whether cell numbers are required, and listing any dependencies affecting the timer. Syntax - giving the change command and display command strings using the particular timer parameter. Values - giving the value type, valid range, and the default value for the particular timer parameter. References - giving any related information such as internal name, GSM name, and ITU/GSM specification. For more information about BSS timers, refer to the Maintenance Information: BSS Timers (68P02901W58) manual.

68P02901W23-S Nov 2009

7-1

add_access_class

Chapter 7: Timer parameters

add_access_class

Description
The add_access_class timer specifies the guard time period between individual mobile access classes to come into service. This permits MSs to access the system gradually. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) No No None

Syntax
Change command string
chg_element add_access_class <value> <location>

Display command string

disp_element add_access_class <location>

Values
Value type Valid range Default value Integer (milliseconds) 0 to 1000000 60000

References
Internal name MTCRM_ADD_ACC_CLASS This is a Motorola defined timer.

7-2

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

assign_successful

Description
The assign_successful timer causes a Clear Request message to be sent to the MSC when it expires. This timer starts when the BSC sends an assignment command to the BTS. The bssmap_t1 timer controls how long a call remains queued when waiting for a resource. In all cases, the bssmap_t1 timer must be less than the assign_successful timer. The reason for this is that the assignment procedure fails when the assign_successful timer expires. If this timer expires, the call terminates. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No None

Syntax
Change command string
chg_element assign_successful <value> <location>

Display command string

disp_element assign_successful <location>

Values
Value type Valid range Default value Integer (milliseconds) 0 to 1000000 30000

68P02901W23-S

7-3 Nov 2009

References

Chapter 7: Timer parameters

References
Internal name SSM_MTN This is a Motorola defined timer.

7-4

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

auto_dl_dur

Description
The auto_dl_dur auto downlink duration BSS parameter sets the number of block periods for which the network delays the release of a live downlink TBF. This TBF is created through the auto downlink mechanism which is waiting for new downlink data to arrive. One block period equals 20 ms. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No The GPRS feature must be unrestricted.

Syntax
Change command string
chg_element auto_dl_dur <value> <location>

Display command string

disp_element auto_dl_dur <location>

Values
Value type Valid range Default value Integer (20 ms block periods) 15 to 250 50

68P02901W23-S

7-5 Nov 2009

bcch_info

Chapter 7: Timer parameters

bcch_info

Description
The bcch_info timer specifies the wait time for the Radio Subsystem (RSS) to hold an information message for the BCCH System Information Messages from Call Processing (CP) before sending the information message to the channel coders. The information message is sent immediately if all necessary BCCH system information messages are received depending on the mode being used. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) No No None

Syntax
Change command string
chg_element bcch_info <value> <location>

Display command string

disp_element bcch_info <location>

Values
Value type Valid range Default value Integer (milliseconds) 0 to 10000 2000

References
Internal name GSM specification TM_BCCH_INFO TS GSM 04.08 - section 9.1.34. This is a Motorola defined timer.

7-6

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

bep_period

Description
The bep_period parameter is used in an EGPRS cell to indicate the BEP (Bit Error Probability) filter averaging period used for filtering channel quality measurements by the mobile.

NOTE
A BSS software process is notified whenever the bep_period element value is changed.

Type Supported by OMC-R GUI Cell description required Dependencies

A (no operator actions) Yes Yes The EGPRS feature must be unrestricted.

Syntax
Change command strings
chg_element bep_period <value> <location> <cell_desc> chg_cell_element bep_period <value> <cel_desc_opt>

Display command strings

disp_cell <cell_id> [full] disp_element bep_period <location> <cell_desc>

Values
Value type Valid range Default value Integer (BEP filter averaging period) 0 to 10 0 Eliminates forgetting factor 'e' from channel quality measurement algorithms executed by the MS.

68P02901W23-S

7-7 Nov 2009

bep_period2

Chapter 7: Timer parameters

bep_period2

Description
The bep_period2 parameter is optionally used in an EGPRS cell to further indicate the BEP (Bit Error Probability) filter averaging period used for filtering channel quality measurements by the mobile. The bep_period2 parameter is a forgetting factor for the mobile station to use when filtering the Bit Error Probability. If this parameter is sent, the mobile station in the cell uses it, until the mobile station in the same cell receives a new bep_period2, or the mobile station leaves the cell or the MS enters packet idle mode. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes The EGPRS feature must be unrestricted.

Syntax
Change command strings
chg_element bep_period2 <value> <location> <cell_desc> chg_cell_element bep_period2 <value> <cel_desc_opt>

Display command strings

disp_cell <cell_id> [full] disp_element bep_period2 <location> <cell_desc>

Values
Value type Valid range Default value Integer (Secondary BEP filter averaging period) 0 to 15 15 Allows normal filtering

7-8

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

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 Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes 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 Valid range Integer (SACCH periods) 0 to 255 0 1 to 255 Default value 0 Disabled SACCH periods

68P02901W23-S

7-9 Nov 2009

bounce_protect_qual_tmr

Chapter 7: Timer parameters

bounce_protect_qual_tmr

Description
The bounce_protect_qual_tmr timer specifies the number of SACCH periods after an RXQUAL handover. The system applies the bounce_protect_margin value. This timer helps to prevent continuous handover bouncing between cells due to RXQUAL reasons. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes None

Syntax
Change command strings
chg_element bounce_protect_qual_tmr <value> <location> <cell_desc> chg_cell_element bounce_protect_qual_tmr <value> <cell_desc_opt>

Display command string

disp_element bounce_protect_qual_tmr <location> <cell_desc>

Values
Value type Valid range Integer (representing SACCH periods) 0 to 127 0 1 to 127 Default value 0 Disabled SACCH periods

7-10

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

bsc_audit

Description
The bsc_audit timer specifies how long activity is monitored on a dedicated channel. This timer starts when the call is not performing any connection-related processes at the BSC. If this timer expires, the BSC sends an audit message to the BTS. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) No No 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 Valid range Default value Integer (milliseconds) 0 to 1000000 120000

References
Internal name SSM_MTV This is a Motorola defined parameter.

68P02901W23-S

7-11 Nov 2009

bsc_audit_response

Chapter 7: Timer parameters

bsc_audit_response

Description
The bsc_audit_response timer specifies the wait time for audit ssm call response from RRSM timer. This timer starts when the BSC sends an audit message to the BTS. If the bsc_audit_response timer expires a specified number of times in a row without receiving a response from the BTS, the BSC clears the call. The num_audit_retries parameter specifies the number of timer expirations. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) No No None

Syntax
Change command string
chg_element bsc_audit_response <value> <location>

Display command string

disp_element bsc_audit_response <location>

Values
Value type Valid range Default value Integer (milliseconds) 0 to 1000000 30000

References
Internal name SSMAUDIT_TIMER This is a Motorola defined parameter.

7-12

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

bss_overload_control

Description
The bss_overload_control parameter is an RSL Congestion Control (RCC) timer which defines the BSS Overload message interval It is recommended that this timer is set less than bssmap_t6 and greater than bssmap_t5at the MSC. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No None

Syntax
Add/Change command strings
chg_element bss_overload_control <value> bsc

Display command strings

disp_element bss_overload_control bsc

Values
Value type Valid range Default value Integer (milliseconds) 1000 to 1000000 12500

68P02901W23-S

7-13 Nov 2009

bssgp_fc_period_c

Chapter 7: Timer parameters

bssgp_fc_period_c

Description
The bssgp_fc_period_c timer specifies the rate at which the BSS is allowed to send flow control messages for a given BVC or MS. The BSS may send a new Flow Control PDU every C seconds, where C is a value which is predefined and common to the BSS SGSN. The timer starts when the BSS sends a Flow Control PDU for a BVC or MS to the SGSN. When the timer expires, the BSS may send another Flow Control PDU if the condition which caused the sending of the PDU still exists. If the BSS detects a missing FLOW-CONTROL-ACK from the SGSN and the condition which causes the sending of FLOW-CONTROL PDU may be retransmitted immediately. In this case, the BSS may violate the repetition rate defined by the C value. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) No No The GPRS feature must be unrestricted.

NOTE
BSS software processes using this parameter are not notified when the change is made. That is, this parameter can be modified without a reset to a particular device or function.

Syntax
Change command string
chg_element bssgp_fc_period_c <value> <location>

Display command string

disp_element bssgp_fc_period_c <location>

7-14

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Values

Values
Value type Valid range 10 100 Default value Integer (tenths of a second) 10 to 100 1 second 10 seconds 10 (1 second) 1000 milliseconds 10000 milliseconds

References
GSM specification TS GSM 08.18 - Section 8.2.3.4 This is a Motorola defined timer.

68P02901W23-S

7-15 Nov 2009

bssgp_t1_timer

Chapter 7: Timer parameters

bssgp_t1_timer

Description
The bssgp_t1_timer guards the BVC Blocking and Unblocking procedures between the BSS and SGSN. This timer is set when the BSS sends a BVC-BLOCK or BVC-UNBLOCK PDU to the SGSN. This timer is cleared when the BSS receives the BVC-BLOCK or BVC-UNBLOCK-ACK PDU from the SGSN. If a BVC-BLOCK-ACK PDU is not received for a BVC-BLOCK PDU within bssgp_t1_timer seconds, then the BVC-BLOCK PDU procedure is repeated a maximum of bssgp_block_retries attempts. After the maximum attempts fail, the status of the BVC remains blocked, the procedure is stopped and GPRS status BVCI goes OOS. If a BVC-UNBLOCK-ACK PDU is not received for a BVC-UNBLOCK PDU within bssgp_t1_timer seconds, then the BVC-UNBLOCK PDU procedure is repeated a maximum of bssgp_unblock_retries attempts. After the maximum attempts fail, the status of the BVC remains blocked, the procedure is stopped and GPRS status BVCI goes OOS. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) No No The GPRS feature must be unrestricted.

NOTE
BSS software processes using this parameter are not notified when the change is made. That is, this parameter can be modified without a reset to a particular device or function.

Syntax
Change command string
chg_element bssgp_t1_timer <value> <location>

Display command string

disp_element bssgp_t1_timer <location>

7-16

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Values

Values
Value type Valid range Default value Integer (seconds) 1 to 120 3

References
Internal name GSM specification BSSGP T1 TS GSM 08.18 - Section 8.3 This is a Motorola defined timer.

68P02901W23-S

7-17 Nov 2009

bssgp_t2_timer

Chapter 7: Timer parameters

bssgp_t2_timer

Description
The bssgp_t2_timer guards the BVC Reset procedures between the BSS and SGSN. This timer is set when the BSS sends a BVC-RESET to the SGSN. This timer is cleared when the BSS receives the BVC-RESET-ACK from the SGSN. If the timer expires before an ACK is received, the BVC Reset procedure is repeated a maximum number of bssgp_reset_retries attempts. After the maximum attempts fail, the BVC remains blocked. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) No No The GPRS feature must be unrestricted.

NOTE
BSS software processes using this parameter are not notified when the change is made. That is, this parameter can be modified without a reset to a particular device or function.

Syntax
Change command string
chg_element bssgp_t2_timer <value> <location>

Display command string

disp_element bssgp_t2_timer <location>

7-18

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Values

Values
Value type Valid range Default value Integer (seconds) 1 to 120 60

References
GSM specification TS GSM 08.18 - Section 8.4 This is a Motorola defined timer.

68P02901W23-S

7-19 Nov 2009

bssgp_t4_timer

Chapter 7: Timer parameters

bssgp_t4_timer

{27717}

Description
The bssgp_t4_timer parameter guards the GPRS SUSPEND and RESUME procedures. This timer is set when the RESUME PDU or SUSPEND PDU is sent out to SGSN. The timer is cleared when the PCU receives RESUME ACK/NACK PDU or SUSPEND ACK/NACK PDU from SGSN. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No The GPRS optional feature must be unrestricted.

Syntax
Change command string
chg_element bssgp_t4_timer <value> <location>

Display command string

disp_element bssgp_t4_timer <location>

Values
Value type Valid range Default value Integer (milliseconds) 100 to 10000 800

7-20

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

References

References
3GPP specifications In Motorola BSS, bssgp_t4_timer is used for both Suspend and Resume procedure. In 3GPP TS 48.018 section 7.4 and 7.5, corresponding timer is T3 and T4.

68P02901W23-S

7-21 Nov 2009

bssgp_t5_timer

Chapter 7: Timer parameters

bssgp_t5_timer

Description
The bssgp_t5_timer guards the RA-CAPABILTY-UPDATE procedure. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes The GPRS feature must be unrestricted.

Syntax
Change command string
chg_element bssgp_t5_timer <value> <location>

Display command string

disp_element bssgp_t5_timer <location>

Values
Value type Valid range Default value Integer 1000 to 30000 3000

7-22

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

bssgp_t6_timer

Description
The bssgp_t6_timer guards the DOWNLOAD-BSS-PFC procedure. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes The QoS feature must be unrestricted. The value of this parameter cannot be changed when bssgp_pfc_bit equals 1.

Syntax
Change command string
chg_element bssgp_t6_timer <value> <location>

Display command string

disp_element bssgp_t6_timer <location>

Values
Value type Valid range Default value Integer 100 to 10000 3000

68P02901W23-S

7-23 Nov 2009

bssgp_t8_timer

Chapter 7: Timer parameters

bssgp_t8_timer

Description
The bssgp_t8_timer is a PCU timer that guards the MODIFY-BSS-PFC procedure. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No The QoS feature must be unrestricted. The value of this parameter cannot be changed when bssgp_pfc_bit equals 1.

Syntax
Change command string
chg_element bssgp_t8_timer <value> <location>

Display command string

disp_element bssgp_t8_timer <location>

Values
Value type Valid range Default value Integer 100 to 10000 3000

7-24

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

bssmap_t1

Description
The bssmap_t1 timer specifies the wait time for a Blocking Acknowledge or Unblocking Acknowledge from the MSC. The value set must allow enough time for the MSC to respond to a Block/Unblock, even if the MSC is not in a state to respond immediately. A typical value for this timer is 1000 milliseconds. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) No No None

Syntax
Change command string
chg_element bssmap_t1 <value> <location>

Display command string

disp_element bssmap_t1 <location>

Values
Value type Valid range Default value Integer (milliseconds) 0 to 1000000 30000

References
Internal name GSM name GSM specification CLM_T1 T1 8.08 - 3.1.2 8.08 - 3.2.3: BSSMAP timers

68P02901W23-S

7-25 Nov 2009

bssmap_t4

Chapter 7: Timer parameters

bssmap_t4

Description
The bssmap_t4 timer specifies the wait time for return of the Reset Acknowledgment from MSC. Set this timer to allow enough time for the BSS to recover from a global reset. A typical value for this timer is 1000 milliseconds. If this timer expires, it sends a Circuit Reset message and restarts the timer based on a database parameter value. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) No No None

Syntax
Change command string
chg_element bssmap_t4 <value> <location>

Display command string

disp_element bssmap_t4 <location>

Values
Value type Valid range Default value Integer (milliseconds) 0 to 1000000 50000

7-26

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

References

References
Internal name GSM name GSM specification CLM_T4 T4 8.08 - 3.2.3: BSSMAP timers 8.08 - 3.1.4.1.3.1: T4

68P02901W23-S

7-27 Nov 2009

bssmap_t7

Chapter 7: Timer parameters

bssmap_t7

Description
In an inter-BSS (external) handover, the BSC (SSM) timer bssmap_t7 guards against something going wrong at the MSC with the handover that the BSC has triggered. The BSC responds to the MSC and sets the timer to guard against non-receipt of the MSC approval to proceed with the handover. If the timer expires before the HANDOVER COMMAND message is received from the MSC, the result depends on the setting of the handover_recognized_period parameter. The relationship between this parameter and the handover_recognized_period parameter is described in Maintenance Information: BSS Timers (68P02901W58). Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) No No None

Syntax
Change command string
chg_element bssmap_t7 <value> <location>

Display command string

disp_element bssmap_t7 <location>

Values
Value type Valid range Default value Integer (milliseconds) 0 to 1000000 30000

7-28

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

References

References
Internal name GSM name GSM specification SSM_T7 T7 8.08 - 3.2.3: all BSSMAP timers 8.08 - 3.1.5, 3.1.5.1.1: T7

68P02901W23-S

7-29 Nov 2009

bssmap_t8

Chapter 7: Timer parameters

bssmap_t8

Description
The bssmap_t8 timer specifies the wait time for the receipt of a successful handover. This is the sum of the time required for all messages to be sent to the mobile plus the time it takes to access a target and come back, if necessary. This timer starts at the source BTS when it is informed of an inter-cell handover. If this timer expires, the BTS deallocates the old channel at the source cell. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) No No None

Syntax
Change command string
chg_element bssmap_t8 <value> <location>

Display command string

disp_element bssmap_t8 <location>

Values
Value type Valid range Default value Integer (milliseconds) 0 to 1000000 28000

7-30

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

References

References
Internal name GSM name GSM specification RRSM_T8 T8 12.20 - 5.2.7.2 bss Map Timer In Bsc - bss Map T8: 4.08 Section 11 8.08 - 3.2.3: all RRSM timers

68P02901W23-S

7-31 Nov 2009

bssmap_t10

Chapter 7: Timer parameters

bssmap_t10

Description
The bssmap_t10 timer specifies the wait time for return assignment complete MS. Because the bssmap_t10 timer is used twice in the system, it is considered to be a timer in cascade. Its value corresponds to the lowest assigned value. This timer starts when the BTS sends an Assignment Command to the MS. If this timer expires, the call is terminated. The recommended value is 13000 milliseconds. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) No No None

Syntax
Change command string
chg_element bssmap_t10 <value> <location>

Display command string

disp_element bssmap_t10 <location>

Values
Value type Valid range Default value Integer (milliseconds) 0 to 1000000 28000

7-32

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

References

References
Internal name GSM name GSM specification RRSM_T10 T10 4.08 - Section 11 8.08 - 3.2.3: all RRSM timers. Motorola implementation of RRSM_T10 is aligned with the implementation of T3107 as specified in TS GSM 04.08, section 3.4.3.3.

68P02901W23-S

7-33 Nov 2009

bssmap_t11

Chapter 7: Timer parameters

bssmap_t11

Description
The bssmap_t11 timer specifies the wait time for a queued resource request. This timer starts when the BTS attempts to queue an Assignment Request. This timer must be less than the assign_successful timer. A Clear Request message is sent to the MSC when the assign_successful timer expires. If this timer is greater than the assign_successful timer, the call queues for the length of time specified by the assign_successful timer. If this timer expires, the call terminates. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No 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 Valid range Default value Integer (milliseconds) 0 to 1000000 28000

7-34

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

References

References
Internal name GSM name GSM specification RRSM_T11 T11 4.08 - Section 11 8.08 - 3.2.3: all RRSM timers

68P02901W23-S

7-35 Nov 2009

bssmap_t13

Chapter 7: Timer parameters

bssmap_t13

Description
The bssmap_t13 timer specifies the wait time for the reset guard period at the BSS. This timer starts when the Reset message from the MSC is received at the BSS. Set this timer long enough to allow the BSS to clear all active processes after receiving a reset from the MSC but not too long as to slow down recovery time. A typical value for this timer is 1000 milliseconds. If this timer expires, the BSS responds to the MSC with a Reset Acknowledgment. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) No No None

Syntax
Change command string
chg_element bssmap_t13 <value> <location>

Display command string

disp_element bssmap_t13 <location>

Values
Value type Valid range Default value Integer (milliseconds) 0 to 1000000 40000

7-36

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

References

References
Internal name GSM parameter GSM specification CLM_T13 T13 8.08 - 3.2.3: BSSMAP timers

68P02901W23-S

7-37 Nov 2009

bssmap_t19

Chapter 7: Timer parameters

bssmap_t19

Description
The bssmap_t19 timer specifies the wait time for a Reset Circuit Acknowledge from the MSC. The value must allow the MSC enough time to respond to a BSC initiated Reset Circuit. A typical value for this timer is 1000 milliseconds. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) No No None

Syntax
Change command string
chg_element bssmap_t19 <value> <location>

Display command string

disp_element bssmap_t19 <location>

Values
Value type Valid range Default value Integer (milliseconds) 0 to 1000000 30000

References
Internal name GSM name GSM specification CLM_T19 T19 GSM 8.08

7-38

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

bssmap_t20

Description
The bssmap_t20 timer specifies the wait time for Circuit Group Blocking Ack or Circuit Group Unblocking Ack from MSC. A typical value for this timer is 1000 milliseconds. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) No No None

Syntax
Change command string
chg_element bssmap_t20 <value> <location>

Display command string

disp_element bssmap_t20 <location>

Values
Value type Valid range Default value Integer (milliseconds) 0 to 1000000 30000

References
Internal name GSM name GSM specification CLM_T20 T20 GSM 8.08

68P02901W23-S

7-39 Nov 2009

bssmap_tqho

Chapter 7: Timer parameters

bssmap_tqho

Description
The bssmap_tqho timer specifies the maximum allowed queuing time for a handover request. This timer starts when the BSC queues the Handover Request. If this timer expires, the system starts the MTB1 timer to wait for another handover request. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) No No None

Syntax
Change command string
chg_element bssmap_tqho <value> <location>

Display command string

disp_element bssmap_tqho <location>

Values
Value type Valid range Default value Integer (milliseconds) 0 to 1000000 30000

References
Internal name GSM name GSM technical specification SSM_TQHO T_qho GSM 8.008

7-40

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

bts_audit

Description
The bts_audit timer specifies the wait time for the audit timer for the state on dedicated channel. This timer starts when the call is not performing any connection-related processes at the BTS. If this timer expires, the BTS initiates the audit. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) No No 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 Valid range Default value Integer (milliseconds) 0 to 1000000 The lesser value of 60000 or the bsc_audit timer minus 1

References
Internal name GSM specification RRSM_MTW 4.08 - Section 11 8.08 - 3.2.3: all RRSM timers This is a Motorola defined timer.

68P02901W23-S

7-41 Nov 2009

bts_audit_response

Chapter 7: Timer parameters

bts_audit_response

Description
The bts_audit_response timer specifies the wait time for audit Radio Resource State Machine (RRSM) call response from the SCCP State Machine (SSM). Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) No No None

Syntax
Change command string
chg_element bts_audit_response <value> <location>

Display command string

disp_element bts_audit_response <location>

Values
Value type Valid range Default value Integer (milliseconds) 0 to 100000 30000

References
Internal name GSM specification RRSM_AUDIT_TIMER 4.08 - Section 11 8.08 - 3.2.3: all RRSM timers 8.08 - 3.1 This is a Motorola defined parameter.

7-42

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

bts_escalation

Description
The bts_escalation timer specifies how long the BTS can be out of communication with the BSC before resetting. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) No No The parameter is only valid for a remote BTS site.

Syntax
Change command string
chg_element bts_escalation <value> <location>

Display command string

disp_element bts_escalation <location>

Values
Value type Valid range Default value Integer (minutes) 0, and 30 to 360 60 (0 indicates that the BTS does not reset due to loss of communication with the BSC)

68P02901W23-S

7-43 Nov 2009

carrier_free_immediate

Chapter 7: Timer parameters

carrier_free_immediate

Description
The carrier_free_immediate timer specifies the time allowed to free all channels on a carrier when the channels must be freed immediately (regardless of state). This value should be eight times greater than the value required to free a single timeslot. This timer starts when the BTS attempts to deactivate a carrier. The timer stops when carrier deactivation is completed. If the timer expires, the BTS deallocates the carrier. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) No No None

Syntax
Change command string
chg_element carrier_free_immediate <value> <location>

Display command string

disp_element carrier_free_immediate <location>

Values
Value type Valid range Default value Integer (milliseconds) 0 to 1000000 120000

References
Internal name MTCRM_CARRIER_FREE_IMMEDIATE This is a Motorola defined timer.

7-44

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

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 Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) No No None

Syntax
Change command string
chg_element cbch_1 <value> <location>

Display command string

disp_element cbch_1 <location>

Values
Value type Valid range Default value Integer (milliseconds) 0 to 1000000 30000

References
Internal name MTCRM_CBT1 This is a Motorola defined timer.

68P02901W23-S

7-45 Nov 2009

cbch_2

Chapter 7: Timer parameters

cbch_2

Description
The cbch_2 timer specifies the wait time for updating the CBCH response from RSS. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) No No None

Syntax
Change command string
chg_element cbch_2 <value> <location>

Display command string

disp_element cbch_2 <location>

Values
Value type Valid range Default value Integer (milliseconds) 0 to 1000000 30000

References
Internal name MTCRM_CBT2 This is a Motorola defined timer.

7-46

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

cbch_3

Description
The cbch_3 timer specifies the wait time for the CBCH activation acknowledgment from RCI. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) No No None

Syntax
Change command string
chg_element cbch_3 <value> <location>

Display command string

disp_element cbch_3 <location>

Values
Value type Valid range Default value Integer (milliseconds) 0 to 1000000 35000

References
Internal name MTCRM_CBT3 This is a Motorola defined timer.

68P02901W23-S

7-47 Nov 2009

channel_act

Chapter 7: Timer parameters

channel_act

Description
The channel_act timer specifies how long the Radio Subsystem (RSS) waits for a confirmation from the channel coder after sending a CHAN_ACTIVATE request to the channel coders. This request is sent to the channel coders to activate a channel. A typical channel activation can take up to 5 seconds, depending on the activity at a BTS. If this timer expires for a TCH the channel coder is taken out of service when it receives the CHANNEL_ACTIVATION_ACK message from RSS. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) No No None

Syntax
Change command string
chg_element channel_act <value> <location>

Display command string

disp_element channel_act <location>

Values
Value type Valid range Default value Integer (milliseconds) 0 to 10000 10000

References
Internal name TM_CHANNEL_ACT This is a Motorola defined parameter.

7-48

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

channel_teardown

Description
The channel_teardown timer specifies the wait time for channel teardown. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) No No None

Syntax
Change command string
chg_element channel_teardown <value> <location>

Display command string

disp_element channel_teardown <location>

Values
Value type Valid range Default value Integer (milliseconds) 0 to 1000000 28000

References
Internal name GSM technical specification RRSM_MTQ 4.08 - Section 11 8.08 - 3.2.3: all RRSM timers. This is a Motorola defined parameter.

68P02901W23-S

7-49 Nov 2009

cipher_comp_ms

Chapter 7: Timer parameters

cipher_comp_ms

Description
The cipher_comp_ms (and the ciphering_successful) parameters are guard timers that are used to verify that expected messages are received. If an expected message is not received within the specified time, the resources associated with the call are released. This timer starts when the BTS is informed that the MSC is requesting a ciphering procedure. When the MSC sends the cipher mode command to the BSC, it is sent to the SSM. The SSM picks the encryption algorithm and sends it in a ciphering request to the RRSM. It then starts the ciphering_successful timer. When the RRSM receives the ciphering request, it sends a cipher mode command to the MS. It then starts the cipher_comp_ms timer. When the MS returns the Ciphering Mode Complete message to the RRSM, the cipher_comp_ms timer is stopped and a ciphering successful message is sent to the SSM. When the SSM receives the ciphering successful message, it stops the ciphering_successful timer and sends the Cipher Mode Complete message to the MSC. If the timer expires, however, the call terminates. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) No No The ciphering_successful parameter value must be greater than the cipher_comp_ms parameter value.

Syntax
Change command string
chg_element cipher_comp_ms <value> <location>

Display command string

disp_element cipher_comp_ms <location>

7-50

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Values

Values
Value type Valid range Default value Integer (milliseconds) 0 to 1000000 28000

References
Internal name GSM technical specification RRSM_MTA 4.08 - Section 11 8.08 - 3.2.3: all RRSM timers. This is a Motorola defined parameter.

68P02901W23-S

7-51 Nov 2009

ciphering_successful

Chapter 7: Timer parameters

ciphering_successful

Description
The ciphering_successful (and the ciphering_comp_ms) parameters are guard timers that are used to verify that expected messages are received. If an expected message is not received within the specified time, the resources associated with the call are released. When the MSC sends the cipher mode command to the BSC, it is sent to the SSM. The SSM picks the encryption algorithm and sends it in a ciphering request to the RRSM. It then starts the ciphering_successful timer. When the RRSM receives the ciphering request, it sends a ciphering mode command to the MS. It then starts the cipher_comp_ms timer. When the MS returns the Ciphering Mode Complete message to the RRSM, the cipher_comp_ms timer is stopped and a ciphering successful message is sent to the SSM. When the SSM receives the ciphering successful message, it stops the ciphering_successful timer and sends the Cipher Mode Complete message to the MSC. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) No No The ciphering_successful parameter value must be greater than the cipher_comp_ms parameter value.

Syntax
Change command string
chg_element ciphering_successful <value> <location>

Display command string

disp_element ciphering_successful <location>

7-52

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Values

Values
Value type Valid range Default value Integer (milliseconds) 0 to 1000000 30000

References
Internal name SSM_MTI This is a Motorola defined parameter.

68P02901W23-S

7-53 Nov 2009

circuit_reset_ack

Chapter 7: Timer parameters

circuit_reset_ack

Description
The circuit_reset_ack timer specifies the wait time for the circuit reset acknowledgment from internal subsystems. A typical value for this timer is 1000 milliseconds. This is not a BSSAP timer. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) No No None

Syntax
Change command string
chg_element circuit_reset_ack <value> <location>

Display command string

disp_element circuit_reset_ack <location>

Values
Value type Valid range Default value Integer (milliseconds) 0 to 1000000 70000

References
Internal name CLM_MTA1 This is a Motorola defined timer.

7-54

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

clear_cmd_ext_ho

Description
The clear_cmd_ext_ho timer specifies the wait time for the clear command from the MSC when the MSC sends a Handover command. In an external (inter-BSS) handover, the BSC (SSM) timer clear_cmd_ext_ho guards for the original channel being released by the MSC after a successful handover, or a lost MS during handover. Set the clear_cmd_ext_ho timer long enough to ensure that the MS has enough time in the worst case to receive the handover command, attempt to access the target cell, and in failure, to recover back to the source cell. Also set the clear_cmd_ext_ho timer long enough to hold the original channel at the source cell such that in failure to access the target channel, the MS can recover to the old channel (longer than bssmap_t8). Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No This timer is valid only for the BSC.

Syntax
Change command string
chg_element clear_cmd_ext_ho <value> 0

Display command string

disp_element clear_cmd_ext_ho 0

Values
Value type Valid range Default value Integer (milliseconds) 0 to 1000000 30000

68P02901W23-S

7-55 Nov 2009

clear_command

Chapter 7: Timer parameters

clear_command

Description
The clear_command timer specifies the wait time for the clear command from the MSC. This timer starts when the BSC sends the Clear request. If the timer expires, the call terminates. Since the introduction of the clear_cmd_ext_ho timer, the clear_command timer has no relationship with the bssmap_t8 timer. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) No No None

Syntax
Change command string
chg_element clear_command <value> <location>

Display command string

disp_element clear_command <location>

Values
Value type Valid range Default value Integer (milliseconds) 0 to 1000000 30000

References
Internal name SSM_MTG This is a Motorola defined parameter.

7-56

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

dealloc_inact

Description
The dealloc_inact timer specifies the wait time for the deallocation of a channel for which a fatal error indication has been received from the BSS. The channel is held for the specified time in case the connection recovers. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) No Yes None

Syntax
Change command strings
chg_element dealloc_inact <value> <location> <cell_desc> chg_cell_element dealloc_inact <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full] disp_element dealloc_inact <location> <cell_desc>

Values
Value type Valid range Default value Integer (milliseconds) 0 to 1000000 None

References
Internal name MTCRM_DEALLOC_INACT This is a Motorola defined timer.

68P02901W23-S

7-57 Nov 2009

delay_dl_rel_dur

Chapter 7: Timer parameters

delay_dl_rel_dur

Description
The delayed downlink Temporary Block Flow (TBF) release duration BSS parameter, delay_dl_rel_dur, sets the number of block periods for which the network delays the release of a downlink TBF. One block period equals 20 ms. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes (Read-Write) No The GPRS feature must be unrestricted.

Syntax
Change command strings
chg_element delay_dl_rel_dur <value> <location>

Display command strings

disp_element delay_dl_rel_dur <location>

Values
Value type Valid range Default value Integer (20 ms block periods) 15 to 600 Number of block periods in which the network delays the release of a downlink TBF. 50 (1000 ms)

7-58

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

delay_ul_rel_dur

Description
The delay_ul_rel_dur parameter is used to configure the delayed uplink Temporary Block Flow (TBF) release duration. The delay_ul_rel_dur parameter is configurable on a per BSS basis. Type Supported by OMC-R GUI Cell description required Dependencies Operator actions A Yes No GPRS must be unrestricted. 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 Valid range Default value Integer (20 ms block period) 0 to 50 18 Number of block periods in which the network delays the release of an uplink TBF. (360 ms).

68P02901W23-S

7-59 Nov 2009

downlink_sync_timer

Chapter 7: Timer parameters

downlink_sync_timer

Description
The downlink_sync_timer parameter specifies the wait time a Channel Coder Unit (CCU) allows for the downlink TRAU Sync to be lost during a call before generating an error indication. The loss of downlink TRAU Sync in this case should not be due to receiving the idle pattern or the urgent alarm pattern The BSS allows the values of the initial_sync_timer, downlink_sync_timer, uplink_sync_timer and static_sync_timer to be modified so that only one site reset is required for all to be changed. The GPRS feature restricts the modifications of the gprs_alarm_time period, gci_error_inc, gci_error_gen_threshold, gci_error_clr_threshold and static sync timer parameters. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No This parameter is not allowed at a stand-alone BSC or a stand-alone RXCDR. It can be used at a BTS.

Syntax
Change command string
chg_element downlink_sync_timer <value> <location>

NOTE
A site reset occurs when the value of downlink_sync_timer changes and the system is in SYSGEN OFF mode. Resetting the site generates several alarms. However, the system blocks these alarms.

Display command string

disp_element downlink_sync_timer <location>

7-60

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Values

Values
Value type Valid range Default value Integer (milliseconds) 1000 to 3000 1000

68P02901W23-S

7-61 Nov 2009

dynet_retry_time

Chapter 7: Timer parameters

dynet_retry_time

Description
The dynet_retry_time timer specifies the amount of time that the BTS waits for a response from the BSC when the BTS requests a terrestrial backing source. The value for this timer depends on whether satellites are used to connect the BSC to the BTS. Systems that do not use satellites should use the minimum retry value of 150 milliseconds. Satellite systems should use a value 1.2 seconds greater, such as 1.35 seconds. Satellites introduce a one-way delay of 600 milliseconds.

The retry value affects call setup and handover times. The BTS makes three requests for a terrestrial backing resource. Hence, a setting of 1.35 seconds for the retry time requires 4.05 seconds before the BTS stops attempting to allocate resources. At that point, the BTS cannot allocate a TCH due to the lack of a terrestrial backing resource. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) No Yes This parameter is not available unless the containing site is configured to support Dynamic Allocation and this option is in operation. The parameter is invalid for the BSC (location 0).

Syntax
Change command string
chg_element dynet_retry_time <value> <location> <cell_desc>

Display command string

disp_element dynet_retry_time <location> <cell_desc>

7-62

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Values

Values
Value type Valid range Default value Integer (milliseconds) 150 to 3000 150

68P02901W23-S

7-63 Nov 2009

early_classmark_delay

Chapter 7: Timer parameters

early_classmark_delay

Description
The early_classmark_delay timer specifies how long the BSS delays sending the Classmark Update message to the MSC during Early Classmark sending. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No The Multiband Inter-cell Handover feature must be enabled. This parameter can only be viewed at the BSC.

Syntax
Change command string
chg_element early_classmark_delay <value> 0

Display command string

disp_element early_classmark_delay 0

Values
Value type Valid range Default value Integer (milliseconds) 0 to 100000 0

References
GSM specification GSM TS 8.08 Section 3.1.13. This is a Motorola defined parameter

7-64

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

emerg_reserved

Description
The emerg_reserved timer specifies how long a TCH is reserved for an emergency call access. The TCH becomes reserved after an existing call is torn down due to the lack of TCHs at the time of an emergency call access. If emergency call preemption is enabled, traffic channels are reserved for emergency calls waiting on SDCCHs. If idle channels are not available, existing normal calls may be torn down to make TCHs available for the emergency calls. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) No No None

Syntax
Change command string
chg_element emerg_reserved <value> <location>

Display command string

disp_element emerg_reserved <location>

Values
Value type Valid range Default value Integer (milliseconds) 0 to 1000000 120000

References
Internal name MTCRM_EMERG_RESERVED This is a Motorola defined timer.

68P02901W23-S

7-65 Nov 2009

ext_ho_allocation

Chapter 7: Timer parameters

ext_ho_allocation

Description
The ext_ho_allocation timer specifies the wait time for handover allocation. This timer starts when the MSC sends a Handover Request to the BSC. If this timer expires, the handover terminates. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) No No None

Syntax
Change command string
chg_element ext_ho_allocation <value> <location>

Display command string

disp_element ext_ho_allocation <location>

Values
Value type Valid range Default value Integer (milliseconds) 0 to 1000000 30000

References
Internal name SSM_MTC1 This is a Motorola defined parameter.

7-66

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

ext_rtry_cand_prd

Description
The ext_rtry_cand_prd timer specifies the time between successive attempts for a given source cell to attempt an inter-BSS handover to a target cell which had previously rejected a handover attempt because of congestion. When a handover is rejected because of congestion, the source BSS does not attempt to perform an imperative handover to that particular cell during the length of time specified by ext_rtry_cand_prd. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) No Yes The Congestion Relief feature must be enabled. The inter_cell_handover_allowed parameter must be enabled for ECR functionality to work properly.

Syntax
Change command strings
chg_element ext_rtry_cand_prd <value> <location> <cell_desc> chg_cell_element ext_rtry_cand_prd <value> <cell_desc_opt>

Display command string

disp_element ext_rtry_cand_prd <location> <cell_desc>

Values
Value type Valid range Default value Integer (milliseconds) 1 to 1000000 4000

68P02901W23-S

7-67 Nov 2009

flow_control_t1

Chapter 7: Timer parameters

flow_control_t1

Description
The flow_control_t1 timer specifies the wait time before the Flow Control mechanism considers new overload messages. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) No Yes The flow_control_t1 value must be at least 1000 milliseconds less than the flow_control_t2 value.

Syntax
Change command strings
chg_element flow_control_t1 <value> <location> <cell_desc> chg_cell_element flow_control_t1 <value> <cell_desc_opt>

Display command string

disp_element flow_control_t1 <location> <cell_desc>

Values
Value type Valid range Default value Integer (milliseconds) 0 to 1000000 20000

References
Internal name GSM name GSM specification MTCRM_FC_T1 FC_T1 8.58 - 6.3

7-68

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

flow_control_t2

Description
The flow_control_t2 timer specifies the wait time before a previously flow control barred access class is brought back in service. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) No Yes The flow_control_t1 value must be at least 1000 milliseconds less than the flow_control_t2 value.

Syntax
Change command strings
chg_element flow_control_t2 <value> <location> <cell_desc> chg_cell_element flow_control_t2 <value> <cell_desc_opt>

Display command string

disp_element flow_control_t2 <location> <cell_desc>

Values
Value type Valid range Default value Integer (milliseconds) 0 to 1000000 30000

References
Internal name GSM name GSM specification MTCRM_FC_T2 FC_T2 8.58 - 6.3

68P02901W23-S

7-69 Nov 2009

gbl_thrput_period

Chapter 7: Timer parameters

gbl_thrput_period

Description
The gbl_thrput_period timer specifies the time period to compute the statistics GBL_UL_DATA_THRPUT and GBL_DL_DATA_THRPUT. These statistics indicate the throughput of a GBL uplink and downlink. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No The GPRS feature must be unrestricted.

NOTE
BSS software processes using this parameter are not notified when the change is made. That is, this parameter can be modified without a reset to a particular device or function.

Syntax
Change command string
chg_element gbl_thrput_period <value> PCU

Display command string

disp_element gbl_thrput_period PCU

Values
Value type Valid range Default value Integer (tenths of a second) 1 to 255 50

7-70

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

gprs_penalty_time

Description
The gprs_penalty_time timer specifies the length of time for which the parameter gprs_temporary_offset is active for a cell. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes The PBCCH/PCCH feature must be unrestricted.

Syntax
Change command strings
chg_cell_element gprs_penalty_time <value> <location> <cell_desc_opt> chg_element gprs_penalty_time <value> <cell_desc>

Display command strings

disp_cell <cell_id> full disp_element gprs_penalty_time <cell_desc>

Values
Value type Valid range Integer 0 to 31 0 1 2 ... 29 30 31 Default value 0 10 seconds 20 seconds 30 seconds ... 300 seconds 310 seconds 320 seconds 10 seconds

68P02901W23-S

7-71 Nov 2009

gprs_smg30_t3192

Chapter 7: Timer parameters

gprs_smg30_t3192

Description
The gprs_smg30_t3192 timer specifies the MS timers used by the BTS on the BCCH blocks. It specifies the time that the MS continues the assigned PDCHs after receiving its last data block and before it returns to monitoring its paging groups. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes The GPRS feature must be unrestricted. If the parameter smg_gb_vers is less than or equal to 30, then it is used. Otherwise, gprs_t3192 is used.

Syntax
Change command strings
chg_element gprs_smg30_t3192 <value> <location> <cell_desc> chg_cell_element gprs_smg30_t3192 <value> <cell_desc_opt>

Display command string

disp_cell_element gprs_smg30_t3192 <cell_desc>

Values
Value type Valid range Default value Select integer (milliseconds) 500, 1000, 2000, and 4000 500

7-72

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

gprs_t3168

Description
The gprs_t3168 timer specifies the MS timers used by the BTS on the BCCH blocks. This parameter specifies the wait time for the MS waits to get a Packet Uplink Assignment after sending a Packet Resource Request. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes The GPRS feature must be unrestricted.

Syntax
Change command strings
chg_element gprs_t3168 <value> <location> <cell_desc> chg_cell_element gprs_t3168 <value> <cell_desc_opt>

Display command string

disp_element gprs_t3168 <location> <cell_desc>

Values
Value type Valid range Default value Select integer (milliseconds) 500, 1000, 2000, and 4000 4000

68P02901W23-S

7-73 Nov 2009

gprs_t3192

Chapter 7: Timer parameters

gprs_t3192

Description
The gprs_t3192 timer specifies the MS timers used by the BTS on BCCH blocks. This parameter specifies the time that the MS continues the assigned PDCHs after receiving its last data block and before it returns to monitoring its paging groups. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes The GPRS feature must be unrestricted.

Syntax
Change command strings
chg_element gprs_t3192 <value> <location> cell_desc> chg_cell_element gprs_t3192 <value> <cell_desc_opt>

Display command string

disp_element gprs_t3192 <location> <cell_desc>

Values
Value type Valid range Default value Select integer (milliseconds) 0, 80, 120, 160, 200, 500, 1000, and 1500 500

7-74

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

handover_recognized_period

Description
In an inter-BSS (external) handover, the handover_recognized_period parameter specifies the per cell periodicity timer that gives the minimum period between handover attempts for a BTS queuing for handover. It sets the minimum period between internal BTS handover messages being generated and that result in a HANDOVER REQUIRED message being sent from the BSS to the MSC. To set this threshold, enable call queuing and the following equation must be true: h_interval less than handover_recognized_period (T_hand_rqd at the MSC). The MSC parameter h_interval specifies how long a handover request message remains queued by the MSC. The MSC timer T_hand_rqd has the same function as handover_recognized_period. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes Call queueing must be enabled. MSC h_interval < handover_recognized_period

Syntax
Add/Change command strings
add_cell <gsm_cell_desc> <location> chg_element handover_recognized_period <value> <location> <cell_desc> chg_cell_element handover_recognized_period <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full] disp_element handover_recognized_period <location> <cell_desc>

68P02901W23-S

7-75 Nov 2009

Values

Chapter 7: Timer parameters

Values
Value type Valid range Default value Integer (SACCH multiframes) 2 to 64 (even values only) 2

References
GSM parameter GSM specification T_HAND_RQD 5.08 - Appendix A - 6 8.08 - 3.1.17.2, and 3.2.3: Tqho 12.20 - 5.2.8.4 - Adjacent Cell Handover - t_hand_rqd.

7-76

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

ho_ack

Description
In an intra-cell handover, the ho_ack timer specifies the wait time for the BTS/BSC assignment of the target handover channel. If this timer expires before this assignment, the handover attempt fails, the newly assigned channel is freed, and a new handover procedure has to start. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes None

Syntax
Change command strings
chg_element ho_ack <value> <location> <cell_desc> chg_cell_element ho_ack <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full] disp_element ho_ack <location> <cell_desc>

Values
Value type Valid range Default value Integer (milliseconds) 0 to 1000000 5000

References
Internal name MTCRM_HANDOVER_ACK This is a Motorola defined timer.

68P02901W23-S

7-77 Nov 2009

ho_allocation

Chapter 7: Timer parameters

ho_allocation

Description
The ho_allocation timer specifies the wait time for handover allocation from destination cell RRSM. The system starts this timer when the BSC requests a resource from the BTS to perform an intra-BSS handover. If this timer expires, the handover terminates. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) No No None

Syntax
Change command string
chg_element ho_allocation <value> <location>

Display command string

disp_element ho_allocation <location>

Values
Value type Valid range Default value Integer (milliseconds) 0 to 1000000 30000

References
Internal name SSM_MTK This is a Motorola defined timer.

7-78

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

ho_complete

Description
The ho_complete timer specifies the wait time for handover complete from an MS on the target cell. This timer starts when the BTS attempts to assign a channel for a handover. If this timer expires, the handover terminates. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) No No None

Syntax
Change command string
chg_element ho_complete <value> <location>

Display command string

disp_element ho_complete <location>

Values
Value type Valid range Default value Integer (milliseconds) 0 to 1000000 28000

References
Internal name GSM specification RRSM_MTD 4.08 - Section 11 8.08 - 3.2.3: all RRSM timers This is a Motorola defined timer.

68P02901W23-S

7-79 Nov 2009

ho_request

Chapter 7: Timer parameters

ho_request

Description
The ho_request timer specifies the wait time for handover request from the MSC after the SCCP connection is established. This timer starts when the MSC sends an empty CR to the BTS and the BTS informs the BSC. If this timer expires, the handover terminates. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) No No None

Syntax
Change command string
chg_element ho_request <value> <location>

Display command string

disp_element ho_request <location>

Values
Value type Valid range Default value Integer (milliseconds) 0 to 1000000 30000

References
Internal name SSM_MTB1 This is a Motorola defined timer.

7-80

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

ho_successful

Description
The ho_successful parameter specifies the wait time for handover complete from target cell Radio Resource State Machine (RRSM). The system starts this timer when the handover_request_ack message is sent to the MSC. If this timer expires, the call terminates. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) No No None

Syntax
Change command string
chg_element ho_successful <value> <location>

Display command string

disp_element ho_successful <location>

Values
Value type Valid range Default value Integer (milliseconds) 0 to 1000000 30000

References
Internal name SSM_MTJ This is a Motorola defined timer.

68P02901W23-S

7-81 Nov 2009

hop_count_timer

Chapter 7: Timer parameters

hop_count_timer

Description
The hop_count _timer specifies the number of SACCH periods for which intra-cell interference handovers are counted. The hop_count_timer works with both the hop_count and the hr_fr_hop_count parameters to limit the number of intra-cell interference handovers. If the number of handovers defined by the hop_count parameter occur within the time set by the hop_count_timer, the system escalates the handover to an RXQUAL handover to another cell. If the number of quality/interference handovers from Half Rate (HR) to Full Rate (FR) defined by the hr_fr_hop_count parameter occur within the time set by hop_count_timer, the system keeps the mobile on the FR channel if it is a candidate for FR to HR reconfiguration due to congestion. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes None

Syntax
Change command strings
chg_element hop_count_timer <value> <cell_desc> chg_cell_element hop_count_timer <value> <cell_desc_opt>

Display command string

disp_element hop_count_timer <cell_desc>

Values
Value type Valid range Default value Integer (SACCH periods) 0 to 255 0 A value of 0 disables this feature.

7-82

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

initial_sync_timer

Description
The initial_sync_timer specifies the wait time for a Channel Coder Unit (CCU) to receive the initial downlink Transcoding and Rate Adaption Unit (TRAU) frame before generating an error indication. The BSS allows the values of the initial_sync_timer, downlink_sync_timer, uplink_sync_timer and static_sync_timer to be modified so that only one site reset is required for all to be changed. The GPRS feature restricts the modifications of the gprs_alarm_time period, gci_error_inc, gci_error_gen_threshold, gci_error_clr_threshold and static sync timer parameters. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No This timer is not allowed at a stand-alone BSC or RXCDR. It can be used at a BTS. The initial_sync_timer is valid only at BTS sites.

NOTE
A site reset occurs when the value of initial_sync_timer is changed in SYSGEN OFF mode. Resetting the site generates several alarms. However, the system blocks these alarms.

Syntax
Change command string
chg_element initial_sync_timer <value> <location>

Display command string

disp_element initial_sync_timer <location>

68P02901W23-S

7-83 Nov 2009

Values

Chapter 7: Timer parameters

Values
Value type Valid range Default value Integer (1 step = 1 millisecond) 1500 to 7000 4000 (4 seconds)

7-84

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

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 Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No The Location Services feature must be unrestricted.

Syntax
Change command string
chg_element lb_int_bssmap_t4 <value> <location>

Display command string

disp_element lb_int_bssmap_t4 <location>

Values
Value type Valid range Default value Integer (milliseconds) 0 to 1000000 50000

68P02901W23-S

7-85 Nov 2009

lb_int_bssmap_t13

Chapter 7: Timer parameters

lb_int_bssmap_t13

Description
The lb_int_bssmap_t13 (Lb-interface BSSMAP T13) timer is the reset guard timer. The system starts this timer when the reset message from the BSS-based SMLC is received at the BSS. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No The Location Services feature must be unrestricted.

Syntax
Change command string
chg_element lb_int_bssmap_t13 <value> <location>

Display command string

disp_element lb_int_bssmap_t13 <location>

Values
Value type Valid range Default value Integer (milliseconds) 0 to 1000000 40000

References
GSM specification GSM 8.08-3.2.3

7-86

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

lb_int_clear_command

Description
The lb_int_clear_command (Lb-interface clear command) timer is the wait for clear command from the BSS-based SMLC timer. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No 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 Valid range Default value Integer (milliseconds) 0 to 1000000 30000

68P02901W23-S

7-87 Nov 2009

lb_int_sccp_released

Chapter 7: Timer parameters

lb_int_sccp_released

Description
The lb_int_sccp_released (Lb-interface SCCP released) timer is the wait for SCCP released message from BSS-based SMLC timer. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No 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 Valid range Default value Integer (millisecond) 0 to 1000000 30000

7-88

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

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 Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No The Location Services feature must be unrestricted.

Syntax
Change command string
chg_element lb_int_sccp_tconn_est <value> <location>

Display command string

disp_element lb_int_sccp_tconn_est <location>

Values
Value type Valid range Default value Integer (milliseconds) 0 to 1000000 30000

68P02901W23-S

7-89 Nov 2009

lb_int_sccp_tiar

Chapter 7: Timer parameters

lb_int_sccp_tiar

Description
The lb_int_sccp_tiar timer is the receive inactivity control timer for the Lb-interface. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No The Location Services feature must be unrestricted. The value of this parameter should be greater than the lb_int_sccp_tias parameter value. The value of this parameter should be greater than the value of the sccp_tiar at the BSS-based SMLC

Syntax
Change command string
chg_element lb_int_sccp_tiar <value> <location>

Display command string

disp_element lb_int_sccp_tiar <location>

Values
Value type Valid range Default value Integer (milliseconds) 0 to 1000000 30000

References
GSM specification GSM 8.08-3.23

7-90

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

lb_int_sccp_tias

Description
The lb_int_sccp_tias timer is the send activity control timer for the Lb-interface. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No The Location Services feature must be unrestricted. The value of this parameter should be less than the lb_int_sccp_tiar parameter value.

Syntax
Change command string
chg_element lb_int_sccp_tias <value> <location>

Display command string

disp_element lb_int_sccp_tias <location>

Values
Value type Valid range Default value Integer (milliseconds) 0 to 1000000 30000

References
GSM specification GSM 8.08-3.23

68P02901W23-S

7-91 Nov 2009

lb_int_sccp_trel

Chapter 7: Timer parameters

lb_int_sccp_trel

Description
The lb_int_sccp_trel timer is the wait for SCCP release complete timer for the Lb-interface. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No The Location Services feature must be unrestricted.

Syntax
Change command string
chg_element lb_int_sccp_trel <value> <location>

Display command string

disp_element lb_int_sccp_trel <location>

Values
Value type Valid range Default value Integer (milliseconds) 4000 to 15000 10000

References
GSM specification This is a Motorola defined timer.

7-92

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

lb_int_spi

Description
The lb_int_spi timer specifies the amount of time the BSS must wait before initiating an internal reset after either SubSystem Prohibited (SSP) or SPI has occurred over the Lb-interface. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No The Location Services feature must be unrestricted.

Syntax
Change command string
chg_element lb_int_spi <value> <location>

Display command string

disp_element lb_int_spi <location>

Values
Value type Valid range Default value Integer (milliseconds) 10000 to 1000000 60000

References
GSM specification GSM 8.08 - 3.1.15 This is a Motorola defined timer.

68P02901W23-S

7-93 Nov 2009

lb_int_ss7_l2_t1

Chapter 7: Timer parameters

lb_int_ss7_l2_t1

Description
The lb_int_ss7_l2_t1 (Lb-interface MTP layer 2 T1) timer is the alignment ready timer associated with the Lb-interface. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No The Location Services feature must be unrestricted. The valid ranges for this element are dependent upon the value of the ss7_mode.

Syntax
Change command string
chg_element lb_int_ss7_l2_t1 <value> <location>

Display command string

disp_element lb_int_ss7_l2_t1 <location>

Values
Value type Valid range Default value Integer (milliseconds) ss7_mode = 0: 40000 to 50000 ss7_mode = 1: 13000 to 30000 ss7_mode = 0: 50000 ss7_mode =1: 13000

References
ITU specification CCITT Q.703

7-94

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

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 Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No 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 Valid range Default value Integer (millisecond) ss7_mode = 0: 5000 to 150000 ss7_mode = 1: 5000 to 30000 ss7_mode = 0: 25000 ss7_mode =1: 23000

References
ITU specification CCITT Q.703

68P02901W23-S

7-95 Nov 2009

lb_int_ss7_l2_t3

Chapter 7: Timer parameters

lb_int_ss7_l2_t3

Description
The lb_int_ss7_l2_t3 (Lb-interface MTP layer 2 T3) timer is the aligned timer associated with the Lb-interface. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No The Location Services feature must be unrestricted. The valid ranges for this element are dependent upon the value of the ss7_mode.

Syntax
Change command string
chg_element lb_int_ss7_l2_t3 <value> <location>

Display command string

disp_element lb_int_ss7_l2_t3 <location>

Values
Value type Valid range Default value Integer (milliseconds) ss7_mode = 0: 1000 to 1500 ss7_mode = 1: 5000 to 14000 ss7_mode = 0: 1400 ss7_mode =1: 11500

References
ITU specification CCITT Q.703

7-96

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

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 Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No 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 Valid range Default value Integer (milliseconds) 400 to 600 600

References
ITU specification CCITT Q.703

68P02901W23-S

7-97 Nov 2009

lb_int_ss7_l2_t5

Chapter 7: Timer parameters

lb_int_ss7_l2_t5

Description
The lb_int_ss7_l2_t5 (Lb-interface MTP layer 2 T5) timer is the sending SIB timer associated with the Lb-interface. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No The Location Services feature must be unrestricted.

Syntax
Change command string
chg_element lb_int_ss7_l2_t5 <value> <location>

Display command string

disp_element lb_int_ss7_l2_t5 <location>

Values
Value type Valid range Default value Integer (milliseconds) 80 to 120 100

References
ITU specification CCITT Q.703

7-98

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

lb_int_ss7_l2_t6

Description
The lb_int_ss7_l2_t6 (Lb-interface MTP layer 2 T6) timer is the remote congestion timer associated with the Lb-interface. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No The Location Services feature must be unrestricted. The valid ranges for this element are dependent upon the value of the ss7_mode.

Syntax
Change command string
chg_element lb_int_ss7_l2_t6 <value> <location>

Display command string

disp_element lb_int_ss7_l2_t6 <location>

Values
Value type Valid range Default value Integer (millisecond) ss7_mode = 0: 3000 to 6000ss7_mode = 1: 1000 to 6000 ss7_mode = 0: 5000ss7_mode =1: 5000

References
ITU specification ITU Q.703

68P02901W23-S

7-99 Nov 2009

lb_int_ss7_l2_t7

Chapter 7: Timer parameters

lb_int_ss7_l2_t7

Description
The lb_int_ss7_l2_t7 (Lb-interface MTP layer 2 T7) timer is the excessive delay of acknowledgment timer associated with the Lb-interface. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No The Location Services feature must be unrestricted. The valid ranges for this element are dependent upon the value of the ss7_mode.

Syntax
Change command string
chg_element lb_int_ss7_l2_t7 <value> <location>

Display command string

disp_element lb_int_ss7_l2_t7 <location>

Values
Value type Valid range Default value Integer (milliseconds) 500 to 2000 1000

References
ITU specification CCITT Q.703

7-100

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

lb_int_ss7_l3_t1

Description
The lb_int_ss7_l3_t1 (Lb-interface MTP layer 3 T1) timer is the delay to avoid mis-sequencing on changeover timer associated with the Lb-interface. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No 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 Valid range Default value Integer (milliseconds) 500 to 1200 850

References
ITU specification CCITT Q.704

68P02901W23-S

7-101 Nov 2009

lb_int_ss7_l3_t2

Chapter 7: Timer parameters

lb_int_ss7_l3_t2

Description
The lb_int_ss7_l3_t2 (Lb-interface MTP layer 3 T2) timer is the waiting for changeover acknowledgment timer associated with the Lb-interface. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No The Location Services feature must be unrestricted.

Syntax
Change command string
chg_element lb_int_ss7_l3_t2 <value> <location>

Display command string

disp_element lb_int_ss7_l3_t2 <location>

Values
Value type Valid range Default value Integer (milliseconds) 700 to 2000 1400

References
ITU specification CCITT Q.704

7-102

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

lb_int_ss7_l3_t4

Description
The lb_int_ss7_l3_t4 (Lb-interface MTP layer 3 T4) timer is the waiting for changeback acknowledgment (first attempt) timer associated with the Lb-interface. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No The Location Services feature must be unrestricted.

Syntax
Change command string
chg_element lb_int_ss7_l3_t4 <value> <location>

Display command string

disp_element lb_int_ss7_l3_t4 <location>

Values
Value type Valid range Default value Integer (milliseconds) 500 to 1200 850

References
ITU specification CCITT Q.704

68P02901W23-S

7-103 Nov 2009

lb_int_ss7_l3_t5

Chapter 7: Timer parameters

lb_int_ss7_l3_t5

Description
The lb_int_ss7_l3_t5 (Lb-interface MTP layer 3 T5) timer is the waiting for changeback acknowledgment (second attempt) timer associated with the Lb-interface. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No 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 Valid range Default value Integer (milliseconds) 500 to 1200 850

References
ITU specification CCITT Q.704

7-104

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

lb_int_ss7_l3_t12

Description
The lb_int_ss7_l3_t12 (Lb-interface MTP layer 3 T12) timer is the waiting for uninhibit acknowledgment timer associated with the Lb-interface. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No The Location Services feature must be unrestricted.

Syntax
Change command string
chg_element lb_int_ss7_l3_t12 <value> <location>

Display command string

disp_element lb_int_ss7_l3_t12 <location>

Values
Value type Valid range Default value Integer (milliseconds) 800 to 1500 1150

References
ITU specification CCITT Q.704

68P02901W23-S

7-105 Nov 2009

lb_int_ss7_l3_t13

Chapter 7: Timer parameters

lb_int_ss7_l3_t13

Description
The lb_int_ss7_l3_t13 (Lb-interface MTP layer 3 T13) timer is the waiting for force uninhibit timer associated with the Lb-interface. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No The Location Services feature must be unrestricted.

Syntax
Change command string
chg_element lb_int_ss7_l3_t13 <value> <location>

Display command string

disp_element lb_int_ss7_l3_t13 <location>

Values
Value type Valid range Default value Integer (milliseconds) 800 to 1500 1150

References
ITU specification CCITT Q.704

7-106

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

lb_int_ss7_l3_t14

Description
The lb_int_ss7_l3_t14 (Lb-interface MTP layer 3 T14) timer is the waiting for inhibition acknowledgment timer associated with the Lb-interface. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No 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 Valid range Default value Integer (milliseconds) 2000 to 3000 2500

References
ITU specification CCITT Q.704

68P02901W23-S

7-107 Nov 2009

lb_int_ss7_l3_t17

Chapter 7: Timer parameters

lb_int_ss7_l3_t17

Description
The lb_int_ss7_l3_t17 (Lb-interface MTP layer 3 T17) timer is the delay to avoid oscillation of initial alignment failure and link restart timer associated with the Lb-interface. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No The Location Services feature must be unrestricted.

Syntax
Change command string
chg_element lb_int_ss7_l3_t17 <value> <location>

Display command string

disp_element lb_int_ss7_l3_t17 <location>

Values
Value type Valid range Default value Integer (milliseconds) 800 to 1500 1150

References
ITU specification CCITT Q.704

7-108

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

lb_int_ss7_l3_t22

Description
The lb_int_ss7_l3_t22 (Lb-interface MTP layer 3 T22) timer is the local inhibit test timer associated with the Lb-interface. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No The Location Services feature must be unrestricted. The ss7_mode dependent parameters are set to the appropriate defaults when the ss7_mode is changed. The valid values for this element are dependent upon the value of the ss7_mode element.

Syntax
Change command string
chg_element lb_int_ss7_l3_t22 <value> <location>

Display command string

disp_element lb_int_ss7_l3_t22 <location>

Values
Value type Valid range Default value Integer (milliseconds) ss7_mode = 0: 180000 to 360000 ss7_mode = 1: 90000 to 120000 ss7_mode = 0: 270000 ss7_mode =1: 90000

NOTE
The ss7_mode dependent parameters are set to the appropriate defaults when the ss7_mode is changed.

68P02901W23-S

7-109 Nov 2009

References

Chapter 7: Timer parameters

References
ITU specification CCITT Q.704

7-110

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

lb_int_ss7_l3_t23

Description
The lb_int_ss7_l3_t23 (Lb-interface MTP layer 3 T23) timer is the remote inhibit test timer associated with the Lb-interface. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No The Location Services feature must be unrestricted. This parameter is automatically changed to the appropriate default value if the ss7_mode element is changed. The valid values for this element are dependent upon the value of the ss7_mode element.

Syntax
Change command string
chg_element lb_int_ss7_l3_t23 <value> <location>

Display command string

disp_element lb_int_ss7_l3_t23 <location>

Values
Value type Valid range Default value Integer (milliseconds) ss7_mode = 0: 180000 to 360000 ss7_mode = 1: 90000 to 120000 ss7_mode = 0: 270000 ss7_mode =1: 90000

References
ITU specification CCITT Q.704

68P02901W23-S

7-111 Nov 2009

lb_int_ss7_slt_t1

Chapter 7: Timer parameters

lb_int_ss7_slt_t1

Description
The lb_int_ss7_slt_t1 (Lb-interface SS7 Signaling Link Test (SLT) T1) timer is the supervision timer for signaling link test acknowledgment message timer associated with the Lb-interface. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No The Location Services feature must be unrestricted.

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 Valid range Default value Integer (milliseconds) 4000 to 12000 8000

References
ITU specification CCITT Q.707

7-112

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

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. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No 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 Valid range Default value Integer (millisecond) 0 to 1000000 90000

68P02901W23-S

7-113 Nov 2009

lcs_perf_location

Chapter 7: 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 Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No 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 Valid range Default value Integer (millisecond) 0 to 1000000 300000

7-114

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

lcs_segmentation

Description
The lcs_segmentation timer is used for supervising a Location Services segmentation operation. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No The Location Services feature must be unrestricted. The value of this parameter should be less than the value of the lcs_supervision timer.

Syntax
Change command string
chg_element lcs_segmentation <value> <location>

Display command string

disp_element lcs_segmentation <location>

Values
Value type Valid range Default value Integer (millisecond) 0 to 1000000 10000

68P02901W23-S

7-115 Nov 2009

lcs_supervision

Chapter 7: Timer parameters

lcs_supervision

Description
The lcs_supervision timer is used for supervising the overall operation of a location request. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No The Location Services feature must be unrestricted. 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 Valid range Default value Integer (millisecond) 0 to 1000000 30000

7-116

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

mode_modify

Description
The mode_modify timer specifies the wait time for the MODE MODIFY message to be sent from Abis to Physical Layer 1. If this timer expires before the MODE MODIFY message arrives, the MODE MODIFY ACKNOWLEDGE message is sent in response to Call Processing (CP) and RSS generates a MODE_MODIFY_ACK message to CP . Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) No No The value of the mode_modify_ack CP timer must be greater than or equal to the RSS timers + 10 ms.

Syntax
Change command string
chg_element mode_modify <value> <location>

Display command string

disp_element mode_modify <location>

Values
Value type Valid range Default value Integer (milliseconds) 0 to 10000 10000

References
Internal name TM_MODE_MODIFY This is a Motorola defined timer.

68P02901W23-S

7-117 Nov 2009

mode_rr_modify_ack

Chapter 7: Timer parameters

mode_rr_modify_ack

Description
The mode_rr_modify_ack timer specifies the wait time for the MODE MODIFY ACKNOWLEDGE message from the MS. This timer starts when the BTS receives confirmation on modification of the channel mode. When this timer expires, the BTS aborts the mode modification. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) No No 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 Valid range Default value Integer (milliseconds) 0 to 1000000 28000

7-118

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

References

References
Internal name GSM technical specification RRSM_MTY 4.08 - Section 11 8.08 - 3.2.3: all RRSM timers. This is a Motorola defined timer.

68P02901W23-S

7-119 Nov 2009

ms_sapi3_est

Chapter 7: Timer parameters

ms_sapi3_est

Description
The ms_sapi3_est timer specifies the wait time for SAPI 3 SMS establishment from the MS. This is an internal timer dealing with SAPI3 connection procedures. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) No No None

Syntax
Change command string
chg_element ms_sapi3_est <value> <location>

Display command string

disp_element ms_sapi3_est <location>

Values
Value type Valid range Default value Integer (milliseconds) 0 to 1000000 28000

7-120

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

References

References
Internal name GSM specification RRSM_MTE1 12.20 - 5.2.7.2 BSS Map Timer In BSC 4.08 - Section 11 8.08 - 3.2.3: all RRSM timers 8.08 - 3.1. This is a Motorola defined timer.

68P02901W23-S

7-121 Nov 2009

nc_non_drx_period

Chapter 7: Timer parameters

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. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No The GPRS and NCCR features must be unrestricted. The PCU must be equipped.

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

Syntax
Change command string
chg_element nc_non_drx_period <value> <location>

Display command string

disp_element nc_non_drx_period <location>

7-122

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Values

Values
Value type Valid range Integer 0 to 7 0 1 2 3 4 5 6 7 Default value No non_drx_period set 0.24 seconds 0.48 seconds 0.72 seconds 0.96 seconds 1.20 seconds 1.44 seconds 1.96 seconds

2 (0.48 seconds)

68P02901W23-S

7-123 Nov 2009

nc_reporting_period_i

Chapter 7: Timer parameters

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 Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No The GPRS and NCCR features must be unrestricted. The PCU must be equipped.

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

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 Valid range Integer 4 to 6 4 5 6 Default value 6 15.36 seconds 30.72 seconds 61.44 seconds

7-124

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

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. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No The GPRS and NCCR features must be unrestricted. The PCU must be equipped.

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

Syntax
Change command string
chg_element nc_reporting_period_t <value> <location>

Display command string

disp_element nc_reporting_period_t <location>

68P02901W23-S

7-125 Nov 2009

Values

Chapter 7: Timer parameters

Values
Value type Valid range Integer 0 or 6 0 1 2 3 4 5 6 Default value 2 0.96 seconds 1.92 seconds 3.84 seconds 7.68 seconds 15.36 seconds 30.72 seconds 61.44 seconds

7-126

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

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 neighbors. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes The Concentric Cells feature must be unrestricted the inner_zone_alg element must be set to 2.

Syntax
Change command strings
chg_element neighbor_report_timer <value> <location> <cell_desc> chg_cell_element neighbor_report_timer <value> <cell_desc_opt>

Display command string

disp_element neighbor_report_timer <location> <cell_desc>

Values
Value type Valid range Default value Integer (SACCH periods) 0 to 255 10

68P02901W23-S

7-127 Nov 2009

ns_alive_timer

Chapter 7: Timer parameters

ns_alive_timer

Description
The ns_alive_timer guards the NS Test Procedure between the BSS and the SGSN. This timer is set when the BSS sends an NS-ALIVE-ACK PDU to the SGSN. This timer is cleared when the BSS receives the NS-ALIVE-ACK from the SGSN. If the timer expires before the ACK is received, the NS Test Procedure is repeated a maximum of ns_alive_retries attempts. After the maximum number of attempts fail, the NS Test Procedure is stopped and the NSVC is marked dead and blocked. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) No No The GPRS feature must be unrestricted.

NOTE
BSS software processes using this parameter are not notified when the change is made. That is, this parameter can be modified without a reset to a particular device or function.

Syntax
Change command string
chg_element ns_alive_timer <value> <location>

Display command string

disp_element ns_alive_timer <location>

Values
Value type Valid range Default value Integer (seconds) 1 to 30 3

7-128

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

ns_block_timer

Description
The ns_block_timer guards the NS Blocking and Unblocking Procedures between the BSS and SGSN. This timer is set when the BSS sends an NS-BLOCK or NS-UNBLOCK PDU to the SGSN. This timer is cleared when BSS receives the NS-BLOCK-ACK or NS-UNBLOCK-ACK PDU from the SGSN. If the timer expires before an ACK is received, the NS Blocking or Unblocking procedure is repeated a maximum of ns_block_retries attempts. After the maximum attempts fail, the NSVC remains unblocked. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) No No The GPRS feature must be unrestricted.

NOTE
BSS software processes using this parameter are not notified when the change is made. That is, this parameter can be modified without a reset to a particular device or function.

Syntax
Change command string
chg_element ns_block_timer <value> <location>

Display command string

disp_element ns_block_timer <location>

Values
Value type Valid range Default value Integer (seconds) 1 to 30 3

68P02901W23-S

7-129 Nov 2009

ns_reset_period

Chapter 7: Timer parameters

ns_reset_period

Description
The ns_reset_period timer specifies the period for which the BSS attempts to reset an NSVC using the NS Reset Procedure. This timer is set when the BSS initiates the NS Reset Procedure. If the NS-RESET-ACK is not returned before ns_reset_timer expires, then the NS Reset Procedure is repeated for the ns_reset_period. If the NS Reset Procedure is not successful before the ns_reseet_period expires, the NSVC remains unblocked. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) No No The GPRS feature must be unrestricted.

NOTE
BSS software processes using this parameter are not notified when the change is made. That is, this parameter can be modified without a reset to a particular device or function.

Syntax
Change command string
chg_element ns_reset_period <value> <location>

Display command string

disp_element ns_reset_period <location>

7-130

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Values

Values
Value type Valid range Default value Integer (seconds) 1 to 250 125

68P02901W23-S

7-131 Nov 2009

ns_reset_timer

Chapter 7: Timer parameters

ns_reset_timer

Description
The ns_reset_timer guards the NS Reset Procedure between the BSS and the SGSN. This timer is set when the BSS sends an NS-RESET to the SGSN. This timer is cleared when the BSS receives NS-RESET-ACK from the SGSN. If the timer expires before the ACK is received, the NS Reset Procedure is repeated until the ns_reset_period expires. If the NS Reset Procedure is not successful before the ns_reset_period expires, the NSVC remains blocked. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) No No This parameter can be used only if the GPRS feature is unrestricted.

NOTE
BSS software processes using this parameter are not notified when the change is made. That is, 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

Chapter 7: Timer parameters

Values
Value type Valid range Integer (1 Step = 20 seconds) 0 to 31 0 1 2 ... 30 20 seconds 40 seconds 60 seconds ... 620 seconds

Default value

NOTE
A value of 31 is reserved to indicate that cell_reselect_offset is subtracted from C2 and temporary_offset is ignored.

References
GSM parameter GSM specification PENALTY_TIME TSGSM 4.08 Table 10.32a Section 10.5.2.35 TSGSM 5.08 TSGSM 3.22

7-138

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

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. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No This parameter cannot be modified for a GPRS PCU MMS.

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 Valid range Default value Integer (seconds) 0 to 3600 0 50 (M-Cell only)

68P02901W23-S

7-139 Nov 2009

psi1_repeat_period

Chapter 7: Timer parameters

psi1_repeat_period

Description
The psi1_repeat_period timer specifies the time interval between consecutive Packet System Information (PSI) type 1 messages in 52-frame multiframes for a cell. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes The PBCCH/PCCCH optional feature must be unrestricted.

NOTE
BSS software processes using this parameter are not notified when the change is made. That is, this parameter can be modified without a reset to a particular device or function.

Syntax
Change command string
chg_element psi1_repeat_period <value> <location> <cell_desc> chg_cell_element psi1_repeat_period <value> <cell_desc_opt>

Display command string

disp_cell <cell_id> full disp_element psi1_repeat_period <location> <cell_desc>

7-140

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Values

Values
Value type Valid range Integer 0 to 16 0 1 to 16 Default value 5 Period calculated by algorithm (based on bs_pbcch_blks and number of PSI instances in low repetition rate group). Frequency of PSI1 in a 52-frame multiframe Five PSI1s in a 52-frame multiframe

Table 7-1 shows the combinations of psi1_repeat_period and bs_pbcch_blks that are not permitted.

Table 7-1

Impermissible combinations of psi1_repeat_period and bs_pbcch_blks

psi1_repeat_period 1 1 Allowed No No

bs_pbcch_blks 1 2

68P02901W23-S

7-141 Nov 2009

radio_chan_released

Chapter 7: Timer parameters

radio_chan_released

Description
The radio_chan_released timer specifies how long the BSC waits for the BTS to release a call. This timer starts when one of the following occurs: The BSC sends the Clear Request to the MSC. The MSC sends the Clear command to the BSC. A (no operator actions) No No None

Type Supported by OMC-R GUI Cell description required Dependencies

Syntax
Change command string
chg_element radio_chan_released <value> <location>

Display command string

disp_element radio_chan_released <location>

Values
Value type Valid range Default value Integer (milliseconds) 0 to 1000000 30000

References
Internal name SSM_MTH This is a Motorola defined timer.

7-142

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

red_psp_audit_tmr

Description
The red_psp_audit_tmr timer specifies the audit interval for checking the health of the redundant PSP (MPROC). Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) No No GPRS must be unrestricted

Syntax
Change command string
chg_element red_psp_audit_tmr <value> <location>

Display command string

disp_element red_psp_audit_tmr <location>

Values
Value type Valid range Default value Integer 0 to 24 24

References
This timer is a Motorola defined timer.

68P02901W23-S

7-143 Nov 2009

register_exp

Chapter 7: Timer parameters

register_exp

Description
The register_exp timer specifies the wait time for the CRM to initiate registration with the BSC. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) No No None

Syntax
Change command string
chg_element register_exp <value> <location>

Display command string

disp_element register_exp <location>

Values
Value type Valid range Default value Integer (milliseconds) 0 to 1000000 120000

References
Internal name MTCRM_REGISTER_EXP This is a Motorola defined timer.

7-144

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

rf_chan_rel_ack

Description
The rf_chan_rel_ack timer specifies the wait time an RF channel release (acknowledgment) message from the Radio Subsystem (RSS). Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes 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_opt>

Display command strings

disp_cell <cell_id> [full] disp_cell <cell_id> [full]

Values
Value type Valid range Default value Integer (milliseconds) 0 to 1000000 5000

References
Internal name MTCRM_RF_CHAN_REL_ACK This is a Motorola defined timer.

68P02901W23-S

7-145 Nov 2009

rr_ny1_rep

Chapter 7: 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. RSS Layer 1 process uses this parameter. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes rr_t3105

Syntax
Change command strings
chg_element rr_ny1_rep <value> <location> <cell_desc> chg_cell_element rr_ny1_rep <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full] disp_element rr_ny1_rep <location> <cell_desc>

Values
Value type Valid range Default value Integer (the amount of repetitions) 0 to 200 20

7-146

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

References

References
Internal name GSM specification TM_HO_NY1_REP 4.08 - 3.4.4.2 4.08 - 3.4.4.2.2: NY1 12.20 - 5.3.8.11: NY1 This is a Motorola defined timer.

68P02901W23-S

7-147 Nov 2009

rr_t3103

Chapter 7: Timer parameters

rr_t3103

Description
The rr_t3103 timer specifies how long the BSS waits for an internal handover to complete. The purpose is to keep the old channels long enough for the MS to retain the ability to return to the old channels when necessary and to release the channels if the call is dropped. The rr_t3103 wait time must have a longer duration than the combined wait time for a handover command to be sent plus the maximum time it takes to attempt to establish a data link with a multiframe mode. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes None

Syntax
Change command strings
chg_element rr_t3103 <value> <location> <cell_desc> chg_cell_element rr_t3103 <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full] disp_element rr_t3103 <location> <cell_desc>

Values
Value type Valid range Default value Integer (milliseconds) 0 to 1000000 30000

7-148

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

References

References
GSM name GSM specification T3103 4.08 - 3.4.4 4.08 - 11.1.2

68P02901W23-S

7-149 Nov 2009

rr_t3101

Chapter 7: 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 Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes The rr_t3101 value must be greater than the maximum length of time it takes for a Layer 2 establishment attempt.

Syntax
Change command strings
chg_element rr_t3101 <value> <location> <cell_desc> chg_cell_element rr_t3101 <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full] disp_element rr_t3101 <location> <cell_desc>

Values
Value type Valid range Default value Integer (milliseconds) 0 to 1000000 5000 (add_cell default)

References
GSM name GSM specification T3101 4.08

7-150

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

rr_t3105

Description
The rr_t3105 parameter specifies the repetition between transmissions of the Physical Information messages during the handover procedure. The RSS uses this value to calculate the number of blocks to skip. This value is sent to the DRI. Enter the values for this parameter in increments of 20 milliseconds. Although the system accepts any value between 0 and 200, only multiples of 20 are significant. If a value is entered that is not a 20 millisecond increment, the BSS rounds the entered value to the nearest multiple of 20 that is less than the value entered. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes None

Syntax
Change command strings
chg_element rr_t3105 <value> <location> <cell_desc> chg_cell_element rr_t3105 <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full] disp_element rr_t3105 <location> <cell_desc>

Values
Value type Valid range Default value Select integer (milliseconds in 20 millisecond increments) 0 to 200 60

68P02901W23-S

7-151 Nov 2009

References

Chapter 7: Timer parameters

References
Internal name GSM name GSM specification TM_HO_T3105 T3105 4.08 - 3.4.4.2 12.20 - 5.2.8.5: T3105

7-152

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

rr_t3109

Description
The rr_t3109 timer is used during the channel release procedure in case of a radio link timeout. When the timer expires, the CRM sends an RF channel release message to the RSS. Set the rr_t3109 timer to a higher value than the CRM radio_link_timeout parameter (T100). To ensure that the network does not put two MSs on the same dedicated channel, the network must hold onto a channel that has lost radio link long enough for the MS to release it.

NOTE
The recommended rr_t3109 value is four 96-SACCH blocks (1.5 times the radio_link_timeout parameter value).

Type Supported by OMC-R GUI Cell description required Dependencies

A (no operator actions) No No The rr_t3109 value must be greater than the rr_t3111_sd and the rr_t3111_tch values.

Syntax
Change command strings
chg_element rr_t3109 <value> <location> chg_cell_element rr_t3109 <value>

Display command strings

disp_cell <cell_id> [full] disp_element rr_t3109 <location> <cell_desc>

68P02901W23-S

7-153 Nov 2009

Values

Chapter 7: Timer parameters

Values
Value type Valid range Default value Integer (milliseconds) 0 to 1000000 14400

References
GSM name GSM specification T3109 4.08 - 3.5: T3109, 4.08 - 11.1.2, 11.2 12.20 - 5.2.8.5 BTS air timer - air int BTS T4: T3109

7-154

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

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 signaling link. The purpose is to allow some time for the possible repetition of the disconnection of the main signaling link. This timer starts whenever the BTS attempts to configure a hopping timeslot. This timer stops when the procedure completes. The rr_t3111_sd timer causes the BSS to wait before the channel in question is allocated to another connection. Set the rr_t3111_sd value equal to the value of T3110 (a timer in the MS that is hard coded by the MS manufacturer).

NOTE
The rr_t3111_sd and rr_t3111_tch timers replace the rr_t3111 timer beginning in GRS4.

Type Supported by OMC-R GUI Cell description required Dependencies

A (no operator actions) Yes Yes The rr_t3111_sd value must be less than the rr_t3109 value. The rr_t3111_sd value must be set equal to the value of T3110.

Syntax
Change command strings
chg_element rr_t3111_sd <value> <location> <cell_desc> chg_cell_element rr_t3111_sd <value> <cell_desc_opt>

68P02901W23-S

7-155 Nov 2009

Values

Chapter 7: Timer parameters

Display command strings

disp_cell <cell_id> [full] disp_element rr_t3111_sd <location> <cell_desc>

Values
Value type Valid range Default value Integer (milliseconds) 0 to 1000000 1500

References
GSM name GSM specification T3111 4.08 - 3.5: T3111 4.08 - 11.1.2, 11.2 12.20 - 5.2.8.5 bts air timer - air int BTS T5: T3111

7-156

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

rr_t3111_tch

Description:
The rr_t311_tch timer specifies the delay for the deactivation of a traffic channel (TCH) after the disconnection of the main signaling link. The purpose is to allow some time for the possible repetition of the disconnection of the main signaling link. This timer starts whenever the BTS attempts to configure a hopping timeslot. This timer stops when the procedure completes. The rr_t3111_tch timer causes the BSS to wait before the channel in question is allocated another connection. Set the rr_t3111_tch parameter value to a value equal to the value of T3110 (a timer in the MS that is hard coded by the MS manufacturer).

NOTE
The rr_t3111_sd and rr_t3111_tch timers replace the rr_t3111 timer beginning in GRS4.

Type Supported by OMC-R GUI Cell description required Dependencies

A (no operator actions) Yes Yes The rr_t3111_tch value must be less than the rr_t3109 value. The rr_t3111_tch value must be set equal to the value of T3110.

Syntax
Change command strings
chg_element rr_t3111_tch <value> <location> <cell_desc> chg_cell_element rr_t3111_tch <value> <cell_desc_opt>

68P02901W23-S

7-157 Nov 2009

Values

Chapter 7: Timer parameters

Display command strings

disp_cell <cell_id> [full] disp_element rr_t3111_tch <location> <cell_desc>

Values
Value type Valid range Default value Integer (milliseconds) 0 to 1000000 1500

References
GSM parameter GSM technical specification T3111 4.08 - 3.5: T3111 4.08 - 11.1.2, 11.2 12.20 - 5.2.8.5 bts air timer - air int BTS T5: T3111

7-158

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

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 signaling terminates. The timeout value is broadcast in a SYSTEM INFORMATION message. A value of 0 indicates an infinite timeout value. The rr_t3212 timer value should give a reasonable time between periodic location updates. This timer stops when mobility management service or signaling initiates. Subsystem/Process Type Supported by OMC-R GUI Cell description required Dependencies CRM A (no operator actions) Yes Yes None

Syntax
Change command strings
chg_element rr_t3212 <value> <location> <cell_desc> chg_cell_element rr_t3212 <value> <cell_desc_opt>

Display command strings

disp_cell <cell_id> [full] disp_element rr_t3212 <location> <cell_desc>

68P02901W23-S

7-159 Nov 2009

Values

Chapter 7: Timer parameters

Values
Value type Valid range Integer (1 step = 6 minutes) 0 to 255 0 1 2 ... ... 255 Default value 10 0 minutes 6 minutes 12 minutes ... ... 1530 minutes (25.5 hours)

References
GSM parameter GSM technical specification T3212 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

7-160

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

rsl_congestion_alarm_timer

Description
The rsl_congestion_alarm_timer parameter is an RSL Congestion Control (RCC) alarm timer which defines the minimum interval between reporting and clearing RSL congestion alarms to the OMC-R on a per RSL-LCF basis. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No None

Syntax
Add/Change command strings
chg_element rsl_congestion_alarm_timer <value> bsc

Display command strings

disp_element rsl_congestion_alarm_timer bsc

Values
Value type Valid range Default value Integer (milliseconds) 1000 to 600000 600000

68P02901W23-S

7-161 Nov 2009

rtry_cand_prd

Chapter 7: Timer parameters

rtry_cand_prd

Description
The rtry_cand_prd timer specifies how long a cell can be marked as congested and cannot 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 required 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 neighbors, which could vary in congestion levels. Using the source cell value for all its neighbors does not give this flexibility. This applies only to internal neighbors. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes 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 has 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_opt>

Display command string

disp_element rtry_cand_prd <location> <cell_desc>

7-162

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Values

Values
Value type Valid range Default value Integer (milliseconds) 1 to 1000000 4000

68P02901W23-S

7-163 Nov 2009

sacch_info

Chapter 7: 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 Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) No No None

Syntax
Change command string
chg_element sacch_info <value> <location>

Display command string

disp_element sacch_info <location>

Values
Value type Valid range Default value Integer (milliseconds) 0 to 10000 2000

7-164

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

References

References
Internal name GSM specification TM_SACCH_INFO 08.58 - 4.12 and 8.4.20 This is a Motorola defined timer.

68P02901W23-S

7-165 Nov 2009

sccp_released

Chapter 7: 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 Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) No No None

Syntax
Change command string
chg_element sccp_released <value> <location>

Display command string

disp_element sccp_released <location>

Values
Value type Valid range Default value Integer (milliseconds) 0 to 1000000 30000

References
Internal name SSM_MTL This is a Motorola defined timer.

7-166

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

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 Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) No No None

Syntax
Change command string
chg_element sccp_tconn_est <value> <location>

Display command string

disp_element sccp_tconn_est <location>

Values
Value type Valid range Default value Integer (milliseconds) 0 to 1000000 30000

References
Internal name TCONN_EST This is a Motorola defined timer.

68P02901W23-S

7-167 Nov 2009

sccp_tiar

Chapter 7: 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 Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) No No 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 Valid range Default value Integer (milliseconds) 0 to 1000000 30000

7-168

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

References

References
Internal name GSM specification SSM_TIAR 8.08 - 3.2.3: all BSSMAP timers ITU-TSS (blue book) Q.714: TIAS, TIAR This is a Motorola defined timer.

68P02901W23-S

7-169 Nov 2009

sccp_tias

Chapter 7: 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 Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) No No 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 Valid range Default value Integer (milliseconds) 0 to 1000000 30000

References
Internal name GSM specification SSM_TIAS 8.08 - 3.2.3: all BSSMAP timers ITU-TSS (blue book) Q.714: TIAS, TIAR. This is a Motorola defined timer.

7-170

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

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 Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) No No None

Syntax
Change command string
chg_element sccp_trel <value> <location>

Display command string

disp_element sccp_trel <location>

Values
Value type Valid range Default value Integer (milliseconds) 4000 to 15000 10000

References
GSM parameter TREL This is a Motorola defined parameter.

68P02901W23-S

7-171 Nov 2009

sm_audit_response

Chapter 7: Timer parameters

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 Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) No No None

Syntax
Change command string
chg_element sm_audit_response <value> <location>

Display command string

disp_element sm_audit_response <location>

Values
Value type Valid range Default value Integer (milliseconds) 0 to 1000000 30000

References
Internal name SSM_MTX This is a Motorola defined parameter.

7-172

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

spi

Description
The spi timer specifies the wait time before initiating an internal reset after either Subsystem Prohibited (SSP) or Signaling 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 Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) No No None

Syntax
Change command string
chg_element spi <value> <location>

Display command string

disp_element spi <location>

Values
Value type Valid range Default value Integer (milliseconds) 10000 to 1000000 60000

68P02901W23-S

7-173 Nov 2009

References

Chapter 7: Timer parameters

References
Internal name GSM name GSM specification CLM_SPI_TIMER SPI 8.08 section 3.1.15 This is a Motorola defined timer.

7-174

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

ss7_l2_t1

Description
The ss7_l2_t1 timer specifies the alignment ready timer. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No 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 Valid range Integer (milliseconds) The range of values is dependent upon the value of the ss7_mode parameter 40000 to 50000 13000 to 30000 Default value If ss7_mode = 0 (ITU) If ss7_mode = 1 (ANSI)

The default value is dependent upon the value of the ss7_mode parameter. 50000 13000 If ss7_mode = 0 (ITU) If ss7_mode = 1 (ANSI)

NOTE
The default value is set when the ss7_mode parameter value is changed.

68P02901W23-S

7-175 Nov 2009

References

Chapter 7: Timer parameters

References
Internal name GSM name GSM specification T1 (ITU) T1 ITU (blue book) Q.703 page 72.

7-176

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

ss7_hsp_l2_t1

{28337}

Description
During the process of bringing an HSP MTL link into service, the BSC timer ss7_hsp_l2_t1, known as the alignment ready timer, is used for the signaling link alignment procedure. This timer is set in the BSS database using ss7_hsp_l2_t1 parameter. Security Level Command Type Supported by OMC-R GUI Cell description required Dependencies 4 A (no operator actions) Yes No The HSP MTL feature must be unrestricted.

Syntax
Change command string
chg_element ss7_hsp_l2_t1 <value> <location>

Display command string

disp_element ss7_hsp_l2_t1 <location>

Values
Value type Valid range Default value Integer (milliseconds) 25000 to 350000. 300000

68P02901W23-S

7-177 Nov 2009

References

Chapter 7: Timer parameters

References
Internal name GSM name GSM specification T1 (ITU) T1 ITU (blue book) Q.703 pg 72

7-178

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

ss7_l2_t1

Description
The ss7_l2_t1 timer specifies the alignment ready timer. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No ss7_mode

Syntax
Change command string
chg_element ss7_l2_t1 <value> <location>

Display command string

disp_element ss7_l2_t1 <location>

The default value is dependent upon the value of the ss7_mode parameter. 50000 13000 If ss7_mode = 0 (ITU) If ss7_mode = 1 (ANSI)

NOTE
The default value is set when the ss7_mode parameter value is changed.

68P02901W23-S

7-179 Nov 2009

References

Chapter 7: Timer parameters

References
Internal name GSM name GSM specification T1 (ITU) T1 ITU (blue book) Q.703 pg 72

7-180

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

ss7_l2_t2

Description
The ss7_l2_t2timer specifies the not aligned timer. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No 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 Valid range Integer (milliseconds) The range of values is dependent upon the value of the ss7_mode parameter 5000 to 150000 5000 to 30000 Default value If ss7_mode = 0 (ITU) If ss7_mode = 1 (ANSI)

The default value is dependent upon the value of the ss7_mode parameter. 25000 23000 If ss7_mode = 0 (ITU) If ss7_mode = 1 (ANSI)

NOTE
The default value is set when the ss7_mode parameter value is changed.

68P02901W23-S

7-181 Nov 2009

References

Chapter 7: Timer parameters

References
Internal name GSM name GSM specification T2 (ITU) T2 ITU (blue book) Q.703 pg 72

7-182

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

ss7_l2_t3

Description
The ss7_l2_t3 timer specifies the aligned timer. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No 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 Valid range Integer (milliseconds) The range of values is dependent upon the value of the ss7_mode parameter 1000 to 1500 5000 to 14000 Default value If ss7_mode = 0 (ITU) If ss7_mode = 1 (ANSI)

The default value is dependent upon the value of the ss7_mode parameter. 1400 11500 If ss7_mode = 0 (ITU) If ss7_mode = 1 (ANSI)

NOTE
The default value is set when the ss7_mode parameter value is changed.

68P02901W23-S

7-183 Nov 2009

References

Chapter 7: Timer parameters

References
Internal name GSM parameter GSM technical specification T3 (ITU) T3 ITU (blue book) Q.703 pg 72

7-184

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

ss7_l2_t4

Description
The ss7_l2_t4 timer specifies the emergency proving period timer. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No None

Syntax
Change command string
chg_element ss7_l2_t4 <value> <location>

Display command string

disp_element ss7_l2_t4 <location>

Values
Value type Valid range Default value Integer (milliseconds in increments of 5 milliseconds) 400 to 600 600

References
Internal name GSM parameter GSM technical specification T4 (ITU) T4 ITU (blue book) Q.703 pg 72

68P02901W23-S

7-185 Nov 2009

ss7_l2_t5

Chapter 7: Timer parameters

ss7_l2_t5

Description
The ss7_l2_t5 timer specifies the sending SIB timer. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No None

Syntax
Change command string
chg_element ss7_l2_t5 <value> <location>

Display command string

disp_element ss7_l2_t5 <location>

Values
Value type Valid range Default value Integer (milliseconds in increments of 5 milliseconds) 80 to 120 100

References
Internal name GSM name GSM technical specification T5 (ITU) T5 ITU (blue book) Q.703 pg 72

7-186

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

ss7_l2_t6

Description
The ss7_l2_t6 timer specifies the remote congestion timer. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator action) Yes No 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 Valid range Integer (milliseconds) The range of values is dependent upon the value of the ss7_mode parameter 3000 to 6000 1000 to 6000 Default value If ss7_mode = 0 (ITU) If ss7_mode = 1 (ANSI)

The default value is dependent upon the value of the ss7_mode parameter. 5000 5000 If ss7_mode = 0 (ITU) If ss7_mode = 1 (ANSI)

68P02901W23-S

7-187 Nov 2009

References

Chapter 7: Timer parameters

References
Internal name GSM parameter GSM technical specification T6 (ITU) T6 ITU (blue book) Q.703 pg 72.

7-188

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

ss7_l2_t7

Description
The ss7_l2_t7 timer specifies the excessive delay of acknowledgment timer. If the error correction method is set to PCR, the minimum value for this parameter is 0.8 seconds. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No 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 Valid range Default value Integer (milliseconds) 500 to 2000 1000

References
Internal name GSM parameter GSM technical specification T7 (ITU) T7 ITU (blue book) Q.703 pg 72

68P02901W23-S

7-189 Nov 2009

ss7_l3_t1

Chapter 7: Timer parameters

ss7_l3_t1

Description
The ss7_l3_t1 timer specifies the delay to avoid mis-sequencing on changeover timer. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No None

Syntax
Change command string
chg_element ss7_l3_t1 <value> <location>

Display command string

disp_element ss7_l3_t1 <location>

Values
Value type Valid range Default value Integer (milliseconds in 5 millisecond increments) 500 to 1200 850

References
GSM parameter GSM technical specification T1_TIMER ITU (blue book) Q.704 pgs 196-197 ITU (blue book) Q.707 pg 349: supervision timers T1, T2 (SLT_T1, SLT_T2)

7-190

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

ss7_l3_t2

Description
The ss7_l3_t2 timer specifies the wait time for changeover acknowledgment timer. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No 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 Valid range Default value Integer (milliseconds in 5 millisecond increments) 700 to 2000 1400

References
Internal name GSM name GSM technical specification T2_TIMER T2 ITU (blue book) Q.704 pgs 196-197 ITU (blue book) Q.707 pg 349: supervision timers T1, T2 (SLT_T1, SLT_T2)

68P02901W23-S

7-191 Nov 2009

ss7_l3_t4

Chapter 7: Timer parameters

ss7_l3_t4

Description
The ss7_l3_t4 timer specifies the waiting for changeback acknowledgment (first attempt) timer. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No None

Syntax
Change command string
chg_element ss7_l3_t4 <value> <location>

Display command string

disp_element ss7_l3_t4 <location>

Values
Value type Valid range Default value Integer (milliseconds in 5 millisecond increments) 500 to 1200 850

References
Internal name GSM name GSM technical specification T4_TIMER T4 ITU (blue book) Q.704 pgs 196-197 ITU (blue book) Q.707 pg 349: supervision timers T1, T2 (SLT_T1, SLT_T2)

7-192

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

ss7_l3_t5

Description
The ss7_l3_t5 timer specifies the waiting for changeback acknowledgment (second attempt) timer. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No None

Syntax
Change command string
chg_element ss7_l3_t5 <value> <location>

Display command string

disp_element ss7_l3_t5 <location>

Values
Value type Valid range Default value Integer (milliseconds in 5 millisecond increment) 500 to 1200 850

References
Internal name GSM parameter GSM technical specification T5_TIMER T5 ITU (blue book) Q.704 pgs 196-197 ITU (blue book) Q.707 pg 349: supervision timers T1, T2 (SLT_T1, SLT_T2)

68P02901W23-S

7-193 Nov 2009

ss7_l3_t12

Chapter 7: Timer parameters

ss7_l3_t12

Description
The ss7_l3_t12 timer specifies the uninhibit acknowledgment timer. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No None

Syntax
Change command string
chg_element ss7_l3_t12 <value> <location>

Display command string

disp_element ss7_l3_t12 <location>

Values
Value type Valid range Default value Integer (milliseconds in 5 millisecond increments) 800 to 1500 1150

References
Internal name GSM parameter GSM technical specification T12_TIMER (ITU) T12 ITU (blue book) Q.704 pgs 196-197 ITU (blue book) Q.707 pg 349: supervision timers T1, T2 (SLT_T1, SLT_T2)

7-194

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

ss7_l3_t13

Description
The ss7_l3_t13 timer specifies the force uninhibit timer. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No None

Syntax
Change command string
chg_element ss7_l3_t13 <value> <location>

Display command string

disp_element ss7_l3_t13 <location>

Values
Value type Valid range Default value Integer (milliseconds in 5 millisecond increments) 800 to 1500 1150

References
Internal name GSM parameter GSM technical specification T13_timer (ITU) T13 ITU (blue book) Q.704 pgs 196-197 ITU (blue book) Q.707 pg 349: supervision timers T1, T2 (SLT_T1, SLT_T2)

68P02901W23-S

7-195 Nov 2009

ss7_l3_t14

Chapter 7: Timer parameters

ss7_l3_t14

Description
The ss7_l3_t14 timer sets the inhibition acknowledgment timer. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No None

Syntax
Change command string
chg_element ss7_l3_t14 <value> <location>

Display command string

disp_element ss7_l3_t14 <location>

Values
Value type Valid range Default value Integer (milliseconds in 5 millisecond increments) 2000 to 3000 2500

References
Internal name GSM name GSM technical specification T14_TIMER (ITU) T14 ITU (blue book) Q.704 pgs 196-197 ITU (blue book) Q.707 pg 349: supervision timers T1, T2 (SLT_T1, SLT_T2)

7-196

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

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 Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No None

Syntax
Change command string
chg_element ss7_l3_t17 <value> <location>

Display command string

disp_element ss7_l3_t17 <location>

Values
Value type Valid range Default value Integer (milliseconds in 5 millisecond increments) 800 to 1500 1150

References
Internal name GSM parameter GSM technical specification T17_TIMER T17 ITU (blue book) Q.704 pgs 196-197 ITU (blue book) Q.707 pg 349: supervision timers T1, T2 (SLT_T1, SLT_T2)

68P02901W23-S

7-197 Nov 2009

ss7_l3_t22

Chapter 7: Timer parameters

ss7_l3_t22

Description
The ss7_l3_t22 timer specifies the local inhibit test timer. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No 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 Valid range Integer (milliseconds in 5 millisecond increments) The range of values is dependent upon the value of the ss7_mode parameter. 180000 to 360000 90000 to 120000 Default value If ss7_mode = 0 (ITU) If ss7_mode = 1 (ANSI)

The default value is dependent upon the value of the ss7_mode parameter. 270000 90000 If ss7_mode = 0 (ITU) If ss7_mode = 1 (ANSI)

NOTE
The default value is set when the ss7_mode parameter value is changed.

7-198

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

References

References
Internal name GSM name GSM technical specification T22_TIMER T22 ITU (blue book) Q.704 pgs 196-197 ITU (blue book) Q.707 pg 349: supervision timers T1, T2 (SLT_T1, SLT_T2)

68P02901W23-S

7-199 Nov 2009

ss7_l3_t23

Chapter 7: Timer parameters

ss7_l3_t23

Description
The ss7_l3_t23 timer specifies the remote inhibit test timer. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No ss7_mode

Syntax
Change command string
chg_element ss7_l3_t23 <value> <location>

Display command string

disp_element ss7_l3_t23 <location>

The default value is dependent upon the value of the ss7_mode parameter. 270000 90000 If ss7_mode = 0 (ITU) If ss7_mode = 1 (ANSI)

NOTE
The default value is set when the ss7_mode parameter value is changed.

7-200

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

References

References
Internal name GSM parameter GSM technical specification T23_TIMER T23 ITU (blue book) Q.704 pgs 196 -197 ITU (blue book) Q.707 pg 349: supervision timers T1, T2 (SLT_T1, SLT_T2)

68P02901W23-S

7-201 Nov 2009

ss7_slt_t1

Chapter 7: Timer parameters

ss7_slt_t1

Description
The ss7_slt_t1 parameter specifies the supervision timer for signaling link test acknowledgment. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No None

Syntax
Change command string
chg_element ss7_slt_t1 <value> <location>

Display command string

disp_element ss7_slt_t1 <location>

Values
Value type Valid range Default value Integer (milliseconds in 5 millisecond increments) 4000 to 12000 8000

References
Internal name GSM name GSM technical specification SLT_T1_TIMER T1 ITU (blue book) Q.704 pgs 196-197 ITU (blue book) Q.707 pg 349: supervision timers T1, T2 (SLT_T1, SLT_T2)

7-202

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

start_ack

Description
The start_ack parameter specifies the BSC wait time for the starting acknowledgment of a single registered BTS during configuration time. The value selected must give the CRM enough time to answer a request from the CLM when the system is coming out of reset. The typical value for this timer is 1000 milliseconds. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) No No None

Syntax
Change command string
chg_element start_ack <value> <location>

Display command string

disp_element start_ack <location>

Values
Value type Valid range Default value Integer (milliseconds) 0 to 1000000 30000

References
Internal name CLM_MTJ1 This is a Motorola defined timer.

68P02901W23-S

7-203 Nov 2009

static_sync_timer

Chapter 7: Timer parameters

static_sync_timer

Description
This static_sync_timer specifies the maximum amount of time that is allowed for the channel coder to transition from initial time alignment to static time alignment. Static time alignment is necessary before the channel coder can process data. The BSS allows the values of the Initial Sync Timer, Downlink Sync Timer, Uplink Sync Timer and Static Sync Timer to be modified so that one site reset is required for all to be changed. The GPRS feature restricts the modifications of the GPRS Alarm Increment/Decrement Time Period, GCI error increment, GCI error generation threshold, GCI error clear threshold and Static Sync Timer parameters. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No The GPRS feature must be unrestricted.

NOTE
BSS software processes using this parameter are not notified when this parameter is changed.

Syntax
Change command string
chg_element static_sync_timer <value> <location>

Display command string

disp_element static_sync_timer <location>

7-204

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Values

Values
Value type Valid range Integer (milliseconds) 1 to 65535 0 1 ... 12000 ... 65535 0 seconds 0.001 second ... 12 seconds ... 65.535 seconds 0 milliseconds 1 millisecond 12000 milliseconds 65535 milliseconds

Default value

12000

68P02901W23-S

7-205 Nov 2009

stop_dri_tx_time

Chapter 7: Timer parameters

stop_dri_tx_time

Description
The stop_dri_tx_time parameter adjusts the period of time between the cell going Out of Service (OOS) and the radios stop transmitting. When the Stop Tx when Cell OOS feature is enabled, the operator can adjust the period of time between the cell going OOS, and the radios to stop transmitting by changing the value of stop_dri_tx_time. Changes to this parameter can be made at any time but do not take effect if changed between the CELL going OOS and the radios stop transmitting. Type Supported by OMC-R GUI Cell numbers required Dependencies A (no operator actions) Yes Yes The Stop Tx when Cell OOS feature must be unrestricted and enabled (stop_dri_tx_enable=1).

Syntax
Change command strings
chg_cell_element stop_dri_tx_time <value> <cell_desc_opt> chg_element stop_dri_tx_time <value> <location> <cell_desc>

Display command strings

disp_element stop_dri_tx_time <location> <cell desc>

Values
Value type Valid range Default value Integer (seconds) 0 to 1800 300

7-206

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

t_stat_info

Description
The t_stat_info timer specifies the interval between Subsystem Status Test (SST) messages to the MSC. This timer is also known as clm_t_stat_info in some Motorola documentation. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator action) Yes No None

Syntax
Change command string
chg_element t_stat_info <value> <location>

Display command string

disp_element t_stat_info <location>

Values
Value type Valid range Default value Integer (milliseconds) 0 to 1000000 900000

References
GSM specification Q.714, Section 5.3.4.2. This is a Motorola defined timer.

68P02901W23-S

7-207 Nov 2009

uplink_sync_timer

Chapter 7: Timer parameters

uplink_sync_timer

Description
The uplink_sync_timer specifies how long a Channel Coder Unit (CCU) waits for the urgent alarm pattern to be received before generating an error indication. The uplink_sync_timer is also the wait time for an uplink frame error (UFE) bit of the downlink transcoding and rate adoption unit (TRAU) frame to remain reset during a call before generating an error indication. The BSS allows the values of the initial_sync_timer, downlink_sync_timer, uplink_sync_timer and static_sync_timer to be modified so that only one site reset is required for all to be changed. The GPRS feature restricts the modifications of the gprs_alarm_time period, gci_error_inc, gci_error_gen_threshold, gci_error_clr_threshold and static sync timer parameters. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes No This parameter is not allowed at a stand-alone BSC or RXCDR. It can be used at a BTS.

Syntax
Change command string
chg_element uplink_sync_timer <value> <location>

NOTE
A site reset occurs when the value of uplink_sync_timer is changed in SYSGEN OFF mode. Resetting the site generates several alarms. However, the system blocks these alarms.

7-208

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Values

Display command string

disp_element uplink_sync_timer <location> This parameter can be used at a BTS.

Values
Value type Valid range Default value Integer (milliseconds) 1000 to 3000 1000

68P02901W23-S

7-209 Nov 2009

valid_candidate_period

Chapter 7: 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. The copy_cell command copies this timer. Type Supported by OMC-R GUI Cell description required Dependencies A (no operator actions) Yes Yes The ho_exist_congest parameter must be enabled.

Syntax
Change command strings
chg_element valid_candidate_period <value> <location> <cell_desc> chg_cell_element valid_candidate_period <value> <cell_desc_opt>

Display command string

disp_element valid_candidate_period <location> <cell_desc>

Values
Value type Valid range Default value Integer (milliseconds) 1 to 1000000 4000

7-210

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

zone_pingpong_disable_win

Description
The zone_pingpong_disable_win parameter is an interzone timer that sets the time window in which ping-pong handovers between zones are not allowed. This parameter can be changed when the operator is in RAM or Sysgen mode. This parameter can only be modified at the BSC. Type Supported by OMC-R GUI Cell description required Dependencies A (No operator actions required) Yes No 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 Valid range Default value Integer (1 second steps) 0 to 255 30

68P02901W23-S

7-211 Nov 2009

zone_pingpong_enable_win

Chapter 7: Timer parameters

zone_pingpong_enable_win

Description
The zone_pingpong_enable_win parameter is an interzone timer that sets the time window in which ping-pong handovers between zones are continuously allowed as regulated by the zone_pingpong_count parameter (see zone_pingpong_count on page 6-916). This parameter can be changed when the operator is in RAM or Sysgen mode. This parameter can only be modified at the BSC. Type Supported by OMC-R GUI Cell description required Dependencies A (No operator actions required) Yes No 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 Valid range Default value Integer (1 second steps) 0 to 255 30

7-212

68P02901W23-S Nov 2009

Chapter

8
Device/Function parameters

Device and function database parameters are BSS parameters associated with equipped devices and functions, that can be modified. The modify_value command is used to modify parameters on devices and functions that have been equipped using the equip command. For detailed information on the modify_value command, refer to the command description under modify_value on page 3-456. In this chapter the device/function database parameters are described in alphabetical order using the presentation layout as detailed in the Device and function database parameters presentation section at the start of this chapter.

68P02901W23-S Nov 2009

8-1

Device and function database parameters presentation

Chapter 8: Device/Function parameters

Device and function database parameters presentation

The layout of the device/function parameter reference information is explained in the following section.

Parameter reference
The actual parameter reference appears at the head of the page containing the reference information. It also is reproduced in the contents and the index of this manual.

Description
This section of the reference presentation describes the parameter function in detail. Dependencies on other database elements and system functions are included in the parameter description.

Device/Function
This subsection indicates the devices or functions from the following list, for which the parameter of the modify_value command may be modified: AXCDR BSP BSS BTP CAB CAGE CBL COMB DHP DRI DYNET EAS GBL GCLK LCF Associated XCDR Base Site control Processor Base Station Subsystem Base Transceiver Processor Cabinet Cage Cell Broadcast Link COMBiner Digital Host Processor Digital Radio Interface Dynamic Network External Alarm System Gb Link Generic CLocK board Link Control Function

8-2

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Description

MMS MSI PCU RSL RTF SITE XBL

Multiple serial interface link Multiple Serial Interface board Packet Control Unit Radio Signaling Link Receive Transmit Function BSC or BTS Transcoder to BSS Link

Type
This subsection indicates the classification of the database parameter as Type A or Type B where: Type A parameters do not require additional operator actions when the parameter value is changed. Type B parameters require additional operator actions when the parameter value is changed. The specific action required is described in the Operator actions field.

OMC-R GUI support

This subsection indicates whether the database element value may be changed through the OMC-R GUI (Graphics User Interface). If the OMC-R GUI does not support a value, it can be changed by performing a remote login (rlogin) from the OMC-R, or at the site, using a PC connected to the master GPROC.

Cell description required

This subsection indicates whether the database parameter affects specific cells and requires the GSM cell numbers to be included in the command syntax when the parameter is displayed or changed.

Dependencies
This subsection describes any database internal or external dependencies which may affect value assignments of the database parameter. Consider these dependencies when changes are made to the parameter.

Operator actions
This subsection lists specific actions required when changing Type B parameters, and includes any precautions that are appropriate.

Use of all location option

This subsection indicates whether the all location option of the modify_value command is or is not permitted when changing the parameter value.

68P02901W23-S

8-3 Nov 2009

Syntax

Chapter 8: Device/Function parameters

Syntax
This section provides the syntax of the change and display command strings for the particular device/function database parameter.

Change command strings

This subsection contains the: Modify_value command syntax used to change values to a parameter is provided to assist the operator in entering the command. The command name, the parameter name, indices (if required), the new element value, and the location affected are included in the command syntax. equip command syntax which is included where an element is initially assigned using the equip command and modified using the modify_value command. The individual equip command prompts are listed in the equip command description equip on page 3-403.

Display command strings

This subsection contains the disp_equipment command syntax used to display the database element value. The command name, the parameter name, indices (if required), and the location are included in the command syntax.

Values
This section lists the value types and valid ranges for the database values for the particular parameter.

Value type
This subsection indicates whether the parameter database value is an integer, Boolean, text, or alphanumeric and, if required, what the value represents.

Value range
This subsection indicates the range of the parameter database value. Values for some elements are expressed as steps representing incremental values.

8-4

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Values

Default values
This subsection indicates the default database value if available for the parameter. Some parameters are assigned default values when the database is initially loaded. This default value may only be displayed by using the disp_equipment command before the database parameter is changed for the first time. The default value may be changed by using the appropriate modify_value command. If an invalid value is entered when using the modify_value command, the command is abandoned and an error message presented. The original value of the parameter remains unchanged.

68P02901W23-S

8-5 Nov 2009

antenna_select

Chapter 8: Device/Function parameters

antenna_select

Description
The antenna_select parameter specifies the first antenna attached to a transceiver. Device/Function Type Supported by OMC-R GUI Cell description required Dependencies Operator actions Use of all locations option DRI B (operator actions required) Yes No The transceiver must be locked when modifying this parameter. Lock the transceiver before modifying this parameter. 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 Valid range Default value Integer 1 to 6 None

8-6

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Values

NOTE
Set this parameter to a value of 2 for a secondary frequency in a multiband Horizonmacro site. For a DRI equipped to a Horizon II mini cabinet, antenna_select takes a value of either 1 or 2.

68P02901W23-S

8-7 Nov 2009

ber_oos_mon_period

Chapter 8: Device/Function parameters

ber_oos_mon_period

Description
The ber_oos_mon_period parameter specifies the length of time that an in-service MMS must be above a specified Bit Error Rate (BER) before it is taken Out Of Service (OOS). The default value for this parameter is assigned when MMSs are equipped automatically on the equipping of an MSI. This parameter is available for MMSs equipped from GPRS PMC MSIs. Device/Function Type Supported by OMC-R GUI Cell description required Dependencies Use of all locations option MMS A (no operator actions) Yes No None 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>

NOTE
An additional check is performed while displaying an MMS. If the MSI type of the MMS is RF_UNIT, ber_oos_mon_period is not displayed.

8-8

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Values

Values
Value type Valid range Default value Integer (seconds) 1 to 60 8

68P02901W23-S

8-9 Nov 2009

ber_restore_mon_period

Chapter 8: Device/Function parameters

ber_restore_mon_period

Description
The ber_restore_mon_period parameter specifies the length of time that an out-of-service MMS must be at a 0.000001 Bit Error Rate (BER) before it is put in service. The default value for this parameter is assigned when MMSs are equipped automatically on the equipping of an MSI. This parameter is available for MMSs equipped from GPRS PMC MSIs. Device/Function Type Supported by OMC-R GUI Cell description required Dependencies Use of all locations option MMS A (no operator actions) Yes No None 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>

NOTE
An additional check is performed while displaying an MMS. If the MSI type of the MMS is RF_UNIT, ber_restore_mon_period is not displayed.

8-10

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Values

Values
Value type Valid range Default value Integer (100 milliseconds) 0 to 18000 600

68P02901W23-S

8-11 Nov 2009

bsc_cbc_operator

Chapter 8: Device/Function parameters

bsc_cbc_operator

Description
The bsc_cbc_operator parameter specifies the BSC CBC operator. Device/Function Type Supported by OMC-R GUI Cell description required Dependencies CBL A (no operator actions) Yes No 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 Valid range Default value Text Up to 20 alphanumeric characters None

NOTE
Enter the alphanumeric characters for value within quotation marks.

8-12

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

cabinet_type

Description
The cabinet_type parameter specifies the cabinet type within a BSC/RXCDR/BTS site. Table 8-1 lists the cabinet types and associated groups.

Table 8-1

Cabinets/Groups
Group GPROC MCU TCU MICRO not supported Horizonmacro master Horizonmacro extension Horizoncompact BTS Horizonmicro2 BTS Horizoncompact2 BTS Horizon II macro Horizon II macro extension Horizon II mini Horizon II mini extension {26481} Horizon II micro {26481} Horizon II micro extension

Cabinets 0 to 9 10 to 11 12 to 13 14 to 16 17 18 19 20 22 23 24 25 26 27 28 29

NOTE
Cabinet groups 24 and 25 are capable of supporting dual band frequencies in a single cabinet.

68P02901W23-S

8-13 Nov 2009

Description

Chapter 8: Device/Function parameters

Device/Function Type Supported by OMC-R GUI Cell description required Dependencies No

CAB A (no operator actions) Yes

When changing the cabinet type, the new cabinet type must be in the same cabinet group as the old cabinet type. The cabinet type may not be modified from Horizonmicro (M-Cellarena), Horizoncompact (M-Cellarenamacro), to M-Cellcity or M-Cellmicro if frequency hopping is enabled at the site. The system rejects an attempt to alter the cabinet type from M-Cellcity, Horizonmicro (M-Cellarena) or Horizoncompact (M-Cellarenamacro) to M-Cellmicro if any MSIs of type niu_hdsl are equipped at the M-Cellcity, Horizonmicro (M-Cellarena) or Horizoncompact (M-Cellarenamacro) sites. The cabinet type may not be modified to M-Cell2 if there are any MSI devices equipped in slots other than 0, or if there are any MSI devices with a first device ID greater than 1. The system rejects the modify_value cabinet_type command if the change is from TCU_6 to TCU_2, and the cabinet has at least one DRI equipped through the FMUX. A DRI that uses an FMUX as the TCU connection type cannot be equipped to a TCU_2 cabinet. If a modify_value command from M-Cellcity, Horizonmicro (M-Cellarena) or Horizoncompact (M-Cellarenamacro) to M-Cellmicro is accepted, all the hdsl parameters initially set by the chg_element command are set to their defaults. If a cabinet type of Horizonmicro (M-Cellarena) or Horizoncompact (M-Cellarenamacro) is entered during CAB device equipage, then the CAB ID entered must be 0 if CAB device 0 does not yet exist. The bts_type per SITE element is set to 1 upon equipage of a slave Horizonmicro or Horizoncompact CAB device. The valid CAB ID range at a Horizonmicro BTS site is 0 to 2. When modifying this parameter ensure that the cabinet_type is compatible with the hardware board type. A mismatch during a hard reset causes the BTS to remain OOS. The modify_value cabinet_type command is rejected if an attempt is made to modify a TCU_2 cabinet type, with frequency type other than EGSM900 and/or DCS1800, to a (Horizon II) extension cabinet. The Horizon II mini extension cabinet type is allowed to be mixed with M-Cell6, Horizonmacro, Horizonmacro2, and Horizon II mini cabinets at a BTS site. The Horizon II mini master cabinet can control TCU-6, Horizonmacro extension, Horizonmacro2 extension, and Horizon II mini extension cabinets.

8-14

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Syntax

Syntax
Change command strings
equip <location> cab unequip <location> cab <id1> <id2> <id3> modify_value <location> cabinet_type <value> cab <id1> <id2> <id3>

NOTE
Unequip of an HorizonII mini extension cabinet is rejected if the cabinet is not locked or if it has one or more dependent devices. The CAB device cabinet_type can be modified to other cabinet types as specified in Table 8-2 (restrictions on these transitions are not shown). All other transitions involving Horizon II mini master and extension cabinets are disallowed.

Table 8-2

Permitted CAB modifications

New cabinet type horizonmacro2 horizon2mini horizonmacro2_ext horizon2mini_ext

Old cabinet type horizon2mini horizonmacro2 horizon2mini_ext horizonmacro_ext, tcu_6, tcu_2, horizonmacro2_ext

Display command string

disp_equipment <location> cab <id1> <id2> <id3>

NOTE
Information for only one PSU is displayed for Horizon II mini master and Horizon II mini extension cabinets.

68P02901W23-S

8-15 Nov 2009

Values

Chapter 8: Device/Function parameters

Values
Value type Valid range Integer or alphanumeric (entered as an alphanumeric string, without any delimiters) 0 to 29 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 22 23 24 25 26 27 28 29 Default value None bts4d_48v bts4d_27v bssc_48v bssc_27v bts_dab bssc_dab excell_4 excell_6 topcell bts_5 m_cell_2 m_cell_6 tcu_2 tcu_6 m_cell_micro m_cellcity m_cellarena not supported horizonmacro horizonmacro_ext m_cellarena_macro horizonmicro2 horizoncompact2 horizonmacro2 horizonmacro2_ext horizon2mini horizon2mini_ext {26481} horizon2micro {26481} horizon2micro_ext

8-16

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

cavity

Description
The cavity parameter specifies the cavity number within the COMB device that is used by the DRI. Device/Function Type Supported by OMC-R GUI Cell description required Dependencies DRI A (no operator actions) No No If the combining_type is 0, the combiner_id and cavity values are considered invalid and no modifications are allowed. If the combining_type is 1 or 2, the combiner_id and cavity number are required and are prompted. If these values have already been specified, the existing values can be used as defaults. All affected devices must be locked.

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 Valid range Default value Integer 0 to 5 None

68P02901W23-S

8-17 Nov 2009

cbc_operator

Chapter 8: Device/Function parameters

cbc_operator

Description
The cbc_operator parameter specifies the CBC operator. Device/Function Type Supported by OMC-R GUI Cell description required Dependencies Use of all locations option CBL A (no operator actions) No No This parameter only applies to the BSC. 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 Valid range Default value Text Up to 20 alphanumeric characters None

NOTE
Enter the alphanumeric characters for value within quotation marks.

8-18

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

cell_zone

Description
The cell_zone parameter specifies the zone to which an RTF belongs in a concentric cell environment. If the GPRS feature is in use, GPRS carriers must be in the outer zone of a concentric cell. Device/Function Type Supported by OMC-R GUI Cell description required Dependencies RTF A (no operator actions) Yes No The Concentric Cells feature must be enabled and inner_zone_alg must be set to other than 0. Only non-BCCH carriers can be configured in the inner zone. Yes

Use of all locations option

Syntax
Change command strings
modify_value <location> cell_zone <value> rtf <dev_fun_id1> <dev_fun_id2> <dev_fun_id3> equip <location> rtf

NOTE
If the cell_zone value for an RTF is changed in SYSGEN OFF mode, the system displays a warning message. The RTF cycles if the change is made in SYSGEN OFF mode. If the inner_zone_alg is disabled in a cell and a carrier is equipped in the inner zone, or changed to the inner zone, the system displays a warning message.

Display command string

disp_equipment <location> rtf <id1> <id2> <id3>

68P02901W23-S

8-19 Nov 2009

Values

Chapter 8: Device/Function parameters

Values
Value type Valid range Boolean 0 or 1 0 1 Default value 0 Outer zone Inner zone

8-20

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

chan_alloc_priority

Description
The chan_alloc_priority parameter specifies the channel allocation priority of an in-service carrier. The interference band of a channel is still the first criterion in the channel allocation algorithms. A channel from the highest priority carrier matching the requested interference band is allocated to a channel request. Device/Function Type Supported by OMC-R GUI Cell description required Dependencies Use of all locations option RTF A (no operator actions) Yes No None 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 Valid range Integer 0 to 250 0 250 Default value 0 Highest priority Lowest priority

68P02901W23-S

8-21 Nov 2009

cic_block_thresh

Chapter 8: Device/Function parameters

cic_block_thresh

Description
The cic_block_thresh parameter specifies the threshold for blocking Circuit Identity Codes (CICs) according to the availability of idle Aters. This parameter is disabled when set to 245. Device/Function Type Supported by OMC-R GUI Cell description required Dependencies AXCDR A (no operator actions) Yes No This parameter can be modified inside and outside Sysgen mode. The AMR Enhanced Capacity and/or GSM Half Rate feature must be unrestricted. An AXCDR device cannot be in Enhanced Auto-Connect mode if CIC validation is disabled. The eac_mode parameter must be enabled. The cic_block_thresh parameter must be less than the cic_unblock_thresh parameter by at least 10 except when both parameters are 0. Use of all locations option No

Syntax
Change command strings
modify_value 0 cic_block_thresh <value> AXCDR <axcdr_id> equip 0 AXCDR

8-22

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Values

NOTE
After entering the equip AXCDR command, the operator is prompted for following parameters: device ID. CIC validation. EAC mode.

When eac_mode is enabled, the operator is prompted for the following parameters: CIC blocking threshold. CIC unblocking threshold.

Display command string

disp_equipment 0 AXCDR <axcdr_id>

Values
Value type Valid range Default value Integer 0 to 245 0 245 disables this parameter.

68P02901W23-S

8-23 Nov 2009

clkx0

Chapter 8: Device/Function parameters

Chapter 8: Device/Function parameters

combiner_address

Description
The combiner_address parameter specifies the message routing address for the Combiner (COMB). Device/Function Type Supported by OMC-R GUI Cell description required Dependencies Use of all locations option COMB A (no operator actions) No No The address must be unique within a site. All affected devices must be locked. 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 Valid range Default value Integer 0 to 255 None

8-30

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

combiner_id

Description
The combiner_id parameter specifies the identity of the COMB device the DRI uses for combining. Device/Function Type Supported by OMC-R GUI Cell description required Dependencies DRI A (no operator actions) No No If the combining_type is 0, the combiner_id and cavity values are considered invalid and no modifications are allowed. If the combining_type is 1 or 2, the combiner_id and cavity number are required and are prompted. If these values have already been specified, the existing values can be used as defaults. All affected devices must be locked. No

Use of all locations option

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 Valid range Default value Integer 0 to 13 None

68P02901W23-S

8-31 Nov 2009

combining_type

Chapter 8: Device/Function parameters

combining_type

Description
The combining_type parameter specifies what type of combining is associated with each DRI. Device/Function Type Supported by OMC-R GUI Cell description required Dependencies DRI A (no operator actions) No No If the combining_type is 0, the combiner_id and cavity values are considered invalid and no modifications are allowed. If the combining_type is 1 or 2, the combiner_id and cavity number are required and are prompted. If these values have already been specified, the existing values can be used as defaults. All affected devices must be locked. No

Use of all locations option

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>

8-32

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Values

Values
Value type Valid range Integer 0 to 2 0 1 2 Default value 0 None Non-controlling Controlling

68P02901W23-S

8-33 Nov 2009

dri_density

Chapter 8: Device/Function parameters

dri_density

Description
The dri_density parameter specifies the density mode (single or double). Device/Function Type Supported by OMC-R GUI Cell description required Dependencies DRI A (no operator actions) Yes No A number of existing parameters that can be modified under the DRI device are affected by the double density DRI devices. Modifications of tcu_port and antenna_select are propagated to the associated DRI device if the DRI being modified is in double density mode. The parameter combining_type is not valid to be modified for double density DRI devices.

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>

8-34

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Values

Values
Value type Valid range Integer or text 1 or 2, single or double 1 or single 2 or double Default value None single density mode double density mode

68P02901W23-S

8-35 Nov 2009

ext_pdchs

Chapter 8: Device/Function parameters

ext_pdchs

{23311A}

Description
The RTF parameter ext_pdchs indicates the number of extended range PDCHs supported by the RTF. The parameter also indicates if the Extended Range Cell for Data is disabled or enabled. ext_pdchs can be configured both in and out of SYSGEN mode. Device/Function Type Supported by OMC-R GUI Cell description required Dependencies Configuring this element is allowed only if Extended Range Cell for the Data feature is unrestricted (ercgprsOpt = 1). Changing this element is allowed only if gprs_enabled is set to 0 for the cell. Value of ext_pdchs is 0 when Baseband hopping is enabled (hopping_support = 2) for the cell. Value of ext_pdchs is 0 when ASYM feature is enabled (asym_edge_enabled=1) for the site. Value of ext_pdchs is 0 when ext_range_cell is disabled (ext_range_cell = 0) for the cell. Value of ext_pdchs is 0 when pkt_radio_type = NONE for the RTF. Value of ext_pdchs is 0 when the ext_pdchs of any other RTF in this cell > 0. Value of ext_pdchs is always <= ext_timeslots for the RTF. RTF A (no operator actions) Yes No

Use of all locations option No

8-36

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Syntax

Syntax
Change command strings
modify_value <location> ext_pdchs <value> rtf <id1> <id2> [<id3>] equip <location> RTF

Display command string

disp_equipment <location> rtf <id1> <id2> [<id3>]

Values
Value type Valid range Integer 0 to 4 0 1 2 3 4 Default value 0 Extended PDCHs on this RTF are disabled, and extended PDCHs number = 0. Extended PDCHs on this RTF are enabled, and extended PDCHs number = 1. Extended PDCHs on this RTF are enabled, and extended PDCHs number = 2. Extended PDCHs on this RTF are enabled, and extended PDCHs number = 3. Extended PDCHs on this RTF are enabled, and extended PDCHs number = 4.

68P02901W23-S

8-37 Nov 2009

ext_timeslots

Chapter 8: Device/Function parameters

ext_timeslots

Description
The ext_timeslots parameter specifies the number of extended range timeslots for an RTF. Device/Function Type Supported by OMC-R GUI Cell description required Dependencies RTF A (no operator actions) Yes No The number of extended range timeslots can be changed only if the Extended Range Cells feature is unrestricted. The number of extended range timeslots cannot be modified for inner-zone carriers. An RTF having one or more extended range timeslots configured cannot have the cell_zone changed to inner. If the Extended Range Cell feature is enabled, the number of extended range timeslots for the BCCH RTF must support the number of configured BCCH, CCCH, and SDCCH channels. EGPRS PDs are not configured on double density CTU2 Carrier A when the corresponding timeslots on carrier B are extended range timeslots. No

Use of all locations option

NOTE
When an attempt is made to modify ext_timeslots of an RTF, and the requested PDTCHs exceed the GDS or PMC capacity on the PCU, the BSS accepts the request and issues a warning to indicate that there is not enough GDS or PMC resource available.

Syntax
Change command strings
modify_value 0 ext_timeslots <value> rtf <id1> <id2> [<id3>] equip <location> rtf

8-38

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Values

NOTE
The system displays a warning message whenever the value for the ext_timeslots parameter is changed. The RTF cycles when the ext_timeslots value is modified in SYSGEN OFF mode.

Display command string

disp_equipment <location> rtf <id1> <id2> [<id3>]

Values
Value type Valid range Default value Integer 0 to 4 0

68P02901W23-S

8-39 Nov 2009

fm_cell_type

Chapter 8: Device/Function parameters

fm_cell_type

Description
The fm_cell_type parameter specifies the type of cell structure supported at the BTS in which a specific DRI is equipped. Device/Function Type Supported by OMC-R GUI Cell description required Dependencies Operator actions Use of all locations option DRI B (operator actions required) Yes No Setting of this parameter depends on the setting of diversity_flag. See the table of values below. Lock the DRI/RCU before modifying this parameter. 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>

8-40

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Values

Values
Value type Valid range diversity_flag 0 0 0 1 1 {27236} 2 2 Default value None Integer 0 to 4 (depends on diversity_flag) as follows: fm_cell_type 0 1 2 3 4 3 4 Result Non-diversity (RCUs only) Use branch 1 of a DRCU in a non-diversity mode Use branch 2 of a DRCU in a non-diversity mode Shared diversity Full diversity for 2 branch. Full diversity for 4 branch. Full diversity for 4 branch.

68P02901W23-S

8-41 Nov 2009

frequency_type

Chapter 8: Device/Function parameters

frequency_type

Description
The frequency_type parameter specifies the frequencies allowed for a cabinet. Device/Function Type Supported by OMC-R GUI Cell description required Dependencies CAB A (but see Operator actions below) Yes No If any of the frequency types specified are not valid at the BSS, the system rejects the modify_value command. Valid frequency types at a BSS can be modified or displayed by the freq_types_allowed command. Frequency_types can be added and deleted in SYSGEN ON mode. Frequencies can be added but not deleted in SYSGEN OFF mode.

ias_connected

Description
The ias_connected parameter enables or disables internal alarms system (IAS). Device/Function Type Supported by OMC-R GUI Cell description required Dependencies Use of all locations option CAGE A (no operator actions) Yes No None 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 Valid range Text yes or no yes no Default value None Enabled Disabled

8-50

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

int_antenna

Description
The int_antenna parameter specifies whether the cabinet contains an internal integrated antenna. Device/Function Type Supported by OMC-R GUI Cell description required Dependencies Use of all locations option CAB A (no operator actions) Yes No This parameter is only allowed for M-Cellcity M-Cellarena, and Horizonmicro cabinets. 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 Valid range Text yes or no yes no Default value None Internal antenna is present and should be used. Internal antenna is not present.

68P02901W23-S

8-51 Nov 2009

int_hdsl_modem

Chapter 8: Device/Function parameters

int_hdsl_modem

Description
The int_hdsl_modem parameter indicates whether an internal HDSL modem is present in the cabinet. Device/Function Type Supported by OMC-R GUI Cell description required Dependencies Use of all locations option CAB A (no operator actions) Yes No This parameter is only allowed for M-Cellcity, M-Cellarena, Horizonmicro and Horizoncompact cabinets. 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

Chapter 8: Device/Function parameters

Values
Value type Valid range Default value Integer (milliseconds) 1400 to 5000 (in 50 millisecond increments) 2500

8-58

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

max_cbls

Description
The max_cbls parameter specifies the maximum number of CBLs that an LCF supports. The all location option of the modify_value command is not permitted when changing this parameter. Device/Function Type Supported by OMC-R GUI Cell description required Dependencies Use of all locations option LCF A (no operator actions) No No None 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 Valid range Default value Boolean 0 or 1 None

68P02901W23-S

8-59 Nov 2009

max_dris

Chapter 8: Device/Function parameters

max_dris

Description
This max_dris parameter specifies the maximum number of DRIs supported by the specified GPROC device or function (BTP or DHP). The new value is not effective until the DRI is brought back into service. DRIs already in service are not affected while they are still in service. A value of 0 may not be specified for this parameter if the BTS type is 0. DRIs can be reassigned to other GPROCs within a cage, to bring the number of DRIs below the modified threshold. There is no automatic redistribution of DRIs from the specified GPROC, should the modified threshold fall below the number of DRIs already assigned. However, if a DRI assigned to the GPROC is taken Out Of Service (OOS), it cannot be brought back into service until the number of DRIs assigned to the GPROC is less than the value of max_dris. If the new threshold is greater than the number of DRIs already assigned to the GPROC, the value is immediately used.

NOTE
max_dris cannot be modified for a BTP equipped to an M-Cell site (MCU).

Device/Function Type Supported by OMC-R GUI Cell description required Dependencies Use of all locations option

BTP , DHP B (operator actions required) Yes No None No

8-60

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Syntax

Syntax
Add/Change command strings
modify_value <location> max_dris <value> btp <dev_fun_id1> <dev_fun_id2> <dev_fun_id3> 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 Valid range Integer 0 to 6 for BTP 1 to 6 for DHP Default value None

68P02901W23-S

8-61 Nov 2009

max_gsls

Chapter 8: Device/Function parameters

max_gsls

Description
The max_gsls parameter specifies the maximum number of GSLs that can be configured on the LCF. Device/Function Type Supported by OMC-R GUI Cell description required Dependencies LCF A (no operator actions) No No This parameter can be used only if the GPRS feature is unrestricted. The sum of all max_gsls specified by the equipped LCFs must be greater than or equal to the total number of GSLs equipped. The value for max_gsls must not exceed the available LCF HDLC channel capacity.

Syntax
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 Valid range Default value Integer 0 to 12 0

8-62

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

max_mtls

Description
The max_mtls parameter specifies the maximum number of MTLs supported by a BSP or LCF. Set this parameter to 1 for all BSPs on a bsc_type 0, non-RXCDR system. Set this parameter to 1 for at least one LCF on a BSC site where the BSC type is not zero. Set this parameter to 2 for GPROC-2 boards. When the value is set to 2, the system displays a warning message and accepts the command. Device/Function Type Supported by OMC-R GUI Cell description required Dependencies Use of all locations option BSP, LCF B (no operator actions) Yes No Change the security level to 2 to modify this parameter. 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-S

8-63 Nov 2009

Values

Chapter 8: Device/Function parameters

Values
Value type Valid range Default value Integer 0 to 2 None

8-64

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

mms_priority

Description
The mms_priority parameter sets the priority rating for an MMS. It determines its possible use as a reference source to which the GCLK may phase lock. The higher the priority value, the more likely the MMS is used as a reference source to which the GCLK device frequently locks. If the priority ratings for all MMs are set 0, the GCLK is placed in the set frequency mode. In a GPRS system, a non-zero value for mms_priority is not permitted for a PCU MMS or an MMS which is part of a GDS. Device/Function Type Supported by OMC-R GUI Cell description required Dependencies Use of all locations option MMS A (no operator actions) Yes No None 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 Valid range Integer 0 to 255 0 1 255 Default value None MMS is not used as a clock extraction source. Lowest priority Highest priority

68P02901W23-S

8-65 Nov 2009

msc_mms_id

Chapter 8: Device/Function parameters

msc_mms_id

Description
The MSC MMS specifies the E1 link to be used to route data for the transcoding circuits from a GDP towards the MSC. The MSC MMS consists of two identifiers: msc_msi_id and msc_mms_id. The msc_msi_id parameter is the MSI identifier of a GDP whose MMS is available for routing the transcoding circuits of a secondary GDP towards the MSC. The msc_mms_id parameter is always zero because MSIs are not used to provide MSC MMSs. Device/Function Type Supported by OMC-R GUI Cell description required Dependencies Use of all locations option MSI A (no operator actions) Yes No This parameter may be modified only when the MSI type is GDP . 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 Valid range Default value Integer 0 0

8-66

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

msi_type

Description
The msi_type parameter specifies a database value for a single equipped device or function at a site for all equipped devices or functions of the type specified in the command. The msi_type parameter also specifies modification between transcoder (XCDR) boards and Generic Digital Processor (GDP) boards and GDP Version 2 (GDP2) and Multiple Serial Interface (MSI) boards and secondary GDP boards. Device/Function Type Supported by OMC-R GUI Cell description required Dependencies MSI B (operator actions required) Yes No The MSI type cannot be changed from GDP to XCDR when an enhanced full rate (EFR) or GDP control is enabled. The MSI type cannot be modified for a PICP MSI. The MSI type cannot be changed from GDP or GDP2 to XCDR when the trans_capability is Enhanced or GDP_2E1. Operator actions Use of all locations option Change to security level 2 to change this parameter. 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>]

68P02901W23-S

8-67 Nov 2009

Values

Chapter 8: Device/Function parameters

Values
Value type Valid range Integer 0 1 2 3 7 8 9 12 14 20 21 Default value None (text) (msi) (xcdr) (gdp) (niu) (msi_ext_hdsl) (niu_hdsl) (niu_ext_hdsl) (RF_unit) (E1_pmc) (gdp2) (H2sc_niu2)

8-68

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

n391

Description
The n391 parameter specifies the value for the frame relay default full status polling counter. Device/Function Type Supported by OMC-R GUI Cell description required Dependencies GBL A (no operator actions) Yes No The GPRS feature must be unrestricted.

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 Valid range Default value Integer (number of polling cycles) 1 to 255 6

68P02901W23-S

8-69 Nov 2009

n392

Chapter 8: Device/Function parameters

n392

Description
The n392 parameter specifies the frame relay default value for error threshold counter. Device/Function Type Supported by OMC-R GUI Cell description required Dependencies GBL A (no operator actions) Yes No The GPRS feature must be unrestricted. This parameter must be less than or equal to the value of n393.

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 Valid range Default value Integer (number of errors) 1 to 10 3

8-70

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

n393

Description
The n393 parameter specifies the frame relay default value for monitored events counter. Device/Function Type Supported by OMC-R GUI Cell description required Dependencies GBL A (no operator actions) Yes No The GPRS feature must be unrestricted. The value of this parameter must be greater than or equal to the value of n392.

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 Valid range Default value Integer (number of events) 1 to 10 4

68P02901W23-S

8-71 Nov 2009

nbit

Chapter 8: Device/Function parameters

nbit

Description
The nbit parameter enables and disables the second remote alarm bit (nbit). The default value for this parameter is automatically assigned when the MSI is equipped. This parameter is available for MMSs equipped from GPRS PMC MSIs. Device/Function Type Supported by OMC-R GUI Cell description required Dependencies Operator actions Use of all locations option MMS B (operator actions required) Yes No The MMS must be locked when modifying this parameter. Lock the MMS before modifying this parameter 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 Valid range Boolean 0 or 1 0 1 Default value 0 Disabled Enabled

8-72

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

ne_id

Description
The ne_id parameter specifies the network identity. Device/Function Type Supported by OMC-R GUI Cell description required Dependencies BSS, RXCDR A (no operator actions) Yes No Changing the ne_id causes all AXCDR or ABSS devices to be cycled, resulting in the loss of all active calls managed by the associated device. No

Use of all locations option

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, enter the following command: disp_equipment 0 bss|rxcdr * To display information about a specific bss/rxcdr, enter the following command: disp_equipment 0 bss|rxcdr <id1>

Values
Value type Valid range Default value Integer 1 to 254 None

68P02901W23-S

8-73 Nov 2009

opto_reporting

Chapter 8: Device/Function parameters

opto_reporting

Description
The opto_reporting parameter allows the operator to modify the reporting status and external alarm string mapping for DRI and EAS optocouplers. When enabling opto_reporting for a DRI, the operator is prompted for the index of the user-defined alarm string for the optocoupler. The range of values is 0 to 33; there is no default value. When enabling opto_reporting for an EAS, the operator is prompted for: The optocoupler whose state is reported. Up to eight values (separated by a comma or a space) may be entered for an EAS at an InCell site; up to 12 values may be entered for a Horizon II mini site; up to 16 values may be entered for an M-Cell site. The values may be entered in any order. The value all may be specified. A range of values may be specified. The user-defined alarm index. The operator must enter one value indicating the index of the alarm string for each optocoupler specified in the previous prompt. The range of values is 0 to 33 and 128; there is no default value. (The text string mpf is equivalent to a value of 128.) When disabling opto_reporting for an EAS, the operator may enter up to eight values (separated by a comma or a space) for an EAS at an InCell site; up to 12 values may be entered for a Horizon II mini site; up to 16 values may be entered for an M-Cell site. The values may be entered in any order. The value all may be specified. A range of values may be specified. Device/Function Type Supported by OMC-R GUI Cell description required Dependencies Operator actions Use of all locations option DRI/EAS B (operator actions required) Yes No None Lock the affected DRI/EAS device before modifying this parameter. Yes

8-74

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Syntax

Syntax
Change command string
modify_value <location> opto_reporting <value> <device> <id1> <id2> <id3>

NOTE
After this command string is entered, additional prompts are displayed, depending on the device specified. The range of optos is limited to 0 to 11 for Horizon II mini (see description for details).

Display command string

disp_equipment <location> <device> <id1> <id2> <id3>

Values
Value type Valid range Boolean off or on off on Default value None Disabled Enabled

68P02901W23-S

8-75 Nov 2009

pkt_radio_type

Chapter 8: Device/Function parameters

pkt_radio_type

Description
The pkt_radio_type parameter specifies the terrestrial resource capability of an RTF. The mutually exclusive options are: none, 16 kbit/s, 32 kbit/s, and 64 kbit/s. This parameter determines if an RTF can carry GPRS/EGPRS or not. The SDCCH allocation favors carriers with low values.

NOTE
A BSS software process is notified whenever the pkt_radio_type element value is changed. An EGPRS-capable RTF can carry EGPRS PDTCHs and can allocate 64 kbit/s terrestrial channels to support the EGPRS coding schemes on the air timeslots. EGPRS RTFs cannot be equipped if there are no Horizonmacro, Horizonmacro2 or MCell family of cabinets at the site. EGPRS RTFs and GPRS RTFs can be equipped in the same cell. For baseband hopping only, the equipage of an RTF with Packet Radio Capability set to 64 K and a hopping system which is shared with any other RTF that is not a 64 K RTF is not supported. Any attempt to configure the system in this manner is rejected. EGPRS RTFs can baseband hop only if the master cabinet at the site is a Horizon II. EGPRS RTFs with associated RSLs cannot be equipped. Sub-equipped EGPRS RTFs cannot be equipped. The pkt_radio_type parameter replaces and enhances the allow_32k_trau parameter which is no longer supported. The use_bcch_for_gprs parameter is not supported for EGPRS. The pkt_radio_type parameter provides the ability to specify whether a BCCH RTF is used for data.

NOTE
When an attempt is made to modify pkt_radio_type and the requested PDTCHs exceed the GDS or PMC capacity on the PCU, the BSS accepts the request and issues a warning to indicate that there is not enough GDS or PMC resource available.

8-76

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Description

Device/Function Type Supported by OMC-R GUI Cell description required Dependencies

RTF A (no operator actions) Yes No An RTF cannot 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 or double density CTU2 carrier A, the Coding Schemes 3 and 4 (CS3/4) feature and the GPRS feature to be unrestricted. An RTF cannot be equipped with 16 kbit/s packet radio type if the GPRS feature is restricted. An RTF cannot be equipped with 32 kbit/s packet radio type if the Coding Schemes 3 and 4 feature is restricted. 64 kbit/s and 32 kbit/s cannot be equipped at a BTS concentration site. A sub-equipped RTF cannot be equipped with 64 kbit/s or 32 kbit/s packet radio type. An RTF cannot be equipped with 64 kbit/s packet radio type if there are no Horizonmacro, Horizonmacro2 or Mcell family of cabinets at the site. An RTF cannot be equipped with a non-zero packet radio type in the inner zone of a cell. An RTF cannot be equipped with 64 kbit/s packet radio type if extended range timeslots are configured. An RTF cannot be equipped with 64 kbit/s packet radio type if there is an associated RSL. An RTF cannot be equipped when sharing a baseband hopping system with a non-EGPRS RTF. EGPRS RTFs can baseband hop only if the master cabinet at the site is a Horizon II. The Improved Timeslot Sharing feature extends the restriction of baseband hopping support on the Horizon II cabinet, for 64 kbit/s RTF hosted by a double 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. There are two DD CTU2 radios on Horizon II cabinet, carrier A and carrier B. Carrier B supports base band hopping when a non-64 kbit/s BBH RTF is mapped to carrier B, provided carrier A is locked or not initialized. The 64 kbit/s is downgraded to 16 kbit/s when carrier A is unlocked and a 64 kbit/s RTF is mapped to the carrier A.

Use of all locations option

68P02901W23-S

8-77 Nov 2009

Syntax

Chapter 8: Device/Function parameters

Syntax
Change command strings

CAUTION
Changing this parameter causes the RTF to go out of service and then back into service. equip <location> rtf modify_value <location> pkt_radio_type <value> rtf <dev_func_id1> <dev_func_id2>

NOTE
Use the equip command to initiate this functionality. Use the modify_value command to change its value. When changing the pkt_radio_type element value a warning is displayed indicating that the RTF is cycled.

Display command string

disp_equipment <location> rtf <dev_func_id1> <dev_func_id2>

Values
Value type Valid range Numeric 0 to 3 0 1 2 3 Default value 0 1 Text None, 16 k, 32 K, and 64 K None 16 K 32 K 64 K No packet radio support 16 kbit/s packet radio (CS1/2) 32 kbit/s packet radio (CS3/4) 64 kbit/s packet radio (EGPRS)

If GPRS is restricted or the RTF is in the inner zone. If GPRS is unrestricted and the RTF is in the outer zone.

8-78

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

pref_rtf_id

Description
The pref_rtf_id specifies a preferred RTF identifier. This allows at least one carrier unit per cabinet that is able to provide GPRS feature service. This parameter must be an RTF unique identifier or null for resetting to no preferred RTF. The value may be entered as a string or an integer. The operator is prompted for each opto that is enabled. Device/Function Type Supported by OMC-R GUI Cell description required Dependencies Use of all locations option DRI A (No operator actions) Yes No This parameter must be an RTF unique identifier or null for resetting to no preferred RTF. 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 Valid range Default value Integer or string 0 to 11, or null None

68P02901W23-S

8-79 Nov 2009

rsl_rate

Chapter 8: Device/Function parameters

rsl_rate

Description
The rsl_rate parameter specifies the signaling and control information rate of the Radio Signal Link (RSL). Device/Function Type Supported by OMC-R GUI Cell description required Dependencies SITE A (no operator actions) Yes No The 16 kbit/s RSL option must be available. The RSL cannot be changed if RSLs are already equipped for this site. The RSL rate cannot be changed for the BSC (site 0). The RSL cannot be changed if the site uses dynamic allocation. No

Use of all locations option

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 Valid range Default value Integer (rate in kbit/s) 1664 None

8-80

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

rtf_ds0_count

Description
The rtf_ds0_count specifies the number of RTF backhaul timeslots allocated for a 64 kbit/s carrier between the BTS and BSC. The VersaTRAU Backhaul feature must be unrestricted to modify this parameter.

NOTE
This parameter is only valid for a 64 kbit/s carrier. 64 K RTFs mapped to Carrier A is downgraded to 16 K when the rtf_ds0_count is modified, if Carrier B is set to BBH (even if hopping is not active).

NOTE
To maintain carrier A EGPRS capability and to minimize the effect of Carrier B, lock Carrier B before modifying the rtf_ds0_count of Carrier A.

Device/Function Type Supported by OMC-R GUI Cell description required Dependencies

RTF A (no operator actions) Yes No The VersaTRAU (VT) Backhaul feature must be unrestricted. The specified RTF must be equipped. The specified RTF must be a 64 kbit/s RTF (pkt_radio_type = 3).

Syntax
Change command strings
modify_value <location> rtf_ds0_count <value> rtf <id1> <id2>

Display command strings

display_equip <location> rtf <id1> <id2>

68P02901W23-S

8-81 Nov 2009

Values

Chapter 8: Device/Function parameters

Values
Value type Valid range Integer 3 to 7 3 to 8 Default value 3 (Number of terrestrial timeslots) If VT is unrestricted and RTF is BCCH carrier. If VT is unrestricted and RTF is non BCCH carrier.

NOTE
While creating or modifying an RTF, when the pkt_radio_type parameter is changed to 3 and versatrau is purchased, the rtf_ds0_count parameter is set to its default value 3. While modifying an RTF, the following message is also displayed on the status bar: Modify the value of rtf_ds0_count attribute If the value is not changed, the default value goes to the BSS and the OMC always sends the rtf_ds0_count to the BSS.

8-82

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

sd_load

Description
The sd_load parameter specifies the maximum number of timeslots to be configured as SDCCHs on an RTF. This parameter determines the number of timeslots on a specified carrier that can be SDCCH. The BSS configures the SDCCHs on the carrier with the highest priority, up to their SDCCH load. Changing the sd_load parameter may cause a channel reconfiguration to make the new values effective. The reconfiguration occurs as channels become idle. Device/Function Type Supported by OMC-R GUI Cell description required Dependencies Use of all locations option RTF A (no operator actions) Yes No None 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>

68P02901W23-S

8-83 Nov 2009

Values

Chapter 8: Device/Function parameters

Values
Value type Valid range Integer 0 0 to 8 2 N/A 0 0 0 0 to 8 <=2 BCCH EGSM extension band carrier when egsm_bcch_sd is 0 (off) BCCH EGSM extension band carrier when egsm_bcch_sd is 1 (on) BCCH extended range cell BCCH inner zone carrier Non-BCCH EGSM extension band carrier Non-BCCH extended range cell Non-BCCH inner zone carrier All other types of non-BCCH carrier When the Sd Increased feature is restricted.

All other types of BCCH carrier: ccch_conf sd_load range for BCCH RTF 0 1 2 4 6 Default value None 0-7 0-7 0-6 0-5 0-4

8-84

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

sd_priority

Description
The sd_priority parameter determines the SDCCH placement priority for an RTF. The BSS configures the SDCCHs on the carriers with the highest priority, up to their SDCCH load (see sd_load on page 8-83 parameter). Changing the sd_load parameter may cause a channel reconfiguration to make the new values effective. The reconfiguration occurs as channels become idle. Device/Function Type Supported by OMC-R GUI Cell description required Dependencies Use of all locations option RTF A (no operator actions) Yes No The sd_priority element cannot be changed for an EGSM, Extended Range Cell, or inner zone carrier. 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 Valid range Integer 0 to 250 0 250 Default value highest priority lowest priority

Non-BCCH default = 0 BCCH default = 0

68P02901W23-S

8-85 Nov 2009

shared_timeslots

Chapter 8: Device/Function parameters

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 Type Supported by OMC GUI Cell description required Dependencies Use of all locations option DYNET A (no operator actions) No No DYNET must be equipped. The site must be a BSC (Location = 0). 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 Valid range Integer 0 to 31 0 to 31 Default value E1 link

0 (no timeslots reserved)

8-86

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

slot

Description
The slot parameter specifies the slot in which the DRI device is fitted. When the slot parameter is modified outside SYSGEN mode, a warning message is displayed that the specified DRI is about to be cycled (locked then unlocked). A prompt is included that enables the operator to choose to continue or abort the change. Device/Function Type Supported by OMC-R GUI Cell description required Dependencies Use of all locations option DRI A (no operator actions) No No None 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 Valid range Default value Integer 7 to 17 (odd values only) None

68P02901W23-S

8-87 Nov 2009

start_ts

Chapter 8: Device/Function parameters

start_ts

Description
The start_ts parameter specifies the first GBL timeslot on the E1 link. Device/Function Type Supported by OMC-R GUI Cell description required Dependencies GBL A (no operator actions) Yes No The GPRS feature must be unrestricted.

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 Valid range Default value Integer (first GBL timeslot) 1 to 31 None

8-88

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

t391

Description
The t391 parameter specifies the frame relay default link integrity verification polling timer.

NOTE
This timer attempts to bring the GBL B-U after t391 plus 1 second. If not, it waits for the expiry of the original t391 * n391 timer value and re-attempts to connect the GBL. If the re-attempt is also unsuccessful, then the GBL notifies PCA of the status.

Device/Function Type Supported by OMC-R GUI Cell description required Dependencies

GBL A (no operator actions) Yes No The GPRS feature must be unrestricted.

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>

Values
Value type Valid range Default value Integer (seconds) 5 to 29 10

68P02901W23-S

8-89 Nov 2009

t392

Chapter 8: Device/Function parameters

t392

Description
The t392 parameter is the frame relay default polling verification timer. Device/Function Type Supported by OMC-R GUI Cell description required Dependencies GBL A (no operator actions) Yes No 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 Valid range Default value Integer (seconds) 6 to 30 15

8-90

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

tcu_port

Description
The tcu_port parameter specifies the port to which a TCU is connected. When the tcu_port parameter is modified outside SYSGEN mode, a warning message is displayed that the specified DRI is about to be cycled (locked then unlocked). A prompt is included that enables the operator to chose to continue or abort the change. The command is rejected if an attempt is made to modify the tcu_port parameter at a Dual band Horizon II macro cabinet such that it contains an invalid Horizon II Dual band DRI setup. Device/Function Type Supported by OMC-R GUI Cell description required Dependencies Use of all locations option DRI A (no operator actions) No No None No

Syntax
Add/Change command strings
modify_value <location> tcu_port <value> dri <id1> <id2> <id3> equip <location> dri

Display command string

disp_equipment <location> dri <id1> <id2> <id3>

Values
Value type Valid range Default value Integer 0 to 5 None

68P02901W23-S

8-91 Nov 2009

Values

Chapter 8: Device/Function parameters

NOTE
If the FOX/FMUX connection parameter is specified as direct when the TCU is equipped, the range for this parameter is limited to 0 or 1. For a DRI equipped to a Horizon II mini cabinet, tcu_port only takes the value of either 0 or 1.

8-92

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

tdOpt

{31400}

Description
The tdOpt parameter indicates whether the TD-SCDMA inter-working feature functionality is restricted or unrestricted in the BSS software. Device/Function Type Supported by OMC-R GUI Cell description required Dependencies BSS A (no operator actions) Yes No If the tdOpt flag indicates that TD-SCDMA inter-working feature is restricted, attempts to add TD-SCDMA neighbor cell and modify/display TD-SCDMA measurement parameters is rejected.

Syntax
Display command string
disp_options [all]

Values
Value type Valid range Boolean 0 1 Default value N/A TD-SCDMA inter-working is restricted. TD-SCDMA inter-working is unrestricted.

68P02901W23-S

8-93 Nov 2009

transcoding_capability

Chapter 8: Device/Function parameters

transcoding_capability

Description
The transcoding_capability parameter specifies the functionality provided by a GDP board. Basic and enhanced functionality are available. Device/Function Type Supported by OMC-R GUI Cell description required Dependencies MSI A (no operator actions) Yes No When equipping the second MMS for GDP_2E1 on upper cage of RXCDR, the parameter ias_connected should be disabled. No

Use of all locations option

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 Valid range Boolean 0 1 Default value 0 Basic GDP function Enhanced GDP function

8-94

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

tru_id

Description
The tru_id parameter specifies up to six TRUs (TopCell Radio Units) in a TopCell site. A value of 0 indicates this site is a non-TopCell site. When the tru_id parameter is modified outside SYSGEN mode, a warning message is displayed that the specified DRI is about to be cycled (locked then unlocked). A prompt is included that enables the operator to chose to continue or abort the change. Device/Function Type Supported by OMC-R GUI Cell description required Dependencies Use of all locations option DRI A (no operator actions) Yes No None 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 Valid range Integer 0 to 6 0 1 to 6 Default value None Non-TopCell unit TopCell ID

68P02901W23-S

8-95 Nov 2009

trx_pwr_red

Chapter 8: Device/Function parameters

trx_pwr_red

Description
The trx_pwr_red parameter represents the max trx power in inner zone when the inner_zone_alg is power based. Device/Function Type Supported by OMC-R GUI Cell description required Dependencies RTF A (no operator actions) Yes No This parameter is used only if the cell_zone parameter is set to 1 (inner zone) and the maximum transmission power is in inner zone when the inner_zone_alg is power based. trx_pwr_red can be modified for an RTF that is equipped in the inner_zone of a cell only. The value of this parameter must be greater than or equal to the value of max_tx_bts if inner_zone_alg is set to 1 (power based use algorithm). The Concentric Cells option must be unrestricted. Yes

Use of all locations option

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]

8-96

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Values

Values
Value type Valid range Default value Integer (1 step = 2 dBm) -1 to 21 for PGSM, EGSM, and DCS1800 0 to 6 for M-Cellmicro sites None

NOTE
Refer to Table 8-3, Table 8-4, Table 8-5, Table 8-6 and Table 8-7 for additional information about the values for this parameter. Table 8-3 lists values for PGSM, EGSM, and PCS 1900 sites.

Table 8-3

Values for PGSM, EGSM and PCS 1900 sites

Value -1 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 Power 45 dBm 43 dBm 41 dBm 39 dBm 37 dBm 35 dBm 33 dBm 31 dBm 29 dBm 27 dBm 25 dBm 23 dBm 21 dBm 19 dBm 17 dBm 15 dBm 13 dBm 11 dBm Continued

68P02901W23-S

8-97 Nov 2009

Values

Chapter 8: Device/Function parameters

Table 8-3

Values for PGSM, EGSM and PCS 1900 sites (Continued)

Value 17 18 19 20 21 Power 9 dBm 7 dBm 5 dBm 3 dBm 1 dBm

NOTE
Value -1 is valid only for BTS sites with an M-CELL2, M-CELL6, HorizonMacro, HorizonMacro2, Horizon2micro or Horizon2mini as controlling cabinet and with frequencies PGSM amd EGSM only. Table 8-4 lists values for DCS 1800 sites.

Table 8-4

Values for DCS 1800 sites

Power 39 dBm 37 dBm 35 dBm 33 dBm 31 dBm 29 dBm 27 dBm 25 dBm 23 dBm 21 dBm 19 dBm 17 dBm 15 dBm 13 dBm 11 dBm 9 dBm 7 dBm Continued

Value 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16

8-98

68P02901W23-S Nov 2009

Technical Description: BSS Command Reference

Values

Table 8-4

Values for DCS 1800 sites (Continued)

Power 5 dBm 3 dBm 1 dBm -1 dBm -3 dBm

Value 17 18 19 20 21

Table 8-5 lists values for PGSM and EGSM M-Cellmicro sites.

Table 8-5

Values for PGSM and EGSM M-Cellmicro sites

Power 34 dBm 32 dBm 30 dBm 28 dBm 26 dBm 24 dBm 22 dBm

Value 0 1 2 3 4 5 6

Table 8-6 lists values for DCS 1800 for M-CELL6, HorizonMacro, HorizonMacro2, Horizon2micro and Horizon2mini sites.

Table 8-6 Values for DCS 1800 for M-CELL6, HorizonMacro, HorizonMacro2, Horizon2micro and Horizon2mini sites
Value -1 0 1 2 3 4 5 6 7 8 9 10 Power 44 dBm 42 dBm 40 dBm 38 dBm 36 dBm 34 dBm 32 dBm 30 dBm 28 dBm 26 dBm 24 dBm 22 dBm Continued

68P02901W23-S

8-99 Nov 2009

Values

Chapter 8: Device/Function parameters

Table 8-6 Values for DCS 1800 for M-CELL6, HorizonMacro, HorizonMacro2, Horizon2micro and Horizon2mini sites (Continued)
Value 11 12 13 14 15 16 17 18 19 20 21 Power 20 dBm 18 dBm 16 dBm 14 dBm 12 dBm 10 dBm 8 dBm 6 dBm 4 dBm 2 dBm 0 dBm

Table 8-7 lists values for DCS 1800 and PCS 1900 M-Cellmicro sites.

Table 8-7

Values for DCS 1800 and PCS 1900 M-Cellmicro sites

Power 30 dBm 28 dBm 26 dBm 24 dBm 22 dBm 20 dBm 18 dBm

Value 0 1 2 3 4 5 6

8-100

68P02901W23-S Nov 2009

Index

A
A_LEV_HO . . . . . . . . . . A_LEV_PC . . . . . . . . . . . A_PBGT_HO. . . . . . . . . . A_QUAL_HO . . . . . . . . . A_QUAL_PC . . . . . . . . . . AC_CN . . . . . . . . . . . . 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 . . . . add_access_class . . . . . . . add_cell . . . . . . . . . . . . add_conn . . . . . . . . . . . add_neighbor . . . . . . . . . add_nsvc . . . . . . . . . . . add_rtf_path . . . . . . . . . adj_chan_intf_test . . . . . . . alarm devices . . . . . . . . . alarm_mode . . . . . . . . . . alias . . . . . . . . . . . . . . allow_8k_trau . . . . . . . . . alt_qual_proc . . . . . . . . . ambiguous command response . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-761, 6-769 . . . . 6-763 6-761, 6-828 6-774, 6-778 . . . . 6-780 . . . . 6-142 . . . . . 6-9 . . . . 6-10 . . . . 6-11 . . . . 6-12 . . . . 6-13 . . . . 6-15 . . . . 6-16 . . . . 6-17 . . . . 6-18 . . . . 6-19 . 3-448, 6-20 . . . . 6-21 . . . . 6-22 . . . . 6-23 . . . . . 7-2 . . . . 3-22 . . . . 3-33 . . . . 3-35 . . . . 3-48 . . . . 3-50 . . . . 3-448 . . . . 3-20 . . . . 3-52 . . . . . 4-2 . . . . 6-24 . . . . 6-26 . . . . 1-27 amr_bss_full_rate_enabled amr_bss_half_rate_enabled amr_dl_la_mode_chg_min . amr_dl_thresh_adjust . . . amr_fr_dl_la_enabled . . . amr_fr_ul_la_enabled . . . amr_full_rate_enabled. . . amr_half_rate_enabled . . amr_hr_dl_la_enabled . . . amr_hr_ul_la_enabled . . . amr_ms_high_cmr . . . . . amr_ms_high_rxqual . . . amr_ms_low_cmr . . . . . amr_ms_low_rxqual . . . . amr_ms_monitor_period. . antenna_select . . . . . . arp_bg_1 . . . . . . . . . arp_bg_2 . . . . . . . . . arp_bg_3 . . . . . . . . . arp_i_be_1. . . . . . . . . arp_i_be_2. . . . . . . . . arp_i_be_3. . . . . . . . . arp_streaming_1 . . . . . arp_streaming_2 . . . . . arp_streaming_3 . . . . . assess . . . . . . . . . . . assign_successful . . . . . asym_edge_enabled . . . . ATT . . . . . . . . . . . . attach_detach . . . . . . . auto_dl_dur . . . . . . . . auto_rf_loss_trace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-31 . . . . . . 6-30 . . . . . . 6-32 . . . . . . 6-33 . . . . . . 6-34 . . . . . . 6-35 . . . . . . 6-36 . . . . . . 6-38 . . . . . . 6-40 . . . . . . 6-41 . . . . . . 6-42 . . . . . . 6-43 . . . . . . 6-44 . . . . . . 6-45 . . . . . . 6-46 . . . . . . . 8-6 . . . . . . 6-47 . . . . . . 6-49 . . . . . . 6-51 . . . . . . 6-53 . . . . . . 6-55 . . . . . . 6-57 . . . . . . 6-59 . . . . . . 6-61 . . . . . . 6-63 . . . . . . 3-54 . . . . . . . 7-3 . . . . . . 6-65 . . . . . . 6-67 6-65 to 6-66, 6-178 . . . . . . . . 7-5 . . . . . . . 6-68

B
ba_alloc_proc . . . . . ba_bcch . . . . . . . . ba_gprs . . . . . . . . band_preference . . . band_preference_mode base_ip_address. . . . bcch_info . . . . . . . bep_period . . . . . . bep_period2 . . . . . . ber_loss_daily . . . . . 68P02901W23-S Nov 2009 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-70 . . 3-448 . . 3-448 . . 6-72 . . 6-74 . . 6-77 . . . 7-6 . . . 7-7 . . . 7-8 6-77, 6-79 ber_loss_hourly . . . . . . ber_oos_mon_period . . . ber_restore_mon_period . blind_search_preference . bounce_protect_cong_tmr . bounce_protect_margin . . bounce_protect_qual_tmr . bs_ag_blks_res . . . . . . BS_AG_BLKS_RES . . . . bs_pa_mfrms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-80 . . 8-8 . 8-10 . 6-81 . . 7-9 . 6-82 . 7-10 . 6-83 . 6-84 . 6-85 IX-1

Index

BS_PA_MFRMS . . . . . . bs_pag_blks_res . . . . . . bs_pbcch_blks . . . . . . . bs_pcc_chans . . . . . . . bs_prach_blks . . . . . . . BS_TXPWR_RED . . . . . bsc_audit . . . . . . . . . bsc_audit_response . . . . bsc_cbc_operator . . . . . bsc_type. . . . . . . . . . bsic . . . . . . . . . . . . BSIC . . . . . . . . . . . BSIC_NC(n) . . . . . . . . BSP max_mtls . . . . . . . . BSS ne_id . . . . . . . . . . BSS Initialization Process about . . . . . . . . . . _bss_data,10 . . . . . . . Description . . . . . . . Syntax . . . . . . . . . Values . . . . . . . . . . _bss_data,6 . . . . . . . . Description . . . . . . . Syntax . . . . . . . . . Values . . . . . . . . . . bss_egsm_alm_allowed . . bss_msc_overload_allowed bss_overload_control . . . BSSGP T1 . . . . . . . . . bssgp_block_retries . . . . bssgp_cbl_bit . . . . . . .

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

. 6-86 . 6-87 . 6-88 . 6-89 . 6-90 . 6-552 . 7-11 . 7-12 . 8-12 . 6-91 . 6-93 . 6-95 . 6-95 8-63 8-73 1-15 3-588 3-588 3-588 3-588 3-587 3-587 3-587 3-587 6-97 6-98 7-13 7-17 6-99 6-100

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

bssgp_dwnld_retry . . . . bssgp_fc_period_c . . . . . bssgp_pfc_bit . . . . . . . bssgp_racap_retries . . . . bssgp_reset_retries . . . . bssgp_t1_timer . . . . . . bssgp_t2_timer . . . . . . bssgp_t4_timer . . . . . . bssgp_t5_timer . . . . . . bssgp_t6_timer . . . . . . bssgp_t8_timer . . . . . . bssgp_unblock_retries . . bssmap_t1. . . . . . . . . bssmap_t10 . . . . . . . . bssmap_t11 . . . . . . . . bssmap_t13 . . . . . . . . bssmap_t19 . . . . . . . . bssmap_t20 . . . . . . . . bssmap_t4. . . . . . . . . bssmap_t7. . . . . . . . . bssmap_t8. . . . . . . . . bssmap_tqh0 . . . . . . . BTP max_dris . . . . . . . . bts_audit . . . . . . . . . bts_audit_response . . . . bts_escalation . . . . . . . bts_p_con_ack . . . . . . . bts_p_con_interval . . . . bts_power_control_allowed bts_txpwr_max_inner . . . bts_type . . . . . . . . . . bvci . . . . . . . . . . . .

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

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

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

6-102 7-14 6-103 6-105 6-106 7-16 7-18 7-20 7-22 7-23 7-24 6-107 7-25 7-32 7-34 7-36 7-38 7-39 7-26 7-28 7-30 7-40 8-60 7-41 7-42 7-43 6-108 6-110 6-112 6-438 6-118 6-120

. . . . . . . . . . . . . . . . . . . . . 6-114, . . . . . . . .

C
C2. . . . . . . . . . . . . . . . . . . c31_hyst . . . . . . . . . . . . . . . c32_qual . . . . . . . . . . . . . . . cab . . . . . . . . . . . . . . . . . . int_antenna . . . . . . . . . . . . . int_hdsl_modem . . . . . . . . . . . cabinet_type . . . . . . . . . . . . . cage_audit . . . . . . . . . . . . . . Call Processing about . . . . . . . . . . . . . . . . call_trace_options . . . . . . . . . . . called_pci . . . . . . . . . . . . . . . calling_pci . . . . . . . . . . . . . . carrier_disable_time . . . . . . . . . carrier_free_immediate . . . . . . . . carriers_ins_pwr_fail . . . . . . . . . Caution, commands Commands to be used with caution . Caution, parameters Parameters to be used with caution . . . . . . . . . . . . . . . . . 6-856 . 6-180 . 6-182 . 8-13 . 8-51 . 8-52 . 8-13 . 3-58 . . . . . . . 1-16 6-122 6-124 6-125 6-126 7-44 6-127 1-24 1-25 cavity . . . . . . . . . . . . . cbc_fast_select . . . . . . . . cbc_intface_vers . . . . . . . cbc_operator . . . . . . . . . cbc_vbind_cntr . . . . . . . . cbch_1 . . . . . . . . . . . . cbch_2 . . . . . . . . . . . . cbch_3 . . . . . . . . . . . . cbch_enabled . . . . . . . . . CBL bsc_cbc_operator . . . . . . cbc_operator . . . . . . . . cbs_outage_cntr. . . . . . . . ccch_conf . . . . . . . . . . . bs_ag_blks_res dependency . CCCH_CONF . . . . . . . . . CCCH_LOAD_IND_PERIOD . . ccch_load_period . . . . . . . CCCH_SDCCH_COMB . . . . CCITT Q.713 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-17 6-129 6-131 8-18 6-132 7-45 7-46 7-47 6-133 8-12 8-18 6-134 6-135 6-83 6-137 6-139 6-138 6-137 6-124

. . . .

IX-2

68P02901W23-S Nov 2009

Index

CE_RE_HYS . . . . . . . . . . . . . cell identity UTRAN . . . . . . . . . . . . . . CELL_BAR_ACCESS . . . . . . . . cell_bar_access_class . . . . . . . . cell_bar_access_switch . . . . . . . cell_bar_qualify . . . . . . . . . . . cell_barred_delay . . . . . . . . . . cell_name . . . . . . . . . . . . . . cell_reselect_hysteresis . . . . . . cell_reselect_offset . . . . . . . . . CELL_RESELECT_OFFSET . . . . . cell_reselect_param_ind. . . . . . . CELL_RESELECT_PARAM_IND . . . cell_zone . . . . . . . . . . . . . . chan_alloc_priority . . . . . . . . . channel_ack . . . . . . . . . . . . . channel_reconfiguration_switch. . . channel_teardown. . . . . . . . . . chg_a5_alg_pr . . . . . . . . . . . . chg_acs_params. . . . . . . . . . . chg_audit_sched . . . . . . . . . . chg_cell_element . . . . . . . . . . chg_cell_id . . . . . . . . . . . . . chg_cmd_level . . . . . . . . . . . chg_csfp . . . . . . . . . . . . . . chg_dte . . . . . . . . . . . . . . . chg_eas_alarm . . . . . . . . . . . chg_element . . . . . . . . . . . . chg_element (statistics application) . chg_hop_params . . . . . . . . . . chg_ksw_config . . . . . . . . . . . chg_level . . . . . . . . . . . . . . chg_rtf_freq . . . . . . . . . . . . . chg_severity. . . . . . . . . . . . . chg_smscb_msg . . . . . . . . . . . data_coding_scheme . . . . . . . chg_stat_prop . . . . . . . . . . . . chg_throttle . . . . . . . . . . . . . chg_time . . . . . . . . . . . . . . chg_ts_usage . . . . . . . . . . . . chg_x25config. . . . . . . . . . . . cic_block_thresh . . . . . . . . . . cic_error_clr_thresh . . . . . . . . . cic_error_gen_thresh . . . . . . . . cic_error_inc . . . . . . . . . . . . ciph_mode_rej_allowed . . . . . . . cipher_comp_ms . . . . . . . . . . ciphering_successful . . . . . . . . circuit_reset_ack . . . . . . . . . . clear_cal_data . . . . . . . . . . . . clear_command . . . . . . . . . . . clear_database . . . . . . . . . . .

. . . 6-149 . . . 6-366 . . . 6-144 . . . 6-140 . . . 6-143 . . . 6-145 . . . 6-147 . . . 3-62 6-148, 6-312 . . . 6-150 . . . 6-151 . . . 6-152 . . . 6-153 . . . 8-19 . . . 8-21 . . . 7-48 . . . 6-154 . . . 7-49 . . . 3-73 . . . 3-65 . . . 3-76 . . . 3-84 . . . 3-90 . . . 3-94 . . . 3-95 . . . 3-98 . . . 3-102 . . . 3-106 . . . 5-48 . . . 3-128 . . . 3-136 . . . 3-142 . . . 3-144 . . . 3-148 . . . 3-150 . . . 3-152 . . . . 5-5 . . . 3-156 . . . 3-158 . . . 3-161 . . . 3-166 . . . 8-22 . . . 6-156 . . . 6-157 . . . 6-158 . . . 6-160 . . . 7-50 . . . 7-52 . . . 7-54 . . . 3-169 . . . 7-56 . . . 3-171

clear_gclk_avgs . . . . . . . clk_src_fail_reset_period . . clkx0 . . . . . . . . . . . . clkx1 . . . . . . . . . . . . clkx2 . . . . . . . . . . . . CLM_MTA1 . . . . . . . . . CLM_MTJ1 . . . . . . . . . CLM_SPI_TIMER . . . . . . clm_t_stat_info . . . . . . . CLM_T1 . . . . . . . . . . . CLM_T13 . . . . . . . . . . CLM_T19 . . . . . . . . . . CLM_T20 . . . . . . . . . . CLM_T4 . . . . . . . . . . . coincident_cell . . . . . . . coincident_mb. . . . . . . . coincident_offset . . . . . . combiner_address. . . . . . combiner_id . . . . . . . . . combining_type . . . . . . . command response ambiguous . . . . . . . . Command Security Levels. . command types . . . . . . . concentric cells inner_zone_alg . . . . . . config_packet_size in BSS View at OMC GUI . config_window_size in BSS View at OMC GUI . Configuration Management BSS MMI functions . . . . configure_csfp . . . . . . . confusion_msg_allowed . . . congest_at_source. . . . . . congest_at_target . . . . . . congest_ho_margin . . . . . connection_code . . . . . . copy_cell . . . . . . . . . . copy_path . . . . . . . . . . Counter statistics . . . . . . cp_option_reset_ckt . . . . . cp_option_rr_status . . . . . cr_calling . . . . . . . . . . CRM rr_t3111_sd . . . . . . . . rr_t3212. . . . . . . . . . ct_flow_control_hi_level . . . ct_flow_control_lo_level . . . ct_flow_control_msc_trace . ctu2d_asym_opt . . . . . . . ctu2d_cap_opt. . . . . . . .

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

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

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-162, . . . . . . . . . . . . . . .

3-173 6-161 8-24 8-26 8-28 7-54 7-203 7-174 7-207 7-25 7-37 7-38 7-39 7-27 6-165 6-165 6-164 8-30 8-31 8-32 1-27 1-22 1-23

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

. . . . . . . 6-436 . . . . . . . 3-166 . . . . . . . 3-166 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-16 . . . 3-175 . . . 6-167 . . . 6-168 . . . 6-170 3-448, 6-171 . . . 3-177 . . . 3-179 . . . 3-187 . . . . 5-3 . . . 6-172 . . . 6-173 . . . 6-174 . . . . . . . . . . . . . . . . . . . . . 7-155 7-159 6-175 6-176 6-177 6-178 6-179

IX-5

Index

erc_ta_priority . . . . . eth_rx_errors_threshold . eth_tx_errors_threshold . ext_ho_allocation . . . .

. . . .

. 6-278 . . . . . . . . . . . . . . .

to . . .

6-280 6-279 6-280 7-66

ext_range_cell. . . 6-281, 6-283 to ext_rtry_cand_prd . . . . . . . . . . ext_timeslots . . . . . . . . . . . . extended_paging_active . . . . . . .

6-284, . . . . . . . . .

6-288 7-67 8-38 6-286

. . . . . . 1-17 . . . . . . 6-557 . . . . . . 1-28 . . . . . . . . . . . . . . . . . . . . . 1-28 . 1-32 . 1-26 . 6-558

68P02901W23-S Nov 2009

IX-9

Index

modify_neighbor (contd.)
umts_ba_bcch . . . . . . umts_meas_margin . . . umts_ncell_avg_period . modify_value . . . . . . . ms_distance_allowed . . . ms_max_range . . . . . . ms_p_con_ack . . . . . . . ms_p_con_interval. . . . . ms_power_control_allowed ms_power_offset . . . . . MS_RANGE_MAX . . . . . ms_sapi3_est . . . . . . . ms_txpwr_max . . . . . . MS_TXPWR_MAX . . . . . ms_txpwr_max_cch . . . . MS_TXPWR_MAX_CCH . . ms_txpwr_max_cell . . . . ms_txpwr_max_def . . . . MS_TXPWR_MAX_DEF . . ms_txpwr_max_inner . . . msc_bss_overload_allowed msc_mms_id. . . . . . . . msc_preference . . . . . . msc_qt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-450 to 3-450 to 3-450 to . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-438, . . . . . . . . . . . . . . . . 3-451 3-451 3-451 3-456 6-563 6-565 6-567 6-569 6-571 6-573 6-566 7-120 3-449 6-554 6-574 6-576 6-577 6-579 6-580 6-581 6-582 8-66 6-583 6-585

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

msc_release . . . . . . . . . . . . . . . . 6-587 MSI msc_mms_id . . . . . . . . . . . . . . 8-66 msi_type . . . . . . . . . . . . . . . . 8-67 transcoding-capability . . . . . . 8-93 to 8-94 msi_type . . . . . . . . . . . . . . . . . 8-67 mspwr_alg . . . . . . . . . . . . . . . . 6-588 mtbr_downgrade_enabled . . . . . . . . . 6-589 MTCRM_ADD_ACC_CLASS . . . . . . . . . 7-2 MTCRM_CARRIER_FREE_IMMEDIATE . . 7-44 MTCRM_CBT1 . . . . . . . . . . . . . . 7-45 MTCRM_CBT2 . . . . . . . . . . . . . . 7-46 MTCRM_CBT3 . . . . . . . . . . . . . . 7-47 MTCRM_DEOC_INTACT . . . . . . . . . 7-57 MTCRM_EMERG_RESERVED . . . . . . . 7-65 MTCRM_FC_T1 . . . . . . . . . . . . . . 7-68 MTCRM_FC_T2 . . . . . . . . . . . . . . 7-69 MTCRM_HANDOVER_ACK . . . . . . . . 7-77 MTCRM_REGISTER_EXP . . . . . . . . . 7-144 MTCRM_RF_CHAN_REL_ACK . . . . . . 7-145 mtl_loadshare_granularity . . . . . . . . 6-590 MULT bsic . . . . . . . . . . . . . . . . . . . 6-93 multiband_reporting . . . . . . . . . . . 6-591

N
n_avg_i . . . . . . . . N1 . . . . . . . . . . N2 . . . . . . . . . . N3 . . . . . . . . . . n391 . . . . . . . . . n392 . . . . . . . . . n393 . . . . . . . . . N4 . . . . . . . . . . N5 . . . . . . . . . . N6 . . . . . . . . . . N7 . . . . . . . . . . N8 . . . . . . . . . . nacc_enabled . . . . . nacc_nc2_enabled . . . Description . . . . . Syntax . . . . . . . Values . . . . . . . . nbit . . . . . . . . . . nc_non_drx_period . . nc_reporting_period_i . nc_reporting_period_t . NCC. . . . . . . . . . ncc_of_plmn_allowed . nccr_enabled . . . . . nccrOpt . . . . . . . . ne_id . . . . . . . . . neighbor_journal . . . neighbor_report_timer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-598, . . . . . . . . . . . . 6-594 6-192 6-194 6-196 8-69 8-70 8-71 6-198 6-200 6-202 6-204 6-206 6-593 3-469 3-469 3-469 3-469 8-72 7-122 7-124 7-125 6-596 6-595 6-597 6-637 8-73 6-599 7-127 neighboring_range . . . . . network_control_order . . . new_calls_hr . . . . . . . . ni . . . . . . . . . . . . . . NIU equip command . . . . . . ns_alive_retries . . . . . . . ns_alive_timer. . . . . . . . ns_block_retries . . . . . . . ns_block_timer . . . . . . . ns_burst_excess mod_nsvc command. . . . ns_burst_size mod_nsvc command. . . . ns_commit_info_rate mod_nsvc command. . . . ns_reset_period . . . . . . . ns_reset_timer . . . . . . . ns_test_timer . . . . . . . . ns_unblock_retries . . . . . nsei . . . . . . . . . . . . . num_audit_retires . . . . . . num_emerg_access . . . . . num_emerg_rejected . . . . num_emerg_tch_kill . . . . . num_emerg_term_sdcch . . num_gbl_dl_thrput_samples . num_gbl_ul_thrput_samples . . . . . . . . . 6-582, . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-603, . . . . . . . . . . . . . . . . . . 3-449 6-601 7-161 6-604 2-42 6-606 7-128 6-607 7-129

. . . . . . . 3-445 . . . . . . . 3-445 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-445 7-130 7-132 7-133 6-608 6-609 6-610 6-611 6-612 6-613 6-614 6-615 6-616

IX-10

68P02901W23-S Nov 2009

Index

number_of_preferred_cells . . . . . . . . 6-617

number_sdcchs_preferred. . . . . . . . . 6-619

O
opc . . . . . . . option_alg_a5_1 . option_alg_a5_2 . option_alg_a5_3 . option_alg_a5_4 . option_alg_a5_5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-621 6-623 6-624 6-625 6-626 6-627 option_alg_a5_6 . . . . . . . . . option_alg_a5_7 . . . . . . . . . option_preempt . . . . . . . . . opto_reporting . . . . . . . . . outer_zone_usage_level . . . . . override_intra_bss_pre_transfer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-628 6-629 6-630 8-74 6-632 6-633

1-16 3-530 6-822 3-534 6-823

stp_pc_enabled . . . . . . . stream_downgrade_enabled. streaming_enabled . . . . . surround_cell . . . . . . . . sw_pdtch_priority . . . . . . sw_ts_less_one_carrier . . . swap_devices . . . . . . . . swfm_enable . . . . . . . . switch_gprs_pdchs . . . . . sync_loss_daily . . . . . . . sync_loss_hourly . . . . . . sync_loss_oos . . . . . . . . sync_loss_restore . . . . . . sync_time_oos . . . . . . . . sync_time_restore . . . . . . synchronized . . . . . . . . Syntax command syntax . . . . . SYSGEN OFF mode . . . . . SYSGEN ON mode . . . . . sysgen_mode . . . . . . . . sysgen_mode off . . . . . . sysgen_mode on. . . . . . .

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

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

6-824 6-825 6-826 6-827 6-829 6-830 3-537 6-832 6-833 6-835 6-836 6-837 6-838 6-839 6-840 3-449

. 1-26 . 1-43 . 1-43 . 3-540 . 1-44 . 1-44

T
t_avg_t . . . . . . . . t_avg_w . . . . . . . . T_HAND_RQD. . . . . T_SDCCH_HO_OWED . t_stat_info . . . . . . . T1 (CCITT) . . . . . . T1_TIMER. . . . . . . T12_TIMER . . . . . . T13_TIMER . . . . . . T14_TIMER . . . . . . T17_TIMER . . . . . . T2 (CCITT) . . . . . . T2_TIMER. . . . . . . T22_TIMER . . . . . . T23_TIMER . . . . . . T3 . . . . . . . . . . . T3101 . . . . . . . . . T3103 . . . . . . . . . T3105 . . . . . . . . . T3109 . . . . . . . . . T3111 . . . . . . . . . T3212 . . . . . . . . . t391 . . . . . . . . . . t392 . . . . . . . . . . T4 (CCITT) . . . . . . T4_TIMER. . . . . . . T5 (CCITT) . . . . . . T5_TIMER. . . . . . . T6 (CCITT) . . . . . . T7 (CCITT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-176, . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-178, . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-156, . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-841 6-842 7-76 6-796 7-207 7-180 7-190 7-194 7-195 7-196 7-197 7-182 7-191 7-199 7-201 7-184 7-150 7-149 7-152 7-154 7-158 7-160 8-89 8-90 7-185 7-192 7-186 7-193 7-188 7-189 tch_busy_critical_threshold . . tch_busy_norm_threshold . . . tch_congest_prevent_thres . . tch_flow_control. . . . . . . . tch_full_need_low_water_mark tch_usage_threshold . . . . . TCONN_EST . . . . . . . . . tcu_port . . . . . . . . . . . . td_enabled . . . . . . . . . . tdd_qoffset . . . . . . . . . . tdm_switch . . . . . . . . . . tdm_ts_blocks . . . . . . . . . tdOpt . . . . . . . . . . . . . temporary_offset . . . . . . . thp_be_weight. . . . . . . . . thp_bg_weight . . . . . . . . thp_i2_weight . . . . . . . . . thp_i3_weight . . . . . . . . . thp_stream_weight . . . . . . THRES_PC_RLF . . . . . . . . threshold . . . . . . . . . . . time_cell_oos . . . . . . . . . time_stamp . . . . . . . . . . timeouts. . . . . . . . . . . . timing_advance_period . . . . tlli_blk_coding. . . . . . . . . TM_CHANNEL_ACT . . . . . TM_HO_NY1_REP . . . . . . . TM_HO_T3105 . . . . . . . . TM_MODE_MODIFY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-352, . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-844 6-845 6-846 6-847 6-849 6-850 7-167 8-91 6-852 6-851 6-853 6-854 8-93 6-855 6-857 6-858 6-859 6-860 6-861 6-525 6-862 7-206 3-548 1-27 6-863 6-865 7-48 7-147 7-152 7-117

IX-14

68P02901W23-S Nov 2009

Index

TM_SAACH_INFO . . . Tqho . . . . . . . . . trace call_trace_options . . trace_call command . . trace_connection . . . trace_msgs_after_ho . trace_msgs_before_ho. trace_stop . . . . . . . transcoding_capability TREL . . . . . . . . . tru_id . . . . . . . . .

. . . . . . . . . . 7-165 . . . . . . . . . . 7-40 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-122 3-550 3-562 6-866 6-867 3-564 8-94 7-171 8-95

trunk_critical_threshold . . . . . . trunk_major_threshold . . . . . . trx_pwr_red . . . . . . . . . . . . ts_alloc_flag . . . . . . . . . . . . ts_in_usf_active . . . . . . . . . . tsc_update_method . . . . . . . . tx_integer . . . . . . . . . . . . . TX_INTEGER . . . . . . . . . . . tx_power_cap . . . . . . . . . . . Type A commands and parameters Type B commands and parameters

. . . . . . . . . . .

6-868 6-869 8-96 6-870 6-872 6-873 6-875 6-876 6-877 1-23 1-23

U
u_rxlev_dl_ih . . . . u_rxlev_dl_p . . . . . U_RXLEV_DL_P . . . u_rxlev_ul_h . . . . . u_rxlev_ul_p . . . . . U_RXLEV_UL_P . . . u_rxqual_dl_p . . . . U_RXQUAL_DL_P . . u_rxqual_dl_p_hr . . u_rxqual_ul_p . . . . U_RXQUAL_UL_P . . u_rxqual_ul_p_hr . . ul_audio_lev_offset . ul_rxlev_ho_allowed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-879 6-881 6-882 6-883 6-885 6-886 6-887 6-888 6-889 6-891 6-892 6-893 6-895 6-896 ul_rxqual_ho_allowed . . . . UMTS UTRAN Cell ID. . . . umts_band_preferred . . . . umts_cpich_ec_no_min . . . umts_cpich_rscp_min . . . . unalias . . . . . . . . . . . unconfigure_csfp . . . . . . unequip . . . . . . . . . . . unequipped_circuit_allowed. unlock_device . . . . . . . . uplink_sync_timer . . . . . . use_bcch_for_gprs . . . . . use_derived_ho_power . . . use_neighbor_pbgt_hreqave. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-898 6-366 6-900 6-901 6-902 4-10 3-568 3-570 6-903 3-581 7-208 6-905 6-906 6-907

V
valid card slots . . . . . . . . . . . . . . 3-17 valid_candidate_period . . . . . . . . . . 7-210 volume_control_type . . . . . . . . . . . 6-908

W
wait_for_reselection. . . . . . . . . . . . 6-910 wait_indication_parameters . . . . . . . . 6-911 window_size. . . . . . . . . . . . . . . . 3-166 worse_neighbor_ho . . . . . . . . . . . . 6-913

X
XBL lapd_k . . . . . . . . . . . . . . . . . . lapd_n200 . . . . . . . . . . . . . . . .

XBL (contd.)
8-53 8-55 lapd_t200_timer . . . . . . . . . . . . . 8-57 xcdr_d_vad_dtx . . . . . . . . . . . . . . 6-226

68P02901W23-S Nov 2009

IX-15

Index

Z
zone_ho_hyst . . . . . . . . . . . 6-438, 6-914 zone_pingpong_count . . . . . . . . . . . 6-916 zone_pingpong_disable_win . . . . . . . . 7-211 zone_pingpong_enable_win . . . . . . . . 7-212 zone_pingpong_preferred_zone . . . . . . 6-917

IX-16

68P02901W23-S Nov 2009

Tj5500-Tj5100 Im Guide
No ratings yet
Tj5500-Tj5100 Im Guide
57 pages
ZXMSG 9000 Media Gateway Operation Guide 9000
100% (1)
ZXMSG 9000 Media Gateway Operation Guide 9000
177 pages
Copia Parte1 PDF
100% (1)
Copia Parte1 PDF
578 pages
Sap Time Management Holiday and Virriant Configuration Final PDF
No ratings yet
Sap Time Management Holiday and Virriant Configuration Final PDF
47 pages
1350 Oms SDH R 9.1.1 MNT4 - Top63052 - V1.0
No ratings yet
1350 Oms SDH R 9.1.1 MNT4 - Top63052 - V1.0
825 pages
AXE 810 Inro-1
No ratings yet
AXE 810 Inro-1
8 pages
Trainig BTSM
No ratings yet
Trainig BTSM
38 pages
Project File Format
No ratings yet
Project File Format
11 pages
Transcend Chorus For Packet SR10.0 Third Party Hardware and Software Requirements
No ratings yet
Transcend Chorus For Packet SR10.0 Third Party Hardware and Software Requirements
34 pages
r48 3500e3 Datasheet PDF
No ratings yet
r48 3500e3 Datasheet PDF
2 pages
MGW Device Trouble Shoot
No ratings yet
MGW Device Trouble Shoot
131 pages
Technical Description BSS Command Reference
No ratings yet
Technical Description BSS Command Reference
1,834 pages
8650 SDM Product Installation Sheet
100% (2)
8650 SDM Product Installation Sheet
32 pages
Digital Image Processing - Lecture Weeks 1&2 PDF
No ratings yet
Digital Image Processing - Lecture Weeks 1&2 PDF
50 pages
Planet Sip Analog Telephone Adapter Vip 156-157 Series
100% (1)
Planet Sip Analog Telephone Adapter Vip 156-157 Series
75 pages
Ericsson AXE 810: Switch (ROTD)
No ratings yet
Ericsson AXE 810: Switch (ROTD)
4 pages
Cabinet Interfaces and External Cables of IPA-RNC
No ratings yet
Cabinet Interfaces and External Cables of IPA-RNC
50 pages
Language Form One
No ratings yet
Language Form One
91 pages
RNC Configuration
No ratings yet
RNC Configuration
5 pages
Examen y Respuestas Mtcre
100% (1)
Examen y Respuestas Mtcre
3 pages
Compatibility Matrix FOS 8x September 2021
No ratings yet
Compatibility Matrix FOS 8x September 2021
50 pages
Broadgate Bg-30 Iomm A01 v3 en
No ratings yet
Broadgate Bg-30 Iomm A01 v3 en
204 pages
Avoset Pump User Manual US 15132 048 0003 UM
No ratings yet
Avoset Pump User Manual US 15132 048 0003 UM
88 pages
LG Xh-t9546 DVD Home Theater
No ratings yet
LG Xh-t9546 DVD Home Theater
57 pages
OMS1260 EX Inst Technic
100% (1)
OMS1260 EX Inst Technic
30 pages
Phan Cung MGC
No ratings yet
Phan Cung MGC
120 pages
ERX Intro+bras
No ratings yet
ERX Intro+bras
156 pages
Huawei Elte3.3 Dbs3900 FDD
No ratings yet
Huawei Elte3.3 Dbs3900 FDD
2 pages
Site Creation - Commissioning Guide - 5060 MGC10: Implementation Methods
No ratings yet
Site Creation - Commissioning Guide - 5060 MGC10: Implementation Methods
114 pages
ISAM R2.2 CLI Command Guide
100% (4)
ISAM R2.2 CLI Command Guide
923 pages
Nokia BSC 3i3
No ratings yet
Nokia BSC 3i3
3 pages
01 01 CT53331EN53GLA0 RNC Architecture and Functionalities
No ratings yet
01 01 CT53331EN53GLA0 RNC Architecture and Functionalities
71 pages
Updating ESB26 Binos Version
No ratings yet
Updating ESB26 Binos Version
20 pages
Stec55x - Pilot Guide
No ratings yet
Stec55x - Pilot Guide
80 pages
Nokia RNC Catalogue
No ratings yet
Nokia RNC Catalogue
2 pages
Hella-India Report
No ratings yet
Hella-India Report
36 pages
LCT APT V2 - Boot Configuration Tool - R1-Notes
100% (1)
LCT APT V2 - Boot Configuration Tool - R1-Notes
11 pages
Cellular Parametric Test: Racal Instruments Wireless Solutions 6113
No ratings yet
Cellular Parametric Test: Racal Instruments Wireless Solutions 6113
8 pages
Study On: Dubbing
No ratings yet
Study On: Dubbing
22 pages
M1 R5 O-Level Detailed
No ratings yet
M1 R5 O-Level Detailed
4 pages
IBM SAP AMS Cloud and OnPrem Support
100% (1)
IBM SAP AMS Cloud and OnPrem Support
16 pages
Carritech AXE10 - 810 September 2015
No ratings yet
Carritech AXE10 - 810 September 2015
27 pages
Spare Tracker Region
No ratings yet
Spare Tracker Region
56 pages
00 CN60050EN42GLA1 Presentation
No ratings yet
00 CN60050EN42GLA1 Presentation
6 pages
APG40
100% (1)
APG40
4 pages
Coding Guidelines
No ratings yet
Coding Guidelines
22 pages
Sjzl20070303-ZXWN MGW (V3.06) Media Gateway Technical Manual
No ratings yet
Sjzl20070303-ZXWN MGW (V3.06) Media Gateway Technical Manual
119 pages
Your Free Disaster Recovery Plan Template 1
0% (1)
Your Free Disaster Recovery Plan Template 1
21 pages
Bootimx8 Boot Log
No ratings yet
Bootimx8 Boot Log
15 pages
Advanced Linux System Administra3on: Topic
No ratings yet
Advanced Linux System Administra3on: Topic
49 pages
DV55A-A BOE Digital Signage Spec-55 Inch-V0.1
No ratings yet
DV55A-A BOE Digital Signage Spec-55 Inch-V0.1
4 pages
BG 64 Details
100% (1)
BG 64 Details
4 pages
08-9696-308 Alcatel-Lucent 9370 RNC Physical Installation May09
No ratings yet
08-9696-308 Alcatel-Lucent 9370 RNC Physical Installation May09
58 pages
Jumper Setting PCU2-E C110629
No ratings yet
Jumper Setting PCU2-E C110629
3 pages
Os 1-4
No ratings yet
Os 1-4
16 pages
Student Login Details For PG SEM I 2023 - GEOGRAPHY
No ratings yet
Student Login Details For PG SEM I 2023 - GEOGRAPHY
36 pages
Data Analytics Process
No ratings yet
Data Analytics Process
10 pages
1660SM31 Oper Ed01
No ratings yet
1660SM31 Oper Ed01
494 pages
5620 SAM Part Number Listing
No ratings yet
5620 SAM Part Number Listing
109 pages
Release Notes 5.8 SR1.En
No ratings yet
Release Notes 5.8 SR1.En
24 pages
Cisco D9854
No ratings yet
Cisco D9854
8 pages
OpenScape Business V1, OpenStage 40-60-80 T USB Driver, Installation Guide, Issue 1
No ratings yet
OpenScape Business V1, OpenStage 40-60-80 T USB Driver, Installation Guide, Issue 1
11 pages
Chapter-5-The Internet and Its Uses
No ratings yet
Chapter-5-The Internet and Its Uses
17 pages
Motorola Parameter PDF
No ratings yet
Motorola Parameter PDF
2,195 pages
Managing The Forces of Fragmentation
No ratings yet
Managing The Forces of Fragmentation
9 pages
Exploiting Overestimated Volatility Risk Premium A Contrarian ETF Trading Strategy
No ratings yet
Exploiting Overestimated Volatility Risk Premium A Contrarian ETF Trading Strategy
16 pages
Warehouse Design and Operation Using Augmented Reality Technology - A Papermaking Industry Case Study
No ratings yet
Warehouse Design and Operation Using Augmented Reality Technology - A Papermaking Industry Case Study
6 pages
NSN RNC 2600 Npgep Expansion
No ratings yet
NSN RNC 2600 Npgep Expansion
50 pages
Bts Siemens 241
No ratings yet
Bts Siemens 241
28 pages
01 Rn28121en20gla0 Bss Overview
No ratings yet
01 Rn28121en20gla0 Bss Overview
17 pages
NokiaNSN DX 200 MSC Server MSS Catalogue
No ratings yet
NokiaNSN DX 200 MSC Server MSS Catalogue
3 pages
February 2011 5780 DSC R3-0 DS
No ratings yet
February 2011 5780 DSC R3-0 DS
5 pages
GGSN Monitoring First Layer Handling PDF
No ratings yet
GGSN Monitoring First Layer Handling PDF
24 pages
(Readings) Deep Learning Applications in Business Activities
No ratings yet
(Readings) Deep Learning Applications in Business Activities
6 pages
3em22842ab - v1 - 9500 MPR Users Manual (Ansi) r01.01.00
No ratings yet
3em22842ab - v1 - 9500 MPR Users Manual (Ansi) r01.01.00
188 pages
Sitio Principal Resepción de Material
No ratings yet
Sitio Principal Resepción de Material
6 pages
Finding A Cryptocurrency Transaction ID (TXID) : What Is A Bitcoin Account?
No ratings yet
Finding A Cryptocurrency Transaction ID (TXID) : What Is A Bitcoin Account?
3 pages
Website Contents Details
No ratings yet
Website Contents Details
5 pages
Network Inter Working Between GSM MAP and ANSI-41 CDMA
100% (1)
Network Inter Working Between GSM MAP and ANSI-41 CDMA
547 pages
Tellabs Interface Module Concentrator 2 (IFC2)
No ratings yet
Tellabs Interface Module Concentrator 2 (IFC2)
2 pages
Nokia Siemens Networks Flexi MR 10 BTS Datasheet 19022013
No ratings yet
Nokia Siemens Networks Flexi MR 10 BTS Datasheet 19022013
5 pages
Lecture#02 of Ai Basic Course
No ratings yet
Lecture#02 of Ai Basic Course
5 pages
BS241 Commissioning
No ratings yet
BS241 Commissioning
35 pages
MC BSC
No ratings yet
MC BSC
4 pages
Base System (Binary, Decimal, Octal & Hexadecimal)
No ratings yet
Base System (Binary, Decimal, Octal & Hexadecimal)
2 pages
Motorola BSS Equipment Planning
No ratings yet
Motorola BSS Equipment Planning
855 pages
Microblogging Platforms Explained
No ratings yet
Microblogging Platforms Explained
4 pages
Nokia
No ratings yet
Nokia
40 pages
Global System For Mobile Communications (GSM) : 1 Summer Internship Report
No ratings yet
Global System For Mobile Communications (GSM) : 1 Summer Internship Report
51 pages
Voice over LTE Standard Requirements
From Everand
Voice over LTE Standard Requirements
Gerardus Blokdyk
3/5 (1)