BSC GSM

HUAWEI BSC6900 GSM
V900R014C00SPC500
Release Notes
Issue 01
Date 2012-04-26
HUAWEI TECHNOLOGIES CO., LTD.

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

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

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

Copyright © Huawei Technologies Co., Ltd..
HUAWEI BSC6900 GSM
V900R014C00SPC500 Release Notes About This Document
About This Document
Author
Prepared by Zhao Gang,Chen Jie,Wei Qi Date 2012-04-05
Reviewed by Yao Jianhui,Xu Jiajia, Dang Date 2012-04-08

Gang,Ni Huijun
Tested by Fu Xuedong Date 2012-04-10
Approved by Zou Yu Date 2012-04-26
Change History
Issue Date Author Description
01 2012-04-26 Zhao Gang,Chen Jie,Wei Qi First issue
Issue 01 (2012-04-26) Huawei Proprietary and Confidential ii

HUAWEI BSC6900 GSM
V900R014C00SPC500 Release Notes Contents
Contents
1 Version Requirements..................................................................................................................1
1.1 Product Version..................................................................................................................................................1
1.2 Software Versions..............................................................................................................................................1
1.3 Hardware Versions.............................................................................................................................................1
1.4 Related Product Versions...................................................................................................................................4
1.5 OS and Database Versions.................................................................................................................................7
1.6 Virus Scan Result...............................................................................................................................................7
2 Version Compatibility..................................................................................................................9
2.1 Compatibility with Earlier Product Versions.....................................................................................................9
2.2 Compatibility with Earlier Board Software Versions........................................................................................9
3 Important Notes...........................................................................................................................12
4 Changes from V900R014C00SPC300 to V900R014C00SPC500...........................................13
4.1 What's New......................................................................................................................................................13
4.1.1 Feature Updates......................................................................................................................................13
4.1.2 Hardware Updates..................................................................................................................................37
4.1.3 Command Line Updates.........................................................................................................................37
4.1.4 Parameter Updates..................................................................................................................................37
4.1.5 Alarm Updates........................................................................................................................................37
4.1.6 Event Updates.........................................................................................................................................38
4.1.7 Counter Updates.....................................................................................................................................38
4.1.8 License Updates......................................................................................................................................38
4.2 Resolved Issues................................................................................................................................................38
4.3 Known Issues...................................................................................................................................................76
5 Changes from V900R014C00SPC200 to V900R014C00SPC300...........................................78

5.1 What's New......................................................................................................................................................78
5.1.1 Feature Updates......................................................................................................................................78
5.1.2 Hardware Updates................................................................................................................................102
5.1.3 Command Line Updates.......................................................................................................................102
5.1.4 Parameter Updates................................................................................................................................102
5.1.5 Alarm Updates......................................................................................................................................102
5.1.6 Event Updates.......................................................................................................................................103
Issue 01 (2012-04-26) Huawei Proprietary and Confidential iii

HUAWEI BSC6900 GSM
V900R014C00SPC500 Release Notes Contents
5.1.7 Counter Updates...................................................................................................................................103

5.1.8 License Updates....................................................................................................................................103
5.2 Resolved Issues..............................................................................................................................................103
5.3 Known Issues.................................................................................................................................................111
6 Changes from V900R013C00SPC500 to V900R014C00SPC200.........................................112

6.1 What's New....................................................................................................................................................112
6.1.1 Feature Updates....................................................................................................................................112
6.1.5 Alarm Updates......................................................................................................................................254
6.1.6 Event Updates.......................................................................................................................................254
6.1.7 Counter Updates...................................................................................................................................254
6.1.8 License Updates....................................................................................................................................254
6.2 Resolved Issues..............................................................................................................................................254
6.3 Known Issues.................................................................................................................................................297
7 Changes from V900R012C01SPC500 to V900R014C00SPC200.........................................299

7.1 What's New....................................................................................................................................................299
7.1.1 Feature Updates....................................................................................................................................299
7.1.5 Alarm Updates......................................................................................................................................354
7.1.6 Event Updates.......................................................................................................................................354
7.1.7 Counter Updates...................................................................................................................................354
7.1.8 License Updates....................................................................................................................................354
7.2 Resolved Issues..............................................................................................................................................354
7.3 Known Issues.................................................................................................................................................395
8 Related Documentation............................................................................................................396
8.1 V900R014C00 Documentation......................................................................................................................396
8.2 Updates to Related Documentation...............................................................................................................396
8.2.1 Changes from V900R014C00SPC300 to V900R014C00SPC500.......................................................396
8.3 Obtaining Documentation..............................................................................................................................397
8.3.1 Support Website....................................................................................................................................397
Issue 01 (2012-04-26) Huawei Proprietary and Confidential iv

HUAWEI BSC6900 GSM
V900R014C00SPC500 Release Notes Version RequirementsVersion Requirements
1 Version Requirements
1.1 Product Version

Product Name HUAWEI BSC6900/HUAWEI BSC6000
Product Model HUAWEI BSC6900/HUAWEI BSC6000
Product Version V900R014C00SPC500
1.2 Software Versions

Software Name Software Version
LMT V900R014C00SPC500
OMU V900R014C00SPC500
M2000 mediation iManagerM2000_BSC6900GSM_MATCH_ENG_V200R012C
00SPC500
1.3 Hardware Versions

Physical Logical Board Bar Code PCB BIOS/Extended BootROM Upgrade
Board Name Label Version BIOS Version Required (Yes/No)
Name
SCUa SCUa WP11PSCUa Ver.D 258 Yes

SCUb SCUb WP11SCUb Ver.B 117 Yes
Issue 01 (2012-04-26) Huawei Proprietary and Confidential 1

HUAWEI BSC6900 GSM

Name
GCUa GCUa WP11GCUa Ver.B 224 Yes

Ver.C
Ver.F
GCGa GCGa WP11GCGa Ver.B 224 Yes
Ver.C
Ver.F
TNUa TNUa WP11PTSUa Ver.A 224 Yes
Ver.B
Ver.C
XPUa XPUa/GCP WP11XPUa Ver.B 257 Yes
XPUa/RGCP Ver.C
XPUa/MCP
DPUa DPUa/GTC WP11DPUa Ver.A 224 Yes
Ver.B
Ver.C
DPUb DPUb/GTC WP11DPUb Ver.C 224 Yes
DPUb/GPCU
DPUc DPUc/GTC WP11DPUc Ver.C 224 Yes
DPUd DPUd/GPCU WP11DPUd Ver.C 224 Yes
DPUf DPUf WP11PVCU Ver.B 117 Yes
DPUg DPUg WP11DPUg Ver.B 120 Yes
Ver.C
Ver.E
PEUa PEUa/FR WP11PEUa Ver.A 120 Yes
PEUa/HDLC
PEUa/IP
PEUa/Abis_IP
POUa POUa/IP WP11POUa Ver.A 120 Yes
FG2a FG2a/GbIP WP11FG2a Ver.A 120 Yes
FG2a/IP
GOUa GOUa/IP WP11GOUa Ver.A 120 Yes

HUAWEI BSC6900 GSM

Name
EIUa EIUa/Abis WP11EIUa Ver.A 255 Yes

EIUa/Ater Ver.B
EIUa/Pb
EIUa/A
OIUa OIUa/Abis WP11OIUa Ver.A 255 Yes
OIUa/Ater Ver.B
OIUa/Pb
OIUa/A
XPUb XPUb/GCP WP11XPUb Ver.B 120 Yes
XPUb/RGCP Ver.C
XPUb/MCP Ver.D
Ver.E
POUc POUc/TDM WP11POUc Ver.B 120 Yes
POUc/IP Ver.C
Ver.E
FG2c FG2c/IP WP11FG2c Ver.B 120 Yes
Ver.C
Ver.E
GOUc GOUc/IP WP11GOUc Ver.B 120 Yes
Ver.C
Ver.E
FG2d FG2d/IP WP11FG2d Ver.E 120 Yes
GOUd GOUd/IP WP11GOUd Ver.E 120 Yes
OMUa OMUa WP11OMUa - - -
OMUb OMUb WP11OMUb - - -
OMUc OMUc WP11OMUc Ver.B 025 Yes
DPUe DPUe WP11DPUe Ver.B 120 Yes
Ver.C
Ver.E
NIUa NIUa WP11PNIUa Ver.E 120 Yes
FG2d FG2d/IP WP11FG2d Ver.B 120 Yes
Ver.C
Ver.E

HUAWEI BSC6900 GSM

Name
GOUd GOUd/IP WP11GOUd Ver.B 120 Yes

Ver.C
Ver.E
1.4 Related Product Versions

Product Name Product Model Product Version Remarks
CBC CBC CBC V300R001B02D001

(recommended)
MSC G9 MSC9880 Developed on the CPCI
MSOFTX3000V100R005C01 platform
(recommended among the earlier
versions, which are compatible with
the current version of the BSC, in
cases other than IP transport on the A
interface)
The following versions or later
(required in the case of IP transport
on the A interface):
a) MSC9880 MSOFTX3000
V100R008C03
b) MSC9880 MSOFTX3000
V100R007C05
MSC9880
MSOFTX3000V100R008C03 or
later (required in the case of hybrid
IP transport on the A interface)
MSC9880 Developed on the
MSOFTX3000V200R008C03 ATCA platform
G6 MSCV620R004C02B027 NA
(recommended for China Mobile)
MSCV600R004B03D103
(recommended for China Unicom)
MSCV610R002B12D004
(recommended for other telecom
operators)

HUAWEI BSC6900 GSM
G3 MSCV300R005B04D005 NA
(recommended for deployment in
China)
MSCV330R006B08D004
(recommended for deployment in
regions out of China)
UMG UMG UMG V200R007C01 (recommended NA
among the earlier versions, which
are compatible with the current
version of the BSC, in cases other
than IP transport on the A interface)
UMG V200R008C03 or later
(required in the case of IP transport
on the A interface)
SGSN SGSN SGSN9810 V800R009C01 Developed on the CPCI
(recommended) platform
SGSN9810 V900R001C03 or later
(required for interoperability
between GSM and LTE)
GGSN GGSN GGSN9811 V900R007C01 Developed on the PGP
(recommended) platform
GGSN9811 V900R007C02 SPC500
or later (required for differentiation
between PS services)
M2000 M2000-II iManager M2000
V200R012C00SPC200 or later
CME CME iManager M2000-CME
VNP VNP V100R001C00SPC301 or later
INSIGHT INSIGHT SHARP INSIGHT SHARP
SHARP V100R002C00SPC500
NASTAR NASTAR iManager Nastar
MBTS MBTS BTS3900V100R007C00SPC200 or SRAN7.0
later
BTS3900 V100R004C00SPC100 or SRAN6.0
later
later
later

HUAWEI BSC6900 GSM
BTS BTS3900 series BTS3000V100R014C00SPC006 or BSS14.0

(including the BTS3900, later
BTS3900A, BTS3900L,
and DBS3900) BTS3000V100R0013C00SPC003 or BSS13.0
later
BTS3000V100R0012C00SPC025 or BSS12.0
later
BTS3900 V100R009C00SPC058 or BSS9.0
later
BTS3900 V100R009C00SPC081 or
later (required for Abis over IP)
BTS3000V100R008C11SPC003 or BSS8.1
later
Pico and micro BTS3000V600R013C00 or later BSS13.0
BTSs(BTS3900B/BTS39
00E) BTS3000V100R008C12SPC008 or BSS8.1
later
BTS3012 series BTS3000V200R0013C00 or later BSS13.0
(including the BTS3012,
BTS3012AE, BTS3012II, BTS3000V200R0012C00 or later BSS12.0
BTS3006C, and
BTS3002E)
later
later
BSS9.0 version required for Abis
over IP
BTS3X series For the BTS30/BTS312/BTS3012A: BSS7.0
G3BTS32V302R007C02SPC025 or
later
For the BTS3001C (micro cell): BSS7.0
G3BTS34V304R002C08 or later
For the BTS3002C (micro cell):
G3BTS36V306R007C01B018 or
later
BTS2X series Not supported NA
PCU PCU35 V300R008C03SPH008(recommende NA
d), compatible with all
V300R008C03 versions
PCU6000 V300R008C11SPH003(recommende NA
d), compatible with V300R008C03
and later

HUAWEI BSC6900 GSM
1.5 OS and Database Versions

OS Version Database Version Remarks
Windows 2003 Server mysql 5.0 Only the installation can be

Standard Edition SP2 performed.
Patch package: To download the patch package,

Win2k3ENx862011Basic perform the following steps:
Patches 1. Access
http://support.huawei.com.
2. After a successful login,
choose Software Center >
Version Software > Wireless
Product Line> SingleRAN >
SRAN O&M tools.
3. Download
“Win2k3ENx862011Basic” and
the detailed information about
the patch is listed in the
document “2011Basic Patches
information list_20120104.xls”.
Suse Linux 9 mysql 5.0 Only the installation can be
performed.
Dopra Linux mysql 5.0 Only the installation can be
V100R001C03 performed.
Dopra Linux
V200R003C02
1.6 Virus Scan Result

This software package has been scanned by the McAfee antivirus software. No virus is
detected. The detailed scanning result is as follows.
Antivirus McAfee
Software Name
Antivirus ver.8.7.0i
Software
Version
Virus Database 6603

Version
Scanning Date 2012-5-2

HUAWEI BSC6900 GSM
Scanning Result Normal

HUAWEI BSC6900 GSM
V900R014C00SPC500 Release Notes Version CompatibilityVersion Compatibility
2 Version Compatibility
2.1 Compatibility with Earlier Product Versions

The current version of the BSC can provide all features of BSC6900 V900R13C00,BSC6900
V900R12C01, BSC6900 V900R11C00, BSC6000 V900R008C12 and earlier versions.
2.2 Compatibility with Earlier Board Software Versions

The following tables describe the compatibility of the current version with earlier released
board versions.
In the following tables, Y represents compatible, and N represents incompatible.
Table 1.1 Compatibility with earlier board versions

Board Name BSC6000V900R008C12 BSC6000V900R008C01
SCUa Y Y
GCUa Y Y
TNUa Y Y
XPUa Y Y
DPUa Y Y
DPUc Y Y
DPUd Y Y
PEUa Y Y
FG2a Y Y
GOUa Y Y
EIUa Y Y

HUAWEI BSC6900 GSM
Board Name BSC6000V900R008C12 BSC6000V900R008C01
OIUa Y Y
OMUb Y Y
Table 1.2 Compatibility with earlier board versions (BSC6900)

Board Name BSC6900V900R BSC6900V900R BSC6900V900
011 012C01 R013C00
SCUa Y Y Y
SCUb N N Y
GCUa Y Y Y
TNUa Y Y Y
XPUa Y Y Y
DPUa Y Y Y
DPUc Y Y Y
DPUd Y Y Y
DPUf N N Y
DPUg N N Y
PEUa Y Y Y
FG2a Y Y Y
GOUa Y Y Y
EIUa Y Y Y
OIUa Y Y Y
OMUb Y Y Y
GOUc Y Y Y
XPUb Y Y Y
FG2c Y Y Y
POUc Y Y Y
GCGa Y Y Y
POUa Y Y Y
OMUa Y Y Y
OMUc N N Y
DPUe N N N

HUAWEI BSC6900 GSM
Board Name BSC6900V900R BSC6900V900R BSC6900V900

011 012C01 R013C00
NIUa N N N
FG2d N N N
GOUd N N N

HUAWEI BSC6900 GSM
V900R014C00SPC500 Release Notes Important NotesImportant Notes
3 Important Notes
Table 1.3 Notes and cautions for using BSC6900 V900R014C00SPC500

No. Item Description
1 Time No restriction.
2 Area/Site None.
3 Others Limited features can be launched for commercial use only
after they pass Beta tests.
4 End of the version It is determined by version life cycle management.

Changes from V900R014C00SPC300 to
HUAWEI BSC6900 GSM V900R014C00SPC500Changes from
V900R014C00SPC500 Release Notes V900R014C00SPC300 to V900R014C00SPC500
4 Changes from V900R014C00SPC300 to

V900R014C00SPC500
4.1 What's New

4.1.1 Feature Updates
New Features
1. Forcible SSL Application to the Communication Between a BSC6900 and External
Devices

Description This function forcibly applies the Secure Sockets Layer (SSL) protocol to
the communication between a BSC6900 and external devices.
External devices include peripherals that interconnect with the BSC6900,
for example, the Vendor Network Probe (VNP), and devices that remotely
manage the BSC6900, for example, the M2000.
Benefit This function further secures the communication between the BSC6900
and external devices.
Implementation This function is enabled when the CONNTYPE parameter in the SET
CONNTYPE command is set to ONLY_SSL(Only SSL Connection).
Before this function is enabled, a root certificate file, a certificate file, and
a private key file must be added to the BSC6900.
After this function is enabled, the following must be done:
 The BSC6900 must automatically shut down all the non-SSL ports used
for communication with external devices.
 External devices must establish only SSL connections to the BSC6900.
They cannot establish non-SSL connections.
Related Run the following command to enable this function:
Operations SET CONNTYPE: CONNTYPE=ONLY_SSL;
Run the LST SSLCONF command to check whether this function has
been enabled.
Trouble Ticket DTS: 2011121904845
Number
Feature ID None
2. Independent Upgrade of the Rule Library

Description The rule library can be upgraded independently in this release.
Benefit The rule library upgrade is independent of the version upgrade.
Implementatio 1. Run the DSP BRDVER command to obtain the current version number of
n the rule library. Check whether the rule library is of the desired version.
2. If the version of the current rule library is different from the desired
version, upload the desired rule library file to the OMU active
workspace/bam/version_x/bin/fam directory through FTP.
3. Run the LOD BRD command to load the file to the NIUa. Then, run the
RST BRD command to reset the NIUa.
The active OMU does not check the rule library file during the integrity check.
The standby OMU automatically synchronizes the rule library file with the
active OMU.
The CMP BRDVER command no longer checks the rule library file, avoiding
false alarm reporting.
Related 1. To query the version number of the current rule library, run the DSP
Operations BRDVER command. The following is an example:
DSP BRDVER: SRN=0, SN=8;
2. To load the rule library file to the NIUa, run the LOD BRD command. The
following is an example:
LOD BRD: BT=NIUa, LGCAPPTYPE=NIU, SRN=0, SN=8,
LT=RULELIB;
3. To enable the new rule library to take effect on the NIUa, run the RST
BRD command to reset the NIUa. The following is an example:
RST BRD: SRN=0, SN=8;
Trouble Ticket CR GU01245b

Number
Feature ID None
3. Optimizing SIM Card Registration

Description The SIM card registration is optimized for the Fast WCDMA
Reselection at 2G CS Call Release feature. The optimization enables
the BSC to determine whether an MS preferentially reselects a 3G
cell after the call is released based on the value of the information
element (IE) "Service Handover" in the Assignment Request or
Handover Request message.
Before the optimization, the algorithm used by the Fast WCDMA
Reselection at 2G CS Call Release feature does not consider whether
MSs' SIM cards register with the UMTS network. As stated in 3GPP
specifications, MSs whose SIM cards do not register with the UMTS
network search for signals for at least 10s.
Benefit The optimization prevents MSs whose SIM cards do not register with
the UMTS network from failing to access the network.
Implementation The information about neighboring UMTS cells is not contained in
the Channel Release message if the following conditions are met:
The Select 3G Cell After Call Release parameter is set to YES(Yes).
 The BSC CS Reserved Switch Parameter 0 parameter is set to
SW1(SwPara1).
 The IE "Service Handover" is contained in the Assignment Request
or Handover Request message and the value of the IE "Service
Handover" is "Handover to UTRAN or cdma2000 shall not be
performed."
Related 1.Run the SET GCELLCCAD command with the Select 3G Cell
Operations After Call Release parameter set to YES(Yes). The following is an
example:
SET GCELLCCAD: IDTYPE=BYID, CELLID=0,
CELLSELECTAFTERCALLREL=YES;
2.Run the SET GRSVPARA command with the BSC CS Reserved
Switch Parameter 0 parameter set to SW1(SwPara1). The following
is an example:
SET GRSVPARA: BSCCSSWRSV0=SW1-1;
Trouble Ticket GU1484
Number
Feature ID GBFD-114325
4. Enhance user data security

Description To enhance user data security, user-plane data is deleted from traced
messages, and PS service data trace is no longer supported.
Benefit User-plane data is not included in the PTP BVC, PS Um, PS Abis, or
PS single-user tracing messages.
PS service data trace is no longer supported.
User information in the PS CHR is encrypted.
Implementation  PTP BVC tracing
In LLC PDU data blocks, the first two segments of the server IP
address is set to 0XFF and IP addresses of MSs are encrypted. All
GMM signaling messages are traced.
 PS Um tracing
Only RLC/MAC headers are reserved in RLC data blocks. All control
signaling messages are traced.
 PS Abis tracing
Only TRAU headers are reserved in TRAU frames. All information,
synchronization, and handshake frames are traced.
 PS recording
MML commands and messages related to PS service data trace are
deleted.
 PS CHR
In the PS CHR, the first two segments of the server IP address is set
to 0XFF, and IP addresses, IMSIs, and IMEIs of MSs are encrypted.
Related None
Operations
Trouble Ticket DTS2012010402091

Number
Feature ID None
5. Support for Anonymous User Identity

Description The BSC supports anonymous processing for user identity

information in tracing messages and log files, such as international
mobile subscriber identity (IMSI), international mobile equipment
identity (IMEI), mobile station international ISDN number
(MSISDN), and IP address.
Benefit This ensures user data privacy.
Implementation 1. The BSC supports anonymous processing for user identity

information in tracing messages and log files, such as IMSI, IMEI,
MSISDN, and IP address.
2. On the M2000, users can set whether anonymous processing for
user identity information can be performed on the BSC side.
3. The cipher key and the function of anonymizing user identity
information in tracing messages and log files can be specified on the
M2000, but cannot be changed on the BSC side.
4. The function of anonymizing user identity information in tracing
messages and log files is disabled by default. After this function is
enabled, users must enter the anonymous user identity information
when starting a single-user tracing task on the M2000 or LMT.
5. After the function of anonymizing user identity information in
tracing messages and log files is enabled, the CPU usage of the XPU
board may slightly increase if you start paging message tracing over
the A interface.
Related 1. Set the cipher key and enable the function of anonymizing user
Operations identity information in tracing messages and log files by
performing the following operations:
On the M2000, choose Monitor > Signaling Trace >
Anonymous Policy Management.
In the displayed dialog box, select Change Cipher Key, type the
cipher key in Cipher Key and Confirm Cipher Key. Then, click
OK. Select the Anonymous Policy option and click Enable
Anonymous Policy. Then, click OK.
2. Run the LST USERIDANONSWITCH command to check
whether the function of anonymizing user identity information in
tracing messages and log files is enabled.
Number
Feature ID None
6. Setting the Value of SI2Quater Indicator in the SI3 Message to TRUE in the NC1 or NC2
Mode

Description The condition for setting the SI2Quater indicator in the SI3 message is
modified. This modification allows that the value of the SI2Quater
indicator in the SI3 message can be set to TRUE, instructing an MS to
parse the SI2Quater message, when the Network Control Mode
parameter is not set to NC0(NC0).
Benefit Before the modification, if a cell is not configured with inter-RAT
neighboring cells and the Measurement Report Type parameter is not set
to EnhMeasReport(Enhanced Measurement Report), the value of
SI2Quater indicator cannot be set to TRUE. In this situation, the MS does
not parse the SI2Quater message and reports packet measurement reports
at the default interval of 3.84s in NC1 or NC2 mode.
After the modification, the MS reports packet measurement reports at the
interval specified in the 2Quater message in the preceding scenario. If the
interval specified in the 2Quater message is shorter than 3.84s, the values
of the following counters increase:
 A9401: Number of 8-Bit Packet Channel Requests Received on CCCH
 A9403: Number of 8-Bit Single Block Channel Requests Received on
RACH
 A9501: Number of Uplink Assignments
If the interval specified in the 2Quater message is longer than 3.84s, the
values of the preceding counters decrease.
Implementation The value of SI2Quater indicator is set to TRUE if the Support Sent
2QUATER parameter is set to YES(Yes) and the Network Control Mode
parameter is set to NC1(NC1) or NC2(NC2).
Related 1. Run the following command with the Support Sent 2QUATER
Operations parameter set to YES(Yes):
SET OTHSOFTPARA: Send2QuterFlag=YES;
2. Run either of the following commands with the Network Control
Mode parameter set to NC1(NC1) or NC2(NC2):
SET GCELLPSBASE: NCO=NC1;
SET GCELLPSBASE: NCO=NC2;
Number
7. Integrating IBCA with Dynamic PDCH

Description This feature is optimized to ensure that a proper IBCA priority is set and
dynamic PDCH conversion is allowed when the IBCA algorithm is
enabled. Before the optimization, when the dynamic mobile allocation
index offset (MAIO) allocated to the PDCH is inconsistent with that
allocated to the TCH, the CS call occupying the TCH must be handed
over to another TCH, increasing the number of CS handovers. In
addition, the CS call may not be allocated to an optimal TCH due to an
improper IBCA priority.
Benefit The optimization decreases the CS call drop rate and increases the
handover success rate and the value of the high quality indicator (HQI).
However, it also increases the TBF abnormal release rate.
Implementation 1. For the cells that participate in both radio frequency (RF) frequency
hopping (FH) and cyclic FH and are enabled with the IBCA
algorithm:
If the Enhanced IBCA PDCH Dynamic Conversion parameter is
set to ON(On) and the Target CIR for IBCA MAIO Configured
on TRX parameter is set to 255, TCHs in the cells cannot be
converted to dynamic PDCHs. In other situations, TCHs in the cells
can be converted to dynamic PDCHs. In addition, only the MAIOs
allocated to the PDCHs can be used. If the ongoing CS calls using
the allocated MAIOs experience soft blocking, TCH-to-PDCH
conversion cannot be performed until the timer specified by the
IBCA PDCH Dynamic Convert Penalty Timer parameter expires.
2. The Enhanced IBCA PDCH Dynamic Conversion parameter is
set to ON(On) when the BSC evaluates interference on TCHs. In
this situation, the BSC updates the IBCA priority by accumulating
the interference on TCHs, PDCHs, and SDCCHs.
Related  Run the SET GCELLCHMGAD command with the Enhanced
Operations IBCA PDCH Dynamic Conversion parameter set to ON(On). The
SET GCELLCHMGAD: IDTYPE=BYID, CELLID=0,
IBCAPDDYNTRENHANCE=ON;
 Run the SET GCELLCHMGAD command with the IBCA PDCH
Dynamic Convert Penalty Timer parameter set to an appropriate
value. The following is an example:
IBCAPDCHDYNTRANTMR=8;
Number
8. Support for Normalized IP VLAN Configuration

Description When a BTS is configured in multi-mode, configuration policies for

traditional IP virtual local area networks (VLAN) vary depending on
networking topologies and the configuration relationship is complex.
This feature simplifies VLAN configuration solutions and achieves
normalized VLAN policies.
Benefit  The platform is unified and VLAN polices for different products are
consistent.
 Networking and configuration solutions are simplified.
 Co-transmission requirements are met.
Implementatio  The value of VLAN Priority in the ADD BTSVLANMAP command
n has been changed to 0 to 7 and 255. (The original value range is 0 to
7.)
 When VLAN Priority is set to 255, the MML command SET
BTSDSCPMAP is added to uniformly configure the mapping between
differentiated services code points (DSCPs) and VLAN priorities,
achieving normalized VLAN policies.
Related  Run the ADD BTSVLANMAP command with VLAN Priority set to
Operations 255, which indicates that the VLAN priority is invalid.
 When VLAN Priority is set to 255, run the SET BTSDSCPMAP
command to set the mapping between DSCPs and VLAN priorities.
Number
Modified Features
1. Optimized Mechanism for Masking the Cause of ALM-21581 Path Fault

Description The mechanism for masking the cause of ALM-21581 Path Fault has
been optimized.
Benefit Alarm reporting is more accurate.
Implementation If multiple faults cause a path fault, the BSC6900 reports ALM-
21581 Path Fault with the highest-priority cause.
The alarm causes are listed in descending order of priority: bearing
port not configured, bearing board fault, bearing port unavailable,
path unavailability notified by OM, and ping failure.
If ALM-21581 Path Fault with the cause "ping failure" has been
reported before a bearing port not configured fault is detected, the
BSC6900 clears the alarm and reports ALM-21581 Path Fault with
the cause "bearing port not configured".
If ALM-21581 Path Fault with the cause "ping failure" has been
reported before a bearing port unavailable fault is detected, the
BSC6900 clears the alarm.
Related This function does not need to be configured.
Operations

Number
Feature ID None
2. VAMOS

Description This feature supports separate configuration of load thresholds for

VAMOS channel multiplexing during intra-cell handovers and
assignment and separate configuration of quality and signal level
thresholds for VAMOS channel multiplexing and demultiplexing in the
overlaid and underlaid subcells.
Benefit This feature allows differentiated VAMOS channel multiplexing and
demultiplexing parameters for the overlaid and underlaid subcells,
improving configuration flexibility for VAMOS parameters.
Implementatio VAMOS parameter setting optimization
n The Multiplexing Load Thres. Offset in Assignment parameter is
added. When VAMOS channel multiplexing during assignment is
enabled in common cells and underlaid subcells in concentric cells, the
decision procedure for VAMOS channel multiplexing during assignment
is triggered if the cell load or load in the underlaid subcell is higher than
or equal to the sum of Channel Multiplex Load Thres. and
Multiplexing Load Thres. Offset in Assignment. When VAMOS
channel multiplexing during assignment is enabled in overlaid subcells,
the decision procedure for VAMOS channel multiplexing during
assignment is triggered if the load in the overlaid subcell is higher than
or equal to the sum of Load Thres. in Overlaid Subcell and
Multiplexing Load Thres. Offset in Assignment.
 The OL Multiplexing Rx Level Thres. Offset parameter is added. A
new call in the overlaid subcell is selected as the candidate VAMOS
call if both of the following conditions are met:
 The downlink receive level of the new call is higher than or equal to
the sum of DL Rx Lev. Thres. of VAMOS Calls, Rx Lev. Thres.
Offset During Assignment, and OL Multiplexing Rx Level Thres.
Offset.
 The uplink and downlink receive signal quality, AdapTive Cell Border
(ATCB), and P/N criterion meets specified conditions.
An established call in the overlaid subcell is selected as the candidate
VAMOS call if both of the following conditions are met:
 The downlink receive signal level of the established call is higher than
or equal to the sum of DL Rx Lev. Thres. of VAMOS Calls and OL
Multiplexing Rx Level Thres. Offset.
 The uplink and downlink receive signal quality, ATCB, and P/N
criterion meets specified conditions.
The OL Multiplexing Rx Quality Thres. Offset parameter is added. A
new call in the overlaid subcell is selected as the candidate VAMOS call
if the following conditions are met:
 The uplink receive signal quality of the new call is smaller than or
equal to UL Rx Qual. Thres. of Established Calls minus Channel
Multiplex Rx Qual. Thres. Offset in Asgmt. and OL Multiplexing
Rx Quality Thres. Offset.
 Downlink receive signal quality of the new call is smaller than or equal
to DL Rx Qual. Thres. of Established Calls minus
VamosAssUlQualThdOffset and Channel Multiplex Rx Qual.
Thres. Offset in Asgmt.
 The downlink receive level of the new call, ATCB, and P/N criterion
meet specified conditions.

An established call in the overlaid subcell is selected as the candidate

VAMOS call if the following conditions are met:
 The uplink receive signal quality of the established call is smaller than
or equal to UL Rx Qual. Thres. of Established Calls minus OL
Multiplexing Rx Quality Thres. Offset.
 The downlink receive signal quality of the established call is smaller
than or equal to DL Rx Qual. Thres. of Established Calls minus OL
Multiplexing Rx Quality Thres. Offset.
 The downlink receive signal level of the established call, ATCB, and
P/N criterion meet specified conditions.
The OL BQ Demultiplexing Rx Quality Thres. Offset parameter is
added. VAMOS channel demultiplexing due to bad quality is triggered if
the P/N criterion is met and either of the following conditions is met:
 The uplink receive signal quality of the VAMOS call in the overlaid
subcell is higher than or equal to UL RX Bad Qual. Demultiplex
Thres. minus OL BQ Demultiplexing Rx Quality Thres. Offset.
 The downlink receive signal quality of the VAMOS call in the overlaid
subcell is higher than or equal to DL RX Bad Qual. Demultiplex
Thres. minus OL BQ Demultiplexing Rx Quality Thres. Offset.
Related Run the SET GCELLVAMOS command with Multiplexing Load
Operations Thres. Offset in Assignment, OL Multiplexing Rx Level Thres.
Offset, OL Multiplexing Rx Quality Thres. Offset, and OL BQ
Demultiplexing Rx Quality Thres. Offset set to appropriate values.
SET GCELLVAMOS: IDTYPE=BYID, CELLID=0,
VamosSwitch=ON, VamosAssSwitch=ON,
VAMOSASSLOADOFT=100, VAMOSOLRXLEVOFT=128,
VAMOSOLRXQUALOFT=70, VAMOSDEPOLRXQUALOFT=70;
Trouble Ticket CR GU01369
Number
3. Setting Power Control Parameters for Overlaid and Underlaid Subcells Independently

Description Traditionally, power control parameters are set on a concentric cell basis.
Now, power control parameters are set independently for an overlaid
subcell and an underlaid subcell.
Benefit Provides optimal network performance because power control parameters
for the overlaid and underlaid subcells are decoupled to implement
different power control strategies for the overlaid and underlaid subcells.
Increases the high quality indicator (HQI) for the overlaid subcell.
Implementation  In an overlaid subcell, if power control decision III, Interference Based
Channel Allocation (IBCA), Multi-Carrier Power Amplifier (MCPA),
or Voice services over Adaptive Multi-user channels on One Slot
(VAMOS) invokes the power control III parameters, the SET
GCELLPWR3 command is executed with specific offset parameters
set to appropriate values. The offsets are then added to the values of the
power control III parameters.
 In an underlaid subcell or a common cell, the offset parameters do not
take effect.
Related Run the SET GCELLPWR3 command with the following offset
Operations parameters set to appropriate values:
 OL UL Level Threshold Offset
 OL DL Level Threshold Offset
 OL UL Quality Threshold Offset
 OL DL Quality Threshold Offset
 OL UL Level Class Protect Factor Offset
 OL DL Level Class Protect Factor Offset
 OL UL Quality Class Protect Factor Offset
 OL DL Quality Class Protect Factor Offset
Number
4. HUAWEI I Handover

Description Use of BCCH receive level after filtering

For the overlaid subcell of an enhanced concentric cell using Huawei
handover algorithm I, the BCCH receive level after filtering is used
to rank candidate cells for handovers.
Benefit Decreases the number of handover requests when the BCCH receive
level after filtering is used for calls in the overlaid subcell of an
enhanced concentric cell. This is because the BCCH receive level
may fluctuate when calls are in the overlaid subcell of an enhanced
concentric cell. If the BCCH receive level fluctuates greatly, the
number of handover requests increases.
Implementation If the MR Interpolation Optimize parameter is set to YES(Yes), the
BCCH receive level after filtering is used to rank candidate cells for
handovers. If the MR Interpolation Optimize parameter is set to
NO(No), the BCCH receive level reported in real time is used to
rank candidate cells for handovers. If no BCCH receive level is
reported, the compensated TCH receive level for power control is
used to rank candidate cells for handovers.
Related Run the SET GCELLHOBASIC command with Current HO
Operations Control Algorithm set to HOALGORITHM1(Handover algorithm I)
and MR Interpolation Optimize set to YES(Yes). The following is an
example:
SET GCELLHOBASIC: IDTYPE=BYID, CELLID=1,
HOCTRLSWITCH=HOALGORITHM1, MrIntrplOptSwitch=YES;
Number
5. Enhanced Voice Quality During Compatible Handover in A over IP Mode

Description After a compatible handover in A over IP mode, the synchronization
source (SSRC) remains unchanged, and the sequence number (SN)
and timestamp number (TSN) are continuous in the RTP frame sent
over the A interface from the BSC.
Benefit Voice quality improves during compatible handovers.
Implementation After a compatible handover in A over IP mode, the BSC sends an

RTP frame that inherits information about the SSRC, SN, and TSN
from the last RTP frame sent before the handover. Therefore, the
SSRC remains unchanged, and the SN and TSN are continuous in
the RTP frame sent over the A interface from the BSC.
Related None
Operations

Number

6. Enhanced A over IP transmission

Description In A over IP mode, the BSC processes invalid AMR rate carried in an
AMR request message during a voice call.
Benefit The BSC is enhanced to interwork with the MGW of another vendor.
Implementation In A over IP mode, the BSC sends the MGW an AMR request
message where the AMR field is always set to a valid value to the
MGW.
After receiving a request message where the AMR field is 0xF from
the MGW, the BSC sets this CMR field to the maximum rate in the
current active codec set (ACS).
Related To set SwPara0 and SwPara1 of TC Reserve Para1 to ON, run the
Operations following MML command:
SET TCRSVPARA: TCRESERVEPARA1=SW0-1&SW1-1;
Number
7. Enhanced TFO
Description During an intra-BSC handover, the voice quality improves after the
Tandem Free Operation (TFO) feature is enhanced.
Benefit The MOS for voice quality improves after TFO establishment.
In BM/TC combined mode, the value of the A3407: TFO
Establishment Duration counter increases, and the values of the
following counters decrease:
 A3301: Number of Successful TFO Establishments(HR)
 A3302: Number of Successful TFO Establishments (FR)
 A3303: Number of Successful TFO Establishments (EFR)
 A3304: Number of Successful TFO Establishments (FAMR)
 A3305: Number of Successful TFO Establishments (HAMR)
 A3306: Number of Successful TFO Establishments (WBAMR)
Implementation During an intra-BSC handover, the TFO establishment speeds up to
shorten the codec time for calls. This minimizes the impact on voice
calls and improves voice quality.
Related None
Operations

Number

8. TFO Supporting the Codec Type UMTS_AMR_2

Description The TFO feature is enhanced to support the codec type
UMTS_AMR_2.
Benefit The BSC supports TFO establishment for the MS (in another BSC)
that adopts the codec type UMTS_AMR_2 during inter-MSC calls or
2G-3G calls.
Implementation The TFO feature enables the BSC to process Tandem Free Operation
(TFO) messages and frames where the codec type is UMTS_AMR_2.
Related None
Operations

Number
9. Optimization of License Usage Measurement for Certain License Control Items

The policies for handling license control items have been optimized for
Description the following features during an upgrade:
 Extended BCCH
 Fast LTE Reselection at 2G CS Call Release
 Multi Technology Neighbour Cell Based Handover
 Radio Resource Reserved Handover Between GSM/TD-SCDMA
Based on Iur-g
If licenses controlling these features are insufficient, the configuration
on the BSC is limited 60 days after an upgrade. To resolve this
problem, users need to disable these features or apply for licenses that
meet the requirements of the configuration data.
Benefit In the pre-upgrade stage, if the upgrade tool checks that configuration
data exceeds the license capacity, users are prompted whether to
continue with the upgrade, and whether to resolve this problem by
deleting the extra data or applying for a new license within 60 days
after the upgrade so that the configuration on the BSC will not be
limited.
Implementation For users who have not used the following features, the corresponding
license control items are added. For users who have used the following
features, the corresponding license control items remain unchanged.
 Extended BCCH
 Fast LTE Reselection at 2G CS Call Release
 Multi Technology Neighbour Cell Based Handover
 Radio Resource Reserved Handover Between GSM/TD-SCDMA
Based on Iur-g
For users who have used the preceding features, the upgrade tool
determines whether the licenses for the new version are sufficient
based on the current configuration data during an upgrade. If the
configuration data exceeds the license capacity, users are prompted to
delete the extra data within 60 days after the upgrade or to apply for a
new license that meets the requirements of the configuration data and
activate the license. Otherwise, the alarm ALM-20743 Insufficient
License Resources is reported every day within the period, and the
configuration on the BSC will be limited after 60 days.
Related  Run the CHK DATA2LIC command to check whether configuration
Operations data of any license control item exceeds the license capacity. The
CHK DATA2LIC: FN="license_file.dat";
 Run the DSP LICUSAGE command to query the current usage of
each license control item. The following is an example:
DSP LICUSAGE: TYPE=Current;
Number
Feature ID None
10. Optimizing the ADD GSMSCB Command Output

Description ADD GSMSCB is an operation and maintenance (OM) command for

simplified cell broadcast. Its command output displays a successful
execution even when the command execution has failed. This misleads
users over the maintenance of simplified cell broadcast. To resolve this
problem, this feature optimizes the ADD GSMSCB command output.
Specifically, this feature displays a list of cells with command execution
failures and the cause values for the command execution failures if the
command execution has failed.
Benefit This feature helps users quickly and accurately identify faults about
simplified cell broadcast.
Implementation  If the ADD GSMSCB command is executed successfully for all cells,
a successful command output is returned with ulfailCellNum
displayed as 0. When this occurs, the OMU does not parse the received
list of cells with command execution failures.
 If the ADD GSMSCB command fails to be executed because its
parameters are set to incorrect values or the number of cells exceeds
the maximum number allowed, a specific cause value for the execution
failure is returned with ulfailCellNum displayed as 0. When this
occurs, the OMU does not parse the received list of cells with
command execution failures.
 In other cases, if the ADD GSMSCB command fails to be executed,
one of the following cause values is returned:
 SCB_CELL_ADD_MSG_FAIL: indicates that the command fails to be
executed for all cells.
 SCB_CELL_ADD_MSG_SOME_CELL_FAIL: indicates that the
command fails to be executed for some cells.
 SCB_CELL_ID_ERROR: indicates that the cell index in use is
incorrect.
In addition, a list of cells with command execution failures is displayed
with ulfailCellNum displayed as the actual number of cells with
command execution failures. When this occurs, the OMU does not parse
the received list of cells with command execution failures.
Related  To add simplified cell broadcast messages to cells with specified cell
Operations names or indexes, do as follows:
Run the ADD GSMSCB command with cell names or indexes set to
appropriate values. If some cells fail to process the messages, a list of
the cells is returned.
 To add simplified cell broadcast messages to cells without specifying
cell names or indexes, do as follows:
Run the ADD GSMSCB command. After all cells under the BSC are
traversed, the messages are added to activated cells that support
simplified cell broadcast and are configured with cell broadcast
channels (CBCHs). The actual execution result (a successful execution
or a list of cells with command execution failures) is returned.
 To add simplified cell broadcast messages with the same sequence
number to cells, do as follows:
Run the ADD GSMSCB command with some message sequence
numbers set to the same value. The following message is returned: All
cells fail in processing cell broadcast messages.

 To add more than 63 simplified cell broadcast messages to cells, do as

follows:
Run the ADD GSMSCB command with the number of cells exceeding
63. A list of cells with command execution failures is returned.
Number
11. Optimizing DTM Combined Update

Description This feature enables users to optimize dual transfer mode (DTM)
combined update. The optimization shortens the duration of GPRS
service interruption during a location area update (LAU).
Benefit This feature optimizes the combined LAU/routing area update (RAU)
procedure in DTM, improving user experience.
Implementation The DTM Combined Update Optimize Type parameter has been added
to specify whether to optimize DTM combined update.
If this parameter is set to RAU_ACC_SEND_DELAY, the BSC sends
the Routing Area Updating Accept message to an MS in the packet
immediate assignment procedure after an SDCCH is released.
If this parameter is set to SDCCH_REL_DELAY, the BSC sends the
downlink GPRS Information message instead of the Routing Area
Updating Accept message to an MS. If the BSC receives a DTM Request
message on an SDCCH, the BSC delays releasing the SDCCH.
If this parameter is set to NO_DELAY, the BSC does not optimize DTM
combined update.
Related Run the SET OTHSOFTPARA command with DTM Combined
Operations Update Optimize Type set to an appropriate value.

Number
12. MOCN SHA Configuration Optimization

Description This feature is optimized so that an MS can hand over to a specified

neighboring cell only if the public land mobile network (PLMN) of the
specified neighboring cell is consistent with that in the mapping
between handover sharing areas and location areas. Before the
optimization, an MS can hand over to a specified neighboring cell only
if the PLMN and location area code (LAC) of the specified
neighboring cell are consistent with those in the mapping between
handover sharing areas and location areas.
Benefit The optimization simplifies configuration and effectively enhances
configuration and maintenance of handover sharing areas.
Implementation The Ignore LAC parameter is added to the ADD SHALAMAP and
MOD SHALAMAP commands. If this parameter is set to ON(On),
the neighboring cell whose PLMN is consistent with that in the
mapping between handover sharing areas and location areas can be
considered as the target cell for handovers. If this parameter is set to
OFF(Off), the neighboring cell whose PLMN and LAC are consistent
with those in the mapping between handover sharing areas and location
areas can be considered as the target cell for handovers.
Related 1.Run the ADD SHALAMAP command to add the mapping between
Operations handover areas and location areas. The following is an example:
ADD SHALAMAP: ShaIndex=0, SHAC=1, MCC="450",
MNC="30", LAC=3030, IgnorLac=ON;
2.Run the MOD SHALAMAP command to modify the mapping
between handover areas and location areas. The following is an
example:
MOD SHALAMAP: ShaIndex=0, IgnorLac=ON;
3.Run the LST SHALAMAP command to query the mapping between
handover areas and location areas.
Number
13. Strategy for Selecting Speech Versions Based on the Speech Version Priorities Carried in
the Message from the MSC

Description This feature provides a new strategy for selecting speech versions.
With this strategy, the BSC can select a speech version according to
the speech version priorities carried in the ASSIGNMENT
REQUEST or HANDOVER REQUEST message from the MSC. In A
over TDM mode, the BSC selects a speech version according to the
following speech version priorities in descending order: FR AMR-
WB, FR AMR, EFR, FR, HR AMR, and HR. If the speech version
priorities carried in a message from an MGW are inconsistent with
the preceding priorities, establishing TFO between a Huawei BSC
and the MGW fails.
Benefit  This feature increases the success rate of TFO establishments
between a Huawei BSC and an MGW.
 If the A over TDM Speech Version Select Strategy parameter is
set to MSC(MSC Strategy), the proportion of traffic volume for a
speech version is positively related to its priority carried in the
request message from the MSC.
Implementation The A over TDM Speech Version Select Strategy parameter is
added. If this parameter is set to BSC(BSC Strategy), the BSC
selects a speech version according to the following speech version
priorities in descending order: FR AMR-WB, FR AMR, EFR, FR,
HR AMR, and HR. If this parameter is set to MSC(MSC Strategy),
the BSC selects a speech version according to the speech version
priorities carried in the ASSIGNMENT REQUEST or HANDOVER
REQUEST message from the MSC. This parameter is set to
BSC(BSC Strategy) by default.
In A over TDM mode, the BSC selects a speech version according to
the value of this parameter in any of the following scenarios:
 Channel assignment
 Intra-BSC handovers
 Incoming BSC handovers
Related  Run the SET AITFOTHPARA command with the A over TDM
Operations Speech Version Select Strategy parameter set to MSC(MSC
Strategy).
The following is an example:
SET AITFOTHPARA: CNNODEIDX=0,
SpVerTdmStrategy=BSC;
 Run the SET GCELLBASICPARA command with the TFO
Switch parameter set to ENABLE(Enable).
SET GCELLBASICPARA: IDTYPE=BYID, CELLID=0,
NBAMRTFOSWITCH=ENABLE;
Trouble Ticket N/A
Number
14. Support for configuring an RRU3942 on the BSC

Description An RRU3942, a new type of multi-carrier remote radio unit (MRRU),

can be configured on the BSC.
Benefit The BSC supports the configuration of an RRU3942.
Implementation A parameter value for the RRU3942 is added to all corresponding

MML commands.
Related The value RRU3942 is added to the RXU Specification parameter in
Operations the ADD BTSRXUBRD and MOD BTSRXUBRD commands.

Number
Feature ID None
15. Support for configurations of an RRU3926 on a BSC

Description The BSC supports the configuration of RRU3926 on BTSs.
Benefit BSCs support configurations of RRU3926s.
Implementation The information about RRU3926s is added to the ADD

BTSRXUBRD and MOD BTSRXUBRD commands.
Related The value RRU3926 is added to the RXU Specification parameter
Operations in the ADD BTSRXUBRD and MOD BTSRXUBRD commands.

Number
Feature ID None
16. Transparent timeslots can be configured in Abis IP over E1 mode.

Description Transparent timeslots can be configured in Abis IP over E1 mode.
Benefit BTSs from different vendors cannot be cascaded in Abis IP over E1

mode.
Implementation In Abis IP over E1 mode, transparent timeslots can be configured
for lower-level cascaded BTSs by using the ADD BTSTRANSTS
command. After this configuration, BTSs from different vendors
can be cascaded.
Related Run the following commands to configure transparent timeslots in
Operations Abis IP over E1 mode:
ADD BTSTRANSTS/MOD BTSTRANSTS/RMV
BTSTRANSTS
Number
Feature ID None

17. Support for BTS bypass in IP over E1 mode

Description The BTS bypass function is supported in IP over E1 mode.
Benefit When an upper-level BTS is powered off, its lower-level BTSs that are
cascaded in the same link can still work properly.
Implementation The BTS bypass function can be used in IP over E1 transmission mode.
The restriction on local IP addresses is removed. Specifically, when
local IP addresses of PPP links or ML PPP link groups on cascaded
BTSs are all 0s, these IP addresses can be configured in the same
network segment.
The restrictions on scenarios where this feature is used are as follows:
 Currently, only 3900 series base stations support this feature.
 Only a BTS logical IP address can be used as a service IP address.
 When an upper-level BTS is powered off, services processed by its
lower-level BTSs are not interrupted. When an upper-level BTS is
powered on, its lower-level BTSs restart.
 The BTS bypass function is ineffective when transmission is
interrupted or the BTS resets.
 The BTS bypass function is not supported when two or more E1 are
used.
 The BTS bypass function is effective only when at least one PPP link
or ML PPP link is configured on port 0.
Related Run the following MML commands:
Operations  ADD BTS/MOD BTS
 ADD BTSPPPLNK/MOD BTSPPPLNK
 ADD BTSMPGRP/MOD BTSMPGRP
Number
18. Support for configurations of an RRU3922E on the BSC

Description The BSC supports the configuration of an RRU3922E on BTSs.
Benefit The BSC can work with BTSs configured with RRU3922Es (a new
MRRU type).
Implementation The RRU3922E-related information is added to the ADD
BTSRXUBRD and MOD BTSRXUBRD commands.
In addition, the value RRU3922E is provided to the RXU
Specification parameter.
Related Operations Run the following MML commands:
 ADD BTSRXUBRD
 MOD BTSRXUBRD
Number
Feature ID None
19. Adding the Reserved Parameter Disuse Statement

Description In BSC6900 V900R014, the reserved parameter disuse statement is
added to inform users that reserved parameters are used in patch
versions and will be replaced with new parameters in later R versions.
Benefit The disuse statement prevents users from using the reserved
parameters on the configuration interface.
Implementatio  The disuse statement of a reserved parameter is added to the
n parameter meaning.
Disuse statement: This parameter is used temporarily in patch versions
and will be replaced with a new parameter in later versions. The new
parameter ID reflects the parameter function. Therefore, this parameter
is not recommended for the configuration interface.
 The Disuse Reserved Parameter worksheet is added to the
BSC6900 GSM V900R014C00SP**** Used Reserved Parameter
List.xls file. In this worksheet, the reserved parameters that are
disused in BSC6900 V900R014 or later are listed.
Related None
Operations

Number
Feature ID None
Deleted Features
None.

4.1.2 Hardware Updates

New Hardware
None.
Modified Hardware
None.
Removed Hardware
None.
4.1.3 Command Line Updates

See Appendix 1 of the release notes.
4.1.4 Parameter Updates

4.1.5 Alarm Updates

4.1.6 Event Updates

4.1.7 Counter Updates

4.1.8 License Updates

4.2 Resolved Issues

1. The EIUa or OIUa board resets abnormally

Trouble Ticket iCare: 690385/793298

Number DTS2011070605293
Description The EIUa or OIUa board that serves as an Abis interface board may reset
when you perform any of the following operations:
 Adding a BTS
 Removing a BTS
 Activating a cell
 Deactivating a cell
Severity Minor
Root Cause The BTS internal protection mechanism is defective.
Solution The internal protection mechanism defect has been rectified.
Solution Impact None
Test Case ID CASE_Commercial_PR_Regression_V9R14C00SPC500_001
2. Failed Communication Between the OMU Board and BSC6900 Boards After a Non-
Physical-Layer Fault Occurs on the Link Connecting the OMU Board and the SCU Board

Number
Description Either of the following problems occurs:

 ALM-20223 Communication Between GE Switching Board and OMU
Faulty is reported.
 The panel on the LMT shows that all BSC6900 boards are faulty or not
detected.
Severity Minor
Root Cause The hardware of the Operation and Maintenance Unit (OMU) or GE
Switching network and Control Unit (SCU) board is faulty, causing a
non-physical-layer fault on one of the links between the OMU board and
SCU board.
Solution A function has been added to detect faults on the links between the OMU
board and SCU board. After such a fault is detected, ALM-20223
Communication Between GE Switching Board and OMU Faulty is still
reported. However, the BSC6900 will automatically block the faulty link
so that the SCU board can communicate with the OMU board by using a
functional link.
3. The flow control level is incorrect over the A interface.


Number
Description The BSC increases the flow control level over the A interface when the
flow control level should be decreased.
Severity Minor
Root Cause When the BSC converts unsigned long data to unsigned char data,
precision loss occurs if the unsigned long data exceeds 256.
Solution The BSC now checks whether the unsigned long data to be converted
exceeds 256. If the data exceeds 256, the BSC provides protection for
the data. This prevents precision loss.
4. The BSC does not record the information about discarded paging messages
Number
Description The BSC discards excessive paging messages and records related logs,
but does not provide counters indicating information about discarded
paging messages.
Severity Minor
Root Cause The maximum number of paging messages allowed by the BSC exceeds
the maximum number of buffered IMSIs defined by the BSC.
Solution The maximum number of buffered IMSIs has been increased. If the BSC
discards excessive paging messages, it now records system faults in
logs.
5. The statistical value of the AR3555A: Rate of TCHs in Busy State counter is greater than
the actual value.


Number
Description The statistical value of the AR3555A: Rate of TCHs in Busy State
counter is greater than the actual value.
Severity Minor
Root Cause The AR3555A: Rate of TCHs in Busy State counter provides the rate of
occupied TCHs to available TCHs in a cell in a measurement period.
The statistical value of available TCHs is smaller than the actual value,
and therefore the statistical value of the AR3555A: Rate of TCHs in
Busy State counter is greater than the actual value.
Solution The BSC now correctly measures the number of available TCHs in a
cell.
Solution Impact After the solution is used, the values of the following counters decrease:
 AR3555A: Rate of TCHs in Busy State
 AR3555B: Rate of TCHs on BCCH TRX in Busy State
 AR3555C: Rate of TCHs on Non-BCCH TRX in Busy State
6. The BSC configured with an external PCU does not measure the CR3001-Number of
Initially Configured Channels (Static PDCH) counter.

Trouble Ticket iCare: none

Number DTS2012032104445
Description The BSC configured with an external PCU does not measure the
CR3001-Number of Initially Configured Channels (Static PDCH)
counter.
Severity Minor
Root Cause Measurement of the CR3001-Number of Initially Configured Channels

(Static PDCH) counter does not take into account configuration of an
external PCU.
Solution The BSC configured with an external PCU now measures the CR3001-
Number of Initially Configured Channels (Static PDCH) counter.
Solution Impact After this solution is used for the BSC configured with an external PCU,
the values of the following counters increase:
 R3001A-Number of Initially Configured Channels (Static PDCH)
(900/850/810 band)
 R3001B-Number of Initially Configured Channels (Static PDCH)
(1800/1900 Band)
After this solution is used for the BSC configured with a built-in PCU,
the values of the following counters decrease:
 R3032-Number of Initially Configured Channels (Static PDCH)
(Overlay Cell)
 AR3029-Mean Number of Dynamically Configured Channels (PDCH)
(OLCELL)
 AR3034-Mean Number of Available Channels (PDCH) (Overlay Cell)
 R3005A-Number of Initially Configured Channels (Static PDTCH
Support EDGE) (900/850/810 band)
 R3005B-Number of Initially Configured Channels (Static PDTCH
Support EDGE) (1800/1900 Band)
 AR3025A-Mean Number of Available Channels (Support EDGE)
(900/850/810 band)
 AR3025B-Mean Number of Available Channels (Support EDGE)
(1800/1900 Band)
 AR3030-Mean Number of Dynamically Configured Channels
(Support EDGE) (OLCELL)
 AR3035-Mean Number of Available Channels (Support EDGE)
(Overlay Cell)
7. The value of the TK3104: Traffic Volume on TCH Carrying Traffic in One Location
Group counter is doubled after the MR.Preprocessing parameter is set to
BSC_Preprocessing(BSC preprocessing).


Number
Description After the MR.Preprocessing parameter is set to BSC_Preprocessing(BSC

preprocessing), the value of the TK3104: Traffic Volume on TCH
Carrying Traffic in One Location Group counter is doubled.
Severity Major
Root Cause When the Sent Freq.of preprocessed MR parameter is set to

Once_ps(Once every second) and an MS reports two original
measurement reports (MRs) to the BTS:
If the MR.Preprocessing parameter is set to BTS_Preprocessing(BTS
preprocessing), the BTS reports one MR to the BSC.
If the value of the MR.Preprocessing parameter changes to
BSC_Preprocessing(BSC preprocessing), the BTS reports two MRs to
the BSC.
As a result, the number of MRs is doubled.
Solution The BSC now measures the number of MRs based on the number of
original MRs. Specifically, if the Sent Freq.of preprocessed MR parameter
is set to Once_ps(Once every second), the number of MRs is incremented
by two each time the BTS reports an MR. In this way, the BSC measures
the TK3104:Traffic Volume on TCH Carrying Traffic in One Location
Group counter based on the number of original MRs instead of the setting
of the Sent Freq.of preprocessed MR parameter.
Solution Impact After this solution is used:
 The values of the following counters is doubled if the MR.Preprocessing
parameter is set to BTS_Preprocessing(BTS preprocessing) and the Sent
Freq.of preprocessed MR parameter is set to Once_ps(Once every
second) before this solution is used:
 TK3104:Traffic Volume on TCH Carrying Traffic in One Location
Group
 TK3004:Traffic Volume on SDCCH in One Location Group
 TK3204:Traffic Volume on TCH Carrying Signalling in One Location
Group
 The values of the preceding counters are quadrupled if the
MR.Preprocessing parameter is set to BTS_Preprocessing(BTS
preprocessing) and the Sent Freq.of preprocessed MR parameter is set to
Once_2s(Once every two second) before this solution is used.
However, if the setting of the Sent Freq.of preprocessed MR parameter is
changed after this solution is used, the values of the preceding counters
remain unchanged.
8. One-way audio may occur when AMRC is enabled.


Number
Description When Adaptive Multi Rate Control (AMRC) is enabled, one-way audio
may occur.
Severity Suggestion
Root Cause When AMRC is enabled, the BSC sends different AMR sets to the BTS
and the TC subrack.
Solution AMRC triggered by congestion on the Abis interface is ineffective in
Flex Abis or AMR local switching scenarios. In other scenarios, the BSC
sends the same AMR set to the BTS and TC subrack when AMRC is
triggered
9. Counters related to outgoing inter-cell handovers in the GCELL-GCELL measurement

object are incorrectly measured.


Number
Description 1.The BSC measures inter-cell handovers caused by directed retry in

both the Outgoing Inter-Cell Handover Requests (Directed Retry) and
Outgoing Inter-Cell Handover Requests (Other Causes) counters.
However, the BSC measures these handovers only once in the
Outgoing Inter-Cell Handover Requests counter. As a result, the sum of
all counters in Outgoing Inter-Cell Handover Requests (Handover
Causes) is greater than the value of the Outgoing Inter-Cell Handover
Requests counter, but the sum should be equal to the value.
2.The formula used for calculating the value of the Failed Outgoing
Inter-Cell Handovers counter does not include the Failed Outgoing
Inter-Cell Handovers (Directed Retry) counter. The BSC measures
inter-cell handover failures caused by directed retry in both the Failed
Outgoing Inter-Cell Handovers (Directed Retry) and Failed Outgoing
Inter-Cell Handovers (Other Causes) counters.
3.The formula used for calculating the value of the Outgoing Inter-Cell
Handover Commands counter does not include the Outgoing Inter-Cell
Handover Commands (Directed Retry) counter. The BSC measures
inter-cell handovers caused by directed retry in the Outgoing Inter-Cell
Handover Commands (Other Causes) counter.
Severity Suggestion
Root Cause The formulas used for calculating the values of the Failed Outgoing
Inter-Cell Handovers and Outgoing Inter-Cell Handover Commands
counters do not include directed retry-related counters.
Solution 1.The BSC measures inter-cell handovers caused by directed retry only
in the Outgoing Inter-Cell Handover Requests (Directed Retry) counter.
2.The formula used for calculating the value of the Failed Outgoing
Inter-Cell Handovers counter includes the Failed Outgoing Inter-Cell
Handovers (Directed Retry) counter. The BSC measures inter-cell
handovers caused by directed retry only in the Failed Outgoing Inter-
Cell Handovers (Directed Retry) counter.
3.The Outgoing Inter-Cell Handover Commands (Directed Retry)
counter is added. The formula used for calculating the value of the
Outgoing Inter-Cell Handover Commands counter includes the
Outgoing Inter-Cell Handover Commands (Directed Retry) counter.
The BSC measures inter-cell handovers caused by directed retry only
in the Outgoing Inter-Cell Handover Commands (Directed Retry)
counter.
Solution Impact After this solution is used, values of the following counters decrease:
 Outgoing Inter-Cell Handover Requests (Other Causes)
 Outgoing Inter-Cell Handover Commands (Other Causes)
 Successful Outgoing Inter-Cell Handovers (Other Causes)
 Outgoing Inter-Cell Handover Commands (Other Causes)
Compared with BSC6900 V900R13C00SPC500, BSC6900
V900R14C00SPC500 adds the Outgoing Inter-Cell Handover
Commands (Directed Retry) counter to measure inter-cell handovers
caused by directed retry.

10. The measured values of some counters related to inter-concentric cell handovers are
incorrect.


Number
Description The number of inter-concentric cell handover commands is greater than

the number of inter-concentric cell handover requests.
Severity Major
Root Cause When the BSC measures the number of inter-concentric cell handover
requests, it measures the number of incoming underlaid or overlaid
subcell handover requests based on the setting of the Pref. Subcell in
HO of Intra-BSC parameter. However, the allocated channel may be
different from the channel that should be preferentially selected. As a
result, the measured number of inter-concentric cell handover requests is
incorrect.
Solution The BSC now measures the number of incoming underlaid or overlaid
subcell handover requests based on the allocated channel.
Solution Impact After this solution is used, the values of the following counters may
fluctuate:
 Number of Outgoing Internal Inter-Cell Handover Requests
(Underlaid Subcell to Underlaid Subcell)
 Number of Incoming Internal Inter-Cell Handover Requests
(Underlaid Subcell to Overlaid Subcell)
 Number of Outgoing Internal Inter-Cell Handover Requests (Overlaid
Subcell to Overlaid Subcell)
 Number of Incoming Internal Inter-Cell Handover Requests (Overlaid
Subcell to Underlaid Subcell)
If the Pref. Subcell in HO of Intra-BSC parameter is set to OSubcell:
 The values of the following counters decrease:
 The value of the following parameters increase:


If the Pref. Subcell in HO of Intra-BSC parameter is set to USubcell,
it is the other way round.
11. Background service-related counters are incorrectly measured after the PFC function is
enabled.
Number
Description If an MS has subscribed to the background service, after the PFC function
is enabled, the BSC does not measure the traffic and data transmission
duration for this MS.
Severity Minor
Root Cause The measurement points are not specified.
Solution The measurement points for background service-related counters have

been added.
Solution Impact The values of the following counters increase:
 Total Bytes of Downlink GPRS Background Service LLC PDUs Sent
 Total Bytes of Downlink EGPRS Background Service LLC PDUs Sent
 Total Bytes of Uplink GPRS Background Service LLC PDUs Sent
 Total Bytes of Uplink EGPRS Background Service LLC PDUs Sent
 Number of Transmissions of Downlink GPRS Background Service
 Number of Transmissions of Downlink EGPRS Background Service
 Number of Transmissions of Uplink GPRS Background Service
 Number of Transmissions of Uplink EGPRS Background Service
 Total Transmission Duration of Downlink GPRS Background Service
 Total Transmission Duration of Downlink EGPRS Background Service
 Total Transmission Duration of Uplink GPRS Background Service
 Total Transmission Duration of Uplink EGPRS Background Service
12. An MS fails to hang up properly


Number
Description The BSC sends a Handover Command message to an MS after receiving a

Disconnect message. As a result, the MS fails to hang up properly.
Severity Suggestion
Root Cause The BSC triggers a handover before receiving a Disconnect message and
sends a Handover Command message to the MS after receiving the
Disconnect message. Then, the MS attempts to occupy a new channel, and
therefore fails to receive the Channel Release message from the BSC.
Solution The BSC now determines whether it has received a Disconnect, Release, or
Release Complete message before sending a Handover Command message
to an MS. If the BSC has received the message, it does not send the
Handover Command message to the MS and releases the resources for the
call.
This solution is controlled by bit 16 of BSC-level Reserved parameter 20.
If the bit 16 is set to the default value 1, this solution is not used. If the bit
16 is set to 0, this solution is used.
Solution After this solution is used, the values of the following counters increase if
Impact an MS hangs up after a handover is triggered:
 Number of Outgoing Internal Inter-Cell Handover Commands
 Incoming Internal Inter-Cell Handover Clear Cmd Times (Before
Handover Response)
 Internal Intra-Cell Handover Commands
 Outgoing External Inter-Cell Handover Commands
 Outgoing External Inter-Cell Handover Clear Cmd Times (Before
Handover Response)
 Intra-BSC Handover Success Rate
 Intra-BSC Radio Handover Success Rate
 Success Rate of Outgoing External Inter-Cell Handovers
 Success Rate of External Outgoing Cell Radio Handovers
13. Ping-pong handovers occur


Number
Description An MS performs a quick handover from cell A to cell B and then back to
cell A immediately, causing ping-pong handovers.
Severity Minor
Root Cause The BSC does not perform penalty on the α filtering algorithm in the
source cell after a quick handover. In addition, the Quick Handover
Offset parameter is set to 0.
Solution The BSC now performs penalty on the α filtering algorithm in the source
cell after a quick handover.
Solution Impact After this solution is used in high-speed railway scenarios:
 Ping-pong handovers can be prevented when a quick handover is
triggered.
 The values of the following counters remain unchanged or decrease
slightly:
 H374L: Outgoing Inter-Cell Handover Requests (Other Causes)
 H372L: Failed Outgoing Inter-Cell Handovers (Other Causes)
 CM33: Call Drops on Traffic Channel
14. Units of some counters are missing on the NMS.

Number
Description Units of some counters are missing or displayed "none" on the NMS,
making it difficult to understand the counter values.
The missing units may be "%" or "s".
Severity Warning
Root Cause English units are automatically converted from input Chinese units by a
tool.
Errors occur during unit conversion due to incorrectly input Chinese units
of some counters, and the units of these counters are automatically
converted to "none".
Solution Incorrect Chinese units have been corrected to ensure normal unit
conversion.
Solution Impact Changes have been made to display counter units correctly on the M2000
and PRS, facilitating the understanding these counters.
For example, a counter value has changed from 7.84 to 7.84% on the
M2000.

15. The session ID of a user that has logged in to the web LMT may be stolen.


Number
Description The web LMT manages the status and data of login users through the
session mechanism. After a user logs in to the web LMT, the web
browser sends a Hypertext Transfer Protocol (HTTP) request to the LMT
server. The uniform resource locator (URL) in the request includes the
user session ID. If the _sid parameter is intercepted, an attacker can
forge a similar URL on another PC and send the URL to the server to
perform unauthorized operations.
Severity Minor
Root Cause There is a security loophole in the web LMT system.
Solution The security loophole of the web LMT system has been closed.
The web LMT now does not consider the user session ID as a common
HTTP request parameter any longer. Instead, it stores the user session ID
in the cookies of the web browser. The cookies are automatically sent to
the web LMT server with the HTTP request and become invalid after a
user closes the web browser. The web LMT server checks whether the
request is valid by verifying the user session ID contained in the HTTP
request cookies.
In this way, the cookies and the client web browser are bound.
Therefore, attackers cannot intercept user session IDs to perform
unauthorized operations.
Solution Impact User session IDs are saved in the cookies of the web browser to ensure
security. However, this brings about the following impacts:
1. The web LMT requires that the web browser allow cookies. If the
cookies are blocked, users will fail to log in to the web LMT.
2. Cookie mechanisms vary according to web browser versions. When
Internet Explorer 8/Internet Explorer 9 or Firefox is used, the pages
opened by one user share the same session ID, and therefore one
user can open only one web LMT for the same NE. If the user
opens another web LMT, the following error information is
displayed:
If the preceding error information is displayed, Internet Explorer

8/Internet Explorer 9 users can choose File > New Session from the
menu bar to open a new page and then log in to the web LMT. The new
page does not share the same session ID with the old pages, and

therefore multiple web LMTs can be opened for one NE.

Another cause for the preceding error is that the user session ID saved in
the cookies remains valid after a user logs out of the LMT unexpectedly.
In this case, Internet Explorer 6/Internet Explorer 7 users need to close
the web LMT page; Internet Explorer 8/Internet Explorer 9 and Firefox
users need to close all opened pages to invalidate the old user session
ID, restart the web browser, and log in to the web LMT again.
16. Some PS counters deteriorate when the Start Flex MAIO Switch parameter is set to
ON(On).


Number
Description Before the GBSS is upgraded to a version earlier than 14.0, the Start
Flex MAIO Switch parameter is set to ON(On) and dynamic channel
conversion messages are sent and received over operation and
maintenance links (OMLs). After the upgrade, dynamic channel
conversion messages are sent and received over radio signaling links
(RSLs). As a result, the uplink and downlink TBF establishment success
rates decrease and the downlink call drop rate increases on the entire
network. The involved counters are as follows:
 A9004: Number of Failed Uplink GPRS TBF Establishments due to
MS No Response
 A9104: Number of Failed Downlink GPRS TBF Establishments due to
MS No Response
 A9204: Number of Failed Uplink EGPRS TBF Establishments due to
MS No Response
 A9304: Number of Failed Downlink EGPRS TBF Establishments due
to MS No Response
 A9006: Number of Uplink GPRS TBF Abnormal Releases due to
N3101 Overflow (MS No Response)
 A9106: Number of Downlink GPRS TBF Abnormal Releases due to
N3105 Overflow
 A9206: Number of Uplink EGPRS TBF Abnormal Releases due to
N3101 Overflow (MS No Response)
 A9306: Number of Downlink EGPRS TBF Abnormal Releases due to
N3105 Overflow
Severity Major
Root Cause The BSC does not send mobile allocation index offsets (MAIOs) to the
BTS during dynamic TCH-to-PDCH conversions. As a result, the
MAIOs saved on the BSC are inconsistent with those saved on the BTS.
Solution If dynamic channel conversion messages are sent and received over
RSLs, the BSC now sends dynamic frequency hopping information
(including MAIOs) to the BTS during dynamic TCH-to-PDCH
conversions.
Solution Impact After this solution is used, the preceding PS counters return to normal.
17. Some counters cannot be used in BSC6900 V900R014.


Number
Description In BSC6900V900R014, the following counters cannot be used:

H3006A:CELL.INTRACEL.HO.REQ.TIMES.WBAMR.WB.NWB
H3006B:CELL.INTRACEL.HO.REQ.TIMES.WBAMR.NWB.WB
H3016A:CELL.INTRACELL.HO.CMD.TIMES.WBAMR.WB.NWB
H3016B:CELL.INTRACELL.HO.CMD.TIMES.WBAMR.NWB.WB
H3026A:CELL.INTRACELL.HO.FAIL.TIMES.WBAMR.WB.NWB
H3026B:CELL.INTRACELL.HO.FAIL.TIMES.WBAMR.NWB.WB
TH3036A:CELL.INTRACELL.HO.SUCC.RATE.WBAMR.WB.TO.NW
B
TH3036B:CELL.INTRACELL.HO.SUCC.RATE.WBAMR.NWB.TO.W
B
In the preceding counters:
The H3006A and H3006B counters measure the number of handover
requests during internal intra-cell handovers due to TFO speech version
incompatibility.
The H3016A and H3016B counters measure the number of handover
commands during internal intra-cell handovers due to TFO speech
version incompatibility.
The H3026A and H3026B counters measure the number of failed internal
intra-cell handovers due to TFO speech version incompatibility.
The TH3036A and TH3036B counters measure the success rate of
internal intra-cell handovers due to TFO speech version incompatibility.
Severity Major
Root Cause The preceding counters cannot completely reflect statistics during
handovers due to TFO speech version incompatibility because these
handovers involve both internal intra-cell handovers and internal inter-
cell handovers, and also involve both WB AMR-NB AMR handovers and
handovers between other speech versions.
Solution The preceding counters are not used now. Instead, the following counters
are added:
A3408:CELL.TRAU.TFO.HO.REQ.TIMES.INCOMP
A3409:CELL.TRAU.TFO.HO.CMD.TIMES.INCOMP
A3410:CELL.TRAU.TFO.HO.FAIL.TIMES.INCOMP
RA3408:CELL.TRAU.TFO.HO.SUCC.RATE.INCOMP
The A3408 counter measures the number of handover requests during
internal intra- and inter-cell handovers due to TFO speech version
incompatibility.
The A3409 counter measures the number of handover commands during
internal intra- and inter-cell handovers due to TFO speech version
incompatibility.
The A3410 counter measures the number of failed internal intra- and
inter-cell handovers due to TFO speech version incompatibility.
The RA3408 counter measures the success rate of internal intra- and

inter-cell handovers due to TFO speech version incompatibility.

Solution Impact After this solution is used, the original eight counters become ineffective.
18. The BSC does not measure discarded CS pagings when paging message packaging is
enabled and the LAPD link is faulty.


Number
Description When the BSC is upgraded to BSC6900 V900R014C00SPC500 and the

paging message packaging function is enabled for a faulty cell before
and after the upgrade, the BSC measures the A531: CS Pagings
Discarded on LAPD Link counter in the cell.
Severity Minor
Root Cause The cell once functioned properly before the upgrade, and therefore the
BSC obtained information about the cell's paging message packaging
capability from the BTS. However, the cell is faulty before and after the
upgrade, and therefore the BSC fails to obtain such information. As a
result, the BSC measures the A531: CS Pagings Discarded on LAPD
Link counter, which is the way the BSC processes this counter when the
paging message packaging function is disabled for the cell. Actually, the
BSC does not measure this counter when the paging message packaging
function is enabled.
Solution When the LAPD link is faulty, the BSC now measures the A531: CS
Pagings Discarded on LAPD Link counter regardless of whether the
paging message packaging function is enabled.
Solution Impact After this solution is used, the values of the following counters change:
 A531: CS Pagings Discarded on LAPD Link
 A532: PS Pagings Discarded on LAPD Link
 A530: SM Pagings Discarded on LAPD Link
The following table lists the specific changes of the preceding counters.
Whether Whether A531: CS A532: PS A530: SM

the the Pagings Pagings Pagings
Paging Paging Discarded Discarded Discarded
Message Message on LAPD on LAPD on LAPD
Packagin Packagin Link Link Link
g g
Function Function
Is Is
Enabled Enabled
Before After the
the Upgrade
Upgrade
Enable Enable Increase Increase Remain

unchanged
Enable Disable Increase Increase Increase
Disable Enable Increase Increase Decrease

19. The BSC does not provide counters to record information about paging messages
discarded over the A interface due to flow control.
Number
Description The BSC does not provide counters to record information about paging
messages discarded over the A interface due to flow control. This causes
difficulties in analyzing flow control.
Severity Major
Root Cause The paging messages discarded over the A interface due to flow control
can only be queried by using the DSP PAGINGNUM command.
However, the BSC does not provide any counters to record information
about such paging messages.
Solution The BSC now provides counters to record information about these
paging messages. The counters include:
 A1300C-Number of Discarded CS Paging Messages (Flow Control
over Message Arrival Rate)
 A1300P-Number of Discarded PS Paging Messages (Flow Control
over Message Arrival Rate)
over Re-Paging)
 A1302P-Number of Discarded PS Re-paging Messages (Flow Control
over Re-paging)
over CPU Overload)
 A1303P-Number of Discarded PS Paging Messages (Flow Control
over CPU Overload)
20. The BSC incorrectly measures the counters under the MR.Iterf.TRX_LOCGRP
measurement unit.


Number
Description If a BTS is not configured with subsites, the BSC incorrectly measures
the counters under the MR.Iterf.TRX_LOCGRP measurement unit. The
values of those counters are greater than 0.
Severity Major
Root Cause The BSC does not initialize the message buffer upon receiving the RF
RESOURCE IND message from the BTS and does not determine
whether message reading is complete based on the message length when
parsing the message. As a result, invalid bytes of the previous message in
the message buffer are parsed as subsite information.
Solution The BSC now initializes the message buffer upon receiving the RF
RESOURCE IND message from the BTS and determines whether
message reading is complete based on the message length when parsing
the message.
Solution Impact If the BTS is not configured with subsites, the BSC does not measure the
counters under the MR.Iterf.TRX_LOCGRP measurement unit. And the
measured value of the MR.Iterf.TRX_LOCGRP will be 0.
21. The interference level and quality calculated by the BSC are incorrect.


Number DTS2012013104326
Description The interference level and quality calculated by the BSC are incorrect.
Severity Minor
Root Cause When MR.Preprocessing is set to BSC_Preprocessing(BSC
preprocessing), the BSC uses an incorrect value to calculate the
interference level and quality after receiving measurement reports. This
leads to incorrect channel allocation.
Solution The BSC now uses a correct value to calculate the interference level and
quality.
Solution Impact After a BSC earlier than BSC6900 V900R012C01SPH526 or earlier than
BSC6900 V900R013C00SPC550 is upgraded to BSC6900
V900R014C00, user experience improves in the following aspects:
 The values for the counters S4210B-Downlink Interference Indication
Messages (SDCCH) and S4219B-Downlink Interference Indication
Messages (TCH) decrease dramatically.
 The value for the counter AS3241A-Average BTS Power Level of
AMR Call decreases slightly.
 The proportions of quality bands 0 to 3 in the uplink and downlink
increase slightly.
 The proportion of interference band 1 increases slightly.
However, if the BCCH in a cell experiences an abrupt interference, the
call drop rate of the cell increases by less than 0.01%.
22. The fast cell reselection between GSM and LTE networks becomes ineffective.


Number
Description
When the location area code (LAC) carried by a called MS is
inconsistent with the LAC of a GSM cell, the BSC does not deliver the
LTE E-UTRA absolute radio frequency channel number (EARFCN) to
the called MS after it reselects the GSM cell based on CS fallback and
hangs up. As a result, the called MS cannot quickly reselect an LTE cell,
and the fast cell reselection between GSM and LTE networks becomes
ineffective.
Severity
Major
Root Cause
In the preceding scenario, upon reselecting a GSM cell based on CS
fallback, the MS performs location area update (LAU) and then answers
a call. However, the BSC incorrectly considers that the MS performs
LAU when it answers a call. In this situation, the MS does not perform
fast cell reselection after LAU. As a result, the MS cannot perform fast
cell reselection after the call is released.
Solution The mechanism for identifying service type has been corrected.
Therefore, the BSC can correctly identify the services performed by an
MS to ensure that the MS can perform fast cell reselection.
Bit 19 of Reserved parameter 21 in the SET OTHSOFTPARA
command specifies whether the BSC can correctly identify the services
performed by an MS.
If bit 19 is set to 0, the BSC can correctly identify the services performed
by the MS.
If bit 19 is set to 1, the BSC cannot correctly identify the services

performed by the MS, and therefore such problem persists.
Solution Impact For BSC6900 V900R014C00SPC500 or later, this defect has been
corrected by default. There has no impact at the site.
For BSC6900 V900R014C00SPC500 or later that is upgraded from an
earlier version, this defect has not been corrected yet. To correct this
defect, set bit 19 of Reserved parameter 21 to 0.
After that, the value of the A3039J: SDCCH Seizures for Speech
Service, A301F: TCHF Seizures for Speech Service, or A301HH: TCHH
Seizures for Speech Service counter increases, and the value of the
RA333: Success Rate of Call Establishment counter decreases slightly.
23. The uplink packet immediate assignment success rate is low when BCCH+CBCH is
configured on the BCCH TRX.


Number
Description When BCCH+CBCH is configured on the BCCH TRX, the uplink
packet immediate assignment success rate is low.
Severity Minor
Root Cause When BCCH+CBCH is configured on the BCCH TRX, the proportion of
AGCHs decreases. If the number of assignment messages increases, the
BTS buffers assignment messages in the assignment queue before
sending them to MSs. As a result, the packet immediate assignment
message is sent to the MS at the time later than the starting time
specified in this message. This leads to an uplink packet immediate
assignment failure.
Solution When BCCH+CBCH is configured on the BCCH TRX, a 140-ms delay
is added to the starting time in the packet immediate assignment
message.
Whether to add a delay for the starting time in the immediate assignment
message is determined by the GCELLPSSWRSV0 parameter in the
SET GCELLRSVPARA command.
The following is as example:
SET GCELLRSVPARA: IDTYPE=BYID, CELLID=0,
GCELLPSSWRSV0=SW3-1;
 If this parameter is set to SW3-1, a 140-ms delay is added to the
starting time in the immediate assignment message.
 If this parameter is set to SW3-0, the starting time in the immediate
assignment message remains unchanged.
Solution Impact  When the traffic on the BCCH TRX is heavy, the value for the
counter Number of Successful Uplink PS Immediate Assignments
increases.
 The two-phase access delay prolongs.
24. The values of counters related to the number of abnormal TBF releases due to N3103
overflow increase if Not Send Dummy Message with Extended Uplink TBF is set to
NOTSEND(NOTSEND).


Number
Description If Not Send Dummy Message with Extended Uplink TBF is set to
NOTSEND(NOTSEND), the values of counters related to the number
of abnormal TBF releases due to N3103 overflow increase.
Severity Minor
Root Cause If Not Send Dummy Message with Extended Uplink TBF is set to
NOTSEND(NOTSEND), certain MSs do not respond to the Packet
Uplink Ack/Nack message where FAI is set to 1.
Solution The BSC does not measure the counters related to the number of
abnormal TBF releases due to N3103 overflow when the following
conditions are met:
 Inactive Period of Extended Uplink TBF is set to a value other
than 0.
 Not Send Dummy Message with Extended Uplink TBF is set to
NOTSEND(NOTSEND).
 The MS supports extended uplink TBFs.
 The MS does not respond to the Packet Uplink Ack/Nack message
where FAI is set to 1.
Whether the BSC measures these counters is determined by the
GCELLPSSWRSV0 parameter in the SET GCELLRSVPARA
command.
SET GCELLRSVPARA: IDTYPE=BYID, CELLID=0,
GCELLPSSWRSV0=SW4-1;
If GCELLPSSWRSV0 is set to SW4-1, the BSC does not measure the
counters related to the number of abnormal TBF releases due to N3103
overflow when MSs do not respond to the Packet Uplink Ack/Nack
message where FAI is set to 1. If GCELLPSSWRSV0 is set to SW4-0,
the BSC measures the counters related to the number of abnormal TBF
releases due to N3103 overflow when MSs do not respond to the Packet
Uplink Ack/Nack message where FAI is set to 1.
Solution Impact If GCELLPSSWRSV0 is set to SW4-1, the values of the following
counters decrease:
 Number of Uplink EGPRS TBF Abnormal Releases due to N3103
Overflow
 Number of Uplink GPRS TBF Abnormal Releases due to N3103
Overflow
25. The values for the counters of Receive Quality Measurement per TRX Location
Group are smaller than the actual values


Number
Description The values for the counters of Receive Quality Measurement per TRX
Location Group measurement is lower than the actual values
Severity Minor
Root Cause When the MR.Preprocessing parameter is set to
BTS_Preprocessing(BTS preprocessing) and the Receive Quality
Measurement per TRX Location Group measurement unit is
subscribed to on the M2000, the BSC obtains a random subsite number
when measuring the counters. As a result, the measured times of these
counters are few and the measured values are smaller than the actual
values.
Solution Use the correct subsite number instead of a random one.
Solution Impact The values of the counters under Receive Quality Measurement per
TRX Location Group measurement unit will increase. In addition, the
value of the counter “AR9780: Average CPU Usage of the XPU” will
increase by about 0.3% to 0.6% in the standard traffic model.
26. The BSC does not send an assignment failure message to the MSC
Trouble Ticket
DTS2012020304776
Number
Description After the BSC initiates a directed retry, it starts the dual transfer mode
(DTM) assignment procedure. If the directed retry fails, the BSC does
not send an assignment failure message to the MSC. The call release is
delayed
Severity Major
Root Cause The BSC stops the directed retry timer by mistake.
Solution The BSC now does not perform the DTM assignment procedure after
initiating a directed retry.
Solution Impact After this solution is used, the value of the CA312-Failed Assignments
(Channel Unavailable) counter increases slightly, and the values of the
following counters decrease slightly:
 A9802-Number of Uplink DTM Assignments Sent on DCCH
 A9808-Number of Downlink DTM Assignments Sent on DCCH
 A9803-Number of Successful Uplink DTM Assignments Received
on DCCH
 A9809-Number of Successful Downlink DTM Assignments
Received on DCCH
 RCA313-Assignment Success Rate
Test Case ID CASE_Commercial_PR_Regression_V9R13C00SPH556_102

27. The value for the counter Number of VAMOS Call Handover Attempts (Demultiplexing)
is greater than the actual value
Number
Description After the Voice services over Adaptive Multi-user channels on One Slot
(VAMOS) function is enabled, The value for the counter Number of
VAMOS Call Handover Attempts (Demultiplexing) is greater than the
actual value.
Severity Minor
Root Cause When demultiplexing is enabled for lightly-loaded VAMOS services,
the BSC uses an incorrect formula to calculate the number of channel
pairs to be demultiplexed.
Solution The BSC now uses a correct formula to calculate the number of channel
Solution Impact The value for the counter Number of VAMOS Call Handover Attempts
(Demultiplexing) will decrease.
28. The value for the counter Number of Successful VAMOS Candidate Call Decisions
(Intra-Cell Handover) is greater than the actual value
Trouble Ticket DTS2011120602349/DTS2011120603070
Number
Description After the VAMOS function is enabled, The value for the counter
Number of Successful VAMOS Candidate Call Decisions (Intra-Cell
Handover) is greater than the actual value.
Severity Minor
Root Cause When the BSC makes VAMOS candidate call decisions, it does not
filter out the calls initiated by MSs that support Single Antenna
Interference Cancellation (SAIC) but not VAMOS multiplexing and the
calls initiated by MSs that do not meet the P/N criterion.
Solution When the BSC makes VAMOS candidate call decisions, it now filters
out the calls initiated by MSs that support SAIC but not VAMOS
multiplexing and the calls initiated by MSs that do not meet the P/N
criterion.
Solution The value for the counter Number of Successful VAMOS Candidate
Impact Call Decisions (Intra-Cell Handover) will decrease.

CASE_Commercial_PR_Regression_V9R13C00SPH552_104
29. A low-priority MS occupies TCHs reserved for high-priority MSs


Number
Description A low-priority MS whose directed retry times out occupies the TCHs
reserved for high-priority MSs. Calls initiated by high-priority MSs fail
if no TCH is available except the reserved TCHs.
Severity Minor
Root Cause After the directed retry by a low-priority MS times out, the BSC
incorrectly sets the MS priority to the highest. As a result, the MS
occupies the TCHs reserved for high-priority MSs.
Solution After the directed retry by a low-priority MS times out, the BSC now
correctly sets the MS priority when reallocating TCHs to the MS.
Solution Impact The call success rate may increase which initiated by high-priority
MSs. And the call success rate may decrease which initiated by low-
priority MSs.
30. The value for the counter Failed Assignments (A Interface Failure) increases
Number
Description In BM/TC separated mode, a call fails if the following conditions are
met:
 Allow Reassign is set to YES(Yes).
 Assigning Better Cell Allowed is set to ON(On).
 The call fails to access the target cell and returns to the original cell
for TCH reassignment when the BSC preferentially selects a better
cell for the call.
The call fails because the BSC fails in TCH assignment, and The value
for the counter Failed Assignments (A Interface Failure) increases.
Severity Minor
Root Cause The BSC repeatedly requests circuit identification codes (CICs) over
the A interface for the call during TCH reassignment.
Solution The BSC now does not repeatedly request CICs over the A interface for
the call during TCH reassignment.
Solution Impact The value for the counter Failed Assignments (A Interface Failure) may
decrease.
31. The measured numbers of available PDCHs of certain types are inaccurate


Number
Description The measured numbers of available PDCHs of certain types are
inaccurate.
The values for the following counters are greater than the actual values:
 AR3034-Mean Number of Available Channels (PDCH) (Overlay
Cell)
 AR3025A-Mean Number of Available Channels (Support EDGE)
(900/850/810 band)
 AR3025B-Mean Number of Available Channels (Support EDGE)
(1800/1900 Band)
 CR3025-Mean Number of Available Channels (Support EDGE)
 AR3035-Mean Number of Available Channels (Support EDGE)
(Overlay Cell)
Severity Minor
Root Cause The BSC ignores certain conditions for measuring the numbers of
available PDCHs of certain types.
Solution The BSC now measures the number of available PDCHs only when all
measurement conditions are met.
Solution Impact The values for the above counters may decrease.
32. The value for the counter Number of Unsuccessful Application Attempts of Abis
Timeslot Because of no Idle Timeslot is incorrect
Number
Description The value for the counter Number of Application Attempts of Abis
Timeslot is greater than 0, but the numbers of successful and failed
applications for Abis timeslots are 0.
Severity Warning
Root Cause If the BTS works on the reverse ring in Abis over TDM mode and idle
Abis timeslots are insufficient, the BSC measures the counter Number
of Application Attempts of Abis Timeslot but not the number of failed
applications for Abis timeslots due to a BSC internal software defect.
Solution The BSC software defect has been rectified. If there is no idle Abis
timeslot, the BSC now measures the counter Number of Unsuccessful
Application Attempts of Abis Timeslot Because of no Idle Timeslot
once.
Solution Impact The value for the counter Number of Unsuccessful Application
Attempts of Abis Timeslot Because of no Idle Timeslot may increase.

33. The signaling BVC remains faulty for an extended duration after active/standby SGSN
boards are switched over
Number
Description After active/standby SGSN boards are switched over, the signaling
BSSGP virtual connection (BVC) remains faulty for an extended
duration. PS services are interrupted.
BSSGP is short for Base Station Subsystem GPRS Protocol.
Severity Major
Root Cause After SGSN boards are switched over, the network service virtual links
(NSVLs) over the Gb interface become temporarily faulty. If the
downlink NSVLs (detected by the SGSN) recover prior to the uplink
NSVLs (detected by the BSC), the SGSN initiates a Signaling BVC-
RESET procedure. Upon receiving the Signaling BVC-RESET
message from the SGSN, the BSC responds with a Signaling BVC-
RESET-ACK. Because the uplink NSVLs are still faulty, the network
service (NS) module discards the Signaling BVC-RESET-ACK
message. However, the network management (NM) module assumes
that the Signaling BVC-RESET-ACK has been successfully sent to the
SGSN and updates the Signaling BVC status to normal. As a result, the
Signaling BVC status is inconsistent on the BSC and SGSN sides.
Solution After the BSC receives a Signaling BVC-RESET from the SGSN, the
BSC now does not forward the Signaling BVC-RESET message to the
NM module if the NS module does not finish rectifying the NSVL
fault.
Solution Impact None.
34. The value for the counter Number of Failed VAMOS Channel Multiplexing Attempts
(Assignment) is incorrect

Trouble Ticket
DTS2011101302252
Number
Description The value for the counter Number of Failed VAMOS Channel
Multiplexing Attempts (Assignment) is incorrect.
Severity Minor
Root Cause When VAMOS multiplexing during assignment fails, the BSC uses an
incorrect method to determine the status of VAMOS multiplexing.
Solution When measuring the counter Number of Failed VAMOS Channel
Multiplexing Attempts (Assignment), the BSC uses a correct method to
determine the status of VAMOS multiplexing.
Solution Impact The value for Number of Failed VAMOS Channel Multiplexing
Attempts (Assignment) will be correct.
35. Configuring 32 neighboring GSM cells with 32 frequencies is not allowed in an MOCN
shared cell on a single telecom operator's network


Number
Description Configuring 32 neighboring GSM cells with 32 frequencies is not
allowed in an MOCN shared cell on a single telecom operator's
network. MOCN convergence cannot inherit the planned neighboring
GSM cell data.
Severity Minor
Root Cause As defined in 3GPP TS44.018, a cell can be configured with a
maximum of 64 neighboring GSM cells, but only 32 neighboring cell
frequencies.
Solution  A cell configured as an MOCN shared cell can now be configured
with a maximum of 64 neighboring GSM cells with 64 frequencies.
If this cell is shared by two telecom operators, either telecom
operator can be configured with a maximum of 32 neighboring GSM
cells with 32 frequencies.
 The BA1 list still supports the configuration of a maximum of 32
frequencies and 64 neighboring GSM cells. To configure more than
32 frequencies for neighboring GSM cells, manually add the
additional frequencies to the BA1 list.
 If Filter CS Based on Operator Neighboring Cell List is set to
YES(Yes) but the telecom operator is not identified, or if Filter CS
Based on Operator Neighboring Cell List is set to NO(No), the BA
list in the SI 5, 5bis, or 5ter sent by the BSC contains only 32
neighboring GSM cells with 32 frequencies (sorted in ascending
order). Otherwise, the BSC sends the SI Modify carrying a
maximum of 32 frequencies for neighboring GSM cells served by
the identified telecom operator.
 Frequencies for neighboring GSM cells are dynamically configured
and sent in the SI 5, 5bis, or 5ter.
36. Only 64 frequencies can be configured for a GSM cell


Number
Description Only 64 frequencies can be configured for a GSM cell. Users cannot
perform certain data configuration during network planning.
Severity Minor
Root Cause As defined in 3GPP TS44.018, the BSC sends MSs the SI 1, carrying
the frequency list (referred to as a CA list) of a GSM cell with
frequency hopping (FH) enabled. The CA list contains a maximum of
64 frequencies due to the length limit on messages transmitted over
the Um interface.
Solution  A maximum of 128 frequencies can now be configured for a GSM
cell. No more than 64 frequencies can be on the same frequency
band as the BCCH frequency. A maximum of 64 frequencies can be
configured for a cell in a single mobile allocation (MA) group.
 A GSM cell can be configured with two types of frequencies:
Frequencies on the same frequency band as the BCCH frequency:
These frequencies are contained in the CA list in the SI 1 to MSs.
Frequencies on frequency bands different from the BCCH
frequency: These frequencies are contained in an assignment or
handover command message to MSs.
37. The multiplexing rate is low during peak hours after the VAMOS feature is enabled
Number
Description The multiplexing rate is low during peak hours after the Voice services
over Adaptive Multi-user channels on One Slot (VAMOS) feature is
enabled. Ongoing services are not affected, but channel usage decreases.
Severity Minor
Root Cause Due to the TCHF-TCHH adjustment or channel insufficiency during
peak hours, calls are likely to be placed in queue awaiting channel
allocation. After calls are allocated channels successfully, some MS
capabilities that support the VAMOS feature are updated incorrectly. As
a result, these MSs fail to perform channel multiplexing, which reduces
the channel multiplexing rate.
Solution The capabilities of MSs that support the VAMOS feature are now
updated correctly.
Solution Impact The values for the counters Number of VAMOS Channel Multiplexing
Attempts (Assignment) and Number of VAMOS Channel Multiplexing
Attempts (Intra-Cell Handover) increase.

38. The values of Downlink Interference Indication Messages (TCH) and Downlink
Interference Indication Messages (SDCCH) increase greatly after a BSC is upgraded to
BSC6900 V900R014C00SPC500
Number
Description In a version between BSC6900 V900R013C00 and BSC6900

V900R013C00SPH532, the values of Downlink Interference Indication
Messages (TCH) and Downlink Interference Indication Messages
(SDCCH) increase greatly. The values of Downlink Interference
Indication Messages (TCH) and Downlink Interference Indication
Messages (SDCCH) are greater than the actual numbers.
Severity Minor
Root Cause The BSC uses incorrect formulas to estimate channel interference after
MR.Preprocessing is set to BSC preprocessing.
Solution The BSC uses correct formulas to estimate channel interference after
MR.Preprocessing is set to BSC preprocessing.
Solution The values of Downlink Interference Indication Messages (TCH) and
Impact Downlink Interference Indication Messages (SDCCH) may decrease
after a BSC is upgrade from From a version between BSC6900
V900R013C00 and BSC6900 V900R013C00SPH532.
In scenarios with strong interference over the Um interface, the high
quality indicator (HQI) may change.
39. BSC incorrectly determines the value of CCCH Load Indication Period


Number
Description When the value of the CCCH Load Indication Period parameter is
greater than 60, a BSC does not resolve the congestion problem. As a
result, CCCH congestion cannot be relieved. CCCH congestion cannot
be relieved.
Severity Minor
Root Cause Because of software errors, a BSC discards a load indication message
when it detects that the value of the CCCH Load Indication Period
parameter in the message is greater than 60. Therefore, when the value
of the CCCH Load Indication Period parameter is greater than 60,
the BSC does not resolve the congestion problem because it discards
the load indication message.
Solution The BSC software errors are corrected so that the BSC determines that
CCCH Load Indication Period is valid when CCCH Load
Indication Period ranges from 0 to 255.
Solution Impact If the value of the CCCH Load Indication Period parameter is
greater than 60 after the software errors are corrected, the following
performance counters decrease:
Counter Impact
AR9505: Number of Uplink PS Immediate Decrease

Assignments
AR9307: Number of Successful Downlink PS Decrease
Immediate Assignments
40. The incoming BSC signaling channel handovers fail in certain scenarios

Trouble Ticket
DTS2011101806330
Number
Description An incoming BSC signaling channel handover fails if the channel type in
the handover request message is TCHH-only or TCHF-only. The
incoming BSC signaling channel handover success rate is low.
Severity Minor
Root Cause The BSC allocates an SDCCH to an MS during an incoming BSC

signaling channel handover if the channel type in the handover request
message is TCHH-only or TCHF-only.
Solution The BSC allocates a TCHH or TCHF accordingly to an MS during an
incoming BSC signaling channel handover if the channel type in the
handover request message is TCHH-only or TCHF-only.
Solution Impact The incoming BSC signaling channel handover success rate may
increase after this solution is applied.
4.3 Known Issues

1. An MS that has not been defined in the 3G network encounters 2G/3G ping-pong cell
reselections in NC2 mode.
Number
Description In NC2 mode, after the BSC instructs an MS that has not defined in the
3G network to reselect a 3G cell, the MS cannot process PS services in
the 3G cell and encounters ping-pong cell reselections.
Severity Suggestion
Workaround None
Progress The cause of this issue has been found and the issue will be resolved in
a later version.



V900R014C00SPC300
5.1 What's New

New Features
1. Protocol-specific Packet Capturing

Description The protocol-specific packet capturing function applies to the FG2a, GOUa,
FG2c, GOUc, FG2d, and GOUd boards. With this function, the following
packets can be separately captured over the ports on the preceding boards:
 Dynamic Host Configuration Protocol (DHCP) packets
 All IP packets of a specified address
 802.3ah/Link Aggregation Control Protocol (LACP) packets
 Address Resolution Protocol (ARP) packets
 Internet Control Message Protocol (ICMP) packets
 Bidirectional Forwarding Detection (BFD) packets
 IP performance monitoring (IPPM) packets
 NodeB OM packets
 Gas Tube Protector Unit (GTPU) control packets
 GTPU data packets
 802.1ag packets
Benefit Users can specify fewer parameters for packet capturing.
Implementation This function differentiates packets according to their protocol types and
captures the packets in compliance with a certain protocol.
Related To perform protocol-specific packet capturing, perform the following
Operations operations on the LMT:
Choose Trace > Device Commissioning > Packet Capture. On the
displayed Packet Capture dialog box, choose Basic Mode from the Mode
Select drop-down combo box and choose an appropriate value from the
Scene Select drop-down combo box.
Number
Feature ID MRFD-210801
2. Abis Transmission Backup Enhancement

Description End-to-end IP over FE/GE and IP over E1 transmission links are

configured in primary/backup mode to provide transmission
redundancy in Abis over IP mode. When the primary link is faulty, the
BTS automatically switches ongoing services over to the backup link.
As a result, ongoing services are interrupted for less than one minute.
After the switchover, new services are assigned to the backup link.
After the primary link is recovered, the BTS automatically switches
ongoing services back to the primary link. After the switchover, new
services are assigned to the primary link.
Benefit  Improves Abis link reliability by shortening the service interruption
duration caused by Abis link faults.
 Improves GSM network availability.
Implementation For a traffic-carrying link, the BTS checks the link status using the
LAPD link status check function.
For a non-traffic-carrying link, the BTS checks the link status using a
loopback mechanism. The BTS sends UDP ping packets to the BSC
through the link. Upon detecting the UDP ping packets, the BSC loops
back the packets to the BTS. If the BTS receives the UDP ping packets,
the link is normal. Otherwise, the link is faulty.
If the BTS finds that the primary link is faulty, the BTS automatically
switches ongoing services over to the backup link. When the primary
link is recovered, the BTS automatically switches the services back to
the primary link.
 During the switchover, ongoing services are interrupted for less than one
minute.
 Changing the value of the Wait Time Before Link Switchover parameter
affects the service interruption duration.
 Both the primary and backup links are configured with an IP path. Services
can only be assigned to the IP path that corresponds to the traffic-carrying link.
Related The following is an example.

Operations 1. Set the IP physical transmission type.
− For a new BTS, run the ADD BTS command with
IPPHYTRANSTYPE set to IP_OVER_FE/GE_AND_E1.
ADD BTS: BTSID=0, BTSNAME="BtsName",
BTSTYPE=BTS3900A_GSM, SEPERATEMODE=SUPPORT,
SERVICEMODE=IP,
IPPHYTRANSTYPE=IP_OVER_FE/GE_AND_E1,
SRANMODE=SUPPORT, INNBBULICSHAEN=NO;
− For a reconstructed BTS, run the MOD BTS command with
IPPHYTRANSTYPE set to IP_OVER_FE/GE_AND_E1.
MOD BTS: IDTYPE=BYID, BTSID=0, SERVICEMODE=IP,
IPPHYTRANSTYPE=IP_OVER_FE/GE_AND_E1;
2. Run the ADD BTSIPBAK command to add BTS and BSC IP
addresses for the standby link.
ADD BTSIPBAK: IDTYPE=BYID,
BTSID=0,BAKBTSIP="40.40.40.1", BAKBSCIP="40.40.40.40",
BAKCFGFLAG=NULL;

3. (Optional) Run the SET BTSLNKBKATTR command to modify

the attributes of the standby link.
SET BTSLNKBKATTR: IDTYPE=BYID, BTSID=0, WTBS=0,
DETECTTXINT=3, DETECTCOUNT=5;
4. Run the ADD IPPATH command to add an IP path for the active
link.
ADD IPPATH: ANI=0, PATHID=0, ITFT=ABIS, PATHT=EF,
TXBW=100000, RXBW=100000, VLANFlAG=DISABLE,
PATHCHK=DISABLED, AbisLnkBKFLAG=ON;
5. Run the ADD IPPATH command to add an IP path for the standby
link.
ADD IPPATH: ANI=0, PATHID=1, ITFT=ABIS, PATHT=EF,
TXBW=100000, RXBW=100000, VLANFlAG=DISABLE,
PATHCHK=DISABLED, AbisLnkBKFLAG=ON ,
PATHFLAG=Backup;
Trouble Ticket None
Number
3. New Transport Layer Alarms and Event

Description A transport layer alarm is reported under the following conditions:

 The total number of transport layer resource requests within a period
reaches the minimum number.
 The ratio of transport layer resource request failures to total requests
reaches the alarm threshold.
Benefit  When services are affected due to configuration errors or traffic
overload, an alarm is reported, reminding users to solve the problem.
Implementation  Each MPU subsystem periodically calculates the number of Abis,
Ater, TC, and board switching resource requests and request failures.
When the ratio of request failures to total requests reaches the alarm
threshold and the total number of requests reaches the minimum
number, ALM-21604 Insufficient Transmission Resources is
reported. The alarm is cleared when either of the following
conditions is met:
− The ratio of request failures to total requests is smaller than or
equal to the alarm clearance threshold, and the total number of
requests reaches the minimum number.
− The number of request failures is zero for three consecutive
periods.
 Each MPU subsystem periodically calculates the number of IP path
resource requests and request failures. When the ratio of request
failures to total requests is greater than or equal to 5% and the total
number of requests is greater than or equal to 10, ALM-21605 Path
Configuration Error is reported. The alarm is cleared when either of
the following conditions is met:
− The ratio of request failures to total requests is zero, and the total
number of requests is greater than or equal to 10.
− The number of request failures is zero for three consecutive
periods.
 EVT-22921 Unconfigured Circuits over A Interface is reported under
the following conditions:
− When the MPU subsystem receives a circuit reset message,
circuit blocked message, circuit unblocked message, assignment
request message, or switchover request message from the MSC.
− The corresponding Circuit Identification Codes (CICs) are not
configured or the CIC state configured on the MSC is
inconsistent with that configured on the BSC.

Related  Run the SET TNALMPARA command with AlmSwitch,

Operations AlmCntPeriod, AllocTimesPerPeriod, KpiAlmThd, and
KpiAlmClrThd set to appropriate values. The following is an
example:
SET TNALMPARA: FaultType=Abis, AlmSwitch=ON,
AlmCntPeriod=5, AllocTimesPerPeriod=10, KpiAlmThd=15,
KpiAlmClrThd=5;
 Run the LST TNALMPARA command to query the parameters
related to the preceding alarms.
LST TNALMPARA: FaultType=Abis;
 Run the DSP IPPATHCFGERRIP command to query the peer IP
addresses that failed to match IP paths. The following is an example:
DSP IPPATHCFGERRIP: SRN=0, SN=0;

Number
Feature ID None
4. WLAN Hot Spot Notification

Description With the WLAN Hot Spot Notification feature, the BSC sends WLAN
access information configured by operators to the MSs supporting
WLAN Hot Spot Notification through the GSM network.
Benefit Decreases PS service loads in GSM cells by migrating PS services
from GSM cells to the WLAN.
Helps operators learn about the operating status of the WLAN by
providing counters related to the WLAN Hot Spot Notification feature.
Implementation After MSs supporting the WLAN Hot Spot Notification feature send
WLAN registration requests to the BSC, the BSC will send WLAN
access information configured by operators to MSs through the GSM
network if the following conditions are met:
− The BSC has been configured with the service set identifier
(SSID).
− The WLAN Hot Spot Notification feature is enabled in GSM
cells.
− PS service loads in GSM cells exceed the specified value for
WLAN Load Distribution Start Threshold.
The BSC will measure counters related to the success rate and failure
causes for WLAN load distribution.
Related The MML commands related to this feature are as follows:
Operations To set parameters controlling WLAN load distribution for GSM cells,
run the following command:
SET GCELLWLAN
SET GCELLWLAN: IDTYPE=BYID, CELLID=1, WlanCtrl=ON,
LoadThrToWlan=60, LoadThrStpWlan=40, WifiTmr=10,
StpWifiTmr=10;
To set parameters related to WLAN access for operators, run the
following command:
ADD GWLANINFO
ADD GWLANINFO: OPINDEX=0, SSID="CMCC";
Trouble Ticket OR201109095277
Number
5. GPRS Packet Fast Transmission

Description The GPRS Packet Fast Transmission feature extends the size of the
downlink GPRS sending window to a value greater than 64 and
reduces the probability of downlink window stop-and-wait.
Benefit This feature increases the rate for sending downlink GPRS data.
Implementation The Downlink GPRS TBF Window Expansion Optimization

parameter is added to control the size of the downlink GPRS sending
window. This enables the BSC to continue sending downlink GPRS
data even when the downlink GPRS sending window reaches 64.
Related Run the SET GCELLPSOTHERPARA command to set the size of
Operations the downlink GPRS sending window. The following is an example:
SET GCELLPSOTHERPARA: IDTYPE=BYID, CELLID=0,
DlGprsTbfExpandOp=90;
Trouble Ticket None
Number
6. LLC Acceleration
Description With the LLC Acceleration feature, the BSC reorders LLC PDUs
whose N-PDU numbers are in random order before sending them to
MSs. The random is generally caused by transmission faults or faults in
the CN.
Benefit The BSC sends LLC PDUs in a correct order to MSs, avoiding data
packet retransmission by the CN.
Implementation The BSC checks N-PDU numbers for downlink LLC PDUs. If the N-
PDU numbers are in random order, the BSC buffers and reorders the
downlink LLC PDUs. The BSC then sends downlink LLC PDUs in a
correct order to MSs within a specified time.
Related Run the SET GCELLPSOTHERPARA command to enable the
Operations function of reordering downlink LLC PDUs. The following is an
example:
SET GCELLPSOTHERPARA: IDTYPE=BYID, CELLID=0,
LLCPDUReorder=ON;
Trouble Ticket None
Number
Modified Features
1. The default value of the POLICY parameter has been changed

Description The default value of the POLICY parameter in the SET

WEBLOGINPOLICY command has been changed from COMPATIBLE
to LOGIN_HTTPS_ONLY.
After the change, users must use the Hypertext Transfer Protocol Secure
(HTTPS) protocol to log in to a local maintenance terminal (LMT), but the
Hypertext Transfer Protocol (HTTP) is still used to transmit data.
 Port 443 must be open on all the network elements (NEs) managed by the LMT
before the HTTPS protocol is enabled.
 Opening the LMT login window using HTTPS is slightly slower than using HTTP.
 When a user logs in to the LMT using HTTPS, the web browser displays a security
warning, which does not affect operation of the LMT and can be ignored.
Benefit Enhances security for data transmission between the LMT and NEs
Minimizes malicious attacks on the NEs
Implementatio Users can run the SET WEBLOGINPOLICY command to change the
n value for POLICY.
Note: An upgrade to RAN14.0 does not change the value for POLICY.
Related 1.Run the following command to set POLICY to the new default value:
Operations SET WEBLOGINPOLICY: POLICY=LOGIN_HTTPS_ONLY;
Run the following command to reset the LMT:
RST OMUMODULE:TG=ACTIVE, MNAME=weblmt;
2.Run the LST WEBLOGINPOLICY command to check whether the
new default value is used.
The preceding steps are not required for new sites because the new default value is
used by default.
Trouble Ticket None

Number
Feature ID None
2. Optimizing the Method for Calculating Cell Load

Description This feature incorporates the method for calculating cell load based on the
proportion of idle timeslots.
Benefit This feature helps reduce cell load because the optimization increases the
probability for the BSC to trigger load-based handovers and TCHH
allocations when optimizing intra-cell handovers is enabled. For the
standard traffic model, enabling this feature increases the CPU usage of the
XPU board by 2% to 3%.
NOTE
Optimizing intra-cell handovers includes optimizing intra-cell TCHF-
TCHH handovers, intra-concentric cell handovers, and intra-cell TCHH
integration.
Implementatio The Load Calculation Optimization parameter is added to specify
n whether the BSC calculates cell load based on the TCHF usage. If this
parameter is set to ON(On), the BSC calculates cell load based on the
TCHF usage. If this parameter is set to OFF(Off), the BSC calculates cell
load based on the TCHH usage.
The Load Type parameter is added to work with the Load Calculation
Optimization parameter. Assuming that Load Calculation Optimization
is set to ON(On), the BSC calculates cell load based on the proportion of
idle TCHFs:
If Load Type is not specified, dynamic PDCHs are considered as occupied
TCHFs.
If Load Type is set to any of the following values, dynamic PDCHs are
considered as idle TCHFs:
 INTRACELLFHHO(Intra-cell TCHF-TCHH Handovers)
 INTERCELLLOADHO(Inter-cell Load Control)
 SUBCELLLOADHO(OL and UL Load Control)
 HALFRATEREPACKING(TCHH Integration)
 HALFRATEASSIGNMENT(TCHH Assignment)
Setting Load Calculation Optimization to ON(On) takes effect only for Huawei
handover algorithm II if Load Type is set to any of the preceding values except
HALFRATEASSIGNMENT(TCHH Assignment).
Related Run the SET GCELLCHMGAD command with Load Calculation

Operations Optimization set to ON(On) and Load Type set to an appropriate value.
SET GCELLCHMGAD: SCENELOADTYPE=INTRACELLFHHO-
0&INTERCELLLOADHO-0&SUBCELLLOADHO-
0&HALFRATEREPACKING-0&HALFRATEASSIGNMENT-1,
TCHLOADOPTSWITCH=ON;
Number
3. Optimizing Interference Handovers Between Concentric Cells

Description This feature enables interference handover parameters to be set

independently for underlaid and overlaid subcells and channel allocation
to be optimized during quality-based handovers.
Benefit  This feature increases the high quality indicator (HQI) and reduces
interference, increasing the success rate of quality-based handovers and
decreasing the number of quality-based handovers.
 When the interference in overlaid and underlaid subcells is different,
this feature reduces intra-network interference and transmit power on
the entire network, improving KPIs.
Implementation  The following parameters have been added to the SET GCELLHOAD
command:
 OL Offset for Interference HO
 OL UL Level Offset for Interference HO
 OL DL Level Offset for Interference HO
 OL UL Quality Offset for Interference HO
 OL DL Quality Offset for Interference HO
 In addition, the Quality Handover Channel Priority Optimize has been
added to the SET GCELLCHMGAD command.
 When Huawei handover algorithm II is used:
 If an MS camps on the overlaid subcell in a concentric cell and the OL
Offset for Interference HO parameter is set to YES(Yes), the BSC
determines whether to allow interference handovers based on the
settings of the following parameters:
 OL UL Level Offset for Interference HO
 OL DL Level Offset for Interference HO
 OL UL Quality Offset for Interference HO
 OL DL Quality Offset for Interference HO
 If an MS camps on the underlaid subcell in a concentric cell or the OL
Offset for Interference HO parameter is set to NO(No), the BSC
determines whether to allow interference handovers based on the
settings of the following parameters:
 ULevOffset for Interfere HO
 DLevOffset for Interfere HO
 UQualOffset for Interfere HO
 DQualOffset for Interfere HO
 During the following channel allocations due to quality-based
handovers (including reassignment, interference handover, and bad
quality (BQ) handover), source channels refer to those occupied before
handovers and target channels refer to those to be selected in channel
allocation.
 Of two target channels that do not participate in frequency hopping
(FH), when one uses the same frequency as that used by the source
channel and the other uses a frequency different from that used by the
source channel:
 If the Quality Handover Channel Priority Optimize parameter is set
to ON(On), the latter channel is preferentially allocated.


to OFF(Off), frequencies are not considered.
 When both target channels have the same frequency set as that used by
the source channel or channels that do not participate in FH share the
same frequency set with the source channel:
to ON(On), the channel on the timeslot different from that of the source
channel is preferentially allocated. If either or both of two target
channels and the source channel are on the same timeslot, the channel
on the TRX different from that of the source channel is preferentially
allocated.
to OFF(Off) and two channels have the same frequency set as that of
the source channel, the channel on the TRX different from that of the
source channel is preferentially allocated. If two target channels and the
source channel are on the same TRX, the channel on the timeslot
different from that of the source channel is preferentially allocated.
 When two target channels have a frequency set which is different from
that of the source channel:
to ON(On), TRX and timeslot factors are not considered.
to OFF(Off), TRX and timeslot factors must be considered. That is, the
channel on the TRX which is different from that of the source channel
is preferentially allocated. If two target channels and the source channel
are on the same TRX, the channel on the timeslot different from that of
the source channel is preferentially allocated.
Related Run the SET GCELLHOAD command with OL Offset for
Operations Interference HO set to YES(Yes). The following is an example:
SET GCELLHOAD: IDTYPE=BYID, CELLID=2,
INTERFEROFFSWITCHOL=YES, INTERFEREULEVOFFOL=-10,
INTERFEREDLEVOFFOL=0, INTERFEREULQUALOFFOL=0,
INTERFEREDLQUALOFFOL=10;
Run the SET GCELLCHMGAD command with Quality Handover
Channel Priority Optimize set to ON(On). The following is an example:
QUALHOPRIALLOW=ON;
Number
GBFD-510501
GBFD-111004

Description Optimization of the mechanism for forbidding consecutive intra-cell

handovers by using the HUAWEI I Handover feature
 The measurement and penalty ranges for consecutive intra-cell
handover are controlled.
Introduction of frequency deviation compensation for MSs accessing
overlaid subcells during concentric cell handovers specified by
Huawei handover algorithm I
The method for calculating the receive level of underlaid subcells is
controlled when the following conditions are met:
 The handover is performed in an enhanced concentric cell.
 An MS accesses the overlaid subcell.
 The BCCH receive level of underlaid subcells is lost.
Benefit Triggers intra-cell handovers more promptly, increasing the number
of intra-cell handover requests on a BSC. When certain frequency or
timeslot experiences interference, enable this function for the BSC to
trigger intra-cell handovers in a timely manner. When an entire cell
experiences serious interference, that is, most of channels experience
interference, you are advised not to enable this function. This is
because enabling this function increases the number of intra-cell
handovers, which may deteriorate the HQI and increase the call drop
rate.
Avoids unnecessary handovers from an overlaid subcell to a
neighboring cell and keeps the number of outgoing cell handovers
unchanged or slightly reduced when the MS accesses the overlaid
subcell and the BCCH receive level in underlaid subcells is lost in an
enhanced concentric cell.
Implementation The parameter User-Level Intra-Cell HO Prohibit is added. If this
parameter is set to YES(Yes), the measured object and the forbidden
object specified by the parameter Forbidden time after MAX
Times are changed from the whole cell to a user. If this parameter is
set to NO(No), the measured object and the forbidden object
specified by the parameter Forbidden time after MAX Times
remain the whole cell.
The parameter Concentric Cell Signal Compensation Optimize is
added. Assuming an MS accesses the overlaid subcell in an enhanced
concentric cell and the BCCH receive level of underlaid subcells is
lost:
 If the parameter Concentric Cell Signal Compensation Optimize
is set to ON(On), the receive level of underlaid subcells is
substituted by the sum of the TCH receive level of overlaid
subcells, power control compensation, and the value of UO Signal
Strength Difference.
 If this parameter is set to OFF(Off), the receive level of underlaid
subcells is substituted by the sum of the TCH receive level of
overlaid subcells and the power control compensation.

Related  Run the SET GCELLHOBASIC command with User-Level

Operations Intra-Cell HO Prohibit set to YES(Yes). The following is an
example:
INTRACELLSINUSEREN=YES;
 Run the SET GCELLHOIUO command with Current HO
Control Algorithm set to HOALGORITHM1(Handover algorithm
I) and Concentric Cell Signal Compensation Optimize set to
YES(Yes). The following is an example:
SET GCELLHOIUO: IDTYPE=BYID, CELLID=1,
HOCTRLSWITCH=HOALGORITHM1,
SIGAMPTDIFFOPTALLOW=ON;
Number CR GU01398
GBFD-110601
5. HUAWEI II Handover

Description Optimizes the mechanism for forbidding consecutive intra-cell

handovers, controlling measurement and penalty ranges for such
handovers.
The initial incremental filtering algorithm is added.
Mechanism is added to adjust the priorities of handovers using
Huawei handover algorithm II.
This feature optimizes intra-cell load-based handovers.
Benefit  Triggers intra-cell handovers more promptly, increasing the
number of intra-cell handover requests on a BSC. When certain
frequency or timeslot experiences interference, enable this
function for the BSC to trigger intra-cell handovers in a timely
manner. When an entire cell experiences serious interference,
that is, most of channels experience interference, you are advised
not to enable this function. This is because enabling this function
increases the number of intra-cell handovers, which may
deteriorate the HQI and increase the call drop rate.
 When consecutive downlink measurement reports (MRs) are
lost:
− Bad quality (BQ) handovers are triggered more timely and
frequently.
− The value of the Call Drop Rate on TCH per cell(Excluding
Handover) counter decreases.
− The value of the Call Drop Rate on TCH per cell(including
Handover) counter remains unchanged or increases slightly.
− The value of the Call Drop Rate on TCH per BSC counter
remains unchanged or decreases slightly.
− The value of the Internal Intra-Cell Handover Requests or
Number of Outgoing Internal Inter-Cell Handover Requests
counter remains unchanged or increases slightly.
 More better cell handovers but fewer BQ handovers are
performed. The value of the Outgoing Inter-Cell Handover
Commands (Better Cell) counter increases while the values of
the Outgoing Inter-Cell Handover Commands (Uplink Quality)
and Outgoing Inter-Cell Handover Commands ((Downlink
Quality) counters decrease.
 Accurately controls the number of MSs that perform intra-cell
load-based handovers, including intra-concentric cell handovers
and intra-cell TCHF-TCHH load-based handovers, preventing
excessive MSs from performing handovers simultaneously when
the load is heavy. Increases the number of available TCHFs in a
cell.
 For the standard traffic model, enabling this feature increases the
CPU usage of the XPU board by 0.5% to 1%.
Implementation The parameter User-Level Intra-Cell HO Prohibit is added. If
this parameter is set to YES(Yes), the measured object and the
forbidden object specified by the Forbidden time after MAX
Times parameter are changed from the whole cell to a user. If this
parameter is set to NO(No), the measured object and the forbidden
object specified by the parameter Forbidden time after MAX

Times remain the whole cell.

The Initial Increment Filtering Allowed parameter is added. If
this parameter is set to YES(Yes), the initial incremental filtering
algorithm is enabled when a call accesses a new channel, and the
timers specified by Min Interval for TCH Hos and Min Interval
for SDCCH Hos are started at the same time. If this parameter is
set to NO(No), the initial incremental filtering algorithm is
disabled.
The Voice/Data Channel Increment Filter Length parameter is
added to specify the period of initial incremental filtering for voice
or data channels.
The Signaling Channel Increment Filter Length parameter is
added to specify the period of initial incremental filtering for
signaling channels.
The HO Priority Adjustment parameter is added. If this
parameter is set to YES(Yes), an edge handover is not classified as
an emergency handover, a better cell handover takes precedence
over an emergency handover, and cell category, priority, and load
are considered in an emergency handover. If this parameter is set
to NO(No), the priorities of handovers using Huawei handover
algorithm II remain unchanged.
The OL/UL Load Control Optimization parameter is added. If
this parameter is set to YES(Yes), the BSC accurately controls the
number of MSs that perform intra-concentric cell load-based
handovers.
The Intra-cell F/H Load Control Optimization parameter is
added. If this parameter is set to YES(Yes), the BSC accurately
controls the number of MSs that perform intra-cell TCHF-TCHH
load-based handovers.
The TCHH Integration parameter is added. If this parameter is
set to YES(Yes), the BSC enables two MSs that use different
timeslots on a half-rate channel to share one timeslot by
performing a forced handover.

Related  Run the SET GCELLHOBASIC command with User-Level

Operations Intra-Cell HO Prohibit set to YES(Yes). The following is an
example:
INTRACELLSINUSEREN=YES;
 Run the SET GCELLHOFITPEN command with Initial
Increment Filtering Allowed set to YES(Yes), Voice/Data
Channel Increment Filter Length and Signaling Channel
Increment Filter Length set to appropriate values. The following
is an example:
SET GCELLHOFITPEN: IDTYPE=BYID, CELLID=1,
DATASTRUPFLTLEN=5, SIGSTRUPFLTLEN=2,
INITUPFILEN=YES;
 Run the SET GCELLHOBASIC command with HO Priority
Adjustment set to YES(Yes). The following is an example:
HOPRIOMODEN=YES;
 Run the SET GCELLHOIUO command with OL/UL Load
Control Optimization set to YES(Yes). The following is an
example:
SET GCELLHOIUO: IDTYPE=BYID, CELLID=0,
UOLOADOPTSWITCH=YES;
 Run the SET GCELLHOBASIC command with Intra-cell F/H
Load Control Optimization set to YES(Yes). The following is an
example:
INTRACELLFHOPTSWITCH=YES;
 Run the SET GCELLCHMGAD command with TCHH
Integration set to YES(Yes). The following is an example:
HALFRATEREPACKINGSWITCH=YES;
Number CR GU01421
CR GU01422
CR GU01425
6. Optimizing Interference Band and Continuity Preference

Description This feature enables the BSC to consider PDCH allocation continuity and
inherits the existing interference band information during channel
conversion. This ensures that the interference preference accurately
indicates the interference on channels.
Benefit Optimizes channel allocation modes by considering PDCH allocation
continuity and reducing the numbers of PDCH conversions and
preemptions.
Improves the high quality indicator (HQI) by eliminating interference,
increasing the success rate of quality-based handovers, and reducing the
number of quality-based handovers.
Implementation The Channel Allocation Algorithm Optimization and BCCH TRX
Allocation Preference parameters are added to the SET
GCELLCHMGAD command. In addition, two values Continuity
preferred and Management preferred are added to the Channel Allocate
Strategy parameter in the SET GCELLCHMGBASIC command.
During TCH allocation:
If the BCCH TRX Allocation Preference parameter is set to CSFIRST,
the BSC preferentially allocates TCHs on the BCCH TRX to CS services.
If the BCCH TRX Allocation Preference parameter is set to PSFIRST,
the BSC preferentially allocates TCHs on the non-BCCH TRX to CS
services.
If the Channel Allocation Algorithm Optimization parameter is set to
YES and the Channel Allocate Strategy parameter is set to Continuity
preferred, the BSC considers PDCH allocation continuity to ensure that
the TCHs on certain timeslots of certain TRXs are allocated to CS
services, reducing adverse impact on CS and PS services.
During channel conversion, the BSC inherits the existing interference
band preference and history preference. If a channel is released
abnormally, the BSC performs penalty on its interference band preference
to reduce the interference band preference.
When the Channel Allocate Strategy parameter is set to Continuity
preferred or Management preferred, the BSC allocates TCHs to CS
services based on the preference accordingly.
Related To set BCCH TRX Allocation Preference to CSFIRST, run the
Operations following command:
SET GCELLCHMGAD: BTRXPRIORITYSWITCH=CSFIRST;
To set Channel Allocation Algorithm Optimization to YES, run the
following command:
SET GCELLCHMGAD: CHALLOCATIONOPTSWITCH=YES;
To set Channel Allocate Strategy to Continuity preferred, run the
following command:
SET GCELLCHMGBASIC: CHALLOCSTRATEGY=CONTINUITY;
Number

7. Optimizing Load Sharing Algorithm for XPU Subsystems

Description The load sharing algorithm for XPU subsystems is optimized to balance
CPU loads on XPU subsystems.
Benefit  After the BSC6900 is upgraded to V900R014C00, the CPU usage
of XPU subsystems changes. Specifically, the CPU usage decreases
for XPU subsystems that are under heavy load before the upgrade
while increases for XPU systems that are under light load before the
upgrade. This reduces flow control risks for XPU subsystems that
are under heavy load before the upgrade.
 When the CPU usage for all XPU subsystems in the BSC exceeds
75% (the default value of the Share in CPU Rate parameter), calls
are not forwarded, and therefore the CPU usage does not increase.
 When load sharing is performed, the number of outgoing and
incoming calls increases, and therefore the average CPU usage
increases for all XPU subsystems in the BSC(about 0.5~2%).
Implementation  For a BSC6900 earlier than V900R014C00, the default load sharing
start threshold is 80%. Specifically, the BSC distributes calls to
other XPU subsystems under light load only if the CPU usage of an
XPU subsystem exceeds 80%.
 For a BSC6900 of V900R014C00, the load sharing start threshold
changes to 20%. This balances the CPU usage for all XPU
subsystems in the BSC and enhances the BSC's capability for
processing burst services, improving the system reliability.
Related None
Operations

Number
Feature ID None
8. Dynamic Planning of PDCH Channel Priority Type

Description Dynamic planning of the PDCH channel priority type (specified by the
PDCH Channel Priority Type parameter) enables the BSC to
automatically plan the following EGPRS channels based on their
numbers: EGPRS special channels, EGPRS priority channels, and
EGPRS normal channels. This feature enables the PDCH Channel
Priority Type parameter to be independently set for the underlaid and
overlaid subcells in a concentric cell.
Benefit Improves the efficiency for planning the PDCH channel priority type on
the live network.
Implementation  The following parameters are added to the SET GCELLPSCHM
command:
− GPRS Channel Priority Type Auto-Planning
− Number of EGPRS Special Channels
− Number of EGPRS Priority Channels
− Number of EGPRS Normal Channels
− Number of EGPRS Special Channels (OL Subcell)
− Number of EGPRS Priority Channels (OL Subcell)
− Number of EGPRS Normal Channels (OL Subcell)
 If the BSC detects that a PS cell starts to work, it automatically
distributes EGPRS channels of various types based on their numbers.
 If the total number of channels that can be configured in a cell is less
than the total number of EGPRS channels specified during parameter
setting, the number of EGPRS channels is ensured in the following
priority (from high to low): EGPRS priority channels > EGPRS normal
channels > EGPRS special channels. However, the PDCH channel
priority type is planned in the following priority (from high to low):
EGPRS special channels > EGPRS priority channels > EGPRS normal
channels. These channels are planned on the TRX with the highest
priority, from timeslots 7 to 0 in descending order. After all EGPRS
channels in a cell are planned according to the parameter settings, the
channels that are still available for planning in the cell are configured
as GPRS channels.
 The TRX priority is determined in the following sequence:
The TRX whose Spectrum Sharing Shutdown Allowed is set to
NO(No) is preferentially selected.
If Multiband RA Capability is set to BCCHANDSUBFREQS(BCCH
Band and Compatible Bands), the TRXs on a frequency band
compatible with the BCCH frequency band are preferentially selected.
The TRX that has more static PDCHs is preferentially selected.
If BCCH TRX Allocation Preference is set to PSFIRST(PSFirst), the
BCCH TRX is preferentially selected. If BCCH TRX Allocation
Preference is set to CSFIRST(CSFirst), a non-BCCH TRX is
preferentially selected.
The TRX that has more convertible channels and low interference is
preferentially selected. If two TRXs experience the same interference,
the TRX that has more convertible channels is preferentially selected.
The BSC checks dynamic planning of the PDCH channel priority type
every 30 minutes. If the preferred channel type planned this time is
different from that previously planned, the BSC triggers a PS cell reset

and starts an automatic planning again.

Related Run the SET GCELLPSCHM command with GPRS Channel Priority
Operations Type Auto-Planning set to ON(On). The following is as example:
SET GCELLPSCHM: IDTYPE=BYID, CELLID=0,
AutoGprsChPri=ON, EgprsSpeChnum=4, EgprsPriChnum=8,
EgprsNorChnum=18, EgprsSpeChnumInn=0, EgprsPriChnumInn=0,
EgprsNorChnumInn=0;
Number
9. PDCH Management Optimization

Description The PDCH management optimization algorithm improves the functions

of allocating, converting, preempting, and prebinding secondary links for
PDCHs.
Benefit  Enhances the PDCH continuity.
 Increases the multislot satisfaction rate.
 Improves the channel bearing efficiency and reduces the interference
caused by PS services to the entire network by decreasing the number
of TCHs converted to PDCHs and the number of occupied PDCHs.
NOTE
With this optimization, most PDCHs are distributed on certain TRXs
after PDCH conversion. For example, if a maximum of nine TCHs can
be converted to PDCHs in a cell, PDCHs may be distributed as follows
after PDCH conversion:
Eight PDCHs are distributed on a TRX, and the remaining one is
distributed on another TRX.
Such a distribution decreases the multislot satisfaction rate and single-
user throughput.
Implementation The PDCH Management Optimization parameter is added to the SET
GCELLPSCHM command.
 During PDCH allocation, if this parameter is set to ON(On), the
weight for the total number of continuous PDCHs on a TRX is added
to the channel allocation weight table. This ensures the PDCH
continuity.
 During PDCH conversion, if this parameter is set to ON(On), the
PDCH conversion priority is optimized as follows based on PDCH
continuity rules:
− For load-based PDCH conversion, the BSC preferentially converts
TCHs to PDCHs on a TRX with PDCHs to ensure that the existing
PDCHs and the PDCHs converted from TCHs are continuous. The
BSC converts TCHs to PDCHs on a TRX without PDCHs only
when no TCH is available for conversion on the TRX with PDCHs.
− For multislot capability-triggered PDCH conversion, the BSC
converts TCHs to PDCHs based on the MS multislot capacity. If all
TRXs have a sufficient number of TCHs for conversion, the BSC
preferentially converts TCHs to PDCHs on a TRX with PDCHs. If
no TRX has a sufficient number of TCHs for conversion, the BSC
converts TCHs to PDCHs on a TRX with the largest number of
available TCHs.
 During PDCH preemption, if this parameter is set to ON(On), the
preemption priority is optimized as follows: The channels on a TRX
with poor PDCH continuity, more GPRS channels, and fewer PDCHs
are preferentially preempted. On the TRX, GPRS channels are
preferentially preempted.
During PDCH activation, if this parameter is set to ON(On), the BSC
binds secondary links with EGPRS special channels, EGPRS priority
channels, and EGPRS normal channels based on the value for Number
of Initially Bound Secondary Links. However, the BSC does not bind
any secondary links with GPRS channels.
Related Run the SET GCELLPSCHM command with PDCH Management

Operations Optimization set to ON(On). The following is as example:

SET GCELLPSCHM: IDTYPE=BYID, CELLID=2,
EnPDAdminOpt=ON;
Number

Description The names of some license control items have been changed. The license
usage measurement for these license control items has been optimized.
In addition, the configuration data for some of these license control items
will be checked during an upgrade.
Benefit  The license usage measurement for certain license control items is
more accurate.
 During an upgrade, if the upgraded tool determines that the
configuration data exceeds the license capacity, users are prompted
to delete the extra data within 60 days after the upgrade or to apply
for a new license that meets the requirements of the configuration
data. Otherwise, the configuration on the system will be limited
after 60 days.
Implementation  License control items corresponding to the following features have
been changed(Licenses for the PS Power Control Resource feature
are calculated based on 64kbps):
− III Power Control AMR Power Control Resource
− AMR Coding Rate Threshold Adaptive Adjustment Resource
− Network Support SAIC Resource
− Active Power Control Resource
− PS Power Control Resource
− Extended Dynamic Allocation(EDA) Resource
− Dynamic Cell Power Off Resource
− PSU Smart Control Resource
− Enhanced Dual-Band Network Resource
− AFC(Automatic Frequency Correction) Resource
− Fast Move Handover Resource
− LLC Acceleration
− RACH Storm Filtration
− GPRS Packet Fast Transmission
For users who have not used the preceding features, the corresponding
license control items are added. For users who have used the preceding
features, the license usage measurement of the corresponding license
control items is based on the number of TRXs on which a specific
feature is enabled (Licenses for the RACH Storm Filtration feature are
calculated based on the number of cells).
 The upgrade tool will check the new license capacity when users
who have used the following features implement an upgrade:
− III Power Control AMR Power Control Resource
− AMR Coding Rate Threshold Adaptive Adjustment Resource
− Active Power Control Resource
− Enhanced Dual-Band Network Resource
− AFC(Automatic Frequency Correction) Resource
− Fast Move Handover Resource
− LLC Acceleration
− RACH Storm Filtration

− GPRS Packet Fast Transmission

If the configuration data for the license control items corresponding to
the preceding features exceeds the license capacity, users are prompted
to delete the extra data within 60 days after the upgrade or to apply for a
new license that meets the requirements of the configuration data. If no
action is taken, the ALM-20743 Insufficient License Resources will be
reported every day within 60 days, and the configuration on the system
will be limited after 60 days.
Related  To check whether configuration data of any license control items
Operations exceeds the license capacity, run the following command:
 To query the current usage of each license control item, run the
following command:
Number
Feature ID None
Deleted Features
None.

New Hardware
None.
Modified Hardware
None.
Removed Hardware
None.


5.1.5 Alarm Updates


5.1.6 Event Updates



5.2 Resolved Issues

1. The value of the PEAK.BSC.PROC.SPEED counter is incorrect in Gb over IP mode.
Number
Description In Gb over IP mode, when the active port is configured on the standby
Gb interface board in the BSC6900, the value of the
PEAK.BSC.PROC.SPEED counter is incorrect.
Severity Minor
Root Cause The value of the preceding counter should be calculated based on the
amount of data processed on both the active and the standby Gb interface
boards. The active board, however, reports only the amount of data
processed on itself. As a result, the value of the preceding counter is
smaller than the actual value.
Solution The active board sums up the amount of data processed on both the active
and the standby boards and then reports the summed-up values.
Solution Impact The value of the preceding counter becomes correct.
2. The BSC releases calls made by low-priority MSs with the release cause "OM
intervention" if low-priority MSs fail to perform forced handovers.


Number
Description If the eMLPP function is enabled and high-priority MSs preempt the
channels occupied by low-priority MSs, the BSC triggers low-priority
MSs to perform forced handovers. If the handovers fail, the BSC needs to
release calls made by low-priority MSs with the release cause "OM
intervention."
eMLPP stands for enhanced multi-level precedence and preemption.
Severity Minor
Root Cause After low-priority MSs fail to perform forced handovers, the BSC releases
calls made by low-priority MSs with an incorrect release cause.
Solution The BSC now releases calls made by low-priority MSs with the release
cause "preemption" if low-priority MSs fail to perform forced handovers.
Solution Impact After this solution is used, the value of the CM404-Number of Clear
Requests Sent on the A Interface (OM) counter decreases.
3. The unit of FE or GE BER in the output of the DSP BTSIPPM command is inconsistent
with the unit of FE or GE BER reported by BTSs.
Number DTS2012021304359
Description The unit of FE or GE BER in the output of the DSP BTSIPPM command
is byte/s. However, the unit of FE or GE BER reported by BTSs is bit/s.
Severity Minor
Root Cause The unit of FE or GE BER in the output of the DSP BTSIPPM command
is defined incorrectly.
Solution The unit of FE or GE BER in the output of the DSP BTSIPPM command
has been changed to bit/s.
4. The measured value for the counter Number of VAMOS Call Handover Attempts
(Demultiplexing) is greater than the actual value


Number
Description After the Voice services over Adaptive Multi-user channels on One Slot
(VAMOS) function is enabled, the measured value for the counter
Number of VAMOS Call Handover Attempts (Demultiplexing) is
greater than the actual value.
Severity Minor
Root Cause When demultiplexing is enabled for lightly-loaded VAMOS services,

the BSC uses an incorrect formula to calculate the number of channel
Solution The BSC now uses a correct formula to calculate the number of channel
Solution Impact The measured value for the counter Number of VAMOS Call Handover
Attempts (Demultiplexing) will decrease.
5. The call drop rate increases during handovers after the DTM function is enabled.
Number DTS2012022002672
Description After the Dual Transfer Mode (DTM) function is enabled, the call drop
rate increases during handovers.
Severity Minor
Root Cause When the BSC makes handover decisions, it allows only emergency
handovers, forced handovers and fast movement handovers for MSs in
DTM mode. Most of these handovers occur when the Um interface
quality is poor. As a result, the handover success rate is low.
Solution The DTM CS Handover Optimization parameter has been added to
specify the handover policy for MSs in DTM mode. If this parameter is
set to No, the BSC allows only emergency handovers, forced handovers
and fast movement handovers for MSs in DTM mode. If this parameter
is set to Yes, the BSC forbids only load-based handovers for MSs in
DTM mode.
Solution Impact If the DTM CS Handover Optimization parameter is set to Yes,the
values for the following counters increase:
Number of Abnormal Uplink DTM TBF Releases Due to CS Hangup or

Handover
Number of Abnormal Downlink DTM TBF Releases Due to CS Hangup

or Handover

6. The measured values for TFO-related counters are incorrect after an inter-cell handover
occurs.
Number DTS2012010601642
Description In BM/TC separated mode, if tandem free operation (TFO) is enabled,
and if full-rate or half-rate speech versions are used both before and
after an inter-cell handover, the measured values for TFO-related
counters are incorrect.
Severity Minor
Root Cause The TFO-related counters are measured on a per cell basis. After an
inter-cell handover occurs in the preceding scenario, the TFO-related
counters that should be measured for the target cell are measured for the
source cell.
Solution The TFO-related counters have been measured for the cell where an MS
is currently located.
Solution Impact The values for the TFO-related counters may fluctuate in BM/TC
separated mode.
7. The number of abnormal downlink EGPRS TBF releases increases

Trouble Ticket BB4D51791

Number
Description After sending data blocks whose final block indicators (FBIs) are set to
1, the BSC uses a high-rate coding scheme to send unacknowledged
data blocks. In this scenario, the number of abnormal downlink EGPRS
TBF releases increases.
Severity Minor
Root Cause When the signal quality deteriorates, if the BSC uses a high-rate coding
scheme to send unacknowledged data blocks, mobile stations (MSs)
may fail to receive the data blocks.
Additionally, after receiving the EGPRS Packet Downlink Ack/Nack
message that indicates a poor signal quality, the BSC cannot decrease
the coding scheme in a timely manner.
Solution After sending data blocks whose FBIs are set to 1, the BSC splits and
resends unacknowledged data blocks.
For example, if the BSC uses MCS6 to send an unacknowledged data
block but MSs fail to receive the data block, the BSC splits the data
block and uses MCS3 to resend it.
NOTE
This problem has been resolved in BSC6900 V900R012C00.
Solution Impact The following table lists the impact of this solution on counters.
Counter Impact
A9305: Number of Downlink EGPRS TBF Increased
Normal Releases
A9306: Number of Downlink EGPRS TBF Decreased
Abnormal Releases due to N3105 Overflow
A9317: Number of Downlink EGPRS TBF Decreased
Abnormal Releases due to Other Cause
RL9325: Retransmission Rate of Downlink Decreased
EGPRS MCS6 RLC Data Blocks
RL9324: Retransmission Rate of Downlink Decreased
EGPRS MCS5 RLC Data Blocks
8. The UDP MUX function cannot take effect on the downlink.


Number DTS2011112100004
Description In A over IP mode, the UDP multiplexing (MUX) function cannot take
effect on the downlink when the Receive UDP MUX Mode parameter is
set to RTPCOMP.
Downlink refers to the direction from the media gateway (MGW) to the BSC.
Severity Minor
Root Cause When the Receive UDP MUX Mode parameter is set to RTPCOMP,
the BSC fills the MUX field with an incorrect value in UDP MUX
packets sent to the MGW. As a result, the negotiation between the BSC
and the MGW fails and the UDP MUX function cannot take effect on
the downlink.
Solution The BSC fills the MUX field with a correct value in UDP MUX packets
sent to the MGW.
9. The counters related to abnormal TBF releases due to CS handovers are incorrectly
measured in DTM mode.


Number
Description The counters related to abnormal TBF releases due to CS handovers are
incorrectly measured in DTM mode.
Severity Suggestion
Root Cause During dual transfer mode (DTM) services, abnormal downlink TBF
releases due to CS handovers are mistakenly counted as abnormal
uplink TBF releases.
Solution The measurement point has been corrected.
Solution Impact After this solution is used:

 The values for the following counters reduce:
 Number of Abnormal Uplink EGPRS TBF Releases due to CS
Handover
 Number of Abnormal Uplink GPRS TBF Releases due to CS
Handover
 The values for the following counters increase:
 Number of Abnormal Downlink EGPRS TBF Releases due to CS
Handover
Number of Abnormal Downlink GPRS TBF Releases due to CS
Handover
10. IP-path-related RTP counters are incorrectly measured.


Number
Description In A over IP mode, if the Enable RTCP parameter is set to ON(Open),

the following IP-path-related RTP counters are incorrectly measured:
Delay Jitter at Local End of IP Path
RTT at Local End of IP Path
Severity Minor
Root Cause Delay Jitter at Local End of IP Path: The measurement unit for this
counter is millisecond (ms) but its calculation precision is 20 ms.
RTT at Local End of IP Path: Only certain sampled values are
measured.
Solution Delay Jitter at Local End of IP Path: The calculation precision of this
counter has been corrected.
RTT at Local End of IP Path: The method for measuring this counter
has been corrected.
5.3 Known Issues

11. The communication between the OMU and host boards is interrupted when a non-
physical-layer fault occurs on the links between the OMU and the SCU boards
Description When a non-physical-layer fault occurs on the links between the OMU
and the SCU boards, the LMT alarm console generates ALM-20223
Communication Between GE Switching Board and OMU Faulty, or the
LMT maintenance panel displays that all boards are faulty or cannot be
detected.
Trigger Condition The OMU or SCU boards experience a hardware failure.
Impact The communication between the OMU and the SCU boards is
occasionally interrupted. As a result, the SCU and other service boards
cannot be maintained.
Severity Minor
Workaround None

Number
Progress A solution is being designed, and the fault will be rectified in later
versions.


V900R014C00SPC200
6.1 What's New

New Features
1. Support for Informing Users that a Configuration Command Does not Take Effect in
Subracks in Non-effective Mode
Description When a configuration command is executed on subracks in
ineffective mode, the command output indicates that the execution
result of this command does not take effect on subracks in ineffective
mode.
Benefit Users can be informed that a configuration command does not take
effect in subracks in non-effective mode.
Implementation The following information has been added to the output of the
configuration command executed on subracks in ineffective mode:
The current subracks xxx are in ineffective mode. The execution of
this command is not effective on subracks in ineffective mode.
Related N/A
Operations
Trouble Ticket CR-GU01048

Number
2. Permanent&Temporary License

Description With this function, customers can have a free trial of temporary
licenses for a certain period of time besides the permanent licenses
they have purchased. If the customers do not purchase temporary
licenses after the free trial ends, the temporary licenses will become
invalid while their permanent licenses remain active.
If this function is used and the configured values of the license
control items TRU which works as Multi transceivers Resource
(per TRX) or Maximum TRX number allowed Resource (per
TRX) is larger than the allowed values, the frequencies and power of
temporarily authorized TRXs cannot be modified, while those of
non-temporarily authorized TRXs can be modified.
Benefit  Using permanent and temporary licenses concurrently reduces the
risk of network service interruption when temporary licenses
expire.
 For versions earlier than the BSC6900 V900R014, if the
configured value of any license control item exceeds the allowed
value, users cannot activate GSM base stations, cells, or TRXs,
and cannot modify parameters and frequencies of the GSM cells.
For the BSC6900 V900R014 or later versions, if the configured
values of the preceding license control items exceed the allowed
values, users can modify the frequencies and power of temporarily
authorized TRXs without changing those of non-temporarily
authorized TRXs.
Implementation  The BSC supports the activation and use of the
permanent&temporary license. When the temporary licenses
become invalid, the BSC automatically withdraws them and uses
only the permanent licenses.
 If the configured values do not exceed the allowed values of the
license control items, users can modify the configuration of any
TRXs, cells, and base stations.
 If the configured values exceed the allowed values, only the
frequencies and power of temporarily authorized TRXs can be
modified when the following conditions are met:
− A permanent&temporary license is used.
− The Limited Mode parameter is set to Limitation on TRXs.
− The configured values of TRU which works as Multi
transceivers Resource (per TRX) or Maximum TRX
number allowed Resource (per TRX) exceeds the allowed
values.
When any of the preceding conditions is not met, Limited Mode
is set to Limitation on System and users cannot use the
following commands:
− ACT BTS
− ACT GCELL
− ACT GTRX
− ADD GCELLFREQ
− MOD GCELL
− RMV GCELLFREQ

Related 1. Run the following command to activate the license file:

Operations ACT LICENSE: FN="license_file.dat";
2. Run the following command to set the license policy:
SET LICPOLICY: RVKMODE=TRX;
3. Run the following commands to identify a temporarily
controlled TRX:
ADD GTRX: IDTYPE=BYID, CELLID=0, TRXID=0,
FREQ=0, ISTMPTRX =YES;
MOD GTRX: IDTYPE=BYID, TRXID=0, ISTMPTRX=YES;
Trouble Ticket GBSC-OR-010
Number
3. SGSN Clock Obtaining Failure Detection for the POUc Board

Description This function enables the BSC6900 to automatically detect whether
the POUc board can successfully extract clock signals from the
SGSN. If the POUc board fails to extract clock signals, an alarm is
generated.
Benefit If the POUc board fails to extract clock signals from the SGSN, PS
services carried by that board will be affected. The reporting of the
alarm helps operators to handle the problem in time.
Implementation The ALM-20212 Clock Reference Source of An Interface Board
Unavailable is reported when the BSC6900 detects that the POUc
board fails to extract clock signals from the SGSN.
Related None.
Operations
Trouble Ticket MBSCV9R14C00-CR-GU00696

Number
4. Support for Hot Patch Status Consistency Check Between the OMU and Host Boards

Description The following mechanisms for hot patch status consistency check
between the OMU and host boards have been added:
1. The BSC6900 automatically checks the hot patch status
consistency once every day.
2. The CMP BRDVER command has been provided for checking
the hot patch status consistency, and the consistency results will be
displayed.
Benefit Users can check patch status consistency.
Implementation 1. The BSC6900 starts a hot patch state consistency check once
every day to compare the number of hot patches and their status on
the host boards with the data recorded in the OMU. If they are
inconsistent, the BSC6900 reports an alarm ALM-20733 Software
Version Inconsistency Between OMU and Host.
2. After the CMP BRDVER command is executed, the BSC6900
compares the number of hot patches and their status on the host
boards with the data recorded in the OMU, and displays the detailed
information in the command output if they are inconsistent.
Related To check the hot patch status consistency, run the CMP BRDVER
Operations command. The following is an example:
CMP BRDVER: SRN=0;
Number
5. Improving the Internal Communication Reliability of DPUs

Description The error packet detection function is enhanced for heartbeat packets
between a DPU core and each DSP on this DPU.
Benefit The internal communication reliability of DPUs is improved. The
average CPU usage of DPUs increases by about 0.3%.
Implementation The DPU core detects heartbeat packets between the DPU core and
each DSP. If an error heartbeat packet is detected, the DPU core
sends the heartbeat packet again.
Related None
Operations
Trouble Ticket None

Number
Feature ID None
6. Support for Checking the Physical Memory and Logical CPU of the OMU Board

Description If the physical memory or logical CPU of the OMU board is faulty,
the ALM-20720 OMU Board Fault is reported. The alarm cause for a
physical memory fault, is "The physical memory capacity does not
comply with OMU specifications." The alarm cause for a logical
CPU fault is "The number of logical CPU does not comply with
OMU specifications."
Benefit If the physical memory or logical CPU of the OMU board is faulty,
users are alerted to replace the faulty OMU board to eliminate the
impact on system capacity.
Implementation The capacity of the physical memory and the number of logical
CPUs are checked. If they do not comply with the OMU
specifications, the ALM-20720 OMU Board Fault is reported to alert
users that the OMU board is faulty.
Related Run the following command to query the capacity of the physical
Operations memory and the number of the logical CPUs:
DSP OMUSRV:;
Number
Feature ID None
7. Support for Verification of OMU IP Addresses

Description OMU IP addresses are verified. If they are incorrect, the ALM-20721
OMU IP Address Configuration Error is reported.
Benefit OMU IP addresses are incorrect, the OMU external and internal
networks are disconnected or the data synchronization between the
active and standby OMUs fails.
This function detects OMU IP address errors. Once an error is
detected, the alarm is reported, prompting users to correct the OMU
IP addresses.
Implementation OMU IP addresses are verified every 5 minutes. If they are incorrect,
the alarm is reported.
Related If the alarm is reported, clear it following the online help.
Operations Run the DSP OMU command to query the OMU IP addresses.
For details on the OMU IP addresses, see section "Changing IP
Addresses and Masks of the OMU Ethernet Adapters" in the
BSC6900 OMU Administration Guide.
Trouble Ticket None
Number
Feature ID None
8. Support for Checking for Weak OMU Passwords

Description The OMU password policy is optimized by adding the function of

checking for weak OMU passwords.
Benefit The optimized OMU password policy enhances user account security
by requiring users to employ strong passwords.
Implementation A weak password dictionary has been added to the OMU software.
When a user creates a password for a new account or modifies an old
password, the OMU checks whether the new password is included in
the weak password dictionary. If so, a message "You cannot use
common words included in the weak password dictionary." is
displayed on the LMT or M2000. The user can continue with the
operation only after they enter a password that is not included in the
weak password dictionary.
Related To enable the function of checking for weak OMU passwords, run
Operations the following command:
SET PWDPOLICY: DICTCHKSW=ON;
This function is disabled by default.
Number
9. Specifying a Data Port Range for the FTP Server (for M2000)

Description 1. When connecting an FTP client to an FTP server, users can set
ServerIP to 0.0.0.0 to match all server IP addresses.
2. Users can specify the data port range for the FTP server in passive
mode.
3. The mechanism for specifying a port for the FTP server to listen to
has been changed.
Benefit 1. As there are a large number of OSS FTP servers, configuring
destination ports on the FTP servers one by one based on host IP
addresses is very time-consuming. Because most FTP servers have
the same destination port, users can configure destination ports on
such servers at a time by setting ServerIP to 0.0.0.0 (matching all IP
addresses) and Port to the number of the desired destination port.
This helps users quickly configure destination ports and deploy the
security policy.
2. Users can now specify the data port range for the FTP server in
passive mode to deploy the security policy.
3. The mechanism for specifying a port for the FTP server to listen to
has been changed, meeting security requirements.
Implementation 1. Users can run the ADD FTPSCLTDPORT command to set
ServerIP to 0.0.0.0 to match all server IP addresses.
2. Users can run the SET FTPSSRV command to specify the data
port range for the FTP server in passive mode.
 The SET FTPSRVPORT command is deleted.
 The LST FTPSRVPORT command is deleted.
 The ACDPORTLWLT and ACDPORTUPLT parameters are
added to the SET FTPSSRV command, specifying the lower and
upper limits of the data port range for the FTP server in passive
mode, respectively.
 After users run the LST FTPSSRV command, the lower and upper
limits of the data port range for the FTP server in passive mode are
displayed.
3. If users specify a port for the FTP server to listen to before the
mechanism is changed, the external and internal networks listen to
both the default port (port 21) and the user-defined port. If users
specify a port for the FTP server to listen to after the mechanism is
changed, the external network listens only to the user-defined port
and the internal network listens only to the default port (port 21). In
addition, after users change the listening port, the change takes effect
immediately. Users no longer need to restart the FTP server for the
change to take effect.
Related 1. Run the following command to add the information about the FTP
Operations server. In this example, set ServerIP to 0.0.0.0 and Port to 8021.
ADD FTPSCLTDPORT: ServerIP="0.0.0.0", Port= 8021;
2. Run the following command to specify the data port range for the
FTP server in passive mode:
SET FTPSSRV:
DFTPORTSWT=DEFAULTPORT,ACDPORTLWLT=25001,
ACDPORTUPLT=30000;

3. Run the following command to configure the listening port of the

FTP server:
SET FTPSSRV: DFTPORTSWT=CUSTOMPORT,
SRVCMDPORT=9021, SRVDATAPORT=9020;
Trouble Ticket OR-353
Number
10. Support for Filtering Events with Special Alarm Flag on the M2000
Description If an NE is set to work in maintenance mode, events from this NE
will include a field Special Alarm Flag to indicate the maintenance
mode of the NE. The events with this field can be filtered on the
M2000.
Benefit Events from NEs working in maintenance mode can be filtered on
the M2000. This improves the efficiency for users to observe the
events from NEs working in normal mode.
Implementation If an NE works in maintenance mode, the field Special Alarm Flag
will be included in the event from this NE.
Related To query all the events from NEs working in maintenance mode, run
Operations the following command:
LST ALMLOG: ALMTP=evt, SPCALMFLG=ALL_SPECIAL;
Trouble Ticket N/A
Number
11. New Self-healing Switch for Abnormal Active-OMU Resets

Description Without this function:

If the abnormal active-OMU reset takes no more than 5 minutes, the
self-healing operation is not performed no matter how many times
the OMU is reset.
With this function:
If the abnormal active-OMU reset that takes no more than 5 minutes
occurs 3 times within 24 hours, the active and standby OMUs are
switched over.
Benefit When the number of consecutive abnormal OMU resets reaches 3
within 24 hours, the active and standby OMUs are switched over to
prevent OMU service interruption.
Implementation A new parameter Self-healing Switch for Abnormal Active-OMU
Reset has been added to the SET SLFSLVSW command. This
parameter specifies whether to enable this function.
The standby OMU checks whether the active OMU is reset
abnormally. When the following conditions are met, the standby
OMU sends a switchover request to the active OMU and the active
OMU will initiate a switchover.
The parameters Self-healing Switch and Self-healing Switch for
Abnormal Active-OMU Reset are set to ON in the SET SLFSLVSW
command.
The standby OMU detects that the active OMU has been abnormally
reset 3 times within 24 hours.
The requirements for switching over the active and standby OMUs
are met.
Related Run the following command to enable this function:
Operations SET SLFSLVSW: SWITCH=ON, RSW=ON;
Run the following command to query the status of the self-healing
switch for abnormal active-OMU reset:
LST SLFSLVSW:;
Run the following command to disable this function:
SET SLFSLVSW: SWITCH=ON, RSW=OFF;
Number
Feature ID None
12. Support for Fault Management

Description This feature is used to quickly locate the following faults: RRC
connection setup faults, CS service setup faults, PS service setup
faults, paging faults, and a large number of unavailable cells. The
LMT analyzes the counters, alarms, and logs of a problem site by
following the diagnosis rules, and then sends a query result to users
to quickly clear faults.
Benefit The time for rectifying a fault is reduced, therefore shortening the
service interruption time.
Implementation The Fault Management Assistant tool is installed on the OMU.
Related To enable the feature, do as follows:

Operations 1.On the LMT, click Device Maintenance. The Device
Maintenance tab page is displayed.
2.On the BSC Maintenance tab page, click BSC Maintenance and
double-click Fault Management Assistant. The Fault Management
Assistant dialog box is displayed.
3.Select a fault scenario in the displayed dialog box.
4.Click Start and wait for the query result.
The query results are as follows:
 If the operation is successful, the query result is shown in a new
webpage. Choose Page > Save on the tool bar to save the query
result as a local file.
The query result includes the following items:
− Trend chart of the KPIs and counters
Each KPI or counter has three curves, representing three 8-hour
periods: the past 8 hours, the 8-hour period that ended 24 hours
ago, and the 8-hour period that ended 7 days ago.
The X-coordinate represents the time measurement (in
minutes); the left Y-coordinate represents the counters (in the
unit of each counter), and the right Y-coordinate represents the
KPIs (in percentage).
− KPIs
− Fault causes
− Suggestions for rectifying faults
− Operation logs
 If the operation fails, a dialog box is displayed with the failure
cause.
Trouble Ticket None
Number
13. Software Integrity Protection

Description The RNC now checks the OMU software integrity periodically and
reports an alarm if any OMU software file is lost or damaged.
Benefit The OMU software files may be lost or damaged because of power
failure or manual deletion. As a result, some of the OMU functions
may be disabled or the OMU board cannot be loaded.
With this function, OMU software integrity is checked and users are
prompted to restore the lost or damaged OMU software files.
Implementatio The OMU software integrity is checked once every 12 hours, and the
n ALM-20723 File Loss or Damage is reported if any file is lost or
damaged.
Related If the alarm is reported, clear it by referring to the online help.
Operations
Trouble Ticket MBSC-OR-122

Number
14. Support for the FTP Client Authenticating the FTP Server
Description The FTP client now can authenticate the FTP server when they both
are using the SSL encryption mode for transmission.
Benefit The FTP connection security is enhanced.
Implementation The FTP client authenticates the FTP server by using the root
certificate issued by the M2000.
Related The SSLCERTAUTH parameter has been added to the SET
Operations FTPSCLT command. This parameter specifies whether to enable the
FTP client to authenticate the FTP server.
To enable the FTP client to authenticate the FTP server, run the
following command:
SET FTPSCLT: ENCRYMODE=ENCRYPTED,
SSLCERTAUTH=YES;
Note: Related certificates must be configured on the M2000.
Number
15. SSL Encryption Function Supported by the Tool for Preparing Data on the USB Storage
Device and Upgrade Tool

Description The tool for preparing data on the USB storage device can now be
connected to the BSC in SSL-encrypted mode and the upgrade tool
can now upgrade the BSC in SSL-encrypted mode.
Benefit The compatibility and security of the tool for preparing data on the
USB storage device and the upgrade tool are improved.
Implementation An interface is displayed for users to select a secure transmission
type when using the tool for preparing data on the USB storage
device or the upgrade tool.
Related 1. Before using the tool for preparing data on the USB storage device
Operations or the upgrade tool, log in to the LMT and run the LST SSLCONF
command to obtain the secure transmission information of the BSC
to be upgraded.
2. Select the required secure transmission type on the Add NE
Dialog Box of the tool for preparing data on the USB storage device
or on the Input Step 1 window of the upgrade tool client.
Number
16. Support for Setting the IEEE 802.1ag Standard Version Used by the Ethernet Ports on
the BSC6900

Description This feature uses MML commands to modify the IEEE 802.1ag
standard version used by the Ethernet ports on the BSC6900. After
the default version of the IEEE 802.1ag standard has been rectified,
the BSC6900 can be properly connected to the packet transport
network (PTN).
Benefit The default version of the IEEE 802.1ag standard supported by the
Ethernet ports on a newly deployed BSC6900 can be rectified to
enable the BSC6900 and the PTN to interconnect.
Users can set the version of the IEEE 802.1ag standard supported by
the Ethernet ports that use the TRUNK mode so that the BSC6900
can interconnect with the peer equipment.
Implementation The default value of the CFMVER parameter in the SET
ETHPORT command has been changed from V7 to V8.
The default value of the CFMVER parameter in the ADD
ETHTRK command has been changed from V7 to V8.
The MOD ETHTRK command has been added. It is used to set the
CFMVER parameter.
Related For an Ethernet port on a newly added FG2c, GOUc, FG2d, GOUd,
Operations FG2a, or GOUa board, perform the following operations:
 To query the value of the CFMVER parameter, run the LST
ETHPORT command. The following is an example:
LST ETHPORT: SRN=0, SN=18, PN=0;
 To change the value of the CFMVER parameter, run the SET
ETHPORT command. The following is an example:
SET ETHPORT: SRN=2, SN=26, BRDTYPE=FG2a, PTYPE=FE,
PN=0, CFMVER=V8;
For an Ethernet port that has been added into a link aggregation
group (LAG), perform the following operations:
 To change the value of the CFMVER parameter to V8, run the
ADD ETHTRK command. The following is an example:
ADD ETHTRK: SRN=0, SN=20, TRKN=0,
WORKMODE=LOAD_SHARING, LACPMODE=STATIC_LACP,
FLOWCTRLSWITCH=ON, CFMVER=V8;
 To query the value of the CFMVER parameter, run the LST
ETHTRK command. The following is an example:
LST ETHTRK: SRN=0, SN=20, TRKN=0;
 To change the value of the CFMVER parameter, run the MOD
ETHTRK command. The following is an example:
MOD ETHTRK: SRN=0, SN=20, TRKN=0, CFMVER=V8;
Number
17. Support for Querying APR Packets

Description Address Resolution Protocol (ARP) packets are important control

messages over Ethernet ports that may affect the operation of
Ethernet ports. ARP packets are also broadcast packets at the data
link layer. They are prone to broadcast storms and may carry an
incorrect Media Access Control (MAC) address to the BSC.
Generally, ARP problems are located and analyzed by capturing ARP
packets.
This feature provides the function of querying ARP packets by using
man-machine language (MML) commands, an easy method of
locating and analyzing ARP problems.
Benefit Using MML commands to query ARP packets makes it easy to
locate ARP-related problems.
Implementation 1. Running the new STR ARPPKTCAPTURE command starts the
ARP packet capture process. The received and transmitted ARP
packets are saved into corresponding queues by running this
command.
2. Running the new STP ARPPKTCAPTURE command stops the
ARP packet capture process. After this command is executed, ARP
packets are not saved any more.
3. Running the new DSP ARPPKTCAPTURE command queries
the captured ARP packets. The ARP packets are obtained from
corresponding queues by running this command.
Related 1. Run the STR ARPPKTCAPTURE command to start capturing
Operations ARP packets.
2. Run the STP ARPPKTCAPTURE command to stop capturing
ARP packets.
3. Run the DSP ARPPKTCAPTURE command to query the
captured ARP packets.
Trouble Ticket None
Number
Feature ID GBFD-118601/GBFD-118602/GBFD-118603
18. Support for Built-in Firewalls

Description This feature increases the security capabilities of FG2c, FG2d,

GOUc and GOUd boards and the maintainability of built-in
firewalls.
This feature increases the security capabilities of FG2c, FG2d,
GOUc and GOUd boards as follows:
 Adds protection against gratuitous ARP-spoofing attacks.
 Enhances flow control on the packets transmitted over the FG2c,
FG2d, GOUc and GOUd boards.
This feature increases the maintainability of built-in firewalls as
follows:
 Improves the mechanism for reporting the ALM-21388 Invalid
Packets Exceeding Alarm.
 Adds a mechanism for measuring packets transmitted over the
FG2c, FG2d, GOUc and GOUd boards.
Benefit  When being attacked by gratuitous ARP spoofing, the BSC reports
the ALM-21391 ARP Conflict.
 The flow control on the packets transmitted over the FG2c, FG2d,
GOUc and GOUd boards is improved to prevent conflicts between
different ports or between different types of packets in the same
priority queue.
 The mechanism for reporting the ALM-21388 Invalid Packets
Exceeding Alarm is also improved.
 Users can query statistics about the packets transmitted over a port
on an FG2c, FG2d, GOUc or GOUd board or over the entire
board.
Implementation 1. The ARPANTICHEATSW parameter, which specifies the switch
for protection against gratuitous ARP-spoofing attacks, has been
added to the SET IPGUARD command, and the ALM-21391 ARP
Conflict has been added. If ARPANTICHEATSW is set to ON, the
BSC reports the ALM-21391 ARP Conflict when being attacked by
ARP spoofing.
2. Flow control is enhanced to prevent conflicts between different
ports or between different types of packets.
3. To improve the mechanism for reporting the ALM-21388 Invalid
Packets Exceeding Alarm, the following parameters are added to the
SET IPGUARD command:
 INVALIDMCASTALMSW, INVALIDMCASTALMTHD, and
INVALIDMCASTALMRTHD
 ICMPALMSW, ICMPALMTHD, and ICMPALMRTHD
These parameters are added to provide protection against various
types of invalid packets and to modify invalid packet alarm
thresholds. In addition, the PN parameter is added to the SET
IPGUARD command to specify the port protected against invalid
packets.
4. The DSP ETHSTAT and DSP IPSTAT commands are added to
query the statistics about the packets transmitted over a port on an
FG2c, FG2d, GOUc or GOUd board or over the entire board.
Related 1.To enable the protection against gratuitous ARP-spoofing attacks,

Operations run the SET IPGUARD command with ARPANTICHEATSW set

to ON. The following is an example:
SET IPGUARD: SRN=2, SN=24, BRDTYPE=FG2c,
ARPANTICHEATSW=ON;
2.To enable the protection against invalid packets. The following is
an example:
INVALIDMCASTALMSW=ON, INVALIDMCASTALMTHD=512,
INVALIDMCASTALMRTHD=256, ICMPALMSW=ON,
ICMPALMTHD=512, ICMPALMRTHD=256;
3.To query statistics about the packets transmitted over a port on an
FG2c or GOUc board, run the DSP ETHSTAT command. The
DSP ETHSTAT: SRN=2, SN=24, PN=2;
4.To query statistics about the packets transmitted over an FG2c or
GOUc board, run the DSP IPSTAT command. The following is an
example:
DSP IPSTAT: SRN=2, SN=24;
Trouble Ticket OR-224
Number
19. Support for Querying the Route based on the Source IP Address

Description The source route function has been added to the FG2c, GOUc, FG2d
and GOUd boards, enabling these two boards to query the route used
for transmission based on the source IP address of a data packet.
The source IP address can be an ETHIP, ETHTRKIP, or DEVIP.
When the source IP address is an ETHIP or ETHTRKIP, only one
port on the FG2c, GOUc, FG2d or GOUd board can be configured as
the outgoing port. When the source IP address is a DEVIP, two ports,
one active and the other standby, can be configured as the outgoing
ports.
Benefit This function simplifies route configuration in the scenario where the
BSC6900 uses one IP address to communicate with multiple peer
devices over one transmission path. In such a scenario, only one
route based on the source IP address is required.
Implementation 1. New commands ADD SRCIPRT, DSP SRCIPRT, MOD
SRCIPRT, and RMV SRCIPRT have been added. Operators can
use these commands to set a route based on the source IP address by
setting the source IP address and next hop IP address.
2. When the source IP address is an ETHIP or ETHTRKIP, operators
can specify only one next hop IP address, and the next hop IP
address must be on the same network segment as the source IP
address.
3. When the source IP address is a DEVIP, operators can specify two
next hop IP addresses, one active and the other standby.
4. The two next hop IP addresses must be the existing next hop IP
addresses configured on a route based on an Ethernet IP address or
Ethernet trunk IP address. Of the two next hop IP addresses, the
active one must be specified, and the standby one is specified only
when the STANDBYNEXTHOPSWITCH parameter is set to YES.
By default, the active next hop IP address is used.
5. The standby next hop IP address is used only when the active next
hop outgoing port is faulty. When the active next hop outgoing port
is recovered, the BSC6900 will wait 30 seconds and then switch over
services to the active next hop outgoing port.
Related Run the following commands to add an Ethernet IP address, an
Operations Ethernet trunk IP address, and two device IP addresses:
ADD ETHIP: SRN=1, SN=24, PN=0, IPINDEX=0,
IPADDR="1.1.1.1", MASK="255.255.255.0";
ADD ETHTRKIP: SRN=1, SN=24, TRKN=0, IPINDEX=0,
IPADDR="2.2.2.2", MASK="255.255.255.0";
ADD DEVIP: SRN=1, SN=24, DEVTYPE=LOGIC_IP,
IPADDR="3.3.3.3";
IPADDR="4.4.4.4";
Run the following commands to set routes based on the preceding
Ethernet IP address and Ethernet trunk IP address:
ADD SRCIPRT: SRN=1, SN=24, IPTYPE=ETHIP,
SRCIPADDR="1.1.1.1", NEXTHOP="1.1.1.2";
ADD SRCIPRT: SRN=1, SN=24, IPTYPE=ETHTRKIP,

Run the following command to set a route based on a preceding

device IP address with the outgoing port set to an Ethernet port:
ADD SRCIPRT: SRN=1, SN=24, IPTYPE=DEVIP,
SRCIPADDR="3.3.3.3", NEXTHOP="1.1.1.2",
STANDBYNEXTHOPSWITCH=NO;
Run the following command to set a route based on the other device
IP address with the outgoing port set to a trunk group:
STANDBYNEXTHOPSWITCH=NO;
Run the following command to check whether the route is
configured for the IP address 1.1.1.1 on the board in slot 24 subrack
1:
DSP SRCIPRT: SRN=1, SN=24, SRCIPADDR="1.1.1.1";
Trouble Ticket N/A
Number
20. Support for Manual Clearing of Dynamic ARP Entries

Description Dynamic ARP entries can be manually cleared in the following
ways:
 Clearing all the dynamic ARP entries learnt by a port
 Clearing the dynamic ARP entry corresponding to an IP address
With this function, users can clear incorrect dynamic ARP entries on
the BSC6900 when there is an exception on a BSC6900 interface
board or the interconnected transmission equipment of the board.
Then, the BSC6900 can learn the ARP entries again without waiting
for 20 minutes (ARP table aging time).
Benefit The O&M performance is enhanced.
Implementation The CLR ARP command has been added. The CLRTYPE
parameter, which indicates whether to clear ARP entries by port or
by IP address, has been added to this command.
Related 1.To clear ARP entries by port, run the CLR ARP command. The
Operations following is an example:
CLR ARP: SRN=0, SN=14, CLRTYPE=CLRPORT,
PORTTYPE=ETHER, PN=2;
2.To clear ARP entries by IP address, run the CLR ARP command.
CLR ARP: SRN=0, SN=14, CLRTYPE=CLRIP,
IPADDR="11.11.11.2";
Number

21. Support for Real-time BER Monitoring

Description This feature enables users to view the bit error rate (BER) on an
E1/T1 port in real time. This helps to quickly locate transmission
problems on the E1/T1 link.
Benefit Without this feature, users can only view bit error seconds on the
LMT in real time and perform BER monitoring in E1/T1 loopback
scenarios. With this feature, users can view the BER of E1/T1 links
in real time.
Implementation A BER curve is displayed after bit error second monitoring is started
on the LMT. The BER is calculated based on the number of error
frames on the E1/T1 link and the number of CRC failures.
Related None
Operations

Number
22. Support for Cross Connection Detection Between a BSC and a Transmission Device
When They Work in MSP Mode

Description This feature enables the BSC to detect optical fiber cross connections
of the protection channels and working channels between the BSC
and a transmission device (for example, OSN), which work in
Multiplex Section Protection (MSP) mode. The following figure
shows the correct connection:
This feature detects cross connections in the following scenarios:

The TX and RX working channel ports on the BSC are connected to
the RX and TX protection channel ports on the OSN. The TX and RX
protection channel ports on the BSC are connected to the RX and TX
working channel ports on the OSN.
The TX working channel port on the BSC is connected to the RX

protection channel port on the OSN. The TX protection channel port
on the BSC is connected to the RX working channel port on the OSN.
The RX working channel port on the BSC is connected to the TX

protection channel port on the OSN. The RX protection channel port
on the BSC is connected to the TX working channel port on the OSN.

Benefit This feature prevents service interruption due to cross connections.
Implementation After this feature is enabled, the BSC sends SDH frames with the
MS-AIS field over the standby optical port and determines whether
the connections are correct based on received frames.
Related Run the CHK OPTCRS command to detect optical fiber cross
Operations connections. The following uses port 3 on the board in slot 16 of
subrack 0 as an example:
CHK OPTCRS: SRN=0, SN=16, PN=3;
The output is as follows:
Check OPT Cross Connection
--------------------------
Subrack No. = 1
Slot No. = 22
Port No. = 0
Check Result = loopback
(Number of results = 1)
Number
23. Configurable VLAN Priority and DSCP

Description The Virtual Local Area Network (VLAN) priority indicates the
priority of a packet at the data link layer. The Differentiated Services
Code Point (DSCP) is a field in an IP packet that indicates the
service level of the packet. If a router filters packets based on the
VLAN priority or DSCP, and the VLAN priority or DSCP value of a
packet is lower than the VLAN priority or DSCP value specified in
the router, the router will discard the packet.
In BSC6900 V900R013C00SPC500, the following types of packets
use fixed VLAN priorities:
Address Resolution Protocol (ARP) packets
IEEE 802.1ag Ethernet OAM packets
OAM is short for Operations, Administration, and Maintenance.
In addition, the following types of packets use fixed DSCP values:
Dynamic Host Configuration Protocol (DHCP) packets
Bidirectional Forwarding Detection (BFD) packets
Trace Route packets
If the fixed VLAN priorities or DSCP values of the packets are
relatively low, the packets are probably discarded by the router.
In BSC6900 V900R014C00SPC200, associated parameters have
been added so that users can customize the VLAN priority and
DSCP value of packets.
Benefit Users can customize the VLAN priority and DSCP value of packets.
Implementation The fixed VLAN priority and DSCP value are invalidated.
The VLANPRI and ARPVLANPRI parameters have been added for
specifying the VLAN priority. The DSCP parameter has been added
for specifying the DSCP value.
Related To set the VLAN priority and DSCP value, perform the following
Operations operations on the BSC6900 LMT:
 To set the VLAN priority of IEEE 802.1ag Ethernet OAM packets,
run the ADD CFMMA command with the VLANPRI parameter
set to an appropriate value. The following is an example:
ADD CFMMA: SRN=2, SN=24, MDIDX=0, VLANID=24,
MAIDX=0, MANAME="ma0", VLANPRI=4;
 To set the DSCP value of Trace Route packets, run the TRC
IPADDR command with the DSCP parameter set to an
appropriate value. The following is an example:
TRC IPADDR: SRN=2, SN=24, DESTIP="23.23.23.2",
DSCP=30;
 To set the DSCP value of BFD packets, run the STR IPCHK
command with the DSCP parameter set to an appropriate value.
STR IPCHK: SRN=2, SN=24, CHKTYPE=SBFD,
CARRYT=ETHPORT, PN=3,
MODE=CHECK_ON_PRIMARY_PORT,
PEERIP="23.23.23.2", WHETHERAFFECTSWAP=NO,
DSCP=50;
 To set the DSCP value of DHCP packets and the VLAN priority of

ARP packets, run the SET INTBRDPARA command with the

DSCP and ARPVLANPRI parameters set to appropriate values.
SET INTBRDPARA: SRN=2, SN=24, BT=FG2c,
DHCPDSCP=30, ARPVLANPRI=7;
Number
Feature ID None
24. 5-Minute Measurement of the Highest Transmit and Receive Rates in the Transport
Network

Description The following counters have been added:

VS.IPPATH.IPLAYER.FIVE.MINUTES.PEAK.TXRATE:
Maximum Transmit Rate of an IP Path at the IP Layer (5-Minute)
VS.IPPATH.IPLAYER.FIVE.MINUTES.PEAK.RXRATE:
Maximum Receive Rate of an IP Path at the IP Layer (5-Minute)
VS.FEGE.FIVE.MINUTES.RXMAXSPEED: Highest Receive Rate
of the FEGE Ethernet Port (5-Minute)
VS.FEGE.FIVE.MINUTES.TXMAXSPEED: Highest Transmit Rate
of the FEGE Ethernet Port (5-Minute)
VS.LGCPRT.FIVE.MINUTES.PEAK.TXRATE: Maximum
Transmit Rate of Logical Port (5-Minute)
Benefit Users can query the highest transmit and receive rates sampled every
5 minutes within a specified measurement period.
Implementation The preceding counters are measured as follows:
1. Within a specified measurement period, the BSC6900 measures
the number of transmitted and received bytes every 5 seconds and
accumulates the number of bytes at the end of every 5-minute
sampling period to obtain the total number of bytes transmitted or
received within the sampling period.
2. The BSC6900 calculates the transmit and receive rate within every
5-minute sampling period with the following formula:
Transmit and receive rate within a 5-minute sampling period = Total
number of bytes transmitted and received within a 5-minute
sampling period/300
3. The BSC6900 compares all of the collected transmit and receive
rates to obtain the highest transmit and receive rate within the
specified measurement period, which is the value of the
corresponding counter.
Related None
Operations
Trouble Ticket CR-2198

Number
25. Support for the ALM-21522 Low SCCP Connection Setup Success Rate

Description If the SCCP connection setup success rate is smaller than the value
of Threshold of Low SCCP Setup Success Rate and the number of
Connection Request (CR) messages is larger than the value of
Minimum number of CR, the alarm ALM-21522 Low SCCP
Connection Setup Success Rate is reported.
Benefit This alarm warns users if service setups fail due to incorrect
configurations, transmission congestion, or congestion on the peer
equipment.
Implementation Each SPU subsystem calculates the number of CR messages sent and
Connection Confirmed (CC) messages received by each destination
signaling point (DSP) every 5 minutes. This alarm is reported when
the following conditions are met for two consecutive periods:
The number of CR messages sent by a DSP is larger than the value
of Minimum number of CR.
The ratio of CC to CR is smaller than the value of Threshold of
Low SCCP Setup Success Rate.
Related Run the SET TNSOFTPARA command and set Minimum number
Operations of CR and Threshold of Low SCCP Setup Success Rate. The
following is shown as an example:
SET TNSOFTPARA: CRMinNum=100, CCCRRatioThrd=80;
To query the setting of Minimum number of CR and Threshold of
Low SCCP Setup Success Rate, run the following command:
LST TNSOFTPARA: LstFormat=VERTICAL;
Number
Feature ID None
26. CPU Load Balancing Among MPU Subsystems

Description In versions earlier than BSC6900V900R014, transmission resources

are assigned to a base station by an MPU subsystem through an
interface board. The interface board is bound to the MPU subsystem.
In BSC6900V900R014, transmission resources are assigned to a
base station by an MPU subsystem through a CPU for Service
(CPUS) subsystem. Each CPUS subsystem is bound to an MPU
subsystem and manages the control-plane resources of several base
stations. If the BSC6900 uses IP transmission and the CPU load
balancing function is enabled, another MPU subsystem in the
BSC6900 will alternatively assign transmission resources when the
CPU load of the MPU subsystem reaches the load balancing
threshold.
Benefit When the CPU load of all MPU subsystems in the BSC6900 reaches
or exceeds the load balancing threshold, more MPU subsystems can
be added to reduce the CPU load of the existing MPU subsystems.
In versions earlier than BSC6900V900R014, the CPU load of an
MPU subsystem is distributed among the interface boards bound to
the MPU subsystem.
In BSC6900V900R014, the CPU load of an MPU subsystem is
distributed among the CPUS subsystems bound to the MPU
subsystem. In the BSC6900, the number of CPUS subsystems is
always larger than the number of interface boards. Also, the CPUS
subsystems are more evenly bound to MPU subsystems than the
interface boards.
Therefore, after an upgrade to BSC6900V900R014, the CPU load of
MPU subsystems is better balanced in the scenario where traffic load
is evenly distributed among the base stations that are managed by the
MPU subsystems.
After the CPU load balancing among MPU subsystem is enabled, the
CPU load of a multi-core interface board (AOUc, POUc, UOIc,
FG2c, or GOUc) increases by 3%.
If a maximum of 24 MPU subsystems are configured in the
BSC6900V900R014, the CPU load of each MPU subsystem
increases by 2% when there is no traffic compared with the same
configuration in the BSC6900 of an earlier version.
However, in BSC6900V900R014, the CPU load caused by a single
user is less than that in an earlier version. Therefore,
BSC6900V900R014 outperforms its earlier versions when the
average CPU load of the MPU subsystems is equal to or higher than
40%.
If only one SPU board is configured with an MPU subsystem, the
CPU usage of the MPU subsystem increases by about 3% after the
BSC6900 is upgraded to BSC6900V900R014. However, this
increase does not have any significant impact on the BSC6900
capacity, MPU performance is not a system bottleneck.
Implementation Transmission resources are preferentially assigned to a base station
by an MPU subsystem through a CPUS subsystem. Each CPUS
subsystem is bound to an MPU subsystem and manages the control-
plane resources of several base stations.
The MPU Load Sharing Threshold and MPU Load Difference
Threshold parameters are added. If the user plane uses IP

transmission, the BSC6900 checks the CPU load of each MPU

subsystem before transmission resources are assigned. The BSC6900
selects another MPU subsystem to assign transmission resources for
the base station when both the following conditions are met:
− The maximum CPU load among all MPU subsystems is larger
than the value for MPU Load Sharing Threshold.
− The difference between the maximum and minimum CPU load
in the MPU subsystem exceeds MPU Load Difference
Threshold.
After an upgrade to BSC6900V900R014, the load balancing
threshold of the BSC6900 is set to 75% by default. The default
threshold can be decreased to trigger the CPU load balancing process
more easily to better balance the CPU load.
Related To specify the load balancing threshold and load difference
Operations threshold, run the SET TNLOADBALANCEPARA command. The
SET TNLOADBALANCEPARA: MPULOADSHARETH=40,
MPULOADDIFFTH=10;
Trouble Ticket IR-RAN14.0-019-SR-01-AR-01
Number
27. Support for a new parameter GTP-U+BSSGP Parameter Transport Mode

Feature When the CN supports service type identification, this function

Description enables the BSC to interpret service types contained in GTP-U and
BSSGP packets. This function, requested by China Mobile, helps
make efficient use of radio resources.
Improvement This function helps the BSC make efficient use of radio resources
by dynamically adjusting radio resources based on service types
that are identified by the CN.
Implementati After identifying a service type, the GGSN adds the service type to
on the extension field of a GTP-U packet header. Then, the GGSN
sends this GTP-U packet to the SGSN.
The SGSN adds this service type to the extension field of a BSSGP
packet header after successfully interpreting the service type. Then,
the SGSN sends this BSSGP packet to the BSC.
After receiving the BSSGP packet, the BSC interprets the service
type contained in the extension field of the BSSGP packet header.
Then, the BSC dynamically allocates radio resources based on the
interpreted service type.
Currently, only QQ services are supported.
Related Run the SET GCELLGPRS command with Support DPI set to
Operations SUPPORT(GGSN Support) and DPI Parameter Transport
Mode set to GTP-U+BSSGP(GTP-U+BSSGP).
PR Number FF-034
Feature ID N/A
28. Support for synchronization and Co-BCCH between BTS3900 and BTS3012

Feature To meet the requirements for smooth upgrade from

Description BTS3012/BTS3012AE/BTS3012II to
BTS3900/BTS3036/BTS3900A/BTS3036A/DBS3900/DBS3036/
BTS3900L, this function supports co-site between
BTS3012/BTS3012AE/BTS3012II and
BTS3900L. The base stations share a site and antenna in terms of
hardware, support inter-BTS cells in terms of services, and
remain two independent sites in terms of configuration and
maintenance.
The following groups of base stations can be enabled with co-
site:
 BTS3012 + BTS3900 (or BTS3036)
 BTS3012II + BTS3900 (or BTS3036)
 BTS3012AE + BTS3900A (or BTS3036A)
 BTS3012AE + DBS3900 (or DBS3036)
 BTS3012 + DBS3900 (or DBS3036)
 BTS3012II + DBS3900 (or DBS3036)
 BTS3012 + BTS3900L
 BTS3012II + BTS3900L
Improvement BTS3012/BTS3012AE/BTS3012II can be upgraded to
BTS3900L smoothly.
Implementation A BTS3012_SRAN cabinet is added to BTS3012,
BTS3012AE_SRAN cabinet to BTS3012AE, and
BTS3012II_SRAN cabinet to BTS3012II.
This feature is implemented in terms of hardware in the

following ways:
A BBU subrack (including a UCIU board) and GRFU or MRFU
boards are added to the new cabinet of
BTS3012/BTS3012AE/BTS3012II.
BTS3900L has an independent BTS3900 cabinet. Therefore, a
BBU subrack is not installed in a
BTS3012_SRAN/BTS3012AE_SRAN/BTS3012II_SRAN
cabinet.
Co-site is enabled on the local maintenance terminal (LMT) in

the following ways: The cabinet type of
BTS3012/BTS3012AE/BTS3012II is changed to new type, and a
BBU subrack (including a UCIU board) and GRFU or MRFU
boards are added to
BTS3900L.
Related New commands are added: ADD BTSGRP, RMV BTSGRP, LST
Operations BTSGRP, and SET BTS3012SRANMODE.
The alarms ALM-21806 BTS Not Support Configured Function

and ALM-21801 GSM Cell out of Service are modified.

Co-site between the existing BTS3012 and the added BTS3900 is
used as an example for the co-site of the
BTS3012/BTS3012AE/BTS3012 II and the
BTS3900L.
Run the SET BTS3012SRANMODE command to set the
BTS3012 to a normalized base station and change its cabinet
type.
Run the ADD BTS command to add a BTS3900 that supports
normalized mode.
Run the ADD BTSCABINET command to add a BTS3900
cabinet.
If the BTS3900 and the BTS3012 shares a cabinet, then a
BTS3012_SRAN/BTS3012AE_SRAN/BTS3012II_SRAN
cabinet is configured.
If the BTS3900 uses an independent cabinet, then a BTS3900
cabinet is configured on the basis of the physical cabinet type.
Run the ADD BTSBRD command to add a UCIU board to the
BTS3900 so that the BTS3900 clock is synchronized with the
BTS3012 clock.
Run the ADD BTSGRP command to configure the BTS3012 and
BTS3900 as a co-site group.
Run the ADD CELLBIND2BTS command to bind the BTS3012
cells to the BTS3900 so that they are inter-site cells.
Run the ADD GRTX command to configure TRXs for the inter-
site cells.
Run the ADD TRXBIND2PHYBRD command to bind the
TRXs to the BTS3900.
PR Number FF-001
Feature ID N/A
29. Support for the U-TDOA positioning method over the Lb interface

Description In addition to CELL ID+TA and A-GPS, the feature Lb Interface enables
the BSC to support a new positioning method: Uplink Time Difference
of Arrival (U-TDOA).
Improvement U-TDOA is more precise than CELL ID+TA and supports more
subscribers than A-GPS.
Without introduction of this feature, Huawei BSS supports CELL ID+TA
and A-GPS. However, CELL ID+TA cannot meet operators'
requirements for precise positioning. A-GPS is the most precise, but is
available only to GPS-capable MSs.
With this feature, U-TDOA meets operators' requirements for precise
positioning and has no special requirement for MS capability. This helps
operators support more subscribers.
Implementation U-TDOA requires the cooperation between the Location Measurement
Unit (LMU) and the Serving Mobile Location Center (SMLC). The
LMU is provided by a third-party vendor. The BSC does not manage the
LMU or process messages between the LMU and the SMLC. It only
provides transparent channels between the LMU and SMLC. Physically,
the LMU sets up a transparent channel using transmission resources over
the Abis interface, and the SMLC sets up a transparent channel using
transmission resources over the Lb interface. Then, the BSC
interconnects the two transparent channels. The Abis and Lb interfaces
must use the same transmission mode. Currently, only the
AbisTDM+LbTDM and AbisIP+LbIP transmission modes are
supported.
In AbisTDM+LbTDM mode, the BSC is configured with a semi-
permanent link between the LMU and the SMLC. This semi-permanent
link transparently transmits messages between the LMU and the SMLC.
In AbisIP+LbIP mode, the LMU and the SMLC exchange messages with
each other directly through a router, not through the BSC.
The signaling process for U-TDOA over the Lb interface is as follows:
MSC BSC SMLC
BSSAP Perform Location Request
BSSAP-LE Perform Location Request
U-TDOA Request
U-TDOA Reponse
BSSAP-LE Perform Location Response
BSSAP Perform Location Response
The U-TDOA Delta Timer parameter is added to the BSC.

Related To enable U-TDOA over the Lb interface, perform the following steps
Operations on the BSC:
Add an SMLC destination signaling point and set the type of the
destination signaling point to LB by running the following MML
command:

ADD N7DPC: NAME="smlc", DPX=1, SPX=0, SPDF=WNF,

DPC=H'F5, DPCT=LB, BEARTYPE=MTP3;
Add an SMLC by running the following MML command:
ADD GEXTSMLC: SMLCIDX=0, OPNAME="huawei",
SMLCMode=OUTER, DPX=1;
Add a semi-permanent link, for example in AbisTDM+LbTDM mode,
by running the following MML commands as required:
In BM/TC combined mode:
ADD SEMILINK: IDX=0, APPTYPE=OTHER, LNKRATE=64K,
INSRN=0, INSN=18, INPN=31, INTSN=24, OUTSRN=0, OUTSN=24,
OUTPN=31, OUTTSN=32;
In BM/TC separated mode (the Lb interface is configured in the TC
subrack and the semi-permanent link passes through the Ater interface):
PR Number FF-011
30. Support for NC2 Between GSM and TD-SCDMA

Feature Without the NC2 Between GSM and TD-SCDMA feature, some
Description TD-SCDMA UEs' packet switched (PS) services are processed in
GSM cells, causing GSM cells burdened with PS traffic.
With this feature, the BSC adopts a differential interoperability
policy for TD-SCDMA UEs. Specifically, the BSC forcibly
reselects TD-SCDMA UEs' PS services to qualified TD-SCDMA
cells to strike a traffic balance between GSM and TD-SCDMA
cells.
Improvement Traffic balance between GSM and TD-SCDMA cells
Increased TD-SCDMA network usage
Improved user experience
Implementation When a TD-SCDMA UE is processing PS services in a GSM cell,
the BSC instructs the UE to change its network control mode and
modify the values of measurement control parameters by sending
a Packet Measurement Order message. This message contains
neighboring TD-SCDMA cell information, such as frequencies
and primary scrambling codes.
Then, the BSC sends a Packet Cell Change Order message to the
UE to forcibly reselect this UE's PS services to a neighboring
TD-SCDMA cell if the following conditions are met:
This neighboring TD-SCDMA cell has a required signal level and
is not overloaded.
The UE has been processing PS services for more than N
seconds. Where, N specifies the value of the TDD Reselection
time Threshold parameter in the SET
GCELLRESELECTUTRANTDD command.
The BSC obtains traffic information about neighboring TD-SCDMA cells

from the cell common measurement procedure. In addition, it obtains
other information required for initiating the cell reselection procedure
from packet measurement reports that are periodically sent by the UE.
Related Run the SET GCELLPSOTHERPARA command with GSM-

Operations to-TD Cell Reselection Allowed set to FORCENC2(Force NC2
Mode).
Run the SET GCELLRESELECTUTRANTDD command with
TDD_MULTIRAT_REPORTING set to a value other than 0.
Run the ADD IMEIGRP command with IMEI Group Index,
Start IMEI, and End IMEI set to appropriate values.
PR Number FF-035
31. Support for geographic display of hot spots and terminals for GSM PS services

Description Geographic display of hot spots and terminals for GSM packet
switched (PS) services enables the BSC to provide a
comprehensive grid map based on PS Call History Record (CHR)
logs. The grid map shows the geographic distribution of terminals
and highlights GSM PS service hot spots so that operators can see
what types of terminals or services are being used in these areas.
In this problem report, the term "PS services" refers to GSM PS services.
Improvement This feature helps operators:

 Learn about resource distribution in the entire network
 Identify blind spots
 Track a single subscriber in the network
 Locate and analyze network faults
 Deploy networks and expand network capacity
Implementation The BSC records the following information in PS CHR logs on a
per subscriber basis:
 Common information, including the service type, service
duration, terminal capability, service's server IP address,
service's server port number, and International Mobile Station
Equipment Identity (IMEI)
 Event information, including events in the ATTACH, DETACH,
Packet Data Protocol (PDP) activation, PDP deactivation, and
routing area update procedures
 Network access and cell reselection information, including the
receive level upon network access, downlink bit error
probability (BEP) upon network access, information in the
FLUSH LL procedure, receive level upon cell reselection, and
BEP upon cell reselection
 Services (delay-sensitive, upload, and download services)
location information, including the transmission delay,
transmission jitter, uplink and downlink LLC-layer traffic,
uplink and downlink RLC-layer traffic, and uplink and
downlink PS service channel usage
 Exception information, including uplink and downlink LLC-
layer transmission interruptions, uplink and downlink TBF
establishment failures, and uplink and downlink abnormal TBF
releases
 Measurement report information, including the serving cell's
BCCH signal level and TRX index, and neighboring cells'
BCCH signal levels and frequencies
 Service types information, including uplink and downlink LLC-
layer traffic, uplink and downlink RLC-layer traffic, uplink and
downlink PS service channel usage, uplink and downlink TBF
duration, and uplink and downlink TBF establishment intervals
Nastar analyzes PS CHR log data and displays it in a
comprehensive grid map. Using this grid map, operators can
locate and analyze network faults, perform service- and terminal-
based performance analysis, estimate user experience, and ensure
high signal quality for VIP users.

Related 1.Run the SET GPSCHRCTRL command with the following

Operation parameters set to appropriate values:
 PS CHR Switch
 Service Location Information
 Access and Reselection Information
 Event Information
 Exception Information
 Measurement Report Information
 Service Type Information
 IMEI Information
2.Run the SET GPSCHRSCOPE command with PS CHR
Collect Switch set to an appropriate value.
3.Run the ADD GPSCHRUSER command to add a VIP user
whose PS CHR logs need to be exported.
PR Number FF-036 FF-041 FF-042 FF-043 FF-044 FF-045
32. Support for High Speed Circuit Switched Data Service

Feature The feature High Speed Circuit Switched Data Service enables
Description GBSS to allocate a maximum of four TCHs to a CS data service,
increasing the rate of the CS data service to 57.6 kbit/s.
Improvement With this feature, a CS data service can be allocated a maximum
of four TCHs. Therefore, the rate of the CS data service increases
from 14.4 kbit/s to 57.6 kbit/s, improving user experience.
Implementation 1. HSCSD services are classified into transparent and non-
transparent services. The GBSS allocates TCHs to an HSCSD
service according to the required number of TCHs.
2. A transparent HSCSD service can be set up only at a specified
rate. In a congested cell, a transparent HSCSD service cannot be
set up because the service cannot be allocated sufficient
continuous idle TCHs.
3. A non-transparent HSCSD service supports a variable rate.
When a cell is congested, the GBSS allocates as many continuous
idle TCHs as possible to a non-transparent HSCSD service (in
this case, the actual transmission rate may be lower than the
requested rate). When the cell has sufficient channel resources,
the GBSS allocates more idle TCHs to the service to meet the call
rate request.
4. Huawei GBSS can handle requests for increasing or decreasing
TCHs from MSs that are performing non-transparent HSCSD
services.
5. In an extended cell, an HSCSD service can be allocated only
one TCH. Therefore, an MS performing a non-transparent
HSCSD service can be handed over to an extended cell; however,
an MS performing a transparent HSCSD service cannot be
handed over to an extended cell.
Related To enable this feature, perform the following steps on the BSC:
Operations Turn on the early classmark sending control (ECSC) switch by
running the following MML command:
SET GCELLCCBASIC: IDTYPE=BYID, CELLID=2,
ECSC=YES;
Set the maximum number of channels to be allocated to an
HSCSD service and the dynamic TCH adjustment period by
running the following MML command:
SET GCELLOTHEXT: IDTYPE=BYID, CELLID=2,
HSCSDTRAFFSET=TWO_CHANNELS,
HSCSDSCANPER=4500;
Set the HSCSD Traffic Busy Threshold parameter by running
the following MML command:
SET GCELLCHMGAD: HSCSDBUSYTHRES=80;
PR Number FF-027
33. Support for scenarios where a Pico uses satellite transmission

Description Specific configurations are used to ensure the quality of voice

services in scenarios where a Pico uses satellite transmission.
Such scenarios are characterized by low bandwidth, long delay,
and high jitter.
Improvement With these configurations, the quality of voice services is
ensured in scenarios where a Pico uses satellite transmission.
Implementation Scenarios where a Pico uses satellite transmission have the
following characteristics:
 Long delay: It takes such a SmartPico 2.5 seconds to access
the Abis interface.
 High jitter in the delay: The jitter in the delay for satellite
transmission increases to 300 ms.
 Low bandwidth: The bandwidth of a link is limited to 40
kbit/s.
To ensure the quality of voice services under these conditions,
the following operations are performed:
 The PICO_AND_SAT_TRANS mode is used so that the T200
timer can be increased to 3240 ms for the LAPD link between
the SmartPico and the BSC.
 The jitter buffer of the BSC voice processing module is
increased to fit the 300 ms jitter in the delay.
 The maximum delay for Abis multiplexing is set to 90 ms so
that several continuous speech frames of a single subscriber
can be multiplexed into one IP packet. This saves the
bandwidth used by a single subscriber.
This solution has the following restrictions:
 Voice services are supported, but PS services and data services
are not supported.
 This solution is not applicable to the A over IP mode.
Related To ensure the quality of voice services in scenarios where a
Operations SmartPico uses satellite transmission, perform the following
operations:
Run the SET BTSTRANS command, with Transmission Mode
set to PICO_AND_SAT_TRANS.
Run the ADD BTSABISMUXFLOW command, with Maximum
Delay Time set to 90.
Run the SET BSCJBF command, with IP over satellite
jitterbuffer init value set to 300.
Run the SET GCELLCCACCESS command. In this step,
select the following options under the Speech Version
parameter:
 FULL_RATE_VER1
 HALF_RATE_VER3
Run the SET GCELLCCAMR command. In this step, select
the following options under the AMR ACS[H] parameter:
 4_75KBIT/S
Run the SET GCELLCHMGAD command, with TCH Traffic

Busy Threshold set to 0, AMR TCH/H Prior Allowed set to ON,

and AMR TCH/H Prior Cell Load Threshold set to 0.
Run the SET GCELLBASICPARA command, with HR Use
Downlink DTX set to YES and HR Uplink DTX set to
Shall_Use.
Run the LST GCELLSOFT command and view the DL DTX
Strategy. If the parameter is set to MSC Strategy, the downlink
DTX follows the CN. Now, ensure that the DTX switch of the
CN is enabled.
Run the ADD IPMUX command to add an IP MUX channel.
For example:
ADD IPMUX: MUXTYPE=ABISMUX, ANI=1, PATHID=1,
ISQOSPATH=NO, SUBFRAMELEN=352,
MAXFRAMELEN=1031, FPTIMER=50;
The value of FPTIMER is equal to that of Maximum Delay
Time[ms]. For a FG2c or GOUc multi-core board, the value of
FPTIMER ranges from 1 to 90. The value of this parameter can
be increased only in step of 20 when it exceeds 30.
PR Number FF-039
Feature ID N/A
34. Support for 1+1 unidirectional protection switching

Description OIUa and TDM-enabled POUc boards now support 1+1

unidirectional protection switching.
The working principle of 1+1 unidirectional protection switching
is as follows, with the OIUa board used as an example:
Two OIUa boards work in active/standby mode.
An optical port on the active OIUa board and an optical port on
the standby OIUa board work in active/standby mode. This is
called "1+1." Both ports simultaneously transmit data, but only
one of them receives data at a time.
When the two ports are interconnected with devices provided by
another vendor and a switchover is triggered, the two OIUa
boards do not need to negotiate with the peer devices about the
switchover. In other words, the switchover can be independently
performed at each end. This is called "unidirectional protection
switching."
Improvement Without 1+1 unidirectional protection switching, two
interconnected devices occasionally fail to negotiate with each
other about switchovers because they interpret the multiplex
section protection (MSP) function inconsistently.
With this function, there is a high probability that switchovers are
successfully performed on two interconnected devices because
switchover negotiation is no longer required.
Implementation Through multicast channels, the OIUa and TDM-enabled POUc
boards use active and standby ports to transmit data over the Ater
OML, Ater RSL, Pb SL, MTP2, or LAPD link.
The Backup mode parameter in the SET MSP command is set to
MODE2(1+1 Single End) for the OIUa and TDM-enabled POUc
boards.
For the OIUa board, the default value of Backup mode is
changed from MODE3(1+1 Both End) to MODE2(1+1 Single
End).
Related Run the LST MSP command for a specific optical port to check
Operation whether the value of Backup mode is MODE2(1+1 Single End).
If the value is MODE2(1+1 Single End), no further action is
required.
If the value is not MODE2(1+1 Single End), go to the next step.
Run the SET MSP command for the port with Backup mode set
to MODE2(1+1 Single End).
PR Number DTS2011050300306
Feature ID N/A
35. Support for DBS3900 and BTS3900 baseband extension boards

Description Vodafone, India carriers, and CMCC require VAMOS and EDGE+,
which have a high requirement on the GSM baseband processing
capability. The baseband processing capability of TRX boards,
however, cannot meet the requirement for VAMOS and EDGE+.
This feature is introduced to improve BTS baseband processing
capability so that features that require a high BTS baseband
processing capability can be implemented.
Improvement A GSM baseband unit GBBP is added to the BBU to improve
baseband processing capability so that the GSM carrier baseband is
moved from its TRX board to the GBBP. This enables the TRX
board that has a limited baseband processing capability to support
features that requires a high baseband processing capability, such as
VAMOS and EGPRS-2A.
Implementation 1. The GBBP value of Board Type is added to the ADD BTSBRD
command.
2. The SET BTSBBMODE and LST BTSBBMODE commands
are added to set and query the BTS baseband work mode
respectively.
3. The MOV BTSBRDRXUCHAIN command is added to move
all the RXU chains and rings on a BTS board to the same port on
another BTS board.
4. The DSP BTSBRDBBINFO command is added to query the
information of BTS board baseband, including the information of
GSM carriers on a BTS board.
Related 1.To add a GBBP board (to slot 1 or slot 2 of a BBU), run the
ADD BTSBRD: IDTYPE=BYID, CN=0, BTSID=1003, SRN=0,
SN=1, BT=GBBP;
2. To set the GSM baseband work mode of a BTS (Baseband Work
Mode = Baseband Extension Adjusting), run the following
command:
SET BTSBBMODE: IDTYPE=BYID, BTSID=1003,
BBMODE=BBEXTADJ, CN=0, SRN=0, SN=1;
3. Move the CPRI chains from a GTMU to the GBBP.
4. To move all the RXU chains and rings on a GTMU to the same
port of the GBBP, run the following command:
MOV BTSBRDRXUCHAIN: IDTYPE=BYID, BTSID=1003,
CN=0, SRN=0, SN=6, DCN=0, DSRN=0, DSN=1;
5. To set the GSM baseband work mode of a BTS (Baseband Work
Mode = Whole Baseband Extension), run the following
command:
SET BTSBBMODE: IDTYPE=BYID, BTSID=1003,
BBMODE=BBEXT, BBENHRAP=REASSCHK,
TRXDECRAP=REASSCHK, BBAIDPOLICY=AIDIMM,
BBRECPOLICY=RECCHK, BBAVAILTRXTHD=75;
6. To query the information of BTS board baseband, run the
following command:
DSP BTSBRDBBINFO: IDTYPE=BYID, BTSID=1003, CN=0,

SRN=0, SN=1;
PR Number FF-003
36. Support for GBTS multi-IP address transmission

Description The data on the user plane, control plane, and maintenance plane
of a GBTS is transmitted by different IP addresses of a physical
GBTS port.
Improvement 1. This feature helps carriers separate maintenance plane data,
user plane data, and control plane data from each other on both
physical and logical transport channels. In this way, carriers can
perform security management and QoS management on different
data in different ways.
2. This feature helps carriers monitor and analyze signaling links
and maintenance links, and locate network problems.
Implementation 1. Multiple Ethernet port IP addresses, PPP link IP address,
MLPPP link IP addresses, and loopback interface IP address of a
BTS are required. Therefore, the parameters Port Type and IP
Index are added to the ADD BTSDEVIP command.
2. The BTS MultiIP Switch parameter is added to the SET BTSIP
command to specify whether the BTS supports multiple IP
addresses.
3. If BTS MultiIP Switch is set to Yes, parameters BTS Control
Plane IP, BSC Control Plane IP, BTS User Plane IP, and BSC User
Plane IP are added to specify the IP addresses on the signaling
plane and user plane of the BTS. BTS IP and BSC IP specify the
BTS maintenance plane IP address and BSC maintenance plane IP
address respectively. The BTS Maintenance Plane IP for Ethernet
Port parameter is added to specify the outgoing interface on the
maintenance plane of the BTS.
4. If the BTS is configured with multiple IP addresses at the BSC
but the BTS does not support multiple IP addresses, the
maintenance channel functions properly. However, the BTS
cannot be initialized and therefore does not provide services. The
BTS reports the alarm ALM-21806 BTS Not Support Configured
Function with the cause value of "The BTS does not support
multiple IP addresses."
5.In the data configuration, IP addresses can be set for two
Ethernet ports.The IP address of the FE port that does not carry
services for the BTS is unavailable when the hardware version of
the main control processing board of the BTS cannot be
configured with IP addresses of two Ethernet ports.
Related 1. To configure the IP addresses of multiple Ethernet ports on a
Operations BTS, run the following command:
ADD BTSDEVIP: IDTYPE=BYID, BTSID=1020,
PT=ETHPORT, PN=0, CN=0, SRN=0, SN=6, IP="2.3.4.8",
MASK="255.255.255.0";
ADD BTSDEVIP: IDTYPE=BYID, BTSID=1020,
PT=ETHPORT, PN=0, CN=0, SRN=0, SN=6, IPIDX=1,
IP="2.3.3.7", MASK="255.255.255.0";
2. To specify whether the BTS supports multiple IP addresses, run
the following command:
SET BTSIP: IDTYPE=BYID, BTSID=1020,
BTSCOMTYPE=PORTIP, BTSIP="2.3.4.8", BSCIP="2.3.3.4",
BTSMUTIP=YES, BTSCPIP="10.10.10.10",

BSCCPIP="10.161.99.1", BTSUPIP="10.10.11.10",
BSCUPIP="10.161.99.2";
3. To query BTS IP addresses, run the following command:

LST BTSDEVIP: IDTYPE=BYID, BTSID=1020;
4. To query the IP addresses used by an IP-based BTS, run the

following command:
LST BTSIP: IDTYPE=BYID, BTSID=1020;
PR Number FF-030
37. Support for Checking the BA2 list of GSM cells When the Neighboring 3G Cell
Measurement Starts
Description The BA2 list of GSM cells is checked when the neighboring 3G cell
measurement starts.
Benefit When the neighboring 3G cell measurement starts, if the number of
different frequencies in the BA2 list of GSM cells equals 32, the
measurement stops. The system then displays error information so
that users know they need to reduce the number of different
frequencies in the BA2 list to less than 32 and then restart the
measurement.
Implementation When the neighboring 3G cell measurement starts, the number of
different frequencies in the BA2 list of GSM cells is checked. If this
number reaches 32, the measurement stops and the system displays
the message "The number of different frequencies in BA2 table must
be less than 32."
Related To start the neighboring 3G cell measurement, log in to the Nastar
Operations and choose Maintenance > Data Subscription Management >
Application Subcription > GSM/UMTS Neighboring Cell
Analysis.
Number
38. Support for Configuring a DPUe Board to Process GSM PS Services

Description In BSC6900 V900R014 and later versions, a DPUe board can be

used as a DPUg board. It has the same function and specification as a
DPUg board when processing GSM PS services.
Note that a DPUg board cannot be used as a DPUe board.
Benefit Users can use a DPUe board to replace a DPUg board.
Implementation A logical function option GPCU is added for DPUe boards in the
ADD BRD command so that users can enable a DPUe board to
function as a GPCU on the BSC6900.
Related To set the logical function type of a DPUe board to GPCU, run the
ADD BRD: SRN=0, BRDCLASS=DPU, BRDTYPE=DPUe,
LGCAPPTYPE=GPCU, SN=8, MPUSUBRACK=0, MPUSLOT=0;
Number
39. Installing Any Board Except SCUa/SCUb, GCUa, and GCGa in Slots 4 and 5
Description The restriction that only TNUa boards can be installed in slots 4 and
5 is now lifted. In all-IP networking mode, no TNUa board is
needed. Therefore, the preceding restriction is changed as follows:
All boards except SCUa/SCUb, GCUa, and GCGa can be installed in
slots 4 and 5.
Benefit The utilization of slots 4 and 5 is improved.
Implementation The restriction that only TNUa boards can be installed in slots 4 and
5 has been removed from the configuration restriction of the ADD
BRD command.
Related You can run the ADD BRD command to add any board except
Operations SCUa/SCUb, GCUa, and GCGa in slots 4 and 5. The following is an
example:
ADD BRD: SRN=0, BRDCLASS=DPU, BRDTYPE=DPUb,
LGCAPPTYPE=GTC, SN=4, ISTCBRD=NO, MPUSUBRACK=0,
MPUSLOT=0;
Number
40. Transmission Resource Pool for the A Interface

Description In Ethernet layer 3 networking, multiple IP interface boards on the

BSC side form a transmission resource pool, and the IP addresses for
these boards form an IP address pool. A media gateway (MGW) can
be connected to any IP interface board in the transmission resource
pool. When a call needs to be set up, the BSC selects an IP address
from the IP address pool for the service while maintaining load
balancing.
Benefit  Higher reliability for IP networking
If transmission resource pools are configured, a peer network element
(NE) can be connected to multiple IP interface boards of the BSC.
 More efficient use of transmission resources
An algorithm is used to balance the load among IP interface boards
and transmission ports.
 Better serviceability of the BSC
With the IP path configuration-free function and source-based
routing, no adjustments need to be made to the configuration on the
BSC side when the user-plane capacity of a peer NE is expanded.
 Higher maintainability
With this feature, transmission capacity expansions for the A interface
can be achieved by simply running relevant configuration commands
on the BSC side to add interface boards to transmission resource
pools.
Implementation The BSC sequences the SIP addresses in the IP address pool of a
transmission resource pool for the A interface every five seconds.
Load shares are determined based on the load status of the SIP
addresses. When a service needs to be set up over the A interface, the
BSC selects a SIP address according to the load shares.
When retransmission resource pools are configured, admission
control is not performed over the A interface.
Running the ping command checks the connectivity between all IP
addresses in the IP address pool and the peer IP addresses. An alarm
is reported if a fault is detected. This function also collects statistics
on the packet loss rates over IP addresses on the local end. During the
load balancing processes, IP addresses with low packet loss rates are
preferred. Packet loss rates in the interval [Lowest packet loss rate,
Lowest packet loss rate + 5%] are considered low.
Related 1. Run the BSC69000 MML command ADD DEVIP to add a
Operations device IP address.
IPADDR="14.226.10.14";
2. Run the BSC6900 MML command ADD ETHIP to add an IP
address for an Ethernet port.
ADD ETHIP: SRN=0, SN=14, PN=2, IPINDEX=0,
IPADDR="183.25.95.1", MASK="255.255.255.0";
3. Run the BSC6900 MML command ADD SRCIPRT to add a
source-based route, with the IPTYPE parameter set to ETHIP,
the SRCIPADDR parameter set to the IP address configured in
Step 2, and the NEXTHOP parameter set to an IP address

within the same network segment as the source IP address.

ADD SRCIPRT: SRN=0, SN=14, IPTYPE=ETHIP,
4. Run the BSC6900 MML command ADD SRCIPRT to add a
source-based route, with the IPTYPE parameter set to DEVIP,
the SRCIPADDR parameter set to the device IP address
configured in Step 1, the NEXTHOP parameter set to the next-
hop address configured in Step 3, and the
STANDBYNEXTHOPSWITCH parameter set to NO. If the
STANDBYNEXTHOPSWITCH parameter is set to YES, the
STANDBYNEXTHOP parameter needs to be set accordingly.
STANDBYNEXTHOPSWITCH=NO, REMARK="A";
5. Run the BSC69000 MML command ADD IPPOOL to add an
IP address pool, with the IPPOOLINDEX parameter set to an
appropriate value.
ADD IPPOOL: IPPOOLINDEX=10, IPPOOLNAME="A";
6. Run the BSC69000 MML command ADD IPPOOLIP to add an
IP address to the IP address pool, with the IPPOOLINDEX
parameter set to the value configured in Step 1 and the SRN,
SN, and IPADDR parameters set to the values configured in
Step 1.
ADD IPPOOLIP: IPPOOLINDEX=10, SRN=0, SN=14,
IPADDR="14.226.10.14";
7. Run the BSC6900 MML command ADD ADJNODE to add an
adjacent node, with the ANI, NAME, and CNMNGMODE
parameters set to appropriate values, the NODET parameter set
to A, the ISIPPOOL parameter set to YES, the
IPPOOLINDEX parameter set to the value configured in Step
5, and the PINGSWITCH parameter set to ENABLE.
ADD ADJNODE: ANI=5, NAME="A", NODET=A,
ISIPPOOL=YES, IPPOOLINDEX=10,
CNMNGMODE=SHARE, PINGSWITCH=ENABLE;
Trouble Ticket IR-RAN14.0-124-SR-01-AR-01
Number
41. Support for Separation of the Communication Data Flow Between the BSC and VNP
from that Between the BSC and EMS/LMT

Description With this function, the communication data flow between the BSC
and Vendor Network Probe (VNP) is separated from that between the
BSC and EMS/LMT.
Benefit The communication data flow between the BSC and VNP is
separated from that between the BSC and EMS/LMT.
Implementation A BSC is configured with different IP addresses and VLAN IDs for
its communication with the VNP and EMS/LMT.
The VLAN IDs configured on the active and standby OMU boards
are checked every 5 minutes. If the VLAN ID configured on the
active OMU board is inconsistent with that on the standby OMU
board, the ALM-20722 VLAN ID Inconsistency on Active and
Standby OMU Boards is reported.
BSC local IP addresses configured on the active and standby OMU
boards are checked every 5 minutes. If they are incorrect, the ALM-
20721 OMU IP Address Configuration Error is reported.
Related 1.Run the following command to query the BSC local IP address and
Operations VLAN IDs:
LST GVNPLOCALIP:;
2. Use the omutool to query the BSC local IP address and VLAN IDs
for communication with the VNP. For details, see section "Changing
IP Addresses and Subnet Masks of the OMU Ethernet Adapters" in
the BSC6900 GSM OMU Administration Guide.
3. Use the omutool to modify the BSC local IP address and VLAN
IDs for communication with the VNP. For details, see section
"Configuring Radio Measurement Data Interface for Navigation" in
the GBSS Feature Activation Guide.
Number
42. BSC Supporting Blind Search

Description With the BSC supporting Blind Search feature, users only need to
configure 3G frequencies instead of neighboring 3G cells when 2G-
to-3G cell reselection is enabled. Based on the configured 3G
frequencies, an MS automatically reselects an appropriate
neighboring 3G cell.
Benefit This feature simplifies configurations for 2G/3G interoperability.
Implementation Assuming that users have configured 3G frequencies instead of

neighboring 3G cells, and 3G ARFCNs for Cell Reselection and
Select 3G Cell After Call Release are set to YES(Yes):
 If TCHs are idle, the BSC sends frequencies in the system
information 2Quater to MSs.
 If TCHs are occupied, the BSC sends frequencies in the Channel
Release message to MSs.
If a cell under the BSC is configured with frequencies, the BSC sends these
frequencies to the MSs in the cell.
If a cell under the BSC is not configured with frequencies, the BSC sends the
frequencies configured for the BSC to the MSs in the cell.
Related 1. Run the SET GCELLHOBASIC command with Inter-RAT

Operations Cell Reselection Enable set to YES(Yes). The following is an
example:
INTERRATCELLRESELEN=YES;
2. Run the SET GCELLCCAD command with Select 3G Cell
After Call Release set to YES(Yes). The following is an
example:
CELLSELECTAFTERCALLREL=YES;
3. Run the SET GCELL3GARFCN command with 3G ARFCNs
for Cell Reselection set to YES(Yes). The following is an
example:
SET GCELL3GARFCN: IDTYPE=BYID, CELLID=0,
INPUT3GARFCNEN=YES,
INPUT3GARFCNENTYPE=TDD, ARFCN1=100;
4. Run the SET G3GARFCN command with 3G ARFCNs for
Cell Reselection set to YES(Yes). The following is an example:
SET G3GARFCN: INPUT3GARFCNEN=YES,
INPUT3GARFCNENTYPE=FDD, ARFCN1=100;
Trouble Ticket G-OR-BLIND-SEARCH
Number
43. PDCH Loopback Test

Description In Abis over TDM mode, segment-by-segment loopbacks can be

performed on an intermittent or faulty PDCH to identify fault points
and fault types.
Benefit Without the segment-by-segment loopback function, PDCH faults
can only be identified by the packet capture tool, which makes fault
identification difficult, time-consuming, and inaccurate. This
function loops back transmission channels segment by segment to
quickly identify fault points, and analyzes the uplink and downlink
loopback data to determine fault types.
Implementation The MML commands STR PDCHLOOPTST, STP
PDCHLOOPTST, and DSP PDCHLOOPTST are added.
The following functions are added to the LMT: starting PDCH
loopbacks, stopping PDCH loopbacks, and querying PDCH
loopback status.
After a loopback is started on a PDCH, the BSC sends test data to
the BTS and compares the sent data with the received data to
determine whether the segment where the loopback is performed is
faulty.
Related To start a PDCH loopback, stop a PDCH loopback, or query PDCH
Operations loopback status, run the following MML commands:
 Run the STR PDCHLOOPTST command to start a PDCH
loopback.
 Run the STP PDCHLOOPTST command to stop a PDCH
loopback.
 Run the DSP PDCHLOOPTST command to query PDCH
loopback status.
To start a PDCH loopback on the LMT, do as follows:
1. On the LMT, click Device Maintenance.
2. On the BTS Maintenance tab page, click Monitor Channel
Status.
3. On the Monitor Channel Status tab page, right-click a PDCH
where a loopback needs to be performed and choose Start
Loop from the shortcut menu.
4. In the Start Loop dialog box, set the required parameters and
click OK.
To stop a PDCH loopback on the LMT, do as follows:
1. On the LMT, click Device Maintenance.
2. On the BTS Maintenance tab page, click Monitor Channel
Status.
3. On the Monitor Channel Status tab page, right-click a PDCH
where a loopback needs to be performed and choose Stop Loop
from the shortcut menu.
4. In the Stop Loop dialog box, set the required parameters and
click OK.
Note that no action is required for querying PDCH loopback status
because the status is automatically queried.

Trouble Ticket None

Number
Feature ID None
44. Mega BSC

Description When IP over FE/GE/STM-1 is used over the A, Abis, and Gb

interfaces, a BSC6900 can be configured with a maximum of 8192
TRXs and a DPUg board supports a maximum of 1536 PDCHs.
The improved specifications are as follows:
Item Specifications
Number of TRXs 8192
Traffic volume 45,000 (Erlang)
Busy hour call attempts (BHCA) 11,000,000
for a CS+PS composite service
Number of users 2,200,000
Circuit identification codes 61,440
(CICs) on the A interface
Number of PDCHs that can be 32,768
activated
PS traffic throughput 3072 (Mbit/s)
Number of PDCHs supported by 1536
a DPUg board
 When TDM over FE/GE/STM-1 is used over the A, Abis, and Gb

interfaces, a maximum of 4096 TRXs can be configured for a BSC6900.
 When TDM is used over the Abis interface, a DPUg board still supports a
maximum of 1024 PDCHs.
Benefit  Increases the number of MSs per BSC without affecting the voice
quality.
 Improves the equipment integration, decreasing the number of
BSCs, equipment room, and power consumption per TRX.
 Simplifies inter-BSC parameter settings, improving the operation
and maintenance (O&M) efficiency.
 Decreases inter-BSC handovers and cell reselections, improving
network performance.
Implementation Additional interface boards, DPUs, and XPUs are added.
A BSC6900 V900R013 or later is configured with the following
boards: DPUf, DPUg, XPUb, SCUb, GCUa, GCGa, OMUc, FG2c,
FG2d, GOUc, GOUd, and POUc.
A DPUg board has 14 DSPs (numbered from 0 to 13), supporting a
maximum of 1536 PDCHs. These DSPs are divided into the
following groups:
 Group 1: DSPs 0 to 9. TDM and IP cells can be distributed on
these DSPs. The maximum number of PDCHs allocated to TDM
cells is 1024.
 Group 2: DSPs 10 to 13. Only IP cells can be distributed on these
DSPs.

Related 1. Apply for and activate a license that supports the following
Operations license control items:
 Maximum TRX number allowed Resource (per TRX) = 8192
 Mega BSC (per TRX) = 8192
2. Use IP over FE/GE/STM-1 transmission for the A, Abis, and
Gb interfaces.
3. Run the ADD GTRX command to add 8192 TRXs. Then, run
ACT BTS, ACT GCELL, or ACT GTRX to activate these
TRXs.
Purchase the Packet Service Hardware Capacity license to use improved

DPUg specifications. The license specifies the number of additional PDCHs.
Trouble Ticket None

Number
45. Active TBF Allocation

Description The Active TBF Allocation feature enables the BSC to periodically
collect the number of temporary block flows (TBFs) in transfer
mode multiplexed on each PDCH. The BSC uses this number to
adjust channel allocation and channel conversion algorithms.
Benefit The PDCH bearer efficiency increases because fewer PDCHs are
required if the cell throughput remains unchanged. Therefore, the
system capacity will need to be expanded less frequently.
The number of PDCHs for voice services during busy hours is
reduced, and the percentage of half-rate TCHs decreases. As s result,
the voice quality is improved.
Implementation The BSC periodically collects the number of TBFs in transfer mode
multiplexed on each PDCH. The BSC uses this number to adjust
channel allocation and channel conversion algorithms.
Related Run the SET GCELLPSCHM command to set Dynamic TBF
Operations Switch to ON(ON).
Set Dynamic TBF DL MUX Thres. for Channel Conversion.
The default value of this parameter is 20. If the average multiplexing
ratio for downlink TBFs in transfer mode in a cell exceeds the value
of this parameter, channel conversion is triggered.
Set Dynamic TBF UL MUX Thres. for Channel Conversion.
The default value of this parameter is 20. If the average multiplexing
ratio for uplink TBFs in transfer mode in a cell exceeds the value of
this parameter, channel conversion is triggered.
The Active TBF Allocation feature may not function as expected if Downlink
Multiplex Threshold of Dynamic Channel Conversion and Uplink Multiplex
Threshold of Dynamic Channel Conversion are set to too large values.
Trouble Ticket G-OR-TBFALLOCATE

Number
46. Dynamic Multiple CCCH

Description In traffic surge scenarios such as holidays or emergencies, paging

overload occurs, which greatly affects services. In static multiple
common control channel (CCCH) configuration mode, the specific
number of configured channels is difficult to determine. If the
configured channels are insufficient, paging overload cannot be
resolved thoroughly; if excessive channels are configured, channel
resources are wasted.
The Dynamic Multiple CCCH feature can resolve the preceding
issues. With this feature, If the load on the CCCHs increases, the
TCHs corresponding to timeslots 2, 4, and 6 on the BCCH TRX are
dynamically converted to CCCHs in succession. This increases the
paging capability over the Um interface.If the load on the CCCHs
decreases, the CCCHs corresponding to timeslots 6, 4, and 2 are
dynamically converted to TCHs in succession. This increases the
resource usage.
Benefit This feature has the following benefits:
 Increases channel usage, compared with that in static multiple
CCCH configuration mode.
 Improves the paging capability over the Um interface, reducing the
possibility of low paging efficiency due to a sharp increase in
paging messages and PS services.
− Increases non-BCCH radio signaling link (RSL) bandwidth
usage, because the BCCH RSL bandwidth is independently
allocated.
Implementation This feature is implemented as follows:
Dynamic Multiple CCCHs is set to ON and related parameters are
set on the CME or LMT.
The BSC sends the parameters to the BTS.
The BTS calculates the CCCH load and determines whether to add
or remove a CCCH based on the threshold received from the BSC.
Then, the BTS sends a CCCH addition or removal request to the
BSC.
Assuming that the BTS makes a request to add a CCCH:
 If the current channel is an idle TCH, the BSC converts the TCH
into a CCCH.
 If the current channel is a TCH occupied by a call, the BSC
performs an intra-cell handover.
 When the TCH becomes idle, the BSC converts the TCH into a
CCCH.
 When the TCH is still occupied (If the handover fails, the BSC
releases the call except a call initiated by a VIP user or an
emergency call.), the BSC fails to convert the TCH to a CCCH.
 If the current channel is a dynamic PDCH, the BSC requests the
PCU to release the PDCH.
 When the PDCH is released, the BSC converts the channel into a
CCCH.
 When the PDCH is not released, the BSC fail to convert the PDCH
into a CCCH.

Assuming that the BTS makes a request to decrease CCCHs:

The BSC converts a CCCH into a TCH and starts protection over
paging messages within a specified time. This prevents paging
messages from being lost because paging groups on the BSS and
MSs are inconsistent due to channel conversion.
The BSC broadcasts the updated SI 3 over the Um interface.
NOTE
CCCHs are added one by one in the order of timeslot 2, 4, and then
6, whereas they are removed one by one in the order of timeslot 6, 4,
and then 2.
Related Run the SET GCELLCCCH command with Dynamic Multiple
Operations CCCHs set to ON. The following is an example:
SET GCELLCCCH: IDTYPE=BYID, CELLID=2,
DynCCCHSwitch=ON, MaxDynCCCHNum=2,
DynCCCHLoadIncrThr=90, DynCCCHLoadRedcThr=65,
DynCCCHLoadDuration=10, DynCCCHReduceInterval=30;
A larger value for Maximum Number of Dynamic CCCHs
indicates a greater paging capability over the Um interface. To
prevent paging message congestion over the Abis interface, set
BCCH TRX RSL Multiplexing Mode to its recommended value.
Number
47. IM Service Efficiency Improvement, Web Browsing Service Efficiency Improvement,

Email Service Efficiency Improvement, Streaming Media Service Resource Balancing,
and P2P Resource Balancing

Description With these features, the BSC allocates Um interface resources to

users based on user priority and PS service class, which is identified
by Deep Packet Inspection (DPI).
Benefit Increase the multiplexing ratio for short-period services and decrease
that for long-period services, increasing PDCH usage during peak
hours and reducing the requirement on network capacity expansion
for operators.
Increase the usage of Um interface resources, improving user
experience for high-priority users and for users with high-value
services.
Implementation An NIU board is added for the BSC to support DPI, which identifies
the PS service class based on configured mapping between protocol
ID and service class.
The BSC allocates PDCHs to users based on user priority and
service class during channel allocation.
When MAC Scheduling Type is set to BUDGET(Scheduling
Based On Budget) or PFSCHEDULE(Proportion Fair
Scheduling), the BSC uses different weights to schedule services
with different user priorities and service classes.
The BSC uses different downlink TBF release delays for services
with different service classes.
Related 1. Run the ADD BRD command to add an NIU board.
Operations 2. Run the SET GCELLGPRS command to set GPRS to
SUPPORT(Support as built-in PCU) and Support DPI to
BSCSUPPORT(BSC Support).
3. Run the ADD TRAFFICMAP command to set the mapping
between Protocol ID and Service Type.
4. Run the SET GCELLPSOTHERPARA command to set MAC
Scheduling Type to BUDGET(Scheduling Based On Budget)
or PFSCHEDULE(Proportion Fair Scheduling).
5. Run the SET GCELLPSDIFFSERVICE command to set
parameters related to differentiated PS services.
Trouble Ticket G-OR-PSDIFFERENT
Number
GBFD-511604
GBFD-511605
GBFD-511606
GBFD-511607
48. PS AFC

Description The PS Automatic Frequency Correction (AFC) feature corrects the

frequency offset for the uplink PS services performed by fast-
moving MSs. This reduces the Doppler frequency shift caused by
high-speed movement
Benefit This feature greatly improves the uplink receive demodulation

performance for all MSs moving at 200 km/h on the GSM900
frequency band or 100 km/h on the DCS1800 frequency band,
increasing the average uplink rate for a single timeslot and
decreasing the uplink retransmission rate at the EGPRS RLC layer.
Implementation The UL PS Automatic Frequency Correction parameter has been
added to control whether to enable the PS AFC feature. The PS AFC
feature performs frequency discrimination on the antenna data of a
burst before whitening filtering to estimate the frequency offset.
After correcting the frequency offset for the antenna data of the burst
based on the estimation, the BTS performs data synchronization and
Least Square (LS) channel estimation.
Related Run the following command to enable the PS AFC feature:
Operations SET GCELLOTHEXT: IDTYPE=BYID, CELLID=1,
PSULFREQADJ=YES;
Trouble Ticket G-OR-PSULAFC

Number
49. Support for electronic label of an alternating current (AC) power module on an MRRU
or GRRU board in V3 RRU

Description The GBFD-111202 O&M of BTS feature enables users to query the
electronic label of an alternating current (AC) power module on an
MRRU or GRRU board in V3 RRU. This feature also enables users
to export and upload a device file for the BTS that holds the AC
power module.
Benefit This feature improves the efficiency of maintaining an AC power
module.
Implementation Users can run the DSP BTSELABEL command to query the
electronic label of an AC power module.
Users can also run the EXP BTSDEVFILE command to export a
device file for the BTS; view the device information about an AC
power module, including the electronic label, in the board area of the
device file.
Related Run the DSP BTSELABEL command to query the electronic label
Operations of the AC power module on a specified board. In this step, set Query
Type to BRD(Board), Cabinet No. to the number of the cabinet,
Subrack No. to the number of the subrack, Slot No. to the number
of the slot that holds the board, and Sub Slot No. to 1.
Run the EXP BTSDEVFILE command to export a device file for
the BTS. View the device information about the AC power module in
the board area of the device file.
Trouble Ticket None
Number
50. Abis IPHC

Description The GBFD-118612 Abis IPHC feature enables 3900 series base
stations except BTS3900E and BTS3900B to support the Abis IPHC
function. 3012 series base stations support Abis IPHC since the base
version of this feature.
The IP Header Compression (IPHC) function complies with
RFC2507: IP Header Compression and RFC3544: IP Header
Compression over PPP. IPHC is a standard compression technology
in IP over E1 mode. With this function, the redundant information
contained in IP/UDP headers of data packets can be removed from
User Datagram Protocol (UDP) data flow, saving IP transmission
resources and improving the transmission efficiency. The UDP data
flow refers to the UDP packets that share the same source IP address,
destination IP address, source port, and destination port.
Benefit This feature saves IP transmission resources and improves the
transmission efficiency.
Implementation 3900 series base stations except BTS3900E and BTS3900B support
the compression of IP headers in data packets that are transmitted
over Point-to-Point Protocol (PPP) links or in Multi-Link Point-to-
Point Protocol (MLPPP) link groups.
Headers of data packets transmitted over PPP links or in MLPPP link
groups consist of IP headers in the network layer, TCP/UDP headers
in the transport layer and various headers in the application layer. If
the connection works as normal, most information contained in the
headers does not change or changes in a mode specified by the
protocols for various layers.
With the IPHC function, the information that does not change can be
removed from the headers, and the information that changes in the
specified mode can be replaced with fewer bits.
Related Enabling the IPHC Function
Operations  On a BTS configured with PPP links:
1. Enable IPHC on a BTS by setting IP Header Compression to
ENABLE(ENABLE) in the ADD BTSPPPLNK or MOD
BTSPPPLNK command.
2. Enable IPHC on a BSC by setting Head compress to
UDP/IP_HC(UDP/IP_HC) in the ADD PPPLNK or MOD
PPPLNK command. If the BSC works in IP over FE/GE mode,
enable IPHC on the router instead of the BSC.
3. Run the DSP BTSPPPLNK command to query IPHC
Negotiation Result. If IPHC has been enabled, IPHC
Negotiation Result is Enabled in the command output.
Otherwise, IPHC Negotiation Result is Disabled in the
command output.
 On a BTS configured with MLPPP link groups:
1. Enable IPHC on a BTS by setting IP Header Compression to
ENABLE(ENABLE) in the ADD BTSMPGRP or MOD
BTSMPGRP command.
2. Enable IPHC on a BSC by setting Head compress to
UDP/IP_HC(UDP/IP_HC) in the ADD MPGRP or MOD
MPGRP command. If the BSC works in IP over FE/GE mode,

enable IPHC on the router instead of the BSC.

3. Run the DSP BTSMPGRP command to query IPHC
Negotiation Result. If IPHC has been enabled, IPHC
Negotiation Result is Enabled in the command output.
Otherwise, IPHC Negotiation Result is Disabled in the
command output.
Trouble Ticket G-OR-BTSIPHC
Number
51. BTS Integrated IPSec

Description This feature encrypts data transmitted between a BTS and a BSC that
are connected to the network through an external security gateway.
This ensures data confidentiality, integrity, and non-repeated
transmission and provides operators with a secure end-to-end
network.
Benefit This feature protects IP packets transmitted on an IP network from
being intercepted or modified, providing end-to-end security
protection for user data.
Implementation IPSec uses the Authentication Header (AH) and Encapsulating
Security Payload (ESP) protocols to ensure secure transmission of IP
packets. IPSec also uses Internet Key Exchange (IKE) to perform
automatic key negotiation, set up and maintain security association.
This simplifies the use and management of IPSec.
IKE supports peer-end identification by using pre-shared keys and
digital certificates to enhance bearer network security.
Related 1. Run the ADD BTSACL command with ACL ID and ACL
Operations Description specified to add an access control list (ACL).
2. Run the ADD BTSACLRULE command to configure ACL
rules.
3. Run the ADD BTSPACKETFILTER command to configure
packet filtering rules in the receiving direction. Only packets
meeting the configured rules are received.
4. Run the SET BTSIKECFG command to configure basic
Internet Key Exchange (IKE)configurations.
5. Run the ADD BTSIKEPROPOSAL command to configure
IKE security proposals.
6. Run the ADD BTSIKEPEER command to configure an IKE
peer.
7. Run the ADD BTSIPSECPROPOSAL command to configure
IPSec security proposals.
8. Run the ADD BTSIPSECPOLICY command to configure
IPSec security policies.
9. Run the ADD BTSIPSECBIND command to configure IPSec
security policy group binding (binding the specified security
policies to the transmission output port).
Trouble Ticket OR-GBTS14-002
Number
Feature ID GBFD-113524, MRFD-211602
52. BTS Supporting PKI

Description Based on Certificate Management Protocol version 2 (CMPv2), this

feature provides a set of functions to manage certificates between
NEs. The functions include certificate registration request, key
update, key restore, certificate revocation, cross-certification, CA key
update notification, certificate authorization notification, and
certificate revocation notification.
Benefit By authenticating NE identification, this feature prevents
unauthorized users from accessing the network and therefore
improves the network security. This feature is used with encryption
technologies provided in IPSec or Secure Socket Layer (SSL) to
protect user data from being intercepted or modified.
Implementation CMPv2BTSs are configured with Huawei device certificates before
delivery. With these device certificates, BTSs can request one or
multiple operator certificates from the CA server according to the
CMPv2 protocol and set up links to the security gateways at the peer
end, ensuring secure communication between BTSs and a BSC.
Related 1. Run the MOD BTSCERTREQ command to modify the
Operations contents of the BTS certificate request file.
2. Run the REQ BTSDEVCERT command to apply for a device
certificate according to the BTS certificate request file.
3. Run the ADD BTSCERTMK command to add the BTS device
certificate to the configuration library.
4. Run the MOD BTSAPPCERT command to configure the
current BTS certificate.
5. Run the ADD BTSTRUSTCERT command to add a BTS trust
certificate.
6. Run the SET BTSCERTCHKTSK command to set a task to
check the BTS certificate validity.
7. Run the DSP BTSTRUSTCERT command to query the status
of the BTS trust certificate.
8. Run the TST BTSAPPCERT command to check whether the
current certificate is functional.
Number
53. Built-in Firewall

Description As an important technology to maintain network security, the built-in

firewall analyzes the contents of packets sent over BTSs to identify
and filter out illegal data flows and malicious packets.
Benefit The built-in firewall filters out illegal data flows and malicious
packets to ensure that the BTS functions properly.
Implementation The built-in firewall provides the following functions:
 ACL-based packet filter: The access control list (ACL) module
filters out illegal data flows to protect legal data. The ACL filtering
policy supports sextuple-based filtering and VLAN ID-based
filtering. A sextuple consists of six elements: source IP address,
source port, destination IP address, destination port, protocol, and
differentiated services code point (DSCP). The ACL module also
supports both whitelist- and blacklist-based filtering.
 Malicious packet filter: This filter provides basic network
protections against various types of attacks, such as address
resolution protocol (ARP) spoofing, flooding attacks, and
malformed packet attacks.
Related 1. Run the ADD BTSACL command to configure a BTS ACL.
Operations 2. Run the ADD BTSACLRULE command to add ACL rules.
3. Run the ADD BTSPACKETFILTER command to configure
the packet filtering function for the BTS.
4. Run the ADD BTSFLOODDEFEND command to configure
alarms and policies that protect against flooding attacks on the
BTS.
5. Run the SET IPGUARD command to set the policies that
protect against IP attacks.
Number
Feature ID None
54. BTS3900AL Cabinet

Description The BTS3900AL cabinet is used for outdoor large-capacity sites and
has the following characteristics:
1. Co-site of a macro base station and a distributed base station:
 A BTS3900AL cabinet supports a maximum of 3 baseband units
(BBUs). The power consumption of a fully equipped BTS3900AL
cabinet is 650 W.
 A BTS3900AL cabinet supports a maximum of 18 radio frequency
units (RFUs). In remote connection mode, it supports a maximum
of 9 RFUs and 9 remote radio units (RRUs).
 A BTS3900AL cabinet can be deployed independently or in
combination with other BTS3900AL cabinets to meet the capacity
requirements in multi-band or multi-mode co-site scenarios.
2. Built-in microwave or optical transmission devices: If there is
no built-in backup power device, a BTS3900AL cabinet
provides up to 11 U of space. If there is a built-in backup power
device, a BTS3900AL cabinet provides up to 4 U of space,
which can house most of microwave indoor units (IDUs) in the
industry.
3. Diversified backup power supply solutions:
 Short-term: Batteries together with transmission devices are
installed in a BTS3900AL cabinet.
 Middle- and long-term: An IBBS700T battery cabinet is used to
supply backup power.
Benefit This feature improves the service capacity of a single site, facilitates
site swapping, and improves the competitiveness of the SingleRAN
solution. In addition, this feature facilitates transition from a single-
mode site to a multi-mode site.
Implementation The cabinet control unit (CCU) centrally controls cabinets, and
manages cabinet inventory and monitoring units.
The heat assembly unit (HAU) automatically heats cabinets when
they start or work at a low temperature.
Related 1. Run the ADD BTSCABINET command to configure a
Operations BTS3900AL cabinet.
2. Run the DSP BTSELABEL command to query the electronic
label.
Number
Feature ID None
55. VSWR Derating Mode for a Multi-Carrier BTS

Description This feature provides the voltage standing wave ratio (VSWR)
derating mode which enables BTSs to continue processing some
services when the critical alarm ALM-26529 RF Unit VSWR
Threshold Crossed is reported. When the antenna VSWR meets the
alarm clearance conditions, the alarm automatically clears, and
services automatically return to normal.
Without this feature, services are interrupted when the critical alarm
ALM-26529 RF Unit VSWR Threshold Crossed is reported.
Maintenance engineers have to reset or replace the faulty TRX
module at the site to clear the alarm even if the alarm clearance
conditions have been met.
Benefit This feature prevents service interruption caused by the alarm ALM-
26529 RF Unit VSWR Threshold Crossed, improves network
stability, and reduces the operational expenditure of operators.
Implementation To avoid resetting or replacing the faulty TRX module at the site and
service interruption caused by the alarm ALM-26529 RF Unit
VSWR Threshold Crossed, operators can determine whether to shut
down the power amplifier on a TRX module by setting the Serious
VSWR Alarm Post-processing Mode parameter of the SET
BTSRXUBP command.
If the power amplifier is not shut down, the TRX module can be
used. If the power amplifier is shut down, the TRX module must be
reset or replaced when the alarm is reported.
Related Run the SET BTSRXUBP command with Serious VSWR Alarm
Operations Post-processing Mode set to NOTURNOFFPA (Reduce Power).

Number
Feature ID None
56. RSSI Monitoring on the Receive Path

Description Received signal strength indicator (RSSI) monitoring on the receive

path is important for detecting whether the uplink radio frequency
(RF) path on the RXU module is faulty. When the uplink RF path is
faulty, the alarm ALM-26521 RF Unit RX Channel RTWP/RSSI Too
Low or ALM-26522 RF Unit RX Channel RTWP/RSSI Unbalanced
is reported. Operators can clear the alarm or replace the faulty RXU
module to rectify the faults in the uplink RF path according to the
alarm information in a timely manner.
Benefit Two hardware alarms ALM-26521 RF Unit RX Channel
RTWP/RSSI Too Low and ALM-26522 RF Unit RX Channel
RTWP/RSSI Unbalanced are added to check whether the uplink RF
path is normal. By using the alarms, the problem location time and
operational expenditure are reduced.
Implementation RSSI monitoring is categorized into:
 RSSI below minimum threshold: It is used to check whether the
RSSI value exceeds the minimum threshold. When no services are
being processed, if 80% of RSSI values of the receive path are
below the minimum RSSI threshold, the alarm ALM-26521 RF
Unit RX Channel RTWP/RSSI Too Low is reported.
 RSSI unbalanced: It is used to check the quality difference
between the main and diversity received signals if the cables
between combined cabinets are disconnected. When services are
being processed, if more than 80% of RSSI differences between
the main and diversity received signals exceed the normal RSSI
threshold during a measurement period, the alarm ALM-26522 RF
Unit RX Channel RTWP/RSSI Unbalanced is reported.
Related Run the SET BTSRXUBP command to set the thresholds for
Operations reporting the alarms ALM-26521 RF Unit RX Channel RTWP/RSSI
Too Low and ALM-26522 RF Unit RX Channel RTWP/RSSI
Unbalanced.
Number
Feature ID None
57. One BBU Supporting 126 TRXs

Description The One BBU Supporting 126 TRXs feature increases the maximum
number of TRXs supported by a single baseband unit (BBU) from 72
to 126 in TDM transmission mode. With this feature, more TRXs can
be configured without increasing the number of BTSs.
Benefit This feature improves BTS service processing capability and reduces
capital expenditure (CAPEX) for operators.
Implementation BSC and BTS are configured with 12 E1s to process a maximum of
126 TRXs.
Related None
Operations

Number
Feature ID None
58. Intelligent Upgrade of Board Software

Description During a BTS upgrade, the Intelligent Upgrade of Board Software
feature can download files with software updates only. This reduces
the software upgrade duration.
Benefit This feature improves the upgrade efficiency.
Implementation The main control board checks whether the target and source
versions are consistent for a board. If they are consistent, the BTS
does not download files. If they are inconsistent, the BTS downloads
files from the BSC.
Related None
Operations

Number
Feature ID None
59. 21-Level RRU Cascading

Description The 21-Level RRU Cascading feature increases the cascading levels
of remote radio units (RRUs) from 6 to 21. With this feature,
services are not interrupted during a ring topology switchover.
Benefit In scenarios where RRUs and BBUs are spaced far apart, this
feature:
 Consumes fewer common public radio interface (CPRI) optical
fibers between BBUs and RRUs, reducing CAPEX for operators.
 Reduces the duration of a ring topology switchover, improving
service stability.
Implementation A single BTS is enabled to support a maximum of 21 levels of
cascaded RRUs.
The procedure for CPRI ring topology switchover has been
optimized so that the duration of a CPRI ring topology switchover is
reduced without interrupting ongoing services. This is done by
eliminating the need for CPRI fault switchover protection and
shortening the period during which hop times are detected.
Related 1. Run the SET BTSOTHPARA command to enable fast CPRI
Operations ring topology switchover.
2. Run the ADD BTSRXUBRD command to add an RRU.
Number
Feature ID None
60. Intelligent Battery Management

Description This feature provides the following functions:

 Automatically uses different battery management methods for
different power grids.
 Automatically protects batteries at high temperatures.
 Estimates the remaining power supply time of batteries when the
mains supply is off.
Benefit  Prolongs battery lifetime and reduces operation expenditure
(OPEX).
 Prolongs battery lifetime at high temperatures.
 Enables operators to take preventive measures before the battery
runs out of power.
Implementation  The power monitoring unit (PMU) measures the power-off times
and power-off duration of the mains supply and determines the
power grid class. In power grid class 1 and class 2, batteries can
enter the dormant state for a certain period rather than stay in the
floating charging state.
 When the battery temperature is higher than the value for
Temperature Alarm Upper Threshold minus 5 for 5 minutes, the
batteries start floating charging and no alarm is generated.
 When the battery temperature is higher than the value for
Shutdown Temperature for 5 minutes, batteries enter the high-
temperature protection state. In this case, the charging power to
batteries is turned off or the charging level is lowered.
 The PMU calculates the remaining power supply time of batteries
based on the remaining power capacity and the discharging
current, and displays the results in the command output if a user
runs the DSP BTSBATCAP command.
Related  To enable automatic switching between battery management
Operations methods, do as follows:
Run the SET BTSOTHPARA command with Battery Intelligent
Management Switch set to ON(On).
 To enable high-temperature protection for batteries, do as follows:
Run the SET BTSAPMUBP command with High Temperature
Shutdown Flag set to ENABLE(ENABLE), and with Shutdown
Temperature and Temperature Alarm Upper Threshold set to
appropriate values. The default values for Shutdown Temperature
and Temperature Alarm Upper Threshold are recommended.
 To query whether battery intelligent management has taken effect,
do as follows:
Run the DSP BTSPWR command to verify that the value for
Battery Intelligent Management Capability is Support and the
value for Battery Intelligent Management Switch is ON(On) in
the command output.
 To query the remaining power supply time of batteries, run the
DSP BTSBATCAP command.
Trouble Ticket G-OR-BTSBATIM
Number

61. CRAN CPRI O&M Capability Improvement

Description The CRAN CPRI O&M Capability Improvement feature manages
CPRI links and ports for BTSs in the Main Topology window of the
M2000. This feature provides the following functions:
 Queries information about CPRI ports and optical/electrical
modules.
 Displays the alarm status for the receive and transmit ports of the
RRU, GTMU, GBBP, and UBRI optical/electrical module in the
Main Topology window of the M2000.
 Queries and sets the threshold of the bit error rate (BER) at the
physical layer by running MML commands.
Benefit This feature improves the efficiency of locating CPRI link and port
problems, enhancing BTS maintainability.
Implementation 1. The BTS supports the function of querying and analyzing
information about optical modules and CPRI ports in the Main
Topology window of the M2000.
2. The BTS supports the function of displaying the alarm status for
the receive and transmit ports of the RRU, GTMU, GBBP, and
UBRI optical/electrical module in the Main Topology window
of the M2000. If alarms are reported by the optical module, the
alarm indicator next to the optical port displays the status of
only the alarm with the highest severity.
3. The BTS supports the function of setting and querying the BER
threshold at the physical layer by running MML commands.
The threshold can be set based on individual needs or left as the
default value.
Related  Run the DSP BTSCPRIPORT command to query static and
Operations dynamic information about CPRI ports.
 Run the DSP BTSOPTMODULE command to query information
about the specified UBRI optical/electrical module.
 Run the SET BTSCPRITHRESHOLD command to set the BER
threshold.
 Run the DSP BTSCPRITHRESHOLD command to query the
BER threshold.
Number
Feature ID None
62. Dynamic MA for GU Dynamic Spectrum Sharing (GSM)

Description With this feature, if the spectrum sharing function is enabled,

different mobile allocations (MAs) can be used before and after
spectrum sharing.
Benefit Before spectrum is shared, common and sharing TRXs (sharing
TRXs are enabled with spectrum sharing, and common TRXs are
not) can use the same MA. This increases frequency hopping (FH)
gains and decreases network interference.
Implementation Before spectrum is shared, all frequencies involved in FH for
common and sharing TRXs are configured in the same MA so that
all TRXs in a cell can use the frequencies in this MA.
When spectrum is being shared, the BSC divides the MA into two
smaller MAs, one for common TRXs and the other for sharing
TRXs. Then, the BSC blocks the TRXs using the MA for sharing
TRXs and activates the UMTS cells working on the same frequency
band as the frequencies in this MA. These UMTS cells now share the
spectrum with the GSM network.
After spectrum sharing is reclaimed, MSs are prohibited to access
these UMTS cells.
Related Run the SET GTRXCHANHOP command to set the MAs to be
Operations used before and after spectrum sharing. The following is an example:
SET GTRXCHANHOP: IDTYPE=BYID, TRXID=1000,
CHNO=5, TRXHOPINDEX=0, TRXMAIO=0,
TRXDSSHOPINDEX=1, TRXDSSMAIO=0;
Number
63. Support for GUI Components Used for Activating and Deactivating a Cell

Description Graphical user interface (GUI) components are added for activating and
deactivating a cell.
Benefit The added GUI components facilitate user operation and improve
maintenance efficiency.
Implementation In the Device Navigation Tree on the LMT, the options Activate Cell
and Deactivate Cell are added to the shortcut menu of every cell node.
Related Activating a cell

Operations To activate a cell, right-click the cell in the Device Navigation Tree on
the LMT and choose Activate Cell from the shortcut menu.
Deactivating a cell
To deactivate a cell, right-click the cell in the Device Navigation Tree

on the LMT and choose Deactivate Cell from the shortcut menu.
Trouble Ticket None
Number
Feature ID None
64. Support for the OML/RSL Connection Check Function

Description The OML/RSL connection check function checks signaling link
connections of a GSM BTS by checking the electronic bar code of
the BTS against the configured electronic bar code. This function is
applicable only in TDM mode.
Benefit This function can detect an incorrectly connected BTS signaling link.
A BTS that has an incorrectly connected signaling link fails to
provide services.
Implementation The OML/RSL connection check function checks the electronic bar
code of the base station against the configured one. If the detected
electronic bar code differs from the configured one, the BSC reports
the alarm Site signaling link connection mismatch. Applicable
scenarios:
 The function is applicable to the BTSs with small load on
signaling links because the function increases the load of signaling
links.
 The function is applicable to scenarios where multiple BTSs have
similar hardware and software configurations, because incorrect
connections of signaling links will not take effect on BTSs that
differ greatly from each other in the hardware and software
configuration.
Related To enable this function, run the SET BTSOMLDETECT command.
Operations In this step, set Whether to Enable OML Detection to Signaling
link check and BTS Bar Code to the BTS electronic bar code in the
network plan.
After an incorrectly connected signaling link is detected, reconnect
the signaling link or reconfigure the electronic bar code by
modifying associated parameters based on the network plane.
Trouble Ticket FF-002
Number
65. Support cross feeder test function

Description The BTS cross feeder test function of the GBFD-111202 O&M of
BTS feature enables radio frequency (RF) modules of a newly
deployed BTS to analyze signals that are sent or received and
quickly detect whether there are crossed pairs among cells that the
BTS serves.
Benefit This feature locates and rectifies crossed pairs that are not detected
when a BTS is deployed and eliminates potential risks, improving
the network quality.
This feature enhances the delivery efficiency and quality and reduces
the delivery cost by decreasing reworking.
Implementation Users can run the MML command STR BTSCROSFEEDTST on the
M2000 or LMT to start a cross feeder test on a BTS.
The BSC sends a cross feeder test request to the BTS through an
operation and maintenance link (OML).
The BTS performs the test and sends the test progress report and
results back to the BSC.
The BSC displays the test progress report and results in the
command output.
Related Run the following MML command to start a cross feeder test on a
Operations BTS:
STR BTSCROSFEEDTST: IDTYPE=BYID, BTSID=0,
MINFREQ=0, MAXFREQ=100;
Note: This test can only be performed on 3900 series base stations,
and the parameters Minimum Frequency and Maximum Frequency
must be set to values within the frequency range that the BTS
supports.
Number
66. Optimizing Abis over IP Transmission by Processing GSM PS Dummy Frames

Description The transmission of GSM PS dummy frames in Abis over IP mode is

optimized.
Benefit The transmission efficiency in Abis over IP mode is improved, and
network congestion is reduced.
Implementation The BSC only sends GSM PS dummy frames that carry the Uplink
State Flag (USF) to BTSs. However, the BTSs still send dummy
blocks to MSs over the Um interface.
The BSC compresses GSM PS dummy frames that carry the USF.
Related Run the SET GCELLPSOTHERPARA command with Abis IP
Operations Dummy Frame Optimization set to SUPPORT(Support).

Number
67. Support for Changing the OPC Online

Description Before this optimization, changing the Original Signaling Point Code
(OPC) had the following two restrictions:
1. To change an OPC bound with a GSM cell, users must first
deactivate the cell.
2. To change an OPC used by any M3LE on a BSC6900 in IP
transmission mode, users must be offline. The offline operation is
complex and interrupts services for a long time.
These restrictions are now lifted.
After the OPC is changed, the BSC releases services bound with the original
OPC.
Benefit The operation for changing the OPC is simplified and the
interruption duration is shorter.
Implementation Users no longer need to deactivate the cell before changing an OPC
bound with a GSM cell.
Users can now run the MOD OPC command to change an OPC
used by only one M3LE on a BSC6900 in IP transmission mode.
If an OPC is used by two or more M3LEs, users still need to set all subracks
to ineffective mode before changing the OPC.
Related In A over TDM mode, run the MOD OPC command to change the
Operations OPC. The following is shown as an example:
MOD OPC: SPX=1, SPCBITS=BIT14, SPDF=WNF, SPC=101;
In A over IP mode or TDM/IP dual-stack mode, change an OPC as
follows:
To query whether the OPC to be changed is used by any M3LE, run
the LST M3LE command.
If the OPC is used by one M3LE, run the MOD OPC command to
change the OPC. The following is shown as an example:
If the OPC is used by two or more M3LEs, do as follows to change
the OPC:
Run the following command to set all subracks to ineffective mode:
SET CFGDATAINEFFECTIVE:
Run the MOD OPC command to change the OPC. The following is
shown as an example:
Run the SET CFGDATAEFFECTIVE command to set all subracks
to effective mode.
Run the FMT DATA command to generate a data configuration file.
Run the RST BSC command to reset the BSC6900. The following is
shown as an example:
RST BSC: BSCID=0;
Trouble Ticket GBSC-OR-085
Number

Feature ID None
Modified Features
1. Support for Quick Identification of Single-user Tracing Files and Quick Entry of an
IMSI/TMSI/IMEI/MSISDN/TLLI
Description This function helps users quickly identify the tracing file about a
specific user from a great number of tracing files.
This function also enables the LMT to display the latest five IMSIs,
TMSIs, IMEIs, MSISDNs, or TLLIs when users initiate one of the
following functions on the LMT:
 Single User CS Trace
 Single User PS Trace
 Query Single-User Resources
 Remote Speech Channel Loopback
 Test Internal Speech Channel
Benefit Without this feature, user tracing files are named in the same
format. To find a tracing file, users need to open all tracing files and
search for key information elements (IEs).
With this feature, users can quickly find specific tracing files for
individual users from a great number of tracing files. In addition,
when initiating any of the previously-mentioned functions on the
LMT, users are prompted with the latest five IMSIs, TMSIs, IMEIs,
MSISDNs, or TLLIs for quick entry.
Implementation The naming conventions for single-user tracing files are optimized
so that the name contains the last four digits of the IMSI, TMSI,
IMEI, MSISDN, or TLLI of the user.
When initiating any of the previously-mentioned functions on the
LMT, users are prompted with the latest five IMSIs, TMSIs, IMEIs,
MSISDNs, or TLLIs for quick entry.
Related N/A
Operations
Trouble Ticket G-OR-TRACE

Number
2. Optimization of Operation Logs of Tracing and Monitoring Tasks

Description Key information has been added into operation logs for tracing and
monitoring tasks.
Benefit There is more information for later analysis purposes.
Implementation Key information (for example, Cell ID, IMSI, Link No.) has been
added into operation logs for tracing and monitoring tasks.
Related None.
Operations

Number
Feature ID MRFD-210801/MRFD-210802
3. Support for sensitive data protection

Description There is no plain text password for the operator user, FTP user, and
database of the BSC and BSC-related tools.
Improvement The security of the operator user, FTP user, and database is enhanced.
Implementation The plain text password for the BSC and BSC-related tools are
removed.
Related N/A
Operations
PR Number FF-024
4. Support for BSC security algorithm enhancement

Description An enhanced security encryption algorithm, AES256 encryption
algorithm, is used to protect the passwords for the BSC operator user
account and FTP user account.
Improvement The security of the operator user and FTP user is enhanced.
Implementation The AES256 encryption algorithm is used to protect the passwords

for the BSC operator user account and FTP user account.
Related N/A
Operations
PR Number FF-017
5. Support for SSL security enhancement

Description Secure Socket Layer (SSL) V2 has security problems and is not
recommended. When SSL is required, for example, when File
Transfer Protocol Over SSL (FTPS) is applied, users need to adopt
the SSL password protection enhancement policy.
Improvement The security of SSL communication is enhanced.
Implementation SSL V2 is prohibited.

Encryption algorithms with keys less than 64 bits and plain text
algorithms are removed.
Related N/A
Operations
PR Number FF-015
6. Optimization for Exporting Files by Running the EXP CFGMML Command

Description The name of the file exported by running the EXP CFGMML
command now contains the BSC6900 IP address. Running this
command now generates only compressed files.
Benefit The IP address in a file name helps users identify the source of the
file.
OMU hard disk space increases because all files in .txt format are
deleted.
Implementation The BSC6900 IP address is added to the name of exported files by
running the EXP CFGMML command.
Original files in .txt format are deleted once they are compressed.
Related Run the EXP CFGMML command to export the scripts.
Operations
Trouble Ticket CR GU00856, CR GU00864

Number
7. Utilization Optimization of 146-GB Hard Disk for the OMU

Description For an OMU whose hard disk space is 146 GB, the maximum space
for storing binary logs is expanded from 9 GB to 16.4 GB and the
maximum number of the logs is increased from 12,000 to 30,000. If
the maximum space or number is reached, a new log replaces the
earliest log.
Benefit The utilization of the OMU hard disk space is improved, and binary
logs can be kept for a longer time.
Implementation The OMU is monitoring its hard disk space for storing binary logs
and the number of the logs. The maximum space and number are
16.4 GB and 30,000, respectively.
Related None.
Operations

Number
Feature ID None.
8. Support for Security Log Optimization

Description The security log function is optimized by including the operation
records of commands ADD CCG and RMV CCG.
Benefit The optimized security log function has the following benefits:
 Helps users analyze system security and prevent potential attacks
on the system.
 Helps users trace the source of security threats.
Implementation When a user runs the ADD CCG or RMV CCG command, the
following information is recorded in the security log: Operator name,
Event Type, Event Level, Operation time, Detail Event, and IP
address.
Related N/A
Operations

Number
9. Support for the Optimization of Maintenance Mode Configuration

Description The optimization is as follows:

 Commands have been added to support configuration of the
following NE maintenance modes on the M2000 or LMT:
NORMAL, INSTALL, EXPAND, UPGRADE, TESTING,
ExpandStatus1, ExpandStatus2, ExpandStatus3, ExpandStatus4,
ExpandStatus5, ExpandStatus6, ExpandStatus7, ExpandStatus8,
ExpandStatus9, and ExpandStatus10.
 The data of NE maintenance mode is synchronized to the M2000
as configuration data.
 After an NE is set to work in maintenance mode, the following
alarms can be reported as usual: ALM-20047 Smoke, ALM-20043
Water Damage, ALM-20048 Theft Proof, ALM-20040 Overhigh
Subrack Temperature, ALM-25671 Smoke Alarm, ALM-25670
Water Alarm, ALM-25672 Burglar Alarm, and ALM-25602
Sensor Failure.
 In BSC6900 V900R014C00SPC200, this feature can export MML
scripts for an NE in normal operating status. In BSC6900
V900R014C00SPC300 and later versions, this feature cannot
export MML scripts for an NE in normal operating status.
Benefit  Users can run MML commands on the M2000 or LMT to set the
maintenance mode for an NE.
 Alarms indicating abnormalities in the equipment room can be
reported for NEs in maintenance mode so that users can respond
in a timely manner.
Implementation  The SET MNTMODE command has been added to set the
maintenance mode for a BSC.
 The SET BTSMNTMODE command has been added to set the
maintenance mode for a BTS.
 The LST STATUS command has been deleted. The LST
MNTMODE command has been added to list the maintenance
mode configuration of a BSC.
 The LST BTSSTATUS command has been deleted. The LST
BTSMNTMODE command has been added to list the
maintenance mode configuration of a BTS.
 The DSP MNTMODE command has been added for users to
query the current maintenance mode of a BSC.
 The DSP BTSSTATUS command has been modified for users to
query the current maintenance mode of a BTS.
Related Run the following command to set the maintenance mode of a BSC
Operations to Install:
SET MNTMODE: MNTMode=INSTALL,
ST=2011&10&20&00&00&00, ET=2011&10&21&00&00&00,
MMSetRemark="date 2011_10_19";
Run the following command to set the BTS with ID 0 to work in
EXPAND mode:
SET BTSMNTMODE: IDTYPE=BYID, BTSID=0, MNTMode=
EXPAND, ST=2011&10&20&00&00&00,
ET=2011&10&21&00&00&00, MMSetRemark="date

2011_10_19";
The maintenance mode of a BTS can be set to EXPAND or TESTING by

BTS ID or BTS name. If neither BTS ID nor BTS name is set, all the BTSs
are set to work in EXPAND or TESTING mode.
Run the following command to query the maintenance mode
configuration of a BSC:
LST MNTMODE:;
Run the following command to query the maintenance mode
configuration of a BTS with ID 0:
LST BTSMNTMODE: LSTTYPE=BYBSINFO, IDTYPE=BYID,
BTSID=0;
Run the following command to query the current maintenance mode
of a BSC:
DSP MNTMODE:;
Run the following command to query the current maintenance mode
of a BTS with ID 1:
DSP BTSSTATUS: IDTYPE=BYID, BTSID=1;
Number
10. Support for the Optimization of OMU Performance Measurement Mechanism

Description During the period that the OMU is reset or the active and standby
OMUs are switched over, performance statistics collected by the
OMU from the host are not saved as a result file. With the optimized
OMU performance measurement mechanism, the OMU will save the
statistics into a result file after the reset or switchover.
Benefit The performance statistics collected during the reset of the OMU or
the switchover of the active and standby OMUs will not be lost.
Implementation After the OMU is reset or the active and standby OMUs are switched
over, the OMU will check the performance statistics of the last
measurement period. If the statistics have not been saved into a result
file, the OMU will save them into a result file and report it to the
M2000.
Related N/A
Operations
Trouble Ticket MBSCSH-880

Number
11. Support for the Enhanced SBFD Detection

Description A route associated flag is added to the Single-Hop Bidirectional

Forwarding Detection (SBFD) mechanism. If the flag is applied and
the SBFD detection of an IP address fails, the route that uses the IP
address as its next hop is not used as an alternative route.
Benefit Users can choose whether to apply the route associated flag
according to their actual needs. This feature can increase the IP
transmission reliability.
Implementation The Route associated flag parameter has been added to the STR
IPCHK command. When the parameter is set to SBFD, the Route
associated flag parameter is set to YES by default.
When the Route associated flag parameter is set to YES and the
SBFD detection of an IP address fails, the BSC6900 automatically
isolates the route that uses the IP address as its next hop. When the
parameter is set to NO and the SBFD detection fails, the BSC6900
does not perform such an action.
Related Run the STR IPCHK command. When Check type is set to SBFD,
Operations set Route associated flag to an appropriate value. The following is
an example:
CARRYT=ETHPORT, PN=0,
MODE=CHECK_ON_PRIMARY_PORT, PEERIP="99.9.9.100",
WHETHERAFFECTSWAP=YES,
ROUTEASSOCIATEDFLAG=NO;
Run the LST IPCHK command to query the value of Route
associated flag. The following is an example:
%%LST IPCHK: SRN=0, SN=14, CHKN=0,
LstFormat=VERTICAL;%%
RETCODE = 0 Execution succeeded.
List IP Connectible Check

-------------------------
Subrack No. = 0
Subrack name = MPS
Slot No. = 14
Check Index = 0
Check type = SBFD
Carry port type = ETHPORT
Port No. = 0
Trunk group work mode = <NULL>
Trunk group No. = <NULL>
Check mode = Check on Active
Port
Multi hop BFD detect local ip = <NULL>
Backup port IP address = <NULL>
Backup port mask = <NULL>
Peer IP address = 183.23.95.5
My discriminator of BFD = 2
Whether affect the port swapping = YES
Min interval of BFD packet send [ms] = 100
Min interval of BFD packet receive [ms] = 100

Detect multiplier of BFD packet = 3

ARP packet time-out[s] = <NULL>
ARP packet resend times = <NULL>
Route associated flag = YES
Differentiated services code point = 56
(Number of results = 1)

Number
12. Support for Enhanced Load Sharing

Description Enhanced load sharing is designed for IP networking scenarios that

require reliable backup between active and standby ports or links.
With enhanced load sharing, single-hop bidirectional forwarding
detection (SBFD) or address resolution protocol (ARP) detection can
be implemented on sublinks in a link aggregation group (LAG), and
active and standby sublinks in an LAG can be switched over
manually. If detection on a sublink fails, active and standby sublinks
will be switched over automatically.
Benefit Enhanced load sharing brings the following benefits:
Ports on the same board can be configured to work in active/standby
mode.
Compared with switchover between active and standby ports,
switchover between active and standby sublinks shortens the time
taken by ARP reestablishment, which is caused by switchover
between active and standby ports or sublinks, and therefore avoids
service failures caused by ARP reestablishment.
Implementation When a non-revertive LAG in manual aggregation mode containing
active and standby sublinks is configured, the following functions
are enabled:
SBFD or ARP detection can be implemented on the active and
standby sublinks. When the detection fails, sublinks instead of ports
are switched over to recover services quickly.
Active and standby sublinks can be manually switched over.
Each packet complying with IEEE 802.3ah that is transmitted from a
port carries the active/standby flag of the port to regularly inform the
peer network element (NE) of the port's active/standby mode.
Accordingly, the peer NE performs switchover between the active
and standby ports of its own.
Related Perform the following operations:
Operations To add a non-revertive LAG in manual aggregation mode, run the
ADD ETHTRK command with Trunk group work mode set to
ACTIVE_STANDBY, Revertive type set to NON-REVERTIVE,
and Aggregation Mode set to MANUAL_AGGREGATION. The
following is shown as an example:
WORKMODE=ACTIVE_STANDBY, RT=NON-REVERTIVE,
LACPMODE=MANUAL_AGGREGATION,
FLOWCTRLSWITCH=ON;
To add a sublink, run the ADD ETHTRKLNK command with the
priority specified properly and the Trunk group work mode
parameter set to ACTIVE_STANDBY. The following is an
example:
ADD ETHTRKLNK: SRN=2, SN=26, TRKN=2, TRKLNKSN=26,
TRKLNKPN=2, WORKMODE=ACTIVE_STANDBY,
PORTPRI=101;
To add another sublink, run the ADD ETHTRKLNK command
with the priority specified properly and the Trunk group work
mode parameter set to ACTIVE_STANDBY. The following is an
example:


TRKLNKPN=2, WORKMODE=ACTIVE_STANDBY,
PORTPRI=102;
To set the IP address for an LAG, run the ADD ETHTRKIP
command. The following is shown as an example:
ADD ETHTRKIP: SRN=2, SN=26, TRKN=2, IPINDEX=0,
IPADDR="123.123.123.123", MASK="255.255.255.0";
To start SBFD detection on an LAG, run the STR IPCHK command
with Trunk group work mode set to ACTIVE_STANDBY and
Whether affect the port swapping set to YES. The following is an
example:
CARRYT=TRUNK, WORKMODE=ACTIVE_STANDBY,
TRUNKN=2, PEERIP="123.123.123.1",
WHETHERAFFECTSWAP=YES;
To start ARP detection on the standby sublink of an LAG, run the
STR IPCHK command with Trunk group work mode set to
ACTIVE_STANDBY and Check mode set to
CHECK_ON_STANDBY_TRUNKLINK. The following is shown
as an example:
STR IPCHK: SRN=2, SN=26, CHKTYPE=ARP,
CARRYT=TRUNK, WORKMODE=ACTIVE_STANDBY,
TRUNKN=2, MODE=CHECK_ON_STANDBY_TRUNKLINK,
BAKIP="123.123.123.10", BAKMASK="255.255.255.0",
PEERIP="123.123.123.100";
To switch over the active and standby sublinks manually, run the
SWP ETHTRKLNK command. The following is an example:
SWP ETHTRKLNK: SRN=2, SN=26, TRKN=2;
Trouble Ticket SOR-235
Number
13. More Precise Packet Loss Rate Measured by IPPM

Description The packet loss rate measured by the IP Performance Monitor

(IPPM) feature is precise to 1/100, which cannot facilitate
monitoring the IP transmission network quality. This feature changes
the precision of the packet loss rate measured by IPPM to 1/100000.
Benefit The transmission quality of the IP transmission network is monitored
more precisely.
Implementation 1. The unit of the packet loss rate measured by IPPM is changed to
1/100000.
2. The new counter VS.IPPM.Forword.Precise.Peak.DropRates is
added. The unit of this counter is 1/100, and its value is precise to
0.001.
Related To activate the IPPM function, run the ACT IPPM command. The
Operations following is an example:
ACT IPPM: ANI=0, PATHID=1, ISQOSPATH=NO,
LOSTPKTDETECTSW=OFF;
Start a task of link performance monitoring to observe the link status
in real time, as shown in the following figure:
Check the counter VS.IPPM.Forword.Precise.Peak.DropRates, as

shown in the following figure.

Number
14. Improved BSC6900 Maintainability

Description The maintainability of the BSC6900 using IP transport is improved

by enhancing the ping IP and trace IP functions.
The ping IP function is enhanced in RAN14.0 by increasing the
maximum size of IP detection packets for packet segmentation test
purposes. In earlier versions, the maximum size of IP detection
packets is too small to support packet segmentation tests.
The trace IP function is enhanced in RAN14.0 by specifying the hop
where IP tracing starts and the destination UDP port of the IP
detection packets. With the destination UDP port specified, the
BSC6900 checks whether the UDP port is used by the intermediate
transmission equipment. In earlier versions, the trace IP function can
be started only from the first hop of the source IP address. This leads
to a long detection time and inaccurate detection results.
Benefit The enhanced ping IP and trace IP functions improve BSC6900
maintainability.
Implementation The maximum size of IP detection packets has been increased from
1500 bytes to 3000 bytes.
New parameters BEGINTTL and UDPPORTID have been added
to the TRC IPADDR command. They specify the hop where IP
tracing starts and the destination UDP port of the IP detection
packets.
Related Run the following command with PKTSIZE set to 3000:
Operations PING IP: SRN=2, SN=26, SIPADDR="16.17.18.19",
DESTIP="22.22.22.1", CONTPING=NO, PKTSIZE=3000;
Run the following command to specify BEGINTTL and
UDPPORTID:
TRC IPADDR: SRN=2, SN=26, DESTIP="22.22.22.1",
BEGINTTL=1, MAXTTL=16, UDPPORTID=52889;
Number
15. Support for the Enhanced F5 Function

Description In BSC6900 V900R13C00SPC520, the F5 entity (F5 indicates the

O&M flow on virtual channel level) must be activated on the
BSC6900 so that the BSC6900 reports the ALM-21322 VCL Alarm
Indication Signal or ALM-21323 VCL Remote Alarm Indication
upon receiving an Alarm Indication Signal (AIS) or Remote Defect
Indication (RDI) cell from the peer equipment.
In BSC6900 V900R14C00B010, the F5 function is enhanced.
Therefore, the BSC6900 reports the ALM-21322 VCL Alarm
Indication Signal or ALM-21323 VCL Remote Alarm Indication
upon receiving an AIS or RDI cell regardless of whether the F5 entity
has been activated.
Benefit When the BSC6900 receives an AIS or RDI cell but the F5 entity is
not activated, the BSC6900 performs the following operations:
 Sets both the permanent virtual connection (PVC) and the path
carried by the PVC to the unavailable state to isolate services from
the faulty path
 Reports the two previously-mentioned alarms
These operations improve the O&M performance in ATM
transmission mode.
Implementation The SET INTBRDPARA command has been added. The
F5OamAlmSwitch parameter, which indicates whether to enable the
enhanced F5 function, has been added to this command.
Related To enable the enhanced F5 function, run the SET INTBRDPARA
Operations command. The following is an example:
SET INTBRDPARA: SRN=0, SN=14, BT=AOUa,
F5OamAlmSwitch=ON;
Number
Feature ID None
16. Support for the Modified Power Unit for Optical Ports

Description The transmit and receive power unit for optical ports is mW, but the
power unit for other transmission equipment is dBm. This difference
imposes difficulties in the deployment and routine maintenance. To
solve the problem, the transmit and receive power unit for optical
ports is changed to dBm in BSC6900 V900R014.
Benefit The power unit is now uniform. This facilitates the deployment and
routine maintenance.
Implementation The power value in the unit of mW is converted into the power value
in the unit of dBm with the following formula:
1 dBm = 10 x log(1 mW)
Related Run the DSP OPT command to query the transmit and receive power
Operations of an optical port. The following is an example:
DSP OPT: SRN=2, SN=14, BT=AOUc, PFMT=GROUP;
Number
17. IP Address Anti-Attack for OMU Internal Network

Description The FG2c, GOUc, FG2d, or GOUd board discards the received
packets of which the destination IP addresses are in the same
network segment as the IP address of the OMU internal Ethernet
adapter.
Benefit When many packets that are forwarded by an interface board to an IP
address in the OMU internal network segment, for example, the IP
address of an XPU board, there is an increase in the CPU usage of
the board to which the IP address belongs.
This feature prevents forwarding of such packets and therefore
avoids an increase in the CPU usage of the corresponding boards.
Implementation The FG2c, GOUc, FG2d, or GOUd board discards the packets of
which the destination IP addresses are in the same network segment
as the IP address of the OMU internal Ethernet adapter.
The OMUFWFLAG parameter is added to the SET IPGUARD
command to specify whether to forward packets of which the
destination IP addresses are the same as the IP address of the OMU
internal Ethernet adapter. This parameter is set to ON by default.
The statistics item "Number of packets discarded due to destination
IP addresses in the same network segment as the OMU internal
Ethernet adapter" is added to the output of the DSP IPSTAT
command.
Related To enable a specified interface board to forward packets to the IP
Operations address of the OMU internal Ethernet adapter, run the SET
IPGUARD command. The following is an example:
OMUFWFLAG=ON;
To prevent a specified interface board from forwarding packets to the
IP address of the OMU internal Ethernet adapter, run the SET
IPGUARD command. The following is an example:
OMUFWFLAG=OFF;
To query the number of packets discarded by a specified interface
board due to destination IP addresses in the same network segment
as the OMU internal Ethernet adapter, run the DSP IPSTAT
command. The following is an example:
DSP IPSTAT: SRN=0, SN=16;
Number
18. Support for Optimized Load Sharing Algorithm

Description Before the load sharing algorithm was optimized, signaling messages
sent to the same destination signaling point (DSP) were carried by a
maximum of 16 signaling links. As a result, signaling link resources
were not fully used if more than 16 signaling links were configured.
Now, load sharing can be performed on a maximum of 256 signaling
links.
Benefit Increased signaling link usage
Minimized signaling link congestion
Improved service reliability
Implementation The following restrictions have been lifted:
The result of performing the bitwise AND operation between the
signaling link mask of the MTP3 signaling linkset and the signaling
route mask of the corresponding DSP must be 0.
When the service mode is load sharing, the result of the bitwise AND
operation performed between the signaling link mask and signaling
route mask on its DSP must be zero.
If the parameter Traffic mode in the command ADD M3LKS is set to

M3UA_LOADSHARE_MOD, the service mode is load sharing.
The default value of the parameter SLSMASK in the command ADD N7DPC
is changed to B1111.
Related If IP transmission is used, perform the following steps:

Operations Run the following command to add a DSP whose signaling route
mask is B1111 and DSP bearer type is M3UA:
ADD N7DPC: NAME="A", DPX=0, SPX=0, SPDF=WNF,
DPC=1000, DPCT=STP, SLSMASK=B1111, BEARTYPE=M3UA;
Run the following command to add an M3UA link set whose
signaling link mask is B1111:
ADD M3LKS: SIGLKSX=0, DENO=0, LNKSLSMASK=B1111,
NAME="A";
If TDM or ATM transmission is used, perform the following steps:
Run the following command to add a DSP whose signaling route
mask is B1111 and DSP bearer type is MTP3:
ADD N7DPC: NAME="B", DPX=1, SPX=0, SPDF=WNF,
DPC=2000, DPCT=STP, SLSMASK=B1111, BEARTYPE=MTP3;
Run the following command to add an MTP3 link set whose
signaling link mask is B1111:
ADD MTP3LKS: SIGLKSX=0, DPX=1, LNKSLSMASK=B0000,
NAME="B";
Number
19. Interface Board Load Balancing

Description The Interface Board Load Balancing feature applies to scenarios

where IP over Iu or IP over A is used and multiple interface boards
carry service data and Iu/A interface signaling data.
Based on the comprehensive load of each interface board, this feature
balances load across these interface boards.
Benefit  Balanced load across interface boards
 Lower traffic volume across subracks in the case of inter-subrack
bandwidth insufficiency
Implementation The comprehensive load of an interface board equals the board load
or inter-subrack load, whichever is larger.
The following formulas are used to calculate board load and inter-
subrack load:
Board load = Actual board throughput/Maximum board throughput
Inter-subrack load = Inter-subrack traffic volume/Total inter-subrack
bandwidth
Note that activating this feature may cause load imbalance across IP
paths between the base station controller and the peer end. Activating
this feature may also cause load imbalance among the ports or
interface boards that carry the IP paths.
Related None
Operations
Trouble Ticket None

Number
20. Optimized Transmission Resource Modification Procedure

Description Previously, all transmission resource modifications are processed by

the MPU subsystem. With this optimization, the MPU subsystem
processes transmission resource modifications only when the
transmission bandwidth is changed.
Benefit 1. There are fewer message exchanges between the SPU and MPU
subsystems during RRC connection setups. This improves the MPU
subsystem performance.
2. The values of the VS.ANI.IP.Conn.Modify.Att and
VS.ANI.IP.Conn.Modify.Succ counters decrease because they are
measured on the MPU subsystem.
Implementation During RRC connection setups, the SPU subsystem checks whether
the transmission bandwidth is changed after a transmission resource
modification. If the transmission bandwidth is not changed, the SPU
subsystem does not send a transmission resource modification
request to the MPU subsystem.
Related None
Operations

Number
Feature ID None
21. The Parameter Reference is Optimized

Description The Parameter Reference is Optimized:
 Managed objects (MOs) and parameters that are not related to
configuration have been deleted.
 The description of some parameters, such as IsKey and Access, has
been corrected.
Benefit The accuracy of the parameter reference is improved.
Implementation Only configuration-related MOs and parameters are described in the

parameter reference.
For more information about the deleted MOs and parameters, see
“Appendix 7 MOs and Parameters deleted in the BSC6900
Parameter Reference”.
Related None
Operations

Number
Feature ID None
22. Support for both IBCA and DTM

Description The restriction that the Interference Based Channel Allocation

(IBCA) feature cannot be used with the Dual Transfer Mode (DTM)
feature has been lifted.
Improvement IBCA and DTM can be used at the same time.
Implementation The restriction on data configuration is lifted.

When both IBCA and DTM are enabled, only non-frequency-
hopping channels or baseband-frequency-hopping channels can be
allocated to the CS and PS services of a DTM MS. This ensures that
these channels use the same mobile allocation index offset (MAIO).
When all non-frequency-hopping channels or baseband-frequency-
hopping channels are occupied, the BSC initiates a channel
preemption request.
A DTM MS can preempt a TCH that is mapped onto a non-
frequency-hopping or baseband-frequency-hopping channel and has
a PDCH configured on the adjacent timeslot on the same channel.
If the TCH is occupied by a non-DTM MS, the BSC forcibly hands
the MS over to another TCH so that the DTM MS can successfully
preempt the TCH. If none of the TCHs is suitable, the channel
preemption for the DTM MS fails. In this case, the BSC suspends
the PS service and ensures the continuity of the CS service on the
original TCH.
Related Run the SET GCELLCHMGAD command. In this step, set IBCA
operation Allowed to YES and other IBCA-related parameters to appropriate
values.
Run the SET GCELLGPRS command. In this step, set Support
DTM to SUPPORT and other DTM-related parameters to
appropriate values.
Feature ID GBFD-117002/ GBFD-114151
23. Support for both VAMOS and IBCA

Description The restriction that the Interference Based Channel Allocation

(IBCA) feature cannot be used with the Voice services over
Adaptive Multi-user Orthogonal Subchannels (VAMOS) feature
has been lifted.
Improvement IBCA and VAMOS can be used at the same time.
Implementation The IBCA feature calculates the mutual interference between a

new call and all established calls that have the same Training
Sequence Code (TSC) as the new call.
If a SAIC- or VAMOSI-capable MS processes a new common
call, the IBCA feature takes the impact of high-order modulation
into account when estimating the carrier-to-interference ratio
(CIR) of the new call.
The IBCA feature enables the BSC to obtain the CIR by querying
the mapping between the CIR and quality level based on different
Alpha values. This increases the interference calculation accuracy
when the BSC calculates how much a new call interferes with
established calls.
The VAMOS feature prioritizes candidate MSs to be multiplexed
onto a channel based on their quality level.
Related Run the SET GCELLCHMGAD command. In this step, set
operation IBCA Allowed to YES, IBCA Flexible TSC Allowed to OFF,
and other IBCA-related parameters to appropriate values.
Run the SET GCELLVAMOS command. In this step, set
VAMOS Switch to ON and other VAMOS-related parameters to
appropriate values.
PR Number FF-10
Feature ID GBFD-115830/ GBFD-117002
24. Support for optimized Mute SAIC identification

Description This feature disables the interference handover, bad quality handover,
and TCHF-TCHH handover during the Mute Single Antenna
Interference Cancellation (SAIC) identification. This improves the
efficiency of Mute SAIC identification. Otherwise, Mute SAIC
identification fails if a quality-related handover is triggered during the
identification process.
Improvement The Mute SAIC identification efficiency is increased.
Implementation After sending a Mute SAIC identification request, the BSC starts a
timer during which interference handover, bad quality handover, and
TCHF-TCHH handover are disabled. The timer value is calculated as
follows:
(MuteSaicIdeTotalTime x MuteSaicIdeOnePrdTime +1) x 1s
Related N/A
Operations
25. Support for VAMOS channel multiplexing for concentric cells

Description This feature enables concentric cells to use the Voice Service over
Adaptive Multi-user channels on One Slot (VAMOS) function. The
following mechanisms have been modified for concentric cells: candidate
VAMOS user decision and VAMOS channel multiplexing decision.
Improvement VAMOS is supported in concentric cells. This expands the network
capacity of the GSM/EDGE Radio Access Network (GERAN) without
adding RF units or frequency resources.
Implementation The VAMOS channel multiplexing procedure for concentric cells has been
modified in the following ways:
Candidate VAMOS user decision
During channel assignment
 The following condition for the downlink receive level has been added
for candidate VAMOS users:
Downlink receive level >= DL Rx Lev. Thres. of VAMOS Calls + Rx Lex.
Thres. Offset During Assignment
 A concentric cell does not support VAMOS if the OPTILAYER
parameter is set to NoPrefer for the cell. If an overlaid subcell is
preferred for new calls, an AdapTive Cell Border (ATCB) offset is added
to the original ACTB threshold.
For accessed MSs
 The following condition for the downlink receive level has been added
for candidate VAMOS users:
Downlink receive level >= DL Rx Lev. Thres. of VAMOS Calls
 If the call is in the overlaid subcell, an ATCB offset is added to the
original ACTB threshold.
VAMOS channel multiplexing decision
VAMOS channel multiplexing triggered during channel allocation
 If an underlaid subcell is preferred for new calls:
If the traffic load on the cell exceeds the value of VamosMultLoadThd,
the BSC checks whether the call meets the condition for being a candidate
VAMOS user.
If the call can be a candidate VAMOS user, the BSC checks all candidate
VAMOS calls that have accessed the underlaid subcell, and then selects the
most suitable one and allocates the VAMOS half-rate (HR) channel in the
same timeslot as the new call to the new call.
If the call cannot be a candidate VAMOS user, the BSC allocates an idle
HR channel to the new call by following the normal channel allocation
procedure.
 If an overlaid subcell is preferred for new calls:
If the traffic load on the cell exceeds the value of
VamosIuoInnerLoadThd, the BSC checks whether the call meets the
condition for being a candidate VAMOS user.
If the call can be a candidate VAMOS user, the BSC checks all candidate
VAMOS calls that have accessed the overlaid subcell, and then selects the
most suitable one and allocates the VAMOS half-rate (HR) channel in the
same timeslot as the new call to the new call.
If the call cannot be a candidate VAMOS user, the BSC allocates an idle

HR channel to the new call by following the normal channel allocation

procedure.
VAMOS channel multiplexing triggered by an intra-cell handover
 If the traffic load on the underlaid subcell exceeds the value of
VamosMultLoadThd, the BSC selects some MSs that have accessed the
underlaid subcell and triggers intra-cell handovers to multiplex these
MSs in to fewer channels. When the traffic load on the cell drops below
the value of VamosMultLoadThd, channel multiplexing is stopped.
 If the traffic load on the overlaid subcell exceeds the value of
VamosIuoInnerLoadThd, the BSC selects some MSs that have
accessed the overlaid subcell and triggers intra-cell handovers to
multiplex these MSs in to fewer channels. When the traffic load on the
cell drops below the value of VamosIuoInnerLoadThd, channel
multiplexing is stopped..
Related Four parameters are involved in this feature:
Operations  VamosIntraHoDlRxlevThd(DL Rx Lev. Thres. of VAMOS Calls)
 VamosAssDlRxlevThdOffset(Rx Lex. Thres. Offset During
Assignment)
 VamosIuoInnerAtcbThd(ATCB Offset in Overlaid Subcell)
 VamosIuoInnerLoadThd(Load Thres. in Overlaid Subcell)
The following is an example of setting the preceding two parameters:
SET GCELLVAMOS: IDTYPE=BYID, CELLID=0, VamosSwitch=ON,
VamosAssSwitch=ON, VamosIntraHoDlRxlevThd=0,
VamosAssDlRxlevThdOffset=128, VamosIuoInnerAtcbThd=138,
VamosIuoInnerLoadThd=75;
26. Multi-Site Cell

Description The Multi-Site Cell feature optimizes the inter-module operand

allocation algorithm for a multi-site cell. and provides the following
specifications:
 8 carriers per subsite x 30 subsites
 12 carriers per subsite x 18 subsites
In addition, the primary carrier can be configured in a secondary
subsite.
Benefit This feature increases the capacity for a multi-site cell and meets
the BTS capacity requirement of high-speed railways and indoor
coverage.
Implementation  The maximum number of subsites is increased to 30 in a multi-
site cell, and the maximum number of carriers per subsite is
increased to 12.
 The DSP BTSLOCGRPMAINTRX command is added to query
the BTS-level deployment of the primary carrier in a multi-site
cell.
 The SWP BTSLOCGRPMAINTRX command is added to
relocate the primary carrier to another subsite.
The inter-module operand allocation algorithm is optimized to
support the configuration of the primary carrier in a secondary
subsite.
Related  To query the deployment of the primary carrier, run the DSP
Operations BTSLOCGRPMAINTRX command.
 To relocate the primary carrier to another subsite, run the SWP
BTSLOCGRPMAINTRX command.
Trouble Ticket G-OR-PSLOCGRP
Number
27. Supporting AMR Speech Versions During TCH Immediate Assignment

Description In versions earlier than BSC6900 V900R014C00, users are not

allowed to select adaptive multirate (AMR) speech versions in TCH
assignment after TCHs are allocated to MSs during TCH immediate
assignment. In BSC6900 V900R014, users are allowed to do so.
Benefit Users are allowed to select adaptive multirate (AMR) speech
versions in the preceding scenario. This increases the traffic volume
of AMR calls.
Implementation During TCH immediate assignment, AMR speech versions are
allowed only when TCHs are allocated to MSs and the AMR license
is valid. In this way, AMR speech versions can be used during
subsequent TCH assignment.
Related 1. Run the SET OTHSOFTPARA command with either
Operations Immediately Allocate TCHs to MOC or Immediately
Allocate TCHs to MTC set to YES, or both of them set to
YES.
2. Run the SET GCELLBASICPARA command with TCH
Immediate Assignment set to YES.
SET OTHSOFTPARA: IMMTCHMOC=YES,
IMMTCHMTC=YES;
IMMASSEN=YES;
AMR speech versions can be selected by default when TCH
immediate assignment is allowed.
Number
GBFD-115502
GBFD-115507
GBFD-110502
28. 2G PS Re-paging Flow Control

Description If the PCH is overloaded or the number of CPUS-level paging

messages exceeds a specified threshold, flow control is performed on
PS re-paging. (CPUS is short for CPU for Service.)
Benefit The impact of PS paging on CS paging is minimized so that CS
paging messages are preferentially processed.
Implementation 1. The BSC regards PS paging as re-paging if the interval between
the time a PS paging message was sent and the time the last
paging message was sent is within the period specified by the
Ready timer.
2. If the PCH is overloaded or if the number of PS paging
messages received within the period specified by Paging
Statistical Period exceeds 80% of Max PS Paging Message
Num in Period, the BSC discards the re-paging message.
Related 1. Run the SET BSCFCPARA command with PS Re-paging
Operations Flow Control set to ON(On). The following is an example:
SET BSCFCPARA: SECONDPSPGFCCTRL=ON;
2. Run the SET BSCPSSOFTPARA command with Ready
Timer set to a value the same as that on the SGSN. The
SET BSCPSSOFTPARA: ReadyTimer=44;
3. Run the SET BSCFCPARA command with both Paging
Statistical Period and Max PS Paging Message Num in
Period set to appropriate values. The following is an example:
SET BSCFCPARA: PGSTATPERIOD=1000,
PGMAXPSMSGNUMINPERIOD=660;
Trouble Ticket CR-GU00796
Number
29. Optimizing PS Service Configuration Enhancement

Description The Network-Controlled Cell Reselection (NC2) feature provides

configuration enhancement for PS services. With the enhancement,
the BSC preferentially allocates a dual-mode MS processing PS
services to a UMTS cell in a GSM/UMTS hybrid network.
Benefit  Balances the load between the GSM and UMTS networks.
 Improves user experience.
Implementation The SET GCELLRESELUTRANFDD command is added.
In this command:
The Network-controlled GSM-to-FDD Cell Reselection parameter
determines whether to enable forced network-controlled GSM-to-
FDD cell reselection.
The following parameters determine the conditions in which an MS
reports neighboring FDD cells in the Packet Measurement Report
message:
 FDD Multi-RAT Reporting
 FDD Reporting Offset
 FDD Reporting Threshold
 Min. RSCP Threshold 2 for PS FDD Reporting
 Min. Ec/No Threshold 2 for PS FDD Reporting
The Min. RSCP Threshold 2 for PS FDD Reporting or Min.
Ec/No Threshold 2 for PS FDD Reporting parameter specifies the
value for the information element (IE)
FDD_REPORTING_THRESHOLD_2 in the Packet Measurement
Order message sent to a dual-mode MS processing PS services.
In a GSM/UMTS hybrid network, if Network-controlled GSM-to-
FDD Cell Reselection is set to SUPPORT(Support), the BSC
sends a Packet Measurement Order message to a dual-mode MS
processing PS services. The message carries the following IEs:
 NETWORK_CONTROL_ORDER (with the value for NC2)
 FDD_MULTIRAT_REPORTING
 FDD_REPORTING_OFFSET
 FDD_REPORTING_THRESHOLD
 FDD_REPORTING_THRESHOLD_2
Based on the values of these IEs and the signal quality of
neighboring cells, the MS determines whether to send the BSC
measurement reports (MRs) containing neighboring cell information.
After receiving the MRs, the BSC hands over an MS whose TBF
connection duration reaches FDD Reselection Threshold to a
neighboring UMTS cell with the highest receive level among the
reported neighboring cells or instructs the MS to reselect such a
neighboring UMTS cell.
Related Run the SET GCELLRESELUTRANFDD command with
Operations Network-controlled GSM-to-FDD Cell Reselection set to
SUPPORT(Support), FDD Reselection Threshold set to the
default value, and FDD Multi-RAT Reporting, FDD Reporting
Offset, FDD Reporting Threshold, Min. RSCP Threshold 2 for
PS FDD Reporting and Min. Ec/No Threshold 2 for PS FDD

Reporting set to recommended values.

SET GCELLRESELUTRANFDD: IDTYPE=BYID, CELLID=0,
GSMTOFDDFORCENC2=SUPPORT, PsBestFddCellNum=1,
PsFddCellRptOff=0, PsFddCellRptThd=0,PsFddRptThr2Ecno=10,
PsFddRptThr2Rscp=10, FddReselTimeThd=2000;
Trouble Ticket S-OR-OSYSHOPARAOPT
Number
30. Randomizing Padding Bytes in PS Dummy Blocks and PSI13

Description A parameter is added to determine whether to randomize padding
bytes in PS dummy blocks and the Packet System Information (PSI)
13 message. If the padding bytes are randomized, when PS data
transmitted on different channels contains the same baseband
information and the frequency configuration in a cell causes
intermodulation interference, call drops due to intermodulation
interference decrease.
Benefit Call drops due to intermodulation interference decrease, and network
quality improves.
Implementation The Padding Byte Randomization parameter is used to determine
whether to randomize the padding bytes.
 If Padding Byte Randomization is set to SUPPORT(Support),
padding bytes are randomized.
 If Padding Byte Randomization is set to NOTSUPPORT(Not
Support), all padding bytes are set to 0x2B.
Related Run the SET GCELLPSOTHERPARA command with Padding
Operations Byte Randomization set to SUPPORT(Support).

Number
31. Adding Counters Related to the Number of Dummy Blocks with USF

Description The PS activity factor is calculated based on the proportions of

various data blocks, including data blocks using CS1 to CS4, data
blocks using MCS1 to MCS9, dummy data blocks with the USF, and
dummy data blocks without the USF.
In earlier versions, counters collect the total number of dummy
blocks without differentiating the type.
In this version, the following counters are added to calculate the
number of dummy blocks with the USF:
Number of Packet Downlink Dummy Control Blocks with Valid
USF on GPRS PDCH
Number of Packet Downlink Dummy Control Blocks with Valid
USF on EGPRS PDCH
Benefit Improved calculation avoids traffic congestion due to an inaccurate
PS activity factor.
Implementation The two counters are collected separately when the BSC schedules
downlink dummy blocks.
Related Subscribe to the two counters on the M2000.
Operations

Number
32. Adding Subsite-based Data Service Counters

Description In earlier versions, the Multi-site Cell feature measures subsite-based
counters related to voice services only. In this version, subsite-based
counters related to data services are also measured.
Benefit This feature enables users to quickly and accurately locate faults in
site-level data services and provides guidance for network
expansion, reducing operation and maintenance costs.
Implementation The following measurement units are added:
TBF Establishment and Release Performance Measurement for Cell-
level Subsite
RLC Data Transmission Performance Measurement for Cell-level
Subsite
Related Subscribe to cell-level subsite measurement objects on the M2000.
Operations
Trouble Ticket G-OR-PSLOCGRP

Number
33. Automatically Planned BTS Relocation Restriction

Description In versions earlier than GBSS14.0, an automatically planned BTS

provides services even after it is relocated.
In GBSS14.0, with the Automatically Planned BTS Relocation
Restriction feature, an automatically planned BTS is prohibited from
providing services after it is relocated.
Benefit This feature helps operators increase return on investment.
Implementation After this feature is enabled on the LMT or M2000, the M2000
checks the BTS configuration data on the BSC and the neighboring
cell information reported by the BTS during automatic planning. If
none of the neighboring cells reported by the BTS are planned
neighboring cells, the M2000 prohibits the BTS from providing
services.
Related  To enable this feature, run the SET BTSAUTOPLANCFG
Operations command with Relocation Restricted set to ON.
 After this feature is enabled, if operators intend to allow a BTS
relocation, run the RST AUTOPLAN command with Relocation
Allowed During Replanning set to YES.
Trouble Ticket GBSS14.0-IR-0111
Number
GBFD-510701
34. Ater RSL Flow Control

Description The GSM Flow Control feature incorporates the Ater radio signaling
link (RSL) flow control function. This function applies to Ater over
TDM when the BSC is configured in BM/TC separated mode. With
this function, the BSC performs flow control for optional services
when the RSL bandwidth is insufficient.
Benefit Improves network quality and equipment reliability, providing better
user experience.
Ensures stable processing of basic CS services when traffic is heavy.
Implementation The Ater RSL Flow Control parameter is added to determine

whether to enable Ater RSL flow control.
If RSL level-1 congestion occurs over the Ater interface, the BSC
stops sending maintenance-specific messages between the BM and
TC subracks.
If RSL level-2 congestion occurs over the Ater interface, the BSC
stops sending optional service-specific messages between the BM
and TC subracks.
Related Run the SET BSCFCPARA command with Ater RSL Flow
Operations Control set to ON(On). The following is an example:
SET BSCFCPARA: AterRslFcCtrl=ON;
Number
35. 2G/3G Neighboring Cell Automatic Optimization

Description With traditional neighboring cell measurement, users must query the
number of frequencies configured in the BA2 list and set the
Measurement Step parameter based on the number of frequencies.
With this feature, the BSC automatically calculates the value for the
Measurement Step parameter based on the number of frequencies
configured in the BA2 list.
Benefit This feature reduces manual operations, improving the usability for
neighboring cell measurement.
Implementation In the STR NCS command, the attribute of the Measurement Step
parameter is changed from mandatory to optional. If Measurement
Step is set, the set value is used for measurement. If Measurement
Step is not set, the BSC automatically calculates the value for
Measurement Step based on the number of frequencies configured
in the BA2 list and uses the calculated value for measurement.
Related Run the STR NCS command to start neighboring cell measurement
Operations without setting Measurement Step.
When the number of frequencies involved in a measurement task has reached

the maximum allowed number of frequencies, the information about
frequencies in unspecified neighboring cells is incorrect if you perform either
of the following operations:
Adding neighboring 2G cells.
Adding neighboring 3G cells when there are no neighboring 3G cells.
Trouble Ticket None

Number
36. GSM Flow Control

Description The GSM Flow Control feature optimizes signaling flow control
over the A interface.
Benefit Enhances system reliability.
Increases system capacity, creating new revenue growth
opportunities for operators.
Implementation Based on the cause value carried in the CREF message from the
MSC, the BSC determines whether the MSC is congested. If the
MSC is congested, the BSC increases the flow control level for
signaling over the A interface, which increases the number of service
requests to be flow controlled.
The settings of the following parameters are invalidated:
 Measurement Period of A Interface Signaling Arrival Rate
 A Interface Signaling Arrival Rate Threshold
 SCCP Congestion Level Threshold
 Threshold for Number of Connection Requests on A Interface
Related To activate signaling flow control over the A interface, run the SET
Operations BSCFCPARA command with Allow Flow Control Upon A
Interface Signaling Congestion set to YES(Yes).
To adjust the effect of signaling flow control over the A interface,
run the SET BSCFCPARA command with Lower Threshold of
Messages Discarded on A Interface set to an appropriate value. A
larger value for this parameter indicates that more service requests
will be discarded due to flow control.
Number
37. HUAWEI II Handover

Description The HUAWEI II Handover feature optimizes the following
handover mechanisms:
Load-based handover penalty mechanism
A penalty inheritance mechanism for load-based handovers is
added.
TCHF-TCHH handover processing mechanism
The TCHF-TCHH handover mechanism is optimized as follows:
 Provides more detailed uplink/downlink receive quality
thresholds for handover decision, improving the handover
decision accuracy.
 Optimizes the value range for AdapTive Cell Border (ATCB)
threshold for handover decision, which allows MSs at the high-
quality cell edge to reside on TCHHs and therefore improves the
cell capacity.
 Supports load hysteresis for load-based TCHF-TCHH handovers

to prevent frequent TCHF-TCHH handovers.

Quick PBGT handover
Quick power budget (PBGT) handovers and frequency offset
handovers are implemented independently.
Level offset is configured per neighboring cell so that different
level offsets can be set for a cell serving as a neighboring cell for
two cells at the same time.
Benefit  Reduces the possibility of ping-pong effect when load-based
handovers and other types of handovers are performed.
 Enables operators to flexibly control and adjust the cell capacity
and the proportion of TCHHs to all TCHs.
 Enables operators to flexibly select a handover algorithm for fast
movement, implementing differentiated mobility management
for users on the high-speed rail and other users.
 Provides an appropriate candidate cell for a handover, increasing
the handover success rate for high-speed users.
Implementation After a call is successfully handed over, the BSC checks whether a
load-based handover has been performed. If a load-based handover
has been performed and the call is still within handover penalty
period, the call remains in the handover penalty state until the
penalty period ends.
The parameters AMR TCHF-TCHH HO Quality Thres. Fine
Tune and Non-AMR TCHF-TCHH HO Quality Thres. Fine
Tune are added so that the value range for uplink/downlink
receive quality threshold is changed to [0, 70].
The value range for the ATCB threshold is changed to [-63, 255].
After a TCHF-TCHH handover is complete, the BSC no long
performs any TCHF-TCHH handover if the cell load does not
reach the preset threshold.
The parameter Quick PBGT Handover Enable is added to
control whether quick PBGT handovers are allowed when
triggering conditions are met. If Quick PBGT Handover Enable
is set to YES(Yes), quick PBGT handovers are allowed when
triggering conditions are met. If Quick PBGT Handover Enable
is set to NO(No), quick PBGT handovers are not allowed even
when triggering conditions are met.
The neighboring cell-level parameter Quick Handover Offset for
Neighbor Cell is added to allow different level offsets for a cell
serving as a neighboring cell for two cells at the same time. The
value of this parameter is used as an offset against the value for
Quick Handover Offset during quick PBGT handover decision.
Related  Run the SET GCELLHOFITPEN command to enable load-
Operations based handover penalty inheritance. The following is an
example:
SET GCELLHOFITPEN: IDTYPE=BYID, CELLID=0,
LoadHoPunishInheritSwitch=ON;
 Run the SET GCELLHOBASIC command to set the receive
quality thresholds for AMR TCHF-TCHH handovers and non-
AMR TCHH-TCHF handovers 69 and 21, respectively. The

INTRACELLHOEN=YES,
AMRFULLTOHALFHOQUALTHRESH=6,
NOAMRHALFTOFULLHOQUALTHRESH=2,
AMRF2HHOQUALTHFINE=9,
NOAMRH2FHOQUALFINE=1;
 Run the SET GCELLHOBASIC command to set the ATCB
threshold for AMR TCHF-TCHH handovers to –10. The
INTRACELLHOEN=YES,
AMRFULLTOHALFHOATCBTHRESH=-10;
 Run the SET GCELLHOBASIC command to set the load
threshold for stopping TCHF-TCHH handovers to 50%. The
INTRACELLHOEN=YES,
AMRFULLTOHALFHOALLOW=YES,
AMRFULLTOHALFHOTHRESH=60,
FullToHalfHoLoadStf=10;
 Run the SET GCELLHOBASIC command with Quick PBGT
Handover Enable set to YES(Yes). The following is an
example:
HOCTRLSWITCH=HOALGORITHM1, QUICKHOEN=YES,
QUICKPBGTHOEN=YES;
 Run the MOD G2GNCELL command with Quick Handover
Offset for Neighbor Cell set to an appropriate value. The
MOD G2GNCELL: IDTYPE=BYID, SRC2GNCELLID=0,
NBR2GNCELLID=1, NCELLTYPE=HANDOVERNCELL,
ISCHAINNCELL=YES,
CHAINNCELLTYPE=QUICK_HO_NCELL_TYPE_A,
ADJHOOFFSET=1;
Number CR GU01130
GBFD-510102

Description A capacity and quality-based TCHF-TCHH handover algorithm is

added.
Quick PBGT handover
 Quick power budget (PBGT) handovers and frequency offset
 Level offset is configured per neighboring cell so that different
Optimization of intra-cell handovers using the HUAWEI I Handover
feature
 The scope for bad quality (BQ) handovers is controlled.
 The scope and priority for interference handovers are controlled.
Benefit  Enables operators to flexibly adjust the cell capacity and the
proportion of TCHHs to all TCHs.
 Adjusts TCHFs/TCHHs for AMR and non-AMR calls based on the
cell load and call quality.
 Enables operators to flexibly select a handover algorithm for fast
movement, implementing differentiated mobility management for
users on the high-speed rail and other users.
 Decreases the call drop rate and increases the handover success
rate for intra-cell handovers using the HUAWEI I Handover
feature.
Implementation If the cell load is heavy and the call quality is higher than or equal to
the preset threshold, some MSs using TCHFs are allocated TCHHs.
If the cell load is light or the call quality is lower than the preset
threshold, some MSs using TCHHs are allocated TCHFs.
The Quick PBGT Handover Enable parameter is added to control
whether quick PBGT handovers are allowed when triggering
conditions are met. If Quick PBGT Handover Enable is set to
YES(Yes), quick PBGT handovers are allowed when triggering
NO(No), quick PBGT handovers are not allowed even when
triggering conditions are met.
serving as a neighboring cell for two cells at the same time. The
value of this parameter is used as an offset against the value for
Quick Handover Offset during quick PBGT handover decision.
The Bad Quality Handover Optimization Allowed parameter is
added. If this parameter is set to YES(Yes), only inter-cell BQ
handovers are allowed. If this parameter is set to NO(No), both intra-
and inter-cell BQ handovers are allowed.
The Interference Handover Optimization Allowed parameter is
added. If this parameter is set to YES(Yes), only intra-cell
interference handovers are allowed, and the priority for deciding
such handovers is lower than AMR TCHF-TCHH handovers. That is,
the priority for interference handovers is degraded from urgent to

common. If this parameter is set to NO(No), both intra- and inter-cell

interference handovers are allowed.
Related  Run the SET GCELLHOBASIC command to enable the capacity
Operations and quality-based TCHF-TCHH handover algorithm. The
INTRACELLFHHOEN=HOBASECAPANDQUAL;
 Run the SET GCELLHOBASIC command with Quick PBGT
Handover Enable set to YES(Yes). The following is an example:
QUICKPBGTHOEN=YES;
 Run the MOD G2GNCELL command with Quick Handover
Offset for Neighbor Cell set to an appropriate value. The
ISCHAINNCELL=YES,
ADJHOOFFSET=1;
 Run the SET GCELLHOBASIC command with Current HO
Control Algorithm set to HOALGORITHM1(Handover algorithm
I), and Intracell HO Allowed, BQ HO Allowed, and Interference
HO Allowed set to YES(Yes). The following is an example:
INTRACELLHOEN=YES, BQHOEN=YES,
INTERFHOEN=YES;
 Run the SET GCELLHOBASIC command with Bad Quality
Handover Optimization Allowed set to YES(Yes). The following is
an example:
BADQUALHOOPTALLOW=YES;
 Run the SET GCELLHOBASIC command with Interference
Handover Optimization Allowed set to YES(Yes). The following is
an example:
INTERHOOPTALLOW=YES;
Number CR GU01130
CR GU01265
GBFD-115522
GBFD-510102

39. Controlling Whether to Send LOAD INDICATION Messages

Description To comply with 3GPP TS 48.008, the Sending LOAD
INDICATION to the MSC parameter is added to specify whether
the BSC sends LOAD INDICATION messages to the MSC.
Benefit Users can use this feature in accordance with 3GPP TS 48.008.
Implementation The SendLoadIndicationToMSC parameter is added.

If this parameter is set to ON(ON), the BSC sends LOAD
INDICATION messages to the MSC. This increases data flow over
the A interface.
If this parameter is set to OFF(OFF), the BSC does not send LOAD
INDICATION messages to the MSC. This decreases the success rate
of incoming BSC handovers if a cell is overloaded.
Related Run the SET AITFOTHPARA command with Sending LOAD
Operations INDICATION to the MSC set to an appropriate value. The
SET AITFOTHPARA: CNNODEIDX=0,
SendLoadIndicationToMSC=ON;
Number
40. Support for Gb Interface NS Signaling Tracing

Description The Gb interface Network Service (NS) signaling tracing function

traces signaling messages at the NS layer over the Gb interface. This
helps users quickly locate faults.
Benefit Before this function was introduced, users used either of the
following two inefficient methods to locate a fault when the BSC
failed to interwork with the SGSN:
Analyzing NS signaling tracing logs saved on the BSC
Analyzing tracing results obtained from a signaling catcher
With Gb interface NS signaling tracing, users can quickly locate
faults.
Implementation This function is available on the M2000 and local maintenance
terminal (LMT). After starting a Gb interface NS signaling tracing
task, users can perform the following operations on the M2000 or
LMT:
 Browsing tracing results in real time
 Stopping and restarting tracing tasks
 Saving selected or all traced messages to a specific path
Also, users can browse and analyze saved tracing results offline.
Related 1. Log in to the LMT, and click Trace.
Operations 2. In Trace Navigation Tree, choose Trace > GSM Services, and
double-click Gb Interface NS Signal Trace.
3. In the displayed Gb Interface NS Signal Trace dialog box, set
the parameters to appropriate values.
4. Click Submit.
Trouble Ticket IR-GBSS14-NSTRACE-022
Number
Feature ID None
41. Acoustic Echo Cancellation (AEC)

Description The AEC feature recognizes and processes acoustic echoes but has
low detection accuracy. To enhance the detection accuracy, this
release optimizes the echo detection algorithm for AEC and adds
AEC performance measurement.
Benefit Enhances detection accuracy, restrains strong echoes, and improves
the user experience in terms of discontinuous voice when the calling
and called parties speak at the same time.
Facilitates AEC gain measurement.
Implementation The echo detection algorithm is optimized for AEC.
AEC performance measurement is added.
Related  To enable AEC, perform the following operations:
Operations Run the SET TCPARA command. In this step, set AEC Switch to
ON(On) and specify AEC Mode for the DPU board.
 To enable AEC performance measurement, perform the following
operations:
Run the SET OTHSOFTPARA command. In this step, set Enable
TC Performance Measurement to YES(Yes), and select the
AEC(AEC_Measurement) check box under the parameter TC
Performance Measurement Type.
Trouble Ticket None
Number
42. Automatic Level Control (ALC)

Description The ALC feature automatically adjusts the voice volume of both
parties during a call into a comfort range, but does not effectively
control the signal level if the voice volume fluctuates. To address this
problem, this release optimizes the gain adjustment module for ALC
and adds ALC performance measurement.
Benefit Improves ALC performance in scenarios where the voice volume
fluctuates.
Facilitates ALC gain measurement.
Implementation The gain adjustment module is optimized for ALC.
ALC performance measurement is added.
Related  To enable ALC to work in fixed level mode, perform the following
Operations operations:
Run the SET TCPARA command. In this step, set ALC Switch to
ON(On), ALC Mode to FIXEDLEVEL(Fixed level mode), and
ALC Fix Target Level to the recommended value for the DPU
board.
 To enable ALC to work in fixed gain mode, perform the following
operations:
ON(On), ALC Mode to FIXEDGAIN(Fixed gain mode), and ALC
Fix Gain to the recommended value for the DPU board.
 To enable ALC to work in adaptive mode, perform the following
operations:
ON(On), ALC Mode to ADAPTIVE(Adaptive mode), and ALC
Max Target Level and ALC Min Target Level to the recommended
values for the DPU board.
 To enable ALC performance measurement, perform the following
operations:
ALC(ALC_Measurement) check box under the parameter TC
Trouble Ticket None
Number
43. Automatic Noise Restraint (ANR)

Description During a voice call, the ANR feature decreases the noise level and
increases the signal-to-noise ratio, but does not effectively restrain
non-stationary noises. To address this problem, this release optimizes
the noise detection algorithm for ANR and adds ANR performance
measurement.
Benefit  Effectively restrains non-stationary noises, such as noises from
factories, streets, or super markets to make voices and music
clearer.
 Facilitates ANR gain measurement.
Implementation The noise detection algorithm is optimized for ANR.
ANR performance measurement is added.
Related  To enable ANR, perform the following operations:
Operations Run the SET TCPARA command. In this step, set ANR Switch to
UPLINK(On for uplink) or DOWNLINK(On for dnlink), Noise
Suppression Algorithm Switch to MODE1(Optimized version),
and Noise Attenuation Mode, Noise Suppression Mode, and
Transparent Transmit Thresh of Noise Lev to appropriate values
for the DPU board.
 To enable ANR performance measurement, perform the following
operations:
ANR(ANR_Measurement) check box under the parameter TC
Trouble Ticket None
Number
44. Automatic Noise Compensation (ANC)

Description During a voice call, if the background noise is strong at the local
end, the ANC feature adaptively raises the voice volume of the other
end to improve the voice quality. This release adds ANC
performance measurement.
Benefit Easy measurement for ANC gains
Implementation ANC performance measurement is added.
Related To enable ANC performance measurement, perform the following

Operations operations:
ANC(ANC_Measurement) check box under the parameter TC
Trouble Ticket None
Number
45. PS Power Control

Description The following functions are added: downlink GPRS closed-loop

power control, uplink EGPRS closed-loop power control, and slow
scheduling of uplink dummy blocks.
The downlink EGPRS closed-loop power control algorithm is
optimized to ensure that the current coding scheme does not change
to a lower-rate coding scheme due to tight power control.
The values Throughput preferred and Power control preferred are
added to the PS Power Control Policy parameter.
Benefit When an MS performs GPRS services, the BTS transmit power is
decreased and the High Quality Indicators (HQIs) of the network
increase.
Downlink EGPRS power control is now stable, which reduces
downlink call drops caused by power control fluctuation.
PS Power Control Policy can be set to Throughput preferred or
Power control preferred.
When an MS is performing EGPRS services, the BSC controls the
uplink transmit power and reduces the MS power consumption. This
improves the HQIs of the entire network.
The number of uplink dummy blocks decreases, reducing uplink
interference.
Implementation  Enhanced downlink EGPRS closed-loop power control
The BSC considers the effect of power control when it determines
whether to select a low-rate coding scheme based on the Mean-Bep
IE reported by an MS. This ensures that the BTS transmit power
decreases even if an MS uses a higher-rate coding scheme.
 Downlink GPRS closed-loop power control
The BTS transmit power is decreased when an MS performs GPRS
services and the downlink receive quality exceeds the specified
threshold.
 Power control policies
If PS Power Control Policy is set to 0(Throughput preferred),
downlink power control is performed without reducing the current
coding scheme. If PS Power Control Policy is set to 1(Power
control preferred), the BTS transmit power is minimized when the
current coding scheme is greater than or equal to DL EGPRS Power
Control Enable Coding Scheme Thres.
 Uplink EGPRS closed-loop power control
Based on the uplink measurement reports from the BTS, the BSC
dynamically adjusts the uplink transmit power of an MS performing
EGPRS services. With the uplink EGPRS closed-loop power control
function, the BSC decreases the MS transmit power without
compromising the MS uplink transmission performance.
Slow scheduling of uplink dummy blocks
The uplink extended TBFs during inactive periods are scheduled less
frequently, and the number of uplink dummy blocks sent by MSs is
reduced.
Related  Enabling downlink GPRS power control
Operations Run the SET GCELLPSPWPARA command with DL GPRS

Closed-Loop Power Control Support set to YES(Yes).

 Enabling the downlink EGPRS measurement report optimization
function
Run the SET GCELLPSPWPARA command with DL EGPRS
Closed-Loop Power Control Support and DL EGPRS Closed-
Loop Power Control MR Optimized set to YES(Yes).
 Setting the power control policy
Run the SET GCELLPSPWPARA command with PS Power
Control Policy set to 0(Throughput preferred) or 1(Power control
preferred).
 Enabling uplink EGPRS closed-loop power control
Run the SET GCELLPSPWPARA command with Uplink EGPRS
Closed-loop Power Control set to YES(Support).
 Enabling slow scheduling of uplink dummy blocks
Run the SET GCELLPSBASE command with Scheduling Period
for Inactive Periods set to an appropriate value.
Number
46. GSM/WCDMA Interoperability

Description In versions previous to GBSS14.0, handovers or cell reselections

from GSM to WCDMA are implemented using only single-threshold
mode but not dual-threshold mode, which is stipulated in the 3GPP
specifications. With this feature, handovers can be implemented with
dual-threshold mode on the GSM side by adding a field in the
system information.
Benefit Parameters related to handovers and cell reselections can be set
flexibly.
Implementation The field "3G ADDITIONAL MEASUREMENT Parameters
Description 2" is added to the system information 2Quater and
MEASUREMENT INFORMATION. A parameter is used to
determine whether this field is carried in the system information and
to specify the field value.
Related Run the SET GCELLCCUTRANSYS command.
Operations If FDD REP QUANT is set to RSCP(RSCP), set Min. Ec/No
Threshold 2 for FDD Reporting to enable the dual-threshold mode.
If FDD REP QUANT is set to EcN0(Ec/No), set Min. RSCP
Threshold 2 for FDD Reporting to enable the dual-threshold mode.
NOTE
To disable dual-threshold mode, set the corresponding parameter to
255.
Number
47. BSC Load Reallocation Supported by MSC Pool

Description In an MSC pool, when MSs registered on an MSC in the offload

state initiate location updates, the BSC reallocates these MSs to other
functioning MSCs proportionally. This feature requires that TMSI-
based MS reallocation be enabled on MSCs.
Benefit  Easy maintenance of network elements (NEs): The BSC allocates
loads on MSCs in an MSC pool without support from the CN.
 Fast reallocation of MSs: The related parameters are configurable
and users can determine the proportion of registered MSs.
 Easy operations: Enabling this feature does not require any
auxiliary tools.
Implementation  MSC Administrable State is set to OFFLOAD and MS

reallocation-related parameters are set on the CME or LMT.
 After an MS reallocation is started, MSs registered on an MSC in
the offload state are proportionally reallocated to other functioning
MSCs.
 New MSs accessing the network are not allocated to any MSCs in
the offload state.
 During execution of the STR MSCRSL command:

 If an MSC in the offload state has not started any MS reallocation, an MS
reallocation starts based on the settings of Reallocation Proportion and
Reallocation Duration.
 If an MSC in the offload state has started an MS reallocation, the MS
reallocation terminates and another MS reallocation starts based on the
settings of Reallocation Proportion and Reallocation Duration.
 If MSC Administrable State is set to NORMAL or UNAVAIL, the MS
reallocation terminates.
 If active and standby boards are reset simultaneously, the ongoing MS
reallocation is stopped. If an MS reallocation has been started on another
board that has not been reset, the status of MS reallocations becomes
inconsistent between boards. To resolve this problem, stop and then restart
MS reallocations.
Related 1. Run the MOD GCNNODE command with MSC

Operations Administrable State set to OFFLOAD(Offload), and with
Reallocation Proportion and Reallocation Duration set to
appropriate values. The following is an example:
MOD GCNNODE: CNNODEIDX=0, DPX=4, DPCGIDX=0,
OPNAME="Client", MSCCAP=1800, CNID=0,
MSCSTATUE=OFFLOAD, DFDPC=YES, PROPORTION=80,
PERIOD=50;
2. Run the STR MSCRSL command to start a load reallocation
task. The following is an example:
STR MSCRSL: CNNODEIDX=0;
Trouble Ticket G-OR-MSCPOOLREALLOC
Number

48. SI 2Quater Optimization

Description This feature provides the following functions:
 Optimizes the methods used to deliver the system information
2Quater and MEASUREMENT INFORMATION.
 Reduces the quantity of system information.
 Shortens the duration of PS service interruption during cell
reselection.
Benefit With this feature, the duration of PS service interruption decreases
during cell reselection.
Implementation  The SI 2Quater Optimization parameter is added.
 The neighboring UMTS cell list in 2Quater and MEASUREMENT
INFORMATION is flexibly delivered.
Related 1. Run the SET GCELLHOBASIC command with both Inter-RAT
Operations Cell Reselection Enable and Inter-RAT Out BSC Handover
Enable set to YES(Yes). The following is an example:
SET GCELLHOBASIC: INTERRATOUTBSCHOEN=YES,
INTERRATCELLRESELEN=YES;
2. Run the SET GCELLCCUTRANSYS command with SI 2Quater
Optimization set to YES(YES). The following is an example:
SET GCELLCCUTRANSYS: IDTYPE=BYID, CELLID=0,
SI2QUATEROPTIMIZEDALLOWED=YES
Number
Feature ID None
49. Optimizing the Measurement of Counters Related to Incoming BSC Handover Failures
and Counters Related to Call Drops

Description The Call Control feature optimizes the measurement of the following
counters:
 Counters related to call drops due to equipment failure
− In versions earlier than GBSS14.0,
when call connections are stable in IP or Flex Abis mode, if
Abis links become unavailable due to BTS faults, Clear
Request messages over the A interface carry the cause value
Um Interface Failure. Therefore, these messages are included
in the counter CM402-Number of Clear Requests Sent on the
A Interface (Um Interface Failure).
− In GBSS14.0, the measurement of Clear
Request messages is corrected, and the measurement of call
drops in the preceding scenario is optimized.
 Counters related to incoming BSC handover failures
Benefit This feature helps users to locate faults quickly and accurately.
Implementation  Counters related to call drops due to equipment failure

Assuming that call connections are stable in IP or Flex Abis mode:
− If Abis links become unavailable due to BTS faults, Clear
Request messages over the A interface carry the cause value
Equipment Failure so that these messages are included in the
counter CM401-Number of Clear Requests Sent on the A
Interface (Equipment Failure). This function is enabled by
default.
− If call drops occur because the Abis links become unavailable
due to BTS faults or the resource check performed in the
early morning shows that resources are inconsistent, these call
drops are included in the counters related to call drops due to
equipment failure. This function is controlled by the
Equipment Fail Call Drop Stat. Optimize parameter.
 Counters related to incoming BSC handover failures
The internal procedure is optimized so that the following counters
are measured to observe handover failures due to internal faults:
− H362-Failed Incoming Inter-RAT Inter-Cell Handovers:
During an inter-RAT incoming cell handover, the BSC
measures this counter if the handover fails due to a BSC
internal fault after the BSC receives an HO REQ message.
− CH342-Failed Incoming External Inter-Cell Handovers:
During an inter-BSC incoming handover, the BSC measures
this counter upon receiving an SCCP-initiated connection
release indication before the network connection
establishment is complete.
This function is controlled by the Stat. Optimization of Failed
Incoming BSC HO parameter.
Related  Run the SET OTHSOFTPARA command with Stat. Optimization
Operations of Failed Incoming BSC HO set to ON(On). The following is an
example:
SET OTHSOFTPARA: InHOFailStatOpt=ON;
 Run the SET OTHSOFTPARA command with Equipment Fail

Call Drop Stat. Optimize set to ON(On). The following is an

example:
SET OTHSOFTPARA: EquipFailDropOpt=ON;
Number
50. TFO
Description With this feature, the number of failed TFO establishments is
measured for each speech version in use and the TFO establishment
duration during a call is measured per cell.
Benefit TFO helps familiarize users with network conditions and optimize
networks.
 If TFO negotiation fails, the following counters corresponding to
different speech versions are measured:
− Number of Failed TFO Establishments (HR)
− Number of Failed TFO Establishments (FR)
− Number of Failed TFO Establishments (EFR)
− Number of Failed TFO Establishments (FAMR)
− Number of Failed TFO Establishments (HAMR)
− Number of Failed TFO Establishments (WBAMR)
 If TFO establishment succeeds, the TFO Establishment Duration
counter is measured regardless of speech versions. The TFO
establishment duration refers to the interval between a TFO is
successfully established and the corresponding call is released.
 The preceding measurements help users quickly and accurately
locate problems.
Related Run the SET GCELLBASICPARA command with TFO switch set
Operations to ENABLE(enable).
Run the SET OTHSOFTPARA command with Enable TC
Performance Measurement set to YES(Yes) and TC Performance
Measurement Type set to TFO(TFO measurement).
Trouble Ticket None
Number
51. VAMOS

Description In BSC6900 V900R014, Voice Services Over Adaptive Multi-User

Channels on One Slot (VAMOS) demultiplexing enables the BSC to
hand over a high-quality VAMOS call, but not a poor-quality
VAMOS call, to a common channel. In addition, BTS local
switching can be enabled for VAMOS services.
Benefit This reduces the VAMOS call drop rate and increases the handover
success rate, and saves transmission resources.
Implementation The BQ VAMOS Channel Demultiplex Optimize parameter is added.
After this parameter is set to ON(On):
For VAMOS calls, the BSC can trigger only one type of quality
based handover – BQ VAMOS demultiplexing handovers.
The BSC hands over high-quality VAMOS calls and triggers a
penalty for poor-quality VAMOS calls. During the penalty period
specified by BQ VAMOS Channel Demultiplex Penalty Period,
the BSC is not allowed to trigger an interference, BQ, or TCHF-to-
TCHH handover on poor-quality VAMOS calls.
In addition, the BTS notifies the BSC of whether VAMOS services
support local switching. If local switching is supported, the BSC
allows BTS local switching to be enabled for VAMOS services.
Related Run the SET GCELLVAMOS command with BQ VAMOS
Operations Channel Demultiplex Optimize set to ON(On). The following is an
example:
VamosSwitch=ON, VamosQualReuseSwitch=ON,
VamosQualUndoPntSwitch=ON, VamosQualUndoPntTimer=5;
Number CR GU01119
52. SAIC Capability Identification

Description In versions earlier than BSC6900 V900R014, Single Antenna

Interference (SAIC) capability data of MSs must be manually
exported as MML scripts and the data takes effect only after the
MML scripts are executed. In BSC6900 V900R014, the M2000
converts the SAIC capability data into MML scripts and
automatically imports the data into the BSCs for data sharing. In
addition, interchange between SAIC capability identification and the
following features is optimized: local switching and TFO.
SAIC capability identification consists of the Mute SAIC MS Identification

and VAMOS Call Drop Solution features.
Benefit Operation and maintenance (O&M) efficiency is increased because

the SAIC capability data of MSs is automatically imported into
BSCs for data sharing.
The SAIC capabilities of MSs can be more accurately identified.
Implementation SAIC capability identification is implemented as follows:
1. Users select source and target BSCs on the M2000.
2. The M2000 periodically instructs the source BSCs to export the
SAIC capability data of MSs.
3. The source BSCs export the data as MML scripts.
4. The M2000 obtains the MML scripts and combines them into a
single MML script.
5. The M2000 delivers this MML script to the target BSCs using
FTP.
6. The M2000 instructs the target BSCs to run the received MML
script.
If SAIC capability identification is required, local switching and TFO cannot

be enabled. As a result, the numbers of local switchings and TFOs decrease.
After SAIC capability identification is disabled, the numbers of local
switchings and TFOs return to normal.
Related Enable this function on the M2000.

Operations

Number
GBFD-115832
53. Setting Priorities for Encryption Algorithms

Description Traditionally, the priorities for encryption algorithms used over the
Um interface are, from high to low, as follows: A5/7 > A5/6 > A5/5
> A5/4 > A5/3 > A5/2 > A5/1 > A5/0, as stipulated in 3GPP
specifications. In Huawei GBSS14.0, users can set priorities for
these encryption algorithms.
The priority for encryption algorithm A5/0 cannot be set because A5/0 always
has the lowest priority.
Benefit Users can identify the priorities based on the security level of
encryption algorithms and select the highest-priority algorithm
available. This effectively enhances network security.
Implementation The following parameters are provided in the SET
GCELLBASICPARA command for setting the priorities for
encryption algorithms:
 Encryption Algorithm 1
where encryption algorithm 1 has the highest priority and encryption
algorithm 7 has the lowest priority. The priority for each encryption
algorithm must be unique.
The LST GCELLBASICPARA command is used to query the
priorities for encryption algorithms.
Related Run the SET GCELLBASICPARA command to set the priorities
Operations for encryption algorithms. The following is an example:
EncryptionAlgorithm1st=A51, EncryptionAlgorithm2nd=A52,
EncryptionAlgorithm3rd=A53, EncryptionAlgorithm4th=A54,
EncryptionAlgorithm5th=A55, EncryptionAlgorithm6th=A57,
EncryptionAlgorithm7th=A56;
Number
GBFD-113503
GBFD-113521
54. Dynamic Adjustment Between FR and HR

Description If a policy where half-rate traffic channels (TCHHs) should be

preferentially allocated to an MS is used, the BSC compares the
downlink receive level of the MS with a preset threshold during a
handover or a channel allocation. If the receive level is higher than
the threshold, the BSC preferentially allocates TCHHs to the MS. If
the receive level is lower than the threshold, the BSC preferentially
allocates full-rate traffic channels (TCHFs) to the MS.
During TCH allocation, when allocating TCHHs to MSs initiating
AMR calls, the BSC compares the loads in the underlaid and
overlaid subcells with different thresholds.
Benefit In normal situations, this feature increases the mean opinion score
(MOS) and improves the speech quality. However, if the traffic is
heavy, this feature decreases system capacity and lead to channel
congestion. The reason is that the BSC preferentially allocates
TCHFs instead of TCHHs to MSs that have too low signal levels and
poor speech quality.
In addition, this feature accurately controls the number of MSs
initiating AMR calls to access TCHHs in the overlaid and underlaid
subcells, relieving access congestion.
Implementation Assuming that the traffic volume exceeds TCH Traffic Busy
Threshold(%), or the traffic volume for AMR calls exceeds AMR
TCH/H Prior Cell Load Threshold when AMR TCH/H Prior
Allowed is set to YES(Yes):
 If the receive level of an MS is higher than Level Threshold for
TCHH Allocation, the BSC preferentially allocates TCHHs to the
MS.
 If the receive level of an MS is lower than Level Threshold for
TCHH Allocation, the BSC preferentially allocates TCHFs to the
MS.
The AMR Load Calculation Optimization parameter is added.
When this parameter is set to YES(Yes), AMR TCH/H Prior
Allowed is set to ON(On), and Load of UL-OL Cells Rate Select
Allowed is set to YES(Yes).
 If the overlaid subcell load is lower than the value for Threshold
for OL Load with AMR HR Preferred, the BSC allocates
TCHFs to MSs. Otherwise, the BSC allocates TCHHs to MSs.
 If the underlaid subcell load is lower than the value for Threshold
for UL Load with AMR HR Preferred, the BSC allocates
TCHFs to MSs. Otherwise, the BSC allocates TCHHs to MSs.
Related  Run the SET GCELLCHMGAD command with TCHH
Operations Allocation Considering Signal Level set to ON(On) and Level
Threshold for TCHH Allocation set to an appropriate value.
 Run the SET GCELLCHMGAD command with its parameters
set as follows:
− AMR TCH/H Prior Allowed is set to ON(On).
− AMR Load Calculation Optimization is set to YES(Yes).
− Load of UL-OL Cells Rate Select Allowed is set to YES(Yes).
− Threshold for OL Load with AMR HR Preferred and
Threshold for UL Load with AMR HR Preferred are set to

appropriate values based on network conditions.

Number
55. Optimizing 0.2 dB Power Control

Description In BSC6900 V900R014, the 0.2 dB power control algorithm is
optimized. 0.2 dB is compensated for power control, active power
control, or handovers. This increases the precision on downlink
power control and the accuracy of handover decision.
Benefit When HUAWEI III Power Control Algorithm and 0.2 dB power
control are enabled, this optimization reduces the BTS transmit
power, the SDCCH and TCH call drop rates, and the proportion of
high downlink signal levels.
The cell-level parameter 0.2 dB Power Control Optimization is
provided to control the optimization of 0.2 dB-step power control.
0.2 dB is compensated for power control, active power control, or
handovers when 0.2dB Power Control Enable is set to YES and 0.2
dB Power Control Optimization is set to ON.
A power control command is delivered when the following
conditions are met:
 For 2 dB-step power control, the power control levels during two
consecutive power control periods are the same.
 For 0.2 dB-step power control, the power control levels during two
consecutive power control periods are different.
The 0.2 dB-step power control level is considered when measuring
the Average BTS Power Control counter.
Related 1. Run the SET GCELLPWRBASIC command with Power
Operations Control Switch set to PWR3(Power control III) to enable
HUAWEI III Power Control Algorithm. The following is an
example:
SET GCELLPWRBASIC: IDTYPE=BYID, CELLID=0,
PWRCTRLSW=PWR3;
2. Run the SET GCELLPWR3 command with 0.2dB Power
Control Enable set to YES(Yes) and 0.2 dB Power Control
Optimization set to ON(On). The following is an example:
SET GCELLPWR3: IDTYPE=BYID, CELLID=0,
FINESTEPPCALLOWED=YES,
PwrFineCtlOptimizeSwitch=ON;
Number

56. Optimizing Active Power Control

Description In BSC6900 V900R014, the active power control algorithm is
optimized as follows:
Active power control is performed independently for signaling and
voice, as well as for the assignment and handover procedures.
The formula involved in the active power control algorithm is
optimized.
The BTS correctly determines the status of active power control
during measurement report preprocessing.
Benefit This feature provides the following benefits:
1. Enables users to flexibly set the active power control level,
reducing power consumption and interference.
2. Reduces the call drop rate and increases the assignment and
handover success rates.
The preceding benefits are obvious in densely-populated urban
areas.
Implementation  The Active Power Control Algorithm Optimize parameter is
provided to control the optimization of active power control.
 The Active Power Control Assign Power Offset and Active
Power Control HO Power Offset parameters are provided to
implement independent active power control for signaling and
voice.
 The formula for calculating the path loss in active power control is
optimized to ensure that dynamic power boost technology (PBT)
gain is taken into account during calculation of path loss and
power level.
 The BSC sends the value for Active Power Control Algorithm
Optimize to the BTS to ensure that the BTS correctly determines
the status of active power control.
Related Run the SET GCELLPWRBASIC command with the following
Operations parameters set to appropriate values: Power Forecast Allowed,
Active Power Control Algorithm Optimize, Active Power
Control Assign Power Offset, and Active Power Control HO
Power Offset. The following is an example:
SET GCELLPWRBASIC: IDTYPE=BYID, CELLID=0,
PWRBCDALLOWD=YES, PwrBCDOptimizeSwitch=ON,
PwrBCDAssOffset =2, PwrBCDHoOffset=2;
Number
57. Enhancing VGCS/VBS Reliability

Description This feature allows users to maintain and monitor voice group call
service (VGCS)/voice broadcast service (VBS) calls as follows:
 Query the list of cells processing VGCS/VBS calls.
 Query the resource occupation of a specified cell processing
VGCS/VBS calls.
 Release VGCS/VBS calls or uplink channels for VGCS calls.
 Check whether any uplink channels are occupied by VGCS calls.
Benefit This feature optimizes the maintenance and monitoring of
VGCS/VBS calls on the public network, and therefore increases
problem locating efficiency.
Implementation During a VGCS or VBS call, the BSC records the index of the cell
where the VGCS or VBS call is initiated and the resources occupied
by the VGCS or VBS speaker. After the DSP GRPCALLCELL and
DSP GRPCALLRES commands are executed with VGCS/VBS
No. and Service Type set to appropriate values, the information is
displayed on the LMT.
After the REL GRPCALL command is executed with VGCS/VBS
No., Service Type, and Release Mode set to appropriate values, the
BSC control connection sends a CLEAR REQUEST or UPLINK
RELEASE INDICATION message to the MSC. In this way, the
VGCS/VBS call or the VGCS/VBS speaker under the BSC is
released.
If VGCS Uplink Check Switch is set to ON(ON), the BSC checks
whether any uplink channels are occupied by VGCS calls. If the
uplink channels are abnormal, the BSC requests the MSC to release
these channels and updates the corresponding information.
Related  To query the list of cells processing VGCS/VBS, do as follows:
Operations Run the DSP GRPCALLCELL command, with VGCS/VBS No.
and Service Type set to appropriate values.
 To query the resource occupation of a specified cell processing
VGCS/VBS calls, do as follows:
Run the DSP GRPCALLRES command, with VGCS/VBS No.,
Service Type, Index Type, and Cell Index/Cell Name (as specified
by Index Type) set to appropriate values.
 To release VGCS/VBS calls or uplink channels occupied by VGCS
calls, do as follows:
Run the REL GRPCALL command, with VGCS/VBS No., Service
Type, and Release Mode set to appropriate values.
 To check whether any uplink channels are occupied by VGCS
calls, do as follows:
Run the SET OTHSOFTPARA command with VGCS Uplink
Check Switch set to ON(ON).
Number
GBFD-510302

58. Adding Counters Related to DSP CPU and Resource Usage in the CS User Plane
Description Counters specifying the TC DSP usage and TC channel usage have
been added to the BSC.
Benefit The new counters enable users to better evaluate the operating status
of the TC DSP, facilitating network optimization.
Note that this feature increases the value for the following counters:
 Sampling Times of DSP CPU Usage
 Average DSP CPU Usage
 Total Sampled DSP CPU Usage
Implementation The BSC automatically measures the following counters:
 Counters specifying the TC DSP usage, such as Maximum DSP
CPU Usage and Average DSP CPU Usage
 Counters specifying the TC channel usage, such as Maximum
Number of Activated TC Channels on a DSP and Minimum
Number of Activated TC Channels on a DSP
Related Subscribe to the new counters on the M2000.
Operations

Number
59. Fast Move Handover

Description With the Fast Move Handover feature:

 Quick power budget (PBGT) handovers and frequency offset
 Level offset is configured per neighboring cell so that different
Benefit  Enables operators to flexibly select a handover algorithm for fast
movement, implementing differentiated mobility management for
users on the high-speed rail and other users.
Implementation The Quick PBGT Handover Enable parameter is added to control
whether quick PBGT handovers are allowed when triggering
YES(Yes), quick PBGT handovers are allowed when triggering
NO(No), quick PBGT handovers are not allowed even when
triggering conditions are met.
serving as a neighboring cell for two cells at the same time. The value
of this parameter is used as an offset against the value for Quick
Handover Offset during quick PBGT handover decision.
Related Run the SET GCELLHOBASIC command with Quick PBGT
Operations Handover Enable set to YES(Yes). The following is an example:
QUICKPBGTHOEN=YES;
Run the MOD G2GNCELL command with Quick Handover Offset
for Neighbor Cell set to an appropriate value. The following is an
example:
ISCHAINNCELL=YES,
ADJHOOFFSET=1;
Number
60. Optimizing Counters Related to Transmission Call Drops

Description The 16Kbit RSL and OML on A-bis Interface feature optimizes the
counter measurement method to resolve the following problem:
The number of call drops due to BTS port faults is counted into the
counter M3330A-Call Drops due to Abis Link Failures in Stable Local
Switch State. In normal cases, M3330A is used to count the number of
link establishment failures in Flex Abis mode.
With the optimization, the number of call drops due to BTS port faults
is now counted into the counter CM333-Call Drops due to Abis
Terrestrial Link Failure (Traffic Channel).
Benefit The optimization improves user experience.
Implementation The Abis Territorial Link Fault Call Drop Stat parameter is added to
specify whether the number of call drops due to BTS port faults is
counted into the counter CM333. If this parameter is set to ON(On), the
number of call drops due to BTS port faults is counted into the counter
CM333.
By default, this parameter is set to ON(On) for newly-deployed sites
and to OFF(Off) for upgrade scenarios.
Related Run the MML command SET OTHSOFTPARA with Abis Territorial
Operations Link Fault Call Drop Stat set to ON(On).

Number
61. Shortening Service Interruption Duration Due to Handovers in Local Switching When
the Abis Interface Uses Satellite Transmission

Description The BSC Local Switch and BTS Local Switch features are optimized.
The optimization shortens the service interruption for calls that meet the
following conditions during local switching:
 The calls use AMR speech versions.
 The calls are involved in handovers.
 Satellite transmission is used over the Abis interface.
Benefit The feature optimization shortens the service interruption duration by
half and therefore improves user experience.
Implementation The procedure for initiating a handover for a call using AMR speech
versions is simplified. In this way, the number of messages transmitted
over the Abis interface decreases, shortening the service interruption
duration.
Related None
Operations

Number
GBFD-117702
62. IP Performance Monitor

Description The IP Performance Monitor feature is enhanced as follows:

 The BSC implements IP PM when link aggregation groups (LAGs)
work in active and standby mode.
 The BTS implements IP PM in IP over E1/T1 mode.
 The BTS allows the threshold for the IP PM Excessive Lost Packets
alarm to be configured.
 The BTS collects IP PM-related statistical data and reports the data to
the BSC.
Benefit The enhancements provide the following benefits, respectively:
 Improves link reliability.
 Reuses existing resources.
 Helps provide reliable link quality.
 Displays BTS IP PM-related counters on the M2000, facilitating
operation and maintenance.
Implementation  When LAGs work in active and standby mode, the BSC starts IP PM.
If the active and standby LAGs are switched over, the BSC restarts IP
PM and clears the previously measured counters.
 The BTS allows the threshold for the IP PM Excessive Lost Packets
alarm to be set. The default threshold is the same as that set on the
BSC side.
 The BTS reports IP PM-related statistical data to the BSC every
minute. The BSC then measures the corresponding counters. When a
measurement period arrives, the BSC reports these counters to the
M2000.
Related To activate BTS IP PM, run the ACT BTSIPPM command with its
Operations parameters set as follows:
 Index Type is set to BYID(By Index).
 BTS Index is set to the index of the target BTS.
 Service Type is set to the monitoring object.
 Lost Packet Detection Switch is set to ON(On).
Number

Description The names of some license control items have been changed. The
license usage measurement for these license control items has been
optimized. In addition, the configuration data for some of these
license control items will be checked during an upgrade.
Benefit  The license usage measurement for certain license control items is
more accurate.
 During an upgrade, if the upgraded tool determines that the
configuration data exceeds the license capacity, users are prompted
to delete the extra data within 60 days after the upgrade or to apply
for a new license that meets the requirements of the configuration
data. Otherwise, the configuration on the system will be limited
after 60 days.
Implementation  License control items corresponding to the following features have
been changed:
− TRX Working Voltage Adjustment Resource
− AMR HR Resource
− BSS Paging Coordination Resource
− TRX Power Amplifier Intelligent Shutdown Resource
− TRX Power Amplifier Intelligent Shutdown on Timeslot Level
Resource
− DTM Resource
− Enhanced Full Rate Resource
− EICC Resource
− ICC Resource
− Enhanced BCCH Power Consumption Optimization Resource
− Multi-Carrier Intelligent Voltage Regulation Resource
− Intersystem Handover & Reselection Resource
− TFO Support Resource
For users who have not used the preceding features, the
corresponding license control items are added. For users who have
used the preceding features, the license usage measurement of the
corresponding license control items is based on the number of TRXs
on which a specific feature is enabled.
 The upgrade tool will check the new license capacity when users
who have used the following features implement an upgrade:
− RX Working Voltage Adjustment Resource
− BSS Paging Coordination Resource
− Enhanced Full Rate Resource
− ICC Resource
− Multiple CCCH
− TFO Support Resource
If the configuration data for the license control items corresponding
to the preceding features exceeds the license capacity, users are
prompted to delete the extra data within 60 days after the upgrade or
to apply for a new license that meets the requirements of the
configuration data. If no action is taken, the ALM-20743 Insufficient

License Resources will be reported every day within 60 days, and the
configuration on the system will be limited after 60 days.
Related  To check whether configuration data of any license control items
Operations exceeds the license capacity, run the following command:
 To query the current usage of each license control item, run the
following command:
Trouble Ticket G-OR-SALE
Number
Feature ID None
Deleted Features
None.

New Hardware
Name Description
FG2d PARC WP11FG2d 12-port FE or 4-port electronic GE interface

unit REV:d
GOUd PARC WP11GOUd 4-port packet over GE Optical interface Unit
REV:d
NIUa PARC,WP11NIUa,Network Intelligence Unit REV:a
Modified Hardware
None.
Removed Hardware
None.



6.1.5 Alarm Updates

6.1.6 Event Updates



6.2 Resolved Issues

1. The BSC6900 cannot enter the emergency license state after a non-commercial license is
activated.
Number
Description After a non-commercial license is activated, the BSC6900 cannot

enter the emergency license state.
Severity Minor
Root Cause The optional feature License Control for Urgency is regarded as a
basic feature in BSC6900V900R013C00SPC500. However, the
BSC6900 cannot enter the emergency license state after a non-
commercial license is activated. This restriction needs to be removed.
Solution The preceding restriction is removed.
Solution Impact N/A
2. In the command output of the LST OMUIPRT command, the automatically and
manually added IP routes to the OMU are not differentiated.


Number
Description In the command output of the LST OMUIPRT command, the IP

route to the OMU added by running the ADD OMUIPRT command
and that added automatically when service data is configured are not
differentiated. As a result, when users run the RMV OMUIPRT
command to remove a manually added IP route, the automatically
added IP route may also be deleted mistakenly.
Severity Minor
Root Cause In the command output of the LST OMUIPRT command, there are
no fields to identify the route category.
Solution The Is Service Route field has been added to the LST OMUIPRT
command. If an IP route to the OMU is added by running the ADD
OMUIPRT command, the value of this field is NO. If an IP route to
the OMU is added automatically when service data is configured, the
value of this field is YES.
3. The ALM-20736 Data Inconsistency Between OMU and Host is reported too frequently.
Number
Description For a host-board CPU subsystem (CPUS), the ALM-20736 Data

Inconsistency Between OMU and Host is reported too frequently.
Severity Suggestion
Root Cause For a host-board CPUS, the ALM-20736 Data Inconsistency

Between OMU and Host is reported many times if data of several
tables of the CPUS saved on the host board is inconsistent with that
saved on the OMU.
Solution 1. The alarm parameter Data Table Name of the ALM-20736 Data
Inconsistency Between OMU and Host becomes invalid and its fixed
value is NULL.
2. The ALM-20736 Data Inconsistency Between OMU and Host will
be reported only once for a host-board CPUS if data of more than
one data table for the CPUS saved on the host board is inconsistent
with that saved on the OMU.
3. The alarm will be cleared only when the data of all tables of a
host-board CPUS saved on the host board is consistent with that
saved on the OMU.

4. Reliability of some counters is shown as Unreliable when the DST offset is an integer
multiple of the measurement periods of these counters.
Number
Description When the Daylight Saving Time (DST) offset is an integer multiple
of the measurement periods of some counters, Reliability of these
counters is shown as Unreliable during the first measurement period
after DST starts and ends.
This problem does not affect services.
Severity Suggestion
Root Cause Reliability of these counters is set to Unreliable.
Solution Reliability of these counters has been changed to Reliable.
Solution Impact Services are not affected.
5. The BSC6900 becomes out of service after an interface board is logically inhibited.
Number
Description If only one pair of A interface boards are configured, the BSC6900
becomes out of service if a user runs the INH BRD command to
logically inhibit the A/Iu interface boards.
Severity Suggestion
Root Cause The usage scenario of the INH BRD command is not considered
thoroughly and there is no restriction that this command cannot be
executed on the preceding scenario.
Solution A restriction is added to the INH BRD command: this command can
only be executed to logically inhibit or uninhibit a DPU or NIU
board.
Solution Impact The INH BRD command cannot be executed to logically inhibit an
XPU, INT, or TNU board. If this command is executed to logically
inhibit an XPU, INT, or TNU board, the BSC6900 returns a message,
indicating that this command cannot be executed on such a board.
6. No alarm is reported when the standby destination IP address of a dual-homing SCTP

link is unreachable.

Trouble Ticket N/A

Number
Description No alarm is reported when the standby destination IP address of a

dual-homing SCTP link is unreachable. In this case, the SCTP link is
unavailable and the services will be disrupted when the active
destination IP address also becomes unreachable.
Severity Minor
Root Cause The BSC6900 does not check the status of the standby destination IP
address for the SCTP link.
Solution 1.The execution result of the DSP SCTPLNK command now
contains The Primary Destination IP Address, which indicates the
current destination IP address of the SCTP link. If the link is faulty,
The Primary Destination IP Address is the value of the parameter
First destination IP address.
2.The alarm ALM-21543 SCTP Link IP Address Unreachable is
added. Now, the BSC6900 automatically checks both active and
standby destination IP addresses and reports the alarm when
detecting unreachable destination IP addresses.
Solution Impact N/A
7. Users cannot configure enough MTP3 routes and IP paths.


Number DTS2011082203465
Description Users cannot configure enough MTP3 routes and IP paths because of
certain specification restrictions. As a result, the BSC6900 does not
support a complex networking. So the networking reliability is
affected.
Severity Minor
Root Cause The following specification restrictions are responsible for this
problem:
Each Destination Signaling Point (DSP) can only be configured with
two MTP3 routes.
For the IP path configuration over the A or Iur-g interface, the
number of combinations of peer IP addresses and peer masks must
not exceed 256.
Solution The previously mentioned restrictions have been modified as
follows:
 Each DSP can be configured with a maximum of five MTP3
routes.
 Each M3UA destination entity can be configured with a maximum
of five M3UA routes.
For the IP path configuration over the A or Iur-g interface, the
number of combinations of peer IP addresses and peer masks must
not exceed 512.
8. The call drop rate increases in the process of replacing a transmission board or
disconnecting some of its cables.

Trouble Ticket N/A

Number
Description In the process of replacing a transmission board or disconnecting

some of its cables, services carried on the board or the cables are
interrupted. So the call drop rate increases.
Severity Minor
Root Cause There is no mechanism that prevents services from being interrupted
in the process of replacing a transmission board or disconnecting
some of its cables.
Solution The BLK IPPATH command has been added to prohibit new
services from being carried by the board by blocking an IP path.
Running this command does not affect ongoing services.
Users can replace the transmission board or disconnect its cables
after all the ongoing services are released. When the board is again
ready for service, the new UBL IPPATH command can be used to
unblock the IP path.
After the execution of the BLK IPPATH command, the ALM-21580
IP Path Blocked alarm is reported to inform users that an IP path has
been blocked. This alarm is cleared after the execution of the UBL
IPPATH command or the RMV IPPATH command.
To block an IP path, run the following command:
BLK IPPATH: ANI=1, PATHID=1;
To unblock an IP path, run the following command:
UBL IPPATH: ANI=1, PATHID=1;
Solution Impact N/A
9. The default TRMMAP setting is improper.


Number
Description Packets of certain high-priority services are discarded if a default

transport resource mapping (TRMMAP) setting is applied.
Severity Minor
Root Cause The default TRMMAP setting is improper.
Solution In the default TRMMAP setting, paths are re-mapped from AF43,
AF33, AF23, AF13, LQAF43, LQAF23, and LQAF13 to AF41,
AF31, AF21, AF11, LQAF41, LQAF21, and LQAF11, respectively.
The value range of the TRMMAP ID parameter in the MOD
TRMMAP command has been changed from 14–63 to 0–163. As a
result, the default transport resource mapping can be modified.
10. The performance measurement for the IP path ping process is inaccurate.
Trouble Ticket
DTS2011111706164
Number
Description When an IP path ping process is started for an IP path that is carried
on a logical port, the measurement result of the following
performance counters is inaccurate:
Average IP Path Ping Delay
Maximum IP Path Ping Delay
Severity Minor
Root Cause The interworking channel for an IP path ping process is always
carried on a physical port, regardless of whether the IP path is carried
on a logical or physical port. Therefore, the measurement result for
the IP path ping process is inaccurate if the IP path is carried on a
logical port.
Solution The software is modified to ensure that the interworking channel for
an IP path ping process is carried on the physical port if the actual
interworking channel for the IP path is carried on a physical port, and
that the interworking channel for the IP path ping process is carried
on the logical port if the actual interworking channel for the IP path is
carried on a logical port.
11. Severities defined for the alarms are incorrect.


Number
Description The severities defined for some alarms do not accurately reflect the
impacts of the reported issues.
Severity Minor
Root Cause Incorrect severities are defined for the alarms.
Solution In the alarm help, the severities of the alarms have been changed.
The severities of the following alarms are changed from "Warning"
to "Minor":
 ALM-20903 SAU Process Abort
 ALM-21203 E1/T1 Remote Alarm Indication Signal
 ALM-21225 IMA Link TX Unusable at Far End
 ALM-21232 IMA Group Activated Links Insufficient at Far End
 ALM-21243 Fractional IMA Link Remote Failure Indication
 ALM-21244 Fractional IMA Link TX Unusable at Far End
 ALM-21260 SDH/SONET LP Remote Failure Indication
 ALM-21324 VCL CC Activation Failure
 ALM-21327 VCL PM Activation Failure
 ALM-21328 VCL PM Configuration Failure
 ALM-22201 UMTS Cell Congested
 ALM-22207 UMTS Cell Reconfiguration Failed
 ALM-22233 IMB Cell Common Channel Setup Failed
 ALM-22502 UMTS Cell Broadcast Service Congestion
The severities of the following alarms are changed from "Minor" to
"Major":
 ALM-20205 System Clock Reference Source Unavailable
 ALM-20207 Failure in Locking System Clock Source
 ALM-20208 Clock Reference Source of Main Control Board
Unavailable
 ALM-20228 GE Link Between GE Switching Board and Service
Board Faulty
 ALM-20230 TDM Link Between TDM Switching Board and
Service Board Faulty
 ALM-20250 Sub-board Status Abnormal
 ALM-20734 License Inconsistency Between OMU and Host
 ALM-21231 IMA Group Activated Links Insufficient
 ALM-21290 Optical Module Mismatch
 ALM-21346 IP Connectivity Check Failure
 ALM-22209 UMTS Cell Common Channel Reconfiguration
Failed

12. The counter VS.AAL2PATH.PVCLAYER.DROPFORTXOVERFLOWCELLS is

measured incorrectly.
Number
Description The counter

VS.AAL2PATH.PVCLAYER.DROPFORTXOVERFLOWCELLS is
measured incorrectly for the AEUa, AOUa, and UOIa boards.
Severity Minor
Root Cause To obtain the measurement result of the counter

VS.AAL2PATH.PVCLAYER.DROPFORTXOVERFLOWCELLS,
the BSC6900 falsely measures the number of cells discarded from all
permanent virtual channels (PVCs) whose traffic volume exceeds the
configured bandwidth.
Solution The measurement mechanism for this counter has been rectified so
that the BSC6900 measures the number of cells discarded from a
single PVC whose traffic volume exceeds the configured bandwidth.
13. The configuration mode of the LMT login policy is not easy to use and poses security
risks.


Number
Description The LMT login policy is configured in the config.httpcfg file on the
OMU. The configuration mode is not easy to use and poses security
risks.
Severity Minor
Root Cause The management of the LMT login policy is not well designed.
Solution The original configuration mode of the LMT login policy is no

longer supported. The following MML commands have been added
to manage the LMT login policy:
LST WEBLOGINPOLICY: used to query the current LMT login
policy
SET WEBLOGINPOLICY: used to change the LMT login policy
Solution Impact Reconfigure the LMT login policy after old versions are upgraded to
the current version because the original one becomes invalid after the
upgrade. The new LMT login policy will be inherited during later
upgrades.
14. The file manager on the LMT has defects in terms of user rights management and
security management.


Number
Description The file manager on the LMT has the following defects:
ADMINISTRATOR-level users have permission to download and
delete files. Other users only have permission to download files. A
user's permission on files cannot be configured as required.
Domain users are regarded as non-ADMINISTRATOR users and
only have permission to download files.
There are no logs and therefore no security management.
Severity Minor
Root Cause The file manager is not well designed in terms of user rights
management and security management.
Solution 1. The 0X0310 and 0X0311 switches have been added to control
user permission on files.
The 0X0310 switch controls whether users can download files.
Turning on this switch grants user permission to read files in the file
manager.
The 0X0311 switch controls whether users can download, upload
and delete files. Turning on this switch grants user permission to
write into files in the file manager.
Local users' permission on files in the file manager has been
configured as follows:
ADMINISTRATOR-level users have permission to read and write
files. The permission cannot be changed.
 OPERATOR-, USER-, and GUEST-level users only have
permission to read files. The permission cannot be changed.
 CUSTOM-level users' permission to read/write files can be
configured. The details are as follows:
To configure user operation rights for CUSTOM-level users in a
user-defined command group, run the ADD CCG command and
select 0X0310 or 0X0311 for Command Name for the command
group:
Domain users' permission on files in the file manager has been

configured as follows:
On the Bound NE tab page on the M2000, bind the users to an NE
and assign the users a command group with the 0X0310 or 0X0311
switch turned on:

2. All the file download, upload, and deletion operations in the file
manager will be recorded in operation logs.
15. ALM-21341 IP PM Activation Failure is reported and cleared repeatedly, leading to

alarm message buffer overflow.
Number
Description During IP performance monitoring (IPPM) activation, the BSC6900

receives ACT_ACK packets but does not receive any BR packets
because the transmission network or the peer equipment is faulty. As
a result, ALM-21341 IP PM Activation Failure is reported and
cleared repeatedly. When users are activating a large number of
IPPM tasks, repeated alarm reporting and clearing leads to alarm
message buffer overflow, affecting the transmission of other alarm
messages.
Severity Minor
Root Cause As stipulated in IPPM protocols, if the BSC6900 receives

ACT_ACK packets, IPPM is successfully activated. Under this
circumstance, ALM-21341 IP PM Activation Failure should not be
reported even if the BSC6900 does not receive BR packets. This
alarm should be reported only when IPPM is reactivated and the
reactivation fails.
Solution The preceding alarm is reported only when the BSC6900 does not
receive ACT_ACK packets during IPPM activation.
Solution Impact If the BSC6900 receives ACT_ACK packets, the preceding alarm is
not reported. Users can run the DSP IPPM command to query the
IPPM status and packet exchange information.
16. Solving the problem that the CPU load has a sharp increase for a short period when the
system is in stable operation.


Number
Description The CPU load has a sharp increase for a short period when the
system is in stable operation.
Severity Minor
Root Cause The message scheduling algorithm is improper. As are result, a

massive of messages may need to be processed together.
Solution The message scheduling algorithm has been optimized.
Solution Impact Services are not affected.
17. CS users fail to access the network due to a lack of LVDS resources.
Trouble Ticket N/A
Number
Description CS users cannot preempt the Low Voltage Differential Signal

(LVDS) resources of PS users when the LVDS resources on the
backplane are insufficient for the BSC6900 Abis interface board that
supports Time Division Multiplexing (TDM) transmission. As a
result, CS users fail to access the network.
Severity Minor
Root Cause In the old algorithm, the BSC6900 rejects the access requests of CS
users when the LVDS resources on the backplane are insufficient.
Solution The CS user access algorithm has been optimized. CS users can now
preempt the LVDS resources of PS users when the LVDS resources
on the backplane are insufficient. In this way, access success rate for
CS users are not affected. However, access success rate for PS users
decreases while call drop rate and congestion rate for PS users
increase.
The ENPREEMPTABISLVDSADMT parameter has been added to
the SET BSCBASIC command. This parameter specifies the
preemption function.
The preemption function is enabled for new sites by default. For
exiting sites, whether this function is enabled depends on parameter
settings. The settings remain unchanged before and after an upgrade.
Run the following command to disable the preemption function:
SET BSCBASIC: ENPREEMPTABISLVDSADMT=OFF;
Run the following command to enable this function:
SET BSCBASIC: ENPREEMPTABISLVDSADMT=ON;
The preemption function is enabled by default.
Solution Impact N/A

18. The IP path cannot be changed on the BSC side when the IP address assigned by the
MGW changes in A over IP scenarios.
Number
Description If the new IP address assigned by the media gateway (MGW) is on a

different network segment from the old IP address during the handover
of a CS service, the IP path cannot be changed on the BSC side.
Severity Major
Root Cause The BSC uses the new IP address without updating the IP path.
Therefore, the BSC is connected to the old MGW by using the old IP
path.
Solution  If the new IP address assigned by the MGW is different from the old
one during the handover of a CS service, a pair of messages is added
in the BSC to request a new IP path. The new IP path must be
configured with the same local IP address and User Datagram
Protocol (UDP) port as the old one.
 The response message of the newly added messages contains the old
IP path under any of the following conditions:
− On the BSC side, the new and old local IP addresses are different.
− The new IP address assigned by the MGW and the old one are on
the same network segment.
− There is no matching IP path under the adjacent node determined
by the current routing matching method.
Solution None
Impact
19. DSP allocation is not even.


Number
Description If the number of calls processed by a data processing unit (DPU)

board reaches its limit, some DSPs are overloaded while others have
too light a load due to uneven digital signal processor (DSP)
allocation.
Severity Minor
Root Cause The main processing unit (MPU) allocates DSPs to DPU boards
based on the CPU usage of each DSP. However, there is a delay
before the MPU receives the CPU usage information reported by
each DSP. During the delay, the CPU usage on a DSP may increase
because it accepts more users. As a result, the MPU does not realize
that the CPU usage on this DSP has increased and may continue to
allocate this DSP to other users, in which case the DSP becomes
overloaded.
Solution Now a DSP reports its CPU usage as well as the CPU usage step and
number of activated paths to the MPU. The MPU determines
whether to continue to allocate this DSP to new users based on the
reported information and the number of assigned paths on each DSP,
which is saved on the MPU. This helps to prevent DSPs from
becoming overloaded.
A DSP rejects new users if its CPU usage exceeds 95%.
Solution Impact N/A
20. The downlink TBF establishment success rate is lower than the actual value.


Number DTS2011092800528
Description The BSC does not properly measure the counters related to the
downlink TBF establishment success rate. As a result, the downlink
TBF establishment success rate is lower than the actual value.
Severity Major
Root Cause When a downlink PDU initiates a downlink TBF establishment, the
BSC measures the counters related to the downlink TBF establishment
success rate as follows:
 If the TBF establishment fails, the BSC measures one TBF
establishment attempt and one TBF establishment failure. Then, the
downlink PDU initiates downlink TBF establishment retries based
on the value for Retry Times of Downlink TBF Establishment.
 Each time the downlink TBF establishment retry fails, the BSC
measures one TBF establishment attempt and one TBF
establishment failure.
However, from the perspective of an MS, if the first downlink TBF
establishment and subsequent downlink TBF establishment retries are
initiated by the same downlink PDU, only one TBF establishment
attempt and one TBF establishment failure should be measured.
Repeated measurements of TBF establishment attempt and TBF
establishment failure lead to the low downlink TBF establishment
success rate.
Solution 1. The method for measuring the counters related to the downlink
TBF establishment success rate has been optimized as follows:
When Retry Times of Downlink TBF Establishment is set to a
value greater than 0:
 If the first downlink TBF establishment initiated by a downlink PDU
is successful, the BSC measures one TBF establishment attempt and
one successful TBF establishment.
 If the first several downlink TBF establishments fail but the last
downlink TBF establishment initiated by the same PDU is
successful, the BSC measures one TBF establishment attempt and
one successful TBF establishment.
 If all downlink TBF establishments initiated by the same PDU fail,
the BSC measures one TBF establishment attempt and one TBF
establishment failure.
2. The parameters TDM Cell DL TBF Establishment
Measurement and IP Cell DL TBF Establishment
Measurement are added to the SET BSCPSSTAT command to
control the function of optimizing the measurement of the
downlink TBF establishment success rate.
 When TDM Cell DL TBF Establishment Measurement is set to
ON(ON), this function is enabled for TDM cells. When TDM Cell
DL TBF Establishment Measurement is set to OFF(OFF), this
function is disabled for TDM cells. The default value is OFF(OFF).
 When IP Cell DL TBF Establishment Measurement is set to
ON(ON), this function is enabled for IP cells. When IP Cell DL TBF

Establishment Measurement is set to OFF(OFF), this function is

disabled for IP cells. The default value is ON(ON).
Solution This function may increase the downlink TBF establishment success
Impact rate.
21. CIC allocation fails because of repeated allocations of a CIC over the A interface.
Trouble Ticket iCare: 166539
Number DTS2011061702076
Description The BSC allocates the same circuit identification code (CIC) to
different calls over the A interface when the Support Apply Used A
Cic parameter is set to No. This results in a CIC allocation failure
and causes an MS access failure.
Severity Critical
Root Cause The possible causes are as follows:

Because the BSC does not receive a GPRS Resume Ack message
from the PCU within a specified time, the BSC does not release the
CIC occupied by the current call upon receiving a Clear Command
message from the MSC. The MSC then requests the BSC to allocate
the CIC to another call.
In remote TC subrack configuration mode, the MSC requests the
BSC to reallocate a CIC if resource allocation fails over the Um
interface. Because the time sequence is reversed, the BSC may
allocate the CIC occupied by the current call again before releasing
it.
Solution Upon receiving a Clear Command message from the MSC, the BSC
releases the CIC without waiting for the GPRS Resume Ack message
from the PCU.
The BSC does not reallocate the CIC if resource allocation fails over
the Um interface and the CIC to be allocated is the same as that
occupied by the current call.
Solution Impact The solution increases the assignment success rate.
22. XPUa and XPUb are reset.


Number DTS2011090202243
Description When standard cell broadcast (CB) is enabled, the message packets
on the XPUa and XPUb are exhausted if the cell broadcast center
(CBC) sends a large number of cell broadcast messages to the BSC
within a short period. As a result, the XPUa and XPUb are reset.
Severity Major
Root Cause The BSC does not perform standard CB flow control.
Solution The following parameters have been added to perform standard CB

flow control:
 Flow Control over Standard CB
 Standard CB CPU Usage Start Thres.
 Standard CB CPU Usage End Thres.
 Standard CB Message Usage Start Thres.
 Standard CB Message Usage End Thres.
Where Flow Control over Standard CB specifies whether to enable
standard CB flow control.
Assuming that Flow Control over Standard CB is set to ON(On):
 The BSC starts standard CB flow control, discards all messages
from the CBC, and reports the event ALM-22901 Standard CB
Flow Control (indicating that flow control is in progress) if one of
the following conditions is met:
− The CPU usage of the standard CB subsystem is greater than or
equal to Standard CB CPU Usage Start Thres.
− The message packet usage of the standard CB subsystem is
greater than or equal to Standard CB Message Usage Start
Thres.
 The BSC stops standard CB flow control, processes the messages
from the CBC, and reports the event ALM-22901 Standard CB
Flow Control (indicating that flow control is stopped) if the
following conditions are met:
− The CPU usage of the standard CB subsystem is less than or
equal to Standard CB CPU Usage End Thres.
− The message packet usage of the standard CB subsystem is less
than or equal to Standard CB Message Usage End Thres.
The following counters have been added:
 Number of Cell Broadcast Messages the BSC Receives: provides
the number of standard cell broadcast messages received by the
BSC.
 Number of Cell Broadcast Messages the BSC Discards Due to
Flow Control: provides the number of standard cell broadcast
messages discarded by the BSC due to flow control.

23. The priority for a PS user to apply for an Abis link is incorrectly filled.
Number DTS2011090702169
Description The priority for a PS user to apply for an Abis link is incorrectly filled.
This adversely affects the PS call drop rate and CS access success rate
when Abis links are congested.
Severity Major
Root Cause If the Level of Preempting Dynamic Channel parameter in the SET
GCELLPSCHM command is set to LEVEL0(Preempt all dynamic
TCHFs) or LEVEL1(No preempt of CCHs), the value for the PS
Preferred PS Service Priority parameter in the SET
PSPREFABISCONGCTRL command is used as the priority for a PS
user to apply for an Abis link. However, the value for the CS
Preferred PS Priority parameter in the SET CSABISCONGCTRL
command should be used.
Solution The value for the CS Preferred PS Priority parameter in the SET
CSABISCONGCTRL command is now used as the priority for a PS
user to apply for an Abis link.
To prevent performance counter fluctuations after the BSC is upgraded
to V900R014, the upgrade tool has changed the value for CS
Preferred PS Priority in the SET CSABISCONGCTRL command
to the value for PS Preferred PS Service Priority in the SET
PSPREFABISCONGCTRL command.
Solution After the BSC is upgraded to V900R014, the value for CS Preferred
Impact PS Priority in the SET CSABISCONGCTRL command inherits the
value for PS Preferred PS Service Priority in the SET
PSPREFABISCONGCTRL command.
24. TBF-movement-related performance counters are incorrectly measured.


Number DTS2011101101795
Description The following counters are incorrectly measured:
 Number of Uplink GPRS TBF Movements Because of EGPRS User
Access
 Number of Downlink GPRS TBF Movements Because of EGPRS
User Access
Severity Minor
Root Cause The algorithm for measuring these counters is defective with a
maximum deviation of 100%.
Solution The algorithm for measuring these counters has been optimized.
Solution When there is a PDCH whose PDCH Channel Priority Type is set to
Impact EGPRSPRICH(EGPRS Priority Channel) in an EGPRS-capable
cell, the values for these counters may increase or decrease by a
maximum of 100% after the BSC is upgraded to V900R014.
25. Handovers due to TFO speech version incompatibility are incorrectly measured.
Number DTS2011061702141
Description If the speech versions used by the calling and called MSs are
incompatible at a site enabled with Tandem Free Operation (TFO),
the BSC hands over one of the MSs to another channel to make the
speech versions compatible. However, this type of handover
(handover due to TFO speech version incompatibility) is incorrectly
measured in the counters related to wideband AMR handovers.
Severity Major
Root Cause No counters are provided to measure handovers due to TFO speech
version incompatibility.
Solution The following counters have been provided to measure handovers due
to TFO speech version incompatibility:
 Number of Intra-BSC Handover Requests Due to TFO Speech
Version Incompatibility
 Number of Intra-BSC Handover Commands Due to TFO Speech
 Number of Failed Intra-BSC Handovers Due to TFO Speech
 Success Rate of Intra-BSC Handovers Due to TFO Speech Version
Incompatibility

26. The counter Number of Failed VAMOS Channel Multiplexing Attempts (Assignment) is
incorrectly measured.
Number DTS2011071903442
Description When Voice Services Over Adaptive Multi-User Channels on One Slot
(VAMOS) multiplexing during channel assignment fails, the value for
the counter Number of Failed VAMOS Channel Multiplexing
Attempts (Assignment) is 0.
Severity Minor
Root Cause Due to a code defect, the BSC does not measure this counter.
Solution The code defect has been rectified for the BSC to measure this counter
in the preceding scenario.
Solution None
Impact
27. The counter Number of Call Detect Messages Originated during Local Switching is
incorrectly measured.
Number DTS2011070401771
Description When the BSC initiates detection on local switching after a successful
intra-BSC handover, the value for the counter Number of Call Detect
Messages Originated during Local Switching is incorrect.
Severity Minor
Root Cause Due to a code defect, the BSC does not measure this counter.
Solution The code defect has been rectified to add the following measurement
point:
The BSC measures the counter Number of Call Detect Messages
Originated during Local Switching when the BSC initiates detection
on local switching after a successful intra-BSC handover.
Solution None
Impact
28. The counters related to outgoing BSC handover failures are incorrectly measured.


Number DTS2011072801936
Description When transmission over the A and Abis interfaces is abnormal, the
values for counters related to outgoing BSC handover failures are
incorrect.
Severity Minor
Root Cause Due to a code defect, the BSC does not measure these counters.
Solution The Internal Fault-Related KPI Measurement parameter in the

SET OTHSOFTPARA command is used to rectify the code defect
If this parameter is set to ON(ON), the BSC measures counters
related to outgoing BSC handover failures.
If this parameter is set to OFF(OFF), the BSC does not measure
these counters.
Solution Impact If Internal Fault-Related KPI Measurement is set to ON(ON), the
values for counters related to outgoing BSC handover failures may
increase.
29. The counters Successful Outgoing Inter-Cell Handovers (Downlink Strength) and
Successful Outgoing Inter-Cell Handovers (Load) are incorrectly measured.
Number DTS2011092004536
Description The BSC incorrectly measures the following counters:
 Successful Outgoing Inter-Cell Handovers (Downlink Strength)
 Successful Outgoing Inter-Cell Handovers (Load)
Severity Minor
Root Cause The BSC uses the CURR method instead of the SUM method to
measure the two counters.
Solution The method for measuring the two counters has been changed to
SUM.
Solution Impact The values for the two counters increase.
30. The counters related to inter-BSC outgoing cell handovers are incorrectly measured.


Number DTS2011081101695
Description When timers T7 and T8 expire during an outgoing BSC handover for
CS-domain data services, the values for the counters related to inter-
BSC outgoing cell handovers are incorrect.
Severity Minor
Root Cause Due to a code defect, the BSC does not measure these counters.
Solution The CSD Outgoing BSC HO Failure Stat. parameter has been added
to the SET OTHSOFTPARA command to rectify the code defect.
If this parameter is set to YES(Yes), the BSC measures the following
counters:
 Failed Outgoing External Inter-Cell Handovers (T7 Expiry) (TCHF)
(Traffic Channel)
 Failed Outgoing External Inter-Cell Handovers (T7 Expiry) (TCHH)
(Traffic Channel)
 Failed Outgoing External Inter-Cell Handovers (T8 Expiry) (TCHF)
(Traffic Channel)
 Failed Outgoing External Inter-Cell Handovers (T8 Expiry) (TCHH)
(Traffic Channel)
If this parameter is set to NO(No), the BSC does not measure any of
the preceding counters.
Solution If CSD Outgoing BSC HO Failure Stat. is set to YES(Yes), the
Impact values for the preceding counters may increase.
31. The counter Call Drops on Traffic Channel is incorrectly measured.


Number DTS2011052703759
Description In Abis over IP or Flex Abis mode, if links fail to be established over
the Abis interface, the value for the Call Drops on Traffic Channel
counter is incorrect.
Severity Minor
Root Cause The method for measuring the Call Drops on Traffic Channel counter
is incorrect.
Solution The Equipment Fail Call Drop Stat. Optimize parameter has been
added to the SET OTHSOFTPARA command.
If this parameter is set to YES(Yes), the BSC measures the counter
Call Drops on Traffic Channel.
If this parameter is set to NO(No), the BSC does not measure the
counter.
Solution If Equipment Fail Call Drop Stat. Optimize is set to YES(Yes), the
Impact value for the Call Drops on Traffic Channel counter may increase.
32. The value for the P0 field in the packet assignment message is incorrect.
Number DTS2011111202255
Description When downlink EGPRS power control is enabled in a cell, if P0 is set
to a value other than DB0(0dB), the value for the P0 field in the
packet assignment message is twice the configured value. This lowers
the MS uplink transmit power.
Severity Minor
Root Cause The value for the P0 field in the packet assignment message is
incorrect.
Solution The algorithm for assigning the P0 field has been optimized.
Solution After the BSC is upgraded to V900R014:

Impact  The uplink transmit power for an MS processing PS services
increases by the configured value for P0.
 The uplink TBF call drop rate and high quality indicator (HQI)
decrease by less than 1%.
You can run the SET GCELLPSPWPARA command to increase the
value for GAMMA so that the MS uplink transmit power restores to
its original value.

33. The counter Number of Preferable Selections of TCHH in a Cell (Abis Resource
Congestion) is incorrectly measured.
Number DTS2011081802853
Description The value for the counter Number of Preferable Selections of TCHH
in a Cell (Abis Resource Congestion) is 0 in scenarios with half-rate
TCHs (TCHHs) preferentially allocated when resources are congested
on the Abis interface in IP, HDLC, or Flex Abis networking mode.
Not all the related networking modes are provided in the description of
this counter.
Severity Minor
Cause This counter is not measured if TCHHs are preferentially allocated in

the preceding condition.
Solution This counter is increased by one each time a TCHH is preferentially
allocated to an MS because of Abis resources congestion in IP, HDLC,
or Flex Abis networking mode.
The description of this counter is corrected as follows: This counter
provides the number of times TCHHs are preferentially allocated in a
cell because of Abis resource congestion when the BSC performs CS
services in IP, HDLC, or Flex Abis networking mode.
Impact None
34. Inter-RAT load-based handovers fail on some MSs in the access state.


Number DTS2011033104542
Description In the algorithm for Iur-g interface-based load balancing between
GSM and UMTS, inter-RAT load-based handovers fail on some MSs
in the access state.
Severity Major
Root Cause The length of the inter-RAT directed retry timer is permanently set to
4s. Within the timer length, some MSs in the access state fail to report
information about neighboring WCDMA cells to the BSC. When this
happens, inter-RAT load-based handovers fail on these MSs in the
algorithm for Iur-g interface-based load balancing between GSM and
UMTS.
Solution The Inter-RAT Directed Retry Timer parameter has been added for
users to customize the length of the inter-RAT directed retry timer.
Solution A larger value for Inter-RAT Directed Retry Timer indicates a
Impact higher success rate for inter-RAT load-based handovers for the MSs in
the access state but a longer call access duration for some MSs.
35. The number of successful Intra-BSC handovers is greater than the number of detected
intra-BSC handovers.
Number DTS2011102803522
Description The number of successful intra-BSC handovers is greater than the
number of detected intra-BSC handovers when the BSC receives a
Clear Command message before receiving a Handover Detect
message.
Severity Minor
Root Cause The BSC measures the number of successful intra-BSC handovers but
does not measure the number of detected intra-BSC handovers.
Solution The measurement method has been optimized for the BSC to measure
both the number of successful and detected intra-BSC handovers in
the preceding scenario.
Solution The values for the following counters increase:
Impact  Number of Incoming Internal Inter-Cell Handover Detection
Messages Received by BSC
 Internal Intra-Cell Handover Detection Messages Received by BSC
 Successful TCH Seizures in TCH Handovers (Traffic Channel)
The value for the counter Call Drop Rate on TCH per cell (Including
Handover) decreases.

36. Rate of VGCS TCH Uplink Call Drop Exceeds 100%.

Number DTS2011101004963
Description During inter-cell handovers for voice group call service (VGCS) calls,
the calculated value for the counter Rate of VGCS TCH Uplink Call
Drop exceeds 100%.
Severity Minor
Root Cause The denominator of the formula for calculating the counter does not
include the numbers of successful intra- and inter-BSC incoming VGCS
handovers.
Solution The numbers of successful intra- and inter-BSC incoming VGCS
handovers have been added to the denominator.
Solution Impact The northbound interface is affected.
37. The number of successful incoming BSC handovers is greater than the number of
detected incoming BSC handovers.
Number DTS2011060400104
Description The number of successful incoming BSC handovers is greater than the
number of detected incoming BSC handovers when the following
conditions are met:
The BSC receives a Clear Command message with the cause value
Call Control before receiving a Handover Detect message.
In BSC Clear Command Statistics Opt Sw is set to ON(On).
Severity Minor
Root Cause The BSC measures the number of successful incoming BSC handovers
but does not measure the number of detected incoming BSC
handovers.
Solution The measurement method has been optimized for the BSC to measure
both the number of successful and detected incoming BSC handovers
Solution The values for the counters Incoming External Inter-Cell Handover
Impact Detection Messages Received by BSC and Successful TCH Seizures
in TCH Handovers (Traffic Channel) increase, and the value for the
counter Call Drop Rate on TCH per cell (Including Handover)
decreases.

38. The value for the counter Success Rate of Radio Handover exceeds 100%.
Number DTS2011041402150
Description The value for the counter Success Rate of Radio Handover exceeds
100% when the following conditions are met:
The target channel for an inter-cell handover is preempted upon
request.
The handover command has not been delivered.
Severity Minor
Root Cause The BSC does not measure the number of handover commands, but
incorrectly measures the number of successful handovers.
Solution The BSC measures neither the number of handover commands nor the
number of successful handovers in the preceding scenario.
Solution None
Impact
39. The counter Successful Incoming Inter-RAT Inter-Cell Handovers is incorrectly

measured.


Number DTS2011070101833
Description Inter-RAT In BSC Handover Enable is set to NO(No), but the value
for the counter Successful Incoming Inter-RAT Inter-Cell Handovers is
not 0.
Severity Minor
Root Cause The information element (IE) Discriminator, which indicates the
source cell identifier, in the Handover Request message for an inter-
RAT incoming BSC handover is CGI. When this happens, the setting
of Inter-RAT In BSC Handover Enable does not take effect. As a
result, the BSC still allows inter-RAT incoming BSC handovers.
Solution Set Inter-RAT In BSC Handover Enable to YES(Yes). In addition,
run the SET OTHSOFTPARA command with UMTS Source Cell
Identification Optimization set to ON(On). The following is an
example:
SET OTHSOFTPARA: SERV3GCELLIDOPT=ON;
Solution 1. When UMTS Source Cell Identification Optimization is set to
Impact ON(On):
 If the value of Discriminator for a cell is LAIRNCI, RNCI,
LACRNCI, SAI, or LAIRNCIDCI, the cell is considered a UMTS
source cell.
 If the value of Discriminator for a cell is CGI, LACCI, CI, LAI,
LAC, or ALL_CELL, and if the cell is configured as an external
neighboring UMTS cell, the cell is considered a UMTS source cell.
2. When UMTS Source Cell Identification Optimization is set to
OFF(Off), a cell is considered a UMTS source cell only if the
value of Discriminator is SAI.
40. The counters related to underlaid-to-overlaid handovers are incorrectly measured.


Number DTS2011061702165
Description If Allocate OL Channel Based on RX Level is set to ON(On) and
the signal level in the overlaid subcell is low, the BSC hands over an
MS from one channel to another channel in the underlaid subcell.
When this happens, the BSC measures the following counters:
Internal Intra-Cell Handover Commands (Underlaid to Overlaid)
Successful Internal Intra-Cell Handovers (Underlaid to Overlaid)
Severity Major
Root Cause The BSC incorrectly allocates a new channel in the underlaid subcell
to the MS.
Solution The Low Level Optimization for UL-to-OL Handover parameter
has been added to determine whether to allocate a channel to the MS.
Solution If Low Level Optimization for UL-to-OL Handover is set to
Impact ON(On), the BSC does not allocate a channel to the MS.
If Low Level Optimization for UL-to-OL Handover is set to
OFF(Off), the BSC allocates a new channel in the underlaid subcell to
the MS.
41. The counter Number of Received PTRAU Packets is incorrectly measured.

Number DTS2011110904012
Description The value for the counter Number of Received PTRAU Packets
contains only the number of uplink single-frame data blocks.
Severity Minor
Root Cause The numbers of uplink information frames and uplink multiframes are
not measured for the counter Number of Received PTRAU Packets.
Solution The counter now measures the numbers of uplink information frames
and uplink multiframes in addition to the number of uplink single-
frame data blocks.
Solution The value for this counter will increase after the BSC is upgraded to
Impact V900R014.
42. Three counters in the measurement object IPPATH.RTP are incorrectly measured.


Number DTS2011100901650
Description In A over IP mode, the values of the following counters in the
measurement object IPPATH.RTP may be greater than 100:
 Rate of lost Packet at Local End of IP Path
 Rate of Duration that Delay Jitter Exceeds Threshold of IP Path
 Rate of Duration that RTT Exceeds Threshold of IP Path
Actually, the values of these counters should always be smaller than
or equal to 100.
Severity Major
Root Cause The methods of measuring the three counters are incorrect.
Use Rate of lost Packet at Local End of IP Path as an example. This
counter is calculated as follows:
Rate of lost Packet at Local End of IP Path = Number of lost packets
in a period x 100/Number of packets expected to be received in the
period
Due to a software defect, the period used for measuring the number
of lost packets is different from that for measuring the number of
expected packets. As a result, the number of lost packets may be
greater than the number of expected packets. In this case, the value
for Rate of lost Packet at Local End of IP Path is greater than 100.
The possible causes are as follows:
Solution The methods of measuring the three counters have been corrected so
that the items in the formula are measured in the same period.
Solution Impact The values for these counters may increase or decrease after the BSC
is upgraded to V900R014.
43. Call drops occur and too early handovers occur frequently because of pessimistic
interpolation.


Number DTS2011090502764
Description When handover algorithm II is used:
If downlink measurement reports (MRs) or neighboring cell
measurement information is lost, the BSC performs pessimistic
interpolation on neighboring cells. As a result, handovers are delayed
and call drops occur.
If MRs are not received, the BSC performs pessimistic interpolation
on serving cells. As a result, too early handovers occur frequently.
Severity Minor
Root Cause With pessimistic interpolation:

If downlink MRs or neighboring cell measurement information is lost,
the BSC uses –110 dBm as the neighboring cell signal level. The
signal level used does not meet the requirements for the signal level of
the target cell requirements. As a result, MSs are not handed over to
the neighboring cells in time and call drops occur.
If MRs are not received, the BSC performs pessimistic interpolation
on serving cells, leading to lower signal level and poorer signal
quality. As a result, too early handovers occur frequently.
Solution The BSC now performs linear interpolation, not pessimistic
interpolation. The MrIntrplOptSwitch parameter specifies whether to
use linear interpolation in the preceding scenarios. If
MrIntrplOptSwitch is set to YES(Yes), the BSC performs linear
interpolation. If MrIntrplOptSwitch is set to NO(No), the BSC still
performs pessimistic interpolation. The default value of
MrIntrplOptSwitch is NO(No).
NOTE
In handover algorithm I, bit 0 of the cell-level reserved parameter 16
specifies whether to use linear interpolation. Now,
MrIntrplOptSwitch specifies whether to use linear interpolation in
both handover algorithms I and II.
Solution After MrIntrplOptSwitch is set to YES(Yes):
Impact  The number of handover requests and the number of handover
failures may increase if downlink MRs or neighboring cell
measurement information is lost.
 The number of handover requests may decrease if MRs are not
received.
44. The phase of a PCM code stream changes after A-law compression and decompression.


Number DTS2011111700519
Description In A over TDM mode, the phase of a pulse code modulation (PCM)
code stream changes by 180 degrees after A-law compression and
decompression.
Severity Major
Root Cause The A-law table used during A-law compression and decompression
is incorrect. The possible causes are as follows:
Solution The A-law table is corrected.
If user data is transmitted over a TCH, do not enable the voice quality
enhancement functions (such as automatic noise reduction and anti-clip) or
the tandem free operation (TFO) function.
45. Call access fails because of incorrect processing of channel allocation policy.
Number DTS2011072503077
Description When the half-rate traffic channel-preferred (TCHH-preferred)
policy is used but the license controlling the TCHH usage is
unavailable, calls still successfully occupy TCHHs instead of full-
rate traffic channels (TCHFs) with TRX amplifiers enabled. This
leads to call access failures.
Severity Minor
Root Cause During intelligent TRX amplifier startup, the BSC misinterprets the
TCHH-preferred policy as the TCHH-only policy and therefore does
not allocate TCHFs to MSs.
Solution The mechanism for processing channel allocation policies during
intelligent TRX amplifier startup has been corrected.
Solution Impact The call access success rate increases in the following scenarios:
 The TCHH-preferred policy is used but the license controlling the
TCHH usage is unavailable.
 The TCHF-preferred policy is used but TCHFs with TRX
amplifiers enabled are unavailable.
46. The cause value for handover failure is incorrect.


Number DTS2011072903749
Description The BSC records an incorrect cause value for a handover failure due to
an incorrect IP address in A over IP mode.
Severity Minor
Root Cause The IP address contained in the handover request message from the
MSC is incorrect, and therefore the handover fails. The BSC
incorrectly considers such a failure as "equipment failure".
Solution The BSC records the cause value for such a failure as "MSC message
error".
Solution The handover failures as "MSC message error" will increase and the
Impact handover failures as equipment failure will decrease.
47. The TFO codec type optimization function is occasionally ineffective in A over TDM
and BM/TC separated modes.
Number DTS2011081205908
Description In A over TDM and BM/TC separated modes, the TFO codec type
optimization cannot reach the expected effect occasionally, leading to
a tandem free operation (TFO) connection setup failure.
Severity Minor
Root Cause When Support TFO Codec Optimize is set to YES(Yes) and only
one Transcoder (TC) involved in a TFO connection setup requires
TFO codec type optimization, the TC sends a message to initiate TFO
negotiation. If the message is discarded due to exceptions, TFO codec
type optimization fails.
Solution Both TCs instead of one TC involved in a TFO connection initiate
TFO negotiation.
Solution None
Impact
48. The DPUf fails to report counters under the measurement unit Measurement related to
RTP flux in IPPATH(IPPATH.RTP) in A over IP Mode.


Number DTS2011092304664
Description In A over IP mode, the DPUf fails to report counters under the
measurement unit Measurement related to RTP flux in
IPPATH(IPPATH.RTP).
Severity Minor
Root Cause When reporting counters under the measurement unit Measurement
related to RTP flux in IPPATH(IPPATH.RTP), the DSP software
module on the DPUf uses an incorrect ID for an IP path. As a result,
the DPUf fails to identify the IP path.
Solution The DSP software module on the DPUf now uses a correct ID for an
IP path.
49. The ALM-20243 Board Hardware Fault is generated on the DPUc or DPUa when AMR-
WB voice services are processed.
Number DTS2011121306363
Description When adaptive multirate wideband (AMR-WB) voice services are
processed, the ALM-20243 Board Hardware Fault is generated on
the DPUc or DPUa.
Severity Major
Root Cause Bugs on the digital signal processor (DSP) chip occasionally cause
instruction errors. As a result, the DSP resets or becomes abnormal.
Solution The solution provided by the DSP chip vendor has been used to
solve this problem.
50. BSC-level reserved parameters experience poor operability.


Number DTS2012010900853
Description The following BSC-level reserved parameters experience poor
operability:
 Reserved Parameter 8
All these parameters are set in the MML command SET
OTHSOFTPARA.
Severity Minor
Root Cause Bits of the preceding parameters control whether to enable specific
functions.
Solution Bits of the preceding parameters have been converted to external
parameters as follows:
 Bit 8 of Reserved Parameter 8 has been converted to the PDCH-to-
TCH Adjustment parameter.
 Bit 11 of Reserved Parameter 8 has been converted to the Difference
Compensated for Time Stamp parameter.
 Bit 12 of Reserved Parameter 8 has been converted to the Handover
II Reorder After K Sorting parameter.
 Bit 1 of Reserved Parameter 20 has been converted to the Out-BSC
HO Request Stat. Adjust Policy parameter.
 Bit 5 of Reserved Parameter 20 has been converted to the
TRX.RL.ABNORM.BY.TA.GT.63 Stat. Optimize parameter.
 Bit 6 of Reserved Parameter 20 has been converted to the Iur-g Load
and Capacity Calculation parameter.
 Bit 7 of Reserved Parameter 20 has been converted to the Internal
Fault-Related KPI Measurement parameter.
 Bit 8 of Reserved Parameter 20 has been converted to the Cipher
Protocol Consistency parameter.
 Bit 9 of Reserved Parameter 20 has been converted to the Inter-RAT
Cell Reselection Optimization parameter.
 Bit 10 of Reserved Parameter 20 has been converted to the Neighbor
Cell Output Mode in MR parameter.
 Bit 11 of Reserved Parameter 20 has been converted to the
VAMOS Active Power Control parameter.
 Bit 16 of Reserved Parameter 21 has been converted to the TCH
Busy Duration Measurement Optimize parameter.
 Bit 0 of Reserved Parameter 22 has been converted to the Radio Data
Report for Navigation in Advance parameter.
 Bit 1 of Reserved Parameter 22 has been converted to the Notify
Response Conflict Release Cause parameter.
 Bit 2 of Reserved Parameter 22 has been converted to the Call Re-
setup Timeout Call Drop Stat. Optimize parameter.

 Bit 3 of Reserved Parameter 22 has been converted to the Incoming

BSC HO Emergency Call Guarantee parameter.
 Bit 4 of Reserved Parameter 22 has been converted to the MSC
Reallocation Optimization parameter.
 Bit 5 of Reserved Parameter 22 has been converted to the Fast
Reselection During Location Update parameter.
After conversion, external parameters inherit the settings from the bits
of the original reserved parameters. Therefore, the specified functions
continue to work properly after a BSC is upgraded to BSC6900
V900R014.
Solution Impact After a BSC is upgraded to BSC6900 V900R014, the external
parameters take effect, while the preceding reserved parameters are no
longer in effect and their respective bits return to default values.
51. The single-block packet immediate assignment procedure fails occasionally.

Number DTS2011113001293
Description The single-block packet immediate assignment procedure fails with a
probability of less than 0.5%.
Severity Minor
Root Cause The BSC may incorrectly fill the single-block packet immediate
assignment message, leading to a failure to send the message to an MS.
Solution The defect in filling the single-block packet immediate assignment
message has been corrected.
Solution Impact The number of access retries due to assignment failures decreases. As a
result, the values for the following counters decrease by less than 0.5%:
 Number of 8-Bit Packet Channel Requests Received on CCCH
 Number of 11-Bit Packet Channel Requests Received on CCCH
 Number of 8-Bit Single Block Channel Requests Received on RACH
 Number of 11-Bit Single Block Channel Requests Received on
RACH
52. An invalid destination IP Address can be configured when the ADD BTSBFD command
is executed.


Number DTS2011121205162
Description An invalid destination IP address can be configured when the ADD
BTSBFD command is executed.
Severity Major
Root Cause When the ADD BTSBFD command is executed, the mechanism for
checking the validity of a destination IP address is defective.
Solution The mechanism for checking the validity of a destination IP address
has been optimized so that an invalid destination IP address is not
allowed for adding a BFD session. A valid IP address must be an IP
address of A, B, or C type but cannot be a multicast IP address.
Solution Impact During a version upgrade, if data in the source version contains BFD
sessions with an invalid destination IP address, a message is
displayed. The upgrade continues until the IP address is changed to a
valid one.
53. Low-priority MSs occupy idle TCHs reserved for high-priority MSs.
Number DTS2011102702318
Description If there are idle TCHs reserved for high-priority MSs in a serving cell,
low-priority MSs that have failed in performing directed retry in the
serving cell can occupy these reserved TCHs.
Severity Minor
Root Cause After low-priority MSs fail to perform directed retry, the BSC
reallocates TCHs to these MSs, but the MS priorities are not inherited
from the assignment request messages delivered by the MSC. As a
result, the low-priority MSs occupy the idle TCHs reserved for high-
priority MSs.
Solution The MS priorities have been inherited from the assignment request
messages delivered by the MSC.
Solution Impact Low-priority MSs do not occupy idle TCHs reserved for high-priority
MSs. This ensures that services from high-priority MSs are properly
processed, but the value for the counter K3045-Congestion Rate on
TCH (All Channels Busy) increases.
54. The SDCCH is occupied for an excessively long time.


Number DTS2012011302038
Description The SDCCH is occupied for an excessively long time if an MS waits in
a queue again in a serving cell under the following conditions:
 Forced Queue During Assignment is set to YES(Yes).
 The MS fails to perform directed retry.
 There are no idle channels in the serving cell.
Severity Minor
Root Cause Under the preceding conditions, the BSC forces the MS to wait in a
queue again.
Solution The BSC now does not allow the MS to wait in a queue again.
Solution Impact The values for the counters RR370-Congestion Rate on SDCCH per
CELL (due to Busy) and RCA313-Assignment Success Rate decrease.
55. The BSC fails to transmit downlink DTMF signals after being upgraded.
Number DTS2011112102692
Description After BSC6000V900R008C12 or BSC6900 V900R011C00 is
upgraded to BSC6900 V900R012C01, the BSC fails to transmit
downlink dual tone multiple frequency (DTMF) signals.
Severity Minor
Root Cause The DTMF Downlink Message Filter feature has been available since
BSC6900 V900R012C01. During an upgrade from
BSC6000V900R008C12 or BSC6900 V900R011C00 to BSC6900
V900R012C01, some configuration data is found to be abnormal. As a
result, the Downlink DTMF Signaling Processing Allowed parameter
is set to OPEN(Open) after the upgrade. When this occurs, the BSC
voice processing module filters downlink DTMF signals.
Solution The abnormal data has been corrected during the upgrade.
56. The CPU usage on the XPU increases and transmission resources are wasted in Flex
Abis mode.


Number DTS2011121902328
Description If transmission resources are congested in Flex Abis mode, the BSC
triggers load reshuffling (LDR) and repeatedly releases and applies for
secondary links on a PDCH. This leads to an increase in the CPU
usage on the XPU and a waste of transmission resources.
Severity Major
Root Cause The current LDR algorithm is defective. The algorithm is implemented
as follows:
If transmission resources are congested in Flex Abis mode, the BSC
triggers LDR to release secondary links on a PDCH, regardless of
whether these links are carried on idle or Flex Abis timeslots.
 When secondary links on idle timeslots are released, the idle
timeslots can be allocated only to PS services, leading to a waste of
transmission resources.
 When secondary links on Flex Abis timeslots are released,
transmission congestion is relieved. As a result, the BSC applies for
new Flex Abis timeslots and releases them repeatedly.
Solution In BSC6900 V900R014C00, the Number of Application Attempts of
Abis Timeslot counter is incremented by one when the BSC applies for
a timeslot from the transmission module.
The LDR-triggered Secondary Link Release parameter in the SET
BSCPSSOFTPARA command controls whether the BSC releases
secondary links when it triggers LDR.
 If this parameter is set to ON(On), the BSC releases secondary links.
The default value is ON(On).
 If this parameter is set to OFF(Off), the BSC records the
transmission congestion status without releasing any secondary links.
In addition, the BSC applies only for idle timeslots carrying
secondary links under the congested BTSs.
Solution Impact The optimized LDR algorithm has impact on the following counters:
 After the BSC6900 is upgraded from V900R12C01SPC500,
V900R13C00SPC500, or V900R13C01SPC200 to V900R014C00:
Counter Impact
R9101: Number of Application Attempts of Abis Decrease
Timeslot
Abis congestion rate (= 1 – R9102/R9101) Decrease
 If the LDR-triggered Secondary Link Release parameter is set to

OFF(Off) in BSC6900 V900R014C00:
Counter Impact
R9101: Number of Application Attempts of Abis Decrease
Timeslot

R9102: Number of Successful Application Attempts Decrease

of Abis Timeslot
Abis congestion rate (= 1 – R9102/R9101) Increase
K3034: TCHH Traffic Volume Increase
57. Increased Occurrences of TRX Transmit Power Clipping.

Number DTS2011121400088
Description After the multi-carrier power amplifier (MCPA) algorithm is used, the
BTS clips the TRX transmit power when both CS and PS services are
processed with heavy traffic, leading to increased occurrences of TRX
transmit Power clipping.
Severity Minor
Root Cause The PDCH conversion algorithm is defective; therefore, timeslots 4

through 7 are used more frequently. In this case, if PDCHs are
allocated to multiple carriers in a carrier group on the same timeslot,
the TRX transmit power is clipped.
Solution PDCHs have been evenly allocated to different timeslots on each TRX.
Solution Impact After the MCPA algorithm is used, the number of carriers allocated
with PDCHs in a carrier group on the same timeslot decreases. As a
result, the TRX transmit power cannot reach the power clipping
threshold and the occurrences of TRX transmit power clipping
decrease.
The value of the counter "The total BURST count cut 1.0 dB power"
decreases.
58. Delayed MCS Adjustment for Uplink EGPRS TBFs.


Number DTS2012010904920
Description If the Um interface quality is good and Uplink Default MCS Type is
set to a small value, the transmission rate for uplink EGPRS TBFs
increases slowly. If the Um interface quality is poor and Uplink
Default MCS Type is set to a large value, a large number of uplink
EGPRS TBFs are released abnormally.
Severity Minor
Root Cause When Support EGPRS Uplink MCS Dynamic Adjust is set to
2(According to uplink quality measurements reported by BTS) and
Adjusting Curr CS Receving First UL Data Block is set to OFF(OFF),
the BSC starts to adjust the modulation and coding scheme (MCS)
only when receiving the twentieth uplink data block after uplink
EGPRS TBFs are established.
Solution The Adjusting Curr CS Receving First UL Data Block parameter is
now set to ON(ON). As a result, the BSC starts to adjust the MCS
when it receives the first uplink data block if Support EGPRS Uplink
MCS Dynamic Adjust is set to 2(According to uplink quality
measurements reported by BTS).
Solution Impact The MCS adjustment for uplink EGPRS TBFs is controlled by the
Adjusting Curr CS Receving First UL Data Block parameter, whose
default value is OFF(OFF). If this parameter is set to ON(ON),
counters listed in the following table are affected.
Counter Impact
“A9206: Number of Uplink EGPRS TBF Abnormal Releases due to
N3101 Overflow (MS No Response)”: Decrease
“TL9232: Average Throughput of Uplink EGPRS RLC”: Increase
“L9424: Throughput of Uplink EGPRS Users LLC PDU”: Increase
59. Solving the problem that configuring a large number of PS cells across subracks lowers
the assignment success rate for CS services


Number
Description The assignment success rate for CS services (indicated by

BSCRPT.ASS.SUCC) drops when a large number of PS cells are
configured across subracks.
Severity Major
Root Cause When a large number of cells are configured across subracks, these
cells consume a large amount of inter-subrack resources, leaving
insufficient resources for CS services.
Solution Improvements have been made to achieve the following effects:
 When the remaining inter-subrack resources are below
ISCCONGALMTH, the alarm ALM-21600 Insufficient Inter-
Subrack Connection Resources will be reported to remind you to
check the resource status and adjust configuration policies. When
the remaining inter-subrack resources reach
ISCCONGALMCLRTH, the alarm will be cleared.
To set the threshold for remaining inter-subrack resource
insufficiency, run SET BSCBASIC with ISCCONGALMTH set to
the desired value. The following is an example:
SET BSCBASIC: ISCCONGALMTH=5;
To set the threshold for clearing remaining inter-subrack resource
insufficiency, run SET BSCBASIC with ISCCONGALMCLRTH
set to the desired value. The following is an example:
SET BSCBASIC: ISCCONGALMCLRTH=10;
 When CS services fail to obtain inter-subrack resources, they will
preempt those occupied by PS services.
To enable this function, run the following command:
SET BSCBASIC: ENPREEMPTISCADMT=ON;
To disable this function, run the following command:
SET BSCBASIC: ENPREEMPTISCADMT=OFF;
Solution Impact The counter BSCRPT.ASS.SUCC drops.
Test Case ID CASE_Commercial_PR_Regression_ V9R14C00SPC200_443
6.3 Known Issues

60. The communication between the OMU and host boards is interrupted when a non-
physical-layer fault occurs on the links between the OMU and the SCU boards

Description When a non-physical-layer fault occurs on the links between the OMU
and the SCU boards, the LMT alarm console generates ALM-20223
Communication Between GE Switching Board and OMU Faulty, or
the LMT maintenance panel displays that all boards are faulty or
cannot be detected.
Trigger Condition The OMU or SCU boards experience a hardware failure.
Impact The communication between the OMU and the SCU boards is
occasionally interrupted. As a result, the SCU and other service boards
cannot be maintained.
Severity Minor
Workaround None

Number
Progress A solution is being designed, and the fault will be rectified in later
versions.

HUAWEI BSC6900 GSM V900R014C00SPC200 Changes from

V900R014C00SPC200
Feature updates from V900R013C00SPC500 to V900R014C00SPC200, refer to 6.1.1Feature

Updates.
Feature updates from V900R012C01SPC500 to V900R013C00SPC500:
7.1 What's New

New Features
1. Support for VIP channels

Description Some channels in a cell can always be reserved for VIP users, which
ensures the service quality for VIP users.
Improvement VIP channels in a cell are dedicated to VIP users, which ensure a high
access success rate for them. If the cell is congested, VIP users can still
quickly access the cell, but congestion may deteriorate because non-VIP
users cannot use VIP channels.
Implementation The parameters Reserved Channel Use Allow and Reserve Channel
have been added to the commands ADD VIPUSR and SET
GTRXCHAN, respectively.
Reserved Channel Use Allow specifies whether to allow a VIP user to
occupy VIP channels, and Reserve Channel specifies whether a channel
is reserved for VIP users.
Reserve Channel is valid only for traffic channels (TCHs), because VIP
users cannot occupy other types of channels.
A channel for which Reserve Channel is set to YES cannot be occupied
by a non-VIP user or by a VIP user for whom Reserved Channel Use
Allow is set to NO. This channel remains reserved and is not affected by
services on other channels.
After Reserve Channel is changed to YES for this channel and this
channel is occupied by an ordinary call, the serving BSC attempts to
transfer the service to a channel for which Reserve Channel is changed
to NO. If the target channel is occupied by a PS service, the serving BSC
releases the PS service.
When a user is handed over between two BSCs, the user's Reserved
Channel Use Allow value is recorded so that the user can occupy VIP
channels under the target BSC.
Related Configure a user as a VIP user by using the following command:
Operations ADD VIPUSR: VIPUSRINDEX=0, VIPUSRTYPE=MSISDN,
VIPUSRNUMBER="110", VIPCHANRSV=YES;
Configure a VIP channel by using the following command:
SET GTRXCHAN: TRXID=0, CHNO=2, CHANRSV=YES;
2. Support for configuring V3 series RF modules on the BSC

Description Version 3 (V3) series radio frequency (RF) modules can be configured on
the BSC.
Improvement The BSC supports the configuration of V3 series RF modules.
Implementation Parameter values for V3 series RF modules are added to all

corresponding MML commands.
Related The following values are added to the RXU Specification parameter in
Operations the ADD BTSRXUBRD and MOD BTSRXUBRD commands:
 RRU3029
 RRU3929
 RRU3928
 GRFU_V3
 GRFUe
 GRFU_V2a
 MRFUe
 MRFUd
 MRFU_V2a
PR Number SOR-70
Feature ID None
3. Support for bit error detection and signaling link reliability improvement

Description The bit error detection function is provided for signaling messages over
the Ater interface to optimize the data transmitting mechanism for
signaling links.
Improvement The transmission efficiency and reliability of signaling links are
improved.
Implementation The BSC monitors the data transmitting capability of each Ater signaling
link. Based on the monitoring results, the BSC adjusts the number of
signaling messages sent over each signaling link. This ensures that
signaling messages are preferentially sent over a stable signaling link,
improving the transmission efficiency. If an Ater signaling link is faulty,
signaling messages in the buffer of the link are sent over another
signaling link.
Related This function is enabled by default.
Operations  Adjust the number of signaling messages sent over each signaling
link:
1. To enable this function, run the following command:
MOD ATERSL: ATERSLID=0, BTCFLAG=CFGBM,
CONGTHRDADJSW=ON;
MOD ATERCONSL: ATERSLID=0, CONGTHRDADJSW=ON;
2. To disable this function, run the following command:
MOD ATERSL: ATERSLID=0, BTCFLAG=CFGBM,
CONGTHRDADJSW=OFF;
MOD ATERCONSL: ATERSLID=0, CONGTHRDADJSW=OFF;
3. To check whether this function has been enabled, run the following
command:
LST ATERSL: ATERSLID=0;
 Send the signaling messages in the buffer of the faulty link over
another signaling link:
1. To enable this function, run the following command:
SET TNSOFTPARA: AterSlReliabilitySw=ON;
2. To disable this function, run the following command:
SET TNSOFTPARA: AterSlReliabilitySw=OFF;
3. To check whether this function has been enabled, run the following
command:
LST TNSOFTPARA: LstFormat=VERTICAL;
PR Number OR 201003260376
4. Support for Radio Measurement Data Interface for Navigation

Description The Radio Measurement Data Interface for Navigation feature is used for
real-time navigation on high ways. With this feature, a VNP can collect
real-time measurement data for navigation.
Improvement Huawei BSS can provide measurement data to support navigation
services that are deployed by the operator and navigation service
provider.
Implementati IP transmission is used between the BSC and the VNP. The BSC, which
on provides TCP port 6200, reports MS-related application events to the
VNP through TCP/IP connections. The VNP then sends the measurement
data to a third-party server for calculation.
This feature can be enabled by setting the BSC-level Event Report
Switch parameter to ON.
The VNP IP Address parameter is used to set a valid VNP connection.
Negotiation with the VNP side is required to ensure correct configuration
of the Category Version, BSC Protocol Version No., and BSC
Application Version No. parameters.
The cell-level parameter Real-Time Event Report Switch is used to
specify whether a cell supports this feature.
Related 1. Set the VNP IP Address and Category Version parameters as follows:
Operation
ADD GVNPADDR: VNPIP="10.146.56.89",
CATEGORY=CATEGORY2;
2. Set the BSC-level parameters Event Report Switch, BSC Protocol
Version No., BSC Application Version No., and Access Cause as
follows:
SET BSCBASIC: ENTCAUSE=PERIOD_LOCATION_UPDATE-
1&NORMAL_LOCATION_UPDATE-1&IMSI_ATTACH-1&SMS-
1&CALL_SETUP-1&PAGING_RESPONSE-1&IMSI_DETACH-
1&OTHERS-1, ENTSWITCH=ON, BSCPVN=0, BSCAVN=0;
3. Set the cell-level Real-Time Event Report Switch parameter as
follows:
SET GCELLSOFT: IDTYPE=BYID, CELLID=0, ENTSWITCH=ON;
The preceding parameter values are for your reference only.
PR Number SOR-020
5. Support for the VAMOS Call Drop Solution

Description At present, the mainstream MSs in the market support Single Antenna
Interference Cancellation (SAIC); however, call drops are likely to occur
when using the VAMOS feature. The cause for such call drops is a defect
in the Auto Frequency Correction (AFC) function of some types of MSs.
To prevent call drops when using the VAMOS feature, the VAMOS Call
Drop Solution is provided.
Improvement With this solution, call drops no longer occur when the MS with AFC
defects is multiplexed with another MS on an HR channel. This increases
network capacity and guarantees continuity of service.
Implementati The BSC records whether each model of SAIC-capable MS has the
on preceding AFC defect.
Before assigning a channel to an MS, the BSC obtains the International
Mobile Equipment Identity (IMEI) of the MS and then checks whether
this MS has the AFC defect.
When an MS with AFC defects is multiplexed with another MS, the BSC
informs the BTS of the power control policy specific to the MS with AFC
defects.
Related To enable this feature, run the MML command SET GCELLVAMOS on
Operation the BSC with the VAMOS Switch, Problem SAIC Terminal
Processing Switch, and Problem SAIC Terminal Identify Switch
parameters to ON. The following command is an example.
VamosSwitch=ON, SaicProMsSwitch=ON, SaicProMsIdeSwitch=ON;
PR Number MBSCV9R13C00-OR-15
6. Support for the SCUb

Description The GE Switching network and Control Unit REV:b (SCUb) board
provides GE switching for the BSC6900.
The SCUb board provides a switching capacity of 240 Gbit/s, which is
much greater than 60 Gbit/s of the SCUa.
Improvement The SCUb board provides the BSC6900 a high inter-subrack switching
capacity.
Implementatio The SCUb hardware is added and its configuration data can be added by
n using the ADD BRD command.
If the SCUa board is configured for each subrack, the star topology is used
for inter-subrack connections. If the SCUb board is configured for each
subrack, the chain topology is used for inter-subrack connections.
Related To add an SCUb board, run the following command:
Operation ADD SUBRACK: SRN=1, SRName=" EPS1", TYPE=EPS,
WORKMODE=GO, SCUTYPE=SCUb;
Feature ID None

7. Support for the OMUc

Description The Operation and Maintenance Unit REV:c (OMUc) is introduced to
provide functions such as configuration management, performance
management, fault management, security management, and loading
management. It provides LMT and M2000 users the OM interface for the
BSC6900.
Two OMUc boards in active/standby mode can be installed in slots 0 to 3,
slots 20 to 23, or slots 24 to 27 in the MPS. Slots 24 and 25 are
recommended.
Improvement The OMUc board occupies only one slot and is much lighter than the
OMUa and OMUb boards. Compared with the OMUa and OMUb boards,
the OMUc board is designed with much lower power consumption and
larger memory and hard disk capacities.
Implementatio The OMUc hardware is added and its configuration data can be added by
Related To add an OMUc board, run the following command:

Operation ADD BRD: SRN=0, BRDCLASS=OMU, BRDTYPE=OMUc, SN=20;
Feature ID None
8. Support for the DPUf

Description The Data Processing Unit REV:f (DPUf) board is added. The DPUf board
processes GSM voice services and has a much higher service processing
capacity than the DPUa, DPUb, and DPUc boards.
The DPUf board has the following service processing capacities:
1920 TC channels
7680 interworking function flows in all-IP networking mode
3840 interworking function flows in Abis over TDM or Ater over TDM
mode
Improvement When the BSC6900 uses DPUf boards, the service processing capacity of
the TC boards in the BSC is improved.
Implementatio The DPUf hardware is added and its configuration data can be added by
Related To add a DPUf board, run the following command:

Operation ADD BRD: SRN=0, BRDCLASS=DPU, BRDTYPE=DPUf, SN=8,
ISTCBRD=NO, MPUSUBRACK=0, MPUSLOT=0;
Feature ID None

9. Support for the DPUg

Description The Data Processing Unit REV:g (DPUg) board is added. The DPUg board
processes PS services of GSM. Compared with the DPUb and DPUd
boards, the DPUg board has a much higher PS service processing capacity
(maximum number of subscribers that can be processed by the board
simultaneously) though it supports the same amount of activated PDCHs.
The DPUg board supports a maximum of active 1024 PDCHs at an MCS9
rate.
Improvement The DPUg hardware is added and its configuration data can be added by
using the ADD BRD command.
Implementatio The DPUf hardware is added and its configuration data can be added by
Related To add a DPUg board, run the following command:

Operation ADD BRD: SRN=0, BRDCLASS=DPU, BRDTYPE=DPUg, SN=8,
MPUSUBRACK=0, MPUSLOT=0;
Feature ID None
10. Support for IP attack defense

Description IP attack defense involves invalid packet check and ARP flooding attack.
 Invalid packet check takes statistics about received invalid packets. When
detecting that the number of received invalid packets has exceeded a
specified invalid packet alarm threshold, invalid packet check reports
Invalid Packets Exceeding alarms (alarm ID: 21388) and records
information about attack sources. Users can obtain the information about
attack sources by viewing logs or running query commands. The
information assists users in updating system security policies against
attacks.
 ARP flooding attack is implemented based on ARP learning strict, which
enables the BSC6900 interface board to learn only ARP packets
responding to its own ARP request packets.
Improvement  Invalid packet check enables users to check a network for invalid packets
and to obtain information about attack sources.
 ARP flooding attack improves security by preventing attacks from ARP
packets.
Implementati The FG2c, GOUc, FG2d and GOUd support invalid packet check. The
on FG2c, GOUc, FG2d, GOUd, FG2a, and GOUa support ARP flooding attack.
The SET IPGUARD command is used to enable invalid packet check on the
FG2c, GOUc, FG2d and GOUd and to set Invalid Packet Alarm Threshold
and Invalid Packet Alarm Clearance Threshold.
The SET IPGUARD command is used to enable ARP learning strict on the
FG2c, GOUc, FG2d, GOUd, FG2a, and GOUa.
Related Run the SET IPGUARD command to enable invalid packet check, with
Operation Invalid Packet Alarm Threshold and Invalid Packet Alarm Clearance
Threshold set to the default values.
VALIDPKTCHKSW=ON;
Run the DSP INVALIDPKTINFO command to query information of the
invalid packet.
DSP INVALIDPKTINFO: SRN=2, SN=22;
Run the SET IPGUARD command to enable ARP learning strict.
SET IPGUARD: SRN=2, SN=20, BRDTYPE=GOUa,
ARPLRNSTRICTSW=ON;
Feature ID None
11. Support for UDP ping detection on IP paths

Description UDP ping detection is supported on IP paths over the Abis interface.
Improvement In versions earlier than V900R013C00, only ICMP packet detection is

supported on IP paths. In V900R013C00, UDP ping detection is added
to solve ICMP transmission problems on the network. The UDP Ping
packets are encapsulated in the same protocol as services. This
improves the reliability of packet transmission on the network. In
addition, UDP ping packets are not processed by the CPUs of the
interface boards, reducing CPU processing load of the interface boards.
When many links are detected at the same time, the detection reliability
is improved.
Implementation This feature is supported only by Huawei products and requires
compliance with BSC and BTS versions. If UDP ping detection is
enabled for the IP path on the BSC side, the MPU of the BSC
originates UDP ping detection requests, with UDP packets in standard
format and reserved port ID 65042 in use. After the UDP detection
packets are looped back on the BTS side, they are sent to the MPU for
loopback detection.
Related To enable this feature, enable UDP ping detection on the BTS side, and
Operation perform the following operations on the BSC6900 side:
Run the following command to enable UDP ping detection for the IP
path whose adjacent node ID is 100 and IP path ID is 0:
MOD IPPATH: ANI=101, PATHID=1, ITFT=ABIS,
PATHCHK=ENABLED, ECHOIP="11.11.11.11", CHECKT=UDP;
Run the following command to disable UDP ping detection for the IP
path whose adjacent node ID is 100 and IP path ID is 0:
MOD IPPATH: ANI=101, PATHID=1, ITFT=ABIS,
PATHCHK=DISABLED;
12. Support for VAMOS

Description Voice Services over Adaptive Multi-user Orthogonal Subchannels

(VAMOS) is a technology that multiplexes two voice users onto one
voice channel to expand the GSM network capacity.
VAMOS further expands network capacity by use of half-rate channels.
Test results show that VAMOS performance depends on the penetration
rate of VAMOS-capable MSs and the frequency reuse pattern.
Improvement VAMOS expands network capacity by multiplexing two voice users onto
one voice channel. When VAMOS-capable MSs are used extensively
with a low frequency reuse rate, a combination of VAMOS and AMR
half-rate channels expands network capacity by 48%.
Implementati VAMOS affects the voice quality of multiplexed voice users and causes
on interference to the network. Therefore, in the load control algorithm,
VAMOS is enabled to expand network capacity only when the system
experiences channel resource congestion. When network load becomes
light, VAMOS is disabled to improve the voice quality of multiplexed
voice users.
Related To enable VAMOS, run the following commands:
Operation Run the SET GCELLVAMOS command with VAMOS Switch set to On
and Allow Channel Multiplex in Assignment set to On, or Allow Channel
Multiplex via In-Cell HO set to On.
Run the SET GCELLPWR3 command with III Power Control
Optimized Enable set to Yes.
Run the SET GCELLHOAD command with Waiting for MR on
SDCCH Switch set to On.
Run the SET GTRXDEV command with TCH Rate Adjust Allow set to
Yes.
Set other parameters based on the actual network plan.
13. Support for mute SAIC-capable MS identification

Description A network can distinguish Single Antenna Interference Cancellation

(SAIC)-incapable MSs from SAIC-capable MSs that do not report their
SAIC capabilities to the BSS. In this way, the SAIC-capable MSs can be
paired with VAMOS.
Improvement This feature correctly identifies MS capabilities to ensure that SAIC-
capable MSs are paired with VAMOS. This increases the existing number
of MSs paired with VAMOS and expands network capacity.
Implementati A network distinguishes mute SAIC-capable MSs from SAIC-incapable
on MSs.
Related To enable this feature, run the SET GCELLVAMOS command with
Operation VAMOS Switch set to On and Mute SAIC Terminal Processing Switch
set to On and Auto Mute SAIC Identification Switch set to On.
14. Support for call-based flow control

Description This feature allows mobile originated calls (MOCs) and mobile
terminated calls (MTCs) to adopt different flow control policies during
the traffic bursts caused by an emergency or disaster.
Improvement In the process of flow control, the priorities of MOCs and MTCs can be
configured.
Implementati The MOC Access CPU Rate and MTC Access CPU Rate values
on determine the priorities of calling and called users.
If the MOC Access CPU Rate value is greater than the MTC Access CPU
Rate value, calling users take precedence over called users. Therefore,
flow control is preferentially enabled for called users.
Related Run the SET BSCFCPARA command to set MOC Access CPU Rate
Operation and MTC Access CPU Rate. If the MOC Access CPU Rate value is
greater than the MTC Access CPU Rate value, calling users take
precedence over called users.
15. Support for flow control based on user priority

Description During traffic bursts, the BSC adopts different flow control policies for
users based on enhanced Multi-Level Precedence and Preemption
(eMLPP) user priorities during flow control. This ensures high-priority
users enjoy services preferentially.
Improvement During traffic bursts, high-priority users enjoy services preferentially.
Implementati When traffic volume increases significantly, the BSC determines whether
on a user is a VIP user based on eMLPP user priorities. If the user is a VIP
user, the user is paged preferentially. If the user is a common user, the
common flow control algorithm is applied.
To prevent high-priority users from being affected by flow control (for
example, prevent their signaling messages from being discarded), the
BSC distinguishes signaling priorities based on eMLPP user priorities.
Therefore, high-priority users may not be affected by flow control, but
the signaling messages of low-priority users may be discarded due to
flow control.
User priorities are applied to flow control at call assignment, handover,
and paging phases.
Related To enable this feature, run the SET BSCFCPARA command with
Operation Support Priority Based Flow Control set to Yes.
16. Support for CSFB

Description In the process of Circuit Switch Fallback (CSFB), users under E-UTRAN
coverage fall back to GERAN or UTRAN for voice services and other
CS services by means of PS handovers or cell reselections. This feature
can be applied only when E-UTRAN has the same coverage as GERAN
or UTRAN.
Improvement Users under E-UTRAN coverage provide CS services using the existing
GERAN, which help operators maximize return on investment (ROI) of
the live network.
Operators can provide CS services using GERAN and high-speed PS
services using E-UTRAN.
Compared with Single Radio Voice Call Continuity (SRVCC), CSFB
provides voice services for users under E-UTRAN coverage. The
network structure is simplified because the IP Multimedia Subsystem
(IMS) is not required.
Implementati Add the CSFB function switch (CSFB Support) to enable or disable
on CSFB.
After CSFB is enabled, called CSFB users are allowed to access.
Related To enable CSFB, run the following command:
Operation SET GCELLSOFT: IDTYPE=BYID, CELLID=1,
SUPPORTCSFB=SUPPORT;
To view the settings of the CSFB function switch, run the following
command:
LST GCELLSOFT:;
17. Support for GPRS/EGPRS Time Slot Multiplexing Priority

Description EGPRS Priority weight is configured to control uplink and downlink
scheduling policies for General Packet Radio Service (GPRS) and
Enhanced General Packet Radio Service (EGPRS) users, respectively.
Improvemen EGPRS users' experience is improved, and system throughput is increased.
t
Implementat EGPRS users' priority weights are set to larger values to differentiate
ion between GPRS and EGPRS users' scheduling priorities.
Related Run the SET GCELLPSOTHERPARA command with EgprsPriWeight

Operation set to a larger value.
18. Support for Layered Paging

Description Common control channels (CCCHs) are overloaded when the number of
packet switched (PS) paging messages exceeds the number of circuit
switched (CS) paging messages and increases sharply and continuously.
This affects access of CS services.
Layered paging enables the first paging message to be sent only to the last
cell on which the mobile station (MS) camps and to its neighboring cells.
Improvemen Load of PS paging on the CCCHs is reduced.
t
Implementat The first paging message is sent only to the last cell on which active PS
ion users camp and to its neighboring cells.
If the first paging fails and the cell paging policy is set to First precise
paging, the base station controller (BSC) sends paging messages to paging
areas specified by the core network (CN). If the cell paging policy is set to
Always precise paging, the BSC continues to send paging messages only
to the last cell on which the active PS users camp and to its neighboring
cells.
Related 1. Run the SET GCELLGPRS command with PS Paging Control set to
Operation First precise paging or Always precise paging.
2. Run the SET BSCPSSOFTPARA command with Ready Timer set as
required to check for the first paging, the parameter value should be same
with SGSN side configuration.
PR Number CR GU00325
19. Support for EVAD

Description The earlier voice activity detection (VAD) algorithms may consider soft
music as silence and mistakenly encode it in the downlink. This affects
user experience.
Based on Huawei patented algorithm, the enhanced voice activity detector
(EVAD) enhances music recognition accuracy, significantly reducing the
probability that music is mistakenly considered as silence.
Improvemen User experience is improved, and value-added music services are easy to
t promote.
Implementat The adaptive multirate (AMR) encoder integrated with an EVAD encodes
ion music frames received in A over TDM mode to distinguish them from
noise frames. This process hardly affects the downlink VAD efficiency.
Related Run the SET TCPARA command with EVAD Switch set to ON.
Operation
20. Support for BSC local switch

Description In GSM Only (GO) mode, when the BSC works in BM/TC separate mode
and IP transmission is applied over the Abis interface, BSC local switch is
supported.
Improvemen This feature saves remote or local transmission resources on the Ater
t interface.
Implementat If calling MSs and called MSs are controlled by the same BSC, the BSC
ion loops back speech signals within the BSC without sending the signals to the
core network over the Ater and A interfaces. This saves Ater-interface
transmission resources and TC coding resources.
Related To enable this feature, perform the following operations on the BSC6900
Operation side:
Enable BTS local switch by running the following command:
SET BTSLSW: IDTYPE=BYID, BTSID=0,
ISSUPPORTBTSLSWITCH=YES;
Set BSS local switch policies by running the following command:
SET BSSLS: BssLsGenMode=BSCPRIORITY,
BtsLsStartMode=UNCONDITIONALSTART,
BscLsStartMode=UNCONDITIONALSTART;
21. Support for remote modification of BTS3900B preconfiguration data in batches

Description BTS3900B preconfiguration data such as the shared key of the IPsec tunnel
between the BTS3900B and the security gateway can be remotely modified
in batches on the BSC.
Improvemen In versions earlier than V900R013C00, BTS3900B preconfiguration data is
t first stored in a USB storage device and then imported into the BTS3900B
through the USB storage device for data modification. This leads to a heavy
workload. In addition, most BTS3900Bs are deployed at homes. This makes
site maintenance inconvenient. Therefore, remote modification of BTS3900B
preconfiguration data in batches is required, which is implemented in
V900R013C00.
Implementat Users update preconfiguration data on the BSC, and then BTS3900Bs save
ion the updated data to their memories. Then, the BSC activates the BTS3900Bs
in batches on the BSC.
Related To import BTS networking configuration data, run the IMP BTSNETPARA
Operation command.
To export BTS networking configuration data, run the EXP BTSNETPARA
command.
To import basic BTS IKE configuration data, run the IMP BTSIKECFG
command.
To export basic BTS IKE configuration data, run the EXP BTSIKECFG
command.
To import BTS IKEPEER configuration data, run the IMP BTSIKEPEER
command.
To export BTS IKEPEER configuration data, run the EXP BTSIKEPEER
command.
To activate imported BTS configuration data, run the ACT BTSIMPDATA
command.
For example,
Import BTS networking configuration data by running the following
command:
IMP BTSNETPARA: IDTYPE=BYID, BTSID=900,
IPSECSWITCH=ENABLE, BTSIP="10.10.12.13",
MASK="255.255.255.0", BTSGATEWAYIP="10.10.12.14",
BTSDNSIP="10.10.12.15", ADDRTYPE=BYIP, PSEGWIP="10.10.12.16",
M2000IP="10.10.12.17";
Import basic BTS IKE configuration data by running the following
command:
IMP BTSIKECFG: IDTYPE=BYID, BTSID=900,
LOCALNAME="admin", KEEPALIVEINTERVAL=20,
KEEPALIVETIMEOUT=28800;
Import BTS IKEPEER configuration data by running the following
command:
IMP BTSIKEPEER: IMP BTSIKEPEER: IDTYPE=BYID, BTSID=900,
GWTYPE=PSEGW, PEERNAME="admin", IKEVERSION=IKE_V2,
LOCALIDTYPE=IP, REMOTEIP="10.10.12.13", DPDSW=PERIODIC,
DPDIDLETIME=15, DPDRETRYITV=16, DPDRETRYCNT=10;
Activate imported BTS configuration data by running the following
command:

ACT BTSIMPDATA: IDTYPE=BYID, BTSID=900;

Feature ID None
22. Support for query of BTS board information in batches

Description BTS board status information can be queried in batches in V900C013C00.
Improvemen This function helps collect statistics about BTS boards in the live network
t quickly, simplifying inventory management of BTS boards.
Implementat The information about boards configured and boards that are installed but not
ion configured in a BTS can be queried on the BSC at a time.
Related To set Information Type to In-Position Board Information, run the following
Operation command:
DSP BTSBRD: INFOTYPE=INPOSBRD, IDTYPE=BYID, BTSID=900;
Feature ID None
23. The BSC supports IP header compression in IP over E1 transmission mode.

Description In IP over E1/T1 transmission mode, a typical small IP packet, such as speech
packet, over the Abis interface takes only 50% to 60% payload. In this case,
the transmission efficiency is low. By using the IP header compression
(IPHC) function, IP/UDP packet headers are compressed to increase the data
payload, saving IP transmission resources.
Improvemen By using IPHC over the Abis interface, the IP header of the data packet is
t compressed over the Abis interface, saving transmission resources. For
example, the typical full-rate speech data packet is shortened from 72 bytes to
48 bytes, saving more than 30% transmission resources.
Implementat Add the IP Header Compression parameter to the ADD BTSPPPLNK and
ion ADD MPGRP commands and set this parameter to ENABLE. In this way, the
BTS supports IP/UDP header compression and the BSC can parse the
compressed packet.
Related Run the ADD BTSPPPLNK/MOD BTSPPPLNK or ADD
Operation BTSMPGRP/MOD BTSMPGRP command to set IP Header Compression
to ENABLE or DISABLE.
Run the LST BTSPPPLNK or LST BTSMPGRP command to query
whether the IPHC function is enabled.
Run the DSP BTSPPPLNK or DSP BTSMPGRP command to query
whether the IPHC function takes Improvement on the BTS side.

24. Support for creation, deletion, and query of a task for tracing a single GSM user by using
MML commands
Description A task for tracing a single GSM user can be created by using an MML
command.
Improvement The tracing of a single GSM user can be created and deleted by using
MML commands.
This helps operators to conduct signaling tracing of a VIP user and analyze
traced signaling, which improves the user experience of VIP users.
Implementatio A task for tracing a single GSM user can be created, deleted, and queried
n by using the related MML commands.
Related Run the CRE USERTRCTASK command to create a task for tracing a
Operation single GSM user:
CRE USERTRCTASK: ITFTYPE=AITF&ABISITF&UMITF,
TRCCONDITION=CHANNEL, BTSNAME="bts3012", TRXNO=0,
CHNNO=0, SUBCHNNO=0, STRDT=2008&02&15,
STRTM=16&34&05, ENDDT=2008&02&15, ENDTM=17&34&05;
Run the DEL TRCTASK command to delete a task for tracing a single
GSM user:
DEL TRCTASK: TASKNO=32;
Run the LST TRCTASK command to query tasks for querying single
GSM users:
LST TRCTASK: TRCTYPE=USERTRACE;
25. Support for the BSC obtaining clock signals from the Abis interface in TDM mode

Description The BSC can obtain clock signals from the Abis interface in TDM mode.
Improvement When the A interface is in IP over E1 mode, the BSC can obtain clock
signals from the A interface. When the A interface is in IP over Ethernet
mode, and the Abis interface is in TDM mode, the BSC can obtain clock
signals from the Abis interface to ensure the frequency synchronization
between the BSC and BTS.
Implementati The GCUa or GCGa obtains the line clock signals from the Abis interface
on and then distributes the signals to other boards in the BSC through the
backplane. This achieves the clock synchronization between the BSC and
BTS.
Related To enable this function, perform the following operations on the BSC6900
Operation LMT:
Run the following command to specify the clock source of the BSC:
ADD CLKSRC: SRCGRD=2, SRCT=LINE1_8KHZ;
Run the following command to specify the clock source for the Abis-
interface board:
SET CLK: SRT=MPS, SN=14, BT=EIUa, REF2MCLKSRC=0,
BACK8KCLKSW1=ON;
PR Number None
Feature ID SOR-82
26. Support for IP port backup of the BTS and access of monitoring devices through IP ports

Description IP port backup of the BTS and access of monitoring devices through IP ports
are supported as follows:
A BTS working in IP over FE mode has an Ethernet optical port and an
electrical port. The ports can work simultaneously or in active/standby mode
for BTSs working under BSC6900 V900R013C00. If one port is faulty,
services are quickly switched to the other port. This improves transmission
reliability.
Third-party monitoring devices can be connected over IP ports to a BTS
working under BSC6900 V900R013C00.
Improvement The function of IP port backup of the BTS improves transmission reliability.
The function of the access of monitoring devices through IP ports enables
operators to connect monitoring devices in the IP network to monitor the
surrounding environment of the BTS.
Implementatio When a BTS works in IP over E1 mode, a monitoring device is connected to
n the BTS over an FE port, and the monitoring data flows are forwarded
through the Point-to-Point Protocol (PPP)/Multilink Protocol (MP) link
under IP over E1. If the link is disrupted, the BTS reports the alarm ALM-
25880 Ethernet Link Fault. When the BTS works in IP over FE mode, the
other FE port is used for access of monitoring devices to the IP network.
To enable IP port backup, a BTS must communicate with other network
elements (NEs) by using its device IP address and be configured with high-
and low-priority routes to the same destination network segment. In
addition, the BTS ARP detection function must be enabled on BSC
V900R013C00. If the device IP address or high- and low-priority routes to
the same destination network segment are not configured, the BTS ARP
detection function is only applicable to the detection of the monitoring link,
but not to the triggering of route switching.
Related To enable the function of the access of monitoring devices to the IP network,
Operation do as follows:
To set the Ethernet attributes and IP address of the FE port that provides
access of monitoring devices, run the following commands:
ADD BTSDEVIP: IDTYPE=BYID, BTSID=0, PN=1,CN=0,SRN=0,SN=6,
IP="10.33.2.56", MASK="255.255.255.0";
SET BTSETHPORT: IDTYPE=BYID, BTSID=0, PN=1, MTU=1500;
To query the traffic statistics of the FE port in a BTS working in IP over E1
mode, run the following command:
DSP BTSIPPM: TYPE= FLOWSTAT, IDTYPE=BYID, BTSID=0,
BTSPORTNO=1;
To query the bit error rate of the FE port in a BTS working in IP over E1
DSP BTSIPPM: TYPE=BER, IDTYPE=BYID, BTSID=0,
BTSPORTNO=1;
To enable the function of the IP port backup, set the two Ethernet ports of
the BTS, and then run the following command to enable the BTS ARP
detection function:
ADD BTSARPSESSION: IDTYPE=BYID, BTSID=0, ARPIDX=0,
DSTIP="10.161.55.9", ARPTIMEOUT=5, ARPRETRY=6,
WHETHERAFFECTSWAP=YES;

Feature ID None
27. Support for BTS transmission maintainability and testability in IP network mode
Description The state of Ethernet ports, Address Resolution Protocol (ARP) attributes,
and E1/T1 attributes of a BTS can be queried.
Improvement Transmission faults can be located and the network quality can be detected
in IP network mode.
Implementatio The state of Ethernet ports, ARP attributes, and E1/T1 attributes of a BTS
n can be queried by running the DSP BTSETHPORT, DSP BTSARP, and DSP
BTSE1T1 commands respectively.
Related To query the E1/T1 attributes of a single port of a BTS, run the following
Operation command:
DSP BTSE1T1: IDTYPE=BYID, BTSID=0, CN=0, SRN=0, SN=6,
PS=SINGLEPORT, PN=0, LSTFORMAT=VERTICAL;
To query the state of an Ethernet port of a BTS, run the following command:
DSP BTSETHPORT: IDTYPE=BYID, BTSID=0, CN=0, SRN=0, SN=6,
PN=0, LSTFORMAT=VERTICAL;
To query the ARP attributes of a BTS, run the following command:
DSP BTSARP: IDTYPE=BYID, BTSID=0, CN=0, SRN=0,
SN=6,LSTFORMAT=VERTICAL;
Feature ID None
28. Support for RF maintenance and test over the air interface

Description This function helps improve the capability of locating RF-related problems
over the air interface. It is applicable to the following scenarios:
1. RF counter test under site deployment
2. RF intermodulation detection in routine operation and maintenance (OM)
3. Obtaining frequency spectrum remotely (with capacity loss)
4. Obtaining frequency spectrum locally (with capacity loss)
5. Obtaining frequency spectrum remotely (without capacity loss)
6. Interference identification and cancellation
Improvement A spectrum analyzer is a bottleneck of improving the capability of identifying
and canceling RF interferences. This function moves part of the common
functions of the spectrum analyzer to the BSC, thereby reducing OPEX and
improving OM efficiency.
Implementati Offline RF counter test, online antenna passive intermodulation test, and
on CDMA interference test are performed on the M2000. The LMT functions as
a remote spectrum analyzer, on which interferences are identified and results
are analyzed on a BSC-level basis. The Site Maintenance Terminal (SMT)
functions as a local spectrum analyzer.
The following table lists the mapping between this function and its
application scenarios.
RF RF Obtaini Obtaini Obtaini Interf
count inter ng ng ng erenc
er test modu frequen frequen frequen e
under lation cy cy cy identi
site detect spectru spectru spectru ficati
deplo ion in m m m on
ymen routin remotel locally remotel and
t e y (with (with y cance
opera capacity capacit (withou llatio
tion loss) y loss) t n
and capacit
maint y loss)
enanc
e
Remote offline Y Y - - - -
RF counter test
Local offline Y - - - - -
RF counter test
Online antenna - Y - - - Y
passive
intermodulation
test
Remote - - - -
spectrum
scanning Y
Local spectrum - - - Y - -
scanning

Online - - - - Y -
spectrum
scanning
CDMA - - - - - Y
interference test
Related To conduct an offline RF counter test, an online antenna passive

Operation intermodulation test, and a CDMA interference test, perform either of the
following operations
1. On the BSC6900 LMT, run the STR BTSRFTST command. The RF
interference test results are displayed.
2. On the M2000 client, choose Maintenance > RF Performance Test >
Interference Measurement. The interference detection report is displayed.
To perform remote and local spectrum scanning, do as follows:
On the BSC6900 LMT, click the Monitor tab. On the Monitor Navigation
Tree tab page in the left pane of the window, click GSM Monitoring to
expand the folder. Double-click Spectrum Scan Monitoring. The Spectrum
Scan Monitoring window is displayed. The spectrum scanning results are
displayed.
Feature ID None
29. Support for BTS power saving Improvement display

Description A BTS measures energy consumption, such as power, and reports the results
to the BSC. The BSC then reports the results to the M2000. Users can query
the results on the M2000 client.
Improvement The energy consumption of a BTS and its auxiliary devices is measured on the
BTS side. In addition, users can query the measurement results on the M2000
client.
Implementati The Site Energy Consumption Measurement counter is added.
on The Enable Energy Consumption Measurement parameter is added to the BSC
for measuring energy consumption of the BTS.
Related To enable this function, run the following command with Whether to Enable
Operation Energy Consumption Measurement set to YES and Energy Consumption
Measurement Point to AC:
SET BTSOTHPARA: IDTYPE=BYID, BTSID=0, SPRECM=YES,
ECMP=AC;
Feature ID None
30. Support for 12-level static power control for the BTS3900B.

Description BSC6900 V900R013C00 enables users to configure up to 12 static power

control levels for the BTS3900B.
Improvement Up to 12 static power control levels are available for the BTS3900B.
Implementati A maximum of 12 static power levels are configured for the BTS3900B.
on
Related Run the SET GRXDEV command to configure static power levels for the
Operation BTS3900B.
For example, to configure the static power control level to 11, run the SET
GTRXDEV command with Power Level set to 11.
SET GTRXDEV: TRXID=123, POWL=11;
Feature ID None
31. Support for TRX backup for the BTS3900B.

Description BSC6900 V900R013C00 supports transceiver (TRX) backup for the
BTS3900B.
Improvement Users do not need to replace hardware onsite.
Implementati TRX backup is supported for the BTS3900B, and backup TRXs are swapped
on manually.
Related Run the SET BTSTRXBACKUP command to configure TRX backup for the
Operation BTS3900B.
Run the SWP GTRX command to manually swap backup TRXs.
For example, to enable TRX backup for the BTS3900B, run the SET
BTSTRXBACKUP command with TRX Backup Switch set to ON.
SET BTSTRXBACKUP: IDTYPE=BYID, BTSID=123, TRXBPSW=ON;
To manually swap backup TRXs, run the SWP GTRX command.
SWP GTRX: IDTYPE=BYID, BTSID=123;
Feature ID None
32. Support for enhanced SMT security for the BTS3900B.

Description BSC6900 V900R013C00 enables users to change site maintenance terminal

(SMT) user names and passwords.
Improvement Security is enhanced.
Implementati SMT user names and passwords are changed.

on
Related Run the SET BTSUSERPWD command to change SMT user names and
Operation passwords.
For example, to change SMT user names and passwords based on cell
identifiers and location area codes (LACs), run the SET BTSUSERPWD
command with Username and Password Type set to By Cell CI and LAC.
SET BTSUSERPWD: IDTYPE=BYID, BTSID=123, UPTYPE=CI_LAC;
Feature ID None
33. Support for optimized BTS clock maintenance

Description The base station (BS) clock is remotely maintained based on location
information, which is provided by the BS clock module on the LMT.
Improvement Network jitter and phase discrimination data is collected to identify BS clock
faults.
Implementati Tasks are added on the LMT for monitoring the BS clock module and
on obtaining location information. Monitoring results are displayed on the LMT.
Related On the LMT, choose Monitor > GSM Monitoring > Clock Test.
Operation
Set Monitor Item, Site, and Duration, and then click Start.
View results.

Feature ID None
34. Support for isolation of E1/T1 ports on the POUc_TDM, EIUa, and OIUa when the BER
exceeds a specified threshold

Description When the BER of an E1/T1 link exceeds a specified threshold, the BSC
automatically blocks the E1/T1 link. A blocked E1/T1 link does not carry
any services. When detecting that the BER of a blocked E1/T1 link is lower
than a specified threshold, the BSC automatically unblocks the E1/T1 link.
Then, the E1/T1 link continues to carry services.
Improvement When detecting that the BER of an E1/T1 link has exceeded a specified
threshold, the POUc_TDM, EIUa, and OIUa automatically block the E1/T1
link and isolate its services.
User experience is improved by preventing time division multiplexing
(TDM) microwave transmission from being disconnected intermittently for
a long period of time.
Implementati 1. The SET E1T1 command is used to enable isolation of E1/T1 ports on
on the POUc_TDM, EIUa, and OIUa and to set an isolation threshold.
2. When detecting that the BER of an E1/T1 link has exceeded the specified
threshold, the POUc_TDM, EIUa, and OIUa automatically block the E1/T1
link, isolate its services, and report E1/T1 Excessive Bit Error Rate alarms
(alarm ID: 21207). When detecting that the BER of a blocked E1/T1 link is
lower than the specified threshold, the POUc_TDM, EIUa, and OIUa
automatically unblock the blocked E1/T1 link and clear E1/T1 Excessive Bit
Error Rate alarms (alarm ID: 21207).
Related 1. Run the SET E1T1 command to enable isolation of E1/T1 ports on the
Operation POUc_TDM, EIUa, and OIUa and to set an isolation threshold.
SET E1T1: SRN=0, SN=18, BT=POUc, PS=SINGLE, PN=0,
BERAUTOISOSW=ON, BERAUTOISOTHRD=O1E3_R5E4;
2. Run the LST E1T1 command to query execution results.
LST E1T1: SRN=0, SN=18, BT=POUc, PN=0, LstFormat=VERTICAL;
Feature ID None
35. Support for query of electronic labels of EMUs, cabinets, and optical modules using
MML commands

Description BSC6900 V900R013C00 enables users to query electronic labels of

environment monitoring units (EMUs), cabinets, and optical modules.
Improvemen Assets management is enhanced.
t
Implementat The DSP ELABEL command is used to query electronic labels of EMUs,
ion cabinets, or optical modules. Electronic labels of optical modules are reported
together with electronic labels of boards.
Related Run the DSP ELABEL command to query electronic labels of EMUs.
Operation DSP ELABEL: DEVTYPE=EMU, SRN=0;
Run the DSP ELABEL command to query electronic labels of cabinets.
DSP ELABEL: DEVTYPE=CAB, CN=0;
Run the DSP ELABEL command to query electronic labels of optical
modules.
DSP ELABEL: DEVTYPE=BOARD, SRN=0, SN=0;
36. Support for collecting the Ater-interface link disconnection log

Description The function is used to collect the Ater-interface link disconnection log.
Based on the log, users can locate the cause of the Ater-interface link
disconnection.
Improvemen The log helps locating the cause of the Ater-interface link disconnection.
t
Implementat A program used to log the Ater-interface link disconnection information is

ion added to the BSC. Therefore, the BSC can record the link disconnection
information and send the information to an external PC through a port on the
active SCU board.
Related 1. Connect a PC to the active SCUa/SCUb board in the faulty remote TC
Operation subrack as follows: Connect one end of an Ethernet cable to the PC and the
other end to port 10 or 11 on the SCUa board or port 6 or 7 on the SCUb
board.
2. Set the IP address of the PC to A.168.3.42, where A is the network
segment of the remote TC subrack, of which the mask is 255.0.0.0.
3. On the PC, log in to the FTP server with both the user name and password
of PARC. Obtain the log from the folder tcdebug through FTP. This folder
can be created on the FTP server.
4. Analyze the log on the PC to locate the cause of the Ater-interface link
disconnection.
PR Number CMM: BB4D41262
Feature ID None

37. Support for security alarms

Description Security alarms and security logs are important security protection functions
of radio devices. They inform the device OM personnel of the potential and
existing security threats and attacks in the system, and instruct them to handle
the security threats and attacks.
The following alarms are added to this version:
ALM-20850 Digital Certificate Will Be out of Valid Time
ALM-20851 Digital Certificate Loss, Expiry, or Damage
ALM-20852 Exceeded Failures of Logins by the Local User
ALM-21388 Invalid Packets Exceeding Alarm
Improvemen When the system is subjected to security threats or attacks, it reports security
t alarms in real time and records security logs. Users can view the alarms on
the LMT in real time and remove the threats and attacks by following the
alarm handling suggestions.
Implementat The system monitors the user login, digital certification usage, and received
ion invalid packets in real time. It reports security alarms and records security
logs when:
The number of failed attempts of user logins exceeds the threshold.
The digital certificate expires.
The number of received invalid packets exceeds the threshold.
After the system is no longer subjected to security threats, the alarms are
cleared.
Related None
Operation

38. Support for software integrity protection

Description Software integrity protection is achieved as follows:
The software package is signed digitally when it is prepared.
The digital signature is verified when the software package is installed. This
ensures that the software package is reliable and complete.
Improveme Software integrity protection allows timely detection of viruses or malicious
nt software distortion. This prevents devices from running insecure or infected
files.
Implementa The system signs the software package digitally by using a signing tool when
tion the software package is prepared.
After a user uploads the software package to the M2000 server or upgrade
client, the M2000 server or upgrade client verifies the digital signature of the
software package. If the digital signature does not pass the verification, the
software package is incomplete or has been distorted. The system forbids the
software package from being uploaded.
When the software package is installed, it verifies its digital signature. If the
digital signature does not pass the verification, the software package is
incomplete or has been distorted. The system forbids the software package
from being installed.
Related None
Operation
39. Support for M2000 upgrade integrality

Description In versions earlier than V900R013C00, after the upgrade client is started
using the M2000, the M2000 does not trace the upgrade operations and the
upgrade client performs the upgrade operations.
In V900R013C00, this function enables users to create an upgrade task and to
query the process, progress, and status of the upgrade task on the M2000
client. This function also enables users to save and view an upgrade report on
the M2000 client after the upgrade is complete.
Improvemen The effects of this function are as follows:
t A task of upgrading a base station controller is created on the M2000 client.
The interface of creating this task is the same as that of creating a task of
upgrading other types of network elements (NEs) on the M2000 client.
Users can query the upgrade progress, upgrade status, and upgrade result on
different M2000 clients.
After the upgrade is complete, the upgrade report is saved on the M2000
server. Users can view the upgrade report at any time after the upgrade is
complete.
Operation Type no longer needs to be specified when an NE is upgraded,
reducing misoperations. In addition, the password for user admin no longer
needs to be entered, omitting redundant authentication, when the BSC6810 or
BSC6900 products earlier than V900R013C0 are upgraded to BSC6900
V900R013C00.
Implementat When an NE is upgraded using the M2000, the M2000 provides the upgrade
ion type as well as the IP address and account information of the FTP server for
the NE. During the upgrade, the upgrade client uploads the information of the
upgrade progress and upgrade status to the FTP server so that the information
is displayed on the M2000 client. After the upgrade is complete, the NE
uploads the upgrade report to the FTP server. Then, the M2000 saves the
upgrade report so that users can view it at any time.
Related Upgrade and roll back an NE by using the M2000.
Operation
40. Support for automatic dialing test on the A interface for the slave BSC in the TC pool
scenario

Description The automatic A-interface dialing test is supported for the slave BSC in the
TC pool scenario.
Improvement The A-interface dialing test is mandatory after a BSC in BM/TC separated
mode is deployed. After the A-interface dialing test is supported, the dialing
test can be performed automatically, improving the working efficiency.
Implementati The dialing test on the A interface aims to check whether CICs on the A
on interface are normal. During a dialing test, the BSC tests the CICs one by one.
It identifies the MSISDN of the MS that is used for the dialing test and blocks
the CIC used by the test call after the call is released so that a CIC will not be
repeatedly tested. To enable the A interface dialing test on the slave BSC in a
TC pool scenario, the dialing test switch must be turned on at both the
primary BSC and the slave BSC.
This function can only be used by maintenance personnel during site
deployment because a large amount of A-interface CICs will be blocked after
this function is enabled. After performing dialing tests, disable this function
to unblock the CICs.
Related To enable this function, run the following command on the primary and slave
Operation BSCs respectively:
SET ATESTPARA: AINTFTESTENABLE=YES,
AINTFTESTMSISDN1="13511486327",
AINTFTESTBLOCKCICENABLE=YES,
AINTFTESTSAMPLINGENABLE=YES,
AINTFTESTSAMPLINGNUMBER=6, ATESTBSCID=5;
In this command,
 MSISDN1 in A Interface Test is the MSISDN of the MS used for the test;
 A Interface Block CIC and A Interface Sampling Test must be set to YES;
 A Interface E1/T1 Sampling Number is set according to the actual situation;
 ID of a BSC to be Tested is the ID of the slave BSC. When the test is
performed for a primary BSC or a BSC that is not in a TC pool, ID of a
BSC to be Tested must be set to 0.
 To disable this function, run the following command on the primary and
slave BSCs separately:
SET ATESTPARA: AINTFTESTENABLE=NO;
Feature ID None
41. Support for automatic detection of the connection between TNU boards in different
subracks

Description The BSC checks the connection between the TNU boards in different
subracks, and reports an alarm "Inter-Subrack Connection Resources exist
fault alarm" (ID: 21601) if a fault is detected. If a fault is detected on a link
that connects two active TNU boards, that link is isolated.
Improvemen The inter-subrack connections are checked periodically and an alarm is
t reported if any fault is detected. In addition, the faulty link is isolated to
avoid the one-way audio or no audio problem caused by the link fault.
Implementat The BSC periodically sends check data on the links between TNU boards in
ion different subracks.
Related This function is enabled by default.

Operation To disable this feature, run the following command on the primary and slave
BSCs separately:
SET TNSOFTPARA: SrConPathCheckSwitch=OFF;
To enable this function again, run the following command on the primary and
slave BSCs separately:
SET TNSOFTPARA: SrConPathCheckSwitch=ON;
Feature ID None
42. Support for the LAG in active and standby mode

Description The two links in a Link Aggregation Group (LAG) in active and standby
mode have different priorities. When the high-priority link is functional, the
data stream carried by the LAG is transmitted only over the high-priority
link. When the high-priority link is faulty, the data stream is transmitted
over the low-priority link.
Improvement In addition to the LAG in load sharing mode, the LAG in active and standby
mode is added to achieve flexible transmission networking.
Implementati 1. The Trunk group work mode and Revertive type parameters are added to
on the MML command ADD ETHTRK so that the LAG can work in either
load sharing mode (LOAD_SHARING) or active and standby mode
(ACTIVE_STANDBY), and the LAG can be of the revertive
(REVERTIVE) or non-revertive type (NON-REVERTIVE).
If the LAG in active and standby mode is set as the revertive type, the data
stream carried by the LAG will be switched back to the high-priority link
when the faulty high-priority link is recovered.
If the LAG in active and standby mode is set as the non-revertive type, the
data stream carried by the LAG will still be transmitted over the low-
priority link when the faulty high-priority link is recovered.
2. The Trunk group work mode and Port priority parameters are added to the
MML command ADD ETHTRKLNK so that links in the LAG can work in
either load sharing mode or active and standby mode and can be prioritized.
Related 1. To add an LAG in active and standby mode and of the non-revertive type,
Operation with the negotiation mode of static LACP, run the following command:
WORKMODE=ACTIVE_STANDBY, LACPMODE=STATIC_LACP,
FLOWCTRLSWITCH=ON;
2. To add two links with priorities 80 and 100 in an LAG in active and
standby mode, run the following command:
TRKLNKPN=0, WORKMODE=ACTIVE_STANDBY, PORTPRI=80;
TRKLNKPN=1, WORKMODE=ACTIVE_STANDBY, PORTPRI=100;
3. To query the status information about the LAG in active and standby
DSP ETHTRK: SRN=0, SN=18, TRKN=0;
4. To query the status information about a link in the LAG in active and
standby mode, run the following command:
DSP ETHTRKLNK: SRN=0, TRKLNKSN=18, TRKLNKPN=1;
PR Number None
43. Support for activating or deactivating the light emission function of a single optical port

Description The light emission function of a specific optical port on the POUc board
can be activated or deactivated by running the ACT OPTPORT or DEA
OPTPORT command respectively.
Improvement  Users can deactivate the light emission function of idle optical ports on
the POUc boards by running the DEA OPTPORT command on the
LMT. This reduces the power consumption of optical ports.
 Users can activate or deactivate the light emission function of optical
ports on the POUc boards by running the ACT OPTPORT or DEA
OPTPORT command respectively on the M2000 client. Then, users can
view the state of the optical ports on the peer devices connected to the
POUc boards. This ensures that these boards are connected to the peer
devices properly.
Implementation  The DEA OPTPORT command is added to deactivate the light
emission function of a specific optical port.
 The ACT OPTPORT command is added to activate the light emission
function of a specific optical port.
Related To deactivate the light emission function of a specific optical port, run the
Operation following command:
DEA OPTPORT: SRN=0, SN=18, PN=0;
To activate the light emission function of a specific optical port, run the
following command:
ACT OPTPORT: SRN=0, SN=18, PN=0;
PR Number None
44. Support for setting the generation threshold for B3 signal failure and B3 signal
degradation to IE-3 for an OIUa board

Description For an OIUa board, users can run the SET OPT command to set the
generation threshold for B3 signal failure and B3 signal degradation to IE-
3 and the corresponding recovery threshold to IE-4.
Improvement The enumeration values of the generation threshold for B3 signal failure
and for B3 signal degradation of the OIUa board are changed from [1E-9,
1E-8, 1E-7, 1E-6, 1E-5, 1E-4] to [1E-9, 1E-8, 1E-7, 1E-6, 1E-5, 1E-4, IE-
3]. This expands the value range, thereby improving the transmission
compatibility.
Implementatio The B3 signal fail threshold and B3 signal degraded threshold parameters
n are added with an enumeration value O1E3_R1E4.
Related To set the generation threshold for B3 signal failure to IE-3 and the
Operation recovery threshold for B3 signal failure to IE-4, run the following
command:
SET OPT: SRN=0, SN=18, BT=OIUa, B3SFTHRD=O1E3_R1E4;
To set the generation threshold for B3 signal degradation to IE-3 and the
recovery threshold for B3 signal degradation to IE-4, run the following
command:
SET OPT: SRN=0, SN=18, BT=OIUa, B3SDTHRD=O1E3_R1E4;
PR Number None
45. Support for automatic LMT screen lockup

Description The function of automatic screen lockup is added to the local maintenance
terminal (LMT). If no operation is performed on the LMT for 10 minutes
(default duration), the LMT screen is locked automatically. Users must
enter the password again when logging in to the LMT.
Improvement The LMT security is improved.
Implementatio A link for screen lockup is added to the LMT workspaces. This link
n enables automatic screen lockup and allows users to specify the screen
lockup duration.
If no operation is performed on the LMT for the duration, the LMT screen
is locked automatically.
Related Click Lockup Setting on the LMT. The Lockup Setting dialog box is
Operation displayed. Select Auto lockup and set the duration.
Enter the password again to log in to the LMT after the LMT screen is
locked.
SET OPT: SRN=0, SN=18, BT=OIUa, B3SDTHRD=O1E3_R1E4;
PR Number None
Feature ID None
46. Support for OMU database can be backed up and restored on the LMT

Description The OMU database can be backed up and restored on the LMT.
Improvement The OMU database can be backed up and restored in a fast, complete, and
secure manner.
Implementatio The Device Maintenance tab page on the LMT provides users with a
n graphical user interface (GUI), on which the OMU data is backed up and
restored.
Related To start the function of data backup and restore on the LMT, do as follows:
Operation On the Device Navigation Tree tab page, right-click BSC and choose
Backup Data or Restore Data. Alternatively, on the BSC Maintenance tab
page, unfold BSC Maintenance and click Backup Data or Restore Data.
To back up data, do as follows:
On the Backup Data tab page, click Backup. Enter a file name to back up
the current data as a file with the name. Click OK. The Progress dialog box
is displayed, showing the backup progress.
If file name is left blank, the current data is backed up as a file with the default name.
To download data, do as follows:
On the Backup Data tab page, select a backup file from the backup file list
and click Download. Specify a path that saves the backup file. The LMT
downloads the backup file from the OMU to the path on the LMT PC.
Click Save. The download progress is displayed.
To restore data, do as follows:
On the Restore Data tab page, select a backup file to be restored from the
backup file list and click Restore. A dialog box is displayed, prompting for
confirmation. Click OK and then click Restore Data. The Progress dialog
box is displayed, showing the restore progress. A message is displayed,
indicating that the data restore is complete.
To upload data, do as follows:
On the Restore Data tab page, click Upload. The Open window is
displayed, prompting for a file to be uploaded. Select a file from the LMT
PC and click Open. The LMT starts to upload the file to the OMU. The
upload progress is displayed.
To refresh data, do as follows:
On the Backup Data or Restore Data tab page, click Refresh. The list of
backup files is refreshed.
PR Number None
Feature ID None
47. Support for perceiving bandwidth saving effects

Description Multiplexing and compression techniques have been applied to IP-based

networks to save bandwidth. Bandwidth saving effects need to be directly
perceived by users.
With this feature, the bandwidth usage for PPP links and MP groups can be
monitored on the LMT. In addition, the formulas for calculating the
bandwidth-related counters about PPP links, MP groups, and logical ports
are optimized. This helps users accurately calculate the bandwidth and
directly perceive bandwidth saving effects.
Improvement The bandwidth usage for PPP links and MP groups is displayed in the real-
time performance monitoring window on the LMT.
The formulas for calculating the bandwidth-related counters about PPP
links, MP groups, and logical ports are optimized to ensure uniform and
accurate bandwidth calculation.
Implementatio The bandwidth usage for PPP links and MP groups is calculated based on
n the used bandwidth and displayed in a chart and numerically in the real-
time performance monitoring window on the LMT.
The header, payload, flag field, and cyclic redundancy check (CRC) field
are added to the formulas for calculating the bandwidth-related counters
about PPP links, MP groups, and logical ports.
Related None
Operation
PR Number None
Feature ID None
Modified Features
1. Performance improvement of running MML scripts in batches online on the CME

Description The performance of running MML scripts in batches online on the

Configuration Management Express (CME) is improved (this function is
displayed as BULK CM on the CME).
Improvement This function speeds up MML script execution in batches online on the
CME.
Implementati The online MML command execution involves the following procedures:
on 1.The configuration rule is verified on the OMU .
2.The host data is synchronized with the OMU data and takes effect.
These two procedures are implemented step by step in most cases. They
are optimized in the way that the second procedure of the current MML
command is performed at the same time as the first procedure of the next
MML command is performed. This shortens the whole process, thereby
speeding up the MML script execution.
Related Run MML scripts in batches on the CME(this function is displayed as
Operation BULK CM on the CME).
Feature ID None
2. Support for flow control on standby interface boards

Description Standby interface boards now support flow control. The details are as
follows:
1. Flow control is implemented based on CPU usage.
2. Flow control thresholds can be configured and queried.
3. When the traffic reaches or falls below a flow control threshold, a
flow control event (ID: 22835) is reported.
Improvement 1. Users can conveniently check whether a standby interface board
is under flow control.
2. The status of a standby interface board remains normal under
heavy traffic.
Implementation Flow control takes effect after a flow control threshold is set for each
controlled item. When the CPU usage of a standby interface board
reaches a flow control threshold, a flow control event (ID: 22835) is
reported stating that the interface board is under flow control. When
the CPU usage of the interface board drops below this flow control
threshold, another flow control event (ID: 22835) is reported stating
that the interface board is in the normal state.
Related 1. Run the SET FCCPUTHD command to set a flow control
Operation threshold for each controlled item. For example:
SET FCCPUTHD: BRDCLASS=INT, TRACECTHD=60;
2. Run the LST FCCPUTHD command to query the flow control
threshold for each controlled item. For example:
LST FCCPUTHD: LstFormat=VERTICAL;
3. Support for a license controlling Extended BCCH

Description The Extended BCCH feature is under license control from

V900R013C00 onwards.
Improvement The Extended BCCH feature is under license control.
Implementati The resource control item of the license for the Extended BCCH feature
on is configured using MML commands. When the license is insufficient,
the parameters 2Quater Message Transmission Channel and Channel
of Sending SI13 Message cannot be set to BCCHExt.
If the SI2Quater and SI13 messages are sent on an extended BCCH in
versions earlier than V900R013C00, a new license is required or the
Extended BCCH feature must be disabled before a BSC is upgraded to
V900R013C00 or later.
Related To disable the Extended BCCH feature, run the following commands:
Operations SET GCELLCCUTRANSYS: IDTYPE=BYID, CELLID=0,
POS2QUATER=BCCHNorm;
POSSI13=BCCH_Norm;
PR Number N/A
4. Support for Abis Independent Transmission

Description BSC6900 V900R012C01 supports RAN sharing. This function allows

multiple telecom operators to share one base station and associated auxiliary
devices and to share transmission resources under one base station and
power resources under one TRX.
BSC6900 V900R013C00 allows telecom operators to use their respective
Abis transmission resources and supports reporting of BTS multi-segment
TRX group capabilities. BSC6900 V900R013C00 logically differentiates
telecom operators when BSS sharing (implemented based on RAN sharing)
is used in Abis over IP mode. This facilitates assigning transmission
bandwidths to different telecom operators and preparing customized QoS
parameters.
Improvement Differentiated transmission bandwidth and QoS configurations are
supported so that telecom operators can make flexible business policies
when implementing BSS sharing.
Transmission resources under one base station can be shared among telecom
operators or exclusively used by their respective telecom operators.
BTS multi-segment TRX group capabilities can be reported.
Telecom operators can specify whether to separately use transmission
resources under a logic port.
Congestion problems in IP over Ethernet mode on the GBSC side can be
solved.
Implementati 1. The restrictions on the use of the SET BTSSHARING command are
on lifted. This ensures that Transmission Sharing Support can be set to NO
when Service Type is IP.
2. In Abis over TDM mode, the Operator Name parameter is configured in
the SET BTSIDLETS command. If the Transmission Sharing Support
parameter is set to NO, the system selects only the same idle timeslots as
those allocated to the operator of the cell for activating the secondary link
on the packet channel.
3. BTS multi-segment TRX group capabilities can be reported.
4. The parameter The type of operator is added to the ADD OPSEPINFO
and RMV OPSEPINFO commands for users to specify an operator type
(GSM or UMTS).
5. The Operator Separated Flag and Operator Separated Index parameters
are added to the ADD IPLOGICPORT and MOD IPLOGICPORT
commands, respectively. This helps users specify whether to share logic
ports among telecom operators.
6. The parameter The type of operator is added to the DSP ADJNODE
command and the operator index range is modified based on the operator
type. This helps users query the information about a specific telecom
operator.
7. The parameters The type of operator and CN Operator index are added to
the DSP IPLOGICPORT command for users to query the information
about a specific telecom operator under a logic port.
Related 1. Run the SET BTSSHARING command with Transmission Sharing
Operation Support set to NO.
2. Change the BTS service bearer mode.
Run the MOD BTS command to change Service Type to IP.

3. Set idle timeslots.

Run the SET BTSIDLETS command to set the Operator Name parameter.
4. Set operator separation information.
Run the ADD OPSEPINFO command to add target telecom operators to
the operator separation information table.
5. Configure the logic port tree.
Configure logic ports based on actual networking and congestion
conditions.
6. Bind logic ports with operator separation indexes.
Run the ADD IPLOGICPORT or MOD IPLOGICPORT command to set
operator separation indexes.
5. Support for SRVCC

Description Single Radio Voice Call Continuity (SRVCC) ensures that voice services are
smoothly handed over from an LTE network to a GERAN network, with the
help of VoIP service routing, control, and triggering provided by the IP
Multimedia Subsystem (IMS) and handover control provided by the Mobile
Management Entity (MME).
Unlike CSFB, SRVCC is a real LTE VoIP technique because voice services
are implemented in the LTE network. UEs access the IMS through the CS
domain in the GERAN network or through the LTE network. As a result,
continuity of voice services is ensured based on the IMS and UEs can be
handed over from the LTE network to the GERAN network.
SRVCC is applicable only to scenarios where the GERAN and LTE
networks cover the same area. In addition, SRVCC in Dual Transfer Mode
(DTM) is not supported.
Improvement Continuity of voice services is ensured when the GERAN and LTE
networks cover the same area during the evolution from GERAN to LTE.
Implementati In SRVCC, the source MSC (which is connected to the MME) interprets the
on PS-to-CS handover as an inter-MSC PS-to-CS handover, and then sends a
Prepare Handover Request message to the target MSC. The target MSC
assigns a default Service Area Identifier (SAI) as the ID of the source cell.
This SAI must be different from the one used by the UTRAN so that the
BSC can identify SRVCC handover requests.
Related 1. Run the SET GCELLNC2PARA command with Cell Service
Operation Reselection Allowed set to PERMIT.
2. Run the SET GCELLHOBASIC command to enable SRVCC.
3. Run the SET GCELLHOBASIC command to set the LTE SAI.

6. Support for AMR under BSC local switch

Description AMR can be used together with BSC local switch. Based on the AMR rate
sets and protocol-specified preferred rate sets of both the calling and called
parties under different BTSs, the BSC calculates a new rate adjustment
threshold. The purpose is to select the best AMR codec scheme for both
the calling and called parties under BSC local switch.
Improvemen Voice quality of calls under BSC local switch can be enhanced.
t
Implementat For AMR calling and called parties with the same rate type but different
ion rate sets, the codec rate sets are changed to the protocol-specified preferred
rate sets, respectively, through the robust AMR traffic synchronization
procedure. Then, BSC local switch is performed. If the calling party
occupies an AMR TCHF and the called party occupies an AMR TCHH, or
the other way round, the party that occupies an AMR TCHH is switched to
an AMR TCHF, and then the BSC adjusts the AMR codec rates of both
parties before BSC local switch is enabled.
Related Run the SET GCELLCCAMR command with Is RATSCCH Function
Operation Enabled set to Enable.
For details about the configuration of BSC local switch, see the Feature
Activation Guide.
7. Support for AMR under BTS local switch

Description AMR can be used together with BTS local switch. Based on the AMR rate
sets and protocol-specified preferred rate sets of both the calling and called
parties under a BTS, the BSC calculates a new rate adjustment threshold.
The purpose is to select the best AMR codec scheme for both the calling
and called parties under BTS local switch.
Improvemen Voice quality of calls under BTS local switch can be enhanced.
t
Implementat For AMR calling and called parties with the same rate type but different
ion rate sets, the codec rate sets are changed to the protocol-specified preferred
rate sets, respectively, through the robust AMR traffic synchronization
procedure. Then, BTS local switch is performed. If the calling party
occupies an AMR TCHF and the called party occupies an AMR TCHH, or
the other way round, the party that occupies an AMR TCHH is switched to
an AMR TCHF, and then the BSC adjusts the AMR codec rates of both
parties before BTS local switch is enabled.
Related Run the SET GCELLCCAMR command with Is RATSCCH Function
Operation Enabled set to Enable.
For details about the configuration of BSC local switch, see the Feature
Activation Guide.
8. Support for AMR FR

Description E-coder is introduced in BSC6900 V900R013C00 and it is used in A over
TDM scenarios. E-coder uses the enhanced filter and enhanced LSP
techniques to improve the voice quality of AMR FR services, without
affecting network interconnection or interworking. E-coder is not applicable
to the A over IP or TFO scenarios.
Improvement E-coder increases the Mean Opinion Score (MOS) by 0.05 to 0.12 and
slightly improves voice quality.
Implementati In A over TDM scenarios, an enhanced AMR encoder is used to encode
on voices that have been decoded in compliance with G.711, decreasing signal
distortion.
Related Run the SET TCPARA command with Coding Mode set to Enhanced code
Operation mode.
9. Support for AMR HR


techniques to improve the voice quality of AMR HR services, without
affecting network interconnection or interworking. E-coder is not applicable
to the A over IP or TFO scenarios.
Improvement E-coder increases the MOS by 0.05 to 0.12 and slightly improves voice
quality.
Implementati In A over TDM scenarios, an enhanced AMR encoder is used to encode
distortion.
Related Run the SET TCPARA command with Coding Mode set to Enhanced code
Operation mode.
10. Support for Enhanced Full Rate (EFR)

techniques to improve the voice quality of enhanced full rate (EFR)
services, without affecting network interconnection or interworking. E-
coder is not applicable to the A over IP or TFO scenarios.
Improvement E-coder increases the MOS by 0.05 to 0.12 and slightly improves voice
quality.
Implementati In A over TDM scenarios, an enhanced EFR encoder is used to encode
distortion.
Related Run the SET TCPARA command with Coding Mode set to Enhanced
Operation code mode.
11. Support for Enhancement Packet Loss Concealment (EPLC)

Description EPLC recovers and compensates for lost speech frames. This, to a certain
extent, solves the problem of speech frame loss during transmission in a poor
radio environment, hence improving voice quality, network performance, and
customer satisfaction. The packet loss prediction algorithm is optimized in
BSC6900 V900R013C00 so that received voice gets closer to the original
voice in fidelity, improving user experience.
Improvemen In the case of packet loss of various severity levels, the MOS can be
t increased by 0.1 to 0.2.
Implementat If packet loss occurs in the uplink on the Um or Abis interface, the AMR
ion decoder that is configured with EPLC recovers AMR code streams to obtain a
better voice waveform. This feature is applicable to A over TDM scenarios.
Related Run the SET TCPARA command with EPLC Switch set to ON.
Operation
12. Support for the enhanced functions of SCTP link trace

Description Based on the original SCTP Link Trace functions, the following functions
are added:
SCTP link tracing on interface boards
Improvement SCTP Link Trace functions, retained on the XPU board, are also added to
interface boards to help locate lost or erroneous packets in a faulty or
congested SCTP link on the interface board.
Implementati When SCTP Link Trace are started on the LMT, the OMU sends the
on signaling messages to be traced to the XPU and interface board where the
SCTP links are located.
After receiving the tracing command, the XPU and interface board start
tracing the messages and then send the traced data to the OMU.
The OMU parses the traced data and sends them to the LMT so that users
can view the traced data.
Related 1. Start the SCTP Link Trace function over the A interface.
Operation
2. Select FLOWTRACE on the SCTP trace page.

3. The traced data contains messages over the XPU and interface board,
which helps locate faults in the links by parsing the traced messages.
PR Number MBSCV9R13C00-OR-1030, MBSCV9R13C00-OR-1032
Feature ID None
13. Support for query of BTS failure cause

Description Users can query the detailed failure cause of a specified BTS on the LMT.
Improvemen This function facilitates fault location, thereby reducing the OPEX.
t
Implementat An interface is added to the LMT, on which the detailed failure cause of a
ion specified BTS can be queried.
Related On the BTS Maintenance tab page in the left pane of the Device Maintenance
Operation window, expand the BTS Maintenance node. Click Query Failure Cause of
Config Alarm. Query the detailed failure cause of a specified BTS on the
displayed window.
Feature ID None
14. Support for change of the RXU Specification parameter

Description In V900R013C00 or later, the RXU Specification parameter is changed from

optional to mandatory and its NA enumeration value is deleted.
Improvemen A value must be assigned to the RXU Specification parameter. This ensures
t that the software configuration at the BSC is consistent with the hardware
configuration.
Implementat The RXU Specification parameter in the ADD BTSRXUBRD command is
ion changed from optional to mandatory and is not assigned a default value. In
addition, its NA enumeration value is deleted
For a BTS upgrade, this function is implemented as follows:
If the source version does not support the RXU Specification parameter, the
RXU Specification parameter in V900R013C00 is set as guided by the
following table.
If the source version supports the RXU Specification parameter, then:
The original value of the RXU Specification parameter is retained after the
upgrade is complete if it is not NA.
The value of the RXU Specification parameter is reassigned as guided by the
following table if its original value is NA.
Board GRRU MRRU GRFU MRFU BTS390
Type 0E
RXU RRU30 RRU39 GRFU_ MRFU_ BTS390
Specific 08_V2 08_V2 V2 V2 0E_V1
ation
After
the
Upgrade
Is
Complet
e
The RXU Specification parameter is checked and updated after the upgrade
is complete.
Related Run the ADD BTSRXUBRD command on the LMT with RXU
Operation Specification set to an appropriate value.
PR Number None
Feature ID None
15. Support for query of BTS Equipment Serial Number

Description An MML command is added to V900R013C00 for querying the Equipment

Serial Number (ESN) of a non-IP-based BTS.
Improvement The ESN of a non-IP-based BTS can be queried at the BSC when the BTS is
working normally. This improves the efficiency of transforming a TDM-
based network to an IP-based network.
Implementati The DSP BTSESNINFO command is added.
on
Related To query the ESN of a non-IP-based BTS, run the following command:
Operation DSP BTSESNINFO: IDTYPE=BYID, BTSID=0;
PR Number None
Feature ID None
16. Support for OML backup algorithm optimization

Description The OML backup algorithm is optimized in V900R013C00. When OML
backup is enabled, the TRX timeslots are evenly distributed among all the
input E1 ports on a BTS. If the BTS has at least two E1s, cells are not out of
service even if some of the E1s are disconnected.
Improvement If a BTS is configured with at least two E1s and OML backup is enabled,
cells are not out of service even if some of the E1s are disconnected
Implementati When OML backup is enabled, the TRX timeslots are evenly distributed
on among all the input E1 ports on a BTS. The idle timeslots in TDM mode are
evenly distributed among all the input E1 ports on the BTS.
Related Run the following command with Configure Backup OML set to YES and
Operation TRX Timeslot Allocate Mode to Share Among all Ports:
SET BTSOMLBACKUP: IDTYPE=BYID, BTSID=0, OMLBKUP=YES,
TRXTSALLOC=ALL_PORT;
Feature ID None
17. Support for an adjacent node name containing a maximum of 64 characters

Description In versions earlier than V900R013C00, the name of an adjacent node

contains a maximum of 31 characters.
In V900R013C00, the name of an adjacent node contains a maximum of 64
characters.
Improvement The name of an adjacent node is equal in length to the name of a BTS
specified in the MML command ADD BTS. This achieves data
configuration consistency in the entire network.
Implementati The name of an adjacent node is extended from 31 to 64 characters.
on
Related Run the MML command ADD/MOD ADJNODE with the adjacent node
Operation name set to a maximum of 64 characters.
Feature ID None
18. Support for 3GPP protocols compliance

Description Huawei GBSS devices comply with 3GPP specifications. In compliance
with 3GPP Release 8, this feature enables Huawei GBSS devices to be
interconnected with other NEs that comply with 3GPP R99, Release 4,
Release 5, Release 6, Release 7, or Release 8. This provides diverse
services with optimal performance for subscribers and improves the
competitive edge of operators.
Effect Huawei GBSS devices support GSM and LTE interoperability
improvements that are specified in 3GPP TS 44018-8b0, TS 44060-890,
TS 45008-870, TS 43129-820, and TS 48018-860.
Implementati In compliance with 3GPP TS 44018-8b0, TS 44060-890, TS 45008-870,
on TS 43129-820, and TS 48018-860, Huawei GBSS devices support
associated message and signaling procedures.
Related None
Operations
Trouble MBSCV9R13C00-OR-79
Ticket
Number
Deleted Features
None


New Hardware
Name Description
FG2d PARC WP11FG2d 12-port FE or 4-port electronic GE interface

unit REV:d
GOUd PARC WP11GOUd 4-port packet over GE Optical interface Unit
REV:d
Modified Hardware
None.
Removed Hardware
None.


7.1.5 Alarm Updates

7.1.6 Event Updates



7.2 Resolved Issues

Resolved issues from V900R013C00SPC500 to V900R014C00SPC200, refer to 6.2Resolved
Issues.
Resolved issues from V900R012C01SPC500 to V900R013C00SPC500:

1. Solving the problem that the MML command RMV LICENSE is falsely contained in
command group G0
Description The MML command RMV LICENSE is falsely contained in
command group G0, in which all commands are used to query system
information.
Cause The command is falsely contained in command group G0.
Impact User experience is affected.
Severity Minor
Solution The command has been removed from command group G0.
PR Number CMM: DTS2010121504124

GCRMS: 4966654
Test Case ID T13-0121
2. Solving the problem that the MML command RMV LOGRST is falsely contained in
command group G_2
Description The MML command RMV LICENSE is falsely contained in command
group G_2, in which all commands are used to query configuration
information.
Cause The command is falsely contained in command group G_2.
Severity Minor
Solution The command has been removed from command group G_2.

GCRMS: 4966654
3. Solving the problem that the MML command SET SLFSLVSW is falsely contained in
command group G_1/G_8

Description The MML command SET SLFSLVSW is falsely contained in

command group G_1 and G_8, in which all commands are used to
query system and equipment information.
Cause The command is falsely contained in command group G_1/G_8,
whereas it should be contained in G_9.
Severity Minor
Solution The command has been removed from command group G_1/G_8 and
added to command group G_9.
GCRMS: 4966654
4. Solving the problem that a BTS cannot ping its controlling BSC after IP paths are
removed from and then added to the BTS
Description A BTS under the BSC cannot ping the BSC after users perform the
following operations:
1. Upgrade the BSC to BSC6900V900R012.
2. Remove all the IP paths from the BTS.
3. Add IP paths to the BTS.
Cause During the upgrade to BSC6900V900R012, the active SCU board
sends IP path configuration data to interface boards twice. Therefore,
the interface boards have redundant IP path configuration data. The
redundant data leads to the ping failure.
Impact The BSC can ping the BTS but the BTS cannot ping the BSC. This
problem does not affect BSC services.
Severity Minor
Solution During an upgrade, the active SCU board sends IP path configuration
data to interface boards only once.
5. Solving the problem that the assignment success rate drops when the Real-time Transport
Control Protocol (RTCP) is enabled

Description The assignment success rate during busy hours (BSCRPT.ASS.SUCC)

drops by 10% to 50% when both the following conditions are met:
RTCP is enabled.
The FG2a or UOIa is used as the A interface board.
To check whether RTCP is enabled, run the LST GCNNODE command.
RTCP is enabled if the command output shows its status is OPEN.
Cause In V900R013, RTCP reliability over the A interface was optimized.
However, internal resource consumption was increased at the same time.
When the FG2a or UOIa is used as the A interface board, RTCP data flow
setup consumes twice as many internal resources as what is expected by
design. During busy hours, internal resources may be insufficient, leading
to assignment failures.
Impact During busy hours, voice calls may fail.
Severity Major
Solution The software has been improved so that the internal resource consumption
meets the designed specifications.
6. Solving the problem that some bandwidth-related performance counters may not be
accurately measured

Description When the configured bandwidth and the traffic volume are both high,
bandwidth-related performance counters may not be accurately measured,
for example, the average forward bandwidth allocated to logical ports
(VS.LGCPRT.Alloced.Ave.Fwd) and the average backward bandwidth
allocated to logical ports (VS.LGCPRT.Alloced.Ave.Bwd).
Cause The measurement period of the raw counters for this type of performance
counters is 60 minutes. If the traffic volume exceeds 18 Mbit/s, the value
of the accumulated bandwidth within 15 seconds exceeds 32 digits when
converted to a binary number. The calculation is as follows:
18 x 1024 x 1024 x (60 x 60/15) = 10E000000
The corresponding variable on the equipment allows for only 32 binary
digits. When the value of the accumulated bandwidth exceeds 32 binary
digits, it is reset to 0. As a result, the average bandwidth values cannot be
accurately calculated.
Impact The values of some bandwidth-related performance counters are incorrect.
Severity Warning
Solution The number of binary digits in the variable on the equipment has been
increased to accommodate the digits in the value of the accumulated
bandwidth.
7. Solving the problem that an alarm is not reported after the IP route for an IP path is
removed
Description After the RMV IPRT command is run to remove the IP route for an IP
path, the IP path has no carrying port and experiences a disconnection on
the physical link. When this occurs, an alarm about an IP path fault is
supposed to be reported, but it is not reported.
Cause There is a defect in the mechanism for processing IP path faults.
Severity Minor
Solution The mechanism for processing IP path faults has been improved. This
ensures that an alarm is reported when an IP path fault occurs due to the
lack of carrying port configuration.
8. Solving the problem that the help information on the LMT does not include the
specifications for IP paths on the FG2a, GOUa, or UOIa (IP)

Description The system imposes restrictions on the specifications for IP paths

configured on the FG2a, GOUa, and UOIa (IP), because these boards
provide only limited support for IP paths. However, the help information
on the LMT does not include the specifications for IP paths configured on
these boards.
Cause The specifications for IP paths on the FG2a, GOUa, and UOIa (IP) are
missing from the help information on the LMT.
Impact Users may be confused when configuring IP paths.
Severity Warning
Solution The following content has been added to the help information for the ADD
IPPATH command:
For FG2a, GOUa, and UOIa(IP) board, because of the limit of the board's
capacity, the SCTP link, NodeBIP and IPPATH numbers on one board
should obey the following rules: (the number of SCTP link + NodeBIP +
No-Qos IPPATH + 14*Qos IPPATH) <= 2048.
9. Solving the problem that the alarm ALM-20715 OMU File Synchronization Failure
cannot be cleared automatically
Problem The alarm OMU File Synchronization Failure is reported and cannot be
Description cleared automatically after the /ftp/bts_upgrade/backup_file directory
is removed from the OMU.
Cause The /ftp/bts_upgrade/backup_file directory cannot be created
automatically after it is removed from the OMU.
Impact The alarm OMU File Synchronization Failure is reported and cannot be
cleared automatically.
Severity Minor
Solution Monitor the /ftp/bts_upgrade/backup_file directory in real time so that

it is created automatically after it is removed from the OMU.
10. Solving the problem that the performance counter PEAK.BSC.PROC.SPEED is not
accurately measured

Description When the standby board in an active/standby pair provides the active port,
the value of the performance counter PEAK.BSC.PROC.SPEED is smaller
than what it should be.
Cause In earlier versions, statistics are not collected for data received and sent by
standby boards. When the standby board in an active/standby pair provides
the active port, only traffic over the standby port provided by the active
board is reported to the service layer.
Impact After the version is upgraded, traffic over the active port provided by the
standby board in an active/standby pair is also reported to the service
layer, and the amount of data received over this port is greater than the
amount of data sent over this port. As a result, the value of this counter
increases manifold compared to the value before the upgrade.
Severity Minor
Solution Measures have been taken so that statistics are collected for traffic over
ports provided by both active and standby boards.
11. Solving the problem that errors exist in the calculation of performance counters
measuring MTP2 bandwidth utilization efficiency
Description In earlier versions, the values of the performance counters
MTP2.LNK.RATIO.TX and MTP2.LNK.RATIO.RX measuring MTP2
bandwidth utilization efficiency are smaller than what they should be.
Cause The values of these counters are percentages, but decimals are reported.
Since the calculation formulas do not multiply decimal calculation results
by 100 to obtain percentages, the displayed values are one-hundredth of
what they should be.
Impact After the version is upgraded, the values of these performance counters
increases 100-fold.
Severity Minor
Solution The calculation formulas for these two performance counters have been
corrected.
12. Solving the problem that an RNC does not receive any response from the BSC at the
peer end after sending common measurement initiation requests

Description The connection between the RNC and the BSC is broken for 15 to 20
seconds due to a transmission interruption on the Iur-g interface. Then, the
BSC discards all the common measurement initiation requests from the
RNC without responding.
Cause The value of the Anti DPC Intermittent Disconnect Timer on the Iur-g
interface is 15 seconds on the BSC side and the value of this timer on the
Iur-g interface is 20 seconds on the RNC side. This timer is
unconfigurable.
When the timer on the BSC expires and the timer on the RNC does not
expire, the BSC releases application-layer data for the Signaling
Connection Control Part (SCCP) link.
After being reconnected to the BSC, the RNC continues sending common
measurement initiation requests to the BSC over the SCCP link. After
receiving these requests, the BSC fails to interpret them because it has
released the application-layer data for the SCCP link. Then, the BSC
discards these requests without responding.
Impact The BSC fails to exchange load information with the RNC.
Severity Minor
Solution The value of the timer on the BSC side has been changed to 20 seconds.
13. Solving the problem that MTP2 links are disconnected and cannot be reestablished
Description In BM/TC separated mode, Message Transfer Part level 2 (MTP2) links
carried on the EIUa, OIUa, or POUc board in the TC subrack are
disconnected and cannot be reestablished.
Cause The time division multiplexing (TDM) switching chip of the EIUa, OIUa,
or POUc board in the TC subrack encounters a soft error, leading to failure
in TDM transmission.
Impact Services carried on the MTP2 links are interrupted.
Severity Major
Solution The RNC checks the TDM switching chip of the EIUa, OIUa, or POUc
board in the TC subrack when MTP2 links are disconnected. If a soft error
is found, the RNC reports an alarm and resets the board.
14. Solving the problem that the CPU usage of the active GOUa board reaches 100% in
heavy traffic

Description The CPU usage of the active GOUa board reaches 100% in heavy traffic.
Cause The flow control algorithm of the GOUa board is defective. As a result,
the traffic load on the GOUa board exceeds the service processing
capability of the GOUa board when the traffic is heavy.
Impact Packets are lost during transmission and some cells are unavailable.
Severity Minor
Solution The flow control algorithm of the GOUa board has been optimized to
ensure that the traffic load on the GOUa board will not exceed the service
processing capability of the GOUa board.
15. Solving the problem that the XPUa or XPUb board is reset after one-way audio detection
is enabled
Description After one-way audio detection is enabled, the XPUa or XPUb board is
reset when a call that occupies resources of two BM subracks in a BSC
encounters the one-way audio problem.
Cause After one-way audio detection is enabled, the OMU logs every detected
one-way audio problem. Currently, a log for the one-way audio problem
allows a maximum of 1024 bytes. The one-way audio log for a call that
occupies resources of two BM subracks in a BSC, however, may exceed
1024 bytes. If this happens, the stack memory will be damaged and
therefore the XPUa or XPUb board will be reset.
Impact Services carried by the reset XPUa or XPUb board are interrupted.
This problem occurs at a low probability.
Severity Major
Solution The space allowed for a one-way audio log is expanded to 1536 bytes.
16. Solving the problem that the cell broadcast and the simple cell broadcast functions
become unavailable after XPU boards are reset

Description After a BSC is upgraded to V900R013C00SPC200 or

V900R013C00SPC300, the cell broadcast and the simple cell broadcast
functions become unavailable when any of the following conditions is
met:
 The BSC is reset.
 XPU boards are reset.
 The active and standby XPU boards are switched over.
 Boards in the BM subrack are reset.
Cause The data of the XPU boards will be reloaded after the boards are reset.
Due to a software bug, the BSC fails to reload the data for the two
functions.
Impact The two functions are unavailable.
Severity Minor
Solution The bug has been fixed so that the BSC successfully reloads the data for
the two functions.
17. Solving the problem that some counters related to random access are incorrectly
measured

Description If both the parameters Access Cause Statistics Optimization Sw and

Non-Call Immediate Ass Stat Opt Sw are set to ON, the value of the
counter Success Rate of Random Access is greater than 100%, and the
values of the counters Immediate Assignment Commands (SDCCH),
Immediate Assignment Commands (TCHF), Immediate Assignment
Commands (TCHH), and Immediate Assignment Commands (Circuit
Service) are greater than the actual values.
Cause The number of immediate assignment commands is measured twice:
when the BSC sends an immediate assignment command and when the
BSC receives a link setup indication message. As a result, the measured
value is greater than the actual value.
The type of channel in use determines which one of the following
counters will be measured: Immediate Assignment Commands
(SDCCH), Immediate Assignment Commands (TCHF), and Immediate
Assignment Commands (TCHH).
The counter Success Rate of Random Access is calculated using the
following formula:
Success Rate of Random Access = Immediate Assignment Commands
(Circuit Service) x {100}/Channel Requests (Circuit Service)
Where,
Immediate Assignment Commands (Circuit Service) = Immediate
Assignment Commands (SDCCH) + Immediate Assignment Commands
(TCHF) + Immediate Assignment Commands (TCHH)
Impact The value of the counter Success Rate of Random Access is greater than
100%, and the values of the counters Immediate Assignment Commands
(SDCCH), Immediate Assignment Commands (TCHF), Immediate
Assignment Commands (TCHH), and Immediate Assignment
Commands (Circuit Service) are greater than the actual values.
Severity Minor
Solution The mechanism for measuring the number of immediate assignment

commands has been optimized so that the measurement is triggered only
when the BSC receives a link setup indication message.
18. Solving the problem that the value of the counter Success Rate of Radio Handover is
greater than 100%

Description In A over IP mode, there is a low probability that the value of the counter
Success Rate of Radio Handover is greater than 100%.
Cause In A over IP mode, the BSC measures the number of handover requests
after it sends an Internal Ho Req message to the CN.
Normally, the CN responds with an Internal Ho Cmd message and the
BSC measures the number of handover commands and the number of
unsuccessful handovers if any.
If exceptions occur, the CN does not respond with an Internal Ho Cmd
message. Instead, it sends an A interface connection release indication to
release the call. In this case, the BSC should measure the number of
unsuccessful handovers. Due to a software bug in RAN13, however, the
BSC does not measure the number of unsuccessful handovers. As a
result, the measured number of unsuccessful handovers is less than the
actual number.
The counter RH303A: Success Rate of Radio Handover is calculated
using the following formulas:
Success Rate of Radio Handover = Number of successful handovers x
{100%}/Number of handover commands
Number of successful handovers = Number of handover requests -
Number of unsuccessful handovers
Because the number of unsuccessful handovers is less than the actual
number, the value of the counter Success Rate of Radio Handover is
greater than the actual value or even exceeds 100%.
Impact The value of the counter Success Rate of Radio Handover is greater than
100%.
Severity Minor
Solution The software bug has been fixed so that the number of unsuccessful
handovers is measured when the CN sends an A interface connection
release indication to release the call.
19. Solving the problem that a small number of MSs process AMR services on TCHHs in a
cell

Description A small number of MSs process Adaptive Multi Rate (AMR) services on
TCHHs in a cell.
Cause The formula for calculating the percentage of MSs processing AMR
services on TCHHs in a cell is defective. As a result, the calculated value
is less than the actual value. Therefore, a cell fails to be assigned any
TCHHs when the calculated value does not reach the Ratio of AMR-
HR in the SET GCELLCHMGBASIC command.
Impact Speech quality is affected.
Severity Minor
Solution This formula has been rectified.
20. Solving the problem that the value of the counter Call Drops on Traffic Channel is not
equal to the sum of related counter values
Description When call drops occur because of Abis link disconnection, the value of
the counter Call Drops on Traffic Channel is not equal to the sum of the
following counters:
 Call Drops on TCH(TA)
 Call Drops on TCH(Uplink Received Level)
 Call Drops on TCH(Downlink Received Level)
 Call Drops on TCH(Uplink and Downlink Received Level)
 Call Drops on TCH(Uplink FER)
 Call Drops on TCH(Downlink FER)
 Call Drops on TCH(Uplink and Downlink FER)
 Call Drops on TCH(Uplink Quality)
 Call Drops on TCH(Downlink Quality)
 Call Drops on TCH(Uplink and Downlink Quality)
 Call Drops on TCH(Other)
Cause Due to a software bug, the counter Call Drops on Traffic Channel is not
updated with the preceding counters.
Impact The measurement of the counter Call Drops on Traffic Channel is
incorrect.
Severity Minor
Solution In BSC6900 V900R013C00SPC200, the preceding counters are not

increased by one when call drops occur because of Abis link
disconnection.

21. Solving the problem that the counter Channel Conversion Requests (TCHF-TCHH) and
the other 15 counters are incremented
Description In BSC6900 V900R013C00SPC500, the counter Channel Conversion
Requests (TCHF-TCHH) and the following 15 counters are
incremented:
 Mean Number of SDCCHs in Interference Band N in One Location
Group
 Mean Number of TCHFs in Interference Band N in One Location
Group
 Mean Number of TCHHs in Interference Band N in One Location
Group
N: an integer ranging from 1 to 5
Cause Due to a software bug, the preceding 16 counters are updated along with
the counter Number of Available Channels During Spectrum Sharing.
Impact The preceding 16 counters are incremented.
Severity Minor
Solution The bug has been fixed so that the preceding 16 counters are not updated
along with the counter Number of Available Channels During Spectrum
Sharing.
PR Number DTS2011031601742 and DTS2011032800647
22. Solving the problem that the counters of call drops on SDCCHs are incorrectly measured
Description The following counters are incorrectly measured when call drops occur
on TCHs carrying signaling data:
 Call Drops on SDCCH(TA)
 Call Drops on SDCCH(Received Level)
 Call Drops on SDCCH(Quality)
 Call Drops on SDCCH(Other)
Cause This problem is caused by a software bug.
Impact The values of the preceding counters increase when call drops occur on
TCHs carrying signaling data.
Severity Minor
Solution The bug has been fixed so that the preceding counters are correctly
measured.

23. Solving the problem that the TCHH usage increases with the PDCH usage in busy hours
Description The TCHH usage increases with the PDCH usage in busy hours.
Cause When the TCH usage reaches the TCH traffic busy threshold specified
by TCH Traffic Busy Threshold in the SET GCELLCHMGAD
command, TCHHs are preferentially assigned to guarantee network
capacity.
The formula for calculating the TCH usage is as follows:
TCH usage = (Occupied TCHFs in busy hours + Occupied TCHHs in
busy hours/2)/(Available TCHFs + Available TCHHs/2) x 100%
The BSC assigns a fixed number of traffic channels to a cell, including
TCHFs, TCHHs, and PDCHs. According to the preceding formula, the
TCH usage increases with the PDCH usage because assigned TCHFs
may have been converted into PDCHs. As a result, the TCHH usage
increases.
Impact Speech quality deteriorates.
Severity Minor
Solution A new parameter Traffic Busy Thres Calculation Opt Sw is added to

the SET BSCBASIC command. The following formula is added for
calculating the TCH usage in busy hours:
TCH usage = (Occupied TCHFs in busy hours + Occupied TCHHs in
busy hours/2)/(Available TCHFs + Available TCHHs/2 + Preemptable
PDCHs) x 100%
The formula is used when the following conditions are met:
Type of Cell Load Calculation in the SET GCELLCHMGAD
command is set to DYNPDCHASIDLE(Count dynamic PDCH(Idle)).
Traffic Busy Thres Calculation Opt Sw in the SET BSCBASIC
command is set to OPEN(Open).
24. Solving the problem that the MCPA algorithm is defective in channel allocation when the
power for an overloaded timeslot is higher than a specific threshold

Description When the power for an overloaded timeslot is higher than a specific
threshold, the multi-carrier power amplifier (MCPA) algorithm still
allows this timeslot to be allocated to a call, leading to uneven allocation
of power among timeslots.
Cause The MCPA algorithm is defective and does not consider whether the
power for an overloaded timeslot is higher than the threshold.
Impact An increased number of handovers are trigged because of power
insufficiency, and peak clipping occurs more frequently in timeslots. As a
result, the interference becomes stronger.
Severity Minor
Solution The PWR Optimization for Overloaded MCPA TSs parameter has
been added to the SET GCELLCHMGAD command. When this
parameter is set to YES, the MCPA algorithm does not allow an
overloaded timeslot to be allocated to a call if the power for this timeslot
is higher than the threshold. An example use of this command is as
follows:
MCPACHAPPOPT=YES;
25. Solving the problem that the handover algorithm leads to ping-pong handovers and the
power control algorithm leads to inaccurate power control

Description When baseband frequency hopping is used and involves the Broadcast
Control Channel (BCCH) TRX, power control may be inaccurate, and
ping-pong handovers may occur.
Cause In this scenario, an MS hops onto the BCCH TRX and the TCH TRX in
different timeslots. The TCH TRX will perform power control when the
BCCH TRX operates at full power. The MS samples the signal levels on
the BCCH TRX and TCH TRX, calculates its power based on the
sampling result, and reports the calculated value to the BSC.
Currently, the BSC uses different methods for compensating for signal
level loss caused by power control and handovers.
 If the CANPC parameter is set to NO, the BSC only considers the
signal level of the MS on the TCH TRX to compensate for signal level
loss caused by power control. This leads to overcompensation and an
extended step for power control. Compensation for signal level loss
caused by handovers is correct in this case.
 If the CANPC parameter is set to YES, the BSC compensates less for
signal loss caused by handovers than for signal loss caused by power
control. This leads to ping-pong handovers. Compensation for signal
level loss caused by power control is correct in this case.
In other words, the compensation method for cases where CANPC is set
to NO is used when CANPC is set to YES, and the compensation
method to be used when CANPC is set to YES is used when CANPC is
set to NO.
Impact Power control is inaccurate, and ping-pong handovers easily occur. This
compromises voice quality and increases interference, especially when
frequency hopping involves only a small number of TRXs.
Severity Minor
Solution The Power Control and Handover CMP CON Sw parameter has been
added to the SET GCELLOTHEXT command. When this parameter is
set to YES, the BSC uses the same method for compensating for signal
level loss caused by power control and handovers. An example use is as
follows:
SET GCELLOTHEXT: IDTYPE=BYID, CELLID=0,
PCHOCMPCON=YES;
Details about the BSC using the same compensation method are as
follows:
When a call is occupying the BCCH TRX:
 Compensation is not performed if frequency hopping is not used or
frequency hopping is used but does not involve the BCCH TRX.
 The following formula is used if frequency hopping involves the
BCCH TRX and CANPC is set to YES:
 Compensation value = 2 x power control level
BCCH TRX and CANPC is set to NO:
Compensation value = (N –1)/N x power control level x 2
Where, N is the number of TRXs involved in frequency hopping.
When the call is not occupying the BCCH TRX:

 The following formula is used if the BCCH TRX is not involved in

frequency hopping:
BCCH TRX and CANPC is set to YES:
BCCH TRX and CANPC is set to NO:
Compensation value = (N –1)/N x power control level x 2
Where, N is the number of TRXs involved in frequency hopping.
26. Solving the problem that no channels are available for trunk services
Description When trunk services are enabled over a public network, no channels are
available for trunk services in a cell if both the following conditions are
met:
The cell load is heavy.
All channels are occupied.
Cause To improve voice quality and mitigate interference, trunk services over a
public network use only full-rate channels. In versions earlier than
BSC6900V900R013, when channel resources are insufficient, the BSC
ensures that a number of channels are available for trunk services, but
these channels are randomly picked and may include half-rate channels.
When the cell load is heavy, full-rate channels in the cell are converted to
half-rate channels, and therefore no full-rate channels are available for
trunk services anymore. When a user initiates a trunk service in this cell,
it is difficult for half-rate channels to convert to full-rate channels,
because most of the half-rate channels are occupied. As a result, no full-
rate channels can be allocated to the trunk service.
Impact Trunk-service users cannot use any channels and fail to access the
network.
Severity Minor
Solution Measures have been taken so that:

A number of full-rate channels are always reserved for trunk services.
All sub-channels on the reserved channels can be allocated only to trunk
services.
If one of the reserved channels becomes faulty, an available channel will
substitute it.

27. Solving the problem that the values of some counters are small when full-rate speech
version 5 is used
Description When full-rate speech version 5 is used, the following counters are not
measured:
 Number of MRs (TA = M)
 Number of MRs (TA = 30 or 31)
 Number of MRs (TA = 40 to 44)
 Number of MRs (TA greater than 63)
 RQI (TA = N)
 RQI (TA = 30 or 31)
 RQI (TA = 32 or 33)
 RQI (TA = 34 or 35)
 RQI (TA = 36 or 37)
 RQI (TA = 38 or 39)
 RQI (TA = 40 to 44)
 RQI (TA = 45 to 49)
 RQI (TA = 50 to 54)
 RQI (TA = 55 to 63)
 RQI (TA greater than 63)
M: an integer ranging from 0 to 29

Cause This problem is caused by a software bug.
Impact The values of the preceding counters decrease.
Severity Minor
Solution The bug has been fixed.
28. Solving the problem that the TFO function is disabled when an MS is handed over again

Description With the speech version optimization function enabled, a handover is

triggered and the Tandem Free Operation (TFO) function is
implemented. The TFO function, however, is disabled when the MS is
handed over again.
Cause The BSC uses an incorrect cause value for the initial handover because
this cause value does not require the setting of a TFO flag. However,
when the MS is handed over again, the BSC must determine whether to
change speech versions based on the setting of the TFO flag. As a result,
the BSC changes speech versions because the TFO flag is not set, and
the TFO function is disabled.
Impact The MS is successfully handed over though speech quality deteriorates.
The values of the following two counters may fluctuate after a BSC is
upgraded to BSC6900 V900R013C00SPC500:
 Full Rate AMR TCH Successful Handover Occupancy Times (Service
Channel)
 Half Rate AMR TCH Successful Handover Occupancy Times (Service
Channel)
Severity Minor
Solution The BSC uses correct handover cause values to set TFO flags.
29. Solving the problem that the downlink path loss calculated by handover algorithm II is
small
Description When handover algorithm II is used during TCHH/TCHF handovers, the
calculated downlink path loss is small.
Cause The formula for calculating the downlink path loss is as follows:
Downlink path loss = Actual transmit power of the BTS – Actual receive
level of an MS
However, the algorithm uses the compensated receive level of an MS, not
the actual receive level of the MS.
Impact TCHF-to-TCHH handovers can be easily initiated but TCHH-to-TCHF
handovers cannot. As a result, a large number of MSs process services on
TCHHs, and traffic in the cell decreases.
Severity Minor
Solution Handover algorithm II uses the actual receive level of an MS.
30. Solving the problem that an intra-BSC asynchronous handover fails

Description During an intra-BSC asynchronous handover, the value of the

Information Element (IE) Handover Reference in the channel activation
message is different from that of the same IE in the handover command.
This results in handover failures.
Cause If the BSC receives a forced handover indication immediately after
sending a channel activation message, it uses the value of Handover
Reference contained in the indication as that of the same IE in the
follow-up handover command. This results in the inconsistency of IE
values between the channel activation message and the handover
command.
Impact The intra-BSC asynchronous handover fails and the handover success
rate decreases.
Severity Minor
Solution The BSC processes a forced handover indication only after receiving a
channel activation acknowledgment message.
31. Solving the problem that the counter TO314: Failed Outgoing Inter-Cell Handovers in
One Location Group is measured in a non-location group cell
Description After an MS fails to be handed over from a non-location group cell to a
location group cell and return to the original channel, the counter
TO314: Failed Outgoing Inter-Cell Handovers in One Location Group is
mistakenly measured in the source cell.
Cause When the number of unsuccessful handovers in the source cell is
measured, the location group information contained in the Handover
Detect message sent by the target cell is mistaken for the information of
the source cell. As a result, the counter Failed Outgoing Inter-Cell
Handovers in One Location Group is mistakenly measured in the source
cell.
Impact The counter TO314: Failed Outgoing Inter-Cell Handovers in One
Location Group is mistakenly measured in the source cell.
Severity Minor
Solution The mechanism for measuring this counter was rectified so that correct
location group information is used during the measurement.
32. Solving the problem that the co-cell location group measurement objects can measure
only a maximum of six location groups

Description The measurement objects Measurement of Cell Location Group

Performance and Measurement of TRX Location Group Performance
can measure only a maximum of six location groups.
Cause The BTSs of earlier versions support a maximum of six location groups,
and accordingly the BSC supports the measurement of performance
counters on only a maximum of six location groups. When the BTS
capacity is expanded, however, the BSC capability is not improved with
the BTS capability and as a result the counters still measure a maximum
of six location groups.
Impact If more than six location groups are configured, the preceding
measurement objects measure only the first six location groups.
Severity Minor
Solution The BSC capability is improved to support the measurement of

performance counters on a maximum of 18 location groups.
33. Solving the problem that the BSC does not promptly report the values of some counters
in a measurement period

Description The BSC does not promptly report the values of the following counters
in a measurement period:
 HM310: Number of Bursts with High-Order Modulation Power
Increase of 0.4 dB
Increase of 0.8 dB
Increase of 1.2 dB
Increase of 1.6 dB
Increase of 2.0 dB
Increase of 2.4 dB
Increase of 2.8 dB
Increase of 3.2 dB
Increase of 3.6 dB
Increase of 4.0 dB or Above
As a result, the value of the counter HM300: Number of Bursts in High-
Order Modulation Scheme is smaller than the sum of the preceding
counter values.
Cause There are two mechanisms available for reporting the counter values.
One mechanism operates in the following way:
When 30 counters are successfully measured, the BSC reports the values
of the 30 counters.
The other mechanism operates in the following way:
The BSC reports a certain number of counter values at an interval of 100
ms.
When the former mechanism is used, the BSC has to report the values of
some counters in the next measurement period. Due to a software bug,
the BSC does not check all TRXs and cells when the latter mechanism is
used.
Impact The values of some counters are incorrect.
Severity Minor
Solution The bug has been fixed so that the BSC checks all TRXs and cells when
the latter mechanism is used.

34. Solving the problem that the BSC fails to initiate handovers for MSs that support only
full-rate speech version 1 when Speech Version Protocol Expand is set to YES(Yes)
Description In A over IP mode, the BSC fails to initiate handovers for MSs that
support only full-rate speech version 1 when Speech Version Protocol
Expand in the SET AITFOTHPARA command is set to YES(Yes).
Cause When Speech Version Protocol Expand is set to YES(Yes), the BSC
disables the support for speech versions if the MSC supports only full-
rate speech version 1. As a result, the BSC fails to initiate any
handovers.
Impact In A over IP mode, the BSC cannot initiate handovers for MSs that
support only full-rate speech version 1 when Speech Version Protocol
Expand is set to YES(Yes).
Severity Minor
Solution When Speech Version Protocol Expand is set to YES(Yes), the BSC
no longer disables the support for speech versions if the MSC supports
only full-rate speech version 1.
35. Solving the problem that the counter Mean Number of Messages in the BSC Message
Library should not have been measured when simple cell broadcast is enabled
Description When simple cell broadcast is enabled at a BSC, the counter Mean
Number of Messages in the BSC Message Library is measured.
Cause This counter should be measured only when standard cell broadcast is
enabled. Due to a software bug, the counter is also measured when
simple cell broadcast is enabled.
Impact This counter is measured as 21840 when simple cell broadcast is
enabled.
Severity Minor
Solution The bug has been fixed so that the counter Mean Number of Messages
in the BSC Message Library is measured only when standard cell
broadcast is enabled.
36. Solving the problem that the value of the counter Distance Between MS and BTS
remains 0

Description The value of the counter Distance Between MS and BTS remains 0,
which is the initial value.
Cause The BSC does not measure the maximum distance between an MS and a
BTS if measurement reports are pre-processed by the BTS.
Impact The value of this counter remains 0.
Severity Minor
Solution Within a measurement period, after receiving pre-processed

measurement reports from the BTS, the BSC compares the Timing
Advance (TA) values in the valid pre-processed measurement reports.
Then, the BSC records the maximum TA value as the value of this
counter.
37. Solving the problem that the values of RQI-related counters greatly decrease after an
upgrade

Description After a BSC is upgraded to BSC6900 V900R013C00SPC200, the values

of the following Radio Quality Indication (RQI)-related counters greatly
decrease:
 RQI (TA = N)
 RQI (TA = 30 or 31)
 RQI (TA = 32 or 33)
 RQI (TA = 34 or 35)
 RQI (TA = 36 or 37)
 RQI (TA = 38 or 39)
 RQI (TA = 40 to 44)
 RQI (TA = 45 to 49)
 RQI (TA = 50 to 54)
 RQI (TA = 55 to 63)
 RQI (TA greater than 63)
Cause Due to a software bug, the following counters are mistakenly measured
as the preceding RQI-related counters:
 Number of MRs (TA = M)
 Number of MRs (TA greater than 63)
M: an integer ranging from 0 to 29
Impact The values of the preceding RQI-related counters greatly decrease after
the upgrade.
Severity Minor
Solution The bug has been fixed so that the preceding RQI-related counters are
measured correctly.
38. Solving the problem that requests for handing over MSs from TCHFs to TCHHs
decrease in A over IP mode

Description In A over IP mode, requests for handing over MSs from TCHFs to
TCHHs decrease if the Information Element (IE) Speech Codec List does
not include any of the following speech versions:
 Half-rate VER 1
 Half-rate VER 2
 Half-rate VER 3
This IE is contained in each channel assignment request that is designated
for a called party and is sent from the MSC to the BSC.
Cause In BSC6900 V900R011, when making TCHF-to-TCHH handover
decisions, the BSC does not determine whether MSs support any of the
preceding speech versions. In BSC6900 V900R013, when making the
decisions, the BSC determines whether MSs support one of these speech
versions. Then, MSs not supporting any of the three speech versions
cannot be handed over to TCHHs. This aims to save transmission
resources.
In BSC6900 V900R013, instead of using the IE Speech Version required
in the TCHF-to-TCHH handover decision procedure, the BSC uses the IE
Speech Codec List required in the channel assignment procedure when
making the handover decisions. This may result in TCHF-to-TCHH
handover failures. This problem is caused by a software bug.
In a channel assignment request designated for a called party, the IE
Speech Codec List uses the intersection of the following four parties'
support for speech versions:
 Cell where the calling party camps
 Cell where the called party camps
 Called party
 MSC
By doing this, the Transcoder Free Operation (TrFO) can be established
successfully.
The IE Speech Version uses the intersection of the following two parties'
support for speech versions:
 Called party
 MSC
In this case, there is a high probability that the IE Speech Version
includes one of the three speech versions if MSs support one of them.
As described earlier, the IE Speech Codec List is required only in the
channel assignment procedure and the IE Speech Version is required in
the TCHF-to-TCHH handover decision procedure.
According to the 3GPP, the two IEs use the intersection of the same
parties' support for speech versions. Due to a software bug at the MSC,
the two IEs use the intersection of different parties' support for speech
versions.
Because of these strict handover conditions, the BSC has difficulty
initiating TCHF-to-TCHH handover requests.
Impact Requests for handing over MSs from TCHFs to TCHHs decrease, which
may result in a higher congestion rate in a congested cell.
Severity Major

Solution The bug at the MSC has been fixed. The bug at the BSC has also been
fixed so that the IE Speech Version is used in the TCHF-to-TCHH
handover decision procedure.
39. Solving the problem that the counter Site Serving Normal Period is incorrectly measured
Description In versions earlier than BSC6900 V900R013C00SPC200, the counter
Site Serving Normal Period is incorrectly measured when the following
conditions are met:
 The measurement period of this counter is changed from 15 minutes to
60 minutes.
 The attribute Time Statistical Method of this counter is set to SUM.
Cause Due to a software bug, the values of this counter are not summed.
Instead, the minimum one in these values is obtained.
Impact This counter is incorrectly measured.
Severity Minor
Solution The bug has been fixed in BSC6900 V900R013C00SPC200.
40. Solving the problem that two counters are incorrectly measured

Description The following two counters are incorrectly measured in versions earlier
than BSC6900 V900R013C00SPC200:
 Number of Successful Uplink DTM Assignments Received on DCCH
 Number of Successful Downlink DTM Assignments Received on DCCH
This problem occurs when the following conditions are met:
 The measurement period of the two counters is changed from 15 minutes
to 60 minutes.
 The attribute Time Statistical Method of the two counters is set to
SUM.
Cause Due to a software bug, the values of the two counters are not summed.
Instead, the values are averaged.
Impact The values of the two counters are small.
Severity Minor
41. Solving the problem that counters related to Mean Bep are incorrectly measured
Description The following counters are incorrectly measured in versions earlier than
BSC6900 V900R013C00SPC200:
 Number of Times UPLINK_8PSK_MEAN_BEP=N
 Number of Times UPLINK_GMSK_MEAN_BEP=N
Cause Due to a software bug, the preceding counters are incorrectly measured.
For example, when an MS reports the value of Mean Bep as 0 and the MS
uses the Gaussian minimum shift-frequency keying (GMSK) modulation
scheme, the corresponding counter Number of Times
UPLINK_GMSK_MEAN_BEP=0 is not incremented by one. Instead,
another counter is incremented by one.
Impact The preceding counters are incorrectly measured.
Severity Minor
PR Number BB4D50809
42. Solving the problem that PTRAU performance counters are incorrectly measured

Description Packet-based Transcoder and Rate Adapter Unit (PTRAU) performance

counters at the TRX level are incorrectly measured.
Cause After reporting the values of PTRAU performance counters, the BSC
does not remove the corresponding object index but mistakenly removes
another object index. As a result, the counters that should have been
measured as 0 are incremented.
Impact The values of PTRAU performance counters listed in the following table
may be greater than expected.
Counter ID Counter Name
L9B01: Number of Received

RX.PACKETS
PTRAU Packets
L9B02: Number of Sent
TX.PACKETS
PTRAU Packets
L9B03: Number of Discarded
UPLINK.DISCARD.PACKETS PTRAU Packets During
Uplink Transmission
L9B04: Number of disorderly
DISORDER.PACKETS
received PTRAU Packets
Severity Minor
Solution The BSC removes the object index corresponding to the PTRAU
performance counters after reporting their values.
43. Solving the problem that the usage of advanced coding schemes and the throughput at
the RLC layer are slightly low

Description In scenarios with high signal quality over the Um interface, the BSC
does not immediately use advanced coding schemes to raise the service
data rate.
Cause MSs do not send measurement reports to the BSC immediately after
downlink temporary block flows (TBFs) are successfully established. As
a result, the BSC does not immediately use advanced coding scheme in
the downlink.
The BSC does not process the measurement reports immediately after
uplink TBFs are successfully established. As a result, the BSC does not
immediately use advanced coding schemes in the uplink.
Impact The usage of advanced coding schemes and the throughput at the RLC
layer are slightly low.
Severity Minor
Solution The TBF establishment procedure has been optimized as follows:

 The BSC requests MSs to send measurement reports immediately after
downlink TBFs are successfully established.
 The BSC processes measurement reports immediately after uplink
TBFs are successfully established.
44. Solving the problem that the downlink TBF retransmission rate at the RLC layer is
slightly high
Description MSs inform the BSC in the Packet Downlink Ack messages that some
data blocks are missing and the BSC repeatedly retransmits the data
blocks. As a result, the downlink TBF retransmission rate at the RLC
layer is slightly high.
Cause When the BSC transmits data blocks to an MS in sequence, the MS may
not receive the data blocks in the same sequence because transmission
delay may vary from one channel to another. Although the MS informs
the BSC that some data blocks are missing, these data blocks are actually
being transmitted. After receiving a retransmission request from the MS,
the BSC retransmits the data blocks without checking whether they have
been transmitted.
Impact The downlink TBF retransmission rate at the RLC layer is slightly high.
Severity Minor
Solution A mechanism has been added to check whether data blocks have been
transmitted. With this mechanism, the BSC will retransmit only the data
blocks that have not been transmitted.

45. Solving the problem that uplink TBFs fail to be released in time because uplink GPRS
data blocks use incorrect coding schemes
Description After scheduling data blocks for an uplink GPRS TBF, the BSC fails to
release the uplink TBF in time if it receives the blocks using coding schemes
other than CS1 to CS4.
Cause The BSC considers coding schemes other than CS1 to CS4 incorrect and
discards the uplink data blocks that use these coding schemes in an uplink
GPRS TBF. The counter N3101 is not incremented by one for this TBF due
to a software defect.
Severity Minor
Solution The software defect is rectified to ensure that the counter N3101 is
incremented by one when the BSC considers the coding scheme incorrect
and discards the related uplink data blocks. In this way, the counter N3101
can increase to a specified value so that the BSC can release uplink TBFs in
time.
46. Solving the problem that the measured value of Number of Initially Configured Channels
(SDCCH) is incorrect
Description The measured value of Number of Initially Configured Channels (SDCCH)
is incorrect.
Cause According to 3GPP specifications, BCCH+CBCH includes three SDCCHs,
SDCCH+CBCH includes seven SDCCHs, and Combined BCCH includes
four SDCCHs. However, when measuring the counter Number of Initially
Configured Channels (SDCCH), the BSC considers zero SDCCH in
BCCH+CBCH, eight SDCCHs in SDCCH+CBCH, and zero SDCCH in
Combined BCCH.
Impact The measured value of Number of Initially Configured Channels (SDCCH)
is incorrect.
Severity Minor
Solution The BSC measures the value of Number of Initially Configured Channels
(SDCCH) according to 3GPP specifications.
47. Solving the problem that Ater resources are insufficient if more than 7168 timeslots are
configured on a POUc board with a logical function type of TDM

Description In BM/TC separated mode, if a POUc board with a logical function type of
TDM is configured as the Ater interface board, the assignment success rate
decreases when more than 7168 timeslots for 16-kbit/s services are
configured on the board.
Cause A POUc board, when configured as an Ater interface board with a logical
function type of TDM, supports a maximum of 7168 timeslots for 16-kbit/s
services. The BSC, however, ignores this limitation and allows the
configuration of more than 7168 timeslots.
Impact The assignment success rate decreases.
Severity Warning
Solution The BSC now provides a check mechanism so that the configuration fails if
more than 7168 timeslots for 16-kbit/s services over the Ater interface are
configured on a POUc board.
48. Solving the problem that the ALM-21801 GSM Cell out of Service alarm is not reported
when it should have been
Description The radio signaling link (RSL) corresponding to the BCCH carrier is faulty,
but the ALM-21801 GSM Cell out of Service alarm is not reported.
Cause When the RSL corresponding to the BCCH carrier is faulty, the data link
layer still receives data from the service layer to minimize the impact of
intermittent disconnection on services. As a result, the RSL may be faulty
and congested. The data link layer reports only the congested state to the
service layer, which then considers the data link layer as normal and does not
report the preceding alarm.
Impact The preceding alarm is not reported when the RSL corresponding to the
BCCH carrier is faulty.
Severity Minor
Solution The fault reporting mechanism of the data link layer is optimized so that the
data link layer notifies the service layer of the fault when the link is faulty
and congested.
49. Solving the problem that an MS becomes muted during an intra-BSC handover

Description An MS becomes muted during an intra-BSC handover if the signal quality is

poor on the Um interface.
Cause After sending a Handover Command message to the MS over the original
TCH, the BSC receives an Error Indication, Connection Failure, or Release
Indication message over the original TCH due to the poor signal quality on
the Um interface. The BSC then instructs the BTS to deactivate the SACCH
that is mapped onto the same physical channel as the original TCH. After the
SACCH is deactivated, the BSC fails to receive any measurement reports
over the original TCH. After the timer waiting for a Handover Complete
message has expired, the BSC mistakenly assumes that the MS still uses the
original TCH, and therefore releases the new TCH.
Impact The MS becomes muted.
Severity Minor
Solution Now, the BSC does not instruct the BTS to deactivate the SACCH that is
mapped onto the same physical channel as the original TCH after receiving
an Error Indication, Connection Failure, or Release Indication message over
the original TCH.
This solution may increase the counters Call Drops in TCH Handovers (Traffic
Channel) and Call Drop Rate on TCH per cell(including Handover) and decrease the
counter Handover Success Rate if the signal quality is poor on the Um interface.
However, the call drops caused by this solution do not affect user experience because
the calls are muted.
50. Solving the problem that the counters Total Bytes of Uplink EGPRS Users LLC PDUs
and Total Bytes of Uplink GPRS Users LLC PDUs are incorrectly measured

Description The counters Total Bytes of Uplink EGPRS Users LLC PDUs and Total
Bytes of Uplink GPRS Users LLC PDUs are incorrectly measured.
Cause Upon receiving an uplink data block from an MS, the BSC determines
whether the MS supports EGPRS based on the MS context. If the MS
supports EGPRS, the counter Total Bytes of Uplink EGPRS Users LLC
PDUs is incremented by one. If the MS does not support EGPRS, the
counter Total Bytes of Uplink GPRS Users LLC PDUs is incremented by
one.
However, when the BSC receives the first uplink data block from an MS
supporting EGPRS, the BSC fails to determine whether the MS supports
EGPRS because the MS context has not been set up. As a result, the counter
Total Bytes of Uplink EGPRS Users LLC PDUs is mistakenly measured as
the counter Total Bytes of Uplink GPRS Users LLC PDUs.
Impact The counters Total Bytes of Uplink GPRS Users LLC PDUs and Throughput
of Uplink GPRS Users LLC PDU are greater than actual.
The counters Total Bytes of Uplink EGPRS Users LLC PDUs and
Throughput of Uplink EGPRS Users LLC PDU are less than actual.
Severity Minor
Solution The BSC sets up the MS context and records the MS EGPRS capability
before receiving the first uplink data block. If the MS supports EGPRS, the
counter Total Bytes of Uplink EGPRS Users LLC PDUs is incremented by
one.
51. Solving the problem that the CS assignment success rate decreases
Description Some CS calls cannot obtain inter-subrack timeslots in TDM mode.
Cause The BSC does not preferentially distribute a PS cell to the digital signal
processor (DSP) that is located in the same subrack as the Abis interface
board in the BTS serving the cell. As a result, PS services occupy too many
inter-subrack timeslots in TDM mode.
Impact The CS assignment success rate decreases.
Severity Warning
Solution The BSC preferentially distributes a PS cell to the DSP in the same subrack
as the Abis interface board in the BTS serving the cell. In this way, CS calls
can occupy certain inter-subrack timeslots.
With this solution, cell distribution will change when a BSC is upgraded.

52. Solving the problem that radio resource usage does not increase after TCH Pre-
Conversion into SDCCH Switch is turned on

Description The radio resource usage does not increase after TCH Pre-Conversion
into SDCCH Switch is set to ON.
Cause The BSC does not consider the TCHs that can be converted into SDCCHs
in the cell and therefore the collected value of Number of Initially
Configured Channels (TCH) is greater than the actual number.
Radio resource usage is calculated by using the following formula:
Radio resource usage = (K3014 + AR9311)/(CR300B + CR3002 +
CR3001) x K
Where,
K3014 : Traffic Volume on TCH
AR9311: Average Number of Occupied PDCHs
CR300B: Number of Initially Configured Channels (TCH)
CR3002: Number of Initially Configured Channels (Dynamic PDCH)
CR3001: Number of Initially Configured Channels (Static PDCH)
K varies according to the actual condition
Impact The effect of TCH Pre-Conversion into SDCCH Switch is not correctly
reflected in the radio resource usage.
Severity Minor
Solution If TCH Pre-Conversion into SDCCH Switch is set to ON and the value
of Number of TCHs Pre-Converted into SDCCHs is greater than 0, the
BSC records the number of TCHs that can be or have been converted into
SDCCHs in the cell as A.
The BSC measures the value of Number of Initially Configured Channels
(TCHF) and Number of Initially Configured Channels (TCHH) as follows:
 If the collected value of Number of Initially Configured Channels
(TCHF) is greater than or equal to A:
Number of Initially Configured Channels (TCHF) = collected value of
Number of Initially Configured Channels (TCHF) – A
(TCHH) plus the collected value of Number of Initially Configured
Channels (TCHF) is greater than or equal to A:
Number of Initially Configured Channels (TCHH) = collected value of
Number of Initially Configured Channels (TCHH) – (A – collected value of
Number of Initially Configured Channels (TCHF))
(TCHH) plus the collected value of Number of Initially Configured
Channels (TCHF) is smaller than A:
Number of Initially Configured Channels (TCHF) = 0
Number of Initially Configured Channels (TCHH) = 0
In this manner, the value of Number of Initially Configured Channels
(SDCCH) increases and the value of Number of Initially Configured
Channels (TCH) decreases.

53. Solving the problem that the TFO function fails to be enabled
Description The Tandem Free Operation (TFO) function fails to be enabled when the
following conditions are met:
1. The Time Division Multiplexing (TDM) technique is used on the A
interface.
2. Huawei BSC6900 is interconnected with devices provided by other
vendors.
3. The adaptive multirate (AMR) codec version applied to Huawei BSC6900
is FR_AMR, and the AMR codec version applied to the interconnected
devices is HR_AMR.
Cause As indicated in 3GPP TS 28062, the frame structure must be
AMR_TFO_8+8k to enable TFO in the preceding scenario.
Huawei BSC6900, however, does not use this frame structure. As a result, the
TFO function fails to be enabled.
Impact The TFO function fails to be enabled.
Severity Minor
Solution Huawei BSC6900 uses the frame structure AMR_TFO_8+8k.

To prevent compatibility issues, all interconnected Huawei BSC6900s must
be upgraded to BSC6900 V900R013C00SPC300 or later.
54. Solving the problem that four parameters in the SET GCELLHOFITPEN command have
the same names as four parameters in the SET GCELLCHMGAD command

Description Four parameters in the SET GCELLHOFITPEN command have the same
names as four parameters in the SET GCELLCHMGAD command.
Cause Adequate care was not taken to ensure that each parameter in the SET
GCELLCHMGAD command has a unique name.
Impact BSC functions are not affected. However, the user experience is affected.
Severity Major
Solution Four parameters in the SET GCELLCHMGAD command have been

renamed as follows:
Filter Length for SDCCH Level is changed into Filter Len of SDCCH Level
for Interf Ind.
Filter Length for SDCCH Qual. is changed into Filter Len of SDCCH Qual
for Interf Ind.
Filter Length for TCH Level is changed into Filter Len of TCH Level for
Interf Ind.
Filter Length for TCH Qual. is changed into Filter Len of TCH Qual for
Interf Ind.
55. Solving the problem that a handover fails if an MS sends a new measurement report to
the BSC when handover attempts are still initiated to original candidate cells

Description During intra-BSC handovers, an MS sends a new measurement report

to the BSC when handover attempts are still initiated to original
candidate cells. In the report, candidate cells are no longer the original
candidate cells. As a result, handing over the MS to newly specified
candidate cells fails.
Cause During intra-BSC handovers, the BSC can select a maximum of three
candidate cells to hand over an MS to one of the three cells when the
handover decision is positive. If the first handover attempt fails
because of channel assignment failure, the BSC will initiate a handover
to another candidate cell. Before the MS is allowed to be handed over
to this candidate cell, the MS has sent a new measurement report
including a new candidate cell list to the BSC. In this case, the MS can
no longer be handed over to the rest two cells. However, the BSC keeps
attempting to hand over the MS to the two cells. As a result, handing
over the MS to newly specified candidate cells fails.
Impact During intra-BSC handovers, an MS sends a new measurement report
to the BSC when handover attempts are still initiated to original
candidate cells. In the report, candidate cells are no longer the original
candidate cells. As a result, handing over the MS to newly specified
candidate cells fails.
Severity Major
Solution A parameter has been added to the BSC to limit the number of
neighboring cells after a positive handover decision is made.
7.3 Known Issues

None.

HUAWEI BSC6900 GSM
V900R014C00SPC500 Release Notes Related DocumentationRelated Documentation
8 Related Documentation
8.1 V900R014C00 Documentation

Solution Product Documentation Website
Version Version Version
GBSS14.0 BSC6900V900R (For Customer)BSC6900 Documentation>

014C00SPC500 GSM Product Wireless>SingleRAN>
Documentation MBSC>BSC6900
(V900R014C00_01) GSM>V900R014C00
(HDX)-EN
GBSS13.0 BSC6900V900R (For Customer)BSC6900 http://support.huawei.co
013C00SPC500 GSM Product m/support/pages/kbcent
Documentation er/view/product.do?
(V900R013C00_02) actionFlag=detailProduc
(HDX)-EN tSimple&web_doc_id=S
E0000519720&doc_typ
e=ProductManual
8.2 Updates to Related Documentation

For details about documentation updates, see (For Customer)BSC6900 GSM Product
Documentation (V900R014C00_01) (HDX)-EN.
8.2.1 Changes from V900R014C00SPC300 to V900R014C00SPC500

Update Update Reason Documentation Version
The GBSS This document provides methods (For Customer)BSC6900 GSM

Troubleshooting for troubleshooting the GBSS. Product Documentation
Guide has been (V900R014C00_01)-EN
added.

HUAWEI BSC6900 GSM

None.

The BSC6900 This document describes BSC6900 (For Customer)BSC6900 GSM

Communication product communication matrix. Product Documentation
Matrix has been (V900R014C00_ Draft A)-EN
added.

The BSC6900 This document describes BSC6900 (For Customer)BSC6900 GSM

Communication product communication matrix. Product Documentation
Matrix has been (V900R014C00_ Draft A)-EN
added.
The BSC6900 Spare parts, part numbers, and (For Customer)BSC6900 GSM
GSM Spare Parts pictures of the product are Product Documentation
Catalog has been provided for easy identification. (V900R014C00_ Draft A)-EN
added.
8.3 Obtaining Documentation

8.3.1 Support Website
You can view or download related documentation from http://support.huawei.com.
You must apply for permission to obtain documentation from the website. If you are using
http://support.huawei.com for the first time, first register with the website.
Registering with the Website

To register with http://support.huawei.com, perform the following steps:
Step 1 Access http://support.huawei.com.
Step 2 Click Register, and follow the instructions to complete the registration process.
If your registration is successful, you will be informed of your user name and password within
two or three working days.

HUAWEI BSC6900 GSM
----End
Viewing or Downloading Documentation

To view or download documentation from http://support.huawei.com, perform the following
steps:
Step 1 Access http://support.huawei.com.
Step 2 Click Log In. In the dialog box that is displayed, enter the user name, password, and
verification code and click Login.
Step 3 After a successful login, choose Wireless > SingleRAN > MBSC>Product Documentation in
the Product catalog pane.
The product documentation page is displayed.
Step 4 Click the view or download icon on the right of the documentation package name to view or
download the documentation.
 You can also enter the product name in the Product Name text box on the home page of
http://support.huawei.com to search for documents specific to a product.
 If the file name extension of a documentation package is .hdx, use HedEx Lite to view the
documents. You can obtain the software from Huawei customer service engineers.
----End

HUAWEI BSC6900 GSM
V900R014C00SPC500 Release Notes Acronyms and AbbreviationsAcronyms and Abbreviations
A Acronyms and Abbreviations
A
AAL2 ATM Adaptation Layer type 2
ABIS ABIS Interface
ABISPC ABIS interface Port Control
AICP A Interface Common Processing
APC A interface Port Control
ASUBPC ASUB interface Port Control
ATM Asynchronous Transfer Mode
B
BER Bit Error Rate
BHCA Busy Hour Call Attempt
BOOTP Bootstrap Protocol
BCC Bearer Channel resource Control
BIOS Basic Input Output System
BSC Base Station Controller
BSSGP BSSGP instance
BTS Base Transceiver Station
BTSM BTS Management
C
CBC Cell Broadcast Center

HUAWEI BSC6900 GSM
CCP Communication Control Port

CDT Call Data Tracing
CoRRM Connection Orient Radio Resource Management
CPLD Complex Programmable Logical Device
CRC Concentrate Routing Board
E
EDGE Enhanced Data rates for GSM Evolution
F
FE Fast Ethernet
FP Frame Protocol
FR Frame Relay
G
GBPC Gb interface Port Control
GCC Group Call Control
GCP GSM Control Processor
GE Gigabit Ethernet
GERAN GSM EDGE Radio Access Network
GPRS General Packet Radio Service
GPS Global Positioning System
GSM Global System for Mobile Communications
GTP-U GPRS Tunneling Protocol for User Plane
H
HARQ Hybrid Automatic Repeat Request
HDLC High level Data Link Control
HSDPA High Speed Downlink Packet Access
HS-DSCH High Speed Downlink Shared Channel
HSUPA High Speed Uplink Packet Access

HUAWEI BSC6900 GSM
I
IDC Instance Distribution Control
IGWLC Inner Gateway Link Control
IMA Inverse Multiplexing on ATM
IP Internet Protocol
IPoA Internet Protocols over ATM
L
LAN Local Area Network
LAPD Link Access Protocol on D channel
LBIP Lb Interface Processing
LMT Local Maintenance Terminal
LRM Local Resource Management
M
MAC Medium Access Control
MBMS Multimedia Broadcast and Multicast Service
MIMO Multi Input Multi Output
MOCN Multiple Operator Core Network
MSIC MS Instance Control
MSIP MS Instance Process
MSP Multiplex Section Protection
MTLS Mapping and Transfer between LAPD entity and
Service entity
MTP Message Transfer Part
MTSS Mapping and Transfer between SCCP entity and
Service entity
N
NS NS instance
NSEP NS Entity Processing

HUAWEI BSC6900 GSM
PARC Platform of Advanced Radio Controller

PBIP Pb Interface Processing
PBLC PB Link Control
PBPC PB interface Port Control
PCU Packet Control Unit
PDCP Packet Data Convergence Protocol
PRR Packet domain Radio Resource control
PGC Paging Control
PPP Point-to-Point Protocol
PSLC PS Link Control
PVC Permanent Virtual Channel
R
RBSC Radio Base Station Controller
RBTS Radio Base Station System
RDLC Radio Link Control
RESC Radio Embed-resources Set Control
RGCP GSM Control Processor with Resource Management
RLC RLC instance
RLCC RLC resource Control
RRM Radio Resource Management
Q
QoS Quality of Service
S
SAAL Signaling ATM Adaptation Layer
SABP Service Area Broadcast Protocol
SCCP Signaling Connection Control Part
SCP Service Control Plane
SCTP Stream Control Transmission Protocol
SIGPC Signal Port ts resource Control

HUAWEI BSC6900 GSM
SPCC Semi-Permanent Connection Control

SRAP Service Resource Access Plane
SRCP Service Resource Control Plane
SRP Service Resource Plane
T
TC TC instance
TCC TC resource Control
TDM Time Division Multiplexing
TDMC TDM resource Control
TRAU TRAU instance
TRX Transceiver
U
UE User Equipment
UMTS Universal Mobile Telecommunications System
UNI User-Network Interface
UP User Plane
V
VLAN Virtual Local Area Network
VoIP Voice over IP
W
WCDMA Wideband Code Division Multiple Access


BSC GSM

Transféré par

Informations du document

Titre original

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

BSC GSM

Transféré par

Droits d'auteur :

Formats disponibles

HUAWEI BSC6900 GSM

HUAWEI TECHNOLOGIES CO., LTD.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Issue 01 (2012-04-26) Huawei Proprietary and Confidential i

About This Document

Reviewed by Yao Jianhui,Xu Jiajia, Dang Date 2012-04-08

Approved by Zou Yu Date 2012-04-26

01 2012-04-26 Zhao Gang,Chen Jie,Wei Qi First issue

Issue 01 (2012-04-26) Huawei Proprietary and Confidential ii

5 Changes from V900R014C00SPC200 to V900R014C00SPC300...........................................78

Issue 01 (2012-04-26) Huawei Proprietary and Confidential iii

5.1.7 Counter Updates...................................................................................................................................103

6 Changes from V900R013C00SPC500 to V900R014C00SPC200.........................................112

7 Changes from V900R012C01SPC500 to V900R014C00SPC200.........................................299

Issue 01 (2012-04-26) Huawei Proprietary and Confidential iv

1.1 Product Version

Product Model HUAWEI BSC6900/HUAWEI BSC6000

Product Version V900R014C00SPC500

1.2 Software Versions

1.3 Hardware Versions

SCUa SCUa WP11PSCUa Ver.D 258 Yes

Issue 01 (2012-04-26) Huawei Proprietary and Confidential 1

Physical Logical Board Bar Code PCB BIOS/Extended BootROM Upgrade

GCUa GCUa WP11GCUa Ver.B 224 Yes

Issue 01 (2012-04-26) Huawei Proprietary and Confidential 2

Physical Logical Board Bar Code PCB BIOS/Extended BootROM Upgrade

EIUa EIUa/Abis WP11EIUa Ver.A 255 Yes

Issue 01 (2012-04-26) Huawei Proprietary and Confidential 3

Physical Logical Board Bar Code PCB BIOS/Extended BootROM Upgrade

GOUd GOUd/IP WP11GOUd Ver.B 120 Yes

1.4 Related Product Versions

CBC CBC CBC V300R001B02D001

Issue 01 (2012-04-26) Huawei Proprietary and Confidential 4

Product Name Product Model Product Version Remarks

Issue 01 (2012-04-26) Huawei Proprietary and Confidential 5

Product Name Product Model Product Version Remarks

BTS BTS3900 series BTS3000V100R014C00SPC006 or BSS14.0

Issue 01 (2012-04-26) Huawei Proprietary and Confidential 6

1.5 OS and Database Versions

Windows 2003 Server mysql 5.0 Only the installation can be

Patch package: To download the patch package,

1.6 Virus Scan Result

Virus Database 6603

Scanning Date 2012-5-2

Issue 01 (2012-04-26) Huawei Proprietary and Confidential 7

Scanning Result Normal

Issue 01 (2012-04-26) Huawei Proprietary and Confidential 8

2.1 Compatibility with Earlier Product Versions

2.2 Compatibility with Earlier Board Software Versions

In the following tables, Y represents compatible, and N represents incompatible.

Table 1.1 Compatibility with earlier board versions

Issue 01 (2012-04-26) Huawei Proprietary and Confidential 9

Board Name BSC6000V900R008C12 BSC6000V900R008C01

Table 1.2 Compatibility with earlier board versions (BSC6900)

Issue 01 (2012-04-26) Huawei Proprietary and Confidential 10

Board Name BSC6900V900R BSC6900V900R BSC6900V900

Issue 01 (2012-04-26) Huawei Proprietary and Confidential 11

Table 1.3 Notes and cautions for using BSC6900 V900R014C00SPC500

Issue 01 (2012-04-26) Huawei Proprietary and Confidential 12

4 Changes from V900R014C00SPC300 to

4.1 What's New

Issue 01 (2012-04-26) Huawei Proprietary and Confidential 13