Bsc6910 Gsm v100r016c00spc620 Release Notes

BSC6910 GSM
V100R016C00SPC620
Release Notes
Issue 01
Date 2014-09-12
HUAWEI TECHNOLOGIES CO., LTD.

Copyright Huawei Technologies Co., Ltd. 2014. 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
Huawei Proprietary and Confidential

Issue 01 (2014-09-12) Copyright Huawei i
Technologies Co., Ltd.
BSC6910 GSM
Release Notes About This Document
About This Document
Author
Prepared by Wang Erli, Xu Date 2014-08-25
Qigang, Hou Wei, Li
Jian, Zhu Jiangbo
Reviewed by Liu Yong, Liu Qi, Xu Date 2014-09-01
Yousong, Wang Jun,
Wang Qingyan, Chen
Yiwen, Zhang Peng,
Wu Xiuliang
Tested by Zheng Hang Date 2014-09-08
Approved by Wang Dong Date 2014-09-12
Overview
This document provides only the changes between adjacent patch versions for
BSC6910V100R016C00SPC600.
If a BSC earlier than BSC6910V100R016C00SPC600 on the live network is upgraded to the
current patch version, obtain the release documentation matching
BSC6910V100R016C00SPC600 and use the obtained release documentation together with
this document.
The "Known Issues" chapter in each version describes the status of all known issues. If a
known issue has been resolved, the progress of this known issue will be displayed in the
"Resolved Issues" chapter in a later version. Users can check the progress of a known issue
according to its trouble ticket number.
Change History
Issu Date Author Description
e
01 2014-09-12 Wang Erli, Xu This is the first commercial release.
Issue 01 (2014-09-12) Huawei Proprietary and Confidential ii

Copyright Huawei
BSC6910 GSM
Issu Date Author Description

e
Qigang, Hou Wei,

Li Jian, Liu Lei
Introduction
This document is intended for system engineers. It provides the following information:
Version Requirements
This chapter lists all information about this product version, for example, software,
hardware, operating system (OS), database, documentation, and any other required
products. This chapter also provides important notes and virus scan results for this
product version.
Version Compatibility
This chapter describes the compatibility between this product version and earlier
versions, including their software and hardware versions.
Change Description
This chapter describes the changes in the current version compared with the previous
version, including the change summary, feature changes, resolved issues, and known
issues. Where,
The feature summary includes information about capacity and performance,
hardware, features, resolved issues, operation and maintenance, and related
documentation, as described in Table 1 Section description.
Table 1 Section description

Section Description
Capacity and Describes the possible impact of a specific product version on system
performance capacity and network performance.
Hardware Describes any hardware addition and modification in a specific product
version. The hardware end of marketing (EOM) and end of service
(EOS) information does not map onto the software version. For details,
see the corresponding PCN.
Features Provides a summary of all feature changes in a specific product
version. Users can select desired features by "Impact on Capacity and
Performance", "Hardware Dependency", "Parameter Control?", or
"Parameter Control?".
Resolved issues Provides a summary of all resolved issues in a specific product version.
Users can select desired resolved issues by "Solution Impact",
"Parameter Control?", or "Post-Upgrade Value".
Operation and Describes the changes to configuration management, performance
maintenance management, fault management, license management, and their
management mechanisms and rules in a specific product version.
Related Describes the changes to related documentation of a specific product
documentation version.
Issue 01 (2014-09-12) Huawei Proprietary and Confidential iii

Copyright Huawei
BSC6910 GSM
Figure 1 Relationships among sections in Change Summary shows the relationships

among the preceding sections.
Figure 1 Relationships among sections in Change Summary
Feature Changes: details feature changes.

Resolved Issues: details resolved issues by severity.
Known Issues: details known issues in this product version by severity.
Operation and Maintenance Changes
This chapter describes changes to MML commands, parameters, alarms, events,
counters, and licenses.
Appendix
The appendixes describe how to obtain related documentation and provide acronyms and
abbreviations involved.
Issue 01 (2014-09-12) Huawei Proprietary and Confidential iv

Copyright Huawei
BSC6910 GSM
Release Notes Contents
Contents
About This Document.......................................................................ii

1 Version Requirements...................................................................1
1.1 Product Version..............................................................................................................................................................1
1.2 Software Versions...........................................................................................................................................................1
1.3 Hardware Versions..........................................................................................................................................................1
1.4 Related Product Versions................................................................................................................................................2
1.5 OS and Database Versions..............................................................................................................................................4
1.6 Related Documentation..................................................................................................................................................4
1.7 Virus Scan Result............................................................................................................................................................5
1.8 Important Notes..............................................................................................................................................................6
2 Version Compatibility....................................................................7
2.1 Software Version Compatibility.....................................................................................................................................7
2.2 Hardware Version Compatibility....................................................................................................................................7
3 Changes from V100R016C00SPH609 to V100R016C00SPC620..........9

3.1 Change Summary...........................................................................................................................................................9
3.1.1 Capacity and Performance.........................................................................................................................................10
3.1.2 Hardware...................................................................................................................................................................10
3.1.3 Features......................................................................................................................................................................11
3.1.4 Resolved Issues..........................................................................................................................................................11
3.1.5 Operation and Maintenance.......................................................................................................................................11
3.1.5.1 Configuration Management....................................................................................................................................11
3.1.5.2 Performance Management......................................................................................................................................12
3.1.5.3 Fault Management..................................................................................................................................................12
3.1.5.4 License Management..............................................................................................................................................12
3.1.6 Related Documentation.............................................................................................................................................12
3.2 Feature Changes...........................................................................................................................................................12
3.2.1 New Features.............................................................................................................................................................12
3.2.2 Modified Features......................................................................................................................................................12
3.2.2.1 TCH-related Counter Optimization for Users with Specific Priorities..................................................................12
3.2.2.2 CCCH Flow Control Parameter Optimization.......................................................................................................15
3.2.2.3 Support for Subrack DIP Switch Status Check......................................................................................................19
Issue 01 (2014-09-12) Huawei Proprietary and Confidential v

Copyright Huawei
BSC6910 GSM
3.2.2.4 Upgrade Tool Reliability Optimization..................................................................................................................21

3.2.3 Deleted Features........................................................................................................................................................23
3.3 Resolved Issues............................................................................................................................................................23
3.3.1 Critical.......................................................................................................................................................................23
3.3.2 Major.........................................................................................................................................................................24
3.3.2.1 The measured call setup duration is incorrect after an MS is handed over to another BSC and makes a call to a
third MS..............................................................................................................................................................................24
3.3.2.2 Incoming RNC-to-BSC handovers are displayed as incoming inter-BSC handovers on the Nastar because the
source cell ID has changed.................................................................................................................................................24
3.3.2.3 DTM congestion occurs because the BSC does not dynamically convert PDCHs into TCHs in a timely manner
in the DTM procedure........................................................................................................................................................25
3.3.2.4 The BSC cannot allocate TCH channels on BCCH-incompatible frequency bands to MSs during immediate
assignment when the BSC supports TCHs that function as signaling channels.................................................................27
3.3.2.5 The value of the K3043 counter is greater than 100% when the BSC processes buffered downlink DTM service
requests after a DTM assignment fails...............................................................................................................................28
3.3.2.6 PS services cannot be performed when the BCCH TRX participates in frequency hopping and the MA group
includes frequencies on P and E bands...............................................................................................................................28
3.3.3 Minor.........................................................................................................................................................................30
3.3.3.1 The loading speed of the TDM BTS software version is always 64 kbit/s............................................................30
3.3.3.2 The RST BSC command execution times out when the active and standby SCU boards are unavailable............30
3.3.3.3 The causes for signaling link interruption or transmission faults cannot be quickly identified.............................31
3.3.3.4 The value of the Hosted domain queried in the DSP OPC command output is incorrect......................................32
3.3.3.5 The DSP GPS command output may be incorrect..................................................................................................32
3.3.3.6 A BSC6910 fails to be upgraded when adjacent nodes are bound to IP logical ports of active and standby boards
in odd-numbered slots........................................................................................................................................................33
3.3.4 Suggestion.................................................................................................................................................................34
3.3.4.1 The BSC whose homing status is "Not homed" cannot correctly detect transmission connectivity over the A
interface..............................................................................................................................................................................34
3.3.4.2 Call access fails because the cell PA status on the BSC side is inconsistent with the TRX PA status on the
eGBTS side.........................................................................................................................................................................34
3.3.4.3 Users have difficulty querying configurable cell parameters when adding a cell template...................................35
3.3.4.4 The SDCCH and BCCH cannot be configured on the same timeslot....................................................................36
3.3.4.5 MSs are inaccurately located by using the Gb-based Location Service (Cell ID+TA) function............................36
3.3.4.6 The BSC incorrectly measures counters related to abnormal downlink TBF release............................................37
3.3.4.7 The BSC mistakenly terminates the rerouting procedure in a cell enabled with the MOCN Shared Cell feature.38
3.3.4.8 The number of activated PDCHs is unbalanced among GUPPSs when PS traffic volumes are unbalanced among
cells.....................................................................................................................................................................................40
3.3.4.9 Users are not prompted with a message about the parameter relationship when setting the AMR ACS[F] or AMR
ACS[H] parameter..............................................................................................................................................................42
3.3.4.10 The alarm location information in some transmission alarms is insufficient.......................................................42
3.3.4.11 The failure cause cannot be quickly identified when an IP continuity check fails...............................................43
3.3.4.12 No information is available for locating the fault when a chip of the interface processing board fails to be
initialized............................................................................................................................................................................44
3.4 Known Issues................................................................................................................................................................45
3.4.1 Critical.......................................................................................................................................................................45
Issue 01 (2014-09-12) Huawei Proprietary and Confidential vi

Copyright Huawei
BSC6910 GSM
3.4.2 Major.........................................................................................................................................................................45
3.4.3 Minor.........................................................................................................................................................................45
3.4.3.1 When the full MML scripts are exported and delivered on the CME, the SET BTSPORTTS command fails to be
executed..............................................................................................................................................................................45
3.4.4 Suggestion.................................................................................................................................................................45
4 Changes from V100R016C00SPH608 to V100R016C00SPH609........46

4.1 Change Summary.........................................................................................................................................................46
4.1.2 Hardware...................................................................................................................................................................47
4.1.3 Features......................................................................................................................................................................47
4.1.4 Resolved Issues.........................................................................................................................................................47
4.2 Feature Changes...........................................................................................................................................................48
4.2.1 New Features.............................................................................................................................................................48
4.3 Resolved Issues............................................................................................................................................................49
4.3.1 Critical.......................................................................................................................................................................49
4.3.2 Major.........................................................................................................................................................................49
4.3.2.1 The WebLMT displays a message "Internal error" if the file name of an uploaded file contains Chinese
characters in batch configuration........................................................................................................................................49
4.3.2.2 Multicast configuration fails after an SCU board has been running for an excessively long period of time.........49
4.3.3 Minor.........................................................................................................................................................................50
4.3.4 Suggestion.................................................................................................................................................................50
4.4 Known Issues................................................................................................................................................................50
4.4.1 Critical.......................................................................................................................................................................50
4.4.2 Major.........................................................................................................................................................................50
4.4.3 Minor.........................................................................................................................................................................51
executed..............................................................................................................................................................................51
4.4.4 Suggestion.................................................................................................................................................................51

5.1 Change Summar...........................................................................................................................................................52
5.1.2 Hardware...................................................................................................................................................................53
5.1.3 Features......................................................................................................................................................................54
5.1.4 Resolved Issues.........................................................................................................................................................54
Issue 01 (2014-09-12) Huawei Proprietary and Confidential vii

Copyright Huawei
BSC6910 GSM

5.2 Feature Changes...........................................................................................................................................................54
5.2.1 New Features.............................................................................................................................................................54
5.3 Resolved Issues............................................................................................................................................................55
5.3.1 Critical.......................................................................................................................................................................55
5.3.2 Major.........................................................................................................................................................................55
5.3.3 Minor.........................................................................................................................................................................55
5.3.4 Suggestion.................................................................................................................................................................55
5.4 Known Issues................................................................................................................................................................55
5.4.1 Critical.......................................................................................................................................................................55
5.4.2 Major.........................................................................................................................................................................55
5.4.3 Minor.........................................................................................................................................................................55
executed..............................................................................................................................................................................55
5.4.4 Suggestion.................................................................................................................................................................56

6.1 Change Summary.........................................................................................................................................................57
6.1.2 Hardware...................................................................................................................................................................58
6.1.3 Features......................................................................................................................................................................59
6.1.4 Resolved Issues.........................................................................................................................................................59
6.2 Feature Changes...........................................................................................................................................................60
6.2.1 New Features.............................................................................................................................................................60
6.2.2.1 Support for Changing the RXU Board Type on GSM Networks...........................................................................60
6.2.2.2 Added the G_NIC Command Group for Encapsulating All Commands for the NIC Function.............................61
6.2.2.3 Enhanced Anti-Attack Protection for Fragmented Packets Received by the Interface Board...............................63
6.3 Resolved Issues............................................................................................................................................................64
Issue 01 (2014-09-12) Huawei Proprietary and Confidential viii

Copyright Huawei
BSC6910 GSM
6.3.1 Critical.......................................................................................................................................................................64
6.3.2 Major.........................................................................................................................................................................65
6.3.2.1 MO short messages are prohibited when the Short Message Downlink Disabled parameter is set to YES(Yes)..65
6.3.2.2 A GSM/UMTS MS in GSM-only mode fast reselects to a UMTS FDD cell after releasing a call.......................65
6.3.2.3 The measured values of counters under the "Incoming Inter-RAT Inter-Cell Handover Measurement per Cell"
and "SRVCC Handover Measurement per Cell" measurement units are incorrect............................................................66
6.3.2.4 TCHH allocation fails when TCH rate adjustment is not allowed and the Half Rate Speech (per TRX) and AMR
HR (per TRX) license control items do not coexist...........................................................................................................67
6.3.3 Minor.........................................................................................................................................................................68
6.3.3.1 Frequency scanning results cannot be correctly displayed if the NE reports more than 2500 items.....................68
6.3.3.2 Synchronization between the controller and the U2000/CME has not been performed for a long time because
configuration synchronization times out for several times.................................................................................................68
6.3.3.3 The POUc/FG2d/FG2c/GOUd/GOUc board incorrectly reports ALM-20280 Board Temperature Abnormal.....70
6.3.3.4 The DSP GPS command output is incorrect...........................................................................................................70
6.3.4 Suggestion.................................................................................................................................................................71
6.3.4.1 The permissions of local users are lost when the BSC database is abnormal........................................................71
6.3.4.2 Instantaneous traffic is too heavy after the FTP upload and download performance is optimized........................71
6.3.4.3 The value of a single bit in the FPGA of the FG2d/GOUd/POUc/FG2c/GOUc board is changed and the FPGA
cannot recover through self-healing...................................................................................................................................72
6.4 Known Issues................................................................................................................................................................73
6.4.1 Critical.......................................................................................................................................................................73
6.4.2 Major.........................................................................................................................................................................73
6.4.3 Minor.........................................................................................................................................................................73
executed..............................................................................................................................................................................73
6.4.4 Suggestion.................................................................................................................................................................74
7 Changes from V100R016C00SPC600 to V100R016C00SPH602........75

7.1 Change Summary.........................................................................................................................................................75
7.1.2 Hardware...................................................................................................................................................................76
7.1.3 Features......................................................................................................................................................................77
7.1.4 Resolved Issues.........................................................................................................................................................77
7.2 Feature Changes...........................................................................................................................................................78
7.2.1 New Features.............................................................................................................................................................78
7.2.2.1 Immediately Notifying the Peer End of the Receive Buffer Space Update...........................................................78
7.2.2.2 Upgrade Tool Supporting Risk Check Before an Upgrade....................................................................................79
Issue 01 (2014-09-12) Huawei Proprietary and Confidential ix

Copyright Huawei
BSC6910 GSM
7.2.2.3 Removed the FTP Text Box from the Batch Configuration Module......................................................................81
7.2.2.4 Support for Feature-based Information Display in the LST LICENSE Command Output....................................82
7.3 Resolved Issues............................................................................................................................................................84
7.3.1 Critical.......................................................................................................................................................................84
7.3.2 Major.........................................................................................................................................................................84
7.3.2.1 EVT-22921 Unconfigured Circuits over A Interface in the BSC is frequently reported........................................84
7.3.2.2 The number of abnormal TBF releases due to DTM establishments is incorrectly measured...............................84
7.3.2.3 The NSVL on the Gb interface becomes faulty due to intermittent transmission interruption over the Gb
interface after an SCU switchover......................................................................................................................................86
7.3.2.4 Cell information cannot be displayed in the cell performance monitoring interface.............................................86
7.3.2.5 Users cannot log in to the WebLMT on the PC where JRE of a specific version is installed................................87
7.3.2.6 The High-Risk Command List in MML Command Reference includes some non-risky commands....................87
7.3.3 Minor.........................................................................................................................................................................88
7.3.3.1 An adjacent node is successfully added by BTS name although the BTS does not exist......................................88
7.3.3.2 An isolated standby OMU cannot be de-isolated...................................................................................................89
7.3.3.3 The excessively long MML command outputs cannot be completely displayed on the U2000............................90
7.3.4 Suggestion.................................................................................................................................................................91
7.3.4.1 MSs are inaccurately located by using the BSS-based Location Service (Cell ID+TA) function.........................91
7.3.4.2 The alarm location information in ALM-21521, ALM-21503, and ALM-21553 is insufficient...........................91
7.3.4.3 The counter values measured during a patch upgrade are incorrect.......................................................................92
7.4 Known Issues................................................................................................................................................................93
7.4.1 Critical.......................................................................................................................................................................93
7.4.2 Major.........................................................................................................................................................................93
7.4.3 Minor.........................................................................................................................................................................93
executed..............................................................................................................................................................................93
7.4.4 Suggestion.................................................................................................................................................................93
8 Operation and Maintenance Changes...........................................94

8.1 MML Command Changes............................................................................................................................................94
8.2 Parameter Changes.......................................................................................................................................................94
8.3 Alarm Changes.............................................................................................................................................................94
8.4 Event Changes..............................................................................................................................................................94
8.5 Counter Changes..........................................................................................................................................................94
8.6 License Changes...........................................................................................................................................................95
8.7 Other Changes..............................................................................................................................................................95
A Obtaining Documentation............................................................96
B Acronyms and Abbreviations.......................................................97
Issue 01 (2014-09-12) Huawei Proprietary and Confidential x

Copyright Huawei
BSC6910 GSM
Release Notes 1 Version Requirements
1 Version Requirements
1.1 Product Version

Product Name HUAWEI BSC6910
Product Model HUAWEI BSC6910
Product V100R016C00SPC620
Version
1.2 Software Versions

Software Version
LMT V100R016C00SPC620
BAM V100R016C00SPC620
U2000 BSC6910 GSM:
Mediation iManagerOSS_BSC6910GSM_MATCH_ENG_V200R014C00SPC620
1.3 Hardware Versions

Physical Logical Bar Code PCB BIOS/Exten BootRO
Board Board Label Version ded BIOS M
Name Name Version Upgrade
Require
d
(Yes/No)
EOMUa EOMUa WP11EOMUa Ver.B 131 Yes
Issue 01 (2014-09-12) Huawei Proprietary and Confidential 1

Copyright Huawei
BSC6910 GSM
Physical Logical Bar Code PCB BIOS/Exten BootRO

Board Board Label Version ded BIOS M
Name Name Version Upgrade
Require
d
(Yes/No)
SCUb SCUb WP11SCUb Ver.C 133 Yes

Ver.D
GCUa GCUa WP11GCUa Ver.G 269 Yes
GCGa GCGa WP11GCGa Ver.G 269 Yes
EGPUa EGPUa WP11EGPUa Ver.A 143 Yes
EXOUa EXOUa/IP WP11EXOUa Ver.A 143 Yes
FG2c FG2c/IP WP11FG2c Ver.E 141 Yes
GOUc GOUc/IP WP11GOUc Ver.E 141 Yes
FG2d FG2d/IP WP11FG2d Ver.B 141 Yes
Ver.C
Ver.E
GOUd GOUd/IP WP11GOUd Ver.B 141 Yes
Ver.C
Ver.E
POUc POUc/TD WP11POUc Ver.B 141 Yes
M Ver.C
POUc/IP Ver.E
ESAUa ESAUa WP11ESAUa Ver.B 131 Yes
DPUf DPUf WP11PVCU Ver.B 133 Yes
ENIUa ENIUa WP11ENIUa Ver.A 143 Yes
EXPUa EXPUa WP11EXPUa Ver.A 143 Yes
GCUb GCUb WP11GCUb Ver.C 137 Yes
GCGb GCGb WP11GCGb Ver.C 137 Yes
GOUe GOUe/IP WP11GOUe Ver.A 106 Yes

Copyright Huawei
BSC6910 GSM
1.4 Related Product Versions

Product Product Product Version Remar
Name Model ks
U2000 U2000 iManager U2000 V200R014C00SPC200 or N/A

later
CME CME iManager U2000-CME V200R014C00 N/A
SPC200 or later
NASTAR NASTAR GENEX Nastar V600R014C00SPC100 or N/A
later
Note: Compared with versions earlier than
the BSC6910 V100R016C00, the
BSC6910 V100R016C00 has a changed
MR log structure.
PRS PRS iManager PRS V100R014C00 or later N/A
MBTS MBTS BTS3900V100R009C00SPC100 or later SRAN9.0
BTS BTS3900 series BTS3900V100R009C00SPC100 or later BSS16.0
(including the
BTS3900, BTS3000V100R015C00 or later BSS15.0
BTS3900A,
BTS3000V100R014C00SPC006 or later BSS14.0
BTS3900L, and
DBS3900) BTS3000V100R0013C00SPC003 or later BSS13.0
BTS3900 V100R009C00SPC058 or later BSS9.0
BTS3900 V100R009C00SPC081 or later
(required for Abis over IP)
Pico and micro BTS3000V600R013C00 or later BSS13.0
BTSs(BTS3900B/
BTS3900E) BTS3000V100R008C12SPC008 or later BSS8.1
BTS3012 series BTS3000V200R0013C00 or later BSS13.0

(including the
BTS3012, BTS3000V200R0012C00 or later BSS12.0
BTS3012AE,
BTS3012II,
BTS3006C, and BTS3000V100R008C11SPC026 or later BSS8.1
BTS3002E)
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

Copyright Huawei
BSC6910 GSM
Product Product Product Version Remar

Name Model ks
BTS2X series Not supported N/A

PCU PCU35 V300R008C03SPH008(recommended), N/A
compatible with all V300R008C03
versions
PCU6000 V300R008C11SPH003(recommended), N/A
compatible with V300R008C03 and later
ECO6910 ECO6910 ECO6910 V100R003C00SPC600 or later N/A
1.5 OS and Database Versions

OS/Database Patch Package Remarks
Version Version
RTOS V100R001C00 None The installation and upgrade

can be performed.
RTOS V200R003 RTOS The installation can be
V200R003C08SPC080 performed, and some
NOTE versions can be upgraded to
Patch packages of earlier the latest patch version. For
versions can still be used, but details about these versions,
you are advised to use the see section 1.1
RTOS patch package of the "Environment Requirements
latest version. for Upgrade" in BSC6910
Guide to Rtos Remote Patch
Upgrade.
NOTE
Contact Huawei engineers who
can obtain BSC6910 Guide to
Rtos Remote Patch Upgrade
by performing the following
operation:
1. Access
http://support.huawei.com.
2. After a successful login,
choose Software Center >
Version Software > Wireless
Product Line > SingleRAN >
MBSC.
3. Download BSC6910 Guide
to Rtos Remote Patch
Upgrade.
MySQL5.0.96 None Only the installation can be

performed.

Copyright Huawei
BSC6910 GSM
1.6 Related Documentation

Solutio Product Documentation Website
n Version
Version
GBSS16.0 BSC6910V100R (For Customer)BSC6910 Documentation >

016C00SPC620 GSM Product Wireless > SingleRAN >
Documentation MBSC> BSC6910 GSM
(V100R016C00_04)(HDX)- > V100R016C00
EN
(For Customer)GBSS16.0 Documentation >
Feature Documentation 04 Wireless > GSM-BSS >
(HDX)-EN GSM-BSS Public >
Feature Documentation
016C00SPH609 GSM Product Wireless > SingleRAN >
BSC6910V100R Documentation MBSC> BSC6910 GSM
016C00SPH608 (V100R016C00_03)(HDX)- > V100R016C00
EN
BSC6910V100R
016C00SPH605 (For Customer)GBSS16.0 Documentation >
016C00SPH602 GSM Product Wireless > SingleRAN >
Documentation MBSC> BSC6910 GSM
(V100R016C00_02)(HDX)- > V100R016C00
EN
016C00SPC600 GSM Product Wireless > SingleRAN >
Documentation MBSC > BSC6910 GSM
(V100R016C00_01)(HDX)- > V100R016C00
EN

Copyright Huawei
BSC6910 GSM
1.7 Virus Scan Result

This software package has been scanned by the following antivirus software and no risks were
found. The following table lists the virus scan results.
Antivirus Antivirus Antivirus Time of Result

Software Software Database Scan
Name Version Version
Kav 10.1.0.867 20140911- 2014-09-12 No risks were

060002 found.
Avira 8.03.24.022 7.11.171.148 2014-09-12 No risks were
found.
Symantec 12.1.2015.2015 2014-09-07r3 2014-09-12 No risks were
found.
McAfee 5600:1067 7556:0 2014-09-12 No risks were
found.
OSCE 9.750.1007 1113900 2014-09-12 No risks were
found.
1.8 Important Notes

Table 1.1 Important notes for using BSC6910 V100R016C00SPC620
No. Event Remarks
1 Time restrictions None

2 Region/site restrictions None
3 Other restrictions The restricted features must be tested on one site
before the commercial release.
4 Version termination The time that a version terminates depends on the
version lifecycle management.

Copyright Huawei
BSC6910 GSM
Release Notes 2 Version Compatibility
2 Version Compatibility
2.1 Software Version Compatibility

BSC version compatibility: The current version supports all the features of
BSC6910V100R015C00.
2.2 Hardware Version Compatibility

The following table describes compatibility between the hardware and the software versions.
Y indicates that the current product version is compatible with an earlier board software version, and N
indicates that the current product version is incompatible with an earlier board software version.
Table 1.1 Hardware version compatibility (BSC6910)

Board Name BSC6910V100R015C00
SCUb Y
GCUa Y
GCGa Y
UOIc Y
FG2c Y
GOUc Y
FG2d Y
GOUd Y
POUc Y
EOMUa Y
ESAUa Y

Copyright Huawei
BSC6910 GSM
Release Notes 2 Version Compatibility
Board Name BSC6910V100R015C00
EGPUa Y
EXOUa Y
ENIUa Y
EXPUa Y
DPUf N
GCUb N
GCGb N
GOUe N

Copyright Huawei
BSC6910 GSM 3 Changes from V100R016C00SPH609 to
Release Notes V100R016C00SPC620
3 Changes from
V100R016C00SPH609 to
V100R016C00SPC620
3.1 Change Summary

Capacity and Performance
Compared with those in BSC6910V100R016C00SPH609, capacity and performance remain
unchanged in BSC6910V100R016C00SPC620.
Hardware
Compared with that in BSC6910V100R016C00SPH609, hardware remains unchanged in
BSC6910V100R016C00SPC620.
Features
Compared with those in BSC6910V100R016C00SPH609, no features have been added, 4
features have been modified, and no features have been deleted in
BSC6910V100R016C00SPC620.
3.1.3 Features provides the following information about new or modified features:
Whether this feature has any impact on capacity and performance
Whether this feature is license-controlled
Whether this feature requires hardware support
Whether data configurations are required to enable this feature
Resolved Issues
Compared with those in BSC6910V100R016C00SPH609, no critical issues, 6 major issues, 6
minor issues, and 12 suggestion-level issues have been resolved in
BSC6910V100R016C00SPC620.
3.1.4 Resolved Issues provides the following information about resolved issues:

Copyright Huawei
Whether there is any impact of this solution

Whether this solution is controlled by a parameter
Default value of the parameter that controls the solution after an upgrade
Operation and Maintenance

Configuration management
Compared with those in BSC6910V100R016C00SPH609, configuration management
functions remain unchanged in BSC6910V100R016C00SPC620. For details about MML
command and parameter changes, see 8.1 MML Command Changes and 8.2 Parameter
Changes, respectively.
Performance management
Compared with those in BSC6910V100R016C00SPH609, performance management
functions remain unchanged in BSC6910V100R016C00SPC620. For details about
counter changes, see 8.5 Counter Changes.
Fault management
Compared with those in BSC6910V100R016C00SPH609, fault management functions
remain unchanged in BSC6910V100R016C00SPC620. For details about alarm and event
changes, see 8.3 Alarm Changes and 8.4 Event Changes, respectively.
License management
Compared with those in BSC6910V100R016C00SPH609, license management functions
remain unchanged in BSC6910V100R016C00SPC620. For details about license
changes, see 8.6 License Changes.
Related Documentation
Compared with those in BSC6910V100R016C00SPH609, document organization and
document templates remain unchanged in BSC6910V100R016C00SPC620. For details about
documentation updates, see (For Customer)BSC6910 GSM Product Documentation
(V100R016C00_04)(HDX)-EN.
3.1.1 Capacity and Performance

This section describes the general impact of this version on system capacity and network
performance.
unchanged in BSC6910V100R016C00SPC620.
3.1.2 Hardware
This section describes any hardware addition and modification. The hardware end of
marketing (EOM) and end of service (EOS) information does not map onto the software
version. For details, see the corresponding product change notice (PCN).
New Hardware
None
Modified Hardware
None

Copyright Huawei
3.1.3 Features
This section provides the following aspects of all feature changes from
BSC6910V100R016C00SPH609 to BSC6910V100R016C00SPC620:
Change type
Feature description
Impact on capacity and performance
(Optional) RAT
For a summary of these changes, see Summary of Feature Changes in BSC6910 GSM
V100R016C00SPC620.xls, or see the V100R016C00SPC620 vs V100R016C00SPH609 sheet
in Summary of Feature Changes delivered with the release notes for a version later than
BSC6910V100R016C00SPC620.
For details about these changes, see 3.2 Feature Changes.
3.1.4 Resolved Issues

This section provides the following aspects of issues resolved in
BSC6910V100R016C00SPC620 but unresolved in BSC6910V100R016C00SPH609:
Trouble ticket number
Issue description
Severity
Solution impact
Parameter control
(Optional) RAT
For a summary of these issues, see Summary of Resolved Issues in BSC6910 GSM
V100R016C00SPC620.xls, or see the V100R016C00SPC620 vs V100R016C00SPH609 sheet
in Summary of Resolved Issues delivered with the release notes for a version later than
BSC6910V100R016C00SPC620.
For details about these issues, see 3.3 Resolved Issues.
3.1.5 Operation and Maintenance

3.1.5.1 Configuration Management
functions remain unchanged in BSC6910V100R016C00SPC620. For details about changes to
MML commands and parameters, see 8.1 MML Command Changes and 8.2 Parameter
Changes.

Copyright Huawei
3.1.5.2 Performance Management

functions remain unchanged in BSC6910V100R016C00SPC620. For details about counter
changes, see 8.5 Counter Changes.
3.1.5.3 Fault Management

remain unchanged in BSC6910V100R016C00SPC620. For details about changes to alarms
and events, see 8.3 Alarm Changes and 8.4 Event Changes.
3.1.5.4 License Management

remain unchanged in BSC6910V100R016C00SPC620. For details about license changes, see
8.6 License Changes.
3.1.6 Related Documentation

For details about documentation updates, see (For Customer)BSC6910 GSM Product
Documentation (V100R016C00_04)(HDX)-EN.
3.2 Feature Changes

3.2.1 New Features
None
3.2.2 Modified Features

3.2.2.1 TCH-related Counter Optimization for Users with
Specific Priorities
Description
This feature optimizes counters related to traffic channels (TCHs) for users with specific
priorities. The optimization includes the following aspects:
The measurement points for certain counters are modified. After the modification, these
counters are no longer measured in the handover procedure, thereby helping customers
clearly learn the initial access success rate for users with a specific priority in a cell.
Reserved counters are used to measure the number of successful TCH assignments for
users with a specific priority.
Implementation
The measurement points for the following counters have been modified:
A0331B: Number of TCH Occupation Requests for Priority 1 User
A0331A: Number of Successful TCH Occupation for Priority 1 User
A0301G: Number of TCH Occupation Requests for Priority 2 User

Copyright Huawei
A0331F: Number of Successful TCH Occupation for Priority 2 User

Before the modification, the BSC measures these counters in both assignment and handover
procedures.
After the modification, the BSC measures these counters in the assignment procedure but
does not measure them in the handover procedure. This way, the counters indicate the
numbers of TCH requests and successful TCH assignments for users with a specific priority in
the assignment procedure.
The following reserved counters are now used to measure the number of successful TCH
assignments for users with a specific priority:
Reserved counter 14 for cell
This counter represents "Number of Successful TCH Assignments for Priority 1 User
(Excluding Handover)", which provides the number of successful TCH assignments
for priority 1 users in the assignment procedure for call setup.
This counter represents "Number of Successful TCH Assignments for Priority 2 User
(Excluding Handover)", which provides the number of successful TCH assignments
for priority 2 users in the assignment procedure for call setup.
The following counter relationships are adopted:
A0331B: Number of TCH Occupation Requests for Priority
1 User Number of Successful TCH Assignments for
Priority 1 User (Excluding Handover) A0331A: Number of
Successful TCH Occupation for Priority 1 User
A0301G: Number of TCH Occupation Requests for Priority 2
User Number of Successful TCH Assignments for Priority
2 User (Excluding Handover) A0331F: Number of
Successful TCH Occupation for Priority 2 User
Impact on Capacity and Performance

None
Impact on NEs
None
Impact on Hardware
None
Impact on Inter-NE Interfaces

None
Impact on Operation and Maintenance

Impact on license management

Copyright Huawei
None
Impact on configuration management
None
Impact on performance management
Used "Reserved counter 14 for cell" and "Reserved
counter 15 for cell."
Modified the measurement points for the following
counters:
A0331B: Number of TCH Occupation Requests for
Priority 1 User
A0331A: Number of Successful TCH Occupation for
Priority 1 User
A0301G: Number of TCH Occupation Requests for
Priority 2 User
A0331F: Number of Successful TCH Occupation for
Priority 2 User
Impact on fault management
None
Impact on Other Features

None
Related Operations
Subscribe to the following counters on the U2000:
A0331B: Number of TCH Occupation Requests for Priority 1 User
A0331A: Number of Successful TCH Occupation for Priority 1 User
A0301G: Number of TCH Occupation Requests for Priority 2 User
A0331F: Number of Successful TCH Occupation for Priority 2 User
Trouble Ticket Number

DTS2014072904678
Feature ID
GBFD-115001

Copyright Huawei
3.2.2.2 CCCH Flow Control Parameter Optimization
Description
This feature uses certain bits of reserved parameters for the CCCH flow control function. This
feature helps resolve CCCH congestion caused by a large number of access requests when
traffic is heavy and is used in emergency handling.
This feature includes the following solutions:
Solution 1: Before this optimization, the BSC performs flow control based on the paging
message arrival rate, and the maximum of paging messages that can be processed by a
CPUS is fixed to 6000. After this optimization, the maximum of paging messages that
can be processed by a CPUS can be configured using a parameter.
Solution 2: The BSC accurately controls the number of MSs accessing a cell with an
excessively large number of accesses based on the settings of parameters related to the
random access message arrival rate at the cell level.
Implementation
Solution 1: Configure the paging message arrival rate at the subsystem level.
The BSC monitors the number of CS paging messages in real time. If the number of
CS paging messages received by the BSC exceeds the maximum number of CS
paging messages that can be processed by a CPUS per second within 1s,the BSC
discards subsequent CS paging messages during this period. If the Paging Message
Classifying Allowed parameter in the SET BSCFCPARA command is set to 2 and
the number of paging messages exceeds 80% of the maximum number of CS paging
messages that can be processed by a CPUS per second, the BSC discards subsequent
secondary paging messages during this period.
Bits 15 to 20 of the BSC CS Reserved Parameter 1 parameter in the SET
GRSVPARA command specifies the maximum number of CS paging messages that
can be processed by a CPUS per second. When bits 15 to 20 is set to 63, the
maximum number of CS paging messages that can be processed by a CPUS per
second is 6000. When bits 15 to 20 is set to a value ranging from 1 to 60, the
maximum number of CS paging messages that can be processed by a CPUS per
second is equal to the value of bits 15 to 20 multiplied by 100. When bits 15 to 20 is
set to a value less than 1 or greater than 60, the maximum number of CS paging
messages that can be processed by a CPUS per second is 6000. The default GUI
value of bits 15 to 20 is 63.
The BSC monitors the number of PS paging messages in real time. If the number of
PS paging messages received by the BSC exceeds the maximum number of PS
paging messages that can be processed by a CPUS per second within 1s,the BSC
discards subsequent PS paging messages during this period.
Bits 7 to 12 of the BSC PS Reserved Parameter 1 parameter in the SET
GRSVPARA command specifies the maximum number of PS paging messages that
can be processed by a CPUS per second. When bits 7 to 12 is set to 0, the maximum
number of PS paging messages that can be processed by a CPUS per second is 6000.
When bits 7 to 12 is set to a value ranging from 1 to 60, the maximum number of PS
paging messages that can be processed by a CPUS per second is equal to the value of
bits 7 to 12 multiplied by 100. When bits 7 to 12 is set to a value greater than 60, the
maximum number of PS paging messages that can be processed by a CPUS per
second is 6000. The default GUI value of bits 7 to 12 is 0.
Solution 2: Configure the random access request message arrival rate at the cell level.

Copyright Huawei
The BSC monitors the number of random CS access requests in real time.
If the number of random access requests with the access cause location update
received by a cell exceeds the maximum number of location update request messages
that can be processed by the cell per second within 1s, the BSC discards subsequent
random access requests with the access cause location update during this period. This
function is controlled by a parameter and is disabled by default.
Bits 12 to 15 of the Cell CS Reserved Parameter 1 parameter in the SET
GCELLRSVPARA command specifies the maximum number of location update
request messages that can be processed by a cell per second. When bits 12 to 15 is set
to 15, the flow control based on the location update request message arrival rate at the
cell level is not triggered. When bits 12 to 15 is set to a value ranging from 1 to 14,
the maximum number of location update request messages that can be processed by a
cell per second is equal to the value of bits 12 to 15 multiplied by 10. When bits 12 to
15 is set to 0, the maximum number of location update request messages that can be
processed by a cell per second is 150. The default GUI value of bits 12 to 15 is 15.
If the number of call access requests received by a cell exceeds the maximum number
of CS channel request messages that can be processed by the cell per second within
1s, the BSC discards subsequent call access requests during this period. This function
is controlled by a parameter and is disabled by default.
Bits 0 to 4 of the Cell CS Reserved Parameter 2 parameter in the SET
GCELLRSVPARA command specifies the maximum number of CS channel request
messages that can be processed by a cell per second. When bits 0 to 4 is set to 31, the
flow control based on the CS channel request message arrival rate at the cell level is
not triggered. When bits 0 to 4 is set to a value ranging from 1 to 30, the maximum
number of CS channel request messages that can be processed by a cell per second is
equal to the value of bits 0 to 4 multiplied by 10. When bits 0 to 4 is set to a value
less than 1, the flow control based on the CS channel request message arrival rate at
the cell level is not triggered. The default GUI value of bits 0 to 4 is 31.
The BSC monitors the number of random PS access requests in real time.
If the number of random PS access requests for calls received by a cell exceeds the
maximum number of PS channel request messages that can be processed by the cell
per second within 1s, the BSC discards subsequent random PS access requests during
this period. This function is controlled by a parameter and is disabled by default.
Bits 4 to 9 of the Cell PS Reserved Parameter 1 parameter in the SET
GCELLRSVPARA command specifies the maximum number of PS channel request
messages that can be processed by a cell per second. When bits 4 to 9 is set to 0, the
flow control based on the PS channel request message arrival rate at the cell level is
not triggered. When bits 4 to 9 is set to a value ranging from 1 to 60, the maximum
number of PS channel request messages that can be processed by a cell per second is
equal to the value of bits 4 to 9 multiplied by 10. When bits 4 to 9 is set to a value
greater than 60, the flow control based on the PS channel request message arrival rate
at the cell level is not triggered. The default GUI value of bits 4 to 9 is 0.

After the flow control based on the paging message arrival rate is triggered, the values of
the following counters increase based on the access cause value:
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)

Copyright Huawei
After the flow control based on the random access request message arrival rate is
triggered, the values of the following counters increases based on the access cause value:
L3189A: Discarded Channel Requests (MOC)
L3189B: Discarded Channel Requests (MTC)
L3189C: Discarded Channel Requests (Emergency Call)
L3189D: Discarded Channel Requests (Call Re-establishment)
L3189E: Discarded Channel Requests (Location Updating)
L3189F: Discarded Channel Requests (Packet Call)
L3189G: Discarded Channel Requests (LMU+Reserved)
L3189H: Discarded Channel Requests (Protocol Undefined)
L3189I: Discarded Channel Requests
A1309A: Number of Discarded CS Channel Requests (Flow Control over Message
Arrival Rate)
A1309B: Number of Discarded PS Channel Requests (Flow Control over Message
Arrival Rate)
Impact on NEs
None
Impact on Hardware
None

None

None
Used bits 5 to 20 of the BSC CS Reserved Parameter 1 parameter in the SET
GRSVPARA command to specify the maximum number of CS paging messages that
can be processed by a CPUS per second.
Used bits 7 to 12 of the BSC PS Reserved Parameter 1 parameter in the SET
GRSVPARA command to specify the maximum number of PS paging messages that
can be processed by a CPUS per second.
Used bits 12 to 15 of the Cell CS Reserved Parameter 1 parameter in the SET
GCELLRSVPARA command to specify the maximum number of location update
request messages that can be processed by a cell per second.
Used bits 0 to 4 of the Cell CS Reserved Parameter 2 parameter in the SET
GCELLRSVPARA command to specify the maximum number of CS channel
Used bits 4 to 9 of the Cell PS Reserved Parameter 1 parameter in the SET
GCELLRSVPARA command to specify the maximum number of PS channel

Copyright Huawei

None
None

None
Related Operations
Configure the paging message arrival rate at the subsystem level by performing the
following operations:
To set the maximum number of CS paging messages that can be processed by a
CPUS per second to 3000, run the following command:
SET GCELLRSVPARA: BSCCSDPARA1=4293885951;
Set BSC CS Reserved Parameter 1 based on the current parameter setting. For
example, if the current value of BSC CS Reserved Parameter 1 is 4294967295
(11111111111111111111111111111111 in binary), set this parameter to 4293885951
(11111111111011110111111111111111 in binary) with bits 5 to 20 set to 30.
To set the maximum number of PS paging messages that can be processed by a CPUS
per second to 3000, run the following command:
SET GRSVPARA: BSCPSDPARA1=3840;
Set BSC PS Reserved Parameter 1 based on the current parameter setting. For
example, if the current value of BSC PS Reserved Parameter 1 is 0
Configure the channel request message arrival rate at the cell level by performing the
following operations:
To enable the flow control based on the location update request message arrival rate
at the cell level and set the maximum number of location update request messages
that can be processed by a cell per second to 10, run the following command:
SET GCELLRSVPARA: IDTYPE=BYID, CELLID=0, GCELLCSDPARA1=8191;
Set Cell CS Reserved Parameter 1 based on the current parameter setting. For
example, if the current value of Cell CS Reserved Parameter 1 is 65535
(1111111111111111 in binary), set this parameter to 8191 (0001111111111111 in
binary) with bits 12 to 15 set to 1.
To disable the flow control based on the location update request message arrival rate
at the cell level, run the following command:
SET GCELLRSVPARA: IDTYPE=BYID, CELLID=0,
GCELLCSDPARA1=65535;
(0001111111111111 in binary), you can set this parameter to 65535 (1111111111111111
in binary) with bits 12 to 15 set to 15.
To enable the flow control based on the CS channel request message arrival rate at
the cell level and set the maximum number of CS channel request messages that can
be processed by a cell per second to 70, run the following command:

Copyright Huawei
(11111111111111111 in binary), set this parameter to 65511 (1111111111100111 in
binary) with bits 0 to 4 set to 7.
To disable the flow control based on the CS channel request message arrival rate at
the cell level, run the following command:
(1111111111100111 in binary), you can set this parameter to 65535 (1111111111111111
in binary) with bits 0 to 4 set to 31.
To enable the flow control based on the PS channel request message arrival rate at the
cell level and set the maximum number of PS channel request messages that can be
processed by a cell per second to 100, run the following command:
SET GCELLRSVPARA: IDTYPE=BYID, CELLID=0, GCELLPSDPARA1=160;
Set Cell PS Reserved Parameter 1 based on the current parameter setting. For
example, if the current value of Cell PS Reserved Parameter 1 is 0
To disable the flow control based on the PS channel request message arrival rate at
the cell level, run the following command:
SET GCELLRSVPARA: IDTYPE=BYID, CELLID=0, GCELLPSDPARA1=0;
Set Cell PS Reserved Parameter 1 based on the current parameter setting. For
example, if the current value of Cell PS Reserved Parameter 1 is 160
(00000000000000000000000010100000 in binary), you can set this parameter to 0

DTS: DTS2014081207966
Feature ID
GBFD-111705
3.2.2.3 Support for Subrack DIP Switch Status Check
Description
The subrack DIP switch status check function is added to the FMA on the Web LMT. With
this function, users can check whether the DIP switch on a subrack is correctly set and
efficiently locate and resolve problems if the DIP switch status is abnormal.
Implementation
The GSM Equipment health check option has been added to the Others node under GSM
Fault Analysis on the FMA tab page on the Web LMT. When this option is selected, the
system performs Fault Diagnosis function, including DIP switch status check.

Copyright Huawei

None
Impact on NEs
None
Impact on Hardware
None

None

None
None
None
None

None

Copyright Huawei
Related Operations
None

DTS: DTS2014052300745
Feature ID
None
3.2.2.4 Upgrade Tool Reliability Optimization
Description
This feature optimizes the upgrade operation procedure and the display of upgrade reports on
the upgrade tool. With this feature, user misoperations can be reduced, and upgrade reports
better steer upgrade operations, thereby improving the reliability of the upgrade tool.
Implementation
The optimization is described as follows:
1. The statements have been added to the Input Step 1 window on the upgrade tool, as
shown in the following figure. The statements help users avoid performing illegal
operations during an upgrade.
2. In version upgrade scenarios, suggestive descriptions have been added to the Confirm
window displayed after users click Next in the Input Step 2 window on the upgrade
tool.
For an upgrade not requiring an intermediate version, the following descriptions are
added.
For an upgrade requiring an intermediate version, the following descriptions are

added.

Copyright Huawei
3. The display of the Runtime Result column in upgrade reports has been optimized. If
users select Continue when an item fails during an upgrade, instead of IGNORED,
error information is displayed in the Runtime Result column for the item, as shown in
the following figure.
4. The Error Impact and Troubleshooting columns have been added to upgrade reports,
as shown in the following figure. The Error Impact column describes the impacts when
the execution of a check item fails. The Troubleshooting column provides guidance in
handling the failure.

None
Impact on NEs
None

Copyright Huawei
Impact on Hardware
None

None

None
None
None
None

None
Related Operations
None

DTS: DTS2014071004638
Feature ID
None
3.2.3 Deleted Features

None
3.3 Resolved Issues

3.3.1 Critical
None

Copyright Huawei
3.3.2 Major
3.3.2.1 The measured call setup duration is incorrect after
an MS is handed over to another BSC and makes a call to a
third MS.
Trouble iCare: 2206822
Ticket DTS: DTS2014070100182
Number
Descriptio Condition:
n An MS (MS 1) makes a call to another MS (MS 2) under a BSC (BSC
1). The call is processed properly.
MS 1 is handed over to another BSC (BSC 2) and makes a call to a third
MS (MS 3) under BSC 2. MS 1 sends the HOLD message to the MSC
to hold the call with MS 2.
Symptom: The measured values of the AA033: Mean Duration of Call
Establishment and AA3251: Average Call Setup Duration counters
measured by BSC 2 are greater than the actual values.
Impact: The measured values of the preceding counters cannot reflect the
actual call setup duration.
Severity Major
Root In the preceding scenario, BSC 2 measures the call setup duration for MS
Cause 1 from the time BSC 2 receives the incoming BSC handover request from
the MSC to the time BSC 2 receives the first ALTERTING message from
MS 1.
After MS 1 is handed over to BSC 2 and the MS 1-to-MS 2 call is
maintained for a while, MS 1 makes the call to MS 3. However, BSC 2
includes the MS 1-to-MS 3 call setup duration, which includes the MS 1-
to-MS 2 call duration under BSC 2, in the AA033 and AA3251 counters.
As a result, the values of the AA033 and AA3251 counters measured for
MS 1 are greater than the actual values.
Solution BSC 2 no longer includes the MS 1-to-MS 3 call setup duration in the
AA033 and AA3251 counters in the preceding scenario.
Solution After this solution is used, the values of the following counters decrease:
Impact AA033: Mean Duration of Call Establishment
AA3251: Average Call Setup Duration
Test Case CASE_Commercial_PR_Regression_R016C00SPC620_201
3.3.2.2 Incoming RNC-to-BSC handovers are displayed as

incoming inter-BSC handovers on the Nastar because the
source cell ID has changed.
Ticket

Copyright Huawei
Number DTS: DTS2014071603826
Description Condition: The source cell ID changes during an incoming RNC-to-

BSC handover. As a result, the source cell ID in the handover
information area of CHRs recorded by the BSC is different from that in
the interworking rule used by the Nastar for incoming RNC-to-BSC
handovers.
Symptom: Incoming RNC-to-BSC handovers are displayed as
incoming inter-BSC handovers on the Nastar.
Impact: The incoming BSC handovers displayed on the Nastar cannot
reflect actual handover types.
Severity Major
Root Cause According to the original interworking rule between the BSC and
Nastar, if the source cell ID in the handover information area of CHRs
is 5048, the handover type displayed on the Nastar is incoming RNC-
to-BSC handover. As the specifications of external neighboring cells
change on the BSC side, the interworking rule on the BSC side
becomes inconsistent with that on the Nastar side. As a result, incoming
RNC-to-BSC handovers are displayed as incoming inter-BSC
handovers on the Nastar.
Solution The BSC and Nastar now use a new interworking rule in the preceding
scenario. Specifically, both the BSC and Nastar set the source cell ID in
the handover information area of CHRs for an incoming RNC-to-BSC
handover to 50000. This solution requires support from iManager
Nastar V600R014C00SPC230 or later.
Solution None
Impact
3.3.2.3 DTM congestion occurs because the BSC does not

dynamically convert PDCHs into TCHs in a timely manner in
the DTM procedure.
Number
Descripti Condition:
on The Support DTM parameter in the SET GCELLGPRS is set to
SUPPORT(Support).
The DTM Performance Optimization Switch parameter in the SET
GCELLGPRS is set to OFF(Off).
In the DTM procedure, an MS has occupied an SDCCH for CS services
and needs to apply for TCHs.
There are idle TCHs in the cell. The adjacent channels of the idle TCHs
are not PDCHs.

Copyright Huawei
There are dynamic PDCHs in the cell.

Symptom: In the DTM procedure, the BSC allocates TCHs to the MS
using the assignment procedure.
Impact: DTM services fail.
Severity Major
Root In the preceding scenario, the BSC allocates TCHs to the MS using the
Cause assignment procedure and dynamically converts channels adjacent to the
TCHs into PDCHs. These PDCHs will be used in next DTM procedure.
However, the BSC does not dynamically convert PDCHs into TCHs in the
current DTM procedure. As a result, DTM congestion occurs.
Solution The BSC now dynamically converts PDCHs into TCHs for CS services in
the current DTM procedure in the preceding scenario.
SW17 of the Cell CS Reserved Switch Parameter 0 parameter in the SET
GCELLRSVPARA command controls whether to enable this solution. By
default, this feature is disabled (default value: 0) for new networks, but is
enabled (default value: 1) after upgrades.
Solution After this solution is used, the values of the following counters decrease:
Impact A9815: Number of Failed Uplink DTM TBF Establishments Due to No
Channel
A9818: Number of Failed Downlink DTM TBF Establishments Due to
No Channel
A9203: Number of Failed Uplink EGPRS TBF Establishments due to No
Channel
A9003: Number of Failed Uplink GPRS TBF Establishments due to No
Channel
A9303: Number of Failed Downlink EGPRS TBF Establishments due to
No Channel
A9103: Number of Failed Downlink GPRS TBF Establishments due to
No Channel
AL9426: Uplink Throughput of EGPRS Users LLC PDU
AL9425: Uplink Throughput of GPRS Users LLC PDU
AL9529: Downlink Throughput of GPRS Users LLC PDU
AL9530: Downlink Throughput of EGPRS Users LLC PDU
The values of the following counters increase:
R3161A: Number of BSC-Initiated Requests for Dynamic PDCH
A9217: Number of Uplink EGPRS TBF Abnormal Releases due to
Channel Preemption
A9017: Number of Uplink GPRS TBF Abnormal Releases due to
Channel Preemption
A9316: Number of Downlink EGPRS TBF Abnormal Releases due to
Channel Preemption
A9116: Number of Downlink GPRS TBF Abnormal Releases due to
Channel Preemption

Copyright Huawei
3.3.2.4 The BSC cannot allocate TCH channels on BCCH-

incompatible frequency bands to MSs during immediate
assignment when the BSC supports TCHs that function as
signaling channels.
Number
Descripti Condition:
on The BSC supports TCHs that function as signaling channels. For
example, the TCH Immediate Assignment parameter in the SET
GCELLBASICPARA command is set to YES(Yes).
All idle channels in a cell are TCHs on BCCH-incompatible frequency
bands.
Symptom: The BSC fails to allocate TCH channels to MSs during
immediate assignment.
Impact: Calls fail to access the cell.
Severity Major
Root In the preceding scenario, the BSC cannot obtain the frequency band
Cause capability of MSs. As a result, the BSC fails to allocate channels to MSs.
For example, if the frequency of the BCCH TRX is 1 and that of non-
BCCH TRXs is 0, when the BCCH TRX participates in baseband
frequency hopping, the channel on timeslot 0 on the BCCH TRX is on P
band and the other channels are on E band. In this situation, the BSC
considers that the MS only supports P band. As a result, the channel
allocation fails.
Solution The BSC now uses the following channel allocation policy in the preceding
scenario:
The BSC can allocate idle TCHs on BCCH-incompatible frequency bands
to MSs. This policy is controlled by SW15 of the Cell CS Reserved
Switch Parameter 0 parameter in the SET GCELLRSVPARA command.
By default, this policy is disabled (default value: 0) for both new networks
and upgrade scenarios.
Solution After this solution is used:
Impact When SW15 of the Cell CS Reserved Switch Parameter 0 parameter in
the SET GCELLRSVPARAcommand is set to 1:
The value of the K3023: Successful TCH Seizures (Signaling Channel)
counter increases.
The value of the K3021: Failed TCH Seizures due to Busy TCH
(Signaling Channel) counter decreases.
If MSs supporting only BCCH-compatible frequency bands exist in a cell,
the value of the CA304: Call Setup Indications Timed Out counter
increases.

Copyright Huawei
3.3.2.5 The value of the K3043 counter is greater than 100%

when the BSC processes buffered downlink DTM service
requests after a DTM assignment fails.
Number
Description Condition: The BSC processes buffered downlink DTM service

requests after a DTM assignment fails.
Symptom: The value of the K3043: TCH Seizure Success Rate
counter is greater than 100%.
Impact: The measured value of the K3043 counter is incorrect. It is
inconvenient for users to monitor network performance.
Severity Major
Root Cause After a DTM assignment fails, if downlink DTM service requests are
buffered, the BSC incorrectly processes these DTM services as
common calls. As a result, the BSC sends the Handover Command
messages to MSs. As these Handover Command messages have no
corresponding handover requests, the value of the K3043: TCH
Seizure Success Rate counter is greater than 100%.
Solution After a DTM assignment fails, the BSC now discards the buffered
downlink DTM service requests if any.
Solution After this solution is used, the values of the following counters
Impact decrease:
K3043: TCH Seizure Success Rate
CH301: Internal Intra-Cell Handover Commands
CH304: Internal Intra-Cell Handover Detection Messages Received
by BSC
3.3.2.6 PS services cannot be performed when the BCCH

TRX participates in frequency hopping and the MA group
includes frequencies on P and E bands.
Number

Copyright Huawei
Description Condition: The BCCH TRX of a cell works on P band and

participates in frequency hopping. The MA group includes
frequencies on P and E bands.
Symptom: The values of the following counters increase:
A9203: Number of Failed Uplink EGPRS TBF Establishments due
to No Channel
A9003: Number of Failed Uplink GPRS TBF Establishments due to
No Channel
Impact: The BSC rejects PS service requests of MSs in the cell. As a
result, MSs fail to access the cell.
Severity Major
Root Cause The frequency band of a TRX is the highest frequency band among
all frequency bands supported by MA groups on all timeslots of the
TRX.
The frequency band of an MA group is the highest frequency band
among all frequency bands where frequencies in the MA group
belong to.
If frequencies in an MA group belong to P and E bands, the frequency
band of the MA group is E band. If the frequency band of the BCCH
TRX is P band, the TRX for the MA group is incompatible with the
BCCH TRX (referred to as a BCCH-incompatible TRX).
When the BSC does not obtain the multislot capability of an MS, the
BSC can only select channels on BCCH-compatible TRXs for the
MS. As the BCCH TRX participates in frequency hopping and the
MA group includes frequencies on P and E bands, the BSC cannot
find any BCCH-compatible TRXs and therefore it rejects PS service
requests of the MS.
Solution The BSC can now select channels on both BCCH-compatible TRXs
and BCCH-incompatible TRXs in a cell in the preceding scenario.
Bit 30 of the Cell Reserved Parameter 4 parameter in the SET
GCELLPRIVATEOPTPARA command controls whether to enable
this solution. When bit 30 is set to 1, this solution is enabled. When
bit 30 is set to 0, this solution is disabled. By default, this solution is
disabled (default value: 0) for both new networks and upgrade
scenarios.
To set bit 30 to 1, run the following command:
SET GCELLPRIVATEOPTPARA: IDTYPE=BYID, CELLID=0,
CellPSReservePara4=1073741824;
where the value 1073741824 (0100 0000 0000 0000 0000 0000 0000
0000 in binary) indicates that bit 30 is set to 1.
Set Cell Reserved Parameter 4 based on the current parameter
setting. For example, if the current value of Cell Reserved
Parameter 4 is 1 (0000 0000 0000 0001 in binary), set this parameter
to 1073741825 (0100 0000 0000 0000 0000 0000 0000 0001 in
binary) with bit 30 set to 1.
Solution After this solution is used, the BSC no longer rejects PS service
Impact requests in the preceding scenario. The values of the following

Copyright Huawei
counters decrease:
to No Channel
No Channel
However, if MSs that do not support BCCH-incompatible frequency
bands exist in a cell, the values of the following counters increase:
to MS No Response
MS No Response
3.3.3 Minor
3.3.3.1 The loading speed of the TDM BTS software version
is always 64 kbit/s.
Trouble DTS: DTS2014072505780
Ticket
Number
Description Condition: The BTS uses TDM transmission. The Abis interface board
is POUc.
Symptom: The loading speed of the BTS software version is always 64
kbit/s.
Impact: The loading speed of the BTS software version is low.
Severity Minor
Root Cause During the loading of the BTS software version in the preceding
scenario, the service module sends a message to the Abis interface
board to activate the DML. However, the CPU ID contained in the
message is incorrect. As a result, the DML cannot be activated properly.
In this situation, the BTS software version can only be loaded over the
OML. Therefore, the loading speed is always 64 kbit/s.
Solution The service module now fills the correct CPU ID in the message to be
sent to the Abis interface board to ensure that the DML can be activated
properly.
Solution None
Impact

Copyright Huawei
3.3.3.2 The RST BSC command execution times out when the
active and standby SCU boards are unavailable.
Ticket
Number
Description Condition: The RST BSC command is executed when the active and
standby SCU boards are unavailable.
Symptom: The RST BSC command execution times out.
Impact: The BSC reset fails.
Severity Minor
Root Cause When the active and standby SCU boards are unavailable, they do not
respond to the RST BSC command. As a result, the RST BSC
command execution times out.
Solution The BSC now retries automatically when the RST BSC command
execution times out, thereby increasing the command execution success
rate. In addition, the LMT now displays the command execution
progress.
Solution The RST BSC command execution timeout interval increases from 1
Impact minute to 4 minutes.
3.3.3.3 The causes for signaling link interruption or

transmission faults cannot be quickly identified.
Ticket
Number
Description Condition: LAPD or SCTP links are carried on an

FG2c/GOUc/FG2d/GOUd/GOUe/EXOUa board.
Symptom: When the LAPD or SCTP links on the preceding boards are
interrupted or transmission on these links becomes faulty, the existing
information cannot help engineers quickly analyze the faults.
Impact: No method is available for engineers to quickly identify the
cause of LAPD or SCTP link faults.
Severity Minor
Root Cause When LAPD or SCTP links are interrupted or transmission on these
links becomes faulty, the existing information for quickly identifying
the fault cause is inadequate to determine whether the interface board
can correctly receive and send LAPD or SCTP packets.
Solution Packet capturing is used to collect the information about LAPD or
SCTP packet headers, and tracing the route to the peer IP address
using the Tracert command is used to collect the information about

Copyright Huawei
the transmission path of packets. This solution can be enabled on the

preceding boards for up to four times a day. Each packet capturing
lasts for 30s.
TS22(Time_slot_22) of Reserve switch 1 in the SET
TRANSRSVPARA command controls whether to automatically
enable the packet capturing and trace the route to the peer IP address
using the Tracert command when SCTP or LAPD links become
faulty. By default, this solution is enabled (default value: 1) for both
new networks and upgrade scenarios.
Solution After this solution is used, the duration of automatic packet capturing
Impact triggered by ALM-21388 Invalid Packets Exceeding Alarm is extended
from 10s to 30s.
3.3.3.4 The value of the Hosted domain queried in the DSP

OPC command output is incorrect.
Number
Descriptio Condition: Users run the DSP OPC command with The host type of
n signalling point set to SINGLEHOST(SINGLEHOST)to query the
originating point code (OPC) status.
Symptom: The value of Hosted is Yes in the DSP OPC command output.
Impact: The queried value of Hosted is incorrect and misleads users in
the preceding scenario.
Severity Minor
Root The Hosted domain is invalid although its value is Yes when The host
Cause type of signalling point is set to SINGLEHOST(SINGLEHOST). The
Hosted domain in the DSP OPC command output is valid only if The
host type of signalling point is set to PRIMHOST(PRIMHOST) or
SLAVEHOST(SLAVEHOST).
Solution Now, the value of Hosted in the DSP OPC command output is NULL
when The host type of signalling point is set to
SINGLEHOST(SINGLEHOST).
Solution None
Impact
3.3.3.5 The DSP GPS command output may be incorrect.

Ticket

Copyright Huawei
Number DTS: DTS2014061606607
n The BSC6910 uses a V100R016 version earlier than
V100R016C00SPC620.
The GPS is configured on a GCGa board. When the GPS is running
properly, the DSP GPScommand is executed.
Symptom: The DSP GPS command output shows "Gps out of position"
even if ALM-20243 Board Hardware Fault with the cause of "Satellite
Card Fault" is not reported on the alarm console.
Impact: The DSP GPS command output may be inconsistent with the
actual conditions.
Severity Minor
Root In V100R016C00 or later, the DSP GPSSTAT command is added to
Cause query the satellite health status. However, initially configuring the GPS
on a GCGa board prolongs and may expire. As a result, the GPS status is
set to "Not installed", and the DSP GPS command output shows "Gps out
of position."
Solution The GPS initial configuration expiration duration of the GCGa board has
been changed from 5s to 10s.
Solution None
Impact
3.3.3.6 A BSC6910 fails to be upgraded when adjacent

nodes are bound to IP logical ports of active and standby
boards in odd-numbered slots.
Ticket
Number
Descripti Condition: In non-trunk networking mode, a BSC6910 is upgraded from

on V100R015C00SPC525 or a later V100R015C00 patch version to a
V100R016C00 version earlier than V100R016C00SPC620. In addition,
adjacent nodes are bound to IP logical ports of active and standby
FG2c/GOUc/GOUe/EXOUa/FG2d/GOUd boards in odd-numbered slots.
Symptom: Database operations fail.
Impact: The BSC6910 upgrade fails.
Severity Minor
Root The slot No. specified in the ADD ADJLOGICPORTBIND command is

Cause inconsistent with that in the LST ADJLOGICPORTBIND command
output. Therefore, the slot No. in the LST ADJLOGICPORTBIND
command output is changed for V100R015C00SPC525 and later. However,
the upgrade rules are not changed accordingly. As a result, the upgrade fails.

Copyright Huawei
Solution The upgrade rules have been changed to ensure that the slot No. specified in
the ADD ADJLOGICPORTBIND command is consistent with that in the
LST ADJLOGICPORTBIND command output in the preceding scenario.
Solution None
Impact
Test CASE_Commercial_PR_Regression_R016C00SPC620_005
Case
3.3.4 Suggestion
3.3.4.1 The BSC whose homing status is "Not homed" cannot
correctly detect transmission connectivity over the A
interface.
Ticket
Number
Descriptio Condition: When BSC Node Redundancy is enabled, the homing status
n of a BSC is "Not homed."
Symptom: SCTP links to the BSC on the signaling plane over the A
interface become faulty.
Impact: No alarm is reported in the preceding scenario.
Severity Suggestion
Root When the homing status of the BSC is "Not homed", the status of the
Cause SCTP links to the BSC is forcibly changed to "Faulty."
Solution The BSC now detects the transmission connectivity on the signaling plane
over the A interface according to the actual SCTP link status.
Solution None
Impact
3.3.4.2 Call access fails because the cell PA status on the

BSC side is inconsistent with the TRX PA status on the
eGBTS side.
Ticket
Number
Description Condition:
To enable the Dynamic Cell Power Off feature for eGBTSs, run the
SET GCELLDYNTURNOFF command with the Enable Turning

Copyright Huawei
Off Cell parameter set to ENABLE(Enable).;

The eGBTS deployment test, radio frequency (RF) loopback, or
frequency scanning is performed on the eGBTS side. In this
situation, the eGBTS cannot disable the TRX.
Symptom: The cell PA on the BSC side is disabled, causing call access
failures. The TRX PA on the eGBTS side is enabled.
Impact: The value of the RA303G: Success Rate of Immediate
Assignments counter decreases.
Severity Suggestion
Root Cause In the preceding scenario, the BSC sends a TRX SERVICE CONTROL
message to the eGBTS, instructing the eGBTS to disable the TRX. The
eGBTS responds the TRX SERVICE CONTROL message with another
TRX SERVICE CONTROL message. Upon receiving the TRX
SERVICE CONTROL message from the eGBTS, the BSC sets the cell
PA status to power-off. As the TRX PA on the eGBTS side is still
enabled in the preceding scenario, call access attempts are allowed.
However, the cell PA is disabled on the BSC side. As a result, the BSC
rejects the immediate assignment request, causing call access failures.
Solution The BSC no longer sets the cell PA status to power-off upon receiving
the TRX SERVICE CONTROL message from the eGBTS. Instead, the
BSC now updates the cell PA status according to the BCCH TRX PA
status reported by the eGBTS. This ensures that the cell PA status on
the BSC is consistent with the TRX PA status on the eGBTS side.
Solution After this solution is used, the value of the RA303G: Success Rate of
Impact Immediate Assignments counter increases.
3.3.4.3 Users have difficulty querying configurable cell

parameters when adding a cell template.
Trouble DTS:DTS2014070105634
Ticket
Number
Description When users add a cell template by running the ADD

GCELLTEMPLATEPARA command, cell parameters configured in
the cell template are not listed in the LST GCELLTEMPLATEPARA
command output as expected. As a result, the configuration result does
not take effect even if the ADD GCELLTEMPLATEPARA command
was successfully executed.
Severity Suggestion
Root Cause Users must run the LST GCELLTEMPLATEPARA command before
adding a cell template. In addition, this requirement is not described in
MML Command Reference.
Solution The preceding requirement is now described in MML Command

Copyright Huawei
Reference.
The following note has been added to the ADD
GCELLTEMPLATEPARA command reference:
"Parameters supported by the cell template whose TEMPLATEID is
0 can be added to the customized template. To query these
parameters, run the LST GCELLTEMPLATEPARA command or
refer to the list of parameters supported by the cell template."
The list of parameters supported by the cell template has been attached,
as shown in the following:
Solution None
Impact
Test Case ID CASE_Commercial_PR_Regression_R016C00SPC620_210
3.3.4.4 The SDCCH and BCCH cannot be configured on the

same timeslot.
Ticket
Number
Description Condition: SDCCH8 or SDCCH_CBCH is configured on the same

timeslot as the BCCH on the GRRU/MRRU/GRFU/MRFU/3900E
boards.
Symptom: The SET GTRXDEV command is successfully executed,
but the following error message is displayed:
For the GRRU, MRRU, GRFU, MRFU, or 3900E, the SDCCH cannot
be configured on the same timeslot as the BCCH.
Impact: The preceding error message is displayed although the
SDCCH and BCCH can be configured on the same timeslot.
Severity Suggestion
Root Cause The error message was added in earlier versions. With the evolution of
product versions, the restriction has been removed but the error
message is not removed accordingly.
Solution The error message has been removed.
Solution None
Impact
Test Case ID CASE_Commercial_PR_Regression_R016C00SPC620_211

Copyright Huawei
3.3.4.5 MSs are inaccurately located by using the Gb-based

Location Service (Cell ID+TA) function.
Ticket
Number
Description Condition: During location services using the Gb-based Location

Service (Cell ID+TA) function, the timing advance (TA) value based on
which the BSC calculates the MS location has a deviation of 0.5.
Symptom: The calculated MS location is not the actual MS location.
Impact: The location result cannot reflect the actual MS location,
affecting user experience.
Severity Suggestion
Root Cause When calculating the MS location based on the TA value reported by
the BTS, the BSC considers that the TA value has been rounded down.
For example, if the received TA value is 0, the BSC considers that the
measured TA value is within the range of [0,1). However, the BTS
rounds off the measured TA value before reporting it to the BSC. For
example, if the measured TA value is within the range of [0,0.5), the
BTS reports the TA value 0. Therefore, the TA value based on which the
BSC calculates the MS location has a deviation of 0.5.
Solution The BSC now subtracts 0.5 from the TA value reported by the BTS
before calculating the MS location in the preceding scenario.
Solution None
Impact
3.3.4.6 The BSC incorrectly measures counters related to

abnormal downlink TBF release.
Ticket
Number
Scenario 1: The downlink TBF is released abnormally due to N3105
overflow.
Scenario 2: The downlink TBF is released abnormally due to DTM
establishment.
Symptom:
Scenario 1: The BSC occasionally includes the values of the "A9306:

Copyright Huawei
Number of Downlink EGPRS TBF Abnormal Releases due to N3105

Overflow" and "A9106: Number of Downlink GPRS TBF Abnormal
Releases due to N3105 Overflow" counters in the values of the
"A9347: Number of Downlink EGPRS TBF Abnormal Releases due
to DTM Establishment" and "A9143: Number of Downlink GPRS
TBF Abnormal Releases due to DTM Establishment" counters,
respectively.
Scenario 2: The BSC occasionally includes the values of the "A9347:
Number of Downlink EGPRS TBF Abnormal Releases due to DTM
Establishment" and "A9143: Number of Downlink GPRS TBF
Abnormal Releases due to DTM Establishment" counters in the
values of the "A9306: Number of Downlink EGPRS TBF Abnormal
Releases due to N3105 Overflow" and "A9106: Number of Downlink
GPRS TBF Abnormal Releases due to N3105 Overflow" counters,
respectively.
Impact: The measured values of the preceding counters are
inconsistent with the actual values. It is inconvenient for users to
observe network performance.
Severity Suggestion
Root Cause Due to a BSC internal processing error, the BSC uses a random value
as the cause value for abnormal downlink TBF release in the
preceding scenarios. As a result, the measured values of the preceding
counters are occasionally incorrect.
Solution The BSC internal processing error has been rectified. The BSC now
uses the correct cause value for abnormal downlink TBF release
when measuring the preceding counters. This way, the measured
values of these counters are correct.
Impact In scenario 1, the values of the following counters increase:
A9306: Number of Downlink EGPRS TBF Abnormal Releases due
to N3105 Overflow
A9106: Number of Downlink GPRS TBF Abnormal Releases due
to N3105 Overflow
The values of the following counters decrease:
to DTM Establishment
In scenario 2, the values of the following counters increase:
The values of the following counters decrease:
to N3105 Overflow

Copyright Huawei
to N3105 Overflow
3.3.4.7 The BSC mistakenly terminates the rerouting

procedure in a cell enabled with the MOCN Shared Cell
feature.
Number
A cell is enabled with the MOCN Shared Cell feature. MOCN is short
for multi-operator core network.
The MOCN Switch parameter is set to a value other than
CLOSE(Close) and the Re-Routing Occasion parameter is set to a
value other than NOTREDIR(Not Redirect) in the SET
OTHSOFTPARA command.
The BSC receives a non-access message for an MS from the SGSN
when performing the rerouting procedure for the MS.
Symptom: The BSC terminates the rerouting procedure. The rerouting
due to timer expiration cannot be triggered for the MS.
Impact: The number of rerouting times of the MS and the probability
of selecting an appropriate core network (CN) decrease.
NOTE
Access messages sent from the SGSN to MSs are:
ATTACH ACCEPT
ATTACH REJECT
ROUTING AREA UPDATE ACCEPT
ROUTING AREA UPDATE REJECT
For details, see 3GPP TS 24.008.
Severity Suggestion
Root Cause The BSC mistakenly terminates the rerouting procedure upon receiving
a non-access message from the SGSN in the preceding scenario.
Solution In the preceding scenario, the BSC no longer terminates the rerouting
procedure to ensure that the MS can be rerouted to an appropriate CN.
Bit 6 of the BSC Reserved Parameter 4 parameter in the SET
BSCPSSOFTPARA command controls whether to enable this solution.
By default, this solution is enabled (default value: 0) for new networks.
In upgrade scenarios:
By default, this solution is disabled (default value: 1) after the BSC is
upgraded from a BSC6910 V100R015C00 version earlier than
BSC6910 V100R015C00SPC525 to the current version. By default,
this solution is enabled (default value: 0) after the BSC is upgraded
from BSC6910 V100R015C00SPC525 or later to the current version.

Copyright Huawei
To set bit 6 to 1, run the following command:

SET BSCPSSOFTPARA: BSCPSReservePara4=64;
where the value 64 (0000 0000 0000 0000 0000 0000 0100 0000 in
binary) indicates that the value of bit 6 is 1.
Set BSC Reserved Parameter 4 based on the current parameter
setting. For example, if the current value of BSC Reserved Parameter
4 is 1 (0000 0000 0000 0001 in binary), set this parameter to 65 (0000
0000 0100 0001 in binary) with bit 6 set to 1.
Solution After this solution is used, the number of rerouting times of the MS and
Impact the probability of selecting an appropriate CN increase.
Specifically, the values of the following counters increase:
R9750: Number of SGSN Selections Based on Re-Routing
A9304: Number of Failed Downlink EGPRS TBF Establishments
due to MS No Response
A9104: Number of Failed Downlink GPRS TBF Establishments due
to MS No Response
3.3.4.8 The number of activated PDCHs is unbalanced

among GUPPSs when PS traffic volumes are unbalanced
among cells.
Ticket
Number
Description Condition: Packet switched (PS) traffic volumes are unbalanced

among cells.
Symptom: The value of the R9346: Number of Dynamic PDCH
Requests Without Application Attempts Because the Number of
Activated PDCHs Reaches Board Specification counter increases.
Impact: Activated PDCHs in PS cells are unevenly distributed on
GUPPSs, affecting PS service performance.
Severity Suggestion
Root Cause The BSC does not consider the number of activated PDCHs in each PS
cell when allocating PS cells to GUPPSs. As a result, activated PDCHs
in PS cells are unevenly distributed on GUPPSs when PS traffic
volumes are unbalanced among these cells.
Solution Solution 1: The BSC balances PS cells on GUPPSs based on the
number of activated PDCHs on the GUPPSs at the specified time.
Bits 7 to 13 of the BSC Reserved Parameter 4 parameter in the
SET BSCPSSOFTPARA command controls whether to enable this
solution.
By default, this solution is disabled (default value: 0) for both new

Copyright Huawei
networks and upgrade scenarios.

When this solution is enabled, the BSC selects the GUPPSs that
need to be adjusted based on the value of bits 7 to 13 and reallocates
the PS cells between each pair of the GUPPS with the heaviest load
and the GUPPS with the lightest load. When bits 7 to 13 is not set to
0, the configurations of the Dynamic Balanced Cell Distribution
Switch and Dynamic Balanced Cell Distribution Optimization
parameters do not take effect.
SET BSCPSSOFTPARA command specifies the absolute time
when the BSC implements the preceding adjustment. Bits 20 to 24
indicates hour, and bits 14 to 19 indicates minute. When bits 20 to
24 is set to 4 and bits 14 to 19 is set to 30, the BSC implements the
preceding adjustment at 04:30:00 every day. The absolute time
ranges from 00:01 to 23:59. When bits 14 to 24 is set to 0, the BSC
implements the preceding adjustment at 02:22:22 by default.
Solution 2: The BSC performs a penalty on a cell where PDCH
application fails due to restrictions of GUPPS specifications to
decrease the number of PDCH requests in the cell. Within the
penalty time, the BSC does not attempt to convert TCHs into
PDCHs in the cell.
SET BSCPSSOFTPARA command specifies the penalty time
(unit: s). The value of bits 25 to 30 ranges from 3 (default value) to
60.When bits 25 to 30 is set to a value less than 3 or greater than 60,
the penalty time is 3s.
To set bits 25 to 30 to 31 (0000 0000 0001 1111 in binary), run the
following command:
SET BSCPSSOFTPARA: BSCPSReservePara4=1040187392;
where the value 1040187392 (0011 1110 0000 0000 0000 0000
0000 0000 in binary) indicates the value of bits 25 to 30 is 31.
Set BSC Reserved Parameter 4 based on the current parameter
setting. For example, if the current value of BSC Reserved
Parameter 4 is 1 (0000 0000 0000 0001 in binary), set this
parameter to 1040187393 (0011 1110 0000 0000 0000 0000 0000
0001 in binary) with bits 25 to 30 set to 31.
Solution 3: The BSC performs a penalty on an IP-based cell where
PDCH application fails due to restrictions of GUPPS specifications.
Within the penalty time, the BSC does not attempt to convert TCHs
into PDCHs in the cell.
SW23 of the BSC PS Reserved Switch Parameter 0 parameter in
the SET GRSVPARA command controls whether to enable this
solution.
By default, this solution is disabled (default value: 0) for both new
networks and upgrade scenarios.
When this solution is enabled, the penalty time is the same as that
used in solution 2.
Solution After solution 1 is used, PS cells will be more evenly distributed.
Impact The value of the R9346: Number of Dynamic PDCH Requests Without
Application Attempts Because the Number of Activated PDCHs

Copyright Huawei
Reaches Board Specification counter decreases.

The values of the following counters increase or remain unchanged:
AR9381: Average Number of Available EGPRS PDCHs
AR9383: Average Number of Available GPRS PDCHs
After solution 2 is used, a larger value of bits 25 to 30 indicates smaller
values of the R9341: Number of TCH to PDTCH Conversion Attempts
and R9346: Number of Dynamic PDCH Requests Without Application
Attempts Because the Number of Activated PDCHs Reaches Board
Specification counters.
After solution 3 is used, the values of the following counters decrease
in IP-based cells:
R9341: Number of TCH to PDTCH Conversion Attempts
R9346: Number of Dynamic PDCH Requests Without Application
Attempts Because the Number of Activated PDCHs Reaches Board
Specification
The values of the following counters decrease or remain unchanged:
AR9381: Average Number of Available EGPRS PDCHs
AR9383: Average Number of Available GPRS PDCHs
3.3.4.9 Users are not prompted with a message about the

parameter relationship when setting the AMR ACS[F] or
AMR ACS[H] parameter.
Number
1. The AMR ACS Collection (Full Rate) or AMR ACS Collection
(Half Rate) parameter in the SET GCELLCCAMR command is
not set to SINGLEMODE.
2. Users change the value of the AMR ACS[F] or AMR ACS[H]
parameter in the SET GCELLCCAMR command.
Symptom: The function using the coding rates specified by the AMR
ACS[F] or AMR ACS[H] parameter does not take effect.
Impact: Users are not prompted with a message about the parameter
relationship when setting the AMR ACS[F] or AMR ACS[H]
parameter. This affects parameter usability.
Severity Suggestion
Root Cause The AMR ACS[F] or AMR ACS[H] parameter is valid only if the
AMR ACS Collection (Full Rate) or AMR ACS Collection (Half
Rate) parameter is set to SINGLEMODE. No message about this
parameter relationship is displayed when users set the AMR ACS[F]
or AMR ACS[H] parameter. As a result, the function using the coding

Copyright Huawei
rates specified by the AMR ACS[F] or AMR ACS[H] parameter does

not take effect.
Solution The following message is now displayed when users change the value
of the AMR ACS[F] or AMR ACS[H] parameter in the SET
GCELLCCAMR command:
This parameter [GCELLCCAMR:ACTCDSETF] or
[GCELLCCAMR:ACTCDSETH] is valid only if
[GCELLCCAMR:ACSSETF] is set to SINGLEMODE or
[GCELLCCAMR:ACSSETH] is set to SINGLEMODE.
Solution None
Impact
3.3.4.10 The alarm location information in some

transmission alarms is insufficient.
Ticket
Number
Descriptio Condition: Transmission objects become faulty or traffic on these objects

n is congested. The following alarms and event are reported:
ALM-21501 MTP3 Signaling Link Congestion
ALM-21502 MTP3 DSP Congestion
ALM-21504 MTP3 Signaling Route Inaccessible
ALM-21505 MTP3 Signaling Link Set Unavailable
ALM-21506 MTP3 Signaling Link Faulty
ALM-21551 M3UA Link Fault
ALM-21552 M3UA Destination Entity Route Unavailable
ALM-21522 Low SCCP Setup Success Rate
EVT-22920 SCCP Subsystem Congested
Symptom: The information about the core network (CN) node
corresponding to the destination signaling point (DSP) is not contained in
the preceding alarms and event.
Impact: Users cannot determine which CN node is faulty.
Severity Suggestion
Root The alarms and event reported by the base station controller contains only
Cause the DSP information and do not contain the information about the faulty
CN node.
Solution The alarm parameter Additional Information is added to the preceding
alarms and event.
If the DSP type is A, the value of the additional information parameter
is "GSM CN Node: CN Node Index=x, Operator Index=y, Operator

Copyright Huawei
Name=z."
For other DSP types, the value of the additional information parameter
is "NULL."
Solution None
Impact
3.3.4.11 The failure cause cannot be quickly identified when

an IP continuity check fails.
Ticket
Number
Descriptio Condition: An IP continuity check whose type is single-hop bidirectional

n forwarding detection (SBFD) or address resolution protocol (ARP) is
started to detect faults.
Symptom: When an IP continuity check fails, the failure cause cannot be
quickly identified.
Impact: The existing IP continuity check mechanism cannot quickly
identify the failure cause.
Severity Suggestion
Root When an IP continuity check fails, especially the IP continuity check fails
Cause and then recovers, the maintenance function for quickly identifying the
failure cause has defects, and therefore cannot determine whether an
interface board can properly receive or transmit BFD or ARP packets.
Solution 1. When an IP continuity check fails, MAC packet capturing is triggered
automatically.
2. SBFD/ARP packets are captured by a pair of boards in active/standby
configuration.
3. The packet capturing function can be automatically started on a board
for up to five times in a day and the packet capturing duration is 30s.
Solution None
Impact
3.3.4.12 No information is available for locating the fault

when a chip of the interface processing board fails to be
initialized.
Number

Copyright Huawei
Descriptio Condition: A chip of the board is faulty.

n Symptom: Due to a hardware fault, a board fails to start up, but no
information about the faulty chip is displayed.
Impact: Faults in the following chips cannot be located: memory chip,
flash chip, CPLD logic chip, FPGA logic chip, clock chip, and
temperature and voltage monitoring chip.
Severity Suggestion
Root The board's basic input/output system (BIOS) does not record required
Cause information in the last word when a chip of the board fails to be
initialized.
Solution The board's BIOS records the number of the chip that fails to be initialized
and the returned value in the last word.
Solution None
Impact
3.4 Known Issues

3.4.1 Critical
None
3.4.2 Major
None
3.4.3 Minor
3.4.3.1 When the full MML scripts are exported and
delivered on the CME, the SET BTSPORTTS command fails to
be executed.
Trouble DTS2013042503189
Ticket
Number
Description When the Index Type parameter is set to BYNAME (By Name) and
full MML scripts are exported and delivered on the Configuration
Management Express (CME), the SET BTSPORTTS command fails to
be executed.
Severity Minor
Workaroun Workaround:
d If some timeslots on the BTS are manually allocated, run the CLR

Copyright Huawei
BTSMANUAL command to clear these timeslots.

Emergency measures:
Set the TS Object BTSINDEX and TS Object TRX No. parameters to
appropriate values. Then, deliver and run the SET BTSPORTTS
command again.
Domain None
Progress The cause of this issue has been found and the issue will be resolved in a
later version.
3.4.4 Suggestion
None

Copyright Huawei
Release Notes V100R016C00SPH609
4 Changes from
V100R016C00SPH609
4.1 Change Summary

unchanged in BSC6910V100R016C00SPH609.
Hardware
BSC6910V100R016C00SPH609.
Features
Compared with those in BSC6910V100R016C00SPH608 features and functions remain
Resolved Issues
Compared with those in BSC6910V100R016C00SPH608, 0 critical issues, 2 major issues, 0
BSC6910V100R016C00SPH609.


Copyright Huawei

functions remain unchanged in BSC6910V100R016C00SPH609. For details about MML
functions remain unchanged in BSC6910V100R016C00SPH609. For details about
Fault management
remain unchanged in BSC6910V100R016C00SPH609. For details about alarm and event
License management
remain unchanged in BSC6910V100R016C00SPH609. For details about license
document templates remain unchanged in BSC6910V100R016C00SPH609. For details about
(V100R016C00_03)(HDX)-EN.

performance.
4.1.2 Hardware
New Hardware
None
Modified Hardware
None
4.1.3 Features
Compared with BSC6910V100R016C00SPH608, there are no feature changes in
BSC6910V100R016C00SPH609.

Copyright Huawei

BSC6910V100R016C00SPH609 but unresolved in BSC6910V100R016C00SPH608:
Issue description
Severity
Solution impact
Parameter control
(Optional) RAT
V100R016C00SPH609.xls, or see the V100R016C00SPH609 vs V100R016C00SPH608 sheet
BSC6910V100R016C00SPH609.

functions remain unchanged in BSC6910V100R016C00SPH609. For details about changes to
Changes.

functions remain unchanged in BSC6910V100R016C00SPH609. For details about counter

remain unchanged in BSC6910V100R016C00SPH609. For details about changes to alarms

remain unchanged in BSC6910V100R016C00SPH609. For details about license changes, see


Copyright Huawei
4.2 Feature Changes

4.2.1 New Features
None

None

None
4.3 Resolved Issues

4.3.1 Critical
None
4.3.2 Major
4.3.2.1 The WebLMT displays a message "Internal error" if
the file name of an uploaded file contains Chinese
characters in batch configuration.
Ticket
Number
Description Condition: A user uses the batch configuration function of the Web
LMT. The file name of an uploaded file or a file that has been
decrypted contains Chinese characters.
Symptom: The Web LMT displays a message "Internal error".
Impact: The batch configuration function fails.
Severity Major
Root Cause The Web LMT and interconnected NE adopt inconsistent character
encoding schemes. Specifically, if the file name of an uploaded file
contains Chinese characters in batch configuration, the Web LMT
notifies the interconnected NE of the file name in UTF-8, whereas the
interconnected NE reads the file name in GB2312.
Solution In batch configuration, the Web LMT now converts the file name of
an uploaded file to codes supported by the language in use before
notifying the interconnected NE.
Solution None
Impact
Test Case ID CASE_Commercial_PR_Regression_R016C00SPH609_001

Copyright Huawei
4.3.2.2 Multicast configuration fails after an SCU board has

been running for an excessively long period of time.
Number
An SCU board in a subrack (subrack A) has been running for more
than 497 days.
The total number of MPS and EPSs exceeds 2.
SCU boards in a subrack (subrack B) that is not directly connected
to subrack A reset.
Symptom: After the SCU boards in subrack B restart, multicast
configuration of subrack A cannot be added to the SCU boards in
subrack B.
Impact: Inter-subrack services are interrupted.
Severity Major
Root Cause After arithmetic overflow occurs on the global variable (TICK value)
recording the running period of the SCU board subrack A, if the SCU
boards in subrack B are switched over, the SCU board in subrack A
incorrectly performs calculation between the current TICK value and
the TICK value obtained during the previous multicast configuration.
In this situation, the conditions for sending inter-subrack multicast
configuration messages are not meet. As a result, multicast
configuration of subrack A cannot be added to the SCU boards
subrack B.
Solution The SCU boards now correctly perform calculation between the
current TICK value and the TICK value obtained during the previous
multicast configuration in the preceding scenario. This ensures that
the calculated result is correct when arithmetic overflow occurs on the
TICK value.
Solution None
Impact
4.3.3 Minor
None
4.3.4 Suggestion
None

Copyright Huawei
4.4 Known Issues

4.4.1 Critical
None
4.4.2 Major
None
4.4.3 Minor
be executed.
Ticket
Number
be executed.
Severity Minor
Emergency measures:
command again.
Domain None
later version.
4.4.4 Suggestion
None

Copyright Huawei
5 Changes from
V100R016C00SPH608
5.1 Change Summar

Hardware
BSC6910V100R016C00SPH608.
Features
Compared with those in BSC6910V100R016C00SPH605, 0 features have been added, 3
features have been modified, and 0 features have been deleted in
BSC6910V100R016C00SPH608.
Resolved Issues
BSC6910V100R016C00SPH608.

Copyright Huawei


Fault management
License management
(V100R016C00_03)(HDX)-EN.

performance.
5.1.2 Hardware
New Hardware
None
Modified Hardware
None

Copyright Huawei
5.1.3 Features
Compared with BSC6910V100R016C00SPH605, there are no feature changes in
BSC6910V100R016C00SPH608.

Compared with BSC6910V100R016C00SPH605, there are no issues resolved in
BSC6910V100R016C00SPH608.

Changes.




5.2 Feature Changes

5.2.1 New Features
None

None

Copyright Huawei

None
5.3 Resolved Issues

5.3.1 Critical
None
5.3.2 Major
None
5.3.3 Minor
None
5.3.4 Suggestion
None
5.4 Known Issues

5.4.1 Critical
None
5.4.2 Major
None
5.4.3 Minor
be executed.
Ticket
Number
be executed.
Severity Minor

Copyright Huawei
d
If some timeslots on the BTS are manually allocated, run the CLR
Emergency measures:
command again.
Domain None
later version.
5.4.4 Suggestion
None

Copyright Huawei
6 Changes from
V100R016C00SPH605
6.1 Change Summary

Hardware
BSC6910V100R016C00SPH605.
Features
Compared with those in BSC6910V100R016C00SPH602, 0 features have been added, 3
BSC6910V100R016C00SPH605.
Resolved Issues
BSC6910V100R016C00SPH605.

Copyright Huawei


Fault management
License management
(V100R016C00_03)(HDX)-EN.

performance.
6.1.2 Hardware
New Hardware
None
Modified Hardware
None

Copyright Huawei
6.1.3 Features
BSC6910V100R016C00SPH602 to BSC6910V100R016C00SPH605:
Change type
Feature description
(Optional) RAT
BSC6910V100R016C00SPH605.

BSC6910V100R016C00SPH605 but unresolved in BSC6910V100R016C00SPH602:
Issue description
Severity
Solution impact
Parameter control
(Optional) RAT
BSC6910V100R016C00SPH605.

Changes.

Copyright Huawei




6.2 Feature Changes

6.2.1 New Features
None

6.2.2.1 Support for Changing the RXU Board Type on GSM
Networks
Description
This feature incorporates a new command for users to change the RXU board type, thereby
facilitating the replacement of RXU boards.
Implementation
The MOD BTSRXUBRDQUICK command is added for users to change the following
parameters for an RXU board:
Board Type
RXU Specification
RXU Name
The value of the Board Type parameter can be changed only between MRRU and GRRU or
between MRFU and GRFU. Before running this command, ensure that TRXs on the RXU
board are not activated.

Copyright Huawei

None
Impact on NEs
None
Impact on Hardware
None

None

None
Added the MOD BTSRXUBRDQUICK command.
None
None

None
Related Operations
None

DTS: DTS2014060603718
Feature ID
GBFD-111202
6.2.2.2 Added the G_NIC Command Group for Encapsulating

All Commands for the NIC Function
Description
The G_NIC command group is added as the default command group to encapsulate all
commands for the NIC function. Customized users can perform the NIC function by adding

Copyright Huawei
this command group without specifying a user-defined command group. This simplifies user
operations.
Implementation
All commands for the NIC function are encapsulated in the G_NIC command group.
Customized users can use this command group to perform the NIC function. Operations
related to this command group are as follows:
The Command Group parameter in the ADD OP command can be set to G_NIC when
this command is executed to add a customized user.
The Command Group parameter in the MOD OP command can be set to G_NIC when
this command is executed to modify a customized user.
The Command Group parameter in the LST OP command can be set to G_NIC when
this command is executed to query an operator's information by command group.
The Command Group parameter in the LST CCG command can be set to G_NIC
when this command is executed to query the commands in this command group.
The Command Group parameter in the LST CCGN command can be set to G_NIC to
query the name of this command group.

None
Impact on NEs
None
Impact on Hardware
None

None

None
Added the value G_NIC to the Command Group parameter in the ADD OP, MOD
OP, LST OP, LST CCG, and LST CCGN commands.
None
None

None

Copyright Huawei
Related Operations
None

CR-0000072490
Feature ID
None
6.2.2.3 Enhanced Anti-Attack Protection for Fragmented

Packets Received by the Interface Board
Description
The protection against fragmented packet attack has been optimized for interface boards
POUc/FG2c/FG2d/GOUc/GOUd/GOUe to prevent the impact of fragmented packet attack on
services. It is recommended that this feature be enabled in scenarios where there are a great
number of fragmented packets on the transmission network.
Implementation
This feature implements protection against fragmented packet attack by limiting the number
of fragmented packets received by the preceding interface boards 256. If the number of
fragmented packets required for assembling a complete packet is greater than 256, the packet
assembly fails and these fragmented packets are discarded.
BIT0 under the RSVDSW1 parameter in the SET DEVRSVDPARA command controls
whether to enable the function of limiting the number of fragmented packets received by
interface boards. When this function is enabled, the number of fragmented packets received
by interface boards is limited. When function is disabled, the number of fragmented packets
received by interface boards is not limited. By default, this function is disabled (default value:
1) for both new networks and upgrade scenarios.

None
Impact on NEs
None
Impact on Hardware
None

None

Copyright Huawei

None
BIT0 under the RSVDSW1 parameter in the SET DEVRSVDPARA command is now
used.
None
None

None
Related Operations
Run the following command to enable the function of limiting the number of fragmented
packets received by interface boards:
SET DEVRSVDPARA: RSVDSW1=BIT0-0;
Run the following command to disable the function of limiting the number of fragmented
packets received by interface boards:

DTS: DTS2014061603298
Feature ID
None

None
6.3 Resolved Issues

6.3.1 Critical
None

Copyright Huawei
6.3.2 Major
6.3.2.1 MO short messages are prohibited when the Short
Message Downlink Disabled parameter is set to YES(Yes).
Number
Description Condition: The Short Message Downlink Disabled parameter is set

to YES(Yes). A mobile originated (MO) short message service (SMS)
is initiated.
Symptom: The BSC prohibits the MO short messages.
Impact: The MO SMS fails.
Severity Major
Root Cause When the Short Message Downlink Disabled parameter is set to
YES(Yes), upon receiving a CP ACK message from the MSC, the
BSC returns a reject message to the MSC without distinguishing
between MO and mobile terminated (MT) short messages.
Solution When Short Message Downlink Disabled is set to YES(Yes), the
BSC now allows MO short messages to be sent over standalone
dedicated control channels (SDCCHs).
Solution None
Impact
Test Case CASE_Commercial_PR_Regression_R016C00SPH605_201
6.3.2.2 A GSM/UMTS MS in GSM-only mode fast reselects to

a UMTS FDD cell after releasing a call.
Ticket
Number
The BSC is enabled with the Fast WCDMA Reselection at 2G CS
Call Release feature.
The BSC is enabled with the BSC supporting Blind Search feature
and configured with UMTS FDD frequencies.
Symptom:
A GSM/UMTS MS in GSM-only mode fast reselects to a UMTS FDD
cell after releasing a call.
Impact:
MSs that were expected to camp on a GSM cell camp on a UMTS
FDD cell.
Severity Major

Copyright Huawei
Root Cause In the preceding scenario, the BSC does not check the network support
capability of the MS. As a result, the Channel Release message
contains UMTS FDD frequencies when a call is released.
Solution The BSC now checks the network support capability of an MS before
containing UMTS FDD frequencies in the Channel Release message.
The BSC contains UMTS FDD frequencies in the Channel Release
message only if the BSC determines that the value of the "UMTS FDD
Radio Access Technology Capability" information element (IE) in
Classmark 3 reported by the MS is "UMTS FDD supported".
Solution After this solution is used, a GSM/UMTS MS in GSM-only mode
Impact reselects to a GSM cell in the preceding scenario.
6.3.2.3 The measured values of counters under the

"Incoming Inter-RAT Inter-Cell Handover Measurement per
Cell" and "SRVCC Handover Measurement per Cell"
measurement units are incorrect.
Number
Description Condition: The source cell ID type (identified by the cell-

identification-discriminator IE) in the handover request message for an
incoming UMTS-to-GSM inter-cell handover is service area identifier
(SAI). The MCC and MNC in the SAI are consistent with those for
external neighboring LTE cells configured on the BSC side.
Symptom: The BSC includes the incoming UMTS-to-GSM inter-cell
handovers in the "SRVCC Handover Measurement per Cell"
measurement unit rather than the "Incoming Inter-RAT Inter-Cell
Handover Measurement per Cell" measurement unit.
Impact: Counter measurements are incorrect and therefore
inaccurately reflect network performance.
Severity Major
Root Cause Both UMTS-to-GSM and LTE-to-GSM inter-cell handover requests

contain SAI. If the MCC and MNC for neighboring UMTS cells are
consistent with those for neighboring LTE cells, the BSC
preferentially includes these handovers in the "SRVCC Handover
Measurement per Cell" measurement unit.
Solution The BSC now interprets an incoming BSC handover request as an
SRVCC handover request when all of the following conditions are
met:
The SRVCC Handover Allowed parameter in the SET
GCELLHOBASIC command is set to YES(Yes).

Copyright Huawei
The source cell ID type in the incoming BSC handover request is

SAI.
The values of lte sai mcc, lte sai mnc, lte sai lac, and lte sai sac for
the source cell carried in the incoming BSC handover request
message are consistent with those configured on the BSC side.
Otherwise, the BSC interprets the incoming BSC handover request as
an incoming UMTS-to-GSM inter-cell handover request.
Impact The values of counters in the "Incoming Inter-RAT Inter-Cell
Handover Measurement per Cell" measurement unit increase.
The values of counters in the "SRVCC Handover Measurement per
Cell" measurement unit decrease.
6.3.2.4 TCHH allocation fails when TCH rate adjustment is

not allowed and the Half Rate Speech (per TRX) and AMR HR
(per TRX) license control items do not coexist.
Number
The TCH Rate Adjust Allow parameter in the SET GTRXDEV
command is set to NO(No).
The Half Rate Speech (per TRX) and AMR HR (per TRX) license
control items do not coexist, that is, either of the following
conditions is met:
The licensed value of the Half Rate Speech (per TRX) license
control item is not 0, and it is greater than or equal to the usage
value. The licensed value of the AMR HR (per TRX) license
control item is 0, or it is less than the usage value.
The licensed value of the AMR HR (per TRX) license control
item is not 0, and it is greater than or equal to the usage value.
The licensed value of the Half Rate Speech (per TRX) license
control item is 0, or it is less than the usage value.
Symptom: The value of the RM3278: Successful TCH Seizures
(Traffic Channel) (TCHH) counter decreases.
Impact: Half-rate traffic channel (TCHH) allocation fails.
Severity Major
Root Cause In the preceding scenario, the BSC mistakenly determines that TCHHs
can be allocated only when both the Half Rate Speech (per TRX) and
AMR HR (per TRX) license control items are available.
Solution The BSC can now allocate TCHHs to an MS when the Half Rate
Speech (per TRX) or AMR HR (per TRX) license control item is

Copyright Huawei
available and the MS supports the corresponding speech version in the

preceding scenario.
Solution After this solution is used, the values of the following counters
Impact increase:
RM3278: Successful TCH Seizures (Traffic Channel) (TCHH)
K3034: TCHH Traffic Volume
K3043: TCH Seizure Success Rate
RCA313: Assignment Success Rate
The value of the K3045: Congestion Rate on TCH (All Channels Busy)
counter decreases.
6.3.3 Minor
6.3.3.1 Frequency scanning results cannot be correctly
displayed if the NE reports more than 2500 items.
Ticket
Number
Description Condition: The Query Frequency Scan function is used on the Web
LMT, and the NE reports more than 2500 entries.
Symptom: The Query Frequency Scan function cannot be performed.
Impact: Frequency scanning results cannot be correctly displayed.
Severity Minor
Root Cause The Web LMT requests for frequency scanning results every 10s, and
the NE reports 1500 or less entries at a time. The Web LMT compares
the newly obtained data with existing data, and then displays the new
entries. When there are more than 2500 entries, the Query Frequency
Scan function cannot be performed.
Solution Extra entries cannot be displayed on the Web LMT, and the earlier
data will be cleared upon each data analysis. Only the latest data is
displayed, 1500 entries for at most 50 frequencies.
Solution This solution effectively increases the information update speed.
Impact

Copyright Huawei
6.3.3.2 Synchronization between the controller and the

U2000/CME has not been performed for a long time because
configuration synchronization times out for several times.
Number
Description Condition: When the EXP CFGMML command is being executed, the
command for exporting the data for configuration synchronization on the
U2000/CME is also being executed.
Symptom: Execution of the command for exporting the data for
configuration synchronization on the U2000/CME times out for several
times. As a result, the synchronization between the controller and the
U2000/CME cannot be performed for a long time.
Impact: The controller data is not synchronized to the U2000/CME in a
timely manner.
Severity Minor
Root Cause When the EXP CFGMML command is being executed, the controller
receives the command for exporting the data for configuration
synchronization delivered by the U2000 and CME. Execution of the
EXP CFGMML command is too slow and blocks execution of the
command for exporting the data for configuration synchronization. As a
result, execution of the command for exporting the data for
configuration synchronization times out and a new full synchronization
is triggered. In this situation, the problem persists for a long time.
Solution If one command for exporting data, such as EXP CFGMML and
EXP CFGBCP is being executed, re-execution of the EXP
CFGMML or EXP CFGBCP command will be rejected. If the
command for exporting data for configuration synchronization
delivered by U2000/CME is being executed, re-execution of the EXP
CFGBCP command will be rejected. This implementation does not
take effect if the EXP CFGMML or EXP CFGBCP command is
executed periodically.
If the message carrying the command for exporting the data for
configuration synchronization is in the queue during execution of the
EXP CFGMML or EXP CFGBCP command, configuration data
between the controller and the U2000/CME is synchronized after
execution of the EXP CFGMML or EXP CFGBCP command is
complete or times out.
Solution If one EXP CFGMML command is being executed, execution of the
Impact EXP CFGMML or EXP CFGBCP command will be rejected and
the error message "Please try again later as the EXP CFGMML
command is being executed." is displayed.
If one EXP CFGBCP command is being executed, execution of the
EXP CFGMML or EXP CFGBCP command will be rejected and
the error message "Please try again later as the EXP CFGBCP
command is being executed." is displayed.
If one command for exporting data for configuration synchronization
delivered by the U2000/CME is being executed, execution of the

Copyright Huawei
EXP CFGBCP command will be rejected and the error message

"The export command for configuration synchronization on the
U2000/CME is being executed. Please try again later." is displayed.
6.3.3.3 The POUc/FG2d/FG2c/GOUd/GOUc board incorrectly

reports ALM-20280 Board Temperature Abnormal.
Trouble iCare: 2572077, 2572059, and 2572067
Number
Description Condition: The CPU temperature sensor reports incorrect temperature.

Symptom: ALM-20280 Board Temperature Abnormal is reported.
Impact: The fan box runs at full speed, which does not affect services.
Severity Minor
Root Cause A board has three temperature monitoring points. If the temperature of
any of the three temperature monitoring points exceeds the preset
threshold, ALM-20280 Board Temperature Abnormal is reported. Due to
the incorrect temperature reported by the CPU temperature sensor,
ALM-20280 Board Temperature Abnormal is reported when the board
temperature is within the normal range.
Solution ALM-20280 Board Temperature Abnormal is now reported when the
temperatures of two temperature monitoring points exceed the preset
threshold.
Solution None
Impact
6.3.3.4 The DSP GPS command output is incorrect.

Ticket
Number
n 1. V100R016C00SPC600 is used.
2. The DSP GPS command is executed when the GPS is normal.
Symptom: ALM-20243 Board Hardware Fault whose Alarm Cause is
GPS Card Fault is not reported. However, the DSP GPS command
output indicates Gps out of position.
Impact:The DSP GPS command output is inconsistent with the actual
conditions.

Copyright Huawei
Severity Minor
Root Cause The redundancy fields are deleted from the message structure of the DSP
GPS command to optimize the memory on the clock board in
V100R016C00SPC600. As a result, the message structure on the clock
board becomes inconsistent with that on the OMU board, causing the
DSP GPS command to be incorrectly parsed.
Solution Redundancy fields are also deleted from the message structure of the
DSP GPS command on the OMU board to ensure consistent message
structure on the OMU board and the clock board. This way, the DSP
GPS command can be correctly parsed.
Solution None
Impact
6.3.4 Suggestion
6.3.4.1 The permissions of local users are lost when the BSC
database is abnormal.
Number
Descriptio Condition: The connection between the BSC and the U2000 is normal. A
n local user logs in to the FTP server when the BSC database is abnormal.
Symptom: After the local user logs in to the LMT, a message is displayed
indicating that the local user has no permission to execute MML
commands.
Impact: The permissions of the local user are lost. As a result, the local
user cannot execute MML commands properly.
Severity Suggestion
Root A defect exists in the FTP login of a local user. Due to the defect,
Cause information about the local user fails to be obtained during the login if the
BSC database is abnormal. In this case, the BSC grants the minimum
permissions to the local user.
Solution During the authentication of an FTP login of a local user, if information
about the local user fails to be obtained due to database exceptions, the
BSC now stops the login and returns a message indicating the login
failure.
Solution The permissions of local users are not affected even if the BSC database is
Impact abnormal.

Copyright Huawei
6.3.4.2 Instantaneous traffic is too heavy after the FTP

upload and download performance is optimized.
Ticket
Number
Descriptio Condition: The base station controller works as an FTP server to upload
n and download files.
Symptom: Instantaneous traffic is too heavy during file upload and
download.
Impact: Traffic on the base station controller's Ethernet adapters is
congested. As a result, data transmission becomes slow and some packets
are lost.
Severity Suggestion
Root After the FTP upload and download performance is optimized, the base
Cause station controller does not perform flow control over instantaneous traffic.
Solution Flow control is now performed over FTP transmission to ensure that
traffic is smoothly processed during file upload and download. In this
way, data is transmitted symmetrically.
Solution None
Impact
6.3.4.3 The value of a single bit in the FPGA of the

FG2d/GOUd/POUc/FG2c/GOUc board is changed and the
FPGA cannot recover through self-healing.
Ticket
Number
Descriptio Condition: The value of a single bit in the FPGA of the

n FG2d/GOUd/POUc/FG2c/GOUc board is changed.
Symptom: The board does not perform self-healing on the changed bit of
the FPGA.
Impact: Internal data of the FPGA is incorrect, which affects services.
Severity Suggestion
Root The FG2d/GOUd/POUc/FG2c/GOUc board does not perform self-healing

Cause when the value of a single bit in the FPGA is changed.
Solution The FG2d/GOUd/POUc/FG2c/GOUc board rectifies the error when the

value of a single bit in the FPGA is changed.
The BIT8 of the RSVDSW2 parameter in the SET DEVRSVDPARA
command is used to control this solution. By default, this solution is

Copyright Huawei
enabled (default value: 1) for both new networks and upgrade scenarios.
When this solution is enabled, the FG2d/GOUd/POUc/FG2c/GOUc board
rectifies the error if the value of a single bit in the FPGA is changed.
When this solution is disabled, the FG2d/GOUd/POUc/FG2c/GOUc
board does not rectify the error if the value of a single bit in the FPGA is
changed.
To enable this solution, run the following command:
To disable this solution, run the following command:
Solution None
Impact
6.4 Known Issues

6.4.1 Critical
None
6.4.2 Major
None
6.4.3 Minor
be executed.
Ticket
Number
be executed.
Severity Minor
Emergency measures:

Copyright Huawei

command again.
Domain None
later version.
6.4.4 Suggestion
None

Copyright Huawei
BSC6910 GSM 7 Changes from V100R016C00SPC600 to
7 Changes from
V100R016C00SPC600 to
V100R016C00SPH602
7.1 Change Summary

Compared with those in BSC6910V100R016C00SPC600, capacity and performance remain
Hardware
Compared with that in BSC6910V100R016C00SPC600, hardware remains unchanged in
BSC6910V100R016C00SPH602.
Features
Compared with those in BSC6910V100R016C00SPC600, 0 features have been added, 4
BSC6910V100R016C00SPH602.
Resolved Issues
Compared with those in BSC6910V100R016C00SPC600, 0 critical issues, 6 major issues, 3
BSC6910V100R016C00SPH602.

Copyright Huawei


Compared with those in BSC6910V100R016C00SPC600, configuration management
Compared with those in BSC6910V100R016C00SPC600, performance management
Fault management
Compared with those in BSC6910V100R016C00SPC600, fault management functions
License management
Compared with those in BSC6910V100R016C00SPC600, license management functions
Compared with those in BSC6910V100R016C00SPC600, document organization and
(V100R016C00_02)(HDX)-EN.

performance.
Compared with those in BSC6910V100R016C00SPC600, capacity and performance remain
7.1.2 Hardware
New Hardware
None
Modified Hardware
None

Copyright Huawei
7.1.3 Features
BSC6910V100R016C00SPC600 to BSC6910V100R016C00SPH602:
Change type
Feature description
(Optional) RAT
V100R016C00SPH602.xls, or see the V100R016C00SPH602 vs V100R016C00SPC600 sheet
BSC6910V100R016C00SPH602.

BSC6910V100R016C00SPH602 but unresolved in BSC6910V100R016C00SPC600:
Issue description
Severity
Solution impact
Parameter control
(Optional) RAT
V100R016C00SPH602.xls, or see the V100R016C00SPH602 vs V100R016C00SPC600 sheet
BSC6910V100R016C00SPH602.

Compared with those in BSC6910V100R016C00SPC600, configuration management
Changes.

Copyright Huawei

Compared with those in BSC6910V100R016C00SPC600, performance management

Compared with those in BSC6910V100R016C00SPC600, fault management functions remain
unchanged in BSC6910V100R016C00SPH602. For details about changes to alarms and
events, see 8.3 Alarm Changes and 8.4 Event Changes.

Compared with those in BSC6910V100R016C00SPC600, license management functions

7.2 Feature Changes

7.2.1 New Features
None

7.2.2.1 Immediately Notifying the Peer End of the Receive
Buffer Space Update
Description
When the remaining space of the receive buffer over an SCTP link is changed from 0 to a
value other than 0, the base station controller immediately notifies the peer end of the buffer
space update.
Implementation
The base station controller now sends the SACK packet upon a buffer space update to notify
the peer end of the update, regardless of whether the peer end sends a detection packet.
SW15(SwPara15) of Reserved Switch Parameter1in the SET TNRSVDPARA command
controls whether to enable this solution. By default, this solution is disabled (default value: 0)
for both new networks and upgrade scenarios.

None

Copyright Huawei
Impact on NEs
None
Impact on Hardware
None

None

None
None
None
None

None
Related Operations
To enable this solution, run the following command:
SET TNRSVDPARA: RSVDSW1=SW15-1;
To disable this solution, run the following command:
SET TNRSVDPARA: RSVDSW1=SW15-0;

DTS2014051201678
Feature ID
None
7.2.2.2 Upgrade Tool Supporting Risk Check Before an

Upgrade
Description
With this feature, the upgrade tool supports the risk check function before an upgrade. This
feature enables the upgrade tool to:
Automatically check the running status of the BSC before the upgrade.

Copyright Huawei
Display check reports.

Remind users to rectify risks before the upgrade.
During a U2000-based upgrade of the BSC, the upgrade tool does not support the risk check function.
Implementation
The upgrade tool provides the Risk check option, as shown in the following figure.
If this option is selected:

The Pre-upgrade button changes to the Risk check button.
When uploading the NE software installation package, users also need to upload the
risk check package corresponding to the NE software version.
Before the pre-upgrade, the upgrade tool automatically performs risk check and
generates a check report.
If the check report only includes passed items (green), users can perform subsequent
upgrade operations.
If the check report includes warning items (yellow), the running of the BSC to be
upgraded has potential risks but has no critical impacts on the upgrade. In this
situation, users can perform subsequent upgrade operations.
If the check report includes failed items (red), the running of the BSC to be upgraded
has critical risks and may cause upgrade failures. In this situation, users are not
allowed to perform subsequent upgrade operations. Instead, these risks must be
eliminated before the upgrade.
If this option is deselected, the upgrade tool does not perform risk check before the
upgrade. Instead, it implements the upgrade following the original procedure.

None
Impact on NEs
None
Impact on Hardware
None

Copyright Huawei

None

None
None
None
None

None
Related Operations
1. Contact Huawei engineers who can obtain the risk check package corresponding to the
BSC version by performing the following operation (BSC6910 V100R016C00SPH602 is
used as an example):
1. Access http://support.huawei.com/.
2. After a successful login, choose Software Center > Version Software > Wireless
Product Line > SingleRAN > MBSC > BSC6910 > BSC6910 V100R016 > BSC6910
V100R016C00SPH602.
3. Download BSC6910 V100R016C00SPH602 Upgrade Risk Checking Package-EN.
2. Select the Risk check option on the upgrade tool and upload the risk check package.

DTS: DTS2014052200999
Feature ID
None
7.2.2.3 Removed the FTP Text Box from the Batch

Configuration Module
Description
The FTP text box is removed from the batch configuration module.

Copyright Huawei
Implementation
Under circumstances of keeping the batch configuration function in BSC Maintenance
module, in order to reduce user operation, the FTP Server IP, FTP User Name, and FTP
Password text boxes are deleted and the input operation is simplified.
The LST OMUAREA command is added to the GUI authorization item for batch
configuration. After a user-defined command group is configured with the GUI authorization
item for batch configuration, user-defined users bound to the command group have execute
permission for the LST OMUAREA command.
This feature is involved in a BSC6910 V100R016 upgrade from a version earlier than
BSC6910 V100R016C00SPH602 to BSC6910 V100R016C00SPH602.

None
Impact on NEs
None
Impact on Hardware
None

None

Impact on license: none
Impact on configuration management: none
Impact on performance management: none
Impact on fault management: none

None
Related Operations
None

REQ211851
Feature ID
None

Copyright Huawei
7.2.2.4 Support for Feature-based Information Display in the

LST LICENSE Command Output
Description
Besides the existing file-based information display, the LST LICENSE command supports
the feature-based information display. Specifically, the detailed parameter information queried
from the license file can be displayed by feature in the command output. In this way, users can
query detailed information about features that have been requested.
Implementation
In the LST LICENSE command, the optional parameter Display Mode is added. When
Display Mode is set to Feature Mode, the detailed parameter information is displayed by
feature in the command output. The specific information includes the authorized values of the
permanent and trial license items and the expiration date of each feature.

None
Impact on NEs
None
Impact on Hardware
None

None

Impact on license management: none
Impact on configuration management: none
Impact on performance management: none
Impact on fault management: none

None
Related Operations
None

CR-0000069393

Copyright Huawei
Feature ID
None

None
7.3 Resolved Issues

7.3.1 Critical
None
7.3.2 Major
7.3.2.1 EVT-22921 Unconfigured Circuits over A Interface in
the BSC is frequently reported.
Number
Description Condition: The POUc board is configured as the A interface board and
the DPUf board is configured for the BSC. The BSC local switching is
enabled.
Symptom: EVT-22921 Unconfigured Circuits over A Interface in the
BSC is frequently reported.
Impact: A large number of EVT-22921 is reported on the alarm
console. This does not affect service access.
Severity Major
Root Cause When triggering the BSC local switching restoration procedure for
services in the preceding scenario, the BSC checks whether the circuit
identification code (CIC) used by services has been configured for the
BSC. However, the CIC checked by the BSC is incorrect. As a result,
the BSC considers that the CIC has not been configured and reports
EVT-22921.
Solution The BSC now uses a correct CIC to check whether it is configured in
the preceding scenario.
Solution None
Impact

Copyright Huawei
7.3.2.2 The number of abnormal TBF releases due to DTM

establishments is incorrectly measured.
Ticket
Number
Description Condition: In a cell that is enabled with DTM and has DTM-capable
MSs, the BSC performs either of the following operations:
Deactivates the cell and then reactivates it.
Removes the cell and then adds it again.
Symptom:
The values of the following DTM-related counters decrease:
A9242:Number of Uplink EGPRS TBF Abnormal Releases due to DTM
Establishment
A904A:Number of Uplink GPRS TBF Abnormal Releases due to DTM
Establishment
A9347:Number of Downlink EGPRS TBF Abnormal Releases due to
DTM Establishment
A9143:Number of Downlink GPRS TBF Abnormal Releases due to
DTM Establishment
The values of the following TBF call drop rate-related counters
increase:
A9306:Number of Downlink EGPRS TBF Abnormal Releases due to
N3105 Overflow
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)
A9006:Number of Uplink GPRS TBF Abnormal Releases due to N3101
Overflow (MS No Response)
A9207:Number of Uplink EGPRS TBF Abnormal Releases due to
N3103 Overflow (MS No Response)
A9007:Number of Uplink GPRS TBF Abnormal Releases due to N3103
Overflow (MS No Response)
Impact: Network performance cannot be accurately reflected.
Severity Major
Root Cause In a DTM-enabled cell, if an MS initiates CS services while processing
PS services, its TBF will be abnormally released, as described in 3GPP
TS 43.055. In this situation, the BSC counts this abnormal TBF release
in corresponding TBF call drop rate-related counters. To differentiate
such abnormal TBF releases from abnormal TBF releases caused by
poor Um interface quality and accurately reflect the network status, the
BSC is supposed to actively release the ongoing PS services and count
the described abnormal TBF release in corresponding DTM-related
counters.
However, due to an internal interface error, the BSC neither actively

Copyright Huawei
releases the ongoing PS services nor counts that abnormal TBF release
in corresponding DTM-related counters. Instead, the BSC counts that
abnormal TBF release in corresponding TBF call drop rate-related
counters.
Solution In the given situation, the BSC now uses the correct interface to actively
release the current TBF and counts the abnormal TBF release in
corresponding DTM-related counters.
Solution After this solution is used, the values of the preceding DTM-related
Impact counters increase and those of the preceding TBF call drop rate-related
counters decrease.
7.3.2.3 The NSVL on the Gb interface becomes faulty due to

intermittent transmission interruption over the Gb interface
after an SCU switchover.
Number
Description Condition: After the active and standby SCU boards are switched over,
transmission over the Gb interface carried by an EXOUa board is
interrupted. More than 30s later, the transmission recovers.
Symptom: The Network Service Virtual Link (NSVL) carried on the
EXOUa board becomes faulty. ALM-22044 NSVL Faulty is reported
and cannot be cleared.
Impact: The NSVL on the EXOUa board becomes faulty.
Severity Major
Root Cause After SCU boards are switched over, the Gb resource status on the
EXOUa board is not backed up when the standby SCU board enters the
active state. Therefore, transmission over the Gb interface is interrupted
and resources on the Gb interface are requested again. However, the
requested resources conflict with the resources in use. As a result, the
NSVL becomes faulty.
Solution The Gb resource status on the EXOUa board is now backed up when the
standby SCU board enters the active state. This prevents resource
collision after the SCU board switchover.
Solution None
Impact

Copyright Huawei
7.3.2.4 Cell information cannot be displayed in the cell

performance monitoring interface.
Number
Description Condition: Open GSM Cell Performance Monitor.

Symptom: No corresponding information about CellID.
Impact: Corresponding information about CellID is not available for
users.
Severity Major
Root Cause The cell performance mentoring function in the earlier version does
not incorporate the display of cell IDs.
Solution The CellID column is now added to the cell performance monitoring
interface.
Solution None
Impact
7.3.2.5 Users cannot log in to the WebLMT on the PC where

JRE of a specific version is installed.
Ticket
Number
Descripti Condition: Users attempt to log in to the WebLMT on the PC where the
on installed Java runtime environment (JRE) version (JRE 1.7.0.0 for
example) does not match the WebLMT.
Symptom: Users cannot log in to the WebLMT.
Impact: Users cannot use the WebLMT.
Severity Major
Root It is good practice to install the latest version (JRE 1.7.0.55) among JRE
Cause 1.7 series versions on the PC. Users are prohibited from accessing the
WebLMT on the PC where the installed JRE version does not match the
WebLMT. Besides, the WebLMT login page provides a download link for
JRE 1.6.0.26. If users install JRE 1.6.0.26 without uninstalling JRE 1.7.0.0
first, JRE 1.7.0.0 is still running on the PC.
Solution The WebLMT login page now provides a download link for JRE 1.7.0.55.
Besides, users are allowed to access the WebLMT on the PC where the
installed JRE version does not match the WebLMT. In this case, a message
is displayed indicating a possible compatibility problem.
Solution Some functions of the WebLMT are unavailable if the installed JRE version

Copyright Huawei
Impact does not match the WebLMT.
7.3.2.6 The High-Risk Command List in MML Command

Reference includes some non-risky commands.
Ticket
Number
Descripti Condition: This problem lies in MML Command Reference in the

on BSC6910 product documentation or in reference documents for a certain
software version.
Symptom: The High-Risk Command List in MML Command Reference
includes some non-risky commands.
Impact: Some commands in the High-Risk Command List are non-risky
commands.
Severity Major
Root The High-Risk Command List includes all commands that have a dialog
Cause box prompted before its execution. However, in addition to the dialog box,
risky commands should also interrupt services.
Solution The High-Risk Command List now includes only risky commands.
Solution The following commands are no longer included in High-Risk Command
Impact List.

Copyright Huawei
7.3.3 Minor
7.3.3.1 An adjacent node is successfully added by BTS name
although the BTS does not exist.
Ticket
Number
Descripti Condition: In BSC6910 V100R016C00SPC100 or V100R016C00SPC200,

on users run the ADD ADJNODE command to add an adjacent node, with the
Adjacent Node Type parameter set to ABIS(Abis Interface), the Index
Type parameter set to BYNAME(By Name), and the BTS Name
parameter set to the name of a BTS that does not exist. Then, the BSC6910
is upgraded from V100R016C00SPC100 or V100R016C00SPC200 to
V100R016C00SPH602.
Symptom: The ADD ADJNODE command is executed successfully, but
no message is displayed to indicate that the BTS does not exist.
Impact: The added adjacent node does not take effect and the
configuration data is redundant.
Severity Minor
Root In BSC6910 V100R016C00, the BTS existence check rule is changed for
Cause the addition of an Abis interface adjacent node. Specifically, the BSC does
not check the BTS existence when an adjacent node is added by BTS name.
Solution During the addition of an Abis interface adjacent node, the BSC now
checks whether a BTS exists according to its name. An Abis interface
adjacent node can now be successfully added by BTS name only when the
BTS exists. This ensures that the Abis interface adjacent node takes effect
after being added.
Solution If there is data of the Abis interface adjacent node where the BTS is not
Impact configured in BSC6910 V100R016C00SPC100 or V100R016C00SPC200,
the upgrade precheck is performed to prompt users to modify or delete the
redundant data during a BSC6910 upgrade to V100R016C00SPH602 or
V100R016C00 patch version.
ID
7.3.3.2 An isolated standby OMU cannot be de-isolated.

Ticket
Number

Copyright Huawei
Description Condition: The standby OMU board is faulty, and therefore the SCU
board detects "Back Layer 2 Table Fault."
Symptom: The standby OMU is isolated from service processing
boards by the SCU. The following alarms are reported on the alarm
console:
ALM-20702 Active and Standby OMU Communication Link Failure
ALM-20720 OMU Board Fault (Slot No.: number of the slot that
accommodates the standby OMU board)
ALM-20228 GE Link Between GE Switching Board and Service
Board Faulty (Peer Board Slot No.: number of the slot that
accommodates the standby OMU board)
ALM-20714 OMU Time Synchronization Abnormity
Impact: The standby OMU board remains faulty and cannot be de-
isolated.
Severity Minor
Root Cause The board uninhibition command UIN BRD is ineffective against an
OMU board. As a result, the standby OMU cannot recover after being
isolated by the SCU board.
Solution The UIN BRD command can now be used to physically uninhibit an
OMU board. If the standby OMU board is isolated by the SCU board,
run the UIN BRD command to physically inhibit the standby OMU
board.
Solution None
Impact
7.3.3.3 The excessively long MML command outputs cannot

be completely displayed on the U2000.
Number
Descripti Condition: The length of the MML command output exceeds 64 KB.
on Symptom: The MML command output cannot be completely displayed on
the U2000.
Impact: This problem causes difficulty in executing MML commands on
the U2000.
Severity Minor
Root If the length of the MML command output exceeds 64 KB, the MML
Cause command output is divided into multiple packets shorter than 64 KB
according to the OMU packet parsing mechanism. As a result, the packet
end flag may be unexpectedly inserted into the middle of the MML
command output. When this occurs, the U2000 stops receiving subsequent

Copyright Huawei
packets upon detecting the packet end flag. This causes the incomplete
display of MML command outputs.
Solution The OMU packet parsing mechanism has been optimized. When the length
of the MML command output exceeds 64 KB, the packet end flag is no
longer inserted into the middle of the MML command output.
Solution All MML command outputs are completely displayed on the U2000.
Impact
7.3.4 Suggestion
7.3.4.1 MSs are inaccurately located by using the BSS-based
Location Service (Cell ID+TA) function.
Number
Description Condition: During location services using the BSS-based Location

Service (Cell ID+TA) function, the timing advance (TA) value based
on which the BSC calculates the MS location has a deviation of 0.5.
Symptom: The calculated MS location is not the actual MS location.
Impact: The location result cannot reflect the actual MS location,
affecting user experience.
Severity Suggestion
Root Cause When calculating the MS location based on the TA value reported by
the BTS, the BSC considers that the TA value has been rounded down.
For example, if the received TA value is 0, the BSC considers that the
measured TA value is within the range of [0,1). However, the BTS
rounds off the measured TA value before reporting it to the BSC. For
example, if the measured TA value is within the range of [0,0.5), the
BTS reports the TA value 0. Therefore, the TA value based on which
the BSC calculates the MS location has a deviation of 0.5.
Solution The BSC now subtracts 0.5 from the TA value reported by the BTS
before calculating the MS location in the preceding scenario.
Solution None
Impact
7.3.4.2 The alarm location information in ALM-21521, ALM-

21503, and ALM-21553 is insufficient.

Copyright Huawei
Ticket
Number
Descripti Condition: The destination signaling point (DSP) status changes from
on Normal to Faulty.
Symptom: Users cannot determine which CN node or adjacent RNC is
faulty based on the alarm parameters in ALM-21521, ALM-21503, and
ALM-21553.
Impact: Users cannot quickly identify the problem cause.
Severity Suggestion
Root When the base station controller report ALM-21521, ALM-21503, or ALM-
Cause 21553, the alarm parameter specifies only the DSP information and does not
specify the information about the CN node or adjacent RNC.
Solution The Additional Information parameter is added to ALM-21521, ALM-
21503, and ALM-21553. The following table lists the Additional
Information parameters for different destination signaling point (DSP)
types.
If the DSP type is A, the value of the additional information parameter is
"GSM CN Node: CN Node Index=x, Operator Index=y, Operator Name=z".
For other DSP types, the value of the additional information parameter is
"NULL".
Solution None
Impact
Test CASE_Commercial_PR_Regression_R016C00SPH602_005
Case
7.3.4.3 The counter values measured during a patch

upgrade are incorrect.
Ticket DTS: DTS2014051501133 and DTS2014041802705
Number
Descripti Condition: Counters are measured when the OMU has been upgraded to the
on new version but the host has not been upgraded to the new version because
the host is not reset during a patch upgrade.
Symptom: The counter values are inappropriate, for example, ultra-large
values are displayed.
Impact: The measured counter values are incorrect.
Severity Suggestion
Root During the patch upgrade, the OMU software version and the host software
Cause version will be temporarily inconsistent, causing the number of counters for
the same measurement object to change after the upgrade. As a result, the
performance measurement result on the OMU is incorrect.
Solution The following functions are now enabled during a patch upgrade:

Copyright Huawei
The counters that users subscribed to before the upgrade are completely
inherited after the upgrade.
The OMU checks the performance measurement result file reported by the
host before performing the measurement. If the number of counters for a
measurement object is incorrect, the OMU does not measure performance
counters of the measurement object.
Solution None
Impact
Test CASE_Commercial_PR_Regression_R016C00SPH602_006
Case
7.4 Known Issues

7.4.1 Critical
None
7.4.2 Major
None
7.4.3 Minor
be executed.
Ticket
Number
be executed.
Severity Minor
Emergency measures:
command again.

Copyright Huawei
Domain None
later version.
7.4.4 Suggestion
None

Copyright Huawei
BSC6910 GSM
Release Notes 8 Operation and Maintenance Changes
8 Operation and Maintenance

Changes
8.1 MML Command Changes

See Appendix 1 of the release notes.
Appendix 1 BSC6910 GSM V100R016C00SPC620 MML Command Changes.xls
8.2 Parameter Changes

For parameter changes, see Appendix 2 of the release notes.
Appendix 2 BSC6910 GSM V100R016C00SPC620 MO and Parameter Changes.xls
For reserved parameter changes, see the following appendix:
BSC6910 GSM V100R016C00SPC620 Used Reserved Parameter List.xls
8.3 Alarm Changes

Appendix 3 BSC6910 GSM V100R016C00SPC620 Alarm Changes.xls
8.4 Event Changes

Appendix 4 BSC6910 GSM V100R016C00SPC620 Event Changes.xls

Copyright Huawei
BSC6910 GSM
Release Notes 8 Operation and Maintenance Changes
8.5 Counter Changes

For counter changes, see Appendix 5 of the release notes.
Appendix 5 BSC6910 GSM V100R016C00SPC620 Performance Counter Changes.xls
For reserved counter changes, see the following appendix:
BSC6910 GSM V100R016C00SPC620 Used Reserved Counter List.xls
8.6 License Changes

Appendix 6 BSC6910 GSM V100R016C00SPC620 License Changes.xls
8.7 Other Changes

None

Copyright Huawei
BSC6910 GSM
Release Notes A Obtaining Documentation
A Obtaining Documentation
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

Step 1 Access http://support.huawei.com.
Step 2 Click Register, and follow the instructions to complete the registration process.
----End
If your registration is successful, you will be informed of your user name and password within two or
three working days.
Viewing or Downloading Documentation

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 Network > 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.
----End
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.

Copyright Huawei
BSC6910 GSM
Release Notes B Acronyms and Abbreviations
B Acronyms and Abbreviations
A
AAL2 ATM Adaptation Layer type 2
ATM Asynchronous Transfer Mode
B
BER Bit Error Rate
BHCA Busy Hour Call Attempt
BOOTP Bootstrap Protocol
BIOS Basic Input Output System
C
CBC Cell Broadcast Center
CCP Communication Control Port
CDT Call Data Tracing
CoRRM Connection Orient Radio Resource Management
CPLD Complex Programmable Logical Device
CRC Concentrate Routing Board
F
FE Fast Ethernet
FP Frame Protocol
FR Frame Relay

Copyright Huawei
BSC6910 GSM
G
GCC Group Call Control
GE Gigabit Ethernet
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
I
IDC Instance Distribution Control
IMA Inverse Multiplexing on ATM
IP Internet Protocol
IPoA Internet Protocols over ATM
L
LAN Local Area Network
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

Copyright Huawei
BSC6910 GSM
MSP Multiplex Section Protection

MTP Message Transfer Part
MTSS Mapping and Transfer between SCCP entity and
Service entity
P
PARC Platform of Advanced Radio Controller
PCU Packet Control Unit
PDCP Packet Data Convergence Protocol
PRR Packet domain Radio Resource control
PGC Paging Control
PPP Point-to-Point Protocol
PVC Permanent Virtual Channel
R
RDLC Radio Link Control
RESC Radio Embed-resources Set Control
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
SPCC Semi-Permanent Connection Control
SRAP Service Resource Access Plane
SRCP Service Resource Control Plane

Copyright Huawei
BSC6910 GSM
SRP Service Resource Plane
T
TDM Time Division Multiplex
TDMC TDM resource Control
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

Copyright Huawei

Язык

Добро пожаловать в Scribd!

Bsc6910 Gsm v100r016c00spc620 Release Notes

Загружено:

Сведения о документе

Описание:

Дата загрузки

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Описание:

Авторское право:

Доступные форматы

Bsc6910 Gsm v100r016c00spc620 Release Notes

Загружено:

Описание:

Авторское право:

Доступные форматы

Похожие издания

BSC6910 GSM

HUAWEI TECHNOLOGIES CO., LTD.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Huawei Proprietary and Confidential

About This Document

01 2014-09-12 Wang Erli, Xu This is the first commercial release.

Issue 01 (2014-09-12) Huawei Proprietary and Confidential ii

Issu Date Author Description

Qigang, Hou Wei,

Table 1 Section description

Issue 01 (2014-09-12) Huawei Proprietary and Confidential iii

Figure 1 Relationships among sections in Change Summary shows the relationships

Figure 1 Relationships among sections in Change Summary

Feature Changes: details feature changes.

Issue 01 (2014-09-12) Huawei Proprietary and Confidential iv

About This Document.......................................................................ii

3 Changes from V100R016C00SPH609 to V100R016C00SPC620..........9

Issue 01 (2014-09-12) Huawei Proprietary and Confidential v

3.2.2.4 Upgrade Tool Reliability Optimization..................................................................................................................21

Issue 01 (2014-09-12) Huawei Proprietary and Confidential vi

4 Changes from V100R016C00SPH608 to V100R016C00SPH609........46

5 Changes from V100R016C00SPH605 to V100R016C00SPH608........52

Issue 01 (2014-09-12) Huawei Proprietary and Confidential vii

5.1.5 Operation and Maintenance.......................................................................................................................................54

6 Changes from V100R016C00SPH602 to V100R016C00SPH605........57

Issue 01 (2014-09-12) Huawei Proprietary and Confidential viii

7 Changes from V100R016C00SPC600 to V100R016C00SPH602........75

Issue 01 (2014-09-12) Huawei Proprietary and Confidential ix

8 Operation and Maintenance Changes...........................................94

Issue 01 (2014-09-12) Huawei Proprietary and Confidential x

1.1 Product Version

1.2 Software Versions

1.3 Hardware Versions

EOMUa EOMUa WP11EOMUa Ver.B 131 Yes

Issue 01 (2014-09-12) Huawei Proprietary and Confidential 1

Physical Logical Bar Code PCB BIOS/Exten BootRO

SCUb SCUb WP11SCUb Ver.C 133 Yes

Issue 01 (2014-09-12) Huawei Proprietary and Confidential 2

1.4 Related Product Versions

U2000 U2000 iManager U2000 V200R014C00SPC200 or N/A

BTS3012 series BTS3000V200R0013C00 or later BSS13.0

Issue 01 (2014-09-12) Huawei Proprietary and Confidential 3

Product Product Product Version Remar

BTS2X series Not supported N/A

1.5 OS and Database Versions

RTOS V100R001C00 None The installation and upgrade

MySQL5.0.96 None Only the installation can be

Issue 01 (2014-09-12) Huawei Proprietary and Confidential 4

1.6 Related Documentation

GBSS16.0 BSC6910V100R (For Customer)BSC6910 Documentation >

Issue 01 (2014-09-12) Huawei Proprietary and Confidential 5

1.7 Virus Scan Result

Antivirus Antivirus Antivirus Time of Result

Kav 10.1.0.867 20140911- 2014-09-12 No risks were

1.8 Important Notes

1 Time restrictions None