BSS Feature Configuration Guide (Based On MML) (V900R008C12 - 01)

HUAWEI BSC6000 Base Station Controller V900R008C12
BSS Feature Configuration Guide(Based on MML)

Issue Date 01 2010-05-20
HUAWEI TECHNOLOGIES CO., LTD.
Copyright Huawei Technologies Co., Ltd. 2010. All rights reserved. No part of this document may be reproduced or transmitted in any form or by any means without prior written consent of Huawei Technologies Co., Ltd.
Trademarks and Permissions

and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd. All other trademarks and trade names mentioned in this document are the property of their respective holders.
Notice
The purchased products, services and features are stipulated by the contract made between Huawei and the customer. All or part of the products, services and features described in this document may not be within the purchase scope or the usage scope. Unless otherwise specified in the contract, all statements, information, and recommendations in this document are provided "AS IS" without warranties, guarantees or representations of any kind, either express or implied. The information in this document is subject to change without notice. Every effort has been made in the preparation of this document to ensure accuracy of the contents, but all statements, information, and recommendations in this document do not constitute the warranty of any kind, express or implied.
Huawei Technologies Co., Ltd.

Address: Huawei Industrial Base Bantian, Longgang Shenzhen 518129 People's Republic of China http://www.huawei.com [email protected]
Website: Email:
Issue 01 (2010-05-20)
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.
HUAWEI BSC6000 Base Station Controller BSS Feature Configuration Guide(Based on MML)
About This Document
About This Document
Purpose
This document provides the information on how to configure, modify, and verify the features on the Local Maintenance Terminal and the BSC6000 Local Maintenance Terminal.
Product Versions
The following table lists the product versions related to this document. Product Name BSC BTS Product Model BSC6000 BTS3012 BTS3012AE BTS3006C BTS3002E DBS3036 BTS3036 BTS3036A DBS3900 GSM BTS3900 GSM BTS3900A GSM BTS3900B GSM BTS3900E GSM Product Version V900R008C12 V300R008 V300R008 V300R008 V300R008 V300R008 V300R008 V300R008 V300R008 V300R008 V300R008 V300R008 V300R008
Issue 01 (2010-05-20)
iii
About This Document
Intended Audience
This document is intended for:
l l
Technical support engineers Maintenance engineers
Organization
1 Changes in BSS Feature Configuration Guide (Based on MML) This describes the changes in the various versions of BSS Feature Configuration Guide(Based on MML). 2 Configuring the Multiband Network A multiband network consists of multiple frequency bands. The combined multiband network can increase the utilization of frequency resources on the radio network. 3 Configuring the Speech Version This describes how to configure the speech version on the Local Maintenance Terminal. 4 Configuring ALC Automatic level control (ALC) adjusts the gain of digital voice signals on the uplink and downlink every 20 ms and changes the amplitude of digital voice signals in static or dynamic mode. This keeps the voice level of the entire network in a predefined state, prevents the volume fluctuation of the two parties during a call, and reduces interference among the normal calls. 5 Configuring Acoustic Echo Cancellation Acoustic echo cancellation (AEC) can decrease acoustic echo caused by the MS, thus improving the network quality and voice quality. 6 Configuring Cell Broadcast Cell broadcast is a teleservice that periodically broadcasts messages to all the MSs in a specified area. With cell broadcast, the mobile network operators can provide special services for users. 7 Configuring Ciphering The ciphering algorithm encrypts the subscriber information such as the voice and data so that the information is securely transmitted on the Um interface. 8 Configuring Frequency Hopping With this feature, wanted signals are transmitted by switching a carrier among many frequencies according to the specified sequences. Frequency hopping involves RF hopping and baseband hopping.Frequency hopping is a spread-spectrum technology, which has the features such as resistance to interference, anti-attenuation, and high security. The application of frequency hopping in the GSM supresses the interference and increases the system capacity. 9 Configuring eMLPP The eMLPP is a supplementary service offered by the GSM system. The eMLPP service allows a subscriber to initiate calls with different priorities. The network side employs different channel
iv Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2010-05-20)
About This Document
assignment strategies for the subscribers according to the priorities. If the network is congested, the call with higher priority is served preferably. 10 Configuring Priority-Based Resource Reservation With priority-based resource reservation, the system reserves a certain number of TCHFs for the high-priority users to ensure their QoS. By using this function, operators can provide services of different levels for users with different priorities, thus increasing the operators' revenues. 11 Configuring Network Support SAIC This describes how to configure the Network Support SAIC. The Single Antenna Interference Cancellation (SAIC) is a technique for restraining the co-channel interference and adjacentchannel interference. This technique is especially adopted in the single antenna scenario to reduce the interference on the reception of downlink signals. 12 Configuring Active Power Control This describes how to configure the active power control. After an MS accesses the network or an intra-BSC handover is performed successfully, the BSC controls the uplink and downlink power so that the MS and the BTS transmit signals at the proper power. In this way, power control can be performed in time. Through the active power control, the system interference is reduced, the QoS is improved, and the power consumption of the BTS and the MS is decreased. 13 Configuring Robust Air Interface Signalling With the robust air interface signalling function, when the radio quality is poor, the antiinterference capability of the FACCH and SACCH is improved through repeated sending of the FACCH and SACCH frames. In this manner, the MS and BSC can receive the signaling messages more successfully. The robust air interface signalling function includes repeated sending of the FACCH frames in the downlink and the repeated sending of the SACCH frames in the uplink and downlink. 14 Configuring BSS Paging Coordination With the BSS paging coordination function, the network can send the CS domain paging message to an MS in the packet transfer state on the PACCH if the Gs interface is not configured between the MSC/VLR and the SGSN. In this manner, the MS in the packet transfer state can respond to the CS domain paging. 15 Configuring a Co-BCCH Cell Co-BCCH cell is realized on the basis of the principles of the concentric cell. The TRXs on the GSM900M (or GSM850M) are configured in the underlaid subcell, which is used to expand the coverage area; and the TRXs on the DCS1800M (or PCS1900M) are configured in the overlaid subcell, which is used to absorb the traffic. The TRXs on two bands are distributed in the overlaid subcell and underlaid subcell that share one BCCH TRX. Co-BCCH cell increases the traffic capacity of a cell, decreases handovers and interference, and improves the continuous coverage and sparse coverage in hot spots. 16 Configuring 2G/3G Interoperability The 2G/3G interoperability feature enables an MS to be handed over to or reselected to the GSM network if the serving cell of the MS is not covered by the WCDMA/TD-SCDMA network or if the serving WCDMA/TD-SCDMA cell is in a weak coverage area. In addition, an MS can be handed over to or reselected to the WCDMA/TD-SCDMA network if the MS requires the PS services. When a dual-mode MS enters the coverage of the WCDMA/TD-SCDMA network again, or the MS detects that the WCDMA/TD-SCDMA cell is better than the serving GSM cell,
Issue 01 (2010-05-20) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. v
About This Document
the MS can be handed over to or reselected to the WCDMA/TD-SCDMA network if the handover or cell reselection conditions are met. Then, the MS can use the abundant services provided by the WCDMA/TD-SCDMA network. 17 Configuring TRX Cooperation With this feature, when the BCCH TRX or the TRX involved in baseband FH is faulty, the cell automatically rectifies the faults. Thus, the services in the cell are not affected before the faulty TRX is replaced. Based on the type of faulty TRXs and the handling method, the TRX cooperation is classified into BCCH TRX cooperation and baseband FH TRX cooperation. For the non-baseband FH cell, only the BCCH TRX cooperation occurs. For the baseband FH cell, both BCCH TRX cooperation and baseband FH TRX cooperation are likely to occur. 18 Configuring Cell Frequency Scan The cell frequency scan function enables the scanning of the levels of the uplink signals at specific frequencies on a specific channel of a cell. The scanned results of the signal levels provides references for engineers to select proper operating frequencies. 19 Configuring High-Speed Signaling Links The BSC uses the high-speed signaling when the 64 kbit/s signaling fail to meet the signaling requirements on the A interface due to high traffic volume. With this feature, the N timeslots in an E1 are bound for the physical transmission of the SS7 signaling. Therefore, the bandwidth of a signaling link is extended to N x 64 kit/s and a maximum of 2 Mbit/s E1 bandwidth (N = 31) can be used. 20 Configuring Local Multiple Signaling Points With this feature, a physical node is logically classified into multiple signaling points. Each signaling point can be independently connected to other signaling points and thus meets the signaling link requirements for large capacity processing of the BSC6000. In addition, the requirements for the signaling networking capability of the MSC are reduced because the highspeed signaling technology is not used. Thus, the operators' investment is saved. 21 Configuring DTX and DRX Discontinuous transmission (DTX) and discontinuous reception (DRX) increases the standby time and call duration of an MS. 22 Configuring Location Service Location sevice (LCS) enables the network to provide various services for an MS based on the location of the MS. These services include weather forecasts, trip scheduling, emergency assistance, stock information, business planning, and transportation conditions. The simple location service can locate an MS based on the information obtained during single-user message tracing. 23 Configuring TFO The TFO feature can reduce the speech signal degradation caused by tandem operation, thus improving the voice quality. When the calling MS and the called MS use the same speech version, the TFO link is established through the in-band signaling negotiation. In addition, the least significant bit (or the second least significant bit) is stolen to seize the 8 kbit/s (or 16 kbit/s) sublink of the PCM transmission link for transparent transmission of TFO frames and bypass TC encoding/decoding. In this manner, the speech signal is encoded at the MS initiating the call and decoded at the MS terminating the call for only once. Thus, the degradation of the speech signals due to tandem operation is reduced and the voice quality is improved. This process is called tandem free operation (TFO).
vi Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2010-05-20)
About This Document
24 Configuring PBT In the DTRU, two TRXs are integrated into a TRX module that is configured with a combiner. The combiner combines the radio signals of the same frequency and same phrase from two TRXs, and then transmits the combined signals. In this way, the downlink transmit power is higher than the transmit power of the original signals, and the transmit power with high gain is achieved and the downlink coverage is extended. 25 Configuring Transmit Diversity In the DTRU, two TRXs are integrated into one TRX module. With this feature, the two TRXs on the DTRU transmit the correlated signals of the same carrier. This provides two independent multi-path signals for the downlink. Then, the two independent multi-path signals are processed by the equalizer of the MS. In this way, the diversity gain is obtained, and the quality of the receive signal is improved. Therefore, the downlink coverage is improved. When the DTRU works in single TRX mode, the BTS can enable this feature through data configuration. 26 Configuring 4-Way Receive Diversity With appropriate design, the 4-way receiver diversity technology allows one TRX module to receive the uplink signals from four RX channels and then combine the uplink signals to achieve better signal quality and demodulation performance. Thus, the receive sensitivity is improved, and the receive effect is much better than that of none receiver diversity and that of two-way receiver diversity. 27 Configuring SDCCH Dynamic Adjustment SDCCH dynamic adjustment is to dynamically adjust the number of SDCCHs according to the load of the TCHs and SDCCHs. In this way, the effect of the initial configuration of the SDCCH on the system is minimized, and radio resources are fully utilized.This describes how to configure SDCCH dynamic adjustment on the Local Maintenance Terminal. 28 Configuring NACC NACC refers to network-assisted cell reselection. To implement rapid PS access after cell reselection, the BSC sends the system information about the target cell to the MS before cell reselection. Therefore, the service interruption time due to the cell reselection is minimized. This describes how to configure NACC on the Local Maintenance Terminal. 29 Configuring NC2 The network-controlled cell reselection (NC2) refers to the situation that the MS in packet transfer mode can be controlled by the network to reselect a cell according to the measurement report.This describes how to configure NC2 on the Local Maintenance Terminal. 30 Configuring Packet Performance Improvement This describes how to configure packet performance improvement on the external PCU maintenance console or Local Maintenance Terminal. 31 Configuring Flex Abis Flex Abis implements the sharing of the transmission resources on the Abis interface between different BTSs, cells, and services, and thus improves the resource utilization. Flex Abis is an allocation mode of the transmission resources on the Abis interface. That is, the transmission resources on the Abis interface form a resource pool to share resources between CS services and PS services (including idle timeslots) and also between different cells or BTSs. Especially when Flex Abis is enabled in multi-cell large capacity BTSs, cascading BTSs, and the cells configured
Issue 01 (2010-05-20) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. vii
About This Document
with the EGPRS function, the transmission resources on the Abis interface can be used in an efficient way. 32 Configuring the MSC Pool With this feature, a maximum of 32 MSCs form a resource pool to provide services for the subscribers under one group of BSCs. Through the MSC pool, one BSC can be connected to multiple MSCs at the same time. In addition, the traffic on the BSC is evenly distributed to the MSCs in the pool according to the NRI or load balancing principle. 33 Configuring BTS Ring Topology The ring networking mode is a special chain networking mode. Several BTSs form a chain, and the lowest-level BTS is connected to the BSC through the transmission link, thus forming a ring. If there is a breakpoint on the ring, the BTSs that precede the breakpoint remain unchanged in networking mode whereas the BTSs that follow the breakpoint form a new chain connection in the reverse direction. The BTS ring topology is categorized into two types: Huawei BTS ring topology I and Huawei BTS ring topology II. 34 Configuring APS The automatic protection switching (APS) function applies to optical port backup. If a fault occurs on the working channel, the BSC negotiates with the optical transmission equipment on the protection channel through the APS to switch traffic signals onto the protection channel. APS can improve the stability and maintainability of the entire system. The APS configuration consists of configuring and verifying APS. 35 Configuring BSC Local Switching With this feature, if the calling MS and called MS are under the same BSC, the speech signals on the Abis interface are looped back to the MS without traveling around the NSS. In addition, in the BSC local switch, the speech coding schemes of the calling MS and called MS are the same and thus no coding conversion is required. Therefore, the TC resources involved in the BSC local switch can be released, and thus the speech quality is improved. 36 Configuring BTS Local Switching With this feature, if the calling MS and called MS are within the coverage of the same BTS or BTS group, the BSC performs the loopback on the cabinet group of the convergent BTS. 37 Configuring Dynamic MAIO Under the BTSs with large capacity, adjacent-channel or co-channel interference are likely to occur among channels because the frequency resources are insufficient and the tight frequency reuse is adopted.With the dynamic MAIO, when an MAIO is assigned to a channel under activation, the MAIO value is dynamically adjusted according to the current interference and the MAIO value with the minimum interference is assigned to the channel,reduces the adjacentchannel and co-channel interference in the GSM system. 38 Configuring Antenna Hopping This describes how to configure antenna hopping. With antenna hopping, the downlink data on each TRX can be randomly transmitted on other TRXs. This optimizes the data reception of the MS from the main BCCH TRX and the data transmission of the main BCCH TRX, thus improving network performance. 39 Configuring Voice Quality Index
viii Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2010-05-20)
About This Document
The voice quality index (VQI) feature provides a direct method to measure the voice quality of the radio network. By measuring the uplink VQI and downlink VQI, the voice quality of the network is quantified, which provides a reference for future network optimization. 40 Configuring ANR Automatic noise restraint (ANR) reduces the background noise in the uplink speech signals and improves the signal noise ratio (SNR) and speech intelligibility. Thus, the speech signals are received clearly at the peer end. 41 Intelligent Power Consumption Decrease This describes how to decrease the power consumption of various BTS parts through the use of a technology to decrease the overall BTS power consumption. The technologies used for intelligent power consumption decrease are as follows: TRX Power Amplifier Intelligent Shutdown, Timeslot-level Shutdown of the Power Amplifier, Intelligent Combiner Bypass, PSU Smart Control, Power Optimization Based on Channel Type, Enhanced BCCH Power Consumption Optimization, Active Backup Power Control, Multi-Carrier Intelligent Voltage Regulation and TRX Working Voltage Adjustment. The technologies such as channel assignment algorithm, DTX, and power control also help to decrease the power consumption. 42 Configuring Tight BCCH Frequency Reuse The tight BCCH frequency reuse technology is applicable to the network with insufficient frequency resources. It increases the reusability of BCCH frequencies and reduces the number of frequencies used by the BCCHs. Therefore, more frequencies can be used at the FH layer, thus improving the system capacity. 43 Configuring Connection Inter BSC over IP This describes how to configuring Inter-BSC signaling links on the current BSC and external BSC on the Local Maintenance Terminal. 44 Managing a BSC Soft-Synchronized Network Task The Soft-Synchronized Network feature realizes the synchronization through software. With this feature, all the BTSs under one BSC synchronize with each other by adjusting the frame number, timeslot number, and bit offset in the timeslot to be the same through software. In a synchronous network, dynamic frequency allocation and dynamic channel assignment can be adopted to minimize inter-cell co-channel and adjacent-channel collision. This greatly improves the frequency usage and increases the network capacity. 45 Configuring Entire Network Synchronization This describes how to configure the DGPS in the BTS3012 or configure the USCU in the 3900 series base station or 3036 series base station to support the GPS function so that the entire network is synchronized. 46 Configuring BSS IP Transmission This describes three types of IP transmission in the BSS: A over IP, Abis over IP, and Gb over IP. According to the network planning, different networking modes can be used on each interface in the BSS as required. The networking reliability can be guaranteed by the active/standby mode, load sharing, and link detection. Meanwhile, the quality of IP transmission can be guaranteed by various QoS mechanisms. 47 Configuring Abis Transmission Optimization or HubBTS The Abis Transmission Optimization feature introduces the HDLC frame and HDLC channel without changing the physical transmission mode. It statistically multiplexes the traffic data,
Issue 01 (2010-05-20) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. ix
About This Document
signaling data, and OM data on the HDLC channel to obtain a higher transmission gain through voice frame compression and multiplexing. 48 Configuring SGSN Pool This feature enables a maximum of 32 SGSNs to form a resource pool to provide services for the subscribers belonging to one group of BSCs. With this feature, one BSC can be connected to multiple SGSNs at the same time. In addition, the traffic on the BSC is evenly distributed to the SGSNs in the pool according to the network resource identifier (NRI) or load balancing principle. 49 Configuring RAN Sharing On the condition that independency of CNs of multiple operators is maintained, RAN Sharing enables multiple operators to share one GBSS network so that they can use the resources (including the BSC, BTS, antenna system, transmission, and so on) in the GBSS network simultaneously. RAN Sharing supports a maximum of four operators. Each operator has an independent CN (MSC and SGSN). The shared GBSS uses a uniform network management system, which implements comprehensive management of all the resources in the GBSS. 50 Configuring Multi-site Cell This feature enables the subsites in different physical sites to be set to a logical cell, which is also called a cascading cell. A subsite refers to a certain area physically covered by multiple RRU/RFUs that belong to the same BBU. In the scenarios such as railway, tunnel, or indoor coverage, a cascading cell can reduce handovers, improve the coverage efficiency, and enhance the user experience. 51 Configuring IBCA IBCA algorithm is a channel assignment algorithm, which has a remarkable effect on improving the utilization of frequency resources and expanding the network capacity. To use the IBCA algorithm, the inter-site Um interface software synchronization or GPS synchronization should be enabled. In addition, the GPS synchronization requires the support from the hardware configuration. 52 Configuring BTS in automatic planning mode Before the automatic planning of the BTS, you need to preconfigure some parameters used by the algorithm on the M2000 client. You can also query the progress and result of the automatic planning of the BTS, analyze the data, or locate the fault on the M2000 client. For details, see M2000 Operator Guide. Configuring BTS in automatic planning mode includes Configuring a BTS3900B GSM in automatic planning mode and Configuring a BTS3900E GSM in automatic planning mode 53 Configure DTM Dual Transfer Mode (DTM) is a 3GPP-defined standard function. This feature implements the simplified operation function of the class A mobile phone, that is, concurrent CS services and PS services. DTM allows simultaneous transfer of CS service and PS service. That is, a subscriber can send photos or browse websites during a call. The 3G network provides concurrent CS service and PS service. With DTM, the subscribers in a GSM network can enjoy services similar to those provided in a 3G network. In addition, in areas with insufficient 3G coverage, subscribers can use the services that are similar to 3G services through the 2G network. 54 Configuring VGCS/VBS This describes how to configure the VGCS/VBS. Compared with the original GSM system, the GSM-R has new features, such as the Voice Group Call Service (VGCS), Voice Broadcast
x Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2010-05-20)
About This Document
Service (VBS), and enhanced Multi-Level Precedence and Pre-emption (eMLPP) service. The GSM-R can provide diversified voice dispatch services required in the private network. 55 Configuring AMR The adaptive multi rate (AMR) is a speech encoding and decoding algorithm, which can be adjusted between full-rate speech version 3 and half-rate speech version 3 specified by the protocol. With AMR, the BTS and the MS can evaluate the interference on the radio network according to the measurements such as receive level, receive quality, and carrier-to-interference (C/I) ratio, and then adjust the voice encoding rate accordingly. In this way, both the antiinterference capability of the radio communications system and the voice quality are improved. 56 Configuring Dynamically Adjusting the Uplink MCS Coding The BSS supports nine codec schemes: MCS-1 to MCS-9. With the Dynamically Adjusting the Uplink MCS Coding function, the uplink rate of an EGPRS user can be dynamically adjusted according to the actual network status. The BSC dynamically adjusts the codec scheme adopted by the PDCH according to the uplink measurement report reported by the BTS. In this manner, the codec scheme of the PDCH changes with the radio environment where the MS locates, thus improving the uplink throughput. 57 Configuring Concentric Cell A concentric cell is divided into an overlaid subcell and an underlaid subcell. Different frequency reuse patterns can be applied to the overlaid and underlaid subcells. 58 Configuring Extended Cell The application of extended cell breaks the coverage limit of 35 km of a GSM cell. This helps operators to provide wider coverage in special areas. 59 PS QoS PS QoS refers to GPRS/EGPRS QoS, that is, the quality of GPRS/EGPRS services on radio access network. The requirements for PS QoS are defined by QoS attributes, including the traffic class, transfer delay, maximum bit rate (MBR), guaranteed bit rate (GBR), traffic handling priority (THP), allocation/retention priority (ARP), and reliability. 60 Configuring Half-Rate Half-rate indicates that the voice coding rate decreases by half based on the new coding algorithm. In this way, a physical channel can carry the services of two half-rate MSs instead of the services of a full-rate MS. 61 Configuring MS High Multislot Classes The function of MS high multislot classes enables the allocation of a maximum of five uplink/ downlink timeslots to an MS, thus increasing the uplink/downlink throughput of an MS. 62 Configuring Extended Dynamic Allocation(EDA) The EDA function enables the allocation of more uplink timeslots to an MS, thus increasing the uplink throughput. 63 Configuring CS-3/CS-4 The CS-3/CS-4 function enables the BSC to automatically adjust the coding scheme to a higher one in the area with a low bit error rate based on the existing coding scheme of a GPRS MS and the transmission quality of the MS. In this manner, a higher throughput is provided. 64 Configuring Network Operation Mode I
Issue 01 (2010-05-20) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xi
About This Document
The function of network operation mode I enables the sending of the CS paging messages over PCCCHs, CCCHs, or PACCHs on the network side. The MS monitors only one paging channel. 65 Configuring Pre-Processing of Measurement Report The function of pre-processing of measurement report enables the BTS to interpolate and filter measurement reports (MRs) and then report the results of the processed MRs to the BSC. In this manner, the BSC does not need to process the MRs, thus reducing the load of the BSC. 66 Configuring Enhanced Measurement Report (EMR) The EMR is the downlink measurement report (MR) of a new type introduced in R99. Compared with the common MR, more measurement objects such as bit error probability (BEP) and frame erase ratio (FER) are included. In this manner, the performance of the power control algorithm and handover algorithm is improved. 67 Configuring Automatic Frequency Correction(AFC) The automatic frequency correction (AFC) function uses a special balancing algorithm to estimate the difference between the standard frequency and the frequency of the GMSK signal sent from the fast-moving MS to the BTS. The AFC estimates the frequency offset between the frequency of each received burst and the standard frequency in real time. Then, the estimated frequency offset is used to correct the RX working frequency of the BTS. 68 Configuring Handover The service area of the GSM is composed of the cells with continuous coverage. To enable the subscribers to communicate without interruption and to optimize the network performance, the handover technique is introduced to the GSM system. 69 Configuring Flex Ater With the Flex Ater function, the Ater resources are allocated according to the service type during a call connection. If full-rate channels are used over the Um interface, the 16 kbit/s Ater resources are allocated. If half-rate channels are used over the Um interface, the 8 kbit/s Ater resources are allocated. 70 Configuring Abis Transmission Backup When the active SDH transmission link is faulty due to a natural disaster, the GBSS automatically switches the terrestrial TDM transmission link on the Abis interface to a backup satellite transmission link, thus maintaining the normal operation of the network. 71 Configuring End-to-End MS Signaling Tracing The function of end-to-end MS signaling tracing enables the tracing of faults of an NE based on the collected information about specified users with only a small number of resources occupied, thus facilitating fault rectification. 72 Configuring PDCH Dynamic Adjustment The function of PDCH dynamic adjustment enables the automatic conversion between TCHs and PDCHs as required instead of configuring fixed PDCHs. 73 Configuring 14.4 Kbps Circuit Switched Data Huawei GBSS supports the use of a single CS channel for transmitting PS services, including the 14.4 kbps CSD services.
xii Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2010-05-20)
About This Document
Conventions
Symbol Conventions The symbols that may be found in this document are defined as follows. Symbol Description Indicates a hazard with a high level of risk, which if not avoided,will result in death or serious injury. Indicates a hazard with a medium or low level of risk, which if not avoided, could result in minor or moderate injury. Indicates a potentially hazardous situation, which if not avoided,could result in equipment damage, data loss, performance degradation, or unexpected results. Indicates a tip that may help you solve a problem or save time. Provides additional information to emphasize or supplement important points of the main text.
General Conventions The general conventions that may be found in this document are defined as follows. Convention Times New Roman Boldface Italic Courier New Description Normal paragraphs are in Times New Roman. Names of files, directories, folders, and users are in boldface. For example, log in as user root. Book titles are in italics. Examples of information displayed on the screen are in Courier New.
Command Conventions The command conventions that may be found in this document are defined as follows. Convention Boldface Italic []
Issue 01 (2010-05-20)
Description The keywords of a command line are in boldface. Command arguments are in italics. Items (keywords or arguments) in brackets [ ] are optional.
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xiii
About This Document
Convention { x | y | ... } [ x | y | ... ] { x | y | ... }*
Description Optional items are grouped in braces and separated by vertical bars. One item is selected. Optional items are grouped in brackets and separated by vertical bars. One item is selected or no item is selected. Optional items are grouped in braces and separated by vertical bars. A minimum of one item or a maximum of all items can be selected. Optional items are grouped in brackets and separated by vertical bars. Several items or no item can be selected.
[ x | y | ... ]*
GUI Conventions The GUI conventions that may be found in this document are defined as follows. Convention Boldface > Description Buttons, menus, parameters, tabs, window, and dialog titles are in boldface. For example, click OK. Multi-level menus are in boldface and separated by the ">" signs. For example, choose File > Create > Folder.
Keyboard Operations The keyboard operations that may be found in this document are defined as follows. Format Key Key 1+Key 2 Key 1, Key 2 Description Press the key. For example, press Enter and press Tab. Press the keys concurrently. For example, pressing Ctrl+Alt +A means the three keys should be pressed concurrently. Press the keys in turn. For example, pressing Alt, A means the two keys should be pressed in turn.
Mouse Operations The mouse operations that may be found in this document are defined as follows. Action Click Description Select and release the primary mouse button without moving the pointer.
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2010-05-20)
xiv
About This Document
Action Double-click Drag
Description Press the primary mouse button twice continuously and quickly without moving the pointer. Press and hold the primary mouse button and move the pointer to a certain position.
Issue 01 (2010-05-20)
xv
Contents
Contents
About This Document...................................................................................................................iii 1 Changes in BSS Feature Configuration Guide (Based on MML).....................................1-1 2 Configuring the Multiband Network....................................................................................2-1
2.1 Configuring a Multiband Network..................................................................................................................2-2 2.2 Configuring an Enhanced Dual-Band Network..............................................................................................2-6
3 Configuring the Speech Version.............................................................................................3-1 4 Configuring ALC........................................................................................................................4-1 5 Configuring Acoustic Echo Cancellation..............................................................................5-1 6 Configuring Cell Broadcast......................................................................................................6-1
6.1 Configuring Cell Broadcast.............................................................................................................................6-2 6.2 Configuring Simplified Cell Broadcast...........................................................................................................6-7
7 Configuring Ciphering.............................................................................................................7-1 8 Configuring Frequency Hopping............................................................................................8-1

8.1 Principles of Configuring the FH Cell............................................................................................................8-3 8.2 Changing None FH to RF FH.........................................................................................................................8-5 8.3 Changing None FH to Baseband FH...............................................................................................................8-6 8.4 Changing RF FH to Baseband FH...................................................................................................................8-7 8.5 Changing Baseband FH to RF FH...................................................................................................................8-8 8.6 Changing RF FH to None FH.........................................................................................................................8-9 8.7 Changing Baseband FH to None FH.............................................................................................................8-10 8.8 Setting FH Mode to Hybrid FH.....................................................................................................................8-10 8.9 Changing Hybrid FH to None FH.................................................................................................................8-12 8.10 Configuring MA Group...............................................................................................................................8-13
9 Configuring eMLPP...................................................................................................................9-1 10 Configuring Priority-Based Resource Reservation.........................................................10-1 11 Configuring Network Support SAIC.................................................................................11-1 12 Configuring Active Power Control.....................................................................................12-1 13 Configuring Robust Air Interface Signalling...................................................................13-1
Issue 01 (2010-05-20) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xvii
Contents
14 Configuring BSS Paging Coordination.............................................................................14-1 15 Configuring a Co-BCCH Cell..............................................................................................15-1

15.1 Co-BCCH Cell Configuration Principles....................................................................................................15-2 15.2 Preparations for the Co-BCCH Cell Configuration....................................................................................15-2 15.3 Configuring a Co-BCCH Cell.....................................................................................................................15-3
16 Configuring 2G/3G Interoperability..................................................................................16-1 17 Configuring TRX Cooperation............................................................................................17-1 18 Configuring Cell Frequency Scan.......................................................................................18-1 19 Configuring High-Speed Signaling Links........................................................................19-1 20 Configuring Local Multiple Signaling Points..................................................................20-1 21 Configuring DTX and DRX..................................................................................................21-1
21.1 Configuring DTX........................................................................................................................................21-2 21.2 Configuring DRX........................................................................................................................................21-7
22 Configuring Location Service..............................................................................................22-1

22.1 Configuring Location Service.....................................................................................................................22-2 22.2 Configuring Simple Location Service.........................................................................................................22-3
23 Configuring TFO....................................................................................................................23-1 24 Configuring PBT....................................................................................................................24-1

24.1 Installing Hardware (PBT)..........................................................................................................................24-2 24.2 Configuring PBT.........................................................................................................................................24-4 24.3 Configuring Dynamic PBT.........................................................................................................................24-5
25 Configuring Transmit Diversity.........................................................................................25-1

25.1 Installing Hardware (Transmit Diversity)...................................................................................................25-2 25.2 Configuring Transmit Diversity..................................................................................................................25-6 25.3 Configuring Dynamic Transmit Diversity..................................................................................................25-8
26 Configuring 4-Way Receive Diversity...............................................................................26-1

26.1 Installing Hardware (4-Way Receive Diversity).........................................................................................26-2 26.2 Configuring 4-Way Receive Diversity........................................................................................................26-5
27 Configuring SDCCH Dynamic Adjustment.....................................................................27-1 28 Configuring NACC................................................................................................................28-1 29 Configuring NC2....................................................................................................................29-1 30 Configuring Packet Performance Improvement..............................................................30-1 31 Configuring Flex Abis...........................................................................................................31-1
31.1 Configuring Flex Abis.................................................................................................................................31-2 31.2 Configuring Exclusive Timeslot.................................................................................................................31-7 xviii Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2010-05-20)
Contents
32 Configuring the MSC Pool...................................................................................................32-1

32.1 Configuring MSC Pool (A over TDM).......................................................................................................32-2 32.2 Configuring the MSC Pool (A over IP)...................................................................................................... 32-4
33 Configuring BTS Ring Topology........................................................................................33-1

33.1 Configuring BTS Ring Topology................................................................................................................33-2 33.2 Changing Non-Ring Topology to Ring Topology...................................................................................... 33-5 33.3 Querying BTS Ring Topology....................................................................................................................33-6 33.4 Deleting a BTS from the Ring Topology....................................................................................................33-7 33.5 Manually Switching over BTS Ring Topology...........................................................................................33-8
34 Configuring APS....................................................................................................................34-1 35 Configuring BSC Local Switching......................................................................................35-1 36 Configuring BTS Local Switching......................................................................................36-1 37 Configuring Dynamic MAIO..............................................................................................37-1
37.1 Precautions for Configuring Dynamic MAIO.............................................................................................37-2 37.2 Configuring Dynamic MAIO......................................................................................................................37-2
38 Configuring Antenna Hopping...........................................................................................38-1 39 Configuring Voice Quality Index.......................................................................................39-1 40 Configuring ANR...................................................................................................................40-1 41 Intelligent Power Consumption Decrease........................................................................41-1
41.1 Configuring TRX Power Amplifier Intelligent Shutdown..........................................................................41-3 41.2 Configuring Intelligent Combiner Bypass.................................................................................................. 41-6 41.3 Configuring PSU Smart Control.................................................................................................................41-8 41.4 Configuring Power Optimization Based on Channel Type.........................................................................41-9 41.5 Configuring Enhanced BCCH Power Consumption Optimization...........................................................41-10 41.6 Configuring Active Backup Power Control..............................................................................................41-12 41.7 Configuring Multi-Carrier Intelligent Voltage Regulation.......................................................................41-14 41.8 Configuring TRX Working Voltage Adjustment......................................................................................41-16
42 Configuring Tight BCCH Frequency Reuse.....................................................................42-1 43 Configuring Connection Inter BSC over IP......................................................................43-1 44 Managing a BSC Soft-Synchronized Network Task.......................................................44-1
44.1 Concepts Related to the Soft-Synchronized Network.................................................................................44-3 44.2 Creating an Intra-BSC Soft-Synchronized Network Task..........................................................................44-3 44.3 Configuring a Pair of Neighboring Cells of Intra-BSC Soft-Synchronized Network Task........................44-5 44.4 Verifying an Intra-BSC Soft-Synchronized Network Task........................................................................ 44-7 44.5 Creating an Inter-BSC Soft-Synchronized Network Task..........................................................................44-7 44.6 Verifying an Inter-BSC Soft-Synchronized Network Task......................................................................44-11 44.7 Collecting the Offset Information Between BTSs....................................................................................44-12 44.8 Synchronizing BTSs..................................................................................................................................44-15 Issue 01 (2010-05-20) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xix
Contents
44.9 Deleting a Soft-Synchronized Network Task............................................................................................44-16
45 Configuring Entire Network Synchronization.................................................................45-1 46 Configuring BSS IP Transmission......................................................................................46-1

46.1 A over IP Configuration Data.....................................................................................................................46-2 46.2 Abis over IP Configuration Data.................................................................................................................46-6 46.3 Gb over IP Configuration Data.................................................................................................................46-12 46.4 Configuring A over IP...............................................................................................................................46-16 46.5 Configuring Abis over IP..........................................................................................................................46-21 46.6 Configuring Gb over IP.............................................................................................................................46-27
47 Configuring Abis Transmission Optimization or HubBTS..........................................47-1 48 Configuring SGSN Pool.......................................................................................................48-1 49 Configuring RAN Sharing...................................................................................................49-1
49.1 Configuring Operator Information..............................................................................................................49-3 49.2 Configuring BTS Sharing............................................................................................................................49-4 49.3 Binding the Cell and the Operator...............................................................................................................49-5 49.4 Binding the MSC and Operator...................................................................................................................49-6 49.5 Binding the SGSN and Operator.................................................................................................................49-7 49.6 Binding the PCU and Operator...................................................................................................................49-7 49.7 Configuring RAN Sharing to Support Multiple CBCs...............................................................................49-8 49.8 Configuring the Distributed BTS TRX to Support RAN Sharing............................................................49-10 49.9 Verifying and Deactivating RAN Sharing................................................................................................49-11
50 Configuring Multi-site Cell.................................................................................................50-1

50.1 Adding a Location Group............................................................................................................................50-2 50.2 Configuring Parameters of Location Groups..............................................................................................50-3 50.3 Verifying Configuration Information About Location Group....................................................................50-4 50.4 Deleting a Location Group..........................................................................................................................50-5 50.5 Setting Binding Relations of Location Groups...........................................................................................50-5 50.6 Deleting Binding Relations of Location Groups.........................................................................................50-7
51 Configuring IBCA..................................................................................................................51-1
51.1 Configuration Principles of IBCA...............................................................................................................51-4 51.2 Data Negotiated and Planned for Configuring IBCA.................................................................................51-4 51.3 Configuring IBCA.......................................................................................................................................51-8 51.4 Configuring the IBCA Cell that Supports HWIII Power Control Algorithm...........................................51-10 51.5 Configuring the Cell that Enables the IBCA Algorithm Switch...............................................................51-11 51.6 Configuring an IBCA Neighboring Cell...................................................................................................51-12 51.7 Configuring the BTS Synchronization Mode............................................................................................51-13 51.8 Configuring External Attributes of the BSC.............................................................................................51-14 51.9 Binding the external BSC and the External Cell.......................................................................................51-15 51.10 Deactivating IBCA..................................................................................................................................51-16
xx
Issue 01 (2010-05-20)
Contents
52 Configuring BTS in automatic planning mode................................................................52-1

52.1 Adding the BTS3900B GSM...................................................................................................................... 52-2 52.2 Adding the BTS3900E GSM.......................................................................................................................52-4
53 Configure DTM......................................................................................................................53-1 54 Configuring VGCS/VBS.......................................................................................................54-1 55 Configuring AMR..................................................................................................................55-1 56 Configuring Dynamically Adjusting the Uplink MCS Coding...................................56-1 57 Configuring Concentric Cell................................................................................................57-1 58 Configuring Extended Cell..................................................................................................58-1 59 PS QoS......................................................................................................................................59-1
59.1 Configuring Streaming QoS(GBR).............................................................................................................59-2 59.2 Configuring QoS ARP and THP.................................................................................................................59-3 59.3 Configuring PS Active Package Management............................................................................................59-5 59.4 Configuring PoC QoS................................................................................................................................. 59-6
60 Configuring Half-Rate..........................................................................................................60-1 61 Configuring MS High Multislot Classes...........................................................................61-1 62 Configuring Extended Dynamic Allocation(EDA)..........................................................62-1 63 Configuring CS-3/CS-4..........................................................................................................63-1 64 Configuring Network Operation Mode I..........................................................................64-1 65 Configuring Pre-Processing of Measurement Report.....................................................65-1 66 Configuring Enhanced Measurement Report (EMR)......................................................66-1 67 Configuring Automatic Frequency Correction(AFC)......................................................67-1 68 Configuring Handover..........................................................................................................68-1
68.1 Configuring Basic Handover.......................................................................................................................68-3 68.2 Configuring PBGT Handover..................................................................................................................... 68-7 68.3 Configuring Signal Level Rapid Fall Handover......................................................................................... 68-8 68.4 Configuring Load Handover....................................................................................................................... 68-9 68.5 Configuring Layered and Hierarchical Handover.....................................................................................68-11 68.6 Configuring Speed-Sensitive Handover....................................................................................................68-13 68.7 Configuring Directed Retry.......................................................................................................................68-14 68.8 Configuring Chain Cell Handover............................................................................................................68-15 68.9 Configuring Better Cell Handover............................................................................................................68-17
69 Configuring Flex Ater............................................................................................................69-1 70 Configuring Abis Transmission Backup...........................................................................70-1 71 Configuring End-to-End MS Signaling Tracing..............................................................71-1
Issue 01 (2010-05-20) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xxi
Contents
72 Configuring PDCH Dynamic Adjustment........................................................................72-1 73 Configuring 14.4 Kbps Circuit Switched Data.................................................................73-1
xxii
Issue 01 (2010-05-20)
Figures
Figures
Figure 6-1 Trace RSL Message on the Abis Interface dialog box.......................................................................6-6 Figure 6-2 Tracing the RSL Message at Abis Interface.......................................................................................6-6 Figure 6-3 Trace RSL Message on the Abis Interface dialog box.....................................................................6-11 Figure 6-4 Trace the RSL Message at Abis Interface dialog box......................................................................6-11 Figure 24-1 Connections between the DTRU and the DDPU in PBT mode.....................................................24-3 Figure 25-1 Cable connections between the DTRU and the DDPU in the BTS3012/BTS3012AE in transmit diversity mode.....................................................................................................................................................25-3 Figure 25-2 Cable connections between the DDPM and the DDRM in the BTS3006C in transmit diversity mode. .............................................................................................................................................................................25-4 Figure 25-3 Cable connections between the DDPM and the DDRM in the BTS3002E in transmit diversity mode .............................................................................................................................................................................25-5 Figure 25-4 Cable connections in the DBS3900 GSM in transmit diversity mode...........................................25-6 Figure 26-1 Connection between the DTRU and the DDPU in 4-way receive diversity mode.........................26-3 Figure 31-1 Configuration of BTS combined cabinets and cabinet groups.......................................................31-4 Figure 39-1 Trace User Message dialog box......................................................................................................39-2 Figure 39-2 Result of the user message tracing..................................................................................................39-3 Figure 39-3 Message Browser window..............................................................................................................39-4
Issue 01 (2010-05-20)
xxiii
Tables
Tables
Table 2-1 Example of the data negotiated and planned for configuring a multiband network............................2-2 Table 2-2 Example of the data negotiated and planned for adding the GSM900 cell or GSM1800 cell.............2-3 Table 2-3 Example of the data configuring cell idle parameters or cell handover parameters............................2-4 Table 2-4 Example of the data negotiated and planned for configuring an enhanced dual-band network..........2-6 Table 3-1 Example of the data negotiated and planned for configuring the EFR/AMR/HR...............................3-1 Table 4-1 Example of the data negotiated and planned for configuring ALC.....................................................4-1 Table 5-1 Example of the data negotiated and planned for configuring AEC.....................................................5-1 Table 6-1 Example of the data negotiated and planned for configuring cell broadcast.......................................6-2 Table 6-2 Example of the data negotiated and planned for configuring simplified cell broadcast......................6-7 Table 7-1 Example of the data negotiated and planned for configuring ciphering..............................................7-1 Table 8-1 Example of the data negotiated and planned for changing none FH to RF FH...................................8-5 Table 8-2 Example of the data negotiated and planned for changing none FH to baseband FH.........................8-6 Table 8-3 Example of the data negotiated and planned for changing RF FH to none FH...................................8-9 Table 8-4 Example of the data negotiated and planned for changing baseband FH to none FH.......................8-10 Table 8-5 Example of the data negotiated and planned for changing the FH mode of a cell from none FH to hybrid FH........................................................................................................................................................................8-11 Table 8-6 Example of the data negotiated and planned for changing hybrid FH to none FH............................8-13 Table 8-7 Example of the data negotiated and planned for configuring the MA group.....................................8-14 Table 9-1 Example of the data negotiated and planned for adding a BTS...........................................................9-1 Table 9-2 Example of the data negotiated and planned for configuring eMLPP.................................................9-3 Table 10-1 Example of the data negotiated and planned for configuring priority-based resource reservation .............................................................................................................................................................................10-1 Table 11-1 Example of the data negotiated and planned for configuring the Network Support SAIC..............11-2 Table 12-1 Example of the data negotiated and planned for configuring the active power control...................12-1 Table 13-1 Example of the data negotiated and planned for configuring the robust air interface signalling function .............................................................................................................................................................................13-1 Table 14-1 Example of the data negotiated and planned for configuring the BSS paging coordination function .............................................................................................................................................................................14-1 Table 15-1 Example of the data negotiated and planned for configuring a co-BCCH cell................................15-4 Table 16-1 Example of the data negotiated and planned for configuring the GSM/TD-SCDMA Interoperability .............................................................................................................................................................................16-2 Table 17-1 Example of the data negotiated and planned for adding a BTS.......................................................17-1 Table 17-2 Example of the data negotiated and planned for configuring TRX Cooperation.............................17-3 Table 18-1 Example of the data negotiated and planned for configuring cell frequency scan..........................18-1 Issue 01 (2010-05-20) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xxv
Tables
HUAWEI BSC6000 Base Station Controller BSS Feature Configuration Guide(Based on MML) Table 19-1 Example of the data negotiated and planned for configuring high-speed signaling links in BM/TC combined mode...................................................................................................................................................19-1 Table 19-2 Example of the data negotiated and planned for configuring high-speed signaling links in BM/TC separate mode......................................................................................................................................................19-2 Table 20-1 Example of the data negotiated and planned for configuring the mapping between the first OPC and the subrack...........................................................................................................................................................20-1 Table 20-2 Example of the data negotiated and planned for configuring the mapping between the Second OPC and the subrack...........................................................................................................................................................20-2 Table 20-3 Example of the data negotiated and planned for configuring DPC..................................................20-2 Table 21-1 Example of the data negotiated and planned for adding a BTS.......................................................21-2 Table 21-2 Example of the data negotiated and planned for configuring DTX.................................................21-4 Table 21-3 Example of the data negotiated and planned for adding a BTS.......................................................21-7 Table 21-4 Example of the data negotiated and planned for configuring DTX.................................................21-9 Table 22-1 Example of the data negotiated and planned for configuring LCS..................................................22-2 Table 22-2 Example of the data negotiated and planned for configuring simple location service....................22-4 Table 23-1 Example of the data negotiated and planned for configuring TFO..................................................23-2 Table 24-1 Example of the data negotiated and planned for configuring PBT..................................................24-4 Table 24-2 Example of the data negotiated and planned for configuring dynamic PBT...................................24-6 Table 25-1 Example of the data negotiated and planned for configuring transmit diversity.............................25-7 Table 25-2 Example of the data negotiated and planned for configuring transmit diversity.............................25-8 Table 26-1 Description of ports on the DTRU...................................................................................................26-3 Table 26-2 Description of ports on the DDPU...................................................................................................26-4 Table 26-3 Example of the data negotiated and planned for configuring 4-way receive diversity....................26-5 Table 27-1 Example of the data negotiated and planned for configuring SDCCH dynamic adjustment...........27-1 Table 28-1 Example of the data negotiated and planned for configuring NACC..............................................28-1 Table 29-1 Example of the data negotiated and planned for configuring NC2..................................................29-1 Table 31-1 Example of the data negotiated and planned for configuring Flex Abis..........................................31-4 Table 31-2 Example of the data negotiated and planned for configuring exclusive timeslots...........................31-7 Table 32-1 Example of the data negotiated and planned for configuring MSC Pool in A over TDM...............32-2 Table 32-2 Example of the data negotiated and planned for configuring links on the A interface....................32-5 Table 32-3 Example of the data negotiated and planned for configuring MSC Pool in A over IP....................32-6 Table 33-1 Example of the data negotiated and planned for configuring BTS ring topology...........................33-3 Table 33-2 Example of the data negotiated and planned for changing non-ring topology to ring topology .............................................................................................................................................................................33-6 Table 34-1 Example of the data negotiated and planned for configuring APS.................................................34-2 Table 35-1 Example of the data negotiated and planned for configuring BSC local switching........................35-2 Table 36-1 Example of the data negotiated and planned for adding a BTS.......................................................36-2 Table 36-2 Example of the data negotiated and planned for configuring BTS local switching.........................36-3 Table 37-1 Example of the data negotiated and planned for configuring dynamic MAIO................................37-3 Table 38-1 Example of the data negotiated and planned for configuring antenna hopping...............................38-2 Table 39-1 Example of the data negotiated and planned for configuring VQI..................................................39-1 Table 40-1 Example of the data negotiated and planned for configuring ANR.................................................40-1 Table 41-1 Example of the data negotiated and planned for configuring intelligent power consumption reduction .............................................................................................................................................................................41-4
xxvi
Issue 01 (2010-05-20)
Tables
Table 41-2 Example of Configuring the Intelligent Combiner Bypass..............................................................41-7 Table 41-3 Example of configuring PSU Smart Control...................................................................................41-8 Table 41-4 Example of the configuring the Power Optimization Based on Channel Type.............................41-10 Table 41-5 Example of the configuring the Enhanced BCCH Power Consumption Optimization.................41-11 Table 41-6 Example of the configuring the Active Backup Power Control.....................................................41-13 Table 41-7 Example of the configuring the Multi-Carrier Intelligent Voltage Regulation..............................41-15 Table 41-8 Example of the TRX Working Voltage Adjustment......................................................................41-16 Table 42-1 Example of the data negotiated and planned for adding a BTS.......................................................42-1 Table 42-2 Example of the data negotiated and planned for configuring tight BCCH frequency reuse............42-3 Table 43-1 Example of the data negotiated and planned for Configuring Inter-BSC Signaling Links..............43-1 Table 44-1 Example of the data negotiated and planned for setting the BTS synchronization zone.................44-4 Table 44-2 Example of the data negotiated and planned for creating an intra-BSC soft-synchronized network task .............................................................................................................................................................................44-4 Table 44-3 Example of the data negotiated and planned for creating an intra-BSC soft-synchronized network task .............................................................................................................................................................................44-6 Table 44-4 Example of the data negotiated and planned for setting the BTS synchronization zone.................44-8 Table 44-5 Example of the data negotiated and planned for creating an inter-BSC soft-synchronized network .............................................................................................................................................................................44-8 Table 44-6 Example of the data negotiated and planned for configuring the cell that creates the inter-BSC softsynchronized network task..................................................................................................................................44-9 Table 44-7 Example of the data negotiated and planned for collecting the intra-BSC offset information between BTSs..................................................................................................................................................................44-13 Table 44-8 Example of the data negotiated and planned for collecting the inter-BSC offset information between BTSs..................................................................................................................................................................44-14 Table 44-9 Example of the data negotiated and planned for synchronizing the BTSs.....................................44-15 Table 45-1 Example of the data negotiated and planned for configuring the USCU.........................................45-1 Table 45-2 Example of the data negotiated and planned for configuring the system clock source...................45-2 Table 46-1 Example of the data negotiated and planned for configuring system clock.....................................46-2 Table 46-2 Example of the data negotiated and planned for configuring 8K reference clock for the GMPS and GEPS...................................................................................................................................................................46-2 Table 46-3 Example of the data negotiated and planned for configuring the M3AU entity..............................46-2 Table 46-4 Example of the data negotiated and planned for configuring the signaling point for the GMPS .............................................................................................................................................................................46-3 Table 46-5 Example of the data negotiated and planned for configuring the GFGUA......................................46-3 Table 46-6 Example of the data negotiated and planned for configuring the A interface link..........................46-4 Table 46-7 Example of the data negotiated and planned for configuring the BFD detection over the A interface .............................................................................................................................................................................46-4 Table 46-8 Example of the data negotiated and planned for configuring the QoS mechanism over the A interface .............................................................................................................................................................................46-5 Table 46-9 Example of the data negotiated and planned for configuring the GFGUB......................................46-6 Table 46-10 Example of the data negotiated and planned for configuring the BFD link detection over the Abis interface...............................................................................................................................................................46-7 Table 46-11 Example of the data negotiated and planned for configuring Clock over IP.................................46-8 Table 46-12 Example of the data negotiated and planned for configuring QoS for the Abis interface.............46-8
Issue 01 (2010-05-20)
xxvii
Tables
HUAWEI BSC6000 Base Station Controller BSS Feature Configuration Guide(Based on MML) Table 46-13 Example of the data negotiated and planned for configuring IP PATH for the Abis interface ...........................................................................................................................................................................46-10 Table 46-14 Example of the data negotiated and planned for configuring ABIS MUX..................................46-11 Table 46-15 Example of the data negotiated and planned for configuring LAPD...........................................46-11 Table 46-16 Example of the data negotiated and planned for configuring IP PM...........................................46-12 Table 46-17 Example of the data negotiated and planned for setting the BTS Ping Switch to Off.................46-12 Table 46-18 Example of the data negotiated and planned for configuring the GDPUP..................................46-12 Table 46-19 Example of the data negotiated and planned for configuring the GFGUG..................................46-13 Table 46-20 Example of the data negotiated and planned for configuring the SGSN.....................................46-14 Table 46-21 Example of the data negotiated and planned for configuring the BFD link detection over the Gb interface.............................................................................................................................................................46-15 Table 46-22 Example of the data negotiated and planned for configuring traffic shaping over the Gb interface and congestion management....................................................................................................................................46-15 Table 47-1 Example of the data negotiated and planned for configuring HDLC_HubBTS service mode for BTS3012..............................................................................................................................................................47-2 Table 48-1 Example of the data negotiated and planned for configuring SGSN pool.......................................48-1 Table 48-2 Example of the data negotiated and planned for adding the first SGSN..........................................48-2 Table 48-3 Example of the data negotiated and planned for adding the second SGSN.....................................48-3 Table 49-1 Example of the data negotiated and planned for configuring the primary operator information .............................................................................................................................................................................49-3 Table 49-2 Example of the data negotiated and planned for configuring the secondary operator information .............................................................................................................................................................................49-3 Table 49-3 Example of the data negotiated and planned for configuring BTS sharing.....................................49-4 Table 49-4 Example of the data negotiated and planned for binding the cell and operator...............................49-5 Table 49-5 Example of the data negotiated and planned for binding the MSC and operator............................49-6 Table 49-6 Example of the data negotiated and planned for binding the PCU and operator.............................49-8 Table 49-7 Example of the data negotiated and planned for configuring RAN sharing to support multiple CBCs .............................................................................................................................................................................49-9 Table 49-8 Example of the data negotiated and planned for configuring the distributed BTS TRX to support RAN sharing...............................................................................................................................................................49-10 Table 50-1 Example of the data negotiated and planned for adding a location group.......................................50-2 Table 50-2 Example of the data negotiated and planned for configuring parameters of the BTS.....................50-3 Table 50-3 Example of data negotiated and planned for setting binding relations of location groups..............50-6 Table 51-1 Example of the data negotiated and planned for configuring the GXPUI.......................................51-5 Table 51-2 Example of the data negotiated and planned for configuring the GFGUB......................................51-5 Table 51-3 Example of the data negotiated and planned for configuring an FH cell.........................................51-5 Table 51-4 Example of the data negotiated and planned for enabling Huawei III power control algorithm in a cell .............................................................................................................................................................................51-6 Table 51-5 Example of the data negotiated and planned for enabling the IBCA algorithm in a cell.................51-7 Table 51-6 Example of the data negotiated and planned for configuring an internal IBCA neighboring cell .............................................................................................................................................................................51-7 Table 51-7 Example of the data negotiated and planned for configuring the BTS synchronization method .............................................................................................................................................................................51-7 Table 51-8 Example of the data negotiated and planned for configuring an external IBCA neighboring cell .............................................................................................................................................................................51-8
xxviii
Issue 01 (2010-05-20)
Tables
Table 51-9 Example of the data negotiated and planned for configuring the cell that supports HWIII power control algorithm...........................................................................................................................................................51-11 Table 51-10 Example of the data negotiated and planned for configuring the cell that enables the IBCA algorithm switch................................................................................................................................................................ 51-12 Table 51-11 Example of the data negotiated and planned for configuring an IBCA neighboring cell............51-13 Table 51-12 Example of the data negotiated and planned for configuring the BTS synchronization mode ...........................................................................................................................................................................51-14 Table 51-13 Example of the data negotiated and planned for adding external attributes of the BSC..............51-15 Table 52-1 Example of the data negotiated and planned for adding the BTS3900B GSM................................52-2 Table 52-2 Example of the data negotiated and planned for adding the BTS3900E GSM in TDM networking mode .............................................................................................................................................................................52-5 Table 52-3 Example of the data negotiated and planned for adding the BTS3900E GSM in HDLC/HUB networking mode....................................................................................................................................................................52-6 Table 52-4 Example of the data negotiated and planned for adding the BTS3900E GSM in IP networking mode .............................................................................................................................................................................52-6 Table 53-1 Example of the negotiated and planned data for configuring the DTM...........................................53-2 Table 54-1 Example of the data negotiated and planned for configuring the VGCS/VBS................................54-1 Table 55-1 Example of the data negotiated and planned for configuring AMR...............................................55-1 Table 56-1 Example of the configuring dynamically adjusting the uplink MCS coding...................................56-1 Table 57-1 Example of the configuring concentric cell.....................................................................................57-1 Table 58-1 Example of the configuring extended cell........................................................................................58-1 Table 59-1 Example of the configuring streaming QoS(GBR)..........................................................................59-2 Table 59-2 Example of the configuring QoS ARP and THP.............................................................................59-4 Table 59-3 Example of the configuring PS active package management..........................................................59-5 Table 59-4 Example of the configuring PoC QoS..............................................................................................59-7 Table 60-1 Example of the configuring Half-Rate.............................................................................................60-1 Table 61-1 Example of the data negotiated and planned for configuring MS high multislot classes................61-1 Table 62-1 Example of the data negotiated and planned for configuring EDA.................................................62-1 Table 63-1 Example of the data negotiated and planned for configuring CS-3/CS-4........................................63-1 Table 64-1 Example of the data negotiated and planned for configuring network operation mode I................64-1 Table 65-1 Example of the data negotiated and planned for configuring the function of pre-processing of measurement report.............................................................................................................................................65-1 Table 66-1 Example of the data negotiated and planned for configuring EMR.................................................66-1 Table 67-1 Example of the data negotiated and planned for configuring AFC..................................................67-1 Table 68-1 Example of the data negotiated and planned for configuring basic handover.................................68-3 Table 68-2 Example of the data negotiated and planned for configuring PBGT handover...............................68-7 Table 68-3 Example of data negotiated and planned for configuring signal level rapid fall handover.............68-9 Table 68-4 Example of the data negotiated and planned for configuring load handover.................................68-10 Table 68-5 Example of the data negotiated and planned for configuring layered and hierarchical handover ...........................................................................................................................................................................68-12 Table 68-6 Example of the data negotiated and planned for configuring speed-sensitive handover...............68-13 Table 68-7 Example of the data negotiated and planned for configuring directed retry..................................68-15 Table 68-8 Example of the data negotiated and planned for configuring chain cell handover........................68-16 Table 68-9 Example of the data negotiated and planned for configuring better cell handover........................68-18 Issue 01 (2010-05-20) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xxix
Tables
HUAWEI BSC6000 Base Station Controller BSS Feature Configuration Guide(Based on MML) Table 69-1 Example of the data negotiated and planned for configuring Flex Ater..........................................69-1 Table 70-1 Example of the data negotiated and planned for configuring Abis transmission backup................70-1 Table 71-1 Example of the data negotiated and planned for configuring end-to-end MS signaling tracing .............................................................................................................................................................................71-1 Table 72-1 Example of the data negotiated and planned for configuring PDCH dynamic adjustment.............72-1 Table 73-1 Example of the data negotiated and planned for configuring 14.4 Kbps circuit switched data.......73-1
xxx
Issue 01 (2010-05-20)
1 Changes in BSS Feature Configuration Guide (Based on MML)
Changes in BSS Feature Configuration Guide (Based on MML)
This describes the changes in the various versions of BSS Feature Configuration Guide(Based on MML).
01(2010-05-20) of V900R008C12
This is the initial commercial release.
Issue 01 (2010-05-20)
1-1
2 Configuring the Multiband Network
2
Context
l
Configuring the Multiband Network
About This Chapter

A multiband network consists of multiple frequency bands. The combined multiband network can increase the utilization of frequency resources on the radio network.
Huawei GSM BSS supports the following types of multiband networks:

GSM850 + GSM900 + DCS1800 GSM850 + GSM900 + PCS1900
l l
The most common combination is GSM900 with DCS1800 and GSM850 with PCS1900. Huawei GSM BSS supports GSM900/DCS1800 co-BCCH cells, and does not support GSM850/PCS1900 co-BCCH cells. Huawei GSM BSS supports GSM900, DCS1800, PCS1900, and GSM850, and does not support GSM450 or GSM480.
2.1 Configuring a Multiband Network This describes how to configure a multiband network on the Local Maintenance Terminal. 2.2 Configuring an Enhanced Dual-Band Network The enhanced dual-band network is an improvement on the existing dual-band network. In the enhanced dual-band network, two co-sited cells with different coverage areas are logically formed into a cell group. One is an overlaid subcell, and the other is an underlaid subcell. The enhanced dual-band network algorithm enables channel sharing and load balancing between the two cells in a cell group. .
Issue 01 (2010-05-20)
2-1
2.1 Configuring a Multiband Network

This describes how to configure a multiband network on the Local Maintenance Terminal. Scenario Impact A multiband network is configured to increase the utilization of frequency resources on the radio network. None.
NEs Involved MS, BTS, BSC, and MSC.
Prerequisite
l
The TRXs in the BTS must support the corresponding frequency bands.
Preparation
Table 2-1 Example of the data negotiated and planned for configuring a multiband network Data Type Adding BTS Parameter ID BTSNAM E TYPE UPNODE SRN SN PN MPMODE AST ServiceMo de DCELLNA ME DCTYPE DCMCC DCMNC DCLAC DCCI
2-2
Parameter Name BTS Name BTS Type Up Node Type Subrack No. Slot No. Port No. Multiplexing Mode Activity state Service Type Source Cell Name Cell type Cell MCC Cell MNC Cell LAC Cell CI
Example BTS3012 BTS3012 BSC 0 14 0 MODE4_1 ACTIVATED (Activated) TDM cell GSM900 400 00 1 2
Source Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning
Issue 01 (2010-05-20)
Data Type
Parameter ID CPLMode TRXBN TRXTP TRXPN FREQ
Parameter Name Separate Mode TRX Board No. TRX Board Type TRX Board Path No. TRX Freq.
Example SUPPORT (Support) 0 QTRU 0 12
Source Network planning Network planning Network planning Network planning Network planning
Table 2-2 Example of the data negotiated and planned for adding the GSM900 cell or GSM1800 cell Data Type GSM900 CELL Parameter ID IDXTYPE BTSIDX CELLNA ME CTYPE AST MCC MNC LAC CI TRXBN TRXTP TRXPN2 TRXFREQ GSM1800 IDXTYPE BTSIDX Parameter Name Index Type BTS Index Source Cell Name Freq. Band Activity state MCC MNC LAC CI TRX Board No. TRX Board Type TRX Board Path No. TRX Freq. Index Type BTS Index Example BYIDX(By Index) 0 Cell_900 GSM900 ACTIVATED (Activated) 460 00 1 1 0 QTRU(QTRU) 0 70 BYIDX(By Index) 0 Source Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning
Issue 01 (2010-05-20)
2-3
Data Type
Parameter ID CELLNA ME CTYPE AST MCC MNC LAC CI TRXBN TRXFREQ
Parameter Name Source Cell Name Freq. Band Activity state MCC MNC LAC CI TRX Board No. TRX Freq.
Example Cell_1800 DCS1800 ACTIVATED (Activated) 460 00 2 3 1 512
Source Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning
Table 2-3 Example of the data configuring cell idle parameters or cell handover parameters Data Type Cell idle parameter s Parameter ID IDXTYPE CELLIDX ATT CBA CBQ PI Parameter Name Index Type Cell Index Attach-detach Allowed Cell Bar Access Cell bar qualify Cell reselect parameters indication Index Type Cell Index HO Control Switch Example BYIDX(By Index) 0 YES(Yes) YES(Yes) NO(NO) YES(Yes) Source Network planning Network planning Network planning Network planning Network planning Network planning
Cell basic Handover Parameter s
IDXTYPE CELLIDX HOCTRLS WITCH
BYIDX(By Index) 0 HOALGORITH M2(HO Algorithm II)
Network planning Network planning Network planning
2-4
Issue 01 (2010-05-20)
Procedure
Step 1 On the Local Maintenance Terminal, run the ADD BTS command to add a BTS. Step 2 On the Local Maintenance Terminal, run the ADD CELL command to add a GSM900 cell. Set Freq. Band to GSM900, and set Activity state to ACTIVATED(Activated). Step 3 On the Local Maintenance Terminal, run the ADD CELL command to add a GSM1800 cell. Set Freq. Band to DCS1800, and set Activity state to ACTIVATED(Activated). Step 4 On the Local Maintenance Terminal, run the MOD CELLIDLEBASIC command to configure cell idle parameters. Step 5 On the Local Maintenance Terminal, run the SET CELLHOBASIC command to configure cell basic handover parameters. ----End
Example
An example script for configuring a multiband network is as follows:
/*Add a BTS*/ ADD BTS: BTSNAME="bts3012", TYPE=BTS3012, UPNODE=BSC, SRN=0, SN=14, PN=0, MPMODE=MODE4_1, AST=ACTIVATED, ServiceMode=TDM, DCELLNAME="cell", DCTYPE=GSM900, DCMCC="460", DCMNC="00", DCLAC=1, DCCI=2, CPLMode=SUPPORT, TRXBN=0, TRXTP=QTRU, TRXPN=0, FREQ=12; /*Add a GSM900 cell*/ ADD CELL: IDXTYPE=BYIDX, BTSIDX=0, CELLNAME="Cell_900", CTYPE=GSM900, AST=ACTIVATED, MCC="460", MNC="00", LAC=1 , CI=1, TRXBN=0, TRXTP=QTRU, TRXPN2=0, TRXFREQ=70; /*Add a DCS1800 cell*/ ADD CELL: IDXTYPE=BYIDX, BTSIDX=0, CELLNAME="Cell_1800", CTYPE=DCS1800, AST=ACTIVATED, MCC="460", MNC="00", LAC=2, CI=3, TRXBN=1, TRXFREQ=512; /*Configure cell idle parameters*/ MOD CELLIDLEBASIC: IDXTYPE=BYIDX, CELLIDX=0, ATT=YES, CBA=YES, CBQ=NO, PI=YES; /*Configure cell basic handover parameters*/ SET CELLHOBASIC: IDXTYPE=BYIDX, CELLIDX=0, HOCTRLSWITCH=HOALGORITHM2;
Postrequisite
l
Verifying multiband network 1. 2. 3. Use an MS supporting the GSM900 frequency band to camp on a 900 MHz cell. Perform the dialing test. The call is normal. Use an MS supporting the DCS1800 frequency band to camp on a 1800 MHz cell. Perform the dialing test. The call is normal. Use an MS supporting the GSM900 and DCS1800 frequency bands to camp on a 900 MHz cell. Perform the dialing test. After the call is set up, move the MS towards the centre of the 1800 MHz cell. Then, observe the window displaying the monitored channel status. The MS is handed over to the 1800 MHz cell, and the call is still normal. This section takes the reservation of a 900 MHz cell as an example. On the Local Maintenance Terminal, run the RMV CELL command to delete other cells except for the 900 MHz cell.
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 2-5
Deactivating a multiband network 1. 2.
Issue 01 (2010-05-20)
3. 4.
Use an MS supporting the GSM900 frequency band to camp on the 900 MHz cell. Perform the dialing test. The call is normal. Use an MS supporting the DCS1800 frequency band to camp on the 900 MHz cell. The call cannot be set up.
2.2 Configuring an Enhanced Dual-Band Network

The enhanced dual-band network is an improvement on the existing dual-band network. In the enhanced dual-band network, two co-sited cells with different coverage areas are logically formed into a cell group. One is an overlaid subcell, and the other is an underlaid subcell. The enhanced dual-band network algorithm enables channel sharing and load balancing between the two cells in a cell group. . Scenario Impact On condition that the KPIs are acceptable, the resource sharing of the overlaid and underlaid subcells expands the system capacity. None.
Prerequisite
l l
The enhanced dual-band network is not license-controlled. When two cells belong to different operators, the enhanced dual-band network cannot be configured. When changing the relation between the cell and the operator, check whether the enhanced dual-band network is configured. If yes, modify the attributes of the enhanced dual-band network and change the relation between the cell and the operator. The BTS must support the frequency band to be configured. The cell must be a single band cell. That is, the frequency bands GSM900_DCS1800, GSM850_1800, or GSM850_1900 cannot be used in the cell.
l l
Preparation
Table 2-4 Example of the data negotiated and planned for configuring an enhanced dual-band network Data Type GSM900 cell configuration Parameter ID IDXTYPE BTSIDX CELLNAME CTYPE Parameter Name Index Type BTS Index Cell Name Freq. Band Example BYIDX(By Index) 0 Cell1 GSM900 Source Network planning Network planning Network planning Network planning
Issue 01 (2010-05-20)
2-6
Data Type
Parameter ID AST MCC MNC LAC CI TRXBN TRXTP TRXPN2 TRXFREQ
Parameter Name Activity state MCC MNC LAC CI TRX Board No. TRX Board Type TRX Board Path No. TRX Freq. Index Type Source Cell Name Neighbor Cell Name Current HO Control Algorithm in Source Cell Index Type Source Cell Name Neighbor Cell Name Current HO Control Algorithm in Source Cell
Example ACTIVATED (Activated) 460 00 1 1 0 QTRU(QTRU) 0 1 BYNAME (By Name) Cell1 Cell2 HOALGORITH M1(HO Algorithm I) BYNAME (By Name) Cell2 Cell1 HOALGORITH M1(HO Algorithm I)
Source Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning
Adding Cell2 to be the neighboring cell of Cell1
IDXTYPE SRCCELLN AME NBRCELLN AME HOCTRLSW ITCH
Adding Cell1 to be the neighboring cell of Cell2
IDXTYPE SRCCELLN AME NBRCELLN AME HOCTRLSW ITCH
Network planning Network planning Network planning Network planning
Issue 01 (2010-05-20)
2-7
Data Type Concentric cell type
Parameter ID IDXTYPE CELLIDX IUOTP
Parameter Name Index Type Cell Index Cell IUO Type
Example BYIDX(By Index) 0 EDB_cell (Enhanced double freq cell) Inner(Inner) BYIDX(By Index) 1
Source Network planning Network planning Network planning Network planning Network planning Network planning
CELLINEXT P DBLFREQA DJIDXTYPE DBLFREQA DJCIDX
Cell Inner/Extra Property Same Group Cell Index Type Same Group Cell Index
Procedure
Step 1 On the Local Maintenance Terminal, run the ADD CELL command to add a single band cell. Step 2 On the Local Maintenance Terminal, run the ADD CELL2GNC command to add a 2G unidirectional neighboring cell for the source cell. Step 3 On the Local Maintenance Terminal, run the ADD CELL2GNC command to add the source cell to be the neighboring cell of the 2G unidirectional neighboring cell so that the two cells are bidirectional neighboring cells with each other. Step 4 On the Local Maintenance Terminal, run the MOD CELLIUO command to set Cell IUO Type to EDB_cell(Enhanced double freq cell). Step 5 On the Local Maintenance Terminal, run the SET CELLHOEDBPARA command to Set the parameters that affect overlaid/underlaid subcell handover in enhanced dual-band network. ----End
Example
An example script for adding a single band cell is as follows:
/*Add a GSM900 cell*/ ADD CELL: IDXTYPE=BYIDX, BTSIDX=0, CELLNAME="Cell1", CTYPE=GSM900, AST=ACTIVATED, MCC="460", MNC="00", LAC=1, CI=1, TRXBN=0, TRXTP=QTRU, TRXPN2=0, TRXFREQ=1; /*Add Cell2 to be the neighboring cell of Cell1*/ ADD CELL2GNC: IDXTYPE=BYNAME, SRCCELLNAME="Cell1", NBRCELLNAME="Cell2", HOCTRLSWITCH=HOALGORITHM1; /*Add Cell1 to be the neighboring cell of Cell2*/ ADD CELL2GNC: IDXTYPE=BYNAME, SRCCELLNAME="Cell2", NBRCELLNAME="Cell1", HOCTRLSWITCH=HOALGORITHM1; /*Set the concentric type of the cell to be an enhanced dual-band cell*/ MOD CELLIUO: IDXTYPE=BYIDX, CELLIDX=0, IUOTP=EDB_cell, CELLINEXTP=Inner,
2-8
Issue 01 (2010-05-20)
DBLFREQADJIDXTYPE=BYIDX, DBLFREQADJCIDX=1;
Postrequisite
l
Verifying an enhanced dual-band network

NOTE
After the verification, the data must be restored because the data needs to be modified.
1.
On the Local Maintenance Terminal, run the MOD CELLCCBASIC command to set ECSC of the two cells to YES, and then run the MOD CELLBASICPARA command to set Directed Retry of the two cells to YES. On the Local Maintenance Terminal, run the SET CELLHOEDBPARA command to set the parameters of the GSM900 cell as follows: set UL Subcell Assignment Optimization to YES, UL Subcell Lower Load Threshold to 0, UL Subcell General Overload Threshold[%] to 1, Distance Between Boudaries of Subcells [dB] to 0, and Distance Hysteresis Between Boudaries[dB] to 0. Set Load HO Allowed and Load HO of OL Subcell to UL Subcell to NO(No). Make MS 1 and MS 2 (both supporting GSM900 and DCS1800 frequency bands) camp on the GSM900 cell. Then, use MS 1 to call a fixed-line phone. MS 1 is assigned to a channel of the GSM900 cell. Maintain the call of MS 1 and use MS 2 to call the fixed-line phone in the GSM900 cell. MS 2 is assigned to a channel of the DCS1800 cell because the load of the underlaid subcell is higher than UL Subcell General Overload Threshold[%]. This indicates that the call in the underlaid cell can be assigned to the overlaid cell when the traffic in the underlaid cell is heavy and the signals in the overlaid cell are strong enough. Stop all the calls. On the Local Maintenance Terminal, run the SET CELLHOEDBPARA command to set the parameters of the DCS1800 cell as follows: set UL Subcell Assignment Optimization to NO(No), OL Subcell Assignment Optimization to YES(Yes), UL Subcell Lower Load Threshold to 50, and UL Subcell General Overload Threshold[%] to 80. On the Local Maintenance Terminal, run the MOD CELLHOCTRL command to set Min Power Level For Directed Retry of the DCS1800 cell to 0. Make MS 1 camp on the DCS1800 cell and initiate a call. MS 1 is assigned to the underlaid GSM900 cell because the load of the underlaid cell is not higher than UL Subcell Lower Load Threshold(%). This indicates that the call in the overlaid cell can be assigned to the underlaid cell when the traffic in the underlaid cell is light. On the Local Maintenance Terminal, run the MOD CELLIUO command to set Cell IUO Type to Normal_cell(Normal cell). The adjustment of the reserved cell is complete. On the Local Maintenance Terminal, run the RMV CELL command to delete the cell on the other frequency band.
2.
3.
4.
5.
6. 7.
Deactivating an enhanced dual-band network 1.
2.
Issue 01 (2010-05-20)
2-9
3 Configuring the Speech Version
3
Scenario Impact
Configuring the Speech Version
This describes how to configure the speech version on the Local Maintenance Terminal. The speech version is configured to improve the speech quality. None.
Prerequisite
l l l l
The AMR function is license-controlled. The half rate function is license-controlled. The EFR function is not license-controlled. The license is activated on the Local Maintenance Terminal. For details, see Activate BSC License. The AMR HR supports the 7.95 kbit/s coding scheme only when Service Type of the Abis interface is IP or HDLC. In A over IP mode, the EFR function cannot be enabled forcibly. For Huawei MSC, the BSC should be configured with full-rate speech version 3, half-rate speech version 3, or both. For details, see the user manuals related to Huawei MSC.
l l
Preparation
Table 3-1 Example of the data negotiated and planned for configuring the EFR/AMR/HR Parameter ID IDXTYPE CELLIDX Parameter Name Index Type Cell Index Example BYIDX(By Index) 0 Source Network planning Network planning
Issue 01 (2010-05-20)
3-1
Parameter ID VOICEVER
Parameter Name Speech Version
Example Configuring EFR: FULL_rate_Ver2 (Full-rate Ver 2) Configuring AMR: Full_rate_Ver3(Full-rate Ver 3), Half_rate_Ver3(Half-rate Ver 3) Configuring HR: FULL_rate_Ver1 (Full-rate Ver 1)
Source Network planning
AVer
A Interface Tag
GSM_PHASE_2
Network planning
Procedure
l Configure the EFR. On the Local Maintenance Terminal, run the MOD CELLCCACCESS command to change Speech Version to FULL_rate_Ver2 (Full-rate Ver 2). l Configure EFR forcibly On the Local Maintenance Terminal, run the SET CELLSOFT command to change Cell EFR Forced Switch to YES(YES). l Configure the AMR. 1. 2. On the Local Maintenance Terminal, run the MOD BSCBASIC command to change A Interface Tag to GSM_PHASE_2. On the Local Maintenance Terminal, run the MOD CELLCCACCESS command to change Speech Version to FULL_rate_Ver3 (Full-rate Ver 3). If the cell supports the HR services, select Half_rate_Ver3(Half-rate Ver 3) simultaneously. Run the MOD CELLCCAMR command on the Local Maintenance Terminal to configure AMR FR and AMR HR.
NOTE
3.
Configure AMR ACS[F] and AMR ACS[H] to select different coding rates. One to four coding rates can be selected. Configure AMR rate control switch to select different rate adjustment algorithms.
4.
Run the MOD CELLCCBASIC command on the Local Maintenance Terminal to configure AFR Radio Link Timeout and AHR Radio Link Timeout to configure the timeout period of radio link. Run the SET CELLHOBASIC command on the Local Maintenance Terminal to configure the AMR intra-cell TCHF-TCHH handover parameters. Set Intracell F-H HO Allowed to YES(YES). Run the MOD CELLPWRBASIC command on the Local Maintenance Terminal to configure AMR power control parameters of the cell. Set Power Control Switch to HW2(HW2 Power Control) or HW3(HW3 Power Control). According to the value of Power Control Switch, run the MOD CELLPWRHW2 or MOD CELLPWRHW3 command on the Local Maintenance Terminal to configure the parameters related to the AMR power control.
5.
6.
7.
3-2
8.
Run the MOD CELLCHMGAD command on the Local Maintenance Terminal to configure AMR TCH/H Prior Allowed and AMR TCH/H Prior Cell Load Threshold. Run the MOD BTSMPMODE command on the Local Maintenance Terminal to change the multiplexing mode of the Abis interface. Set Multiplexing Mode to MODE1_1 or MODE2_1. On the Local Maintenance Terminal, run the MOD CELLCCACCESS command to change Speech Version to FULL_rate_Ver1 (Full-rate Ver 1). Half_rate_Ver2 (Half-rate Ver 2) under Speech Version is reserved. Currently, no service of halfrate version 2 is available. Run the MOD CHAN command on the Local Maintenance Terminal to change the channel type. Set Channel Type to TCHHR(TCH Half Rate).
NOTE
Configure the HR. 1.
2.
3.
To configure a channel as a TCHH fixedly, set its Channel Type to TCHHR(TCH Half Rate). To configure a channel as a TCHF fixedly or as a dynamically adjusted channel, set its Channel Type to TCHFR(TCH Full Rate). To enable the HR services of the TRX that is not configured with TCHHs, run the MOD TRXDEV command on the Local Maintenance Terminal to set TCH Rate Adjust Allow to YES(YES).
4.
Run the MOD CELLCHMGAD command on the Local Maintenance Terminal to configure TCH Traffic Busy Threshold.
----End
Example
An example script for configuring the EFR is as follows:
MOD CELLCCACCESS: IDXTYPE=BYIDX, CELLIDX=0, VOICEVER=Full_rate_Ver2-0;
An example script for configuring the AMR is as follows:

/*Change the A interface tag to be GSM_PHASE_2*/ MOD BSCBASIC: AVer=GSM_PHASE_2; /*Change the speech version to be full-rate version 2*/ MOD CELLCCACCESS: IDXTYPE=BYIDX, CELLIDX=0, VOICEVER=Full_rate_Ver1-0&Full_rate_Ver2-1&Full_rate_Ver3-0&Half_rate_Ver1-0&Half_ rate_Ver2-0&Half_rate_Ver3-0; /*Configure AMR FR and AMR HR*/ MOD CELLCCAMR: IDXTYPE=BYIDX, CELLIDX=0, RATECTRLSW=ALG1, ACTCDSETF=4_75Kbps-1&5_15Kbps-1&5_90Kbps-1&6_70Kbps-1, ACTCDSETH=4_75Kbps-1&5_15Kbps-1&5_90Kbps-1&6_70Kbps-1; /*Configure the timeout period of radio link*/ MOD CELLCCBASIC: IDXTYPE=BYIDX, CELLIDX=0, AFRDSBLCNT=20, AHRDSBLCNT=20; /*Configure the AMR intra-cell TCHF-TCHH parameters*/ SET CELLHOBASIC: IDXTYPE=BYIDX, CELLIDX=0, HOCTRLSWITCH=HOALGORITHM1, INTRACELLFHHOEN=YES; /*Configure the AMR power control parameters of the cell*/ MOD CELLPWRBASIC: IDXTYPE=BYIDX, CELLIDX=0, PWRCTRLSW=HW3; /*Configure the parameters related to the AMR power control*/ MOD CELLPWRHW3: IDXTYPE=BYNAME, CELLNAME="0", ULADJPRD=15, DLADJPRD=15; /*Configure the AMR call parameters of the cell*/ MOD CELLCHMGAD: IDXTYPE=BYIDX, CELLIDX=0, TCHBUSYTHRES=0, AMRTCHHPRIORALLOW=YES, AMRTCHHPRIORLOAD=50;
An example script for configuring the HR is as follows:

Issue 01 (2010-05-20) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 3-3
/*Change the multiplexing mode of the Abis interface*/ MOD BTSMPMODE: IDXTYPE=BYIDX, BTSIDX=1, MPMODE=MODE1_1; /*Change the speech version*/ MOD CELLCCACCESS: IDXTYPE=BYIDX, CELLIDX=0, VOICEVER=Full_rate_Ver1-1; /*Configure TCH Traffic Busy Threshold*/ MOD CELLCHMGAD: IDXTYPE=BYIDX, CELLIDX=0, TCHBUSYTHRES=50;
Postrequisite
l
Verifying the speech version
On the Local Maintenance Terminal, run the DSP CALLRES command to query the call resources of a user. Verify that the speech version in the query result is FR, EFR, FAMR, HR, or HAMR. On the Local Maintenance Terminal, run the MOD CELLCCACCESS command to modify the setting of Speech Version and clear the unnecessary speech versions. On the Local Maintenance Terminal, run the LST CELLCCACCESS command to query the speech version of the cell. Verify that the corresponding speech version is deactivated.
Deactivating the speech version 1. 2.
3-4
Issue 01 (2010-05-20)
4 Configuring ALC
4
Scenario Impact None NEs Involved BSC
Configuring ALC
Automatic level control (ALC) adjusts the gain of digital voice signals on the uplink and downlink every 20 ms and changes the amplitude of digital voice signals in static or dynamic mode. This keeps the voice level of the entire network in a predefined state, prevents the volume fluctuation of the two parties during a call, and reduces interference among the normal calls. ALC is configured to keep the voice level of the entire network in a predefined state and avoid the volume fluctuation of two parties during a call.
Prerequisite
l l l
ALC is not restricted by the license. The GDPUC or GDPUX is already configured. ALC and TFO cannot be enabled at the same time.
Preparation
Table 4-1 Example of the data negotiated and planned for configuring ALC Parameter ID SRN SN ALCSWITH ALCADAPTMODE Parameter Name Subrack No. Slot No. ALC Switch ALC Mode Example 5 0 OPEN(Open) FIXEDLEVEL(Fixed Level Mode) Source Network planning Network planning Network planning Network planning
Issue 01 (2010-05-20)
4-1
4 Configuring ALC
Parameter ID
Parameter Name
Example FIXEDGAIN(Fixed Gain Mode) ADAPTIVE (Adaptive Mode)
Source Network planning Network planning
Procedure
l Set FIXEDLEVEL(Fixed Level Mode). 1. On the Local Maintenance Terminal, run the MOD DSPTC command. If you do not set DSP No., all the parameters related to the DSP TC are configured. Set ALC Switch to OPEN(Open), and ALC Mode to FIXEDLEVEL(Fixed Level Mode). For ALC Fix Target Level [dBm0], retain the default value -18.
NOTE
If you need to raise the voice, set ALC Fix Target Level [dBm0] to -4. If you need to reduce the voice, set ALC Fix Target Level [dBm0] to -23.
Set FIXEDGAIN(Fixed Gain Mode). 1. On the Local Maintenance Terminal, run the MOD DSPTC command. If you do not set DSP No., all the parameters related to the DSP TC are configured. Set ALC Switch to OPEN(Open), and ALC Mode to FIXEDGAIN(Fixed Gain Mode). For ALC Fix Gain[dB], use the default value 6.
NOTE
If you need to raise the voice, set ALC Fix Gain[dB] to 12. If you need to reduce the voice, set ALC Fix Gain[dB] to 3.
Set ADAPTIVE(Adaptive Mode). 1. On the Local Maintenance Terminal, run the MOD DSPTC command. If you do not set DSP No., all the parameters related to the DSP TC are configured. Set ALC Switch to OPEN(Open), and ALC Mode to ADAPTIVE(Adaptive Mode). For ALC Max Target Level[dBm0] and ALC Min Target Level[dBm0], use the default values -4 and -23 respectively.
NOTE
The value of the adaptive level should be between ALC Min Target Level[dBm0] and ALC Max Target Level[dBm0].
----End
Example
An example script for configuring ALC is as follows:
/*Configure fixed level mode*/ MOD DSPTC: SRN=5, SN=0, ALCSWITH=OPEN, ALCADAPTMODE=FIXEDLEVEL; /*Configure fixed gain mode*/ MOD DSPTC: SRN=5, SN=0, ALCSWITH=OPEN, ALCADAPTMODE=FIXEDGAIN; /*Configure adaptive mode*/ MOD DSPTC: SRN=5, SN=0, ALCSWITH=OPEN, ALCADAPTMODE=ADAPTIVE;
4-2
Issue 01 (2010-05-20)
4 Configuring ALC
Postrequisite
l
Verifying ALC
NOTE
This section takes the verification of the FIXEDGAIN(Fixed Gain Mode) mode as an example. The method of verifying the FIXEDLEVEL(Fixed Level Mode) or ADAPTIVE(Adaptive Mode) mode is similar.
1.
On the Local Maintenance Terminal, run the MOD DSPTC command to set ALC Switch to OPEN(Open), ALC Mode to FIXEDGAIN(Fixed Gain Mode), and ALC Fix Gain[dB] to 0. In the same cell, use MS 1 to call MS 2 with a normal voice. Then, hang up the phone. On the Local Maintenance Terminal, run the MOD DSPTC command to set ALC Switch to OPEN(Open), ALC Mode to FIXEDGAIN(Fixed Gain Mode), and ALC Fix Gain[dB] to 12. On the Local Maintenance Terminal, run the LST DSPTC command to verify that ALC Switch is set to OPEN. Use MS1 to call MS2 again with a normal voice. The volume of the heard voice increases. On the Local Maintenance Terminal, run the MOD DSPTC command to set ALC Switch to CLOSE(Close). Verifying deactivation of ALC: In the same cell, use MS 1 to call MS 2 with a normal voice. Verify that the voice volume is restored to that before the ALC function is enabled.
2. 3.
4. 5.
l
Deactivating ALC 1. 2.
Issue 01 (2010-05-20)
4-3
5 Configuring Acoustic Echo Cancellation
5
Prerequisite
Configuring Acoustic Echo Cancellation

Acoustic echo cancellation (AEC) can decrease acoustic echo caused by the MS, thus improving the network quality and voice quality. Scenario Impact AEC is configured to reduce or cancel the acoustic echo during the call, thus improving the voice quality. None
NEs Involved BSC
l l
The GDPUC or GDPUX is already configured. AEC and TFO cannot be enabled at the same time.
Preparation
Table 5-1 Example of the data negotiated and planned for configuring AEC Data Type TC DSP attributes Parameter ID SRN SN AECSWITH Parameter Name Subrack No. Slot No. AEC Switch Example 5 0 OPEN(Open) Source Network planning Network planning Network planning
Issue 01 (2010-05-20)
5-1
5 Configuring Acoustic Echo Cancellation
Procedure
Step 1 On the Local Maintenance Terminal, run the MOD DSPTC command. If you do not set DSP No., all the parameters related to the DSP TC are configured. Set AEC Switch to OPEN (Open) and retain the default values of other related parameters. ----End
Example
An example script for configuring AEC is as follows:
MOD DSPTC: SRN=5, SN=0, AECSWITCH=OPEN;
Postrequisite
l
Verifying AEC 1. Check whether the acoustic echo is eliminated or becomes lower and whether the call is normal.
NOTE
l l l l
The echo is easily generated when a common MS is enabled with the handsfree function and placed in a sealing box. The acoustic echo is generated between MSs. The echo generated between an MS and a fixed-line phone is termed as electric echo. The electric echo problem needs to be solved by the CN side. When the satellite transmission is used over the Abis interface or Ater interface, you need to set AEC Path Delay[ms] to eliminate the extra delay due to satellite transmission.
Deactivating AEC 1. 2. On the Local Maintenance Terminal, run the MOD DSPTC command to set AEC Switch to CLOSE(Close). Verifying deactivation of AEC: Verify that an acoustic echo exists or becomes higher.
5-2
Issue 01 (2010-05-20)
6 Configuring Cell Broadcast
6
About This Chapter
Configuring Cell Broadcast
Cell broadcast is a teleservice that periodically broadcasts messages to all the MSs in a specified area. With cell broadcast, the mobile network operators can provide special services for users. 6.1 Configuring Cell Broadcast This describes how to configure cell broadcast on the Local Maintenance Terminal with the cooperation of the server and CBC operating system. 6.2 Configuring Simplified Cell Broadcast This describes how to configure simplified cell broadcast on the Local Maintenance Terminal.
Issue 01 (2010-05-20)
6-1
6.1 Configuring Cell Broadcast

This describes how to configure cell broadcast on the Local Maintenance Terminal with the cooperation of the server and CBC operating system. Scenario Impact With cell broadcast, the network sends messages to the MS and does not require any response from the MS. None.
NEs Involved MS, BTS, BSC, and CBC.
Prerequisite
l l
Cell broadcast is restricted by the license. Activate the license on the Local Maintenance Terminal. For details, refer to Activate BSC License.
Preparation
Table 6-1 Example of the data negotiated and planned for configuring cell broadcast Data Type GXPUM Parameter ID SRN SN BT BackType Parameter Name Subrack No. Slot No. Board Type Back Type Example 0 0 GXPUM NONE (Independent Mode) 0 0 0 OPEN(Open) 0 0 VALID (Valid) H'DF Source Network planning Network planning Network planning Network planning
GXPUM port attributes
SRN SN PN PortSwitch
Subrack No. Slot No. Port No. Panel Port Switch Subrack No. Slot No. VLAN Port Valid Switch MAC Address
Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning
GXPUM VLAN parameters
SRN SN AddrValid MAC
6-2
Issue 01 (2010-05-20)
Data Type
Parameter ID IP NETMASK
Parameter Name Ip Address Net Mask BSC name Area Code CC MCC MNC Support Cell Broadcast
Example 192.168.101.1 1 255.255.255.0 bsc 10 086 460 00 SPPRTSTAN DARD (SupportStand ard CB) 60000 YES(Yes) 192.168.101.1 PHASE_FLA G-1 cbc 192.160.100.6 6 0 46000 BYIDX(By Index) 0 0 0 0
Source Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning
BSC attributes
Name AreaCode CC MCC MNC SpprtCB
CB interface CBIPPRT parameters IFCBSHAKE HAND BSCGATEW AYIP CBCItfPara CBC parameters CBCNAME CBCIP CBCPRT OPNAME TRX channel attributes IDXTYPE CELLIDX TRXBN TRXPN CHNO
CBC interface port CB interface handshake BSC Gateway CBC Interface Param CBC Name CBC IP CBC port Owned Operator Index Type Cell Index TRX Board No. TRX Board Path No. Channel No.
Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning
Issue 01 (2010-05-20)
6-3
Data Type
Parameter ID CHTYPE
Parameter Name Channel Type
Example BCCH_CBC H(BCCH +CBCH)
Procedure
Step 1 On the Local Maintenance Terminal, run the ADD BRD command to add a GXPUM. Step 2 On the Local Maintenance Terminal, run the MOD XPUPORT command to configure the attributes of the port on the GXPUM. Step 3 On the Local Maintenance Terminal, run the MOD XPUVLAN command to configure the VLAN parameters of the GXPUM. Step 4 On the Local Maintenance Terminal, run the MOD BSCBASIC command to change Support Cell Broadcast to SPPRTSTANDARD(SupportStandard CB). Step 5 On the Local Maintenance Terminal, run the MOD CBPARA command to change CB interface handshake to YES(Yes). Step 6 On the Local Maintenance Terminal, run the ADD CBC command to add the parameters related to the CBC. Step 7 On the Local Maintenance Terminal, run the LST CHAN command to check whether Channel Type is set to MBCCH(Main BCCH) or SDCCH8(SDCCH8). Step 8 On the Local Maintenance Terminal, run the MOD CHAN command to change the corresponding channel type.
l
If the channel is the main BCCH, change MBCCH(Main BCCH) to BCCH_CBCH(BCCH +CBCH). If the channel is the SDCCH8, change SDCCH8(SDCCH8) to SDCCH_CBCH(SDCCH +CBCH).
Step 9 Configure the route of the CBC server. 1. 2. Log in to the CBC operating system as the system administrator. Specify the IP address for the CBC.
NOTE
If the CBC and server are in different network segments, the following operations must be performed. Otherwise, the following operations need not be performed.
3. 4. 5.
Choose Start > Run. The Run text box is displayed. Type cmd to display the command line window. In the displayed window, enter route add xxx.xxx.xxx.xxx mask 255.255.255.255 yyy.yyy.yyy.yyy. xxx.xxx.xxx.xxx indicates the external IP address for the cell broadcast service; yyy.yyy.yyy.yyy indicates the IP address for the router. After the setting is complete, enter ping xxx.xxx.xxx.xxx to check whether the communication between the CBC and the BSC is normal. If the communication is normal, the setting succeeds.
6.
6-4
NOTE
The ping command is used to check the communication between the CBC and the BSC rather than the CBC services.
----End
Example
An example script for configuring cell broadcast is as follows:
/*Add a GXPUM*/ ADD BRD: SRN=0, SN=0, BT=GXPUM, BackType=NONE; /*Configure the attributes of the port on the GXPUM*/ MOD XPUPORT: SRN=0, SN=0, PN=0, PortSwitch=OPEN; /*Modify the VLAN parameters of the GXPUM*/ MOD XPUVLAN: SRN=0, SN=0, AddrValid=VALID, MAC=H'DF, IP="192.168.101.11", NETMASK="255.255.255.0"; /*Change "Support Cell Broadcast" to "SPPRTSTANDARD(SupportStandard CB)"*/ MOD BSCBASIC: Name="bsc", AreaCode=10, CC=086, MCC="460", MNC="00", SpprtCB=SPPRTSTANDARD; /*Modify the parameters related to the CB interface*/ MOD CBPARA: CBIPPRT=60000, IFCBSHAKEHAND=YES, BSCGATEWAYIP="192.168.101.1", CBCItfPara=PHASE_FLAG-0; /*Add the parameters related to the CBC*/ ADD CBC: CBCNAME="cbc", CBCIP="192.160.100.66", CBCPRT=0, OPNAME="46000"; /*Query the attributes of the TRX channel*/ LST CHAN: IDXTYPE=BYIDX, CELLIDX=0, TRXBN=0, TRXPN=0; /*Modify the attributes of the TRX channel*/ MOD CHAN: IDXTYPE=BYIDX, CELLIDX=0, TRXBN=0, CHNO=0, CHTYPE=BCCH_CBCH;
Postrequisite
l
Verifying cell broadcast 1. On the Trace & Monitor tab page, choose Trace > Trace Message on the Abis Interface > RSL Message. A dialog box is displayed, as shown in Figure 6-1.
Issue 01 (2010-05-20)
6-5
Figure 6-1 Trace RSL Message on the Abis Interface dialog box
2. 3.
Set Tracing Mode to Report, and click OK. In the displayed dialog box shown in Figure 6-2, if SMS Broadcast Command exists in Message Type, you can infer that the cell broadcast function operates normally. Figure 6-2 Tracing the RSL Message at Abis Interface
6-6
Issue 01 (2010-05-20)
Deactivating cell broadcast 1. 2. On the Local Maintenance Terminal, run the MOD BSCBASIC command to set Support Cell Broadcast to NOTSPPRTBC(NotSupport CB). Verifying deactivation of cell broadcast: The method of verifying the deactivation of the cell broadcast function is identical to that of verifying the cell broadcast function. If SMS Broadcast Command does not exist in Message Type, you can infer that the cell broadcast function is deactivated successfully.
6.2 Configuring Simplified Cell Broadcast

This describes how to configure simplified cell broadcast on the Local Maintenance Terminal. Scenario Simplified cell broadcast provides the simplified cell broadcast services without the CBC system. The simplified cell broadcast and the cell broadcast provided by the CBC cannot be used at the same time. None.
Impact
NEs Involved MS, BTS, and BSC.
Prerequisite
l l
Simplified cell broadcast is restricted by the license. Activate the license on the Local Maintenance Terminal. For details, refer to Activate BSC License. Simplified cell broadcast feature cannot be used in combination with the cell broadcast function provided by the CBC.
Preparation
Table 6-2 Example of the data negotiated and planned for configuring simplified cell broadcast Data Type GXPUM Parameter ID SRN SN BT BackType Parameter Name Subrack No. Slot No. Board Type Back Type Example 0 0 GXPUM NONE (Independent Mode) 0 0 0 Source Network planning Network planning Network planning Network planning
GXPUM port attributes
SRN SN PN
Subrack No. Slot No. Port No.

6-7
Issue 01 (2010-05-20)
Data Type
Parameter ID PortSwitch
Parameter Name Panel Port Switch Subrack No. Slot No. VLAN Port Valid Switch MAC Address Ip Address Net Mask BSC name Area Code CC MCC MNC Support Cell Broadcast
Example OPEN(Open) 0 0 VALID(Valid) H'DF 192.168.101.11 255.255.255.0 bsc 10 086 460 00 SPPRTSIMPL E (SupportSimpl e CB) 60000 YES(Yes) 192.168.101.1 PHASE_FLAG -1 BYIDX(By Index) 0 0 0 0
GXPUM VLAN parameters
SRN SN AddrValid MAC IP NETMASK
BSC attributes
Name AreaCode CC MCC MNC SpprtCB
CB interface parameters
CBIPPRT IFCBSHAKEH AND BSCGATEWA YIP CBCItfPara
CBC interface port CB interface handshake BSC Gateway CBC Interface Param Index Type Cell Index TRX Board No. TRX Board Path No. Channel No.
Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning
TRX channel attributes
IDXTYPE CELLIDX TRXBN TRXPN CHNO
6-8
Issue 01 (2010-05-20)
Data Type
Parameter ID CHTYPE
Example BCCH_CBCH (BCCH +CBCH) BYIDX(By Index) 0 YES(YES)
Source Cell Name
IDXTYPE CELLIDX SUPPORTCEL LBROADCAS T
Index Type Cell Index Support cell broadcast name Index type Cell Index Geography scope Code Update Chan ID Coding scheme Content of message Repeat Interval Start time End time
Simplified cell broadcast message
IDXTYPE CELLINDEX GS CODE UPDATE CHANID SCHEME TEXT REP INT ST ET
BYIDX(By Index) 0 LAC(LAC) 3 0 1 GB2312 (GB2312) test 1 2 08-12-19 17:55:50 08-12-19 17:55:51
Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning
Procedure
Step 1 On the Local Maintenance Terminal, run the ADD BRD command to add the GXPUM. Step 2 On the Local Maintenance Terminal, run the MOD XPUPORT command to configure the attributes of the port on the GXPUM. Step 3 On the Local Maintenance Terminal, run the MOD XPUVLAN command to configure the VLAN parameters of the GXPUM.
Issue 01 (2010-05-20)
6-9
Step 4 On the Local Maintenance Terminal, run the MOD BSCBASIC command to change Support Cell Broadcast to SPPRTSIMPLE(SupportSimple CB). Step 5 On the Local Maintenance Terminal, run the MOD CBPARA command to change CB interface handshake to YES(Yes). Step 6 On the Local Maintenance Terminal, run the LST CHAN command to check whether Channel Type is set to MBCCH(Main BCCH) or SDCCH8(SDCCH8). Step 7 On the Local Maintenance Terminal, run the MOD CHAN command to change the corresponding channel type.
l
If the channel is the main BCCH, change MBCCH(Main BCCH) to BCCH_CBCH(BCCH +CBCH). If the channel is the SDCCH8, change SDCCH8(SDCCH8) to SDCCH_CBCH(SDCCH +CBCH).
Step 8 On the Local Maintenance Terminal, run the MOD CELLSBC command to change Support cell broadcast name to YES(YES). Step 9 On the Local Maintenance Terminal, run the ADD SMSCB command to add the simplified cell broadcast message for the cell. ----End
Example
An example script for configuring simplified cell broadcast is as follows:
/*Add a GXPUM*/ ADD BRD: SRN=0, SN=0, BT=GXPUM, BackType=NONE; /*Configure the attributes of the port on the GXPUM*/ MOD XPUPORT: SRN=0, SN=0, PN=0, PortSwitch=OPEN; /*Modify the VLAN parameters of the GXPUM*/ MOD XPUVLAN: SRN=0, SN=0, AddrValid=VALID, MAC=H'DF, IP="192.168.101.11", NETMASK="255.255.255.0"; /*Change "Support Cell Broadcast" to "SPPRTSIMPLE(SupportSimple CB)"*/ MOD BSCBASIC: Name="bsc", AreaCode=10, CC=086, MCC="460", MNC="00", SpprtCB=SPPRTSIMPLE; /*Modify the parameters related to the CB interface*/ MOD CBPARA: CBIPPRT=60000, IFCBSHAKEHAND=YES, BSCGATEWAYIP="192.168.101.1", CBCItfPara=PHASE_FLAG-0; /*Query the attributes of the TRX channel*/ LST CHAN: IDXTYPE=BYIDX, CELLIDX=0, TRXBN=0, TRXPN=0; /*Modify the attributes of the TRX channel*/ MOD CHAN: IDXTYPE=BYIDX, CELLIDX=0, TRXBN=0, CHNO=0, CHTYPE=BCCH_CBCH; /*Change "Support cell broadcast name" to "YES(YES)"*/ MOD CELLSBC: IDXTYPE=BYIDX, CELLIDX=0, SUPPORTCELLBROADCAST=YES; /*Add the simplified cell broadcast message*/ ADD SMSCB: IDXTYPE=BYIDX, CELLINDEX=0, GS=LAC, CODE=3, UPDATE=0, CHANID=1, SCHEME=GB2312, TEXT="test", REP=1, INT=2, ST=2008&11&15&15&46&13, ET=2008&11&15&15&00&13;
Postrequisite
l
Verifying simple cell broadcast 1. On the Trace & Monitor tab page, choose Trace > Trace Message on the Abis Interface > RSL Message. A dialog box is displayed, as shown in Figure 6-3.
6-10
Issue 01 (2010-05-20)
Figure 6-3 Trace RSL Message on the Abis Interface dialog box
2. 3.
Set Tracing Mode to Report, and click OK. In the displayed dialog box shown in Figure 6-4, if SMS Broadcast Command exists in Message Type, you can infer that the simple cell broadcast runs normally. Figure 6-4 Trace the RSL Message at Abis Interface dialog box
Issue 01 (2010-05-20)
6-11
Deactivating simplified cell broadcast 1. 2. On the Local Maintenance Terminal, run the MOD BSCBASIC command to set Support Cell Broadcast to NOTSPPRTBC(NotSupport CB). Verifying deactivation of simple cell broadcast: The method of verifying the deactivation of the simple cell broadcast function is identical to that of verifying the simple cell broadcast function. If SMS Broadcast Command does not exist in Message Type, you can infer that the simple cell broadcast function is deactivated successfully.
6-12
Issue 01 (2010-05-20)
7 Configuring Ciphering
7
Scenario Impact None
Configuring Ciphering
The ciphering algorithm encrypts the subscriber information such as the voice and data so that the information is securely transmitted on the Um interface. Ciphering is configured to ensure the information security.
NEs Involved MS, BTS, BSC, MSC/VLR, AUC, and HLR
Prerequisite
l l
Ciphering is license-controlled. Activate the license on the Local Maintenance Terminal. For details, see Activate BSC License.
Preparation
Table 7-1 Example of the data negotiated and planned for configuring ciphering Data Type Basic call control attributes of the cell Parameter ID IDXTYPE CELLIDX RACHBUSYTH RED PAGTIMES ASSLOADJUDG EEN Parameter Name Index Type Cell Index RACH Busy Threshold Paging Times Assignment Cell Load Judge Enable Example BYIDX(By Index) 0 16 4 DISABLE (DISABLE) Source Network planning Network planning Network planning Network planning Network planning
Issue 01 (2010-05-20)
7-1
Data Type
Parameter ID DTLOADTHRE D MSMAXRETRA N ERGCALLDIS ECSC MBR REASSEN EMLPPEN
Parameter Name Directed Retry Load Access Threshold MS MAX Retrans Emergent Call Disable ECSC Multi-band report Allow Reassign Allow EMLPP SD Fast Ho Timer of Reserved TCH for EMC[s] Timer For SD Fast Ho trig Encryption Algorithm BSC name Area Code CC MCC MNC A Interface Tag
Example 85
Source Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning
4_Times (4_Times) YES(YES) YES(YES) 2 YES(YES) YES(YES) ON(ON) 10
Cell software parameters Cell timer
SDFASTHOSWI TCH WAITRESVCHA NREFRESHTIM ER WTSDFASTHOTRIGTMR
5 A5/0, A5/3 bsc 12 086 460 00 GSM_PHASE_ 2Plus
Cell basic attributes BSC basic attributes
ENCRY Name AreaCode CC MCC MNC AVer
7-2
Issue 01 (2010-05-20)
Procedure
Step 1 On the Local Maintenance Terminal, run the MOD CELLCCBASIC command to configure the basic call parameters of the cell. Step 2 On the Local Maintenance Terminal, run the SET CELLSOFT command to set SD Fast Ho.
NOTE
SD Fast Ho is configured to improve the security of the A5 ciphering algorithm.
Step 3 On the Local Maintenance Terminal, run the SET CELLTMR command to set Timer For SD Fast Ho trig. Step 4 On the Local Maintenance Terminal, run the MOD CELLBASICPARA command to configure the ciphering algorithm.
NOTE
A5/0 must be included in the encryption algorithm.
Step 5 On the Local Maintenance Terminal, run the MOD BSCBASIC command to set A Interface Tag to GSM_PHASE_2 or GSM_PHASE_2Plus. Step 6 Enable the A5/0 and A5/3 ciphering algorithms on the MSC side. For details, see the related configuration manual. ----End
Example
An example script for configuring ciphering is as follows:
/*Modify the basic call parameters of the cell*/ MOD CELLCCBASIC: IDXTYPE=BYIDX, CELLIDX=0, RACHBUSYTHRED=16, PAGTIMES=4, ASSLOADJUDGEEN=DISABLE, DTLOADTHRED=85, MSMAXRETRAN=4_Times, ERGCALLDIS=YES, ECSC=YES, MBR=2, REASSEN=YES, EMLPPEN=YES; /*Set "SD Fast Ho"*/ SET CELLSOFT: SDFASTHOSWITCH=ON; /*Set "Timer For SD Fast Ho trig"*/ SET CELLTMR: IDXTYPE=BYIDX, CELLIDX=0, WAITRESVCHANREFRESHTIMER=10, WTSDFASTHOTRIGTMR=5; /*Set "Encryption Algorithm"*/ MOD CELLBASICPARA: IDXTYPE=BYIDX, CELLIDX=0, ENCRY=A5/0-1&A5/3-1; /*Set "A Interface Tag"*/ MOD BSCBASIC: Name="bsc", AreaCode=12, CC=086, MCC="460", MNC="00", AVer=GSM_PHASE_2Plus;
Postrequisite
l
Verifying ciphering 1. 2. Start the tracing of the BSSAP messages on the A interface. For details, see Tracing BSSAP Messages on the A Interface in the BSC LMT User Guide. After the window for tracing the BSSAP messages on the A interface is opened, initiate a call in the test cell. When the call is set up, verify that the Cipher Mode CMD message is present. On the Local Maintenance Terminal, run the MOD CELLBASICPARA command to modify the setting of the Encryption Algorithm parameter by clearing the unnecessary ciphering algorithms.
Deactivating ciphering 1.
Issue 01 (2010-05-20)
2.
Verifying deactivation of ciphering: The method of verifying the deactivation of the ciphering function is identical to that of verifying the ciphering function. Verify that the Cipher Mode CMD message does not exist in the queried result.
7-4
Issue 01 (2010-05-20)
8 Configuring Frequency Hopping
8
Context
Configuring Frequency Hopping
About This Chapter

With this feature, wanted signals are transmitted by switching a carrier among many frequencies according to the specified sequences. Frequency hopping involves RF hopping and baseband hopping.Frequency hopping is a spread-spectrum technology, which has the features such as resistance to interference, anti-attenuation, and high security. The application of frequency hopping in the GSM supresses the interference and increases the system capacity.
The frequency hopping improves the speech quality; however, it has negative impact on PS services. Especially in high data rate coding schemes such as CS3-CS4, MCS5-MCS9, it may have negative impact on the network. Therefore, you are advised not to enable frequency hopping in this case. 8.1 Principles of Configuring the FH Cell This describes the principles of configuring the frequency hopping (FH) cell. 8.2 Changing None FH to RF FH This describes how to change the FH mode of a cell from none FH to RF FH on the Local Maintenance Terminal. 8.3 Changing None FH to Baseband FH This describes how to change the FH mode of a cell from none FH to baseband FH on the Local Maintenance Terminal. 8.4 Changing RF FH to Baseband FH This describes how to change the FH mode of a cell from RF FH to baseband FH on the Local Maintenance Terminal. 8.5 Changing Baseband FH to RF FH This describes how to change the FH mode of a cell from baseband FH to RF FH on the Local Maintenance Terminal. 8.6 Changing RF FH to None FH This describes how to change the FH mode of a cell from RF FH to none FH on the Local Maintenance Terminal. 8.7 Changing Baseband FH to None FH
This describes how to change the FH mode of a cell from baseband FH to none FH on the Local Maintenance Terminal. 8.8 Setting FH Mode to Hybrid FH This describes how to set the FH mode of a cell to hybrid FH on the Local Maintenance Terminal. 8.9 Changing Hybrid FH to None FH This describes how to change the FH mode of a cell from hybrid FH to none FH on the Local Maintenance Terminal. 8.10 Configuring MA Group This describes how to configure a MA group for the cell on the Local Maintenance Terminal.
8-2
Issue 01 (2010-05-20)
8.1 Principles of Configuring the FH Cell

This describes the principles of configuring the frequency hopping (FH) cell. When configuring an FH cell, adhere to the following principles:
l
The GSM900 is classified into sub frequency bands: P-GSM, E-GSM, and R-GSM. The P-GSM (900P) band provides the frequencies numbered from 1 to 124, the E-GSM (900E) provides the frequencies numbered 0 and those numbered from 975 to 1023, and the RGSM band provides the frequencies numbered from 955 to 974. In initial configuration, the first channel to be configured is the BCCH by default. If the main BCCH frequency belongs to the 900P band, the frequencies from the 900P band are called compatible frequencies while those from the 900E and 1800M bands are called incompatible frequencies. If the main BCCH frequency belongs to the 900E band, the frequencies from the 900P and 900E bands are called compatible frequencies while those from the 900R and 1800M bands are called incompatible frequencies. If the main BCCH frequency belongs to the 900R band, the frequencies from the 900P, 900E, and 900R bands are called compatible frequencies while the frequencies from the 1800M band are called incompatible frequencies. For frequency hopping in non co-BCCH cells, if the main BCCH frequency belongs to the 900P band, the cells cannot contain the frequencies from the incompatible EGSM or 1800M band. The frequency of the TRX that carries the SDCCH can be compatible or incompatible with the main BCCH frequency. If the frequency of the TRX that carries the SDCCH and the main BCCH frequency belong to the same frequency band, the frequency band where the TRX with the SDCCH operates should not be higher than that where the TRX with the main BCCH operates. The PDCH can configured only on the TRX of compatible main BCCH frequency. If a cell is configured with less than two TRXs, the cell should not be configured as an FH cell. In a double-timeslot cell, the TRX carrying the main BCCH must be configured in the underlaid subcell. When a double-timeslot cell is also a concentric cell, at least one static PDCH should be configured in the overlaid subcell. In a double-timeslot cell, the odd-numbered channels on the TRXs in the underlaid subcell must be SDCCHs. If a double-timeslot cell is configured with baseband FH, the TRXs in the underlaid subcell should not be in the same FH group with other TRXs. If baseband FH is configured in a COBCCH cell, the frequencies in a FH group must be on the same frequency band. In RF FH, the TRX carrying the main BCCH must be set to No FH. If the baseband FH and the EDGE functionality conflict, they cannot be configured simultaneously. When the cell software parameter TSC Plan Enable is set to the ON state, the base station color code (BCC) of a cell must be the same as the training sequence code (TSC) in the FH data table. When the cell software parameter TSC Plan Enable is set to the OFF state, the base station color code (BCC) of a cell must be different from the training sequence code (TSC) in the FH data table.
l l
Issue 01 (2010-05-20)

l
In the baseband FH, the FH group of non-main BCCH frequencies in timeslot 0 is exclusive to the main BCCH frequencies. In RF FH, the TRX carrying the main BCCH must be set to No FH. If a double-transceiver BTS is configured with baseband FH, the TRXs whose frequencies are in one FH group must be configured in the same cabinet. If a single-transceiver BTS is configured with baseband FH, the TRXs whose frequencies are in one FH group must be configured in the same cabinet group. For the FH TRXs, the same timeslots should not have the same FH group number and the same Mobile Allocation Index Offset (MAIO) simultaneously. In a cell, the TCHs on the carriers incompatible with the BCCH carrier can be converted into PDCHs if the MS supports the related frequency bands; the TCHs on only the carriers compatible with the BCCH carrier can be converted into PDCHs if the MS does not support the related frequency band. When the long-range FH switch is turned on, the number of carriers compatible with the BCCH carrier can be greater than 24 in a GPRS cell or greater than 16 in an EGPRS cell, but the following conditions must be met:

l l
At least one static PDCH should be configured on the BCCH carrier. The carriers compatible with the BCCH carrier and those incompatible with the BCCH carrier should not be configured in the same MA list.
If the number of carriers compatible with the BCCH carrier in a cell is greater than 32, at least one non-FH TRX should be configured in the cell.If the number of carriers compatible with the BCCH carrier in a GPRS cell is greater than 24 but smaller than or equal to 32, or the number of carriers compatible with the BCCH carrier in an EGPRS cell is greater than 16 but smaller than or equal to 32, a maximum of one MA list in which the carriers are compatible with the BCCH carrier can be configured.
l
In a concentric cell, if the BCCH carrier is located in the OL subcell, the carriers compatible with the BCCH carrier should be configured with PDCHs, and the carriers incompatible with the BCCH carrier can be configured with PDCHs or the channels on these carriers can be converted into PDCHs. If all the traffic channels in a concentric cell are configured as dynamic PDTCHs, the parameter Dynamic Channel Conversion Parameter of Concentric Cell of GPRS Attributes should be set to Convert dynamic channel in both subcells and underlaid subcell preferred. In a concentric cell, if the BCCH carrier is located in the UL subcell, the carrier assigned to the MS accessing the network for the first time should meet the following conditions: It should be located in the UL subcell and be compatible with the BCCH carrier, and PDCH should be configured on the carrier. Otherwise, the MS cannot access the network. The carriers incompatible with the BCCH carrier can be configured with PDCHs or the channels on these carriers can be converted into PDCHs so that the MS can be assigned these carriers through the Packet Timeslot Reconfigure procedure. If there is an MA containing a BCCH-compatible frequency and a non-BCCH-compatible frequency in the configured FH cell, you are advised to enable a TRX (the BCCH TRX is preferred) to meet one of the following conditions to ensure the initial access of the MS:
The TRX does not participate in FH and is compatible with the BCCH. In addition, the TRX is configured with static PDCHs or channels that can be converted into PDCHs. The TRX participates in FH, but all the frequencies in the MA are compatible with the BCCH. In addition, the TRX is configured with static PDCHs or channels that can be converted into PDCHs.
8-4
Issue 01 (2010-05-20)
8.2 Changing None FH to RF FH

This describes how to change the FH mode of a cell from none FH to RF FH on the Local Maintenance Terminal. Scenario Impact The frequency hopping simplifies frequency planning, improves the antiinterference capability, and increases the capacity of the system. The frequency hopping improves the speech quality; however, it has negative impact on PS services.
NEs Involved MS, BTS, and BSC

NOTE
When the FH mode of a cell is changed from none FH to RF HP, the system automatically changes the FH attributes of all TRXs in a cell to RF FH.
Prerequisite
The number of TRXs in a cell must be greater than or equal to two.
Preparation
Table 8-1 Example of the data negotiated and planned for changing none FH to RF FH Parameter ID IDXTYPE CELLNAME FHMODE Parameter Name Index Type Cell Name Frequency hopping mode Example BYNAME Cell_1 RF_FH(RF FH) Source Network planning Network planning Network planning
Procedure
Step 1 On the Local Maintenance Terminal, run the MOD CELLHOPTP command. Select the target cell according to the Cell Index or Cell Name, and then set the Frequency hopping mode to RF_FH(RF FH). ----End
Example
An example script of changing the FH mode of a cell from none FH to RF FH is as follows:
MOD CELLHOPTP: IDXTYPE=BYNAME, CELLNAME="Cell_1", FHMODE=RF_FH;
Issue 01 (2010-05-20)
8-5
Postrequisite
l
Verifying FH 1. Start the tracing of the RSL messages on the Abis interface. For details, see Tracing RSL Messages on the Abis Interface in the BSC LMT User Guide. Use the MS to make a call in the cell to be verified. Verify that that the call is normal and the voice quality is good. Then, observe the Abis signaling tracing window. The result shows that the Assignment Command message is traced and the information element h:rf-hoppingchannel in the message is 1.
8.3 Changing None FH to Baseband FH

This describes how to change the FH mode of a cell from none FH to baseband FH on the Local Maintenance Terminal. Scenario Impact The frequency hopping simplifies frequency planning, improves the antiinterference capability, and increases the capacity of the system. The frequency hopping improves the speech quality; however, it has negative impact on PS services.
Prerequisite
l l
The number of TRXs in a cell must be greater than or equal to two. The BTS supports baseband FH.
Preparation
Table 8-2 Example of the data negotiated and planned for changing none FH to baseband FH Parameter ID IDXTYPE CELLNAME FHMODE BCCHTRXHP Parameter Name Index Type Cell Name Frequency hopping mode Frequency hopping mode of BCCH TRX Example BYNAME Cell_1 BaseBand_FH (BaseBand FH) Hop(Hop) Source Network planning Network planning Network planning Network planning
Procedure
Step 1 On the Local Maintenance Terminal, run the MOD CELLHOPTP command. Select the target cell according to the Cell Index or Cell Name. Select the Frequency hopping mode to
8-6 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 01 (2010-05-20)
BaseBand_FH (BaseBand FH) and then Select the Frequency hopping mode of BCCH TRX to Hop, set the BCCH carrier frequency hopping.
NOTE
For the FH that the BCCH carrier participates in, the BCCH timeslot is not involved, but the rest timeslots can participate in the baseband hopping. This feature depends on baseband hopping and mutually exclusive RF hopping.
----End
Example
An example script of changing the FH mode of a cell from none FH to baseband FH with the BCCH TRX involving in FH is as follows:
MOD CELLHOPTP: IDXTYPE=BYNAME, CELLNAME="Cell_1", FHMODE=BaseBand_FH, BCCHTRXHP=Hop;
Postrequisite
l
Verifying FH 1. Start the tracing of RSL messages on the Abis interface. For details, see Tracing RSL Messages on the Abis Interface in the BSC LMT User Guide. Use the MS to make a call in the cell to be verified. Verify that that the call is normal and the voice quality is good. Then, observe the Abis signaling tracing window. The Assignment Command message is traced and the information element h:rf-hopping-channel in the message is 1.
8.4 Changing RF FH to Baseband FH

This describes how to change the FH mode of a cell from RF FH to baseband FH on the Local Maintenance Terminal. Scenario Impact The frequency hopping simplifies frequency planning, improves the antiinterference capability, and increases the capacity of the system. The frequency hopping improves the speech quality; however, it has negative impact on PS services.

NOTE
The BSC does not allow the direct switch from RF FH to baseband FH. Therefore, change the FH mode of a cell from RH FH to none FH, and then from none FH to baseband FH. For how to change the FH mode of a cell from RF FH to none FH, see 8.6 Changing RF FH to None FH. For how to change the FH mode of a cell from none FH to baseband FH , see 8.3 Changing None FH to Baseband FH.
Prerequisite
l l
The number of TRXs in a cell must be greater than or equal to two. The BTS supports baseband FH.
Issue 01 (2010-05-20)
Procedure
Step 1 On the Local Maintenance Terminal, run the MOD CELLHOPTP command and set the Frequency hopping mode to NO_FH(NO FH). Step 2 On the Local Maintenance Terminal, run the MOD CELLHOPTP command and set the Frequency hopping mode to BaseBand_FH(BaseBand FH). ----End
Example
An example script of changing RF FH to baseband FH is as follows:
/*Change the FH mode of a cell MOD CELLHOPTP: IDXTYPE=BYNAME, /*Change the FH mode of a cell MOD CELLHOPTP: IDXTYPE=BYNAME, BCCHTRXHP=Hop; from RF FH to none FH*/ CELLNAME="Cell_1", FHMODE=NO_FH; from none FH to baseband FH*/ CELLNAME="Cell_1", FHMODE=BaseBand_FH,
8.5 Changing Baseband FH to RF FH

This describes how to change the FH mode of a cell from baseband FH to RF FH on the Local Maintenance Terminal. Scenario Impact The frequency hopping simplifies frequency planning, improves the antiinterference capability, and increases the capacity of the system. The frequency hopping improves the speech quality; however, it has negative impact on PS services.

NOTE
The BSC does not allow the direct switch from baseband FH to RF FH. Therefore, change the FH mode of a cell from baseband FH to RF FH; and then change baseband FH to none FH. For change the FH mode of a cell from baseband FH to none FH , see 8.7 Changing Baseband FH to None FH. Change the FH mode of a cell from none FH to RF FH, see 8.2 Changing None FH to RF FH.
Prerequisite
Procedure
Step 1 On the Local Maintenance Terminal, run the MOD CELLHOPTP command and set the Frequency hopping mode to NO_FH(NO FH). Step 2 On the Local Maintenance Terminal, run the MOD CELLHOPTP command and set the Frequency hopping mode to RF_FH(RF FH). ----End
Example
An example script of changing baseband FH to RF FH is as follows:
/*Change the FH mode of a cell MOD CELLHOPTP: IDXTYPE=BYNAME, /*Change the FH mode of a cell MOD CELLHOPTP: IDXTYPE=BYNAME, from baseband FH to none FH*/ CELLNAME="Cell_1", FHMODE=NO_FH; from none FH to RF FH*/ CELLNAME="Cell_1", FHMODE=RF_FH, BCCHTRXHP=Hop;
8.6 Changing RF FH to None FH

This describes how to change the FH mode of a cell from RF FH to none FH on the Local Maintenance Terminal. Scenario Impact In high data rate coding schemes of PS services, the frequency hopping may have negative impact on the network. The frequency hopping improves the speech quality; however, it has negative impact on PS services.
Prerequisite
Preparation
Table 8-3 Example of the data negotiated and planned for changing RF FH to none FH Parameter ID IDXTYPE CELLNAME FHMODE Parameter Name Index Type Cell Name Frequency hopping mode Example BYNAME Cell_1 NO_FH(NO FH) Source Network planning Network planning Network planning
Procedure
Step 1 On the Local Maintenance Terminal, run the MOD CELLHOPTP command. Select the target cell according to the Cell Index or Cell Name and set the Frequency hopping mode to NO_FH (NO FH). ----End
Example
An example script of changing the FH mode of a cell from RF FH to none FH is as follows:
MOD CELLHOPTP: IDXTYPE=BYNAME, CELLNAME="Cell_1", FHMODE=NO_FH;
8.7 Changing Baseband FH to None FH

This describes how to change the FH mode of a cell from baseband FH to none FH on the Local Maintenance Terminal. Scenario Impact In high data rate coding schemes of PS services, the frequency hopping may have negative impact on the network. The frequency hopping improves the speech quality; however, it has negative impact on PS services.
Prerequisite
Preparation
Table 8-4 Example of the data negotiated and planned for changing baseband FH to none FH Parameter ID IDXTYPE CELLNAME FHMODE Parameter Name Index Type Cell Name Frequency hopping mode Example BYNAME Cell_1 NO_FH(NO FH) Source Network planning Network planning Network planning
Procedure
Example
An example script of changing the FH mode of a cell from baseband FH to none FH is as follows:
MOD CELLHOPTP: IDXTYPE=BYNAME, CELLNAME="Cell", FHMODE=NO_FH;
8.8 Setting FH Mode to Hybrid FH

This describes how to set the FH mode of a cell to hybrid FH on the Local Maintenance Terminal.
Scenario Impact
The frequency hopping simplifies frequency planning, improves the antiinterference capability, and increases the capacity of the system. The frequency hopping improves the speech quality; however, it has negative impact on PS services.

NOTE
The BSC does not allow the direct switch from baseband FH/RF FH to hybrid FH.
l l
If the FH mode of a cell is none FH, set the FH mode to hybrid FH directly. If the FH mode of a cell is baseband FH or RF FH, change the FH mode from baseband or RF FH to none FH, and then from none FH to hybrid FH.
l l
For how to change the FH mode of a cell from RF FH to none FH, see 8.6 Changing RF FH to None FH. For how to change the FH mode of a cell from baseband FH to none FH , see 8.7 Changing Baseband FH to None FH.
Prerequisite
Preparation
The configuration parameters of changing the FH mode from none FH to hybrid FH or from baseband FH or RF FH to hybrid FH are almost the same. The following is an example of the parameters planned for changing the FH mode of a cell from none FH to hybrid FH. Table 8-5 Example of the data negotiated and planned for changing the FH mode of a cell from none FH to hybrid FH Parameter ID IDXTYPE CELLNAME FHMODE BCCHTRXHP Parameter Name Index Type Cell Name Frequency hopping mode Frequency hopping mode of BCCH TRX Example BYNAME Cell_1 Hybrid_FH(Hybrid FH) Hop(Hop) Source Network planning Network planning Network planning Network planning
Procedure
l If the FH mode of a cell is none FH, do as follows: 1. On the Local Maintenance Terminal, run the MOD CELLHOPTP command. Select the target cell according to the Cell Index or Cell Name and set the Frequency hopping mode to Hybrid_FH(Hybrid FH).
Issue 01 (2010-05-20)
If the FH mode of a cell is baseband FH or RF FH, do as follows: 1. On the Local Maintenance Terminal, run the MOD CELLHOPTP command to select the target cell according to the Cell Index or Cell Name, and then set the Frequency hopping mode to NO_FH(NO FH). On the Local Maintenance Terminal, run the MOD CELLHOPTP command. Select the target cell according to the Cell Index or Cell Name and set the Frequency hopping mode to Hybrid_FH(Hybrid FH).
2.
----End
Example
An example script of changing the FH mode of a cell from none FH to hybrid FH is as follows:
MOD CELLHOPTP: IDXTYPE=BYNAME, CELLNAME="Cell_1", FHMODE=Hybrid_FH, BCCHTRXHP=Hop;
An example script of changing the FH mode of a cell from baseband FH/RF FH to hybrid FH is as follows:
/*Change the FH mode of a cell MOD CELLHOPTP: IDXTYPE=BYNAME, /*Change the FH mode of a cell MOD CELLHOPTP: IDXTYPE=BYNAME, to none FH*/ CELLNAME="Cell_1", FHMODE=NO_FH; from none FH to hybrid FH*/ CELLNAME="Cell_1", FHMODE=Hybrid_FH, BCCHTRXHP=Hop;
Postrequisite
l
Verifying FH 1. Start the tracing of RSL messages on the Abis interface. For details, see Tracing RSL Messages on the Abis Interface in the BSC LMT User Guide. Use the MS to make a call in the cell to be verified. Verify that that the call is normal and the voice quality is good. Then, observe the Abis signaling tracing window. The Assignment Command message is traced and the information element h:rf-hopping-channel in the message is 1.
8.9 Changing Hybrid FH to None FH

This describes how to change the FH mode of a cell from hybrid FH to none FH on the Local Maintenance Terminal. Scenario Impact In high data rate coding schemes of PS services, the frequency hopping may have negative impact on the network. The frequency hopping improves the speech quality; however, it has negative impact on PS services.

NOTE
To change the FH mode of a cell from hybrid FH to baseband FH or RF FH, first change hybrid FH to none FH, and then change none FH to baseband FH or RF FH.
Prerequisite
Preparation
Table 8-6 Example of the data negotiated and planned for changing hybrid FH to none FH Parameter ID IDXTYPE CELLNAME FHMODE Parameter Name Index Type Cell Name Frequency hopping mode Example BYNAME Cell_1 NO_FH(NO FH) Source Network planning Network planning Network planning
Procedure
Example
An example script of changing the FH mode of a cell from hybrid FH to none FH is as follows:
MOD CELLHOPTP: IDXTYPE=BYNAME, CELLNAME="Cell_1", FHMODE=NO_FH;
8.10 Configuring MA Group

This describes how to configure a MA group for the cell on the Local Maintenance Terminal. Scenario Impact The MA group is configured to simplify the frequency planning, improve the anti-interference capability, and increase the system capacity. The frequency hopping improves the speech quality; however, it affects the PS services.
Prerequisite
l l
The current cell is configured with FH mode. The frequencies of cells must meet at least one of the following conditions:

The ARFCN is greater than 0 but not greater than 124. The difference between the maximum ARFCN and the minimum ARFCN is not greater than 111. The interval between two adjacent frequencies is not less than 913.
Issue 01 (2010-05-20)

The number of frequencies is not greater than 16. The number of frequencies is 17 and the minimum ARFCN is 0. The number of frequencies is not greater than 18 and the maximum interval between two frequencies (or minimum frequency - maximum frequency + 1024) is greater than 512. The number of frequencies is not greater than 22 and the maximum interval between two frequencies (or minimum frequency - maximum frequency + 1024) is greater than 786. The number of frequencies is not greater than 29 and the maximum interval between two frequencies (or minimum frequency - maximum frequency + 1024) is greater than 896.
Preparation
Table 8-7 Example of the data negotiated and planned for configuring the MA group Parameter Type Cell frequency Parameter ID IDXTYPE CELLNAME FREQ1 FREQ2 FREQ3 MA group IDXTYPE CELLNAME HSN TSC HOPMODE FREQ1 FREQ2 Parameter Name Index Type Cell Name frequency 1 frequency 2 frequency 3 Index Type Cell Name HSN TSC Frequency hopping mode frequency 1 frequency 2 Example BYNAME Cell_1 30 35 40 BYNAME Cell_1 0 0 BaseBand_FH (BaseBand FH) 30 35 Source Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning
Issue 01 (2010-05-20)
8-14
Parameter Type
Parameter ID FREQ3
Parameter Name frequency 3 Index Type Cell Name Channel No. No.1 TRX Board No. No.1 TRX Board Pass No. Trx1 Hop Index Trx1 Maio
Example 40 BYNAME Cell_1 1 2 0 5 11
FH index and MAIO
IDXTYPE CELLNAME CHANNO TRXBN1 TRXPN1 TRX1HOPIND EX TRX1MAIO
Procedure
Step 1 On the Local Maintenance Terminal, run the LST CELLMAGRP command to query the configuration information about the MA group of the cell. Step 2 On the Local Maintenance Terminal, run the ADD CELLFREQ command to add frequencies for the cell. If the frequencies configured for the cell are sufficient, skip this step. Step 3 On the Local Maintenance Terminal, run the ADD CELLMAGRP command to add MA groups for the cell. HSN should be the same as the corresponding BCC.
NOTE
If the original MA groups need to be modified, run the MML command MOD CELLMAGRP.
Step 4 On the Local Maintenance Terminal, run the LST CELLCHANHOP command to query the configuration information about the FH index and MAIO of the cell. Step 5 On the Local Maintenance Terminal, run the MOD CELLCHANHOP command to configure the FH index and MAIO for the added MA groups. ----End
Example
An example script for configuring the MA group is as follows:
/*Query the configuration information about the MA group of the cell*/ LST CELLMAGRP: IDXTYPE=BYNAME, CELLNAME="Cell_1"; /*Add frequencies*/
Issue 01 (2010-05-20)
8-15
ADD CELLFREQ: IDXTYPE=BYNAME, CELLNAME="Cell_1", FREQ1=30, FREQ2=35, FREQ3=40; /*Add MA groups*/ ADD CELLMAGRP: IDXTYPE=BYNAME, CELLNAME="Cell_1", HSN=0, TSC=0, HOPMODE=BaseBand_FH, FREQ1=30, FREQ2=35, FREQ3=40; /*Query the FH index and MAIO*/ LST CELLCHANHOP: IDXTYPE=BYNAME, CELLNAME="Cell_1"; /*Configure the FH index and MAIO*/ MOD CELLCHANHOP: IDXTYPE=BYNAME, CELLNAME="Cell_1", CHANNO=1, TRXBN1=2, TRXPN1=0, TRX1HOPINDEX=5, TRX1MAIO=11;
8-16
Issue 01 (2010-05-20)
9 Configuring eMLPP
9
Configuring eMLPP
The eMLPP is a supplementary service offered by the GSM system. The eMLPP service allows a subscriber to initiate calls with different priorities. The network side employs different channel assignment strategies for the subscribers according to the priorities. If the network is congested, the call with higher priority is served preferably. The eMLPP function is configured to ensure normal conversation of the MS with higher priority if the network resources are insufficient.
NEs Involved HLR, MSC, BSC, BTS, and MS
Prerequisite
l l
The eMLPP function is restricted by the license. Activate the license on the Local Maintenance Terminal. For details, see Activate BSC License. The GXPUM and Abis interface board are configured on the GMPS or GEPS, and there is idle port on the Abis interface board. The eMLPP feature should be supported by the MSC, HLR, and MS.
Preparation
Take the configuration of BTS3012 in TDM transmission mode as an example. Table 9-1 Example of the data negotiated and planned for adding a BTS Data Type BTS basic attributes Parameter ID BTSNAME TYPE UPNODE Parameter Name BTS Name BTS Type Up Node Type Example BTS3012 BTS3012 BSC Source Network planning Network planning Network planning
9-1
Issue 01 (2010-05-20)
9 Configuring eMLPP
Data Type
Parameter ID SRN SN PN BTSDESC MPMODE FlexAbisMode AbisByPassMod e ServiceMode DCELLNAME DCTYPE DCMCC DCMNC DCLAC DCCI CPLMode TRXBN FREQ
Parameter Name Subrack No. Slot No. Port No. BTS Description Multiplexing Mode Flex Abis Mode Abis By Pass Mode Service Type Cell Name Cell type Cell MCC Cell MNC Cell LAC Cell CI Separate Mode TRX Board No. TRX Freq. 0 26 0
Example
Source Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning
TDM BTS3012 MODE4_1 FLEX_ABIS(Flex Abis) FALSE(Not Support) TDM TDMCELL GSM900 460 34 62 98 UNSUPPORT(Not Support) 0 5
9-2
Issue 01 (2010-05-20)
9 Configuring eMLPP
Table 9-2 Example of the data negotiated and planned for configuring eMLPP Data Type GSM-R Parameters of the cell Parameter ID IDXTYPE CELLNAME EMLPPPRIORIT Y Basic call control parameters of the cell EMLPPEN Parameter Name Index Type Cell Name eMLPP Priority Allow EMLPP Example BYNAME (By Name) TDMCELL Priority2 (Priority 2) YES(YES) Source Network planning Network planning Network planning Network planning
Procedure
Step 1 On the Local Maintenance Terminal, run the ADD BTS command to add a BTS. Step 2 On the Local Maintenance Terminal, run the MOD CELLGSMR command to configure eMLPP priority.
NOTE
Priority4(Priority 4) is the highest priority whereas PriorityB(Priority B) is the lowest priority.
Step 3 On the Local Maintenance Terminal, run the MOD CELLCCBASIC command to set Allow EMLPP to YES(YES) to enable the eMLPP function. ----End
Example
An example script for configuring eMLPP for a BTS3012 in TDM transmission mode is as follows:
/*Add a BTS3012*/ ADD BTS: BTSNAME = "BTS3012", TYPE = BTS3012, UPNODE = BSC, SRN = 0, SN=26, PN = 10, BTSDESC = "TDM BTS3012" , MPMODE = MODE4_1, FlexAbisMode = FLEX_ABIS, AbisByPassMode = False, ServiceMode = TDM,DCELLNAME = "TDMCELL ", DCTYPE = GSM900, DCMCC = "460", DCMNC = "34", DCLAC = 62, DCCI = 98, CPLMode = UNSUPPORT, TRXBN = 0, FREQ = 5; /*Configure eMLPP*/ MOD CELLGSMR: IDXTYPE=BYNAME, CELLNAME="TDMCELL", EMLPPPRIORITY = Priority2; /*Enable the eMLPP function*/ MOD CELLGSMR: IDXTYPE=BYNAME, CELLNAME="TDMCELL", EMLPPEN=YES;
Postrequisite
l
Verifying eMLPP 1. The priorities of the MSs in the HLR are as follows: MS 1 > MS 2 > MS 3.
Issue 01 (2010-05-20)
9 Configuring eMLPP
2. 3.
Ensure that a higher-priority MS can preempt the channel used by a lower-priority MS by configuring the data on the MSC side. Choose Trace Message on the A Interface > BSSAP Message and Trace Message on the Abis Interface > RSL Message. For details, see Tracing BSSAP Messages on the A Interface and Tracing RSL Messages on the Abis Interface in the BSC LMT User Guide. In the test cell, use MS 2 and MS 3 separately to make a call to the PSTN. On the Local Maintenance Terminal, run the SET BTSOBJ command to block the remaining idle TCHs in the cell. Use MS 1 to make a call to the PSTN. MS 3 is found to be handed over to other cells. If the handover fails, the channel used by MS 3 is released and then occupied by MS 1. The call initiated by MS 2 is not affected.
NOTE
4. 5. 6.
When the eMLPP function is enabled, whether an MS with a lower priority can be handed over to another cell is determined by whether the neighboring cell relations is configured correctly (the configuration of the neighboring cell relations is not involved in the configuration of the eMLPP function). In addition, when the eMLPP function is enabled, the data configuration on the CN side must be correct, and the configuration relations included in the Priority information element (IE) of the assignment request message, which indicates the MS that can be preempted, must comply with the priorities. The assignment request message can be viewed in the A interface tracing window.
l
Deactivating eMLPP 1. 2. On the Local Maintenance Terminal, run the MOD CELLCCBASIC command to set Allow EMLPP to NO(NO). Verifying deactivation of eMLPP: The method of verifying the deactivation of the eMLPP function is identical to that of verifying the eMLPP function. Use MS 1 to make a call to the PSTN. The channel used by MS 3 is released (no handover attempt) and then occupied by MS 1. The call initiated by MS 2 is not affected.
9-4
Issue 01 (2010-05-20)
10 Configuring Priority-Based Resource Reservation
10
Configuring Priority-Based Resource Reservation
With priority-based resource reservation, the system reserves a certain number of TCHFs for the high-priority users to ensure their QoS. By using this function, operators can provide services of different levels for users with different priorities, thus increasing the operators' revenues. Scenario Impact The priority-based resource reservation function is configured to provide services of different levels for users with different priorities. The priority-based resource reservation function can be combined with the eMLPP function to guarantee the benefits of users and improve the users' satisfaction.
NEs Involved BSC, BTS, and MS
Prerequisite
l l
The priority-based resource reservation function is license-controlled. Activate the license on the Local Maintenance Terminal. For details, see Activate BSC License.
Preparation
Table 10-1 Example of the data negotiated and planned for configuring priority-based resource reservation Parameter ID IDXTYPE CELLNAME GRADEACCALLO W HPRIOR
Issue 01 (2010-05-20)
Parameter Name Index Type Cell Name Grade Access Allow Highest Priority
Example BYNAME(By Name) CELL01 YES(YES) 2
Source Network planning Network planning Network planning Network planning

10-1
10 Configuring Priority-Based Resource Reservation
Parameter ID REVCHANNUM
Parameter Name Reserved Channel Number
Example 50
Procedure
Step 1 On the Local Maintenance Terminal, run the SET CELLCHMGBASIC command to set Grade Access Allow to YES(YES). In addition, set Highest Priority and Reserved Channel Number based on the actual network conditions. ----End
Example
An example script for configuring priority-based resource reservation is as follows:
/*Configure priority-based resource reservation*/ SET CELLCHMGBASIC: IDXTYPE=BYNAME, CELLNAME="CELL01", MINRESTIMETCH=60, GRADEACCALLOW=YES, HPRIOR=2, REVCHANNUM=50;
Postrequisite
l
Verifying priority-based resource reservation
On the Local Maintenance Terminal, run the LST CELLCHMGBASIC command to check the setting of Grade Access Allow. If the parameter is set to YES, it indicates that the function of priority-based resource reservation is activated. On the Local Maintenance Terminal, run the SET CELLCHMGBASIC command to set Grade Access Allow to NO(NO). On the Local Maintenance Terminal, run the LST CELLCHMGBASIC command to check the setting of Grade Access Allow. If the parameter is set to NO, it indicates that the function of priority-based resource reservation is deactivated.
Deactivating priority-based resource reservation 1. 2.
10-2
Issue 01 (2010-05-20)
11 Configuring Network Support SAIC
11
Configuring Network Support SAIC
This describes how to configure the Network Support SAIC. The Single Antenna Interference Cancellation (SAIC) is a technique for restraining the co-channel interference and adjacentchannel interference. This technique is especially adopted in the single antenna scenario to reduce the interference on the reception of downlink signals. Scenario The transmit power of the BTS that serves the MS supporting the SAIC can be reduced on the network side. In this way, the interference on the entire network is reduced. None.
Impact
Prerequisite
l l
The Network Support SAIC function is license-controlled. Activate the license on the Local Maintenance Terminal. For details, see Activate BSC License. The MS supports the SAIC function.
Preparation
The MS supporting the SAIC function has a stronger anti-interference capability. Therefore, the range of the power control threshold can be adjusted according to the following policies during the power control of the BSC or the BTS.
l
When Huawei II power control algorithm is applied, the value of Power Control threshold Adjust for SAIC should be added to that of DL Qual. Upper Threshold and DL Qual. Lower Threshold. When Huawei III power control algorithm is applied, the value of HW3 threshold Adjust for SAIC should be subtracted from that of HW3DL**RexQualHighThred[dB] and HW3DL**RexQualLowThred[dB]. ** indicates full-rate services (FS), half-rate services (HS), AMR full-rate services (AFS), or AMR half-rate services (AHS) in different situations.
Issue 01 (2010-05-20)
11-1
Table 11-1 Example of the data negotiated and planned for configuring the Network Support SAIC Parameter ID IDXTYPE CELLNAME BTSSAICPCADJSWITCH Parameter Name Index Type Cell Name Switch for BTS Supporting SAIC Power Control Adjustment Power Control Switch Saic Allowed Example BYNAME(By Name) CELL01 ON(ON) Source Network planning Network planning Network planning
PWRCTRLSW SAICALLOWED
HW3(HW3 Power Control) YES(YES)
Network planning Network planning
Procedure
Step 1 On the Local Maintenance Terminal, run the SET CELLSOFT command, and then set Switch for BTS Supporting SAIC Power Control Adjustment to ON(ON). Step 2 On the Local Maintenance Terminal,run the MOD CELLPWRBASIC command, and then set Power Control Switch to HW3(HW3 Power Control) and set Saic Allowed to YES (YES). Step 3 On the Local Maintenance Terminal, run the MOD CELLPWRHW3 command, and then set HW3 threshold Adjust for SAIC to 2.
NOTE
When Huawei III power control algorithm is applied, run the MML command MOD CELLPWRHW2, and then set Power Control threshold Adjust for SAIC.
----End
Example
An example script for configuring the Network Support SAIC is as follows:
/*Configure Network Support SAIC*/ SET CELLSOFT: IDXTYPE=BYNAME, CELLNAME="CELL01", BTSSAICPCADJSWITCH=ON; MOD CELLPWRBASIC: IDXTYPE=BYNAME, CELLNAME="CELL01", PWRCTRLSW=HW3, SAICALLOWED=YES; MOD CELLPWRHW3: IDXTYPE=BYNAME, CELLNAME="CELL01", DLFSREXQUALHIGHTHRED=18, DLFSREXQUALLOWTHRED=14, DLHSREXQUALHIGHTHRED=18, DLHSREXQUALLOWTHRED=18, DLAFSREXQUALHIGHTHRED=14, DLAFSREXQUALLOWTHRED=14, DLAHSREXQUALHIGHTHRED=16, DLAHSREXQUALLOWTHRED=16, HW3SAICTHREDAPDTVALUE=2;
Postrequisite
l
Verifying network support SAIC

11-2
1. 2. 3.
l
Start the tracing of RSL messages on the Abis interface. For details, see Tracing RSL Messages on the Abis Interface in the BSC LMT User Guide. Use an MS occupying the non-BCCH to make a call to a fixed-line phone in the test cell. Verify that the value of the SAIC information element in the MS capability field carried in the Channel Activation message is 1. On the Local Maintenance Terminal,run the MOD CELLPWRBASIC command, and set Saic Allowed to NO(NO). Verifying the deactivation of network support SAIC: The operations are the same as those for Verifying Network Support SAIC. Verify that the value of the SAIC information element in the MS capability field carried in the Channel Activation message is 0.
Deactivating network support SAIC 1. 2.
Issue 01 (2010-05-20)
11-3
12 Configuring Active Power Control
12
Scenario Impact
Configuring Active Power Control
This describes how to configure the active power control. After an MS accesses the network or an intra-BSC handover is performed successfully, the BSC controls the uplink and downlink power so that the MS and the BTS transmit signals at the proper power. In this way, power control can be performed in time. Through the active power control, the system interference is reduced, the QoS is improved, and the power consumption of the BTS and the MS is decreased. The active power control is enabled to control the transmit power of the BTS and the MS so that the system interference is reduced and the QoS is improved. None.
Preparation
Table 12-1 Example of the data negotiated and planned for configuring the active power control Parameter ID IDXTYPE CELLNAME PWRBCDALLOW D COMBINERLOSS DOUBLEANTENN AGAIN PATHLOSS Parameter Name Index Type Cell Name Power Forecast Allowed Combiner Loss (0.1dB) Double Antenna Gain(0.1dB) Path Loss of Different Frequency Band(0.1dB) Expected DL RX_LEV Example BYNAME(By Name) CELL01 YES(YES) 50 200 150 Source Network planning Network planning Network planning Network planning Network planning Network planning
EXPDLRXLEV
20
Network planning
Issue 01 (2010-05-20)
12-1
12 Configuring Active Power Control
Parameter ID EXPULRXLEV
Parameter Name Expected UL RX_LEV
Example 30
Procedure
Step 1 On the Local Maintenance Terminal, run the MOD CELLPWRBASIC command. Then, set Power Forecast Allowed to YES(YES) and set the following parameters according to the actual conditions of the existing network: Combiner Loss(0.1dB), Double Antenna Gain(0.1dB), Path Loss of Different Frequency Band(0.1dB), Expected DL RX_LEV, and Expected UL RX_LEV. ----End
Example
An example script for configuring the active power control is as follows:
/*Configure the active power control*/ MOD CELLPWRBASIC: IDXTYPE=BYNAME, CELLNAME="CELL01", PWRBCDALLOWD=YES, COMBINERLOSS=50, DOUBLEANTENNAGAIN=200, PATHLOSS=150, EXPDLRXLEV=20, EXPULRXLEV=30;
Postrequisite
l
Verifying active power control 1. 2. Start the tracing of RSL messages on the Abis interface. For details, see Tracing RSL Messages on the Abis Interface in the BSC LMT User Guide. Verify that the values of power-level in the ms-power and bs-power information elements in the Channel Activation messages are greater than those when the active power control function is disabled. On the Local Maintenance Terminal, run the MOD CELLPWRBASIC command to set Power Forecast Allowed to NO(NO). On the Local Maintenance Terminal, run the LST CELLPWRBASIC command to check the setting of Power Forecast Allowed. If the parameter is set to NO, it indicates that the function of active power control is deactivated.
Deactivating active power control 1. 2.
12-2
Issue 01 (2010-05-20)
13 Configuring Robust Air Interface Signalling
13
Scenario
Configuring Robust Air Interface Signalling
With the robust air interface signalling function, when the radio quality is poor, the antiinterference capability of the FACCH and SACCH is improved through repeated sending of the FACCH and SACCH frames. In this manner, the MS and BSC can receive the signaling messages more successfully. The robust air interface signalling function includes repeated sending of the FACCH frames in the downlink and the repeated sending of the SACCH frames in the uplink and downlink. The robust air interface signalling function helps to improve the performance of the FACCH and SACCH , thus reducing the call drop rate of the MS and improving the accuracy of the BSC handover and power control decision. The speech quality is slightly affected because the signaling messages are repeatedly sent through frame stealing.
Impact
Prerequisite
l l
The robust air interface signalling function is license-controlled. Activate the license on the Local Maintenance Terminal. For details, see Activate BSC License.
Preparation
Table 13-1 Example of the data negotiated and planned for configuring the robust air interface signalling function Parameter ID IDXTYPE CELLNAME Parameter Name Index Type Cell Name Example BYNAME(By Name) CELL01 Source Network planning Network planning
Issue 01 (2010-05-20)
13-1
13 Configuring Robust Air Interface Signalling
Parameter ID REPEATDLFASET REPEATDLFATHR ED REPEATSASET
Parameter Name Repeated Downlink FACCH Repeated Downlink FACCH Threshold Repeated SACCH
Example YES(YES) 5 YES(YES)
Source Network planning Network planning Network planning
Procedure
Step 1 On the Local Maintenance Terminal, run the MOD CELLCCBASIC command to set Repeated Downlink FACCH to YES(YES), and Repeated SACCH to YES(YES). In addition, set Repeated Downlink FACCH Threshold based on the actual conditions of the network. ----End
Example
An example script for configuring the robust air interface signalling function is as follows:
/*Configure robust air interface signalling*/ MOD CELLCCBASIC: IDXTYPE=BYNAME, CELLNAME="CELL01", REPEATDLFASET=YES, REPEATDLFATHRED=5, REPEATSASET=YES;
Postrequisite
l
Verifying robust air interface signalling
On the Local Maintenance Terminal, run the LST CELLCCBASIC command to check the setting of Repeated Downlink FACCH and Repeated SACCH. If the two parameters are set to YES, it indicates that the function of robust air interface signalling is activated. On the Local Maintenance Terminal, run the MOD CELLCCBASIC command to set Repeated Downlink FACCH and Repeated SACCH to NO(NO). On the Local Maintenance Terminal, run the LST CELLCCBASIC command to check the settings of Repeated Downlink FACCH and Repeated SACCH. If the two parameters are set to NO, it indicates that the function of robust air interface signalling is deactivated.
Deactivating robust air interface signalling 1. 2.
13-2
Issue 01 (2010-05-20)
14 Configuring BSS Paging Coordination
14
Configuring BSS Paging Coordination
With the BSS paging coordination function, the network can send the CS domain paging message to an MS in the packet transfer state on the PACCH if the Gs interface is not configured between the MSC/VLR and the SGSN. In this manner, the MS in the packet transfer state can respond to the CS domain paging. Scenario Impact In the network with a lot of PS services, the BSS paging coordination function helps to increase the paging success rate if no Gs interface is configured. None.
NEs Involved BSC
Prerequisite
l l
The BSS paging coordination function is not license-controlled. This function is implemented in built-in PCU mode.
Preparation
Table 14-1 Example of the data negotiated and planned for configuring the BSS paging coordination function Parameter ID ACOOPERATPAGINGSWITCH IDXTYPE CELLNAME BSSPAGINGCOOR DINATION Parameter Name A Interface Collaboration Paging Switch Index Type Cell Name BSS Paging Coordination Example OPEN(Open) Source Network planning
BYCELLNAME(By Cell Name) CELL01 YES(YES)
Issue 01 (2010-05-20)
14-1
14 Configuring BSS Paging Coordination
Procedure
Step 1 On the Local Maintenance Terminal, run the SET PSSOFTPARA command to set A Interface Collaboration Paging Switch to OPEN(Open). Step 2 On the Local Maintenance Terminal, run the SET PSBASE command to set BSS Paging Coordination to YES(YES). ----End
Example
An example script for configuring the BSS paging coordination function is as follows:
/*Configure BSS paging coordination*/ SET PSSOFTPARA: ACOOPERATPAGINGSWITCH=OPEN; SET PSBASE: IDXTYPE=BYCELLNAME, CELLNAME="CELL01", BSSPAGINGCOORDINATION=YES;
Postrequisite
l
Verifying BSS paging coordination
On the Local Maintenance Terminal, run the LST PSBASE command. If BSS Paging Coordination is set to YES, it indicates that the function of BSS paging coordination is activated. On the Local Maintenance Terminal, run the SET PSBASE command to set BSS Paging Coordination to NO(NO). On the Local Maintenance Terminal, run the LST PSBASE command. If BSS Paging Coordination is set to NO, it indicates that the function of BSS paging coordination is deactivated.
Deactivating BSS paging coordination 1. 2.
14-2
Issue 01 (2010-05-20)
15 Configuring a Co-BCCH Cell
15
About This Chapter
Configuring a Co-BCCH Cell
Co-BCCH cell is realized on the basis of the principles of the concentric cell. The TRXs on the GSM900M (or GSM850M) are configured in the underlaid subcell, which is used to expand the coverage area; and the TRXs on the DCS1800M (or PCS1900M) are configured in the overlaid subcell, which is used to absorb the traffic. The TRXs on two bands are distributed in the overlaid subcell and underlaid subcell that share one BCCH TRX. Co-BCCH cell increases the traffic capacity of a cell, decreases handovers and interference, and improves the continuous coverage and sparse coverage in hot spots. 15.1 Co-BCCH Cell Configuration Principles This describes the configuration principles of the co-BCCH cell. 15.2 Preparations for the Co-BCCH Cell Configuration Before configuring a co-BCCH cell, get familiar with the related information based on which the parameters are set. 15.3 Configuring a Co-BCCH Cell This describes how to configure a co-BCCH cell on the Local Maintenance Terminal.
Issue 01 (2010-05-20)
15-1
15.1 Co-BCCH Cell Configuration Principles

This describes the configuration principles of the co-BCCH cell. A co-BCCH cell consists of an overlaid subcell and an underlaid subcell. The specific band configuration is as follows:
l
If the overlaid subcell is configured in the DCS1800M, the underlaid subcell is configured in the GSM900M or GSM850M. If the overlaid subcell is configured in the PCS1900M, the underlaid subcell is configured in the GSM850M.
NOTE
The signal loss of the DCS1800M is faster with the transmission distance. At the distance of 0.5-1 km, the signal power of the DCS1800M is about 15 dB less than the signal power of the GSM900M.
The configuration of the co-BCCH cell should comply with the following principles:
l
Generally, the overlaid subcell channel is not directly assigned to a call, the incoming intercell handover request is not directly assigned to the overlaid subcell, and a call beyond the coverage of the DCS1800M TRX is not forcibly assigned to the overlaid subcell. The traffic in the underlaid subcell and the overlaid subcell should be properly assigned to maintain the traffic balance between the overlaid subcell and the underlaid subcell. Generally, the GSM900M or GSM850M is configured in the underlaid cell to expand the coverage, whereas the DCS1800M or PCS1900M is configured in the overlaid cell to absorb the traffic. Configure the BCCH in the GSM900M TRX. The priorities of different types of TRXs are: P-GSM > E-GSM > R-GSM. Configure the SDCCH, PDCH, and BCCH on the same TRX. The frequency hopping between the GSM900M and the DCS1800M is not allowed. The frequency hopping within the same frequency band is allowed. Avoid a multi-layer concentric cell due to inconsistent combination mode of the TRXs on the same frequency band. A multi-layer concentric cell affects the network KPIs, such as handover success rate and assignment success rate.
l l
15.2 Preparations for the Co-BCCH Cell Configuration

Before configuring a co-BCCH cell, get familiar with the related information based on which the parameters are set. Get familiar with the status of the current cell, including the following items:
l l l l l
Subscriber distribution and traffic volume in the coverage of the site Ratio of the coverage of the DCS1800/PCS1900 to that of the entire cell Ratio of the coverage of the GSM900/GSM850 to that of the entire cell Whether the TRXs in the GSM900/GSM850 can carry all the traffic in the cell Number of the TRXs in the GSM900/GSM850 and DCS1800/PCS1900 in the co-BCCH cell; whether the frequency reuse on the GSM900/GSM850 is tight and whether interference exists
During network planning, the following restrictions apply:

l
Number of TRXs
If the traffic is distributed mainly in the overlaid subcell, the congestion is unlikely to occur in the underlaid subcell. Therefore, the number of TRXs configured in the underlaid subcell can be small. If the traffic volume in the underlaid subcell is high, the number of TRXs in the underlaid subcell should be greater or be equal to that in the overlaid subcell to prevent the congestion in the underlaid subcell. If the TRXs in the underlaid subcell are not sufficient, the congestion is likely to occur in a fully-loaded cell at high traffic hours. The network KPIs such as TCH Seizure Success Rate and Handover Success Rate deteriorate. If the co-BCCH cell is not adjacent to two or more single-band cells at the same time, this factor is negligible. Otherwise, you should consider the network hierarchy. If the co-BCCH cell has a low priority, this factor is negligible.
Neighboring cell
If the co-BCCH cell has a high priority, you should consider the traffic load of the neighboring cells. If the traffic load of neighboring cells is high, the traffic distributed on the edge of a common cell is switched to the co-BCCH cell. Thus, the underlaid subcell in the co-BCCH cell is likely to be congested and the network KPIs such as TCH Seizure Success Rate and Handover Success Rate deteriorate. In such a case, the co-BCCH cell is not recommended. If the co-BCCH cell has to be used, you should analyze the traffic distribution based on the congestion conditions in the underlaid subcell and then adjust the handover parameters of related cells. The purpose is to prevent the calls on the edge of a common cell from being handed over to the co-BCCH cell.
15.3 Configuring a Co-BCCH Cell

This describes how to configure a co-BCCH cell on the Local Maintenance Terminal. Scenario Impact Co-BCCH cell improves the traffic capacity of a cell. None
NEs Involved BSC, BTS
Prerequisite
l l l l l
Co-BCCH cell is not restricted by the license. The BTS that adds a co-BCCH cell must support the configured frequency band. The BTS and MS should support the co-BCCH cell. The serving BSC has enabled the concentric cell function. The co-BCCH cell function and the extended cell function cannot be enabled at the same time.
Issue 01 (2010-05-20)
15-3
Preparation
Table 15-1 Example of the data negotiated and planned for configuring a co-BCCH cell Data Type Cell attributes Parameter ID IDXTYPE BTSIDX CELLNAME CTYPE AST MCC MNC LAC CI TRXBN TRXFREQ BSC basic attributes Basic call control parameters of the cell HiFreqBandSupport CELLIDX ASSLOADJUDG EEN MSMAXRETRA N ERGCALLDIS ECSC Parameter Name Index Type BTS Index Cell Name Freq. Band Activity State MCC MNC LAC CI TRX Board No. TRX Freq. Support High Frequency Band Cell Index Assignment Cell Load Judge Enable MS MAX Retrans Emergent Call Disable ECSC Example BYIDX(By Index) 0 cell GSM900_DCS1 800 ACTIVATED (Activated) 460 00 1 1 0 1 PCS1900 0 ENABLE (ENABLE) 2_Times (2_Times) NO(NO) NO(NO) Source Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning
15-4
Issue 01 (2010-05-20)
Data Type
Parameter ID REASSEN
Parameter Name Allow Reassign Cell IUO Type Enhanced Concentric Allowed BCCH IUO of Double Freq Cell Current HO Control Algorithm UL to OL HO Allowed OL to UL HO Allowed RX_LEV for UO HO Allowed RX_QUAL for UO HO Allowed TA for UO HO Allowed
Example YES(Yes) Concentric_cell (Concentric cell) YES(Yes)
Source Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning
Cell concentric attributes
IUOTP ENIUO
DBFREQBCCHIU O Cell concentric handover parameters HOCTRLSWITC H ULTOOLHOALL OW OLTOULHOALL OW RECLEVUOHOA LLOW RECQUALUOHO ALLOW TAFORUOHOAL LOW
Extra(Extra) HOALGORITH M1(HO Algorithm I) NO(NO) YES(Yes) YES(Yes) NO(NO) YES(Yes)
Procedure
Step 1 (Optional) When you select GSM850_1900, you should modify the BSC attributes. On the Local Maintenance Terminal, run the MOD BSCBASIC command to set Support High Frequency Band to PCS1900.
NOTE
If the cell to be added is in the GSM900_DCS1800 or GSM850_1800, skip this step.
Step 2 On the Local Maintenance Terminal, run the ADD CELL command to add a co-BCCH cell. Set Freq. Band to GSM900_DCS1800,GSM850_1800 or GSM850_1900. Step 3 On the Local Maintenance Terminal, run the MOD CELLCCBASIC command to configure the basic call parameters of the cell according to the actual network condition. Step 4 On the Local Maintenance Terminal, run the MOD CELLIUO command to configure cell concentric attributes. Set Cell IUO Type to Concentric_cell(Concentric cell), and then set Enhanced Concentric Allowed and BCCH IUO of Double Freq Cell according to the actual network condition. It is recommended that BCCH IUO of Double Freq Cell be set to Extra (Extra).
Step 5 On the Local Maintenance Terminal, run the SET CELLHOIUO command to configure concentric handover parameters of the cell according to the actual network condition. ----End
Example
An example script for adding a co-BCCH cell is as follows:
/*(Optional) When you select "GSM850_1900", you should modify the BSC attributes. Set "Support High Frequency Band" to "PCS1900".*/ MOD BSCBASIC: HiFreqBandSupport=PCS1900; /*Add a co-BCCH cell in the GSM900_DCS1800*/ ADD CELL: IDXTYPE=BYIDX, BTSIDX=0, CELLNAME="cell", CTYPE=GSM900_DCS1800, AST=ACTIVAED, MCC="460", MNC="00", LAC=1, CI=1, TRXBN=0, TRXFREQ=1; /*Configure the basic call control parameters of the cell*/ MOD CELLCCBASIC: IDXTYPE=BYIDX, CELLIDX=0, ASSLOADJUDGEEN=ENABLE, MSMAXRETRAN=2_Times, ERGCALLDIS=NO, ECSC=NO, REASSEN=YES; /*Configure cell concentric type*/ MOD CELLIUO: IDXTYPE=BYIDX, CELLIDX=0, IUOTP=Concentric_cell, ENIUO=YES, DBFREQBCCHIUO=Extra; /*Configure concentric handover parameters of the cell*/ SET CELLHOIUO: IDXTYPE=BYIDX, CELLIDX=0, HOCTRLSWITCH=HOALGORITHM1, ULTOOLHOALLOW=NO, OLTOULHOALLOW=YES, RECLEVUOHOALLOW=YES, RECQUALUOHOALLOW=NO, TAFORUOHOALLOW=YES;
Postrequisite
l
Verifying co-BCCH cell

NOTE
In this section, the verification of a GSM900&DCS1800 co-BCCH cell is taken as an example. The verification of the co-BCCH cell with other frequency bands combined is similar.
1. 2. 3.
Use an MS supporting the GSM900 frequency band to camp on a 900 MHz cell. Perform the dialing test. The call is normally connected. Use an MS supporting the DCS1800 frequency band to camp on a 1800 MHz cell. Perform the dialing test. The call is normally connected. Use an MS supporting the GSM900 and DCS1800 frequency bands to camp on a 900 MHz cell. Perform the dialing test. After the call is connected, move the MS towards the 1800 MHz cell. Then, observe the window displaying the monitored channel status. The MS is handed over to the 1800 MHz cell, and the call is still normally connected.
15-6
Issue 01 (2010-05-20)
16 Configuring 2G/3G Interoperability
16
Configuring 2G/3G Interoperability
The 2G/3G interoperability feature enables an MS to be handed over to or reselected to the GSM network if the serving cell of the MS is not covered by the WCDMA/TD-SCDMA network or if the serving WCDMA/TD-SCDMA cell is in a weak coverage area. In addition, an MS can be handed over to or reselected to the WCDMA/TD-SCDMA network if the MS requires the PS services. When a dual-mode MS enters the coverage of the WCDMA/TD-SCDMA network again, or the MS detects that the WCDMA/TD-SCDMA cell is better than the serving GSM cell, the MS can be handed over to or reselected to the WCDMA/TD-SCDMA network if the handover or cell reselection conditions are met. Then, the MS can use the abundant services provided by the WCDMA/TD-SCDMA network. Scenario This feature is used for the MS reselection and handovers between the GSM network and the WCDMA/TD-SCDMA network, and the interactions between the GSM network and other 3G networks. None
Impact
NEs Involved MS, BTS, BSC, MSC
Prerequisite
l
The MS must be a dual-mode MS, which supports the GSM and WCDMA/TD-SCDMA networks. The MS must support bidirectional (2G to 3G and 3G to 2G) cell reselection and handovers. A Interface Tag, Um Interface Tag, and Abis Interface Tag are all set to GSM_PHASE_2Plus. 2G/3G interoperability requires the support of the BSS and NSS. The NSS and BSS must support inter-RAT cell selection, cell reselection, location update procedures, flow control during inter-RAT handovers, handover decisions, and handover signaling procedures. The configuration of 2G/3G interoperability is license-controlled. Activate the license on the Local Maintenance Terminal. For details, see Activate BSC License.
l l
Preparation
The procedure for configuring GSM/WCDMA interoperability is similar to the procedure for configuring GSM/TD-SCDMA interoperability. The configuration of GSM/TD-SCDMA interoperability is taken as an example. The negotiated and planned data is as follows:
Table 16-1 Example of the data negotiated and planned for configuring the GSM/TD-SCDMA Interoperability Parameter Cell Name Cell MCC Cell MNC Cell LAC Cell CI Utran cell type Sync case Load Handover Support Load Req.on Candidate Cell Index Type Cell Name MSC Version indication HO Control Switch Inter-RAT Out BSC Handover Enable Inter-RAT In BSC Handover Enable Inter-RAT Cell Reselection Enable TDD System Information Optimized Allowed TDD MI System Information Broadcasting Prohibit Qsearch I Qsearch P Qsearch C TDD cell reselect diversity [db] ECSC Example 3G External Cell-1 460 86 10 11 TDD(TDD) SyncCase1(Sync case 1) YES(YES) 50 BYNAME (By Name) CELL_1 R99_or_above(R99 or above) HOALGORITHM2(HO Algorithm II) YES(YES) YES(YES) YES(YES) YES(YES) YES(YES) Source Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning
5 5 5 5 YES(YES)
Network planning Network planning Network planning Network planning Network planning
16-2
Issue 01 (2010-05-20)
Procedure
Step 1 Run the ADD CELL3GEXTC command to add a 3G external cell. Set Utran cell type to TDD (TDD),Sync case to SyncCase1 (Sync case 1).
NOTE
l l
The value of Sync case must be the same as that set for the source 3G cell. If the 2G/3G Interoperability is required, set Utran cell type to FDD(FDD) and set the following parameters according to the network condition: Ec/No threshold for layer Of 3G cell, Min Ec/No threshold, and PS FDD Ec/No Quality Threshold.
Step 2 Run the SET CELLHOBASIC command to configure the 2G cell handover parameters. Set Inter-RAT Cell Reselection Enable to YES(YES), Inter-RAT Out BSC Handover Enable to YES(YES), and Inter-RAT In BSC Handover Enable to YES(YES).
l
If the inter-RAT load handover function needs to be configured, set Load HO Allowed to YES(YES). In addition, run the SET CELLHOAD command to set Inter RAN Load Information Allowed to YES(YES). If the inter-RAT service handover function needs to be configured, you should also run the SET OTHSOFTPARA command to set Service Based Handover Switch to OPEN (Open).
Step 3 According to the type of the 3G external cells that perform interoperability, run the MOD CELLHOUTRANFDD or MOD CELLHOUTRANTDD command to configure the data relevant to the handover from the GSM system to the WCDMA/TD-SCDMA system. Step 4 Run the MOD CELLCCUTRANSYS command to configure the cell call control parameters. 1. Set MSC Version indication to R99_or_above(R99 or above) and set the following parameters according to the current network condition: Qsearch I, Qsearch P, and Qsearch C.
NOTE
If Utrancell type is set to FDD(FDD), skip Step b. Then, set FDD Q offset according to the current network condition.
2.
Based on the current cell type, set TDD System Information Optimized Allowed to YES (YES) and TDD MI System Information Broadcasting Prohibit to YES(YES). Then, set TDD cell reselect diversity according to the network condition.
Step 5 Run the MOD CELLCCBASIC command to set ECSC to YES(YES). Step 6 Run the ADD CELL3GNC command to configure the neighboring cell relations. Then, set RSCP Offset according to the network condition.
NOTE
If Utrancell type is set to FDD(FDD), set Ec/No Offset according to the network condition.
----End
Example
/*Add a 3G external cell*/ ADD CELL3GEXTC: CELLNAME="3G External Cell-1 ", MCC="460", MNC="86", LAC=10, CI=11, SYNCCASE=SyncCase1, UTRANCELLTYPE=TDD,LoadHoEn=YES, LoadAccThres=50; /*Configure the cell handover parameters*/ SET CELLHOBASIC: IDXTYPE=BYNAME, CELLNAME="CELL_1", HOCTRLSWITCH=HOALGORITHM2, INTERRATOUTBSCHOEN=NO, INTERRATINBSCHOEN=YES, INTERRATCELLRESELEN=YES;
Issue 01 (2010-05-20)
16-3
/*Configure the cell call parameters*/ MOD CELLCCUTRANSYS: IDXTYPE=BYNAME, CELLNAME="CELL_1", MSCVER=R99_or_above, QI=5, QP=5, QSEARCHC=5, TDDCELLRESELDIV=5, TDDSIOPTIMIZEDALLOWED=YES, TDDMIPROHIBIT=YES; MOD CELLCCBASIC: IDXTYPE=BYNAME, CELLNAME="3G External Cell-1", ECSC=YES; /*Configure the neighboring cell relations*/ ADD CELL3GNC: IDXTYPE=BYNAME, SRCCELLNAME="CELL_1", NBRCELLNAME="3G External Cell-1";
Postrequisite
l
Verifying 2G/3G interoperability 1. 2. Start the tracing of the RSL messages over the Abis interface. For details, see Tracing BSSAP Messages on the A Interface in the BSC LMT User Guide. Query the CS-related BCCH Information messages over the Abis interface to identify the messages whose system-info-type is system-information-2quater. Then, check whether the L3 contents of the messages are null. If they are not null, it indicates that 2G/3G inter-RAT reselection takes effect. Query the CS-related SACCH Filling messages over the Abis interface to identify the messages whose system-info-type is measurement-information. Then, check whether the L3 contents of the messages are null. If they are not null, it indicates that 2G/3G inter-RAT handover takes effect. On the Local Maintenance Terminal, run the SET CELLHOBASIC command to set Inter-RAT Cell Reselection Enable to NO(NO), Inter-RAT Out BSC Handover Enable to NO(NO), and Inter-RAT In BSC Handover Enable to NO (NO). Verifying the deactivation of 2G/3G interoperability: The operations are the same as those for Verifying deactivation of 2G/3G interoperability. Check the L3 contents of the messages are null.
3.
Deactivating 2G/3G interoperability 1.
2.
16-4
Issue 01 (2010-05-20)
17 Configuring TRX Cooperation
17
Configuring TRX Cooperation
With this feature, when the BCCH TRX or the TRX involved in baseband FH is faulty, the cell automatically rectifies the faults. Thus, the services in the cell are not affected before the faulty TRX is replaced. Based on the type of faulty TRXs and the handling method, the TRX cooperation is classified into BCCH TRX cooperation and baseband FH TRX cooperation. For the non-baseband FH cell, only the BCCH TRX cooperation occurs. For the baseband FH cell, both BCCH TRX cooperation and baseband FH TRX cooperation are likely to occur. TRX Cooperation is configured to ensure that the cell is always in service.
NEs Involved BTS, BSC
Prerequisite
l l
TRX Cooperation is not restricted by the license. At least two TRXs are configured in the cell.
Preparation
Take the configuration of BTS3012 in TDM transmission mode as an example. Table 17-1 Example of the data negotiated and planned for adding a BTS Parameter ID BTSNAME TYPE UPNODE SRN Parameter Name BTS Name BTS Type Up Node Type Subrack No. Example BTS3012 BTS3012 BSC 0 Source Network planning Network planning Network planning Network planning
17-1
Issue 01 (2010-05-20)
Parameter ID SN PN BTSDESC MPMODE FlexAbisMode AbisByPassMode ServiceMode DCELLNAME DCTYPE DCMCC DCMNC DCLAC DCCI CPLMode TRXBN FREQ
Parameter Name Slot No. Port No. BTS Description Multiplexing Mode Flex Abis Mode Abis By Pass Mode Service Type Cell Name Cell type Cell MCC Cell MNC Cell LAC Cell CI Separate Mode TRX Board No. TRX Freq.
Example 26 10 TDM BTS3012 MODE4_1 FIX_ABIS(Fix Abis) FALSE(Not Support) TDM TDMCELL GSM900 460 34 62 98 UNSUPPORT(Not Support) 0 5
Source Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning
17-2
Issue 01 (2010-05-20)
Table 17-2 Example of the data negotiated and planned for configuring TRX Cooperation Parameter ID IDXTYPE CELLNAME TRXAIDSWITC H Parameter Name Index Type Cell Name TRX Aiding Function Control Example BYNAME (By Name) TDMCELL AllowReForbid(Allowed & Recover Forbidden) Source Network planning Network planning Network planning
Procedure
Step 1 On the Local Maintenance Terminal, run the ADD BTS command to add a BTS. Step 2 On the Local Maintenance Terminal, run the MOD CELLCCACCESS command to set TRX Aiding Function Control as required. ----End
Example
An example script for configuring TRX Cooperation is as follows:
/*Add a BTS3012*/ ADD BTS: BTSNAME = "BTS3012", TYPE = BTS3012, UPNODE = BSC, SRN = 0, SN=26, PN = 10, BTSDESC = "TDM BTS3012" , MPMODE = MODE4_1, FlexAbisMode = FIX_ABIS, AbisByPassMode = False, ServiceMode = TDM, DCELLNAME = "TDMCELL", DCTYPE = GSM900, DCMCC = "460", DCMNC = "34", DCLAC = 62, DCCI = 98, CPLMode = UNSUPPORT, TRXBN = 0, FREQ = 5; /*Configure TRX Cooperation*/ MOD CELLCCACCESS: IDXTYPE=BYNAME, CELLNAME="TDMCELL", TRXAIDSWITCH=AllowReForbid;
Postrequisite
l
Verifying TRX cooperation 1. 2. Switch off the power of the main BCCH TRX. In this way, the main BCCH TRX becomes faulty, and thus the main BCCH TRX mutual aid is triggered. After a period of time (less than 15 minutes), the cell begins to be reinitialized. In this case, run the MML command DSP CHNSTAT to query the channel status. The query result shows that Current Channel Type of one TRX (not the initially configured main BCCH TRX) whose channel number is 0 is set to Main BCCH. Make a call in the cell where the TRX mutual aid is enabled. The call is successfully set up, and the voice is clear. On the Local Maintenance Terminal, run the MOD CELLCCACCESS command to set TRX Aiding Function Control to TRXAid_NotAllow. Verifying deactivation of TRX cooperation: Switch off the power supply of the main BCCH TRX in the cell so that the main BCCH of the cell becomes faulty. Use the test
3.
l
Deactivating TRX cooperation 1. 2.
Issue 01 (2010-05-20)
MS to initiate a call in the cell. If the call fails to be set up, it indicates that the TRX cooperation function is deactivated.
17-4
Issue 01 (2010-05-20)
18 Configuring Cell Frequency Scan
18
Scenario Impact
NOTE
Configuring Cell Frequency Scan
The cell frequency scan function enables the scanning of the levels of the uplink signals at specific frequencies on a specific channel of a cell. The scanned results of the signal levels provides references for engineers to select proper operating frequencies. The cell frequency scan provides a reference for network optimization. Scanning the cell frequencies may affect the performance of other features.
Cell frequency scan has the following impacts on other features:

l l l
Cell frequency scan occupies an idle TCH. Cell frequency scan cannot be performed when an RF hopping loopback test is performed. The cell frequency scan cannot be performed when an idle frame test is performed.
Preparation
Table 18-1 Example of the data negotiated and planned for configuring cell frequency scan Parameter ID IDXTYPE CELLIDX STRTM TIME FREQBAND Parameter Name Index Type Cell Index Start time Duration minute Frequency Band Example BYIDX(By Index) 0 17:06:07 5 E-GSM900 Source Network planning Network planning Network planning Network planning Network planning
Issue 01 (2010-05-20)
18-1
18 Configuring Cell Frequency Scan
Procedure
Step 1 On the Local Maintenance Terminal, run the SET FREQSCAN command to configure cell frequency scan.
NOTE
If a BSC earlier than BSC6000V900R008C12SP25 is used, a maximum of 50 commands are allowed in the batch processing file when the commands are processed in batches. If more than 50 commands exist in the batch processing file, some cells cannot be scanned. If a BSC in BSC6000V900R008C12SP25 or a later version is used, no restriction is imposed on the number of commands in the batch processing file when the commands are processed in batches. In addition, 50 commands are executed per 30 seconds in sequence. Therefore, Duration minute cannot be set to a very small value. Otherwise, the execution of the commands cannot be completed in the specified duration.
Step 2 On the Local Maintenance Terminal, run the LST FREQSCAN command to query the information of cell frequency scan. Step 3 On the Local Maintenance Terminal, run the STP FREQSCAN command to stop the cell frequency scan. ----End
Example
An example script of configuring cell frequency scan is as follows:
/*Configure cell frequency scan*/ SET FREQSCAN: IDXTYPE=BYIDX, CELLIDX=0, STRTM=17&06&07, TIME=5, FREQBAND=E-GSM900, FREQLST_E900=0&975&1023; /*Query the frequency scan information of the cell with index of 0*/ LST FREQSCAN: IDXTYPE=BYIDX, CELLIDX=0; /*Stop the frequency scan information of the cell with index of 0*/ STP FREQSCAN: IDXTYPE=BYIDX, CELLIDX=0;
18-2
Issue 01 (2010-05-20)
19 Configuring High-Speed Signaling Links
19
Scenario
Configuring High-Speed Signaling Links
The BSC uses the high-speed signaling when the 64 kbit/s signaling fail to meet the signaling requirements on the A interface due to high traffic volume. With this feature, the N timeslots in an E1 are bound for the physical transmission of the SS7 signaling. Therefore, the bandwidth of a signaling link is extended to N x 64 kit/s and a maximum of 2 Mbit/s E1 bandwidth (N = 31) can be used. Generally, high-speed signaling links are used for terrestrial transmission instead of satellite transmission and used together with the Local Multiple Signaling Points feature to support more flexible signaling networking mode. Compared with 64 kbit/s signaling link, the 2 Mbit/s signaling link is configured with more timeslots; thus, the signaling transmission capacity of the 2 Mbit/s signaling link is greatly enhanced.
Impact
NEs Involved BSC, MSC, and MGW
Prerequisite
l l
The GEIUA is configured. This feature should be supported by the MSC.
Preparation
Table 19-1 Example of the data negotiated and planned for configuring high-speed signaling links in BM/TC combined mode Parameter ID SERVICEMODE SRN ASN Parameter Name Service Mode Subrack No. A Interface Slot No. Example TOGETHER(BM/TC Together) 0 24 Source Network planning Network planning Network planning
Issue 01 (2010-05-20)
19-1
Parameter ID APN ATSMASK SLC SLCSEND DPC LKRATE
Parameter Name A Interface Port No. A Interface Timeslot Mask SLC SLC Send DPC Link Rate Type
Example 0 TS8(8) 23 0 h'cc 2 M(2 Mbit/s)
Table 19-2 Example of the data negotiated and planned for configuring high-speed signaling links in BM/TC separate mode Parameter ID SERVICEMODE ATERPIDX ASN APN ATSMASK ATERTSMASK SLC SLCSEND DPC LKRATE Parameter Name Service Mode Ater Connection Path Index A Interface Slot No. A Interface Port No. A Interface Timeslot Mask Ater Interface Timeslot Mask SLC SLC Send DPC Link Rate Type Example SEPARATE(BM/TC Separate) 0 24 0 TS8(8)-TS11(11) TS8(9)-TS11(11) 0 0 h'cc 2 M(2 Mbit/s) Source Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning
Procedure
Step 1 On the Local Maintenance Terminal, run the ADD N7LNK command to add SS7 signaling links.
19-2
Issue 01 (2010-05-20)
NOTE
Set the parameter value of Service Mode based on the current service mode in the system. Run the LST BSCBASIC command to query the current service mode, and set Link Rate Type to 2 Mbit/s. In BM/TC separate mode, when the GTCS is configured remotely, you are advised not to select TS1 under Ater Interface Timeslot Mask for the SS7 signaling link in the main GTCS subrack.
----End
Example
An example script of configuring high-speed signaling links is as follows:
/*Configure high-speed signaling links in BM/TC combined mode*/ ADD N7LNK: SERVICEMODE=TOGETHER, SRN=0, ASN=24, APN=0, ATSMASK=TS0-0&TS1-0&TS2-0&TS3-0&TS4-0&TS5-0&TS6-0 & TS7-0&TS8-1&TS9-0&TS10-0&TS11-0&TS12-0&TS13-0&TS14-0&TS15-0&TS16-0&TS17-0&TS18-0&T S19-0&TS20-0&TS21-0&T S22-0&TS23-0&TS24-0&TS25-0&TS26-0&TS27-0&TS28-0&TS29-0&TS30-0&TS31-0, SLC=0, SLCSEND=0, DPC=h'cc, LKRATE =2M; /*Configure high-speed signaling links in BM/TC separate mode, and there is a connection path on the Ater interface*/ ADD N7LNK: SERVICEMODE=SEPARATE, ATERPIDX=0, ASN=24, APN=0, ATSMASK=TS0-0&TS1-0&TS2-0&TS3-0&TS4-0&TS5-0& TS6-0&TS7-0&TS8-1&TS9-1&TS10-1&TS11-1&TS12-0&TS13-0&TS14-0&TS15-0&TS16-0&TS17-0&TS 18-0&TS19-0&TS20-0&TS2 1-0&TS22-0&TS23-0&TS24-0&TS25-0&TS26-0&TS27-0&TS28-0&TS29-0&TS30-0&TS31-0, ATERTSMASK=TS0-0&TS1-0&TS2-0& TS3-0&TS4-0&TS5-0&TS6-0&TS7-0&TS8-1&TS9-1&TS10-1&TS11-1&TS12-0&TS13-0&TS14-0&TS150&TS16-0&TS17-0&TS18-0 & TS19-0&TS20-0&TS21-0&TS22-0&TS23-0&TS24-0&TS25-0&TS26-0&TS27-0&TS28-0&TS29-0&TS300&TS31-0, SLC=0, SLCS END=0, DPC=h'cc, LKRATE=2M;
Postrequisite
l
Verifying high-speed signaling links 1. On the Local Maintenance Terminal, run the LST N7LNK command to query the information of the SS7 signaling link. Specify the Service Mode as required. The Link Type should be 2 M. On the Local Maintenance Terminal, run the LST N7DPC command. Enter the specified DPC Code obtained from adding a high-speed signaling link to query the corresponding DPC Index. On the Local Maintenance Terminal, run the DSP MTP3LNK command. Set the Destination signalling point index according to the DPC Index obtained from step 2, and then check the current status of the MTP link. If INUSE is YES, the configured high-speed signaling link is normal. On the Local Maintenance Terminal, run the DEA MTP3LNK command to deactivate SS7 signaling links.
2.
3.
Deactivating high-speed signaling links
Issue 01 (2010-05-20)
19-3
20 Configuring Local Multiple Signaling Points
20
Configuring Local Multiple Signaling Points
With this feature, a physical node is logically classified into multiple signaling points. Each signaling point can be independently connected to other signaling points and thus meets the signaling link requirements for large capacity processing of the BSC6000. In addition, the requirements for the signaling networking capability of the MSC are reduced because the highspeed signaling technology is not used. Thus, the operators' investment is saved. Scenario The traffic volume is properly distributed to the logical BSCs, which effectively reduces the impact of the paging traffic on the BSC;Used together with the High Speed Signaling feature to support more flexible signaling networking mode. With this feature, the original intra-BSC handover or intra-BSC directed retry may be converted into outgoing BSC handover or outgoing BSC directed retry. Thus, the signaling load on the A interface and the call establishment time are increased.
Impact
NEs Involved BSC, MSC and MGW

NOTE
For each BM subrack, you should configure the mapping between the BM subrack and the local signaling point. For each signaling point, you should configure SS7 signaling links. The configuration procedure is the same as that for configuring general SS7 signaling links. A maximum of four OPCs, 32 DPCs, and 32 STPs can be configured to a BSC.
Preparation
This operation takes the configuration of two OPCs and one DPC as an example. The two OPCs correspond to number 0 and number 1 BM subracks. Table 20-1 Example of the data negotiated and planned for configuring the mapping between the first OPC and the subrack Data Type OPC attributes Parameter ID NAME Parameter Name OPC Name Example OPC1 Source Network planning
20-1
Issue 01 (2010-05-20)
Data Type
Parameter ID OPC
Parameter Name OPC Code Subrack No. OSP Code
Example H'A1 0 H'A1
Configuring the mapping between the subrack and the OPC
SRN OPC
Table 20-2 Example of the data negotiated and planned for configuring the mapping between the Second OPC and the subrack Data Type OPC attributes Parameter ID NAME OPC Configuring the mapping between the subrack and the OPC SRN OPC Parameter Name OPC Name OPC Code Subrack No. OSP Code Example OPC2 H'A2 1 H'A2 Source Network planning Network planning Network planning Network planning
Table 20-3 Example of the data negotiated and planned for configuring DPC Data Type DPC attributes Parameter ID NAME DPC USESTP DPCGIDX CNID Parameter Name DPC Name DPC Code Using STP DPC Group Index MSC ID Example DSP1 H'C1 YES(Yes) 0 0 Source Network planning Network planning Network planning Network planning Network planning
20-2
Issue 01 (2010-05-20)
Procedure
Step 1 On the Local Maintenance Terminal, run the ADD OPC command to add the first OPC. Step 2 On the Local Maintenance Terminal, run the ADD SROPCMAP command to configure the mapping between the subrack and the OPC. Step 3 Repeat step 1 and step 2 to add the second OPC and the mapping between the second OPC and the subrack. Step 4 On the Local Maintenance Terminal, run the ADD N7DPC command to add DPCs.
NOTE
If there is no direct physical link between the OPC and the DPC, then you have to configure STPs.Using STP should be set to YES(Yes).
Step 5 Optional: When you need to configure the STP, run the ADD STP command on the Local Maintenance Terminal to add the STP. ----End
Example
Example scripts of configuring local multiple signaling points are as follows:
/*Add an OPC*/ ADD OPC: NAME="OPC1", OPC=H'A1; /*Add the mapping between the subrack and the OPC*/ ADD SROPCMAP: SRN=0, OPC=H'A1; /*Add the second OPC*/ ADD OPC: NAME="OPC2", OPC=H'A2; /*Add the mapping between the subrack and the OPC*/ ADD SROPCMAP: SRN=1, OPC=H'A2; /*Add a DPC*/ ADD N7DPC: NAME="DSP1", DPC=H'C1, DPCGIDX=0, USESTP=YES, CNID=0;
Postrequisite
l
Verifying local multiple signaling points
On the Local Maintenance Terminal, run the DSP SCCPSSN command to query the status of the SCCP subsystem. If the status of the SCCP subsystem is "allowed", it indicates that local multiple signaling points are successfully activated. On the Local Maintenance Terminal, run the MOD SROPCMAP command to modify the OPC of the non-main subrack to be the same as that of the main subrack. On the Local Maintenance Terminal, run the RMV OPC command to delete the corresponding OPC.
Deactivating local multiple signaling points 1. 2.
Issue 01 (2010-05-20)
20-3
21 Configuring DTX and DRX
21
About This Chapter
Configuring DTX and DRX
Discontinuous transmission (DTX) and discontinuous reception (DRX) increases the standby time and call duration of an MS. 21.1 Configuring DTX This describes how to configure discontinuous transmission (DTX) on the Local Maintenance Terminal. 21.2 Configuring DRX This describes how to configure discontinuous reception (DRX) on the Local Maintenance Terminal.
Issue 01 (2010-05-20)
21-1
21.1 Configuring DTX

This describes how to configure discontinuous transmission (DTX) on the Local Maintenance Terminal. Scenario Impact DTX is configured to reduce power and system interference, save system resources, and increase the call duration and standby time. DTX affects only the transmission of TCH frames.
CAUTION
DTX cannot be configured in co-cell mode.
Prerequisite
l l l
DTX is not restricted by the license. The setting of uplink DTX is completed by the BSC. The setting of downlink DTX should be performed at both the BSC and MSC. Otherwise, the downlink DTX does not work.
Preparation
Take the configuration of BTS3012 in TDM transmission mode as an example. Table 21-1 Example of the data negotiated and planned for adding a BTS Data Type BTS basic attributes Parameter ID BTSNAME Parameter Name BTS Name Example BTS3012 Source Networ k plannin g Networ k plannin g Networ k plannin g
TYPE
BTS Type
BTS3012
UPNODE
Up Node Type
BSC
21-2
Issue 01 (2010-05-20)
Data Type
Parameter ID SRN
Parameter Name Subrack No.
Example 0
Source Networ k plannin g Networ k plannin g Networ k plannin g Networ k plannin g Networ k plannin g Networ k plannin g Networ k plannin g Networ k plannin g Networ k plannin g Networ k plannin g
SN
Slot No.
26
PN
Port No.
BTSDESC
BTS Description
TDM BTS3012
MPMODE
Multiplexing Mode
MODE4_1
FlexAbisMode
Flex Abis Mode
FLEX_ABIS(Flex Abis)
AbisByPassMod e
Abis By Pass Mode
FALSE(Not Support)
ServiceMode
Service Type
TDM
DCELLNAME
Cell Name
TDMCELL
DCTYPE
Cell type
GSM900
Issue 01 (2010-05-20)
21-3
Data Type
Parameter ID DCMCC
Parameter Name Cell MCC
Example 460
Source Networ k plannin g Networ k plannin g Networ k plannin g Networ k plannin g Networ k plannin g Networ k plannin g Networ k plannin g
DCMNC
Cell MNC
34
DCLAC
Cell LAC
62
DCCI
Cell CI
98
CPLMode
Separate Mode
UNSUPPORT(Not Support)
TRXBN
TRX Board No.
FREQ
TRX Freq.
Table 21-2 Example of the data negotiated and planned for configuring DTX Data Type Filter and penalty data of the cell handover Parameter ID IDXTYPE Parameter Name Index Type Example BYNAME (By Name) Source Networ k plannin g Networ k plannin g
CELLNAME
Cell Name
TDMCELL
21-4
Issue 01 (2010-05-20)
Data Type
Parameter ID HOCTRLSWIT CH
Parameter Name HO Control Switch
Example HOALGORITHM 1(HO Algorithm I)
Source Networ k plannin g Networ k plannin g Networ k plannin g Networ k plannin g Networ k plannin g Networ k plannin g
DTXMEASUSE D
DtxMeasUsed
OPEN(open)
Cell basic attributes
FRULDTX
TCH/F Uplink DTX
Shall_Use(Shall Use)
HRULDTX
TCH/H Uplink DTX
Shall_Use(Shall Use)
FRDLDTX
TCH/F Use Downlink DTX
YES(Yes)
HRDLDTX
TCH/H Use Downlink DTX
YES(Yes)
Procedure
Step 1 On the Local Maintenance Terminal, run the ADD BTS command to add a BTS. Step 2 On the Local Maintenance Terminal, run the SET CELLHOFITPEN command to set DtxMeasUsed to OPEN(open). Step 3 On the Local Maintenance Terminal, run the MOD CELLBASICPARA command to set TCH/F Uplink DTX or TCH/H Uplink DTX to Shall_Use(Shall Use) and set TCH/F Use Downlink DTX or TCH/H Use Downlink DTX to YES(YES). ----End
Example
An example script for configuring DTX for a BTS3012 in TDM transmission mode is as follows:
/*Add a BTS3012*/ ADD BTS: BTSNAME="BTS3012", TYPE=BTS3012, UPNODE=BSC, SRN=0, SN=27, PN=0, BTSDESC="TDM BTS3012", MPMODE=MODE4_1, FlexAbisMode=FLEX_ABIS, AbisByPassMode=False, ServiceMode=TDM, DCELLNAME="TDMCELL", DCTYPE=GSM900, DCMCC="460", DCMNC="34", DCLAC=62, DCCI=98, CPLMode=UNSUPPORT, TRXBN=0, FREQ=5; /*Set "DtxMeasUsed" to "OPEN(open)"*/ SET CELLHOFITPEN: IDXTYPE = BYNAME, CELLNAME = "TDMCELL", HOCTRLSWITCH = HOALGORITHM1, DTXMEASUSED = OPEN;
Issue 01 (2010-05-20)
21-5
/*Set "TCH/F Uplink DTX" or "TCH/H Uplink DTX" to "Shall_Use(Shall Use)" and set "TCH/F Use Downlink DTX" or "TCH/H Use Downlink DTX" to "YES(YES)"*/ MOD CELLBASICPARA: IDXTYPE = BYNAME, CELLNAME="TDMCELL", FRULDTX = Shall_Use, HRULDTX = Shall_Use, FRDLDTX=YES, HRDLDTX=YES;
Postrequisite
l
Verifying DTX
Verifying the uplink DTX 1. On the Local Maintenance Terminal, run the MOD CELLBASICPARA command to set TCH/F Uplink DTX to Shall_Use(Shall Use), TCH/H Uplink DTX to Shall_Use(Shall Use), TCH/F Use Downlink DTX to YES(Yes), and TCH/H Use Downlink DTX to YES(Yes). On the Local Maintenance Terminal, run the SND SYSMSG command to forcedly send system information to the test cell. Check the BCCH Information messages in the Abis messages in the CS domain and find out the messages whose system-info-type is system-information-3 in the detailed information. If the value of dtx in the cell-options information element is 1, it indicates that the system information is sent correctly. Use the MS to make a call. The call is successfully set up. Verify that the Abis signaling messages in the CS domain and the A signaling messages are traced. Check the Channel Activation messages in the Abis messages in the CS domain. If the value of dtx-uplink in the messages with channel-type being bm-acch is 1, it indicates that the BSC supports the uplink DTX function. On the Local Maintenance Terminal, run the MOD CELLBASICPARA command to set TCH/F Uplink DTX to Shall_Use(Shall Use), TCH/H Uplink DTX to Shall_Use(Shall Use), TCH/F Use Downlink DTX to YES(Yes), and TCH/H Use Downlink DTX to YES(Yes). Use the MS to make a call. The call is successfully set up. Check that the A signaling messages and Abis signaling messages in the CS domain are traced. Check the Assignment Request messages in the messages on the A interface. If the value of the downlink-dtx-flag information element is 0, it indicates that the downlink DTX is allowed on the MSC. Check the Channel Activation messages in the messages on the Abis interface in the CS domain. If dtx-downlink in the channel-mode information element is 1, it indicates that the BSC supports the downlink DTX.
2. 3.
4. 5.
Verifying the downlink DTX 1.
2. 3.
Deactivating DTX 1. On the Local Maintenance Terminal, run the MOD CELLBASICPARA command to set TCH/F Uplink DTX or TCH/H Uplink DTX to Shall_NOT_Use (Shall Not Use) and set TCH/F Use Downlink DTX or TCH/H Use Downlink DTX to NO (No). The operations for verifying deactivation of DTX are the same as those for Verifying DTX. Verify that the values of dtx-uplink and dtx-downlink are 0.
2.
21-6
Issue 01 (2010-05-20)
21.2 Configuring DRX

This describes how to configure discontinuous reception (DRX) on the Local Maintenance Terminal. Scenario Impact DRX increases the call duration and standby time of an MS. None
Prerequisite
DRX is not restricted by the license.
Preparation
Take the configuration of BTS3012 in TDM transmission mode as an example. Table 21-3 Example of the data negotiated and planned for adding a BTS Data Type BTS basic attributes Parameter ID BTSNAME Parameter Name BTS Name Example BTS3012 Source Networ k plannin g Networ k plannin g Networ k plannin g Networ k plannin g Networ k plannin g Networ k plannin g
21-7
TYPE
BTS Type
BTS3012
UPNODE
Up Node Type
BSC
SRN
Subrack No.
SN
Slot No.
27
PN
Port No.
Issue 01 (2010-05-20)
Data Type
Parameter ID BTSDESC
Parameter Name BTS Description
Example TDM BTS3012
Source Networ k plannin g Networ k plannin g Networ k plannin g Networ k plannin g Networ k plannin g Networ k plannin g Networ k plannin g Networ k plannin g Networ k plannin g Networ k plannin g
MPMODE
Multiplexing Mode
MODE4_1
FlexAbisMode
Flex Abis Mode
FLEX_ABIS(Flex Abis)
AbisByPassMod e
Abis By Pass Mode
FALSE(Not Support)
ServiceMode
Service Type
TDM
DCELLNAME
Cell Name
TDMCELL
DCTYPE
Cell type
GSM900
DCMCC
Cell MCC
460
DCMNC
Cell MNC
34
DCLAC
Cell LAC
62
21-8
Issue 01 (2010-05-20)
Data Type
Parameter ID DCCI
Parameter Name Cell CI
Example 98
Source Networ k plannin g Networ k plannin g Networ k plannin g Networ k plannin g
CPLMode
Separate Mode
UNSUPPORT(Not Support)
TRXBN
TRX Board No.
FREQ
TRX Freq.
Table 21-4 Example of the data negotiated and planned for configuring DTX Data Type Basic idle parameters of the cell Parameter ID IDXTYPE Parameter Name Index Type Example BYNAME (By Name) Source Networ k plannin g Networ k plannin g Networ k plannin g Networ k plannin g
CELLNAME
Cell Name
TDMCELL
BSAGBLKSRE S
Number of CCCH blocks reserved for the AGCH Number of multiframes in a cycle on the paging channel
BSPAMFRAM
2_M_PERIOD(2 Multiframe Period)
Procedure
Step 1 On the Local Maintenance Terminal, run the ADD BTS command to add a BTS.
Issue 01 (2010-05-20)
21-9
Step 2 On the Local Maintenance Terminal, run the MOD CELLIDLEBASIC command to set Number of CCCH blocks reserved for the AGCH to 2 and set Number of multi-frames in a cycle on the paging channel to 2_M_PERIOD(2 Multiframe Period). ----End
Example
An example script for configuring DRX for a BTS3012 in TDM transmission mode is as follows:
/*Add a BTS3012*/ ADD BTS: BTSNAME="BTS3012", TYPE=BTS3012, UPNODE=BSC, SRN=0, SN=27, PN=0, BTSDESC="TDM BTS3012", MPMODE=MODE4_1, FlexAbisMode=FLEX_ABIS, AbisByPassMode=False, ServiceMode=TDM, DCELLNAME="TDMCELL", DCTYPE=GSM900, DCMCC="460", DCMNC="34", DCLAC=62, DCCI=98, CPLMode=UNSUPPORT, TRXBN=0, FREQ=5; /*Configure DRX*/ MOD CELLIDLEBASIC: IDXTYPE=BYNAME, CELLNAME="TDMCELL", BSAGBLKSRES=2, BSPAMFRAMS=2_M_PERIOD;
Postrequisite
l
Verifying DRX 1. On the Local Maintenance Terminal, run the MOD CELLIDLEBASIC command to set Number of CCCH blocks reserved for the AGCH to 2 and set Number of multi-frames in a cycle on the paging channel to 2_M_PERIOD(2 Multiframe Period). On the Local Maintenance Terminal, run the SND SYSMSG command to forcedly send system information to the test cell. Check the BCCH Information messages in the Abis messages in the CS domain and find out the messages whose system-info-type is system-information-3 in the detailed information. Check whether bs-ag-blks-res (the corresponding parameter is Number of CCCH blocks reserved for the AGCH) is 2, and whether bs-pamfrms (the corresponding parameter is Number of multi-frames in a cycle on the paging channel) is 0 in the control-channel-description information element. If so, it indicates that the system information is sent correctly. Use an MS to call another MS with a known IMSI (such as M). The call is successfully set up. Check the Page Command messages in the messages traced over the Abis interface in the CS domain. If the paging-group information element in the message is M% 1000%14%14, it indicates that the setting of the paging group that delivers the paging messages is consistent with that set in the system information. In this case, the MS can implement DRX by listening to the paging subchannel.
NOTE
2. 3.
4. 5.
% in M%1000%14%14 indicates the modulo operator. The obtained paging group number is decimal.
21-10
Issue 01 (2010-05-20)
22 Configuring Location Service
22
About This Chapter
Configuring Location Service
Location sevice (LCS) enables the network to provide various services for an MS based on the location of the MS. These services include weather forecasts, trip scheduling, emergency assistance, stock information, business planning, and transportation conditions. The simple location service can locate an MS based on the information obtained during single-user message tracing. 22.1 Configuring Location Service This describes how to configure location service (LCS) on the Local Maintenance Terminal. 22.2 Configuring Simple Location Service This describes how to configure simple location service on the Local Maintenance Terminal.
Issue 01 (2010-05-20)
22-1
22.1 Configuring Location Service

This describes how to configure location service (LCS) on the Local Maintenance Terminal. Scenario Impact The built-in SMLC supports the BSS-based Cell ID+TA location service. None
NEs Involved SGSN, BSC, BTS, and MS
Prerequisite
l l
LCS is restricted by the license. Activate the license on the Local Maintenance Terminal. For details, see Activate BSC License.
Preparation
Table 22-1 Example of the data negotiated and planned for configuring LCS Data Type Other software parameters on the A Interface Parameter ID DPC LcsSupportControl IDXTYPE CELLIDX INPUTMD Parameter Name Subrack No. LCS Support Control Index Type Cell Index Latitude and Longitude input mode NS Latitude Latitude int part Latitude decimal part WE Longitude Example 5 YES BYIDX(By Index) 0 Degree(degree) Source Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning
Cell LCS parameters
NSLATI LATIINT LATIDECI WELONGI
North_latitude (North latitude) 45 5 East_Longitude (East Longititude)
22-2
Issue 01 (2010-05-20)
Data Type
Parameter ID LONGIINT LONGIDECI
Parameter Name Longitude int part Longitude decimal part
Example 115 6
Procedure
Step 1 On the Local Maintenance Terminal, run the SET AITFOTHPARA command to configure LCS. Step 2 On the Local Maintenance Terminal, run the MOD CELLHOCTRL command to configure cell LCS parameters. ----End
Example
An example script for configuring LCS is as follows:
/*Configure the BSC to support LCS*/ SET AITFOTHPARA: DPC=12, LcsSupportControl=YES; /*Configure cell LCS parameters*/ MOD CELLIDLEBASIC: IDXTYPE=BYIDX, CELLIDX=0, INPUTMD=Degree, NSLATI=North_latitude, LATIINT=45, LATIDECI="5", WELONGI=East_Longitude, LONGIINT=115, LONGIDECI="6";
Postrequisite
l
Verifying location service 1. 2. Use an MS to make a call in the cell where the location service is enabled. On the BSC6000 Local Maintenance Terminal, enable the single-user tracing to trace the call signaling of the MS. For details, see Tracing CS Domain User Messages in the BSC LMT User Guide. Analyze the A interface signaling, if the signaling Perform Location Request and Perform Location Response, and if Perform Location Response contains Location Estimate IE, it indicates that the location service is active. On the Local Maintenance Terminal, run the SET AITFOTHPARA command, and set LCS Support Control to NO. Verifying the deactivation of location service: The operations are the same as those for Verifying location service. Verify that Perform Location Response does not contain Location Estimate IE.
3.
Deactivating location service 1. 2.
22.2 Configuring Simple Location Service

This describes how to configure simple location service on the Local Maintenance Terminal.
Scenario Impact
The simple location service is configured to trace the MS. None
NEs Involved BSC
Prerequisite
l l
Simple location service is restricted by the license. Activate the license on the Local Maintenance Terminal. For details, see Activate BSC License.
Preparation
Table 22-2 Example of the data negotiated and planned for configuring simple location service Data Type Simple location service attributes Parameter ID ITFTYPE TRCCONDITIO N MSISDN STRDT STRTM ENDDT ENDTM TASKNO TRCTYPE TRCMODE Parameter Name Interface type Tracing condition MSISDN Start date Start time End date End time trace task number Trace type Trace mode Example AITF(A INTERFACE) MSISDN 1399455166 2008-11-15 21:22:51 2008-11-15 22:22:51 3212 USERTRACE (User Trace) RMSTREAM (STREAM) Source Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning
Procedure
Step 1 On the Local Maintenance Terminal, configure LCS. For details, see Configuring Location Service.
Step 2 On the Local Maintenance Terminal, run the CRE USERTRCTASK command to create a tracing task. Step 3 On the Local Maintenance Terminal, run the STR TRCTASK command to start the tracing task.
NOTE
The task started must be a task that is not running.
Step 4 On the Local Maintenance Terminal, run the LST TRCTASK command to query the tracing task. Step 5 On the Local Maintenance Terminal, run the STP TRCTASK command to stop the tracing task.
NOTE
The task stopped must be a task that is running.
Step 6 On the Local Maintenance Terminal, run the DEL TRCTASK command to delete the tracing task. ----End
Example
An example script for configuring simple location service is as follows:
/*Create a tracing task*/ CRE USERTRCTASK: ITFTYPE=AITF, TRCCONDITION=MSISDN, MSISDN="1399455166", STRDT=2008&11&15, STRTM=21&22&51, ENDDT=2008&11&15, ENDTM=2 1&22&51; /*Start the tracing task*/ STR TRCTASK:TASKNO=3212; /*Stop the tracing task*/ STR TRCTASK:TASKNO=3212; TASKNO=3212; /*Delete the tracing task*/ STR TRCTASK:TASKNO=3212; TASKNO=3212; /*Query the tracing task*/ LST TRCTASK: TRCTYPE=USERTRACE, TRCMODE=RMSTREAM;
Issue 01 (2010-05-20)
22-5
23 Configuring TFO
23
Scenario Impact
Configuring TFO
The TFO feature can reduce the speech signal degradation caused by tandem operation, thus improving the voice quality. When the calling MS and the called MS use the same speech version, the TFO link is established through the in-band signaling negotiation. In addition, the least significant bit (or the second least significant bit) is stolen to seize the 8 kbit/s (or 16 kbit/s) sublink of the PCM transmission link for transparent transmission of TFO frames and bypass TC encoding/decoding. In this manner, the speech signal is encoded at the MS initiating the call and decoded at the MS terminating the call for only once. Thus, the degradation of the speech signals due to tandem operation is reduced and the voice quality is improved. This process is called tandem free operation (TFO). In A over TDM, the traffic volume is evenly distributed in the MSC pool. None.
NEs Involved MS, BSC, MSC, MGW, and HLR

NOTE
The TFO is not supported in A over IP. Configure the TFO according to the combination types of the BSC subracks:
l l
In BM/TC separated mode, the TFO should be configured for the GDPUC/GDPUX in the GTCS and the GDPUX of the GMPS/GEPS does not require the configuration of the TFO. In BM/TC combined mode and the TDM transmission is adopted on the Abis interface, the TFO should be configured for the GDPUX in the GMPS/GEPS.
Prerequisite
l l
The GDPUC/GDPUX is configured. The data between the TCs at the two ends should be transmitted transparently. In addition, the TFO should be supported by the TCs at both ends. This function cannot be enabled at the same time as ALC, AEC, or ANR.
Issue 01 (2010-05-20)
23-1
23 Configuring TFO
Preparation
Table 23-1 Example of the data negotiated and planned for configuring TFO Parameter ID SRN SN Tfo_Switch Parameter Name Subrack No. Slot No. TFO Switch Example 0 5 OPEN(Open) Source Network planning Network planning Network planning
Procedure
Step 1 On the Local Maintenance Terminal, run the MOD DSPTC command to set TFO Switch to OPEN(Open).If you do not set DSP No., the TC attributes of all the DSPs are configured. ----End
Example
An example script of configuring TFO is as follows:
MOD DSPTC: SRN=0, SN=5, Tfo_Switch=OPEN;
Postrequisite
l
Verifying TFO 1. 2. Use the test MS to call another MS, and then hold on the call. On the Local Maintenance Terminal, run the DSP DSPSTAT command. If Available State is Normal in the result, the DSP is normal. If you do not set DSP No., the status of all DSPs are queried. On the Local Maintenance Terminal, run the DSP DSPSVRSTAT. If the TFO state of certain channels is Connect, the verification of the TFO is successful. If you do not set DSP No., the service status of all DSPs are queried. On the Local Maintenance Terminal, run the MOD DSPTC command to set TFO Switch to CLOSE(Close). The operations for deactivating TFO are the same as those for Verifying TFO. Verify that no service channel with the TFO status being Connect exists.
3.
Deactivating TFO 1. 2.
23-2
Issue 01 (2010-05-20)
24 Configuring PBT
24
About This Chapter
Context
Configuring PBT
In the DTRU, two TRXs are integrated into a TRX module that is configured with a combiner. The combiner combines the radio signals of the same frequency and same phrase from two TRXs, and then transmits the combined signals. In this way, the downlink transmit power is higher than the transmit power of the original signals, and the transmit power with high gain is achieved and the downlink coverage is extended.
The TRX attributes and antenna feeder mode for the DBS3900 GSM are set on the BSC side. The method of configuring PBT for the DBS3900 is the same as that for the BTS3012/ BTS3012AE. 24.1 Installing Hardware (PBT) This describes how to connect the cables in PBT mode. 24.2 Configuring PBT This describes how to configure PBT on the Local Maintenance Terminal. 24.3 Configuring Dynamic PBT Dynamic Power Boost Technology (PBT) is a timeslot-based PBT. the timeslot-based dynamic transmit diversity maintains optimal balance between capacity and coverage. This describes how to configure dynamic PBT on the Local Maintenance Terminal.
Issue 01 (2010-05-20)
24-1
24 Configuring PBT
24.1 Installing Hardware (PBT)

This describes how to connect the cables in PBT mode.
Procedure
l Figure 24-1 shows the connections between the DTRU and the DDPU in PBT mode.
24-2
Issue 01 (2010-05-20)
24 Configuring PBT
Figure 24-1 Connections between the DTRU and the DDPU in PBT mode
DDPU
RUN ALM VSWRA VSWRB
COM
POWER
RXA1
RXA2 TXA RXA3 RXA4 RXB1 RXB2 RXB3 TXB RXB4
DTRU
TX1
TCOM
TX2
RUN ACT ALM RF_IND
RS T RXM1 RXD1 RXM2 RXD2
POWER
Issue 01 (2010-05-20)
24-3
24 Configuring PBT
----End
24.2 Configuring PBT

This describes how to configure PBT on the Local Maintenance Terminal. Scenario Impact The PBT is used to increase the coverage area of a BTS. None.
Prerequisite
l l
The PBT is restricted by the license. Activate the license on the Local Maintenance Terminal. For details, refer to Activate BSC License. With this feature, the two TRXs in the DTRU are used as one TRX. The following BTSs support the PBT: BTS3012, BTS3012AE (DTRU available), BTS3900 or BTS3900A (DRFU available), and DBS3900 (RRU3004 available).
Preparation
Table 24-1 Example of the data negotiated and planned for configuring PBT Parameter ID IDXTYPE CELLIDX TRXBN TRXPN SNDMD Parameter Name Index Type Cell Index TRX Board No. TRX Board Path No. Send Mode Example BYIDX(By Index) 0 0 0 PBT(PBT) Source Network planning Network planning Network planning Network planning Network planning
Procedure
Step 1 On the Local Maintenance Terminal, run the MOD TRXDEV command to set Send Mode to PBT(PBT).
NOTE
When you configure PBT, the signal can be transmitted through only channel 0.
----End
Example
An example script for configuring PBT is as follows:
24 Configuring PBT
MOD TRXDEV: IDXTYPE=BYIDX, CELLIDX=0, TRXBN=0, TRXPN=0, SNDMD=PBT;
Postrequisite
l
Verifying PBT 1. Use the test MS to make a call.

NOTE
This step is required only when the main BCCH is not carried on the test TRX.
2.
On the Local Maintenance Terminal, run the MOD TRXDEV command to set Send Mode to NONE(none). Test the BTS power by using the power meter, and then record the test result. On the Local Maintenance Terminal, run the MOD TRXDEV command to set Send Mode to PBT(PBT). On the Local Maintenance Terminal, run the LST TRXDEV command to verify that Send Mode is set to PBT(PBT). Test the BTS power by using the power meter, and then record the test result. Compare the test result recorded in Step 2 with that recorded in Step 4. If the power obtained in Step 4 is much larger than that obtained in Step 2, it indicates that the PBT is activated.
3. 4.
5.
Deactivating PBT 1. 2. On the Local Maintenance Terminal, run the MOD TRXDEV command to set Send Mode to NONE(none). On the Local Maintenance Terminal, run the LST TRXDEV command to verify that Send Mode is set to NONE. It indicates that the PBT is deactivated.
24.3 Configuring Dynamic PBT

Dynamic Power Boost Technology (PBT) is a timeslot-based PBT. the timeslot-based dynamic transmit diversity maintains optimal balance between capacity and coverage. This describes how to configure dynamic PBT on the Local Maintenance Terminal. Scenario Impact Dynamic PBT is configured to achieve the balance between capacity and coverage. None.
Prerequisite
l l
Dynamic PBT is restricted by the license. Activate the license on the Local Maintenance Terminal. For details, refer to Activate BSC License. Currently, dynamic PBT is supported by the following types of BTSs: BTS3012/ BTS3012AE configured with the DTRU BTS3900/BTS3900A configured with the DRFU, DBS3900 configured with the RRU3004.
Issue 01 (2010-05-20)
24-5
24 Configuring PBT
Preparation
Table 24-2 Example of the data negotiated and planned for configuring dynamic PBT Parameter ID IDXTYPE CELLIDX TRXBN TRXPN SNDMD Parameter Name Index Type Cell Index TRX Board No. TRX Board Path No. Send Mode Example BYIDX(By Index) 0 0 0 DPBT(DPBT) Source Network planning Network planning Network planning Network planning Network planning
Procedure
Step 1 On the Local Maintenance Terminal, run the MOD CELLIUO command to set Cell IUO Type to Concentric_cell(Concentric cell). Step 2 On the Local Maintenance Terminal, run the SET CELLCHMGBASIC command to set Dynamic Transmission Div<PBT> Supported to DPBT(DPBT). Step 3 On the Local Maintenance Terminal, run the MOD TRXDEV command to set Send Mode of the TRX in the overlaid subcell to DPBT(DPBT).
NOTE
l l
You can use the LST TRXIUO command to check whether the TRX is in the overlaid subcell or underlaid subcell. To configure dynamic PBT, two TRXs must be configured. In addition, dynamic PBT cannot be configured on the MBCCH.
----End
Example
An example script for configuring dynamic PBT is as follows:
MOD CELLIUO: IDXTYPE=BYIDX, CELLIDX=0, IUOTP=Concentric_cell; SET CELLCHMGBASIC: IDXTYPE=BYIDX, CELLIDX=0, DYNPBTSUPPORTED=DPBT; MOD TRXDEV: IDXTYPE=BYIDX, CELLIDX=0, TRXBN=1, TRXPN=1, SNDMD=DPBT;
Postrequisite
l
Verifying dynamic PBT 1. Monitor the channel status, and use the test MS to initiate an emergency call in an area with weak signals (such as at the boundary between an overlaid subcell and an underlaid subcell). When a call occupies a TRX with dynamic PBT enabled, the channel status monitoring interface shows that the call occupies two channels on the same timeslots of two TRXs.
2.
24-6
24 Configuring PBT
The status of one channel is Working, whereas that of another channel is Subordinate Channel.
l
Deactivating dynamic PBT 1. On the Local Maintenance Terminal, run the SET CELLCHMGBASIC command to set Dynamic Transmission Div<PBT> Supported to NOTSUPPORT(Not Support). On the Local Maintenance Terminal, run the LST CELLCHMGBASIC command. If Dynamic Transmission Div<PBT> Supported is set to Not Support, it indicates that the dynamic PBT function is deactivated.
2.
Issue 01 (2010-05-20)
24-7
25 Configuring Transmit Diversity
25
Configuring Transmit Diversity
About This Chapter

In the DTRU, two TRXs are integrated into one TRX module. With this feature, the two TRXs on the DTRU transmit the correlated signals of the same carrier. This provides two independent multi-path signals for the downlink. Then, the two independent multi-path signals are processed by the equalizer of the MS. In this way, the diversity gain is obtained, and the quality of the receive signal is improved. Therefore, the downlink coverage is improved. When the DTRU works in single TRX mode, the BTS can enable this feature through data configuration. 25.1 Installing Hardware (Transmit Diversity) This describes how to connect the cables in transmit diversity mode. 25.2 Configuring Transmit Diversity This describes how to configure transmit diversity on the Local Maintenance Terminal. 25.3 Configuring Dynamic Transmit Diversity Dynamic transmit diversity is timeslot-based transmit diversity. timeslot-based dynamic transmit diversity maintains optimal balance between capacity and coverage.This describes how to configure dynamic transmit diversity on the Local Maintenance Terminal.
Issue 01 (2010-05-20)
25-1
25.1 Installing Hardware (Transmit Diversity)

This describes how to connect the cables in transmit diversity mode.
Procedure
l The blue lines in Figure 25-1 show the cable connections between the DTRU and the DDPU in the BTS3012/BTS3012AE in transmit diversity mode.
25-2
Issue 01 (2010-05-20)
Figure 25-1 Cable connections between the DTRU and the DDPU in the BTS3012/ BTS3012AE in transmit diversity mode
DDPU
RUN ALM VSWRA VSWRB
COM
POWER
RXA1
DTRU
TX1
TCOM
TX2
RUN ACT ALM RF_IND
POWER
Issue 01 (2010-05-20)
25-3
Figure 25-2 shows the cable connections between the DDPM and the DDRM in the BTS3006C in transmit diversity mode. Figure 25-2 Cable connections between the DDPM and the DDRM in the BTS3006C in transmit diversity mode.
DDRM DSEM
TX1-
TX2-
DMCM DSEM DDPM
TXB TXA
RXB1
RUN ALM VSWR A
RUN/SLPACTALMRF_IND
RXA1
RXM1RXD1-
RXB2
VSWRB
RXA2
RXM2RXD2FAN-
RXB3
RXA3
ANTB ANTA
Figure 25-3 shows the cable connections between the DDPM and the DDRM in the BTS3002E in transmit diversity mode.
25-4
Issue 01 (2010-05-20)
Figure 25-3 Cable connections between the DDPM and the DDRM in the BTS3002E in transmit diversity mode
DDPM DDRM DPSM
TX1TXB TXA
RXB1 RUN ALM VSWRB RXB2 RXA2 RXA1
TX2-
VSWR A
RXB3
RXA3
ANTB ANTA
DMCM DATM
FAN-
DOOR
Figure 25-4 shows the cable connections in the DBS3900 GSM in transmit diversity mode.
Issue 01 (2010-05-20)
25-5
Figure 25-4 Cable connections in the DBS3900 GSM in transmit diversity mode
ANT Antenna
ANT_TX/RXA
ANT_TX/RXB
RX_IN/OUT
RRU0
CPRI_E
CPRI_W
CPRI0
CPRI5
BBU
----End
25.2 Configuring Transmit Diversity

This describes how to configure transmit diversity on the Local Maintenance Terminal. Scenario Impact Transmit diversity is configured to improve the downlink signal strength by manually realizing multipath. None.
Prerequisite
l l
Transmit diversity is restricted by the license. Activate the license on the Local Maintenance Terminal. For details, refer to Activate BSC License. The two TRXs enabling the transmit diversity work as only a TRX. In addition, at least a pair of dual-polarized antenna feeders or two pairs of single-polarized antenna feeders are required. The following BTSs or TRXs support the transmit diversity: BTS3012,
25-6
BTS3012AE (DTRU available), BTS3006C or BTS3002E (DDRM available), BTS3900 or BTS3900A (DRFU available), and DBS3900 (RRU3004 or RRU3008 available).
Preparation
Table 25-1 Example of the data negotiated and planned for configuring transmit diversity Parameter ID IDXTYPE CELLIDX TRXBN TRXPN SNDMD Parameter Name Index Type Cell Index TRX Board No. TRX Board Path No. Send Mode Example BYIDX(By Index) 0 0 0 DIVERSITY (DiversityTrans mit) Source Network planning Network planning Network planning Network planning Network planning
Procedure
Step 1 On the Local Maintenance Terminal, run the MOD TRXDEV command to set Send Mode to Diversity(DiversityTransmit).
NOTE
When you configure transmit diversity, one double-transceiver unit serves as one TRX. In addition, the signal can be transmitted through only channel 0.
----End
Example
An example script for configuring transmit diversity is as follows:
MOD TRXDEV: IDXTYPE=BYIDX, CELLIDX=0, TRXBN=0, TRXPN=0, SNDMD=DIVERSITY;
Postrequisite
l
Verifying transmit diversity
Test the power of channel B on the TRX whose Send Mode is set to DIVERSITY (DiversityTransmit) by using a power meter. Then, record the test results. If the power is not 0, it indicates that the transmit diversity function takes effect. On the Local Maintenance Terminal, run the MOD TRXDEV command to set Send Mode to a value other than DIVERSITY(DiversityTransmit). On the Local Maintenance Terminal, run the LST TRXDEV command to verify that Send Mode is set to a value other than DIVERSITY(DiversityTransmit). It indicates that the transmit diversity is deactivated.
Deactivating transmit diversity 1. 2.
Issue 01 (2010-05-20)
25.3 Configuring Dynamic Transmit Diversity

Dynamic transmit diversity is timeslot-based transmit diversity. timeslot-based dynamic transmit diversity maintains optimal balance between capacity and coverage.This describes how to configure dynamic transmit diversity on the Local Maintenance Terminal. Scenario Impact Dynamic transmit diversity makes full use of the idle timeslots to expand the coverage in the areas with weak signals. None.
NEs Involved BTS, BSC.
Prerequisite
l l
Dynamic transmit diversity is restricted by the license. Activate the license on the Local Maintenance Terminal. For details, refer to Activate BSC License. The cell to which dynamic transmit diversity is applied must be configured with a minimum of one dual-polarized antenna or two uni-polarized antennas. Currently, this feature is supported by the following types of BTSs:BTS3012/BTS3012AE configured with the DTRU,BTS3006C/BTS3002E configured with the DDRM,BTS3900/BTS3900A configured with the DRFU,DBS3900 configured with the RRU3004 or RRU3008.
Preparation
Table 25-2 Example of the data negotiated and planned for configuring transmit diversity Parameter ID IDXTYPE CELLIDX IUOTP ENIUO Parameter Name Index Type Cell Index Cell IUO Type Enhanced Concentric Allowed Dynamic Transmission Div<PBT> Supported TRX Board No. TRX Board Path No. Example BYIDX(By Index) 0 Concentric_cell (Concentric cell) NO(NO) Source Network planning Network planning Network planning Network planning
DYNPBTSUPPOR TED
DDIVERSITY (DDiversityTransmit)
Network planning
TRXBN TRXPN
1 0
25-8
Issue 01 (2010-05-20)
Parameter ID SNDMD
Parameter Name Send Mode
Example DDIVERSITY (DDiversityTransmit)
Procedure
Step 1 On the Local Maintenance Terminal, run the MOD CELLIUO command to set Cell IUO Type to Concentric_cell(Concentric cell). Step 2 On the Local Maintenance Terminal, run the SET CELLCHMGBASIC command to set Dynamic Transmission Div<PBT> Supported to DDIVERSITY(DDIVERSITY). Step 3 On the Local Maintenance Terminal, run the MOD TRXDEV command to set Send Mode of the TRX in the overlaid subcell to DDIVERSITY(DDiversityTransmit).
NOTE
l l
You can run the LST TRXIUO command to check whether the TRX is in the overlaid subcell or in the underlaid subcell. To configure dynamic transmit diversity, two TRXs must be configured. In addition, dynamic transmit diversity cannot be configured on the MBCCH.
----End
Example
An example script for configuring dynamic transmit diversity is as follows:
MOD CELLIUO: IDXTYPE=BYIDX, CELLIDX=0, IUOTP=Concentric_cell, ENIUO=NO; SET CELLCHMGBASIC: IDXTYPE=BYIDX, CELLIDX=0, DYNPBTSUPPORTED=DDIVERSITY; MOD TRXDEV: IDXTYPE=BYIDX, CELLIDX=0, TRXBN=1, TRXPN=0, SNDMD=DDIVERSITY;
Postrequisite
l
Verifying dynamic transmit diversity 1. Monitor the channel status, and use the test MS to initiate an emergency call in an area with weak signals (such as at the boundary between an overlaid subcell and an underlaid subcell). When a call occupies a TRX with dynamic transmit diversity enabled, the channel status monitoring interface shows that the call occupies two channels on the same timeslots of two TRXs. The status of one channel is Working, whereas that of another channel is Subordinate Channel.
2.
Deactivating dynamic transmit diversity 1. On the Local Maintenance Terminal, run the SET CELLCHMGBASIC command to set Dynamic Transmission Div<PBT> Supported to NOTSUPPORT(Not Support). On the Local Maintenance Terminal, run the LST CELLCHMGBASIC command. If Dynamic Transmission Div<PBT> Supported is set to Not Support, it indicates that the dynamic transmission diversity function is deactivated.
2.
Issue 01 (2010-05-20)
26 Configuring 4-Way Receive Diversity
26
Configuring 4-Way Receive Diversity
About This Chapter

With appropriate design, the 4-way receiver diversity technology allows one TRX module to receive the uplink signals from four RX channels and then combine the uplink signals to achieve better signal quality and demodulation performance. Thus, the receive sensitivity is improved, and the receive effect is much better than that of none receiver diversity and that of two-way receiver diversity. 26.1 Installing Hardware (4-Way Receive Diversity) This describes how to connect the cables in 4-way receive diversity mode. 26.2 Configuring 4-Way Receive Diversity This describes how to configure 4-way receive diversity on the Local Maintenance Terminal.
Issue 01 (2010-05-20)
26-1
26.1 Installing Hardware (4-Way Receive Diversity)

This describes how to connect the cables in 4-way receive diversity mode.
Procedure
Step 1 This takes the BTS3012/BTS3012AE as an example. The red lines in Figure 26-1 shows the connection between the DTRU and the DDPU in 4-way receive diversity mode.
26-2
Issue 01 (2010-05-20)
Figure 26-1 Connection between the DTRU and the DDPU in 4-way receive diversity mode
DDPU
RUN ALM VSWRA VSWRB
DDPU
RUN ALM VSWRA VSWRB
COM
COM
POWER
POWER
RXA1
RXA1
DTRU
TX1
DTRU
TX1
TCOM
TCOM
TX2
RUN ACT ALM RF_IND
TX2
RUN ACT ALM RF_IND
POWER
POWER
Table 26-1 Description of ports on the DTRU Port TX1

Issue 01 (2010-05-20)
Type N female connector
Explanation TX1 output

26-3
Port TCOM TX2 RXM1 RXD1 RXM2 RXD2 PWR
Type N female connector N female connector SMA female connector SMA female connector SMA female connector SMA female connector 3V3 power connector
Explanation Combines and exports signals from TX1 and TX2 or exports PBT combined signals. TX2 output Main receive port of TRX 1 or diversity receive port 1 of TRX 1 Diversity receive port of TRX 1 or diversity receive port 2 of TRX 1 Main receive port of TRX 2 or diversity receive port 3 of TRX 1 Diversity receive port of TRX 2 or diversity receive port 4 of TRX 1 Power input
Table 26-2 Description of ports on the DDPU Port COM Type DB26 female connector Explanation
l
Receives control signal, communication signal, clock signal, and rack number signal from the DCTB of the BTS3012. Receives control signal, communication signal, and clock signal from the DSCB of the BTS3012AE.
POWER TXA TXB RXA1 RXA2 RXA3 RXA4 RXB1 RXB2 RXB3 RXB4
3V3 power connector N female connector N female connector SMA female connector SMA female connector SMA female connector SMA female connector SMA female connector SMA female connector SMA female connector SMA female connector
Power input Combined TX input from the DTRU to the DCOM Combined TX input from the DTRU to the DCOM Main output port for route 1 Main output port for route 2 Main output port for route 3 Main output port for route 4 Diversity output port for route 1 Diversity output port for route 2 Diversity output port for route 3 Diversity output port for route 4
26-4
Issue 01 (2010-05-20)
Port ANTA
Type DIN female connector
Explanation
l
Connects to the BTS3012 indoor 1/2-inch jumper or the Bias-Tee. Connects to the BTS3012AE indoor 1/4-inch jumper or the Bias-Tee. Connects to the BTS3012 indoor 1/2-inch jumper or the Bias-Tee. Connects to the BTS3012AE indoor 1/4-inch jumper or the Bias-Tee.
ANTB
DIN female connector
----End
26.2 Configuring 4-Way Receive Diversity

This describes how to configure 4-way receive diversity on the Local Maintenance Terminal. Scenario Impact The 4-way receive diversity is configured to improve the gain of the uplink signals on the radio channel and the receiver sensibility. None.
Prerequisite
l l l
Only one TRX can be configured on a DTRU. The 4-way receive diversity is restricted by the license. Activate the license on the Local Maintenance Terminal. For details, refer to Activate BSC License. The cell to which 4-way receiver diversity is applied must be configured with two dualpolarized antennas or four uni-polarized antennas. Currently, this feature is supported by the following types of BTSs: BTS3012/BTS3012AE configured with the DTRU,BTS3006C/BTS3002E configured with the DDRM, and BTS3900/BTS3900A configured with the DRFU.
Preparation
Table 26-3 Example of the data negotiated and planned for configuring 4-way receive diversity Parameter ID IDXTYPE CELLIDX TRXBN
Issue 01 (2010-05-20)
Parameter Name Index Type Cell Index TRX Board No.
Example BYIDX(By Index) 0 0

26-5
Parameter ID TRXPN RCVMD
Parameter Name TRX Board Path No. Receive Mode
Example 0 FOURDIVERSIT Y(Four Diversity Receiver)
Procedure
Step 1 On the Local Maintenance Terminal, run the MOD TRXDEV command to set Receive Mode to FOURDIVERSITY(Four Diversity Receiver).
NOTE
l l
If the TRX of the DTRU is allocated to channel O, set Send Mode to NOCOMB(NoCombin), PBT (PBT), DIVERSITY(DiversityTransmit), DDIVERSITY(DDiversityTransmit), or DPBT(DPBT). If the TRX of the DTRU is allocated to channel 1, Send Mode can be set to only NOCOMB (NoCombin).
----End
Example
An example script for configuring 4-way receive diversity is as follows:
MOD TRXDEV: IDXTYPE=BYIDX, CELLIDX=0, TRXBN=0, TRXPN=0, RCVMD=FOURDIVERSITY;
Postrequisite
l
Verifying 4-way receive diversity
On the Local Maintenance Terminal, run the LST TRXDEV command to verify that Receive Mode is set to FOURDIVERSITY(Four Diversity Receiver). It indicates that the 4-way receive diversity function is activated. On the Local Maintenance Terminal, run the MOD TRXDEV command to set Receive Mode to a value other than FOURDIVERSITY(Four Diversity Receiver). On the Local Maintenance Terminal, run the LST TRXDEV command to verify that Receive Mode is set to a value other than FOURDIVERSITY(Four Diversity Receiver). It indicates that the 4-way receive diversity function is deactivated.
Deactivating 4-way receive diversity 1.
2.
26-6
Issue 01 (2010-05-20)
27 Configuring SDCCH Dynamic Adjustment
27
Scenario Impact
Configuring SDCCH Dynamic Adjustment
SDCCH dynamic adjustment is to dynamically adjust the number of SDCCHs according to the load of the TCHs and SDCCHs. In this way, the effect of the initial configuration of the SDCCH on the system is minimized, and radio resources are fully utilized.This describes how to configure SDCCH dynamic adjustment on the Local Maintenance Terminal. The SDCCH dynamic adjustment is performed to reduce the SDCCH congestion rate and the impact of the SDCCH initial configuration on the system performance. The SDCCH dynamic adjustment can decrease the TCH traffic bearer capability and increase intra-cell handovers.
NEs Involved BTS, BSC.
Preparation
Table 27-1 Example of the data negotiated and planned for configuring SDCCH dynamic adjustment Parameter ID IDXTYPE CELLIDX SDDYN IDLESDTHRES CELLMAXSD MINRESTIMETC H Parameter Name Index Type Cell Index SDCCH Dynamic Allocation Allowed Idle SDCCH Threshold N1 Cell SDCCH Channel Maximum TCH Minimum Recovery Time<s> Example BYIDX(By Index) 0 YES(YES) 2 80 60 Source Network planning Network planning Network planning Network planning Network planning Network planning
Issue 01 (2010-05-20)
27-1
27 Configuring SDCCH Dynamic Adjustment
Procedure
Step 1 On the Local Maintenance Terminal, run the MOD CELLBASICPARA command to set SDCCH Dynamic Allocation Allowed to YES(YES). Step 2 On the Local Maintenance Terminal, run the SET CELLCHMGBASIC command to set Idle SDCCH Threshold N1, Cell SDCCH Channel Maximum, and TCH Minimum Recovery Time<s>. ----End
Example
An example script for configuring SDCCH dynamic adjustment is as follows:
MOD CELLBASICPARA: IDXTYPE=BYIDX, CELLIDX=0, SDDYN=YES; SET CELLCHMGBASIC: IDXTYPE=BYIDX, CELLIDX=0, IDLESDTHRES=2, CELLMAXSD=80, MINRESTIMETCH=60;
Postrequisite
l
Verifying SDCCH dynamic adjustment
On the Local Maintenance Terminal, run the LST CELLBASICPARA command. If SDCCH Dynamic Allocation Allowed is set to YES, it indicates that the function of SDCCH dynamic adjustment is activated. On the Local Maintenance Terminal, run the MOD CELLBASICPARA command to set SDCCH Dynamic Allocation Allowed to NO(No). On the Local Maintenance Terminal, run the LST CELLBASICPARA command. If SDCCH Dynamic Allocation Allowed is set to No, it indicates that the function of SDCCH dynamic adjustment is deactivated.
Deactivating SDCCH dynamic adjustment 1. 2.
27-2
Issue 01 (2010-05-20)
28 Configuring NACC
28
Scenario Impact None. NEs Involved MS, BSC, and PCU.
Configuring NACC
NACC refers to network-assisted cell reselection. To implement rapid PS access after cell reselection, the BSC sends the system information about the target cell to the MS before cell reselection. Therefore, the service interruption time due to the cell reselection is minimized. This describes how to configure NACC on the Local Maintenance Terminal. NACC is configured to reduce the time of service interruption caused by the cell reselection.
Prerequisite
l l l
The cell supports the GPRS services. NACC is restricted by the license. Activate the license on the Local Maintenance Terminal. For details, refer to Activate BSC License.
Preparation
Table 28-1 Example of the data negotiated and planned for configuring NACC Parameter ID IDXTYPE CELLIDX NCO GPRS NACCSPT Parameter Name Index Type Cell Index Network Control Mode GPRS NaccSpt Example BYIDX(By Index) 0 nc0(nc0) SupportAsInnPcu (SupportAsInnPcu) YES(Yes) Source Network planning Network planning Network planning Network planning Network planning
Issue 01 (2010-05-20)
28-1
28 Configuring NACC
Procedure
Step 1 On the Local Maintenance Terminal, run the SET PSBASE command to set Network Control Mode to nc0(nc0) or nc1(nc1). Step 2 On the Local Maintenance Terminal, run the SET CELLGPRS command. 1. 2. Set GPRS to SupportAsInnPcu(SupportAsInnPcu) or SupportAsExtPcu (SupportAsExtPcu) as required. Set NaccSpt to YES(Yes).
----End
Example
An example script for configuring NACC is as follows:
SET PSBASE: IDXTYPE=BYCELLIDX, CELLIDX=0, NCO=nc0; SET CELLGPRS: IDXTYPE=BYIDX, CELLIDX=0, GPRS=SupportAsInnPcu, NACCSPT=YES;
Postrequisite
l
Verifying NACC 1. On the Local Maintenance Terminal, run the SET CELLGPRS command to set Nc2Spt to NO(No).
NOTE
When Network Control Mode is set to NC2, the cell reselection procedure is the NC2 procedure. Thus, you are advised to disable the NC2 function before verifying NACC.
2. 3. 4.
Make an MS camp on the serving cell. Then, activate the GPRS services and trace the signaling on the Um interface. Adjust the position of the MS or increase the power of the target cell so that the level of the target cell is higher than that of the serving cell. Trace PS messages on the Um interface. When detecting that the signal strength of the serving cell weakens and that a neighboring cell with better signal strength is available, the MS sends a PACKET CELL CHANGE NOTIFICATION message to the BSC. After receiving the message, the BSC replies a PACKET NEIGHBOUR CELL DATA message containing SI1, SI3, and SI13 of the target cell. Then, the BSC sends a PACKET CELL CHANGE CONTINUE message to the MS to instruct the MS to continue with cell reselection. On the Local Maintenance Terminal, run the SET CELLGPRS command to set NaccSpt to NO(No). The operations for verifying deactivation of NACC are the same as those for Verifying NACC. Verify that the message interchange in Verifying NACC does not exist.
Deactivating NACC 1. 2.
28-2
Issue 01 (2010-05-20)
29 Configuring NC2
29
Scenario Impact None. NEs Involved MS, BSC.
Configuring NC2
The network-controlled cell reselection (NC2) refers to the situation that the MS in packet transfer mode can be controlled by the network to reselect a cell according to the measurement report.This describes how to configure NC2 on the Local Maintenance Terminal. With NC2, the network instructs the MS to perform cell reselection.
Prerequisite
l l l
The cell supports the GPRS services. NC2 is restricted by the license. Activate the license on the Local Maintenance Terminal. For details, refer to Activate BSC License.
Preparation
Table 29-1 Example of the data negotiated and planned for configuring NC2 Parameter ID IDXTYPE CELLIDX NCO GPRS NC2SPT Parameter Name Index Type Cell Index Network Control Mode GPRS Nc2Spt Example BYIDX(By Index) 0 nc2(nc2) SupportAsInnPcu (SupportAsInnPcu) YES(Yes) Source Network planning Network planning Network planning Network planning Network planning
Issue 01 (2010-05-20)
29-1
29 Configuring NC2
Procedure
Step 1 On the Local Maintenance Terminal, run the SET PSBASE command to set Network Control Mode to nc2(nc2). Step 2 On the Local Maintenance Terminal, run the SET CELLGPRS command. 1. 2. Set GPRS to SupportAsInnPcu(SupportAsInnPcu) or SupportAsExtPcu (SupportAsExtPcu) as required. Set Nc2Spt to YES(Yes).
----End
Example
An example script for configuring NC2 is as follows:
SET PSBASE: IDXTYPE=BYCELLIDX, CELLIDX=0, NCO=nc2; SET CELLGPRS: IDXTYPE=BYIDX, CELLIDX=0, GPRS=SupportAsInnPcu, NC2SPT=YES;
Postrequisite
l
Verifying NC2 1. 2. 3. Start the tracing of the messages on the Um interface. For details, see Tracing PS Domain Messages on the Um Interface in the BSC LMT User Guide. Make an MS camp on the serving cell. Then, activate the GPRS services and trace the signaling on the Um interface. Verify that network-control-order in the Packet PSI13 message is NC2 in the tracing result. On the Local Maintenance Terminal, run the SET CELLGPRS command, and set Nc2Spt to NO(No). Verifying the deactivation of NC2: The operations are the same as those for Verifying NC2. Verify that network-control-order in the Packet PSI13 message is not NC2.
Deactivating NC2 1. 2.
29-2
Issue 01 (2010-05-20)
30 Configuring Packet Performance Improvement
30
Prerequisite Context
Configuring Packet Performance Improvement
This describes how to configure packet performance improvement on the external PCU maintenance console or Local Maintenance Terminal.
The packet performance improvement function is not license-controlled.
Extended uplink TBF can decrease transmission delay, 11-bit EGPRS access on CCCH can improve the EDGE MS performance, and takeover of the packet immediate assignment by the BTS can improve MS access performance and decrease access delay. For PCU commands, see the Manual of Commands related to the PCU.
NOTE
l l
When the PCU is in external mode, the BSC6000V900R008C02 and later versions support takeover of immediate assignment and packet assignment by the BTS When the PCU is in external mode, you can run the pcu cfgpara add<BoardNo>g_bCellSptImmAssDlShift 4 0 command to disable the function of takeover of immediate assignment by the BTS, and you can run the pcu cfgpara add<BoardNo>g_bCellSptPackAssDlShift 4 0 command to disable the function of takeover of packet assignment by the BTS. Then, reset the cell.
Procedure
Step 1 Configure extended uplink TBF.
l
In external PCU mode, run the PCU add privateoptpara command on the PCU maintenance terminal to configure the duration of the inactive period timer. To configure the duration of the inactive period timer to 2000 ms, run the following command: pcu add privateoptpara<LCNo><PSPrecedence><UpTbfRelDelay>2000<DnTbfRelDelay>
In built-in PCU mode, run the SET PRIVATEOPTPARA command on the Local Maintenance Terminal to configure the duration of the inactive period timer.
Issue 01 (2010-05-20)
30 Configuring Packet Performance Improvement
Step 2 Configuring EGPRS access of 11-bit messages on the CCCH.

l
In external PCU mode, run the PCU set egprspara command on the PCU maintenance terminal to configure the EGPRS access of 11-bit messages on the CCCH for the cell.
To enable the EGPRS access of 11-bit messages on the CCCH for the cell, run the following command: pcu set egprspara<LCNo><LQCMode> <BepPeriod>yes<UpFixMcs><UpDefaultMcs><DnFixMcs><DnDefaultMcs>
To disable the EGPRS access of 11-bit messages on the CCCH for the cell, run the following command: pcu set egprspara<LCNo><LQCMode> <BepPeriod>no<UpFixMcs><UpDefaultMcs><DnFixMcs><DnDefaultMcs>
In built-in PCU mode, run the SET PSBASE command on the Local Maintenance Terminal to enable the EGPRS access of 11-bit messages.
Step 3 Configure takeover of immediate assignment by the BTS.

l
In external PCU mode, run the pcu cfgpara add<BoardNo>g_bCellSptImmAssDlShift 4 1 command on the PCU maintenance terminal to configure takeover of immediate assignment by the BTS. Then, reset the cell. In built-in PCU mode, run the SET PSOTHERPARA command on the Local Maintenance Terminal to configure takeover of immediate assignment by the BTS.
Step 4 Configure takeover of packet assignment by the BTS.

l
In external PCU mode, run the pcu cfgpara add<BoardNo>g_bCellSptPackAssDlShift 4 1 command on the PCU maintenance terminal to configure takeover of packet assignment by the BTS. Then, reset the cell. In built-in PCU mode, run the SET PSOTHERPARA command on the Local Maintenance Terminal to configure takeover of packet assignment by the BTS.
----End
Postrequisite
l
Verifying Packet Performance Improvement 1. Extended uplink TBF
Connect an MS supporting the GERAN Feature Package 1 to a PC to test the Ping service performance, with the extended uplink TBF enabled and disabled. Connect an EGPRS capable MS to a PC to test the Ping service performance, with the EGPRS access of 11-bit messages on the CCCH enabled and disabled. Connect an MS to a PC to test the Ping service performance, with the takeover of packet assignment by the BTS enabled and disabled. Connect an MS to a PC to test the Ping service performance, with the takeover of immediate assignment by the BTS enabled and disabled.
2.
EGPRS access of 11-bit messages on the CCCH
3.
Takeover of immediate and packet immediate assignments by the BTS
30-2
Issue 01 (2010-05-20)
31 Configuring Flex Abis
31
About This Chapter
Configuring Flex Abis
Flex Abis implements the sharing of the transmission resources on the Abis interface between different BTSs, cells, and services, and thus improves the resource utilization. Flex Abis is an allocation mode of the transmission resources on the Abis interface. That is, the transmission resources on the Abis interface form a resource pool to share resources between CS services and PS services (including idle timeslots) and also between different cells or BTSs. Especially when Flex Abis is enabled in multi-cell large capacity BTSs, cascading BTSs, and the cells configured with the EGPRS function, the transmission resources on the Abis interface can be used in an efficient way.
Context
For the impact of configuring the Flex Abis on the system, see BSS Feature Description. 31.1 Configuring Flex Abis This describes how to configure Flex Abis on the Local Maintenance Terminal. 31.2 Configuring Exclusive Timeslot This describes how to configure exclusive timeslots on the Local Maintenance Terminal.
Issue 01 (2010-05-20)
31-1
31.1 Configuring Flex Abis

This describes how to configure Flex Abis on the Local Maintenance Terminal. Scenario Impact With the Flex Abis feature, the utilization of the transmission resources on the Abis interface are greatly improved. The signaling load on the Abis interface is increased and the reliability of the system is reduced.
Prerequisite
l l
The configuration of Flex Abis is license-controlled. The license is activated through the Local Maintenance Terminal. For details, see Activate BSC License. Flex Abis serves as the basis of the BTS local switching. After the BTS local switching is performed, the occupied transmission resources on the Abis interface are released. This can save the transmission resources on the Abis interface. The Flex Abis and Abis bypass functions can be enabled simultaneously. When BTS ring topology I and Flex Abis are simultaneously enabled, the following restrictions should apply:
l l
Flex Abis must be enabled in all the BTSs, and only the forward and reverse single E1 link is supported. The Abis bypass function is not supported. The 16 kbit/s LAPD link is not supported.
31-2
Issue 01 (2010-05-20)
Preparation
NOTE
l l
When Flex Abis is enabled, Multiplexing Mode can be set to 5:1 or 6:1 to multiplex five or six RSLs onto a 64 kbit/s timeslot. This can prevent an additional 64 kbit/s timeslot from being occupied. When the BTS is initially configured, Flex Abis Mode is set to FLEX_ABIS(Flex Abis) or SEMI_ABIS(Semisolid Abis) to enable Flex Abis. If Flex abis needs to be enabled after the BTS is configure, set Flex Abis Mode to FLEX_ABIS(Flex Abis) or SEMI_ABIS(Semisolid Abis). When Flex Abis is enabled and Abis Resource Adjustment TCHH Function Switch is set to YES (YES), the system allocates TCHHs preferentially if the fixed Abis channel seizure rate exceeds Fix Abis Prior Choose Abis Load Thred{%} and the Flex Abis channel seizure rate exceeds Flex Abis Prior Choose Abis Load Thred{%}. After Flex Abis is enabled, the Abis transmission resources may be insufficient even if there are still available TCHFs. In this case, the allocation of TCHHs can be triggered based on the Abis transmission resource load to increase the call access success rate. After Flex Abis is enabled in the BSC, the transmission resources on the Abis interface can be dynamically allocated without configuring the static PDTCH and idle timeslots if the actual traffic volume is smaller than the estimated value in network design. That is, the primary link and secondary link are dynamically allocated. When Flex Abis is enabled, the CS services and PS services share the transmission resources on the Abis interface.
l l
The CS services can preempt the resources of PS services on the secondary link (or even the primary link if necessary) in a BTS and its lower-level BTS. If there are lower-level BTSs, you are advised to set both Sublink resources preemption switch and Lower-level sublink resources preemption switch to Yes. In this manner, the access success rate of the CS service users is increased if the Abis transmission resources are insufficient. If there are no lower-level BTSs, you need to set only Sublink resources preemption switch to Yes to increase the access success rate of the CS service users if the Abis transmission resources are insufficient. When the built-in PCU is configured, Sub Res Preempt Flag is set to YES(YES) to allow the CS services to preempt the resources of PS services on the secondary link in the same-level BTSs. Low Lev Sub Res Preempt Flag is set to YES(YES) to allow the CS services to preempt the resources of PS services on the secondary link in the lower-level BTSs. When the external PCU is configured, PCU Support PREEMPT_ABIS_LINK message is set to YES(YES) to allow the BSC to send a PREEMPT_ABIS_LINK message to the PCU so that the CS services can preempt the transmission resources occupied by the PCU if the PCU supports the processing of this message.
After a call is released, the transmission link that the call uses can be reserved if a new call can totally or partly uses the link. In this manner, the Abis interface transmission link can be quickly established when the new call arrives. To enable this function, you need to set FlexAbis Bypast-connect Status to Yes. If the Flex Abis function is enabled on the BTS, and if the extension cabinet group is directly connected to the BSC, the Abis timeslots allocated to the extension cabinet group are displayed as TCH, indicating fixed timeslots, as shown in Figure 31-1. If the extension cabinet group needs to process data services, and if the high-rate coding schemes (CS3 and CS4; MCS3 to MCS9) are required, idle timeslots need to be configured. If the Flex Abis function is enabled on the BTS, and if the channel type is changed to static PDCH, the type of corresponding Abis timeslots is automatically changed to TCH, indicating fixed timeslots. In the case of cascaded BTSs, if an upper-level BTS is in Flex Abis mode, and if a lower-level BTS is in SemiSolid mode, the type of the timeslots allocated to the lower BTS is displayed as TCH, indicating fixed timeslots, but the timeslot type that the upper-level BTS reports to the BSC is displayed as Flex.If the lower-level BTS needs to process data services, and if the high-rate coding schemes (CS3 and CS4; MCS3 to MCS9) are required, idle timeslots need to be configured.
l l
Issue 01 (2010-05-20)
31-3
Figure 31-1 Configuration of BTS combined cabinets and cabinet groups
BTS
Master cabinet group
Flex Abis/SemiSolid BSC
Extension cabinet group Fix Abis
The following is an example of configuring Flex Abis for the BTS3012 in TDM service mode. Table 31-1 Example of the data negotiated and planned for configuring Flex Abis Parameter ID BTSNAME TYPE UPNODE SRN SN PN BTSDESC MPMODE FlexAbisMode Parameter Name BTS name BTS Type Up Node Type Subrack No. Slot No. Port No. BTS Description Multiplexing Mode Flex Abis Mode Example BTS3012 BTS3012 BSC 0 26 0 TDM BTS3012 MODE4_1 FLEX_ABIS(Flex Abis) Source Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning
31-4
Issue 01 (2010-05-20)
Parameter ID AbisByPassMod e ServiceMode DCELLNAME DCTYPE DCMCC DCMNC DCLAC DCCI CPLMode TRXBN FREQ SUBRESPREE MPTFLG LOWLEVSUBR ESPREEMPTFL G ABISRESADJT CHHFUNSWIT CH FIXABISPRIOR ABISLOADTH RED FLEXABISPRI ORABISLOAD THRED FLEXABISUSE CONNSTATE
Parameter Name Abis By Pass Mode Service Type Cell Name Cell Type Cell MCC Cell MNC Cell LAC Cell CI Separate Mode TRX Board No. TRX Freq. Sub Res Preempt Flag Low Lev Sub Res Preempt Flag Abis Resource Adjustment TCHH Function Switch Fix Abis Prior Choose Abis Load Thred{%} Flex Abis Prior Choose Abis Load Thred{%} FlexAbis Bypastconnect Status
Example FALSE(Not Support) TDM TDMCELL GSM900 460 01 8240 1 UNSUPPORT(Not Support) 0 988 YES(YES) YES(YES)
YES(YES)
Network planning
80
Network planning
85
Network planning
YES(YES)
Network planning
Procedure
Step 1 On the Local Maintenance Terminal, run the ADD BTS command. Add a BTS and set the Flex Abis Mode to FLEX_ABIS(Flex Abis). Step 2 On the Local Maintenance Terminal, run the MOD FLEXABIS command to configure parameters of Flex Abis.
Issue 01 (2010-05-20)
31-5
Step 3 (Optional)On the Local Maintenance Terminal, run the SET OTHSOFTPARA command, set the FlexAbis Bypast-connect Status to YES(YES). ----End
Example
An example script of configuring Flex Abis on BTS3012 in TDM service mode is as follows:
*Add a BTS3012*/ ADD BTS: BTSNAME="BTS3012", TYPE=BTS3012, UPNODE=BSC, SRN=0, SN=26, PN=0, BTSDESC="TDM BTS3012", MPMODE=MODE4_1, FlexAbisMode=FLEX_ABIS, ServiceMode=TDM, DCELLNAME="TDMCELL", DCTYPE=GSM900, DCMCC="460", DCMNC="01", DCLAC=8240, DCCI=1, CPLMode=UNSUPPORT, TRXBN=0, FREQ=988; /*Configure Flex Abis parameters*/ MOD FLEXABIS: IDXTYPE=BYNAME, BTSNAME="BTS3012", MODE=FLEX_ABIS, SUBRESPREEMPTFLG=YES, LOWLEVSUBRESPREEMPTFLG=YES, ABISRESADJTCHHFUNSWITCH=YES, FIXABISPRIORABISLOADTHRED=80, FLEXABISPRIORABISLOADTHRED=85; /*Configure FlexAbis Bypast-connect Status*/ SET OTHSOFTPARA: FlexAbisUseConnState=YES;
Postrequisite
l
Verifying Flex Abis 1. On the Local Maintenance Terminal, run the MOD FLEXABIS command to set Abis By Pass Mode to FLEX_ABIS(Flex Abis) and Multiplexing Mode to MODE16K. On the Local Maintenance Terminal, run the LST BTSTS command to query the timeslots on the ports of the BTS. On the Local Maintenance Terminal, run the SET BTSFORBIDTS command to block the Flex Abis timeslots. To block the Flex Abis timeslots, do as follows: Select Start Timeslot NO., Start Sub Timeslot NO., End Timeslot NO., and End Sub Timeslot NO. according to the Flex Abis timeslots and sub-timeslots queried in Step 2. Then, block the Flex Abis timeslots and sub-timeslots until only two consecutive 8 kbit/s Flex Abis sub-timeslots are available.
NOTE
2. 3.
Do not block any timeslot other than Flex Abis timeslots. Reserve only one 16 kbit/s subtimeslot for services during the test because the timeslots are blocked in unit of 16 kbit/s subtimeslots.
4. 5.
Leave only cell 1 with the main BCCH, SDCCH, and two TCHs by deactivating cells through MOD CELLACS and blocking channels through SET BTSOBJ. Use the test MS to call a fixed-line phone in the cell, and hold on the call. Run the DSP ABISTS command to query the timeslot status. Verify that State is set to OCCUPIED(Occupied). It is found that the Abis timeslot corresponding to the channel occupied by the call is the unblocked Flex Abis timeslot. End the call and block the occupied TCH. Then, only one unblocked channel is available. Use the test MS to initiate a call in the cell, and hold on the call. Run the DSP ABISTS command to query the timeslot status. Verify that State is set to OCCUPIED (Occupied). The call occupies another TCH in the cell. The Abis timeslot
6. 7.
31-6
corresponding to the occupied TCH is the unblocked Flex Abis timeslot. This indicates that the configuration takes effect. 8.
l
Release the call. On the Local Maintenance Terminal, run the MOD FLEXABIS command to set Abis By Pass Mode to FIX_ABIS(Fix Abis). On the Local Maintenance Terminal, run the LST FLEXABIS command to verify that Abis By Pass Mode is set to FIX_ABIS(Fix Abis).
Deactivating Flex Abis 1. 2.
31.2 Configuring Exclusive Timeslot

This describes how to configure exclusive timeslots on the Local Maintenance Terminal. Scenario Impact Test the timeslots on the port to check whether the timeslots work normally. None

NOTE
If a timeslot on the port is disabled, it cannot serve as an OML, an RSL, or a TCH. The test personnel disables the other timeslots on the port to check whether a timeslot without being disabled work normally.
Prerequisite
l
Both the GXPUM and GXPUT are configured. There are idle ports on the configured GEIUB. The BTS is configured.
Preparation
Table 31-2 Example of the data negotiated and planned for configuring exclusive timeslots Parameter ID IDXTYPE BTSNAME OPTYPE PN STARTTS ENDTS Parameter Name Index Type BTS name Operate Type Port No. Start Timeslot No. End Timeslot No. Example BYNAME (By Name) BTS3012 FORBID(Forbid) 0 10 23 Source Network planning Network planning Network planning Network planning Network planning Network planning
Procedure
Step 1 On the Local Maintenance Terminal, run the SET BTSFORBIDTS command to disable the specified timeslots on a BTS.

NOTE
You can also run this command to enable the exclusive timeslots, numbered from 1 to 30.
----End
Example
Disable the timeslots from 10 to 23 on the BTS3012. An example script of configuring exclusive timeslots is as follows:
SET BTSFORBIDTS: IDXTYPE=BYNAME, BTSNAME="BTS3012", OPTYPE=FORBID, PN=0, STARTTS=10, ENDTS=23;
Postrequisite
l
Verifying exclusive timeslot
On the Local Maintenance Terminal, run the LST BTSTS command to view the timeslots on the ports of the BTS. On the Local Maintenance Terminal, run the SET BTSFORBIDTS command to set Operate Type to RESTORE(Restore). On the Local Maintenance Terminal, run the LST BTSTS command to view the timeslots on the ports of the BTS.
Unblocking exclusive timeslot 1. 2.
31-8
Issue 01 (2010-05-20)
32 Configuring the MSC Pool
32
About This Chapter
Prerequisite
l l l l
Configuring the MSC Pool
With this feature, a maximum of 32 MSCs form a resource pool to provide services for the subscribers under one group of BSCs. Through the MSC pool, one BSC can be connected to multiple MSCs at the same time. In addition, the traffic on the BSC is evenly distributed to the MSCs in the pool according to the NRI or load balancing principle.
The BSC and the MSC are Huawei devices. The MSC server interconnects with the MGW, and the relevant data is configured correctly. The MSC pool requires a license. Activate the license on the Local Maintenance Terminal. For details, see Activate BSC License.
32.1 Configuring MSC Pool (A over TDM) This describes how to verify the MSC pool in A over TDM on the Local Maintenance Terminal. 32.2 Configuring the MSC Pool (A over IP) This describes how to configure the MSC pool in A over IP on the Local Maintenance Terminal.
Issue 01 (2010-05-20)
32-1
32.1 Configuring MSC Pool (A over TDM)

This describes how to verify the MSC pool in A over TDM on the Local Maintenance Terminal. Scenario Impact In A over TDM, the traffic volume is evenly distributed in the MSC pool. None.
Preparation
The prerequisites of the operation is that the mapping between the OPC and the subrack is configured. This describes how to configure the MSC pool in A over TDM on the BSC. Table 32-1 Example of the data negotiated and planned for configuring MSC Pool in A over TDM Data Type DPC attributes Parameter ID NAME DPC DPCGIDX CNID Attributes of E1 on the A interface SRN SN PN STCIC DPCGIDX MSC pool switch attributes OPNAME Parameter Name DPC Name DPC Code DPC Group Index MSC ID Subrack No. Slot No. Port No. Start CIC DPC Group Index Operator Name Example dsp1 h'cc 0 0 5 14 0 0 0 46000 Source Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning
32-2
Issue 01 (2010-05-20)
Data Type
Parameter ID MSCPOOLAL LOW NRILEN MSCNULLNR I
Parameter Name MSC Pool Function Enabled Length of NRI in TMSI NULL-NRI Value NRI Value DPC
Example YES(Yes)
3 4 3 h'cc
Mapping between the NRI and the MSC
NRI DPC
Procedure
Step 1 Configure the data of the MSC server and the MGW.For details on parameter settings, see relevant user manuals of the MSC. 1. 2. For Huawei core network devices, enable the MSC pool on the MSC side. Configure the parameters related to the MSC pool, such as the NRI and NULL_NRI of each MSC, available capacity of the MSC, MNC, and MSC ID. For details on parameter settings, see the user manuals related to the MSC products.
Step 2 On the Local Maintenance Terminal, run the ADD N7DPC command to add DPCs.
NOTE
When you add multiple DPCs, the first DPC is the default signaling point. You can run the MOD N7DPC command to modify the default signaling point.
Step 3 On the Local Maintenance Terminal, run the ADD AE1T1 command to add E1s on the A interface. The start CICs of different ports within a DPC group cannot be duplicate. Step 4 On the Local Maintenance Terminal, run the SET MSCPOOL command. Set MSC Pool Function Enabled to YES(Yes) and specify Length of NRI in TMSI and NULL-NRI Value. Step 5 On the Local Maintenance Terminal, run the ADD NRIMSCMAP command to configure the mapping between the NRI and the MSC. ----End
Example
Assume that the OPC is configured according to the network planning. Example scripts are as follows:
/*Add a DPC*/ ADD N7DPC: NAME="dsp1", DPC=h'cc, DPCGIDX=0, CNID=0; /*Add an E1 on the A interface*/ ADD AE1T1: SRN=5, SN=14, PN=0, STCIC=0, DPCGIDX=0; /*Enable the MSC pool function*/ SET MSCPOOL: OPNAME="46000", MSCPOOLALLOW=YES, NRILEN=3, MSCNULLNRI=4;
Issue 01 (2010-05-20)
32-3
/*Configure the mapping between the NRI and the MSC*/ ADD NRIMSCMAP: NRI=3, DPC=h'cc;
Postrequisite
l
Verifying MSC Pool (A over TDM) 1. 2. Combine MSC 1 and MSC 2 to form an MSC pool. Then, enable the TMSI reallocation function on the core network side. On the BSC side, run the SET MSCPOOL command to enable the MSC pool function. In addition, ensure that the values of parameters such as Length of NRI in TMSI and NULL-NRI are same as those on the MSC side, and ensure that the BSC status and MSC status are normal. Get two MSs that are registered in the MSC pool ready. Start the trace of the messages on the A interface. Set DPC Code(Hex) to the DPC code of MSC 1/MSC 2, and set Selected Cells on the BSSAP tab page to the cell where the MS camps. Verify the A signaling messages between BSC and MSC 1/ MSC 2. Power on MS 1 so that MS 1 initiates the location update procedure on MSC 1. Then, the core network allocates the TMSI to MS 1. Power on MS 2 so that MS 2 initiates the location update procedure on MSC 2. Then, the core network allocates the TMSI to MS 2.
NOTE
3. 4.
5. 6.
If you want to make an MS to initiate the location update procedure on a specific MSC, run the MOD N7DPC command to set MSC Administrable State of the MSCs except for this specific MSC to UNAVAIL(Unavail). After the location update is complete, change the value of MSC Administrable State to NORMAL(Normal).
7. 8.
Run the MOD N7DPC command to set MSC Administrable State of MS 1 to UNAVAIL(Unavail). Use MS 1 to call MS 2 in the area covered by the MSC pool. Verify that the call is normal, and MSC 2 assigns a new TMSI to MS 1 according to the messages traced over the A interface. On the Local Maintenance Terminal, run the SET MSCPOOL command to set MSC Pool Function Enabled to NO(No). On the Local Maintenance Terminal, run the LST MSCPOOL command to verify that MSC Pool Function Enabled is set to NO. It indicates that the MSC pool(A over TDM) function is deactivated.
Deactivating MSC pool(A over TDM) 1. 2.
32.2 Configuring the MSC Pool (A over IP)

This describes how to configure the MSC pool in A over IP on the Local Maintenance Terminal. Scenario Impact In A over IP, the traffic volume is evenly distributed in the MSC pool. None.
32-4
Issue 01 (2010-05-20)
Preparation
The prerequisites of the operation is that the M3UA local entity and the mapping between the OPC and the subrack is configured. This describes how to configure the MSC pool in A over IP on the BSC. Table 32-2 Example of the data negotiated and planned for configuring links on the A interface Data Type M3UA destination entity Parameter ID DENO NAME DPC RTCONTEXT SSN CNID M3UA link set SIGLKSIDX NAME DENO Parameter Name Destination Entity No. Destination Entity Name DPC Code Routing Context Subsystem Number Network Element ID Signaling Link Set Index Signaling Link Set Name Adjacent Destination Entity No. Destination Entity No. Signaling Link Set Index Signaling Link Set Index Subrack No. Local Port No. Destination Port No. Example 1 m3de h'cc 0 254 0 0 linkset_1 1 Source Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning
M3UA route
DENO SIGLKSIDX
1 0 0 0 2048 2048
M3UA link
SIGLKSIDX SRN LOCPN PEERPN
Issue 01 (2010-05-20)
32-5
Data Type
Parameter ID LOCIP1 PEERIP1
Parameter Name First Local IP Address First Destination IP Address
Example 192.168.10.2 192.168.30.1
Table 32-3 Example of the data negotiated and planned for configuring MSC Pool in A over IP Data Type MSC pool switch attributes Parameter ID OPNAME MSCPOOLAL LOW NRILEN MSCNULLNR I Mapping between the NRI and the MSC NRI DPC Parameter Name Operator Name MSC Pool Function Enabled Length of NRI in TMSI NULL-NRI Value NRI Value DPC Example 46000 YES(Yes) Source Network planning Network planning Network planning Network planning Network planning Network planning
3 4 3 h'cc
Procedure
Step 1 Configure the data of the MSC server and the MGW.For details on parameter settings, see relevant user manuals of the MSC. 1. 2. For Huawei core network devices, enable the MSC pool on the MSC side. Configure the parameters related to the MSC pool, such as the NRI and NULL_NRI of each MSC, available capacity of the MSC, MNC, and MSC ID. For details on parameter settings, see the user manuals related to the MSC products.
Step 2 On the Local Maintenance Terminal, run the ADD M3DE command to add M3UA destination entities. Step 3 On the Local Maintenance Terminal, run the ADD M3LKS command to add M3UA link sets. Step 4 On the Local Maintenance Terminal, run the ADD M3RT command to add the M3UA route. Step 5 Configure GFGUA/GOGUA.
Step 6 On the Local Maintenance Terminal, run the ADD M3LNK command to add M3UA links. Step 7 On the Local Maintenance Terminal, run the SET MSCPOOL command to configure the parameters related to the MSC pool. Set MSC Pool Function Enabled to YES(Yes) and specify Length of NRI in TMSI and NULL-NRI Value. Step 8 On the Local Maintenance Terminal, run the ADD NRIMSCMAP command to configure the mapping between the NRI and the MSC. ----End
Example
Assume that the M3UA local entity is configured according to the network planning. Example scripts are as follows:
/*Add an M3UA destination entity*/ ADD M3DE: DENO=1, NAME="m3de", DPC=h'cc, RTCONTEXT=0, SSN=254, CNID=0; /*Add an M3UA link set*/ ADD M3LKS: SIGLKSIDX=0, NAME="linkset_1", DENO=1; /*Add an M3UA route*/ ADD M3RT: DENO=1, SIGLKSIDX=0; /*Add an M3UA link*/ ADD M3LNK: SIGLKSIDX=0, SRN=0, LOCPN=2048, PEERPN=2048, LOCIP1="1.1.1.1", PEERIP1="2.2.2.2"; /*Enable the MSC pool function*/ SET MSCPOOL: OPNAME="46000", MSCPOOLALLOW=YES, NRILEN=3, MSCNULLNRI=4; /*Configure the mapping between the NRI and the MSC*/ ADD NRIMSCMAP: NRI=3, DPC=h'cc;
Postrequisite
l
Verifying MSC pool (A over IP) 1. 2. Combine MSC 1 and MSC 2 to form an MSC pool. Then, enable the TMSI reallocation function on the core network side. On the BSC side, run the SET MSCPOOL command to enable the MSC pool function. In addition, ensure the values of parameters such as Length of NRI in TMSI and NULL-NRI are same as those on the MSC side, and ensure the BSC status and MSC status are normal. Get ready two MSs that are registered in the MSC pool. Start the trace of the messages on the A interface. Set DPC Code(Hex) to the DPC code of MSC 1/MSC 2, and set Selected Cells on the BSSAP tab page to the cell where the MS camps. Verify the A signaling messages between BSC and MSC 1/ MSC 2. Power on MS 1 so that MS 1 initiates the location update procedure on MSC 1. Then, the core network allocates the TMSI to MS 1. Power on MS 2 so that MS 2 initiates the location update procedure on MSC 2. Then, the core network allocates the TMSI to MS 2.
NOTE
3. 4.
5. 6.
If you want to make an MS to initiate the location update procedure on a specific MSC, run the MOD N7DPC command to set MSC Administrable State of the MSCs except for this specific MSC to UNAVAIL(Unavail). After the location update is complete, change the value of MSC Administrable State to NORMAL(Normal).
7.
Run the MOD N7DPC command to set MSC Administrable State of MS 1 to UNAVAIL(Unavail).
Issue 01 (2010-05-20)
8.
Use MS 1 to call MS 2 in the area covered by the MSC pool. Verify that the call is normal, and MSC 2 assigns a new TMSI to MS 1 according to the messages traced over the A interface. On the Local Maintenance Terminal, run the SET MSCPOOL command to set MSC Pool Function Enabled to NO(No). On the Local Maintenance Terminal, run the LST MSCPOOL command to verify that MSC Pool Function Enabled is set to NO. It indicates that the MSC pool(A over IP) function is deactivated.
Deactivating MSC pool(A over IP) 1. 2.
32-8
Issue 01 (2010-05-20)
33 Configuring BTS Ring Topology
33
Context
Configuring BTS Ring Topology
About This Chapter

The ring networking mode is a special chain networking mode. Several BTSs form a chain, and the lowest-level BTS is connected to the BSC through the transmission link, thus forming a ring. If there is a breakpoint on the ring, the BTSs that precede the breakpoint remain unchanged in networking mode whereas the BTSs that follow the breakpoint form a new chain connection in the reverse direction. The BTS ring topology is categorized into two types: Huawei BTS ring topology I and Huawei BTS ring topology II.
In BTS ring topology I, the reverse-link BTS is reinitialized after the transmission is interrupted, the BTS services are disrupted. In BTS ring topology II, the services of the reverse-link BTS are not disrupted after the transmission is interrupted. 33.1 Configuring BTS Ring Topology This describes how to configure the BTS ring topology on the Local Maintenance Terminal. 33.2 Changing Non-Ring Topology to Ring Topology This describes how to change a BTS in non-ring topology to a BTS in ring topology on the Local Maintenance Terminal. 33.3 Querying BTS Ring Topology This describes how to query the ring topology attributes of a BTS on the Local Maintenance Terminal. 33.4 Deleting a BTS from the Ring Topology This describes how to delete a BTS from the ring topology on the Local Maintenance Terminal. 33.5 Manually Switching over BTS Ring Topology This describes how to manually switch over the BTS ring topology on the Local Maintenance Terminal.
Issue 01 (2010-05-20)
33-1
33.1 Configuring BTS Ring Topology

This describes how to configure the BTS ring topology on the Local Maintenance Terminal. Scenario
At the sites with high traffic volume, a wide range of services are affected when the transmission links are disrupted. Thus, you are advised to deploy the ring topology. To improve the security and reliability of the chain topology in the multilevel cascading network, you are advised to deploy the ring topology. To facilitate the maintenance of the unstable transmission quality or the transmission at the sites in mountainous areas or isolated islands, you are advised to deploy the ring topology. At the sites in the areas with frequent earthquakes, the Abis transmission backup function is recommended. When the active SDH transmission link is faulty due to a natural disaster, the GBSS automatically switches the terrestrial TDM transmission link on the Abis interface to a backup satellite transmission link, thus maintaining the normal operation of the network. Ring topology I
Impact
If you switch over the BTS in ring topology I manually, the BTS is reset and the services of the BTS are affected. After link disconnection, the disconnected BTS is initialized and the services of the BTS are affected. The ring topology with Flex Abis enabled does not support the preemption of the lower-level PS secondary links. The Abis transmission backup function is license-controlled.
Ring topology II The switchover between the forward link and the reverse link of the BTS in ring topology (the time between the disconnection of the physical link and the restoration of the OML and the RSL) is less than eight seconds.
Prerequisite
l l l
The GXPUM, GXPUT, and GEIUB are configured on the GMPS or GEPS in the BSC. The BTS is configured. Ring topology I

The Abis over IP, OML backup, and HubBTS functions are not supported. The BTS ring topology with Flex Abis enabled has the following impact on other features: Flex Abis must be enabled in all the BTSs and only the forward and reverse single E1 link can be configured. The Abis bypass function is not supported. The 16 kbit/s LAPD signaling link is not supported. In satellite transmission mode, the services are disrupted in the case of switchover.
Ring topology II
33-2
l
The Abis over IP, OML backup, and HubBTS functions are not supported. The Flex Abis and Abis bypass functions are not supported. Only the forward and reverse single E1 link can be configured. In satellite transmission mode, the services are disrupted in the case of switchover. The HDLC-TDM hybrid networking and the connection of secondary links are not supported. The cabinets of the BTS30 or BTS312 cannot be used in cabinet groups. The configuration of exclusive timeslots is supported but the configuration of monitoring timeslots is not supported. The Flex Abis, Abis bypass, local switching, and 16 kbit/s LAPD signaling links are not supported. The conversion of the bearing modes is not supported, that is, the conversion from the HDLC ring topology to the TDM ring topology is not supported. In HDLC ring topology, timeslots cannot be manually allocated.
HDLC ring topology
Preparation
The following is an example of configuring a BTS3012 in TDM service mode. Table 33-1 Example of the data negotiated and planned for configuring BTS ring topology Parameter ID BTSNAME TYPE UPNODE SRN SN PN BTSDESC MPMODE FlexAbisMode Parameter Name BTS name BTS Type Up Node Type Subrack No. Slot No. Port No. BTS Description Multiplexing Mode Flex Abis Mode Example BTS3012 BTS3012 BSC 0 26 0 TDM BTS3012 MODE4_1 Fix Abis(Fix Abis) Source Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning
Issue 01 (2010-05-20)
33-3
Parameter ID AbisByPassMode ServiceMode DCELLNAME DCTYPE DCMCC DCMNC DCLAC DCCI CPLMode TRXBN FREQ REVCFGRING REVSN REVPN
Parameter Name Abis By Pass Mode Service Type Cell Name Cell Type Cell MCC Cell MNC Cell LAC Cell CI Separate Mode TRX Board No. TRX Freq. Ring Mode Rev ring slot No. Rev ring port No.
Example FALSE(Not Support) TDM TDMCELL GSM900 460 01 8240 1 UNSUPPORT(Not Support) 0 988 YES(Yes) 26 1
Source Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning
Procedure
Step 1 On the Local Maintenance Terminal, run the ADD BTS command to add a BTS. ----End
Example
An example script of configuring ring topology for the BTS3012 in TDM service mode is as follows:
/*Add an OPC*/ ADD OPC: NAME="1", OPC=h'aa, NETSTRUCT=BIT14, NI=NATB;
33-4
Issue 01 (2010-05-20)
/*Add a DPC*/ ADD N7DPC: NAME="2", DPC=h'cc, DPCGIDX=1, CNID=0; /*Add Subrack-OPC Mapping*/ ADD SROPCMAP: SRN=0, OPC=h'aa; /*Add a GXPUM*/ ADD BRD: SRN=0, SN=1, BT=GXPUM, BackType=OUTPEER; /*Add a GXPUT*/ ADD BRD: SRN=0, SN=2, BT=GXPUT, BackType=OUTPEER; /*Add a GEIUB*/ ADD BRD: SRN=0, SN=26, BT=GEIUB, WorkMode=E1, BackType=OUTPEER; /*Add a BTS3012 and configure BTS ring topology*/ ADD BTS: BTSNAME= "BTS3012", TYPE = BTS3012, UPNODE = BSC, SRN = 0, SN=26, PN=0, BTSDESC = "TDM BTS3012", MPMODE = MODE4_1, FlexAbisMode=FLEX_ABIS, AbisByPassMode=False, ServiceMode=TDM, DCELLNAME="TDMCELL", DCTYPE=GSM900, DCMCC="460", DCMNC="01", DCLAC=8240, DCCI=1, CPLMode=UNSUPPORT, TRXBN=0, FREQ=988, REVCFGRING=YES, REVSN=26, REVPN=1;
33.2 Changing Non-Ring Topology to Ring Topology

This describes how to change a BTS in non-ring topology to a BTS in ring topology on the Local Maintenance Terminal. Scenario
At the sites with high traffic volume, a wide range of services are affected when the transmission links are disrupted. Thus, you are advised to deploy the ring topology. To improve the security and reliability of the chain topology in the multilevel cascaded network, you are advised to deploy the ring topology. To facilitate the maintenance of the unstable transmission quality or the transmission at the sites in mountainous areas or isolated islands, you are advised to deploy the ring topology. At the sites in the areas with frequent earthquakes, the Abis transmission backup function is recommended. When the active SDH transmission link is faulty due to a natural disaster, the GBSS automatically switches the terrestrial TDM transmission link on the Abis interface to a backup satellite transmission link, thus maintaining the normal operation of the network.
Impact
Performing this operation leads to the resetting of the BTS.
Prerequisite
l l l
The GEIUB/GOIUB/GEHUB board is configured. The BTSs are configured in the non-ring topology mode. The BTSs must be in the chain topology, and port 1 of the upper-level BTS must be connected to port 0 of the lower-level BTS.
Issue 01 (2010-05-20)
33-5
Preparation
Table 33-2 Example of the data negotiated and planned for changing non-ring topology to ring topology Parameter ID CONFIGRING REVSN REVP Parameter Name Configure ring Reverse slot No. Reverse port No. Example YES(Yes) 26 1 Source Network planning Network planning Network planning
Procedure
Step 1 On the Local Maintenance Terminal, run the MOD BTSRINGATTR command. Set Configure ring to YES(Yes) and set the corresponding Reverse slot No. and Reverse port No.. ----End
Example
An example script of configuring ring topology for BTSs is as follows:
MOD BTSRINGATTR: IDXTYPE=BYNAME, STNAME="BTS3012", CONFIGRING=YES, REVSN=26, REVPN=1;
Postrequisite
To change a BTS in ring topology to a BTS in non-ring topology, enter the MOD BTSRINGATTR command on the Local Maintenance Terminal, and then set Configure ring to NO(No).
33.3 Querying BTS Ring Topology

This describes how to query the ring topology attributes of a BTS on the Local Maintenance Terminal. Scenario Impact Query the BTS ring topology. None.
Prerequisite
The BTS is configured.
Procedure
Step 1 On the Local Maintenance Terminal, run the LST BTSRINGATTR command to query the ring topology information of the BTS.
NOTE
Check whether the Configure ring, Reverse slot No., and Reverse port No. are consistent with the settings in the 33.2 Changing Non-Ring Topology to Ring Topology.
----End
Example
An example script of querying the ring topology attribute of a BTS is as follows:
LST BTSRINGATTR: IDXTYPE=BYNAME, BTSNAME="BTS3012";
33.4 Deleting a BTS from the Ring Topology

This describes how to delete a BTS from the ring topology on the Local Maintenance Terminal. Scenario Impact Besides saving transmission resources, the BTS ring topology improves the reliability of the system. For the impact of deleting a BTS from the ring topology on the system, see BSS Feature Description.
Prerequisite
The BTSs are configured in the ring topology mode.
Procedure
Step 1 On the Local Maintenance Terminal, run the MOD BTSACTSTAT command to modify the Active State to NOT_ACTIVATED(Not Activated). Step 2 On the Local Maintenance Terminal, run the RMV BTS command to delete a BTS from the ring topology.
NOTE
If the deleted BTS has lower-level BTSs, the lower-level BTSs are also deleted.
----End
Example
An example script of deleting a BTS3012 from the ring topology is as follows:
MOD BTSACTSTAT: IDXTYPE=BYNAME, BTSNAME="BTS3012", ACTSTAT=NOT_ACTIVATED; RMV BTS: IDXTYPE=BYNAME, BTSNAME="BTS3012";
Issue 01 (2010-05-20)
33-7
33.5 Manually Switching over BTS Ring Topology

This describes how to manually switch over the BTS ring topology on the Local Maintenance Terminal. Scenario After a link is broken, the BTS reverse link is set up and the transmission is restored. The BTS link cannot switch over to the forward direction automatically. The maintenance personnel, however, can forcibly switch over the link to the forward direction. When the transmission quality in the forward direction is poor, the maintenance personnel can manually switch over the link to the reverse direction. The manual switchover of BTS ring topology is critical to operation and maintenance. After the switchover, the BTS cannot work for a certain period. Thus, perform this operation with caution.
Impact

NOTE
When the switchover is performed manually from the forward link to the reverse link, start from the highest-level BTS in the reverse direction. After a BTS is successfully connected in the reverse direction and automatically initialized, perform the switchover on the next BTS. When the switchover is performed manually from the reverse link to the forward link, start from the highest-level BTS in the forward direction and then the other BTSs in sequence.
Prerequisite
l l
The BTSs are configured in ring topology mode. The transmission in the forward and reverse directions must work normally during manual switchover.
Procedure
Step 1 On the Local Maintenance Terminal, run the SWP BTSRING command. Set the port for link establishment after the switchover as required to manually switch over the ring topology direction of a BTS. ----End
Example
An example script of manually switching over the ring topology of a BTS3012 from forward direction to reverse direction is as follows:
SWP BTSRING: IDXTYPE=BYNAME, BTSNAME="BTS3012", OMLCPT=1;
33-8
Issue 01 (2010-05-20)
34 Configuring APS
34
Scenario Impact
Configuring APS
The automatic protection switching (APS) function applies to optical port backup. If a fault occurs on the working channel, the BSC negotiates with the optical transmission equipment on the protection channel through the APS to switch traffic signals onto the protection channel. APS can improve the stability and maintainability of the entire system. The APS configuration consists of configuring and verifying APS. The GOIUA, GOIUB, GOIUT, and GOIUP can be configured to support the APS function. When the BSC is connected to the optical transmission equipment and the working channel is faulty, the BSC negotiates with the optical transmission equipment on the protection channel through the APS to switch over the active OIUa and standby OIUa. Then the traffic signals are switched from the channel used to receive the data to the protection channel.
NEs Involved MSC, BSC, MGW, and SGSN

NOTE
l l l l l l l
In BM/TC separated and external PCU mode, APS can be configured on the GOIUA, GOIUB, GOIUT, and GOIUP. In BM/TC combined and external PCU mode, APS can be configured on the GOIUA, GOIUB, and GOIUP. In A over IP and external PCU mode, APS can be configured on the GOIUB and GOIUP. In BM/TC separated and built-in PCU mode, APS can be configured on the GOIUA, GOIUB, and GOIUT. In BM/TC combined and built-in PCU mode, APS can be configured on the GOIUA and GOIUB. In BM/TC separated mode, the APS function is supported by default and cannot be deactivated after the GOIUB/GOIUP/GOIUT is added. In BM/TC combined and A over IP mode, the APS function is supported by default and cannot be deactivated after the GOIUB/GOIUP/GOIUT is added.
Prerequisite
The principles of and requirements for configuring APS are as follows:
l
The APS attributes at the local and peer ends must be consistent. The default configuration is recommended for the BSC. If the configured APS attributes at the local and peer ends are inconsistent, you must modify the APS attributes.
Issue 01 (2010-05-20)
34 Configuring APS
l
The interconnected optical ports must be in the same mode. The optical port in SDH mode cannot interconnect with that in SONET mode. APS must be enabled at both ends. The optical fiber must be connected properly. The protection channel at the local end must be properly connected to that at the peer end. Otherwise, protocol switching cannot be performed. The protection modes at both ends must be consistent. The BSC supports only the 1+1 protection mode. The parameter settings at both ends must be consistent. For example, SWITCH_MODE and REVERT_MODE at both ends must be consistent. Otherwise, the protocol switching may be affected.
l l
Preparation
The following procedure takes the configuration of APS on the GOIUA in BM/TC separated and external PCU mode as an example. Table 34-1 Example of the data negotiated and planned for configuring APS Parameter ID SRN SN Parameter Name Subrack No. Slot No. Example 5 14 Source Network planning Network planning
Procedure
Step 1 On the Local Maintenance Terminal, run the ADD OIUAPS command to add the APS function. ----End
Example
In BM/TC separated mode, the GOIUA already exists. An example script is as follows:
/*Configure the APS function*/ ADD OIUAPS: SRN=5, SN=14;
Postrequisite
l
Verifying APS 1. On the Local Maintenance Terminal, run the SET APSCMD command. Set Subrack No. and Slot No. of the GOUIA whose APS needs to be verified. Then, set APS command to EXERS(Exercise switch). On the Local Maintenance Terminal, run the DSP APS command. Set Subrack No. and Slot No. of the GOIUA whose APS needs to be verified. If Switch Request is set to Forced Switch or Exercise Switch, and APS Status is set to SWITCH, it indicates that the APS function is configured successfully.
NOTE
2.
When verifying the APS, you are not advised to set APS Command to other switching modes.
34-2
Issue 01 (2010-05-20)
l
34 Configuring APS
Deactivating APS
On the Local Maintenance Terminal, run the RMV OIUAPS command to delete the APS function of the GOIUA.
NOTE
If you need to reconfigure the APS attributes, run the MOD OIUAPS command on the Local Maintenance Terminal.
Issue 01 (2010-05-20)
34-3
35 Configuring BSC Local Switching
35
Scenario Impact
Configuring BSC Local Switching
With this feature, if the calling MS and called MS are under the same BSC, the speech signals on the Abis interface are looped back to the MS without traveling around the NSS. In addition, in the BSC local switch, the speech coding schemes of the calling MS and called MS are the same and thus no coding conversion is required. Therefore, the TC resources involved in the BSC local switch can be released, and thus the speech quality is improved. BSC local switching is configured to save the transmission resources on the Ater interface. BSC local switching may decrease handover success rate or increase call drop rate. In addition, If the CN equipment is not provided by Huawei, the following functions are unavailable after the BTS local switch is enabled: lawful interception, MSC announcement, DTMF, fax during voice, and independent charging of the BTS local switch.
NEs Involved MSC, BSC, and BTS
Prerequisite
l l
The BSC local switching is license-controlled. The license is activated on the Local Maintenance Terminal. For details, see Activate BSC License. The SS7 signaling point of the BSC is already configured. For details, see Configuring Local Multiple Signaling Points. In A over IP mode, BSS local switching is not supported. In Abis over IP mode or Abis over HDLC mode, BSC local switching is not supported. In BM/TC combined mode, BSC local switching is not supported. The BTS local switching function has enabled before the BSC local switching function is activated.
l l l l
Issue 01 (2010-05-20)
35-1
Preparation
Table 35-1 Example of the data negotiated and planned for configuring BSC local switching Data Type DPC attributes Parameter ID IDXTYPE Parameter Name Index Type Example BYDPC(By DPC Code) Source Networ k plannin g Networ k plannin g Networ k plannin g Networ k plannin g Networ k plannin g Networ k plannin g Networ k plannin g
DPC
DPC Code
h'cc
BSSLSMSCCO OPSW
BSS Loop Switch MSC Cooperate
NOTSUPPORT (Not Support)
BSS local switching parameters
BssLsGenMode
BSS General Strategy
BSCONLY(BSC Only)
BscLsStartMode
Options for BSC Local Switch
ATERCONGEST S(Start When Ater Congests) 50
ATERJAMTHR ESHOLD2STAR TLS BSSBSCCLOSE
Start Ater Threshold for BSC
BSC Close Based on Number
NO(No)
Procedure
Step 1 On the Local Maintenance Terminal, run the MOD N7DPC command to configure the way of finishing BSS local switching. l l If the BSC performs BSS local switching independently, set BSS Loop Switch MSC Cooperate to NOTSUPPORT(Not Support). If the MSC cooperates with the BSC to perform BSS local switching, set BSS Loop Switch MSC Cooperate to BASIC(Basic) or ENHANCED(Enhanced) and set the related parameters on the MSC side to support the BSS local switching. When BSS Loop Switch MSC Cooperate is set to NOTSUPPORT(Not Support), the BSC independently performs BSC local switching.
35-2
When BSS Loop Switch MSC Cooperate is set to BASIC(Basic), either of the following cases may occur: If the MSC does not allow the BSS local switching, the MSC carries the indication information in the assignment request or incoming BSC handover request message and prohibits the BSC from enabling the local switching. In this case, the BSC cannot process the local switching. If the MSC allows the BSS local switching, the BSC determines whether to enable the local switching. In this case, the ongoing supplementary services are interrupted. When BSS Loop Switch MSC Cooperate is set to ENHANCED(Enhanced), either of the following cases may occur: If the MSC does not allow the BSS local switching, the MSC carries the indication information in the assignment request or incoming BSC handover request message and prohibits the BSC from enabling the local switching. In this case, the BSC cannot process the local switching. If the MSC allows the BSS local switching, the BSC determines whether to enable the local switching. In this case, the calls involved in the local switching are restored to normal calls so that the supplementary services can be processed normally.
Step 2 On the Local Maintenance Terminal, run the MOD BSSLS command to set BSS General Strategy to BSCPRIORITY(BSC Priority) or BSCONLY(BSC Only) and set Options for BSC Local Switch] and BSC Close Based on Number. l l l If Options for BSC Local Switch is set to ATERCONGESTS(Start When Ater Congests), you should set Start Ater Threshold for BSC. If Options for BSC Local Switch is set to PREFIXNUMBER(Start by Prefix Number), you should set Prefix Number for BSC. If BSC Close Based on Number is set to Yes(Yes), you should set the Avoid Number for BSC .
----End
Example
An example script for configuring BSC local switching is as follows:
/*Set "BSS Loop Switch MSC Cooperate"*/ MOD N7DPC: IDXTYPE=BYDPC, DPC=h'cc, BSSLSMSCCOOPSW=CLOSE; /*Configure the parameters related to BSC local switching on the BSC*/ MOD BSSLS: BssLsGenMode=BSCONLY, BscLsStartMode=ATERCONGESTS, BssBscClose=NO, AterJamThreshold2StartLs=50;
Postrequisite
l
Verifying BSC local switching
On the Local Maintenance Terminal, run the DSP CALLRES command to query the call resources of an MS.
NOTE
If BSC local switching is started successfully, Ater Interface Information and TC Resource Information is not shown in the result.
l
Deactivating BSC local switching 1. 2. On the Local Maintenance Terminal, run the MOD BSSLS command to set BSS General Strategy to NEITHERSTART(Neither Start). The operations for verifying deactivation of BSC local switching are the same as those for verifying BSC local switching. Verify that the information about the Ater interface and TC resources are included in the query result.
Issue 01 (2010-05-20)
36 Configuring BTS Local Switching
36
Scenario Impact
Configuring BTS Local Switching
With this feature, if the calling MS and called MS are within the coverage of the same BTS or BTS group, the BSC performs the loopback on the cabinet group of the convergent BTS. BTS local switching can save the transmission resources on the Abis and Ater interfaces and reduce the TC processing delay during the call. If the CN equipment is not provided by Huawei, the following functions are unavailable after the BTS local switch is enabled: lawful interception, MSC announcement, DTMF, fax during voice, and independent charging of the BTS local switch.
NEs Involved BTS
Prerequisite
l
BTS local switching is not restricted by the license. If the BTS local switching is enabled in the network, in addition to the license of the BTS local switching, the license of the BSC local switching is required. The license is activated through the Local Maintenance Terminal. For details, see Activate BSC License. The SS7 signaling point on the BSC is already configured. For details, see Configuring Local Multiple Signaling Points. In Abis over TDM, the BTS local switching can be enabled after Flex Abis is enabled (Flex Abis is license-controlled). In Abis over HDLC, the BTS local switching is not supported. In Abis over IP, the BTS local switching can be enabled on the lower-level BTSs only. If IP transmission mode is adopted on the A interface, the BTS local switching is not supported. At the sites with hybrid BTS cabinet groups, the BSS local switching can be enabled only when both the BTS software and the TRX software support BSS local switching. The BTS local switching and BTS ring topology cannot be enabled at the same time for one BTS.
Preparation
Take the configuration of BTS3012 in TDM transmission mode as an example.
Table 36-1 Example of the data negotiated and planned for adding a BTS Data Type BTS basic attributes Parameter ID BTSNAME TYPE UPNODE SRN SN PN BTSDESC MPMODE FlexAbisMode AbisByPassMode ServiceMode DCELLNAME DCTYPE DCMCC DCMNC DCLAC DCCI CPLMode Parameter Name BTS Name BTS Type Up Node Type Subrack No. Slot No. Port No. BTS Description Multiplexing Mode Flex Abis Mode Abis By Pass Mode Service Type Cell Name Cell type Cell MCC Cell MNC Cell LAC Cell CI Separate Mode Example BTS3012 BTS3012 BSC 0 10 0 TDM BTS3012 MODE4_1 FLEX_ABIS (Flex Abis) FALSE(Not Support) TDM TDMCELL GSM900 460 34 62 98 UNSUPPORT (Not Support) Source Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning
36-2
Issue 01 (2010-05-20)
Data Type
Parameter ID TRXBN FREQ
Parameter Name TRX Board No. TRX Freq.
Example 0 5
Table 36-2 Example of the data negotiated and planned for configuring BTS local switching Data Type BTS local switching parameters Parameter ID IDXTYPE BTSIDX IsSupportBTSLSwitch BSSLSGENMOD E BTSLSSTARTM ODE BSSBTSCLOSE ABISJAMTHRE SHOLD2START LS Parameter Name Index Type BTS Index Support BTS Local Switch BSS General Strategy Options for BTS Local Switch BTS Close Based on Number Start Abis Threshold for BTS Example BYIDX(By Index) 0 SUPPORT (Yes) BTSONLY (BTS Only) ABISCONGES TS(Start When Abis Congests) NO(No) 50 Source Network planning Network planning Network planning Network planning Network planning Network planning Network planning
Procedure
Step 1 On the Local Maintenance Terminal, run the ADD BTS command to set Flex Abis Mode to FLEX_ABIS(Flex Abis).
NOTE
If a BTS is already configured, enter the MOD FLEXABIS command on the Local Maintenance Terminal and then set Flex Abis Mode to FLEX_ABIS(Flex Abis) to configure the Flex Abis for the BTS. For details, see Configuring Flex Abis.
Step 2 On the Local Maintenance Terminal, run the MOD BTSLSW command to set Support BTS Local Switch to SUPPORT(Yes). Step 3 On the Local Maintenance Terminal, run the MOD N7DPC command to configure the way of finishing BSS local switching.
l l
When BSS Loop Switch MSC Cooperate is set to NOTSUPPORT(Not Support), the BSC independently performs BSC local switching. When BSS Loop Switch MSC Cooperate is set to BASIC(Basic), either of the following cases may occur: If the MSC does not allow the BSS local switching, the MSC carries the indication information in the assignment request or incoming BSC handover request message and prohibits the BSC from enabling the local switching. In this case, the BSC cannot process the local switching. If the MSC allows the BSS local switching, the BSC determines whether to enable the local switching. In this case, the ongoing supplementary services are interrupted. When BSS Loop Switch MSC Cooperate is set to ENHANCED(Enhanced), either of the following cases may occur: If the MSC does not allow the BSS local switching, the MSC carries the indication information in the assignment request or incoming BSC handover request message and prohibits the BSC from enabling the local switching. In this case, the BSC cannot process the local switching. If the MSC allows the BSS local switching, the BSC determines whether to enable the local switching. In this case, the calls involved in the local switching are restored to normal calls so that the supplementary services can be processed normally.
Step 4 On the Local Maintenance Terminal, run the MOD BSSLS command to set BSS General Strategy to BTSPRIORITY(BTS Priority) or BTSONLY(BTS Only) and set Options for BTS Local Switchand BTS Close Based on Number. l l l If Options for BTS Local Switch is set to ABISCONGESTS(Start When Abis Congests), you should set Start Abis Threshold for BTS. If Options for BTS Local Switch is set to PREFIXNUMBER(Start by Prefix Number), you should set Prefix Number for BTS. If BTS Close Based on Number is set to Yes(Yes), you should set the Avoid Number for BTS .
NOTE
For BTSs in IP transmission mode, it is impossible to set Options for BTS Local Switch.
----End
Example
An example script for configuring BTS local switching is as follows:
/*Add an OPC*/ ADD OPC: NAME="1", OPC=h'aa, NETSTRUCT=BIT14, NI=NATB; /*Add a DPC*/ ADD N7DPC: NAME="2", DPC=h'cc, DPCGIDX=1, CNID=0; /*Configure subrack-OPC mapping*/ ADD SROPCMAP: SRN=0, OPC=h'aa; /*Add a GXPUM*/ ADD BRD: SRN=0, SN=1, BT=GXPUM, BackType=OUTPEER; /*Add a GEIUB*/ ADD BRD: SRN=0, SN=10, BT=GEIUB, WorkMode=E1, BackType=OUTPEER; /*Add a BTS3012*/ ADD BTS: BTSNAME = "BTS3012", TYPE = BTS3012, UPNODE = BSC, SRN = 0, SN=10, PN = 0, BTSDESC = "TDM BTS3012", MPMODE = MODE4_1, FlexAbisMode = FLEX_ABIS, AbisByPassMode = False, ServiceMode = TDM, DCELLNAME = "TDMCELL", DCTYPE = GSM900, DCMCC = "460", DCMNC = "34", DCLAC = 62, DCCI = 98, CPLMode = UNSUPPORT, TRXBN = 0, FREQ = 5; /*Set "BSS Loop Switch MSC Cooperate"*/ MOD N7DPC: IDXTYPE=BYDPC, DPC=h'cc, BSSLSMSCCOOPSW=CLOSE; /*Configure BTS local switching*/ MOD BTSLSW: IDXTYPE=BYIDX, BTSIDX=0, IsSupportBTSLSwitch = SUPPORT;
36-4
Issue 01 (2010-05-20)
/*Configure the parameters related to BTS local switching on the BSC*/ MOD BSSLS: BssLsGenMode=BTSONLY, BtsLsStartMode=ABISCONGESTS, BssBtsClose=NO, AbisJamThreshold2StartLs=50;
Postrequisite
l
Verifying BTS local switching 1. 2. Set up a call between two MSs under the same BTS. On the Local Maintenance Terminal, run the DSP CALLRES command to query the call resources of an MS.
NOTE
If the information about the Ater interface and Abis interface is not contained in the query result, it indicates that the BTS local switching function is enabled successfully.
l
Deactivating BTS local switching 1. 2. On the Local Maintenance Terminal, run the MOD BTSLSW command to set Support BTS Local Switch to NOTSUPPORT(Not Support). The operations for verifying deactivation of BTS local switching are the same as those for Verifying BTS local switching. Verify that the information about the Ater interface and Abis interface are included in the query result.
Issue 01 (2010-05-20)
36-5
37 Configuring Dynamic MAIO
37
About This Chapter
Configuring Dynamic MAIO
Under the BTSs with large capacity, adjacent-channel or co-channel interference are likely to occur among channels because the frequency resources are insufficient and the tight frequency reuse is adopted.With the dynamic MAIO, when an MAIO is assigned to a channel under activation, the MAIO value is dynamically adjusted according to the current interference and the MAIO value with the minimum interference is assigned to the channel,reduces the adjacentchannel and co-channel interference in the GSM system. 37.1 Precautions for Configuring Dynamic MAIO This provides the precautions for configuring dynamic MAIO. In different scenarios, the requirements for the FH data configuration of the BTS are different. 37.2 Configuring Dynamic MAIO This describes how to configure dynamic MAIO on the Local Maintenance Terminal.
Issue 01 (2010-05-20)
37-1
37.1 Precautions for Configuring Dynamic MAIO

This provides the precautions for configuring dynamic MAIO. In different scenarios, the requirements for the FH data configuration of the BTS are different. The requirements for configuring dynamic MAIO are as follows:
l l l l l l
Each cell can be configured with up to two different MAs. The length of MA used by the same timeslot in a BTS must be the same. The channels in the same timeslot in a cell must use the same MA during FH. No cell in the BTS is configured with frame offset. The value of Flex MAIO Switch must be the same for the cells in the same BTS. Dynamic MAIO cannot be configured for the double-timeslot extension cell.
For better performance of the dynamic MAIO algorithm, the FH data configuration of the BTS must meet the following requirements:
l
1x1 frequency reuse with BCCH frequencies not joining in FH
All the FH channels in the BTS use the same MA and HSN. All the channels on timeslot 0 in the BTS use one set of FH data {MA0, HSN0}. All the other timeslots use another set of FH data {MA1, HSN1}. The FH data used by the cells in the BTS is different, but the number of frequencies in all MAs and the HSN are the same. Adjacent frequencies exist not in MAs but between the MAs. The FH data used by all the FH channels in the cell is the same. The FH data used by the cells in the BTS is different, but the number of frequencies in all MAs on the same timeslot and the HSN are the same. Adjacent frequencies exist not in MAs but between the MAs. The MA used by timeslot 0 in the cell is different from the MA used by other timeslots. The FH data used by other timeslots is the same.
1x1 frequency reuse with BCCH frequencies joining in FH
1x3 frequency reuse with BCCH frequencies not joining in FH
1x3 frequency reuse with BCCH frequencies joining in FH
37.2 Configuring Dynamic MAIO

This describes how to configure dynamic MAIO on the Local Maintenance Terminal. Scenario Reduces the adjacent-channel and co-channel interference in the GSM system, achieves the tight frequency reuse within the BTSs and thus improves the system capacity. None
Impact
37-2
Issue 01 (2010-05-20)
Prerequisite
l
During baseband frequency hopping, dynamic MAIO assignment is not supported. Only the function of selecting a channel with the least interference is supported. Only the CS services support dynamic MAIO assignment. The PS services do not support dynamic MAIO assignment.
Preparation
Table 37-1 Example of the data negotiated and planned for configuring dynamic MAIO Parameter ID IDXTYPE CELLIDX FLEXMAIO HSNSW Parameter Name Index Type Cell Index Flex MAIO Switch Flex HSN Switch Example BYIDX(By Index) 0 OPEN(Open) OPEN(Open) Source Network planning Network planning Network planning Network planning
Procedure
Step 1 On the Local Maintenance Terminal, run the MOD CELLFLEXMAIO command to set Flex MAIO Switch and Flex HSN Switch to OPEN(Open). Step 2 On the Local Maintenance Terminal, configure the cell to be an FH cell. For details, see 8 Configuring Frequency Hopping.
NOTE
Dynamic MAIO cannot be configured for the PS services.
----End
Example
An example script for configuring dynamic MAIO is as follows:
/*Modify the channel management parameters related to Flex MAIO*/ MOD CELLFLEXMAIO: IDXTYPE=BYIDX, CELLIDX=0, FLEXMAIO=OPEN, HSNSW=OPEN;
Postrequisite
l
Verifying dynamic MAIO 1. On the Local Maintenance Terminal, run the DSP CALLRES command to query the call resources occupied by a specified MS, including the setting of the parameters TRX No. and Channel No..
Issue 01 (2010-05-20)

NOTE
The dynamic MAIO message of the MS can be traced only when the call is set up and the MS occupies the TCH on the non-BCCH TRX.
2.
On the Local Maintenance Terminal, run the DSP BTSATTR command to query MAIO according to the obtained values of TRX No. and Channel No.. Then, record the query result. Repeat Step 2. If MAIO shown in the query result constantly changes, it indicates that dynamic MAIO is already enabled. Otherwise, dynamic MAIO is not enabled. On the Local Maintenance Terminal, run the MOD CELLFLEXMAIO command to set Flex MAIO Switch to CLOSE(Close). On the Local Maintenance Terminal, run the LST CELLFLEXMAIO command. If Flex MAIO Switch is set to Close, it indicates that dynamic MAIO is deactivated.
3.
l
Deactivating dynamic MAIO 1. 2.
37-4
Issue 01 (2010-05-20)
38 Configuring Antenna Hopping
38
Scenario Impact
Configuring Antenna Hopping
This describes how to configure antenna hopping. With antenna hopping, the downlink data on each TRX can be randomly transmitted on other TRXs. This optimizes the data reception of the MS from the main BCCH TRX and the data transmission of the main BCCH TRX, thus improving network performance. Antenna hopping is configured to optimize the data reception of the MS from the main BCCH TRX and the data transmission of the main BCCH TRX, thus improving network performance. None

NOTE
A cell can be configured with multiple antenna hopping groups. When a TRX in an antenna hopping group is faulty, antenna hopping is disabled in the antenna hopping group upon the automatic notification from the BSC. If the faulty TRX recovers, antenna hopping in the antenna hopping group is enabled again. When baseband frequency hopping and antenna hopping are applied at the same time, adhere to the following principles:
l l
When baseband FH (or hybrid FH) is configured, antenna hopping group must share the same TRX with baseband MA group. One TRX must belong to the baseband MA group and the antenna hopping group with the same group number.
Prerequisite
l l l
Antenna hopping is not restricted by the license. The BTS must be a double-transceiver BTS. There are at least two TRXs in an antenna hopping group.
Issue 01 (2010-05-20)
38-1
Preparation
Table 38-1 Example of the data negotiated and planned for configuring antenna hopping Parameter ID IDXTYPE CELLIDX HOPTRXHSN TRX1BN TRX1PN TRX2BN TRX2PN Parameter Name Index Type Cell Index Hop Trx Group Hsn No.1 TRX Board No. No.1 TRX Board Pass No. No.2 TRX Board No. No.2 TRX Board Pass No. Example BYIDX 0 0 0 0 0 1 Source Network planning Network planning Network planning Network planning Network planning Network planning Network planning
Procedure
Step 1 On the Local Maintenance Terminal, run the ADD CELLHOPANTGRP command to configure antenna hopping.
NOTE
At least two TRXs should be configured in an antenna hopping group. Do not set HSN to 0 because this leads to low quality of interference source diversity. If you use multi-transceiver TRX board, specify the path number of the TRX board.
----End
Example
An example script for configuring antenna hopping is as follows:
ADD CELLHOPANTGRP: IDXTYPE=BYIDX, CELLIDX=0, HOPTRXHSN=0, TRX1BN=0, TRX1PN=0, TRX2BN=0, TRX2PN=1;
Postrequisite
l
Verifying antenna hopping
On the Local Maintenance Terminal, run the LST CELLHOPANT command to view the setting of Cell Hop Ant. If the parameter is set to Yes, it indicates that antenna hopping is activated.
Deactivating antenna hopping
38-2
Issue 01 (2010-05-20)
On the Local Maintenance Terminal, run the RMV CELLHOPANTGRP command to delete the antenna hopping group.
Issue 01 (2010-05-20)
38-3
39 Configuring Voice Quality Index
39
Scenario Impact
Configuring Voice Quality Index
The voice quality index (VQI) feature provides a direct method to measure the voice quality of the radio network. By measuring the uplink VQI and downlink VQI, the voice quality of the network is quantified, which provides a reference for future network optimization. VQI is configured to monitor the voice quality. None
Prerequisite
l l
The cell is already configured. The EMR feature should be supported by the MS.
Preparation
Table 39-1 Example of the data negotiated and planned for configuring VQI Parameter ID IDXTYPE CELLIDX RPTVOICE Parameter Name Index Type Cell Index Voice quality report switch Example BYIDX(By Index) 0 YES(Report) Source Network planning Network planning Network planning
Procedure
Step 1 On the Local Maintenance Terminal, run the MOD CELLOTHBASIC command to set Cell Name or Cell Index, and set Voice quality report switch. ----End
Example
An example script for configuring VQI is as follows:
MOD CELLOTHBASIC: IDXTYPE=BYIDX, CELLIDX=0, RPTVOICE=YES;
Postrequisite
l
Verifying voice quality index 1. On the Trace&Monitor tab page of the BSC6000 Local Maintenance Terminal, choose Trace > Trace CS Message > Trace User Message. A dialog box is displayed, as shown in Figure 39-1. Set the parameters under Interface Type, Tracing Mode, and Color. Then, select and enter the IMSI, TMSI, MSISDN, IMEI, or Channel of the user to be traced. Figure 39-1 Trace User Message dialog box
2.
Click OK to start tracing. The result is displayed, as shown in Figure 39-2.
39-2
Issue 01 (2010-05-20)
Figure 39-2 Result of the user message tracing
3.
Double-click Preprocessed Measurement Result (if the preprocessed measurement result function is not enabled, double-click Measurement Result). A dialog box is displayed, as shown in Figure 39-3.
Issue 01 (2010-05-20)
39-3
Figure 39-3 Message Browser window
According to the result shown in Figure 39-3, if the tlv-type-vqi field exists, you can infer that the BTS reports the VQI information.
NOTE
When the VQI function is enabled, the BTS reports the VQI information once every five measurement report periods. That is, the tlv-type-vqi field exists in the Preprocessed Measurement Result or Measurement Result once every five measurement report periods.
l
Deactivating VQI 1. On the Local Maintenance Terminal, run the MOD CELLOTHBASIC command to set Cell Name or Cell Index of the target cell. Then, set Voice quality report switch to NO(Not report). Verifying the deactivation of VQI: The operations are the same as those for verifying the VQI function. Verify that the tlv-type-vqi field does not exist.
2.
39-4
Issue 01 (2010-05-20)
40 Configuring ANR
40
Scenario Impact NEs Involved BSC
Configuring ANR
Automatic noise restraint (ANR) reduces the background noise in the uplink speech signals and improves the signal noise ratio (SNR) and speech intelligibility. Thus, the speech signals are received clearly at the peer end. ANR is configured to reduce the background noise in the uplink speech signals and improve the SNR and speech intelligibility. Thus, the speech signals are received clearly at the peer end. ANR can improve the voice quality when background noise exists.
Prerequisite
l l
The GDPUC or GDPUX is already configured. ANR and TFO cannot be enabled at the same time.
Preparation
Table 40-1 Example of the data negotiated and planned for configuring ANR Parameter ID SRN SN ANRSWITH Parameter Name Subrack No. Slot No. ANR Switch Example 5 0 OPEN(Open) Source Network planning Network planning Network planning
Procedure
Step 1 On the Local Maintenance Terminal, run the MOD DSPTC command to set ANR Switch to OPEN(Open).
Issue 01 (2010-05-20)
40-1
40 Configuring ANR
NOTE
l l l l
If you do not set DSP No., all the DSP TC objects are configured. ANR Mode can be set to only MODE0(Mode 0) at present. Other values are invalid and reserved. ANR Noise Target Level [dB] can be set to only the default value -48dB. Other values are invalid and reserved. ANR Noise Reduction Level[dB] determines the extent to which the noise can be restrained. The greater the value is, the greater the noise can be restrained.
----End
Example
An example script for configuring ANR is as follows:
/*Configure ANR*/ MOD DSPTC: SRN=5, SN=0, ANRSWITH=OPEN;
Postrequisite
l
Verifying ANR 1. 2. 3. 4. 5. On the Local Maintenance Terminal, run the MOD DSPTC command to set ANR Switch to CLOSE(Close). In the same cell, use MS 1 to call MS 2 with a normal voice in a noisy environment. In this case, when you hear loud background noise, hang up the phone. On the Local Maintenance Terminal, run the MOD DSPTC command to set ANR Switch to OPEN(Open). On the Local Maintenance Terminal, run the LST DSPTC command to verify that ANR Switch is set to OPEN(Open). Use MS 1 to call MS 2 again with a normal voice. The volume of the background noise decreases. It indicates that ANR is activated. On the Local Maintenance Terminal, run the MOD DSPTC command to set ANR Switch to CLOSE(Close). On the Local Maintenance Terminal, run the LST DSPTC command. If ANR Switch is set to Close, it indicates that ANR is deactivated.
Deactivating ANR 1. 2.
40-2
Issue 01 (2010-05-20)
41 Intelligent Power Consumption Decrease
41
Intelligent Power Consumption Decrease
About This Chapter

This describes how to decrease the power consumption of various BTS parts through the use of a technology to decrease the overall BTS power consumption. The technologies used for intelligent power consumption decrease are as follows: TRX Power Amplifier Intelligent Shutdown, Timeslot-level Shutdown of the Power Amplifier, Intelligent Combiner Bypass, PSU Smart Control, Power Optimization Based on Channel Type, Enhanced BCCH Power Consumption Optimization, Active Backup Power Control, Multi-Carrier Intelligent Voltage Regulation and TRX Working Voltage Adjustment. The technologies such as channel assignment algorithm, DTX, and power control also help to decrease the power consumption. 41.1 Configuring TRX Power Amplifier Intelligent Shutdown When TRX power amplifier intelligent shutdown is enabled, only some TRXs carry the traffic in a cell, and the power amplifiers of the TRXs not carrying traffic are shut down. That is, the power amplifiers of the TRXs whose dynamic power consumption is zero are shut down. Thus, the BTS power consumption is reduced. 41.2 Configuring Intelligent Combiner Bypass This describes how to configure the intelligent combiner bypass (ICB). ICB is applicable to the dual-transceiver unit. ICB is aimed at decreasing the BTS power consumption when the traffic load is light. In ICB, the carrier of channel B is shut down in idle hours and the carrier of channel A is configured to work in PBT mode. In addition, the voltage of both channels is decreased to reduce the power consumption. You can enable the TRX to work in ICB mode through configuration. 41.3 Configuring PSU Smart Control This describes how to configure the PSU smart control. In the PSU smart control, only the required PSUs are switched on and the redundant PSUs are shut down to improve the efficiency of power conversion, thus reducing the power consumption and prolonging the operation time and lifetime of the PSU. 41.4 Configuring Power Optimization Based on Channel Type This describes how to configure the power optimization based on channel type, which is also called dynamic voltage adjustment. In the power optimization based on channel type, different
working voltages are applied to the TRX power amplifier on the basis of the modulation modes of the channels to reduce the BTS power consumption. 41.5 Configuring Enhanced BCCH Power Consumption Optimization This describes how to configure the enhanced BCCH power consumption optimization. The enhanced BCCH power consumption optimization reduces the BTS power consumption in idle hours by reducing the power of non-BCCHs on the BCCH TRX, thus reducing the OPEX of the operators. The time segment and degree of the power reduction are configurable. 41.6 Configuring Active Backup Power Control This describes how to configure the active backup power control. The BTS uses the configured battery for power supply when the mains failure occurs. The battery provides a limited capacity. To prolong the power supply time of the battery, the BSC shuts down certain TRXs or reduces the maximum transmit power of the TRX to reduce the BTS power consumption. This is called active backup power control. 41.7 Configuring Multi-Carrier Intelligent Voltage Regulation This feature monitors the output power of all the carriers within the module. When the total output power of the power amplifier reduces after the measurement for a period, this feature adjusts the working voltage of the power amplifier to a lower value according to the related algorithm. In this way, the power amplifier works with great efficiency after the output power reduces, thus reducing the power consumption of the TRX. 41.8 Configuring TRX Working Voltage Adjustment The working voltage of the TRX is always set to a high level to ensure the maximum output power of the TRX. In actual application, however, the maximum output power of the TRX is not always required. In this case, if the TRX still works under such a high voltage, extra power is consumed because a lower working voltage can also provide the required output power. To reduce the power consumption of the TRX, Huawei developed the function of "TRX Working Voltage Adjustment" that enables the intelligent adjustment of the TRX working voltage according to the output power.
41-2
Issue 01 (2010-05-20)
41.1 Configuring TRX Power Amplifier Intelligent Shutdown

When TRX power amplifier intelligent shutdown is enabled, only some TRXs carry the traffic in a cell, and the power amplifiers of the TRXs not carrying traffic are shut down. That is, the power amplifiers of the TRXs whose dynamic power consumption is zero are shut down. Thus, the BTS power consumption is reduced. Scenario
For the BTS main equipment that does not process services, the dormant mode is started to reduce the power consumption. If the BTS main equipment works normally and processes services, you can enable intelligent power consumption reduction without affecting the services.
Impact
None
Prerequisite
l l
Intelligent shutdown of the TRX is restricted by the license. Activate the license on the Local Maintenance Terminal. For details, see Activate BSC License. When the BSC enables intelligent shutdown of the TRX, the BTS checks only the CS services. Before configuring Dynamic Close TRX Ampier Power switch on the TRX, ensure that the TRX meets the following requirements:

The TRX must be the TRX where the non-BCCH is located. The PDCH does not exist. Antenna hopping is disabled.
When the main BCCH participates in baseband FH, the function of intelligent shutdown of TRXs is not supported. When basband FH is enabled but the main BCCH does not participate in baseband FH, the TRXs can be shut down only when all the TRXs in the cell (except the main BCCH TRXs) are idle.
NOTE
During a BTS deployment test, you need to set the parameter Dynamic Open Trx AmpierPower Switch to NO(No) by running the MOD CELLBASICPARA command.
Issue 01 (2010-05-20)
41-3
Preparation
Table 41-1 Example of the data negotiated and planned for configuring intelligent power consumption reduction Data Type Intelligent shutdown of the TRX Parameter ID BSCDynSwitchTr xPAAllow Parameter Name Allow Dynamic Shutdown of TRX Power Amplifier by BSC Index Type Cell Index Dynamic Open Trx AmpierPower Switch Base Hop Support Close TRX Allowed TRX Board No. TRX Board Path No. TRX Priority Dynamic Close TRX Ampier Power switch Time Slot Turning Off PA Enable Example YES(Yes) Source Network planning
IDXTYPE CELLIDX DYNOpenTrxPo wer BASEHOPCLOS ETRXALLOWE D TRXBN TRXPN OPTL CPS
BYIDX(By Index) 0 YES(Yes)
Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning
YES(Yes)
0 0 L7(Level7) YES(Yes)
TsTurningOffEna ble
YES(Yes)
Procedure
l Configure intelligent shutdown of the TRX. 1. 2. 3. On the Local Maintenance Terminal, run the MOD BSCDSTPA command to set Allow Dynamic Shutdown of TRX Power Amplifier by BSC to YES(Yes). On the Local Maintenance Terminal, run the MOD CELLBASICPARA command to set Dynamic Open Trx AmpierPower Switch to YES(Yes). On the Local Maintenance Terminal, run the SET CELLSOFT command to set Base Hop Support Close TRX Allowed to YES(YES).
41-4
Issue 01 (2010-05-20)
NOTE
Before configuring Dynamic Close TRX Ampier Power switch, ensure that Base Hop Support Close TRX Allowed is set to YES(YES) if the baseband FH is allowed in the cell.
4. 5.
On the Local Maintenance Terminal, run the MOD TRXDEV command to set Dynamic Close TRX Ampier Power switch to YES(YES). (Optional) On some special days such as holidays, the traffic volume surges. In such a case, do not shut down the power amplifiers of the TRX modules. Do as follows: (1) On the Local Maintenance Terminal, run the ADD BSCDSTPADATE command to set the period of prohibiting intelligent shutdown of the TRX. You can set up to 12 periods. (2) Run the MOD BSCDSTPA command to set the time when intelligent shutdown of the TRX is enabled and disabled. To query the parameter Prohibiting Dynamic Shutdown of TRX Power Amplifier Date Range, run the LST BSCDSTPA command.
6.
(Optional) On the Local Maintenance Terminal, run the RMV BSCDSTPADATE command to delete the period of prohibiting intelligent shutdown of the TRX. On the Local Maintenance Terminal, run the MOD CELLBASICPARA command to set Adjust Voltage to YES(YES).
NOTE
Configure dynamic voltage adjustment. 1.
The TRX power amplifier intelligent shutdown on timeslot level can be controlled by Time Slot Turning Off PA Enable. This function is license-controlled. The TRXs supporting the timeslot-level intelligent shutdown of the power amplifier function are DRFU, DRRU, and optimized DTRU.
----End
Example
An example script for configuring intelligent shutdown of the TRX is as follows:
/*Modify the parameters related to intelligent shutdown of the TRX*/ MOD BSCDSTPA: BSCDynSwitchTrxPAAllow=YES, StartTimeTACloseTrxPA=00&00, EndTimeTACloseTrxPA=08&00, StartMonthDSTPA=JAN, StartDayDSTPA=1, EndMonthDSTPA=JAN, EndDayDSTPA=28, TsTurningOffEnable=NO; /*Set "Dynamic Open Trx AmpierPower Switch"*/ MOD CELLBASICPARA: IDXTYPE=BYIDX, CELLIDX=0, DYNOpenTrxPower=YES, BTSadjust=YES; /*Set "Base Hop Support Close TRX Allowed"*/ SET CELLSOFT: IDXTYPE=BYIDX, CELLIDX=0, BASEHOPCLOSETRXALLOWED=YES; /*Set "Dynamic Close TRX Ampier Power switch"*/ MOD TRXDEV: IDXTYPE=BYIDX, CELLIDX=0, TRXBN=0, TRXPN=0, OPTL=L7, CPS=YES; /*Add the period of prohibiting intelligent shutdown of the TRX*/ ADD BSCDSTPADATE: BSCDynSwitchTrxPAAllow=YES, StartMonthDSTPA=FEB, StartDayDSTPA=1, EndMonthDSTPA=FEB, EndDayDSTPA=28; /*Delete the period of prohibiting intelligent shutdown of the TRX*/ RMV BSCDSTPADATE: BSCDynSwitchTrxPAAllow=YES, DateRangeIndex=1;
An example script for configuring dynamic voltage adjustment is as follows:

/*Set "Adjust Voltage"*/ MOD CELLBASICPARA: IDXTYPE=BYIDX, CELLIDX=0, BTSadjust=YES;
Issue 01 (2010-05-20)
41-5
Postrequisite
l
TRX power amplifier intelligent shutdown
Deactivating TRX power amplifier intelligent shutdown 1. On the Local Maintenance Terminal, run the MOD BSCDSTPA command to set Allow Dynamic Shutdown of TRX Power Amplifier by BSC to NO(No).
Time slot turning off PA enable
Verifying time slot turning off PA enable
On the Local Maintenance Terminal, run the LST BSCDSTPA command to query the setting of the parameter Time Slot Turning Off PA Enable. If the parameter is set to Yes, it indicates that the function of timeslot turning off PA is activated.
Deactivating time slot turning off PA enable 1. 2. On the Local Maintenance Terminal, run the MOD BSCDSTPA command to set Time Slot Turning Off PA Enable to NO(NO). On the Local Maintenance Terminal, run the LST BSCDSTPA command to query the setting of the parameter Time Slot Turning Off PA Enable. If the parameter is set to No, it indicates that the function of timeslot turning off PA is deactivated.
41.2 Configuring Intelligent Combiner Bypass

This describes how to configure the intelligent combiner bypass (ICB). ICB is applicable to the dual-transceiver unit. ICB is aimed at decreasing the BTS power consumption when the traffic load is light. In ICB, the carrier of channel B is shut down in idle hours and the carrier of channel A is configured to work in PBT mode. In addition, the voltage of both channels is decreased to reduce the power consumption. You can enable the TRX to work in ICB mode through configuration. Scenario Impact The function of intelligent combiner bypass reduces the power consumption of the idle TRX that is on the same dual-transceiver unit as the BCCH TRX. When the TRX other than the BCCH TRX is idle, the dual-transceiver unit that houses the BCCH TRX starts working in ICB mode and the capacity of the dualtransceiver unit decreases to one TRX. If the minimum working voltage is applied to the TRX, the output power of the single power amplifier of the TRX is decreased to 15 W or 10 W. After the power burst technology (PBT) is enabled on a TRX, the cabinet-top power of the TRX is the same as the cabinet-top power provided when the single power amplifier transmits at 60 W or 40 W.
NEs Involved
Prerequisite
l l l
The intelligent combiner bypass function is not license-controlled. The cell attribute parameter Allow Dynamic Voltage Adjustment is set to Yes. All the non-BCCH TRXs on the double-transceiver unit where the BCCH TRX is located are idle. In addition, the BCCH TRX and non-BCCH TRXs are configured for the same cell.
41-6
l
The ICB is applicable to only the double-transceiver TRXs and must be configured as combining output. The TRXs supporting ICB are DRRU, DRFU, and optimized DTRU. Power Level of the BCCH TRX is set to 0 or 1. The non-BCCH TRX is not configured with PDCHs. The baseband FH and antenna hopping are not configured. To implement the intelligent combiner bypass, set TRX Priorityof the TRX that is on the same double-transceiver unit as the BCCH TRX to a small value. This is to ensure that the preferred double-transceiver TRX board where the BCCH is located enters the ICB mode in the same alternative conditions in idle hours, thus reducing the power consumption. TRX Priority should be used together with the channel management parameter of the cell Allocation TRX Priority Allowed. The channels can be allocated according to the TRX priorities only when Allocation TRX Priority Allowed is set to Yes.
l l l l
Preparation
Table 41-2 Example of Configuring the Intelligent Combiner Bypass Parameter ID IDXTYPE CELLNAME ICBALLOW Parameter Name Index Type Cell Name ICB Allowed Example BYNAME(By Name) BTS3900_01 YES(YES) Source Network planning Network planning Network planning
Procedure
Step 1 On the Local Maintenance Terminal, run the MOD CELLBASICPARA command to set ICB Allowed to YES(Yes).
NOTE
To implement the intelligent combiner bypass, run the MOD TRXDEV command to set TRX Priority of the TRX that is on the same double-transceiver unit as the BCCH TRX to a low value. This is to ensure the preferred double-transceiver TRX board where the BCCH is located enter the ICB mode in the same alternative conditions in idle hours, thus reducing the power consumption. TRX Priority should be used together with the channel management parameter of the cell Allocation TRX Priority Allowed. The channels can be allocated according to the TRX priorities only when Allocation TRX Priority Allowed is set to Yes through the MOD CELLCHMGAD command.
----End
Example
An example script for configuring the Intelligent Combiner Bypass
/*Configuring the Intelligent Combiner Bypass*/ MOD CELLBASICPARA: IDXTYPE=BYNAME, CELLNAME="BTS3900_01", ICBALLOW=YES;
Postrequisite
l
Verifying intelligent combiner bypass

Issue 01 (2010-05-20)
On the Local Maintenance Terminal, run the LST CELLBASICPARA command to check the setting of the ICB Allowed parameter. If the parameter is set to Yes, it indicates that intelligent combiner bypass is activated. On the Local Maintenance Terminal, run the MOD CELLBASICPARA command to set ICB Allowed to NO(NO). On the Local Maintenance Terminal, run the LST CELLBASICPARA command to check the setting of the ICB Allowed parameter. If the parameter is set to NO, it indicates that intelligent combiner bypass is deactivated.
Deactivating Intelligent Combiner Bypass 1. 2.
41.3 Configuring PSU Smart Control

This describes how to configure the PSU smart control. In the PSU smart control, only the required PSUs are switched on and the redundant PSUs are shut down to improve the efficiency of power conversion, thus reducing the power consumption and prolonging the operation time and lifetime of the PSU. Scenario The redundant PSUs are shut down if the power requirement of the BTS is met. In this manner, only parts of the PSUs are used to supply power. Thus, the efficiency of power conversion is improved and the lifetime of the PSU is prolonged. None.
Impact
Prerequisite
l l
The configuration of PSU smart control is license-controlled. Activate the license on the Local Maintenance Terminal. For details, see Activate BSC License. The working mechanism of the PSU smart control is as follows: The main control unit of the BTS in cooperation with the PMU in the power supply system manages the PSU. The BTS3012AE and BTS3006C/BTS3002E delivered with APM support this function. In addition, the BTS3900A, BTS3900, and DBS3900 delivered with APM30 support this function.
Preparation
Table 41-3 Example of configuring PSU Smart Control Parameter ID IDXTYPE STNAME PSUTURNINGO FFENABLE Parameter Name Index Type BTS Name PSU Turning Off Enable Example BYNAME(By Name) BTS3900 YES(YES) Source Network planning Network planning Network planning
41-8
Issue 01 (2010-05-20)
Procedure
Step 1 On the Local Maintenance Terminal, run the MOD BTSOTHPARA command to set PSU Turning Off Enable to YES(Yes). ----End
Example
An example script for configuring the PSU Smart Control
/*Configuring the PSU Smart Control*/ MOD BTSOTHPARA: IDXTYPE=BYNAME, BTSNAME="BTS3900", PSUTURNINGOFFENABLE=YES;
Postrequisite
l
Verifying PSU smart control
After the function of PSU smart control is enabled, part of the PSUs are automatically disabled at BTSs with low power consumption.
Deactivating PSU smart control 1. 2. On the Local Maintenance Terminal, run the MOD BTSOTHPARA command to set PSU Turning Off Enable to NO(No). Verifying deactivation of PSU smart control: After the function of PSU smart control is disabled, all the PSUs at BTSs with low power consumption are working properly.
41.4 Configuring Power Optimization Based on Channel Type

This describes how to configure the power optimization based on channel type, which is also called dynamic voltage adjustment. In the power optimization based on channel type, different working voltages are applied to the TRX power amplifier on the basis of the modulation modes of the channels to reduce the BTS power consumption. Scenario In the power optimization based on channel type, different working voltages are applied to the TRX power amplifier on the basis of the modulation modes of the channels to reduce the BTS power consumption. None
Impact
NEs Involved BSC,BTS
Prerequisite
l l l
This function is not license-controlled. This function is supported by 3012 series and 3900 series base stations. This function is not supported by the non-optimized DTRU.
Issue 01 (2010-05-20)
41-9
Preparation
Table 41-4 Example of the configuring the Power Optimization Based on Channel Type Parameter ID IDXTYPE CELLNAME EDGE BTSADJUST PDCHPWRSAV EN Parameter Name Index Type Cell Name EDGE Adjust Voltage PDCH Power Saving Enable Example BYNAME(By Name) BTS3900_01 YES(YES) YES(YES) YES(YES) Source Network planning Network planning Network planning Network planning Network planning
Procedure
Step 1 On the Local Maintenance Terminal, run the SET CELLGPRS command to set EDGE to YES(Yes). Step 2 On the Local Maintenance Terminal, run the MOD CELLBASICPARA command to set Adjust Voltage to YES(Yes). Step 3 On the Local Maintenance Terminal, run the SET CELLSOFT command to set PDCH Power Saving Enable to YES(Yes). ----End
Example
An example script for configuring the Power Optimization Based on Channel Type
/*Configuring the Power Optimization Based on Channel Type*/ SET CELLGPRS: IDXTYPE=BYNAME, CELLNAME="BTS3900_01", GPRS=SupportAsInnPcu, EDGE=YES; MOD CELLBASICPARA: IDXTYPE=BYNAME, CELLNAME="BTS3900_01", BTSadjust=YES; SET CELLSOFT: IDXTYPE=BYNAME, CELLNAME="BTS3900_01", DROPCTRLCONNFAILRLFAIL=1, PDCHPWRSAVEN=YES;
Postrequisite
l
Deactivating power optimization based on channel type 1. 2. On the Local Maintenance Terminal, run the MOD CELLBASICPARA command to set Adjust Voltage to NO(No). On the Local Maintenance Terminal, run the SET CELLSOFT command to set PDCH Power Saving Enable to NO(No).
41.5 Configuring Enhanced BCCH Power Consumption Optimization

This describes how to configure the enhanced BCCH power consumption optimization. The enhanced BCCH power consumption optimization reduces the BTS power consumption in idle
hours by reducing the power of non-BCCHs on the BCCH TRX, thus reducing the OPEX of the operators. The time segment and degree of the power reduction are configurable. Scenario Impact Reduce the BTS power consumption in idle hours None
NEs Involved BSC,BTS
Prerequisite
l
The configuration of Enhanced BCCH Power Consumption Optimization is licensecontrolled. Activate the license on the Local Maintenance Terminal. For details, see Activate BSC License. This function is supported by 3012 series and 3900 series base stations.
Preparation
Table 41-5 Example of the configuring the Enhanced BCCH Power Consumption Optimization Parameter ID IDXTYPE BTSNAME MAINBCCHPW RDTEN MAINBCCHPWRDTS TIME MAINBCCHPW RDTETIME MAINBCCHPWRDTR ANGE MAINBCCHPWDTAC TCHEN Parameter Name Index Type BTS Name Main BCCH Trx Non-Bcch Time Slot Power Derating Enable BCCH TRX Non-BCCH Timeslot Power Derating Start Time[HH:MM] BCCH TRX Non-BCCH Timeslot Power Derating End Time[HH:MM] Main BCCH Trx Non-Bcch Time Slot Power Derating Range[0.2dB] BCCH TRX Non-BCCH Timeslot Power Derating Enabled Example BYNAME(By Name) BTS3900 YES(YES) Source Network planning Network planning Network planning
00:00
Network planning
05:00
Network planning
Network planning
YES(YES)
Network planning
Procedure
Step 1 On the Local Maintenance Terminal, run the MOD CELLOTHEXT command to set Main BCCH Trx Non-Bcch Time Slot Power Derating Enable to YES(Yes).Then, configure the time segment and degree of the power reduction.

NOTE
When the power of the non-BCCH timeslots on the BCCH TRX is reduced, the MS camping on a neighboring cell may not measure the downlink receive level of the serving cell accurately. This may affect the MS handover from the neighboring cell to the serving cell. Therefore, be careful when you enable the function of enhanced BCCH power consumption optimization. When Main BCCH Trx Non-Bcch Time Slot Power Derating Enable is set to YES(YES) and the current time is between Main BCCH Trx Non-Bcch Time Slot Power Derating Start Time and Main BCCH Trx Non-Bcch Time Slot Power Derating End Time, the BTS decreases the transmit power of idle channels on the non-BCCH timeslots of the BCCH TRX. The power decrease degree is controlled by Main BCCH Trx Non-Bcch Time Slot Power Derating Range When Main BCCH Trx Non-Bcch Time Slot Power Derating Active Channel Enable is set to YES (YES), the BTS performs power decrease on the occupied channels on the BCCH TRX. If the power control is performed on the occupied channels and the decreased power is smaller than Main BCCH Trx Non-Bcch Time Slot Power Derating Range, adopt Main BCCH Trx Non-Bcch Time Slot Power Derating Range to transmit signals. Otherwise, adopt the power required for the channel power control to transmit signals.
----End
Result Example
An example script for configuring the Enhanced BCCH Power Consumption Optimization
/*Configuring the Enhanced BCCH Power Consumption Optimization*/ MOD CELLOTHEXT: IDXTYPE=BYNAME, CELLNAME="BTS3900_01", MAINBCCHPWRDTEN=YES, MAINBCCHPWRDTSTIME=00&00, MAINBCCHPWRDTETIME=05&00, MAINBCCHPWRDTRANGE=2, MAINBCCHPWDTACTCHEN=YES;
Postrequisite
l
Verifying enhanced BCCH power consumption optimization
On the Local Maintenance Terminal, run the LST CELLOTHEXT command to query the setting of Main BCCH Trx Non-Bcch Time Slot Power Derating Enable. If the parameter is set to YES(Yes), it indicates that the function of enhanced BCCH power consumption optimization is activated. On the Local Maintenance Terminal, run the MOD CELLOTHEXT command to set Main BCCH Trx Non-Bcch Time Slot Power Derating Enable to NO(No). On the Local Maintenance Terminal, run the LST CELLOTHEXT command to query the setting of Main BCCH Trx Non-Bcch Time Slot Power Derating Enable. If the parameter is set to NO(No), it indicates that the function of enhanced BCCH power consumption optimization is deactivated.
Deactivating enhanced BCCH power consumption optimization 1. 2.
41.6 Configuring Active Backup Power Control

This describes how to configure the active backup power control. The BTS uses the configured battery for power supply when the mains failure occurs. The battery provides a limited capacity. To prolong the power supply time of the battery, the BSC shuts down certain TRXs or reduces the maximum transmit power of the TRX to reduce the BTS power consumption. This is called active backup power control.
Scenario
When the mains failure occurs, the BSC shuts down certain TRXs or reduces the maximum transmit power of the TRX to reduce the BTS power consumption, thus prolonging the power supply time of the battery. None
Impact
Prerequisite
l l
The configuration of Active Backup Power Control is license-controlled. Activate the license on the Local Maintenance Terminal. For details, see Activate BSC License. The BTS is configured with the PMU. This function is supported by 3012, 3012II, 3012III and 3900 series base stations.
l l
Preparation
Table 41-6 Example of the configuring the Active Backup Power Control Parameter ID IDXTYPE STNAME BAKPWRSAVM ETHOD BAKPWRSAVP OLICY DROPPWRSTA RTTIME SHUTDOWNTR XSTARTTIME DROPPWRINTE RVAL DROPPWRSTEP MAXDROPPWR THRESHOLD Parameter Name Index Type BTS Name Backup Power Saving Method Backup Power Saving Policy Drop Power Start Time [T1][hour] Shutdown Trx Start Time [T2][hour] Drop Power Time Interval [T3][min] Drop Power Step [dB] Max Drop Power Threshold[dB] Example BYNAME(By Name) BTS3900 BYPWR(Reduce Power) BYSAVING(Backup Power Preferred) 2 3 5 2 10 Source Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning
Procedure
Step 1 On the Local Maintenance Terminal, run the MOD BTSBAKPWR command to set Backup Power Saving Method to BYPWR(Reduce Power).Then, set the following parameters: Drop Power Start Time(T1)(H), Shutdown Trx Start Time(T2)(H), Drop Power Time Interval (T3)(M), Drop Power Step(db), and Max Drop Power Threshold(db).

NOTE
When Backup Power Saving Method is set to BYTRX(Turn off Trx), the BSC shuts down the TRXs whose Shut Down Enabled is set to ENABLE(Enable) after the BTS is powered off. The Shut Down Enabled parameter can be set by running the MOD TRXDEVcommand.
----End
Example
An example script for configuring the Active Backup Power Control
/*Configuring the Active Backup Power Control*/ MOD BTSBAKPWR: IDXTYPE=BYNAME, STNAME="BTS3900", BAKPWRSAVMETHOD=BYPWR, BAKPWRSAVPOLICY=BYSAVING, DROPPWRSTARTTIME=2, SHUTDOWNTRXSTARTTIME=3, DROPPWRINTERVAL=5, DROPPWRSTEP=2, MAXDROPPWRTHRESHOLD=10;
Postrequisite
l
Verifying active backup power control 1. Turn off the mains power supply switch of the BTS. Then, part of the TRXs are automatically shut down under the control of the timer. In addition, the transmit power of the TRXs is reduced in certain steps. Turn on the mains power supply switch of the BTS. Verify that the shut-down TRXs are automatically started up, and all the TRXs normally transmit power. On the Local Maintenance Terminal, run the MOD TRXDEV command to set Shut Down Enabled to DISABLE(Disable). Verifying deactivation of active backup power control: Turn off the mains power supply switch of the BTS. Then, the BSC shuts down all the TRXs that can be shut down under the BTS. The power of the remaining TRXs does not change. Then, turn on the mains power supply switch of the BTS, and verify that the BTS automatically starts up all the shut-down TRXs.
2.
l
Deactivating active backup power control 1. 2.
41.7 Configuring Multi-Carrier Intelligent Voltage Regulation

This feature monitors the output power of all the carriers within the module. When the total output power of the power amplifier reduces after the measurement for a period, this feature adjusts the working voltage of the power amplifier to a lower value according to the related algorithm. In this way, the power amplifier works with great efficiency after the output power reduces, thus reducing the power consumption of the TRX. Scenario The working voltage of the power amplifier of the multi-carrier is adjusted on the basis of the output power of the power amplifier. Thus, the working efficiency of the power amplifier is improved and the power consumption of the BTS is reduced. None
Impact
41-14
Issue 01 (2010-05-20)
Prerequisite
l l
The configuration of PSU smart control is license-controlled. Activate the license on the Local Maintenance Terminal. For details, see Activate BSC License. The multi-carrier intelligent voltage adjustment is supported by 3900 series base stations. The TRXs supporting this function are GRRU and GRFU. The cell attribute parameter Adjust Voltage is set to YES(YES).
Preparation
Table 41-7 Example of the configuring the Multi-Carrier Intelligent Voltage Regulation Parameter ID IDXTYPE STNAME PAADJVOL Parameter Name Index Type BTS Name PA Intelligent Adjust Voltage Example BYNAME(By Name) BTS3900 YES(YES) Source Network planning Network planning Network planning
Procedure
Step 1 On the Local Maintenance Terminal, run the MOD BTSOTHPARA command to set PA Intelligent Adjust Voltage to YES(Yes). ----End
Example
An example script for configuring the Multi-Carrier Intelligent Voltage Regulation
/*Configuring Multi-Carrier Intelligent Voltage Regulation*/ MOD BTSOTHPARA: IDXTYPE=BYNAME, BTSNAME="BTS3900", PAADJVOL=YES;
Postrequisite
l
Verifying multi-carrier intelligent voltage regulation
On the Local Maintenance Terminal, run the LST BTSOTHPARA command. Check the setting of PA Intelligent Adjust Voltage. If the parameter is set to YES, it indicates that the function of multi-carrier intelligent voltage regulation is activated. On the Local Maintenance Terminal, run the MOD BTSOTHPARA command to set PA Intelligent Adjust Voltage to NO(No). On the Local Maintenance Terminal, run the LST BTSOTHPARA command to check the setting of PA Intelligent Adjust Voltage. If the parameter is set to NO, it indicates that the function of multi-carrier intelligent voltage regulation is deactivated.
Deactivating multi-carrier intelligent voltage regulation 1. 2.
Issue 01 (2010-05-20)
41.8 Configuring TRX Working Voltage Adjustment

The working voltage of the TRX is always set to a high level to ensure the maximum output power of the TRX. In actual application, however, the maximum output power of the TRX is not always required. In this case, if the TRX still works under such a high voltage, extra power is consumed because a lower working voltage can also provide the required output power. To reduce the power consumption of the TRX, Huawei developed the function of "TRX Working Voltage Adjustment" that enables the intelligent adjustment of the TRX working voltage according to the output power. Scenario Adjustment of the TRX working voltage according to the output power. Hence, to lower the TRX power consumption, the TRX should work under a suitable voltage to ensure an efficient output power. None
Impact
NEs Involved BSC and BTS
Prerequisite
l
This function is supported by the optimized TRX modules of the BTS3012 series base stations. This function is supported by the TRX modules of all the BTS3900 series base stations.
Preparation
Table 41-8 Example of the TRX Working Voltage Adjustment Data Type Cell Attributes Parameter ID IDXTYPE CELLNAME BTSADJUST Device Attributes TRXBN POWL POWT Parameter Name Index Type Cell Name Adjust Voltage TRX Board No. Power Level Power Type Example BYNAME(By Name) BTS3900_01 YES(YES) 0 1 45W(45W) Source Network planning Network planning Network planning Network planning Network planning Network planning
Procedure
Step 1 On the Local Maintenance Terminal, run the MOD CELLBASICPARA command to set Adjust Voltage to YES(Yes). ----End
Example
An example script for configuring the TRX Working Voltage Adjustment
/*Configuring TRX Working Voltage Adjustment*/ /*Configuring Cell Attributes */ MOD CELLBASICPARA: IDXTYPE=BYNAME, CELLNAME="BTS3900_01", BTSadjust=YES; /*Configuring Device Attributes*/ MOD TRXDEV: IDXTYPE=BYNAME, CELLNAME="BTS3900_01", TRXBN=0, POWL=1, POWT=45W;
Postrequisite
l
Verifying TRX working voltage adjustment
On the Local Maintenance Terminal, run the LST CELLBASICPARA command to check the setting of Adjust Voltage. If the parameter is set to YES, it indicates that the function of TRX working voltage adjustment is activated. On the Local Maintenance Terminal, run the MOD CELLBASICPARA command to set Adjust Voltage to NO(No). On the Local Maintenance Terminal, run the LST CELLBASICPARA command to check the setting of Adjust Voltage. If the parameter is set to No, it indicates that the function of TRX working voltage adjustment is deactivated.
Deactivating TRX working voltage adjustment 1. 2.
Issue 01 (2010-05-20)
41-17
42 Configuring Tight BCCH Frequency Reuse
42
Configuring Tight BCCH Frequency Reuse
The tight BCCH frequency reuse technology is applicable to the network with insufficient frequency resources. It increases the reusability of BCCH frequencies and reduces the number of frequencies used by the BCCHs. Therefore, more frequencies can be used at the FH layer, thus improving the system capacity. Scenario Tight BCCH frequency reuse is configured in the network with insufficient frequency resources, thus improving frequency reuse rate and increasing the system capacity. When the function of tight BCCH frequency reuse is enabled, an MS may be handed over from the non-BCCH TRX to the BCCH TRX if the load of a cell increases. This increases the number of handovers in the network. Concentric cell and multiband networks do not support tight BCCH frequency reuse.
Impact
NEs Involved BSC
Prerequisite
l l
Tight BCCH frequency reuse is not restricted by the license. The GXPUM and Abis interface board are configured on the GMPS or GEPS, and there is idle port on the Abis interface board.
Preparation
Take the configuration of BTS3012 in TDM transmission mode as an example. Table 42-1 Example of the data negotiated and planned for adding a BTS Data Type BTS basic attributes Parameter ID BTSNAME Parameter Name BTS Name Example BTS3012 Source Network planning
Issue 01 (2010-05-20)
42-1
Data Type
Parameter ID TYPE UPNODE SRN SN PN BTSDESC MPMODE FlexAbisMod e AbisByPass Mode ServiceMode DCELLNAM E DCTYPE DCMCC DCMNC DCLAC DCCI CPLMode TRXBN
Parameter Name BTS Type Up Node Type Subrack No. Slot No. Port No. BTS Description Multiplexing Mode Flex Abis Mode Abis By Pass Mode Service Type Cell Name Cell type Cell MCC Cell MNC Cell LAC Cell CI Separate Mode TRX Board No.
Example BTS3012 BSC 0 26 0 TDM BTS3012 MODE4_1 FLEX_ABIS(Flex Abis) FALSE(Not Support) TDM TDMCELL GSM900 460 01 8240 1 UNSUPPORT(Not Support) 0
Source Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning
42-2
Issue 01 (2010-05-20)
Data Type
Parameter ID FREQ
Parameter Name TRX Freq.
Example 988
Table 42-2 Example of the data negotiated and planned for configuring tight BCCH frequency reuse Data Type Channel management parameters of the cell Parameter ID IDXTYPE CELLIDX TIGHTBCCHSWI TCH Advanced channel management parameters of the cell TIGHTBCCHASSMAINBCCHLEV Parameter Name Index Type Cell Index TIGHT BCCH Switch Level Thresh. for Assigning Main BCCH Carrier Channel Under TIGHT BCCH Quality Thresh. for Assigning Main BCCH Carrier Channel Under TIGHT BCCH HO Control Switch Example BYIDX(By Index) 0 YES(YES) 30 Source Network planning Network planning Network planning Network planning
TIGHTBCCHASSMAINBCCHQUA L
Network planning
Cell handover parameters
HOCTRLSWITCH
HOALGORITH M1(HO Algorithm I) 3 3 3
TIGHTBCCHHOS TATTIME TIGHTBCCHHOL ASTTIME Cell handover advanced parameters TIGHTBCCHRXQUALTHRES TIGHTBCCHHOLOADTHRES
TIGHT BCCH HO Watch Time[s] TIGHT BCCH HO Valid Time[s] RX_QUAL Threshold for TIGHT BCCH HO Load Threshold for TIGHT BCCH HO
80
Procedure
Step 1 On the Local Maintenance Terminal, run the ADD BTS command to add a BTS.
Step 2 On the Local Maintenance Terminal, run the SET CELLCHMGBASIC command to set TIGHT BCCH Switch to YES(YES). Step 3 On the Local Maintenance Terminal, run the MOD CELLCHMGAD command to set Level Thresh. for Assigning Main BCCH Carrier Channel Under TIGHT BCCH and Quality Thresh. for Assigning Main BCCH Carrier Channel Under TIGHT BCCH. Step 4 On the Local Maintenance Terminal, run the SET CELLHOBASIC command to set HO Control Switch, TIGHT BCCH HO Watch Time[s], and TIGHT BCCH HO Valid Time [s]. Step 5 On the Local Maintenance Terminal, run the SET CELLHOAD command to set RX_QUAL Threshold for TIGHT BCCH HO and TIGHT Load Threshold for TIGHT BCCH HO. ----End
Example
An example script for configuring tight BCCH frequency reuse for the BTS3012 in TDM transmission mode is as follows:
/*Add a BTS3012*/ ADD BTS: BTSNAME= "BTS3012", TYPE = BTS3012, UPNODE = BSC, SRN = 0, SN=26, PN=0, BTSDESC = "TDM BTS3012", MPMODE = MODE4_1, FlexAbisMode=FLEX_ABIS, AbisByPassMode=False, ServiceMode=TDM, DCELLNAME="TDMCELL", DCTYPE=GSM900, DCMCC="460", DCMNC="01", DCLAC=8240, DCCI=1, CPLMode=UNSUPPORT, TRXBN=0, FREQ=988; /*Set basic channel management parameters of the cell*/ SET CELLCHMGBASIC: IDXTYPE=BYIDX, CELLIDX=0, TIGHTBCCHSWITCH=YES; /*Modify advanced channel management parameters of the cell*/ (MOD CELLCHMGAD)MOD CELLCHMGAD: IDXTYPE=BYIDX, CELLIDX=0, TIGHTBCCHASSMAINBCCHLEV=30, TIGHTBCCHASSMAINBCCHQUAL=1; /*Set basic handover parameters of the cell*/ SET CELLCHMGBASIC: IDXTYPE=BYIDX, CELLIDX=0, HOCTRLSWITCH=HOALGORITHM1, TIGHTBCCHHOSTATTIME=3, TIGHTBCCHHOLASTTIME=2; /*Set advanced handover parameters of the cell*/ SET CELLCHMGBASIC: IDXTYPE=BYIDX, CELLIDX=0, HOCTRLSWITCH=HOALGORITHM1, TIGHTBCCHRXQUALTHRES=3, TIGHTBCCHHOLOADTHRES=80;
Postrequisite
l
Verifying tight BCCH frequency reuse 1. On the Local Maintenance Terminal, run the MOD CELLCHMGAD command to set Level Thresh. for Assigning Main BCCH Carrier Channel Under TIGHT BCCH to 63 and Quality Thresh. for Assigning Main BCCH Carrier Channel Under TIGHT BCCH to 0. On the Local Maintenance Terminal, run the SET CELLHOAD command to set TIGHT Load Threshold for TIGHT BCCH HO to 100. Use the MS to initiate a call in the cell. Verify that the call is successfully set up.
2. 3.
l
Deactivating tight BCCH frequency reuse 1. 2. On the Local Maintenance Terminal, run the SET CELLCHMGBASIC command to set TIGHT BCCH Switch to NO(No). On the Local Maintenance Terminal, run the LST CELLCHMGBASIC command. If TIGHT BCCH Switch is set to NO, it indicates that the function of tight BCCH frequency reuse is deactivated.
42-4
43 Configuring Connection Inter BSC over IP
43
Configuring Connection Inter BSC over IP

This describes how to configuring Inter-BSC signaling links on the current BSC and external BSC on the Local Maintenance Terminal. Scenario Impact the scenarios of inter-BSC information exchange None
NEs Involved BSC
Prerequisite
If Abis over IP or A over IP is adopted, the IP interface boards of two BSCs can be connected through the switches. If Abis over IP or A over IP is not adopted, a pair of IP interface boards need to be added to each BSC.
Preparation
Assume that the name of the current BSC is BSC216 and that of the external BSC is BSC217. By setting the parameters of the current BSC and external BSC, you can finish the configuration of the inter-BSC signaling links. The configuration of the current BSC is the same as that of the external BSC. Take the configuration of the current BSC216 as an example negotiated and planned as follows: Table 43-1 Example of the data negotiated and planned for Configuring Inter-BSC Signaling Links Data Type Board attributes Parameter ID SRN SN Parameter Subrack No. Slot No. Example 0 24 Source Network planning Network planning
Issue 01 (2010-05-20)
43-1
Data Type IP attributes Device IP address
Parameter ID IPADDR MASK Port IP address PORT IPINDEX IPADDR MASK BSC route IPADDR MASK GATEWAY
Parameter IP address Subnet mask Port No. IP address index IP address Subnet mask IP address Subnet mask Gateway IP address Local Entity Name OPC Code Routing Context Destination Entity No. Destination Entity Name DPC Code Routing Context Subsystem Number Network Element ID
Example 10.10.10.216 255.255.255. 0 0 0 2.2.2.2 255.255.255. 0 10.10.10.217 255.255.255. 255 2.2.2.1 BSC216 h'a1 4294967290 98 BSC217 h'b1 4294967290 143 1
MU3A attributes
M3UA local entity
NAME OPC RTCONTE XT
M3UA destination entity
DENO NAME DPC RTCONTE XT SSN CNID
43-2
Issue 01 (2010-05-20)
Data Type M3UA link set
Parameter ID SIGLKSID X NAME
Parameter Signalling Link Set Index Signalling Link Set Name Adjacent Destination Entity No. Destination Entity No. Signalling Link Set Index Signalling link set index Subrack No. Local Port No. Destination Port No. First Local IP Address First Destination IP Address
Example 1
Source Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning
T0217
DENO
98
M3UA route
DENO SIGLKSID X
98 1
M3UA link
SIGLKSID X SRN LOCPN PEERPN LOCIP1 PEERIP1
1 0 1 45 10.10.10.216 10.10.10.217
Procedure
Step 1 On the Local Maintenance Terminal of the current BSC, run the command LST ITFIPTYPE to query the communication type of the Abis interface. Step 2 On the Local Maintenance Terminal of the current BSC, run the command ADD DEVIP to add the device IP address. Step 3 On the Local Maintenance Terminal of the current BSC, run the command ADD PHYPORTIP to add the port IP address. Step 4 On the Local Maintenance Terminal of the current BSC, run the command ADD IPRT to add the IP address. The gateway address is the IP address of the peer board, that is, the IP address of the GFGUB port on the external BSC.
Step 5 On the Local Maintenance Terminal of the current BSC, run the command ADD M3LE to add the M3UA local entity. Step 6 On the Local Maintenance Terminal of the current BSC, run the command ADD M3DE to add the M3UA destination entity. Step 7 On the Local Maintenance Terminal of the current BSC, run the command ADD M3LKS to add the M3UA link set. Step 8 On the Local Maintenance Terminal of the current BSC, run the command ADD M3RT to add the M3UA router. Step 9 On the Local Maintenance Terminal of the current BSC, run the command ADD M3LNK to add the M3UA link. Step 10 Repeat Step 1 through Step 9 on the Local Maintenance Terminal of the external BSC to configure links of the external BSC. ----End
Example
The example script for configuring the current BSC is as follows:
/*Confirm the transmission mode on the Gb interface*/ LST ITFIPTYPE:; /*Add device IP address of the current BSC*/ ADD DEVIP: SRN=0, SN=24, IPADDR="10.10.10.216", MASK="255.255.255.0"; /*Add port IP address of the current BSC*/ ADD PHYPORTIP: SRN=0, SN=24, PORT=1, IPADDR="2.2.2.2", MASK="255.255.255.0"; /*Add IP route of the current BSC*/ ADD IPRT: SRN=0, SN=24, IPADDR="10.10.10.217", MASK="255.255.255.255", GATEWAY="2.2.2.1"; /*Add M3UA local entity*/ ADD M3LE: NAME="BSC216", OPC=h'a1, RTCONTEXT=0, NETSTRUCT=BIT14; /*Add M3UA destination entity*/ ADD M3DE: DENO=98, NAME="BSC217", DPC=h'b1, RTCONTEXT=0, SSN=143, CNID=1; /*Add M3UA link set*/ ADD M3LKS: SIGLKSIDX=1, NAME="T0217", DENO=98; /*Add M3UA route*/ ADD M3RT: DENO=98, SIGLKSIDX=1; /*Add M3UA link*/ ADD M3LNK: SIGLKSIDX=1, SRN=0, LOCPN=1, PEERPN=45, LOCIP1="10.10.10.216", PEERIP1="10.10.10.217";
43-4
Issue 01 (2010-05-20)
44 Managing a BSC Soft-Synchronized Network Task
44
Managing a BSC Soft-Synchronized Network Task
About This Chapter

The Soft-Synchronized Network feature realizes the synchronization through software. With this feature, all the BTSs under one BSC synchronize with each other by adjusting the frame number, timeslot number, and bit offset in the timeslot to be the same through software. In a synchronous network, dynamic frequency allocation and dynamic channel assignment can be adopted to minimize inter-cell co-channel and adjacent-channel collision. This greatly improves the frequency usage and increases the network capacity.
Prerequisite
The license is obtained and activated. To obtain and activate the license, do as follows:
l l
The license is required for the implementation of Soft-Synchronized Network. Activate the license on the Local Maintenance Terminal. For details, see Activate BSC License You can configure parameters related to Soft-Synchronized Network only by running MML commands on the local maintenance terminal. To make best use of the Soft-Synchronized Network technology, comply with the following rules:
The Soft-Synchronized Network technology is applicable to the tight frequency reuse scenario. The distance between BTSs should be shorter than 900 m. A distance of shorter than 800 m is recommended. The network using the Soft-Synchronized Network technology should be planned in an continuous coverage area. That is, under a BSC, the continuous coverage area can be regarded as a to-be-synchronized area. When the Soft-Synchronized Network technology is used in dual-band networks, the networks operating at different bands should be separated for synchronization. The BTSs operating at 900 MHz are grouped together for synchronization, and the BTSs operating at 1800 MHz are grouped together for synchronization.
Issue 01 (2010-05-20)
If concentric cells exist in a network, collect synchronization information of underlaid subcells. If BTSs with GPS antennas exist in the network, it is recommended that you set these BTSs as reference BTSs to shorten the synchronization time of the entire network.
44.1 Concepts Related to the Soft-Synchronized Network This describes the concepts related to the soft-synchronized network. The concepts consist of reference BSC, lower-level BSC, controlling BSC, and collaborating BSC. 44.2 Creating an Intra-BSC Soft-Synchronized Network Task This describes how to create an intra-BSC soft-synchronized network task on the Local Maintenance Terminal. 44.3 Configuring a Pair of Neighboring Cells of Intra-BSC Soft-Synchronized Network Task In an intra-BSC soft-synchronized network task, a pair of neighboring cells are automatically generated by the program according to the rules. If the neighboring cells do not meet the measurement requirements, you can reconfigure the neighboring cells as required. 44.4 Verifying an Intra-BSC Soft-Synchronized Network Task This describes how to verify an intra-BSC soft-synchronized network task on the Local Maintenance Terminal. 44.5 Creating an Inter-BSC Soft-Synchronized Network Task This describes how to create an inter-BSC soft-synchronized network task on the Local Maintenance Terminal of the controlling BSC and collaborating BSC. 44.6 Verifying an Inter-BSC Soft-Synchronized Network Task This describes how to verify the inter-BSC soft-synchronized network task on the Local Maintenance Terminal. 44.7 Collecting the Offset Information Between BTSs This describes how to collect the offset information between BTSs on the Local Maintenance Terminal. Collecting the offset information between BTSs consists of collecting the intra-BSC and inter-BSC offset information between BTSs. The collected offset information provides a basis for adjusting the BTS clock. 44.8 Synchronizing BTSs After a soft-synchronized network task is created, the BTS offset information is collected and the offset time is adjusted automatically to synchronize the BTSs. If the drive test result shows that the offset between the synchronized BTSs is great, you can manually synchronize the BTSs on the Local Maintenance Terminal. This operation is optional as required. 44.9 Deleting a Soft-Synchronized Network Task This describes how to delete a soft-synchronized network task on the Local Maintenance Terminal.
44-2
Issue 01 (2010-05-20)
44.1 Concepts Related to the Soft-Synchronized Network

This describes the concepts related to the soft-synchronized network. The concepts consist of reference BSC, lower-level BSC, controlling BSC, and collaborating BSC.
l
Reference BSC: The inter-BSC soft-synchronized network task is implemented in hierarchical mode. The BSC located in the center of the coverage area of the BSCs is taken as the starting point of the hierarchical synchronization. Therefore, it is referred to as the reference BSC. Lower-level BSC: The inter-BSC soft-synchronized network task is implemented in hierarchical mode. If BSC A is located in a lower level than BSC B, then BSC A is a lowerlevel BSC relative to BSC B. Controlling BSC: The BSC that initiates the offset information collection between BSCs and plays a controlling role in the soft-synchronized network task is called a controlling BSC. Collaborating BSC: The BSC that collaborates with the controlling BSC during the softsynchronized network task is referred to as a collaborating BSC.
NOTE
Controlling BSC and collaborating BSC are relative concepts. If the soft-synchronized network task is implemented between BSC A and reference BSC, the reference BSC is the controlling BSC whereas BSC A is the collaborating BSC. If the soft-synchronized network task is implemented between BSC A and a lower-level BSC B, then BSC A is the controlling BSC whereas BSC B is the collaborating BSC.
44.2 Creating an Intra-BSC Soft-Synchronized Network Task

This describes how to create an intra-BSC soft-synchronized network task on the Local Maintenance Terminal. Scenario The soft-synchronized network is applicable to the scenario of tight frequency reuse. The soft-synchronized network must work with other technologies such as network planning or IBCA. The gain of the radio-related KPIs can be greatly improved. In addition, the conversion from an asynchronous network to a synchronous network can effectively reduce the interference on the entire network and expand the network capacity.
Impact
Prerequisite
l
Each BSC should be configured with at least two BTSs. In addition, the BTSs should support the soft-synchronized network. The BTSs must be configured with the same SiteSyncZone. Each BTS should be configured with at least two cells. In addition, the longitude, latitude, and antenna azimuth of each cell should be configured.
l l
Issue 01 (2010-05-20)
Preparation
The following operation creates the soft-synchronized network task (Aiss Task Index = 0). Assume that this soft-synchronized network task is implemented between two BTSs. Table 44-1 Example of the data negotiated and planned for setting the BTS synchronization zone Parameter ID IDXTYPE BTSIDX SYMOFFSET SITESYNCZONE Parameter Name Index Type BTS index SymOffset SiteSyncZone Example BYIDX(By Index) 1, 2 0 0 Source Network planning Network planning Network planning Network planning
Table 44-2 Example of the data negotiated and planned for creating an intra-BSC softsynchronized network task Parameter ID TASKIDX GATHON Parameter Name Aiss Task Index Offset Information Collection Switch Offset Time Adjustment Switch Reference BTS Index Reinitialize Neighboring Cell List Support BSC AISS Example 0 ON(ON) Source Network planning Network planning
ADTON
ON(ON)
Network planning
BASEBTSIDX REINITTBL
1, 2 YES(YES)
ISSPTBSCAISS
NO(NO)
Network planning
Procedure
Step 1 Run the SET BTSAISS command on the Local Maintenance Terminal. Set the same SiteSyncZone for the BTSs that participate in the soft-synchronized network task.
44-4
Issue 01 (2010-05-20)
NOTE
Set the same SiteSyncZone for the BTSs numbered 1 and 2. SymOffset is an optional parameter. This parameter determines the value of Frame Offset [frame No.], and should be set as required. In general, the default value is retained.
Step 2 On the Local Maintenance Terminal, run the ADD AISSCFG command. Choose the BTSs that support the soft-synchronized network. Then, set Offset Information Collection Switch and Offset Time Adjustment Switch to ON(ON), and set Support BSC AISS to NO(NO) to create an intra-BSC soft-synchronized network task.
NOTE
After the Offset Information Collection Switch and Offset Time Adjustment Switch are turned on, the BTS offset information are collected and the offset time are adjusted automatically to finish the softsynchronized network task. To manually collect the offset information and adjust the offset time, see 44.7 Collecting the Offset Information Between BTSs and 44.8 Synchronizing BTSs.
----End
Example
An example script of creating the intra-BSC soft-synchronized network task is as follows:
/*Set the BTS synchronization zone*/ SET BTSAISS: IDXTYPE=BYIDX, BTSIDX=1, SYMOFFSET=0, SITESYNCZONE=0; SET BTSAISS: IDXTYPE=BYIDX, BTSIDX=2, SYMOFFSET=0, SITESYNCZONE=0; /*Create an intra-BSC soft-synchronized network task*/ ADD AISSCFG: TASKIDX=0, GATHON=ON, ADTON=ON, BASEBTSIDX=1, REINITTBL=YES, ISSPTBSCAISS=NO; ADD AISSCFG: TASKIDX=0, GATHON=ON, ADTON=ON, BASEBTSIDX=2, REINITTBL=YES, ISSPTBSCAISS=NO;
44.3 Configuring a Pair of Neighboring Cells of Intra-BSC Soft-Synchronized Network Task

In an intra-BSC soft-synchronized network task, a pair of neighboring cells are automatically generated by the program according to the rules. If the neighboring cells do not meet the measurement requirements, you can reconfigure the neighboring cells as required.
NOTE
The BTSs that serve the configured cells should support soft-synchronized network. If the neighboring cell list is empty, you must add the pair of neighboring cells starting from the reference BTS. The BTS that serves the first cell in the pair of neighboring cells should be in the neighboring cell list of the softsynchronized network task. You can run the DSP NCELLTBL command to query the neighboring cell list composed of the cells and BTSs that serve the cells.
Prerequisite
l l l
The intra-BSC soft-synchronized network task is created successfully. The neighboring cell relations between the pair of neighboring cells are configured. The two added cells must be in the same frequency band. If the cell is a concentric cell, the overlaid cell and underlaid cell must be in the same frequency band.
Issue 01 (2010-05-20)
Preparation
Table 44-3 Example of the data negotiated and planned for creating an intra-BSC softsynchronized network task Parameter ID TASKIDX BYCELLTYPE SCELLIDX MCELLIDX Parameter Name Aiss Task Index Cell Index Type First Cell Index Second Cell Index Example 0 BYIDX(By Index) 10 15 Source Network planning Network planning Network planning Network planning
Procedure
Step 1 On the Local Maintenance Terminal, run the DSP NCELLTBL command to check whether the neighboring cell list meets the actual measurement requirements. If the neighboring cell list does not meet the requirements of the actual measurement, reconfigure the neighboring cell list as follows: Step 2 On the Local Maintenance Terminal, run the ADD NCELL command to add an optimal pair of neighboring cells. ----End
Example
An example script of configuring the neighboring cells for an intra-BSC soft-synchronized network task is as follows:
/*Check whether the neighboring cell list meets the requirements of the actual measurement*/ DSP NCELLTBL: TASKIDX=0; /*Add the optimal pair of neighboring cells*/ ADD NCELL: TASKIDX=0, BYCELLTYPE=BYIDX, SCELLIDX=10, MCELLIDX=15;
Postrequisite
Run the DEL NCELL command on the Local Maintenance Terminal to delete the optimal pair of neighboring cells. An example script is as follows: TASKIDX=0, BYCELLTYPE=BYIDX, SCELLIDX=10, MCELLIDX=15, DELSITE=YES;
NOTE
If the BTS is also deleted, you need to set Delete BTS In the Neighboring Cell List to Yes.
l l
The BTS can be deleted only when there are no neighboring cells in the BTS. If there are neighboring cells in the BTS, the BTS cannot be deleted even if Delete BTS In the Neighboring Cell List is set to YES(YES).
44-6
Issue 01 (2010-05-20)
44.4 Verifying an Intra-BSC Soft-Synchronized Network Task

This describes how to verify an intra-BSC soft-synchronized network task on the Local Maintenance Terminal.
Procedure
Step 1 On the Local Maintenance Terminal, run the LST AISSCFG command to query the information about the soft-synchronized network task.
NOTE
If you do not set Aiss Task Index, the detailed information about all the soft-synchronized network tasks are queried. Check whether Aiss Task Index added in the procedure of 44.2 Creating an Intra-BSC SoftSynchronized Network Task exists. If it exists, the task of creating the soft-synchronized network task is successful.
----End
44.5 Creating an Inter-BSC Soft-Synchronized Network Task

This describes how to create an inter-BSC soft-synchronized network task on the Local Maintenance Terminal of the controlling BSC and collaborating BSC. Scenario The soft-synchronized network is applicable to the scenario of tight frequency reuse. The soft-synchronized network must work with other technologies such as network planning or IBCA. The gain of the radio-related KPIs can be greatly improved. In addition, the conversion from an asynchronous network to a synchronous network can effectively reduce the interference on the entire network and expand the network capacity.
Impact
Prerequisite
l l
The inter-BSC link is configured and the communication is normal. Each BSC should be configured with at least two BTSs. In addition, the BTSs should support the soft-synchronized network. The BTSs must be configured with the same SiteSyncZone. Each BTS should be configured with at least two cells. In addition, the longitude, latitude, and antenna azimuth of each cell should be configured. The communication links between the BSCs are configured and work normally. For details, see Connection Inter BSC over IP.
l l
Issue 01 (2010-05-20)
44-7
Preparation
The following operation creates the soft-synchronized network task (Aiss Task Index = 0). Assume that this soft-synchronized network task is implemented between two BTSs. Table 44-4 Example of the data negotiated and planned for setting the BTS synchronization zone Parameter ID IDXTYPE BTSIDX SYMOFFSET SITESYNCZONE Parameter Name Index type BTS index SymOffset SiteSyncZone Example BYIDX(By Index) 1,2 0 0 Source Network planning Network planning Network planning Network planning
Assume that BTS 1 under the controlling BSC216 and BTS 2 under the collaborating BSC217 support soft-synchronized network. Table 44-5 Example of the data negotiated and planned for creating an inter-BSC softsynchronized network Data Type Controlli ng BSC216 paramet ers Parameter ID TASKIDX GATHON Parameter Name Aiss Task Index Offset Information Collection Switch Offset Time Adjustment Switch Reference BTS Index Reinitialize Neighboring Cell List Support BSC AISS Base BSC Example 0 ON(ON) Source Network planning Network planning
ADTON
ON(ON)
1 YES(YES)
ISSPTBSCAISS ISBASICBSC
YES(YES) YES(YES)
44-8
Issue 01 (2010-05-20)
Data Type Collabor ating BSC217 paramet ers
Parameter ID TASKIDX GATHON
Parameter Name Aiss Task Index Offset Information Collection Switch Offset Time Adjustment Switch Reference BTS Index Reinitialize Neighboring Cell List Support BSC AISS Base BSC Controlling BSC DPC
Example 0 ON(ON)
ADTON
ON(ON)
Network planning Network planning Network planning Network planning Network planning Network planning
2 YES(YES)
ISSPTBSCAISS ISBASICBSC CTRBSCDPC
YES(YES) NO h'a1
Table 44-6 Example of the data negotiated and planned for configuring the cell that creates the inter-BSC soft-synchronized network task Data Type 2G external cell configur ation Parameter ID CELLIDX CELLNAME MCC MNC LAC CI Parameter Name Cell Index Cell Name Cell MCC Cell MNC Cell LAC Cell CI Example 2048 D 460 01 8240 1 Source Network planning Network planning Network planning Network planning Network planning Network planning
Issue 01 (2010-05-20)
44-9
Data Type
Parameter ID BCCH NCC BCC
Parameter Name BCCH FD NCC BCC Index type Source Cell Index Neighbor Cell Index Current HO Control Algorithm in Source Cell Index type BSC inner Cell index Adjacent BSC DPC BSC adjacent Cell index
Example 988 1 1 BYIDX(By Index) 0 2048 HOALGORIT HM1
Source Network planning Network planning Network planning Network planning Network planning Network planning Network planning
2G unidirect ional neighbor ing cell configur ation
IDXTYPE SRCCELLIDX NBRCELLIDX HOCTRLSWITCH
Neighbo ring cell pair configur ation
IDXTYPE INNCELLIDX ADJBSCDPC EXTADJCELLIDX
BYIDX(By Index) 0 h'a3 2048
Procedure
Step 1 Run the SET BTSAISS command on the Local Maintenance Terminal. Set the same SiteSyncZone for the BTSs that participate in the inter-BSC soft-synchronized network task.
NOTE
Set the same SiteSyncZone for the BTSs numbered as 1 and 2. SymOffset is an optional parameter. This parameter determines the value of Frame Offset [frame No.], and should be set as required. In general, the default value is selected.
Step 2 On the Local Maintenance Terminal of the controlling BSC216, run the ADD AISSCFG command to create a soft-synchronized network task. Set Support BSC AISS and Base BSC to Yes. Step 3 On the Local Maintenance Terminal of the collaborating BSC217, run the ADD AISSCFG command to create a soft-synchronized network task. Set Base BSC to No, and specify Controlling BSC DPC.
NOTE
After the Offset Information Collection Switch and Offset Time Adjustment Switch are set to ON (ON), the BTS offset information are collected and the offset time are adjusted automatically to finish the soft-synchronized network task. To manually collect the offset information and adjust the offset time, see 44.7 Collecting the Offset Information Between BTSs and 44.8 Synchronizing BTSs.
Step 4 On the Local Maintenance Terminal of the controlling BSC216, run the ADD CELL2GEXTC command to add a 2G external cell.
NOTE
Configure cell D under the BSC217 as an external cell under the BSC216. Set Cell Index according to the configured cells.
Step 5 On the Local Maintenance Terminal of the controlling BSC216, run the ADD CELL2GNC command to add a 2G unidirectional neighboring cell and configure cell D as the neighboring cell of cell C. Step 6 On the Local Maintenance Terminal of the controlling BSC216, run the ADD EXTNCELL command to add a pair of neighboring cells, that is, to make cell C and cell D into a pair. Then, the task of creating the soft-synchronized network is complete. ----End
Example
An example script of creating an inter-BSC soft-synchronized network task is as follows:
/*Set the BTS synchronization zone*/ SET BTSAISS: IDXTYPE=BYIDX, BTSIDX=1, SYMOFFSET=0, SITESYNCZONE=0; SET BTSAISS: IDXTYPE=BYIDX, BTSIDX=2, SYMOFFSET=0, SITESYNCZONE=0; /*Create a soft-synchronized network task on the controlling BSC216*/ ADD AISSCFG: TASKIDX=0, GATHON=ON, ADTON=ON, BASEBTSIDX=1, REINITTBL=YES, ISSPTBSCAISS=YES, ISBASICBSC=YES; /*Create a soft-synchronized network task on the collaborating BSC217*/ ADD AISSCFG: TASKIDX=0, GATHON=ON, ADTON=ON, BASEBTSIDX=2, REINITTBL=YES, ISSPTBSCAISS=YES, ISBASICBSC=NO, CTRBSCDPC=h'a1; /*Add a 2G external cell*/ ADD CELL2GEXTC: CELLIDX=2048, CELLNAME="D", MCC="460", MNC="01", LAC=8240, CI=1, BCCH=988, NCC=1, BCC=3; /*Add a 2G unidirectional neighboring cell*/ ADD CELL2GNC: IDXTYPE=BYIDX, SRCCELLIDX=0, NBRCELLIDX=2048, HOCTRLSWITCH=HOALGORITHM1; /*Add a pair of neighboring cells*/ ADD EXTNCELL: IDXTYPE=BYIDX, INNCELLIDX=0, ADJBSCDPC=h'a3, EXTADJCELLIDX=2055;
44.6 Verifying an Inter-BSC Soft-Synchronized Network Task

This describes how to verify the inter-BSC soft-synchronized network task on the Local Maintenance Terminal.
Prerequisite
A soft-synchronized network task is created through the ADD AISSCFG command and the task supports inter-BSC soft-synchronized network.
Procedure
Step 1 On the Local Maintenance Terminal, run the LST AISSCFG command to query the information about the soft-synchronized network task. Ensure that Support BSC AISS is set to Yes on the controlling BSC and that the Controlling BSC DPC on the collaborating BSC is the DPC of the controlling BSC. Step 2 On the Local Maintenance Terminal, run the DSP AISSRUNSTATE command to query the information about the intra-BSC soft-synchronized network task and check whether the status of synchronization between the BTSs is normal. Step 3 On the Local Maintenance Terminal, run the DSP BSCSYNCINFO command to query the offset information about the synchronization between two BSCs.
NOTE
l l
The status of this BSC is queried if the entered Adjacent BSC DPC is the DPC of the controlling BSC of this BSC. The status of the collaborating BSC is queried if the entered Adjacent BSC DPC is the DPC of the collaborating BSC of this BSC.
Enter the Adjacent BSC DPC of the collaborating BSC to query the status of the collaborating BSC. At the initial stage of the task of creating the soft-synchronized network, the BSC Sync State should be Waiting for Initial Collection.
Step 4 On the Local Maintenance Terminal, run the DSP BTSSYNCINFO command to query the offset information about the BTS. At the initial stage of the task of creating the soft-synchronized network, BTS Status should be Waiting for Initial Collection. ----End
Example
An example script of verifying an inter-BSC soft-synchronized network task is as follows:
/*Query the information about the soft-synchronized network task*/ LST AISSCFG; /*Query the information about the inter-BSC soft-synchronized network task*/ DSP AISSRUNSTATE: TASKIDX=1; /*Query the offset information about the synchronization of the BSC*/ DSP BSCSYNCINFO: TASKIDX=1, BSCDPC=h'a17; /*Query the offset information about the synchronization of the BTS*/ DSP BTSSYNCINFO: TASKIDX=1, IDXTYPE=BYIDX, BTSIDX=0;
44.7 Collecting the Offset Information Between BTSs

This describes how to collect the offset information between BTSs on the Local Maintenance Terminal. Collecting the offset information between BTSs consists of collecting the intra-BSC and inter-BSC offset information between BTSs. The collected offset information provides a basis for adjusting the BTS clock.
Prerequisite
The inter-BSC or intra-BSC soft-synchronized network task is created successfully.
44-12
Issue 01 (2010-05-20)
Preparation
Table 44-7 Example of the data negotiated and planned for collecting the intra-BSC offset information between BTSs Data Type Offset informat ion collectio n Parameter ID TASKIDX GATHON Parameter Name Aiss Task Index Offset Information Collection Switch Offset Time Adjustment Switch Reference BTS Index Reinitialize Neighboring Cell List Support BSC AISS Reserve State Aiss Task Index Collection Type Cell Index Type First BTS Index Second BTS Index Example 0 ON(ON) Source Network planning Network planning
ADTON
ON(ON)
Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning
1 NO(NO)
ISSPTBSCAISS RESERVESTATE Frame offset and inframe bit offset collectio n TASKIDX COLTYPE CELLIDXTYPE SCELLIDX MCELLIDX
NO(NO) YES(YES) 0 BYSITE(By Site) BYIDX(By Index) 0 1
Issue 01 (2010-05-20)
44-13
Table 44-8 Example of the data negotiated and planned for collecting the inter-BSC offset information between BTSs Data Type Offset informat ion collectio n Parameter ID TASKIDX DPC Parameter Name Aiss Task Index BSC DPC Example 0 h'a3 Source Network planning Network planning
Procedure
l Collect the offset information about the BTSs in the BSC. 1. On the Local Maintenance Terminal, run the MOD AISSCFG command. Set Offset Time Adjustment Switch and Offset Information Collection Switch to ON(ON). Then, the BSC automatically starts to adjust the BTS time and collect the offset information. Optional: If the information collected in step 1 differs greatly from the drive test result, run the COL SYNCINFO command to recollect Frame Offset [frame No.] and In Frame Bit Offset [1/8 bit] of two BTSs or cells under the BSC.
NOTE
2.
The two BTSs or cells used in the command should be listed in the neighboring cell list. The status of the first BTS or cell must be collected or synchronized, and the second BTS or cell must be the BTS to be collected or the cell under the BTS.
Collect the inter-BSC offset information. 1. On the Local Maintenance Terminal, run the MOD AISSCFG command. Set Offset Time Adjustment Switch and Offset Information Collection Switch to ON(ON). Then, the BSC automatically starts to adjust the BTS time and collect the offset information. Optional: If the information collected in step 1 differs greatly from the drive test result, run the COL BSCSYNCINFO command and enter the DPC of the specified collaborating BSC to recollect Frame Offset [frame No.] and In Frame Bit Offset [1/8 bit] of the control BSC and collaborating BSC.
2.
----End
Example
An example script of collecting the intra-BSC offset information between BTSs is as follows:
/*Start the tasks of collecting the BTS offset information and adjusting the BTS offset time*/ MOD AISSCFG: TASKIDX=0, GATHON=ON, ADTON=ON, BASEBTSIDX=1, REINITTBL=NO, ISSPTBSCAISS=NO, ISBASICBSC=NO, RESERVESTATE=YES; /*Recollect the frame offset and in frame bit offset in the intra-BSC softsynchronized network*/ COL SYNCINFO: TASKIDX=0, COLTYPE=BYSITE, BTSIDXTYPE=BYIDX, SBTSIDX=0, MBTSIDX=1;
An example script of collecting the inter-BSC offset information between BTSs is as follows:
/*Start the tasks of collecting the BTS offset information and adjusting the BTS offset time*/
44-14
Issue 01 (2010-05-20)
MOD AISSCFG: TASKIDX=0, GATHON=ON, ADTON=ON, BASEBTSIDX=1, REINITTBL=NO, ISSPTBSCAISS=YES, ISBASICBSC=YES, RESERVESTATE=YES; /*Recollect the frame offset and in frame bit offset in the inter-BSC softsynchronized network*/ COL BSCSYNCINFO: TASKIDX=0, DPC=h'a3;
44.8 Synchronizing BTSs

After a soft-synchronized network task is created, the BTS offset information is collected and the offset time is adjusted automatically to synchronize the BTSs. If the drive test result shows that the offset between the synchronized BTSs is great, you can manually synchronize the BTSs on the Local Maintenance Terminal. This operation is optional as required. Impact During the BTS synchronization, call drops may occur. Therefore, you are advised to synchronize the BTSs when the traffic volume is low.
NOTE
Take BTS1 as the reference BTS and keep the frame number and offset of BTS1 unchanged. Then, adjust the frame number and offset of BTS2 according to the frame offset and in-frame bit offset of BTS2 relative to BTS1 to synchronize BTS2 with BTS1.
Preparation
Table 44-9 Example of the data negotiated and planned for synchronizing the BTSs Parameter ID TASKIDX IDXTYPE BTSIDX ADJMODE FRAMEOFFSET BITOFFSET Parameter Name Aiss Task Index Index type BTS index Adjustment Mode Frame Offset [frame No.] In Frame Bit Offset [1/8 bit] Example 0 BYIDX(By Index) 1 BYMANUAL(By Manual) 100 10 Source Network planning Network planning Network planning Network planning Network planning Network planning
Procedure
Step 1 On the Local Maintenance Terminal, run the MOD BTSEXCURSION command to manually synchronize the BTSs. Frame Offset [frame No.] and In Frame Bit Offset [1/8 bit] should correspond to the drive test result. ----End
Example
An example script of adjusting the frame offset and in-frame bit offset is as follows:
MOD BTSEXCURSION: TASKIDX=0, IDXTYPE=BYIDX, BTSIDX=1, ADJMODE=BYMANUAL, FRAMEOFFSET=100, BITOFFSET=10;
44.9 Deleting a Soft-Synchronized Network Task

This describes how to delete a soft-synchronized network task on the Local Maintenance Terminal.
Prerequisite
A soft-synchronized network task is created through the ADD AISSCFG command.
Preparation Procedure
Step 1 On the Local Maintenance Terminal, run the RMV AISSCFG command to delete a softsynchronized network task. Step 2 To delete an inter-BSC soft-synchronized network task, you should also delete the pair of interBSC neighboring cells through the RMV EXTNCELL command on the Local Maintenance Terminal. ----End
Example
An example script of deleting a soft-synchronized network task is as follows:
RMV AISSCFG: TASKIDX=1; /*Delete the pair of inter-BSC neighboring cells and the inter-BSC softsynchronized network task*/ RMV EXTNCELL: INDEX=0;
44-16
Issue 01 (2010-05-20)
45 Configuring Entire Network Synchronization
45
Scenario Impact
Configuring Entire Network Synchronization
This describes how to configure the DGPS in the BTS3012 or configure the USCU in the 3900 series base station or 3036 series base station to support the GPS function so that the entire network is synchronized. To synchronize the entire network through hardware configuration The conversion from an asynchronous network to a synchronous network can effectively reduce the interference on the entire network, expand the network capacity, and improve the gain of the radio-related KPIs.
Prerequisite
l l
The configuration of entire network is not restricted by the license. The BTS3012 should be configured with the DGPS;The BTS3900/BTS3900A/DBS3900 should be configured with the Universal Satellite card and Clock Unit (USCU). The communication between the BSC and the BTS is normal.
Preparation
Configure the DGPS in the BTS3012 or configure the USCU in the 3900 series base station or 3036 series base station to support the GPS entire network synchronization. Take configuration of the USCU in the BTS3900 GSM as an example. Table 45-1 Example of the data negotiated and planned for configuring the USCU Parameter ID IDXTYPE BTSIDX SRN
Issue 01 (2010-05-20)
Parameter Name Index Type BTS Index Subrack No.
Example BYIDX(By Index) 5 0

45-1
Parameter ID SN CNT BT GPSORGLONASS ANTENNALONG ANTENNAPOWER SWITCH
Parameter Name Slot No. Cabinet Type Board Type GPS or Glonass GPS Antenna Delay Antenna Power Supply Switch
Example 0 BTS3900_GSM USCU(USCU) GPS(GPS) 800 NOPOWER(No Power)
Table 45-2 Example of the data negotiated and planned for configuring the system clock source Parameter ID IDXTYPE BTSIDX CLKTYPE Parameter Name Index Type BTS Index Clock Type Example BYIDX(By Index) 5 TRCGPS_CLK (Trace GPS Clock) Source Network planning Network planning Network planning
Procedure
Step 1 On the Local Maintenance Terminal, run the ADD BTSBRD command to add the USCU. Step 2 On the Local Maintenance Terminal, run the MOD USCUBP command to set GPS or Glonass to GPS(GPS), GPS Antenna Delay to 800, and Antenna Power Supply Switch to NOPOWER(No Power).
NOTE
GPS or Glonass is set according to the type of the GPS satellite card. Antenna Power Supply Switch is set to NOPOWER(No Power) only in the co-antenna scenario. GPS Antenna Delay is set according to the feeder length.
Step 3 On the Local Maintenance Terminal, run the MOD BTSCLK command to set Clock Type to TRCGPS_CLK(Trace GPS Clock). ----End
Example
An example script is as follows:
/*Add a USCU*/ ADD BTSBRD: IDXTYPE=BYIDX, BTSIDX=5, SRN=0, SN=0, CNT=BTS3900_GSM, BT=USCU; /*Configure the USCU to support the GPS function*/ MOD USCUBP: IDXTYPE=BYIDX, BTSIDX=5, SRN=0, SN=0, GPSORGLONASS=GPS, ANTENNALONG=800, ANTENNAPOWERSWITCH=NOPOWER; /*Configure the system clock source*/ MOD BTSCLK: IDXTYPE=BYIDX, BTSIDX=5, ClkType=TRCGPS_CLK;
45-2
Issue 01 (2010-05-20)
Postrequisite
l
Verifying entire network synchronization
On the Local Maintenance Terminal, run the LST BTSCLK command. Check the setting of Clock Type of the BTS. If the parameter is set to TRCGPS_CLK(Trace GPS Clock), it indicates that the function of entire network synchronization is activated. On the Local Maintenance Terminal, run the MOD BTSCLK command to set Clock Type to a value other than TRCGPS_CLK(Trace GPS Clock). On the Local Maintenance Terminal, run the LST BTSCLK command to check the setting of Clock Type of the BTS. If the parameter is set to a value other than TRCGPS_CLK(Trace GPS Clock), it indicates that the function of entire network synchronization is deactivated.
Deactivating entire network synchronization 1. 2.
Issue 01 (2010-05-20)
45-3
46 Configuring BSS IP Transmission
46
Context
Configuring BSS IP Transmission
About This Chapter

This describes three types of IP transmission in the BSS: A over IP, Abis over IP, and Gb over IP. According to the network planning, different networking modes can be used on each interface in the BSS as required. The networking reliability can be guaranteed by the active/standby mode, load sharing, and link detection. Meanwhile, the quality of IP transmission can be guaranteed by various QoS mechanisms.
46.1 A over IP Configuration Data This provides the configuration data of the IP transmission over the A interface. 46.2 Abis over IP Configuration Data This provides the configuration data of the IP transmission over the Abis interface. 46.3 Gb over IP Configuration Data This provides the configuration data of the IP transmission over the Gb interface. 46.4 Configuring A over IP This describes how to configure A over IP on the Local Maintenance Terminal. 46.5 Configuring Abis over IP This describes how to configure Abis over IP on the Local Maintenance Terminal. 46.6 Configuring Gb over IP This describes how to configure Gb over IP on the Local Maintenance Terminal.
Issue 01 (2010-05-20)
46-1
46.1 A over IP Configuration Data

This provides the configuration data of the IP transmission over the A interface. Table 46-1 Example of the data negotiated and planned for configuring system clock Parameter ID SRCTYPE Parameter Name Clock Reference Source Type Example 2M_ExternalClk0 (2M_ExternalClk0) 2M_ExternalClk1 (2M_ExternalClk1) SRCSUBTYPE Clock Reference Source Sub-type Clock Reference Source Priority 2M_HZ 2M_Bps 1 2 Source Network planning Network planning Network planning Network planning Network planning Network planning
PRIORITY
Table 46-2 Example of the data negotiated and planned for configuring 8K reference clock for the GMPS and GEPS Parameter ID SRN Parameter Name Subrack No. Example 0 1 REFCLK clock type GGCU_BACK (GGCU Backplane) GGCU_BACK (GGCU Face) Source Network planning Network planning Network planning Network planning
Table 46-3 Example of the data negotiated and planned for configuring the M3AU entity Data Type M3UA local entity M3UA destination entity Parameter ID OPC DPC Parameter Name OPC Code DPC Code Example h'a1 h'cc Source Network planning Network planning
46-2
Issue 01 (2010-05-20)
Table 46-4 Example of the data negotiated and planned for configuring the signaling point for the GMPS Parameter Subrack No. OPC Code Example 0 h'a1 Source BSC internal planning Network planning
Table 46-5 Example of the data negotiated and planned for configuring the GFGUA Data Type BSC attributes Board attributes Parameter ID ServiceMod e SRN SN BT PORTTYPE BACKTYP E Parameter Name Service Mode Subrack No. Slot No. Board Type Port Type Back Type Example AIP(AIP) 0 14 GFGUA FE OUTPEER (Active/ Standby Mode) 0 ENABLE (ENABLE) 1000 DEVIP (Device IP address) 2.2.2.2 255.255.255. 0 0 Source Network planning Network planning Network planning Network planning Network planning Network planning
PN AN MTU IP attributes Communicat ion type Device IP address AIPTYPE
Port No. Auto Neg MTU A-interface Communicat ion IP type IP Address Subnet Mask Port No.
Network planning Network planning Network planning Network planning Network planning Network planning Network planning
IPADDR MASK
Port IP address
PORT
Issue 01 (2010-05-20)
46-3
Data Type
Parameter ID IPINDEX IPADDR MASK IPADDR2 BSC route IPADDR MASK GATEWAY
Parameter Name IP address index IP Address Subnet Mask Standby IP address IP Address Subnet Mask Gateway
Example 0 3.3.3.3 255.255.255. 0 3.3.3.4 5.5.5.0 255.255.255. 0 3.3.3.1
Table 46-6 Example of the data negotiated and planned for configuring the A interface link Parameter ID SIGLKSIDX DENO Parameter Name Signalling Link Set Index Adjacent Destination Entity No. Local Port No. Peer Port No. First Local IP Address Peer Address 1 Example 0 0 Source Network planning Network planning
LOCPN PEERPN LOCIP1 PEERIP1
4096 4096 2.2.2.2 5.5.5.5
Table 46-7 Example of the data negotiated and planned for configuring the BFD detection over the A interface Parameter ID IPINDEX PEERIP Parameter Name Local IP Index Peer IP Example 0 3.3.3.1 Source Network planning Network planning
46-4
Issue 01 (2010-05-20)
Parameter ID MINTXINTERVA L MINRXINTERVA L DETECTMULT
Parameter Name Minimum TX Interval[ms] Minimum RX Interval[ms] DetectMult
Example 30 30 3
Table 46-8 Example of the data negotiated and planned for configuring the QoS mechanism over the A interface Data Type Priority mapping Parameter ID SRN SN ITFTYPE TRMTYPE SRVTYPE VLANFLAG VLANID PHB DSCP VLANPRI Traffic shaping and congestion management SRN SN PN Parameter Name Subrack No. Slot No. InterfaceType TRM Type Service Type VLAN Flag VLAN ID PHB DSCP PRI Subrack No. Slot No. Port No. Example 0 14 A(A Interface) IP(IP) CSVOICE(CS Voice) ENABLE (Enable) 2 EF 0 7 0 14 0 Source Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning
Issue 01 (2010-05-20)
46-5
Data Type
Parameter ID WQDT DRPTYPE UPTHP
Parameter Name Queue Display Type Discarding Type Upper Discarding Threshold Congestion Threshold Restore Threshold Shaping Enable Shaping Bandwidth [32K]
Example PQ REJECT (REJECT) 3
CGTHP RSTHP SPENABLE SPBW
4 4 YES(Yes) 3200
46.2 Abis over IP Configuration Data

This provides the configuration data of the IP transmission over the Abis interface. Table 46-9 Example of the data negotiated and planned for configuring the GFGUB Data Type Board attributes Parameter ID SRN SN BT PORTTYPE BACKTYP E Parameter Name Subrack No. Slot No. Board Type Port Type Back Type Example 0 17 GFGUB FE OUTPEER (Active/ Standby Mode) 0 Source Network planning Network planning Network planning Network planning Network planning
PN
Port No.
Network planning
Issue 01 (2010-05-20)
46-6
Data Type
Parameter ID AN MTU
Parameter Name Auto Neg MTU Abisinterface Communicat ion IP type IP address Subnet mask Port No. IP address index IP address Subnet mask Standby IP address IP address Subnet mask Gateway IP address
Example ENABLE (ENABLE) 1000 DEVIP (Device IP address) 6.6.6.6 255.255.255. 0 0 0 8.8.8.3 255.255.255. 0 8.8.8.4 5.5.5.0 255.255.255. 0 8.8.8.1
IP attributes
Communicat ion type
ABISIPTYP E
Device IP address
IPADDR MASK
Port IP address
PORT IPINDEX IPADDR MASK IPADDR2
BSC route
IPADDR MASK GATEWAY
Table 46-10 Example of the data negotiated and planned for configuring the BFD link detection over the Abis interface Data Type BSC Parameter ID IPINDEX PEERIP Parameter Name Local IP Index Peer IP Example 0 8.8.8.3 Source Network planning Network planning
46-7
Issue 01 (2010-05-20)
Data Type
Parameter ID MINTXINTER VAL MINRXINTE RVAL DETECTMUL T
Parameter Name Minimum TX Interval[ms] Minimum RX Interval[ms] Detect Multiple BTSWTR Minimum TX Interval[ms] Minimum RX Interval[ms] Detect Multiple
Example 30 30 3 0 30 30 3
BTS
BTSWTR MINTXINTER VAL MINRXINTE RVAL DETECTMUL T
Table 46-11 Example of the data negotiated and planned for configuring Clock over IP Parameter ID IPINDEX SHPA SHPB SHPC SYNMODE Parameter Name Clock server IP ShakeHand period A[s] ShakeHand period B[s] ShakeHand period C[s] Clock Synchronization Mode Example 9.9.9.1 3 3 3 CONSYN (Consecutive Synchronizing) Source Network planning Network planning Network planning Network planning Network planning
Table 46-12 Example of the data negotiated and planned for configuring QoS for the Abis interface Data Type Priority mapping on the BSC side Parameter ID SRN Parameter Name Subrack No. Example 0 Source Network planning
46-8
Issue 01 (2010-05-20)
Data Type
Parameter ID SN ITFTYPE TRMTYPE SRVTYPE VLANFLAG VLANID PHB DSCP VLANPRI
Parameter Name Slot No. Interface Type TRM Type Service Type VLAN Flag VLAN ID PHB DSCP PRI Index Type BTS Index Service Type DSCP VLANSwitch VLAN ID PRI Subrack No. Slot No.
Example 17 Abis(Abis Interface) IP(IP) CSVOICE(CS Voice) ENABLE (Enable) 2 EF 0 7 BYIDX(By Index) 0 CSVOICE 0 YES ENABLE (Enable) 7 0 17
Priority mapping on the BTS side
IDXTYPE BTSIDX SERVICETYP E DSCP VLANSWITC H VLANID VLANPRI
Traffic shaping and congestion management
SRN SN
Issue 01 (2010-05-20)
46-9
Data Type
Parameter ID PN WQDT DRPTYPE UPTHP CGTHP RSTHP SPENABLE SPBW
Parameter Name Port No. Queue Display Type Drop Type Upper Limit Congestion Threshold Restore Threshold Shaping Enable Shaping Bandwidth [32K]
Example 0 PQ REJECT (REJECT) 3 4 4 YES(Yes) 3200
Table 46-13 Example of the data negotiated and planned for configuring IP PATH for the Abis interface Data Type Logical port Parameter ID PN LPN BANDWIDTH Parameter Name Logical Port No. Logical Port No. Bandwidth of the Logical Port [32kbps] Subrack No. Transport Resource Group No. Is First Class Transport Resource Group Example 0 0 10 Source Network planning Network planning Network planning
Resource group
SRN GRPID
0 0
ISFIRSTCLAS S
YES(Yes)
Network planning
46-10
Issue 01 (2010-05-20)
Data Type
Parameter ID LOCTRMBAN D
Parameter Name Local Class Transport Resource Bandwidth [kbps] IP Path ID Interface Type BTS Index IP Path Type Transport Resource Bandwidth [kbps] Carry Flag Logical Port No. LDR First
Example 10
IP PATH
PATHID INTTYPE BTSID PATHT TRMBAND
1 ABISINT(Abis Interface) 0 CS(CS) 10
CARRYFLAG LPN LDR attributes LDRFST
LOGPORT (Logical Port) 0 PSDOWN(PS Downspeeding)
Table 46-14 Example of the data negotiated and planned for configuring ABIS MUX Data Type BSC/BTS Parameter ID ABISMUXF LAG SRVTYPE Parameter Name ABIS-MUX Global Enable Flag Service Type Example ENABLE(Enable) Source Network planning
CSVOICE(CS Voice)
Network planning
Table 46-15 Example of the data negotiated and planned for configuring LAPD Parameter ID WINADJSWIT CH Parameter Name LAPD window adjust switch Example ALLOW(Allow) Source Network planning
Issue 01 (2010-05-20)
46-11
Table 46-16 Example of the data negotiated and planned for configuring IP PM Parameter ID BTSID DIRECTION Parameter Name BTS Index Direction Example 0 DOWN (DOWN)/UP (UP) CSVOICE (CS Voice) 1 Source BSC internal planning BSC internal planning BSC internal planning BSC internal planning
SERVICETYPE PMPRD
Service Type IPPM Packet Send Period[100ms]
Table 46-17 Example of the data negotiated and planned for setting the BTS Ping Switch to Off Parameter ID BTSPINGSWIT CH Parameter Name BTS Ping Switch Example OFF(Off) Source Network planning
46.3 Gb over IP Configuration Data

This provides the configuration data of the IP transmission over the Gb interface. Table 46-18 Example of the data negotiated and planned for configuring the GDPUP Parameter PCU Type Subrack No. Slot No. Board Type Back Type Example INNER(Inner PCU) 0 8 GDPUP NONE(Independent Mode) Source BSC internal planning BSC internal planning BSC internal planning BSC internal planning BSC internal planning
46-12
Issue 01 (2010-05-20)
Table 46-19 Example of the data negotiated and planned for configuring the GFGUG Data Type Board attributes Parameter ID SRN SN BT PORTTYPE BACKTYP E Parameter Name Subrack No. Slot No. Board Type Port Type Back Type Example 0 18 GFGUG FE OUTPEER (Active/ Standby Mode) 0 ENABLE (ENABLE) 1000 DEVIP (Device IP address) 12.12.12.12 255.255.255. 0 0 0 13.13.13.13 255.255.255. 0 13.13.13.4 15.15.15.0 Source Network planning Network planning Network planning Network planning Network planning
PN AN MTU IP attributes GBIPTYPE GBIPTYPE
Port No. Auto Neg MTU Gb-interface Communicat ion IP type IP address Subnet mask Port No. IP address index IP address Subnet mask Standby IP address IP address
Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning
Device IP address
IPADDR MASK
Port IP address
PORT IPINDEX IPADDR MASK IPADDR2
BSC route
IPADDR
Issue 01 (2010-05-20)
46-13
Data Type
Parameter ID MASK GATEWAY
Parameter Name Subnet mask Gateway IP address
Example 255.255.255. 0 13.13.13.1
Table 46-20 Example of the data negotiated and planned for configuring the SGSN Data Type SGSN node Parameter ID CNOPNAME CNID NSE NSEI SRN PT Local NSVL NSVLI IP UDPPN SIGLW SRVLW Remote NSVL NSVLI IP UDPPN SIGLW Parameter Name Operator Name SGSN Node ID NSE Identifier Agent Subrack No. Subnetwork Protocol Type Local NSVL Identifier IP Address UDP Port No. Signaling Load Weight Traffic Load Weight Remote NSVL Identifier IP Address UDP Port No. Signaling Load Weight Example 46000 1 1 0 GB_OVER_IP (Gb over IP) 0 12.12.12.12 5000 100 100 1 15.15.15.15 5555 100 Source BSC internal planning Negotiating with the peer end Negotiating with the peer end BSC internal planning Negotiating with the peer end Negotiating with the peer end Negotiating with the peer end Negotiating with the peer end Negotiating with the peer end Negotiating with the peer end Negotiating with the peer end Negotiating with the peer end Negotiating with the peer end Negotiating with the peer end
46-14
Issue 01 (2010-05-20)
Data Type
Parameter ID Traffic Load Weight
Parameter Name Traffic Load Weight PTPBVC Identifier Index Type Cell Name
Example 100 2 BYCELLNAME (By Cell Name) CELL_1
Source Negotiating with the peer end BSC internal planning BSC internal planning BSC internal planning
PTPBVC
BVCI IDXTYPE CELLNAME
Table 46-21 Example of the data negotiated and planned for configuring the BFD link detection over the Gb interface Parameter ID IPINDEX PEERIP MINTXINTERVA L MINRXINTERVA L DETECTMULT Parameter Name Local IP Index Peer IP Minimum TX Interval[ms] Minimum RX Interval[ms] DetectMult Example 0 13.13.13.1 30 30 3 Source Network planning Network planning Network planning Network planning Network planning
Table 46-22 Example of the data negotiated and planned for configuring traffic shaping over the Gb interface and congestion management Parameter ID SRN SN PN WQDT DRPTYPE UPTHP CGTHP Parameter Name Subrack No. Slot No. Port No. Queue Display Type Discarding Type Upper Discarding Threshold Congestion Threshold Example 0 18 0 PQ REJECT(REJECT) 3 4 Source Network planning Network planning Network planning Network planning Network planning Network planning Network planning
Issue 01 (2010-05-20)
46-15
Parameter ID RSTHP SPENABLE SPBW
Parameter Name Restore Threshold Shaping Enable Shaping Bandwidth [32K]
Example 4 YES(Yes) 3200
46.4 Configuring A over IP

This describes how to configure A over IP on the Local Maintenance Terminal. Scenario Impact The A over IP is used for signaling and CS signals transmission in the BSS system. None.
NEs Involved BTS, BSC, MSC, MGW When the IP transmission is used over the A interface, the functions of the GTCS are implemented by the MGW and the BSC does not perform transcoding. The compressed speech coding scheme is still used, and thus the transmission bandwidth is reduced on the A interface. When an MS calls another MS in the network, secondary speech coding/decoding can be avoided if the calling party and called party use the same speech coding scheme. Thus, the speech quality is enhanced and the resources are saved.
Prerequisite
l l
Configure the A over IP that is restricted by the license. Activate the license on the Local Maintenance Terminal. For details, see Activate BSC License. The BSC supports communication through the device IP address or port IP address. When the device IP address is used for communication, the peer device should be configured with the static route to the IP address of the BSC even if the BSC is directly connected to the peer device. When the port IP address is used for communication, the static route is not required. The A/Abis interface board can be configured with only one device IP address. The Gb interface board can be configured with up to five device IP addresses. The Abis over IP supports only IPv4. When the BSC is directly connected to the MSC or MGW or the network is in Layer 2 topology, the BSC should be configured with the route to the peer device even if the IP address of the MSC or MGW is on the same network segment with the port IP address of the BSC. When the A interface is directly connected to the BSC, the BSC must be configured with the route to the MGW.
l l
Preparation
Except for different configuration parameters between the GFGUA and GOGUA, the procedures for configuring the GFGUA and GOGUA are the same. The following procedure is an example
of configuring the GFGUAs in active/standby mode in the GMPS subrack. For the configuration data, see 46.1 A over IP Configuration Data.
Procedure
Step 1 Configure BSC attributes. On the Local Maintenance Terminal, run the MOD BSCBASIC command and set Service mode to AIP(AIP). Step 2 Configure the BSC clock.
NOTE
In A over IP mode, the clock source of the BSC can be only a BITS clock. The BITS clock is obtained from the BITS device. It is classified into the 2 MHz clock and 2 Mbit/s clock. It has two input modes: BITS0 and BITS1. The BSC obtains the BITS clock from the input port of synchronous clock signals on the GGCU to provide the reference clock for the GMPS/GEPS.
1. 2. 3. 1. 2.
On the Local Maintenance Terminal, run the ADD CLKSRC command to configure the system clock. Run the MOD SCUCLK command and configure the 8 kHz reference clock for the GMPS. Run the MOD SCUCLK command and configure the 8 kHz reference clock for the GEPS. On the Local Maintenance Terminal, run the ADD M3LE command to configure the local entity. Run the ADD M3DE to configure the destination entity.
NOTE
Step 3 Configure the M3UA entities.
If there is no direct physical link between the local entity and the destination entity, the transfer entity must be configured. When configuring the destination entity, you need to set Using STP to YES (Yes).
3.
Run the ADD M3STE command to configure the transfer entity.
Step 4 Configure subrack-OPC mapping. On the Local Maintenance Terminal, run the ADD SROPCMAP command to configure the subrack-OPC mapping. Step 5 Configure the GFGUA/GOGUA. 1. On the Local Maintenance Terminal, run the ADD BRD command to add the GFGUA. Set Back Type to OUTSHARE(LoadShare Mode) or OUTPEER(Active/Standby Mode) to enhance the networking reliability. Run the SET ETHPORTPROP command and set Port Type to configure the port attribute of the GFGUA.
NOTE
2.
l l l
If the FE transmission is used, one GFGUA can be configured with eight ports numbered from zero to seven. If the GE transmission is used, one GFGUA can be configured with two ports numbered zero and four. If the GE transmission is used, one GOGUA can be configured with two ports numbered zero and one.
3.
Run the SET ITFIPTYPE command and set A-interface Communication IP type. If the communication type is PORTIP(PORT IP), go to Step 5.5.
Issue 01 (2010-05-20)
4.
Run the ADD DEVIP command to configure the device IP address.

NOTE
The device IP address is the logical IP address used for communication. The address is valid for all the ports on the board. The active and standby interface boards must be configured with the same IP address.
5.
Run the ADD PHYPORTIP command to configure the port IP address.

NOTE
The following two methods implement the separation between signaling and traffic data over the A interface on the bearer network.
l l
The signaling and traffic data are mapped to different VPNs through different ports to implement their separation on the bearer network. Configure several IP address index, that is, several IP addresses are configured to each port. Different IP addresses are mapped to different VPNs, thus implementing the separation between signaling and traffic data on the bearer network. The IP address of the port and that of the device must be on different network segments. Each port can be configured with six IP addresses and all IP addresses of each port must be configured on different network segments. In active/standby mode, the IP addresses of related ports must be configured on the same network segment. In load sharing mode, if the BSC performs communication through device IP addresses, then the two boards for load sharing must use the same device IP address. Regardless of whether device IP addresses or port IP addresses are used for communication, port IP addresses must be on different network segments.
The principles of configuring the port IP address are as follows:

l l l
6.
Run the ADD IPRT command and configure the BSC route.
NOTE
The principles of configuring the BSC route are as follows:

l l l
Destination IP Address should be set as the destination network address but not a single IP address. Gateway IP Address should be on the same network segment as the port IP address of the GFGUA. If the active and standby GFGUAs are configured, add a BSC route after their port IP addresses are configured.
Step 6 Configure a link over the A interface. 1. 2. 3. On the Local Maintenance Terminal, run the ADD M3LKS command to configure the M3UA link set. Run the ADD M3RT command to configure the M3UA route.. Run the ADD M3LNK command and configure the M3UA link to achieve the configuration of the IP transmission over the A interface.
46-18
Issue 01 (2010-05-20)
NOTE
When the device IP mode is used over the A interface, the M3UA link can be configured only when the device IP address is configured. In addition, First Local IP Address is the device IP address of the interface board, and Second Local IP Address is optional. But if the SCTP multihoming function is required, Second Local IP Address must be set to the device IP address, and First Local IP Address and Second Local IP Address must be on different network segments. When the port IP mode is used over the A interface, the M3UA link can be configured only when the device IP address is configured. In addition, First Local IP Address can be selected from the list of port IP addresses of the interface boards, and Second Local IP Address is optional. But if the SCTP multi-homing function is required, Second Local IP Address must be set to the port IP address, and First Local IP Address and Second Local IP Address must be on different network segments.
Step 7 Configure the reliability mechanism of the A interface.

NOTE
The networking reliability can be guaranteed by configuring the back type over the A interface. Besides, the system must detect the fault when the link or the board is faulty to prevent the services from disruption. The BFD (Bidirectional Forwarding Detection) and ARP (Address Resolution Protocol) are used for link detection. When one GFGUA or GOGUA board is configured in the BSC (independent mode), the BFD and ARP function are not enabled because the board itself can automatically detect faults to guarantee the networking reliability. One physical port supports only one type of link detection. Configure the BFD or ARP according to the capability of the equipment at both ends and the requirement of networking reliability.
1.
For the configuration of the BFD detection over the A interface, the BFD session is setup only when two ends of the link support the BFD and the parameters at two ends are consistent. Run the ADD BFD command to configure the BFD detection on the BSC side.
NOTE
If Back Type of the BSC is set to OUTPEER(Active/Standby Mode) and the standby board enables the BFD or ARP detection, Peer Standby Board IP need to be configured. The principles of configuring the BFD detection are as follows:
l l
Port No. must be the number of the port that is configured with an IP address. Peer IP must be different from the device IP address and the port IP address.
2.
Configure the ARP detection on the BSC side. Run the ADD ARPDETECT command and configure the attributes of the ARP detection.
Step 8 Configure the QoS mechanism of the A interface. 1. Configure the traffic shaping for the physical port to restrict the burst flow in the network. Run the SET QOSPROP command. Set Shaping Enable to YES(Yes) and set Shaping BandWidth[32K] to specify the data rate. 2. Configure the priority mapping.
NOTE
The BSC maps the data onto different Differentiated Services Code Points (DSCPs) or different VLAN priorities and VLAN IDs. The network device of layer three maps different DSCPs to different Per-Hop Behaviors (PHBs); the network device of layer two performs QoS scheduling based on the VLAN priority.
Issue 01 (2010-05-20)
46-19

l
Run the SET DSCPMAP command to configure the mapping between the DSCP and the VLAN priority. Run the ADD IPVLANMAP command to configure the mapping between the IP and the VLAN. The Destination IP Address and the port IP address must be on the same network segment. Run the SET SRVVLANMAP command and set VLAN ID, PHB, and DSCP related to the service type over the A interface to achieve their mapping. You should configure the mapping between DSCP and VLAN priority to implement the mapping between the service priorities at the network layer and the service priorities at the data link layer. If VLAN Flag is set to ENABLE(Enable), the QoS scheduling is performed according to the VLAN priority. Otherwise, the QoS scheduling is performed according to the DSCP.
3.
Congestion management. Congestion occurs when the data arrive at the port at a higher rate than the data sending rate of the port. The Priority Queue (PQ) and Weighted Round Robin (WRR) techniques of queue scheduling can be used to solve the congestion problem. Run the SET QOSPROP command and set Queue Display Type to REJECT or Weighted Random Early Detection (WRED) to manage the congestion.
----End
Example
Configure the IP transmission over the A interface. The example script of configuring the GFGUA in active/standby mode and configuring the device communication type and the BFD detection.
/*Set the service mode*/ MOD BSCBASIC: ServiceMode=AIP; /*Set the system clock*/ ADD CLKSRC: SRCTYPE=2M_ExternalClk0, SRCSUBTYPE=2M_HZ, PRIORITY=1; ADD CLKSRC: SRCTYPE=2M_ExternalClk1, SRCSUBTYPE=2M_Bps, PRIORITY=2; / *Set the 8 kHz reference clock for the GMPS*/ MOD SCUCLK: SRN=0, RefClk=GGCU_BACK; / *Set the 8 kHz reference clock for the GEPS*/ MOD SCUCLK: SRN=1, RefClk=GGCU_FACE; /*Add the M3UA local entity*/ ADD M3LE: NAME="m3le_1", OPC=h'a1, RTCONTEXT=1; /*Add the M3UA destination entity*/ ADD M3DE: DENO=0, NAME="m3de_1", DPC=h'cc, RTCONTEXT=1, SSN=254, CNID=0; /*Add subrack-OPC mapping*/ ADD SROPCMAP: SRN=0, OPC=h'a1; /*Add the GFGUA*/ ADD BRD: SRN=0, SN=14, BT=GFGUA, PortType=FE, BackType=OUTPEER; / *Set the attribute of an Ethernet port*/ SET ETHPORTPROP: SRN=0, SN=14, BT=GFGUA, PT=FE, PN=0, AN=ENABLE, MTU=1000; /*Set the IP communication over the A interface*/ SET ITFIPTYPE: AIPTYPE=DEVIP; / *Add the device IP address*/ ADD DEVIP: SRN=0, SN=14, IPADDR="2.2.2.2", MASK="255.255.255.0"; /*Add the Ethernet port IP address*/ ADD PHYPORTIP: SRN=0, SN=14, PORT=0, IPINDEX=0, IPADDR="3.3.3.3", MASK="255.255.255.0", IPADDR2="3.3.3.4"; /*Add a BSC route*/ ADD IPRT: SRN=0, SN=14, IPADDR="5.5.5.0", MASK="255.255.255.0", GATEWAY="3.3.3.1"; /*Add the M3UA link set*/ ADD M3LKS: SIGLKSIDX=0, NAME="m3linkset_1", DENO=0; /*Add the M3UA route*/ ADD M3RT: DENO=0, SIGLKSIDX=0; /*Add the M3UA link*/ ADD M3LNK: SIGLKSIDX=0, SRN=0, LOCPN=4096, PEERPN=4096, LOCIP1="2.2.2.2", PEERIP1="5.5.5.5"; /*Add the BFD*/ ADD BFD: SRN=0, SN=14, PN=0, IPINDEX=0, PEERIP="3.3.3.1", MINTXINTERVAL=30, MINRXINTERVAL=30, DETECTMULT=3; /*Configure the QoS attributes of a port*/ /*Configure the traffic Shaping for a
46-20
Issue 01 (2010-05-20)
physical port*/ SET QOSPROP: SRN=0, SN=14, PN=0, SPENABLE=YES, SPBW=3200; /*Priority mapping*/ /*Configure the mapping between the DSCP and the VLAN priority*/ SET DSCPMAP: SRN=0, SN=14, DSCP=0, VLANPRI=7; /*Configure the mapping between the IP address and the VLAN priority*/ ADD IPVLANMAP: SRN=0, SN=14, DSTIPADDR="3.3.3.5", VLANID=2; /*Configure the mapping of the service type, DSCP, and VLAN ID*/ SET SRVVLANMAP: ITFTYPE=A, TRMTYPE=IP, SRVTYPE=CSVOICE, VLANFLAG=ENABLE, VLANID=2, PHB=EF, DSCP=0; /*Perform the congestion management with priority queue (PQ)*/ SET QOSPROP: SRN=0, SN=14, PN=0, WQDT=PQ, DRPTYPE=REJECT, UPTHP=3, CGTHP=4, RSTHP=4;
Postrequisite
l
Verifying A over IP 1. 2. Verify that the physical links on the A interface is normal. For details, see Verifying the Physical Links on the A Interface (A over IP) in the BSC Commissioning Guide. Verify that the control plane on the A interface is normal. For details, see Verifying the Control Plane on the A Interface (A over IP) in the BSC Commissioning Guide.
46.5 Configuring Abis over IP

This describes how to configure Abis over IP on the Local Maintenance Terminal. Scenario Impact The Abis over IP is used for signaling and CS signals transmission in the BSS system. None.
NEs Involved BTS, BSC, MSC, MGW, and SGSN
Prerequisite
l l
Configure the Abis over IP that is restricted by the license. Activate the license on the Local Maintenance Terminal. For details, see Activate BSC License. The BSC supports communication through the device IP address or port IP address. When the device IP address is used for communication, the peer device should be configured with the static route to the IP address of the BSC even if the BSC is directly connected to the peer device. When the port IP address is used for communication, the static route is not required. The A/Abis interface board can be configured with only one device IP address. The Gb interface board can be configured with up to five device IP addresses. The BFD is supported by only 3012 series base stations. It is not supported by 3900 series base stations. The Abis over IP supports only the built-in PCU and BTS star topology. It does not support the HubBTS and TDM/IP hybrid transport. The Abis over IP supports only IPv4. For a layer 2 topology in Abis over IP, the BSC and BTS directly start BFD to perform link detection. In this scenario, the BTS cannot use the device IP address for communication.
l l
l l
Issue 01 (2010-05-20)
Preparation
Except for different configuration parameters between the GFGUB and GOGUB, the procedures for configuring the GFGUB and GOGUB are the same. The following procedure is an example of configuring two GFGUBs in the GMPS subrack. For the configuration data, see 46.2 Abis over IP Configuration Data.
Procedure
Step 1 Configure BSC attributes. On the Local Maintenance Terminal, run the SET ITFIPTYPE command to set Abisinterface Communication IP type. Step 2 Configure the GFGUB/GOGUB. 1. On the Local Maintenance Terminal, run the ADD BRD command to add the GFGUB. Set Back Type to OUTSHARE(LoadShare Mode) or OUTPEER(Active/Standby Mode) to enhance the networking reliability. Run the SET ETHPORTPROP command and set Port Type to configure the port attribute of the GFGUB.
NOTE
2.
l l l
If the FE transmission is used, one GFGUB can be configured with eight ports numbered from zero to seven. If the GE transmission is used, one GFGUB can be configured with two ports numbered zero and four. If the GE transmission is used, one GOGUB can be configured with two ports numbered zero and one.
3. 4.
Run the SET ITFIPTYPE command and set Abis-interface Communication IP type. If the communication type is PORTIP(PORT IP), go to Step 2.5. Run the ADD DEVIP command to configure the device IP address.
NOTE
The device IP address is the logical IP address used for communication. The address is valid for all the ports on the board. The active and standby interface boards must be configured with the same IP address.
5.

NOTE

l l l
The IP address of the port and that of the device must be on different network segments. Each port can be configured with six IP addresses and all IP addresses of each port must be configured on different network segments. In active/standby mode, the IP addresses of related ports must be configured on the same network segment. In load sharing mode, if the BSC performs communication through device IP addresses, then the two boards for load sharing must use the same device IP address. Regardless of whether device IP addresses or port IP addresses are used for communication, port IP addresses must be on different network segments.
6.
Run the ADD IPRT command and configure the BSC route.
46-22
Issue 01 (2010-05-20)
NOTE

l l l
Destination IP Address should be set as the destination the network address but not a single IP address. Gateway IP Address should be on the same network segment as the port IP address of the GFGUB. In the case of active and standby boards, add a BSC route after their port IP addresses are configured.
Step 3 Configure the reliability mechanism for the Abis interface.

NOTE
The reliability of the Abis over IP networking is the same as that of the A over IP. For details, see the Configure the reliability mechanism for the A interface. in the 46.4 Configuring A over IP.
1.
The BFD detection over the Abis interface requires the support of the BTS and BSC. On the BTS side, set parameters corresponding to the BSC. When the parameters of both sides are consistent, the BFD session can be established. a. b. Run the ADD BFD command and configure the BFD link detection on the BSC side. Run the ADD BTSBFD command and configure the BFD link detection on the BTS side.
NOTE
When the BSC enables the OUTPEER(Active/Standby Mode) networking mode and the BFD or ARP link detection is enabled on the standby board, set Peer Standby Board IP. The principles of configuring the BFD link detection are as follows:
l l
Port No. must be the number of the port that is configured with an IP address. Peer IP must be different from the device IP address and the port IP address.
2.
Configure the ARP detection on the BSC side. Run the ADD ARPDETECT command and configure the attributes of the ARP link detection.
Step 4 Configure the Clock Over IP and configure the clock synchronization information of the IP transmission network. Run the MOD IPCLKSRV command. Set Clock Synchronization Mode to CONSYN (Consecutive Synchronizing) or INTERSYN(Intermittent Synchronizing) to configure the synchronization mode between IP Clock Server and IP Clock Client. The IP Clock Server obtains the clock source from other devices and sends the clock synchronization messages to the BTS (IP Clock Client) through the IP network.
l
In consecutive synchronizing mode, the BTS works as the Client of Clock over IP to send datagram continuously for clock synchronization. In intermittent synchronizing mode, the BTS works as the Client of Clock over IP and keep the clock synchronization with the Server according to Interim Synchronization Period [Day], Interval Synchronization Start Time[Hour], and Interval Synchronization Start Time[Minute]. Configure the traffic shaping for the physical port to restrict the burst flow in the network. Run the SET QOSPROP command. Set Shaping Enable to YES(Yes) and set Shaping BandWidth[32K] to specify the data rate.
Step 5 Configure the QoS mechanism of the Abis interface. 1.
Issue 01 (2010-05-20)
46-23
2.
Configure the priority mapping.

NOTE
The BSC maps the data onto different Differentiated Services Code Points (DSCPs) or different VLAN priorities and VLAN IDs. The network device of layer three maps different DSCPs to different Per-Hop Behaviors (PHBs); the network device of layer two performs QoS scheduling based on the VLAN priority.
l
Run the SET DSCPMAP command to configure the mapping between the DSCP and the VLAN priority. Run the ADD IPVLANMAP command to configure the mapping between the IP and the VLAN. The Destination IP Address and the port IP address must be on the same network segment. Run the SET SRVVLANMAP command and set VLAN ID, PHB, and DSCP related to the service type over the A interface to achieve their mapping. You should configure the mapping between DSCP and VLAN priority to implement the mapping between the service priorities at the network layer and the service priorities at the data link layer. If VLAN Flag is set to ENABLE(Enable), the QoS scheduling depends on the VLAN priority. Otherwise, the QoS scheduling depends on the DSCP. Run the MOD BTSVLAN command and perform the service schedule in the transmission network according to different DSCP, VLANID, VLANPRI of different Service Type. The services and signaling can be logically separated according to VLANID, thus enhancing the security of the network. The parameters must be consistent with those on the BSC side.
3.
Configure the congestion management. Congestion occurs when the data arrive at the port at a higher rate than the data sending rate of the port. The Priority Queue (PQ) and Weighted Round Robin (WRR) techniques of queue scheduling can be used to solve the congestion problem. Run the SET QOSPROP command and set Queue Display Type to REJECT or Weighted Random Early Detection (WRED) to manage the congestion.
Step 6 Configure the IP PATH over the Abis interface.

NOTE
The IP PATH is a logical link with virtual bandwidth, which is carried on the physical port, logical port, or resource groups to achieve multi-level admission control. The admission control for the MS is based on the following parameters: Local Class Transport Resource Bandwidth[kbps], Reserved Bandwidth Threshold[%], Congestion Bandwidth Threshold[%], and Congestion Clear Bandwidth Threshold [%].
1.
Configure the logical port or resource group.

l
When the IP PATH is carried on the logical port, run the ADD LOGICALPORT command to implement several logical ports with logical bandwidth on one physical port. Several BTSs can share the port bandwidth on the physical port to guarantee proper bandwidth for each BTS.
NOTE
l l
One Logical Port No. is configured for one BSC board and Physical Port No. specifies the physical port carried by the logical port. Set Reserved Bandwidth Threshold[%] > Congestion Bandwidth Threshold[%] > Congestion Clear Bandwidth Threshold[%] to implement two-level admission control. That is, the services must be controlled when the services access through the IP PATH and logical port.
46-24
Issue 01 (2010-05-20)
l
If the bandwidth of the intermediate transmission network restricts the access of services, you are advised to set the IP PATH to be carried on the resource groups. Run the ADD RSCGRP command to configure the resource groups.
NOTE
If Is First Class Transport Resource Group is set to NO(No), Upper Class Transport Resource Group No. must be identified to perform multi-level admission control. The group number of the upper class transport resource must be different from that of the lower class transport resource. A maximum of five levels can be configured for the transport resource group. When multi-level resource group is configured, the upper-level transport resource bandwidth cannot be higher than the local-level transport resource bandwidth. Set Local Class Transport Resource Bandwidth[kbps] and set Reserved Bandwidth Threshold[%]>Congestion Bandwidth Threshold[%]>Congestion Clear Bandwidth Threshold[%] to configure the bandwidth and threshold of resource groups. Then, two-level admission control can be implemented. That is, the services must be controlled when the services access through the IP PATH and logical port.
l l l
2.
Run the ADD IPPATH command to configure the IP PATH.

NOTE
l l
The IP path ID must be unique in one BSC. IP PATH Type consists of CS, PS, and QoS (carries both CS and PS). Each BTS can be configured with multiple IP paths for carrying various services. If IP Path Type is set to CS or PS, each BTS can be configured with one CS IP path or one PS IP path. If IP Path Type is set to QoS, each BTS can be configured with one QoS IP path. Set Transport Resource Bandwidth[kbps] to allocate the bandwidth. Reserved Bandwidth Threshold[%]>Congestion Bandwidth Threshold[%]>Congestion Clear Bandwidth Threshold[%]. The entered BTS Index must exist. In addition, the IP BTS must connect the GFGUB/GOGUB in the BSC. If Carry Flag is set to LOGPORT(Logical Port), the physical port that corresponds to the logical port must be the port on the board on the BSC side, and one IP path can correspond to only one logical port, but one logical port can correspond to multiple IP paths.
l l
3.
Configure the congestion management. Run the SET LDR command and set from LDR First to LDR Fourth to achieve the dynamic TCHF-TCHH conversion of the CS services and the downspeeding of the PS services. To reduce the speed of the accessed services during the congestion control and bandwidth reserve can improve the system capacity.
Step 7 Configure the Abis MUX on the BSC and BTS.

NOTE
The Abis MUX technology is used to multiplex several packets into one packet. Then, the efficiency of the IP transmission over the Abis interface is improved. The packets with the same attributes can be multiplexed. That is, only the packets that have the same source IP addresses, destination IP address, and DSCP value can be multiplexed into one packet.
1. 2.
Run the SET BSCABISMUXPARA command and set ABIS-MUX Global Enable Flag to ENABLE(Enable). Run the ADD BSCABISMUXFLOW command and set Service Type for the BTS. Then the packets with the same source IP addresses, destination IP address, and service type can be multiplexed and the peer end can correctly demultiplex. Set MUX Sub Frame Threshold, MUX Packet Length Threshold, and Time Out[0.1ms] to configure the multiplexing mode.
Issue 01 (2010-05-20)
3. 4.
Run the MOD PTUPARA command and set ABIS-MUX Global Enable Flag to ENABLE(Enable). Run the ADD BTSABISMUXFLOW command and configure the parameters corresponding to those on the BSC side.
Step 8 Configure the LAPD optimization.

NOTE
The impacts of configuring the LAPD optimization are as follows:

l l
The QoS tolerance of the LAPD link is enhanced and the call drop rate due to poor quality of the link is reduced. Thus, the network KPIs are improved. The flow retransmission is decreased and the utilization of the bandwidth is improved.
Run the SET OTHSOFTPARA command and set LAPD window adjust switch to ALLOW (Allow) to start the LAPD optimization. Step 9 Configure the IP Performance Monitor (IP PM).
NOTE
The IP PM monitors the transmission network by rapidly detecting the QoS of the intermediate network. This function requires the support of the BTS and BSC. Set BTS Index to specify a BTS detected by the IP PM. When an IP PM session is activated, the sending end sends the FM message periodically and then determines the packet loss based on the BR message received from the receiving end. The length of the period is determined by IPPM Packet Send Period[100ms].
l l
Run the ADD IPPM command and set Direction to DOWN. Then, perform the IP PM function from the BSC to the BTS. Run the ADD IPPM command and set Direction to UP. Then, perform the IP PM function from the BTS to the BSC.
Step 10 Set BTS Ping Switch to Off.

NOTE
If the external device frequently pings the BTS, the BTS responds to the ping requests. The BTS may break down if it is pinged a lot. This is called ping attack, which belongs to DOS attack.
Run the MOD PTUPARA command. If BTS Ping Switch is set to ON(On), the BTS receives all ping packets; if the parameter is set to OFF(Off), the BTS discards all ping packets. ----End
Example
Configure the IP transmission over the Abis interface. The example script of configuring the GFGUB in active/standby mode and configuring the device communication type and the BFD detection.
/*Add the GFGUB*/ ADD BRD: SRN=0, SN=17, BT=GFGUB, PortType=FE, BackType=OUTPEER; / *Set the attribute of an Ethernet port*/ SET ETHPORTPROP: SRN=0, SN=17, BT=GFGUB, PT=FE, PN=0, AN=ENABLE, MTU=1000; /*Set the IP communication type over the Abis interface*/ SET ITFIPTYPE: AIPTYPE=DEVIP; /*Add the device IP address*/ ADD DEVIP: SRN=0, SN=17, IPADDR="6.6.6.6", MASK="255.255.255.0"; /*Add the Port IP address*/ ADD PHYPORTIP: SRN=0, SN=17, PORT=0, IPINDEX=0, IPADDR="8.8.8.3", MASK="255.255.255.0", IPADDR2="8.8.8.4"; /*Add the BSC route*/ ADD IPRT: SRN=0, SN=17, IPADDR="5.5.5.0", MASK="255.255.255.0", GATEWAY="8.8.8.1"; /*Add the BFD*/ ADD BFD: SRN=0, SN=17, PN=0, IPINDEX=0, PEERIP="8.8.8.3",
46-26
Issue 01 (2010-05-20)
MINTXINTERVAL=30, MINRXINTERVAL=30, DETECTMULT=3; ADD BTSBFD: IDXTYPE=BYIDX, BTSIDX=0, BTSWTR=0, MINTXINTERVAL=30, MINRXINTERVAL=30, DETECTMULT=3; /*Configure the Clock Over IP*/ MOD IPCLKSRV: CLOSERIP="9.9.9.1", SHPA=3, SHPB=3, SHPC=3, SYNMODE=CONSYN; /*Configure the QoS attribute of a port*/ /*Configure the traffic shaping for a physical port*/ SET QOSPROP: SRN=0, SN=17, PN=0, SPENABLE=YES, SPBW=3200; /*Priority mapping*/ /*Configure the mapping between the DSCP and the VLAN priority*/ SET DSCPMAP: SRN=0, SN=17, DSCP=0, VLANPRI=7; /*Configure the mapping between the IP address and the VLAN priority*/ ADD IPVLANMAP: SRN=0, SN=17, DSTIPADDR="8.8.8.5", VLANID=2; /*Configure the mapping of the service type, DSCP, and VLANID*/ SET SRVVLANMAP: ITFTYPE=Abis, TRMTYPE=IP, SRVTYPE=CSVOICE, VLANFLAG=ENABLE, VLANID=2, PHB=EF, DSCP=0; /*Configure the mapping of the service type on the BTS side, DSCP, and VLANID*/ MOD BTSVLAN: IDXTYPE=BYIDX, BTSIDX=0, SERVICETYPE=CSVOICE, DSCP=0, VLANSWITCH=YES, VLANID=2, VLANPRI=7; /*Perform the congestion management with priority queue (PQ)*/ SET QOSPROP: SRN=0, SN=17, PN=0, WQDT=PQ, DRPTYPE=REJECT, UPTHP=3, CGTHP=4, RSTHP=4; /*Configure the IP PATH over the Abis interface*/ /*Configure the logical port*/ ADD LOGICALPORT: SRN=0, SLOTNO=17, PN=0, LPN=0, BANDWIDTH=10; /*Configure the resource group*/ ADD RSCGRP: SRN=0, GRPID=0, ISFIRSTCLASS=YES, LOCTRMBAND=10; / *Configure the IP PATH*/ ADD IPPATH: PATHID=1, INTTYPE=ABISINT, BTSID=0, PATHT=CS, TRMBAND=10, CARRYFLAG=LOGPORT, LPN=0; /*Configure the congestion management*/ SET LDR: LDRFST=PSDOWN; /*Configure the Abis MUX*/ /*Set ABIS-MUX Global Enable Flag of the interface board on the BSC side to Enable*/ SET BSCABISMUXPARA: SRN=0, SN=17, ABISMUXFLAG=ENABLE; / *Add the data record of the Abis MUX on the BSC side and set the service type to CS Voice*/ ADD BSCABISMUXFLOW: SRN=0, SN=17, IDXTYPE=BYNAME, BTSNAME="BTS3012", SRVTYPE=CSVOICE; /*Set ABIS-MUX Global Enable Flag of the interface board on the BTS side to Enable*/ MOD PTUPARA: IDXTYPE=BYNAME, BTSNAME="BTS3012", ABISMUXFLAG=ENABLE; /*Add the data record of the Abis MUX on the BTS side and set the service type to CS Voice*/ ADD BTSABISMUXFLOW: IDXTYPE=BYNAME, BTSNAME="BTS3012", SRVTYPE=CSVOICE; /*Configure the LAPD optimization*/ SET OTHSOFTPARA: WINADJSWITCH=ALLOW; /*Configure the IP PM*/ ADD IPPM: BTSID=0, DIRECTION=DOWN, SERVICETYPE=CSVOICE, PMPRD=1; ADD IPPM: BTSID=0, DIRECTION=UP, SERVICETYPE=CSVOICE, PMPRD=1; /*Configure BTS Ping Switch to Off*/ MOD PTUPARA: IDXTYPE=BYIDX, BTSIDX=0, BTSPINGSWITCH=OFF;
Postrequisite
l
Verifying Abis over IP 1. Verify that the physical links on the Abis interface is normal. For details, see Verifying the Physical Links on the Abis Interface (Abis over IP) in the BSC Commissioning Guide. Verify that the control plane on the A interface is normal. For details, see Verifying the Control Plane on the Abis Interface (Abis over IP) in the BSC Commissioning Guide.
2.
46.6 Configuring Gb over IP

This describes how to configure Gb over IP on the Local Maintenance Terminal. Scenario The Gb over IP is used for signaling and PS signals transmission in the BSS system.
Issue 01 (2010-05-20)
Impact
None.
NEs Involved BTS, BSC and SGSN
Prerequisite
l l l l
The built-in PCU is configured. An empty slot for configuring the GFGUG is in the subrack. Configure the Gb over IP that is restricted by the license. Activate the license on the Local Maintenance Terminal. For details, see Activate BSC License. The BSC supports communication through the device IP address or port IP address. When the device IP address is used for communication, the peer device should be configured with the static route to the IP address of the BSC even if the BSC is directly connected to the peer device. When the port IP address is used for communication, the static route is not required. The A/Abis interface board can be configured with only one device IP address. The Gb interface board can be configured with up to five device IP addresses. The BFD is supported by only 3012 series base stations. It is not supported by 3900 series base stations.
l l
Preparation
For the GFGUG configuration data, see 46.3 Gb over IP Configuration Data.
Procedure
Step 1 Configure the GDPUP. 1. 2. On the Local Maintenance Terminal, run the SET PCUTYPE command to set PCU Type to INNER(Inner PCU). Run the ADD BRD command to add a GDPUP.
Step 2 Configure the GFGUG. 1. On the Local Maintenance Terminal, run the ADD BRD command to add a GFGUG. Set Back Type to OUTPEER(Active/Standby Mode) to enhance the networking reliability. Run the SET ETHPORTPROP command and set Port Type to configure the port attributes of the GFGUG.
NOTE
2.
l l
If the FE transmission is used, one GFGUG can be configured with eight ports numbered from zero to seven. If the GE transmission is used, one GFGUG can be configured with two ports numbered zero and four.
3. 4.
46-28
Run the SET ITFIPTYPE command and set Gb-interface Communication IP type. If the communication type is PORTIP(PORT IP), go to Step 2.5. Run the ADD DEVIP to configure the device IP address.
NOTE
The device IP address is the logical IP address used for communication. The address is valid for all the ports on the board.
5.

NOTE

l l l
The IP address of the port and that of the device must be on different network segments. Each port can be configured with six IP addresses and all IP addresses of each port must be configured on different network segments. In active/standby mode, the IP addresses of related ports must be configured on the same network segment.
6.
Run the ADD IPRT command and configure the BSC route..
NOTE

l l l
Destination IP Address should be set as the destination the network address but not a single IP address. Gateway IP Address must be on the same network segment as the port IP address of the GFGUG. In the case of active and standby boards, add a BSC route after their port IP addresses are configured.
Step 3 Configure Gb over IP. 1. 2. 3. 4. 5. On the Local Maintenance Terminal, run the ADD SGSNNODE command to configure the SGSN. Run the ADD NSE command to configure the NSE. Run the ADD NSVLLOCAL command to configure local NSVL. Run the ADD NSVLREMOTE command to configure remote NSVL. Run the ADD PTPBVC command to configure the PTPBVC.
Step 4 The networking reliability configuration of Gb over IP is the same as that of A over IP. For details, see the Configure the reliability mechanism of the A interface. in the 46.4 Configuring A over IP. Step 5 The QoS mechanism configuration of the Gb interface is the same as that of the A interface. For details, see the Configure the QoS mechanism of the A interface. in the 46.4 Configuring A over IP.
NOTE
The Gb interface does not support the VLAN priority mapping.
----End
Example
Configure the IP transmission over the Gb interface. The example script of configuring the GFGUG in active/standby mode and configuring the device communication type and the BFD detection.
/*Configure the built-in PCU*/ SET PCUTYPE: TYPE=INNER; /*Configure the built-in PCU and the GDPUP*/ ADD BRD: SRN=0, SN=8, BT=GDPUP,
Issue 01 (2010-05-20)
46-29

BackType=NONE;
/*Add the GFGUG*/ ADD BRD: SRN=0, SN=18, BT=GFGUG, PortType=FE, BackType=OUTPEER; /*Set the Ethernet port attribute*/ SET ETHPORTPROP: SRN=0, SN=18, BT=GFGUG, PT=FE, PN=0, AN=ENABLE, MTU=1000; /*Set the IP communication type over the Gb interface*/ SET ITFIPTYPE: GBIPTYPE=DEVIP; /*Add the device IP address*/ ADD DEVIP: SRN=0, SN=18, IPADDR="12.12.12.12", MASK="255.255.255.0"; /*Add the Port IP address*/ ADD PHYPORTIP: SRN=0, SN=18, PORT=0, IPINDEX=0, IPADDR="13.13.13.13", MASK="255.255.255.0", IPADDR2="13.13.13.4"; /*Add the BSC route*/ ADD IPRT: SRN=0, SN=18, IPADDR="15.15.15.0", MASK="255.255.255.0", GATEWAY="13.13.13.1"; /*Configure Gb over IP*/ ADD SGSNNODE: CnOpName="46000", CNId=1; ADD NSE: NSEI=1, SRN=0, PT=GB_OVER_IP, ISNCMODE=STATIC, CnOpName="46000", CNId=1; ADD NSVLLOCAL: NSVLI=0, NSEI=1, IP="12.12.12.12", UDPPN=5000, SRN=0, SN=18, SIGLW=100, SRVLW=100; ADD NSVLREMOTE: NSVLI=1, NSEI=1, IP="15.15.15.15", UDPPN=5555, SIGLW=100, SRVLW=100; ADD PTPBVC: NSEI=1, BVCI=2, IDXTYPE=BYCELLNAME, CELLNAME="CELL_1"; /*Add the BFD*/ ADD BFD: SRN=0, SN=18, PN=0, IPINDEX=0, PEERIP="13.13.13.1", MINTXINTERVAL=30, MINRXINTERVAL=30, DETECTMULT=3; /*Configure the QoS attribute of a port*/ /*Configure traffic shaping for a physical port*/ SET QOSPROP: SRN=0, SN=18, PN=0, SPENABLE=YES, SPBW=3200; /*Perform congestion management with priority queue (PQ)*/ SET QOSPROP: SRN=0, SN=18, PN=0, WQDT=PQ, DRPTYPE=REJECT, UPTHP=3, CGTHP=4, RSTHP=4;
Postrequisite
l
Verifying Gb over IP 1. 2. 3. 4. Verify that the NSVLs are available. For details, see Verifying the NSVL in the BSC Commissioning Guide. Verify that the IP routes on the Gb interface are normal. For details, see Verifying the IP Routes on the Gb Interface in the BSC Commissioning Guide. Verify that the SIG BVCs are available. For details, see Verifying the SIGBVC in the BSC Commissioning Guide. Verify that the PTP BVCs are available. For details, see Verifying the PTPBVC in the BSC Commissioning Guide.
46-30
Issue 01 (2010-05-20)
47 Configuring Abis Transmission Optimization or HubBTS
47
Scenario Impact
Configuring Abis Transmission Optimization or HubBTS
The Abis Transmission Optimization feature introduces the HDLC frame and HDLC channel without changing the physical transmission mode. It statistically multiplexes the traffic data, signaling data, and OM data on the HDLC channel to obtain a higher transmission gain through voice frame compression and multiplexing. The utilization of the transmission resources are improved. None.

NOTE
Based on the Abis transmission optimization, the HubBTS function can be implemented by installing a DPTU in the BTS. The HubBTS converges and forwards data.
Prerequisite
l l
The Abis Transmission Optimization or HubBTS function is license-controlled. Activate the license on the Local Maintenance Terminal. For details, see Activate BSC License. In HubBTS mode, the DPTU must be configured in the BTS. The BSC supports the Abis transmission optimization or HubBTS in E1/T1 or STM-1 transmission mode. The GEHUB is configured. The GMPS/GEPS holding the GEHUB is configured with the GDPUX. This feature should be supported by the BTS. The Abis Transmission Optimization or HubBTS function cannot be enabled at the same time as the Flex Abis or BTS local switching function.
l l
l l l l
Preparation
The difference between the HubBTS and the Abis transmission optimization lies in the transmission mode. The transmission mode of the HubBTS is HDLC_HubBTS, whereas the transmission mode of the Abis transmission optimization is HDLC.
The following is an example of configuring HDLC_HubBTS service mode on the GEHUB of the GEPS subrack for BTS3012. Table 47-1 Example of the data negotiated and planned for configuring HDLC_HubBTS service mode for BTS3012 Parameter ID BTSNAME TYPE UPNODE SRN SN PN BTSDESC MPMODE FlexAbisMode AbisByPassMode ServiceMode DCELLNAME DCTYPE DCMCC DCMNC DCLAC DCCI Parameter Name BTS name BTS Type Up Node Type Subrack No. Slot No. Port No. BTS Description Multiplexing Mode Flex Abis Mode Abis By Pass Mode Service Type Cell Name Cell Type Cell MCC Cell MNC Cell LAC Cell CI Example BTS3012 BTS3012 BSC 0 26 0 BTS3012_Hub MODE4_1 Fix Abis(Fix Abis) FALSE(Not Support) HDLC_HubBTS HDLC_HubBTS_CE LL GSM900 460 01 8240 1 Source Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning
Issue 01 (2010-05-20)
47-2
Parameter ID CPLMode TRXBN FREQ
Parameter Name Separate Mode TRX Board No. TRX Freq.
Example UNSUPPORT(Not Support) 0 988
NOTE
The HubBTS and the Abis transmission optimization are different in the configuration of the service mode. The service mode of the HubBTS is HDLC_HubBTS, and that of Abis transmission optimization is HDLC.
Procedure
Step 1 On the Local Maintenance Terminal, run the ADD BTS command and set the Service Type to HDLC_HubBTS.
NOTE
The HDLC_HubBTS does not support the ring topology, bypass, and FLEX_ABIS; while the HDLC does not support bypass and FLEX_ABIS.
----End
Result Example
An example script of configuring Abis transmission optimization or HubBTS is as follows:
/*Add an OPC*/ ADD OPC: NAME="BSC001", OPC=h'aa, NETSTRUCT=BIT14, NI=NATB; /*Add a DPC*/ ADD N7DPC: NAME="MSC001", DPC=h'cc, DPCGIDX=1, CNID=0; /*Add Subrack-OPC Mapping*/ ADD SROPCMAP: SRN=0, OPC=h'aa; /*Add a GXPUM, GXPUT and a GDPUX*/ ADD BRD: SRN=0, SN=0, BT=GXPUM, BackType=NONE; ADD BRD: SRN=0, SN=2, BT=GXPUT, BackType=NONE; ADD BRD: SRN=0, SN=8, BT=GDPUX, BackType=NONE; /*Add a GEHUB*/ ADD BRD: SRN=0, SN=26, BT=GEHUB, WorkMode=E1, BackType = OUTPEER; /*Add a BTS3012 in HDLC_HubBTS service mode*/ ADD BTS: BTSNAME = "BTS3012", TYPE = BTS3012, UPNODE = BSC, SRN=0, SN=26, PN=0, BTSDESC = "BTS3012_Hub", MPMODE=MODE4_1, FlexAbisMode = FIX_ABIS, AbisByPassMode = False, ServiceMode = HDLC_HubBTS, DCELLNAME = "HDLC_HubBTS_CELL", DCTYPE = GSM900, DCMCC="460", DCMNC="01", DCLAC=8240, DCCI=1, CPLMode=UNSUPPORT, TRXBN=0, FREQ=988;
Issue 01 (2010-05-20)
47-3
Postrequisite
l
Verifying Abis transmission optimization or HubBTS
On the Local Maintenance Terminal, run the LST BTS command. Check the setting of Service Type. If the parameter is set to HDLC_HubBTS, it indicates that the function of Abis transmission optimization or HubBTS is activated. On the Local Maintenance Terminal, run the MOD BTSSRVMODE command to set Service Type to TDM or IP. On the Local Maintenance Terminal, run the LST BTS command. Check the setting of Service Type. If the parameter is set to TDM or IP, it indicates that the function of Abis transmission optimization or HubBTS is deactivated.
Deactivating Abis Transmission optimization or HubBTS 1. 2.
47-4
Issue 01 (2010-05-20)
48 Configuring SGSN Pool
48
Scenario Impact None. NEs Involved BSC and SGSN
Configuring SGSN Pool
This feature enables a maximum of 32 SGSNs to form a resource pool to provide services for the subscribers belonging to one group of BSCs. With this feature, one BSC can be connected to multiple SGSNs at the same time. In addition, the traffic on the BSC is evenly distributed to the SGSNs in the pool according to the network resource identifier (NRI) or load balancing principle. PS services are evenly distributed among SGSNs in the SGSN pool.
Prerequisite
l l
The communication between the BSC and the SGSN is normal. SGSN pool should be supported by the SGSN.
Preparation
This operation takes the minimum configuration of an SGSN pool as an example. A cell named CELL_1 is served by two SGSNs and the telecom operator is named 46000. Table 48-1 Example of the data negotiated and planned for configuring SGSN pool Data Type SGSN pool switch Parameter ID CnOpName POOLALLOW NRILEN Parameter Name Operator Name Allow SGSN Pool NRI length Example 46000 ALLOW(Allow) 3 Source Network planning Network planning Network planning
Issue 01 (2010-05-20)
48-1
Data Type
Parameter ID NULLNRI
Parameter Name NullNRI Value
Example 4
Table 48-2 Example of the data negotiated and planned for adding the first SGSN Data Type Attributes of SGSN 0 Parameter ID CnOpName CNId Mapping between the NRI and SGSN 0 NRI CnOpName CNId Mapping between the NSE and SGSN 0 NSEI SRN PT CnOpName CNId Mapping between CELL_1 and SGSN 0 NSEI BVCI IDXTYPE CELLNAME Parameter Name Operator Name SGSN Node ID NRI Value Operator Name SGSN Node ID NSE Identifier Agent Subrack No. Subnetwork Protocol Type Operator Name SGSN Node ID NSE Identifier PTPBVC Identifier Index Type Cell Name Example 46000 0 3 46000 0 10 0 GB_OVER_FR (Gb over FR) 46000 0 10 2 BYCELLNAME CELL_1 Source Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning
48-2
Issue 01 (2010-05-20)
Table 48-3 Example of the data negotiated and planned for adding the second SGSN Data Type Attributes of SGSN 1 Parameter ID CnOpName CNId Mapping between the NRI and SGSN 1 NRI CnOpName CNId Mapping between the NSE and SGSN 1 NSEI SRN PT CnOpName CNId Mapping between CELL_1 and SGSN 1 NSEI BVCI IDXTYPE CELLNAME Parameter Name Operator Name SGSN Node ID NRI Value Operator Name SGSN Node ID NSE Identifier Agent Subrack No. Subnetwork Protocol Type Operator Name SGSN Node ID NSE Identifier PTPBVC Identifier Index Type Cell Name Example 46000 1 4 46000 1 23 0 GB_OVER_FR (Gb over FR) 46000 1 23 3 BYCELLNAME CELL_1 Source Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning
Procedure
Step 1 On the Local Maintenance Terminal, run the SET SGSNPOOL command. Set Allow SGSN Pool to ALLOW(Allow). The values of NRI length and NullNRI Value should be the same as that on the SGSN through negotiation. Step 2 On the Local Maintenance Terminal, run the ADD SGSNNODE. Set Operator Name and the SGSN node ID to add an SGSN.
Issue 01 (2010-05-20)
48-3
Step 3 On the Local Maintenance Terminal, run the ADD NRISGSNMAP command to configure the mapping between the NRI and the SGSN.
NOTE
The value of NRI Value should be the same as that on the SGSN through negotiation. The values of Operator Name and SGSN Node ID should be the same as those set for the SGSN added in step 2.
Step 4 On the Local Maintenance Terminal, run the ADD NSE command. Set NSE Identifier to add the NSE to the new SGSN.
NOTE
Set SGSN Node ID to the value of that set for the SGSN added in step 2.The settings of other parameters should be consistent with the settings on the SGSN.
Step 5 On the Local Maintenance Terminal, run the ADD PTPBVC command. Set the corresponding NSE identifier. The configuration of the first SGSN that serves CELL_1 is complete. Step 6 Repeat steps 2 through 5 to add the second SGSN to complete the configuration of the second SGSN that serves CELL_1. ----End
Example
Example scripts of configuring SGSN pool are as follows:
/*Enable the SGSN pool function*/ SET SGSNPOOL: CnOpName="46000", POOLALLOW=ALLOW, NRILEN=3, NULLNRI=4; /*Add an SGSN with the SGSN node ID as 0*/ ADD SGSNNODE: CnOpName="46000", CNId=0; /*Configure the mapping between the NRI and SGSN 0*/ ADD NRISGSNMAP: NRI=3, CnOpName="46000", CNId=0; /*Add the NSE with the NSE identifier as 10 to SGSN 0*/ ADD NSE: NSEI=10, SRN=0, PT=GB_OVER_FR, CnOpName="46000", CNId=0; /*Add a PTPBVC to configure the mapping between CELL_1 and SGSN 0*/ ADD PTPBVC: NSEI=10, BVCI=2, IDXTYPE=BYCELLNAME, CELLNAME="CELL_1"; /*Add an SGSN with the SGSN node ID as 1*/ ADD SGSNNODE: CnOpName="46000", CNId=1; /*Configure the mapping between the NRI and SGSN 1*/ ADD NRISGSNMAP: NRI=4, CnOpName="46000", CNId=1; /*Add the NSE with the NSE identifier as 23 to SGSN 1*/ ADD NSE: NSEI=23, SRN=0, PT=GB_OVER_FR, CnOpName="46000", CNId=1; /*Add a PTPBVC to configure the mapping between CELL_1 and SGSN 1*/ ADD PTPBVC: NSEI=23, BVCI=3, IDXTYPE=BYCELLNAME, CELLNAME="CELL_1";
Postrequisite
l
Verifying SGSN pool 1. 2. On the Local Maintenance Terminal, run the DSP PTPBVC command to view and record the PTP BVCs in the normal state. Check whether the FLOW CONTROL messages on all the PTP BVCs in the normal state are sent from the BSC to the SGSN by referring to Tracing PTP Messages on the Gb Interface. If so, it indicates that the SGSN pool function is normally enabled.
Deactivating SGSN pool 1. On the Local Maintenance Terminal, run the SET SGSNPOOL command to set Allow SGSN Pool to DENY(deny).
48-4
2.
On the Local Maintenance Terminal, run the LST SGSNPOOL command. Check the setting of Allow SGSN Pool. If the parameter is set to DENY(deny), it indicates that the transmit diversity is deactivated.
Issue 01 (2010-05-20)
48-5
49 Configuring RAN Sharing
49
About This Chapter
Prerequisite
l l
Configuring RAN Sharing
On the condition that independency of CNs of multiple operators is maintained, RAN Sharing enables multiple operators to share one GBSS network so that they can use the resources (including the BSC, BTS, antenna system, transmission, and so on) in the GBSS network simultaneously. RAN Sharing supports a maximum of four operators. Each operator has an independent CN (MSC and SGSN). The shared GBSS uses a uniform network management system, which implements comprehensive management of all the resources in the GBSS.
The RAN sharing function is license-controlled. Activate the license on the Local Maintenance Terminal. For details, see Activate BSC License. In RAN sharing mode, a maximum of four operators (including a primary operator) are supported. In RAN sharing mode, a maximum of four CBCs are supported. The operators must use the same networking mode (BM/TC separated, BM/TC combined, or A over IP). In addition, they must use the same transmission mode (TDM or IP) over the A interface. The MSCs of different operators must use the same SS7 signaling link rate type.
l l
49.1 Configuring Operator Information This describes how to configure the operator information on the Local Maintenance Terminal. 49.2 Configuring BTS Sharing This describes how to configure BTS sharing on the Local Maintenance Terminal. 49.3 Binding the Cell and the Operator This describes how to bind the cell and operator on the Local Maintenance Terminal. 49.4 Binding the MSC and Operator This describes how to bind the MSC and operator on the Local Maintenance Terminal. 49.5 Binding the SGSN and Operator
This describes how to bind the SGSN and operator on the Local Maintenance Terminal. 49.6 Binding the PCU and Operator This describes how to bind the PCU and operator on the Local Maintenance Terminal. 49.7 Configuring RAN Sharing to Support Multiple CBCs This describes how to configure multiple CBCs on the Local Maintenance Terminal. 49.8 Configuring the Distributed BTS TRX to Support RAN Sharing This describes how to configure the distributed BTS TRX to support the RAN sharing function on the Local Maintenance Terminal. 49.9 Verifying and Deactivating RAN Sharing This describes how to verify and deactivate RAN sharing on the Local Maintenance Terminal.
49-2
Issue 01 (2010-05-20)
49.1 Configuring Operator Information

This describes how to configure the operator information on the Local Maintenance Terminal.
Prerequisite
l l l
The BSC supports the RAN sharing function. The GDPUC or GDPUX is already configured. In RAN sharing mode, a maximum of four operators (including a primary operator) are supported. In RAN sharing mode, the operators are classified into the following types: Primary operator and Secondary operator. There is only one primary operator. Others are secondary operators.
Preparation
Table 49-1 Example of the data negotiated and planned for configuring the primary operator information Parameter ID OPNAME SPTRANSHARING HOBTWNOTHOP ALLOW Parameter Name Master Operator Name Support Sharing Handover Between Operators Allow Example Master YES(YES) YES(YES) Source Network planning Network planning Network planning
Table 49-2 Example of the data negotiated and planned for configuring the secondary operator information Parameter ID OPNAME MCC MNC SPPRTCB Parameter Name Accessorial Operator Name MCC MNC Support Cell Broadcast Handover Between Operators Allow Example coop1 460 14 SPPRTSTANDARD (SupportStandard CB) YES(YES) Source Network planning Network planning Network planning Network planning
HOBTWNOTHOP ALLOW
Network planning
Issue 01 (2010-05-20)
49-3
Procedure
Step 1 On the Local Maintenance Terminal, run the LST BSCBASIC command to check whether Support Sharing and Handover Between Operators Allow are set to YES(YES). If they are set to No, go to step 2.
NOTE
l l
The secondary operator can be added only when Support Sharing is set to YES(YES). Handover Between Operators Allow can be changed from YES(YES) to NO(NO) only when no neighboring cell relations in this BSC are affected by this parameter.
Step 2 On the Local Maintenance Terminal, run the MOD BSCBASIC command to configure the primary operator information. Set Master Operator Name, Support Sharing, and Handover Between Operators Allow as required. Step 3 On the Local Maintenance Terminal, run the ADD COOPBASIC command to configure the secondary operator information as required. ----End
Example
/*Configure primary operator information*/ MOD BSCBASIC: OPNAME="Master", SptRanSharing=YES, HoBtwnOthOpAllow=YES; /*Add the secondary operator*/ ADD COOPBASIC: OPNAME="coop1", MCC="460", MNC="14", SpprtCB=SPPRTSTANDARD, HOBTWNOTHOPALLOW=YES;
49.2 Configuring BTS Sharing

This describes how to configure BTS sharing on the Local Maintenance Terminal.
Prerequisite
l l
Support Sharing is set to YES(YES). The configured 3012 series base stations or 3900 series base stations support the RAN sharing function.
Preparation
Table 49-3 Example of the data negotiated and planned for configuring BTS sharing Parameter ID IDXTYPE BTSIDX SHARINGALLOW Parameter Name Index Type BTS Index Sharing Allow Example BYIDX(By Index) 0 YES(YES) Source Network planning Network planning Network planning
49-4
Issue 01 (2010-05-20)
Procedure
Step 1 On the Local Maintenance Terminal, run the LST BTSSHARING command to check whether Sharing Allow is set to YES(YES). If the value is NO(NO), go to the next step. Step 2 On the Local Maintenance Terminal, run the MOD BTSSHARING command to set Sharing Allow to YES(YES).
NOTE
Sharing Allow can be changed from YES(YES) to NO(NO) only when the cells under the BTS belong to the primary operator.
----End
Example
Take DBS3900 GSM as an example. The script for configuring the BTS sharing is as follows:
/*Query the BTS sharing configuration*/ LST BTSSHARING: IDXTYPE=BYIDX, BTSIDX=0; /*Configure the BTS sharing parameters*/ MOD BTSSHARING: IDXTYPE=BYIDX, BTSIDX=0, SHARINGALLOW=YES;
49.3 Binding the Cell and the Operator

This describes how to bind the cell and operator on the Local Maintenance Terminal.
Prerequisite
l l
Support Sharing is set to YES(YES). Sharing Allow is set to YES(YES).
Preparation
Table 49-4 Example of the data negotiated and planned for binding the cell and operator Parameter ID IDXTYPE IDXTYPE CELLIDX OPNAME Parameter Name Cell Index Type Cell Index Type Cell Index Operator Name Example BYALL(By All) BYIDX(By Index) 1 coop1 Source Network planning Network planning Network planning Network planning
Procedure
Step 1 On the Local Maintenance Terminal, run the LST OPCELL command to check whether the operator and cell are already bound. If they are not, go to the next step. Step 2 On the Local Maintenance Terminal, run the SET OPCELL command to bind the cell and operator.
CAUTION
l l l
Handover Between Operators Allow is set to YES(YES). The operator is the primary operator by default when a new cell is added. If neighboring cell relations exist in the configured cell, verify that the new operator allows neighboring cell relations. The cells configured with enhanced dual-band network must belong to the same operator. If the PTPBVC is already configured, the NSE must correspond to the operator when you change the operator of a cell. The BSC is shared by at least two operators. The parameter Handover Between Operators Allow is set to Yes for the secondary operator.
l l
----End
Example
An example script for binding the cell and operator is as follows:
/*Query the relation between the operator and cell*/ LST OPCELL: IDXTYPE=BYALL; /*Bind the cell and operator*/ SET OPCELL:IDXTYPE=BYIDX, CELLIDX=1, OPNAME="coop1";
49.4 Binding the MSC and Operator

This describes how to bind the MSC and operator on the Local Maintenance Terminal.
Prerequisite
l l
Support Sharing is set to YES(YES). The SS7 signaling point or M3UA destination entity are correctly configured.
Preparation
Table 49-5 Example of the data negotiated and planned for binding the MSC and operator Parameter ID IDXTYPE DPC OPNAME Parameter Name Index Type DPC Code Operator Name Example BYDPC(By DPC) h'cc coop1 Source Network planning Network planning Network planning
Procedure
Step 1 On the Local Maintenance Terminal, run the SET OPMSC command to bind the DPC and operator.
NOTE
When you run the ADD N7DPC command to add the DPC or run the ADD M3DE command to add the M3UA entity, the DPC and M3UA are configured for the primary operator by default. If you bind the MSC and secondary operator, you must run the SET OPMSC command. The SET OPMSC command can bind only the destination entity with the subsystem numbered 254 rather than 143.
----End
Example
/*Bind the MSC and operator*/ SET OPMSC: IDXTYPE=BYDPC, DPC=h'cc, OPNAME="coop1";
49.5 Binding the SGSN and Operator

This describes how to bind the SGSN and operator on the Local Maintenance Terminal.
Prerequisite
l l
Support Sharing is set to YES(YES). PCU Type is set to Inner.
Preparation
Parameter ID CNOPNAME CNID Parameter Name Operator Name SGSN Node ID Example coop1 0 Source Network planning Network planning
Procedure
Step 1 On the Local Maintenance Terminal, run the ADD SGSNNODE command to bind the SGSN and operator. ----End
Example
/*Bind the SGSN and operator*/ ADD SGSNNODE: CnOpName="coop1", CNId=0;
49.6 Binding the PCU and Operator

This describes how to bind the PCU and operator on the Local Maintenance Terminal.
Prerequisite
l l
Support Sharing is set to YES(YES). PCU Type is set to Outer.
Preparation
Table 49-6 Example of the data negotiated and planned for binding the PCU and operator Parameter ID IDXTYPE NAME OPNAME Parameter Name Index Type PCU Name Operator Name Example BYNAME (By PCU Name) pcu1 coop1 Source Network planning Network planning Network planning
Procedure
Step 1 On the Local Maintenance Terminal, run the ADD SGSNNODE command to bind the PCU and operator. ----End
Example
Suppose the name of the secondary operator is "coop 1" and that of the external PCU is "pcu1". An example script is as follows:
/*Bind the PCU and operator*/ SET OPMSC: IDXTYPE=BYNAME, NAME="pcu1", OPNAME="coop1";
49.7 Configuring RAN Sharing to Support Multiple CBCs

This describes how to configure multiple CBCs on the Local Maintenance Terminal.
Prerequisite
l l l
Support Sharing is set to YES(YES). The BSC supports the standard cell broadcast. The operator supports the standard cell broadcast.
49-8
Issue 01 (2010-05-20)
Preparation
Table 49-7 Example of the data negotiated and planned for configuring RAN sharing to support multiple CBCs Parameter ID IDXTYPE OPNAME SPPRTCB CBCNAME CBCIP CBCPRT OPNAME Parameter Name Index Type Accessorial Operator Name Support Cell Broadcast CBC Name CBC IP CBC port Owned Operator Example BYNAME (By Name) coop1 SPPRTSTANDARD (SupportStandard CB) cbc1 5.5.5.5 0 coop1 Source Network planning Network planning Network planning Network planning Network planning Network planning Network planning
Procedure
Step 1 Set Support Cell Broadcast so that the operator supports the standard cell broadcast. l If the operator is the secondary operator, run the MOD COOPBASIC command on the Local Maintenance Terminal to set Support Cell Broadcast to SPPRTSTANDARD (SupportStandard CB). If the operator is the primary operator, run the MOD BSCBASIC command on the Local Maintenance Terminal to set Support Cell Broadcast to SPPRTSTANDARD (SupportStandard CB).
Step 2 On the Local Maintenance Terminal, run the ADD CBC command to add CBC.
NOTE
The BSC supports up to four standard CBCs. One operator can use only one CBC whereas a CBC can belong to multiple operators.
----End
Example
Suppose the name of the secondary operator is "coop1". An example script is as follows:
/*Make the secondary operator support the standard cell broadcast*/ MOD COOPBASIC: IDXTYPE=BYNAME, OPNAME="coop1", SpprtCB=SPPRTSTANDARD; /*Make the primary operator support the standard cell broadcast*/ MOD COOPBASIC: SpprtCB=SPPRTSTANDARD; /*Add CBC*/ ADD CBC: CBCNAME="cbc1", CBCIP="5.5.5.5", CBCPRT=0, OPNAME="coop1";
Issue 01 (2010-05-20)
49-9
49.8 Configuring the Distributed BTS TRX to Support RAN Sharing

This describes how to configure the distributed BTS TRX to support the RAN sharing function on the Local Maintenance Terminal.
Prerequisite
l l l l
Support Sharing is set to YES(YES). Sharing Allow is set to YES(YES). The BTS is a distributed BTS. The BTS configured with the DRRU/DRFU/MRRU/GRRU/MRFU/GRFU/MBTU supports the RAN sharing function.
Preparation
Table 49-8 Example of the data negotiated and planned for configuring the distributed BTS TRX to support RAN sharing Parameter ID IDXTYPE BTSIDX RXUIDXTYPE SRN SN RXUTYPE SPTSHARING Parameter Name Index Type BTS Index RXU Index Type Subrack No. Slot No. RXU Board Type RanSharing Support Example BYIDX(By Index) 0 SRNSN(SRNSN) 3 3 MRRU YES(YES) Source Network planning Network planning Network planning Network planning Network planning Network planning Network planning
Procedure
Step 1 On the Local Maintenance Terminal, run the LST RXUBP command to check whether RanSharing Support is set to YES(YES). If the value is NO(NO), go to the next step. Step 2 On the Local Maintenance Terminal, run the MOD BTSSHARING command to set RanSharing Support to YES(YES).
NOTE
In the distributed BTS, only the MRRU/DRRU/DRFU/MBTU supports the RAN sharing function.
----End
Example
Take the MRRU as an example. The script is as follows:
/*Query the parameters related to the RXU*/ LST RXUBP: IDXTYPE=BYIDX, BTSIDX=0, RXUIDXTYPE=SRNSN, SRN=3, SN=3; /*Modify the basic data of the BSC to support RAN sharing*/ SET RXUBP: IDXTYPE=BYIDX, BTSIDX=0, RXUIDXTYPE=SRNSN, SRN=3, SN=3, RXUTYPE=MRRU, SPTSHARING=YES;
49.9 Verifying and Deactivating RAN Sharing

This describes how to verify and deactivate RAN sharing on the Local Maintenance Terminal.
Prerequisite
The RAN sharing function is configured.
Procedure
l Verifying RAN sharing
NOTE
In this section, assume that two operators share the GBSS network. MS 1 belongs to the primary operator and MS 2 belongs to the secondary operator.
1.
In the coverage area enabled with the RAN sharing function, use MS 1 to make a call to a fixed-line phone in the cell belonging to the primary operator. Verify that the call is initiated successfully. In the coverage area enabled with the RAN sharing function, use MS 2 to make a call to a fixed-line phone in the cell belonging to the secondary operator. Verify that the call is initiated successfully. On the Local Maintenance Terminal, run the SET OPCELL command to set the primary operator as the operator serving the cell. On the Local Maintenance Terminal, run the SET RXUBP command to set RanSharing Support of the TRX board of the BTS to NO(NO). On the Local Maintenance Terminal, run the MOD BTSSHARING command to set Sharing Allow of the BTS to NO(NO). On the Local Maintenance Terminal, run the SET OPMSC command to delete the settings of the MSC of the secondary operator. On the Local Maintenance Terminal, run the RMV SGSNNODE command to delete the settings of the SGSN of the secondary operator. On the Local Maintenance Terminal, run the SET OPPCU command to delete the settings of the PCU of the secondary operator. On the Local Maintenance Terminal, run the RMV CBC command to delete the settings of the CBC of the secondary operator. On the Local Maintenance Terminal, run the RMV COOPBASIC command to delete the information about the secondary operator. Then, run the MOD BSCBASIC command to change the value of Support Sharing to NO(NO).
2.
Deactivating RAN sharing 1. 2. 3. 4. 5. 6. 7. 8.
Issue 01 (2010-05-20)
49-11
9.
Verifying deactivation of RAN sharing: In the original coverage area enabled with the RAN sharing function, use MS 2 to call a fixed-line phone in the original cell belonging to the secondary operator. Verify that the call fails to be initiated.
----End
49-12
Issue 01 (2010-05-20)
50 Configuring Multi-site Cell
50
About This Chapter
Configuring Multi-site Cell
This feature enables the subsites in different physical sites to be set to a logical cell, which is also called a cascading cell. A subsite refers to a certain area physically covered by multiple RRU/RFUs that belong to the same BBU. In the scenarios such as railway, tunnel, or indoor coverage, a cascading cell can reduce handovers, improve the coverage efficiency, and enhance the user experience. 50.1 Adding a Location Group This describes how to add a location group on the Local Maintenance Terminal. 50.2 Configuring Parameters of Location Groups This describes how to configure parameters of location groups on the Local Maintenance Terminal. 50.3 Verifying Configuration Information About Location Group This describes how to verify the configuration information about the location group on the Local Maintenance Terminal. 50.4 Deleting a Location Group This describes how to delete a location group on the Local Maintenance Terminal. 50.5 Setting Binding Relations of Location Groups This describes how to set binding relations of location groups on the Local Maintenance Terminal. 50.6 Deleting Binding Relations of Location Groups This describes how to delete binding relations of location groups on the Local Maintenance Terminal.
Issue 01 (2010-05-20)
50-1
50.1 Adding a Location Group

This describes how to add a location group on the Local Maintenance Terminal. Scenario Impact Signal coverage under the high-speed railway and indoor coverage can be achieved. None.

NOTE
l l l l l l l
A maximum of 36 location groups can be configured under one base station. A maximum of 24 logical TRXs can be configured in one location group. A maximum of 18 location groups can be configured in one multi-site cell. Currently, only DBS3036 and DBS3900 GSM support multi-site cells. In V300R008, a base station supports a maximum of six location groups, and a location group supports a maximum of six TRXs. In a co-cell, only a main location group can be configured. One location group belongs to only one Multi-site Cell. The board types between the primary location group and secondary location group need not be consistent. The radio TRX number of number of radio TRXs between the primary location group and secondary location group, however, must be consistent.
Prerequisite
The BTS is configured.
Preparation
Table 50-1 Example of the data negotiated and planned for adding a location group Parameter ID IDXTYPE BTSNAME CELLNO LOCGRPNO RXUNO Parameter Name Index Type BTS name Cell No. Location Group No. RXU No. Example BYNAME (BY NAME) DBS3036 0 0 0 Source Network planning Network planning Network planning Network planning Network planning
50-2
Issue 01 (2010-05-20)
Procedure
Step 1 On the Local Maintenance Terminal, run the ADD LOCGRP command. Then, enter the information about of the target BTS, Cell No. and Location Group No. of the co-cell, and the RXU No. in the location group.
NOTE
l l l l l
If the TRX board added in the first TRX board is bound to the TRX, this position is called main location group. The TRX board that is bound to the TRX can be added to the main location group. The TRX board that is not bound to the TRX can be only added to the location group. If the entered location group number does not exist, create a new location group with this location group number. If the entered location group number exists, the board can be added to the location group.
----End
Example
An example script of adding the board numbered 0 to the location group (BTS name: DBS3036, cell number: 0, and location group number: 0) is as follows:
ADD LOCGRP: IDXTYPE=BYNAME, BTSNAME="DBS3036", CELLNO=0, LOCGRPNO=0, RXUNO=0;
50.2 Configuring Parameters of Location Groups

This describes how to configure parameters of location groups on the Local Maintenance Terminal. Scenario Impact Signal coverage under the high-speed railway and indoor coverage can be achieved. None.
Prerequisite
Location groups are added to the BTS.
Preparation
Table 50-2 Example of the data negotiated and planned for configuring parameters of the BTS Parameter ID IDXTYPE BTSNAME Parameter Name Index Type BTS Name Example BYNAME (BY NAME) DBS3036 Source Network planning Network planning
50-3
Issue 01 (2010-05-20)
Parameter ID LOCGRPNO RACJACCLEV OUTPUTPOWERUNI T OUTPUTPOWER
Parameter Name Location Group No. RACH Min.Access Level Output Power Unit Output Power
Example 0 -88 0_1W (Output Power Unit is 0.1W) 1210
Procedure
Step 1 On the Local Maintenance Terminal, run the MOD LOCGRP command to configure parameters of the location groups.
NOTE
The default power of the location group is as follows:

l l
The default power of the MRRU or GRRU in the location group is 15 W. The default power of the DRRU over 850 MHz or 900 MHz in the location group is 18 W, and the default power of the DRRU over 1800 MHz or 1900 MHz is 15 W.
----End
Example
An example script of configuring parameters of location groups is as follows:
MOD LOCGRP: IDXTYPE=BYNAME, BTSNAME="DBS3036", LOCGRPNO=0, RACJACCLEV=-88, OUTPUTPOWERUNIT=0_1W, OUTPUTPOWER=1210;
50.3 Verifying Configuration Information About Location Group

This describes how to verify the configuration information about the location group on the Local Maintenance Terminal. Scenario Impact Verify the configuration information about the location group None.
50-4
Issue 01 (2010-05-20)
Procedure
Step 1 On the Local Maintenance Terminal, run the LST LOCGRP command to query whether parameters of Configuring Parameters of Location Groups are set successfully according to Index Type. ----End
Example
An example script of the information about all the location groups in the cell (BTS index: 0; cell number: 0) is as follows:
LST LOCGRP: IDXTYPE=BYIDX, BTSIDX=0, CELLNO=0;
50.4 Deleting a Location Group

This describes how to delete a location group on the Local Maintenance Terminal. Scenario Impact Network planning None.
Procedure
Step 1 On the Local Maintenance Terminal, run the RMV LOCGRP command to enter Location Group No. and RXU No. to be deleted.
NOTE
l l l
If you enters only location group number, the whole location group can be deleted. If you enters only RXU No., a board in the location group can be deleted. Location groups with binding relations are not allowed to be deleted. If the deletion is required, the binding relation should be lifted first. For details, see 50.6 Deleting Binding Relations of Location Groups.
----End
Example
Example scripts of deleting the configuration information about location groups are as follows:
/*Delete the location group that the BTS name is DBS3036, cell number is 0, and the location group number is 1*/ RMV LOCGRP: IDXTYPE=BYNAME, BTSNAME="DBS3036", CELLNO=0, LOCGRPNO=1; /*Delete the board that the BTS name is DBS3036, cell number is 0, and the location group number is 0, and the RXU number is 2*/ RMV LOCGRP: IDXTYPE=BYNAME, BTSNAME="DBS3036", CELLNO=0, LOCGRPNO=0, RXUNO=2;
50.5 Setting Binding Relations of Location Groups

This describes how to set binding relations of location groups on the Local Maintenance Terminal.
Scenario Impact
Signal coverage under the high-speed railway and indoor coverage can be achieved. None.
Prerequisite
l l
The co-cell is configured in the BTS. Main location group and sub-location group are configured in the co-cell.
Preparation
Table 50-3 Example of data negotiated and planned for setting binding relations of location groups Parameter ID IDXTYPE BTSIDX TRXNO TRXBN TRXPN Parameter Name Index Type BTS Index Main Location Group Logical TRX No. Sub-Location Group TRX Board No. Sub-Location Group TRX Board Channel No. Example BYIDX(By Index) 0 0 4 0 Source Network planning Network planning Network planning Network planning Network planning
Procedure
Step 1 On the Local Maintenance Terminal, run the SET BINDLOCGRP command to set the logical TRX number of the TRX board in the main location group, the TRX board number and channel number of the TRX board in the sub-location group that is bound to the TRX in the main location group.
NOTE
l l l l l
The TRX on the TRX board in the main location group can be bound to all the channels in a sublocation group only once, and can be also bound to multiple sub-location groups. The TRX of each main location group must be bound to the sub-location group. The main location group and sub-location groups with binding relations can be configured in only a co-cell. The binding relation can be set only between the board of the main location group and that of the sublocation group. For the MRRU or GRRU, the antenna channel number is required.
----End
Example
An example script of binding the TRX that the BTS index is 0 and the TRX number of the main location group is 0 with the idle board and channel that the TRX board number of the sub-location group is 4 and the channel number of the TRX board in the sub-location group is 0 is as follows:
SET BINDLOCGRP: IDXTYPE=BYIDX, BTSIDX=0, TRXNO=0, TRXBN=4, TRXPN=0;
50.6 Deleting Binding Relations of Location Groups

This describes how to delete binding relations of location groups on the Local Maintenance Terminal. Scenario Impact Network planning None.
Prerequisite
l l
The co-cell is configured in the BTS. In the co-cell, there is binding relation between the TRX in the main location group and the channel of the board in the sub-location group.
Procedure
Step 1 On the Local Maintenance Terminal, run the SET UNBINDLOCGRP command, and then enter BTS Index or BTS Name, logical TRX number of the main location group, and the TRX board number of the sub-location group to delete binding relations of location groups.
NOTE
l l
When you delete binding relations between the main location group and the sub-location group, the antenna channel number of the MRRU or DRRU is not required. When you run the RMV CELL command to delete the co-cell, the information about location groups in the cell and binding relations of location groups can be deleted.
----End
Example
An example script of deleting binding relations between the main location group (BTS index: 0; logical TRX number of the main location group: 0) and the sub-location group (TRX number: 4; channel number of the TRX board of the sub-location group: 0) is as follows:
SET UNBINDLOCGRP: IDXTYPE=BYIDX, BTSIDX=0, TRXNO=0, TRXBN=4, TRXPN=0;
Issue 01 (2010-05-20)
50-7
51 Configuring IBCA
51
About This Chapter
Prerequisite
l l l
Configuring IBCA
IBCA algorithm is a channel assignment algorithm, which has a remarkable effect on improving the utilization of frequency resources and expanding the network capacity. To use the IBCA algorithm, the inter-site Um interface software synchronization or GPS synchronization should be enabled. In addition, the GPS synchronization requires the support from the hardware configuration.
IBCA is restricted by the license. Activate the license on the Local Maintenance Terminal. For details, see Activate BSC License. To enable the IBCA algorithm, the GXPUI should be added to the BSC. The GXPUI is used to estimate the interference experienced by each idle channel in every channel assignment procedure and the interference of a new call to established calls on the same timeslot in the IBCA neighboring cells. To enable the inter-BSC IBCA algorithm, the GFGUB or GOGUB should be added to the BSC. The GFGUB or GOGUB is used to establish a communication link to transfer the related information about the IBCA algorithm between BSCs.
Context
Purpose IBCA is applied to the network in which frequency resources are insufficient and thus the same frequency is repeatedly used in neighboring cells. In this case, the severe inter-cell interference cannot be solved even if the frequency hopping is used. In this network, the bottleneck that restricts the network capacity is not the interference (link quality) but the channel number. In this situation, the C/I ratios of idle channels need to be estimated. The channels that the C/I ratios meet the requirements of calls are assigned to the calls. In addition, there is no unfavorable influence on the established call after a new call is established. This channel assignment algorithm is called interference based channel assignment (IBCA). IBCA algorithm has a remarkable effect on improving the utilization of frequency resources and expanding the network capacity.
51 Configuring IBCA
Working Principle Considering the inter-channel interference, the IBCA requests that the interference of the assigned channel on the calls in the same timeslot should be minimized. In addition, the interference of the calls in the same timeslot on the assigned channel should also be minimized. The IBCA algorithm is compatible with the existing channel assignment mechanism. That is, the optimal channel is selected on the basis of channel priorities. In the synchronization and cyclic frequency hopping network, the inter-site interference relations can be predicted. Thus, the C/I ratio of the new call established on the idle channel can be predicted. In addition, the influence of the new call on the established call can be estimated. On this basis, the MAIO and the idle channel that meets the requirements of the new call and has the least impact on the established call can be selected. The Um interface synchronization is required to use the IBCA algorithm. The Um interface synchronization involves the Um interface software synchronization and GPS synchronization, either of synchronization modes can be adopted. The IBCA algorithm switch is a cell-level parameter. For cells that enable the IBCA algorithm, the IBCA algorithm needs to calculate the intra-cell and inter-cell interference between channels in the same timeslot. If the two cells that exist the interference relations are distributed in two BSCs, the inter-BSC communication interface is required to send the information about the interference calculation of related cells to the corresponding BSC. Hardware Configuration As the IBCA module involves many calculations, the load of CPU0 increases greatly and thus affects normal working of the BSC if this module is placed in CPU0. Therefore, two GXPUIs are added in the BSC, which perform most calculations of the IBCA module. Configuring IBCA involves configuring the GXPUI, configuring the TRX that supports the IBCA algorithm, and configuring the cell that supports the IBCA algorithm. 51.1 Configuration Principles of IBCA This describes the configuration principles of the IBCA. 51.2 Data Negotiated and Planned for Configuring IBCA The following data involves the configuration of a 2G internal IBCA neighboring cell relation and a 2G external IBCA neighboring cell relation. 51.3 Configuring IBCA This describes how to configure IBCA on the Local Maintenance Terminal. 51.4 Configuring the IBCA Cell that Supports HWIII Power Control Algorithm This describes how to configure the IBCA cell that supports HWIII power control algorithm on the Local Maintenance Terminal. HWIII power control algorithm must be enabled in the IBCA cell. 51.5 Configuring the Cell that Enables the IBCA Algorithm Switch This describes how to configure the cell that enables the IBCA algorithm switch on the Local Maintenance Terminal. 51.6 Configuring an IBCA Neighboring Cell This describes how to configure an IBCA neighboring cell on the Local Maintenance Terminal. 51.7 Configuring the BTS Synchronization Mode This describes how to configure the BTS synchronization mode on the Local Maintenance Terminal.
51 Configuring IBCA
51.8 Configuring External Attributes of the BSC This describes how to add external attributes of the BSC on the Local Maintenance Terminal. 51.9 Binding the external BSC and the External Cell This describes how to configure the binding relation between the external BSC and the external cell on the Local Maintenance Terminal. 51.10 Deactivating IBCA This describes how to deactivate IBCA on the Local Maintenance Terminal.
Issue 01 (2010-05-20)
51-3
51 Configuring IBCA
51.1 Configuration Principles of IBCA

This describes the configuration principles of the IBCA.
l
Network planning should be performed in the cell where IBCA is to be implemented before the implementation of IBCA.

The number of IBCA neighboring cells should be planned for the cell. The MAIO, MA group, and number of different frequency bands to which the frequencies in the MA group belong should be planned for the cell.
In a cell where the IBCA algorithm is enabled, if IBCA Dynamic Measure Neighbor Cell Allowed is set to YES(Yes), IBCA Waiting Measurement Report Time must be smaller than Min Interval for Consecutive Hos and Min Interval for Emerg.Hos. If the cell with the IBCA enabled is already configured with the IBCA neighboring cell, and if the parameter IBCA Dynamic Measure Neighbor Cell Allowed is set to YES (Yes), the EMR function cannot be enabled in the cell simultaneously. In the IBCA cell, only one MA group can be configured in each timeslot and each frequency. In the Co-BCCH cell, two MA groups can be configured (each frequency band for one MA group). For the BSC enabled with the IBCA algorithm, the number of MA tables used in an IBCA cell group must not exceed three. The number of frequencies in the MA table for the cell where the IBCA algorithm is enabled must not exceed 12. The number of IBCA neighboring cells of a cell must not exceed 12. The number of neighboring BSCs of a BSC on which the inter-BSC IBCA algorithm is enabled must not exceed 16. The IBCA algorithm only applies to the assignment of channels on the TRXs involved in FH. The IBCA algorithm does not support the external PCU. The Huawei III power control algorithm must be enabled in the cell where the IBCA algorithm is to be enabled. The active power control algorithm is not allowed to be enabled in the IBCA cell. IBCA uses its own power prediction algorithm to perform the initial power prediction. Neither Flex MAIO nor Flex TSC can be enabled in the IBCA cell. In RF FH mode, preferentially use the fixed MAIOs in the frequency planning for the configured SDCCHs. For the SDCCHs dynamically converted from the TCHs, use the MAIOs dynamically allocated by the IBCA. These MAIOs cannot be dynamically allocated to other MSs that use the same timeslots in the cell. In IBCA cell, the static PDTCHs that are on the same TRX and use the same MA group must be configured with the same MAIO. In IBCA cell, the PDTCH and SDCCH that are on the same TRX and use the same MA group must be configured with the same MAIO.
l l l l l l l l l l
l l
51.2 Data Negotiated and Planned for Configuring IBCA

The following data involves the configuration of a 2G internal IBCA neighboring cell relation and a 2G external IBCA neighboring cell relation.
51 Configuring IBCA
Table 51-1 Example of the data negotiated and planned for configuring the GXPUI Parameter ID SRN SN BT BackType Parameter Name Subrack No. Slot No. Board Type Back Type Example 1 13 GXPUI NONE(Independent Mode) Source Network planning Network planning Network planning Network planning
Table 51-2 Example of the data negotiated and planned for configuring the GFGUB Parameter ID SRN SN BT BackType PORTTYPE Parameter Name Subrack No. Slot No. Board Type Back Type Port Type Example 1 15 GXPUI NONE(Independent Mode) GE Source Network planning Network planning Network planning Network planning Network planning
Table 51-3 Example of the data negotiated and planned for configuring an FH cell Parameter ID BTSNAME TYPE UPNODE SRN SN PN MPMODE AST SERVICEMODE CELLNAME MCC Parameter Name BTS Name BTS Type Up Node Type Subrack No. Slot No. Port No. Multiplexing Mode Activity State Service Type Cell Name Cell MCC Example BTS_IBCA BTS3012 BSC 1 2 0 MODE4_1 ACTIVATED (Activated) TDM IBCA_01 460 Source Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning
Issue 01 (2010-05-20)
51-5
51 Configuring IBCA
Parameter ID MNC LAC CI CTYPE CPLMODE TRXBN TRXTP TRXPN TRXFREQ FREQ FHMODE HOPINDEX FREQ1-FREQ5 MAIO1-MAIO5
Parameter Name Cell MNC Cell LAC Cell CI Freq. Band Separate Mode TRX Board No. TRX Board Type TRX Board Pass No. TRX Freq Freq. Frequency hopping mode Hop Index frequency 1frequency 5 MAIO1-MAIO5
Example 11 10 1 GSM900_DCS1800 SUPPORT(Support) 0 QTRU 0 40 50, 60, 70, 80, 90 RF_FH(RF FH) 0 50, 60, 70, 80, 90 0, 1, 2, 3, 4
Source Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning
Table 51-4 Example of the data negotiated and planned for enabling Huawei III power control algorithm in a cell Parameter ID IDXTYPE CELLNAME PWRCTRLSW PWRBCDALLOW D Parameter Name Index Type Cell Name Power Control Switch Power Forecast Allowed Example BYNAME(By Name) IBCA_01 HW3(HW3 Power Control) NO(NO) Source Network planning Network planning Network planning Network planning
51-6
Issue 01 (2010-05-20)
51 Configuring IBCA
Table 51-5 Example of the data negotiated and planned for enabling the IBCA algorithm in a cell Parameter ID IDXTYPE CELLNAME IBCAALLOWED IBCASOFTBLKSWITCH IBCAICDMSWITCH IBCADYNCMEASUR ENCELLALLOWED IBCAMAIOUSMTD Parameter Name Index Type Cell Name IBCA Allowed IBCA Soft Block Switch IBCA ICDM Switch IBCA Dynamic Measure Neighbor Cell Allowed IBCA MAIO Using Method Example BYNAME(By Name) IBCA_01 YES(Yes) YES(Yes) YES(YES) NO(NO) Source Network planning Network planning Network planning Network planning Network planning Network planning
0(Max. Optimized MAIO)
Network planning
Table 51-6 Example of the data negotiated and planned for configuring an internal IBCA neighboring cell Parameter ID IDXTYPE SRCCELLNAME NBRCELLNAME IBCANCELLFLAG IBCADYNCMEASURENCELLALLOWED Parameter Name Index Type Source Cell Name Neighbor Cell Name IBCA Neighbor Cell Flag IBCA Dynamic Measure Neighbor Cell Flag Example BYNAME(By Name) IBCA_01 IBCA_02 YES(YES) YES(YES) Source Network planning Network planning Network planning Network planning Network planning
Table 51-7 Example of the data negotiated and planned for configuring the BTS synchronization method Parameter ID IDXTYPE BTSIDX Parameter Name Index Type BTS Index Example BYIDX(By Index) 1 Source Network planning Network planning
Issue 01 (2010-05-20)
51-7
51 Configuring IBCA
Parameter ID SYNCMETHOD
Parameter Name Site Synchronization Method
Example AISS(Air Interface Software Sync)
Table 51-8 Example of the data negotiated and planned for configuring an external IBCA neighboring cell Parameter ID IBSCNAME BSCDPC CELLNAME MCC MNC LAC CI BCCH NCC BCC BSCIDX Parameter Name External BSC Name External BSC DPC Cell Name Cell MCC Cell MNC Cell LAC Cell CI BCCH FD NCC BCC External BSC Index Example EXTBSC 170 EXTCELL_01 460 11 10 10 15 0 0 0 Source Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning
51.3 Configuring IBCA

This describes how to configure IBCA on the Local Maintenance Terminal.
Preparation
The following procedure takes how to configure a 2G internal IBCA neighboring cell relation and a 2G external IBCA neighboring cell relation as examples. For details, see 51.2 Data Negotiated and Planned for Configuring IBCA.
Procedure
Step 1 On the Local Maintenance Terminal, run the ADD BRD command to add a GXPUI and a GFGUB. Step 2 Add a BTS and a cell, and configure this cell as an FH cell. 1. 2.
51-8
On the Local Maintenance Terminal, run the ADD BTS command to add a cell. On the Local Maintenance Terminal, run the ADD TRX command to add a TRX.
51 Configuring IBCA
3.
On the Local Maintenance Terminal, run the MOD CELLHOPTP command to set the FH mode of the cell to RF FH. For details, see 8 Configuring Frequency Hopping.
Step 3 On the Local Maintenance Terminal, run the MOD CELLMAGRP to configure the FH group. Step 4 On the Local Maintenance Terminal, run the MOD CELLPWRBASIC command to set Power Control Switch to HW3(HW3 Power Control). Thus, Huawei III power control algorithm is enabled in the configured cell. Step 5 On the Local Maintenance Terminal, run the MOD MAIOPLAN to configure the MAIO data. Step 6 On the Local Maintenance Terminal, run the MOD CELLCHMGAD command to set IBCA Allowed to YES(YES). Thus, the IBCA algorithm is enabled in the configured cell. Step 7 Repeat Step 2 through Step 6 to add another IBCA cell.
NOTE
For internal cells of the BSC, the IBCA algorithm must be enabled in the neighboring cells of the IBCA cell.
Step 8 On the Local Maintenance Terminal, run the ADD CELL2GNC command to configure 2G internal neighboring cell relations, and set the attribute parameters of the neighboring cell IBCA Neighbor Cell Flag and IBCA Dynamic Measure Neighbor Cell Flag to YES(YES). Step 9 On the Local Maintenance Terminal, run the MOD BTSOTHPARA command to set Site Synchronization Method to AISS(Air Interface Software Sync). The BTS synchronization method is configured as soft-synchronized network. Step 10 Add an external cell and configure it as a 2G external neighboring cell. 1. 2. 3. On the Local Maintenance Terminal, run the ADD EXTBSC command to configure the data of the signaling points in the external BSC. On the Local Maintenance Terminal, run the command LST EXTBSC to query the external BSC index. On the Local Maintenance Terminal, run the ADD CELL2GEXTC command to add a 2G external cell, and then bind this cell and the added external BSC specified in Step 7.a according to the external BSC index obtained from Step 7.b.
Step 11 On the Local Maintenance Terminal,run the SET OTHSOFTPARA command to set IBCA Information Report Period Within BSC to 200 and IBCA Information Report Period Between BSC to 8. Step 12 Repeat Step 8 to configure 2G external neighboring cell relations. ----End
Example
/*Add a GXPUI*/ ADD BRD: SRN=1, SN=13, BT=GXPUI, BackType=NONE; /*Add a GFGUB*/ ADD BRD: SRN=1, SN=15, BT=GFGUB, PortType=GE, BackType=NONE; /*Add a BTS and a cell*/ ADD BTS: BTSNAME="BTS_IBCA", TYPE=BTS3012, UPNODE=BSC, SRN=1, SN=2, PN=0, MPMODE=MODE4_1, AST=ACTIVATED, ServiceMode=TDM, DCELLNAME="IBCA_01", DCTYPE=GSM900_DCS1800, DCMCC="460", DCMNC="11", DCLAC=10, DCCI=0, CPLMode=SUPPORT, TRXBN=0, TRXTP=QTRU, TRXPN=0, FREQ=40;
Issue 01 (2010-05-20)
51-9
51 Configuring IBCA
/*Add a TRX*/ ADD TRX: IDXTYPE=BYNAME, CELLNAME="IBCA_01", TRXBN=0, TRXTP=QTRU, TRXPN2=1, FREQ=50; ADD TRX: IDXTYPE=BYNAME, CELLNAME="IBCA_01", TRXBN=0, TRXTP=QTRU, TRXPN2=2, FREQ=60; ADD TRX: IDXTYPE=BYNAME, CELLNAME="IBCA_01", TRXBN=0, TRXTP=QTRU, TRXPN2=3, FREQ=70; ADD TRX: IDXTYPE=BYNAME, CELLNAME="IBCA_01", TRXBN=0, TRXTP=QTRU, TRXPN2=4, FREQ=80; ADD TRX: IDXTYPE=BYNAME, CELLNAME="IBCA_01", TRXBN=0, TRXTP=QTRU, TRXPN2=5, FREQ=90; /*Configure an FH cell*/ MOD CELLHOPTP: IDXTYPE=BYNAME, CELLNAME="IBCA_01", FHMODE=RF_FH; /*Enable Huawei III power control algorithm in a cell*/ MOD CELLPWRBASIC: IDXTYPE=BYNAME, CELLNAME="IBCA_01", PWRCTRLSW=HW3, PWRBCDALLOWD=NO; /*Configure an FH group*/ MOD CELLMAGRP: IDXTYPE=BYNAME, CELLNAME="IBCA_01", HOPINDEX=0, FREQ1=50, FREQ2=60, FREQ3=70, FREQ4=80, FREQ5=90; /*Configure the MAIO data*/ MOD MAIOPLAN: IDXTYPE=BYNAME, CELLNAME="IBCA_01", HOPINDEX=0, MAIO1=0, MAIO2=1, MAIO3=2, MAIO4=3, MAIO5=4; /*Enable the IBCA algorithm in a cell*/ MOD CELLCHMGAD: IDXTYPE=BYNAME, CELLNAME="IBCA_01", IBCAALLOWED=YES, IBCASOFTBLKSWITCH=YES, IBCADYNCMEASURENCELLALLOWED=NO, IBCAICDMSWITCH=YES, IBCAMAIOUSMTD=0; /*Configure 2G internal neighboring cell relations*/ ADD CELL2GNC: IDXTYPE=BYNAME, SRCCELLNAME="IBCA_01", NBRCELLNAME="IBCA_02", IBCANCELLFLAG=YES, IBCADYNCMEASURENCELLALLOWED=YES; /*Configure the synchronization method of the BTS*/ MOD BTSOTHPARA: IDXTYPE=BYNAME, BTSNAME="BTS_IBCA", SYNCMETHOD=AISS; /*Add an external BSC*/ ADD EXTBSC: BSCNAME="EXTBSC", BSCDPC=170; /*Add a cell to the external BSC*/ ADD CELL2GEXTC: CELLNAME="EXTCELL_01", MCC="460", MNC="11", LAC=10, CI=10, BCCH=15, NCC=0, BCC=0, BSCIDX=0; /*Configure BSC parameters*/ SET OTHSOFTPARA: IBCAINBSCINFORPTPRD=200, IBCAOUTBSCINFORPTPRD=8; /*Configure 2G external neighboring cell relations*/ ADD CELL2GNC: IDXTYPE=BYNAME, SRCCELLNAME="IBCA_01", NBRCELLNAME="EXTCELL_01", IBCANCELLFLAG=YES, IBCADYNCMEASURENCELLALLOWED=YES;
51.4 Configuring the IBCA Cell that Supports HWIII Power Control Algorithm
This describes how to configure the IBCA cell that supports HWIII power control algorithm on the Local Maintenance Terminal. HWIII power control algorithm must be enabled in the IBCA cell.
51-10
Issue 01 (2010-05-20)
51 Configuring IBCA
Preparation
Table 51-9 Example of the data negotiated and planned for configuring the cell that supports HWIII power control algorithm Parameter ID IDXTYPE CELLNAME PWRCTRLSW Parameter Name Index Type Cell Name Power Control Algorithm Switch Example BYNAME (BY NAME) IBCA1_1 HW3 (HW3 Power Control) Source Network planning Network planning Network planning
Procedure
Step 1 On the Local Maintenance Terminal, run the LST CELLPWRBASIC command to query whether the parameter of the target IBCA cell Power Control Algorithm Switch is set to HW3 (HW3 Power Control). That is, check whether HWIII power control algorithm of the target cell is enabled. Step 2 If HWIII power control algorithm is not enabled for the target cell, run the MOD CELLPWRBASIC command to set Power Control Algorithm Switch to HW3 (HW3 Power Control). ----End
Example
An example script of configuring the IBCA cell that supports HWIII power control algorithm is as follows:
MOD CELLPWRBASIC: IDXTYPE=BYNAME, CELLNAME="IBCA1_1", PWRCTRLSW=HW3;
51.5 Configuring the Cell that Enables the IBCA Algorithm Switch
This describes how to configure the cell that enables the IBCA algorithm switch on the Local Maintenance Terminal.
Prerequisite
l
If IBCA algorithm is enabled and IBCA Dynamic Measure Neighbor Cell Allowed is set to Yes in the cell, IBCA Waiting Measurement Report Time must be less than Min Interval for Consecutive HOs and Min Interval for Emerg.HOs.
NOTE
Run commands LST CELLCHMGAD and LST CELLHOCTRL to query whether above parameters meet requirements. If parameters do not meet requirements, run commands MOD CELLCHMGAD and MOD CELLHOCTRL to modify parameters.
Issue 01 (2010-05-20)
51-11
51 Configuring IBCA
l
For internal cells of the BSC, cell A must enable the IBCA algorithm if cell A is an IBCA neighboring cell of cell B. The active power control algorithm is not allowed to be enabled in the cell where enables the IBCA algorithm. IBCA algorithm has power prediction algorithm to perform the initial power prediction.
Preparation
Table 51-10 Example of the data negotiated and planned for configuring the cell that enables the IBCA algorithm switch Parameter ID IDXTYPE CELLNAME IBCAALLOWED Parameter Name Index Type Cell Name IBCA Allowed Example BYNAME (BY NAME) IBCA1_1 YES(Yes) Source Network planning Network planning Network planning
Procedure
Step 1 On the Local Maintenance Terminal, run the LST CELLCHMGAD command to query whether the parameter IBCA Allowed of the target IBCA cell is set to Yes. Step 2 If this parameter is set to No, run the MOD CELLPWRBASIC command to set IBCA Allowed to Yes. ----End
Example
An example script of configuring the cell that enables the IBCA algorithm switch is as follows:
MOD CELLCHMGAD: IDXTYPE=BYNAME, CELLNAME="IBCA1_1", IBCAALLOWED=YES;
51.6 Configuring an IBCA Neighboring Cell

This describes how to configure an IBCA neighboring cell on the Local Maintenance Terminal.
Prerequisite
At least two cells enable the IBCA algorithm switch.
51-12
Issue 01 (2010-05-20)
51 Configuring IBCA
Preparation
Table 51-11 Example of the data negotiated and planned for configuring an IBCA neighboring cell Parameter ID IDXTYPE SRCCELLIDX NBRCELLIDX HOCTRLSWITCH Parameter Name Index Type Source Cell Index Neighbor Cell Index Current HO Control Algorithm in Source Cell IBCA Neighbor Cell Flag IBCA Dynamic Measure Neighbor Cell Flag Example BYIDX(By Index) 0 2 HOALGORITH M2(HO Algorithm II) YES(Yes) YES(Yes) Source Network planning Network planning Network planning Network planning
IBCANCELLFLAG IBCADYNCMEASURENCELLALLOWED
Procedure
Step 1 On the Local Maintenance Terminal, run the ADD CELL2GNC command to add neighboring relations of 2G neighboring cells. Then, configure the cell that enables the IBCA algorithm switch as an IBCA neighboring cell according to the network planning. Set IBCA Neighbor Cell Flag and IBCA Dynamic Measure Neighbor Cell Flag to Yes. ----End
Example
An example script of configuring an IBCA neighboring cell is as follows:
ADD CELL2GNC: IDXTYPE=BYIDX, SRCCELLIDX=0, NBRCELLIDX=2, HOCTRLSWITCH=HOALGORITHM2, IBCANCELLFLAG=YES, IBCADYNCMEASURENCELLALLOWED=YES;
51.7 Configuring the BTS Synchronization Mode

This describes how to configure the BTS synchronization mode on the Local Maintenance Terminal.
Issue 01 (2010-05-20)
51-13
51 Configuring IBCA
Preparation
The BTS synchronization involves GPS synchronization and Um interface software synchronization. The following takes how to configure the Um interface software synchronization as BTS synchronization mode as an example. For details, see 44 Managing a BSC Soft-Synchronized Network Task. Table 51-12 Example of the data negotiated and planned for configuring the BTS synchronization mode Parameter ID IDXTYPE BTSIDX SYNCMETHOD Parameter Name Index Type BTS Index Site Synchronization Method Example BYIDX(By Index) 1 AISS (Air Interface Software Sync) Source Network planning Network planning Network planning
Procedure
Step 1 On the Local Maintenance Terminal, run the MOD BTSOTHPARA command to set Site Synchronization Method to AISS (Air Interface Software Sync). Then, the BTS configuration mode is configured as the Um interface software synchronization. ----End
Result
On the Local Maintenance Terminal, run the LST BTSOTHPARA command to query whether the parameter Site Synchronization Method is set to AISS (Air Interface Software Sync).
Example
Example scripts of configuring the Um interface software synchronization as BTS synchronization mode are as follows:
/*Configure the mode*/ MOD BTSOTHPARA: /*Query the BTS LST BTSOTHPARA: Um interface software synchronization as BTS synchronization IDXTYPE=BYIDX, BTSIDX=1, SYNCMETHOD=AISS; synchronization mode*/ IDXTYPE=BYNAME, BTSNAME="IBCA1";
51.8 Configuring External Attributes of the BSC

This describes how to add external attributes of the BSC on the Local Maintenance Terminal.
51 Configuring IBCA
Preparation
Table 51-13 Example of the data negotiated and planned for adding external attributes of the BSC Parameter ID IBSCNAME BSCDPC Parameter Name External BSC Name External BSC DPC Example 201 170 Source Network planning Network planning
Procedure
Step 1 On the Local Maintenance Terminal, run the ADD EXTBSC command to configure external signaling points of the BSC. ----End
Result
On the Local Maintenance Terminal, run the LST EXTBSC command to query whether external signaling points of the BSC are configured.
Example
Example scripts of adding external attributes of the BSC are as follows:
/*Configure external signaling points of the BSC*/ ADD EXTBSC: BSCNAME="201", BSCDPC=170; /*Query configurations of external signaling points of the BSC*/ LST EXTBSC:;
51.9 Binding the external BSC and the External Cell

This describes how to configure the binding relation between the external BSC and the external cell on the Local Maintenance Terminal.
Prerequisite
External signaling points of the BSC are configured.
Procedure
Step 1 On the Local Maintenance Terminal, run the LST EXTBSC command to query 51.8 Configuring External Attributes of the BSC configured External BSC Index. Step 2 Configure the binding relation between the external BSC and the external cell on the Local Maintenance Terminal.
l
To bind the added external cell and the external BSC, do as follows: run the ADD CELL2GEXTC command to set BSC Index to the index number queried in step 1.
Issue 01 (2010-05-20)
51 Configuring IBCA
l
To bind the original external cell and the external BSC, do as follows: run the ADD CELL2GEXTC command to set BSC Index to the index number queried in step 1.
----End
Example
Example scripts of configuring the binding relation between the external BSC and the external cell are as follows:
/*Query configurations of external signaling points of the BSC*/ LST EXTBSC:; /*Bind the added external cell and the external BSC*/ ADD CELL2GEXTC: CELLNAME="IBCA2_2", MCC="460", MNC="00", LAC=10, CI=1, BCCH=988, NCC=0, BCC=0, BSCIDX=0; /*Modify attributes of the original external cell and bind the original external cell and the external BSC*/ MOD CELL2GEXTC: IDXTYPE=BYNAME, CELLNAME="IBCA2_2", ", BSCIDX=0;
51.10 Deactivating IBCA

This describes how to deactivate IBCA on the Local Maintenance Terminal.
Prerequisite
The IBCA function is configured.
Procedure
Step 1 On the Local Maintenance Terminal, run the MOD CELLCHMGAD command to set IBCA Allowed to NO(NO) to deactivate the IBCA function. ----End
51-16
Issue 01 (2010-05-20)
52 Configuring BTS in automatic planning mode
52
Configuring BTS in automatic planning mode
About This Chapter

Before the automatic planning of the BTS, you need to preconfigure some parameters used by the algorithm on the M2000 client. You can also query the progress and result of the automatic planning of the BTS, analyze the data, or locate the fault on the M2000 client. For details, see M2000 Operator Guide. Configuring BTS in automatic planning mode includes Configuring a BTS3900B GSM in automatic planning mode and Configuring a BTS3900E GSM in automatic planning mode 52.1 Adding the BTS3900B GSM This describes how to add a BTS3900B GSM in automatic planning mode on the Local Maintenance Terminal. 52.2 Adding the BTS3900E GSM This describes how to add a BTS3900E GSM in automatic planning mode on the Local Maintenance Terminal.
Issue 01 (2010-05-20)
52-1
52.1 Adding the BTS3900B GSM

This describes how to add a BTS3900B GSM in automatic planning mode on the Local Maintenance Terminal. Scenario Mandatory/ Optional Impact The BTS3900B GSM is mainly used in the area where the macro BTS cannot cover. Optional. The configuration of the BTS3900B GSM can increase the network coverage, realize the automatic configuration of the cell parameters, and reduce the maintenance cost and difficulty in network planning.
NEs Involved BTS, BSC, and M2000
Prerequisite
l
The GFGUB/GOGUB is already configured and works in active/standby mode.
When the Abis interface uses device IP address in communication, the device IP address and port IP address of the active and standby boards are already configured. When the Abis interface uses port IP address in communication, the port IP address of the active and standby boards are already configured.
The GXPUM/GXPUT/GDPUX is configured in the GMPS or GEPS where the GFGUB/ GOGUB is located. The license is obtained and activated. To obtain and activate a license, do as follows: 1. In BSC6000V900R008 Exceptional Commercial License Application Template, set Whether to activate PICO Solution Package under License control items to 1. The value 1 indicates that this function is enabled. Activate the license on the Local Maintenance Terminal. For details, see Activate BSC License.
2.
Preparation
Table 52-1 Example of the data negotiated and planned for adding the BTS3900B GSM Parameter Site attribute s BTSNAME TYPE UPNODE Parameter Name BTS name BTS type Up Node Type Example pico BTS3900B_G SM BSC Source Network planning Network planning Network planning
52-2
Issue 01 (2010-05-20)
Parameter SRN SN PN SVCMODE IP IPMSK GWIP BARCODE
Parameter Name Subrack No. Slot No. Port No. Service Type BTS IP BTS IP Mask BTS SeGW IP Address BTS Interface Board Bar Code Cell Name Cell Type BTS Automatic Plan Maximum TRX Number
Example 0 26 0 IP 192.168.1.1 255.255.255.0 199.169.1.1 111122222233 33333 pico_cell0 DCS1800 1
Source Network planning Network planning Network planning Network planning Network planning Network planning Network planning Factory setting
Cell attribute s
DCELLNAME DCTYPE MAXFQNUM
Procedure
Step 1 On the Local Maintenance Terminal, run the ADD AUTOPLANBTS command to add the BTS3900B GSM.
NOTE
When you add the BTS3900B GSM, Service Type can be set to IP only. CGI and RAC Automatic Plan Arithmetic Switch, Freq. and BSIC Automatic Optimize Arithmetic Switch, and Capacity and Coverage Automatic Optimize Arithmetic Switch is set to ON(ON) by default. Run the MOD AUTOPLANCFG command to select the automatic planning algorithm.
----End
Example
An example script for adding the BTS3900B GSM is as follows:
ADD AUTOPLANBTS: BTSNAME="pico", TYPE=BTS3900B_GSM, UPNODE=BSC, SRN=0, SN=26, PN=0, SVCMODE=IP, IP="192.168.1.1", IPMSK="255.255.255.0", GWIP="199.169.1.1", BARCODE="11112222223333333", DCELLNAME="pico_cell0", DCTYPE=DCS1800, MAXFQNUM=1;
52.2 Adding the BTS3900E GSM

This describes how to add a BTS3900E GSM in automatic planning mode on the Local Maintenance Terminal. Scenario Mandatory/ Optional Impact The BTS3900E GSM is mainly used for indoor coverage and public area coverage. Optional. The configuration of the BTS3900E GSM realizes the automatic planning and optimization of the BTS and reduces the maintenance cost and difficulty in network planning.
NEs Involved BTS, BSC, and M2000
Prerequisite
l
In TDM networking mode:

The GEIUB/GOIUB is already configured. There are idle ports on the GEIUB/GOIUB in the GMPS or GEPS. The GXPUM is configured in the GMPS or GEPS where the GEIUB/GOIUB is located. The GEHUB is already configured. There are idle ports on the GEHUB in the GMPS or GEPS. The GXPUM/GXPUT/GDPUX is configured in the GMPS or GEPS where the GFGUB/GOGUB is located. The GFGUB/GOGUB is already configured. If the GFGUB/GOGUB works in active/ standby mode, the device IP addresses and port IP addresses should be configured for the active and standby GFGUBs/GOGUBs. The GXPUM/GXPUT/GDPUX is configured in the GMPS or GEPS where the GFGUB/GOGUB is located. In BSC6000V900R008 Exceptional Commercial License Application Template, set Whether to activate Easy GSM Solution Package under License control items to 1. The value 1 indicates that this function is enabled. Activate the license on the Local Maintenance Terminal. For details, see Activate BSC License.
In HDLC/HUB networking mode:

In IP networking mode:
The license is obtained and activated. To obtain and activate a license, do as follows: 1.
2.
52-4
Issue 01 (2010-05-20)
Preparation
Table 52-2 Example of the data negotiated and planned for adding the BTS3900E GSM in TDM networking mode Parameter BTS attribute s BTSNAME TYPE UPNODE SRN SN PN SVCMODE Cell attribute s DCELLNAME DCTYPE MCC MNC LAC CI Parameter Name BTS name BTS type Up Node Type Subrack No. Slot No. Port No. Service Type Cell Name Cell Type MCC MNC LAC CI Example shanghai BTS3900E_GS M BSC 0 26 0 TDM shanghai_0 DCS1800 460 01 8240 2 Source Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning
Issue 01 (2010-05-20)
52-5
Table 52-3 Example of the data negotiated and planned for adding the BTS3900E GSM in HDLC/HUB networking mode Parameter Site attribute s BTSNAME TYPE UPNODE SRN SN PN SVCMODE Cell attribute s DCELLNAME DCTYPE MCC MNC LAC CI Parameter Name BTS name BTS type Up Node Type Subrack No. Slot No. Port No. Service Type Cell Name Cell Type MCC MNC LAC CI Example shanghai BTS3900E_GS M BSC 0 26 0 HDLC shanghai_0 DCS1800 460 01 8240 2 Source Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning
Table 52-4 Example of the data negotiated and planned for adding the BTS3900E GSM in IP networking mode Parameter Site attribute s BTSNAME Parameter Name BTS name Example shanghai Source Network planning
52-6
Issue 01 (2010-05-20)
Parameter TYPE UPNODE SRN SN PN SVCMODE IP IPMSK GWIP BARCODE
Parameter Name BTS type Up Node Type Subrack No. Slot No. Port No. Service Type BTS IP BTS IP Mask BTS SeGW IP Address BTS Interface Board Bar Code Cell Name Cell Type MCC MNC LAC CI
Example BTS3900E_GS M BSC 0 26 0 IP 192.168.1.1 255.255.255.0 199.169.1.1 111122222233 33333 shanghai_0 DCS1800 460 01 8240 2
Source Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning Unique identifier Network planning Network planning Network planning Network planning Network planning Network planning
Cell attribute s
DCELLNAME DCTYPE MCC MNC LAC CI
Procedure
Step 1 On the Local Maintenance Terminal, run the ADD AUTOPLANBTS command to add a BTS3900E GSM.

NOTE
When adding a BTS3900E GSM, you can set Service Type to TDM, HDLC, HDLC_HubBTS, or IP. Freq. and BSIC Automatic Plan Arithmetic Switch, Freq. and BSIC Automatic Optimize Arithmetic Switch, and Capacity and Coverage Automatic Optimize Arithmetic Switch is set to ON(ON) by default. Run the MOD AUTOPLANCFG command to select the automatic planning algorithms and automatic optimization algorithms.
----End
Example
An example script for adding the BTS3900E GSM in TDM networking mode is as follows:
ADD AUTOPLANBTS: BTSNAME="shanghai", TYPE=BTS3900E_GSM, UPNODE=BSC, SRN=0, SN=26, PN=0, SVCMODE=TDM, DCELLNAME="shanghai_0", DCTYPE=DCS1800, MCC="460", MNC="01", LAC=8240, CI=2;
52-8
Issue 01 (2010-05-20)
53 Configure DTM
53
Scenario Impact
Configure DTM
Dual Transfer Mode (DTM) is a 3GPP-defined standard function. This feature implements the simplified operation function of the class A mobile phone, that is, concurrent CS services and PS services. DTM allows simultaneous transfer of CS service and PS service. That is, a subscriber can send photos or browse websites during a call. The 3G network provides concurrent CS service and PS service. With DTM, the subscribers in a GSM network can enjoy services similar to those provided in a 3G network. In addition, in areas with insufficient 3G coverage, subscribers can use the services that are similar to 3G services through the 2G network. supports concurrent CS service and PS service. That is, a subscriber can provide PS service without disrupting the CS service. In DTM, NC2 is not supported because GPRS measurement reports are not reported. If DTM is enabled in a cell and the parameter Network Operation Mode of the GPRS attributes is not set to Network Operation Mode I, the A Interface Collaboration Paging Switch should be set to Open so that the network can page the MSs in packet transfer mode successfully.
NEs Involved BSC, BTS, MS, MSC, SGSN
Prerequisite
l l
The DTM function is license-controlled. Activate the license on the Local Maintenance Terminal. For details, see Activate BSC License. DTM requires the support of the BSC, MS, MSC, and SGSN. In addition, the MSC must support the COMMON ID message. DTM is used in built-in PCU configuration mode rather than in external PCU configuration mode. In an extended cell, DTM is not supported due to the limitation of the MS multislot capability. DTM is not supported in a cell enabled with the queuing function. After a cell is enabled with DTM, it is recommended that the early classmark sending control (ECSC) be set to Yes.
l l
Issue 01 (2010-05-20)
53 Configure DTM
Preparation
Table 53-1 Example of the negotiated and planned data for configuring the DTM Parameter ID IDXTYPE CELLNAME GPRS EDGE SUPPORTDTM SUPPORTENDTM ECSC Parameter Name Index Type Cell Name GPRS EDGE SupportDTM SupportEndTM ECSC Example BYNAME(By Name) CELL01 SupportAsInnPcu (SupportAsInnPcu) YES(Yes) SUPPORT(Support) SUPPORT(Support) YES(YES) Source Network planning Network planning Network planning Network planning Network planning Network planning Network planning
Procedure
Step 1 Run the SET CELLGPRS command to set GPRS to SupportAsInnPcu (SupportAsInnPcu),SupportDTM to SUPPORT(Support),SupportEndTM to SUPPORT (Support), configure the cell supports the DTM.
NOTE
Support Enhanced DTM, Support Class11 DTM, and Support HMC DTM cannot be set to Yes in BSC6000 V900R008C12. You are advised not to enable these functions during configuration.
Step 2 Run the MOD CELLCCBASIC command to set ECSC to YES(YES), configure the cell supports use early classmark sending. ----End
Example
An example script of configuring the DTM is as follows:
/*Configure the cell supports the DTM*/ SET CELLGPRS: IDXTYPE=BYNAME, CELLNAME="CELL01", GPRS=SupportAsInnPcu, EDGE=YES, SUPPORTDTM=SUPPORT, SUPPORTENDTM=SUPPORT; MOD CELLCCBASIC: IDXTYPE=BYNAME, CELLNAME="CELL01", ECSC=YES;
Postrequisite
l
Verifying DTM 1. 2. Use an MS supporting the DTM to make a call to a fixed-line phone and maintain the call. Connect the MS to the dialing terminal to set up the dial-up connection.
53-2
53 Configure DTM
3.
l
After the connection is successful, verify that the web page can be browsed and the call is not affected. On the Local Maintenance Terminal, run the SET CELLGPRS command to set SupportDTM to UNSUPPORT(Unsupport). Verifying the deactivation of DTM: The operations are the same as those for Verifying DTM. Verify that the web page cannot be browsed when the call is in progress.
Deactivating DTM 1. 2.
Issue 01 (2010-05-20)
53-3
54 Configuring VGCS/VBS
54
Scenario Impact None.
Configuring VGCS/VBS
This describes how to configure the VGCS/VBS. Compared with the original GSM system, the GSM-R has new features, such as the Voice Group Call Service (VGCS), Voice Broadcast Service (VBS), and enhanced Multi-Level Precedence and Pre-emption (eMLPP) service. The GSM-R can provide diversified voice dispatch services required in the private network. VGCS, VBS, and eMLPP.
NEs Involved BTS, BSC, and MSC
Preparation
The cell does not support the VGCS/VBS by default, that is, the default value of NCH Occupy Block Number is 0. Set NCH Occupy Block Number and NCH Start Block to configure the VGCS/VBS. When NCH Occupy Block Number is not 0, the BSC initiates the NCH messages to the MS in system information type 1. The MS initiates a VGCS/VBS call after receiving the message indicating that the system supports the VGCS/VBS. Table 54-1 Example of the data negotiated and planned for configuring the VGCS/VBS Data Type VGCS/ VBS Parameter ID IDXTYPE CELLNAME NCHOCBLOCKNU M NCHSTARTBLOCK eMLPP EMLPPPRIORITY Parameter Name Index Type Cell Name NCH Occupy Block Number NCH Start Block eMLPP Priority Example BYNAME (By Name) CELL_1 1 0 Priority4 (Priority 4) Source Network planning Network planning Network planning Network planning Network planning
Issue 01 (2010-05-20)
54-1
Procedure
Step 1 Configure the VGCS/VBS. 1. On the Local Maintenance Terminal, run the LST CELLGSMR command. Query the initial configuration of the VGCS/VBS of the current cell according to the index type. If NCH Occupy Block Number is set to 0, the current cell does not support the VGCS/VBS. On the Local Maintenance Terminal, run the MOD CELLGSMR command. Set NCH Occupy Block Number and NCH Start Block and run the command. Then, the BSC initiates a message to an MS. After receiving the message, the MS initiates a VGCS or VBS call in the group where the MS belongs.
NOTE
2.
NCH Occupy Block Number must not be 0. The number of NCH Occupy Block Number plus NCH Start Block must be smaller than or equal to the number of Number of CCCH blocks reserved for the AGCH. Run the LST CELLIDLEBASIC command to query the number of Number of CCCH blocks reserved for the AGCH.
3.
Run the LST CELLGSMR command and ensure that NCH Occupy Block Number is not 0. That is, the VGCS or VBS is successfully configured in the cell.
Step 2 Configure the eMLPP in the VGCS/VBS. On the Local Maintenance Terminal, run the MOD CELLGSMR command and set eMLPP Priorityin the VGCS/VBS. If the paging message priority is higher than the value of eMLPP Priority set on the BSC side, the BTS preferentially schedules the paging messages. ----End
Example
The example script of configuring the VGCS/VBS is as follows:
/*Configure the VGCS/VBS*/ /*Query the VGCS/VBS data configuration of CELL_1 and verify the number of blocks occupied by the NCH*/ LST CELLGSMR: IDXTYPE=BYNAME, BTSNAME="BTS_1", CNAME="CELL_1"; /*If NCH Occupy Block Number is 0, change NCH Occupy Block Number to 1 and NCH Start Block to 0*/ MOD CELLGSMR: IDXTYPE=BYNAME, CELLNAME="CELL_1", NCHOCBLOCKNUM=1, NCHSTARTBLOCK=0; /*Ensure that CELL_1 supports the VGCS/VBS*/ LST CELLGSMR: IDXTYPE=BYNAME, BTSNAME="BTS_1", CNAME="CELL_1"; /*Configure the eMLPP in the VGCS/VBS*/ MOD CELLGSMR: IDXTYPE=BYNAME, CELLNAME="CELL_1", EMLPPPRIORITY=Priority4;
Postrequisite
l
VGCS
Verifying VGCS 1. 2. Make MS 1 camp on the test cell. Then, use MS 1 to initiate a VGCS. The VGCS/VBS Setup, VGCS/VBS Setup Ack, VGCS/VBS Assignment Request, VGCS/VBS Assignment Result, and VGCS/VBS Talker Information messages are traced over the A interface. Observe the channel status of the test cell. The VGCS channel and a TCH are in the occupied state. Five seconds later, the TCH is released.
3.
54-2
4.
Make MS 2 camp on the test cell. Then, use MS 2 to initiate a VGCS with the same ID. MS 2 alerts that the VGCS exists. Then, MS 2 selects to join the VGCS and displays the VGCS ID. Hold on the PTT key on MS 2 to occupy the uplink. Then, observe the traced messages on the A interface and the information displayed on MS 1. The Uplink Request, Uplink Request Ack, Uplink Request Confirmation, and VGCS/VBS Talker Information messages are traced over the A interface. The number of MS 2 is displayed on MS 1 and the voice from MS 2 can be heard. Hold on the PTT key on MS 2 to occupy the uplink. At the same time, hold on the PTT key on MS 1 to occupy the uplink. The occupation of the uplink by MS 1 is refused. On the Local Maintenance Terminal, run the MOD CELLGSMR command to set NCH Occupy Block Number to 0. On the Local Maintenance Terminal, run the LST CELLGSMR command to check the setting of NCH Occupy Block Number. If the parameter is set to 0, it indicates that the VGCS function is deactivated.
5.
6.
Deactivating VGCS 1. 2.
VBS
Verifying VBS 1. The VGCS/VBS Setup, VGCS/VBS Setup Ack, VGCS/VBS Assignment Request, and VGCS/VBS Assignment Result messages are traced over the A interface. Observe the channel status of the test cell. The VBS channel and a TCH are found to be in the occupied state. Make MS 2 camp on the test cell. Then, use MS 2 to initiate a VBS with the same ID. MS 2 alerts that the VBS exists. After MS 2 selects to join the VBS, the number of MS 1 is displayed on MS 2 and the voice from MS 1 is heard. On the Local Maintenance Terminal, run the MOD CELLGSMR command to set NCH Occupy Block Number to 0. On the Local Maintenance Terminal, run the LST CELLGSMR command to check the setting of NCH Occupy Block Number. If the parameter is set to 0, it indicates that the VBS function is deactivated.
2. 3.
Deactivating VBS 1. 2.
Issue 01 (2010-05-20)
54-3
55 Configuring AMR
55
Scenario Impact None. NEs Involved MS, BTS, BSC, and MSC
Configuring AMR
The adaptive multi rate (AMR) is a speech encoding and decoding algorithm, which can be adjusted between full-rate speech version 3 and half-rate speech version 3 specified by the protocol. With AMR, the BTS and the MS can evaluate the interference on the radio network according to the measurements such as receive level, receive quality, and carrier-to-interference (C/I) ratio, and then adjust the voice encoding rate accordingly. In this way, both the antiinterference capability of the radio communications system and the voice quality are improved. The AMR function is used to balance the voice quality and the system capacity.
Prerequisite
l l
The AMR function is license-controlled. Activate the license on the Local Maintenance Terminal. For details, see Activate BSC License. The MS, BTS, and MSC support the AMR function.
Preparation
Table 55-1 Example of the data negotiated and planned for configuring AMR Data Type AMR basic parameter Parameter ID IDXTYPE CELLIDX AVer Parameter Name Index Type Cell Index A Interface Tag Example BYIDX(By Index) 0 GSM_PHASE_ 2Plus Source Network planning Network planning Network planning
Issue 01 (2010-05-20)
55-1
55 Configuring AMR
Data Type
Parameter ID VOICEVER
Parameter Name Speech Version AFR SACCH Multi-Frames AFR Radio Link Timeout AMR rate control switch AMR TFO Switch AMR Uplink Adaptive Threshold Allowed HO Control Switch Intracell F-H HO Allowed Intracell F-H HO Stat Time[s] Intracell F-H HO Last Time [s] F2H HO threshold H2F HO threshold Power Control Switch AMR PC Interval AMR MR. Compensation Allowed AMR UL MR. Number Predicted
Example Full_rate_Ver3 (Full-rate Ver 3) 48 64 ALG1 (Algorithm I) DISABLE (DISABLE) NO(NO)
AMR call processing parameter
AFRSAMULF RM AFRDSBLCNT RATECTRLS W AMRTFOSWI TCH AMRUADTHA W
AMR intra-cell TCHH-TCHF handover parameter
HOCTRLSWIT CH INTRACELLF HHOEN INFHHOSTAT INFHHOLAST
HOALGORIT HM1(HO Algorithm I) YES(YES) 5 4
INHOF2HTH INHOH2FTH AMR power control parameter PWRCTRLSW AMRPCADJPE RIOD AMRMRCOM PREG AMRULPRED LEND
25 12 HW2(HW2 Power Control) 3 YES(YES)
55-2
Issue 01 (2010-05-20)
55 Configuring AMR
Data Type
Parameter ID AMRDLPRED LEND
Parameter Name AMR DL MR. Number Predicted Ratio of AMRHR AMR TCH/H Prior Allowed AMR TCH/H Prior Cell Load Threshold
Example 0
AMR channel management parameter
ALLOWAMR HALFRATEUS ERPERC AMRTCHHPR IORALLOW AMRTCHHPR IORLOAD
100
YES(YES) 55
Procedure
Step 1 Set the AMR basic parameters. 1. 2. On the Local Maintenance Terminal, run the MOD BSCBASIC command to set A Interface Tag to GSM_PHASE_2Plus. On the Local Maintenance Terminal, run the MOD CELLCCACCESS command to set Speech Version to Full_rate_Ver3(Full-rate Ver 3). If the cell supports the half-rate service, select Half_rate_Ver3(Half-rate Ver 3) simultaneously. On the Local Maintenance Terminal, run the MOD CELLCCBASIC command to set AFR SACCH Multi-Frames and AFR Radio Link Timeout according to the actual network conditions. If the cell supports the half-rate service, set AHR SACCH MultiFrames and AHR AHR Radio Link Timeout simultaneously. On the Local Maintenance Terminal, run the MOD CELLCCAMR command to set the parameters related to the AMR call control of the TCHH or TCHF.
NOTE
Step 2 Configure the parameters related to the AMR call processing. 1.
2.
In A over IP mode, if Speech Version is set to Full_rate_Ver3(Full-rate Ver 3) and Half_rate_Ver3 (Half-rate Ver 3), the settings of AMR ACS[F]and AMR ACS[H] must be consistent with the settings on the CN side. Otherwise, calls cannot be set up.
Step 3 Set the parameters related to the AMR intra-cell TCHH-TCHF handover. On the Local Maintenance Terminal, run the SET CELLHOBASIC command to set the parameters related to the AMR intra-cell TCHH-TCHF handover.
l
When HO Control Switch is set to HOALGORITHM1(HO Algorithm I), set Intracell F-H HO Allowed to YES(YES), and set Intracell F-H HO Stat Time[s], Intracell F-H HO Last Time[s], F2H HO threshold, and H2F HO threshold. When HO Control Switch is set to HOALGORITHM2(HO Algorithm II), the relevant settings are as follows:
In the case of the AMR TCHH-to-TCHF handover, set AMR F-H Ho Allowed to YES (YES), and set the following parameters: AMR F-H Traffic Threshold, AMR F-H Ho Qual. Threshold, AMR F-H Ho ATCB Threshold, AMR F-H Ho Pathloss
Issue 01 (2010-05-20)
55 Configuring AMR
Threshold, AMR F-H Ho Pathloss Adjust Step, and AMR F-H Ho ATCB Adjust Step.
In the case of TCHF-to-TCHH handover, set AMR H-F Qaul. Ho Allowed to YES (YES), and set the following parameters: AMR H-F Ho Qual. Threshold, AMR H-F Traffic Threshold, AMR H-F Ho ATCB Threshold, and AMR H-F Ho Pathloss Threshold.
Step 4 Configure the parameters related to the AMR power control in a cell. On the Local Maintenance Terminal, run the MOD CELLPWRBASIC command to set Power Control Switch to HW2(HW2 Power Control) or HW3(HW3 Power Control). In addition, set AMR SACCH Downlink Power Upgrade according to the actual network conditions.
l
When Power Control Switch is set to HW2(HW2 Power Control), run the MOD CELLPWRHW2 command on the Local Maintenance Terminal to set the parameters related to Huawei II power control according to the actual network conditions. When Power Control Switch is set to HW3(HW3 Power Control), run the MOD CELLPWRHW3 command on the Local Maintenance Terminal to set the parameters related to Huawei III power control according to the actual network conditions.
Step 5 Set the parameters related to the AMR channel management in a cell. 1. 2. On the Local Maintenance Terminal, run the SET CELLCHMGBASIC command to set Ratio of AMR-HR according to the actual network conditions. On the Local Maintenance Terminal, run the MOD CELLCHMGAD command to set AMR TCH/H Prior Allowed and AMR TCH/H Prior Cell Load Threshold according to the actual network conditions.
----End
Example
/*Set the AMR basic parameters.*/ MOD BSCBASIC: AbisVer=GSM_PHASE_2Plus; MOD CELLCCACCESS: IDXTYPE=BYIDX, CELLIDX=0, VOICEVER=Full_rate_Ver1-0&Full_rate_Ver2-0 &Full_rate_Ver3-1&Half_rate_Ver1-0&Half_rate_Ver2-0&Half_rate_Ver3-0; /*Set the parameters related to the AMR call control.*/ MOD CELLCCBASIC: IDXTYPE=BYIDX, CELLIDX=0, AFRSAMULFRM=48, AFRDSBLCNT=64; MOD CELLCCAMR: IDXTYPE=BYIDX, CELLIDX=0, RATECTRLSW=ALG1, AMRTFOSWITCH=DISABLE, AMRUADTHAW=NO; /*Set the parameters related to the AMR intra-cell TCHF-TCHH handover.*/ SET CELLHOBASIC: IDXTYPE=BYIDX, CELLIDX=0, HOCTRLSWITCH=HOALGORITHM1, INTRACELLFHHOEN=YES, INFHHOSTAT=5, INFHHOLAST=4, INHOF2HTH=25, INHOH2FTH=12; /*Set the parameters related to the AMR power control in a cell.*/ MOD CELLPWRBASIC: IDXTYPE=BYIDX, CELLIDX=0, PWRCTRLSW=HW2, AMRSADLUPGRADE=0; MOD CELLPWRHW2: IDXTYPE=BYIDX, CELLIDX=0, AMRPCADJPERIOD=3, AMRMRCOMPREG=YES, AMRULPREDLEND=0, AMRDLPREDLEND=0; /*Configure the parameters related to the AMR channel management in a cell.*/ SET CELLCHMGBASIC: IDXTYPE=BYIDX, CELLIDX=0, ALLOWAMRHALFRATEUSERPERC=100; MOD CELLCHMGAD: IDXTYPE=BYIDX, CELLIDX=0, AMRTCHHPRIORALLOW=YES, AMRTCHHPRIORLOAD=55;
55-4
Issue 01 (2010-05-20)
55 Configuring AMR
Postrequisite
l
Verifying AMR 1. 2. Two MSs supporting AMR make calls. On the Local Maintenance Terminal, run the DSP CALLRES command to verify that Service Type in the TC Resource Information is set to FAMR or HAMR. Method 1: Set A Interface Tag to GSM_PHASE_1 or GSM_PHASE_2. In this case, none of the cells under the BSC supports AMR. 1. 2.
Deactivating AMR
On the Local Maintenance Terminal, run the MOD BSCBASIC command to set A Interface Tag to GSM_PHASE_1 or GSM_PHASE_2. On the Local Maintenance Terminal, run the LST BSCBASIC command to verify that A Interface Tag is set to GSM_PHASE_1 or GSM_PHASE_2.
Method 2: Deselect Full-rate Ver 3 and Half_rate_Ver3. In this case, only the current cell does not support AMR. 1. On the Local Maintenance Terminal, run the MOD CELLCCACCESS command to deselect Full_rate_Ver3(Full-rate Ver 3) and Half_rate_Ver3 (Half-rate Ver 3) in the Speech Version drop-down list. On the Local Maintenance Terminal, run the LST CELLCCACCESS command to verify that bit 3 and bit 6 from the right to the left of the Speech Version attribute are 0.
2.
Issue 01 (2010-05-20)
55-5
56 Configuring Dynamically Adjusting the Uplink MCS Coding
56
Configuring Dynamically Adjusting the Uplink MCS Coding

The BSS supports nine codec schemes: MCS-1 to MCS-9. With the Dynamically Adjusting the Uplink MCS Coding function, the uplink rate of an EGPRS user can be dynamically adjusted according to the actual network status. The BSC dynamically adjusts the codec scheme adopted by the PDCH according to the uplink measurement report reported by the BTS. In this manner, the codec scheme of the PDCH changes with the radio environment where the MS locates, thus improving the uplink throughput. Scenario Impact This feature increases the uplink rate of the EGPRS users, enhances the user experience, and improves the network quality. None.
Prerequisite
l l
The Dynamically Adjusting the Uplink MCS Coding function is not license-controlled. The GPRS/EGPRS function is enabled.
Preparation
Table 56-1 Example of the configuring dynamically adjusting the uplink MCS coding Parameter ID IDXTYPE CELLIDX UPFIXMCS Parameter Name Index Type Cell Index UpFixMcs Example BYCELLIDX(By Cell Index) 0 UNFIXED (UNFIXED) Source Network planning Network planning Network planning
Issue 01 (2010-05-20)
56-1
56 Configuring Dynamically Adjusting the Uplink MCS Coding
Procedure
Step 1 On the Local Maintenance Terminal, run theSET EGPRSPARA command to setUpFixMcs to UNFIXED(UNFIXED). ----End
Example
An example script for configuring dynamically adjusting the uplink MCS coding
SET EGPRSPARA: IDXTYPE=BYCELLIDX, CELLIDX=0, UPFIXMCS=UNFIXED;
Postrequisite
l
Verifying dynamically adjusting the uplink MCS coding
Start the trace of the messages on the Um interface in the PS domain. Verify that the coding scheme changes within Uplink Data Block (MCS-1) through Uplink Data Block (MCS-9) when uploading is performed on the PC connected to the EGPRS MS. On the Local Maintenance Terminal, run the SET EGPRSPARA command to set UpFixMcs to one value between MCS1 and MCS9. Verifying deactivation of dynamically adjusting the uplink MCS coding: The operations are the same as those for Verifying dynamically adjusting the uplink MCS coding. Verify that the coding scheme shown in the trace window does not change.
Deactivating dynamically adjusting the uplink MCS coding 1. 2.
56-2
Issue 01 (2010-05-20)
57 Configuring Concentric Cell
57
Scenario Impact None. NEs Involved BSC
Configuring Concentric Cell
A concentric cell is divided into an overlaid subcell and an underlaid subcell. Different frequency reuse patterns can be applied to the overlaid and underlaid subcells. The tight frequency reuse pattern is applied to the overlaid subcell. Therefore, the system capacity is expanded without affecting the voice quality.
Prerequisite
l
The concentric cell function is not license-controlled.
Preparation
Table 57-1 Example of the configuring concentric cell Data Type Cell attributes Parameter ID IDXTYPE BTSIDX CELLNAME CTYPE AST MCC Parameter Name Index Type BTS Index Cell Name Freq. Band Activity State MCC Example BYIDX(By Index) 0 cell GSM900 ACTIVATED (Activated) 460 Source Network planning Network planning Network planning Network planning Network planning Network planning
Issue 01 (2010-05-20)
57-1
Data Type
Parameter ID MNC LAC CI TRXBN TRXFREQ
Parameter Name MNC LAC CI TRX Board No. TRX Freq. Cell IUO Type Enhanced Concentric Allowed HW_Concentric Attribute Concentric Circles HO Allowed Current HO Control Algorithm UL to OL HO Allowed OL to UL HO Allowed RX_LEV for UO HO Allowed RX_QUAL for UO HO Allowed TA for UO HO Allowed
Example 00 1 1 0 1 Concentric_cell (Concentric cell) YES(Yes)
Source Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning
IUOTP ENIUO
TRX concentric attributes Cell handover basic parameters Cell concentric handover parameters
IUO
UNDERLAID (Underlaid Subcell) YES(Yes)
CONHOEN
HOCTRLSWITC H ULTOOLHOALL OW OLTOULHOALL OW RECLEVUOHOA LLOW RECQUALUOHO ALLOW TAFORUOHOAL LOW
HOALGORITH M1(HO Algorithm I) NO(NO) YES(Yes) YES(Yes) NO(NO) YES(Yes)
Procedure
Step 1 On the Local Maintenance Terminal, run the ADD CELL command to add a cell.
57-2
Issue 01 (2010-05-20)
Step 2 On the Local Maintenance Terminal, run the MOD CELLIUO command to set Cell IUO Type to Concentric_cell(Concentric cell), and set Enhanced Concentric Allowed according to the actual network conditions. Step 3 On the Local Maintenance Terminal, run the MOD TRXIUO command to set HW_Concentric Attribute of the TRX to OVERLAID(Overlaid Subcell) or UNDERLAID (Underlaid Subcell) according to the actual network conditions. Step 4 On the Local Maintenance Terminal, run the SET CELLHOBASIC command to set Concentric Circles HO Allowed to YES(Yes). Step 5 On the Local Maintenance Terminal, run the SET CELLHOIUO command to set the parameters related to the concentric cell handover according to the actual network conditions. ----End
Example
/*Add a cell.*/ ADD CELL: IDXTYPE=BYIDX, BTSIDX=0, CELLNAME="cell", CTYPE=GSM900, AST=ACTIVAED, MCC="460", MNC="00", LAC=1, CI=1, TRXBN=0, TRXFREQ=1; /*Configure the concentric attributes of the cell.*/ MOD CELLIUO: IDXTYPE=BYIDX, CELLIDX=0, IUOTP=Concentric_cell, ENIUO=YES; /*Configure the concentric attributes of the TRX.*/ MOD TRXIUO: IDXTYPE=BYIDX, CELLIDX=0, TRXBN=0, IUO=UNDERLAID; /*Set the basic handover parameters of the cell.*/ SET CELLHOBASIC: IDXTYPE=BYIDX, CELLIDX=0, HOCTRLSWITCH=HOALGORITHM1, CONHOEN=YES; /*Configure concentric handover parameters of the cell*/ SET CELLHOIUO: IDXTYPE=BYIDX, CELLIDX=0, HOCTRLSWITCH=HOALGORITHM1, ULTOOLHOALLOW=NO, OLTOULHOALLOW=YES, RECLEVUOHOALLOW=YES, RECQUALUOHOALLOW=NO, TAFORUOHOALLOW=YES;
Postrequisite
l
Verifying concentric cell 1. At the fringe of the test cell far from the BTS, use the test MS to make a call to a fixedline phone. Then, perform the test and record the frequencies used by the MS as the frequencies configured for the underlaid cell. Hold on the call and move the MS from the fringe of the test cell towards the BTS. Switch over the frequencies used by the MS to the frequencies used by the overlaid cell when the MS is near to the BTS. On the Local Maintenance Terminal, run the MOD CELLIUO command to set Cell IUO Type to Normal_cell(Normal cell) or EDB_cell(Enhanced double freq cell). On the Local Maintenance Terminal, run the MOD CELLIUO command. If Cell IUO Type is set to Normal_cell(Normal cell) or EDB_cell(Enhanced double freq cell), it indicates that the concentric cell function is deactivated. At the fringe of the test cell far from the BTS, use the test MS to make a call to the fixed-line phone. Then, perform the test and record the frequencies used by the MS.
2. 3.
l
Deactivating concentric cell 1.
2.
Verifying the deactivation of concentric cell 1.
Issue 01 (2010-05-20)
2. 3.
Hold on the call and move the MS from the fringe of the test cell towards the BTS. Verify that the frequencies used by the MS do not change when the MS is near to the BTS.
57-4
Issue 01 (2010-05-20)
58 Configuring Extended Cell
58
Scenario Impact None. NEs Involved BSC, BTS
Configuring Extended Cell
The application of extended cell breaks the coverage limit of 35 km of a GSM cell. This helps operators to provide wider coverage in special areas. The extended cell function is applicable in less populated areas with low signal fading such as deserts, seashores, islands, and water areas.
Prerequisite
l l
The extended cell function is license-controlled. Activate the license on the Local Maintenance Terminal. For details, see Activate BSC License. The extended cell function depends on the concentric cell function.
Preparation
Table 58-1 Example of the configuring extended cell Data Type Cell attributes Parameter ID IDXTYPE BTSIDX CELLNAME CTYPE AST Parameter Name Index Type BTS Index Cell Name Freq. Band Activity State Example BYIDX(By Index) 0 cell GSM900 ACTIVATED (Activated) Source Network planning Network planning Network planning Network planning Network planning
58-1
Issue 01 (2010-05-20)
Data Type
Parameter ID MCC MNC LAC CI TRXBN TRXFREQ
Parameter Name MCC MNC LAC CI TRX Board No. TRX Freq. Cell IUO Type Enhanced Concentric Allowed Cell Extension Type
Example 460 00 1 1 0 1 Concentric_cell (Concentric cell) YES(Yes)
Source Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning
IUOTP ENIUO
Cell extension type
EXTTP
DaulTst_ExtCell (Double Timeslot Extension Cell) UNDERLAID (Underlaid Subcell) YES(Yes)
TRX concentric attributes Cell handover basic parameters Cell concentric handover parameters
IUO
HW_Concentric Attribute Concentric Circles HO Allowed Current HO Control Algorithm UL to OL HO Allowed OL to UL HO Allowed RX_LEV for UO HO Allowed RX_QUAL for UO HO Allowed
Network planning Network planning Network planning Network planning Network planning Network planning Network planning
CONHOEN
HOCTRLSWITC H ULTOOLHOALL OW OLTOULHOALL OW RECLEVUOHOA LLOW RECQUALUOHO ALLOW
HOALGORITH M1(HO Algorithm I) NO(NO) YES(Yes) YES(Yes) NO(NO)
58-2
Issue 01 (2010-05-20)
Data Type
Parameter ID TAFORUOHOAL LOW
Parameter Name TA for UO HO Allowed
Example YES(Yes)
Procedure
Step 1 On the Local Maintenance Terminal, run the ADD CELL command to add a cell. Step 2 On the Local Maintenance Terminal, run the MOD CELLIUO command to set Cell IUO Type to Concentric_cell(Concentric cell), and set Enhanced Concentric Allowed according to the actual network conditions. Step 3 On the Local Maintenance Terminal, run the MOD CELLEXT command to set Cell Extension Type to DaulTst_ExtCell(Double Timeslot Extension Cell). Step 4 On the Local Maintenance Terminal, run the MOD TRXIUO command to set HW_Concentric Attribute of the TRX to OVERLAID(Overlaid Subcell) or UNDERLAID (Underlaid Subcell) according to the actual network conditions. Step 5 On the Local Maintenance Terminal, run the SET CELLHOBASIC command to set Concentric Circles HO Allowed to YES(Yes). Step 6 On the Local Maintenance Terminal, run the SET CELLHOIUO command to set the parameters related to the concentric cell handover according to the actual network conditions. ----End
Example
/*Add a cell.*/ ADD CELL: IDXTYPE=BYIDX, BTSIDX=0, CELLNAME="cell", CTYPE=GSM900, AST=ACTIVAED, MCC="460", MNC="00", LAC=1, CI=1, TRXBN=0, TRXFREQ=1; /*Configure the concentric attributes of the cell.*/ MOD CELLIUO: IDXTYPE=BYIDX, CELLIDX=0, IUOTP=Concentric_cell; /*Set the cell extension type.*/ MOD CELLEXT: IDXTYPE=BYIDX, CELLIDX=0, EXTTP=DaulTst_ExtCell; /*Configure the concentric attributes of the TRX.*/ MOD TRXIUO: IDXTYPE=BYIDX, CELLIDX=0, TRXBN=0, IUO=UNDERLAID; /*Set the basic handover parameters of the cell.*/ SET CELLHOBASIC: IDXTYPE=BYIDX, CELLIDX=0, HOCTRLSWITCH=HOALGORITHM1, CONHOEN=YES; /*Set the concentric handover parameters of the cell.*/ SET CELLHOIUO: IDXTYPE=BYIDX, CELLIDX=0, HOCTRLSWITCH=HOALGORITHM1, ULTOOLHOALLOW=NO, OLTOULHOALLOW=YES, RECLEVUOHOALLOW=YES, RECQUALUOHOALLOW=NO, TAFORUOHOALLOW=YES;
Postrequisite
l
Verifying extended cell 1. Start the monitoring of the channel status. For details, see Monitoring Channel Status in the BSC LMT User Guide.
Issue 01 (2010-05-20)
2.
Use an MS to call a fixed-line phone on the edge of the test cell. In the monitoring interface, verify that two adjacent TCHs with the same TRX No. turn into the working state. When the call is terminated, the TCHs turn into the idle state simultaneously. On the Local Maintenance Terminal, run the MOD CELLEXT command to set Cell IUO Type to Normal_cell(Normal cell). Verifying deactivation of extended cell: The operations are the same as those for Verifying extended cell. Verify that no two adjacent TCHs simultaneously change the state.
3.
l
Deactivating extended cell 1. 2.
58-4
Issue 01 (2010-05-20)
59 PS QoS
59
About This Chapter
PS QoS
PS QoS refers to GPRS/EGPRS QoS, that is, the quality of GPRS/EGPRS services on radio access network. The requirements for PS QoS are defined by QoS attributes, including the traffic class, transfer delay, maximum bit rate (MBR), guaranteed bit rate (GBR), traffic handling priority (THP), allocation/retention priority (ARP), and reliability. 59.1 Configuring Streaming QoS(GBR) For the streaming class services, after the QoS mechanism is introduced, the BSC allocates radio resources according to the guaranteed bit rate (GBR) of the QoS to ensure the data transmission rate. When the radio resources are insufficient, the subscribers with high priority can preempt the radio resources of the subscribers with low priority. 59.2 Configuring QoS ARP and THP After the QoS mechanism is introduced, the BSC allocates radio resources to the users according to the allocation/retention priority (ARP) and traffic handle priority (THP) of the QoS. The higher-priority users enjoy more radio resources and higher radio bandwidth. To be compatible with R97/R98 QoS, this feature supports the mapping between R97/98 QoS and R99 QoS. 59.3 Configuring PS Active Package Management With this feature, the server at the application layer adjusts the transmit rate based on the bandwidth that can be provided by the radio links, thus avoiding IP packet loss and timeout of the IP packet transmission. As a result, the performance of the services such as large-sized email sending, webpage browsing, and file transfer is improved. In addition, the packet performance is greatly improved when multiple services are processed simultaneously. 59.4 Configuring PoC QoS The push to talk over cellular (PoC) service is a type of real-time packet service that has high bandwidth and delay requirements. To guarantee the service quality and real-time performance, Huawei GBSS provides the QoS means such as GBR, reduced data transmission delay, and balanced uplink and downlink channel allocation.
Issue 01 (2010-05-20)
59-1
59 PS QoS
59.1 Configuring Streaming QoS(GBR)

For the streaming class services, after the QoS mechanism is introduced, the BSC allocates radio resources according to the guaranteed bit rate (GBR) of the QoS to ensure the data transmission rate. When the radio resources are insufficient, the subscribers with high priority can preempt the radio resources of the subscribers with low priority. Scenario Ensures sufficient and stable bandwidth for the streaming services. Ensures preferentially the bandwidth requirement and service experience of the subscribers with high priority when radio resources are insufficient. None.
Impact
NEs Involved BSC, MS, SGSN
Prerequisite
l l
The Streaming QoS(GBR) function is license-controlled. Activate the license on the Local Maintenance Terminal. For details, see Activate BSC License. The MS and SGSN support the packet flow management (PFM) procedure and the R99 QoS function. The GPRS/EGPRS function is enabled. The SGSN is configured.
l l
Preparation
Table 59-1 Example of the configuring streaming QoS(GBR) Parameter ID IDXTYPE CELLIDX PFCSUP GBRQOS QOSOPT STREAMSWH Parameter Name Index Type Cell Index PFC Support Support Gbr QoS Support QoS Optimize Occupy Switch of Streaming Resource Example BYCELLIDX(By Cell Index) 0 YES(Support) YES(Support) YES(Support) YES(YES) Source Network planning Network planning Network planning Network planning Network planning Network planning
59-2
Issue 01 (2010-05-20)
59 PS QoS
Procedure
Step 1 On the Local Maintenance Terminal, run theMOD NSE command to setPFC Support to YES(Support). Step 2 On the Local Maintenance Terminal, run theSET PSOTHERPARA command to setSupport Gbr QoS and Support QoS Optimize to YES(Support). Step 3 On the Local Maintenance Terminal, run theMOD BSCBASIC command to setOccupy Switch of Streaming Resource to YES(YES). ----End
Example
An example script of configuring streaming QoS(GBR) is as follows:
/*Modify NSE*/ MOD NSE: NSEI=1, PFCSUP=YES; /*Configure parameters of GPRS cell*/ SET PSOTHERPARA: IDXTYPE=BYCELLIDX, CELLIDX=0, GBRQOS=YES, QOSOPT=YES; /*Configure attributes of BSC*/ MOD BSCBASIC: STREAMSWH=YES;
Postrequisite
l
Verifying Streaming QoS
On the Local Maintenance Terminal, run the LST NSE command to verify that PFC Support is set to YES(Support). On the Local Maintenance Terminal, run the LST PSOTHERPARA command to verify that Support Gbr QoS and Support QoS Optimize are set to YES(Support). On the Local Maintenance Terminal, run the LST BSCBASIC command to check the setting of Occupy Switch of Streaming Resource. If the parameter is set to Yes, it indicates that the function of streaming QoS is activated. On the Local Maintenance Terminal, run the MOD BSCBASIC command to set Occupy Switch of Streaming Resource to NO(No). On the Local Maintenance Terminal, run the LST BSCBASIC command to check the setting of Occupy Switch of Streaming Resource. If the parameter is set to NO (No), it indicates that the function of streaming QoS is deactivated.
Deactivating streaming QoS 1. 2.
59.2 Configuring QoS ARP and THP

After the QoS mechanism is introduced, the BSC allocates radio resources to the users according to the allocation/retention priority (ARP) and traffic handle priority (THP) of the QoS. The higher-priority users enjoy more radio resources and higher radio bandwidth. To be compatible with R97/R98 QoS, this feature supports the mapping between R97/98 QoS and R99 QoS. Scenario Impact
Issue 01 (2010-05-20)
Ensuring the higher-priority user to obtain higher bandwidth, enjoy faster data rate, and thus obtain better QoS. None.
59 PS QoS
NEs Involved BSC
Prerequisite
l l
The QoS ARP and THP function is license-controlled. Activate the license on the Local Maintenance Terminal. For details, see Activate BSC License. The GPRS/EGPRS function is enabled.
Preparation
Table 59-2 Example of the configuring QoS ARP and THP Parameter ID IDXTYPE CELLIDX BKGARP1PRIWEIGH T BKGARP2PRIWEIGH T BKGARP3PRIWEIGH T Parameter Name Index Type Cell Index Background-ARP1 Priority Weight Background-ARP2 Priority Weight Background-ARP3 Priority Weight Example BYCELLIDX(By Cell Index) 0 4 2 1 Source Network planning Network planning Network planning Network planning Network planning
Procedure
Step 1 On the Local Maintenance Terminal, run theSET PSCHM command to set GPRS channel management parameters.
l
Set the following parameters to control the radio block budget weights of the interactive service: THP1-ARP1 Priority Weight, THP1-ARP2 Priority Weight, THP1-ARP3 Priority Weight, THP2-ARP1 Priority Weight, THP2-ARP2 Priority Weight, THP2ARP3 Priority Weight, THP3-ARP1 Priority Weight, THP3-ARP2 Priority Weight, and THP3-ARP3 Priority Weight. Set the following parameters to control the radio block budget weights of the background service: Background-ARP1 Priority Weight, Background-ARP2 Priority Weight, and Background-ARP3 Priority Weight. Set the following parameters to control the radio block budget weights of the BE service: BestEffort-ARP1 Priority Weight, BestEffort-ARP2 Priority Weight, and BestEffortARP3 Priority Weight.
----End
Example
An example script of configuring QoS ARP and THP is as follows:
59 PS QoS
SET PSCHM: IDXTYPE=BYCELLIDX, CELLIDX=0, BKGARP1PRIWEIGHT=4, BKGARP2PRIWEIGHT=2, BKGARP3PRIWEIGHT=1;
59.3 Configuring PS Active Package Management

With this feature, the server at the application layer adjusts the transmit rate based on the bandwidth that can be provided by the radio links, thus avoiding IP packet loss and timeout of the IP packet transmission. As a result, the performance of the services such as large-sized email sending, webpage browsing, and file transfer is improved. In addition, the packet performance is greatly improved when multiple services are processed simultaneously. Scenario Impact The feature is applicable to scenarios where congestion may occur because of bandwidth limitation. None.
NEs Involved BSC
Prerequisite
l l
The PS Active Package Management function is not license-controlled. The GPRS/EGPRS function is enabled.
Preparation
Table 59-3 Example of the configuring PS active package management Parameter ID AqmMinTh AqmTarTh AqmMaxTh AqmSwitch AqmNinit AqmNLowerBound AqmNUpBound AqmM Parameter Name Aqm MINth AAqm TarTh Aqm MaxTh Aqm Switch Aqm Ninit Aqm NLowerBound Aqm NUpBound Aqm M Example 256 384 1024 OPEN(Open) 20 10 20 20 Source Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning
Issue 01 (2010-05-20)
59-5
59 PS QoS
Procedure
Step 1 On the Local Maintenance Terminal, run theSET PSSOFTPARA command to setAqm Switch to OPEN(Open). Then, set the following parameters according to the network condition: Aqm MINth, Aqm TarTh, Aqm MaxTh, Aqm Ninit, Aqm NLowerBound, Aqm NUpBound, and Aqm M. ----End
Example
An example script of configuring PS active package management is as follows:
SET PSSOFTPARA: AqmMinTh=256, AqmTarTh=384, AqmMaxTh=1024, AqmSwitch=OPEN, AqmNinit=20, AqmNLowerBound=10, AqmNUpBound=20, AqmM=20;
Postrequisite
l
Verifying PS active package management
On the Local Maintenance Terminal, run the LST PSSOFTPARA command to check the setting of Aqm Switch. If the parameter is set to OPEN(Open), it indicates that PS active package management is activated.
Deactivating PS active package management 1. 2. On the Local Maintenance Terminal, run the SET PSSOFTPARA command to set Aqm Switch to CLOSE(Close). On the Local Maintenance Terminal, run the LST PSSOFTPARA command to check the setting of Aqm Switch. If the parameter is set to CLOSE(Close), it indicates that PS active package management is deactivated.
59.4 Configuring PoC QoS

The push to talk over cellular (PoC) service is a type of real-time packet service that has high bandwidth and delay requirements. To guarantee the service quality and real-time performance, Huawei GBSS provides the QoS means such as GBR, reduced data transmission delay, and balanced uplink and downlink channel allocation. Scenario Impact This feature guarantees the real-time performance of the PoC service, improves the voice quality of the PoC service. None.
NEs Involved BSC, MS
Prerequisite
l l l
The PoC QoS function is not license-controlled. The GPRS/EGPRS function is enabled. The Streaming QoS(GBR) function is configured.
59-6
59 PS QoS
Preparation
Table 59-4 Example of the configuring PoC QoS Parameter ID IDXTYPE CELLIDX POCGBRMIN POCGBRMAX POCDELAY Parameter Name Index Type Cell Index Min. GBR for POC Service Max. GBR for POC Service Transmission Delay of POC Service Example BYCELLIDX(By Cell Index) 0 6 16 650 Source Network planning Network planning Network planning Network planning Network planning
Procedure
Step 1 On the Local Maintenance Terminal, run theSET PSOTHERPARA command to set the following parameters according to the network condition: Min. GBR for POC Service, Max. GBR for POC Service, and Transmission Delay of POC Service. ----End
Example
An example script of configuring PoC QoS is as follows:
SET PSOTHERPARA: IDXTYPE=BYCELLIDX, CELLIDX=0, POCGBRMIN=6, POCGBRMAX=16, POCDELAY=650;
Issue 01 (2010-05-20)
59-7
60 Configuring Half-Rate
60
Scenario Impact None. NEs Involved BSC, MSC, MS
Configuring Half-Rate
Half-rate indicates that the voice coding rate decreases by half based on the new coding algorithm. In this way, a physical channel can carry the services of two half-rate MSs instead of the services of a full-rate MS. The feature applies to increase the network capacity and improve the frequency usage without increasing the hardware cost.
Prerequisite
l l
The half-rate function is license-controlled. Activate the license on the Local Maintenance Terminal. For details, see Activate BSC License.
Preparation
Table 60-1 Example of the configuring Half-Rate Parameter ID IDXTYPE BTSIDX MPMODE CELLIDX VOICEVER Parameter Name Index Type BTS Index Multiplexing Mode Cell Index Speech Version Example BYIDX(By Index) 0 MODE2_1 0 Half_rate_Ver1(Halfrate Ver 1) Source Network planning Network planning Network planning Network planning Network planning
60-1
Issue 01 (2010-05-20)
Parameter ID TRXBN CHNO CHTYPE TCHAJFLAG TCHBUSYTHRES
Parameter Name TRX Board No. Channel No. Channel Type TCH Rate Adjust Allow TCH Traffic Busy Threshold
Example 0 3 TCHHR(TCH Half Rate) YES(YES) 50
Procedure
Step 1 On the Local Maintenance Terminal, run theMOD BTSMPMODE command to set Multiplexing Mode to MODE1_1 or MODE2_1. Step 2 On the Local Maintenance Terminal, run theMOD CELLCCACCESS command to set Speech Version to Half_rate_Ver1(Half-rate Ver 1). Step 3 On the Local Maintenance Terminal, run theMOD CHAN command. Then, set Channel Type according to the network condition.
NOTE
Adhere to the following principles when configuring the channel type:

l l
To configure a channel as a TCHH fixedly, set its Channel Type to TCH Half Rate. To configure a channel as a TCHF fixedly or configure a channel with dynamic conversion between the TCHF and TCHH, set its Channel Type to TCH Full Rate.
Step 4 On the Local Maintenance Terminal, run theMOD TRXDEV command to set TCH Rate Adjust Allow to YES(YES).
NOTE
If a TRX does not have TCHHs and only has TCHFs, TCH Rate Adjust Allow needs to be enabled to support the half-rate service. For a TRX whose TCH Rate Adjust Allow is not enabled, channels on the TRX are assigned preferably. Therefore, the channels on the TRXs that support the rate adjustment can be reserved for further use. The resources can be used maximally.
Step 5 On the Local Maintenance Terminal, run theMOD CELLCHMGAD command to set TCH Traffic Busy Threshold to 50.If the value of this parameter exceeds 50, the channel will be converted from the TCHF to the TCHH.
NOTE
In channel assignment algorithms, the BSC determines to assign TCHHs or TCHFs based on the traffic volume of the network. If the channel seizure rate exceeds the TCH Traffic Busy Threshold, it indicates that the traffic volume of the current network is high. If the network is busy, TCHHs are assigned preferably. If the network is not busy, TCHFs are assigned preferably.
----End
Example
An example script of configuring Half-Rate is as follows:
/*Change the multiplexing mode of the Abis interface*/ MOD BTSMPMODE: IDXTYPE=BYIDX, BTSIDX=0, MPMODE=MODE2_1; /*Configure the half-rate speech version*/ MOD CELLCCACCESS: IDXTYPE=BYIDX, CELLIDX=0, VOICEVER=Half_rate_Ver1-1; /*Configure the channel type*/ MOD CHAN: IDXTYPE=BYIDX, CELLIDX=0, TRXBN=0, CHNO=3, CHTYPE=TCHHR; /*Enable the adjustment of the TCH rate*/ MOD TRXDEV: IDXTYPE=BYIDX, CELLIDX=0, TRXBN=0, TCHAJFLAG=YES; /*Configure the traffic busy threshold of the TCH*/ MOD CELLCHMGAD: IDXTYPE=BYIDX, CELLIDX=0, TCHBUSYTHRES=50;
Postrequisite
l
Verifying half-rate 1. 2. Use the MS to call a fixed-line phone in the test cell. On the Local Maintenance Terminal, run the DSP CALLRES command to view the call resources of an MS. If Speech Version is HR, it indicates that the half-rate function is activated. On the Local Maintenance Terminal, run the MOD CELLCCACCESS command to change Speech Version to a value other than Half_rate_Ver1 (Half-rate Ver 1). Verifying deactivation of half-rate: Use the MS to call a fixed-line phone in the test cell. Then, run the DSP CALLRES command to verify that Speech Version is not HR.
Deactivating half-rate 1. 2.
Issue 01 (2010-05-20)
60-3
61 Configuring MS High Multislot Classes
61
Prerequisite
Configuring MS High Multislot Classes

The function of MS high multislot classes enables the allocation of a maximum of five uplink/ downlink timeslots to an MS, thus increasing the uplink/downlink throughput of an MS. Scenario Impact The uplink/downlink throughput of an MS is increased. None.
NEs Involved BSC, MS
l l l
The function of MS high multislot classes is not license-controlled. The MS must support this function. If more than three timeslots are required on the uplink, the function of extended dynamic allocation must be enabled.
Preparation
Table 61-1 Example of the data negotiated and planned for configuring MS high multislot classes Parameter ID SUPPORTDL5TS Parameter Name Support High Multislot Class Example SUPPORT(Support) Source Network planning
Procedure
Step 1 On the Local Maintenance Terminal, run the SET PSSOFTPARA command to set Support High Multislot Class to SUPPORT(Support). ----End
Example
An example script for configuring the function of MS high multislot classes is as follows:
61 Configuring MS High Multislot Classes
/*Configure the function of MS high multislot classes*/ SET PSSOFTPARA: SUPPORTDL5TS=SUPPORT;
Postrequisite
l
Verifying MS high multislot classes 1. 2. 3. Start the tracing of the messages in the PS domain on the Um interface. For details, see Tracing PS Domain Messages on the Um Interface in the BSC LMT User Guide. Use an MS supporting the function of MS high multislot classes to download data in the test cell. Double-click the Packet Downlink Assignment message in the traced messages, and query the value of the timeslot-allocation information element (IE). Verify that the number of 1s in the value of the IE in the corresponding binary bitmap reaches the maximum number of downlink timeslots in the high multislot capability. On the Local Maintenance Terminal, run the SET PSSOFTPARA command to set Support High Multislot Class to NOTSUPPORT(Not Support). Verifying the deactivation of MS high multislot classes: The operations are the same as those for Verifying MS high multislot classes. Verify that the maximum number of 1s in the value of timeslot-allocation in the corresponding binary bitmap is four, which is smaller than the maximum number of downlink timeslots in the high multislot capability.
Deactivating MS high multislot classes 1. 2.
61-2
Issue 01 (2010-05-20)
62 Configuring Extended Dynamic Allocation(EDA)
62
Scenario Impact
Configuring Extended Dynamic Allocation(EDA)
The EDA function enables the allocation of more uplink timeslots to an MS, thus increasing the uplink throughput. The uplink rate is increased, and services with high traffic volume are implemented on the uplink. None.
NEs Involved BSC and MS
Prerequisite
l l
The EDA function is license-controlled. Activate the license on the Local Maintenance Terminal. For details, see Activate BSC License. The MS must support the EDA function.
Preparation
Table 62-1 Example of the data negotiated and planned for configuring EDA Parameter ID SUPPORTEDA Parameter Name Support EDA Example SUPPORT(Support) Source Network planning
Procedure
Step 1 On the Local Maintenance Terminal, run the SET PSSOFTPARA command to set Support EDA to SUPPORT(Support). ----End
62 Configuring Extended Dynamic Allocation(EDA)
Example
An example script for configuring the EDA function is as follows:
/*Configure the EDA function*/ SET PSSOFTPARA: SUPPORTEDA=SUPPORT;
Postrequisite
l
Verifying EDA 1. 2. 3. Start the tracing of the messages in the PS domain on the Um interface. For details, see Tracing PS Domain Messages on the Um Interface in the BSC LMT User Guide. Use an MS supporting the EDA function to upload data. Double-click the Packet Uplink Assignment message in the traced messages, and query the values of is-tn0 to is-tn7 in the timeslot-allocation-power-ctrl information element (IE). Verify that the number of 1s in the values of is-tn0 to is-tn7 exceeds two. On the Local Maintenance Terminal, run the SET PSSOFTPARA command to set Support EDA to NOTSUPPORT(Not Support). Verifying the deactivation of EDA: The operations are the same as those for Verifying EDA. Verify that the maximum number of is-tn0 to is-tn7 with the value being one in the timeslot-allocation-power-ctrl message is two.
Deactivating EDA 1. 2.
62-2
Issue 01 (2010-05-20)
63 Configuring CS-3/CS-4
63
Configuring CS-3/CS-4
The CS-3/CS-4 function enables the BSC to automatically adjust the coding scheme to a higher one in the area with a low bit error rate based on the existing coding scheme of a GPRS MS and the transmission quality of the MS. In this manner, a higher throughput is provided. The rate of GPRS services is increased, and the performance of GPRS services is improved in the area where the EGPRS services are not put into operation.
Prerequisite
l l
The CS-3/CS-4 function is license-controlled. Activate the license on the Local Maintenance Terminal. For details, see Activate BSC License.
Preparation
Table 63-1 Example of the data negotiated and planned for configuring CS-3/CS-4 Parameter ID IDXTYPE CELLIDX UPFIXCS DNFIXCS Parameter Name Index Type Cell Index Uplink Fixed CS Type Downlink Fixed CS Type Example BYIDX(By Index) 0 CS3(CS3) CS3(CS3) Source Network planning Network planning Network planning Network planning
Issue 01 (2010-05-20)
63-1
63 Configuring CS-3/CS-4
Procedure
Step 1 On the Local Maintenance Terminal, run the SET CELLPSCS command to set Uplink Fixed CS Type and Downlink Fixed CS Type to CS3(CS3) or CS4(CS4).
NOTE
If Uplink Fixed CS Type and Downlink Fixed CS Type are set to UNFIXED(UNFIXED), it indicates that the used coding scheme is adjusted dynamically.
----End
Example
An example script for configuring the CS-3/CS-4 function is as follows:
/*Configure the CS-3/CS-4 function*/ SET CELLPSCS: IDXTYPE=BYCELLIDX, CELLIDX=0, UPFIXCS=CS3, DNFIXCS=CS4;
Postrequisite
l
Verifying CS-3/CS-4 1. 2. Start the tracing of the messages in the PS domain on the Um interface. For details, see Tracing PS Domain Messages on the Um Interface in the BSC LMT User Guide. When the Web browsing is performed on the PC connected to an MS performing GPRS services, verify that the Downlink Data Block (CS-3) or Downlink Data Block (CS-4) message is present. When the uploading is performed on the PC connected to an MS performing GPRS services, verify that the Uplink Data Block (CS-3) or Uplink Data Block (CS-4) message is present. On the Local Maintenance Terminal, run the SET CELLPSCS command to set Uplink Fixed CS Type and Downlink Fixed CS Type to CS1(CS1) or CS2(CS2). Verifying the deactivation of CS-3/CS-4: The operations are the same as those for Verifying CS-3/CS-4. Verify that the Downlink Data Block (CS-3), Downlink Data Block (CS-4), Uplink Data Block (CS-3), or Uplink Data Block (CS-4) message is not present.
3.
Deactivating CS-3/CS-4 1. 2.
63-2
Issue 01 (2010-05-20)
64 Configuring Network Operation Mode I
64
Configuring Network Operation Mode I

The function of network operation mode I enables the sending of the CS paging messages over PCCCHs, CCCHs, or PACCHs on the network side. The MS monitors only one paging channel. Scenario To enable the paging co-ordination function, the GBSS equipment must support network operation mode I, and the Gs interface (the interface between the MSC/ VLR and the SGSN) must exist. With the function of network operation mode I, the signaling traffic between the MS and the network is reduced, thus saving and optimizing radio resources. None.
Impact
NEs Involved BSC and MSC
Prerequisite
l l
The function of network operation mode I is license-controlled. Activate the license on the Local Maintenance Terminal. For details, see Activate BSC License. The Gs interface is already configured.
Preparation
Table 64-1 Example of the data negotiated and planned for configuring network operation mode I Parameter ID IDXTYPE CELLIDX NMO Parameter Name Index Type Cell Index Network Operation Mode Example BYIDX(By Index) 0 NMOI(Network Operation Mode I) Source Network planning Network planning Network planning
Issue 01 (2010-05-20)
64-1
64 Configuring Network Operation Mode I
Procedure
Step 1 On the Local Maintenance Terminal, run the SET PSBASE command to set Network Operation Mode to NMOI(Network Operation Mode I). ----End
Example
An example script for configuring the function of network operation mode I is as follows:
/*Configure the function of network operation mode I*/ SET PSBASE: IDXTYPE=BYCELLIDX, CELLIDX=0, NMO=NMOI;
Postrequisite
l
Verifying network operation mode I 1. 2. 3. Start the tracing of the messages in the PS domain on the Um interface. For details, see Tracing PS Domain Messages on the Um Interface in the BSC LMT User Guide. Use an MS to perform PS services in the test cell. Double-click the Packet PSI13 message. Verify that the value of nmo in the gprscell-options information element (IE) is network-Mode-of-operation-I. On the Local Maintenance Terminal, run the SET PSBASE command to set Network Operation Mode to NMOI(Network Operation Mode I). Verifying the deactivation of network operation mode I: The operations are the same as those for Verifying network operation mode I. Verify that the value of nmo in the gprs-cell-options IE is not network-Mode-of-operation-I.
Deactivating network operation mode I 1. 2.
64-2
Issue 01 (2010-05-20)
65 Configuring Pre-Processing of Measurement Report
65
Scenario Impact
Configuring Pre-Processing of Measurement Report
The function of pre-processing of measurement report enables the BTS to interpolate and filter measurement reports (MRs) and then report the results of the processed MRs to the BSC. In this manner, the BSC does not need to process the MRs, thus reducing the load of the BSC. The CPU load of the board for processing the signaling of the CS services is reduced, and the signaling on the Abis interface is decreased, thus minimizing the risks of Abis transmission congestion. None.
Prerequisite
l l
The function of pre-processing of measurement report is not license-controlled. The BTS must support this function.
Preparation
Table 65-1 Example of the data negotiated and planned for configuring the function of preprocessing of measurement report Parameter ID IDXTYPE CELLIDX BTSMESRPTPREPRO C PRIMMESPPT Parameter Name Index Type Cell Index MR.Preprocessing Transfer Original MR Example BYIDX(By Index) 0 YES(YES) NO(NO) Source Network planning Network planning Network planning Network planning
65-1
Issue 01 (2010-05-20)
65 Configuring Pre-Processing of Measurement Report
Parameter ID BSMSPWRLEV MRPREPROCFREQ
Parameter Name Transfer BS/MS Power Clas Sent Freq.of preprocessed MR
Example YES(YES) Once_ps(Once every second)
Procedure
Step 1 On the Local Maintenance Terminal, run the MOD CELLHOCTRL command to set MR.Preprocessing to YES(Yes) and set Transfer Original MR, Transfer BS/MS Power Class, and Sent Freq.of preprocessed MR as required. ----End
Example
An example script for configuring the function of pre-processing of measurement report is as follows:
/*Configure the function of pre-processing of measurement report*/ MOD CELLHOCTRL: IDXTYPE=BYIDX, CELLIDX=0, BTSMESRPTPREPROC=YES, PRIMMESPPT=NO, BSMSPWRLEV=YES, MRPREPROCFREQ=Once_ps;
Postrequisite
l
Verifying pre-processing of measurement report 1. 2. 3. Start the tracing of RSL messages on the Abis interface. For details, see Tracing RSL Messages on the Abis Interface in the BSC LMT User Guide. Use the MS to call a fixed-line phone in the test cell. Verify that the Preprocessed Measurement Result message is present. On the Local Maintenance Terminal, run the MOD CELLHOCTRL command to set MR.Preprocessing to NO(NO). Verifying the deactivation of pre-processing of measurement report: The operations are the same as those for Verifying pre-processing of measurement report. Verify that the Measurement Result message rather than the Preprocessed Measurement Result message is present.
Deactivating measurement report preprocessing 1. 2.
65-2
Issue 01 (2010-05-20)
66 Configuring Enhanced Measurement Report (EMR)
66
Configuring Enhanced Measurement Report (EMR)
The EMR is the downlink measurement report (MR) of a new type introduced in R99. Compared with the common MR, more measurement objects such as bit error probability (BEP) and frame erase ratio (FER) are included. In this manner, the performance of the power control algorithm and handover algorithm is improved. Scenario Impact The capability of monitoring the voice quality and the performance of the power control algorithm and handover algorithm are improved. None.
NEs Involved BSC and MS
Prerequisite
l l
The EMR is not license-controlled. The MS must support the EMR function.
Preparation
Table 66-1 Example of the data negotiated and planned for configuring EMR Parameter ID IDXTYPE CELLIDX MEASURETYPE Parameter Name Index Type Cell Index Report Type Example BYIDX(By Index) 0 Source Network planning Network planning
EnhMeasReport Network (Enhanced planning Measurement Report)
Issue 01 (2010-05-20)
66-1
66 Configuring Enhanced Measurement Report (EMR)
Procedure
Step 1 On the Local Maintenance Terminal, run the MOD CELLCCUTRANSYS command to set Report Type to EnhMeasReport(Enhanced Measurement Report). ----End
Example
An example script for configuring EMR is as follows:
/*Configure EMR*/ MOD CELLCCUTRANSYS: IDXTYPE=BYIDX, CELLIDX=0, MEASURETYPE=EnhMeasReport;
Postrequisite
l
Verifying EMR 1. 2. 3. Start the tracing of RSL messages on the Abis interface. For details, see Tracing RSL Messages on the Abis Interface in the BSC LMT User Guide. Use an MS supporting the EMR function to call a fixed-line phone in the test cell. Double-click the measurement result message. Verify that the value of the pd-orenhanced-meas-msgtype information element (IE) is 0x10. Double-click the SACCH Filling message. Verify that the value of report-type is enhancedmeasurement-report when the value of system-info-type is measurementinformation. On the Local Maintenance Terminal, run the MOD CELLCCUTRANSYS command to set Report Type to a value other than EnhMeasReport(Enhanced Measurement Report). Verifying the deactivation of EMR: The operations are the same as those for Verifying EMR. Double-click the SACCH Filling message. Verify that the value of reporttype is not enhanced-measurement-report when the value of system-info-type is measurement-information.
Deactivating EMR 1.
2.
66-2
Issue 01 (2010-05-20)
67 Configuring Automatic Frequency Correction(AFC)
67
Scenario Impact
Configuring Automatic Frequency Correction(AFC)
The automatic frequency correction (AFC) function uses a special balancing algorithm to estimate the difference between the standard frequency and the frequency of the GMSK signal sent from the fast-moving MS to the BTS. The AFC estimates the frequency offset between the frequency of each received burst and the standard frequency in real time. Then, the estimated frequency offset is used to correct the RX working frequency of the BTS. The stable and reliable connection between the MS and the BTS in the case of high-speed mobile communications is ensured. None.
NEs Involved BSC
Prerequisite
l
AFC is not license-controlled.
Preparation
Table 67-1 Example of the data negotiated and planned for configuring AFC Parameter ID IDXTYPE CELLIDX FREQADJ Parameter Name Index Type Cell Index Frequence Adjust Switch Example BYIDX(By Index) 0 YES(YES) Source Network planning Network planning Network planning
Issue 01 (2010-05-20)
67-1
67 Configuring Automatic Frequency Correction(AFC)
Procedure
Step 1 On the Local Maintenance Terminal, run the MOD CELLOTHEXT command to set Frequence adjust switch to YES(YES). ----End
Example
An example script for configuring AFC is as follows:
/*Configure AFC*/ MOD CELLOTHEXT: IDXTYPE=BYIDX, CELLIDX=0, FREQADJ=YES;
Postrequisite
l
Verifying AFC 1. 2. 3. Start the tracing of RSL messages on the Abis interface. For details, see Tracing RSL Messages on the Abis Interface in the BSC LMT User Guide. Use the MS to call a fixed-line phone in the test cell, and hold on the call. Double-click the measurement result message. Verify that the frequency-shiftupmeasure information element (IE) is included in the message. On the Local Maintenance Terminal, run the MOD CELLOTHEXT command to set Frequence adjust switch to NO(NO). Verifying the deactivation of AFC: The operations are the same as those for Verifying AFC. Verify that the frequency-shift-upmeasure IE is not included in the measurement result message.
Deactivating AFC 1. 2.
67-2
Issue 01 (2010-05-20)
68 Configuring Handover
68
About This Chapter
Configuring Handover
The service area of the GSM is composed of the cells with continuous coverage. To enable the subscribers to communicate without interruption and to optimize the network performance, the handover technique is introduced to the GSM system. 68.1 Configuring Basic Handover The basic handover is classified into edge handover, TA handover, Bad Quality (BQ) handover, and interference handover. 68.2 Configuring PBGT Handover A PBGT handover is performed in a neighboring cell with the lowest path loss in a period. In this manner, the user always receives services in a better serving cell, thus improving the voice quality. 68.3 Configuring Signal Level Rapid Fall Handover The algorithm of signal level rapid fall handover is more sensitive to level changes, thus preventing call drops due to a quick decrease in the level. 68.4 Configuring Load Handover The load handover enables the load balance between different cells. Specifically, the traffic of a heavy-loaded cell is transferred to an adjacent light-loaded cell in time. 68.5 Configuring Layered and Hierarchical Handover In the layered and hierarchical network, the layered and hierarchical handover enables the handover between different layers and hierarchies, thus evenly distributing the traffic on each frequency band. 68.6 Configuring Speed-Sensitive Handover The speed-sensitive handover function enables a fast-moving MS in a micro cell to be handed over to a macro cell, thus reducing the number of handovers and call drops and improving user experience and network KPIs. 68.7 Configuring Directed Retry Directed retry is a special handover. During the assignment process, the BSC initiates the directed retry procedure if no TCH is available in the serving cell or the load of the serving cell is heavy. In this way, the MS is handed over to a neighboring cell. 68.8 Configuring Chain Cell Handover
The chain cell handover function enables a fast-moving MS to be preferentially handed over to a chain neighboring cell. 68.9 Configuring Better Cell Handover Evolving from the inter-layer handover and PBGT handover in handover algorithm I, the better cell handover is the specific handover decision in handover algorithm II.
68-2
Issue 01 (2010-05-20)
68.1 Configuring Basic Handover

The basic handover is classified into edge handover, TA handover, Bad Quality (BQ) handover, and interference handover. Scenario Impact The continuity of a call is ensured. None.
NEs Involved BSC
Prerequisite
l
The basic handover function is not license-controlled.
Preparation
Table 68-1 Example of the data negotiated and planned for configuring basic handover Parameter ID IDXTYPE CELLIDX HOCTRLSWITCH FRINGEHOEN ULEDGETHRES DLEDGETHRES TAHOEN BQHOEN INTERFHOEN Parameter Name Index Type Cell Index HO Control Switch Edge Handover Allowed Edge HO UL RX_LEV Threshold Edge HO DL RX_LEV Threshold TA HO Allowed BQ HO Allowed Interference HO Allowed Example BYIDX(By Index) 0 HOALGORITHM1 (HO Algorithm I) YES(YES) 10 20 YES(YES) YES(YES) YES(YES) Source Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning
Issue 01 (2010-05-20)
68-3
NOTE
Edge handover: The edge handover is the handover based on level for avoiding call drops. When an edge handover is triggered, the level of the target cell must be higher than the level of the serving cell and the inter-cell handover hysterisis. The edge handover is triggered when the receive level of the serving cell is lower than the edge handover threshold, and when the P/N criterion is satisfied during a certain statistical period. In this manner, the communication quality of the MS is maintained to some extent. TA handover: TA can be used as a standard of restricting the size of a cell. When the BSC determines that the TA of an MS exceeds the specified maximum TA threshold, a TA handover is triggered. If a serving cell meets the requirement for a TA handover, the serving cell is punished after the handover is complete. In this manner, the handover to the serving cell due to other causes is prevented. To meet the special requirements of an extended cell, special processing is performed on the TA handover algorithm. BQ handover: The bit error ratio (BER) reflects the transmission quality of radio links. The BSC measures the transmission quality of radio links according to the quality level in the measurement report. A poor quality level may be caused by low signal power or inter-channel interference. When the receive quality of the serving cell is lower than the BQ handover threshold, the BQ handover algorithm is enabled to maintain the communication quality of the MS. If a serving cell meets the requirement for a BQ handover, the serving cell is punished after the handover is complete. In this manner, the handover to the serving cell due to other causes is prevented. Interference handover: When the receive level of a serving cell is good but the receive quality deteriorates, the interference handover algorithm is enabled to maintain the communication quality of the MS.
Procedure
l Configuring edge handover 1. On the Local Maintenance Terminal, run the SET CELLHOBASIC command to set Edge Handover Allowed to YES(YES) and set Edge HO UL RX_LEV Threshold and Edge HO DL RX_LEV Threshold as required.
When HO Control Switch is set to HOALGORITHM1(HO Algorithm I), set Edge HO Watch Time[s], Edge HO Valid Time[s], Edge HO AdjCell Watch Time[s], and Edge HO AdjCell Valid Time[s] as required. When HO Control Switch is set to HOALGORITHM2(HO Algorithm II), set Edge HO Watch Time[0.5s], Edge HO Valid Time[0.5s], Edge HO AdjCell Watch Time[0.5s], and Edge HO AdjCell Valid Time[0.5s] as required.
Configuring TA handover 1. 2. On the Local Maintenance Terminal, run the SET CELLHOBASIC command to set TA HO Allowed to YES(YES). Then, set the following parameters as required:
When HO Control Switch is set to HOALGORITHM2(HO Algorithm II), set TA HO watch time[0.5 s] and TA HO valid time[0.5 s] by running the SET CELLHOBASIC command on the Local Maintenance Terminal. On the Local Maintenance Terminal, run the MOD CELLHOIUO command to set Emergency Handover TA Threshold. On the Local Maintenance Terminal, run the SET CELLHOFITPEN command to set Penalty Time after TA HO[s] and Penalty Level after TA HO.
Configuring BQ handover 1. 2. On the Local Maintenance Terminal, run the SET CELLHOBASIC command to set BQ HO Allowed to YES(YES). Then, set the following parameters as required:
68-4
When HO Control Switch is set to HOALGORITHM2(HO Algorithm II), set BQ HO watch time[0.5 s] and BQ HO valid time[0.5 s] by running the SET CELLHOBASIC command on the Local Maintenance Terminal. In the case of non-AMR calls, set UL Qual. Threshold and DL Qual. Threshold by running the MOD CELLHOEMG command on the Local Maintenance Terminal. In the case of AMR FR calls, set DLQuaLimitAMRFR and ULQuaLimitAMRFR by running the SET CELLAMRQUL command on the Local Maintenance Terminal. In the case of AMR HR calls, set DLQuaLimitAMRHR and ULQuaLimitAMRHR by running the SET CELLAMRQUL command on the Local Maintenance Terminal.
Configuring interference handover 1. 2. On the Local Maintenance Terminal, run the SET CELLHOBASIC command to set Interference HO Allowed to YES(YES). Then, set the following parameters as required:
When HO Control Switch is set to HOALGORITHM2(HO Algorithm II), set Interfere HO static time[0.5 s] and Interfere HO valid time[0.5 s] by running SET CELLHOBASIC command and set Penalty time on interfere HO[s] by running the SET CELLHOFITPEN command on the Local Maintenance Terminal. In the case of non-AMR-FR calls, set RXQUAL1 to RXQUAL12 by running the SET CELLAMRQUL command on the Local Maintenance Terminal. In the case of AMR FR calls, set RXLEVOff and RXQUAL1 to RXQUAL12 by running the SET CELLAMRQUL command on the Local Maintenance Terminal.
----End
Example
An example script for configuring the basic handover function is as follows:
/*Configure edge handover*/ SET CELLHOBASIC: IDXTYPE=BYIDX, CELLIDX=0, FRINGEHOEN=YES, ULEDGETHRES=10, DLEDGETHRES=20; /*Configure TA handover*/ SET CELLHOBASIC: IDXTYPE=BYIDX, CELLIDX=0, /*Configure BQ handover*/ SET CELLHOBASIC: IDXTYPE=BYIDX, CELLIDX=0, /*Configuring interference handover*/ SET CELLHOBASIC: IDXTYPE=BYIDX, CELLIDX=0, INTERFHOEN=YES;
HOCTRLSWITCH=HOALGORITHM1,
HOCTRLSWITCH=HOALGORITHM1, TAHOEN=YES; HOCTRLSWITCH=HOALGORITHM1, BQHOEN=YES; HOCTRLSWITCH=HOALGORITHM1,
Postrequisite
l
Verifying basic handover
Verifying edge handover 1. Start the tracing of the BSSAP messages on the A interface. For details, see Tracing BSSAP Messages on the A Interface in the BSC LMT User Guide.
Issue 01 (2010-05-20)
2.
After the A interface tracing window is displayed, verify that the values of certain cause information elements in the Handover Performed message (intra-BSC handover) or Handover Required message (inter-BSC handover) are ecv_norm_a_uplink_strenth or ecv_norm_a_downlink_strenth. Start the tracing of the BSSAP messages on the A interface. For details, see Tracing BSSAP Messages on the A Interface in the BSC LMT User Guide. After the A interface tracing window is displayed, verify that the values of certain cause information elements in the Handover Performed message (intra-BSC handover) or Handover Required message (inter-BSC handover) are ecv_norm_a_distance. Start the tracing of the BSSAP messages on the A interface. For details, see Tracing BSSAP Messages on the A Interface in the BSC LMT User Guide. After the A interface tracing window is displayed, verify that the values of certain cause information elements in the Handover Performed message (intra-BSC handover) or Handover Required message (inter-BSC handover) are ecv_norm_a_uplink_quality or ecv_norm_a_downlink_quality. Start the tracing of the BSSAP messages on the A interface. For details, see Tracing BSSAP Messages on the A Interface in the BSC LMT User Guide. After the A interface tracing window is displayed, verify that the values of certain cause information elements in the Handover Performed message (intra-BSC handover) or Handover Required message (inter-BSC handover) are ecv_norm_a_uplink_interfere or ecv_norm_a_downlink_interfere.
Verifying TA handover 1. 2.
Verifying BQ handover 1. 2.
Verifying interference handover 1. 2.
Deactivating basic handover
Deactivating edge handover 1. 2. On the Local Maintenance Terminal, run the SET CELLHOBASIC command to set Edge HO Allowed to NO(NO). Verifying the deactivation of edge handover: The operations are the same as those for Verifying edge handover. Verify that the value of the cause information element in the Handover Performed or Handover Required message is not ecv_norm_a_uplink_strenth or ecv_norm_a_downlink_strenth. On the Local Maintenance Terminal, run the SET CELLHOBASIC command to set TA HO Allowed to NO(NO). Verifying the deactivation of TA handover: The operations are the same as those for Verifying TA handover. Verify that the value of the cause information element in the Handover Performed or Handover Required message is not ecv_norm_a_distance. On the Local Maintenance Terminal, run the SET CELLHOBASIC command to set BQ HO Allowed to NO(NO). Verifying the deactivation of BQ handover: The operations are the same as those for Verifying BQ handover. Verify that the value of the cause information
Deactivating TA handover 1. 2.
Deactivating BQ handover 1. 2.
68-6
element in the Handover Performed or Handover Required message is not ecv_norm_a_uplink_quality or ecv_norm_a_downlink_quality.
Deactivating interference handover 1. 2. On the Local Maintenance Terminal, run the SET CELLHOBASIC command to set Interference HO Allowed to NO(NO). Verifying the deactivation of interference handover: The operations are the same as those for Verifying interference handover. Verify that the value of the cause information element in the Handover Performed or Handover Required message is not ecv_norm_a_uplink_interfere or ecv_norm_a_downlink_interfere.
68.2 Configuring PBGT Handover

A PBGT handover is performed in a neighboring cell with the lowest path loss in a period. In this manner, the user always receives services in a better serving cell, thus improving the voice quality. Scenario Impact With this function, the user can camp on a better cell, thus enjoying better voice quality. None.
NEs Involved BSC
Prerequisite
l l
The PBGT handover function is not license-controlled. The PBGT handover function is effective only when HO algorithm I is enabled.
Preparation
Table 68-2 Example of the data negotiated and planned for configuring PBGT handover Parameter ID IDXTYPE CELLIDX HOCTRLSWITCH PBGTHOEN PBGTSTAT PBGTLAST Parameter Name Index Type Cell Index HO Control Switch PBGT HO Allowed PBGT Watch Time [s] PBGT Valid Time[s] Example BYIDX(By Index) 0 HOALGORITHM1 (HO Algorithm I) YES(YES) 3 2 Source Network planning Network planning Network planning Network planning Network planning Network planning
68-7
Issue 01 (2010-05-20)
Procedure
Step 1 On the Local Maintenance Terminal, run the SET CELLHOBASIC command to set PBGT HO Allowed to YES(YES) and set PBGT Watch Time [s] and PBGT Valid Time[s] as required. ----End
Example
An example script for configuring the PBGT handover function is as follows:
/*Configure PBGT handover*/ SET CELLHOBASIC: IDXTYPE=BYIDX, CELLIDX=0, HOCTRLSWITCH=HOALGORITHM1, PBGTHOEN=YES, PBGTSTAT=3, PBGTLAST=2;
Postrequisite
l
Verifying PGBT handover 1. 2. Start the tracing of the BSSAP messages on the A interface. For details, see Tracing BSSAP Messages on the A Interface in the BSC LMT User Guide. After the A interface tracing window is displayed, verify that certain cause information elements in the Handover Performed message (intra-BSC handover) or Handover Required message (inter-BSC handover) are ecv_norm_a_better_cell. On the Local Maintenance Terminal, run the SET CELLHOBASIC command to set PBGT HO Allowed to NO(NO).
Deactivating PBGT handover 1.
68.3 Configuring Signal Level Rapid Fall Handover

The algorithm of signal level rapid fall handover is more sensitive to level changes, thus preventing call drops due to a quick decrease in the level. Scenario With this function, if the level of a user quickly decreases during a call because the call is made in a corner or a concave ground or because the components of the BTS component become ineffective, a handover is performed to prevent call drops. None.
Impact
NEs Involved BSC
Prerequisite
l l
The function of signal level rapid fall handover is not license-controlled. The function of signal level rapid fall handover is effective only when HO algorithm I is enabled.
68-8
Preparation
Table 68-3 Example of data negotiated and planned for configuring signal level rapid fall handover Parameter ID IDXTYPE CELLIDX HOCTRLSWITCH RXQCKFALLHOEN Parameter Name Index Type Cell Index HO Control Switch Rx_Level_Drop HO Allowed Example BYIDX(By Index) 0 HOALGORITHM1 (HO Algorithm I) YES(YES) Source Network planning Network planning Network planning Network planning
Procedure
Step 1 On the Local Maintenance Terminal, run the SET CELLHOBASIC command to set Rx_Level_Drop HO Allowed to YES(YES). ----End
Example
An example script for configuring the function of signal level rapid fall handover is as follows:
/*Configure signal level rapid fall handover*/ SET CELLHOBASIC: IDXTYPE=BYIDX, CELLIDX=0, HOCTRLSWITCH=HOALGORITHM1, RXQCKFALLHOEN=YES;
Postrequisite
l
Verifying signal level rapid fall handover 1. 2. Start the tracing of the BSSAP messages on the A interface. For details, see Tracing BSSAP Messages on the A Interface in the BSC LMT User Guide. After the A interface tracing window is displayed, verify that the values of certain cause information elements (IEs) in the Handover Performed message (intra-BSC handover) or Handover Required message (inter-BSC handover) are ecv_norm_a_uplink_strenth. On the Local Maintenance Terminal, run the SET CELLHOBASIC command to set Rx_Level_Drop HO Allowed to NO(NO).
Deactivating signal level rapid fall handover 1.
68.4 Configuring Load Handover

The load handover enables the load balance between different cells. Specifically, the traffic of a heavy-loaded cell is transferred to an adjacent light-loaded cell in time.
Scenario Impact
The load between cells is shared, thus alleviating congestion. In hot spots, congestion can be effectively reduced. None.
NEs Involved BSC
Prerequisite
l
The load handover function is not license-controlled.
Preparation
Table 68-4 Example of the data negotiated and planned for configuring load handover Parameter ID IDXTYPE CELLIDX HOCTRLSWITCH LOADHOEN SYSFLOWLEV TRIGTHRES ACCTHRES LOADOFFSET PERIOD STEP Parameter Name Index Type Cell Index HO Control Switch Load HO Allowed System Flux Threshold for Load HO Load HO Threshold Load Req.on Candidate Cell Load HO Bandwidth Load HO Step Period Load HO Step Level Example BYIDX(By Index) 0 HOALGORITHM1 (HO Algorithm I) YES(YES) 10 90 85 25 10 5 Source Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning
Procedure
Step 1 On the Local Maintenance Terminal, run the SET CELLHOBASIC command to set Load HO Allowed to YES(YES). Step 2 On the Local Maintenance Terminal, run the SET CELLHOAD command to set the following parameters as required: System Flux Threshold for Load HO, Load HO Threshold, Load
Req.on Candidate Cell, Load HO Bandwidth, Load HO Step Period, and Load HO Step Level. ----End
Example
An example script for configuring the load handover function is as follows:
/*Configure load handover*/ SET CELLHOBASIC: IDXTYPE=BYIDX, CELLIDX=0, HOCTRLSWITCH=HOALGORITHM1, LOADHOEN=YES; SET CELLHOAD: IDXTYPE=BYIDX, CELLIDX=0, HOCTRLSWITCH=HOALGORITHM1, SYSFLOWLEV=10, TRIGTHRES=90, ACCTHRES=85, LOADOFFSET=25, PERIOD=10, STEP=5;
Postrequisite
l
Verifying load handover 1. 2. Start the tracing of the BSSAP messages on the A interface. For details, see Tracing BSSAP Messages on the A Interface in the BSC LMT User Guide. After the A interface tracing window is displayed, verify that certain cause information elements in the Handover Performed message (intra-BSC handover) or Handover Required message (inter-BSC handover) are ecv_norm_a_traffic.
Deactivating load handover 1. 2. On the Local Maintenance Terminal, run the SET CELLHOBASIC command to set Load HO Allowed to NO(NO). Verifying deactivation of load handover: The operations are the same as those for Verifying load handover. Verify that the cause information element in the Handover Performed or Handover Required message is not ecv_norm_a_traffic.
68.5 Configuring Layered and Hierarchical Handover

In the layered and hierarchical network, the layered and hierarchical handover enables the handover between different layers and hierarchies, thus evenly distributing the traffic on each frequency band. Scenario In a layered and hierarchical network, this function implements the even distribution of traffic, thus meeting the requirements of different networking modes. In a GSM900/DCS1800 multi-band network, this function enables the even distribution of traffic between different frequency bands, thus solving the problem of insufficient frequency resources. None.
Impact
NEs Involved BSC
Prerequisite
l
The function of layered and hierarchical handover is not license-controlled.

Issue 01 (2010-05-20)
l
The function of layered and hierarchical handover is effective only when HO algorithm I is enabled.
Preparation
Table 68-5 Example of the data negotiated and planned for configuring layered and hierarchical handover Parameter ID IDXTYPE CELLIDX HOCTRLSWITCH LEVHOEN LEVSTAT LEVLAST INLAYHOTH LEVHOHYST Parameter Name Index Type Cell Index HO Control Switch Level HO Allowed Layer HO Watch Time [s] Layer HO Valid Time[s] Inter-layer HO Threshold Inter-layer HO Hysteresis Example BYIDX(By Index) 0 HOALGORITHM1 (HO Algorithm I) YES(YES) 3 2 25 2 Source Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning
Procedure
Step 1 On the Local Maintenance Terminal, run the SET CELLHOBASIC command to set Level HO Allowed to YES(YES) and set the following parameters as required: Layer HO Watch Time[s], Layer HO Valid Time[s], Inter-layer HO Threshold, and Inter-layer HO Hysteresis. ----End
Example
An example script for configuring the function of layered and hierarchical handover is as follows:
/*Configure layered and hierarchical handover*/ SET CELLHOBASIC: IDXTYPE=BYIDX, CELLIDX=0, HOCTRLSWITCH=HOALGORITHM1, LEVHOEN=YES, LEVSTAT=3, LEVLAST=2, INLAYHOTH=25, LEVHOHYST=2;
68-12
Issue 01 (2010-05-20)
Postrequisite
l
Verifying layered and hierarchical handover 1. 2. Start the tracing of the BSSAP messages on the A interface. For details, see Tracing BSSAP Messages on the A Interface in the BSC LMT User Guide. After the A interface tracing window is displayed, verify that certain cause information elements in the Handover Performed message (intra-BSC handover) or Handover Required message (inter-BSC handover) are ecv_norm_a_better_cell. On the Local Maintenance Terminal, run the SET CELLHOBASIC command to set Level HO Allowed to NO(NO).
Deactivating layered and hierarchical handover 1.
68.6 Configuring Speed-Sensitive Handover

The speed-sensitive handover function enables a fast-moving MS in a micro cell to be handed over to a macro cell, thus reducing the number of handovers and call drops and improving user experience and network KPIs. Scenario Impact It is recommended that the speed-sensitive handover function be applied only in special areas such as highways to reduce the CPU load. None.
NEs Involved BSC
Prerequisite
l
The speed-sensitive handover function is not license-controlled.
Preparation
Table 68-6 Example of the data negotiated and planned for configuring speed-sensitive handover Parameter ID IDXTYPE CELLIDX HOCTRLSWITCH QCKMVHOEN Parameter Name Index Type Cell Index HO Control Switch MS Fast Moving HO Allowed Example BYIDX(By Index) 0 HOALGORITHM1 (HO Algorithm I) YES(YES) Source Network planning Network planning Network planning Network planning
Issue 01 (2010-05-20)
68-13
Procedure
Step 1 On the Local Maintenance Terminal, run the SET CELLHOBASIC command to set MS Fast Moving HO Allowed to YES(YES). Step 2 Then, set the following parameters as required:
l
When HO Control Switch is set to HOALGORITHM2(HO Algorithm II), set HCS HO watch time[0.5 s] and HCS HO valid time[0.5 s] by running the SET CELLHOBASIC command on the Local Maintenance Terminal. On the Local Maintenance Terminal, run the SET CELLHOAD command to set the following parameters: MS Fast-moving Watch Cells, MS Fast-moving Valid Cells, MS Fast-moving Time Threshold[s], Penalty on MS Fast Moving HO, and Penalty Time on Fast Moving HO[s].
----End
Example
An example script for configuring the speed-sensitive handover function is as follows:
/*Configure speed-sensitive handover*/ SET CELLHOBASIC: IDXTYPE=BYIDX, CELLIDX=0, HOCTRLSWITCH=HOALGORITHM1, QCKMVHOEN=YES;
Postrequisite
l
Verifying speed-sensitive handover 1. 2. Start the tracing of the BSSAP messages on the A interface. For details, see Tracing BSSAP Messages on the A Interface in the BSC LMT User Guide. After the A interface tracing window is displayed, verify that certain cause information elements in the Handover Performed message (intra-BSC handover) or Handover Required message (inter-BSC handover) are ecv_norm_a_better_cell. On the Local Maintenance Terminal, run the SET CELLHOBASIC command to set MS Fast Moving HO Allowed to NO(NO).
Deactivating speed-sensitive handover 1.
68.7 Configuring Directed Retry

Directed retry is a special handover. During the assignment process, the BSC initiates the directed retry procedure if no TCH is available in the serving cell or the load of the serving cell is heavy. In this way, the MS is handed over to a neighboring cell. Scenario The number of call access failures due to TCH congestion in the serving cell is reduced, and the call setup success rate is increased. In addition, the traffic load in each cell is balanced, thus preventing the load imbalance. None.
Impact
NEs Involved BSC
68-14
Issue 01 (2010-05-20)
Prerequisite
l
The directed retry function is not license-controlled.
Preparation
Table 68-7 Example of the data negotiated and planned for configuring directed retry Parameter ID IDXTYPE CELLIDX DIRECTRYEN Parameter Name Index Type Cell Index Direct Retry Example BYIDX(By Index) 0 YES(YES) Source Network planning Network planning Network planning
Procedure
Step 1 On the Local Maintenance Terminal, run the MOD CELLBASICPARA command to set Directed Retry to YES(YES). ----End
Example
An example script for configuring the directed retry function is as follows:
/*Configure directed retry*/ MOD CELLBASICPARA: IDXTYPE=BYIDX, CELLIDX=0, DIRECTRYEN=YES;
Postrequisite
l
Verifying directed retry 1. 2. Start the tracing of RSL messages on the Abis interface. For details, see Tracing RSL Messages on the Abis Interface in the BSC LMT User Guide. After the Abis interface tracing window is displayed, the hando_det message is displayed. On the Local Maintenance Terminal, run the MOD CELLBASICPARA command to set Directed Retry to NO(NO). Verifying deactivation of directed retry: The operations are the same as those for Verifying directed retry. Verify that the hando_det message is not displayed.
Deactivating directed retry 1. 2.
68.8 Configuring Chain Cell Handover

The chain cell handover function enables a fast-moving MS to be preferentially handed over to a chain neighboring cell.
Scenario
With this function, the handover success rate of a fast-moving MS is increased, and the call continuity and low call drop rate are ensured. This function applies to the urban backbone roads, selected routes, and high-speed railroads. None.
Impact
NEs Involved BSC
Prerequisite
l l
The chain cell handover function is not license-controlled. The target cell must be a chain neighboring cell of the serving cell, which is controlled by the setting of Chain Neighbor Cell.
Preparation
Table 68-8 Example of the data negotiated and planned for configuring chain cell handover Parameter ID IDXTYPE CELLIDX HOCTRLSWITCH QUICKHOEN HOUPTRIGE HODOWNTRIGE MOVESPEEDTHRES HOSTATICTIME HOLASTTIME TIMEPUNISH HOPUNISHVALUE HOOFFSET Parameter Name Index Type Cell Index HO Control Switch Quick Handover Enable Quick Handover Up Triger Level[dB] Quick Handover Down Triger Level[dB] Quick Move Speed Thres[m/s] Quick Handover Static Time[0.5s] Quick Handover Last Time [0.5s] Quick Handover Punish Time[s] Quick Handover Punish Value[dB] Quick Handover Offset [dB] Example BYIDX(By Index) 0 HOALGORITHM1 (HO Algorithm I) YES(YES) 50 50 35 4 3 10 63 68 Source Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning Network planning
68-16
Issue 01 (2010-05-20)
Procedure
Step 1 On the Local Maintenance Terminal, run the SET CELLHOBASIC command to set Quick Handover Enable to YES(YES) and set PBGT Watch Time [s] and PBGT Valid Time[s] as required. Step 2 On the Local Maintenance Terminal, run the MOD CELLHOFAST command to set the parameters including Quick Handover Up Triger Level[dB], Quick Handover Down Triger Level[dB], Quick Move Speed Thres[m/s], Quick Handover Static Time[0.5s], Quick Handover Last Time [0.5s], Quick Handover Punish Time[s], Quick Handover Punish Value[dB], and Quick Handover Offset[dB]. ----End
Example
An example script for configuring the chain cell handover function is as follows:
/*Configure chain cell handover*/ SET CELLHOBASIC: IDXTYPE=BYIDX, CELLIDX=0, HOCTRLSWITCH=HOALGORITHM1, QUICKHOEN=YES; MOD CELLHOFAST: IDXTYPE=BYIDX, CELLIDX=0, HOUPTRIGE=50, HODOWNTRIGE=50, MOVESPEEDTHRES=35, HOSTATICTIME=4, HOLASTTIME=3, TIMEPUNISH=10, HOPUNISHVALUE=63, HOOFFSET=68;
Postrequisite
l
Verifying chain cell handover 1. 2. Start the tracing of the BSSAP messages on the A interface. For details, see Tracing BSSAP Messages on the A Interface in the BSC LMT User Guide. After the A interface tracing window is displayed, verify that the values of certain cause information elements (IEs) in the Handover Performed message (intra-BSC handover) or Handover Required message (inter-BSC handover) are ecv_norm_a_better_cell. On the Local Maintenance Terminal, run the SET CELLHOBASIC command to set Quick Handover Enable to NO(NO).
Deactivating chain cell handover 1.
68.9 Configuring Better Cell Handover

Evolving from the inter-layer handover and PBGT handover in handover algorithm I, the better cell handover is the specific handover decision in handover algorithm II. Scenario Impact None. None.
NEs Involved BSC
Prerequisite
l
The better cell handover function is not license-controlled.

Issue 01 (2010-05-20)
l
The better cell handover function is effective only when HO algorithm II is enabled.
Preparation
Table 68-9 Example of the data negotiated and planned for configuring better cell handover Parameter ID IDXTYPE CELLIDX HOCTRLSWITCH BETTERCELLHOEN BETTERCELLSTATTIME BETTERCELLLASTTIME Parameter Name Index Type Cell Index HO Control Switch Better Cell Handover Enable Better Cell HO Watch Time[s] Better Cell HO Valid Time[s] Example BYIDX(By Index) 0 HOALGORITHM2 (HO Algorithm II) YES(YES) 3 2 Source Network planning Network planning Network planning Network planning Network planning Network planning
Procedure
Step 1 On the Local Maintenance Terminal, run the SET CELLHOBASIC command to set Better Cell Handover Enable to YES(YES) and set Better Cell HO Watch Time[s] and Better Cell HO Valid Time[s] as required. ----End
Example
An example script for configuring the better cell handover function is as follows:
/*Configure better cell handover*/ SET CELLHOBASIC: IDXTYPE=BYIDX, CELLIDX=0, HOCTRLSWITCH=HOALGORITHM2, BETTERCELLHOEN=YES, BETTERCELLSTATTIME=3, BETTERCELLLASTTIME=2;
Postrequisite
l
Verifying better cell handover 1. 2. Start the tracing of the BSSAP messages on the A interface. For details, see Tracing BSSAP Messages on the A Interface in the BSC LMT User Guide. After the A interface tracing window is displayed, verify that the values of certain cause information elements (IEs) in the Handover Performed message (intra-BSC handover) or Handover Required message (inter-BSC handover) are ecv_norm_a_better_cell.
Deactivating better cell handover

68-18
1.
On the Local Maintenance Terminal, run the SET CELLHOBASIC command to set Better Cell Handover Enable to NO(NO).
Issue 01 (2010-05-20)
68-19
69 Configuring Flex Ater
69
Configuring Flex Ater
With the Flex Ater function, the Ater resources are allocated according to the service type during a call connection. If full-rate channels are used over the Um interface, the 16 kbit/s Ater resources are allocated. If half-rate channels are used over the Um interface, the 8 kbit/s Ater resources are allocated. When the TC subrack is configured remotely, the expenditure on transmission on the Ater interface is effectively reduced.
Prerequisite
l
The Flex Ater function is not license-controlled.
Preparation
Table 69-1 Example of the data negotiated and planned for configuring Flex Ater Parameter ID ATER8KSW ATERCONGSTRATIO ATERCONGHRFLAG Parameter Name Switch of 8K On Ater Congestion Ratio on Ater Resource[%] HR Allocation Flag while Ater Resource Congested Example YES 85 Open Source Network planning Network planning Network planning
Procedure
Step 1 On the Local Maintenance Terminal, run the SET OTHSOFTPARA command to set Switch of 8K On Ater to YES.
69 Configuring Flex Ater
When the Ater resources are insufficient, the half-rate Ater resources are preferentially allocated through the settings of Congestion Ratio on Ater Resource(%) and HR Allocation Flag while Ater Resource Congested. In this manner, the congestion of Ater resources is alleviated, and the processing capability of the system is improved. ----End
Example
An example script for configuring the Flex Ater function is as follows:
/*Configure Flex Ater*/ SET OTHSOFTPARA: Ater8KSw=YES, AterCongstRatio=85, AterCongHRFlag=Open;
Postrequisite
l
Verifying Flex Ater 1. 2. In a cell using half-rate channels, make a call using an MS supporting half-rate channels, and hold on the call. On the Local Maintenance Terminal, run the DSP CHNSTAT command to monitor the channel status. If you detect that any half-rate channel is occupied, start the querying of the Ater resources. For details, see Maintaining Ater Interface Resources in the BSC LMT User Guide. In the displayed querying results, verify that part of the occupied Ater resources is 8 kbit/s Ater resources. On the Local Maintenance Terminal, run the SET OTHSOFTPARA command to set Switch of 8K On Ater to NO.
3.
l
Deactivating Flex Ater 1.
69-2
Issue 01 (2010-05-20)
70 Configuring Abis Transmission Backup
70
Configuring Abis Transmission Backup

When the active SDH transmission link is faulty due to a natural disaster, the GBSS automatically switches the terrestrial TDM transmission link on the Abis interface to a backup satellite transmission link, thus maintaining the normal operation of the network. Scenario Impact This feature is applicable in the case of Abis over TDM and not applicable in the case of Abis over IP. None.
Prerequisite
l l
The Abis transmission backup function is license-controlled. Activate the license on the Local Maintenance Terminal. For details, see Activate BSC License. This function is applied only in the case of Abis over TDM.
Preparation
Table 70-1 Example of the data negotiated and planned for configuring Abis transmission backup Parameter ID IDXTYPE BTSIDX TRANSMODE Parameter Name Index Type BTS Index Transmission Mode Example BYIDX(By Index) 0 TER_AND_SAT_T RANS(Terrestrial and Satellite Transmission) Source Network planning Network planning Network planning
Issue 01 (2010-05-20)
70-1
70 Configuring Abis Transmission Backup
Procedure
Step 1 On the Local Maintenance Terminal, run the MOD BTSTRANS command to set Transmission Mode to TER_AND_SAT_TRANS(Terrestrial and Satellite Transmission). ----End
Example
An example script for configuring the Abis transmission backup function is as follows:
/*Configure Abis transmission backup*/ MOD BTSTRANS: IDXTYPE=BYIDX, BTSIDX=0, TransMode=TER_AND_SAT_TRANS;
Postrequisite
l
Deactivating Abis transmission backup 1. On the Local Maintenance Terminal, run the MOD BTSTRANS command to set Transmission Mode to a value other than TER_AND_SAT_TRANS(Terrestrial and Satellite Transmission).
70-2
Issue 01 (2010-05-20)
71 Configuring End-to-End MS Signaling Tracing
71
Configuring End-to-End MS Signaling Tracing
The function of end-to-end MS signaling tracing enables the tracing of faults of an NE based on the collected information about specified users with only a small number of resources occupied, thus facilitating fault rectification. Scenario Impact The information about the whole procedure related to a faulty user is collected. None.
NEs Involved BSC, HLR, and MSC/VLR
Prerequisite
l
The function of end-to-end MS signaling tracing is not license-controlled.
Preparation
Table 71-1 Example of the data negotiated and planned for configuring end-to-end MS signaling tracing Parameter ID END2ENDTRACESTATE AINTERMSGTRACE Parameter Name Support end-to-end user tracing function Trace A interface messages[end-to-end user tracing] Support BSS INVOKE TRACE message report [end-to-end user tracing] Example YES(YES) YES(YES) Source Network planning Network planning Network planning
HOCTRLSWITCH
YES(YES)
Issue 01 (2010-05-20)
71-1
71 Configuring End-to-End MS Signaling Tracing
Procedure
Step 1 On the Local Maintenance Terminal, run the SET OTHSOFTPARA command to set Support end-to-end user tracing function, Trace A interface messages[end-to-end user tracing], and Support BSS INVOKE TRACE message report[end-to-end user tracing] to YES(YES). ----End
Example
An example script for configuring the function of end-to-end MS signaling tracing is as follows:
/*Configure end-to-end MS signaling tracing*/ SET OTHSOFTPARA: End2EndTraceState=YES, AInterMsgTrace=YES, SendBssInvokeTrace=YES;
Postrequisite
l
Verifying end-to-end MS signaling tracing 1. 2. 3. Use the test MS to initiate a call. Start the tracing task management on the Abis interface. For details, see Maintaining Ater Interface Resources in the BSC LMT User Guide. Verify that at least one single-user tracing task that is initiated at the network side is present. On the Local Maintenance Terminal, run the SET OTHSOFTPARA command to set Support end-to-end user tracing function to NO(NO).
Deactivating end-to-end MS signaling tracing 1.
71-2
Issue 01 (2010-05-20)
72 Configuring PDCH Dynamic Adjustment
72
Configuring PDCH Dynamic Adjustment
The function of PDCH dynamic adjustment enables the automatic conversion between TCHs and PDCHs as required instead of configuring fixed PDCHs. With this function, the impact of GPRS services on the original GSM voice services is minimized, maintenance and configuration workloads are reduced, and the channel utilization and network capacity are improved.
Prerequisite
l l l
The PDCH dynamic adjustment function is not license-controlled. The GPRS/EGPRS services are configured. An external PCU is configured.
Preparation
Table 72-1 Example of the data negotiated and planned for configuring PDCH dynamic adjustment Parameter ID IDXTYPE CELLIDX TRXBN CHNO Parameter Name Index Type Cell Index TRX Board No. Channel No. Example BYIDX(By Index) 0 0 0 Source Network planning Network planning Network planning Network planning
72-1
Issue 01 (2010-05-20)
72 Configuring PDCH Dynamic Adjustment
Parameter ID CHTYPE
Example DPDCH(Dynamic PDCH)
Procedure
Step 1 On the Local Maintenance Terminal, run the MOD CHAN command to set Channel Type to DPDCH(Dynamic PDCH). ----End
Example
An example script for configuring the function of PDCH dynamic adjustment is as follows:
/*Configure PDCH dynamic adjustment*/ MOD CHAN: IDXTYPE=BYIDX, CELLIDX=0, TRXBN=0, CHNO=0, CHTYPE=DPDCH;
Postrequisite
l
Deactivating PDCH dynamic adjustment 1. On the Local Maintenance Terminal, run the MOD CHAN command to set Channel Type to DPDCH(Dynamic PDCH).
72-2
Issue 01 (2010-05-20)
73 Configuring 14.4 Kbps Circuit Switched Data
73
Configuring 14.4 Kbps Circuit Switched Data

Huawei GBSS supports the use of a single CS channel for transmitting PS services, including the 14.4 kbps CSD services. Scenario Impact Compared with ordinary circuit PS services, this function provides circuit PS services with a higher bandwidth. None.
NEs Involved BSC and MSC
Prerequisite
l l l l
The function of 14.4 kbps circuit switched data is not license-controlled. The IWF is configured in the MSC. The PS services are enabled in the HLR for the corresponding users. The MS must support the PS services.
Preparation
Table 73-1 Example of the data negotiated and planned for configuring 14.4 Kbps circuit switched data Parameter ID IDXTYPE CELLIDX DATATRAFFSET Parameter Name Index Type Cell Index Data service Allowed Example BYIDX(By Index) 0 T14_4K(4) Source Network planning Network planning Network planning
Issue 01 (2010-05-20)
73-1
73 Configuring 14.4 Kbps Circuit Switched Data
Procedure
Step 1 On the Local Maintenance Terminal, run the MOD CELLOTHEXT command to set Data service allowed to T14_4K(4). ----End
Example
An example script for configuring the function of 14.4 Kbps circuit switched data is as follows:
/*Configure 14.4 Kbps circuit switched data*/ MOD CELLOTHEXT: IDXTYPE=BYIDX, CELLIDX=0, DATATRAFFSET=T14_4K-1;
Postrequisite
l
Deactivating 14.4 Kbps circuit switched data 1. On the Local Maintenance Terminal, run the MOD CELLOTHEXT command to clear T14_4K(4) in the Data service allowed drop-down list.
73-2
Issue 01 (2010-05-20)

BSS Feature Configuration Guide (Based On MML) (V900R008C12 - 01)

Uploaded by

Copyright:

Available Formats

BSS Feature Configuration Guide (Based On MML) (V900R008C12 - 01)

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

BSS Feature Configuration Guide (Based On MML) (V900R008C12 - 01)

Uploaded by

Copyright:

Available Formats

HUAWEI BSC6000 Base Station Controller V900R008C12

BSS Feature Configuration Guide(Based on MML)

HUAWEI TECHNOLOGIES CO., LTD.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

About This Document

About This Document

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

About This Document

Technical support engineers Maintenance engineers

About This Document

About This Document

About This Document

About This Document

About This Document

About This Document

About This Document

About This Document

About This Document

About This Document

Convention { x | y | ... } [ x | y | ... ] { x | y | ... }*

About This Document

Action Double-click Drag

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

7 Configuring Ciphering.............................................................................................................7-1 8 Configuring Frequency Hopping............................................................................................8-1

14 Configuring BSS Paging Coordination.............................................................................14-1 15 Configuring a Co-BCCH Cell..............................................................................................15-1

22 Configuring Location Service..............................................................................................22-1

23 Configuring TFO....................................................................................................................23-1 24 Configuring PBT....................................................................................................................24-1

25 Configuring Transmit Diversity.........................................................................................25-1

26 Configuring 4-Way Receive Diversity...............................................................................26-1

32 Configuring the MSC Pool...................................................................................................32-1

33 Configuring BTS Ring Topology........................................................................................33-1

44.9 Deleting a Soft-Synchronized Network Task............................................................................................44-16

45 Configuring Entire Network Synchronization.................................................................45-1 46 Configuring BSS IP Transmission......................................................................................46-1

50 Configuring Multi-site Cell.................................................................................................50-1

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

52 Configuring BTS in automatic planning mode................................................................52-1

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

1 Changes in BSS Feature Configuration Guide (Based on MML)

Changes in BSS Feature Configuration Guide (Based on MML)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

2 Configuring the Multiband Network

Configuring the Multiband Network

About This Chapter

Huawei GSM BSS supports the following types of multiband networks:

GSM850 + GSM900 + DCS1800 GSM850 + GSM900 + PCS1900

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

2 Configuring the Multiband Network

2.1 Configuring a Multiband Network

NEs Involved MS, BTS, BSC, and MSC.

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

2 Configuring the Multiband Network

Parameter ID CPLMode TRXBN TRXTP TRXPN FREQ