Feature Activation Guide PDF

GBSS14.
Feature Activation Guide
Issue 06
Date 2013-04-15
HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2013. 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 a warranty of any kind, express or implied.
Huawei Technologies Co., Ltd.

Address: Huawei Industrial Base
Bantian, Longgang
Shenzhen 518129
People's Republic of China
Website: http://www.huawei.com
Email: support@huawei.com
Issue 06 (2013-04-15) Huawei Proprietary and Confidential i

Copyright © Huawei Technologies Co., Ltd.
GBSS14.0
Feature Activation Guide About This Document
About This Document
Purpose
This document provides guidelines for enabling or disabling a feature after initial configuration.
Based on the activation, verification, and deactivation of a feature in the feature list, the
guidelines aim to ensure that the feature is available on the network.
This document describes how to activate a license and configure a feature in GBSS.
NOTE
The BSC6900 is used as an example to describe the network controller in this document.
Product Version
The solution version is GBSS14.0 related to this document, for more details you can refer to the
following table.
Product Name Product Version
BSC6900 V900R014C00
BTS3900/BTS3900A/BTS3900L/ V100R014C00
BTS3900AL/DBS3900
Intended Audience
This document is intended for:
l Technical support engineers
l Maintenance engineers
l Field engineers
l Network optimization engineers
Organization
1 Changes in the GBSS Feature Activation Guide
Issue 06 (2013-04-15) Huawei Proprietary and Confidential ii

GBSS14.0
This chapter describes the changes in the GBSS Feature Activation Guide.
2 Feature Activation and License Item Descriptions
GBSSFeatures are classified into basic and optional features. Basic features are not license-
controlled and therefore do not require license activation before use. Some optional features are
license-controlled and therefore require license activation before use. If the Configuration
Method column for a basic feature in the RAN basic feature list is None, enabling this feature
does not involve any configurations. If the Configuration Method column for an optional feature
in the RAN optional feature list is None, this feature is enabled once it is activated.
3 Overview of Configurations on the CME
This section provides an overview of the configuration on the CME. The CME is a configuration
tool on GUIs assisting you to effectively configure the data about wireless NE features. You can
reconfigure configuration parameters by using the configuration expresses provided by the CME
to activate or deactivate specified features.
4 Activating the GSM License
This describes how to activate the GSM license.
5 Configuring Multi-band Sharing One BSC
This section describes how to activate, verify, and deactivate the basic feature GBFD-114401
Multi-band Sharing One BSC.
6 Configuring Emergency Call Service (TS12)
Emergency Call Service (TS12).
7 Configuring IMSI Detach
IMSI Detach.
8 Configuring HUAWEI I Handover
HUAWEI I Handover.
9 Configuring Directed Retry
Directed Retry.
10 Configuring Assignment and Immediate Assignment
Assignment and Immediate Assignment.
11 Configuring Call Reestablishment
Call Reestablishment.
12 Configuring TCH Re-assignment
TCH Re-assignment.
Issue 06 (2013-04-15) Huawei Proprietary and Confidential iii

GBSS14.0
13 Configuring Radio Link Management
This section describes how to activate, verify, and deactivate the link error indication procedure
of the basic feature GBFD-111002 Radio Link Management. Other procedures of the feature do
not need to be configured.
14 Configuring Faulty Management
This section describes how to activate, verify, and deactivate the OML detection function in the
optional feature MRFD-210304 Faulty Management.
15 Configuring BTS Software Management
This section describes how to activate, verify, and deactivate the integrity check function
introduced in the basic feature MRFD-210402 BTS Software Management. Other functions
involved in the feature do not need to be configured. (This feature cannot be configured using
the CME. )
16 Configuring Combined Cabinets and Cabinet Groups of BTSs
This section describes how to activate, verify, and deactivate the basic features GBFD-111501
BTS Combined Cabinet and GBFD-111502 BTS Hybrid Cabinet Group. (This feature cannot
be configured using the CME. )
17 Configuring Connection Inter BSC over IP
Connection Inter BSC over IP.
18 Configuring Link Aggregation
This section describes how to activate, verify, and deactivate the basic feature MRFD-210103
Link Aggregation.
19 Configuring Intelligent Shutdown of TRX Due to PSU Failure
Intelligent Shutdown of TRX Due to PSU Failure.
20 Configuring Call-Based Flow Control
Call-Based Flow Control.
21 Configuring Pre-Processing of Measurement Report
Pre-Processing of Measurement Report.
22 Configuring System Information Sending
System Information Sending.
23 Configuring Daylight Saving Time
Daylight Saving Time (DST).
24 Configuring SDCCH Dynamic Adjustment
Issue 06 (2013-04-15) Huawei Proprietary and Confidential iv

GBSS14.0
SDCCH Dynamic Adjustment.
25 Configuring Cell Frequency Scan
Cell Frequency Scan. (This feature cannot be configured using the CME. )
26 Configuring Signaling Transport Point (STP)
Signaling Transport Point (STP).
27 Configuring 14-Digit Signaling Point Code
14-Digit Signaling Point Code.
28 Configuring Discontinuous Reception (DRX)
Discontinuous Reception (DRX).
29 Configuring BTS Power Management
BTS Power Management.
30 Configuring Enhanced Power Control Algorithm
Enhanced Power Control Algorithm.
31 Configuring DTMF Downlink Message Filter
DTMF Downlink Message Filter.
32 Configuring High Speed Signaling
High Speed Signaling.
33 Configuring Guaranteed Emergency Call
Guaranteed Emergency Call.
34 Configuring License Control for Urgency
License Control for Urgency. (This feature cannot be configured using the CME. )
35 Configuring HUAWEI III Power Control Algorithm
HUAWEI III Power Control Algorithm.
36 Configuring the satellite transmission on the Pb interface
Satellite Transmission over Pb Interface. (This feature cannot be configured using the CME. )
Issue 06 (2013-04-15) Huawei Proprietary and Confidential v

GBSS14.0
37 Configuring PDCH Dynamic Adjustment

PDCH Dynamic Adjustment.
38 Configuring Connection with TMA
Connection with TMA (Tower Mounted Amplifier). (This feature cannot be configured using
the CME. )
39 Configuring Remote Electrical Tilt
Remote Electrical Tilt. (This feature cannot be configured using the CME. )
40 Configuring 2-Antenna Receive Diversity
2-Antenna Receive Diversity.
41 Configuring BTS Clock
BTS Clock. (This feature cannot be configured using the CME. )
42 Configuring Voice Fault Detection
Voice Fault Detection.
43 Configuring Abis Crossed Pair Diagnosis
Abis Crossed Pair Diagnosis.
44 Configuring IP Performance Monitor
IP Performance Monitor.
45 Configuring GSM PS Service Map
GSM PS Service Map.
46 Configuring Multi-mode BS Common CPRI Interface (GBTS)
Multi-mode BS Common CPRI Interface (GBTS).
47 Configuring Enhanced Full Rate (EFR)
This section describes how to activate, verify, and deactivate the GBFD-113301 Enhanced Full
Rate (EFR) feature.
48 Configuring Automatic Level Control (ALC)
The ALC feature adjusts the gains of uplink and downlink digital speech signals and changes
the amplitude of digital speech signals at an interval of 20 ms. This retains the speech signal
level in the entire network in a stable state and ensures that the speech quality is not affected by
Issue 06 (2013-04-15) Huawei Proprietary and Confidential vi

GBSS14.0
the volume fluctuation of both parties. This section describes how to activate, verify, and
deactivate the optional feature GBFD-115601 Automatic Level Control (ALC).
49 Configuring Acoustic Echo Cancellation (AEC)
The AEC helps reduce the acoustic echo caused by the terminal, improving the speech quality.
Acoustic echo is generated when the MS speaker is not completely isolated from the MS receiver.
After the voice of one party (Party A) reaches the MS, the voice is transmitted back to Party A
through the receiver. Then, Party A can hear his/her own voice. The phenomena is known as
acoustic echo. AEC is a feature with which acoustic echoes can be pre-assessed and eliminated
by means of the analysis on forward and backward voice signals. This section describes how to
activate, verify, and deactivate the optional feature GBFD-115602 Acoustic Echo Cancellation
(AEC).
50 Configuring Automatic Noise Restraint (ANR)
ANR reduces the background noise on the uplink and downlink speech signals and improves
the signal-to-noise ratio (SNR) and speech intelligibility. In this way, the other party of the call
can clearly hear the voice. This section describes how to activate, verify, and deactivate the
optional feature GBFD-115603 Automatic Noise Restraint (ANR).
51 Configuring TFO
This section describes how to activate, verify, and deactivate the optional feature GBFD-115701
TFO.
52 Configuring Automatic Noise Compensation (ANC)
By comparing the background noise level at the local end and the signal level at the peer end,
ANC adaptively increases the speech volume of the peer end if the background noise level of
the local end is high. Therefore, the ratio of the signal level at the peer end to the background
noise level at the local end increases, which helps to improve the voice quality. This section
describes how to activate, verify, and deactivate the optional feature GBFD-115703 Automatic
Noise Compensation (ANC).
53 Configuring Enhancement Packet Loss Concealment (EPLC)
Enhancement Packet Loss Concealment (EPLC).
54 Configuring EVAD
EVAD, namely enhanced voice activity detection.
55 Configuring Voice Quality Index (VQI)
Voice Quality Index (VQI).
56 Configuring Um Interface Speech Frame Repairing
Um Interface Speech Frame Repairing.
57 Configuring AMR
This section describes how to activate, verify, and deactivate the optional features GBFD-115501
AMR FR, GBFD-115502 AMR HR and GBFD-115503 AMR Power Control.
58 Configuring AMR Coding Rate Threshold Adaptive Adjustment
Issue 06 (2013-04-15) Huawei Proprietary and Confidential vii

GBSS14.0
AMR Coding Rate Threshold Adaptive Adjustment.
59 Configuring WB AMR
WB AMR.
60 Configuring Half Rate Speech (HR)
This section describes how to activate, verify, and deactivate the feature GBFD-113401 Half
Rate Speech (HR).
61 Configuring Dynamic Adjustment Between FR and HR
With GBFD-113402 Dynamic Adjustment Between FR and HR, the full-rate (FR) channels and
the half-rate (HR) channels are dynamically converted to automatically adapt to the proportions
of FR channels and HR channels in a cell during a call. In this manner, the situation in which
one type of channel is congested whereas the other type of channel is idle can be prevented. This
section describes how to activate, verify, and deactivate the optional feature GBFD-113402
Dynamic Adjustment Between FR and HR.
62 Configuring Dynamic HR/FR Adaptation
Dynamic HR/FR Adaptation.
63 Configuring VAMOS
VAMOS.
64 Configuring Mute SAIC MS Identification
Mute SAIC MS Identification. (This feature cannot be configured using the CME. )
65 Configuring VAMOS Call Drop Solution
VAMOS Call Drop Solution. (This feature cannot be configured using the CME. )
66 Configuring Short Message Service Cell Broadcast (TS23)
Short Message Service Cell Broadcast (TS23).
67 Configuring Simplified Cell Broadcast
Simplified Cell Broadcast. (This feature cannot be configured using the CME. )
68 Configuring VGCS and VBS
This section describes how to activate, verify, and deactivate Voice Group Call Service (VGCS)
and Voice Broadcast Service (VBS).
69 Configuring GSM-T Relay
GSM-T Relay.
Issue 06 (2013-04-15) Huawei Proprietary and Confidential viii

GBSS14.0
70 Configuring LCS (cell ID + TA)

LCS (cell ID + TA).
71 Configuring Lb Interface
Lb Interface.
72 Configuring Resource Reservation
Resource Reservation.
73 Configuring Enhanced Multi Level Precedence and Preemption (eMLPP)
Enhanced Multi Level Precedence and Preemption (eMLPP).
74 Configuring Flow Control Based on Cell Priority
Flow Control Based on Cell Priority.
75 Configuring Flow Control Based on User Priority
Flow Control Based on User Priority.
76 Configuring PS Service in Priority
PS Service in Priority.
77 Configuring GPRS
GPRS. (This feature cannot be configured using the CME. )
78 Configuring Network Operation Mode I
Network Operation Mode I.
79 Configuring EGPRS
EGPRS.
80 Configuring 11-Bit EGPRS Access
11-Bit EGPRS Access, GBFD-119203 Extended Uplink TBF and the basic feature
GBFD-119202 Packet Assignment Taken Over by the BTS. (This feature cannot be configured
using the CME. )
81 Configuring Packet Channel Dispatching
Packet Channel Dispatching.
Issue 06 (2013-04-15) Huawei Proprietary and Confidential ix

GBSS14.0
82 Configuring Streaming QoS(GBR)

Streaming QoS(GBR). (This feature cannot be configured using the CME. )
83 Configuring QoS ARP&THP
QoS ARP&THP. (This feature cannot be configured using the CME. )
84 Configuring PS Active Package Management
PS Active Package Management.
85 Configuring PoC QoS
PoC QoS.
86 Configuring Conversational QoS
Conversational QoS. (This feature cannot be configured using the CME. )
87 Configuring NC2
This section describes how to configure, verify, and deactivate the optional feature
GBFD-116201 Network Control Mode 2 (NC2).
88 Configuring Network Assisted Cell Change (NACC)
Network Assisted Cell Change (NACC) and GBFD-119801 Packet SI Status(PSI). (This feature
cannot be configured using the CME. )
89 Configuring BSS Paging Coordination
BSS Paging Coordination.
90 Configuring PS Handover
PS Handover. (This feature cannot be configured using the CME. )
91 Configuring PS Power Control
PS Power Control.
92 Configuring PDCH Dynamic Adjustment with Two Thresholds
PDCH Dynamic Adjustment with Two Thresholds.
93 Configuring Timeslot Multiplexing Priority for GPRS/EGPRS User
Timeslot Multiplexing Priority for GPRS/EGPRS User.
94 Configuring EDA
Issue 06 (2013-04-15) Huawei Proprietary and Confidential x

GBSS14.0
Extended Dynamic Allocation (EDA).
95 Configuring MS High Multislot Classes
MS High Multislot Classes.
96 Configuring DTM
DTM.
97 Configuring Class11 DTM
Class11 DTM.
98 Configuring HMC DTM
HMC DTM.
99 Configuring 14.4 kbit/s Circuit Switched Data
This chapter describes how to activate, verify, and deactivate the optional feature GBFD-119405
14.4 kbit/s Circuit Switched Data.
100 Configuring High Speed Circuit Switched Data
High Speed Circuit Switched Data.
101 Configuring Active TBF Allocation
Active TBF Allocation.
102 Configuring MSRD
This section describes how to activate, verify, and deactivate the optional feature GBFD 510801
Mobile Station Receive Diversity (MSRD).
103 Configuring Dual Carriers in Downlink
Dual Carriers in Downlink (DLDC).
104 Configuring the EGPRS2-A
Uplink EGPRS2-A and GBFD-510804 Downlink EGPRS2-A.
105 Configuring Latency Reduction
Latency Reduction.
106 Configuring IM Service Efficiency Improvement
The service-based differentiated PS service categorizes the specific services that have been
identified into several types according to their characteristics, and allocates different Um
Issue 06 (2013-04-15) Huawei Proprietary and Confidential xi

GBSS14.0
interface resources to MSs based on the service type and the user priority. This enhances the
Um interface resource usage, improves high-value services and the experience of high-priority
users. Five features are included: GBFD-511603 IM Service Efficiency Improvement,
GBFD-511604 Web Browsing Service Efficiency Improvement, GBFD-511605 Email Service
Efficiency Improvement, GBFD-511606 Streaming Media Service Resource Balancing, and
GBFD-511607 P2P Resource Balancing. This section describes how to activate, verify, and
deactivate the optional feature GBFD-511603 IM Service Efficiency Improvement.
107 Configuring Web Browsing Service Efficiency Improvement
deactivate the optional feature GBFD-511604 Web Browsing Service Efficiency Improvement.
108 Configuring Email Service Efficiency Improvement
deactivate the optional feature GBFD-511605 Email Service Efficiency Improvement.
109 Configuring Streaming Media Service Resource Balancing
deactivate the optional feature GBFD-511606 Streaming Media Service Resource Balancing.
110 Configuring P2P Resource Balancing
deactivate the optional feature GBFD-511607 P2P Resource Balancing.
111 Configuring WLAN Hot Spot Notification
Issue 06 (2013-04-15) Huawei Proprietary and Confidential xii

GBSS14.0
WLAN Hot Spot Notification.
112 Configuring Multiple CCCHs
Multiple CCCHs.
113 Configuring Layered Paging
Layered Paging.
114 Configuring Dynamic Multiple CCCH
In traffic surge scenarios such as holidays or emergencies, paging overload occurs, which greatly
affects services. In static multiple common control channel (CCCH) configuration mode, the
specific number of configured channels is difficult to determine. If the configured channels are
insufficient, paging overload cannot be resolved thoroughly; if excessive channels are
configured, channel resources are wasted. The Dynamic Multiple CCCH feature can resolve the
preceding issues. With this feature, if the load on the CCCHs increases, the TCHs corresponding
to timeslots 2, 4, and 6 on the BCCH TRX are dynamically converted to CCCHs in succession.
This increases the paging capability over the Um interface. If the load on the CCCHs decreases,
the CCCHs corresponding to timeslots 6, 4, and 2 on the BCCH TRX are dynamically converted
to TCHs in succession. This increases the resource usage. This section describes how to activate,
verify, and deactivate the optional feature GBFD-511503 Dynamic Multiple CCCH.
115 Configuring RACH Storm Filtration
RACH Storm Filtration.
116 Configuring Active Power Control
Active Power Control.
117 Configuring Discontinuous Transmission (DTX)-Downlink
Discontinuous Transmission (DTX)-Downlink.
118 Configuring Discontinuous Transmission (DTX)-Uplink
Discontinuous Transmission (DTX)-Uplink.
119 Configuring TRX Power Amplifier Intelligent Shutdown
TRX Power Amplifier Intelligent Shutdown.
120 Configuring TRX Power Amplifier Intelligent Shutdown on Timeslot Level
TRX Power Amplifier Intelligent Shutdown on Timeslot Level.
121 Configuring Intelligent Combiner Bypass
Intelligent Combiner Bypass.
Issue 06 (2013-04-15) Huawei Proprietary and Confidential xiii

GBSS14.0
122 Configuring Active Backup Power Control
Active Backup Power Control.
123 Configuring Power Optimization Based on Channel Type
Power Optimization Based on Channel Type.
124 Configuring PSU Smart Control
This section describes how to activate, verify, and deactivate the GBFD-111608 PSU Smart
Control feature. (This feature cannot be configured using the CME. )
125 Configuring Enhanced BCCH Power Consumption Optimization
This section describes how to activate, verify, and deactivate the GBFD-111609 Enhanced
BCCH Power Consumption Optimization feature.
126 Configuring Dynamic Cell Power Off
This section describes how to activate, verify, and deactivate the GBFD-111610 Dynamic Cell
Power Off feature.
127 Configuring TRX Working Voltage Adjustment
This section describes how to activate, verify, and deactivate the GBFD-111611 TRX Working
Voltage Adjustment feature.
128 Configuring Multi-Carrier Intelligent Voltage Regulation
This section describes how to activate, verify, and deactivate the GBFD-111612 Multi-Carrier
Intelligent Voltage Regulation feature.
129 Configuring Flex Abis
Flex Abis. (This feature cannot be configured using the CME. )
130 Configuring BTS Local Switch
BTS Local Switch.
131 Configuring Abis Transmission Optimization
Abis Transmission Optimization. (This feature cannot be configured using the CME. )
132 Configuring Abis Congestion Trigger HR Distribution
Abis Congestion Trigger HR Distribution. (This feature cannot be configured using the CME. )
133 Configuring Flex Ater
Flex Ater.
134 Configuring BSC Local Switch
Issue 06 (2013-04-15) Huawei Proprietary and Confidential xiv

GBSS14.0
BSC Local Switch.
135 Configuring Ater Compression Transmission
Ater Compression Transmission. (This feature cannot be configured using the CME. )
136 Configuring Local Multiple Signaling Points
Local Multiple Signaling Points.
137 Configuring PS Dummy Frame Compression
PS Dummy Frame Compression.
138 Configuring Clock over IP support 1588v2
Clock over IP support 1588v2.
139 Configuring Synchronous Ethernet
Synchronous Ethernet.
140 Configuring Abis over IP
Abis over IP.
141 Configuring Abis IP over E1/T1
Abis IP over E1/T1.
142 Configuring Abis MUX
Abis MUX.
143 Configuring Abis IPHC
Abis IPHC.
144 Configuring A over IP
A over IP.
145 Configuring A IP over E1/T1
A IP over E1/T1.
146 Configuring UDP MUX for A Transmission
UDP MUX for A Transmission.
Issue 06 (2013-04-15) Huawei Proprietary and Confidential xv

GBSS14.0
147 Configuring TDM/IP Dual Transmission over A Interface

TDM/IP Dual Transmission over A Interface. (This feature cannot be configured using the
CME. )
148 Configuring Gb over IP
Gb over IP.
149 Configuring Ethernet OAM
Ethernet OAM.
150 Configuring A Interface Transmission Pool
A Interface Transmission Pool. When an Ethernet Layer 3 networking is used, multiple IP
interface boards used by the A interface on the BSC form a resource pool and the IP addresses
for these interface boards also form a resource pool. Any interface board in the resource pool is
accessible to the core network (CN). The BSC selects an IP address from the resource pool for
bearing incoming services based on load balancing so that interface boards share resources in
the pool.
151 Configuring Satellite Transmission over Abis Interface
Satellite Transmission over Abis Interface. (This feature cannot be configured using the CME. )
152 Configuring Satellite Transmission over A Interface
Satellite Transmission over A Interface.
153 Configuring Satellite Transmission over Ater Interface
Satellite Transmission over Ater Interface. (This feature cannot be configured using the CME. )
154 Configuring Satellite Transmission over Gb Interface
Satellite Transmission over Gb Interface.
155 Configuring RAN Sharing
RAN Sharing.
156 Configuring MOCN Shared Cell
MOCN Shared Cell.
157 Configuring IMSI-Based Handover
IMSI-Based Handover.
158 Configuring Abis Independent Transmission
Issue 06 (2013-04-15) Huawei Proprietary and Confidential xvi

GBSS14.0
Abis Independent Transmission.
159 Configuring PICO/Compact BTS Automatic Configuration and Planning
PICO Automatic Configuration and Planning and GBFD-510701 Compact BTS Automatic
Configuration and Planning. (This feature cannot be configured using the CME. )
160 Configuring PICO Synchronization
PICO Synchronization.
161 Configuring PICO Dual-band Auto-planning
PICO Dual-band Auto-planning. (This feature cannot be configured using the CME. )
162 Configuring PICO USB Encryption
PICO USB Encryption.
163 Configuring PICO Sleeping Mode
PICO Sleeping Mode.
164 Configuring PICO Automatic Optimization
PICO Automatic Optimization. (This feature cannot be configured using the CME. )
165 Configuring PICO Transceiver Redundancy
PICO Transceiver Redundancy.
166 Configuring Weather Adaptive Power Management
This section describes how to manage a GBTS weather-adaptive energy conservation task on
the M2000. You can perform operations such creating, modifying, starting, deleting, and viewing
a task. After you create such a task and then start it on the M2000, the M2000 predicts the quantity
of electricity to be generated on GBTS solar panels based on weather data, and then periodically
generates power levels available to the GBTSs based on various types of information such as
generated electricity, remaining electricity of batteries, and GBTS power consumption.
167 Configuring Compact BTS Automatic Capacity Planning
Compact BTS Automatic Capacity Planning. (This feature cannot be configured using the
CME. )
168 Configuring Compact BTS Automatic Neighbor Cell Planning and Optimization
Compact BTS Automatic Neighbor Cell Planning and Optimization. (This feature cannot be
configured using the CME. )
169 Configuring Compact BTS Timing Power Off
Issue 06 (2013-04-15) Huawei Proprietary and Confidential xvii

GBSS14.0
Compact BTS Timing Power Off. (This feature cannot be configured using the CME. )
170 Configuring Local User Management
Local User Management.
171 Configuring Intelligent Battery Management
Intelligent battery management includes the automatic switch between battery management
modes, overtemperature protection, and leftover capacity. This section describes how to activate,
verify, and deactivate the optional feature GBFD-510710 Intelligent Battery Management.
172 Configuring PBT
Power Boost Technology (PBT).
173 Configuring Transmit Diversity
Transmit Diversity (TD).
174 Configuring 4-Way Receiver Diversity
4-Way Receiver Diversity. The 4-way receive diversity combines 4-way receive signals to
optimize the quality of uplink signals.
175 Configuring Dynamic Transmit Diversity
Dynamic Transmit Diversity.
176 Configuring Dynamic PBT
Dynamic PBT.
177 Configuring Enhanced EDGE Coverage
Enhanced EDGE Coverage.
178 Configuring Dynamic Power Sharing
Dynamic Power Sharing.
179 Configuring Extended Cell
Extended Cell.
180 Configuring Concentric Cell
Concentric Cell.
181 Configuring Co-BCCH Cell
Issue 06 (2013-04-15) Huawei Proprietary and Confidential xviii

GBSS14.0
Co-BCCH Cell.
182 Configuring Enhanced Dual-Band Network
Enhanced Dual-Band Network.
183 Configuring Flex MAIO
Flex Mobile Allocation Index Offset (MAIO).
184 Configuring ICC
ICC.
185 Configuring EICC
EICC.
186 Configuring Frequency Hopping (RF hopping, baseband hopping)
This section describes how to activate and verify the optional feature GBFD-113701 Frequency
Hopping (RF hopping, baseband hopping). (This feature cannot be configured using the CME. )
187 Configuring BCCH Carrier Frequency Hopping
BCCH Carrier Frequency Hopping. (This feature cannot be configured using the CME. )
188 Configuring Antenna Frequency Hopping
Antenna Frequency Hopping. (This feature cannot be configured using the CME. )
189 Configuring BCCH Dense Frequency Multiplexing
BCCH Dense Frequency Multiplexing.
190 Configuring IBCA
IBCA (Interference Based Channel Allocation).
191 Configuring Soft-Synchronized Network
Soft-Synchronized Network. (This feature cannot be configured using the CME. )
192 Configuring BTS GPS Synchronization
This section describes how to activate the optional feature GBFD-510401 BTS GPS
Synchronization.
193 Configuring Network Support SAIC
Network Support SAIC.
Issue 06 (2013-04-15) Huawei Proprietary and Confidential xix

GBSS14.0
194 Configuring Mega BSC
Mega BSC. With this feature, a BSC supports a maximum of 8192 TRXs when IP over FE/GE/
STM-1 is used over the A, Abis, and Gb interfaces. This feature enables a BSC to support more
subscribers while maintaining the speech quality.
195 Configuring PS Downlink DTX
PS Downlink DTX. With the PS Downlink DTX feature, the BSC decreases the number of
dummy control blocks sent on PDCHs and the number of data blocks unnecessarily retransmitted
over the Um interface. This reduces the BTS power consumption and network interference,
improving the service quality.
196 Configuring PS Uplink DTX
PS Uplink DTX. With the PS Uplink DTX feature, the BSC decreases the frequency of
scheduling extended uplink TBFs in inactive periods or sends system information instructing
MSs not to send dummy control blocks for extended uplink TBFs in inactive periods. This
reduces the MS power consumption and network interference, improving the service quality.
197 Configuring Automatic Frequency Correction (AFC)
This section describes how to activate, verify, and deactivate the feature GBFD-510101
Automatic Frequency Correction (AFC).
198 Configuring Fast Move Handover
Fast Move Handover.
199 Configuring Chain Cell Handover
Chain Cell Handover.
200 Configuring Multi-Site Cell
Multi-Site Cell.
201 Configuring PS Automatic Frequency Correction (PS AFC)
This section describes how to activate, verify, and deactivate the feature GBFD-5101051 PS
Automatic Frequency Correction (PS AFC).
202 Configuring HUAWEI II Handover
HUAWEI II Handover.
203 Configuring Handover Re-establishment
Handover Re-establishment.
204 Configuring Enhanced Measurement Report
Issue 06 (2013-04-15) Huawei Proprietary and Confidential xx

GBSS14.0
Enhanced Measurement Report.
205 Configuring BTS power lift for handover
BTS power lift for handover.
206 Configuring GSM/WCDMA Interoperability
GSM/WCDMA Interoperability.
207 Configuring GSM/WCDMA Service Based Handover
Configuring GSM/WCDMA Service Based Handover.
208 Configuring GSM/WCDMA Load Based Handover
GSM/WCDMA Load Based Handover.
209 Configuring 2G/3G Cell Reselection Based on MS State
2G/3G Cell Reselection Based on MS State.
210 Configuring the Fast WCDMA Reselection at 2G CS Call Release
Fast WCDMA Cell Reselection at 2G CS Call Release.
211 Configuring Load Based Handover Enhancement on Iur-g
Load Based Handover Enhancement on Iur-g.
212 Configuring NACC(Network Assisted Cell Change) Procedure Optimization Based
on Iur-g between GSM and WCDMA
NACC Procedure Optimization Based on Iur-g between GSM and WCDMA.
213 Configuring GSM and WCDMA Load Balancing Based on Iur-g
GSM and WCDMA Load Balancing Based on Iur-g.
214 Configuring GSM and WCDMA Traffic Steering Based on Iur-g
GSM and WCDMA Traffic Steering Based on Iur-g.
215 Configuring BSC supporting Blind Search
This section describes how to activate, verify, and deactivate the feature GBFD-511110 BSC
supporting Blind Search.
216 Configuring Cell Reselection Between GSM and LTE
Cell Reselection Between GSM and LTE.
Issue 06 (2013-04-15) Huawei Proprietary and Confidential xxi

GBSS14.0
217 Configuring PS Handover Between GSM and LTE Based on Coverage

PS Handover Between GSM and LTE Based on Coverage.
218 Configuring PS Handover Between GSM and LTE Based on Quality
PS Handover Between GSM and LTE Based on Quality.
219 Configuring PS Handover Between GSM and LTE Based on Cell Load
PS Handover Between GSM and LTE Based on Cell Load.
220 Configuring GSM/LTE Service Based PS Handover
GSM/LTE Service Based PS Handover.
221 Configuring eNC2 Between GSM and LTE
eNC2 Between GSM and LTE. Here, eNC2 is short for Network Control Mode 2.
222 Configuring eNACC Between GSM and LTE
eNACC Between GSM and LTE. Here, eNACC is short for External Network Assisted Cell
Change. (This feature cannot be configured using the CME. )
223 Configuring SRVCC
Single Radio Voice Call Continuity (SRVCC).
224 Configuring Multi Technology Neighbour Cell Based Handover
Multi Technology Neighbour Cell Based Handover.
225 Configuring Fast LTE Reselection at 2G CS Call Release
Fast LTE Reselection at 2G CS Call Release.
226 Configuring CSFB
CSFB.
227 Configuring GSM/TD-SCDMA Interoperability
GSM/TD-SCDMA Interoperability.
228 Configuring Iur-g Interface Between GSM and TD-SCDMA
Iur-g Interface Between GSM and TD-SCDMA.
229 Configuring Radio Resource Reserved Handover Between GSM/TD-SCDMA Based
on Iur-g
Issue 06 (2013-04-15) Huawei Proprietary and Confidential xxii

GBSS14.0
Radio Resource Reserved Handover Between GSM/TD-SCDMA Based on Iur-g.
230 Configuring Extended BCCH
Extended BCCH.
231 Configuring NC2 Between GSM and TD-SCDMA
NC2 between GSM and TD-SCDMA.
232 Configuring Ciphering
A5/1 and A5/2 Ciphering Algorithm and GBFD-113503 A5/3 Ciphering Algorithm.
233 Configuring A5/1 Encryption Flow Optimization
This section describes how to activate, verify, deactivate the optional feature GBFD-113521
A5/1 Encryption Flow Optimization.
234 Configuring BTS Integrated IPsec
BTS Integrated IPsec. (This feature cannot be configured using the CME. )
235 Configuring BTS Supporting PKI
The BTS Supporting PKI feature enables an NE to automatically obtain a digital certificate
authorized by the Certificate Authority (CA) of an operator. With the digital certificate, the NE
can pass the authentication that uses the Internet Protocol Security (IPsec), 802.1x, or Secure
Socket Layer (SSL) protocol. This feature contains a suite of functions based on Certificate
Management Protocol version 2 (CMPv2) for certificate management between NEs. CMPv2
provides functions such as certificate register request, key update, key restore, certificate
revocation, CA key update notification, certificate authorization notification, and certificate
revocation notification. This section describes how to activate, verify, and deactivate the optional
feature GBFD-113526 BTS Supporting PKI. (This feature cannot be configured using the
CME. )
236 Configuring Ring Topology
Ring Topology.
237 Configuring TRX Cooperation
TRX Cooperation.
238 Configuring MSC Pool
MSC Pool. (This feature cannot be configured using the CME. )
239 Configuring the SGSN Pool
SGSN Pool.
Issue 06 (2013-04-15) Huawei Proprietary and Confidential xxiii

GBSS14.0
240 Configuring Abis Bypass
Abis Bypass.
241 Configuring Robust Air Interface Signalling
Robust Air Interface Signalling.
242 Configuring Abis Transmission Backup
Abis Transmission Backup.
243 Configuring BSC Node Redundancy
This section describes how to activate, verify, and deactivate the GBFD-113725 BSC Node
Redundancy feature.
244 Configuring TC Pool
TC Pool. The A interface boards of the BSC that supports the TC Pool feature can use only TDM
transmission. The Ater interface boards can use TDM transmission or IP transmission.
245 Configuring OML Backup
OML Backup. When the operation and maintenance link (OML) backup function of the BTS is
enabled, the BTS automatically switches to anther port to set up an OML if the established OML
is disconnected, thereby reducing service interruption duration.
246 Configuring Access Control Class
Access Control Class (ACC).
247 Configuring Adaptive Transmission Link Blocking
Adaptive Transmission Link Blocking.
248 Configuring Semi-Permanent Connection
Semi-Permanent Connection.
249 Configuring End-to-End MS Signaling Tracing
End-to-End MS Signaling Tracing.
250 Configuring Radio Measurement Data Interface for Navigation
Radio Measurement Data Interface for Navigation. (This feature cannot be configured using the
CME. )
251 Configuring Multi-mode Dynamic Power Sharing (GSM)
Issue 06 (2013-04-15) Huawei Proprietary and Confidential xxiv

GBSS14.0
This section describes how to activate, verify, and deactivate the optional feature MRFD-211801
Multi-mode Dynamic Power Sharing (GSM).
252 Configuring GSM and UMTS Dynamic Spectrum Sharing(GSM)
GSM and UMTS Dynamic Spectrum Sharing(GSM). This feature enables the spectrum
resources to be dynamically shared between the GSM and UMTS networks based on their traffic
load, improving frequency utilization.
253 Configuring IP-Based Multi-mode Co-Transmission on BS side (GBTS)
IP-Based Multi-mode Co-Transmission on BS side (GBTS). For details about data
configurations, see section Configuration Reference > MBTS Configuration Reference
(V100R007C00) > Common Transmission in the 3900 Series Base Station Initial
Configuration Guide, or see section Common Transmission in the GBSS Feature
Documentation. The latest 3900 Series Base Station Initial Configuration Guide can be obtained
from the following path: HUAWEI Technical Support (support.huawei.com), Support >
Documentation > SingleRAN > MBTS > SingleRAN7.0.
254 Configuring TDM-Based Multi-mode Co-Transmission via Backplane on BS side

(GBTS)
TDM-Based Multi-mode Co-Transmission via Backplane on BS side(GBTS). (This feature
255 Configuring Multi-Mode BS Common Reference Clock (GBTS)
Multi-Mode BS Common Reference Clock (GBTS). For details about data configurations, see
section Configuration Reference > MBTS Configuration Reference (V100R007C00) >
Common Clock in the 3900 Series Base Station Initial Configuration Guide, or see section
Common Clock in the GBSS Feature Documentation. The latest 3900 Series Base Station Initial
Configuration Guide can be obtained from the following path: HUAWEI Technical Support
(support.huawei.com), Support > Documentation > SingleRAN > MBTS > SingleRAN7.0.
256 Configuring Dynamic MA for GU Dynamic Spectrum Sharing (GSM)
This section describes how to activate, verify, and deactivate the multi-mode feature
MRFD-211803 Dynamic MA for GU Dynamic Spectrum Sharing(GSM). (For details about
operations performed on the CME, see the Configuring a GU DSS Task in the M2000-CME
documentation.)
257 Configuring GSM Power Control on Interference Frequency for GU Small Frequency
Gap (GSM)
MRFD-211804 GSM Power Control on Interference Frequency for GU Small Frequency gap
(GSM).
258 Multi-mode BS Common IPSec(GSM)
MRFD-211602 Multi-mode BS Common IPSec(GSM). (This feature cannot be configured
using the CME. )
Issue 06 (2013-04-15) Huawei Proprietary and Confidential xxv

GBSS14.0
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 or medium level of risk

which, if not avoided, could result in death or serious injury.
Indicates a hazard with a low level of risk which, if not

avoided, could result in minor or moderate injury.
Indicates a potentially hazardous situation that, if not

avoided, could result in equipment damage, data loss,
performance deterioration, or unanticipated 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 Description
Times New Roman Normal paragraphs are in Times New Roman.
Boldface Names of files, directories, folders, and users are in

boldface. For example, log in as user root.
Italic Book titles are in italics.

Courier New 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.
Boldface The keywords of a command line are in boldface.
Italic Command arguments are in italics.
[] Items (keywords or arguments) in brackets [ ] are optional.
Issue 06 (2013-04-15) Huawei Proprietary and Confidential xxvi

GBSS14.0
{ x | y | ... } Optional items are grouped in braces and separated by

vertical bars. One item is selected.
[ x | y | ... ] Optional items are grouped in brackets and separated by

vertical bars. One item is selected or no item is selected.
{ x | y | ... }* 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.
[ x | y | ... ]* Optional items are grouped in brackets and separated by

vertical bars. Several items or no item can be selected.
GUI Conventions
The GUI conventions that may be found in this document are defined as follows.
Boldface 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 Description
Key Press the key. For example, press Enter and press Tab.
Key 1+Key 2 Press the keys concurrently. For example, pressing Ctrl+Alt
+A means the three keys should be pressed concurrently.
Key 1, Key 2 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 Description
Click Select and release the primary mouse button without moving
the pointer.
Issue 06 (2013-04-15) Huawei Proprietary and Confidential xxvii

GBSS14.0
Action Description
Double-click Press the primary mouse button twice continuously and

quickly without moving the pointer.
Drag Press and hold the primary mouse button and move the
pointer to a certain position.
Issue 06 (2013-04-15) Huawei Proprietary and Confidential xxviii

GBSS14.0
Feature Activation Guide Contents
Contents
About This Document.....................................................................................................................ii

1 Changes in the GBSS Feature Activation Guide.....................................................................1
2 Feature Activation and License Item Descriptions.................................................................8
3 Overview of Configurations on the CME...............................................................................44
3.1 Introduction to Configuration Methods............................................................................................................47
3.2 Configuring Device Data..................................................................................................................................48
3.3 Introduction to the Configuration Express for BSCs........................................................................................49
3.4 Introduction to the Configuration Express for A Interfaces.............................................................................50
3.5 Introduction to the Configuration Express for Ater Interfaces.........................................................................51
3.6 Introduction to the Configuration Express for Gb Interfaces...........................................................................52
3.7 Introduction to the Configuration Express for the (G)Iur-g Interface..............................................................53
3.8 BSC Abis IP Configuration Express................................................................................................................53
3.9 Introduction to the Configuration Express for Abis Interfaces........................................................................55
3.10 Introduction to the BTS Topology View........................................................................................................56
3.11 Introduction to the Configuration Express for BTSs......................................................................................59
3.12 Configuration Express for BTS IP Addresses................................................................................................60
3.13 Introduction to the GSM Device Panel...........................................................................................................62
3.14 Introduction to the Configuration Express for TRXs.....................................................................................65
3.15 Introduction to the Configuration Express for GSM Cells.............................................................................66
3.16 Introduction to the Configuration Express for Neighboring GSM Cells........................................................67
3.17 Modifying GBSC Parameters in Batches.......................................................................................................68
3.18 Modifying GBTS Parameters in Batches.......................................................................................................69
3.19 Deleting GSM Cells in Batches......................................................................................................................69
3.20 Modifying GSM Cell Parameters in Batches.................................................................................................70
3.21 Modifying BSC External Cell Parameters in Batches....................................................................................71
3.22 Modifying GSM TRX Parameters in Batches................................................................................................72
3.23 Introduction to the Object Group Configuration............................................................................................73
4 Activating the GSM License......................................................................................................74

5 Configuring Multi-band Sharing One BSC...........................................................................75
6 Configuring Emergency Call Service (TS12)..........................................................................78
7 Configuring IMSI Detach..........................................................................................................80
Issue 06 (2013-04-15) Huawei Proprietary and Confidential xxix

GBSS14.0
8 Configuring HUAWEI I Handover..........................................................................................82

9 Configuring Directed Retry.......................................................................................................95
10 Configuring Assignment and Immediate Assignment......................................................98
11 Configuring Call Reestablishment......................................................................................100
12 Configuring TCH Re-assignment........................................................................................104
13 Configuring Radio Link Management................................................................................106
14 Configuring Faulty Management.........................................................................................108
15 Configuring BTS Software Management...........................................................................110
16 Configuring Combined Cabinets and Cabinet Groups of BTSs...................................112
17 Configuring Connection Inter BSC over IP.......................................................................117
18 Configuring Link Aggregation.............................................................................................120
19 Configuring Intelligent Shutdown of TRX Due to PSU Failure....................................124
20 Configuring Call-Based Flow Control.................................................................................126
21 Configuring Pre-Processing of Measurement Report......................................................128
22 Configuring System Information Sending.........................................................................130
23 Configuring Daylight Saving Time.....................................................................................132
24 Configuring SDCCH Dynamic Adjustment......................................................................134
25 Configuring Cell Frequency Scan........................................................................................137
26 Configuring Signaling Transport Point (STP)...................................................................139
27 Configuring 14-Digit Signaling Point Code......................................................................145
28 Configuring Discontinuous Reception (DRX)...................................................................147
29 Configuring BTS Power Management................................................................................149
30 Configuring Enhanced Power Control Algorithm............................................................151
31 Configuring DTMF Downlink Message Filter..................................................................156
32 Configuring High Speed Signaling ....................................................................................158
33 Configuring Guaranteed Emergency Call..........................................................................161
34 Configuring License Control for Urgency..........................................................................164
35 Configuring HUAWEI III Power Control Algorithm.......................................................166
36 Configuring the satellite transmission on the Pb interface............................................173
37 Configuring PDCH Dynamic Adjustment.........................................................................175
Issue 06 (2013-04-15) Huawei Proprietary and Confidential xxx

GBSS14.0
38 Configuring Connection with TMA....................................................................................179

39 Configuring Remote Electrical Tilt......................................................................................182
40 Configuring 2-Antenna Receive Diversity.........................................................................185
41 Configuring BTS Clock..........................................................................................................187
42 Configuring Voice Fault Detection......................................................................................189
43 Configuring Abis Crossed Pair Diagnosis.........................................................................192
44 Configuring IP Performance Monitor.................................................................................194
45 Configuring GSM PS Service Map......................................................................................199
46 Configuring Multi-mode BS Common CPRI Interface (GBTS).....................................204
47 Configuring Enhanced Full Rate (EFR)...............................................................................206
48 Configuring Automatic Level Control (ALC)....................................................................208
49 Configuring Acoustic Echo Cancellation (AEC)................................................................213
50 Configuring Automatic Noise Restraint (ANR)................................................................216
51 Configuring TFO.....................................................................................................................219
52 Configuring Automatic Noise Compensation (ANC)......................................................223
53 Configuring Enhancement Packet Loss Concealment (EPLC).......................................226
54 Configuring EVAD.................................................................................................................228
55 Configuring Voice Quality Index (VQI).............................................................................230
56 Configuring Um Interface Speech Frame Repairing........................................................233
57 Configuring AMR...................................................................................................................235
58 Configuring AMR Coding Rate Threshold Adaptive Adjustment...............................238
59 Configuring WB AMR............................................................................................................242
60 Configuring Half Rate Speech (HR)....................................................................................244
61 Configuring Dynamic Adjustment Between FR and HR................................................246
62 Configuring Dynamic HR/FR Adaptation..........................................................................255
63 Configuring VAMOS.............................................................................................................261
64 Configuring Mute SAIC MS Identification.......................................................................274
65 Configuring VAMOS Call Drop Solution..........................................................................278
66 Configuring Short Message Service Cell Broadcast (TS23)............................................282
67 Configuring Simplified Cell Broadcast..............................................................................285
Issue 06 (2013-04-15) Huawei Proprietary and Confidential xxxi

GBSS14.0
68 Configuring VGCS and VBS.................................................................................................287

69 Configuring GSM-T Relay....................................................................................................290
70 Configuring LCS (cell ID + TA)...........................................................................................293
71 Configuring Lb Interface.......................................................................................................297
72 Configuring Resource Reservation......................................................................................307
73 Configuring Enhanced Multi Level Precedence and Preemption (eMLPP)................309
74 Configuring Flow Control Based on Cell Priority............................................................313
75 Configuring Flow Control Based on User Priority...........................................................316
76 Configuring PS Service in Priority......................................................................................318
77 Configuring GPRS..................................................................................................................320
78 Configuring Network Operation Mode I...........................................................................323
79 Configuring EGPRS................................................................................................................325
80 Configuring 11-Bit EGPRS Access.......................................................................................328
81 Configuring Packet Channel Dispatching.........................................................................332
81.1 Configuring EGPRS Special Channel Be Used by Only EGPRS Service...................................................334
81.2 Configuring EGPRS Preferred Channel.......................................................................................................335
81.3 Configuring Channel Multiplexing in the E Down G Up Scenario.............................................................337
82 Configuring Streaming QoS(GBR)......................................................................................339

83 Configuring QoS ARP&THP................................................................................................342
84 Configuring PS Active Package Management...................................................................345
85 Configuring PoC QoS.............................................................................................................347
86 Configuring Conversational QoS.........................................................................................349
87 Configuring NC2.....................................................................................................................351
88 Configuring Network Assisted Cell Change (NACC).....................................................354
89 Configuring BSS Paging Coordination...............................................................................357
90 Configuring PS Handover.....................................................................................................359
91 Configuring PS Power Control.............................................................................................363
91.1 Configuring EGPRS Downlink Power Control............................................................................................365
91.2 Configuring GPRS Downlink Power Control..............................................................................................366
92 Configuring PDCH Dynamic Adjustment with Two Thresholds.................................368

93 Configuring Timeslot Multiplexing Priority for GPRS/EGPRS User..........................372
94 Configuring EDA.....................................................................................................................376
Issue 06 (2013-04-15) Huawei Proprietary and Confidential xxxii

GBSS14.0
95 Configuring MS High Multislot Classes............................................................................379

96 Configuring DTM...................................................................................................................381
97 Configuring Class11 DTM.....................................................................................................383
98 Configuring HMC DTM........................................................................................................385
99 Configuring 14.4 kbit/s Circuit Switched Data..................................................................387
100 Configuring High Speed Circuit Switched Data............................................................390
101 Configuring Active TBF Allocation...................................................................................393
102 Configuring MSRD...............................................................................................................396
103 Configuring Dual Carriers in Downlink..........................................................................398
104 Configuring the EGPRS2-A.................................................................................................400
105 Configuring Latency Reduction.........................................................................................402
106 Configuring IM Service Efficiency Improvement..........................................................404
107 Configuring Web Browsing Service Efficiency Improvement.....................................409
108 Configuring Email Service Efficiency Improvement.....................................................414
109 Configuring Streaming Media Service Resource Balancing.........................................419
110 Configuring P2P Resource Balancing................................................................................424
111 Configuring WLAN Hot Spot Notification......................................................................429
112 Configuring Multiple CCCHs............................................................................................432
113 Configuring Layered Paging...............................................................................................434
114 Configuring Dynamic Multiple CCCH.............................................................................436
115 Configuring RACH Storm Filtration.................................................................................443
116 Configuring Active Power Control....................................................................................446
117 Configuring Discontinuous Transmission (DTX)-Downlink......................................448
118 Configuring Discontinuous Transmission (DTX)-Uplink............................................450
119 Configuring TRX Power Amplifier Intelligent Shutdown...........................................452
120 Configuring TRX Power Amplifier Intelligent Shutdown on Timeslot Level
..........................................................................................................................................................456
121 Configuring Intelligent Combiner Bypass.......................................................................459
122 Configuring Active Backup Power Control.....................................................................461
123 Configuring Power Optimization Based on Channel Type..........................................464
124 Configuring PSU Smart Control.........................................................................................467
Issue 06 (2013-04-15) Huawei Proprietary and Confidential xxxiii

GBSS14.0
125 Configuring Enhanced BCCH Power Consumption Optimization............................470

126 Configuring Dynamic Cell Power Off..............................................................................473
127 Configuring TRX Working Voltage Adjustment............................................................477
128 Configuring Multi-Carrier Intelligent Voltage Regulation..........................................479
129 Configuring Flex Abis..........................................................................................................482
130 Configuring BTS Local Switch...........................................................................................490
131 Configuring Abis Transmission Optimization...............................................................493
132 Configuring Abis Congestion Trigger HR Distribution...............................................496
133 Configuring Flex Ater...........................................................................................................499
134 Configuring BSC Local Switch...........................................................................................501
135 Configuring Ater Compression Transmission................................................................504
136 Configuring Local Multiple Signaling Points.................................................................508
137 Configuring PS Dummy Frame Compression.................................................................511
138 Configuring Clock over IP support 1588v2......................................................................513
139 Configuring Synchronous Ethernet...................................................................................515
140 Configuring Abis over IP.....................................................................................................517
141 Configuring Abis IP over E1/T1.........................................................................................522
142 Configuring Abis MUX........................................................................................................525
143 Configuring Abis IPHC........................................................................................................527
144 Configuring A over IP..........................................................................................................531
145 Configuring A IP over E1/T1...............................................................................................534
146 Configuring UDP MUX for A Transmission...................................................................537
147 Configuring TDM/IP Dual Transmission over A Interface..........................................539
148 Configuring Gb over IP........................................................................................................543
149 Configuring Ethernet OAM................................................................................................546
150 Configuring A Interface Transmission Pool....................................................................552
151 Configuring Satellite Transmission over Abis Interface...............................................555
152 Configuring Satellite Transmission over A Interface....................................................560
153 Configuring Satellite Transmission over Ater Interface...............................................563
154 Configuring Satellite Transmission over Gb Interface.................................................565
Issue 06 (2013-04-15) Huawei Proprietary and Confidential xxxiv

GBSS14.0
155 Configuring RAN Sharing...................................................................................................567

156 Configuring MOCN Shared Cell.......................................................................................576
157 Configuring IMSI-Based Handover..................................................................................588
158 Configuring Abis Independent Transmission................................................................591
159 Configuring PICO/Compact BTS Automatic Configuration and Planning..............596
160 Configuring PICO Synchronization..................................................................................600
161 Configuring PICO Dual-band Auto-planning................................................................602
162 Configuring PICO USB Encryption...................................................................................605
163 Configuring PICO Sleeping Mode....................................................................................607
164 Configuring PICO Automatic Optimization...................................................................609
165 Configuring PICO Transceiver Redundancy...................................................................611
166 Configuring Weather Adaptive Power Management.....................................................615
167 Configuring Compact BTS Automatic Capacity Planning............................................618
168 Configuring Compact BTS Automatic Neighbor Cell Planning and Optimization
..........................................................................................................................................................620
169 Configuring Compact BTS Timing Power Off................................................................623
170 Configuring Local User Management...............................................................................625
171 Configuring Intelligent Battery Management.................................................................627
172 Configuring PBT....................................................................................................................631
173 Configuring Transmit Diversity.........................................................................................633
174 Configuring 4-Way Receiver Diversity.............................................................................635
175 Configuring Dynamic Transmit Diversity.......................................................................637
176 Configuring Dynamic PBT..................................................................................................640
177 Configuring Enhanced EDGE Coverage...........................................................................643
178 Configuring Dynamic Power Sharing...............................................................................646
179 Configuring Extended Cell..................................................................................................650
180 Configuring Concentric Cell...............................................................................................652
181 Configuring Co-BCCH Cell.................................................................................................657
182 Configuring Enhanced Dual-Band Network...................................................................663
183 Configuring Flex MAIO.......................................................................................................667
184 Configuring ICC....................................................................................................................670
Issue 06 (2013-04-15) Huawei Proprietary and Confidential xxxv

GBSS14.0
185 Configuring EICC..................................................................................................................672

186 Configuring Frequency Hopping (RF hopping, baseband hopping).........................674
187 Configuring BCCH Carrier Frequency Hopping............................................................677
188 Configuring Antenna Frequency Hopping......................................................................680
189 Configuring BCCH Dense Frequency Multiplexing......................................................682
190 Configuring IBCA.................................................................................................................684
191 Configuring Soft-Synchronized Network........................................................................692
192 Configuring BTS GPS Synchronization...........................................................................696
193 Configuring Network Support SAIC................................................................................698
194 Configuring Mega BSC........................................................................................................701
195 Configuring PS Downlink DTX.........................................................................................704
196 Configuring PS Uplink DTX...............................................................................................708
197 Configuring Automatic Frequency Correction (AFC)....................................................712
198 Configuring Fast Move Handover.....................................................................................715
199 Configuring Chain Cell Handover.....................................................................................718
200 Configuring Multi-Site Cell................................................................................................720
201 Configuring PS Automatic Frequency Correction (PS AFC)........................................724
202 Configuring HUAWEI II Handover...................................................................................726
203 Configuring Handover Re-establishment........................................................................740
204 Configuring Enhanced Measurement Report..................................................................742
205 Configuring BTS power lift for handover........................................................................744
206 Configuring GSM/WCDMA Interoperability.................................................................746
207 Configuring GSM/WCDMA Service Based Handover..................................................749
208 Configuring GSM/WCDMA Load Based Handover......................................................752
209 Configuring 2G/3G Cell Reselection Based on MS State..............................................755
210 Configuring the Fast WCDMA Reselection at 2G CS Call Release............................758
211 Configuring Load Based Handover Enhancement on Iur-g..........................................761
212 Configuring NACC(Network Assisted Cell Change) Procedure Optimization Based
on Iur-g between GSM and WCDMA......................................................................................764
213 Configuring GSM and WCDMA Load Balancing Based on Iur-g..............................766
214 Configuring GSM and WCDMA Traffic Steering Based on Iur-g..............................770
Issue 06 (2013-04-15) Huawei Proprietary and Confidential xxxvi

GBSS14.0
215 Configuring BSC supporting Blind Search......................................................................773

216 Configuring Cell Reselection Between GSM and LTE..................................................777
217 Configuring PS Handover Between GSM and LTE Based on Coverage....................780
218 Configuring PS Handover Between GSM and LTE Based on Quality.......................784
219 Configuring PS Handover Between GSM and LTE Based on Cell Load...................788
220 Configuring GSM/LTE Service Based PS Handover......................................................792
221 Configuring eNC2 Between GSM and LTE.....................................................................796
222 Configuring eNACC Between GSM and LTE.................................................................799
223 Configuring SRVCC.............................................................................................................801
224 Configuring Multi Technology Neighbour Cell Based Handover..............................803
225 Configuring Fast LTE Reselection at 2G CS Call Release.............................................806
226 Configuring CSFB.................................................................................................................808
227 Configuring GSM/TD-SCDMA Interoperability...........................................................811
228 Configuring Iur-g Interface Between GSM and TD-SCDMA......................................815
229 Configuring Radio Resource Reserved Handover Between GSM/TD-SCDMA Based
on Iur-g...........................................................................................................................................819
230 Configuring Extended BCCH..............................................................................................822
231 Configuring NC2 Between GSM and TD-SCDMA........................................................825
232 Configuring Ciphering.........................................................................................................828
233 Configuring A5/1 Encryption Flow Optimization..........................................................831
234 Configuring BTS Integrated IPsec.....................................................................................836
235 Configuring BTS Supporting PKI......................................................................................844
236 Configuring Ring Topology................................................................................................848
237 Configuring TRX Cooperation............................................................................................851
238 Configuring MSC Pool.........................................................................................................854
239 Configuring the SGSN Pool................................................................................................858
239.1 Configuring SGSN Pool (Gb over IP)........................................................................................................859
239.2 Configuring SGSN Pool (Gb over FR).......................................................................................................862
240 Configuring Abis Bypass.....................................................................................................866

241 Configuring Robust Air Interface Signalling..................................................................871
242 Configuring Abis Transmission Backup..........................................................................874
242.1 Configuring Satellite Transmission Backup (Ring Topology)...................................................................875
Issue 06 (2013-04-15) Huawei Proprietary and Confidential xxxvii

GBSS14.0
242.2 Configuring Satellite Transmission Backup (Dual-Logical BTS).............................................................877

242.3 Configuring Abis Transmission Backup Enhancement..............................................................................882
243 Configuring BSC Node Redundancy................................................................................898

244 Configuring TC Pool.............................................................................................................911
244.1 Configuring TC Pool (Ater over TDM).....................................................................................................912
244.2 Configuring TC Pool (Ater over IP)...........................................................................................................916
245 Configuring OML Backup...................................................................................................924

246 Configuring Access Control Class.....................................................................................927
247 Configuring Adaptive Transmission Link Blocking......................................................929
248 Configuring Semi-Permanent Connection.......................................................................932
249 Configuring End-to-End MS Signaling Tracing.............................................................935
250 Configuring Radio Measurement Data Interface for Navigation................................937
251 Configuring Multi-mode Dynamic Power Sharing (GSM)..........................................943
252 Configuring GSM and UMTS Dynamic Spectrum Sharing(GSM)............................946
253 Configuring IP-Based Multi-mode Co-Transmission on BS side (GBTS).................951
254 Configuring TDM-Based Multi-mode Co-Transmission via Backplane on BS side
(GBTS)............................................................................................................................................952
255 Configuring Multi-Mode BS Common Reference Clock (GBTS)...............................958
256 Configuring Dynamic MA for GU Dynamic Spectrum Sharing (GSM)....................959
257 Configuring GSM Power Control on Interference Frequency for GU Small Frequency
Gap (GSM).....................................................................................................................................962
258 Multi-mode BS Common IPSec(GSM).............................................................................968
Issue 06 (2013-04-15) Huawei Proprietary and Confidential xxxviii

GBSS14.0
Feature Activation Guide 1 Changes in the GBSS Feature Activation Guide
1 Changes in the GBSS Feature Activation

Guide
This chapter describes the changes in the GBSS Feature Activation Guide.
06 (2013-04-15)
This is the sixth commercial release of GBSS14.0.
Compared with issue 05 (2012-12-31), this issue does not include any topics.
Compared with issue 05 (2012-12-31), this issue incorporates the following changes:
Content Description
243 Configuring BSC Node Redundancy The prerequisite, context, and activation
procedure are changed.
129 Configuring Flex Abis The activation procedure and verification

124 Configuring PSU Smart Control The prerequisite and verification procedure
are changed.
125 Configuring Enhanced BCCH Power The activation procedure and verification
Consumption Optimization procedure are changed.
126 Configuring Dynamic Cell Power Off The prerequisite, activation procedure, and
verification procedure are changed.
127 Configuring TRX Working Voltage The prerequisite, activation procedure, and
Adjustment verification procedure are changed.
128 Configuring Multi-Carrier Intelligent The prerequisite and verification procedure

Voltage Regulation are changed.
241 Configuring Robust Air Interface The verification procedure is changed.

Signalling
58 Configuring AMR Coding Rate The prerequisite is changed.

Threshold Adaptive Adjustment
Issue 06 (2013-04-15) Huawei Proprietary and Confidential 1

GBSS14.0
Content Description
215 Configuring BSC supporting Blind The prerequisite is changed.

Search
231 Configuring NC2 Between GSM and The prerequisite is changed.

TD-SCDMA
91 Configuring PS Power Control The prerequisite is changed.
196 Configuring PS Uplink DTX The activation procedure and verification

195 Configuring PS Downlink DTX The verification procedure is changed.
63 Configuring VAMOS The prerequisite and verification procedure

are changed.
Compared with issue 05 (2012-12-31), this issue does not exclude any topics.
05 (2012-12-31)
This is the fifth commercial release of GBSS14.0.
Content Description
113 Configuring Layered Paging The prerequisite is changed.
104 Configuring the EGPRS2-A The context is changed.
239 Configuring the SGSN Pool The feature deactivation procedure is

changed.
62 Configuring Dynamic HR/FR The feature activation procedure is changed.

Adaptation
233 Configuring A5/1 Encryption Flow
Optimization
04 (2012-11-07)
This is the fourth commercial release of GBSS14.0.
Compared with issue 03 (2012-08-30), this issue includes the following new topics:
l 43 Configuring Abis Crossed Pair Diagnosis

GBSS14.0
l 86 Configuring Conversational QoS

Content Description
140 Configuring Abis over IP The dependencies on other features is

175 Configuring Dynamic Transmit changed.
Diversity
172 Configuring PBT
174 Configuring 4-Way Receiver Diversity
118 Configuring Discontinuous The verification procedure is changed.

Transmission (DTX)-Uplink
118 Configuring Discontinuous The feature deactivation procedure is

Transmission (DTX)-Uplink changed.
118 Configuring Discontinuous The feature activation procedure is changed.

35 Configuring HUAWEI III Power
Control Algorithm
212 Configuring NACC(Network Assisted
Cell Change) Procedure Optimization
Based on Iur-g between GSM and
WCDMA
03 (2012-08-30)
This is the third commercial release of GBSS14.0.
Compared with issue 02 (2012-06-30), this issue includes the following new topics:
l 205 Configuring BTS power lift for handover
Content Description
5 Configuring Multi-band Sharing One The dependencies on other features is

BSC changed.

GBSS14.0
Content Description
25 Configuring Cell Frequency Scan The verification procedure is changed.

34 Configuring License Control for
Urgency
93 Configuring Timeslot Multiplexing
Priority for GPRS/EGPRS User
66 Configuring Short Message Service Cell The feature deactivation procedure is

Broadcast (TS23) changed.
149 Configuring Ethernet OAM The feature activation procedure is changed.

242 Configuring Abis Transmission
Backup
02 (2012-06-30)
This is the second commercial release of GBSS14.0.
Content Description
55 Configuring Voice Quality Index (VQI) The dependencies on other features is

56 Configuring Um Interface Speech changed.
Frame Repairing
66 Configuring Short Message Service Cell
Broadcast (TS23)
77 Configuring GPRS
212 Configuring NACC(Network Assisted
Cell Change) Procedure Optimization
Based on Iur-g between GSM and
WCDMA
233 Configuring A5/1 Encryption Flow The verification procedure is changed.

Optimization

GBSS14.0
Content Description
214 Configuring GSM and WCDMA The feature deactivation procedure is

Traffic Steering Based on Iur-g changed.
56 Configuring Um Interface Speech The verification procedure is changed.

Frame Repairing
01 (2012-04-26)
This is the first commercial release of GBSS14.0.
Compared with issue Draft B (2012-03-26), this issue includes the following new topics:
l 115 Configuring RACH Storm Filtration
Compared with issue Draft B (2012-03-26), this issue incorporates any changes.
Compared with issue Draft B (2012-03-26), this issue does not exclude any topics.
Draft B (2012-03-26)
This is the Draft B release of GBSS14.0.
Compared with issue Draft A (2012-02-15), this issue includes the following new topics:
l 111 Configuring WLAN Hot Spot Notification
Compared with issue Draft A (2012-02-15), this issue incorporates any changes.
Compared with issue Draft A (2012-02-15), this issue does not exclude any topics.
Draft A (2012-02-15)
This is the Draft A release of GBSS14.0.
Compared with issue 08 (2012-01-05) of GBSS13.0, this issue includes the following new topics:
l 45 Configuring GSM PS Service Map
l 100 Configuring High Speed Circuit Switched Data
l 101 Configuring Active TBF Allocation
l 106 Configuring IM Service Efficiency Improvement
l 107 Configuring Web Browsing Service Efficiency Improvement
l 108 Configuring Email Service Efficiency Improvement
l 109 Configuring Streaming Media Service Resource Balancing
l 110 Configuring P2P Resource Balancing
l 114 Configuring Dynamic Multiple CCCH
l 137 Configuring PS Dummy Frame Compression
l 171 Configuring Intelligent Battery Management

GBSS14.0
l 194 Configuring Mega BSC

l 195 Configuring PS Downlink DTX
l 196 Configuring PS Uplink DTX
l 201 Configuring PS Automatic Frequency Correction (PS AFC)
l 215 Configuring BSC supporting Blind Search
l 231 Configuring NC2 Between GSM and TD-SCDMA
l 234 Configuring BTS Integrated IPsec
l 235 Configuring BTS Supporting PKI
Compared with issue 08 (2012-01-05) of GBSS13.0, this issue incorporates the following
changes:
content Description
151 Configuring Satellite Transmission The configuration of satellite transmission for

over Abis Interface Pico BTSs is added.
71 Configuring Lb Interface The U-TDOA positioning method is added.
48 Configuring Automatic Level Control The configuration of the gain monitoring

(ALC) switch is added.
49 Configuring Acoustic Echo The configuration of the gain monitoring

Cancellation (AEC) switch is added.
50 Configuring Automatic Noise Restraint The configuration of the gain monitoring

(ANR) switch is added.
52 Configuring Automatic Noise The configuration of the gain monitoring

Compensation (ANC) switch is added.
61 Configuring Dynamic Adjustment The configuration that level is also

Between FR and HR considered for deciding whether to assign
TCHHs is added.
63 Configuring VAMOS The limit that GBFD-115830 VAMOS

cannot be used together with GBFD-117002
IBCA or GBFD-113201 Concentric Cell is
deleted from Prerequisites. The configuration
of channel demultiplexing optimization is
added.
64 Configuring Mute SAIC MS The limit for enabling the Mute SAIC MS
Identification Identification feature is added to the
Prerequisites.
65 Configuring VAMOS Call Drop The limit for enabling the VAMOS Call Drop
Solution Solution feature is added to the Prerequisites.
190 Configuring IBCA The limit that GBFD-117002 IBCA cannot be

used together with GBFD-115830 VAMOS
is deleted from Prerequisites.

GBSS14.0
content Description
180 Configuring Concentric Cell The limit that GBFD-113201 Concentric Cell
cannot be used together with GBFD-115830
VAMOS is deleted from Prerequisites.
238 Configuring MSC Pool The content on that GBFD-117401MSC Pool

supports the BSC to initiate independent load
reassignment is added to Background
Information and Activation Procedure.
206 Configuring GSM/WCDMA The content on optimizing 2Quater system

Interoperability information (SI) is added to Background
Information and Activation Procedure.
209 Configuring 2G/3G Cell Reselection The content on optimizing 2Quater SI is

Based on MS State added to Background Information and
Activation Procedure.
8 Configuring HUAWEI I Handover The configuration of TCHF-TCHH handover

optimization function is added.
202 Configuring HUAWEI II Handover l The configuration of the TCHF-TCHH

handover optimization, load-based
handover penalty inheritance functions is
added.
l The configuration of the quick handover
algorithm is modified.
14 Configuring Faulty Management The configuration of the OML identification

function is added.
159 Configuring PICO/Compact BTS The configuration for locations of BTSs in

Automatic Configuration and Planning automatic planning mode is added.
8 Configuring HUAWEI I Handover The configuration of the quick handover

198 Configuring Fast Move Handover The configuration of the quick handover
91 Configuring PS Power Control The configurations for EGPRS uplink power

control and uplink dummy block slow
scheduling are added.
Compared with issue 08 (2012-01-05) of GBSS13.0, this issue does not exclude any topics.

GBSS14.0
Feature Activation Guide 2 Feature Activation and License Item Descriptions
2 Feature Activation and License Item

Descriptions
GBSSFeatures are classified into basic and optional features. Basic features are not license-
controlled and therefore do not require license activation before use. Some optional features are
license-controlled and therefore require license activation before use. If the Configuration
Method column for a basic feature in the RAN basic feature list is None, enabling this feature
does not involve any configurations. If the Configuration Method column for an optional feature
in the RAN optional feature list is None, this feature is enabled once it is activated.
Table 2-1 lists the GBSS basic features. Table 2-2 lists the GBSS optional features.
Table 2-1 GBSS Basic Feature List

Feature ID Feature Name Configuration Method
GBFD-110000 GBSS9.0 System None

Improvement

Improvement
GBFD-110030 3GPP Protocol Compliance None

Improvement
GBFD-110101 Frequency Band None
GBFD-114401 Multi-band Sharing One 5 Configuring Multi-band

BSC Sharing One BSC
GBFD-114901 Support for E-GSM and R- None

GSM Frequency Band
GBFD-110201 Telephone Service (TS11) None
GBFD-110202 Emergency Call Service 6 Configuring Emergency

(TS12) Call Service (TS12)

GBSS14.0
GBFD-110203 Point To Point Short None

Message Service (TS21,
TS22)
GBFD-110204 G3 Fax (TS61, TS62) None
GBFD-110205 Bearer Service None
GBFD-110301 Location Updating None
GBFD-110302 IMSI Detach 7 Configuring IMSI Detach
GBFD-110303 CS Paging None
GBFD-110304 Authentication None
GBFD-110601 HUAWEI I Handover 8 Configuring HUAWEI I

Handover
GBFD-110607 Direct Retry 9 Configuring Directed

Retry
GBFD-110608 SDCCH Handover 202 Configuring HUAWEI

II Handover
GBFD-110401 Basic Cell Selection None
GBFD-110402 Basic Cell Re-selection None
GBFD-110501 Call Control None
GBFD-110502 Assignment and Immediate 10 Configuring Assignment

Assignment and Immediate Assignment
GBFD-110503 Call Reestablishment 11 Configuring Call

Reestablishment
GBFD-112501 TCH Re-assignment 12 Configuring TCH Re-

assignment
GBFD-119202 Packet Assignment Taken 80 Configuring 11-Bit

Over by the BTS EGPRS Access
GBFD-111001 TRX Management None
GBFD-111002 Radio Link Management 13 Configuring Radio Link

Management
GBFD-111003 Radio Common Channel None

Management
GBFD-111004 Radio Dedicated Channel None

Management
GBFD-111005 Enhanced Channel None

Assignment Algorithm

GBSS14.0
MRFD-210301 Configuration Management None
MRFD-210302 Performance Management None
MRFD-210303 Inventory Management None
MRFD-210304 Faulty Management 14 Configuring Faulty

Management
MRFD-210305 Security Management None
MRFD-210309 DBS Topology Maintenance None
MRFD-210310 BTS/NodeB Software USB None

Download
GBFD-111202 O&M of BTS None
GBFD-111203 O&M of BSC None
GBFD-111207 BTS Test Function None
GBFD-111210 Integrated Network None

Management Interface
GBFD-116501 Integrated Network None

Management Interface
GBFD-116402 Maintenance Mode Alarm None
GBFD-113523 NAT Beside OM None
MRFD-210401 BSC/RNC Software None

Management
MRFD-210402 BTS/NodeB Software 15 Configuring BTS

Management Software Management
GBFD-111213 Remote Upgrade of the None

BSC&BTS Software
MRFD-210403 License Management None
GBFD-114601 Multi-Cell Function None
GBFD-111501 BTS Combined Cabinet 16 Configuring Combined

Cabinets and Cabinet
Groups of BTSs
GBFD-111502 BTS Hybrid Cabinet Group 16 Configuring Combined

Cabinets and Cabinet
Groups of BTSs
GBFD-118801 BSC Cabinet/Subrack None

Sharing
MRFD-210204 Star Topology None

GBSS14.0
MRFD-210205 Chain Topology None
MRFD-210206 Tree Topology None
GBFD-118621 Connection Inter BSC over 17 Configuring Connection

IP Inter BSC over IP
GBFD-111701 Board Switchover None
GBFD-111705 GSM Flow Control None
GBFD-112301 Remote EAC Maintenance None
GBFD-111214 Operation & Maintenance None

System One-Key Recovery
GBFD-111211 Reporting the Temperature None

List of the BTS Equipment
Room
MRFD-210101 System Redundancy None
MRFD-210102 Operate System Security None

Management
MRFD-210103 Link aggregation 18 Configuring Link

Aggregation
MRFD-210104 BSC/RNC Resource Sharing None
GBFD-117804 Intelligent Shutdown of TRX 19 Configuring Intelligent

Due to PSU Failure Shutdown of TRX Due to
PSU Failure
GBFD-511003 Call-Based Flow Control 20 Configuring Call-Based

Flow Control
GBFD-110901 Adjustment of Adaptive None

Timing Advance
GBFD-110801 Processing of Measurement None

Report
GBFD-110802 Pre-processing of 21 Configuring Pre-

Measurement Report Processing of Measurement
Report
GBFD-111101 System Information Sending 22 Configuring System

Information Sending
GBFD-111102 Forced System Information None

Sending by OMC
GBFD-111901 Supporting Three-Digit None

MNC

GBSS14.0
GBFD-116101 Support of Daylight Saving 23 Configuring Daylight

Time Saving Time
GBFD-113001 SDCCH Dynamic 24 Configuring SDCCH

Adjustment Dynamic Adjustment
GBFD-112401 Cell Frequency Scan 25 Configuring Cell

Frequency Scan
GBFD-111806 STP (Signaling Transport 26 Configuring Signaling

Point) Transport Point (STP)
GBFD-111802 14-Digit Signaling Point 27 Configuring 14-Digit

Code Signaling Point Code
MRFD-210801 Interface Message Tracing None
MRFD-210802 User Signaling Tracing None
GBFD-112203 Cell Tracing None
GBFD-111301 LAPD Multiplexing at Abis 129 Configuring Flex Abis

Interface
GBFD-114802 Discontinuous Reception 28 Configuring

(DRX) Discontinuous Reception
(DRX)
GBFD-111601 BTS Power Management 29 Configuring BTS Power

Management
GBFD-110703 Enhanced Power Control 30 Configuring Enhanced

Algorithm Power Control Algorithm
GBFD-113525 DTMF Downlink Message 31 Configuring DTMF

Filter Downlink Message Filter
GBFD-115201 High Speed Signaling 32 Configuring High Speed

Signaling
GBFD-110521 Guaranteed Emergency Call 33 Configuring

Guaranteed Emergency
Call
GBFD-511001 License Control for Urgency 34 Configuring License

Control for Urgency
GBFD-117601 HUAWEI III Power Control 35 Configuring HUAWEI

Algorithm III Power Control
Algorithm
GBFD-111801 Ater Interface 4:1 None

Multiplexing
GBFD-119001 Gb Interface Function None

GBSS14.0
GBFD-111803 A Interface Circuit None

Management
GBFD-111804 A Interface Protocol Process None
GBFD-111805 A Interface Occupation Rate None

Monitoring
GBFD-113904 Satellite Transmission over 36 Configuring the satellite

Pb Interface transmission on the Pb
interface
GBFD-119101 Packet Channel Combination None

Type
GBFD-119102 Packet System Information None
GBFD-119103 MS Types None
GBFD-119104 MAC Mode None
GBFD-119105 RLC Mode None
GBFD-119106 Coding Scheme None
GBFD-119107 Networking Control Mode None
GBFD-119108 Network Operation Mode None

Support
GBFD-119109 QoS(Best Effort) None
GBFD-119110 Access None
GBFD-119111 Assignment None
GBFD-119112 PS Paging None
GBFD-119113 Timing Advance Update None
GBFD-119115 Power Control None
GBFD-119116 Packet Uplink Flow Control None
GBFD-119117 Flow Control on Gb Interface None
GBFD-113101 PDCH Dynamic Adjustment 37 Configuring PDCH

Dynamic Adjustment
GBFD-119205 Dynamically Adjusting the None

RRBP Frequency
GBFD-119303 Load Sharing None
GBFD-119501 Adaptive Adjustment of None

Uplink and Downlink
Channels

GBSS14.0
MRFD-210601 Connection with TMA 38 Configuring Connection

(Tower Mounted Amplifier) with TMA
MRFD-210602 Remote Electrical Tilt 39 Configuring Remote

Electrical Tilt
MRFD-210604 2-Antenna Receive Diversity 40 Configuring 2-Antenna

Receive Diversity
MRFD-210501 BTS/NodeB Clock 41 Configuring BTS Clock
MRFD-210502 BSC/RNC Clock None
GBFD-119301 Voice Fault Diagnosis 42 Configuring Voice Fault

Detection
GBFD-119306 Abis Crossed Pair Diagnosis 43 Configuring Abis

Crossed Pair Diagnosis
GBFD-119307 Spectrum Scan None
GBFD-119308 Intermodulation Testing None
GBFD-118607 IP Performance Monitor 44 Configuring IP

Performance Monitor
GBFD-118614 GSM PS Service Map 45 Configuring GSM PS

Service Map
MRFD-210701 Documentation None
MRFD-210001 Multi-mode BS Common 46 Configuring Multi-

CPRI Interface(GBTS) mode BS Common CPRI
Interface (GBTS)
MRFD-210002 Multi-mode BS RRU/RFU None

star-connection with separate
CPRI interface(GBTS)
Table 2-2 GBSS Optional Feature List

Feature ID Feature Name License License Configuration
Control Item Configured Method
on...
GBFD-113301 Enhanced Full Enhanced Full BSC6900 47 Configuring

Rate Rate Function Enhanced Full
(per TRX) or Rate (EFR)
Enhanced Full
Rate Resource
(per TRX)

GBSS14.0

on...
GBFD-115601 Automatic Automatic BSC6900 48 Configuring

Level Control Level Control Automatic
(ALC) Function (per Level Control
TRX) (ALC)
GBFD-115602 Acoustic Echo Acoustic Echo BSC6900 49 Configuring

Cancellation Cancellation Acoustic Echo
(AEC) Function (per Cancellation
TRX) (AEC)

Noise Restraint Noise Restraint Automatic
(ANR) (ANR) Function Noise Restraint
(per TRX) (ANR)
GBFD-115701 TFO TFO Function BSC6900 51 Configuring

(per TRX) or TFO
TFO Support
Resource (per
TRX)
GBFD-115702 TrFO TrFO Function BSC6900 None

(per TRX)

Noise Noise Automatic
Compensation Compensation Noise
(ANC) (ANC) Function Compensation
(per TRX) (ANC)
GBFD-115704 Enhancement Enhancement BSC6900 53 Configuring

Packet Loss Packet Loss Enhancement
Concealment Concealment Packet Loss
(EPLC) (EPLC) Concealment
Function (per (EPLC)
TRX)
GBFD-115711 EVAD EVAD (per BSC6900 54 Configuring

TRX) EVAD
GBFD-116801 Voice Quality Voice Quality BSC6900 55 Configuring

Index (VQI) Index (VQI) Voice Quality
Function (per Index (VQI)
TRX)
GBFD-115708 Um Interface Um Interface BSC6900 56 Configuring

Speech Frame Speech Frame Um Interface
Repairing Repairing (per Speech Frame
TRX) Repairing

GBSS14.0

on...
GBFD-115501 AMR FR AMR Resource BSC6900 57 Configuring

FR(per TRX) AMR
GBFD-115502 AMR HR AMR HR BSC6900 57 Configuring

Function (per AMR
TRX) or AMR
HR Resource
(per TRX)
GBFD-115503 AMR Power AMR Power BSC6900 57 Configuring

Control Control AMR
Function (per
TRX)
GBFD-115504 AMR FR/HR AMR FR/HR BSC6900 202

Dynamic Dynamic Configuring
Adjustment Adjustment HUAWEI II
Function (per Handover
TRX)
GBFD-115505 AMR Radio AMR Wireless BSC6900 57 Configuring

Link Timer Link Timer AMR
Function (per
TRX)
GBFD-115506 AMR Coding AMR Coding BSC6900 58 Configuring

Rate Threshold Rate Threshold AMR Coding
Adaptive Adaptive Rate
Adjustment Adjustment Threshold
Function (per Adaptive
TRX) Adjustment
GBFD-115507 WB AMR WB AMR BSC6900 59 Configuring

Resource (per WB AMR
TRX)
GBFD-113401 Half Rate Half Rate BSC6900 60 Configuring

Speech Resource (per Half Rate
TRX) Speech (HR)
GBFD-113402 Dynamic Dynamic BSC6900 61 Configuring

Adjustment Adjustment Dynamic
Between FR and Between FR and Adjustment
HR HR Function Between FR
(per TRX) and HR
GBFD-115522 Dynamic HR/ Dynamic HR/ BSC6900 62 Configuring

FR Adaptation FR Adaptation Dynamic HR/
Function (per FR Adaptation
TRX)

GBSS14.0

on...
GBFD-115830 VAMOS VAMOS (per BSC6900 63 Configuring

TRX) VAMOS
GBFD-115831 Mute SAIC MS Mute SAIC MS BSC6900 64 Configuring

Identification Identification Mute SAIC MS
(per TRX) Identification
GBFD-115832 VAMOS Call VAMOS Call BSC6900 65 Configuring

Drop Solution Drop Solution VAMOS Call
(per TRX) Drop Solution
GBFD-113601 Short Message Short Message BSC6900 66 Configuring

Service Cell Service Cell Short Message
Broadcast Broadcast Service Cell
(TS23) (TS23) Broadcast
Function (per (TS23)
TRX)
GBFD-113602 Simplified Cell Simplified Cell BSC6900 67 Configuring

Broadcast Broadcast Simplified Cell
Function (per Broadcast
TRX)
GBFD-510301 Public Voice Basic Voice BSC6900 68 Configuring

Group Call Group Call VGCS and
Service Service(VGCS) VBS
Resource (per
TRX)
GBFD-510303 Late Group Late Group Call BSC6900 68 Configuring

Channel Channel VGCS and
Assignment Assignment VBS
Function (per
TRX)
GBFD-510305 Single Channel Single Channel BSC6900 68 Configuring

Group Call Group Call VGCS and
Originating Originating VBS
Function (per
TRX)
GBFD-510306 Talker Talker BSC6900 68 Configuring

Identification Identification VGCS and
function (per VBS
TRX)
GBFD-510307 Group Call Group Call BSC6900 68 Configuring

EMLPP EMLPP VGCS and
Function (per VBS
TRX)

GBSS14.0

on...
GBFD-510308 Fast Group Call Fast Group Call BSC6900 68 Configuring

Setup Setup Function VGCS and
(per TRX) VBS
GBFD-510309 Group Call Group Call BSC6900 68 Configuring

Reliability Reliability VGCS and
Enhancing Enhancing VBS
Function (per
TRX)
GBFD-510302 Public Voice Basic Voice BSC6900 68 Configuring

Broadcast Broadcast VGCS and
Service Service(VBS) VBS
Resource (per
TRX)
GBFD-510304 Late Broadcast Late Broadcast BSC6900 68 Configuring

Channel Channel VGCS and
Assignment Assignment VBS
Function (per
TRX)
GBFD-510310 GSM-T Relay GSM-T Relay BSC6900 69 Configuring

(per TRX) GSM-T Relay
GBFD-115402 BSS-Based LCS(CELL ID BSC6900 70 Configuring

LCS (Cell ID + +TA) Function LCS (cell ID +
TA) (per TRX) TA)
GBFD-115404 Lb Interface Lb Interface BSC6900 71 Configuring

Lb Interface
GBFD-116001 Resource Channel BSC6900 72 Configuring

Reservation Reserved Resource
Function (per Reservation
TRX)
GBFD-115001 Enhanced Multi eMLPP BSC6900 73 Configuring

Level Function (per Enhanced
Precedence and TRX) Multi Level
Preemption Precedence
(EMLPP) and
Preemption
(eMLPP)
GBFD-115002 Flow Control Flow Control BSC6900 74 Configuring

Based on Cell Based on Cell Flow Control
Priority Priority Based on Cell
Function (per Priority
TRX)

GBSS14.0

on...
GBFD-115003 Flow control Flow control BSC6900 75 Configuring

based on User based on User Flow Control
priority priority (per Based on User
TRX) Priority
GBFD-119907 PS Service in PS Service in BSC6900 76 Configuring

Priority Priority (Per PS Service in
64Kbps) Priority
GBFD-114101 GPRS GPRS Software BSC6900 77 Configuring

Function (per GPRS
TRX)
GBFD-510001 Network Network BSC6900 78 Configuring

Operation Mode operation mode Network
I I Function (per Operation
64Kbps) Mode I
GBFD-114201 EGPRS EDGE BSC6900 79 Configuring

Resource (per EGPRS
TRX)
GBFD-510002 Gb Over FR GB Over FR BSC6900 None

Resource (per
64Kbps)
GBFD-119201 11-Bit EGPRS 11-Bit EGPRS BSC6900 80 Configuring

Access Access 11-Bit EGPRS
Function (per Access
64Kbps)
GBFD-119203 Extended Extended BSC6900 80 Configuring

Uplink TBF Uplink TBF 11-Bit EGPRS
Function (per Access
64Kbps)
GBFD-119302 Packet Channel Packet Channel BSC6900 81 Configuring

Dispatching Dispatching Packet
Function (per Channel
64Kbps) Dispatching
GBFD-119509 GPRS Fast GPRS Packet BSC6900 None

Transmission Fast
Transmission
(per TRX)
GBFD-119901 Streaming QoS GBR Qos BSC6900 82 Configuring

(GBR) Function (per Streaming QoS
64Kbps) (GBR)

GBSS14.0

on...
GBFD-119902 QoS QoS Function BSC6900 83 Configuring

ARP&THP (per 64Kbps) QoS
ARP&THP
GBFD-119904 PS Active PS Active BSC6900 84 Configuring

Package Queue PS Active
Management Management Package
Function (per Management
64Kbps)
GBFD-119905 PoC QoS PoC QoS BSC6900 85 Configuring

Function (per PoC QoS
TRX)
GBFD-119906 Conversational Conversational BSC6900 86 Configuring

QoS Qos Function Conversational
(per 64Kbps) QoS
GBFD-116201 Network- NC2 Function BSC6900 87 Configuring

Controlled Cell (per TRX) NC2
Reselection
(NC2)
GBFD-116301 Network NACC Function BSC6900 88 Configuring

Assisted Cell (per TRX) Network
Change Assisted Cell
(NACC) Change
(NACC)
GBFD-119801 Packet SI Status Packet SI Status BSC6900 88 Configuring

(PSI) (PSI) Function Network
(per 64Kbps) Assisted Cell
Change
(NACC)
GBFD-119305 BSS Paging BSS Paging BSC6900 89 Configuring

Coordination Coordination BSS Paging
Function (per Coordination
TRX) or BSS
Paging
Coordination
Resource (per
TRX)
GBFD-119502 PS Handover PS Handover BSC6900 90 Configuring

Function (per PS Handover
64Kbps)

GBSS14.0

on...
GBFD-119503 Early TBF Early TBF BSC6900 None

Establishment Establishment
Function (per
64Kbps)
GBFD-119504 PS Power PS Power BSC6900 91 Configuring

Control Control (Per PS Power
64Kbps) Control
GBFD-119505 PDCH Dynamic Two Thresholds BSC6900 92 Configuring

Adjustment PDCH Dynamic PDCH
with Two Adjustment (Per Dynamic
Thresholds 64Kbps) Adjustment
with Two
Thresholds
GBFD-119506 GPRS/EGPRS GPRS/EGPRS BSC6900 93 Configuring

Time slot Time slot Timeslot
multiplexing multiplexing Multiplexing
priority priority (per Priority for
TRX) GPRS/EGPRS
User
GBFD-119401 Extended EDA Function BSC6900 94 Configuring

Dynamic (per 64Kbps) EDA
Allocation
(EDA)
GBFD-119402 MS High Terminal BSC6900 95 Configuring

Multislot multislot classes MS High
Classes Function (per Multislot
TRX) Classes
GBFD-114151 DTM DTM Function BSC6900 96 Configuring

(per 64Kbps) or DTM
DTM Resources
(per TRX)
GBFD-119403 Class11 DTM DTM High BSC6900 97 Configuring

Multi-slot class Class11 DTM
11 Function (per
64Kbps)
GBFD-119404 HMC DTM HMC DTM BSC6900 98 Configuring

Function (per HMC DTM
64Kbps)

GBSS14.0

on...
GBFD-119405 14.4kbit/s 14.4Kbps BSC6900 99 Configuring

Circuit Circuit 14.4 kbit/s
Switched Data Switched Data Circuit
Function (per Switched Data
TRX)
GBFD-119406 High Speed High Speed BSC6900 100

Circuit Circuit Configuring
Switched Data Switched Data High Speed
(per TRX) Circuit
Switched Data
GBFD-119407 Active TBF Active TBF BSC6900 101

Allocation Allocation (per Configuring
TRX) Active TBF
Allocation
GBFD-510801 MSRD MSRD BSC6900 102

Function (per Configuring
TRX) MSRD
GBFD-510802 Dual Carriers in Dual Carriers in BSC6900 103

Downlink Downlink Configuring
Function (per Dual Carriers
TRX) in Downlink
GBFD-510803 Uplink Uplink BSC6900 104

EGPRS2-A EGPRS2-A Configuring
Resource (per the EGPRS2-A
TRX)
GBFD-510804 Downlink Downlink BSC6900 104

EGPRS2-A EGPRS2-A Configuring
Resource (per the EGPRS2-A
TRX)
GBFD-510805 Latency Latency BSC6900 105

Reduction Reduction Configuring
Function (per Latency
64Kbps) Reduction
GBFD-511603 IM Service IM Service BSC6900 106

Efficiency Efficiency Configuring
Improvement Improvement IM Service
(per TRX) Efficiency
Improvement

GBSS14.0

on...
GBFD-511604 Web Browsing Web Browsing BSC6900 107

Service Service Configuring
Efficiency Efficiency Web Browsing
Improvement Improvement Service
Improvement
GBFD-511605 Email Service Email Service BSC6900 108

Efficiency Efficiency Configuring
Improvement Improvement Email Service
Improvement
GBFD-511606 Streaming Streaming BSC6900 109

Media Service Media Service Configuring
Resource Resource Streaming
Balancing Balancing (per Media Service
TRX) Resource
Balancing
GBFD-511607 P2P Resource P2P Resource BSC6900 110

Balancing Balancing (per Configuring
TRX) P2P Resource
Balancing
GBFD-511608 WLAN Hot WLAN Hot BSC6900 111

Spot Spot Configuring
Notification Notification WLAN Hot
(per TRX) Spot
Notification
GBFD-511501 Multiple Multiple CCCH BSC6900 112

CCCHs (per TRX) Configuring
Multiple
CCCHs
GBFD-511502 Layered Paging Layered Paging BSC6900 113

(per TRX) Configuring
Layered
Paging
GBFD-511503 Dynamic Dynamic BSC6900 114

Multiple CCCH Multiple CCCH Configuring
(per CELL) Dynamic
Multiple
CCCH
GBFD-511505 RACH Storm RACH Storm BSC6900 115

Filtration Filtration (per Configuring
CELL) RACH Storm
Filtration

GBSS14.0

on...
GBFD-117602 Active Power Active Power BSC6900 116

Control Control Configuring
Function (per Active Power
TRX) Control
GBFD-114801 Discontinuous Discontinuous BSC6900 117

Transmission Transmission Configuring
(DTX)- (DTX) Discontinuous
Downlink Downlink Transmission
Function (per (DTX)-
TRX) Downlink
GBFD-114803 Discontinuous Discontinuous BSC6900 118

(DTX)-Uplink (DTX) Uplink Discontinuous
Function (per Transmission
TRX) (DTX)-Uplink
GBFD-111602 TRX Power Dynamic BSC6900 119

Amplifier Shutdown Trx Configuring
Intelligent PA Function TRX Power
Shutdown (per TRX) or Amplifier
TRX Power Intelligent
Amplifier Shutdown
Intelligent
Shutdown
Resources (per
TRX)
GBFD-111603 TRX Power Time slot BSC6900 120

Amplifier Intelligent Configuring
Intelligent Power TRX Power
Shutdown on Optimization Amplifier
Timeslot Level Function (per Intelligent
TRX) or TRX Shutdown on
Power Timeslot Level
Amplifier
Intelligent
Shutdown on
Timeslot Level
Resources (per
TRX)
GBFD-111604 Intelligent Intelligent BSC6900 121

Combiner Combiner Configuring
Bypass Bypass Intelligent
Function (per Combiner
TRX) Bypass

GBSS14.0

on...
GBFD-111605 Active Backup Active Backup BSC6900 122

Power Control Power Control Configuring
Function (per Active Backup
TRX) Power Control
GBFD-111606 Power Power BSC6900 123

Optimization Optimization Configuring
Based on Based on Power
Channel Type Channel Type Optimization
Function (per Based on
TRX) Channel Type
GBFD-111608 PSU Smart PSU Smart BSC6900 124

Control Control Configuring
Function (per PSU Smart
TRX) Control
GBFD-111609 Enhanced Enhanced BSC6900 125

BCCH Power BCCH Power Configuring
Consumption Consumption Enhanced
Optimization Optimization BCCH Power
Function (per Consumption
TRX) or Optimization
Enhanced
BCCH Power
Consumption
Optimization
Resources (per
TRX)
GBFD-111610 Dynamic Cell Dynamic Cell BSC6900 126

Power Off Power Off Configuring
Function (per Dynamic Cell
TRX) Power Off
GBFD-111611 TRX Working TRX Working BSC6900 127

Voltage Voltage Configuring
Adjustment Adjustment TRX Working
Function(per Voltage
TRX) or RX Adjustment
Working
Voltage
Adjustment
Resource (per
TRX)

GBSS14.0

on...
GBFD-111612 Multi-Carrier Multi-Carrier BSC6900 128

Intelligent Intelligent Configuring
Voltage Voltage Multi-Carrier
Regulation Function (per Intelligent
TRX) or Multi- Voltage
Carrier Regulation
Intelligent
Voltage
Regulation
Resources (per
TRX)
GBFD-116701 16Kbit RSL and 16K LAPD BSC6900 None

OML on A-bis Function (per
Interface TRX)
GBFD-117301 Flex Abis Flex Abis BSC6900 129

Resource (per Configuring
TRX) Flex Abis
GBFD-117702 BTS Local BTS local BSC6900 130

Switch switching Configuring
Resource (per BTS Local
TRX) Switch
GBFD-118401 Abis Transmission BSC6900 131

Transmission optimization on Configuring
Optimization the Abis Abis
interface Transmission
Resource (per Optimization
TRX)
GBFD-112013 Abis Abis BSC6900 132

Congestion Congestion Configuring
Trigger HR Trigger HR Abis
Distribution Distribution Congestion
Function (per Trigger HR
TRX) Distribution
GBFD-116901 Flex Ater Flex Ater BSC6900 133

TRX) Flex Ater
GBFD-117701 BSC Local BSC Local BSC6900 134

Switch Switching Configuring
Resource (per BSC Local
TRX) Switch

GBSS14.0

on...
GBFD-116902 Ater Ater BSC6900 135

Compression Compression Configuring
Transmission Transmission Ater
Function (per Compression
TRX) Transmission
GBFD-115301 Local Multiple Local Multiple BSC6900 136

Signaling Points Signaling Points Configuring
Function (per Local Multiple
TRX) Signaling
Points
GBFD-117705 PS Dummy PS Dummy BSC6900 137

Frame Frame Configuring
Compression Compression PS Dummy
(per TRX) Frame
Compression
GBFD-118606 Clock over IP Clock over IP BSC6900 None

Function (per
TRX)
GBFD-118620 Clock over IP Clock over IP BSC6900 138

support 1588v2 support 1588V2 Configuring
Function (per Clock over IP
TRX) support 1588v2
GBFD-118202 Synchronous Synchronous BSC6900 139

Ethernet Ethernet(per Configuring
TRX) Synchronous
Ethernet
GBFD-118601 Abis over IP Abis Over IP BSC6900 140

TRX) Abis over IP
GBFD-118611 Abis IP over E1/ Abis IP Over BSC6900 141

T1 E1/T1 Resource Configuring
(per TRX) Abis IP over
E1/T1
GBFD-118604 Abis MUX Abis MUX BSC6900 142

TRX) Abis MUX
GBFD-118612 Abis IPHC Abis IPHC (per BSC6900 143

TRX) Configuring
Abis IPHC

GBSS14.0

on...
GBFD-118602 A over IP A Over IP BSC6900 144

Function (per Configuring A
TRX) over IP
GBFD-118622 A IP over E1/T1 A IP over E1 BSC6900 145

Function (per Configuring A
TRX) IP over E1/T1
GBFD-118610 UDP MUX for UDP MUX for BSC6900 146

A Transmission A Transmission Configuring
Function (per UDP MUX for
TRX) A
Transmission
GBFD-118623 TDM/IP Dual TDM/IP Dual BSC6900 147

over A Interface over A Interface TDM/IP Dual
(per TRX) Transmission
over A
Interface
GBFD-118603 Gb over IP GB Over IP BSC6900 148

64Kbps) Gb over IP
GBFD-118605 IP QOS IP QoS Function BSC6900 None

(per TRX)
GBFD-118630 Ethernet OAM Ethernet OAM BSC6900 149

TRX) Ethernet OAM
GBFD-118631 A Interface A Interface BSC6900 150

Transmission Transmission Configuring A
Pool Resource Pool Interface
Pool
GBFD-113901 Satellite Site Supporting BSC6900 151

Transmission Satellite Configuring
over Abis Transmission Satellite
Interface Resource (per Transmission
Site) over Abis
Interface
GBFD-113902 Satellite Satellite BSC6900 152

over A Interface over A Interface Satellite
TRX) over A
Interface

GBSS14.0

on...

over Ater over Ater Satellite
Interface Interface Transmission
Function (per over Ater
TRX) Interface

over Gb over Gb Satellite
Interface Interface Transmission
Function (per over Gb
64Kbps) Interface
GBFD-118701 RAN Sharing RAN Sharing BSC6900 155

TRX) RAN Sharing
GBFD-118702 MOCN Shared MOCN BSC6900 156

Cell Common Cell Configuring
(per TRX) MOCN Shared
Cell
GBFD-118703 IMSI-Based IMSI Based BSC6900 157

Handover Handover(per Configuring
TRX) IMSI-Based
Handover

Independent Independent Configuring
Transmission Transmission Abis
(per TRX) Independent
Transmission
GBFD-510601 PICO PICO Solution BSC6900 159

Automatic Packet Function Configuring
Configuration (per TRX) PICO/
and Planning Compact BTS
Automatic
Configuration
and Planning
GBFD-510602 PICO PICO Solution BSC6900 160

Synchronizatio Packet Function Configuring
n (per TRX) PICO
Synchronizatio
n

GBSS14.0

on...
GBFD-510603 PICO Dual- PICO Dual- BSC6900 161

band Auto- band Auto- Configuring
planning planning(per PICO Dual-
TRX) band Auto-
planning
GBFD-510604 PICO USB PICO USB BSC6900 162

Encryption Encryption(per Configuring
TRX) PICO USB
Encryption
GBFD-510605 PICO Access PICO Access BSC6900 None

Control List Control List
(ACL) (ACL)(per
TRX)
GBFD-510606 PICO Sleeping PICO Sleeping BSC6900 163

Mode Mode(per TRX) Configuring
PICO Sleeping
Mode
GBFD-510607 PICO PICO BSC6900 164

Automatic Automatic Configuring
Optimization Optimization PICO
(per TRX) Automatic
Optimization
GBFD-510608 PICO PICO BSC6900 165

Tranceiver Tranceiver Configuring
redundancy Redundancy PICO
(per TRX) Transceiver
Redundancy
GBFD-111613 Weather Weather BSC6900 166

Adaptive Power Adaptive Power Configuring
Management Management Weather
(per TRX) Adaptive
Power
Management
GBFD-510701 Compact BTS Easy GSM BSC6900 159

Automatic Solution Packet Configuring
Configuration Function (per PICO/
and Planning TRX) Compact BTS
Automatic
Configuration
and Planning

GBSS14.0

on...
GBFD-510702 Compact BTS Easy GSM BSC6900 167

Automatic Solution Packet Configuring
Capacity Function (per Compact BTS
Planning TRX) Automatic
Capacity
Planning
GBFD-510704 Compact BTS Automatic BSC6900 168

Automatic Neighbor Cell Configuring
Neighbor Cell Planning and Compact BTS
Planning and Optimization Automatic
Optimization (per TRX) Neighbor Cell
Planning and
Optimization
GBFD-510705 Compact BTS Compact BTS BSC6900 169

Timing Power Timing Power Configuring
Off Off(per TRX) Compact BTS
Timing Power
Off
GBFD-510706 Local User Local User BSC6900 170

Management Management Configuring
(per TRX) Local User
Management
GBFD-510710 Intelligent Intelligent BSC6900 171

Battery Battery Configuring
Management Management Intelligent
(per BTS) Battery
Management
GBFD-115901 PBT(Power Multi- BSC6900 172

Boost transceivers Configuring
Technology) supporting PBT PBT
transmit
Resource (per
TRX)
GBFD-115902 Transmit Multi- BSC6900 173

Diversity transceivers Configuring
supporting Transmit
diversity Diversity
transmit
Resource (per
TRX)

GBSS14.0

on...
GBFD-115903 4-Way Receiver Multi- BSC6900 174

Diversity transceivers Configuring 4-
supporting 4- Way Receiver
way receive Diversity
diversity
Resource (per
TRX)
GBFD-118101 Dynamic Dynamic PBT BSC6900 175

Transmit Resource (per Configuring
Diversity TRX) Dynamic
Transmit
Diversity
GBFD-118102 Dynamic PBT Dynamic PBT BSC6900 176

(Power Boost Resource (per Configuring
Technology) TRX) Dynamic PBT

EDGE EDGE Configuring
Coverage Coverage(per Enhanced
TRX) EDGE
Coverage
GBFD-118106 Dynamic Power Dynamic Power BSC6900 178

Sharing Sharing (per Configuring
TRX) Dynamic
Power Sharing
GBFD-114001 Extended Cell Extended cell BSC6900 179

Cell) Extended Cell
GBFD-113201 Concentric Cell Concentric Cell BSC6900 180

TRX) Concentric
Cell
GBFD-114501 Co-BCCH Cell Co-BCCH Cell BSC6900 181

TRX) Co-BCCH Cell
GBFD-114402 Enhanced Dual- Enhanced Dual- BSC6900 182

Band Network Band Network Configuring
Function (per Enhanced
TRX) Dual-Band
Network
GBFD-117001 Flex MAIO Flex MAIO BSC6900 183

TRX) Flex MAIO

GBSS14.0

on...
GBFD-115801 ICC ICC(Inference BSC6900 184

Counteract Configuring
Combine) ICC
Function (per
TRX) or ICC
Resource (per
TRX)
GBFD-115821 EICC the EICC BSC6900 185

TRX) or EICC EICC
Resources (per
TRX)
GBFD-113701 Frequency Frequency BSC6900 186

Hopping (RF Hopping Configuring
hopping, Function (per Frequency
baseband TRX) Hopping (RF
hopping) hopping,
baseband
hopping)
GBFD-113702 BCCH Carrier BCCH Carrier BSC6900 187

Frequency Frequency Configuring
Hopping Hopping BCCH Carrier
Function (per Frequency
TRX) Hopping
GBFD-113703 Antenna Antenna BSC6900 188

Hopping Hopping Antenna
TRX) Hopping
GBFD-118001 BCCH Dense BCCH Dense BSC6900 189

Multiplexing Multiplexing BCCH Dense
TRX) Multiplexing
GBFD-117002 IBCA IBCA Function BSC6900 190

(Interference (per TRX) Configuring
Based Channel IBCA
Allocation)
GBFD-118201 Soft- Soft BSC6900 191

Synchronized Synchronizatio Configuring
Network n Function (per Soft-
TRX) Synchronized
Network

GBSS14.0

on...
GBFD-510401 BTS GPS BTS GPS BSC6900 192

Synchronizatio Synchronizatio Configuring
n n Function (per BTS GPS
TRX) Synchronizatio
n
GBFD-118103 Network SAIC Function BSC6900 193

Support SAIC (per TRX) Configuring
Network
Support SAIC
GBFD-113706 Mega BSC Mega BSC (per BSC6900 194

TRX) Configuring
Mega BSC
GBFD-119507 PS Downlink PS Downlink BSC6900 195

DTX DTX (per TRX) Configuring
PS Downlink
DTX
GBFD-119508 PS Uplink DTX PS Uplink DTX BSC6900 196

(per TRX) Configuring
PS Uplink DTX
GBFD-510101 Automatic AFC Function BSC6900 197

Frequency (per TRX) Configuring
Correction Automatic
(AFC) Frequency
Correction
(AFC)
GBFD-510102 Fast Move High Speed BSC6900 198

Handover PBGT Switch Configuring
Fast Move
Handover
GBFD-510103 Chain Cell Chain Cell BSC6900 199

Handover Handover Configuring
Function (per Chain Cell
TRX) Handover
GBFD-510104 Multi-site Cell Multi-site Cell BSC6900 200

TRX) or Multi-Site Cell
Maximum
Slave Module
number allowed
Resource (per
Module)

GBSS14.0

on...
GBFD-510105 PS AFC PS AFC (per BSC6900 201

TRX) Configuring
PS Automatic
Frequency
Correction (PS
AFC)
GBFD-510501 HUAWEI II HUAWEI II BSC6900 202

Handover Handover Configuring
Function (per HUAWEI II
TRX) Handover
GBFD-510502 Handover Re- Handover Re- BSC6900 203

establishment establishment Configuring
Function (per Handover Re-
TRX) establishment

Measurement Measurement Configuring
Report(EMR) Report(EMR) Enhanced
Function (per Measurement
TRX) Report
GBFD-117101 BTS power lift BTS power lift BSC6900 205

for handover for handover Configuring
Function (per BTS power lift
TRX) for handover
GBFD-114301 GSM/WCDMA Intersystem BSC6900 206

Interoperability Handover & Configuring
Reselection GSM/
Function (per WCDMA
TRX) Interoperabilit
y

Service Based Handover due to Configuring
Handover Service GSM/
Function (per WCDMA
TRX) Service Based
Handover

Load Based Handover due to Configuring
Handover Load Function GSM/
(per TRX) WCDMA Load
Based
Handover

GBSS14.0

on...
GBFD-114323 2G/3G Cell 2G/3G Cell BSC6900 209

Reselection Reselection Configuring
Based on MS Based on MS 2G/3G Cell
State State Function Reselection
(per TRX) Based on MS
State
GBFD-114325 Fast WCDMA Fast 3G BSC6900 210

Reselection at Reselection at Configuring
2G CS Call 2G Cs Call the Fast
Release Release WCDMA
Function (per Reselection at
TRX) 2G CS Call
Release
GBFD-511101 Load Based Handover BSC6900 211

Handover Based on Load Configuring
Enhancement on Iur-g Load Based
on Iur-g Function (per Handover
TRX) Enhancement
on Iur-g
GBFD-511102 NACC NACC BSC6900 212

Procedure Procedure Configuring
Optimization Optimization NACC
Based on Iur-g Based on Iur-g (Network
between GSM Function (per Assisted Cell
and WCDMA TRX) Change)
Procedure
Optimization
Based on Iur-g
between GSM
and WCDMA
GBFD-511103 GSM and BSC Load BSC6900 213

WCDMA Load Balancing Configuring
Balancing Based on Iur-g GSM and
Based on Iur-g Function (per WCDMA Load
TRX) Balancing
Based on Iur-g
GBFD-511104 GSM and BSC Service BSC6900 214

WCDMA Distribution Configuring
Traffic Steering Based on Iur-g GSM and
Based on Iur-g Function (per WCDMA
TRX) Traffic
Steering Based
on Iur-g

GBSS14.0

on...
GBFD-511110 Blind Search BSC supporting BSC6900 215

Blind Search Configuring
(per TRX) BSC
supporting
Blind Search
GBFD-511301 Cell Reselection Cell Reselection BSC6900 216

Between GSM Between GSM Configuring
and LTE and LTE(per Cell
TRX) Reselection
Between GSM
and LTE
GBFD-511302 PS Handover PS Handover BSC6900 217

and LTE Based and LTE Based PS Handover
on Coverage on Coverage Between GSM
(per TRX) and LTE Based
on Coverage

on Quality on Quality(per Between GSM
TRX) and LTE Based
on Quality

on Cell Load on Cell Load Between GSM
(per TRX) and LTE Based
on Cell Load
GBFD-511305 PS Handover PS Handover BSC6900 None

Between GSM Between GSM
and LTE Based and LTE Based
on Mode on Mode
Priority Priority (per
TRX)
GBFD-511306 GSM/LTE GSM/LTE BSC6900 220

Service Based Service Based Configuring
PS Handover PS Handover GSM/LTE
(per TRX) Service Based
PS Handover
GBFD-511307 eNC2 Between eNC2 Between BSC6900 221

GSM and LTE GSM and LTE Configuring
(per TRX) eNC2 Between
GSM and LTE

GBSS14.0

on...
GBFD-511308 eNACC eNACC BSC6900 222

and LTE and LTE (per eNACC
TRX) Between GSM
and LTE
GBFD-511309 SRVCC SRVCC (per BSC6900 223

TRX) Configuring
SRVCC
GBFD-511310 Multi Multi BSC6900 224

Technology Technology Configuring
Neighbour Cell Neighbour Cell Multi
Based Based Technology
Handover Handover (per Neighbour Cell
TRX) Based
Handover
GBFD-511312 Fast LTE Fast LTE BSC6900 225

Reselection at Reselection at Configuring
2G CS Call GSM CS Call Fast LTE
Release Release (per Reselection at
TRX) 2G CS Call
Release
GBFD-511313 CSFB CSFB (per BSC6900 226

TRX) Configuring
CSFB
GBFD-114302 GSM/TD- Intersystem BSC6900 227

SCDMA Handover & Configuring
Interoperability Reselection GSM/TD-
Function (per SCDMA
TRX) or GSM/ Interoperabilit
TD-SCDMA y
Interoperability
Resources (per
TRX)
GBFD-511401 Iur-g Interface Iur-g Interface BSC6900 228

and TD- and TD- Iur-g Interface
SCDMA SCDMA(per Between GSM
TRX) and TD-
SCDMA

GBSS14.0

on...
GBFD-511402 Radio Resource Radio Resource BSC6900 229

Reserved Reserved Configuring
Handover Handover Radio
Between GSM/ Between GSM/ Resource
TD-SCDMA TD-SCDMA Reserved
Based on Iur-g Based on Iur-g Handover
(per TRX) Between GSM/
TD-SCDMA
Based on Iur-g
GBFD-511403 Extended Extended BSC6900 230

BCCH BCCH (per Configuring
TRX) Extended
BCCH
GBFD-511405 NC2 Between NC2 between BSC6900 231

GSM and TD- GSM and TD- Configuring
SCDMA SCDMA (per NC2 Between
TRX) GSM and TD-
SCDMA
GBFD-113501 A5/1 and A5/2 Encryption BSC6900 232

Ciphering (A5/1,A5/2) Configuring
Algorithm Function (per Ciphering
TRX)
GBFD-113503 A5/3 Ciphering Encryption BSC6900 232

Algorithm (A5/3) Function Configuring
(per TRX) Ciphering
GBFD-113521 A5/1 Enhanced BSC6900 233

Encryption Encryption Configuring
Flow Function (per A5/1
Optimization TRX) Encryption
Flow
Optimization
GBFD-113522 Encrypted Encrypted BSC6900 None

Network Network
Management Management
Function (per
TRX)
GBFD-113524 BTS Integrated BTS Integrated BSC6900 234

IPsec IPsec (per BTS) Configuring
BTS
Integrated
IPsec

GBSS14.0

on...
GBFD-113526 BTS Supporting BTS Supporting BSC6900 235

PKI PKI (per BTS) Configuring
BTS
Supporting
PKI
GBFD-117801 Ring Topology Ring topology BSC6900 236

TRX) Ring Topology
GBFD-113801 TRX TRX BSC6900 237

Cooperation Cooperation Configuring
Function (per TRX
TRX) Cooperation
GBFD-117401 MSC Pool MSC POOL BSC6900 238

TRX) MSC Pool
GBFD-119701 SGSN Pool Gb Flex BSC6900 239

64Kbps) the SGSN Pool
GBFD-116601 Abis Bypass Abis Bypass BSC6900 240

TRX) Abis Bypass
GBFD-113721 Robust Air Robust Air BSC6900 241

Interface Interface Configuring
Signalling Signalling Robust Air
Function (per Interface
TRX) Signalling

Backup Backup Abis
TRX) Backup
GBFD-113725 BSC Node BSC Node BSC6900 243

Redundancy Redundancy Configuring
Function (per BSC Node
TRX) Redundancy
GBFD-113726 TC Pool TC Pool BSC6900 244

TRX) TC Pool
GBFD-113728 OML Backup OML Backup BSC6900 245

TRX) OML Backup

GBSS14.0

on...
GBFD-511002 Access Control Access Control BSC6900 246

Class(ACC) Class(per TRX) Configuring
Access Control
Class
GBFD-113729 Adaptive Adaptive BSC6900 247

Link Blocking Link Blocking Adaptive
Link Blocking
GBFD-114701 Semi- Semipermanent BSC6900 248

Permanent Connection Configuring
Connection Resource (per Semi-
LINK) Permanent
Connection
GBFD-116401 End-to-End MS End-to-End MS BSC6900 249

Signaling Signaling Configuring
Tracing Tracing End-to-End
Function (per MS Signaling
TRX) Tracing
GBFD-510901 2G/3G 2G/3G BSC6900 None

Neighboring Neighboring
Cell Automatic Cell Automatic
Optimization Optimization
Function (per
TRX)
GBFD-511701 Radio Radio BSC6900 250

Measurement Measurement Configuring
Data Interface Data Interface Radio
for Navigation for Navigation Measurement
(per TRX) Data Interface
for Navigation
MRFD-211801 Multi-mode GSM and BSC6900 251

Dynamic Power UMTS Configuring
Sharing(GSM) Dynamic Power Multi-mode
Sharing Dynamic
Power Sharing
(GSM)
MRFD-211802 GSM and GSM and BSC6900 252

UMTS UMTS Configuring
Dynamic Dynamic GSM and
Spectrum Spectrum UMTS
Sharing(GSM) Sharing(Per Dynamic
Site) Spectrum
Sharing(GSM)

GBSS14.0

on...
MRFD-211501 IP-Based Multi- None None 253

mode Co- Configuring
Transmission IP-Based
on BS side Multi-mode
(GBTS) Co-
Transmission
on BS side
(GBTS)
MRFD-211504 TDM-Based None None 254

Multi-mode Co- Configuring
Transmission TDM-Based
via Backplane Multi-mode
on BS side Co-
(GBTS) Transmission
via Backplane
on BS side
(GBTS)
MRFD-211505 Bandwidth Bandwidth NodeB None

sharing of sharing of
MBTS Multi- MBTS Multi-
mode Co- mode Co-
Transmission Transmission
(GBTS) (NodeB)(Per
NodeB)
MRFD-211601 Multi-mode BS None None 255

Common Configuring
Reference Multi-Mode
Clock(GBTS) BS Common
Reference
Clock (GBTS)
MRFD-211703 2.0MHz Central 2.0MHz Central BSC6900 None

Frequency point Frequency point
separation separation
between GSM between GSM
and UMTS and UMTS
mode(GSM) mode(Per Site)
MRFD-211803 GSM and Dynamic MA BSC6900 256

UMTS for GU Configuring
Dynamic Dynamic Dynamic MA
Spectrum Spectrum for GU
Sharing(GSM) Sharing(per Dynamic
BTS) Spectrum
Sharing (GSM)

GBSS14.0

on...
MRFD-211804 2.0MHz Central GSM Power BSC6900 257

Frequency point Control on Configuring
separation Interference GSM Power
between GSM Frequency for Control on
and UMTS GU Small Interference
mode(GSM) Frequency gap Frequency for
(per BTS) GU Small
Frequency
Gap (GSM)
MRFD-211602 Multi-mode BS Co-IPSec BSC6900 258 Multi-

Common IPSec Between mode BS
(GSM) GSM,UMTS Common
and LTE (per IPSec(GSM)
BTS)

GBSS14.0
Feature Activation Guide 3 Overview of Configurations on the CME
3 Overview of Configurations on the CME
About This Chapter
This section provides an overview of the configuration on the CME. The CME is a configuration
tool on GUIs assisting you to effectively configure the data about wireless NE features. You can
reconfigure configuration parameters by using the configuration expresses provided by the CME
to activate or deactivate specified features.
Feature activation and deactivation are mainly performed on the configuration expresses on the
CME. This part introduces the operations on the configuration expresses and you need to
understand the operations before activating or deactivating features.
3.1 Introduction to Configuration Methods
This section describes how to configure the features of one or multiple NEs at a time by using
the CME.
3.2 Configuring Device Data
This section describes how to configure device data on the device panel.
3.3 Introduction to the Configuration Express for BSCs
This section describes the structure and provides the configuration guidance to the configuration
express for BSCs.
3.4 Introduction to the Configuration Express for A Interfaces
express for A interfaces.
3.5 Introduction to the Configuration Express for Ater Interfaces
express for Ater interfaces.The configuration express for Ater interfaces cannot be used for
configuration of the BSC6910.
3.6 Introduction to the Configuration Express for Gb Interfaces
express for Gb interfaces.
3.7 Introduction to the Configuration Express for the (G)Iur-g Interface
express for the (G)Iur-g interface.
3.8 BSC Abis IP Configuration Express

GBSS14.0
This section describes the structure of the BSC Abis IP configuration express and provides a
configuration guidance.
3.9 Introduction to the Configuration Express for Abis Interfaces
express for Abis interfaces.
3.10 Introduction to the BTS Topology View
This section provides the introduction to the BTS topology view. The CME provides the BTS
topology view to display information including networking relationships, physical connections,
and port information between the BSC and the BTS, and between BTSs in an intuitive manner.
The CME also allows you to perform operations including creating sites and cells, configuring
frequencies and TRXs, and browsing timeslots. This improves configuration and maintenance
efficiency.
3.11 Introduction to the Configuration Express for BTSs
express for BTSs.
3.12 Configuration Express for BTS IP Addresses
express for BTS IP addresses.
3.13 Introduction to the GSM Device Panel
This section provides the introduction to the GSM device panel, including the structure and
configuration guidance to device panels for the BSC and the BTS and the RXU topology view.
3.14 Introduction to the Configuration Express for TRXs
express for TRXs.
3.15 Introduction to the Configuration Express for GSM Cells
express for GSM cells.
3.16 Introduction to the Configuration Express for Neighboring GSM Cells
express for neighboring GSM cells.
3.17 Modifying GBSC Parameters in Batches
This section describes how to change values of specified parameters for specified GBSCs in
batches.
3.18 Modifying GBTS Parameters in Batches
This section describes how to change values of specified parameters for specified GBTSs in
batches.
3.19 Deleting GSM Cells in Batches
This section describes how to delete GSM cells in batches.
3.20 Modifying GSM Cell Parameters in Batches
This section describes how to change values of specified parameters for specified GSM cells in
batches.
3.21 Modifying BSC External Cell Parameters in Batches
This section describes how to change values of specified parameters for specified BSC external
cells in batches.
3.22 Modifying GSM TRX Parameters in Batches

GBSS14.0
This section describes how to change values of specified parameters for specified TRXs in
batches.
3.23 Introduction to the Object Group Configuration
This section describes how to search for external cells in an object group and configure them.

GBSS14.0
3.1 Introduction to Configuration Methods

This section describes how to configure the features of one or multiple NEs at a time by using
the CME.
Introduction to Configuration Methods

The CME enables you to configure NE features in both single and batch modes. For details, see
Table 3-1.
Table 3-1 Introduction to configuration methods
Config Characteristics
uratio
n
Metho
d
Single Configures parameters for only one object (for example, a base station or a cell)
configu each time.
ration The CME provides configuration expresses and device panels for various types of
data to configure one object.
l The CME displays a navigation tree in the left pane and a table in the right pane.
The navigation tree shows managed objects (MOs) while the table shows the
parameters of the MOs and parameter values. After selecting an MO in the
navigation tree, you can configure its values in the table.
l The device panel is displayed on a GUI, allowing you to directly configure data
for devices such as cabinet, subrack, and board.
Batch Applies the configuration data about an object (for example, a base station or a
modific cell) to other objects.
ation NOTE
center This method is applicable to scenarios where the parameters for multiple objects need to be
configured the same.
For example, after setting the VAMOSSWITCH parameter for cell 1 to ON, you
can use the batch modification function to set the VAMOSSWITCH parameters
for other specified cells to ON at a time. By doing this, you do not need to configure
the parameters for these cells one by one.
Introduction to Data Configuration Procedures

Before using the CME to configure features, you need to be familiar with basic operations on
the CME. For details, see CME Guidelines in the M2000 Help.
The procedures for using the CME to activate or deactivate features are as follows:
1. Synchronize the data in the current data area with the data on the live network.
2. Create a planned data area and copy the data in the current data area to the planned data
area for configuration.

GBSS14.0
3. Modify the parameters according to the planned data.

4. After configuring data, export the data as scripts.
5. Deliver the exported scripts to the live network for the configuration data to take effect on
NEs.
3.2 Configuring Device Data

This section describes how to configure device data on the device panel.
Right-click a BSC to be configured in the Main View navigation tree in the left pane, and choose
Device Panel from the shortcut menu. The NE device panel is displayed, as shown in Figure
3-1.
Figure 3-1 Device panel

GBSS14.0
Operatio Operation description

n
Add l In the upper-right part of the device panel window, click Add Cabinet.
l Right-click an empty subrack on the device panel window, and choose Add
Subrack from the shortcut menu.
l Right-click the empty slots on the panels of each subrack, and choose the
required board types from the shortcut menu.
Delete l Right-click a cabinet to be deleted, and choose Delete Cabinet from the
shortcut menu.
l Right-click a subrack to be deleted, and choose Delete Subrack from the
shortcut menu.
l Right-click a board to be deleted, and choose Delete Board from the shortcut
menu.
View or Right-click a device to be viewed or modified, and choose Property to view or

modify modify the device.
3.3 Introduction to the Configuration Express for BSCs

express for BSCs.
The configuration express provides a window for configuring BSC-level objects, as shown in
Figure 3-2.
Figure 3-2 Configuration express for BSCs

GBSS14.0
Configuration Guidance
1. In area 1, choose The NE to be configured > GSM > BSC in the Transport navigation
tree. The express window for configuring BSCs is displayed.
2. In area 2, select an object to be configured in the Properties navigation tree. The
configuration parameters of the object are displayed in area 3.
TIP
In area 2, you can also type the parameters to be configured on the tab pages Parameter List and
Search. This helps to quickly locate parameters.
3. In area 3, configure the data.
3.4 Introduction to the Configuration Express for A

Interfaces
express for A interfaces.
The configuration express provides a window for configuring interface-level objects, as shown
in Figure 3-3.
Figure 3-3 Configuration express for A interfaces
1. In area 1, choose The NE to be configured > GSM > A in the Transport navigation tree.
The express window for configuring A interfaces is displayed.

GBSS14.0
TIP
3.5 Introduction to the Configuration Express for Ater

Interfaces
express for Ater interfaces.The configuration express for Ater interfaces cannot be used for
configuration of the BSC6910.
in Figure 3-4.
Figure 3-4 Configuration express for Ater interfaces
1. In area 1, choose The NE to be configured > GSM > Ater in the Transport navigation
tree. The express window for configuring Ater interfaces is displayed.
TIP

GBSS14.0
3.6 Introduction to the Configuration Express for Gb

Interfaces
express for Gb interfaces.
The configuration express provides a window for objects of interface-level objects, as shown in
Figure 3-5.
Figure 3-5 Configuration express for Gb interfaces
1. In area 1, choose The NE to be configured > GSM > Gb in the Transport navigation
tree. The express window for configuring Gb interfaces is displayed.
TIP

GBSS14.0
3.7 Introduction to the Configuration Express for the (G)Iur-

g Interface
express for the (G)Iur-g interface.
in Figure 3-6.
Figure 3-6 Configuration express for the (G)Iur-g interface
1. In area 1, choose The NE to be configured > GSM > Iur-g in the Transport navigation
tree. The configuration express window for configuring (G)Iur-g interfaces is displayed.
TIP
3.8 BSC Abis IP Configuration Express

This section describes the structure of the BSC Abis IP configuration express and provides a
configuration guidance.

GBSS14.0
Portal to BSC Abis IP Configuration Express

1. In area 1 of the Figure 3-7, right-click a GSM NE to be configured in the Main View
navigation tree, and choose Show BTS Topology from the shortcut menu. The BTS
topology view is displayed, as shown in Figure 3-7.
Figure 3-7 BTS topology view
2. In Figure 3-7, select an IP interface board in area 3, right-click an IP interface board in

area 2, and choose Configure BSC ABIS IP Properties from the shortcut menu. The
express window for configuring BSC Abis IP addresses is displayed, as shown in Figure
3-8.

GBSS14.0
Figure 3-8 BSC Abis IP configuration express
1. In area 1 of the Figure 3-8, select an object to be configured in the Properties navigation
tree. The configuration parameters of the object are displayed in area 2.
TIP
2. In area 2 of the Figure 3-8, configure the parameters.
3.9 Introduction to the Configuration Express for Abis

Interfaces
express for Abis interfaces.
in Figure 3-9.

GBSS14.0
Figure 3-9 Configuration express for Abis interfaces
1. In area 1, choose The NE to be configured > GSM > Abis in the Transport navigation
tree. The express window for configuring Abis interfaces is displayed.
TIP
3.10 Introduction to the BTS Topology View

This section provides the introduction to the BTS topology view. The CME provides the BTS
topology view to display information including networking relationships, physical connections,
and port information between the BSC and the BTS, and between BTSs in an intuitive manner.
The CME also allows you to perform operations including creating sites and cells, configuring
frequencies and TRXs, and browsing timeslots. This improves configuration and maintenance
efficiency.
Figure 3-10 shows the BTS topology view.

GBSS14.0
1. Area for selecting interface boards 4. Area for displaying cells and TRXs
2. Area for displaying operation buttons 5. Area for displaying information
3. Area for displaying the topology view 6. Area for searching, refreshing, and Help
1. Right-click a BSC or BTS in the Main View navigation tree, and choose Show BTS
Topology to open the BTS topology view.
2. View the information as required.
Operation Description
View the meaning of

In area 6, click . The icon description window is
each icon in the topology
displayed. You can click this button again to close the icon
view
description window.
View the description of

In area 6, click . The description window of the BTS
the BTS creation
creation procedure is displayed.
procedure

GBSS14.0
Switch to another Select the subrack number, slot number, and logical board
interface board of the BSC from area 1, switch to another interface board,
and view the BTS topology information under this interface
board.
Check physical l Lines connecting BSCs and BTSs indicate the physical
connections connections. If only one line exists, it indicates that only
the primary connection is configured. If two or more
lines exist, it indicates that secondary connections are
configured.
l Lines displayed on a BTS indicate the internal
connections between cabinets.
l The number on the left board indicates the slot number.
The string on the BTS indicates the BTS name.
l You can view the port numbers by clicking the ports at
both ends of a line.
View the connections of 1. Click the interface board icon on the BSC side. Area 5
the interface board displays the information about the interface board.
2. In this window, you can view the following information:
l Physical type and logical type of the board
l Total number of BTSs connected to the board
l Number of ports being used on the board and number
of each port
Add BTSs 1. Right-click the interface board in area 3, and choose Add
Site from the shortcut menu. The Add Site dialog box is
displayed.
2. In the displayed dialog box, set BTS attributes, and click
OK.
View basic BTS 1. Click a BTS icon. Area 5 displays the basic information
information about the BTS.
2. In this window, you can browse basic information such
as the index, name, and type of the BTS.
Add cells 1. Right-click the blank area in area 4, and choose Add
Cell from the shortcut menu. The Add Cell dialog box
is displayed.
2. In the displayed dialog box, set cell attributes, and click
OK.
View basic cell 1. Click a cell icon. Area 5 displays the basic information
information about the cell.
2. In this window, you can view the information such as the
cell ID, cell name, frequency band, mobile country code
(MCC), Mobile Network Code (MNC), location area
code (LAC), cell identity (CI), and BCCHNo.

GBSS14.0
View basic TRX Click a TRX icon. Area 5 displays the basic information
information about the TRX.
In this window, you can view the information such as the
TRX ID, TRX number, used frequency, subrack number,
slot number and channel number of the TRX board, and
board type.
Select a display mode of Right-click in the blank area, and select a display mode of
the message box the window as required:
l Hide Cell Panel: The message box is displayed in a fixed
way and can be dragged.
l Hide Bulletin: The message box is hidden.
Search for a cell or BTS

1. Click . The search dialog box is displayed.
2. Select the option of searching by name or ID, enter the
name or ID of the cell or BTS, and click OK. The
retrieved cell or BTS is highlighted.
View the activation status View the dots to the lower right of the BTS, cell, or TRX
of a BTS, cell, or TRX icon.
l If the dot is green, the BTS, cell, or TRX is activated.
l If the dot is gray, the BTS, cell, or TRX is not activated.
Refresh the GUI

In area 6, click .
3.11 Introduction to the Configuration Express for BTSs

express for BTSs.
The configuration express provides a window for configuring BTS-level objects, as shown in
Figure 3-11.

GBSS14.0
Figure 3-11 Configuration express for BTSs
1. In area 1, right-click a BTS to be configured in the Main View navigation tree, and choose
BTS Configuration Express from the shortcut menu. The express window for configuring
BTSs is displayed.
2. In area 2, select a BTS to be configured.
TIP
4. In area 4, configure the parameters.
3.12 Configuration Express for BTS IP Addresses

express for BTS IP addresses.
Portal of the Configuration Express for BTS IP Addresses

1. In area 1 in the Figure 3-12, right-click a BTS to be configured in the Main View navigation
tree, and then choose Show BTS Topology from the shortcut menu. The BTS topology
view is displayed, as shown in Figure 3-12.

GBSS14.0
2. In area 3 in the Figure 3-12, select an IP interface board, right-click a BTS in area 2, and
then choose Configure BTS IP Properties from the shortcut menu. The express window
for configuring BTS IP addresses is displayed, as shown in Figure 3-13.

GBSS14.0
Figure 3-13 Configuration express for BTS IP addresses
1. In area 1 in the Figure 3-13, select a BTS to be configured.
2. In area 2 in the Figure 3-13, select an object to be configured in the Properties navigation
tree. The configuration parameters of the object are displayed in area 3.
TIP
You can also type the configuration parameters on the tab pages Parameter List and Search in area
2. This helps to quickly locate parameters.
3. In area 3 of the Figure 3-13, configure the parameters.
3.13 Introduction to the GSM Device Panel

This section provides the introduction to the GSM device panel, including the structure and
configuration guidance to device panels for the BSC and the BTS and the RXU topology view.
BSC Device Panel

Right-click a BSC to be configured in the Main View navigation tree in the left pane, and choose
Device Panel from the shortcut menu. The BSC device panel is displayed, as shown in Figure
3-14.

GBSS14.0
Figure 3-14 Device panel
1. Cabinet device This area displays the structure between the cabinets, subrack, and boards.
panel You can delete cabinets, add or delete subracks and boards, or view or
modify device attributes in this area.
2. Operation You can add cabinets and cables between subracks in this area.
buttons
BTS Device Panel

The BTS device panel differs by BTS type. This section introduces the BTS device panel that
supports the BTS3900 in SRAN mode.
Right-click a BTS to be configured in the Main View navigation tree in the left pane, and choose
Device Panel from the shortcut menu. The BTS device panel is displayed, as shown in Figure
3-15.

GBSS14.0
Figure 3-15 BTS3900 device panel
1. Cabinet navigation You can add or delete cabinets, or view cabinet attributes in this area.
tree
2. RXU chain You can add or delete RXU chains and RXU boards, or view attributes
navigation tree in this area.
3. RXU topology You can switch over between the RXU topology view and the cabinet
view and cabinet tab tab page in this area.
page
4. Device panels of You can add or delete boards and cabinets, or view or modify device
cabinets, subracks, attributes in this area.
and boards
5. Operation buttons This area displays basic information about the current BTS, including
the BTS index, name, and type. You can also add cabinets in this area.
RXU Topology View

In area 3 of Figure 3-15, click the RXU Topology tab, as shown in Figure 3-16.

GBSS14.0
Figure 3-16 RXU topology view
The RXU topology view contains the following information:

l Cabinet number, subrack number, and slot number of the GBBP, GTMU, or UBRI board
l Chain head or ring head/tail location of an RXU chain/ring (port number of the GBBP/
GTMU/UBRI board)
l Cascaded location of the RXU in the RXU chain/ring
You can add or delete RXU boards and RXU chains, set breakpoints, or view device attributes
in this area.
3.14 Introduction to the Configuration Express for TRXs

express for TRXs.
The configuration express provides a window for configuring TRX-level objects, as shown in
Figure 3-17.

GBSS14.0
Figure 3-17 Configuration express for TRXs
1. In area 1, right-click a TRX in the Main View navigation tree, and choose TRX
Configuration Express from the shortcut menu. The express window for configuring
TRXs is displayed.
2. In area 2, select a TRX to be configured.
TIP
3.15 Introduction to the Configuration Express for GSM

Cells
express for GSM cells.
The configuration express provides a window for configuring cell-level objects, as shown in
Figure 3-18.

GBSS14.0
Figure 3-18 Configuration express for GSM cells
1. In area 1, right-click a GSM cell to be configured in the Main View navigation tree, and
choose UMTS Cell Configuration Express from the shortcut menu. The express window
for configuring GSM cells is displayed.
2. (Optional)In area 2, select a cell to be configured.
TIP
4. In area 4, configure the parameters.
3.16 Introduction to the Configuration Express for

Neighboring GSM Cells
express for neighboring GSM cells.
The configuration express provides a window for cell-level objects, as shown in Figure 3-19.

GBSS14.0
Figure 3-19 Configuration express for neighboring GSM cells
1. In the Main View navigation tree in area 1, right-click a GSM cell to be configured, and
choose UMTS Neighboring Cell Configuration Express from the shortcut menu. The
express window is displayed for you to configure GSM neighboring cells.
2. (Optional)Select a source cell in area 2.
3. Select the object to be configured in the Properties navigation tree in area 3.
4. Select the corresponding Template and NE in area 4. Select one or multiple required
neighboring cells, and click Add. The information about the neighboring cell is displayed
in area 5.
5. (Optional) Right-click the neighboring cell selected in area 5, and choose Modify NCell
Relationship from the shortcut menu to modify the information about the neighboring cell.
3.17 Modifying GBSC Parameters in Batches

This section describes how to change values of specified parameters for specified GBSCs in
batches.
Procedure
Step 1 In the configuration window, select a data record and click . The dialog box for selecting
objects is displayed.
Step 2 Select GBSCs to be modified in batches.

GBSS14.0
Step 3 Click Next. The dialog box for selecting parameters is displayed.
Step 4 Select parameters to be modified in batches.

NOTE
The dialog box displays only names and values of the parameters that can be changed in batches. You can
change parameter values as required.
The CME uses values of selected parameters as references to change parameter values of other specified
GBSCs in batches.
Step 5 Click Next. The CME starts batch modification. After modification, the CME displays the
results.
Step 6 Click Finish.
----End
3.18 Modifying GBTS Parameters in Batches

This section describes how to change values of specified parameters for specified GBTSs in
batches.
Procedure
Step 2 Click Add and select the mode for adding GBTSs based on site requirements. For details, see
Introduction to the Object Selection Modes.

NOTE
GBTSs in batches.
results.
----End
3.19 Deleting GSM Cells in Batches

This section describes how to delete GSM cells in batches.

GBSS14.0
Procedure
Step 1 Right click cell in the BTS topology, select Delete Cell.A dialog box is displayed for you to
delete cells in batches.
Step 2 Select the cells to be deleted.

1. Select Delete 2G external cells for GSM/UMTS.
If the cell to be deleted serves as the external or neighboring cell on other BSCs or RNCs,
select Delete 2G external cells for GSM/UMTS. The data about this cell is also deleted
from other BSCs or RNCs.
2. Click Add, and select the cells to be deleted.
The CME provides three modes for you to select cells. For detailed operations, see
Step 3 Click Next. In the displayed confirmation dialog box, click Yes. The CME starts to delete the
cells and displays the results after the deletion is complete.
Step 4 Click Finish to exit the wizard.

If the CME fails to delete any of the cells, all the cells and their neighbor relationships are restored
to the status before the deletion. A failure report is displayed. You can reconfigure the data based
on the failure cause and perform the deletion again.
----End
3.20 Modifying GSM Cell Parameters in Batches

This section describes how to change values of specified parameters for specified GSM cells in
batches.
Procedure
Step 2 Select cells to be modified in batches.
If you need to... Then...
Modify all cells under an NE in batches Select BY NE from the Select mode drop-down
list and select NEs in the NE list.
Modify specified cells under an NE in Select BY Cell from the Select mode drop-down
batches list, click Add, and select the mode for adding
cells based on site requirements. For details, see

GBSS14.0
NOTE
cells in batches.
results.
----End
3.21 Modifying BSC External Cell Parameters in Batches

This section describes how to change values of specified parameters for specified BSC external
cells in batches.
Procedure
Step 2 Select BSC external cells to be modified in batches.
Modify all BSC external cells under an Select BY NE from the Select mode drop-down
NE in batches list and select NEs in the NE list.
Modify specified BSC external cells The following uses GBSC 2G external cell as an
under an NE in batches example.
Select By BSC 2G External Cell from the
Select mode drop-down list, click Add, and
select the mode for adding BSC external cells
based on site requirements. For details, see
NOTE
To modify BSC 3G external cells or BSC LTE external
cells, select By BSC 3G External Cell or By BSC
LTE External Cell from the Select mode drop-down
list.

GBSS14.0
NOTE
BSC external cells in batches.
results.
----End
3.22 Modifying GSM TRX Parameters in Batches

This section describes how to change values of specified parameters for specified TRXs in
batches.
Procedure
Step 2 Select TRXs to be modified in batches.
Modify all TRXs under an NE in batches Select BY NE from the Select mode drop-down
list and select NEs in the NE list.
Modify specified TRXs under an NE in Select BY GSM TRX from the Select mode
batches drop-down list, click Add, and select the mode
for adding TRXs based on site requirements. For
details, see Introduction to the Object Selection
Modes.

NOTE
TRXs in batches.
results.
----End

GBSS14.0
3.23 Introduction to the Object Group Configuration

This section describes how to search for external cells in an object group and configure them.
Figure 3-20 shows the window for configuring external cells.
Figure 3-20 Window for configuring external cells
1. In area 1, select the BSC to be configured in the Main View navigation tree.
2. In area 2, select the external cell to be configured in the Object Group navigation tree.
TIP
In area 2, you can also type the parameters to be set on the Search tab page. This helps quickly locate
parameters.

GBSS14.0
Feature Activation Guide 4 Activating the GSM License
4 Activating the GSM License
This describes how to activate the GSM license.
Prerequisites
l The BSC6900 is in service.
l The LMT is started and you are logged in to the BSC6900.
l The valid BSC6900 license is obtained and stored in the OMU active workspace \FTP
\License
Procedure
Step 1 Run the BSC6900 MML command LST LICENSE and enter the name of the license file to be
activated to query the file information.
If... Then...
The file information comply with the information of the Go to Step 2.

file that you apply for,
The file information does not comply with the Exit the task and contact Huawei.
information of the file that you apply for,
Step 2 Run the BSC6900 MML command LST CFGMODE to query the subrack configuration status.
If the subrack is offline, Run the BSC6900 MML command SET CFGDATAEFFECTIVE to
switch it to online.
Step 3 Run the BSC6900 MML command ACT LICENSE to active the License.
----End

GBSS14.0
Feature Activation Guide 5 Configuring Multi-band Sharing One BSC
5 Configuring Multi-band Sharing One BSC
Multi-band Sharing One BSC.
Prerequisites
l Dependencies on Hardware
– This feature does not have any special requirements for hardware.
l Dependencies on Other Features
– You are advised to use this feature together with GBFD-111610 Dynamic Cell Power
Off to reduce the network power consumption.
l License
– This feature is not under license control.
l Other Prerequisites
– The TRXs configured for the BTS supports the corresponding frequency bands.
Context
l Huawei GSM BSS supports the following types of multiband networks:
– GSM850 band + GSM900 band + DCS1800 band
– GSM850 band + GSM900 band + PCS1900 band
l The most common combination is GSM900 with DCS1800 and GSM850 with PCS1900.
l Huawei GSM BSS does not support the co-existence of a GSM900/DCS1800 co-BCCH
cell and a GSM850/PCS1900 co-BCCH cell.
l Huawei GSM BSS supports GSM900 band, DCS1800 band, PCS1900 band, and GSM850
band. Huawei GSM BSS does not support GSM450 band or GSM480 band.
The dual-band network configured on the GSM900 and DCS1800 bands of a BTS is used as an
example.
Procedure
l Activation Procedure

GBSS14.0
1. Run the BSC6900 MML command ADD GCELL (CME single configuration: BTS
Topology > Right click BTS > ADD Cell; CME batch modification center: not
supported) to add a GSM cell. In this step, set Freq. Band Type to GSM900.
2. Run the BSC6900 MML command ACT GCELL (CME single configuration: Main
View > Right click GSM cell > Activate Cell; CME batch modification center: not
supported) to activate the cell.
3. Repeat Step 1 and Step 2 to set Freq. Band to DCS1800.
l Verification Procedure
1. Run the BSC6900 MML command SET GCELLHOBASIC to set the basic handover
parameters of the GSM900 and DCS1800 cells based on the network plan.
2. Use an MS supporting the GSM900 band to camp on a 900 MHz cell. Perform the
dialing test. The call is normal.
3. Use an MS supporting the DCS1800 band to camp on a 1800 MHz cell. Perform the
dialing test. The call is normal.
4. Use an MS supporting the GSM900 and DCS1800 bands to camp on a 900 MHz cell.
Perform the dialing test. After the call is set up, move the MS towards the center of
the 1800 MHz cell. Then, check the channel status in the monitoring window. The
MS is handed over to the 1800 MHz cell, and the call is kept alive.
NOTE
l On the LMT, click Device Maintenance. In the Device Navigation Tree, right-click a specified
cell, and then choose Monitor Channel Status.
l When a call is handed over to the 1800 MHz cell, the color of a channel in the Monitor Channel
Status window is displayed as green. This indicates that the channel is occupied by the call
handed to the 1800 MHz cell.
l Deactivation Procedure
1. Run the BSC6900 MML command DEA GCELL (CME single configuration: Main
View > Right click GSM cell > Deactivate Cell; CME batch modification center:
not supported). In this step, set Freq. Band to GSM900.
2. Run the BSC6900 MML command LST GCELL (CME single configuration: Cell
Configuration Express > Cell Attributes > GSM CELL) to query the value Active
status.
Expected result: The value of Active status is DEACTIVATED.
3. Repeat Step 1 and Step 2 to deactivate the cell whose Freq. Band is DCS1800.
----End
Example
//Activating Multi-band Sharing One BSC
//Adding a GSM cell

ADD GCELL: CELLID=0, CELLNAME="Cell0", TYPE=GSM900, MCC="460", MNC="10",
LAC=10, CI=11, NCC=0, BCC=0, IUOTP=Normal_cell, FLEXMAIO=OFF;
//Activating the GSM cell
ACT GCELL: IDTYPE=BYID, CELLID=0;
//Adding a DCS cell

ADD GCELL: CELLID=1, CELLNAME="Cell1", TYPE=DCS1800, MCC="460", MNC="10",
LAC=11, CI=12, NCC=0, BCC=0, IUOTP=Normal_cell, FLEXMAIO=OFF;
//Activating the DCS cell

GBSS14.0
//Verifying Multi-band Sharing One BSC

SET GCELLHOBASIC: IDTYPE=BYID, CELLID=0, HOCTRLSWITCH=HOALGORITHM2;
//Deactivating NSS-based LCS (cell ID + TA)
DEA GCELL: IDTYPE=BYID, CELLID=0;

GBSS14.0
Feature Activation Guide 6 Configuring Emergency Call Service (TS12)
6 Configuring Emergency Call Service (TS12)
Emergency Call Service (TS12).
Prerequisites
– This feature does not depend on other features.
l License
Context
The emergency call service takes precedence over other services during network access even if
the MS requesting the service is suspended or the telephone charge is overdue.
Procedure
1. Run the BSC6900 MML command SET GCELLCCBASIC (CME single
configuration: Cell Configuration Express > Call Control > Call Control Basic
Parameters of Cell; CME batch modification center: 3.20 Modifying GSM Cell
Parameters in Batches) to enable the emergency call service. In this step, set
Emergency Call Disable to NO(No).
1. Run the BSC6900 MML command LST GCELLCCBASIC to query whether the
emergency call service is enabled.
Expected result: The value of Emergency Call Disable is No.
2. Tracing Messages on the A Interface. On the Basic tab page, set DPC(HEX) to the
DPC of the cell and select the BSSAP check box. On the BSSAP tab page, set Cell
ID(cell1,cell2,...cell16) to the ID of the cell. Click Submit.
3. Use the MS to make an emergency call. After the call is put through, you can hear a
voice prompt.

GBSS14.0
Feature Activation Guide 6 Configuring Emergency Call Service (TS12)
4. Check the BSSAP messages traced on the A interface.

Expected result: An EMERGENCY_SETUP message is traced on the A interface.
This indicates that the emergency call service is enabled.
Parameters in Batches) to disable the emergency call service. In this step, set
Emergency Call Disable to YES(Yes).
----End
Example
//Activating Emergency Call Service (TS12)
SET GCELLCCBASIC: IDTYPE=BYID, CELLID=0, ERGCALLDIS=NO;
//Deactivating Emergency Call Service (TS12)

SET GCELLCCBASIC: IDTYPE=BYID, CELLID=0, ERGCALLDIS=YES;

GBSS14.0
Feature Activation Guide 7 Configuring IMSI Detach
7 Configuring IMSI Detach
IMSI Detach.
Prerequisites
l License
Context
After the IMSI is detached, the MS is marked as an invalid MS by the network. The network
does not send any paging message to this MS.
The network informs the MS whether the IMSI attach or detach is allowed by sending the system
information type 3 message.
Procedure
1. Run the BSC6900 MML command SET GCELLIDLEBASIC (CME single
configuration: Cell Configuration Express > Idle Mode > Idle Basic Parameters
of Cell; CME batch modification center: 3.20 Modifying GSM Cell Parameters in
Batches). In this step, set Attach-detach Allowed to YES(Yes).
1. Run the BSC6900 MML command LST GCELLIDLEBASIC to query the value of
Attach-detach Allowed.
Expected result: The value of Attach-detach Allowed is YES(Yes).
2. On the BSC6900 LMT, initiate A interface message tracing by referring to Tracing
Messages on the A Interface. On the Basic tab page, set DPC(HEX) to the DPC of
the cell and select the BSSAP check box. On the BSSAP tab page, set Cell ID
(cell1,cell2,...cell16) to the ID of the cell. Click Submit.

GBSS14.0
Feature Activation Guide 7 Configuring IMSI Detach
3. After the A interface message tracing window is displayed, power off the MS.
Expected result: The IMSI DETACH INDICATION message is traced on the A
interface.
Batches). In this step, set Attach-detach Allowed to NO(No).
----End
Example
//Activating IMSI Detach
SET GCELLIDLEBASIC: IDTYPE=BYID, CELLID=0, ATT=YES;
//Deactivating IMSI Detach

SET GCELLIDLEBASIC: IDTYPE=BYID, CELLID=0, ATT=NO;

GBSS14.0
Feature Activation Guide 8 Configuring HUAWEI I Handover
8 Configuring HUAWEI I Handover
HUAWEI I Handover.
Prerequisites
This feature does not depend on the hardware.
This feature does not depend on other features.
l License
This feature is not under license control.
Neighboring 2G cells have been configured. For details, see Configuring the Radio Data.
Context
Handover is used to keep the call continuity of the UE during its movement. It also helps optimize
the network performance by balancing the traffic between cells.
Huawei I handover is classified into high-speed railway quick handover, emergency handover,
enhanced dual-band network handover, load-based handover, and normal handover. The
emergency handover is classified into TA handover, bad quality (UL/DL) handover, quick level
drop handover, interference handover, and no downlink measurement report handover. The
normal handover is classified into edge handover, hierarchical handover, PBGT handover,
concentric cell handover, AMR handover, and better 3G cell handover.

GBSS14.0
CAUTION
l After quick handover, bad quality handover, and TA handover are successful, penalty is
applied on the old cell during the penalty time to prevent an immediate handover back to the
old cell.
l A bad quality handover is an intra- or inter-cell handover. If Bad Quality Handover
Optimization Allowed is set to YES(Yes), only an inter-cell bad quality handover can be
initiated.
l During TA handover, if the TA Threshold of a co-site neighboring cell is lower than or equal
to the TA Threshold of the serving cell, a handover to the cell is prohibited.
l An interference handover is an intra- or inter-cell handover. If Interference Handover
Optimization Allowed is set to YES(Yes), only an intra-cell interference handover can be
initiated. However, when intra-cell handover is triggered several times continuously, it will
be forbidden within a specified duration.
l On the enhanced dual-band network, the MS should not be handed over to a cell in the same
underlaid/overlaid cell group when the load-based handovers between the overlaid cell and
the underlaid cell (specified by Load HO From UL Subcell to OL Subcell Allowed and
Load HO of OL Subcell to UL Subcell Enabled) are allowed. This is to prevent a load-
based handover of a normal cell from colliding with a load-based handover between the
overlaid cell and the underlaid cell on the network.
l PBGT handover toward a cell of the same group is not allowed once it is triggered between
the enhanced dual-band network cells.
l After the fast-moving micro cell handover is successful, penalty is applied on all the
neighboring micro cells.
l SDCCH handover supports the quick handover, TA handover, bad quality handover, quick
level drop handover, interference handover, no downlink measurement report handover, edge
handover, and fast-moving micro cell handover. It does not support the enhanced dual-band
network handover, load-based handover, hierarchical handover, PBGT handover, AMR
handover, better 3G cell handover, concentric cell handover, and tight BCCH handover.
Procedure
1. Run the BSC6900 MML command SET GCELLHOBASIC (CME single
configuration: Cell Configuration Express > Handover Data > Basic Handover
Parameters in Batches). In this step, set Current HO Control Algorithm to
HOALGORITHM1(Handover algorithm I).
2. Run the BSC6900 MML command SET GCELLHOEMG (CME single
configuration: Cell Configuration Express > Handover Data > Emergency
Handover Parameters of Cell; CME batch modification center: 3.20 Modifying
GSM Cell Parameters in Batches). In this step, set Current HO Control
Algorithm to HOALGORITHM1(Handover algorithm I).
3. Run the BSC6900 MML command SET GCELLHOFITPEN (CME single
configuration: Cell Configuration Express > Handover Data > Filter/Penalty
Parameters of Cell Handover; CME batch modification center: 3.20 Modifying
Algorithm to HOALGORITHM1(Handover algorithm I).

GBSS14.0
4. Run the BSC6900 MML command SET GCELLHOIUO (CME single

configuration: Cell Configuration Express > Handover Data > Intelligent
Underlay Overlay (IUO) Handover Parameters of Cell; CME batch modification
center: 3.20 Modifying GSM Cell Parameters in Batches). In this step, set Current
HO Control Algorithm to HOALGORITHM1(Handover algorithm I).
5. Run the BSC6900 MML command SET GCELLHOAD (CME single configuration:
Cell Configuration Express > Handover Data > Advanced Handover Parameters
Batches). In this step, set Max. Num. of HO Attempts to an appropriate value.
6. Optional: Run the BSC6900 MML command SET GCELLCCCH (CME single
configuration: Cell Configuration Express > Idle Mode > Common Control
Channel Parameters of Cell; CME batch modification center: 3.20 Modifying GSM
Cell Parameters in Batches). In this step, set PWRC to YES(Yes). Run the BSC6900
MML commandSET GCELLOTHEXT (CME single configuration: Cell
Configuration Express > Other Attributes > Extended Parameters of Cell; CME
batch modification center: 3.20 Modifying GSM Cell Parameters in Batches). In
this step, set Power Control and Handover CMP CON Sw to YES(Yes). This helps
to improve the effect of handover and power control when the BCCH participates in
baseband frequency hopping.
7. Activating the quick handover algorithm
a. Run the BSC6900 MML command MOD G2GNCELL (CME single
configuration: Cell Configuration Express > Neighboring Cell > BSC 2G
Neighbor Cell; CME batch modification center: not supported). In this step, set
Index Type (Not required on the CME), Source Cell Index, Neighbor 2G Cell
Index, and Chain Neighbor Cell Type to appropriate values; then, set Chain
Neighbor Cell to YES(Yes), and set Quick Handover Offset and Neighboring
Cell Type to appropriate values.
b. Run the BSC6900 MML command SET GCELLHOBASIC (CME single
configuration: Cell Configuration Express > Handover Data > Basic
Handover Parameters of Cell; CME batch modification center: 3.20
Modifying GSM Cell Parameters in Batches). In this step, set Quick
Handover Enable to YES(Yes), and set Quick PBGT Handover Enable to
YES(Yes) if quick PBGT handovers are needed.
NOTE
The quick handover algorithm consists of the frequency offset handover algorithm and
quick PBGT handover algorithm. Quick Handover Enable controls whether to initiate
frequency offset and quick PBGT handovers. Quick PBGT Handover Enable controls
whether to initiate quick PBGT handovers only.
c. Run the BSC6900 MML command SET GCELLHOFAST (CME single
configuration: Cell Configuration Express > Handover Data > Fast
Modifying GSM Cell Parameters in Batches). In this step, set Handover
Direction Forecast Enable to YES(Yes), and set Quick Handover Up Trigger
Level, Quick Handover Down Trigger Level, Quick Move Speed
Threshold, Serving Cell Filter Length MR Number, Neighbor Cell Filter
Length MR Number, Ignore Measurement Report Number, Quick
Handover Punish Time, Quick Handover Punish Value, Quick Handover
Offset, Handover Direction Forecast Statistic Times, Handover Direction
Forecast Last Times, Frequency Shift Handover Statistic Time and
Frequency Shift Handover Duration to appropriate values.

GBSS14.0
NOTE
If the neighboring cell is an external neighboring cell, run the MOD GEXT2GCELL
(CME single configuration: Object Group > GSM Service Configuration and
Maintenance Management > External Cell Configuration > BSC 2G External
Cell; CME batch modification center: 3.21 Modifying BSC External Cell Parameters
in Batches) command. In this step, set Quick Handover Offset, Quick Handover
Punish Time, and Quick Handover Punish Value to appropriate values.
d. Optional: Run the BSC6900 MML commandSET GCELLOTHEXT (CME
single configuration: Cell Configuration Express > Other Attributes >
Extended Parameters of Cell; CME batch modification center: 3.20 Modifying
GSM Cell Parameters in Batches). In this step, set UL Frequency Adjust
Switch, DL Frequency Adjust Switch, and UL Frequency Adjust Value
according to the frequency offset information reported by the base station.
8. Activating the TA handover algorithm
a. Run the BSC6900 MML command SET GCELLHOBASIC (CME single
Modifying GSM Cell Parameters in Batches). In this step, set TA HO
Allowed to YES(Yes).
b. Run the BSC6900 MML command SET GCELLHOEMG (CME single
Modifying GSM Cell Parameters in Batches). In this step, set TA
Threshold to an appropriate value.
c. Run the BSC6900 MML command SET GCELLHOFITPEN (CME single
Parameters of Cell Handover; CME batch modification center: 3.20
Modifying GSM Cell Parameters in Batches). In this step, set Penalty Level
after TA HO and Penalty Time after TA HO to appropriate values.
9. Activating the bad quality handover algorithm
Modifying GSM Cell Parameters in Batches). In this step, set BQ HO
b. Optional: For non-AMR calls, run the SET GCELLHOEMG (CME single
Modifying GSM Cell Parameters in Batches) command. In this step, set DL
Qual. Threshold and UL Qual. Threshold to appropriate values.
c. Optional: For AMR FR calls or AMR HR calls, run the SET
GCELLAMRQUL (CME single configuration: Cell Configuration Express >
Call Control > AMR Quality Threshold Parameters of Cell; CME batch
modification center: 3.20 Modifying GSM Cell Parameters in Batches)
command. In this step, set UULQUALIMITAMRFR, DL Qual. Limit for
AMR FR, UL Qual. Limit for AMR HR, and DL Qual. Limit for AMR
HR to appropriate values.
d. Run the BSC6900 MML command SET GCELLHOFITPEN (CME single

GBSS14.0
Modifying GSM Cell Parameters in Batches). In this step, set Penalty Level
after BQ HO and Penalty Time after BQ HO to appropriate values.
10. Activating rapid level drop handover algorithm
Modifying GSM Cell Parameters in Batches). In this step, set Rx_Level_Drop
HO Allowed to YES(Yes) and Edge HO UL RX_LEV Threshold to an
appropriate value.
Modifying GSM Cell Parameters in Batches). In this step, set Filter
Parameter A1, Filter Parameter A2, Filter Parameter A3, Filter Parameter
A4, Filter Parameter A5, Filter Parameter A6, Filter Parameter A7, Filter
Parameter A8 and Filter Parameter B to appropriate values.
11. Activating the interference handover algorithm
Modifying GSM Cell Parameters in Batches). In this step, set Interference
HO Allowed to YES(Yes), and set Intracell HO Allowed and Inter-layer HO
Threshold to appropriate values.
NOTE
If this cell has external neighboring cells, run the MOD GEXT2GCELL (CME single
configuration: Object Group > GSM Service Configuration and Maintenance
Management > External Cell Configuration > BSC 2G External Cell; CME batch
modification center: 3.21 Modifying BSC External Cell Parameters in Batches)
command. In this step, set Inter-layer HO Threshold to an appropriate value.
b. Run the BSC6900 MML command SET GCELLHOAD (CME single
configuration: Cell Configuration Express > Handover Data > Advanced
Modifying GSM Cell Parameters in Batches). In this step, set Forbidden time
after MAX Times to an appropriate value.
c. Run the BSC6900 MML command MOD G2GNCELL (CME single
Adjacent Cell Inter-layer HO Hysteresis to an appropriate value.
d. Run the BSC6900 MML command SET GCELLAMRQUL (CME single
configuration: Cell Configuration Express > Call Control > AMR Quality
Threshold Parameters of Cell; CME batch modification center: 3.20
Modifying GSM Cell Parameters in Batches). In this step, set Interfere HO
Qual. Thresh 1 for Non-AMR FR, Interfere HO Qual. Thresh 2 for Non-
AMR FR, Interfere HO Qual. Thresh 3 for Non-AMR FR, Interfere HO

GBSS14.0
AMR FR, Interfere HO Qual. Thresh 12 for Non-AMR FR and Interfere

HO Qual. Thresh Offset for AMR FR to appropriate values.
12. Activating the no downlink measurement report handover algorithm
a. Run the BSC6900 MML command SET GCELLHOEMG (CME single
Modifying GSM Cell Parameters in Batches). In this step, set No Dl Mr.HO
Allowed to YES(Yes), and set No Dl Mr.Ul Qual HO Limit, Cons.No Dl
Mr.HO Allowed Limit, No Dl Mr. HO Statistic Time, and No Dl Mr. HO
Last Time to appropriate values.
b. Run the BSC6900 MML command SET GCELLHOFITPEN (CME single
Modifying GSM Cell Parameters in Batches). In this step, set Filter Length
for TCH Qual and Filter Length for SDCCH Qual to appropriate values.
13. Activating the enhanced dual-band network handover algorithm
a. Run the BSC6900 MML command MOD GCELL (CME single configuration:
Cell Configuration Express > Cell Attributes > GSM CELL; CME batch
modification center: 3.20 Modifying GSM Cell Parameters in Batches). In this
step, set Cell IUO Type to EDB_cell(Enhanced Double Frequency Cell), set
Cell Inner/Extra Property and Same Group Cell Index Type (Not required
on the CME) to appropriate values, and set Same Group Cell Name or Same
Group Cell Index based on the value of Same Group Cell Index Type (Not
required on the CME).
b. Run the BSC6900 MML command SET GCELLHOEDBPARA (CME single
configuration: Cell Configuration Express > Handover Data > Enhanced
Dual-Band Handover Parameters of Cell; CME batch modification center:
3.20 Modifying GSM Cell Parameters in Batches). In this step, set Load HO
Allowed, UL Subcell General Overload Threshold, Inner Cell Serious
OverLoad Thred, Subcell HO Allowed Flow Control Level, Incoming OL
Subcell HO Level TH, Step Length of UL Subcell Load HO, UL Subcell
Load Hierarchical HO Periods, MOD Step LEN of UL Load HO Period,
Step Length of UL Subcell Load HO, UL Subcell Lower Load Threshold,
Subcell HO Allowed Flow Control Level, Outgoing OL Subcell HO Level
TH, OL Subcell Load Diversity HO Period, Step Length of OL Subcell Load
HO, Distance Between Boundaries of Subcells and Distance Hysteresis
Between Boundaries to appropriate values.
14. Activating the load-based handover algorithm
Modifying GSM Cell Parameters in Batches). In this step, set Load Handover
Support to YES(Yes) and Edge HO DL RX_LEV Threshold and Inter-layer
HO Threshold to appropriate values.
b. Run the BSC6900 MML command SET GCELLHOAD (CME single
Modifying GSM Cell Parameters in Batches). In this step, set System Flux
Threshold for Load HO, Load HO Threshold, Load handover Load Accept

GBSS14.0
Threshold, Load HO Bandwidth, Load HO Step Period, and Load HO Step

Level to appropriate values.
NOTE
If this cell has external neighboring GSM cells, run the MOD GEXT2GCELL (CME
single configuration: Object Group > GSM Service Configuration and Maintenance
command. In this step, set Load handover Load Accept Threshold to an appropriate
value. If this cell has external neighboring UMTS cells, run the MOD
GEXT3GCELL (CME single configuration: Object Group > GSM Service
Configuration and Maintenance Management > External Cell Configuration > BSC
3G External Cell; CME batch modification center: 3.21 Modifying BSC External Cell
Parameters in Batches) command. In this step, set Load handover Load Accept
15. Activating the edge handover algorithm
Modifying GSM Cell Parameters in Batches). In this step, set Edge HO
Allowed to YES(Yes), and set Edge HO UL RX_LEV Threshold, Edge HO
DL RX_LEV Threshold, Handover Algorithm I Edge HO Watch Time, and
Handover Algorithm I Edge HO Valid Time to appropriate values.
b. Run the BSC6900 MML command MOD G2GNCELL (CME single
16. Activating the fast-moving micro cell handover algorithm
a. Run the BSC6900 MML command SET GCELLBASICPARA (CME single
configuration: Cell Configuration Express > Cell Attributes > Basic
Parameters in Batches). In this step, set Layer of the Cell to an appropriate
value.
Modifying GSM Cell Parameters in Batches). In this step, set MS Fast
Moving HO Allowed to YES(Yes) and Inter-layer HO Threshold to an
appropriate value.
c. Run the BSC6900 MML command SET GCELLHOAD (CME single
Modifying GSM Cell Parameters in Batches). In this step, set MS Fast-
moving Watch Cells, MS Fast-moving Valid Cells, MS Fast-moving Time
Threshold, Penalty on MS Fast Moving HO, and Penalty Time on Fast
Moving HO to appropriate values.

GBSS14.0
NOTE
If this cell has external neighboring GSM cells, run the Run the BSC6900 MML
commandMOD GEXT2GCELL (CME single configuration: Object Group > GSM
Service Configuration and Maintenance Management > External Cell
Configuration > BSC 2G External Cell; CME batch modification center: 3.21
Modifying BSC External Cell Parameters in Batches) command. In this step, set
Layer of the Cell, Inter-layer HO Threshold, Penalty Time on Fast Moving HO, and
Penalty on Fast Moving HO to appropriate values.
d. Run the BSC6900 MML command MOD G2GNCELL (CME single
17. Activating the inter-layer handover algorithm
Modifying GSM Cell Parameters in Batches). In this step, set Level HO
Allowed to YES(Yes) and set Inter-layer HO Threshold to an appropriate
value.
b. Run the BSC6900 MML command SET GCELLBASICPARA (CME single
Parameters in Batches). In this step, set Layer of the Cell and Cell Priority to
appropriate values.
NOTE
command. In this step, set Layer of the Cell and Cell Priority to appropriate values.
Adjacent Cell Inter-layer HO Hysteresis, Layer HO Watch Time, and Layer
HO Valid Time to appropriate values.
18. Activating the PBGT handover algorithm
Modifying GSM Cell Parameters in Batches). In this step, set PBGT HO
b. Run the BSC6900 MML command SET GCELLBASICPARA (CME single
Parameters in Batches). In this step, set Layer of the Cell and Cell Priority to
appropriate values.

GBSS14.0
NOTE
command. In this step, set Layer of the Cell and Cell Priority to appropriate values.
Current HO CTRL Algorithm in Source Cell to HOALGORITHM1
(Handover algorithm I), and set Neighboring Cell Type, Adjacent Cell Inter-
layer HO Hysteresis, PBGT Watch Time, and PBGT Valid Time to
appropriate values.
19. Activating the AMR handover algorithm
Modifying GSM Cell Parameters in Batches). In this step, set Intracell F-H
HO Allowed to YES(Yes), and set Intracell F-H HO Stat Time, Intracell F-
H HO Last Time, F2H HO Threshold, and H2F HO Threshold to appropriate
values.
b. Run the BSC6900 MML command SET GTRXDEV (CME single
configuration: TRX Configuration Express > Site TRX Dev Property > Site
TRX Dev Property; CME batch modification center: 3.22 Modifying GSM
TRX Parameters in Batches). In this step, set TCH Rate Adjust Allow to YES
(Yes).
c. Run the BSC6900 MML command SET GCELLCCACCESS (CME single
configuration: Cell Configuration Express > Call Control > Call Access
Control Parameters of Cell; CME batch modification center: 3.20 Modifying
GSM Cell Parameters in Batches). In this step, set Speech Version to at least
FULL_RATE_VER3 and HALF_RATE_VER3.
d. Run the BSC6900 MML command SET BSCBASIC (CME single
configuration: GSM Global Configuration Express > BSC Basic
Configuration > Basic Attributes of BSC; CME batch modification center:
3.17 Modifying GBSC Parameters in Batches). In this step, set A Interface
Tag to GSM_PHASE_2Plus.
e. Run the BSC6900 MML command SET GCELLCHMGAD (CME single
configuration: Cell Configuration Express > Channel Management >
Advanced Channel Management Parameters of Cell; CME batch
step, set AMR TCH/H Prior Allowed and AMR TCH/H Prior Cell Load
20. Activating the capacity- and quality-based TCHF-TCHH handover algorithm
Modifying GSM Cell Parameters in Batches). In this step, set Intracell F-H
HO Allowed to HOBASECAPANDQUAL(HOBASECAPANDQUAL),
AMR F-H Ho Allowed to YES(Yes), and Non-AMR F-H Ho Allowed to YES
(Yes). Set the following parameters to appropriate values: Non-AMR F-H

GBSS14.0
Traffic Threshold F-H Ho Duration F-H Ho Period AMR F-H Ho Pathloss

Adjust Step AMR F-H Ho ATCB Adjust Step AMR F-H Ho Pathloss
Threshold F-H Pathloss Offset Overlay AMR F-H Ho ATCB Threshold F-
H ATCB Offset Overlay AMR F-H Ho Qual. Threshold F-H Ho Stat.
Time F-H Ho Last Time AMR H-F Traffic Threshold H-F Ho Duration
AMR H-F Ho ATCB Threshold H-F ATCB Offset Overlay Non-AMR H-F
Ho Pathloss Threshold H-F Pathloss Offset Overlay Non-AMR H-F Ho
Qual. Threshold H-F Ho Stat. Time H-F Ho Last Time Non-AMR F-H
Traffic Threshold Non-AMR F-H Ho Pathloss Adjust Step Non-AMR F-H
Ho ATCB Adjust Step Non-AMR F-H Ho Pathloss Threshold Non-AMR F-
H Ho ATCB Threshold Non-AMR F-H Ho Qual. Threshold Non-AMR H-
F Traffic Threshold Non-AMR H-F Ho ATCB Threshold Non-AMR H-F
Ho Pathloss Threshold Non-AMR H-F Ho Qual. Threshold
(Yes).
GSM Cell Parameters in Batches). In this step, set Speech Version to
FULL_RATE_VER3(Full-rate VER 3) and HALF_RATE_VER3(Half-rate
VER 3).
21. Activating the SDCCH handover algorithm
Modifying GSM Cell Parameters in Batches). In this step, set SDCCH HO
b. Run the BSC6900 MML command SET GCELLHOCTRL (CME single
configuration: Cell Configuration Express > Handover Data > Handover
GSM Cell Parameters in Batches) In this step, set Inter-BSC SDCCH HO
ALLowed to an appropriate value.
1. Run the BSC6900 MML command LST GCELLHOBASIC. In this step, query the
setting of Current HO Control Algorithm.
Expected result: The value of Current HO Control Algorithm is
2. Start the BSSAP message tracing task by referring to Tracing Messages on the A
Interface.
Expected result: The BSC sends the MSC a Handover Performed message with the
handover cause value of better-cell, distance, uplink-quality, downlink-quality,
traffic, uplink-strength, or downlink-strength.

GBSS14.0
– In the case of the quick handover, the handover cause value is better-cell.
– In the case of the TA handover, the handover cause value is distance.
– In the case of the BQ handover, the handover cause value is uplink-quality or
downlink-quality.
– In the case of the rapid level drop handover algorithm, the handover cause value
is uplink-strength.
– In the case of the interference handover, the handover cause value is uplink-
quality or downlink-quality.
– In the case of the no downlink measurement report handover, the handover cause
value is uplink-quality.
– In the case of the enhanced dual-band network handover, the handover cause value
is better-cell or traffic.
– In the case of the load-based handover, the handover cause value is traffic.
– In the case of the edge handover, the handover cause value is uplink-strength or
downlink-strength.
– In the case of the fast-moving micro cell handover, the handover cause value is
better-cell.
– In the case of the inter-layer handover, the handover cause value is better-cell.
– In the case of the PBGT handover, the handover cause value is better-cell.
– In the case of the AMR handover or the capacity- and quality-based TCHF-TCHH
handover, the handover cause value is downlink-quality.
– In the case of the SDCCH handover, the handover cause value is better-cell,
distance, uplink-quality, downlink-quality, traffic, uplink-strength, or
downlink-strength.
This feature does not need to be deactivated.
----End
Example
//Activating HUAWEI I handover algorithm
SET GCELLHOEMG: IDTYPE=BYID, CELLID=0, HOCTRLSWITCH=HOALGORITHM1;
SET GCELLHOFITPEN: IDTYPE=BYID, CELLID=0, HOCTRLSWITCH=HOALGORITHM1;
SET GCELLHOIUO: IDTYPE=BYID, CELLID=0, HOCTRLSWITCH=HOALGORITHM1;
SET GCELLHOAD: IDTYPE=BYID, CELLID=0, HOTRYCNT=3;
//Activating the quick handover algorithm
MOD G2GNCELL: IDTYPE=BYID, SRC2GNCELLID=0, NBR2GNCELLID=1,
NCELLTYPE=HANDOVERNCELL, ISCHAINNCELL=YES,
CHAINNCELLTYPE=QUICK_HO_NCELL_TYPE_A, ADJHOOFFSET=1;
SET GCELLHOBASIC: IDTYPE=BYID, CELLID=0, HOCTRLSWITCH=HOALGORITHM1,
QUICKHOEN=YES, QUICKPBGTHOEN=YES;
SET GCELLHOFAST: IDTYPE=BYID, CELLID=0, HOUPTRIGE=50, HODOWNTRIGE=50,
MOVESPEEDTHRES=35, SCELLFILTER=4, NCELLFILTER=4, IGNOREMRNUM=1,
TIMEPUNISH=10, HOPUNISHVALUE=63, HOOFFSET=68, MSLEVSTRQPBGT=NO,
HODIRFORECASTEN=YES, HODIRSTATIME=3, HODIRLASTTIME=2, AFCHOSTATTIME=4,
AFCHOLASTTIME=3;
SET GCELLOTHEXT: IDTYPE=BYID, CELLID=0, FREQADJ=YES, DLFREQADJ=YES,
FREQADJVALUE=36671;
//Activating the TA handover algorithm

GBSS14.0
TAHOEN=YES;
SET GCELLHOEMG: IDTYPE=BYID, CELLID=0, HOCTRLSWITCH=HOALGORITHM1,
TALIMIT=125;
SET GCELLHOFITPEN: IDTYPE=BYID, CELLID=0, HOCTRLSWITCH=HOALGORITHM1,
SSTAPUNISH=40, TIMETAPUNISH=10;
//Activating the bad quality handover algorithm
BQHOEN=YES;
DLQUALIMIT=55, ULQUALIMIT=60;
SSBQPUNISH=63, TIMEBQPUNISH=10;
//Activating rapid level drop handover algorithm
RXQCKFALLHOEN=YES, ULEDGETHRES=10;
FLTPARAA1=10, FLTPARAA2=10, FLTPARAA3=10, FLTPARAA4=10, FLTPARAA5=10,
FLTPARAA6=10, FLTPARAA7=10, FLTPARAA8=10, FLTPARAB=0;
//Activating the interference handover algorithm
INTRACELLHOEN=YES, INTERFHOEN=YES, HOTHRES=2;
SET GCELLHOAD: IDTYPE=BYID, CELLID=0, BANTIME=20;
NCELLTYPE=HANDOVERNCELL, INTELEVHOHYST=67;
SET GCELLAMRQUL: IDTYPE=BYID, CELLID=0, RXQUAL1=70, RXQUAL2=60,
RXQUAL3=59, RXQUAL4=58, RXQUAL5=57, RXQUAL6=56, RXQUAL7=55, RXQUAL8=54,
RXQUAL9=53, RXQUAL10=52, RXQUAL11=51, RXQUAL12=50;
//Activating the no downlink measurement report handover algorithm
NODLMRHOEN=YES, NODLMRHOQUALLIMIT=50, NODLMRHOALLOWLIMIT=8,
NODLMRHOSTATTIME=1, NODLMRHOLASTTIME=1;
DATAQUAFLTLEN=4, SIGQUAFLTLEN=2;
//Activating the enhanced dual-band network handover algorithm
MOD GCELL: IDTYPE=BYID, CELLID=0, IUOTP=EDB_cell, CELLINEXTP=Inner,
DBLFREQADJIDTYPE=BYID, DBLFREQADJCID=1;
SET GCELLHOEDBPARA: IDTYPE=BYID, CELLID=0, OUTASSOPTEN=YES;
//Activating the load-based handover algorithm
LoadHoEn=YES, DLEDGETHRES=20, HOTHRES=25;
SET GCELLHOAD: IDTYPE=BYID, CELLID=0, SYSFLOWLEV=10, TRIGTHRES=90,
LoadAccThres=80, LOADOFFSET=25, LOADHOPERIOD=10, LOADHOSTEP=5;
//Activating the edge handover algorithm
FRINGEHOEN=YES, ULEDGETHRES=10, DLEDGETHRES=20, EDGESTAT1=6, EDGELAST1=4;
//Activating the fast-moving micro cell handover algorithm
SET GCELLBASICPARA: IDTYPE=BYID, CELLID=0, LAYER=3;
QCKMVHOEN=YES, HOTHRES=25;
SET GCELLHOAD: IDTYPE=BYID, CELLID=0, QCKSTATCNT=3, QCKTRUECNT=2,
QCKTIMETH=15, SPEEDPUNISH=30, SPEEDPUNISHT=4;
//Activating the inter-layer handover algorithm
LEVHOEN=YES, HOTHRES=25;
SET GCELLBASICPARA: IDTYPE=BYID, CELLID=0, LAYER=3, PRIOR=PRIOR-3;

GBSS14.0

NCELLTYPE=HANDOVERNCELL, INTELEVHOHYST=67, LEVSTAT=6, LEVLAST=4;
//Activating the PBGT handover algorithm
PBGTHOEN=YES;
SET GCELLBASICPARA: IDTYPE=BYID, CELLID=0, LAYER=3, PRIOR=PRIOR-3;
NCELLTYPE=HANDOVERNCELL, INTELEVHOHYST=67, PBGTSTAT=6, PBGTLAST=4;
NCELLTYPE=HANDOVERNCELL, SRCHOCTRLSWITCH=HOALGORITHM1, PBGTMARGIN=68,
PBGTSTAT=6, PBGTLAST=4;
//Activating the AMR handover algorithm
INTRACELLFHHOEN=YES, INFHHOSTAT=10, INFHHOLAST=8, INHOF2HTH=25,
INHOH2FTH=12;
SET GTRXDEV: TRXID=0, TCHAJFLAG=YES;
SET GCELLCCACCESS: IDTYPE=BYID, CELLID=0,
VOICEVER=FULL_RATE_VER1-1&FULL_RATE_VER2-0&FULL_RATE_VER3-1&HALF_RATE_VER
1-1&HALF_RATE_VER2-0&HALF_RATE_VER3-1&FULL_RATE_VER5-0;
SET BSCBASIC: AVer=GSM_PHASE_2Plus, UmVer=GSM_PHASE_2Plus,
AbisVer=GSM_PHASE_2Plus;
SET GCELLCHMGAD: IDTYPE=BYID, CELLID=0, AMRTCHHPRIORALLOW=ON,
AMRTCHHPRIORLOAD=55;
//Activating the capacity- and quality-based TCHF-TCHH handover algorithm
SET GCELLHOBASIC: IDTYPE=BYID, CELLID=0, HOCTRLSWITCH= HOALGORITHM1,
INTRACELLFHHOEN=HOBASECAPANDQUAL, AMRFULLTOHALFHOALLOW=YES,
AMRFULLTOHALFHOTHRESH=75, FULLTOHALFHODURATION=5, FULLTOHALFHOPERIOD=1,
AMRFULLTOHALFHOPATHADJSTEP=1, AMRFULLTOHALFHOATCBADJSTEP=2,
AMRFULLTOHALFHOPATHTHRESH=100, FULLTOHALFHOPATHOFFSET=10,
AMRFULLTOHALFHOATCBTHRESH=20, FULLTOHALFHOATCBOFFSET=20,
AMRFULLTOHALFHOQUALTHRESH=0, FULLTOHALFHOSTATTIME=6,
FULLTOHALFHOLASTTIME=4, AMRHALFTOFULLHOTHRESH=45,
AMRHALFTOFULLHOQUALALLOW=YES, HALFTOFULLHODURATION=5,
AMRHALFTOFULLHOATCBTHRESH=4, HALFTOFULLATCBOFFSET=20,
AMRHALFTOFULLHOPATHTHRESH=108, HALFTOFULLHOPATHOFFSET=10,
AMRHALFTOFULLHOQUALTHRESH=3, HALFTOFULLHOSTATTIME=6,
HALFTOFULLHOLASTTIME=4, NOAMRFULLTOHALFHOALLOW=YES,
NOAMRFULLTOHALFTHRESH=85, NOAMRFULLTOHALFHOPATHADJSTEP=1,
NOAMRFULLTOHALFHOATCBADJSTEP=2, NOAMRFULLTOHALFHOPATHTHRESH=95,
NOAMRFULLTOHALFHOATCBTHRESH=30, NOAMRFULLTOHALFHOQUALTHRESH=0,
NOAMRHALFTOFULLTHRESH=25, NOAMRHALFTOFULLHOQUALALLOW=YES,
NOAMRHALFTOFULLHOATCBTHRESH=14, NOAMRHALFTOFULLHOPATHTHRESH=103,
NOAMRHALFTOFULLHOQUALTHRESH=2;
SET BSCBASIC: AVer=GSM_PHASE_2;
//Activating the SDCCH handover algorithm
SET GCELLHOBASIC: IDTYPE=BYID, CELLID=0, HOCTRLSWITCH= HOALGORITHM1,
SIGCHANHOEN=YES;
SET GCELLHOCTRL: IDTYPE=BYID, CELLID=0, INRBSCSDHOEN=YES;

GBSS14.0
Feature Activation Guide 9 Configuring Directed Retry
Directed Retry.
Prerequisites
l License
– This feature is not controlled by a license.
Context
Directed retry is a special type of handover. That is, during assignment, the BSC initiates the
directed retry procedure to switch the MS to a neighboring cell if no TCH is available or the
traffic load is heavy in the serving cell. The BSC does not initiate the directed retry procedure
during high speed circuit switched data (HSCSD) assignment.
This feature helps reduce call access failures due to TCH congestion in the serving cell,
increasing the access success rate. It also helps evenly distribute traffic load between cells.
Procedure
1. Run the BSC6900 MML commandSET GCELLBASICPARA (CME single
configuration: Cell Configuration Express > Cell Attributes > Basic Parameters
Batches). In this step, set Directed Retry to YES(Yes).
2. (Optional) Run the BSC6900 MML commandSET GCELLCCBASIC (CME single
Parameters in Batches) to enable directed retry based on the actual load in a cell. In
this step, set Assignment Cell Load Judge Enable to ENABLE(Enable).
3. (Optional) Run the BSC6900 MML commandSET GCELLOTHEXT (CME single
configuration: Cell Configuration Express > Other Attributes > Extended

GBSS14.0
Parameters in Batches) to enable directed retry based on the actual load in a cell. In
this step, set Cell Directed Retry Forbidden Threshold to an appropriate value based
on the actual load in the serving cell.
4. Run the BSC6900 MML commandSET GCELLCCBASIC (CME single
Parameters in Batches) if Huawei I Handover algorithm is used. In this step, set
Directed Retry Load Access Threshold to an appropriate value based on the actual
load in candidate neighboring cells. Run the BSC6900 MML commandSET
GCELLHOAD (CME single configuration: Cell Configuration Express >
Handover Data > Advanced Handover Parameters of Cell; CME batch
modification center: 3.20 Modifying GSM Cell Parameters in Batches) if Huawei
II Handover algorithm is used. In this step, set Load handover Load Accept
Threshold to an appropriate value based on the actual load in candidate neighboring
cells.
5. Run the BSC6900 MML commandSET GCELLHOBASIC (CME single
HOALGORITHM1(Handover algorithm I). Run the BSC6900 MML
commandSET GCELLHOCTRL (CME single configuration: Cell Configuration
Express > Handover Data > Handover Control Parameters of Cell; CME batch
modification center: 3.20 Modifying GSM Cell Parameters in Batches). In this step,
set Min Power Level For Directed Retry to an appropriate value based on the actual
receive level in neighboring cells. Run the BSC6900 MML commandADD
G2GNCELL (CME single configuration: Cell Configuration Express >
Neighboring Cell > BSC 2G Neighbor Cell; CME batch modification center: not
supported) if Current HO Control Algorithm is set to HOALGORITHM2
(Handover algorithm II). In this step, set Inter-cell HO Hysteresis and Directed
Retry Handover Level Range to appropriate values based on the actual receive level
in neighboring cells.
6. Optional: Set the number of cells for directed retry and the priorities of these cells.
a. Run the BSC6900 MML commandSET GCELLOTHEXT (CME single
Parameters in Batches). In this step, set DRD HO Target Cell Selection
Optimized to YES(Yes).
b. Run the BSC6900 MML commandSET GCELLHOAD (CME single
Modifying GSM Cell Parameters in Batches). In this step, set Max. Num. of
HO Attempts to an appropriate value.
NOTE
The following configurations are only used for verification. For commercially used networks, configure
parameters based on the network plan. After this feature is verified, restore the configurations before
verification.
1. Block all TCHs in cell 0. Meanwhile, ensure that SDCCHs in cell 0 are available for
use.

GBSS14.0
2. Trace the BSSAP messages on the A interface and the RSL messages on the Abis
interface in cells 0 and 1 by referring to Tracing Messages on the A Interface and
Tracing CS Domain Messages on the Abis Interface.
3. Use an MS to make a call in cell 0.
4. View the BSSAP messages traced over the A interface and RSL messages traced over
the Abis interface in cells 0 and 1.
Expected result: Calls are established successfully and the speech quality is good. The
Handover Detection message is traced over the Abis interface in cell 1. The
Assignment Complete message is traced over the A interface in cell 1.
5. Open the Single User CS Trace page. It indicates that the value of the ucHoCause
information element (IE) in the Handover Triggered Indication message is directed-
retry.
1. Run the BSC6900 MML commandSET GCELLBASICPARA (CME single
Batches). In this step, set Directed Retry to NO(No).
----End
Example
//Activating Directed Retry
SET GCELLBASICPARA: IDTYPE=BYID, CELLID=0, DIRECTRYEN=YES;
SET GCELLOTHEXT: IDTYPE=BYID, CELLID=0, DRTAGCELLSEL=YES;
SET GCELLCCBASIC: IDTYPE=BYID, CELLID=0, DTLOADTHRED=85;
SET GCELLHOCTRL: IDTYPE=BYID, CELLID=0, MINPWRLEVDIRTRY=16;
ADD G2GNCELL: IDTYPE=BYID, SRC2GNCELLID=0, INTERCELLHYST=68,
DRHOLEVRANGE=72;
//Deactivating Directed Retry
SET GCELLBASICPARA: IDTYPE=BYID, CELLID=0, DIRECTRYEN=NO;

GBSS14.0
Feature Activation Guide 10 Configuring Assignment and Immediate Assignment
10 Configuring Assignment and Immediate

Assignment
Assignment and Immediate Assignment.
Prerequisites
l License
Context
Assignment and immediate assignment are two important procedures during call setup. Normal
immediate and immediate assignment procedures do not require setting of any parameter.
Parameter setting is required only in the immediate assignment of TCHs. The following section
describes how to configure the function of immediate TCH assignment.
Procedure
1. Run the BSC6900 MML command SET GCELLBASICPARA (CME single
Batches). In this step, set TCH Immediate Assignment to YES(Yes).
1. When an MS camps on a cell and no MS is processing services in the cell, block the
SDCCHs and disable the SDCCH dynamic adjustment function.
– Run the BSC6900 MML command SET GTRXCHANADMSTAT to block an
SDCCH. In this step, set Channel No. to the number of the SDCCH and
Administrative State to Lock(Lock). To block more SDCCHs, run the SET
GTRXCHANADMSTAT command for each SDCCH you want to block.

GBSS14.0
Feature Activation Guide 10 Configuring Assignment and Immediate Assignment
– Run the BSC6900 MML command SET GCELLBASICPARA to disable

SDCCH dynamic adjustment. In this step, set SDCCH Dynamic Allocation
Allowed to NO(No).
2. Use the MS to initiate a call.
3. Check the messages traced over the Abis interface.
On the Abis interface message tracing window, the CHANNEL ACTIVATION
message is traced. The field Channel Mode and Type indicates that a TCH, instead of
an SDCCH, is assigned during immediate assignment. During assignment, the
messages Mode Modify Request and Mode Modify Acknowledge are traced.
4. After the verification, unblock the SDCCH and enable SDCCH dynamic adjustment
immediately.
– Run the BSC6900 MML command SET GTRXCHANADMSTAT to unblock
an SDCCH. In this step, set Channel No. to the number of the SDCCH and
Administrative State to Unlock(Unlock). To unblock more SDCCHs, run the
SET GTRXCHANADMSTAT command for each SDCCH you want to unblock.
– Run the BSC6900 MML command SET GCELLBASICPARA to enable
SDCCH dynamic adjustment. In this step, set SDCCH Dynamic Allocation
Batches). In this step, set TCH Immediate Assignment to NO(No).
----End
Example
//Activating Assignment and Immediate Assignment
SET GCELLBASICPARA: IDTYPE=BYID, CELLID=0, IMMASSEN=YES;
//Deactivating Assignment and Immediate Assignment

SET GCELLBASICPARA: IDTYPE=BYID, CELLID=0, IMMASSEN=NO;

GBSS14.0
Feature Activation Guide 11 Configuring Call Reestablishment
11 Configuring Call Reestablishment
Call Reestablishment.
Prerequisites
l License
– The MSC supports this feature.
Context
When an MS encounters a radio link failure during the call, the call reestablishment procedure
can be performed to reestablish the radio link connection so that the original call can proceed.
This mechanism shortens call interruption and improves user experience.
Procedure
Batches). In this step, set Call Reestablishment Forbidden to NO(No).
2. Optional: Run the BSC6900 MML command SET GCELLTMR (CME single
configuration: Cell Configuration Express > Timer Attributes > Timer
Parameters in Batches). In this step, set TREESTABLISH to an appropriate value.
If this parameter is set to a great value, the radio resources assigned previously are
reserved for a long time, which results in network congestion.

GBSS14.0
1. Select a cell for test. The test cell must have two TRXs, where, TRX1 is the BCCH
TRX and TRX2 is the non-BCCH TRX. TRX2 requires an independent variable
attenuator or a device that can dynamically adjust the uplink and downlink signals of
TRX2.
2. Use an MS to make a call on the test cell. Block all the TCHs on TRX1 so that the
MS uses a TCH on TRX2. Then, unblock all the TCHs on TRX1. For details about
how to block and unblock TCHs, see SET GTRXCHANADMSTAT
3. Attenuate the signals of TRX2 sharply by using the variable attenuator or other
devices, check the signaling traced on the A and Abis interfaces, and monitor the
channel status of the test cell.
Expected result:
– As displayed in the channel status monitoring window, the MS reestablishes a call
on TRX1 of the test cell.
– The signaling messages shown in Figure 11-1 are traced.

GBSS14.0
Figure 11-1 Signaling messages

GBSS14.0

Batches). In this step, set Call Reestablishment Forbidden to YES(Yes).
----End
Example
//Activating Call Reestablishment
SET GCELLBASICPARA: IDTYPE=BYID, CELLID=0, CALLRESTABDIS=NO;
SET GCELLTMR: IDTYPE=BYID, CELLID=0, MSIPFAILINDDELAY=10000;
//Deactivating Call Reestablishment

SET GCELLBASICPARA: IDTYPE=BYID, CELLID=0, CALLRESTABDIS=YES;

GBSS14.0
Feature Activation Guide 12 Configuring TCH Re-assignment
12 Configuring TCH Re-assignment
TCH Re-assignment.
Prerequisites
l License
Context
TCH re-assignment is a procedure in which the BSC re-assigns a TCH to the MS after the MS
returns to the SDCCH because a TCH fails to be assigned to the MS.
Procedure
Parameters in Batches). In this step, set Allow Reassign to YES(Yes).
1. Optional: Run the BSC6900 MML command SET GCELLCCAD. In this step, set
Frequency Band of Reassign to Same_Band(Same Band).
NOTE
This parameter indicates the frequency band to be assigned during TCH re-assignment. If the
parameter is set to Same_Band(Same Band), then a channel of the same frequency band as
the originally assigned TCH is assigned preferentially.
2. Reserve an idle TCH on the BCCH TRX and block other TCHs on the BCCH TRX.

GBSS14.0
Feature Activation Guide 12 Configuring TCH Re-assignment
Run the BSC6900 MML command SET GTRXCHANADMSTAT to block a TCH.

In this step, set Channel No. to the number of the TCH to be blocked and
Administrative State to Lock(Lock).
3. Reserve an idle TCH on the non-BCCH TRX and block other TCHs on the non-BCCH
TRX. In addition, degrade the uplink signal transmitted on the TRX, for example,
remove the uplink antenna for the non-BCCH TRX.
Expected result: Initiate a call in the cell. In the first assignment, a TCH on the non-
BCCH TRX is assigned. The call is re-assigned onto the TCH of the BCCH TRX,
because the assignment over the Um interface fails for this TRX.
Parameters in Batches). In this step, set Allow Reassign to NO(No).
----End
Example
//Activating TCH Re-assignment
SET GCELLCCBASIC: IDTYPE=BYID, CELLID=0, REASSEN=YES;
//Verifying TCH Re-assignment

SET GCELLCCAD: IDTYPE=BYID, CELLID=0, REASSFREQBAND=Same_Band;
//Deactivating TCH Re-assignment

SET GCELLCCBASIC: IDTYPE=BYID, CELLID=0, REASSEN=NO;

GBSS14.0
Feature Activation Guide 13 Configuring Radio Link Management
13 Configuring Radio Link Management
This section describes how to activate, verify, and deactivate the link error indication procedure
of the basic feature GBFD-111002 Radio Link Management. Other procedures of the feature do
not need to be configured.
Prerequisites
l License
Context
The procedures involved in radio link management are as follows:
l Link establishment indication
l Link establishment request
l Link release indication
l Link release request
l Transmission of a transparent L3-Message in acknowledged mode
l Reception of a transparent L3-Message in acknowledged mode
l Transmission of a transparent L3-Message in unacknowledged mode
l Reception of a transparent L3-Message in unacknowledged mode
l Link error indication
The link error indication procedure enables the BTS to notify the BSC of exceptions that occur
on the radio link layer.
Procedure
1. Run the BSC6900 MML command SET GCELLCCTMR (CME single
configuration: Cell Configuration Express > Call Control > Call Control Timer

GBSS14.0
Feature Activation Guide 13 Configuring Radio Link Management
Parameters in Batches) to set parameters for a specified cell. In this step, set T200
SDCCH, T200 FACCH/F, T200 FACCH/H, T200 SACCH TCH SAPI0, T200
SACCH TCH SAPI, T200 SACCH SDCCH, T200 SDCCH SAPI3, Use LAPDm
N200, N200 of Release, N200 of Establish, N200 of SACCH, N200 of SDCCH,
N200 of FACCH/Half Rate, and N200 of FACCH/Full Rate to appropriate values.
1. Run the BSC6900 MML command LST GCELLCCTMR to query call control timer
parameters for the corresponding cell.
Expected result: The parameter values queried by running the preceding command
are the same as the values set in the activation procedure.
2. On the BSC6900 LMT, click Trace and display the Abis Interface CS Trace dialog
box. On the Basic tab page, select RSL under Trace Type. On the RSL tab page,
select RLM under Message Type, select TRX from the Filter Flag drop-down list,
and then specify the TRX ID.
3. Use an MS to make a call and query the channel occupied by the call. Remove the
battery of the MS during the call.
4. Run the BSC6900 MML command SET FHO to initiate a forced handover for the
MS. Set Handover Scope to FREE(Free).
5. Check messages traced in step 2. Then, check whether the interval between the DATA
REQ message and the ERROR INDication message is consistent with the values of
N200 and T200 set in the activation procedure. The DATA REQ message contains
the Handover command message, which is transmitted over the Um interface.
Expected result: The interval of the messages for the full-rate channel is the same as
the product of values of N200 of FACCH/Full Rate and T200 FACCH/Full Rate.
The interval of the messages for the half-rate channel is the same as the product of
values of N200 of FACCH/Half Rate and T200 FACCH/Half Rate.
----End
Example
//Activating the link error indication procedure of Radio Link Management
SET GCELLCCTMR: IDTYPE=BYID, CELLID=0, T200SDCCH=1, T200FACCHF=1,
T200FACCHH=1, T200SACCT0=1, T200SACCH3=1, T200SACCHS=1, T200SDCCH3=1;
//Verifying the link error indication procedure of Radio Link Management
LST GCELLCCTMR: IDTYPE=BYID, CELLID=0;
SET FHO: OBJTYPE=CELL, CELLIDTYPE=BYID, CELLID=0, HOMOD=FREE;

GBSS14.0
Feature Activation Guide 14 Configuring Faulty Management
14 Configuring Faulty Management
This section describes how to activate, verify, and deactivate the OML detection function in the
optional feature MRFD-210304 Faulty Management.
Prerequisites
– All 3900 series base stations except BTS3900B support this feature.
l License
– TDM transmission is applied between the BSC and the BTS.
Context
OML detection enables operators to determine whether the E1 link connection between the BSC
and the BTS is correct immediately after the link is set up, facilitating fault locating and
troubleshooting.
In IP over E1 networking mode, OML detection is unnecessary because the BSC uses the
Equipment Serial Number (ESN) of a BTS to identify a BTS or sends transmission configuration
to a BTS. If the link connection between the BSC and the BTS is incorrect, extended signaling
links (ESLs) or operation and maintenance links (OMLs) fail to be set up.
Procedure
1. Run the BSC6900 MML command DEA BTS (CME single configuration: Main
View > Right click BTS > Deactivate BTS; CME batch modification center: not
supported) to deactivate the BTS.
2. Run the BSC6900 MML command SET BTSOMLDETECT (CME single
configuration: BTS Configuration Express > BTS Extend Attributes > BTS OML
Timeslot Detection Function; CME batch modification center: not supported). In
this step, set OMLDETECTSWITCH to CONCHK(Signaling link check) and

GBSS14.0
Feature Activation Guide 14 Configuring Faulty Management
BTSBARCODE to the ESN of the target BTS, that is, the bar code of the BBU
backplane.
3. Run the BSC6900 MML command ACT BTS (CME single configuration: Main
View > Right click BTS > Activate BTS; CME batch modification center: not
supported) to activate the BTS.
1. Run the BSC6900 MML command SET BTSOMLDETECT. In this step, set
OMLDETECTSWITCH to CONCHK(Signaling link check) and
BTSBARCODE to the ESN which is of a non-target BTS.
2. Log in to the LMT and then choose Alarm/Event > Browse Alarm/Event, check
whether the ALM-21821 Site Signaling Link Connection Mismatch is generated on
the alarm console.
Expected result: The alarm is generated.
2. Run the BSC6900 MML command SET BTSOMLDETECT (CME single
configuration: BTS Configuration Express > BTS Extend Attributes > BTS OML
Timeslot Detection Function; CME batch modification center: not supported). In
this step, set OMLDETECTSWITCH to OFF(Off).
----End
Example
/*Activating OML detection*/
//Deactivating the BTS
DEA BTS: IDTYPE=BYID, BTSID=1;
//Enabling OML detection
SET BTSOMLDETECT: IDTYPE=BYID, BTSID=1, OMLDETECTSWITCH=CONCHK,
BTSBARCODE="20";
//Activating the BTS
ACT BTS: IDTYPE=BYID, BTSID=1;
/*Verifing OML detection
SET BTSOMLDETECT: IDTYPE=BYID, BTSID=1, OMLDETECTSWITCH=CONCHK,
BTSBARCODE="21";
/*Deactivating OML detection*/
//Disabling OML detection
SET BTSOMLDETECT: IDTYPE=BYID, BTSID=1, OMLDETECTSWITCH=OFF;

GBSS14.0
Feature Activation Guide 15 Configuring BTS Software Management
15 Configuring BTS Software Management
This section describes how to activate, verify, and deactivate the integrity check function
introduced in the basic feature MRFD-210402 BTS Software Management. Other functions
involved in the feature do not need to be configured. (This feature cannot be configured using
the CME. )
Prerequisites
– Only 3900 series base stations support this feature.
l License
– The M2000 supports this feature.
Context
When software and a configuration file are transmitted between the M2000 and the BSC, the
software and file may be damaged because of unstable transmission links or malicious attacks.
The integrity check function can check the correctness and integrity of software and
configuration files.
Procedure
1. Run the BSC6900 MML command SET BTSDIGSIGN to turn on the BTS software
integrity protection switch. In this step, set Software Digital Signature Verification
Switch to ON(On).
1. Run the BSC6900 MML command DSP BTSDIGSIGN to check whether the BTS
software integrity protection switch has been turned on.
Expected result: Software Digital Signature Verification Switch is set to ON
(On).

GBSS14.0
Feature Activation Guide 15 Configuring BTS Software Management
1. Run the BSC6900 MML command SET BTSDIGSIGN to turn off the BTS software
integrity protection switch. In this step, set Software Digital Signature Verification
Switch to OFF(Off).
----End
Example
//Activation procedure
SET BTSDIGSIGN: IDTYPE=BYID, BTSID=1, DIGSIGNSW=ON;
//Verification procedure
DSP BTSDIGSIGN: IDTYPE=BYID, BTSID=1;
//Deactivation procedure
SET BTSDIGSIGN: IDTYPE=BYID, BTSID=1, DIGSIGNSW=OFF;

GBSS14.0 16 Configuring Combined Cabinets and Cabinet Groups of
Feature Activation Guide BTSs
16 Configuring Combined Cabinets and

Cabinet Groups of BTSs
This section describes how to activate, verify, and deactivate the basic features GBFD-111501
BTS Combined Cabinet and GBFD-111502 BTS Hybrid Cabinet Group. (This feature cannot
be configured using the CME. )
Prerequisites
– The cabinets and cables of the BTSs in combined-cabinet and cabinet-group mode are
installed.
– The DIP switches of the BTSs in combined-cabinet and cabinet-group mode are set.
NOTE
For details about how to install cabinets, connect cables, and set DIP switches, see the relevant
Product Description and Installation Guide contained in customer documents.
– The BTS3012, BTS3006C, BTS3002E, and BTS3900E support the combined-cabinet
installation mode.
– The BTS3012, BTS3012II, BTS3012III, BTS3012AE, BTS3006C, BTS3002E, and
BTS3900E support the cabinet-group installation mode.
l License
Context
l Combined cabinets
– Multiple BTS cabinets of the same type are connected together to serve as one BTS. In
this case, the DTRU subrack is enlarged.
– The cabinet configured with the DTMU is the basic cabinet, whereas the cabinet not
configured with the DTMU is the extension cabinet. The extension cabinet shares the
DTMU with the basic cabinet.
– Figure 16-1 shows the connections of the BTS3012 combined cabinets.

Figure 16-1 Connections of the BTS3012 combined cabinets
l Cabinet groups
– Multiple groups of compatible combined cabinets are connected together to serve as
one BTS. In this case, the service capacity of each site is increased. The first cabinet of
each cabinet group is the basic cabinet.
– A cabinet group can be one basic cabinet or two combined cabinets. The cabinet group
that provides synchronization clock signals is called basic cabinet group. Other cabinet
groups are called extension cabinet groups. The basic cabinet of each cabinet group
can be configured with one or two DTMUs.
– Figure 16-2 shows the connections of the BTS3012 cabinets groups.
Figure 16-2 Connections of BTS3012 cabinet groups
l The BTS3012 supports a maximum of two combined cabinets and three cabinet groups.
Two combined cabinets of the BTS3012 support 24 carriers, and three cabinet groups
support 72 TRXs.
l Combined cabinets and cabinet groups are distinguished in cabinet numbers. In cabinet
group mode, three consecutive combined cabinets form one cabinet group. The basic
cabinet group is comprised of cabinets 0 to 2, extension cabinet group 1 is comprised of
cabinets 3 to 5, and extension cabinet group 2 is comprised of cabinets 6 to 8. The BTS3012
supports a maximum of two combined cabinets and three cabinet groups. The
corresponding cabinet numbers are as follows:
– Basic cabinet group: 0 and 1
– Extension cabinet group 1: 3 and 4
– Extension cabinet group 2: 6 and 7

Procedure
l Activation procedure
1. Run the BSC6900 MML command ADD BTS to add a BTS.
2. Run the BSC6900 MML command ADD BTSCABINET to add a cabinet.
NOTE
In combined-cabinet and cabinet-group mode, the principles for adding Cabinet No. are as
follows:
l If the BTS3012 is in combined-cabinet mode, Cabinet No. is 0 and 1.
l If the BTS3012 is in cabinet-group mode, Cabinet No. is 0, 1, 3, 4, 6, and 7.
3. Run the BSC6900 MML command ADD BTSTRXBRD to add TRX boards.
NOTE
If the BTS3012 does not support the separated mode, the QTRU cannot be configured.
4. Run the BSC6900 MML command ADD GCELL to add GSM cells.
5. Run the BSC6900 MML command ADD GCELLFREQ to add cell frequencies.
6. Run the BSC6900 MML command ADD GCELLOSPMAP to add cell signaling
point relation.
7. Run the BSC6900 MML command ADD CELLBIND2BTS to bind cells to the BTS.
8. Optional: Run the BSC6900 MML command SET GCELLGPRS to set the basic
GPRS attributes of 2G cells.
9. Run the BSC6900 MML command ADD GTRX to add TRXs for a cell.
10. Run the BSC6900 MML command ADD TRXBIND2PHYBRD to bind logical
TRXs to the channels on TRX boards
11. Optional: Run the BSC6900 MML command SET GTRXDEV to set TRX device
attributes.
12. Optional: Run the BSC6900 MML command SET BTSIDLETS to configure idle
timeslots.
NOTE
During the processing of PS services, perform step 8, step 11, and step 12.
13. Run the BSC6900 MML command ADD BTSANTFEEDERBRD to add the antenna
board.
14. Run the BSC6900 MML command SET BTSANTFEEDERCONNECT to
configure the connection relation of antennas of the BTS.
15. Run the BSC6900 MML command MOD BTSANTFEEDERBRD to modify the
frequency band attributes of BTS antennas.
16. Repeat Step 2 through Step 15 to add and configure the extension cabinet and
information about the cabinet according to the principles for adding Cabinet No. in
combined-cabinet and cabinet-group mode.
NOTE
If the BTS3012 is in combined-cabinet mode, addition of cells for the extension cabinet is not
required. Therefore, you do not need to repeat Step 4 through Step 8.
17. Add the BTS connection according to the type of BTS connection.
– If the BTS3012 is in combined-cabinet mode, go to Step 18.
– If the BTS3012 is in cabinet-group mode, go to Step 19.

18. Run the BSC6900 MML command ADD BTSCONNECT to add the connection links
from the basic cabinet to the BSC, and then set Dest Node Type to BSC. In addition,
set Subrack No., Slot No., and Port No..
19. Add the connection links from the basic cabinet group to the BSC, and add the
connection links from the extension cabinet groups to the basic cabinet group or the
BSC.
– Run the BSC6900 MML command ADD BTSCONNECT to add the connection
links from the basic cabinet group to the BSC, and then set Dest Node Type (select
Connect to BSC on the CME) to BSC. In addition, set Subrack No., Slot No.,
and Port No..
– Run the BSC6900 MML command ADD BTSCONNECT to add the connection
links from the extension cabinet groups to the basic cabinet group or the BSC
– If the extension cabinet groups connect to the basic cabinet group, set Dest
Node Type (select Connect to BSC on the CME) to BTS. In addition, set the
following parameters related to the BTSs in extension cabinet groups: Dest
Father Index Type (Not required on the CME), Dest Father BTS Index (Not
required on the CME), and Dest Father BTS Port No..
– If the extension cabinet groups connect to the BSC, set Dest Node Type (select
Connect to BSC on the CME) to BSC. In addition, set Subrack No., Slot
No., and Port No..
20. Run the BSC6900 MML command ACT BTS to activate a BTS.
l Verification procedure
1. Click Device Maintenance on the LMT. The Device Maintenance tab page is
displayed.
2. Click the added BTSs in Activation Procedures in Device Navigation Tree. The
corresponding device panels are displayed on BTS Device Panel.
3. Select the main and extension cabinets in the Rack No. drop-down list. Then, check
the board status on BTS Device Panel.
– If the board status is Normal, the BTS3012 is in combined-cabinet and cabinet-
group mode.
– If the board status is Faulty, clear the alarm according to handling suggestions
provided in the BSC6900 Alarm Reference.
l Deactivation procedure
1. Run the BSC6900 MML command DEA BTS to deactivate a BTS.
2. Run the BSC6900 MML command RMV BTS to delete a BTS.
----End
Example
//Add a BTS
ADD BTS: BTSID=9, BTSNAME="BTS3012_TDM", BTSTYPE=BTS3012, BTSDESC="3012",
SEPERATEMODE=SUPPORT, SERVICEMODE=TDM;
//Add a cabinet
ADD BTSCABINET: IDTYPE=BYID, BTSID=9, CN=0, SRANMODE=NOT_SUPPORT,
TYPE=BTS3012;
//Add TRX boards
ADD BTSTRXBRD: IDTYPE=BYID, BTSID=9, BT=TRU, SRN=1, SN=0;
//Add GSM cells
ADD GCELL: CELLID=0, CELLNAME="cell0", TYPE=GSM900, MCC="460", MNC="10",

LAC=10, CI=11, IUOTP=Normal_cell;

//Add cell frequencies
ADD GCELLFREQ: IDTYPE=BYID, CELLID=0, FREQ1=1, FREQ2=2;
//Add cell signaling point relation
ADD GCELLOSPMAP: IDTYPE=BYID, CELLID=0, OPC=153;
//Bind cells to the BTS
ADD CELLBIND2BTS: IDTYPE=BYID, CELLID=0, BTSID=9;
//Set the basic GPRS attributes of 2G cells
SET GCELLGPRS: IDTYPE=BYID, CELLID=1, GPRS=SupportAsInnPcu, EDGE=NO;
//Add TRXs for a cell
ADD GTRX: IDTYPE=BYID, CELLID=0, TRXID=0, FREQ=1,ISMAINBCCH=YES;
//Bind logical TRXs to the channels on TRX boards
ADD TRXBIND2PHYBRD: TRXID=0, TRXTP=TRU, TRXPN=0, SRN=1, SN=0;
//Set TRX device attributes
SET GTRXDEV: TRXID=0, POWL=8;
//Add the extension cabinet of the basic cabinet group
TYPE=BTS3012;
//Add the basic cabinet of the extension cabinet group
TYPE=BTS3012;
//Configure idle timeslots
SET BTSIDLETS: IDTYPE=BYID, BTSID=9, CGN=1, TSCOUNT=20;
//Add the antenna board
ADD BTSANTFEEDERBRD: IDTYPE=BYID, BTSID=9, SRN=3, SN=4, BT=DDPM_DDPU,
DTRX=1, DTRXSRN=1, DTRXSN=0, DTRXPN=0, AORB=A;
//Configure the connection relation of antennas of the BTS
SET BTSANTFEEDERCONNECT: IDTYPE=BYID, BTSID=9, SRN=3, SN=4, BT=DDPM_DDPU,
DTRX=1, DTRXSRN=1, DTRXSN=0, DTRXPN=1,AORB=B;
//Add the connection links from the basic cabinet group to the BSC
ADD BTSCONNECT: IDTYPE=BYID, BTSID=9, INPN=0, DESTNODE=BSC, SRN=0, SN=25,
PN=1;
//Add the connection links from the extension cabinet groups to the basic
cabinet group
ADD BTSCONNECT: IDTYPE=BYID, BTSID=9, INPN=8, DESTNODE=BTS,
UPBTSIDTYPE=BYID, UPBTSID=9, FPN=1;
//activate a BTS
ACT BTS: IDTYPE=BYID, BTSID=9, ACTTYPE=ACTALL;
//Deactivate a BTS
//Delete a BTS
RMV BTS: IDTYPE=BYID, BTSID=0;

GBSS14.0
Feature Activation Guide 17 Configuring Connection Inter BSC over IP
17 Configuring Connection Inter BSC over

IP
Connection Inter BSC over IP.
Prerequisites
– If the Abis or A interface uses IP transmission, switches can be used to interconnect the
IP interface boards of two BSCs. If the Abis or A interface does not use IP transmission,
a pair of IP interface boards need to be configured for each BSC.
l License
– The license controlling this feature has been activated. For details on how to activate
the license, see 4 Activating the GSM License. For details about license items, see 2
Feature Activation and License Item Descriptions.
Context
IP-based inter-BSC interconnection enables operators to use IP networks to interconnect the
BSCs so that the BSCs can communicate with each other directly. Inter-BSC interconnection is
used for exchanging information between BSCs in scenarios such as an inter-BSC soft-
synchronized network or interference-based channel allocation (IBCA). Only signaling can be
exchanged over inter-BSC interconnection.
Procedure
1. Optional: Run the BSC6900 MML command ADD BRD (CME single configuration:
Device Panel > Add Board; CME batch modification center: not supported) at the
current BSC to add a pair of IP interface boards.
2. Run the BSC6900 MML command ADD DEVIP (CME single configuration: Abis
Configuration Express > IP Transport > Device IP Address; CME batch
modification center: not supported) at the current BSC to add a device IP address.

GBSS14.0
3. Run the BSC6900 MML command ADD ETHIP (CME single configuration: Abis
Configuration Express > IP Transport > Ethernet Port IP Address; CME batch
modification center: not supported) at the current BSC to add a port IP address.
4. Run the BSC6900 MML command ADD IPRT (CME single configuration: Abis
Configuration Express > IP Transport > IP Route; CME batch modification center:
not supported) at the current BSC to add an IP route. In this step, set Destination IP
address to the port IP address of the peer board (that is, the port IP address of the IP
interface board at the peer BSC).
5. Run the BSC6900 MML command ADD OPC (CME single configuration: GSM
Global Configuration Express > BSC Basic Configuration > OSP; CME batch
modification center: not supported) at the current BSC to add an OSP.
6. Run the BSC6900 MML command ADD N7DPC (CME single configuration: GSM
Global Configuration Express > BSC Basic Configuration > DSP Of DPU; CME
batch modification center: not supported) at the current BSC to add a DSP.
7. Run the BSC6900 MML command ADD M3LE (CME single configuration: GSM
Global Configuration Express > BSC Basic Configuration > M3UA Local
Entity; CME batch modification center: not supported) at the current BSC to add an
M3UA local entity.
8. Run the BSC6900 MML command ADD M3DE (CME single configuration: GSM
Global Configuration Express > BSC Basic Configuration > M3UA Destination
Entity; CME batch modification center: not supported) at the current BSC to add an
M3UA destination entity.
9. Run the BSC6900 MML command ADD M3LKS (CME single configuration: GSM
Global Configuration Express > BSC Basic Configuration > M3UA Link Set;
CME batch modification center: not supported) at the current BSC to add an M3UA
link set.
10. Run the BSC6900 MML command ADD M3RT (CME single configuration: A
Configuration Express > IP Transport > M3UA Route; CME batch modification
center: not supported) at the current BSC to add an M3UA route.
11. Run the BSC6900 MML command ADD SCTPLNK (CME single configuration: A
Configuration Express > IP Transport > SCTP Link; CME batch modification
center: not supported) at the current BSC to add an SCTP link.
12. Run the BSC6900 MML command ADD M3LNK (CME single configuration: GSM
CME batch modification center: not supported) at the current BSC to add an M3UA
link. After this command is executed, the configuration of links at the current BSC is
complete.
13. Repeat Step 1 through Step 12 to configure the links at the peer BSC.
1. Run the BSC6900 MML command DSP N7DPC, and verify that the value of SCCP
DSP state is Accessible.
----End
Example
//Configuring Connection Inter BSC over IP

GBSS14.0
//(Optional) Adding a pair of IP interface boards

ADD BRD: SRN=0, BRDCLASS=XPU, BRDTYPE=XPUa, LGCAPPTYPE=RGCP, SN=0;
ADD BRD: SRN=0, BRDCLASS=XPU, BRDTYPE=XPUa, LGCAPPTYPE=RGCP, SN=1;
//Adding a device IP address for the current BSC

ADD DEVIP: SRN=0, SN=24, DEVTYPE=LOGIC_IP, IPADDR="10.10.10.216";
//Adding a port IP address for the current BSC

ADD ETHIP: SRN=0, SN=24, PN=1, IPINDEX=0, IPADDR="2.2.2.2",
MASK="255.255.255.0";
//Adding an IP route for the current BSC

ADD IPRT: SRN=0, SN=24, DSTIP="10.10.10.217", DSTMASK="255.255.255.255",
NEXTHOP="2.2.2.1", PRIORITY=HIGH, REMARK="IPRT";
//Adding an OSP for the current BSC

ADD OPC: NAME="BSC216", SPX=0, NI=NATB, SPCBITS=BIT14, SPDF=WNF,
SPC=H'A1;
//Adding a DSP for the current BSC

ADD N7DPC: NAME="BSC217", DPX=0, SPX=0, SPDF=WNF, DPC=H'B1, DPCT=IUR_G,
BEARTYPE=M3UA;
//Adding an M3UA local entity

ADD M3LE: LENO=0, SPX=0, ENTITYT=M3UA_IPSP, RTCONTEXT=0, NAME="BSC216";
//Adding an M3UA destination entity

ADD M3DE: DENO=98, LENO=0, DPX=0, ENTITYT=M3UA_IPSP, RTCONTEXT=0,
NAME="BSC217";
//Adding an M3UA link set

ADD M3LKS: SIGLKSX=1, DENO=98, NAME="T0217";
//Adding an M3UA route

ADD M3RT: DENO=98, SIGLKSX=1, PRIORITY=0, NAME="TO217";
//Adding an SCTP link

ADD SCTPLNK: SRN=0, SN=0, SCTPLNKN=0, MODE=CLIENT, APP=M3UA, DSCP=48,
LOCPN=60000, LOCIP1="10.10.10.216", PEERIP1="10.10.10.217", PEERPN=2905,
LOGPORTFLAG=NO, VLANFLAG1=DISABLE, VLANFlAG2=DISABLE, SWITCHBACKFLAG=YES;
//Adding an M3UA link

ADD M3LNK: SIGLKSX=1, SIGLNKID=0, SRN=0, SN=0, SCTPLNKN=0, PRIORITY=0,
NAME="TO217";

GBSS14.0
Feature Activation Guide 18 Configuring Link Aggregation
18 Configuring Link Aggregation
Link Aggregation.
Prerequisites
– This feature applies only to 3900 series base stations excluding the BTS3902E.
– This feature is only supported on BSC6900.
– In the earlier versions than RAN13.0, trunk group configuration cannot support IP PM.
l License
l Others
– This feature requires the support from peer transmission devices, such as switches and
base stations.
– This feature supports IP networking, layer 2 (L2) networking, and layer 3 (L3)
networking.
Context
This feature enables multiple FE or GE ports to be bound to form a logical port. This provides
high bandwidth for end-to-end transmission, achieves load sharing across these FE or GE ports,
and improves the transmission reliability.
Procedure
– Activate Link Aggregation on the BSC6900.
1. Run the BSC6900 MML command ADD DEVIP (CME single configuration:
Abis Configuration Express > IP Transport > Device IP Address; CME batch
modification center: not supported) to add a device IP address to a board.
2. Run the BSC6900 MML command ADD ETHTRK (CME single configuration:
Abis Configuration Express > IP Transport > Link Aggregation; CME batch
modification center: not supported) to add an Ethernet link aggregation group. In

GBSS14.0
this step, set the Trunk group work mode to LOAD_SHARING(Load

sharing), set the Aggregation Mode to STATIC_LACP when the peer end
supports the LACP protocol or set the Aggregation Mode to
MANUAL_AGGREGATION when the peer end does not support the LACP
protocol, and set the Flow control switch to ON(ON).
3. Run the BSC6900 MML command ADD ETHTRKLNK (CME single
configuration: Abis Configuration Express > IP Transport > Link
Aggregation; CME batch modification center: not supported) to add a specified
physical port to an Ethernet link aggregation group.
NOTE
If the Ethernet link aggregation group is configured with multiple physical ports, repeat this step
until all the required physical ports are configured.
4. Run the BSC6900 MML command ADD ETHTRKIP (CME single
configuration: Abis Configuration Express > IP Transport > Trunk IP
Address; CME batch modification center: not supported) to add an IP address to
an Ethernet link aggregation group. When multiple virtual local area network
(VLAN) gateways are planned, run this command for each IP address you want to
add.
– Activate Link Aggregation on the NodeB.
1. Run the NodeB MML command ADD DEVIP (CME single configuration: NodeB
Configuration Express > IUB_NodeB > IP Transport Layer > IPPort > Device
IP Address; CME batch modification center: Modifying Physical NodeB
Parameters in Batches) to add a device IP address to an Ethernet port. In this step,
set Port Type to ETHTRK(Ethernet Trunk).
2. Run the NodeB MML command ADD ETHTRK (CME single configuration:
NodeB Configuration Express > IUB_NodeB > IP Transport Layer >
IPPort > Ethernet Trunk; CME batch modification center: not supported) to add
an Ethernet link aggregation group.
3. Run the NodeB MML command ADD ETHTRKLNK (CME single
configuration: NodeB Configuration Express > IUB_NodeB > IP Transport
Layer > IPPort > Ethernet Trunk > Ethernet Trunk Member; CME batch
modification center: not supported) to add a member port to an Ethernet link
aggregation group. When multiple member ports need to be added, run this
command for each port you want to add.
– Verify the effect of Link Aggregation on the BSC6900.
1. Run the BSC6900 MML command DSP ETHTRK to query whether an Ethernet
link aggregation group is available.
NOTE
Expected result: If the value of Status of ETHTRK is UP in the command output, the Ethernet
link aggregation group is available.
2. Set the IP address of the peer NE to be on the same network segment as the IP
address for the Ethernet link aggregation group. For example, set the IP address
of the peer NE to 16.16.16.2.
3. Run the BSC6900 MML command PING IP to check the IP communication
between the local and peer ends.

GBSS14.0
NOTE
Expected result: If this command is executed and the command output indicates that no packet
loss occurs, the Ethernet link aggregation group has been successfully configured.
– Verify the effect of Link Aggregation on the NodeB.
1. Run the NodeB MML commandDSP ETHTRK to query whether an Ethernet link
aggregation group is available.
2. Run the NodeB MML commandDSP ETHTRKLNK to query whether a member
port of an Ethernet link aggregation group is available.
– Deactivate Link Aggregation on the BSC6900.
1. Run the BSC6900 MML commandRMV ETHTRKIP (CME single
Address; CME batch modification center: not supported) to remove an IP address
from an Ethernet link aggregation group. If the removal fails, perform operations
as prompted.
2. Run the BSC6900 MML commandRMV ETHTRK (CME single configuration:
Abis Configuration Express > IP Transport > Link Aggregation; CME batch
modification center: not supported) to remove an Ethernet link aggregation group.
– Deactivate Link Aggregation on the NodeB.
1. Run the NodeB MML commandRMV DEVIP (CME single configuration: NodeB
Configuration Express > IUB_NodeB > IP Transport Layer > IPPort > Device
IP Address; CME batch modification center: not supported) to remove a device
IP address.
2. Run the NodeB MML commandRMV ETHTRK (CME single configuration:
NodeB Configuration Express > IUB_NodeB > IP Transport Layer >
IPPort > Ethernet Trunk; CME batch modification center: not supported) to
remove an Ethernet link aggregation group.
----End
Example
//Activating Link Aggregation on the BSC6900
ADD ETHTRK: SRN=2, SN=26, TRKN=2, WORKMODE=ACTIVE_STANDBY,
LACPMODE=MANUAL_AGGREGATION, FLOWCTRLSWITCH=ON;
ADD ETHTRKLNK: SRN=2, SN=26, TRKN=2, TRKLNKSN=26, TRKLNKPN=2,
WORKMODE=ACTIVE_STANDBY, PORTPRI=101;
ADD ETHTRKLNK: SRN=2, SN=26, TRKN=2, TRKLNKSN=27, TRKLNKPN=2,
WORKMODE=ACTIVE_STANDBY, PORTPRI=102;
ADD ETHTRKIP: SRN=2, SN=26, TRKN=2, IPINDEX=0, IPADDR="126.126.126.1",
MASK="255.255.255.0";
/Activating Link Aggregation on the NodeB

//Adding a device IP address to an Ethernet port
ADD DEVIP: CN=0, SRN=0, SN=0, SBT=BASE_BOARD, PT=ETHTRK, PN=0,
IP="192.168.2.24", MASK="255.255.255.0";
//Adding an Ethernet link aggregation group and adding a member port to

an Ethernet link aggregation group
ADD ETHTRK: CN=0, SRN=0, SN=0, SBT=ETH_COVERBOARD, TN=0;
ADD ETHTRKLNK: CN=0, SRN=0, SN=0, SBT=ETH_COVERBOARD, TN=0, PN=0,
PRI=255, FLAG=YES;

GBSS14.0
//Deactivating Link Aggregation on the BSC6900

//Removing active/standby Ethernet link aggregation groups
RMV ETHTRKIP: SRN=2, SN=26, TRKN=2, IPINDEX=0;
RMV ETHTRK: SRN=2, SN=26, TRKN=2;
//Deactivating Link Aggregation on the NodeB
//Removing a device IP address from an Ethernet port

RMV DEVIP: CN=0, SRN=0, SN=0, SBT=BASE_BOARD, PT=ETHTRK, PN=0,
IP="192.168.2.24";
//Removing an Ethernet link aggregation group

RMV ETHTRK: CN=0, SRN=0, SN=0, SBT=ETH_COVERBOARD, TN=0;

GBSS14.0 19 Configuring Intelligent Shutdown of TRX Due to PSU
Feature Activation Guide Failure
19 Configuring Intelligent Shutdown of

TRX Due to PSU Failure
Intelligent Shutdown of TRX Due to PSU Failure.
Prerequisites
– The following types of BTSs support the feature: the DBS3900, BTS3900, and
BTS3900A
l License
Context
If a BTS uses an AC power input and the power switch unit (PSU) is faulty, the power amplifiers
of some TRXs are shut down to reduce the power demand of the BTS to ensure the normal
operation of the BTS.
Procedure
1. Run the BSC6900 MML command SET BTSPSUFP (CME single configuration:
BTS Configuration Express > BTS Board > PSU Fault Shutdown Of TRX
Parameters; CME batch modification center: not supported) to set the parameters
related to TRX shutdown of the PSU board. In this step.
– Set Board Parameter Configuration Enabled to YES(YES).
– Set Tran. Cabinet Configured according to actual requirements.
– Set Service Priority Policy to GSM_PRIOR.
– GSM Multi Carrier BTS Standard does not need to be set.
1. Run the BSC6900 MML command LST BTSPSUFP to query the parameters related
to TRX shutdown when the PSUs are faulty in the corresponding site.

GBSS14.0 19 Configuring Intelligent Shutdown of TRX Due to PSU
Feature Activation Guide Failure
Expected result:
– The value of Board Parameter Configuration Enabled queried in step 2 is
YES.
– The value of Tran. Cabinet Configured queried in step 2 is the same as that set
in step 1.
– The value of Service Priority Policy queried in step 2 is GSM_PRIOR.
2. Remove some PSUs of the site. Ensure that the remaining PSUs and the DCDU cannot
supply power to all the TRXs at the site but can supply power to other equipment.
3. Run the BSC6900 MML command DSP CHNSTAT to query the channel status of
all TRXs at the entire site. In this step, set Object Type to SITE.
Expected result: the status of some TRXs is Enabled and that of some others is
Disabled. The BTS works properly and there is no call drops due to insufficient power
supply.
1. Run the BSC6900 MML command SET BTSPSUFP (CME single configuration:
BTS Configuration Express > BTS Board > PSU Fault Shutdown Of TRX
Parameters; CME batch modification center: not supported). In this step, set Board
Parameter Configuration Enabled to NO(NO).
Expected result: Some TRXs do not automatically shut themselves down when PSU
faults occur.
----End
Example
SET BTSPSUFP: IDTYPE=BYID, BTSID=0, CFGFLAG=YES, ISTRANCABCON=CONFIG,
SRVPRIPOLICY=GSM_PRIOR;
LST BTSPSUFP: IDTYPE=BYID, BTSID=0;
DSP CHNSTAT: OBJTYPE=SITE, IDTYPE=BYID, BTSID=0;
SET BTSPSUFP: IDTYPE=BYID, BTSID=0, CFGFLAG=NO;

GBSS14.0
Feature Activation Guide 20 Configuring Call-Based Flow Control
20 Configuring Call-Based Flow Control
Call-Based Flow Control.
Prerequisites
l License
Context
In cases of emergencies or disasters, a large number of fixed telephones or cell phones from
external networks request to reach the emergency or disaster center. This causes considerable
increase in the mobile terminated services and also causes heavy traffic in the system. This
feature identifies mobile originated call (MOCs) and mobile terminated calls (MTCs) by
different flags and protects either MOCs or MTCs from the effects of flow control. It also allows
telecom operators to decide whether to discard signaling of MOCs or MTCs using flow control,
thereby keeping the system load within a normal level.
Procedure
1. Run the BSC6900 MML command SET BSCFCPARA (CME single configuration:
GSM Global Configuration Express > Software Parameter Configuration > Flow
Control Parameters; CME batch modification center: 3.17 Modifying GBSC
Parameters in Batches). In this step, set MOC Access CPU Rate to be greater than
MTC Access CPU Rate but less than Share in CPU Rate.
NOTE
When the value of MOC Access CPU Rate is greater than that of MTC Access CPU Rate,
the call-based flow control is triggered, and flow control is preferentially implemented on
MTCs.

GBSS14.0
Feature Activation Guide 20 Configuring Call-Based Flow Control
1. Retrieve the counter L3189A: Discarded Channel Requests (MOC) and the counter
L3189B: Discarded Channel Requests (MTC) on the M2000.
Expected result: The value of the counter L3189A: Discarded Channel Requests
(MOC) is smaller than that of the counter L3189B: Discarded Channel Requests
(MTC).
Parameters in Batches). In this step, set MOC Access CPU Rate to a value that is
smaller than or equal to the value of MTC Access CPU Rate.
----End
Example
//Activating Call-Based Flow Control
SET BSCFCPARA: SHAREINCPURATE=50, MOCACCESSCPURATE=51,
MTCACCESSCPURATE=52;
//Deactivating Call-Based Flow Control
SET BSCFCPARA: MOCACCESSCPURATE=52, MTCACCESSCPURATE=51;

GBSS14.0
Feature Activation Guide 21 Configuring Pre-Processing of Measurement Report
21 Configuring Pre-Processing of
Measurement Report
Pre-Processing of Measurement Report.
Prerequisites
– The BTS must support this function.
l License
Context
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, 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, therefore minimizing the risks of Abis transmission
congestion.
Procedure
1. Run the BSC6900 MML command SET GCELLHOCTRL (CME single
configuration: Cell Configuration Express > Handover Data > Handover Control
Parameters in Batches) command to set MR.Preprocessing to
BTS_Preprocessing and set Transfer Original MR, Transfer BTS/MS Power
Class, and Sent Freq.of preprocessed MR as required.
1. Start the tracing of RSL messages on the Abis interface. For details, see Tracing CS
Domain RSL Messages on the Abis Interface in the BSC6900 LMT User Guide.

GBSS14.0
Feature Activation Guide 21 Configuring Pre-Processing of Measurement Report
2. Use the MS to call a fixed-line phone in the test cell.

3. Verify that the Preprocessed Measurement Result message is present.
1. Run the BSC6900 MML command SET GCELLHOCTRL (CME single
configuration: Cell Configuration Express > Handover Data > Handover Control
Parameters in Batches) command to set MR.Preprocessing to
BSC_Preprocessing.
----End
Example
//Activating Pre-Processing of Measurement Report
SET GCELLHOCTRL: IDTYPE=BYID, CELLID=0,
BTSMESRPTPREPROC=BTS_Preprocessing, PRIMMESPPT=NO, BSMSPWRLEV=YES,
MRPREPROCFREQ=Once_ps;
//Deactivating Pre-Processing of Measurement Report

BTSMESRPTPREPROC=BSC_Preprocessing;

GBSS14.0
Feature Activation Guide 22 Configuring System Information Sending
22 Configuring System Information

Sending
System Information Sending.
Prerequisites
l License
Context
System information involves main radio network parameters on the Um interface, including
network identity parameters, cell selection parameters, system control parameters, and network
function parameters. Based on the received system information, an MS can properly select and
access a radio network. Then, the MS can fully use various services provided by the network
and well cooperate with the network.
Procedure
1. Run the BSC6900 MML command SET OTHSOFTPARA (CME single
configuration: GSM Global Configuration Express > Software Parameter
Configuration > Other Software Parameters of BSC; CME batch modification
center: 3.17 Modifying GBSC Parameters in Batches). In this step, set Support
Sent 2QUATER to YES(Yes).
2. Run the BSC6900 MML command ADD G3GNCELL (CME single configuration:
Cell Configuration Express > Neighboring Cell > BSC 3G Neighbor Cell; CME
batch modification center: not supported) to configure neighboring 3G cells based on
the network plan.

GBSS14.0
Feature Activation Guide 22 Configuring System Information Sending
Parameters in Batches) to enable outgoing inter-RAT handovers and incoming inter-
RAT handovers. In this step, set Inter-RAT Out BSC Handover Enable and Inter-
RAT In BSC Handover Enable to YES(Yes).
1. Initiate Abis interface message tracing by referring to Tracing CS Domain Messages
on the Abis Interface. In the Trace Type area, click RSL to trace RSL messages on
the Abis interface.
2. Run the BSC6900 MML command SND GCELLSYSMSG to send system
information. In this step, set Index Type (Not required on the CME) to Cell Index
and the cell index to an appropriate value.
3. Check the CS domain messages traced on the Abis interface.
Expected result: The value of si2-quarter-ind in the System Information Type 3
message is 1. This indicates that the feature has been activated.
Sent 2QUATER to NO(No).
----End
Example
//Activating System Information Sending
SET OTHSOFTPARA: Send2QuterFlag=YES;
ADD G3GNCELL: IDTYPE=BYID, SRC3GNCELLID=2047, NBR3GNCELLID=5100;
SET GCELLHOBASIC: IDTYPE=BYID, CELLID=2047, INTERRATOUTBSCHOEN=YES,
INTERRATINBSCHOEN=YES;
//Deactivating System Information Sending

SET OTHSOFTPARA: Send2QuterFlag=NO;

GBSS14.0
Feature Activation Guide 23 Configuring Daylight Saving Time
23 Configuring Daylight Saving Time
Daylight Saving Time (DST).
Prerequisites
l License
Context
With the DST change rules, you can select the date configuration, week configuration, or hybrid
configuration. Date configuration indicates the DST starts from or ends on a certain date in a
certain month. Week configuration indicates that the DST starts from or ends on a certain day
of a certain week in a certain month. Hybrid configuration indicates that the DST starts from or
ends on a certain day after a certain date in a certain month.
Procedure
1. Run the BSC6900 MML command SET TZ (CME single configuration: GSM Global
Configuration Express > BSC Basic Configuration > Information About Time
Zone and Daylight Saving Time; CME batch modification center: not supported)
command to configure DST. In this step, set DaylightSave to YES(Yes), set Start
Type, StartTime, End Type, EndTime, and AdjustMethod as required.
1. Run the BSC6900 MML command LST TZ command to check whether
DaylightSave is set to YES.
2. As it was daylight saving time, the time with sign DST in MML, Alarms, and log
reports shows the feature has been active, such as 2011-07-01 15:50:25 DST.

GBSS14.0
Feature Activation Guide 23 Configuring Daylight Saving Time
1. Run the BSC6900 MML command SET TZ (CME single configuration: GSM Global
Configuration Express > BSC Basic Configuration > Information About Time
Zone and Daylight Saving Time; CME batch modification center: not supported)
command. In this step, set DaylightSave to NO(No).
----End
Example
//Activating Daylight Saving Time
SET TZ: ZONET=GMT-0800, DST=YES, SM=WEEK, SMONTH=MAR, SWSEQ=LAST,
SWEEK=SUN, ST=02&00&00, EM=WEEK, EMONTH=OCT, EWSEQ=LAST, EWEEK=SUN,
ET=03&00&00, TO=60;
//Deactivating Daylight Saving Time
SET TZ: ZONET=GMT-0800, DST=NO;

GBSS14.0
Feature Activation Guide 24 Configuring SDCCH Dynamic Adjustment
24 Configuring SDCCH Dynamic

Adjustment
SDCCH Dynamic Adjustment.
Prerequisites
l License
l Others
– This feature does not need to be configured when PCU is inner.
– This feature needs to be configured when PCU is outer.
– None.
Context
When the number of users in a cell increases substantially, some users may not be able to access
the network because they cannot obtain SDCCHs. In this case, some TCHs need to be converted
to SDCCHs. When TCHs are not sufficient enough to meet requirements of channel conversion,
dynamic PDCHs are converted to SDCCHs to ensure that all the users can access the network.
When the traffic load decreases, the TCHs and dynamic PDCHs used as SDCCHs are converted
back to TCHs to increase system capacity.
When SDCCHs are insufficient, channels are converted to SDCCHs in the following sequence:
TCHs on the BCCH frequency band, TCHs not on the BCCH frequency band, and dynamic
PDCHs.
Procedure

GBSS14.0

Batches). In this step, set both SDCCH Dynamic Allocation Allowed and Dynamic
PDCH Conversion to SDCCH Allowed to YES(Yes).
2. Run the BSC6900 MML command SET GCELLCHMGBASIC (CME single
configuration: Cell Configuration Express > Channel Management > Basic
Channel Management Parameters of Cell; CME batch modification center: 3.20
Modifying GSM Cell Parameters in Batches). In this step, set Idle SDCCH
Threshold N1, Cell SDCCH Channel Maximum, TCH Minimum Recovery
Time, and Num of TSs Convertible to SDCCHs per TRX to appropriate values.
NOTE
When TCHs on the BCCH frequency band are insufficient, set Dynamically Adjust Inter-
Freq Band SDCCH to YES(Yes) as required.
3. Run the BSC6900 MML command SET GCELLPSCHM (CME single
configuration: Cell Configuration Express > GPRS Attributes > GPRS Channel
Management Parameters of 2G Cell; CME batch modification center: 3.20
Modifying GSM Cell Parameters in Batches). In this step, set Maximum Rate
Threshold of PDCHs in a Cell and Reservation Threshold of Dynamic Channel
Conversion to appropriate values.
NOTE
Monitor Channel Status by referring to Monitoring Channel Status.

As all the channels are occlusive except BCCH.
1. The value of Idle SDCCH Threshold N1 is not smaller than the number of configured
SDCCH channel, and make a CS call in the cell.
Expected result: A TCH is converted to an SDCCH.
2. Run the BSC6900 MML command SET GCELLPSCHM. In this step, set Maximum
Rate Threshold of PDCHs in a Cell to 100 and Reservation Threshold of Dynamic
Channel Conversion to 0.
3. Perform PS services in the cell.
Expected result: All TCHFs are converted to PDCHs.
4. Make another CS call in the cell.
Expected result: A dynamic PDCH is converted to an SDCCH.
5. Enable the cell to remain in the idle state for two minutes. The minimum time of
SDCCHs convert back to TCHs is 120 seconds.
Expected result: The two channels used as SDCCHs are converted back to TCHs.
Batches). In this step, set both SDCCH Dynamic Allocation Allowed and Dynamic
PDCH Conversion to SDCCH Allowed to NO(No).
----End
Example
//Activating SDCCH Dynamic Adjustment
SET GCELLBASICPARA: IDTYPE=BYID, CELLID=1, SDDYN=YES, PDCH2SDEN=YES;

GBSS14.0
SET GCELLCHMGBASIC: IDTYPE=BYID, CELLID=1, IDLESDTHRES=8, CELLMAXSD=100,

MINRESTIMETCH=60;
SET GCELLPSCHM: MAXPDCHRATE=30, DYNCHTRANRESLEV=2;
//Deactivating SDCCH Dynamic Adjustment
SET GCELLBASICPARA: IDTYPE=BYID, CELLID=1, SDDYN=NO, PDCH2SDEN=NO;

GBSS14.0
Feature Activation Guide 25 Configuring Cell Frequency Scan
25 Configuring Cell Frequency Scan
Cell Frequency Scan. (This feature cannot be configured using the CME. )
Prerequisites
l License
Context
CAUTION
Cell frequency scan has the following impacts on other features:
l Cell frequency scan occupies an idle TCH.
l Cell frequency scan cannot be performed when an RF hopping loopback test is performed.
l The cell frequency scan cannot be performed when an idle frame test is performed.
Procedure
1. Run the BSC6900 MML command SET GCELLFREQSCAN command to
configure cell frequency scan.
NOTE
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 cannot be set to a very small value. Otherwise, the execution of the
commands cannot be completed in the specified duration.

GBSS14.0
Feature Activation Guide 25 Configuring Cell Frequency Scan
1. Using WEBLMT, cell frequency scan is queryed.
1. This feature does not need to be deactivated.
----End
Example
//Configure cell frequency scan
SET GCELLFREQSCAN: IDTYPE=BYID, CELLID=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 GCELLFREQSCAN: IDTYPE=BYID, CELLID=0;

GBSS14.0
Feature Activation Guide 26 Configuring Signaling Transport Point (STP)
26 Configuring Signaling Transport Point

(STP)
Signaling Transport Point (STP).
Prerequisites
– The XPUa board is configured.
l License
l Others
– The OPC is configured.
– The physical layer and the data link layer on the A interface are configured.
– The CN supports this feature.
Context
According to the requirements of the operator, the BSC can be connected to the MSC directly
or through STP.
To use an MGW as an STP, ensure that the MGW supports MTP3/M3UA signaling transfer.
Procedure
– TDM transmission
modification center: not supported) to add an Originating Signaling Point (OSP).
In this step, set OSP code bits to BIT14(BIT14).
2. Run the BSC6900 MML command ADD N7DPC (CME single configuration:
GSM Global Configuration Express > BSC Basic Configuration > DSP Of

GBSS14.0
DPU; CME batch modification center: not supported) to add the MGW as the
destination signaling point. In this step, set DSP code[Whole Number] to the
signaling point code of the MGW, DSP type to STP function switch, Link Bear
type to MTP3, and Adjacent flag to YES(DIRECT_CONNECT).
3. Run the BSC6900 MML command ADD MTP3LKS (CME single configuration:
A Configuration Express > TDM Transport > MTP3 Signalling Link Set >
MTP3 Signalling Link Set; CME batch modification center: not supported) to
add an MTP3 link set. In this step, set DSP index to the DSP index set in 2.
4. Run the BSC6900 MML command ADD MTP3LNK (CME single configuration:
MTP3 Signalling Link; CME batch modification center: not supported) to add an
MTP3 link to the link set. In this step, set Signalling link set index to the
Signalling link set index set in 3.
5. Run the BSC6900 MML command ADD MTP3RT (CME single configuration:
A Configuration Express > TDM Transport > MTP3 Signalling Route; CME
batch modification center: not supported) to add an MTP3 route. In this step, set
DSP index to the DSP index set in 2 and Signalling link set index to the
DPU; CME batch modification center: not supported) to add the MSC as the
signaling point code of the MSC, DSP type to A, Link Bear type to MTP3, and
Adjacent flag to NO(NO_DIRECT_CONNECT).
7. Run the BSC6900 MML command ADD MTP3RT (CME single configuration:
batch modification center: not supported) to add an MTP3 route. In this step, set
DSP index to the DSP index set in 6 and Signalling link set index to the
8. Run the BSC6900 MML command ADD GCNNODE (CME single configuration:
GSM Global Configuration Express > BSC Basic Configuration > GSM CN
Node; CME batch modification center: not supported) to add a CN node. In this
step, set DSP index to the DSP index set in 6.
– IP transmission
1. Run the BSC6900 MML command ADD ETHIP (CME single configuration:
Abis Configuration Express > IP Transport > Ethernet Port IP Address; CME
batch modification center: not supported) to add an IP address for an Ethernet port
or Run the BSC6900 MML command ADD ETHTRKIP (CME single
Address; CME batch modification center: not supported) to add an IP address for
a trunk group.
2. Optional: Run the BSC6900 MML command ADD DEVIP (CME single
configuration: Abis Configuration Express > IP Transport > Device IP
Address; CME batch modification center: not supported) to add a device IP
address for a board.
Entity; CME batch modification center: not supported) to add an M3UA local
entity.

GBSS14.0
4. Run the BSC6900 MML command ADD SCTPLNK (CME single configuration:
A Configuration Express > IP Transport > SCTP Link; CME batch
modification center: not supported) to add an SCTP link.
DPU; CME batch modification center: not supported) to add the MGW as the
signaling point code of the MGW, DSP type to STP function switch, Link Bear
type to M3UA, and Adjacent flag to YES(DIRECT_CONNECT).
6. Run the BSC6900 MML command ADD M3DE (CME single configuration:
GSM Global Configuration Express > BSC Basic Configuration > M3UA
Destination Entity; CME batch modification center: not supported) to add an
M3UA destination entity. In this step, set Local entity No. to the M3UA Local
entity No. set in 3, DSP index to the DSP index set in 5.
7. Run the BSC6900 MML command ADD M3LKS (CME single configuration:
Link Set; CME batch modification center: not supported) to add an M3UA
signaling link set. In this step, set Destination entity No. to the Destination entity
No. set in 6.
8. Run the BSC6900 MML command ADD M3LNK (CME single configuration:
Link Set; CME batch modification center: not supported) to add an M3UA link.
In this step, set Signalling link set index to the Signalling link set index set in
7, and set Subrack No., Slot No., and SCTP link No. to the Subrack No., Slot
No., and SCTP link No. set in 4.
Configuration Express > IP Transport > M3UA Route; CME batch
modification center: not supported) to add an M3UA route. In this step, set
Destination entity No. to the Destination entity No. set in 6 and Signalling link
set index to the Signalling link set index set in 7.
DPU; CME batch modification center: not supported) to add the MSC as the
signaling point code of the MSC, DSP type to A, Link Bear type to M3UA, and
Adjacent flag to NO(NO_DIRECT_CONNECT).
11. Run the BSC6900 MML command ADD M3DE (CME single configuration:
Destination Entity; CME batch modification center: not supported) to add an
M3UA destination entity. In this step, set Local entity No. to the M3UA Local
entity No. set in 3, DSP index to the DSP index set in 10.
modification center: not supported) to add an M3UA route. In this step, set
1. Run the BSC6900 MML command DSP N7DPC to check that SCCP DSP state is
set to Accessible.

GBSS14.0
– TDM transmission
1. Run the BSC6900 MML command RMV GCNNODE (CME single
Configuration > GSM CN Node; CME batch modification center: not supported)
to remove the CN node.
2. Run the BSC6900 MML command RMV MTP3RT (CME single configuration:
batch modification center: not supported) to remove the MTP3 route. In this step,
set DSP index to the DSP index set in 6 and Signalling link set index to the
3. Run the BSC6900 MML command RMV N7DPC (CME single configuration:
DPU; CME batch modification center: not supported) to remove the DPC of the
MSC.
4. Run the BSC6900 MML command RMV MTP3RT (CME single configuration:
batch modification center: not supported) to remove the MTP3 route. In this step,
set DSP index to the DSP index set in 2 and Signalling link set index to the
5. Run the BSC6900 MML command RMV MTP3LNK (CME single configuration:
MTP3 Signalling Link; CME batch modification center: not supported) to remove
the MTP3 link from the link set. In this step, set Signalling link set index to the
6. Run the BSC6900 MML command RMV MTP3LKS (CME single configuration:
MTP3 Signalling Link Set; CME batch modification center: not supported) to
remove the MTP3 link set. In this step, set Signalling link set index to the
SIGLKSX set in 3.
MGW.
– IP transmission
1. Run the BSC6900 MML command RMV M3RT (CME single configuration: A
modification center: not supported) to remove the M3UA route. In this step, set
2. Run the BSC6900 MML command RMV M3DE (CME single configuration:
Destination Entity; CME batch modification center: not supported) to remove the
M3UA destination entity. In this step, set Destination entity No. to the
Destination entity No. set in 11.
MSC.

GBSS14.0
4. Run the BSC6900 MML command RMV M3RT (CME single configuration: A
modification center: not supported) to remove the M3UA route. In this step, set
5. Run the BSC6900 MML command RMV M3LNK (CME single configuration:
Link Set; CME batch modification center: not supported) to remove the M3UA
link from the link set. In this step, set Signalling link set index to the Signalling
link set index set in 7.
6. Run the BSC6900 MML command RMV M3LKS (CME single configuration:
Link Set; CME batch modification center: not supported) to remove the M3UA
signaling link set. In this step, set Destination entity No. to the Destination entity
No. set in 6.
7. Run the BSC6900 MML command RMV M3DE (CME single configuration:
Destination Entity; CME batch modification center: not supported) to remove the
M3UA destination entity. In this step, set Destination entity No. to the
Destination entity No. set in 6.
MGW.
9. Run the BSC6900 MML command RMV SCTPLNK (CME single configuration:
A Configuration Express > IP Transport > SCTP Link; CME batch
modification center: not supported) to remove the SCTP link.
10. Run the BSC6900 MML command RMV M3LE (CME single configuration:
Local Entity; CME batch modification center: not supported) to remove the
M3UA local entity.
11. Optional: Run the BSC6900 MML command RMV DEVIP (CME single
configuration: Abis Configuration Express > IP Transport > Device IP
Address; CME batch modification center: not supported) to remove the device IP
address from the board.
12. Run the BSC6900 MML command RMV ETHIP (CME single configuration:
Abis Configuration Express > IP Transport > Ethernet Port IP Address; CME
batch modification center: not supported) to remove the IP address from the
Ethernet port or Run the BSC6900 MML command RMV ETHTRKIP (CME
single configuration: Abis Configuration Express > IP Transport > Trunk IP
Address; CME batch modification center: not supported) to remove the IP address
from the trunk group.
----End
Example
//Activating Signaling Transport Point (STP)
//TDM transmission
ADD OPC: NAME="test", SPX=1, NI=NAT, SPCBITS=BIT14, SPDF=WNF, SPC=260;
ADD N7DPC: NAME="MGW", DPX=1, SPX=1, SPDF=WNF, DPC=270, DPCT=STP,
BEARTYPE=MTP3, NEIGHBOR=YES;

GBSS14.0
ADD MTP3LKS: SIGLKSX=1, DPX=1, NAME="MGWMTP3LKS";

ADD MTP3LNK: SIGLKSX=1, SIGSLC=1, SRN=1, SN=0, TCMODE=SEPERATE_PRINCIPAL,
ATERIDX=0, ATERMASK=TS16-0, ASRN=3, ASN=18, MTP2LNKN=1, APN=0,
ATSMASK=TS16-0, LKTATE=64K, NAME="MTP3LNKS1_1";
ADD MTP3RT: DPX=1, SIGLKSX=1, NAME="MGWRT";
ADD N7DPC: NAME="MSC", DPX=2, SPX=1, SPDF=WNF, DPC=280, DPCT=A,
BEARTYPE=MTP3, NEIGHBOR=NO;
ADD MTP3RT: DPX=2, SIGLKSX=1, NAME="MSCRT";
ADD GCNNODE: CNNODEIDX=1, DPX=2, DPCGIDX=1, OPNAME="share", CNID=2,
DFDPC=YES, ATransMode=TDM;
//IP transmission
MASK="255.255.255.0";
ADD ETHTRKIP: SRN=1, SN=0, TRKN=0, IPINDEX=0, IPADDR="9.9.9.9",
MASK="255.255.255.0";
ADD M3LE: LENO=1, SPX=1, ENTITYT= M3UA_IPSP, NAME="LOCALBSC";
ADD SCTPLNK: SRN=1, SN=0, SCTPLNKN=100, MODE=CLIENT, APP=M3UA,
LOCIP1="172.17.15.253", PEERIP1="172.17.12.253", PEERPN=2905,
ADD N7DPC: NAME="MGW", DPX=1, SPX=1, SPDF=WNF, DPC=270, DPCT=STP,
BEARTYPE=M3UA, NEIGHBOR=YES;
ADD M3DE: DENO=1, LENO=1, DPX=1, ENTITYT=M3UA_IPSP, NAME="MGW";
ADD M3LKS: SIGLKSX=1, DENO=1, WKMODE=M3UA_IPSP, NAME="MGWLKS";
ADD M3LNK: SIGLKSX=1, SIGLNKID=1, SRN=1, SN=0, SCTPLNKN=100,
NAME="MGWLNK";
ADD M3RT: DENO=1, SIGLKSX=1, NAME="MGWM3RT";
ADD N7DPC: NAME="MSC", DPX=2, SPX=1, SPDF=WNF, DPC=280, DPCT=A,
BEARTYPE=M3UA, NEIGHBOR=NO;
ADD M3DE: DENO=2, LENO=1, DPX=2, ENTITYT=M3UA_IPSP, NAME="MSCM3DE";
ADD M3RT: DENO=2, SIGLKSX=1, NAME="MSCM3RT";
//Verifying Signaling Transport Point (STP)
DSP N7DPC:;
//Deactivating Signaling Transport Point (STP)
//TDM transmission
RMV GCNNODE: CNNODEIDX=1;
RMV MTP3RT: DPX=2, SIGLKSX=1;
RMV N7DPC: DPX=2;
RMV MTP3LNK: SIGLKSX=1, SIGSLC=1;
RMV MTP3LKS: SIGLKSX=1;
RMV N7DPC: DPX=1;
//IP transmission
RMV M3RT: DENO=2, SIGLKSX=1;
RMV M3DE: DENO=2;
RMV N7DPC: DPX=2;
RMV M3RT: DENO=1, SIGLKSX=1;
RMV M3LNK: SIGLKSX=1, SIGLNKID=1;
RMV M3LKS: SIGLKSX=1;
RMV M3DE: DENO=1;
RMV N7DPC: DPX=1;
RMV SCTPLNK: SRN=1, SN=0, SCTPLNKN=100;
RMV M3LE: LENO=1;
RMV DEVIP: IPADDR="10.171.35.123";
RMV ETHIP: SRN=1, SN=0, PN=0, IPINDEX=0;
RMV ETHTRKIP: SRN=1, SN=0, TRKN=0, IPINDEX=0;

GBSS14.0
Feature Activation Guide 27 Configuring 14-Digit Signaling Point Code
27 Configuring 14-Digit Signaling Point

Code
14-Digit Signaling Point Code.
Prerequisites
l License
l Others
– The CN supports this feature.
Context
Huawei GBSS can be connected to the MSC through the No.7 signaling system. The No.7
signaling system adopts the coding scheme in the 14-bit format. The signaling point code consists
of three sub-fields: sub-field for identifying the world geographical zone where the network is
located; sub-field for identifying the geographical area or network within a specific world zone;
sub-field for identifying the signaling point within a specific geographical area or network.
Procedure
1. At a newly deployed site, Run the BSC6900 MML command ADD OPC (CME single
configuration: GSM Global Configuration Express > BSC Basic Configuration >
OSP; CME batch modification center: not supported) to add an Originating Signaling
Point (OSP). In this step, set OSP code bits to BIT14(BIT14).
2. If the OSPs in non-14-bit format have been configured, Run the BSC6900 MML
command RMV OPC (CME single configuration: GSM Global Configuration
Express > BSC Basic Configuration > OSP; CME batch modification center: not
supported) to remove all the OSPs, and then proceed with Step 1.

GBSS14.0
Feature Activation Guide 27 Configuring 14-Digit Signaling Point Code
NOTE
A Signaling Point Code (SPC) must be unique in the signaling network and cannot be
0.BSC6900 does not support configuration of OSPs with different number of bits.
1. Run the BSC6900 MML command LST OPC to check that OSPs are in the 14-bit
format.
1. Run the BSC6900 MML command RMV OPC (CME single configuration: GSM
modification center: not supported) to remove all configured OSPs.
----End
Example
//Activating 14-Digit Signaling Point Code
ADD OPC: NAME="test", SPX=1, NI=NAT, SPCBITS=BIT14, SPDF=WNF, SPC=H'2cc7;
//Verifying 14-Digit Signaling Point Code
LST OPC:;
//Deactivating 14-Digit Signaling Point Code
RMV OPC: SPX=1;

GBSS14.0
Feature Activation Guide 28 Configuring Discontinuous Reception (DRX)
28 Configuring Discontinuous Reception

(DRX)
Discontinuous Reception (DRX).
Prerequisites
– This feature does not depend on the hardware.
l License
– The BCCH, SDCCH, and TCHs have been configured in the test cell.
Context
DRX increases the call duration and standby time of an MS.
Each MS is mapped to a paging group, and each paging group is mapped to a paging sub-channel
in the serving cell. In idle mode, the MS detects the paging messages broadcast by the system
only on the mapped paging sub-channel. The MS blocks other paging sub-channels by powering
off hardware, such as the receiver. This also saves power.
The configuration of a BTS3012 in TDM mode is taken as an example.
Procedure
Batches). In this step, set CCCH Blocks Reserved for AGCH to 2 and Multi-
Frames in a Cycle on the Paging CH to 2_M_PERIOD(2 Multiframe Period).

GBSS14.0
Feature Activation Guide 28 Configuring Discontinuous Reception (DRX)
1. Run the BSC6900 MML command SND GCELLSYSMSG to forcibly send the
system message to the test cell.
2. Enable an Abis Interface CS Trace task, then select RSL in the test cell.
3. Check the messages with the type of BCCH Information over the Abis interface for
the one whose system-info-type is system-information-3. In the IE control-
channel-description of this message, if bs-ag-blks-res (CCCH Blocks Reserved
for AGCH) is 2 and bs-pa-mfrms (Multi-Frames in a Cycle on the Paging CH) is
0, the system message is correct.
4. Use a MS to make a call to another MS (assume that the IMSI of the called MS is
"M"), and ensure that the call is set up successfully.
5. Check the CS message of the Abis Cell Pack Page Command type over the Abis
interface. If the IE cs-paging-group in this message is M%1000%14%14, the paging
group contained in the paging message is consistent with the settings in the system
message. In this case, the MS can implement DRX by monitoring the paging sub-
channel.
NOTE
"%" in M%1000%14%14 indicates the MOD operation, and the group number is in decimal
format.
----End
Example
SET GCELLIDLEBASIC: IDTYPE=BYID, CELLID=1024, BSAGBLKSRES=2,
BSPAMFRAMS=2_M_PERIOD;
SND GCELLSYSMSG: IDTYPE=BYID, CELLID=1024;

GBSS14.0
Feature Activation Guide 29 Configuring BTS Power Management
29 Configuring BTS Power Management
BTS Power Management.
Prerequisites
l License
Context
BTS power management enables the BTS to allocate load dynamically based on the actual power
situation, thereby prolonging the working time of the BTS.
Power management is applicable to the following scenarios:
l No mains supply
– Soft shutdown: The BTS automatically blocks all TCH TRXs except the BCCH TRX.
– Hard shutdown: When the battery capacity drops to a predefined threshold value, the
BTS automatically shuts down all TRXs.
l Unfavorable operating environment
– When the temperature inside a BTS cabinet exceeds a predefined threshold value, the
BTS shuts down PAs for some TRXs.
– When critical faults occur on a TRX, for example, the VSWR value far exceeds the
limit, the BTS shuts down the TRX.
Procedure
1. Run the BSC6900 MML command SET BTSAPMUBP (CME single configuration:
BTS Device Panel > Right click PMU Board > Properties > APMU/PMU(BTS
That Support SingleRAN) Board Parameters; CME batch modification center: not

GBSS14.0
Feature Activation Guide 29 Configuring BTS Power Management
supported). In this step, set Board Parameter Configuration Enabled to YES

(YES) and power management parameters to appropriate values.
1. Run the BSC6900 MML command LST BTSAPMUBP to query the value of Board
Parameter Configuration Enabled.
Expected result: Board Parameter Configuration Enabled is set to YES, and power
management parameters are set based on configurations.
1. Run the BSC6900 MML command SET BTSAPMUBP (CME single configuration:
BTS Device Panel > Right click PMU Board > Properties > APMU/PMU(BTS
That Support SingleRAN) Board Parameters; CME batch modification center: not
supported). In this step, set Board Parameter Configuration Enabled to NO(NO).
----End
Example
//Activating BTS Power Management
SET BTSAPMUBP: IDTYPE=BYID, BTSID=2, CN=0, SRN=7, SN=0, CFGFLAG=YES,
PTYPE=APM30, HTSDF=ENABLE;
//Verifying BTS Power Management
LST BTSAPMUBP: IDTYPE=BYID, BTSID=2, CN=0, SRN=7, SN=0;
//Deactivating BTS Power Management
SET BTSAPMUBP: IDTYPE=BYID, BTSID=2, CN=0, SRN=7, SN=0, CFGFLAG=NO;

GBSS14.0
Feature Activation Guide 30 Configuring Enhanced Power Control Algorithm
30 Configuring Enhanced Power Control

Algorithm
Enhanced Power Control Algorithm.
Prerequisites
l License
– The BSC to which the test cell belongs is connected to the M2000, and cell-level
counters can be retrieved on the M2000.
Context
Enhanced power control algorithm refers to HUAWEI II power control algorithm.
Power control is a process in which the BSS controls MS or BTS transmit power. Without
affecting the speech quality, power control reduces the interference in the entire network and
decreases power consumption. Power control mainly applies to the network with tight frequency
reuse, high traffic volume, or strong interference. In the GSM network, power control can be
separately performed on the uplink and downlink. It can also be performed on each MS.
Procedure
1. Run the BSC6900 MML command SET GCELLPWRBASIC (CME single
configuration: Cell Configuration Express > Power Control > Basic Parameters
for Power Control of Cell; CME batch modification center: 3.20 Modifying GSM
Cell Parameters in Batches). In this step, set Power Control Switch to PWR2
(Power control II).

GBSS14.0
2. Run the BSC6900 MML command SET GCELLPWR2 (CME single configuration:
Cell Configuration Express > Power Control > Parameters for Power Control II
Batches). In this step, set MR. Compensation Allowed to YES(Yes), and set AMR
MR. Compensation Allowed to YES(Yes). In addition, adjust Huawei II power
control parameters or set them to their default values.
3. Optional: Run the BSC6900 MML command SET GCELLCCCH (CME single
configuration: Cell Configuration Express > Idle Mode > Common Control
Cell Parameters in Batches) to improve the effect of handover and power control
when the BCCH participates in baseband frequency hopping. In this step, set
PWRC to YES(Yes). Run the BSC6900 MML command SET GCELLOTHEXT
(CME single configuration: Cell Configuration Express > Other Attributes >
GSM Cell Parameters in Batches). In this step, set Power Control and Handover
CMP CON Sw to YES(Yes).
1. Configure two cells, cell 0 and cell 1, on the BSC6900 and set the frequencies of the
BCCH TRXs of the two cells as non co-channel or adjacent-channel frequencies while
the frequencies of the non-BCCH TRXs as co-channel or adjacent-channel
frequencies.
2. Retrieve the following counters related to cell 0 on the M2000.
Table 30-1 Counters for verifying HUAWEI II power control
Measurement Unit Counter Name
Measurement of Power Average MS Power Level of Non-AMR Call

Control Messages in MR
per Cell Average BTS Power Level of Non-AMR Call
Ratio of Maximum Downlink Power Duration (%)
Ratio of Maximum Uplink Power Duration (%)
Mean Strength of Downlink Signals
Mean Strength of Uplink Signals
Mean Quality of Downlink Signals
Mean Quality of Uplink Signals
Interference Band Mean Number of SDCCHs in Interference Band 1

Measurement per TRX
Mean Number of SDCCHs in Interference Band 2
Mean Number of TCHFs in Interference Band 1

GBSS14.0
Mean Number of TCHHs in Interference Band 1
Receive Quality Number of MRs on Uplink TCHF (Mean Receive

Measurement per TRX Quality Rank 0)
Number of MRs on Uplink TCHF (Mean Receive

Quality Rank 1)

Quality Rank 2)

Quality Rank 3)

Quality Rank 4)

Quality Rank 5)

Quality Rank 6)

Quality Rank 7)
Number of MRs on Downlink TCHF (Mean Receive

Quality Rank 0)

Quality Rank 1)

Quality Rank 2)

Quality Rank 3)

Quality Rank 4)

Quality Rank 5)

GBSS14.0

Quality Rank 6)

Quality Rank 7)
Number of MRs on Uplink TCHH (Mean Receive

Quality Rank 0)

Quality Rank 1)

Quality Rank 2)

Quality Rank 3)

Quality Rank 4)

Quality Rank 5)

Quality Rank 6)

Quality Rank 7)
Number of MRs on Downlink TCHH (Mean Receive

Quality Rank 0)

Quality Rank 1)

Quality Rank 2)

Quality Rank 3)

Quality Rank 4)

Quality Rank 5)

Quality Rank 6)

Quality Rank 7)

GBSS14.0
3. Run the BSC6900 MML command SET GCELLBASICPARA. In this step, set UL
PC Allowed and DL PC Allowed of cell 0 and cell 1 to NO(No).
4. Initiate a large number of calls in cell 0 and cell 1.
5. Check the counters for one hour and save them.
6. Run the BSC6900 MML command SET GCELLBASICPARA. In this step, set UL
PC Allowed and DL PC Allowed of cell 0 and cell 1 to YES(Yes).
7. Run the BSC6900 MML command SET GCELLPWRBASIC. In this step, set
Power Control Switch of cell 0 and cell 1 to PWR2(Power control II).
8. Run the BSC6900 MML command SET GCELLPWR2. In this step, set MR.
Compensation Allowed to YES(Yes), and set AMR MR. Compensation Allowed
to YES(Yes) for cell 0 and cell 1.
11. Compare the measured counter results obtained from Step 10 and Step 5.
Expected result: For the counters related to power level, the power level obtained in
Step 10 is smaller than that obtained in Step 5. For the counters related to interference
band, the value of a counter with lower quality rank obtained in Step 10 is larger than
that obtained in Step 5. For the counters related to receive quality, the value of a
counter with lower quality rank obtained in Step 10 is larger than that obtained in
Step 5.
----End
Example
//Activating HUAWEI II Power Control Algorithm
SET GCELLPWRBASIC: IDTYPE=BYID, CELLID=0, PWRCTRLSW=PWR2;
SET GCELLPWR2: IDTYPE=BYID, CELLID=0, MRCOMPREG=YES, AMRMRCOMPREG=YES;

GBSS14.0
Feature Activation Guide 31 Configuring DTMF Downlink Message Filter
31 Configuring DTMF Downlink Message

Filter
DTMF Downlink Message Filter.
Prerequisites
l License
– A over TDM transmission is used.
Context
CAUTION
After this feature is configured, the processing capability of DSPs is decreased by about 10%.
This feature shields the downlink DTMF messages on the user plane and control plane of the A
interface. In this case, after the call is set up, the called cell phone will not receive DTMF signals.
By shielding downlink DTMF signals, this feature enhances the GBSS network security.
Procedure

GBSS14.0
Feature Activation Guide 31 Configuring DTMF Downlink Message Filter
center: 3.17 Modifying GBSC Parameters in Batches) with Downlink DTMF

Signaling Processing Allowed set to OPEN(Open).
1. Use an MS to make a call to another MS. During the call, press a key on either MS.
Expected result: The peer end cannot hear clear DTMF tones but silence.
2. Run the BSC6900 MML command SET OTHSOFTPARA with
DLDTMFPRCSW set to CLOSE(Close).
3. Repeat Step 1.
Expected result: The peer end hears clear DTMF tones.
center: 3.17 Modifying GBSC Parameters in Batches) with Downlink DTMF
Signaling Processing Allowed set to CLOSE(Close).
----End
Example
//Activating DTMF downlink message filter
SET OTHSOFTPARA: DLDTMFPRCSW=OPEN;
//Deactivating DTMF downlink message filter

SET OTHSOFTPARA: DLDTMFPRCSW=CLOSE;

GBSS14.0
Feature Activation Guide 32 Configuring High Speed Signaling
32 Configuring High Speed Signaling
High Speed Signaling.
Prerequisites
– This feature is mutually exclusive to the feature GBFD-118602 A over IP or
GBFD-118622 A IP over E1/T1.
l Dependency on License
– The license for this feature is activated.
l Other prerequisites
– The MSC supports high-speed signaling.
– TDM transmission is applied over the A interface.
– The EIUa/OIUa board is configured.
– The OPC and DPC are configured.
Context
This feature is characterized by:
l High capacity
The BSC is not limited by the capacity of a single signaling point when narrowband
signaling is used. This feature not only meets the requirements for signaling link bandwidth
of large capacity processing capability but also saves operators' signaling resources and
simplifies network topology.
l Flexible bandwidth configuration
The high-speed signaling link bandwidth is N x 64 kbit/s. Where, N ranges from 1 to 31.
Operators can flexibly configure the high-speed signaling link bandwidth based on the
traffic volume to reduce the transmission cost.
l Short delay

GBSS14.0
High-speed signaling links carry signaling data using multiple timeslots. This reduces the
transmission delay of signaling data over the A interface especially in off-peak hours,
reducing the call setup duration.
Generally, high-speed signaling links are used for terrestrial transmission. Satellite transmission
does not use high-speed signaling links.
WARNING
Reconfiguring the signaling link over the A interface will disrupt the services of the BSC6900.
Therefore, perform the operation when the traffic is light, for example, in the early morning.
The whole process (including board restart) takes about 10 minutes.
Procedure
1. Run the BSC6900 MML command ADD AE1T1 (CME single configuration: A
Configuration Express > TDM Transport > A Interface E1/T1; CME batch
modification center: not supported) to add an E1/T1 on the A interface.
2. Run the BSC6900 MML command ADD MTP3LKS (CME single configuration: A
Configuration Express > TDM Transport > MTP3 Signalling Link Set > MTP3
Signalling Link Set; CME batch modification center: not supported) to add an MTP3
signaling link set.
3. Run the BSC6900 MML command ADD MTP3LNK (CME single configuration: A
Signalling Link; CME batch modification center: not supported). In this step, set
DSP bear type to MTP2(MTP2) and Link rate type to 2M(2Mbit/s).
NOTE
In BM/TC separated mode where the TCS is configured remotely, you are advised to set Ater
Mask of the MTP3 signaling links on the main TCS to values rather than TS1.
4. Run the BSC6900 MML command ADD MTP3RT (CME single configuration: A
Configuration Express > TDM Transport > MTP3 Signalling Route; CME batch
modification center: not supported) to add an MTP3 route.
1. Run the BSC6900 MML command LST MTP3LNK to query the information about
the MTP3 signaling link.
Expected result: The value of Link rate type is 2Mbit/s.

A Configuration Express > TDM Transport > MTP3 Signalling Link Set > MTP3
Signalling Link; CME batch modification center: not supported). In this step, set
Signalling link set index and Signalling link code.
2. Run the BSC6900 MML command RMV MTP3RT (CME single configuration: A
modification center: not supported). In this step, set DSP index and Signalling link
set index.

GBSS14.0
3. Run the BSC6900 MML command RMV MTP3LKS (CME single configuration: A
Signalling Link Set; CME batch modification center: not supported). In this step, set
Signalling link set index.
4. Run the BSC6900 MML command RMV AE1T1 (CME single configuration: A
modification center: not supported) to remove an E1/T1 on the A interface.
----End
Example
/*Activation procedure*/
//Configuring an E1/T1 over the A Interface
ADD AE1T1: SRN=0, SN=12, PN=1, OPCIDX=0, ALLTSTYPE=ALLCIC,
BSCFLAG=MAINBSC, STCIC=0;
//Configuring an MTP3 signaling link set
ADD MTP3LKS: SIGLKSX=0, DPX=0, NAME="123";
//Configuring an MTP3 signaling link
ADD MTP3LNK: SIGLKSX=0, SIGSLC=1, BEARTYPE=MTP2,
TCMODE=SEPERATE_BSC_INTERFACE, ATERIDX=1,
ATERMASK=TS1-1&TS2-1&TS3-1&TS4-1&TS5-1&TS6-1&TS7-1&TS8-1&TS9-1&TS10-1&TS1
1-1&TS12-1&TS13-1&TS14-1&TS15-1&TS16-1&TS17-1&TS18-1&TS19-1&TS20-1&TS21-1
&TS22-1&TS23-1&TS24-1&TS25-1&TS26-1&TS27-1&TS28-1&TS29-1&TS30-1&TS31-1,
MTP2LNKN=1, LKTATE=2M, NAME="123";
//Adding an MTP3 signaling route
ADD MTP3RT: DPX=0, SIGLKSX=0, NAME="111";
/*Deactivation procedure*/
//Removing an MTP3 signaling link
//Removing an MTP3 signaling route
//Removing an MTP3 signaling link set
RMV MTP3LKS: SIGLKSX=0;
//Removing an E1/T1 over the A interface
RMV AE1T1: SRN=0, SN=12, PN=1;

GBSS14.0
Feature Activation Guide 33 Configuring Guaranteed Emergency Call
33 Configuring Guaranteed Emergency Call
Guaranteed Emergency Call.
Prerequisites
l License
l Others Prerequisites
– The MSC supports the TCH preemption function.
Context
The Guaranteed Emergency Call feature is introduced to increase the setup success rate of
emergency calls to the greatest extent. Therefore, normal communications are ensured in disaster
relief activities.
This feature has the following characteristics:
l Emergency calls are preferentially assigned full-rate TCHs (TCHFs) in the immediate
assignment phase.
l The system reserves TCHFs for the MSs making emergency calls.
l The MSs making emergency calls preempt the channels occupied by low-priority calls.
Without this feature, the TCHs occupied by emergency calls can be preempted by high-priority
calls. After this feature is enabled, emergency calls can preempt the TCHs that are occupied by
other common calls and can be preempted when there is no idle TCH. Emergency calls, however,
cannot preempt the TCHs occupied by other emergency calls.

GBSS14.0
Procedure
1. Run the BSC6900 MML command LST GCELLCCAD (CME single configuration:
Cell Configuration Express > Call Control > Call Control Advanced Parameters
of Cell) to query the value of Priority of Emergency Call. If the value of Priority
of Emergency Call is 15, this feature is not activated.
2. Run the BSC6900 MML command SET GCELLCCAD (CME single configuration:
Batches). In this step, set Priority of Emergency Call to an appropriate value, for
example, 1.
Modifying GSM Cell Parameters in Batches). In this step, set Max Channel Num
Reserved for EC to an appropriate value, for example, 2.
Batches). In this step, set Emergency Call Preemption Permitted to ON(On).
5. (Optional) Run the BSC6900 MML command SET GCELLTMR (CME single
configuration: Cell Configuration Express > Timer Attributes > Timer
Parameters in Batches). In this step, set Timer of Reserved TCH for EMC to an
appropriate value, for example, 15.
1. Run the BSC6900 MML command LST GCELLCCAD to query the value of
Priority of Emergency Call.
Expected result: The value of Priority of Emergency Call is 1.
2. Run the BSC6900 MML command LST GCELLCHMGBASIC to query the value
of Max Channel Num Reserved for EC.
Expected result: The value of Max Channel Num Reserved for EC is 2.
3. Run the BSC6900 MML command LST GCELLCCAD to query the value of
Emergency Call Preemption Permitted.
Expected result: The value of Emergency Call Preemption Permitted is ON(On).
4. (Optional) Run the BSC6900 MML command LST GCELLTMR to query the value
of Timer of Reserved TCH for EMC.
Expected result: The value of Timer of Reserved TCH for EMC is 15.
5. Use an MS to make an emergency call.
All the TCHs in the cell are occupied by common calls and there are no idle TCHs.
There exists a call whose priority is lower than the priority of the emergency call and
the channel resources of the call can be preempted.
Expected result: A call in the cell is released because its resources are preempted.
6. The MS makes the emergency call successfully. An SDCCH is assigned in the
immediate assignment phase and a TCHF is assigned in the assignment phase.

GBSS14.0
Batches). In this step, set Priority of Emergency Call to 15.
of Cell) to query the value of Priority of Emergency Call.
Expected result: The value of Priority of Emergency Call is 15.
Batches). In this step, set Emergency Call Preemption Permitted to OFF(Off).
of Cell) to query the value of Emergency Call Preemption Permitted.
Expected result: The value of Emergency Call Preemption Permitted is OFF
(Off).
----End
Example
//Activating Guaranteed Emergency Call
LST GCELLCCAD: IDTYPE=BYID, BTSID=1, CELLID=1;
SET GCELLCCAD: IDTYPE=BYID, CELLID=1, EMCPRILV=1;
SET GCELLCHMGBASIC: IDTYPE=BYID, CELLID=1, RSVCHMFORECNUM=2;
SET GCELLCCAD: IDTYPE=BYID, CELLID=1, PREEMPTIONPERMIT=ON;
SET GCELLTMR: IDTYPE=BYID, CELLID=1, WAITRESVCHANREFRESHTIMER=15;
//Deactivating Guaranteed Emergency Call
SET GCELLCCAD: IDTYPE=BYID, CELLID=1, EMCPRILV=15;
SET GCELLCCAD: IDTYPE=BYID, CELLID=1, PREEMPTIONPERMIT=OFF;

GBSS14.0
Feature Activation Guide 34 Configuring License Control for Urgency
34 Configuring License Control for Urgency
License Control for Urgency. (This feature cannot be configured using the CME. )
Prerequisites
l License
Context
CAUTION
This feature is enabled only in scenarios where the traffic volume increases abruptly, for
example, in a disaster.
This function can be performed only three times for each R version and it is valid only in seven
days since it is enabled.
After this feature is enabled, the network capacity can reach the maximum supported by the
hardware.
Procedure
1. Run the BSC6900 MML command SET LICENSECTRL. In this step, set Bfd
Protocol Switch to ON(ON).
1. Run the BSC6900 MML command DSP LICUSAGE to check the resource items of
the license.

GBSS14.0
Feature Activation Guide 34 Configuring License Control for Urgency
The returned result shows that all the values of the resource items reach the maximum.
2. Run the BSC6900 MML command LST LICENSECTRL to query the setting of
Grace Protection Period Switch State.
Expected result: In the returned result, there are the settings of Remaining Grace
Protection Times and Remaining Grace Protection Days, and Grace Protection
Period Switch State is set to ON.
3. On the next day (later than 1 a.m.) after this feature is enabled, check whether the
event EVT-22812 Operation of Maximum License Capacity is reported by the alarm
console of BSC6900.
1. Run the BSC6900 MML command SET LICENSECTRL. In this step, set Bfd
Protocol Switch to OFF(OFF).
----End
Example
SET LICENSECTRL: SWITCH=ON;
SET LICENSECTRL: SWITCH=OFF;

GBSS14.0
Feature Activation Guide 35 Configuring HUAWEI III Power Control Algorithm
35 Configuring HUAWEI III Power Control

Algorithm
HUAWEI III Power Control Algorithm.
Prerequisites
– You are advised to use this feature together with the feature GBFD-118103 Network
Support SAIC.
l License
– The BSC to which the test cell belongs is connected to the M2000, and cell-level
counters can be retrieved on the M2000.
Context
Power control is a process in which the BSS controls MS or BTS transmit power. Without
affecting the speech quality, power control reduces the interference in the entire network and
decreases power consumption. Power control mainly applies to the network with tight frequency
reuse, high traffic volume, or strong interference. In the GSM network, power control can be
separately performed on the uplink and downlink. It can also be performed on each MS.
HUAWEI III power control algorithm enhances and optimizes the GBFD-110703 Enhanced
Power Control Algorithm feature in terms of the filtering algorithm, interpolation of the
measurement report, power control decision algorithm, and flexibility of threshold
configuration.
Procedure

GBSS14.0
Batches). In this step, set both UL PC Allowed and DL PC Allowed to YES(Yes).
(Power control III).
3. Run the BSC6900 MML command SET GCELLPWR3 (CME single configuration:
Cell Configuration Express > Power Control > Parameters for Power Control
III of Cell; CME batch modification center: 3.20 Modifying GSM Cell Parameters
in Batches). In this step, set Allow III Power Control For AMR to ON(Allowed),
set Allow III Power Control For Non-AMR to ON(Allowed), and set III Power
Control Optimized Enable to YES(Yes).
NOTE
l Allow III Power Control For AMR is set toOFF(Not Allowed) by default, Allow III
Power Control For Non-AMR is set to ON(Allowed) by default.
l By default, PC Step Calculation Optimization is set to NO (No). It can be set to YES
(Yes) as required to optimize the results of power control.
l Power control parameters need to be adjusted based on site requirements.
4. Optional: To improve the effect of handover and power control when the BCCH
participates in baseband frequency hopping, run the BSC6900 MML command SET
GCELLCCCH (CME single configuration: Cell Configuration Express > Idle
Mode > Common Control Channel Parameters of Cell; CME batch modification
center: 3.20 Modifying GSM Cell Parameters in Batches). In this step, set
PWRC to YES(Yes). Run the BSC6900 MML command SET GCELLOTHEXT
(CME single configuration: Cell Configuration Express > Other Attributes >
GSM Cell Parameters in Batches). In this step, set Power Control and Handover
CMP CON Sw to YES(Yes).
5. Optional: To activate 0.2 dB Power Control, run the BSC6900 MML command SET
GCELLPWR3 (CME single configuration: Cell Configuration Express > Power
Control > Parameters for Power Control III of Cell; CME batch modification
center: 3.20 Modifying GSM Cell Parameters in Batches). In this step, set 0.2dB
Power Control Enable to YES(Yes) and set 0.2 dB Power Control Optimization
to ON(On).
1. Configure two cells, cell 0 and cell 1, on the BSC6900 and set the frequencies of the
BCCH TRXs of the two cells as non co-channel or adjacent-channel frequencies while
the frequencies of the non-BCCH TRXs as co-channel or adjacent-channel
frequencies.
2. Retrieve the following counters related to cell 0 on the M2000.
Table 35-1 Counters for verifying HUAWEI III power control
Measurement of Power Average MS Power Level of Non-AMR Call

Control Messages in MR
per Cell Average BTS Power Level of Non-AMR Call

GBSS14.0
Ratio of Maximum Downlink Power Duration (%)
Ratio of Maximum Uplink Power Duration (%)
Mean Strength of Downlink Signals
Mean Strength of Uplink Signals
Mean Quality of Downlink Signals
Mean Quality of Uplink Signals
Interference Band Mean Number of SDCCHs in Interference Band 1

Measurement per TRX
Receive Quality Number of MRs on Uplink TCHF (Mean Receive

Measurement per TRX Quality Rank 0)

Quality Rank 1)

Quality Rank 2)

Quality Rank 3)

Quality Rank 4)

GBSS14.0

Quality Rank 5)

Quality Rank 6)

Quality Rank 7)

Quality Rank 0)

Quality Rank 1)

Quality Rank 2)

Quality Rank 3)

Quality Rank 4)

Quality Rank 5)

Quality Rank 6)

Quality Rank 7)

Quality Rank 0)

Quality Rank 1)

Quality Rank 2)

Quality Rank 3)

Quality Rank 4)

Quality Rank 5)

Quality Rank 6)

Quality Rank 7)

GBSS14.0

Quality Rank 0)

Quality Rank 1)

Quality Rank 2)

Quality Rank 3)

Quality Rank 4)

Quality Rank 5)

Quality Rank 6)

Quality Rank 7)
Power Control Switch of cell 0 and cell 1 to PWR2(Power control II).
4. Run the BSC6900 MML command LST GCELLPWRBASIC to query the setting
of Power Control Switch of cell 0 and cell 1.
Expected result: Power Control Switch is set to Power control II.
Power Control Switch of cell 0 and cell 1 to PWR3(Power control III).
8. Run the BSC6900 MML command LST GCELLPWRBASIC to query the setting
of Power Control Switch of cell 0 and cell 1.
Expected result: Power Control Switch is set to Power control III.
9. Run the BSC6900 MML command SET GCELLPWR3. In this step, set Allow III
Power Control For AMR to ON(Allowed), and set Allow III Power Control For
Non-AMR to ON(Allowed) for cell 0 and cell 1.
10. Run the BSC6900 MML command LST GCELLPWR3 to query the settings of
Allow III Power Control For AMR and Allow III Power Control For Non-
AMR for cell 0 and cell 1.
Expected result: Both Allow III Power Control For AMR and Allow III Power
Control For Non-AMR are set to ON(Allowed).
13. Compare the measured counter results obtained from Step 12 and Step 6.
Expected result: For the counters related to power level, the power level obtained in
Step 12 is smaller than that obtained in Step 6. For the counters related to interference

GBSS14.0
bands, the proportion of channels in low interference bands, which is obtained in Step
12, is greater than that obtained in Step 6. For the counters related to receive quality,
the value of a counter with lower quality rank obtained in Step 12 is greater than that
obtained in Step 6.
14. Optional: Run the BSC6900 MML command LST GCELLPWR3 to query the
settings of 0.2dB Power Control Enable and 0.2 dB Power Control
Optimization of cell 0 and cell 1.
Expected result: 0.2dB Power Control Enable is set to YES(Yes) and 0.2 dB Power
Control Optimization is set to ON(On).
15. Optional: Start tracing CS messages of a single MS in cell 0, and use the MS to initiate
a call.
16. Optional: Check the tracing result.
Expected result: The call is successfully initiated and the communication is normal.
In a BS Power Control message, the value of fine-pwr-ctrl is 1, and the value of fine-
pwr-ctrl-value is not the maximum value. In addition, the 0.2 dB power level is
reported in the measurement report. The BSC6900 sends BS Power Control messages
to the BTS even if the 0.2 dB power control steps in two BS Power Control messages
are different.
(Power control II).
2. Run the BSC6900 MML command LST GCELLPWRBASIC (CME single
for Power Control of Cell) to query the setting of Power Control Switch.
Expected result: Power Control Switch is set to PWR2(Power control II).
3. Optional: To deactivate the function of optimizing handover and power control when
the BCCH participates in baseband frequency hopping, run the BSC6900 MML
command SET GCELLCCCH (CME single configuration: Cell Configuration
Express > Idle Mode > Common Control Channel Parameters of Cell; CME batch
set PWRC to NO(No). Run the BSC6900 MML command SET
GCELLOTHEXT (CME single configuration: Cell Configuration Express >
Other Attributes > Extended Parameters of Cell; CME batch modification center:
3.20 Modifying GSM Cell Parameters in Batches). In this step, set Power Control
and Handover CMP CON Sw to NO(No).
4. Optional: To deactivate 0.2 dB Power Control, run the BSC6900 MML command
SET GCELLPWR3 (CME single configuration: Cell Configuration Express >
Power Control > Parameters for Power Control III of Cell; CME batch
set 0.2dB Power Control Enable to NO(No) and set 0.2 dB Power Control
Optimization to OFF(Off).
----End
Example
//Activating HUAWEI III Power Control Algorithm

GBSS14.0
SET GCELLPWR3: IDTYPE=BYID, CELLID=2,PWRCTRLOPTIMIZEDEN=YES,

AMRCALLPCALLOWED=ON, NONAMRCALLPCALLOWED=ON, PCSTEPOPT=YES;
//Deactivating HUAWEI III Power Control Algorithm
SET GCELLPWR3: IDTYPE=BYID, CELLID=2, PWRCTRLOPTIMIZEDEN=NO,
AMRCALLPCALLOWED=OFF, NONAMRCALLPCALLOWED=OFF, PCSTEPOPT=NO;

GBSS14.0
Feature Activation Guide 36 Configuring the satellite transmission on the Pb interface
36 Configuring the satellite transmission on

the Pb interface
Satellite Transmission over Pb Interface. (This feature cannot be configured using the CME. )
Prerequisites
l License
Context
l If terrestrial lines between the BSC and the external PCU cannot be installed or the
installation cost of the terrestrial lines is high, satellite transmission can be deployed on the
Pb interface.
l The transmission delay over the G-Abis interface of a satellite-capable cell is longer than
that over the G-Abis interface of an ordinary cell. If the same amount of data is transmitted
by these two types of cell, it takes longer time for the satellite-capable cell to wait for a
response message from the MS. Therefore, the transmission performance of a satellite-
capable cell is worse than that of an ordinary cell. Under the condition that the average
downlink rate of an MS is not affected, the network reduces the maximum number of
downlink PDCHs allocated to the MS so that the time required for the RLC sending window
to overflow is prolonged.
Procedure
1. Configure satellite transmission on the Pb interface on the LMT.
– Run the BSC6900 MML command ADD PBE1T1. In this step, set Transmission
Mode to SATEL(Satellite Transmission).

GBSS14.0
Feature Activation Guide 36 Configuring the satellite transmission on the Pb interface
NOTE
The value of Start PCIC must be a multiple of 128.

After satellite transmission is applied on the Pb E1 link, the Pb signaling link automatically
switches to the satellite transmission mode accordingly.
2. Configure satellite transmission on the Pb interface through PCU LocalWS.
– Run the mt gcell deactive<LCNo> command to deactivate a cell.
– Run the pcu add sattrans<LCNo> yes command to configure satellite
transmission for the cell.
– Run the mt gcell active <LCNo> command to activate the cell.
3. Optional: Run the BSC6900 MML command SET GCELLPSBASE. In this step,
set T3168 to 2000ms(2000ms), T3192 to 0ms(0ms), and BS_CV_MAX to 15.
1. Run the mt gcell deactive<LCNo> command to deactivate the cell.
2. Run the pcu add sattrans<LCNo> yes command to configure satellite transmission
for the cell.
3. Run the mt gcell active<LCNo> command to activate the cell.
4. Run the mt gcell show stat<LCNo> command to verify that the state of the cell is
UNBLOCK.
5. Use the MS to perform PS services. PS services are normally performed.
1. Disable satellite transmission on the Pb interface on the LMT.
– Run the BSC6900 MML command MOD PBE1T1. In this step, set Transmission
Mode to TRRS(Terrestrial Transmission).
2. Configure terrestrial transmission on the Pb interface through PCU LocalWS.
– Run the mt gcell deactive<LCNo> command to deactivate the cell.
– Run the pcu set sattrans<LCNo> no command to configure terrestrial
transmission for the cell.
– Run the mt gcell active <LCNo> command to activate the cell.
set T3168 to 500ms(500ms), T3192 to 500ms(500ms), and BS_CV_MAX to 10.
----End
Example
/*Activating Satellite Transmission over Pb Interface*/
ADD PBE1T1: SRN=0, SN=20, PN=0, PCUNO=0, SPCIC=0, TNMODE=SATEL;
/*Deactivating Satellite Transmission over Pb Interface*/
MOD PBE1T1: SRN=0, SN=20, PN=0, TNMODE=SATEL, OPMODE=MODRANGETS,
STARTTS=4, ENDTS=32, ALLTSTYPE=ALLCIC;

GBSS14.0
Feature Activation Guide 37 Configuring PDCH Dynamic Adjustment
37 Configuring PDCH Dynamic

Adjustment
PDCH Dynamic Adjustment.
Prerequisites
– The feature GBFD-114101 GPRS or GBFD-114201 EGPRS has been configured before
this feature is activated.
l License
– None
l Dependencies on Running Environment
– A built-in PCU is configured. A packet switched (PS) service processing board and the
Gb interface board are used.
l Requirements for Transmission Network
– None
l Requirements for Other NEs and Third-Party Devices
– The mobile station (MS) and core network (CN) supports PS services.
– A built-in PCU is configured. The Gb interface is configured. For details, see
Configuring the Gb Interface (over FR) and Configuring the Gb Interface (over IP).
– The transmission mode for the BTS is configured.
Context
l Type of PDCHs
PDCHs are divided into the following types based on the type of services they carry:
– Static PDCHs: PDCHs that carry only PS services.
– Dynamic PDCHs: Initially speech TCHFs. TCHFs and PDCHs can be converted into
each other dynamically.
l PDCH Dynamic Adjustment

GBSS14.0
Static PDCHs carry only PS services. Dynamic PDCHs are TCHFs when initially
configured. They can be converted into PDCHs if there are insufficient PS resources. On
the hand, PDCHs can be converted into TCHFs if there are insufficient CS resources.
Therefore, PDCH dynamic adjustment enhances the utility of channel resources based on
practical needs, reduces the complexity of configuring and maintaining PDCHs, and
reduces the impact of improper PDCH configuration on service performance.
l Data Preparation
Table 37-1 Configuring a cell that supports PS services

Parameter Parameter ID Parameter Setting Data
Name Source
GPRS GPRS If the operator requires that the cell Internal

supports only GPRS services, set planning
this parameter to
SupportAsInnPcu(Support as
built-in PCU).
EDGE EDGE If the operator requires that the cell Internal

supports both GPRS and EDGE planning
services, set GPRS to
SupportAsInnPcu(Support as
built-in PCU), then set this
parameter to YES(Yes).
Procedure
1. Configure dynamic PDCHs. Run the BSC6900 MML commandSET GTRXCHAN
(CME single configuration: TRX Configuration Express > Channel Type >
Channel Type; CME batch modification center: 3.22 Modifying GSM TRX
Parameters in Batches). In this step, set CHTYPE to TCHFR(TCH Full Rate) for
channels to be configured to dynamic PDCHs.
2. Optional: Activate the PDCH management algorithm optimization function. Run the
BSC6900 MML commandSET GCELLPSCHM (CME single configuration: Cell
Configuration Express > GPRS Attributes > GPRS Channel Management
Parameters of 2G Cell; CME batch modification center: 3.20 Modifying GSM Cell
Parameters in Batches) with PDCH Management Optimization set to ON(On).
3. Optional: Activate the GPRS channel priority type auto planning function. Run the
BSC6900 MML commandSET GCELLPSCHM (CME single configuration: Cell
Configuration Express > GPRS Attributes > GPRS Channel Management
Parameters in Batches) with GPRS Channel Priority Type Auto-Planning set to
ON(On).
If the cell is not a concentric cell, set Number of EGPRS Normal Channels, Number
of EGPRS Priority Channels, and Number of EGPRS Special Channels according
to the number of EGPRS normal channels, EGPRS priority channels, and EGPRS
special channels configured for the cell. Set Number of EGPRS Special Channels
(OL Subcell), EgprsPriChnumInn, and Number of EGPRS Normal Channels
(OL Subcell) to 0.

GBSS14.0
If the cell is a concentric cell, set Number of EGPRS Normal Channels, Number
of EGPRS Priority Channels, and Number of EGPRS Special Channels according
to the number of EGPRS normal channels, EGPRS priority channels, and EGPRS
special channels configured for the underlaid cell. Set Number of EGPRS Special
Channels (OL Subcell), EgprsPriChnumInn, and Number of EGPRS Normal
Channels (OL Subcell) according to the number of EGPRS normal channels, EGPRS
priority channels, and EGPRS special channels configured for the overlaid cell.
1. Verify PDCH dynamic adjustment.
Use an MS to perform download services. Monitor the channel status on the LMT.
The results show that some TCHFs are converted into PDCHs.
2. Optional: Verify the PDCH management algorithm optimization function.
Use several MSs to perform PS services. Monitor the channel status on the LMT. The
results show that dynamic PDCHs are distributed on a few TRXs.
3. Optional: Verify the GPRS channel priority type auto planning function.
Run the BSC6900 MML commandDSP CHNSTAT to query the status of channels
for a cell. The results for PDCH Channel Priority Type shows the optimized PDCH
type after auto planning.
1. Verify PDCH dynamic adjustment.
None
2. Optional: Verify the PDCH management algorithm optimization function.
Run the BSC6900 MML commandSET GCELLPSCHM (CME single
Modifying GSM Cell Parameters in Batches) with PDCH Management
Optimization set to OFF(Off).
3. Optional: Verify the GPRS channel priority type auto planning function.
Run the BSC6900 MML commandSET GCELLPSCHM (CME single
Modifying GSM Cell Parameters in Batches) with GPRS Channel Priority Type
Auto-Planning set to OFF(Off).
----End
Example
//Configuring dynamic PDCHs:
SET GTRXCHAN: IDTYPE=BYID, TRXID=901, CHNO=7, CHTYPE=TCHFR;
//Optional: Activating the PDCH management algorithm optimization
function:
SET GCELLPSCHM: IDTYPE=BYID, CELLID=0, EnPDAdminOpt=ON;
//Optional: Activating GPRS channel priority type auto planning function:
SET GCELLPSCHM: IDTYPE=BYID, CELLID=0, AutoGprsChPri=ON, EgprsSpeChnum=4,
EgprsPriChnum=8, EgprsNorChnum=18, EgprsSpeChnumInn=0,
EgprsPriChnumInn=0, EgprsNorChnumInn=0;
//Optional: Deactivating the PDCH management algorithm optimization
function:
SET GCELLPSCHM: IDTYPE=BYID, CELLID=0, EnPDAdminOpt=OFF;
//Optional: Deactivating GPRS channel priority type auto planning

GBSS14.0
function:
SET GCELLPSCHM: IDTYPE=BYID, CELLID=0, AutoGprsChPri=OFF;

GBSS14.0
Feature Activation Guide 38 Configuring Connection with TMA
38 Configuring Connection with TMA
Connection with TMA (Tower Mounted Amplifier). (This feature cannot be configured using
the CME. )
Prerequisites
l Hardware Dependencies for Common TMA
– The RRU3004 does not support the connection with a common TMA.
– The RRU3008 and RRU3908 support the connection with a common TMA.
– The GRFU and MRFU support the connection with a common TMA.
– The DRFU supports the connection with a common TMA through the GATM board.
l Hardware Dependencies for Smart TMA
– The 3012 series base stations do not support the configuration of the smart TMA.
– A 3900 or 3036 series base station with the GATM board does not support the
configuration of the smart TMA.
– A 3900 or 3036 series base station with the RXU board does not support the
configuration of the smart TMA in non-SRAN mode.
– An antenna device is numbered uniquely within a site. In addition, the device number
of a Remote Electrical Tilt (RET) and that of a TMA must be different within a site.
l License
Context
Installed on the tower top, the TMA is a device for amplifying uplink signals. As an optional
component of the antenna system, the TMA compensates for the feeder loss caused by a long
feeder to improve the uplink sensitivity and converge. In a network whose uplink coverage is
limited, the TMA can be installed to improve the receiver sensitivity and expand the cell radius,
reducing the number of BTSs and minimizing investments.
If a BTS is configured with the TMA, users must configure the BTS-related parameters based
on the actual RF antenna port, power supply mode, and TMA characteristics.

GBSS14.0
Procedure
l Activation Procedure for a Common TMA
1. Run the BSC6900 MML command SET BTSRXUBP to configure TMA data after
setting Antenna Tributary 1 Flag, Antenna Tributary 1 Factor, Antenna
Tributary 2 Flag, and Antenna Tributary 2 Factor.
l Activation Procedure for a Smart TMA
1. Run the BSC6900 MML command SET BTSRXUBP to turn on the power switches
for antenna ports.
2. Run the BSC6900 MML command STR BTSALDSCAN to scan antenna devices.
3. Run the BSC6900 MML command ADD BTSTMA to add a smart TMA.
4. Optional: To modify the attributes of a TMA subunit, run the BSC6900 MML
command MOD BTSTMASUBUNIT.
5. Optional: To modify the attributes of a TMA device, run the BSC6900 MML
command MOD BTSTMADEVICEDATA.
l Verification Procedure for a Common TMA
1. Run the BSC6900 MML command LST BTSRXUBP to query the TMA-related
parameters, including Antenna Tributary 1 Flag, Antenna Tributary 1 Factor,
Antenna Tributary 2 Flag, and Antenna Tributary 2 Factor.
2. On the BSC6900 LMT, click Trace. On the Trace Navigation Tree pane, navigate
to Trace > GSM Services > Abis Interface CS Trace. On the Basic tab page of the
displayed dialog box, select RSL under Trace Type. On the RSL tab page, select
DCM(Measurement Report) under Message Type, select TRX under Filter Flag,
and then specify the TRX ID.
3. For the RRU or RFU board whose RF feeder is attached with the TMA, perform a
dialing test to occupy the channel. Then, check the measured level reported by the
BTS.
Expected result: The Uplink RxLev specified in the Measurement Report message is
normal.
l Verification Procedure for a Smart TMA
1. Run the BSC6900 MML command STR BTSALDSCAN to check whether the
antenna devices are functioning.
2. Run the BSC6900 MML command DSP BTSTMA to query the information of a smart
TMA.
l Deactivation Procedure for a Common TMA
1. Run the BSC6900 MML command SET BTSRXUBP to configure the TMA data. In
this step:
– Set Antenna Tributary 1 Flag to NO(NO).
– Set Antenna Tributary 2 Flag to NO(NO).
l Deactivation Procedure for a Smart TMA
1. Run the BSC6900 MML command RMV BTSTMA to remove a smart TMA.
----End
Example
//Activating a common TMA
SET BTSRXUBP: IDTYPE=BYID, BTSID=9, RXUIDTYPE=SRNSN, SRN=4, SN=3,

GBSS14.0
RXUTYPE=DRFU, SndRcvMode1=SGL_ANTENNA, HAVETT1=YES, ATTENFACTOR1=5,

HAVETT2=YES, ATTENFACTOR2=10;
//Activating a smart TMA
SET BTSRXUBP: IDTYPE=BYID, BTSID=9, RXUIDTYPE=SRNSN, CN=0, SRN=4, SN=3,
RXUTYPE=MRRU, PwrSwitchRET=ON, THRESHOLDTYPERET=UER_SELF_DEFINE,
OverCurAlmThdRET=600, OverCurClrThdRET=300, UnderCurAlmThdRET=50,
UnderCurClrThdRET=100;
STR BTSALDSCAN: IDTYPE=BYID, BTSID=9, CTRLPORTSRN=4, CTRLPORTSN=3;
ADD BTSTMA: IDTYPE=BYID, BTSID=9, DEVICENO=1, DEVICENAME="tafang",
PWRSUPPLYTYPE=SINGLE_PORT_POWER, CTRLPORTCN=0, CTRLPORTSRN=4,
CTRLPORTSN=3, SUBUNITNUM=2;
//Verifying a common TMA
LST BTSRXUBP: IDTYPE=BYID, BTSID=9, RXUIDTYPE=SRNSN, SRN=4, SN=3;
SET FHO: OBJTYPE=CELL, CELLIDTYPE=BYID, CELLID=0, HOMOD=FREE;
//Verifying a smart TMA
STR BTSALDSCAN: IDTYPE=BYID, BTSID=9, CTRLPORTSRN=4, CTRLPORTSN=3;
DSP BTSTMA: IDTYPE=BYID, BTSID=9, DEVICENO=1;
//Deactivating a common TMA
RXUTYPE=DRFU, HAVETT1=NO, HAVETT2=NO;
//Deactivating a smart TMA
RMV BTSTMA: IDTYPE=BYID, BTSID=9, DEVICENO=1;

GBSS14.0
Feature Activation Guide 39 Configuring Remote Electrical Tilt
39 Configuring Remote Electrical Tilt
Remote Electrical Tilt. (This feature cannot be configured using the CME. )
Prerequisites
– The base station is connected to a remote electrical tilt (RET) antenna properly.
– The power switch for an RET antenna is turned on. The overcurrent and undercurrent
thresholds are checked since they are related to the number of RET antennas installed
on a board.
l License
Context
With this feature activated, users can remotely adjust the tilt of an RET antenna to optimize
network performance.
Procedure
l The following operations are applicable to the version V100R012 or later:
Activation Procedure
1. Optional: Run the BSC6900 MML command SET BTSRXUBP. In this step, set
RET ALD Power Switch, RET ALD Over Current Occur Threshold, RET ALD
Over Current Clear Threshold, RET ALD Under Current Occur Threshold, and
RET ALD Under Current Clear Threshold to appropriate values.
2. Run the BSC6900 MML command STR BTSALDSCAN to start an RET antenna
scanning task.
3. Run the BSC6900 MML command ADD BTSRET to add an RET antenna.
NOTE
For vendor information, see the antenna equipment manual or scan the RET antenna.

GBSS14.0
4. Optional: To modify parameters concerning an RET antenna subunit, run the

BSC6900 MML command MOD BTSRETSUBUNIT.
5. Optional: To modify parameters concerning the attributes of an RET device, run the
BSC6900 MML command MOD BTSRETDEVICEDATA.
6. Optional: To set the tilt angle of an RET antenna, run the BSC6900 MML
command MOD BTSRETTILT.
Verification Procedure
1. Run the BSC6900 MML command STR BTSALDSCAN to check whether an RET
antenna scanning task has been started.
2. Run the BSC6900 MML command DSP BTSRET to query the dynamic information
on an RET antenna.
3. Optional: Run the BSC6900 MML command DSP BTSRETSUBUNIT to query the
dynamic information on an RET antenna subunit.
Deactivation Procedure
l The following operations are applicable to the version V100R009 or earlier:
Activation Procedure
1. Optional: Run the BSC6900 MML command SET BTSRXUBP. In this step, set
RET ALD Power Switch, RET ALD Over Current Occur Threshold, RET ALD
Over Current Clear Threshold, RET ALD Under Current Occur Threshold, and
RET ALD Under Current Clear Threshold to appropriate values.
2. Run the BSC6900 MML command STR BTSALDSCAN to start an RET antenna
scanning task.
3. Run the BSC6900 MML command ADD BTSRET to add an RET antenna.
NOTE
For vendor information, see the antenna equipment manual or scan the RET antenna.
4. Optional: To set the tilt angle of an RET antenna, run the BSC6900 MML
command SET BTSRETANTTILT.
Verification Procedure
1. Run the BSC6900 MML command STR BTSALDSCAN to check whether an RET
antenna scanning task has been started.
2. Run the BSC6900 MML command DSP BTSRETANTTILT to query the tilt range
of the RET antenna and it's current tilt angle.
Deactivation Procedure
----End
Example
l The following scripts are applicable to the version V100R012 or later:
SET BTSRXUBP: IDTYPE=BYID, BTSID=9, RXUIDTYPE=RXUNAME,
RXUNAME="rru1", RXUTYPE=MRRU, PwrSwitchRET=ON;
STR BTSALDSCAN: IDTYPE=BYID, BTSID=9, CTRLPORTCN=0, CTRLPORTSRN=4,

GBSS14.0
CTRLPORTSN=0;
ADD BTSRET: IDTYPE=BYID, BTSID=9, DEVICENO=0, DEVICENAME="tianxian",
CTRLPORTCN=0, CTRLPORTSRN=4, CTRLPORTSN=0,
CTRLPORTNO=0, RETTYPE=MULTI_RET, SUBUNITNUM=1, SCENARIO=REGULAR,
VENDORCODE="AA", SERIALNO="123456";
MOD BTSRETSUBUNIT: IDTYPE=BYID, BTSID=9, DEVICENO=0, SUBUNITNO=1,
TILT=50;
MOD BTSRETDEVICEDATA: IDTYPE=BYID, BTSID=9, DEVICENO=0, SUBUNITNO=1,
BEARING=50, MODELNO="1";
MOD BTSRETTILT: IDTYPE=BYID, BTSID=9, OPMODE=DEVICENO, DEVICENO=0,
TILT=45;
CTRLPORTSN=0;
DSP BTSRET: IDTYPE=BYID, BTSID=9, DEVICENO=0;
DSP BTSRETSUBUNIT: IDTYPE=BYID, BTSID=9, DEVICENO=0;
l The following scripts are applicable to the version V100R009 or earlier:
SET BTSRXUBP: IDTYPE=BYID, BTSID=9, RXUIDTYPE=RXUNAME,
RXUNAME="rru1", RXUTYPE=MRRU, PwrSwitchRET=ON;
CTRLPORTSN=0;
ADD BTSRET: IDTYPE=BYID, BTSID=9, DEVICENO=0, DEVICENAME="tianxian",
CTRLPORTCN=0, CTRLPORTSRN=4, CTRLPORTSN=0,
CTRLPORTNO=0, RETTYPE=MULTI_RET, SUBUNITNUM=1, SCENARIO=REGULAR,
VENDORCODE="AA", SERIALNO="123456";
SET BTSRETANTTILT: OPMODE=DEVICENO, BTSIDTYPE=BYID, BTSID=9,
DEVICENO=0, TILT=45;
CTRLPORTSN=0;
DSP BTSRETANTTILT: OPMODE=SITE, IDTYPE=BYID, BTSID=9;

GBSS14.0
Feature Activation Guide 40 Configuring 2-Antenna Receive Diversity
40 Configuring 2-Antenna Receive

Diversity
2-Antenna Receive Diversity.
Prerequisites
– The BTS3006C or BTS3002E is configured with the DATM board.
– The BTS3012 or BTS3012AE is configured with the DATU board.
– The BTS3900, BTS3900A, or BTS3900L that uses the DRFU is configured with the
GATM board.
l License
Context
Two-antenna receive diversity is an effective approach of reducing signal attenuation by using
two antennas to receive a signal at the reception end, where two received signals are combined
after processing.
The following procedures assume that two-antenna receive diversity is configured for a DRFU
of a BTS3900.
Procedure
1. Run the BSC6900 MML command SET BTSRXUBP (CME single configuration:
BTS Device Panel > RXU Topology > Right click RXU Board > RXU Board
Porperties > RUX board Parameters; CME batch modification center: not
supported). In this step, set DRFU Sending Receiving Mode to
DOUBLE_ANTENNA(Double Feeder[2TX+2RX]).

GBSS14.0
Feature Activation Guide 40 Configuring 2-Antenna Receive Diversity
NOTE
Based on the type and number of TRX boards, the receiving and sending mode can be set to
SGLDOUBLE_ANTENNA(Single Feeder[1TX + 2RX]), DOUBLE_ANTENNA(Double
Feeder[2TX + 2RX]), or DOUBLEDOUBLE_ANTENNA(Double Feeder[1TX + 2RX])
to meet site requirements.
1. Run the BSC6900 MML command LST BTSRXUBP to query the receiving and
sending mode of the TRX board.
Expected result: DRFU Sending Receiving Mode is set to Double Feeder[2TX +
2RX].
----End
Example
RXUTYPE=DRFU, SndRcvMode1=DOUBLE_ANTENNA;
//Verifying 2-Antenna Receive Diversity
LST BTSRXUBP: IDTYPE=BYID, BTSID=153, LSTFORMAT=VERTICAL;

GBSS14.0
Feature Activation Guide 41 Configuring BTS Clock
41 Configuring BTS Clock
BTS Clock. (This feature cannot be configured using the CME. )
Prerequisites
– When the synchronization with the GPS clock is configured, the DBS3900/BTS3900/
BTS3900A must be configured with the USCU.
– When the synchronization with the BITS clock is configured, the DBS3900/BTS3900/
BTS3900A must be configured with the USCU.
l License
Context
l The synchronization of the BTS clock provides the basis for the frame synchronization.
The BTS uses the synchronization clock to obtain the reference clock source for the internal
frame synchronization.
l The BTS supports three clock synchronization modes: synchronization with the Abis clock,
synchronization with the GPS clock, and synchronization with the BITS clock. In addition,
the BTS internal clock can work in free-run mode to temporarily provide a stable reference
clock source for the BTS.
Procedure
Synchronization with the Abis clock (default mode)
1. Run the BSC6900 MML command SET BTSCLKPARA. In this step, set Clock
Type to TRCBSC_CLK(Trace BSC Clock).
Synchronization with the GPS clock
1. Run the BSC6900 MML command SET BTSCLK. In this step, set Clock Type to
TRCGPS_CLK(Trace GPS Clock).
Synchronization with the BITS clock

GBSS14.0
Feature Activation Guide 41 Configuring BTS Clock
1. Run the BSC6900 MML command SET BTSCLK. In this step, set Clock Type to
EXTSYN_CLK(External Sync Clock).
1. Run the BSC6900 MML command LST BTSCLK to query the current configuration
of the system clock.
Expected result:
If... Then...
The clock information corresponds to The configuration is successful.

the clock type configured
The clock information is inconsistent The configuration is unsuccessful.

with the configuration
2. Run the BSC6900 MML command DSP BTSATTR to query the attributes of the
BTS. Here,
– Set List Object to SITE(By Site).
– Select CLKATTR(CLKATTR) under the BTS Attribute check box.
Expected result: Clock attribute is Available.
----End
Example
//Configure the Synchronization with the Abis clock.
SET BTSCLK: IDTYPE=BYID, BTSID=1, ClkType=TRCBSC_CLK;
//Configure the Synchronization with the GPS clock
SET BTSCLK: IDTYPE=BYID, BTSID=1, ClkType=TRCGPS_CLK;
//Configure the Synchronization with the BITS clock
SET BTSCLK: IDTYPE=BYID, BTSID=1, ClkType=EXTSYN_CLK;
LST BTSCLK: IDTYPE=BYID, BTSID=1;
DSP BTSATTR: OBJTP=SITE, IDTYPE=BYID, BTSID=1, SITEATTR=CLKATTR;

GBSS14.0
Feature Activation Guide 42 Configuring Voice Fault Detection
42 Configuring Voice Fault Detection
Voice Fault Detection.
Prerequisites
– The crosstalk detection function cannot be used together with the features
GBFD-117701 BSC Local Switch, GBFD-117702 BTS Local Switch, GBFD-115701
TFO, GBFD-115702 TrFO, GBFD-118611 Abis IP over E1/T1, and GBFD-118601
Abis over IP.
– The one-way audio detection function cannot be used together with the features
GBFD-117701 BSC Local Switch and GBFD-117702 BTS Local Switch.
l License
– The crosstalk detection function can be enabled only in A over TDM transmission mode.
Context
This feature provides alarm mechanisms for crosstalk and one-way audio. The BSC records the
number of times of crosstalk and one-way audio occurrences periodically. If the number exceeds
a specified threshold, the BSC reports the BSS Internal Voice Channel Alarm.
Procedure
l Activation procedure for One-Way Audio Detection
NOTE
The parameters should be set to their recommended values for a commercial network. The following
operations are recommended only when you want to enable this feature immediately.
1. Run the BSC6900 MML command SET BSCBASIC (CME single configuration:
GSM Global Configuration Express > BSC Basic Configuration > Basic
Attributes of BSC; CME batch modification center: 3.17 Modifying GBSC
Parameters in Batches). In this step, set One-Way Mute Alarm Reporting

GBSS14.0
Period to 12, Speech Channel Alarm Threshold to 10, Speech Channel Alarm
Clearance Threshold to 6, One-Way Audio Log Type to
LEV2_MUTETEST_LOG_REC and IP_MUTETEST_LOG_REC, and Force
HO Upon Speech Problem to an appropriate value.
2. Run the BSC6900 MML command SET GCELLSOFT (CME single configuration:
Cell Configuration Express > Software Parameter and Reserved Parameter >
Software Parameters of Cell; CME batch modification center: 3.20 Modifying GSM
Cell Parameters in Batches). In this step, set Mute Detect Class1 Switch to
ENABLE(ENABLE), Period of Mute Detect Class1 to 5, Exceptional Frame
Threshold of Mute Detect Class1 to 25, Mute Detect Class2 Switch to ENABLE
(ENABLE), Period of Mute Detect Class2 TRAU Frame to 2, and Period of Mute
Detect Class2 to 4.
NOTE
If the proportion of bad frames to all speech frames exceeds the threshold specified in Exceptional
Frame Threshold of Mute Detect Class1 in the measurement period specified in Period of Mute
Detect Class1, one-way audio have occurred. Then the one-way audio detection class 2 starts. If no
test speech frame is received in the measurement period specified in Period of Mute Detect
Class2, the one-way audio is confirmed, and the BSC records a one-way audio occurrence. If the
number of times of one-way audio occurrences exceeds the threshold specified in Speech Channel
Alarm Threshold in the measurement period specified in One-Way Mute Alarm Reporting
Period, the BSC reports the BSS Internal Voice Channel Alarm. If the number of times of one-way
audio occurrences is smaller than the threshold specified in Speech Channel Alarm Clearance
Threshold in the measurement period specified in One-Way Mute Alarm Reporting Period, the
BSS Internal Voice Channel Alarm is cleared. If Force HO Upon Speech Problem is set to ON
(On), the BSC hands over the calls to another cell to avoid voice faults when detecting one-way audio
class 2.
l Activation procedure for Crosstalk Detection
Parameters in Batches). In this step, set One-Way Mute Alarm Reporting
Period to 12, Speech Channel Alarm Threshold to 10, Speech Channel Alarm
Clearance Threshold to 6, Force HO Upon Speech Problem to an appropriate value,
and do not set Cross Call Detect Time Threshold to 255.
2. Run the BSC6900 MML command SET GCELLBTSSOFTPARA (CME single
configuration: Cell Configuration Express > BTS Cell Parameter > BTS Soft
Parameters for Cell; CME batch modification center: not supported). In this step,
set BTS Crosstalk Detection to on.
NOTE
TheBTS Crosstalk Detection is set on the BTS. The Cross Call Detect Time Threshold specifies
the tolerance duration for crosstalk. If the duration of crosstalk exceeds the threshold specified in
Cross Call Detect Time Threshold, the BSC records a crosstalk occurrence. If the number of times
of crosstalk occurrences exceeds the threshold specified in Speech Channel Alarm Threshold in
the measurement period specified in One-Way Mute Alarm Reporting Period, the BSC reports
the BSS Internal Voice Channel Alarm. If the number of times of crosstalk occurrences is smaller
than the threshold specified in Speech Channel Alarm Clearance Threshold in the measurement
period specified in One-Way Mute Alarm Reporting Period, the BSS Internal Voice Channel
Alarm is cleared. If Force HO Upon Speech Problem is set to ON(On), the BSC hands over the
calls to another cell to avoid voice faults when detecting crosstalk.
1. When crosstalk or one-way audio occurs, view Dynamic Alarms.
Expected result: The BSS Internal Voice Channel Alarm exists with Failure
Type being Crosstalk or One-way Audio.

GBSS14.0
NOTE
If the number of times of actual crosstalk or one-way audio occurrences exceeds the threshold
specified in Speech Channel Alarm Threshold, the LMT reports the BSS Internal Voice
Channel Alarm.
l Deactivation procedure for One-Way Audio Detection
Cell Parameters in Batches). In this step, set Mute Detect Class1 Switch to
DISABLE(DISABLE) and Mute Detect Class2 Switch to DISABLE(DISABLE).
Parameters in Batches). In this step, clear the LEV1_MUTETEST_LOG_REC
check box under the parameter One-Way Audio Log Type.
l Deactivation procedure for Crosstalk Detection
Parameters in Batches). In this step, set Cross Call Detect Time Threshold to
255.
2. Run the BSC6900 MML command SET GCELLBTSSOFTPARA (CME single
configuration: Cell Configuration Express > BTS Cell Parameter > BTS Soft
Parameters for Cell; CME batch modification center: not supported). In this step,
set BTS Crosstalk Detection to OFF(OFF)
----End
Example
//Activating One-Way Audio Detection by running the following commands:
SET BSCBASIC: SpeechAlmPeriod=12, SPEECHCHANALARMTHRES=10,
SPEECHCHANRESUMEALARMTHRES=6,
MuteTestLogStyle=LEV1_MUTETEST_LOG_REC-0&LEV2_MUTETEST_LOG_REC-1&IP_MUTET
EST_LOG_REC-1&CIC_MUTETEST_LOG_REC-0, SpeechErrorForceHOSwitch=OFF;
SET GCELLSOFT: IDTYPE=BYID, CELLID=0, TCMUTEDETECTFLAG=ENABLE,
MUTECHECKCLASS1PERIOD=5, EXCEPFRAMETHRES=25,
MUTECHECKCLASS2SWITCH=ENABLE, DETECTFRAMEPERIOD=2, MUTECHECKPEIROD=4;
//Activating Crosstalk Detection by running the following commands:
SET BSCBASIC: CROCALTMTHRD=64, SpeechAlmPeriod=12,
SPEECHCHANALARMTHRES=10, SPEECHCHANRESUMEALARMTHRES=6,
SpeechErrorForceHOSwitch=OFF;
SET GCELLBTSSOFTPARA: CROCALCHKSW=ON;
//Deactivating One-Way Audio Detection by running the following command:

SET GCELLSOFT: IDTYPE=BYID, CELLID=0, TCMUTEDETECTFLAG=DISABLE,
MUTECHECKCLASS2SWITCH=DISABLE;
SET BSCBASIC: MuteTestLogStyle=LEV1_MUTETEST_LOG_REC-0;
//Deactivating Crosstalk Detection by running the following command:
SET BSCBASIC: CROCALTMTHRD=255;
SET GCELLBTSSOFTPARA: CROCALCHKSW=OFF;

GBSS14.0
Feature Activation Guide 43 Configuring Abis Crossed Pair Diagnosis
43 Configuring Abis Crossed Pair

Diagnosis
Abis Crossed Pair Diagnosis.
Prerequisites
l License
– This feature supports only TDM transmission.
Context
The Abis Crossed Pair Diagnosis feature helps detect exceptions in a transmission cable that
connects the BSC to a BTS when TDM transmission is used. If an exception occurs because of
incorrect cable connection, the BSC reports an alarm, switches the transmission cable to the
faulty status, and no longer allocates services to the cable.
Procedure
2. Run the BSC6900 MML command SET BTSRSV (CME single configuration: BTS
Configuration Express > BTS Basic Attributes > Reserved Parameters of BTS;
CME batch modification center: not supported). In this step, set Reserved Parameter
Index to 1 and bit 0 of Reserved Parameter Value also to 1. Specifically, when

GBSS14.0
Feature Activation Guide 43 Configuring Abis Crossed Pair Diagnosis
Reserved Parameter Index is set to 1, bit 0 of Reserved Parameter Value controls

whether to enable the Abis Crossed Pair Diagnosis feature.
Set Reserved Parameter Value based on the current parameter setting. For example,
if the current value of Reserved Parameter Value is 254 (0000 0000 1111 1110 in
binary), set this parameter to 255 (0000 0000 1111 1111 in binary) with bit 0 set to 1.
No verification procedure is required.
When this feature is enabled, the BSC reports ALM-28006 Radio Signaling Link
Disconnected and switches all channels on the TRX to the faulty status after detecting an
exception in signaling links.
2. Run the BSC6900 MML command SET BTSRSV (CME single configuration: BTS
Configuration Express > BTS Basic Attributes > Reserved Parameters of BTS;
CME batch modification center: not supported). In this step, set Reserved Parameter
Index to 1 and bit 0 of Reserved Parameter Value also to 0.
----End
Example
//Activating Abis Crossed Pair Diagnosis
SET BTSRSV: IDTYPE=BYID, BTSID=0, RSVID=1, RSVVALUE=255;
//Deactivating Abis Crossed Pair Diagnosis
SET BTSRSV: IDTYPE=BYID, BTSID=0, RSVID=1, RSVVALUE=254;

GBSS14.0
Feature Activation Guide 44 Configuring IP Performance Monitor
44 Configuring IP Performance Monitor
IP Performance Monitor.
Prerequisites
– The feature GBFD-118601 Abis over IP has been configured before this feature is
activated.
l License
– None
– The GOUa/FG2a/GOUc/FG2c/GOUd/FG2d interface board is configured on the BSC
side.
– The GTMU/GTMUb board is configured on the BTS side.
l Requirements for Transmission Networking
– IP Over FE/GE is used over the Abis interface. Alternatively, IP over E1/T1 is used on
the BTS side, E1/T1 is terminated on the intermediate router, and FE/GE interface is
configured on the BSC side.
– None
– None
Context
IP PM checks the performance of transmission between the BSC and a BTS in an IP network.
By effectively monitoring the changes in QoS-related parameters, IP PM quickly checks the
QoS of an IP bearer network over the Abis interface online. The check results serve as a basis
for flow control and admission control.

GBSS14.0
CAUTION
l This feature cannot be simultaneously used with load sharing networking. Since R14, this
feature can be used on the BSC when LAGs work in active/standby mode.
l IP PM uses a Huawei proprietary protocol and requires support from both the BSC and BTS.
l The BSC and BTS must use the same DSCP value for the same IP path. Otherwise, IP PM
will not work.
l The DSCP value must not be changed by any intermediate device between the BSC and BTS
because the BSC and BTS summarize the calculation results of the three QoS parameters by
DSCP value. If the DSCP value is changed, IP PM will not work.
l When configuring an IP path on the BSC side, set Peer subnet mask to 255.255.255.255.
Otherwise, IP PM cannot be activated.
Data Preparation
Paramete Parameter Remarks Data Source

r Name ID
Adjacent ANI Adjacent node identifier BSC internal planning

node ID of this IP path
IP path ID PATHID IP path where IP PM is to BSC internal planning

be activated
IS IS Whether the path is BSC internal planning

QOSPAT QOSPATH QOSPATH
H
PHB PHB PHB type of the IPPM to BSC internal planning

be enabled
BTS Index BTSID Index of the BTS where BTS internal planning
IP PM is to be activated
BTS BTSNAME Name of the BTS where BTS internal planning

Name IP PM is to be activated
Service SRVTYPE Type of the service for BTS internal planning

Type which IP PM is to be
activated
Procedure
– Activating IP PM on the BSC Side
1. Run the BSC6900 MML command ADD IPPATH (CME single configuration:
Abis Configuration Express > IP Transport > IP Path; CME batch modification
center: not supported)to add an IP path. In this step, set Interface Type to ABIS

GBSS14.0
(Abis Interface), Adjacent node ID, IP path ID, IP path type, Forward
Bandwidth, and Backward Bandwidth to appropriate values.
2. Run the BSC6900 MML command ACT IPPM (CME single configuration: Abis
Configuration Express > IP Transport > IPPM; CME batch modification
center: not supported) to activate the IP PM of the target IP path. In this step, set
Adjacent node ID, IP path ID, and IS QOSPATH to appropriate values.
– Activating IP PM on the BTS Side
1. Run the BSC6900 MML command ACT BTSIPPM (CME single configuration:
BTS Configuration Express > BTS Transmission Link > BTS IPPM
Function; CME batch modification center: not supported) to activate the IP PM
on the BTS side. In this step, set Index Type (Not required on the CME) to BYID
(By Index), BTS Index (Not required on the CME) to the index of the target BTS,
Service Type to the service to monitor (for example, CS Voice), and Lost Packet
Detection Switch to ON(On).
NOTE
After activating IP PM, users can query the QoS of the transport network between the BSC and BTS
by running MML commands or starting monitoring tasks on the LMT.
1. MML commands: are used to check the operating status of IP PM and to check whether IP PM
has been activated.
2. On the LMT, you can monitor the QoS of an IP transport network in real time, but only the results
of real-time monitoring on the BSC side are displayed. The BSC exports monitoring results every
5s.
– Verifying IP PM on the BSC Side
– By Running an MML Command
1. Run the BSC6900 MML command DSP IPPM to query the IP PM status of
the target IP path. In this step, set Adjacent node ID and IP path ID to
appropriate values.
The value of IPPM State is PM_UP, and the values of all IP PM statistics are
valid for the IP path that carries services.
– By Using the LMT
1. Click Monitor on the LMT main page. The Monitor tab page is displayed.
2. Choose Monitor > Common Monitoring > Link Performance Monitoring
on Monitor Navigation Tree. The Link Performance Monitoring dialog box
is displayed.

GBSS14.0
Figure 44-1 Link Performance Monitoring
3. In Link Performance Monitoring dialog box, set Monitor Item to IPPM and
related parameters to appropriate values.
if... then...
QOS IP PATH set Trace toQOSand Priority to an

appropriate value.
non QOS IP PATH set Trace toother.
4. Click Submit to start the monitoring.

When the monitoring is started, the real-time monitoring window is displayed.
The task name and related parameters are displayed in the Title bar, and the
monitoring results are displayed in tables and diagrams in real time.
– Verifying IP PM on the BTS Side
1. Run the BSC6900 MML command DSP BTSIPPMLNK to query the status of
the IP PM link. In this step, set Index Type (Not required on the CME) to BYID
(By Index), BTS Index (Not required on the CME) the index of the target BTS,
and Service Type to the activated service (for example, CS Voice).
Expected result: The value of PM Active State is Activated, and the values of IP
PM statistics on the BTS side are valid.
NOTE
The parameters Jitter Sum and Jitter Var Sum measure the jitters that a network experiences.
If the absolute value of the Jitter Sum parameter or the value of Jitter Var Sum parameter
is small, the network is stable.
It is recommended that the Jitter Var Sum parameter be set to a value less than 15 ms in
terrestrial transmission or less than 40 ms in satellite transmission.
If the value of the Jitter Var Sum parameter is greater than 50 ms, the network experiences
large jitters and is unstable.
– Deactivating IP PM on the BSC Side
1. Run the BSC6900 MML command DEA IPPM (CME single configuration: Abis
Configuration Express > IP Transport > IPPM; CME batch modification

GBSS14.0
center: not supported) to deactivate the IP PM of the target IP path. In this step,
set Adjacent node ID and IP path ID to appropriate values.
– Deactivating IP PM on the BTS Side
1. Run the BSC6900 MML command DEA BTSIPPM (CME single configuration:
BTS Configuration Express > BTS Transmission Link > BTS IPPM
Function; CME batch modification center: not supported) to deactivate the IP PM
that has been activated on the BTS side. In this step, set Index Type (Not required
on the CME) to BYID(By Index), BTS Index (Not required on the CME) the
index of the target BTS, and Service Type to the service to monitor (for example,
CS Voice).
----End
Example
// Activation procedure
ADD IPPATH: ANI=0, PATHID=1, ITFT=ABIS, PATHT=QoS, TXBW=10000,
RXBW=10000, VLANFlAG=DISABLE, PATHCHK=DISABLED;
ACT IPPM:ANI=0, PATHID=1, ISQOSPATH=YES,
PHB=BE-1&AF11-0&AF12-0&AF13-0&AF21-0&AF22-0&AF23-0&AF31-0&AF32-0&AF33-0&A
F41-0&AF42-0&AF43-0&EF-0, LOSTPKTDETECTSW=ON;
ACT BTSIPPM: IDTYPE=BYID, BTSID=0, SRVTYPE=CSVOICE,LOSTPKTDETECTSW=ON,
LOSTPKTALARMTHD=O1E2_R5E3;
// Verification procedure
DSP IPPM: ANI=1, PATHID=0;
DSP BTSIPPMLNK: IDTYPE=BYID, BTSID=0, DSCP=CS_SPEECH;
// Deactivation procedure
DEA IPPM: ANI=0, PATHID=1;
DEA BTSIPPM: IDTYPE=BYID, BTSID=0, SRVTYPE=CSVOICE;

GBSS14.0
Feature Activation Guide 45 Configuring GSM PS Service Map
45 Configuring GSM PS Service Map
GSM PS Service Map.
Prerequisites
– Built-in packet control unit (PCU)
– PS service processing boards
– Gb interface boards
– NIU boards, which perform service identification
– Service Aware Unit (SAU) boards
l License
l Others
– Terminals support NC1 or NC2 mode.
– The Nastar supports the feature.
Context
This feature provides a grid-based geographical representation of GSM PS traffic based on the
PS CHR log. This helps operators in understanding the resource distribution and bottlenecks of
the entire network. This also helps operators to address the problem of data deluge and guides
operators in hotspot coverage and network capacity expansion.
Data Preparation
Parameter Parameter Remarks (Configuration

Name ID Principle for Different Scenarios) Data Source
PS CHR PSRCDSW This parameter specifies whether to Network

Switch record PS CHR logs. planning

GBSS14.0

Mode Control PSOUTMOD This parameter specifies the mode Network

E used to export PS CHR logs. Values: planning
l COMMONUSRM(Common User
Mode) - PS CHR logs of the cell
specified using the SET
GPSCHRSCOPE command are
exported.
l SPECUSRM(Specified User
Mode) - PS CHR logs of the
terminals specified using the ADD
GPSCHRUSER command are
exported.
The two modes can coexist without
affecting each other.
IMEI PSCHRIMEI This parameter specifies whether to Network

Information extract IMEI information from PS planning
CHR logs.
Measurement PSCHRMR This parameter specifies whether to Network

Report extract MR information from PS CHR planning
Information logs.
Service Type PSCHRServi This parameter specifies whether to Network

Information ceType extract service type information from planning
PS CHR logs.
Support DPI SPTDPI This parameter specifies whether a Network

cell supports PS service identification. planning
The BSC performs differentiated
management for service types.
The value BSCSUPPORT(BSC
Support) is recommended.
PS CHR CHRCOLLE This parameter specifies whether to Network

Collect Switch CTSWITCH collect CHR logs for a specified planning
object.

GBSS14.0

Network NCO This parameter specifies the network Network

Control Mode control mode for cell reselection. planning
There are three modes.
l NC0: normal terminal control.
Terminals perform autonomous
cell reselection.
l NC1: terminal control with MRs
reported. Terminals send MRs to
the network and perform
autonomous cell reselection.
l NC2: network control. Terminals
send MRs to the network but do not
perform autonomous cell
reselection. When this parameter is
set to NC2(NC2) and Support NC2
is set to YES(Yes) (in the SET
GCELLGPRS command), the
network can control cell
reselection for terminals.
The value NC1(NC1) or NC2(NC2) is
recommended.
Cell RPTPERIOD This parameter specifies the interval at Network

Reselection I which a terminal in packet idle mode planning
MR Period in sends MRs.
Packet Idle The value 61.44sec(61.44sec) is
Mode recommended.
Cell RPTPERIOD This parameter specifies the interval at Network

Reselection T which a terminal in packet transfer planning
MR Period in mode sends measurement reports.
Packet The value 0.96sec(0.96sec) is
Transfer Mode recommended.
IMSI IMSI This parameter specifies the Network

international mobile subscriber planning
identity of a terminal. Set this
parameter to the valid IMSI of a
terminal on the live network.
Procedure
1. Run the BSC6900 MML command SET GPSCHRCTRL (CME single
PS CHR Control Switch; CME batch modification center: 3.17 Modifying GBSC
Parameters in Batches). In this step, set PS CHR Switch to ON(ON), Mode
Control to COMMONUSRM(Common User Mode), IMEI Information to ON

GBSS14.0
(Output) , and Measurement Report Information to ON(Output), set Service

Type Information to ON(Output), and set other parameters based on the network
plan.
2. Run the BSC6900 MML command SET GCELLGPRS (CME single configuration:
Cell Configuration Express > GPRS Attributes > Basic GPRS Attributes of 2G
Cell; CME batch modification center: 3.20 Modifying GSM Cell Parameters in
Batches), set Support DPI to SUPPORT(GGSN Support).
3. Run the BSC6900 MML command SET GPSCHRSCOPE (CME single
PS CHR Scope; CME batch modification center: not supported). In this step, set PS
CHR Collect Switch to ON(ON).
4. Run the BSC6900 MML command SET GCELLPSBASE (CME single
configuration: Cell Configuration Express > GPRS Attributes > Basic PS
Attributes of 2G Cell; CME batch modification center: 3.20 Modifying GSM Cell
Parameters in Batches). In this step, select the NC1(NC1) or NC2(NC2) check boxes
under the parameter Network Control Mode.
NOTE
If Network Control Mode is set to NC2(NC2), run the SET GCELLGPRS (CME single
configuration: Cell Configuration Express > GPRS Attributes > Basic GPRS Attributes
of 2G Cell; CME batch modification center: 3.20 Modifying GSM Cell Parameters in
Batches) command with Support NC2 set to YES(Yes) so that the network can control cell
reselection.
If Network Control Mode has already been set to NC1(NC1) or NC2(NC2), retain the setting.
5. Run the BSC6900 MML command SET GCELLNWCTRLMSRPARA (CME
single configuration: Cell Configuration Express > GPRS Attributes > Network
Control Measurement Parameters in System Information of 2G Cell; CME batch
modification center: 3.20 Modifying GSM Cell Parameters in Batches), In this step,
set Cell Reselection MR Period in Packet Idle Mode and Cell Reselection MR
Period in Packet Transfer Mode.
To specify terminals, perform Step 6 and Step 7.
Parameters in Batches). In this step, set PS CHR Switch to ON(ON), Mode
Control to SPECUSRM(Specified User Mode). and set other parameters based on
the network plan.
7. Run the BSC6900 MML command ADD GPSCHRUSER (CME single
PS CHR User; CME batch modification center: not supported) to add information
about a terminal. Repeat this step if you need to add more than one terminal.
1. Use an MS to perform PS services.
2. Stop the PS services on the MS.
3. A GPHR log will be generated after five minutes.
NOTE
Before verifying this feature, ensure that PS services can be processed properly.

GBSS14.0
Parameters in Batches). In this step, select PS CHR Switch to OFF(OFF), Mode
Control to COMMONUSRM(Common User Mode).
2. Run the BSC6900 MML command SET GPSCHRSCOPE (CME single
PS CHR Scope; CME batch modification center: not supported). In this step, select
Mode Control to OFF(OFF).
To specify a user, perform the following steps:
Parameters in Batches). In this step, select PS CHR Switch to OFF(OFF), Mode
Control to SPECUSRM(Specified User Mode).
----End
Example
//Activation procedure in common user mode
//Enabling PS CHR
SET GPSCHRCTRL: PSRCDSW=ON, PSOUTMODE=COMMONUSRM, PSCHRTraffic=ON,
PSCHRReselect=ON, PSCHREvent=ON, PSCHRAbnormal=ON, PSCHRMR=ON,
PSCHRServiceType=ON, PSCHRIMEI=ON;
//Enabling cell-level logging
SET GPSCHRSCOPE: IDTYPE=BYID, CELLID=0, CHRCOLLECTSWITCH=ON;
//Enabling NC1 for a cell
SET GCELLPSBASE: IDTYPE=BYID, CELLID=0, NCO=NC1;
SET GCELLNWCTRLMSRPARA: IDTYPE=BYID, CELLID=0, RPTPERIODI=61.44sec,
RPTPERIODT=0.96sec;
//Deactivation procedure in common user mode

//Disabling PS CHR
SET GPSCHRCTRL: PSRCDSW=OFF, PSOUTMODE=COMMONUSRM;

//Disabling cell-level logging
SET GPSCHRSCOPE: IDTYPE=BYID, CELLID=0, CHRCOLLECTSWITCH=OFF;
//Activation procedure in specified user mode

//Enabling PS CHR
SET GPSCHRCTRL: PSRCDSW=ON, PSOUTMODE= SPECUSRM, PSCHRTraffic=ON,
PSCHRReselect=ON, PSCHREvent=ON, PSCHRAbnormal=ON, PSCHRMR=ON,
PSCHRServiceType=ON, PSCHRIMEI=ON;
//Specifying users
ADD GPSCHRUSER: IMSI="460311026110900";
ADD GPSCHRUSER: IMSI="460311026110901";
//Deactivation procedure in specified user mode

SET GPSCHRCTRL: PSRCDSW=OFF, PSOUTMODE=SPECUSRM;

GBSS14.0 46 Configuring Multi-mode BS Common CPRI Interface
Feature Activation Guide (GBTS)
46 Configuring Multi-mode BS Common

CPRI Interface (GBTS)
Multi-mode BS Common CPRI Interface (GBTS).
Prerequisites
– As Figure 46-1 shows, the hardware of the base station is installed.
Figure 46-1 Network topology of Multi-mode BS Common CPRI Interface
NOTE
As Figure 46-1 shows, CPRI0, CPRI1, and CPRI2 on the GTMU board are respectively connected
to one CPRI port on the WBBP board. CPRI3, CPRI4, and CPRI5 are connected to the RRU3908.
l License

GBSS14.0 46 Configuring Multi-mode BS Common CPRI Interface
Context
In the traditional GSM+UMTS dual-mode solution, the GSM and UMTS base stations use the
same site. Different RF modules are used for different radio standards and therefore separate
optical cables are required. As a result, many optical cables are required for the entire system,
which increases the deployment cost. After this feature is applied, the demand of optical cables
is reduced by 50%, which helps reduce the cost of the optical modules and optical cables and
reduce the expense in the installation and maintenance of the optical cables between the BBU
and RF modules.
Procedure
1. Run the BSC6900 MML command ADD BTSSFPMODE (CME single
configuration: BTS Device Panel > Right click GTMU Board > Configure SFP
Switch Port; CME batch modification center: not supported) to configure the
switching relation of the SFP ports and switch the data of CPRI0, CPRI1, and CPRI2
on the GTMU to CPRI3, CPRI4, and CPRI5 on the GTMU.
NOTE
The switching relation of the SFP ports is configured only on the GSM side.
1. Run the BSC6900 MML command LST BTSSFPMODE to query the configurations
of the SFP ports.
1. Run the BSC6900 MML command RMV BTSSFPMODE (CME single
configuration: BTS Device Panel > Right click GTMU Board > Configure SFP
Switch Port; CME batch modification center: not supported) to remove the SFP port
switching relation.
----End
Example
ADD BTSSFPMODE: IDTYPE=BYID, BTSID=161, CN=0, SRN=0, SN=6, SFPPORTNO=0,
SWITCHPORTNO=3;
LST BTSSFPMODE: IDTYPE=BYID, BTSID=161, CN=0, SRN=0, SN=6, SFPPORTNO=0;
RMV BTSSFPMODE: IDTYPE=BYID, BTSID=161, CN=0, SRN=0, SN=6, SFPPORTNO=0;

GBSS14.0
Feature Activation Guide 47 Configuring Enhanced Full Rate (EFR)
This section describes how to activate, verify, and deactivate the GBFD-113301 Enhanced Full
Rate (EFR) feature.
Prerequisites
l License
l Others
– MSs support EFR.
Context
EFR is used to improve voice quality.
Procedure
1. Run the BSC6900 MML command SET GCELLCCACCESS (CME single
configuration: Cell Configuration Express > Call Control > Call Access Control
Parameters in Batches). In this step, set Speech Version to FULL_RATE_VER2
(Full-rate VER 2).
2. Optional: Run the BSC6900 MML command SET GCELLSOFT (CME single
configuration: Cell Configuration Express > Software Parameter and Reserved
Parameter > Software Parameters of Cell; CME batch modification center: 3.20
Modifying GSM Cell Parameters in Batches) to enable EFR forcibly as the current
speech version. In this step, set Allow Forced EFR in Cell to YES(Yes).
3. Optional: Run the BSC6900 MML command SET TCPARA (CME single
configuration: Device Panel > Right click data processing Board > Properties >

GBSS14.0
Feature Activation Guide 47 Configuring Enhanced Full Rate (EFR)
TC Attributes of DSP; CME batch modification center: not supported) to further

improve voice quality by enabling the E-Coder function. In this step, specify the
subrack number and slot number based on actual configuration of the DPUa, DPUc,
or DPUf board and set Coding Mode to ECODEC(Enhanced code mode).
NOTE
In A over IP mode, the EFR and E-Coder cannot be forcibly enabled.

1. Run the BSC6900 MML command DSP CALLRES during a dialing test or a call. In
this step, set User Identity Type to BYMSISDN(By MSISDN) and MSISDN to
ISDNs of MS 1 and MS 2. Then, observe the Channel Service Type field of TC
Resource Info in The result area.
Expected result: Available speech versions for EFR are displayed.
Run the BSC6900 MML command SET GCELLCCACCESS (CME single
Parameters in Batches). In this step, set Speech Version to a value other than
FULL_RATE_VER2(Full-rate VER 2).
----End
Example
//Activating EFR
SET GCELLCCACCESS: IDTYPE=BYID, CELLID=0, VOICEVER=FULL_RATE_VER2-1;
//(Optional) Enabling EFR forcibly

SET GCELLSOFT: IDTYPE=BYID, CELLID=0, FORCEDCELLEFRSWITCH=YES;
//(Optional) Enabling ECODEC forcibly

SET TCPARA: SRN=0, SN=9, EncodeMode=ECODEC;
//Deactivating EFR

GBSS14.0
Feature Activation Guide 48 Configuring Automatic Level Control (ALC)
48 Configuring Automatic Level Control

(ALC)
The ALC feature adjusts the gains of uplink and downlink digital speech signals and changes
the amplitude of digital speech signals at an interval of 20 ms. This retains the speech signal
level in the entire network in a stable state and ensures that the speech quality is not affected by
the volume fluctuation of both parties. This section describes how to activate, verify, and
deactivate the optional feature GBFD-115601 Automatic Level Control (ALC).
Prerequisites
– This feature applies only in A over TDM mode and is mutually exclusive with the
following features:
– GBFD-118602 A over IP
– GBFD-118622 A IP over E1/T1
– This feature takes effect only if none of the following features is applied to a call:
– GBFD-115701 TFO
– GBFD-117701 BSC Local Switch
– GBFD-117702 BTS Local Switch
l License
The license controlling this feature has been activated. For details on how to activate the
license, see 4 Activating the GSM License. For details about license items, see 2 Feature
Activation and License Item Descriptions.
The DPUa/DPUc/DPUf board is started normally.
l Dependencies on Transport Network
TDM transmission is used over the A interface.
l Dependencies on Other NEs and Third-Party Devices
N/A
N/A

GBSS14.0
Context
l Precautions
None
l Data Preparation
Table 48-1 Configuring the fixed level mode

Parameter Data
Name Parameter ID Parameter Setting Source
ALC Switch AlcEnFlag OFF(Off) Internal

planning
ALC Mode AlcAdaptMode FIXEDLEVEL(Fixed level mode) Internal

planning
ALC Fix AlcFixLev -18 Internal

Target Level planning
Enable TC TcStatisticSw NO(No) Internal

Performance planning
Measurement
TC TCSTATISTICT ALC(ALC Measurement) not Internal

Performance YPE selected by default planning
Measurement
Type
Table 48-2 Configuring the fixed gain mode

Parameter Data

planning
ALC Mode AlcAdaptMode FIXEDGAIN(Fixed gain mode) Internal

planning
ALC Fix Gain AlcFixGain 0 Internal

planning

Measurement

Measurement
Type

GBSS14.0
Table 48-3 Configuring the adaptive mode
Parameter Data

planning
ALC Mode AlcAdaptMode ADAPTIVE(Adaptive mode) Internal

planning
ALC Max AlcMaxLev -4 Internal

ALC Min AlcMinLev -23 Internal


Measurement

Measurement
Type
Table 48-4 Configuring ACLP (Optional)
Parameter Data
ACLP Switch ACLPENFLAG OFF(Off) Internal

planning

Measurement
TC TCSTATISTICT ACLP(ACLP Measurement) not Internal

Measurement
Type
Procedure
– If the fixed level mode is required, perform the following operations:
Run the BSC6900 MML command SET TCPARA (CME single configuration: Device
Panel > Right click data processing Board > Properties > TC Attributes of DSP;
CME batch modification center: not supported). In this step, set ALC Switch to ON
(On), ALC Mode to FIXEDLEVEL(Fixed level mode), and ALC Fix Target
Level to its recommended value for the DPU board.

GBSS14.0
NOTE
If DSPNO is not specified, the attributes of all the DSPs are set, it can be set as required.
To increase the acoustic volume, set ALC Fix Target Level to a larger value. Its maximum value
is -4. To decrease the acoustic volume, set ALC Fix Target Level to a smaller value. Its minimum
value is -23.
– If the fixed gain mode is required, perform the following operations:
(On), ALC Mode to FIXEDGAIN(Fixed gain mode), and ALC Fix Gain to its
recommended value for the DPU board.
NOTE
To increase the acoustic volume, set ALC Fix Gain to 12. To decrease the acoustic volume, set
ALC Fix Gain to 3.
– If the adaptive mode is required, perform the following operations:
(On) and ALC Mode to ADAPTIVE(Adaptive mode) on the DPU board. In addition,
set ALC Max Target Level and ALC Min Target Level to their recommended values.
– (Optional) Configuring ACLP
CME batch modification center: not supported) with ACLP Switch set to BOTH(On
for uplink and downlink) for all DSPs on the DPU. In this manner, the ACLP function
is enabled on both the uplink and downlink.
NOTE
Run the BSC6900 MML command SET OTHSOFTPARA (CME single configuration: GSM
Global Configuration Express > Software Parameter Configuration > Other Software
Parameters of BSC; CME batch modification center: 3.17 Modifying GBSC Parameters in
Batches) to measure the gain brought by ALC/ACLP. In this step, set Enable TC Performance
Measurement to YES(Yes) and TC Performance Measurement Type to ALC(ALC
Measurement) or ACLP(ACLP Measurement).
The following takes the fixed gain mode as an example to describe the verification
operations.
1. Run the BSC6900 MML command SET TCPARA. In this step, set ALC Switch of
all the DSPs on the tested DPU board to ON(On), ALC Mode to FIXEDGAIN(Fixed
gain mode), and ALC Fix Gain to 0.
2. Run the BSC6900 MML command LST TCPARA to check whether all the
parameters set in Step 1 are listed. If all the parameters are listed, the previous
commands are executed successfully.
3. In the same cell, use MS1 to call MS2 with a normal voice. Then, hang up the phone.
4. Run the BSC6900 MML command SET TCPARA. In this step, set ALC Switch of
all the DSPs on the tested DPU board to ON(On), ALC Mode to FIXEDGAIN(Fixed
gain mode), and ALC Fix Gain to 12.

GBSS14.0
parameters set in step Step 4 are listed. If all the parameters are listed, the previous
6. Use MS 1 to call MS 2 again. Speak with a normal volume on MS 1.
Expected result: The volume of the heard voice increases, compared with the volume
heard in Step 3.
NOTE
The previous steps are performed when ALC Mode is set to FIXEDGAIN(Fixed gain
mode). The verification steps are similar when ALC Mode is set to FIXEDLEVEL(Fixed
level mode) or ADAPTIVE(Adaptive mode).
1. Run the BSC6900 MML command SET TCPARA (CME single configuration:
Device Panel > Right click data processing Board > Properties > TC Attributes
of DSP; CME batch modification center: not supported). In this step, set ALC
Switch to OFF(Off) for the DPU board.
----End
Example
//Activating ALC when the fixed level mode is used
SET TCPARA: SRN=3, SN=8, AlcEnFlag=ON, AlcAdaptMode=FIXEDLEVEL,
AlcFixLev=-18;
//Activating ALC when the fixed gain mode is used
SET TCPARA: SRN=3, SN=8, AlcEnFlag=ON, AlcAdaptMode=FIXEDGAIN,
AlcFixGain=0;
//Activating ALC when the adaptive mode is used
SET TCPARA: SRN=3, SN=8, AlcEnFlag=ON, AlcAdaptMode=ADAPTIVE,
AlcMaxLev=-4, AlcMinLev=-23;
//Activating ACLP
SET TCPARA: SRN=3, SN=8, ACLPENFLAG=BOTH;
//Deactivating ALC
SET TCPARA: SRN=3, SN=8, AlcEnFlag=OFF;

GBSS14.0
Feature Activation Guide 49 Configuring Acoustic Echo Cancellation (AEC)
49 Configuring Acoustic Echo Cancellation

(AEC)
The AEC helps reduce the acoustic echo caused by the terminal, improving the speech quality.
Acoustic echo is generated when the MS speaker is not completely isolated from the MS receiver.
After the voice of one party (Party A) reaches the MS, the voice is transmitted back to Party A
through the receiver. Then, Party A can hear his/her own voice. The phenomena is known as
acoustic echo. AEC is a feature with which acoustic echoes can be pre-assessed and eliminated
by means of the analysis on forward and backward voice signals. This section describes how to
activate, verify, and deactivate the optional feature GBFD-115602 Acoustic Echo Cancellation
(AEC).
Prerequisites
following features:
– GBFD-115701 TFO
l License
N/A

GBSS14.0
N/A
Context
l Precautions
None
l Data Preparation
Parameter Data
ANC Switch AecEnFlag OFF(Off) Internal

planning

Measurement
TC TCSTATISTICT AEC(AEC Measurement) not Internal

Measurement
Type
AEC Echo AecDefaultERL 20 Internal

Return Loss planning
AEC Echo AecTail 300 Internal

Path Delay planning
AEC Path AecPureDelay 100 Internal

Delay planning
Procedure
of DSP; CME batch modification center: not supported) with AEC Switch set to ON
(On) and other parameters set to their default values for the DPU board.
NOTE
Batches) to measure the gain brought by AEC. In this step, set Enable TC Performance
Measurement to YES(Yes) and TC Performance Measurement Type to AEC(AEC
Measurement).
1. Run the BSC6900 MML command SET TCPARA with AEC Switch set to OFF
(Off) and other parameters set to their default values for the DPU board.

GBSS14.0
3. Use one test MS (MS 1) to make a call to another test MS (MS 2). Check that acoustic
echo occurs, and then hand off the call.
NOTE
The echo is easily generated when a common MS enabled with the hands-free function is placed
in a sealing box.
4. Run the BSC6900 MML command SET TCPARA with AEC Switch of the DPU
board set to ON(On) and other parameters set to their default values.
6. Use MS 1 to make a call to MS 2 again, and check whether acoustic echoes are reduced.
If the echoes are reduced, finish the verification.
If the echoes are not reduced, hand off the call and then Run the BSC6900 MML
command SET TCPARA with AEC Echo Return Loss set to a smaller value within
the valid range. If AEC Echo Return Loss is already set to the smallest value, set
AEC Echo Path Delay to a larger value. Repeat step Step 6 to check whether the
echoes are reduced.
NOTE
l The acoustic echo is generated between MSs. The echo generated between an MS and a fixed-
line phone is termed the electric echo. The electric echo problem is solved by the CN side.
l When satellite transmission on the Abis or Ater interface is required, AEC Path Delay must be
set, so as to eliminate the extra delay caused by satellite transmission.
of DSP; CME batch modification center: not supported) with AEC Switch set to OFF
(Off) for the DPU board.
----End
Example
//Activating AEC
SET TCPARA: SRN=3, SN=8, AecEnFlag=ON;
//Deactivating AEC
SET TCPARA: SRN=3, SN=8, AecEnFlag=OFF;

GBSS14.0
Feature Activation Guide 50 Configuring Automatic Noise Restraint (ANR)
50 Configuring Automatic Noise Restraint

(ANR)
ANR reduces the background noise on the uplink and downlink speech signals and improves
the signal-to-noise ratio (SNR) and speech intelligibility. In this way, the other party of the call
can clearly hear the voice. This section describes how to activate, verify, and deactivate the
optional feature GBFD-115603 Automatic Noise Restraint (ANR).
Prerequisites
following features:
– GBFD-115701 TFO
l License
N/A
N/A

GBSS14.0
Context
l Precautions
None
l Data Preparation
Parameter Data
ANR Switch AnrEnFlag OFF(Off) Internal

planning

Measurement
TC TCSTATISTICT ANR(ANR Measurement) not Internal

Measurement
Type
Noise AnrMode MODE1(Optimized version) Internal

Suppression planning
Algorithm
Switch
Noise AnrNseReductM RELATIVELEVEL(Relative Internal

Attenuation ode level) planning
Mode
Noise AnrNseReductLe RELATIVE_2(Relative mode Internal

Suppression v level 2) planning
Mode
Transparent AnrByPassNseLe -43 Internal

Transmit v planning
Thresh of
Noise Lev
Procedure
of DSP; CME batch modification center: not supported) with ANR Switch set to
UPLINK(On for uplink) or DOWNLINK(On for dnlink), Noise Suppression
Algorithm Switch to MODE1(Optimized version), and Noise Attenuation Mode,
Noise Suppression Mode, and Transparent Transmit Thresh of Noise Lev set to
appropriate values for the DPU board.

GBSS14.0
NOTE
Batches) to measure the gain brought by ANR. In this step, set Enable TC Performance
Measurement to YES(Yes) and TC Performance Measurement Type to ANR(ANR
Measurement).
1. Run the BSC6900 MML command SET TCPARA with ANR Switch for all the DSPs
on the DPU board to be tested set to OFF(Off).
2. Ensure that two test MSs (MS 1 and MS 2) are in the same cell. Use MS 1 to make a
call to MS 2 in a noisy environment. Check that great background noises can be heard
through the MS 2, and then hand off the call.
3. Run the BSC6900 MML command SET TCPARA with ANR Switch for all the DSPs
on the DPU board to be tested set to UPLINK(On for uplink) or DOWNLINK(On
for dnlink).
5. Use MS 1 to make a call to MS 2 again. Speak at the normal volume on MS 1, and
check that the background noises heard through MS 2 are reduced.
of DSP; CME batch modification center: not supported) with ANR Switch for all the
DSPs on the DPU board to be tested set to OFF(Off).
----End
Example
//Activating ANR
SET TCPARA: SRN=3, SN=8, AnrEnFlag=UPLINK, AnrMode=MODE1,
AnrNseReductMode=RELATIVELEVEL, AnrNseReductLev=RELATIVE_2,
AnrByPassNseLev=-43;
//Deactivating ANR
SET TCPARA: SRN=3, SN=8, AnrEnFlag=OFF;

GBSS14.0
Feature Activation Guide 51 Configuring TFO
51 Configuring TFO
TFO.
Prerequisites
following features:
– The following features take effect only if TFO establishment fails for a call:
– GBFD-115601 Automatic Level Control (ALC)
– GBFD-115602 Acoustic Echo Cancellation (AEC)
– GBFD-115603 Automatic Noise Restraint (ANR)
– GBFD-115703 Automatic Noise Compensation (ANC)
– GBFD-115704 Enhancement Packet Loss Concealment (EPLC)
– GBFD-115711 EVAD
– GBFD-115506 AMR Coding Rate Threshold Adaptive Adjustment
– This feature cannot be used if either of the following features is applied to a call:
l License

GBSS14.0
Context
TFO solves the problem of speech signal damage in repeated encoding and decoding by
canceling one encoding and decoding process to improve the signal quality.
If the WRFD-011600 TFO/TrFO feature is activated on the 3G network when this feature is
enabled, the AMR feature must be supported by the 3G network to ensure that TFO is supported
during a call between the 2G and 3G networks.
To enable TFO for calls using the AMR speech version, the BSC version and BTS version must
meet the mapping relationship in the following table.
BSC Version BTS Version Support TFO for Calls
Using AMR
GBSS8.1 GBSS8.1 Support
GBSS8.1 GBSS9.0 and later Not support
GBSS9.0 and later GBSS8.1 Not support
GBSS9.0 and later GBSS9.0 and later Support
To enable TFO for calls using the non-AMR speech version, there is no requirements for the
mapping between the BSC version and BTS version.
Procedure
Batches). In this step, set TFO Switch to ENABLE(Enable).
2. Configure the speech version by performing the following operations:
– For non-AMR services:
a. Run the BSC6900 MML command SET GCELLCCACCESS (CME single
Control Parameters of Cell; CME batch modification center: 3.20
Modifying GSM Cell Parameters in Batches). In this step, set Speech
Version to FULL_RATE_VER1(Full-rate VER 1), FULL_RATE_VER2
(Full-rate VER 2), and HALF_RATE_VER1(Half-rate VER 1).
b. Optional: If you need to observe counters related to TFO, Run the BSC6900
MML command SET OTHSOFTPARA (CME single configuration: GSM
Global Configuration Express > Software Parameter Configuration >
Other Software Parameters of BSC; CME batch modification center: 3.17
Modifying GBSC Parameters in Batches). In this step, set Enable TC
Performance Measurement to YES(Yes), and set TC Performance
Measurement Type to TFO(TFO Measurement).
– For AMR services:
a. Run the BSC6900 MML command SET BSCBASIC (CME single

GBSS14.0

Tag to GSM_PHASE_2Plus, set Um Interface Tag to
GSM_PHASE_2Plus , set Abis Interface Tag to GSM_PHASE_2Plus .
b. Run the BSC6900 MML command SET GCELLCCACCESS (CME single
Version to FULL_RATE_VER1(Full-rate VER 1) and
FULL_RATE_VER3(Full-rate VER 3), or FULL_RATE_VER1(Full-
rate VER 1) and HALF_RATE_VER3(Half-rate VER 3).
c. Optional: If you need to observe counters related to TFO, Run the BSC6900
MML command SET OTHSOFTPARA (CME single configuration: GSM
Global Configuration Express > Software Parameter Configuration >
Other Software Parameters of BSC; CME batch modification center: 3.17
Modifying GBSC Parameters in Batches). In this step, set Enable TC
Performance Measurement to YES(Yes), and set TC Performance
Measurement Type to TFO(TFO Measurement).
3. Optional: Run the BSC6900 MML command SET AITFOTHPARA (CME single
Configuration > Software Parameters for A Interface; CME batch modification
center: not supported) to configure TFO between MSCs. In this step, set A over TDM
Speech Version Select Strategy to MSC(MSC Strategy). In this way, the BSC
selects a speech version according to the speech version priorities carried in the
assignment request from the MSC.
NOTE
The following uses verifying the TFO function for non-AMR services as an example.
1. Run the BSC6900 MML command SET GCELLCHMGAD with TCH Traffic Busy
Threshold set to 100 to ensure that new calls are preferentially assigned full-rate
TCHs.
2. Run the BSC6900 MML command SET GCELLCCACCESS. In this step, only set
Speech Version to FULL_RATE_VER1(Full-rate VER 1).
NOTE
Only FULL_RATE_VER1(Full-rate VER 1) is selected, two test MSs use the same FR
coding scheme. This ensures the implementation of TFO.
3. Run the BSC6900 MML command SET GCELLBASICPARA. In this step, set TFO
Switch of the test cell to DISABLE(Disable).
4. Use MS 1 and MS 2 to access the network from the test cell, and use MS 1 to call MS
2.
5. Run the BSC6900 MML command DSP CALLRES for MS 1 and MS 2 separately.
In this step, set User Identity Type to BYMSISDN(By MSISDN) and MSISDN to
the ISDNs of MS 1 and MS 2. Check whether the value of Tfo State is TFO not
start in the result area.
6. Terminate the call.
7. Run the BSC6900 MML command SET GCELLBASICPARA. In this step, set TFO
Switch of the test cell to ENABLE(Enable).
8. Optional: If TFO is configured between MSCs when the BSC selects a speech version
according to the speech version priorities carried in the request message from the MSC,

GBSS14.0
Run the BSC6900 MML command SET AITFOTHPARA, set A over TDM Speech
Version Select Strategy to MSC(MSC Strategy).
9. Use MS 1 to call MS 2 again.
10. Run the BSC6900 MML command DSP CALLRES for MS 1 and MS 2 separately.
In this step, set User Identity Type to BYMSISDN(By MSISDN) and MSISDN to
the ISDNs of MS 1 and MS 2. Check whether the value of Tfo State is TFO Instance
Succeed in the result area. If the value of Tfo State is TFO Instance Succeed and
the speech quality improves, TFO has been enabled.
NOTE
Ensure that an inter-BSC or inter-cell handover is not performed during the call when verifying
TFO. This is because the DSP CALLRES command cannot be executed after such a handover.
Batches). In this step, set TFO Switch of the test cell to DISABLE(Disable).
----End
Example
//Activating TFO
/*Activating TFO for non-AMR services*/
SET GCELLBASICPARA: IDTYPE=BYID, CELLID=0, NBAMRTFOSWITCH=ENABLE;
/*Activating TFO for AMR services*/
SET GCELLBASICPARA: IDTYPE=BYID, CELLID=0, NBAMRTFOSWITCH=ENABLE;
SET GCELLCCAMR: IDTYPE=BYID, CELLID=0, ACTCDSETF=4_75KBIT/S-1&5_15KBIT/
S-0&5_90KBIT/S-1&6_70KBIT/S-0&7_40KBIT/S-1&7_95KBIT/S-0&10_2KBIT/
S-0&12_2KBIT/S-1;
//Deactivating TFO
SET GCELLBASICPARA: IDTYPE=BYID, CELLID=0, NBAMRTFOSWITCH=DISABLE;
//Configuring TFO between MSCs when the BSC selects a speech version
according to the speech version priorities carried in the request message
from the MSC:
SET AITFOTHPARA: CNNODEIDX=1, SpVerTdmStrategy=MSC;

GBSS14.0
Feature Activation Guide 52 Configuring Automatic Noise Compensation (ANC)
52 Configuring Automatic Noise

Compensation (ANC)
By comparing the background noise level at the local end and the signal level at the peer end,
ANC adaptively increases the speech volume of the peer end if the background noise level of
the local end is high. Therefore, the ratio of the signal level at the peer end to the background
noise level at the local end increases, which helps to improve the voice quality. This section
describes how to activate, verify, and deactivate the optional feature GBFD-115703 Automatic
Noise Compensation (ANC).
Prerequisites
following features:
– GBFD-115701 TFO
l License
N/A
N/A

GBSS14.0
Context
l Precautions
None
l Data Preparation
Parameter Data
ANC Switch AncEnFlag OFF(Off) Internal

planning
ANC Target AncSnrGateRS 12 Internal

SNR planning
ANC Max AncMaxGain 6 Internal

Gain planning

Measurement
TC TCSTATISTICT ANC(ANC Measurement) not Internal

Measurement
Type
Procedure
of DSP; CME batch modification center: not supported). In this step, set ANC
Switch to ON(On), and set ANC Target SNR and ANC Max Gain to the
recommended values for the DPU board.
NOTE
Batches) to measure the gain brought by ANC. In this step, set Enable TC Performance
Measurement to YES(Yes) and TC Performance Measurement Type to ANC(ANC
Measurement).
1. Run the BSC6900 MML command SET TCPARA. In this step, set Subrack No. and
Slot No. to those of the DPU board, and set ANC Switch to OFF(Off).
2. Place MS 1 in a noisy place, and then use MS 2 to call MS 1.
Expected result: MS 2 cannot hear the voice of MS 1 clearly.
3. Run the BSC6900 MML command SET TCPARA. In this step, set Subrack No. and
Slot No. to those of the DPU board. Then, set ANC Switch to ON(On), and set
AncSnrGateRS and AncMaxGain to the recommended values.
4. Run the BSC6900 MML command LST TCPARA to check the values of ANC
Switch, ANC Target SNR, and ANC Max Gain.

GBSS14.0
Expected result: The value of ANC Switch is ON, which indicates that the ANC
feature is enabled.
5. Use MS 2 to call MS 1 again.
Expected result: The voice of MS 1 is clearer.
of DSP; CME batch modification center: not supported). In this step, set ANC
Switch to OFF(Off).
----End
Example
//Activating ANC
SET TCPARA: SRN=3, SN=8, AncEnFlag=ON, AncSnrGateRS=12, AncMaxGain=6;
//Deactivating ANC
SET TCPARA: SRN=3, SN=8, AncEnFlag=OFF;

GBSS14.0 53 Configuring Enhancement Packet Loss Concealment
Feature Activation Guide (EPLC)
53 Configuring Enhancement Packet Loss

Concealment (EPLC)
Enhancement Packet Loss Concealment (EPLC).
Prerequisites
– The following feature has been configured before this feature is activated:
GBFD-115501 AMR FR, GBFD-115502 AMR HR, or GBFD-113301 Enhanced Full
Rate.
– This feature cannot be used together with the feature GBFD-115701 TFO,
GBFD-115702 TrFO, GBFD-118602 A over IP, GBFD-117701 BSC Local Switch or
GBFD-117702 BTS Local Switch.
l License
Context
With EPLC, frames of lost packets can be recovered and compensated. To a extent, this helps
solve the problem of speech frame loss in a poor transmission or radio environment, thereby
improving the network performance.
Procedure
of DSP; CME batch modification center: not supported). In this step, set EPLC
Switch to ON(On) and retain the default values of other parameters.

GBSS14.0 53 Configuring Enhancement Packet Loss Concealment
Feature Activation Guide (EPLC)
1. Run the BSC6900 MML command LST GCELLCCACCESS to query the value of
Speech Version.
Expected result: At least one of Full-rate VER 2, Full-rate VER 3, and Half-rate
VER 3 is selected for Speech Version.
2. Run the BSC6900 MML command SET TCPARA. In this step, set EPLC Switch to
OFF(Off) and retain the default values of other parameters.
3. Run the BSC6900 MML command LST TCPARA to query the configuration
information about the TC.
Expected result: The value of EPLC Switch is Off.
4. Use an MS to perform speech services in a poor radio environment where the uplink
receive quality is in the range of 4-7 and record the average MOS of the voice quality.
5. Run the BSC6900 MML command SET TCPARA. In this step, set EPLC Switch to
ON(On) and retain the default values of other parameters.
6. Run the BSC6900 MML command LST TCPARA to query the configuration
information about the TC.
Expected result: The value of EPLC Switch is On.
7. Use an MS to perform speech services in a poor radio environment where the uplink
receive quality is in the range of 4-7 and record the average MOS of the voice quality.
8. Compare the MOSs recorded in Step 4 and Step 7.
Expected result: The MOS recorded in Step 7 is greater than that recorded in Step
4.
of DSP; CME batch modification center: not supported). In this step, set EPLC
Switch to OFF(Off).
----End
Example
//Activating EPLC
SET TCPARA: SRN=3, SN=8, EPLCSwitch=ON;
//Deactivating EPLC
SET TCPARA: SRN=3, SN=8, EPLCSwitch=OFF;

GBSS14.0
Feature Activation Guide 54 Configuring EVAD
54 Configuring EVAD
EVAD, namely enhanced voice activity detection.
Prerequisites
– The DPUc, DPUa, or DPUf board is configured and functional.
– The configurations of the other features, on which this feature depends, are complete.
This feature depends on the feature GBFD-114801 Discontinuous Transmission (DTX)-
Downlink and GBFD-115501 AMR FR/GBFD-115502 AMR HR/GBFD-113301
Enhanced Full Rate.
– This feature is mutually exclusive to features GBFD-118602 A over IP, GBFD-118622
A IP over E1/T1, GBFD-115701 TFO, GBFD-115702 TrFO, GBFD-117701 BSC Local
Switch, and GBFD-117702 BTS Local Switch.
l License
Context
The enhanced VAD technology improves the encoding effect of music and prevents damage to
music by the traditional VAD algorithm.
Procedure
of DSP; CME batch modification center: not supported), in this step, set EVAD
Switch to ON(On) on the DPUc, DPUa, or DPUf board.
1. Use a UE to initiate and set up a call.

GBSS14.0
Feature Activation Guide 54 Configuring EVAD
2. Have the called UE play the ring back tone (RBT).

Expected result: The music received by the UE is smooth and with a good voice
quality.
of DSP; CME batch modification center: not supported) with EVAD Switch to OFF
(Off).
----End
Example
//Activating EVAD
SET TCPARA: SRN=0, SN=10, EVADEnFlag=ON;
//Deactivating EVAD
SET TCPARA: SRN=0, SN=10, EVADEnFlag=OFF;

GBSS14.0
Feature Activation Guide 55 Configuring Voice Quality Index (VQI)
55 Configuring Voice Quality Index (VQI)
Voice Quality Index (VQI).
Prerequisites
l License
– The cell is configured with neighboring cells.
– The BTS of the cell supports downlink VQI.
Context
The VQI establishes the mapping between radio network performance and voice quality. The
VQI value, which helps learn the voice quality, is calculated based on the radio quality
parameters for the uplink and downlink speech signals. The MOS analysis method is applied in
VQI to measure the voice quality. The MOS is used to assess the quality of middle-rate and low-
rate voice coding. The MOS value ranges from 1 to 5.
Based on the MOS analysis method, Huawei further divides the voice quality into 11 levels. In
this manner, the voice quality is quantified to facilitate voice problem identification and network
optimization.
Procedure
– Activating downlink VQI
1. Run the BSC6900 MML command SET GCELLSOFT (CME single
configuration: Cell Configuration Express > Software Parameter and

GBSS14.0
Reserved Parameter > Software Parameters of Cell; CME batch modification

Report Downlink VQI Allowed to ENABLE(Enable).
NOTE
VQI is recorded in a measurement report if only Report Downlink VQI Allowed is set to
ENABLE(Enable) and a voice service is processed.
– Activating uplink VQI
1. Run the BSC6900 MML command SET GCELLOTHBASIC (CME single
configuration: Cell Configuration Express > Cell Attributes > Other Basic
Parameters in Batches). In this step, set Report Speech Quality to YES
(Report).
– Verifying downlink VQI
1. Run the BSC6900 MML command SET GCELLSOFT. In this step, set
CELLID to the index of the cell to be verified and RPTDLVQIALLOWED to
ENABLE(Enable). Perform a voice service test and check the downlink VQI
value in the measurement reports.
Expected result: The downlink VQI value is not reported.
2. Run the BSC6900 MML command SET GCELLCCACCESS. In this step, set
VOICEVER to one that matches the channel type. Speech versions are
FULL_RATE_VER1(Full-rate VER 1), FULL_RATE_VER2(Full-rate VER
2), FULL_RATE_VER3(Full-rate VER 3), HALF_RATE_VER1(Half-rate
VER 1), HALF_RATE_VER2(Half-rate VER 2), and HALF_RATE_VER3
(Half-rate VER 3). Perform a voice service test and check the downlink VQI value
in the measurement reports.
Expected result: The downlink VQI value is reported.
3. Run the BSC6900 MML command SET GCELLHOCTRL. In this step, set
BTSMESRPTPREPROC to BTS_Preprocessing(BTS preprocessing) and
MRPREPROCFREQ to an appropriate value based on the site requirements.
Perform a voice service test and check the downlink VQI value in the preprocessed
measurement reports.
Expected result: The downlink VQI value is reported.
– Verifying uplink VQI
1. On the BSC6900 LMT, initiate CS domain message tracing of a single subscriber
by referring to Tracing CS domain messages of a single subscriber. Perform a voice
service test, and check the uplink VQI value in the measurement reports.
Expected result: The uplink VQI value is reported.
2. Run the BSC6900 MML command SET GCELLHOCTRL. In this step, set
BTSMESRPTPREPROC to BTS_Preprocessing(BTS preprocessing) and
MRPREPROCFREQ to an appropriate value based on the site requirements.
Perform a voice service test and check the uplink VQI value in the preprocessed
measurement reports.
Expected result: The uplink VQI value is reported.
– Deactivating downlink VQI

GBSS14.0
1. Run the BSC6900 MML command SET GCELLSOFT (CME single

Report Downlink VQI Allowed to DISABLE(Disable).
– Deactivating uplink VQI
Parameters in Batches). In this step, set Report Speech Quality to NO(Not
report).
----End
Example
//Activating downlink VQI
SET GCELLSOFT: IDTYPE=BYID, CELLID=1, RPTDLVQIALLOWED=ENABLE;
//Activating uplink VQI
SET GCELLOTHBASIC: IDTYPE=BYID, CELLID=1, RPTVOICE=YES;
//Verifying downlink VQI
SET GCELLSOFT: IDTYPE=BYID, CELLID=0, RPTDLVQIALLOWED=ENABLE;
BTSMESRPTPREPROC=BTS_Preprocessing, MRPREPROCFREQ=Once_ps;
//Deactivating downlink VQI
SET GCELLSOFT: IDTYPE=BYID, CELLID=1, RPTDLVQIALLOWED=DISABLE;
//Deactivating uplink VQI
SET GCELLOTHBASIC: IDTYPE=BYID, CELLID=1, RPTVOICE=NO;

GBSS14.0
Feature Activation Guide 56 Configuring Um Interface Speech Frame Repairing
56 Configuring Um Interface Speech Frame

Repairing
Um Interface Speech Frame Repairing.
Prerequisites
– The following types of RF modules support this feature: MRFU V2, GRFU V2,
MRFUd, MRFUe, RRU3908 V2, RRU3008 V2, RRU3926, RRU3928, RRU3929, and
RRU3922E.
l License
Context
Currently, the speech services using EFR and AMR-NB account for the largest proportion of
speech services in live networks. When the bit error rate (BER) is high and the C/I is low, the
channel decoding fail. As a result, the erroneous results of channel decoding will be discarded,
which greatly degrades the voice quality.
To solve the preceding problem, Huawei develops a technique based on the characteristics of
EFR and AMR-NB speech frames to repair the erroneous speech frames over the Um interface.
This technique increases the success rate of voice decoding, thus improving the voice quality
under low C/I. This feature, applicable to only the uplink, repairs speech frames in the source
and channel decoding of EFR and three types of AMR: 4.75 kbit/s, 7.40 kbit/s, and 12.2 kbit/s.
Therefore, this feature improves the Mean Opinion Score (MOS) by 0.1 to 0.2 when the CIR is
low.
Procedure

GBSS14.0
Feature Activation Guide 56 Configuring Um Interface Speech Frame Repairing

Parameters in Batches). In this step, set Um Interface Speech Frame Repair
Switch to YES(Yes), and then set Speech Frame Classification Threshold, BQ
Speech Frame Repair BER Threshold, and GQ Speech Frame Repair BER
Threshold as required.
1. Run the BSC6900 MML command LST GCELLCCBASIC to query the parameters
related to the Um interface speech frame repairing feature.
Expected result:
– The value of Um Interface Speech Frame Repair Switch is YES(Yes).
– The values of Speech Frame Classification Threshold, BQ Speech Frame
Repair BER Threshold, and GQ Speech Frame Repair BER Threshold are the
same as those set in the activation procedure.
2. When making calls in an area of the network with severe frame loss, Run the BSC6900
MML command SET GCELLSOFT with FER Report Enable set to YES(Yes) to
allow the BTS to report the Frame Erase Ratio (FER).
3. Query FER-related counters reported by the BTS on the M2000. To do so, choose
Performance > Query Result on the menu bar. In the displayed window, click New
Query. The Query Result window is displayed. Navigate to BSC6900 GSM > MR
Measurement > FER Measurement per TRX. Then, check the value of the counter
EFR Average FER.
Expected result: After the Um interface speech frame repairing feature is enabled, the
value of EFR Average FER decreases and the speech quality is improved.
Parameters in Batches) with Um Interface Speech Frame Repair Switch set to
NO(No).
----End
Example
SET GCELLCCBASIC: IDTYPE=BYID, CELLID=0, UMSFRSWITCH=YES,
UMSFRLLRFACTOR=4, UMSFRLLRTHRESH=60, UMSFRBERTHRESH=50;
LST GCELLCCBASIC: IDTYPE=BYID, CELLID=0;
SET GCELLSOFT: IDTYPE=BYID, CELLID=0, FERRPTEN=YES;
SET GCELLCCBASIC: IDTYPE=BYID, CELLID=0, UMSFRSWITCH=NO;

GBSS14.0
Feature Activation Guide 57 Configuring AMR
57 Configuring AMR
AMR FR, GBFD-115502 AMR HR and GBFD-115503 AMR Power Control.
Prerequisites
l License
– The MS, BTS, and MSC support the AMR function.
Context
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 anti-
interference capability of the radio communications system and the voice quality are improved.
NOTE
l The AMR HR supports the 7.95 kbit/s coding scheme only when Service Mode of the Abis interface
is IP or HDLC in BM/TC combined or A over IP mode.
l If a BTS supports AMR but its software version does not, then AMR cannot be configured. In this case,
a BTS software version that supports AMR must be obtained.
Procedure
1. Set basic AMR parameters.

GBSS14.0

3.17 Modifying GBSC Parameters in Batches) with A Interface Tag set to
GSM_PHASE_2Plus.
b. Run the BSC6900 MML command SET GCELLCCACCESS (CME single
GSM Cell Parameters in Batches). In this step, select the
FULL_RATE_VER3(Full-rate VER 3) and FULL_RATE_VER1(Full-rate
VER 1)check box in the Speech Version parameter for the cell.
NOTE
If the cell also supports half-rate services, select the HALF_RATE_VER3(Half-rate

VER 3) check box simultaneously.
c. To further improve voice quality by enabling the E-Coder function, Run the
BSC6900 MML command SET TCPARA (CME single configuration: Device
Panel > Right click data processing Board > Properties > TC Attributes of
DSP; CME batch modification center: not supported). In this step, specify the
subrack number and slot number based on actual configuration of the DPU board
and set Coding Mode to ECODEC(Enhanced code mode).
2. Set AMR call processing parameters.
a. Run the BSC6900 MML command SET GCELLCCBASIC (CME single
configuration: Cell Configuration Express > Call Control > Call Control
Basic Parameters of Cell; CME batch modification center: 3.20 Modifying
GSM Cell Parameters in Batches) with AFR Radio Link Timeout and AFR
SACCH Multi-Frames set to appropriate values.
NOTE
If the cell also supports half-rate services, set AHR Radio Link Timeout and AHR
SACCH Multi-Frames to appropriate values simultaneously.
b. Optional: Run the BSC6900 MML command SET GCELLCCAMR (CME
single configuration: Cell Configuration Express > Call Control > Call
Control AMR Parameters of Cell; CME batch modification center: 3.20
Modifying GSM Cell Parameters in Batches) to set AMR call control
parameters related to full-rate and half-rate channels.
NOTE
l AMR ACS[F] and AMR ACS[H] can be set to one to four coding rates respectively.
In A over IP mode, their settings must be consistent with those on the CN side.
l You can select different algorithms according to the setting of AMR Rate
Adjustment Switch.
3. To set parameters for AMR intra-cell handover between TCHF and TCHH, see
Activating the AMR handover algorithm in 8 Configuring HUAWEI I
Handover and Activating the algorithm for the handover between TCHF and
TCHH in 202 Configuring HUAWEI II Handover.
4. Optional: Set AMR power control parameters.
– When Huawei II power control algorithm is used, Run the BSC6900 MML
command SET GCELLPWR2 (CME single configuration: Cell Configuration
Express > Power Control > Parameters for Power Control II of Cell; CME

GBSS14.0
batch modification center: 3.20 Modifying GSM Cell Parameters in Batches) to

set AMR power control parameters such as AMR PC Interval.
– When Huawei III power control algorithm is used, Run the BSC6900 MML
command SET GCELLPWR3 (CME single configuration: Cell Configuration
Express > Power Control > Parameters for Power Control III of Cell; CME
batch modification center: 3.20 Modifying GSM Cell Parameters in Batches).
In this step, set Allow III Power Control For AMR to ON(Allowed) and set other
AMR power control parameters based on network conditions.
5. Set AMR channel management parameters.
a. Run the BSC6900 MML command SET GCELLCHMGAD (CME single
modification center: 3.20 Modifying GSM Cell Parameters in Batches) with
AMR TCH/H Prior Allowed and AMR TCH/H Prior Cell Load Threshold
set to appropriate values.
1. Start a call between two MSs.
2. Run the BSC6900 MML command DSP CALLRES.
Expected result: Available speech versions including FAMR are displayed.
At least one speech version must be configured for the BSC6900. Therefore, the
deactivation procedure is unnecessary. However, you can Run the BSC6900 MML
command SET GCELLCCACCESS (CME single configuration: Cell Configuration
Express > Call Control > Call Access Control Parameters of Cell; CME batch
modification center: 3.20 Modifying GSM Cell Parameters in Batches) to modify the
speech version.
----End
Example
SET BSCBASIC: AVer=GSM_PHASE_2;
1-0&HALF_RATE_VER2-0&HALF_RATE_VER3-0&HALF_RATE_VER5-0;
SET GCELLCCBASIC: IDTYPE=BYID, CELLID=0, AFRSAMULFRM=48, AHRSAMULFRM=32,
AFRDSBLCNT=64_Times, AHRDSBLCNT=52_Times;
SET GCELLCCAMR: IDTYPE=BYID, CELLID=0, RATECTRLSW=ALG1,
ACTCDSETF=4_75KBIT/S-1&5_15KBIT/S-1&5_90KBIT/S-1&6_70KBIT/S-1,
ACTCDSETH=4_75KBIT/S-1&5_15KBIT/S-1&5_90KBIT/S-1&6_70KBIT/S-1,
AMRDADTHAW=YES;
SET GCELLPWR2: IDTYPE=BYID, CELLID=0, AMRPCADJPERIOD=3;
SET GCELLPWR3: IDTYPE=BYID, CELLID=0, AMRCALLPCALLOWED=ON;
SET GCELLCHMGAD IDTYPE=BYID, CELLID=0, AMRTCHHPRIORALLOW=ON,
AMRTCHHPRIORLOAD=55;

GBSS14.0 58 Configuring AMR Coding Rate Threshold Adaptive
Feature Activation Guide Adjustment
58 Configuring AMR Coding Rate

Threshold Adaptive Adjustment
AMR Coding Rate Threshold Adaptive Adjustment.
Prerequisites
– The BTS supports AMR Coding Rate Threshold Adaptive Adjustment.
– An MOS tester and a vehicle for drive test are ready.
This feature depends on at least one of the following features:
– GBFD-115501 AMR FR
– GBFD-115502 AMR HR
– GBFD-115507 WB AMR
The AMR downlink adaptive threshold adjustment function also depends on the
GBFD-117501 Enhanced Measurement Report (EMR) feature.
– This feature cannot be used together with the following feature:
– GBFD-115701 TFO
l License
– The test cell is configured with neighboring cells.

Context
NOTE
BTS3006C, BTS3002E, BTS3012, and BTS3012AE do not support this feature when they use a non-
optimized DTRU.
This feature sets the target voice quality of the network and adjusts the coding rate threshold
adaptively so that a proper coding rate is selected for the AMR speech service and therefore to
gain optimal AMR voice quality.
AMR coding rate threshold adaptive adjustment, which is uplink/downlink specific, brings the
following benefits:
l A proper coding rate is selected for the AMR speech service.
l Optimal AMR voice quality is gained.
Procedure
l Activate AMR uplink adaptive threshold adjustment.
1. Run the BSC6900 MML command SET GCELLCCAMR (CME single
configuration: Cell Configuration Express > Call Control > Call Control AMR
Parameters in Batches) with AMR Uplink Adaptive Threshold Allowed set to
YES(Yes).
l Verify AMR uplink adaptive threshold adjustment.
Select a BTS that provides continuous cell coverage. In the coverage area of the test cell,
select a test path where the downlink level ranges from -50 dBm to -110 dBm and is equally
distributed along the test path.
Parameters in Batches) with Speech Version set to at least FULL_RATE_VER1
(FULL-RATE VER 1),FULL_RATE_VER3(FULL-RATE VER 3) and
HALF_RATE_VER3(HALF-RATE VER 3).
Parameters in Batches) with AMR Uplink Adaptive Threshold Allowed set to
YES(Yes).
3. Connect the MOS tester to the test MS, use the test MS to make a call, and then perform
a drive test on the test path.
NOTE
The recommended test scheme is as follows: The distance of the test path is 1 km to 2 km, the moving
speed of the vehicle for the drive test is 20 km/h, and the drive test is performed three times (three
come-and-goes). Record the MOSs and calculate the average MOS.
Parameters in Batches) with AMR Uplink Adaptive Threshold Allowed set to NO
(No).
5. Repeat Step 3.

6. Compared the data recorded in Step 3 and Step 5 to find the difference in voice quality
when AMR Uplink Adaptive Threshold Allowed is set to YES(Yes) and when it is
set to NO(No).
Expected result: The MOS when AMR Uplink Adaptive Threshold Allowed is set
to YES(Yes) is higher than the MOS when AMR Uplink Adaptive Threshold
Allowed is set to NO(No).
l Deactivate AMR uplink adaptive threshold adjustment.
Parameters in Batches) with AMR Uplink Adaptive Threshold Allowed set to NO
(No).
2. Run the BSC6900 MML command LST GCELLCCAMR (CME single
Parameters of Cell) to view the value of AMR Uplink Adaptive Threshold
Allowed.
Expected result: AMR Uplink Adaptive Threshold Allowed is set to NO(No).
l Activate AMR downlink adaptive threshold adjustment.
Parameters in Batches) with AMR Downlink Adaptive Threshold Allowed set to
YES(Yes) and Is RATSCCH Function Enabled to ENABLE(Enable).
2. Run the BSC6900 MML command SET GCELLCCUTRANSYS (CME single
configuration: Cell Configuration Express > Call Control > Call Control UTRAN
System Message Parameters of Cell; CME batch modification center: 3.20
Modifying GSM Cell Parameters in Batches) with Measurement Report Type to
EnhMeasReport(Enhanced Measurement Report).
l Verify AMR downlink adaptive threshold adjustment.
Select a BTS that provides continuous cell coverage. In the coverage area of the test cell,
select a test path where the downlink level ranges from -50 dBm to -110 dBm and is equally
distributed.
Parameters in Batches) with Speech Version set to at least FULL_RATE_VER1
(FULL-RATE VER 1),FULL_RATE_VER3(FULL-RATE VER 3) and
HALF_RATE_VER3(HALF-RATE VER 3).
YES(Yes).
3. Connect the MOS tester to the test MS, use the test MS to make a call, and then perform
a drive test on the test path.

NOTE
The recommended test scheme is as follows: The distance of the test path is 1 km to 2 km, the moving
speed of the vehicle for the drive test is 20 km/h, and the drive test is performed three times (three
come-and-goes). Record the MOSs and calculate the average MOS.
NO(No).
5. Repeat Step 3.
6. Compared the data recorded in Step 3 and Step 5 to find the difference in voice quality
when AMR Downlink Adaptive Threshold Allowed is set to YES(Yes) and when
it is set to NO(No).
Expected result: The MOS when AMR Downlink Adaptive Threshold Allowed is
set to YES(Yes) is higher than the MOS when AMR Downlink Adaptive Threshold
Allowed is set to NO(No).
l Deactivate AMR downlink adaptive threshold adjustment.
NO(No).
2. Run the BSC6900 MML command LST GCELLCCAMR (CME single
Parameters of Cell) to view the value of AMR Downlink Adaptive Threshold
Allowed.
Expected result: AMR Downlink Adaptive Threshold Allowed is set to NO(No).
----End
Example
//Activating AMR uplink adaptive threshold adjustment
SET GCELLCCAMR: IDTYPE=BYID, CELLID=0, AMRUADTHAW=YES;
//Deactivating AMR uplink adaptive threshold adjustment
SET GCELLCCAMR: IDTYPE=BYID, CELLID=0, AMRUADTHAW=NO;
//Activating AMR downlink adaptive threshold adjustment
SET GCELLCCAMR: IDTYPE=BYID, CELLID=0, AMRDADTHAW=YES;
//Deactivating AMR downlink adaptive threshold adjustment
SET GCELLCCAMR: IDTYPE=BYID, CELLID=0, AMRDADTHAW=NO;

GBSS14.0
Feature Activation Guide 59 Configuring WB AMR
59 Configuring WB AMR
WB AMR.
Prerequisites
– The BTS3006C, BTS3002E, BTS3012, and BTS3012AE do not support this feature
when they use a non-optimized DTRU.
– This feature depends on the TrFO feature in A over IP mode. TrFO needs to be enabled
on the MGW or MSC Server.
l License
– The MS, MGW, and MSC server support this feature.
Context
l WB AMR is a coding scheme that can significantly improve speech quality. Using WB
AMR, the sampling rate is increased to 16 kHz and the speech frequency range is extended
to 0.05-7 kHz. WB AMR provides clear and loud voice and high-quality speech compared
with the narrow band AMR with the sampling rate of 8 kHz and the speech frequency range
between 200 Hz and 3400 Hz.
l WB AMR adopts the Guassian Minimum Shift Keying (GMSK) mode and supports the
rates of 6.60 kbit/s, 8.85 kbit/s, and 12.65 kbit/s on full-rate TCHs.
Procedure

GBSS14.0
Feature Activation Guide 59 Configuring WB AMR
Parameters in Batches). In this step, set A Interface Tag, Um Interface Tag, and
Abis Interface Tag to GSM_PHASE_2Plus.
Parameters in Batches) to set the access control parameters for the cell.
NOTE
Select the FULL_RATE_VER5(Full-rate VER 5) check box under the parameter Speech
Version while retaining the default speech versions.
Parameters in Batches) to set the call control AMR parameters for the cell. The call
control AMR parameters are AMR UL Coding Rate adj.th1[WB], AMR UL
Coding Rate adj.th2[WB], AMR UL Coding Rate adj.hyst1[WB], AMR UL
Coding Rate adj.hyst2[WB], AMR DL Coding Rate adj.th1[WB], AMR DL
Coding Rate adj.th2[WB], AMR DL Coding Rate adj.hyst1[WB], and AMR DL
Coding Rate adj.hyst2[WB].
NOTE
When transmission quality over the Um interface is good, the value of the coding rate
adjustment threshold should be relatively low. In this way, a rate can be easily increased to
improve speech quality. If the value of the coding rate adjustment threshold is high, a low rate
coding mode should be used to improve robustness over the Um interface.
Reducing the coding rate hysteresis leads to frequent rate adjustments.
1. Use two MSs supporting WB AMR to call each other.
2. Run the BSC6900 MML command DSP CALLRES to verify that the value of
Channel Service Type is AMR_WB.
Parameters in Batches). In this step, clear the FULL_RATE_VER5(Full-rate VER
5) check box under the parameter Speech Version.
----End
Example
//Activating WB AMR
//Verifying WB AMR
DSP CALLRES: USERIDTYPE=BYMSISDN, MSISDN="13818889988";
//Deactivating WB AMR

GBSS14.0
Feature Activation Guide 60 Configuring Half Rate Speech (HR)
60 Configuring Half Rate Speech (HR)
This section describes how to activate, verify, and deactivate the feature GBFD-113401 Half
Rate Speech (HR).
Prerequisites
l License
Context
This feature enables the operator to expand the network capacity and improve the frequency
usage without increasing the hardware investment. In addition, a higher traffic volume can be
carried on an E1.
Procedure
Parameters in Batches) with Speech Version of a cell to FULL_RATE_VER1
(Full-rate VER 1), HALF_RATE_VER1(Half-rate VER
1),HALF_RATE_VER3(Half-rate VER 3), and HALF_RATE_VER2(Half-rate
VER 2). HALF_RATE_VER2(Half-rate VER 2) of Speech Version is reserved
for compliance with protocols. Currently, no service uses HR speech version 2.
1. Run the BSC6900 MML command LST GCELLCCACCESS to view the setting of
Speech Version of a specified cell.

GBSS14.0
Feature Activation Guide 60 Configuring Half Rate Speech (HR)
Expected result: The activated speech versions are labeled USED.

At least one speech version must be configured for the BSC6900. Therefore, the
deactivation procedure is unnecessary. However, you can Run the BSC6900 MML
command SET GCELLCCACCESS (CME single configuration: Cell Configuration
Express > Call Control > Call Access Control Parameters of Cell; CME batch
modification center: 3.20 Modifying GSM Cell Parameters in Batches) to modify the
speech version.
----End
Example
//Activating half rate speech (HR)

GBSS14.0
Feature Activation Guide 61 Configuring Dynamic Adjustment Between FR and HR
61 Configuring Dynamic Adjustment

Between FR and HR
With GBFD-113402 Dynamic Adjustment Between FR and HR, the full-rate (FR) channels and
the half-rate (HR) channels are dynamically converted to automatically adapt to the proportions
of FR channels and HR channels in a cell during a call. In this manner, the situation in which
one type of channel is congested whereas the other type of channel is idle can be prevented. This
section describes how to activate, verify, and deactivate the optional feature GBFD-113402
Dynamic Adjustment Between FR and HR.
Prerequisites
– The feature GBFD-113401 Half Rate Speech has been configured before this feature is
activated.
l License
– The cell works properly.
Context
l Precautions
None
l Data Preparation
Parameter Name Parameter ID Parameter Data Source
Setting
TCH Rate Adjust TCHAJFLAG YES(Yes) Network planning

Allow

GBSS14.0

Setting
TCH Traffic Busy TCHBUSYTHRES You are advised to Network planning

Threshold use the default
value.
Set this parameter
to a small value to
increase the
proportion of MSs
on TCHHs and set
this parameter to a
large value to
reduce the
proportion of MSs
on TCHHs.
Load of UL-OL HRIUOLDRATES This parameter is Network planning

Cells Rate Select ELALLOW required for
Allowed concentric cells,
including co-
BCCH cells.
Tch Traffic Busy TCHTRICBUSYO You are advised to Network planning

Overlay Threshold VERLAYTHR use the default
value.
For a concentric
cell, set this
parameter to a small
value to increase the
proportion of MSs
on TCHHs in the
overlaid subcell and
set this parameter to
a large value to
reduce the
proportion of MSs
on TCHHs in the
overlaid subcell.

GBSS14.0

Setting
Tch Traffic Busy TCHTRIBUSYUN You are advised to Network planning

Underlay DERLAYTHR use the default
Threshold value.
For a concentric
cell, set this
parameter to a small
proportion of MSs
on TCHHs in the
underlaid subcell
and set this
parameter to a large
value to reduce the
proportion of MSs
on TCHHs in the
underlaid subcell.
AMR TCH/H Prior AMRTCHHPRIO You are advised to Network planning

Cell Load RLOAD use the default
Threshold value.
This parameter is
required if the cell
enables the AMR
function. Set this
value to a small
proportion of MSs
on AMR TCHHs
and set this
parameter to a large
value to reduce the
proportion of MSs
on AMR TCHHs.
NOTE
l This parameter
is valid only if
AMRTCHHP
RIORALLOW
is set to ON
(On).
l This parameter
is invalid for
concentric cells
if
AMRLOADO
PTEN and
HRIUOLDRA
TESELALLO
W are set to YES
(Yes) at the
same time.

GBSS14.0

Setting
AMR Load AMRLOADOPTE You are advised to Network planning

Calculation N set this parameter to
Optimization YES(Yes) for a
concentric cell.
For AMR calls in a
concentric cell, set
this parameter to
YES(Yes) if the
proportion of MSs
on TCHHs needs to
be accurately
controlled in the
overlaid and
underlaid subcells.
NOTE
This parameter is
valid only if
AMRTCHHPRIO
RALLOW is set to
ON(On).
Threshold for OL INNAMRTCHHP You are advised to Network planning

Load with AMR RIORLOAD use the default
HR Preferred value.
For AMR calls in a
this parameter to a
small value if you
need to increase the
proportion of MSs
on TCHHs in the
overlaid subcell.
Set this parameter
to a large value if
you need to
decrease the
proportion of MSs
on TCHHs in the
overlaid subcell.
NOTE
This parameter is
valid only if
AMRLOADOPTE
N and
HRIUOLDRATES
ELALLOW are set
to YES(Yes), and
AMRTCHHPRIO
RALLOW is set to
ON(On).

GBSS14.0

Setting
Threshold for UL OUTAMRTCHHP You are advised to Network planning

Load with AMR RIORLOAD use the default
HR Preferred value.
For AMR calls in a
this parameter to a
small value if you
need to increase the
proportion of MSs
on TCHHs in the
underlaid subcell.
Set this parameter
to a large value if
you need to
decrease the
proportion of MSs
on TCHHs in the
underlaid subcell.
NOTE
This parameter is
valid only if
AMRLOADOPTE
N and
HRIUOLDRATES
ELALLOW are set
to YES(Yes), and
AMRTCHHPRIO
RALLOW is set to
ON(On).
TCHH Allocation JudgeRxLevWhe- You are advised to Network planning

Considering Signal nAssignHr set this parameter to
Level OFF(Off).
If this parameter is
set to ON(On), you
need to consider the
signal level when
assigning the
TCHHs. If the
signal level is too
low, assign the
TCHFs. There is no
need to consider the
signal level if this
parameter is set to
OFF(Off).

GBSS14.0

Setting
Level Threshold for MinRxLevWhenAs You are advised to Network planning

TCHH Allocation signHr use the default
value.
This parameter
specifies the lowest
signal level
threshold for
assigning AMR
calls the TCHHs.
The TCHFs
channels are
assigned to MSs if
the signal level is
lower than the
parameter value,
and otherwise the
TCHHs channels
are assigned to
MSs.
This parameter is
valid only when
JudgeRxLevWhe-
nAssignHr is set to
ON(On).
You are advised to
set this parameter to
a value smaller than
the maximum
transmit power of
TRXs in a cell
minus
AMRFULLTOH
ALFHOPATHTH
RESH.
For non-AMR calls,
the decision
principle is as
follows: When
NOAMRFULLT
OHALFHOALL
OW is set to NO
(No), TCHFs are
preferentially
assigned if the RX
signal level is lower
than the parameter
value plus 5.
Otherwise, TCHHs

GBSS14.0

Setting
are preferentially
assigned. When
NOAMRFULLT
OHALFHOALL
OW is set to YES
(Yes), TCHFs are
preferentially
assigned if the RX
signal level is lower
than the value (this
parameter value +
AMRFULLTOH
ALFHOPATHTH
RESH -
NOAMRFULLT
OHALFHOPATH
THRESH).
Otherwise, TCHHs
are preferentially
assigned.
Procedure
1. Run the BSC6900 MML command SET GTRXDEV (CME single configuration:
TRX Configuration Express > Site TRX Dev Property > Site TRX Dev
Property; CME batch modification center: 3.22 Modifying GSM TRX Parameters
in Batches) for each TRX you want to configure. In this step, set TCH Rate Adjust
Allow of a TRX to YES(Yes).
2. Run the BSC6900 MML commandSET GCELLCHMGAD (CME single
configuration: Cell Configuration Express > Channel Management > Advanced
Modifying GSM Cell Parameters in Batches) to set the threshold for dynamic
adjustment between TCHHs and TCHFs.
– For non-AMR calls in a common cell, set TCH Traffic Busy Threshold to an
appropriate value based on the actual requirement. For non-AMR calls in a
concentric cell whose Load of UL-OL Cells Rate Select Allowed is set to YES
(Yes), set Tch Traffic Busy Overlay Threshold and Tch Traffic Busy Underlay
– For AMR calls, set AMR TCH/H Prior Allowed to ON(On), and set other
parameters as follows:
– For common cells, set AMR TCH/H Prior Cell Load Threshold to an
appropriate value based on individual needs.
– For concentric cells, if Load of UL-OL Cells Rate Select Allowed and AMR
Load Calculation Optimization are not set to YES(Yes) at the same time, set
AMR TCH/H Prior Cell Load Threshold to an appropriate value based on
individual needs. If Load of UL-OL Cells Rate Select Allowed and AMR

GBSS14.0
Load Calculation Optimization are set to YES(Yes) at the same time, set
Threshold for OL Load with AMR HR Preferred for overlaid subcells and
Threshold for UL Load with AMR HR Preferred for underlaid subcells to
appropriate values.
– When the BSC preferentially assigns TCHHs, and TCHH Allocation
Considering Signal Level is set to ON(On), the BSC performs a decision on the
RX signal level in addition to the traffic volume. If the RX signal level is less than
the value for Level Threshold for TCHH Allocation, TCHFs are preferentially
assigned. If the RX signal level is greater than or equal to the value for Level
Threshold for TCHH Allocation, TCHHs are preferentially assigned.
Assume that non-AMR calls are performed in a common cell. Only the traffic volume,
instead of the RX signal level, is considered in assignment of TCHHs. The verification
procedure is as follows:
1. Monitor channel status by referring to Monitoring Channel Status.

2. Run the BSC6900 MML command SET GCELLCHMGAD. In this step, set TCH
Traffic Busy Threshold to 0 to ensure that new calls are preferentially assigned
TCHHs.
3. Use an MS to initiate a call in the cell.
A TCHF is converted into two TCHHs and are occupied by MSs.
Expected result: The TCHHs are not converted into a TCHF.
5. Run the BSC6900 MML command SET GTRXCHANADMSTAT. In this step, set
Administrative State to Lock(Lock) to block all TCHFs in the cell.
Traffic Busy Threshold to 100 to ensure that new calls are preferentially assigned
TCHFs.
NOTE
In Step 6, if the calling party and the called party camp on the same cell, reserve a TCHF to
ensure successful setup of the call.
The MS occupies a TCHF.
Assume that non-AMR calls are performed in a common cell. The traffic volume and RX
signal level are considered in assignment of TCHHs. The verification procedure is as
follows:
1. Monitor channel status by referring to Monitoring Channel Status.

2. Run the BSC6900 MML command SET GCELLCHMGAD to specify the
corresponding cell. In this step, set TCH Traffic Busy Threshold and Level
Threshold for TCHH Allocation to 0.
The MS occupies a TCHH.

GBSS14.0
Expected result: The TCHHs are not converted into a TCHF.

5. Run the BSC6900 MML command SET GCELLCHMGAD to change Level
Threshold for TCHH Allocation of the corresponding cell to 63.
The MS occupies a TCHF.
in Batches) for each TRX you want to configure. In this step, set TCH Rate Adjust
Allow to NO(No).
2. Run the BSC6900 MML command LST GTRXDEV (CME single configuration:
Property) to query the setting of TCH Rate Adjust Allow.
Expected result: The value of TCH Rate Adjust Allow is NO.
----End
Example
//Activating Dynamic Adjustment Between FR and HR
SET GCELLCHMGAD: IDTYPE=BYID, CELLID=0, TCHBUSYTHRES=60,
JudgeRxLevWhenAssignHr=ON, MinRxLevWhenAssignHr=15;
//Deactivating Dynamic Adjustment Between FR and HR
SET GTRXDEV: TRXID=0, TCHAJFLAG=NO;

GBSS14.0
Feature Activation Guide 62 Configuring Dynamic HR/FR Adaptation
62 Configuring Dynamic HR/FR

Adaptation
Dynamic HR/FR Adaptation.
Prerequisites
l License
– The test cell is enabled with the half-rate (HR) function. In addition, the test cell is
configured with available full-rate traffic channels (TCHFs) and half-rate traffic
channels (TCHHs).
Context
The Dynamic HR/FR Adaptation feature specifies dynamic adjustment of TCHH/TCHF
resources for established calls based on channel resource usage in the cell.
l If channel resources are sufficient, calls that use TCHHs but experience poor radio
transmission quality are handed over to TCHFs to improve the speech quality.
l If channel resources are insufficient, calls that use TCHFs and enjoy good radio
transmission quality are handed over to TCHHs to improve the cell capacity.
Procedure

GBSS14.0
Parameters in Batches). In this step, set its parameters based on actual conditions.
– When Current HO Control Algorithm is set to HOALGORITHM1(Handover
algorithm I), AMR calls support this feature if Intracell F-H HO Allowed is set
to YES(Yes); non-AMR calls and AMR calls support this feature if Intracell F-
H HO Allowed is set to HOBASECAPANDQUAL
(HOBASECAPANDQUAL), and AMR F-H Ho Allowed and Non-AMR F-H
Ho Allowed are set to YES(Yes).
– When Current HO Control Algorithm is set to HOALGORITHM2(Handover
algorithm II), non-AMR and AMR calls support this feature if Intracell HO
Allowed is set to YES(Yes), and AMR F-H Ho Allowed and Non-AMR F-H Ho
Allowed are set to YES(Yes).
2. Configure FR/HR call conversion.
– Convert full-rate calls to half-rate calls.
(Full-rate VER 2), FULL_RATE_VER3(Full-rate VER 3),
HALF_RATE_VER1(Half-rate VER 1), HALF_RATE_VER3(Half-
rate VER 3), and FULL_RATE_VER5(Full-rate VER 5).
Modifying GSM Cell Parameters in Batches). In this step, if Current HO
Control Algorithm is set to either HOALGORITHM1(Handover
algorithm I) or HOALGORITHM2(Handover algorithm II) and
Intracell F-H HO Allowed is set to HOBASECAPANDQUAL
(HOBASECAPANDQUAL), set the following parameters to appropriate
values based on actual conditions: AMR F-H Traffic Threshold, AMR F-
H Ho Qual. Threshold, AMR F-H HO Quality Thres. Fine Tune, AMR
F-H Ho Pathloss Threshold, AMR F-H Ho ATCB Threshold, AMR F-H
Ho Pathloss Adjust Step, AMR F-H Ho ATCB Adjust Step, Non-AMR
F-H Ho Qual. Threshold, Non-AMR F-H HO Quality Thres. Fine
Tune, Non-AMR F-H Ho Pathloss Threshold, Non-AMR F-H Ho ATCB
Threshold, Non-AMR F-H Ho Pathloss Adjust Step, Non-AMR F-H Ho
ATCB Adjust Step, F-H HO Load Band Optimization Allowed, TCHF-
TCHH HO Load Hysteresis, F-H Ho Duration, F-H Ho Period, F-H Ho
Stat. Time, and F-H Ho Last Time. For concentric cells, set
FULLTOHALFHOPATHOFFSET F-H Pathloss Offset Overlay and F-
H ATCB Offset Overlay to appropriate values based on actual conditions.
If Current HO Control Algorithm is set to HOALGORITHM1(Handover
algorithm I) and Intracell F-H HO Allowed is set to YES(Yes), set
Intracell F-H HO Stat Time, Intracell F-H HO Last Time, and F2H HO
Threshold based on actual conditions.
c. Run the BSC6900 MML command SET GCELLCHMGBASIC (CME
single configuration: Cell Configuration Express > Channel
Management > Basic Channel Management Parameters of Cell; CME
batch modification center: 3.20 Modifying GSM Cell Parameters in

GBSS14.0
Batches). In this step, set Ratio of AMR-HR and Ratio of TCHH based on
actual conditions.
d. Run the BSC6900 MML command SET GCELLCHMGAD (CME single
modification center: 3.20 Modifying GSM Cell Parameters in Batches). In
this step, set AMR TCH/H Prior Allowed and AMR TCH/H Prior Cell
Load Threshold based on actual conditions.
– Convert half-rate calls to full-rate calls.
(Full-rate VER 2), FULL_RATE_VER3(Full-rate VER 3),
HALF_RATE_VER1(Half-rate VER 1), HALF_RATE_VER3(Half-
rate VER 3), and HALF_RATE_VER5(Half-rate VER 5).
Modifying GSM Cell Parameters in Batches). In this step, if Current HO
Control Algorithm is set to either HOALGORITHM1(Handover
algorithm I) or HOALGORITHM2(Handover algorithm II) and
Intracell F-H HO Allowed is set to HOBASECAPANDQUAL
(HOBASECAPANDQUAL), set the following parameters to appropriate
values based on actual conditions: AMR H-F Traffic Threshold, AMR H-
F Ho Qual. Threshold, AMR H-F HO Quality Thres. Fine Tune, AMR
H-F Ho Pathloss Threshold, AMR H-F Ho ATCB Threshold, Non-AMR
H-F Ho Qual. Threshold, Non-AMR H-F HO Quality Thres. Fine
Tune, Non-AMR H-F Ho Pathloss Threshold, Non-AMR H-F Ho ATCB
Threshold, H-F Ho Duration, H-F Ho Stat. Time, and H-F Ho Last
Time. For concentric cells, set H-F Pathloss Offset Overlay and H-F ATCB
Offset Overlay. If Current HO Control Algorithm is set to
HOALGORITHM1(Handover algorithm I) and Intracell F-H HO
Allowed is set to YES(Yes), set H2F HO Threshold to an appropriate value
based on actual conditions.
NOTE
The following configuration is temperarily implemented to quickly bring this feature into effect. For a
commercial network, implement the configuration as planned. Restore to the original configuration after
the verification.
Convert full-rate calls to half-rate calls.

– If Current HO Control Algorithm is set to HOALGORITHM1(Handover
algorithm I) and Intracell F-H HO Allowed is set to YES(Yes):
1. Run the BSC6900 MML command SET GCELLCHMGAD. In this step, set
AMR TCH/H Prior Allowed to OFF(Off) in a specified cell.
2. Run the BSC6900 MML command SET GCELLHOBASIC. In this step, set F2H
HO Threshold to 0 in a specified cell.

GBSS14.0
3. Run the BSC6900 MML command SET GCELLCHMGBASIC. In this step, set
Ratio of AMR-HR to 100.
4. Trace BSSAP messages over the A interface and RSL messages over the Abis
interface by referring to Tracing Messages on the A Interface and Tracing CS
Domain Messages on the Abis Interface, respectively.
5. Use an MS to make a call in a cell where the message tracing over the A interface
and Abis interface is started.
6. Check the results of message tracing over the A interface and Abis interface.
Expected result: The calls have been set up and the voice quality is good. During the
call setup, the speech version in use is FAMR. During the call, the speech version
changes to HAMR. The Handover Detection and Handover Complete messages can be
traced over the Abis interface.
– If Current HO Control Algorithm is set to either HOALGORITHM1(Handover
algorithm I) or HOALGORITHM2(Handover algorithm II) and Intracell F-H HO
Allowed is set to HOBASECAPANDQUAL(HOBASECAPANDQUAL):
AMR TCH/H Prior Allowed to OFF(Off) in a specified cell.
2. Run the BSC6900 MML command SET GCELLHOBASIC. In this step, set
AMR F-H Traffic Threshold to 0, F-H HO Load Band Optimization
Allowed to OFF(Off), F-H Ho Period to 1, AMR F-H Ho Qual. Threshold to
7, AMR F-H Ho Pathloss Threshold to 255, AMR F-H Ho ATCB Threshold
to -63, Non-AMR F-H Traffic Threshold to 0, Non-AMR F-H Ho Qual.
Threshold to 7, Non-AMR F-H Ho Pathloss Threshold to 255, and set Non-
AMR F-H Ho ATCB Threshold to -63.
Ratio of AMR-HR and Ratio of TCHH to 100.
Convert half-rate calls to full-rate calls.
– If Current HO Control Algorithm is set to HOALGORITHM1(Handover

algorithm I) and Intracell F-H HO Allowed is set to YES(Yes):
AMR TCH/H Prior Allowed to ON(On), AMR TCH/H Prior Cell Load
Threshold to 0, and TCH Traffic Busy Threshold to 0 in a specified cell.
2. Run the BSC6900 MML command SET GCELLHOBASIC. In this step, set H2F
HO Threshold to 39 in a specified cell.
Ratio of AMR-HR to 100.

GBSS14.0
– If Current HO Control Algorithm is set to either HOALGORITHM1(Handover
algorithm I) or HOALGORITHM2(Handover algorithm II) and Intracell F-H HO
Allowed is set to HOBASECAPANDQUAL(HOBASECAPANDQUAL):
AMR TCH/H Prior Allowed to ON(On), AMR TCH/H Prior Cell Load
Threshold to 0, and TCH Traffic Busy Threshold to 0 in a specified cell.
AMR H-F Traffic Threshold to 100, F-H HO Load Band Optimization
Allowed to OFF(Off), AMR H-F Ho Qual. Threshold and AMR H-F HO
Quality Thres. Fine Tune to 0, and set Non-AMR H-F Ho Qual. Threshold and
Non-AMR H-F HO Quality Thres. Fine Tune to 0 in a specified cell.
Parameters in Batches). In this step, set AMR F-H Ho Allowed to NO(No).
2. Run the BSC6900 MML command LST GCELLHOBASIC (CME single
Parameters of Cell) to query the value of AMR F-H Ho Allowed.
Expected result: The value of AMR F-H Ho Allowed is NO(No).
Parameters in Batches). In this step, set Non-AMR F-H Ho Allowed to NO(No).
Parameters of Cell) to query the value of Non-AMR F-H Ho Allowed.

GBSS14.0
Expected result: The value of Non-AMR F-H Ho Allowed is NO(No).

Parameters in Batches). In this step, set Intracell F-H HO Allowed to NO(No).
Parameters of Cell) to query the value of Intracell F-H HO Allowed.
Expected result: The value of Intracell F-H HO Allowed is NO(No).
----End
Example
//Activating Dynamic HR/FR Adaptation when handover algorithm II is used

AMRFULLTOHALFHOALLOW=YES, NOAMRFULLTOHALFHOALLOW=YES;
//Activating Dynamic HR/FR Adaptation for AMR and non-AMR calls when
handover algorithm I is used
INTRACELLFHHOEN=HOBASECAPANDQUAL, AMRFULLTOHALFHOALLOW=YES,
NOAMRFULLTOHALFHOALLOW=YES;
//Activating Dynamic HR/FR Adaptation for AMR calls when handover
algorithm I is used
INTRACELLFHHOEN=YES;
//Deactivating Dynamic HR/FR Adaptation when handover algorithm II is
used
AMRFULLTOHALFHOALLOW=NO, NOAMRFULLTOHALFHOALLOW=NO;
//Deactivating Dynamic HR/FR Adaptation when handover algorithm I is used
INTRACELLFHHOEN=NO;

GBSS14.0
Feature Activation Guide 63 Configuring VAMOS
63 Configuring VAMOS
VAMOS.
Prerequisites
– Only the GRFU V1, GRFU V2, GRFU V2a, RRU3008 V1, RRU3008 V2, RRU3928,
RRU3929, MRFUd, and MRFUe of 3900 series base stations support VAMOS.
– VAMOS-capable MSs are classified into Non-SAIC, SAIC, VAMOS level I, and
VAMOS level II. At present, VAMOS level I and VAMOS level II MSs are not available
for commercial use.
– This feature cannot be used together with the feature GBFD-117501 Enhanced
Measurement Report(EMR), GBFD-117001 Flex MAIO, GBFD-510104 Multi-site
Cell, GBFD-113521 A5/1 Encryption Flow Optimization, GBFD-114001 Extended
Cell or GBFD-510101 Automatic Frequency Correction (AFC).
– In Abis over TDM mode, the configurations of the features on which this feature
depends are complete. This feature depends on the features GBFD-117601 Configuring
HUAWEI III Power Control Algorithm, GBFD-115502 AMR HR / GBFD-113401
Configuring Half Rate Speech (HR), GBFD-118103 Network Support SAIC, and
GBFD-117301 Flex Abis.
– In Abis over IP mode, the configurations of the features on which this feature depends
are complete. This feature depends on the features GBFD-117601 Configuring
HUAWEI III Power Control Algorithm, GBFD-115502 AMR HR/GBFD-113401
Configuring Half Rate Speech (HR), GBFD-118103 Network Support SAIC, and
GBFD-118601 Configuring Abis over IP / GBFD-118611 Configuring Abis IP over
E1/T1.
l License
– VAMOS supports the following transmission modes over the Abis interface: TDM in
Flex Abis mode, Ethernet IP, IP over E1, and high level data link control (HDLC).

GBSS14.0
– Double-timeslot cells and repeaters do not support VAMOS.

– VAMOS is incompatible with enhanced multi-level precedence and preemption
(eMLPP), that is, resources occupied by VAMOS-capable MSs cannot be preempted.
– VAMOS timeslots cannot be integrated for PS services.
Context
Voice services over Adaptive Multi-user Orthogonal Subchannels (VAMOS) aims to expand
the capacity of a GSM network without adding TRXs or frequencies. Without adding any
configurations, VAMOS increases the traffic volume.
Although VAMOS expands the network capacity and reduces the network congestion rate, it
affects the voice quality and deteriorates some other KPIs. Therefore, it is recommended that
the Half-Rate Service feature be enabled preferentially to expand network capacity and VAMOS
be enabled only when network capacity needs to be further expanded. VAMOS is not
recommended for users sensitive to voice quality.
VAMOS is applicable to scenarios with loose frequency reuse.
VAMOS deteriorates voice quality and causes interference to the entire network. Therefore, it
is recommended that VAMOS multiplexing be enabled to increase network capacity when
channels are congested in a cell and VAMOS demultiplexing be enabled to improve voice quality
when the cell load is low.
Call drops may occur if users dynamically add a carrier in a network where the VAMOS feature
has been enabled. Therefore, it is recommended that users perform this operation in low traffic
hours.
VAMOS multiplexing is classified into:
l VAMOS multiplexing during assignment
l VAMOS multiplexing through intra-cell handover
VAMOS demultiplexing is classified into:
l VAMOS demultiplexing due to low cell load
l VAMOS demultiplexing due to poor voice quality
l Optimization of VAMOS demultiplexing due to poor voice quality
NOTE
The BSS automatically resets the cell after you change the setting of the VAMOS Switch parameter. The BSS
forces inter-cell handovers for ongoing calls in the cell before resetting the cell and considers a handover failure
as a call drop.
Procedure
– Activating VAMOS multiplexing during assignment
1. Run the BSC6900 MML command SET GCELLPWR3 (CME single
configuration: Cell Configuration Express > Power Control > Parameters for
Power Control III of Cell; CME batch modification center: 3.20 Modifying GSM
Cell Parameters in Batches), In this step, set III Power Control Optimized
Enable to YES(Yes).
2. Run the BSC6900 MML command SET GCELLVAMOS (CME single
configuration: Cell Configuration Express > Call Control > VAMOS Channel

GBSS14.0
Multiplex Parameters of Cell; CME batch modification center: 3.20 Modifying

GSM Cell Parameters in Batches). In this step, set VAMOS Switch to ON
(On), set Allow Channel Multiplex in Assignment to ON(On), set Primary TSC
in VAMOS and Secondary TSC in VAMOS to appropriate values.
3. Run the BSC6900 MML command SET GCELLHOAD (CME single
GSM Cell Parameters in Batches). In this step, set Waiting for MR on SDCCH
Switch to ON(On), set Duration for Waiting MR on SDCCH to appropriate
values.
– Activating VAMOS multiplexing through intra-cell handover
Enable to YES(Yes).
(On), set Allow Channel Multiplex via In-Cell HO to ON(On), set Primary
TSC in VAMOS and Secondary TSC in VAMOS to appropriate values.
– Activating VAMOS demultiplexing due to low cell load
Enable to YES(Yes).
(On), set Channel Demultiplex on Low Cell Load to ON(On), set Primary TSC
in VAMOS and Secondary TSC in VAMOS to appropriate values.
– Activating VAMOS demultiplexing due to poor voice quality
Enable to YES(Yes).
(On), set Channel Demultiplex on Bad Qual. to ON(On), set Primary TSC in
VAMOS and Secondary TSC in VAMOS to appropriate values.
– Activating optimization of VAMOS demultiplexing due to poor voice quality

GBSS14.0
Enable to YES(Yes).
(On), Channel Demultiplex on Bad Qual. to ON(On), and BQ VAMOS
Channel Demultiplex Optimize to ON(On), and set Primary TSC in
VAMOS and Secondary TSC in VAMOS to appropriate values.
NOTE
the verification.
– Verifying VAMOS multiplexing during assignment
Assume that there are idle half-rate traffic channels (TCHHs) in cell 0, both MS 1 and
MS 2 support SAIC, the Abis interface uses IP transmission, and the BTS supports
VAMOS.
TCH Traffic Busy Threshold to 0 and AMR TCH/H Prior Allowed to OFF
(Off),set Load of UL-OL Cells Rate Select Allowed to NO(No).
both Ratio of TCHH and Ratio of AMR-HR to 100.
3. Run the BSC6900 MML command SET OTHSOFTPARA. In this step, set TCH
Rate Modify to YES(Yes).
4. Run the BSC6900 MML command SET GCELLVAMOS. In this step, set
VAMOS Switch to ON(On), Allow Channel Multiplex in Assignment to ON
(On), Channel Multiplex Load Thres. to 0, Channel Multiplex ATCB Thres.
Offset in Asgmt. to 0, ATCB Thres. of Established SAIC Calls to 1, Channel
Multiplex Rx Qual. Thres. Offset in Asgmt. to 0, UL Rx Qual. Thres. of
Established Calls to 70, DL Rx Qual. to 70, Path Loss Offset Thres. of VAMOS
Call to 63,Load Thres. in Overlaid Subcell to 0, and set ATCB Offset in
Overlaid Subcell to 128.
5. Start channel status monitoring in cell 0. Figure 63-1 shows the TCHH status in
cell 0.
Figure 63-1 TCHH status 1
6. Use MS 1 to call a fixed-line phone in cell 0. After the call is connected, use MS
2 to call another fixed-line phone in cell 0.
7. Check the TCHH status in cell 0.

GBSS14.0
Expected result: The calls are processed correctly and the call quality is good. MS 1 and
MS 2 are multiplexed on the same TCHH. Figure 63-2 shows the possible TCHH status
in cell 0.
– Verifying VAMOS multiplexing through intra-cell handover

Assume that there are idle TCHHs in cell 0, both MS 1 and MS 2 support SAIC, the
Abis interface uses IP transmission, and the BTS supports VAMOS.
(Off).
VAMOS Switch to ON(On), Channel Multiplex Load Thres. to 0, ATCB
Thres. of Established SAIC Calls to 1, UL Rx Qual. Thres. of Established
Calls to 70, DL Rx Qual. Thres. of Established Calls to 70, and Path Loss Offset
Thres. of VAMOS Call to 63.
cell 0.
Expected result: The calls are processed correctly and the call quality is good. MS
1 and MS 2 occupy their respective TCHHs during call establishment. Figure
63-4 shows the possible TCHH status in cell 0.

GBSS14.0
8. Several seconds later, MS 1 and MS 2 are multiplexed on the same TCHH. Figure
– Verifying VAMOS demultiplexing due to low cell load

(Off).
4. Run the BSC6900 MML command SET GCELLVAMOS. In this step, set both
VAMOS Switch and Channel Demultiplex on Low Cell Load to ON(On) and
set Load Thres. of Channel Demultiplex to 100.
cell 0.

GBSS14.0
8. Run the BSC6900 MML command SET FHO. In this step, trigger a VAMOS
multiplexing handover of an MS and check the TCHH status. Figure 63-8 shows
the possible TCHH status in cell 0.
9. Check the TCHH status in cell 0 several seconds later. Figure 63-9 shows the
possible TCHH status in cell 0.
Expected result: After VAMOS multiplexing through handover is performed

successfully, MS 1 and MS 2 are multiplexed on the same TCHH. Several seconds
later, VAMOS demultiplexing is triggered and MS 1 and MS 2 occupy their
respective TCHHs.
– Verifying VAMOS demultiplexing due to poor voice quality
(Off).
VAMOS Switch and Channel Demultiplex on Bad Qual. to ON(On) and set
both UL RX Bad Qual. Demultiplex Thres.. and DL RX Bad Qual. Demultiplex
Thres. to 0.
cell 0.

GBSS14.0
8. Run the BSC6900 MML command SET FHO. In this step, trigger a VAMOS
multiplexing handover of an MS and check the TCHH status. Figure 63-12 shows
the possible TCHH status in cell 0.
Expected result: After VAMOS multiplexing through handover is performed

successfully, MS 1 and MS 2 are multiplexed on the same TCHH. Several seconds
later, VAMOS demultiplexing is triggered and MS 1 and MS 2 occupy their
respective TCHHs.
– Verifying optimization of VAMOS demultiplexing due to poor voice quality
(Off).

GBSS14.0
cell 0.
7. Run the BSC6900 MML command SET FHO. In this step, use MS 1 or MS 2 to
perform a VAMOS handover and check the TCHH status in cell 0. Figure 63-16
shows the possible TCHH status in cell 0.
8. Enable the bad quality (BQ) handover algorithm to verify that the BSC allows only
handovers based on VAMOS demultiplexing due to poor voice quality and
prohibits other quality-based handovers (interference handovers, BQ handovers,
and TCHF-TCHH handovers). To enable the BQ handover algorithm, perform the
following operations:
a. Run the BSC6900 MML command SET GCELLHOBASIC. In this step,
set Intracell HO Allowed to YES(Yes) and BQ HO Allowed to YES
(Yes).

GBSS14.0
b. Run the BSC6900 MML command SET GCELLAMRQUL. In this step,

set DL Qual. Threshold to 0 and UL Qual. Threshold to 0.
c. Run the BSC6900 MML command SET GCELLAMRQUL. In this step,
set DL Qual. Limit for AMR FR to 0 and DL Qual. Limit for AMR HR
to 0.
Expected result: MS 1 and MS 2 remain in the multiplexing state and BQ handovers
are not performed.
VAMOS Switch to ON(On), Channel Demultiplex on Bad Qual. to ON(On),
BQ VAMOS Channel Demultiplex Optimize to ON(On), UL RX Bad Qual.
Demultiplex Thres. to 0, and DL RX Bad Qual. Demultiplex Thres. to 0.
Expected result: VAMOS demultiplexing is triggered several seconds after

optimization of VAMOS demultiplexing due to poor voice quality is activated.
Several seconds later, the MS whose speech quality is better performs a BQ
handover and the MS whose speech quality is poorer does not perform a BQ
handover until the BQ VAMOS Channel Demultiplex Penalty Period expires.
– Deactivating VAMOS multiplexing during assignment
(On) and Allow Channel Multiplex in Assignment to OFF(Off).
GSM Cell Parameters in Batches). In this step, set VAMOS Switch to OFF
(Off).
3. Run the BSC6900 MML command SET GCELLHOAD (CME single
GSM Cell Parameters in Batches). In this step, set Waiting for MR on SDCCH
Switch to OFF(Off).
– Deactivating VAMOS multiplexing through intra-cell handover

GBSS14.0

(On) and Allow Channel Multiplex via In-Cell HO to OFF(Off).
(Off).
– Deactivating VAMOS demultiplexing due to low cell load
(On) and Channel Demultiplex on Low Cell Load to OFF(Off).
(Off).
– Deactivating VAMOS demultiplexing due to poor voice quality
(On) and Channel Demultiplex on Bad Qual to OFF(Off).
(Off).
– Deactivating optimization of VAMOS demultiplexing due to poor voice quality
(On), Channel Demultiplex on Bad Qual. to ON(On), and BQ VAMOS
Channel Demultiplex Optimize to OFF(Off).
(On) and Channel Demultiplex on Bad Qual. to OFF(Off).
(off).
----End

GBSS14.0
Example
//Activating VAMOS multiplexing during assignment
SET GCELLPWR3: IDTYPE=BYID, CELLID=0, PWRCTRLOPTIMIZEDEN=YES;
SET GCELLVAMOS: IDTYPE=BYID, CELLID=0, VamosSwitch=ON,
VamosAssSwitch=ON,VamosMainTsc=0, VamosSubTsc=2;
SET GCELLHOAD: IDTYPE=BYID, CELLID=0, SDCCHWaitMREn=ON;
//Verifying VAMOS multiplexing during assignment

AMRTCHHPRIORALLOW=ON, HRIUOLDRATESELALLOW=NO;
SET GCELLCHMGBASIC: IDTYPE=BYID, CELLID=0, ALLOWHALFRATEUSERPERC=100,
ALLOWAMRHALFRATEUSERPERC=100;
SET OTHSOFTPARA: TCHRATEMODIFY=YES;
SET GCELLVAMOS: IDTYPE=BYID, CELLID=0, VamosSwitch=ON, VamosAssSwitch=ON,
VamosMultLoadThd=0, VamosAssMultAtcbOffset=0, VamosAssUlQualThdOffset=0,
VamosIntraHoSaicAtcbThd=1, VamosIntraHoUlQualThd=70,
VamosIntraHoDlQualThd=70, VamosPathLossMaxDiffValue=63,
VamosIuoInnerAtcbThd=128, VamosIuoInnerLoadThd=0;
//Deactivating VAMOS multiplexing during assignment

VamosAssSwitch=OFF;
SET GCELLVAMOS: IDTYPE=BYID, CELLID=0, VamosSwitch=OFF;
SET GCELLHOAD: IDTYPE=BYID, CELLID=0, SDCCHWaitMREn=OFF;
//Activating VAMOS multiplexing through intra-cell handover

VamosIntraHoSwitch=ON,VamosMainTsc=0, VamosSubTsc=2;
//Verifying VAMOS multiplexing through intra-cell handover

AMRTCHHPRIORALLOW=OFF;
SET GCELLCHMGAD: IDTYPE=BYID, CELLID=0,TCHBUSYTHRES=0;
VamosMultLoadThd=0, VamosIntraHoSwitch=ON, VamosIntraHoSaicAtcbThd=1,
VamosIntraHoUlQualThd=70, VamosIntraHoDlQualThd=70,
VamosPathLossMaxDiffValue=63;
//Deactivating VAMOS multiplexing through intra-cell handover

VamosIntraHoSwitch=OFF;
//Activating VAMOS demultiplexing due to low cell load

VamosLoadReuseSwitch=ON,VamosMainTsc=0, VamosSubTsc=2;
//Verifying VAMOS demultiplexing due to low cell load

SET GCELLCHMGAD: IDTYPE=BYID, CELLID=0,TCHBUSYTHRES=0,

GBSS14.0

VamosLoadReuseSwitch=ON, VamosLoadReuseLoadThd=100;
//Deactivating VAMOS demultiplexing due to low cell load

VamosLoadReuseSwitch=OFF;
//Activating VAMOS demultiplexing due to poor voice quality

VamosQualReuseSwitch=ON,VamosMainTsc=0, VamosSubTsc=2;
//Verifying VAMOS demultiplexing due to poor voice quality

VamosQualReuseSwitch=ON, VamosQualReuseDownLinkQualThd=0,
VamosQualReuseUpLinkQualThd=0;
//Deactivating VAMOS demultiplexing due to poor voice quality

VamosQualReuseSwitch=OFF;
//Activating optimization of VAMOS demultiplexing due to poor voice

quality
VamosQualReuseSwitch=ON, VamosQualUndoPntSwitch=ON,VamosMainTsc=0,
VamosSubTsc=2;
//Verifying optimization of VAMOS demultiplexing due to poor voice

quality
VamosQualReuseSwitch=ON, VamosQualUndoPntSwitch=ON,
VamosQualReuseDownLinkQualThd=0, VamosQualReuseUpLinkQualThd=0;
SET GCELLHOBASIC: IDTYPE=BYID, CELLID=0, INTRACELLHOEN=YES, BQHOEN=YES;
SET GCELLHOEMG: IDTYPE=BYID, CELLID=0, DLQUALIMIT=0, ULQUALIMIT=0;
SET GCELLAMRQUL: IDTYPE=BYID, CELLID=0, DLQUALIMITAMRHR=0,
ULQUALIMITAMRHR=0;
//Deactivating optimization of VAMOS demultiplexing due to poor voice
quality
VamosQualReuseSwitch=ON, VamosQualUndoPntSwitch=OFF;
VamosQualReuseSwitch=OFF;

GBSS14.0
Feature Activation Guide 64 Configuring Mute SAIC MS Identification
64 Configuring Mute SAIC MS

Identification
Mute SAIC MS Identification. (This feature cannot be configured using the CME. )
Prerequisites
– This feature cannot be used together with the GBFD-115702 TrFO feature.
This feature depends on GBFD-115830 VAMOS.
l License
– This feature is not applicable to the A over IP transmission mode because the results of
identifying mute SAIC-capable MSs be inaccurate.
Context
VAMOS aims to expand the GSM network capacity without adding TRXs or frequencies. Mute
SAIC MSs are the MSs that support SAIC but report Non-SAIC in CLASSMARK3. A non-
SAIC MS can only be multiplexed with a VAMOS Level II MS. However, VAMOS level II
MSs are not available for commercial use at present. To improve VAMOS multiplexing rate,
Huawei BSC provides an effective detection mechanism to identify the Mute SAIC MSs.
A database is created at the BSC to record whether an MS is a Mute SAIC MS. The BSC
differentiates Mute SAIC MSs from Non-SAIC MSs upon channel allocation.
The Mute VAMOS MS Identification is applicable in scenarios with loose frequency reuse and
limited network capacity. The MS drop off when the BSC When the Mute SAIC MS
identification is enabled, call drops may occur during detection of SAIC-capable MSs.

GBSS14.0
Procedure
1. Run the BSC6900 MML command SET GCELLVAMOS with its parameters set as
follows:
– Set Mute SAIC Terminal Processing Switch and Auto Mute SAIC
Identification Switch to ON(On).
– Set Average RX Qual Difference Threshold, Abnormal Average RX Qual
Times Threshold, and Periods for Auto Mute SAIC Identify to appropriate
values.
NOTE
The value of Abnormal Average RX Qual Times Threshold must be less than or equal to the
value of Periods for Auto Mute SAIC Identify. If the value of Periods for Auto Mute SAIC
Identify is constant, a larger value of Abnormal Average RX Qual Times Threshold indicates
that an MS is more likely to be identified as a mute SAIC MS. It is recommended that Abnormal
Average RX Qual Times Threshold be set to 1 when Periods for Auto Mute SAIC
Identify is set to the default value of 3.
2. Wait about one month.
3. Run the BSC6900 MML command EXP MSSAICCAPMML to export the mute
SAIC MS detection result in an MML script. In this step, set Export type to
NEWDATA(New generated data) and File Name to the name of the MML script.
The MML script file is saved in the \bam\version_x\ftp\ms_saic_cap path.
NOTE
l Use File Manager on the LMT to locate the script file in the save path.
l version_x refers to the active OMU workspace.You can run the LST OMUAREA command to
query it. The value of Workarea flag in the command output indicates the active OMU
workspace.
4. Run the MML script to import the mute SAIC MS identification result into the SAIC
MS capability database.
5. Run the BSC6900 MML command SET GCELLVAMOS to disable the mute SAIC
MS detection. In this step, set VAMOS Switch to ON(On), Mute SAIC Terminal
Processing Switch to ON(On), and Auto Mute SAIC Identification Switch to OFF
(Off).
Assume that there are idle TCHHs in cell 0, the Abis interface uses IP transmission, the
BTS supports VAMOS, and MS 1 and MS 2 are Mute SAIC MSs.
NOTE
operations are recommended only when you want to enable this feature immediately:
1. Run the BSC6900 MML command SET GCELLVAMOS. In this step, set VAMOS
Switch to ON(On), Allow Channel Multiplex via In-Cell HO to ON(On), Channel
Multiplex Load Thres. to 0, ATCB Thres. of Established SAIC Calls to 1, UL Rx
Qual. Thres. of Established Calls to 70, DL Rx Qual. Thres. of Established
Calls to 70, and Path Loss Offset Thres. of VAMOS Call to 63.
Traffic Busy Threshold to 0.
3. Run the BSC6900 MML command SET GTRXDEV. In this step, set TCH Rate
Adjust Allow to YES(Yes).

GBSS14.0
4. View the International Mobile Equipment Identity (IMEI) on the back of each MS or
input *#06# on each MS to display their respective IMEIs. The MS model and origin
comprise the initial 8-digit portion of the IMEI, known as type approval code (TAC).
5. Run the BSC6900 MML command ADD GMSSAICCAP. In this step, specify MS
1 as a Mute SAIC MS, and set TAC to the initial eight digits of the IMEI, Mute SAIC
Flag to YES(Yes), and Problem SAIC Flag to UNCERTAIN(Uncertain).
NOTE
If you are not sure whether an MS is a problem SAIC MS, set Problem SAIC Flag to
UNCERTAIN(Uncertain).
2 as a Mute SAIC MS, and set TAC to the initial eight digits of the IMEI, Mute SAIC
Flag to YES(Yes), and Problem SAIC Flag to UNCERTAIN(Uncertain).
7. Start channel status monitoring in cell 0. Figure 64-1 shows the TCHH status in cell
0.
8. Use MS 1 and MS 2 to call each other in cell 0.

9. Observe the TCHH status in cell 0. MS 1 and MS 2 occupy their respective TCHHs.
Figure 64-2 shows the possible TCHH status in cell 0.
10. Check whether two MSs are multiplexed a few seconds later. Figure 64-3 shows the
possible TCHH status in cell 0 after multiplexing.
VamosSwitch to ON(On) and Mute SAIC Terminal Processing Switch to OFF
(Off).
12. Run Step 8 through Step 10 again. The two MSs cannot be multiplexed.

GBSS14.0
Switch to ON(On) and Mute SAIC Terminal Processing Switch to OFF(Off).
----End
Example
//Activating Mute SAIC MS identification
SET GCELLVAMOS: IDTYPE=BYID, CELLID=0, VamosSwitch=ON, MuteSaicSwitch=ON;
SET GCELLVAMOS: IDTYPE=BYID, CELLID=0, VamosSwitch=ON, MuteSaicSwitch=ON,
MuteSaicIdeSwitch=OFF;
//Verifying Mute SAIC MS identification

VamosMultLoadThd=0, VamosIntraHoSwitch=ON, VamosIntraHoSaicAtcbThd=1,
VamosIntraHoUlQualThd=70, VamosIntraHoDlQualThd=70,
VamosPathLossMaxDiffValue=63;
SET GCELLCHMGAD: IDTYPE=BYID, CELLID=0, TCHBUSYTHRES=0;
SET GTRXDEV: IDTYPE=BYID, TRXID=0, TCHAJFLAG=YES;
ADD GMSSAICCAP: TAC="11111111", MuteSAICFlag=YES, ProSAICFlag=UNCERTAIN;
ADD GMSSAICCAP: TAC="22222222", MuteSAICFlag=YES, ProSAICFlag=UNCERTAIN;
MuteSaicSwitch=OFF;
//Deactivating Mute SAIC MS identification

SET GCELLVAMOS: IDTYPE=BYID, CELLID=0, VamosSwitch=ON, MuteSaicSwitch=OFF;

GBSS14.0
Feature Activation Guide 65 Configuring VAMOS Call Drop Solution
65 Configuring VAMOS Call Drop

Solution
VAMOS Call Drop Solution. (This feature cannot be configured using the CME. )
Prerequisites
– This feature cannot be used together with the GBFD-115702 TrFO feature.
– The feature GBFD-115830 VAMOS has been configured before this feature is
activated.
l License
– This feature is not applicable to the A over IP transmission mode because the results of
identifying defective SAIC-capable MSs may be inaccurate.
Context
VAMOS aims to expand the GSM network capacity without adding TRXs or frequencies. Test
results, however, indicate that call drops are likely to occur after SAIC-capable MSs are
multiplexed with other MSs. To obtain the desired capacity gain through VAMOS, the BSC
provides a mechanism to identify defective SAIC-capable MSs so that these MSs can be
multiplexed with other suitable MSs based on support capability. In addition, the BSC uses a
power control policy specific to defective SAIC-capable MSs to ensure speech quality.
A database is created at the BSC to record whether the MSs under the BSC have defects in SAIC.
All the MSs under the BSC are classified into three types: defective SAIC-capable MSs that
cannot use VAMOS, defective SAIC-capable MSs that can use VAMOS but require alpha
hopping modulation, and normal SAIC-capable MSs that can use VAMOS but require alpha-
QPSK modulation. Before allocating a channel to an MS, the BSC determines the MS type and
the required modulation scheme by checking the records in the database.

GBSS14.0
The VAMOS call drop solution is applicable in scenarios with loose frequency reuse and limited
network capacity.When the VAMOS call drop solution is enabled, call drops may occur during
detection of SAIC-capable MSs with AFC defects.
Procedure
1. Run the BSC6900 MML command SET GCELLVAMOS with its parameters set as
follows:
– Set Problem SAIC Terminal Processing Switch and Problem SAIC Terminal
Identify Switch to ON(On).
– Set Faulty SAIC MS Mean RX Qual Differ Thres, Faulty SAIC MS Mean RX
Qual Abnor Thres, and Auto Identify Periods for Faulty SAIC MSto
appropriate values.
NOTE
If the value of Auto Identify Periods for Faulty SAIC MS is constant, a larger value of Faulty
SAIC MS Mean RX Qual Abnor Thres indicates that an MS is more likely to be identified as
a SAIC MS that allows VAMOS channel multiplexing using the Alpha hopping modulation. It
is recommended that Faulty SAIC MS Mean RX Qual Abnor Thres be set to 1 when Auto
Identify Periods for Faulty SAIC MS is set to the default value of 3.
2. Wait about one month.
3. Run the BSC6900 MML command EXP MSSAICCAPMML to export the problem
SAIC MS detection result in an MML script. In this step, set Export typeto
NEWDATA(New generated data) and File Name to the name of the MML script.
The MML script file is saved in the \bam\version_x\ftp\ms_saic_cap path.
NOTE
l Use File Manager on the LMT to locate the script file in the save path.
l version_x refers to the active OMU workspace. You can run the LST OMUAREA command
to query it. The value of Workarea flag in the command output indicates the active OMU
workspace.
4. Run the MML script to import the problem SAIC MS identification result into the
SAIC MS capability database.
5. Run the BSC6900 MML command SET GCELLVAMOS with VAMOS Switch set
to ON(On), Problem SAIC Terminal Processing Switch set to ON(On), and
Problem SAIC Terminal Identify Switch set to OFF(Off).
Assume that there are idle TCHHs in cell 0, IP transmission is used over the Abis interface,
the BTS supports VAMOS, and MS 1 and MS 2 are SAIC-capable but MS 2 has defects
in SAIC.
NOTE
operations are recommended only when you want to enable this feature immediately:
Switch to ON(On) and Problem SAIC Terminal Processing Switch to OFF(Off).
Traffic Busy Threshold to 0.
3. Run the BSC6900 MML command SET GTRXDEV. In this step, set TCH Rate
Adjust Allow to YES(Yes).

GBSS14.0
4. Initiate channel status monitoring in cell 0. Figure 65-1 shows the TCHH status in
cell 0.
5. Use MS 1 and MS 2 to call each other in cell 0.

6. Check the TCHH status in cell 0. MS 1 and MS 2 occupy their respective TCHHs.
Figure 65-2 shows the possible TCHH status in cell 0.
7. Run the BSC6900 MML command SET FHO. In this step, hand over an MS for
VAMOS multiplexing. MS 1 and MS 2 are multiplexed on the same TCHH. Figure
8. A call drop occurs on defective SAIC-capable MS 2 a few seconds later.

VAMOS Switch and Problem SAIC Terminal Processing Switch to ON(On).
10. View the International Mobile Equipment Identity (IMEI) on the back of each MS or
input *#06# on each MS to display their respective IMEIs. The MS model comprises
the initial 8-digit portion of the IMEI, known as type approval code (TAC).
1 as a normal SAIC-capable MS, and set TAC to the first eight digits of the IMEI of
MS 1, Mute SAIC Flag to NOTINVOLVED(Not involved), and Problem SAIC
Flag to NOTINVOLVED(Not involved).
2 as a defective SAIC-capable MS, and set TAC to the first eight digits of the IMEI
of MS 2, Mute SAIC Flag to NOTINVOLVED(Not involved), and Problem SAIC
Flag to JUMP_ALPHA(Alpha hopping modulation).
13. Repeat Step 5 through Step 7 to multiplex MS 1 and MS 2 on the same TCHH. MS
2 does not experience a call drop.

GBSS14.0
Expected result: When Problem SAIC Flag is set to NO(No), a call drop occurs in
MS 2 after being multiplexed with normal SAIC-capable MS 1. When Problem SAIC
Flag is set to YES(Yes), MS 2 does not experience a call drop after being multiplexed
with normal SAIC-capable MS 1.
Switch to ON(On) and Problem SAIC Terminal Processing Switch to OFF(Off).
----End
Example
//Activating VAMOS Call Drop Solution
SaicProMsSwitch=ON;
SaicProMsSwitch=ON, SaicProMsIdeSwitch=OFF;
//Verifying VAMOS Call Drop Solution
SaicProMsSwitch=OFF;
SET GCELLCHMGAD: IDTYPE=BYID, TCHBUSYTHRES=0;
SET GTRXDEV: IDTYPE=BYID, TRXID=0, TCHAJFLAG=YES;
SET FHO: OBJTYPE=CHN, TRXID=0, CHNO=1, HOMOD=VAMOSREUSE, SUBCHNO=0,
DESTTRXID=1, DESTCHNO=7, DESTSUBCHNO=0;
SaicProMsSwitch=ON;
ADD GMSSAICCAP: TAC="11111111", MuteSAICFlag=NOTINVOLVED,
ProSAICFlag=NOTINVOLVED;
ADD GMSSAICCAP: TAC="22222222", MuteSAICFlag=NOTINVOLVED,
ProSAICFlag=JUMP_ALPHA;
//Deactivating VAMOS Call Drop Solution

SaicProMsSwitch=OFF;

GBSS14.0 66 Configuring Short Message Service Cell Broadcast
Feature Activation Guide (TS23)
66 Configuring Short Message Service Cell

Broadcast (TS23)
Short Message Service Cell Broadcast (TS23).
Prerequisites
– An XPUa/XPUb board is configured.
– This feature cannot be used together with the feature GBFD-113602 Simplified Cell
Broadcast.
l License
– The cell broadcast center (CBC) works properly and supports handshake with the BSC.
– The hardware and software of the CBC and the corresponding networking equipment
are installed.
Procedure
1. Run the BSC6900 MML command MOD GCNOPERATOR (CME single
GSM Operator; CME batch modification center: not supported) to modify the
attributes for a GSM operator. In this step, set Support Cell Broadcast to
SPPRTSTANDARD(SupportStandard CB).
2. Run the BSC6900 MML command ADD XPUVLAN (CME single configuration:
Device Panel > Right clink XPU Board > Properties > VLAN Attributes of XPU
board; CME batch modification center: not supported) to add the VLAN attributes
of the XPU board. In this step, specify IP Address as required and set the VLAN
attributes at the BSC6900 that is connected to the CBC.

3. Run the BSC6900 MML command SET XPUPORT (CME single configuration:
Device Panel > Right clink XPU Board > Properties > Port Attributes of XPU
Board; CME batch modification center: not supported) to set the attributes of ports
on the XPU board. In this step, set Panel Port Switch to OPEN(Open).
4. Run the BSC6900 MML command ADD GCBSADDR (CME single configuration:
GSM Global Configuration Express > BSC Basic Configuration > CBC
Address; CME batch modification center: not supported) to add CBC address. In this
step, set the following parameters:
– Set CBC INDEX to appropriate value.
– Set OP INDEX SET to the index of the operator to which the cell to be verified
belongs.
– Set Subrack No., Slot No., CPU NO, and BSC IP to those of the XPU board
added by Run the BSC6900 MML command ADD XPUVLAN (CME single
configuration: Device Panel > Right clink XPU Board > Properties > VLAN
Attributes of XPU board; CME batch modification center: not supported)
command.
– Set BSC Port to appropriate value.
– Set BSC GateWay IP to the gateway IP address of the lab.
– Set CBC IP to the IP address of the CBC.
– Set Mask to appropriate value.
– Set CBC Port to appropriate value.
– Set If CB Shake Hand to YES(Yes).
– Set CBC ITF Para to appropriate value.
5. Run the BSC6900 MML command SET GTRXCHAN (CME single configuration:
TRX Configuration Express > Channel Type > Channel Type; CME batch
modification center: 3.22 Modifying GSM TRX Parameters in Batches) to set TRX
and channel attributes. In this step, specify Channel No., and set TRX ID to the index
of the BCCH TRX in the cell to be verified and Channel Type to BCCH_CBCH
(BCCH+CBCH) or SDCCH_CBCH(SDCCH+CBCH).
NOTE
If Channel Type is set to SDCCH_CBCH(SDCCH+CBCH), set TRX ID to the index of any
TRX and Channel No. to a value within the range 0 to 3.
6. Add the settings of the BSC, cell, area, channel, and user on the CBC side, and divide
cells into different cell groups. In addition, send cell broadcast messages to the cells.
1. Connect an Ethernet cable to the port whose Panel Port Switch is set to OPEN
(Open). Then, Ensure that the IP address of this port can be pinged.
Expected result: The IP address can be pinged. The port works properly.
2. Use an MS enabled with the CBC function to access the network in different cells,
and initiate message tracing on the BSC-CBC(Cb interface) and Abis interfaces.
Expected result:
In the initial phase of connection, the messages CBCH Query and CBCH Query
Response are traced on the BSC-CBC interface.
When system information messages are sent, messages Write/Replace Message and
Report are traced on the BSC-CBC interface.
The SMS Broadcast Command message is traced on the Abis interface.

The MS properly receives the cell broadcast messages sent from the CBC.
1. Run the BSC6900 MML command RMV GCBSADDR (CME single configuration:
GSM Global Configuration Express > BSC Basic Configuration > CBC
Address; CME batch modification center: not supported). In this step, remove CBC
information add in step4.
2. Run the BSC6900 MML command RMV XPUVLAN (CME single configuration:
Device Panel > Right clink XPU Board > Properties > VLAN Attributes of XPU
board; CME batch modification center: not supported). In this step, remove the VLAN
attributes of the XPU board add in step2.
GSM Operator; CME batch modification center: not supported). In this step, set
Support Cell Broadcast to NOTSPPRTBC(NotSupport CB).
----End
Example
/*Activating Short Message Service Cell Broadcast (TS23)*/
//Enabling cell broadcast
MOD GCNOPERATOR: OPINDEX=0, SpprtCB=SPPRTSTANDARD;
//Setting the VLAN attributes of the XPU board
ADD XPUVLAN: SRN=0, SN=0, SSN=1, MAC=0, IP="10.161.72.185",
NETMASK="255.255.255.0";
//Setting attributes of the port on the XPU board
SET XPUPORT: SRN=0, SN=0, PortSwitch=OPEN;
//Adding CBC information
ADD GCBSADDR: CBCINDEX=0,
OPINDEXSET=OPINDEX0-1&OPINDEX1-0&OPINDEX2-0&OPINDEX3-0, SRN=0, SN=0,
CPUN=1, BSCIP="10.161.72.185", BSCPORT=5000, BSCGATEWAYIP="19.168.6.1",
CBCIP="19.168.6.20", MASK="255.255.255.0", CBCPORT=6000;
//Setting TRX parameters
SET GTRXCHAN: TRXID=0, CHNO=0, CHTYPE=BCCH_CBCH;
/*Deactivating Short Message Service Cell Broadcast (TS23)*/
//Remove CBC information
RMV GCBSADDR: CBCINDEX=0;
//Remove the VLAN attributes of the XPU board
RMV XPUVLAN: SRN=0, SN=0, SSN=1;
//Disabling cell broadcast
MOD GCNOPERATOR: OPINDEX=0, SpprtCB=NOTSPPRTBC;

GBSS14.0
Feature Activation Guide 67 Configuring Simplified Cell Broadcast
Simplified Cell Broadcast. (This feature cannot be configured using the CME. )
Prerequisites
– The XPUa/XPUb board is configured.
– This feature cannot be used together with the feature GBFD-113601 Short Message
Service Cell Broadcast (TS23).
l License
Context
The Simplified Cell Broadcast feature provides simple cell broadcast services when there is no
available CBC system.
Procedure
1. Run the BSC6900 MML command MOD GCNOPERATOR to modify the attributes
of a GSM operator. In this step, set Support Cell Broadcast to SPPRTSIMPLE
(SupportSimple CB).
2. Run the BSC6900 MML command SET GTRXCHAN. In this step, set Channel
No., and set TRX ID to the index of the BCCH TRX in the cell to be verified and
Channel Type to BCCH_CBCH(BCCH+CBCH).
NOTE
If Channel Type is set to SDCCH_CBCH(SDCCH+CBCH), set TRX ID to the index of any
TRX and Channel No. to a value within the range 0 to 3.
3. Send cell broadcast messages.
– Sending a specified message without any restrictions

GBSS14.0
Feature Activation Guide 67 Configuring Simplified Cell Broadcast
a. Run the BSC6900 MML command SET GCELLSBC. In this step, set Cell
Index to the index of the cell to be verified and set Support Cell Broadcast
Name to YES(Yes). Set Chan ID, Geography Scope, Broadcast Content,
Coding Scheme, and Broadcast Interval to appropriate values.
– Sending a specified message at a specified time a specified number of transmission
times
a. Run the BSC6900 MML command ADD GSMSCB. In this step, set Cell
Index List to the index of the cell to be verified, Geography Scope to
LAC_CI(CELL IMME), Code to 1, and Update to 0. In addition, set
Repeat and Broadcast Interval, set Start Time and End Time to the
specified time, and set Chan ID, Coding Scheme, and Content of
Message to appropriate values.
NOTE
l The time specified by End Time in the ADD GSMSCB command must be later than the
current time displayed on the OMU.
l When Repeat and Broadcast Interval are both set to 60, StartTime and EndTime must
be set to values later than the current time displayed on the OMU and the interval between
the two values must be longer than 1 hour to ensure that the simple broadcast message can
be successfully transmitted 60 times.
1. On the LMT, start an Abis interface CS trace task with trace type set to RSL. For
details on how to start the task, see Tracing CS Domain RSL Messages on the Abis
Interface in the LMT User Guide. Set the same channel on the MS side as the channel
specified by CHANID in Step 3 (the setting procedure depends on the MS brand).
The SMS Broadcast Command message can be traced on the Abis interface. The MS
can receive the BROADCASTCONTENT specified in Step 3.
NOTE
BROADCASTCONTENT set through the SET GCELLSBC command can be received at

any time. BROADCASTCONTENT set through the ADD GSMSCB command can be
received only within the specified time period.
1. Run the BSC6900 MML command MOD GCNOPERATOR with Support Cell
Broadcast set to NOTSPPRTBC(NotSupport CB).
----End
Example
//Supporting Simplified Cell Broadcast
MOD GCNOPERATOR: OPINDEX=0, SpprtCB=SPPRTSIMPLE;
//Setting TRX and channel attributes
SET GTRXCHAN: TRXID=0, CHNO=0, CHTYPE=BCCH_CBCH;//
//Sending cell broadcast messages
SET GCELLSBC: IDTYPE=BYID, CELLID=0, SUPPORTCELLBROADCAST=YES, GS=LAC_CI,
CHANID=0, SCHEME=ENGLISH, BROADCASTCONTENT="Happy", BROADCASTINTERVAL=60;
//Not supporting Simplified Cell Broadcast
MOD GCNOPERATOR: OPINDEX=0, SpprtCB=NOTSPPRTBC;

GBSS14.0
Feature Activation Guide 68 Configuring VGCS and VBS
68 Configuring VGCS and VBS
This section describes how to activate, verify, and deactivate Voice Group Call Service (VGCS)
and Voice Broadcast Service (VBS).
Prerequisites
– The test cell is configured with the VGCS function and VGCS ID at the MSC.
– Non-single channel originating is configured at the MSC.
– VGCS and VBS are enabled for the IMSIs used in this test at the HLR.
– Two test MSs, MS1 and MS2, that support VGCS and VBS are available.
l License
– The test cell has idle TCHs.
– Channel status monitoring of the test cell is started. For details, see Monitoring Channel
Status.
– The BTS3012/BTS3012AE (configured with QTRUs), BTS3900B, and BTS3012E do
not support this feature.
Context
Compared with GSM, GSM-R provides new features, such as VGCS, VBS, and enhanced Multi-
Level Precedence and Preemption (eMLPP) service. GSM-R can provide diversified voice
dispatch services required in the private network.
A cell does not support VGCS or VBS by default, that is, the default value of NCH Occupy
Block Number is 0. Configure VGCS and VBS by setting NCH Occupy Block Number and
NCH Start Block. When NCH Occupy Block Number is not 0, the BSC informs the MS of
the NCH information in system information type 1. The MS initiates a VGCS/VBS call after
receiving the message indicating that the system supports VGCS/VBS.

GBSS14.0
Procedure
1. Run the BSC6900 MML command SET GCELLGSMR (CME single configuration:
Cell Configuration Express > Call Control > GSM-R Parameters of Cell; CME
this step, set NCH Occupy Block Number and NCH Start Block to appropriate
values.
NOTE
l NCH Occupy Block Number must be set to a value other than 0. The sum of NCH Occupy
Block Number and NCH Start Block must be smaller than or equal to the value of CCCH
Blocks Reserved for AGCH. Run the BSC6900 MML command LST
GCELLIDLEBASIC (CME single configuration: Cell Configuration Express > Idle
Mode > Idle Basic Parameters of Cell) to query the value of CCCH Blocks Reserved
for AGCH.
– Verifying VGCS
1. Use MS1 to perform VGCS in the test cell.
2. On the LMT, open the A Interface Trace dialog box and select BSSAP.
Expected result: The messages VGCS/VBS Setup, VGCS/VBS Setup Ack,
VGCS/VBS Assignment Request, VGCS/VBS Assignment Result, and VGCS/
VBS Talker Information are traced on the A interface.
3. Check the status of the TCHs in the test cell. You can see that besides the TCH for
VGCS, another TCH is occupied and this TCH is released 5 seconds later.
NOTE
A calling session lasts for 5 seconds after pressing the push-to-talk (PTT) key. To prolong the
calling session, press and hold down the PTT key for as long as necessary.
4. Use MS2 to perform VGCS with the same VGCS ID as MS1 in the test cell.
Expected result: MS2 is notified that the VGCS already exists. After adding MS2
to the ongoing VGCS, you can view the current VGCS ID from the screen of MS2.
5. Press the PTT key on MS2 to occupy the uplink resources. Then check the traced
messages displayed in the A Interface Trace window and on the MS1.
Expected result: The messages Uplink Request, Uplink Request Ack, Uplink
Request Confirmation, and VGCS/VBS Talker Information are traced on the
A interface. You can use MS1 to view the MS2 phone number and hear the voice
from MS2.
6. Press the PTT key on MS2 and then on MS1 to occupy the uplink resources. The
occupation attempt of MS1 is rejected.
– Verifying VBS
1. Use MS1 to perform VBS in the test cell.
2. On the LMT, open the A Interface Trace dialog box and select BSSAP.
Expected result: The messages VGCS/VBS Setup, VGCS/VBS Setup Ack,
VGCS/VBS Assignment Request, and VGCS/VBS Assignment Result are
traced on the A interface.
3. Check the status of the TCHs in the test cell. You can see that besides the TCH for
VBS, another TCH is occupied.
4. Use MS1 to perform VBS with the same VBS ID as MS1 in the test cell.

GBSS14.0
Expected result: MS2 is notified that the VBS already exists. After adding MS2 to
the ongoing VBS, you can view the current VBS ID from the screen of MS2.
this step, set NCH Occupy Block Number to 0.
----End
Example
/*Activating VGCS and VBS*/
//Enabling VGCS and VBS
SET GCELLGSMR: IDTYPE=BYID, CELLID=0, NCHOCBLOCKNUM=1, NCHSTARTBLOCK=1;
/*Deactivating VGCS and VBS*/
//Disabling VGCS and VBS
SET GCELLGSMR: IDTYPE=BYID, CELLID=0, NCHOCBLOCKNUM=0;

GBSS14.0
Feature Activation Guide 69 Configuring GSM-T Relay
69 Configuring GSM-T Relay
GSM-T Relay.
Prerequisites
– The MS, MSC, and HLR need to support this feature.
– The BTS has been upgraded to a version that supports trunking services. The earliest
version that supports trunking services on a pulic network is BTS3000V300R009C01.
The recommended version is GBSS13.0.
– The MS supports trunking services.
l License
Context
If a BSC supports GSM-T Relay, the BSC is connected to both the public MSC and the trunking
MSC. By routing trunking services to the trunking MSC, the BSC separates the networking of
trunking services and point-to-point call services.
Procedure
batch modification center: not supported) to add a signaling point of the trunking MSC.
In this step, set DSP index according to the network planning, and set DSP type to
A(A) and DSP bear type to MTP3(MTP3).
2. Run the BSC6900 MML command ADD GCNNODE (CME single configuration:
Node; CME batch modification center: not supported) to add a CN node. In this step,

GBSS14.0
set CN Node Index, DPC Group Index, and Operator Name according to the
network planning; set MSC ID to a value that identifies a trunking MSC; set DSP
index to the value specified in Step 1; set Default DPC to NO(Not Default DPC),
Trunking MSC to YES(Yes), and Support Paging Message from Trunking
MSC to YES(Yes).
modification center: not supported) to add an E1/T1 on the A interface.
signaling link set. In this step, set Signalling link set index according to the network
planning.
Signalling Link; CME batch modification center: not supported) to add an MTP3
signaling link. In this step, set Signalling link set index to the value specified in Step
4 and set TC mode based on the subrack combination mode.
modification center: not supported) to add an MTP3 route. In this step, set DSP
index to the index of the DSP added in Step 1 and Signalling link set index to the
index of the signaling link set added in Step 4.
this step, set NCH Occupy Block Number of the target cell to a value that is not less
than 1.
1. On the LMT, start the A interface message tracing by referring to Tracing BSSAP
Messages on the A Interface. In this step, set Trace Type to BSSAP and DPC
(Hex) to the DPC of the trunking MSC.
2. On the BSSAP tab page, set Cell ID(cell1,cell2,...cell16) to the ID of the target cell
specified in Step 7. Then, click Submit. The A Interface Trace message window is
displayed.
3. Initiate a successful VGCS call. Then, check the messages traced on the A interface.
Expected result: The A interface signaling of the VGCS initiating MS is displayed in
the A interface tracing window.
1. Run the BSC6900 MML command MOD GCNNODE (CME single configuration:
Node; CME batch modification center: not supported). In this step, set Default
DPC to NO(Not Default DPC), and Trunking MSC to NO(No).
----End
Example
//Configuring a DPC

GBSS14.0
ADD N7DPC: NAME="dpc", DPX=1, SPX=0, SPDF=WNF, DPC=1111, DPCT=A,

BEARTYPE=MTP3;
//Configuring a CN node of a trunking MSC
ADD GCNNODE: CNNODEIDX=0, DPX=1, DPCGIDX=0, OPNAME="op1", CNID=0,
DFDPC=NO, SaGsmrMsc=YES, SptPaging=YES, ATransMode=TDM;
//Configuring an E1/T1 over the A Interface
//Configuring an MTP3 signaling link set
ADD MTP3LKS: SIGLKSX=1, DPX=0, NAME="MTP3LKS";
//Configuring an MTP3 signaling link
MTP2LNKN=0, LKTATE=64K, NAME="MTP3LNK";
//Configuring an MTP3 route
ADD MTP3RT: DPX=1, SIGLKSX=1, NAME="MTP3RT";
//Setting GSM-R parameters of a cell
SET GCELLGSMR: IDTYPE=BYID, CELLID=0, NCHOCBLOCKNUM=1;
//Modifying parameters of a CN node
MOD GCNNODE: CNNODEIDX=0, DFDPC=NO, SaGsmrMsc=NO;

GBSS14.0
Feature Activation Guide 70 Configuring LCS (cell ID + TA)
70 Configuring LCS (cell ID + TA)
LCS (cell ID + TA).
Prerequisites
l License
– The CN must support this feature.
– The MSC supports the LCS.
– The test cell is operational, and idle channels are available in the test cell.
Context
LCS is used to locate an MS with precision of a certain level and provide a series of specific
services based on the location of the MS. For example, LCS can locate an MS that initiates an
emergency call or provide information about the MS location for other value added services
(VASs). LCS can be categorized into three types: NSS-based LCS (cell ID + TA), BSS-based
LCS (cell ID + TA), and simple mode LCS (cell ID + TA). In the NSS-based LCS (cell ID +
TA), the BSC provides the cell ID and TA of an MS for the MSC, and then the MSC calculates
the MS location. In the BSS-based LCS (cell ID + TA), the BSC calculates the MS location
based on the cell ID and TA of the MS and sends the location information to the MSC. In the
simple mode LCS (cell ID + TA), the BSC calculates the MS location based on the cell ID and
TA of the MS and sends the location information to the MS through single user trace messages.
Procedure
l NSS-based LCS in idle mode (cell ID + TA) Activation Procedure

GBSS14.0
1. Run the BSC6900 MML command SET AITFOTHPARA (CME single

center: not supported). In this step, set ESTINDL3MSGTAFLAG to OPEN
(Open).
l NSS-based LCS (cell ID + TA) in dedicated mode Activation Procedure
1. Run the BSC6900 MML command ADD GEXTSMLC (CME single configuration:
GSM Global Configuration Express > BSC Basic Configuration > External
SMLC Information; CME batch modification center: not supported), In this setp, set
SMLC Mode to INNER(Inner).
center: not supported). In this step, set ESTINDL3MSGTAFLAG to OPEN
(Open).
l BSS-based LCS (cell ID + TA) Activation Procedure
SMLC Information; CME batch modification center: not supported) to add settings
of the SMLC to the test cell. In this step, set SMLC Mode to INNER(Inner).
NOTE
Run the BSC6900 MML command LST GCELL (CME single configuration: Cell
Configuration Express > Cell Attributes > GSM CELL) to obtain Operator Name.
2. Run the BSC6900 MML command SET GCELLLCS (CME single configuration:
Cell Configuration Express > LCS Parameters > LCS Parameters of Cell; CME
configure the LCS parameters of a cell.
l Simple Mode LCS (Cell ID + TA) Activation Procedure
SMLC Information; CME batch modification center: not supported) to add SMLC
configurations to the operator of the test cell. In this step, set SMLC Mode to INNER
(Inner).
NOTE
To obtain the operator of a cell, Run the BSC6900 MML command LST GCELL (CME single
configuration: Cell Configuration Express > Cell Attributes > GSM CELL). Operator
Name in the returned result specifies the operator.
2. Run the BSC6900 MML command SET GCELLLCS (CME single configuration:
Cell Configuration Express > LCS Parameters > LCS Parameters of Cell; CME
configure the LCS parameters of the test cell.
3. After the preceding configurations are complete, log out of the LMT and then log in
to it again.
l NSS-based LCS in idle mode (cell ID + TA) Verification Procedure
1. Initiate A interface message tracing by referring to Tracing Messages on the A
Interface. Select the BSSAP check box in the Trace Type area.
2. Use an MS to originate a call and keep the call alive.

GBSS14.0
3. Check the APDU information element (IE) in the CM Service Request message traced
on the A interface.
The APDU IE carries timing advance (TA) information of the MS.
l NSS-based LCS in dedicated mode (cell ID + TA) Verification Procedure
1. Initiate A interface message tracing by referring to Tracing Messages on the A
Interface. Select the BSSAP check box in the Trace Type area.
3. Check the APDU information element (IE) in the CM Service Request message traced
on the A interface.
The APDU IE carries timing advance (TA) information of the MS.
l BSS-based LCS (cell ID + TA) Verification Procedure
1. Enable an Tracing Messages on the A Interface task, and select BSSAP in the test
cell.
2. Use an MS to initiate a call and hold on after the call is established successfully.
3. Check that the Perform Location Request message and Perform Location
Response message are traced over the A interface after the MSC is triggered on the
MSC side to request location information query. Check that the correct MS location
can be displayed on the MSC.
l Simple Mode LCS (Cell ID + TA) Verification Procedure
1. Initiate CS message tracing of a single user by referring to Tracing CS Domain
Messages of a Single Subscriber. In this step, select the Location Flag check box.
3. Check the traced messages.
Verify that the MS location information sent to the MS is correct.
l NSS-based LCS in idle mode (cell ID + TA) Deactivation Procedure
center: not supported). In this step, set ESTINDL3MSGTAFLAG to CLOSE
(Close).
l NSS-based LCS in dedicated mode (cell ID + TA) Deactivation Procedure
center: not supported). In this step, set ESTINDL3MSGTAFLAG to CLOSE
(Close).
l BSS-based LCS (cell ID + TA) Deactivation Procedure
1. Run the BSC6900 MML command MOD GEXTSMLC (CME single configuration:
SMLC Information; CME batch modification center: not supported) to add settings
of the SMLC to the test cell. In this step, set SMLC Mode to NOTSUPPORT(Not
Support).
l Simple Mode LCS (Cell ID + TA) Deactivation Procedure
SMLC Information; CME batch modification center: not supported) to modify the

GBSS14.0
SMLC configurations for the operator of the test cell. In this step, set SMLC Mode
to NOTSUPPORT(Not Support).
----End
Example
//Activating NSS-based LCS in idle mode (cell ID + TA)
SET AITFOTHPARA: CNNODEIDX=1, ESTINDL3MSGTAFLAG=OPEN;
//Activating NSS-based LCS in dedicated mode (cell ID + TA)
ADD GEXTSMLC: SMLCIDX=0, OPNAME="0", SMLCMode=INNER;
SET AITFOTHPARA: CNNODEIDX=1, ESTINDL3MSGTAFLAG=OPEN;
//Activating BSS-based LCS (cell ID + TA)
ADD GEXTSMLC: SMLCIDX=1, OPNAME="abc", SMLCMode=INNER;
SET GCELLLCS: IDTYPE=BYID, CELLID=0, INPUTMD=D_min_sec_std,
LatitudeDegreeSec="90:00:00.0000", LongitudeDegreeSec="180:00:00.0000";
//Activating Simple Mode LCS (Cell ID + TA)
ADD GEXTSMLC: SMLCIDX=1, OPNAME="abc", SMLCMode=INNER;
SET GCELLLCS: IDTYPE=BYID, CELLID=0, INPUTMD=D_min_sec_std,
LatitudeDegreeSec="90:00:00.0000", LongitudeDegreeSec="180:00:00.0000";
//Deactivating NSS-based LCS in idle mode (cell ID + TA)
SET AITFOTHPARA: CNNODEIDX=1, ESTINDL3MSGTAFLAG=CLOSE;
//Deactivating NSS-based LCS in dedicated mode (cell ID + TA)
SET AITFOTHPARA: CNNODEIDX=1, ESTINDL3MSGTAFLAG=CLOSE;
//Deactivating BSS-based LCS (cell ID + TA)
MOD GEXTSMLC: SMLCIDX=1, OPNAME="abc", SMLCMode=NOTSUPPORT;
//Deactivating Simple Mode LCS (Cell ID + TA)
MOD GEXTSMLC: SMLCIDX=1, OPNAME="abc", SMLCMode=NOTSUPPORT;

GBSS14.0
Feature Activation Guide 71 Configuring Lb Interface
71 Configuring Lb Interface
Lb Interface.
Prerequisites
l License
– The MSC supports location service (LCS).
– The MS supports the assisted GPS (AGPS) location service when the AGPS positioning
method is used.
– The operator is configured. Assume that the operator name is op1.
– The Abis, Ater, and Lb interfaces apply the same transmission modes if the Uplink-
Time Difference Of Arrival (U-TDOA) locating mode is applied.
– The LMU (type B) must be configured to support the U-TDOA location mode.
Context
The BSC6900 supports two types of location services:
l 70 Configuring LCS (cell ID + TA)
l LCS based on an external Serving Mobile Location Center (SMLC) which is connected to
the BSC6900 through the Lb interface
The first type of LCS adopt a built-in SMLC, that is, positioning is performed by the BSS internal
algorithm. The last type of LCS adopts an external SMLC, that is, positioning is performed by
a third-party network element. LCS based on a built-in SMLC and that based on an external
SMLC cannot be used together. This feature is involved in the last type of LCS.

GBSS14.0
The Lb interface is a standard interface between BSC and SMLC. The main function of the
SMLC is to locate an MS based on the measurement results reported by the MS.
Huawei BSS equipment supports the standard Lb interface, and can be interconnected with the
SMLC of other vendorsFigure 71-1 shows the position of the SMLC in a network.
Figure 71-1 Position of the SMLC in the network
Generally, one BSC is connected to only one SMLC. When the BSS Sharing feature is enabled,
one BSC can be interconnected with four SMLCs of four different operators.
A BSC can be connected to an SMLC in the following ways:

l By adding an Lb interface board
TDM or IP transport can be used over the Lb interface.
NOTE
The Lb interface can be configured on any interface boards.

l Without adding an Lb interface board
– In BM/TC separated configuration mode, if TDM transport is used over the Lb interface,
the Lb interface must be configured on the Ater interface board of the BM subrack or
on the A interface board of the TC subrack.
– In BM/TC combined configuration mode, if TDM transport is used over the Lb
interface, the Lb interface must be configured on the A interface board.
– If IP transport is used over the Lb interface, the Lb interface must be configured on the
A or Abis interface board of the BM subrack.
To connect the BSC6900 to an SMLC, data needs to be negotiated and planned for the Lb
interface. Table 71-1 and Table 71-2 provide Lb interface configuration examples.
Table 71-1 Lb interface configuration example (TDM transport)
Parameters Configuration Data Source
OSP Code 1 Negotiated with the peer end
DSP Code 2 Negotiated with the peer end
Network ID NATB(NATB) Negotiated with the peer end

GBSS14.0
Parameters Configuration Data Source
OSP code bits BIT14 Negotiated with the peer end
SS7 protocol type ITUT(ITUT) Negotiated with the peer end
Signalling link code 0 Negotiated with the peer end
Link rate type 64K(64Kbit/s) Negotiated with the peer end
Link timeslot (A interface TS16(Timeslot 16) Negotiated with the peer end
timeslot mask or A interface
timeslot mask)
Test Code Length 10 Negotiated with the peer end
Test Code 170 Negotiated with the peer end
Table 71-2 Lb interface configuration example (IP transport)

Parameter Configuration Data Source
OSP Code 1 Negotiated with the peer end
DSP Code 2 Negotiated with the peer end
Network ID NATB(NATB) Negotiated with the peer end
OSP code bits BIT14 Negotiated with the peer end
SS7 protocol type ITUT(ITUT) Negotiated with the peer end
Local entity type M3UA_IPSP(M3UA IPSP) Negotiated with the peer end
Destination Entity Type M3UA_IPSP(M3UA IPSP) Negotiated with the peer end
Traffic mode M3UA_OVERRIDE_MOD Negotiated with the peer end

(Active/Standby Mode)
Work mode M3UA_IPSP(M3UA IPSP) Negotiated with the peer end
In multiple local signaling points scenarios, configure the Lb interface according to the following
operations. Specifically, establish the relationship between the signaling points and the SMLCs
and configure related link and route information for the signaling points and the SMLCs.
Procedure
l Activation Procedure (Adding an Lb interface board)
1. Run the BSC6900 MML command ADD BRD (CME single configuration: Device
Panel > Add Board; CME batch modification center: not supported) to add an
interface board. In this step, set Board Class to INT, and set Slot No., Subrack
No., Board type, and other parameters to appropriate values.

GBSS14.0
2. Select one of the following activation procedures based on the transport technology
adopted over the Lb interface.
l Activation Procedure (BM/TC Separated, Lb over TDM, and Lb Interface Configured on
an Ater Interface Board in the BM Subrack)
batch modification center: not supported) to add a DSP. In this step, set DSP name,
DSP index, and OSP index to appropriate values; set DSP code to the signaling point
code of the SMLC, DSP type to LB(LB), and DSP bear type to MTP3(MTP3).
SMLC Information; CME batch modification center: not supported) to add an
SMLC. In this step, set SMLC Index and Operator Name to appropriate values; set
SMLC Mode to OUTER(Outer) and DSP index to the index of the DSP added in
Step 1.
NOTE
Run the BSC6900 MML command LST GEXTSMLC (CME single configuration: GSM Global
Configuration Express > BSC Basic Configuration > External SMLC Information) to query
the value of SMLC Mode for the target SMLC.
If the BSC6900 has the SMLC function, Run the BSC6900 MML command MOD GEXTSMLC
(CME single configuration: GSM Global Configuration Express > BSC Basic Configuration >
External SMLC Information; CME batch modification center: not supported). In this step, set
SMLC Index and Operator Name to appropriate values, and set SMLC Mode to OUTER
(Outer).
3. Run the BSC6900 MML command ADD ATERE1T1 (CME single configuration:
Ater Configuration Express > TDM Transport > Ater Interface E1/T1; CME
batch modification center: not supported) to add an E1/T1 over the Ater interface. In
this step, set BM/TC config flag to CFGBM(BM); set Ater connection path
index to an available path; set Subrack No., Slot No., and Port No. based on the
actual cable connection over the Lb interface.
signaling link set. In this step, set DSP index to the index of the DSP added in Step
1 and Signalling link set index to a value that is not in use.
signaling link. In this step, set Signalling link set index to the index added in Step
4, TC mode to SEPERATE_BSC_INTERFACE(BSC Interface), Ater connection
path index to the index added in Step 3, Signalling link code and MTP2 link No.
to values that are not in use, and Ater Mask to the negotiated value.
index added in Step 4.
7. Optional: (Required if U-TDOA LCS is used) Run the BSC6900 MML command
ADD SEMILINK (CME single configuration: GSM Global Configuration
Express > BSC Basic Configuration > Semipermanent Link; CME batch
modification center: not supported). In this step, set Application Type to OTHER

GBSS14.0
(OTHER); set Semipermanent Link Rate to 64K(64Kbit/s); set In BSC Subrack

No., In BSC Slot No., and In BSC Port No. based on the actual cable connection
over the Lb interface set in Step 3; set In BSC Start Timeslot No. to a multiple of 8
and the value cannot be 0; set Out BSC Subrack No., Out BSC Slot No., and Out
BSC Port No. to the port that the Location Measurement Unit (LMU) is connected
to; set Out BSC Start Timeslot No. to a multiple of 8 and the value cannot be 0; set
Semipermanent Link Index to an appropriate value.
l Activation Procedure (BM/TC Separated, Lb over TDM, and Lb Interface Configured on
an A Interface Board in the TC Subrack)
Step 1.
NOTE
(Outer).
3. Run the BSC6900 MML command ADD ATERE1T1 (CME single configuration:
Ater Configuration Express > TDM Transport > Ater Interface E1/T1; CME
batch modification center: not supported) to add an E1/T1 over the Ater interface. In
this step, set BM/TC config flag to CFGBM(BM); set Ater connection path
index to an available path; set Subrack No., Slot No., and Port No. based on the
actual cable connection over the Lb interface.
signaling link. In this step, set Signalling link set index to the index added in Step
4, TC mode to SEPERATE_BSC_INTERFACE(BSC Interface), Ater connection
path index to the index added in Step 3, Signalling link code and MTP2 link No.
to values that are not in use, and Ater Mask to the negotiated value.

GBSS14.0
BSC Port No. to a port on an Ater interface board in the TC subrack; set Out BSC
Start Timeslot No. to a multiple of 8 and the value cannot be 0; set Semipermanent
Link Index to an appropriate value.
No., In BSC Slot No., and In BSC Port No. to the port in the BM subrack
corresponding to that port in the TC subrack set in Step 7; set In BSC Start Timeslot
No. to a multiple of 8 and the value cannot be 0; set Out BSC Subrack No., Out BSC
Slot No., and Out BSC Port No. to the port that the LMU is connected to; set Out
BSC Start Timeslot No. to a multiple of 8 and the value cannot be 0; set
l Activation Procedure (BM/TC Combined, Lb over TDM, and Lb Interface Configured on
A Interface Board)
Step 1.
NOTE
(Outer).
modification center: not supported) to add an E1/T1 link to the target port on the A
interface board. In this step, set Subrack No., Slot No., and Port No. to the port that
the link is connected. Then, set other parameters to appropriate values.

GBSS14.0
signaling link. In this step, set TC mode to SEPERATE_PRINCIPAL(Principal
BSC) or TOGETHER(BSC/TC Together). Then set other parameters based on the
negotiation or the transmission configuration.
NOTE
l In BM/TC separated mode, set TC mode to SEPERATE_PRINCIPAL(Principal BSC); set

Ater connection path index to the value that is in use; set Signalling link code and MTP2
link No. to values that are not in use; set A interface subrack No., A interface slot No, and A
interface port No. based on the actual cable connection over the Lb interface; set Ater Mask
and A interface timeslot mask to the values negotiated with the SMLC.
l In BM/TC combined mode, set TC mode to TOGETHER(BSC/TC Together); set Signalling
link code and MTP2 link No. to the values that are not in use; set A interface subrack No., A
interface slot No., and A interface port No. based on the actual cable connection over the Lb
interface; set A interface timeslot mask to the value negotiated with the SMLC.
BSC Port No. to the port that the Location Measurement Unit (LMU) is connected
to; set Out BSC Start Timeslot No. to a multiple of 8 and the value cannot be 0; set
l Activation Procedure (Lb over IP)
NOTE
If U-TDOA LCS is used and IP transmission is applied between the LMU and the SMLC, the LMU is
connected to the SMLC through a router rather than the BSC. The router must be configured on site.
code of the SMLC, DSP type to LB(LB), and DSP bear type to M3UA(M3UA).
SMLC. In this step, set SMLC Index and Operator Name according to the actual

GBSS14.0
situation; set SMLC Mode to OUTER(Outer) and DSP index to the index of the
DSP added in Step 1.
NOTE
(Outer).
Entity; CME batch modification center: not supported) to add an M3UA local entity.
In this step, set Local entity No. to a value that is not in use; set OSP index and Local
entity type based on the network plan.
Entity; CME batch modification center: not supported) to add an M3UA destination
entity. In this step, set Destination entity No. to a value that is not in use; set Local
entity No. and DSP index to the values specified in Step 3 and Step 1 respectively;
set Destination entity type to an appropriate value.
5. Run the BSC6900 MML command ADD SCTPLNK (CME single configuration: A
Configuration Express > IP Transport > SCTP Link; CME batch modification
center: not supported) to add an SCTP link. In this step, set Subrack No., Slot No.,
SCTP link No., and Logic Port Flag based on the network plan; set Signalling link
mode to CLIENT(CLIENT MOD) and Application type to M3UA(M3UA); set
First local IP address, First destination IP address, and Destination SCTP port
No. to the values negotiated with the engineers of the SMLC.
6. Run the BSC6900 MML command ADD M3LKS (CME single configuration: GSM
CME batch modification center: not supported) to add an M3UA link set. In this step,
set Signalling link set index to a value that is not in use. In this step:
– If Local entity type is set to M3UA_IPSP(M3UA_IPSP) in Step 3, set Work
Mode of the M3UA link set to M3UA_IPSP(M3UA_IPSP).
– If Local entity type is set to M3UA_ASP(M3UA_ASP) in Step 3 and
Destination entity type is set to M3UA_SP(M3UA SP) in Step 4, set Work
Mode of the M3UA link set to M3UA_IPSP(M3UA_IPSP). Otherwise, set Work
Mode of the M3UA link set to M3UA_ASP(M3UA_ASP).
Configuration Express > IP Transport > M3UA Route; CME batch modification
center: not supported) to add an M3UA route. In this step, set Destination entity
No. and Signalling link set index to the values specified in Step 4 and Step 6
respectively.
8. Run the BSC6900 MML command ADD M3LNK (CME single configuration: GSM
CME batch modification center: not supported) to add an M3UA link. In this step, set
Signalling link set index to the value specified in Step 6; set SCTP link No. to the
value specified in Step 5; set Signaling link ID, Subrack No., Slot No., and M3UA
Signaling link name according to the actual situation.

GBSS14.0
1. Run the BSC6900 MML command LST GEXTSMLC to query the value of SMLC
Mode.
Expected result: The value of SMLC Mode is OUTER(Outer).
2. Run the BSC6900 MML command DSP N7DPC. In this step, set DSP index to DSP
index of the SMLC.
Expected result: The value of SCCP DSP state is Accessible. The value of MTP3
DSP state is Available or the value of M3UA DSP state is Available.
3. Initiate a location service on the LCS client side, as shown in Figure 71-1.
Expected result: The target MS is located.
SMLC Information; CME batch modification center: not supported) command. In
this step, set SMLC Mode to NOTSUPPORT(Not Support).
----End
Example
/*Activation procedure (BM/TC separated configuration, Lb over TDM, and
Lb interface configured on an Ater interface board)*/
//Adding a DPC
ADD N7DPC: NAME="dpc1", DPX=2, SPX=0, SPDF=WNF, DPC=111, DPCT=LB,
BEARTYPE=MTP3;
//Adding an SMLC
ADD GEXTSMLC: SMLCIDX=0, OPNAME="op1", SMLCMode=OUTER, DPX=2;
//Adding an E1/T1 link over the Ater Interface
ADD ATERE1T1: BTCFLAG=CFGBM, ATERIDX=0, SRN=0, SN=10, PN=12;//Adding an
MTP3 signaling link set
//Adding an MTP3 signaling link
MTP2LNKN=2, LKTATE=64K, NAME="MTP3LNK";
ADD MTP3RT: DPX=2, SIGLKSX=0, NAME="LT";
/*Activation procedure (Lb over TDM and Lb interface configured on an A

interface board)*/
//Adding a DPC
BEARTYPE=MTP3;
//Adding an SMLC
//Configuring the A interface E1/T1
ADD AE1T1: SRN=0, SN=10, PN=14, OPCIDX=0, ALLTSTYPE=ALLNULL,
BSCFLAG=MAINBSC;
//Adding an MTP3 signaling link set
//Adding an MTP3 signaling link
ADD MTP3LNK: SIGLKSX=0, SIGSLC=0, TCMODE=TOGETHER, ASRN=0, ASN=10,
MTP2LNKN=0, APN=14,

GBSS14.0
ATSMASK=TS1-0&TS2-0&TS3-0&TS4-0&TS5-0&TS6-0&TS7-0&TS8-0&TS9-0&TS10-0&TS11
-0&TS12-0&TS13-0&TS14-0&TS15-0&TS16-1&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&TS30-0&TS31-0,
LKTATE=64K, NAME="MTP3LNK";
ADD MTP3RT: DPX=2, SIGLKSX=0, NAME="LT";
/*Activation procedure (Lb over IP)*/

//Adding a DPC
BEARTYPE=M3UA;
//Adding an SMLC
//Adding an M3UA local entity
ADD M3LE: LENO=0, SPX=0, ENTITYT=M3UA_ASP, NAME="m3ualocal";
//Adding an M3UA destination entity
ADD M3DE: DENO=1, LENO=0, DPX=2, ENTITYT=M3UA_SGP, NAME="m3uaaim";
//Adding an SCTP link
LOCIP1="10.20.30.40", PEERIP1="10.20.30.50", PEERPN=1024, LOGPORTFLAG=NO,
VLANFLAG1=DISABLE, VLANFlAG2=DISABLE, SWITCHBACKFLAG=YES;
//Adding an M3UA link set
ADD M3LKS: SIGLKSX=0, DENO=1, NAME="m3uaidx";
//Adding an M3UA route
ADD M3RT: DENO=1, SIGLKSX=0, NAME="m3uarot";
//Adding an M3UA link
ADD M3LNK: SIGLKSX=0, SIGLNKID=1, SRN=0, SN=10, SCTPLNKN=1, NAME="m3ua";
//Disabling the SMLC mode
MOD GEXTSMLC: SMLCIDX=0, SMLCMode=NOTSUPPORT;

GBSS14.0
Feature Activation Guide 72 Configuring Resource Reservation
72 Configuring Resource Reservation
Resource Reservation.
Prerequisites
Context
With the resource reservation feature, the system reserves TCHFs for high-priority users to
ensure their QoS.
l Channel resources are reserved for high-priority users, therefore ensuring the QoS of the
VIP users and improving user experience.
l Resource reservation provides a segmentation function for operators. Using this function,
operators can provide different levels of services for users with different priorities. In this
way, the operation revenue is increased.
This feature can be used together with the feature GBFD-115001 Enhanced Multi Level
Precedence and Preemption (eMLPP) to better guarantee the benefits of users and improve the
user satisfaction.
Procedure
Modifying GSM Cell Parameters in Batches). In this step, set Grade Access

GBSS14.0
Feature Activation Guide 72 Configuring Resource Reservation
Allow to YES(Yes), and set Highest Priority and Reserved Channel Number to
proper values.
Highest Priority to 7 and Reserved Channel Number to 1.
2. Block the TCHs in cell 0 and reserve only one idle TCH.
3. Start Trace BSSAP Message on the A Interface of cell 0 on the LMT.
4. Use MS 1 to make a common call in cell 0. Then, check the priority delivered by the
CN in the assignment request.
Expected result: If the priority is greater than 7, the call fails. Otherwise, the call can
be established and a TCHF is assigned during the assignment procedure.
5. Use MS 1 to make an emergency call in cell 0. Then, check the priority delivered by
the CN in the assignment request.
Expected result: If the priority is greater than 7, the call fails. Otherwise, the call can
be established and a TCHF is assigned during the assignment procedure.
Modifying GSM Cell Parameters in Batches). In this step, set Grade Access
Allow to NO(No).
2. Run the BSC6900 MML command LST GCELLCHMGBASIC (CME single
Channel Management Parameters of Cell) to query the value of Grade Access
Allow.
Expected result: The value of Grade Access Allow is NO(No).
----End
Example
//Activation Procedure
SET GCELLCHMGBASIC: IDTYPE=BYID, CELLID=0, GRADEACCALLOW=YES, HPRIOR=7,
REVCHANNUM=1;
//Verification Procedure
SET GCELLCHMGBASIC: IDTYPE=BYID, CELLID=0, GRADEACCALLOW=YES, HPRIOR=7,
REVCHANNUM=1;
//Deactivation Procedure
SET GCELLCHMGBASIC: IDTYPE=BYID, CELLID=0, GRADEACCALLOW=NO;
LST GCELLCHMGBASIC: IDTYPE=BYID, BTSID=0, CELLID=0, LstFormat=VERTICAL;

GBSS14.0 73 Configuring Enhanced Multi Level Precedence and
Feature Activation Guide Preemption (eMLPP)
73 Configuring Enhanced Multi Level

Precedence and Preemption (eMLPP)
Enhanced Multi Level Precedence and Preemption (eMLPP).
Prerequisites
l License
– The MSC, HLR, and MS support eMLPP.
Context
The eMLPP service offers a segmentation function. Using this feature, operators can provide
differentiated services for subscribers of different priorities. The eMLPP function ensures the
speech quality of high-priority MSs when the network traffic is heavy.
The MS needs to support eMLPP so that it can initiate calls of different priorities. This feature
ensures the service quality of high-priority calls by using methods such as preemption, queuing,
direct retry, and forced handovers.
eMLPP involves two mechanisms: preemption and queuing.
Procedure
1. Run the BSC6900 MML command LST BSCBASIC (CME single configuration:
Attributes of BSC) to query the value of A Interface Tag.

NOTE
If the value of A Interface Tag is not GSM_PHASE_2Plus, Run the BSC6900 MML command
SET BSCBASIC (CME single configuration: GSM Global Configuration Express > BSC Basic
Configuration > Basic Attributes of BSC; CME batch modification center: 3.17 Modifying GBSC
Parameters in Batches) to set A Interface Tag to GSM_PHASE_2Plus.
center: 3.17 Modifying GBSC Parameters in Batches). In this step, set Preemption
Allowed to YES(Yes) to allow high-priority MSs to preempt resources for low-
priority MSs when there is no resource available for high-priority MSs.
Parameters in Batches). In this step, set Allow EMLPP to YES(Yes).
NOTE
Service preemption is used as an example to describe the verification procedure. Assume that in Step 3,
Allow EMLPP is set to YES(Yes).
1. Prepare three test MSs (MS1, MS2, and MS3), and assign the highest priority for MS1
and the lowest priority for MS3 on the HLR side.
2. Configure data on the MSC side. Ensure that the resources for low-priority MSs can
be preempted by high-priority MSs.
3. On the BSC6900 LMT, initiate CS message tracing of a single user by referring to
Tracing CS Domain Messages of a Single Subscriber. Set Trace Object Symbol
Type to IMSI and enter the IMSI of the MS to be traced, as shown in Figure 73-1.

Figure 73-1 Single User CS Trace dialog box (1)
4. Use MS2 and MS3 to make PSTN calls in the test cell.
5. Check the measurement reports sent by MSs on TCHs and determine the numbers of
the TCHs occupied by MS2 and MS3, as shown in Figure 73-2.
Figure 73-2 Single User CS Trace dialog box (2)

6. Run the BSC6900 MML command SET GTRXCHANADMSTAT to block

remaining idle TCHs in the cell.
7. Use MS1 to make a PSTN call in the cell.
8. If no neighboring relationship is correctly configured, view the measurement reports
sent by MS1 and check whether MS1 has preempted the TCH used by MS2 or MS3.
The call of MS3 is released. MS1 and MS2 continue their calls properly. Check the
measurement reports sent by MS1. The number of the TCH occupied by MS1 is the
same as that of the TCH occupied by MS3 in step 6. This indicates that MS1 occupies
the TCH of MS3.
9. If neighboring relationship is correctly configured, view the measurement reports sent
by MS1 to check whether MS1 has preempted the TCH used by MS2 or MS3 and
check whether the preempted MS has been handed over to a neighboring cell to
continue the call properly.
MS1, MS2, and MS3 make calls properly. MS1 preempts the TCH of MS3, and MS3
has been handed over to a neighboring cell. Check the measurement reports sent by
MS3. The number of the TCH occupied by MS3 is a TCH number of the neighboring
cell.
center: 3.17 Modifying GBSC Parameters in Batches). In this step, set Preemption
Allowed to NO(No).
Parameters in Batches). In this step, set A Interface Tag to its original value in the
activation procedure.
Parameters in Batches). In this step, set Allow EMLPP to NO(No).
----End
Example
LST BSCBASIC
SET OTHSOFTPARA: BSCPMA=YES;
SET GCELLCCBASIC: IDTYPE=BYID, CELLID=0, EMLPPEN=YES;
SET OTHSOFTPARA: BSCPMA=NO;
SET GCELLCCBASIC: IDTYPE=BYID, CELLID=0, EMLPPEN=NO;

GBSS14.0
Feature Activation Guide 74 Configuring Flow Control Based on Cell Priority
74 Configuring Flow Control Based on Cell

Priority
Flow Control Based on Cell Priority.
Prerequisites
– The feature GBFD-111705 GSM Flow Control has been configured before this feature
is activated.
The two features are recommended working together: GBFD-115002 Flow Control
Based on Cell Priority and GBFD-115003 Flow control based on User priority. The
former one controls uplink flow and the latter one controls downlink flow.
Context
This feature is enabled when the BSC is congested to ensure the calls in VIP cells and the paging
to VIP MSs. This feature has no impact on the BSC operation or the high-priority call continuity
success rate.
This feature is applied to scenarios where traffic intensity becomes extremely great in case of
natural disasters. When the GSM network is congested due to an unexpected traffic peak, VIP
cells are created by splitting up existing cells or adding base stations. Special Location Area
Codes (LACs) are assigned to the VIP cells, and roaming areas are specified for the special
LACs at the CN. Only VIP MSs are allowed to camp on VIP cells, which avoids that a large
number of common MSs camp on VIP cells and then VIP cells become congested again. The
CN does not impose roaming area limitation on a common cell. In this case, a large number of
users may camp on a common cell. Then, congestion may occur in this common cell. As a result,
services provided by the cell are affected.

GBSS14.0
Procedure
Topology > Right click BTS > ADD Cell; CME batch modification center: not
supported) or MOD GCELL (CME single configuration: Cell Configuration
Express > Cell Attributes > GSM CELL; CME batch modification center: 3.20
Modifying GSM Cell Parameters in Batches). In this step, set VIP Cell to YES
(Yes).
Parameters in Batches). In this step, set Support Priority Based Flow Control to
YES(Yes), and set VIP Share in CPU Rate, VIP Access CPU Rate, and VIP
Priority.
1. Run the BSC6900 MML command LST GCELL to query the value of VIP Cell.
Expected result: The value of VIP Cell to YES(Yes).
2. Run the BSC6900 MML command LST BSCFCPARA to query the values of
Support Priority Based Flow Control, VIP Share in CPU Rate, VIP Access CPU
Rate, and VIP Priority.
Expected result: The value of Support Priority Based Flow Control is YES(Yes).
The parameters VIP Share in CPU Rate, VIP Access CPU Rate, and VIP
Priority are set to some values.
3. When service congestion occurs in the BSC, check whether the call setup success rate
of a VIP cell and the call setup success rate of VIP users are affected.
Expected result: Ongoing services in the VIP cell and ongoing VIP services are
normal. In addition, call setup success rates of new services in the VIP cell and new
VIP services increase.
Parameters in Batches). In this step, set Support Priority Based Flow Control is
NO(No).
2. Run the BSC6900 MML command MOD GCELL (CME single configuration: Cell
Configuration Express > Cell Attributes > GSM CELL; CME batch modification
center: 3.20 Modifying GSM Cell Parameters in Batches). In this step, set VIP
Cell to NO(No).
----End
Example
//Setting a VIP cell
ADD GCELL: CELLID=0, CELLNAME="cell", TYPE=GSM900, MCC="460", MNC="188",
LAC=10, CI=1, IUOTP=Normal_cell, FLEXMAIO=OFF, VIPCELL=YES;
//Enabling the Flow Control Based on Cell Priority function
SET BSCFCPARA: PRIFCEN=YES, VIPSHAREINCPURATE=50, VIPACCESSCPURATE=80,
VIPPRIORITY=LEVEL0;

GBSS14.0
//Disabling the Flow Control Based on Cell Priority function
SET BSCFCPARA: PRIFCEN=NO;
//Changing a cell from VIP to non-VIP
MOD GCELL: IDTYPE=BYID, CELLID=0, VIPCELL=NO;

GBSS14.0
Feature Activation Guide 75 Configuring Flow Control Based on User Priority
75 Configuring Flow Control Based on User

Priority
Flow Control Based on User Priority.
Prerequisites
– The feature GBFD-111705 GSM Flow Control has been configured before this feature
is activated.
The two features are recommended working together: GBFD-115002 Flow Control
Based on Cell Priority and GBFD-115003 Flow control based on User priority. The
former one controls uplink flow and the latter one controls downlink flow.
l License
– The paging messages sent by the core network carries eMLPP information.
Context
With this feature, user signaling is differentiated based on user priority to ensure that services
of high-priority users are not affected while signaling of low-priority users may be discarded.
Procedure
Parameters in Batches). In this step, set Support Priority Based Flow Control to
YES(Yes) and VIP Priority to an appropriate value based on the flow control imposed
on calls of different priorities.

GBSS14.0
Feature Activation Guide 75 Configuring Flow Control Based on User Priority
NOTE
Flow control is not performed on users whose priority is higher than VIP Priority.
1. Initiate a large number of calls to make the traffic volume exceeds the system
specification.
2. Deliver short message paging to high-priority users and speech paging to other users
at the core network side.
3. Run the BSC6900 MML command DSP PAGINGNUM to query the number of
discarded paging messages.
Expected result: Paging messages for short message services are not discarded and
those for speech services are discarded.
4. Run the BSC6900 MML command SET BSCFCPARA with Support Priority
Based Flow Control set to NO(No).
5. Repeat Step 2.
6. Run the BSC6900 MML command DSP PAGINGNUM to query the number of
discarded paging messages.
Expected result: Paging messages for short message services are discarded and those
for speech services are not discarded.
Parameters in Batches) with Support Priority Based Flow Control set to NO
(No).
----End
Example
//Activating Flow Control Based on User Priority
SET BSCFCPARA: PRIFCEN=YES, VIPPRIORITY=LEVEL0;
//Deactivating Flow Control Based on User Priority
SET BSCFCPARA: PRIFCEN=NO;

GBSS14.0
Feature Activation Guide 76 Configuring PS Service in Priority
76 Configuring PS Service in Priority
PS Service in Priority.
Prerequisites
– A built-in PCU, a packet service processing board, and a Gb interface board are
configured.
– This feature cannot be used with the following feature: GBFD-119902 QoS ARP&THP.
l License
– The MS and SGSN support this feature.
Context
Using different resource scheduling policies on the Um interface, this feature makes it possible
to provide differentiated services for PS users of different priorities. This ensures better
experience for high-priority users.
Procedure
1. Run the BSC6900 MML command SET GCELLPSOTHERPARA (CME single
configuration: Cell Configuration Express > GPRS Attributes > Other GPRS
Parameters in Batches). In this step, set Support PS Service in Priority to
SUPPORT(Support), MAC Scheduling Type to PFSCHEDULE(Proportion Fair
Scheduling), and Downlink Minimum Guaranteed Rate and Rate Filter Time
Window to appropriate values based on the site requirements.

GBSS14.0
Feature Activation Guide 76 Configuring PS Service in Priority
Assume that in the registration information, Traffic class is set to the same value:
INTERACT for MS1 and MS2, and all other information is the same for both MSs except
the values of Traffic handling priority and Allocation/Retention priority.
1. When the Um interface quality is the same for MS1 and MS2, use the two MSs to
perform EDGE download services with the same coding scheme and either of them
occupies four PDCHs. Observe the download rate.
Expected result:
– If the PFC procedure is used, the ratio of MS1 download rate to MS2 download
rate equals the ratio of MS1 THP-ARP priority weight to MS2 THP-ARP priority
weight.
– If the PFC procedure is not used, the ratio of MS1 download rate to MS2 download
rate is determined by BestEffort-ARP1 Priority Weight, BestEffort-ARP2
Priority Weight and BestEffort-ARP3 Priority Weight.
NOTE
THP-ARP priority weight can be configured in the MML command SET GCELLPSCHM.
Parameters in Batches). In this step, set Support PS Service in Priority to
NOTSUPPORT(Not Support).
----End
Example
//Activating PS Service in Priority
SET GCELLPSOTHERPARA: IDTYPE=BYID, CELLID=1024, PSDIFSERVICESUP=SUPPORT,
MACSCHEDULETYPE=PFSCHEDULE, DLMINGUARANTEERATE=10, RATEFILTERTIMEWIN=50;
//Deactivating PS Service in Priority
SET GCELLPSOTHERPARA: IDTYPE=BYID, CELLID=1024,
PSDIFSERVICESUP=NOTSUPPORT;

GBSS14.0
Feature Activation Guide 77 Configuring GPRS
77 Configuring GPRS
GPRS. (This feature cannot be configured using the CME. )
Prerequisites
– The external PCU is installed if the external PCU is used.
– A packet processing board and a Gb interface board are required if the built-in PCU is
used.
l License
– This feature should be supported by the Core Network(CN) and Mobile Station (MS).
– If external PCU is used, the Pb interface is configured. For details, see Configuring the
Pb Interface.
– If built-in PCU is used, the Gb interface is configured. For details, see Configuring the
Gb Interface (over FR) and Configuring the Gb Interface (over IP).
– The BTS transmission mode is configured. For details, see Configuring the
Transmission Data.
Context
This feature implements mainly three functions: managing radio links and resources, controlling
MS access, and providing routing functions for packet data transmission.
Procedure
1. Run the BSC6900 MML command SET GCELLGPRS to set the parameters as
follows:

GBSS14.0
– If external PCU is used, set GPRS to SupportAsExtPcu(Support as external

Pcu), and then run the PCU set attr command on the PCU maintenance console
to support GPRS.
– If built-in PCU is used, set GPRS to SupportAsInnPcu(Support as built-in
PCU).
2. Optional: If built-in PCU is used, if Configuring CS3/CS4, run the BSC6900 MML
command SET GCELLPSCS with both Downlink Fixed CS Type and Uplink
Fixed CS Type set to UNFIXED(UNFIXED).
3. Run the BSC6900 MML command SET GTRXCHAN to set Channel Type to
PDTCH(PDTCH) for at least one channel.
4. Do the following operations according to the BTS works:
– If the BTS works in TDM transmission mode, configure idle timeslots for the BTS
by referring to Configuring the BTS Timeslots.
– If the BTS works in IP transmission mode, configure the IPPATH by Run the
BSC6900 MML command ADD IPPATH. It is recommended that IP path ID be
set to QoS(QoS), BE(BE), AF11(AF11), AF12(AF12), AF13(AF13), AF21
(AF21), AF22(AF22), or AF23(AF23).
1. Run the BSC6900 MML command SET GCELLPSCS with Uplink Fixed CS
Type and Downlink Fixed CS Type set to CS3(CS3) or CS4(CS4).
NOTE
This operation affects the ongoing services of the cells. Therefore, perform the operation in
low traffic hours.
2. Use an MS to perform PING services. On the BSC6900 LMT, trace PS messages on
the Um interface by referring to Tracing PS Domain Messages on the Um Interface.
You can view that the CS3 or CS4 coding scheme is used in the uplink and downlink.
CAUTION
After the verification is complete, set Uplink Fixed CS Type and Downlink Fixed
CS Type to UNFIXED(UNFIXED) according to the activation procedure.
1. Use an MS that camps on the serving cell to download or upload data.
Expected result: The MS downloads or uploads data successfully.
1. Run the BSC6900 MML command SET GCELLGPRS to set GPRS to NO(Not
support).
----End
Example
/*Activating GPRS*/
//External PCU command
SET GCELLGPRS: IDTYPE=BYID, CELLID=0, GPRS=SupportAsExtPcu;
PCU SET ATTR 0 460009162963A 1 02187 1 yes 2 255 true Cell-0
//Built-in PCU command
SET GCELLGPRS: IDTYPE=BYID, CELLID=0, GPRS=SupportAsInnPcu;

GBSS14.0
SET GTRXCHAN: TRXID=0, CHNO=7, CHTYPE=PDTCH;

//(Optional)Built-in PCU command
SET GCELLPSCS: IDTYPE=BYID, CELLID=0, UPFIXCS=UNFIXED, DNFIXCS=UNFIXED;
//(Optional)Verification procedure
SET GCELLPSCS: IDTYPE=BYID, CELLID=0, UPFIXCS=CS3, DNFIXCS=CS4;
//Deactivating GPRS
SET GCELLGPRS: IDTYPE=BYID, CELLID=0, GPRS=NO;

GBSS14.0
Feature Activation Guide 78 Configuring Network Operation Mode I
78 Configuring Network Operation Mode I
Network Operation Mode I.
Prerequisites
– A built-in PCU, a packet service processing board, and a Gb interface board are required.
l License
– The Gs interface (the interface between MSC/VLR and SGSN) is configured between
the MSC and SGSN. If a cell is configured with MOCN, the Gs interface must be
available on the MSC and the SGSN of all operators.
Context
The combination of Network Operation Mode I and Gs interface supports coordinated paging
and CS paging in packet transfer mode.
Procedure
Batches). In this step, set GPRS to SupportAsInnPcu(Support as built-in PCU).
Parameters in Batches). In this step, set Network Operation Mode to NMOI
(Network Operation Mode I).

GBSS14.0
Feature Activation Guide 78 Configuring Network Operation Mode I
1. Use a MS to perform a ping service.
2. Use another MS to call the MS processing the ping service.
Expected result: The call is successfully established and the voice quality is good.
Parameters in Batches). In this step, set Network Operation Mode to NMOII
(Network Operation Mode II).
----End
Example
//Activating Network Operation Mode I
SET GCELLPSBASE: IDTYPE=BYID, CELLID=0, NMO=NMOI;
//Deactivating Network Operation Mode I
SET GCELLPSBASE: IDTYPE=BYID, CELLID=0, NMO=NMOII;

GBSS14.0
Feature Activation Guide 79 Configuring EGPRS
79 Configuring EGPRS
EGPRS.
Prerequisites
– The external PCU is installed if the external PCU is used.
– A packet processing board and a Gb interface board are required if the built-in PCU is
used.
This feature depends on the optional feature GBFD-114101 GPRS.
l License
– This feature should be supported by the GPRS Support Node (GGSN/SGSN) and the
Mobile Station (MS).
– If external PCU is used, the Pb interface is configured. For details, see Configuring the
Pb Interface.
– If built-in PCU is used, the Gb interface is configured. For details, see Configuring the
Gb Interface (over FR) and Configuring the Gb Interface (over IP).
– The BTS transmission mode is configured. For details, see Configuring the
Transmission Data.
Context
Provides high-speed PS services, increases packet capacity, and reduces the delay of PS services
and the congestion rate, improving the service quality and enhancing the user experience.
Procedure

GBSS14.0
Batches) to set the parameters as follows:
– If external PCU is used, set GPRS to SupportAsExtPcu(Support as external
Pcu) and EDGE to YES(Yes).
– If built-in PCU is used, set GPRS to SupportAsInnPcu(Support as built-in
PCU) and EDGE to YES(Yes).
2. Do the following operations according to the BTS works:
– If the BTS works in TDM transmission mode, configure idle timeslots for the BTS
by referring to Configuring the BTS Timeslots.
– If the BTS works in IP transmission mode, configure the IPPATH by running the
ADD IPPATH (CME single configuration: Abis Configuration Express > IP
Transport > IP Path; CME batch modification center: not supported) command.
It is recommended that IP path type be set to QoS(QoS), BE(BE), AF11
(AF11), AF12(AF12), AF13(AF13), AF21(AF21), AF22(AF22), or AF23
(AF23).
3. Optional: If built-in PCU is used, configuring dynamically adjusting the uplink MCS
coding, run the BSC6900 MML command SET GCELLEGPRSPARA (CME single
configuration: Cell Configuration Express > GPRS Attributes > EGPRS
Parameters in Batches). In this step, set Uplink Fixed MCS Type to UNFIXED
(UNFIXED) and Support EGPRS Uplink MCS Dynamic Adjust to 2(According
to uplink quality measurements reported by BTS).
– In the case that the external PCU is used, use an MS to perform PING services. Then,
start the message tracing over the Um interface on the PCU maintenance console. The
result shows that the coding schemes MCS1 to MCS9 that are supported by EGPRS are
used.
– In the case that the built-in PCU is used, use an MS to perform PING services. Then,
start the task Um Interface PS Trace on the LMT. The result shows that the coding
schemes MCS1 to MCS9 that are supported by EGPRS are used.
Optional: verification procedure of configuring dynamically adjusting the uplink MCS

coding
– Route downlink BTS signals to the shielding cabinet.

– After combining the uplink signals and interference source signals, route the combined
signals to the receive end of the TRX.
– Set the interference source frequency to the uplink frequency of the TRX, set the
transmit power, and then put the MS in the shielding cabinet.
– Use the MS to load files through FTP.
– Initiate the PS domain message tracing over the Um interface on the BSC6900 LMT
by referring to Tracing PS Domain Messages on the Um Interface. Trace the result of
uplink MCS coding adjustment.
The expected result: When the interference source power increases, the rate of uplink
EGPRS coding scheme decreases.

GBSS14.0
– In the case that the external PCU is used, run the BSC6900 MML command SET
GCELLGPRS (CME single configuration: Cell Configuration Express > GPRS
Attributes > Basic GPRS Attributes of 2G Cell; CME batch modification center:
3.20 Modifying GSM Cell Parameters in Batches). In this step, set GPRS to
SupportAsExtPcu(Support as external Pcu) and EDGE to NO(No).
– In the case that the built-in PCU is used, Run the BSC6900 MML command SET
GCELLGPRS (CME single configuration: Cell Configuration Express > GPRS
Attributes > Basic GPRS Attributes of 2G Cell; CME batch modification center:
3.20 Modifying GSM Cell Parameters in Batches). In this step, set GPRS to
SupportAsInnPcu(Support as built-in PCU) and EDGE to NO(No).
– Optional: If built-in PCU is used, run the BSC6900 MML command SET
GCELLEGPRSPARA (CME single configuration: Cell Configuration Express >
GPRS Attributes > EGPRS Parameters of 2G Cell; CME batch modification center:
3.20 Modifying GSM Cell Parameters in Batches). In this step, set Support EGPRS
Uplink MCS Dynamic Adjust to 1(According to downlink quality measurements
reported by MS).
----End
Example
//Activating EGPRS
SET GCELLGPRS: IDTYPE=BYID, CELLID=0, GPRS=SupportAsInnPcu, EDGE=YES;
//(Optional)Activating Dynamically Adjusting the Uplink MCS Coding
SET GCELLEGPRSPARA: IDTYPE=BYID, CELLID=0, UPFIXMCS=UNFIXED,
ADJUSTULMCSTYPE=2;
//Deactivating EGPRS
//(Optional)Deactivating Dynamically Adjusting the Uplink MCS Coding
SET GCELLEGPRSPARA: IDTYPE=BYID, CELLID=0, ADJUSTULMCSTYPE=1;

GBSS14.0
Feature Activation Guide 80 Configuring 11-Bit EGPRS Access
80 Configuring 11-Bit EGPRS Access
11-Bit EGPRS Access, GBFD-119203 Extended Uplink TBF and the basic feature
GBFD-119202 Packet Assignment Taken Over by the BTS. (This feature cannot be configured
using the CME. )
Prerequisites
l Dependency on Hardware
– Built-in PCU should be used, the Packet Processing board and Gb interface board are
required.
l Dependency on Other Features
– The configurations of the features on which this feature depends are complete. This
feature depends on the feature: GBFD-114201 EGPRS.
l License
– This feature should be supported by the MS.
Context
The extended uplink TBF can shorten the transmission delay and reduce the MS power
consumption. The 11-bit EGPRS access on the CCCH can improve the access performance of
the EDGE MS. The BTS takes over the packet and immediate assignments. This can improve
the access performance of the MS and shorten the access delay.
For PCU commands, see the Manual of Commands related to the PCU.Run the BSC6900 MML
command

GBSS14.0
NOTE
l In external PCU mode, the PCU supports the takeover of the immediate assignment by the BTS and
the takeover of the packet assignment by the BTS by default.
l In external PCU mode, if you need to disable the takeover of the immediate assignment by the BTS,
run the pcu cfgpara add<BoardNo> g_bCellSptImmAssDlShift 4 0 command. If you need to disable
the takeover of the packet assignment by the BTS, run the pcu cfgpara add<BoardNo>
g_bCellSptPackAssDlShift 4 0 command. After running the command, you should reset the cell.
Procedure
1. Configure the extended uplink TBF.
– In external PCU mode, run the PCU add privateoptpara command on the PCU
maintenance terminal to set the duration of the inactive period timer to a value
greater than 0.
– In built-in PCU mode, run the BSC6900 MML command SET
GCELLPRIVATEOPTPARA on the LMT. In this step, set Inactive Period of
Extended Uplink TBF to a value greater than 0.
NOTE
Run the BSC6900 MML command SET GCELLPSBASE. In this step, set
EXT_UTBF_NODATA to NOTSEND to reduce the MS power consumption.
2. Configure the 11-bit EGPRS access on the CCCH.
– In external PCU mode, run the PCU ADD EGPRSPara command on the PCU
maintenance terminal to configure the EGPRS access of 11-bit messages on the
CCCH for the cell.
GCELLPSBASE on the LMT. In this step, set Support 11BIT EGPRS Access
to YES(Yes).
BSCPSSOFTPARA on the LMT. In this step, set Force MS Two-phase
Access to Close(Close).
3. Configure the takeover of the packet assignment by the BTS.
– In external PCU mode, run the PCU CfgPara ADD allrppu
g_bCellSptPackAssDlShift 4 1 command on the PCU maintenance terminal to
configure the takeover of the packet assignment by the BTS. After running the
command, you should reset the cell.
GCELLPSOTHERPARA on the LMT. In this step, set Move Packet
Assignment Down to BTS to YES(Yes).
1. Verify the extended uplink TBF.
Run the BSC6900 MML command LST GCELLPRIVATEOPTPARA to check

whether Inactive Period of Extended Uplink TBF is greater than 0. Use the MS to
perform PS services. After transmitting the uplink data to the BSC, the MS does not
release the uplink TBF immediately. Instead, it releases the uplink TBF after the
duration equal to Inactive Period of Extended Uplink TBF.
2. Verify the 11-bit EGPRS access on the CCCH.

GBSS14.0
Use the MS that supports 11-bit EGPRS to perform PS services. If the value of random
access for a channel request is 11-bit, the MS has accessed the network.
3. Verify the takeover of packet assignment by the BTS.
Use the MS to make a dial-up connection to the network and then to perform the ping
function. Enabling Move Packet Assignment Down to BTS can reduce the ping delay
by 30 to 50 ms, which depends on the transmission over the Abis interface.
1. Deactivate the extended uplink TBF.
– In external PCU mode, run the PCU set privateoptpara command on the PCU
maintenance terminal to set the duration of the inactive period timer to 0.
GCELLPRIVATEOPTPARA on the LMT. In this step, set Inactive Period of
Extended Uplink TBF to 0.
2. Deactivate the 11-bit EGPRS access on the CCCH.
– In external PCU mode, run the PCU set egprspara command on the PCU
maintenance terminal to configure the cell not to support the function of 11-bit
EGPRS access on the CCCH.
GCELLPSBASE on the LMT. In this step, set Support 11BIT EGPRS Access
to NO(No).
3. Deactivate the takeover of packet assignment by the BTS.
– In external PCU mode, run the PCU CfgPara SET allrppu
g_bCellSptPackAssDlShift 4 1 command on the PCU maintenance terminal to
configure the cell not to support the takeover of packet assignment by the BTS.
After running the command, reset the cell.
GCELLPSOTHERPARA on the LMT. In this step, set Move Packet
Assignment Down to BTS to NO(No).
----End
Example
/*Activating the extended uplink TBF*/
//External PCU mode, set the duration of the inactive period timer to a
value greater than 0
PCU ADD PrivateOptPara 11 0 120 2000 2400
//Built-in PCU mode, set the duration of the inactive period timer to a
value greater than 0
SET GCELLPRIVATEOPTPARA: IDTYPE=BYID, CELLID=0, UPEXTTBFINACTDELAY=2000;
SET GCELLPSBASE: IDTYPE=BYID, CELLID=0, EXTUTBFNODATA=NOTSEND;
/*Activating the 11-bit EGPRS access on the CCCH*/

//External PCU mode
PCU ADD EGPRSPara 11 la 8 yes unfixed mcs2 unfixed mcs6
//Built-in PCU mode
SET GCELLPSBASE: IDTYPE=BYID, CELLID=0, EGPRS11BITCHANREQ=YES;
//Closing the Force MS Two-phase Access

SET BSCPSSOFTPARA: Force2Phase=Close;
/*Activating the takeover of the packet assignment by the BTS*/
//External PCU mode

GBSS14.0
PCU CfgPara ADD allrppu g_bCellSptPackAssDlShift 4 1

//Built-in PCU mode
SET GCELLPSOTHERPARA: IDTYPE=BYID, CELLID=0, PACKASSDLSHIFT=YES;
/*Deactivating the extended uplink TBF*/
//External PCU mode, set the duration of the inactive period timer to 0
PCU SET PrivateOptPara 11 0 120 0 2400
//Built-in PCU mode, set the duration of the inactive period timer to 0
SET GCELLPRIVATEOPTPARA: IDTYPE=BYID, CELLID=0, UPEXTTBFINACTDELAY=0;
/*Deactivating the 11-bit EGPRS access on the CCCH*/

//External PCU mode
PCU SET EGPRSPara 11 la 8 no unfixed mcs2 unfixed mcs6
//Built-in PCU mode
SET GCELLPSBASE: IDTYPE=BYID, CELLID=0, EGPRS11BITCHANREQ=NO;
/*Deactivating the takeover of the packet assignment by the BTS*/
//External PCU mode
PCU CfgPara SET allrppu g_bCellSptPackAssDlShift 4 0
//Built-in PCU mode
SET GCELLPSOTHERPARA: IDTYPE=BYID, CELLID=0, PACKASSDLSHIFT=NO;

GBSS14.0
Feature Activation Guide 81 Configuring Packet Channel Dispatching
81 Configuring Packet Channel

Dispatching
About This Chapter
Packet Channel Dispatching.
Prerequisites
required.
l License
– An MS (GSM MS) that supports only voice service is available.
– An MS (GPRS MS) that supports only GPRS service is available.
Context
l The GPRS system uses only the GMSK modulation scheme whereas the EGPRS system
uses the GMSK and 8PSK modulation schemes. When EGPRS downlink services and
GPRS uplink services use the same packet channel, the EGPRS downlink data blocks with
the USF should be used to schedule the GPRS uplink services. In this case, the EGPRS
downlink data blocks can use only the GMSK modulation scheme. This greatly affects the
downlink throughput of the EGPRS MS. With this feature, the operator can separate the
EGPRS service from the GPRS service, thus effectively increasing the downlink
throughput of the EGPRS MS.

GBSS14.0
l This feature reduces the probability that the EGPRS service and the GPRS service use the
same channel, thus increasing the EGPRS service rate, improving the entire network
performance, and enhancing the user experience.
81.1 Configuring EGPRS Special Channel Be Used by Only EGPRS Service
This section describes how to activate, verify, and deactivate the feature EGPRS Special Channel
Be Used by Only EGPRS Service.
81.2 Configuring EGPRS Preferred Channel
This section describes how to activate, verify, and deactivate EGPRS Preferred Channel. (This
feature cannot be configured using the CME. )
81.3 Configuring Channel Multiplexing in the E Down G Up Scenario
This section describes how to activate, verify, and deactivate channel multiplexing in the E
(EGPRS) Down G (GPRS) Up scenario.

GBSS14.0
81.1 Configuring EGPRS Special Channel Be Used by Only

EGPRS Service
This section describes how to activate, verify, and deactivate the feature EGPRS Special Channel
Be Used by Only EGPRS Service.
Procedure
1. Configure an EGPRS TRX for the cell.
Batches). In this step, set GPRS to SupportAsInnPcu(Support as built-in PCU)
and EDGE to YES(Yes) to enable the EGPRS function.
modification center: 3.22 Modifying GSM TRX Parameters in Batches). In this
step, set TRX ID, Channel No., Channel Type, and PDCH Channel Priority
Type.
The expected result: The values of Channel Type of six channels are PDTCH
(PDTCH), and the values of PDCH Channel Priority Type are EGPRSSPECH
(EGPRS Special Channel).
NOTE
An GPRS MS(class10)that supports GPRS service and an EGPRS MS(class10) that supports EGPRS
service are available.
1. Monitor the channels used by the MSs.
2. Use the GPRS MS to make a PDP activation.
3. Attach the EGPRS MS to the EGPRS network and initiate the PDP activation.
The expected result:
– The GPRS MS cannot make PDP activation successes.
– The EGPRS MS can be attached to the EGPRS network and the PDP activation
successes.
step, set Channel Type to PDTCH(PDTCH) and PDCH Channel Priority Type to
any value except EGPRSSPECH(EGPRS Special Channel).
----End
Example

GBSS14.0
SET GTRXCHAN: TRXID=0, CHNO=2, CHTYPE=PDTCH, GPRSCHPRI=EGPRSSPECH;

SET GTRXCHAN: TRXID=0, CHNO=2, CHTYPE=PDTCH, GPRSCHPRI=EGPRSNORCH;
81.2 Configuring EGPRS Preferred Channel

This section describes how to activate, verify, and deactivate EGPRS Preferred Channel. (This
feature cannot be configured using the CME. )
Procedure
1. Configure two EGPRS TRXs for the cell.
2. Run the BSC6900 MML command SET GCELLGPRS. In this step, set GPRS to
SupportAsInnPcu(Support as built-in PCU) and EDGE to YES(Yes) to enable the
EGPRS function.
TRX ID, Channel No., and Administrative State.
The expected result: The values of all Administrative State for all the TCHs on the
BCCH TRX are Lock(Lock).
Type and PDCH Channel Priority Type.
The expected result: The values of Channel Type are PDTCH(PDTCH). PDCH
Channel Priority Type of four channels is EGPRSPRICH(EGPRS Priority
Channel) and PDCH Channel Priority Type of the other four channels is GPRS
(GPRS Channel).
NOTE
The GPRS MS1 (class10), MS2 (class10), and EGPRS MS1 (class10) are attached to the GPRS cell.
1. Record the process of configuring devices.
2. EGPRS MS1 activates PDP and starts DL FTP.
3. GPRS MS1 activates PDP and starts DL FTP.
4. GPRS MS2 activates PDP and starts DL FTP.
5. EGPRS MS1 stops DL FTP and releases PDCH.
6. EGPRS MS1 starts DL FTP again after a period of time.
7. Use a drive test tool to record the channels used by the MSs.

GBSS14.0
– After EGPRS MS1 activates PDP for the first time, it starts DL FTP and uses the EGPRS
preferred channel.
– After GPRS MS2 starts DL FTP, it shares packet channels with GPRS MS1. The system
does notallocate the EGPRS preferred channel to GPRS MS2.
– After EGPRS MS1 stops DL FTP and releases PDCH, GPRS MS2 or GPRS MS1 is
swiched to the correct channel instead of sharing the PDCH with GPRS MS1. The
correct channel is the EGPRS preferred channel used by EGPRS MS1.
– After EGPRS MS1 starts DL FTP again, GPRS MS2 or GPRS MS1 is switched out of
the EGPRS preferred channel and then shares the PDCH with GPRS MS1 or GPRS
MS2.
– The EGPRS preferred channel is allocated to EGPRS MS1 again, and EGPRS MS1
starts DL FTP on the EGPRS preferred channel.
1. Run the BSC6900 MML command SET GTRXCHAN. In this step, set TRX ID to
the index of the EGPRS-capable TRX, Channel Type to TCHFR(TCH Full Rate),
and PDCH Channel Priority Type to any value except EGPRSPRICH(EGPRS
Priority Channel).
----End
Example
SET GTRXCHANADMSTAT: TRXID=0, CHNO=2, ADMSTAT=Lock;
SET GTRXCHAN: TRXID=1, CHNO=0, CHTYPE=PDTCH, GPRSCHPRI=EGPRSPRICH;
SET GTRXCHAN: TRXID=1, CHNO=4, CHTYPE=PDTCH, GPRSCHPRI=GPRS;
SET GTRXCHANADMSTAT: TRXID=0, CHNO=2, ADMSTAT=Ulock;
SET GTRXCHAN: TRXID=1, CHNO=0, CHTYPE=TCHFR, GPRSCHPRI= EGPRSNORCH;

GBSS14.0
81.3 Configuring Channel Multiplexing in the E Down G

Up Scenario
This section describes how to activate, verify, and deactivate channel multiplexing in the E
(EGPRS) Down G (GPRS) Up scenario.
Procedure
1. Configure an EGPRS TRX for the cell.
step, set TRX ID, Channel No., Channel Type, and PDCH Channel Priority
Type.
The expected result: The values of Channel Type are PDTCH(PDTCH), and the
values of PDCH Channel Priority Type of at least two channels are
EGPRSNORCH(EGPRS Normal Channel).
3. Run the BSC6900 MML command SET BSCPSSOFTPARA (CME single
Configuration > PS Software Parameter; CME batch modification center: 3.17
Modifying GBSC Parameters in Batches) . In this step, set Allow E Down G Up
Switch to CLOSE(Close).
NOTE
Two GPRS MSs (class 8) and one EGPRS MS (class10) are available.
1. Attach GPRS MS1 to the GPRS network and initiate the PDP activation. GPRS MS1
starts UL FTP and uses an uplink channel. The uplink channels are not used.
2. Attach EGPRS MS1 to the EGPRS network and initiate the PDP activation. EGPRS
MS1 starts DL FTP and does not share the channel with GPRS MS1.
3. Attach GPRS MS2 to the GPRS network and initiate the DPD activation. EGPRS MS1
starts UL FTP and share the uplink channel with GPRS MS1.
4. Record the channels used by each MS.
– After EGPRS MS1 accesses the cell and starts DL FTP, the uplink channel of GPRS
MS1 does not share the channel with the downlink channel of EGPRS MS1.
– After GPRS MS2 accesses the cell and starts DL FTP, the uplink channel of GPRS MS2
does not share the channel with the downlink channel of EGPRS MS1.
Modifying GBSC Parameters in Batches). In this step, set Allow E Down G Up
Switch to OPEN(Open).
----End

GBSS14.0
Example
SET BSCPSSOFTPARA: FORBIDEDGU=CLOSE;
SET BSCPSSOFTPARA: FORBIDEDGU=OPEN;

GBSS14.0
Feature Activation Guide 82 Configuring Streaming QoS(GBR)
82 Configuring Streaming QoS(GBR)
Streaming QoS(GBR). (This feature cannot be configured using the CME. )
Prerequisites
configured.
– The feature GBFD-114101 GPRS, GBFD-114201 EGPRS, GBFD-510803 Uplink
EGPRS2-A or GBFD-510804 Downlink EGPRS2-A has been configured before this
feature is activated.
l License
– The MSs and SGSN support the PFM procedure and R99 QoS.
– The cell is configured with static PDCHs.
Context
In the case of streaming services, the BSC allocates radio blocks to users based on their QoS
attribute GBR and ensures that the data transmission rates meet the requirements of streaming
services. If streaming services support resource preemption, high-priority streaming services
can preempt radio blocks of low-priority streaming services when radio resources are
insufficient. This ensures that higher-priority services preferentially use radio resources. If
streaming services do not support resource preemption, the GBR is decreased when radio
resources are insufficient; when radio resources become sufficient, the GBR is restored to the
negotiated values. When the BSC needs to decrease or restore the GBR, it requests the SGSN
to modify the GBR through a PFM procedure.
Procedure

GBSS14.0
1. Run the BSC6900 MML command SET GCELLPSOTHERPARA. In this step, set
Support GBR QoS to YES(Support). To enable streaming services to preempt
PDCHs, set OccupyStreamingSwitch to ON(ON).
2. Run the BSC6900 MML command MOD NSE. In this step, set PFC Support to YES
(Support).
3. On the SGSN side, enable the network service entity (NSE) to support Packet Flow
Context (PFC). To enable streaming services to preempt PDCHs, configure the NSE
to carry the ARP information element.
4. Run the BSC6900 MML command RST SIGBVC to reset the SIGBVC to ensure that
the NSE on the CN side is consistent with that on the NE side.
1. Initiate Um interface PS message tracing and check the PSI13 message.
Expected result: The value of pfc-feature-mode in the PSI13 message is 1. This
indicates that the BSC supports PDC.
2. Initiate Gb interface PTP tracing. Perform PDP context activation on an MS whose
registered traffic class is streaming.
Expected result: Signaling messages such as CREATE BSS PFC and CREATE BSS
PFC ACK are traced. This indicates that the PDP context is activated.
3. Use an MS whose registered traffic class is streaming and an MS whose registered
traffic class is interactive or background to perform PS services. The MSs share the
same channel group.
Expected result: The BSC allocates resources to the MS whose registered traffic class
is streaming based on the registered GBR. The other MSs share the remaining
resources.
4. Use multiple MSs whose registered traffic class is streaming to perform PS services.
Expected result: If the MSs have the same priority, the BSS allocates resources to the
MS that is the first to access the network. If the MSs have different priorities and
support resource preemption, a high-priority MS can preempt resources of a low-
priority MS.
NOTE
The information element ARP of CREATE BSS PFC of the Gb interface specifies information such
as the priority of streaming services and whether streaming services can preempt resources and be
preempted.
Support GBR QoS to NO(Not Support) and Preempt Switch of Streaming
Resource to OFF(OFF).
2. Run the BSC6900 MML command MOD NSE. In this step, set PFC Support to NO
(No Support).
Expected result: The value of pfc-feature-mode in the PSI13 message is 0.
3. Run the BSC6900 MML command RST SIGBVC to reset the SIGBVC.
----End
Example
//Activating Streaming QoS(GBR)
SET GCELLPSOTHERPARA: IDTYPE=BYID, CELLID=0, GBRQOS=YES,
OccupyStreamingSwitch=ON;

GBSS14.0
MOD NSE: NSEI=1, PFCSUP=YES;

RST SIGBVC: NSEI=1;
//Deactivating Streaming QoS(GBR)
SET GCELLPSOTHERPARA: IDTYPE=BYID, CELLID=0, GBRQOS=NO,
OccupyStreamingSwitch=OFF;
MOD NSE: NSEI=1, PFCSUP=NO;
RST SIGBVC: NSEI=1;

GBSS14.0
Feature Activation Guide 83 Configuring QoS ARP&THP
83 Configuring QoS ARP&THP
QoS ARP&THP. (This feature cannot be configured using the CME. )
Prerequisites
configured.
– This feature cannot be used with the following features:
– GBFD-119506 GPRS/EGPRS Time slot multiplexing priority.
– GBFD-119907 PS Service in Priority.
l License
Context
The BSC allocates radio resources to the MS according the allocation/retention priority (ARP)
and traffic handle priority (THP) in the QoS attributes. The higher-priority users enjoy more
radio resources and wider radio bandwidth. The BSC maps the R97/R98 QoS to the R99 QoS
according to the 3GPP specifications.
With this feature, the operator allocates radio resources according to service types and user
priority. As a result, the user with a higher priority can seize more bandwidth and enjoy higher
data rate and services of better quality.
Interactive services: The BSS allocates radio resources to users according to the ARP and THP
in the QoS attributes. If the ARPs of users are the same, users with a higher THP are allocated
more radio resources. If the THPs of users are the same, users with a higher ARP are allocated
more radio resources.
Background services: The BSS allocates radio resources to users according to the ARP of QoS.
Users with a higher ARP are allocated more radio resources.

GBSS14.0
The BSS allocates radio resources to services that do not support QoS in the way it allocates
radio resources to best effort services.
Procedure
Support GBR QoS to YES(Support), set MAC Scheduling Type to BUDGET
(Scheduling Based On Budget), set Support QoS Optimize to YES(Support).
2. Run the BSC6900 MML command MOD NSE. In this step, set PFC Support to YES
(Support).
3. Configure the NSE to support PFC on the SGSN side.
4. Run the BSC6900 MML command RST SIGBVC to reset SIGBVC to ensure that
the NSE on the CN side is consistent with that on the NE side.
5. Run the BSC6900 MML command SET GCELLPSCHM. In this step, set the values
of THP1-ARP1 Priority Weight, THP1-ARP2 Priority Weight, THP1-ARP3
Priority Weight, THP2-ARP1 Priority Weight, THP2-ARP2 Priority Weight,
THP2-ARP3 Priority Weight, THP3-ARP1 Priority Weight, THP3-ARP2
Priority Weight, THP3-ARP3 Priority Weight, Background-ARP1 Priority
Weight, Background-ARP2 Priority Weight, Background-ARP3 Priority
Weight, BestEffort-ARP1 Priority Weight, BestEffort-ARP2 Priority Weight,
and BestEffort-ARP3 Priority Weight according to the weight of bandwidths
occupied by users with different priorities.
NOTE
To verify this feature, you can run the command SET GTRXCHANADMSTAT to block idle channels
in the cells so that as many MSs as possible are multiplexed on the same channel group.
To query the channel number of each MS, initiate PS message tracing of a single user by referring to
Tracing PS Domain Messages of a Single Subscriber. Perform PS download services to check the data
rate of each MS.
1. Use the MSs whose registered traffic classes are interactive or background to perform
PS services and ensure that the MSs share the same channel group.
Expected result: When the same coding scheme is used, the ratio of the transmission
rate of the MSs is similar to the ratio of the weight of THP or ARP.
Support GBR QoS to NO(Not Support), set Support QoS Optimize to NO(Not
Support).
2. Run the BSC6900 MML command MOD NSE. In this step, set PFC Support to NO
(Not Support).
----End
Example
//Activating QoS ARP/THP
SET GCELLPSOTHERPARA: IDTYPE=BYID, CELLID=0, GBRQOS=YES, QOSOPT=YES,
MACSCHEDULETYPE
=BUDGET;

GBSS14.0
RST SIGBVC: NSEI=1;

SET GCELLPSCHM: IDTYPE=BYID, CELLID=0, THP1ARP1PRIWEIGHT=10,
THP1ARP2PRIWEIGHT=6, THP1ARP3PRIWEIGHT=4, THP2ARP1PRIWEIGHT=8,
THP2ARP2PRIWEIGHT=4, THP2ARP3PRIWEIGHT=3, THP3ARP1PRIWEIGHT=6,
THP3ARP2PRIWEIGHT=3, THP3ARP3PRIWEIGHT=2, BKGARP1PRIWEIGHT=4,
BKGARP2PRIWEIGHT=2, BKGARP3PRIWEIGHT=1, BEARP1PRIWEIGHT=8,
BEARP2PRIWEIGHT=4, BEARP3PRIWEIGHT=2;
//Deactivating QoS ARP/THP
SET GCELLPSOTHERPARA: IDTYPE=BYID, CELLID=0, GBRQOS=NO, QOSOPT=NO;
RST SIGBVC: NSEI=1;

GBSS14.0
Feature Activation Guide 84 Configuring PS Active Package Management
84 Configuring PS Active Package

Management
PS Active Package Management.
Prerequisites
– Embedded PCU should be used, the Packet Process board and Gb interface board is
required.
feature depends on the feature: GBFD-114101 GPRS or GBFD-114201 EGPRS.
l License
Context
Active queue management (AQM) is an algorithm used to maintain the buffer queue length
within an appropriate range by discarding data packets in the buffer queue actively. It increases
data throughput and reduces service delay at the price of buffer utilization.
AQM is applicable to scenarios in which bandwidth is limited and congestion may occur.
AQM not only ensures high link utilization but also reduces the delay of services that require
low transfer delay. It also enhances fair utilization of bandwidth among services and increases
data throughput.
AQM is applicable to interactive services, background services, and BE services (namely,

services without QoS requirements). It is not applicable to conversational services or streaming
services.
Procedure

GBSS14.0
Feature Activation Guide 84 Configuring PS Active Package Management

Modifying GBSC Parameters in Batches). In this step, set AQM Switch to OPEN
(Open). Set AQM Congestion Threshold, AQM Target Threshold, AQM
Maximum Threshold, AQM Packet Discard Initial Interval, AQM Packet
Discard Interval Lower Threshold, AQM Packet Discard Interval Upper
Threshold, and AQM N Update Interval according to actual network conditions. It
is advised that these values be set to recommended values.
1. Use an MS to download a large-sized file (about 2 MB) through FTP. After the
download is started, use the MS to download a small-sized file (about 200 KB) through
FTP.
2. View the result of downloading the small-sized file.
The expected result: When AQM Switch is set to OPEN(Open), the time required to
download the small-sized file is reduced, and the rate for downloading the large-sized
file is decreased.
Modifying GBSC Parameters in Batches). In this step, set AQM Switch to CLOSE
(Close).
2. Run the BSC6900 MML command LST BSCPSSOFTPARA (CME single
Configuration > PS Software Parameter) and view the value of AQM Switch.
The expected result: The value of AQM Switch is Close.
----End
Example
SET BSCPSSOFTPARA: AqmMinTh=256, AqmTarTh=384, AqmMaxTh=1024,
AqmSwitch=OPEN, AqmNinit=20, AqmNLowerBound=10, AqmNUpBound=20, AqmM=20;
SET BSCPSSOFTPARA: AqmSwitch=CLOSE;
LST BSCPSSOFTPARA:;

GBSS14.0
Feature Activation Guide 85 Configuring PoC QoS
85 Configuring PoC QoS
PoC QoS.
Prerequisites
– Embedded PCU should be used,the Packet Process board and Gb interface board is
required.
feature depends on the following features GBFD-119901 Streaming QoS(GBR).
l License
– The MS and the CN support PoC service.
Context
The push to talk over cellular (PoC) service is a type of group call service implemented on the
GSM network. The PoC service adopts the packet switching technology and it is carried on the
GPRS/EGPRS networks.
Huawei GBSS equipment can correctly distinguish PoC services from other services and apply
QoS mechanisms for the PoC services. The QoS mechanisms consist of GBR, reduced data
transmission delay, and uplink/downlink balanced channel allocation method.
Procedure
Parameters in Batches). In this step, set POC Support to Support(Support). Set

GBSS14.0
Feature Activation Guide 85 Configuring PoC QoS
Min. GBR for POC Service, Max. GBR for POC Service, and Transmission Delay
of POC Service according to actual situations.
1. Set the registration type of the MS to streaming service. Ensure that the GBR value
is between the values of Min. GBR for POC Service and Max. GBR for POC
Service. The transfer delay must be smaller than Transmission Delay of POC
Service.
2. Use the MS to perform PoC service.
The expected result: The PoC result runs properly.
3. Use the MS whose registration type is streaming service and the MSs of other types
to perform Ping service. The MSs share the same channel group.
The expected result: The Ping delay is smaller after PoC QoS is activated.
Parameters in Batches). In this step, set POC Support to NO(Not Support).
----End
Example
SET GCELLPSOTHERPARA: IDTYPE=BYID, CELLID=1024, POCGBRMIN=6,
POCGBRMAX=16, POCDELAY=650, PocSup=Support;
SET GCELLPSOTHERPARA: IDTYPE=BYID, CELLID=1024, PocSup=NotSupport;

GBSS14.0
Feature Activation Guide 86 Configuring Conversational QoS
86 Configuring Conversational QoS
Conversational QoS. (This feature cannot be configured using the CME. )
Prerequisites
– A built-in PCU, a packet service processing board, and a Gb interface board have been
configured.
l Requirements for the Network Topology
– The Abis interface must use the Abis over IP and Abis over HDLC networking modes.
– The MS and SGSN must support the PFM procedure and R99 QoS.
– The following features have been configured before this feature is activated:
GBFD-114101 GPRS, GBFD-114201 EGPRS, GBFD-510803 Uplink EGPRS2-A,
GBFD-510804 Downlink EGPRS2-A, GBFD-510805 Latency Reduction.
l License
– None
Context
As real-time services, conversational services require low transfer delay. The priorities for
scheduling radio resources for the PoC service and conversational services are higher than those
for other services. As defined in 3GPP specifications, the transfer delay of conversational
services must not exceed 80 ms. Generally, the end-to-end transfer delay of VoIP services must
not exceed 300 ms. Otherwise, user satisfaction deteriorates.
Procedure

GBSS14.0
Feature Activation Guide 86 Configuring Conversational QoS
1. Run the BSC6900 MML command SET GCELLPSOTHERPARA with Support

GBR QoS set to YES(Support).
2. Run the BSC6900 MML commandMOD NSE with PFC Support set to YES
(Support).
3. On the SGSN side, enable the network service entity (NSE) to support Packet Flow
Context (PFC).
4. Run the BSC6900 MML commandRST SIGBVC to reset the SIGBVC to ensure that
the NSE status on the SGSN side is consistent with that on the BSC side.
1. Initiate PS message tracing over the Um interface and check the PSI13 message.
Expected result: The value of pfc-feature-mode in the PSI13 message is 1, indicating
that the BSC supports PFC.
2. Start PTP message tracing over the Gb interface. Perform PDP context activation on
an MS whose registered traffic class is Conversational.
Expected result: Signaling messages such as Create BSS PFC and Create BSS PFC
Ack are displayed, indicating that the PDP context has been activated.
3. Use an MS whose registered traffic class is Conversational and an MS whose
registered traffic class is interactive or background to perform PS services. Ensure
that the two MSs are multiplexed on the same PDCH group.
Expected result: The wireless-block scheduling delay, BER, and number of data
transmission times for MS whose registered traffic class is Conversational are less
than those for the MS whose registered traffic class is non-Conversational.
1. Run the BSC6900 MML command SET GCELLPSOTHERPARA with Support
GBR QoS set to NO(Not Support).
2. Run the BSC6900 MML command MOD NSE with PFC Support set to NO(Not
Support).
----End
Example
//Activating Conversational QoS
SET GCELLPSOTHERPARA: IDTYPE=BYID, CELLID=0, GBRQOS=YES;
RST SIGBVC: NSEI=1;
//Deactivating Conversational QoS
SET GCELLPSOTHERPARA: IDTYPE=BYID, CELLID=0, GBRQOS=NO;
RST SIGBVC: NSEI=1;

GBSS14.0
Feature Activation Guide 87 Configuring NC2
87 Configuring NC2
This section describes how to configure, verify, and deactivate the optional feature
GBFD-116201 Network Control Mode 2 (NC2).
Prerequisites
– Embedded PCU should be used,the Packet Process board and Gb interface board is
required.
– This feature cannot be used together with the feature GBFD-511110 BSC supporting
Blind Search when GERAN-to-UTRAN Cell Reselection.
l License
– The test cell has a neighboring cell.
– The serving cell works properly.
– The serving cell and the target cell belong to the same PLMN. If they belong to different
PLMNs, configure the two PLMNs as equivalent PLMNs on the SGSN.
– For the GSM-to-WCDMA Network-Controlled Cell Reselection function, ensure that
the Inter-RAT Cell Reselection Enable parameter has been set to YES(Yes) for the
GSM cell, and at least one neighboring WCDMA cell has been configured.
Context
With this feature, an MS in a cell with poor signal quality, heavy load, or low signal level can
reselect a neighboring cell with good signal quality, light load, or high signal level.
Compared with the MS-controlled cell reselection, the network-controlled cell reselection
considers factors such as the service type of the MS, and receive level, traffic load, and signal
level of neighboring cells so that the MS can reselect a better cell.

GBSS14.0
Procedure
– Activating NC2
1. Run the BSC6900 MML command SET GCELLGPRS (CME single
configuration: Cell Configuration Express > GPRS Attributes > Basic GPRS
Attributes of 2G Cell; CME batch modification center: 3.20 Modifying GSM
Cell Parameters in Batches). In this step, set the parameters as follows:
– Set GPRS to SupportAsInnPcu(Support as built-in PCU).
– Set Support NC2 to YES(Yes).
Cell Parameters in Batches). In this step, set Network Control Mode to NC2
(NC2).
3. Run the BSC6900 MML command SET GCELLNC2PARA (CME single
configuration: Cell Configuration Express > GPRS Attributes > NC2
Parameters of 2G Cell; CME batch modification center: 3.20 Modifying GSM
Cell Parameters in Batches). In this step, set the thresholds at cell reselection.
– Activating GSM-to-WCDMA Network-Controlled Cell Reselection
Cell Parameters in Batches). In this step, set GPRS to SupportAsInnPcu
(Support as built-in PCU).
(NC0) or NC1(NC1).
3. Run the BSC6900 MML command SET GCELLRESELUTRANFDD (CME
single configuration: Cell Configuration Express > GPRS Attributes >
UTRAN FDD Reselection Parameters for GSM Cells; CME batch
step, set Network-controlled GSM-to-FDD Cell Reselection to SUPPORT
(Support) and the following parameters set to appropriate values:FDD Multi-
RAT Reporting, FDD Reporting Offset, FDD Reporting Threshold, Min.
Ec/No Threshold 2 for PS FDD Reporting, Min. RSCP Threshold 2 for PS
FDD Reporting and FDD Reselection Threshold.
– Verifying NC2
1. Use the MS to perform GPRS services on the GSM serving cell. On the LMT,
trace PS messages on the Um interface by referring to Tracing PS Domain
Messages on the Um Interface.
2. Move the MS, increase the power of the target cell so that the level of the target
cell is higher than that of the serving cell, or increase the number of MSs in the
serving cell so that it becomes overloaded.
3. Check the messages traced over the Um interface. If the following messages are
traced, the NC2 is enabled.

GBSS14.0
– The Packet Measurement Report message that the MS sends to the BSC.
– The Packet Cell Change Order message that the BSC sends to the MS.
– Verifying GSM-to-WCDMA Network-Controlled Cell Reselection
1. On the LMT, trace PS messages on the Um interface by referring to Tracing PS
Domain Messages on the Um Interface.
2. In the Um Interface PS Trace dialog box, set Trace Type to Cell and Cell ID
to the index of the cell to be verified.
3. Check the messages traced over the Um interface. If the following messages are
traced, the GSM-to-WCDMA Network-Controlled Cell Reselection is enabled.
– The BSC sends a Packet Measurement Order message to the MS.
– The MS periodically sends a Packet Measurement Report message to the
BSC.
– When the PS service duration exceeds the value of the FddReselTimeThd
parameter, the BSC sends a Packet Cell Change Order message to the MS.
– Deactivating NC2
(Support as built-in PCU) and Support NC2 to NO(No).
– Deactivating GSM-to-WCDMA Network-Controlled Cell Reselection
1. Run the BSC6900 MML command SET GCELLRESELUTRANFDD (CME
UTRAN FDD Reselection Parameters for GSM Cells; CME batch
step, set Network-controlled GSM-to-FDD Cell Reselection to
----End
Example
//Activating NC2
SET GCELLGPRS: IDTYPE=BYID, CELLID=0, GPRS=SupportAsInnPcu, NC2SPT=YES;
SET GCELLNC2PARA: IDTYPE=BYID, CELLID=0, MINACCRXLEV=50;
//Activating GSM-to-WCDMA Network-Controlled Cell Reselection
SET GCELLRESELUTRANFDD: GSMTOFDDFORCENC2=SUPPORT, PsBestFddCellNum=3,
PsFddCellRptOff=0, PsFddCellRptThd=0, PsFddRptThr2Ecno=10,
PsFddRptThr2Rscp=10, FddReselTimeThd=2000;
//Deactivating NC2
SET GCELLGPRS: IDTYPE=BYID, CELLID=0, GPRS=SupportAsInnPcu, NC2SPT=NO;
//Deactivating GSM-to-WCDMA Network-Controlled Cell Reselection
SET GCELLRESELUTRANFDD: GSMTOFDDFORCENC2=NOTSUPPORT;

GBSS14.0
Feature Activation Guide 88 Configuring Network Assisted Cell Change (NACC)
88 Configuring Network Assisted Cell

Change (NACC)
Network Assisted Cell Change (NACC) and GBFD-119801 Packet SI Status(PSI). (This feature
Prerequisites
configured.
– The feature GBFD-114101 GPRS has been configured before this feature is activated.
l License
– The MS and Core Network (CN) must support this feature.
– The test cell is a GSM cell and has a neighboring GSM cell.
– The cell supports the GRPS service or EDGE service.
– The serving cell support NACC.
– The network control modes of the serving cell is set to NC0 or NC1.
– The serving cell and the target cell belong to the same PLMN. If they belong to different
PLMNs, configure the two PLMNs as equivalent PLMNs on the SGSN.
– The MS detects signal strength deterioration in the serving cell and detects a neighboring
cell with better signal strength.
Context
NACC can be configured to accelerate the cell reselection of an MS and shorten the period of
service disruption caused by cell reselection.
The BSC sends the system information on the neighboring cells to the MS that works in packet
transfer mode so that the MS can initiate packet access after cell reselection. After receiving the

GBSS14.0
system information on neighboring cells on the PACCH, the MS that is in packet transfer mode
can keep these information for 30 seconds, during which it can attempt to access the neighboring
cell according to the system information.
Procedure
– Activating Intra-BSC NACC
1. Run the BSC6900 MML command SET GCELLPSBASE. In this step, set
Network Control Mode to NC0(NC0) or NC1(NC1).
2. Run the BSC6900 MML command SET GCELLGPRS. In this step, set GPRS
to SupportAsInnPcu(Support as built-in PCU) and Support NACC to YES
(Yes).
NOTE
To further improve the performance of PS services, the parameter PACKET SI can be set
to YES(Yes).
– Activating Inter-BSC NACC
1. Run the BSC6900 MML command SET GCELLPSBASE. In this step, set
Network Control Mode to NC0(NC0) or NC1(NC1).
to SupportAsInnPcu(Support as built-in PCU) and Support NACC to YES
(Yes).
NOTE
To further improve the performance of PS services, the parameter PACKET SI can be set
to YES(Yes).
3. Run the BSC6900 MML command MOD NSE. In this step, set RIM Support to
YES(Support).
NOTE
l Both the serving cell and the target cell support RIM.
l RIM Support in the NSE assigned to the serving cell and target cell is set to Yes.
l RIM Support in the NSE assigned to the SGSN is set to Yes.
CAUTION
l Before performing 4, set RIM Support to YES(Support) on both the BSC and
SGSN sides. Otherwise, the RIM does not take effect.
4. Run the BSC6900 MML command RST SIGBVC to activate RIM.

NOTE
Perform this operation when the traffic is light because it affects the services of all cells
under the NSE.
1. Use the MS to initiate GPRS services, and monitor the signaling over the Um interface.
Ensure that the MS is in the serving cell.
2. Move the MS or increase the power of the target cell to make the receive level of the
target cell higher than that of the serving cell.

GBSS14.0
3. Trace the signaling on the Um interface by referring to Tracing PS Domain Messages

on the Um Interface.
After detecting signal strength deterioration in the serving cell and an external
neighboring cell with better signal strength, the MS sends the PACKET CELL
CHANGE NOTIFICATION message to the BSC. Then, the BSC responds with the
PACKET NEIGHBOUR CELL DATA message, which contains the SI1, SI3, and
SI13 system information about the target cell. In addition, the BSC sends the
PACKET CELL CHANGE CONTINUE message to the MS, instructing the MS to
proceed with the cell reselection procedure.
1. Run the BSC6900 MML command SET GCELLGPRS. In this step, set Support
NACC to NO(No) and PACKET SI to NO(No).
Expected result: The value of Support NACC is NO(No) and that of PACKET SI
is NO(No). The cell supports neither NACC nor PACKET SI STATUS.
----End
Example
//Activating Intra-BSC Network Assisted Cell Change (NACC)
SET GCELLGPRS: IDTYPE=BYID, CELLID=0, GPRS=SupportAsInnPcu, NACCSPT=YES,
PKTSI=YES;
//Activating Inter-BSC Network Assisted Cell Change (NACC)
SET GCELLGPRS: IDTYPE=BYID, CELLID=0, GPRS=SupportAsInnPcu, NACCSPT=YES,
PKTSI=YES;
MOD NSE: NSEI=0, RIMSUP=YES;
RST SIGBVC: NSEI=0;
//Deactivating Network Assisted Cell Change (NACC)
SET GCELLGPRS: IDTYPE=BYID, CELLID=0, GPRS=SupportAsInnPcu, NACCSPT=NO,
PKTSI=NO;

GBSS14.0
Feature Activation Guide 89 Configuring BSS Paging Coordination
89 Configuring BSS Paging Coordination
BSS Paging Coordination.
Prerequisites
required.
– None
l License
– The Gs interface does not exist.
– The MS supports this feature.
Context
In the case the Gs interface between the MSC/VLR and SGSN is not configured and the MS is
in packet transfer mode, the network can send CS paging messages for a user on the PACCH to
enable the user in packet transfer mode to respond to the CS paging.
Procedure
Batches). In this step, set GPRS to SupportAsInnPcu(Support as built-in PCU).

GBSS14.0
Feature Activation Guide 89 Configuring BSS Paging Coordination
Parameters in Batches). In this step, set BSS Paging Co-ordination to YES

(YES).
1. Use one test MS to perform the PING service.
2. Use a second MS to call the test MS.
The expected result: The call is set up successfully and the conversation is proper.
NOTE
After a CS paging is initiated, a CS call is set up successfully but the ongoing PS service is
interrupted.
Parameters in Batches). In this step, set BSS Paging Co-ordination to NO(NO).
----End
Example
SET GCELLPSBASE: IDTYPE=BYID, CELLID=0, BSSPAGINGCOORDINATION=YES;
SET GCELLPSBASE: IDTYPE=BYID, CELLID=0, BSSPAGINGCOORDINATION=NO;

GBSS14.0
Feature Activation Guide 90 Configuring PS Handover
90 Configuring PS Handover
PS Handover. (This feature cannot be configured using the CME. )
Prerequisites
– The BSC is configured with a built-in PCU, a packet service processing board, and a
Gb interface board.
l License
– The MS supports PS handover. To support inter-RAT PS handover between GSM and
UMTS, the MS must be a multi-mode MS.
– The CN supports PS handover.
– The SGSN supports PS handover.
– A neighboring GSM or UMTS cell has been configured.
Context
After an NSE is configured to support PS handover, all cells under this NSE support PS handover.
l Intra-RAT PS handover allows an MS performing a PS service to be handed over from a

GSM cell to another GSM cell under the same BSC or different BSCs.
l Inter-RAT incoming PS handover allows an MS performing a PS service to be handed over
from a UMTS cell to a GSM cell.
l Inter-RAT outgoing PS handover allows an MS performing a PS service to be handed over
from a GSM cell to a UMTS cell.

GBSS14.0
Procedure
– Activate PFC at an NSE by performing the following operations:
1. Run the BSC6900 MML command MOD NSE. In this step, set PFC Support to
YES(Support).
2. Run the BSC6900 MML command SET GCELLPSOTHERPARA. In this step,
set Support GBR QoS to YES(Support).
– Activate PS handover at the NSE by performing the following operation:
1. Run the BSC6900 MML command MOD NSE. In this step, set PS Handover
Support to YES(Support).
– Activate inter-RAT incoming PS handover in a cell by performing the following
operation:
to SupportAsInnPcu(Support as built-in PCU) and Support In Inter-RAT
Inter-cell PS Handover to SUPPORT(Support).
– Activate inter-RAT outgoing PS handover in a cell by performing the following
operation:
to SupportAsInnPcu(Support as built-in PCU) and Support In Inter-RAT
Inter-cell PS Handover to SUPPORT(Support).
– Run the BSC6900 MML command RST SIGBVC to reset the SIG BVC.
NOTE
Perform this operation when the traffic is light because it affects the services of all cells under
the NSE.
NOTE
The verification procedure must be performed immediately after the activation procedure. Otherwise,
some messages will not be traced successfully.
– Verify that the NSE supports PS handover by performing the following operations:
1. Initiate Gb-interface signaling tracing of the NSE on the BSC6900 LMT by
referring to Tracing SIG Messages on the Gb Interface.
2. Run the BSC6900 MML command RST SIGBVC to reset the SIG BVC.
Expected result: In the BVC-RESET message, the value of PS Handover contained in
Extended Feature Bitmap is 1.
– Verify that a cell supports intra-RAT PS handover by performing the following
operations:
1. Initiate Gb-interface PTP message tracing on the BSC6900 LMT by referring to
Tracing PTP Messages on the Gb Interface.
2. When the handover requirement for the cell level is met, initiate a PS handover
request.
Expected result: The PS Handover Required message contains the information element
(IE) "Target RNC Identifier."
– Verify that a cell supports inter-RAT incoming PS handover by performing the

GBSS14.0
1. Enable the MS to camp on a UMTS cell and upload and download files. Initiate
Gb-interface PTP message tracing on the BSC6900 LMT by referring to Tracing
PTP Messages on the Gb Interface.
2. Move the MS away from the UMTS cell or increase the number of MSs that upload
and download files in the UMTS cell.
3. Check the PTP messages traced on the Gb interface of the target GSM cell.
Expected result: The PS Handover Request message carries the IE "Source RNC
Identifier." In addition, the PS Handover Request Ack message from the BSC can
be viewed.
– Verify that a cell supports inter-RAT outgoing PS handover by performing the following
operations:
1. Enable the MS to camp on a GSM cell and upload and download files. Initiate Gb-
interface PTP message tracing on the BSC6900 LMT by referring to Tracing PTP
Messages on the Gb Interface.
2. Move the MS away from the GSM cell or increase the number of MSs that upload
and download files in the GSM cell.
3. Check the PTP messages traced on the Gb interface of the target UMTS cell.
Expected result: The PS Handover Required message contains the IE "Target RNC
Identifier."
– Deactivate inter-RAT incoming PS handover in a cell by performing the following
operation:
to SupportAsInnPcu(Support as built-in PCU) and Support Out Inter-RAT
Inter-Cell PS Handover to UNSUPPORT(Not Support).
– Deactivate the inter-RAT outgoing PS handover in a cell by performing the following
operation:
to SupportAsInnPcu(Support as built-in PCU) and Support Out Inter-RAT
Inter-Cell PS Handover to UNSUPPORT(Not Support).
– Deactivate PS handover at the NSE by performing the following operation:
1. Run the BSC6900 MML command MOD NSE. In this step, set PS Handover
Support to NO(No Support).
– Run the BSC6900 MML command RST SIGBVC to reset the SIG BVC.
----End
Example
//Activating PFC at an NSE
SET GCELLPSOTHERPARA: IDTYPE=BYID, CELLID=0, GBRQOS=YES;
//Activating PS handover at the NSE
MOD NSE: NSEI=0, PSHOSUP=YES;
//Activating inter-RAT incoming PS handover in a cell
SET GCELLGPRS: IDTYPE=BYID, CELLID=0, GPRS=SupportAsInnPcu,
SPTINTERRATINBSCPSHO=SUPPORT;
//Activating inter-RAT outgoing PS handover in a cell
SPTINTERRATOUTBSCPSHO=SUPPORT;

GBSS14.0
//Resetting the SIG BVC

RST SIGBVC: NSEI=0;
//Deactivating inter-RAT incoming PS handover in a cell
SPTINTERRATINBSCPSHO=UNSUPPORT;
//Deactivating inter-RAT outgoing PS handover in a cell
SPTINTERRATOUTBSCPSHO=UNSUPPORT;
//Deactivating PS handover at the NSE
MOD NSE: NSEI=0, PSHOSUP=NO;
//Resetting the SIG BVC
RST SIGBVC: NSEI=0;

GBSS14.0
Feature Activation Guide 91 Configuring PS Power Control
91 Configuring PS Power Control
About This Chapter
PS Power Control.
Prerequisites
– A built-in packet control unit (PCU), PS service processing boards, and Gb interface
boards have been configured.
GBFD-114101 GPRS and GBFD-114201 EGPRS
l License
Context
l Note
Enabling downlink power control may decrease the proportion of high-rate coding
schemes.
l Data Preparation
– Scenario 1: Normal EGPRS power decrease
Parameter Data
DL EGPRS SUPPSDLPC YES(Yes) Internal

Closed-Loop planning
Power
Control
Support

GBSS14.0
Parameter Data
DL EGPRS SUPEGPRSDL YES(Yes) Internal

Closed-Loop PCMROPT planning
Power
Control MR
Optimized
PS Power PSPCPOLICY 0(Throughput preferred) Internal

Control planning
Policy
– Scenario 2: Preferential EGPRS power decrease

Parameter Data
DL EGPRS SUPPSDLPC YES(Yes) Internal

Closed-Loop planning
Power
Control
Support
SUPEGPRSDL YES(Yes) Internal

PCMROPT planning
PS Power PSPCPOLICY 1(Power control preferred) Internal

Control planning
Policy
– Scenario 3: GPRS downlink power control

Parameter Data
DL GPRS SUPGPRSDLP YES(Yes) Internal

Closed-Loop C planning
Power
Control
Support
91.1 Configuring EGPRS Downlink Power Control

This section describes how to activate, verify, and deactivate EGPRS downlink power control.
91.2 Configuring GPRS Downlink Power Control
This section describes how to activate, verify, and deactivate GPRS downlink power control.

GBSS14.0
91.1 Configuring EGPRS Downlink Power Control

This section describes how to activate, verify, and deactivate EGPRS downlink power control.
Procedure
Batches) with GPRS set to SupportAsInnPcu(Support as built-in PCU) and
EDGE set to YES(Yes). Run the BSC6900 MML command SET
GCELLPSPWPARA (CME single configuration: Cell Configuration Express >
GPRS Attributes > PS Power Control Parameters for GSM Cells; CME batch
modification center: 3.20 Modifying GSM Cell Parameters in Batches) with DL
EGPRS Closed-Loop Power Control Support set to YES(Yes) and
PC_MEAS_CHAN set to BCCH(BCCH).
Set the following parameters based on network planning:
– DL Power Control Coding Scheme Stat. Thres.

– DL Power Control Coding Scheme Stable Thres.
– DL EGPRS Power Control Enable Coding Scheme Thres.
– P0
– DL EGPRS Power Control Target CIR Position
– DL EGPRS Power Control Target CIR Offset
– Max. Downlink Power Decrease Granularity
– Downlink Power Control Precision
– Dummy Power Reduce Granularity
– USF Dummy Power Control Factor
– PS Power Control Policy
– DL EGPRS Closed-Loop Power Control MR Optimized
– Downlink EGPRS MR Filtering Factor
1. Run the BSC6900 MML command SET GCELLEGPRSPARA with both Uplink
Fixed MCS Type and Downlink Fixed MCS Type set to MCS9(MCS9).
3. Start a PS trace task over the Um interface on the BSC6900 LMT by referring to
Tracing PS Domain Messages on the Um Interface. View the Packet Uplink
Assignment, Immediate Assignment, Packet Downlink Assignment, DTM
Assignment Command, and Packet Timeslot Reconfigure messages to ensure that
the information elements (IEs) p0 and pr-mode are carried in these messages.
NOTE
For example, in the Packet Uplink Assignment message, the value of is-p0 is 1, and the IEs
p0 and pr-mode are carried in the message. (The value of is-p0 is 0 when PS power control is
not enabled.)

GBSS14.0
1. Run the BSC6900 MML command SET GCELLPSPWPARA (CME single
configuration: Cell Configuration Express > GPRS Attributes > PS Power
Control Parameters for GSM Cells; CME batch modification center: 3.20
Modifying GSM Cell Parameters in Batches). In this step, set DL EGPRS Closed-
Loop Power Control Support to NO(No).
----End
Example
//Activating EGPRS downlink power control and optimization of EGPRS
downlink closed-loop measurement report
SET GCELLPSPWPARA: IDTYPE=BYID, CELLID=0, PCMEASCHAN=BCCH, SUPPSDLPC=YES,
MCSSTATTHR=10, MCSSTABTHR=8, DLPCSTARTTHR=MCS9, DLPCINITPR=DB0,
TGTCIRPOS=3, TGTCIROFFSET=2, MAXPCSTEP=1, PSPCPRES=0.6dB, DummyPRGran=15,
USFDummyPCFactor=3, PSPCPOLICY=0, SUPEGPRSDLPCMROPT=YES;
//Deactivating EGPRS downlink power control
SET GCELLPSPWPARA: IDTYPE=BYID, CELLID=0, SUPPSDLPC=NO;
91.2 Configuring GPRS Downlink Power Control

This section describes how to activate, verify, and deactivate GPRS downlink power control.
Procedure
Batches) with GPRS set to SupportAsInnPcu(Support as built-in PCU) and
EDGE set to NO(No). Run the BSC6900 MML command SET
GCELLPSPWPARA (CME single configuration: Cell Configuration Express >
GPRS Attributes > PS Power Control Parameters for GSM Cells; CME batch
modification center: 3.20 Modifying GSM Cell Parameters in Batches) with DL
GPRS Closed-Loop Power Control Support set to YES(Yes) and
PC_MEAS_CHAN set to BCCH(BCCH).
Set the following parameters based on network planning:
– DL Power Control Coding Scheme Stat. Thres.

– DL Power Control Coding Scheme Stable Thres.
– DL GPRS Power Control Enable Coding Scheme Thres.
– P0
– Max. Downlink Power Decrease Granularity
– Downlink Power Control Precision
– Dummy Power Reduce Granularity
– USF Dummy Power Control Factor
– Downlink EGPRS MR Filtering Factor
– DL GPRS Power Control Target Level Thres.

GBSS14.0
– DL GPRS Power Control Level Class Adj. Factor

1. Run the BSC6900 MML command SET GCELLPSCS with both Uplink Fixed CS
Type and Downlink Fixed CS Type set to CS4(CS4).
3. Start a PS trace task over the Um interface on the BSC6900 LMT by referring to
Tracing PS Domain Messages on the Um Interface. View the Packet Uplink
Assignment, Immediate Assignment, Packet Downlink Assignment, DTM
Assignment Command, and Packet Timeslot Reconfigure messages to ensure that
the information elements (IEs) p0 and pr-mode are carried in these messages.
NOTE
For example, in the Packet Uplink Assignment message, the value of is-p0 is 1, and the IEs
p0 and pr-mode are carried in the message. (The value of is-p0 is 0 when PS power control is
not enabled.)
1. Run the BSC6900 MML command SET GCELLPSPWPARA (CME single
configuration: Cell Configuration Express > GPRS Attributes > PS Power
Control Parameters for GSM Cells; CME batch modification center: 3.20
Modifying GSM Cell Parameters in Batches). In this step, set DL GPRS Closed-
Loop Power Control Support to NO(No).
----End
Example
//Activating GPRS downlink power control
SET GCELLPSPWPARA: IDTYPE=BYID, CELLID=0, SUPGPRSDLPC=YES,
GPRSDLMRFLTGENE=30, GPRSDLPCSTARTTHR=CS4, GPRSDLPCRELTHR=50,
GPRSDLPCRELADJGENE=6, PSPCPOLICY=0;
//Deactivating GPRS downlink power control
SET GCELLPSPWPARA: IDTYPE=BYID, CELLID=0, SUPGPRSDLPC=NO;

GBSS14.0 92 Configuring PDCH Dynamic Adjustment with Two
Feature Activation Guide Thresholds
92 Configuring PDCH Dynamic

Adjustment with Two Thresholds
PDCH Dynamic Adjustment with Two Thresholds.
Prerequisites
required.
l License
– The cell is configured with dynamic TCHFs.
Context
With this feature, the conversion between PDCH and TCH can be dynamically performed
according to the traffic load in the cell. This feature effectively increases the channel usage,
reduces the possibility of CS services preempting the radio resources of PS services, and thus
improves the CS access performance and PS retainability performance.
l Data Preparation

Parameter Data
Uplink UPDYNCHNT This parameter controls dynamic channel Networ

Multiplex RANLEV conversion requests and releases based on k
Threshold of the uplink load in a cell. If the proportion plannin
Dynamic of PDCHs is large in a cell, you are g
Channel advised to set this parameter to a large
Conversion value to minimize the impact of PS
services on CS services.
Downlink DWNDYNCH This parameter controls dynamic channel Networ

Multiplex NTRANLEV conversion requests and releases based on k
Threshold of the downlink load in a cell. If the plannin
Dynamic proportion of PDCHs is large in a cell, you g
Channel are advised to set this parameter to a large
Conversion value to minimize the impact of PS
services on CS services.
Upper CHIDLHIGHT When the proportion of idle TCHs is Networ

Threshold for HR greater than this threshold and more than k
CS Idle one MS is multiplexed onto a PDCH, a plannin
Channel Rate dynamic channel conversion request is g
raised.
Lower CHIDLLOWT When the proportion of idle TCHs for CS Networ

Threshold for HR services is less than this threshold, a k
CS Idle dynamic channel release is triggered. plannin
Channel Rate g
Inter_Cell PS PSRESPREEM This parameter specifies whether PS Networ

Resource PT services in a cell can preempt PDCHs of k
Preempt other cells if Abis transmission resources plannin
Allowed or DPU resources are insufficient. g
Inter_Cell PS PSRESPREEM This parameter specifies whether PDCHs Networ

Resource PTED in a cell can be preempted by PS services k
Preempted of other cells if Abis transmission plannin
Allowed resources or DPU resources are g
insufficient.
PS Service PDCHGBR This parameter specifies the minimum Networ

Guaranteed number of Abis resources requested for k
Rate PDCHs at a site. For example, if this plannin
parameter is set to 16K(16K), a minimum g
of 16 kbit/s bandwidth must be requested.
To enable the services carried on PDCHs
to use a high-rate coding scheme, set this
parameter to a value indicating a high rate.
Procedure


Modifying GSM Cell Parameters in Batches) to set Uplink Multiplex Threshold
of Dynamic Channel Conversion, Dynamic TBF DL MUX Thres. for Channel
Conversion, Upper Threshold for CS Idle Channel Rate, Lower Threshold for
CS Idle Channel Rate, Inter_Cell PS Resource Preempt Allowed and Inter_Cell
PS Resource Preempted Allowed. The value of Lower Threshold for CS Idle
Channel Rate must be smaller than 100.
2. Run the BSC6900 MML command SET BTSOTHPARA (CME single
configuration: BTS Configuration Express > BTS Basic Attributes > Other
Parameters of BTS; CME batch modification center: not supported) to set PS Service
Guaranteed Rate.
3. Run the BSC6900 MML command SET GCELLPRIVATEOPTPARA (CME
Customized Network Optimization Parameters of 2G Cell; CME batch
set bit 18 of Cell ReservedParameter 4 to 1.
NOTE
The following configuration is temporarily implemented to quickly bring this feature into effect. For
a commercial network, it is recommended that the configuration be implemented as planned. Restore
to the original configuration after the verification.
1. Configure sufficient idle timeslots.
2. Run the BSC6900 MML command SETGCELLPSCHM. In this step, set Upper
Threshold for CS Idle Channel Rate to a small value (for example, 20), Lower
Threshold for CS Idle Channel Rate to a small value (for example, 5), Maximum
Rate Threshold of PDCHs in a Cell to 100, and Reservation Threshold of Dynamic
Channel Conversion to 0.
3. Configure one static PDCH and multiple TCHFs. Ensure that at least 4 PDCHs can
be generated through channel conversion after PS services are initiated, and that the
proportion of idle TCHs is greater than the value of Upper Threshold for CS Idle
Channel Rate.
4. Use two MSs to process PS services (data downloading). When the proportion of idle
TCHs to all TCHs is greater than the value of Upper Threshold for CS Idle Channel
Rate, TCHF-to-PDCH conversion is triggered.
5. Use more MSs to process PS services (data downloading). When the proportion of
idle TCHs to all TCHs is greater than the value of Lower Threshold for CS Idle
Channel Rate and the average downlink load of PDCHs in the cell is greater than the
value of Downlink Multiplex Threshold of Dynamic Channel Conversion, TCHF-
to-PDCH conversion is triggered.
6. Initiate CS services to occupy more TCHs. When the proportion of idle TCHs to all
TCHs is less than the value of Lower Threshold for CS Idle Channel Rate, idle
PDCHs are converted to TCHs.
Modifying GSM Cell Parameters in Batches). In this step, set Downlink Multiplex

Threshold of Dynamic Channel Conversion to the value before this feature is

activated and Upper Threshold for CS Idle Channel Rate to 100.
Parameters of BTS; CME batch modification center: not supported). In this step, set
PS Service Guaranteed Rate to the value before this feature is activated.
set bit 18 of Cell ReservedParameter 4 to 0.
----End
Example
//Activating PDCH Dynamic Adjustment with Two Thresholds
SET GCELLPSCHM: IDTYPE=BYID, CELLID=0, UPDYNCHNTRANLEV=20,
DWNDYNCHNTRANLEV=20, CHIDLHIGHTHR=20, CHIDLLOWTHR=10, PSRESPREEMPT=YES,
PSRESPREEMPTED=YES;
SET BTSOTHPARA: IDTYPE=BYID, BTSID=0, PDCHGBR=64K;
SET GCELLPRIVATEOPTPARA: IDTYPE=BYID, CELLID=0, CellPSReservePara4=262144;
//Deactivating PDCH Dynamic Adjustment with Two Thresholds
SET GCELLPSCHM: IDTYPE=BYID, CELLID=0, DWNDYNCHNTRANLEV=10,
CHIDLHIGHTHR=100;
SET BTSOTHPARA: IDTYPE=BYID, BTSID=0, PDCHGBR=32K;
SET GCELLPRIVATEOPTPARA: IDTYPE=BYID, CELLID=0, CellPSReservePara4=0;

GBSS14.0 93 Configuring Timeslot Multiplexing Priority for GPRS/
Feature Activation Guide EGPRS User

Timeslot Multiplexing Priority for GPRS/EGPRS User.
Prerequisites
– A built-in PCU, packet service processing board, and Gb interface board have been
configured.
– The following feature has been configured before this feature is activated:
– GBFD-114101 GPRS
– GBFD-114201 EGPRS
– GBFD-119907 PS Service in Priority
– This feature cannot be used with the following features: GBFD-119902 QoS
ARP&THP.
l License
– The Gb interface has been configured. For details, see Configuring the Gb Interface
(over FR) and Configuring the Gb Interface (over IP).
Context
This feature controls the proportion of Um interface resources allocated to GPRS users and
EGPRS users by adjusting GPRS/EGPRS timeslot multiplexing priority parameter settings,
thereby increasing the network throughput.
Procedure


Parameters in Batches). In this step, set MAC Scheduling Type to PFSCHEDULE
(Proportion Fair Scheduling).
2. Optional: Run the BSC6900 MML command SET GCELLPSOTHERPARA
(CME single configuration: Cell Configuration Express > GPRS Attributes >
Other GPRS Parameters of 2G Cell; CME batch modification center: 3.20
Modifying GSM Cell Parameters in Batches). In this step, set Priority Weight of
EGPRS Users to an appropriate value based on the network plan.
NOTE
The default value of Priority Weight of EGPRS Users is 1. If this parameter is set to another
value, EGPRS and GPRS users are multiplexed based on their priorities.
3. Optional: Run the BSC6900 MML command SET GCELLPSOTHERPARA
(CME single configuration: Cell Configuration Express > GPRS Attributes >
Other GPRS Parameters of 2G Cell; CME batch modification center: 3.20
Modifying GSM Cell Parameters in Batches). In this step, set Downlink Minimum
Guaranteed Rate to an appropriate value based on the network plan.
4. Optional: Run the BSC6900 MML command SET GCELLPSCHM (CME single
Modifying GSM Cell Parameters in Batches). In this step, set PDCH Management
Optimization to ON(On).
Modifying GSM Cell Parameters in Batches). In this step, set GPRS Channel
Priority Type Auto-Planning to ON(On) and set Number of EGPRS Special
Channels, Number of EGPRS Priority Channels, Number of EGPRS Priority
Channels, Number of EGPRS Special Channels (OL Subcell), Number of EGPRS
Priority Channels (OL Subcell), and Number of EGPRS Normal Channels (OL
Subcell) to appropriate values based on the network plan.
NOTE
Before performing the preceding operation, back up the settings of PDCH Channel Priority
Type for PDCHs in the cell.
Priority Weight of EGPRS Users to the minimum value, 1.
2. Use two MSs, one supporting EGPRS and the other supporting GPRS, to download
data through FTP simultaneously. Check the downloading rates of the two MSs.
Priority Weight of EGPRS Users to the maximum value, 3. Then, check the
downloading rates of the two MSs. The expected result is that the downloading rate
of the EGPRS MS increases whereas the downloading rate of the GPRS MS decreases.
4. Optional: Run the BSC6900 MML command SET GCELLPSCHM. In this step,
set GPRS Channel Priority Type Auto-Planning to ON(On), set Number of
EGPRS Priority Channels to the planned value, and set Number of EGPRS Special
Channels, Number of EGPRS Priority Channels, Number of EGPRS Special

Channels (OL Subcell), Number of EGPRS Priority Channels (OL Subcell), and
Number of EGPRS Normal Channels (OL Subcell) to 0.
5. Optional: Run the BSC6900 MML command SET GCELLPSCHM. In this step,
set PDCH Management Optimization to ON(On). Then, check the download rate
of the two MSs. The download rate for the EGPRS MS remains or increases and that
for the GPRS MS increases.
Parameters in Batches). In this step, set Priority Weight of EGPRS Users to the
default value 1 or set MAC Scheduling Type to a value other than PFSCHEDULE
(Proportion Fair Scheduling).
Modifying GSM Cell Parameters in Batches). In this step, set PDCH Management
Optimization to OFF(Off).
Modifying GSM Cell Parameters in Batches). In this step, set GPRS Channel
Priority Type Auto-Planning to OFF(Off).
Modifying GSM Cell Parameters in Batches). In this step, set PDCH Channel
Priority Type so that the PDCH priority types of PDCHs roll back to the settings
before GPRS Channel Priority Type Auto-Planning is set to ON(On).
----End
Example
SET GCELLPSOTHERPARA: IDTYPE=BYID, CELLID=0, MACSCHEDULETYPE=PFSCHEDULE;
SET GCELLPSOTHERPARA: IDTYPE=BYID, CELLID=0, EgprsPriWeight=2;
SET GCELLPSOTHERPARA: IDTYPE=BYID, CELLID=0, DLMINGUARANTEERATE=12;
SET GCELLPSCHM: IDTYPE=BYID, CELLID=0, EnPDAdminOpt =ON;
SET GCELLPSCHM: IDTYPE=BYID, CELLID=0, AutoGprsChPri =ON;
ET GCELLPSCHM: IDTYPE=BYID, CELLID=0, EgprsSpeChnum=0;
SET GCELLPSCHM: IDTYPE=BYID, CELLID=0, EgprsPriChnum=4;
SSET GCELLPSCHM: IDTYPE=BYID, CELLID=0, EgprsNorChnum=0;
SET GCELLPSCHM: IDTYPE=BYID, CELLID=0, EgprsSpeChnumInn=0;
SET GCELLPSCHM: IDTYPE=BYID, CELLID=0, EgprsPriChnumInn=0;
SET GCELLPSCHM: IDTYPE=BYID, CELLID=0, EgprsNorChnumInn=0;
SET GCELLPSCHM: IDTYPE=BYID, CELLID=0, EnPDAdminOpt =ON;
SET GCELLPSCHM: IDTYPE=BYID, CELLID=0, AutoGprsChPri =ON;
SET GCELLPSCHM: IDTYPE=BYID, CELLID=0, EgprsPriChnum=4;
SET GCELLPSCHM: IDTYPE=BYID, CELLID=0, EgprsSpeChnum=0;
SET GCELLPSCHM: IDTYPE=BYID, CELLID=0, EgprsNorChnum=0;
SET GCELLPSCHM: IDTYPE=BYID, CELLID=0, EgprsSpeChnumInn=0;

SET GCELLPSCHM: IDTYPE=BYID, CELLID=0, EgprsPriChnumInn=0;

SET GCELLPSCHM: IDTYPE=BYID, CELLID=0, EgprsNorChnumInn=0;
SET GCELLPSOTHERPARA: IDTYPE=BYID, CELLID=0,
MACSCHEDULETYPE=CIRSCHEDULE,
SET GCELLPSCHM: IDTYPE=BYID, CELLID=0, EnPDAdminOpt =OFF;
SET GCELLPSCHM: IDTYPE=BYID, CELLID=0, AutoGprsChPri =OFF;

GBSS14.0
Feature Activation Guide 94 Configuring EDA
94 Configuring EDA
Extended Dynamic Allocation (EDA).
Prerequisites
required.
l License
– This feature is supported by MS.
Context
Generally, the GPRS/EGPRS traffic is higher in downlink than in uplink. In specific situations
(for example, sending large size email through the GPRS/EGPRS network), however, the
requirement on uplink bandwidth is stricter. The EDA feature can allocate at least three timeslots
for an MS in the uplink. If the high multislot class is supported, five timeslots can be allocated
to the MS of high multislot class 34 in the uplink, thus meeting the requirement for higher
bandwidth in the uplink.
The use of the EDA feature needs the support from the MS. In the radio access capability reported
to the network, the MS indicates whether it supports GPRS uplink EDA or EGRPS uplink EDA.
Procedure

GBSS14.0
Modifying GBSC Parameters in Batches). In this step, set Support EDA to

SUPPORT(Support).
Batches). In this step, set Support EDA to SUPPORT(Support).
1. Start the Gb Interface PTP Trace window on the LMT and use the MS to dial a number
(activate PDP context).
The expected result: Check in the ACTIVE PDP CONTEXT ACCEPT message that
the value of gprs-extended-dynamic-allocation-capability is 1or the value of egprs-
extended-dynamic-alloccation is 1.
2. Run the BSC6900 MML command SET BSCPSSOFTPARA. In this step, set
Support EDA to NOTSUPPORT(Not Support).
3. Run the BSC6900 MML command LST BSCPSSOFTPARA to check the value of
Support EDA.
The expected result: The value of Support EDA is Not Support.
EDA to NOTSUPPORT(Not Support).
5. Run the BSC6900 MML command LST GCELLGPRS to check the value of
Support EDA.
6. Use the MS to perform FTP uploading services.
7. Record the uploading speed and the number of PDCHs occupied by the MS.
NOTE
If the cell has only one MS, Run the BSC6900 MML command DSP PDCH to check number
of PDCHs with the Number of Uplink TBFs (GPRS) or Number of Uplink TBFs
(EGPRS) being 1 and record the result.
8. Run the BSC6900 MML command SET BSCPSSOFTPARA. In this step, set
Support EDA to SUPPORT(Support).
9. Run the BSC6900 MML command LST BSCPSSOFTPARA to check the value of
Support EDA.
The expected result: The value of Support EDA is Support.
EDA to SUPPORT(Support).
11. Run the BSC6900 MML command LST GCELLGPRS to check the value of
Support EDA.
The expected result: The value of Support EDA is Support.
12. Use the MS to perform FTP uploading services.
13. Record the uploading speed and the number of PDCHs occupied by the MS.
NOTE
If the cell has only one MS, Run the BSC6900 MML command DSP PDCH to check number
of PDCHs with the Number of Uplink TBFs (GPRS) or Number of Uplink TBFs
(EGPRS) being 1 and record the result.
14. Compare the results obtained in Step 7 and Step 13.

GBSS14.0
The expected result: As recorded in Step 13, the number of PDCHs occupied by the
MS is greater than or equal to 3, and the uploading speed is improved to a great extent
than that recorded in Step 7.
Modifying GBSC Parameters in Batches). In this step, set Support EDA to
2. Run the BSC6900 MML command LST BSCPSSOFTPARA (CME single
Configuration > PS Software Parameter) to check the value of Support EDA.
Batches). In this step, set Support EDA to NOTSUPPORT(Not Support).
4. Run the BSC6900 MML command LST GCELLGPRS (CME single configuration:
Cell) to check the value of Support EDA.
----End
Example
SET BSCPSSOFTPARA: SUPPORTEDA=SUPPORT;
SET GCELLGPRS: SUPPORTEDA=SUPPORT;
SET BSCPSSOFTPARA: SUPPORTEDA=NOTSUPPORT;
LST BSCPSSOFTPARA:;
SET GCELLGPRS: SUPPORTEDA=NOTSUPPORT;
LST GCELLGPRS:;
DSP PDCH: IDXTYPE=BYCELL, IDTYPE=BYID, CELLID=0;
SET BSCPSSOFTPARA: SUPPORTEDA=SUPPORT;
LST BSCPSSOFTPARA:;
SET GCELLGPRS: SUPPORTEDA=SUPPORT;
LST GCELLGPRS:;
SET BSCPSSOFTPARA: SUPPORTEDA=NOTSUPPORT;
LST BSCPSSOFTPARA:;
SET GCELLGPRS: SUPPORTEDA=NOTSUPPORT;
LST GCELLGPRS:;

GBSS14.0
Feature Activation Guide 95 Configuring MS High Multislot Classes
95 Configuring MS High Multislot Classes
MS High Multislot Classes.
Prerequisites
required.
This feature depends on the optional feature GBFD-119401 Extended Dynamic
Allocation (EDA) when more than two timeslots are required on the uplink.
l License
– This feature is supported by MS.
Context
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.
Procedure
Modifying GBSC Parameters in Batches). In this step, set Support High Multislot
Class to SUPPORT(Support).

GBSS14.0
Feature Activation Guide 95 Configuring MS High Multislot Classes
1. 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.
2. Use the MS to download data in the test cell.
3. 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.
Modifying GBSC Parameters in Batches). In this step, set Support High Multislot
Class to NOTSUPPORT(Not Support).
----End
Example
\\Activation Procedure
SET BSCPSSOFTPARA: SUPPORTDL5TS=SUPPORT;
\\Deactivation Procedure
SET BSCPSSOFTPARA: SUPPORTDL5TS=NOTSUPPORT;

GBSS14.0
Feature Activation Guide 96 Configuring DTM
96 Configuring DTM
DTM.
Prerequisites
configured.
– This feature cannot be used together with the feature GBFD-114001 Extended Cell or
GBFD-116201 Network-Controlled Cell Reselection (NC2).
l License
– If the network operation mode II or III is configured, BSS paging coordination must be
configured so that CS pagings can be performed successfully in packet transfer mode.
For details on how to configure BSS paging coordination, see 89 Configuring BSS
Paging Coordination.
– Early Classmark Sending Control (ECSC) must be configured so that the MS can
automatically send the classmark control message to the network as early as possible
after the immediate assignment.
NOTE
ECSC can be configured by running the BSC6900 MML command SET GCELLCCBASIC
(CME single configuration: Cell Configuration Express > Call Control > Call Control Basic
Parameters of Cell; CME batch modification center: 3.20 Modifying GSM Cell Parameters
in Batches).
– The MSC and MS support DTM.
– The MSC must support the COMMON ID message.
Context
DTM allows simultaneous transfer of CS services and PS services. That is, a subscriber can send
photos or browse websites during a voice call. In a 3G network, the speech and data services are

GBSS14.0
Feature Activation Guide 96 Configuring DTM
processed in parallel. In this sense, DTM enables the GSM subscribers to enjoy the services
similar to those provided by the 3G network. In addition, the 2G network can complement the
3G network in terms of coverage.
Procedure
and Support DTM to SUPPORT(Support).
1. Use the MS to make a CS call.
2. Initiate the single-user CS signaling tracing on the LMT by referring to Tracing CS
Domain Messages of a Single Subscriber.
3. Use the MS to perform PS data downloading services.
4. Check the single-user CS signaling tracing result.
Expected result: PS downloading services are performed successfully while the CS
call is not affected.
NOTE
One of the following messages is traced: DTM Request, DTM Assignment Command, or
Packet Assignment.
and Support DTM to UNSUPPORT(Not Support).
----End
Example
//Activating DTM
SUPPORTDTM=SUPPORT;
//Deactivating DTM
SUPPORTDTM=UNSUPPORT;

GBSS14.0
Feature Activation Guide 97 Configuring Class11 DTM
97 Configuring Class11 DTM
Class11 DTM.
Prerequisites
configured.
– Features GBFD-114151 DTM and GBFD-119401 EDA have been configured before
l License
configured so that CS pagings can be performed successfully in packet transfer mode.
For details on how to configure BSS paging coordination, see 89 Configuring BSS
Paging Coordination.
NOTE
ECSC can be configured by running the BSC6900 MML command SET GCELLCCBASIC
(CME single configuration: Cell Configuration Express > Call Control > Call Control Basic
Parameters of Cell; CME batch modification center: 3.20 Modifying GSM Cell Parameters
in Batches).
– DTM should be supported by the MSC. Class11 DTM should be supported by the MS.
Context
Based on common DTM, Class 11 DTM doubles the bandwidth for the uplink PS services of
the MS. When an MS using Class11 DTM provides mainly uplink service, the channel
assignment of Speech + 1Downlink + 2Uplink is supported. That is, two uplink PDCHs and one
downlink PDCH are assigned to the MS.

GBSS14.0
Feature Activation Guide 97 Configuring Class11 DTM
Procedure
Batches). In this step, set GPRS to SupportAsInnPcu(Support as built-in PCU),
SUPPORT DTM to SUPPORT(Support), and Support Class11 DTM to
SUPPORT(Support).
1. Make a CS call.
3. Initiate the single-user PS signaling tracing on the LMT by referring to Tracing PS
4. Use the MS to perform PS data uploading services.
6. Check the single-user PS signaling tracing result.
Expected result:
PS services are performed successfully while the CS call is not affected.
NOTE
One of the following messages is traced in the single-user CS signaling tracing: DTM Request,
DTM Assignment Command, or Packet Assignment.
Single-user PS signaling tracing result shows that two uplink PDCHs are occupied by service
messages.
SUPPORT DTM to SUPPORT(Support), and Support Class11 DTM to
UNSUPPORT(Not Support).
----End
Example
//Activating Class11 DTM
SUPPORTDTM=SUPPORT, CLASS11DTM=SUPPORT;
//Deactivating Class11 DTM
SUPPORTDTM=SUPPORT, CLASS11DTM=UNSUPPORT;

GBSS14.0
Feature Activation Guide 98 Configuring HMC DTM
98 Configuring HMC DTM
HMC DTM.
Prerequisites
required.
feature depends on the following features: GBFD-114151 DTM, GBFD-119401 EDA,
GBFD-119402 MS High multislot classes.
l License
configured so that CS pagings can be performed successfully in packet transmission
mode.
– DTM should be supported by the MSC. DTM HMC should be supported by the MS.
Context
Based on common DTM, HMC DTM improves the bandwidth of the uplink and downlink PS
services of the MS. The MS can occupy a maximum of three uplink and downlink PDCHs
respectively during a call. The following channel assignments are supported: Speech +
3Downlink + 1Uplink, Speech + 2Downlink + 2Uplink, and Speech + 1Downlink + 3Uplink.
The DTM multislot classes defined in 3GPP specifications are classes 5, 6, 9, 10, 11, 31-33,
36-38, and 41-44. The class 31-33 are called HMC DTM. For an MS of DTM multislot class
32-33, the Extended Dynamic Allocation (EDA) function must be used if the MS requires more
than or equal to three channels in the uplink.

GBSS14.0
Feature Activation Guide 98 Configuring HMC DTM
Procedure
Support DTM to SUPPORT(Support), and Support HMC DTM to SUPPORT
(Support).
1. Make a CS call.
3. Initiate the single-user PS signaling tracing on the LMT by referring to Tracing PS
4. Use the MS to perform PS data downloading services.
6. Check the single-user PS signaling tracing result.
Expected result:
PS services are performed successfully while the CS call is not affected.
NOTE
One of the following messages is traced in the single-user CS signaling tracing: DTM Request,
DTM Assignment Command, or Packet Assignment.
Single-user PS signaling tracing result shows that three PDCHs are occupied by service
messages.
Support DTM to SUPPORT(Support), and Support HMC DTM to UNSUPPORT
(Not Support).
----End
Example
SUPPORTDTM=SUPPORT, HMCDTM=SUPPORT;
SUPPORTDTM=SUPPORT, HMCDTM=UNSUPPORT;

GBSS14.0
Feature Activation Guide 99 Configuring 14.4 kbit/s Circuit Switched Data
99 Configuring 14.4 kbit/s Circuit Switched

Data
This chapter describes how to activate, verify, and deactivate the optional feature GBFD-119405
14.4 kbit/s Circuit Switched Data.
Prerequisites
– BTS3012/AE/3006C/3002E does not support this feature when using non optimized
DTRU.
– The BTS3900B/E does not support the feature.
l License
– 14.4kbit/s Circuit Switched Data of single-timeslot mode should be supported by the
MSC.
Context
Huawei GSM BSS supports the transfer of PS services on individual speech channels with a
high rate of 14.4 kbit/s for transparent data services.
Procedure
1. Run the BSC6900 MML command SET GCELLOTHEXT (CME single
Parameters in Batches). In this step, select NT14_5K and T14_4K in the Data
Service Allowed parameter.

GBSS14.0
1. Run the BSC6900 MML command LST GCELLOTHEXT to check the value of
Data service allowed.
Expected result: The values of both T14_4K and NT14_5K in the Data service
allowed parameter are USED.
2. Use an MS to initiate a 14.4 kbit/s circuit switched data service. Then, trace the
signaling on the A interface.
Expected result: The service has been initiated. After the signaling on the A interface
is parsed, the value of Channel Type in the Assignment Request message is as
follows:
– non-transparent data service
Figure 99-1 Non-transparent data service
– transparent data service
Figure 99-2 Transparent data service

GBSS14.0
Parameters in Batches). In this step, deselect NT14_5K and T14_4K in the Data
Service Allowed parameter.
----End

GBSS14.0
Feature Activation Guide 100 Configuring High Speed Circuit Switched Data
100 Configuring High Speed Circuit

Switched Data
High Speed Circuit Switched Data.
Prerequisites
– BTS3900E supports this feature.
– The BTSs that use the following TRX modules also support this feature: GRFU V2,
MRFU V2, GRFU V2a, MRFU V2a, MRFUd, MRFUe, RRU3008 V2, RRU3908 V2,
RRU3928, RRU3929, RRU3942, and RRU3926.
– This feature is incompatible with the following features: GBFD-117002 IBCA,
GBFD-117001 Flex MAIO.
l License
– The MS and the CN must support this feature.
– The feature works in a BM/TC combined mode.
– Dual-timeslot extension cells do not support multislot HSCSD. CS domain data services
can only use a single timeslot.
Context
With this feature, a maximum of four TCHs can be combined to form a channel group. The data
rate of such a channel group reaches up to 57.6 kbps, improving user experience.
Procedure

GBSS14.0
Parameters in Batches). In this step, set ECSC to YES(Yes).
Parameters in Batches). In this step, set Data Service Allowed to Choose All, and
set Maximum Number of HSCSD Channels and HSCSD Channel Scanning
Period to appropriate values based on the network plan.HSCSD Channel Scanning
Period can be set to the default value.
3. Run the BSC6900 MML command SET GCELLCHMGAD (CME single
Modifying GSM Cell Parameters in Batches). In this step, set HSCSD Traffic Busy
Threshold to an appropriate value based on the network plan or the default value.
5. Optional: Run the BSC6900 MML command SET OTHSOFTPARA (CME single
center: 3.17 Modifying GBSC Parameters in Batches). In this step, set the following
reserved parameters to appropriate values:
– Bit 13 of Reserved parameter 4: Specifies whether to change the primary channel
when a single channel is upgraded to multiple channels or multiple channels are
degraded to a single channel after the MS initiates HSCSD user rate speedup or
slowdown. If bit 13 is set to 1, the primary channel is not changed. If bit 13 is set
to 0, the primary channel is changed.
– Bit 14 of Reserved parameter 4: Specifies whether to allow a call to preempt the
secondary channel for HSCSD services. If bit 14 is set to 1, the call can preempt
the secondary channel. If bit 14 is set to 0, the call cannot preempt the secondary
channel.
– Bit 1 of Reserved parameter 10: Specifies whether to allow HSCSD channel
integration. If bit 1 is set to 1, HSCSD channel integration is not allowed. If bit 1
is set to 0, HSCSD channel integration is allowed.
NOTE
The cell to be verified is in the normal state and has at least 2 consecutive idle TCHF channels.
1. Run the BSC6900 MML command SET GCELLOTHEXT. In this step, set
Maximum Number of HSCSD Channels to NOT_SUPPORT(Not Support).
2. Use a test MS to establish CS-based data services at a rate of 28.8 kbps.
3. Initiate A interface message tracing on the LMT by referring to Tracing Messages on
the A Interface, and select BSSAP in the Trace Type area.
CS-based data services fail to be established. The Assignment Failure message is
traced on the A interface.

GBSS14.0
4. Run the BSC6900 MML command SET GCELLOTHEXT. In this step, set
Maximum Number of HSCSD Channels to TWO_CHANNELS(Two
Channels).
5. Use a test MS to establish CS-based data services at a rate of 28.8 kbps.
6. Initiate A interface message tracing on the LMT by referring to Tracing Messages on
the A Interface, and select BSSAP in the Trace Type area.
CS-based data services are established.
7. Monitor the channel state in the cell. The services occupy two consecutive channels.
Parameters in Batches). In this step, set Maximum Number of HSCSD
Channels to NOT_SUPPORT(Not Support).
----End
Example
//Activating High Speed Circuit Switched Data
//Enabling ECSC:
SET GCELLCCBASIC: IDTYPE=BYID, CELLID=2, ECSC=YES;
//Setting the data service, the maximum number of channels allowed for an
MS and the channel dynamic adjustment period:
SET GCELLOTHEXT: IDTYPE=BYID, CELLID=2,
DATATRAFFSET=NT14_5K-1&NT12K-1&NT6K-1&T14_4K-1&T9_6K-1&T4_8K-1&T2_4K-1&T1
_2K-1&T600_BITS-1&T1200_75-1, HSCSDTRAFFSET=TWO_CHANNELS,
HSCSDSCANPER=4500;
//Setting HSCSD traffic busy threshold:

SET GCELLCHMGAD: IDTYPE=BYID, CELLID=2, HSCSDBUSYTHRES=80;
//Setting interface tag:

//Setting that the primary channel is changed:

SET OTHSOFTPARA: BSCRESERVEDPARA4=57343;
//Setting that a call cannot preempt the secondary channel for HSCSD
services:
SET OTHSOFTPARA: BSCRESERVEDPARA4=49151;
//Setting that HSCSD channel integration is allowed:

SET GCELLOPTREV: IDTYPE=BYID, CELLID=0, CELLOPTRSVPARA10=65533;
//Deactivating High Speed Circuit Switched Data
SET GCELLOTHEXT: IDTYPE=BYID, CELLID=2, HSCSDTRAFFSET=NOT_SUPPORT;

GBSS14.0
Feature Activation Guide 101 Configuring Active TBF Allocation
101 Configuring Active TBF Allocation
Active TBF Allocation.
Prerequisites
l License
– The test cell is configured to support GPRS in built-in PCU mode.
– The test cell supports the GRPS or EDGE services.
Context
On the live network, the number of TBFs multiplexed on a PDCH cannot reflect the actual PDCH
usage. For low-throughput services, data transmission time is a small part of a TBF life cycle.
This leads to a PDCH usage.
The Active TBF Allocation feature directs the BSC to allocate PDCHs to TBFs to balance the
loads between PDCHs. Enabling this feature has the following impacts on system capacity:
l Increases the downlink LLC throughput of GPRS or EGPRS MSs when the number of
activated PDCHs remains unchanged or decreases.
l Increases the efficiency in which PDCHs carry TBFs by decreasing the number of activated
PDCHs, while maintaining the cell throughput and downlink LLC throughput.
l Data Preparation

GBSS14.0
Parameter Parameter ID Remarks Data Source

Name (Configuration
Principle for
Different
Scenarios)
Dynamic TBF ACTIVETBFSWITCH Set this parameter to Network

Switch ON(On). planning
Uplink Multiplex UPDYNCHNTRANLEV To increase the Network

Threshold of downlink LLC planning
Dynamic throughput of GPRS or
Channel EGPRS MSs, set
Conversion Dynamic TBF
Switch to ON(On).
To improve the
efficiency in which
PDCHs carry TBFs,
set Dynamic TBF
Switch to ON(On) and
Uplink Multiplex
Threshold of
Dynamic Channel
Conversion to a large
value.
Downlink DWNDYNCHNTRANLEV To increase the Network

Multiplex downlink LLC planning
Threshold of throughput of GPRS or
Dynamic EGPRS MSs, set
Channel Dynamic TBF
Conversion Switch to ON(On).
To improve the
efficiency in which
PDCHs carry TBFs,
set Dynamic TBF
Switch to ON(On) and
Downlink Multiplex
Threshold of
Dynamic Channel
Conversion to a large
value.
Procedure

GBSS14.0
Modifying GSM Cell Parameters in Batches). In this step, set Dynamic TBF
Switch to ON(ON).
1. Subscribe to the following counter:
TX.DOWN.EGPRS.LLC.PDU.THRPUT.RATE.AVG (AL9530: Downlink
Throughput of EGPRS Users LLC PDU).
Type to PDTCH(PDTCH) for at least one channel and set Channel Type to TCHFR
(TCH Full Rate) for multiple channels.
3. Run the BSC6900 MML command SET GCELLPSCHM. In this step, set Dynamic
TBF Switch to OFF(OFF).
4. Use multiple MSs to initiate EGPRS PS services. Ensure that most of them are low-
throughput services and few of them are FTP services.
5. Run the BSC6900 MML commandSET GCELLPSCHM. In this step, set Dynamic
TBF Switch to ON(On).
6. Maintain the EGPRS PS services in Step 4 for a period of time.
Expected result: The value of
TX.DOWN.EGPRS.LLC.PDU.THRPUT.RATE.AVG (AL9530: Downlink
Throughput of EGPRS Users LLC PDU) increases after the Active TBF Allocation
feature is enabled.
Modifying GSM Cell Parameters in Batches). In this step, setDynamic TBF
Switch to OFF(OFF).
----End
Example
//Activating Active TBF Allocation
SET GCELLPSCHM: IDTYPE=BYID, CELLID=1, ACTIVETBFSWITCH=ON;
//Deactivating Active TBF Allocation
SET GCELLPSCHM: IDTYPE=BYID, CELLID=1, ACTIVETBFSWITCH=OFF;

GBSS14.0
Feature Activation Guide 102 Configuring MSRD
102 Configuring MSRD
This section describes how to activate, verify, and deactivate the optional feature GBFD 510801
Mobile Station Receive Diversity (MSRD).
Prerequisites
required.
feature depends on the feature: GBFD-114101 GPRS.
– This feature is mutually exclusive to the feature: GBFD-510802 Dual Carriers in
Downlink.
l License
Context
The MSRD improves the signal receiving capability of the MS. Two antennas are used to
eliminate interference, therefore achieving enhanced channel diversity capability.
Procedure
Modifying GSM Cell Parameters in Batches). In this step, set MSRD PDCH
Downlink Multiplex Threshold to 10 and MSRD MCS Threshold to MCS9
(MCS9).

GBSS14.0
Feature Activation Guide 102 Configuring MSRD
1. Assume that the interference is the same and dual carrier in the downlink is not
supported. Use the MS that supports MSRD to perform packet services. Check that
the rate of this MS is more stable than the MS that does not support MSRD.
----End
Example
//Activating MSRD
SET GCELLPSCHM: IDTYPE=BYID, CELLID=0, MSRDPDCHLEV=10, MSRDMCSLEV=MCS9;

GBSS14.0
Feature Activation Guide 103 Configuring Dual Carriers in Downlink
103 Configuring Dual Carriers in

Downlink
Dual Carriers in Downlink (DLDC).
Prerequisites
required.
– This feature is mutually exclusive to the feature: GBFD-510801 MSRD.
l License
– The license controlling this feature has been activated.
– The cell has sufficient resources and the cell is configured with more than two carriers.
Context
The network supports the feature of allocating downlink channel resources on the two carriers
at the same time. This improves the rate of the downlink packet data.
The dual carriers in downlink function can improve the rate of the downlink packet data of a
single MS (100% at the most). A single MS may take up more resources, and therefore the
number of MSs supported by the network is reduced.
Procedure

GBSS14.0
Feature Activation Guide 103 Configuring Dual Carriers in Downlink

EDGE to YES(Yes), and Support Downlink Dual-Carrier to SUPPORT
(Support).
1. Use the MS to perform streaming services.
2. Refer to Monitoring Channel Status to check the usage of occupied channels.
Expected result:
and Support Downlink Dual-Carrier to UNSUPPORT(Not Support), EDGE to
NO(No).
----End
Example
//Activating DLDC
SET GCELLGPRS: IDTYPE=BYID, CELLID=0, GPRS=SupportAsInnPcu, EDGE=YES,
DLDCSPT=SUPPORT;
//Deactivating DLDC
SET GCELLGPRS: IDTYPE=BYID, CELLID=0, GPRS=SupportAsInnPcu, EDGE=NO,
DLDCSPT=UNSUPPORT;

GBSS14.0
Feature Activation Guide 104 Configuring the EGPRS2-A
104 Configuring the EGPRS2-A
Uplink EGPRS2-A and GBFD-510804 Downlink EGPRS2-A.
Prerequisites
required.
– This feature only applies to IP networking scenarios, the PEUa /POUc boards are needed
as Abis interface board, the DPUc boards are needed in GMPS /GEPS subrack.
feature depends on the following features: GBFD-118601 Abis over IP or
GBFD-118611 Abis IP over E1/T1 or GBFD-118401 Abis Transmission Optimization
or GBFD-114101 GPRS or GBFD-114201 EGPRS.
l License
– The Abis interface of the cell works in HDLC or IP mode.
– Only DBS3900(RRU3008) supports this feature.
– The TRXs configured for the BTS should support this feature.
– MS should support this feature.
Context
l After a cell is configured to support the EGPRS2-A, the network can allocate the Temporary
Block Flow (TBF) in EGPRS2-A mode to the MSs in the cell.
l Impact on the performance: The UL/DL packet rate of a single MS is improved. The uplink
data rate over the air interface can be increased to 76.8 kbit/TS and the downlink to 98.4
kbit/TS.

GBSS14.0
Feature Activation Guide 104 Configuring the EGPRS2-A
Procedure
and EGPRS2-A to YES(Yes).
1. Run the BSC6900 MML command SET GCELLEGPRSPARA. In this step, Uplink
EGPRS2-A Fixed MCS Type and Downlink EGPRS2-A Fixed MCS Type to the
coding types required by the test.
2. Use the MS to perform the PING service, and Tracing PS Domain Messages on the
Um Interface on the BSC6900 LMT. In this step, The uplink/downlink EGRPS2-A
coding schemes set in Step 1 can be viewed.
3. Run the BSC6900 MML command SET GCELLGPRS. In this step, set GPRS to
SupportAsInnPcu(Support as built-in PCU) and EGPRS2-A to NO(No).
4. Use the MS to perform the PING service, and Tracing PS Domain Messages on the
Um Interface on the BSC6900 LMT. The output result shows that only the coding
schemes from MCS1 to MCS9 are used.
and EGPRS2-A to NO(No).
----End
Example
SET GCELLGPRS: IDTYPE=BYID, CELLID=0, GPRS=SupportAsInnPcu, EGPRS2A=YES;
SET GCELLEGPRSPARA: IDTYPE=BYID, CELLID=0, UPE2AFIXMCS=MCS2,
DNE2AFIXMCS=MCS2;
SET GCELLGPRS: IDTYPE=BYID, CELLID=0, GPRS=SupportAsInnPcu, EGPRS2A=NO;
SET GCELLGPRS: IDTYPE=BYID, CELLID=0, GPRS=SupportAsInnPcu, EGPRS2A=NO;

GBSS14.0
Feature Activation Guide 105 Configuring Latency Reduction
105 Configuring Latency Reduction
Latency Reduction.
Prerequisites
– BSC6900 built-in PCU should be used, the Packet Process board and Gb interface board
is required.
– This feature only applies to IP networking scenarios.
feature depends on the features GBFD-118601 Abis over IP or GBFD-118611 Abis IP
over E1/T1 or GBFD-118401 Abis Transmission Optimization or GBFD-114201
EGPRS.
l License
– The BTS and MS support the latency reduction.
Context
Latency reduction is introduced in the HDLC/IP transmission mode over the Abis interface to
reduce the transmission latency, enhance user experience on the conversational service, and
improve user satisfaction.
NOTE
BTS3006C/BTS3002E/BTS3012/BTS3012AE/BTS3900B/E do not support this feature.
Procedure

GBSS14.0
Feature Activation Guide 105 Configuring Latency Reduction
EDGE to YES(Yes), and Support Reduced Latency Capability to SUPPORT
(Support).
1. Use the MS to perform conversational services in the PS domain.
2. Run the BSC6900 MML command DSP PDCH to query the status of the PDCH.
Expected Result: In the displayed result, the number of RTTI TBFs on the PDCH is
not zero.
and Support Reduced Latency Capability to UNSUPPORT(Not Support).
----End
Example
//Activating Latency Reduction
SPTREDUCELATENCY=SUPPORT;
//Deactivating Latency Reduction
SPTREDUCELATENCY=UNSUPPORT;

GBSS14.0
Feature Activation Guide 106 Configuring IM Service Efficiency Improvement
106 Configuring IM Service Efficiency

Improvement
deactivate the optional feature GBFD-511603 IM Service Efficiency Improvement.
Prerequisites
This feature depends on the GBFD-114101 GPRS or GBFD-114201 EGPRS feature.
The ARP1 scheduling weight, ARP2 scheduling weight, and ARP3 scheduling weight
functions of this feature depend on the GBFD-119902 QoS ARP&THP or
GBFD-119907 PS Service in Priority feature.
– IM PDCH Multiplexing Weight becomes ineffective when this feature and
GBFD-119407 Active TBF Allocation are enabled simultaneously.
l License
The Network Intelligence Unit (NIUa) board is configured.
The built-in PCU is configured.
This feature is ineffective when the logical link control (LLC) layer is encrypted, or the
subnetwork dependent convergence protocol (SNDCP) layer is compressed because the
services cannot be identified.

GBSS14.0
N/A
Context
l Data Preparation
Parameter
Name Parameter ID Parameter Setting Data Source
Board Class BRDCLASS NIU Internal

planning
Board Type BRDTYPE NIUa Internal

planning
Logical function LGCAPPTYPE NIU Internal

type planning
Subrack No. SRN Number of the subrack that Internal

houses the NIU board planning
Slot No. SN Number of the slot that Internal

MPU Subrack MPUSUBRACK Number of the subrack that Internal

No. houses the MPU subsystem planning
MPU Slot No. MPUSLOT Number of the slot that Internal

houses the MPU subsystem planning
GPRS GPRS SupportAsInnPcu(Support Network

as built-in PCU) planning
Support DPI SPTDPI BSCSUPPORT(BSC Network

Support) planning
Protocol ID PROTOCOLID ID of the protocol used by Network

PS services. Set this planning
parameter based on
customers' requirements.
Service Type TRAFFICTYPE IMSERVICE(Instant Network

Messaging Service) planning
Maximum IMARP1MAXPD Set this parameter based on Network

Number of CHNUM the service priority. planning
PDCHs for IM
ARP1

PDCHs for IM
ARP2

GBSS14.0
Parameter

PDCHs for IM
ARP3
IM ARP1 IMARP1WEIGHT Set this parameter based on Network

Scheduling the service priority. planning
Weight

Weight

Weight
IM PDCH IMPDCHMULTIP Set this parameter based on Network

Multiplexing LEXWEIGHT the service priority. planning
Weight
IM Downlink IMDLTBFRELDE Set this parameter based on Network

TBF Release LAY the service priority. planning
Delay
IM Service IMOPT Whether to enable the Network

Optimize function of optimizing IM planning
services. If this parameter is
set to ON(On), the BSC
allocates radio resources to
IM services based on the
settings of IM service
optimization parameters.
Procedure
Panel > Add Board; CME batch modification center: not supported) to add an NIU
board. In this step, set Board Class to NIU, Board Type to NIUa, Logical function
type to NIU, Subrack No. and Slot No. to the number of the subrack and the number
of the slot that houses the NIU board, and MPU Subrack No. and MPU Slot No. to
the number of the subrack and the number of the slot that houses the MPU subsystem,
respectively.
Batches) to enable service identification. In this step, set GPRS to SupportAsInnPcu
(Support as built-in PCU) and Support DPI to BSCSUPPORT(BSC Support).

GBSS14.0
3. Run the BSC6900 MML command ADD TRAFFICMAP (CME single

the Mapping Between Protocol IDs and Service Types; CME batch modification
center: not supported) to map a specific protocol ID to an instant messaging (IM)
service. In this step, set Protocol ID to an appropriate value and Service Type to
IMSERVICE(Instant Messaging Service).
NOTE
For details about the mapping between Protocol ID and protocol name for specific services,
see the Protocol List.
4. Run the BSC6900 MML command SET GCELLPSDIFFSERVICE (CME single
configuration: Cell Configuration Express > GPRS Attributes > Service-based
Differentiated PS Parameters; CME batch modification center: 3.20 Modifying
GSM Cell Parameters in Batches). In this step, set IM Service Optimize to ON
(On) and configure resource optimization parameters for IM services.
NOTE
l Maximum Number of PDCHs for IM ARP1, Maximum Number of PDCHs for IM

ARP2 and Maximum Number of PDCHs for IM ARP3 must be set to appropriate values
simultaneously.
l IM ARP1 Scheduling Weight, IM ARP2 Scheduling Weight and IM ARP3 Scheduling
Weight must be set to appropriate values simultaneously.
1. Run the BSC6900 MML command SET GCELLPSDIFFSERVICE. In this step,
set Maximum Number of PDCHs for IM ARP1, Maximum Number of PDCHs
for IM ARP2, and Maximum Number of PDCHs for IM ARP3 to 1.
2. Run the BSC6900 MML command SET GCELLPSCHM, In this step, set Layered
Service Optimize Start Threshold to 0.
3. Use an MS to perform an IM service for more than one minute and check whether
only one PDCH is occupied by the MS on the Web LMT. Ensure that a specific
protocol ID has been mapped to the IM service.
GSM Cell Parameters in Batches), In this step, set IM Service Optimize to OFF
(Off).
----End
Example
//Adding an NIU board
ADD BRD: SRN=0, BRDCLASS=NIU, BRDTYPE=NIUa, SN=10, MPUSUBRACK=0,
MPUSLOT=0;
//Setting a cell to support BSC service awareness
SPTDPI=BSCSUPPORT;
//Adding mapping
ADD TRAFFICMAP: PROTOCOLID=184, TRAFFICTYPE=IMSERVICE;
//Setting resource optimization parameters for IM services
SET GCELLPSDIFFSERVICE: IDTYPE=BYID, CELLID=0, IMARP1MAXPDCHNUM=1,
IMARP2MAXPDCHNUM=1,

GBSS14.0
IMARP3MAXPDCHNUM=1, IMARP1WEIGHT=5, IMARP2WEIGHT=5, IMARP3WEIGHT=5,

IMPDCHMULTIPLEXWEIGHT=50, IMDLTBFRELDELAY=1200, IMOPT=ON;
SET GCELLPSDIFFSERVICE: IDTYPE=BYID, CELLID=0, IMOPT=OFF;

GBSS14.0 107 Configuring Web Browsing Service Efficiency
Feature Activation Guide Improvement
107 Configuring Web Browsing Service

Efficiency Improvement
deactivate the optional feature GBFD-511604 Web Browsing Service Efficiency Improvement.
Prerequisites
– Web Browsing PDCH Multiplexing Weight becomes ineffective when this feature
and GBFD-119407 Active TBF Allocation are enabled simultaneously.
l License

N/A
Context
l Data Preparation
Parameter

planning

planning

type planning






Support) planning

parameter based on
Service Type TRAFFICTYPE WEBSERVICE(Web Page Network

Browsing Service) planning
Maximum WEBARP1MAXP Set this parameter based on Network

Number of DCHNUM the service priority. planning
PDCHs for Web
Browsing ARP1

PDCHs for Web
Browsing ARP2

Parameter

PDCHs for Web
Browsing ARP3
Web Browsing WEBARP1WEIG Set this parameter based on Network

ARP1 HT the service priority. planning
Scheduling
Weight

Scheduling
Weight

Scheduling
Weight
Web Browsing WEBPDCHMULT Set this parameter based on Network

PDCH IPLEXWEIGHT the service priority. planning
Multiplexing
Weight
Web Browsing WEBDLTBFREL Set this parameter based on Network

Downlink TBF DELAY the service priority. planning
Release Delay
Web Browsing WEBOPT Whether to enable the Network

Service function of optimizing web planning
Optimize browsing services. If this
parameter is set to ON(On),
the BSC allocates radio
resources to web browsing
services based on the
settings of web browsing
service optimization
parameters.
Procedure
respectively.

Batches) to enable service identification. In this step, set GPRS and Support DPI to
SupportAsInnPcu(Support as built-in PCU) and BSCSUPPORT(BSC
Support), respectively.
center: not supported) to map a specific protocol ID to a web browsing service. In this
step, set Protocol ID to an appropriate value and Service Type to WEBSERVICE
(Web Page Browsing Service).
NOTE
GSM Cell Parameters in Batches). In this step, set Web Browsing Service
Optimize to ON(On) and configure resource optimization parameters for web
browsing services.
NOTE
l Maximum Number of PDCHs for Web Browsing ARP1, Maximum Number of

PDCHs for Web Browsing ARP2 and Maximum Number of PDCHs for Web
Browsing ARP3 must be set to appropriate values simultaneously.
l Web Browsing ARP1 Scheduling Weight, Web Browsing ARP2 Scheduling Weight
and Web Browsing ARP3 Scheduling Weight must be set to appropriate values
simultaneously.
set Maximum Number of PDCHs for Web Browsing ARP1, Maximum Number
of PDCHs for Web Browsing ARP2, and Maximum Number of PDCHs for Web
Browsing ARP3 to 1.
3. Use an MS to perform a web browsing service for more than one minute and check
whether only one PDCH is occupied by the MS on the Web LMT. Ensure that a
specific protocol ID has been mapped to the web browsing service.
GSM Cell Parameters in Batches), In this step, set Web Browsing Service
Optimize to OFF(Off).
----End
Example


MPUSLOT=0;
SPTDPI=BSCSUPPORT;
//Adding mapping
ADD TRAFFICMAP: PROTOCOLID=64, TRAFFICTYPE=WEBSERVICE;
//Setting resource optimization parameters for web browsing services
SET GCELLPSDIFFSERVICE: IDTYPE=BYID, CELLID=0, WEBARP1MAXPDCHNUM=2,
WEBARP2MAXPDCHNUM=2,
WEBARP3MAXPDCHNUM=2, WEBARP1WEIGHT=10, WEBARP2WEIGHT=10,
WEBARP3WEIGHT=10,
WEBPDCHMULTIPLEXWEIGHT=50, WEBDLTBFRELDELAY=2400, WEBOPT=ON;
SET GCELLPSDIFFSERVICE: IDTYPE=BYID, CELLID=0, WEBOPT=OFF;

GBSS14.0
Feature Activation Guide 108 Configuring Email Service Efficiency Improvement
108 Configuring Email Service Efficiency

Improvement
deactivate the optional feature GBFD-511605 Email Service Efficiency Improvement.
Prerequisites
– Email PDCH Multiplexing Weight becomes ineffective when this feature and
l License

GBSS14.0
N/A
Context
l Data Preparation
Parameter

planning

planning

type planning






Support) planning

parameter based on
Service Type TRAFFICTYPE EMAILSERVICE(Email Network

Service) planning
Maximum EMAILARP1MA Set this parameter based on Network

Number of XPDCHNUM the service priority. planning
PDCHs for
Email ARP1

PDCHs for
Email ARP2

GBSS14.0
Parameter

PDCHs for
Email ARP3
Email ARP1 EMAILARP1WEI Set this parameter based on Network

Scheduling GHT the service priority. planning
Weight

Weight

Weight
Email PDCH EMAILPDCHMU Set this parameter based on Network

Multiplexing LTIPLEXWEIGH the service priority. planning
Weight T
Email Downlink EMAILDLTBFRE Set this parameter based on Network

TBF Release LDELAY the service priority. planning
Delay
Email Service EMAILOPT Whether to enable the Network

Optimize function of optimizing planning
email services. If this
parameter is set to ON(On),
the BSC allocates radio
resources to email services
based on the settings of
email service optimization
parameters.
Procedure
board. In this step, set Board Class to NIU, Board type to NIUa, Logic function
respectively.

GBSS14.0

center: not supported) to map a specific protocol ID to an email service. In this step,
set Protocol ID to an appropriate value and Service Type to EMAILSERVICE
(Email Service).
NOTE
GSM Cell Parameters in Batches). In this step, set Email Service Optimize to ON
(On) and configure resource optimization parameters for email services.
NOTE
l Maximum Number of PDCHs for Email ARP1, Maximum Number of PDCHs for
Email ARP2 and Maximum Number of PDCHs for Email ARP3 must be set to
appropriate values simultaneously.
l Email ARP1 Scheduling Weight, Email ARP2 Scheduling Weight and Email ARP3
Scheduling Weight must be set to appropriate values simultaneously.
set Maximum Number of PDCHs for Email ARP1, Maximum Number of PDCHs
for Email ARP2, and Maximum Number of PDCHs for Email ARP3 to 1.
3. Use an MS to perform an email service for more than one minute and check whether
protocol ID has been mapped to the email service.
GSM Cell Parameters in Batches), In this step, set Email Service Optimize to OFF
(Off).
----End
Example
MPUSLOT=0;
SPTDPI=BSCSUPPORT;
//Adding mapping
ADD TRAFFICMAP: PROTOCOLID=449, TRAFFICTYPE=EMAILSERVICE;
//Setting resource optimization parameters for email services

GBSS14.0
SET GCELLPSDIFFSERVICE: IDTYPE=BYID, CELLID=0, EMAILARP1MAXPDCHNUM=3,

EMAILARP2MAXPDCHNUM=3,
EMAILARP3MAXPDCHNUM=3, EMAILARP1WEIGHT=10, EMAILARP2WEIGHT=10,
EMAILARP3WEIGHT=10,
EMAILPDCHMULTIPLEXWEIGHT=80, EMAILDLTBFRELDELAY=80, EMAILOPT=ON;
SET GCELLPSDIFFSERVICE: IDTYPE=BYID, CELLID=0, EMAILOPT=OFF;

GBSS14.0 109 Configuring Streaming Media Service Resource
Feature Activation Guide Balancing
109 Configuring Streaming Media

Service Resource Balancing
deactivate the optional feature GBFD-511606 Streaming Media Service Resource Balancing.
Prerequisites
– Streaming Media PDCH Multiplexing Weight becomes ineffective when this feature
and GBFD-119407 Active TBF Allocation are enabled simultaneously.
l License

N/A
Context
l Data Preparation
Parameter

planning

planning

type planning






Support) planning

parameter based on
Service Type TRAFFICTYPE STREAMINGSERVICE Network

(Streaming Media Service) planning
Maximum STREAMINGAR Set this parameter based on Network

Number of P1MAXPDCHNU the service priority. planning
PDCHs for M
Streaming
Media ARP1

PDCHs for M
Streaming
Media ARP2

Parameter

PDCHs for M
Streaming
Media ARP3
Streaming STREAMINGAR Set this parameter based on Network

Media ARP1 P1WEIGHT the service priority. planning
Scheduling
Weight

Scheduling
Weight

Scheduling
Weight
Streaming STREAMPDCHM Set this parameter based on Network

Media PDCH ULTIPLEXWEIG the service priority. planning
Multiplexing HT
Weight
Streaming STREAMINGDL Set this parameter based on Network

Media TBFRELDELAY the service priority. planning
Downlink TBF
Release Delay
Streaming STREAMINGOPT Whether to enable the Network

Media Service function of optimizing planning
Optimize streaming media services.
If this parameter is set to
ON(On), the BSC allocates
radio resources to
streaming media services
based on the settings of
streaming media service
Procedure

respectively.
center: not supported) to map a specific protocol ID to a streaming media service. In
this step, set Protocol ID to an appropriate value and Service Type to
STREAMINGSERVICE(Streaming Media Service).
NOTE
GSM Cell Parameters in Batches). In this step, set Streaming Media Service
Optimize to ON(On) and configure resource optimization parameters for streaming
media services.
NOTE
l Maximum Number of PDCHs for Streaming Media ARP1, Maximum Number of

PDCHs for Streaming Media ARP2 and Maximum Number of PDCHs for Streaming
Media ARP3 must be set to appropriate values simultaneously.
l Streaming Media ARP1 Scheduling Weight, Streaming Media ARP2 Scheduling
Weight and Streaming Media ARP3 Scheduling Weight must be set to appropriate
values simultaneously.
set Maximum Number of PDCHs for Streaming Media ARP1, Maximum
Number of PDCHs for Streaming Media ARP2, and Maximum Number of
PDCHs for Streaming Media ARP3 to 1.
3. Use an MS to perform a streaming media service for more than one minute and check
whether only one PDCH is occupied by the MS on the Web LMT. Ensure that a
specific protocol ID has been mapped to the streaming media service.
GSM Cell Parameters in Batches),In this step, set Streaming Media Service
Optimize to OFF(Off).
----End

Example
MPUSLOT=0;
SPTDPI=BSCSUPPORT;
//Adding mapping
ADD TRAFFICMAP: PROTOCOLID=209, TRAFFICTYPE=STREAMINGSERVICE;
//Setting resource optimization parameters for streaming media services
SET GCELLPSDIFFSERVICE: IDTYPE=BYID, CELLID=0,
STREAMINGARP1MAXPDCHNUM=4,
STREAMINGARP2MAXPDCHNUM=4, STREAMINGARP3MAXPDCHNUM=4,
STREAMINGARP1WEIGHT=10,
STREAMINGARP2WEIGHT=10, STREAMINGARP3WEIGHT=10,
STREAMPDCHMULTIPLEXWEIGHT=100, STREAMINGDLTBFRELDELAY=2400,
STREAMINGOPT=ON;
SET GCELLPSDIFFSERVICE: IDTYPE=BYID, CELLID=0, STREAMINGOPT=OFF;

GBSS14.0
Feature Activation Guide 110 Configuring P2P Resource Balancing
110 Configuring P2P Resource Balancing
deactivate the optional feature GBFD-511607 P2P Resource Balancing.
Prerequisites
– P2P PDCH Multiplexing Weight becomes ineffective when this feature and
l License

GBSS14.0
N/A
Context
l Data Preparation
Parameter Parameter ID Parameter Setting Data Source
Name

planning

planning

type planning




GPRS GPRS SupportAsInnPcu(Support Internal

Support DPI SPTDPI BSCSUPPORT(BSC Internal

Support) planning
Protocol ID PROTOCOLID ID of the protocol used by Internal

parameter based on
Service Type TRAFFICTYPE P2PSERVICE(P2P Internal

Service) planning
Maximum P2PARP1MAXPD Set this parameter based on Internal

PDCHs for P2P
ARP1

PDCHs for P2P
ARP2

GBSS14.0

Name

PDCHs for P2P
ARP3
P2P ARP1 P2PARP1WEIGH Set this parameter based on Internal

Scheduling T the service priority. planning
Weight

Weight

Weight
P2P PDCH P2PPDCHMULTI Set this parameter based on Internal

Multiplexing PLEXWEIGHT the service priority. planning
Weight
P2P Downlink P2PDLTBFRELD Set this parameter based on Internal

TBF Release ELAY the service priority. planning
Delay
P2P Service P2POPT Whether to enable the Internal

Optimize function of optimizing P2P planning
services. If this parameter is
set to ON(On), the BSC
allocates radio resources to
P2P services based on the
settings of P2P service
Procedure
respectively.

GBSS14.0

center: not supported) to map a specific protocol ID to a point-to-point (P2P) service.
In this step, set Protocol ID to an appropriate value and Service Type to
P2PSERVICE(P2P Service).
NOTE
GSM Cell Parameters in Batches). In this step, set P2P Service Optimize to ON
(On) and configure resource optimization parameters for P2P services.
NOTE
l Maximum Number of PDCHs for P2P ARP1, Maximum Number of PDCHs for P2P
ARP2 and Maximum Number of PDCHs for P2P ARP3 must be set to appropriate values
simultaneously.
l P2P ARP1 Scheduling Weight, P2P ARP2 Scheduling Weight and P2P ARP3
Scheduling Weight must be set to appropriate values simultaneously.
set Maximum Number of PDCHs for P2P ARP1, Maximum Number of PDCHs
for P2P ARP2, and Maximum Number of PDCHs for P2P ARP3 to 1.
3. Use an MS to perform a P2P service for more than one minute and check whether
protocol ID has been mapped to the P2P service.
GSM Cell Parameters in Batches),In this step, set P2P Service Optimize to OFF
(Off).
----End
Example
MPUSLOT=0;
SPTDPI=BSCSUPPORT;
//Adding mapping
ADD TRAFFICMAP: PROTOCOLID=842, TRAFFICTYPE=P2PSERVICE;
//Setting resource optimization parameters for P2P services

GBSS14.0
SET GCELLPSDIFFSERVICE: IDTYPE=BYID, CELLID=0, P2PARP1MAXPDCHNUM=4,

P2PARP2MAXPDCHNUM=4,
P2PARP3MAXPDCHNUM=4, P2PARP1WEIGHT=10, P2PARP2WEIGHT=10,
P2PARP3WEIGHT=10,
P2PPDCHMULTIPLEXWEIGHT=100, P2PDLTBFRELDELAY=2400, P2POPT=ON;
SET GCELLPSDIFFSERVICE: IDTYPE=BYID, CELLID=0, P2POPT =OFF;

GBSS14.0
Feature Activation Guide 111 Configuring WLAN Hot Spot Notification
111 Configuring WLAN Hot Spot

Notification
WLAN Hot Spot Notification.
Prerequisites
l License
– N/A
– N/A
– A suitable WLAN traffic distribution application is installed on a terminal.
– This feature is supported only for a built-in packet control unit (PCU).
– This feature does not apply to encryption and compression at the LLC-PDU or SNDCP
layer.
– This feature does not apply to encryption at the network layer.
– This feature does not apply to the acknowledgement mode at the logical link control
(LLC) layer.
Context
As PS traffic in mobile networks soars, mobile networks face a greater challenge of traffic. The
WLAN Hot Spot Notification feature helps to discover WiFi hot spots and distribute intelligent
WiFi under control of mobile networks by coordinating WiFi and mobile networks, therefore

GBSS14.0
improving the usage of operators' WLANs and relieving the pressure of PS traffic in mobile
networks.
l Precautions
– None
l Data Preparation
Parameter
Service Set ID SSID Set this parameter to the Network

same value as the SSID of planning
the WLAN.
WLAN Control WlanCtrl Operators can enable or Network

Policy disable this function based planning
on their WiFi coverage or
cell load.
WLAN Load LoadThrToWlan Set this parameter when Network

Distribution WLAN Control Policy is planning
Start Threshold set to ON(ON). The
recommended value for this
parameter is 60.
WLAN Load LoadThrStpWlan Set this parameter when Network

Distribution WLAN Control Policy is planning
Stop Threshold set to ON(ON). The value
of this parameter must be
less than WLAN Load
Distribution Start
Threshold. The
parameter is 40.
Wi-Fi Searching WifiTmr Duration for a terminal to Network

Duration search for WiFi. The planning
parameter is 10.
Wi-Fi Disable StpWifiTmr A period of time after Network

Timer which WiFi is disabled planning
automatically if no data
traffic occurs from the
moment when WiFi is
enabled. The recommended
value for this parameter is
300.
Procedure
1. Run the BSC6900 MML command ADD GWLANINFO (CME single configuration:
GSM Global Configuration Express > BSC Basic Configuration > Operator

GBSS14.0
WLAN Information; CME batch modification center: not supported). In this step,
set Service Set ID to an appropriate value.
2. Run the BSC6900 MML command SET GCELLWLAN (CME single configuration:
Cell Configuration Express > GPRS Attributes > WLAN Distribution Control
Parameters for GSM Cells; CME batch modification center: 3.20 Modifying GSM
Cell Parameters in Batches). In this step, set WLAN Control Policy to ON(ON)
and set WLAN Load Distribution Start Threshold, WLAN Load Distribution
Stop Threshold, Wi-Fi Searching Duration, and Wi-Fi Disable Timer to
appropriate values.
1. Run the BSC6900 MML command LST GCELLWLAN to query parameters
controlling WLAN traffic distribution in GSM cells.
Expected results: WLAN Control Policy is set to ON.
2. Verify that the following results are achieved when the cell load exceeds the value of
WLAN Load Distribution Start Threshold:
Expected results: The WiFi function is automatically enabled on the MS on which the
WLAN distribution software is installed, and partial PS services on the GSM network
are distributed to the WLAN.
1. Run the BSC6900 MML command SET GCELLWLAN (CME single configuration:
Cell Configuration Express > GPRS Attributes > WLAN Distribution Control
Parameters for GSM Cells; CME batch modification center: 3.20 Modifying GSM
Cell Parameters in Batches). In this step, set WLAN Control Policy to OFF
(OFF).
----End
Example
//Activating WLAN Hot Spot Notification
ADD GWLANINFO: OPINDEX=1, SSID="CMCC";
SET GCELLWLAN: IDTYPE=BYID, CELLID=1, WlanCtrl=ON, LoadThrToWlan=60,
LoadThrStpWlan=40, WifiTmr=10, StpWifiTmr=300;
//Deactivating WLAN Hot Spot Notification
SET GCELLWLAN: IDTYPE=BYID, CELLID=1, WlanCtrl=OFF;

GBSS14.0
Feature Activation Guide 112 Configuring Multiple CCCHs
112 Configuring Multiple CCCHs
Multiple CCCHs.
Prerequisites
l License
Context
Based on configuration of BCCH TRX timeslot 0 as the BCCH physical channel, the feature of
Multiple CCCHs allows one to configure timeslots 2, 4, and 6 as BCCH physical channels. This
increases the number of CCCHs in a cell and therefore improves the paging and random access
capabilities of the cell.
Procedure
modification center: 3.22 Modifying GSM TRX Parameters in Batches) with TRX
ID and Channel No. set to appropriate values and Channel Type set to BCH
(BCH).
NOTE
The main BCCH can be configured in only channel 0, and the extension BCCH can be
configured in channel 2, 4, or 6.
If an extension BCCH is configured, the CCCH parameter in the system message needs to be
configured accordingly. For example, if an extension BCCH is configured in timeslot 2, the
CCCH parameter in the system message needs to be configured as two uncombined CCCHs.

GBSS14.0
Feature Activation Guide 112 Configuring Multiple CCCHs
1. Run the BSC6900 MML command SET GTRXCHAN with TRX ID set to an
appropriate value, Channel No. set to 2, and Channel Type set to TCHFR(TCH
Full Rate) or TCHHR(TCH Half Rate).
2. Make a call.
3. Trace RSL messages on the Abis interface by referring to Tracing CS Domain
Messages on the Abis Interface.
Expected result: The value of channel-no. in all paging messages is 0.
4. Run the BSC6900 MML command SET GTRXCHAN with TRX ID set to an
appropriate value, Channel No. set to 2, and Channel Type set to BCH(BCH).
5. Make a call.
Expected result: In paging messages, the value of channel-no. is 2.
modification center: 3.22 Modifying GSM TRX Parameters in Batches) with TRX
ID and Channel No. set to appropriate values, and Channel Type set to TCHFR
(TCH Full Rate) or TCHHR(TCH Half Rate).
----End
Example
//Activating Multiple CCCHs
SET GTRXCHAN: TRXID=0, CHNO=2, CHTYPE=BCH;
//Deactivating Multiple CCCHs
SET GTRXCHAN: TRXID=0, CHNO=2, CHTYPE=TCHFR;

GBSS14.0
Feature Activation Guide 113 Configuring Layered Paging
Layered Paging.
Prerequisites
l License
– GSM, UMTS, or LTE neighboring cells are configured.
– The value of the Ready timer configured on the SGSN side is obtained.
– Layered Paging must be enabled for cells that correspond to the same network service
entity (NSE). Otherwise, Layered Paging does not take effect.
Context
The CCCHs will be overloaded when the number of PS paging messages exceeds that of CS
paging messages and increases continuously, which affects the access CS users. Layered paging
enables the first paging to be sent only to the last cell on which the MS camps and to its configured
neighboring cells, reducing the CCCHs for PS paging.
Procedure

GBSS14.0
Feature Activation Guide 113 Configuring Layered Paging
and then set PS Paging Control to FIRSTPRECISEPAGING(First precise

paging) or ALWAYSNORMALPAGING(Always normal paging) according to
the network planning.
Modifying GBSC Parameters in Batches), set Ready Timer. Note that the value of
the Ready timer must be the same as that of the Ready timer configured on the SGSN
side.
1. Connect an MS to a laptop and initiate PS services. Then, record the IP address of the
MS and stop PS services.
2. On the LMT, trace SIG messages on the Gb interface by referring to Tracing SIG
Messages on the Gb Interface and trace CS messages on the Um interface by referring
to Tracing CS Domain Messages on the Um Interface.
3. Wait for a period longer than the value of the Ready timer, and then ping the IP address
of the MS on the FTP server to trigger the paging procedure.
Expected result:
– The PS PAGING message can be viewed in the SIG messages traced on the Gb
interface.
– In the CS messages traced on the Um interface, the Packet Ccch Command or
Paging Request message can be viewed only in the cell where the MS camps when
processing PS services and the configured neighboring cells.
and then set PS Paging Control to ALWAYSNORMALPAGING(Always normal
paging).
----End
Example
PSPagingCtrl=FIRSTPRECISEPAGING;
SET BSCPSSOFTPARA: ReadyTimer=44;
PSPagingCtrl=ALWAYSNORMALPAGING;

GBSS14.0
Feature Activation Guide 114 Configuring Dynamic Multiple CCCH
114 Configuring Dynamic Multiple

CCCH
In traffic surge scenarios such as holidays or emergencies, paging overload occurs, which greatly
affects services. In static multiple common control channel (CCCH) configuration mode, the
specific number of configured channels is difficult to determine. If the configured channels are
insufficient, paging overload cannot be resolved thoroughly; if excessive channels are
configured, channel resources are wasted. The Dynamic Multiple CCCH feature can resolve the
preceding issues. With this feature, if the load on the CCCHs increases, the TCHs corresponding
to timeslots 2, 4, and 6 on the BCCH TRX are dynamically converted to CCCHs in succession.
This increases the paging capability over the Um interface. If the load on the CCCHs decreases,
the CCCHs corresponding to timeslots 6, 4, and 2 on the BCCH TRX are dynamically converted
to TCHs in succession. This increases the resource usage. This section describes how to activate,
verify, and deactivate the optional feature GBFD-511503 Dynamic Multiple CCCH.
Prerequisites
This feature does not depend on other features.
l License
Only 3900 series base stations support this feature. BTS3900B/BTS3900E do not support
this feature.
N/A
N/A
N/A

GBSS14.0
Context
l Precautions
1. If timeslot 0 of the BCCH TRX is combined BCCH or BCCH+CBCH, the Dynamic
Multiple CCCH feature cannot be enabled for the BCCH TRX.
2. You are advised to enable or disable this feature in all the cells under the same location
area.
NOTE
The paging mode used by the Huawei BSS is: location area code (LAC) paging and BSC paging.
3. Set BCCH TRX RSL Multiplexing Mode
– TMSI paging: When Maximum Number of Dynamic CCCHs plus the number
of static BCHs is 1, 2, and 3, you are advised to set BCCH TRX RSL Multiplexing
Mode to MODE2_1, MODE1_1, and MODE1_1, respectively.
– IMSI paging: When Maximum Number of Dynamic CCCHs plus the number
of static BCHs is 1, 2, and 3, you are advised to set BCCH TRX RSL Multiplexing
Mode to MODE4_1, MODE2_1, and MODE1_1.
NOTE
A large value of Maximum Number of Dynamic CCCHs represents a high Um interface

capability. To avoid message delivery congestion over the Abis interface, you need to increase
the RSL bandwidth of BCCHs and set BCCH TRX RSL Multiplexing Mode by referring to
the preceding suggestions.
4. The following negative gains occur on the channels involved in baseband frequency
hopping, on the channels configured as SDCCHs or static PDCHs, and on the channels
reserved for VIP users in the cell:
– If Maximum Number of Dynamic CCCHs is set to 1, the channels cannot be
configured in timeslot 2. Otherwise, this feature cannot be enabled.
configured in timeslot 2 or 4. Otherwise, this feature cannot be enabled.
configured in timeslot 2, 4, or 6. Otherwise, this feature cannot be enabled.
l Data Preparation
Parameter Data
Dynamic DynCCCHSwitch If static BCHs are configured in Internal

Multiple a cell, remove static BCHs and planning
CCCHs enable this feature in all cells
under the location area. If over
70% of all cells under a location
area experience paging timeout
during peak hours on the live
network, disable this feature in all
the cells under the location area.
If over 160,000 paging messages
are sent in one peak hour in a cell
on the live network, enable this
feature in all the cells under the
location area.

GBSS14.0
Parameter Data
Dynamic DynCCCHLoa- Load threshold for dynamically Network

CCCH dIncrThr converting a TCH to an extended planning
Addition CCCH. If the CCCH load is
Threshold higher than the value of this
parameter within the duration
specified by
DynCCCHLoadDuration, a TCH
is dynamically converted to an
extended CCCH. The larger the
value of this parameter, the less
the number of TCHs dynamically
converted to extended CCCHs
during peak hours, the lower the
paging efficiency. The smaller
the value of this parameter, the
more the number of TCHs
dynamically converted to
extended CCCHs during off-
peak hours, the lower the
resource usage.
Dynamic DynCCCHLoa- Load threshold for dynamically Network

CCCH dRedcThr converting an extended CCCH to planning
Removal a TCH. An extended CCCH can
Threshold be dynamically converted to a
TCH if the following conditions
are met: The CCCH load is lower
than the value of this parameter
within the duration specified by
DynCCCHLoadDuration. The
BSC predicts that the message
sending capability on the Um
interface is adequate after the
number of CCCHs decreases.
The interval between two
consecutive conversions reaches
the value specified by
DynCCCHReduceInterval. The
larger the value of this parameter,
the more the number of extended
CCCHs dynamically converted
to TCHs during peak hours, the
lower the paging efficiency. The
smaller the value of this
parameter, the more the number
of extended CCCHs dynamically
converted to TCHs during off-
peak hours, the lower the
resource usage.

GBSS14.0
Parameter Data
Dynamic DynCCCHLoadDu Duration during which the Network

CCCH Load ration CCCH load is higher than the planning
Stat. Duration value of "DynCCCHLoa-
dIncrThr" or lower than the value
of "DynCCCHLoadRedcThr".
After this duration is exceeded,
the BTS triggers dynamic
additions or removals of
extended CCCHs. The larger the
value of this parameter, the
longer the time to trigger
dynamic conversion between
extended CCCHs and TCHs, the
less the number of dynamic
conversions, the lower the paging
efficiency. The smaller the value
of this parameter, the shorter the
time to trigger dynamic
conversion between extended
CCCHs and TCHs, the more the
number of unnecessary
conversions due to inaccurate
determination, the lower the
resource usage.

GBSS14.0
Parameter Data
Maximum MaxDynCCCHNu Maximum number of extended Network

Number of m CCCHs that can be dynamically planning
Dynamic converted in a cell. In each cell,
CCCHs there are a maximum of three
extended CCCHs, including
dynamically converted CCCHs
and statically configured
CCCHs. These CCCHs are
carried by timeslots 2, 4, and 6 on
the BCCH TRX. When the
CCCH load is low, the channels
on these timeslots can be
occupied by signaling, CS
services, or PS services. When
the CCCH load is high, the
channels on these timeslots are
dynamically converted to
extended CCCHs, which reduces
the CCCH load. The larger the
value of this parameter, the more
the number of TCHs dynamically
converted to CCCHs during peak
hours, the less the number of
available TCHs, the higher the
TCH congestion rate. The
parameter, the less the number of
TCHs dynamically converted to
CCCHs, the lower the paging
efficiency.

GBSS14.0
Parameter Data
Interval for DynCCCHReduceI Period during which dynamic Network

Dynamically nterval conversion from extended planning
Removing CCCHs to TCHs is prohibited
CCCHs after dynamic conversion
between extended CCCHs and
TCHs are performed. Specifying
such period prevents ping-pong
dynamic conversions due to
CCCH load changes. The larger
the value of this parameter, the
less the number of extended
CCCHs dynamically converted
to TCHs during off-peak hours,
the lower the resource usage. The
parameter, the more the number
of extended CCCHs dynamically
converted to TCHs, the more the
number of ping-pong dynamic
conversions due to paging burst,
the lower the paging efficiency.
Procedure
1. Run the BSC6900 MML command SET GCELLCCCH (CME single configuration:
Cell Configuration Express > Idle Mode > Common Control Channel
Parameters in Batches). In this step, set Dynamic Multiple CCCHs to ON(ON),
Dynamic CCCH Addition Threshold, Dynamic CCCH Removal Threshold,
Dynamic CCCH Load Stat. Duration, Maximum Number of Dynamic CCCHs
and Interval for Dynamically Removing CCCHs to appropriate values.
To support the Dynamic Multiple CCCH feature, configure SDCCHs, static PDCHs,
or channels reserved for VIP users that involve in the baseband frequency hopping in
the cell by complying with the following rules:
configured in timeslot 2.
configured in timeslot 2 or 4.
configured in timeslot 2, 4, or 6.
1. Run the BSC6900 MML command SET GCELLCCCH. In this step, set Dynamic
Multiple CCCHs to ON(ON), Dynamic CCCH Addition Threshold to 0, Dynamic
CCCH Removal Threshold to 0, Dynamic CCCH Load Stat. Duration to 0.

GBSS14.0
2. Trace CS messages over the RSL on the Abis interface. Initiate a large number of calls
(including originated calls and terminated calls). Ensure that more than 100 paging
messages are delivered within a second.
3. On the LMT, click Device Maintenance, and then choose BTS3900 series > cell >
Monitor Channel Status in Device Navigation Tree.
Expected result: Timeslot 2 of the BCCH TRX is a BCH.
1. Run the BSC6900 MML command SET GCELLCCCH (CME single configuration:
Cell Configuration Express > Idle Mode > Common Control Channel
Parameters in Batches). In this step, set Dynamic Multiple CCCHs to OFF
(OFF).
----End
Example
//Activating Dynamic Multiple CCCH
SET GCELLCCCH: IDTYPE=BYID, CELLID=2, DynCCCHSwitch=ON, MaxDynCCCHNum=2,
DynCCCHLoadIncrThr=90,
DynCCCHLoadRedcThr=65, DynCCCHLoadDuration=10, DynCCCHReduceInterval=30;
//Deactivating Dynamic Multiple CCCH
SET GCELLCCCH: IDTYPE=BYID, CELLID=2, DynCCCHSwitch=OFF;

GBSS14.0
Feature Activation Guide 115 Configuring RACH Storm Filtration
115 Configuring RACH Storm Filtration
RACH Storm Filtration.
Prerequisites
– N/A
– N/A
l License
Context
Table 115-1 Data preparation
Parameter ID Parameter Remarks Data Source

Name
RACHFLTSW RACH Storm This parameter specify whether to Network

ITCH Filter enable the RACH Storm Filtration planning
feature.
RACHFLTTA RACH Storm This parameter specify the filter Network

THD Filter Access threshold for the TA difference planning
TA Threshold between two consecutive random
access request messages with the same
random access reference value, which
is considered as a TA filter condition.
If the actual TA difference is less than
or equal to this threshold, the TA filter
condition is met.
The recommended value is 4.

GBSS14.0
Parameter ID Parameter Remarks Data Source

Name
RACHFLTFR RACH Storm This parameter specify the filter Network

EQ Filter Access threshold for the number of planning
Frequency consecutive random access request
messages with the same random access
reference value, which is considered as
a frequency filter condition. If the
number of random access request
reference value is greater than this
threshold, the frequency filter
condition is met.
It is recommended that RACH Storm
Filter Access Frequency be set to a
value greater than the value of the MS
MAX Retrans parameter. The
recommended value is 4.
RACHFLTTY RACH Storm This parameter specifies whether to Network

PE Filter Access filter out the random access request planning
Type messages whose access type is
emergency call.
RACHFLTTM RACH Storm This parameter specify the filter Network

INTVAL Filter Access threshold for the interval between two planning
Interval consecutive random access request
reference value, which is considered as
a time filter condition. If the actual
interval is less than or equal to this
threshold, the time filter condition is
met.
The recommended value is 1 and the
unit is 100 ms.
Procedure
1. Run the BSC6900 MML command SET GCELLREV (CME single configuration:
Cell Configuration Express > Other Attributes > Reserved Parameters of Cell;
CME batch modification center: not supported). In this step, set RACH Storm
Filter to YES(Yes) set RACH Storm Filter Access TA Threshold, RACH Storm
Filter Access Frequency, RACH Storm Filter Access Type, and RACH Storm
Filter Access Interval parameters to appropriate values.
Query the values of the following counters before and after this feature is enabled:
– RA303I-Success Rate of Call Setup (Immediate Assignment)

GBSS14.0
– K3014-Traffic Volume on TCH

Expected result: Compared with the values of the two counters before this feature is
enabled, the value of the RA303I-Success Rate of Call Setup (Immediate Assignment)
counter increases slightly and the value of the K3014-Traffic Volume on TCH counter
remains unchanged or decreases after this feature is enabled.
NOTE
When the cell traffic volume decreases greatly, set RACH Storm Filter Access Interval a small value.
It is recommended that the actual value should not exceed 5s.
Run the BSC6900 MML command SET GCELLREV (CME single configuration: Cell
Configuration Express > Other Attributes > Reserved Parameters of Cell; CME batch
modification center: not supported). In this step, set RACH Storm Filter to NO(No).
----End
Example
//Activating RACH Storm Filtration
SET GCELLSOFT: RACHFLTSWITCH=YES, RACHFLTTYPE=EMERGENCY_CALL_ALLOWED-1,
RACHFLTTMINTVAL=1, RACHFLTTATHD=4, RACHFLTFREQ=4;
//Deactivating RACH Storm Filtration
SET GCELLSOFT: RACHFLTSWITCH=NO;

GBSS14.0
Feature Activation Guide 116 Configuring Active Power Control
116 Configuring Active Power Control
Active Power Control.
Prerequisites
l License
Context
Active power control enables immediate control of MS or BTS transmit power during the MS
assignment or intra-BSC handover. In such a case, the BSC can control the uplink and downlink
power promptly. With active power control, the system interference is decreased, QoS is ensured,
and power consumption of the MS or BTS is decreased.
Procedure
Cell Parameters in Batches). In this step, set Power Forecast Allowed to YES
(Yes), set Active Power Control Algorithm Optimize to ON(On), and set Active
Power Control Assign Power Offset and Active Power Control HO Power
Offset to appropriate values.

GBSS14.0
Feature Activation Guide 116 Configuring Active Power Control
Batches). In this step, set UL PC Allowed to YES(Yes), and set DL PC Allowed to

YES(Yes).
1. Run the BSC6900 MML command SET GTRXCHANADMSTAT. In this step,
specify TRX ID and Channel No., and then set Administrative State to Lock
(Lock) to block all TCHs on the BCCH TRX of cell 0 except SDCCH.
2. Start tracing the CS messages of a single subscriber in cell 0 by referring to Tracing
CS Domain Messages of a Single Subscriber.
3. Initiate a call.
4. Check the result in Single User CS Trace window.
The TCH occupied by the call is on a non-BCCH TRX, and the Measurement Result
message regarding the call is present before the Channel Activation message is
delivered. In addition, the values of bs power, ms power, phase-ii-bs-power, and
phase-ii-ms-power in the Channel Activation message are not the maximum.
Cell Parameters in Batches). In this step, set Power Forecast Allowed to NO(No)
and set Active Power Control Algorithm Optimize to OFF(Off).
2. Run the BSC6900 MML command LST GCELLPWRBASIC (CME single
for Power Control of Cell) to query the setting of Power Forecast Allowed.
Expected result: Power Forecast Allowed is set to No and Active Power Control
Algorithm Optimize is set to Off.
----End
Example
//Activating Active Power Control
SET GCELLPWRBASIC:IDTYPE=BYID, CELLID=0, PWRBCDALLOWD=YES,
PwrBCDOptimizeSwitch=ON, PwrBCDAssOffset =2, PwrBCDHoOffset=2;
SET GCELLBASICPARA: IDTYPE=BYID, CELLID=0, UPPCEN=YES, DNPCEN=YES;
//Deactivating Active Power Control
SET GCELLPWRBASIC:IDTYPE=BYID, CELLID=0, PWRBCDALLOWD=NO,
PwrBCDOptimizeSwitch=OFF;

GBSS14.0 117 Configuring Discontinuous Transmission (DTX)-
Feature Activation Guide Downlink
117 Configuring Discontinuous

Transmission (DTX)-Downlink
Discontinuous Transmission (DTX)-Downlink.
Prerequisites
l License
– Idle channels are available in the test cell.
Context
DTX reduces data to be transmitted during inactive speech periods, thereby reducing system
interference and saving system resources. DTX also reduces BTS power consumption and
frequency interference on the radio interface.
CAUTION
DTX cannot be configured in multi-site cell mode.
Procedure

GBSS14.0 117 Configuring Discontinuous Transmission (DTX)-
Feature Activation Guide Downlink
Batches). In this step, set FR Use Downlink DTX to YES(Yes).
NOTE
If half-rate calls are in progress, set HR Use Downlink DTX to YES(Yes).

Cell Parameters in Batches). In this step, set DL DTX Strategy to
BSC_STRATEGY(BSC Strategy).
1. Use an MS to originate a call. The call is set up successfully.
Messages on the Abis Interface, and then check the message tracing results.
Expected result: A message of the Channel Activation type is traced. In the
information element (IE) channel-mode, the value of dtx-downlink is 1, indicating
that the BSC supports downlink DTX.
Batches). In this step, set FR Use Downlink DTX to NO(No).
----End
Example
//Activating Discontinuous Transmission (DTX)-Downlink
SET GCELLBASICPARA: IDTYPE=BYID, CELLID=1024, FRDLDTX=YES;
SET GCELLSOFT: IDTYPE=BYID, CELLID=1024, DLDTXPOLICY=BSC_STRATEGY;
//Deactivating Discontinuous Transmission (DTX)-Downlink
SET GCELLBASICPARA: IDTYPE=BYID, CELLID=1024, FRDLDTX=NO;

GBSS14.0
Feature Activation Guide 118 Configuring Discontinuous Transmission (DTX)-Uplink
118 Configuring Discontinuous

Discontinuous Transmission (DTX)-Uplink.
Prerequisites
l License
l Others
– Idle channels are available in the test cell.
Context
This feature reduces the data to be transmitted during inactive speech periods, reducing the
system interference and saving system resources. In addition, this feature reduces the workload
of the TX module of the MS, prolonging the call duration and standby time.
Procedure
Batches). In this step, set FR Uplink DTX to Shall_Use(Shall Use).
2. Optional: Run the BSC6900 MML command SET GCELLBASICPARA (CME
single configuration: Cell Configuration Express > Cell Attributes > Basic

GBSS14.0
Feature Activation Guide 118 Configuring Discontinuous Transmission (DTX)-Uplink
Parameters in Batches) if HR services are processed currently. In this step, set HR

Uplink DTX to Shall_Use(Shall Use).
2. Run the BSC6900 MML command SND GCELLSYSMSG to send system messages
to the test cell.
3. Query the results for tracing CS messages over the Abis interface.
Expected result: A message of the SACCH Filling type is traced. system-info-type
is system-information-6 and the value of dtx2 is 01. System messages are sent
correctly.
NOTE
If HR Uplink DTX is set to Shall_Use(Shall Use), the value of dtx1 is 1.
4. Use an MS to initiate a call. The call is successfully initiated.
5. Query the results for tracing CS messages over the Abis interface.
Expected result: A message of the Channel Activation type is traced. The value of
dtx-uplink is 1. This indicates that the BSC supports the uplink DTX.
Batches). In this step, set FR Uplink DTX to Shall_NOT_Use(Shall not Use).
Batches) if HR services are processed. In this step, set HR Uplink DTX to
Shall_NOT_Use(Shall not Use).
----End
Example
//Activating full-rate uplink DTX
SET GCELLBASICPARA: IDTYPE=BYID, CELLID=1024, FRULDTX=Shall_Use;
//Verifying full-rate uplink DTX
//Deactivating full-rate uplink DTX
SET GCELLBASICPARA: IDTYPE=BYID, CELLID=1024, FRULDTX=Shall_NOT_Use;
//Activating half-rate uplink DTX

SET GCELLBASICPARA: IDTYPE=BYID, CELLID=1024, HRULDTX=Shall_Use;
//Verifying half-rate uplink DTX
//Deactivating half-rate uplink DTX
SET GCELLBASICPARA: IDTYPE=BYID, CELLID=1024, HRULDTX=Shall_NOT_Use;

GBSS14.0
Feature Activation Guide 119 Configuring TRX Power Amplifier Intelligent Shutdown
119 Configuring TRX Power Amplifier

Intelligent Shutdown
TRX Power Amplifier Intelligent Shutdown.
Prerequisites
– The BTS3900B and BTS3900E do not support this feature.
– At least two QTRUs or GRFUs need to be configured to support this feature.
This feature cannot be used with the following features:
– GBFD-113701 Frequency Hopping (baseband hopping) when one frequency hopping
group is involved in baseband hopping.
– GBFD-113701 Frequency Hopping (RF hopping) when inter-module RF hopping is
applied.
– GBFD-510104 Multi-site Cell.
– GBFD-118106 Dynamic Power Sharing.
l License
Context
The TRX Power Amplifier Intelligent Shutdown function can be enabled during a specific
period. After this function is enabled, idle TRXs can be shut down to reduce power consumption
when estimated traffic load is light, and disabled TRXs can be switched on so that they are
available for use when estimated traffic load is heavy.
Generally, channel allocation measures are used together with this function. The channels on
the BCCH TRX are preferentially assigned so that the utilization of the non-BCCH TRX
channels is decreased and the overall power consumption of the BTS is reduced. In addition, the
BTS allocates channels based on the priorities of TRXs. Channels on the TRXs with high

GBSS14.0
priorities are preferentially assigned to MSs. In this way, the BSC centralizes busy channels into
a few TRXs so that as many idle TRXs as possible can be shut down.
When the BCCH TRX participates in baseband FH, the cell TRX cannot be shut down. Thus,
the TRX power amplifier intelligent shutdown cannot be used.
When the BCCH TRX does not participate in baseband FH and all the TRXs (excluding the
BCCH TRX) in the cell are idle, the TRXs can be shut down.
Before configuring Allow Shutdown of TRX Power Amplifier on the TRX, ensure that the TRX
meets the following conditions:
l The TRX is not on the BCCH.
l The PDCH is not available on the TRX.
After confirming that all target TRXs are shutdown, wait for one minute, and then check whether
the power decreases.
Data Preparation
Parameter Data
Name Parameter ID Remarks Source
Allow Dynamic BSCDynSwitchT This parameter specifies whether to Networ

Shutdown of TRX rxPAAllow enable the TRX Intelligent Shutdown k
by BSC feature. This parameter takes effect on plannin
all BTSs under a BSC. g
Time When the StartTimeTAClo- Set this parameter based on the cell Networ
Function Is seTrxPA traffic volume. You are advised to use k
Enabled this feature during off-peak hours. plannin
g
Time When the EndTimeTAClo- Set this parameter based on the cell Networ
Function Is seTrxPA traffic volume. You are advised to use k
Disabled this feature during off-peak hours. plannin
g
Allow Dynamic DYNOpenTrxPo You are advised to set this parameter to Networ
Shutdown of TRX wer YES(Yes) for all cells. k
plannin
g
Allow Dynamic CPS This parameter specifies whether to Networ

Shutdown of TRX allow the BSC to enable or disable the k
TRX power amplifier based on the plannin
traffic volume. g
TRX Power-on ProtectTimeTrx- This parameter is set to prevent the BSC Networ
Protection Time PowerOn from frequently enabling or disabling k
the TRX. After a TRX is powered on, plannin
the BSC is not allowed to disable the g
TRX within the period of time specified
by this parameter.

GBSS14.0
Parameter Data
Reserve Idle RsvIdleChanNu This parameter specifies the number of Networ

Channel Number m reserved idle channels. If this parameter k
is set too small, the TRX will be plannin
frequently enabled or disabled. If this g
parameter is set too large, idle TRXs will
not be disabled in a timely manner.
Procedure
1. Run the BSC6900 MML command SET BSCDSTPA (CME single configuration:
GSM Global Configuration Express > BSC Basic Configuration > Parameters
of Dynamic Shutdown of TRX; CME batch modification center: 3.17 Modifying
GBSC Parameters in Batches). In this step, set Allow Dynamic Shutdown of TRX
by BSC to YES(Yes), and set Time When the Function Is Enabled and Time When
the Function Is Disabled according to the actual condition.
Batches). In this step, set Allow Dynamic Shutdown of TRX to YES(Yes) to enable
the TRX power amplifier intelligent shutdown function for the cell.
in Batches). In this step, set Allow Dynamic Shutdown of TRX to YES(Yes),
therefore allowing the BSC6900 to shut down the power amplifier of a TRX based on
the traffic volume.
4. Optional: Run the BSC6900 MML command ADD BSCDSTPADATE (CME single
Date Range for Prohibiting Dynamic Shutdown of TRX; CME batch modification
center: not supported). In this step, set the period in which the TRX power amplifier
intelligent shutdown function is disabled. In the period of heavy traffic, this function
needs to be disabled.
NOTE
l The BSC6900 MML command LST BSCDSTPADATE (CME single configuration: GSM
Global Configuration Express > BSC Basic Configuration > Date Range for Prohibiting
Dynamic Shutdown of TRX) can be used to query the value of Prohibit DynShutdown TRX
DateRangeldx.
l The BSC6900 MML command RMV BSCDSTPADATE (CME single configuration: GSM
Global Configuration Express > BSC Basic Configuration > Date Range for Prohibiting
Dynamic Shutdown of TRX; CME batch modification center: not supported) can be used to
remove the period in which the TRX power amplifier intelligent shutdown function is disabled.
1. Wait for about five minutes. Then, Run the BSC6900 MML command DSP
GTRXSTAT to query the value of Close TRX Power.

GBSS14.0
Expected result: The value of Close TRX Power is Yes.

GBSC Parameters in Batches). In this step, set Allow Dynamic Shutdown of TRX
by BSC to NO(No).
Batches). In this step, set Allow Dynamic Shutdown of TRX to NO(No).
in Batches). In this step, set Allow Dynamic Shutdown of TRX to NO(No).
----End
Example
//Enabling the TRX Power Amplifier Intelligent Shutdown function for the
BSC
SET BSCDSTPA: BSCDynSwitchTrxPAAllow=YES, StartTimeTACloseTrxPA=19&00,
EndTimeTACloseTrxPA=24&00;
//Enabling the TRX Power Amplifier Intelligent Shutdown function for a
cell
SET GCELLBASICPARA: IDTYPE=BYID, CELLID=1, DYNOpenTrxPower=YES;
//Enabling the TRX Power Amplifier Intelligent Shutdown function for a
TRX
SET GTRXDEV: TRXID=2, CPS=YES;
//Setting the period during which the TRX Power Amplifier Intelligent
Shutdown function is prohibited
ADD BSCDSTPADATE: DateRangeIndex=1, StartMonthDSTPA=JAN,
StartDayDSTPA=10, EndMonthDSTPA=FEB, EndDayDSTPA=10;
//Disabling the TRX Power Amplifier Intelligent Shutdown function for the
BSC
SET BSCDSTPA: BSCDynSwitchTrxPAAllow=NO;
//Disabling the TRX Power Amplifier Intelligent Shutdown function for a
cell
SET GCELLBASICPARA: IDTYPE=BYID, CELLID=1, DYNOpenTrxPower=NO;
//Disabling the TRX Power Amplifier Intelligent Shutdown function for a
TRX
SET GTRXDEV: TRXID=2, CPS=NO;

GBSS14.0 120 Configuring TRX Power Amplifier Intelligent Shutdown
Feature Activation Guide on Timeslot Level
120 Configuring TRX Power Amplifier

Intelligent Shutdown on Timeslot Level
TRX Power Amplifier Intelligent Shutdown on Timeslot Level.
Prerequisites
– DRFU, RRU3004, and DTRU (type B) support this feature.
– BTSs configured with multi-transceivers do not support this feature.
– The BTS3006C, BTS3002E, BTS3012, and BTS3012AE do not support this feature
when they use a non-optimized double-transceiver unit.
l License
Context
TRX Power Amplifier Intelligent Shutdown on Timeslot Level is a function based on which the
PA is controlled on a timeslot basis. In this manner, the static power consumption of the PA is
0 in the timeslots when the TRX is has no data to transmit, and thus the static power consumption
of the PA is reduced.
TRX power consumption is a major part of the BTS power consumption, and PA power
consumption is a major part of TRX power consumption. According to network operation
experiences, TRXs do not transmit signals all the time. This function shuts down the PA of the
TRX when no data is transmitted in idle timeslots, reducing the cost on power greatly.
Data Preparation

Parameter
Name Parameter ID Remarks Data Source
Allow Turning TsTurningOffEna- This parameter does not Network

Off Time Slot ble depend on other parameters. planning
Procedure
l For all BTSs:
– Activation Procedure
GBSC Parameters in Batches). In this step, set Allow Turning Off Time Slot
to YES(Yes).
– Verification Procedure
1. Run the BSC6900 MML command LST BSCDSTPA to check the value of Time
Slot Turning Off PA Enable. The expected result is Yes.
– Deactivation Procedure
GBSC Parameters in Batches). In this step, set Allow Turning Off Time Slot
to NO(No).
l For the specified BTS:
– Activation Procedure
Parameters of BTS; CME batch modification center: not supported). In this step,
set Allow Turning Off Time Slot to YES(Yes).
– Verification Procedure
1. Run the BSC6900 MML command LST BTSOTHPARA to check the value of
Allow Turning Off Time Slot. The expected result is Yes.
– Deactivation Procedure
set Allow Turning Off Time Slot to NO(No).
----End
Example
l For all BTSs:
SET BSCDSTPA: TsTurningOffEnable=YES;

SET BSCDSTPA: TsTurningOffEnable=NO;
l For the specified BTS:
SET BTSOTHPARA: IDTYPE=BYID, BTSID=0, TSSHTDOWNEN=YES;
SET BTSOTHPARA: IDTYPE=BYID, BTSID=0, TSSHTDOWNEN=NO;

GBSS14.0
Feature Activation Guide 121 Configuring Intelligent Combiner Bypass
121 Configuring Intelligent Combiner

Bypass
Intelligent Combiner Bypass.
Prerequisites
– Intelligent Combiner Bypass (ICB) is applicable to only the double-transceiver TRXs
and must be configured as combining output. The TRXs supporting ICB are the DTRU
(type B), RRU3004, and DRFU.
– This feature cannot be used together with the feature GBFD-113701 Frequency Hopping
(baseband hopping), GBFD-113701, Antenna Frequency Hoppingare or GBFD-510104
Multi-site Cell.
l License
– Adjust Voltage in the MML command SET GCELLBASICPARA (CME single
configuration: Cell Configuration Express > Cell Attributes > Basic Parameters of
Batches) is set to YES(Yes).
– For double-transceiver RF units of the BTS3012, Send Mode in the SET
GTRXDEV (CME single configuration: TRX Configuration Express > Site TRX
Dev Property > Site TRX Dev Property; CME batch modification center: 3.22
Modifying GSM TRX Parameters in Batches) command must be set to
WBANDCOMB(Wideband Combination).
– For double-transceiver RF units of the BTS3900, Send Mode in the SET
GTRXDEV (CME single configuration: TRX Configuration Express > Site TRX
Dev Property > Site TRX Dev Property; CME batch modification center: 3.22
Modifying GSM TRX Parameters in Batches) command must be set to DTIC
(Transmit Independency or Combination) and RXU Sending Receiving Mode in
the SET BTSRXUBP (CME single configuration: BTS Device Panel > RXU

GBSS14.0
Feature Activation Guide 121 Configuring Intelligent Combiner Bypass
Topology > Right click RXU Board > RXU Board Porperties > RUX board
Parameters; CME batch modification center: not supported) command must be set to
DOUBLEDOUBLE_ANTENNA(Double Feeder[1TX + 2RX]).
Context
The ICB can be enabled only when all the non-BCCH carriers are idle and there are idle channels
on the BCCH carrier in the cell.
The ICB function cannot be enabled on channels that are configured as static PDCHs. Neither
can the function be enabled on dynamic PDCHs (TCHs) that are converted to PDCHs.
The enabled ICB feature does not save energy in all cases. It is energy-saving only when the
output power of the TRX is 40 W and the static power level is 0, when the output power of the
TRX is 60 W and the static power level is 0, or when the output power of the TRX is 60 W and
the static power level is 1.
Data Preparation
Parameter Parameter
Name ID Remarks Data Source
ICB Allowed ICBALLOW You can set this parameter to YES Network
(YES) only when the SNDMD for an planning
RF module is set to WBANDCOMB
(Wideband Combination).
Procedure
Batches). In this step, change ICB Allowed to YES(YES).
None.
----End
Example
SET GCELLBASICPARA: IDTYPE=BYID, CELLID=1, ICBALLOW=YES;

GBSS14.0
Feature Activation Guide 122 Configuring Active Backup Power Control
122 Configuring Active Backup Power

Control
Active Backup Power Control.
Prerequisites
– The BTS must be configured with the battery and PMU.
– The BTS3900B does not support this feature.
– The BTS3012AE supports this feature since GBSS13.0.
l License
– Huawei power backup device is needed, such as APM30.
Context
When the BTS external power supply fails, storage batteries are started to supply power. The
BTS shuts down some TRXs automatically under the control of a timer to save the backup power.
Meanwhile, the BTS gradually decreases the TRX transmit power with a certain step until the
entire BTS is powered off. When the BTS external power supply recovers, start the TRXs. Then,
the transmit power of all the TRXs recovers.
Considering the cell coverage, cell capacity, and backup power, this feature gradually decreases
cell coverage and hands over MSs at the cell edge to neighboring cells. This does not degrade
network performance.
NOTE
Using this feature decreases the system capacity.
Operators can choose any of the following modes:

GBSS14.0
l Coverage preferred
Shut down some TRXs and then gradually reduce the transmit power of the remaining
TRXs.
l Capacity preferred
Gradually reduce the transmit power of all TRXs and then shut down some of the TRXs.
l Backup power preferred
Shut down some TRXs and at the same time reduce the transmit power of the remaining
TRXs.
Procedure
1. Coverage preferred
Run the BSC6900 MML command SET BTSBAKPWR (CME single configuration:
BTS Configuration Express > BTS Basic Attributes > Parameters of Hierarchical
Backup Power Reduction; CME batch modification center: not supported) to set
parameters related to hierarchical backup power reduction of a BTS. In this step, set
Backup Power Saving Method to BYPWR(Reduce Backup Power) and Backup
Power Saving Policy to BYCOVER(Cover Priority), and set Drop Power Start
Time[T1], Shutdown TRX Start Time[T2], Drop Power Time Interval[T3], Drop
Power Step, and Max Drop Power Threshold to appropriate values.
2. Capacity preferred
Power Saving Policy to BYCAP(Capability Priority), and set Drop Power Start
3. Backup power preferred
Power Saving Policy to BYSAVING(Saving Priority), and set Drop Power Start
1. Before the feature is activated:
a. Shut down the mains power supply of the BTS locally. The BTS reports
ALM-25622 Mains Input Out of Range, and the battery starts to supply power
b. When the BTS reports ALM-21807 OML Fault, the entire BTS is powered off.
c. Measure the difference between the time the BTS reporting ALM-25622 Mains
Input Out of Range and the time the BTS reporting ALM-21807 OML
Fault. That is, measure the lasting duration.

GBSS14.0
2. After the feature is activated, perform the same operations as that are performed before
the feature is activated at the same time of a different day.
3. Compare the lasting duration before and after the feature is activated. If the lasting
duration after feature activation is greater than that before feature activation, this
feature takes effect.
NOTE
The methods of deactivating this feature in GUL modes are the same.
1. Run the BSC6900 MML command SET BTSBAKPWR (CME single configuration:
Backup Power Reduction; CME batch modification center: not supported). In this
step, set Backup Power Saving Method to BYTRX(Turn off TRX).
----End
Example
//Enabling Active Backup Power Control
SET BTSBAKPWR: IDTYPE=BYID, BTSID=1, BAKPWRSAVMETHOD=BYPWR;
//Disabling Active Backup Power Control

SET BTSBAKPWR: IDTYPE=BYID, BTSID=1, BAKPWRSAVMETHOD=BYTRX;

GBSS14.0 123 Configuring Power Optimization Based on Channel
Feature Activation Guide Type
123 Configuring Power Optimization

Based on Channel Type
Power Optimization Based on Channel Type.
Prerequisites
– Currently, only double-transceiver TRXs support this feature.
(baseband hopping), GBFD-113703 Antenna Frequency Hopping, or GBFD-510104
Multi-site Cell.
Context
The power consumption optimization based on channel type has two functions: dynamic voltage
adjustment and dynamic PDCH voltage adjustment. With the dynamic voltage adjustment
function, different working voltages are provided for the TRX power amplifiers according to
the applied modulation scheme. If all channels on a TRX are configured as TCHs and the TRX
works in GMSK mode, the BTS provides the TRX with the working voltage required in GMSK
mode. If a channel on the TRX is configured as dynamic or static PDCH and the TRX works in
8PSK mode; the BTS provides the TRX with the working voltage required in 8PSK mode. The
BTS provides the TRX with appropriate working voltage, reducing the power consumption.
Data Preparation
Parameter
GPRS GPRS Set this parameter based on the Network

current network status. planning

Parameter
EDGE EDGE Set this parameter based on the Network

current network status. planning
PDCH Power PDCHPWRSAV Set this parameter to YES(Yes) Network

Saving Enable EN only for carriers with dynamic planning
PDCHs.
Adjust Voltage BTSadjust The recommended value is YES Network

(Yes). planning
Procedure
and EDGE to YES(Yes).
Cell Parameters in Batches). In this step, set PDCH Power Saving Enable to YES
(Yes).
Batches). In this step, set Adjust Voltage to YES(Yes).
1. Run the BSC6900 MML command LST GCELLSOFT to query the value of PDCH
Power Saving Enable.
Expected result: The value of PDCH Power Saving Enable is Yes.
2. Run the BSC6900 MML command LST GCELLBASICPARA to query the value
of Adjust Voltage.
Expected result: The value of Adjust Voltage is Yes.
Cell Parameters in Batches). In this step, set PDCH Power Saving Enable to NO
(No).
Batches) to set Adjust Voltage to NO(No).
----End

Example
//Enabling GPRS and EDGE
//Enabling the PDCH power optimization function
SET GCELLSOFT: IDTYPE=BYID, CELLID=1, PDCHPWRSAVEN=YES;
//Enabling the dynamic voltage adjustment function
SET GCELLBASICPARA: IDTYPE=BYID, CELLID=1, BTSadjust=YES;
//Disabling the PDCH power optimization function
SET GCELLSOFT: IDTYPE=BYID, CELLID=1, PDCHPWRSAVEN=NO;
//Disabling the dynamic voltage adjustment function
SET GCELLBASICPARA: IDTYPE=BYID, CELLID=1, BTSadjust=NO;

GBSS14.0
Feature Activation Guide 124 Configuring PSU Smart Control
124 Configuring PSU Smart Control
This section describes how to activate, verify, and deactivate the GBFD-111608 PSU Smart
Control feature. (This feature cannot be configured using the CME. )
Prerequisites
– The BTS3006C, BTS3002E, BTS3012 (DTRU/QTRU), BTS3900B, and BTS3900E
do not support this feature.
– The BTS must be configured with storage batteries, without any alarms related to broken
battery loop, unavailable batteries, AC overvoltage or undervoltage, or power module
faults.
– None
l License
l Others
The BTS must be configured with PMUs and PSUs. In addition, the PMU must meet the
requirements described in Table 124-1.
NOTE
You can run the DSP BTSELABEL command on the BSC LMT to obtain the PMU hardware type from
the electric label. Table 124-1 lists the mapping between PMU hardware types and items in the electric
label.
Table 124-1 PSU Smart Control requirements for PMUs
Item in
PMU the
Power Hardware Electric
System Type Label PMU Software Version
ETP PMU 10A 02310G All versions

WL

GBSS14.0
Item in
PMU the
Power Hardware Electric
System Type Label PMU Software Version
PMU 11A 02310LY All versions

P
APM30 PMU 01B 0231727 All versions

5
EPMU01 0231511 GBSS8.1 or later

1
0231306 The power system does not support this

9 feature.
EPS4890 PMU 01B 0231727 All versions

5
EPMU01 0231511 GBSS8.1 or later

1
0231306 The power system does not support this

9 feature.
EPS4815 EPMU03 0231600 The power system does not support this
5 feature.
SC48200 SC48200 5224005 The power system does not support this
6 feature.
APM100 AEMU01 None The power system does not support this
feature.
APM200 AEMU01 None The power system does not support this
feature.
Context
Data Preparation
Parameter Parameter Setting Notes Data Source

Name ID
PSU Turning PSUTURNI Set this parameter to YES(YES) to Network plan

Off Enable NGOFFEN enable the PSU Smart Control feature.
ABLE
Procedure

GBSS14.0
1. Enable the PSU Smart Control feature. Run the BSC6900 MML command SET
BTSOTHPARA on the BSC LMT with PSU Turning Off Enable set to YES
(YES).
On live networks, observing the gains brought by this feature is difficult because traffic
loads change in various ways at long intervals and the power consumption is likely to
fluctuate. Therefore, you are advised to select the site models in several different areas, for
example, heavily-populated areas, urban areas, suburbs, and countryside, to observe the
feature gains in a laboratory. You are advised to monitor the performance on 2 days with
similar traffic volume.
NOTE
Ensure that batteries are fully charged because battery charging affects the power consumption.
1. Do as follows without enabling PSU Smart Control:
a. Use a current measurement instrument and a voltage measurement instrument to
continuously measure the BTS current and voltage, respectively.
– Measure the voltage only once because the voltage is stable.
– Measure the current for a 24-hour period at a fixed interval, such as 5-minute,
because the current fluctuates from time to time.
b. Record the measured values. Use the average current and voltage measured in
an hour as the current and voltage values for the hour, and then calculate the
power consumption in each hour by multiplying the average current and voltage.
2. Enable PSU Smart Control, and repeat the operations in Step 1 to obtain the power
consumption per day.
3. Compare the power consumption before and after PSU Smart Control is activated.
Expected result: The power consumption decreases after the feature is activated.
1. Run the BSC6900 MML command SET BTSOTHPARA with PSU Turning Off
Enable set to NO(NO).
----End
Example
//Activating PSU Smart Control
SET BTSOTHPARA: IDTYPE=BYID, BTSID=1, PSUTURNINGOFFENABLE=YES;
//Deactivating PSU Smart Control

SET BTSOTHPARA: IDTYPE=BYID, BTSID=1, PSUTURNINGOFFENABLE=NO;

GBSS14.0 125 Configuring Enhanced BCCH Power Consumption
Feature Activation Guide Optimization
125 Configuring Enhanced BCCH Power

Consumption Optimization
This section describes how to activate, verify, and deactivate the GBFD-111609 Enhanced
BCCH Power Consumption Optimization feature.
Prerequisites
– None
l License
Context
With this feature, the transmit power of non-BCCH timeslots on the BCCH carrier can be
decreased. This helps decrease the BTS power consumption.
Data Preparation
Parameter
Name Parameter ID Setting Notes Data Source
Power Derating MAINBCCHPW Set this parameter to YES(Yes) Network plan

Enabled RDTEN to enable Enhanced BCCH
Power Consumption
Optimization. When this feature
is enabled, the BTS decreases
the transmit power of timeslots 1
to 7 on the BCCH carrier.
Power Derating MAIN- Set this parameter to a time when Network plan
Start Time BCCHPWRDTS traffic is light.
TIME

Parameter
Power Derating MAINBCCHPW Set this parameter to a time later Network plan
End Time RDTETIME than the time specified by
MAINBCCHPWRDTSTIME.
Power Derating MAIN- Set this parameter to an Network plan

Range BCCHPWRDTR appropriate value to minimize
ANGE the impact on cell selection, cell
reselection, and handovers.
Power Derating MAIN- When this parameter is set to Network plan

Active Channel BCCHPWDTAC YES(Yes), the BTS performs
Enabled TCHEN downlink power control on
occupied timeslots 1 to 7 on the
BCCH carrier.
WARNING
After the transmit power timeslots 1 to 7 on the BCCH carrier is reduced in a cell, the downlink
receive level measured by MSs camping on a neighboring cell is inaccurate. This may affect
handovers to cell. Therefore, use this feature with caution.
Procedure
Parameters in Batches) to enable the BTS to decrease the transmit power of idle
timeslots 1 to 7 on the BCCH carrier. In this step, set the parameters as follows:
– Set Power Derating Enabled to YES(Yes).
– Set Power Derating Start Time and Power Derating End Time to appropriate
values. Ensure that Power Derating End Time is later than Power Derating Start
Time.
– Set Power Derating Range to specify the power decrease range.
2. Optional: Run the BSC6900 MML command SET GCELLOTHEXT (CME single
Parameters in Batches) command with Power Derating Active Channel
Enabled set to YES(Yes) to enable downlink power control on occupied timeslots 1
to 7 on the BCCH carrier. The maximum power control step is determined by Power
Derating Range in Step 1.

NOTE
1. Do as follows without enabling PSU Smart Control:
continuously measure the BTS current and voltage, respectively.
– Measure the voltage only once because the voltage is stable.
– Measure the current for a 24-hour period at a fixed interval, such as 5-minute,
because the current fluctuates from time to time.
2. Enable PSU Smart Control, and repeat the operations in Step 1 to obtain the power
consumption per day.
3. Compare the power consumption before and after PSU Smart Control is activated.
Expected result: The power consumption decreases after the feature is activated.
Parameters in Batches) on the BSC LMT with Power Derating Enabled set to NO
(No).
----End
Example
//Activating Enhanced BCCH Power Consumption Optimization
SET GCELLOTHEXT: IDTYPE=BYID, CELLID=1, MAINBCCHPWRDTEN=YES,
MAINBCCHPWRDTSTIME=01&00, MAINBCCHPWRDTETIME=04&00,
MAINBCCHPWRDTRANGE=10;
//Deactivating Enhanced BCCH Power Consumption Optimization
SET GCELLOTHEXT: IDTYPE=BYID, CELLID=1, MAINBCCHPWRDTEN=NO;

GBSS14.0
Feature Activation Guide 126 Configuring Dynamic Cell Power Off
126 Configuring Dynamic Cell Power Off
This section describes how to activate, verify, and deactivate the GBFD-111610 Dynamic Cell
Power Off feature.
Prerequisites
– This feature is mutually exclusive with GBFD-118106 Dynamic Power Sharing (the
dual-PA power sharing function).
– It is recommended that this feature be used with GBFD-111602 TRX Power Amplifier
Intelligent Shutdown.
If TRX Power Amplifier Intelligent Shutdown is enabled alone in a cell, the BSC can
disable all the TRXs except the BCCH TRX in the cell, and the cell can continue
providing services for subscribers. However, if Dynamic Cell Power Off is enabled
alone in a cell, the BSC disables all the TRXs in the cell when related conditions are
met. In this case, the cell no longer provides services for subscribers. It is recommended
that the Dynamic Cell Power Off feature be used with the TRX Power Amplifier
Intelligent Shutdown feature and the specified time when TRX Power Amplifier
Intelligent Shutdown starts be earlier than the specified time when Dynamic Cell Power
Off starts. This provides the following benefits: When traffic volume in the cell
decreases, TRX Power Amplifier Intelligent Shutdown enables the BSC to disable idle
TRXs in the cell, thereby reducing cell load. When the cell load is reduced to a
predefined threshold, Dynamic Cell Power Off enables the BSC to disable the BCCH
TRX, thereby decreasing the power consumption of the cell.
– It is recommended that the Dynamic Cell Power Off feature be used with the Multi-
band Sharing One BSC feature.
The 900 MHz/1800 MHz dual-band network in Multi-band Sharing One BSC is a
recommended application scenario for Dynamic Cell Power Off.
l License
l Others

GBSS14.0
– The cell in which you wish to use this feature has a co-coverage cell, and the two cells
are served by the same BSC.
Context
When the traffic volume is low on a network enabled with the Multi-band Sharing One BSC
feature, a fully covered network can carry all the traffic on the existing network. In this case, all
network equipment of the other frequency band can be disabled to reduce the network power
consumption.
Data Preparation
Parameter
Enable TURNOFFENA Set this parameter to ENABLE Network plan

Turning Off BLE (Enable) to enable the Dynamic
Cell Cell Power Off feature.
Same SAMECVGCEL This parameter specifies a co- Network plan

Coverage Cell LID coverage cell.
Index
Same SAMECVGCEL Set this parameter based on Network plan

Coverage Cell LLOADTHRD historical traffic statistics.
Load
Threshold
Dyn. Turning TURNONCELL Set this parameter based on Network plan

On Cell Load LOADTHRD historical traffic statistics.
Threshold
Dyn. Turning TURNOFFCEL Setting this parameter to a small Network plan

Off Cell Busy LCHANNUM value decreases the number of
Channel Num. inter-cell handovers, delays cell
power off, and reduces the gains
provided by this feature. You are
advised to use the default value of
this parameter.
Dyn. Turning PROTECTTIME Setting this parameter to a large Network plan

Off Cell value prevents a cell from being
Protection powered off and on frequently,
Time shortens the period when the cell is
powered off, and reduces the gains
this parameter.

GBSS14.0
Parameter
Same SAMECVGCEL Setting this parameter to a large Network plan

Coverage Cell LLOADSTATT value prevents a cell from being
Load Stat. M powered off and on frequently,
Time shortens the period when the cell is
powered off, and reduces the gains
this parameter.
Dyn. Turning TURNOFFCEL Set this parameter based on Network plan

Off Cell Start LSTRTIME historical traffic statistics.
Time Specifically, set this parameter to a
time when traffic volume is lower
than the threshold specified by
TURNONCELLLOADTHRD.
Dyn. Turning TURNOFFCEL Set this parameter based on Network plan

Off Cell Stop LSTPTIME historical traffic statistics.
Time Specifically, set this parameter to a
time when traffic volume is lower
than the threshold specified by
TURNONCELLLOADTHRD.
Procedure
1. Enable the Dynamic Cell Power Off feature. Run the BSC6900 MML command SET
GCELLDYNTURNOFF (CME single configuration: Cell Configuration Express
> Cell Attributes > Parameters for Dynamically Turning off Cell; CME batch
modification center: 3.20 Modifying GSM Cell Parameters in Batches) on the BSC
LMT with Enable Turning Off Cell set to ENABLE(Enable). In this step, specify
the co-coverage cell and set Same Coverage Cell Load Threshold, Dyn. Turning
On Cell Load Threshold, Dyn. Turning Off Cell Busy Channel Num., Dyn.
Turning Off Cell Protection Time, Same Coverage Cell Load Stat. Time, Dyn.
Turning Off Cell Start Time, and Dyn. Turning Off Cell Stop Time.
NOTE
If the co-coverage cell does not support part of the services in the current cell, the co-coverage
cell cannot provide these services after the current cell is powered off.

GBSS14.0
NOTE
Ensure that the following conditions are met: 1. The cell to be verified has a co-coverage cell that
works correctly. 2. There is no call access request in the cell to be verified. 3. The traffic of the co-
coverage cell is lower than the threshold specified by Same Coverage Cell Load Threshold.
Set Same Coverage Cell Load Threshold to a value close to the maximum value 100 in Step 2. In
this way, the BSC can easily determine that the current cell can be powered off. After the verification,
set this parameter to an appropriate value based on network planning.
The time to wait before you run the DSP GCELLSTAT command in Step 3 depends on the value
of the Same Coverage Cell Load Stat. Time parameter. If the value of Same Coverage Cell Load
Stat. Time is n, wait n minutes and then run the DSP GCELLSTAT command. The default value
of Same Coverage Cell Load Stat. Time is 5.
1. Start an Abis Interface CS Trace task to trace messages over the operation and
maintenance link (OML).
2. Run the BSC6900 MML command SET GCELLDYNTURNOFFwith Cell Index
set to the index of the cell to be verified, Enable Turning Off Cell set to ENABLE
(Enable), Same Coverage Cell Index Type (Not required on the CME) set to the
index of the co-coverage cell, and Dyn. Turning Off Cell Start Time and Dyn.
Turning Off Cell Stop Time to appropriate values so that the current time is within
the period specified by the two parameters.
3. Run the BSC6900 MML command DSP GCELLSTAT after 5 minutes to query the
status of the cell.
Expected results: The value of Cell Dynamic Switch is Yes. The value of
"operationalType" in "bsc-bts-set-trx-power" in the Set Trx Pa message is power-off.
4. Run the BSC6900 MML command SET GCELLDYNTURNOFF with Dyn.
Turning Off Cell Start Time and Dyn. Turning Off Cell Stop Time set to
appropriate values so that the current time is not within the period specified by the
two parameters.
5. Run the BSC6900 MML command DSP GCELLSTAT after about 1 minute to query
the status of the cell.
Expected results: The value of Cell Dynamic Switch is No. The value of
"operationalType" in "bsc-bts-set-trx-power" in the Set Trx Pa message is power-on.
1. Run the BSC6900 MML command SET GCELLDYNTURNOFF (CME single
configuration: Cell Configuration Express > Cell Attributes > Parameters for
Dynamically Turning off Cell; CME batch modification center: 3.20 Modifying
GSM Cell Parameters in Batches) on the BSC LMT with Enable Turning Off
Cell set to DISABLE(Disable).
----End
Example
//Activating Dynamic Cell Power Off
SET GCELLDYNTURNOFF: IDTYPE=BYID, CELLID=0, TURNOFFENABLE=ENABLE,
SAMECVGCELLIDTYPE=BYID, SAMECVGCELLID=1, TURNOFFCELLSTRTIME=23&33,
TURNOFFCELLSTPTIME=05&33;
//Deactivating Dynamic Cell Power Off
SET GCELLDYNTURNOFF: IDTYPE=BYID, CELLID=0, TURNOFFENABLE=DISABLE;

GBSS14.0
Feature Activation Guide 127 Configuring TRX Working Voltage Adjustment
127 Configuring TRX Working Voltage

Adjustment
This section describes how to activate, verify, and deactivate the GBFD-111611 TRX Working
Prerequisites
– The BTS3900B and multi-carrier RF module do not support this feature.
– None
l License
Context
Data Preparation
Parameter
Adjust Voltage BTSadjust Set this parameter to YES(Yes) Network plan

to enable the TRX Working
Procedure
1. Enable TRX Working Voltage Adjustment.Run the BSC6900 MML command SET
GCELLBASICPARA (CME single configuration: Cell Configuration Express >
Cell Attributes > Basic Parameters of Cell; CME batch modification center: 3.20

GBSS14.0
Feature Activation Guide 127 Configuring TRX Working Voltage Adjustment
Modifying GSM Cell Parameters in Batches). on the BSC LMT with Adjust
Voltage set to YES(Yes).
NOTE
1. Do as follows without enabling TRX Working Voltage Adjustment:
continuously measure the current and voltage of a multi-carrier RF module,
respectively. Measure the current and voltage for a 24-hour period at a fixed
interval, such as 5-minute.
2. Enable TRX Working Voltage Adjustment, and repeat the operations in Step 1 to
obtain the power consumption per day.
3. Compare the power consumption before and after TRX Working Voltage Adjustment
is activated.
The power consumption decreases after the feature is activated.
1. .Run the BSC6900 MML command SET GCELLBASICPARA (CME single
Batches) on the BSC LMT with Adjust Voltage set to NO(No).
----End
Example
//Activating TRX Working Voltage Adjustment
SET GCELLBASICPARA: IDTYPE=BYID, CELLID=0, BTSadjust=YES;
//Deactivating TRX Working Voltage Adjustment
SET GCELLBASICPARA: IDTYPE=BYID, CELLID=0, BTSadjust=NO;

GBSS14.0 128 Configuring Multi-Carrier Intelligent Voltage
Feature Activation Guide Regulation
128 Configuring Multi-Carrier

Intelligent Voltage Regulation
This section describes how to activate, verify, and deactivate the GBFD-111612 Multi-Carrier
Intelligent Voltage Regulation feature.
Prerequisites
– Only multi-carrier RF modules support this feature.
– This feature is mutually exclusive with the GBFD-510104 Multi-site Cell feature.
– The gain brought by the Multi-Carrier Intelligent Voltage Regulation feature is
insignificant if this feature is enabled on the 2-TX RF module in any of the following
scenarios:
– BCCHs are configured for both channels of the RF module.
– The BCCH is configured for one channel of the RF module, and transmit diversity
is configured for this RF module.
– The RF module works in dual-channel (2TX+2RX) mode, and all carriers are
configured on one channel.
– The RF module works in 1TX mode.
l License
Context
Data Preparation

Parameter
PA Intelligent PaAdjVol Set this parameter to YES(Yes) Network plan

Adjust Voltage to enable Multi-Carrier
Intelligent Voltage Regulation.
Procedure
1. Enable the Multi-Carrier Intelligent Voltage Regulation feature. Run the BSC6900
MML command SET BTSOTHPARA (CME single configuration: BTS
Configuration Express > BTS Basic Attributes > Other Parameters of BTS; CME
batch modification center: not supported) on the BSC LMT with PA Intelligent
Adjust Voltage set to YES(Yes).
NOTE
1. Do as follows without enabling Multi-Carrier Intelligent Voltage Regulation:
continuously measure the current and voltage of a multi-carrier RF module,
respectively. Measure the current and voltage for a 24-hour period at a fixed
interval, such as 5-minute.
2. Enable Multi-Carrier Intelligent Voltage Regulation, and repeat the operations inStep
1 to obtain the power consumption per day.
3. Compare the power consumption before and after TRX Working Voltage Adjustment
is activated.
The power consumption decreases after the feature is activated.
Parameters of BTS; CME batch modification center: not supported) on the BSC LMT
with PA Intelligent Adjust Voltage set to NO(No).
----End
Example
//Activating Multi-Carrier Intelligent Voltage Regulation
SET BTSOTHPARA: IDTYPE=BYID, BTSID=0, PaAdjVol=YES;

//Deactivating Multi-Carrier Intelligent Voltage Regulation

SET BTSOTHPARA: IDTYPE=BYID, BTSID=0, PaAdjVol=NO;

GBSS14.0
Feature Activation Guide 129 Configuring Flex Abis
129 Configuring Flex Abis
Flex Abis. (This feature cannot be configured using the CME. )
Prerequisites
– For a BTS3900B or BTS3X series base station which does not support Flex Abis,
– If a BTS3X series base station is a root node in a chain or tree topology, none of the
base stations in the chain or tree support Flex Abis.
– If a BTS3X series base station is a lower-level base station of BTSs that support Flex
Abis, Flex Abis can be enabled on the upper-level BTSs only when the following
conditions are met:
Flex Abis Mode for the BTS is set to SEMI_ABIS(Semisolid Abis).
Flex Abis Mode for its upper-level BTSs is set to FLEX_ABIS(Flex Abis).
– This feature cannot be used together with the feature GBFD-116701 16Kbit RSL and
OML on A-bis Interface, GBFD-118601 Abis over IP, GBFD-118611 Abis IP over E1/
T1, GBFD-118401 Abis Transmission Optimization, or GBFD-116601 Abis Bypass.
l License
– The configuration on the BTS is complete. For details, see Configuring a BTS.
Context
Flex Abis enables the sharing of the Abis transmission resources among different BTSs, cells,
and services and therefore improves the resource utilization. Especially for multi-cell large
capacity BTSs, cascaded BTSs, and the cells configured with the EDGE function, the dynamic
Abis resource allocation can greatly improve resource utilization.
Before Flex Abis is introduced, there is one-to-one mapping between the Um interface resources
and the Abis interface transmission resources. After Flex Abis is enabled in the BSC, the Abis

GBSS14.0
interface transmission resources work in resource pool mode to improve the utilization of the
transmission resources.
If a ring topology needs to be configured, only BTS ring topology I is supported. When both
Huawei I BTS ring topology and Flex Abis are applied, the following conditions must be met:
l Flex Abis must be configured on all BTSs. In addition, the BTSs support only the
configuration of one E1 for the forward link and one E1 for the reverse link.
l No BTS can be configured with Abis bypass.
l No BTS can be configured with 16 kbit/s LPAD signaling links.
l No BTS can be configured with Abis timeslot self-detection and self-healing functions.
When Flex Abis is enabled, DXX devices are supported. The limitations in using this feature
are as follows:
l DXX cascading network is not supported.
l In ring topology I network, DXX is not supported.
l If faults occur during DXX timeslot switching, no audio will occur.
Before deploying Flex Abis, collect the information specified in Table 129-1.

GBSS14.0

Parameter
Flex Abis Mode FLEXABISMO Configuration principles for Network

DE cascaded BTSs planning
l To enable Flex Abis for a
cascaded BTS on a link, set
Flex Abis Mode to
FLEX_ABIS for its upper-
level BTSs.
l If Flex Abis Mode is set to
SEMI_ABIS for a cascaded
BTS on a link, set Flex Abis
Mode to SEMI_ABIS for all
its lower-level BTSs.
l Use the E1 port of the primary
cabinet group to connect the
primary cabinet group of the
level-1 BTS to a BSC interface
board. Use the internal
connections of the primary
cabinet group to connect the
secondary cabinet group to a
BSC interface board.
Alternatively, use the E1 port
of the secondary cabinet group
to connect the secondary
cabinet group to a BSC
interface board.
l Use only the E1 ports of the
primary cabinet groups to
connect cascaded BTSs. Use
the internal connections of the
primary cabinet group of a
lower-level BTS to connect the
BTS to an upper-level BTS.
Alternatively, use the E1 port
of the secondary cabinet to
connect the BTS to a BSC
interface board. Note that
secondary cabinet groups
belonging to the same BTS
cannot be cascaded.
l One BTS can only have one
upper-level BTS.
Configuration principles for other
BTSs
Users are allowed to run the
BSC6900 MML command SET

GBSS14.0
Parameter
BTSFORBIDTSto disable certain

timeslots except timeslots in fixed
allocation mode, such as signaling
timeslots and monitoring timeslots
on E1 links for a Flex Abis-enabled
BTS. Certain timeslots need to be
disabled in certain transmission
modes, such as satellite mode or
when only some timeslots on an E1
link can be used.
Multiplexing MPMODE If this parameter is set to a large Network

Mode value, the RSLs will become planning
congested. Therefore, set this
parameter to MODE5_1 or
MODE6_1 only when the traffic
on a BTS is light.
Reserved Traffic RSVTCHTSNU This parameter specifies the Network

Timeslots on an M number of 64 kbit/s timeslots for planning
E1/T1 TCH, dynamic PDCH, or
secondary links on an E1/T1.
These timeslots exclude the
timeslots for OML, ESL, RSL, and
static PDCH, fixedly-configured
idle timeslots, monitoring
timeslots, and transparent
timeslots.
Transmission ENPREEMPTT To enable CS services to preempt Network

Resource RANSADMT the Abis transmission resources planning
Preempting occupied by PS services when all
Support Abis transmission resources are
occupied, set this parameter to
ON.
The setting of this parameter is
effective for all BTSs under the
BSC.
Transport Type TRANST Set this parameter to TDM Network

(TDM). planning
Congestion TDMCONGTH Set this parameter to a value Network

remain ratio smaller than that of Congestion planning
clear remain ratio to prevent
ping-pong handovers when
transmission links are congested.

GBSS14.0
Parameter
Congestion clear TDMCONGCL Set this parameter to a value larger Network

remain ratio RTH than that of Congestion remain planning
ratio to prevent ping-pong
handovers when transmission
links are congested.
TRM Load LOADTHSW l If this parameter is set to ON, Network

Threshold switch load control is enabled when planning
transmission links are
congested. In this case, set
TRM load threshold index to
specify the threshold used for
load control.
TRM load TRMLOADTHI The value of this parameter must Network

threshold index NDEX be unique. planning
LDR First LDRFST If this parameter is set to any value Network

other than CLOSE, the value must planning
be different from the values of
LDR Second, LDR Third, and
LDR Fourth.
LDR Second LDRSND If this parameter is set to any value Network

LDR First, LDR Third, and LDR
Fourth.
LDR Third LSRTRD If this parameter is set to any value Network

LDR First, LDR Second, and
LDR Fourth.
LDR Fourth LDRFOUH If this parameter is set to any value Network

LDR First, LDR Second, and
LDR Third.

GBSS14.0
Parameter
LDR-triggered RelFlexAbis- This parameter specifies whether Network

Secondary Link ForLdr the BSC releases secondary links planning
Release on a PDCH when Load
Reshuffling (LDR) is triggered
because transmission resources are
congested under a BTS using Flex
Abis. If this parameter is set to ON
(On), the BSC releases secondary
links when LDR is triggered. If this
parameter is set to OFF(Off), the
BSC does not release the
secondary links currently used but
cannot apply for subsequent
secondary links.
UL Coding UlCsAdjForAbis This parameter specifies whether Network

Scheme Adj. for Rel the BSC adjusts uplink coding planning
Secondary Link schemes in real time after releasing
Release secondary links on a PDCH. If this
parameter is set to ON(On), the
BSC adjusts uplink coding
schemes in real time. If this
parameter is set to OFF(Off), the
BSC does not adjust uplink coding
schemes in real time. Set this
parameter to ON(On) if LDR-
triggered Secondary Link
Release is set to ON(On).
Procedure
CAUTION
This operation will cause the BTS to be out-of-service. Therefore, perform this operation
during off-peak hours.
1. Run the BSC6900 MML command DEA BTS to deactivate the BTS.
2. Run the BSC6900 MML command MOD BTS to enable flex Abis. In this step, set
Flex Abis Mode to FLEX_ABIS(Flex Abis) and set BTS Multiplexing Mode to an
appropriate value.
3. Run the BSC6900 MML command SET BTSFLEXABISPARA. In this step, set
Reserved Traffic Timeslots on an E1/T1 to appropriate values.
4. Optional: Run the BSC6900 MML command SET BSCBASIC. In this step, set
Transmission Resource Preempting Support to ON(On).

GBSS14.0
NOTE
If Transmission Resource Preempting Support is set to ON(On) and all Abis transmission
resources are occupied, new CS services require more Abis transmission resources. In this case,
the CS services can preempt the Abis transmission resources occupied by PS services so that
the requirements for CS services can be preferentially met. The setting of this parameter is
effective for all BTSs under the BSC.
5. Optional: Run the BSC6900 MML command ADD TRMLOADTH. In this step, set
Transport Type to TDM, and set TRM load threshold index, Congestion remain
ratio, and Congestion clear remain ratio to appropriate values.
NOTE
This step is mandatory if the control over transmission resource congestion is required.
6. Optional: Run the BSC6900 MML command SET BSCABISPRIMAP. In this step,
specify the BTS to be configured. Set Carrier Type to TDM, and set TRM Load
Threshold switch and TRM load threshold index to appropriate values.
NOTE
This step is mandatory if the control over transmission resource congestion is required.
TRM load threshold index must be set to the value specified by TRM load threshold
index in ADD TRMLOADTH.
7. Optional: Run the BSC6900 MML command SET LDR. In this step, set LDR
First, LDR Second, LDR Third, and LDR Fourth to appropriate values.
NOTE
The setting of this parameter is effective for all BTSs under the BSC. This step is mandatory
if the control over transmission resource congestion is required.
8. Optional: Run the BSC6900 MML command SET BSCPSSOFTPARA. In this step,
set LDR-triggered Secondary Link Release and UL Coding Scheme Adj. for
Secondary Link Release to appropriate values.
9. Run the BSC6900 MML command ACT BTS to activate the BTS.
1. Run the BSC6900 MML command LST BTSPORTTS. In this step, set BTS In Port
NO. to the number of the port that the base station is connected to, Port Direction to
the same direction as the base station, and TS Type to ALL(ALL).
2. Run the BSC6900 MML command SET BTSFORBIDTS to block flex timeslots. In
this step, set Start Timeslot No., Start Sub Timeslot No., End Timeslot NO., and
End Sub Timeslot NO. according to the timeslot No. and sub-timeslot No. of Flex
timeslots to ensure that only four consecutive 16 kbit/s sub-timeslots are used for Flex
Abis.
NOTE
Block only Flex Abis timeslots. Reserve only one 64 kbit/s sub-timeslot for services because
timeslots are blocked in units of 64 kbit/s sub-timeslots.
3. Run the BSC6900 MML command DEA GCELL. In this step, set Cell Index to the
index of the cell to be blocked. Repeat this step until there is only one cell under the
BTS.
Channel No. to the number of the channel to be blocked, and Administrative State
to Lock(Lock). Repeat this step until the cell under the BTS has only one BCCH, one
SDCCH, and four TCHs.
5. Use four test MSs to call a fixed-line phone in the cell and maintain the call.
6. Run the BSC6900 MML command DSP ABISTS to query the timeslot state. In this
step, specify Subrack No., Slot No., and Port No., and set State to OCCUPIED

GBSS14.0
(OCCUPIED). Check that the Flex Abis timeslot corresponding to the TCH occupied
by the call is the timeslot that is unblocked.
7. End the call and block the occupied TCH by performing the previous Step 4. Then,
unblock the other four TCHs.
8. Use four test MSs to call a fixed-line phone in the cell and maintain the call.
9. Run the BSC6900 MML command DSP ABISTS to check the state of timeslots. In
this step, specify Subrack No., Slot No., and Port No., and set State to OCCUPIED
(OCCUPIED). Check that the call initiated by the MS is carried on a new TCH whose
Flex Abis timeslot is unblocked.
10. Hang up the call.
CAUTION
This operation will cause the BTS to be out-of-service. Therefore, perform this operation
during off-peak hours.
2. Run the BSC6900 MML command MOD BTS. In this step, set Flex Abis Mode to
FIX_16K_ABIS(Fix Abis).
----End
Example
//Activating Flex Abis
MOD BTS: IDTYPE=BYID, BTSID=0, NEWNAME="bts-3900",
FLEXABISMODE=FLEX_ABIS, MPMODE=MODE4_1;
SET BTSFLEXABISPARA: IDTYPE=BYID, BTSID=0, RSVTCHTSNUM=5;
//Deactivating Flex Abis
MOD BTS: IDTYPE=BYID, BTSID=0, NEWNAME="bts-3900",
FLEXABISMODE=FIX_16K_ABIS;

GBSS14.0
Feature Activation Guide 130 Configuring BTS Local Switch
130 Configuring BTS Local Switch
BTS Local Switch.
Prerequisites
– BTS local switching applies only to BTSs using double-transceiver units and 3900 series
base stations in TDM or IP transmission mode.
– In Abis over TDM transmission mode, this feature depends on the feature
GBFD-117301 Flex Abis.
– In Abis over IP transmission mode, this feature depends on the features GBFD-118601
Abis over IP and GBFD-118611 Abis IP over E1/T1.
– This feature cannot be used together with the feature GBFD-118602 A over IP,
GBFD-118622 A IP over E1/T1, GBFD-118401 Abis Transmission Optimization,
GBFD-119301 Voice Fault Diagnosis, GBFD-116601 Abis Bypass, GBFD-115601
Automatic Level Control (ALC), GBFD-115602 Acoustic Echo Cancellation (AEC),
GBFD-115603 Automatic Noise Restraint (ANR), GBFD-115701 TFO, GBFD-115703
Automatic Noise Compensation (ANC), GBFD-115704 Enhancement Packet Loss
Concealment (EPLC), GBFD-115711 EVAD, GBFD-115506 AMR Coding Rate
Threshold Adaptive Adjustment.
l License
– The BSC works in either BM/TC separated mode or BM/TC combined mode, and the
TDM transmission mode is applied over the Ater and A interfaces.
– At sites where BTS312s and BTS3012s combine into groups, BSS local switching is
enabled only when both the BTS software and the TRX software support it.
– If the calling MS and the called MS are registered on two different MSCs, BSS local
switching is not supported regardless of whether the two MSCs are connected to the
same MGW or different MGWs.

GBSS14.0
– In High-Level Data Link Control (HDLC) transmission mode, BSS local switching is
not supported.
– If the IP transmission mode is used over the Abis interface, BTSs enabled with the local
switching function must be configured on the same MPU.
Context
CAUTION
It is recommended that all cells under a BSC be configured to the same speech version and
supported AMR rate set to increase the success rate of BSC local switches.
BTS local switching applies only to BTSs using double-transceiver units and 3900 series base
stations in TDM or IP transmission mode. When a BTS uses the TDM transmission mode, the
BTS must be enabled with Flex Abis.
BTS local switching saves transmission resources on the Abis and Ater interfaces and reduces
the TC processing delay during a call.
If the MSC is not provided by Huawei, the following functions are unavailable in BTS local
switching mode: MSC playing the announcement during a call, DTMF number receiving during
a call, speech service and then fax service, and separate billing of BSS local switching.
Procedure
1. Run the BSC6900 MML command SET BSSLS (CME single configuration: GSM
Global Configuration Express > BSC Basic Configuration > BSS Local Switching
Parameters; CME batch modification center: 3.17 Modifying GBSC Parameters
in Batches). In this step, set BSS Local Switching General Strategy to
BTSPRIORITY(BTS Priority) or BTSONLY(BTS Only) and set Options for BTS
Local Switch and Avoid Number for BTS to appropriate values.
– If Options for BTS Local Switch is set to ABISCONGESTS(Start When Abis
Congests), you need to specify Abis Jam Rate for BTS Local Switch.
– If Options for BTS Local Switch is set to PREFIXNUMBER(Start by Prefix
Number), you need to specify Prefix Number for BTS
Node; CME batch modification center: not supported) to determine whether BSS local
switching is performed by the BSC only or by both the BSC and the MSC.
NOTE
l If the BSC6900 is expected to perform BSS local switching independently based on

network planning, you need to set MSC-Collaborated BSS Local Switching to
l If the MSC is expected to be involved in BSS local switching based on network planning,
you need to set MSC-Collaborated BSS Local Switching to BASIC(Basic Function) or
ENHANCED(Enhanced Function) and then set related parameters on the MSC side.
3. When the BTS uses the TDM transmission mode, Run the BSC6900 MML
command MOD BTS (CME single configuration: Main View > Right click BTS >

GBSS14.0
Modify Multiplexing Mode or Flex Abis Mode; CME batch modification center:
not supported). In this step, set Flex Abis Mode to FLEX_ABIS(Flex Abis).
NOTE
1. Before performing this step, run the MML command DEA BTS (CME single
configuration: Main View > Right click BTS > Deactivate BTS; CME batch modification
center: not supported) to deactivate the BTS if it has been activated.
2. After performing this step, run the MML command ACT BTS (CME single configuration:
Main View > Right click BTS > Activate BTS; CME batch modification center: not
4. Run the BSC6900 MML command SET BTSLSW (CME single configuration: BTS
Configuration Express > Local Switching > BTS Local Switching Parameters;
CME batch modification center: not supported). In this step, set Support BTS Local
Switch to YES(Yes).
1. Ensure that the calling and called MSs are controlled by the same BTS.
2. Run the BSC6900 MML command DSP CALLRES to query call resources used by
an MS.
NOTE
If BTS local switching is enabled successfully, no Ater and Abis information is displayed.
Switch to NO(No).
----End
Example
//Activating BTS Local Switch
SET BSSLS: BssLsGenMode=BTSONLY, BtsLsStartMode=PREFIXNUMBER,
MsisdnPrfxList2StartBtsLs1="139", MsisdnSegList2AvoidBtsLs1="138";
MOD GCNNODE: CNNODEIDX=0, BSSLSMSCCOOP=NONSUPPORT;
MOD BTS: IDTYPE=BYID, BTSID=0, FLEXABISMODE=FLEX_ABIS;
SET BTSLSW: IDTYPE=BYID, BTSID=0, ISSUPPORTBTSLSWITCH=YES;
//Verifying BTS Local Switch
DSP CALLRES: USERIDTYPE=BYMSISDN, MSISDN="13988888888";
//Deactivating BTS Local Switch
SET BTSLSW: IDTYPE=BYID, BTSID=0, ISSUPPORTBTSLSWITCH=NO;

GBSS14.0
Feature Activation Guide 131 Configuring Abis Transmission Optimization

Optimization
Abis Transmission Optimization. (This feature cannot be configured using the CME. )
Prerequisites
– An Abis interface processing board PEUa or POUc is configured.
– In BM/TC separated scenarios, a DPUc board is configured for processing HDLC
frames in the subrack where the PEUa board is located.
– This feature cannot be used together with the feature GBFD-117701 BSC Local Switch,
GBFD-116701 16Kbit RSL and OML on A-bis Interface, or GBFD-117301 Flex Abis.
l License
– The BTS software version supports this function.
Context
Abis transmission optimization allows multiple links to be multiplexed onto a channel composed
of several timeslots, enabling more efficient use of transmission resources.
CAUTION
l HDLC does not support bypass or Flex Abis.

GBSS14.0
Procedure
1. Run the BSC6900 MML command ADD BTS to add a BTS. In this step, set BTS
Index to 1, BTS Type to BTS3012, Service Type to HDLC, Abis ByPass Mode to
FALSE, and Config Ring to NO.
2. Run the BSC6900 MML command ADD BTSCABINET to add a cabinet to a BTS.
In this step, set BTS Name to the BTS name specified in Step 1, Cabinet No. to 0,
and Cabinet Type to the BTS type specified in Step 1.
3. Run the BSC6900 MML command ADD BTSTRXBRD to add a TRX board to the
BTS. In this step, set Board Type to TRU, Subrack No. to 0, and Slot No. to 0.
4. Run the BSC6900 MML command ADD GCELL to add a GSM cell. In this step, set
Cell Index to 1, Cell Name to gcell-1, Freq. Band to GSM900, MCC to 502,
MNC to 85, Cell LAC to H'0185, Cell CI to 2, Cell IUO Type to Normal_cell,
Start Flex MAIO Switch to OFF, and Operator Name to 46000.
5. Run the BSC6900 MML command ADD GCELLFREQ to add a frequency to the
cell. In this step, set Cell Index to the cell index specified in Step 4 and Frequency
1 to 21.
6. Run the BSC6900 MML command ADD GCELLOSPMAP to add the mapping
between the cell and the Originating Signaling Point (OSP). In this step, set Cell
Index to the cell index specified in Step 4 and OSP Code to the Originating Signaling
Point Code (OPC) of the cell.
7. Run the BSC6900 MML command ADD GTRX to add a carrier frequency. In this
step, set Cell Index to the cell index specified in Step 4, TRX ID to 1, and
Frequency to the frequency specified in Step 5.
8. Run the BSC6900 MML command ADD CELLBIND2BTS to bind the cell to the
BTS. In this step, set Cell Index to the cell index specified in Step 4 and BTS
Index to the BTS index specified in Step 1.
9. Run the BSC6900 MML command ADD TRXBIND2PHYBRD to bind the logical
carrier frequency to the physical TRX board. In this step, set TRX ID to the TRX ID
specified in Step 7, TRX Board to TRU, TRX Board Pass No. to 0, Subrack No.
to 1, and Slot No. to 0.
10. Run the BSC6900 MML command SET GTRXCHAN to set channel information
about the TRX. In this step, set TRX ID to the TRX ID specified in Step 7, Channel
No. to 0, Channel Type to MBCCH, and Timeslot Priority to 1.
11. Run the BSC6900 MML command SET GTRXCHAN to set channel information
about the TRX. In this step, set TRX ID to the TRX ID specified in Step 7, Channel
No. to 1, Channel Type to SDCCH8, and Timeslot Priority to 2.
12. Run the BSC6900 MML command SET GTRXDEV to set TRX attributes. In this
step, set TRX ID to the TRX ID specified in Step 7 and Power Level to 7.
13. Run the BSC6900 MML command ADD BTSCONNECT to add a connection
between the BTS and the BSC6900. In this step, set BTS Index to the BTS index
specified in Step 1, BTS In Port No. to 0, Dest Node Type to BSC, Subrack No. to
the number of the subrack where the BSC interface board is located, Slot No. to the
number of the slot where the BSC interface board is located, and Port No to 0.
14. Run the BSC6900 MML command ACT BTS to activate the BTS. In this step, set
BTS Index to the BTS index specified in Step 1.

GBSS14.0
1. Run the BSC6900 MML command DSP BTSSTAT.

Expected result: The value of Cell Initialized is Yes and the value of Channel
Fault is No.
1. Run the BSC6900 MML command DEA BTS. In this step, set BTS Index to the BTS
index specified in Step 1 in the activation procedure.
----End
Example
//Activating Abis Transmission Optimization
ADD BTS: BTSID=1, BTSNAME="BTS-1", BTSTYPE=BTS3012, SEPERATEMODE=SUPPORT,
SERVICEMODE=HDLC, FLEXABISMODE=FIX_16K_ABIS, ABISBYPASSMODE=FALSE,
ISCONFIGEDRING=NO, MPMODE=MODE4_1;
ADD BTSCABINET: IDTYPE=BYNAME ,BTSNAME="BTS-1", CN=0, TYPE=BTS3012;
ADD BTSTRXBRD: IDTYPE=BYNAME ,BTSNAME="BTS-1",BT=TRU ,SRN=1, SN=0;
ADD GCELL: CELLID=1, CELLNAME="gcell-1", TYPE=GSM900, MCC="502",
MNC="85", LAC=H'0185, CI=2, IUOTP=Normal_cell, OPNAME="46000";
ADD GCELLFREQ: IDTYPE=BYID, CELLID=1, FREQ1=21;
ADD GCELLOSPMAP: IDTYPE=BYID, CELLID=1, OPC=H'B85;
ADD GTRX: IDTYPE=BYID, CELLID=1, TRXID=1, FREQ=41;
SET GTRXCHAN: TRXID=1, CHNO=0, CHTYPE=MBCCH, TSPRIORITY=1;
SET GTRXCHAN: TRXID=1, CHNO=1, CHTYPE=SDCCH8, TSPRIORITY=2;
ADD CELLBIND2BTS: IDTYPE=BYID, CELLID=1,BTSID=1;
ADD TRXBIND2PHYBRD: TRXID=1, TRXTP=TRU, TRXPN=0, SRN=1, SN=0;
PN=0;
SET GTRXDEV: TRXID=1, POWL=7;
//Verifying Abis Transmission Optimization
DSP BTSSTAT: IDTYPE=BYID, BTSIDLST=1;
//Deactivating Abis Transmission Optimization
RMV BTS: IDTYPE=BYID, BTSID=1;

GBSS14.0
Feature Activation Guide 132 Configuring Abis Congestion Trigger HR Distribution
132 Configuring Abis Congestion

Trigger HR Distribution
Abis Congestion Trigger HR Distribution. (This feature cannot be configured using the CME. )
Prerequisites
– The feature GBFD-113402 Dynamic Adjustment Between FR and HR has been
configured before this feature is activated.
– In Abis over TDM transmission mode, the feature GBFD-117301 Flex Abis has also
been configured before this feature is activated.
l License
This feature does not have any special requirements for the running environment.
This feature is applicable to the following scenarios:
– The Abis interface uses IP over E1 transmission.
– The Abis interface uses IP over Ethernet transmission.
– The Abis interface uses TDM transmission and the feature GBFD-117301 Flex Abis
has been configured.
Both the MSC and MSs support HR speech versions.

GBSS14.0
Context
Table 132-1 Data Preparation
Parameter Name Parameter Parameter Settings Data Source

ID
LDR First LDRFST If this parameter is set to Network planning

CSPH, this feature will be
activated.
If this parameter is set to
CLOSE, this feature will be
deactivated.
TRM load threshold TRMLOA The value of this parameter Network planning
index DTHINDE must be unique.
X
Transport Type TRANST This parameter must be set to Network planning

the actual type of transmission
used by the Abis interface.
Threshold type THTYPE This parameter can be set to Internal planning

Percentage or Band Width.
Procedure
1. Run the BSC6900 MML command LST LDR. In this step, query the LDR
configuration.
2. Run the BSC6900 MML command SET LDR. In this step, set LDR First to CSPH
and LDR Second, LDR Third, or LDR Fourth to a value except CSPH.
3. Run the BSC6900 MML command ADD TRMLOADTH. In this step, set TRM load
threshold index, Transport Type, and Threshold type to appropriate values
according to threshold types.
4. In IP transmission mode, run the BSC6900 MML command MOD IPPATH. In this
step, set the IP path-related parameters to appropriate values. For example, set TRM
load threshold index to the same value as that set in Step 3.
5. In TDM transmission mode, run the BSC6900 MML command SET
BSCABISPRIMAP. In this step, configure the Abis priority mapping on the BSC
side. For example, set TRM load threshold index to the same value as that set in
Step 3.
This feature can be enabled only when congestion occurs on the Abis interface. Therefore,
this feature cannot be verified when the TRM load threshold is within a normal range.
1. Run the BSC6900 MML command LST LDR. In this step, query the LDR
configuration.

GBSS14.0
2. Run the BSC6900 MML command SET LDR. In this step, change the value of LDR
First, LDR Second, LDR Third, or LDR Fourth from CSPH to CLOSE.
----End
Example
//Activating Abis Congestion Trigger HR Distribution
SET LDR: LDRFST=CSPH;
ADD TRMLOADTH: TRMLOADTHINDEX=10, TRANST=ATM, THTYPE=PERCENTAGE;
MOD IPPATH: ANI=0, PATHID=0, ITFT=ABIS, TRMLOADTHINDEX=10;
SET BSCABISPRIMAP: IDTYPE=BYID, BTSID=0, TRANSTYPE=TDM, LOADTHSW=ON,
TRMLOADTHINDEX=10;
//Deactivating Abis Congestion Trigger HR Distribution
SET LDR: LDRFST=CLOSE;

GBSS14.0
Feature Activation Guide 133 Configuring Flex Ater
133 Configuring Flex Ater
Flex Ater.
Prerequisites
l License
– The TC subrack is located separately from the BSC.
– The Ater interface uses the TDM transmission mode.
Context
With this feature, the Ater resources are classified into 16 kbit/s timeslots and 8 kbit/s timeslots.
The BSC allocates the Ater resources according to the channel type during the call establishment.
If TCHFs are allocated on the Um interface, 16 kbit/s timeslots are used on the Ater interface.
If TCHHs are allocated on the Um interface, 8 kbit/s timeslots are used on the Ater interface.
Therefore, the Ater resources are fully utilized.
This feature effectively reduces the transmission investment on the Ater interface in remote TC
networking.
Procedure

GBSS14.0
Feature Activation Guide 133 Configuring Flex Ater
center: 3.17 Modifying GBSC Parameters in Batches) with Switch of 8K on

Ater set to YES(Yes).
1. Run the BSC6900 MML command DSP ATERTS with BM/TC config flag set to
BM or TC and Ater connection path index to the number of an Ater connection path.
Expected result: The number of occupied 16 kbit/s resources is equal to that of full-
rate calls. In addition, the number of occupied 8 kbit/s resources is equal to that of
half-rate calls. In this case, Flex Ater is enabled.
center: 3.17 Modifying GBSC Parameters in Batches) with Switch of 8K on
Ater set to NO(No).
----End
Example
//Activating Flex Ater
SET OTHSOFTPARA: Ater8KSw=YES;
//Deactivating Flex Ater
SET OTHSOFTPARA: Ater8KSw=NO;

GBSS14.0
Feature Activation Guide 134 Configuring BSC Local Switch
134 Configuring BSC Local Switch
BSC Local Switch.
Prerequisites
– When the Abis interface is in TDM transmission mode, this feature cannot be used
together with the feature GBFD-118401 Abis Transmission Optimization,
GBFD-118601 Abis over IP, GBFD-118611 Abis IP over E1/T1, GBFD-118602 A over
IP, GBFD-119301 Voice Fault Diagnosis, GBFD-115506 AMR Coding Rate Threshold
Adaptive Adjustment and GBFD-118622 A IP over E1/T1.
– When the Abis interface is in IP transmission mode, this feature cannot be used together
with the feature GBFD-118401 Abis Transmission Optimization, GBFD-118602 A
over IP, GBFD-119301 Voice Fault Diagnosis, GBFD-115506 AMR Coding Rate
Threshold Adaptive Adjustment and GBFD-118622 A IP over E1/T1.
l License
– The BSC works in basic module (BM)/transcoder (TC) separate mode and TDM
transmission mode is applied over the Ater interface.
– With BSC Local Switch, neither the base station serving the calling MS nor that serving
the called MS uses Abis Transmission Optimization.
– In sites with a combined BTS cabinet group, BSS local switching can be enabled only
when both the BTS software and the TRX software support it.

GBSS14.0
Context
CAUTION
It is recommended that all cells under a BSC be configured to the same speech version and
supported AMR rate set to increase the success rate of BSC local switches.
With this feature, the BSC performs a voice loopback within the BSC if the calling MS and
called MS are located under the same BSC. Voice signals are no longer transmitted on the Ater
or A interface, therefore releasing transmission resources on the Ater interface and the transcoder
(TC) coding resources.
This feature helps save local or remote transmission resources on the Ater interface.
If the MSC is not provided by Huawei, the following functions are unavailable in the BSC Local
Switch mode: MSC playing the announcement during a call, DTMF number receiving during a
call, speech service first and then fax service, and independent billing of BSS local switching.
The BSS local switching is not supported as follow: The BSC is configured the MSC Pool
function. The calling MS and the called MS are registered on different MGWs, and the MGW
is in IP transmission mode. The BTS is in High-Level Data Link Control (HDLC) transmission
mode.
Procedure
BSCPRIORITY(BSC Priority) or BSCONLY(BSC Only), specify Options for
BSC Local Switch, and set Avoid Number for BSC to appropriate value.
NOTE
l If Options for BSC Local Switch is set to ATERCONGESTS(Start When Ater

Congests), you need to specify Ater Jam Rate for BSC Local Switch.
l If Options for BSC Local Switch is set to PREFIXNUMBER(Start by Prefix
Number), you need to specify Prefix Number for BSC.
Node; CME batch modification center: not supported) to configure whether BSS local
switching is performed by the BSC only or by both the BSC and the MSC.
NOTE
l If only the BSC performs BSS local switching as selected by the network plan, you need
to set MSC-Collaborated BSS Local Switching to NOTSUPPORT(Not Support).
l If both the BSC and the MSC perform BSS local switching as selected by the network plan,
you need to set MSC-Collaborated BSS Local Switching to BASIC(Basic Function) or
ENHANCED(Enhanced Function), and then set related parameters on the MSC side to
support BSS local switching.

GBSS14.0
Switch to YES(Yes).
1. Ensure that the calling and called MSs are controlled by the same BSC.
2. Run the BSC6900 MML command DSP CALLRES to query call resources of an
MS.
Expected result: When this feature is enabled, only the A interface resources of the
TC subrack and Abis interface resources of the BM subrack are displayed, and the
Ater resources and TC resources of the BM and TC subracks are saved.
NEITHERSTART(Neither Start) or BTSONLY(BTS Only).
----End
Example
//Activating BSC Local Switch
SET BSSLS: BssLsGenMode=BSCONLY, BscLsStartMode=PREFIXNUMBER,
MsisdnPrfxList2StartBscLs1="139";
MOD GCNNODE: CNNODEIDX=0, BSSLSMSCCOOP=NONSUPPORT;
SET BTSLSW: IDTYPE=BYID, BTSID=1, ISSUPPORTBTSLSWITCH=YES;
//Deactivating BSC Local Switch
SET BSSLS: BssLsGenMode=NEITHERSTART;

GBSS14.0
Feature Activation Guide 135 Configuring Ater Compression Transmission
135 Configuring Ater Compression

Transmission
Ater Compression Transmission. (This feature cannot be configured using the CME. )
Prerequisites
– The POUc board is in position.
– When the Abis interface uses TDM transmission, the DPUc board is configured.
This feature cannot be used together with GBFD-116901 Flex Ater.
l License
– The BSC initial configuration is complete. The BM/TC subracks are in separated
configuration mode, and the TC subrack is configured remotely.
Context
When the BM/TC subracks are in separated configuration mode and the TC subrack is configured
remotely, the compressed IP transmission mode over the Ater interface can be adopted to
improve the transmission efficiency over the Ater interface and reduce the transmission cost.
The Ater Compression Transmission feature is based on IP over PPP over STM-1 technology,
where the IP packets of speech data are encapsulated using the PPP and then transmitted over
the channelized STM-1.
The compressed IP transmission mode over the Ater interface does not support IP over FE/GE,
but only supports IP over E1 for transmitting the user plane data. The configuration on the
signaling plane is similar to that in Ater over TDM mode.

GBSS14.0
Procedure
1. Run the BSC6900 MML command ADD BRD to add a POUc board to the BM
subrack. Then, repeat the operation to add a POUc board to the TC subrack.
2. Run the BSC6900 MML command SET BSCBASIC with Service mode set to
SEPARATE(Separate) and Ater Interface Transfer Mode to IP(IP).
3. Run the BSC6900 MML command ADD ATERCONPATH to add an Ater
connection path between the MPS and the TCS.
4. Run the BSC6900 MML command ADD ATEROML to add an Ater OML between
the MPS and the main TCS.
5. Run the BSC6900 MML command ADD ATERSL to add an Ater signaling link
between the MPS/EPS and the TCS.
6. Configure the physical layer and data link layer for the POUc board by referring to
Configuring the Physical Layer and Data Link Layer for the POUc Board.
7. Run the BSC6900 MML command ADD ADJNODE with Adjacent Node Type set
to BSC(Ater Interface on BSC) to add an adjacent node.
8. Run the BSC6900 MML command ADD ADJNODE with Adjacent Node Type set
to TC(Ater Interface on TC) to add an adjacent node.
9. Run the BSC6900 MML command ADD IPPATH to add an IP path to the BM
subrack. Then, run the command again to add an IP path to the TC subrack. To add
more IP paths, run this command repeatedly.
1. Run the BSC6900 MML command DSP E1T1 to check the setting of Port State.
2. Verify the links at the physical layer.
– Do as follows when the links at the physical layer are configured as PPP links:
a. Run the BSC6900 MML command DSP PPPLNK to query the settings of
Link state, Local IP address, and Peer IP address.
b. Run the BSC6900 MML command PING IP with Source IP address set to
the same value as Local IP address in the DSP PPPLNK command and
Destination IP address set to the same value as Peer IP address in the DSP
PPPLNK command.
Expected result: The statistics on PING packets can be received, which
indicates that the MLPPP link is functional.
– Do as follows when the links at the physical layer are configured as MLPPP links:
a. Run the BSC6900 MML command DSP MPGRP to query the settings of
Link state, Local IP address, and Peer IP address.
b. Run the BSC6900 MML command DSP MPLNK to query the settings of
Link state and LCP negotiated state.
c. Run the BSC6900 MML command PING IP with Source IP address set to
the same value as Local IP address in the DSP MPGRP command and
Destination IP address set to the same value as Peer IP address in the DSP
MPGRP command.
Expected result: The statistics on PING packets can be received, which
indicates that the MLPPP link is functional.
3. Run the BSC6900 MML command DSP LAPDLNK to check whether the LAPD link
is functional.

GBSS14.0
Expected result: UsageStatus is set to Normal, which indicates that the LAPD link
is functional.
4. Run the BSC6900 MML command DSP ADJNODE to display the state of an adjacent
node, the number of paths to the adjacent node, and available bandwidth.
Expected result: Operation state is Available, and the related bandwidth is greater
than 0. That is, the adjacent node is functional.
5. Run the BSC6900 MML command DSP IPPATH to check whether the IP path is
available.
Expected result: Operation state is Available and the available bandwidth is greater
than 0. That is, the IP path is functional.
6. Make a call. The call is set up successfully. When the call is set up, Run the BSC6900
MML command DSP IPCHN to query the usage of the Ater interface resources.
Expected result: The UDP usage on the BM side and the TC side are the same.
----End
Example
/*Activating the feature Ater Compression Transmission*/
//Adding a POUc board
ADD BRD: SRN=0, BRDCLASS=INT, BRDTYPE=POUc, LGCAPPTYPE=IP, SN=16, RED=NO,
ISTCBRD=NO, MPUSUBRACK=0, MPUSLOT=0;
ADD BRD: SRN=3, BRDCLASS=INT, BRDTYPE=POUc, LGCAPPTYPE=IP, SN=16, RED=NO,
ISTCBRD=YES;
//Setting the transmission mode over the Ater interface
SET BSCBASIC: ServiceMode=SEPARATE, ATERTRANSMODE=IP;
//Adding an Ater connection path
ADD ATERCONPATH: ATERIDX=0, BMSRN=0, BMSN=16, BMPN=0, TCSRN=3, TCSN=16,
TCPN=0;
TCPN=1;
TCPN=2;
TCPN=3;
//Adding an Ater OML
ADD ATEROML: ATEROMLINX=0, ATERPIDX=0,
TSMASK=TS1-1&TS2-1&TS3-1&TS4-1&TS5-1&TS6-1&TS7-1&TS8-1&TS9-1&TS10-1&TS11-
1&TS12-1&TS13-1&TS14-1&TS15-1&TS16-1&TS17-1&TS18-1&TS19-1&TS20-1&TS21-1&T
S22-1&TS23-1&TS24-1&TS25-1&TS26-1&TS27-1&TS28-1&TS29-1&TS30-1&TS31-1;
//Adding an Ater signaling link
ADD ATERCONSL: ATERIDX=2,
TNMODE=TRRS;
//Adding an Ater PPP link to the BM subrack
ADD PPPLNK: SRN=0, SN=16, BRDTYPE=POUc, PPPLNKN=0, DS1=6,
TSBITMAP=TS1-1&TS2-1&TS3-1&TS4-1&TS5-1&TS6-1&TS7-1&TS8-1&TS9-1&TS10-1&TS1

GBSS14.0
BORROWDEVIP=No, LOCALIP="1.1.1.1", MASK="255.255.255.0",

PEERIP="1.1.1.2", IPHC=No_HC, PFC=Disable, ACFC=Disable, PPPMUX=Disable,
AUTHTYPE=NO_V, FLOWCTRLSWITCH=ON, ERRDETECTSW=OFF;
//Adding an Ater PPP link to the TC subrack
TSBITMAP=TS1-1&TS2-1&TS3-1&TS4-1&TS5-1&TS6-1&TS7-1&TS8-1&TS9-1&TS10-1&TS1
BORROWDEVIP=No, LOCALIP="1.1.1.2", MASK="255.255.255.0",
PEERIP="1.1.1.1", IPHC=No_HC, PFC=Disable, ACFC=Disable, PPPMUX=Disable,
AUTHTYPE=NO_V, FLOWCTRLSWITCH=ON, ERRDETECTSW=OFF;
//Adding an Ater adjacent node to the BM subrack
ADD ADJNODE: ANI=0, NAME="adjnode0", NODET=BSC, BSCID=0;
//Adding an Ater adjacent node to the TC subrack
ADD ADJNODE: ANI=1, NAME="adjnode1", NODET=TC;
//Adding an Ater IP path to the BM subrack
ADD IPPATH: ANI=0, PATHID=0, ITFT=ATER, PATHT=QoS, IPADDR="1.1.1.2",
PEERIPADDR="1.1.1.1", TXBW=2000, RXBW=2000, CARRYFLAG=NULL,
PATHCHK=DISABLED;
//Adding an Ater IP path to the TC subrack
PATHCHK=DISABLED;

GBSS14.0
Feature Activation Guide 136 Configuring Local Multiple Signaling Points
136 Configuring Local Multiple

Signaling Points
Local Multiple Signaling Points.
Prerequisites
– Multiple OSPs are configured.
– Multiple DSPs are configured.
– The route, link set, and link data are configured. The Operation State of the link is
Available.
Context
The local multiple signaling point feature enables one physical BSC to serve as multiple logical
BSCs so that each logical BSC can exchange signaling with the MSC. The traffic load is
distributed to each logical BSC. Therefore, the impact on the paging traffic of the BSC is reduced.
CAUTION
The original intra-BSC handover or intra-BSC directed retry may be converted into outgoing
BSC handover or outgoing BSC directed retry after local multiple signaling points are
configured. As a result, the signaling load on the A interface and the call establishment time are
increased.

GBSS14.0
Procedure
modification center: not supported) repeatedly to add the OSPs.
NOTE
l The OSP Code of OSPs must be different from each other. They must also be different from
the DSP code[Whole Number] of DSPs with the same Network ID.
l The SPCBITS of systems with the same Network ID must be the same.
batch modification center: not supported) repeatedly to add the desired DSPs. In this
step, the OSP index and DSP type specified in Step 1 must be set.
NOTE
After the DSP is configured, the connection from a logical BSC to the MSC is configured. Take the
establishment of the connections from two logical BSCs to the same MSC as an example. First, you need
to add two OSPs with different OSP codes. Then, add two DSPs with identical DSP code, which is the
signaling code of the MSC. In this manner, the connections from two logical BSCs to the same MSC are
established.
1. Run the BSC6900 MML command ADD OPC to configure the OSP of the logical
BSC. In this step, set Network ID, SPCBITS, and OSP Code according to network
planning. The OPCs of multiple logical BSCs must be different.
2. Run the BSC6900 MML command ADD N7DPC to configure the logical link
between the OSP and DSP.
NOTE
If multiple logical BSCs need to be connected to the same DPC, the OSP index needs to be set to
the OSP index of the logical BSC set in Step 1. The DSP bear type needs to set according to network
planning. In the case of ATM/TDM transmission, select MTP3(MTP3); in the case of IP
transmission, select M3UA(M3UA); in the case of co-transmission, select MTP3_M3UA(MTP3
and M3UA).
3. Configure the transmission link between OSP and DSP. If the bear type is MTP3, then
the MTP3 link set, MTP3 link, and MTP3 route need to be configured. If the bear type
is M3UA, then the M3UA link set, M3UA link, M3UA route, M3UA local entity, and
M3UA destination entity need to be configured. The following takes the MTP3 bear
type as an example.
4. Run the BSC6900 MML command ADD MTP3LKS to configure the link set between
the OSP and DSP. In this step, set DSP index to that configured in Step 2.
5. Run the BSC6900 MML command ADD MTP3LNK to configure the physical link
between the OSP and DSP. In this step, set the SIGLKSX as specified in Step 4.
6. Run the BSC6900 MML command ADD MTP3RT to configure the route from the
OSP to the DSP. The route from the OSP to the DSP can be set up either in direct
connection or transfer manner.

GBSS14.0
NOTE
In direct connection manner, the DSP index in this command must be the same as the DSP index
corresponding to the link set configured in Step 4. If a signaling transfer point is used, the DSP
index in this command must be different from the DSP index corresponding to the link set configured
in Step 4 and the DSP corresponding to the link set must provide the signaling link transfer
functionality.
7. Run the BSC6900 MML command DSP N7DPC to query the status of the DSP
configured in Step 2.
Expected result: The value of SCCP DSP state is Accessible.
NOTE
You are advised to remove traffic data and then DPCs and OPCs.
1. Run the BSC6900 MML command RMV N7DPC (CME single configuration: GSM
batch modification center: not supported) to remove a DPC.
2. Run the BSC6900 MML command RMV OPC (CME single configuration: GSM
modification center: not supported) to remove an OPC.
----End
Example
//Adding an OPC
ADD OPC: NAME="opc1", SPX=0, NI=NAT, SPCBITS=BIT16, SPDF=WNF, SPC=111;
//Adding a DPC
ADD N7DPC: NAME="dpc1", DPX=1, SPX=0, SPDF=WNF, DPC=222, DPCT=A,
BEARTYPE=MTP3;
//Removing a DPC
RMV N7DPC: DPX=1;
//Removing an OPC
RMV OPC: SPX=0;

GBSS14.0
Feature Activation Guide 137 Configuring PS Dummy Frame Compression
137 Configuring PS Dummy Frame

Compression
PS Dummy Frame Compression.
Prerequisites
GBFD-114101 GPRS or GBFD-114201 EGPRS, and GBFD-118601 Abis over IP or
GBFD-118611 Abis IP over E1/T1.
l License
– None
– This feature can be used only in Abis over IP mode.
– The feature GBFD-117705 PS Dummy Frame Compression has been configured on the
BTSs before this feature is activated.
Context
l Precautions
– Modifying Abis IP Dummy Frame Optimization resets the cells.
l Data Preparation
Parameter
Abis IP Dummy ABISIPDUMMY Enable this feature if the Internal

Frame OPTSUP transmission bandwidth is planning
Optimization insufficient over the Abis
interface.

GBSS14.0
Feature Activation Guide 137 Configuring PS Dummy Frame Compression
Procedure
Parameters in Batches). In this step, set Abis IP Dummy Frame Optimization to
SUPPORT(Support).
Type to PDTCH(PDTCH) to ensure that PDTCHs exist in the cell.
2. Run the BSC6900 MML command RST GCELL with Reset Level set to 3-LEVEL
(Level-3).
3. Run Tracing PS Domain Messages on the Abis Interface on the LMT.
Expected result:
a. The value of the dummy-flag information element in the
PTRAU_ABIS_DL_SHAKEHANDS message is 1 or 0.
NOTE
If PS DTX is set to OFF(Off), the value of dummy-flag is 1.

If PS DTX is set to DTX(ON when no MS is accessed) or ENHANCEDDTX(ON when
no valid data needs to be sent), the value of dummy-flag is 0.
b. The values of ext-flag and dummy-flag in
PTRAU_ABIS_UP_SHAKEHANDS are 1.
c. When no PS services exist,the downlinkPTRAU_ABIS_DL_NB frames is sent
over the PDCH at an interval of 240 ms if downlink dummy frames do not carry
the USF and at an interval of 20 ms if downlink dummy frames carry the USF.
Parameters in Batches). In this step, set Abis IP Dummy Frame Optimization to
----End
Example
//Activating PS Dummy Frame Compression
SET GCELLPSOTHERPARA: IDTYPE=BYID, CELLID=0, ABISIPDUMMYOPTSUP=SUPPORT;
//Deactivating PS Dummy Frame Compression
SET GCELLPSOTHERPARA: IDTYPE=BYID, CELLID=0, ABISIPDUMMYOPTSUP=NOTSUPPORT;

GBSS14.0
Feature Activation Guide 138 Configuring Clock over IP support 1588v2
138 Configuring Clock over IP support

1588v2
Clock over IP support 1588v2.
Prerequisites
– The GTMUa board does not support 1588v2 over MAC clock synchronization.
– The GTMUa board does not support two-step clock synchronization specified in the G.
8265.1 protocol.
– The feature GBFD-118601 Abis over IP has been configured before this feature is
activated.
l License
– The clock server complies with IEEE 1588v2 and G.8265.1 standards.
Context
When the IP over FE/GE transmission mode is used over the Abis interface, the clock server
complying with IEEE 1588v2 and G.8265.1 standards provides high-precision clock
synchronization signals for its connected BTSs.
Procedure
1. Run the BSC6900 MML command SET BTSIPCLKPARA (CME single
configuration: BTS Configuration Express > BTS Transmission Link > BTS IP
Clock Server; CME batch modification center: not supported). In this step, set Clock
Protocol Type to PTP(PTP Protocol), set Clock Topology Mode to
PTPOVERUDP(PTP over UDP Unicast), set Domain consistent with that of the

GBSS14.0
Feature Activation Guide 138 Configuring Clock over IP support 1588v2
clock server, and set Clock Reference Source Redundancy and Profile Type to
appropriate values.
1. Run the BSC6900 MML command DSP BTSIPCLK to query IP Clock Protocol
and Clock Topology Mode of a BTS.
Expected result: IP Clock Protocol is PTP Protocol and Clock Topology Mode is
UDP Unicast.
1. Run the BSC6900 MML command SET BTSCLK (CME single configuration: BTS
Configuration Express > BTS Basic Attributes > Clock Type of BTS; CME batch
modification center: 3.18 Modifying GBTS Parameters in Batches) to set Clock
Type to INT_CLK(Internal Clock).
----End
Example
//Activating Clock over IP support 1588v2
SET BTSIPCLKPARA: IDTYPE=BYID, BTSID=0, CLKPRTTYPE=PTP, DN=4,
CLKTOPOMODE=PTPOVERUDP, SYNMODE=CONSYN, ISCLKREDUCY=UNSUPPORT,
MASTERIPADDR="10.10.10.10", PRFTYPE=G.8265.1;
//Deactivating Clock over IP support 1588v2
SET BTSCLK: IDTYPE=BYID, BTSID=0, ClkType=INT_CLK;

GBSS14.0
Feature Activation Guide 139 Configuring Synchronous Ethernet
139 Configuring Synchronous Ethernet
Synchronous Ethernet.
Prerequisites
– Impact on BSC6900 hardware: IP interface boards need to be used on the Abis interface.
– Impact on BTS hardware: This feature applies to only the 3900 series base stations.
feature depends on the feature GBFD-118601 Abis over IP.
l License
Context
This feature provides a solution for clock synchronization in the all-IP network. The clock of a
synchronous Ethernet can be obtained and recovered from the physical layer of the Ethernet.
The solution provided by this feature is easy to deploy, as it does not require additional BSC or
BTS hardware.
The clock synchronization technology adopted by this feature is based on the physical layer of
the Ethernet. By using this technology, the clock signals can be retrieved from the code flow of
the Ethernet link. With this feature, the data is transmitted at the physical layer by adopting the
highly precise clock. The reception end can retrieve and recover the clock directly from the data
flow. In this way, the accuracy of the clock is ensured. Another benefit of the feature is that it
does not require additional BTS hardware to achieve clock synchronization in the all-IP network.
Procedure

GBSS14.0
Feature Activation Guide 139 Configuring Synchronous Ethernet
modification center: 3.18 Modifying GBTS Parameters in Batches) to set the clock
type of a BTS. In this step, set Clock Type to SYNETH_CLK(SynEth Clock).
1. Run the BSC6900 MML command DSP BTSBRD to query the current clock source
configuration of the system.
Expected results: Selected Clock Source is SynEth Clock.
----End
Example
SET BTSCLK: IDTYPE=BYID, BTSID=0, ClkType=SYNETH_CLK, TRANSTYPE=FE, PN=0;
DSP BTSBRD: INFOTYPE=BASEINFO, IDTYPE=BYID, BTSID=0;

GBSS14.0
Feature Activation Guide 140 Configuring Abis over IP
140 Configuring Abis over IP
Abis over IP.
Prerequisites
l Dependencies on hardware
The BSC configured with the built-in PCU, that means the DPUd or DPUg board is
configured.
The FG2a, FG2c, FG2d, GOUa, GOUc, or GOUd board is in position.
The BTSs that support the Abis over IP transmission mode are as follows:
– Double-transceiver BTSs configured with the DPTU: BTS3012 and BTS3012A
– BTS3900 series
IP fault detection function based on the BFD
– The BTS3900B and BTS3900E do not support the IP fault detection function based on
Bidirectional Forwarding Detection (BFD).
– BTS3900 series (excluding the BTS3900B and BTS3900E) must be configured with
the GTMUb.
– Devices interconnected to the BSC must support the BFD function.
Built-in firewall
– Only BTS3900 series (excluding BTS3900B and BTS3900E) support the built-in
firewall function.
– The UTRPc is required for supporting the built-in firewall function.
l Dependencies on other features
This feature cannot be used with the features GBFD-117801 Ring Topology,
GBFD-117301 Flex Abis, GBFD-116601 Abis Bypass, GBFD-116701 16Kbit RSL and
OML on Abis Interface, MRFD-210206 Tree Topology, MRFD-210205 Chain Topology,
GBFD-113729 Adaptive Transmission Link Blocking and GBFD-119301 Voice Fault
Diagnosis together.
l License

GBSS14.0
l Initial data preparation

The global data is configured. For details, see Configuring the Global Information.
When device IP is used in transmission, the BTS is configured with a static route to the
device IP of the local BSC.
Context
NOTE
When the layer 2 networking is used on the Abis interface, the BSC and BTS automatically performs the
Bidirectional Forwarding Detection (BFD) on links. In this case, the BTS is not allowed to use the device
IP address in communication.
With this feature, the BSC is connected to the BTS through a LAN or WAN, depending on the
location of the BSC and the BTS. This feature provides FE and GE interfaces and supports the
IPv4 protocol.
BFD applies to the following scenarios: When the BSC is connected to a peer device (such as a
BTS, MGW, or SGSN) through a router, BFD detects whether the router is available. When the
BSC is connected to a peer device (such as a BTS, MGW, or SGSN) directly, BFD detects
whether the peer device is available. With BFD, IP route reselection is triggered when the
gateway or the peer entity is faulty, avoiding continuous packet loss or call drop.
Procedure
Panel > Add Board; CME batch modification center: not supported) to add an FG2a,
FG2c, FG2d, GOUa, GOUc, or GOUd board.
2. Configuring BTS attributes by referring to Configuring BTS Attributes.
3. Configure data for base station equipment by referring to Configuring the Equipment
Data.
4. Configure the transmission data for the base station by referring to Configuring the
Transmission Data.
5. Configure the radio data for the base station by referring to Configuring the Radio
Data.
6. Activate the base station configuration by referring to Activating the BTS
Configuration.
7. Optional: Run the BSC6900 MML command STR IPCHK (CME single
configuration: Abis Configuration Express > IP Transport > IP Connectible
Check; CME batch modification center: not supported). In this step, set the parameters
Check type, Check mode, Peer IP address, and Multi hop BFD detect local ip
based on the actual networking.

GBSS14.0
NOTE
l BFD requires support from both the local and peer devices and takes effect only when BFD
is enabled for both the local and peer devices. Otherwise, services will fail.
l If the Ethernet ports work in active/standby mode, set Check mode to
CHECK_ON_PRIMARY_PORT; if the Ethernet port works in independent mode, set
Check mode to CHECK_ON_INDEPENDENT_PORT.
l If Check type is set to SBFD, the single hop BFD is enabled. In this case, set Peer IP
address to an IP address that is on the same network segment as the local IP address.
l If Check type is set to MBFD, the multi-hop BFD is enabled. In this case, set Multi hop
BFD detect local ip to the device IP or port IP if the local board, and set Peer IP
address to an IP address that is on a different network segment from the local IP address.
8. Configure the built-in firewall function.
a. Run the BSC6900 MML command ADD BTSACL (CME single configuration:
BTS Configuration Express > BTS Transmission Security Configuration
and Maintenance > BTS Access Control List; CME batch modification center:
not supported) to add an access control list (ACL).
b. Run the BSC6900 MML command ADD BTSACLRULE (CME single
configuration: BTS Configuration Express > BTS Transmission Security
Configuration and Maintenance > BTS Access Control List Rule; CME batch
modification center: not supported) to add access rules in the ACL.
c. Run the BSC6900 MML command ADD BTSPACKETFILTER (CME single
Configuration and Maintenance > BTS Packet Filter; CME batch
modification center: not supported) to configure the BTS packet filtering
function.
d. Optional: Run the BSC6900 MML command ADD BTSFLOODDEFEND
(CME single configuration: BTS Configuration Express > BTS Transmission
Security Configuration and Maintenance > BTS Flood Attack Defend and
Alarm Parameters; CME batch modification center: not supported) to add the
BTS flooding packet attack resistance and alarm configuration.
e. Optional: Run the BSC6900 MML command SET BTSIPGUARD (CME
single configuration: BTS Configuration Express > BTS Transmission
Security Configuration and Maintenance > BTS IP Security Policy; CME
batch modification center: not supported) to activate ARP spoofing defense and
invalid packet check functions.
1. Verifying data at the physical layer and the data link layer.
a. Run the BSC6900 MML command DSP ETHPORT with subrack number, slot
number, and port number are those of the peer interface board connected to the
BTS. Check Port state and Link Availability Status in the command execution
result.
The expected result: The value of Port state is Activated and Link Availability
Status is Available.
2. Verifying the control plane on the Abis interface
a. Run the BSC6900 MML command DSP ADJNODE to display the state of an
adjacent node, the number of paths to the adjacent node, and available bandwidth
by checking related parameters, for example, Operation state.

GBSS14.0
The expected result: The value of Operation state is Available and the related
bandwidth is greater than 0.
b. Run the BSC6900 MML command DSP LAPDLNK to check whether the LAPD
link is functional.
The expected result: The value of Usage status is Normal.
3. Verifying the user plane on the Abis interface
a. Run the BSC6900 MML command DSP IPPATH to check whether the IP path
is available.
The expected result: The value of Operation state is Available and the available
bandwidth is greater than 0.
4. Optional: Verifying the BFD
a. Run the BSC6900 MML command DSP IPCHK to query the value of Check
state.
The expected result: The value of Check state is UP or DOWN.
5. Verifying the built-in firewall
a. Run the BSC6900 MML command DSP BTSPACKETFILTER to query the
measurement results of BTS packet filtering.
b. Run the BSC6900 MML command DSP BTSFLOODDEFEND to query
information about BTS flood packets.
c. Run the BSC6900 MML command DSP BTSINVALIDPKTINFO to query the
source of BTS invalid packets.
d. Run the BSC6900 MML command DSP BTSARPSPOOFING to query the
BTS black list in an ARP table.
1. Deactivate the built-in firewall function.
a. Run the BSC6900 MML command RMV BTSPACKETFILTER (CME single
Configuration and Maintenance > BTS Packet Filter; CME batch
modification center: not supported) to delete the BTS packet filtering function.
b. Run the BSC6900 MML command RMV BTSFLOODDEFEND (CME single
Configuration and Maintenance > BTS Flood Attack Defend and Alarm
Parameters; CME batch modification center: not supported) to delete the BTS
flooding packet attack resistance and alarm configuration.
c. Run the BSC6900 MML command SET BTSIPGUARD (CME single
Configuration and Maintenance > BTS IP Security Policy; CME batch
modification center: not supported) to deactivate ARP spoofing defense and
invalid packet check functions.
----End
Example
For configurations, see the typical script examples provided in section Configuring Transmission
Data of Chapter Configuring GSM BTS and Cell Data in the BSC6900 GSM Initial
Configuration.

GBSS14.0
//Example of configuring the built-in firewall function
//Adding a BTS ACL
ADD BTSACL: IDTYPE=BYID, BTSID=0, ACLID=3001, ACLDESC="Acl Group is
created";
//Adding rules in a BTS ACL
ADD BTSACLRULE: IDTYPE=BYID, BTSID=0, RULETYPE=ADV, ACLID=3001,
RULEID=10, PT=IP, SIP="1.1.1.1", SWC="0.0.0.0", DIP="2.2.2.2",
DWC="0.0.255.255", MDSCP=YES, DSCP=25, MFRG=YES;
//Configuring the BTS packet filtering function
ADD BTSPACKETFILTER: IDTYPE=BYID, BTSID=0, CN=0, SRN=0, SN=4, PT=ETH,
PN=0, FM=ADV_ACL, ACLID=3001, MB=PERMIT;
//Adding the BTS flooding packet attack resistance and alarm
configuration
ADD BTSFLOODDEFEND: IDTYPE=BYID, BTSID=0, CN=0, SRN=0, SN=4, FLDTYPE=ARP,
DFDSW=ENABLE, DFDTHD=512, ALMSW=ENABLE, ALMTHD=256;
//Activating ARP spoofing defense and invalid packet check functions
SET BTSIPGUARD: IDTYPE=BYID, BTSID=0, ARPSPOOFCHKSW=ENABLE,
ARPSPOOFALMTHD=120, ARPLRNSTRICTSW=ENABLE, INVALIDPKTCHKSW=ENABLE,
INVALIDPKTALMTHD=2000;
Verification procedure
//Querying measurement results of BTS packet filtering
DSP BTSPACKETFILTER: IDTYPE=BYID, BTSID=0, CN=0, SRN=0, SN=4, PT=ETH,
PN=2, CATALOG=PORT, LSTFORMAT=VERTICAL;
//Querying information about BTS flood packets
DSP BTSFLOODDEFEND: IDTYPE=BYID, BTSID=0, CN=0, SRN=0, SN=4, FLDTYPE=ARP,
LSTFORMAT=VERTICAL;
//Querying the source of BTS invalid packets
DSP BTSINVALIDPKTINFO: IDTYPE=BYID, BTSID=0, CN=0, SRN=0, SN=4,
FLDTYPE=FLOOD, LSTFORMAT=VERTICAL;
//Querying the BTS black list in an ARP table
DSP BTSARPSPOOFING: IDTYPE=BYID, BTSID=0, CN=0, SRN=0, SN=4,
LSTFORMAT=VERTICAL;
//Deleting the BTS packet filtering function
RMV BTSPACKETFILTER: IDTYPE=BYID, BTSID=0, CN=0, SRN=0, SN=4, PT=ETH,
PN=0;
//Deleting the BTS flooding packet attack resistance and alarm
configuration
RMV BTSFLOODDEFEND: IDTYPE=BYID, BTSID=0, CN=0, SRN=0, SN=4, FLDTYPE=ARP;
//Deactivating ARP spoofing defense and invalid packet check functions
SET BTSIPGUARD: IDTYPE=BYID, BTSID=0, ARPSPOOFCHKSW=DISABLE,
ARPLRNSTRICTSW=DISABLE, INVALIDPKTCHKSW=DISABLE;

GBSS14.0
Feature Activation Guide 141 Configuring Abis IP over E1/T1
141 Configuring Abis IP over E1/T1
Abis IP over E1/T1.
Prerequisites
– The PEUa/POUc board is in position.
– The BTS supports IP transmission.
This feature cannot be used with the features GBFD-117801 Ring Topology,
GBFD-117301 Flex Abis, GBFD-116701 16Kbit RSL and OML on A-bis Interface and
GBFD-119301 Voice Fault Diagnosis together.
l License
l Initial Data Preparation
Context
NOTE
The BTS3006C and BTS3002E do not support Abis over IP.
A license is required to implement Abis over IP.
When TDM transmission is used over the Abis interface, the IP over E1/T1 scheme can be used
to carry traffic and signaling data.
Procedure
Panel > Add Board; CME batch modification center: not supported) to add a PEUa/
POUc board.

GBSS14.0
2. Configuring BTS attributes by referring to Configuring BTS Attributes.

Data.
4. Configure the transmission data for the base station by referring to Configuring the
Transmission Data.
Data.
6. Activate the base station configuration by referring toActivating the BTS
Configuration.
1. Verify data at the physical layer and the data link layer.
a. Run the BSC6900 MML command DSP E1T1 to check the setting of Port
State.
b. If the PPP link is used, Run the BSC6900 MML command DSP PPPLNK to
query Link State, Local IP Address, and Peer IP Address. If the link state is
normal and the values of Local IP Address and Peer IP Address are consistent
with data configurations, proceed to the following steps. Otherwise, the
transmission link is faulty. Locate and rectify the fault.
c. If the MLPPP link is used, Run the BSC6900 MML command DSP MPGRP to
query Link State, Local IP Address, and Peer IP Address, and Run the
BSC6900 MML command DSP MPLNK to query Link State and LCP
Negotiation State. If the link state is normal, the value of LCP Negotiation
State is Connect available, and the values of Local IP Address and Peer IP
Address are consistent with data configurations, proceed to the following steps.
Otherwise, the transmission link is faulty. Locate and rectify the fault.
d. If the PPP link is used, Run the BSC6900 MML command PING IP with Source
IP address set to the same value as Local IP address in the DSP PPPLNK
command and Destination IP address set to the same value as Peer IP
address in the DSP PPPLNK command. If the statistics on PING packets can
be received, the PPP link is normal.
e. If the MLPPP link is used, Run the BSC6900 MML command PING IP with
Source IP address set to the same value as Local IP address in the DSP
MPGRP command and Destination IP address et to the same value as Peer IP
address in the DSP MPGRP command. If the statistics on PING packets can be
received, the MLPPP link is normal.
2. Verifying the control plane on the Abis interface
a. Run the BSC6900 MML command DSP LAPDLNK to check whether the LAPD
link is normal. If Usage status is set to NORMAL(NORMAL), the LAPD link
is functional.
b. Run the BSC6900 MML command DSP ADJNODE to obtain the state of an
by checking related parameters, for example, Operation state. If Operation
state is Available and the related bandwidth is greater than 0, the adjacent node
is normal.
3. Verifying the user plane on the Abis interface

GBSS14.0
a. Run the BSC6900 MML command DSP IPPATH check whether the IP path is
available. If Operation state is Available and the available bandwidth is greater
than 0, the IP path is functional.
----End
Example
For configurations, see the typical script examples provided in section Configuring the
Transmission Data of Chapter Configuring the BTS in the BSC6900 GSM Initial Configuration.

GBSS14.0
Feature Activation Guide 142 Configuring Abis MUX
142 Configuring Abis MUX
Abis MUX.
Prerequisites
The FG2a/FG2c/FG2d/GOUa/GOUc/GOUd/PEUa/POUc board is configured. The BTS
supports UDP multiplexing.
This feature depends on the feature GBFD-118601 Abis over IP or GBFD-118611 Abis
IP over E1/T1.
l License
Context
Abis MUX is used to save the bandwidth and multiplex the packets. The BSC and the BTS serve
as transmitting end and receiving end of each other. When Abis MUX is applied, the transmitting
end multiplexes the UDP packets that meet the multiplexing requirements. Multiple UDP
packets are multiplexed into one IP/UDP header at the transmitting end and then demultiplexed
at the receiving end to reconstruct the original data in the IP/UDP packets. Thus, the transmission
efficiency is improved and the bandwidth is saved.
Procedure
1. Run the BSC6900 MML command ADD IPMUX (CME single configuration: Abis
Configuration Express > IP Transport > IP MUX Pipe; CME batch modification
center: not supported) with IP MUX Type set to ABISMUX and Adjacent node
ID, IP path ID, and IS QOSPATH set to appropriate values. Exectution of this
command aims to add an IP MUX pipe to enable the multiplexing of IP packets.

GBSS14.0
Feature Activation Guide 142 Configuring Abis MUX
NOTE
The BSC can assign a value to IP MUX Index by default. This parameter can be set to an
appropriate value according to the actual situation.
When IS QOSPATH is set to YES(YES), you can specify the PHB type of the IPMUX to be
enabled by setting PHB.
2. Run the BSC6900 MML command ADD BTSABISMUXFLOW (CME single
configuration: BTS Configuration Express > BTS Transmission Link > BTS
ABIS-MUX Flow; CME batch modification center: not supported) with Service
Type set to an appropriate value if required to add the ABIS-MUX flow on the BTS.
1. Run the BSC6900 MML command DSP IPMUX to display the application of Abix
MUX.
The expected result: IPMUX Status is set to Enable.
1. Run the BSC6900 MML command RMV IPMUX (CME single configuration: Abis
center: not supported) to disable Abis MUX.
2. Run the BSC6900 MML command RMV BTSABISMUXFLOW (CME single
ABIS-MUX Flow; CME batch modification center: not supported) to disable Abis
MUX on the BTS.
----End
Example
//Activating Abis MUX
ADD IPMUX: MUXTYPE=ABISMUX, ANI=0, PATHID=0, ISQOSPATH=NO,IPMUXINDEX=0;
ADD BTSABISMUXFLOW: IDTYPE=BYID, BTSID=0, SRVTYPE=CSVOICE;
//Deactivating Abis MUX
RMV IPMUX: IPMUXINDEX=0;
RMV BTSABISMUXFLOW: IDTYPE=BYID, BTSID=0, SRVTYPE=CSVOICE;

GBSS14.0
Feature Activation Guide 143 Configuring Abis IPHC
143 Configuring Abis IPHC
Abis IPHC.
Prerequisites
– BTS3012 series are configured with the DPTU board.
– BTS3900 series are configured with the GTMUb board.
– The BSC6900 is configured with the POUc board.
– The feature GBFD-118611 Abis IP over E1/T1 has been configured before this feature
is activated.
l License
– If the BTSs communicate with the routers in IP over E1 mode, the IPHC function must
be enabled on the routers.
Context
In IP over E1/T1 mode, typical small packets (for example, speech data) of standard IP packets
over the Abis interface only account for 50% to 60% of the payload, which indicates low
transmission efficiency. This feature can compress IP or UDP headers to increase the payload
and save IP transmission resources.
Procedure
l Activation Procedure for Newly Deployed Sites
1. Run the BSC6900 MML commandADD PPPLNK (CME single configuration: A
Configuration Express > IP Transport > PPP Link; CME batch modification
center: not supported) or ADD MPGRP (CME single configuration: A
Configuration Express > IP Transport > MP Group > MP Group; CME batch
modification center: not supported). In this step, set Subrack No. and Slot No. to the

GBSS14.0
subrack number and slot number of the POUc and set IP Header Compression to
UDP/IP_HC(UDP/IP_HC).
2. Run the BSC6900 MML commandADD BTSPPPLNK (CME single configuration:
BTS Configuration Express > BTS Transmission Link > BTS PPP Link; CME
batch modification center: not supported) or ADD BTSMPGRP (CME single
configuration: BTS Configuration Express > BTS Transmission Link > BTS MP
Group; CME batch modification center: not supported). In this step, set IP Header
Compression to ENABLE(ENABLE).
NOTE
If the BSC works in IP over FE/GE mode:

l Enable IPHC first on the routers, then on the BTSs, but not on the BSC.
l Configure the routers to support only the compression of non-TCP packet headers (that is, UDP
packet headers).
l Activation Procedure for Sites Requiring Adjustment
1. Run the BSC6900 MML commandMOD PPPLNK (CME single configuration: A
center: not supported) or MOD MPGRP (CME single configuration: A
UDP/IP_HC(UDP/IP_HC).
NOTE
If the BSC works in IP over FE/GE mode:

l Enable IPHC first on the routers, then on the BTSs, but not on the BSC.
l Configure the routers to support only the compression of non-TCP packet headers (that is, UDP
packet headers).
2. Run the BSC6900 MML commandMOD BTSPPPLNK (CME single configuration:
batch modification center: not supported) or MOD BTSMPGRP (CME single
Compression to ENABLE(ENABLE).
CAUTION
When you set IP Header Compression in this step, the BTS reinitiates a negotiation
with the BSC or router on establishing a PPP link or an MP group. The negotiation
may cause no audio or interrupt data transmission for less than 3s.
1. Run the BSC6900 MML commandDSP BTSPPPLNK or DSP BTSMPGRP.
Expected result: The value of IPHC Negotiation Result reported by the BTS is
ENABLE.
2. Observe the traffic during a call.
– If a BSC communicates with the BTSs based on PPP/MP, the BSC can monitor
the transmit flow after Realtime Bandwidth is configured. For details about the

GBSS14.0
operations, see Monitoring Transmission Resources in BSC6900 LMT User

Guide.
– If a BSC communicates with the BTSs through routers, the transmit flow must be
calculated on the transmission equipment.
Expected result: Assuming that traffic volume is certain, the transmit flow is less when
IP Header Compression on the BTSs is set to ENABLE(ENABLE) than that when
IP Header Compression is set to DISABLE(DISABLE).
1. Run the BSC6900 MML commandMOD PPPLNK (CME single configuration: A
center: not supported) or MOD MPGRP (CME single configuration: A
No_HC(No_HC).
2. Run the BSC6900 MML commandMOD BTSPPPLNK (CME single configuration:
batch modification center: not supported) or MOD BTSMPGRP (CME single
Compression to DISABLE(DISABLE).
----End
Example
/*Activating Abis IPHC for newly deployed sites*/
//Activating Abis IPHC by configuring a PPP link

ADD PPPLNK: SRN=0, SN=26, BRDTYPE=POUc, PPPLNKN=0, IPHC=UDP/IP_HC;
ADD BTSPPPLNK: IDTYPE=BYID, BTSID=200, PPPLNKN=0, IPHC=ENABLE;
//Activating Abis IPHC by configuring an MP group

ADD MPGRP: SRN=0, SN=26, BRDTYPE=POUc, MPGRPN=0, IPHC=UDP/IP_HC;
ADD BTSMPGRP: IDTYPE=BYID, BTSID=200, MPGRPN=0, IPHC=ENABLE;
/*Activating Abis IPHC for sites requiring adjustment*/
//Activating Abis IPHC by configuring a PPP link

MOD PPPLNK: SRN=0, SN=26, BRDTYPE=POUc, PPPLNKN=0, IPHC=UDP/IP_HC;
MOD BTSPPPLNK: IDTYPE=BYID, BTSID=200, PPPLNKN=0, IPHC=ENABLE;
//Activating Abis IPHC by configuring an MP group

MOD MPGRP: SRN=0, SN=26, BRDTYPE=POUc, MPGRPN=0, IPHC=UDP/IP_HC;
MOD BTSMPGRP: IDTYPE=BYID, BTSID=200, MPGRPN=0, IPHC=ENABLE;
/*Deactivating Abis IPHC*/
//Deactivating Abis IPHC by configuring the PPP link

MOD PPPLNK: SRN=0, SN=26, BRDTYPE=POUc, PPPLNKN=0, IPHC=No_HC;
MOD BTSPPPLNK: IDTYPE=BYID, BTSID=200, PPPLNKN=0, IPHC= DISABLE;

GBSS14.0
//Deactivating Abis IPHC by configuring the MP link

MOD MPGRP: SRN=0, SN=26, BRDTYPE=POUc, MPGRPN=0, IPHC=No_HC;
MOD BTSMPGRP: IDTYPE=BYID, BTSID=200, MPGRPN=0, IPHC= DISABLE;

GBSS14.0
Feature Activation Guide 144 Configuring A over IP
144 Configuring A over IP
A over IP.
Prerequisites
The FG2a, FG2c, FG2d, GOUa, GOUc, or GOUd board is in position.
This feature is mutually exclusive to the feature GBFD-115601 Automatic Level Control
(ALC), GBFD-115602 Acoustic Echo Cancellation (AEC), GBFD-115603 Automatic
Noise Restraint (ANR), GBFD-115703 Automatic Noise Compensation (ANC),
GBFD-115704 Enhancement Packet Loss Concealment (EPLC), GBFD-115701 TFO,
GBFD-117701 BSC Local Switch, GBFD-117702 BTS Local Switch, and GBFD-115711
EVAD.
l License
The FG2a, FG2c, FG2d, GOUa, GOUc, or GOUd board is configured. For details, see
Configuring a Board.
The BSC clock is configured. For details, see Configuring the Clocks.
The MSC/MGW suports the A over IP.
When device IP is used in transmission, the peer end is configured with a static route to the
When IP fault detection based on BFD is configured, the device connected to the BSC
supports BFD.
Context
A over IP supports only the IPv4 protocol.

GBSS14.0
When A over IP is enabled, the functions of the TCS are taken over by the MGW, and the BSC
does not perform transcoding. The A interface uses IP over FE/GE transmission.
BFD applies to the following scenarios:When the BSC is connected to a peer device (such as a
whether the peer device is available.With BFD, IP route reselection is triggered when the
gateway or the peer entity is faulty, thus avoiding continuous packet loss or call drop.
Procedure
2. Configuring the A Interface
a. Configuring the Physical Layer and Data Link Layer for the FG2a/FG2c/FG2d/
GOUa/GOUc/GOUd Board.
b. Configuring the Control Plane of the A Interface (over IP).
c. Configuring the User Plane of the A Interface (over IP).
d. Configuring the Mapping Between Service Types and Transmission Resources
for the Adjacent Node.
configuration: A Configuration Express > IP Transport > IP Connectible
NOTE
a. Run the BSC6900 MML command DSP ETHPORT with subrack number, slot
number, and port number are those of the peer interface board connected to the
BTS.
The expected result: Port state is Activated, and Link Availability Status is
Available. That is, the links carried on the port are normal.
b. Optional: Run the BSC6900 MML command DSP ETHTRK to display the
setting of Status of ETHTRK.

GBSS14.0
The expected result: Status of ETHTRK is UP, which indicates that the link
aggregation group is normal.
c. Optional: Run the BSC6900 MML command DSP ETHTRKLNK to display
the setting of Status of ETHTRKLNK sub-port.
The expected result: Status of ETHTRKLNK sub-port is UP, which indicates
that the sub-port for the link aggregation group is normal.
2. Verify the control plane on the A interface.
a. Run the BSC6900 MML command DSP N7DPC to display the setting of SCCP
DSP state.
The expected result: SCCP DSP state is Accessible, which indicates that the
SCCP DSP is normal.
b. Run the BSC6900 MML command DSP M3LKS to display the settings of
Operation status and Activated status.
The expected result: Operation status is Available, and Activated status is
Activated. That is, the link set is normal.
c. Run the BSC6900 MML command DSP SCTPLNK to check whether
Operation state is Normal.
The expected result: Operation state is Normal, which indicates that the SCTP
link is normal.
3. Verify the user plane on the A interface.
a. Run the BSC6900 MML command DSP ADJNODE to display the Operation
state of an adjacent node, the number of paths to the adjacent node, and available
bandwidth.
The expected result: Operation state is Available, and the related bandwidth is
greater than 0.
b. Run the BSC6900 MML command DSP IPPATH to display the setting of
Operation state.
The expected result: Operation state is Available and the available bandwidth
is greater than 0.
state.
----End
Example
For configurations, see the typical script example provided in section Configuring the A Interface
(over IP) in the BSC6900 GSM Initial Configuration.

GBSS14.0
Feature Activation Guide 145 Configuring A IP over E1/T1
145 Configuring A IP over E1/T1
A IP over E1/T1.
Prerequisites
The PEUa/POUc board is in position.
This feature is mutually exclusive to the feature GBFD-115601 Automatic Level Control
(ALC), GBFD-115602 Acoustic Echo Cancellation (AEC), GBFD-115603 Automatic
Noise Restraint (ANR), GBFD-115703 Automatic Noise Compensation (ANC),
GBFD-115704 Enhancement Packet Loss Concealment (EPLC), and GBFD-115701 TFO.
l License
The PEUa/POUc board is configured. For details, see Configuring a Board.
The BSC clock is configured. For details, see Configuring the Clocks.
Context
When this feature is enabled, the traffic and signaling data can be carried by the PPP based IP
transmission over the A interface. The port of the BSC can be E1, T1, or STM-1.
Procedure

GBSS14.0

Parameters in Batches) with A Interface Tag, Um Interface Tag, and Abis
Interface Tag set to GSM_PHASE_2Plus.
2. In the MPS/EPS, configure the physical layer and data link layer for the PEUa board
by referring to Configuring the Physical Layer and Data Link Layer for the PEUa
Board or configure the physical layer and data link layer for the POUc board by
referring to Configuring the Physical Layer and Data Link Layer for the POUc Board.
3. Configure the control plane of the A interface.
4. Configure the mapping between service types and transmission resources for the
adjacent node.
5. Configure the user plane of the A interface.
State..
The expected result: Port State. is normal.
b. Check the state of the link.
– The link is a PPP link.
a. Run the BSC6900 MML command DSP PPPLNK to query the settings
of Link state, Local IP address, and Peer IP address. If the link
state is normal and the values of Local IP Address and Peer IP
Address are consistent with data configurations, proceed to the
following steps. Otherwise, the transmission link is faulty. Locate and
rectify the fault.
b. Run the BSC6900 MML command PING IP with Source IP address
set to the value of Local IP address obtained in the preceding sub-step,
and Destination IP address set to the value of Peer IP address obtained
in the preceding sub-step.
The expected result: The BSC receives the statistics on PING packets.
– The link is an MLPPP link.
a. Run the BSC6900 MML command DSP MPGRP to query the settings
of Link state, Local IP address, and Peer IP address.
b. Run the BSC6900 MML command DSP MPLNK to query the settings
of Link state and LCP negotiated state.
The expected result: If the link state is normal, the value of LCP
Negotiation State is Connect available, and the values of Local IP
Address and Peer IP Address are consistent with data configurations,
proceed to the following steps. Otherwise, the transmission link is faulty.
Locate and rectify the fault.
c. Run the BSC6900 MML command PING IP with Source IP address
set to the value of Local IP address, and Destination IP address set to
the value of Peer IP address.
The expected result: The BSC receives the statistics on PING packets.
2. Verify the control plane on the A interface.
a. Run the BSC6900 MML command DSP N7DPC to display the setting of SCCP
DSP state.

GBSS14.0
The expected result: SCCP DSP state is Accessible, which indicates that the
SCCP DSP is normal.
b. Run the BSC6900 MML command DSP M3LKS to display the settings of
Operation status and Activated status.
The expected result: Operation status is Available, and Activated status is
Activated. That is, the link set is normal.
c. Run the BSC6900 MML command DSP SCTPLNK to check whether
Operation state is Normal.
The expected result: Operation state is Normal, which indicates that the SCTP
link is normal.
3. Verify the user plane on the A interface.
a. Run the BSC6900 MML command DSP ADJNODE to display the Operation
state of an adjacent node, the number of paths to the adjacent node, and available
bandwidth.
The expected result: Operation state is Available, and the related bandwidth is
greater than 0.
b. Run the BSC6900 MML command DSP IPPATH to display the setting of
Operation state.
The expected result: Operation state is Available, and the available bandwidth
is greater than 0.
----End
Example
For configurations, see the typical script example provided in section Configuring A over IP in
the BSC6900 GSM Initial Configuration.

GBSS14.0
Feature Activation Guide 146 Configuring UDP MUX for A Transmission
146 Configuring UDP MUX for A

Transmission
UDP MUX for A Transmission.
Prerequisites
The FG2a/FG2c/FG2d/GOUa/GOUc/GOUd/PEUa/POUc board is configured. The Core
Network (CN) supports UDP multiplexing.
This feature depends on the feature GBFD-118602 A over IP or GBFD-118622 A IP
over E1/T1.
l License
Enable RTCP has been set to ON(Open) by running the MOD GCNNODE (CME single
configuration: GSM Global Configuration Express > BSC Basic Configuration > GSM
CN Node; CME batch modification center: not supported) command.
Context
When this feature is enabled, multiple Real-time Transport Protocol (RTP) packets are
multiplexed onto one UDP packet. In this way, the proportion of the packet header to the total
packet decreases, and therefore the A interface transmission efficiency is improved.
Procedure
1. Run the BSC6900 MML command ADD IPMUX (CME single configuration: A

GBSS14.0
Feature Activation Guide 146 Configuring UDP MUX for A Transmission
center: not supported) with IP MUX Type to UDPMUX and Adjacent Node ID, IP
path ID, IS QOSPATH, Sender UDP MUX Mode, and Receive UDP MUX
Mode to appropriate values. Repeat this step if this feature is to be enabled on the A
interfaces between the BSC and multiple CN devices.
NOTE
Max subframe length[byte], Maximum Frame Length[byte], and Maximum Delay Time
[ms] must be set as required.
The BSC can assign a value to IP MUX Index by default. This parameter can be set to an
appropriate value according to the actual situation.
When IS QOSPATH is set to YES(Yes), you can specify the PHB type of the UDP MUX to
be enabled by setting PHB.
1. Run the BSC6900 MML command DSP IPMUX to display the application of UDP
MUX for A Transmission.
The expected result: IPMUX Status is set to Enable.
1. Run the BSC6900 MML command RMV IPMUX (CME single configuration: A
center: not supported) to disable IP MUX.
----End
Example
//Activating UDP MUX for A transmission
ADD IPMUX: MUXTYPE=UDPMUX, ANI=0, PATHID=0, ISQOSPATH=NO,
UDPMUXMODSEND=NORTPCOMP, UDPMUXMODRECV=RTPCOMP, IPMUXINDEX=0;
//Deactivating UDP MUX for A transmission

GBSS14.0 147 Configuring TDM/IP Dual Transmission over A
Feature Activation Guide Interface
147 Configuring TDM/IP Dual

Transmission over A Interface
TDM/IP Dual Transmission over A Interface. (This feature cannot be configured using the
CME. )
Prerequisites
– The DPUc or DPUf board is in position.
– The FG2a, FG2c, FG2d, GOUa, GOUc, GOUd, PEUa, or POUc board is in position.
– The MSC or MGW supports this feature. In addition, the configuration of this feature
is complete.
– This feature depends on the feature GBFD-118602 A over IP or GBFD-118622 A IP
over E1/T1.
l License
– The initial configuration of the BSC is complete. A over TDM transmission is used.
Context
This feature enables TDM transmission and IP transmission to be used simultaneously over the
A interface on the BSC side. This feature is applicable to the scenario where GSM is upgraded
from the TDM network to the IP network.
Whether the user plane on the A interface uses TDM transmission or IP transmission is
determined by the MSC in the assignment procedure or in the incoming BSC handover
procedure.

Procedure
1. Run the BSC6900 MML command ADD BRD to add a DPUc or DPUf board.
2. Run the BSC6900 MML command SET TCTYPE. In this step, set Subrack No. and
Slot No. to those of the DPU board which configured in step 1. In addition, set The
type of TC resource to ITC(Packet Conversion).
3. Run the BSC6900 MML command ADD BRD to add an FG2a, FG2c, FG2d, GOUa,
GOUc, GOUd, PEUa, or POUc board.
4. Configure A over IP transmission.
– When IP over FE/GE transmission is used on the A interface, perform operations
by referring to 144 Configuring A over IP.
– When IP over E1/T1 transmission is used on the A interface, perform operations
by referring to 145 Configuring A IP over E1/T1.
5. Run the BSC6900 MML command MOD N7DPC. In this step, set DSP bear type
to MTP3_M3UA(MTP3 and M3UA). In addition, specify Net PRI as required.
6. Run the BSC6900 MML command MOD GCNNODE. In this step, set Bearer for
A Interface User Plane to TDM_IP, and set Report BSS Transmission
Capability to YES(Yes).
1. Run the BSC6900 MML command DSP N7DPC to display the settings of MTP3
DSP state and M3UA DSP state.
The expected result: MTP3 DSP state and M3UA DSP state are both Available.
2. Tracing Messages on the A Interface. Make a call in the cell. The call is successfully
established.
3. Observe the speech codec list Information Element (IE) is correctly carried in the Cm
Service Request message on the A interface.
The expected result, "full-ip" and "pcm-over-tdm" in the speech codec list IE are both
1.
NOTE
When "codec-type" is cs-data, "pcm-over-ip" and "pcm-over-tdm" in the speech codec list IE
are both 1.
4. View the assignment request message.
– The circuit-identity-code IE is carried when the Core Network (CN) instructs the
user plane to use TDM transmission, as shown in Figure 147-1.
Figure 147-1 Assignment request message in TDM transmission
– The aoip-transport-layer-address-mgw and speech codeclist-msc-preferred IEs are

carried when the CN instructs the user plane to use IP transmission, as shown in
Figure 147-2.

Figure 147-2 Assignment request message in IP transmission
5. Check whether the assignment complete message carries the related IEs.
– When the CN instructs the user plane to use TDM transmission, the assignment
complete message does not carry the aoip-transport-layer-address-bss IE.
– When the CN instructs the user plane to use IP transmission, the assignment
complete message carries the aoip-transport-layer-address-bss IE.
1. Change the TDM/IP dual transmission mode over A interface to TDM transmission.
2. Run the BSC6900 MML command MOD GCNNODE. In this step, set Bearer for
A Interface User Plane to TDM, and set Report BSS Transmission Capability to
NO(No).
3. Run the BSC6900 MML command MOD N7DPC. In this step, set DSP bear type
to MTP3.
----End
Example
/*Activating TDM/IP dual transmission over A Interface*
//Configure the DPUc/DPUf
ADD BRD: SRN=0, BRDCLASS=DPU, BRDTYPE=DPUc, SN=10, ISTCBRD=NO, MPUSUBRACK=0,
MPUSLOT=0;
//Configure the TC type of the DPUc/DPUf

SET TCTYPE: SRN=0, SN=10, TCTYPE=ITC;
//Configure the IP interface board when A IP over FE/GE

ADD BRD: SRN=0, BRDCLASS=INT, BRDTYPE=GOUa, SN=26, RED=YES, MPUSUBRACK=0,
MPUSLOT=0;
//Configure the IP interface board when A IP over E1/T1

ADD BRD: SRN=0, BRDCLASS=INT, BRDTYPE=POUc, LGCAPPTYPE=IP, SN=24, RED=YES,
ISTCBRD=NO, MPUSLOT=0;
//Configure the physical layer and data link layer when A IP over FE/GE
ADD ETHREDPORT: SRN=0, SN=26, PN=0;
MASK="255.255.255.0";
//Configure the physical layer and data link layer when A IP over E1/T1

SET E1T1: SRN=0, SN=24, BT=POUc, PS=ALL, WORKMODE=E1, PTTXT=E1_CRC4_MULTI_FRAME,

PTRXT=E1_CRC4_MULTI_FRAME;
SET OPT: SRN=0, SN=24, BT=POUc, PS=ALL, OPTM=SDH;
ADD MPGRP: SRN=0, SN=24, BRDTYPE=POUc, MPGRPN=10, MPTYPE=MCPPP, BORROWDEVIP=YES,
DEVIP="10.171.35.123", MASK="255.255.255.0", PEERIP="10.171.35.100", MHF=LONG,
PPPMUX=Disable, FLOWCTRLSWITCH=ON, AUTHTYPE=NO_V, ERRDETECTSW=OFF,
ANTIERRFLAG=OFF, OPSEPFLAG=OFF;
ADD MPLNK:SRN=0, SN=24, PPPLNKN=0, MPGRPN=10, DS1=191,
TSBITMAP=TS1-1&TS2-1&TS3-1&TS4-1&TS5-1&TS6-1&TS7-1&TS8-1&TS9-1&TS10-1&TS11-1&TS12-
1&TS13-1&TS14-1&TS15-1&TS16-1&TS17-1&TS18-1&TS19-1&TS20-1&TS21-1&TS22-1&TS23-1&TS2
4-1&TS25-1&TS26-1&TS27-1&TS28-1&TS29-1&30-1&TS31-1, BRDTYPE=POUc, RESTARTTMR=3,
FCSTYPE=16bit, KEEPALIVE=2;
//Configure the control plane of the A interface

ADD SCTPLNK:SRN=0, SN=0, SCTPLNKN=10, APP=M3UA, PEERPN=3055,
LOCIP1="10.171.35.123", PEERIP1="10.171.30.100", LOCPN=3055, SWITCHBACKHBNUM=10,
LOGPORTFLAG=NO, MODE=CLIENT, DSCP=48, RTOMIN=150, RTOMAX=3000, RTOINIT=1000,
RTOALPHA=12, RTOBETA=25, HBINTER=1000, MAXASSOCRETR=4, MAXPATHRETR=2, CHKSUMTX=NO,
CHKSUMRX=NO, CHKSUMTYPE=CRC32, MTU=800, CROSSIPFLAG=UNAVAILABLE,
SWITCHBACKFLAG=YES, BUNDLINGFLAG=NO, VLANFLAG1=ENABLE, VLANID1=3900,
VLANFLAG2=DISABLE;
ADD M3LE: LENO=0, SPX=0, ENTITYT=M3UA_IPSP, NAME="TEST";
ADD M3DE: DENO=0, LENO=0, DPX=0, ENTITYT=M3UA_IPSP, NAME="TEST";
ADD M3LKS: SIGLKSX=0, DENO=0, WKMODE=M3UA_IPSP, NAME="TEST";
ADD M3RT: DENO=0, SIGLKSX=0, NAME="TEST";
ADD M3LNK:SIGLKSX=0, SIGLNKID=0, SRN=0, SN=0, SCTPLNKN=10, PRIORITY=0,
LNKREDFLAG=M3UA_MASTER_MOD, NAME="TEST";
//Configure the mapping between service types and transmission resources for the adjacent node
ADD ADJNODE:ANI=0, NAME="MSC_2G", NODET=A;
//Configure the user plane of the A interface

ADD IPPATH: ANI=0, PATHID=0, ITFT=A, PATHT=QoS, IPADDR="10.171.35.123",
VLANFlAG=DISABLE, PATHCHK=DISABLED;
//Change the the beartpye of the N7DPC

MOD GCNNODE: CNNODEIDX=0, ATransMode=TDM_IP, CodecRptFlg=YES;
MOD N7DPC: DPX=0, BEARTYPE=MTP3_M3UA, NETPRI=M3UA_FIRST;
/*Deactivating TDM/IP dual transmission over A Interface*

//Change the the beartpye of the N7DPC
MOD GCNNODE: CNNODEIDX=0, ATransMode=TDM, CodecRptFlg=NO;
MOD N7DPC: DPX=0, BEARTYPE=MTP3;

GBSS14.0
Feature Activation Guide 148 Configuring Gb over IP
148 Configuring Gb over IP
Gb over IP.
Prerequisites
– The FG2a/FG2c/FG2d/GOUc/GOUd board is in position.
– The built-in PCU is used. The DPUd/DPUg board is configured.
feature depends on the feature: GBFD-114101 GPRS.
l License
– The SGSN supports Gb over IP.
– The BSC and its peer device must support BFD.
Context
Gb over IP enables operators to deploy an IP network instead of using frame relay (FR) between
the BSC and the SGSN.
BFD applies to the following scenarios:When the BSC is connected to a peer device (such as a
whether the peer device is available.With BFD, IP route reselection is triggered when the
gateway or the peer entity is faulty, thus avoiding continuous packet loss or call drop.
Procedure

GBSS14.0
Panel > Add Board; CME batch modification center: not supported) to add an FG2a,
FG2c, FG2d, GOUc, or GOUd board.
2. Configure the Physical Layer and Data Link Layer for the FG2a/FG2c/FG2d/GOUc/
GOUd Board.
3. Run the BSC6900 MML command ADD SGSNNODE (CME single configuration:
Gb Configuration Express > SGSN > SGSN Node; CME batch modification center:
not supported) with Operator Name and SGSN Node ID set to appropriate values to
add an SGSN node.
4. Run the BSC6900 MML command ADD NSE (CME single configuration: Gb
Configuration Express > FR Transport > NSE; CME batch modification center:
not supported) with NSE Identifier, Subrack No., Slot No., Subnet Protocol
Type, Operator Name, SGSN Node ID, and Subnetwork Configure Mode set to
appropriate values to add an NSE.
5. Configure the NSVL.
a. Run the BSC6900 MML command ADD NSVLLOCAL (CME single
configuration: Gb Configuration Express > IP Transport > Local NSVL;
CME batch modification center: not supported) with Local NSVL ID, NSE
Identifier, Local IP Address, Local UDP Port No, Subrack No., and Slot
No. set to appropriate values to add an NSVL on the BSC side.
NOTE
When port IP addresses are used for the communication, Local IP Address is set to the
port IP address of the interface board in Step 2. When device IP addresses are used for
the communication, Local IP Address is set to the device IP address of the interface
board in Step 2.
b. Optional: When Subnetwork Configure Mode of the NSE is STATIC
(Static), Run the BSC6900 MML command ADD NSVLREMOTE (CME
single configuration: Gb Configuration Express > IP Transport > Remote
NSVL; CME batch modification center: not supported) with Remote NSVL
ID, NSE Identifier, Remote IP Address, and Remote UDP Port No. set to
appropriate values to add an NSVL on the SGSN side.
6. Run the BSC6900 MML command ADD PTPBVC (CME single configuration: Gb
Configuration Express > IP Transport > PTP BVC; CME batch modification
center: not supported) with PTP BVC Identifier set to an appropriate value, Cell
Name set to the name of the GPRS cell that needs to be bound, and NSE Identifier
set to that of the NSE added in Step 4. Execution of this command aims to add a PTP
BSSGP virtual connection (PTP BVC).
configuration: A Configuration Express > IP Transport > IP Connectible

GBSS14.0
NOTE
1. Run the BSC6900 MML command PING IP with Subrack No., Slot No., Source IP
address, and Destination IP address set to appropriate values.
NOTE
l When Subnetwork Configure Mode of the NSE is DYNAMIC(Dynamic), you need to set
Source IP Address to the same value as Local IP Address in ADD NSVLLOCAL and
Destination IP Address to the same value as Server IP in ADD NSE.
l When Subnetwork Configure Mode of the NSE is STATIC(Static), you need to set Source
IP Address to the same value as Local IP Address in ADD NSVLLOCAL and Destination
IP Address to the same value as Remote IP Address in ADD NSVLREMOTE.
The expected result: The statistics on PING packets can be received, which indicates
that the IP link on the Gb interface is functional.
2. Run the BSC6900 MML command DSP GBIPROUTE with NSE Identifier, Local
NSVL ID, or Remote NSVL ID set to an appropriate value.
The expected result: IP Path State is Normal, which indicates that the IP path at the
service layer on the Gb interface is functional.
3. Run the BSC6900 MML command DSP SIGBVC with NSE Identifier set to an
appropriate value to check whether SIG BVC State is Normal.
The expected result: SIG BVC State is Normal, which indicates that the SIG PVC
on the signaling plane of the Gb interface is normal.
state.
1. This feature need not be deactivated.
----End
Example
For configurations, see the typical script example provided in section Configuring Gb over IP
in the BSC6900 GSM Initial Configuration.

GBSS14.0
Feature Activation Guide 149 Configuring Ethernet OAM
149 Configuring Ethernet OAM
Ethernet OAM.
Prerequisites
– The FG2a/FG2c/FG2d/GOUa/GOUc/GOUd board is configured for the Abis or A
interface, or the FG2a/FG2c/FG2d/GOUc/GOUd board is configured for the Gb
interface.
– The interconnected transmission equipment must comply with IEEE 802.1ag and IEEE
802.3ah standard protocols.
GBFD-118601 Abis over IP, GBFD-118602 A over IP, and GBFD-118603 Gb over IP.
l License
– The BTS3006C, BTS3002E, BTS3900B, and BTS3900E do not support the feature.
– The BBU is configured with a GTMUb board.
Context
As a layer-2 protocol, Ethernet OAM reports the network status at the data link layer. Therefore,
the network is monitored and managed more effectively.
The BSS supports two types of Ethernet OAM: point-to-point Ethernet OAM (IEEE 802.3ah
standard protocol) and end-to-end Ethernet OAM (IEEE 802.1ag standard protocol).
Procedure
– Activating point-to-point Ethernet OAM

GBSS14.0
– BSC
1. Run the BSC6900 MML command ACT EFMAH (CME single configuration:
GSM Global Configuration Express > IP Interface Configuration > EFM
OAM; CME batch modification center: not supported) to activate the EFM
OAM function.
– BTS
1. Run the BSC6900 MML command SET BTSETHPORT (CME single
configuration: BTS Configuration Express > BTS Transmission Link >
Ethernet Port of IP BTS; CME batch modification center: not supported). In
this step, set 3ah Switch to OPEN(Open).
2. Run the BSC6900 MML command ACT BTSETHOAMAH (CME single
configuration: BTS Configuration Express > BTS Ethernet OAM
Maintenance > BTS Ethernet OAM; CME batch modification center: not
supported) to activate the BTS EFM OAM function.
– Activating end-to-end Ethernet OAM
– BSC
NOTE
The values of parameters MD Name, MD Level, MA Name, and VLAN ID must be
consistent on the two ends.
1. Run the BSC6900 MML command ADD CFMMD (CME single
configuration: GSM Global Configuration Express > IP Interface
Configuration > Ethernet OAM MD; CME batch modification center: not
supported) to add a maintenance domain (MD) for the Ethernet OAM. In this
step, set the parameters MD Index, MD Level, and MD Name to appropriate
values.
2. Run the BSC6900 MML command ADD CFMMA (CME single
Configuration > Ethernet OAM MA; CME batch modification center: not
supported) to add an Ethernet OAM maintenance association (MA). In this step,
set MD Index to the value specified in 1, and set VLAN ID, MA Index, and
MA Name to appropriate values.
3. Run the BSC6900 MML command ADD CFMMEP (CME single
Configuration > Ethernet OAM MEP; CME batch modification center: not
supported) to add a maintenance entity group end point (MEP) for Ethernet
OAM at the local end. In this step, set MEP ID to an appropriate value, MEP
Type to LocalMep(LocalMep), Port Type to ETHER, and MA Index to the
value specified in 2.
4. Run the BSC6900 MML command ADD CFMMEP (CME single
supported) to add an MEP for Ethernet OAM at the remote end. In this step,
set MEP ID to an appropriate value, MEP Type to RemoteMep
(RemoteMep), and MA Index to the value specified in 2.
NOTE
MEP ID must be set to the same value at the two ends.
5. Run the BSC6900 MML command ACT CFMCCMTST (CME single
Configuration > Ethernet Port OAM Continuity Check; CME batch

GBSS14.0
modification center: not supported) to activate the connectivity check for the
Ethernet OAM to check the connectivity between the local MEP and the peer
MEP. In this step, set MA Index to the value specified in 2 and MEP ID to the
value specified in 3.
– BTS
NOTE
The values of parameters MD Name, MD Level, MA Name, and VLAN ID must be
consistent on the two ends.
1. Run the BSC6900 MML command ADD BTSETHMD (CME single

Maintenance > BTS Ethernet OAM Maintenance Domain; CME batch
modification center: not supported) to add a MD for BTS Ethernet OAM. In
this step, set the parameters MD Level and MD Name to appropriate values.
2. Run the BSC6900 MML command ADD BTSETHMA (CME single
Maintenance > BTS Ethernet OAM Maintenance Association; CME batch
modification center: not supported) to add a BTS Ethernet OAM MA. In this
step, set MD Name to the value specified in 1, and set VLAN ID and MA
Name to appropriate values.
3. Run the BSC6900 MML command ADD BTSETHLCMEP (CME single
Maintenance > BTS Ethernet OAM Local MEP; CME batch modification
center: not supported) to add an MEP for BTS Ethernet OAM at the local end.
In this step, set MEP ID to an appropriate value, MD Name to the value
specified in 1, and MA Name to the value specified in 2.
4. Run the BSC6900 MML command ADD BTSETHRMMEP (CME single
Maintenance > BTS Ethernet OAM Remote MEP; CME batch modification
center: not supported) to add an MEP for BTS Ethernet OAM at the remote
end. In this step, set MEP ID to an appropriate value, MD Name to the value
specified in 1, and MA Name to the value specified in 2.
NOTE
MEP ID must be set to the same value at the two ends.
5. Run the BSC6900 MML command ACT BTSETHCC (CME single
Maintenance > BTS Ethernet OAM CC Function; CME batch modification
center: not supported) to activate the connectivity check for the Ethernet OAM
to check the connectivity between the local MEP and the peer MEP. In this
step, set MD Name to the value specified in 1, MA Name to the value specified
in 2, and MEP ID to the value specified in 3.
– Verifying point-to-point Ethernet OAM
1. After the EFM OAM function is enabled, the alarm ALM-21371 ETHOAM 3AH
Discovery Failure is reported if the transmission link is faulty or the peer end does
not support the EFM OAM function.
2. Run the BSC6900 MML command STR EFMLOOPTST to start EFM OAM
remote loopback test. After the EFM OAM function is enabled, the alarm
ALM-21374 ETHOAM 3AH Remote Loopback is reported if the loopback is
successful because the loopback operation blocks the ongoing services.

GBSS14.0
– Verifying end-to-end Ethernet OAM

1. Run the BSC6900 MML command PING MAC. In this step, set MA Index and
MEP ID to the values specified in ADD CFMMEP, and set RMEP ID to the
MEP ID of the peer device.
Expected result: The number of received packets equals the number of sent packets.
2. Run the BSC6900 MML command TRC MAC. In this step, set MA Index and
MEP ID to the values specified in ADD CFMMEP, and set RMEP ID to the
MEP ID of the peer device.
Expected result: The returned result contains "Succeed in tracing the destination
address".
– Deactivating point-to-point Ethernet OAM
– BSC
1. Run the BSC6900 MML command DEA EFMAH (CME single configuration:
GSM Global Configuration Express > IP Interface Configuration > EFM
OAM; CME batch modification center: not supported) to deactivate the EFM
OAM function.
– BTS
1. Run the BSC6900 MML command SET BTSETHPORT (CME single
Ethernet Port of IP BTS; CME batch modification center: not supported). In
this step, set 3ah Switch to CLOSE(Close).
2. Run the BSC6900 MML command DEA BTSETHOAMAH (CME single
Maintenance > BTS Ethernet OAM; CME batch modification center: not
supported) to deactivate the BTS EFM OAM function.
– Deactivating end-to-end Ethernet OAM
– BSC
1. Run the BSC6900 MML command DEA CFMCCMTST (CME single
Configuration > Ethernet Port OAM Continuity Check; CME batch
modification center: not supported) to deactivate the connectivity test of
Ethernet OAM.
2. Run the BSC6900 MML command RMV CFMMEP (CME single
supported) to remove the MEPs for Ethernet OAM at the two ends.
3. Run the BSC6900 MML command RMV CFMMA (CME single
Configuration > Ethernet OAM MA; CME batch modification center: not
supported) to remove an Ethernet OAM MA.
4. Run the BSC6900 MML command RMV CFMMD (CME single
Configuration > Ethernet OAM MD; CME batch modification center: not
supported) to remove an Ethernet OAM MD.
– BTS

GBSS14.0
1. Run the BSC6900 MML command DEA BTSETHCC (CME single

Maintenance > BTS Ethernet OAM CC Function; CME batch modification
center: not supported) to deactivate the connectivity test of BTS Ethernet OAM.
2. Run the BSC6900 MML command RMV BTSETHRMMEP (CME single
Maintenance > BTS Ethernet OAM Remote MEP; CME batch modification
center: not supported) to remove an MEP for BTS Ethernet OAM at the remote
end.
3. Run the BSC6900 MML command RMV BTSETHLCMEP (CME single
Maintenance > BTS Ethernet OAM Local MEP; CME batch modification
center: not supported) to remove an MEP for BTS Ethernet OAM at the local
end.
4. Run the BSC6900 MML command RMV BTSETHMA (CME single
Maintenance > BTS Ethernet OAM Maintenance Association; CME batch
modification center: not supported) to remove a BTS Ethernet OAM MA.
5. Run the BSC6900 MML command RMV BTSETHMD (CME single
Maintenance > BTS Ethernet OAM Maintenance Domain; CME batch
modification center: not supported) to remove a BTS Ethernet OAM MD.
----End
Example
//Activating Ethernet OAM
Activating point-to-point Ethernet OAM

//BSC
ACT EFMAH: SRN=0, SN=18, PN=0;
//BTS
SET BTSETHPORT: IDTYPE=BYID, BTSID=7, PN=0, SWITCH3AH=OPEN;
ACT BTSETHOAMAH: IDTYPE=BYID, BTSID=7, PN=0;
Activating end-to-end Ethernet OAM

//BSC
ADD CFMMD: SRN=0, SN=18, MDIDX=0, LEVEL=0, MDNAME="md0";
ADD CFMMA: SRN=0, SN=18, MDIDX=0, VLANID=2, MAIDX=0, MANAME="ma0";
ADD CFMMEP: SRN=0, MAIDX=0, MEPTYPE=LocalMep, MEPID=1, PORTTYPE=ETHER,
SN=18, PN=0;
ADD CFMMEP: SRN=0, MAIDX=0, MEPTYPE=RemoteMep, MEPID=2, SN=18;
ACT CFMCCMTST: SRN=0, SN=18, MAIDX=0, MEPID=1;
//BTS
ADD BTSETHMD: IDTYPE=BYID, BTSID=7, MDNAME="md0", MDLEVEL=0;
ADD BTSETHMA: IDTYPE=BYID, BTSID=7, MDNAME="md0", MANAME="ma0", VLANID=2;
ADD BTSETHLCMEP: IDTYPE=BYID, BTSID=7, MDNAME="md0", MANAME="ma0",
MEPID=2, PN=0;
ADD BTSETHRMMEP: IDTYPE=BYID, BTSID=7, MDNAME="md0", MANAME="ma0",
MEPID=1;
ACT BTSETHCC: IDTYPE=BYID, BTSID=7, MDNAME="md0", MANAME="ma0", MEPID=2;
//Deactivating Ethernet OAM
Deactivating point-to-point Ethernet OAM

//BSC
DEA EFMAH: SRN=0,SN=18,PN=0;

GBSS14.0
//BTS
SET BTSETHPORT: IDTYPE=BYID, BTSID=7, PN=0, SWITCH3AH=CLOSE;
DEA BTSETHOAMAH: IDTYPE=BYID, BTSID=7, PN=0;
Deactivating end-to-end Ethernet OAM

//BSC
DEA CFMCCMTST: SRN=0, SN=18, MAIDX=0, MEPID=1;
RMV CFMMEP: SRN=0, SN=18, MAIDX=0,MEPID=2;
RMV CFMMEP: SRN=0, SN=18, MAIDX=0,MEPID=1;
RMV CFMMA: SRN=0, SN=18, MAIDX=0;
RMV CFMMD: SRN=0, SN=18, MDIDX=0;
//BTS
DEA BTSETHCC: IDTYPE=BYID, BTSID=7, MDNAME="md0", MANAME="ma0", MEPID=2;
RMV BTSETHRMMEP: IDTYPE=BYID, BTSID=7, MDNAME="md0", MANAME="ma0",
MEPID=1;
RMV BTSETHLCMEP: IDTYPE=BYID, BTSID=7, MDNAME="md0", MANAME="ma0",
MEPID=2;
RMV BTSETHMA: IDTYPE=BYID, BTSID=7, MDNAME="md0", MANAME="ma0";
RMV BTSETHMD: IDTYPE=BYID, BTSID=7, MDNAME="md0";

GBSS14.0
Feature Activation Guide 150 Configuring A Interface Transmission Pool
150 Configuring A Interface

Transmission Pool
A Interface Transmission Pool. When an Ethernet Layer 3 networking is used, multiple IP
interface boards used by the A interface on the BSC form a resource pool and the IP addresses
for these interface boards also form a resource pool. Any interface board in the resource pool is
accessible to the core network (CN). The BSC selects an IP address from the resource pool for
bearing incoming services based on load balancing so that interface boards share resources in
the pool.
Prerequisites
– This feature depends on the feature GBFD-118602 A over IP.
– This feature cannot be used together with the feature GBFD-118610 UDP MUX for A
Transmission.
l License
– N/A
– This feature applies to IP transmission only.
– N/A
– GOUc, GOUd, FG2c, and FG2d boards support a transmission resource pool.
Context
l Precautions
– None

GBSS14.0
l Data Preparation
Parameter
IP TYPE IPTYPE - Network

planning
Source IP SRCIPADDR Set this parameter to a value Network

address consistent with the IP planning
address in commands ADD
ETHIP, ADD
ETHTRKIP or ADD
DEVIP based on the setting
of the parameter IP TYPE.
Forward route NEXTHOP IP address for a router Network

address planning
Standby Next STANDBYNEXT This parameter is valid only Network

hop switch HOPSWITCH if the source IP address is a planning
device IP. This parameter is
set to YES when active and
standby gateways are
configured.
Standby next STANDBYNEXT Another IP address for a Network

hop HOP router planning
Transmission IPPOOLNAME - Network

Resource Pool planning
Name
Transmission IPPOOLINDEX - Network

Resource Pool planning
Index
IP Address in IPADDR Same as IP address in the Network

Transmission ADD DEVIP command planning
Resource Pool
Is IP Pool ISIPPOOL - Network

planning
Procedure
– Scenarios for Initial Configuration
1. See Configuring the Physical Layer and Data Link Layer for the FG2c/FG2d/
GOUc/GOUd Board in Initial Configuration Guide.
2. See Configuring the Transmission Resource Pool in Initial Configuration Guide.
3. See Configuring the Control Plane of the A Interface (over Transmission Resource
Pool) in Initial Configuration Guide.

GBSS14.0
4. See Configuring the User Plane of the A Interface (Transmission Resource Pool)
in Initial Configuration Guide.
5. See Configuring the Mapping Between Service Types and Transmission
Resources for the Adjacent Node in Initial Configuration Guide.
– Reconfiguration Scenarios
– See Reconfiguring Networking Mode over the A Interface (IP->Transmission
Resource Pool) in Reconfiguration Guide.
– See Reconfiguring Networking Mode over the A Interface (TDM->Transmission
Resource Pool) in Reconfiguration Guide.
1. Run the BSC6900 MML commandDSP ETHPORT to query the port rate and
working mode.
Expected results: Speed is set to 1000M and Duplex is set to Full.
2. Run the BSC6900 MML commandDSP SRCIPRT to check whether the source IP
address is received at and sent from the interface board in a physical slot.
– If the values of both Number of Packets Sent and Number of Packets
Received increase in the same slot, the route priority on the BSC side is consistent
with that at the peer end.
– If the value of Number of Packets Received increases in both active and standby
slots, the wrongly configured equal-cost route between the router and the BSC
must be replaced with a route in active/standby mode.
– If the slot where the value of Number of Packets Received increases is different
from the slot where the value of Number of Packets Sent increases, the route
priorities on the BSC and the peer route are inconsistent and therefore must be
corrected.
3. Check Ping-related alarms. None of the alarms ALM-21392 Adjacent Node IP
Address Ping Failure, ALM-21393 Adjacent Node IP Path Ping Failure, and
ALM-21394 Transmission Resource Pool Ping Packet Loss is reported.
4. Run the BSC6900 MML commandDSP IPPOOL to check whether the settings of
Send bit rate of the port[bps], Receive bit rate of the port[bps], Send bit rate load
of the board, Receive bit rate load of the board, Send packets load of the board,
and Receive packets load of the board for outgoing ports using source IP addresses
in the transmission resource pool are balanced.
----End
Example
//Activating A Interface Transmission Pool
// Please see typical configuration script examples in Initial
Configuration Guide.

GBSS14.0
Feature Activation Guide 151 Configuring Satellite Transmission over Abis Interface
151 Configuring Satellite Transmission

over Abis Interface
Satellite Transmission over Abis Interface. (This feature cannot be configured using the CME. )
Prerequisites
– This feature cannot be used with the following feature: GBFD-510104 Multi-site Cell.
l License
The cell to be verified is in the normal state and has idle channels.
To ensure the normal processing of PS services in satellite transmission mode, the GPRS
parameters related to a PS cell need to be set as follows: T3168 is set to 1000ms, T3192
to 1000ms, and BS_CV_MAX to 15.
Context
TDM or IP transmission is used over the Abis interface. Using satellite transmission over the
Abis interface enables operators to deploy BTSs in areas that are difficult to reach through
conventional terrestrial transmission, therefore solving the communication problem in these
areas. Compared with terrestrial transmission, the information exchange latency is prolonged in
satellite transmission.
Satellite transmission with limited transmission bandwidth for BTS3900B (a pico base station)
only supports CS services. The method of configuring satellite transmission over the Abis
interface for BTS3900B is different from that for other BTSs.

GBSS14.0
Procedure
– If TDM transmission is used over the Abis interface, perform the following steps:
2. Run the BSC6900 MML command SET BTSTRANS. In this step, set
Transmission Mode to SAT_TRANS(Satellite Transmission).
3. (Optional) Run the BSC6900 MML command SET BTSLAPDWS. In this step,
set RSL LAPD Window Size to an appropriate value based on the actual delay.
NOTE
RSL LAPD Window Size is set to 48 by default and can be flexibly configured by operators
based on the actual delay. A longer delay requires a larger value.
4. (Optional) Run the BSC6900 MML command SET GCELLCCTMR. In this
step, set T200 SDCCH to 200, T200 SACCH SDCCH to 100, and T200 SDCCH
SAPI3 to 200. Operators can adjust the settings of these parameters based on the
actual delay over the Abis interface. A longer delay requires a larger value.
5. (Optional) Run the BSC6900 MML command SET GCELLCCBASIC. In this
step, set MS MAX Retrans to an appropriate value.
NOTE
Setting MS MAX Retrans to a larger value increases the radio access rate and setting MS
MAX Retrans to a smaller value lightens the load of the RACH and SDCCH.
7. Configuring a Clock for a BTS.
NOTE
If the BTS has a difficulty in using the original clock, Run the BSC6900 MML
command SET BTSCLK. In this step, set Clock Type to INT_CLK(Internal Clock).
– If IP transmission is used over the Abis interface, perform the following steps:
– For a BTS,
Transmission Mode to SAT_TRANS(Satellite Transmission).
3. Run the BSC6900 MML command LST GCELLSOFT to query the value of
DL DTX Strategy. If the value of DL DTX Strategy is set to MSC
Strategy, the downlink DTX is consistent with the MSC. In this case, ensure
that DTX is enabled at the CN.
NOTE
command SET BTSCLK. In this step, set Clock Type to INT_CLK(Internal
Clock).
– For a pico BTS with limited transmission bandwidth,
NOTE
Pico satellite transmission is supported only when an FG2c/FG2d/GOUc/GOUd board serve

as the Abis interface board.

GBSS14.0
Transmission Mode to PICO_AND_SAT_TRANS(Pico and Satellite).
3. Run the BSC6900 MML command ADD BTSABISMUXFLOW. In this step,
set Service Type to CSVOICE(CS Voice), and set Maximum Delay Time to
90.
4. Run the BSC6900 MML command SET BSCJBF. In this step, set IP-over-
Satellite JitterBuffer Init Time to 300.
5. Run the BSC6900 MML command ADD IPMUX. In this step, set IP MUX
Type, Adjacent node ID, IP path ID, IS QOSPATH, and Maximum Delay
Time[ms] to 90.
6. Run the BSC6900 MML command SET GCELLCCACCESS with Speech
Version set to FULL_RATE_VER1(Full Rate VER 1) and
HALF_RATE_VER3(Half Rate VER 3).
7. Run the BSC6900 MML command SET GCELLCCAMR. In this step, set
AMR ACS[H] to 4_75KBIT/S, set AMR Starting Mode[H] to 0.
AMR TCH/H Prior Allowed to ON(On), and set Tch Traffic Busy Overlay
Threshold and AMR TCH/H Prior Cell Load Threshold to 0.
9. Run the BSC6900 MML command SET GCELLBASICPARA. In this step,
set HR Use Downlink DTX to YES(Yes) and HR Uplink DTX to Shall_Use
(Shall Use).
10. Run the BSC6900 MML command LST GCELLSOFT to query the value of
DL DTX Strategy. If DL DTX Strategy is set to MSC Strategy, the downlink
DTX is consistent with the MSC. In this case, ensure that DTX is enabled at
the CN.
11. Run the BSC6900 MML command SET GCELLTMR. In this step, set
T3101 to 4000.
NOTE
command SET BTSCLK. In this step, set Clock Type to INT_CLK(Internal
Clock).
1. Run the BSC6900 MML command DSP GCELLSTAT to query the status of the cell.
Expected result: Cell Service State is set to Yes.
2. Use the MS to initiate a call.
3. Tracing CS Domain Messages on the Abis Interface In this step, click RSL under
Trace Type.
Expected result: A complete signaling procedure for the mobile-originated call is
traced.
4. (Optional): When IP transmission is used over the Abis interface, access the internet
by dialing and perform a ping service. The ping service is successful.

GBSS14.0
2. Run the BSC6900 MML command SET BTSTRANS. In this step, set Transmission
Mode to TER_TRANS(Terrestrial Transmission).
3. Optional: Run the BSC6900 MML command SET GCELLCCTMR. In this step,
set T200 SDCCH to 60, T200 SACCH SDCCH to 60, and T200 SDCCH SAPI3 to
60. Adjust settings of these parameters based on the actual delay over the Abis
interface. A longer delay requires a larger value.
4. Optional: Run the BSC6900 MML command SET GCELLCCBASIC. In this step,
set MS MAX Retrans to 2_Times(2_Times). Set MS MAX Retrans to an
appropriate value as required.
set T3168 to 500ms, T3192 to 500ms, and BS_CV_MAX to 10.
----End
Example
/*Activating Satellite Transmission over Abis Interface*/
//Deactivating a BTS
//Setting a transmission mode
SET BTSTRANS: IDTYPE=BYID, BTSID=0, TransMode=SAT_TRANS;
//Activating a pico BTS
//Setting a clock mode
/*Activating Satellite Transmission over Abis Interface for a Pico*/
SET BTSTRANS: IDTYPE=BYID, BTSID=0, TransMode=PICO_AND_SAT_TRANS;
//Setting IP MUX on the BTS side
ADD BTSABISMUXFLOW: IDTYPE=BYID, BTSID=0, SRVTYPE=CSVOICE, TIMEOUT=90;
//setting IP-over-Satellite JitterBuffer Init Time
SET BSCJBF: IPOSATJttTime=300;
//Setting IP MUX on the BSC side
ADD IPMUX: MUXTYPE=ABISMUX, ANI=0, PATHID=0, ISQOSPATH=NO, FPTIMER=90;
//setting Speech Version
1-0&HALF_RATE_VER2-0&HALF_RATE_VER3-1&HALF_RATE_VER5-0;
//Setting AMR call control parameters for the cell
SET GCELLCCAMR: IDTYPE=BYID, CELLID=0, ACTCDSETH=4_75KBIT/S-1&5_15KBIT/
S-0&5_90KBIT/S-0&6_70KBIT/S-0&7_40KBIT/S-0&7_95KBIT/S-0, INITCDMDH=0;
AMRTCHHPRIORALLOW=ON, AMRTCHHPRIORLOAD=0;
//Setting half rate downlink DTX
SET GCELLBASICPARA: IDTYPE=BYID, CELLID=0, HRDLDTX=YES,
HRULDTX=Shall_Use;
//Setting 3101 timer
SET GCELLTMR: IDTYPE=BYID, CELLID=0, ESTABINDTIMER=4000;
//Activating a BTS
//Setting a clock mode
/*Deactivating Satellite Transmission over Abis Interface*/

GBSS14.0

SET BTSTRANS: IDTYPE=BYID, BTSID=0, TransMode=TER_TRANS;
//Activating a pico BTS

GBSS14.0
Feature Activation Guide 152 Configuring Satellite Transmission over A Interface

over A Interface
Satellite Transmission over A Interface.
Prerequisites
– The EIUa/OIUa/POUc board is configured.
l License
The initial configuration of the BSC is complete. The cell to be verified is in the normal
state and has idle channels.
Context
Satellite transmission can be applied on the A interface in situations where terrestrial
transmission cannot be established between the BSC and MSC (for example, in sites where an
emergency situation occurs temporarily or in scenarios where satellite works as a backup
transmission means).
If satellite transmission is applied over the A interface, you are advised to configure satellite
transmission over the Ater interface.
Procedure
modification center: not supported) to add an E1/T1 link on the A interface.

GBSS14.0
NOTE
An EIUa board provides 32 E1s/T1s. Each E1 has thirty-two 64 kbit/s timeslots. Each T1 has
twenty-five 64 kbit/s timeslots. Each timeslot corresponds to a CIC.
For example, if Start CIC of the first E1/T1 is 0, then Start CIC of the second E1/T1 must
belong to a CIC group that is different from the CIC group of Start CIC of the first configured
E1/T1. Here, if E1 is used, Start CIC of the second E1 must be greater than 31. If T1 is used,
Start CIC of the second T1 must be greater than 24.
When the MSC Pool feature is enabled, the Start CIC of the E1s/T1s that have the same pair
of originating and destination signaling points must be unique.
signaling link set on the A interface.
Signalling Link; CME batch modification center: not supported) with Satellite flag
set to YES(YES) to add an MTP3 signaling link on the A interface.
modification center: not supported) to add an MTP3 route on the A interface.
1. Use an MS to originate a call. The call is set up successfully.
2. Run the BSC6900 MML command DSP MTP3LNK to query the status of the MTP3
signaling link.
Expected result: UsageStatus is set to Normal.
3. Trace the messages on the A interface by referring to Tracing Messages on the A
Interface. In this step, click BSSAP under Trace Type. Trace the CS domain messages
on the Abis interface by referring to Tracing CS Domain Messages on the Abis
Interface. In this step, click RSL under Trace Type.
Expected result: Complete signaling procedure of the mobile-originated call can be
seen.
A Configuration Express > TDM Transport > MTP3 Signalling Link Set > MTP3
Signalling Link; CME batch modification center: not supported) to remove the MTP3
signaling link.
Signalling Link; CME batch modification center: not supported) with Satellite flag
set to NO(NO) to add an MTP3 signaling link on the A interface.
----End
Example
/*Activating the feature Satellite Transmission over A Interface*/
//Configuring the A interface E1/T1
ADD AE1T1: SRN=0, SN=14, PN=0, DPCGIDX=0, OPCIDX=0, ALLTSTYPE=ALLCIC,
//Configuring an MTP3 link set over the A interface
ADD MTP3LKS: SIGLKSX=0, DPX=0, NAME="SATTRAN";

GBSS14.0
//Configuring an MTP3 link over the A interface

ADD MTP3LNK: SIGLKSX=0, SIGSLC=1, BEARTYPE=MTP2, TCMODE=TOGETHER, ASRN=0,
ASN=16, MTP2LNKN=0, APN=0, ATSMASK=TS1-1&TS2-1&TS3-1&TS4-1&TS5-1,
LKTATE=64K, STFLG=YES NAME="0";
//Configuring an MTP3 route over the A interface
ADD MTP3RT: DPX=0, SIGLKSX=0, NAME="SAT";
/*Deactivating the feature Satellite Transmission over A Interface*/
//Removing an MTP3 link with Satellite flag set to YES(YES)
//Adding an MTP3 link with Satellite flag set to NO(NO)
ADD MTP3LNK: SIGLKSX=0, SIGSLC=1, BEARTYPE=MTP2, TCMODE=TOGETHER, ASRN=0,
ASN=16, MTP2LNKN=0, APN=0, ATSMASK=TS1-1&TS2-1&TS3-1&TS4-1&TS5-1,
LKTATE=64K, STFLG=NO NAME="1";

GBSS14.0
Feature Activation Guide 153 Configuring Satellite Transmission over Ater Interface

over Ater Interface
Satellite Transmission over Ater Interface. (This feature cannot be configured using the CME. )
Prerequisites
– The EIUa/OIUa board is configured.
l License
The initial configuration of the BSC is complete. The cell to be verified is in the normal
state and has idle channels.
Context
In BM/TC separated mode with the TC configured remotely, satellite transmission over Ater
interface can be used when installing transmission lines is geographically impossible.
If satellite transmission is applied over the A interface, you are advised to configure satellite
transmission over the Ater interface.
Procedure
1. Run the BSC6900 MML command ADD ATERCONPATH to add an Ater
connection path between the MPS and the TCS.
NOTE
If the TC pool feature is supported, the command only applies to the main BSC. The sub-BSC
needs to be configured through the ADD ATERE1T1 command.

GBSS14.0
Feature Activation Guide 153 Configuring Satellite Transmission over Ater Interface
2. Run the BSC6900 MML command ADD ATEROML to add an Ater OML.
3. Run the BSC6900 MML command ADD PBE1T1 with Transmission Mode set to
SATEL(Satellite Transmission) to add an E1/T1 link on the Pb interface.
NOTE
needs to be configured through the ADD ATERSL command.
4. Optional: Run the BSC6900 MML command MOD ATERCONSL with Window
Size set to an appropriate value according to the actual delay.
NOTE
needs to be configured through the MOD ATERSL command.
The longer the delay in satellite transmission, the larger the value to be set.
1. Run the BSC6900 MML command DSP ATERSL to query the status of the Ater
signaling link.
Expected result: UsageStatus is set to Normal.
1. Run the BSC6900 MML command MOD ATERSL with Transmission Mode set to
TRRS(Terrestrial Transmission).
----End
Example
/*Activating the feature Satellite Transmission over Ater Interface*/
//Adding an Ater connection path
TCPN=0;
//Adding an Ater OML
//Adding an Ater signaling link with Transmission Mode set to SATEL
(Satellite Transmission)
TNMODE=SATEL;
/*Deactivating the feature Satellite Transmission over Ater Interface*/
//Modifying the transmission mode of the Ater signaling link
MOD ATERCONSL: ATERSLID=0, TNMODE=TRRS;

GBSS14.0
Feature Activation Guide 154 Configuring Satellite Transmission over Gb Interface

over Gb Interface
Satellite Transmission over Gb Interface.
Prerequisites
– The DPUb board is configured.
l License
Procedure
1. The procedure for configuring the satellite transmission on the Gb interface is the
same as the procedure for configuring the terrestrial transmission on the Gb interface.
For details, see Configuring the Gb Interface (over FR) (CME single configuration:
see the Configuring the Gb Interface (FR) in the M2000-CME documentation; CME
batch modification center: not supported) and Configuring the Gb Interface (over IP)
(CME single configuration: see the Configuring the Gb Interface (IP) in the M2000-
CME documentation; CME batch modification center: not supported).
1. After an NSE is added, Run the BSC6900 MML command DSP SIGBVC to query
the state of an SIG BSSGP virtual connection (SIG BVC) by checking the setting of
SIG BVC State.
Expected result: If SIG BVC State is set to Normal, it indicates that the SIG BVC
works properly.
2. After a PTP BVC is added, Run the BSC6900 MML command DSP PTPBVC to
query the state of the PTP BVC by checking the setting of Service State.

GBSS14.0
Feature Activation Guide 154 Configuring Satellite Transmission over Gb Interface
Expected result: If Manage State is set to Unblock and Service State is set to
Normal, it indicates that the PTP BVC works properly.
----End
Example
For configurations, see the typical script example of the Gb interface configuration in the Initial
Configuration.

GBSS14.0
Feature Activation Guide 155 Configuring RAN Sharing
RAN Sharing.
Prerequisites
– The GBFD-118702 MOCN Shared Cell feature is mutually exclusive with the RAN
Sharing feature.
– The GBFD-118106 Dynamic Power Sharing feature is mutually exclusive with the
RAN Sharing feature.
– The GBFD-114402 Enhanced Dual-Band Network feature is mutually exclusive with
the RAN Sharing feature.
– The GBFD-510104 Multi-site Cell is mutually exclusive with the RAN Sharing feature.
l License
– The BSC supports service processing board sharing by multiple operators. Operators
that share the BSC do not have their respective service processing boards.
– The MSCs of different operators use the same signaling system No. 7 (SS7) rate.
– RAN Sharing supports a maximum of four operators, including the primary operator.
– RAN Sharing supports a maximum of four CBCs.
– The DPC of the SS7 signaling and the total number of SGSNs remain unchanged after
RAN Sharing is enabled.
– The devices of all operators are connected to the same M2000, and the information
about all alarms and performance counters can be viewed on the M2000. Such
information is not displayed on a per operator basis.
– The BSC clock of one operator is used as the reference clock for other operators.
Operators ensure the clock synchronization among their MSCs.

GBSS14.0
– If a network service entity (NSE) and a cell belong to different operators, a packet point-
to-point BSSGP virtual connection (PTP BVC) cannot be configured between the NSE
and the cell.
Context
The RAN sharing function allows multiple operators with independent core networks to share
GBSS network resources, such as BSC, BTS, antenna, and transmission devices. A single cell
under a site provides services for only one operator, and different cells under a site provide
services for multiple operators.
Parameter Data
Support RAN SptRanSharing Set this parameter to YES(Yes). Engineering

Sharing design
Operator Type OperatorType Configure a primary operator Radio

and multiple secondary network
operators. planning
(internal
planning)
Operator Name OPNAME Set this parameter based on the Radio

operator information. network
planning
(internal
planning)
MCC MCC Set this parameter based on the Radio

planning
(Negotiated
with the peer
end)
MNC MNC Set this parameter based on the Radio

planning
(Negotiated
with the peer
end)
Handover HOBTWNOTHOP Set this parameter to YES(Yes) Engineering

Between ALLOW when handovers between cells design
Operators Allow of different operators are
allowed.
DSP name NAME Set this parameter based on the Transmissio

operator information. n network
planning
(internal
planning)

GBSS14.0
Parameter Data
DSP code[Whole DPC Set this parameter based on the Transmissio

Number] operator information. n network
planning
(Negotiated
with the peer
end)

planning
(internal
planning)
MSC ID CNID Set this parameter based on the Radio

planning
(Negotiated
with the peer
end)
Default DPC DFDPC On the CN of the primary Engineering

operator: design
When only one DSP is
configured, set this parameter to
YES(Default DPC), indicating
that all calls of this operator are
accessed on this CN.
When multiple DSPs are
YES(Default DPC) for the DSP
used to generate an equipment
serial number (ESN) and set this
parameter to NO(Not Default
DPC) for other signaling points.
On the CN of a secondary
operator:
When only one DSP is
YES(Default DPC), indicating
that all calls of this operator are
accessed on this CN.
When multiple DSPs are
configured, this parameter is
invalid.

GBSS14.0
Parameter Data

planning
(internal
planning)
SGSN Node ID CNID Set this parameter based on the Device

operator information. planning
Sharing Allow SHARINGALLOW Set this parameter to YES(YES) Device

to share a BTS. planning

planning
(internal
planning)
Procedure
1. Configure the BSC data by referring to BSC6900 GSM Initial Configuration Guide.
For a BSC to be deployed, the following substeps are required for initial configuration.
For a deployed BSC, the following substeps are required for enabling the RAN Sharing
feature.

3.17 Modifying GBSC Parameters in Batches). In this step, set Support RAN
Sharing set to YES(Yes).
b. Run the BSC6900 MML command ADD GCNOPERATOR (CME single
Configuration > GSM Operator; CME batch modification center: not
supported). In this step, set Operator Type to SEC(Secondary Operator). Set
Operator Index, Operator Name, MCC, MNC and Handover Between
Operators Allow based on actual conditions, and set other parameters to
appropriate values.
c. Add DSPs for secondary perators based on actual conditions as in initial
configuration.
NOTE
If a BSC needs multiple originating signaling points (OSPs) to communicate with
operators, configure multiple OSPs by enabling the Local Multiple Signaling Points
feature. For details, see 136 Configuring Local Multiple Signaling Points.
d. If the A interface uses IP transmission, add M3UA local entities and destination
entities for secondary operators based on actual conditions as in initial
configuration.

GBSS14.0
NOTE
If a BSC needs multiple OSPs to communicate with operators, configure M3UA local
entities for secondary operators.
e. Add the A interface and Gb interface data for secondary operators as in initial
configuration.
– Run the BSC6900 MML command ADD GCNNODE (CME single
Configuration > GSM CN Node; CME batch modification center: not
supported). In this step, set Operator Name to the name of a secondary
operator and set other parameters to appropriate values.
– Run the BSC6900 MML command ADD SGSNNODE (CME single
configuration: Gb Configuration Express > SGSN > SGSN Node; CME
batch modification center: not supported). In this step, set Operator Name
to the name of a secondary operator and set other parameters to appropriate
values.
– Run the BSC6900 MML command ADD NSE (CME single configuration:
Gb Configuration Express > IP Transport > NSE; CME batch
modification center: not supported). In this step, set Operator Name to the
name of a secondary operator and set other parameters to appropriate values.
2. Configure the BTS data.
– Transfer cells of the primary operator to secondary operators.
a. Run the BSC6900 MML command SET BTSSHARING (CME single
configuration: BTS Configuration Express > BTS Basic Attributes > BTS
RAN Sharing Parameters; CME batch modification center: not supported)
for a specific target BTS. In this step, set Sharing Allow to YES(YES).
NOTE
For details about how to configure independent resource transmission for operators,
see 158 Configuring Abis Independent Transmission.
b. If a PTP BVC has been configured, Run the BSC6900 MML command RMV
PTPBVC (CME single configuration: Gb Configuration Express > IP
Transport > PTP BVC; CME batch modification center: not supported) to
delete PTP BVCs in a cell.
c. Run the BSC6900 MML command MOD GCELL (CME single
configuration: Cell Configuration Express > Cell Attributes > GSM
CELL; CME batch modification center: 3.20 Modifying GSM Cell
Parameters in Batches) with Operator Name set to the name of a secondary
operator.
NOTE
When a cell has been configured with neighboring cells, delete the existing neighbor
relationships before changing the operator of the cell.
d. If a BSC uses multiple OSPs to communicate with operators, Run the
BSC6900 MML command MOD GCELLOSPMAP (CME single
configuration: Cell Configuration Express > Cell Attributes > Relation
between Cell and OSP; CME batch modification center: 3.20 Modifying
GSM Cell Parameters in Batches) with OSP Code set to the OPC of the
BSC assigned by a secondary operator.
e. After Handover Between Operators Allow is set to YES(Yes), adjust
neighbor relationship between cells of different operators. For details, see
BSC6900 GSM Initial Configuration Guide.

GBSS14.0
f. Run the BSC6900 MML command ADD PTPBVC (CME single

configuration: Gb Configuration Express > IP Transport > PTP BVC;
CME batch modification center: not supported) to add PTP BVCs from cells
to SGSNs of secondary operators.
– Configure new cells for secondary operators. For details, see BSC6900 GSM Initial
a. Run the BSC6900 MML command SET BTSSHARING (CME single
NOTE
b. (Optional) Add a radio frequency unit (RFU) for the BTS as in initial
configuration.
c. Configure the cell data and the binding relationship between cells and BTSs,
and between logical TRXs and physical TRX modules, channel information,
attributes and neighbor relationship of TRXs as in initial configuration. In
this step, set Operator Name to the name of a secondary operator and set other
parameters based on the secondary operator information.
d. Run the BSC6900 MML command ADD PTPBVC (CME single
to SGSNs of secondary operators.
– Configure new BTSs for operators to share. For details, see BSC6900 GSM Initial
a. Add a BTS and configure the related device data as in initial configuration.
b. Run the BSC6900 MML command SET BTSSHARING (CME single
NOTE
c. Add transmission-related data as in initial configuration.
d. Configure the cell data and the binding relationship between cells and BTSs,
and between logical TRXs and physical TRX modules, channel information,
attributes and neighbor relationship of TRXs as in initial configuration. In
this step, set Operator Name to the name of a secondary operator and set other
parameters based on the secondary operator information.
e. Run the BSC6900 MML command ADD PTPBVC (CME single
CME batch modification center: not supported) to add PTP BVCs from cells.
f. Run the BSC6900 MML command ACT BTS (CME single configuration:
Main View > Right click BTS > Activate BTS; CME batch modification
center: not supported) to activate the BTS.

GBSS14.0
1. Get two test MSs ready: MS1 and MS2. MS1 belongs to operator A, and MS2 belongs
to operator B.
2. Initiate Abis-interface CS message tracing on the LMT with Trace Type set to
RSL. For details, see Tracing CS Domain Messages on the Abis Interface.
3. Initiate A-interface CS message tracing on the LMT with Trace Type set to
BSSAP. For details, see Tracing Messages on the A Interface.
4. Enable MS1 to camp on cell1 and make a successful call to a fixed-line phone. Check
the tracing results of cell1.
Expected result: The complete MOC signaling procedure of MS1 is displayed.

5. Enable MS2 to camp on cell2 and make a successful call to a fixed-line phone. Check
the tracing results of cell2.
Expected result: The complete MOC signaling procedure of MS2 is displayed.

6. Initiate Um-interface PS message tracing on the LMT for cell1 and cell2. For details,
see Tracing PS Domain Messages on the Um Interface.
7. Enable MS1 to perform PS services in cell1, and check Um-interface PS message trace
results in cell1.
Expected result: The signaling procedure for PS services of MS1 is displayed.

8. Enable MS2 to perform PS services in cell2, and check Um-interface PS message trace
results in cell2.
Expected result: The signaling procedure for PS services of MS2 is displayed.

1. Disable the BTS data.
– Transfer cells of secondary operators to the primary operator.
a. If a PTP BVC has been configured, Run the BSC6900 MML command RMV
PTPBVC (CME single configuration: Gb Configuration Express > IP
Transport > PTP BVC; CME batch modification center: not supported) to
PTP BVCs from cells to SGSNs of secondary operators.
b. Run the BSC6900 MML command MOD GCELL (CME single
configuration: Cell Configuration Express > Cell Attributes > GSM
CELL; CME batch modification center: 3.20 Modifying GSM Cell
Parameters in Batches) with Operator Name set to the name of the primary
operator.
c. If a BSC uses multiple OSPs to communicate with operators, Run the
BSC6900 MML command MOD GCELLOSPMAP (CME single
configuration: Cell Configuration Express > Cell Attributes > Relation
between Cell and OSP; CME batch modification center: 3.20 Modifying
GSM Cell Parameters in Batches) with OSP Code set to the OPC of the
BSC assigned by the primary operator.
d. After Handover Between Operators Allow is set to YES(Yes), adjust
neighbor relationships between cells of different operators. For details, see
e. Run the BSC6900 MML command ADD PTPBVC (CME single
to SGSNs of primary operators.

GBSS14.0
f. Run the BSC6900 MML command SET BTSSHARING (CME single

for a specific target BTS. In this step, set Sharing Allow to NO(NO).
– Delete cells of secondary operators.
a. Run the BSC6900 MML command RMV GCELL (CME single
configuration: BTS Topology > Right click Cell > Delete Cell; CME batch
modification center: 3.19 Deleting GSM Cells in Batches) to delete the
secondary operator cells.
b. Run the BSC6900 MML command SET BTSSHARING (CME single
for a specific target BTS. In this step, set Sharing Allow to NO(NO).
– Delete the shared BTS.
a. Run the BSC6900 MML command DEA BTS (CME single configuration:
Main View > Right click BTS > Deactivate BTS; CME batch modification
center: not supported) to deactivate a target BTS.
b. Run the BSC6900 MML command RMV BTS (CME single configuration:
Main View > Right click BTS > Delete BTS; CME batch modification
center: not supported) to delete the target BTS.
2. Disable the BSC data.
a. Delete the secondary operator information, DSPs, M3UA destination entities,
CN nodes, A interface data, and Gb interface data involved in BSC data
configuration.
b. Run the BSC6900 MML command SET BSCBASIC (CME single
3.17 Modifying GBSC Parameters in Batches). In this step, set Support RAN
Sharing to NO(No).
----End
Example
/*Activating BSS Sharing*/
//Enabling RAN Sharing
SET BSCBASIC: SptRanSharing=YES;
//Configuring parameters related to BTS sharing
SET BTSSHARING: IDTYPE=BYID, BTSID=0, SHARINGALLOW=YES;
//Deleting the original PTP BVCs for a cell
RMV PTPBVC: NSEI=1, BVCI=10;
//Modifying the operator information
MOD GCELL: IDTYPE=BYID, CELLID=2, OPNAME="B";
//Modifying the Cell-OSP mapping
MOD GCELLOSPMAP: IDTYPE=BYID, CELLID=2, OPC=H'000A12;
//Adding PTP BVCs for a cell
ADD PTPBVC: NSEI=1, BVCI=10, IDTYPE=BYID, CELLID=2;
/*Deactivating BSS Sharing*/

//Deleting PTP BVCs in cells of secondary operators
//Modifying the operator information

GBSS14.0
MOD GCELL: IDTYPE=BYID, CELLID=2, OPNAME="A";

//Modifying the Cell-OSP mapping
MOD GCELLOSPMAP: IDTYPE=BYID, CELLID=2, OPC=H'000B00;
//Adding PTP BVCs for a cell
ADD PTPBVC: NSEI=1, BVCI=11, IDTYPE=BYID, CELLID=2;
//Disabling RAN Sharing for a BTS
SET BTSSHARING: IDTYPE=BYID, BTSID=0, SHARINGALLOW=NO;
//Disabling RAN Sharing
SET BSCBASIC: SptRanSharing=NO;

GBSS14.0
Feature Activation Guide 156 Configuring MOCN Shared Cell
MOCN Shared Cell.
Prerequisites
– The features GBFD-117401 MSC Pool and GBFD-119701 SGSN Pool have been
– GBFD-118701 RAN Sharing is mutually exclusive with the MOCN Shared Cell feature.
– GBFD-117501 Enhanced Measurement Report (EMR) is mutually exclusive with the
MOCN Shared Cell feature.
– The single-user dynamic measurement function in the GBFD-117002 IBCA
(Interference Based Channel Allocation) feature is mutually exclusive with the
neighboring cell filtering function in the MOCN Shared Cell feature.
l License
– If MS routing is determined by the CN, the list of VLRs in which an MS is allowed to
roam needs to be configured on the HLR, or the list of LAIs in which an MS is allowed
to roam needs to be configured on the MSC server.
– Operator have enabled the features MSC Pool and SGSN Pool in their networks.
– MSCs or SGSNs that belong to different operators are configured with different
Network Resource Indication (NRI) values with the same length.
– It is recommended that CNs of different operators use the same transmission over the
A or Gb interface to connect the shared BSC.
– The Abis transmission bandwidth is shared by all operators in a network with MOCN
Shared Cell enabled.

GBSS14.0
– To resolve the incorrect network name display on MSs, MSs support the Network
Identity and Time Zone (NITZ) feature.
– The equivalent PLMN function is recommended on the CN side. In scenarios where an
MOCN cell is adjacent to a private cell, if these two cells correspond to different
PLMNs, enabling the equivalent PLMN function prevents subscribers from periodically
reselecting to the PLMN corresponding to the private cell after these subscribers access
the MOCN cell and therefore reduces the power consumption of the MS.
Context
The BSS sharing function enables multiple operators to share BSS equipment on a per BTS basis
while using their respective core network (CN) equipment. With this feature, different operators
cannot share the same cell.
The MOCN shared cell function, however, enables multiple operators to share BSS equipment
on a per cell basis while using their respective CN equipment.

Remarks (Configuration
Parameter Principle for Different Data
Name Parameter ID Scenarios) Source
MOCN Switch MocnCtrl If this parameter is set to CNSEL Engineering

(CN Select), the proportion of design
subscribers distributed in the
network of each operator is
determined by the CN. If this
parameter is set to BSCSEL
(BSC Select), the proportion of
subscribers distributed in the
network of each operator is
determined by the BSC.
Routing Sharing Srac N/A Engineering

Area Code design
Routing Sharing SracDscrpt N/A Engineering

Area Description design
Location Area LaOpIndex N/A Engineering

Record Index design
MCC MCC N/A Radio

network
planning
(Negotiated
with the peer
end)

GBSS14.0
MNC MNC You are advised to set this Radio

parameter to a new public land network
mobile network (PLMN) planning
identifier. (Negotiated
Currently, only one PLMN with the peer
identifier can be broadcast in a end)
GSM cell. If the PLMN
identifiers for two operators are
25001 and 25002 respectively,
the PLMN identifier to be
broadcast in a shared GSM
network with MOCN Shared
Cell enabled can either be the
new one (for example, 25003) or
an old one (25001 or 25002).
Whether to use the new PLMN
identifier depends on whether
the forbidden PLMN list
EFFPLMN is available in the
SIM cards of served subscribers.
If the forbidden PLMN list is
available in SIM cards of
subscribers served by an
operator and the PLMN
identifier of the other operator is
contained in the list, the new
PLMN identifier must be used.
For example, if 25002 is
contained in the forbidden
PLMN list in the SIM cards of
the operator whose PLMN
identifier is 25001, 25002 must
not be used as the new PLMN
identifier to be broadcast.
Otherwise, MSs that use the
PLMN identifier 25001 cannot
access any service because they
will never register with PLMNs
whose identifier is 25002.
Cell LAC LAC N/A Radio

network
planning
(Negotiated
with the peer
end)

GBSS14.0
Operator Name 1 OPNAME1 N/A BSC internal

planning

planning

planning
Routing Sharing SraLaMapIndex N/A Engineering

Area Record design
Index
MOCN Sharing MocnCmCell Set this parameter to YES(Yes). Radio

Cell network
planning
(Negotiated
with the peer
end)
IMSI Segment ImsiGrpIndex N/A Engineering

Index design
Description of the ImsiGrpDscrpt N/A Engineering

IMSI segment design
Start IMSI value ImsiMin N/A Engineering

design
End IMSI value ImsiMax N/A Engineering

design
Subscriber UsrCatIndex N/A Engineering

Category Index design
Rate of Operator 1 OpShare1 N/A Radio

network
planning
(Negotiated
with the peer
end)

network
planning
(Negotiated
with the peer
end)

GBSS14.0

network
planning
(Negotiated
with the peer
end)
IMSI Category ImsiMapIndex N/A Engineering

Index design
Handover Sharing SHAC N/A Engineering

Area design
Operator Name OPNAME N/A Radio

network
planning
(Negotiated
with the peer
end)
Handover Sharing SHACDscrpt N/A Engineering

Area Description design
Handover Sharing ShaIndex N/A Engineering

Area Record design
Index
Ignore LAC IgnorLac N/A Radio

network
planning
(Negotiated
with the peer
end)
Filter CS Based CSScnIdHoFilter Recommended value: YES Engineering

on Operator (Yes) design
Neighboring Cell
List
Filter PS Based on PSScnIdHoFilter Recommended value: NO(No) Engineering

Operator design
Neighboring Cell
List
Re-Routing ReDirectOpt N/A Engineering

Occasion design

GBSS14.0
Re-Route Cause CauseVal This parameter is carried by the Engineering

Value Location Updating Reject, design
Routing Area Updating Reject,
and Attach Reject messages as
defined in 3GPP TS 24008.
Re-Route Cause CauseRkIdx N/A Engineering

Value Index design
Add Frequency PMOAddFreqAllow Set this parameter to OFF(Off). Radio

Using PMO network
planning
(Negotiated
with the peer
end)
N(U) in Attach ModifyAttReqNu The N(U) value needs to be Radio

Request modified for rerouting an Attach network
Request message. The value of planning
this parameter is determined by (Negotiated
the SGSN connected to the BSC. with the peer
If the N(U) value in an Attach end)
Request message does not need
to be modified, set this
parameter to 512.
Setting this parameter to 512
means that the N(U) value in an
Attach Request message cannot
be modified.
Procedure
1. Configure the BSC data by referring to BSC6900 GSM Initial Configuration Guide.
a. When configuring operator information for the BSC, all BSC-shared secondary
operators must be configured. The MSC Pool and SGSN Pool features must be
enabled.
b. When configuring destination signaling points (DSPs), all DSPs of the BSC must
be configured.
c. In IP transmission mode, when configuring M3UA destination entities, all
M3UA destination entities of the BSC must be configured.
d. When configuring the A and Gb interfaces, the A and Gb interface data for all
operators must be configured. It is recommended that CNs of different operators
use the same transmission over the A or Gb interface to connect the shared BSC.
When configuring CN nodes, all CN nodes used by each operator must be
configured.

GBSS14.0

center: 3.17 Modifying GBSC Parameters in Batches). In this step, set MOCN
Switch to CNSEL(CN Select) or BSCSEL(BSC Select).
3. Run the BSC6900 MML command ADD SRA (CME single configuration: GSM
Global Configuration Express > BSC Basic Configuration > Routing Sharing
Area; CME batch modification center: not supported). In this step, set Routing
Sharing Area Code and Routing Sharing Area Description to appropriate values.
4. Run the BSC6900 MML command ADD LAOPMAP (CME single configuration:
GSM Global Configuration Express > BSC Basic Configuration > LA-Operators
Mapping; CME batch modification center: not supported) to add the mapping
between LAs and operators. In this step, set Location Area Record Index, MCC,
MNC, Cell LAC, Operator Name 1, Operator Name 2, and Operator Name 3 to
appropriate values.
NOTE
The names of all the operators that share BSS equipment must be configured.
5. Run the BSC6900 MML command ADD SRALAMAP (CME single configuration:
GSM Global Configuration Express > BSC Basic Configuration > SRA-LA
Mapping; CME batch modification center: not supported) to add the mapping
between shared routing areas and LAs. In this step, set Routing Sharing Area Record
Index, Routing Sharing Area Code, MCC, MNC, and LAC to appropriate values.
6. Configure the BTS data. For details about how to configure the BTS data, see BSC6900
GSM Initial Configuration Guide.
When configuring the data for a shared cell, set MOCN Shared Cell to YES(Yes),
configure PLMN and LAC information as planned, and configure PTP BVCs from
the cell to all operators that share the cell.
7. Run the BSC6900 MML command ADD IMSIGRP (CME single configuration:
GSM Global Configuration Express > BSC Basic Configuration > Subscriber
IMSI Segment; CME batch modification center: not supported) to add an IMSI
segment. In this step, set IMSI Segment Index, Description of the IMSI segment,
Start IMSI value, and End IMSI value to appropriate values.
8. Run the BSC6900 MML command ADD USRCAT (CME single configuration: GSM
Global Configuration Express > BSC Basic Configuration > Subscriber route
category; CME batch modification center: not supported) to add a subscriber route
category. In this step, set Subscriber Category Index, Operator Name 1, Rate of
Operator 1, Operator Name 2, Rate of Operator 2, Operator Name 3, and Rate
of Operator 3 to appropriate values.
9. Run the BSC6900 MML command ADD IMSISRAMAP (CME single configuration:
GSM Global Configuration Express > BSC Basic Configuration > Routing
category of an IMSI segment; CME batch modification center: not supported) to add
the routing category of an IMSI segment. In this step, set IMSI Category Index,
Routing Sharing Area Code, IMSI Segment Index, and Subscriber Category
Index to appropriate values.
10. Run the BSC6900 MML command ADD SHA (CME single configuration: GSM
Global Configuration Express > BSC Basic Configuration > Handover Sharing
Area; CME batch modification center: not supported) to add a shared handover area.
In this step, set Handover Sharing Area, Operator Name, and Handover Sharing
Area Description to appropriate values.

GBSS14.0
11. Run the BSC6900 MML command ADD SHALAMAP (CME single configuration:
GSM Global Configuration Express > BSC Basic Configuration > Mapping
Between Handover Sharing Area and Location Area; CME batch modification
center: not supported) to add the mapping between shared handover areas and the LAs.
In this step, set Handover Sharing Area Record Index, Handover Sharing Area,
MCC, MNC, Cell LAC, and Ignore LAC to appropriate values.
center: 3.17 Modifying GBSC Parameters in Batches) to configure parameters for
neighboring cell filtering based on inter-operator handover and the rerouting occasion
parameter. In this step, set Filter CS Based on Operator Neighboring Cell List,
Filter PS Based on Operator Neighboring Cell List, and Re-Routing Occasion to
appropriate values.
13. Run the BSC6900 MML command ADD RDRTCAUSE (CME single configuration:
GSM Global Configuration Express > BSC Basic Configuration > Re-Route
Cause; CME batch modification center: not supported) to add a rerouting cause. In
this step, set Re-Route Cause Value, Re-Route Cause Value Index to appropriate
values.
Modifying GBSC Parameters in Batches) with Add Frequency Using PMO set to
an appropriate value.
center: 3.17 Modifying GBSC Parameters in Batches) with N(U) in Attach
Request set to an appropriate value.
l Verification Procedure (CS Services)
1. On the BSC LMT, click the Trace tab.
2. In the displayed Trace Navigation Tree, choose Trace > GSM Services. Double-
click Single User CS Trace.
3. In this displayed Single User CS Trace dialog box, set Trace Object Symbol
Type to IMSI and Trace Interface Type to A Interface. Then, click Submit.
The CS message tracing for a single subscriber function requires subscribers' data,
such as IMSI. This function provides an anonymous data processing method. For
details, see section Tracing CS Domain Messages of a Single Subscriber in BSC6900
GSM LMT User Guide. You are advised to comply with local laws when executing
the task and take ample measures to fully protect subscribers' personal data, such as
setting User Identity Anonymity Switch to ON(On) and deleting the folder that saves
tracing records after you finish processing data.
4. In a shared cell, use a dual-roaming MS to access the network and perform CS services.
5. View the traced single-subscriber CS messages for this MS.
Expected result:
The dual-roaming MS accesses the network of an operator according to the routing

rules of MOCN Shared Cell. Location update-related signaling is traced in the single-
subscriber CS message tracing for this operator.

GBSS14.0
The following is an example:
MOCN Shared Cell is used by operators A and B. The percentage of routing of

operator 1 is 30%, and that of operator 2 is 70%.
If the value for the last two digits of the dual-roaming MS IMSI is less than 30, location
update-related signaling is traced in the single-subscriber CS message tracing for
operator A.
If the value for the last two digits of the dual-roaming MS IMSI is greater than or
equal to 30, location update-related signaling is traced in the single-subscriber CS
message tracing for operator B.
l Verification Procedure (PS Services)
1. On the BSC LMT, click the Trace tab.
2. In the displayed Trace Navigation Tree, choose Trace > GSM Services. Double-
click Single User PS Trace.
3. In this displayed Single User PS Trace dialog box, set Trace Object Symbol
Type to IMSI and Trace Interface Type to Gb Interface. Then, click Submit.
The PS message tracing for a single subscriber function requires subscribers' personal
data, such as IMSI. This function provides an anonymous data processing method.
For details, see section Tracing PS Domain Messages of a Single Subscriber in
BSC6900 GSM LMT User Guide. You are advised to comply with local laws when
executing the task and take ample measures to fully protect subscribers' personal data,
such as setting User Identity Anonymity Switch to ON(On) and deleting the folder
that saves tracing records after you finish processing data.
4. In a shared cell, use a dual-roaming MS to access the network and perform PS services.
5. View the traced single-subscriber PS messages for this MS.
Expected result:
The dual-roaming MS accesses the network of an operator according to the routing

rules of MOCN Shared Cell. Access-related signaling of this MS is traced in the single-
subscriber PS message tracing for this operator.
The following is an example:
MOCN Shared Cell is used by operators A and B. The percentage of routing of

operator 1 is 30%, and that of operator 2 is 70%.
If the value for the last two digits of the dual-roaming MS IMSI is less than 30, access-
related signaling of this MS is traced in the single-subscriber PS message tracing for
operator A.
If the value for the last two digits of the dual-roaming MS IMSI is greater than or
equal to 30, access-related signaling of this MS is traced in the single-subscriber PS
message tracing for operator B.
center: 3.17 Modifying GBSC Parameters in Batches). In this step, set MOCN
Switch to CLOSE(Close), Filter CS Based on Operator Neighboring Cell List and

GBSS14.0
Filter PS Based on Operator Neighboring Cell List to NO(No), Re-Routing

Occasion to NOTREDIR(Not Redirect).
center: 3.17 Modifying GBSC Parameters in Batches) to modify PLMN and LAC
information. In this step, set MOCN Sharing Cell to NO(No).
3. Run the BSC6900 MML command RMV PTPBVC (CME single configuration: Gb
center: not supported) to delete PTP BVCs from the shared cell to all secondary
operators.
4. Run the BSC6900 MML command RMV SRALAMAP (CME single configuration:
GSM Global Configuration Express > BSC Basic Configuration > SRA-LA
Mapping; CME batch modification center: not supported) to remove the mapping
between shared RAs and the LAs.
5. Run the BSC6900 MML command RMV LAOPMAP (CME single configuration:
GSM Global Configuration Express > BSC Basic Configuration > LA-Operators
Mapping; CME batch modification center: not supported) to remove the mapping
between LAs and operators.
6. Run the BSC6900 MML command RMV SRA (CME single configuration: GSM
Global Configuration Express > BSC Basic Configuration > Routing Sharing
Area; CME batch modification center: not supported) to remove the shared RA.
7. Run the BSC6900 MML command RMV IMSISRAMAP (CME single
Routing category of an IMSI segment; CME batch modification center: not
supported) to remove the routing category of the IMSI segment.
8. Run the BSC6900 MML command RMV IMSIGRP (CME single configuration:
IMSI Segment; CME batch modification center: not supported) to remove the
subscriber IMSI segment.
9. Run the BSC6900 MML command RMV USRCAT (CME single configuration:
route category; CME batch modification center: not supported) to remove the
subscriber route category.
10. Run the BSC6900 MML command RMV SHALAMAP (CME single configuration:
center: not supported) to remove the mapping between shared handover areas and
LAs.
11. Run the BSC6900 MML command RMV SHA (CME single configuration: GSM
Area; CME batch modification center: not supported) to remove the shared handover
area.
12. Run the BSC6900 MML command RMV RDRTCAUSE (CME single configuration:
GSM Global Configuration Express > BSC Basic Configuration > Re-Route
Cause; CME batch modification center: not supported) to remove the rerouting cause.

GBSS14.0
Modifying GBSC Parameters in Batches) with Add Frequency Using PMO set to
OFF(Off).
center: 3.17 Modifying GBSC Parameters in Batches) with N(U) in Attach
Request set to its original value.
15. Delete the initially configured BSC data such as secondary operators, DSPs, M3UA
determination entities, CN nodes, and A and Gb interface data.
----End
Example
/*Activating MOCN Shared Cell*/
//Enabling the MOCN control switch on the BSC side
SET OTHSOFTPARA: MocnCtrl=CNSEL;
//Adding a shared RA
ADD SRA: Srac=0, SracDscrpt="Srac 0";
//Adding the mapping between LAs and operators
ADD LAOPMAP: LaOpIndex=0, MCC="460", MNC="30", LAC=h'3030,
OPNAME1="OperatorA", OPNAME2="OperatorB";
ADD LAOPMAP: LaOpIndex=1, MCC="460", MNC="30", LAC=h'3040,
OPNAME1="OperatorA", OPNAME2="OperatorB";
//Adding the mapping between shared RAs and the LAs
ADD SRALAMAP: SraLaMapIndex=0, Srac=0, MCC="460", MNC="30", LAC=h'3030;
ADD SRALAMAP: SraLaMapIndex=1, Srac=0, MCC="460", MNC="30", LAC=h'3040;
//Adding an IMSI segment
ADD IMSIGRP: ImsiGrpIndex=0, ImsiGrpDscrpt="ImsiGrp1",
ImsiMin="460101234000000", ImsiMax="460101234999999";
ADD IMSIGRP: ImsiGrpIndex=1, ImsiGrpDscrpt="ImsiGrp2",
ImsiMin="460205678000000", ImsiMax="460205678999999";
//Adding a subscriber route category
ADD USRCAT: UsrCatIndex=0, OPNAME1="OperatorA", OpShare1=70,
OPNAME2="OperatorB", OpShare2=30;
ADD USRCAT: UsrCatIndex=1, OPNAME1="OperatorA", OpShare1=40,
OPNAME2="OperatorB", OpShare2=60;
//Adding the routing category of an IMSI segment
ADD IMSISRAMAP: ImsiMapIndex=0, Srac=0, ImsiGrpIndex=1, UsrCatIndex=1;
ADD IMSISRAMAP: ImsiMapIndex=1, Srac=0, ImsiGrpIndex=0, UsrCatIndex=0;
//Adding a shared handover area
ADD SHA: SHAC=0, OPNAME="OperatorA", SHACDscrpt="OperatorA Share Ho
Area";
ADD SHA: SHAC=1, OPNAME="OperatorB", SHACDscrpt="OperatorB Share Ho
Area";
//Adding the mapping between shared handover areas and LAs
ADD SHALAMAP: ShaIndex=0, SHAC=0, MCC="460", MNC="30", LAC=h'3030,
IgnorLac=NO;
ADD SHALAMAP: ShaIndex=1, SHAC=1, MCC="460", MNC="30", LAC=h'3040,
IgnorLac=NO;
//Configuring parameters for neighboring cell filtering based on inter-
operator handover and the rerouting occasion parameter
SET OTHSOFTPARA: CSScnIdHoFilter=YES, PSScnIdHoFilter=NO,
ReDirectOpt=ALL;
//Adding a rerouting cause
ADD RDRTCAUSE: CauseVal=17, CauseRkIdx=0;
//Configuring the Add Frequency Using PMO switch
SET BSCPSSOFTPARA: PMOAddFreqAllow=OFF;
//Modifying the N(U) value in an Attach Request message
SET OTHSOFTPARA: ModifyAttReqNu =512;

GBSS14.0
/*Deactivating MOCN Shared Cell*/

//Disabling the MOCN control switch on the BSC side
SET OTHSOFTPARA: MocnCtrl=CLOSE, ReDirectOpt=NOTREDIR,
CSScnIdHoFilter=NO,
PSScnIdHoFilter=NO;
//Disabling the MOCN control switch on the cell side
MOD GCELL: IDTYPE=BYID, CELLID=0, MCC=460, MNC=20, LAC= H'1214,
MocnCmCell=NO;
MOD GCELL: IDTYPE=BYID, CELLID=1, MCC=460, MNC=20, LAC= H'1214,
MocnCmCell=NO;
//Removing PTP BVCs from the shared cell to all secondary operators
//Removing the mapping between shared RAs and the LAs
RMV SRALAMAP: SraLaMapIndex=0;
RMV SRALAMAP: SraLaMapIndex=1;
//Removing the mapping between LAs and operators
RMV LAOPMAP: LaOpIndex=0;
RMV LAOPMAP: LaOpIndex=1;
//Removing the shared RA
RMV SRA: Srac=0;
//Removing the routing category of the IMSI segment
RMV IMSISRAMAP: ImsiMapIndex=0;
RMV IMSISRAMAP: ImsiMapIndex=1;
//Removing the IMSI segment
RMV IMSIGRP: ImsiGrpIndex=0;
RMV IMSIGRP: ImsiGrpIndex=1;
//Removing the subscriber route category
RMV USRCAT: UsrCatIndex=0;
RMV USRCAT: UsrCatIndex=1;
//Removing the mapping between shared handover areas and LAs
RMV SHALAMAP: ShaIndex=0;
RMV SHALAMAP: ShaIndex=1;
//Removing the shared handover area
RMV SHA: SHAC=0;
RMV SHA: SHAC=1;
//Removing the rerouting cause
RMV RDRTCAUSE: CauseVal=0;
//Disabling the Add Frequency Using PMO switch
SET BSCPSSOFTPARA: PMOAddFreqAllow=OFF;
//Modifying the N(U) value in an Attach Request message
SET OTHSOFTPARA: ModifyAttReqNu =512;

GBSS14.0
Feature Activation Guide 157 Configuring IMSI-Based Handover
157 Configuring IMSI-Based Handover
IMSI-Based Handover.
Prerequisites
– A test MS (MS1) is available and its IMSI is recorded.
l License
l Others
– The Common Id and Handover Request messages sent by the MSC need to carry IMSI.
– A BTS is configured with two test cells (CELL1 and CELL2) of the same operator.
These cells are in the normal state and support the GPRS function.
– Idle channels are available in CELL1. CELL1 and CELL2 are neighboring cells of each
other. The two cells are in different location areas.
Context
According to the network planning and service requirements, an operator can divide the network
into multiple areas (called handover shared areas) and restrict the service area of an MS by
configuring the mapping between the IMSI range and the handover shared area.
Procedure
center: 3.17 Modifying GBSC Parameters in Batches). In this step, set IMSI
Handover Switch to YES(Yes).

GBSS14.0
2. Run the BSC6900 MML command ADD IMSIGRP (CME single configuration:
IMSI Segment; CME batch modification center: not supported) to add an IMSI
segment. In this step, set IMSI Segment Index, Description of the IMSI segment,
Start IMSI value, and End IMSI value according to the actual situation (assume that
IMSI of MS1 is within the configured IMSI segment).
3. Run the BSC6900 MML command ADD SHA (CME single configuration: GSM
Area; CME batch modification center: not supported) to add a handover shared area.
In this step, set Handover Sharing Area, Operator Name, and Handover Sharing
Area Description according to the actual situation (assume that Operator Name is
the name of the operator of CELL1).
4. Run the BSC6900 MML command ADD SHALAMAP (CME single configuration:
center: not supported) to configure the mapping between a handover shared area and
a location area. In this step, set Handover Sharing Area Record Index, Handover
Sharing Area, MCC, MNC, and Cell LAC according to the actual situation (assume
that MCC, MNC, and Cell LAC are those of CELL2).
5. Run the BSC6900 MML command ADD IMSISHAMAP (CME single
IMSI Support Handover Area; CME batch modification center: not supported) to
add an IMSI-supported handover area. In this step, set IMSI Index of Handover
Sharing Area Record, Handover Sharing Area, and IMSI Segment Index
according to the settings specified in Step 2 and Step 3.
l Verification Procedure (CS Services)
1. MS1 camps on CELL1 to call a fixed-line phone. The call is set up successfully.
2. Run the BSC6900 MML command ADD G2GNCELL. In this step, set Index
Type (Not required on the CME) to BYID(By index), Source Cell Index to the index
of CELL1, and Neighbor 2G Cell Index to the index of CELL2.
3. Run the BSC6900 MML command SET FHO. In this step, set Object Type to CELL
(Cell), Handover Scope to OUTCELL(Outgoing cell), and Cell Index or Cell
Name to the index or name of CELL1.
4. On the LMT, start the message tracing over the Abis interface by referring to Tracing
CS Domain Messages on the Abis Interface. Select RSL in the Trace Type area.
5. On the RSL tab page, set Cell ID(cell1,cell2,...cell16) to those of CELL1 and CELL2.
Then, click Submit. The Abis Interface CS Trace message interface is displayed.
Run steps 1 through 5 to enable the MS to perform a handover from CELL1 to CELL2.
Expected result:
– If idle channels are unavailable in CELL2, the CS tracing messages on the Abis
interface of CELL1 indicate that handover cannot be performed and measurement
reports are reported continuously.
– If an idle channel is available in CELL2, the CS tracing messages on the Abis
interface of CELL2 indicate that the incoming internal inter-cell handover
procedure for MS1 is performed properly and measurement reports are reported
normally.
l Verification Procedure (PS Services)

GBSS14.0
1. MS1 camps on CELL1 and processes PS services.

2. On the LMT, start the PS message tracing for a single user by referring to Tracing PS
Domain Messages of a Single Subscriber. Set IMSI to the IMSI of MS1.
3. Run the BSC6900 MML command SET GCELLGPRS. In this step, set Cell
Index or Cell Name to the index or name of CELL1; set GPRS to SupportAsInnPcu
(Support as built-in PCU) and Support NC2 to YES(Yes).
4. Run the BSC6900 MML command SET GCELLPSBASE. In this step, set Cell
Index or Cell Name to the index or name of CELL1; set Network Operation
Mode to NC2(NC2).
5. Run the BSC6900 MML command ADD G2GNCELL. In this step, set Index
Type (Not required on the CME) to BYID(By index), Source Cell Index to the index
of CELL1, and Neighbor 2G Cell Index to the index of CELL2.
6. Run the BSC6900 MML command SET GCELLNC2PARA. In this step, set Cell
Index or Cell Name to the index or name of CELL1; set Cell Urgent Reselection
Allowed to PERMIT(Permit) and MS Rx Quality Statistic Threshold to 2.
7. Move the MS to a location where CELL2 has better coverage than CELL1. Then,
check the PS tracing messages of MS1.
Expected result: The signaling procedure for cell reselection of the MS from CELL1
to CELL2 is displayed.
center: 3.17 Modifying GBSC Parameters in Batches). In this step, set IMSI
Handover Switch to NO(No).
----End
Example
//Turning on the IMSI-based handover switch
SET OTHSOFTPARA: ImsiHoCtrl=YES;
//Adding a subscriber IMSI segment
ADD IMSIGRP: ImsiGrpIndex=0, ImsiGrpDscrpt="IMSI",
ImsiMin="460000000000000", ImsiMax="460100000000000";
//Adding a handover sharing area
ADD SHA: SHAC=1, OPNAME="OP1", SHACDscrpt="Share1";
//Configuring mapping between a handover sharing area and a location area
ADD SHALAMAP: ShaIndex=0, SHAC=1, MCC="460", MNC="133", LAC=H'1234;
//Adding an IMSI-supported handover area
ADD IMSISHAMAP: ImsiShaMapIndex=0, SHAC=1, ImsiGrpIndex=0;
//Turning off the IMSI-based handover switch
SET OTHSOFTPARA: ImsiHoCtrl=NO;

GBSS14.0
Feature Activation Guide 158 Configuring Abis Independent Transmission
158 Configuring Abis Independent

Transmission
Abis Independent Transmission.
Prerequisites
– The feature GBFD-118701 BSS Sharing has been configured before this feature is
activated.
l License
Context
In a BSS sharing network, multiple telecom operators share a base station and associated
auxiliary devices. Cells of different telecom operators can reside under one base station, but each
cell can only belong to one telecom operator.
The transmission resources under the base station can be shared among telecom operators or
exclusively used by their respective telecom operators. In Abis over TDM mode, transmission
resources can be configured independently based on only the level of an E1 port. In Abis over
IP mode, transmission resources can be configured independently based on only the level of
logical resources.
Procedure
l Activation Procedure (TDM Transmission)
supported) to deactivate the target BTS.
2. Run the BSC6900 MML command SET BTSSHARING (CME single configuration:
BTS Configuration Express > BTS Basic Attributes > BTS RAN Sharing

GBSS14.0
Parameters; CME batch modification center: not supported) to enable independent

transmission over the Abis interface for the BTS. In this step, set Sharing Allow to
YES(YES) and Transmission Sharing Support to NO(NO).
3. Run the BSC6900 MML command ADD BTSCONNECT (CME single
configuration: BTS Topology > Right click BTS > Chain Management > Add
Chain; CME batch modification center: not supported) to add the connection between
the BTS and the BSC. In this step, set Dest Node Type (select Connect to BSC on
the CME) to BSC, set Operator Name to the name of the operator that the BTS
belongs, and set other parameters to appropriate values.
NOTE
If multiple operators share one BTS or if there are multiple BTSs, run Step 3 repeatedly to add the
connection between each BTS and the BSC for each operator.
4. Run the BSC6900 MML command SET BTSIDLETS (CME single configuration:
BTS Topology > Right click BTS > Timeslot Management > Idle Timeslot; CME
batch modification center: not supported). In this step, set Index Type (Not required
on the CME) to BYID(By Index), set BTS Index (Not required on the CME) and
Cabinet Group No. to appropriate values, set Operator Name to the name of the
operator that the BTS belongs, and set Idle TS Count to the number of idle timeslots
for the operator.
NOTE
If multiple operators share the idle timeslots on an E1 cable, run Step 4 repeatedly to set the number
of idle timeslots for each operator.
l Activation Procedure (IP Transmission)
Parameters; CME batch modification center: not supported) to enable independent
transmission over the Abis interface for the BTS. In this step, set Sharing Allow to
YES(YES) and Transmission Sharing Support to NO(NO).
3. Run the BSC6900 MML command ADD OPSEPINFO (CME single configuration:
GSM Global Configuration Express > Transmission Resources Configuration >
Separate Information for Operators; CME batch modification center: not
supported). In this step, set Index of Separate Information for Operators and the
Count of the Operators Selected, set Transport Type to IP(IP), and set The type
of operator to GSM(GSM). Then, based on the field configuration and number of
operators, set Index of 1st Operator, Bandwidth Ratio of 1st Operator, Load
Threshold of 1st Operator, Index of 2nd Operator, Bandwidth Ratio of 2nd
Operator, Load Threshold of 2nd Operator, Index of 3rd Operator, Bandwidth
Ratio of 3rd Operator, Load Threshold of 3rd Operator, Index of 4th
Operator, Bandwidth Ratio of 4th Operator and Load Threshold of 4th
Operator to appropriate values.
NOTE
The sum of bandwidth ratio of all the operators must be 100%.

GBSS14.0
4. Run the BSC6900 MML command ADD IPLOGICPORT (CME single

configuration: (G)IURG Configuration Express > IP Transport > IP Logical
Port; CME batch modification center: not supported). In this step, set Resource
Management Mode to SHARE, Operator Separated Flag to ON(ON), and
Operator Separated Index to the value set in Step 3. In addition, set the parameter
related to an IP logical port in this step.
1. Run the BSC6900 MML command LST IPLOGICPORT to query Operator
Separated Index.
2. Run the BSC6900 MML command LST OPSEPINFO to query the number of
operators and operator index. In this step, set Index of Separate Information for
Operators to the value displayed in Step 1.
3. Run the BSC6900 MML command DSP IPLOGICPORT to query the realtime
bandwidth of an IP logical port. In this step, set Subrack No., Slot No., and Logic
Port No. to appropriate values.
Expected result: The realtime bandwidth of the IP logical port is displayed. Assume
that the realtime bandwidth is A.
4. Run the BSC6900 MML command DSP IPLOGICPORT to query the realtime
bandwidth of an IP logical port of a specified operator. In this step, set Subrack
No., Slot No., Logic Port No., The type of operator, and CN Operator index to
appropriate values.
Expected result: Assume that two operators share an IP logical port for independent
transmission over the Abis interface. The realtime bandwidth of operators 1 and 2 is
X1 and X2 respectively. Then, X1 + X2 ≤ A.
6. Run the BSC6900 MML command SET BTSSHARING to enable transmission over
the Abis interface for a BTS. In this step, set Sharing Allow to YES(YES) and
Transmission Sharing Support to YES(Yes).
8. Repeat Step 4.
Expected result: A message is displayed, indicating that the information fails to be
queried.
l Deactivation Procedure (TDM Transmission)
Parameters; CME batch modification center: not supported) to disable transmission
sharing for the BTS. In this step, set Sharing Allow to YES(YES) and Transmission
Sharing Support to YES(Yes).
3. Run the BSC6900 MML command MOD BTSCONNECT (CME single
Chain; CME batch modification center: not supported). In this step, set Operator

GBSS14.0
Name to the name of the primary operator and set other parameters to appropriate
values.
batch modification center: not supported) to set the number of idle timeslots for the
secondary operator to 0. In this step, set Idle TS Count to 0 and Operator Name to
the name of the secondary operator.
NOTE
If there are multiple secondary operators, run Step 4 repeatedly to release the idle timeslots for all
secondary operators.
batch modification center: not supported) to return all idle timeslots to the primary
operator. In this step, set Idle TS Count to the number of idle timeslots that the primary
operator have and Operator Name to the name of the primary operator.
l Deactivation Procedure (IP Transmission)
Parameters; CME batch modification center: not supported) to disable transmission
sharing for the BTS. In this step, set Sharing Allow to YES(YES) and Transmission
Sharing Support to YES(Yes).
3. Run the BSC6900 MML command MOD IPLOGICPORT (CME single
configuration: (G)IURG Configuration Express > IP Transport > IP Logical
Port; CME batch modification center: not supported). In this step, set Operator
Separated Flag to OFF(OFF).
----End
Example
/*Activation procedure (TDM transmission)*/
//DEA BTS: IDTYPE=BYID, BTSID=0;
//Enabling independent transmission over the Abis interface
//SET BTSSHARING: IDTYPE=BYID, BTSID=0, SHARINGALLOW=YES, SptTRMShare=NO;
//Adding a connection between BTS and BSC
//ADD BTSCONNECT: IDTYPE=BYID, BTSID=0, INPN=1, DESTNODE=BSC, SRN=1,
SN=14, PN=0, OPNAME="op1";
//Setting idle timeslots of the BTS
//SET BTSIDLETS: IDTYPE=BYID, BTSID=0, CGN=1, TSCOUNT=20, OPNAME="op1";
//ACT BTS: IDTYPE=BYID, BTSID=0;
/*Activation procedure (IP transmission)*/

GBSS14.0
//Enabling independent transmission over the Abis interface
//SET BTSSHARING: IDTYPE=BYID, BTSID=0, SHARINGALLOW=YES, SptTRMShare=NO;
//Configuring operator separation parameters
//ADD OPSEPINFO: OPSEPINDEX=0, OPCOUNT=TWO, TYPE=IP, OPTYPE=GSM,
OPINDEX1=1, BWRATIO1=30, OPINDEX2=2, BWRATIO2=70;
//Configuring an IP logical port
//ADD IPLOGICPORT: SRN=0, SN=10, BT=GOUa, LPN=0, CARRYT=ETHER, PN=0,
RSCMNGMODE=SHARE, BWADJ=OFF, CIR=1, FLOWCTRLSWITCH=ON, OPSEPFLAG=ON,
OPSEPINDEX=0;
/*Deactivation procedure (TDM transmission)*/

//Disabling independent transmission over the Abis interface
//SET BTSSHARING: IDTYPE=BYID, BTSID=0, SHARINGALLOW=YES,
SptTRMShare=YES;
//Modifying the connection of the BTS to the primary operator
MOD BTSCONNECT: IDTYPE=BYID, BTSID=0, INPN=1, DESTNODE=BSC, SRN=1, SN=14,
PN=0, OPNAME="OP1";
//Setting the number of idle timeslots for the secondary operator to 0
//Returning all idle timeslots to the primary operator
/*Deactivation procedure (IP transmission)*/

//Disabling independent transmission over the Abis interface
//SET BTSSHARING: IDTYPE=BYID, BTSID=0, SHARINGALLOW=YES,
SptTRMShare=YES;
//Turing off the operator separation switch
//MOD IPLOGICPORT: SRN=0, SN=10, BT=GOUa, LPN=0, OPSEPFLAG=OFF;

GBSS14.0 159 Configuring PICO/Compact BTS Automatic
Feature Activation Guide Configuration and Planning
159 Configuring PICO/Compact BTS

Automatic Configuration and Planning
PICO Automatic Configuration and Planning and GBFD-510701 Compact BTS Automatic
Configuration and Planning. (This feature cannot be configured using the CME. )
Prerequisites
– Only the BTS3900B and BTS3900E support this feature.
l License
– The matching version of the M2000 is available.
– The initial parameters required for BTS automatic planning algorithm are set in online
mode through the M2000 client.
– Automatic frequency optimization tasks are created by using the M2000.
Context
l The compact BTS refers to the BTS3900E. If the feature is applied to the BTS3900E, a
maximum of two carriers can be configured and the cells of the BTS3900E are configured
in O2 mode.
l The PICO refers to the BTS3900B.
l After being installed and powered on, the BTS3900B and BTS3900E automatically connect
to the BSC with the network automatic detection feature. Operators do not need to configure
radio parameters for cells. The M2000 obtains radio parameters based on frequency bands
and scanning results of the uplink and downlink level of surrounding frequencies reported
from the BTS, and then performs the automatic configuration and planning of the
BTS39000B and BTS3900E. This feature can be applied in newly deployed or swapped

sites. By using this feature, site deployment duration is decreased and operator intervention
is reduced. As a result, OM costs are reduced.
l Before the automatic planning, the following parameters used for the planning algorithm
must be configured in advance on the M2000 client: operator frequency data, BTS
adjacency information, BSIC data, and CGI resource data. You can view the progress and
result of the BTS GSM automatic planning and perform data analysis and fault location on
the M2000 client. For details, see the M2000 Product Documentation.
l If the BSC version is V900R012 or later, the BSC supports the automatic configuration
and automatic planning of 128 BTS3900Es or BTS3900Bs in parallel mode, and the M2000
supports the automatic configuration and automatic planning of 512 BTS3900Es or
BTS3900Bs in parallel mode.
l In the BSC version is V900R014 or later, the M2000 determines the location where a BTS
in automatic planning mode is installed, avoiding using the BTS in a location that the
operator does not allow.
Procedure
1. Run the BSC6900 MML command ADD BTSAUTOPLAN to establish the BTS in
automatic planning mode. The established BTS is enabled with the automatic planning
feature by default. The automatic planning algorithm switch and automatic
optimization algorithm switch are set to ON.
NOTE
l The established BTS that is in automatic planning mode enables the automatic planning
feature automatically when it is powered on for the first time. If the first automatic planning
scan succeeds, the BTS does not enable the automatic planning feature automatically after
the BTS is powered off again or reset. If the site data needs to be planned again, run the
BSC6900 MML command RST AUTOPLAN.
l To enable this feature on a BTS that is configured as a common BTS on the BSC6900, run
the BSC6900 MML command SET BTSAUTOPLANCFG, and then set BTS
Configuration Mode to AUTO.
l For the BTS3900E, set BTS Type to BTS3900E_GSM(BTS3900E GSM), and set
Freq. and BSIC Plan Switch and Freq. and BSIC Optimize Switch to ON(ON).
Then, run the BSC6900 MML command RST AUTOPLAN to plan the site data
automatically.
l For the BTS3900B, set BTS Type to BTS3900B_GSM(BTS3900B GSM), and set
Freq. and BSIC Plan Switch, CGI and RAC Plan Switch, and Neighbor Cell Plan
Switch to ON(ON). Then, run the BSC6900 MML command RST AUTOPLAN to
plan the site data automatically.
2. Optional: Run the BSC6900 MML command SET BTSAUTOPLANCFG to enable
the location control function for a BTS in automatic planning mode. In this step, set
Relocation Restricted to ON(ON).

CAUTION
l If the CGIs of all neighboring cells under the BTS are changed, run the BSC6900
MML command RST AUTOPLAN to restart auto planning for the BTS. In this
step. set Relocation Allowed During Replanning to YES(YES). Otherwise, the
M2000 determines that the BTS location is changed because all neighboring cells
under this BTS are changed, causing an automatic planning failure.
l If a BTS in automatic planning mode is relocated to an area with neighboring cells
from an area without neighboring cells, the M2000 fails to determine the BTS
location. However, the BTS can access the network properly during automatic
planning.
l If a BTS in automatic planning mode is relocated to an area without neighboring
cells from an area with neighboring cells, run the BSC6900 MML command RST
AUTOPLAN to restart auto planning for the BTS. In this step. set Relocation
Allowed During Replanning to YES(YES). Otherwise, the M2000 determines
that the BTS location is changed because all neighboring cells under this BTS are
changed, causing an automatic planning failure.

1. Run the BSC6900 MML command LST BTSAUTOPLANCFG to check whether
BTS Configuration Mode is set to ON(ON).
2. Optional: If the location control function for a BTS in automatic planning mode is
required, run the BSC6900 MML command LST BTSAUTOPLANCFG to check
whether Relocation Restricted is set to ON(ON).
1. Run the BSC6900 MML command SET BTSAUTOPLANCFG. In this step, set
BTS Configuration Mode to NORMAL(NORMAL).
CAUTION
1. After BTS Configuration Mode is set to NORMAL(NORMAL), all the
automatic planning and automatic optimization switches are deactivated.
2. The deactivation of the feature during the automatic planning will result in the reset
of the BTS.
2. Optional: If the location control function for a BTS in automatic planning mode is
not required, run the BSC6900 MML command SET BTSAUTOPLANCFG. In this
step, set Relocation Restricted to OFF(OFF).
----End
Example
//Step 1 Add a BTS in auto-planning mode. The added BTS is enabled with
the auto-planning function by default. The auto-planning algorithm switch
and auto-optimization algorithm switch are set to ON.
ADD BTSAUTOPLAN: BTSNAME="btsname01", BTSTYPE=BTS3900B_GSM, DESTNODE=BSC,

SRN=0, SN=26, PN=0, SERVICEMODE=IP, BTSIP="10.161.30.2",

BTSMASK="255.255.255.0", BSCIP="10.161.10.1", MAINDEVTAB="tab01",
SRANMODE=NOT_SUPPORT, CELLNAME="cellname01", TYPE=DCS1800, MAXFQNUM=1,
CLKPRTTYPE=HW_DEFINED, MASTERIPADDR="139.139.139.1";
SET BTSAUTOPLANCFG: IDTYPE=BYNAME, BTSNAME="btsname01", CFGMODE=AUTO,
BTSTYPE=BTS3900B_GSM, CGIRACSWITCH=ON, FQBSICSWITCH=ON, NBRCELLSWITCH=ON,
FQBSICOPTSWITCH=ON;
//Step 2 Activate the BTS.
//(Optional) Enabling the location control function for a BTS in automatic
planning mode
BTSTYPE= BTS3900B_GSM, POSITIONRESTRICTSWITCH=ON;
LST BTSAUTOPLANCFG: IDTYPE=BYNAME, BTSNAME="btsname01";
///Disabling automatic configuration and planning
SET BTSAUTOPLANCFG: IDTYPE=BYNAME, BTSNAME="btsname01", CFGMODE=NORMAL;
//(Optional) Disabling the location control function for a BTS in
automatic planning mode
BTSTYPE= BTS3900B_GSM, POSITIONRESTRICTSWITCH=OFF;

GBSS14.0
Feature Activation Guide 160 Configuring PICO Synchronization
160 Configuring PICO Synchronization
PICO Synchronization.
Prerequisites
– Neighboring cells of the BTS3900B are available and the neighboring relations are
configured.
– This feature is supported by only the BTS3900B.
l License
Context
l In the GSM network, the 13 MHz frequency synchronization is mandatory among multiple
BTSs to maintain the network QoS, such as the MS handover success rate. The clock
synchronization function of the BTS3900B implements the Um frequency synchronization
with the neighboring macro BTSs through software. The output synchronization clock is
13 MHz.
l After the feature is activated, you do not need to configure a clock server for the BTS3900B.
Procedure
modification center: 3.18 Modifying GBTS Parameters in Batches), and then set
Clock Type to UM_CLK(Um Clock).

GBSS14.0
Feature Activation Guide 160 Configuring PICO Synchronization
1. Run the BSC6900 MML command LST BTSCLK to check whether the correct clock
source is configured.
Expected result: Clock Type is UM_CLK(Um Clock).
2. Run the BSC6900 MML command DSP BTSATTR to check whether the clock
source is available.
Expected result: Clock attribute is Available.
modification center: 3.18 Modifying GBTS Parameters in Batches), and then set
Clock Type to INT_CLK(Internal Clock).
----End
Example
SET BTSCLK: IDTYPE=BYID, BTSID=0, ClkType=UM_CLK;
LST BTSCLK: IDTYPE=BYID, BTSID=0, LstFormat=VERTICAL;
DSP BTSATTR: OBJTP=SITE, IDTYPE=BYID, BTSID=0, SITEATTR=OPSTAT&CLKATTR;

GBSS14.0
Feature Activation Guide 161 Configuring PICO Dual-band Auto-planning
161 Configuring PICO Dual-band Auto-

planning
PICO Dual-band Auto-planning. (This feature cannot be configured using the CME. )
Prerequisites
– None
l License
– The M2000 supports the PICO Dual-band Auto-planning feature.
Context
l The PICO Dual-band Auto-planning feature is license-controlled.
l The Pico is also called the BTS3900B. Pico auto-planning indicates that the BTS3900B
scans the uplink and downlink frequencies of operators according to the frequency band
capability of the BTS3900B. The M2000 evaluates the interference condition of each
frequency according to the scanning result. In addition, considering the neighboring
relationship of the BTS3900B, the M2000 selects the frequency with the minimum
interference as the frequency of the BTS3900B. PICO Dual-band Auto-planning supports
the 900 MHz/1800 MHz and 850 MHz/1900 MHz dual-band scenarios on the basis of the
original single-band auto-planning function. PICO auto-planning helps operators to
implement fast network deployment and flexible network adjustment and reduce the
workload of manual configuration.
l Before the auto-planning, the following parameters used for the planning algorithm should
be set in advance on the M2000 client: operator frequency data, BTS neighboring relations,
BSIC data, and CGI resource data. You can view the progress and result of the BTS3900B

GBSS14.0
GSM auto-planning and perform data analysis and fault location on the M2000 client. For
details, see the M2000 Product Documentation.
l The auto-planning function is mostly used in the site setup scenario. During the execution
of the auto-planning function, the services within the network coverage of the BTS3900B
are disrupted.
Procedure
1. Run the BSC6900 MML command ADD BTSAUTOPLAN to add the auto-planning
BTS3900B, and set Is Support SingleRAN Mode to SUPPORT(Support). The
added BTS3900B is enabled with the auto-planning function by default. In addition,
the auto-planning algorithm switch and auto-optimization algorithm switch are set to
ON, and the Frequency Band Adaptation Allowed switch is set to NO(NO) by
default.
NOTE
l The added BTS3900B that is in auto-planning mode will enable the auto-planning function
automatically when it is powered on for the first time. If the first auto-planning scan
succeeds, the BTS3900B does not enable the auto-planning function automatically during
the subsequent powering-off and resetting operations. If the auto-planning function needs
to be enabled again, Run the BSC6900 MML command RST AUTOPLAN.
l To enable this feature on a BTS that is configured as a common BTS on the BSC6900,
Run the BSC6900 MML command SET BTSAUTOPLANCFG, and set BTS
Configuration Mode to AUTO(AUTOPLAN). Then, set the related auto-planning
algorithm switch, auto-optimization algorithm switch and Frequency Band Adaptation
Allowed switch according to the actual conditions. Then, Run the BSC6900 MML
command RST AUTOPLAN to plan the site data automatically. The Frequency Band
Adaptation Allowed switch has impacts on the auto-planning result. Operators can
determine whether to enable the switch according to the actual conditions. For details, see
the following note.
l Operators can select appropriate planning modes to perform auto-planning according to
the actual conditions. The BTS3900B supports the following planning modes:
l If the BTS3900B is configured with one or two TRXs in band A, the Frequency Band
Adaptation Allowed switch is invalid. The M2000 plans the BTS3900B as the O1 or
O2 site in band A according to the number of configured TRXs.
l If the BTS3900B is configured with two TRXs and the two TRXs are in band A and
band B respectively, the BTS3900B will scan the frequencies of band A and band B.
The frequency bands and site types of the frequencies planned by the BTS3900B,
however, vary with the status of the Frequency Band Adaptation Allowed switch.
a. Frequency Band Adaptation Allowed is set to YES(YES):
The M2000 selects the frequency with the minimum interference as the working
frequency according to the reported scanning results of the two frequencies. The
frequency band where the frequency exists is the working frequency band of the
BTS3900B. The M2000 plans the BTS3900B as the O1 site in corresponding frequency
bands
b. Frequency Band Adaptation Allowed is set to NO(NO):
The M2000 plans the BTS3900B as the O2 site in dual-band. The M2000 selects the
BCCH frequencies in low frequency bands (such as 900 MHz or 850 MHz) and selects
the TCH frequencies in low frequency bands or high frequency bands.
1. Run the BSC6900 MML command LST BTSAUTOPLANCFG aand check that
BTS Configuration Mode is set to AUTO(AUTOPLAN).

GBSS14.0
1. Run the BSC6900 MML command SET BTSAUTOPLANCFG, and then set BTS
Configuration Mode to NORMAL(NORMAL).
CAUTION
The deactivation operation during the execution of the auto-planning function will result
in the reset of the BTS3900B.
----End
Example
ADD BTSAUTOPLAN: BTSNAME="pico", BTSTYPE=BTS3900B_GSM, DESTNODE=BSC,
BTSMASK="255.255.255.0", BSCIP="18.18.18.18",
MAINDEVTAB="2102311045AB09000005", SRANMODE=SUPPORT, CELLNAME="gsm",
TYPE=GSM900_DCS1800, MAXFQNUM=2, MASTERIPADDR="18.18.18.254";
SET BTSAUTOPLANCFG: IDTYPE=BYID, BTSID=0, CFGMODE=AUTO,
BTSTYPE=BTS3900B_GSM, FREQSELFADAPT=YES;
LST BTSAUTOPLANCFG: IDTYPE=BYNAME, BTSNAME="pico";
SET BTSAUTOPLANCFG: IDTYPE=BYNAME, BTSNAME="pico", CFGMODE=NORMAL;

GBSS14.0
Feature Activation Guide 162 Configuring PICO USB Encryption
162 Configuring PICO USB Encryption
PICO USB Encryption.
Prerequisites
– Only BTS3900B supports this feature.
– None
l License
– The M2000 version supports the USB security protection tool.
Context
l A PICO BTS is also named BTS3900B.
l When a newly deployed BTS3900B is locally commissioned by using a USB flash drive,
the configuration file is stored in the USB flash drive as plain text. This file contains
important configuration information, such as the IP addresses of network elements. If the
information is saved as plain text, it may be stolen or disclosed.
l When the PICO USB Encryption feature is introduced, the configuration file is encrypted
by using an encryption software on the M2000 side and then is decrypted on the BTS side,
ensuring information security.
Procedure
1. Copy the configuration file DataCfg.xml to the PC where the M2000 client is installed
and save the DataCfg.xml file in the D:\USB\GBTS3900B\Config\DataCfg.xml
directory.

GBSS14.0
Feature Activation Guide 162 Configuring PICO USB Encryption
NOTE
The USB security protection tool does not support file decryption. Therefore, the file must be
backed up before being encrypted.
2. Choose Start > All Programs > iManager M2000 Client > Start USB Protector
Tool. The USB Protector Tool dialog box is displayed.
3. Choose Setting > Set USB Root Directory, select D:\USB, and click OK.
4. Choose Setting > Set Security Policies. The Set Security Policies dialog box is
displayed.
a. Set Save Path to D:\USB\GBTS3900B.
b. Set Encryption Algorithm and Integrity Algorithm based on your individual
needs.
c. Click OK.
5. Choose File > Open, and select the DataCfg.xml file in the D:\USB\GBTS3900B
\Config directory.
6. Select IsEncrypted:Index.
NOTE
In the file list area, if IsEncrypted:Index before a file is selected, the file is encrypted.
Otherwise, only integrity protection is performed on the file.
7. Click Execute Protect.
8. Delete the source file in the USB flash drive and copy the GBTS3900B folder to the
root directory of the USB flash drive.
1. Open the DataCfg.xml file in the D:\USB\GBTS3900B\Config directory.
If garbled characters are displayed, the file is encrypted successfully.
2. Connect the USB flash drive to the BTS3900B.
The BTS3900B sets up links properly.
N/A
----End

GBSS14.0
Feature Activation Guide 163 Configuring PICO Sleeping Mode
163 Configuring PICO Sleeping Mode
PICO Sleeping Mode.
Prerequisites
– Currently, the BTS3900B and BTS3900E support the sleeping mode feature.
l License
– The M2000 supports the PICO Sleeping Mode feature.
Context
l The PICO refers to the BTS3900B. The PICO Sleeping Mode feature helps to save the site
energy by enabling or disabling the cells in a period. When the BTS3900B is used at night
when the traffic is unavailable in the scenarios, such as offices, warehouses, and exhibition
halls, users can specify the period for enabling or disabling the PICO cells, such as, 00:00
to 6:00 am. In this period, the power amplifiers of all the carriers (including BCCH carriers)
in the cells are shut down.
l When the PICO Sleeping Mode feature takes effect, the PICO cells do not provide radio
network services.
Procedure
GSM Cell Parameters in Batches), and then set Enable Turning Off Cell to
SLEEPING(Sleeping) and set Dyn. Turning Off Cell Start Time and Dyn. Turning
Off Cell Stop Time.

GBSS14.0
Feature Activation Guide 163 Configuring PICO Sleeping Mode
NOTE
When Enable Turning Off Cell is set to SLEEPING(Sleeping), the BSC6900 disables the
cell within the disabling period unconditionally and enables the cell within the enabling period
unconditionally. Currently, the Enable Turning Off Cell parameter of only the BTS3900B
and BTS3900E can be set to SLEEPING(Sleeping).
1. Run the BSC6900 MML command SET GCELLDYNTURNOFF, and then set Cell
Index to the index of the cell to be verified and Enable Turning Off Cell to
SLEEPING(Sleeping), and set Dyn. Turning Off Cell Start Time and Dyn.
Turning Off Cell Stop Time to ensure that the current time is within the period
specified by the two parameters.
2. Wait for about five minutes and Run the BSC6900 MML command DSP
GCELLSTAT, and then set Cell Attribute to DYNSWITCH(Dynamic Switch) to
check the current status of the cell. If Cell Dynamic Switch of the verified cell is set
to Yes, it indicates that the PICO Sleeping Mode feature is effective.
3. Run the BSC6900 MML command SET GCELLDYNTURNOFF, and then set Cell
Index to the index of the cell to be verified and Enable Turning Off Cell to
SLEEPING(Sleeping), and set Dyn. Turning Off Cell Start Time and Dyn.
Turning Off Cell Stop Time to ensure that the current time is beyond the period
specified by the two parameters.
4. Wait for about one minute and Run the BSC6900 MML command DSP
GCELLSTAT, and then set Cell Attribute to DYNSWITCH(Dynamic Switch) to
check the current status of the cell. If Cell Dynamic Switch of the verified cell is set
to No, it indicates that the cell is enabled.
GSM Cell Parameters in Batches), and then set Enable Turning Off Cell to
DISABLE(Disable).
----End
Example
SET GCELLDYNTURNOFF: IDTYPE=BYID, CELLID=0, TURNOFFENABLE=SLEEPING,
TURNOFFCELLSTRTIME=10&00, TURNOFFCELLSTPTIME=12&00;
SET GCELLDYNTURNOFF: IDTYPE=BYID, CELLID=0, TURNOFFENABLE=DISABLE;

GBSS14.0
Feature Activation Guide 164 Configuring PICO Automatic Optimization
164 Configuring PICO Automatic

Optimization
PICO Automatic Optimization. (This feature cannot be configured using the CME. )
Prerequisites
l License
– The M2000 supports the PICO Automatic Optimization feature.
Context
l The PICO Automatic Optimization feature is license-controlled.
l The Pico is also called the BTS3900B. During the operation of the BTS3900B, the
automatic optimization task is created on the M2000 and the BTS3900Bs to be optimized
and the counter thresholds are specified. When the working frequencies are severely
interfered, the M2000 triggers the BTS3900B to restart the uplink and downlink frequency
scan. In addition, the M2000 selects the working frequency with the minimum interference
for the BTS3900B through the automatic optimization algorithm. Through automatic
optimization of working frequencies, the BTS3900B can shield itself from the frequencies
that are severely interfered. In this case, the communication quality within the coverage of
the BTS3900B and the KPIs are improved significantly. In addition, the handover success
rate of the MS in the coverage of the BTS3900B is increased and the call drop rate is
reduced.
l The progress and result of the PICO Automatic Optimization feature can be viewed on the
M2000 client for data analysis and fault location. For details, see the M2000 Product
Documentation.

GBSS14.0
Feature Activation Guide 164 Configuring PICO Automatic Optimization
Procedure
Configuration Mode to AUTO(AUTOPLAN), BTS Type to BTS3900B_GSM
(BTS3900BGSM), and Freq. and BSIC Optimize Switch to ON(ON). Then, set the
related auto-planning algorithm switch and auto-optimization algorithm switch
according to the actual conditions.
1. Run the BSC6900 MML command LST BTSAUTOPLANCFG and check that Freq.
and BSIC Optimize Switch is set to ON.
1. Run the BSC6900 MML command SET BTSAUTOPLANCFG, and then set Freq.
and BSIC Optimize Switch to OFF(OFF).
----End
Example
BTSTYPE=BTS3900B_GSM, FQBSICOPTSWITCH=ON;
LST BTSAUTOPLANCFG: IDTYPE=BYID, BTSID=10;
BTSTYPE=BTS3900B_GSM, FQBSICOPTSWITCH=OFF;

GBSS14.0
Feature Activation Guide 165 Configuring PICO Transceiver Redundancy
165 Configuring PICO Transceiver

Redundancy
PICO Transceiver Redundancy.
Prerequisites
– Two radio frequency (RF) cards for transceiver redundancy must be work on the same
frequency band.
l License
– The BTS3900B configured with two TRXs does not support this feature.
– TRX switchovers are not allowed within five minutes after a BTS3900B is started
successfully.
– When a BTS3900B is interconnected to a Distributed Antenna System (DAS), the
antenna of the DAS must be connected to the transmitting port of another antenna system
for the BTS3900B before a TRX switchover is triggered.
Context
l This feature enables the standby RF card of a BTS3900B configured with a single TRX to
take over the services of the active RF card when the active RF card is faulty, preventing
service disruption.
l PICO Transceiver Redundancy can be applied in the following scenarios:
– No traffic is available on a BTS3900B for a long time.

GBSS14.0
– MSs fail to access the network.

– Voice quality is poor.
– The RF Unit TX Channel Gain Out of Range alarm (alarm ID: 26520) and RF Unit
Clock Problem alarm (alarm ID: 26538) are generated on a BTS3900B.
– RF cards are faulty.
Users can switch over TRXs to the standby RF card to restore services or improve service
quality.
CAUTION
A TRX switchover will lead to service interruption for less than three minutes.
Procedure
1. Run the BSC6900 MML command SET BTSTRXBACKUP (CME single
configuration: BTS Configuration Express > BTS Extend Attributes > BTS TRX
Backup Parameters; CME batch modification center: not supported), and then set
TRX Backup Switch to ON(ON).
NOTE
This feature is disabled by default for a BTS3900B before delivery.
CAUTION
After PICO Transceiver Redundancy is enabled, adding TRXs dynamically is not
allowed.
– Verify TRX backup switch status.
1. Click Trace on the LMT interface, and then double-click Abis Interface CS Trace.
In the displayed Abis Interface CS Trace dialog box, set Trace Mode to OML. Then,
click Submit. The TRX backup status is displayed in Set Site Extend Attribute2
Ack.
– Verify TRX switchover status.
NOTE
Assume that TRX 0 is switched over from RF card 0 to RF card 1.
1. Click Device Maintenance on the LMT interface. The Device Maintenance dialog
box is displayed.
2. Click BSC under Device Navigation Tree, and then select the corresponding BTS.
Then, observe the TRX status before the switchover on the right of BTS Device
Panel. TRX 0 is configured on RF card 0, as shown in Figure 165-1.

GBSS14.0
Figure 165-1 TRX switchover status before switchover
3. Run the BSC6900 MML command SWP GTRX to switch over TRX.
4. Click Device Maintenance on the LMT interface. The Device Maintenance dialog
box is displayed.
5. Click BSC in Device Navigation Tree, and then select the corresponding BTS. Then,
observe the TRX status after the switchover on the right of BTS Device Panel. TRX
0 is switched over to RF card 1, as shown in Figure 165-2.
Figure 165-2 TRX switchover status after switchover
NOTE
If another switchover is performed, the TRX switchover status is restored to the status shown in
Figure 165-1.
1. Run the BSC6900 MML command SET BTSTRXBACKUP (CME single
configuration: BTS Configuration Express > BTS Extend Attributes > BTS TRX
Backup Parameters; CME batch modification center: not supported), and then set
TRX Backup Switch to OFF(OFF).

GBSS14.0
CAUTION
If a TRX switchover is performed on a BTS3900B, the BTS3900B will reset
automatically when TRX Backup Switch is set to OFF(OFF).
----End
Example
SET BTSTRXBACKUP: IDTYPE=BYID, BTSID=1, TRXBPSW=ON;
SWP GTRX: IDTYPE=BYID, BTSID=1;
SET BTSTRXBACKUP: IDTYPE=BYID, BTSID=1, TRXBPSW=OFF;

GBSS14.0
Feature Activation Guide 166 Configuring Weather Adaptive Power Management
166 Configuring Weather Adaptive

Power Management
This section describes how to manage a GBTS weather-adaptive energy conservation task on
the M2000. You can perform operations such creating, modifying, starting, deleting, and viewing
a task. After you create such a task and then start it on the M2000, the M2000 predicts the quantity
of electricity to be generated on GBTS solar panels based on weather data, and then periodically
generates power levels available to the GBTSs based on various types of information such as
generated electricity, remaining electricity of batteries, and GBTS power consumption.
Prerequisites
– Only BTS3900E supports this feature.
l License
– History weather data of the corresponding district is available.
– The third-party system for uploading weather data properly communicates with the
M2000 through FTP.
Procedure
1. Choose Maintenance > Energy Power-Saving Management > GBTS Weather
Adaptive Energy Management. The GBTS Weather Adaptive Energy
Management window is displayed.
2. Import history weather data.
a. Click on the toolbar. The District History Weather Setting dialog box is
displayed.

GBSS14.0
b. Click Export Template or select a district in the navigation tree, and then click
Export. In the displayed dialog box, select a type of monthly average radiant
intensity of the horizontal plane, specify a save path on your local computer, and
then click OK.
c. Type history weather data to the weather data table that is already exported, and
then change the name of the table to the name of the district for which history
data is to be imported.
d. In the District History Weather Setting dialog box, click Import.
After the data is imported, the name of the district corresponding to the weather
data table is displayed in the navigation tree of the District History Weather
Setting dialog box.
CAUTION
If the name of the imported table is the same as that of an existing table in the
M2000 system, this table replaces the existing one.
e. Click Close.
3. Manage a GBTS weather-adaptive energy conservation task.
Perform operations as required in the GBTS Weather Adaptive Energy
Management dialog box.
View a task All created GBTS weather-adaptive energy conservation tasks are
displayed in the task list.
l Status displays the current running status of a GBTS weather-
adaptive energy conservation task.
l Information displays the result of the last execution of a task.
NOTE
The M2000 executes the energy conservation algorithm once an hour.
Double-click a task to be viewed in the task list, or select a task and
then click . The Property dialog box is displayed, in which you

can view parameters related to the task.

GBSS14.0
Create a task
1. Click . The New Task dialog box is displayed.
2. Select a GBTS from the NE navigation tree, and then set task
parameters in the right pane.
You can create only one weather-adaptive energy conservation
task for each GBTS.
3. Click OK.
You can view the new task in the task list.
NOTE
A task is in stopped state by default after it is created, and therefore you need
to manually start it.
Start a task Select a task whose Status is Stopped from the task list, and then
click .
NOTE
A task is in stopped state by default after it is created, and therefore you need
to manually start it.
Modify a task 1. Select a task whose Status is Stopped from the task list, or click
to stop a task.
2. Double-click a task, or click and then modify task parameters

in the Property dialog box.
3. Click OK.
Delete a task Select a task whose Status is Stopped from the task list or click
to stop a task, and then click .
1. Select a task, and then click to view the execution report of the task in the
displayed web page.
The execution report of a task contains task execution records and basic task
information such as related GBTS, district, and weather conditions.
N/A
----End

GBSS14.0
Feature Activation Guide 167 Configuring Compact BTS Automatic Capacity Planning
167 Configuring Compact BTS

Automatic Capacity Planning
Compact BTS Automatic Capacity Planning. (This feature cannot be configured using the
CME. )
Prerequisites
– This feature is supported by only the Compact BTS.
– None
l License
– The initial parameters required for BTS auto-planning algorithm are set in online mode
through the M2000 client.
– Before this feature is configured, the BTS has performed automatic configuration and
planning.
– The automatic optimization task of the GSM BTS is created on the M2000 client before
the feature is activated. For details, see the M2000 Product Documentation.
Context
l The Compact BTS Automatic Capacity Planning feature is license-controlled.
l The compact BTS refers to BTS3900E.
l According to the traffic volume, the BSC adjusts the output power of the TRX in real time
to achieve the balance between capacity and coverage of the network. A cell is initially
configured with one TRX of 30 W power. With the increase of the traffic volume, another
TRX in the cell is automatically activated, and thus these two TRXs share the 30 W power.

GBSS14.0
Feature Activation Guide 167 Configuring Compact BTS Automatic Capacity Planning
NOTE
After the feature is activated, the M2000 measures the traffic volume of the BTS within 24 hours, and then
compares the measurement result with the threshold of the actual traffic volume. If the traffic volume of the
BTS exceeds the threshold, the BTS adds a TRX automatically for expansion.
Procedure
Configuration Mode to AUTO, BTS Type to BTS3900E_GSM, and Capacity and
Coverage Optimize Switch to ON(ON).
1. Run the BSC6900 MML command LST BTSAUTOPLANCFG, and then check that
Capacity and Coverage Optimize Switch is set to ON.
1. Run the BSC6900 MML command SET BTSAUTOPLANCFG, and then set
Capacity and Coverage Optimize Switch to OFF(OFF).
----End
Example
SET BTSAUTOPLANCFG: IDTYPE=BYNAME, BTSNAME="pico", CFGMODE=AUTO,
BTSTYPE=BTS3900E_GSM, CAPCOVEROPTSWITCH=ON;
// Verification procedure
LST BTSAUTOPLANCFG: IDTYPE=BYID, BTSID=0, LSTFORMAT=VERTICAL;
SET BTSAUTOPLANCFG: IDTYPE=BYNAME, BTSNAME="pico", CFGMODE=AUTO,
BTSTYPE=BTS3900E_GSM, CAPCOVEROPTSWITCH=OFF;

GBSS14.0 168 Configuring Compact BTS Automatic Neighbor Cell
Feature Activation Guide Planning and Optimization
168 Configuring Compact BTS

Automatic Neighbor Cell Planning and
Optimization
Compact BTS Automatic Neighbor Cell Planning and Optimization. (This feature cannot be
configured using the CME. )
Prerequisites
– This feature is supported by only the BTS3900E.
l License
– The scanning frequency set and neighbor cell list are configured on the M2000 in
advance.
– The parameters related to automatic optimization are set on the M2000 in advance.
Context
l The Compact BTS Automatic Neighbor Cell Planning and Optimization feature is license-
controlled.
l The compact BTS refers to BTS3900E.
l Automatic Neighbor Cell Planning
– The automatic neighboring cell planning feature is mostly applied in the site deployment
scenario.
– The automatic neighboring cell planning feature indicates that the M2000 triggers the
BTS3900E to perform downlink frequency scan. The BTS3900E reports the
information about the neighboring cells to the M2000. Then, the M2000 configures the

scanned cells as the neighboring cells of the BTS3900E. In addition, the M2000 adds
the cells of the BTS3900E in the scanned cells to the neighboring cell list to set up the
bidirectional neighboring relation. If the scanned cells are beyond the serving area of
the M2000, the M2000 can set up only the unidirectional neighboring relation and
prompt users to manually configure neighboring cells.
l Automatic Neighbor Cell Optimization
– The automatic neighbor cell optimization feature is used during the operation of the
BTS.
– During the operation of the BTS3900E, the automatic optimization task is created on
the M2000. With this feature, the M2000 determines that redundant neighboring cells
exist in the BTS3900E or certain neighboring cells are missed according to the analysis
of the measurement reports. Then, the M2000 triggers the neighbor cell optimization
process automatically and updates the neighboring relation.
l The Automatic Neighbor Cell Planning and Optimization feature can improve network
quality, increase handover success rate, and reduce call drop rate automatically, reducing
the workload of manual configuration and improving OM efficiency.
l The progress and result of the automatic planning and optimization can be viewed on the
M2000 client for data analysis and fault location. For details, see the M2000 Product
Documentation.
Procedure
l Procedure for activating Automatic Neighbor Cell Planning
1. Run the BSC6900 MML command ADD BTSAUTOPLAN to add the BTS3900E in
auto-planning mode. The added BTS3900E is enabled with the auto-planning function
by default. In addition, the related auto-planning algorithm switch and auto-
optimization algorithm switch supported by the BTS3900E are set to ON. You can
Run the BSC6900 MML command SET BTSAUTOPLANCFG to modify the status
of the switches.
NOTE
l The added BTS3900E that is in auto-planning mode will enable the auto-planning function
automatically when it is powered on for the first time. If the first auto-planning scan
succeeds, the BTS3900E does not enable the auto-planning function automatically during
the subsequent powering-off and resetting operations. If the auto-planning function needs
to be enabled again, Run the BSC6900 MML command RST AUTOPLAN.
l To enable this feature on a BTS that is configured as a common BTS on the BSC6900,
Run the BSC6900 MML command SET BTSAUTOPLANCFG, and set BTS
Configuration Mode to AUTO(AUTOPLAN). Then, set Neighbor Cell Plan Switch to
ON(ON). Then, Run the BSC6900 MML command RST AUTOPLAN command to plan
the site data automatically.
l Procedure for activating Automatic Neighbor Cell Optimization
Configuration Mode to AUTO(AUTOPLAN), BTS Type to BTS3900E_GSM,
and set Neighbor Cell Optimize Switch to ON(ON).
1. Run the BSC6900 MML command LST BTSAUTOPLANCFG, and then check that
Neighbor Cell Plan Switch and Neighbor Cell Optimize Switch are set to ON.

Configuration Mode to NORMAL(NORMAL).
----End
Example
ADD BTSAUTOPLAN: BTSNAME="micro", BTSTYPE=BTS3900E_GSM, DESTNODE=BSC,
BTSMASK="255.255.255.0", BSCIP="18.18.18.18",
MAINDEVTAB="11112222223333334444", SRANMODE=SUPPORT,
CELLNAME="micro_cell0",
TYPE=DCS1800, MCC="460", MNC="111", LAC=1214, CI=1000,
MASTERIPADDR="18.18.18.254";
ACT BTS: IDTYPE=BYNAME, BTSNAME="micro", CELLNAMELIST="micro_cell0",
SET BTSAUTOPLANCFG: IDTYPE=BYNAME, BTSNAME="micro", CFGMODE=AUTO,
BTSTYPE=BTS3900E_GSM, NBRCELLSWITCH=ON, NBRCELLOPTSWITCH=ON;
LST BTSAUTOPLANCFG: IDTYPE=BYNAME, BTSNAME="micro";
SET BTSAUTOPLANCFG: IDTYPE=BYNAME, BTSNAME="micro", CFGMODE=NORMAL;

GBSS14.0
Feature Activation Guide 169 Configuring Compact BTS Timing Power Off
169 Configuring Compact BTS Timing

Power Off
Compact BTS Timing Power Off. (This feature cannot be configured using the CME. )
Prerequisites
– The solar controller is connected to the BTS.
– Currently, only the BTS3900E supports the Compact BTS Timing Power Off feature.
l License
– The version the solar controller should not be earlier than POWER2000 V1R1C04.
– The time of the solar controller is consistent with that of the BTS3900E.
Context
l The compact BTS is the BTS3900E. Within the coverage of the BTS3900E, if the
BTS3900E uses solar boards to supply power, users can set the enabling and disabling time
of the BTS3900E on the BSC when the traffic is unavailable or is light. By using the solar
controller, the BTS3900E can enable or disable automatically in the specified periods,
reducing the power consumption of the site, the number of solar boards, and construction
cost.
l The BTS3900E does not provide services when the Compact BTS Timing Power Off
feature takes effect.
Procedure

GBSS14.0
Feature Activation Guide 169 Configuring Compact BTS Timing Power Off
1. Run the BSC6900 MML command SET BTSAPMUBP, and then set Board
Parameter Configuration Enabled to YES(YES) and BTS Power-off Enabled to
ON(ON), and set Power-off Start Time and Power-off End Time according to the
actual conditions.
NOTE
Run the BSC6900 MML command DSP BTSPWR to query the power information about the
BTS.
1. Run the BSC6900 MML command SET BTSAPMUBP, and then set BTS Index
(Not required on the CME) to the index of the BTS to be verified, Board Parameter
Configuration Enabled to YES(YES), and BTS Power-off Enabled to ON(ON),
and set Power-off Start Time and Power-off End Time according to the verification
time at the site to ensure that the verification time is within the period specified by
Power-off Start Time and Power-off End Time.
2. On the main interface of the LMT, click Alarm. The Alarm tab page is displayed.
3. Double-click OML Fault on the Fault tab page under Browse Alarm. The Alarm
Detailed Information dialog box is displayed.
4. Check Alarm Cause of Location Info, if Alarm Cause is displayed as Green Base
Station Power-off, it indicates that the BTS3900E is powered off.
NOTE
The OML Fault alarm is generated after the BTS is powered off. Thus, check the alarm after Power-off
Start Time.
1. Run the BSC6900 MML command SET BTSAPMUBP, and then set Board
Parameter Configuration Enabled to NO(NO) or set Board Parameter
Configuration Enabled to YES(YES) and BTS Power-off Enabled to OFF
(OFF).
----End
Example
BTSSHUTDNASW=ON, SHUTDNST=16&15&19, SHUTDNET=18&15&34;
BTSSHUTDNASW=OFF;

GBSS14.0
Feature Activation Guide 170 Configuring Local User Management
170 Configuring Local User Management
Local User Management.
Prerequisites
– The BTS3900E is in IP over FE transmission mode.
l License
– The PC installed with the Local User Management software is in normal communication
with the BTS3900E.
Context
l The Local User Management feature is license-controlled.
l Currently, only the BTS3900E supports the Local User Management feature.
l This feature can be used to deploy a special commercial mode. When the BTS3900E is
used in rural areas, operators can contract the BTS3900E to entrepreneurs. The
entrepreneurs manage the local users through a PC and provide the registration and
deregistration services, local services, public network services, and local services in single-
site mode.
– The entrepreneurs gain profits by increasing the number of local users. The
entrepreneurs are responsible for registration and communication charging (including
charging strategies) of local users.
– The transmission in rural areas is unstable. This feature ensures that the local user
management can be performed even if the transmission is disrupted. In addition, the
communication and charging between local users are supported.

GBSS14.0
Feature Activation Guide 170 Configuring Local User Management
– The BTS3900E contracted to the entrepreneurs can also provide services for public
network users of operators. In this case, the communication requirements of public
network users can be ensured when the BSC transmission is disrupted.
l The calls between local users support only full rate.
l When the transmission on the Abis interface is disrupted, the BTS3900E enters the single-
site mode. The handover procedure lasts for six minutes, during which services are
disrupted.
l During the communication between local users, only the reporting of the original
measurement report is supported.
Procedure
Parameters of BTS; CME batch modification center: not supported), and then set
Local Call Support Flag to YES(YES).
– Local services and public network services
1. Run the BSC6900 MML command LST BTSOTHPARA, and then check that local
call support flag is set to YES.
2. Use MSs to perform the service dialing test.
Expected result: The call services between local services, between public network
users, and between local users and public network users are normal.
NOTE
The local signaling process of call services between local users is different from the common call
process. You can observe the signaling information through message tracing on the Web LMT.
– Local services in single-site mode
1. Run the BSC6900 MML command LST BTSOTHPARA, and then check that local
call support flag is set to YES.
2. Disconnect the BTS3900E from the BSC and wait for six minutes. Then, perform the
local service dialing test.
Expected result: The call services between local users are normal.
Parameters of BTS; CME batch modification center: not supported), and then set
Local Call Support Flag to NO(NO).
----End
Example
SET BTSOTHPARA: IDTYPE=BYID, BTSID=10, SPRTLU=YES;
SET BTSOTHPARA: IDTYPE=BYID, BTSID=10, SPRTLU=NO;

GBSS14.0
Feature Activation Guide 171 Configuring Intelligent Battery Management
171 Configuring Intelligent Battery

Management
Intelligent battery management includes the automatic switch between battery management
modes, overtemperature protection, and leftover capacity. This section describes how to activate,
verify, and deactivate the optional feature GBFD-510710 Intelligent Battery Management.
Prerequisites
l License
– BTSs configured with the APM30H(Ver.C), BTS3900AL, and TP48600A cabinets
support this feature.
– This feature does not depend on the transport network.
– This feature does not depend on other NEs or third-party devices.
Context
l Precautions
– None
l Data Preparation

GBSS14.0
Parameter Name Parameter ID Parameter Setting Data Source
Battery Intelligent BATIMS The value of this parameter is Internal planning

Management Switch valid only when The license
controlling this feature has
been activated. For details on
how to activate the license,
see 4 Activating the GSM
License. For details about
license items, see 2 Feature
Activation and License
Item Descriptions.
High Temperature HTSDF l To enable automatic Network plan

Shutdown Flag battery power-off
protection in the
overtemperature
environment, set this
parameter to ENABLE
(ENABLE).
l To decrease the charging
voltage and maintain the
battery backup capability
in the overtemperature
environment, set this
parameter to DISABLE
(DISABLE).
Set this parameter to
ENABLE(ENABLE) in
high-temperature regions.

GBSS14.0
Shutdown SDT This parameter specifies the Network plan

Temperature power-off temperature. The
default value is 53°C. If the
battery operating
temperature has been higher
than the value of this
parameter lasts for 5 minutes,
the power monitoring unit
(PMU) performs one of the
following operations to
protect batteries:
l If HTSDF is set to
ENABLE(ENABLE),
the PMU triggers battery
power-off protection.
l If HTSDF is set to
DISABLE(DISABLE),
the PMU decreases the
battery charging voltage
from the busbar.
Temperature Alarm TUTHD Temperature alarm upper Network plan

Upper Threshold threshold = Float charging
trigger threshold + 5°C If the
battery operating
temperature has been higher
than the float charging
trigger threshold lasts for 5
minutes, equalized charging
is changed to float charging
to protect batteries. The
default value of this
parameter is 50°C.
Procedure
– Activate the automatic switch between battery management modes.
set Battery Intelligent Management Switch to ON(On).
– Activate battery overtemperature protection.
1. Battery overtemperature protection is automatically activated after Battery
Intelligent Management Switch is set to ON(On).

GBSS14.0
NOTE
Run the BSC6900 MML command SET BTSAPMUBP (CME single configuration: BTS
Device Panel > Right click PMU Board > Properties > APMU/PMU(BTS That
Support SingleRAN) Board Parameters; CME batch modification center: not supported)
to set battery overtemperature protection parameters. In this step, set High Temperature
Shutdown Flag to ENABLE(ENABLE), and set Shutdown Temperature and
Temperature Alarm Upper Threshold to appropriate values.
– The battery leftover capacity query function does not need to be activated.
– Verify the automatic switch between battery management modes.
1. Run the BSC6900 MML command DSP BTSPWR to query the BTS power
information.
This function has been activated if Battery Intelligent Management
Capability is Support and Battery Intelligent Management Switch is On.
Otherwise, this function has not been activated.
– Verify battery overtemperature protection.
1. Run the BSC6900 MML command DSP BTSBRD to query battery management
parameters. This function has been activated if the values of High-Temperature
Battery Power-off Allowed State, High-Temperature Battery Power-off
Temperature, and High Cell temperature 1 Alarm are the same as the
configured ones.
– Query the battery leftover capacity.
1. Run the BSC6900 MML command DSP BTSBRD to query the battery leftover
capacity.
Parameters of BTS; CME batch modification center: not supported). In this step, set
Battery Intelligent Management Switch to OFF(Off).
----End
Example
//Activating Intelligent Battery Management
SET BTSOTHPARA: IDTYPE=BYID, BTSID=1, BATIMS=ON;
//Querying BTS Power Information
DSP BTSPWR: INFOTYPE=BTSPWR, IDTYPE=BYID, BTSID=9;
//Querying the BTS Battery Leftover Capacity
DSP BTSBATCAP: IDTYPE=BYID, BTSID=7, SRN=0, SN=15;

GBSS14.0
Feature Activation Guide 172 Configuring PBT
172 Configuring PBT
Power Boost Technology (PBT).
Prerequisites
– DTRU, DRFU, and RRU3004 support this feature.
– When a double-transceiver TRX board uses PBT, only channel 0 is configured with one
carrier.
l License
Context
PBT aims to increase the downlink transmit power to extend network coverage. In PBT mode,
only one carrier is configured for a double-transceiver TRX board. A signal transmitted from
the carrier is modulated and then converted into a radio frequency (RF) signal, known as DA
conversion. Then, the RF signal is transmitted to two power amplifiers (PAs). After being
amplified, the two signals are combined and output. The transmit power is increased because
the two signals are aligned accurately. This increases downlink signal strength. PBT is applicable
to wide coverage areas.
Procedure
in Batches). In this step, set Send Mode to PBT(PBT).
NOTE
In PBT mode, the single carrier must be configured on channel 0.

GBSS14.0
Feature Activation Guide 172 Configuring PBT
1. Optional: Use an MS to make a call.
NOTE
This operation is required if the test TRX does not carry a BCCH carrier. This operation can be
skipped if the test TRX carries a BCCH carrier.
2. Run the BSC6900 MML command SET GTRXDEV. In this step, set Send Mode to
NONE(None). Then, use an optical power meter to measure the power of the test base
station, and record the measurement result.
PBT(PBT).
4. Use the optical power meter to measure the power of the test base station, and record
the measurement result.
5. Compare the measurement result obtained in step 2 with that obtained in step 5.
Expected result: The power measured in step 5 is greater than that measured in step
2. This indicates that PBT has taken effect.
----End
Example
SET GTRXDEV: TRXID=0, SNDMD=PBT;
SET GTRXDEV: TRXID=0, SNDMD=NONE;
SET GTRXDEV: TRXID=0, SNDMD=PBT;

GBSS14.0
Feature Activation Guide 173 Configuring Transmit Diversity
173 Configuring Transmit Diversity
Transmit Diversity (TD).
Prerequisites
– The following base stations support this feature: BTS3006C, BTS3002E, BTS3012
(DTRU), BTS3012AE(DTRU), DBS3900(modules except RRU3926), BTS3900
(DRFU/MRFUd), BTS3900A(DRFU/MRFUd), BTS3900L(DRFU/MRFUd), and
BTS3900AL(DRFU/MRFUd).
– When a double-transceiver TRX board uses TD, only channel 0 is configured with one
carrier.
– The cell where TD is applied has at least one dual-polarized antenna or two single-
polarized antennas.
– This feature is mutually exclusive with the following features: GBFD-113701
Frequency Hopping (baseband hopping), GBFD-113703 Antenna Frequency Hopping
and GBFD-510104 Multi-site Cell.
– This feature is mutually exclusive with the following feature when multi-carrier RRU
dynamic TX diversity is used: GBFD-118106 Dynamic Power Sharing(Dual PA power
sharing)
l License
Context
In TD mode, one baseband signal is transmitted through two radio frequency (RF) channels.
This prevents signal levels from changing dramatically and also prevents signal quality from
dropping since there is no correlation between two antennas. As an effect of this, service quality
for users that move at a low speed is improved and the downlink network coverage is expanded.
To sum up, TD improves the downlink signal quality and meets the requirements of high signal
quality in some special areas.
The following procedure illustrates how to configure TD for the DRRU on a GSM DBS3900.

GBSS14.0
Feature Activation Guide 173 Configuring Transmit Diversity
Procedure
supported). In this step, set DRRU Sending Receiving Mode to
DOUBLE_ANTENNA(Double Feeder[2TX+2RX]).
in Batches). In this step, set Send Mode to DIVERSITY(Transmit Diversity).
NONE(None).
2. Use an optical power meter to measure the power of the test base station, and record
the measurement result.
Expected result: The power is 0.
3. Run the BSC6900 MML command SET BTSRXUBP. In this step, set DRRU
Sending Receiving Mode to DOUBLE_ANTENNA(Double Feeder[2TX+2RX]).
DIVERSITY(Transmit Diversity).
5. Use an optical power meter to measure the power of channel B, and record the
measurement result.
Expected result: The power is not 0, which indicates that TD has taken effect.
----End
Example
RXUTYPE=DRRU, SndRcvMode=DOUBLE_ANTENNA, Lvl1Vswr=22, Lvl2Vswr=30;
SET GTRXDEV: TRXID=0, POWL=8, SNDMD=DIVERSITY;
SET GTRXDEV: TRXID=0, SNDMD=NONE;
RXUTYPE=DRRU, SndRcvMode=DOUBLE_ANTENNA, Lvl1Vswr=22, Lvl2Vswr=30;
SET GTRXDEV: TRXID=0, POWL=8, SNDMD=DIVERSITY;

GBSS14.0
Feature Activation Guide 174 Configuring 4-Way Receiver Diversity
174 Configuring 4-Way Receiver

Diversity
4-Way Receiver Diversity. The 4-way receive diversity combines 4-way receive signals to
optimize the quality of uplink signals.
Prerequisites
(DTRU), BTS3012AE(DTRU), BTS3900(DRFU), BTS3900A(DRFU), BTS3900L
(DRFU), and BTS3900AL(DRFU).
– A DTRU board that adopts the 4-way receive diversity technique can be configured
with only one carrier.
– The cell has two dual-polarized antennas or four single-polarized antennas.
l License
Context
The 4-way receive diversity enables signals from four directions to be transmitted to a single
carrier simultaneously. The carrier then combines these 4-way receive signals to improve uplink
receive sensitivity. In this way, this technique optimizes the quality of uplink signals to meet the
demanding requirements for radio communications in certain cases and to improve the uplink
performance in wide network coverage scenarios.
The following procedures assume that the 4-way receive diversity is configured for two
associated DRFUs of a BTS3900.

GBSS14.0
Feature Activation Guide 174 Configuring 4-Way Receiver Diversity
Procedure
supported). In this step, set DRRU Sending Receiving Mode to
DOUBLEFOUR_ANTENNA(Double Feeder[2TX+4RX]).
NOTE
The two associated DRFUs must be configured simultaneously.

in Batches). In this step, set Receive Mode to FOURDIVERSITY(Four Diversity
Receiver).
NOTE
l If the carrier of a double-transceiver TRX board is configured on channel 0, Receive Mode can
be set to DTIC(Transmit Independency or Combination), PBT(PBT), DIVERSITY
(Transmit Diversity), DDIVERSITY(Dynamic Transmit Diversity), or DPBT(DPBT).
l If the carrier of the double-transceiver TRX board is configured on channel 1, Receive Mode
must be set to DTIC(Transmit Independency or Combination).
1. Run the BSC6900 MML command LST GTRXDEV to query the attributes of the
TRX board.
Expected result: Receive Mode is set to FOURDIVERSITY(Four Diversity
Receiver).
----End
Example
//Activating 4-Way Receiver Diversity
RXUTYPE=DRFU, SndRcvMode1=DOUBLEFOUR_ANTENNA;
RXUTYPE=DRFU, SndRcvMode1=DOUBLEFOUR_ANTENNA;
SET GTRXDEV: TRXID=0, RCVMD=FOURDIVERSITY;
//Verifying 4-Way Receiver Diversity
LST GTRXDEV: IDTYPE=BYID, CELLID=9, TRXID=0;

GBSS14.0
Feature Activation Guide 175 Configuring Dynamic Transmit Diversity
175 Configuring Dynamic Transmit

Diversity
Dynamic Transmit Diversity.
Prerequisites
(DTRU), BTS3012AE(DTRU), DBS3900(modules except RRU3926), BTS3900
(DRFU/MRFUd), BTS3900A(DRFU/MRFUd), BTS3900L(DRFU/MRFUd), and
BTS3900AL(DRFU/MRFUd).
– The test cell has at least one dual-polarized antenna or two single-polarized antennas.
– The feature depends on the feature GBFD-113201 Concentric Cell.
– This feature is mutually exclusive with the following feature when multi-carrier RRU
dynamic TX diversity is used: GBFD-118106 Dynamic Power Sharing(Dual PA power
sharing)
l License
Context
In dynamic transmit diversity mode, the transmit diversity technique is applied to two carriers'
same timeslots only. The two carriers belong to a double-transceiver TRX board. After these
timeslots are released, they stop using the transmit diversity technique to transmit signals. The
dynamic transmit diversity technique makes full use of idle timeslots, improves signal quality
in rural areas, and strikes a balance between system capacity and network coverage by
dynamically adjusting network coverage or system capacity according to the actual situation in
the live network.

GBSS14.0
Procedure
Modifying GSM Cell Parameters in Batches). In this step, set Dynamic
Transmission Div Supported to DDIVERSITY(DDIVERSITY).
in Batches). In this step, set Send Mode to DDIVERSITY(Dynamic Transmit
Diversity) for the TRXs in the overlaid subcell.
NOTE
l You can Run the BSC6900 MML command LST GTRXIUO (CME single configuration:
TRX Configuration Express > Hw_concentric Attribute > Hw_concentric
Attribute) to query the attributes of TRXs in the overlaid subcell.
l If the dynamic transmit diversity technique is to be applied to a DTRU, two carriers must
be configured and the technique must not be applied to the BCCH carrier.
1. Run the BSC6900 MML command SET GCELLHOIUO. In this step, set Assign
Optimum Layer to SysOpt(System optimization).
2. Run the BSC6900 MML command SET GTRXADMSTAT. In this step, set
Administrative State to Lock(Lock) for carriers except the BCCH carrier and those
carriers whose send mode is DDIVERSITY(Dynamic Transmit Diversity).
CAUTION
Setting Administrative State for the TRX to Lock(Lock) may causes congestion in
the cell where the TRX is located.
Administrative State to Lock(Lock) for the TCH of the BCCH carrier.
CAUTION
Setting Administrative State for the TCH of main BCCH carrier to Lock(Lock) may
causes congestion in the cell where the TRX is located.
4. Monitor the status of the TCH by referring to Monitoring Channel Status, and use an
MS to make a call.
NOTE
A TCH in the overlaid subcell is assigned to the MS only when the uplink receive level of the
SDCCH meets the following conditions: The difference between the assign-optimum-level
threshold and the PBT gain is smaller than the SDCCH uplink receive level. The SDCCH uplink
receive level is smaller than the assign-optimum-level threshold. The default assign-optimum-
level threshold is 35 while the default PBT gain is 4. You can change the assign-optimum-level
threshold according to the SDCCH uplink receive level to enable the system to assign a channel
to the overlaid subcell. In this way, dynamic transmit diversity can be triggered.

GBSS14.0
Expected result: Checking the channel monitoring tab page on the BSC6900 LMT,
you can find that the emergency call occupies channels of the two carriers' same
timeslots. One channel is in the Working state while the other one is in the
Subordinate Channel state.
in Batches), in this step, set Send Mode for TRXs in the overlaid subcell to other
send modes supported by the TRXs.
Modifying GSM Cell Parameters in Batches), in this step, set Dynamic
Transmission Div Supported to NOTSUPPORT(Not Support).
----End
Example
SET GCELLCHMGBASIC: IDTYPE=BYID, CELLID=0, DYNPBTSUPPORTED=DDIVERSITY;
SET GTRXDEV: IDTYPE=BYID, TRXID=2, SNDMD=DDIVERSITY;
SET GCELLHOIUO: IDTYPE=BYID, CELLID=0, OPTILAYER=SysOpt;
SET GTRXADMSTAT: TRXID=2, ADMSTAT=Lock;
SET GTRXDEV: IDTYPE=BYID, TRXID=2, SNDMD=NOCOMB;
SET GCELLCHMGBASIC: IDTYPE=BYID, CELLID=0, DYNPBTSUPPORTED=NOTSUPPORT;

GBSS14.0
Feature Activation Guide 176 Configuring Dynamic PBT
176 Configuring Dynamic PBT
Dynamic PBT.
Prerequisites
– DTRU, DRFU, RRU3004 support the feature Dynamic PBT currently.
– This feature depends on the feature GBFD-113201 Concentric Cell.
l License
Context
In dynamic Power Boost Technology (PBT) mode, the PBT is applied to two carriers' same
timeslots only. The two carriers belong to a double-transceiver TRX board. After these timeslots
are released, they stop using the PBT to transmit signals. The dynamic PBT makes full use of
idle timeslots, improves signal quality for the areas with poor signal quality, and strikes a balance
between system capacity and network coverage by dynamically adjusting network coverage or
system capacity according to the actual situation in the live network.
Moreover, the dynamic PBT increases the handover success rate for MSs located at the edge of
a cell, and therefore improves the performance of a concentric cell where the Co-BCCH function
is enabled.
The following operation illustrates how to configure the dynamic PBT for the DTRU on a
BTS3012.
Procedure

GBSS14.0

Modifying GSM Cell Parameters in Batches). In this step, set Dynamic
Transmission Div Supported to DPBT(DPBT).
in Batches). In this step, set Send Mode to DPBT(DPBT) for TRXs in the overlaid
subcell.
NOTE
l You can Run the BSC6900 MML command LST GTRXIUO (CME single configuration:
Attribute) to query the attributes of TRXs in the overlaid subcell.
l If the dynamic PBT is to be applied to a radio frequency (RF) module, two carriers must
be configured for the module and the dynamic PBT must not be applied to the RF module
where the BCCH carrier is located..
Optimum Layer to SysOpt(System optimization).
2. Run the BSC6900 MML command SET GTRXADMSTAT. In this step, set
Administrative State to Lock(Lock) for carriers except the BCCH carrier and those
carriers whose send mode is not DPBT(DPBT).
Administrative State to Lock(Lock) for the TCH or TCHF of the BCCH carrier.
4. Monitor the status of the TCH or TCHF by referring toMonitoring Channel Status,
and use an MS to make an emergency call.
NOTE
A TCH in the overlaid subcell is assigned to the MS only when the uplink receive level of the
SDCCH meets the following conditions: The difference between the assign-optimum-level
threshold and the PBT gain is smaller than the SDCCH uplink receive level. The SDCCH uplink
receive level is smaller than the assign-optimum-level threshold. The default assign-optimum-
level threshold is 35 while the default PBT gain is 4. You can change the assign-optimum-level
threshold according to the SDCCH uplink receive level to enable the system to assign a channel
to the overlaid subcell. In this way, dynamic transmit diversity can be triggered.
Expected result: Checking the channel monitoring tab page on the BSC6900 LMT,
you can find that the emergency call occupies channels of the two carriers' same
timeslots. One channel is in the Working state while the other one is in the
Subordinate Channel state.
----End
Example
SET GCELLCHMGBASIC: IDTYPE=BYID, CELLID=0, DYNPBTSUPPORTED=DPBT;
SET GTRXDEV: TRXID=2, SNDMD=DPBT;
SET GCELLHOIUO: IDTYPE=BYID, CELLID=0, OPTILAYER=SysOpt;

GBSS14.0
SET GTRXADMSTAT: TRXID=2, ADMSTAT=Lock;


GBSS14.0
Feature Activation Guide 177 Configuring Enhanced EDGE Coverage
177 Configuring Enhanced EDGE

Coverage
Enhanced EDGE Coverage.
Prerequisites
Enhanced EDGE coverage is supported by the following BTSs and TRXs.
– Double-transceiver series base stations
DTRUs and DTRMs of BTS3012, BTS3012II, BTS3012AE, BTS3006C, and
BTS3002E.
– 3900 series base stations
DBS3900, BTS3900, BTS3900A, BTS3900L, and BTS3900E.
NOTE
Neither QTRUs nor BTS3900B supports enhanced EDGE coverage.

feature depends on the feature GBFD-114201 EGPRS.
– This feature cannot be used together with the feature GBFD-510104 Multi-Site Cell or
GBFD-113703 Antenna Frequency Hopping. enhanced EDGE Coverage of RRU3004/
DRFU cannot be used together with the feature GBFD-111602 TRX Power Amplifier
Intelligent Shutdown or GBFD-111603 TRX Power Amplifier Intelligent Shutdown on
Timeslot Level.
l License
Context
l The Enhanced EDGE Coverage feature described in this feature only applies to the 8PSK
modulation mode.

GBSS14.0
l The Enhanced EDGE Coverage feature improves the average power of PS services through
the coverage enhancement technology and power sharing technology, thus ensuring that
data services can have the same cell coverage capability as speech services. This feature is
applicable to both the DTRU and QTRU.
l After the Enhanced EDGE Coverage feature is activated, the Cell 8PSK Power
Attenuation Grade parameter becomes invalid automatically.
l Table 177-1 list the conditions for implementing the Enhanced EDGE Coverage feature
for the BTS3012 series.
Table 177-1 Prerequisites for implementing the Enhanced EDGE Coverage feature
(BTS3012 series)
Prerequisite Whether Enhanced EDGE Coverage
Is Supported
The TRX module is DTRU (type B). Supported.
The power of two carriers configured on Supported.

the DTRU is 60 W, and the static power
levels of both carriers are equal to 0.
The TRX module is DTRU (type A) or Not supported.

QTRU.
A single DTRU module is configured with Not supported.

one carrier.
When a single DTRU module is configured Not supported.

with two carriers, the intelligent shutdown
function is performed on one of the
carriers.
The two carriers configured on the DTRU Not supported.

module belong to two cells.
When one of the carriers is configured as Not supported.

the BCCH, the other non-BCCH carrier of
the DTRU module is supported or not.
The transmit mode of the DTRU is Not supported.

configured as PBT (excluding dynamic
PBT) or transmit diversity (excluding
dynamic transmit diversity).
A channel of the DTRU is faulty. Not supported.
l Table 177-2 list conditions for implementing the Enhanced EDGE Coverage feature for
the BTS3900E.

GBSS14.0
Table 177-2 Prerequisites for implementing the Enhanced EDGE Coverage feature
(BTS3900E)
Prerequisite Whether Enhanced EDGE Coverage

Is Supported
Not FH, RF FH, and baseband FH Supported.
RanSharing Supported.
Procedure
Batches), and then set High-Order Modulation Power Increase Allowed to
ALLOWED(Allowed), set Enable Enhanced EDGE Coverage to ALLOWED
(Allowed).
NOTE
l The support of High-Order Modulation Power Increase Allowed by the BCCH is

determined by the High-Order Modulation Power Increase on BCCH TRX Allowed
parameter.
l The Power Increase in 8PSK parameter is used to control the increased amplitude of the
maximum power in 8PSK modulation mode.
1. Check traffic statistics information about the measurement unit High-Order
Modulation Power Increase Measurement per TRX on the M2000, and then
determine the effect of the Enhanced EDGE Coverage feature. For details, see the
M2000 product documentation.
NOTE
The measurement unit High-Order Modulation Power Increase Measurement per TRX
contain 11 counters, such as Number of Bursts in High-Order Modulation Scheme and
Number of Bursts with High-Order Modulation Power Increase of n dB. The value of n
can be either of the following values: 0.4, 0.8, 1.2, 1.6, 2.0, 2.4, 2.8, 3.2, 3.6, or 4.0.
Batches), and then set High-Order Modulation Power Increase Allowed to
NOT_ALLOWED(Not Allowed).
----End
Example
SET GCELLBASICPARA: IDTYPE=BYID, CELLID=0, HIGHMODPWREN=ALLOWED,
EDGEPWREN=ALLOWED;
SET GCELLBASICPARA: IDTYPE=BYID, CELLID=0, HIGHMODPWREN=NOT_ALLOWED;

GBSS14.0
Feature Activation Guide 178 Configuring Dynamic Power Sharing
178 Configuring Dynamic Power Sharing
Dynamic Power Sharing.
Prerequisites
– Only multi-carrier RF modules support this feature.
– The RRU3926 does not support the dual-PA power sharing function.
– When a GRFU or MRFU is mixed with an MRFUe, to support the dual-PA power
sharing function, the MRFUe must support 6 or less TRXs, and the difference between
TRX numbers configured on the GRFU/MRFU and MRFUe must be less than or equal
to 1.
– When a GRFU is mixed with an MRFU or MRFUe that supports dual modes, the dual-
PA power sharing function is not supported.
– When an MRFUd is mixed with an RFU that has one transmit channel and two receive
channels, the inter-module power sharing function is not supported.
feature depends on the feature GBFD-117601 HUAWEI III Power Control Algorithm.
– The single-PA power sharing function cannot be used together with any of the following
features: GBFD-117002 IBCA (Interference Based Channel Allocation),
GBFD-117001 Flex MAIO, GBFD-118701 RAN Sharing, and GBFD-114001
Extended Cell.
– For the radio frequency unit (RFU), the dual-PA power sharing function cannot be used
together with any of the following features: GBFD-111602 TRX Power Amplifier
Intelligent Shutdown, GBFD-118701 RAN Sharing, GBFD-113201 Concentric Cell,
GBFD-114501 Co-BCCH Cell, GBFD-113701 Frequency Hopping (RF hopping,
baseband hopping), GBFD-117001 Flex MAIO, GBFD-118701 RAN Sharing, and
GBFD-114001 Extended Cell.
– For the remote radio unit (RRU), the dual-PA power sharing function cannot be used
together with any of the following features: GBFD-111602 TRX Power Amplifier
Intelligent Shutdown, GBFD-118701 RAN Sharing, GBFD-113201 Concentric Cell,
GBFD-115902 Transmit Diversity, GBFD-118101 Dynamic Transmit Diversity,

GBSS14.0
GBFD-117002 IBCA, GBFD-117001 Flex MAIO, GBFD-114001 Extended Cell, and

GBFD-510104 Multi-site Cell.
– If the Dynamic Power Sharing feature has been enabled in a cell, you do not need to
enable the GBFD-117602 Active Power Control feature because the Dynamic Power
Sharing feature contains all of its functions.
– If power control parameters are not properly set, there will be a high percentage of high
signal levels. When this occurs, network performance will not be improved even if
Dynamic Power Sharing is enabled and the number of peak clipping attempts is
minimized. Therefore, set downlink power control parameters to appropriate values and
enable the GBFD-114801 Discontinuous Transmission (DTX)-Downlink function
before enabling Dynamic Power Sharing.
l License
– Dependency on frequency bands and cells: All activated TRXs of a multi-transceiver
unit must work on the same frequency band and must be configured in the same cell.
In the case of a concentric cell, all activated TRXs must be configured in the underlaid
or overlaid subcell.
– Restriction on PS channel allocation: If the remaining power of the timeslot of a PS
channel is lower than the maximum transmit power of the TRX, the channel cannot be
converted into a packet data channel (PDCH).
– Restriction on cell configuration: To avoid cell congestion and enhance network
performance after this feature is enabled, the Channel Assign Allow for Insuff
Power parameter must be set to YES(Yes) and the recommended value of the C/I
Estimate Value parameter is 10 dB.
– Restriction on TRX configuration: The percentage of stand-alone dedicated control
channels (SDCCHs) and PDCHs must be less than or equal to 30% the total number of
channels in a cell. It is recommended that static PDCHs be configured on BCCH carriers
and only one SDCCH be configured on each timeslot.
Context
With this feature, the transmit power of a TRX can be improved if the transmit power of the
TRX cannot meet the actual requirements. In addition, if the total transmit power of TRXs in a
TRX group exceeds the transmit power threshold of the TRX group, calls with different power
requirements are grouped into different timeslots to ensure that the total power of the same
timeslot on the TRX group does not exceed the transmit power threshold. Therefore, this feature
decreases the number of peak clippings and improves the network performance.
Procedure
l Activation Procedure for Single- or Dual-PA Power Sharing
Modifying GSM Cell Parameters in Batches). In this step, set Multi-Density TRX
Power Sharing to DYNAMIC(Dynamic power sharing).

GBSS14.0
in Batches) to improve the transmit power of the TRX. In this step, set Power
Type based on the network plan.
l Activation Procedure for Inter-Module Power Sharing
The procedure for configuring inter-module power sharing for the GRFU is the same as
that for the MRFU. The following uses the MRFU as an example to describe how to
configure inter-module power sharing.
1. Deploy a BTS on the BSC6900. Run the BSC6900 MML command ADD
BTSRXUBRD (CME single configuration: BTS Device Panel > Board > BTS RXU
Board; CME batch modification center: not supported) set Power Class based on
your individual needs. If an MRFU V1 is deployed, set Power Class to CLASS0 or
CLASS2. Otherwise, set Power Class to CLASS0, CLASS1, or CLASS2.
2. Run the BSC6900 MML command LST GTRX (CME single configuration: BTS
Topology > Right click Cell > ADD TRX). Perform subsequent configuration
operations on power sharing based on the query results.
Example result:
TRX ID Freq. TRX No. Subrack No. Slot No. TRX Board Pass No.
24 35 3 4 0 3
25 45 4 4 0 4
2000 49 0 4 0 0
2001 71 1 4 0 1
2002 40 2 4 0 2
22 75 8 4 1 3
23 80 9 4 1 4
2004 65 6 4 1 5
2005 30 5 4 1 2
Configure five carriers for the BCCH TRX module and four carriers for another TRX
module. Then, perform power sharing on the two TRX modules.
supported) to enable inter-module power sharing. In this step, set Associated Board
Function to POWERSHARING(Power Sharing Between Boards) and other
parameters to appropriate values.
in Batches). In this step, set Power Type for each TRX module in the cell to an
appropriate value and ensure that the maximum output power of each TRX module is
higher than the output power required for enabling this feature.
1. Log in to the M2000 client, choose Performance > Query Result. Click New
Query in the display window. Then, the New Query dialog box is displayed. Choose
BSC6900 GSM > BTSM Measurement > TRX State Measurement per TRX to
check the values of counters such as The total BURST count cut 0.5dB power, The
total BURST count cut 1.0dB power, The total BURST count cut 1.5dB power,
and The total BURST count cut 2.0dB power before and after this feature is
activated.
The expected result: After this feature is activated, the probability of peak clipping
for timeslots is decreased.

GBSS14.0
NOTE
When the transmit power of all the calls on a timeslot of a TRX group is greater than the
maximum transmit power of the BTS, the BTS decreases the power of all the calls to ensure
its normal operation. Number of Timeslots with Power Decreased provides the number of
timeslots whose transmit power is decreased.
l Deactivation Procedure for Single- or Dual-PA Power Sharing
Modifying GSM Cell Parameters in Batches) to set Multi-Density TRX Power
Sharing to NONE(None).
l Deactivation Procedure for Inter-Module Power Sharing
supported) to stop inter-module power sharing. In this step, set Associated Board
Function to OFF(OFF) and other parameters to appropriate values.
----End
Example
//Activating dynamic power sharing: single- or dual-PA power sharing
SET GCELLCHMGAD: IDTYPE=BYID, CELLID=0, QTRUPWRSHARE=DYNAMIC;
SET GTRXDEV: TRXID=0, POWT=50W;
//Activating dynamic power sharing: inter-module power sharing
ADD BTSRXUBRD: IDTYPE=BYID, BTSID=20, BT=MRFU, RXUSPEC=MRFU_V1, CN=0,
SRN=0, SN=0, RXUNAME="RXU", RXUCHAINNO=0, RXUPOS=1, ISCONFIGTHD=YES,
PWRMODE=CLASS0;
LST GTRX: IDTYPE=BYID, BTSID=20, CELLID=200;
RXUTYPE=MRFU, RELATEDMODFUNC=POWERSHARING, RELATEDCN=0, RELATEDSRN=4,
RELATEDSN=1;
SET GTRXDEV: TRXID=22, POWL=0, POWT=25W;
//Deactivating dynamic power sharing: single- or dual-PA power sharing
SET GCELLCHMGAD: IDTYPE=BYID, CELLID=0, QTRUPWRSHARE=NONE;
//Deactivating dynamic power sharing: inter-module power sharing
RXUTYPE=MRFU, RELATEDMODFUNC=OFF;

GBSS14.0
Feature Activation Guide 179 Configuring Extended Cell
179 Configuring Extended Cell
Extended Cell.
Prerequisites
This feature does not have any special requirements for hardware.
The configurations of the other features, on which this feature depends, are complete. This
feature depends on the feature GBFD-113201 Concentric Cell.
l License
Context
The Extended Cell feature expands the cell radius and improves the capability of the BTS for
wide coverage.
This feature is applicable to areas with a small population and low signal fading such as deserts,
seashores, islands, and water areas.
Procedure
center: 3.20 Modifying GSM Cell Parameters in Batches) with Cell Extension
Type set to DualTS_ExtCell(Double Timeslot Extension Cell).
1. Monitor the channel status by referring to Monitoring Channel Status.
Expected result: One of the two adjacent TCHs with the same TRX number is not
displayed, as shown in Figure 179-1.

GBSS14.0
Feature Activation Guide 179 Configuring Extended Cell
Figure 179-1 Channels in a cell enabled with Extended Cell
center: 3.20 Modifying GSM Cell Parameters in Batches) with Cell Extension
Type set to Normal_cell(Normal cell).
2. Verify that Extended Cell has been deactivated by monitoring the channel status. For
details, see Monitoring Channel Status.
Expected result: Both of the two adjacent TCHs with the same TRX number are
displayed, as shown in Figure 179-2.
Figure 179-2 Channels in a cell not enabled with Extended Cell
----End
Example
//Activating Extended Cell
MOD GCELL: IDTYPE=BYID, CELLID=0, EXTTP=DualTS_ExtCell;
//Deactivating Extended Cell
MOD GCELL: IDTYPE=BYID, CELLID=0, EXTTP=Normal_cell;

GBSS14.0
Feature Activation Guide 180 Configuring Concentric Cell
180 Configuring Concentric Cell
Concentric Cell.
Prerequisites
l License
– The cell is configured.
Context
l When tight frequency reuse is adopted, the concentric cell technology can be used to avoid
or reduce radio interference and therefore to ensure voice quality.
l The concentric cell technology divides an ordinary cell into two service layers: overlaid
(OL) subcell and underlaid (UL) subcell. Compared with the UL subcell, the OL subcell
is configured with more channels and therefore it becomes the primary traffic bearer layer.
The OL subcell aims to absorb most subscribers in the concentric cell. The UL subcell aims
to provide services for areas that are not covered by the OL subcell.
Parameter Principle for Different
Name Parameter ID Scenarios) Data Source
Cell IUO Type IUOTP Set this parameter to BSC internal

Concentric_cell(Concentric planning
Cell).

GBSS14.0
Enhanced ENIUO Set this parameter to ON BSC internal

Concentric (On). planning
Allowed
UL to OL HO ULTOOLHOALLO Set this parameter to YES BSC internal

Allowed W (Yes). planning
OL to UL HO OLTOULHOALLO Set this parameter to YES BSC internal

Allowed W (Yes). planning
RX_LEV for RECLEVUOHOAL Set this parameter to YES BSC internal

UO HO LOW (Yes). planning
Allowed
RX_QUAL for RECQUALUOHOA Set this parameter to NO BSC internal

UO HO LLOW (No). planning
Allowed
TA for UO HO TAFORUOHOALL Set this parameter to NO BSC internal

Allowed OW (No). planning
Concentric ATCBHOEN Set this parameter to NO BSC internal

Circles ATCB (Close). planning
HO Allowed
Assign OPTILAYER Set this parameter to SysOpt BSC internal

Optimum (System optimization). planning
Layer
Assign- OPTILEVTHRES Decrease the value of this BSC internal

optimum-level parameter in steps of 2 dB if planning
Threshold the underlaid subcell is
congested.
TA Threshold OPTITATHRES Set this parameter to 63. Network planning

of Assignment
Pref
UtoO Traffic UTOOTRAFHOAL Set this parameter to YES BSC internal

HO Allowed LOW (Yes) if overlaid-underlaid planning
load balance needs to be
enabled.
Pref. Subcell in HOALGOPERMLA Set this parameter to SysOpt BSC internal

HO of Intra- Y (System optimization). planning
BSC
Incoming-to- ACCESSOPTILAY Set this parameter to BSC internal

BSC HO USubcell(Underlaid planning
Optimum subcell).
Layer

GBSS14.0
UO HO Watch IUOHOSTATIME Set this parameter to 6. BSC internal

Time planning
UO HO Valid IUOHODURATIM Set this parameter to 4. BSC internal

Time E planning
UtoO HO UTOORECTH Decrease the value of this Network planning

Received Level parameter in steps of 2 dB if
Threshold the underlaid subcell is
congested. Increase the value
of this parameter in steps of 2
dB if the overlaid subcell is
congested.
PS OtoU HO OTOURECEIVETH Set this parameter to 25. Network planning

Receive Level
Threshold
Procedure
center: 3.20 Modifying GSM Cell Parameters in Batches). In this step, set Cell IUO
Type to Concentric_cell(Concentric Cell) and Enhanced Concentric Allowed to
NOTE
After enhanced concentric cell is enabled, the BSC automatically configures the OL subcell
and the UL subcell as neighboring cells. The neighboring cell relationship cannot be removed.
2. Run the BSC6900 MML command SET GTRXIUO (CME single configuration:
Attribute; CME batch modification center: 3.22 Modifying GSM TRX Parameters
in Batches). In this step, set Concentric Attribute to OVERLAID(Overlaid
Subcell) or UNDERLAID(Underlaid Subcell) based on the network plan.
NOTE
It is recommended that Concentric Attribute on the BCCH TRX be set to UNDERLAID
(Underlaid Subcell).
Parameters in Batches). In this step, set Concentric Circles HO Allowed to YES
(Yes).

GBSS14.0
center: 3.20 Modifying GSM Cell Parameters in Batches) command to set the
handover parameters in the concentric cell based on the current network status.
CAUTION
The following configurations are used only for verification. For commercial networks,
configure parameters based on the network plan. After this feature is verified, restore the
configurations before the verification.
Optimum Layer to USubcell(Underlaid subcell).
2. Use an MS to make a call to a fixed-line phone in the cell.
NOTE
To facilitate the verification, ensure that only one call is made in the serving cell.
Expected result: You can obtain the call setup procedure by performing the operations
given in Tracing Messages on the A Interface and Tracing CS Domain Messages on
the Abis Interface. You can learn that the call occupies a TCH on the TRX in the
underlaid subcell by running the BSC6900 MML command DSP CHNSTAT.
3. Run the BSC6900 MML command SET GTRXCHANADMSTAT to block the
channel that is occupied by the call. In this step, set Administrative State to Lock
(Lock).
Expected result: You can learn that the call is handed over to another TCH on the TRX
in the underlaid subcell by using the BSC6900 MML command DSP CHNSTAT.
CAUTION
Setting Administrative State for the TRX to Lock(Lock) may cause congestion in
4. Repeat step 3 to block all available channels on the TRX in the underlaid subcell.
in the overlaid subcell by using the BSC6900 MML command DSP CHNSTAT.
Optimum Layer to OSubcell(Overlaid subcell).
6. Run the BSC6900 MML command SET GTRXCHANADMSTAT to block all TCHs
on the TRX in the underlaid subcell. In this step, set Administrative State to Unlock
(Unlock).
7. Use the MS to make a call to a fixed-line phone in the cell.
overlaid subcell by running the BSC6900 MML command DSP CHNSTAT.

GBSS14.0
center: 3.20 Modifying GSM Cell Parameters in Batches). In this step, set Cell IUO
Type to Normal_cell(Normal Cell).
----End
Example
//Activating Concentric Cell
MOD GCELL: IDTYPE=BYID, CELLID=0, IUOTP=Concentric_cell, ENIUO=ON,
FLEXMAIO=OFF;
SET GTRXIUO: TRXID=0, IUO=UNDERLAIDOVERLAID;
SET GCELLHOBASIC: IDTYPE=BYID, CELLID=0, CONHOEN=YES;
SET GCELLHOIUO: IDTYPE=BYID, CELLID=0, ULTOOLHOALLOW=YES,
OLTOULHOALLOW=YES;
//Verifying Concentric Cell
//Configuring the underlaid subcell to be preferentially assigned
SET GCELLHOIUO: IDTYPE=BYID, CELLID=2047, HOCTRLSWITCH=HOALGORITHM1,
OPTILAYER=USubcell;
//Making a call. Checking that the call occupies a channel of the
underlaid subcell
DSP CHNSTAT: OBJTYPE=CELL, CELLIDTYPE=BYID, CELLID=2047;
//Blocking the channel that the call occupies (assuming that channel 2 of
TRX 2047 is occupied)
//Checking that the call is successfully handed over to a channel of the
overlaid subcell
//Blocking TCHs of all the TRXs of the underlaid subcell
//Making a call. Checking that the call occupies a channel of the overlaid
subcell
//Unblocking TCHs of all the TRXs of the underlaid subcell
SET GTRXCHANADMSTAT: TRXID=2047, CHNO=2, ADMSTAT=Unlock;
//Configuring the overlaid subcell to be preferentially assigned
SET GCELLHOIUO: IDTYPE=BYID, CELLID=2047, OPTILAYER=OSubcell;
//Making a call Checking that the call occupies a channel of the overlaid
subcell
//Deactivating Concentric Cell
MOD GCELL: IDTYPE=BYID, CELLID=0, IUOTP=Normal_cell;

GBSS14.0
Feature Activation Guide 181 Configuring Co-BCCH Cell
181 Configuring Co-BCCH Cell
Co-BCCH Cell.
Prerequisites
– The feature GBFD-113201 Concentric Cell has been configured before this feature is
activated.
l License
– The BTS supports the configured frequency band.
Context
Co-BCCH cell increases the traffic capacity of a cell, reduces handovers and interference, and
supports continuous coverage and sparse coverage in hot spots.
A co-BCCH cell consists of an overlaid subcell and an underlaid subcell. The frequency band
configuration is as follows:
l If the overlaid subcell is configured to be work at DCS1800M, then the underlaid subcell
must be configured to be work at GSM900M or GSM850M.
l If the overlaid subcell is configured to work at PCS1900M, then the underlaid subcell must
be configured to work at GSM850M.
NOTE
The signal loss of DCS1800M changes with the transmission distance. At the distance of 0.5-1 km, the
signal power of DCS1800M is about 15 dB lower than the signal power of GSM900M.

GBSS14.0

Remarks
(Configuration
Principle for
Parameter Different
Support High HiFreqBandSup- Set this parameter to BSC internal planning

Frequency port PCS1900 if a cell
Band supports
GSM850_1900.
BCCH IUO of DBFREQBCCHI l Set this BSC internal planning

Double UO parameter to
Frequency Cell Extra(Extra) if
the coverage
area in the
underlaid
subcell is large
and tight
frequency reuse
is used in the
overlaid subcell.
l Set this
parameter to
Inner(Inner) if
the coverage
areas in the
overlaid and
underlaid
subcells are
similar and tight
frequency reuse
is used on the
BCCH.
Cell IUO Type IUOTP Set this parameter to BSC internal planning
Concentric_cell
(Concentric Cell).
Enhanced ENIUO Set this parameter to BSC internal planning

Concentric ON(On).
Allowed
UL to OL HO ULTOOLHOAL Set this parameter to BSC internal planning

Allowed LOW YES(Yes).
OL to UL HO OLTOULHOAL Set this parameter to BSC internal planning

Allowed LOW YES(Yes).
RX_LEV for RECLEVUOHO Set this parameter to BSC internal planning

UO HO ALLOW YES(Yes).
Allowed

GBSS14.0
Remarks
(Configuration
Principle for
Parameter Different
RX_QUAL for RECQUALUOH Set this parameter to BSC internal planning

UO HO OALLOW NO(No).
Allowed
TA for UO HO TAFORUOHOA Set this parameter to BSC internal planning

Allowed LLOW NO(No).
Concentric ATCBHOEN Set this parameter to BSC internal planning

Circles ATCB NO(Close).
HO Allowed
Assign OPTILAYER Set this parameter to BSC internal planning

Optimum SysOpt(System
Layer optimization).
Assign- OPTILEVTHRE Decrease the value BSC internal planning

optimum-level S of this parameter in
Threshold steps of 2 dB if the
underlaid subcell is
congested.
TA Threshold OPTITATHRES Set this parameter to Network planning

of Assignment 63.
Pref
UtoO Traffic UTOOTRAFHO Set this parameter to BSC internal planning

HO Allowed ALLOW YES(Yes) if load
balance between the
overlaid subcell and
the underlaid
subcell needs to be
enabled.
Pref. Subcell in HOALGOPERM Set this parameter to BSC internal planning

HO of Intra- LAY SysOpt(System
BSC optimization).
Incoming-to- ACCESSOPTIL Set this parameter to BSC internal planning

BSC HO AY USubcell
Optimum (Underlaid
Layer subcell).
UO HO Watch IUOHOSTATIM Set this parameter to BSC internal planning

Time E 6.
UO HO Valid IUOHODURATI Set this parameter to BSC internal planning

Time ME 4.

GBSS14.0
Remarks
(Configuration
Principle for
Parameter Different
UtoO HO UTOORECTH Decrease the value Network planning

Received Level of this parameter in
Threshold steps of 2 dB if the
underlaid subcell is
congested. Increase
the value of this
parameter in steps
of 2 dB if the
overlaid subcell is
congested.
OtoU HO OTOURECEIVE Set this parameter to Network planning

Received Level TH 25.
Threshold
Procedure
1. Optional: When the frequency band of a cell is GSM850_1900, Run the BSC6900
MML command SET BSCBASIC (CME single configuration: GSM Global
Configuration Express > BSC Basic Configuration > Basic Attributes of BSC;
CME batch modification center: 3.17 Modifying GBSC Parameters in Batches). In
this step, set Support High Frequency Band to PCS1900.
Topology > Right click BTS > ADD Cell, Cell Configuration Express > Cell
Attributes > GSM CELL; CME batch modification center: 3.20 Modifying GSM
Cell Parameters in Batches) to add a cell and set the parameters Freq. Band and
BCCH IUO of Double Frequency Cell.
NOTE
If the frequency band of the cell to be added is GSM900_DCS1800 or GSM850_1800, perform

the following steps:
center: 3.20 Modifying GSM Cell Parameters in Batches), In this step, set Cell IUO
Type to Concentric_cell(Concentric Cell) and Enhanced Concentric Allowed to
4. Run the BSC6900 MML command ACT GCELL (CME single configuration: Main
View > Right click GSM cell > Activate Cell; CME batch modification center: not
supported) to activate the cell.
center: 3.20 Modifying GSM Cell Parameters in Batches) to set the handover

GBSS14.0
parameters Current HO Control Algorithm and UL to OL HO Allowed for the

concentric cell.
CAUTION
The following configurations are used only for verification. For commercial networks,
configure parameters based on the network plan. After this feature is verified, restore the
configurations before the verification.
Optimum Layer to USubcell(Underlaid subcell).
2. Use an MS to make a call to a fixed-line phone in the cell.
NOTE
To facilitate the verification, ensure that only one call is made in the serving cell.
underlaid subcell by running the BSC6900 MML command DSP CHNSTAT.
3. Run the BSC6900 MML command SET GTRXCHANADMSTAT to block the
channel that is occupied by the call. In this step, set Administrative State to Lock
(Lock).
in the underlaid subcell by using the BSC6900 MML command DSP CHNSTAT.
CAUTION
Setting Administrative State for the TRX to Lock(Lock) may cause congestion in
4. Repeat step 3 to block all available channels on the TRX in the underlaid subcell.
in the overlaid subcell by using the BSC6900 MML command DSP CHNSTAT.
Optimum Layer to OSubcell(Overlaid subcell).
6. Run the BSC6900 MML command SET GTRXCHANADMSTAT to block all TCHs
on the TRX in the underlaid subcell. In this step, set Administrative State to Unlock
(Unlock).
7. Use the MS to make a call to a fixed-line phone in the cell.
overlaid subcell by running the BSC6900 MML command DSP CHNSTAT.

GBSS14.0
1. Run the BSC6900 MML command RMV GCELL (CME single configuration: BTS
Topology > Right click Cell > Delete Cell; CME batch modification center: 3.19
Deleting GSM Cells in Batches) to remove the co-BCCH cell to be deactivated.
----End
Example
//Activating Co-BCCH Cell
//Assuming that the cell ID is 2047
//Setting Support High Frequency Band to PCS1900
SET BSCBASIC: HiFreqBandSupport=PCS1900;
//Adding a co-BCCH cell with the frequency band set to GSM850_1900 and the
cell type set to concentric cell
ADD GCELL: CELLID=2047, CELLNAME="PCS1900", TYPE=GSM850_1900, MCC="460",
MNC="08", LAC=0808, CI=0001, IUOTP=Concentric_cell, ENIUO= OFF,
DBFREQBCCHIUO=Extra, FLEXMAIO=OFF;
//Modifying concentric cell attributes
MOD GCELL: IDTYPE=BYID, CELLID=2047, IUOTP=Concentric_cell, ENIUO=OFF;
//Setting the concentric cell handover algorithm to handover algorithm I
and allowing handover from the underlaid subcell to the overlaid subcell
ULTOOLHOALLOW=YES;
//Verifying Co-BCCH Cell
//Configuring the underlaid subcell to be preferentially assigned
OPTILAYER=USubcell;
//Making a call. Checking that the call occupies a channel of the
underlaid subcell
//Blocking the channel that the call occupies (assuming that channel 2 of
TRX 2047 is occupied)
//Checking that the call is successfully handed over to a channel of the
overlaid subcell
//Blocking TCHs of all the TRXs of the underlaid subcell
//Making a call. Checking that the call occupies a channel of the overlaid
subcell
//Unblocking TCHs of all the TRXs of the underlaid subcell
SET GTRXCHANADMSTAT: TRXID=2047, CHNO=2, ADMSTAT=Unlock;
//Configuring the overlaid subcell to be preferentially assigned
SET GCELLHOIUO: IDTYPE=BYID, CELLID=2047, OPTILAYER=OSubcell;
//Making a call Checking that the call occupies a channel of the overlaid
subcell
//Deactivating Co-BCCH Cell
//Removing the configured co-BCCH cell
RMV GCELL: IDTYPE=BYID, CELLID=2047;

GBSS14.0
Feature Activation Guide 182 Configuring Enhanced Dual-Band Network
182 Configuring Enhanced Dual-Band

Network
Enhanced Dual-Band Network.
Prerequisites
l License
Context
The enhanced dual-band network is an improved version of the existing dual-band network. In
the enhanced dual-band network, two single-band cells at the same level and layer with different
coverage areas logically form a cell group with two bidirectional neighboring cells. One is an
overlaid subcell and the other is an underlaid subcell. In the enhanced dual-band network
algorithm, channel resources can be shared and cell load can be balanced between the two cells
in a cell group.
NOTE
l If the two cells belong to different operators, an enhanced dual-band network cannot be configured.
l Before changing the relationships between the cells and the operator, check whether an enhanced dual-
band network is configured. If an enhanced dual-band network is configured, modify the parameters
for the enhanced dual-band network.
Procedure
1. A GSM900 cell and a DCS1800 cell are configured in the BSS. Run the BSC6900
MML command ADD G2GNCELL (CME single configuration: Cell Configuration

GBSS14.0
Express > Neighboring Cell > BSC 2G Neighbor Cell; CME batch modification
center: not supported) to configure the GSM900 cell as a unidirectional neighboring
2G cell of the DCS1800 cell.
2. Repeat Step 1 to configure the DCS1800 cell as a unidirectional neighboring 2G cell
of the GSM900 cell, so that the two cells are configured as bidirectional neighboring
cells of each other.
center: 3.20 Modifying GSM Cell Parameters in Batches) to modify the parameters
for the GSM900 cell. In this step, set Cell IUO Type to EDB_cell(Enhanced Double
Frequency Cell), Cell Inner/Extra Property to Extra(Extra), Same Group Cell
Index Type (Not required on the CME) to BYID(By Index), and Same Group Cell
Index to the index of the DCS1800 cell.
– Verify the call access function in the enhanced dual-band network by performing the
1. Run the BSC6900 MML command SET GCELLCCBASIC. In this step, set
ECSC to YES(Yes).
2. Run the BSC6900 MML command SET GCELLBASICPARA. In this step, set
Directed Retry of the two cells to YES(Yes).
3. Run the BSC6900 MML command SET GCELLHOEDBPARA to set the
parameters for the GSM900 cell. In this step, set UL Subcell Assignment
Optimization to YES(Yes), UL Subcell Lower Load Threshold to 0, UL
Subcell General Overload Threshold to 1, and both Distance Between
Boundaries of Subcells and Distance Hysteresis Between Boundaries to 0. Set
Load HO Allowed and Load HO of OL Subcell to UL Subcell to NO(No).
4. Make MS1 and MS2 (both supporting the 900 MHz and 1800 MHz frequency
bands) camp on the GSM900 cell. Then, use MS1 to make a call to a fixed-line
phone. MS1 is assigned a channel in the GSM900 cell.
5. Maintain the call of MS1 and use MS2 to make a call to a fixed-line phone in the
GSM900 cell. MS2 is assigned a channel in 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 subcell can be assigned a channel in
the overlaid subcell when the traffic in the underlaid subcell is heavy and the signals
in the overlaid subcell are strong enough.
6. Terminate the calls. Run the BSC6900 MML command SET
GCELLHOEDBPARA to set the parameters for the DCS1800 cell. In this step,
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.
7. Run the BSC6900 MML command SET GCELLHOCTRL to set the parameters
for the DCS1800 cell. In this step, set Min Power Level For Directed Retry to
0.
8. Make MS1 camp on the DCS1800 cell and make a call. MS1 is assigned a channel
in the underlaid GSM900 subcell because the load of the underlaid subcell is not
higher than UL Subcell General Overload Threshold. This indicates that the call
in the overlaid subcell can be assigned a channel in the underlaid subcell when the
traffic in the underlaid subcell is light.
– Verify the handover in the enhanced dual-band network by performing the following
operations:

GBSS14.0
1. Run the BSC6900 MML command SET GCELLHOBASIC. In this step, set the
parameters for enabling each type of handover to NO(No) and Edge HO DL
RX_LEV Threshold to 4.
2. Run the BSC6900 MML command SET GCELLHOEDBPARA to set the
parameters for the DCS1800 cell. In this step. set UL Subcell Assignment
Optimization to NO(No), OL Subcell Assignment Optimization to NO(No),
UL Subcell Lower Load Threshold to 50, UL Subcell General Overload
Threshold to 80, Load HO Allowed to YES(Yes), Load HO of OL Subcell to
UL Subcell to YES(Yes), Incoming OL Subcell HO Level TH to 10, and
Outgoing OL Subcell HO Level TH to 5.
3. Make MS1 camp on the DCS1800 cell and make a call to a fixed-line phone. MS1
is assigned a channel in the overlaid subcell. Then, MS1 is handed over to the
GSM900 cell because the load of the underlaid subcell is lower than UL Subcell
General Overload Threshold. On the A interface, the HANDOVER PERFORM
message is traced and the handover cause value in the message is traffic.
4. Keep the call alive. Run the BSC6900 MML command SET
GCELLHOEDBPARA to set the parameters for the GSM900 cell. In this step.
Optimization to NO(No), UL Subcell Lower Load Threshold to 0, UL Subcell
General Overload Threshold to 1, Load HO Allowed to YES(Yes), Load HO
of OL Subcell to UL Subcell to YES(Yes), Incoming OL Subcell HO Level
TH to 10, and Outgoing OL Subcell HO Level TH to 5.
5. The call is handed over from the GSM900 cell back to the DCS1800 cell because
the load in the underlaid subcell is higher than UL Subcell General Overload
Threshold. On the A interface, the HANDOVER PERFORM message is traced
and the handover cause value in the message is traffic.
6. Keep the call alive. Run the BSC6900 MML command SET
GCELLHOEDBPARA to set the parameters for the DCS1800 cell. In this step.
Optimization to NO(No), UL Subcell Lower Load Threshold to 0, UL Subcell
General Overload Threshold to 1, Load HO Allowed to NO(No), Load HO of
OL Subcell to UL Subcell to NO(No), Incoming OL Subcell HO Level TH to
63, and Outgoing OL Subcell HO Level TH to 62. Set Inner Cell EDGE HO
Enable to YES(Yes).
7. MS1 is handed over to the GSM900 cell because the receive level of MS1 is lower
than Outgoing OL Subcell HO Level TH. On the A interface, the HANDOVER
PERFORM message is traced and the handover cause value in the message is
better cell.
NOTE
This type of edge handover requires that the underlaid subcell is more preferably selected as the target
cell for handover than the overlaid subcell. You can adjust the levels of the overlaid subcell and
underlaid subcell, so that the level of the underlaid subcell is higher than the level of the overlaid
subcell.
for the GSM900 cell. In this step, set Cell IUO Type to Normal_cell(Normal
Cell).

GBSS14.0
for the DCS1800 cell. In this step, set Cell IUO Type to Normal_cell(Normal
Cell).
3. Run the BSC6900 MML command RMV G2GNCELL (CME single configuration:
batch modification center: not supported) to remove the DCS1800 cell from the
neighboring cell list of the GSM900 cell.
batch modification center: not supported) to remove the GSM900 cell from the
neighboring cell list of the DCS1800 cell.
----End
Example
//Activating Enhanced Dual-Band Network
ADD G2GNCELL: IDTYPE=BYID, SRC2GNCELLID=1, NBR2GNCELLID=2,
NCELLTYPE=HANDOVERNCELL, SRCHOCTRLSWITCH=HOALGORITHM1;
MOD GCELL: IDTYPE=BYID, SRC2GNCELLID=1, IUOTP=EDB_cell, CELLINEXTP=Extra,
//Deactivating Enhanced Dual-Band Network
MOD GCELL: IDTYPE=BYID, SRC2GNCELLID=1, IUOTP=Normal_cell;
MOD GCELL: IDTYPE=BYID, SRC2GNCELLID=2, IUOTP=Normal_cell;

GBSS14.0
Feature Activation Guide 183 Configuring Flex MAIO
183 Configuring Flex MAIO
Flex Mobile Allocation Index Offset (MAIO).
Prerequisites
This feature depends on the feature GBFD-113701 Frequency Hopping (RF hopping,
baseband hopping).
– This feature is mutually exclusive to the features GBFD-117002 IBCA, GBFD-118106
Dynamic Power Sharing and GBFD-115830 VAMOS.
l License
– Frame offset is not configured for the BTS.
– A cell is configured for frequency hopping, and the MAs list used by the same timeslot
have the same length.
Context
Under the BTSs with large capacity, adjacent-channel or co-channel interference is likely to
occur among channels because the frequency resources are insufficient and tight frequency reuse
is adopted. When dynamic MAIO is enabled, the MAIO value is dynamically adjusted according
to the current interference and the MAIO value with the minimum interference is assigned to
the channel. This reduces the adjacent-channel and co-channel interference in the GSM system.
It also achieves tight frequency reuse within the BTSs and therefore improves the system
capacity.

GBSS14.0
CAUTION
l PS services provided by an external PCU do not support dynamic MAIO.
l Flex MAIO must be configured for all the cells under the same BTS, and the settings of flex
MAIO parameters must be the same in all the cells.
l Each cell can be configured with a maximum of two MAs. Flex MAIO cannot be enabled
simultaneously in both the overlaid cell and the underlaid cell.
Procedure
center: 3.20 Modifying GSM Cell Parameters in Batches) with Start Flex MAIO
Switch and HSN Modification Switch set to ON(On).
1. Trace RSL signaling over the Abis interface for cells with Flex MAIO enabled.
2. Select the same timeslot on the same TRX board from the RSL signaling at different
time points.
3. Compare MAIOs allocated to channels at different time points.
Expected result: The Flex MAIO feature is enabled when the MAIOs allocated to
channels at different time points are different, as shown in the Figure 183-1 and
Figure 183-2.
Figure 183-1 MAIO IE 1

GBSS14.0
Figure 183-2 MAIO IE 2
center: 3.20 Modifying GSM Cell Parameters in Batches) with Start Flex MAIO
Switch set to OFF(Off).
----End
Example
//Activating Flex MAIO
MOD GCELL: IDTYPE=BYID, CELLID=0, FLEXMAIO=ON, HSNSW=ON;
//Deactivating Flex MAIO
MOD GCELL: IDTYPE=BYID, CELLID=0, FLEXMAIO=OFF;

GBSS14.0
Feature Activation Guide 184 Configuring ICC
184 Configuring ICC
ICC.
Prerequisites
– Currently, the following BTSs support ICC: the BTS3012, BTS3012AE, BTS3006C,
BTS3002E, BTS3900E GSM, BTS3900 GSM, BTS3900A GSM, BTS3900L GSM,
BTS3900AL GSM and DBS3900 GSM.
l License
Context
Interference Cancellation Combining (ICC) is a technology that combines signals of multiple
antennas to suppress interference. Generally, the interference received by different antennas is
generated by the same interference source. Thus, there are correlations between the interference
signals received by different antennas. ICC uses the correlations when combing signals to
eliminate some interference. In this way, ICC improves the anti-interference capability of
equipment and increases the uplink coverage and receiver sensitivity.
Procedure
1. Run the BSC6900 MML command LST GCELLSOFT (CME single configuration:
Software Parameters of Cell), In this step, Set Interference Cancel Mode
Selection to ICC(ICC).
1. Run the BSC6900 MML command LST GCELLSOFT, to query the value of
Interference Cancel Mode Selection.

GBSS14.0
Feature Activation Guide 184 Configuring ICC
Expected result: the value of Interference Cancel Mode Selection is ICC(ICC).

2. Perform an FTP service in the existing network and then view the upload rate. If the
ICC function is enabled, the upload rate is increased. If the ICC function is disabled,
the upload rate is decreased.
Cell Parameters in Batches), In this step, Set Interference Cancel Mode
Selection to MRC(MRC).
----End
Example
SET GCELLSOFT: IDTYPE=BYID, CELLID=0, ICTYP=ICC;
LST GCELLSOFT: IDTYPE=BYID, CELLID=0;
SET GCELLSOFT: IDTYPE=BYID, CELLID=0, ICTYP=MRC;

GBSS14.0
Feature Activation Guide 185 Configuring EICC
185 Configuring EICC
EICC.
Prerequisites
– The BTS3012 that uses the QTRU, BTS3012AE that uses the QTRU, BTS3900E, and
BTS3900B do not support the feature.
– The RRU3008 V1 and RRU3908 V1 do not support the feature when they are configured
with more than four carriers.
– It is recommended that this feature be used together with the features GBFD-118201
Soft-Synchronized Network and GBFD-510401 BTS GPS Synchronization.
– This feature cannot be used together with the feature GBFD-510101 Automatic
Frequency Correction (AFC).
l License
Context
l The interference between signals received by multiple antennas has both spatial correlation
and temporal correlation: co-channel interference (CCI) and intersymbol interference (ISI).
ICC eliminates these two types of interference independently. EICC, however, considers
the correlation of these two types of interference and constructs the multidimensional
combining coefficient matrix to combine the signals according to the maximum signal-to-
noise ratio (SNR) criteria. In this way, EICC achieves better uplink signals.
l EICC requires the matrix of interference, which is calculated on the basis of the training
sequence of desired signals. For each receive signal, the network estimates a channel model
based on the training sequence of the signal, reconstructs the desired signal, and subtracts
the desired signal from the receive signal to obtain the interference signal. By doing so, the
network estimates the matrix of each interference signal and analyzes the statistical
dependency of these interference signals. Based on the statistical dependency, some

GBSS14.0
Feature Activation Guide 185 Configuring EICC
interference is eliminated during the combination of receive signals to maximize

combination gains.
Procedure
Cell Parameters in Batches) to enable EICC for a cell. In this step, set EICC
NOTE
l Enable the adaptive diversity combining function by setting Interference Cancel Mode
Adaptation to ON(On). This function checks whether the existing call is in an interference-
limited or noise-limited scenario. If the call is in an interference-limited scenario, the BTS
uses EICC. If the call is in a noise-limited scenario, the BTS uses MRC.
l Enhance the correctness of the adaptive diversity combining function scenario detection
by setting Enhanced Interference Cancel Mode Adaptation to ON(On).
1. Run the BSC6900 MML command LST GCELLSOFT to query the value of EICC
Allowed.
2. Perform an FTP upload in a live network with interference. Then, check the upload
rate. If the EICC function is enabled, the upload rate increases. If the EICC function
is disabled, the upload rate decreases.
3. Make a call in a live network with interference. Then, check the counters related to
uplink receive quality on the M2000 in the following way: Choose Performance >
Query Result from the menu bar. In the displayed window, click New Query. The
Query Result window is displayed. Navigate to BSC6900 GSM > MR
Measurement > Receive Quality Measurement per TRX. Then, check the value of
the counter Number of MRs on Uplink TCHF(Mean Receive Quality Rank 0) and
calculate the proportion of this counter to the sum of Number of MRs on Uplink TCHF
(Mean Receive Quality Rank 0) through Number of MRs on Uplink TCHF(Mean
Receive Quality Rank 7). If the EICC function is enabled, the proportion is high,
indicating that the speech quality is good. If the EICC function is disabled, the
proportion is low, indicating that the speech quality is poor.
Cell Parameters in Batches) to disable EICC for a cell. In this step, set EICC
Allowed to NO(No).
----End
Example
//Activating EICC
SET GCELLSOFT: IDTYPE=BYID, CELLID=0, STIRCALLOWED=YES;
//Verifying EICC
LST GCELLSOFT: IDTYPE=BYID, CELLID=0;
//Deactivating EICC
SET GCELLSOFT: IDTYPE=BYID, CELLID=0, STIRCALLOWED=NO;

GBSS14.0 186 Configuring Frequency Hopping (RF hopping, baseband
Feature Activation Guide hopping)
186 Configuring Frequency Hopping (RF

hopping, baseband hopping)
This section describes how to activate and verify the optional feature GBFD-113701 Frequency
Hopping (RF hopping, baseband hopping). (This feature cannot be configured using the CME. )
Prerequisites
– Baseband hopping is mutually exclusive with the following features:
– GBFD-111604 Intelligent Combiner Bypass
– GBFD-111606 Power Optimization Based on Channel Type
– GBFD-118101 Dynamic Transmit Diversity
– GBFD-118102 Dynamic PBT (Power Boost Technology)
l License
– In baseband FH mode, all carriers in a baseband FH group in a cell must be in transmit
diversity mode, or none of the carriers can be in transmit diversity mode.
Context
FH can simplify frequency planning, reduce interference, improve voice quality, and increase
system capacity.
When the PS services use coding schemes of high rate such as CS3, CS4, and MCS5 through
MCS9, applying FH will affect PS services. In this case, FH is not recommended.
If the cell is in Active mode, quick activation for FH can be used.

Procedure
1. Run the BSC6900 MML command DEA GCELL to deactivate the cell.
2. Run the BSC6900 MML command ADD GCELLMAGRP to add a FH group. In
this step, set Index Type (Not required on the CME) to BYID(By Index), and set
Cell Index, Hop Index, Hop Mode, and the frequencies to appropriated values.
NOTE
Hop Mode can be set to BaseBand_FH(Baseband FH) or RF_FH(RF FH).

If the BCCH participates in baseband FH, the cell must be configured with at least two FH
groups.
3. Run the BSC6900 MML command SET GCELLHOPTP. In this step, set Index
Type (Not required on the CME) to BYID(By Index), and set Cell Index and
Frequency Hopping Mode to appropriate values.
4. Run the BSC6900 MML command SET GTRXHOP. In this step, set TRX ID and
Hop Type to appropriate values.
5. Run the BSC6900 MML command SET GTRXCHANHOP. In this step, set
Channel Hop Index and Channel MAIO to appropriate values.
NOTE
If the same FH group is used, the mobile allocation index offset (MAIO) of the same channel
on a TRX must be different.
6. Run the BSC6900 MML command ACT GCELL to activate the cell.
l Procedure for Quick Activation
1. Run the BSC6900 MML command SET GCELLHOPQUICKSETUP to quickly
activate FH for a cell. In this step, set Index Type (Not required on the CME) to BYID
(By Index), and set Cell Index, Frequency Hopping Mode, Frequency Hopping
Mode of BCCH TRX, and TRXID LST to appropriate values.
1. Run the BSC6900 MML command SET GCELLHOPQUICKSETUP. In this step,
set Index Type (Not required on the CME) to BYID(By Index), and set Cell Index
to an appropriated value, then set Frequency Hopping Mode to BaseBand_FH
(Baseband frequency hopping) and Frequency Hopping Mode of BCCH TRX to
Hop(Hop).
2. Use the MS to initiate a call in the cell to be verified. The call is initiated successfully
and the voice quality is good. In the Um interface CS tracing window, the Assignment
Command message is traced, and the value of the information element (IE) h:rf-
hopping-channel in the message is 1.
----End
Example
ADD GCELLMAGRP: IDTYPE=BYID, CELLID=0, HOPINDEX=0, HOPMODE=BaseBand_FH,
FREQ1=1, FREQ2=11;
SET GCELLHOPTP: IDTYPE=BYID, CELLID=0, FHMODE=BaseBand_FH;
SET GTRXHOP: TRXID=0, HOPTYPE=BaseBand_FH;

SET GTRXCHANHOP: TRXID=0, CHNO=0, TRXHOPINDEX=0, TRXMAIO=1;

SET GCELLHOPQUICKSETUP: IDTYPE=BYID, CELLID=0, FHMODE=BaseBand_FH,
BCCHTRXHP=Hop, TRXIDLST="0";

GBSS14.0
Feature Activation Guide 187 Configuring BCCH Carrier Frequency Hopping
187 Configuring BCCH Carrier

Frequency Hopping
BCCH Carrier Frequency Hopping. (This feature cannot be configured using the CME. )
Prerequisites
– The feature GBFD-113701 Frequency Hopping (baseband hopping) has been
(RF hopping).
l License
Context
Frequency hopping (FH) can simplify frequency planning, reduce interference, improve voice
quality, and increase system capacity.
When PS services use higher order coding schemes such as CS3, CS4, and MCS-5 through
MCS-9, the application of FH has a negative impact on the PS services. In this case, enabling
FH is not recommended.
When the cell activation state is Active, BCCH carrier FH can be activated quickly.
Procedure
1. Run the BSC6900 MML command DEA GCELL to deactivate the cell.
2. To configure multiple FH groups and include the BCCH frequencies to the FH groups,
Run the BSC6900 MML command ADD GCELLMAGRP for each FH group you

GBSS14.0
want to add. In this step, set Hop Mode to BaseBand_FH(BaseBand FH) and Cell
Index, Hop Index, and EARFCN to appropriate values.
NOTE
To enable the BCCH TRX to participate in FH, at least two FH groups need to be configured
with one FH group containing the BCCH frequency.
3. Run the BSC6900 MML command SET GCELLHOPTP to set the FH type of a cell
to baseband FH. In this step, set Cell Index and Hop Mode to appropriate values.
4. To configure multiple frequencies and set the FH type of the TRXs participating in
FH (including the BCCH TRX) to baseband FH, Run the BSC6900 MML
command SET GTRXHOP for each frequency you want to set. In this step, set TRX
ID and Hop Type to appropriate values.
5. To configure multiple channels and set the FH index and mobile allocation index offset
(MAIO) of the channels, Run the BSC6900 MML command SET
GTRXCHANHOP for each channel you want to set. In this step, set Channel Hop
Index and Channel MAIO to appropriate values.
NOTE
l When the same FH group is used for the TRXs, the MAIO of the same channel of the TRXs
must be different.
l Channel 0 on the BCCH TRX does not participate in FH, and therefore its FH index should
be set to 255.
6. Run the BSC6900 MML command ACT GCELL to activate the cell.
NOTE
In addition to the preceding activation procedure, you can quickly activate this feature by performing
the following step:
Run the BSC6900 MML command SET GCELLHOPQUICKSETUP to quickly set FH for a cell.
In this step, set Cell Index, Frequency Hopping Mode, Frequency Hopping Mode of BCCH
TRX, and TRXID LST (which contains the BCCH TRX ID) to appropriate values.
set CELLID to the index of the cell to be verified, Frequency Hopping Mode to
BaseBand_FH(Baseband frequency hopping), and Frequency Hopping Mode of
BCCH TRX to Hop(Hop).
2. Use the MS to initiate a call in the cell to be verified. The call is initiated successfully
and the voice quality is good. In the Um interface CS tracing window, the Assignment
Command message is traced, and the value of the information element (IE) h:rf-
hopping-channelin the message is 1.
----End
Example
//Activating BCCH Carrier Frequency Hopping
//Configuring FH groups and setting FREQ2 to the BCCH frequency
FREQ1=1, FREQ2=11, FREQ2=12;
FREQ1=1,FREQ3=12;
SET GCELLHOPTP: IDTYPE=BYID, CELLID=0, FHMODE=BaseBand_FH;

GBSS14.0
//Running the follow command for all TRXs participating in FH

SET GTRXHOP: TRXID=0, HOPTYPE=BaseBand_FH;
//Running the follow command to set the channels of all TRXs participating
in FH
SET GTRXCHANHOP: TRXID=0, CHNO=0, TRXHOPINDEX=1, TRXMAIO=1;
//Verifying BCCH Carrier Frequency Hopping
BCCHTRXHP=Hop, TRXIDLST="0";

GBSS14.0
Feature Activation Guide 188 Configuring Antenna Frequency Hopping
188 Configuring Antenna Frequency

Hopping
Antenna Frequency Hopping. (This feature cannot be configured using the CME. )
Prerequisites
– The following BTSs support this feature:
– The BTS3012 series not using the QTRU support this feature.
– The 3900 series base stations using the DRFU or RRU3004 support this feature.
– There are at lease two antennas in a cell participating in antenna frequency hopping.
– This feature is exclusive with the features GBFD-510104 Multi-site cell, GBFD-118104
Enhanced EDGE Coverage, GBFD-118102 Dynamic PBT (Power Boost Technology),
GBFD-118101 Dynamic Transmit Diversity, GBFD-111604 Intelligent Combiner
Bypass, and GBFD-111606 Power Optimization Based on Channel Type.
l License
Context
Antenna frequency hopping enables downlink data on each TRX to be randomly transmitted on
other TRXs. This improves receive quality of the MS from the BCCH TRX and transmit quality
of the BCCH TRX, thereby improving network performance.
If a cell supports both baseband frequency hopping and antenna frequency hopping, the TRX
involved in baseband frequency hopping must also participate in antenna frequency hopping.
When the cell is active, the antenna frequency hopping feature can be configured quickly.
Procedure

GBSS14.0
Feature Activation Guide 188 Configuring Antenna Frequency Hopping
2. Run the BSC6900 MML command SET GCELLHOPANT. In this step, set Cell
Antenna Hopping to YES_HPANT(Yes).
3. Run the BSC6900 MML command ADD GCELLHOPANTGRP to configure
antenna frequency hopping. In this step, set Cell Index and TRX ID to appropriate
values.
l Quick Configuration Procedure
1. Run the BSC6900 MML command SET GCELLHOPANTQUICKSETUP to
quickly configure antenna frequency hopping. In this step, set Cell Index and Cell
Antenna Hopping to appropriate values.
1. Run the BSC6900 MML command LST GCELLHOPANT to query Cell Antenna
Hopping.
Expected result: Cell Antenna Hopping is set to YES_HPANT(Yes).
1. Run the BSC6900 MML command SET GCELLHOPANT. In this step, set Cell
Antenna Hopping to NO_HPANT(No).
NOTE
When the cell is active, Run the BSC6900 MML command SET
GCELLHOPANTQUICKSETUP. In this step, set Cell Antenna Hopping to NO_HPANT(No).
----End
Example
//Activating Antenna Frequency Hopping
SET GCELLHOPANT: IDTYPE=BYID, CELLID=0, HPANTMODE=YES_HPANT;
ADD GCELLHOPANTGRP: IDTYPE=BYID, CELLID=0, HOPTRXINDEX=0, TRXID1=1,
TRXID2=2;
//Verifying Antenna Frequency Hopping
LST GCELLHOPANT: IDTYPE=BYID, CELLID=0;
//Deactivating Antenna Frequency Hopping
SET GCELLHOPANT: IDTYPE=BYID, CELLID=0, HPANTMODE=NO_HPANT;

GBSS14.0
Feature Activation Guide 189 Configuring BCCH Dense Frequency Multiplexing
189 Configuring BCCH Dense Frequency

Multiplexing
BCCH Dense Frequency Multiplexing.
Prerequisites
– This feature cannot be used together with the feature GBFD-113201 Concentric Cell or
GBFD-114501 Co-BCCH Cell.
l License
Context
The BCCH dense frequency multiplexing technique is used in networks with limited frequency
resources. It helps to reduce the number of frequencies occupied by the BCCH TRXs so that
more frequencies can be used as TCHs, increasing the system capacity.
NOTE
If BCCH dense frequency multiplexing is applied with the increase of the cell load, the handover from a
non-BCCH TRX to the BCCH TRX will be triggered, leading to the increase on the handover of the entire
network.
Procedure
Modifying GSM Cell Parameters in Batches). In this step, set TIGHT BCCH
Switch to ON(On).

GBSS14.0
Feature Activation Guide 189 Configuring BCCH Dense Frequency Multiplexing

Modifying GSM Cell Parameters in Batches). In this step, set Level Thresh for
Assign BCCH Under TBCCH and Quality Thresh for Assign BCCH Under
TBCCH based on the site requirements.
Batches). In this step, set Non-BCCH Load Threshold for TIGHT BCCH HO to
1. Make a call in the cell configured with this feature.
Expected result: The call is successfully set up and the voice quality is good.
2. Run the BSC6900 MML command DSP CHNSTAT. In this step, set Object Type
to CELL(Cell) and Cell Index to the index of the cell to be verified.
Expected result: The value of Sub Channel Status is Occupied.
Modifying GSM Cell Parameters in Batches). In this step, set TIGHT BCCH
Switch to OFF(Off).
----End
Example
//Activating BCCH Dense Frequency Multiplexing
SET GCELLCHMGBASIC: IDTYPE=BYID, CELLID=1, TIGHTBCCHSWITCH=ON;
//Deactivating BCCH Dense Frequency Multiplexing
SET GCELLCHMGBASIC: IDTYPE=BYID, CELLID=1, TIGHTBCCHSWITCH=OFF;

GBSS14.0
Feature Activation Guide 190 Configuring IBCA
190 Configuring IBCA
IBCA (Interference Based Channel Allocation).
Prerequisites
– A built-in PCH and a pair of service processing boards are required. An IP interface
board is required to support inter-BSC IBCA.
GBFD-118201 Soft-Synchronized Network, GBFD-113701 Frequency Hopping (RF
hopping, baseband hopping), GBFD-510401 BTS GPS Synchronization,
GBFD-117601 HUAWEI III Power Control Algorithm.
If Soft-Synchronized Network is enabled, this feature depends on the following features:
GBFD-118621 Connection Inter BSC over IP (when inter-BSC IBCA is supported).
– This feature and the following features and functions are mutually exclusive:
GBFD-117001 Flex MAIO, the very early assignment function in GBFD-110502
Assignment and Immediate Assignment, GBFD-510104 Multi-site Cell,
GBFD-118106 Dynamic Power Sharing, GBFD-119406 High Speed Circuit Switched
Data, GBFD-114501 Co-BCCH Cell, and GBFD-113201 Concentric Cell features. .
If Soft-Synchronized Network is enabled, this feature and the feature GBFD-118601
Abis over IP are mutually exclusive.
l License
– The IBCA feature is implemented on a synchronous network. Therefore, the
transmission and power supply must be stable. If the transmission or power supply is
unstable, for example, the power supply is often disconnected, or transmission links are
disconnected intermittently, frequent synchronizations are performed and therefore call
drops occur. Only one transmission link disconnection and one out-of-lock alarm are
allowed each month at each site.

GBSS14.0
Context
When the network admits a new call, the interference between the established calls and the new
call is calculated. Based on the calculation result, the network assigns a channel with the
minimum interference to the new call. This minimizes the overall interference in the network
and therefore enables a tighter frequency reuse pattern. In addition, this increases the network
capacity while ensuring the voice quality in the entire network.

Principle for Different
Parameter Name Parameter ID Scenarios) Data Source
IBCA Info Report IBCAINBSCIN- Recommended value: 200 Engineering

Period Within BSC FORPTPRD If this parameter is set to a design
large value, the IBCA
interference measurement
result reporting is delayed and
the channel assignment is
affected.
Dyn Measurement NONIBCADYNM Recommended value: NO BSC internal

on a Non-IBCA EAEN (NO) planning
Neighbor Setting this parameter to YES
(YES) affects the accuracy of
the IBCA interference
measurement.
IBCA RxLev Offset IBCARXLEVOFF Recommended value: 10 BSC internal

SET planning
Interf. Priority INTERFPRIALL Recommended value: NO BSC internal

Allowed OW (No) planning
IBCA Allowed IBCAALLOWED Recommended value: YES BSC internal

(Yes) planning
IBCA Soft Block IBCASOFTBLKS Recommended value: YES BSC internal

Switch WITCH (Yes) planning
IBCA FR/EFR Soft IBCAFR- Recommended value: 4 BSC internal

Block Threshold SOFTBLKTHRD If the congestion rate is high planning
and TCH Traffic Busy
Threshold is set to a value
greater than 90, you can adjust
the value of this parameter in
steps of 1 or 2 dB.

GBSS14.0
IBCA HR Soft IBCAHR- Recommended value: 6 BSC internal

steps of 1 or 2 dB.
IBCA AMR FR Soft IBCAAFR- Recommended value: 2 BSC internal

steps of 1 or 2 dB.
IBCA AMR HR IBCAAHR- Recommended value: 4 BSC internal

Soft Block SOFTBLKTHRD If the congestion rate is high planning
Threshold and TCH Traffic Busy
steps of 1 or 2 dB.
IBCA WAMR FR IBCAWAFR- Recommended value: 5 BSC internal

Soft Block SOFTBLKTHRD If the congestion rate is high planning
Threshold and TCH Traffic Busy
steps of 1 or 2 dB.
IBCA Soft Block IBCASOFTBLKS Recommended value: 1 BSC internal

SAIC Offset AICOFF planning
IBCA Max. IBCAMAXINTFS Recommended value: 24 BSC internal

Interference Source RCNUM If this parameter is set to a planning
Num. small value, the calculated
interference is incorrect and
therefore the IBCA
evaluation is inaccurate,
affecting the network
performance.
IBCA Downlink IBCADLPATHLO Recommended value: 3 BSC internal

Path Loss Offset SSOFF planning
IBCA Service Cell IBCASCELLPAT Recommended value: 110 BSC internal

Pathloss HLOSS planning

GBSS14.0
IBCA Pathloss IBCAPATHLOSS Recommended value: 15 BSC internal

Offset OFF planning
IBCA Call IBCACALLINFO Recommended value: 4 BSC internal

Information Filter FILTERLEN planning
IBCA ICDM IBCAICDMSWIT Recommended value: NO BSC internal

Switch CH (No) planning
IBCA Path Lose IBCAPLFILTFAC Recommended value: 6 BSC internal

Filter Factor TOR planning
IBCA Pathloss Est IBCANCELLPAT Recommended value: 0 BSC internal

of Non. MR Ncell HLOSSESTIMAT planning
E
IBCA Non IBCANONMEAN Recommended value: 4 BSC internal

Measurement Ncell CELLSTATNUM planning
Stat. Num
IBCA MAIO Using IBCAMAIOUSM Recommended value: 0(Max. BSC internal

Method TD optimized MAIO) planning
IBCA Init. Power IBCAINITPCRXL Recommended value: 3 BSC internal

Control RexLevDL EVDLOFFSET If this parameter is set to a planning
Offset large value, the downlink
initial transmit power
increases.
IBCA Init. Power IBCAINITPCRXL Recommended value: 3 BSC internal

Control RexLevUL EVULOFFSET If this parameter is set to a planning
Offset large value, the uplink initial
transmit power increases.
IBCA Init. Pwr Ctrl IBCAINITPCRX- Recommended value: 6 BSC internal

Rx Qual DL Offset QUALDLOFFSE If this parameter is set to a planning
T large value, the downlink
initial transmit power
increases.
IBCA Init. Pwr Ctrl IBCAINITPCRX Recommended value: 6 BSC internal

Rx Qual UL Offset QUALULOFFSE If this parameter is set to a planning
T large value, the uplink initial
transmit power increases.
Target CIR Offset IBCANEWCALL Recommended value: 7 BSC internal

of IBCA New Call CIROFFSET planning
Target CIR Offset IBCACALLTAR Recommended value: 4 BSC internal

of IBCA Set-up Call GETCIROFFSET planning

GBSS14.0
IBCA Set-up Call IBCACALLSOFT Recommended value: 0 BSC internal

Soft Block BLOCKTHOFFS planning
Threshold Offset ET
Idle TCH Threshold IBCAFREEBCCH Recommended value: 0 BSC internal

on BCCH TRX CHANTHRSHOL If this parameter is set to a planning
D large value, the congestion
rate increases.
Procedure
Panel > Add Board; CME batch modification center: not supported) to add an XPUa
or XPUb board to the MPS or EPS. In this step, set Logical function type to MCP.
2. Run the BSC6900 MML command SET GTRXBASE (CME single configuration:
TRX Configuration Express > Basic Attributes of TRX > TRX Base; CME batch
modification center: 3.22 Modifying GSM TRX Parameters in Batches) command
with Maximum Number of PDCH of the TCH TRX set to 0.
NOTE
Disable dynamic PDCH conversion on the FH layer because it is not supported by IBCA.
3. Run the BSC6900 MML command MOD GCELLMAGRP (CME single
configuration: BTS Topology > Cell > Configure MA Group; CME batch
modification center: not supported) command with Hop Mode set to RF_FH(RF
FH) and Hop Mode set to an appropriate value.
Modifying GSM Cell Parameters in Batches) command to set its parameters as
listed in Table 190-1.
5. Run the BSC6900 MML command SET GCELLMAIOPLAN (CME single
modification center: not supported) command to with MAIO 1, MAIO 2, …, and
MAIO 24 set to appropriate values based on the cell MAIO plan.
6. Run the BSC6900 MML command SET GTRXCHANHOP (CME single
modification center: not supported) command with Channel MAIO set to an
appropriate value based on the MAIO plan.
Channel MAIO specifies the MAIO of the channel in the TRX. Eight channels in the
same TRX have the same MAIO.

GBSS14.0
NOTE
The MAIOs configured for TRXs in a cell are part of the MAIOs planned for the cell. For example,
two TRXs are configured for a cell but three MAIOs are planned for the cell. The first two MAIOs
are configured for the two TRXs.
7. Configure the IBCA interference neighboring cells.
– If Neighboring Cell Type of both a source cell and its neighboring cell on the
original network is HANDOVERNCELL(Handover Neighboring Cell), run the
MOD G2GNCELL (CME single configuration: Cell Configuration Express >
supported) command with Neighboring Cell set to
HANDOVERANDIBCANCELL(Handover and IBCA Neighboring Cell) and
IBCA RxLev Offset to 10.
– If no neighboring cells have been configured for the source cell on the original
network, run the ADD G2GNCELL (CME single configuration: Cell
Configuration Express > Neighboring Cell > BSC 2G Neighbor Cell; CME
batch modification center: not supported)command to add a neighboring cell for
the source cell. In this step, set Neighboring Cell Type to IBCANCELL(IBCA
Neighboring Cell) and set IBCA RxLev Offset to 10.
8. Configure the BSC software parameters.Run the BSC6900 MML command SET
OTHSOFTPARA (CME single configuration: GSM Global Configuration
Express > Software Parameter Configuration > Other Software Parameters of
BSC; CME batch modification center: 3.17 Modifying GBSC Parameters in
Batches) with IBCA Info Report Period Within BSC set to 200 and Dyn
Measurement on a Non-IBCA Neighbor set to NO(NO).
1. Trace the RSL signaling over the Abis interface in an IBCA-enabled cell.
2. Select the RSL signaling over the same timeslot of the same TRX board at different
time points.
3. Step 3 Compare MAIOs allocated to channels at different time points.
Expected result: The MAIOs are different, indicating that the IBCA algorithm takes
effect. Figure 190-1 and Figure 190-2 show different MAIOs.
Figure 190-1 MAIO 1

GBSS14.0
Figure 190-2 MAIO 2
1. Remove an IBCA interference neighboring cell.
– If Neighboring Cell Type of both a source cell and its neighboring cell on the
original network is HANDOVERNCELL(Handover Neighboring Cell), run the
MOD G2GNCELL (CME single configuration: Cell Configuration Express >
supported) command with Neighboring Cell Type set to HANDOVERNCELL
(Handover Neighboring Cell).
– If no neighboring cells have been configured for the source cell on the original
network, run the RMV G2GNCELL (CME single configuration: Cell
Configuration Express > Neighboring Cell > BSC 2G Neighbor Cell; CME
batch modification center: not supported) command to remove the configured
neighboring cell.
2. Run the SET GCELLCHMGAD (CME single configuration: Cell Configuration
Express > Channel Management > Advanced Channel Management Parameters
Batches) command with IBCA Allowed to NO(No).
CAUTION
Changing the HSN will cause cell resets. Therefore, perform this operation only when
the traffic is light.
3. Run the BSC6900 MML command MOD GCELLMAGRP (CME single

modification center: not supported) to set HSN to the value used before IBCA is
deployed.
----End
Example
//Activating IBCA
SET GTRXCHAN: TRXID=1, CHNO=2, CHTYPE=SDCCH8;
SET GTRXCHAN: TRXID=1, CHNO=3, CHTYPE=PDTCH;
SET GTRXBASE: TRXID=10, MAXPDCHNUM=0;

GBSS14.0
MOD GCELLMAGRP: IDTYPE=BYID, CELLID=0, HOPINDEX=0, HSN=0, TSC=4,

HOPMODE=RF_FH;
SET GCELLMAIOPLAN: IDTYPE=BYID, CELLID=0, HOPINDEX=0, MAIO1=0, MAIO2=3,
MAIO3=6;
SET GTRXCHANHOP: TRXID=1, CHNO=0, TRXMAIO=0;
……
NCELLTYPE=HANDOVERANDIBCANCELL, IBCARXLEVOFFSET=10;
NCELLTYPE=IBCANCELL, IBCARXLEVOFFSET=10;
SET OTHSOFTPARA: IBCAINBSCINFORPTPRD=200, NONIBCADYNMEAEN=NO;
SET GCELLCHMGAD: IDTYPE=BYID, CELLID=0, IBCAALLOWED=YES;
//Deactivating IBCA
MOD G2GNCELL: IDTYPE=BYID, SRC2GNCELLID=0, NBR2GNCELLID=1, NCELLTYPE=
HANDOVERNCELL;
RMV G2GNCELL: IDTYPE=BYID, SRC2GNCELLID=0, NBR2GNCELLID=1;
SET GCELLCHMGAD: IDTYPE=BYID, CELLID=0, IBCAALLOWED=NO;
MOD GCELLMAGRP: IDTYPE=BYID, CELLID=0, HOPINDEX=0, HSN=12;

GBSS14.0
Feature Activation Guide 191 Configuring Soft-Synchronized Network
191 Configuring Soft-Synchronized

Network
Soft-Synchronized Network. (This feature cannot be configured using the CME. )
Prerequisites
– The FG2a/FG2c/FG2d/GOUa/GOUc/GOUd board is configured.
– The BTS supports the feature Soft-Synchronized Network.
– The feature GBFD-118621 Connection Inter BSC over IP has been configured before
– This feature cannot be used together with the feature GBFD-118601 Abis over IP or
GBFD-510104 Multi-Site Cell.
– You are advised to use this feature together with GBFD-115801 ICC,GBFD-115821
EICC,GBFD-118103 Network Support SAIC and GBFD-117002 IBCA.
l License
– The BSC initial configuration is complete. The BSC is configured with at least two
BTSs.
– Each BTS is configured with at least two cells. In addition, the longitude, latitude, and
antenna azimuth of each cell are configured.
Context
The soft-synchronized network applies to the scenario of tight frequency reuse and requires the
cooperation of network planning and features such as IBCA. It can effectively improve the
performance of the KPIs associated with the wireless network. In addition, this feature can
convert an asynchronous network into a synchronous network. In cooperation with other
associated technologies, this technology eliminates random and unpredictable interference and
therefore increases the system capacity.

GBSS14.0
NOTE
l The BTS3900B and BTS3900E do not support this feature.

l This feature can be used together with the feature GBFD-117002 IBCA to improve the frequency
utilization and increase the network capacity.
l This feature is applicable to the scenario where TDM transmission is used between the BSC and BTS,
that is, Abis TDM over E1/T1/STM-1. In a scenario where an IP network is used between the BSC and
BTS, including Abis IP over E1/T1/STM-1 and Abis IP over FE/GE, the Soft-Synchronized Network
feature is not supported.
Procedure
Configuring an intra-BSC soft-synchronized network
1. Run the BSC6900 MML command SET BTSAISS. In this step, specify BTS Index
(Not required on the CME) or BTS Name of the BTS to participate in the intra-BSC
soft-synchronized task. To configure multiple BTSs, run this command for each BTS
you want to add. Site Sync Zone of each BTS must be set to the same value.
NOTE
BTS Symbol Offset is optional. This parameter specifies the frame offset between BTSs and
is set as required.
2. Run the BSC6900 MML command ADD AISSCFG. In this step, set Reference BTS
Index (Not required on the CME) to the index of the BTS that supports the soft-
synchronized network. In addition, set both Offset Information Collection Switch
and Offset Time Adjustment Switch to ON(ON) and Support BSC AISS to NO
(NO).
3. Optional: Run the BSC6900 MML command ADD NCELL to add a pair of
neighboring cells in the BSC. In this step, set AISS Task Index to the index of the
soft-synchronized network task specified in Step 1. Then, set First Cell Index and
Second Cell Index to appropriate values.
NOTE
A pair of neighboring cells in the BSC are automatically generated based on certain rules. If
the neighboring cells do not meet the measurement requirements, reconfigure the neighboring
cells as required.
Configuring an inter-BSC soft-synchronized network

The configuration of the soft-synchronized network between BSC1 and BSC2 is used as
an example. Each BSC has only one BTS. IP-based inter-BSC interconnection is
configured.
1. Run the BSC6900 MML command SET BTSAISS at BSC1 and BSC2 respectively.
In this step, specify BTS Index (Not required on the CME) or BTS Name of the BTS
to participate in the intra-BSC soft-synchronized task. Site Sync Zone of each BTS
must be set to the same value.
2. Run the BSC6900 MML command ADD AISSCFG at BSC1. In this step, set
Reference BTS Index (Not required on the CME) to the index of the BTS that supports
the soft-synchronized network. In addition, set Offset Time Adjustment Switch and
Offset Information Collection Switch to ON(ON), and set Support BSC AISS and
Base BSC to YES(YES).
3. Run the BSC6900 MML command ADD AISSCFG at BSC2. In this step, set
Reference BTS Index (Not required on the CME) to the index of a BTS that supports

GBSS14.0
the soft-synchronized network. In addition, set Offset Time Adjustment Switch and
Offset Information Collection Switch to ON(ON), Support BSC AISS to YES,
Base BSC to NO, and Control BSC DPC to the DPC of BSC1.
4. Run the BSC6900 MML command ADD GEXT2GCELL at BSC1 to configure a
cell under BSC2 as an external cell of BSC1.
5. Run the BSC6900 MML command ADD G2GNCELL at BSC1 to configure the
external cell added in Step 4 as a neighboring cell of a cell under BSC1.
6. Run the BSC6900 MML command ADD EXTNCELL at BSC1 to add a pair of
neighboring cells between BSCs.
NOTE
A pair of neighboring cells between BSCs are automatically generated according to certain rules. If
the neighboring cells do not meet the measurement requirements, reconfigure the neighboring cells
as required. Steps 4 to 6 are performed to add a pair of optimal neighboring cells between BSCs.
Verifying the intra-BSC soft-synchronized network
1. Run the BSC6900 MML command LST AISSCFG to query the information about
the soft-synchronized network.
NOTE
If you do not specify AISS Task Index, the information about all the soft-synchronized network
tasks is queried.
Expected result: Check whether AISS Task Index of the added intra-BSC soft-
synchronized network exists. If the index exists, the intra-BSC soft-synchronized
network is added successfully.
2. Run the BSC6900 MML command DSP NCELLTBL to query information about
neighboring cell pairs within a BSC.
3. Run the BSC6900 MML command DSP AISSRUNSTATE to query the BTS
synchronization information.
4. Run the BSC6900 MML command DSP BTSSYNCINFO to query the frame offset
in the synchronization between BTSs.
Verifying the inter-BSC soft-synchronized network
1. Run the BSC6900 MML command LST AISSCFG to query the information about
the soft-synchronized network.
Expected result: The value of Support BSC AISS for BSC1 is YES and the value of
Control BSC DPC for BSC2 is the signaling point of the control BSC.
2. Run the BSC6900 MML command DSP BSCSYNCINFO to query the information
about the synchronization between BSCs.
NOTE
l Set Adjacent BSC DPC to the signaling point of BSC1 to query the state of the local BSC.
l Set Adjacent BSC DPC to the signaling point of BSC2 to query the state of the
collaborative BSC.
Expected result: The value of BSC Sync State for BSC1 and BSC2 is Adjusted.
3. Run the BSC6900 MML command DSP BTSSYNCINFO to query the frame offset
in the synchronization between BTSs.
Expected result: The value of BTS status for the BTS is Synchronized.

GBSS14.0
1. Run the BSC6900 MML command RMV AISSCFG to remove a soft-synchronized
network task. In this step, specify BTS Index (Not required on the CME) or BTS
Name of the BTS involved in the intra-BSC or inter-BSC soft-synchronized network.
----End
Example
//Activating Soft-Synchronized Network
SET BTSAISS: IDTYPE=BYIDX, BTSID=0, SYMOFFSET=12, SITESYNCZONE=1;
ADD AISSCFG: TASKIDX=0, GATHON=ON, ADTON=ON, BASEBTSID=0, REINITTBL=NO,
ISSPTBSCAISS=NO, ISBASICBSC=YES, GATHST=00&10, GATHET=08&50,
BSCGATHST=10&00, BSCGATHET=12&00;
//Deactivating Soft-Synchronized Network
RMV AISSCFG: TASKIDX=0;

GBSS14.0
Feature Activation Guide 192 Configuring BTS GPS Synchronization
192 Configuring BTS GPS

Synchronization
This section describes how to activate the optional feature GBFD-510401 BTS GPS
Synchronization.
Prerequisites
– The BTS3006C, BTS3002E, and BTS3900B/E do not support the feature.
– In the case of the BTS3012/BTS3012AE, the DGPS board needs to be added.
– In the case of the DBS3900/BTS3900/BTS3900A, the USCU board needs to be added.
l License
l Others
– In Frame Bit Offset can be changed only in TDM mode.
Context
Converting an asynchronous network into a synchronous network can effectively reduce the
interference, increase the network capacity, and improve the performance of the KPIs related to
the radio network.
The following procedure takes how to configure the GPS synchronization of the BTS3900 GSM
as an example.
Procedure
1. Run the BSC6900 MML command ADD BTSBRD (CME single configuration: BTS
Device Panel > Board > BTS Board; CME batch modification center: not supported)
to add a USCU board. In this step, set Board Type to USCU(USCU).

GBSS14.0
Feature Activation Guide 192 Configuring BTS GPS Synchronization
2. Run the BSC6900 MML command SET BTSUSCUBP (CME single configuration:
BTS Device Panel > Right click USCU Board > Properties > USCU Board
Parameters; CME batch modification center: not supported). In this step, set Board
Parameter Configuration Enabled to YES(YES), 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 needs to be 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 needs to be set according to the feeder length.
modification center: 3.18 Modifying GBTS Parameters in Batches). In this step, set
Clock Type to TRCGPS_CLK(Trace GPS Clock).
4. Optional: Run the BSC6900 MML command SET BTSCLK (CME single
configuration: BTS Configuration Express > BTS Basic Attributes > Clock Type
of BTS; CME batch modification center: 3.18 Modifying GBTS Parameters in
Batches) at the sites where same frequencies and TSCs are configured. In this step,
set In Frame BitOffset to 0 for one BTS.
5. Optional: Run the BSC6900 MML command SET BTSCLK (CME single
configuration: BTS Configuration Express > BTS Basic Attributes > Clock Type
of BTS; CME batch modification center: 3.18 Modifying GBTS Parameters in
Batches). In this step, set In Frame BitOffset to 80 for the other BTS.
None.
----End
Example
ADD BTSBRD: IDTYPE=BYID, BTSID=9, CN=0, SRN=0, SN=0, BT=USCU;
SET BTSUSCUBP: IDTYPE=BYID, BTSID=9, CN=0, SRN=0, SN=0, CFGFLAG=YES,
GPSORGLONASS=GPS, ANTENNALONG=800, ANTENNAPOWERSWITCH=NOPOWER;
SET BTSCLK: IDTYPE=BYID, BTSID=9, ClkType=TRCGPS_CLK;
SET BTSCLK: IDTYPE=BYID, BTSID=9, ClkType=TRCGPS_CLK, FRAMEBITOFFSET=0;
SET BTSCLK: IDTYPE=BYID, BTSID=10, ClkType=TRCGPS_CLK, FRAMEBITOFFSET=80;

GBSS14.0
Feature Activation Guide 193 Configuring Network Support SAIC
193 Configuring Network Support SAIC
Network Support SAIC.
Prerequisites
l License
– The MS supports Single Antenna Interference Cancellation (SAIC).
Context
SAIC is a technique that restraints both intra-frequency and inter-frequency interference when
the MS receives signals through a single antenna. SAIC aims to minimize the impact of
interference on the receive quality of downlink signals through signaling processing.
The SAIC-capable MS has a greater capability of bearing interference than the SAIC-incapable
MS. Therefore, the power control policy can be adjusted for the SAIC-capable MS to reduce the
transmit power of the BTS, reducing interference in the entire network.
Procedure
Cell Parameters in Batches). In this step, set SAIC Allowed to YES(Yes).
2. Set power control adjustment.
– When Huawei II power control algorithm is used:

GBSS14.0
a. Run the BSC6900 MML command SET GCELLPWR2 (CME single

configuration: Cell Configuration Express > Power Control > Parameters
for Power Control II of Cell; CME batch modification center: 3.20
Modifying GSM Cell Parameters in Batches). In this step, set Power
Control Threshold Adjust for SAIC to 1.
b. Run the BSC6900 MML command SET GCELLSOFT (CME single
Reserved Parameter > Software Parameters of Cell; CME batch
modification center: 3.20 Modifying GSM Cell Parameters in Batches). In
this step, set Switch for BTS Supporting SAIC PC Adjust to ON(On).
– When Huawei III power control algorithm is used:
a. Run the BSC6900 MML command SET GCELLPWR3 (CME single
configuration: Cell Configuration Express > Power Control > Parameters
for Power Control III of Cell; CME batch modification center: 3.20
Modifying GSM Cell Parameters in Batches). In this step, set Power
Control Threshold Adjust for SAIC to 3.
1. On the BSC6900 LMT, initiate A interface message tracing by referring to Tracing
Messages on the A Interface. Use the MS to make a CS voice call. Check the value
of Downlink Advanced Receiver Performance in the information element (IE)
classmark-information-type3 of the Classmark Update message. This value indicates
the SAIC capability of the MS.
Expected result: The value of Downlink Advanced Receiver Performance is Support
SAIC.
2. On the BSC6900 LMT, initiate Abis interface RSL message tracing by referring to
Tracing CS Domain RSL Messages on the Abis Interface. Check the value of the user-
defined IE MS Capability in the channel activation command sent from the
BSC6900 to the BTS during the assignment request process.
Expected result: The value of SAIC support capability is 1. This indicates that the MS
supports SAIC.
Cell Parameters in Batches). In this step, set SAIC Allowed to NO(No).
2. When Huawei II power control algorithm is used, Run the BSC6900 MML
command SET GCELLSOFT (CME single configuration: Cell Configuration
Express > Software Parameter and Reserved Parameter > Software Parameters
Batches). In this step, set Switch for BTS Supporting SAIC PC Adjust to OFF
(Off).
----End
Example
//Activating Network Support SAIC
SET GCELLPWRBASIC: IDTYPE=BYID, CELLID=0, SAICALLOWED=YES;
SET GCELLPWR2: IDTYPE=BYID, CELLID=0, SAICTHREDAPDTVALUE=1;
SET GCELLSOFT: IDTYPE=BYID, CELLID=0, BTSSAICPCADJSWITCH=ON;

GBSS14.0
//Deactivating Network Support SAIC

SET GCELLPWRBASIC: IDTYPE=BYID, CELLID=0, SAICALLOWED=NO;
SET GCELLSOFT: IDTYPE=BYID, CELLID=0, BTSSAICPCADJSWITCH=OFF;

GBSS14.0
Feature Activation Guide 194 Configuring Mega BSC
194 Configuring Mega BSC
Mega BSC. With this feature, a BSC supports a maximum of 8192 TRXs when IP over FE/GE/
STM-1 is used over the A, Abis, and Gb interfaces. This feature enables a BSC to support more
subscribers while maintaining the speech quality.
Prerequisites
– This feature depends on features GBFD-118601 Abis over IP, GBFD-118602 A over
IP, and GBFD-118603 Gb over IP.
l License
– The license controlling this feature has been activated with the license items Maximum
TRX number allowed Resource (per TRX) and Mega BSC (per TRX) set to 8192 both.
– The BSC6900 hardware version must be V900R013 or later. The BSC boards must be
DPUf, DPUg, XPUb, SCUb, GCUa, GCGa, OMUc, FG2c, FG2d, GOUc, GOUd, or
POUc.
– 10GE ports numbered from 8 to 11 are recommended for the interconnection between
SCUb boards. The SCUbs are connected in star mode, and support 8192 TRXs in only
three subracks that are fully configured.
– The TRX specification of each interface board, DPU board, and XPU board does not
change. The BSC capacity expansion is achieved by adding the number of configured
interface boards, DPU boards, and XPU boards.
– IP over FE/GE/STM-1 is used over the A, Abis, and Gb interfaces.
– This feature does not have any requirements for other NEs or third-party devices.
– This feature does not have any other prerequisites.
Context
l Note

GBSS14.0
– None
l Data Preparation
– This feature does not require data preparations.
Procedure
– For a newly deployed site:
1. The activation method is the same as that for initial configuration. For details, see
the BSC6900 GSM Initial Configuration Guide. A BSC supports a maximum of
8192 TRXs.
– For reconfiguration:
To enable a BSC to support a maximum of 8192 TRXs, perform the following steps:
1. Add a TRX board by referring to Configuring RF Units.
2. Run the BSC6900 MML command ADD GCELLFREQ (CME single
configuration: BTS Topology > Right click GSM cell > Assign Frequency; CME
batch modification center: not supported) to add a frequency for the cell.
3. Run the BSC6900 MML command ADD GTRX (CME single configuration: BTS
Topology > Right click Cell > ADD TRX; CME batch modification center: not
supported) to add a TRX.
4. Run the BSC6900 MML command ADD TRXBIND2PHYBRD (CME single
configuration: BTS Topology > Right click GSM cell > Add TRX; CME batch
modification center: not supported) to add the binding relationship between the
logical TRX and the physical TRX board.
5. Run the BSC6900 MML command SET GTRXCHAN (CME single
configuration: TRX Configuration Express > Channel Type > Channel Type;
CME batch modification center: 3.22 Modifying GSM TRX Parameters in
Batches) to set the TRX channel information.
Property; CME batch modification center: 3.22 Modifying GSM TRX
Parameters in Batches) to set the attributes for the TRX board.
1. Query the channel usage of newly added TRXs by referring to Monitoring Channel
Status.
Expected result: The channels of newly added TRXs can be used.
----End
Example
/*Activation Procedure*/
//Adding a frequency for the cell
//Adding a TRX
ADD GTRX: IDTYPE=BYID, CELLID=1, TRXID=1, TRXNAME="TRX_1", FREQ=2,
ISMAINBCCH=NO, TRXNO=1;

GBSS14.0
//Adding the binding relationship between the logical TRX and the physical
TRX board
ADD TRXBIND2PHYBRD: TRXIDTYPE=BYID, TRXID=1, IDTYPE=BYID, BTSID=0,
TRXTP=TRU, TRXPN=0, CN=0, SRN=1, SN=4;
//Setting the TRX channel information
SET GTRXCHAN: IDTYPE=BYID, TRXID=1, CHNO=0, CHTYPE=TCHFR,
GPRSCHPRI=EGPRSNORCH, TSPRIORITY=0, CHANRSV=NO;
//Setting the attributes for the TRX board
SET GTRXDEV: IDTYPE=BYID, TRXID=1, POWL=3, POWT=DEFAULT, OPTL=L0,
SDFLAG=ENABLE, TCHAJFLAG=NO, PL8PSK=0,
PWRSPNR=DEFAULT, RCVMD=INDEPENDENT, SNDMD=NOCOMB, CPS=YES,
FREQREUSEMODE=LOOSE, PAOPTILEVEL=L3,
OUTHOPWROVERLOADTHRESHOLD=15, INHOPWROVERLOADTHRESHOLD=8, PL16QAM=0,
PL32QAM=0, DSSTRXOFFLINE=NO;

GBSS14.0
Feature Activation Guide 195 Configuring PS Downlink DTX
195 Configuring PS Downlink DTX
PS Downlink DTX. With the PS Downlink DTX feature, the BSC decreases the number of
dummy control blocks sent on PDCHs and the number of data blocks unnecessarily retransmitted
over the Um interface. This reduces the BTS power consumption and network interference,
improving the service quality.
Prerequisites
– This feature cannot be used together with the feature GBFD-119202 Packet Assignment
Taken Over by the BTS.
l License
– A built-in PCU is configured. That is, the DPUd or DPUg board is configured.
– This feature does not have any special requirements for the transmission network.
– This feature does not have any special requirements for other NEs or third-party devices.
– Support DL PACK Retransmission is set to YES(YES).
Context
This feature applies to two scenarios: no MS access and no valid data to be sent.
l No MS access indicates that no uplink or downlink TBF is established on a PDCH. When
PS Downlink DTX is enabled in this scenario, downlink dummy blocks are not sent on this
PDCH, achieving downlink discontinuous transmission.
l No valid data to be sent indicates that no single block assignment is triggered on a PDCH,
or an uplink or downlink TBF is established on a PDCH but are not scheduled by Uplink
State Flag (USF) or Relative Reserved Block Period (RRBP). When PS Downlink DTX is

GBSS14.0
enabled in this scenario, downlink dummy blocks are not sent on this PDCH, achieving
downlink discontinuous transmission.
l When the downlink PACK retransmission function is enabled, the frequency for sending
downlink PACK blocks can be modified.
l Precautions
– None
l Data Preparation

Name
PS DTX PSDTX Setting this parameter to Network

DTX(ON when no MS is planning
accessed) or
ENHANCEDDTX(ON
when no valid data
needs to be sent) shuts
down the TRX power
amplifier in off-peak
hours. This reduces power
consumption and network
interference over the Um
interface. Setting this
parameter to
ENHANCEDDTX(ON
when no valid data
needs to be sent)
enhances the optimization
effect, but deteriorates the
accessibility because MSs
with poor compatibility
cannot properly send
uplink data.

GBSS14.0

Name
DL PACK Block DlPACKSENDPERIOD If this parameter is set to a Network

Send Period large value, the number of planning
PACK blocks sent by the
BSC decreases.
Therefore, interference
with the network
decreases, and the PS
delay and retransmission
rate increase when the
block error rate is high. If
this parameter is set to a
small value, the number
of PACK blocks sent by
the BSC increases.
Therefore, interference
with the network
increases, and the PS
delay and retransmission
rate decrease when the
block error rate is high.
Procedure
set PS DTX to DTX(ON when no MS is accessed) or ENHANCEDDTX(ON when
no valid data needs to be sent).
Parameters in Batches). In this step, set DL PACK Block Send Period to any values
other than 0.
– No MS access
1. Start Um Interface PS Trace and select Dummy Message to query whether Packet
Downlink Dummy Control Block messages are sent on non-occupied PDCHs on
non-BCCH TRXs.
Expected result: Packet Downlink Dummy Control Block messages are not sent
on non-occupied PDCHs on non-BCCH TRXs.
– No valid data to be sent
1. Start Um Interface PS Trace and select Dummy Message to query whether Packet
Downlink Dummy Control Block messages are sent on non-occupied PDCHs on
non-BCCH TRXs.

GBSS14.0
Expected result: Packet Downlink Dummy Control Block messages are not sent
on non-occupied PDCHs on non-BCCH TRXs.
2. Use an MS supporting GPRS or EGPRS to perform a PS ping test. During the ping
test, check in the Um Interface PS Trace results:
– The period of sending PACK blocks during the delayed downlink TBF release
period after the downlink data transmission is complete.
– Packet Downlink Dummy Control Block message is displayed after Packet
Downlink Ack/Nack or Egprs Packet Downlink Ack/Nack whose FAI is 1
in the Um Interface PS Trace results.
Expected result:
– The period of sending PACK blocks during the delayed downlink TBF release
period is longer than or equal to the period specified by DL PACK Block Send
Period.
– No Packet Downlink Dummy Control Block message is displayed after
Packet Downlink Ack/Nack or Egprs Packet Downlink Ack/Nack whose
FAI is 1.
set PS DTX to OFF(OFF).
Parameters in Batches). In this step, set DL PACK Block Send Period to 0.
----End
Example
/*Activating PS Downlink DTX*/
//No MS access
SET GCELLPRIVATEOPTPARA: IDTYPE=BYID, CELLID=0, PSDTX=DTX;
SET GCELLPSOTHERPARA: IDTYPE=BYID, CELLID=0, DlPACKSENDPERIOD=5;
//No valid data to be sent

SET GCELLPRIVATEOPTPARA: IDTYPE=BYID, CELLID=0, PSDTX= ENHANCEDDTX;
/*Deactivating PS Downlink DTX*/

SET GCELLPRIVATEOPTPARA: IDTYPE=BYID, CELLID=0, PSDTX=OFF;

GBSS14.0
Feature Activation Guide 196 Configuring PS Uplink DTX
196 Configuring PS Uplink DTX
PS Uplink DTX. With the PS Uplink DTX feature, the BSC decreases the frequency of
scheduling extended uplink TBFs in inactive periods or sends system information instructing
MSs not to send dummy control blocks for extended uplink TBFs in inactive periods. This
reduces the MS power consumption and network interference, improving the service quality.
Prerequisites
– The feature GBFD-119203 Extended Uplink TBF has been configured before this
feature is activated.
l License
– A built-in PCU is configured. That is, the DPUd or DPUg board is configured.
– This feature does not have any special requirements for the transmission network.
– None
Context
When PS Uplink DTX is enabled, if an MS confirms that the BSC has correctly received all
uplink data blocks, and no uplink dummy block is sent on the uplink extended TBF in the inactive
period, the BSC does not abnormally release uplink TBF even if N3101 overflows. With PS
Uplink DTX enabled, the BSC can reduce the frequency for scheduling the uplink TBF in the
inactive period.
l Precautions
– None
l Data Preparation

GBSS14.0

Name Source
Not Send EXTUTBFNODATA Set this parameter to SEND Network

Dummy (SEND) if the Inactive Period of planning
Message Extended Uplink TBF
with parameter in the SET
Extended GCELLPRIVATEOPTPARA
Uplink TBF (CME single configuration: Cell
Configuration Express >
GPRS Attributes >
Customized Network
Optimization Parameters of
2G Cell; CME batch
modification center: 3.20
Modifying GSM Cell
Parameters in Batches)
command is set to 0. Set this
parameter to SEND(SEND) or
NOTSEND(NOTSEND) if the
Inactive Period of Extended
Uplink TBF parameter in the
SET
GCELLPRIVATEOPTPARA
(CME single configuration: Cell
Configuration Express >
GPRS Attributes >
Customized Network
Optimization Parameters of
2G Cell; CME batch
modification center: 3.20
Modifying GSM Cell
Parameters in Batches)
command is set to a value other
than 0.
If this parameter is set to SEND
(SEND), the traffic volume on
the Um interface and the MS
power consumption increase. If
this parameter is set to
NOTSEND(NOTSEND), the
traffic volume on the Um
interface and MS power
consumption decrease.

GBSS14.0

Name Source
Scheduling INACTSCHPERIOD The larger the value of this Network

Period for parameter, the longer the planning
Inactive minimum access delay in
Periods transmitting uplink data for
extended uplink TBFs in inactive
periods and the fewer uplink
dummy control blocks sent by the
MS. The smaller the value of this
parameter, the shorter the
minimum access delay in
transmitting uplink data for
extended uplink TBFs in inactive
periods and the more uplink
dummy control blocks sent by the
MS.
Inactive UPEXTTBFINACTDELAY Setting this parameter to a large Network

Period of value increases the uplink TBF planning
Extended release delay, wasting uplink
Uplink TBF resources. Setting this parameter
to a small value leads to frequent
uplink TBF releases and
establishments, increasing the
delay in the delay tests for the
Attach and Ping services. Set the
release delay a little longer than
the duration of the interval
between two discontinuous
uplink transmissions.
Procedure
Parameters in Batches). In this step, set Not Send Dummy Message with Extended
Uplink TBF to NOTSEND(NOTSEND), PS Uplink DTX Optimization to ON
(On) and Scheduling Period for Inactive Periods to any values other than 0.
1. Start Um Interface PS Trace and select Dummy Message to query the value of ext-
utbf-no-data in Packet PSI13.
Expected result: The value of ext-utbf-no-data is 1.

2. Use an MS that supports PS Uplink DTX, that is, an MS that does not send dummy
control blocks when extended uplink TBFs are in inactive periods, to perform PS
service verification. In the PS Um tracing result, check whether there is a Packet

GBSS14.0
Uplink Dummy Control Block message after the Uplink Data Block message whose
countdown field is 0.
Expected result: The MS does not send the Packet Uplink Dummy Control Block
message after confirming that the BSC has sent all uplink data blocks.
3. Use an MS that does not support PS Uplink DTX, that is, an MS that still sends dummy
control blocks when extended uplink TBFs are in inactive periods, to perform PS
service verification. In the PS Um tracing result, check whether there is a result on
whether the interval between two times of scheduling is greater than or equal to the
specified period of scheduling extended uplink TBFs in inactive periods after the
Uplink Data Block message whose countdown field is 0.
Expected result: After an MS confirms that all uplink data blocks have been sent on
the network side, the interval between two times of scheduling is greater than or equal
to the specified period of scheduling extended uplink TBFs in inactive periods.
Parameters in Batches). In this step, set Not Send Dummy Message with Extended
Uplink TBF to SEND(SEND), PS Uplink DTX Optimization to OFF(Off) and
Scheduling Period for Inactive Periods to 0.
----End
Example
//Activating PS Uplink DTX
SET GCELLPSBASE: IDTYPE=BYID, CELLID=0, EXTUTBFNODATA=NOTSEND,
PsDtxLaOptiSwitch=ON, INACTSCHPERIOD=5;
//Deactivating PS Uplink DTX

SET GCELLPSBASE: IDTYPE=BYID, CELLID=0, EXTUTBFNODATA=SEND,
PsDtxLaOptiSwitch=OFF, INACTSCHPERIOD=0;

GBSS14.0
Feature Activation Guide 197 Configuring Automatic Frequency Correction (AFC)
197 Configuring Automatic Frequency

Correction (AFC)
This section describes how to activate, verify, and deactivate the feature GBFD-510101
Automatic Frequency Correction (AFC).
Prerequisites
– This feature cannot be used together with the feature GBFD-115821 EICC,
GBFD-115830 VAMOS, or GBFD-115832 VAMOS Call Drop Solution.
l License
– Only the RRU3008 V1 and RRU3908 V1 supports this feature in the downlink.
– None
Context
AFC is a frequency correction algorithm used on the base station side for fast-moving MSs. It
ensures reliability of radio links carrying high-quality speech services for MSs moving at 500
km/h and also ensures service continuity.

GBSS14.0
UL Frequency FREQADJ The parameter Network plan

Adjust Switch determines whether
to enable the
automatic frequency
correction function
in the uplink for the
BTS. Enable this
function in high-
speed railway
scenarios. Use the
parameter in other
scenarios.
DL Frequency DLFREQADJ The parameter Network plan

Adjust Switch determines whether
to enable the
automatic frequency
correction function
in the downlink for
the BTS. This
function must be
enabled with the
automatic frequency
correction function
in the uplink.
Procedure
Parameters in Batches).
If... Then...
The AFC function needs to be enabled Set UL Frequency Adjust Switch to

in the uplink YES(Yes).
The AFC function needs to be enabled Set both UL Frequency Adjust

in the downlink Switch and DL Frequency Adjust
Switch to YES(Yes).
1. Run the BSC6900 MML command LST GCELLOTHEXT.

GBSS14.0
If... Then...
The value of UL Frequency Adjust The AFC function is enabled in the

Switch is YES(Yes) uplink.
The values of both UL Frequency The AFC function is enabled in the

Adjust Switch and DL Frequency downlink.
Adjust Switch are YES(Yes)
2. Initiate a call in a fast-moving vehicle. On the LMT, click Trace. In the navigation
tree, choose Trace > GSM Services > Abis Interface CS Trace. In the displayed
dialog box, click RSL in the Trace Type area. Then, check the value of Uplink
Receive Quality in the measurement report. If the AFC function has been activated,
the value of Uplink Receive Quality decreases.
NOTE
Uplink Receive Quality is specified by the "rxquel-ul" field in the measurement report. The
value ranges from 0 to 7. A small value indicates good quality, for example, 0 indicates that
the quality is the best. A large value indicates poor quality, for example, 7 indicates that the
quality is the worst.
Parameters in Batches). In this step, set UL Frequency Adjust Switch and DL
Frequency Adjust Switch to NO(No).
----End
Example
//Activating Automatic Frequency Correction (AFC)
SET GCELLOTHEXT: IDTYPE=BYID, CELLID=0, FREQADJ=YES, DLFREQADJ=YES;
//Verifying Automatic Frequency Correction (AFC)
LST GCELLOTHEXT: IDTYPE=BYID, BTSID=0, CELLID=0;
//Deactivating Automatic Frequency Correction (AFC)
SET GCELLOTHEXT: IDTYPE=BYID, CELLID=0, FREQADJ=NO, DLFREQADJ=NO;

GBSS14.0
Feature Activation Guide 198 Configuring Fast Move Handover
198 Configuring Fast Move Handover
Fast Move Handover.
Prerequisites
– The BTS3900B and BTS3900E do not support the feature.
feature depends on the feature GBFD-510103 Chain Cell Handover.
l License
Context
Handovers along railway lines need to be completed quickly because users move fast from the
coverage of one cell to that of another cell. To reduce failures, a second handover must be
initiated quickly upon a handover failure (for example, interference occurs abruptly on the radio
interface). The fast move handover algorithm, which is optimized on the basis of the current
algorithm, can trigger better cell handover within a short period.
Procedure
Parameters in Batches). In this step, set both Quick Handover Enable and Quick
PBGT Handover Enable to YES(Yes).
2. Run the BSC6900 MML command SET GCELLHOFAST (CME single
configuration: Cell Configuration Express > Handover Data > Fast Handover
Parameters in Batches). In this step, set Quick Move Speed Threshold, Quick
Handover Up Trigger Level, Quick Handover Down Trigger Level, Quick

GBSS14.0
Handover Offset, Quick Handover Punish Time, Quick Handover Punish

Value, Serving Cell Filter Length MR Number, Neighbor Cell Filter Length MR
Number, Ignore Measurement Report Number, EN Quick PBGT HO ALG
When MS Leaves BTS, Handover Direction Forecast Enable, Handover
Direction Forecast Statistic Times, Frequency Shift Handover Statistic Time, and
Frequency Shift Handover Duration to appropriate values.
NOTE
You can Run the BSC6900 MML command LST G2GNCELL (CME single configuration:
Cell Configuration Express > Neighboring Cell > BSC 2G Neighbor Cell) to query
information about the neighboring cells of this cell.
If this cell is configured with external neighboring cells, Run the BSC6900 MML command
MOD GEXT2GCELL (CME single configuration: Object Group > GSM Service
Configuration and Maintenance Management > External Cell Configuration > BSC 2G
External Cell; CME batch modification center: 3.21 Modifying BSC External Cell
Parameters in Batches) to set Quick Handover Offset, Quick Handover Punish Time, and
Quick Handover Punish Value to appropriate values.
Parameters in Batches). In this step, set UL Frequency Adjust Switch and UL
Frequency Adjust Value to appropriate values.
1. Move the MS away from the serving cell until the frequency offset in the measurement
report, CH RQD, or HO DETECT message is a negative value and the moving speed
of the MS is greater than Quick Move Speed Threshold. When the frequency offset
information fails to be reported or the frequency offset information is invalid, the
uplink level in the serving cell is lower than Quick Handover Up Trigger Level, the
downlink level in the serving cell is lower than Quick Handover Down Trigger
Level, and the path loss of chain neighboring cells is lower than the path loss of the
serving cell minus the sum of Quick Handover Offset and Quick Handover Offset
for Neighbor Cell.
2. On the LMT, trace BSSAP messages over the A interface.
Expected result: The BSC sends a Handover Performed message to the MSC with the
handover cause value "better-cell".
Parameters in Batches). In this step, set Quick PBGT Handover Enable set to NO
(No).
NOTE
Quick handover algorithms consist of the frequency offset handover algorithm and the quick
PBGT handover algorithm. Quick Handover Enable is the switch that controls the frequency
offset handover and the quick PBGT handover. Run the BSC6900 MML command SET
GCELLHOBASIC (CME single configuration: Cell Configuration Express > Handover
Data > Basic Handover Parameters of Cell; CME batch modification center: 3.20 Modifying
GSM Cell Parameters in Batches). In this step, you can deactivate the quick PBGT handover
by setting Quick Handover Enable to NO(No), but the frequency offset handover is also
deactivated.
----End

GBSS14.0
Example
// Activating Fast Move Handover
SET GCELLHOBASIC: IDTYPE=BYID, CELLID=1024, QUICKPBGTHOEN=YES;
MOVESPEEDTHRES=35, MSLEVSTRQPBGT=YES;
SET GCELLOTHEXT: IDTYPE=BYID, CELLID=1024, FREQADJ=YES, FREQADJVALUE=255;
//Deactivating Fast Move Handover
SET GCELLHOBASIC: IDTYPE=BYID, CELLID=1024, QUICKPBGTHOEN=NO;

GBSS14.0
Feature Activation Guide 199 Configuring Chain Cell Handover
199 Configuring Chain Cell Handover
Chain Cell Handover.
Prerequisites
l License
Context
This feature enables fast-moving MSs to move in chain cells by predicting the moving direction
and thereby increases the handover success rate and improves service quality.
Procedure
batch modification center: not supported) to add a neighboring cell. In this step, set
Chain Neighbor Cell to YES(Yes). If a cell has been added as a neighboring cell,
Run the BSC6900 MML command MOD G2GNCELL (CME single configuration:
batch modification center: not supported). In this step, set Neighboring Cell Type to
HANDOVERNCELL(Handover Neighboring cell) and Chain Neighbor Cell to
YES(Yes).
1. Run the BSC6900 MML command LST G2GNCELL to query the value of Chain
Neighbor Cell.
Expected result: The value of Chain Neighbor Cell is YES(Yes).

GBSS14.0
Feature Activation Guide 199 Configuring Chain Cell Handover
1. Run the BSC6900 MML command MOD G2GNCELL (CME single configuration:
batch modification center: not supported). In this step, set Chain Neighbor Cell to
NO(No).
----End
Example
//Activating Chain Cell Handover
NCELLTYPE=HANDOVERNCELL, SRCHOCTRLSWITCH=HOALGORITHM1, ISCHAINNCELL=YES;
//Verifying Chain Cell Handover
LST G2GNCELL: IDTYPE=BYID, SRC2GNCELLID=1024, NBR2GNCELLID=2542;
//Deactivating Chain Cell Handover
NCELLTYPE=HANDOVERNCELL, ISCHAINNCELL=NO;

GBSS14.0
Feature Activation Guide 200 Configuring Multi-Site Cell
200 Configuring Multi-Site Cell
Multi-Site Cell.
Prerequisites
– The base station must be DBS3900.
– Table 200-1 lists the rules for mixed RXU configuration.
Table 200-1 Rules for mixed RXU configuration
Scenario Rules for Mixed RXU Configuration
RXUs configured in Only the following mixed RXU combinations can be

the same subsite configured:
l RRU3008 V1+RRU3008 V2
l RRU3908 V1+RRU3908 V2
RXUs configured in All RRUs (except the RRU3004) that use the same frequency
different subsites in a band can be configured in a mixed manner.
multi-site cell
– Table 200-2 shows the hardware for supporting this feature.
Table 200-2 Dependencies on hardware
TRX/Subsite x GTMU Type RF Module CPRI Rate (Gbit/

Subsite s)
O8*30 GTMUb RRU3926 Equal to or greater

O12*18 RRU3928 than 2.5
RRU3929
RRU3942

GBSS14.0
TRX/Subsite x GTMU Type RF Module CPRI Rate (Gbit/

Subsite s)
O8*18 GTMUb RRU3008 V2 Equal to or greater

O12*10 RRU3908 V2 than 2.5
O6*24 RRU3926
RRU3928
RRU3929
RRU3942
O6*12 GTMUb RRU3004 Equal to or greater

O8*9 RRU3008 V1 than 1.25
O9*8 RRU3908 V1
O10*6
O6*6 GTMU and All types of RRUs Equal to or greater

GTMUb than 1.25
NOTE
Oa*b indicates a TRXs/subsites x b subsites. For example, O8*30 indicates 8 TRXs/subsites x 30

subsites.
When a multi-site cell is configured with several different RXUs, the specification of the multi-site
cell is the lowest among all specifications of these RXUs. For example, the specification of multi-site
cell A, which consists of RRU3008 V1 and RRU3926, is the specification of RRU3008 V1.
– This feature cannot be used together with any of the followings: GBFD-115830
VAMOS, GBFD-111602 TRX Power Amplifier Intelligent Shutdown, GBFD-111604
Intelligent Combiner Bypass, GBFD-111606 Power Optimization Based on Channel
Type, GBFD-111612 Multi-Carrier Intelligent Voltage Regulation, GBFD-118701
RAN Sharing, GBFD-115902 Transmit Diversity, GBFD-118102 Dynamic PBT
(Power Boost Technology), GBFD-113703 Antenna Frequency Hopping,
GBFD-118201 Soft-Synchronized Network, GBFD-114001 Extended Cell,
MRFD-211801 Multi-mode Dynamic Power Sharing(GSM), GBFD-118104 Enhanced
EDGE Coverage, GBFD-113901 Satellite Transmission over Abis Interface,
GBFD-119308 Intermodulation Testing, GBFD-118106 Dynamic Power Sharing (The
multi-site cell feature cannot be used together with dual-PA power sharing), and
GBFD-113701 Frequency Hopping (RF hopping, baseband hopping) (The multi-site
cell feature cannot be used together with cross-module RF hopping)
l License
Context
The multi-site cell feature enables multiple subsites to be configured as one logical cell. Such
cell is also called a cascaded cell. A subsite is defined as an area physically covered by multiple
RRUs that are served by one BBU. In coverage scenarios such as high-speed railways, tunnels,

GBSS14.0
or indoor space, the use of cascaded cells can reduce handovers, increase coverage efficiency,
and therefore improve user experience.
l In a multi-site cell, only one primary subsite can be configured.

l A TRX board bound with carriers can be added only to the primary subsite. TRX boards
that are not bound with any carriers can be added only to the secondary subsite.
Procedure
1. Run the BSC6900 MML command ADD BTSLOCGRP (CME single configuration:
BTS Configuration Express > BTS Board > BTS Location Group; CME batch
modification center: not supported) to add the primary subsite with Location Group
No. set to the desired one and Is Main Local Group set to YES(YES).
2. Run the BSC6900 MML command ADD BTSLOCGRP (CME single configuration:
BTS Configuration Express > BTS Board > BTS Location Group; CME batch
modification center: not supported) to add the secondary subsite with Location Group
No. set to a desired one and Is Main Local Group set to NO(NO).
3. Run the BSC6900 MML command ADD BTSRXU2LOCGRP (CME single
configuration: BTS Configuration Express > BTS Board > Board To Location
Group; CME batch modification center: not supported) to add an RXU to the primary
subsite after specifying Location Group No., Cabinet No., Subrack No., and Slot
No..
4. Run the BSC6900 MML command ADD BTSRXU2LOCGRP (CME single
configuration: BTS Configuration Express > BTS Board > Board To Location
Group; CME batch modification center: not supported) to add an RXU to the
secondary subsite after specifying Location Group No., Cabinet No., Subrack
No., and Slot No..
5. Run the BSC6900 MML command ADD BTSBINDLOCGRP (CME single
configuration: BTS Configuration Express > BTS Board > Location Group
Binding Relations; CME batch modification center: not supported) to bind a carrier
in the primary subsite to an idle channel on the TRX board in the secondary subsite
after specifying Main Location Group No., Sub-Location Group No., TRX ID,
Cabinet No., Subrack No., Slot No., and Sub-Location Group TRX Board Pass
No..
NOTE
l This configuration takes effect only when the TRXs in the primary subsite are the same as
those in the secondary subsite. For example, in a multi-site cell with four subsites, subsite
A is the primary subsite and is configured with three logical TRXs, and subsites B, C, and
D are the secondary subsites. In this situation, you must bind the three logical TRXs in the
primary subsite to the idle channels on the TRX boards in subsites B, C, and D.
l All the subsites under a BTS or cell will be deleted when the BTS or cell is deleted.
Cell Parameters in Batches) with Directly Magnifier BTS Flag set to YES(Yes).
7. Optional: Run the BSC6900 MML command SET GCELLSOFT (CME single
configuration: Cell Configuration Express > Software Parameter and Reserved
Parameter > Software Parameters of Cell; CME batch modification center: 3.20
Modifying GSM Cell Parameters in Batches).

GBSS14.0
If... Then...
Only the power amplifier for the carriers Set Location Group Power Switch to
under the operating subsite needs to be OnlyCurPwrLoc(Only Current
started, Working Location TRXes be Turned
On).
The power amplifier for carriers under Set Location Group Power Switch to
all subsites needs to be started, ALLPwrLoc(All Location TRXes be
Turned On).
1. Start CS single user tracing on the LMT. For details, see Tracing CS Domain Messages
of a Single Subscriber in the BSC6900 LMT User Guide.
2. Use the MS to call a phone in the test subsite.
3. Check the result of CS single user tracing.
The expected result: The location group no carried in the Channel Activation
message is the test location group number.
----End
Example
ADD BTSLOCGRP: IDTYPE=BYID, BTSID=0, LOCGRPNO=0, ISMAINLOCGRP=YES;
ADD BTSLOCGRP: IDTYPE=BYID, BTSID=0, LOCGRPNO=1, ISMAINLOCGRP=NO;
ADD BTSRXU2LOCGRP: IDTYPE=BYID, BTSID=0, LOCGRPNO=0, CN=0, SRN=3, SN=0;
ADD BTSRXU2LOCGRP: IDTYPE=BYID, BTSID=0, LOCGRPNO=1, CN=0, SRN=3, SN=1;
ADD BTSBINDLOCGRP: IDTYPE=BYID, BTSID=0, MAINLOCGRPNO=0, SLAVELOCGRPNO=1,
TRXID=1, CN=0, SRN=3, SN=1, TRXPN=0;
ADD BTSBINDLOCGRP: IDTYPE=BYID, BTSID=0, MAINLOCGRPNO=0, SLAVELOCGRPNO=1,
TRXID=2, CN=0, SRN=3, SN=1, TRXPN=1;
SET GCELLSOFT: IDTYPE=BYID, CELLID=0, DIRMAGANSITEFLAG=YES;

GBSS14.0 201 Configuring PS Automatic Frequency Correction (PS
Feature Activation Guide AFC)
201 Configuring PS Automatic

Frequency Correction (PS AFC)
This section describes how to activate, verify, and deactivate the feature GBFD-5101051 PS
Automatic Frequency Correction (PS AFC).
Prerequisites
– The feature GBFD-114101 GPRS or GBFD-114201 EGPRS has been activated before
– This feature cannot be used together with the feature GBFD-115821 EICC,
GBFD-115830 VAMOS, or GBFD-115832 VAMOS Call Drop Solution.
l License
– 3012 series base stations, BTS3900B, and BTS3900E do not support this feature.
– The DRRU and DRFU do not support this feature.
– This feature supports only LSR services modulated in Gaussian minimum shift-
frequency keying (GMSK) or 8 phase shift keying (8PSK) mode.
Context
The PS AFC feature corrects the frequency offset for PS services processed by fast-moving MSs.
This reduces the Doppler frequency shift caused by high-speed movement, increasing the
throughput of the packet switched (PS) domain.

GBSS14.0 201 Configuring PS Automatic Frequency Correction (PS
Feature Activation Guide AFC)
UL PS Automatic PSULFREQADJ The parameter Network plan

Frequency determines whether
Correction to enable the PS
automatic frequency
correction function
for the BTS. Enable
this function in high-
speed railway
scenarios. Use the
parameter in other
scenarios.
Procedure
Parameters in Batches).In this step, set UL PS Automatic Frequency Correction
to YES(Yes).
1. Run the BSC6900 MML command LST GCELLOTHEXTto query UL PS
Automatic Frequency Correction.
Expected results: UL PS Automatic Frequency Correction is set to YES(Yes).

2. Initiate PS services, and check the uplink throughput and proportions of high-rate
(8PSK) EGPRS coding schemes before and after the PS AFC feature is activated. For
MSs moving at a speed of 200 km/h (900 MHz carrier) or 100 km/h (1,800 MHz
carrier), the uplink throughput and proportion of high-rate EGPRS coding schemes
increase after the PS AFC feature is activated.
Parameters in Batches). In this step, set UL PS Automatic Frequency
Correction to NO(No).
----End
Example
//Activating PS Timeslot AFC
SET GCELLOTHEXT: IDTYPE=BYID, CELLID=0, PSULFREQADJ =YES;
//Verifying PS Timeslot AFC
LST GCELLOTHEXT: IDTYPE=BYID, BTSID=0, CELLID=0;
//Deactivating PS Timeslot AFC
SET GCELLOTHEXT: IDTYPE=BYID, CELLID=0, PSULFREQADJ =NO;

GBSS14.0
Feature Activation Guide 202 Configuring HUAWEI II Handover
202 Configuring HUAWEI II Handover
HUAWEI II Handover.
Prerequisites
l License
Context
Huawei II handover algorithm will traverse all the handover types in the handover decision-
making phase. In the process of traversing the handover types, Huawei II handover algorithm
does not execute a handover immediately but creates a candidate target cell list when the
triggering conditions of the handover are met, compared with the common handover algorithm.
After all the handover types are traversed, the intersection of the candidate cell lists that meet
the handover triggering conditions is selected as the final target cell list. Compared with the
common handover algorithm, Huawei II handover algorithm considers comprehensively all
handover decision-making results so that the final handover decision-making result is accurate.
Huawei II handover algorithm is classified into emergency handover, intra-cell handover, and
inter-cell handover.
l The emergency handover is classified into directed retry, quick handover, bad quality
handover, TA handover, and edge handover.
l The intra-cell handover is classified into interference handover, concentric circles
handover, BCCH dense frequency multiplexing handover, handover between TCHF and
TCHH, and VAMOS Demultiplexing Due to Poor Voice Quality.
l The inter-cell handover is classified into no downlink measurement report handover,
enhanced dual-band network handover, fast-moving micro cell handover, load handover,
better cell handover, and 2G/3G handover.

GBSS14.0
CAUTION
l After quick handover, bad quality handover, and TA handover are successful, penalty is
applied on the old cell during the penalty time to prevent an immediate handover back to the
old cell.
l In Huawei II handover algorithm, the serving cell must not be selected as the target cell of
bad quality handover.
l During TA handover, if the TA Threshold of a co-site neighboring cell is lower than or equal
to the TA Threshold of the serving cell, a handover to the cell is prohibited.
l Intra-cell handover is allowed for the interference handover. However, when intra-cell
handover is triggered several times continuously, it will be forbidden within a specified
duration. In Huawei II handover algorithm, only the serving cell can be selected as the target
cell of interference handover.
l On the enhanced dual-band network, the MS should not be handed over to a cell in the same
underlaid/overlaid cell group when the load-based handovers between the overlaid cell and
the underlaid cell (specified by Load HO From UL Subcell to OL Subcell Allowed and
Load HO of OL Subcell to UL Subcell Enabled) are allowed. This is to prevent a load-
based handover of a normal cell from colliding with a load-based handover between the
overlaid cell and the underlaid cell on the network.
l PBGT handover toward a cell of the same group is not allowed once it is triggered between
the enhanced dual-band network cells.
l After the fast-moving micro cell handover is successful, penalty is applied on all the
neighboring micro cells.
l A load-based handover is not treated as an independent handover type for handover decision-
making. The load-based handover decision is made in the network adjustment phase. The
selection of a target cell should be processed by the better cell handover. That is, the load-
based handover is triggered when the triggering conditions of load-based handover and better
cell handover are met simultaneously.
l Better cell handover is an optimization of inter-layer handover and PBGT handover in
Huawei I handover algorithm. It is specific to Huawei II handover algorithm.
Procedure
HOALGORITHM2(Handover algorithm II).
2. Run the BSC6900 MML command SET GCELLHOEMG (CME single
Algorithm to HOALGORITHM2(Handover algorithm II).
3. Run the BSC6900 MML command SET GCELLHOFITPEN (CME single
Parameters of Cell Handover; CME batch modification center: 3.20 Modifying

GBSS14.0

Algorithm to HOALGORITHM2(Handover algorithm II).
center: 3.20 Modifying GSM Cell Parameters in Batches). In this step, set Current
HO Control Algorithm to HOALGORITHM2(Handover algorithm II).
Batches). In this step, set MAX Consecutive HO Times to an appropriate value.
6. Optional: To improve the effect of handover and power control when the BCCH
participates in baseband frequency hopping, run the SET GCELLCCCH (CME
single configuration: Cell Configuration Express > Idle Mode > Common Control
Cell Parameters in Batches) command with PWRC set to YES(Yes) and run the
SET GCELLOTHEXT (CME single configuration: Cell Configuration Express >
Other Attributes > Extended Parameters of Cell; CME batch modification center:
3.20 Modifying GSM Cell Parameters in Batches) command with Power Control
and Handover CMP CON Sw set to YES(Yes).
7. Activating directed retry.
8. Activating the quick handover algorithm
a. Run the BSC6900 MML command MOD G2GNCELL (CME single
Index, and Neighboring Cell Type to appropriate values; then, set Chain
Neighbor Cell to YES(Yes), and set Chain Neighbor Cell Type to appropriate
values.
Modifying GSM Cell Parameters in Batches). In this step, set Quick
Handover Enable to YES(Yes), and set Quick PBGT Handover Enable to
YES(Yes). if quick PBGT handovers are needed. Then set Quick Handover
Offset for Neighbor Cell to appropriate values.
NOTE
The quick handover algorithm consists of the frequency offset handover algorithm and
quick PBGT handover algorithm. Quick Handover Enable controls whether to initiate
frequency offset and quick PBGT handovers. Quick PBGT Handover Enable controls
whether to initiate quick PBGT handovers only.
c. Run the BSC6900 MML command SET GCELLHOFAST (CME single
configuration: Cell Configuration Express > Handover Data > Fast
Modifying GSM Cell Parameters in Batches). In this step, set the following
parameters to appropriate values: Quick Move Speed Threshold, Quick
Handover Up Trigger Level, Quick Handover Down Trigger Level, Quick
Handover Offset, Quick Handover Punish Time, Quick Handover Punish
Value, Serving Cell Filter Length MR Number, Neighbor Cell Filter Length
MR Number, Ignore Measurement Report Number, EN Quick PBGT HO
ALG When MS Leaves BTS, Handover Direction Forecast Enable,

GBSS14.0
Handover Direction Forecast Statistic Times, Frequency Shift Handover

Statistic Time, and Frequency Shift Handover Duration.
NOTE
If external neighboring cells are configured, set Quick Handover Offset, Quick
Handover Punish Time, and Quick Handover Punish Value by running the
BSC6900MOD GEXT2GCELL (CME single configuration: Object Group > GSM
Service Configuration and Maintenance Management > External Cell
Configuration > BSC 2G External Cell; CME batch modification center: 3.21
Modifying BSC External Cell Parameters in Batches) command.
d. Run the BSC6900 MML command SET GCELLOTHEXT (CME single
Parameters in Batches). In this step, set UL Frequency Adjust Switch, DL
Frequency Adjust Switch, and UL Frequency Adjust Value according to the
frequency offset information reported by the base station.
9. Activating the TA handover algorithm
Modifying GSM Cell Parameters in Batches). In this step, set TA HO
Modifying GSM Cell Parameters in Batches). In this step, set TA
Modifying GSM Cell Parameters in Batches). In this step, set Penalty Time
after TA HO and Penalty Level after TA HO to appropriate values.
d. Run the BSC6900 MML commandMOD G2GNCELL (CME single
Index, Neighboring Cell Type, TA HO Watch Time, and TA HO Valid
Time to appropriate values.
10. Activating the bad quality handover algorithm
Modifying GSM Cell Parameters in Batches). In this step, set BQ HO
b. Optional. For non-AMR calls, run the SET GCELLHOEMG (CME single
Modifying GSM Cell Parameters in Batches) command. In this step, set UL
Qual. Threshold and DL Qual. Threshold to appropriate values.
c. Optional. For AMR FR calls or AMR HR calls, run the SET
GCELLAMRQUL (CME single configuration: Cell Configuration Express >

GBSS14.0
Call Control > AMR Quality Threshold Parameters of Cell; CME batch
modification center: 3.20 Modifying GSM Cell Parameters in Batches)
command. In this step, set UL Qual. Limit for AMR FR, DL Qual. Limit for
AMR FR, UL Qual. Limit for AMR HR, and DL Qual. Limit for AMR
HR to appropriate values.
d. Run the BSC6900 MML command SET GCELLHOFITPEN (CME single
Modifying GSM Cell Parameters in Batches). In this step, set Penalty Time
after BQ HO and Penalty Level after BQ HO to appropriate values.
e. Run the BSC6900 MML command MOD G2GNCELL (CME single
Index, Neighboring Cell Type, TA HO Watch Time, and BQ HO Watch
11. Activating the interference handover algorithm
Modifying GSM Cell Parameters in Batches). In this step, set Interference
HO Allowed to YES(Yes), set Intracell HO Allowed to YES(Yes). and set
Interfere HO Valid Time, Inter-layer HO Threshold and Interfere HO Static
Timeto appropriate values.
Modifying GSM Cell Parameters in Batches). In this step, set Inter-layer HO
Threshold, Interfere HO Static Time, and Interfere HO Valid Time to
appropriate values.
NOTE
modification center: 3.21 Modifying BSC External Cell Parameters in Batches) command.
In this step, set Inter-layer HO Threshold to an appropriate value.
Modifying GSM Cell Parameters in Batches), In this stepset Forbidden time
after MAX Times, MAX Consecutive HO Times and Interval for
Consecutive HO Jud..
Index, Neighboring Cell Type, and Adjacent Cell Inter-layer HO
Hysteresis to appropriate values.
e. Run the BSC6900 MML command SET GCELLAMRQUL (CME single

GBSS14.0

parameters to appropriate values: Interfere HO Qual. Thresh 1 for Non-AMR
FR, Interfere HO Qual. Thresh 2 for Non-AMR FR, Interfere HO Qual.
Thresh 3 for Non-AMR FR, Interfere HO Qual. Thresh 4 for Non-AMR
Thresh 12 for Non-AMR FR, and Interfere HO Qual. Thresh Offset for
AMR FR.
12. Activating the concentric cell algorithm, refer to 180 Configuring Concentric Cell.
13. Activating the BCCH dense frequency multiplexing algorithm, refer to 189
Configuring BCCH Dense Frequency Multiplexing.
14. Activating the no downlink measurement report handover algorithm
a. Run the BSC6900 MML command SET GCELLHOEMG (CME single
Modifying GSM Cell Parameters in Batches). In this step, set No Dl Mr.HO
Allowed to YES(Yes) and set UL Qual. Threshold, Cons.No Dl Mr.HO
Allowed Limit, No Dl Mr. HO Statistic Time, and No Dl Mr. HO Last
b. Run the BSC6900 MML command SET GCELLAMRQUL (CME single
Modifying GSM Cell Parameters in Batches), In this setp, set UL Qual. Limit
for AMR FR, UL Qual. Limit for AMR HR.
Modifying GSM Cell Parameters in Batches). In this step, set Filter Length
for TCH Qual. and Filter Length for SDCCH Qual. to appropriate values.
Index, Neighboring Cell Type, UL BQ HO Static Time, and UL BQ HO Last
15. Activating the enhanced dual-band network handover algorithm
a. Run the BSC6900 MML command MOD GCELL (CME single configuration:
Cell Configuration Express > Cell Attributes > GSM CELL; CME batch
step, set Cell IUO Type to EDB_cell(Enhanced Double Frequency Cell), set
Cell Inner/Extra Property and Same Group Cell Index Type (Not required
on the CME) to appropriate values, and set Same Group Cell Name or Same
Group Cell Index based on the value of Same Group Cell Index Type (Not
required on the CME).
b. Run the BSC6900 MML command SET GCELLHOEDBPARA (CME single
configuration: Cell Configuration Express > Handover Data > Enhanced

GBSS14.0
Dual-Band Handover Parameters of Cell; CME batch modification center:

3.20 Modifying GSM Cell Parameters in Batches). In this step, set the
following parameters to appropriate values: Load HO Allowed, UL Subcell
General Overload Threshold, Inner Cell Serious OverLoad Thred, Subcell
HO Allowed Flow Control Level, Incoming OL Subcell HO Level TH, UL
Subcell Serious Overload Threshold, UL Subcell Load Hierarchical HO
Periods, MOD Step LEN of UL Load HO Period, Step Length of UL Subcell
Load HO, UL Subcell Lower Load Threshold, Subcell HO Allowed Flow
Control Level, Outgoing OL Subcell HO Level TH, OL Subcell Load
Diversity HO Period, Step Length of OL Subcell Load HO, Distance
Between Boundaries of Subcells, and Distance Hysteresis Between
Boundaries
16. Activating the edge handover algorithm
Modifying GSM Cell Parameters in Batches). In this step, set Edge HO
Allowed to YES(Yes) and then set Edge HO UL RX_LEV Threshold, Edge
HO DL RX_LEV Threshold, Handover Algorithm II Edge HO Watch
Time, and Handover Algorithm II Edge HO Valid Time.
Index, Neighboring Cell Type, Inter-cell HO Hysteresis, Edge HO AdjCell
Watch Time, and Edge HO AdjCell Valid Time to appropriate values.
c. Optional: Run the following commands when the edge handover thresholds need
to be different for neighboring cells.
Modifying GSM Cell Parameters in Batches). In this step, set Enhanced
Outgoing Cell Handover Allowed to YES(Yes).
configuration: Cell Configuration Express > Neighboring Cell > BSC
2G Neighbor Cell; CME batch modification center: not supported). In this
step, set Enhanced Outgoing Cell Handover Offset to an appropriate
value.
17. Activating the fast-moving micro cell handover algorithm
a. Run the BSC6900 MML command SET GCELLBASICPARA (CME single
Parameters in Batches). In this step, set Layer of the Cell to an appropriate
value.
NOTE
command. In this step, set Layer of the Cell to an appropriate value.

GBSS14.0

Modifying GSM Cell Parameters in Batches). In this step, set MS Fast
Moving HO Allowed to YES(Yes).
Modifying GSM Cell Parameters in Batches). In this step, set MS Fast-
moving Time Threshold, MS Fast-moving Watch Cells, MS Fast-moving
Valid Cells, Penalty Time on Fast Moving HO, and Penalty on MS Fast
NOTE
command. In this step, set Penalty Time on Fast Moving HO and Penalty on MS Fast
d. Run the BSC6900 MML command SET GCELLHOBASIC (CME single
Modifying GSM Cell Parameters in Batches). In this step, set Inter-layer HO
NOTE
modification center: 3.21 Modifying BSC External Cell Parameters in Batches) command.
In this step, set Inter-layer HO Threshold to an appropriate value.
e. Run the BSC6900 MML command MOD G2GNCELL (CME single
Index, Neighboring Cell Type, Adjacent Cell Inter-layer HO Hysteresis,
HCS HO Watch Time, and HCS HO Valid Time to appropriate values.
18. Activating the better cell handover algorithm
Modifying GSM Cell Parameters in Batches). In this step, set Better Cell
Handover Enable to YES(Yes) and set Pathloss Ho. Enable to an appropriate
value.
Index, Neighboring Cell Type, Better Cell HO Watch Time, and Better Cell
HO Valid Time to appropriate values.
c. Optional: Run the following commands when the better cell handover thresholds
need to be different for neighboring cells.

GBSS14.0

Modifying GSM Cell Parameters in Batches). In this step, set Enhanced
Outgoing Cell Handover Allowed to YES(Yes).
configuration: Cell Configuration Express > Neighboring Cell > BSC
2G Neighbor Cell; CME batch modification center: not supported). In this
step, set Neighboring Cell Penalty Switch to YES(Yes), and set Index
Type (Not required on the CME), Source Cell Index, Neighbor 2G Cell
Index, and Neighboring Cell Type, Enhanced Outgoing Cell Handover
Offset, Penalty Stop Level Threshold, Penalty Timer Length, and Level
Penalty Value on Neighboring Cell to appropriate values.
19. Optional Activating the load-based handover penalty inheritance algorithm
Modifying GSM Cell Parameters in Batches). In this step, set Load Handover
Support to YES(Yes).
b. Run the BSC6900 MML command SET GCELLHOFITPEN (CME single
Modifying GSM Cell Parameters in Batches). In this step, set Load HO
Penalty Optimization to ON(On).
20. Optional Activating the optimized TCHF-TCHH handover algorithm
Modifying GSM Cell Parameters in Batches). In this step, set F-H HO Load
Band Optimization Allowed to ON(On).
Modifying GSM Cell Parameters in Batches). In this step, set TCHF-TCHH
HO Load Hysteresis to an appropriate value.
c. Run the BSC6900 MML command SET GCELLHOBASIC (CME single
Modifying GSM Cell Parameters in Batches). In this step, set Non-AMR F-
H HO Quality Thres. Fine Tune, Non-AMR F-H HO Quality Thres. Fine
Tune, Non-AMR H-F HO Quality Thres. Fine Tune, Non-AMR H-F Ho
Qual. Threshold, Non-AMR F-H HO Quality Thres. Fine Tune, Non-AMR
H-F Ho Qual. Threshold, Non-AMR F-H HO Quality Thres. Fine Tune, and
Non-AMR H-F Ho Qual. Threshold to appropriate values to ensure that the
TCHF-TCHH handover quality threshold ranges from 0 to 70.
d. Run the BSC6900 MML command SET GCELLHOBASIC (CME single
Modifying GSM Cell Parameters in Batches). In this step, set AMR F-H Ho
ATCB Threshold, AMR H-F Ho ATCB Threshold, Non-AMR F-H Ho

GBSS14.0
ATCB Threshold, and Non-AMR H-F Ho ATCB Threshold to appropriate

values to ensure that the TCHF-TCHH handover ATCB threshold ranges from
-63 to 255.
21. Activating the algorithm for the handover between TCHF and TCHH
parameters to appropriate values: AMR F-H Ho Allowed to YES(Yes), Allow
AMR H-F Quality-based HO to YES(Yes), Non-AMR F-H Ho Allowed to
YES(Yes), and Allow Non-AMR H-F Quality-based HO to YES(Yes). Then,
set AMR F-H Traffic Threshold, F-H Ho Duration, F-H Ho Period, AMR
F-H Ho Pathloss Adjust Step, AMR F-H Ho ATCB Adjust Step, AMR F-H
Ho Pathloss Threshold, F-H Pathloss Offset Overlay, AMR F-H Ho ATCB
Threshold, F-H ATCB Offset Overlay, AMR F-H Ho Qual. Threshold, F-H
Ho Stat. Time, F-H Ho Last Time, AMR H-F Traffic Threshold, H-F Ho
Duration, AMR H-F Ho ATCB Threshold, H-F ATCB Offset Overlay, AMR
H-F Ho Pathloss Threshold, H-F Pathloss Offset Overlay, AMR H-F Ho
Qual. Threshold, H-F Ho Stat. Time, H-F Ho Last Time, Non-AMR F-H
Traffic Threshold, Non-AMR F-H Ho Pathloss Adjust Step, Non-AMR F-
H Ho ATCB Adjust Step, Non-AMR F-H Ho Pathloss Threshold, Non-AMR
F-H Ho ATCB Threshold, Non-AMR F-H Ho Qual. Threshold, Non-AMR
H-F Traffic Threshold, Non-AMR H-F Ho ATCB Threshold, Non-AMR H-
F Ho Pathloss Threshold, and Non-AMR H-F Ho Qual. Threshold
(Yes).
GSM Cell Parameters in Batches). In this step, set Speech Version to at least
FULL_RATE_VER1, FULL_RATE_VER3 and HALF_RATE_VER3.
3.17 Modifying GBSC Parameters in Batches). In this step, set Um Interface
Tag, Abis Interface Tag and A Interface Tag to GSM_PHASE_2Plus.
22. Activating the 2G/3G handover algorithm, refer to 207 Configuring GSM/WCDMA
Service Based Handover and 208 Configuring GSM/WCDMA Load Based
Handover.
23. Activating SDCCH handover
Modifying GSM Cell Parameters in Batches), In this step, set SDCCH HO
b. Run the BSC6900 MML command SET GCELLHOCTRL (CME single
configuration: Cell Configuration Express > Handover Data > Handover

GBSS14.0

GSM Cell Parameters in Batches), set Inter-BSC SDCCH HO ALLowed to
1. Run the BSC6900 MML command LST GCELLHOBASIC. In this step, query the
setting of Current HO Control Algorithm.
Expected result: The value of the Current HO Control Algorithm is
HOALGORITHM2(Handover algorithm II).
2. On the LMT, start the message tracing over the A interface by referring to Tracing
Messages on the A Interface. Select BSSAP in the Trace Type area.
Expected result: The BSC sends a Handover performed message to the MSC.
– In the case of the quick handover, the handover cause value is better-cell.
– In the case of the TA handover, the handover cause value is distance.
– In the case of the BQ handover, the handover cause value is uplink-quality or
downlink-quality.
– In the case of the interference handover, the handover cause value is uplink-
quality or downlink-quality.
– In the case of the no downlink measurement report handover, the handover cause
value is uplink-quality.
– In the case of the enhanced dual-band network handover, the handover cause value
is better-cell or traffic.
– In the case of the load-based handover, the handover cause value is traffic.
– In the case of the edge handover, the handover cause value is uplink-strength or
downlink-strength.
– In the case of the fast-moving micro cell handover, the handover cause value is
better-cell.
– In the case of the better cell handover, the handover cause value is better-cell.
– In the case of the handover between TCHF and TCHH, the handover cause value
is downlink-quality.
– In the case of the SDCCH handover, the handover cause value is better-cell,
distance, uplink-quality, downlink-quality, traffic, uplink-strength, or
downlink-strength.
3. Optional Verifying the load-based handover penalty inheritance algorithm
a. Run the BSC6900 MML command SET GCELLHOBASIC. In this step, set
Load Handover Support for cell A to YES(Yes). Assume that there are three
cells: cell A, cell B, and cell C
b. Run the BSC6900 MML command SET GCELLHOFITPEN. In this step, set
Load HO Penalty Optimization for cell A to ON(On) to ensure that a load-
based handover is performed from cell C to cell B and then from cell B to cell
A.
c. Run the BSC6900 MML command SET GCELLHOAD. In this step, set Load
HO Threshold, LoadAccThres, Load HO Bandwidth, and Load HO Step
Level for cell A to appropriate values to ensure that the conditions for a load-
based handover from cell A to cell C are met.
Expected result: The load-based handover from cell A to cell C is not triggered.

GBSS14.0
4. Optional Verifying the optimized TCHF-TCHH handover algorithm

AMR F-H Ho Allowed to YES(Yes), Allow Non-AMR H-F Quality-based
HO to YES(Yes), Non-AMR F-H Ho Allowed to YES(Yes), and Allow Non-
AMR H-F Quality-based HO to YES(Yes).
b. Run the BSC6900 MML command SET GCELLHOBASIC. In this step, set
F-H HO Load Band Optimization Allowed to ON(On).
c. Run the BSC6900 MML command SET GCELLHOBASIC. In this step, set
AMR F-H Traffic Threshold and TCHF-TCHH HO Load Hysteresis for cell
A to appropriate values to ensure that the load in cell A is lower than the value
of AMR F-H Traffic Threshold minus the value of TCHF-TCHH HO Load
Hysteresis after full-rate AMR calls are converted to half-rate AMR calls.
Expected result: Only AMR full-rate calls support AMR TCHF-TCHH handovers.
AMR H-F Ho ATCB Threshold to -10.
Expected result: Only the AMR half-rate calls whose TCHF-TCHH handover ATCB
threshold is lower than or equal to -10 support AMR TCHF-TCHH handovers.
a. Run the BSC6900 MML command SET GCELLHOBASIC. In this step. set
Non-AMR H-F Ho Qual. Threshold to 3 and Non-AMR H-F HO Quality
Thres. Fine Tune to 9.
Expected result: Only the AMR half-rate calls whose TCHF-TCHH handover quality
threshold exceeds 39 support AMR TCHF-TCHH handovers.
----End
Example
//Activating HUAWEI II handover algorithm
SET GCELLHOEMG: IDTYPE=BYID, CELLID=0, HOCTRLSWITCH=HOALGORITHM2;
SET GCELLHOFITPEN: IDTYPE=BYID, CELLID=0, HOCTRLSWITCH=HOALGORITHM2;
SET GCELLHOIUO: IDTYPE=BYID, CELLID=0, HOCTRLSWITCH=HOALGORITHM2;
//Activating the quick handover algorithm
NCELLTYPE=HANDOVERNCELL, ISCHAINNCELL=YES,
CHAINNCELLTYPE=QUICK_HO_NCELL_TYPE_A, ADJHOOFFSET=1;
QUICKHOEN=YES, QUICKPBGTHOEN=YES;
MOVESPEEDTHRES=35, SCELLFILTER=4, NCELLFILTER=4, IGNOREMRNUM=1,
TIMEPUNISH=10, HOPUNISHVALUE=63, HOOFFSET=68, MSLEVSTRQPBGT=NO,
HODIRFORECASTEN=YES, HODIRSTATIME=3, HODIRLASTTIME=2, AFCHOSTATTIME=4,
AFCHOLASTTIME=3;
SET GCELLOTHEXT: IDTYPE=BYID, CELLID=0, FREQADJ=YES, DLFREQADJ=YES,
FREQADJVALUE=36671;

GBSS14.0
//Activating the TA handover algorithm

TAHOEN=YES;
TALIMIT=125;
SSTAPUNISH=40, TIMETAPUNISH=10;
NCELLTYPE=HANDOVERNCELL, TASTATTIME=1, TALASTTIME=1;
//Activating the bad quality handover algorithm
BQHOEN=YES;
DLQUALIMIT=55, ULQUALIMIT=60;
SSBQPUNISH=63, TIMEBQPUNISH=10;
NCELLTYPE=HANDOVERNCELL, BQSTATTIME=1, BQLASTTIME=1;
//Activating the interference handover algorithm
INTRACELLHOEN=YES, INTERFHOEN=YES, HOTHRES=25, INTERFERESTATTIME=3,
INTERFERELASTTIME=2;
SET GCELLHOAD: IDTYPE=BYID, CELLID=0, BANTIME=20;
SET GCELLAMRQUL: IDTYPE=BYID, CELLID=0, RXQUAL1=70, RXQUAL2=60,
RXQUAL3=59, RXQUAL4=58, RXQUAL5=57, RXQUAL6=56, RXQUAL7=55, RXQUAL8=54,
RXQUAL9=53, RXQUAL10=52, RXQUAL11=51, RXQUAL12=50;
//Activating the no downlink measurement report handover algorithm
NODLMRHOEN=YES, NODLMRHOQUALLIMIT=50, NODLMRHOALLOWLIMIT=8,
NODLMRHOSTATTIME=1, NODLMRHOLASTTIME=1;
DATAQUAFLTLEN=4, SIGQUAFLTLEN=2;
NCELLTYPE=HANDOVERNCELL, ULBQSTATTIME=1, ULBQLASTTIME=1;
//Activating the enhanced dual-band network handover algorithm
MOD GCELL: IDTYPE=BYID, CELLID=0, IUOTP=EDB_cell, CELLINEXTP=Inner,
SET GCELLHOEDBPARA: IDTYPE=BYID, CELLID=0, OUTASSOPTEN=YES;
///Activating the edge handover algorithm
FRINGEHOEN=YES, ULEDGETHRES=10, DLEDGETHRES=20, EDGESTAT1=6, EDGELAST1=4;
//Activating the fast-moving micro cell handover algorithm
SET GCELLBASICPARA: IDTYPE=BYID, CELLID=0, LAYER=3;
QCKMVHOEN=YES, HOTHRES=25;
SET GCELLHOAD: IDTYPE=BYID, CELLID=0, QCKSTATCNT=3, QCKTRUECNT=2,
QCKTIMETH=15, SPEEDPUNISH=30, SPEEDPUNISHT=4;
NCELLTYPE=HANDOVERNCELL, SRCHOCTRLSWITCH=HOALGORITHM2, INTELEVHOHYST=67,
HCSSTATTIME=3, HCSLASTTIME=2;
//Activating the better cell handover algorithm
BETTERCELLHOEN=YES, PATHLOSSHOEN=YES;
NCELLTYPE=HANDOVERNCELL, SRCHOCTRLSWITCH=HOALGORITHM2,
BETTERCELLSTATTIME=6, BETTERCELLLASTTIME=4;
//Activating the algorithm for the handover between TCHF and TCHH

GBSS14.0
AMRFULLTOHALFHOALLOW=YES, AMRFULLTOHALFHOTHRESH=75,
FULLTOHALFHODURATION=5, FULLTOHALFHOPERIOD=1,
AMRFULLTOHALFHOPATHADJSTEP=1, AMRFULLTOHALFHOATCBADJSTEP=2,
AMRFULLTOHALFHOPATHTHRESH=100, FULLTOHALFHOPATHOFFSET=10,
AMRFULLTOHALFHOATCBTHRESH=20, FULLTOHALFHOATCBOFFSET=20,
AMRFULLTOHALFHOQUALTHRESH=0, FULLTOHALFHOSTATTIME=6,
FULLTOHALFHOLASTTIME=4, AMRHALFTOFULLHOTHRESH=45,
AMRHALFTOFULLHOQUALALLOW=YES, HALFTOFULLHODURATION=5,
AMRHALFTOFULLHOATCBTHRESH=4, HALFTOFULLATCBOFFSET=20,
AMRHALFTOFULLHOPATHTHRESH=108, HALFTOFULLHOPATHOFFSET=10,
AMRHALFTOFULLHOQUALTHRESH=3, HALFTOFULLHOSTATTIME=6,
HALFTOFULLHOLASTTIME=4, NOAMRFULLTOHALFHOALLOW=YES,
NOAMRFULLTOHALFTHRESH=85, NOAMRFULLTOHALFHOPATHADJSTEP=1,
NOAMRFULLTOHALFHOATCBADJSTEP=2, NOAMRFULLTOHALFHOPATHTHRESH=95,
NOAMRFULLTOHALFHOATCBTHRESH=30, NOAMRFULLTOHALFHOQUALTHRESH=0,
NOAMRHALFTOFULLTHRESH=25, NOAMRHALFTOFULLHOQUALALLOW=YES,
NOAMRHALFTOFULLHOATCBTHRESH=14, NOAMRHALFTOFULLHOPATHTHRESH=103,
NOAMRHALFTOFULLHOQUALTHRESH=2;
//Activating the load-based handover penalty inheritance algorithm
LoadHoPunishInheritSwitch=ON;
//Activating the optimized TCHF-TCHH handover algorithm
SET GCELLPWRBASIC: IDTYPE=BYID, CELLID=0, F2HHOLOADSTFSWITCH=ON;
AMRFULLTOHALFHOATCBTHRESH=-63, AMRFULLTOHALFHOQUALTHRESH=6,
AMRF2HHOQUALTHFINE=8;
//Activating the SDCCH handover algorithm

SIGCHANHOEN=YES;
SET GCELLHOCTRL: IDTYPE=BYID, CELLID=0, INRBSCSDHOEN=YES;

GBSS14.0
Feature Activation Guide 203 Configuring Handover Re-establishment
203 Configuring Handover Re-

establishment
Handover Re-establishment.
Prerequisites
l License
– An available neighboring cell is configured for the test cell. The TRX of the test cell
supports handover re-establishment.
Context
If receiving an Error Indication message from the BTS during a handover, the BSC attempts to
re-establish the call on the original channel instead of treating it as a call drop.
Handover re-establishment provides the following benefits:
l Reducing the call drop rate and improving user satisfaction
Procedure
Cell Parameters in Batches). In this step, set Activate L2 Re-establishment to YES
(Yes).

GBSS14.0
Feature Activation Guide 203 Configuring Handover Re-establishment
NOTE
the verification.
1. Configure two cells: cell0 and cell1. Configure these two cells as neighboring cells
on the same frequency band. Ensure that they operate properly.
2. Initiate RSL message tracing on the Abis interface for cell0 on the BSC6900 LMT by
referring to Tracing CS Domain Messages on the Abis Interface.
3. Run the BSC6900 MML command ADD G2GNCELL. In this step, set Better Cell
HO Watch Time and Better Cell HO Valid Time to 1, and PBGT HO Threshold
to 64.
Current HO Control Algorithm to HOALGORITHM2(Handover algorithm
II).
5. Run the BSC6900 MML command SET GCELLCCTMR. In this step, set Use
LAPDm N200 to ON(On), T200 FACCH/F and T200 FACCH/H to 5, N200 of
FACCH/Half Rate to 30, and N200 of FACCH/Full Rate to 34.
6. Use a test MS to make a call in cell0.
7. Rapidly decrease the BTS transmit power in cell0 to initiate a handover for better cell
to cell1.
8. After issuing the handover command, the BSC receives an Error Indication message
from cell0. The MS cannot receive the handover command. Then, increase the transmit
power in cell0.
9. Check the result of RSL message tracing on the Abis interface for cell0.
Expected result: The test MS continues with the call in cell0. The following messages
can be traced on the Abis interface for cell0: Handover Command, Error Indication,
Establish Request, and Establish Confirm.
Cell Parameters in Batches). In this step, set Activate L2 Re-establishment to NO
(No).
----End
Example
/*Activating Handover Re-establishment*/
//Enabling handover re-establishment
SET GCELLSOFT: IDTYPE=BYID, CELLID=0, ACTL2REEST=YES;
/*Deactivating Handover Re-establishment*/
//Disabling handover re-establishment
SET GCELLSOFT: IDTYPE=BYID, CELLID=0, ACTL2REEST=NO;

GBSS14.0
Feature Activation Guide 204 Configuring Enhanced Measurement Report
204 Configuring Enhanced Measurement

Report
Enhanced Measurement Report.
Prerequisites
– This feature cannot be used together with the feature GBFD-115830 VAMOS.
l License
– The MS supports enhanced measurement report (EMR).
– The test cell is configured with neighboring cells and supports the EMR feature.
Context
EMR is a new downlink measurement report available from 3GPP R99. Measurement results,
such as Bit Error Probability (BEP) and Frame Erase Ratio (FER), are added to an EMR. This
improves the performance of power control algorithms and handover algorithms. This feature
brings the following benefits:
l This feature improves the capability of voice quality monitoring and the performance of
power control algorithms and handover algorithms.
l As many as 15 3G neighboring cells can be configured with EMR. This provides a better
performance of interoperability between the GSM, WCDMA, and TD-SCDMA systems.
Procedure

GBSS14.0
Feature Activation Guide 204 Configuring Enhanced Measurement Report

Modifying GSM Cell Parameters in Batches). In this step, set Measurement
Report Type of cell0 to EnhMeasReport(Enhanced Measurement Report).
Assume that cell0 and cell1 are neighboring 2G cells of each other.
1. Use an MS to make a call in cell0.
2. Check whether the RSL message traced on the Abis interface of cell0 contains the
EMR information element (IE).
Expected result: Calls are established successfully and the voice quality is good. The
RSL message traced on the Abis interface of cell0 contains the EMR IE(In an original
measurement report, the EMR IE is enhanced-measurement-report-struct. In a
preprocessed measurement report, the EMR IE is pre-proc-emr).
NOTE
A common MR is reported if the MS does not support EMR.
Modifying GSM Cell Parameters in Batches). In this step, set Measurement
Report Type of cell0 to ComMeasReport(Common Measurement Report).
----End
Example
//Activating Enhanced Measurement Report
SET GCELLCCUTRANSYS: IDTYPE=BYID, CELLID=1024, MEASURETYPE=EnhMeasReport;
//Deactivating Enhanced Measurement Report
SET GCELLCCUTRANSYS: IDTYPE=BYID, CELLID=1024, MEASURETYPE=ComMeasReport;

GBSS14.0
Feature Activation Guide 205 Configuring BTS power lift for handover
205 Configuring BTS power lift for

handover
BTS power lift for handover.
Prerequisites
– None
– The feature GBFD-110601 HUAWEI I Handover or GBFD-510501 HUAWEI II
Handover has been configured before this feature is activated.
l License
Context
The BTS power lift for handover function determines whether the BTS of the serving cell
transmits signals at the maximum power during a handover. After the function is enabled, the
BTS adjusts its transmit power to the maximum value before the BSC sends a handover
command to the MS. This ensures that the handover can be performed successfully.
Procedure
Parameters in Batches). In this step, set Power Boost before HO Enabled or Not
to YES(StartUp).
1. Run the BSC6900 MML command LST GCELLOTHBASIC.
Expected result: Power Boost before HO Enabled or Not is set to StartUp.

GBSS14.0
Feature Activation Guide 205 Configuring BTS power lift for handover
Parameters in Batches). In this step, set Power Boost before HO Enabled or Not
to NO(Not StartUp).
----End
Example
SET GCELLOTHBASIC: IDTYPE=BYID, CELLID=0, HOPOWERBOOST=YES;
LST GCELLOTHBASIC: IDTYPE=BYID, CELLID=0, LstFormat=VERTICAL;
SET GCELLOTHBASIC: IDTYPE=BYID, CELLID=0, HOPOWERBOOST=NO;

GBSS14.0
Feature Activation Guide 206 Configuring GSM/WCDMA Interoperability
206 Configuring GSM/WCDMA

Interoperability
GSM/WCDMA Interoperability.
Prerequisites
– The MS supports both the GSM and WCDMA networks. It also supports bidirectional
cell reselection and handovers between GSM and WCDMA.
– The BSS and NSS support the GSM/WCDMA inter-RAT cell selection, cell reselection,
and location update. In addition, they support measurement control, handover decision,
and handover signaling procedures during inter-RAT handovers.
l License
The basic data is configured. For details, see Configuring the Basic Data.
Context
The GSM/WCDMA Interoperability feature enables an MS to be handed over to or reselect a
GSM cell if the serving cell of the MS is not covered by the WCDMA network or in an area
with weak WCDMA coverage. When a dual-mode MS enters the coverage of the WCDMA
network again, or the MS detects that the signal quality in the WCDMA cell is higher than that
in the serving GSM cell, the MS can be handed over to or reselect a WCDMA cell if the handover
or cell reselection conditions are met. Then, the MS can enjoy the various services provided by
the WCDMA network.
The feature GSM/WCDMA Interoperability is applied to scenarios such as cell reselection and
handovers between GSM and WCDMA. This feature has no impact on services. The network
elements involved are the BTS, BSC, MSC, PCU, SGSN, GGSN, and HLR.

GBSS14.0
Optimization focuses on the delivery mode of the 2Quater system information (SI) and
measurement information (MI). The information elements (IEs) in the first 2Quater SI are
streamlined, and the neighboring UMTS cell lists of the 2Quater SI and MI are delivered in
dense coding mode. In this way, the amount of system information to be delivered is reduced
and the PS service interruption period during a cell reselection is shortened.
Procedure
1. Run the BSC6900 MML command ADD GEXT3GCELL (CME single
modification center: 3.21 Modifying BSC External Cell Parameters in Batches) to
add a 3G external cell. In this step, set Utran Cell Type to FDD(FDD).
Optional: When Utran Cell Type is set to FDD(FDD), Run the BSC6900 MML
command SET GCELLCCUTRANSYS (CME single configuration: Cell
Configuration Express > Call Control > Call Control UTRAN System Message
Parameters in Batches) to modify the UTRAN system information parameter related
to the cell call control. In this step, set SI 2Quater Optimization to YES(Yes).
batch modification center: not supported) to add a neighboring 3G cell.
Parameters in Batches). In this step, set A Interface Tag and Um Interface Tagto
GSM_PHASE_2Plus.
Sent 2QUATER to YES(Yes), Send 3G Class Flag to YES(Yes), and Classmark
Enquiry With 3G Request to YES(Yes).
Cell Parameters in Batches). In this step, set Query Classmark after In-BSC HO
Enabled to YES(Yes).
Parameters in Batches) to set basic call control parameters of a cell. In this step, set
ECSC to YES(Yes).
Modifying GSM Cell Parameters in Batches) to set the UTRAN system information
parameters for call control in the cell. In this step, set Qsearch I to 7, Qsearch C to
7, Qsearch P to 7, and Qsearch C Initial to Always(Always).

GBSS14.0
1. Run the BSC6900 MML command LST GEXT3GCELL to query the value of Utran
cell type.
Expected result: The value of Utran cell type is FDD.
2. Use an MS to access the 2G cell and then initiate a call. After the call is initiated
normally, move the MS to the coverage area with strong 3G signals. Run the BSC6900
MML command SET GCELLHOINTERRATLDB. In this step, set Allow Inter-
RAT Load HO in Access State to CnService-based. On the CN side, set Service
Handover to Handover to UTRAN or cdma2000 should be performed.
3. On the LMT, trace the BSSAP messages over the A interface.
Expected result: The BSC sends a Handover Required message to the MSC with the
handover cause value of "better-cell" or "directed-retry".
4. Move the MS within the GSM cell or UMTS cell, and ensure that the Ec/No and
Received Signal Code Power (RSCP) of the Common Pilot Channel (CPICH) are
normal during the neighboring cell measurement of the UMTS cell (FDD). If the
following conditions are met within five seconds, then the MS will initiate a cell
reselection from GSM to UMTS: CPICH RSCP > RLA_C + FDD Q Offset or CPICH
Ec/No > FDD Qmin.
5. When the MS is in the GSM cell, the frequency information of the MS indicates that
the MS is in the GSM cell. When the MS is in the UMTS cell, the frequency
information of the MS indicates that the MS is in the UMTS cell.
batch modification center: not supported) to remove the neighboring 3G cell.
2. Run the BSC6900 MML command RMV GEXT3GCELL (CME single
modification center: not supported) to remove the 3G external cell.
----End
Example
//Activating GSM/WCDMA Interoperability
ADD GEXT3GCELL: EXT3GCELLID=5048, EXT3GCELLNAME="5048", MCC="11",
MNC="11", LAC=11, CI=1, RNCID=11, RNCINDEX=255, DF=1, SCRAMBLE=1,
DIVERSITY=NO, UTRANCELLTYPE=FDD, RA=1;
SET BSCBASIC: AVer=GSM_PHASE_2Plus, UmVer=GSM_PHASE_2Plus;
SET OTHSOFTPARA: Send2QuterFlag=YES, SendUtranECSCFlag=YES,
CLASSMARKQUERY=YES;
SET GCELLSOFT: IDTYPE=BYID, CELLID=0, QUERYCMAFTERINBSCHO=YES;
SET GCELLCCUTRANSYS: IDTYPE=BYID, CELLID=0, QI=7, QCI=Always, QP=7,
QSEARCHC=7;
//Deactivating GSM/WCDMA Interoperability
RMV G3GNCELL: EXT3GCELLID=5048, EXT3GCELLNAME="5048";
RMV GEXT3GCELL: IDTYPE=BYID, SRC3GNCELLID=0, NBR3GNCELLID=5048;

GBSS14.0
Feature Activation Guide 207 Configuring GSM/WCDMA Service Based Handover
207 Configuring GSM/WCDMA Service

Based Handover
Configuring GSM/WCDMA Service Based Handover.
Prerequisites
– The BSS and NSS support the inter-RAT cell selection, cell reselection, and location
update. In addition, they support measurement control, handover decision, and handover
signaling procedure during inter-RAT handovers.
This feature depends on the feature GBFD-114301 GSM/WCDMA Interoperability.
l License
– The basic data is configured. For details, see Configuring the Basic Data.
– On the MSC, the BSC is set to support service handovers, and the service handover
attribute of the IMSI for the MS is set to support handovers for 2G CS services.
Procedure
Parameters in Batches) to set the basic handover parameters of the cell. In this step,
set Inter-RAT Out BSC Handover Enable to YES(Yes) and Inter-RAT In BSC
Handover Enable to YES(Yes).

GBSS14.0
2. Run the BSC6900 MML command SET GCELLHOINTERRATLDB (CME single

configuration: Cell Configuration Express > Handover Data > Inter-RAT
Handover Parameters; CME batch modification center: 3.20 Modifying GSM Cell
Parameters in Batches). In this step, set Allow Inter-RAT Load HO in Access
State to CnService-based.
3. Run the BSC6900 MML command SET GCELLHOUTRANFDD (CME single
configuration: Cell Configuration Express > Handover Data > UTRAN FDD
GSM Cell Parameters in Batches) to set the UTRAN FDD handover parameters of
a cell. In this step, set Better 3G Cell HO Allowed to YES(Yes), Inter-rat HO
Preference to Pre_3G_Cell(Preference for 3G cell), RSCP Threshold for Better
3G Cell HO to 0, and Ec/No Threshold for Better 3G Cell HO to 0.
4. Run the BSC6900 MML command MOD G3GNCELL (CME single configuration:
batch modification center: not supported). In this step, set FDD 3G Better Cell HO
Watch Time, FDD 3G Better Cell HO Valid Time, RSCP Offset, and Ec/No
Offset according to the actual requirements.
center: 3.17 Modifying GBSC Parameters in Batches). In this step, set Service
Based Handover Switch to OPEN(Open) and Service Handover Reassign to YES
(Yes).
normally, move the MS to the coverage area with strong 3G signals. On the CN side,
set Service Handover to Handover to UTRAN or cdma2000 should be
performed.
handover cause value of "better-cell" or "directed-retry".
set Inter-RAT Out BSC Handover Enable to NO(No) and Inter-RAT In BSC
Handover Enable to NO(No).
GSM Cell Parameters in Batches). In this step, set Better 3G Cell HO Allowed to
NO(No) and Inter-rat HO Preference to Pre_2G_Cell(Preference for 2G cell).
----End
Example
//Activating GSM/WCDMA Service Based Handover

GBSS14.0
SET GCELLHOINTERRATLDB: IDTYPE=BYID, CELLID=0,

InterRatServiceLoadHoSwitch=CnService-based;
SET GCELLHOUTRANFDD: IDTYPE=BYID, CELLID=0, BET3GHOEN=YES,
HOOPTSEL=Pre_3G_Cell;
SET OTHSOFTPARA: OUTSYSSERVICEHOEN=OPEN, OUTSYSSERVHOREASSIGNEN=YES;
//Deactivating GSM/WCDMA Service Based Handover

SET GCELLHOBASIC: IDTYPE=BYID, CELLID=0, INTERRATOUTBSCHOEN=NO,
INTERRATINBSCHOEN=NO;
SET GCELLHOUTRANFDD: IDTYPE=BYID, CELLID=0, BET3GHOEN=NO,

GBSS14.0
Feature Activation Guide 208 Configuring GSM/WCDMA Load Based Handover
208 Configuring GSM/WCDMA Load

Based Handover
GSM/WCDMA Load Based Handover.
Prerequisites
signaling procedure during inter-RAT handovers.
This feature depends on the feature GBFD-114301 GSM/WCDMA Interoperability.
l License
The basic data is configured. For details, see Configuring the Basic Data.
Context
The MSC transparently transmits the load information of the WCDMA network to the BSC.
Then, the BSC makes a decision on the inter-RAT handover based on its own load and the load
in the WCDMA network. In addition, the BSC sends a handover request carrying its own load
information to the WCDMA network for reference in the decision on the inter-RAT handover.
Procedure

GBSS14.0
set Inter-RAT Out BSC Handover Enable and Inter-RAT In BSC Handover
Enable to YES(Yes).
center: 3.17 Modifying GBSC Parameters in Batches). In this step, set CS 2G 3G
Load Balance Delta Threshold according to the actual requirements.
Parameters in Batches) to set inter-RAT handover parameters.
4. Run the BSC6900 MML command MOD GEXT3GCELL (CME single
modification center: 3.21 Modifying BSC External Cell Parameters in Batches).
In this step, set Load handover Load Accept Threshold according to the actual
requirements.
Batches). In this step, set Load handover Load Accept Threshold according to the
actual requirements.
normally, move the MS to the coverage area with strong 3G signals. Run the BSC6900
MML command SET GCELLHOINTERRATLDB. In this step, set Inter-rat HO
Preference to Load-based(Load-based). On the CN side, set Service Handover to
Handover to UTRAN or cdma2000 should be performed.
handover cause value of "reduce load in serving cell".
set Inter-RAT Out BSC Handover Enable to NO(No) and Inter-RAT In BSC
Handover Enable to NO(No).
GSM Cell Parameters in Batches). In this step, set Better 3G Cell HO Allowed to
NO(No) and Inter-rat HO Preference to Pre_2G_Cell(Preference for 2G cell).
----End
Example
//Activating GSM/WCDMA Load Based Handover

GBSS14.0
SET GCELLHOINTERRATLDB: IDTYPE=BYID, CELLID=0, OutSysLoadHoEn=YES,
InterRatServiceLoadHoSwitch=Load-based;
//Deactivating GSM/WCDMA Load Based Handover

SET GCELLHOBASIC: IDTYPE=BYID, CELLID=0, INTERRATOUTBSCHOEN=NO,
INTERRATINBSCHOEN=NO;
SET GCELLHOUTRANFDD: IDTYPE=BYID, CELLID=0, BET3GHOEN=NO,

GBSS14.0
Feature Activation Guide 209 Configuring 2G/3G Cell Reselection Based on MS State
209 Configuring 2G/3G Cell Reselection

Based on MS State
2G/3G Cell Reselection Based on MS State.
Prerequisites
signaling procedures during inter-RAT handovers.
– This feature cannot be used together with the feature GBFD-116201 Network-
Controlled Cell Reselection (NC2).
l License
The basic data has been configured. For details, see Configuring the Basic Data.
Context
This feature is designed to enable dual-mode MSs in the idle state or in the packet transfer state
to adopt different reselection policies to access the GSM network or WCDMA network as
required.
Procedure

GBSS14.0
Parameters in Batches) to set the basic handover parameters for a cell. In this step,
set Inter-RAT Cell Reselection Enable to YES(Yes).
Modifying GSM Cell Parameters in Batches) to set the UTRAN system information
parameters for call control in the cell. In this step, set Qsearch I to 7, Qsearch P to
15, and Qsearch C Initial to Always(Always).
3. Optional: If Utran Cell Type is set to TDD(TDD), Run the BSC6900 MML
Parameters in Batches) to modify the UTRAN system information parameters for
call control in the cell. In this step, set TDD System Information Optimized
4. Optional: When Utran Cell Type is set to FDD(FDD), Run the BSC6900 MML
Parameters in Batches) to modify the UTRAN system information parameter related
to the cell call control. In this step, set SI 2Quater Optimization to YES(Yes).
NOTE
Optimization focuses on the delivery mode of the 2Quater system information (SI) and
measurement information (MI). The information elements (IEs) in the first 2Quater SI are
streamlined, and the neighboring UMTS cell lists of the 2Quater SI and MI are delivered in
dense coding mode. In this way, the amount of system information to be delivered is reduced
and the PS service interruption period during a cell reselection is shortened.
1. Move the MS within the GSM cell or UMTS cell, and ensure that the Ec/No and
Received Signal Code Power (RSCP) of the Common Pilot Channel (CPICH) are
normal during the neighboring cell measurement of the UMTS cell (FDD). If the
following conditions are met within five seconds, then the MS will initiate a cell
reselection from GSM to UMTS: CPICH RSCP > RLA_C + FDD Q Offset or CPICH
Ec/No > FDD Qmin.
2. When the MS is in the GSM cell, the frequency information of the MS indicates that
the MS is in the GSM cell. When the MS is in the UMTS cell, the frequency
information of the MS indicates that the MS is in the UMTS cell.
Parameters in Batches) to set the basic handover parameters for a cell. In this step,
set Inter-RAT Cell Reselection Enable to NO(No).
----End
Example
//Activating 2G/3G Cell Reselection Based on MS State
SET GCELLHOBASIC: IDTYPE=BYID, CELLID=0, INTERRATCELLRESELEN=YES;
SET GCELLCCUTRANSYS: IDTYPE=BYID, CELLID=0, QI=7, QCI=Always, QP=15;

GBSS14.0
//Deactivating 2G/3G Cell Reselection Based on MS State

SET GCELLHOBASIC: IDTYPE=BYID, CELLID=0, INTERRATCELLRESELEN=NO;

GBSS14.0 210 Configuring the Fast WCDMA Reselection at 2G CS Call
Feature Activation Guide Release
210 Configuring the Fast WCDMA

Reselection at 2G CS Call Release
Fast WCDMA Cell Reselection at 2G CS Call Release.
Prerequisites
l License
– The network involves the GSM network and the WCDMA network
– The UE supports the GSM and WCDMA frequency bands at the same time.
– The UE supports 3GPP Release6 and later specifications.
Context
When an UE terminates a call in the GSM network, it camps on the WCDMA network according
to the cell selection indicator after release information in the Channel Release message
Procedure
1. Run the BSC6900 MML command ADD GEXT3GCELL (CME single
modification center: 3.21 Modifying BSC External Cell Parameters in Batches) to
add a WCDMA FDD cell 1.

batch modification center: not supported) to configure the WCDMA cell 1 as the
neighboring cell of the GSM cell 0.
3. Run the BSC6900 MML command ADD UEXT2GCELL (CME single
configuration: Object Group > UMTS Service Configuration and Maintenance
Management > External Cell Configuration > RNC 2G External Cell; CME batch
modification center: Modifying RNC External Cell Parameters in Batches)to add a
GSM cell 0 on the WCDMA side.
4. Run the BSC6900 MML command ADD U2GNCELL (CME single configuration:
UMTS Cell Configuration Express > Neighboring Cell > GSM Neighboring
Cell; CME batch modification center: not supported) to configure the GSM cell 0 as
the neighboring cell of the WCDMA cell 1.
Parameters in Batches) with A Interface Tag, Um Interface Tag, and Abis
Interface Tag to GSM_PHASE_2Plus.
6. configure the fast WCDMA reselection at 2G CS call release.
– When the Inter-RAT Out BSC Handover Enable set to YES(Yes)
Modifying GSM Cell Parameters in Batches) with Inter-RAT Cell
Reselection Enable of Cell 0, set to YES(Yes).
b. Run the BSC6900 MML command SET GCELLCCAD (CME single
Advanced Parameters of Cell; CME batch modification center: 3.20
Modifying GSM Cell Parameters in Batches) with Select 3G Cell After
Call Release of Cell 0, a GSM cell, set to YES(Yes).
– When the Inter-RAT Out BSC Handover Enable set to NO(No)
Modifying GSM Cell Parameters in Batches) with Inter-RAT Cell
Reselection Enable of Cell 0, set to YES(Yes).
b. Run the BSC6900 MML command SET OTHSOFTPARA (CME single
Configuration > Other Software Parameters of BSC; CME batch
modification center: 3.17 Modifying GBSC Parameters in Batches) with
Inter-RAT Cell Reselection Optimization of Cell 0, set to ON(On).
c. Run the BSC6900 MML command SET GCELLCCAD (CME single
Advanced Parameters of Cell; CME batch modification center: 3.20
Modifying GSM Cell Parameters in Batches) with Select 3G Cell After
Call Release of Cell 0, a GSM cell, set to YES(Yes).
1. On the Um Interface Trace window, it shows that the UE camps on Cell 0 and initiates
a call successfully. In addition, the call is still being maintained.
2. After the call is released, on the screen of the UE, it shows that the UE has camped
on a 3G cell.

NOTE
If the GSM and WCDMA networks use the same indicator, the UE must be equipped with a
function through which a user can query that the currently camped cell is a GSM or WCDMA
cell.
3. On the Um Tracing window, the signaling procedure of the cell shows that the
downlink Channel Release message carries an information element (IE) "cell-
selection-indicator-after-release".
Batches) with Select 3G Cell After Call Release of Cell 0, the GSM cell, set to NO
(No).
----End
Example
//Activating the feature Fast WCDMA Reselection at GSM CS Call Release
ADD GEXT3GCELL: EXT3GCELLID=7572, EXT3GCELLNAME="Cell1", MCC="460",
MNC="10", LAC=10, CI=60, RNCID=0, DF=50, SCRAMBLE=200, DIVERSITY=NO,
UTRANCELLTYPE=FDD,OPNAME="main";
ADD G3GNCELL: IDTYPE=BYNAME, SRC3GNCELLNAME="Cell0",
NBR3GNCELLNAME="Cell1";
ADD U2GNCELL: RNCId=0, CellId=1, GSMCellIndex=0, BlindHoFlag=FALSE,
NPrioFlag=FALSE;
SET GCELLCCAD: IDTYPE=BYNAME, CELLNAME="Cell0",
CELLSELECTAFTERCALLREL=YES;
//Deactivating the feature Fast WCDMA Reselection at GSM CS Call Release
SET GCELLCCAD: IDTYPE=BYID, CELLID=1234, CELLSELECTAFTERCALLREL=NO;

GBSS14.0 211 Configuring Load Based Handover Enhancement on Iur-
Feature Activation Guide g
211 Configuring Load Based Handover

Enhancement on Iur-g
Load Based Handover Enhancement on Iur-g.
Prerequisites
– A GSM/UMTS dual-mode MS is required.
– IP Interface board should be configured to support Iur-g.
– Configurations of other features on which this feature depends are complete.
– This feature depends on features WRFD-070004 Load Based GSM and UMTS
Handover Enhancement Based on Iur-g and GBFD-114322 GSM/WCDMA Load
Based Handover.
l License
– NOTE
The licenses on the BSC and the RNC sides are activated separately.
l Both the 2G network and the 3G network are deployed.
l IP transmission mode is used on the Iur-g interface.
l A GSM cell and a UMTS cell are configured and the GSM cell is configured as the
neighboring cell of the UMTS cell.
l Data is negotiated and planned for the inter-BSC6900 Iur-g interface. For details you can
refer to Configuring the inter-BSC6900 Iur-g interface.
Context
This feature is implemented through the exchange of Huawei proprietary IE containing load
information over the Iur-g interface. The Iur-g protocol stack complies with the 3GPP
specifications. With this feature, the decision on handover that is not caused by insufficient

coverage can be more accurate, thus reducing the possibility of ping-pong handovers between
the GSM network and WCDMA network.
Procedure
Parameters in Batches) to enable inter-RAT handovers. In this step, set Inter-RAT
Out BSC Handover Enable and Inter-RAT In BSC Handover Enable to YES
(Yes) .
Parameters in Batches) to set 2G Load Adjustment Coefficient. Setting 2G Load
Adjustment Coefficient to 10 is recommended.
NOTE
l If the verification achieves the following results as expected, the configuration succeeds. Otherwise,
the configuration fails.
1. 3G-to-2G Load Based Handover Enhancement
CAUTION
The verification can be done when only the UMTS cell is in the basic congestion state.
a. Use the dual-mode MS to call a fixed telephone in the UMTS cell. Trace signaling
on the Iu interface on the LMT. RANAP_RELOCATION_REQUIRED
message is reported. The RANAP_RELOCATION_REQUIRED message
contains reduce-load-in-serving-cell. Trace signaling on the A interface on the
LMT. Handover Request message is reported. The Handover Request
message contains reduce-load-in-serving-cell.
NOTE
After the verification, set the value of system to the value before the verification.
2. 2G-to-3G Load Based Handover Enhancement
a. Use the MS to initiate a call in the GSM cell, and the call is successfully
established.
b. When the GSM cell is in the basic congestion state, the MS hand over to 3G
neighbor cell. Trace signaling on the A interface. Check that Assignment
Request, Handover Required, and Handover Command messages are
reported and cause in the Handover Required message is directed-retry(13).
Parameters in Batches) to deactivate MBSC Handover based on Load Enhancement

on the GSM side. In this step, set Allow Inter-RAT Load HO in Connect State to
NO(No).
----End
Example
//Activating Handover based on Load Enhancement
/*Enabling the inter-RAT handover*/
/*Setting 2G Load Adjustment Coefficient*/
SET GCELLHOINTERRATLDB: IDTYPE=BYID, CELLID=0, G2GLoadAdjustCoeff=10;
//Deactivating Handover based on Load Enhancement
SET GCELLHOINTERRATLDB: IDTYPE=BYID, CELLID=0, OutSysLoadHoEn=NO;

212 Configuring NACC(Network Assisted Cell Change)
GBSS14.0 Procedure Optimization Based on Iur-g between GSM and
Feature Activation Guide WCDMA
212
Assisted Cell Change) Procedure Optimization
Configuring NACC(Network
Based on Iur-g between GSM and WCDMA
NACC Procedure Optimization Based on Iur-g between GSM and WCDMA.
Prerequisites
– This feature depends on feature WRFD-070005 NACC Procedure Optimization Based
on Iur-g.
l License
– NOTE
The licenses on the BSC and the RNC sides are activated separately.
l IP transmission mode is used on the Iur-g interface.
l The MS supports NACC.
l Both the 2G network and the 3G network are deployed.
l A GSM cell and a UMTS cell are configured and the GSM cell is configured as the
l GPRS is set to SupportAsInnPcu(Support as built-in PCU) in the MML command SET
GCELLGPRS.
refer to For details you can refer to Configuring the inter-BSC6900 Iur-g interface.

212 Configuring NACC(Network Assisted Cell Change)
GBSS14.0 Procedure Optimization Based on Iur-g between GSM and
Feature Activation Guide WCDMA
Context
This feature enables the exchange of messages containing the RAN Information Management
(RIM) information over the Iur-g interface between the RNC and BSC. The Iur-g protocol stack
complies with the 3GPP specifications. In this way, the NACC procedure for PS services from
a GSM cell to a WCDMA cell does not require the information transfer via the CN.
Procedure
1. Run the BSC6900 MML commandMOD GNRNC (CME single configuration: (G)
IURG Configuration Express > Neighboring RNC > Neighboring RNC; CME
batch modification center: not supported) to allow NACC-related information
exchange on the Iur-g interface. In this step, set Allow Info Exchange at Iur-g to
YES(Support) and Info Exchange Content to NACCRELATED(NACC Info).
Batches) to set basic GPRS attributes of the GSM cell. In this step, set GPRS to
SupportAsInnPcu(Support as built-in PCU) and Support NACC to YES(Yes).
1. Trace Iur-g and Um interfaces on the LMT.
2. Use a dual-mode MS to download data in the UMTS cell and then switch the MS to
the GSM cell.
3. Check that INFO_EXCHG_INIT_REQ and INFO_EXCHG_INIT_RSP
messages are reported on the Iur-g interface. The value of informationTypeItem in
the INFO_EXCHG_INIT_REQ message is nACC-Related-Data(8) and the
INFO_EXCHG_INIT_RSP message contains nACC-Related-Data.
1. Run the BSC6900 MML commandMOD GNRNC (CME single configuration: (G)
IURG Configuration Express > Neighboring RNC > Neighboring RNC; CME
batch modification center: not supported) to allow NACC-related information
exchange on the Iur-g interface. In this step, set Allow Info Exchange at Iur-g to
NO(No Support).
Batches) to set basic GPRS attributes of the GSM cell. In this step, set GPRS to
SupportAsInnPcu(Support as built-in PCU) and Support NACC to NO(no).
----End
Example
//Activating NACC Procedure Optimization
/*Allowing NACC-related information exchange on the Iur-g interface*/
MOD GNRNC: RNCINDEX=0, SPTINFOEXCHG=YES, INFOEXCHGLIST=NACCRELATED-1;
/*Setting basic GPRS attributes of the GSM cell*/
SET GCELLGPRS: IDTYPE=BYID, CELLID=0, GPRS=SupportAsInnPcu, NACCSPT=YES;
//Deactivating NACC Procedure Optimization
MOD GNRNC: RNCINDEX=0, SPTINFOEXCHG=NO;
SET GCELLGPRS: IDTYPE=BYID, CELLID=0, GPRS=SupportAsInnPcu, NACCSPT=NO;

GBSS14.0 213 Configuring GSM and WCDMA Load Balancing Based
Feature Activation Guide on Iur-g
213 Configuring GSM and WCDMA

Load Balancing Based on Iur-g
GSM and WCDMA Load Balancing Based on Iur-g.
Prerequisites
– This feature depends on features GBFD-114322 GSM/WCDMA Load Based Handover
or WRFD-070006 GSM and UMTS Load Balancing Based on Iur-g.
l License
– NOTE
The licenses on the BSC and RNC sides are activated separately.
l 2G and 3G networks cover the same area.
l IP transmission mode is used over the Iur-g interface.
l The value of the information element (IE) Service Handover in the RAB ASSIGNMENT
REQUEST message sent from the CN to the RNC is Handover to GSM should be
performed.
l The value of the IE Service Handover in the ASSIGNMENT REQUEST message sent
from the CN to the BSC is Handover to UTRAN or cdma2000 should be performed.
l A GSM cell and a UMTS cell are configured, and the GSM cell is configured as a

Context
This feature implements the load-based GSM/WCDMA handover through the exchange of
Huawei proprietary IE over the Iur-g interface. With this feature, the traffic is distributed on the
basis of the service handover indicator and load of the GSM network and WCDMA network
when an MS accesses the network. In this way, a load balance is achieved between the GSM
network and WCDMA network.
Procedure
Parameters in Batches). In this step, set Allow Inter-RAT Load HO in Access
State to Load-based(Load-based), 2G Load Adjustment Coefficient to an
appropriate value.
center: 3.17 Modifying GBSC Parameters in Batches). In this step, set CS 2G 3G
Load Balance Delta Threshold to an appropriate value.
NOTE
If the verification achieves the following results as expected, the configuration succeeds. Otherwise, the
configuration fails.
1. 3G-to-2G Load Balancing
CAUTION
a. The verification procedure consists of the RRC setup phase and the RAB
connection phase. The verification in the latter phase involves CS speech services
and PS data services.
a. Verifying that CS speech services in UMTS cell1 are handed over to GSM
cell2 at the RRC setup phase
1) Use the dual-mode MS to call a fixed telephone in cell1. The call is
successfully established. Initiate Uu-interface signaling tracing on the
LMT. The RRC_RRC_CONNECT_REQ and
RRC_RRC_CONN_REJECT messages are reported, and the
RRC_RRC_CONN_REJECT message contains GSM-
TargetCellInfo. That is, information about cell2 is contained,
indicating that the MS accesses cell2.
b. Verifying that PS data services in UMTS cell1 are handed over to GPRS
cell3 at the RAB connection phase
1) Use the MS to browse the Internet.

2) Initiate Uu-interface message tracing on the LMT. You can find that
the messages RRC_RB_SETUP, RRC_RB_SETUP_CMP,
RRC_MEAS_CTRL, and
RRC_CELL_CHANGE_ORDER_FROM_UTRAN are reported, and
that the value of InterRATEvent in the RRC_MEAS_CTRL message
is event3c.
3) Initiate Iu-interface signaling tracing on the LMT. You can find that
the RANAP_SRNS_CONTEXT_REQ message is sent from the CN
to the RNC and then the RANAP_SRNS_CONTEXT_RESP message
is sent from the RNC to the CN.
the RANAP_SRNS_DATA_FORWARD_COMMAND and
RANAP_IU_RELEASE_COMMAND messages are sent from the
CN to the RNC and then the RANAP_IU_RELEASE_COMPLETE
message is sent from the RNC to the CN.
5) When the MS attempts to reselect cell3, Internet browsing is slightly
affected. After the MS reselects cell3, Internet browsing returns to
normal.
c. Verifying that CS speech services in UMTS cell1 are handed over to GSM
cell2 at the RAB connection phase
1) Use the dual-mode MS to call a fixed telephone in cell1. The call is
successfully established.
2) Initiate Uu-interface tracing on the LMT. You can find that the
messages RRC_RB_SETUP, RRC_RB_SETUP_CMP,
RRC_MEAS_CTRL, and RRC_HO_FROM_UTRAN_CMD_GSM
are reported, and that the value of InterRATEvent in the
RRC_MEAS_CTRL message is event3c.
the RANAP_RELOCATION_REQUIRED message is sent from the
RNC to the CN and then the RANAP_RELOCATION_COMMAND
and RANAP_IU_RELEASE_COMMAND messages are sent from
the CN to the RNC.
the RANAP_IU_RELEASE_COMPLETE message is sent from the
RNC to the CN.
2. 2G-to-3G Load Balancing
CAUTION
The verification can be done when only the GSM cell is in the basic congestion state.
a. Use the MS to initiate a call in the GSM cell. The directed retry procedure is
triggered so that the MS accesses the neighboring UMTS cell. The call is
successfully established. Initiate A-interface signaling tracing on the LMT. You
can find that the Assignment Request, Handover Required, and Handover
Command messages are reported and that the value of cause in the Handover
Required message is directed-retry(13).

Parameters in Batches) to deactivate 2G-to-3G load balancing. In this step, set Allow
Inter-RAT Load HO in Access State to OFF(OFF).
----End
Example
//Activating Load Balancing Based on Iur-g
/*Enabling load balancing*/
SET GCELLHOINTERRATLDB: IDTYPE=BYID, CELLID=0, OutSysLoadHoEn=YES,
InterRatServiceLoadHoSwitch=Load-based, G2GLoadAdjustCoeff=10;
/*Enabling inter-RAT handover*/
SET GCELLHOBASIC: IDTYPE=BYNAME, CELLNAME="0", INTERRATOUTBSCHOEN=YES,
/*Setting load difference thresholds*/
SET OTHSOFTPARA: G2G3GLdBlcDeltaThrd=110;
//Deactivating Load Balancing Based on Iur-g
InterRatServiceLoadHoSwitch=OFF;

GBSS14.0 214 Configuring GSM and WCDMA Traffic Steering Based
214 Configuring GSM and WCDMA

Traffic Steering Based on Iur-g
GSM and WCDMA Traffic Steering Based on Iur-g.
Prerequisites
– A GSM+UMTS dual-mode MS is required.
– This feature depends on features GBFD-114321 GSM/WCDMA Service Based
Handover and WRFD-070007 GSM and WCDMA Traffic Steering Based on Iur-g.
l License
– NOTE
The licenses on the BSC and RNC sides are activated separately.
l 2G and 3G networks cover the same area.
l IP transmission mode is used over the Iur-g interface.
l The value of the information element (IE) Service Handover in the RAB ASSIGNMENT
REQUEST message sent from the CN to the RNC is Handover to GSM should be
performed.
l The value of the IE Service Handover in the ASSIGNMENT REQUEST message sent
from the CN to the BSC is Handover to UTRAN or cdma2000 should be performed or
Handover to UTRAN or cdma2000 should not be performed.
l A GSM cell and a UMTS cell are configured, and the GSM cell is configured as a

Context
This feature supports GSM/WCDMA handover based on service. With this feature, services are
steered on the basis of the service handover indicator, hierarchical network planning, and the
load of the GSM network and WCDMA network when an MS accesses the network.
Procedure
Parameters in Batches) to enable traffic steering. In this step, set Allow Inter-RAT
Load HO in Access State to Service-based(Service-based).
1. The verification procedure of 3G-to-2G Traffic Steering
CAUTION
a. Use the dual-mode MS to call a fixed telephone in the UMTS cell. Initiate Iu-
interface tracing on the LMT. You can find that the
RANAP_RELOCATION_REQUIRED message is reported and the handover
cause value in the message is resource-optimisation-relocation. Initiate A
interface tracing. You can find that the Handover Request message is reported
and the handover cause value in the message is traffic.
CAUTION
Ensure that the GSM cell is not in the congestion state.
2. The verification procedure of 2G-to-3G Traffic Steering
CAUTION
The verification can be done when only the GSM cell is in the basic congestion state.
a. Use the dual-mode MS to call a fixed telephone in the GSM cell. Initiate CS
Domain Messages of a Single Subscriber tracing on the LMT. You can find that
the call is in GSM cell, and don't hand over to UMTS cell.

Parameters in Batches) to disable traffic steering. In this step, set Allow Inter-RAT
Load HO in Access State to OFF(Off).
----End
Example
//Activating 3G-to-2G traffic steering
/*Enabling inter-RAT incoming BSC handover*/
InterRatServiceLoadHoSwitch=Service-based;
//Deactivating 3G-to-2G traffic steering
InterRatServiceLoadHoSwitch=OFF;

GBSS14.0
Feature Activation Guide 215 Configuring BSC supporting Blind Search
215 Configuring BSC supporting Blind

Search
This section describes how to activate, verify, and deactivate the feature GBFD-511110 BSC
supporting Blind Search.
Prerequisites
This feature depends on the feature GBFD-114301 GSM/WCDMA Interoperability or
GBFD-114302 GSM/TD-SCDMA Interoperability.
– GBFD-511110 BSC supporting Blind Search is mutually exclusive with the
GBFD-511405 NC2 between GSM and TD-SCDMA feature.
– GBFD-511110 BSC supporting Blind Search is mutually exclusive with the following
functions:
– Forced NC2 between GSM and WCDMA function
– GSM-to-WCDMA/TD-SCDMA network-controlled cell reselection function in the
GBFD-116201 Network-Controlled Cell Reselection (NC2) feature
l License
– This feature does not depend on the running environment.
– This feature does not have any special requirements for transmission networking.
– The MS must support blind search.
– If 3G ARFCN Type is set to FDD, 3G ARFCN 1 through 3G ARFCN 8 are valid,
whereas ARFCN9 through ARFCN16 are invalid.
– If 3G ARFCN Type is set to TDD, 3G ARFCN 1 through 3G ARFCN 16 are valid.

GBSS14.0
Context
3G ARFCNs for Cell INPUT3GARFCNE This parameter Network Planning

Reselection N specifies whether to
allow configuring
only 3G ARFCNs for
GSM-to-UMTS cell
reselections.
Procedure
Parameters in Batches). In this step, set Inter-RAT Cell Reselection Enable to
YES(Yes).
If... Then...
Each cell uses its customized Run the BSC6900 MML command SET
neighboring 3G ARFCNs GCELL3GARFCN (CME single
configuration: Cell Configuration
Express > Other Attributes >
UARFCNs for a Cell; CME batch
modification center: 3.20 Modifying
GSM Cell Parameters in Batches) to
add a 3G ARFCN.
All cells controlled by the BSC use the Run the BSC6900 MML command SET
same neighboring 3G ARFCNs G3GARFCN (CME single
configuration: GSM Global
Configuration Express > BSC Basic
Configuration > UARFCNs for the
BSC; CME batch modification center:
not supported) to add a 3G ARFCN.
SET GCELL3GARFCN (CME single
Express > Other Attributes >
UARFCNs for a Cell; CME batch
modification center: 3.20 Modifying
GSM Cell Parameters in Batches). In
this step, set 3G ARFCNs for Cell
Reselection to YES(Yes).

GBSS14.0
Parameters in Batches). In this step, set A Interface Tag,Um Interface Tag and
Modifying GSM Cell Parameters in Batches) to set the UTRAN system message
parameters for call control in a cell. In this step, set Qsearch I, Qsearch C, and
Qsearch P to 7, and set Qsearch C Initial to Always(Always).
1. Perform received signal level (RSL) tracing over the Abis interface. The system
information 2Quater carries information about neighboring 3G ARFCNs.
2. Enable the Blind Search function to configure FDD ARFCNs. Move the MS within
the GSM or UMTS cell, and ensure that the Ec/No and Received Signal Code Power
(RSCP) of the Common Pilot Channel (CPICH) are normal during the neighboring
cell measurement of the UMTS cell (FDD). If the following conditions are met within
five seconds, the MS initiates a GSM-to-UMTS cell reselection: CPICH RSCP >
RLA_C + FDD Q Offset and CPICH Ec/No > FDD Qmin
– When the MS is in a GSM cell, the frequency information of the MS indicates that
the MS camps on the GSM cell.
– When the MS is in a UMTS cell, the frequency information of the MS indicates
that the MS camps on the UMTS cell.
3. Enable the Blind Search function to configure TDD frequencies. Move the MS within
the GSM or TD-SCDMA cell, and ensure that Qsearch I and the RSCP of the CPICH
are normal during the neighboring cell measurement of the TD-SCDMA cell (TDD).
If the following condition is met within five seconds, the MS initiates a GSM-to-TD-
SCDMA cell reselection: CPICH RSCP > TDD Cell Reselect Diversity
– When the MS is in a GSM cell, the frequency information of the MS indicates that
the MS camps on the GSM cell.
– When the MS is in a TD-SCDMA cell, the frequency information of the MS
indicates that the MS camps on the TD-SCDMA cell.
If... Then...
Each cell uses its customized neighboring Run the BSC6900 MML command SET
3G ARFCNs GCELL3GARFCN (CME single
Express > Other Attributes > UARFCNs
for a Cell; CME batch modification center:
3.20 Modifying GSM Cell Parameters in
Batches). In this step, do as follows:
1. Set all ARFCNs to 65,535.
2. Set 3G ARFCNs for Cell

GBSS14.0
If... Then...
All cells controlled by the BSC use the Run the BSC6900 MML command SET
same neighboring 3G ARFCNs G3GARFCN (CME single configuration:
GSM Global Configuration Express >
BSC Basic Configuration > UARFCNs
for the BSC; CME batch modification
center: not supported). In this step, do as
follows:
1. Set all ARFCNs to 65,535.
2. Set 3G ARFCNs for Cell
----End
Example
If each cell uses its customized neighboring 3G ARFCNs
SET GCELL3GARFCN: IDTYPE=BYID, CELLID=0, INPUT3GARFCNEN=YES,
INPUT3GARFCNENTYPE=FDD, ARFCN1=10;
QSEARCHC=7;
If all cells controlled by the BSC use the same neighboring 3G ARFCNs
SET G3GARFCN: INPUT3GARFCNEN=YES, INPUT3GARFCNENTYPE=FDD, ARFCN1=10;
SET GCELL3GARFCN: IDTYPE=BYID, CELLID=0, INPUT3GARFCNEN=YES;
QSEARCHC=7;
If each cell uses its customized neighboring 3G ARFCNs
SET GCELL3GARFCN: IDTYPE=BYID, CELLID=0, INPUT3GARFCNEN= YES,
ARFCN1=65535, ARFCN2=65535, ARFCN3=65535, ARFCN4=65535, ARFCN5=65535,
ARFCN11=65535, ARFCN12=65535, ARFCN13=65535, ARFCN14=65535,
ARFCN15=65535, ARFCN16=65535;
SET GCELL3GARFCN: IDTYPE=BYID, CELLID=0, INPUT3GARFCNEN=NO;
If all cells controlled by the BSC use the same neighboring 3G ARFCNs
SET G3GARFCN: INPUT3GARFCNEN=YES, ARFCN1=65535, ARFCN2=65535,
ARFCN13=65535, ARFCN14=65535, ARFCN15=65535, ARFCN16=65535;
SET G3GARFCN: INPUT3GARFCNEN=NO;

GBSS14.0
Feature Activation Guide 216 Configuring Cell Reselection Between GSM and LTE
216 Configuring Cell Reselection

Between GSM and LTE
Prerequisites
– This feature requires support from the MS, BTS, BSC, MSC, PCU, SGSN, GGSN, and
HLR.
l License
– The MS supports both GSM and LTE and supports bidirectional cell reselection between
GSM and LTE.
– The BSS and the NSS support bidirectional cell reselection between GSM and LTE.
Context
Cell reselection between GSM and LTE enables an MS in an LTE network to reselect the GSM
network when the MS is in a blind area of the LTE network or in an area with weak LTE coverage.
When the MS reenters the LTE network coverage or when the MS detects that an LTE cell
provides strong coverage, the MS can reselect the LTE network when the cell reselection
conditions are met.
Procedure
1. Run the BSC6900 MML command ADD GEXTLTECELL (CME single
Management > External Cell Configuration > BSC LTE External Cell; CME

GBSS14.0
batch modification center: 3.21 Modifying BSC External Cell Parameters in

Batches) to add an external LTE cell. In this step, set EUTRAN Cell Type according
to the actual situation.
Parameters in Batches). In this step, set LTE Cell Reselection Allowed to YES
(Yes).
3. Run the BSC6900 MML command SET GCELLPRIEUTRANSYS (CME single
configuration: Cell Configuration Express > Call Control > Cell Priority and
EUTRAN System Information Parameters; CME batch modification center: 3.20
Modifying GSM Cell Parameters in Batches). In this step, set GERAN Priority
smaller than EUTRAN Priority.
4. Run the BSC6900 MML command ADD GLTENCELL (CME single configuration:
Cell Configuration Express > Neighboring Cell > BSC LTE Neighbor Cell; CME
batch modification center: not supported) to add a neighboring LTE cell. In this step,
set Source Cell Index to the index of the cell to be verified, Neighbor Cell Index to
the index of the added LTE cell, and Support Cell Reselection to SUPPORT
(SUPPORT).
1. Run the BSC6900 MML command LST GCELLHOBASIC to check the value of
LTE Cell Reselection Allowed.
Expected result: The value of LTE Cell Reselection Allowed is Yes.
2. Enable the MS to camp on a GSM cell. Initiate RSL message tracing on the Abis
interface on the BSC6900 LMT by referring to Tracing CS Domain Messages on the
Abis Interface. On the RSL tab page, set Filter Flag to Cell and Cell ID
(cell1,cell2,...cell16) to the index of the cell to be verified. Then click Submit and an
Abis Interface CS Trace dialog box is displayed.
Expected result: The MS reselects the LTE cell successfully. The result of RSL
message tracing on the Abis interface shows that BCCH Information is traced and its
message type is System Information 2Quater.
1. Optional: Run the BSC6900 MML command SET GCELLHOBASIC (CME single
Parameters in Batches) to disable cell reselection from a GSM cell to all neighboring
LTE cells. In this step, set LTE Cell Reselection Allowed to NO(No).
2. Optional: Run the BSC6900 MML command MOD GLTENCELL (CME single
configuration: Cell Configuration Express > Neighboring Cell > BSC LTE
Neighbor Cell; CME batch modification center: not supported) to disable cell
reselection from a GSM cell to a specific LTE cell. In this step, set Support Cell
Reselection to UNSUPPORT(UNSUPPORT).
----End

GBSS14.0
Example
/*Activating Cell Reselection Between GSM and LTE*/
//Adding an external LTE cell
ADD GEXTLTECELL: EXTLTECELLID=8048, EXTLTECELLNAME="cell", MCC="460",
MNC="188", ENODEBTYPE=HOME, CI=0, TAC=1, FREQ=2, PCID=3, EUTRANTYPE=FDD;
//Enabling LTE cell reselection
SET GCELLHOBASIC: IDTYPE=BYID, CELLID=0, LTECELLRESELEN=YES;
//Setting the cell priority and the parameters about EUTRAN system
information
SET GCELLPRIEUTRANSYS: IDTYPE=BYID, CELLID=0, GERANPRI=1, EUTRANPRI=7,
THREUTRANHIGH=2, EUTRANQRXLEVMIN=10;
//Enabling cell reselection from a GSM cell to a specific neighboring LTE
cell
ADD GLTENCELL: IDTYPE=BYID, SRCLTENCELLID=0, NBRLTENCELLID=8048,
SPTRESEL=SUPPORT;
//Enabling System Information 2Quater sending
/*Deactivating Cell Reselection Between GSM and LTE*/
//Disabling cell reselection from a GSM cell to all neighboring LTE cells
SET GCELLHOBASIC: IDTYPE=BYID, CELLID=0, LTECELLRESELEN=NO;
//Disabling cell reselection from a GSM cell to a specific neighboring LTE
cell
MOD GLTENCELL: IDTYPE=BYID, SRCLTENCELLID=0, NBRLTENCELLID=8048,
SPTRESEL=UNSUPPORT;

GBSS14.0 217 Configuring PS Handover Between GSM and LTE Based
Feature Activation Guide on Coverage
217 Configuring PS Handover Between

GSM and LTE Based on Coverage
PS Handover Between GSM and LTE Based on Coverage.
Prerequisites
This feature depends on the optional feature GBFD-119502 PS Handover.
l License
l The dual-mode MS supports the PS handover between GSM and LTE.
l The SGSN supports the PS handover between GSM and LTE.
l The SGSN support the PFC procedure.
l The GSM cell is configured with neighboring LTE cells, and the neighboring LTE cells
support the cell reselection.
NOTE
You can Run the BSC6900 MML command ADD GEXTLTECELL (CME single configuration:
Object Group > GSM Service Configuration and Maintenance Management > External Cell
Configuration > BSC LTE External Cell; CME batch modification center: 3.21 Modifying BSC
External Cell Parameters in Batches) to add a neighboring LTE cell, in this step, set EUTRAN
Cell Type according to the actual situation, and Run the BSC6900 MML command SET
GCELLHOBASIC (CME single configuration: Cell Configuration Express > Handover Data >
Basic Handover Parameters of Cell; CME batch modification center: 3.20 Modifying GSM Cell
Parameters in Batches) to configure the neighboring LTE cells to support the cell reselection, in
this step, set LTE Cell Reselection Allowed to YES(Yes).
l The LTE cell is configured with neighboring GSM cells. In addition, the LTE cell supports
the feature of PS Handover Between GSM and LTE Based on Coverage.

Context
l When an NSE is configured to support the PS handover, all the cells under the NSE support
the PS handover.
l The BSC supports the PS handover between E-UTRAN and GERAN. In this way, the
access time of the MS to the target cell is reduced.
Procedure
– Activating the PS Handover from GSM to LTE
Cell Parameters in Batches).
– Set Support Out LTE Inter-cell PS Handover to SUPPORT(Support).
(NC2).
– Set Cell Normal Reselection Allowed to PERMIT(Permit).
– Set Normal Cell Reselection Watch Period as required, for example, 10.
– Set Cell Reselection Hysteresis as required, for example, 6.
– Set Cell Penalty Duration as required, for example, 10.
– Set Normal Cell Reselection Worsen Level Threshold as required, for
example, 1.
– Set Cell Reselection Level Threshold as required, for example, 15.
– Set Cell Penalty Level as required, for example, 30.
– Set Allowed Measure Report Missed Number as required, for example, 4.
– Set Filter Window Size as required, for example, 6.
– Set Cell Reselect Interval as required, for example, 2.
EUTRAN System Information Parameters; CME batch modification center:
3.20 Modifying GSM Cell Parameters in Batches). In this step, set EUTRAN
Priority to 7.
– Activating the PS Handover from LTE to GSM


(Support as built-in PCU) and Support In LTE Inter-cell PS Handover to
SUPPORT(Support).
– Verifying the PS Handover from GSM to LTE
Urgent Reselection Allowed to FORBID(Forbid), Cell Load Reselection
Allowed to FORBID(Forbid), and Cell Service Reselection Allowed to
FORBID(Forbid).
2. Use an MS that camps on the serving cell to download or upload data. Trace PS
messages over the Um interface and PTP messages over the Gb interface on the
LMT by referring to Tracing PS Domain Messages on the Um Interface and
3. Adjust the position of the MS or increase the power in the target cell so that the
level of the target cell is higher than that of the serving cell.
4. Check the messages traced over the Um and Gb interfaces. If the following
messages are traced, the PS handover from GSM to LTE based on coverage is
enabled.
– Gb interface: the PS Handover Required message from BSC to SGSN
– Gb interface: the PS Handover Required Acknowledge message from SGSN
to BSC.
– Um interface: the PS Handover Command message from BSC to MS.
– Verifying the PS Handover from LTE to GSM
1. Use an MS that camps on the LTE serving cell to download or upload data. Trace
the PS messages over the Um interface and PTP messages over the Gb interface
on the LMT by referring to Tracing PS Domain Messages on the Um Interface and
2. Adjust the position of the MS or increase the power in the target GSM cell so that
the level of the target GSM cell is higher than that of the serving cell.
3. Check the PS services on the Um interface and the messages traced over the Gb
interface on the target GSM cell. If PS services are processed normally on the Um
interface and the following messages are traced over the Gb interface, the PS
handover from LTE to GSM based on coverage is enabled.
– Gb interface: the Handover Request message from SGSN to BSC
– Gb interface: the PS Handover Request Acknowledge message from BSC to
SGSN
– Gb interface: the PS Handover Complete message from BSC to SGSN
NOTE
Before the verification, set Support In LTE Inter-cell PS Handover to UNSUPPORT

(Not Support) for all cells except the target GSM cell. After the verification, set Support
In LTE Inter-cell PS Handover back to SUPPORT(Support) for these cells.
Batches). In this step, set Support Out LTE Inter-cell PS Handover to

UNSUPPORT(Not Support) and set Support In LTE Inter-cell PS Handover to

----End
Example
//Activating the PS Handover from GSM to LTE
SET GCELLGPRS: IDTYPE=BYID, CELLID=0, GPRS=SupportAsInnPcu, NC2SPT=YES,
SPTLTEOUTBSCPSHO=SUPPORT;
SET GCELLNC2PARA: IDTYPE=BYID, CELLID=0, MINACCRXLEV=15, RESELHYST=6,
PENALTYRXLEV=30, PENALTYLASTTM=10, ALLOWEDMEASRPTMISSEDNUM=4,
FILTERWNDSIZE=6, NORMALRESELALLOW=PERMIT, RESELWATCHPERIOD=10,
RESELWORSENLEVTHRSH=1, RESELINTERVAL=2;
SET GCELLPRIEUTRANSYS: IDTYPE=BYID, CELLID=0, EUTRANPRI=7;
//Activating the PS Handover from LTE to GSM
SPTLTEINBSCPSHO=SUPPORT;
SET GCELLNC2PARA: IDTYPE=BYID, CELLID=0, URGENTRESELALLOW=FORBID,
LOADRESELALLOW=FORBID, TrafficReselAllow=FORBID;
SPTLTEINBSCPSHO=UNSUPPORT, SPTLTEOUTBSCPSHO=UNSUPPORT;

Feature Activation Guide on Quality

GSM and LTE Based on Quality
PS Handover Between GSM and LTE Based on Quality.
Prerequisites
l License
NOTE
the feature of PS Handover Between GSM and LTE Based on Quality.

Context
the PS handover.
Procedure
(NC2).
– Set Cell Urgent Reselection Allowed to PERMIT(Permit).
– Set MS Rx Quality Statistic Threshold as required, for example, 200.
– Set Cell Rx Quality Worsen Ratio Threshold as required, for example, 30.
– Set EDGE GMSK Quality Threshold as required, for example, 7.
– Set EDGE 8PSK Quality Threshold as required, for example, 16.
– Set GPRS Quality Threshold as required, for example, 5.
Priority to 7.


SUPPORT(Support).
Normal Reselection Allowed to FORBID(Forbid) and Cell Load Reselection
Allowed to FORBID(Forbid).
3. Adjust the position of the MS or increase the power in the target cell so that the
level of the target cell is higher than that of the serving cell.
messages are traced, the PS handover from GSM to LTE based on quality is
enabled.
to BSC.
2. Adjust the position of the MS or increase the power in the target GSM cell so that
the level of the target GSM cell is higher than that of the serving cell.
handover from LTE to GSM based on quality is enabled.
– Gb interface: the PS Handover Request message from SGSN to BSC
SGSN
NOTE
Before the verification, set Support In LTE Inter-cell PS Handover to

UNSUPPORT(Not Support) for all cells except the target GSM cell. After the
verification, set Support In LTE Inter-cell PS Handover back to SUPPORT
(Support) for these cells.

Support Out LTE Inter-cell PS Handover to UNSUPPORT(Not Support) and
Support In LTE Inter-cell PS Handover to UNSUPPORT(Not Support).
----End
Example
FILTERWNDSIZE=6, MSRXQUALSTATTHRSH=200, CELLRXQUALWORSENRATIOTHRSH=30,
URGENTRESELALLOW=PERMIT, RESELINTERVAL=2, EGPRSBEPLIMITGMSK=7,
EGPRSBEPLIMIT8PSK=16, GPRSRXQUALLIMIT=5;
NORMALRESELALLOW=FORBID, TrafficReselAllow=FORBID;

Feature Activation Guide on Cell Load

GSM and LTE Based on Cell Load
PS Handover Between GSM and LTE Based on Cell Load.
Prerequisites
l License
NOTE
the feature of PS Handover Between GSM and LTE Based on Cell Load.

Context
the PS handover.
Procedure
(NC2).
– Set Cell Load Reselection Allowed to PERMIT(Permit).
– Set Load Reselection Start Threshold as required, for example, 85.
– Set Load Reselection Receive Threshold as required, for example, 6.
– Set Load Reselect Level Threshold as required, for example, 40.
Priority to 7.


SUPPORT(Support).
Normal Reselection Allowed to FORBID(Forbid) and Cell Urgent Reselection
Allowed to FORBID(Forbid).
2. Use an MS that camps on the serving cell to download or upload data. Trace the
PS messages over the Um interface and PTP messages over the Gb interface on
the LMT by referring to Tracing PS Domain Messages on the Um Interface and
3. Use more MSs to perform GPRS services in the serving cell.
messages are traced, the PS handover from GSM to LTE based on cell load is
enabled.
to BSC.
2. Use more MSs to perform GPRS services in the serving cell.
handover from LTE to GSM based on cell load is enabled.
– Gb interface: the PS Handover Request message from SGSN to BSC
SGSN
NOTE
Before the verification, set Support In LTE Inter-cell PS Handover to

UNSUPPORT(Not Support) for all cells except the target GSM cell. After the
verification, set Support In LTE Inter-cell PS Handover back to SUPPORT
(Support) for these cells.

Support Out LTE Inter-cell PS Handover to UNSUPPORT(Not Support), and

Support In LTE Inter-cell PS Handover to UNSUPPORT(Not Support).
----End
Example
FILTERWNDSIZE=6, LOADRESELSTARTTHRSH=85, LOADRESELRXTHRSH=6,
LOADRESELALLOW=PERMIT, RESELINTERVAL=2, LOADRESELMAXRXLEV=40;
NORMALRESELALLOW=FORBID, TrafficReselAllow=FORBID;

GBSS14.0
Feature Activation Guide 220 Configuring GSM/LTE Service Based PS Handover
220 Configuring GSM/LTE Service Based

PS Handover
GSM/LTE Service Based PS Handover.
Prerequisites
l License
– The dual-mode MS supports the PS handover between GSM and LTE.
– The SGSN supports the PS handover between GSM and LTE.
– The SGSN carries the Service E-UTRAN CCO IE.
– The SGSN support the PFC procedure.
– The GSM cell is configured with neighboring LTE cells, and the neighboring LTE cells
NOTE
You can Run the BSC6900 MML command ADD GEXTLTECELL (CME single
Management > External Cell Configuration > BSC LTE External Cell; CME batch
modification center: 3.21 Modifying BSC External Cell Parameters in Batches) to add a
neighboring LTE cell, in this step, set EUTRAN Cell Type according to the actual situation, and
Run the BSC6900 MML command SET GCELLHOBASIC (CME single configuration: Cell
Configuration Express > Handover Data > Basic Handover Parameters of Cell; CME batch
modification center: 3.20 Modifying GSM Cell Parameters in Batches) to configure the
neighboring LTE cells to support the cell reselection, in this step, set LTE Cell Reselection

GBSS14.0
– The LTE cell is configured with neighboring GSM cells. In addition, the LTE cell
supports the feature of PS Handover Between GSM and LTE Based on Coverage.
Context
the PS handover.
Procedure
(NC2).
Cell Parameters in Batches), set Cell Service Reselection Allowed to PERMIT
(Permit).
SUPPORT(Support).
Normal Reselection Allowed to FORBID(Forbid), set Cell Urgent Reselection
Allowed to FORBID(Forbid) and Cell Load Reselection Allowed to FORBID
(Forbid).

GBSS14.0
3. Inform an engineer at the NSE to configure the subscription information of this

MS to ensure that the LTE network is preferentially selected.
NOTE
The following message from the SGSN to the BSC can be traced over the Gb interface: the DL-
UNITDATA message with the Service E-UTRAN CCO IE setting to Network initiated cell
change order to E-UTRAN or PS handover to E-UTRAN procedure should be
performed.
messages are traced, the PS handover from GSM to LTE based on coverage is
enabled.
to BSC.
2. Inform an engineer at the LTE to trigger the handover of this service from LTE to
GSM.
handover from LTE to GSM based on coverage is enabled.
– Gb interface: the Handover Request message from SGSN to BSC
SGSN
NOTE
Before the verification, set Support In LTE Inter-cell PS Handover to UNSUPPORT

(Not Support) for all cells except the target GSM cell. After the verification, set Support
In LTE Inter-cell PS Handover back to SUPPORT(Support) for these cells.
Batches). In this step, set Support Out LTE Inter-cell PS Handover to
UNSUPPORT(Not Support) and set Support In LTE Inter-cell PS Handover to
----End
Example
SET GCELLNC2PARA: IDTYPE=BYID, CELLID=0, TrafficReselAllow=PERMIT;

GBSS14.0

LOADRESELALLOW=FORBID, NORMALRESELALLOW=FORBID;

GBSS14.0
Feature Activation Guide 221 Configuring eNC2 Between GSM and LTE
221 Configuring eNC2 Between GSM

and LTE
eNC2 Between GSM and LTE. Here, eNC2 is short for Network Control Mode 2.
Prerequisites
– The DPU board that supports the built-in PCU is installed.
feature depends on the optional features GBFD-114101 GPRS and GBFD-511301 Cell
Reselection Between GSM and LTE.
l License
l The Gb interface is configured. For details, see Configuring the Gb Interface (over FR) and
Configuring the Gb Interface (over IP).
NOTE
Context
l This feature can be configured to implement the network-controlled cell reselection from
GSM to LTE for an MS.

GBSS14.0
l With this feature, an MS in a cell with poor signal quality, heavy load, or low signal level
can reselect a neighboring cell with good signal quality, light load, or high signal level.
Compared with the MS-controlled cell reselection, the network-controlled cell reselection
considers factors such as the service type of the MS, and receive level, traffic load, and
signal level of neighboring cells so that the MS can reselect a better cell.
Procedure
and Support NC2 to YES(Yes).
Parameters in Batches). In this step, set Network Control Mode to NC2(NC2).
configuration: Cell Configuration Express > GPRS Attributes > NC2 Parameters
of 2G Cell; CME batch modification center: 3.20 Modifying GSM Cell Parameters
in Batches). In this step, set Cell Urgent Reselection Allowed, Cell Load
Reselection Allowed, Cell Normal Reselection Allowed, and Cell Service
Reselection Allowed to PERMIT(Permit). Set the related parameters as required
according to network plan.
Modifying GSM Cell Parameters in Batches). In this step, set EUTRAN Priority
to 7.
1. Make the MS camp on the serving GSM cell. Then, use the MS to perform GPRS
services, and trace the signaling on the Um interface by referring to Tracing PS
Domain Messages on the Um Interface.
2. Move the MS, increase the power of the target cell so that the level of the target cell
is higher than that of the serving cell, or increase the number of MSs in the serving
cell.
3. Check the messages traced over the Um interface. If the following messages are traced,
the eNC2 between GSM and LTE is enabled.
– The Packet Measurement Report message from MS to BSC.
– The Packet Cell Change Order message from BSC to MS.
and Support NC2 to NO(No).
----End

GBSS14.0
Example
//Activating eNC2 Between GSM and LTE
SET GCELLGPRS: IDTYPE=BYID, CELLID=0, GPRS=SupportAsInnPcu, NC2SPT=YES;
SET GCELLNC2PARA: IDTYPE=BYID, CELLID=0, URGENTRESELALLOW=PERMIT,
LOADRESELALLOW=PERMIT, NORMALRESELALLOW=PERMIT, TRAFFICRESELALLOW=PERMIT;
//Deactivating eNC2 Between GSM and LTE
SET GCELLGPRS: IDTYPE=BYID, CELLID=0, GPRS=SupportAsInnPcu, NC2SPT=NO;

GBSS14.0
Feature Activation Guide 222 Configuring eNACC Between GSM and LTE
222 Configuring eNACC Between GSM

and LTE
eNACC Between GSM and LTE. Here, eNACC is short for External Network Assisted Cell
Change. (This feature cannot be configured using the CME. )
Prerequisites
– The DPU board that supports the built-in PCU is installed.
This feature depends on the optional features GBFD-114101 GPRS and GBFD-511301
l License
l The Gb interface is configured. For details, see Configuring the Gb Interface (over FR) and
Configuring the Gb Interface (over IP).
NOTE
You can Run the BSC6900 MML command ADD GEXTLTECELL to add a neighboring LTE cell,
in this step, set EUTRAN Cell Type according to the actual situation, and Run the BSC6900 MML
command SET GCELLHOBASIC to configure the neighboring LTE cells to support the cell
reselection, in this step, set LTE Cell Reselection Allowed to YES(Yes).
Context
l The eNACC between E-UTRAN and GERAN supports only the relocation of MSs from
E-UTRAN to GERAN.
l The eNACC can be configured to accelerate the cell reselection of an MS and shorten the
period of service disruption caused by cell reselection.

GBSS14.0
Feature Activation Guide 222 Configuring eNACC Between GSM and LTE
NOTE
The verification procedure must be performed immediately after the activation procedure; otherwise, the
verification cannot be performed.
Procedure
1. Run the BSC6900 MML command MOD NSE. In this step, set RIM Support to
YES(Support).
NOTE
This operation affects the services of all the cells under the NSE. Perform the operation when
the traffic volume is low.
1. Trace SIG messages over the Gb interface on the LMT by referring to Tracing SIG
Messages on the Gb Interface.
2. Check the messages traced over the Gb interface. If the following messages are traced,
the eNACC between GSM and LTE is enabled.
– The RAN INFORMATION REQ message from SGSN to BSC.
– The RAN INFORMATION message from BSC to SGSN.
1. Run the BSC6900 MML command MOD NSE. In this step, set RIM Support to NO
(No Support).
NOTE
This operation affects the services of all the cells under the NSE. Perform the operation when
the traffic volume is low.
----End
Example
//Activating eNACC Between GSM and LTE
MOD NSE: NSEI=0, RIMSUP=YES;
RST SIGBVC: NSEI=0;
//Deactivating eNACC Between GSM and LTE
MOD NSE: NSEI=0, RIMSUP=NO;
RST SIGBVC: NSEI=0;

GBSS14.0
Feature Activation Guide 223 Configuring SRVCC
223 Configuring SRVCC
Single Radio Voice Call Continuity (SRVCC).
Prerequisites
l License
Context
l The SRVCC feature enables the speech services that are carried on the IP Multimedia
Subsystem (IMS) to be handed over to the GSM EDGE Radio Access Network (GERAN).
An MS accesses the IMS to maintain the speech service through the CS domain in the
GERAN or the PS domain in the Evolved UMTS Terrestrial Radio Access Network (E-
UTRAN).
l The SRVCC feature supports only handover of speech services from E-UTRAN to
GERAN. It is available only when the E-UTRAN and the GERAN cover the same area.
Procedure
Parameters in Batches). In this step, set SRVCC Handover Allowed to YES
(Yes), and set the following parameters value same as the value settings on the MSC
Server:
– LTE SAI MCC
– LTE SAI MNC

GBSS14.0
Feature Activation Guide 223 Configuring SRVCC
– LTE SAI LAC

– LTE SAI SAC
1. Run the BSC6900 MML command LST GCELLHOBASIC to query SRVCC
Handover Allowed.
Expected result: The value of SRVCC Handover Allowed is Yes.
2. Tracing the A interface signaling on the LMT by referring to Tracing Messages on
the A Interface. On the Basic tab page, specify the DPC of the test cell for the DPC
(Hex) in the DPC Configuration. Click BSSAP tab in the Trace Type. On the
BSSAP tab page, specify the ID of the test cell for the Cell ID(cell1,cell2,...cell16)
in the Cell. Then click Submit.
3. After the A interface signaling tracing window is displayed, use a GSM/LTE dual-
mode MS to camp on the LTE cell and then make a call.
Expected result: The Handover Request and Handover Complete messages are
traced over the A interface.
Parameters in Batches). In this step, set SRVCC Handover Allowed to NO(No).
----End
Example
//Activating SRVCC
SET GCELLHOBASIC: IDTYPE=BYID, CELLID=0, SRVCCHOEN=YES, LTESAIMCC=538,
LTESAIMNC=735, LTESAILAC=2497, LTESAISAC=3685;
//Deactivating SRVCC
SET GCELLHOBASIC: IDTYPE=BYID, CELLID=0, SRVCCHOEN=NO;

GBSS14.0 224 Configuring Multi Technology Neighbour Cell Based
Feature Activation Guide Handover
224 Configuring Multi Technology

Neighbour Cell Based Handover
Multi Technology Neighbour Cell Based Handover.
Prerequisites
– None
feature depends on the feature GBFD-119502 PS Handover.
l License
– The MS and SGSN support the PS handover.
– GSM neighboring cells, UMTS neighboring cells, and LTE neighboring cells are
configured.
Context
This feature allows the users to configure priorities to GSM, UMTS, and LTE neighboring cells
of a GSM cell on the BSC. If handover conditions (for example, level) are met, the MS is handed
over to a neighboring cell with a higher priority.
NOTE
Assume that the serving GSM cell and two LTE external cells are configured as neighboring cells.
Procedure
1. Run the BSC6900 MML command MOD GLTENCELL (CME single configuration:

batch modification center: not supported) to set Index Type (Not required on the
CME) to BYID(By Index), Source Cell Index to the index of the serving GSM cell,
Neighbor Cell Index to the index of LTE neighboring cell 1, and Neighboring Cell
Priority to 4.
CME) to BYID(By Index), Source Cell Index to the index of the GSM serving cell,
Priority to 5.
1. Use an MS to perform the download service in the GSM cell.
2. On the LMT, On the MT, trace PTP messages on the Gb interface and PS domain
messages on the UM interface by referring to Tracing PTP Messages On the Gb
Interface and Tracing PS Domain Messages on the Um Interface.
3. Relocate the MS to trigger the PS handover.
4. Check the messages traced over the Gb and Um interfaces. If the following messages
exist, it indicates that the MS is handed over to LTE neighboring cell 2 to perform the
PS service.
– Gb interface: the PS Handover Required message from BSC to SGSN. In this
message, Target eNB identifier is LTE neighboring cell 2.
– Gb interface: the PS Handover Required Acknowledge from SGSN to BSC.
– Um interface: the PS Handover Command from BSC to MS.
5. Run the BSC6900 MML command MOD GLTENCELL to set Index Type (Not
required on the CME) to BYID(By Index), Source Cell Index to the index of the
GSM serving cell, Neighbor Cell Index to the index of LTE neighboring cell 2, and
Neighboring Cell Priority to 2.
6. Use an MS to perform the download service in the GSM cell. Relocate the MS to
trigger the PS handover.
7. Check the message process over the Gb interface and Um interface. If the following
messages exist, it indicates that the MS is handed over to LTE neighboring cell 1 to
perform the PS service.
– Gb interface: the PS Handover Required message from BSC to SGSN. In this
message, Target eNB identifier is LTE neighboring cell 1.
– Gb interface: the PS Handover Required Acknowledge from SGSN to BSC.
– Um interface: the PS Handover Command from BSC to MS.
Priority to 255.

Priority to 255.
----End
Example
NCELLPRI=4; MOD GLTENCELL: IDTYPE=BYID, SRCLTENCELLID=0,
NBRLTENCELLID=9002, NCELLPRI=5;
NCELLPRI=255; MOD GLTENCELL: IDTYPE=BYID, SRCLTENCELLID=0,
NBRLTENCELLID=9002, NCELLPRI=255;

GBSS14.0
Feature Activation Guide 225 Configuring Fast LTE Reselection at 2G CS Call Release
225 Configuring Fast LTE Reselection at

2G CS Call Release
Fast LTE Reselection at 2G CS Call Release.
Prerequisites
l License
– The network is covered by both a 2G network and an LTE network.
– The UE supports both 2G and LTE frequency bands.
Context
When the 2G network and the LTE network cover the same area and this feature is activated, a
UE can process services in the LTE network immediately after the UE releases a 2G call. This
accelerates cell reselection.
Procedure
1. Run the BSC6900 MML command ADD GEXTLTECELL (CME single
Management > External Cell Configuration > BSC LTE External Cell; CME
batch modification center: 3.21 Modifying BSC External Cell Parameters in
Batches) to add an LTE external cell.
2. Run the BSC6900 MML command ADD GLTENCELL (CME single configuration:

GBSS14.0
Feature Activation Guide 225 Configuring Fast LTE Reselection at 2G CS Call Release
batch modification center: not supported) to configure the LTE cell 1 as a neighboring
cell of the 2G cell 0, and in this step, set Support Rapid Reselection to SUPPORT
(SUPPORT).
NOTE
The cell 0 must be configured as a neighboring cell of the LTE cell 1 on the LTE side.
Parameters in Batches) to set basic attributes of the BSC. In this step, set A Interface
Tag, Um Interface Tag, and Abis Interface Tag to GSM_PHASE_2Plus.
Modifying GSM Cell Parameters in Batches). In this step, set EUTRAN Priority
to a value greater than UTRAN Priority.
1. Initiate Um interface message tracing. Enable the UE to camp on cell 0, initiate a call
in cell 0 successfully, and maintain the call.
2. Hang up the call and check the network indicator displayed on the UE. The network
indicator indicates that the UE is camping on the LTE cell.
NOTE
If the 2G network and LTE network use the same network indicator, the UE must be capable
of identifying which cell the UE is camping on, a 2G cell or an LTE cell.
3. Trace the Um interface message by referring to Tracing CS Domain messages on the
Um interface. An information element (IE) "cell-selection-indicator-after-release" is
contained in the downlink Channel Release message transmitted over the Um
interface.
batch modification center: not supported). In this step, set Support Rapid
Reselection to UNSUPPORT(UNSUPPORT).
----End
Example
//Activating Fast LTE Reselection at 2G CS Call Release
ADD GEXTLTECELL: EXTLTECELLID=8048, EXTLTECELLNAME="Cell1", MCC="460",
MNC="10", ENODEBTYPE=MACRO, CI=0, TAC=1, FREQ=100, PCID=0,
EUTRANTYPE=FDD;
ADD GLTENCELL: IDTYPE=BYNAME, SRCLTENCELLNAME="Ce110",
NBRLTENCELLNAME="Cell1", SPTRAPIDSEL=SUPPORT;
SET BSCBASIC: AVer=GSM_PHASE_2Plus, AbisVer=GSM_PHASE_2Plus,
UmVer=GSM_PHASE_2Plus;
GCELLPRIEUTRANSYS: IDTYPE=BYNAME, CELLNAME=Ce110, UTRANPRI=0, EUTRANPRI=1;
//Deactivating Fast LTE Reselection at 2G CS Call Release
MOD GLTENCELL: IDTYPE=BYNAME, SRCLTENCELLNAME="Ce110",
NBRLTENCELLNAME="Cell1", SPTRAPIDSEL=UNSUPPORT;

GBSS14.0
Feature Activation Guide 226 Configuring CSFB
226 Configuring CSFB
CSFB.
Prerequisites
l License
l Others
– A SGs interface is configured between the MSC server and the Mobile Management
Entity (MME).
– The MS is a GL dual-mode MS and supports CSFB.
– It is recommended that the CSFB be used together with the GBFD-511301 Cell
Reselection Between GSM and LTE and the GBFD-511312 Fast LTE Reselection at
2G CS Call Release.
Context
Circuit Switch FallBack (CSFB) is a function based on which the MS camping on the E-UTRAN
network moves to the GERNAN or UTRAN network by using PS handover or PS cell reselection
and processes CS services on the GERNAN or UTRAN network.
This feature can be enabled only when the E-UTRAN network covers the same area as the
GERAN or UTRAN network.
Procedure
– when the MSC Pool function is disabled

GBSS14.0
Run the BSC6900 MML command SET GCELLSOFT (CME single configuration:
Cell Parameters in Batches). In this step, specify a target cell and set CSFB
Support to SUPPORT(Support).
– when the MSC Pool function is enabled
Support to SUPPORT(Support), set Unknown Paging Response Support to YES
(Yes).
1. Start CS single user tracing on the LMT. In this step, enter the IMSI or TMSI of the
test MS and click OK. For instructions on how to start CS single user tracing on the
LMT, see Tracing CS Domain Messages of a Single Subscriber.
2. Enable CSFB for LTE NEs on the E-UTRAN side and for the MSC on the GERAN
side.
NOTE
For instructions on how to enable CSFB for LTE NEs and for the MSC, see the related feature
configuration guide.
3. Trigger a CS paging to the MS after the MS operates services normally on the E-
UTRAN network.
4. Query the result of CS single user tracing.
Expected result: The MS sets up a call successfully at the BSC. Both signaling and
speech services are normal.
– when the MSC Pool function is disabled
Support to UNSUPPORT(Not Support).
– when the MSC Pool function is enabled
Support to UNSUPPORT(Not Support), set Unknown Paging Response Support
to NO(No).
----End
Example
//Enabling CSFB when the MSC Pool function is enabled
SET GCELLSOFT: IDTYPE=BYID, CELLID=0, SUPPORTCSFB=SUPPORT,
CSFBPAGRSPBCSWITCH=YES;
//Enabling CSFB when the MSC Pool function is disabled

GBSS14.0
SET GCELLSOFT: IDTYPE=BYID, CELLID=0,

SUPPORTCSFB=SUPPORT;
//Disabling CSFB when the MSC Pool function is enabled
SET GCELLSOFT: IDTYPE=BYID, CELLID=0, SUPPORTCSFB=UNSUPPORT,
CSFBPAGRSPBCSWITCH=NO;
//Disabling CSFB when the MSC Pool function is disabled
SET GCELLSOFT: IDTYPE=BYID, CELLID=0, SUPPORTCSFB=UNSUPPORT;

GBSS14.0
Feature Activation Guide 227 Configuring GSM/TD-SCDMA Interoperability
227 Configuring GSM/TD-SCDMA

Interoperability
GSM/TD-SCDMA Interoperability.
Prerequisites
– The MS supports both the GSM and TD-SCDMA networks. It also supports
bidirectional cell reselection and handovers between GSM and TD-SCDMA.
– The BSS and NSS support the GSM/TD-SCDMA inter-RAT cell selection, cell
reselection, and location update. In addition, they support measurement control,
handover decision, and handover signaling procedure during inter-RAT handovers.
l License
The basic data has been configured. For details, see Configuring the Basic Data.
Context
The GSM/TD-SCDMA Interoperability feature enables an MS to be handed over to or reselect
a GSM cell if the serving cell of the MS is not covered by the TD-SCDMA network or in the
area with weak TD-SCDMA coverage. When a dual-mode MS enters the coverage of the TD-
SCDMA network again, or the MS detects that the signal quality in the TD-SCDMA cell is
higher than that in the serving GSM cell, the MS can be handed over to or reselect a TD-SCDMA
cell if the handover or cell reselection conditions are met. Then, the MS can enjoy the various
services provided by the TD-SCDMA network.
Procedure

GBSS14.0
1. Configure parameters for an inter-RAT neighboring cell reselection or handover.

a. Run the BSC6900 MML command ADD GEXT3GCELL (CME single
configuration: Object Group > GSM Service Configuration and
Maintenance Management > External Cell Configuration > BSC 3G
External Cell; CME batch modification center: 3.21 Modifying BSC External
Cell Parameters in Batches) to add a 3G external cell. In this step, set Utran
Cell Type to TDD(TDD).
b. Run the BSC6900 MML command ADD G3GNCELL (CME single
Neighbor Cell; CME batch modification center: not supported) to add a
neighboring 3G cell.
c. Run the BSC6900 MML command SET BSCBASIC (CME single
d. Run the BSC6900 MML command SET OTHSOFTPARA (CME single
Configuration > Other Software Parameters of BSC; CME batch
modification center: 3.17 Modifying GBSC Parameters in Batches). In this
step, set Support Sent 2QUATER, Send 3G Class Flag, and Classmark
Enquiry With 3G Request all to YES(Yes).
e. Run the BSC6900 MML command SET GCELLSOFT (CME single
Query Classmark after In-BSC HO Enabled to YES(Yes).
f. Optional: Run the BSC6900 MML command SET
GCELLPSOTHERPARA (CME single configuration: Cell Configuration
Express > GPRS Attributes > Other GPRS Parameters of 2G Cell; CME
batch modification center: 3.20 Modifying GSM Cell Parameters in
Batches). In this step, set GSM-to-TD Cell Reselection Allowed and
Neighboring 3G Cells Filtering Mode to appropriate values.
g. Run the BSC6900 MML command SET GCELLCCBASIC (CME single
Basic Parameters of Cell; CME batch modification center: 3.20 Modifying
GSM Cell Parameters in Batches) to set the basic call control parameters of
the cell. In this step, set ECSC to YES(Yes).
h. Optional: Run the BSC6900 MML command SET GCELLPSBASE (CME
single configuration: Cell Configuration Express > GPRS Attributes > Basic
PS Attributes of 2G Cell; CME batch modification center: 3.20 Modifying
GSM Cell Parameters in Batches). In this step, set Network Control Mode to
i. Run the BSC6900 MML command SET GCELLHOBASIC (CME single
Modifying GSM Cell Parameters in Batches) to set the basic handover
parameters of a cell. In this step, set Inter-RAT Cell Reselection Enable to
YES(Yes).

GBSS14.0
j. Run the BSC6900 MML command SET GCELLCCUTRANSYS (CME single

UTRAN System Message Parameters of Cell; CME batch modification center:
3.20 Modifying GSM Cell Parameters in Batches) to set the UTRAN system
message parameters for call control in a cell. In this step, set Qsearch I, Qsearch
C, and Qsearch P to 7, and set Qsearch C Initial to Always(Always).
2. Enable GSM/TD-SCDMA interoperability optimization for MSs in idle mode.
Run the BSC6900 MML command SET GCELLCCUTRANSYS (CME single
Modifying GSM Cell Parameters in Batches). In this step, set TDD System
Information Optimized Allowed to YES(Yes), and set TDD MI System INFO
Broadcasting Prohibit and TDD MI System Information Optimized to appropriate
values.
3. Disable GSM/TD-SCDMA inter-RAT CS handover if necessary. Enable GSM/TD-
SCDMA interoperability optimization for MSs in dedicated mode.
Run the BSC6900 MML command SET GCELLCCUTRANSYS (CME single
Modifying GSM Cell Parameters in Batches). In this step, set TDD MI System
INFO Broadcasting Prohibit to YES(Yes), TDD MI System Information
Optimized to NO(No), and set TDD Cell Reselect Diversity, Best TDD Cell
Number, TDD Reporting Offset, and TDD Reporting Threshold to appropriate
values.
1. Run the BSC6900 MML command LST GEXT3GCELL to query the value for
Utran cell type.
Expected result: The value for Utran cell type is TDD(TDD).
2. Query the MS frequency when the MS is in a GSM cell.
Expected result: The MS frequency indicates that the MS is in a GSM cell.
3. Move the MS to initiate a call reselection from a GSM cell to a TD-SCDMA cell.
When measuring neighboring TD-SCDMA (TDD) cells, the MS initiates a cell
reselection if the Received Signal Code Power (RSCP) of Common Pilot Channel
(CPICH) is normal and CPICH RSCP is greater than the value for
TDDCELLRESELDIV.
4. Query the MS frequency again.
Expected result: The MS frequency indicates that the MS is in a TD-SCDMA cell.
batch modification center: not supported) to remove a neighboring 3G cell.
2. Run the BSC6900 MML command RMV GEXT3GCELL (CME single
modification center: not supported) to remove a 3G external cell.

GBSS14.0
Parameters in Batches) to set the basic handover parameters of a cell. In this step,
set Inter-RAT Cell Reselection Enable to NO(No).
----End
Example
// Activating GSM/TD-SCDMA Interoperability
UTRANCELLTYPE=TDD, SYNCCASE=SyncCase1;
SET BSCBASIC: AVer=GSM_PHASE_2Plus;
SET GCELLSOFT: IDTYPE=BYID, CELLID=0, QUERYCMAFTERINBSCHO=YES;
SET OTHSOFTPARA: Send2QuterFlag=YES, SendUtranECSCFlag=YES,
CLASSMARKQUERY=YES;
QSEARCHC=7;
// Deactivating GSM/TD-SCDMA Interoperability

RMV G3GNCELL: EXT3GCELLID=5048, EXT3GCELLNAME="5048";
RMV GEXT3GCELL: IDTYPE=BYID, SRC3GNCELLID=0, NBR3GNCELLID=5048;
SET GCELLHOBASIC: IDTYPE=BYID, CELLID=0, INTERRATCELLRESELEN=NO;

GBSS14.0 228 Configuring Iur-g Interface Between GSM and TD-
Feature Activation Guide SCDMA
228 Configuring Iur-g Interface Between

GSM and TD-SCDMA
Iur-g Interface Between GSM and TD-SCDMA.
Prerequisites
– The IP interface board is installed.
l License
– The UE supports both the GSM and TD-SCDMA modes.
– The UE supports full-rate AMR.
– The related parameters for the transmission between GSM and TD-SCDMA are
negotiated.
Context
The Iur-g interface is used for information exchange between the BSC and the TD-RNC.
Through the information exchange and common measurement procedures, the BSC and TD-
RNC can obtain the capacity and load information of each other.
Procedure
batch modification center: not supported). In this step, set DSP type to IUR_G
(IUR_G) and DSP bear type to M3UA(M3UA).

Entity; CME batch modification center: not supported) command to add an M3UA
local entity.
Entity; CME batch modification center: not supported) command to add an M3UA
destination entity.
Panel > Add Board; CME batch modification center: not supported) to add an IP
interface board.
5. Configure the physical layer and the data link layer.
– The FG2a, GOUa, FG2c, GOUc, FG2d and GOUd boards adopt IP over FE/GE
transmission.
a. Run the BSC6900 MML command SET ETHPORT (CME single
configuration: Device Panel > Right click Board > Properties > Ethernet
Port Parameters; CME batch modification center: not supported) to set the
attributes of the Ethernet port.
b. (Optional) Run the BSC6900 MML command ADD ETHREDPORT
(CME single configuration: Device Panel > Right click Board >
Properties > Ethernet Red Port; CME batch modification center: not
supported) to add active and standby Ethernet ports if required.
c. Run the BSC6900 MML command ADD ETHIP (CME single configuration:
(G)IURG Configuration Express > IP Transport > Ethernet Port IP
Address; CME batch modification center: not supported) to add an IP address
for the Ethernet port. In this step, set Local IP address based on the network
plan. When multiple VLAN gateways are planned, run this command for each
IP address you want to add.
d. (Optional) When device IP is used in communication, Run the BSC6900
MML command ADD DEVIP (CME single configuration: (G)IURG
Configuration Express > IP Transport > Device IP Address; CME batch
modification center: not supported) to add a device IP address for the interface
board. In this step, set Device IP Address Type and IP address to appropriate
values.
– The PEUa/POUc board adopts IP over E1/T1 transmission.
a. Run the BSC6900 MML command ADD DEVIP (CME single configuration:
(G)IURG Configuration Express > IP Transport > Device IP Address;
CME batch modification center: not supported) to add the device IP address
of the interface board. In this step, set Device IP Address Type and IP
address to appropriate values.
b. Determine the type of link carried on the E1/T1 link (PPP link or MP link
group) and perform the corresponding step.
If the E1/T1 link carries a/an... Then...
PPP link Go to step c.
MP link group Go to step d.

c. Run the BSC6900 MML command ADD PPPLNK (CME single

configuration: A Configuration Express > IP Transport > PPP Link; CME
batch modification center: not supported) to add a PPP link. In this step, set
Board Type to PEUa or POUc. To add more PPP links, run this command
for each PPP link you want to add.
d. Add MP link group data.
a. Run the BSC6900 MML command ADD MPGRP (CME single
configuration: A Configuration Express > IP Transport > MP
Group > MP Group; CME batch modification center: not supported)
to add an MP link group. In this step, set Board Type to PEUa or
POUc.
b. Run the BSC6900 MML command ADD MPLNK (CME single
configuration: A Configuration Express > IP Transport > MP
Group > MP Link; CME batch modification center: not supported) to
add an MP link. In this step, set Board Type to PEUa or POUc. To add
more MP links, run this command for each MP link you want to add.
6. Configure the control plane data (over IP).
a. Run the BSC6900 MML command ADD SCTPLNK (CME single
configuration: (G)IURG Configuration Express > IP Transport > SCTP
Link; CME batch modification center: not supported) to add an SCTP link. In
this step, set Signalling link mode to CLIENT(CLIENT MOD) and
Application type to M3UA(M3UA). To add multiple SCTP links, run this
command for each SCTP link you want to add.
b. Run the BSC6900 MML command ADD M3LKS (CME single configuration:
Link Set; CME batch modification center: not supported) to add an M3UA link
set.
NOTE
l If Local entity type is set to M3UA_IPSP(M3UA_IPSP), set Work mode of the

M3UA link set to M3UA_IPSP(M3UA_IPSP).
l If Local entity type is set to M3UA_ASP(M3UA_ASP) and Destination entity
type is set to M3UA_SP(M3UA_SP), set Work mode of the M3UA link set to
M3UA_IPSP(M3UA_IPSP). In other cases, set Work mode of the M3UA link set
to M3UA_ASP(M3UA_ASP).
c. Run the BSC6900 MML command ADD M3RT (CME single configuration:
(G)IURG Configuration Express > IP Transport > M3UA Route; CME batch
modification center: not supported) to add an M3UA route.
d. Run the BSC6900 MML command ADD M3LNK (CME single configuration:
Link Set; CME batch modification center: not supported) to add an M3UA link.
To add multiple M3UA links, run this command for each M3UA link you want
to add.
1. Run the BSC6900 MML command DSP N7DPC to query the SCCP DSP state. In
this step, set DSP index to the index of the adjacent TD RNC. The result shows that
the SCCP DSP is in the accessible state.


----End

GBSS14.0 229 Configuring Radio Resource Reserved Handover
Feature Activation Guide Between GSM/TD-SCDMA Based on Iur-g
229
Reserved Handover Between GSM/TD-SCDMA
Configuring Radio Resource
Based on Iur-g
Radio Resource Reserved Handover Between GSM/TD-SCDMA Based on Iur-g.
Prerequisites
– The feature GBFD-511401 Iur-g Interface Between GSM and TD-SCDMA has been
l License
– The UE supports both the GSM and TD-SCDMA modes.
– The UE supports full-rate AMR.
– The related parameters for the transmission between GSM and TD-SCDMA are
negotiated.
– The neighboring cell relationship is properly configured on the TD-RNC. Iur-g
Interface Existence Symbol is set to YES(Yes) and Iur-g Interface Supporting
Inter-RAT CS Handover is set to YES(Yes).
Context
In this feature, radio resource reservation is added to the standard GSM/TD-SCDMA handover
procedure through the information exchange on the Iur-g interface between the BSC and the
TD-RNC. In this way, the resource reservation procedure is completed without CN forwarding.

Procedure
Parameters in Batches). In this step, set Index Type (Not required on the CME) to
BYID(By Index), specify the cell ID, and set Inter-RAT In BSC Handover
Enable to YES(Yes) and Allow Incoming BSC Handover at Iur-g to YES(Yes).
NOTE
Carry Speech Data at Iur-g can be set to YES(Yes) to enable the Iur-g interface to carry the
user plane data.
2. Set the local BSC as the neighboring BSC of the TD RNC and set Handover Type
Supported by the Iur-g Interface to Carrying Signaling Plane Handover on the
TD-RNC side.
1. Run the BSC6900 MML command LST GCELLHOBASIC. The returned result
shows that Allow Incoming BSC Handover at Iur-g is set to Yes.
2. Use a UE to initiate a call in the TD-SCDMA network. The call is established.
Attenuate the signal of the TD-SCDMA cell or add path loss between the UE and the
TD-SCDMA cell until the UE is handed over from the 3G cell to a 2G cell.
3. Trace the messages transmitted on the interface between BSCs by referring to Tracing
Messages on the Inter-BSC Interface. You can view additional handover signaling in
the tracing window. Figure 229-1 shows the messages traced on the interface between
BSCs.
Figure 229-1 Messages traced on the interface between BSCs
Parameters in Batches). In this step, set Index Type (Not required on the CME) to
BYID(By Index) and specify the cell index. In addition, set Allow Incoming BSC
Handover at Iur-g to NO(No). If the user plane transmission over the Iur-g interface
also needs to be deactivated, set Inter-RAT In BSC Handover Enable to NO(No).
NOTE
If Inter-RAT In BSC Handover Enable is set to NO(No) before this feature is activated, set this
parameter to NO(No) when deactivating this feature.
----End
Example
//Activating Radio Resource Reserved Handover Between GSM/TD-SCDMA Based
on Iur-g
SET GCELLHOBASIC: IDTYPE=BYID, CELLID=2, INTERRATINBSCHOEN=YES,
InterRatIurgInBscHoEn=YES;
//Deactivating Radio Resource Reserved Handover Between GSM/TD-SCDMA
Based on Iur-g

SET GCELLHOBASIC: IDTYPE=BYID, CELLID=2, INTERRATINBSCHOEN=NO,

InterRatIurgInBscHoEn=NO;

GBSS14.0
Feature Activation Guide 230 Configuring Extended BCCH
230 Configuring Extended BCCH
Extended BCCH.
Prerequisites
l License
– The MS supports this feature.
Context
SI2Quater and SI13 messages are sent on the same normal BCCH as other system information
messages. Only one message is sent in a scheduling period, leading to a long delay. If SI2Quater
and SI13 messages are specified to be broadcast on an extended BCCH, only these two types of
messages are broadcast on the extended BCCH. In addition, one SIQuater or SI13 message is
broadcast in each scheduling period. This speeds up the scheduling and broadcasting of
SI2Quater and SI13 messages. As a result, MSs quickly obtain system information messages
for inter-RAT cell reselection, and the delay in cell reselection decreases.
Procedure
Batches). In this step, set CCCH Blocks Reserved for AGCH to a value greater than
0.

GBSS14.0

Modifying GSM Cell Parameters in Batches). In this step, set 2Quater Message
Transmission Channel to BCCH_Ext(BCCHExt).
Batches). In this step, set Channel of Sending SI13 Message to BCCH_Ext(BCCH
Ext).
1. Run the BSC6900 MML command SND GCELLSYSMSG to send system
information messages. Initiate Abis interface message tracing by referring to Tracing
CS Domain Messages on the Abis Interface. In the Trace Type area, click RSL to
trace RSL messages on the Abis interface. If the value of si2-quater-position in SI
Type 3 is 1, SI2quater is sent on the extended BCCH, as shown in Figure 230-1.
Figure 230-1 BCCH message
2. If the value of si13-position in SI Type 3 is 1, SI13 is sent on the extended BCCH,

and this feature has been activated.
Batches). In this step, set CCCH Blocks Reserved for AGCH to 0.
Modifying GSM Cell Parameters in Batches). In this step, set 2Quater Message
Transmission Channel to BCCH_Norm(BCCH Norm).
Batches). In this step, set Channel of Sending SI13 Message to BCCH_Norm
(BCCH Norm).
----End
Example
//Activating Extended BCCH
SET GCELLIDLEBASIC: IDTYPE=BYID, CELLID=0, BSAGBLKSRES=1;
SET GCELLCCUTRANSYS: POS2QUATER=BCCHExt;
SET GCELLCCAD: IDTYPE=BYID, POSSI13=BCCH_Ext;

GBSS14.0
//Verifying Extended BCCH

//Deactivating Extended BCCH

SET GCELLIDLEBASIC: IDTYPE=BYID, CELLID=0, BSAGBLKSRES=0;
SET GCELLCCUTRANSYS: POS2QUATER=BCCHNorm;
SET GCELLCCAD: IDTYPE=BYID, POSSI13=BCCH_Norm;

GBSS14.0
Feature Activation Guide 231 Configuring NC2 Between GSM and TD-SCDMA
231 Configuring NC2 Between GSM and

TD-SCDMA
NC2 between GSM and TD-SCDMA.
Prerequisites
– The DPU board that supports the built-in PCU is configured.
GBFD-114101 GPRS, GBFD-114302 GSM/TD-SCDMA Interoperability, and
GBFD-511401 Iur-g Interface Between GSM and TD-SCDMA (dependent on this
feature if the neighboring TD-SCDMA cell load is a prerequisite to cell reselection).
– The feature cannot be used together with the feature GBFD-118702 MOCN Shared,
Cell GBFD-114151 DTM, and GBFD-511110 BSC supporting Blind Search.
The TD-SCDMA neighboring cell load acquisition function in the NC2 between GSM
and TD-SCDMA feature is mutually exclusive with the GSM/TD-SCDMA cell
reselection optimization for MSs in packet transfer mode in the GBFD-114302 GSM/
TD-SCDMA Interoperability feature.
l License
– The MS must support all of the following: GSM and TD-SCDMA, bidirectional cell
reselection between GSM and TD-SCDMA, NC2 between GSM and TD-SCDMA, and
the processing of neighboring TD-SCDMA cell information contained in the Packet
Measurement Order message.
– The BSS and NSS support bidirectional cell reselection between GSM and TD-
SCDMA.
– A GSM cell is configured with a neighboring TD-SCDMA cell, and the neighboring
TD-SCDMA cell supports cell reselection.

GBSS14.0
Context
With this feature, a dual-mode MS in a GSM cell can reselect a neighboring TD-SCDMA cell
if the neighboring cell is not overloaded and the signal quality in the neighboring cell is good.
This feature improves users experience. It also reduces the traffic load in GSM and improves
the resource utilization in TD-SCDMA.
Procedure
Parameters in Batches). In this step, set GSM-to-TD Cell Reselection Allowed to
FORCENC2(Force NC2 Mode).
2. Run the BSC6900 MML command SET GCELLRESELECTUTRANTDD (CME
single configuration: Cell Configuration Express > GPRS Attributes > UTRAN
TDD Reselection Parameters of 2G Cell; CME batch modification center: 3.20
Modifying GSM Cell Parameters in Batches). In this step, set
TDD_MULTIRAT_REPORTING, TDD_REPORTING_OFFSET,
TDD_REPORTING_THRESHOLD, TDD Neighboring Cell Overload
Threshold, and TDD Reselection time Threshold to appropriate values.
3. Run the BSC6900 MML command ADD IMEIGRP (CME single configuration:
GSM Global Configuration Express > BSC Basic Configuration > IMEI group;
CME batch modification center: not supported). In this step, set IMEI Group
Index. IMEI Group Description, Start IMEI and End IMEI to appropriate values.
NOTE
The BSC initiates the NC2 procedure only to the GSM/TD-SCDMA MSs in the IMEI group.
1. Initiate Um interface PS message tracing on the BSC6900 LMT by referring to Tracing
PS Domain Messages on the Um Interface. In this step, Select Cell from the Trace
Type drop-down combo box, and specify Cell ID.
2. Use a dual-mode MS to perform PS services in a GSM cell. Expected result: The
following messages are traced in the PS domain on the Um interface, which indicates
that this feature takes effect:
– Packet Measurement Order: sent by the BSC to the MSs using configured IMEIs.
– Packet Measurement Report message: periodically sent by the MS to the BSC.
– Packet Cell Change message: sent by the BSC to the MS when the signal level of
a neighboring TD-SCDMA cell carried in a Packet Measurement Report message
exceeds the RSCP threshold for layer of 3G cell and the MS keeps processing
PS services for the duration longer than TddReselTimeThd. The RSCP threshold
for layer of 3G cell can be queried by running the BSC6900 MML command LST
GEXT3GCELL.

GBSS14.0
Parameters in Batches). In this step, set GSM-to-TD Cell Reselection Allowed to

NORMAL(Normal NC Mode).
----End
Example
//Activating NC2 between GSM and TD-SCDMA
SET GCELLPSOTHERPARA: IDTYPE=BYID, CELLID=0, GSMTOTDALLOWED=FORCENC2;
SET GCELLRESELECTUTRANTDD: IDTYPE=BYID, CELLID=0, PsBestTddCellNum=1,
PsTddCellRptOff=0, PsTddCellRptThd=0, TddNCellLoadThd=60,
TddReselTimeThd=2000;
ADD IMEIGRP: ImeiGrpIndex=0, ImeiGrpDscrpt="Test_MS",
ImeiMin="353043040000000", ImeiMax="353043045000000";
//Deactivating NC2 between GSM and TD-SCDMA
SET GCELLPSOTHERPARA: IDTYPE=BYID, CELLID=0, GSMTOTDALLOWED=NORMAL;

GBSS14.0
Feature Activation Guide 232 Configuring Ciphering
232 Configuring Ciphering
A5/1 and A5/2 Ciphering Algorithm and GBFD-113503 A5/3 Ciphering Algorithm.
Prerequisites
l License
– The MSC and the MS supports ciphering.
Context
There are eight ciphering algorithms specified in the GSM protocols: A5/0, A5/1, A5/2, A5/3,
A5/4, A5/5, A5/6, and A5/7. In A5/0, ciphering is not supported. In A5/1, A5/2, and A5/3, safety
of CS and PS data of a user transmitted over the air interface is guaranteed.
Procedure
Batches). In this step, set Encryption Algorithm to A5/0 and A5/3.

GBSS14.0
NOTE
l This procedure takes A5/3 as an example. The configuration procedures of other ciphering
algorithms are similar as this procedure.
l A5/0 in the Encryption Algorithm drop-down list must be selected.
3. Optional: Set the encryption algorithm priority. Run the BSC6900 MML command
SET GCELLBASICPARA (CME single configuration: Cell Configuration
Express > Cell Attributes > Basic Parameters of Cell; CME batch modification
center: 3.20 Modifying GSM Cell Parameters in Batches) to set Encryption
Algorithm 1 to Encryption Algorithm 7 separately. For example, set Encryption
Algorithm 1 to A51(A5/1), Encryption Algorithm 2 to A52(A5/2), Encryption
Algorithm 3 to A53(A5/3), Encryption Algorithm 4 to A54(A5/4), Encryption
Algorithm 5 to A55(A5/5), Encryption Algorithm 6 to A57(A5/7), and Encryption
Algorithm 7 to A56(A5/6).
NOTE
l The default priority of the encryption algorithm in descending order is A5/7 to A5/0. If you
do not perform any configurations on the priority, use the default priority.
l Each priority corresponds to an encryption algorithm, and different priorities cannot
correspond to the same encryption algorithm.
NOTE
The verification procedures take A5/3 as an example.

1. Run the BSC6900 MML command SET BSCBASIC. In this step, set A Interface
Tag, Um Interface Tag, and Abis Interface Tag to GSM_PHASE_2Plus.
2. Run the BSC6900 MML command SET GCELLBASICPARA. In this step, set Cell
Index to the index of the test cell and Encryption Algorithm to A5/0 and A5/3.
3. Double-click A Interface Trace on the LMT to create a trace task. On the Basic tab
page, specify the DPC of the test cell in the DPC(HEX) text box. Click BSSAP in
the Trace Type area. Specify the ID of the test cell in the Cell ID (cell1,
cell2, ...cell16): text box in the BSSAP tab page. Then, click Submit.
4. After opening the A interface tracing window, use the MS to initiate a call in the test
cell.
Expected result: The call is set up, and the IE chosen-encryption-algorithm in the
Cipher Mode Complete message is gsm-a5-3.
Batches). In this step, set Cell Index to the index of the test cell and Encryption
Algorithm to A5/0.
----End
Example
//Setting Interface Tags
//Setting ciphering algorithms
SET GCELLBASICPARA: IDTYPE=BYID, CELLID=0,

GBSS14.0
ENCRY=A5/0-1&A5/1-0&A5/2-0&A5/3-1&A5/4-0&A5/5-0&A5/6-0&A5/7-0;
//Setting encryption algorithm priority
SET GCELLBASICPARA: IDTYPE=BYID, CELLID=0, EncryptionAlgorithm1st=A51,
EncryptionAlgorithm2nd=A52, EncryptionAlgorithm3rd=A53,
EncryptionAlgorithm4th=A54, EncryptionAlgorithm5th=A55,
EncryptionAlgorithm6th=A57, EncryptionAlgorithm7th=A56;
//Setting Encryption Algorithm to A5/0
SET GCELLBASICPARA: IDTYPE=BYID, CELLID=0,
ENCRY=A5/0-1&A5/1-0&A5/2-0&A5/3-0&A5/4-0&A5/5-0&A5/6-0&A5/7-0;

GBSS14.0
Feature Activation Guide 233 Configuring A5/1 Encryption Flow Optimization
233 Configuring A5/1 Encryption Flow

Optimization
This section describes how to activate, verify, deactivate the optional feature GBFD-113521
A5/1 Encryption Flow Optimization.
Prerequisites
– None
– A5/1 Encryption Flow Optimization depends on the A5/1 ciphering algorithm in the
GBFD-113501 A5/1 and A5/2 Ciphering Algorithm feature.
– The Flex TSC function is mutually exclusive with the GBFD-115830 VAMOS feature.
l License
– The A5/1 encryption algorithm has been enabled. For details, see 232 Configuring
Ciphering.
– The MSC and MSs support encryption.
Context
Based on features related to transmission over the Um interface, the A5/1 Encryption Flow
Optimization feature provides an optimized encryption procedure, enhancing network
transmission security. This feature provides several security functions, which can be enabled as
required.
Procedure
– Activating SDCCH fast handover
Run the BSC6900 MML command SET GCELLHOBASIC (CME single

GBSS14.0
Parameters in Batches) with SDCCH HO Allowed set to YES(Yes).
Cell Parameters in Batches) with SD Quick HO set to ON(On).
– Activating TCH scheduled handover
Run the BSC6900 MML command SET GCELLHOBASIC (CME single
Parameters in Batches) with Intracell HO Allowed set to YES(Yes).
Cell Parameters in Batches) with TCH Time Handover Switch set to ON(On) and
TCH Time Handover Period set to a required value.
– Activating Flex Training Sequence Code (TSC)
Cell Parameters in Batches) with Flex TSC Switch set to ON(On).
– Activating dummy bit randomization
Cell Parameters in Batches) with Dummy Bit Randomization Switch set to ON
(On).
– Activating the function of stopping sending system information 5, 5bis, or 5ter after
encryption
Cell Parameters in Batches) with Stop Send SI 5/5bis/5ter after Encrypt set to ON
(On).
– Activating the randomization of the filling information of SI 6
Cell Parameters in Batches) with SI 6 Filling Random Bits After Cipher set to YES
(Yes).
– Verifying SDCCH fast handover
1. Use an MS to initiate a call and Tracing BSSAP Messages on the A Interface.
Expected result: The Handover Performed message is displayed.
– Verifying TCH scheduled handover
1. Use an MS to initiate a call and Tracing BSSAP Messages on the A Interface.

GBSS14.0
Expected result: The call is initiated successfully and the Handover Performed
message can be observed after the call lasts for a period specified by TCH Time
Handover Period.
– Verifying Flex TSC
1. Use an MS to initiate a call, Tracing CS Domain Messages on the Um Interface,
and record the TSC value in a Assignment Command message.
3. Use an MS to initiate a call again, Tracing CS Domain Messages on the Um
Interface, and record the TSC value in a Assignment Command message.
4. Compare the two TSC values.
Expected result: The two TSC values are different.
– Verifying dummy bit randomization
1. Use an MS to initiate multiple calls, Tracing LAPDm Messages Through BTS
Signaling Trace, and select the TRX carrying the SDCCH on the LAPDm tab.
Then, enter the number of the timeslot or sub-timeslot to be traced.
Expected result: When a call is assigned to the traced SDCCH, the lapdm-rr-frame
information element contained in the MailBox Trace message shows that not all
dummy bits are 2B. This indicates that dummy bits are randomized.
– Verifying the function of stopping sending system information 5, 5bis, or 5ter after
encryption
1. Use an MS to initiate a call, and use a drive test device to trace messages over the
Um interface.
Expected result: SI 5, 5bis, and 5ter is not found in Um interface messages over
the SACCH on the SDCCH after the BTS sends a Ciphering Mode Command
message to the MS.
– Verifying the randomization of the filling information of SI 6
1. Use an MS to initiate a call, and use a drive test device to trace messages over the
Um interface.
Expected result: The tail filling bit of SI 6 in Um messages is not 2B. This indicates
the filling information of SI 6 is randomized.
– Deactivating SDCCH fast handover
Cell Parameters in Batches) with SD Quick HO set to OFF(Off).
– Deactivating TCH scheduled handover
Cell Parameters in Batches) with TCH Time Handover Switch set to OFF(Off).
– Deactivating Flex TSC

GBSS14.0
Cell Parameters in Batches) with Flex TSC Switch set to OFF(Off).
– Deactivating dummy bit randomization
Cell Parameters in Batches) with Dummy Bit Randomization Switch set to OFF
(Off).
– Deactivating the function of stopping sending system information 5, 5bis, or 5ter after
encryption
Cell Parameters in Batches) with Stop Send SI 5/5bis/5ter after Encrypt set to OFF
(Off).
– Deactivating the randomization of the filling information of SI 6
Cell Parameters in Batches) with SI 6 Filling Random Bits After Cipher set to NO
(No).
----End
Example
/*Activating A5/1 Encryption Flow Optimization*/
//Activating SDCCH fast handover
SET GCELLHOBASIC: IDTYPE=BYID, CELLID=0, SIGCHANHOEN=YES;
SET GCELLSOFT: IDTYPE=BYID, CELLID=0, SDFASTHOSWITCH=ON;
//Activating TCH scheduled handover
SET GCELLHOBASIC: IDTYPE=BYID, CELLID=0, INTRACELLHOEN=YES;
SET GCELLSOFT: IDTYPE=BYID, CELLID=0, TCHTIMEHOSWITCH=ON,
TCHTIMEHOPERIOD=60;
//Activating Flex TSC
SET GCELLSOFT: IDTYPE=BYID, CELLID=0, FLEXTSCSWITCH=ON;
//Activating dummy bit randomization
SET GCELLSOFT: IDTYPE=BYID, CELLID=0, DUMMYBITRANDSWITCH=ON;
//Activating the function of stopping sending system information 5, 5bis,
or 5ter after encryption
SET GCELLSOFT: IDTYPE=BYID, CELLID=0, STOPSI5SWITCH=ON;
//Activating the randomization of the filling information of SI 6
SET GCELLSOFT: IDTYPE=BYID, CELLID=0, SI6RandomBit=YES;
/*Deactivating A5/1 Encryption Flow Optimization*/
//Deactivating SDCCH fast handover
SET GCELLSOFT: IDTYPE=BYID, CELLID=0, SDFASTHOSWITCH=OFF;
//Deactivating TCH scheduled handover
SET GCELLSOFT: IDTYPE=BYID, CELLID=0, TCHTIMEHOSWITCH=OFF;
//Deactivating Flex TSC
SET GCELLSOFT: IDTYPE=BYID, CELLID=0, FLEXTSCSWITCH=OFF;
//Deactivating dummy bit randomization
SET GCELLSOFT: IDTYPE=BYID, CELLID=0, DUMMYBITRANDSWITCH=OFF;
//Deactivating the function of stopping sending system information 5,
5bis, or 5ter after encryption
SET GCELLSOFT: IDTYPE=BYID, CELLID=0, STOPSI5SWITCH=OFF;

GBSS14.0
//Deactivating the randomization of the filling information of SI 6

SET GCELLSOFT: IDTYPE=BYID, CELLID=0, SI6RandomBit=NO;

GBSS14.0
Feature Activation Guide 234 Configuring BTS Integrated IPsec
234 Configuring BTS Integrated IPsec
BTS Integrated IPsec. (This feature cannot be configured using the CME. )
Prerequisites
l Dependencies on other Features
– This feature and the GBFD-117702 BTS Local Switch feature are mutually exclusive.
– It is recommended that this feature be used together with the GBFD-113526 BTS
Supporting PKI feature.
l License
– The multi-core UTRPc board is required.
– BTS3900 series (excluding BTS3900B and BTS3900E) support this feature.
– The Abis interface uses the IP over FE/GE transmission mode.
– None
Context
This feature encrypts the transmission data between the BTS and the BSC to ensure the privacy,
integrity, anti-replay capability of the transmission data. (IPSec on the BSC side is configured
through the external security gateway.)
Data Preparation

GBSS14.0
Parameter Parameter ID Remarks Data

Name Source
Local Name IKELNM Set this parameter to be consistent Network

with that on the peer end. planning
Peer end
negotiation
Keepalive IKEKLI - Network

Interval planning
Keepalive IKEKLT
Timeout
NAT NATKLI
Keepalive
Timeout
DSCP DSCP
ACL ID ACLID
Description ACLDESC
Rule Type RULETYPE
Rule ID RULEID
Action ACTION
Protocol Type PT
Source IP SIP
Address
Source SWC
Wildcard
Match Source SMPT

Port
Source Port SOP

Operate
Source Port 1 SPT1
Source Port 2 SPT2
Destination IP DIP
Address
Destination DWC
Wildcard
Match DMPT
Destination
Port

GBSS14.0

Name Source
Destination DOP
Port Operate
Destination DPT1
Port 1
Destination DPT2
Port 2
Match DSCP MDSCP
Differentiated DSCP
Services Code
Point
Match MFRG
Fragment
Message
VLAN ID VLANIDOP
Filter Criteria
VLAN ID 1 VLANID1
VLAN ID 2 VLANID2
Proposal ID PROPID
Encryption ENCALG Set this parameter to be consistent Network

Algorithm with that on the peer end. planning
Peer end
Authentication AUTHALG
negotiation
Algorithm
Authentication AUTHMETH - Network

Method planning
Diffie- DHGRP Set this parameter to be consistent Network

Hellman Group with that on the peer end. planning
Peer end
negotiation
PRF Algorithm PRFALG You are advised to use the default Network
value. planning
ISAKMP SA DURATION Set this parameter to be consistent Network

Duration with that on the peer end. planning
Peer end
negotiation
IKE Peer Name PEERNAME - Network

planning

GBSS14.0

Name Source
Version IKEVERSION Set this parameter to be consistent Network

Exchange EXCHMODE
Peer end
Mode
negotiation
Local ID Type LOCALIDTYPE - Network

planning
Remote IP REMOTEIP
Address
Remote Name REMOTENAME Set this parameter to be consistent Network

Pre-shared Key PKEY
Peer end
negotiation
DPD Mode DPD The dead peer detection (DPD) is Network

enabled by default. It is recommended planning
DPD Idle Time DPDIDLETIME that DPD-related parameters be set to
DPD DPDRETRI consistent values on the two ends of
Retransmissio the Internet Key Exchange (IKE).
n Interval Otherwise, the end with a shorter
timer interval first detects that its peer
DPD DPDRETRN end becomes ineffective and triggers
Retransmissio IKE negotiation again.
n Count
NAT Traversal NATTRAV - Network

planning
Local IP LOCALIP
Address
Pre-shared Key PKEY
IPSec Proposal PROPNAME

Name
Encapsulation ENCAPMODE You are advised to use the tunnel Network

Mode mode. planning
Set this parameter to be consistent Peer end
with that on the peer end. negotiation
Transform TRANMODE Set this parameter to be consistent

with that on the peer end.
AH AHAUTHALG
Authentication
Algorithm
ESP ESPAUTHALG
Authentication
Algorithm

GBSS14.0

Name Source
ESP ESPENCALG
Encryption
Algorithm
Policy Group SPGN - Network

Name planning
IPSec SPSN
Sequence No.
Perfect PFS Set this parameter to be consistent Network

Forward with that on the peer end. planning
Secrecy Peer end
negotiation
SA Duration LTCFG - Network

Mode planning
Lifetime Based LTS

On Time
Lifetime Based LTKB

On Traffic
Anti-Replay REPLAYWND
Window
Cabinet No. CN
Subrack No. SRN
Slot No. SN
Port Type PT
Port No. PN
Policy Group SPGN

Name
Master Policy MSPGN

Group Name
Master IPSec MSPSN

Sequence No.
Slave Policy SSPGN

Group Name
Slave IPSec SSPSN

Sequence No.
BFD Session MBFDSN

ID of Master
Tunnel

GBSS14.0

Name Source
BFD Session SBFDSN

ID of Slave
Tunnel
BFD Session BFDSN

No.
Source IP SRCIP
Address
Destination IP DSTIP
Address
Hop Type HT
Time for BTSWTR

Waiting to
Restore
Minimum TX MINTXINTERVA
Interval L
Minimum RX MINRXINTERV
Interval AL
Detect Period DETECTMULT
DSCP DSCP
Procedure
To configure active and standby IPSec tunnels, perform Step 1 to Step 12. Otherwise,
perform Step 1 to Step 9.
1. Optional: Run the BSC6900 MML command SET BTSIKECFG to set IKE local
configurations.
2. Run the BSC6900 MML command ADD BTSACL to add an access control list
(ACL).
3. Run the BSC6900 MML command ADD BTSACLRULE to add access rules in the
ACL.
4. Run the BSC6900 MML command ADD BTSIKEPROPOSAL to configure IKE
security proposals.
5. Run the BSC6900 MML command ADD BTSIKEPEER to add an IKE peer.
6. Run the BSC6900 MML command ADD BTSIPSECPROPOSAL to add IPSec
security proposals.
7. Run the BSC6900 MML command ADD BTSIPSECPOLICY to add IPSec security
policies.

GBSS14.0
8. Run the BSC6900 MML command ADD BTSIPSECBIND to bind the IPSec security
policy to the output port to validate the security policy.
9. Optional: When the BTS uses an IP clock, the clock server is in a non-security domain,
and Clock Topology Mode is set to PTPOVERUDP, Run the BSC6900 MML
command SET BTSIPCLKPARA. In this step, set Clock Protocol Type to PTP
(PTP Protocol), Clock Topology Mode to PTPOVERUDP(PTP over UDP
Unicast), and Client IP Address to the IP address used for the communication
between the BTS and the clock server.
10. Optional: Repeat Step 1 to Step 9 to configure the second IPSec tunnel.
11. Optional: Run the BSC6900 MML command ADD BTSBFD to configure a
Bidirectional Forwarding Detection (BFD) session for the two IPSec tunnels
respectively.
12. Optional: Run the BSC6900 MML command ADD BTSIPSECDTNL to configure
the active/standby relationship between the two IPSec tunnels.
If the active and standby IPSec tunnels have been configured, perform Step 1 to Step 3.
Otherwise, perform Step 1 and Step 2.
1. Run the BSC6900 MML command DSP BTSIPSECSA to check the IPSec tunnel
status.
Expected result: The results contain IPSec security association (SA) data, indicating
that the IPSec tunnels are set up.
2. Run the BSC6900 MML command LST BTSACLRULE to determine whether
service data is protected by the IPSec as planned by checking ACL rules and check
whether the protected services are normal. For example, if speech services are
protected by the IPSec, you can check whether the speech services are normal by
initiating calls. If management packets are protected by the IPSec, you can check
whether the corresponding BTS is online from the topology window on the M2000.
Expected result: Service data is protected by the IPSec as planned and the protected
services are normal.
3. Remove the Ethernet cable connecting to the active channel, and Run the BSC6900
MML command DSP BTSIPSECDTNL to check whether Current Used IPSec
Policy is Slave IPSec Policy. Use an MS to initiate a call and observe whether the
call is normal. Check whether the corresponding BTS is online from the topology
window on the M2000.
Expected result: Current Used IPSec Policy is Slave IPSec Policy, the call initiated
by the MS is normal, and the corresponding BTS is online.
1. Run the BSC6900 MML command RMV BTSIPSECBIND to delete the binding
relationship between the IPSec security policy and the corresponding port.
----End
Example
The following descriptions assume that the BTS is in IP over FE transmission mode.
//Setting BTS IKE basic configurations
SET BTSIKECFG: IDTYPE=BYID, BTSID=0, IKELNM="IKECFG1", IKEKLI=20,
IKEKLT=60, NATKLI=20, DSCP=48;

GBSS14.0
//Adding a BTS ACL

created";
//Adding BTS IKE security proposals
ADD BTSIKEPROPOSAL: IDTYPE=BYID, BTSID=0, PROPID=10, AUTHALG=MD5,
DURATION=86400;
//Adding a BTS IKE peer
ADD BTSIKEPEER: IDTYPE=BYID, BTSID=0, PEERNAME="ike", PROPID=10,
IKEVERSION=IKE_V1, EXCHMODE=MAIN, LOCALIDTYPE=IP, REMOTEIP="2.2.2.2",
PKEY="*****", DPD=PERIODIC, DPDIDLETIME=20, DPDRETRI=4, DPDRETRN=6,
LOCALIP="1.1.1.1";
//Adding BTS IPSec security proposals
ADD BTSIPSECPROPOSAL: IDTYPE=BYID, BTSID=0, PROPNAME="prop1",
ENCAPMODE=TUNNEL, TRANMODE=ESP, ESPAUTHALG=MD5, ESPENCALG=DES;
//Adding BTS IPSec security policies
ADD BTSIPSECPOLICY: IDTYPE=BYID, BTSID=0, SPGN="policy", SPSN=1,
ACLID=3001, PROPNAME="prop1", PEERNAME="ike", LTCFG=LOCAL;
//Binding a BTS IPSec policy group to a port
ADD BTSIPSECBIND: IDTYPE=BYID, BTSID=0, CN=0, SRN=0, SN=4, PT=ETH, PN=0,
SPGN="policy";
SPGN=" PolicyGroup1";
//Adding a BFD session on the BTS side
ADD BTSBFD: IDTYPE=BYID, BTSID=0, BFDSN=1, SRCIP="1.1.1.1",
DSTIP="2.2.2.2", HT=SBFD, MINTXINTERVAL=100, MINRXINTERVAL=100;
//Adding IPSec dual channels
ADD BTSIPSECDTNL: IDTYPE=BYID, BTSID=0, DUALID=0, MSPGN="policy",
MSPSN=1, SSPGN="PolicyGroup1", SSPSN=1, MBFDSN=1, SBFDSN=2;
//Querying the BTS IPSec SA status
DSP BTSIPSECSA: IDTYPE=BYID, BTSID=0, CN=0, SRN=0, SN=4, SPGN="policy",
SPSN=1;
//Querying the configuration information about the rules in the BTS ACL
LST BTSACLRULE: IDTYPE=BYID, BTSID=0, RULETYPE=ADV, LSTFORMAT=VERTICAL;
//Querying the status of the IPSec dual channels
DSP BTSIPSECDTNL: IDTYPE=BYID, BTSID=0, DUALID=0;
//Deleting the binding relationship between the IPSec security policy
group the corresponding port
RMV BTSIPSECBIND: IDTYPE=BYID, BTSID=0, CN=0, SRN=0, SN=4, PT=ETH, PN=0;

GBSS14.0
Feature Activation Guide 235 Configuring BTS Supporting PKI
235 Configuring BTS Supporting PKI
The BTS Supporting PKI feature enables an NE to automatically obtain a digital certificate
authorized by the Certificate Authority (CA) of an operator. With the digital certificate, the NE
can pass the authentication that uses the Internet Protocol Security (IPsec), 802.1x, or Secure
Socket Layer (SSL) protocol. This feature contains a suite of functions based on Certificate
Management Protocol version 2 (CMPv2) for certificate management between NEs. CMPv2
provides functions such as certificate register request, key update, key restore, certificate
revocation, CA key update notification, certificate authorization notification, and certificate
revocation notification. This section describes how to activate, verify, and deactivate the optional
feature GBFD-113526 BTS Supporting PKI. (This feature cannot be configured using the
CME. )
Prerequisites
l Dependencies on other Features
– It is recommended that this feature be used together with the GBFD-113524 BTS
Integrated IPsec feature.
l License
– The UTRPc board is required.
– DBS3900, BTS3900, BTS3900A, BTS3900L, and BTS3900AL support this feature.
– The Abis interface uses the IP over FE/GE transmission mode.
– Certificate services are provided by third-party CA servers.
Context
l Data Preparation

GBSS14.0
Parameter Name Parameter ID Remarks Data Source

(Configuration
Scenarios)
Certification deploy DEPLOYTYPE Do not set Certification Network planning

position type deploy position type to
NULL.
Certificate Authority CANAME This parameter specifies Network planning

Name the name of the certificate
issuing authority.
Certificate Authority URL l This parameter Network planning

URL specifies the uniform
resource location
(URL) address of the
certificate issuing
authority. The value of
this parameter cannot
contain spaces.
l The URL address must
start with http:// or
https://.
l The URL address must
be a valid IPv4 address.
l The number of a
specified port must be
range from 1 to 65535.
File Name FILENAME This parameter specifies Network planning

the name of BTS
certificate request files.
FTP Server IP IP This parameter specifies Network planning

the IP address of an FTP
server.
Source File Name SRCF This parameter specifies Network planning

the name of source files for
downloaded or uploaded
certificate files (excluding
path names).
Destination File Name DSTF This parameter specifies Network planning

the name of target files for
downloaded or uploaded
certificate files (excluding
path names).

GBSS14.0
Parameter Name Parameter ID Remarks Data Source

(Configuration
Scenarios)
Certificate File Name CERTNAME This parameter specifies Network planning

the file name of trust
certificates or certificate
chains. The file name must
not contain the following
characters: \, /, :, *, ?, ", <,
>, or |.
Application Type APPTYPE This parameter specifies Network planning

the application types of
device certificates. Device
certificates are classified
into Internet Key
Exchange (IKE) and SSL.
The GSM system can be
configured only with the
IKE.
Procedure
1. Run the BSC6900 MML command SET BTSCERTDEPLOY to set the deployment
position of BTS certificates. In this step, set Certification deploy position type to
SPECIFIC, and set Cabinet No., Subrack No., and Slot No. for the UTRPc to
appropriate values.
2. Run the BSC6900 MML command ADD BTSCA to add a certificate issuing
authority. In this step, set Certificate Authority Name and Certificate Authority
URL based on your individual needs.
3. Run the BSC6900 MML command MOD BTSCERTREQ to modify the contents of
BTS certificate request files.
4. Run the BSC6900 MML command CRE BTSCERTREQFILE to create a BTS
certificate request file.
5. Run the BSC6900 MML command ULD BTSCERTFILE to upload the BTS digital
certificate file to the CA server.
6. Send the BTS digital certificate file to the CA administrator through Emails or storage
devices. Then, the CA administrator sends a request to the CA for issuing device
certificates.
7. Run the BSC6900 MML command DLD BTSCERTFILE to download a BTS digital
certificate file.
8. Run the BSC6900 MML command ADD BTSTRUSTCERT to add a BTS trust
certificate.
9. Run the BSC6900 MML command ADD BTSCERTMK to add a BTS device
certificate.

GBSS14.0
10. Run the BSC6900 MML command MOD BTSAPPCERT to modify the in-use BTS
device certificate.
1. Run the BSC6900 MML command TST BTSAPPCERT to perform an IPSec
connection attempt using the device certificate. Check the reported result on the
M2000.
Expected result: The command is executed successfully.

1. Run the BSC6900 MML command RMV BTSCERTMK to delete the mapping
between BTS certificate files.
2. Run the BSC6900 MML command SET BTSCERTDEPLOY with Certification
deploy position type set to NULL.
----End
Example
//Setting the BTS certification deployment position
SET BTSCERTDEPLOY: IDTYPE=BYID, BTSID=0, DEPLOYTYPE=SPECIFIC, CN=0,
SRN=0, SN=4;
//Adding a BTS certificate issuing authority and setting the
authentication mode for the SSL to be the same as that for the CA:
ADD BTSCA: IDTYPE=BYID, BTSID=0, CANAME="Certificate Authority",
URL="http://192.168.119.156:80/pkix/";
//Modifying the contents of the BTS certificate request file
MOD BTSCERTREQ: IDTYPE=BYID, BTSID=0, COMMNAME=ESN,
USERADDINFO="huawei.com", COUNTRY="cn", ORG="ITEF", ORGUNIT="hw",
STATEPROVINCENAME="sc", LOCALITY="cd", SIGNALG=SHA1, KEYSIZE=KEYSIZE1024;
//Creating a BTS certificate request file
CRE BTSCERTREQFILE: IDTYPE=BYID, BTSID=0, FILENAME="PKI.cer";
//Uploading the BTS digital certificate file to the CA server
ULD BTSCERTFILE: IDTYPE=BYID, BTSID=0, IP="10.145.17.100",
SRCF="PKI.cer", DSTF="SSL.cer";
//Downloading a BTS root CA certificate
DLD BTSCERTFILE: IDTYPE=BYID, BTSID=0, IP="10.145.17.100",
SRCF="rootcert.pem", DSTF="rootcert.pem ";
//Downloading a BTS device certificate
DLD BTSCERTFILE: IDTYPE=BYID, BTSID=0, IP="10.145.17.100",
SRCF="BTSCert.pem", DSTF="BTSCert.pem";
//Adding a BTS trust certificate
ADD BTSTRUSTCERT: IDTYPE=BYID, BTSID=0, CERTNAME="rootcert.pem";
//Adding a BTS device certificate
ADD BTSCERTMK: IDTYPE=BYID, BTSID=0, APPCERT="BTSCert.pem"
//Modifying the in-use BTS device certificate
MOD BTSAPPCERT: IDTYPE=BYID, BTSID=0, APPTYPE=IKE, APPCERT="BTSCert.pem";
//Performming an IPSec connection attempt using the device certificate
TST BTSAPPCERT: IDTYPE=BYID, BTSID=0, APPTYPE=IKE, APPCERT="ssc",
IKEPEER="ssa";
//Deleting the mapping between BTS certificate files
MOD BTSAPPCERT: IDTYPE=BYID, BTSID=0, APPTYPE=IKE, APPCERT="null";
RMV BTSCERTMK: IDTYPE=BYID, BTSID=0, APPCERT="BTSCert.pem";
//Setting the BTS certification deployment position
SET BTSCERTDEPLOY: IDTYPE=BYID, BTSID=0, DEPLOYTYPE=NULL;

GBSS14.0
Feature Activation Guide 236 Configuring Ring Topology
236 Configuring Ring Topology
Ring Topology.
Prerequisites
– This feature cannot be enabled when a DXX device is used.
– Reverse and forward links can be connected to the same Abis interface board or different
Abis interface boards in the same BM subrack, but cannot be connected to different
subracks.
OML on A-bis Interface, GBFD-118601 Abis over IP, GBFD-118611 Abis IP over E1/
T1, GBFD-113728 OML Backup, and GBFD-116601 Abis Bypass.
– GBFD-117301 Flex Abis cannot be used together with BTS ring topology II.
l License
– BTS ring topology I
– When this feature is simultaneously enabled with Flex Abis, Flex Abis must be
configured on all BTSs, and only a single E1 link can be configured on the forward
and reverse links.
– BTS ring topology II
– Only a single E1 link can be configured on the forward and reverse links.
– HDLC ring topology (only BTS ring topology II is supported)
– Hybrid networking of HDLC and TDM is not supported. Secondary link is not
supported.
– The cabinets of the BTS30 or BTS312 cannot be used in cabinet groups.

GBSS14.0
– The configuration of exclusive timeslots is supported, but the configuration of

monitoring timeslots is not supported.
– Local switching is not supported.
– The conversion of the bearing modes, that is, the conversion from the HDLC ring
topology to the TDM ring topology, is not supported.
– Timeslots cannot be manually allocated.
Context
A ring topology is a special type of chain topology. In a ring topology, BTSs connect to each
other to form a common chain first, and then the lowest-level BTS is connected to the BSC
through a transmission link, thereby forming a ring. If the transmission link is disconnected at
a point of the ring, the topology of BTSs that precede the breakpoint remains unchanged. BTSs
that follow the breakpoint form a new chain in the reverse direction.
Compared with a common chain topology, the ring topology has the following advantage: When
a transmission link is disconnected at a point, the ring automatically breaks into two chains. In
this way, BTSs that precede and follow the breakpoint can work normally, improving system
robustness.
Procedure
1. Run the BSC6900 MML command ADD BTS (CME single configuration: BTS
Topology > Interface Board > ADD BTS; CME batch modification center: not
supported). In this step, set Config Ring (CME: Support Ring Topology) to YES
(Yes).
Data.
3. Configure the transmission data for the base station by referring to TDM/HDLC.
NOTE
In the forward direction, a BTS in a ring connects to an upper-level BTS or BSC through port
0, and it connects to a lower-level BTS or BSC through port 1.
4. Run the BSC6900 MML command SET BTSRINGATTR (CME single
configuration: BTS Configuration Express > BTS Transmission Link > Ring
Attribues; CME batch modification center: not supported) to configure the attributes
of the ring.
– To enable BTS ring topology I, set Configure Ring II to NO(No), and set Ring
I Wait Time Before Switch and Ring I Try Rotating Duration Time based on
your individual needs.
– To enable BTS ring topology II, set Configure Ring II to YES(Yes), and set Ring
II Wait Time Before Switch, Ring II Try Rotating Duration Time, Ring II
Rotating Penalty Time, T200, T203, andN200 based on your individual needs.
Data.
6. Activate the base station configuration by referring to Activating the BTS
Configuration.
1. Run the BSC6900 MML command DSP BTSRINGPARA.

GBSS14.0
Expected result: The parameter settings in the query results are consistent with the
configured values.
2. Run the BSC6900 MML command MOD BTS (CME single configuration: BTS
Configuration Express > BTS Basic Attributes > BTS; CME batch modification
center: not supported). In this step, set Config Ring (CME: Support Ring
Topology) to NO(No).
3. Run the BSC6900 MML command RMV BTSCONNECT (CME single
Chain; CME batch modification center: not supported) to remove a reverse ring
connection.
----End
Example
//Activating Ring Topology
ADD BTS: BTSID=0, BTSNAME="3900", BTSTYPE=BTS3900_GSM,
SEPERATEMODE=SUPPORT, SERVICEMODE=TDM, ISCONFIGEDRING=YES,
SRANMODE=SUPPORT;
ADD BTSCONNECT: IDTYPE=BYID, BTSID=0, INPN=0, INCN=0, INSRN=0, INSN=6,
DESTNODE=BSC, SRN=0, SN=14, PN=0;
SET BTSRINGATTR: IDTYPE=BYID, BTSID=0, FASTCNETFLAG=YES, BREAKTIME=0,
BUILDTIME=60, ESTTIME=0, T200=12, T203=1, N200=3;
//Verifying Ring Topology
DSP BTSRINGPARA: IDTYPE=BYID, BTSID=0;
//Deactivating Ring Topology
MOD BTS:IDTYPE=BYID, BTSID=0, ISCONFIGEDRING=NO;
RMV BTSCONNECT: IDTYPE=BYID, BTSID=0, INPN=1, INCN=0, INSRN=0, INSN=6;

GBSS14.0
Feature Activation Guide 237 Configuring TRX Cooperation
237 Configuring TRX Cooperation
TRX Cooperation.
Prerequisites
l License
– The cell supports TRX cooperation.
– At least two TRXs in the same band are configured in the cell.
– The cell supports BCCH TRX cooperation.
– The cell supports baseband FH TRX cooperation.
– The cell supports switchback of BCCH TRX cooperation.
– The cell supports switchback of baseband FH TRX cooperation.
Context
TRX cooperation enables the BSC to automatically designate an available TRX in the cell to
replace a faulty BCCH TRX or baseband FH TRX. This ensures that the cell can work properly
when faults occur on some TRXs in the cell. There are two types of TRX cooperation: BCCH
TRX cooperation and baseband FH TRX cooperation.
l BCCH TRX cooperation enables the BSC to use the TRX cooperation algorithm to select
an available TRX as the new BCCH TRX when the original BCCH TRX is faulty. This
ensures that the cell can work properly. When the fault on the original BCCH TRX is
rectified, the BSC can switch the BCCH back to the original TRX.

GBSS14.0
l Baseband FH TRX cooperation enables the BSC to remove a TRX involved in baseband
FH from the FH group when the TRX is faulty in a cell, whereas other TRXs in the FH
group remain in baseband FH.
TRX cooperation is specific to each cell. That is, you can separately enable or disable the TRX
cooperation function for each cell.
Procedure
Parameters in Batches). In this step, set TRX Aiding Function Control to
AllowReImmed(Allowed & Recover Immediately) and Switchback Policy of
Baseband FH Mutual Aid to PART(Part).
Verifying BCCH TRX cooperation and switchback of BCCH TRX cooperation
1. Power off the BCCH TRX for the cell. In this way, the BCCH TRX becomes faulty,
and therefore BCCH TRX cooperation is triggered.
2. Wait for about 15 minutes for cell initialization, and then Run the BSC6900 MML
command DSP CHNSTAT to query the channel status. Verify that Channel Type
of channel 0 of a TRX (not the initially configured BCCH TRX) is set to Main
BCCH.
3. Use an MS to access the cell enabled with the BCCH TRX cooperation function and
make a call. Verify that the call is set up successfully and the voice quality is clear.
4. Power on the TRX mentioned in Step 1 to enable switchback of BCCH TRX
cooperation.
5. Wait about 15 minutes for cell initialization, and then Run the BSC6900 MML
command DSP CHNSTAT to query the channel status. Verify that Channel Type
of channel 0 of the initially configured BCCH TRX is set to Main BCCH.
6. Use an MS to access the cell enabled with the switchback of BCCH TRX cooperation
function and make a call. Verify that the call is set up successfully and the voice quality
is clear.
Verifying baseband FH TRX cooperation and switchback of baseband FH TRX cooperation
set Frequency Hopping Mode to BaseBand_FH(Baseband frequency hopping)
and BCCHTRXHP Frequency Hopping Mode of BCCH TRX to NO_Hop(No
hop).
NOTE
l There are at least two operational TRXs in a baseband FH group to ensure the baseband
FH when a TRX in the same group is faulty.
l Operations such as performing a level-4 reset of a base station, adding a base station after
removing it, activating a base station, and deactivating a base station clear the base station
state recorded at the BSC. As a result, the cell participating in baseband FH TRX
cooperation returns to the initial state.
2. Run the BSC6900 MML command SET GTRXCHANADMSTAT with
Administrative State for the TCH carrying the BCCH set to Lock(Lock).
3. Initiate Abis-interface CS message tracing by referring to Tracing CS Domain
Messages on the Abis Interface. In the Abis Interface CS Trace dialog box, click the

GBSS14.0
OML tab. Then, power off a TRX in the baseband FH group to enable baseband FH
TRX cooperation.
4. Wait 15 minutes, and then check that the IE "arfcnList" in the Set Channel Attributes
message of the faulty TRX contains only one frequency whereas "arfcnList" in the
Set Channel Attributes message of other TRXs in the same baseband FH group
contains multiple frequencies except the frequency of the faulty TRX.
5. Initiate A-interface message tracing by referring to Tracing Messages on the A
Interface. In the A Interface Trace dialog box, click the BSSAP tab, and set related
parameters to start the tracing task. Initiate Abis-interface CS message tracing by
referring to Tracing CS Domain Messages on the Abis Interface. In the Abis Interface
CS Trace dialog box, click the RSL tab, and set related parameters to start the tracing
task. Use an MS to access the test cell and then originate a call. Verify that the voice
is clear during the call and that the messages traced over the Abis and A interfaces are
correct. Ensure that the field h in the IE "hopping-channel" of the ASSIGNMENT
COMMAND message carried in the Data Request message is 1.
6. Power on the TRX mentioned in Step 3 to enable switchback of baseband FH TRX
cooperation.
7. Wait 15 minutes, and then verify that the IE "arfcnList" in the Set Channel Attributes
message of the fault-rectified TRX contains all frequencies in the baseband FH group.
8. Use an MS to access the test cell and then originate a call. Verify that the voice is clear
during the call and that the messages traced over the Abis and A interfaces are correct.
Ensure that h in the IE "hopping-channel" of the ASSIGNMENT COMMAND
message carried in the Data Request message is 1.
Parameters in Batches). In this step, set TRX Aiding Function Control to
TRXAid_NotAllow(TRX Aiding Not Allowed).
----End
Example
//Activating TRX Cooperation
SET GCELLCCACCESS: IDTYPE=BYID, CELLID=1, TRXAIDSWITCH=AllowReImmed,
BHPREPOLICY=PART;
//Verifying TRX Cooperation
Verifying BCCH TRX cooperation and switchback of BCCH TRX cooperation
Verifying baseband FH TRX cooperation and switchback of baseband FH TRX
cooperation
BCCHTRXHP=NO_Hop;
//Deactivating TRX Cooperation
SET GCELLCCACCESS: IDTYPE=BYID, CELLID=1, TRXAIDSWITCH=TRXAid_NotAllow;

GBSS14.0
Feature Activation Guide 238 Configuring MSC Pool
238 Configuring MSC Pool
MSC Pool. (This feature cannot be configured using the CME. )
Prerequisites
l License
– Two MSs are available, and they are registered at the HLR.
– The MSCs and the MGWs are fully interconnected, and the MSC pool function is
configured on the MSC side.
– The interconnection data between the BSC6900 and the MSC is negotiated.
– The M2000 feature WOFD-230100 MSC Pool Management has been enalbed.
– An original signaling point (OSP) and at least two destination signaling points (DSPs)
are configured. For details, see Configuring the OSP and DSP.
– The transmission over the A interface is configured. For details, see Configuring the A
Interface (over TDM) or Configuring the Control Plane of the A Interface (over IP).
Context
An MSC pool consists of multiple MSCs processing traffic from one MSC pool area. A
BSC6900 belonging to an MSC pool area is connected to each MSC in the MSC pool. All MSCs
in the MSC pool share load and resources for equal distribution of traffic in the MSC pool,
reducing inter-MSC handovers and providing disaster-tolerant redundancy capabilities.
This feature enables the BSC to independently initiate the load reassignment function.
One BSC6900 can be connected to a maximum of 32 MSCs.

GBSS14.0
When the MSC does not support the function A Interface Circuits Managed by the MGW or the
function is disabled, DPCs in an MSC pool are configured for different DPC groups.
NOTE
This section uses the configuration of two DSPs whose DPX Index are set to 0 and 1 as an example.
Procedure
1. Run the BSC6900 MML command ADD GCNOPERATOR to add a GSM operator.
In this step, set Operator Type, Operator Index, Operator Name, MCC, and
MNC to appropriate values; set MSC Pool Function Enabled to YES(Yes); and set
Length of NRI in TMSI and MSC NULL-NRI Value based on the data negotiated
with the MSC.
2. Run the BSC6900 MML command ADD GCNNODE to add a CN node for the first
DSP. In this step, set DSP index to 0, set Operator Name to the value set in Step
1, set CN Node Index and DPC Group Index appropriately, and set MSC
Administrable State, MSC ID, and MSC Available Capability<K User
number> based on the data negotiated with the MSC.
3. Run the BSC6900 MML command ADD GCNNODE to add a CN node for the second
DSP. In this step, set DSP index to 1, set Operator Name to the value set in Step
1, set CN Node Index and DPC Group Index appropriately, and set MSC
Administrable State, MSC ID, and MSC Available Capability<K User
number> based on the data negotiated with the MSC.
NOTE
Repeat the BSC6900 MML command ADD GCNNODE if there are more than two DSPs.
4. Run the BSC6900 MML command ADD NRIMSCMAP to add the mapping between
an NRI and an MSC. In this step, set NRI Value based on the data negotiated with
the MSC. Ensure that the NRI value is the same as that on the MSC side.
5. If you need to adjust the number of MSs served by an MSC, run the BSC6900 MML
command MOD GCNNODE with MSC Administrable State set to OFFLOAD
(Offload), Reallocation Proportion set to 100, and Reallocation Duration set to
1. Then, run the BSC6900 MML command STR MSCRSL with CN Node Index set
to an appropriate value to start a BSC load reallocation task on the MSC. Reallocation
Proportion is set according to the proportion of MSs that can be migrated from this
MSC, and Reallocation Duration is set according to the task duration.
1. Enable the TMSI reallocation function on the MSC side.
2. On the LMT, initiate A-interface message tracing by referring to Tracing Messages
on the A Interface. In this step, set Trace Type to BSSAP and DPC(Hex) to the DSP
of MSC 1.
3. On the BSSAP tab page, set Cell ID(cell1,cell2,...cell16) to the ID of the cell where
MS 1 camps on. Then, click Submit. The A Interface Trace message window is
displayed.
NOTE
Initiate A-interface message tracing with the DSP of MSC 2 by using the method described in Step
2 and Step 3.
4. Power on MS 1. Use MS 1 to initiate a location update procedure on the MSC 1 side.
The CN assigns a TMSI to MS 1.

GBSS14.0
5. Power on MS 2. Use MS 2 to initiate a location update procedure on the MSC 2 side.

The CN assigns a TMSI to MS 2.
NOTE
To enable the MS to initiate a location update at a specific MSC, Run the BSC6900 MML
command MOD GCNNODE to set MSC Administrable State for all other MSCs to UNAVAIL
(Unavailable). After the location update, set the parameter to NORMAL(Normal).
6. Move MS 1 to the coverage area of MSC 2. Then, use MS 1 to originate a call and
check the A interface message tracing.
Expected result: MS 1 sets up the call through MSC 1, and the registered MSC of MS
1 remains unchanged.
7. Move MS 2 to the coverage area of MSC 1. Then, use MS 2 to originate a call and
check the A interface message tracing.
Expected result: MS 2 sets up the call through MSC 2, and the registered MSC of MS
2 remains unchanged.
NOTE
In the TMSI reallocation procedure, the MSC assigns the TMSI that contains NRI (configured by
the CN) to the MS. With this information, the BSC6900 can allocate the service to an appropriate
MSC when the MS originates a call service. Note that the mapping between the NRI and the MSC
on the BSC6900 side must be consistent with the mapping between the NRI and the MSC on the
CN side. You can use the BSC6900 MML command ADD NRIMSCMAP to configure the mapping
on the BSC6900 side.
8. If the BSC load reallocation task is started, run the BSC6900 MML command DSP
MSCRSL with CN Node Index set to an appropriate value to query the BSC load
reallocation task status. After the task is started on the MSC, MS 1 initiates the periodic
location update procedure. Check the LA of MS 1 in the A interface message tracing.
Expected result: MS 1 registers with MSC 2, the home MSC for MS 1 changes, and
the load reallocation task is in the started state.
1. Run the BSC6900 MML command MOD GCNOPERATOR. In this step, set MSC
Pool Function Enabled to NO(No).
2. If the BSC load reallocation task is started, run the BSC6900 MML command STP
MSCRSL with CN Node Index set to an appropriate value to stop the task.
----End
Example
/*Activating MSC Pool*/
//Adding a GSM operator and enabling the MSC pool function
ADD GCNOPERATOR: OperatorType=PRIM, OPINDEX=0, OPNAME="op1", MCC="460",
MNC="188",
MSCPOOLALLOW=YES, MSCNRILEN=3, MSCNULLNRI=0, SGSNPOOLALLOW=NO;
//Adding a CN node
ADD GCNNODE: CNNODEIDX=0, DPX=0, DPCGIDX=1, OPNAME="op1", MSCCAP=1800,
CNID=0, DFDPC=YES, ATransMode=TDM;
ADD GCNNODE: CNNODEIDX=1, DPX=0, DPCGIDX=1, OPNAME="op1", MSCCAP=1800,
CNID=1, DFDPC=NO, ATransMode=TDM;
//Adding an NRI-to-MSC mapping
ADD NRIMSCMAP: NRI=10, CNNODEIDX=0;
ADD NRIMSCMAP: NRI=11, CNNODEIDX=1;
//Starting a load reallocation task

GBSS14.0
MOD GCNNODE: CNNODEIDX=0, MSCSTATUE=OFFLOAD, PROPORTION=100, PERIOD=1;

STR MSCRSL: CNNODEIDX=0;
/*Deactivating MSC Pool*/

//Disabling the MSC pool function
MOD GCNOPERATOR: OPINDEX=0, MSCPOOLALLOW=NO;
//Stopping the load reallocation task
STP MSCRSL: CNNODEIDX=0;

GBSS14.0
Feature Activation Guide 239 Configuring the SGSN Pool
239 Configuring the SGSN Pool
About This Chapter
SGSN Pool.
239.1 Configuring SGSN Pool (Gb over IP)

SGSN Pool.
239.2 Configuring SGSN Pool (Gb over FR)
SGSN Pool.

GBSS14.0
239.1 Configuring SGSN Pool (Gb over IP)

SGSN Pool.
Prerequisites
– The DPUd/DPUg/XPUa/XPUb/FG2a/FG2c/FG2d/GOUc/GOUd board is configured.
For details, see Configuring a Board.
– None
l License
– The basic BSC data is configured. For details, see Configuring the Basic Data.
– The communication is normal between the BSC and the SGSN.
– The BSC supports SGSN Pool.
– The P-TMSI allocation function must be enabled on the SGSN side when the SGSN
Pool feature is enabled on the BSC.
– The interface board is configured with a device IP address or port IP address.
Context
SGSN Pool enables multiple SGSNs to form an SGSN pool. The SGSNs in an SGSN pool share
load and resources. Configuring SGSN Pool can expand network capacity, reduce investment
in equipment, implement redundancy, and improve network reliability. In addition, it reduces
the number of inter-SGSN cell reselections, which improves network performance.
Procedure
Allow SGSN Pool to YES(Yes); specify SGSN NRI Length and SGSN NullNRI
Value.
2. Configure the Physical Layer and Data Link Layer for the FG2a/FG2c/FG2d/GOUc/
GOUd Board.
3. Run the BSC6900 MML command SET BSCPCUTYPE (CME single configuration:
GSM Global Configuration Express > Software Parameter Configuration > PCU
Type; CME batch modification center: not supported) to set the type of the packet
control unit (PCU). In this step, set PCU Type to INNER(Built-in PCU).

GBSS14.0
not supported) to add an SGSN node. In this step, set Operator Name and SGSN
Node ID.
5. Run the BSC6900 MML command ADD NRISGSNMAP (CME single
configuration: Gb Configuration Express > SGSN > NRI-SGSN Mapping; CME
batch modification center: not supported) to configure the mapping between the
network resource identifier (NRI) and the SGSN.
Configuration Express > IP Transport > NSE; CME batch modification center: not
supported) to add a network service entity (NSE).
7. Run the BSC6900 MML command ADD NSVLLOCAL (CME single configuration:
Gb Configuration Express > IP Transport > Local NSVL; CME batch modification
center: not supported) to add a network service virtual link (NSVL) on the
BSC6900 side. If the NSE is in static configuration mode, Run the BSC6900 MML
command ADD NSVLREMOTE (CME single configuration: Gb Configuration
Express > IP Transport > Remote NSVL; CME batch modification center: not
supported) to add an NSVL on the SGSN side.
center: not supported). In this step, set NSE Identifier. The mapping between CELL_1
and the first SGSN is complete.
9. Repeat Step 2 through Step 8 to add mapping between CELL_1 and other SGSNs in
the SGSN pool.
1. Run the BSC6900 MML command DSP PTPBVC to query the status of a PTP BSSGP
virtual connection (PTP BVC) and then record it.
2. Trace PTP BVC messages on the Gb interface in CELL_1 by referring to Tracing PTP
messages on the Gb interface, and check the FLOW CONTROL BVC messages sent
from the BSC to the SGSN through all functional PTP BVCs. If these messages are
correct, SGSN Pool is enabled and functional.
3. Ensure that the MS acessses the network in cell 1. Use the MS to perform PS services.
The MS can perform attach, PDP context activation, upload, and download properly.
According to the traced PTP BVC messages on the Gb interface in cell 1, the PS
services are carried on one PTP BVC.
4. Block the PTP BVC carrying services discussed in step 3. Ensure that the MS acessses
the network in cell 1 and use the MS to perform PS services. The MS can perform
attach, PDP context activation, upload, and download properly. According to the
traced PTP BVC messages on the Gb interface in cell 1, the PS services are carried
on another PTP BVC.
center: not supported). In this step, set NSE Identifier and PTP BVC Identifier
corresponding to the current cell to appropriate values.
2. Run the BSC6900 MML command RMV NSVLREMOTE (CME single
configuration: Gb Configuration Express > IP Transport > Remote NSVL; CME
batch modification center: not supported) to remove the remote NSVL.

GBSS14.0
3. Run the BSC6900 MML command RMV NSVLLOCAL (CME single configuration:
Gb Configuration Express > IP Transport > Local NSVL; CME batch modification
center: not supported) to remove the local NSVL.
4. Run the BSC6900 MML command RMV NSE (CME single configuration: Gb
Configuration Express > IP Transport > NSE; CME batch modification center: not
supported) to remove the NSE.
5. Run the BSC6900 MML command RMV NRISGSNMAP (CME single
batch modification center: not supported) to remove the mapping between the NRI
and the SGSN.
6. Run the BSC6900 MML command RMV SGSNNODE (CME single configuration:
not supported) to remove the SGSN node.
Allow SGSN Pool to NO(No).
CAUTION
The BSC allows new MSs to evenly access the SGSNs in an SGSN pool based on the
capacity percentages configured for the SGSNs. The BSC cannot change the distribution
of the existing MSs under the SGSNs in the SGSN pool. After the capacity percentages for
SGSNs are added or modified, or if SGSNs are deleted, MSs under these SGSNs must be
migrated to other SGSNs. This ensures that the MS distribution percentages under the
SGSNs quickly reaches the specified values.
----End
Example
//Enable SGSN Pool and specify SGSN NRI Length and SGSN NullNRI Value:
MOD GCNOPERATOR:OPINDEX=0, OPNAME="abc", SPPRTCB=NOTSPPRTBC,
HOBTWNOTHOPALLOW=NO, MSCPOOLALLOW=NO,
SGSNPOOLALLOW=YES, SGSNNRILEN=4, SGSNNULLNRI=0;
//Configure SGSN Pool (IP transmission mode is used on the Gb

interface):
SET BSCPCUTYPE:TYPE=INNER;
ADD SGSNNODE:OPNAME="abc", CNID=0, SGSNSTATUS=ALLOW, SGSNCAP=1000;
ADD NRISGSNMAP:NRI=8, OPNAME="abc", CNID=0;
ADD NSE:NSEI=23800, SRN=0, OPNAME="abc", PT=GB_OVER_IP, ISNCMODE=DYNAMIC,
SVRIP="131.131.131.134",
SVRPORT=23800, CNID=0, RIMSUP=NO, PFCSUP=NO, SN=0, PSHOSUP=NO;
ADD NSE:NSEI=62380, SRN=0, OPNAME="abc", PT=GB_OVER_IP, ISNCMODE=DYNAMIC,
SVRIP="131.131.131.136",
SVRPORT=62380, CNID=1, RIMSUP=NO, PFCSUP=NO, SN=0, PSHOSUP=NO;
ADD NSVLLOCAL:LOCALNSVLI=238, NSEI=23800, IP="132.134.131.133",
UDPPN=23800, SRN=0, SN=18, SIGLW=100, SRVLW=100;
ADD NSVLLOCAL:LOCALNSVLI=38, NSEI=62380, IP="132.134.131.131",
UDPPN=62380, SRN=0, SN=18, SIGLW=100, SRVLW=100;

GBSS14.0
ADD PTPBVC:NSEI=23800, BVCI=3, IDTYPE=BYID, CELLID=2;

//Query the state of a PTP BVC:
DSP PTPBVC: NSEI=23800, BVCI=3;
//Deactivate SGSN Pool:
RMV NSVLREMOTE: REMOTENSVLI=238;
RMV NSVLREMOTE: REMOTENSVLI=38;
RMV NSVLLOCAL: LOCALNSVLI=238;
RMV NSVLLOCAL: LOCALNSVLI=38;
RMV NSE: NSEI=23800;
RMV NRISGSNMAP: NRI=8, OPNAME="abc";
RMV SGSNNODE: OPNAME="abc", CNID=0;
MOD GCNOPERATOR: OPINDEX=0, SGSNPOOLALLOW=NO;
239.2 Configuring SGSN Pool (Gb over FR)

SGSN Pool.
Prerequisites
– The DPUd/XPUa/PEUa board is configured. For details, see Configuring a Board.
l License
– The basic data of the BSC is configured. For details, see Configuring the Basic Data.
– The communication is normal between the BSC and the SGSN.
– The BSC supports SGSN Pool.
– The P-TMSI allocation function must be enabled on the SGSN side when the SGSN
Pool feature is enabled on the BSC.
Context
The SGSNs in an SGSN pool share load and resources in the pool. Configuring SGSN Pool can
expand network capacity, reduce investment in equipment, implement redundancy, and improve
network reliability. In addition, it reduces the number of inter-SGSN cell reselections, which
improves network performance.
Procedure

GBSS14.0

Allow SGSN Pool to YES(Yes); specify SGSN NRI Length and
SGSNNULLNRI.
2. Run the BSC6900 MML command SET BSCPCUTYPE (CME single configuration:
GSM Global Configuration Express > Software Parameter Configuration > PCU
Type; CME batch modification center: not supported) to set the type of the packet
control unit (PCU). In this step, set PCU Type to INNER(Built-in PCU).
not supported) to add an SGSN node. In this step, set Operator Name and SGSN
Node ID.
4. Run the BSC6900 MML command ADD NRISGSNMAP (CME single
batch modification center: not supported) to configure the mapping between the
network resource identifier (NRI) and the SGSN.
not supported) to add a network service entity (NSE).
6. Run the BSC6900 MML command ADD BC (CME single configuration: Gb
Configuration Express > FR Transport > Bearer Channel; CME batch
modification center: not supported) to add a bearer channel (BC).
7. Run the BSC6900 MML command ADD NSVC (CME single configuration: Gb
Configuration Express > FR Transport > Network Service Virtual Connection;
CME batch modification center: not supported) to add a network service virtual
connection (NSVC).
Configuration Express > FR Transport > PTP BVC; CME batch modification
center: not supported). In this step, set NSE Identifier. The mapping between CELL_1
and the first SGSN is complete.
9. Repeat Step 2 through Step 8 to add mapping between CELL_1 and other SGSNs in
the SGSN pool.
1. Run the BSC6900 MML command DSP PTPBVC to query the status of a PTP BSSGP
virtual connection (PTP BVC) and then record it.
2. Trace PTP BVC messages on the Gb interface in CELL_1 by referring to Tracing PTP
messages on the Gb interface, and check the FLOW CONTROL BVC messages sent
from the BSC to the SGSN through all functional PTP BVCs. If these messages are
correct, SGSN Pool is enabled and functional.
3. Ensure that the MS accesses the network in cell 1. Use the MS to perform PS services.
The MS can perform attach, PDP context activation, upload, and download properly.
According to the traced PTP BVC messages on the Gb interface in cell 1, the PS
services are carried on one PTP BVC.
4. Block the PTP BVC carrying services discussed in step 3. Ensure that the MS accesses
the network in cell 1 and use the MS to perform PS services. The MS can perform
attach, PDP context activation, upload, and download properly. According to the
traced PTP BVC messages on the Gb interface in cell 1, the PS services are carried
on another PTP BVC.

GBSS14.0
Configuration Express > FR Transport > PTP BVC; CME batch modification
center: not supported). In this step, set NSE Identifier and PTP BVC Identifier
corresponding to the current cell to appropriate values.
2. Run the BSC6900 MML command RMV NSVC (CME single configuration: Gb
Configuration Express > FR Transport > Network Service Virtual Connection;
CME batch modification center: not supported) to remove the NSVC.
3. Run the BSC6900 MML command RMV BC (CME single configuration: Gb
Configuration Express > FR Transport > Bearer Channel; CME batch
modification center: not supported) to remove the BC.
4. Run the BSC6900 MML command RMV NSE (CME single configuration: Gb
not supported) to remove the NSE.
5. Run the BSC6900 MML command RMV NRISGSNMAP (CME single
batch modification center: not supported) to remove the mapping between the NRI
and the SGSN.
6. Run the BSC6900 MML command RMV SGSNNODE (CME single configuration:
not supported) to remove the SGSN node.
Allow SGSN Pool to NO(No).
CAUTION
The BSC allows new MSs to evenly access the SGSNs in an SGSN pool based on the
capacity percentages configured for the SGSNs. The BSC cannot change the distribution
of the existing MSs under the SGSNs in the SGSN pool. After the capacity percentages for
SGSNs are added or modified, or if SGSNs are deleted, MSs under these SGSNs must be
migrated to other SGSNs. This ensures that the MS distribution percentages under the
SGSNs quickly reaches the specified values.
----End
Example
//Enable SGSN Pool and specify SGSN NRI Length and SGSN NullNRI Value:
MOD GCNOPERATOR:OPINDEX=0, OPNAME="abc", SPPRTCB=NOTSPPRTBC,
HOBTWNOTHOPALLOW=NO, MSCPOOLALLOW=NO,
SGSNPOOLALLOW=YES, SGSNNRILEN=4, SGSNNULLNRI=0;
//Configure SGSN Pool (FR transmission mode is used on the Gb

interface):
SET BSCPCUTYPE:TYPE=INNER;
ADD NSE: NSEI=134, SRN=0, SN=0, PT=GB_OVER_FR, OPNAME=" abc", CNID=0,

GBSS14.0
RIMSUP=NO, PFCSUP=NO, PSHOSUP=NO;

ADD NSE: NSEI=136, SRN=0, SN=0, PT=GB_OVER_FR, OPNAME=" abc", CNID=1,
RIMSUP=NO, PFCSUP=NO, PSHOSUP=NO;
ADD BC: SRN=0, SN=26, PN=24,BCID=0,
TS=TS1-1&TS2-1&TS3-1&TS4-1&TS5-1&TS6-1&TS7-1&TS8-1&TS9-1&TS10-1&TS11-1&TS
12-1&TS13-1&TS14-1&TS15-1&TS16-1
&
TS17-1&TS18-1&TS19-1&TS20-1&TS21-1&TS22-1&TS23-1&TS24-1&TS25-1&TS26-1&TS2
7-1&TS28-1&TS29-1&TS30-1&TS31-1;
ADD BC: SRN=0, SN=26, PN=25, BCID=1,
TS=TS1-1&TS2-1&TS3-1&TS4-1&TS5-1&TS6-1&TS7-1&TS8-1&TS9-1&TS10-1&TS11-1
&
TS12-1&TS13-1&TS14-1&TS15-1&TS16-1&TS17-1&TS18-1&TS19-1&TS20-1&TS21-1&TS2
2-1&TS23-1&TS24-1&TS25-1&TS26-1&TS27-1
&TS28-1&TS29-1&TS30-1&TS31-1;
ADD NSVC: NSVCIDX=0, NSVCI=134, NSEI=134, SRN=0, SN=26, BCID=0, DLCI=16;
ADD NSVC: NSVCIDX=1, NSVCI=136, NSEI=136, SRN=0, SN=26, BCID=1, DLCI=17;
//Query the state of a PTP BVC:
//Deactivate SGSN Pool:
RMV NSVC: NSVCIDX=0;
RMV NSVC: NSVCIDX=1;
RMV BC: SRN=0, SN=26, BCID=0;
RMV BC: SRN=0, SN=26, BCID=1;
MOD GCNOPERATOR: OPINDEX=0, SGSNPOOLALLOW=NO;

GBSS14.0
Feature Activation Guide 240 Configuring Abis Bypass
Abis Bypass.
Prerequisites
– The BTS3006C and BTS3002E in TDM transmission mode are configured with the
DMCM board that supports Abis Bypass.
– The BTS3012 (DTRU/QTRU) and BTS3012AE (DTRU/QTRU) in TDM transmission
mode are configured with the DABB board that supports Abis Bypass.
OML on A-bis Interface, GBFD-118601 Abis over IP, GBFD-118401 Abis
Transmission Optimization, GBFD-117702 BTS Local Switch, GBFD-117801 Ring
Topology, or GBFD-117301 Flex Abis.
l License
l Others
– The physical transmission link is connected to the GTMU.
– In Abis IP over E1 transmission mode, the BTS uses the logical IP address for
communication.
– In Abis IP over E1 transmission mode, the local and peer IP addresses for the PPP links
or MLPPP link groups over the port connecting the BTS and the BSC or connecting the
BTS and the upper-level BTSs must be set to 0.0.0.0, as shown in Figure 240-1.

GBSS14.0
Figure 240-1 IP address planned for links in IP over E1 transmission mode
Context
Abis bypass is applicable to GBSS chain topologies. When power supply to a BTS fails, this
function makes the BTS bypassed to function only as the path so that signals of lower-level
BTSs can be transmitted to the BSC6900. After power supply is restored, the BTS and lower-
level BTSs in the chain topology automatically reset and restore.
To enable the Abis bypass function for cascaded BTSs, you only need to set Abis ByPass
Mode to TRUE(Support) for each cascaded BTS.
A maximum of five levels of cascaded BTSs support Abis bypass.
For BTS3900 series, this function is effective only after DIP switches are set properly.
l When the Abis interface uses the TDM transmission mode, DIP switches S4 and S5 are
required for supporting this function.
l When the Abis interface uses the IP over E1 transmission mode, only DIP switch S4 is
required for supporting this function.
Table 240-1 and Table 240-2 describe the bits of DIP switches.
Table 240-1 Meanings of bits on DIP switch S4
DIP Switch Bit Status of S4 Remarks
BIT1 BIT2 BIT3 BIT4
S4 ON ON ON ON Abis Bypass
is supported.
OFF OFF OFF OFF Abis bypass

is not
supported.
Other Prerequisites Unavailable

GBSS14.0
Table 240-2 Meanings of bits on DIP switch S5

DIP Switch Bit Status of S5 Remarks
BIT1 BIT2 BIT3 BIT4
S5 ON ON ON ON Abis bypass
is not
supported.
OFF ON ON OFF The first-

level BTSs
support Abis
bypass.
ON OFF ON OFF The second-

level BTSs
support Abis
bypass.
OFF OFF ON OFF The third-

level BTSs
support Abis
bypass.
ON ON OFF OFF The fourth-

level BTSs
support Abis
bypass.
OFF ON OFF OFF The fifth-

level BTSs
support Abis
bypass.
Others Unavailable
Assuming that the Abis Bypass function is activated when the Abis interface uses the IP over
E1 transmission mode:
l When an upper-level BTS experiences a power failure, call drops or mute occur in lower-
level BTSs and last for approximate 5s. As shown in Figure 240-1, when BTS1 is powered
off, the PPP or MP link between BTS1 and BTS2 is interrupted. BTS2 renegotiates with
the BSC about reestablishing a PPP or an MP link. After the negotiation is complete and
OML is reestablished, the services in the lower-level BTSs recover.
l When the upper-level BTS is powered on again, the services in lower-level BTSs are
interrupted. As shown in Figure 240-1, when BTS1 is powered on again, the PPP or MP
link between BTS2 and BSC is interrupted. BTS2 renegotiates with BTS1 about
reestablishing a PPP or an MP link. After the negotiation is complete and OML is
reestablished, the services in the lower-level BTSs recover. The laboratory test data shows

GBSS14.0
that the adjacent lower-level BTS is affected for 4 to 15 minutes. The impact duration
increases by 1 or 2 minutes for a BTS of a higher level.
Procedure
supported) to add an upper-level BTS. In this step, set Abis ByPass Mode to TRUE
(Support).
Topology > Right click BTS > ADD Site; CME batch modification center: not
supported) to add a lower-level BTS. In this step, set Abis ByPass Mode to TRUE
(Support).
Chain; CME batch modification center: not supported) to add a connection for the
lower-level BTS. Repeat this step for each cascaded BTS you want to add, including:
– Set Dest Node Type (select Connect to BSC on the CME) to BTS.
– Set Dest Father BTS Port No. to the number of the port that connects the lower-
level BTS to the upper-level BTS.
NOTE
A BTS connects to an upper-level BTS or BSC through port 0, and it connects to a lower-level
BTS through port 2.
4. In Abis IP over E1 transmission mode, if the type of links carried on the E1/T1 link
is PPP:
– Run the BSC6900 MML command ADD PPPLNK (CME single configuration:
A Configuration Express > IP Transport > PPP Link; CME batch modification
center: not supported) command to add PPP links.
– Run the BSC6900 MML command ADD BTSPPPLNK (CME single
PPP Link; CME batch modification center: not supported) command to add BTS
PPP links.
NOTE
Local IP Address and Peer IP address for PPP links over the port connecting the BTS and
the BSC or connecting the BTS and the upper-level BTSs must be set to 0.0.0.0.
5. In Abis IP over E1 transmission mode, if the type of links carried on the E1/T1 link
is MLPPP link group:
– Run the BSC6900 MML command ADD MPGRP (CME single configuration: A
modification center: not supported) command to add MLPPP link groups.
– Run the BSC6900 MML command ADD MPLNK (CME single configuration:
A Configuration Express > IP Transport > MP Group > MP Link; CME batch
modification center: not supported) command to add MLPPP links.
– Run the BSC6900 MML command ADD BTSMPGRP (CME single
MP Group; CME batch modification center: not supported) command to add BTS
MLPPP link groups.

GBSS14.0
NOTE
Local IP Address and Peer IP Address for MLPPP link groups over the port connecting the
BTS and the BSC or connecting the BTS and the upper-level BTSs must be set to 0.0.0.0.
– Run the BSC6900 MML command ADD BTSMPLNK (CME single
configuration: BTS IP Configuration Express > BTS IP Transmission > BTS
MLPPP Link; CME batch modification center: not supported) command to add
BTS PPP links.
1. Power off the upper-level BTS.
2. On the LMT, click Device Maintenance and enter the lower-level BTS maintenance
page. Select a BTS that is configured with GPS clock synchronization. Then, right-
click the GTMU board and choose Query Board Information from the shortcut
menu. In the displayed dialog box, click Basic Information. If basic information
about the GTMU board is displayed and the OML Faulty message is not displayed,
the Abis bypass function has been enabled.
1. Run the BSC6900 MML command MOD BTS (CME single configuration: Main
View > Right click BTS > Modify Abis Bypass Attribute; CME batch modification
center: not supported). In this step, set Abis ByPass Mode to FALSE(Not
Support).
NOTE
Before performing this step, run the MML command DEA BTS (CME single configuration:
Main View > Right click BTS > Deactivate BTS; CME batch modification center: not
supported) to deactivate the BTS if it has been activated.
----End
Example
//The following uses the Abis over TDM transmission mode as an example.
//Activating Abis Bypass
ADD BTS: BTSID=0, BTSNAME="3900", BTSTYPE=BTS3900_GSM,
SEPERATEMODE=SUPPORT, SERVICEMODE=TDM, ABISBYPASSMODE=TRUE,
SRANMODE=SUPPORT;
ADD BTS: BTSID=1, BTSNAME="3900-1", BTSTYPE=BTS3900_GSM,
SEPERATEMODE=SUPPORT, SERVICEMODE=TDM, ABISBYPASSMODE=TRUE,
SRANMODE=SUPPORT;
ADD BTSCONNECT: IDTYPE=BYID, BTSID=1, INPN=0, DESTNODE=BTS,
UPBTSIDTYPE=BYID, UPBTSID=0, FPN=2;
//Deactivating Abis Bypass
MOD BTS: IDTYPE=BYID, BTSID=0, ABISBYPASSMODE=FALSE;

GBSS14.0
Feature Activation Guide 241 Configuring Robust Air Interface Signalling
241 Configuring Robust Air Interface

Signalling
Robust Air Interface Signalling.
Prerequisites
– Since GBSS12.0, the following RF modules support Repeated SACCH: RRU3004,
DRFU, RRU3008 V1, RRU3008 V2, RRU3908 V1, RRU3908 V2, MRFU V1, MRFU
V2
– Since GBSS13.0, the following RF modules support Repeated SACCH: RRU3926,
RRU3929, RRU3942, MRFUe, MRFUd, and RRU3928
– Since GBSS13.0, the following BTSs support Repeated SACCH: BTS3900B,
BTS3900E, BTS3012, BTS3006C, and BTS3002E configured with DTRUs or DDRMs
– BTS312 do not support Repeated SACCH.
– BTS3012 and BTS3012AE that are configured with QTRUs do not support Repeated
SACCH.
– Except BTS312, BTS3012 configured with QTRUs, and BTS3012AE configured with
QTRUs, all BTSs (including BTS3900B and BTS3900E) and RF modules support
Repeated Downlink FACCH.
l License
– Repeated Downlink FACCH does not require support from MSs. Repeated SACCH
requires the support from R6 MSs.

GBSS14.0
Context
When the radio quality is poor, by retransmitting FACCH or SACCH frames, the anti-
interference capability of the FACCH or SACCH is improved, thereby increasing the possibility
that the MS and BSC receive signaling messages successfully.
The robust air interface signaling function includes retransmission of downlink FACCH frames
and retransmission of uplink/downlink SACCH frames.
Procedure
Parameters in Batches). In this step, set ECSC to YES(Yes), Repeated Downlink
FACCH to YES(Yes) , Repeated Downlink FACCH Threshold to 5, and Repeated
SACCH to YES(Yes).
1. Verify Repeated Downlink FACCH.
Measure the value of the S4233A:Number of Retransmitted Downlink FACCH
Frames counter for all transceivers (TRXs) in the cell with the Robust Air Interface
Signalling feature enabled.
Expected result: The value of the S4233A:Number of Retransmitted Downlink
FACCH Frames counter is greater than 0 for consecutive seven days in certain
measurement periods.
2. Verify Repeated SACCH.
Measure the value of the following counters for all TRXs in the cell with the Robust
Air Interface Signalling feature enabled:
– S4233B:Number of Retransmitted Downlink SACCH Frames
– S4233C:Number of Indications to MS for Retransmitting SACCH Frames
Expected result: The value of either counter is greater than 0 for consecutive seven
days in certain measurement periods.
Parameters in Batches) with Repeated Downlink FACCH and Repeated
SACCH set to NO(No).
----End
Example
//Activating Robust Air Interface Signalling
SET GCELLCCBASIC: IDTYPE=BYID, CELLID=0, ECSC=YES, REPEATDLFASET=YES,
REPEATDLFATHRED=5, REPEATSASET=YES;
//Deactivating Robust Air Interface Signalling

SET GCELLCCBASIC: IDTYPE=BYID, CELLID=0, REPEATDLFASET=NO,
REPEATSASET=NO;

GBSS14.0

GBSS14.0
Feature Activation Guide 242 Configuring Abis Transmission Backup

Backup
About This Chapter
Abis Transmission Backup.
242.1 Configuring Satellite Transmission Backup (Ring Topology)

This section describes how to activate, verify, and deactivate the satellite transmission backup
(ring topology) function in the optional feature GBFD-117803 Abis Transmission Backup.
242.2 Configuring Satellite Transmission Backup (Dual-Logical BTS)
(dual-logical BTS) function in the optional feature GBFD-117803 Abis Transmission Backup.
242.3 Configuring Abis Transmission Backup Enhancement
This section describes how to activate, verify, and deactivate the Abis transmission backup
enhancement function in the optional feature GBFD-117803 Abis Transmission Backup.

GBSS14.0
242.1 Configuring Satellite Transmission Backup (Ring

Topology)
(ring topology) function in the optional feature GBFD-117803 Abis Transmission Backup.
Prerequisites
– Resources are available for terrestrial transmission and satellite transmission.
– The BTS supports the Ring I topology.
– This feature depends on the feature GBFD-113901 Satellite Transmission over Abis
Interface and GBFD-117801 Ring Topology.
l License
Context
When a disaster-caused failure occurs in the active SDH transmission link over the TDM-based
Abis interface, the GBSS automatically switches transmission link to a backup satellite
transmission link. In this manner, the normal operation of the network is ensured.
With the satellite transmission backup enabled, the transmission mode in the forward link is
different from that in the reverse link. That is, the forward link uses terrestrial transmission and
the reverse link uses satellite transmission, as shown in Figure 242-1.
Figure 242-1 Network topology when the satellite transmission backup is enabled
Procedure

GBSS14.0
View > Right click BTS > Modify Ring Topology Attribute; CME batch
modification center: not supported). In this step, set Config Ring (CME: Support
Ring Topology) to YES.
3. Run the BSC6900 MML command SET BTSRINGATTR (CME single
configuration: BTS Configuration Express > BTS Transmission Link > Ring
Attribues; CME batch modification center: not supported). In this step, set Configure
Ring II to NO(No) and Ring I Wait Time Before Switch and Ring I Try Rotating
Duration Time to appropriate values.
Chain; CME batch modification center: not supported) to add a reverse ring
connection.
5. Run the BSC6900 MML command SET BTSTRANS (CME single configuration:
BTS Configuration Express > BTS Basic Attributes > BTS Transfers Mode; CME
batch modification center: not supported). In this step, set Transmission Mode to
TER_AND_SAT_TRANS(Terrestrial and Satellite).
supported) to activate the target BTS.
1. (Optional) Use the MS to make a call.
NOTE
Before verification, ensure that the MS can make a call through terrestrial transmission in a non-
ring topology network.
2. Run the BSC6900 MML command LST BTS to query the value of Config Ring
(CME: Support Ring Topology).
Expected result: The value of Config Ring (CME: Support Ring Topology) is
YES.
3. Run the BSC6900 MML command LST GTRXDEV to query the value of
Transmission Mode.
Expected result: The value of Transmission Mode is TER_AND_SAT_TRANS.

4. Interrupt the terrestrial transmission between the BTS and the BSC. For example,
remove the E1 cable from port 0 on the BTS.
Expected result: The BTS is reset. Five minutes later, the MS can make a call.
2. Run the BSC6900 MML command SET BTSTRANS (CME single configuration:
BTS Configuration Express > BTS Basic Attributes > BTS Transfers Mode; CME
batch modification center: not supported). In this step, set Transmission Mode to

GBSS14.0
TER_TRANS(Terrestrial Transmission) or SAT_TRANS(Satellite

Transmission).
Chain; CME batch modification center: not supported) to remove a reverse ring
connection.
View > Right click BTS > Modify Ring Topology Attribute; CME batch
modification center: not supported). In this step, set Config Ring (CME: Support
Ring Topology) to NO(No).
supported) to activate the target BTS.
----End
Example
/*Activating Satellite Transmission Backup*/
//Deactivating the target BTS
//Enabling ring topology for a BTS
MOD BTS: IDTYPE=BYID, BTSID=1, ISCONFIGEDRING=YES;
SET BTSRINGATTR: IDTYPE=BYID, BTSID=1, FASTCNETFLAG=NO, WTBS=90, TBS=90;
//Adding a reverse ring connection
PN=1;
//Setting BTS transmission mode
SET BTSTRANS: IDTYPE=BYID, BTSID=1, TransMode=TER_AND_SAT_TRANS;
/*Deactivating Satellite Transmission Backup*/

//Setting BTS transmission mode
SET BTSTRANS: IDTYPE=BYID, BTSID=1, TransMode=TER_TRANS;
//Removing a reverse ring connection
RMV BTSCONNECT: IDTYPE=BYID, BTSID=1, INPN=1;
//Disabling ring topology for a BTS
MOD BTS: IDTYPE=BYID, BTSID=1, ISCONFIGEDRING=NO;
//Activating the target BTS
242.2 Configuring Satellite Transmission Backup (Dual-

Logical BTS)
(dual-logical BTS) function in the optional feature GBFD-117803 Abis Transmission Backup.
Prerequisites
– Link resources are required for terrestrial and satellite transmission modes.

GBSS14.0
– An interface board for TDM transmission is required on the BSC side.

– BTS3900, BTS3900A, BTS3900L, and BTS3900AL must be configured with GTMUa
or GTMUb boards to support this feature.
– The terrestrial BTS occupies port 0 on the physical BTS as the main port, and the satellite
BTS occupies port 1 on the physical BTS as the main port.
– This feature depends on the GBFD-117301 Flex Abis feature.
– This feature cannot be used together with the features GBFD-118601 Abis over IP,
GBFD-118611 Abis IP over E1/T1, GBFD-118401 Abis Transmission Optimization,
GBFD-116601 Abis Bypass, GBFD-117801 Ring Topology, and MRFD-210205 Chain
Topology.
l License
Context
The dual-logical BTS solution provides two logical BTSs for a physical BTS. One logical BTS
uses satellite transmission, and the other uses TDM terrestrial transmission. If the TDM
terrestrial transmission is faulty, the system automatically switches over the transmission link
to the backup satellite transmission. The satellite station begins to process services to ensure
normal network communication.
The requirements for naming the two logical BTSs are as follows:
l The type of a BTS (a terrestrial BTS or a satellite BTS) must be identified.
l The mapping between two logical BTSs and a physical BTS must be identified.
For example, two logical BTSs in site A can be named as terrestrial BTS A and satellite BTS
A.
Procedure
1. Configure the terrestrial BTS.
a. Configuring BTS Attributes
b. Configuring the Equipment Data
c. Configuring the Transmission Data
d. Configuring the Radio Data
e. Activating the BTS Configuration
2. Configure the satellite BTS.
NOTE
The configuration data about boards, RXU, cells, and TRXs of the satellite BTS must be
consistent with that of the terrestrial BTS.
a. Configuring BTS Attributes

b. Configuring the Equipment Data
c. Configuring the Transmission Data

GBSS14.0
d. Run the BSC6900 MML command SET BTSOTHPARA (CME single

Parameters of BTS; CME batch modification center: not supported). In this
step, set BTS Port Detection Sequence to CUSTOMIZDE(Customized
Sequence), Number of Customized Detection Types to 2, Preferential
Customized Detection Type to TDME1_1(TDM E1 1 Port), and Subsidiary
Customized Detection Type to TDME1_O(TDM E1 0 Port).
e. Run the BSC6900 MML command SET BTSTRANS (CME single
Transfers Mode; CME batch modification center: not supported). In this step,
set Transmission Mode to SAT_TRANS(Satellite Transmission).
f. Configuring the Radio Data
g. Activating the BTS Configuration
1. Use an MS to process a call.
NOTE
Ensure that the MS processes a call properly in terrestrial transmission mode and non-ring topology
mode.
2. Remove the E1 cable from port 0 of the BTS to disconnect the terrestrial link between
the BTS and the BSC.
Expected result: The original call is interrupted and the BTS resets. The MS can
process a call 10 minutes later.
None
----End
Example
/*Activating Satellite Transmission Backup (Dual-Logical BTS)*/
//Configuring the terrestrial BTS:
ADD BTS: BTSID=9, BTSNAME="BTS3900_Terrestrial", BTSTYPE=BTS3900_GSM,
BTSDESC="BTS3900_Terrestrial",
SEPERATEMODE=SUPPORT, SERVICEMODE=TDM, SRANMODE=SUPPORT;
ADD BTSCABINET: IDTYPE=BYID, BTSID=9, CN=0, SRANMODE=SUPPORT,
TYPE=BTS3900;
ADD BTSBRD: IDTYPE=BYID, BTSID=9, CN=0, SRN=11, SN=0, BT=FMU;
ADD BTSRXUCHAIN: IDTYPE=BYID, BTSID=9, RCN=0, TT=CHAIN, HCN=0, HSRN=0,
HSN=6, HPN=0;
HSN=6, HPN=1;
HSN=6, HPN=2;
ADD BTSRXUBRD: IDTYPE=BYID, BTSID=9, BT=GRFU, RXUSPEC=GRFU_V1, CN=0,
SRN=4, SN=0, RXUNAME=" BTS3900_Terrestrial 0",
RXUCHAINNO=0, RXUPOS=1, ISCONFIGTHD=NO;
ADD GCELL:CELLID=5,CELLNAME="cell-11", TYPE=DCS1800, MCC="460",
MNC="164", LAC=6, CI=1;

GBSS14.0

MNC="164", LAC=6, CI=2;
MNC="164", LAC=6, CI=3;
ADD GCELLFREQ: IDTYPE=BYID,CELLID=5, FREQ1=513,FREQ2=515;
ADD CELLBIND2BTS: IDTYPE=BYID,CELLID=5,BTSID=9;
ADD GTRX: IDTYPE=BYID,CELLID=5,TRXID=9, FREQ=513, ISMAINBCCH=YES;
ADD GTRX: IDTYPE=BYID,CELLID=5,TRXID=10, FREQ=515, ISMAINBCCH=NO;
ADD TRXBIND2PHYBRD: TRXID=9, TRXTP=GRFU, TRXPN=0, RXUIDTYPE=RXUNAME,
RXUNAME=" BTS3900_Terrestrial 0";
SET GTRXCHAN: TRXID=9, CHNO=0,CHTYPE=MBCCH, TSPRIORITY=1;
SET GTRXDEV: TRXID=9, RCVMD=MAINDIVERSITY, SNDMD=DTIC;
SET GTRXDEV: TRXID=10,RCVMD=MAINDIVERSITY, SNDMD=DTIC;
SET GTRXDEV: TRXID=14,RCVMD=MAINDIVERSITY, SNDMD=DTIC;
ACT BTS:IDTYPE=BYID,BTSID=9;
//Configuring the satellite BTS:

ADD BTS: BTSID=10, BTSNAME="BTS3900_Satellite", BTSTYPE=BTS3900_GSM,
BTSDESC="BTS3900_Satellite",
SEPERATEMODE=SUPPORT, SERVICEMODE=TDM, MAINPORTNO=1, SRANMODE=SUPPORT;
ADD BTSCABINET: IDTYPE=BYID, BTSID=10, CN=0, SRANMODE=SUPPORT,
TYPE=BTS3900;
ADD BTSBRD: IDTYPE=BYID, BTSID=10, CN=0, SRN=11, SN=0, BT=FMU;
HSN=6, HPN=0;
HSN=6, HPN=1;
HSN=6, HPN=2;
SRN=4, SN=0, RXUNAME=" BTS3900_Satellite 0",

GBSS14.0

ADD GCELL: CELLID=8, CELLNAME="cell-Satellite 1", TYPE=DCS1800,
MCC="460", MNC="164", LAC=6, CI=4;
MCC="460", MNC="164", LAC=6, CI=5;
MCC="460", MNC="164", LAC=6, CI=6;
RXUNAME=" BTS3900_Satellite 0";
SET BTSOTHPARA: IDTYPE=BYID, BTSID=10, SENDSAMBE=NO, ISSUPERBTS=YES,
PROBESEQ=CUSTOMIZDE, PRIVATEPROBENUM=2,
PRIVATEPROBEFST=TDME1_1, PRIVATEPROBESND=TDME1_O;
SET BTSTRANS: IDTYPE=BYID, BTSID=10, TransMode=SAT_TRANS;
ACT BTS: IDTYPE=BYID,BTSID=10;

GBSS14.0
242.3 Configuring Abis Transmission Backup Enhancement

This section describes how to activate, verify, and deactivate the Abis transmission backup
enhancement function in the optional feature GBFD-117803 Abis Transmission Backup.
Prerequisites
– This feature depends on the features GBFD-118601 Abis over IP and GBFD-118611
Abis IP over E1/T1.
l License
– This feature requires the BSC to be configured with interfaces supporting both IP over
E1 and IP over FE/GE. Of these interface boards, the POUc supports IP over E1 and
the GOUc and FG2c boards supports IP over FE/GE.
– This feature supports BTS3900, BTS3900A, BTS3900L, BTS3900AL, and DBS3900.
However, these BTSs must be configured with GTMUb boards.
– The IP over FE/GE and IP over E1 transmission links are used between the BSC and
the BTS. In addition, The IP over E1 transmission link must be configured in an end-
to-end (E2E) manner.
– N/A
– This feature supports only the built-in PCU.
Context
l Precautions
– When deploying this feature, a BTS must be deactivated, activated or reset. Therefore,
services on the BTS will be interrupted for a short period.
– When primary and backup links are switched over, ongoing services will be interrupted
for less than 1 minute.
– Changing the value of the parameter Wait Time Before Link Switchover shortens or
prolongs the interruption, and therefore the default value is used.
l Data Preparation

GBSS14.0
Parameter
Switch for Abis AbisLnkBKFLAG This parameter is set to Network

link backup ON when the Abis planning
transmission backup
enhancement is supported.
Path flag PATHFLAG Set this parameter to Network

Primary for the primary planning
link and to Backup for the
backup link.
BTS IP in BAKBTSIP The setting of this Network

Backup Link parameter depends on the planning
actual IP address of the
backup link on the BTS
side.
BSC IP in BAKBSCIP The setting of this Network

Backup Link parameter depends on the planning
actual IP address of the
backup link on the BSC
side.
Wait Time WTBTBSCS N/A Network

Before Switch to planning
Peer BSC
Bear Type BAKCFGFLAG This parameter can be set to Network

NULL, IPLGCPORT, or planning
RSCGRP based on actual
demands.
Slot No. BAKSN This parameter is valid only Network

if Bear Type is set to planning
IPLGCPORT.
Logical Port No. BAKLPN This parameter is valid only Network

in Backup Link if Bear Type is set to planning
IPLGCPORT.
Resource Group BAKGRPID This parameter is valid only Network

No. in Backup if Bear Type is set to planning
Link RSCGRP.
Wait Time WTBS N/A Network

Before Link planning
Switchover
Detect Packet DETECTTXINT N/A Network

Transmit planning
Interval

GBSS14.0
Parameter
Detect Packet DETECTCOUNT N/A Network

Retransmission planning
Times
Procedure
– Scenarios for Initial Configuration
Panel > Add Board; CME batch modification center: not supported) to add
interface boards supporting IP over E1 and IP over FE/GE.
supported) to add an IP BTS. In this step, set IP Phy Trans Type to
IP_OVER_FE/GE_AND_E1.
3. Configuring the Equipment Data
NOTE
TRCBSC_CLK(Trace BSC Clock) is recommended when this feature is enabled.
4. Configuring the Transmission Data
– Configuring IP over FE/GE and IP over E1/T1 transmission data
– Run the BSC6900 MML command ADD BTSIPBAK (CME single
configuration: BTS Configuration Express > BTS Transmission Link > a
BTS IP Address with Abis Link Backup Enabled; CME batch modification
center: not supported) to add a communication address for the backup link on
an IP BTS.
– Run the BSC6900 MML command ADD IPPATH (CME single configuration:
Abis Configuration Express > IP Transport > IP Path; CME batch
modification center: not supported) to add an IP path for the primary link. In
this step, set Switch for Abis link backup to ON, and set Path flag to
Primary.
modification center: not supported) to add an IP path for the backup link. In
Backup.
– Run the BSC6900 MML command SET BTSLNKBKATTR (CME single
BTS Backup Link Attributes with Abis Link Backup Enabled; CME batch
modification center: not supported) to change the backup link attribute of this
feature. However, the backup link attribute is usually set to the default value.
– Run the BSC6900 MML command LST BTSLNKBKATTR (CME single
BTS Backup Link Attributes with Abis Link Backup Enabled) to query the
backup link attribute.

GBSS14.0
– Run the BSC6900 MML command ADD IPMUX (CME single configuration:
Abis Configuration Express > IP Transport > IP MUX Pipe; CME batch
modification center: not supported) to enable the IP packet multiplexing
function only on a primary link. The primary link can be an IP over FE/GE link
or an IP over E1 link.
5. Configuring the Radio Data
6. Activating the BTS Configuration
– Changing TDM to Abis Transmission backup enhancement
interface boards supporting IP over E1 and IP over FE/GE.
center: not supported). In this step, set IP Phy Trans Type to IP_OVER_FE/
GE_AND_E1.
4. Configuring the Transmission Data
– Configuring IP over FE/GE and IP over E1/T1 transmission data
– Run the BSC6900 MML command SET BTSIP (CME single configuration:
BTS IP Configuration Express > BTS IP Properties > IP BTS
Communication Address; CME batch modification center: not supported) to
set the communication address for the primary link on an IP BTS.
an IP BTS.
Primary.
Backup.

GBSS14.0
5. Configuring a Clock for a BTS
NOTE
– Changing IP over E1 to Abis transmission backup enhancement
interface boards supporting IP over FE/GE.
GE_AND_E1.
4. Configuring IP over FE/GE transmission data
– Run the BSC6900 MML command RMV IPMUX (CME single configuration:
modification center: not supported) to remove the IP packet multiplexing
function if the IP packet multiplexing function is enabled on the IP over E1
link.
– Run the BSC6900 MML command DEA IPPM (CME single configuration:
Abis Configuration Express > IP Transport > IPPM; CME batch
modification center: not supported) to deactivate IP PM if IP PM is enabled on
the IP over E1 link.
– Run the BSC6900 MML command LST IPPATH (CME single configuration:
Abis Configuration Express > IP Transport > IP Path) to query the
configured IP path.
– Run the BSC6900 MML command RMV IPPATH (CME single
configuration: Abis Configuration Express > IP Transport > IP Path; CME
batch modification center: not supported) to remove the configured IP path.
an IP BTS.

GBSS14.0
Primary.
Backup.
NOTE
– Changing IP over FE/GE to Abis transmission backup enhancement
interface boards supporting IP over E1.
GE_AND_E1.
4. Configuring IP over E1 transmission data
– Run the BSC6900 MML command RMV IPMUX (CME single configuration:
modification center: not supported) to remove the IP packet multiplexing
function if the IP packet multiplexing function is enabled on the IP over FE/
GE link.
– Run the BSC6900 MML command DEA IPPM (CME single configuration:
Abis Configuration Express > IP Transport > IPPM; CME batch
modification center: not supported) to deactivate the IP PM function first if the
IP PM function is enabled on the IP over FE/GE link.

GBSS14.0
– Run the BSC6900 MML command LST IPPATH (CME single configuration:
Abis Configuration Express > IP Transport > IP Path) to query the
configured IP path.
– Run the BSC6900 MML command RMV IPPATH (CME single
configuration: Abis Configuration Express > IP Transport > IP Path; CME
batch modification center: not supported) to remove the configured IP path.
an IP BTS.
Primary.
Backup.
NOTE
– IP over E1
State.

GBSS14.0
b. If the PPP link is used, Run the BSC6900 MML command DSP PPPLNK
to query Link State, Local IP Address, and Peer IP Address. If the link
state is normal and the values of Local IP Address and Peer IP Address are
consistent with data configurations, proceed to the following steps.
Otherwise, the transmission link is faulty. Locate and rectify the fault.
c. If the MLPPP link is used, Run the BSC6900 MML command DSP
MPGRP to query Link State, Local IP Address, and Peer IP Address, and
Run the BSC6900 MML command DSP MPLNK to query Link State and
LCP Negotiation State. If the link state is normal, the value of LCP
Negotiation State is Connect available, and the values of Local IP
Address and Peer IP Address are consistent with data configurations,
proceed to the following steps. Otherwise, the transmission link is faulty.
Locate and rectify the fault.
d. If the PPP link is used, Run the BSC6900 MML command PING IP with
PPPLNK command and Destination IP address set to the same value as
Peer IP address in the DSP PPPLNK command. If the statistics on PING
packets can be received, the PPP link is normal.
e. If the MLPPP link is used, Run the BSC6900 MML command PING IP with
MPGRP command and Destination IP address set to the same value as Peer
IP address in the DSP MPGRP command. If the statistics on PING packets
can be received, the MLPPP link is normal.
– IP over FE/GE
a. Run the BSC6900 MML command DSP ETHPORT with subrack number,
slot number, and port number are those of the peer interface board connected
to the BTS. Check Port state and Link Availability Status in the command
execution result. If Port state is Activated and Link Availability Status is
Available, the link is normal.
b. Run the BSC6900 MML command PING IP with Source IP address set to
BSC IP and Destination IP address set to BTS IP in LST BTSIP for the
active link and with Source IP address set to BSC IP in Backup Link and
Destination IP address set to BTS IP in Backup Link in LST
BTSIPBAK.
2. Verify the control plane on the Abis interface.
a. Run the BSC6900 MML command DSP LAPDLNK to check whether the LAPD
link is normal. If Usagestatus is set to Normal, the LAPD link is functional.
After the command is executed to query Abis signaling link by BTS index, if the
command output shows that Usagestatus is set to Normal for an operation and
maintenance link (OML) whose Link flag is set to Primary, the primary link is
working; if the command output shows that Usagestatus is set to Normal for an
OML whose Link flag is set to Backup, the backup link is working. Under
common circumstances, Usagestatus is set to Faulty for a link that is not
working.
b. Run the BSC6900 MML command DSP ADJNODE to obtain the state of an
by checking related parameters, for example, Operation state. If Operation
state is Available and the related bandwidth is greater than 0, the adjacent node
is normal.

GBSS14.0
3. Verify the user plane on the Abis interface.

a. Run the BSC6900 MML command DSP IPPATH check whether the IP path is
available. If Operation state is Available and the available bandwidth is greater
than 0, the IP path is functional.
2. Run the BSC6900 MML command RMV IPPATH (CME single configuration: Abis
Configuration Express > IP Transport > IP Path; CME batch modification center:
not supported) to remove the IP path of the primary link.
3. Run the BSC6900 MML command SET BTSIP (CME single configuration: BTS IP
Configuration Express > BTS IP Properties > IP BTS Communication
Address; CME batch modification center: not supported) to set the communication
address for the primary link on an IP BTS.
Chain; CME batch modification center: not supported) to remove the BTS connection
if the IP over FE/GE transmission is used.
center: not supported). In this step, set IP Phy Trans Type to IP_OVER_E1 or
IP_OVER_FE/GE.
6. Run the BSC6900 MML command RMV IPPATH (CME single configuration: Abis
not supported) to remove the IP path of the backup link.
7. Run the BSC6900 MML command RMV BTSIPBAK (CME single configuration:
BTS Configuration Express > BTS Transmission Link > a BTS IP Address with
Abis Link Backup Enabled; CME batch modification center: not supported) to
remove the communication address for the backup link on an IP BTS.
8. Run the BSC6900 MML command ADD IPPATH (CME single configuration: Abis
not supported) to add an IP path.
----End
Example
/*Activating Abis Transmission Backup Enhancement*/
// Configuring Abis transmission backup enhancement with IP over FE/GE
transmission link
to be used as the primary link and IP over E1 transmission link to be used
as the
backup link:
ISTCBRD=NO,
MPUSUBRACK=0, MPUSLOT=0;
ADD BRD: SRN=2, BRDCLASS=INT, BRDTYPE=FG2c, LGCAPPTYPE=IP, SN=14,
RED=YES, MPUSUBRACK=2,

GBSS14.0
MPUSLOT=0;
ADD BTS:BTSID=0, BTSNAME="BTS-0", BTSTYPE=BTS3900_GSM,
SEPERATEMODE=SUPPORT,
SERVICEMODE=IP,
FLEXABISMODE=FIX_16K_ABIS, ABISBYPASSMODE=FALSE, ISCONFIGEDRING=NO,
MPMODE=MODE4_1,
WORKMODE=E1, BTSDESC="-",
MAINPORTNO=0, IPPHYTRANSTYPE=IP_OVER_FE/GE_AND_E1, SRANMODE=SUPPORT,
MAINBMPMODE=MODE_NULL, INTRABBPOOLSWITCH=OFF;
ADD BTSCABINET:CN=0, BTSID=0, IDTYPE=BYID, TYPE=BTS3900,
CABINETDESC="btscabinet-0",
SRANMODE=SUPPORT,
ISMAINCABINET=DEFAULTRULE;
ADD BTSRXUCHAIN:RCN=0, BTSID=0, IDTYPE=BYID, TT=CHAIN, HPN=0, HCN=0,
HSRN=0, HSN=6;
ADD BTSRXUBRD:BTSID=0, CN=0, SRN=4, SN=0, IDTYPE=BYID, RXUCHAINNO=0,
BT=DRFU,
RXUNAME="DRFU-0", RXUPOS=1;
ADD GCELL:CELLID=0, CELLNAME="cell0", MCC="502", MNC="86", LAC=390, CI=2,
NCC=0, BCC=0,
EXTTP=Normal_cell,
IUOTP=Normal_cell, FLEXMAIO=OFF, CSVSP=3, CSDSP=5, PSHPSP=4, PSLPSVP=6,
BSPBCCHBLKS=1,
BSPAGBLKSRES=4,
BSPRACHBLKS=1, TYPE=GSM900, OPNAME="g-xiwu0", VIPCELL=NO, MOCNCMCELL=NO,
HYBHIFREQBANDSUPPORT=NO;
ADD GCELLOSPMAP:CELLID=0, IDTYPE=BYID, OPC=2950;
ADD GTRX:TRXID=0, TRXNAME="cell00", FREQ=123, TRXNO=0, CELLID=0,
IDTYPE=BYID,
ISMAINBCCH=YES, ISTMPTRX=NO;
SET GTRXCHAN:TRXID=0, CHNO=7, CHTYPE=TCHFR, TSPRIORITY=0, GPRSCHPRI=GPRS,
CHANRSV=NO,
IDTYPE=BYID;
CHANRSV=NO,
IDTYPE=BYID;
SET GTRXCHAN:TRXID=0, CHNO=5, CHTYPE=PDTCH, TSPRIORITY=0, GPRSCHPRI=GPRS,
CHANRSV=NO,
IDTYPE=BYID;
CHANRSV=NO,
IDTYPE=BYID;
CHANRSV=NO,
IDTYPE=BYID;
CHANRSV=NO,
IDTYPE=BYID;
SET GCELLGPRS:CELLID=0, IDTYPE=BYID, GPRS=SupportAsInnPcu, EDGE=NO,
NACCSPT=NO, PKTSI=NO,
NC2SPT=NO, RA=0,
SUPPORTDTM=UNSUPPORT, DLDCSPT=UNSUPPORT, SPTREDUCELATENCY=UNSUPPORT,
EGPRS2A=NO,
SPTINTERRATOUTBSCPSHO=UNSUPPORT,
SPTINTERRATINBSCPSHO=UNSUPPORT, SPTLTEINBSCPSHO=UNSUPPORT,
SPTLTEOUTBSCPSHO=UNSUPPORT,
SPTDPI=UNSUPPORT,
PSPAGINGCTRL=ALWAYSNORMALPAGING, SUPPORTEDA=NOTSUPPORT;
ADD CELLBIND2BTS:CELLID=0, BTSID=0, IDTYPE=BYID;
ADD TRXBIND2PHYBRD:TRXID=0, TRXIDTYPE=BYID, TRXTP=DRFU, TRXPN=0, CN=0,
SRN=4, SN=0,

GBSS14.0
BTSID=0, RXUIDTYPE=SRNSN,
IDTYPE=BYID;
ADD ETHIP:SRN=2, SN=14, PN=0, IPINDEX=0, IPADDR="50.50.50.50",
MASK="255.255.255.0";
ADD ETHREDPORT:SRN=2, SN=14, PN=0;
ADD IPLOGICPORT:SRN=2, SN=14, BT=FG2c, LPNTYPE=Leaf, LPN=0, CARRYT=ETHER,
PN=0,
RSCMNGMODE=SHARE, BWADJ=OFF,
CIR=500, CBS=4500, OAMFLOWBW=0, FLOWCTRLSWITCH=ON, FCINDEX=0,
TRMLOADTHINDEX=2,
OPSEPFLAG=OFF;
TSBITMAP=TS1-1&TS2-1;&TS3-1;
&
TS4-1;&TS5-1;&TS6-1;&TS7-1;&TS8-1;&TS9-1;&TS10-1;&TS11-1;&TS12-1;&TS13-1;
&TS14-1;
&
TS15-1;&TS16-1;&TS17-1;&TS18-1;&TS19-1;&TS20-1;&TS21-1;&TS22-1;&TS23-1;&T
S24-1;&TS25-1;
&TS26-1;&TS27-1;&TS28-1;&TS29-1;&TS30-1;&TS31-1;, BORROWDEVIP=NO,
LOCALIP="40.40.40.40",
MASK="255.255.255.0", PEERIP="40.40.40.1", PPPMUX=Disable,
AUTHTYPE=NO_V,
FLOWCTRLSWITCH=ON, ERRDETECTSW=OFF, OPSEPFLAG=OFF;
ADD BTSCONNECT:BTSID=0, INPN=0, IDTYPE=BYID, INCN=0, INSRN=0, INSN=6,
DESTNODE=BSC,
SRN=0, SN=8, PN=0,
OPNAME="g-xiwu0";
ADD BTSPPPLNK:PPPLNKN=0, BTSID=0, IDTYPE=BYID, PN=0, CN=0, SRN=0, SN=6,
TSBITMAP=TS1-1&TS2-1;&TS3-1;&TS4-1;&TS5-1;&TS6-1;&TS7-1;&TS8-1;&TS9-1;&TS
10-1;&TS11-1;
&
S21-1;&TS22-1;
&
TS23-1;&TS24-1;&TS25-1;&TS26-1;&TS27-1;&TS28-1;&TS29-1;&TS30-1;&TS31-1;,
LOCALIP="40.40.40.1", MASK="255.255.255.0", PEERIP="40.40.40.40",
PFC=YES, ACFC=YES,
MRU=1500, AUTHTYPE=NO_V, RSTIME=3000, IPHC=DISABLE, PPPEAAT=10,
PPPEADT=5, IPEAAT=10,
IPEADT=5;
SET BTSETHPORT:PN=1, BTSID=0, IDTYPE=BYID, CN=0, SRN=0, SN=6, RATE=AUTO,
MTU=1500,
FC=CLOSE, SWITCH3AH=CLOSE,
MACEAAT=10, MACEADT=5, IPEAAT=10, IPEADT=5;
MTU=1500,
ADD BTSDEVIP:PN=0, BTSID=0, PT=ETHPORT, IPIDX=1, IDTYPE=BYID, CN=0,
SRN=0, SN=6,
IP="60.60.60.1",
MASK="255.255.255.0", ISINNERIP=NO;
SET BTSIP:BTSID=0, IDTYPE=BYID, BSCIP="50.50.50.50", BTSIP="60.60.60.1",
BTSCOMTYPE=PORTIP, HOSTTYPE=SINGLEHOST,
GWIP="255.255.255.255", CFGFLAG=NULL, BTSGWIPSWITCH=OFF, BTSMUTIP=NO;
ADD BTSIPBAK: IDTYPE=BYID, BTSID=0, BAKBTSIP="40.40.40.1",
BAKBSCIP="40.40.40.40",
BAKCFGFLAG=NULL;
ADD BTSESN:BTSID=0, IDTYPE=BYID, MAINDEVTAB="21021127229T8B001500",
OMBEARBOARD=PANEL;
ADD IPRT:DSTIP="60.60.60.0", DSTMASK="255.255.255.0",

GBSS14.0
NEXTHOP="50.50.50.2", SRN=2,
SN=14, REMARK="0", PRIORITY=HIGH;
ADD BTSIPRT:RTIDX=0, BTSID=0, IDTYPE=BYID, PRI=60, CN=0, SRN=0, SN=6,
DSTIP="50.50.50.0",
DSTMASK="255.255.255.0", RTTYPE=NEXTHOP, NEXTHOP="60.60.60.2";
ADD ADJNODE:ANI=0, NAME="IP_over_FE&E1", NODET=ABIS, BTSID=0,
IDTYPE=BYID;
ADD IPPATH: ANI=0, PATHID=0, ITFT=ABIS, PATHT= EF, TXBW=100000,
RXBW=100000,
VLANFlAG=DISABLE, PATHCHK=ENABLED,
ECHOIP="60.60.60.1", PERIOD=4, CHECKCOUNT=3, CHECKT=UDP,
AbisLnkBKFLAG=ON;
ADD IPPATH:ANI=0, PATHID=1, ECHOIP="40.40.40.1", VLANFLAG=DISABLE,
PERIOD=5,
CHECKCOUNT=3, PATHT=QoS,
TXBW=100000, RXBW=100000, PATHCHK=ENABLED, ITFT=ABIS, TRMLOADTHINDEX=2,
ICMPPKGLEN=64,
CHECKT=UDP,
ABISLNKBKFLAG=ON, PATHFLAG=Backup;
ADD IPMUX: MUXTYPE=ABISMUX, ANI=0, PATHID=0, ISQOSPATH=NO, IPMUXINDEX=0;
ACT IPPM: ANI=0, PATHID=0, ISQOSPATH=NO, LOSTPKTDETECTSW=ON;
//Changing TDM to Abis transmission backup enhancement with IP over FE/GE

transmission
link to be used as the primary link and IP over E1 transmission link to
be used as the
backup link:
ISTCBRD=NO,
MPUSLOT=0;
MOD BTS: IDTYPE=BYID, BTSID=0, SERVICEMODE=IP, IPPHYTRANSTYPE=IP_OVER_FE/
GE_AND_E1;
MASK="255.255.255.0";
ADD IPLOGICPORT:SRN=2, SN=14, BT=FG2c, LPNTYPE=Leaf, LPN=0, CARRYT=ETHER,
PN=0,
RSCMNGMODE=SHARE, BWADJ=OFF,
CIR=500, CBS=4500, OAMFLOWBW=0, FLOWCTRLSWITCH=ON, FCINDEX=0,
TRMLOADTHINDEX=2,
OPSEPFLAG=OFF;
&
&TS14-1;
&
S24-1;
&TS25-1;&TS26-1;&TS27-1;&TS28-1;&TS29-1;&TS30-1;&TS31-1;,
BORROWDEVIP=NO,
PPPMUX=Disable,
AUTHTYPE=NO_V, FLOWCTRLSWITCH=ON, ERRDETECTSW=OFF, OPSEPFLAG=OFF;
DESTNODE=BSC,

GBSS14.0
SRN=0, SN=8, PN=0,

OPNAME="g-xiwu0";
10-1;&TS11-1;
&
S21-1;&TS22-1;
&
PFC=YES, ACFC=YES,
IPEADT=5;
MTU=1500,
MTU=1500,
SRN=0, SN=6,
IP="60.60.60.1",
BAKBSCIP="40.40.40.40",
BAKCFGFLAG=NULL;
ADD BTSESN:BTSID=0, IDTYPE=BYID, MAINDEVTAB="21021127229T8B001500",
OMBEARBOARD=PANEL;
NEXTHOP="50.50.50.2", SRN=2,
SN=14, REMARK="0",
PRIORITY=HIGH;
DSTIP="50.50.50.0",
ADD ADJNODE:ANI=0, NAME="IP_over_FE&E1", NODET=ABIS, BTSID=0,
IDTYPE=BYID;
RXBW=100000,
AbisLnkBKFLAG=ON;
PERIOD=5,
CHECKCOUNT=3, PATHT=QoS,
ICMPPKGLEN=64,
CHECKT=UDP,
//Changing IP over E1 transmission to Abis transmission backup enhancement

GBSS14.0
with
IP over FE/GE transmission link to be used as the primary link and IP over
E1 transmission
link to be used as the backup link:
MPUSLOT=0;
GE_AND_E1;
MASK="255.255.255.0";
SRN=0, SN=6,
IP="60.60.60.1",
RMV IPPATH:ANI=0, PATHID=0;
BAKBSCIP="40.40.40.40",
BAKCFGFLAG=NULL;
NEXTHOP="50.50.50.2",
SRN=2, SN=14, REMARK="0", PRIORITY=HIGH;
DSTIP="50.50.50.0",
RXBW=100000,
AbisLnkBKFLAG=ON;
PERIOD=5,
CHECKCOUNT=3, PATHT= EF,
ICMPPKGLEN=64,
CHECKT=UDP,
//Changing IP over FE/GE transmission to Abis transmission backup

enhancement with
IP over FE/GE transmission link to be used as the primary link and IP over
E1 transmission
link to be used as the backup link:
ISTCBRD=NO,
GE_AND_E1;

GBSS14.0
&
&TS14-1;
&
S24-1;
&TS25-1;&TS26-1;&TS27-1;&TS28-1;&TS29-1;&TS30-1;&TS31-1;,
BORROWDEVIP=NO,
PPPMUX=Disable,
AUTHTYPE=NO_V, FLOWCTRLSWITCH=ON, ERRDETECTSW=OFF, OPSEPFLAG=OFF;
DESTNODE=BSC,
SRN=0, SN=8, PN=0,
OPNAME="g-xiwu0";
10-1;&TS11-1;
&
S21-1;&TS22-1;
&
PFC=YES, ACFC=YES,
IPEADT=5;
BAKBSCIP="40.40.40.40",
BAKCFGFLAG=NULL;
RXBW=100000,
AbisLnkBKFLAG=ON;
PERIOD=5,
ICMPPKGLEN=64,
CHECKT=UDP,
/*Deactivating Abis Transmission Backup Enhancement*/
//Changing Abis Transmission Backup Enhancement to IP Over E1:
SET BTSIP: IDTYPE=BYID, BTSID=0, BTSCOMTYPE=PPP/MP, BTSIP="40.40.40.1",
BSCIP="40.40.40.40", CFGFLAG=NULL;
MOD BTS: IDTYPE=BYID, BTSID=0, SERVICEMODE=IP, IPPHYTRANSTYPE=IP_OVER_E1;

GBSS14.0
RMV BTSIPBAK: IDTYPE=BYID, BTSID=0;

PERIOD=5,
ICMPPKGLEN=64,
CHECKT=UDP;
//Changing Abis Transmission Backup Enhancement to IP Over FE/GE:

RMV BTSCONNECT: IDTYPE=BYID, BTSID=0, INPN=0, INCN=0, INSRN=0, INSN=6;
GE;
RMV BTSIPBAK: IDTYPE=BYID, BTSID=0;
PERIOD=5,
ICMPPKGLEN=64,
CHECKT=UDP;

GBSS14.0
Feature Activation Guide 243 Configuring BSC Node Redundancy
243 Configuring BSC Node Redundancy
This section describes how to activate, verify, and deactivate the GBFD-113725 BSC Node
Redundancy feature.
Prerequisites
– IP interface boards are required for the BSC and BTS.
– The A, Abis, and inter-BSC interfaces use IP transmission. No restrictions concerning
transmission are imposed on the Gb interface.
– BTSs other than the BTS3006C, BTS3002E, BTS3900B, and BTS3900E are used,
because the BTS3006C, BTS3002E, BTS3900B, and BTS3900E are not supported.
– Prerequisite features:
– The BSC Node Redundancy feature depends on the GBFD-118601 Abis over IP or
GBFD-118611 Abis IP over E1/T1 feature over the Abis interface.
– The BSC Node Redundancy feature depends on the GBFD-118602 A over IP or
GBFD-118622 A IP over E1/T1 feature over the A interface.
– The BSC Node Redundancy feature depends on the GBFD-115301 Local Multiple
Signaling Points feature if the BSC has single-homed BTSs or works in load sharing
mode.
– The WOFD-231100 BSC Redundancy Management -GBSS feature for the M2000 is
enabled.
l License

GBSS14.0
NOTE
If the electronic serial numbers (ESNs) for BSC 1 and BSC 2 are ESN 1 and ESN 2, respectively:
l In scenarios where only dual-homed BTSs are configured, license 1 is generated when the
order of BSC 1 is bound to ESN 1 and ESN 2, and license 2 is generated when the order of
BSC 2 is bound to ESN 1 and ESN 2. Then, licenses 1 and 2 are combined into one license
file, which is loaded on both BSCs.
l In scenarios where both single- and dual-homed BTSs are configured, license 1 is generated
when the order of BSC 1 is bound to ESN 1, and license 2 is generated when the order of
BSC 2 is bound to ESN 2. Then, license 1 and license 2 are loaded on BSC 1 and BSC 2,
respectively. The licenses for enabling this feature on BSCs 1 and 2 have been obtained.
l IP transmission is used between the BSC and CN/BTS.
l A BTS cannot directly connect to a BSC over the Abis interface. Therefore, BTSs use
routers to connect to the two BSCs in a redundancy group.
l For a BTS under two BSCs in a redundancy group, if the BTS is single-homed, it must be
configured only under one BSC; if the BTS is dual-homed, it must be configured as a
primary-homed BTS under one BSC and a secondary-homed BTS under the other BSC.
l The MSC is configured with M3UA links and M3UA link sets that connect to BSCs.
l Cell broadcast center (CBC) services do not support this feature.
l A redundancy group consists of only two BSCs.
l The two BSCs in a redundancy group connect to only one MSC or MSC pool.
l The two BSCs in a redundancy group connect to only one SGSN or SGSN pool.
l Only built-in packet control units (PCUs) support this feature.
l If both BSCs in a redundancy group are configured with dual-homed service objects, the
size of data for the single- and dual-homed service objects configured under one BSC must
not exceed the specification of the BSC.
Context
CAUTION
l Services are interrupted for 10 to 20 minutes when service objects are being migrated or
migrated back.
l Disable the BSC Node Redundancy feature before upgrading a BSC and enable this feature
after the upgrade is complete.
The data configuration for the BSC Node Redundancy feature consists of the following steps:
1. Configure signaling points and signaling links over the A interface. 2. Configure BTS data.
3. Configure signaling links over the inter-BSC interface. 4. Configure the BSC Node
Redundancy feature. You can configure other BSC data using the same method as that in
common scenarios. For details, see BSC6900 GSM Initial Configuration Guide.

GBSS14.0
NOTE
When BSC Node Redundancy is enabled, the data about BTSs and OPCs is configured in redundancy mode
on two BSCs. Therefore, after configuring data on one BSC, you can copy the configuration scripts to the
other BSC, thereby improving operation and maintenance (O&M) efficiency. However, you need to
manually modify some parameters because they must be set to different values on the two BSCs.
These parameters are classified into two types:
l Parameters related to device IP, port IP, next-hop IP, and destination IP. Setting these parameters to
different values on the two BSCs prevents conflicts of IP addresses.
l Parameters related to BSC Node Redundancy, including The host type of signalling point, HostType,
Local BSC ID, Peer BSC ID, BSC IP, and Peer BSC IP.
Table 243-1 Data Preparation

Parameter Parameter
Name ID Setting Notes Data Source
The host type HOSTTYP See section "Dual- and Engineering design
of signalling E Single-Homed Service
point Objects" in BSC Node
Redundancy Feature
Parameter Description.
HostType HOSTTYP See section "Dual- and Equipment plan

E Single-Homed Service
Objects" in BSC Node
Redundancy Feature
Peer BSC IP PEERBSCI - Radio network plan

P (negotiated with the peer
end)
Peer BTS ID PEERBTSI - Equipment plan

D
Peer BSC Mask PEERBSC - Transmission network plan

MASK (negotiated with the peer
end)
Peer BSC ID PEERBSCI - Transmission network plan

D (internal plan)
BSC Node GROUPIN - Engineering design

Redundancy DEX
Group Index
BSC Node GROUPNA - Engineering design

Redundancy ME
Group Name
Interval for BEATSEN See section "Fault Engineering design

Sending DINGDIS Detection" in BSC Node
Heartbeat Redundancy Feature

GBSS14.0
Parameter Parameter
Name ID Setting Notes Data Source
Master Service MSTSERV - Engineering design

Active Delay ACTDELA
Y
Slave Service SLVSERV - Engineering design

Active Delay ACTDELA
Y
CN Fault Delay CNFAULT - Engineering design

DELAY
CN State CNSTATE Set this parameter to Engineering design

Policy For POLICYFO AINTFBLOCK(AInterf
Group RGROUP Block).
Local BSC ID LocalBSCI - Engineering design

D
Peer BSC ID PeerBSCID - Engineering design
ReHost Type REHOSTT See section "Migrating Back Engineering design

YPE Dual-Homed Service
Redundancy Feature
ReHostDelayT REHOSTD See section "Migrating Back Engineering design

ime ELAYTIM Dual-Homed Service
E Objects" in BSC Node
Redundancy Feature
ReHost REHOSTA See section "Migrating Back Engineering design

Absolute Time BSTIME Dual-Homed Service
Redundancy Feature
Procedure
1. Configuring data on BSC 1 LMT
a. Configure signaling points and signaling links over the A interface.

GBSS14.0
NOTE
In load sharing mode, configure both primary- and secondary-homed OPCs and signaling
links. In active/standby mode, configure primary- or secondary-homed OPCs and signaling
links.
If the BSC has single-homed BTSs, configure single-homed OPCs and signaling links in the
same method as that in common scenarios. For details, see BSC6900 GSM Initial
To configure primary-homed OPCs and signaling links, run the following steps: (You can
configure secondary-homed OPCs and signaling links using the same method. For details, see
"Configuring data on BSC 2 LMT.")
a. Run the BSC6900 MML command ADD OPC (CME single configuration:
GSM Global Configuration Express > BSC Basic Configuration >
OSP; CME batch modification center: not supported). In this step, set OSP
name, OSP index, Network ID, OSP code bits, Signal point data
format, and OSP code to appropriate values. In addition, set The host type
of signalling point to PRIMHOST(PRIMHOST).
b. Run the BSC6900 MML command ADD N7DPC (CME single
Configuration > DSP Of DPU; CME batch modification center: not
supported) to add a destination signaling point (DSP) for the primary-homed
OPC. In this step, set DSP name, DSP index, OSP index, Signal point
data format, DSP code, DSP type, and DSP bear type to appropriate
values.
c. Run the BSC6900 MML command ADD M3LE (CME single
Configuration > M3UA Local Entity; CME batch modification center:
not supported) to add an M3UA local entity for the primary-homed OPC.
In this step, set OSP index to the same value as that for the primary-homed
OPC.
d. Run the BSC6900 MML command ADD M3DE (CME single
Configuration > M3UA Destination Entity; CME batch modification
center: not supported) to add an M3UA destination entity for the primary-
homed OPC. In this step, set DSP index to the same value as that for the
primary-homed OPC.
e. Run the BSC6900 MML command ADD M3LKS (CME single
Configuration > M3UA Link Set; CME batch modification center: not
supported) to add an M3UA link set for the primary-homed OPC. In this
step, set Destination entity No. to the same value as that for the primary-
homed OPC.
f. Run the BSC6900 MML command ADD M3RT (CME single
configuration: A Configuration Express > IP Transport > M3UA
Route; CME batch modification center: not supported) to add an M3UA
route for the primary-homed OPC. In this step, set Destination entity No.
and Signalling link set index to the same values as those for the primary-
homed OPC.
g. Run the BSC6900 MML command ADD SCTPLNK (CME single
configuration: A Configuration Express > IP Transport > SCTP Link;
CME batch modification center: not supported) to add an SCTP link for the
primary-homed OPC. In this step, set First local IP address, First

GBSS14.0
destination IP address, and Destination SCTP port No. to appropriate

values.
h. Run the BSC6900 MML command ADD M3LNK (CME single
supported) to add an M3UA link for the primary-homed OPC. In this step,
set SCTP link No. to the same value as that for the primary-homed OPC.
b. Configure BTS data.
NOTE
l The configuration data for a dual-homing BTS must be consistent on BSC 1 and BSC
2.When configuring BTS homing attributes on the two BSCs, the value of BTS ID
may be different, but the value of BTS NAME may be the same. During routine
maintenance, when you change the value of a BTS-related parameter on BSC 1, you
must simultaneously change the value of this parameter on BSC 2. To improve O&M
efficiency, set BTS ID to the same value on both BSCs.
l Configure a single-homed BTS using the same methods as that in common scenarios.
For details, see BSC6900 GSM Initial Configuration Guide.
l When configuring BTS homing attributes, set BSC IP, HostType, and Peer BSC
IP to the values negotiated between the two BSCs.
l To configure a dual-homed BTS for BSC 1 and BSC 2, run the following steps: (To
configure multiple dual-homed BTSs for BSC 1 and BSC 2, repeat these steps.)
a. Add a BTS onto BSC 1. For details, see Configuring a BTS in BSC6900
b. Run the BSC6900 MML command SET BTSIP (CME single
configuration: BTS IP Configuration Express > BTS IP Properties > IP
BTS Communication Address; CME batch modification center: not
supported). In this step, set BTS IP, BSC IP, HostType, Peer BTS ID,
Peer BSC ID, Peer BSC ID, and Peer BSC Mask to appropriate values.
BSC IP and Peer BSC IP indicate the IP addresses of the two BSCs.
c. Run the BSC6900 MML command ADD BTSIPRT (CME single
configuration: BTS IP Configuration Express > BTS IP Transmission >
BTS Route; CME batch modification center: not supported) to add routes
from the BTS to the two BSCs.
d. Configure neighboring cells by following the principles described in BSC
Node Redundancy Feature Parameter Description. For details, see
e. Configure PTP BVCs for the cells served by the dual-homed BTS on the
two BSCs. For details, see BSC6900 GSM Initial Configuration Guide.
c. Configure signaling links over the inter-BSC interface.
NOTE
When configuring signaling links over the inter-BSC interface, set First local IP address/
Second local IP address for BSC 1 to the same values as those of First destination IP
address/Second destination IP address for BSC 2, respectively. In addition, set First
destination IP address/Second destination IP address for BSC 1 to the same values as those
of First local IP address/Second local IP address for BSC 2, respectively. Set Local SCTP
port No./Destination SCTP port No. for BSC 1 to the same values as those of Destination
SCTP port No./Local SCTP port No. for BSC 2, respectively. Configure multiple signaling
links over the inter-BSC interface, and ensure that the configuration data is consistent on both
BSCs.

GBSS14.0
CME batch modification center: not supported). In this step, set Signalling
link mode to CLIENT(CLIENT MOD), and set Application type to
BBAP(BBAP).
b. Optional: Run the BSC6900 MML command ADD IPRT (CME single
configuration: Abis Configuration Express > IP Transport > IP Route;
CME batch modification center: not supported) to add an IP route from BSC
1 to intermediate equipment if BSC 1 connects to BSC 2 through the
intermediate equipment.
d. Configure the BSC Node Redundancy feature.
a. Run the BSC6900 MML command SET GBSCREDGRP (CME single
configuration: GSM Global Configuration Express > Redundancy
Backup Configuration > BSC Node Redundancy Group; CME batch
modification center: not supported) to configure data for a redundancy
group. In this step, set Local BSC ID and Peer BSC ID for BSC 1 to the
same values as those of Peer BSC ID and Local BSC ID for BSC 2,
respectively. In addition, set CN State Policy For Group to
AINTFBLOCK(AInterf Block).
b. Run the BSC6900 MML command SET
GREDGRPPRIMHOSTPOLICY (CME single configuration: GSM
Global Configuration Express > Redundancy Backup Configuration >
BSC Node Redundancy Group Prime Host Policy; CME batch
modification center: 3.17 Modifying GBSC Parameters in Batches). In
this step, set ReHost Type to an appropriate value.
c. Run the BSC6900 MML command ACT GBSCREDGRP (CME single
Backup Configuration > BSC Node Redundancy Group. Set Active
Status to Activated; CME batch modification center: not supported) to
activate the redundancy group.
2. Configuring data on BSC 2 LMT
a. Configure signaling points and signaling links over the A interface.
NOTE
In load sharing mode, configure both primary- and secondary-homed OPCs and signaling
links. In active/standby mode, configure primary- or secondary-homed OPCs and signaling
links.
If the BSC has single-homed BTSs, configure single-homed OPCs and signaling links in the
same method as that in common scenarios. For details, see BSC6900 GSM Initial
To configure secondary-homed OPCs and signaling links, run the following steps: (You can
configure primary-homed OPCs and signaling links using the same method. For details, see
"Configuring data on BSC 1 LMT.")
a. Run the BSC6900 MML command ADD OPC (CME single configuration:
OSP; CME batch modification center: not supported). In this step, set OSP
name, OSP index, Network ID, OSP code bits, Signal point data
format, and OSP code to appropriate values. In addition, set The host type
of signalling point to SLAVEHOST(SLAVEHOST).
b. Run the BSC6900 MML command ADD N7DPC (CME single
Configuration > DSP Of DPU; CME batch modification center: not
supported) to add a DSP for the secondary-homed OPC. In this step, set

GBSS14.0
DSP name, DSP index, OSP index, Signal point data format, DSP
code, DSP type, and DSP bear type to appropriate values.
c. Run the BSC6900 MML command ADD M3LE (CME single
Configuration > M3UA Local Entity; CME batch modification center:
not supported) to add an M3UA local entity for the secondary-homed OPC.
In this step, set OSP index to the same value as that for the secondary-
homed OPC.
d. Run the BSC6900 MML command ADD M3DE (CME single
Configuration > M3UA Destination Entity; CME batch modification
center: not supported) to add an M3UA destination entity for the secondary-
homed OPC. In this step, set DSP index to the same value as that for the
secondary-homed OPC.
e. Run the BSC6900 MML command ADD M3LKS (CME single
supported) to add an M3UA link set for the secondary-homed OPC. In this
step, set Destination entity No. to the same value as that for the secondary-
homed OPC.
f. Run the BSC6900 MML command ADD M3RT (CME single
configuration: A Configuration Express > IP Transport > M3UA
Route; CME batch modification center: not supported) to add an M3UA
route for the secondary-homed OPC. In this step, set Destination entity
No. and Signalling link set index to the same values as those for the
secondary-homed OPC.
g. Run the BSC6900 MML command ADD SCTPLNK (CME single
CME batch modification center: not supported) to add an SCTP link for the
secondary-homed OPC. In this step, set First local IP address, First
destination IP address, and Destination SCTP port No. to appropriate
values.
h. Run the BSC6900 MML command ADD M3LNK (CME single
supported) to add an M3UA link for the secondary-homed OPC. In this step,
set SCTP link No. to the same value as that for the secondary-homed OPC.
b. Configure BTS data.
NOTE
l The configuration data for a dual-homing BTS must be consistent on BSC 1 and BSC
2.When configuring BTS homing attributes on the two BSCs, the value of BTS ID
may be different, but the value of BTS NAME may be the same. During routine
maintenance, when you change the value of a BTS-related parameter on BSC 1, you
must simultaneously change the value of this parameter on BSC 2. To improve O&M
efficiency, set BTS ID to the same value on both BSCs.
l Configure a single-homed BTS using the same methods as that in common scenarios.
For details, see BSC6900 GSM Initial Configuration Guide.
l When configuring BTS homing attributes, set BSC IP, HostType, and Peer BSC
IP to the values negotiated between the two BSCs.
l To configure a dual-homed BTS for BSC 1 and BSC 2, run the following steps: (To
configure multiple dual-homed BTSs for BSC 1 and BSC 2, repeat these steps.)

GBSS14.0
a. Add a BTS onto BSC 1. For details, see Configuring a BTS in BSC6900
b. Run the BSC6900 MML command SET BTSIP (CME single
configuration: BTS IP Configuration Express > BTS IP Properties > IP
BTS Communication Address; CME batch modification center: not
supported). In this step, set BTS IP, BSC IP, HostType, Peer BTS ID,
Peer BSC ID, Peer BSC ID, and Peer BSC Mask to appropriate values.
BSC IP and Peer BSC IP indicate the IP addresses of the two BSCs.
c. Run the BSC6900 MML command ADD BTSIPRT (CME single
configuration: BTS IP Configuration Express > BTS IP Transmission >
BTS Route; CME batch modification center: not supported) to add routes
from the BTS to the two BSCs.
d. Configure neighboring cells by following the principles described in BSC
Node Redundancy Feature Parameter Description. For details, see
e. Configure PTP BVCs for the cells served by the dual-homed BTS on the
two BSCs. For details, see BSC6900 GSM Initial Configuration Guide.
c. Configure signaling links over the inter-BSC interface.
NOTE
When configuring signaling links over the inter-BSC interface, set First local IP address/
Second local IP address for BSC 1 to the same values as those of First destination IP
address/Second destination IP address for BSC 2, respectively. In addition, set First
destination IP address/Second destination IP address for BSC 1 to the same values as those
of First local IP address/Second local IP address for BSC 2, respectively. Set Local SCTP
port No. for BSC 1 to the same value as that of Destination SCTP port No. for BSC 2.
Configure multiple signaling links over the inter-BSC interface, and ensure that the
configuration data is consistent on both BSCs.

CME batch modification center: not supported). In this step, set Signalling
link mode to CLIENT(CLIENT MOD), and set Application type to
BBAP(BBAP).
b. Optional: Run the BSC6900 MML command ADD IPRT (CME single
configuration: Abis Configuration Express > IP Transport > IP Route;
CME batch modification center: not supported) to add an IP route from BSC
2 to intermediate equipment if BSC 1 connects to BSC 2 through the
intermediate equipment.
d. Configure the BSC Node Redundancy feature.
a. Run the BSC6900 MML command SET GBSCREDGRP (CME single
Backup Configuration > BSC Node Redundancy Group; CME batch
modification center: not supported) to configure data for a redundancy
group. In this step, set Local BSC ID and Peer BSC ID for BSC 2 to the
same values as those of Peer BSC ID and Local BSC ID for BSC 1,
respectively. In addition, set CN State Policy For Group to
AINTFBLOCK(AInterf Block).
b. Run the BSC6900 MML command SET
GREDGRPPRIMHOSTPOLICY (CME single configuration: GSM
Global Configuration Express > Redundancy Backup Configuration >
BSC Node Redundancy Group Prime Host Policy; CME batch

GBSS14.0
modification center: 3.17 Modifying GBSC Parameters in Batches). In

this step, set ReHost Type to an appropriate value.
c. Run the BSC6900 MML command ACT GBSCREDGRP (CME single
Backup Configuration > BSC Node Redundancy Group. Set Active
Status to Activated; CME batch modification center: not supported) to
activate the redundancy group.
This section verifies the BSC Node Redundancy feature by activating this feature on BSC
1 and deactivating this feature on BSC 2 when the queried BTS, M3UA link, and OPC are
all normal.
– Querying information about BSC Node Redundancy when both BSCs work correctly
1. Run the BSC6900 MML command DSP BTSSTAT to check the homing status
of the dual-homed BTS on BSC 1 LMT.
Expected result: The value of Hosted is Yes.
2. Run the BSC6900 MML command DSP M3LNK to check the status of an M3UA
link.
Expected result: The value of Administrative state is Uninhibited.
3. Run the BSC6900 MML command DSP OPC to check the homing status of the
dual-homed OPC.
Expected result: The value of OPC host state is Yes.
Expected result: The value of Hosted is No.
link.
Expected result: The value of Administrative state is Inhibited.
dual-homed OPC.
Expected result: The value of OPC host state is No.
– Verifying BSC Node Redundancy when a BSC fails
1. Power off BSC 1 and wait 20 minutes.
link.
dual-homed OPC.
5. Power on BSC 1 and wait 20 minutes.
6. Run the BSC6900 MML command DSP BTSSTAT on BSC 1 LMT and BSC 2
LMT to check the homing status of the dual-homed BTS controlled by each BSC.

GBSS14.0
Expected result: The value of Hosted for BSC 1 is Yesand the value of Hosted
for BSC 2 is No.
link connecting to each BSC.
Expected result: The value of Administrative state for BSC 1 is Uninhibitedand
the value of Administrative state for BSC 2 is Inhibited.
dual-homed OPC of each BSC.
Expected result: The value of OPC host state for BSC 1 is Yesand the value of
OPC host state for BSC 2 is No.
– Verifying BSC Node Redundancy when all the signaling links on the A interface of a
BSC do not work correctly
1. Run the BSC6900 MML command DEA M3LNK on BSC 1 LMT to deactivate
all the M3UA links on the A interface. Then, wait 20 minutes.
2. Run the BSC6900 MML command DSP BTSSTAT on BSC 2 LMT to check the
homing status of the dual-homed BTS.
link.
dual-homed OPC.
5. Run the BSC6900 MML command ACT M3LNK on BSC 1 LMT to activate all
the M3UA links on the A interface. Then, wait 20 minutes.
6. Run the BSC6900 MML command DSP BTSSTAT on BSC 1 LMT and BSC 2
LMT to check the homing status of the dual-homed BTS controlled by each BSC.
Expected result: The value of Hosted for BSC 1 is Yesand the value of Hosted
for BSC 2 is No.
link connecting to each BSC.
Expected result: The value of Administrative state for BSC 1 is Uninhibitedand
the value of Administrative state for BSC 2 is Inhibited.
dual-homed OPC of each BSC.
Expected result: The value of OPC host state for BSC 1 is Yesand the value of
OPC host state for BSC 2 is No.
1. Run the BSC6900 MML command DEA GBSCREDGRP (CME single
configuration: GSM Global Configuration Express > Redundancy Backup
Configuration > BSC Node Redundancy Group. Set Active Status to
Deactivated; CME batch modification center: not supported) on BSC 1 LMT and
BSC 2 LMT to deactivate BSC Node Redundancy on each BSC.
----End

GBSS14.0
Example
//Configuring data on BSC 1 LMT
//Configuring signaling points and signaling links over the A interface
ADD OPC: NAME="A", SPX=0, NI=NATB, SPCBITS=BIT14, SPDF=WNF, SPC=2730,
HOSTTYPE=PRIMHOST;
ADD N7DPC: NAME="A to MSC", DPX=0, SPX=0, SPDF=WNF, DPC=4369, DPCT=A,
BEARTYPE=M3UA;
ADD M3LE: LENO=0, SPX=0, ENTITYT=M3UA_IPSP, NAME="0";
ADD M3DE: DENO=0, LENO=0, DPX=0, ENTITYT=M3UA_IPSP, NAME="0";
ADD M3LKS: SIGLKSX=0, DENO=0, WKMODE=M3UA_IPSP, NAME="0";
ADD M3RT: DENO=0, SIGLKSX=0, NAME="0";
LOCIP1="192.3.0.111", PEERIP1="192.3.0.2", PEERPN=6000, LOGPORTFLAG=NO,
VLANFLAG1=DISABLE, VLANFlAG2=DISABLE, SWITCHBACKFLAG=YES;
ADD M3LNK: SIGLKSX=0, SIGLNKID=0, SRN=0, SN=2, SCTPLNKN=1, NAME="0";
//Configuring BTS attributes

SET BTSIP:BTSID=72, IDTYPE=BYID, BSCIP="172.18.125.124",
BTSIP="166.253.121.10", BTSCOMTYPE=PORTIP, HOSTTYPE=PRIMHOST,
PEERBTSID=172, PEERBSCIP="172.18.125.69", PEERBSCMASK="255.255.255.255",
PEERBSCID=1, CFGFLAG=NULL, BTSGWIPSWITCH=OFF;
//Configuring BTS routes

ADD BTSIPRT: IDTYPE=BYID, BTSID=72, DSTIP="172.18.125.124",
//Configuring neighboring cells (Cells 1 and 2046 are both dual-homed

cells.)
//Configuring PTP BVCs

ADD PTPBVC: NSEI=0, BVCI=6, IDTYPE=BYNAME, CELLNAME="cell-11";
//Configuring signaling links over the inter-BSC interface

ADD SCTPLNK: SRN=0, SN=2, SCTPLNKN=0, MODE=CLIENT, APP=BBAP, LOCPN=5000,
LOCIP1="192.3.0.111", LOCIP2="10.161.39.111", PEERIP1="192.3.0.110",
PEERIP2="10.161.39.110", PEERPN=58000, LOGPORTFLAG=NO, VLANFLAG1=DISABLE,
VLANFlAG2=DISABLE, SWITCHBACKFLAG=YES;
//Configuring BSC Node Redundancy

SET GBSCREDGRP: GROUPINDEX=0, CNSTATEPOLICYFORGROUP=AINTFBLOCK,
LocalBSCID=0, PeerBSCID=1;
SET GREDGRPPRIMHOSTPOLICY: REHOSTTYPE=REHOSTDELAY, REHOSTDELAYTIME=60;
ACT GBSCREDGRP: GROUPINDEX=0;
//Configuring data on BSC 2 LMT

//Configuring signaling points and signaling links over the A interface
ADD OPC: NAME="A", SPX=0, NI=NATB, SPCBITS=BIT14, SPDF=WNF, SPC=2730,
HOSTTYPE=SLAVEHOST;
ADD N7DPC: NAME="A to MSC", DPX=0, SPX=0, SPDF=WNF, DPC=4369, DPCT=A,
BEARTYPE=M3UA;
ADD M3LE: LENO=0, SPX=0, ENTITYT=M3UA_IPSP, NAME="0";
ADD M3DE: DENO=0, LENO=0, DPX=0, ENTITYT=M3UA_IPSP, NAME="0";
ADD M3LKS: SIGLKSX=0, DENO=0, WKMODE=M3UA_IPSP, NAME="0";
ADD M3RT: DENO=0, SIGLKSX=0, NAME="0";

GBSS14.0

LOCIP1="192.3.0.110", PEERIP1="192.3.0.2", PEERPN=6000,
ADD M3LNK: SIGLKSX=0, SIGLNKID=0, SRN=0, SN=2, SCTPLNKN=1, NAME="0";
//Configuring BTS attributes

SET BTSIP:BTSID=172, IDTYPE=BYID, BSCIP="172.18.125.69",
BTSIP="166.253.121.10", BTSCOMTYPE=PORTIP, HOSTTYPE=SLAVEHOST,
PEERBTSID=72, PEERBSCIP="172.18.125.124", PEERBSCMASK="255.255.255.255",
PEERBSCID=0, CFGFLAG=NULL, BTSGWIPSWITCH=OFF;
//Configuring BTS routes

//Configuring neighboring cells (Cells 1 and 2046 are both dual-homed

cells.)
//Configuring PTP BVCs

ADD PTPBVC: NSEI=1, BVCI=6, IDTYPE=BYNAME, CELLNAME="cell-11";
//Configuring signaling links over the inter-BSC interface

ADD SCTPLNK: SRN=0, SN=2, SCTPLNKN=0, MODE=CLIENT, APP=BBAP, LOCPN=58000,
LOCIP1="192.3.0.110", LOCIP2="10.161.39.110", PEERIP1="192.3.0.111",
PEERIP2="10.161.39.111", PEERPN=5000, LOGPORTFLAG=NO, VLANFLAG1=DISABLE,
VLANFlAG2=DISABLE, SWITCHBACKFLAG=YES;
//Configuring BSC Node Redundancy

SET GBSCREDGRP: GROUPINDEX=0, CNSTATEPOLICYFORGROUP=AINTFBLOCK,
LocalBSCID=1, PeerBSCID=0;
SET GREDGRPPRIMHOSTPOLICY: REHOSTTYPE=REHOSTDELAY, REHOSTDELAYTIME=60;
ACT GBSCREDGRP: GROUPINDEX=0;
//Activating BSC Node Redundancy

DEA GBSCREDGRP: GROUPINDEX=0;

GBSS14.0
Feature Activation Guide 244 Configuring TC Pool
244 Configuring TC Pool
About This Chapter
TC Pool. The A interface boards of the BSC that supports the TC Pool feature can use only TDM
transmission. The Ater interface boards can use TDM transmission or IP transmission.
244.1 Configuring TC Pool (Ater over TDM)

TC Pool in Ater over TDM transmission mode. (This feature cannot be configured using the
CME. )
244.2 Configuring TC Pool (Ater over IP)
TC Pool in Ater over IP transmission mode. (This feature cannot be configured using the CME. )

GBSS14.0
244.1 Configuring TC Pool (Ater over TDM)

TC Pool in Ater over TDM transmission mode. (This feature cannot be configured using the
CME. )
Prerequisites
– The EIUa/OIUa board is configured, and there are idle ports on the configured EIUa/
OIUa board.
– This feature is mutually exclusive with the features GBFD-118602 A over IP and
l License
– Network Topology
– At least two BSCs are configured in the network. The BM/TC subracks of the two
BSCs are in separated configuration mode and the TC subrack of the two BSCs is
configured remotely.
– The configuration of the clock source is the same for the two BSCs. For details on
the configuration of the clock source, see Configuring the Clocks.
– Initial Data Preparation
– The global data is configured. For details, see Configuring the Global Information.
– The EIUa/OIUa board is configured. For details, see Configuring a Board.
– The BSC clock is configured. For details, see Configuring the Clocks.
Context
l To synchronize the frequency of the GSM network, the primary BSC and secondary BSCs
in a TC pool should use the same clock source. In addition, a BSC can be connected to only
one TC pool. One TC pool supports a maximum of 16 BSCs.
l All TCSs in a TC pool are configured and controlled on the primary BSC. The secondary
BSC is only configured with the BM subrack. The primary BSC and secondary BSCs are
connected to the TCS over the Ater interface, and the TCS is connected to the MSC over
the A interface.
l The settings of TC CRC Allow must be the same on the primary BSC and secondary BSCs.
l If TFO Switch of the secondary BSCs is set to ENABLE(Enable), the TFO setting is
effective only when TFO Option Switch of each TCS is set to ON(On) on the primary
BSC. For details on the setting of TFO, see 51 Configuring TFO.

GBSS14.0
Procedure
1. Configure the Ater interface link for the primary BSC.
a. Run the BSC6900 MML command SET BSCBASIC for the primary BSC. In
this step, set Service mode to SEPARATE(Separate), set Is Support TC
Pool to YES(Yes), set Is Main BSC to YES(Yes), and set Ater Interface
Transfer Mode to TDM(TDM). In addition, specify TC Pool ID.
b. Run the BSC6900 MML command ADD ATERCONPATH for the primary
BSC to add an Ater connection path between the BM subrack and TC subrack.
c. Run the BSC6900 MML command ADD ATEROML for the primary BSC to
add the OML on the Ater interface between the primary BSC and the TCS.
d. Run the BSC6900 MML command ADD ATERCONSL for the primary BSC
to add a signaling link on the Ater interface between the BM subrack of the
primary BSC and TC subrack.
2. Configure the A interface link for the primary BSC.
a. Run the BSC6900 MML command ADD AE1T1 for the primary BSC to add an
E1/T1 link on the A interface. In this step, set BSC Flag to MAINBSC(MAIN
BSC).
b. Run the BSC6900 MML command ADD MTP3LKS for the primary BSC to
add an MTP3 signaling link set. In this step, specify Signalling link set index,
DSP index, and Signalling link set name.
c. Run the BSC6900 MML command ADD MTP3LNK for the primary BSC to
add an MTP3 signaling link.
d. Run the BSC6900 MML command ADD MTP3RT for the primary BSC to add
an MTP3 signaling route.
NOTE
The TCSs are configured on the primary BSC. When you add MTP3 links to the primary
BSC, MTP2 links are automatically added to the primary BSC.
3. Configure the Ater interface link for the secondary BSC.
a. Run the BSC6900 MML command SET BSCBASIC for the secondary BSC. In
Pool to YES(Yes), set Is Main BSC to NO(No), and set Ater Interface
Transfer Mode to TDM(TDM). In addition, specify TC Pool ID and ID of a
BSC in TC Pool.
b. Run the BSC6900 MML command ADD ATERE1T1 for the secondary BSC
to add an Ater connection path on the BM side. In this step, set BM/TC config
flag to CFGBM(BM).
c. Run the BSC6900 MML command ADD ATERE1T1 for the primary BSC to
add an Ater connection path on the TC side. In this step, set BM/TC config
flag to CFGTC(TC), and set BSC ID in the TC pool to the ID of the secondary
BSC specified in 3.1.
d. Run the BSC6900 MML command ADD ATERSL for the secondary BSC to
add an Ater signaling link on the BM side. In this step, set BM/TC config flag
to CFGBM(BM).
e. Run the BSC6900 MML command ADD ATERSL for the primary BSC to add
an Ater signaling link on the TC side. In this step, set BM/TC config flag to

GBSS14.0
CFGTC(TC), and set BSC ID in the TC pool to the ID of the secondary BSC
specified in 3.1.
4. Configure the A interface link for the secondary BSC.
A interface E1/T1 link to the secondary BSC. In this step, set BSC Flag to
SUBBSC(SUB BSC), and set ID of slave BSC in TC Pool to the ID of the
secondary BSC specified in 3.1.
b. Run the BSC6900 MML command ADD MTP3LKS for the secondary BSC to
c. Run the BSC6900 MML command ADD MTP3LNK for the secondary BSC to
d. Run the BSC6900 MML command ADD MTP3RT for the secondary BSC to
add an MTP3 signaling route.
NOTE
The MTP2 links cannot be automatically added with the addition of the MTP3 links,
because the secondary BSC is not configured with the TCS.
e. Run the BSC6900 MML command ADD SEMILINK for the primary BSC to
add an MTP2 link to the secondary BSC. In this step, set Application Type to
MTP2(MTP2), and set BSC ID in the TC pool to the ID of the secondary BSC
specified in 3.1. In addition, specify Semipermanent Link Rate.
1. In a cell under the primary BSC, use the MS to perform voice services.
2. Run the BSC6900 MML command DSP ACIC. In this step, set OPC Index and DPC
Group No to those of the primary BSC, set Query mode to BYDPC (BY DPC
Group), set CIC state to OCCUPIED(OCCUPIED), and set BSC Flag to
MAINBSC(MAIN BSC).
Expected result: The occupied CICs are displayed and the primary BSC works
properly.
3. In a cell under a secondary BSC, use the MS to perform voice services.
Group No to those of the secondary BSC, set Query mode to BYDPC (BY DPC
Group), set CIC state to OCCUPIED(OCCUPIED), and set BSC Flag to SUBBSC
(SUB BSC). In addition, specify BSC ID in the TC pool.
Expected result: The occupied CICs are displayed and the secondary BSC works
properly.
1. Run the BSC6900 MML command SET BSCBASIC for the primary BSC. In this
step, set Is Support TC Pool to NO(No).
2. Run the BSC6900 MML command SET BSCBASIC for the secondary BSC. In this
----End
Example
l Configuration on the primary BSC
//Setting the TC Pool and the transmission mode on the Ater interface
SET BSCBASIC: ServiceMode=SEPARATE, IsSupportTcPool=YES,

GBSS14.0
IsMainBSC=YES, TCPOOLID=0,ATERTRANSMODE=TDM;
//Configuring the Ater conpath or the Ater OML
ADD ATERCONPATH: ATERIDX=1, BMSRN=0, BMSN=14, BMPN=1, TCSRN=3,
TCSN=14, TCPN=1;
TSMASK=TS1-0&TS2-1&TS3-1&TS4-1&TS5-1&TS6-1&TS7-1&TS8-1&TS9-0&TS10-0&T
S11-0&TS12-0&TS13-0&TS14-0&TS15-0&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&TS30-0
&TS31-0;
ATERMASK=TS1-1&TS2-0&TS3-0&TS4-0&TS5-0&TS6-0&TS7-0&TS8-0&TS9-0&TS10-0
&TS11-0&TS12-0&TS13-0&TS14-0&TS15-0&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&TS30
-0&TS31-0;
//Configuring the A E1/T1 on the primary BSC
ADD MTP3LKS: SIGLKSX=0, DPX=1, LNKSLSMASK=B0001, EMERGENCY=OFF,
NAME="BM1";
TCMODE=SEPERATE_PRINCIPAL, ATERIDX=1,
-0&TS31-0, ASRN=3, ASN=16, MTP2LNKN=0, APN=0,
ATSMASK=TS1-1&TS2-1&TS3-1&TS4-1&TS5-1&TS6-1&TS7-1&TS8-1&TS9-1&TS10-1&
1&TS31-1, LKTATE=64K, NAME="BM1";
ADD MTP3RT: DPX=1, SIGLKSX=0, NAME="BM1";
//Configuring the Ater E1T1 on the TC side for the secondary BSC
ADD ATERE1T1: BTCFLAG=CFGTC, BSCTID=1, ATERIDX=1, SRN=3, SN=20, PN=0;
//Configuring the Ater RSL on the TC side for the secondary BSC
ADD ATERSL: BTCFLAG=CFGTC, BSCTID=1, ATERIDX=2,
-0&TS31-0, TNMODE=TRRS;
//Configuring the A E1/T1 for the secondary BSC
BSCFLAG=SUBBSC, SUBBSCTID=1, STCIC=0;
//congfiguring the semilink for the secondary BSC
ADD SEMILINK: IDX=0, APPTYPE=MTP2, LNKRATE=64K, BSCTID=1, ATERIDX=2,
INMASK=TS1-1&TS2-1&TS3-1&TS4-1&TS5-1&TS6-1&TS7-1&TS8-1&TS9-1&TS10-1&T
&TS31-1, OUTSRN=3, OUTSN=3, OUTPN=16,
OUTMASK=TS1-1&TS2-1&TS3-1&TS4-1&TS5-1&TS6-1&TS7-1&TS8-1&TS9-1&TS10-1&
1&TS31-1;
l Configuration on the secondary BSC
//Setting the TC Pool and the transmission on the Ater interface
IsMainBSC=NO, BSCTID=1, TCPOOLID=0, ATERTRANSMODE=TDM;
//Configuring the Ater E1/T1 on the BM side for the secondary BSC
ADD ATERE1T1: BTCFLAG=CFGBM, ATERIDX=2, SRN=0, SN=16, PN=0;
//Configuring the Ater RSL on the BM side for the secondary BSC
ADD ATERSL: BTCFLAG=CFGBM, ATERIDX=2,

GBSS14.0
//Configuring the MTP3 links for the secondary BSC
ADD MTP3LKS: SIGLKSX=1, DPX=2, NAME="BM2";
TCMODE=SEPERATE_SUBORDINATE, ATERIDX=1,
244.2 Configuring TC Pool (Ater over IP)

TC Pool in Ater over IP transmission mode. (This feature cannot be configured using the CME. )
Prerequisites
– The EIUa/OIUa/POUc board is configured, and there are idle ports on the configured
EIUa/OIUa/POUc board.
– This feature is mutually exclusive to features GBFD-118602 A over IP and
l License
– Network Topology
– At least two BSCs are configured in the network. The BM/TC subracks of the two
BSCs are in separated configuration mode and the TC subrack of the two BSCs is
configured remotely.
– The configuration of the clock source is the same for the two BSCs. For details on
the configuration of the clock source, see Configuring the Clocks.
– Initial Data Preparation
– The global data is configured. For details, see Configuring the Global Information.
– The EIUa/OIUa/POUc board is configured. For details, see Configuring a Board.
– The BSC clock is configured. For details, see Configuring the Clocks.
Context
l To synchronize the frequency of the GSM network, the primary BSC and secondary BSCs
in a TC pool should use the same clock source. In addition, a BSC can be connected to only
one TC pool. One TC pool supports a maximum of 16 BSCs.

GBSS14.0
l All TCSs in a TC pool are configured and controlled on the primary BSC. The secondary
BSC is only configured with the BM subrack. The primary BSC and secondary BSCs are
connected to the TCS over the Ater interface, and the TCS is connected to the MSC over
the A interface.
l The settings of TC CRC Allow must be the same on the primary BSC and secondary BSCs.
l If TFO Switch of the secondary BSCs is set to ENABLE(Enable), the TFO setting is
effective only when TFO Option Switch of each TCS is set to ON(On) on the primary
BSC. For details on the setting of TFO, see 51 Configuring TFO.
Procedure
1. Configure the Ater interface link for the primary BSC.
a. Run the BSC6900 MML command SET BSCBASIC for the primary BSC. In
Pool to YES(Yes), set Is Main BSC to YES(Yes), and set Ater Interface
Transfer Mode to TDM(TDM). In addition, specify TC Pool ID.
b. Run the BSC6900 MML command ADD ATERCONPATH for the primary
BSC to add an Ater connection path between the BM subrack and TC subrack.
c. Run the BSC6900 MML command ADD ATEROML for the primary BSC to
add the OML on the Ater interface between the primary BSC and the TCS.
d. Run the BSC6900 MML command ADD ATERCONSL for the primary BSC
to add a signaling link on the Ater interface between the BM subrack of the
primary BSC and TC subrack.
e. Determine the type of link carried on the E1/T1 link (PPP link or MLPPP link
group).
– Add PPP link data.
a. Run the BSC6900 MML command ADD PPPLNK for the primary
BSC. In this step, set Slot No to the number of the slot that houses the
IP interface board in the BM subrack.
b. Run the BSC6900 MML command ADD PPPLNK for the primary
BSC. In this step, set Slot No to the number of the slot that houses the
IP interface board in the TC subrack.
NOTE
You can perform the preceding operation to add only one PPP link at a time. If
multiple PPP links are to be added, you need to perform the preceding operation
repeatedly.
– Add MLPPP group data.
a. Run the BSC6900 MML command ADD MPGRP for the primary BSC.
In this step, set Slot No to the number of the slot that houses the IP
interface board in the BM subrack.
b. Run the BSC6900 MML command ADD MPGRP for the primary BSC.
In this step, set Slot No to the number of the slot that houses the IP
interface board in the TC subrack.

GBSS14.0
NOTE
You can perform the preceding operation to add only one MLPPP group at a time.
If multiple MLPPP groups are to be added, you need to perform the preceding
operation repeatedly.
f. Run the BSC6900 MML command ADD ADJNODE for the primary BSC to
add an Ater interface adjacent node on the BM side. In this step, set Adjacent
Node Type to BSC(Ater Interface on BSC). In addition, specify BSC ID.
g. Run the BSC6900 MML command ADD ADJNODE for the primary BSC to
add an Ater interface adjacent node on the TC side. In this step, set Adjacent
Node Type to TC(Ater Interface on TC).
h. Run the BSC6900 MML command ADD IPPATH for the primary BSC. In this
step, set Adjacent Node ID to the ID of the adjacent node on the BM side. In
addition, set Interface Type to ATER(ATER Interface).
i. Run the BSC6900 MML command ADD IPPATH for the primary BSC. In this
step, set Adjacent node ID to the ID of the adjacent node on the TC side. In
addition, set Interface Type to ATER(ATER Interface).
2. Configure the A interface link for the primary BSC.
E1/T1 link on the A interface. In this step, set BSC Flag to MAINBSC(MAIN
BSC).
b. Run the BSC6900 MML command ADD MTP3LKS for the primary BSC to
c. Run the BSC6900 MML command ADD MTP3LNK for the primary BSC to
d. Run the BSC6900 MML command ADD MTP3RT for the primary BSC to add
an MTP3 signaling route.
NOTE
The TCSs are configured on the primary BSC. When you add MTP3 links to the primary
BSC, MTP2 links are automatically added to the primary BSC.
3. Configure the Ater interface link for the secondary BSC.
a. Run the BSC6900 MML command SET BSCBASIC for the secondary BSC. In
Pool to YES(Yes), set Is Main BSC to NO(No), and set Ater Interface
Transfer Mode to TDM(TDM). In addition, specify TC Pool ID and ID of a
BSC in TC Pool.
b. Run the BSC6900 MML command ADD ATERE1T1 for the secondary BSC
to add an E1/T1 link on the Ater interface on the BM side. In this step, set BM/
TC config flag to CFGBM(BM).
c. Run the BSC6900 MML command ADD ATERE1T1 for the primary BSC to
add an E1/T1 link on the Ater interface on the TC side. In this step, set BM/TC
config flag to CFGTC(TC). In addition, specify BSC ID in the TC pool.
d. Run the BSC6900 MML command ADD ATERSL for the secondary BSC to
add an Ater signaling link on the BM side. In this step, set BM/TC config flag
to CFGBM(BM).

GBSS14.0
e. Run the BSC6900 MML command ADD ATERSL for the primary BSC to add
an Ater signaling link on the TC side. In this step, set BM/TC config flag to
CFGTC(TC). In addition, specify BSC ID in the TC pool.
f. Determine the type of link carried on the E1/T1 link (PPP link or MLPPP link
group).
– Add PPP link data.
a. Run the BSC6900 MML command ADD PPPLNK for the secondary
BSC to add a PPP link on the BM side. In this step, set Slot No to the
number of the slot that houses the IP interface board in the BM subrack.
b. Run the BSC6900 MML command ADD PPPLNK for the primary BSC
to add a PPP link on the TC side. In this step, set Slot No to the number
of the slot that houses the IP interface board in the TCS.
– Add MLPPP group data.
a. Run the BSC6900 MML command ADD MPGRP for the secondary
BSC to add an MLPPP group on the BM side. In this step, set Slot No
to the number of the slot that houses the IP interface board in the BM
subrack.
b. Run the BSC6900 MML command ADD MPGRP for the primary BSC
to add an MLPPP group on the TC side. In this step, set Slot No to the
number of the slot that houses the IP interface board in the TCS.
c. Run the BSC6900 MML command ADD MPLNK for the secondary
BSC to add an MLPPP link on the BM side. In this step, set Slot No to
the number of the slot that houses the IP interface board in the BM
subrack.
d. Run the BSC6900 MML command ADD MPLNK for the primary BSC
to add an MLPPP link on the TC side. In this step, set Slot No to the
number of the slot that houses the IP interface board in the TC subrack.
g. Run the BSC6900 MML command ADD ADJNODE for the secondary BSC to
add an Ater interface adjacent node on the BM side. In this step, set Adjacent
Node Type to BSC(Ater Interface on BSC). In addition, specify BSC ID.
h. Run the BSC6900 MML command ADD ADJNODE for the primary BSC to
add an Ater interface adjacent node on the TC side. In this step, set Adjacent
Node Type to TC(Ater Interface on TC).
i. Run the BSC6900 MML command ADD IPPATH for the secondary BSC to
add an IP path on the BM side. In this step, set Adjacent node ID to the ID of
the adjacent node on the BM side. In addition, set Interface Type to ATER
(ATER Interface).
j. Run the BSC6900 MML command ADD IPPATH for the primary BSC to add
an IP path on the TC side. In this step, set Adjacent node ID to the ID of the
adjacent node on the TC side. In addition, set Interface Type to ATER(ATER
Interface).
4. Configure the A interface link for the secondary BSC.
A interface E1/T1 link to the secondary BSC. In this step, set BSC Flag to
SUBBSC(SUB BSC). In addition, specify ID of slave BSC in TC Pool.

GBSS14.0
b. Run the BSC6900 MML command ADD MTP3LKS for the secondary BSC to
c. Run the BSC6900 MML command ADD MTP3LNK for the secondary BSC to
d. Run the BSC6900 MML command ADD MTP3RT for the secondary BSC to
add an MTP3 signaling route.
NOTE
The MTP2 links cannot be automatically added with the addition of the MTP3 links,
because the secondary BSC is not configured with the TCS.
e. Run the BSC6900 MML command ADD SEMILINK for the primary BSC to
add an MTP2 link to the secondary BSC. In this step, set Application Type to
MTP2(MTP2). In addition, specify Semipermanent Link Rate and BSC ID
in the TC pool.
1. In a cell under the primary BSC, use the MS to perform voice services.
Group No to those of the primary BSC, set Query mode to BYDPC (BY DPC
Group), set CIC state to OCCUPIED(OCCUPIED), and set BSC Flag to
MAINBSC(MAIN BSC).
Expected result: The occupied CICs are displayed and the primary BSC works
properly.
3. In a cell under a secondary BSC, use the MS to perform voice services.
Group No to those of the secondary BSC, set Query mode to BYDPC (BY DPC
Group), set CIC state to OCCUPIED(OCCUPIED), and set BSC Flag to SUBBSC
(SUB BSC). In addition, specify BSC ID in the TC pool.
Expected result: The occupied CICs are displayed and the secondary BSC works
properly.
1. Run the BSC6900 MML command SET BSCBASIC for the primary BSC. In this
2. Run the BSC6900 MML command SET BSCBASIC for the secondary BSC. In this
----End
Example
l Configuration on the primary BSC
//Setting the TC Pool and the transmission mode on the Ater interface
IsMainBSC=YES, TCPOOLID=0,ATERTRANSMODE=IP;
//Configuring the Ater conpath on the primary BSC
ADD ATERCONPATH: ATERIDX=1, BMSRN=0, BMSN=14, BMPN=1, TCSRN=3,
TCSN=14, TCPN=1;
//Configuring the Ater OML on the primary BSC
TSMASK=TS1-0&TS2-1&TS3-1&TS4-1&TS5-1&TS6-1&TS7-1&TS8-1&TS9-0&TS10-0&T

GBSS14.0
&TS31-0;
//Configuring the Ater CONSL ont the primary BSC
-0&TS31-0;
//Configuring the Ater PPPlink on the BM side for the primary BSC
TSBITMAP=TS1-1&TS2-1&TS3-1&TS4-1&TS5-1&TS6-1&TS7-1&TS8-1&TS9-1&TS10-1
-1&TS31-1, BORROWDEVIP=No, LOCALIP="1.1.1.1", MASK="255.255.255.0",
PEERIP="1.1.1.2", IPHC=No_HC, PFC=Disable, ACFC=Disable,
PPPMUX=Disable, AUTHTYPE=NO_V, FLOWCTRLSWITCH=ON, ERRDETECTSW=OFF;
//Configuring the Ater PPPlink on the TC side for the primary BSC
//Configuring the Adjnode ong the BM side for the primary BSC
ADD ADJNODE: ANI=0, NAME="adjnode0", NODET=BSC, BSCID=0;
//Configuring the Adjnode ong the TC side for the primary BSC
//Configuring the Ater IPPATH on the BM side for the primary BSC
PATHCHK=DISABLED;
//Configuring the Ater IPPATH on the TC side for the primary BSC
PATHCHK=DISABLED;
//Configuring the A E1/T1 on the primary BSC
//Configuring the MTP3 links on the primary BSC
ADD MTP3LKS: SIGLKSX=0, DPX=1, LNKSLSMASK=B0001, EMERGENCY=OFF,
NAME="BM1";
//Configuring the MTP3 link on the primary BSC
TCMODE=SEPERATE_PRINCIPAL, ATERIDX=1,
//Configuring the MTP3 route on the primary BSC
//Configuring the Ater E1/T1 on the TC side for the secondary BSC
ADD ATERE1T1: BTCFLAG=CFGTC, BSCTID=1, ATERIDX=1, SRN=3, SN=20, PN=0;
//Configuring the Ater RSL on the TC side for the secondary BSC
ADD ATERSL: BTCFLAG=CFGTC, BSCTID=1, ATERIDX=2,

GBSS14.0
//Configuring the Ater PPPLink on the TC side for secondary BSC

//Configuring the adjnode on the TC side for the secondary BSC
//Configuring the Ater IPPATH on the TC side for the secondary BSC
PATHCHK=DISABLED;
//Configuring the A E1/T1 on the secondary BSC
BSCFLAG=SUBBSC, SUBBSCTID=1, STCIC=0;
//Configuring the semilink for the secondary BSC
ADD SEMILINK: IDX=0, APPTYPE=MTP2, LNKRATE=64K, BSCTID=1, ATERIDX=2,
INMASK=TS1-1&TS2-1&TS3-1&TS4-1&TS5-1&TS6-1&TS7-1&TS8-1&TS9-1&TS10-1&T
&TS31-1, OUTSRN=3, OUTSN=3, OUTPN=16,
OUTMASK=TS1-1&TS2-1&TS3-1&TS4-1&TS5-1&TS6-1&TS7-1&TS8-1&TS9-1&TS10-1&
1&TS31-1;
l Configuration on the secondary BSC
//Setting the TC Pool and the transmission on the Ater interface
IsMainBSC=NO, BSCTID=1, TCPOOLID=0, ATERTRANSMODE=TDM;
//Configuring the Ater E1/T1 on the BM side for the secondary BSC
ADD ATERE1T1: BTCFLAG=CFGBM, ATERIDX=2, SRN=0, SN=16, PN=0;
//Configuring the Ater RSL on the BM side for the secondary BSC
ADD ATERSL: BTCFLAG=CFGBM, ATERIDX=2,
//Configuring the Ater PPPLink on the BM side for the secondary BSC
//Configuring the adjnode on the BM side for the secondary BSC
ADD ADJNODE: ANI=1, NAME="adjnode1", NODET=BSC;
//Configuring the Ater IPPATH on the BM side for the secondary BSC
PATHCHK=DISABLED;
//Configuring the MTP3 links on the secondary BSC
ADD MTP3LKS: SIGLKSX=1, DPX=2, NAME="BM2";
//Configuring the MTP3 link on the secondary BSC
TCMODE=SEPERATE_SUBORDINATE, ATERIDX=1,

GBSS14.0

//Configuring the MTP3 route on the secondary BSC

GBSS14.0
Feature Activation Guide 245 Configuring OML Backup
OML Backup. When the operation and maintenance link (OML) backup function of the BTS is
enabled, the BTS automatically switches to anther port to set up an OML if the established OML
is disconnected, thereby reducing service interruption duration.
Prerequisites
– The BTS3900B, BTS3900E, and BTS3X series base station do not support this feature.
– This feature cannot be used together with the feature GBFD-117801 Ring Topology,
GBFD-116601 Abis Bypass, GBFD-118601 Abis over IP, GBFD-118611 Abis IP over
E1/T1, or GBFD-118401 Abis Transmission Optimization.
– When this feature is enabled simultaneously with the GBFD-113801 TRX Mutual Aid
feature:
– The value of Flex Abis Mode of the BTS must be set to FLEX_ABIS(Flex Abis).
– TRX mutual aid is triggered by the active link. The static PDTCH on the active link
is unavailable due to transmission faults. Therefore, you are advised to change the
static PDTCH to dynamic PDTCH.
l License

GBSS14.0
CAUTION
l The BTS in TDM or HDLC transmission mode supports this feature. The BTS in IP
transmission mode does not support this feature.
l OMLs on ports 0 and 1 of the BTS basic cabinet group support this feature. OMLs on other
ports of the basic cabinet group and OMLs of the main and extension cabinet groups do not
support this feature.
l The active and standby OMLs between the BSC and the BTS must not be carried by the same
E1/T1 cable, including the same E1/T1 cable of an upper-level BTS. When the upper-level
BTS is connected to the BSC by using only one E1/T1 cable and the lower-level BTS requires
the OML backup function, a secondary link must be added to directly connect the upper-
level BTS or lower-level BTS to the BSC.
Context
l If the OML between the BSC and the BTS fails, the BTS cannot work. The OML Backup
feature allows a pair of OMLs to be configured on two independent E1 cables (one for
each). When the active OML is faulty, the BTS uses the standby OML. This prevents the
BTS and cells from being out of service due to transmission failures or port failures.
l When this feature is used, one OML is configured on ports 0 and 1 of the BTS, respectively.
After the BTS is reset, it attempts to establish OMLs on the two ports in turn. If the BTS
establishes an OML on a port, it always uses the OML on this port unless the BTS is reset
or the OML is disconnected. When the established OML is broken, the BTS attempts to
establish an OML on another port. If the OML is established successfully, the BSC triggers
an OML switchover procedure.
l After the OML switchover, the RSL, TCH, idle timeslot, and monitoring timeslot are not
switched over. That is, for ports 0 and 1, if the transmission link or port where the active
OML is located is faulty, all TRX channels, idle timeslots, and monitoring timeslots
configured on this port become unavailable. The TRX channels, idle timeslots, and
monitoring timeslots on a normal port, however, are still available. Therefore, cells under
the BTS continue to provide services.
Procedure
2. Run the BSC6900 MML command SET BTSOMLBACKUP (CME single
configuration: BTS Configuration Express > BTS Extend Attributes > The
Information on the Active/Standby Switchover of the OML; CME batch
modification center: not supported). In this step, set Configure Backup OML to YES
(Yes) and set Wait Time before OML Switch and Try Switching Duration Time
to appropriate values.
3. Optional: Adjust the timeslot used by the active and standby OMLs of the BTS.

GBSS14.0
NOTE
l The active and standby OMLs configured on ports 0 and 1 of the BTS must use the same timeslot.
l The BTS must be one of 3012 or 3900 series base stations (excluding BTS3900B and
BTS3900E).
l The BTS works in TDM transmission mode.
a. Run the BSC6900 MML command SET BTSOMLDETECT (CME single

configuration: BTS Configuration Express > BTS Extend Attributes > BTS
OML Timeslot Detection Function; CME batch modification center: not
supported). In this step, set Whether to Enable OML Detection to OMLDET
(OML timeslot automatic detection) and BTS Bar Code to an appropriate
value.
b. Run the BSC6900 MML command SET BTSOMLTS (CME single
configuration: BTS Topology > Right click BTS > TimeSlot Management >
OML Timeslot; CME batch modification center: not supported) to specify the
timeslot used by the active and standby OMLs of the BTS.
1. Run the BSC6900 MML command LST BTSOMLBACKUP to query the value of
Configure Backup OML.
Expected result: Configure Backup OML is set to Yes, and other parameters are set
based on configurations.
2. Run the BSC6900 MML command SET BTSOMLBACKUP (CME single
configuration: BTS Configuration Express > BTS Extend Attributes > The
Information on the Active/Standby Switchover of the OML; CME batch
modification center: not supported). In this step, set Configure Backup OML to NO
(No).
----End
Example
//Activating OML Backup DEA BTS: IDTYPE=BYID, BTSID=0; SET BTSOMLBACKUP:
IDTYPE=BYID, BTSID=0, OMLBKUP=YES, WTBS=30, TBS=30; ACT BTS: IDTYPE=BYID,
BTSID=0;
//Verifying OML Backup LST BTSOMLBACKUP: IDTYPE=BYID,
BTSID=0;
//Deactivating OML Backup DEA BTS: IDTYPE=BYID,
BTSID=0; SET BTSOMLBACKUP: IDTYPE=BYID, BTSID=0, OMLBKUP=NO; ACT BTS:
IDTYPE=BYID, BTSID=0;

GBSS14.0
Feature Activation Guide 246 Configuring Access Control Class
246 Configuring Access Control Class
Access Control Class (ACC).
Prerequisites
l License
– The MS and its SIM card meet the ACC-related requirements specified by the protocols.
Context
This feature enables special users and some common users to access the network preferentially
when the network traffic is excessively high.
When the ACC feature is enabled, the MS checks the access control class set in the SIM card
based on the access control class included in the cell broadcast message. If the access control
class is an allowed one, the MS can preempt the RACH to access the network. If the access
control class is a forbidden one, the MS cannot access the network.
Procedure
1. Run the BSC6900 MML command ADD BSCACCCTRLP (CME single
Access Control Policy; CME batch modification center: 3.17 Modifying GBSC
Parameters in Batches) with Access Control Policy Index, Access Control
Window Size, Starting Point of the Access Control Window, and Sliding Speed
of the Access Control Window set as required.

GBSS14.0
Feature Activation Guide 246 Configuring Access Control Class
NOTE
A maximum of 32 access control policies can be set. You can run the command in Step 1 for
multiple times to set multiple access control policies.
When the Access Control Policy is enabled and the system message is sent by the BSC, the
access of the MSs of classes 10 to 15 is not affected regardless of the Access Control Policy
configuration.
Parameters in Batches) with Access Control Allowed set to YES(Yes) and Access
Control Policy to the value of Access Control Policy Index specified in Step 1.
1. Run the BSC6900 MML command LST GCELLCCBASIC.
Expected result: Access Control Allowed is set to YES(Yes), and Access Control
Policy is specified.
2. Run the BSC6900 MML command LST BSCACCCTRLP.
Expected result: The values of Access Control Window Size, Starting Point of the
Access Control Window, and Sliding Speed of the Access Control Window are
those specified during configuration.
NOTE
The access-control-class in the RACH Control Parameters IE is called the ACC field. The ACC
field contains two octets and is 16 bits in length. Each bit indicates a level of the SIM users
and its value is 0 or 1. When a bit is 0, the SIM users of a certain level are allowed to access
the network. When a bit is 1, the SIM users of a certain level are forbidden to access the network.
Expected result: The Information Element (IE) RACH Control Parameters is included
in the system message, and within the sliding window range the value of the bits in
the ACC field of the RACH Control Parameters is 1 from the starting point onwards.
4. When an MS is used to make a call in the period specified in Step 1, the MS cannot
access the network if the level of the SIM card of the MS belongs to the forbidden
levels. If the level of the SIM card does not belong to the forbidden levels, the MS
can access the network normally.
Parameters in Batches) with Access Control Allowed to NO(No) so that the ACC
feature in a cell is deactivated.
----End
Example
//Activating ACC
ADD BSCACCCTRLP: ACCINDEX=0;
SET GCELLCCBASIC: IDTYPE=BYID, CELLID=0, ACCCTRLEN=YES, ACCCTRLPY=0;
//Deactivating ACC
SET GCELLCCBASIC: IDTYPE=BYID, CELLID=0, ACCCTRLEN=NO;

GBSS14.0
Feature Activation Guide 247 Configuring Adaptive Transmission Link Blocking
247 Configuring Adaptive Transmission

Link Blocking
Adaptive Transmission Link Blocking.
Prerequisites
– The BSC6900 has been configured with an POUc, OIUa, or EIUa board that supports
TDM transmission.
l License
Context
The transmission quality, especially the quality of microwave transmission, is vulnerable to bad
weather, leading to degraded service quality and increased call drop rate. To prevent this
problem, the BSC monitors transmission quality in real time. The BSC automatically blocks an
E1 link if the transmission quality of the E1 link is lower than the specified threshold. After
being blocked, the E1 link carries no service. After the transmission quality of the E1 link
becomes desirable, the BSC unblocks the link. After being unblocked, the E1 link carries
services.
WARNING
This feature blocks an E1/T1 adaptively, leading to service interruption on the E1/T1.

GBSS14.0
Procedure
1. Run the BSC6900 MML command SET E1T1 (CME single configuration: Device
Panel > Board > E1/T1 Port Parameters; CME batch modification center: not
supported) with High BER Auto Isolation Switch set to ON(ON) and High BER
Auto Isolation Threshold set to O1E3_R5E4(OCCUR:1E3, RECOVERY:5E4)
on the POUc/OIUa/EIUa board.
2. Run the BSC6900 MML command SET BTSE1T1BER (CME single configuration:
BTS Configuration Express > BTS Basic Attributes > BTS E1/T1 BER
Threshold; CME batch modification center: not supported) with BER OOS Switch
set to ON(ON) and BER OOS Threshold set to O1E3_R5E4(OCCUR:1E3,
RECOVERY:5E4).
NOTE
Step 1 and Step 2 uses an example for your reference only. Set High BER Auto Isolation
Threshold and BER OOS Threshold based on the field configuration.
1. Run the BSC6900 MML command LST E1T1 to query High BER Auto Isolation
Switch and High BER Auto Isolation Threshold.
Expected result: High BER Auto Isolation Switch is ON(ON) and High BER Auto
Isolation Threshold is the same as that set in the activation procedure.
2. Run the BSC6900 MML command LST BTSE1T1BER to query BER OOS
Switch and BER OOS Threshold.
Expected result: BER OOS Switch is ON(ON) and BER OOS Threshold is the same
as that set in the activation procedure.
3. Use the MS to make a call and wait for BER.
Expected result: The BER is higher than 1E-3.
4. Log in to the LMT or M2000 to view the alarms reported in real time.
Expected result: An ALM-21207 E1/T1 Excessive Bit Error Rate alarm is reported
with the cause value of BER within one minute exceeds the allowed limit. After 10
seconds the alarm is reported, ongoing services are interrupted.
1. Run the BSC6900 MML command SET E1T1 (CME single configuration: Device
Panel > Board > E1/T1 Port Parameters; CME batch modification center: not
supported) with High BER Auto Isolation Switch set to OFF(OFF).
2. Run the BSC6900 MML command SET BTSE1T1BER (CME single configuration:
BTS Configuration Express > BTS Basic Attributes > BTS E1/T1 BER
Threshold; CME batch modification center: not supported) with BER OOS Switch
set to OFF(OFF).
----End
Example
//Configuring the switch and threshold for blocking an E1 link when the
BER exceeds the specified threshold for BSC
SET E1T1: SRN=0, SN=14, BT=OIUa, PS=SINGLE, PN=3, BERAUTOISOSW=ON,
BERAUTOISOTHRD=O1E3_R5E4;

GBSS14.0
//Configuring the switch and threshold for blocking an E1 link when the
BER exceeds the specified threshold for BTS
SET BTSE1T1BER: IDTYPE=BYID, BTSID=1, BEROOSSwitch=ON,
BEROOSTHD=O1E3_R5E4;
//Turning off the switch for blocking an E1 link when the BER exceeds the
specified threshold for BSC
SET E1T1: SRN=0, SN=14, BT=OIUa, PS=SINGLE, PN=3, BERAUTOISOSW=OFF;
//Turning off the switch for blocking an E1 link when the BER exceeds the
specified threshold for BTS
SET BTSE1T1BER: IDTYPE=BYID, BTSID=1, BEROOSSwitch=OFF;

GBSS14.0
Feature Activation Guide 248 Configuring Semi-Permanent Connection
248 Configuring Semi-Permanent

Connection
Semi-Permanent Connection.
Prerequisites
l License
Context
After a semi-permanent connection is configured, the information received by the E1 timeslot
at the receiving end is exchanged to an E1 timeslot at the transmitting end by the internal timeslot
switching function of the BSC. In this way, the collected information is transparently transmitted
in the BSC.
Huawei BSS supports two types of semi-permanent connection:
l Semi-permanent link
The input and output of a semi-permanent link are located at the BSC interface board. In
this case, the BSC performs timeslot switching between the input timeslot and the output
timeslot.
l Monitoring timeslot
One end of the channel associated with a monitoring timeslot is a BTS port, and the other
end of the channel is a BSC interface board. In this case, the BTS and the BSC together
perform timeslot switching.

GBSS14.0
Procedure
– Activating a semi-permanent link
1. Run the BSC6900 MML command ADD SEMILINK (CME single configuration:
Semipermanent Link; CME batch modification center: not supported) to add a
semi-permanent link in the BSC. In this step, set Application Type to OTHER
(OTHER) and Semipermanent Link Rate to an appropriate value as required.
NOTE
In BSC Start Timeslot No. and Out BSC Start Timeslot No. need to be set based on network
planning. Ensure that the associated timeslots are not occupied.
– Activating a monitoring timeslot
1. Run the BSC6900 MML command ADD BTSMONITORTS (CME single
Monitoring Timeslot; CME batch modification center: not supported) to add a
monitoring timeslot. In this step, set Time Slot Rate to an appropriate value based
on the site requirements.
NOTE
If the transmission mode of a BTS is IP over FE/GE, the BTS does not monitoring timeslots.
– Verifying a semipermanent link
1. Run the BSC6900 MML command DSP SEMILINK to query the state of a semi-
permanent link.
Expected result: The value of State is OK.
– Verifying a monitoring timeslot
1. Run the BSC6900 MML command LST BTSMONITORTS to query the state of
a monitoring timeslot.
Expected result: The information about the monitoring timeslot is displayed.
– Deactivating a semi-permanent link
1. Run the BSC6900 MML command RMV SEMILINK (CME single
Configuration > Semipermanent Link; CME batch modification center: not
supported) to remove a semi-permanent link.
– Deactivating a monitoring timeslot
1. Run the BSC6900 MML command RMV BTSMONITORTS (CME single
Monitoring Timeslot; CME batch modification center: not supported) to remove
a monitoring timeslot from a BTS.
----End

GBSS14.0
Example
//Activating a semi-permanent link
ADD SEMILINK: IDX=0, APPTYPE=OTHER, LNKRATE=16K, INSRN=1, INSN=14,
INPN=0, INTSN=10, OUTSRN=1, OUTSN=14, OUTPN=2, OUTTSN=20;
//Activating a monitoring timeslot
ADD BTSMONITORTS: IDTYPE=BYID, BTSID=1, TSRATE=16K, BSCSRN=0, BSCSN=26,
BSCPN=6, BSCTS=10, BSCSUBTS=6, STPN=7, STCN=0, STSRN=0, STSN=6, STTS=10,
STSUBTS=2;
//Verifying a semipermanent link
DSP SEMILINK: IDX=0;
//Verifying a monitoring timeslot
LST BTSMONITORTS: IDTYPE=BYID, BTSID=1, TSIDX=0;
//Deactivating a semi-permanent link
RMV SEMILINK: IDX=0;
//Deactivating a monitoring timeslot
RMV BTSMONITORTS: IDTYPE=BYID, BTSID=1, TSIDX=0;

GBSS14.0
Feature Activation Guide 249 Configuring End-to-End MS Signaling Tracing
249 Configuring End-to-End MS

Signaling Tracing
End-to-End MS Signaling Tracing.
Prerequisites
– This feature requires support from the MSC and M2000.
l License
– This feature requires support from the MSC.
– The M2000 feature WOFD-190600 GBSS Enhanced Subscriber Tracing and
WOFD-191400 G&U CS Subscriber Tracing have been enalbed.
Context
The end-to-end MS signaling tracing function creates or removes a user tracing task in the HLR.
The HLR sends a tracing activation message to the MSC or VLR where the MS is located. When
the traced MS requests services, the MSC instructs the BSC to start user tracing. After the MS
moves to another MSC and initiates location update, the HLR sends a new tracing activation
message to the new VLR. The original user tracing task ends.
By using the end-to-end MS signaling tracing function, the system can collect information about
a specified MS when required. This function occupies a small number of system resources. By
recording the signaling about an MS, this function helps to identify the NE where the fault occurs,
facilitating fault handling.

GBSS14.0
Feature Activation Guide 249 Configuring End-to-End MS Signaling Tracing
Procedure
End-to-end User Tracing Function to YES(Yes), and set A Interface Msg
[End2end User Tracing] and Spt BSS Invoke Trace Rpt[end2end user trace] to
appropriate values.
1. Run the BSC6900 MML command LST OTHSOFTPARA to check the value of
Support End-to-end User Tracing Function.
Expected result: Support End-to-end User Tracing Function is set to YES(Yes).
2. On the M2000, choose Monitor > Signaling Trace > Signaling Trace
Management from the main menu. In the navigation tree, double-click 2G End-to-
End User Trace.
Expected result: A 2G End-to-End User Trace dialog box is displayed.
3. In the 2G End-to-End User Trace window, select User ID type from the drop-down
list and enter the user ID. Then click OK.
Expected result: The M2000 generates a report on the end-to-end MS signaling
tracing.
End-to-end User Tracing Function to NO(No).
----End
Example
/*Activating End-to-End MS Signaling Tracing*/
//Enabling the end-to-end MS signaling tracing function
SET OTHSOFTPARA: End2EndTraceState=YES, AInterMsgTrace=YES,
SENDBSSINVOKETRACE=YES;
/*Deactivating End-to-End MS Signaling Tracing*/

//Disabling the end-to-end MS signaling tracing function
SET OTHSOFTPARA: End2EndTraceState=NO, AInterMsgTrace=NO,
SENDBSSINVOKETRACE=NO;

GBSS14.0 250 Configuring Radio Measurement Data Interface for
Feature Activation Guide Navigation
250 Configuring Radio Measurement

Data Interface for Navigation
Radio Measurement Data Interface for Navigation. (This feature cannot be configured using the
CME. )
Prerequisites
– The BSC6900 is configured with an OMU board running the Linux operating system.
l License
– The port 6200 and the port 8200 used to communicate with the VNP have been enabled
on the OMU.
– The ciphering function has been enabled on the CN side.
– The Vendor Network Probe (VNP) has subscribed to events Cipher Mode Complete,
Clear Command, Handover Command, Handover Complete, Measurement Report
Small, and MS Identity Established.
– The BSC can connect to the Ericsson VNP. The BSC and Ericsson VNP use a protocol
whose version is Category3 or later.
– The BSC can connect to the Huawei VNP. The BSC and Huawei VNP use a protocol
whose version is Category4. The Huawei VNP works in Nastar-TS V100R001C00 or
a later version.
Context
Radio Measurement Data Interface for Navigation enables the BSC to send measured MS-related
radio data to the VNP, which then sends the data to a thirty-party Collection Unit (CU). The CU
processes the data and then sends it to GPS users to instruct the users to avoid congestion.

Assume that the active workspace of the OMU is version_a.
Procedure
l Activation Procedure (Newly-configured, and using the external virtual IP address of the
OMU for communicating with the VNP)
1. Run the BSC6900 MML command ADD GVNPADDR. In this step, set VNP IP
Address and Category Version to appropriate values based on the network plan. Note
that Category Version must be the same as that on the peer VNP.
2. Run the BSC6900 MML command SET BSCBASIC. In this step, set Event Report
Switch to ON, BSC Protocol Version No., BSC Application Version No., and
Access Cause to appropriate values based on the network plan. Note that BSC
Protocol Version No. and BSC Application Version No. must be the same as those
on the peer VNP.
NOTE
If a Huawei VNP is used, set BSC Application Version No. to 13.

3. Run the BSC6900 MML command SET GCELLSOFT. In this step, set Index
Type (Not required on the CME), Cell Index, and Cell Name to appropriate values,
and Real-Time Event Report Switch to ON.
l Activation Procedure (Newly-configured, and using the local IP address of the BSC for
communicating with the VNP)
on the peer VNP.
NOTE

4. Use the debugging IP address to log in to the target OMU at the local end. For details,
see Logging In to the OMU.
5. Run the /etc/rc.d/omud stop command and press Enter to stop the omud process.
6. Run the cd /mbsc/bam/version_a/bin/bam command and press Enter to enter the
directory under which the omutool is located.
7. Run the ./omutool vlan_for_om VLAN ID command to add a VLAN for
interconnecting the OMU and the M2000 based on the network plan.
8. Run the ./omutool vlan_for_vnp VLAN ID command to add a VLAN for
interconnecting the OMU and the VNP based on the network plan.

NOTE
The VLAN ID ranges from 2 to 4094. The VLAN ID in Step 7 and Step 8 cannot be set to the same
value.
If you have configured VLAN in Step 7 and Step 8 twice, you must restart the PC or server running
the OMU before starting the OMU.
9. Run the ./omutool vnpvip IP Address Mask command (for example, ./omutool
vnpvip 10.144.188.101 255.255.255.255) to set the local IP address and mask of the
BSC.
10. Run the /etc/rc.d/omud start command and press Enter to start the omud process.
11. (Optional) If an active and a standby OMUs are configured, perform the steps from
Step 4 to Step 10 repeatedly on the standby OMU. Set the VLAN ID to the same
value.
12. Store related configuration information in Information Record Sheet of OMU
Software Installation.
communicating with the VNP. The VLAN remains unchanged.)
on the peer VNP.
NOTE

vnpvip 10.144.188.101 255.255.255.255) to set the local IP address and mask of the
BSC.
Step 4 to Step 8 repeatedly on the standby OMU. Set the VLAN ID to the same value.
communicating with the VNP. The VLAN has changed.)

on the peer VNP.
NOTE

7. Run the ./omutool vlan_for_om VLAN ID command to modify the VLAN for
interconnecting the OMU and the M2000 based on the network plan.
8. Run the ./omutool vlan_for_vnp VLAN ID command to modify the VLAN for
interconnecting the OMU and the VNP based on the network plan.
NOTE
The VLAN ID ranges from 2 to 4094. The VLAN ID in Step 7 and Step 8 cannot be set to the same
value.
If you have configured VLAN in Step 7 and Step 8 twice, you must restart the PC or server running
the OMU before starting the OMU.
vnpvip 10.144.188.101 255.255.255.255) to modify the local IP address and mask of
the BSC.
Step 4 to Step 10 repeatedly on the standby OMU. Set the VLAN ID to the same
value.
1. Use an MS to process call services and trace IP packets at the BSS.
2. Check the IP packet information.
Expected result: The IP packets contain complete information collected at the BSS
and the reported events comply with protocols.

NOTE
The IP packet information consists of the events reported by the MS, including Cipher Mode
Complete, Clear Command, Handover Command, Handover Complete, Measurement Result
Small, and MS Identity Established. Where, events Cipher Mode Complete, Clear Command,
and Measurement Result Small are always reported for an ordinary call. When inter-BSC call
handover occurs, events Handover Command, Handover Complete, and MS Identity
Established will also be reported besides the preceding events.
3. Run the BSC6900 MML command LST GVNPLOCALIP to query on the OMU the
IP addresses used for connecting to the VNP.
l Deactivation Procedure (Using the external virtual IP address of the OMU for
1. Run the BSC6900 MML command SET BSCBASIC. In this step, set Real-Time
Event Report Switch to OFF.
2. Run the BSC6900 MML command RMV GVNPADDR and specify VNP IP
Address to remove the IP address of the VNP.
l Deactivation Procedure (Using the local IP address of the BSC for communicating with
the VNP)
1. Run the BSC6900 MML command SET BSCBASIC. In this step, set Real-Time
Event Report Switch to OFF.
2. Run the BSC6900 MML command RMV GVNPADDR and specify VNP IP
Address to remove the IP address of the VNP.
6. Run the ./omutool delvnpvip command to remove the local IP address of the BSC.
7. Run the ./omutool delvlan VLAN ID command to remove the VLAN that is used for
interconnecting the OMU and the M2000.
8. Run the ./omutool delvlan VLAN ID command to remove the VLAN that is used for
interconnecting the OMU and the VNP.
----End
Example
l \\Activation procedure (Newly-configured, and using the external virtual IP address of the
OMU for communicating with the VNP)
ADD GVNPADDR: VNPIP="10.10.12.3";
SET BSCBASIC:
ENTCAUSE=PERIOD_LOCATION_UPDATE-0&NORMAL_LOCATION_UPDATE-0&IMSI_ATTACH-0&SMS-1
&CALL_SETUP-0&PAGING_RESPONSE-
0&IMSI_DETACH-0&OTHERS-0, ENTSWITCH=ON, BSCPVN=1, BSCAVN=1;
SET GCELLSOFT: IDTYPE=BYID, CELLID=0, ENTSWITCH=ON;
l Activation procedure (Newly-configured, and using the local IP address of the BSC for
SET BSCBASIC:

/etc/rc.d/omud stop
cd /mbsc/bam/version_a/bin/bam
./omutool vlan_for_om 3
./omutool vlan_for_vnp 4
./omutool vnpvip 10.10.11.4 255.255.255.0
/etc/rc.d/omud start
l Activation procedure (Newly-configured, and using the local IP address of the BSC for
communicating with the VNP. The VLAN remains unchanged.)
SET BSCBASIC:
/etc/rc.d/omud stop
./omutool vnpvip 10.10.11.4 255.255.255.0
communicating with the VNP. The VLAN has changed.)
SET BSCBASIC:
/etc/rc.d/omud stop
./omutool vlan_for_om 3
./omutool vlan_for_vnp 4
./omutool vnpvip 10.10.11.4 255.255.255.0
l Deactivation Procedure (Using the external virtual IP address of the OMU for
SET BSCBASIC:
0&IMSI_DETACH-0&OTHERS-0, ENTSWITCH=OFF, BSCPVN=1, BSCAVN=1;
RMV GVNPADDR: VNPIP="10.10.12.3";
l Deactivation Procedure (Using the local IP address of the BSC for communicating with
the VNP)
SET BSCBASIC:
0&IMSI_DETACH-0&OTHERS-0, ENTSWITCH=OFF, BSCPVN=1, BSCAVN=1;
RMV GVNPADDR: VNPIP="10.10.12.3";
/etc/rc.d/omud stop
./omutool delvlan 3
./omutool delvlan 4

GBSS14.0 251 Configuring Multi-mode Dynamic Power Sharing
Feature Activation Guide (GSM)
251 Configuring Multi-mode Dynamic

Power Sharing (GSM)
Multi-mode Dynamic Power Sharing (GSM).
Prerequisites
– Only the multi-mode RF modules support GSM and UMTS Dynamic Power Sharing
at present.
– GSM and UMTS Dynamic Power Sharing can not be configured with dynamic spectrum
sharing.
– GSM and UMTS Dynamic Power Sharing is not supported in GSM dynamic transmit
diversity.
– It is not recommended that GSM and UMTS Dynamic Power Sharing coexists with the
baseband frequency hopping algorithm involving two power amplifiers. Their
coexistence results in a certain level of performance loss.
– This feature can't be activated with WRFD-010684 2x2 MIMO or WRFD-010693 DL
64QAM+MIMO simultaneously.
– This feature has to be activated with MRFD-221801 Multi-mode Dynamic Power
Sharing (UMTS) simultaneously.
l License
– The UMTS cell must exist HSDPA Carry.
Context
In the case of a 3900 series multi-mode base station, the GSM and UMTS TRXs can share one
power amplifier. When there is unbalanced traffic in the GSM and the UMTS, the power can be

used more efficiently in an effective way, namely, sharing the power amplifier. The overall
network quality of the GSM and the UMTS is therefore improved.
NOTE
l The feature may fail to retake the shared power in one second when the GSM services increase suddenly.
As a result, internal GSM peak clipping occurs, which affects service quality.
l Enabling the feature may cause the UMTS coverage to shrink and therefore increase the drop rate. The
problem can be addressed by handing over services in marginal coverage to a GSM/UMTS cell under
the same coverage as the original UMTS.
l The switch and other parameter configurations are performed only on the GSM side. The UMTS side
requires no configuration.
Procedure
1. Run the BSC6900 MML command SET BTSGUPWRSHRFP (CME single
configuration: BTS Configuration Express > BTS Power > BTS GU Dynamic
Power Sharing Parameters; CME batch modification center: not supported). In this
step, set Board Parameter Configuration Enabled to YES(YES) and set the period
for enabling GU power sharing.
supported). In this step, set RXU Board Type to MRRU(MRRU) or MRFU
(MRFU), set GU Dynamic Power Sharing Switch to YES(YES), and set parameters
Minimum Number of Non-BCCH TRXs in GSM for GU Power Sharing, GSM
Power Load Threshold for GU Power Sharing, Number of Checked Timeslots
for Retrieving Shared Power, Num of Timeslots Meet Requirements for
Retrieving Shared Pwr, GSM Power Reserve Coefficient for Retrieving Shared
Power, GSM Idle Channel Threshold for GU Power Sharing, GSM Idle Channel
Hysteresis for GU Power Sharing, GSM Power Reserve in Low Load for GU
Power Sharing, GSM Power Reserve in High Load for GU Power Sharing,
Maximum Accumulated Shared Power That UMTS Can Accept, Maximum
Shared Power That UMTS Can Accept In Each Period to actual conditions.
3. Run the NodeB MML command MOD LOCELL (CME single configuration: NodeB
Configuration Express > IUB_NodeB > Radio Layer > xx Sector > Locell; CME
batch modification center: Modifying Physical NodeB Parameters in Batches), set
GU Power Share Flag to TRUE(TRUE).
1. Run the BSC6900 MML command LST BTSGUPWRSHRFP and LST
BTSRXUBP and check the returned message.
Exception result: Board Parameter Configuration Enabled and GU Dynamic
Power Sharing Switch are YES.
2. Run the NodeB MML command LST LOCELL, and check the returned message.
Exception result: GU Power Share Flag is YES.
1. Run the NodeB MML command MOD LOCELL (CME single configuration: NodeB
Configuration Express > IUB_NodeB > Radio Layer > xx Sector > Locell; CME
batch modification center: Modifying Physical NodeB Parameters in Batches), set
GU Power Share Flag to FALSE(FALSE).

2. Run the BSC6900 MML command SET BTSGUPWRSHRFP (CME single

configuration: BTS Configuration Express > BTS Power > BTS GU Dynamic
Power Sharing Parameters; CME batch modification center: not supported). In this
step, set Board Parameter Configuration Enabled to NO(NO).
supported). In this step, set GU Dynamic Power Sharing Switch to NO(NO).
NOTE
GSM and UMTS Dynamic Power Sharing can be deactivated by performing either of the two
steps discussed above.
----End
Example
SET BTSGUPWRSHRFP: IDTYPE=BYID, BTSID=1, CFGFLAG=YES,
GUPWRSHARESTM1=07&00, GUPWRSHAREETM1=09&00, GUPWRSHARESTM2=10&00,
GUPWRSHAREETM2=12&00, GUPWRSHARESTM3=14&00, GUPWRSHAREETM3=16&00,
GUPWRSHARESTM4=20&00, GUPWRSHAREETM4=22&00;
RXUTYPE=MRFU, GUPWRSHARESWITCH=YES,
GUPWRSHARETRXNUM=1, GUPWRSHAREPWRLOAD=80, GUPWRSHAREN=8, GUPWRSHAREP=6,
GUPWRSHARERSVFACTOR=50, GUPWRSHAREGSMIDLETH=12,
GUPWRSHAREGSMIDLEHS=2, GUPWRSHAREGSMIDLERSVPWR=5,
GUPWRSHAREGSMBUSYRSVPWR=10, GUPWRSHAREURCVPWR=15, GUPWRSHAREURCVPWRPD=5;
MOD LOCELL: LOCELL=0, SECT=LOCAL_SECTOR, GUPOWERSHARE=TRUE;
LST BTSGUPWRSHRFP: IDTYPE=BYID, BTSID=1, LSTFORMAT=VERTICAL;
LST BTSRXUBP: IDTYPE=BYID, BTSID=1, RXUIDTYPE=SRNSN, CN=0, SRN=4, SN=0,
LSTFORMAT=VERTICAL;
LST LOCELL: MODE=LOCALCELL, LOCELL=0;
SET BTSGUPWRSHRFP: IDTYPE=BYID, BTSID=1, CFGFLAG=NO;
RXUTYPE=MRFU, GUPWRSHARESWITCH=NO;
MOD LOCELL: LOCELL=0, SECT=LOCAL_SECTOR, GUPOWERSHARE=FALSE;

GBSS14.0 252 Configuring GSM and UMTS Dynamic Spectrum
Feature Activation Guide Sharing(GSM)
252 Configuring GSM and UMTS

Dynamic Spectrum Sharing(GSM)
GSM and UMTS Dynamic Spectrum Sharing(GSM). This feature enables the spectrum
resources to be dynamically shared between the GSM and UMTS networks based on their traffic
load, improving frequency utilization.
Prerequisites
– The 900 MHz MRFU and RRU3908 must support this feature.
feature depends on the feature MRFD-221802 GSM and UMTS Dynamic Spectrum
Sharing.
– − This feature cannot be used together with GBFD-117002 IBCA, GBFD-117001 Flex
MAIO, GBFD-115830 VAMOS, or GBFD-510104 Multi-site Cell.
l License
l Start Dynamic Spectrum Sharing on the M2000 by referring to GU DSS Management of
the M2000 Online Help.
Context
The dynamic spectrum sharing (DSS) between GSM and UMTS increases network throughput
and reduces the total cost of data services because UMTS has higher spectral efficiency than
GSM. In theory, the maximum throughput gain is about 50%. After this feature is used, the total
cost of ownership (TCO) of mobile broadband (MBB) can be reduced, and dynamic GSM/
UMTS refarming can be implemented. Thus, the maintenance cost of manual refarming is
reduced.

Procedure
1. Configuration on the RNC side
a. Run the BSC6900 MML command MOD UNODEB (CME single
configuration: NodeB Configuration Express > IUB_RNC > NodeB Basic
Information > NodeB; CME batch modification center: not supported) with
DSS NodeB Flag set to TRUE.
b. Run the BSC6900 MML command ADD UCELLQUICKSETUP (CME single
configuration: Main View > Right click NodeB > Add UMTS Cell, UMTS
Cell Configuration Express > Cell Basic Information > Cell Basic
Information; CME batch modification center: Modifying UMTS Cell
Parameters in Batches) to set up a DSS cell, set DSS Cell Flag to TRUE, and
set Maximum TX Power in Small DSS Coverage and PCPICH TX Power in
Small DSS Coverage based on network conditions.
c. Run the BSC6900 MML command MOD UCELLACCESSSTRICT (CME
single configuration: UMTS Cell Configuration Express > Cell Parameters
> Cell Access Restriction Information; CME batch modification center:
Modifying UMTS Cell Parameters in Batches) with both Cell barred indicator
for SIB3 and Cell barred indicator for SIB4 of DSS cells set to BARRED.
d. Run the BSC6900 MML command ADD UINTERFREQNCELL (CME single
configuration: UMTS Cell Configuration Express > Neighboring Cell >
Inter-frequency Neighboring Cell; CME batch modification center: not
supported) to add the neighbor 3G cells of DSS cells as inter-frequency
neighboring cells, and set Blind Handover Flag to TRUE and
DrdOrLdrFlag to TRUE.
e. Run the BSC6900 MML command ADD U2GNCELL (CME single
configuration: UMTS Cell Configuration Express > Neighboring Cell > GSM
Neighboring Cell; CME batch modification center: not supported) to add the
neighboring GSM cells for DSS cells, and set Blind Handover Flag to TRUE.
f. Run the BSC6900 MML command ADD U2GNCELL (CME single
configuration: UMTS Cell Configuration Express > Neighboring Cell > GSM
Neighboring Cell; CME batch modification center: not supported) to add the
neighboring DSS cells as intra-frequency neighboring cells.
g. Run the BSC6900 MML command SET UCORRMALGOSWITCH (CME
single configuration: UMTS Radio Global Configuration Express >
Connection_Oriented RRM Switch Configuration > Connection Oriented
Algorithm Switches; CME batch modification center: Modifying RNC
Parameters in Batches) with both DRD switch for single RAB and
HO_INTER_FREQ_HARD_HO_SWITCH set to ON.
h. Run the BSC6900 MML command SET UDRD (CME single configuration:
UMTS Radio Global Configuration Express > Directed Retry Parameter
Configuration > RNC-Oriented DRD Algorithm Parameters; CME batch
modification center: Modifying RNC Parameters in Batches) with Load balance
DRD switch for HSDPA set to ON and Load Balancing DRD Choice set to
UserNumber.
i. Run the BSC6900 MML command ADD UCELLDRD (CME single
configuration: UMTS Cell Configuration Express > Cell Parameters > Cell
Oriented DRD Algorithm Parameters; CME batch modification center:
Modifying UMTS Cell Parameters in Batches) with Load balance DRD switch

for HSDPA set to ON and Load Balancing DRD Choice set to

UserNumber.
j. Run the BSC6900 MML command ACT UCELL (CME single configuration:
UMTS Cell Configuration Express > Cell Basic Information > Cell Basic
Information. Set Validation indication to Activated; CME batch modification
center: Modifying UMTS Cell Parameters in Batches) to activate the cell.
2. Configuration on the NodeB side
– Run the NodeB MML command ADD LOCELL (CME single configuration:
NodeB Configuration Express > IUB_NodeB > Radio Layer > xx Sector >
Locell; CME batch modification center: Modifying Physical NodeB Parameters
in Batches) to add local DSS cells, and set GU Power Share Flag to FALSE.
3. Configuration on the BSC side
a. Run the BSC6900 MML command ADD GEXT3GCELL (CME single
configuration: Object Group > GSM Service Configuration and
Maintenance Management > External Cell Configuration > BSC 3G
External Cell; CME batch modification center: 3.21 Modifying BSC External
Cell Parameters in Batches) to add 3G external cells.
b. Run the BSC6900 MML command ADD G3GNCELL (CME single
Neighbor Cell; CME batch modification center: not supported) to add 3G
neighboring cells.
c. Run the BSC6900 MML command SET GDSSPARA (CME single
Spectrum Sharing Parameters; CME batch modification center: not supported)
with Spectrum Sharing Allowed set to YES(Yes).
d. Run the BSC6900 MML command SET GTRXDEV (CME single
TRX Parameters in Batches) with Spectrum Sharing Shutdown Allowed set
to YES(Yes).
CAUTION
The parameter Spectrum Sharing Shutdown Allowed for all TRXs to be shared
under a base station should be set to YES(Yes) except for the BCCH TRX.
1. Start spectrum sharing on the M2000 manually by referring to GU DSS
Management of the M2000 Online Help.
2. Run the BSC6900 MML command DSP UNODEB to query the DSS status of a
NodeB.
Expected result: The value of NodeB DSS state is Actived in Normal DSS
coverage.
3. Run the BSC6900 MML command DSP UCELL to query the DSS status of a cell.
Expected result: The value of DSS state is Actived in Normal DSS coverage.
4. Run the NodeB MML command LST LOCELL to check the value of GU Power
Share Flag.

Expected result: The value of GU Power Share Flag is TRUE.

5. Run the BSC6900 MML command DSP BTSSTAT to query the value of Dynamic
Spectrum Sharing. Expected result: The value of Dynamic Spectrum Sharing is
Yes.
1. Stop Dynamic Spectrum Sharing on the M2000 by referring to GU DSS
Management of the M2000 Online Help.
2. Run the BSC6900 MML command MOD UNODEB (CME single configuration:
NodeB Configuration Express > IUB_RNC > NodeB Basic Information >
NodeB; CME batch modification center: not supported) with DSS NodeB Flag set to
FALSE.
3. Run the BSC6900 MML command SET GDSSPARA (CME single configuration:
BTS Configuration Express > BTS Basic Attributes > BTS Spectrum Sharing
Parameters; CME batch modification center: not supported) with Spectrum Sharing
Allowed set to NO(No).
in Batches) with Spectrum Sharing Shutdown Allowed set to NO(No).
5. Remove the neighboring cell by referring to Reconfiguration Guide.
6. Run the BSC6900 MML command DEA UCELL (CME single configuration: UMTS
Cell Configuration Express > Cell Basic Information > Cell Basic Information.
Set Validation indication to Deactivated; CME batch modification center:
Modifying UMTS Cell Parameters in Batches) to deactivate a cell.
----End
Example
MOD UNODEB: NodeBId=1, DSSFlag=TRUE;
ADD UCELLQUICKSETUP: CellId=102, CellName="dss102", PeerIsValid=INVALID,
CnOpGrpIndex=0, BandInd=Band2, UARFCNDownlink=412, PScrambCode=0,
TCell=CHIP256, LAC=1, SAC=0, CfgRacInd=NOT_REQUIRE, SpgId=1, URANUM=D1,
URA1=0, NodeBName="102", LoCell=102, SupBmc=FALSE, DSSFlag=TRUE,
DSSSmallCovMaxTxPower=431, DSSSmallCovPCPICHPower=331;
MOD UCELLACCESSSTRICT: CellId=102, IdleCellBarred=BARRED,
IdleIntraFreqReselection=ALLOWED, IdleTbarred=D320,
ConnCellBarred=BARRED, ConnIntraFreqReselection=ALLOWED,
ConnTbarred=D320;
ADD UINTERFREQNCELL: RNCId=0, CellId=102, NCellRncId=1, NCellId=105,
SIB11Ind=TRUE, SIB12Ind=FALSE, TpenaltyHcsReselect=D0, BlindHoFlag=TRUE,
NPrioFlag=FALSE, DrdOrLdrFlag=TRUE, InterNCellQualReqFlag=FALSE;
ADD U2GNCELL: RNCId=2, CellId=102, GSMCellIndex=120, BlindHoFlag=TRUE,
NPrioFlag=FALSE;
ADD UINTRAFREQNCELL: RNCId=0, CellId=102, NCellRncId=3, NCellId=121,
SIB11Ind=TRUE, SIB12Ind=FALSE, TpenaltyHcsReselect=D0, NPrioFlag=FALSE;
SET UCORRMALGOSWITCH: DrSwitch=DR_RAB_SING_DRD_SWITCH-1,
HoSwitch=HO_INTER_FREQ_HARD_HO_SWITCH-1;
SET UDRD: LdbDRDSwitchHSDPA=ON, LdbDRDchoice=UserNumber;
ADD UCELLDRD: CellId=120, LdbDRDSwitchHSDPA=ON,
ReDirBandInd=DependOnNCell;
ACT UCELL: CellId=102;
ADD LOCELL: LOCELL=102, STN=1, SECN=0, GUPOWERSHARE=FALSE;


UTRANCELLTYPE=TDD, SYNCCASE=SyncCase1;
SET GDSSPARA: IDTYPE=BYID, BTSID=102, DSSENABLE=YES;
SET GTRXDEV: TRXID=1002, DSSTRXOFFLINE=YES;
SET GTRXDEV: TRXID=1003, DSSTRXOFFLINE=YES;
MOD UNODEB: NodeBId=1, DSSFlag=FALSE;
SET GDSSPARA: IDTYPE=BYID, BTSID=102, DSSENABLE=NO;
HO UCELL: CellId=102, CellChoice=ALLCELL;
DEA UCELL: CellId=102;
RMV UNRELATION: RNCId=0, CellId=102,
NCellType=IntraFreqNCell&InterFreqNCell&InterRatNCell;

GBSS14.0 253 Configuring IP-Based Multi-mode Co-Transmission on
Feature Activation Guide BS side (GBTS)
253 Configuring IP-Based Multi-mode

Co-Transmission on BS side (GBTS)
IP-Based Multi-mode Co-Transmission on BS side (GBTS). For details about data
configurations, see section Configuration Reference > MBTS Configuration Reference
(V100R007C00) > Common Transmission in the 3900 Series Base Station Initial
Configuration Guide, or see section Common Transmission in the GBSS Feature
Documentation. The latest 3900 Series Base Station Initial Configuration Guide can be obtained
from the following path: HUAWEI Technical Support (support.huawei.com), Support >
Documentation > SingleRAN > MBTS > SingleRAN7.0.

GBSS14.0 254 Configuring TDM-Based Multi-mode Co-Transmission
Feature Activation Guide via Backplane on BS side (GBTS)
254 Configuring TDM-Based Multi-

mode Co-Transmission via Backplane on BS side
(GBTS)
TDM-Based Multi-mode Co-Transmission via Backplane on BS side(GBTS). (This feature
Prerequisites
– A GSM and UMTS dual-mode base station supports this feature.
– When the TDM timeslot cross connection co-transmission feature is supported by a
GSM and UMTS dual-mode base station, a UTRP should be configured for the BTS.
The UTRP type must be UTRP3, UTRP4, or UTRPb4.
– WRFD-050302 Fractional ATM Function on Iub Interface or WRFD-050411 Fractional
IP Function on Iub Interface
l License
Context
This feature enables the BTS and NodeB to share E1/T1 transmission resources through a
backplane clock channel with the effective TDM timeslot cross connection function.
Backplane-based co-transmission is classified into the following scenarios:

l In the scenario of GTMU-based TDM timeslot cross connection co-transmission, E1/T1
timeslots on the UMTS side are transmitted to the GTMU through the backplane TOP
channel on the WMPT. E1/T1 ports on the GTMU are connected to the transmission
network. The TDM timeslot cross connection function enables GSM data and UMTS data
to be multiplexed on the transmission network. Therefore, E1/T1 transmission resources
are shared by the GSM and UMTS modes by timeslot, as shown in Figure 254-1.

Figure 254-1 GTMU-based TDM timeslot cross connection co-transmission
l In the scenario of GSM-UTRP-based TDM timeslot cross connection co-transmission, a

UTRP is configured on the GSM side. Therefore, extra E1/T1 resources can be shared by
the UMTS mode through the backplane TOP channel to extend E1/T1 transmission
resources for the UMTS mode, as shown in Figure 254-2.
NOTE
l The number of E1/T1 on the BTS backplane is within the range of 16 through 19. E1/T1 numbers 16 through
19 on the BTS backplane correspond to E1/T1 numbers 0 through 3 on the NodeB backplane. Cross
connection is not supported. For example, E1/T1 No. 16 on the BTS backplane only corresponds to E1/T1
No. 0 on the NodeB backplane.
l E1 timeslot numbers configured on the BTS side must be consistent with those configured on the NodeB
side.
Figure 254-2 GSM-UTRP-based TDM timeslot cross connection co-transmission
Procedure
l Activating the BTS data (GTMU-based)
between a GTMU port and the NodeB. Set Dest Node Type (select Connect to
BSC on the CME) to OTHER.

2. Run the BSC6900 MML command ADD BTSTOPCONFIG to configure the TOP
switching parameters.
– Set Port Subrack No. and Port Slot No. to numbers of the subrack and slot where
the BTS port connected to the NodeB interface board is located. Set TOP Board
Subrack No. and TOP Board Slot No. to numbers of the subrack and slot where
the NodeB interface board is located.
– Set Port Type to TOPEXTOUTPORT.
– Set TS Mask to the timeslot of the NodeB backplane.
NOTE
When E1 transmission resources on the BTS side are shared by the NodeB, set Port Type to
TOPEXTOUTPORT.
l Activating the NodeB data (GTMU-based)
1. Run the NodeB MML command ADD BACKE1T1 to add a backplane E1/T1 link.
– Set Subrack No. and Slot No. to numbers of the subrack and slot that house the
Iub interface board.
– Set Subboard Type to BACK_BOARD.
– Set Destination Slot No. to the number of the slot that houses the GTMU.
NOTE
Similar to a common E1, the backplane E1 can be configured with the upper-layer bearer. It,
however, does not support the configuration of the operating work mode and loopback mode, and
online and offline tests. The upper-layer link bearer of the backplane E1 can be UNILNK/IMALNK/
FRAATMLNK/PPLNK/MPLNK. You need to configure the link bearer according to actual
networking mode.
2. Run the NodeB MML command ADD IMAGRP to add an IMA group. In this step,
set Subboard Type to BASE_BOARD.
3. Run the NodeB MML command ADD IMALNK to add an IMA link and then add it
to the MP group. In this step, set Subboard Type to BACK_BOARD or
BASE_BOARD.
4. Run the NodeB MML command ADD SAALLNK to add an SAAL link.
– Set Subboard Type to BASE_BOARD.
– Set Rate Unit to KBPS or CELL/S. Only one rate unit can be used. Therefore,
rate units in other configuration must be consistent.
5. Run the NodeB MML command ADD AAL2NODE to add an AAL2 node.
– Set Node Type to LOCAL(LOCAL).
– Set ATM Address to a valid ATM address. The recommended value is
H'3900000000000000000000000000000000000000.
6. Run the NodeB MML command ADD AAL2PATH to add an AAL2 path.
– Set Node Type to LOCAL(End Node).
7. Run the NodeB MML command ADD IUBCP to add an NCP link. In this step, set
NCP/CCP Port Type to NCP(NCP Port).
8. Run the NodeB MML command ADD IUBCP to add a CCP link. In this step, set
Port Type to CCP(CCP Port).

NOTE
Before a CCP link is added, the number of the CCP port must be the same as that of the CCP port
on the BSC6900 side. To query information about the CCP link on the BSC6900 side, run the
BSC6900 MML command LST UIUBCP.
l Activating the BTS data (GSM-UTRP-based)
between a UTRP port and the NodeB. Set Dest Node Type (select Connect to BSC
on the CME) to OTHER.
2. Run the BSC6900 MML command ADD BTSTOPCONFIG to configure the TOP
switching parameters.
– Set Port Type to TOPEXTOUTPORT.
– Set TS Mask to the timeslot of the NodeB backplane.
NOTE
When E1 transmission resources on the BTS side are shared by the NodeB, set Port Type to
TOPEXTOUTPORT.
l Activating the NodeB data (GSM-UTRP-based)
1. Run the NodeB MML command ADD BACKE1T1 to add a backplane E1/T1 link.
– Set Cabinet No., Subrack No., and Slot No. to the numbers of the cabinet,
subrack, and slot that house the Iub interface board.
– Set Subboard Type to BACK_BOARD.
– Set Destination Slot No. to the number of the slot that houses the UTRP.
NOTE
Similar to a common E1, the backplane E1 can be configured with the upper-layer bearer. It,
however, does not support the configuration of the operating work mode and loopback mode, and
online and offline tests. The upper-layer link bearer of the backplane E1 can be UNILNK/IMALNK/
FRAATMLNK/PPLNK/MPLNK. You need to configure the link bearer according to actual
networking mode.
2. Run the NodeB MML command ADD IMAGRP to add an IMA group. In this step,
set Subboard Type to BASE_BOARD.
3. Run the NodeB MML command ADD IMALNK to add an IMA link and then add it
to the MP group. In this step, set Subboard Type to BACK_BOARD or
BASE_BOARD.
4. Run the NodeB MML command ADD SAALLNK to add an SAAL link.
5. Run the NodeB MML command ADD AAL2NODE to add an AAL2 node.
– Set Node Type to LOCAL(LOCAL).
– Set ATM Address to a valid ATM address. The recommended value is
H'3900000000000000000000000000000000000000.
6. Run the NodeB MML command ADD AAL2PATH to add an AAL2 path.
– Set Node Type to LOCAL(End Node).

7. Run the NodeB MML command ADD IUBCP to add an NCP link. In this step, set
Port Type to NCP.
8. Run the NodeB MML command ADD IUBCP to add a CCP link. In this step, set
Port Type to CCP.
NOTE
Before a CCP link is added, the number of the CCP port must be the same as that of the CCP port
on the BSC6900 side. To query information about the CCP link on the BSC6900 side, run the
BSC6900 MML command LST UIUBCP.
----End
Example
//Activating the BTS data (GTMU-based)
//Configuring a connection between a GTMU port and the NodeB
DESTNODE=OTHER;
//Configuring the TOP switching relation between the GTMU and the WMPT:
E1 port 16 on the backplane corresponds to port 0 on the WMPT, the GTMU
provides the WMPT with a transmission path, the port type is TOPEXTINPO,
and the output port is E1 port 1 on the GTMU
ADD BTSTOPCONFIG: IDTYPE=BYID, BTSID=255, CN=0, SRN=0, SN=6,
E1T1PORTNO=16, TOPBOARDCN=0, TOPBOARDSRN=0, TOPBOARDSLOTNO=7,
PORTTYPE=TOPEXTOUTPORT, ORIPORT=1,
//Activating the NodeB data (GTMU-based)

//Adding a backplane E1/T1 link
ADD BACKE1T1: SRN=0, SN=7, SBT=BACK_BOARD, DSTSN=6;
//Adding an IMA group
ADD IMAGRP: SRN=0, SN=7, SBT=BASE_BOARD;
//Adding an IMA link
ADD IMALNK: SRN=0, SN=7, SBT=BACK_BOARD, IMAGRPSBT=BASE_BOARD;
//Adding three SAAL links
ADD SAALLNK: SAALNO=4, SRN=0, SN=7, SBT=BASE_BOARD, PT=IMA,
JNRSCGRP=DISABLE, VPI=0, VCI=32, RU=KBPS, ST=CBR, PCR=1024;
//Adding an AAL2 node
ADD AAL2NODE: NT=LOCAL, LN=4,
ADDR="H'3900000000000000000000000000000000001980";
//Adding an AAL2 path
ADD AAL2PATH: NT=LOCAL, PATHID=23, CN=0, SRN=0, SN=7, SBT=BASE_BOARD,
PT=IMA, JNRSCGRP=DISABLE, VPI=4, VCI=36, RU=KBPS, ST=RTVBR, PCR=1024,
SCR=512, RCR=512;
//Adding an NCP or CCP link
ADD IUBCP: CPPT=NCP, BEAR=ATM, LN=5;
ADD IUBCP: CPPT=CCP, BEAR=ATM, LN=6;
//Activating the BTS data (GSM-UTRP-based)
//Configuring a connection between a UTRP port and the NodeB
DESTNODE=OTHER;
//Configuring the TOP switching relation between the UTRP and the WMPT:
E1 port 16 on the backplane corresponds to port 0 on the WMPT, the UTRP
provides the WMPT with a transmission path, the port type is TOPEXTINPO,
and the output port is E1 port 1 on the UTRP

ADD BTSTOPCONFIG: IDTYPE=BYID, BTSID=255, CN=0, SRN=0, SN=0,

E1T1PORTNO=16, TOPBOARDCN=0, TOPBOARDSRN=0, TOPBOARDSLOTNO=7,
PORTTYPE=TOPEXTOUTPORT, ORIPORT=1,
Activating the NodeB data (GSM-UTRP-based)

//Adding a backplane E1/T1 link
ADD BACKE1T1: SRN=0, SN=7, SBT=BACK_BOARD, DSTSN=0;
//Adding an IMA group
ADD IMAGRP: SRN=0, SN=7, SBT=BASE_BOARD;
//Adding an IMA link
ADD IMALNK: SRN=0, SN=7, SBT=BACK_BOARD, IMAGRPSBT=BASE_BOARD;
//Adding three SAAL links
//Adding an AAL2 node
ADD AAL2NODE: NT=LOCAL, LN=4,
ADDR="H'3900000000000000000000000000000000001980";
//Adding an AAL2 path
ADD AAL2PATH: NT=LOCAL, PATHID=23, CN=0, SRN=0, SN=7, SBT=BASE_BOARD,
PT=IMA, JNRSCGRP=DISABLE, VPI=4, VCI=36, RU=KBPS, ST=RTVBR, PCR=1024,
SCR=512, RCR=512;
//Adding an NCP or CCP link
ADD IUBCP: CPPT=NCP, BEAR=ATM, LN=5;
ADD IUBCP: CPPT=CCP, BEAR=ATM, LN=6;

GBSS14.0 255 Configuring Multi-Mode BS Common Reference Clock
255 Configuring Multi-Mode BS

Common Reference Clock (GBTS)
Multi-Mode BS Common Reference Clock (GBTS). For details about data configurations, see
section Configuration Reference > MBTS Configuration Reference (V100R007C00) >
Common Clock in the 3900 Series Base Station Initial Configuration Guide, or see section
Common Clock in the GBSS Feature Documentation. The latest 3900 Series Base Station Initial
Configuration Guide can be obtained from the following path: HUAWEI Technical Support
(support.huawei.com), Support > Documentation > SingleRAN > MBTS > SingleRAN7.0.

GBSS14.0 256 Configuring Dynamic MA for GU Dynamic Spectrum
Feature Activation Guide Sharing (GSM)
256 Configuring Dynamic MA for GU

Dynamic Spectrum Sharing (GSM)
MRFD-211803 Dynamic MA for GU Dynamic Spectrum Sharing(GSM). (For details about
operations performed on the CME, see the Configuring a GU DSS Task in the M2000-CME
documentation.)
Prerequisites
MRFD-211802 GSM and UMTS Dynamic Spectrum Sharing(GSM) and
MRFD-221802 GSM and UMTS Dynamic Spectrum Sharing(UMTS).
– This feature cannot be used together with the feature GBFD-117001 Flex MAIO.
l License
l Requirements for the Operating Environment
– The BTS is configured with the 900 MHz MRFU or RRU3908.
Context
After this feature is activated, the BSC starts spectrum sharing when the traffic volume of a cell
is lighter than what can be carried on two or three TRXs, increasing the spectrum sharing time.
Operators are advised to enable this feature in the scenario where the GSM and UMTS Dynamic
Spectrum Sharing feature is enabled.
l Precautions
– After this feature is activated, dynamically changing an absolute radio frequency
channel number (ARFCN) of a cell leads to cell reset.
– This feature affects the following algorithms:
– Handover algorithm: During dynamic MA changing, the BSC performs an intra-cell
handover on MSs in the GSM cell.

– Admission algorithm: During dynamic MA changing, the BSC preferentially

allocates timeslots with new MA to new MSs.
l Data Preparation
Paramet Parame Description Data Source
er Name ter ID
FH Index TRXDS FH index of channels after spectrum Network planning

Used SHOPIN sharing
After DEX
Frequenc
y
Spectrum
Sharing
MAIO TRXDS MAIO of channels after spectrum Network planning

Used SMAIO sharing
After
Frequenc
y
Spectrum
Sharing
Procedure
1. Run the BSC6900 MML command ADD GCELLMAGRP (CME single
modification center: not supported) to add the mobile allocations (MAs) before and
after dynamic spectrum sharing is enabled.
modification center: not supported). In this step, set FH Index Used After Frequency
Spectrum Sharing and MAIO Used After Frequency Spectrum Sharing for the
channels in the cell.
1. Check that this feature has taken effect by viewing the value of the Number of dynamic
MA changing requests counter.
modification center: not supported). In this step, set FH Index Used After Frequency
Spectrum Sharing to 255.
----End
Example
//GSM and UMTS Dynamic Spectrum Sharing must have been configured before
//Setting the cell frequency hopping (FH) group

ADD GCELLMAGRP: IDTYPE=BYID, CELLID=100, HOPINDEX=1, HSN=0, TSC=0,

HOPMODE=1, FREQ1=802, FREQ2=804, FREQ3=806, FREQ4=808;
HOPMODE=1, FREQ1=802, FREQ2=804;
HOPMODE=1, FREQ1=806, FREQ2=808;
//Setting the FH groups for a channel
SET GTRXCHANHOP: TRXID=1001, CHNO=0, TRXHOPINDEX=1, TRXMAIO=0,
IDTYPE=BYID, TRXDSSHOPINDEX=2, TRXDSSMAIO=0;



GBSS14.0 257 Configuring GSM Power Control on Interference
Feature Activation Guide Frequency for GU Small Frequency Gap (GSM)
257 Configuring GSM Power Control on

Interference Frequency for GU Small Frequency
Gap (GSM)
MRFD-211804 GSM Power Control on Interference Frequency for GU Small Frequency gap
(GSM).
Prerequisites
– The feature GBFD-113701 Frequency Hopping (RF hopping, baseband hopping) has
been configured before this feature is activated.
l License
– Only 3900 series base stations support this feature.
Context
This feature is recommended for the GU refarming 3.8 MHz or 4.2 MHz scenario where the
number of FH TCH frequencies is greater than or equal to 6.
l Precautions
– The interfering frequencies must join in FH.
– Operators are not advised to enable this feature together with the feature MRFD-211801
Multi-mode Dynamic Power Sharing(GSM) or MRFD-221801 Multi-mode Dynamic
Power Sharing(UMTS).
– This feature affects the following features: GBFD-117002 IBCA (Interference Based
Channel Allocation), GBFD-118106 Dynamic Power Sharing, GBFD-113201
Concentric Cell, GBFD-115507 WB AMR, and GBFD-115830 VAMOS.
l Data Preparation

– When this feature is used together with the feature 2.0MHz Central Frequency point
separation between GSM and UMTS mode, operators only need to prepare the data for
the feature 2.0MHz Central Frequency point separation between GSM and UMTS
mode.
– When this feature is used together with the function GU Refarming 4.2 MHz of the
Flexible Frequency Bandwidth of UMTS Carrier feature, the data for this feature is the
same as the data for the function GU Refarming 4.2 MHz.
– The following table describes the parameters that are specific to this feature.
er Name ter ID
Cell CELLI Cell in which frequency-based power Network planning

Index D control is enabled
Frequenc GUDegr Whether to enable frequency-based Network planning

y-based atePwrC power control.
Power trl
Control
Interfere GUDegr Frequency-based power control Network planning

nce atePwrP policy. If this parameter is set to GSM
Coordina ri (GSM), this feature preferentially
tion guarantees the GSM network quality
Policy while minimizing interference to the
UMTS network. If this parameter is
set to UMTS(UMTS), this feature
preferentially guarantees the UMTS
network quality. The specific setting
depends on customers' requirements.


er Name ter ID
GU2.0 GU2000 Maximum power decrease for the Network planning

MHz KHzMa interfering frequency when there is a
Max. xVal 2.0 MHz frequency spacing between
Power the GSM and UMTS networks. The
Decrease expected transmit power of the
for interfering frequency can be
Interferin calculated with the following
g formula: Expected transmit power of
Frequenc the interfering frequency =
y Maximum TRX transmit power -
GU2.0 MHz Max. Power Decrease
for Interfering Frequency. The larger
the parameter value, the lower the
expected transmit power of the
interfering frequency is, and the more
GSM users are affected in terms of
service quality. In this case, if this
parameter is set to UMTS(UMTS),
the UMTS network has more
performance gains; if this parameter
is set to GSM(GSM), the GSM users
on which power compression is
performed are more closer to the cell
center.
GU2.2 GU2200 Maximum power decrease for the Network planning

MHz KHzMa interfering frequency when there is a
Max. xVal 2.2 MHz frequency spacing between
Power the GSM and UMTS networks. The
Decrease expected transmit power of the
for interfering frequency can be
Interferin calculated with the following
g formula: Expected transmit power of
Frequenc the interfering frequency =
y Maximum TRX transmit power -
GU2.2 MHz Max. Power Decrease
for Interfering Frequency. The larger
the parameter value, the lower the
expected transmit power of the
interfering frequency is, and the more
GSM users are affected in terms of
service quality. In this case, if this
parameter is set to UMTS(UMTS),
the UMTS network has more
performance gains; if this parameter
is set to GSM(GSM), the GSM users
on which power compression is
performed are more closer to the cell
center.


er Name ter ID
UMTS UMTSF Downlink absolute radio frequency Network planning

Center reqNum channel number (ARFCN) for the
Frequenc 1 first UMTS frequency that has a 2.0
y1 MHz or 2.2 MHz spacing with the
GSM frequency in GU refarming
scenarios. When one UMTS
frequency is deployed in GU
refarming scenarios, one ARFCN is
configured. When multiple UMTS
frequencies are deployed in GU
refarming scenarios, multiple
ARFCNs are configured. Currently,
a maximum of two such ARFCNs
can be configured.
UMTS UMTSF Downlink ARFCN for the second Network planning

Center reqNum UMTS frequency that has a 2.0 MHz
Frequenc 2 or 2.2 MHz spacing with the GSM
y2 frequency in GU refarming
scenarios. The value of this
parameter ranges from 0 to 1023.
When one UMTS frequency is
deployed in GU refarming scenarios,
one ARFCN is configured. When
multiple UMTS frequencies are
deployed in GU refarming scenarios,
multiple ARFCNs are configured.
Currently, a maximum of two such
ARFCNs can be configured.
Non- NAHR Proportion of power compensation Network planning

AHR CompC for the non-interfering frequencies to
Power oeff power decrease each time the
Compens transmit power of the interfering
ation frequency is decreased by 1 dB for
Proportio enhanced full rate (EFR), full rate
n (FR), half rate (HR), and adaptive
multirate (AMR) FR calls. Increasing
the value of this parameter increases
the power compensation amplitude.


er Name ter ID
Non- NAHR Power compensation offset for EFR, Network planning

AHR CompO FR, HR, and AMR FR calls. Power
Power ffVal decrease amplitude that requires
Compens power compensation =
ation NAHRCompOffVal/
Offset NAHRCompCoeff. When
NAHRCompCoeff is set to 0, this
parameter does not need to be
configured. When this parameter is
set to a smaller value, the power
decrease amplitude that does not
require power compensation
increases.
AHR AHRCo Proportion of power compensation Network planning

Power mpCoef for the non-interfering frequencies to
Compens f power decrease each time the
ation transmit power of the interfering
Proportio frequency is decreased by 1 dB for
n AMR HR calls. Increasing the value
of this parameter increases the power
compensation amplitude.
AHR AHRCo Power compensation offset for AMR Network planning

Power mpOffV HR calls. Power decrease amplitude
Compens al that requires power compensation =
ation AHRCompOffVal/
Offset AHRCompCoeff. When
AHRCompCoeff is set to 0, this
parameter does not need to be
configured. When this parameter is
set to a smaller value, the power
decrease amplitude that does not
require power compensation
increases.
Procedure
1. Run the BSC6900 MML command SET GCELLNONSTANDARDBW (CME
single configuration: Cell Configuration Express > Power Control > GSM/UMTS
Small Frequency Spacing Interference Control Parameters; CME batch
set Frequency-based Power Control to ON and set the other parameters to
appropriate values. The other parameters are Cell Index, Interference Coordination
Policy, GU2.0 MHz Max. Power Decrease for Interfering Frequency, GU2.2 MHz
Max. Power Decrease for Interfering Frequency, UMTS Center Frequency 1,
UMTS Center Frequency 2, Non-AHR Power Compensation Proportion, Non-

AHR Power Compensation Offset, AHR Power Compensation Proportion, and

AHR Power Compensation Offset.
1. When this feature is used together with the feature 2.0MHz Central Frequency point
separation between GSM and UMTS mode, the procedure used to verify this feature
is the same as that used to verify the feature 2.0MHz Central Frequency point
separation between GSM and UMTS mode.
2. When this feature is used together with the GU Refarming 4.2 MHz function of the
Flexible Frequency Bandwidth of UMTS Carrier feature, the procedure used to verify
this feature is the same as that used to verify the Flexible Frequency Bandwidth of
UMTS Carrier feature.
3. Run the NodeB MML command DSP LICENSE to query whether the license
controlling this feature has been activated.
4. Run the BSC6900 MML command LST GCELLNONSTANDARDBW to query
whether Frequency-based Power Control is set to ON and whether Cell Index is
set to the index of the cell where this feature is to be enabled.
5. Check the values of the counters in the following table.
Counter ID Counter Name Description
1282449360 CELL. Average Power Decrease

2MDISTURB.AVG.FAL on GSM 2.0 MHz
L.POWER.RANGE Interfering Frequency
1282449361 CELL. Average Power Decrease

2.2MDISTURB.AVG.F on GSM 2.2 MHz
ALL.POWER.RANGE Interfering Frequency
1282449362 CELL.UNDISTURB.AV Average Power Increase

G.UP.POWER.RANGE on GSM Non-Interfering
Frequency
1. Run the BSC6900 MML command SET GCELLNONSTANDARDBW (CME
single configuration: Cell Configuration Express > Power Control > GSM/UMTS
Small Frequency Spacing Interference Control Parameters; CME batch
set Frequency-based Power Control to OFF.
----End
Example
SET GCELLNONSTANDARDBW: IDTYPE=BYID, CELLID=2, GUDegratePwrCtrl=ON,
GUDegratePwrPri=GSM, GU2000KHzMaxVal=10, GU2200KHzMaxVal=3,
UMTSFreqNum1=0, UMTSFreqNum2=0, NAHRCompCoeff=5, NAHRCompOffVal=-15,
AHRCompCoeff=5, AHRCompOffVal=-15;
SET GCELLNONSTANDARDBW: IDTYPE=BYID, CELLID=2, GUDegratePwrCtrl=OFF;

GBSS14.0
Feature Activation Guide 258 Multi-mode BS Common IPSec(GSM)
258 Multi-mode BS Common IPSec

(GSM)
MRFD-211602 Multi-mode BS Common IPSec(GSM). (This feature cannot be configured
using the CME. )
Prerequisites
– This feature depends on the features GBFD-118601 Abis over IP and WRFD-050402
IP Transmission Introduction on Iub Interface.
– This feature cannot be used together with the feature GBFD-117702 BTS Local Switch
or WRFD-031101 NodeB Self-discovery Based on IP Mode.
l License
– An MBTS must be configured with a UTRPc board to implement IPSec. If a GU dual-
mode base station does not support IPsec, a security gateway (SeGW) must be
configured to implement IPsec.
– If the SEG will authenticate the base station connected to the bearer network by using
the digital certificate, the PKI function must be enabled on both the base station and the
SEG, and a KPI system must be deployed in the operator's network.
– If the base station controller connected to the base station does not support IPSec, an
SEG must be deployed in the network to use IPSec. If the base station is configured
with a primary IPSec tunnel and a secondary IPSec tunnel, the SeGW must be
configured with a dynamic routing protocol.
Context
IPSec Networking of an MBTS
l IPSec networking for a GU, GL, and UL dual-mode base station: IPSec-related data on the
UTRPc board is configured by the mode with the highest priority. During secure base
station deployment, all security-related configuration data is configured by the mode with

GBSS14.0
a higher priority. The mode with a lower priority does not participate in secure base station
deployment.
l IPSec networking for a GUL triple-mode base station:
– GU+L (BBU interconnection): IPSec is implemented on the LMPT board, and the
UTRPc board forwards the LTE service data and processes UMTS and GSM IPSec
data. IPSec-related data on the UTRPc board is configured by the mode with a higher
priority. If digital certificates are used for identity authentication, the LMPT and UTRPc
boards use their respective digital certificates to authenticate with the SeGW.
– GU+L (BBU interconnection): IPSec is implemented on the UMPT board, and the
UTRPc board forwards the UMTS service data and processes LTE and GSM IPSec
data. IPSec-related data on the UTRPc board is configured by the mode with a higher
priority. If digital certificates are used for identity authentication, the UMPT and UTRPc
boards use their respective digital certificates to authenticate with the SeGW.
– In other BBU interconnection scenarios: The UTRPc board performs IPSec-related
processing. IPSec-related data on the UTRPc board is configured by the mode with a
higher priority. If digital certificates are used for identity authentication, the UTRPc
board uses its digital certificate to authenticate with SeGW, and the three mode of the
base station share the same IPSec tunnels and digital certificate.
l Data Preparation

Name Source
Local Name IKELNM Set this parameter to be consistent Network

Peer end
negotiation
Keepalive IKEKLI - Network

Interval planning
Keepalive IKEKLT
Timeout
NAT NATKLI
Keepalive
Timeout
DSCP DSCP
ACL ID ACLID
Description ACLDESC
Rule Type RULETYPE
Rule ID RULEID
Action ACTION
Protocol Type PT
Source IP SIP
Address

GBSS14.0

Name Source
Source SWC
Wildcard
Match Source SMPT

Port
Source Port SOP

Operate
Source Port 1 SPT1
Source Port 2 SPT2
Destination IP DIP
Address
Destination DWC
Wildcard
Match DMPT
Destination
Port
Destination DOP
Port Operate
Destination DPT1
Port 1
Destination DPT2
Port 2
Match DSCP MDSCP
Differentiated DSCP
Services Code
Point
Match MFRG
Fragment
Message
VLAN ID VLANIDOP
Filter Criteria
VLAN ID 1 VLANID1
VLAN ID 2 VLANID2
Proposal ID PROPID
Encryption ENCALG Set this parameter to be consistent Network

Algorithm with that on the peer end. planning
Peer end
negotiation

GBSS14.0

Name Source
Authenticatio AUTHALG
n Algorithm
Authenticatio AUTHMETH - Network

n Method planning
Diffie- DHGRP Set this parameter to be consistent Network

Hellman with that on the peer end. planning
Group Peer end
negotiation
PRF PRFALG You are advised to use the default Network

Algorithm value. planning
ISAKMP SA DURATION Set this parameter to be consistent Network

Duration with that on the peer end. planning
Peer end
negotiation
IKE Peer PEERNAME - Network

Name planning
Version IKEVERSION Set this parameter to be consistent Network

Exchange EXCHMODE
Peer end
Mode
negotiation
Local ID Type LOCALIDTYPE - Network

planning
Remote IP REMOTEIP
Address
Remote Name REMOTENAME Set this parameter to be consistent Network

Pre-shared PKEY
Peer end
Key
negotiation
DPD Mode DPD The dead peer detection (DPD) is Network

enabled by default. It is planning
DPD Idle DPDIDLETIME recommended that DPD-related
Time parameters be set to consistent
DPD DPDRETRI values on the two ends of the
Retransmissio Internet Key Exchange (IKE).
n Interval Otherwise, the end with a shorter
timer interval first detects that its
DPD DPDRETRN peer end becomes ineffective and
Retransmissio triggers IKE negotiation again.
n Count
NAT NATTRAV - Network

Traversal planning

GBSS14.0

Name Source
Local IP LOCALIP
Address
Pre-shared PKEY
Key
IPSec PROPNAME
Proposal
Name
Encapsulation ENCAPMODE You are advised to use the tunnel Network

Mode mode. planning
Set this parameter to be consistent Peer end
with that on the peer end. negotiation
Transform TRANMODE Set this parameter to be consistent

with that on the peer end.
AH AHAUTHALG
Authenticatio
n Algorithm
ESP ESPAUTHALG
Authenticatio
n Algorithm
ESP ESPENCALG
Encryption
Algorithm
Policy Group SPGN - Network

Name planning
IPSec SPSN
Sequence No.
Perfect PFS Set this parameter to be consistent Network

Forward with that on the peer end. planning
Secrecy Peer end
negotiation
SA Duration LTCFG - Network

Mode planning
Lifetime LTS
Based On
Time
Lifetime LTKB
Based On
Traffic
Anti-Replay REPLAYWND
Window

GBSS14.0

Name Source
Cabinet No. CN
Subrack No. SRN
Slot No. SN
Port Type PT
Port No. PN
Policy Group SPGN

Name
Master Policy MSPGN

Group Name
Master IPSec MSPSN

Sequence No.
Slave Policy SSPGN

Group Name
Slave IPSec SSPSN

Sequence No.
BFD Session MBFDSN

ID of Master
Tunnel
BFD Session SBFDSN

ID of Slave
Tunnel
BFD Session BFDSN

No.
Source IP SRCIP
Address
Destination IP DSTIP
Address
Hop Type HT
Time for BTSWTR

Waiting to
Restore
Minimum TX MINTXINTERV
Interval AL
Minimum RX MINRXINTERV
Interval AL
Detect Period DETECTMULT

GBSS14.0

Name Source
DSCP DSCP
Procedure
To configure active and standby IPSec tunnels, perform Step 1 to Step 12. Otherwise,
perform Step 1 to Step 9.
1. Optional: Run the BSC6900 MML command SET BTSIKECFG to set IKE local
configurations.
2. Run the BSC6900 MML command ADD BTSACL to add an access control list
(ACL).
3. Run the BSC6900 MML command ADD BTSACLRULE to add access rules in the
ACL.
4. Run the BSC6900 MML command ADD BTSIKEPROPOSAL to configure IKE
security proposals.
5. Run the BSC6900 MML command ADD BTSIKEPEER to add an IKE peer.
6. Run the BSC6900 MML command ADD BTSIPSECPROPOSAL to add IPSec
security proposals.
7. Run the BSC6900 MML command ADD BTSIPSECPOLICY to add IPSec security
policies.
8. Run the BSC6900 MML command ADD BTSIPSECBIND to bind the IPSec security
policy to the output port to validate the security policy.
9. Optional: When the BTS uses an IP clock, the clock server is in a non-security domain,
and Clock Topology Mode is set to PTPOVERUDP, Run the BSC6900 MML
command SET BTSIPCLKPARA. In this step, set Clock Protocol Type to PTP
(PTP Protocol), Clock Topology Mode to PTPOVERUDP(PTP over UDP
Unicast), and Client IP Address to the IP address used for the communication
between the BTS and the clock server.
10. Optional: Repeat Step 1 to Step 9 to configure the second IPSec tunnel.
11. Optional: Run the BSC6900 MML command ADD BTSBFD to configure a
Bidirectional Forwarding Detection (BFD) session for the two IPSec tunnels
respectively.
12. Optional: Run the BSC6900 MML command ADD BTSIPSECDTNL to configure
the active/standby relationship between the two IPSec tunnels.
If the active and standby IPSec tunnels have been configured, perform Step 1 to Step 3.
Otherwise, perform Step 1 and Step 2.
1. Run the BSC6900 MML command DSP BTSIPSECSA to check the IPSec tunnel
status.
Expected result: The results contain IPSec security association (SA) data, indicating
that the IPSec tunnels are set up.
2. Run the BSC6900 MML command LST BTSACLRULE to determine whether
service data is protected by the IPSec as planned by checking ACL rules and check

GBSS14.0
whether the protected services are normal. For example, if speech services are
protected by the IPSec, you can check whether the speech services are normal by
initiating calls. If management packets are protected by the IPSec, you can check
whether the corresponding BTS is online from the topology window on the M2000.
Expected result: Service data is protected by the IPSec as planned and the protected
services are normal.
3. Remove the Ethernet cable connecting to the active channel, and Run the BSC6900
MML command DSP BTSIPSECDTNL to check whether Current Used IPSec
Policy is Slave IPSec Policy. Use an MS to initiate a call and observe whether the
call is normal. Check whether the corresponding BTS is online from the topology
window on the M2000.
Expected result: Current Used IPSec Policy is Slave IPSec Policy, the call initiated
by the MS is normal, and the corresponding BTS is online.
1. Run the BSC6900 MML command RMV BTSIPSECBIND to delete the binding
relationship between the IPSec security policy and the corresponding port.
----End
Example
The following descriptions assume that the BTS is in IP over FE transmission mode.
//Setting BTS IKE basic configurations
SET BTSIKECFG: IDTYPE=BYID, BTSID=0, IKELNM="IKECFG1", IKEKLI=20,
IKEKLT=60, NATKLI=20, DSCP=48;
//Adding a BTS ACL
created";
//Adding BTS IKE security proposals
ADD BTSIKEPROPOSAL: IDTYPE=BYID, BTSID=0, PROPID=10, AUTHALG=MD5,
DURATION=86400;
//Adding a BTS IKE peer
ADD BTSIKEPEER: IDTYPE=BYID, BTSID=0, PEERNAME="ike", PROPID=10,
IKEVERSION=IKE_V1, EXCHMODE=MAIN, LOCALIDTYPE=IP, REMOTEIP="2.2.2.2",
PKEY="*****", DPD=PERIODIC, DPDIDLETIME=20, DPDRETRI=4, DPDRETRN=6,
LOCALIP="1.1.1.1";
//Adding BTS IPSec security proposals
ADD BTSIPSECPROPOSAL: IDTYPE=BYID, BTSID=0, PROPNAME="prop1",
ENCAPMODE=TUNNEL, TRANMODE=ESP, ESPAUTHALG=MD5, ESPENCALG=DES;
//Adding BTS IPSec security policies
ADD BTSIPSECPOLICY: IDTYPE=BYID, BTSID=0, SPGN="policy", SPSN=1,
ACLID=3001, PROPNAME="prop1", PEERNAME="ike", LTCFG=LOCAL;
//Binding a BTS IPSec policy group to a port
SPGN="policy";
SPGN=" PolicyGroup1";
//Adding a BFD session on the BTS side

GBSS14.0

//Adding IPSec dual channels
ADD BTSIPSECDTNL: IDTYPE=BYID, BTSID=0, DUALID=0, MSPGN="policy",
MSPSN=1, SSPGN="PolicyGroup1", SSPSN=1, MBFDSN=1, SBFDSN=2;
//Querying the BTS IPSec SA status
DSP BTSIPSECSA: IDTYPE=BYID, BTSID=0, CN=0, SRN=0, SN=4, SPGN="policy",
SPSN=1;
//Querying the configuration information about the rules in the BTS ACL
LST BTSACLRULE: IDTYPE=BYID, BTSID=0, RULETYPE=ADV, LSTFORMAT=VERTICAL;
//Querying the status of the IPSec dual channels
DSP BTSIPSECDTNL: IDTYPE=BYID, BTSID=0, DUALID=0;
//Deleting the binding relationship between the IPSec security policy
group the corresponding port


Feature Activation Guide PDF

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

Feature Activation Guide PDF

Uploaded by

Copyright:

Available Formats

GBSS14.

Feature Activation Guide

HUAWEI TECHNOLOGIES CO., LTD.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Issue 06 (2013-04-15) Huawei Proprietary and Confidential i

About This Document

Product Name Product Version

Issue 06 (2013-04-15) Huawei Proprietary and Confidential ii

Issue 06 (2013-04-15) Huawei Proprietary and Confidential iii

13 Configuring Radio Link Management

14 Configuring Faulty Management

15 Configuring BTS Software Management

16 Configuring Combined Cabinets and Cabinet Groups of BTSs

17 Configuring Connection Inter BSC over IP

18 Configuring Link Aggregation

19 Configuring Intelligent Shutdown of TRX Due to PSU Failure

20 Configuring Call-Based Flow Control

21 Configuring Pre-Processing of Measurement Report

22 Configuring System Information Sending

23 Configuring Daylight Saving Time

24 Configuring SDCCH Dynamic Adjustment

Issue 06 (2013-04-15) Huawei Proprietary and Confidential iv

Issue 06 (2013-04-15) Huawei Proprietary and Confidential v

37 Configuring PDCH Dynamic Adjustment

Issue 06 (2013-04-15) Huawei Proprietary and Confidential vi

Issue 06 (2013-04-15) Huawei Proprietary and Confidential vii

Issue 06 (2013-04-15) Huawei Proprietary and Confidential viii

70 Configuring LCS (cell ID + TA)

Issue 06 (2013-04-15) Huawei Proprietary and Confidential ix

82 Configuring Streaming QoS(GBR)

Issue 06 (2013-04-15) Huawei Proprietary and Confidential x

Issue 06 (2013-04-15) Huawei Proprietary and Confidential xi

Issue 06 (2013-04-15) Huawei Proprietary and Confidential xii

Issue 06 (2013-04-15) Huawei Proprietary and Confidential xiii

122 Configuring Active Backup Power Control

123 Configuring Power Optimization Based on Channel Type

124 Configuring PSU Smart Control

125 Configuring Enhanced BCCH Power Consumption Optimization

126 Configuring Dynamic Cell Power Off

127 Configuring TRX Working Voltage Adjustment

128 Configuring Multi-Carrier Intelligent Voltage Regulation

129 Configuring Flex Abis

130 Configuring BTS Local Switch

131 Configuring Abis Transmission Optimization

132 Configuring Abis Congestion Trigger HR Distribution

133 Configuring Flex Ater

134 Configuring BSC Local Switch

Issue 06 (2013-04-15) Huawei Proprietary and Confidential xiv

Issue 06 (2013-04-15) Huawei Proprietary and Confidential xv

147 Configuring TDM/IP Dual Transmission over A Interface

Issue 06 (2013-04-15) Huawei Proprietary and Confidential xvi

Issue 06 (2013-04-15) Huawei Proprietary and Confidential xvii

Issue 06 (2013-04-15) Huawei Proprietary and Confidential xviii

Issue 06 (2013-04-15) Huawei Proprietary and Confidential xix

194 Configuring Mega BSC

195 Configuring PS Downlink DTX

196 Configuring PS Uplink DTX

197 Configuring Automatic Frequency Correction (AFC)

198 Configuring Fast Move Handover

199 Configuring Chain Cell Handover

200 Configuring Multi-Site Cell

201 Configuring PS Automatic Frequency Correction (PS AFC)