GBSS9.0 Network Impact Report

GBSS9.
0
Network Impact Report

Issue 02
Date 2010-10-08

HUAWEI TECHNOLOGIES CO., LTD.

Issue 02 (2010-10-08) Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd
i

Copyright Huawei Technologies Co., Ltd. 2011. All rights reserved.
No part of this document may be reproduced or transmitted in any form or by any means without prior
written consent of Huawei Technologies Co., Ltd.

Trademarks and Permissions
and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective
holders.

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

Huawei Technologies Co., Ltd.
Address: Huawei Industrial Base
Bantian, Longgang
Shenzhen 518129
People's Republic of China
Website: http://www.huawei.com
Email: support@huawei.com

GBSS9.0
Network Impact Report About This Document
ii

About This Document
Purpose
This document describes the impacts of new and enhanced GBSS9.0 features on GBSS8.1.
This document also provides the required information for network planning personnel and
operation and maintenance (OM) personnel to estimate and prepare for upgrades to GBSS9.0.
This document is for reference only, and is subject to change during the development of this
new release. Some detailed information will be provided after General Availability (GA).
Intended Audience
This document is intended for:
Network planning engineers
System engineers

Network operators
Change History
Changes between document issues are cumulative. The latest document issue contains all the
changes in earlier issues.
Issue 02 (2010-10-08)
This issue is the first official release, which incorporates the following changes:
The document template is updated.
1 Overview
The contents are modified.
1 Overview
The description of OSS changes is added.
3 Impacts of New and Enhanced Features in GBSS9.0 on GBSS8.1
The description of some features is modified.
3 Impacts of New and Enhanced Features in GBSS9.0 on GBSS8.1
Information about impacts of features such as GBFD-111705 GSM Flow Control is
added.
GBSS9.0
Network Impact Report About This Document
iii

Issue 01 (2009-10-31)
This is the initial draft.
GBSS9.0
Network Impact Report Contents
iv

Contents
About This Document .................................................................................................................... ii
1 Overview ...................................................................................................................................... 1-1
1.1 Capacity and Performance ............................................................................................................................ 1-1
1.1.1 BSC ...................................................................................................................................................... 1-1
1.1.2 BTS ...................................................................................................................................................... 1-2
1.1.3 M2000 .................................................................................................................................................. 1-2
1.2 Hardware ....................................................................................................................................................... 1-2
1.2.1 BSC ...................................................................................................................................................... 1-2
1.2.2 BTS ...................................................................................................................................................... 1-2
1.2.3 M2000 .................................................................................................................................................. 1-2
1.3 OSS ............................................................................................................................................................... 1-3
1.3.1 Overview .............................................................................................................................................. 1-3
1.3.2 BSC6900 LMT ..................................................................................................................................... 1-4
1.3.3 CME ..................................................................................................................................................... 1-6
1.4 Upgrade Process ............................................................................................................................................ 1-7
1.5 Interfaces ....................................................................................................................................................... 1-8
1.5.1 Inter-NE Interface ................................................................................................................................ 1-8
1.5.2 Man-Machine Interface ........................................................................................................................ 1-8
1.6 Operation ....................................................................................................................................................... 1-8
2 Summary of Feature Impacts ................................................................................................... 2-1
2.1 New and Enhanced Features ......................................................................................................................... 2-1
2.2 Dependency on Other Features ..................................................................................................................... 2-3
2.3 Dependency on NEs ...................................................................................................................................... 2-8
3 Impacts of New and Enhanced Features in GBSS9.0 on GBSS8.1 ................................... 3-1
3.1 MRFD-210301 Configuration Management ................................................................................................. 3-1
3.1.1 Description ........................................................................................................................................... 3-1
3.1.2 Capacity and Performance ................................................................................................................... 3-2
3.1.3 Interfaces .............................................................................................................................................. 3-2
3.1.4 Operation ............................................................................................................................................. 3-2
3.2 MRFD-210310 BTS/NodeB Software USB Download ................................................................................ 3-3
3.2.1 Description ........................................................................................................................................... 3-3
GBSS9.0
v

3.2.3 Interfaces .............................................................................................................................................. 3-3
3.2.4 Operation ............................................................................................................................................. 3-4
3.3 MRFD-210402 BTS/NodeB Software Management .................................................................................... 3-4
3.3.1 Description ........................................................................................................................................... 3-4
3.3.3 Interfaces .............................................................................................................................................. 3-4
3.3.4 Operation ............................................................................................................................................. 3-5
3.4 MRFD-210103 Link Aggregation ................................................................................................................. 3-5
3.4.1 Description ........................................................................................................................................... 3-5
3.4.3 Interfaces .............................................................................................................................................. 3-6
3.4.4 Operation ............................................................................................................................................. 3-6
3.5 MRFD-210104 BSC/RNC Resource Sharing ............................................................................................... 3-6
3.5.1 Description ........................................................................................................................................... 3-6
3.5.3 Interfaces .............................................................................................................................................. 3-7
3.5.4 Operation ............................................................................................................................................. 3-7
3.6 GBFD-117804 Intelligent Shutdown of TRX Due to PSU Failure ............................................................... 3-7
3.6.1 Description ........................................................................................................................................... 3-7
3.6.3 Interfaces .............................................................................................................................................. 3-7
3.6.4 Operation ............................................................................................................................................. 3-8
3.7 GBFD-113701 Frequency Hopping (RF Hopping, baseband Hopping) ....................................................... 3-8
3.7.1 Description ........................................................................................................................................... 3-8
3.7.3 Interfaces .............................................................................................................................................. 3-8
3.7.4 Operation ............................................................................................................................................. 3-8
3.8 GBFD-118606 Clock over IP ........................................................................................................................ 3-9
3.8.1 Description ........................................................................................................................................... 3-9
3.8.3 Interfaces .............................................................................................................................................. 3-9
3.8.4 Operation ............................................................................................................................................. 3-9
3.9 GBFD-118620 Clock over IP Support 1588V2 ............................................................................................. 3-9
3.9.1 Description ........................................................................................................................................... 3-9
3.9.2 Capacity and Performance ................................................................................................................. 3-10
3.9.3 Interfaces ............................................................................................................................................ 3-11
3.9.4 Operation ........................................................................................................................................... 3-11
3.10 GBFD-111610 Dynamic Cell Power Off .................................................................................................. 3-11
3.10.1 Description ....................................................................................................................................... 3-11
3.10.2 Capacity and Performance ............................................................................................................... 3-11
3.10.3 Interfaces .......................................................................................................................................... 3-12
3.10.4 Operation.......................................................................................................................................... 3-12
GBSS9.0
vi

3.11 GBFD-116902 Ater Compression Transmission ....................................................................................... 3-12
3.11.1 Description ....................................................................................................................................... 3-12
3.11.3 Interfaces .......................................................................................................................................... 3-13
3.11.4 Operation .......................................................................................................................................... 3-13
3.12 GBFD-117401 MSC Pool ......................................................................................................................... 3-14
3.12.1 Description ....................................................................................................................................... 3-14
3.12.3 Interfaces .......................................................................................................................................... 3-14
3.12.4 Operation.......................................................................................................................................... 3-14
3.13 GBFD-113725 BSC Node Redundancy .................................................................................................... 3-15
3.13.1 Description ....................................................................................................................................... 3-15
3.13.3 Interfaces .......................................................................................................................................... 3-16
3.13.4 Operation.......................................................................................................................................... 3-16
3.14 GBFD-113726 TC Pool ............................................................................................................................. 3-16
3.14.1 Description ....................................................................................................................................... 3-16
3.14.3 Interfaces .......................................................................................................................................... 3-18
3.14.4 Operation.......................................................................................................................................... 3-18
3.15 GBFD-113728 OML Backup .................................................................................................................... 3-19
3.15.1 Description ....................................................................................................................................... 3-19
3.16 GBFD-114325 Fast 3G Reselection at 2G CS Call Release ..................................................................... 3-19
3.16.1 Description ....................................................................................................................................... 3-19
3.16.3 Interfaces .......................................................................................................................................... 3-20
3.16.4 Operation.......................................................................................................................................... 3-20
3.17 GBFD-115701 TFO................................................................................................................................... 3-20
3.17.1 Description ....................................................................................................................................... 3-20
3.17.3 Interfaces .......................................................................................................................................... 3-21
3.17.4 Operation.......................................................................................................................................... 3-21
3.18 GBFD-115703 Automatic Noise Compensation (ANC) ........................................................................... 3-22
3.18.1 Description ....................................................................................................................................... 3-22
3.18.3 Interfaces .......................................................................................................................................... 3-22
3.18.4 Operation.......................................................................................................................................... 3-22
3.19 GBFD-115704 Enhancement Packet Loss Concealment (EPLC) ............................................................. 3-23
3.19.1 Description ....................................................................................................................................... 3-23
3.19.3 Interfaces .......................................................................................................................................... 3-23
GBSS9.0
vii

3.19.4 Operation.......................................................................................................................................... 3-23
3.20 GBFD-115506 AMR Coding Rate Threshold Adaptive Adjustment......................................................... 3-23
3.20.1 Description ....................................................................................................................................... 3-23
3.20.3 Interfaces .......................................................................................................................................... 3-24
3.20.4 Operation.......................................................................................................................................... 3-24
3.21 GBFD-115507 WB AMR .......................................................................................................................... 3-24
3.21.1 Description ....................................................................................................................................... 3-24
3.21.3 Interfaces .......................................................................................................................................... 3-25
3.21.4 Operation.......................................................................................................................................... 3-25
3.22 GBFD-119906 Conversational QoS .......................................................................................................... 3-25
3.22.1 Description ....................................................................................................................................... 3-25
3.22.3 Interfaces .......................................................................................................................................... 3-26
3.22.4 Operation.......................................................................................................................................... 3-26
3.23 GBFD-119502 PS Handover ..................................................................................................................... 3-27
3.23.1 Description ....................................................................................................................................... 3-27
3.23.3 Interfaces .......................................................................................................................................... 3-27
3.23.4 Operation.......................................................................................................................................... 3-27
3.24 GBFD-119503 Early TBF Establishment .................................................................................................. 3-28
3.24.1 Description ....................................................................................................................................... 3-28
3.24.3 Interfaces .......................................................................................................................................... 3-28
3.24.4 Operation.......................................................................................................................................... 3-29
3.25 GBFD-115002 Flow Control Based on Cell Priority ................................................................................ 3-29
3.25.1 Description ....................................................................................................................................... 3-29
3.25.3 Interfaces .......................................................................................................................................... 3-29
3.25.4 Operation.......................................................................................................................................... 3-29
3.26 GBFD-118601 Abis over IP ...................................................................................................................... 3-30
3.26.1 Description ....................................................................................................................................... 3-30
3.26.3 Interfaces .......................................................................................................................................... 3-30
3.26.4 Operation.......................................................................................................................................... 3-30
3.27 GBFD-118611 Abis IP over E1/T1 ........................................................................................................... 3-30
3.27.1 Description ....................................................................................................................................... 3-30
3.27.3 Interfaces .......................................................................................................................................... 3-32
3.27.4 Operation.......................................................................................................................................... 3-32
3.28 GBFD-118602 A over IP ........................................................................................................................... 3-32
GBSS9.0
viii

3.28.1 Description ....................................................................................................................................... 3-32
3.28.3 Interfaces .......................................................................................................................................... 3-36
3.28.4 Operation.......................................................................................................................................... 3-36
3.29 GBFD-118622 A IP over E1/T1 ................................................................................................................ 3-37
3.29.1 Description ....................................................................................................................................... 3-37
3.29.3 Interfaces .......................................................................................................................................... 3-38
3.29.4 Operation.......................................................................................................................................... 3-38
3.30 GBFD-118610 UDP MUX for A Transmission ......................................................................................... 3-39
3.30.1 Description ....................................................................................................................................... 3-39
3.30.3 Interfaces .......................................................................................................................................... 3-39
3.30.4 Operation.......................................................................................................................................... 3-39
3.31 GBFD-118609 IP Fault Detection Based on BFD ..................................................................................... 3-40
3.31.1 Description ....................................................................................................................................... 3-40
3.31.3 Interfaces .......................................................................................................................................... 3-41
3.31.4 Operation.......................................................................................................................................... 3-41
3.32 GBFD-118630 Ethernet OAM .................................................................................................................. 3-41
3.32.1 Description ....................................................................................................................................... 3-41
3.32.3 Interfaces .......................................................................................................................................... 3-42
3.32.4 Operation.......................................................................................................................................... 3-43
3.33 GBFD-510801 MSRD............................................................................................................................... 3-44
3.33.1 Description ....................................................................................................................................... 3-44
3.33.3 Interfaces .......................................................................................................................................... 3-44
3.33.4 Operation.......................................................................................................................................... 3-44
3.34 GBFD-510802 Dual Carriers in Downlink ............................................................................................... 3-45
3.34.1 Description ....................................................................................................................................... 3-45
3.34.3 Interfaces .......................................................................................................................................... 3-45
3.34.4 Operation.......................................................................................................................................... 3-45
3.35 GBFD-510803 Uplink EGPRS2-A ........................................................................................................... 3-46
3.35.1 Description ....................................................................................................................................... 3-46
3.35.3 Interfaces .......................................................................................................................................... 3-47
3.35.4 Operation.......................................................................................................................................... 3-48
3.36 GBFD-510804 Downlink EGPRS2-A ...................................................................................................... 3-48
3.36.1 Description ....................................................................................................................................... 3-48
GBSS9.0
ix

3.36.3 Interfaces .......................................................................................................................................... 3-49
3.36.4 Operation.......................................................................................................................................... 3-50
3.37 GBFD-510805 Latency Reduction ............................................................................................................ 3-50
3.37.1 Description ....................................................................................................................................... 3-50
3.37.3 Interfaces .......................................................................................................................................... 3-51
3.37.4 Operation.......................................................................................................................................... 3-51
3.38 GBFD-510901 2G/3G Neighboring Cell Automatic Optimization ........................................................... 3-52
3.38.1 Description ....................................................................................................................................... 3-52
3.38.3 Interfaces .......................................................................................................................................... 3-53
3.38.4 Operation.......................................................................................................................................... 3-53
3.39 GBFD-511001 License Control for Urgency ............................................................................................ 3-53
3.39.1 Description ....................................................................................................................................... 3-53
3.39.3 Interfaces .......................................................................................................................................... 3-54
3.39.4 Operation.......................................................................................................................................... 3-54
3.40 GBFD-511101 Load Based Handover Enhancement on Iur-g .................................................................. 3-54
3.40.1 Description ....................................................................................................................................... 3-54
3.40.3 Interfaces .......................................................................................................................................... 3-55
3.40.4 Operation.......................................................................................................................................... 3-55
3.41 GBFD-111705 GSM Flow Control ........................................................................................................... 3-56
3.41.1 Description ....................................................................................................................................... 3-56
3.41.3 Interfaces .......................................................................................................................................... 3-57
3.41.4 Operation.......................................................................................................................................... 3-57
3.42 GBFD-114302 GSM/TD-SCDMA Interoperability .................................................................................. 3-57
3.42.1 Description ....................................................................................................................................... 3-57
3.42.3 Interfaces .......................................................................................................................................... 3-58
3.42.4 Operation.......................................................................................................................................... 3-58
3.43 PS Channel Resources Load Sharing ........................................................................................................ 3-58
3.43.1 Description ....................................................................................................................................... 3-58
3.43.3 Interfaces .......................................................................................................................................... 3-58
3.43.4 Operation.......................................................................................................................................... 3-59
3.44 GBFD-119205 Dynamically Adjusting the RRBP Frequency .................................................................. 3-59
3.44.1 Description ....................................................................................................................................... 3-59
3.44.3 Interfaces .......................................................................................................................................... 3-59
3.44.4 Operation.......................................................................................................................................... 3-59
GBSS9.0
x

3.45 PS Services (EGPRS and GPRS Services) ................................................................................................ 3-60
3.45.1 Description ....................................................................................................................................... 3-60
3.45.3 Interfaces .......................................................................................................................................... 3-60
3.45.4 Operation.......................................................................................................................................... 3-60
3.46 GBFD-119501 Adaptive Adjustment of Uplink and Downlink Channels ................................................. 3-61
3.46.1 Description ....................................................................................................................................... 3-61
3.46.3 Interfaces .......................................................................................................................................... 3-61
3.46.4 Operation.......................................................................................................................................... 3-61
3.47 GBFD-110607 Direct Retry ...................................................................................................................... 3-61
3.47.1 Description ....................................................................................................................................... 3-61
3.47.3 Interfaces .......................................................................................................................................... 3-62
3.47.4 Operation.......................................................................................................................................... 3-62
3.48 GBFD-110303 Paging ............................................................................................................................... 3-62
3.48.1 Description ....................................................................................................................................... 3-62
3.48.3 Operation.......................................................................................................................................... 3-64
3.49 GBFD-115902 Transmit Diversity ............................................................................................................ 3-64
3.49.1 Description ....................................................................................................................................... 3-64
3.49.3 Interfaces .......................................................................................................................................... 3-65
3.49.4 Operation.......................................................................................................................................... 3-65
3.50 GBFD-117501 Enhanced Measurement Report (EMR) ............................................................................ 3-65
3.50.1 Description ....................................................................................................................................... 3-65
3.50.3 Interfaces .......................................................................................................................................... 3-67
3.50.4 Operation.......................................................................................................................................... 3-67
3.51 MRFD-210601 Connection with TMA (Tower Mounted Amplifier) ........................................................ 3-67
3.51.1 Description ....................................................................................................................................... 3-67
3.51.3 Interfaces .......................................................................................................................................... 3-68
3.51.4 Operation.......................................................................................................................................... 3-68

GBSS9.0
Network Impact Report 1 Overview
1-1

1 Overview
1.1 Capacity and Performance
1.1.1 BSC
Capacity of CS Services
The new signaling processing board (XPUb) and interface boards (POUc, FG2c, and GOUc)
are added to the BSC6900 for higher traffic processing capabilities. With the new boards, the
BSC6900 can process a maximum of 19,500 Erlang CS traffic.
The BSC6900 is compatible with BSC6000 hardware. Therefore, the BSC6000 can be
upgraded to the BSC6900 smoothly. If the BSC6900 uses the same hardware as the BSC6000,
the capabilities of the BSC6900 and BSC6000 are the same, that is, a maximum of 13,000
Erlang CS traffic.
Capacity of PS Services
When configured with an external PCU, the BSC6900 has the same PS service capacity as the
BSC6000.
When configured with an internal PCU, the BSC6900 supports a maximum of 12,288
simultaneously activated PDCHs, compared to 8,192 PDCHs supported by the BSC6000. The
BSC6900 also supports a maximum throughput of 1,024 Mbit/s on the Gb interface,
compared to 512 Mbit/s supported by the BSC6000.
Number of TRXs
The BSC6900 configured with new boards supports a maximum of 3,072 TRXs.
If the BSC6900 uses the same hardware as the BSC6000, the capabilities of the BSC6900 and
BSC6000 are the same, that is, a maximum of 2,048 TRXs.
SingleRAN
The BSC6900 is used for SingleRAN and supports the GU dual mode. The BSC6900 can be
flexibly configured as GSM Only (GO), UMTS Only (UO), or GSM&UMTS (GU) mode.
This facilitates the network evolution from GSM to UMTS. To be compatible with both GSM
and UMTS user planes, the processing mechanism of the BSC6900 user plane processing
board (DPU) is modified.
GBSS9.0
1-2

1.1.2 BTS
The capacity and performance of the BTSs remain unchanged.
1.1.3 M2000
When the M2000 V200R009 uses the new model SUN M4000/M5000, the 5+1 SLS
multi-server load sharing system can manage a maximum of 150,000 TRXs.
When the M2000 V200R009 uses other models, it has the same management capability as the
M2000 of earlier versions.
1.2 Hardware
1.2.1 BSC
The BSC6900 is compatible with BSC6000 hardware. Therefore, the BSC6000 can be
upgraded to the BSC6900 without replacing the hardware.
The BSC6900 is added with the following boards:
XPUb: Signaling processing board. This new type of signaling processing board helps
increase the system traffic capacity.
POUc: Interface board. This board provides the STM-1 port for the Abis, Ater, A, Gb,
and Pb interfaces and supports TDM/IP transmission over the channelized STM-1/OC-3
port.
FG2c: Interface board. This board provides the FE/GE electrical port for the Abis, A, and
Gb interfaces and uses IP over Ethernet transmission.
GOUc: Interface board. This board provides the GE optical port for the Abis, A, and Gb
interfaces and uses IP over Ethernet transmission.
1.2.2 BTS
The 3900 series base stations are added with the following boards:
USCU: Universal Satellite Clock Unit. The USCU is of two types: USCUb1 and
USCUb2. The USCUb1 supports Global Positioning System (GPS), and the USCUb2
supports both GPS and Global Navigation Satellite System (GLONASS). The USCU
performs clock synchronization or obtains accurate clock signals.
GTMUb: Basic transmission and control entity of the BBU. The GTMUb has enhanced
functions compared to the GTMU, and the GTMUb has a different exterior from the
GTMU. The GTMUb is compatible with all functions of the GTMU, and therefore can
replace the GTMU without making any change.
The 3012 series base stations are not added with any new hardware.
1.2.3 M2000
No additional hardware is required for the M2000 in the existing sites. For new sites, the SUN
M4000/M5000 model is used.
GBSS9.0
1-3

1.3 OSS
1.3.1 Overview
Figure 1-1 shows the integrated OSS solution for GBSS9.0.
Figure 1-1 Integrated OSS solution

M2000/CME
server
M2000/CME
client
BSC6900
BSC6900
BSC6900
BTS BTS
BTS
Web LMT
Centralized
maintenance
Single-point
operation

Table 1-1 lists the bandwidth required when the OSS manages the BSC6900.
Table 1-1 Bandwidth requirements
Number of BTSs
Under the BSC6900
100 200 400 600 800 1,000
Total Bandwidth
Required by the
M2000 (kbit/s)
1,400 1,500 1,700 1,900 2,100 2,300

The BSC6900 LMT differs greatly from the BSC6000 LMT, which are described as follows:
The BSC6900 LMT is accessed through the Web. Therefore, no client is required.
GBSS9.0
1-4

The GUI configuration based on the BSC6000 LMT is transferred to the CME, enabling
unified configuration management for the entire network.
Figure 1-2 shows two major differences between the BSC6900 LMT and the BSC6000 LMT.
Figure 1-2 Major differences between the BSC6900 LMT and the BSC6000 LMT
GBSS9.0
CME
GBSS8.1
BSC6000 LMT
BSC6900 Web LMT
(BSC6900 W
eb LM
T not
supporting G
UI configuration)
CME
MML
CME supporting GUI
configuration
BSC6900 Web LMT supporting
MML configuration

1.3.2 BSC6900 LMT
On the GUI of the BSC6900 LMT, users can perform BSC6900 operation and maintenance by
running MML commands, viewing the command execution results and alarms, tracing
messages, and monitoring performance.
PCs accessing the BSC6900 LMT must meet the requirements for hardware and software
configuration and requirements for port connection and communication capabilities.
Hardware Configuration Requirements
Table 1-2 lists hardware configuration requirements for PCs accessing the BSC6900 LMT.
Table 1-2 Hardware configuration requirements
Configuration
Item
Quantity Recommended Configuration Minimum
Configuration
CPU 1 2.8 GHz or higher 866 MHz
GBSS9.0
1-5

Configuration
Item
Quantity Recommended Configuration Minimum
Configuration
RAM 1 1 GB 512 MB
Hard disk 1 80 GB 10 GB
Display resolution - 1024x768 or higher 1024x768
CD-ROM 1 - -
Network adapter 1 10 Mbit/s or 100 Mbit/s 10 Mbit/s or 100
Mbit/s
Other devices 5x1 Keyboard, mouse, Modem, sound
card, and sound box
Keyboard and mouse

Software Configuration Requirements
Table 1-3 lists software configuration requirements for the PC accessing the BSC6900 LMT.
Table 1-3 Software configuration requirements
Configuration
Item
Recommended Configuration
Operating system Microsoft Windows XP Professional SP02, Microsoft Windows
2003, Microsoft Windows 2008, or Microsoft Windows Vista
NOTE

If operators log in to the BSC6900 LMT using the IE 6.0 browser on PCs
running the Microsoft Windows XP Professional SP02 or Microsoft Windows
2003, security patches KB944338 and KB960714 must be installed on the
PC.
Default language of
the operating system
English
Web browser Microsoft Internet Explorer 6.0.2900.2180.xpsp_sp2_gdr or later
versions, Microsoft Internet Explorer 7.0.5730.13 or later versions,
Microsoft Internet Explorer 8.0.6001.18702 or later versions, or
official releases of FireFox 3.0 to FireFox 3.5
NOTE

The security level of the Web browser must be set to medium or lower.
Otherwise, the BSC6900 LMT cannot be displayed.
JAVA Platform
Standard Edition
Runtime
Environment (Java
JRE)
Official release of jre-6u11-windows-i586-p-s.exe or later versions
NOTE

This plug-in can be downloaded from http://java.com or
http://support.huawei.com.

GBSS9.0
1-6

To ensure stable functioning of the BSC6900 LMT, use the recommended configuration
for the BSC6900 LMT.
The current version of BSC6900 LMT is compatible only with a 32-bit operating system
and Web browser.
Ports
If there is a firewall between a PC and the BSC6900 LMT, ports 80, 20, and 21 must be
enabled to allow access to the BSC6900 LMT by using the Web browser.
NOTE

Port 80 is the default port used for Web browsing through HTTP.
Ports 20 and 21 are used for file transfer through FTP.
Communication Capability
A PC using the BSC6900 LMT must comply with the TCP/IP protocol and meet the
requirements for efficient bandwidth, as described in Table 1-4.
Table 1-4 Requirements for efficient bandwidth
Configuration
Item
Protocol Recommended
Configuration
Minimum
Configuration
Requirements for
efficient
bandwidth
HTTP 2 Mbit/s or higher 512 kbit/s

NOTE

The speed for accessing the BSC6900 LMT depends on the bandwidth.
The effective bandwidth is the portion of bandwidth used by the BSC6900 LMT. When bandwidth
resources are occupied by many other programs, it may become difficult to access the BSC6900
LMT even if a 2 Mbit/s bandwidth is available.
1.3.3 CME
CM Express (known as CME) is the major component of the integrated configuration solution
of Huawei SingleRAN. It performs configuration for the entire network during initial
deployment, network expansion, base station swapping, and routine reconfiguration of GSM
and UMTS access networks. The main features of the CME are as follows:
Multi-network integrated configuration solution
It supports GO, UO, and GU products, and is applicable to the scenarios where
multiple types of NEs are deployed. Therefore, it serves as a powerful configuration
solution for Huawei SingleRAN.
It is applicable to scenarios such as deployment, network expansion, optimization,
base station swapping, and reconfiguration.
Reliable multi-area design and data check over the entire network
GBSS9.0
1-7

The workspace is separated into the current data area and planned data area.
Customers can plan and modify configuration data in the planned data area, which
does not affect ongoing services before data activation. The separated workspaces
enhance the reliability and security of configuration on the CME and support
concurrent operations of multiple operators.
Logic check of GSM and UMTS global data is supported.
Pre-activation check can be performed on global data. During pre-activation check,
the CME checks data integrity, redundancy, and consistency. Some detected errors
can be rectified automatically to ensure the secured and reliable configuration of the
radio network.
Highly reliable rollback of configuration is supported.
The CME can perform quick rollback on a configuration task if the configuration
result is unsatisfactory. This allows services to return to the state before the
configuration and therefore guarantees stable operation of the network.
Strong capability of browsing and searching global data is provided.
The CME helps users quickly locate useful information among a large amount of data
to prepare for future planning and tuning.
Efficient scenario-based configuration for global data
The CME can manage configuration of global data, which helps telecom operators
improve OM efficiency for the entire network compared with single-point
configuration.
Scenario-based task design, user-friendly configuration wizard, and automatic
calculation simplify data configuration and lower skill requirements.
The CME provides various templates, for example, the base station template, cell
template, and interface template. Based on these templates, batch deployment and
quick network expansion can be achieved, and configuration can be performed
efficiently. This helps lower the OPEX.
The CME provides a device panel for illustrating the hardware configuration of
various NEs and supports corresponding configuration operations on the panel. This
facilitates configuration and management of NEs.
The CME supports automatic update of neighboring relationship during integrated
swapping of base stations. This facilitates data configuration and therefore ensures
smooth swapping.
Flexible interconnection and all-process integration
The CME is interconnected with the customer data planning tool through the northbound
configuration interface. The CME performs data planning, modification, and activation
automatically during deployment, swapping, network optimization, and neighboring
relationship optimization.
1.4 Upgrade Process
This section describes the process for upgrading GBSS8.1 to GBSS9.0. Before upgrading the
software, install associated hardware and obtain the required licenses.
1. Upgrade the M2000 to iManager M2000-II V200R009.
2. Upgrade the CME to CME V200R009.
3. Upgrade the BSC6000 V900R008 to BSC6900 V900R011.
4. Upgrade base stations from GBSS8.1 to GBSS9.0.
GBSS9.0
1-8

For detailed upgrade procedures of all NEs, see corresponding upgrade guides.
1.5 Interfaces
1.5.1 Inter-NE Interface
In GBSS9.0, all interfaces between NEs comply with the 3GPP specifications.
A interface: The A interface based on GBSS8.1 complies with 3GPP Release 99 and Release 4,
and the A interface based on GBSS9.0 complies with 3GPP Release 6.
Gb interface: The Gb interface based on GBSS8.1 complies with 3GPP Release 99 and
Release 4, and the Gb interface based on GBSS9.0 complies with 3GPP Release 6.
The Lb interface that complies with 3GPP Release 6 is supported.
The Abis interface is a Huawei proprietary interface, complying with 3GPP Release 6.
1.5.2 Man-Machine Interface
Users use the Web-based BSC6900 LMT to perform operation and maintenance by running
MML commands. MML commands for the BSC6900 are modified for the following reasons:
The physical and logical models are decoupled.
Conflicts in MML command names occur after GSM and UMTS share an operation and
maintenance client (OMC). For example, ADD CELL is changed to ADD GCELL due
to such conflicts.
MML commands associated with transmission are changed because OM is shared by GU
equipment after GSM and UMTS share an OMC. Most of the MML commands follow
the RNC commands.
For details about the man-machine interface, see description about each feature in chapter 3
"Impacts of New and Enhanced Features in GBSS9.0 on GBSS8.1."
1.6 Operation
For information about impacts of each feature on operation, see description about each feature
in chapter 3 "Impacts of New and Enhanced Features in GBSS9.0 on GBSS8.1."
GBSS9.0
Network Impact Report 2 Summary of Feature Impacts
2-1

2 Summary of Feature Impacts
2.1 New and Enhanced Features
The new and enhanced features in GBSS9.0 are listed in Table 2-1.
Table 2-1 New and enhanced features in GBSS9.0
Solution Feature ID Feature Name New or
Enhanced
Basic or
Optional
Operation and
Maintenance
MRFD-210301 Configuration
Management
Enhanced Basic
MRFD-210310 BTS/NodeB Software
USB Download
New Basic
Software
Management
Management
Enhanced Basic
System Reliability MRFD-210103 Link aggregation New Basic
MRFD-210104 BSC/RNC Resource
Sharing
New Basic
GBFD-117804 Intelligent Shutdown
of TRX Due to PSU
Failure
New Basic
Frequency
Efficiency
Improvement
GBFD-113701 Frequency Hopping
(RF hopping,
baseband hopping)
Enhanced Optional
Network
Synchronization
GBFD-118606 Clock over IP Enhanced Optional
GBFD-118620 Clock over IP support
1588V2
New Optional
Energy Saving GBFD-111610 Dynamic Cell Power
Off
New Optional
A Transmission
Saving
GBFD-116902 Ater Compression
Transmission
New Optional
Network GBFD-117401 MSC Pool Enhanced Optional
GBSS9.0
2-2

Enhanced
Basic or
Optional
Reliability
GBFD-113725 BSC Node
Redundancy
New Optional
GBFD-113726 TC Pool New Optional
GBFD-113728 OML Backup New Optional
2G/3G Seamless
Coverage
GBFD-114325 Fast 3G Reselection at
2G CS Call Release
New Optional
CS General
Enhancement
GBFD-115701 TFO Enhanced Optional
GBFD-115703 Automatic Noise
Compensation (ANC)
New Optional
GBFD-115704 Enhancement Packet
Loss
Concealment(EPLC)
New Optional
AMR Package GBFD-115506 AMR Coding Rate
Threshold Adaptive
Adjustment
Enhanced Optional
GBFD-115507 WB AMR New Optional
PS QoS GBFD-119906 Conversational QoS New Optional
EGPRS Service
Enhancement
GBFD-119502 PS Handover New Optional
GBFD-119503 Early TBF
Establishment
New Optional
VIP Service
Support
GBFD-115002 Flow Control Based
on Cell Priority
New Optional
Abis over IP GBFD-118601 Abis over IP Enhanced Optional
GBFD-118611 Abis IP over E1/T1 New Optional
A over IP GBFD-118602 A over IP Enhanced Optional
GBFD-118622 A IP over E1/T1 New Optional
GBFD-118610 UDP MUX for A
Transmission
New Optional
GBFD-118609 IP Fault Detection
Based on BFD
New Optional
GBFD-118630 Ethernet OAM New Optional
EDGE Evolution GBFD-510801 MSRD New Optional
GBFD-510802 Dual Carriers in
Downlink
New Optional
GBFD-510803 Uplink EGPRS2-A New Optional
GBSS9.0
2-3

Enhanced
Basic or
Optional
GBFD-510804 Downlink EGPRS2-A New Optional
GBFD-510805 Latency Reduction New Optional
Performance
Analysis Toolkit
GBFD-510901 2G/3G Neighboring
Cell Automatic
Optimization
New Optional
Emergency
Communications
GBFD-511001 License Control for
Urgency
New Optional
2G/3G Common
Radio Resource
Management
Based on Iur-g
GBFD-511101 Load Based Handover
Enhancement on Iur-g
New Optional

2.2 Dependency on Other Features
Table 2-2 describes the dependency of each new and enhanced GBSS9.0 feature on other
features.
Table 2-2 Dependency on other features
Solution Feature ID Feature Name Dependency on Other Features
Operation and
Maintenance
Management
N/A
USB Download
N/A
Software
Management
Management
N/A
System
Reliability
MRFD-210103 Link aggregation N/A
Sharing
N/A
GBFD-117804 Intelligent Shutdown of
TRX Due to PSU
Failure
N/A
Frequency
Efficiency
Improvement
(RF hopping, baseband
hopping)
N/A
Network
Synchronization
GBFD-118606 Clock over IP An independent IP clock server is required.
1588V2
A clock server that complies with the
IEEE1588 V2 standards is required.
GBSS9.0
2-4

Off
This feature depends on the feature
GBFD-114401 Multi-band Sharing One
BSC.
A Transmission
Saving
Transmission
This feature and the feature GBFD-116901
Flex Ater are mutually exclusive.
Network
Reliability
GBFD-117401 MSC Pool N/A
GBFD-113725 BSC Node
Redundancy
This feature depends on the following
features:

GBFD-118601 Abis over IP

GBFD-118611 Abis IP over E1/T1

GBFD-118602 A over IP

GBFD-118622 A IP over E1/T1

GBFD-118603 Gb over IP
GBFD-113726 TC Pool This feature and the following features are
mutually exclusive:


GBFD-113728 OML Backup This feature and the following features are
mutually exclusive:

GBFD-117801 Ring Topology

GBFD-116601 Abis Bypass
2G/3G Seamless
Coverage
2G CS Call Release
N/A
CS General
Enhancement
GBFD-115701 TFO This feature and the following features are
mutually exclusive when this feature is used
by a single call:

GBFD-115601 Automatic Level Control
(ALC)

GBFD-115602 Acoustic Echo
Cancellation (AEC)

GBFD-115603 Automatic Noise Restraint
(ANR)

Compensation (ANC)

GBFD-115704 Enhancement Packet Loss
Concealment (EPLC)
Compensation (ANC)
This feature and the following features are
by a single call:

GBFD-115701 TFO

GBFD-115702 TrFO
GBSS9.0
2-5

Loss
Concealment(EPLC)
features:

GBFD-115501 AMR FR

GBFD-115502 AMR HR
This feature and the following features are
by a single call:

GBFD-115701 TFO

GBFD-115702 TrFO
Threshold Adaptive
Adjustment
N/A
GBFD-115507 WB AMR N/A
PS QoS GBFD-119906 Conversational QoS This feature depends on the feature
GBFD-510805 Latency Reduction.
EGPRS Service
Enhancement
GBFD-119502 PS Handover N/A
Establishment
GBFD-119203 Extended Uplink TBF.
VIP Service
Support
GBFD-115002 Flow Control Based on
Cell Priority
N/A
Abis IP GBFD-118601 Abis over IP This feature and the following features are
mutually exclusive:


GBFD-117701 BSC Local Switch

GBFD-117301 Flex Abis
GBFD-118611 Abis IP over E1/T1 This feature and the following features are
mutually exclusive:


GBFD-117701 BSC Local Switch

GBFD-117301 Flex Abis
GBSS9.0
2-6

A IP GBFD-118602 A over IP This feature and the following features are
mutually exclusive:

(ALC)

Cancellation (AEC)

(ANR)

Compensation (ANC)

Concealment (EPLC)

GBFD-115701 TFO
GBFD-118622 A IP over E1/T1 This feature and the following features are
mutually exclusive:

(ALC)

Cancellation (AEC)

(ANR)

Compensation (ANC)

Concealment (EPLC)

GBFD-115701 TFO
Transmission
features:


Based on BFD
This feature can be used only on the
GTMUb. It depends on the following
features:



GBFD-118630 Ethernet OAM This feature can be used only on the
GTMUb. It depends on the following
features:



GBSS9.0
2-7

EDGE Evolution GBFD-510801 MSRD This feature and the feature GBFD-510802
Dual Carriers in Downlink are mutually
exclusive.
Downlink
This feature and the feature GBFD-510801
MSRD are mutually exclusive.
GBFD-510803 Uplink EGPRS2-A This feature depends on the following
features:



GBFD-118401 Abis Transmission
Optimization
GBFD-510804 Downlink EGPRS2-A This feature depends on the following
features:



Optimization
GBFD-510805 Latency Reduction This feature depends on the following
features:



Optimization
Performance
Analysis Toolkit
Cell Automatic
Optimization
N/A
Emergency
Communications
Urgency
N/A
2G/3G Common
Radio Resource
Management
Based on Iur-g
WRFD-070004 Load Based 3G-2G
Handover Enhancement Based on Iur-g.

GBSS9.0
2-8

2.3 Dependency on NEs
Solution Feature ID Feature Name Dependency on Other NEs
MS Core
Network
Other NEs
Operation and
Maintenance
Management
N/A N/A N/A
USB Download
N/A N/A N/A
Software
Management
Management
N/A N/A N/A
System
Reliability
MRFD-210103 Link aggregation N/A N/A N/A
Sharing
N/A N/A N/A
GBFD-117804 Intelligent Shutdown of
TRX Due to PSU
Failure
N/A N/A N/A
Frequency
Efficiency
Improvement
(RF hopping, baseband
hopping)
N/A N/A N/A
Network
Synchronization
GBFD-118606 Clock over IP N/A N/A An
independent
IP clock
server is
required.
1588V2
N/A N/A A clock
server that
complies
with the
IEEE1588
V2 standards
is required.
Off
N/A N/A N/A
A Transmission
Saving
Transmission
N/A N/A N/A
Network
Reliability
GBFD-117401 MSC Pool N/A N/A N/A
GBFD-113725 BSC Node Redundancy N/A N/A N/A
GBFD-113726 TC Pool N/A N/A N/A
GBFD-113728 OML Backup N/A N/A N/A
GBSS9.0
2-9

MS Core
Network
Other NEs
2G/3G Seamless
Coverage
2G CS Call Release
The MS
must
support
this
feature.
N/A N/A
CS General
Enhancement
GBFD-115701 TFO The MS
must
support
this
feature.
The CN
must
support
this
feature.
N/A
Compensation (ANC)
N/A N/A N/A
Loss
Concealment(EPLC)
N/A N/A N/A
Threshold Adaptive
Adjustment
N/A N/A N/A
GBFD-115507 WB AMR The MS
must
support
this
feature.
The CN
must
support
this
feature.
N/A
PS QoS GBFD-119906 Conversational QoS The MS
must
support
this
feature.
The CN
must
support
this
feature.
N/A
EGPRS Service
Enhancement
GBFD-119502 PS Handover The MS
must
support
this
feature.
The CN
must
support
this
feature.
N/A
Establishment
The MS
must
support
this
feature.
N/A N/A
VIP Service
Support
GBFD-115002 Flow Control Based on
Cell Priority
N/A N/A N/A
Abis IP GBFD-118601 Abis over IP N/A N/A N/A
GBFD-118611 Abis IP over E1/T1 N/A N/A N/A
GBSS9.0
2-10

MS Core
Network
Other NEs
A IP GBFD-118602 A over IP N/A The CN
must
support
this
feature.
N/A
GBFD-118622 A IP over E1/T1 N/A The CN
must
support
this
feature.
N/A
Transmission
N/A The CN
must
support
this
feature.
N/A
Based on BFD
N/A N/A N/A
GBFD-118630 Ethernet OAM N/A N/A The peer
equipment
must support
this feature.
EDGE Evolution GBFD-510801 MSRD The MS
must
support
this
feature.
N/A N/A
Downlink
The MS
must
support
this
feature.
N/A N/A
GBFD-510803 Uplink EGPRS2-A The MS
must
support
this
feature.
N/A N/A
GBFD-510804 Downlink EGPRS2-A The MS
must
support
this
feature.
N/A N/A
GBSS9.0
2-11

MS Core
Network
Other NEs
GBFD-510805 Latency Reduction The MS
must
support
this
feature.
N/A N/A
Performance
Analysis Toolkit
Cell Automatic
Optimization
N/A N/A This feature
depends on
the M2000
and the
network
optimization
tool Nastar.
Emergency
Communications
Urgency
N/A N/A N/A
2G/3G Common
Radio Resource
Management
Based on Iur-g
N/A N/A N/A

GBSS9.0
3 Impacts of New and Enhanced Features in GBSS9.0 on
GBSS8.1
3-1

3 Impacts of New and Enhanced Features in
GBSS9.0 on GBSS8.1
This chapter describes the impacts of GBSS9.0 new and enhanced features on GBSS8.1 in
terms of capacity and performance, hardware, interfaces, and operation.
For the dependency of these features on other features, hardware, and NEs, see chapter 2
Summary of Feature Impacts.
3.1 MRFD-210301 Configuration Management
3.1.1 Description
The Configuration Management feature provides the following functions:
BSC6900 LMT based on Web
The BSC6900 LMT in Browser/Server mode provides the OM GUI for the BSC6900,
and the CME provides the configuration GUI for the BSC6900. The BSC6900 LMT
enables MML-based configuration and maintenance for the BSC6900 while eliminating
the need for an MML client.
With the BSC6900 Web LMT, users do not need to install client software. Users can
easily configure and maintain the BSC6900 by using the BSC6900 LMT without
installing and upgrading the client software.
Control of configuration rights
Configuration can be performed only on the BSC LMT, BTS LMT, or M2000 client.
Only users with configuration rights can add, delete, and modify the OMU data. Telecom
operators always have configuration rights. This feature ensures system reliability.
Whether to enable this feature is controlled by a configuration switch, which is turned
off by default.
Rollback of configuration on the BSC side
If NE data is incorrectly modified by using an MML command on the BSC6900 LMT,
operators can perform a rollback immediately by entering an MML command or clicking
the UNDO button in the upper right corner of the BSC6900 LMT. Some MML
commands do not support rollback because of chip incompatibility. The MML
commands that support rollback are listed in the MML help of the ADD
ROLLBACKPOINT command.
GBSS9.0
GBSS8.1
3-2

Data import and export
All MML-associated parameters can be imported and exported.
Data can be backed up in the original database format, and the backup data can be
restored on the NE of the same version. A tool for restoring backup data is available.
The CME provides the configuration GUI, but is incompatible with the .dat files
exported from the GBSS8.1 LMT.
Data in the .BCP format that is synchronized with the OSS data can be exported.
Data upgrade through MML commands
The GBSS8.1 data table can be directly upgraded, and configuration data must be
prepared on the LMT before an upgrade. GBSS9.0 data can be upgraded through MML
commands during the upgrade.
3.1.2 Capacity and Performance
System Capacity
No impact.
Network Performance
No impact.
3.1.3 Interfaces
Inter-NE Interface
The northbound interface changes because of the changes in the NE configuration model.
Man-Machine Interface
The supported MML commands and parameters change because of the changes in the NE
configuration model.
3.1.4 Operation
Configuration rights are controlled by using the following MML commands:
SET CMCTRLSW
LST CMCTRLSW
REQ CMCTRL
REL CMCTRL
FOC CMCTRL
LCK CMCTRL
ULK CMCTRL
LST CMCTRL
Rollback of configuration on the BSC side is performed by using the following MML
commands:
BEG UNDO
GBSS9.0
GBSS8.1
3-3

BEG REDO
BEG ROLLBACK
BEG FORWARD
ADD ROLLBACKPOINT
RMV ROLLBACKPOINT
LST ROLLBACKPOINT
LST ROLLBACKLOG
Data is imported or exported by using the following MML commands:
EXP CFGMML
BKP DB
3.2 MRFD-210310 BTS/NodeB Software USB Download
3.2.1 Description
The BTS/NodeB Software USB Download feature enables users to upgrade the BST/NodeB
software and configuration by using a USB storage device. Each 3900 series base station
provides a USB port for downloading and activating the host software stored on a USB
storage device.
With this feature, software upgrade no longer depends on Abis/Iub transmission. As a result,
the upgrade duration is shortened and sites can be deployed quickly at a low cost. After the
software is activated and the system begins to operate, hardware faults can be detected
according to the indicators on the BBU panel. In addition, the maintenance personnel do not
need to visit the site again as they can commission the software remotely.
System Capacity
No impact.
Network Performance
No impact.
3.2.3 Interfaces
Inter-NE Interface
No impact.
No impact.
GBSS9.0
GBSS8.1
3-4

3.2.4 Operation
Users need to perform the following operations to complete an upgrade:
Copy the software package to a specified directory on a USB storage device and insert the
USB storage device into the USB port on the main control board of the BTS. Then, observe
the indicator on the USB storage device and RUN indicator on the main control board to
ensure that the upgrade process is completed successfully.
3.3 MRFD-210402 BTS/NodeB Software Management
3.3.1 Description
The BTS/NodeB Software Management feature is enhanced in GBSS9.0. With this feature,
the BTS or NodeB does not need to be reset during patch installation.
Both the software version and configuration data of a BTS need to be upgraded when the BTS
is being upgraded from GBSS8.1 to GBSS9.0. The M2000 provides the function of upgrading
special configuration and software of the BTS. This function is classified into two modes:
Large-scale BTS upgrade
Small-scale BTS upgrade
In both the upgrade modes, the duration of service interruption is longer than that during the
upgrade from an earlier version to GBSS8.1. During a large-scale BTS upgrade, the BTSs and
BSC are reset. During a small-scale BTS upgrade, the BTSs and BSC are not reset. The
duration of service interruption is positively related to the number of BTSs being upgraded.
System Capacity
No impact.
Network Performance
No impact.
3.3.3 Interfaces
Inter-NE Interface
No impact.
A BTS patch package can be downloaded, removed, loaded, activated, deactivated, queried,
or confirmed by using MML commands.
GBSS9.0
GBSS8.1
3-5

3.3.4 Operation
To upgrade the software of a BTS from GBSS8.1 to GBSS9.0 on the M2000, create a task of
GBTS special configuration and software upgrade as follows: Choose Software > NE
Upgrade Task Management > NE Upgrade Task. Click Create and choose GBTS > GBTS
Special Configuration & Software Upgrade(GBTS) from the menu.
Associated operations can be performed by using the following MML commands:
DLD BTSPATCH: used to download a BTS patch package
RMV OMUBTSPATCH: used to remove a BTS patch package from the OMU
LST BTSPATCH: used to query the information about a BTS patch package
LOD BTSPATCH: used to load a BTS patch package
ACT BTSPATCH: used to activate a BTS patch package
DEA BTSPATCH: used to deactivate a BTS patch package
CON BTSPATCH: used to confirm a BTS patch package
RMV BTSPATCH: used to remove a BTS patch package
3.4 MRFD-210103 Link Aggregation
3.4.1 Description
Huawei GBSS/RAN supports the aggregation of two or more physical FE/GE ports into one
logical port to provide a high bandwidth for point-to-point transmission on the Ethernet. This
feature reduces the use of IP addresses and improves the operation and maintenance efficiency
of operators.
When a physical FE/GE port becomes faulty or the cable for the port is disconnected, the
faulty physical FE/GE port is removed from the logical port, and the remaining bandwidth
continues to serve IP applications. This enhances network reliability.
The Link Aggregation feature complies with the IEEE 802.3ad standard. This feature is
applicable to scenarios with high requirements for reliability, for example, port aggregation on
the BSC and the Hub NodeB. This feature must be supported by the peer devices, such as the
switch and BTS.
System Capacity
No impact.
Network Performance
No impact.
GBSS9.0
GBSS8.1
3-6

3.4.3 Interfaces
Inter-NE Interface
If the Link Aggregation feature is enabled on the BSC, the devices interconnected to the BSC
must also support this feature.
The Link Aggregation feature can be configured on the BSC.
3.4.4 Operation
ADD ETHTRK: used to add a trunk group
ADD ETHTRKLNK: used to add trunk links to a trunk group
ADD ETHTRKIP: used to add the IP addresses of a trunk group
RST ETHTRK: used to reset a trunk group
3.5 MRFD-210104 BSC/RNC Resource Sharing
3.5.1 Description
The BSC/RNC Resource Sharing feature is classified into user plane resource sharing and
control plane resource sharing.
Control plane resource sharing is related to CPU and memory usage. When the CPU usage of
a signaling processing unit is too high or its memory is insufficient, new calls are allocated to
other signaling processing units with a lower load.
In user plane resource sharing, resources are dynamically shared within the system in resource
pooling and load sharing manners. When a user plane processing unit is overloaded, new calls
are allocated to other user plane processing units with a lower load.
Resource pools for an MBSC are classified into the GSM control plane resource pool, GSM
user plane resource pool, UMTS control plane resource pool, and UMTS user plane resource
pool. Resources can be shared only within one pool, not between pools.
System Capacity
The implementation of resource pooling within the system enables the subracks to share
resources. This maximizes resource usage within the system.
Network Performance
The BSC/RNC Resource Sharing feature increases the resource usage and the call success
rate.
GBSS9.0
GBSS8.1
3-7

3.5.3 Interfaces
Inter-NE Interface
No impact.
No impact.
3.5.4 Operation
No impact.
3.6 GBFD-117804 Intelligent Shutdown of TRX Due to
PSU Failure
3.6.1 Description
When a BTS uses AC power input, power supply units (PSUs) are required for AC/DC
conversion. If some PSUs are faulty, the remaining PSUs may fail to provide efficient power
for the BTS. When this happens, PSU overcurrent protection takes effect, leading to the
power failure of the BTS.
To solve this problem, this feature enables the BTS to shut down some TRXs without
affecting services. The BTS determines the number of TRXs to be shut down and reports the
number to the BSC. The BSC then stops allocating new calls to these TRXs. When no service
is carried on these TRXs, the BTS shuts down the power amplifiers of the TRXs. After the
faulty PSUs are rectified, the BTS restarts the TRXs that have been shut down.
System Capacity
The system capacity decreases after some TRXs are shut down.
Network Performance
If this feature is enabled during busy hours, the network may become congested.
3.6.3 Interfaces
Inter-NE Interface
This feature affects the Abis interface.
The SET BTSPSUFP command is used to configure the Intelligent Shutdown of TRX Due to
PSU Failure feature.
GBSS9.0
GBSS8.1
3-8

3.6.4 Operation
To enable this feature, the parameters Tran. Cabinet Configured and Service Priority
Policy must be set.
3.7 GBFD-113701 Frequency Hopping (RF Hopping,
baseband Hopping)
3.7.1 Description
The Frequency Hopping (RF hopping, baseband hopping) feature is enhanced in GBSS9.0.
The TRX aided baseband frequency hopping (FH) is improved. When a TRX in baseband FH
mode becomes faulty, the faulty TRX is excluded from the baseband FH group, and functional
TRXs continue to participate in baseband FH. After the BCCH TRX aiding is enabled, the
baseband FH is retained in the cell.
System Capacity
No impact.
Network Performance
After the TRX aided baseband FH or BCCH TRX aiding is enabled, the baseband FH feature
continues to be available in the cell, and there is no major impact on service quality or KPIs of
the cell.
3.7.3 Interfaces
Inter-NE Interface
No impact.
After the TRX aided baseband FH is enabled, the original faulty TRX is switched back
according to the user-defined switchback policy when it becomes normal. The switchback
policy can be set by using the SET GCELLCCACCESS command.
3.7.4 Operation
No impact.
GBSS9.0
GBSS8.1
3-9

3.8 GBFD-118606 Clock over IP
3.8.1 Description
The Clock over IP feature is enhanced in GBSS9.0.
IP clock servers are configured on a per BTS basis, with primary and secondary IP clock
servers supported. When the primary IP clock server becomes faulty, clock signals are
extracted from the secondary IP clock server. This enhances flexibility and reliability of IP
clock networking.
System Capacity
No impact.
Network Performance
No impact.
3.8.3 Interfaces
Inter-NE Interface
No impact.
No impact.
3.8.4 Operation
No impact.
3.9 GBFD-118620 Clock over IP Support 1588V2
3.9.1 Description
In TDM mode, the BTS can extract clock signals from the GPS, BITS, or E1 line. In IP mode,
however, there are some problems in clock signal extraction: In all-IP mode, the E1 line clock
is not available; the GPS clock is available, but the GPS receiver, antenna, and feeder are
required, which increases the expenditure; BITS clock is not available for all sites. The
cost-effective Clock over IP feature solves these problems by enabling the BTS to obtain
clock signals from the IP network.
The Clock over IP feature is implemented in client/server mode. The IP clock server generates
time stamps and sends the time stamps to BTSs, which serve as IP clock clients. Then the
BTSs compensate for delay and restore the clock using an adaptive method.
GBSS9.0
GBSS8.1
3-10

Huawei GBSS supports two types of clock protocols: Huawei proprietary clock protocol and
the standard clock protocol IEEE1588V2. This feature complies with only IEEE1588V2. By
using this feature, Huawei IP-based BTS can interconnect with clock servers that comply with
IEEE1588V2 as well as with Huawei IP clock servers.
Figure 3-1 shows the networking for the Clock over IP Support 1588V2 feature.
Figure 3-1 Networking for the Clock over IP Support 1588V2 feature

An IP clock server can be deployed as an independent entity in the network and can serve a
maximum of 512 BTSs. An IP clock client is integrated in the BTS without any additional
hardware.
An IP-based BTS can be connected to the primary and secondary IP clock servers. When the
primary IP clock server becomes faulty, the BTS obtains clock signals from the secondary IP
clock server, enhancing reliability of the clock system.
In GBSS9.0, the BTS implements frequency synchronization in IEEE1588V2 but does not
implement time synchronization. Moreover, the BTS supports only Layer 3 unicast.
System Capacity
No impact.
Network Performance
No impact.
GBSS9.0
GBSS8.1
3-11

3.9.3 Interfaces
Inter-NE Interface
After this feature is configured for the BTS, a clock server that supports IEEE1588V2 must be
configured.
The IP clock mode and the PTP clock mode for the BTS must be set by using the MML
commands.
3.9.4 Operation
SET BTSCLK: used to set the IP clock mode for a BTS
SET BTSIPCLKPARA: used to set the PTP clock mode for a BTS
3.10 GBFD-111610 Dynamic Cell Power Off
3.10.1 Description
With this feature, some 900 MHz/1800 MHz same-coverage cells are dynamically powered
off within a specified period when the network traffic is light. 900 MHz cells are those
operating on the 900 MHz or 850 MHz frequency band, and 1800 MHz cells are those
operating on the 1800 MHz or 1900 MHz frequency band. If the coverage area of an 1800
MHz cell is within the coverage area of a 900 MHz cell and no coverage hole exists, then the
1800 MHz cell is called the same-coverage cell of the 900 MHz cell. Only the same-coverage
cells on the 1800 MHz frequency band can be powered off.
Before powering off a cell that meets the requirements for dynamic cell power-off, the BSC
reselects idle MSs to other cells and hands over MSs processing services to other cells. After
the cell is powered off, the BSC periodically checks the traffic on the same-coverage cell of
this cell. If the load in the same-coverage cell of this cell is constantly higher than the cell
load threshold, this cell is powered on again.
The period when dynamic cell power-off is allowed can be specified on a per cell basis. To
mitigate the impact on the network capacity, it is suggested that dynamic cell power-off be
used only in low traffic periods, for example, 00:00 to 06:00 in the morning.
System Capacity
No impact.
Network Performance
No impact.
GBSS9.0
GBSS8.1
3-12

3.10.3 Interfaces
Inter-NE Interface
No impact.
Parameters related to the Dynamic Cell Power Off feature must be set by using the BSC
MML commands.
3.10.4 Operation
Parameters related to the Dynamic Cell Power Off feature must be set by using the SET
GCELLDYNTURNOFF command.
3.11 GBFD-116902 Ater Compression Transmission
3.11.1 Description
The BM subrack interworks with the remote TC subrack through the Ater interface. To save
the transmission resources over the Ater interface, the TC subrack usually shares a
telecommunications room with CN equipment. That is, the TC subrack is placed remotely
from the BSC. In this case, a bandwidth of 16 kbit/s (full-rate) or 8 kbit/s (half-rate) is enough
for each speech channel over the A interface. Compared with the 64 kbit/s PCM speech
channel over the A interface, 75% of the transmission resources are saved. The application of
Ater compression transmission further saves about 30% of the transmission resources over the
Ater interface.
The Ater compression transmission is based on the IP over PPP over STM-1 technique. With
this technique, the IP packets with speech data are encapsulated using the PPP protocol and
then transmitted over the channelized STM-1 port.
The key techniques involved in the Ater compression transmission are as follows:
1) ML-PPP/MC-PPP, which helps improve the transmission reliability and bandwidth usage
ML-PPP: Multiple PPP links are combined to form one ML-PPP group, providing a link with
relatively high bandwidth for the IP layer. At the transmit end, a large IP packet is divided into
several small packets, which are transmitted concurrently over the PPP links to the receive
end. Upon receipt of the small packets, the receive end reassembles them into the original
large IP packet for further processing. With the ML-PPP technique, multiple E1s/T1s are
bound together to provide load sharing and higher bandwidth for IP transmission.
MC-PPP: The priority scheme is introduced to MC-PPP on the basis of ML-PPP to facilitate
timely transmission of real-time data, thereby reducing transmission delay.
2) VAD, Ater MUX, PPP MUX, and IP header compression, which help save the bandwidth
Voice Activity Detection (VAD): With the cooperation of DTX over the Um interface, this
technique can implement discontinuous transmission of speech frames on the Ater link. Under
typical call conditions (VAD = 0.5), the Ater transmission efficiency is almost doubled.
GBSS9.0
GBSS8.1
3-13

Ater MUX: Multiple IP/UDP packets share one IP/UDP header. On receiving these IP/UDP
packets, the receive end demultiplexes the IP/UDP packets into the original data. This reduces
transmission resources consumed by IP/UDP headers.
PPP MUX: Multiple upper-layer packets (such as UDP packets) are multiplexed into one PPP
frame before being encapsulated. Each multiplexed upper-layer packet is prefixed with a
description field of only one to two bytes. All multiplexed upper-layer packets share the same
PPP header and CRC information. This reduces transmission resources consumed by PPP
headers.
IP header compression: With this technique, redundant information is removed from the
IP/UDP header of the UDP data packets that have the same source IP address, destination IP
address, source port, and destination port. This improves transmission efficiency.
System Capacity
The Ater Compression Transmission feature reduces the cost of transmission resources over
the Ater interface for operators. Compared with the traditional TDM transmission, the Ater
compression transmission saves about 30% of transmission resources.
Network Performance
No impact.
3.11.3 Interfaces
Inter-NE Interface
No impact.
The parameter Ater Transmission Mode is added to the SET BSCBASIC command to
distinguish the TDM transmission mode from the IP transmission mode.
The interface board type POUc is added to the ADD BRD command.
The interface board type POUc is added to the ADD PPPLNK and ADD MPGRP
commands.
The BSC and TC neighboring node types are added to the ADD ADJNODE command.
The interface type Ater is added to the ADD IPPATH command.
3.11.4 Operation
SET BSCBASIC: used to set the Ater transmission mode to the IP mode
ADD BRD: used to add an Ater interface board POUc (IP) in the BM and TC subracks
ADD PPPLNK: used to add PPP links in the BM and TC subracks
ADD MPGRP, ADD MPLNK, and ADD MPLKS: used to add MLPPP links in the
BM and TC subracks and enable functions such as PPP MUX and IP header compression
ADD ADJNODE: used to configure the adjacent nodes for the BM and TC subracks
GBSS9.0
GBSS8.1
3-14

ADD IPPATH: used to configure IP paths on the user plane (carried on the PPP links)
for the BM and TC subracks
ADD IPMUX: used to enable the Ater MUX function
The configurations related to the Ater operation and maintenance link (OML) and Ater
signaling link (SL) are the same as those in TDM transmission mode.
3.12 GBFD-117401 MSC Pool
3.12.1 Description
The MSC Pool feature is enhanced in GBSS9.0.
The number of service requests sent to each MSC in the MSC pool is counted on the basis of
the MS access method (IMSI/IMEI/TMSI). This helps the operators learn the distribution of
different MS access methods.
System Capacity
No impact.
Network Performance
No impact.
3.12.3 Interfaces
Inter-NE Interface
No impact.
The number of service requests sent to each MSC in the MSC pool is counted on the basis of
the MS access method (IMSI/IMEI/TMSI). The new counters distinguish different MS access
methods, including the IMSI load sharing, IMEI load sharing, null NRI load sharing, and NRI
load sharing.
3.12.4 Operation
Counters related to the MSC are set and queried on the M2000.
GBSS9.0
GBSS8.1
3-15

3.13 GBFD-113725 BSC Node Redundancy
3.13.1 Description
The BSC controls radio resources of BTSs. Once a BSC is faulty, all BTSs controlled by this
BSC fail to access the network and communication cannot be performed in the coverage area
of this BSC. In addition, the BSC cannot communicate with a BTS if the link between the
BSC and the BTS is faulty. As a result, services in the coverage area of the BTS are
interrupted.
To prevent service interruption, the BSC Node Redundancy feature is introduced. The BSC
supports 1+1 backup mode. The principles of the 1+1 backup mechanism are as follows:
A BTS is configured with two sets of transmission links, which are connected to the primary
and secondary BSCs. All data concerning BTSs, cells, and neighboring cells is stored on both
the primary and secondary BSCs. BTSs are normally controlled by the primary BSC. When
the primary BSC becomes faulty, the BTSs are switched to the secondary BSC to restore the
normal operation.

A BTS is configured with two Abis interface instances (including two sets of control plane
links, user plane links, and OM links). Two serving BSCs work in cold backup mode (the
ongoing calls under the faulty BSC are not protected) to improve system reliability. In general,
both the primary and secondary BSCs process services. This maximizes the equipment usage.
When a BSC becomes faulty, the other BSC takes over all BTSs under the faulty BSC so that
the BTSs continue to be functioning, preventing a single point of failure (SPOF) at the BSC
level. When this happens, the processing capability (indicated by factors such as CS Erlang
and PS throughput) decreases.
System Capacity
If one of the BSCs is faulty, the processing capability of the BSCs decreases by 50%,
compared with the total processing capability of two independent BSCs.
Network Performance
The BSC Node Redundancy feature improves the reliability and robustness of the GSM
network and reduces the time of service interruption caused by an SPOF.
GBSS9.0
GBSS8.1
3-16

3.13.3 Interfaces
Inter-NE Interface
The message indicating the capability of an IP-based BTS contains a flag, which indicates
whether the BTS supports the BSC Node Redundancy feature. The BSC processes services
based on the flag.
If a BTS supports the BSC Node Redundancy feature, the BSC sends the IP address of the
other BSC involved in the BSC node redundancy to the BTS over the signaling link. Then, the
BTS can be switched between the two BSCs when one of the BSCs becomes faulty.

Basic attributes of a BSC node redundancy group can be configured and queried through
MML commands.
The BSC Node Redundancy feature can be activated and deactivated through MML
commands.
Parameters related to the BSC redundancy service switchback policy can be configured
and queried through MML commands.
Dual-hosting attributes of the IP-based BTS and OPC can be configured, and the
attributes and status of the IP-based BTS and OPC can be queried through MML
commands.
Inter-BSC heartbeat links can be configured and queried through MML commands.
3.13.4 Operation
The BSC Node Redundancy feature is applicable to all-IP networking scenarios. The IP
transmission features for all interfaces are under license control.
SET GBSCREDGRP: used to configure a BSC node redundancy group
SET GREDGRPPRIMHOSTPOLICY: used to configure the BSC node redundancy
policy
MOD OPC: used to set an OPC as the primary or secondary OPC
SET BTSIP: used to modify parameters such as hosting attributes of an IP-based BTS
ADD SCTPLNK: used to add parameters related to the inter-BSC heartbeat links
ACT GBSCREDGRP: used to activate the BSC Node Redundancy feature
3.14 GBFD-113726 TC Pool
3.14.1 Description
The GSM transcoder subrack (GTCS) processes the CS services of the BSC. In general, one
GTCS belongs to only one BSC, and the GTCSs of different BSCs are not associated. In such
a network structure, TC resources are not reused among multiple BSCs. In scenarios where
multiple BSCs with small capacity are deployed in the same network, TC resources are
wasted.
GBSS9.0
GBSS8.1
3-17

In TC pool mode, multiple BSCs share one TC pool. Figure 3-2 shows the typical topology.
Figure 3-2 TC pool topology
E
1
/
S
T
M
-
1
TC(Pool)
MSC2
BSC1 (main BSC)
BSC2(sub BSC)
BSC3(sub BSC)

MSC1
MSC3
BSC4(sub BSC)
E1/STM
-1
E1/STM
-1
E
1
/S
T
M
-
1
E
1
/
S
T
M
-
1
E1/STM-1
E
1
/
S
T
M
-
1

Ater A
Abis

The TC pool is used when the GTCS is deployed on the MSC side and is connected to the BM
subrack through the Ater interface. The coding/decoding resources in the TC pool are shared
by the primary BSC and secondary BSCs, achieving load sharing. When a voice processing
board is faulty, it automatically stops functioning and therefore does not affect the setup of
subsequent CS services, which improves the system reliability. The speech versions supported
by the TC pool are FR, EFR, HR, AMR-FR, and AMR-HR.
To synchronize the frequencies of the GSM network, the primary and secondary BSCs that
are connected to the same TC pool must use the same clock source. A BSC can be connected
to only one TC pool, and one TC pool can be connected to a maximum of 16 BSCs.
System Capacity
The usage of the TC coding/decoding resources is increased because multiple BSCs share the
same resources in one TC pool. When multiple BSCs with small capacity are deployed in the
same network, 20%-30% TC coding/decoding resources can be saved.
This feature helps save 40%-60% of the floor area of an equipment room. Generally, three
GTCSs with small capacity occupy the floor area of three cabinets. In TC pool mode, however,
three GTCSs occupy the floor area of only one cabinet.
The GTCS in the primary BSC must be configured with additional TC subracks, DPU boards,
and A interface boards to serve as the TC pool for multiple BSCs.
GBSS9.0
GBSS8.1
3-18

Network Performance
No impact.
3.14.3 Interfaces
Inter-NE Interface
Signaling planes of the secondary BSCs and TC pool are interconnected through the Ater
signaling links (SLs). In TDM transmission mode, the user planes of the secondary BSCs and
TC pool are interconnected through the Ater connection paths. In IP transmission mode, user
planes of the secondary BSCs and TC pool are interconnected through the PPP/ML-PPP links,
neighboring nodes, and IP paths.
The TC pool switch and the IDs of the BSCs that are connected to the TC pool are added
to the BSC BASIC command.
The ATERE1T1 command is added to configure the Ater connection paths for the
secondary BSCs on the BM and TC sides.
The BM/TC configuration flag indicating whether a link is configured on the BM side or
the TC side is added to the Ater signaling configuration command.
The BSC identifier indicating whether the A interface E1/T1 belongs to the primary BSC
or secondary BSCs is added to the A interface E1/TI configuration command.
The BSC ID, which specifies the BSC to which the semi-permanent link belongs, is
added to the command related to the configuration of the transparent semi-permanent A
interface signaling links in the TC subrack.
The BSC ID specifying the identifier of the BSC neighboring node connected to the TC
is added to the command for configuring the Ater neighboring node.
3.14.4 Operation
The Ater Compression Transmission feature is under license control.
SET BSCBASIC: used to activate the TC pool after setting IsSupportTcPool and
IsMainBSC
ADD ATERCONPATH: used to add an Ater connection path for the primary BSC
ADD ATERCONSL: used to add an Ater signaling link for the primary BSC
ADD ATEROML: used to add an Ater OML for the primary BSC
ADD ATERE1T1: used to configure the Ater resources for the primary and secondary
BSCs
ADD ATERSL: used to configure the Ater SL resources for the primary and secondary
BSCs
ADD PPP, ADD MPGRP, or ADD MPLNK: used to configure the IP paths on the TC
and the BM supporting the Ater Transmission Compression feature
ADD ADJNODE: used to configure the neighboring node of the TC and the BM
supporting the Ater Transmission Compression feature
ADD IPPATH: used to configure the IP paths between the TC and the BM supporting
the Ater Transmission Compression feature
GBSS9.0
GBSS8.1
3-19

3.15 GBFD-113728 OML Backup
3.15.1 Description
The OML is the operation and maintenance link between the BSC and the BTS. When the
OML is faulty, the BTS cannot work. The OML Backup feature is implemented by
configuring two OMLs on two E1s. When the OML in use becomes faulty due to a
transmission link or port failure, the BTS uses the other OML. In this manner, the BTS and
cell can continue to work without any interruption.
When the OML Backup feature is used, the BSC configures one OML on port 0 and the other
OML on port 1. After being reset, the BTS attempts to establish the OML on the two ports in
turn. If the BTS establishes an OML on one port, the BTS always uses the OML on this port
unless the BTS is reset or the OML is unavailable. When the established OML is unavailable,
the BTS attempts to establish an OML on the other port. If this attempt is successful, the BSC
triggers the OML switchover.
The RSLs, TCHs, idle timeslots, and monitoring timeslots, however, are not switched over
after the OML switchover. That is, for port 0 and port 1, if the transmission link or port where
the working OML is located is faulty, all the TRX channels, idle timeslots, and monitoring
timeslots configured on that link or port become unavailable. The functioning port, however,
can continue to provide services for the BTS and cells.
The OM personnel can use MML commands to enable this feature and set the parameters
Waiting Time Before Rotate and Try Rotating Duration Time.
The OML Backup feature is applicable only to BTSs in TDM or HDLC mode, but not to
BTSs in IP mode.
System Capacity
By using the OML Backup feature, the OMLs occupy timeslot 31 of ports 0 and 1. Only one
of the OMLs is functional at a time.
When transmission resources over the Abis interface are sufficient and there are idle timeslots,
this feature does not affect the system capacity. When transmission resources over the Abis
interface are insufficient and all the timeslots are occupied, the number of full-rate CS users
that can access the network is reduced by four because the backup OML occupies some
timeslots.
3.16 GBFD-114325 Fast 3G Reselection at 2G CS Call
Release
3.16.1 Description
The Fast 3G Reselection at 2G CS Call Release feature allows the BSS to preferentially select
an optimal neighboring 3G cell for an MS after the MS terminates its call. This mechanism
enables the MS to camp on the 3G cell whenever possible and obtain 3G services without a
cell reselection procedure.
GBSS9.0
GBSS8.1
3-20

System Capacity
No impact.
Network Performance
No impact.
3.16.3 Interfaces
Inter-NE Interface
The "Cell selection indicator after release of all TCH and SDCCH" information element (IE)
is added to the Channel Release message, which is transmitted over the Um interface. This IE
indicates the cell on which the MS camps after releasing a call.
The parameter Select 3G Cell After Call Release is added to the SET GCELLCCAD
command to activate and deactivate the Fast 3G Reselection at 2G CS Call Release feature.
3.16.4 Operation
To enable this feature, the parameter Select 3G Cell After Call Release in the SET
GCELLCCAD command must be set to YES(Yes).
3.17 GBFD-115701 TFO
3.17.1 Description
GBSS9.0 introduces two enhanced TFO functions: TFO speech version optimization and TFO
ACS optimization. To enable these two features, the TFO feature must be enabled first.
TFO speech version optimization: The prerequisite for TFO establishment is that the speech
versions adopted by the calling and called parties are compatible. If the TFO cannot be
established because of speech version incompatibility, the BSC selects an optimal common
speech version from the speech version sets supported by the calling party and called party on
the basis of the speech quality, robustness, and system capacity. Then, the BSC initiates an
intra-cell speech version switchover. In this manner, the TFO is established to optimize the
speech quality.
TFO ACS optimization: The establishment of narrowband AMR TFO has high requirements
for common active codec set (CACS). If the configured CACS does not meet the
requirements, the BSC selects the optimal codec set through the Robust AMR Traffic
Synchronized Control Channel (RATSCCH) procedure based on the common support codec
set (CSCS) to replace the existing ACS. In this manner, the narrowband AMR TFO is
established to ensure optimal speech quality of the narrowband AMR. The broadband AMR
does not support TFO ACS optimization.
GBSS9.0
GBSS8.1
3-21

System Capacity
After TFO speech version optimization is enabled, the handover from a TCHF to a TCHH
may be triggered if the speech quality is improved. In this manner, the Um interface resources
are saved and the system capacity is improved.
TFO ACS optimization has no impact on the network capacity.
Network Performance
After TFO speech version optimization is enabled, the number of intra-cell handovers may
increase. However, the speech quality is improved.
After TFO ACS optimization is enabled, the speech quality of narrowband AMR calls is
improved.
3.17.3 Interfaces
Inter-NE Interface
No impact.
No impact.
3.17.4 Operation
The TFO feature must be enabled by using the SET GCELLBASICPARA command before
TFO speech version optimization or TFO ACS optimization is enabled.
TFO speech version optimization
To enable TFO speech version optimization, the SET BSCBASIC command must be
used to modify the BSC attributes and set Support TFO Codec Optimize to
YES(Support).
To reduce the number of intra-cell handovers caused by TFO speech version
optimization, it is recommended that the speech versions of the cells in the network be
the same.
TFO ACS optimization
To enable TFO ACS optimization, the SET GCELLCCAMR command must be used to
set Is Ratscch Function Enabled to ENABLE(Enable).
To reduce unnecessary ACS optimization, it is recommended that the AMR ACS in the
cell be configured as follows: Config-NB-Code 1: (FAMR: 12.2, 7.4, 5.9, 4.75)/ (HAMR:
7.4, 5.9, 4.75).
GBSS9.0
GBSS8.1
3-22

3.18 GBFD-115703 Automatic Noise Compensation (ANC)
3.18.1 Description
The Automatic Noise Compensation (ANC) feature evaluates the background noise at the
local end and the speech level at the peer end. If the background noise at the local end is high,
the feature increases the voice volume at the peer end. In this manner, the ratio of the signal at
the peer end to the background noise at the local end is increased so that the listener at the
local end can clearly hear the voice from the peer end.
The ANC feature is disabled by default. The threshold for the ANC feature is configurable
and is specified by the target signal-to-noise ratio (SNR). The maximum gain of noise
compensation is also configurable.
For details about speech processing, see the ITU-T G.169 specifications.
The ANC feature is valid only in A over TDM mode. This feature cannot be used together
with the TrFO or TFO feature.
System Capacity
This feature increases the load of TC devices by about 5%. This affects the maximum number
of speech paths that can be allocated. If TC resources are insufficient, additional TC devices
are required.
Network Performance
The ANC feature helps improve the user experience.
3.18.3 Interfaces
Inter-NE Interface
No impact.
No impact.
3.18.4 Operation
The SET TCPARA command is used to modify the TC attributes, enable the ANC feature,
and configure the parameters related to the ANC algorithm.
GBSS9.0
GBSS8.1
3-23

3.19 GBFD-115704 Enhancement Packet Loss Concealment
(EPLC)
3.19.1 Description
The speech quality may be adversely affected by problems such as acoustic echo, background
noise, and packet loss. To ensure speech quality, theses problem must be solved and additional
gain needs to be provided.
The Enhancement Packet Loss Concealment (EPLC) feature uses Huawei patented algorithms
to restore the lost speech frames by using the information contained in the previous speech
frames.
The EPLC feature processes only AMR voice packets. This feature cannot be used together
with the TrFO or TFO feature.
System Capacity
No impact.
Network Performance
The EPLC feature helps improve the speech quality and user experience.
3.19.3 Interfaces
Inter-NE Interface
No impact.
No impact.
3.19.4 Operation
The SET TCPARA command is used to modify the TC attributes and enable the EPLC
feature.
3.20 GBFD-115506 AMR Coding Rate Threshold Adaptive
Adjustment
3.20.1 Description
The AMR Coding Rate Threshold Adaptive Adjustment feature is enhanced in GBSS9.0.
The AMR coding rate threshold is used to control the AMR coding rate selection. When the
threshold is a fixed value, the AMR coding rate cannot be adapted if the radio channel quality
GBSS9.0
GBSS8.1
3-24

changes or the network planning is not optimal. If this happens, the AMR speech quality
decreases.
The AMR Coding Rate Threshold Adaptive Adjustment feature adaptively adjusts the AMR
coding rate threshold in the downlink based on the speech quality. The BTS obtains the frame
error ratio (FER) of the current call based on the enhancement measurement report (EMR)
from the MS and then estimates the speech quality. If the estimated speech quality deviates
significantly from the target speech quality, it indicates that the configured threshold is
inappropriate. The GBSS then adjusts the threshold by using the related algorithm. The BTS
sends the adjusted AMR coding rate threshold to the MS over the RATSCCH. Based on the
threshold, the MS adjusts the AMR coding rate during the call.
System Capacity
No impact.
Network Performance
The AMR Coding Rate Threshold Adaptive Adjustment feature improves the AMR speech
quality in the downlink and user experience.
3.20.3 Interfaces
Inter-NE Interface
No impact.
No impact.
3.20.4 Operation
The SET GCELLCCAMR command is used to set parameters related to the AMR Coding
Rate Threshold Adaptive Adjustment feature.
The MS must support the EMR.
3.21 GBFD-115507 WB AMR
3.21.1 Description
Wideband Adaptive MultiRate (WB AMR) is a coding scheme that significantly improves the
speech quality. WB AMR allows for a sampling rate of 16 kHz and a speech frequency range
between 0.05 kHz and 7 kHz. WB AMR provides clearer and louder voice, compared with
narrowband AMR. Narrowband AMR has a sampling rate of 8 kHz and a speech frequency
range between 0.2 kHz and 3.4 kHz.
WB AMR adopts the Gaussian Minimum Shift Keying (GMSK) mode and supports the
coding rates of 6.60 kbit/s, 8.85 kbit/s, and 12.65 kbit/s on full-rate TCHs.
GBSS9.0
GBSS8.1
3-25

To achieve ideal speech quality, WB AMR needs to be implemented at both ends of a call.
When used together with the feature GBFD-115701 TFO, the end-to-end WB AMR provides
higher speech quality, as PCM codec is not required at both ends. If the end-to-end WB AMR
call cannot be established, the BSC sets up an AMR FR call instead of a one-end WB AMR
call. This is because the one-end WB AMR call requires PCM codec at both ends, which
affects the speech quality and robustness of WB AMR calls. Huawei BSS equipment supports
the WB AMR feature in Abis over TDM, Abis over IP, and Abis over HDLC transmission
modes.
System Capacity
This feature increases the load of TC devices by a maximum of about 45%. The load of TC
devices depends on the percentage of WB AMR calls. Therefore, this feature affects the
maximum number of speech paths that can be allocated in a network. If TC resources are
insufficient, additional TC devices are required.
Network Performance
This feature significantly improves the speech quality.
3.21.3 Interfaces
Inter-NE Interface
The core network and MS must allow the speech version of the WB AMR to be assigned.
No impact.
3.21.4 Operation
SET BSCBASIC: used to set A Interface Tag, Um Interface Tag, and Abis Interface
Tag to GSM_PHASE_2Plus
SET GCELLCCACCESS: used to set the cell-level WB AMR parameters for access
control. The parameter Full_rate_Ver5 is added.
SET GCELLCCAMR: used to set the cell-level WB AMR parameters for call control
The WB AMR forces the enabling of the TFO feature, eliminating the need for manual
enabling.
3.22 GBFD-119906 Conversational QoS
3.22.1 Description
Conversational services are real-time services that have high requirements for the transfer
latency. As specified by 3GPP specifications, the transfer latency of conversational services
GBSS9.0
GBSS8.1
3-26

must not exceed 80 ms. To ensure user satisfaction, the end-to-end latency for VoIP services
generally do not exceed 300 ms.
Conversational services use the RTTI channels to meet the requirements for the transfer
latency. The scheduling period of radio blocks based on the RTTI is 10 ms, and that based on
the BTTI is 20 ms. If an MS does not support the Latency Reduction feature, the BTTI
channels are assigned. In this case, the requirements for the transfer latency of conversational
services are met as much as possible and the access of the conversational services is not
rejected.
IP services are transparently transmitted by the BSC. Therefore, the BSC cannot recognize the
MS service type. Instead, the BSC obtains the MS service type from the registration
information in the HLR. Whether the transfer latency of conversational services of an MS can
meet the requirements of conversational QoS depends on the following two conditions:
Whether the MS registers the conversational service as the service type
Whether the MS supports the Latency Reduction feature
The current version supports the RTTI feature only in IP/HDLC transmission mode. Therefore,
the IP/HDLC transmission mode is required to achieve optimal QoS for conversational
services.
System Capacity
With the Conversational QoS feature, users can receive conversational services. Therefore,
operators can absorb more users, leading to an increase in operator revenues.
Network Performance
This feature requires support from the RTTI feature. The RTTI channels, however, requires
more radio resources. Therefore, if there are a large number of users processing
conversational service and the network and the MS support RTTI, the radio resources may
become insufficient.
3.22.3 Interfaces
Inter-NE Interface
No impact.
No impact.
3.22.4 Operation
The SET GCELLGPRS command is used to configure the latency reduction capability of the
cell.
GBSS9.0
GBSS8.1
3-27

3.23 GBFD-119502 PS Handover
3.23.1 Description
The PS Handover feature complies with the 3GPP Release 6, including 3GPP TS 44.060,
48.018, and 43.129.
Conversational services have high requirements for service latency. Cell reselection cannot
meet these requirements. To solve this problem, the PS Handover feature enables the BSC to
allocate radio resources of the target cell to the MS before cell change, which reduces the
service interruption time to less than 150 ms. In addition, this feature considers factors such as
signal level and load in the neighboring cells in advance. This ensures a high success rate for
PS handovers and a high throughput for the target cell, which guarantees the QoS.
The PS Handover feature supports inter-cell handovers, inter-BSC handovers, and inter-RAT
handovers. This feature also supports handovers triggered by the MS in NC0 or NC1 mode
and network-controlled handovers in NC2 mode.
System Capacity
No impact.
Network Performance
This feature helps reduce the service latency during cell change.
3.23.3 Interfaces
Inter-NE Interface
1. The PS handover field indicating whether the MS supports the PS handover is carried in
the radio access capability message reported by the MS.
2. The Extended Feature Bitmap field containing the PS Handover field is added to the
BVC RESET and BVC RESET ACK messages transmitted between the BSC and the
SGSN.
3. The following messages are added between the BSC and the SGSN:
PS Handover Required, PS Handover Request Ack, and PS Handover Complete
messages from the BSC to the SGSN
PS Handover Request and PS Handover Required Ack messages from the SGSN to
the BSC
No impact.
3.23.4 Operation
The MS can perform a PS handover only when the following conditions are met:
The BSC license supports PS handovers.
GBSS9.0
GBSS8.1
3-28

The setting of the BSC parameters meets either of the following conditions:
Support NACC is set to Yes, Network Control Mode is set to NC0 or NC1, and PS
Handover Support is set to YES(Support).
Support NC2 is set to Yes, Network Control Mode is set to NC2, and PS
Handover Support is set to YES(Support).
The BSC and SGSN support the PFC procedure.
The SGSN supports PS handovers.
On the BSC side, the MOD NSE command is used to enable the NSE to support PS
handovers and the PFC procedure.
The SET GCELLGPRS command is used to enable cells to support inter-RAT PS handovers.
To support handovers from a UMTS cell to a GSM cell, Support In Inter-RAT
Inter-cell PS Handover must be set to SUPPORT(Support).
To support handovers from a GSM cell to a UMTS cell, Support Out Inter-RAT
Inter-cell PS Handover must be set to SUPPORT(Support).
3.24 GBFD-119503 Early TBF Establishment
3.24.1 Description
The packet transfer latency is a KPI for PS services, particularly for latency-sensitive
conversational services. The Early TBF Establishment feature supports the allocation of the
temporary block flow (TBF) before an MS sends data in the uplink, which reduces the initial
transfer latency of the uplink data.
Before this feature is introduced, the BSC allocates the TBF resources to an MS only if the
MS applies for the resources for transmitting the uplink data. With this feature, the MS applies
for the TBF resources before transmitting data. Then, the BSC pre-allocates the uplink TBF
resources to the MS and sets the TBF to the inactive state. Within a specified period, the MS
can send the uplink data directly without establishing any TBF. After the specified period
passes, the BSC releases the TBF to save the packet transfer resources.
System Capacity
No impact.
Network Performance
By using the Early TBF Establishment feature, the TBF is established before the MS sends
uplink packet data. This reduces the latency during the initial sending of the uplink data and
the round-trip time (RTT).
3.24.3 Interfaces
Inter-NE Interface
No impact.
GBSS9.0
GBSS8.1
3-29

No impact.
3.24.4 Operation
The MS must support the Early TBF Establishment feature. This feature is enabled in
networks by default.
3.25 GBFD-115002 Flow Control Based on Cell Priority
3.25.1 Description
During the flow control processing, different flow control policies are adopted for the cells
with different priorities so that the network can provide differentiated services. When the
network load is excessively high and the resources are insufficient, the Flow Control Based on
Cell Priority feature reduces the congestion rate of high-priority cells (VIP cells). The
congestion rate of low-priority cells (non-VIP cells), however, may increase even though the
system provides best-effort services.
System Capacity
No impact.
Network Performance
With this feature, the access to and paging from the VIP cells are preferentially supported. As
a result, the congestion rate of the VIP cells decrease, but that of the non-VIP cells may
increase when the system resources are insufficient.
3.25.3 Interfaces
Inter-NE Interface
No impact.
The flow control parameters for the VIP users and related parameters for the VIP cells are
added to the MML commands.
3.25.4 Operation
ADD GCELL or MOD GCELL: used to add a VIP cell by setting VIP cell to Yes
SET BSCFCPARA: used to set the flow control parameters of the VIP cell and the call
priorities corresponding to the VIP users in the system
GBSS9.0
GBSS8.1
3-30

3.26 GBFD-118601 Abis over IP
3.26.1 Description
In Abis over IP mode, the data on the signaling plane and user plane is transmitted over the
Abis interface in IP over FE/GE mode. The BSC supports the configuration of the IP
addresses of multiple devices and the configuration of static IP addresses.
The Abis over IP feature supports the configuration of items such as the BTS IP address, BSC
IP address, and routing on the site maintenance terminal (SMT). Compared with the
configuration of the dynamic IP address for the GBSS, the configuration of the static IP
address is more complex, but does not require the configuration of DHCP Relay.
System Capacity
No impact.
Network Performance
No impact.
3.26.3 Interfaces
Inter-NE Interface
No impact.
The ADD DEVIP command is used to add the device IP addresses.
3.26.4 Operation
The ADD DEVIP command is used to add the device IP addresses. One interface board
supports a maximum of 16 device IP addresses.
3.27 GBFD-118611 Abis IP over E1/T1
3.27.1 Description
In IP over E1/T1 mode, the IP packets of the signaling and traffic data are encapsulated by
using the Point-to-Point Protocol (PPP) and then transferred in the E1/T1 or STM-1
transmission mode. The Abis interface boards in the BTS and BSC are responsible for
processing the PPP or ML-PPP protocol.
By using the Abis IP over E1/T1 feature, the IP over E1/T1 mode can be used for the
networking between the BTS and the BSC. The BTS uses the E1/T1 port, and the BSC uses
the E1/T1, channelized STM-1, or FE/GE port. Figure 3-3 shows the networking supported by
Abis IP over E1/T1.
GBSS9.0
GBSS8.1
3-31

Figure 3-3 Networking supported by Abis IP over E1/T1
BSC
BTS
SDH
BTS
IP over E1
IP over E1(STM-1)
IP over E1
IP over FE/GE
IP over E1
BTS

Similar to the TDM mode, in IP over E1/T1 mode, the clock can be locked stratum by stratum
over the E1. The Clock over IP scheme can also be used.
The key techniques adopted in IP over E1/T1 are as follows:
1. ML-PPP/MC-PPP, which helps improve the reliability and bandwidth usage
ML-PPP: Multiple PPP links are bound to form one ML-PPP group to provide a link
with relatively high bandwidth. At the local end, a large IP packet is divided into several
small packets, which are then transmitted concurrently to the peer end over the PPP links.
On receiving the packets, the peer end reassembles the packets and restores the original
IP packet for further processing. By using the ML-PPP technique, multiple E1s/T1s are
bound to provide load sharing for IP transmission. In this manner, the bandwidth usage is
increased.
MC-PPP: The priority scheme is introduced to the MC-PPP on the basis of the ML-PPP
to facilitate the timely transmission of the real-time data, thereby reducing the
transmission latency.
2. VAD and Abis MUX, which help to save the bandwidth
VAD: In Abis IP over E1/T1, discontinuous transmission of the speech frames can be
achieved on the Abis links with the cooperation of the DTX. Under the typical call
condition (VAD = 0.5), the Abis transmission efficiency is doubled compared with that in
traditional TDM mode.
Abis MUX: Multiple small UDP packets use one IP/UDP packet. On receiving the
IP/UDP packet, the peer end demultiplexes the IP/UDP packets to restore the data.
Multiple UDP packets share one IP/UDP packet header, and therefore the IP transmission
efficiency is improved.
3. MSP, which helps to improve the transmission reliability
The BSC supports IP over STM-1. The STM-1 port supports MSP 1+1 unidirectional
switchover and bidirectional switchover and MSP 1:1 bidirectional switchover.
System Capacity
No impact.
GBSS9.0
GBSS8.1
3-32

Network Performance
No impact.
3.27.3 Interfaces
Inter-NE Interface
No impact.
The BSC and BTS support the configuration of the PPP and ML-PPP links.
3.27.4 Operation
The interface boards that support Abis IP over E1/T1 on the BSC side are as follows:
POUc: providing 4 routes of channelized STM-1/OC3 interfaces
PEUa: providing 32 routes of E1/T1/J1 IP interfaces
The following operations use the POUc board as an example:
The ADD BRD command is used to add the interface board. The parameter Logical
function type must be set to IP.
The ADD PPPLNK command is used to add the PPP links.
The following commands are used to configure parameters related to the BTS:
ADD BTS
ADD BTSCONNECT
ADD BTSPPPLNK
SET BTSIP
ADD BTSESN
The ADD ADJNODE and ADD IPPATH commands are used to configure the IP paths
(carried on the PPP links) on the user plane.
3.28 GBFD-118602 A over IP
3.28.1 Description
The A over IP feature is enhanced in GBSS9.0.
In A over IP mode, the data on the signaling plane and user plane is transmitted over the A
interface in IP over FE/GE mode. In A over IP mode, the BSC supports the configuration of
the IP addresses of multiple devices.
The signaling plane and user plane in A over IP mode comply with the related specifications
of the 3GPP Release 8. The user plane and signaling plane comply with TR43.903 and
TS48.008. The CSD coding complies with RFC4040 and RFC2198. Huawei BSCs are
capable of working with the IP-based CN devices from other telecom vendors that comply
with 3GPP Release 8.
GBSS9.0
GBSS8.1
3-33

The A over IP feature supports for TC in MGW, signaling plane IP transmission, and user
plane IP transmission.
In an IP-based core network, the Nb interface uses compressed speech coding, whereas the A
interface still uses conventional TDM transmission. Therefore, calls between MSs controlled
by different MSCs require four coding and decoding operations. Compared with all-TDM
transmission, which requires only two coding and decoding operations, this mode requires
more TCs for the BSC and MGW, which deteriorates the speech quality. When the A over IP
feature is enabled and the IP-based core network and Transcoder Free Operation (TrFO) are
used, the speech data of calling and called MSs need not be coded or decoded. This improves
speech quality and reduces the number of TCs required by the BSC and MGW. The A over IP
feature involves the following techniques:
TC in MGW
Improved speech quality is a major advantage brought by the A over IP feature, which is
made possible by TrFO. As shown in the GSM network topology in the following figure,
the TC is not configured in the BSS but is integrated into the MGW. When the calling
and called MSs use the same speech version or transmit speech data using mutually
compatible AMR rate sets, TrFO can perform specific control on the signaling plane to
eliminate the need for coding and decoding by the TC. This improves speech quality.
Transcoding needs to be performed by the MGW only when the calling and called MSs
use different speech versions and their AMR rate sets are incompatible with each other.

MSC-S
MGW
BSS
A/IP
Mc/IP
MSC-S
MGW
Mc/IP
Nb
Nc
A/IP A/IP
A/IP

e.g. AMR coded
IP based
protocol
stack

e.g. AMR coded
IP based
protocol
stack
BSS
= Transcoder or Transcoder-pair, typically not used in MS-to MS calls
= Signalling
= User plane

IP transmission of speech data
The user plane on the A interface serves as the interface between the BSC and the MGW.
It transmits data using the standard RTP/UDP/IP protocol. The A interface supports all
speech coding formats of the BSS, which are listed as follows:
GSM_FR: RFC 3551 for GSM_FR
GSM_HR: ETSI 101318 for GSM_HR
GSM_EFR: RFC 3551 for EFR
AMR: RFC 3267 for AMR
Since the TC is not configured in the BSS, speech data is transmitted over the A and Um
interfaces using the same speech coding format and different transport formats.
GBSS9.0
GBSS8.1
3-34

MAC / PPP
IP
UDP
RTP
Payload
MAC / PPP
IP
UDP
RTP
Payload
BSC MGW

IP transmission of signaling data
To adapt to IP transmission on the signaling plane of the A interface, the BSC processes
data according to the M3UA/SCTP/IP protocols, and the connection between the BSC
and the MSC complies with the M3UA protocol. In actual networking, signaling and
user data between the BSC and the MSC can be forwarded by the MGW.
As required by TrFO and user plane IP transmission, the BSS MAP signaling
transmission mechanism is enhanced. A process for switching speech versions in the
BSS is added.
The A over IP feature does not affect DTAP messages.
MAC / PPP
IP
SCTP
M3UA
SCCP
BSSMAP+
BSC
MSS
MAC / PPP
IP
SCTP
M3UA
SCCP
BSSMAP+

The A over IP feature in GBSS9.0 incorporates the following improvements:
GBSS9.0 specifies the principle for selecting the multi-rate codec type. This prevents
problems caused by private IP interfaces.
In A over IP transmission mode, configuration of the AMR rate set must comply with the
associated protocol, which defines No.0 to No.15 codec modes.
The following figure describes the codec types defined in the protocol.
GBSS9.0
GBSS8.1
3-35

The A over IP feature has requirements on the selection of initial rates also.

If the selected AMR codec type contains three or fewer rates, the lowest rate is used as
the initial rate for codec.
If the selected AMR codec type contains more than three rates, the second lowest rate is
used as the initial rate for codec.
During intra-BSC handover, a speech version is selected based on the speech version selection
strategy.
When Speech Version Select Strategy in Intra-BSC HO is set to MSC Strategy, the
speech version selection during an intra-BSC handover is based on the speech version
priorities contained in the assignment message from the MSC.
When Speech Version Select Strategy in Intra-BSC HO is set to BSC Strategy, the
speech version selection during an intra-BSC handover is based on the priority sequence
of FR AMR-WB, FR AMR, EFR, FR, HR AMR, and HR. The AMR codec type is
selected in the following sequence:
Full-rate: s1, s14, s7, s12, s6, s5, s10, s4, s9, s3, s8, s2, s0
Half-rate: s1, s5, s10, s4, s9, s3, s8, s2, s0
Among all AMR codec types, s1 is recommended, as indicated in the protocol.
When Speech Version Select Strategy in Intra-BSC HO is set to Speech Version of
Originating Cell Preferred, the speech version (including the codec type) that is used in
the source cell is preferred.
The switching process is modified so that MSC assignment is not controlled by channel
activation on the BSS side, but according to the capability reported to the NSS.
GBSS9.0
GBSS8.1
3-36

CSD service transmission redundancy in A over IP: Certain CSD services, such as the fax
service, are sensitive to data loss. The retransmission mechanism for such services is usually
unavailable at the application layer. Therefore, the packet loss on the IP transmission network
has major impact on services, such as fax services. By using the A over IP feature, the same
CSD service data block is transmitted in different RTP frames, therefore ensuring the
complete transmission of the data and enhancing the user experience of the CSD services. The
CSD service transmission redundancy in A over IP supports a maximum of three levels of
redundancy (a maximum of two consecutive RTP frames can be discarded). The CSD service
bearer in A over IP complies with RFC4040. The CSD service transmission redundancy in A
over IP complies with RFC2198.
UDP MUX for A Transmission: After A over IP is introduced, the RTP/UDP/IP
encapsulation is applied to the user plane data, which reduces the transmission efficiency. By
using the UDP MUX for A Transmission feature, however, multiple RTP packets use one UDP
packet header. As a result, the proportion of the packet header to the entire packet decreases
and therefore the efficiency of transmission over the A interface increases. For details, see
GBFD-118610 UDP MUX for A Transmission.
System Capacity
No impact.
Network Performance
No impact.
3.28.3 Interfaces
Inter-NE Interface
The BSC complies with the 3GPP protocol. Therefore, parameters associated with the
interconnection between the SGSN and BSC must be reconfigured.
If UDP multiplexing and the RTP compression are to be enabled at the same time, both the
BSC and MGW must support the RTP compression.
The ADD IPMUX command is used to set IP MUX Type to UDP MUX.
3.28.4 Operation
The ADD IPMUX command is used to set IP MUX Type to UDP MUX, and set Sender
UDP MUX Mode and Receive UDP MUX Mode to one of the following values:
MUXCLOSE
NORTPCOMP
RTPCOMP
The SET BSCBASIC command is used to set CSD Service Redundancy Level to one of the
following values:
GBSS9.0
GBSS8.1
3-37

NO(Not Supported)
R3(Only R3 Supported)
R2(Only R2 Supported)
R2ANDR3(R2 And R3 Supported)
3.29 GBFD-118622 A IP over E1/T1
3.29.1 Description
In IP over E1/T1 mode, the IP packets of signaling and traffic data are encapsulated using the
PPP protocol and then transferred over the E1/T1/CSTM-1. The peer entity and the A
interface board on the BSC are responsible for processing the PPP/ML-PPP protocol.
By using the A IP over E1/T1 feature, the networking in IP over PPP over E1/T1/CSTM-1
between the BSC and CN is supported. The BSC uses the E1/T1 or channelized STM-1 ports.
The router at the peer end or CN can use the E1/T1, channelized STM-1, or FE/GE ports.
Figure 3-4 shows the networking modes supported by A IP over E1/T1.
Figure 3-4 Networking modes supported by A IP over E1/T1
MSC
MGW
BSC
SDH
MGW
IP over FE/GE
MGW
IP over E1/T1/CSTM-1
IP over FE/GE
MSC
IP over FE/GE
MSC
IP over FE/GE
IP over E1/T1/
CSTM-1
IP over E1/T1/
CSTM-1
IP over E1/T1/
CSTM-1
ROUTER

Similar to the TDM mode, the IP over E1/T1 mode allows the nodes on the E1 link to be
locked one by one.
The key techniques adopted in IP over E1/T1 are as follows:
1. ML-PPP/MC-PPP, which helps improve the reliability and bandwidth usage
ML-PPP: Multiple PPP links are bound to form one ML-PPP group to provide a link
with higher bandwidth. At the local end, a large IP packet is divided into several small
packets, which are then transmitted concurrently to the peer end over the PPP links. On
receiving the packets, the peer end reassembles the packets and restores the original IP
packet for further processing. By using the ML-PPP technique, multiple E1/T1s are
bound to provide load sharing for IP transmission. Therefore, the bandwidth utility is
improved.
MC-PPP: The priority scheme is introduced to the MC-PPP on the basis of the ML-PPP
to facilitate the timely transmission of the real-time data, thereby reducing the
transmission latency.
GBSS9.0
GBSS8.1
3-38

2. UDP multiplexing on the A interface, which helps save the bandwidth
UDP MUX for A Transmission: After A over IP is introduced, the RTP/UDP/IP
encapsulation method is applied to the data of the user plane, therefore reducing
transmission efficiency. By using the UDP MUX for A Transmission feature, however,
multiple RTP packets use one UDP packet header. As a result, the proportion of the
packet header to the entire packet decreases, and therefore the A interface transmission
efficiency increases. For details, see GBFD-118610 UDP MUX for A Transmission.

In IP over E1 mode, only the POUc board supports UDP MUX.
System Capacity
No impact.
Network Performance
No impact.
3.29.3 Interfaces
Inter-NE Interface
No impact.
The BSC supports the configuration of PPP and ML-PPP links.
The BSC supports CRTP compression in PPP mode.
3.29.4 Operation
The interface boards that support A IP over E1/T1 on the BSC side are as follows:
POUc: providing 4 routes of channelized STM-1/OC3 interfaces
PEUa: providing 32 routes of E1/T1/J1 IP interfaces
ADD BRD: used to add a POUc (with Logical function type set to IP)
ADD PPPLNK: used to add a PPP link
ADD SCTPLNK: used to add an SCTP link (carried on a PPP link) on the signaling
plane
ADD IPPATH: used to add an IP path (carried on a PPP link) on the user plane
Other configurations such as the configurations of the M3UA and neighboring nodes remain
the same.
GBSS9.0
GBSS8.1
3-39

3.30 GBFD-118610 UDP MUX for A Transmission
3.30.1 Description
In A over IP, the RTP/UDP/IP encapsulation method is applied to the packets of the user plane,
therefore reducing transmission efficiency, particularly transmission efficiency of small
packets of CS data.
By using the UDP MUX for A Transmission feature, a UDP multiplexing subheader shorter
than UDP is added and multiple RTP packets use one UDP packet header. As a result, the
proportion of the packet header to the entire packet decreases, and therefore the efficiency of
transmission over the A interface can be increased by 30% to 40% depending on the number
of packets that are multiplexed.
UDP multiplexing is supported regardless of whether the RTP header is compressed. The
UDP multiplexing is independent of the transmission mode. That is, the UDP multiplexing is
applicable to IP over E1/T1, IP over channelized STM-1 (CPOS), or IP over FE/GE.
System Capacity
No impact.
Network Performance
No impact.
3.30.3 Interfaces
Inter-NE Interface
No impact.
The ADD IPMUX command is used to set IP MUX Type to UDP MUX.
3.30.4 Operation
To enable this feature, you must run the ADD IPMUX command to set IP MUX Type to
UDP MUX.
Then, set Sender UDP MUX Mode and Receive UDP MUX Mode to one of the following
values:
MUXCLOSE
NORTPCOMP
RTPCOMP
GBSS9.0
GBSS8.1
3-40

3.31 GBFD-118609 IP Fault Detection Based on BFD
3.31.1 Description
Huawei GBSS supports the bidirectional forwarding detection (BFD) of the faults on the Abis
interface, A interface, and Gb interface. BFD is a method for detecting IP connection failures
by periodically transferring BFD packets between two nodes. When no BFD packet is
received within the period of several detection intervals, the transmission fails. In this case,
procedures such as port switchover, board switchover, and IP re-routing are triggered to
prevent traffic loss. The period of BDF detection is about 100 ms, and therefore it can be used
for telecom services carried by the IP network.
BFD involves two cases: one hop and multi-hop. In the case of one hop, the two nodes of the
BFD are the BSC and the nearest layer 3 device connecting to the BSC, such as a router, a
BTS, or an MGW. In the case of multi-hop, the two nodes of the BFD are the BSC and the
configured peer entity, such as a BTS, an MGW, or an SGSN.
The BFD is applicable in the following scenarios:
1. The BSC is connected to the peer device such as a BTS, an MGW, or an SGSN by using a
router. In this case, the BFD can be used to check whether the router is available.

The BFD is activated for the fault detection of p1 and p2. If p1 is faulty, the BSC triggers an
IP re-routing procedure. The packet is then sent and received over p2.
2. The BSC is connected directly to a peer device such as a BTS, an MGW, or an SGSN. In
this case, the BFD can be used to check whether the peer device is available.

GBSS9.0
GBSS8.1
3-41

The BFD is activated for the fault detection of p1 and p2. If p1 is faulty, the BSC triggers an
IP re-routing procedure. The packet is then sent and received over p2.
System Capacity
No impact.
Network Performance
No impact.
3.31.3 Interfaces
Inter-NE Interface
The NE at the peer end must support the BFD feature.
The BFD configurations on the BSC side are added on the BSC side.
The BFD configurations on the BTS side are added on the BSC side.
3.31.4 Operation
STR IPCHK: used to configure parameters related to the one-hop BFD and multi-hop
BFD on the BSC side
SET BFDPROTOSW: used to set Bfd Protocol Switch to BFD_ON(ON) on the BSC
side
ADD IPRTBIND: used to bind the route with the multi-hop BFD on the BSC side
ADD IPPATHBIND: used to bind IP paths with the multi-hop BFD on the BSC side
ADD BTSBFD: used to add a BFD session on the BTS side
ADD BTSIPRTBIND: used to bind the BTS route with the BFD on the BTS side
3.32 GBFD-118630 Ethernet OAM
3.32.1 Description
With the evolution of the GSM network towards an all-IP network, the Ethernet is widely
used for data transmission. As a Layer 2 protocol, Ethernet OAM can report the status of the
network at the data link layer to monitor and manage the network more effectively. The
functions of Ethernet OAM consist of fault detection, notification, verification, and
identification. The faults include hardware faults that can be detected at the physical layer,
such as link interruption, and software faults that cannot be detected at the physical layer,
such as memory bridging unit damage. Ethernet OAM plays a significant role in reducing the
CAPEX and OPEX, as well as in complying with the Service Level Agreement (SLA).
GBSS9.0
GBSS8.1
3-42

The GBSS supports two types of Ethernet OAM: point-to-point Ethernet OAM (802.3ah) and
end-to-end Ethernet OAM (802.1ag).
1. Point-to-point Ethernet OAM
The point-to-point Ethernet OAM, as shown in Figure 3-5, complies with IEEE 802.3ah. The
point-to-point Ethernet OAM is used for the last-mile issues rather than for specific services.
The OAM implements point-to-point maintenance of the Ethernet using mechanisms such as
OAM discovery, loopback, link monitoring, and fault detection.
Figure 3-5 Point-to-point Ethernet OAM

2. End-to-end Ethernet OAM
The end-to-end Ethernet OAM complies with IEEE 802.1ag. The end-to-end Ethernet OAM
performs Ethernet maintenance based on the services and maintenance domain (MD).
When the BSC detects Ethernet faults or degraded network performance through the Ethernet
OAM, the BSC performs route reselection, port switchover, or board switchover to ensure the
proper communication on the Ethernet.
System Capacity
No impact.
Network Performance
No impact.
3.32.3 Interfaces
Inter-NE Interface
The peer end must support the Ethernet OAM protocol.
The configuration related to Ethernet OAM on the BSC side is performed on the BSC side.
GBSS9.0
GBSS8.1
3-43

The configuration related to Ethernet OAM on the BTS side is performed on the BSC side.
3.32.4 Operation
1. Point-to-point Ethernet OAM (802.3ah):
Associated operations can be performed on the BSC side by using the following MML
commands:
ACT ETHOAMAH: used to activate the link monitoring function
DEA ETHOAMAH: used to deactivate the link monitoring function
LST ETHOAMAH: used to query the current configuration
STR ETHOAMLOOPTST: used to enable the remote loopback function
STP ETHOAMLOOPTST: used to disable the remote loopback function
DSP ETHOAMLOOPTST: used to query the remote loopback function
Associated operations can be performed on the BTS side by using the following MML
commands:
ACT BTSETHOAMAH: used to activate the link monitoring function
DEA BTSETHOAMAH: used to deactivate the link monitoring function
2. End-to-end Ethernet OAM (802.1ag):
Associated operations can be performed on the BSC side by using the following MML
commands:
ADD ETHMA: used to add the maintenance association (MA)
ADD ETHMD: used to add an MD
ADD ETHMEP: used to add a maintenance end point (MEP)
ACT ETHCC: used to activate a continuity check (CC)
PING MAC: used to conduct a loopback test
TRC MAC: used to trace a link
Associated operations can be performed on the BTS side by using the following MML
commands:
ADD BTSETHMA: used to add an MA
ADD BTSETHMD: used to add an MD
ADD BTSETHLCMEP: used to add a local MEP
ADD BTSETHRMMEP: used to add a remote MEP
ACT BTSETHCC: used to activate a CC
PING BTSCFM: used to conduct a loopback test
TRC BTSCFM: used to trace a link
GBSS9.0
GBSS8.1
3-44

3.33 GBFD-510801 MSRD
3.33.1 Description
The MS Receive Diversity (MSRD) feature improves the signal receiving capability of the
MS. With the introduction of the Dual Antenna Interference Cancellation (DAIC) technique,
MSRD enables MSs to obtain enhanced channel diversity capability and the GMSK
modulation scheme to have an equivalent anti-interference capability as the 8PSK modulation
scheme. Therefore, the data rate of the MSs is improved and the capacity of the system is
expanded.
System Capacity
No impact.
Network Performance
By using the MSRD feature, the performance of PS services at the cell edge is improved.
3.33.3 Interfaces
Inter-NE Interface
No impact.
No impact.
3.33.4 Operation
The MS must support this feature.
The SET GCELLPSCHM command is used to set MSRD PDCH Multiplex Threshold and
MSRD MCS Threshold.
When the load of downlink PS services is higher than MSRD PDCH Multiplex Threshold,
the allocation of dual carriers for the MS cannot effectively improve the downlink throughput
of the PS services in the entire cell. Therefore, the BSC does not allocate dual carriers to the
MS but enables the MS to be in MSRD mode.
When the coding scheme used by the MS is lower than MSRD MCS Threshold, the C/I of
the place where the MS is located is low. In this case, the use of dual RX antennas can
improve the C/I. Therefore, the BSC does not allocate dual carriers to the MS but enables the
MS to be in MSRD mode.
GBSS9.0
GBSS8.1
3-45

3.34 GBFD-510802 Dual Carriers in Downlink
3.34.1 Description
Dual Carriers in Downlink increases the number of timeslots on which the data can be
received by an MS in a radio block period, therefore increasing the data rate of the MS.
Take an MS supporting EGPRS2-A as an example. In normal conditions, the MS can receive
the data on only one carrier and a maximum of five timeslots can be allocated in a radio block
period. Assume that the highest-rate coding scheme DAS12 is used. Then, the data rate on
each timeslot is 98.4 kbit/s, and the maximum data rate of the MS is 98.4 x 5 = 492 kbit/s.
With this feature, the MS can receive data on two carriers in one radio block period. Therefore,
a maximum of 10 timeslots can be allocated and the maximum data rate of the MS is 98.4 x
10 = 984 kbit/s when DAS12 is used.
System Capacity
No impact.
Network Performance
No impact.
3.34.3 Interfaces
Inter-NE Interface
The MS must support this feature. Whether the MS supports this feature is indicated in the
classmark3 and radio access capability.
The NSS indicates whether the MS uses dual carriers or a single carrier in the downlink in the
command for assigning the downlink TBF, and indicates whether the MS uses dual carriers or
a single carrier in the downlink in the command for reassigning the timeslots of the PS
services.
The LST GCELLGPRS command is used to query whether the Dual Carriers in Downlink
feature is supported in a cell.
3.34.4 Operation
The MS must support the Dual Carriers in Downlink feature.
The SET GCELLGPRS command is used to configure the Dual Carriers in Downlink
feature.
GBSS9.0
GBSS8.1
3-46

3.35 GBFD-510803 Uplink EGPRS2-A
3.35.1 Description
One of the objectives of the evolution to the GSM/EDGE radio access network (GERAN) is
to increase the uplink and downlink rate of PS services. The HUGE solution, which complies
with 3GPP specifications, uses high-order modulation (16QAM) to increase the data rate on
the uplink of the GSM/EGPRS network, as shown in Figure 3-6.
The uplink EGPRS2-A is the first phase of HUGE. With the introduction of the uplink
EGPRS2-A technique, the rate of PS services on the uplink is increased by 30%. When four
timeslots are used on the uplink, the theoretical rate of EGPRS is increased from 236.8 kbit/s
to 307.6 kbit/s.
Figure 3-6 16QAM modulation in the GSM/EGPRS network

Table 3-1 lists the new modulation and coding schemes (MCSs) supported by EGPRS2-A.
GBSS9.0
GBSS8.1
3-47

Table 3-1 New MCSs supported by EGPRS2-A
Coding Scheme UAS-7 UAS-8 UAS-9 UAS-10 UAS-11
Modulation Scheme 16QAM
Family B Apad10 A B Apad10
Bit Rate (kbit/TS) 44.8 51.2 59.2 67.2 76.8
Number of RLC Data Blocks 2 2 2 3 3
Payload (octets) 2x56 2x64 2x74 3x56 3x64

This feature is a trial feature in GBSS9.0 and is not recommended for commercial use.
System Capacity
No impact.
Network Performance
By using the EGPRS2-A feature, the uplink throughput at the EGPRS RLC and LLC layers is
improved.
The bandwidth over the Abis and Gb interfaces needs to be expanded.
3.35.3 Interfaces
Inter-NE Interface
1. The BSC and BTS need to negotiate with each other to support the EGPRS2. The BTS
reports the baseband processing capability. The BSC sends information such as the power
attenuation of the new modulation scheme and the transmit diversity latency.
2. The packet frame structure over the Abis interface supports the new uplink modulation
mode.
3. The MS must support the EGPRS2 feature. For an MS, the uplink EGPRS2-A and
downlink EGPRS2-A are independent. Whether the EGPRS2 is supported is indicated in the
Based on the supporting capability of the MS, BTS, and cell, the BSC specifies a proper
EGPRS grade in the uplink or downlink TBF assignment command. In addition, the BSC
supports the switchover between the EGPRS and the EGPRS2-A.
The EGPRS2 information is displayed in the query results of the BTS, TRX, and channel
attributes.
GBSS9.0
GBSS8.1
3-48

3.35.4 Operation
The MS must support EGPRS2-A.
The BTS must support EGPRS2-A.
Only the BTSs configured with the MRRU/GRRU support EGPRS2-A.
EGPRS2-A is supported only in IP over Abis or IP over HDLC mode.
The SET GCELLGPRS command is used to configure EGPRS2-A.
3.36 GBFD-510804 Downlink EGPRS2-A
3.36.1 Description
One of the objectives of evolution to the GERAN is to increase the uplink and downlink rate
of the PS services. The 3GPP GERAN uses the REduced symbol Duration/Higher Order
modulation and Turbo codes (REDHOT) solution to increase the data rate on the downlink.
With high-order modulation (16QAM or 32QAM), high symbol rate (1.2 times), and Turbo
codes, the GSM/EGPRS network supports higher downlink data rate, as shown in Figure 3-7.
The downlink EGPRS2-A is the first phase of REDHOT. With the introduction of the
downlink EGPRS2-A technology, the rate of PS services on the downlink is doubled. When
10 ms TTI is used in the downlink, the theoretical data rate of EGPRS increases from 592
kbit/s to 984 kbit/s.
Figure 3-7 16QAM and 32QAM modulation in the GSM/EGPRS network

Table 3-2 lists the new MCS coding schemes supported by EGPRS2-A.
GBSS9.0
GBSS8.1
3-49

Table 3-2 New MCS coding schemes supported by EGPRS2-A
Coding
Scheme
DAS-
5
DAS-
6
DAS-
7
DAS-
8
DAS-
9
DAS-1
0
DAS-1
1
DAS-1
2
Modulatio
n Scheme
8PSK 16QAM 32QAM
Family B Ap Bp B Ap Bp Ap Bp
Bit Rate
(kbit/TS)
22.4 27.2 32.8 44.8 54.4 65.6 81.6 98.4
Number of
RLC Data
Blocks
1 2 2 3
Payload
(octets)
1x56 1x68 1x82 2x56 2x68 2x82 3x68 3x82

This feature is a trial feature in GBSS9.0 and is not recommended for commercial use.
System Capacity
No impact.
Network Performance
By using the Downlink EGPRS2-A feature, the downlink throughput at the EGPRS RLC and
LLC layers is improved.
The bandwidth over the Abis and Gb interfaces needs to be expanded.
3.36.3 Interfaces
Inter-NE Interface
1. The BSC and BTS need to negotiate with each other to support the EGPRS2. The BTS is
responsible for reporting the baseband processing capability. The BSC is responsible for
sending the information such as power attenuation and transmit diversity latency of the new
modulation scheme.
2. The structure of packet frames transmitted over the Abis interface supports the new
downlink modulation mode.
3. The MS must support the EGPRS2 feature. For an MS, the uplink EGPRS2-A and
downlink EGPRS2-A are independent. Whether the EGPRS2 is supported is indicated in the
Based on the supporting capability of the MS, BTS, and cell, the BSC specifies a proper
EGPRS grade in the uplink or downlink TBF assignment command. In addition, the BSC
supports the switchover between the EGPRS and the EGPRS2-A.
GBSS9.0
GBSS8.1
3-50

The EGPRS2 information can be displayed by querying the BTS, TRX, and channel
attributes.
3.36.4 Operation
The MS must support EGPRS2-A.
The BTS must support EGPRS2-A. Only BTSs configured with the MRRU or GRRU board
support EGPRS2-A.
EGPRS2-A is supported only in IP over Abis or IP over HDLC mode.
The SET GCELLGPRS command is used to configure EGPRS2-A.
3.37 GBFD-510805 Latency Reduction
3.37.1 Description
Latency reduction is important for GERAN evolution. In GERAN, VoIP services require the
end-to-end service latency to be shorter than 300 ms and the Frame Error Rate (FER) not to
exceed 2%. If the latency is short enough, the data can be retransmitted to reduce the FER of
VoIP services, therefore improving the user experience. In addition, short latency can improve
the user experience on interactive and streaming services.
Two techniques are used to reduce the latency: reduced TTI (RTTI) and fast Ack/Nack report
(FANR).
RTTI: One radio block is transmitted over four bursts, which are carried by two timeslots. On
each timeslot, the radio blocks of 10 ms TTI are transmitted. In this manner, the four bursts
are transmitted on two consecutive TDMA frames, as shown in Figure 3-8.
Figure 3-8 Latency reduction

With the introduction of the RTTI, the transmission latency on the Um interface and the TTI
in the access network are reduced. The TTI is reduced from 130 ms (when 20 ms TTI is used)
GBSS9.0
GBSS8.1
3-51

to 60 ms (when 10 ms RTTI is used), and the single retransmission latency is reduced from
185 ms (when 20 ms TTI is used) to 95 ms (when 10 ms RTTI is used).
FANR: The RTTI can reduce the transmission latency. Under the existing Ack/Nack reporting
policy, however, when an RLC data block is erroneous or missing, the problem cannot be
immediately reported to the sender. Therefore, the RLC data block cannot be retransmitted in
time. As a result, latency is generated for assembling RLC data blocks into an LLC PDU.
Therefore, an efficient Ack/Nack feedback policy is required to reduce the LLC PDU
reassembly latency. Huawei BSCs support FANR and enable the immediate feedback of data
errors and retransmission of RLC data blocks. In this manner, the LLC PDU reassembly
latency is decreased and the signaling overhead is reduced.
System Capacity
No impact.
Network Performance
The RTT of the radio access network and the Um latency are reduced. The TTI is reduced
from 130 ms (when 20 ms TTI is used) to 60 ms (when 10 ms RTTI is used), and the single
retransmission latency is reduced from 185 ms (when 20 ms TTI is used) to 95 ms (when 10
ms RTTI is used).
3.37.3 Interfaces
Inter-NE Interface
The MS must support the Latency Reduction feature. The MS supports the RTTI and FANR
simultaneously. Whether the reduced latency capability is supported is indicated in the
classmark3 and radio access capability. In addition, the MS can carry "One Phase Access
Request by Reduced Latency MS" in the 11-bit EGPRS Packet Channel Request message to
indicate whether the reduced latency capability is supported. After receiving the request, the
BSC establishes the uplink RTTI TBF by sending the IMMEDIATE ASSIGNMENT message.
In the uplink TBF assignment command, the NSS specifies whether the MS uses 20 ms TTI
or 10 ms RTTI. If 10 ms RTTI is used, the PDCH pair of the TBF and USF mode should be
specified.
In the downlink TBF assignment command, the NSS specifies whether the MS uses 20 ms
TTI or 10 ms RTTI. If 10 ms RTTI mode is used, the PDCH pair of the TBF should be
specified. The BSC pairs the RTTI channels into (0, 1), (2, 3), (4, 5), and (6, 7), as specified
by 3GPP specifications.
No impact.
3.37.4 Operation
If a cell supports EDGE, the SET GCELLGPRS command must be used to set Support
Reduced Latency Capability to SUPPORT(Support).
GBSS9.0
GBSS8.1
3-52

The BTS reports to the BSC whether the TRXs of the BTS support the Latency Reduction
feature.
The MS must support the reduced latency.
This feature is supported in built-in PCU mode.
The Latency Reduction feature is supported in Abis over IP or Abis over HDLC, and the 10
ms RTTI is used only for symmetrical latency-sensitive services such as conversational and
POC services.
3.38 GBFD-510901 2G/3G Neighboring Cell Automatic
Optimization
3.38.1 Description
By using the 2G/3G Neighboring Cell Automatic Optimization feature, operators can use the
2G network and the 3G network simultaneously. In addition, the 3G cells are configured as
the neighboring cells of the 2G cells. If the neighboring relationship is configured properly,
the quality of the GSM network can be improved and users can enjoy abundant 3G services. If
the neighboring relationship is not configured properly, there will be insufficient or redundant
neighboring cells. Insufficient neighboring cells prevent MSs from searching for neighboring
cells efficiently.
The 2G/3G Neighboring Cell Automatic Optimization feature must be supported by the MS,
BSC, M2000, and Nastar. The M2000 sends the list of cells whose neighboring cells must be
optimized, the list of neighboring 2G/3G cells that must be measured by the cells, and the
related measurement parameters to the BSC. Then, the BSC regularly sends the information
about the neighboring 2G/3G cells to the MS. After the MS measures a neighboring cell, the
information about the neighboring 2G/3G cell is sent to the BSC using measurement reports.
The BSC records the neighboring cell information to the traffic statistics and sends the
statistics to the M2000. The Nastar obtains the statistics from the M2000 and analyzes the
statistics to obtain the information about locations where cells are insufficient or redundant.
Figure 3-9 shows the networking for the 2G/3G Neighboring Cell Automatic Optimization
feature.
Figure 3-9 Networking for the 2G/3G Neighboring Cell Automatic Optimization feature

GBSS9.0
GBSS8.1
3-53

Huawei BSS supports two types of 3G neighboring cells: WCDMA neighboring cells (FDD
neighboring cells) and TD-SCDMA neighboring cells (TDD neighboring cells). One serving
cell supports only one type of neighboring cell.
System Capacity
No impact.
Network Performance
This feature helps increase the intra-RAT and inter-RAT handover success rate with the proper
configuration of neighboring relationship, which optimizes the GSM network performance
and improves the user experience.
3.38.3 Interfaces
Inter-NE Interface
No impact.
No impact.
3.38.4 Operation
The M2000 and Nastar must support the 2G/3G Neighboring Cell Automatic Optimization
feature.
This feature can be enabled only when the related features of the GBSS and Nastar are
available.
3.39 GBFD-511001 License Control for Urgency
3.39.1 Description
The license limitation can be removed by using MML commands on the LMT or M2000.
After removing the limitation, the devices can process services with their maximum
capacities.
For each R version, the operator can remove the license limitation three times by using MML
commands. The operation takes effect immediately after the commands are executed. The
validity period of each operation is seven days. After removing the license limitation three
times, the license limitation can be removed only by a software upgrade.
In GSM networks, this feature removes the license limitation from both the BSC and BTS
because the license is sent from the BSC to the BTS.
By using this feature, the operator can remove the license limitation in the case of a burst in
traffic volume due to natural disasters so that the network capacity can be increased.
GBSS9.0
GBSS8.1
3-54

System Capacity
The License Control for Urgency feature supports the maximum number of TRXs specified
by the license. Therefore, the network capacity can be increased by configuring the maximum
number of TRXs. If the AMR HR feature is enabled, the maximum number of the TRXs
supporting half-rate specified by the license can be used to increase the network capacity.
Network Performance
No impact.
3.39.3 Interfaces
Inter-NE Interface
No impact.
MML commands can be used on the BSC to enable or disable License Control for Urgency.
3.39.4 Operation
SET LICENSECTRL: used to enable the License Control for Urgency feature with a
validity period (seven days)
LST LICENSECTRL: used to query the remaining days and current status of the
validity period
DSP LICENSE: used to query the license items. The values of the license items
displayed in the returned result are maximum values.
SET LICENSECTRL: used to disable the License Control for Urgency feature. If the
command is not executed within seven days, the feature is disabled automatically.
3.40 GBFD-511101 Load Based Handover Enhancement on
Iur-g
3.40.1 Description
Based on Huawei proprietary information exchange mechanism over the Iur-g interface, this
feature improves the accuracy of the handover between the GSM network and the UMTS
network due to non-coverage issues. As a result, the load of the GSM network and the UMTS
network in the same coverage area increases evenly, and the number of ping-pong handovers
due to incorrect handover decisions is reduced.
GBSS9.0
GBSS8.1
3-55

System Capacity
No impact.
Network Performance
Based on the Huawei proprietary information exchange mechanism over the Iur-g interface,
this feature allows for the selection of best target cells during inter-RAT handovers. In
addition, the probability of the ping-pong handovers due to the high load of the neighboring
inter-RAT cell can be reduced if the following requirements are met:
The neighboring 3G cell whose load meets certain requirements is selected.
The difference between the load in the source cell and the load in the target 2G cell
exceeds the configured threshold.
The handover does not lead to congestion in the target cell.
3.40.3 Interfaces
Inter-NE Interface
This feature is applicable to the scenario where 2G and 3G networks coexist and the BSC and
RNC are configured in the same cabinet. An IP interface board is required for the connection
between the BSC and the RNC.
No impact.
3.40.4 Operation
1. The Iur-g interface is configured by using the following commands:
ADD N7DPC: used to set DSP index and OSP index, DSP type to IUR_G(IUR_G),
and DSP bear type to M3UA(M3UA)
ADD GNRNC: used to add a neighboring RNC, set the MCC, MNC, and index of the
RNC, and set CO-MBSC to YES(Yes)
ADD GIURGCONN: used to add an Iur-g connection
2. The CORRM load handover enhancement is configured by using the following commands:
SET GCELLHOBASIC: used to set Index Type to BYID(By Index), set Cell Index,
and set Intracell HO Allowed to YES(Yes)
SET OTHSOFTPARA: used to set CS 2G 3G Load Balance Delta Threshold
SET GCELLHOINTERRATLDB: used to set Index Type to BYID(By Index), Allow
Inter-RAT Load HO in Connect State to YES(Yes) and set Cell Index
GBSS9.0
GBSS8.1
3-56

3.41 GBFD-111705 GSM Flow Control
3.41.1 Description
When the system is overloaded, this feature reduces the accessing traffic or disables some OM
functions according to the priority. This ensures the operation of basic services and enables
the system to restore to the normal state within a short period of time.
Compared with the BSC6000, the BSC6900 architecture is changed and its capacity is
increased. The value ranges and default values of some parameters associated with flow
control are changed, so that the traffic threshold for triggering flow control in the BSC6900 is
higher than that in the BSC6000.
System Capacity
No impact.
Network Performance
Table 3-3 lists the changed flow control parameters of the BSC6900 compared with the
BSC6000.
Table 3-3 Changed flow control parameters
Parameter BSC6000 BSC6900
Average PS CHAN REQ
Num
800 (per second) 200 (per second)
Max CS Paging Message
Num in Period
160 (per second) 660 (per second)

The Average PS CHAN REQ Num parameter specifies the number of UL PS access
attempts to be permitted in a flow control period. PS flow control is triggered when the UL PS
access attempts exceed this threshold. This parameter for the BSC6000 is used to limit the
number of PS access requests permitted to each GMPS/GEPS in a specified period. For the
BSC6900, this parameter is used to restrict the number of PS access requests to each CPUS in
a specified period. In the BSC6900, each GMPS/GEPS contains seven CPUSs. Therefore,
after the BSC6000 is upgraded to the BSC6900, the value of the Average PS CHAN REQ
Num parameter changes from 800 to 1400. This increases the PS access attempts to be
permitted by a BSC in a specified period and increases the PS traffic. Resource preemption
between CS and PS services, however, increases when both CS and PS services have a high
traffic.
Max CS Paging Message Num in Period specifies the number of paging messages that can
be received by the BSC over the A interface in a period. Paging flow control is triggered when
the number of received paging messages exceeds this threshold. The default value of this
parameter for the BSC6000 is 160 (per second), whereas the default value of this parameter
for the BSC6900 is 660 (per second), about four times the BSC6000 capability. Since this
parameter is increased for the BSC6900, the A, Abis, and Um interfaces will process larger
signaling flows, which improves the system processing capability. When a large number of
GBSS9.0
GBSS8.1
3-57

paging messages are received continuously, the A interface of the BSC6000 will discard fewer
paging messages. This may trigger flow control over the Abis and Um interfaces, which have
relatively lower capabilities in signaling flow processing, and therefore increases the
probability of congestion over the Abis and Um interfaces.
3.41.3 Interfaces
Inter-NE Interface
No impact.
Flow control parameters can be set and modified by using MML commands.
3.41.4 Operation
1. Querying flow control parameters
The MML command BSCFCPARA is used to query flow control parameters on a BSC.
2. Modifying flow control parameters
The MML command SET BSCFCPARA is used to set or modify flow control parameters
such as Average PS CHAN REQ Num and Max CS Paging Message Num in Period.
3.42 GBFD-114302 GSM/TD-SCDMA Interoperability
3.42.1 Description
This feature enables dual-mode MSs to be handed over and also enables cell reselection
between a GSM network and a TD-SCDMA network when the MSs are processing CS
services. This feature does not support PS handovers yet. Therefore, MSs reselect cells
between a GPRS/EDGE network and a TD-SCDMA network through autonomous cell
reselection. Inter-RAT NACC facilitates cell reselection from a TD-SCDMA network to a
GPRS/EDGE network.
System Capacity
No impact.
Network Performance
Owing to the limitation by the protocol, NACC cannot be used for cell reselection from a
GPRS/EDGE network to a TD-SCDMA network. After reselecting to a TD-SCDMA cell, an
MS will intercept system messages on the CCCH. Therefore, if there are a large number of
redundant system messages, latency of cell reselection will be extended. GBSS9.0 simplifies
SI2 Quarter so that the first message of SI2 Quarter carries four TDD ARFCNs (three
ARFCNs were carried previously), thereby reducing the cell reselection latency.
GBSS9.0
GBSS8.1
3-58

The latency of cell reselection from a GPRS/EDGE to a TD-SCDMA cell is decreased to
enhance the UL/DL rate of PS services.
3.42.3 Interfaces
Inter-NE Interface
No impact.
No impact.
3.42.4 Operation
No impact.
3.43 PS Channel Resources Load Sharing
3.43.1 Description
PS load sharing is performed to dynamically distribute users on the PDCH according to the
PDCH load. It aims to increase channel usage and PS service rates of single users.
System Capacity
No impact.
Network Performance
When performing load sharing, GBSS8.1 does not take into account the continuity of channel
groups after channel transfer. This may lead to invalid channel transfer. To solve this problem,
GBSS9.0 improves the PS channel resource load sharing algorithm to ensure continuity of
channel groups after channel transfer. In addition, when the required timeslot capability is not
reached, channels of other carriers can also be used for dynamic channel transfer. This ensures
the continuity of transferred channels and therefore improves resource utilization.
3.43.3 Interfaces
Inter-NE Interface
No impact.
No impact.
GBSS9.0
GBSS8.1
3-59

3.43.4 Operation
No impact.
3.44 GBFD-119205 Dynamically Adjusting the RRBP
Frequency
3.44.1 Description
When RRBP in a DL data block is validated on the NSS side, the MS must send a
DOWNLINK ACK message in a specified UL data block to acknowledge the reception of the
DL data block.
When dynamic adjustment of transmission interval of the RRBP field is enabled, the
transmission interval of RRBP is adjusted dynamically according to the status of UL and DL
TBFs. When there are UL TBFs or it is the late phase of delayed TBF release, RRBP is
transmitted at a long interval to save the UL transmission resource. When there is no UL TBF
or it is the early phase of delayed TBF release, RRBP is transmitted at a short interval to
quicken the access of MSs.
System Capacity
No impact.
Network Performance
In the EDA scenario, if an MS is processing preferential UL services and only a small amount
of DL data needs to be transmitted, the delayed DL release is easily triggered. In this case,
RRBP is validated on the NSS side frequently, preventing the UL rates from increasing. In the
EDA scenario of GBSS9.0, the RRBP is not validated 200 ms later than the previous setting
of the RRBP when DL TBF enters the delayed release state after a new DL data block (FBI
not equal to 1) is transmitted after another delayed release of DL TBF.
This feature increases the UL rate in the EDA scenario and achieves a 10% increase in the
upload rate during the CQT that is not affected by the environment.
3.44.3 Interfaces
Inter-NE Interface
No impact.
No impact.
3.44.4 Operation
No impact.
GBSS9.0
GBSS8.1
3-60

3.45 PS Services (EGPRS and GPRS Services)
3.45.1 Description
In GBSS9.0, PS services, including EGPRS and GRPS services, are enhanced in the
following performance counters:
1. TBF call drop rate
GBSS9.0 optimizes the re-assignment procedure to decrease the TBF call drop rate caused by
the preemption of CS services when there is high CS traffic. In addition, the GRFU/MRFU
does not allow 8PSK to be used by all carriers. Therefore, if the BTS does not report the
8PSK processing capability, uplink 8PSK blocks cannot be resolved, which leads to call drops.
To solve this problem, GBSS9.0 enables the BTS to report the 8PSK processing capability.
2. Latency
GBSS9.0 supports synchronization between the DL TRAU and the BTS in terms of
transmission time. RTT latency is decreased by 30 ms to 40 ms when Abis over TDM is
enabled.
3. PS data rate
When the DXX equipment is used on a live network, the block error rate (BLER) may
increase due to a big difference between the latency of the primary and secondary links. This
affects the access, call hold, and transmission performance of PS services. GBSS9.0 adjusts
the strategies for configuring idle timeslots to reduce the frame error rate (FER) and increase
the PS rate in the circumstance of serious latency inconsistency, which is caused by multiple
transmission paths.
System Capacity
No impact.
Network Performance
This feature improves the PS performance of access, call hold, and transmission.
3.45.3 Interfaces
Inter-NE Interface
No impact.
Abis timeslots can be re-arranged by using MML commands.
3.45.4 Operation
The TID BTSABISTS command is used to re-arrange Abis timeslots.
GBSS9.0
GBSS8.1
3-61

3.46 GBFD-119501 Adaptive Adjustment of Uplink and
Downlink Channels
3.46.1 Description
This feature dynamically adjusts the number of uplink and downlink channels allocated to an
MS based on the uplink and downlink traffic volume.
System Capacity
No impact.
Network Performance
The NSS re-assigns channel resources by sending a timeslot re-assignment command to
an MS when channel resources change. The NSS re-assigns channel resources by
sending a timeslot re-assignment command to an MS when channel resources change. It
takes the MS 480 ms to handle a timeslot re-assignment command, which reduces the
UL and DL rates. Therefore, timeslot re-assignment should be performed only when
necessary.
GBSS9.0 improves this feature by using the existing TAIs and USFs, which prevents
unnecessary timeslot re-assignment caused by changes in TAI and TFI. UL and DL rates
are increased in this manner.
3.46.3 Interfaces
Inter-NE Interface
No impact.
No impact.
3.46.4 Operation
No impact.
3.47 GBFD-110607 Direct Retry
3.47.1 Description
Direct retry is a special type of handover. It is initiated by the BSC to hand over an MS to a
neighboring cell when no traffic channel is available in the serving cell for assignment or the
serving cell is overloaded. Direct retry can help balance traffic among cells and reduce
congestion of the serving cell to raise the access success rate.
GBSS9.0
GBSS8.1
3-62

For a call setup attempt initiated by an MS, the BSC determines the assignment mode to be
used according to the load of the serving cell after it receives an ASSIGN REQ message from
the MSC. The three assignment modes are normal assignment, mode modification, and direct
retry. If the serving cell is overloaded and unable to handle new call setup attempts or if
possible accessed new call setup attempts affect ongoing services, the BSC initiates direct
retry.
Based on the homing BSCs and MSCs of the serving cell and target cell, a direct retry can be
an intra-BSC, inter-BSC, or inter-MSC direct retry. Direct retry can reduce the call access
failures caused by TCH congestion in the serving cell and increase the access success rate.
System Capacity
No impact.
Network Performance
GBSS9.0 optimizes the direct retry procedure. If direct retry to a target cell fails, the MS is
handed over to the serving cell again, and the channel assignment will be successful if there is
any available channel in the serving cell at the moment. The congestion rate decreases when
Directed Retry and Assignment Cell Load Judge Enable are enabled.
3.47.3 Interfaces
Inter-NE Interface
No impact.
No impact.
3.47.4 Operation
No impact.
3.48 GBFD-110303 Paging
3.48.1 Description
The paging procedure is used to instruct an MS to access the network.
An idle MS keeps listening to the paging channels in order to receive calls at any time.
After receiving a paging message, the MS sends a reply to proceed with the call
connection setup procedure.
There are PS and CS paging procedures. The SGSN initiates a PS paging procedure
when there is downlink data for an MS. PS paging messages are carried on the PCCCH
(if configured) or on the PCH if no PCCCH is configured.
GBSS9.0
GBSS8.1
3-63

CS paging messages are carried on the PCH. When a call setup attempt reaches the MSC
of the called MS, the MSC determines the location area (LA) of the MS and broadcasts
paging messages to all BSCs in the location area. Based on the LA, the BSC determines
the cell to which the paging message should be sent and determines the paging group to
which the MS belongs according to the IMSI. Then, the BSC sends the paging message
to the corresponding BTS, and the BTS sends the paging message to the MS through the
PCH.
Huawei GBSS supports the paging queue, paging retransmission, paging combination,
and paging flow control functions. These functions can effectively improve the paging
capacity of the BSC.
Paging queue
The paging messages of a paging group can be transmitted only on the CCCH blocks to
which the paging group is mapped. The paging queue function enables the BTS to
temporarily buffer the paging messages from the BSC and transmit a paging message.
The BTS selects a paging message and transmits it on the corresponding CCCH block
whenever possible. Paging messages of the same priority follow the rule of "first come,
first served (FCFS)".
Paging retransmission
Two-level retransmission is implemented by the MSC and BSS in a GSM network. One
level is at the MSC, where paging messages are retransmitted in a long period to handle
long interruptions. The other level is at the BTS, where paging messages are
retransmitted in a short time and traffic on the Abis and A interfaces can be reduced.
Huawei GBSS supports the paging retransmission function. When the CCCH block has
neither paging messages nor immediate assignment messages to be transmitted, the
paging messages that have been transmitted on this CCCH block will be retransmitted.
The maximum number of paging retransmissions of the same message is specified by a
system-level parameter.
Paging combination
The paging command that the BSC sends to the BTS contains a paging message only for
one MS, whereas a paging request sent over the Um interface contains paging messages
for a maximum of four MSs. To improve the paging efficiency, the BTS combines
paging messages for the maximum possible number of MSs into a paging command that
is sent over the Um interface. When CCCH blocks mapped to a paging group are polled,
the BTS searches for paging messages in the paging queue of the paging group,
encapsulates the maximum possible number of paging messages into proper type of
paging request messages, and sends the encapsulated messages over the Um interface to
the MS. In this way, paging messages for multiple MSs can be sent over the Um
interface at the same time.
Paging flow control
When the paging flow sent by the MSC exceeds the processing capability of the BSS, the
BSS controls the flow according to the current network status. The paging flow control
function ensures the robustness and normal working of the BSS, the high capability of
the BSS to process paging messages, and the smoothness and stability of services.
System Capacity
No impact.
GBSS9.0
GBSS8.1
3-64

Network Performance
The BSC of GBSS9.0 saves the IMSI and TMSI that are sent with paging messages over the
A interface. On receiving a new paging message, the BSC compares the IMSIs contained in
the message with stored IMSIs. If the IMSIs are the same, the new paging message is
regarded as the second paging message intended for the same MS.
GBSS9.0 optimizes the paging flow control mechanism. The BSC can identify the second
paging message for the same MS. If there is paging overload, the BSC discards second paging
messages according to the configured flow control policy to ensure success rate of the first
paging action.
Inter-NE Interface
No impact.
Flow control on second paging messages can be enabled by using MML commands.
3.48.3 Operation
To enable flow control on second paging messages, the SET BSCFCPARA command must
be used to set Paging Message Classifying Allowed to 2.
3.49 GBFD-115902 Transmit Diversity
3.49.1 Description
To implement transmit diversity, the two TRXs in a dual-transceiver unit are connected to a
pair of spatially separated antennas and transmit the same downlink signals on the same
frequency. Between the two carrier signals, controllable delay and changeable phase are
introduced to obtain gain based on time and spatial diversity. This increases strength of
received signals by reducing signal attenuation and therefore ensures signal coverage.
System Capacity
No impact.
Network Performance
In GBSS9.0, the default values of parameters associated with transmit diversity delay are
changed as follows:
1. Diversity Transmitter GMSK Delay: 20
2. Diversity Transmitter 8PSK Delay: 4
3. Diversity Transmitter 16QAM Delay: 4
4. Diversity Transmitter 32QAM Delay: 4
Through the preceding changes, the gain based on transmit diversity is increased.
GBSS9.0
GBSS8.1
3-65

3.49.3 Interfaces
Inter-NE Interface
No impact.
This feature is enabled by using MML commands.
3.49.4 Operation
No impact.
3.50 GBFD-117501 Enhanced Measurement Report (EMR)
3.50.1 Description
The enhanced measurement report (EMR) introduced in 3GPP Release 99 is a new downlink
measurement report sent from the MS to the network. Compared to a common measurement
report (MR), it has the following advantages:
1. An improved coding method enables an EMR to provide information about more
neighboring cells than an MR. An MR can provide information about a maximum of six
neighboring GSM cells, whereas an EMR can provide information about a maximum 15
neighboring GSM/WCDMA/TD-SCDMA cells. This facilitates interoperability between
the GSM and WCDMA/TD-SCDMA systems and ensures service continuity.
2. BEP, a new indicator of the channel quality, is added. Estimated on a per burst basis,
BEP is a comprehensive criterion reflecting the C/I ratio, signal delay extension, and MS
speed. It is coded in five bits while Receive Quality (RXQUAL) in three bits.
3. EMR contains the number of correctly received speech frames for calculating the Frame
Erase Ratio (FER). FER is the measurement of the coding/decoding performance of the
speech signals while RXQUAL is the measurement of the radio signals. Therefore, FER
outperforms RXQUAL in terms of speech quality measurement.
BEP and FER can improve the performance of the algorithms that are used on the basis of the
radio signal quality. They can replace the RXQUAL that is commonly used as an indicator of
the radio signal quality. In this way, the performance of the power control algorithms and
handover algorithms can be improved.
The 3GPP TS 44.018 specifies that the MI/2QUATER message sent to the MS contains the
information whether the MS sends an MR or EMR to report information about the serving and
neighboring cells.
System Capacity
No impact.
GBSS9.0
GBSS8.1
3-66

Network Performance
In GBSS9.0, according to the MEAN_BEP value in the EMR reported by the BTS and the
mapping between the MEAN_BEP and the quality class, the measurement report processing
function in the handover module obtains the quality class and accordingly performs insertion
and filtering on the EMR.
The handover success rate is increased in GBSS9.0.
The following table lists the mapping between the MEAN_BEP value and the quality class.
MEAN_BEP Quality Class (RXQUAL)
0 70
1 67
2 65
3 62
4 60
5 56
6 53
7 50
8 46
9 43
10 40
11 36
12 33
13 30
14 26
15 23
16 20
17 16
18 13
19 10
20 6
21 3
22 0
23 0
24 0
GBSS9.0
GBSS8.1
3-67

MEAN_BEP Quality Class (RXQUAL)
25 0
26 0
27 0
28 0
29 0
30 0
31 0

The values of quality levels listed in the preceding table are ten times the actual ones, and are the same
as the quality levels based on which handover filtering is performed.
3.50.3 Interfaces
Inter-NE Interface
No impact.
No impact.
3.50.4 Operation
No impact.
3.51 MRFD-210601 Connection with TMA (Tower
Mounted Amplifier)
3.51.1 Description
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 coverage.
In GBSS9.0, the maximum value of the TMA attenuation factor for the
MRRU/GRRU/MRFU/GRFU/BTS3900E is changed from 22 to 30 to support a high-gain
TMA.
GBSS9.0
GBSS8.1
3-68

System Capacity
No impact.
Network Performance
Some TMAs can provide high gain with a changed TMA attenuation factor.
3.51.3 Interfaces
Inter-NE Interface
No impact.
The maximum values of the Antenna Tributary 1 Factor and Antenna Tributary 2 Factor
parameters in the SET BTSRXUBP command are changed from 22 to 30.
3.51.4 Operation
No impact.

GBSS9.0 Network Impact Report

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

GBSS9.0 Network Impact Report

Uploaded by

Copyright:

Available Formats

GBSS9.

You might also like