BTS3900 V100R010C10SPC120 (NodeB) Release Notes

BTS3900 V100R010C10SPC120
(NodeB) Release Notes
Issue 01
Date 2015-05-08
HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2015. 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 (2015-05-08) Copyright © Huawei i
Technologies Co., Ltd.
BTS3900 V100R010C10SPC120
(NodeB) Release Notes About This Document
About This Document
Author
Prepared By Li Jiasui Date 2015-5-5
Reviewed By Huang Tao/Wu Hongmei Date 2015-5-6
Tested By Kang Feng Date 2015-5-7
Approved By Li Huasong Date 2015-5-8
Change History
Issue Date Author Change Description
01 2015-5-8 Li Jiasui This issue is the first official

release.
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,
Issue 01 (2015-05-08) Huawei Proprietary and Confidential ii

Copyright © Huawei
BTS3900 V100R010C10SPC120
− 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.
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.
Issue 01 (2015-05-08) Huawei Proprietary and Confidential iii

Copyright © Huawei
BTS3900 V100R010C10SPC120
− 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 (2015-05-08) Huawei Proprietary and Confidential iv

Copyright © Huawei
BTS3900 V100R010C10SPC120
(NodeB) 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..........................................................................................................................................................2
1.4 Related Product Versions..............................................................................................................................................24
1.5 Related Documentation................................................................................................................................................25
1.6 Virus Scan Result..........................................................................................................................................................26
1.7 Important Notes............................................................................................................................................................26
2 Version Compatibility................................................................................................................27
2.1 Software Version Compatibility...................................................................................................................................27
2.2 Hardware Version Compatibility..................................................................................................................................27
3 Changes from V100R010C10SPC100 to V100R010C10SPC120...........................................30

3.1 Change Summary.........................................................................................................................................................30
3.1.1 Capacity and Performance.........................................................................................................................................31
3.1.2 Hardware...................................................................................................................................................................31
3.1.3 Features and Functions..............................................................................................................................................31
3.1.4 Resolved Issues.........................................................................................................................................................32
3.1.5 Operation and Maintenance.......................................................................................................................................32
3.1.5.1 Configuration Management....................................................................................................................................32
3.1.5.2 Performance Management......................................................................................................................................32
3.1.5.3 Fault Management..................................................................................................................................................32
3.1.5.4 License Management..............................................................................................................................................33
3.1.6 Related Documentation.............................................................................................................................................33
3.2 Node.............................................................................................................................................................................33
3.2.1 Feature and Function Changes..................................................................................................................................33
3.2.1.1 New Features and Functions..................................................................................................................................33
3.2.1.2 Modified Features and Functions...........................................................................................................................33
3.2.1.2.1 REQ493088 Optimizing Batch Query Results of Optical Modules....................................................................33
3.2.1.3 Deleted Features and Functions..............................................................................................................................35
3.2.2 Resolved Issues.........................................................................................................................................................35
Issue 01 (2015-05-08) Huawei Proprietary and Confidential v

Copyright © Huawei
BTS3900 V100R010C10SPC120
3.2.2.1 Critical....................................................................................................................................................................35
3.2.2.1.1 UMTS cells served by different subracks are unavailable in scenarios of BBU interconnection involving
BBU3910............................................................................................................................................................................35
3.2.2.2 Major......................................................................................................................................................................36
3.2.2.2.1 The CPU usage is high when pRRUs are fully configured and the served cells are established but not activated
in the LampSite solution.....................................................................................................................................................36
3.2.2.2.2 The base station deployment failure is caused by the incorrect gateway IP address contained in the DHCP
packet received by the base station....................................................................................................................................36
3.2.2.3 Minor......................................................................................................................................................................37
3.2.2.3.1 The counters indicating the maximum and average available uplink bandwidths of a transport resource group
return incorrect values........................................................................................................................................................37
3.2.2.4 Suggestion..............................................................................................................................................................38
3.2.2.4.1 In certain scenarios, no alarm is reported to indicate a low access success rate.................................................38
3.2.2.4.2 The name of the IPSECSWITCH parameter under associated MOs is inaccurate in endpoint mode................38
3.2.2.4.3 The DSP RRU command output shows that an MPMU is connected to two Ethernet cables when it is
connected to only one Ethernet cable in load-sharing networking.....................................................................................39
3.2.2.4.4 A UMTS cell on a LampSite base station fails to be activated, and the base station reports ALM-28211 Cell
Configuration Abnormal.....................................................................................................................................................40
3.2.2.4.5 The value of the VS.IPPM.Peer.Peak.Pkts.RateRx counter is not correctly displayed.......................................40
3.2.2.4.6 When the STR CFGCHK command is executed, ALM-26245 Configuration Data Inconsistency that is
reported because RF modules do not support settings of certain parameters is incorrectly cleared..................................41
3.2.2.4.7 After the STR RFTEST command is executed with Test Type set to PIMON2TONE_2TONE or
PIMON2TONE_SWEEP, the intermodulation interference detection results do not contain IM Product Threshold.......42
3.2.2.4.8 No confirmation message is displayed after the ADD SYNCETH command is executed on the U2000..........42
3.2.2.4.9 The alarm cause for ALM-25900 IP PM Activation Failure is inaccurate if the peer equipment of a base station
does not support IPPM of a later version...........................................................................................................................43
3.2.3 Known Issues.............................................................................................................................................................44
3.3 NodeBFunction.............................................................................................................................................................44
3.3.1.2.1 Licensed Capability Query for the UBBPd Board..............................................................................................44
3.3.2 Resolved Issues.........................................................................................................................................................46
3.3.2.1 Critical....................................................................................................................................................................46
3.3.2.2 Major......................................................................................................................................................................46
3.3.2.2.1 Base stations occasionally fail to be upgraded to RAN17.1...............................................................................46
3.3.2.2.2 In specific scenarios, UEs experience call drops.................................................................................................47
3.3.2.2.3 ALM-26532 RF Unit Hardware Fault is not reported when RRU hardware experiences a failure....................47
3.3.2.2.4 In heavy traffic scenarios in parallel with frequent radio link setup and removal, the UE access success rate
decreases.............................................................................................................................................................................48
3.3.2.2.5 In certain scenarios, ALM-28206 Local Cell Capability Decline is reported when it should not be and the
alarm persists......................................................................................................................................................................48
3.3.2.3 Minor......................................................................................................................................................................49
Issue 01 (2015-05-08) Huawei Proprietary and Confidential vi

Copyright © Huawei
BTS3900 V100R010C10SPC120
3.3.2.3.1 In certain scenarios, the dynamic voltage adjustment function does not take effect...........................................49
3.3.2.3.2 EVT-28200 Iub Common Procedure Failure Indication is reported with no detail about the causes of the alarm
triggering condition provided.............................................................................................................................................49
3.3.2.3.3 The VS.BTS.CnbapCap.UseRate counter returns a value smaller than expected for a base station configured
with the UBBPd5 board......................................................................................................................................................50
3.3.2.3.4 Benefits yielded by WRFD-170201 Seamless Crystal Voice and WRFD-171201 Crystal Voice in Deep
Coverage decrease when WRFD-140202 Control Channel Parallel Interference Cancellation (Phase 2) is enabled.......51
3.3.2.3.5 DC-HSDPA services are reconfigured as SC-HSDPA services and radio link reconfiguration fails if DC-
HSDPA over Iur is enabled.................................................................................................................................................51
3.3.2.3.6 The counter indicating the number of uplink frames discarded by the Iub logical port occasionally returns a
larger value than expected after a handover.......................................................................................................................52
3.3.2.4 Suggestion..............................................................................................................................................................52
3.3.2.4.1 In certain scenarios, ALM-28206 Local Cell Capability Decline is not reported when it should be..................52
3.3.2.4.2 The average ratio of DPCH and F-DPCH transmit power over different SF code channels to the maximum
downlink transmit power in a cell is less than expected....................................................................................................53
3.3.3 Known Issues.............................................................................................................................................................54
4 Changes from V100R010C10SPC050 to V100R010C10SPC100...........................................55

4.1 Change Summary.........................................................................................................................................................55
4.1.2 Hardware...................................................................................................................................................................56
4.1.4 Resolved Issues.........................................................................................................................................................57
4.2 Node.............................................................................................................................................................................59
4.2.1.2.1 DSP SFP Command Output Optimization...........................................................................................................59
4.2.2 Resolved Issues.........................................................................................................................................................61
4.2.2.1 Critical....................................................................................................................................................................61
4.2.2.1.1 A board where the certificate is installed occasionally restarts due to high memory usage................................61
4.2.2.2 Major......................................................................................................................................................................61
4.2.2.2.1 Hardware faults fail to be reported due to the absent FPGA check during the running of a board.....................61
4.2.2.2.2 Hardware faults fail to be reported due to the absent CPLD check during the running of a board....................62
4.2.2.2.3 The VPP component has a vulnerability..............................................................................................................63
4.2.2.2.4 The result of traffic statistics at the IP layer is inaccurate...................................................................................63
4.2.2.2.5 NTP synchronization fails if the OM IP address and device IP address are the same........................................64
Issue 01 (2015-05-08) Huawei Proprietary and Confidential vii

Copyright © Huawei
BTS3900 V100R010C10SPC120
4.2.2.3 Minor......................................................................................................................................................................64
4.2.2.3.1 The CSEC finds that the RC4 algorithm is prone to attacks...............................................................................64
4.2.2.3.2 No alarm is reported when a hard failure occurs in the FPGA of an RF module................................................65
4.2.2.3.3 An RRU configured with cascaded optical modules incorrectly reports ALM-26506 RF Unit Optical Interface
Performance Degraded.......................................................................................................................................................65
4.2.2.3.4 No alarm is reported when the RF module uses the Low-rate optical module as a high rate.............................66
4.2.2.3.5 The configured TMA attenuation value does not take effect..............................................................................67
4.2.2.3.6 Configuration check items do not pass health check on the RRU3801C............................................................67
4.2.2.3.7 ALM-26245 Configuration Data Inconsistency is repeatedly reported and cleared...........................................68
4.2.2.3.8 Statistics on USERPLANEHOSTIP are inaccurate............................................................................................68
4.2.2.4 Suggestion..............................................................................................................................................................69
4.2.2.4.1 DSP faults occur on the WBBPd board but ALM-26200 Board Hardware Fault is not reported.......................69
4.2.2.4.2 In the engineering quality check on the RRU V1 and RRU V2, the PIM test result is incorrect.......................69
4.2.2.4.3 The LST RRU command output on the U2000 is incomplete for a large-scale LampSite network...................70
4.2.2.4.4 The queried session status is incorrect during a certificate request process........................................................71
4.2.2.4.5 A UMTS cell established on multiple boards experiences access exceptions in a certain scenario....................71
4.2.2.4.6 Counters related to IP and ATM physical ports return inaccurate values............................................................72
4.2.3 Known Issues.............................................................................................................................................................72
4.3 NodeBFunction.............................................................................................................................................................72
4.3.1.2.1 Service Drop Rate Reduction for UEs Whose Downlink SRBs are Carried on HSDPA Channels....................73
4.3.1.2.2 WRFD-171203 Uplink Control Channel OLPC.................................................................................................75
4.3.2 Resolved Issues.........................................................................................................................................................77
4.3.2.1 Critical....................................................................................................................................................................77
4.3.2.2 Major......................................................................................................................................................................77
4.3.2.2.1 UEs on the UBBPd board occasionally experience call drops............................................................................77
4.3.2.2.2 ALM-26242 Configuration File Damaged is reported in specific scenarios.......................................................78
4.3.2.2.3 HSDPA throughput is low on a LampSite network.............................................................................................78
4.3.2.2.4 The performance counters related to the NodeB Iub logic port return greater values than expected.................79
4.3.2.2.5 HSDPA throughput of all cells on the WBBPb board is 0..................................................................................79
4.3.2.2.6 The counters measuring the number of UEs enabled with CPC return values greater than expected................80
4.3.2.2.7 In certain scenarios, counters related to service setup delay return values greater than expected......................80
4.3.2.2.8 HSDPA rates of single users fluctuate after handovers in ATM transmission scenarios.....................................81
4.3.2.3 Minor......................................................................................................................................................................82
4.3.2.3.1 If the NodeB serves DC-HSUPA and HSUPA users at the same time, the uplink rate is higher than expected for
DC-HSUPA users and widely fluctuates for HSUPA users................................................................................................82
4.3.2.4 Suggestion..............................................................................................................................................................82
4.3.2.4.1 The ID of the HSUPA Scheduler Pool feature is incorrect in the parameter reference.......................................82
4.3.2.4.2 The actual hardware capability of the UBBPd board cannot be queried.............................................................83
Issue 01 (2015-05-08) Huawei Proprietary and Confidential viii

Copyright © Huawei
BTS3900 V100R010C10SPC120
4.3.3 Known Issues.............................................................................................................................................................83
5 Changes from V100R010C10 to V100R010C10SPC050.........................................................84

5.1 Change Summary.........................................................................................................................................................84
5.1.2 Hardware...................................................................................................................................................................85
5.1.4 Resolved Issues.........................................................................................................................................................86
5.2 Node.............................................................................................................................................................................87
5.2.1.1.1 IPSec NAT Traversal...........................................................................................................................................87
5.2.2 Resolved Issues.........................................................................................................................................................88
5.2.2.1 Critical....................................................................................................................................................................88
5.2.2.1.1 Ports on the management plane can be scanned through all DEVIP addresses..................................................88
5.2.2.2 Major......................................................................................................................................................................89
5.2.2.2.1 The GUI for offline intermodulation interference test is not user-friendly.........................................................89
5.2.2.3 Minor......................................................................................................................................................................90
5.2.2.3.1 Name extensions of files to be downloaded are not checked..............................................................................90
5.2.2.3.2 Board fault alarms fail to be displayed if board software detects faults on the UTRP or UTRPc board............90
5.2.2.3.3 ALM-26200 Board Hardware Fault is not reported when the CPU port of a UTRPc board is faulty................91
5.2.2.4 Suggestion..............................................................................................................................................................92
5.2.2.4.1 VoLTE services that require transmission of large packets fail in scenarios where IPSec encryption is used....92
5.2.3 Known Issues.............................................................................................................................................................92
5.3 NodeBFunction.............................................................................................................................................................93
5.3.2 Resolved Issues.........................................................................................................................................................93
5.3.2.1 Critical....................................................................................................................................................................93
5.3.2.2 Major......................................................................................................................................................................93
5.3.2.2.1 The RRC connection setup success rate slightly decreases for the cell established on the WBBPb or WBBPd
board...................................................................................................................................................................................93
5.3.2.3 Minor......................................................................................................................................................................94
Issue 01 (2015-05-08) Huawei Proprietary and Confidential ix

Copyright © Huawei
BTS3900 V100R010C10SPC120
5.3.2.4 Suggestion..............................................................................................................................................................94
5.3.3 Known Issues.............................................................................................................................................................94
6 Changes from V100R009C00SPC180 to V100R010C10.........................................................95

6.1 Change Summary.........................................................................................................................................................95
6.1.2 Hardware...................................................................................................................................................................97
6.1.3 Features and Functions............................................................................................................................................100
6.1.4 Resolved Issues.......................................................................................................................................................101
6.1.5 Operation and Maintenance.....................................................................................................................................101
6.1.5.1 Configuration Management..................................................................................................................................101
6.1.5.2 Performance Management....................................................................................................................................101
6.1.5.3 Fault Management................................................................................................................................................101
6.1.5.4 License Management............................................................................................................................................102
6.1.6 Related Documentation...........................................................................................................................................102
6.2 Node...........................................................................................................................................................................107
6.2.1 Feature and Function Changes................................................................................................................................107
6.2.1.1 New Features and Functions................................................................................................................................107
6.2.1.1.1 Obtaining Information About the Reused TMA in Base Station Swapping Scenarios.....................................107
6.2.1.1.2 Inter-frequency Mutual Aid of RF Modules......................................................................................................108
6.2.1.1.3 Local Maintenance of the Outdoor BBU Through WLAN Wireless Network Interface Card.........................110
6.2.1.1.4 Configurable TWAMP TCP Port Number.........................................................................................................111
6.2.1.1.5 Local Loop Detection........................................................................................................................................113
6.2.1.1.6 Adding an RRU/RFU/AAMU to a CPRI Chain or Ring Through the CME Without Resetting the Base Station
..........................................................................................................................................................................................114
6.2.1.1.7 DHCP Relay Availability Detection on the Transport Network........................................................................115
6.2.1.1.8 Mitigating the Risks of Violating Regulations by Adding an MOC that Specifies the Authorized Downlink
Frequency Band................................................................................................................................................................117
6.2.1.1.9 Multi-BBU Interconnection...............................................................................................................................119
6.2.1.1.10 Four UMTS and LTE RX Channels Supported by the RRU3952 and RRU3942 Combined to Serve the Same
Sector................................................................................................................................................................................120
6.2.1.2 Modified Features and Functions.........................................................................................................................121
6.2.1.2.1 Separate Removal of Electromagnetic Subracks Using an MML Command...................................................121
6.2.1.2.2 Supporting Up to 24 UMTS Cells by a LampSite Base Station........................................................................123
6.2.1.2.3 Configurable Status for Local Maintenance Ethernet Ports..............................................................................124
6.2.1.2.4 Automatic Adjustment of RRUs' Intermediate Frequency Offset.....................................................................125
6.2.1.2.5 Enhanced SSL Algorithms and Maintenance....................................................................................................127
6.2.1.2.6 Security Parameter Setting Added to Security Level Setting............................................................................128
6.2.1.2.7 Port Number Information Added to ACL Rules in End Point Configuration Mode.........................................130
6.2.1.2.8 Efficiency Improvement in Base Station Upgrade Risk Check........................................................................131
6.2.1.2.9 Enhanced Switchover Mechanism for Active and Standby OM Channels.......................................................132
6.2.1.2.10 User Experience Optimization Displayed on the ALD Management Interface..............................................134
6.2.1.2.11 Reporting the Electronic Label of the BBU Subrack to the U2000................................................................136
Issue 01 (2015-05-08) Huawei Proprietary and Confidential x

Copyright © Huawei
BTS3900 V100R010C10SPC120
6.2.1.2.12 Enhanced Signature Algorithm for the Device Certificate..............................................................................138

6.2.1.2.13 Optical Power Check on CPRI and Transmission Ports Supported in NE Health Check...............................139
6.2.1.2.14 RRU Remote Mode Presented in Base Station Configuration........................................................................140
6.2.1.2.15 Supporting Independent Base Stations............................................................................................................141
6.2.1.3 Deleted Features and Functions............................................................................................................................143
6.2.2 Resolved Issues.......................................................................................................................................................143
6.2.2.1 Critical..................................................................................................................................................................143
6.2.2.1.1 In certain scenarios, the baseband processing unit fails to start........................................................................143
6.2.2.1.2 The UTRPa board occasionally restarts unexpectedly......................................................................................143
6.2.2.1.3 There is a low probability that the WMPT board unexpectedly restarts...........................................................144
6.2.2.2 Major....................................................................................................................................................................144
6.2.2.2.1 IMA group- and IMA link-related alarms are reported when they should not be.............................................144
6.2.2.2.2 In combined RRU configuration, the project quality check fails......................................................................145
6.2.2.2.3 Users having common rights can run some MML commands defined only for users having administrator
rights.................................................................................................................................................................................145
6.2.2.2.4 The access success rate decreases on the UBBPd board...................................................................................146
6.2.2.2.5 The STR RTWPRTTST command output shows only single-carrier RTWP information................................146
6.2.2.2.6 There is a possibility that the RRC connection setup success rate decreases....................................................147
6.2.2.3 Minor....................................................................................................................................................................148
6.2.2.3.1 The output of the DSP IPSECSA6 command is incomplete.............................................................................148
6.2.2.3.2 After a certificate expires, automatic certificate acquisition fails.....................................................................148
6.2.2.3.3 The device panel for the OMB (Ver.C) cabinet is incorrectly displayed...........................................................149
6.2.2.3.4 If the main control boards work in active/standby mode, services carried in the MP group are interrupted....149
6.2.2.3.5 The deployment check fails occasionally..........................................................................................................150
6.2.2.3.6 The links between pRRUs and the BBU in the LampSite solution become faulty...........................................150
6.2.2.4 Suggestion............................................................................................................................................................151
6.2.2.4.1 The MML command description is incorrect....................................................................................................151
6.2.2.4.2 If SSLv3 is used to encrypt data exchanged between a NodeB and the NMS, the encrypted data may be
cracked..............................................................................................................................................................................151
6.2.2.4.3 An inaccurate prompt message is displayed after TLS1.2 is disabled on the CME..........................................152
6.2.2.4.4 The traffic volume queried by running the DSP ETHTRK command or using traffic statistics is different from
the actual one in the trunk group......................................................................................................................................152
6.2.3 Known Issues...........................................................................................................................................................153
6.3 NodeBFunction...........................................................................................................................................................153
6.3.1 Feature and Function Changes................................................................................................................................153
6.3.1.1 New Features and Functions................................................................................................................................153
6.3.1.1.1 WRFD-171201 Crystal Voice in Deep Coverage..............................................................................................153
6.3.1.1.2 WRFD-150209 DB-HSDPA..............................................................................................................................159
6.3.1.1.3 WRFD-150250 3C-HSDPA...............................................................................................................................162
6.3.1.1.4 WRFD-150251 HSPA+ Downlink 63Mbit/s per User......................................................................................164
6.3.1.1.5 WRFD-171207 Virtual CPC..............................................................................................................................166
6.3.1.1.6 WRFD-171209 Coverage Improvement for HSUPA 2 ms TTI UEs................................................................169
Issue 01 (2015-05-08) Huawei Proprietary and Confidential xi

Copyright © Huawei
BTS3900 V100R010C10SPC120
6.3.1.1.7 WRFD-171204 DPCH Power Control Based on Radio Quality.......................................................................172

6.3.1.1.8 WRFD-160251 HSDPA Inter-Cell Power Sharing............................................................................................176
6.3.1.1.9 WRFD-171212 Coverage Expansion Under Interference.................................................................................180
6.3.1.1.10 WRFD-171210 Radio-Aware Video Precedence............................................................................................187
6.3.1.1.11 WRFD-171221 NodeB Supporting IPsec Redirection....................................................................................192
6.3.1.1.12 WRFD-171220 NodeB Supporting Multi-operator PKI.................................................................................195
6.3.1.1.13 NodeB CHR Optimization..............................................................................................................................199
6.3.1.1.14 WRFD-170108 Hitless Cell Rehoming...........................................................................................................201
6.3.1.1.15 WRFD-170106 Iub Self-planning...................................................................................................................203
6.3.1.1.16 WRFD-170201 Seamless Crystal Voice..........................................................................................................208
6.3.1.1.17 WRFD-170203 HSUPA Scheduler Pool.........................................................................................................217
6.3.1.1.18 WRFD-170102 Instant Macro Diversity.........................................................................................................220
6.3.1.1.19 WRFD-170204 Radio Aware Video Shaping..................................................................................................225
6.3.1.1.20 WRFD-171203 Uplink Control Channel OLPC.............................................................................................231
6.3.1.2 Modified Features and Functions.........................................................................................................................234
6.3.1.2.1 WRFD-01061009 HSDPA H-ARQ & Scheduling (MAX C/I, RR and PF).....................................................234
6.3.1.2.2 WRFD-01061010 HSDPA Flow Control..........................................................................................................236
6.3.1.2.3 WRFD-010713 Traffic-Based Activation and Deactivation of the Supplementary Carrier In Multi-carrier....237
6.3.1.2.4 WRFD-150208 Flexible Dual Carrier HSDPA.................................................................................................240
6.3.1.2.5 WRFD-01061212 HSUPA Iub Flow Control in Case of Iub Congestion.........................................................243
6.3.1.2.6 WRFD-140204 DC-HSUPA..............................................................................................................................244
6.3.1.2.7 WRFD-021350 Independent Demodulation of Signals from Multiple RRUs in One Cell...............................251
6.3.1.2.8 WRFD-140225 Narrowband Interference Suppression....................................................................................253
6.3.1.2.9 WRFD-050501 Clock Sync on Ethernet in NodeB...........................................................................................255
6.3.1.2.10 Real-time HSDPA Cell Throughput Monitoring on the LMT.........................................................................257
6.3.1.2.11 WRFD-010696 DC-HSDPA............................................................................................................................258
6.3.1.2.12 MRFD-221601 Multi-mode BS Common Reference Clock(NodeB).............................................................260
6.3.1.3 Deleted Features and Functions............................................................................................................................262
6.3.2 Resolved Issues.......................................................................................................................................................262
6.3.2.1 Critical..................................................................................................................................................................262
6.3.2.1.1 The call drop rate increases if the WRFD-170201 Seamless Crystal Voice feature is activated......................262
6.3.2.2 Major....................................................................................................................................................................263
6.3.2.2.1 If the MC Inter-Board Joint Scheduling Switch is turned on and a DC UE accesses a cell in the handover area,
there is a low probability that a board resets....................................................................................................................263
6.3.2.2.2 Activation, deactivation, or parameter modification of a logical cell fails.......................................................263
6.3.2.2.3 HSDPA throughput is low and the PS service drop rate increases for a cell when MC Inter-Board Joint
Scheduling Switch is turned on........................................................................................................................................264
6.3.2.2.4 After KPI invisible fault detection is enabled, ALM-26203 Board Software Program Error is reported when it
should not be.....................................................................................................................................................................264
6.3.2.2.5 After sleeping cell detection is enabled, ALM-26203 Board Software Program Error is reported when it should
not be................................................................................................................................................................................265
6.3.2.2.6 Cells established on the UBBPd board occasionally experience a decrease in the RRC connection setup
success rate.......................................................................................................................................................................265
Issue 01 (2015-05-08) Huawei Proprietary and Confidential xii

Copyright © Huawei
BTS3900 V100R010C10SPC120
6.3.2.2.7 HSUPA UEs served by the WBBPf or UBBPd board experience low data rates if flow control is triggered and
the switch for correcting the SIR when the RTWP is abnormal is turned on...................................................................266
6.3.2.2.8 There is an extremely low probability that ongoing services carried on the WBBPd or WBBPb board are
interrupted.........................................................................................................................................................................267
6.3.2.2.9 There is a low probability that a cell fails to be established..............................................................................267
6.3.2.2.10 If the Seamless Crystal Voice feature is enabled, there is an extremely low probability that the WBBPf or
UBBPd board resets unexpectedly...................................................................................................................................268
6.3.2.2.11 Verification of UL Frequency Channel Number and DL Frequency Channel Number configured for a local
cell is inaccurate...............................................................................................................................................................268
6.3.2.2.12 The call drop rate of HSDPA users increases after the SRB over HSDPA feature is enabled........................269
6.3.2.2.13 A remote cell reports ALM-28203 Local Cell Unusable if the remote cell and an ordinary cell are served by
the same uplink resource group........................................................................................................................................269
6.3.2.2.14 The VS.HSUPA.AGCHCodeUtil.Mean counter returns an incorrect value if the Turbo IC Phase 2 feature is
enabled..............................................................................................................................................................................270
6.3.2.2.15 The WBBPb board falsely reports that a local cell supports the EAI capability.............................................270
6.3.2.2.16 The NodeB performance counter VS.HSUPA.SingletoAllHARQNum returns a smaller value than expected.
..........................................................................................................................................................................................271
6.3.2.2.17 When the MOCN CE resource independent allocate(per cell) license expires, the NodeB becomes
unavailable and cannot be restored following a restart....................................................................................................271
6.3.2.2.18 The feature query results are incorrect in the scenario with specific NodeB board configurations................272
6.3.2.2.19 There is a low probability that baseband processing units are restarted because CDT tracing is terminated. 273
6.3.2.2.20 The service rate of DC-HSUPA UEs is lower than expected in certain scenarios..........................................273
6.3.2.2.21 The configuration information about HSDPA supplementary carriers and supplementary streams are
incorrectly presented in the results of HSPA Monitoring.................................................................................................274
6.3.2.2.22 After CPC is enabled, the call drop rates of PS/HSDPA/HSUPA services increase in scenarios of DRD, hard
handovers, and F2D/P2D transitions................................................................................................................................274
6.3.2.2.23 The CPU usage is imbalanced between baseband processing units when the UTRPc board is used to expand
the signaling capacity.......................................................................................................................................................275
6.3.2.2.24 In heavy traffic scenarios in parallel with frequent radio link setup and removal, the UE access success rate
decreases...........................................................................................................................................................................276
6.3.2.3 Minor....................................................................................................................................................................276
6.3.2.3.1 The HSDPA service throughput of E-RACH UEs is low..................................................................................276
6.3.2.3.2 The VS.HSUPA.10msTTI.CCHOLPC.UserNum.Mean and VS.HSUPA.2msTTI.CCHOLPC.UserNum.Mean
counters return larger values than expected for a 4-antenna cell.....................................................................................277
6.3.2.3.3 Platinum users experience poor voice services when network congestion occurs............................................277
6.3.2.3.4 If the UBBPd board serves a multi-RRU cell, there is a possibility that ongoing services carried on the UBBPd
board are temporarily interrupted during cell reconfiguration.........................................................................................278
6.3.2.3.5 When the E-DPCCH Boosting feature is activated, HSUPA throughput decreases on the WBBPd board......278
6.3.2.3.6 The link performance for HSDPA data transmission of some DC-HSDPA UEs is slightly poor.....................279
6.3.2.3.7 Values of bandwidth counters are low when the adaptive traffic shaping flow control algorithm is selected for
HSDPA services................................................................................................................................................................279
6.3.2.3.8 License sales units of NodeB licenses displayed on the U2000 are unavailable..............................................280
6.3.2.3.9 The RTWP rises due to a large number of high-speed HSUPA users...............................................................281
6.3.2.3.10 The KPI invisible fault detection mechanism needs to be optimized..............................................................282
6.3.2.3.11 The value of UL Required Load is smaller than expected..............................................................................282
Issue 01 (2015-05-08) Huawei Proprietary and Confidential xiii

Copyright © Huawei
BTS3900 V100R010C10SPC120
6.3.2.3.12 In MOCN scenarios, if licenses for other features are insufficient, ALM-26811 Configured Capacity Limit
Exceeding Licensed Limit is reported from NodeBs of available operators when the alarm should not........................283
6.3.2.3.13 The Uplink CoMP (Joint Reception) feature is unusable................................................................................283
6.3.2.3.14 The VS.ERACH.Thruput and VS.EFACH.Thruput counters return "OverFlow"..........................................284
6.3.2.3.15 In specific scenarios, the NodeB performance counters using units of dBm and dB return an inaccurate value
of 0....................................................................................................................................................................................284
6.3.2.3.16 The alarm cause for ALM-28203 Local Cell Unusable is inaccurate.............................................................285
6.3.2.4 Suggestion............................................................................................................................................................286
6.3.2.4.1 After the FDE feature is activated, throughput of UEs occasionally decreases................................................286
6.3.2.4.2 If a DC UE accesses a cell in the handover area access time, there is a low probability that radio link
reconfiguration fails due to NodeB resource insufficiency..............................................................................................286
6.3.2.4.3 Counters related to power performance in a MOCN network return incorrect values.....................................287
6.3.2.4.4 DC capability derating occasionally occurs after the NodeB is upgraded or restarted, or a NodeB application is
restarted............................................................................................................................................................................288
6.3.2.4.5 The WBBPd or WBBPb board reports ALM-28209 Cell No Traffic when it should not.................................288
6.3.2.4.6 The interface values of parameters in the Dynamic Power Sharing in Multi-Carriers feature are inconsistent
with those of parameters in the HSDPA Inter-Cell Power Sharing feature......................................................................289
6.3.2.4.7 The preemption success rate is low and the PS service drop rate is high when the NodeB CE resource
preemption function is enabled on the RNC....................................................................................................................289
6.3.2.4.8 DSP load values of the WBBPd and WBBPf boards are different between BTS3900 V100R010C10 and
BTS3900 V100R010C00SPC010 when no service is running........................................................................................290
6.3.2.4.9 In specific scenarios, values are inconsistent between the performance counters measuring the maximum,
minimum, and average statistical values for a measurement object................................................................................290
6.3.2.4.10 The ULK USR command cannot be executed on the WebLMT.....................................................................291
6.3.2.4.11 Some counters in the HSDPA function subset return incorrect values............................................................291
6.3.2.4.12 Some counters in the HSUPA function subset return incorrect values............................................................292
6.3.3 Known Issues...........................................................................................................................................................292
7 Changes from V100R008C00SPC300 to V100R010C10.......................................................293

7.1 Change Summary.......................................................................................................................................................293
7.1.1 Capacity and Performance.......................................................................................................................................294
7.1.2 Hardware.................................................................................................................................................................296
7.1.3 Features and Functions............................................................................................................................................297
7.1.4 Resolved Issues.......................................................................................................................................................297
7.1.5 Operation and Maintenance.....................................................................................................................................298
7.1.5.1 Configuration Management..................................................................................................................................298
7.1.5.2 Performance Management....................................................................................................................................298
7.1.5.3 Fault Management................................................................................................................................................298
7.1.5.4 License Management............................................................................................................................................298
7.1.6 Related Documentation...........................................................................................................................................298
7.2 Feature and Function Changes...................................................................................................................................304
7.2.1 New Features and Functions...................................................................................................................................304
7.2.1.1 UL CE Resource Pool for 12 Cells.......................................................................................................................304
7.2.1.2 Improved Downlink Throughput..........................................................................................................................305
Issue 01 (2015-05-08) Huawei Proprietary and Confidential xiv

Copyright © Huawei
BTS3900 V100R010C10SPC120
7.2.1.3 Solution to Inconsistent License Sales and Control Strategies............................................................................313

7.2.1.4 Support for IKEv2 Reauthentication....................................................................................................................318
7.2.1.5 WRFD-160106 Fast Radio Bearer Setup.............................................................................................................319
7.2.1.6 WRFD-160204 CS Voice Precise Power Contro..................................................................................................323
7.2.1.7 WRFD-160208 160 HSPA Users per Cell............................................................................................................327
7.2.1.8 WRFD-160209 192 HSPA Users per Cell............................................................................................................330
7.2.1.9 WRFD-160205 CE Efficiency Improvement for HSUPA TTI 2ms.....................................................................333
7.2.1.10 WRFD-160213 Turbo IC Phase2.......................................................................................................................335
7.2.1.11 WRFD-160201 Control Channel Parallel Interference Cancellation.................................................................339
7.2.1.12 WRFD-151211 RNC IP Active Performance Measurement..............................................................................343
7.2.1.13 WRFD-160274 IPSec Redundancy Among Multiple SeGWs...........................................................................349
7.2.1.14 WRFD-151210 Inter-Dependence of BBU Uplink Resource............................................................................353
7.2.1.15 WRFD-151205 Uplink CoMP (Joint Reception)...............................................................................................356
7.2.1.16 WRFD-151206 HetNet Uplink CoMP (Joint Reception)...................................................................................363
7.2.1.17 WRFD-151207 Uplink CoMP (Joint Reception) Based on Coordinated BBU.................................................369
7.2.1.18 WRFD-151208 Macro-Micro Multi RRUs in One Cell.....................................................................................375
7.2.1.19 WRFD-151209 Macro-Micro DC-HSDPA........................................................................................................378
7.2.1.20 WRFD-160250 Interference Rejection Combining............................................................................................382
7.2.2 Modified Features and Functions............................................................................................................................384
7.2.2.1 Flexible Frequency Bandwidth of UMTS Carrier (GU Refarming 4.2 MHz).....................................................384
7.2.2.2 Deleted Mutual Exclusive Relationships Between the FDE Feature and the Features Related to the Multi-RRU
Cell or Mixed Multi-RRU Cell.........................................................................................................................................386
7.2.2.3 Intelligently Out of Service..................................................................................................................................388
7.2.2.4 Enhanced NodeB Maintenance and Test..............................................................................................................389
7.2.2.5 New Parameter USERLABEL for SRAN MOs...................................................................................................392
7.2.2.6 Optimized RET Management...............................................................................................................................393
7.2.2.7 Support for More ACL Rules in an ACL..............................................................................................................394
7.2.2.8 SSL Transmission of Updated CRLs....................................................................................................................395
7.2.2.9 Optimized Mechanism of Reporting the Imminent Certificate Expiry Alarm.....................................................397
7.2.2.10 Support for the Dormancy Status for PSUs........................................................................................................398
7.2.2.11 Removed the Restriction of Removing the Main Control Board of the Peer Mode Before Deploying the UMTS
Mode When the RNC Operates as the BOOTP Server....................................................................................................399
7.2.2.12 Added an "Auto clear" Flag for ADMC Alarms.................................................................................................400
7.2.2.13 WRFD-140223 MOCN Cell Resource Demarcation.........................................................................................401
7.2.2.14 WRFD-050402 IP Transmission Introduction on Inb Interface.........................................................................406
7.2.2.15 MRFD-221901 Multi-RAT Carrier Joint Inrelligent Shutdown.........................................................................408
7.2.2.16 WRFD-01061203 HSUPA Power Control.........................................................................................................417
7.2.2.17 Single BBU Supporting 24 RHUBs in the LampSite Solution..........................................................................419
7.2.3 Deleted Features and Functions...............................................................................................................................420
7.3 Resolved Issues..........................................................................................................................................................420
7.3.1 Critical.....................................................................................................................................................................420
7.3.1.1 The base station may reset after an IP clock is configured...................................................................................420
Issue 01 (2015-05-08) Huawei Proprietary and Confidential xv

Copyright © Huawei
BTS3900 V100R010C10SPC120
7.3.2 Major.......................................................................................................................................................................421
7.3.2.1 The RRU3804 (AC) and RRU3806 (AC) do not report ALM-26540 RF Unit AC Input Power Failure when they
should be...........................................................................................................................................................................421
7.3.2.2 When the common transport channels fail to be established, there is an extremely low probability that a cell
becomes a sleeping cell....................................................................................................................................................422
7.3.2.3 Inconsistent license sales and control strategies are present for the UBBP board in RAN16.0...........................422
7.3.2.4 There is a low probability that the WBBPd board becomes unavailable.............................................................423
7.3.2.5 The value returned by VS.DlPwrRatio.SF256 is larger than expected................................................................423
7.3.2.6 There is a low probability that a cell fails to be established.................................................................................424
7.3.2.7 Cells served by the WBBPb or WBBPd board experience zero RRC connection setup attempts if flow control is
triggered............................................................................................................................................................................424
7.3.2.8 All cells established on the WBBPd board occasionally experience a low RRC connection setup success rate. 425
7.3.2.9 In specific scenarios, the RAB assignment success rate decreases......................................................................426
7.3.2.10 FTP communication between a NodeB and the M2000 fails and therefore NodeB software fails to be
automatically supplemented.............................................................................................................................................426
7.3.2.11 In specific scenarios, RTWP-related counters all return a value 0.....................................................................427
7.3.2.12 ALM-28206 Local Cell Capability Decline is not reported when it should be..................................................428
7.3.2.13 If an exception occurs, there is a low probability that UEs served by the WBBPd or WBBPb board experience
service drops.....................................................................................................................................................................428
7.3.2.14 RRUs are repetitively loaded due to configuration errors in a dual-mode base station.....................................429
7.3.2.15 The capability of distributed cells declines........................................................................................................429
7.3.2.16 The CPU usage is imbalanced between baseband processing units when the UTRPc board is used to expand the
signaling capacity.............................................................................................................................................................430
7.3.2.17 In certain scenarios, there is a high probability that the NodeB does not report ALM-26200 Board Hardware
Fault..................................................................................................................................................................................431
7.3.2.18 The output power of distributed cells is abnormal.............................................................................................431
7.3.2.19 RRU status modification for a sector and sector equipment on the CME does not take effect.........................432
7.3.2.20 The UTRPc board of RAN14.0 sometimes fails to be upgraded to RAN16.0...................................................432
7.3.2.21 The RRU3804 or WRFU sometimes fails to be upgraded to RAN16.0.............................................................433
7.3.2.22 There is a vulnerability from Heartbleed Security threats when the FTP server downloaded from the LMT uses
OpenSSL 1.0.1g................................................................................................................................................................434
7.3.2.23 A barred cell is reestablished if the NodeB falsely determines that the barred cell experiences exceptions in the
RRC connection setup process.........................................................................................................................................434
7.3.2.24 When the UL CoMP and Multi-BBU Interconnection features are activated, coordinating links cannot be
added.................................................................................................................................................................................435
7.3.2.25 After the Queuing and Pre-Emption feature is activated, the RRC connections fail to be set up......................436
7.3.2.26 After HSDPA UEs are handed over to another cell, their data rates sometimes drop to 0 kbit/s.......................436
7.3.2.27 In ATM transmission mode, a NodeB configured with the UMPT board resets unexpectedly..........................437
7.3.2.28 Faults in the flash memory of a baseband processing unit cannot be detected or reported before a NodeB
upgrade.............................................................................................................................................................................438
7.3.2.29 The WBBPf or UBBPd board occasionally resets after the Boosting feature has been enabled.......................438
7.3.2.30 The RAB setup success rate decreases during inter-RAT handovers.................................................................439
7.3.2.31 Cells excluding multi-RRU cells fail to use power control licenses released by running the MOD
ULOCELLSECTOREQM command...............................................................................................................................439
7.3.2.32 When the MOCN feature is enabled, uplink CE-related counters return inaccurate values..............................440
Issue 01 (2015-05-08) Huawei Proprietary and Confidential xvi

Copyright © Huawei
BTS3900 V100R010C10SPC120
7.3.2.33 In ATM transmission mode, call drops sometimes occur due to asynchronous reconfiguration in specific
scenarios...........................................................................................................................................................................441
7.3.2.34 Iub signaling messages seldom fail to be processed when IRC is enabled on a UBBPd board.........................441
7.3.2.35 There is a low probability that the main control board reports the ALM-26202 Board Overload alarm...........442
7.3.2.36 HSDPA users experience low data rates.............................................................................................................442
7.3.2.37 The local cell experiences intermittent ALM-28203 Local Cell Unusable........................................................443
7.3.2.38 The local cell experiences intermittent ALM-28206 Local Cell Capability Decline after a NodeB is upgraded to
V100R009C00SPC010 or V100R009C00SPC020..........................................................................................................443
7.3.2.39 The NodeB reports EVT-28200 Iub Common Procedure Failure Indication.....................................................444
7.3.2.40 There is a low possibility that UEs fail to access multi-RRU cells if Independent Demodulation of Signals from
Multiple RRUs in One Cell is enabled.............................................................................................................................445
7.3.2.41 The number of extended cells that can be set up on the WBBPf board exceeds the publicized WBBPf
specifications....................................................................................................................................................................445
7.3.2.42 Cells enabled with Uplink Enhanced CELL_FACH fail to be deleted in specific scenarios.............................446
7.3.2.43 The Control Channel Parallel Interference Cancellation (phase 2) feature does not depend on the CCPIC
feature...............................................................................................................................................................................446
7.3.2.44 Downlink 64QAM occasionally becomes unavailable after the NodeB is upgraded to V100R009 in specific
scenarios...........................................................................................................................................................................447
7.3.2.45 Loads on the UMPTa/UTRPc board and the baseband board are unbalanced...................................................447
7.3.2.46 The mode of a remote cell cannot be changed by using the MOD ULOCELL command.................................448
7.3.2.47 After the CQI Adjustment Based on Dynamic BLER Target feature is activated, downloading small-sized files
by using HSDPA cannot reach the expected rate in a short period of time......................................................................448
7.3.2.48 Counters related to adaptive retransmission return incorrect values after the NodeB is upgraded or reset.......449
7.3.2.49 If a NodeB is configured with 24 cells, running the DSP ULOCELL command disconnects the Web LMT from
the U2000.........................................................................................................................................................................449
7.3.2.50 Uplink CE counters return incorrect values 0....................................................................................................450
7.3.2.51 After the E-FACH feature is activated, the VS.EFACH.Thruput counter returns an incorrect value................451
7.3.2.52 The VS.HSUPA.TurboIC.Number counter returns an incorrect value for the WBBPf board...........................451
7.3.2.53 E-RACH user access fails in cells in economical 4-channel demodulation mode.............................................452
7.3.2.54 The FDE feature yields insignificant gains when a WBBPd board is used and RTWP imbalance occurs........452
7.3.2.55 An exported configuration file cannot be activated on a NodeB that has been upgraded from V100R008 to
V100R009.........................................................................................................................................................................453
7.3.2.56 The U2000 fails to collect cell RF data of a NodeB configured with the UMPT..............................................453
7.3.2.57 ALM-28206 Local Cell Capability Decline is reported when it should not be..................................................454
7.3.2.58 There is a possibility that the RRU3804 and WRFU fail to be upgraded..........................................................454
7.3.2.59 The U2000 fails to deliver a power license in specific scenarios.......................................................................455
7.3.2.60 When HSUPA services are carried on the WBBPd board, inner loop power control occasionally does not
function well.....................................................................................................................................................................455
7.3.2.61 The NodeB performance counter VS.HSUPA.Boosting.UtilizeTimeRatio returns an inaccurate value...........456
7.3.2.62 The transmit power of a pRRU processing uplink and downlink services at peak rates becomes 0 occasionally.
..........................................................................................................................................................................................457
7.3.2.63 A cell fails to be activated if a long Ethernet cable not in use is connected to the RRU in the LampSite solution.
..........................................................................................................................................................................................457
7.3.2.64 The value returned by the VS.HSUPA.TTI2to10.Att counter is larger than expected on the WBBPd board if the
NodeB is upgraded from V200R014C00 to V100R009C00SPC150 or an earlier V100R009C00.................................458
Issue 01 (2015-05-08) Huawei Proprietary and Confidential xvii

Copyright © Huawei
BTS3900 V100R010C10SPC120
7.3.2.65 There is a low probability that the WBBPf board resets....................................................................................458

7.3.2.66 The drop rate of PS services on the UBBPd board increases.............................................................................459
7.3.2.67 The maintenance link for an RRU3804 is disconnected after the NodeB is upgraded to V200R014C00SPC350
..........................................................................................................................................................................................460
7.3.2.68 The call drop rate increases and the RRC connection setup success rate decreases after the Uplink Enhanced
CELL_FACH feature is activated.....................................................................................................................................460
7.3.3 Minor.......................................................................................................................................................................461
7.3.3.1 When VSWR tests are conducted on multiple frequencies, the VSWR indicator cannot properly reflect the test
result.................................................................................................................................................................................461
7.3.3.2 HSDPA Inter-Cell Power Sharing fails to take effect...........................................................................................461
7.3.3.3 Counters related to full buffer HSDPA throughput return inaccurate values for a cell........................................462
7.3.3.4 There is an extremely low probability that the main control board unexpectedly restarts...................................463
7.3.3.5 ALM-26765 RHUB Hardware Fault is reported when it should not be in the LampSite solution......................463
7.3.3.6 The upgrade and rollback process of a fully configured LampSite base station is time-consuming...................464
7.3.3.7 When DC-HSUPA UEs are at the cell edge or the secondary cells are congested, the UE throughput decreases.
..........................................................................................................................................................................................464
7.3.3.8 Uplink FFT frequency scan on pRRUs in the LampSite solution returns inaccurate interfering frequencies.....465
7.3.3.9 ALM-26529 RF Unit VSWR Threshold Crossed is occasionally reported when it should not be in the LampSite
solution.............................................................................................................................................................................466
7.3.3.10 Some pRRUs cannot be started after a LampSite base station is upgraded or reset..........................................466
7.3.3.11 The links between pRRUs and the BBU in the LampSite solution become faulty............................................467
7.3.3.12 WRFD-01061212 HSUPA Iub Flow Control in Case of Iub Congestion occasionally fails to take effect........467
7.3.3.13 The mechanism for checking the verification code on the LMT login page is incorrect after a base station
upgrade.............................................................................................................................................................................468
7.3.3.14 The RTWP reaches the peak value when UEs are moving at high speeds.........................................................468
7.3.3.15 Counters measuring HSUPA performance return inaccurate values..................................................................469
7.3.3.16 When the E-DPCCH Boosting feature is activated, HSUPA throughput decreases on the WBBPd board.......470
7.3.3.17 The inter-frequency handover success rate decreases if the Huawei RNC interworks with the RNC provided by
a peer vendor.....................................................................................................................................................................470
7.3.3.18 EVT-28200 Iub Common Procedure Failure Indication is frequently reported in specific scenarios...............471
7.3.3.19 The CE preemption rules for PS services need to be optimized........................................................................471
7.3.3.20 If baseband resources or RF resources for a local cell are insufficient, the NodeB falsely reports alarms related
to the local cell..................................................................................................................................................................472
7.3.3.21 Deployment check on a LampSite base station fails..........................................................................................473
7.3.3.22 In 0.5/0.5 configuration, some RRUs become unavailable when CPRI resources are insufficient...................473
7.3.3.23 The congestion detection algorithm needs to be optimized at the transport layer for HSUPA services............474
7.3.3.24 If the downlink baseband equipment includes a WBBPb board and other baseband processing units, such as
WBBPd, WBBPf, and UBBPd, downlink cell resources are unevenly distributed among these boards.........................474
7.3.3.25 Incorrect software is loaded to RF modules that are not reset after a hot swap of their fiber optic cables........475
7.3.3.26 The RRU type cannot be modified by running MML commands......................................................................476
7.3.3.27 The priority configured for OM packets does not take effect on the LMT........................................................476
7.3.3.28 The value range of Board RTWP is not properly set..........................................................................................477
7.3.3.29 The value returned by the VS.HSUPA.TTI2to10.Att counter is greater than expected if the NodeB is upgraded
from V200R014C00 to V100R009C00SPC120 or an earlier V100R009C00.................................................................477
Issue 01 (2015-05-08) Huawei Proprietary and Confidential xviii

Copyright © Huawei
BTS3900 V100R010C10SPC120
7.3.3.30 There is an extremely low probability that an RL fails to be added or reconfigured for UEs in an IC-capable
cell in heavy traffic scenarios...........................................................................................................................................478
7.3.3.31 The alarm cause for ALM-28203 Local Cell Unusable is inaccurate................................................................478
7.3.3.32 When MOCN is enabled, counters related to CE consumption on the WBBPf or UBBPd board return
inaccurate values for some operators...............................................................................................................................479
7.3.3.33 After a NodeB is upgraded to V100R009, link interruption occasionally occurs on a WRFU..........................479
7.3.3.34 When the NCP or CCP is configured with master and slave CP bearers and CP Switch Flag is set to Disable,
the NCP/CCP becomes abnormal after the NodeB is upgraded or reset..........................................................................480
7.3.3.35 No alarms are reported to inform operators of IP frame errors..........................................................................481
7.3.3.36 UEs experience access failures due to WebLMT login authentication..............................................................481
7.3.3.37 The OpenSSL is vulnerable to security threats...................................................................................................482
7.3.3.38 The WBBPf or UBBPd board occasionally experiences a channel reconfiguration failure for an uplink R99
user....................................................................................................................................................................................482
7.3.3.39 Values of the counters measuring IC on the WBBPf or UBBPd board are less than those on the WBBPd board
after both the IC and CCPIC features have been enabled for a NodeB...........................................................................483
7.3.3.40 The value range of Local Cell Radius is incorrect for a multi-RRU cell...........................................................483
7.3.3.41 There is a possibility that the access performance degrades in a cell using four receiving antennas................484
7.3.3.42 The counters measuring the average finger energy of antennas and the average ratio of the number of valid
antennas to the number of configured antennas return incorrect values..........................................................................485
7.3.3.43 HSDPA UEs performing a soft handover and delayed activation on the uplink dedicated channel sometimes
experience call drops on the the WBBPf or UBBPd board..............................................................................................485
7.3.3.44 The formulas for calculating the VS.UUlCoMPGroup.MaxUserNum, VS.BOARD.UsedHsdpaUserRatio.Max,
and VS.BOARD.UsedHsupaUserRatio.Max counters are exported when they should not be........................................486
7.3.3.45 The NodeB reports an invalid value of performance counters related to the uplink load after OLC event
measurement is enabled on the RNC side........................................................................................................................487
7.3.3.46 RRC connections fail to be set up because VLAN configurations of the WBBPb board occasionally fail to take
effect.................................................................................................................................................................................488
7.3.3.47 The performance of the WBBPf board is not high as expected when it works with the WBBPa, WBBPb, or
WBBPd board...................................................................................................................................................................488
7.3.3.48 The uplink transmission delay variation over the Iub interface is not measured accurately on the WBBPf board.
..........................................................................................................................................................................................489
7.3.3.49 The IC feature occasionally generates no gains for UEs served by a WBBPf4 board.......................................489
7.3.3.50 UTRAN cells sometimes do not recover immediately after non-UTRAN cells release RF or route resources.490
7.3.3.51 Cells are occasionally not evenly distributed among baseband processing units..............................................490
7.3.3.52 The RNC perceives that a logical cell is still usable even though frequencies or power is not properly
configured for this cell......................................................................................................................................................491
7.3.3.53 RF resources are not properly allocated after an RF unit is derated..................................................................491
7.3.3.54 The RTWP occasionally increases when UEs initially access a cell..................................................................492
7.3.3.55 Certain features are still available even though their licenses have entered the emergency state......................492
7.3.3.56 No possible causes are reported for ALM-28203 Local Cell Unusable.............................................................493
7.3.3.57 In certain scenarios, ALM-28206 Local Cell Capability Decline is not reported although it should be...........493
7.3.3.58 The VS.HSDPCCH.POWER counter returns an incorrect value when the WBBPf board is used...................494
7.3.3.59 ALM-26203 Board Software Program Error is occasionally falsely reported...................................................494
7.3.3.60 Root CSNs of parent and child alarms are not associated..................................................................................495
Issue 01 (2015-05-08) Huawei Proprietary and Confidential xix

Copyright © Huawei
BTS3900 V100R010C10SPC120
7.3.3.61 Names of measurement units, measurement objects, and measurement clusters in GSM, UMTS, and LTE are
normalized........................................................................................................................................................................495
7.3.3.62 Some faults in PnP deployment cannot be located.............................................................................................496
7.3.3.63 An RF module is reset when its working mode is modified...............................................................................496
7.3.3.64 Base station deployment fails when two base stations are cascaded by connecting FE/GE ports on the
UTRP/WMPT/LMPT/UMPT boards to form a VLAN in which each port uses multiple IP addresses..........................497
7.3.3.65 The base station restarts and services are interrupted when clock parameter settings are changed in batches
through the CME..............................................................................................................................................................497
7.3.3.66 The upgrade risk check result incorrectly indicates that the BootROM needs to be upgraded..........................498
7.3.3.67 Counters related to the Uplink Enhanced CELL_FACH feature return incorrect values..................................499
7.3.4 Suggestion...............................................................................................................................................................499
7.3.4.1 RRU3826 (code: 02310UPA) and RRU3824 (code: 02310UNY) differ from other RRU3826/RRU3824 units in
postprocessing of ALM-26529 RF Unit VSWR Threshold Crossed...............................................................................499
7.3.4.2 ALM-26522 RF Unit RX Channel RTWP/RSSI Unbalanced cannot be cleared.................................................500
7.3.4.3 ALM-26811 Configured Capacity Limit Exceeding Licensed Limit is reported when it should not be in specific
scenarios...........................................................................................................................................................................501
7.3.4.4 After a NodeB is upgraded to RAN16.0, the cause of ALM-28203 Local Cell Unusable changes.....................501
7.3.4.5 In BTS3900 V100R008C00SPC320 and later versions, the user allocation policy for the UBBPd board requires
modifications....................................................................................................................................................................502
7.3.4.6 The transmit power of pRRUs is reported as N/A occasionally in the LampSite solution..................................503
7.3.4.7 Rights management for the NIC tool is improper................................................................................................503
7.3.4.8 Logs are lost when the OM link becomes faulty..................................................................................................504
7.3.4.9 In the parameter reference, parameters Execute Result, Fail Reason, and Used Status are not associated with any
MML command................................................................................................................................................................504
7.3.4.10 There is a low probability that alarms are incorrectly reported when the optical power of optical modules is too
high...................................................................................................................................................................................505
7.3.4.11 The permission for uploading one-click logs is incorrectly configured.............................................................505
7.3.4.12 The UMTS or LTE side in a multimode base station incorrectly reports an alarm ALM-26200 Board Hardware
Fault..................................................................................................................................................................................506
7.3.4.13 In certain scenarios, modifying the maximum transmit power of a logical cell leads to abnormal cell output
power................................................................................................................................................................................506
7.3.4.14 The statistical method for the performance counters VS.HSUPA.PDUNum and VS.HSUPA.RetransPDUNum
requires optimization........................................................................................................................................................507
7.3.4.15 The MO Counter Reference does not include descriptions about MOs NODEBALGSIMLTTST and DLSIM.
..........................................................................................................................................................................................507
7.3.4.16 The transmission link is disconnected after the ADD SCTPPEER command is executed to add an SCTP peer.
..........................................................................................................................................................................................508
7.3.4.17 ALM25955-SCTP Link IP Address Unreachable is reported when an SCTP link that is configured with only a
pair of IP addresses cannot provide services....................................................................................................................508
7.3.4.18 When the NodeB serves remote cells, TP distribution is inaccurate..................................................................509
7.3.4.19 The NodeB fails to be upgraded to V100R009 or later versions in certain scenarios........................................509
7.3.4.20 LRRUs and LRFUs of NodeBs earlier than V100R008 support UMTS carriers with bandwidths narrower than
4.2 MHz............................................................................................................................................................................510
7.3.4.21 The storage security of the PreShareKey Attribute for the SECURITYTEMPLATE MO has been improved. 511
7.3.4.22 Parameter configuration for fault detection needs to be optimized....................................................................511
Issue 01 (2015-05-08) Huawei Proprietary and Confidential xx

Copyright © Huawei
BTS3900 V100R010C10SPC120
7.3.4.23 No alarms are reported to inform operators of inconsistency between RRU configurations and networking in
specific scenarios..............................................................................................................................................................512
7.3.4.24 Cells rarely become unavailable.........................................................................................................................512
7.3.4.25 When the CE Overbooking feature is activated and the uplink CE usage of a baseband processing unit is high,
UEs experience call drops unexpectedly..........................................................................................................................513
7.3.4.26 The algorithm for a synchronization/asynchronization decision on a UE using Uplink Enhanced CELL_FACH
needs to be improved........................................................................................................................................................513
7.3.4.27 Multi-RRU cells become unavailable due to insufficient licenses.....................................................................514
7.3.4.28 The UMPT and SMPT boards abnormally reset in heavy traffic scenarios.......................................................514
7.3.4.29 The VS.DlCode.Used.Max and VS.DlCode.Used.Mean counters return incorrect values................................515
7.3.4.30 The CCPIC efficiency of the Control Channel Parallel Interference Cancellation (phase 2) feature configured
on the WBBPd board is not calculated accurately............................................................................................................516
7.3.4.31 Users are not alerted when they are removing multi-carrier cell groups...........................................................516
7.3.4.32 Sleeping cell-related alarm and event reporting is inaccurate............................................................................517
7.3.4.33 One-click log export on the WebLMT provides fewer fields than the MML command ULD FILE.................517
7.3.4.34 Certain parameters for the MML command SET NODEBSMTHPWRPARA are assigned incorrect default
values................................................................................................................................................................................518
7.3.4.35 The SLC detection algorithm requires optimization to avoid incorrect detection results..................................518
7.3.4.36 The NodeB falsely reports ALM-28230 Base Station Service Overload...........................................................519
7.4 Known Issues..............................................................................................................................................................520
8 Operation and Maintenance Changes...................................................................................521

8.1 MML Command Changes..........................................................................................................................................521
8.2 Parameter Changes.....................................................................................................................................................521
8.3 Alarm Changes...........................................................................................................................................................522
8.4 Event Changes............................................................................................................................................................522
8.5 Counter Changes........................................................................................................................................................522
8.6 License Changes.........................................................................................................................................................523
8.7 Other Changes............................................................................................................................................................523
8.7.1 The IP PM session function enabled on the UMTS network is enhanced...............................................................523
8.7.2 Details of non-configuration parameters are displayed in the Parameter Reference and MML Command
Reference..........................................................................................................................................................................524
8.7.3 None NodeB service overload detection has been added........................................................................................524
8.7.4 The UDP port range for NodeB services changes...................................................................................................525
8.7.5 Data-related counters for the buffer of DC user queues may change in each carrier..............................................525
8.7.6 The AG collision function is deleted.......................................................................................................................526
A Obtaining Documentation......................................................................................................527
B Acronyms and Abbreviations.................................................................................................528
Issue 01 (2015-05-08) Huawei Proprietary and Confidential xxi

Copyright © Huawei
BTS3900 V100R010C10SPC120
(NodeB) Release Notes Version RequirementsVersion Requirements
1 Version Requirements
1.1 Product Version

Product NodeB
Name
Product BTS3900 WCDMA

Model BTS3900C WCDMA
BTS3900A WCDMA
BTS3900L WCDMA
BTS3900AL WCDMA
DBS3900 WCDMA
DBS3900 LampSite WCDMA
Product V100R010C10SPC120
Version
1.2 Software Versions

Software Version
LMT BTS3900 V100R010C10SPC120_NodeB(LMT)

CME Component CME_COMPONENT_UMTS_V100R010C10SPC120
Package CME_COMPONENT_UMTS_1U_V100R010C10SPC120
U2000 Mediation iManagerOSS_NodeB3900WCDMA_1U_MATCH_ENG_V200
R015C10SPC120_pkg
iManagerOSS_NodeB3900WCDMA_2U_MATCH_ENG_V200
R015C10SPC120_pkg
Issue 01 (2015-05-08) Huawei Proprietary and Confidential 1

Copyright © Huawei
BTS3900 V100R010C10SPC120
1.3 Hardware Versions

Module Software Hardware BootROM BootRO Remark
Name Version Version Version M s
Update
Require
d
WMPT 200.017.10.  256 01.316.01.001 No NA

120  257
 258
 260
UMPTa1 300.005.10.  2560 00.009.01.004 No NA
120  2576
UMPTa2 300.005.10.  2560 00.009.01.004 No N/A
120  2576
UMPTb1 300.005.10.  2561 00.011.01.001 No NA
120
UMPTb2 300.005.10.  2561 00.011.01.001 No N/A
120
UTRP2 300.005.10.  32 00.317.01.001 No NA
120
UTRP3 300.005.10.  48 00.317.01.001 No NA
120  49
 50
 56
UTRP4 300.005.10.  72 00.317.01.001 No NA
120
UTRP6 300.005.10.  96 00.317.01.001 No NA
120
UTRP9 300.005.10.  144 00.317.01.001 No NA
120
UTRPc 300.005.10.  3072 00.007.01.004 No NA
120  3073
WBBPa 200.017.10.  17664 01.013.01.001 No NA
120  17665
 17668
 17676
 17666
WBBPb1 200.017.10.  17921 01.200.01.002 No NA
120  17941

Copyright © Huawei
BTS3900 V100R010C10SPC120

Update
Require
d
WBBPb2 200.017.10.  17922 01.200.01.002 No NA

120  17942
WBBPb3 200.017.10.  17923 01.200.01.002 No NA
120  17943
WBBPb4 200.017.10.  17924 01.200.01.002 No NA
120  17944
WBBPd1 200.017.10.  17952 01.017.01.002 No NA
120  17955
WBBPd2 200.017.10.  17953 01.017.01.002 No NA
120
WBBPd3 200.017.10.  17954 01.017.01.002 No NA
120
USCU 8  USCU:200 NA No NA
 USCU:210
 USCU:220
 USCU:230
 USCU:240
 USCU:250
 USCU:260
 USCU:270
 USCU:280
 USCU:204
 USCU:214
 USCU:224
 USCU:234
 USCU:244
 USCU:254
 USCU:264
 USCU:274
 USCU:284
UCIU 200.017.10.  768 00.014.01.002 No NA
050
UBRIb 300.005.10.  2305 00.004.01.003 No NA
120
BBU3900 NA  V200R007 NA No NA

Copyright © Huawei
BTS3900 V100R010C10SPC120

Update
Require
d
RRU3804 1J.643.10.0  MRRU.HWEI.13 01.095.03.001 No NA

26 0313000
 MRRU.HWEI.13
0313100
 MRRU.HWEI.13
0313200
 MRRU.HWEI.15
0313000
 MRRU.HWEI.15
0313100
 MRRU.HWEI.15
0313200
 MRRU.HWEI.17
0313200
 MRRU.HWEI.23
0313100
 MRRU.HWEI.25
0313100
 MRRU.HWEI.43
0313100
 MRRU.HWEI.45
0313100
 MRRU.HWEI.53
0313100
 MRRU.HWEI.55
0313100
 ARFU.HWEI.130
313000
 ARFU.HWEI.130
313100
 ARFU.HWEI.130
313200
 ARFU.HWEI.150
313000
 ARFU.HWEI.150
313100
 ARFU.HWEI.150
313200
 ARFU.HWEI.170
313000
 ARFU.HWEI.170
313100

Copyright © Huawei
BTS3900 V100R010C10SPC120

Update
Require
d
 ARFU.HWEI.170
313200
 MRRU.HWEI.13
0310200
 MRRU.HWEI.13
0310300
 MRRU.HWEI.13
0310400
 MRRU.HWEI.13
0310F00
 MRRU.HWEI.13
0311500
 MRRU.HWEI.15
0310200
 MRRU.HWEI.15
0310300
 MRRU.HWEI.15
0310400
 MRRU.HWEI.15
0310F00
 MRRU.HWEI.15
0311500
 MRRU.HWEI.23
0310400
 MRRU.HWEI.23
0312400
 MRRU.HWEI.25
0310400
 MRRU.HWEI.25
0312400
 MRRU.HWEI.43
0310200
 MRRU.HWEI.43
0310300
 MRRU.HWEI.43
0310400
 MRRU.HWEI.43
0310F00
 MRRU.HWEI.43
0311500
 MRRU.HWEI.45
0310200

Copyright © Huawei
BTS3900 V100R010C10SPC120

Update
Require
d
 MRRU.HWEI.45
0310300
 MRRU.HWEI.45
0310400
 MRRU.HWEI.45
0310F00
 MRRU.HWEI.45
0311500
 MRRU.HWEI.53
0310200
 MRRU.HWEI.53
0310300
 MRRU.HWEI.53
0310400
 MRRU.HWEI.53
0310F00
 MRRU.HWEI.53
0311500
 MRRU.HWEI.53
0312400
 MRRU.HWEI.55
0310200
 MRRU.HWEI.55
0310300
 MRRU.HWEI.55
0310400
 MRRU.HWEI.55
0310F00
 MRRU.HWEI.55
0311500
 MRRU.HWEI.55
0312400
 ARFU.HWEI.130
310000
 ARFU.HWEI.130
310100
 ARFU.HWEI.130
310200
 ARFU.HWEI.130
310300
 ARFU.HWEI.130
312000

Copyright © Huawei
BTS3900 V100R010C10SPC120

Update
Require
d
 ARFU.HWEI.130
312100
 ARFU.HWEI.130
312200
 ARFU.HWEI.150
310000
 ARFU.HWEI.150
310100
 ARFU.HWEI.150
310200
 ARFU.HWEI.150
310300
 ARFU.HWEI.150
312000
 ARFU.HWEI.150
312100
 ARFU.HWEI.150
312200
 ARFU.HWEI.170
310000
 ARFU.HWEI.170
310100
 ARFU.HWEI.170
310200
 ARFU.HWEI.170
310300
 ARFU.HWEI.170
312000
 ARFU.HWEI.170
312100
 ARFU.HWEI.170
312200
 ARFU.HWEI.530
310000
 ARFU.HWEI.530
310200
 ARFU.HWEI.550
310000
 ARFU.HWEI.550
310200
 ARFU.HWEI.570
310000

Copyright © Huawei
BTS3900 V100R010C10SPC120

Update
Require
d
 ARFU.HWEI.570
310200
RRU3805 1J.651.10.0  MRRU.HWEI.x3 18.230.10.017 No NA
09 B130002
RRU3808 1J.651.10.0  LRRU.HWEI.x00 18.323.10.017 No NA
26 130100
 LRRU.HWEI.x00
130002
 LRRU.HWEI.x00
170100
 LRRU.HWEI.x00
130100
 LRRU.HWEI.x00
130002
 LRRU.HWEI.x00
170100
 LRRU.HWEI.x00
130100
 LRRU.HWEI.x00
130002
 LRRU.HWEI.x00
170100
RRU3824 1E.03B.10.  MRRU.HWEI.x5 1C.211.10.019 No NA
009 A13GX00
009 A13GX00
009 A130000
009 A130W00
RRU3832 1J.651.10.0  MRRU.HWEI.x5 1C.018.10.019 No NA
09 B13KY00
 MRRU.HWEI.x5
A13KY01
RRU3838 1J.651.10.0  MRRU.HWEI.x5 1C.018.10.019 No NA
09 B13DX00
RRU3841 NA  MRRU.HWEI.x5 NA No NA
A12B200
 MRRU.HWEI.x5

Copyright © Huawei
BTS3900 V100R010C10SPC120

Update
Require
d
A12BY00
 MRRU.HWEI.x5
A12F200
 MRRU.HWEI.x5
A12FY00
RRU3908 13.C3B.10.  MRRU.HWEI.C0 02.039.10.009 No NA
V1 009 2420000
 MRRU.HWEI.C5
2430000
 MRRU.HWEI.C5
2430100
 MRRU.HWEI.C5
2430200
 MRRU.HWEI.C5
2430300
 MRRU.HWEI.C5
2430400
 MRRU.HWEI.C5
2540000
 MRRU.HWEI.C5
2540100
 MRRU.HWEI.C5
2540200
 MRRU.HWEI.C5
2540300
 MRRU.HWEI.C5
2540400
 MRRU.HWEI.C5
2420000
 MRRU.HWEI.C5
2420100
 MRRU.HWEI.C5
2420200
 MRRU.HWEI.C5
2420300
 MRRU.HWEI.C5
2420400
 MRRU.HWEI.J02
420400
 MRRU.HWEI.J52
420400

Copyright © Huawei
BTS3900 V100R010C10SPC120

Update
Require
d
 MRRU.HWEI.J52
430000
 MRRU.HWEI.J52
430100
 MRRU.HWEI.J52
430200
 MRRU.HWEI.J52
430300
 MRRU.HWEI.J52
430400
 MRRU.HWEI.J52
540000
 MRRU.HWEI.J52
540100
 MRRU.HWEI.J52
540200
 MRRU.HWEI.J52
540300
 MRRU.HWEI.J52
540400
 MRRU.HWEI.J52
420000
 MRRU.HWEI.J52
420100
 MRRU.HWEI.J52
420200
 MRRU.HWEI.J52
420300
 MRRU.HWEI.G5
2430000
 MRRU.HWEI.G5
2430100
 MRRU.HWEI.G5
2430200
 MRRU.HWEI.G5
2430300
 MRRU.HWEI.G5
2430400
 MRRU.HWEI.G5
2540000
 MRRU.HWEI.G5
2540100

Copyright © Huawei
BTS3900 V100R010C10SPC120

Update
Require
d
 MRRU.HWEI.G5
2540200
 MRRU.HWEI.G5
2540300
 MRRU.HWEI.G5
2540400
 MRRU.HWEI.G5
2420000
 MRRU.HWEI.G5
2420100
 MRRU.HWEI.G5
2420200
 MRRU.HWEI.G5
2420300
 MRRU.HWEI.G5
2420400
 MRRU.HWEI.F5
2440000
 MRRU.HWEI.F5
2440100
 MRRU.HWEI.F5
2440200
 MRRU.HWEI.F5
2420000
 MRRU.HWEI.F5
2420100
 MRRU.HWEI.F5
2420200
 MRRU.HWEI.F5
2430000
 MRRU.HWEI.F5
2430100
 MRRU.HWEI.F5
2430200
 MRRU.HWEI.F5
2540000
 MRRU.HWEI.F5
2540100
 MRRU.HWEI.F5
2540200
 MRRU.HWEI.x3
0120001

Copyright © Huawei
BTS3900 V100R010C10SPC120

Update
Require
d
 MRRU.HWEI.x3
0120001
 MRRU.HWEI.x3
0120001
 MRRU.HWEI.x3
0140001
 MRRU.HWEI.x3
0140001
 MRRU.HWEI.x3
0130001
 MRRU.HWEI.x3
0130001
 MRRU.HWEI.x31
130002
RRU3908 18.83B.10.  MRRU.HWEI.x4 18.226.10.017 No NA
V2 009 A120007
 MRRU.HWEI.x4
A140008
 MRRU.HWEI.x4
A120109
 MRRU.HWEI.x4
A140109
 MRRU.HWEI.x8
A140001
 MRRU.HWEI.x4
A120007
 MRRU.HWEI.x4
A140008
 MRRU.HWEI.x4
A120109
 MRRU.HWEI.x4
A140109
 MRRU.HWEI.x8
A140001
 MRRU.HWEI.x8
0120000
 MRRU.HWEI.x8
0130000
 MRRU.HWEI.x8
A120000
 MRRU.HWEI.x8

Copyright © Huawei
BTS3900 V100R010C10SPC120

Update
Require
d
A130000
 MRRU.HWEI.x4
A130000
 MRRU.HWEI.x4
A130109
 LRRU.HWEI.x4A
121000
 LRRU.HWEI.x4A
130008
 LRRU.HWEI.x4A
131000
 MRRU.HWEI.x4
A120000
 MRRU.HWEI.x4
A120102
 MRRU.HWEI.x4
A130000
 MRRU.HWEI.x4
A130102
 MRRU.HWEI.x4
A140000
 MRRU.HWEI.x4
A140102
 MRRU.HWEI.x8
0120000
 MRRU.HWEI.x8
0130000
 MRRU.HWEI.x8
A120000
 MRRU.HWEI.x8
A130000
009 A123000
 MRRU.HWEI.x5
A123W00
 MRRU.HWEI.x5
B123000
 MRRU.HWEI.x5
B123W00
009 A120000

Copyright © Huawei
BTS3900 V100R010C10SPC120

Update
Require
d
 MRRU.HWEI.x5
A120W00
 MRRU.HWEI.x5
A122101
 MRRU.HWEI.x5
B120000
009 A120W00
 MRRU.HWEI.x5
A130000
 MRRU.HWEI.x5
A130W00
 MRRU.HWEI.x5
B120W00
 MRRU.HWEI.x5
B120W00
009 A12JX00
 MRRU.HWEI.x5
B12JX00
009 A124200
 MRRU.HWEI.x5
A124301
 MRRU.HWEI.x5
A124Y00
 MRRU.HWEI.x5
A12I200
 MRRU.HWEI.x5
A12IY00
009 A125Y00
MRFU V1 13.C3B.10.  MRFU.HWEI.C7 18.239.10.017 No NA
009 0420100
 MRFU.HWEI.C7
0420200
 MRFU.HWEI.C5
0420000
 MRFU.HWEI.C5
0420100

Copyright © Huawei
BTS3900 V100R010C10SPC120

Update
Require
d
 MRFU.HWEI.C5
0420200
 MRFU.HWEI.F70
430000
 MRFU.HWEI.F70
430100
 MRFU.HWEI.F70
430200
 MRFU.HWEI.F50
430000
 MRFU.HWEI.F50
430100
 MRFU.HWEI.F50
430200
 MRFU.HWEI.F70
420000
 MRFU.HWEI.F70
420100
 MRFU.HWEI.F70
420200
 MRFU.HWEI.F50
420000
 MRFU.HWEI.F50
420100
 MRFU.HWEI.F50
420200
 MRFU.HWEI.G7
0430100
 MRFU.HWEI.G7
0430200
 MRFU.HWEI.G7
0420100
 MRFU.HWEI.G7
0420200
 MRFU.HWEI.F70
420000
 MRFU.HWEI.F70
420100
 MRFU.HWEI.F70
420200
 MRFU.HWEI.F50
420000

Copyright © Huawei
BTS3900 V100R010C10SPC120

Update
Require
d
 MRFU.HWEI.F50
420100
 MRFU.HWEI.F50
420200
 GRFU.HWEI.C70
540000
 GRFU.HWEI.C70
540100
 GRFU.HWEI.C70
540200
 GRFU.HWEI.C50
540000
 GRFU.HWEI.C50
540100
 GRFU.HWEI.C50
540200
 GRFU.HWEI.F70
540000
 GRFU.HWEI.F70
540100
 GRFU.HWEI.F70
540200
 GRFU.HWEI.F50
540000
 GRFU.HWEI.F50
540100
 GRFU.HWEI.F50
540200
 GRFU.HWEI.G70
540100
 GRFU.HWEI.G70
540200
 MRFU.HWEI.D7
0420100
 MRFU.HWEI.C5
2420100
 MRFU.HWEI.C5
2430000
 MRFU.HWEI.F52
420000
 MRFU.HWEI.F50
420000

Copyright © Huawei
BTS3900 V100R010C10SPC120

Update
Require
d
 MRFU.HWEI.F50
420100
 MRFU.HWEI.F50
420200
 MRFU.HWEI.F70
420000
 MRFU.HWEI.F70
420100
 MRFU.HWEI.F70
420200
 MRFU.HWEI.C5
0430000
 MRFU.HWEI.C5
0430100
 MRFU.HWEI.C5
0430200
 MRFU.HWEI.C7
0420000
 MRFU.HWEI.C7
0430000
 MRFU.HWEI.C7
0430100
 MRFU.HWEI.C7
0430200
MRFU V2 1E.03B.10.  MRFU.HWEI.x6 1C.211.10.019 No NA
009 B125X00
MRFU V2 13.C3B.10.  MRFU.HWEI.x3 18.231.10.017 No NA
009 A122102
 MRFU.HWEI.x3
C122102
 MRFU.HWEI.x3
D122102
 MRFU.HWEI.x8
A122102
 MRFU.HWEI.x8
C122102
 MRFU.HWEI.x8
D122102
 MRFU.HWEI.xa
A122102
 MRFU.HWEI.xa

Copyright © Huawei
BTS3900 V100R010C10SPC120

Update
Require
d
C122102
 GRFU.HWEI.x3A
142102
 GRFU.HWEI.x3C
142102
 GRFU.HWEI.x3D
142102
 GRFU.HWEI.x8A
142102
 GRFU.HWEI.x8C
142102
 GRFU.HWEI.x8D
142102
 GRFU.HWEI.xaA
142102
 GRFU.HWEI.xaC
142102
 MRFU.HWEI.x30
122102
 MRFU.HWEI.x80
122102
 MRFU.HWEI.xa0
122102
 GRFU.HWEI.x30
142102
 GRFU.HWEI.x80
142102
 GRFU.HWEI.xa0
142102
 MRFU.HWEI.x8
C122103
 MRFU.HWEI.x8
D122103
 MRFU.HWEI.x8
D122203
 MRFU.HWEI.x8
C122303
 MRFU.HWEI.x8
D122303
 GRFU.HWEI.x8C
142303
 GRFU.HWEI.x8D

Copyright © Huawei
BTS3900 V100R010C10SPC120

Update
Require
d
142303
 MRFU.HWEI.x8
D122403
 GRFU.HWEI.x8D
142602
 MRFU.HWEI.x8
D122602
 MRFU.HWEI.x8
A122502
 MRFU.HWEI.x3
D122202
 MRFU.HWEI.x3
A122102
 MRFU.HWEI.x3
C122102
 MRFU.HWEI.x3
D122102
 MRFU.HWEI.x8
A122102
 MRFU.HWEI.x8
C122102
 MRFU.HWEI.x8
D122102
 MRFU.HWEI.xa
A122102
 MRFU.HWEI.xa
C122102
 MRFU.HWEI.x30
122102
 MRFU.HWEI.x80
122102
 MRFU.HWEI.xa0
122102
 MRFU.HWEI.x8
D122203
 MRFU.HWEI.x8
C122303
 MRFU.HWEI.x8
D122303
 MRFU.HWEI.x8
D122403
 MRFU.HWEI.x8

Copyright © Huawei
BTS3900 V100R010C10SPC120

Update
Require
d
D122602
 MRFU.HWEI.x8
A122502
 MRFU.HWEI.x3
D122202
 MRFU.HWEI.x30
132102
 MRFU.HWEI.x3
A132102
 MRFU.HWEI.x3
C132102
 MRFU.HWEI.x3
D132102
 MRFU.HWEI.x80
132102
 MRFU.HWEI.x8
A132102
 MRFU.HWEI.x8
C132102
 MRFU.HWEI.x8
D132102
 MRFU.HWEI.x8
C132303
 MRFU.HWEI.x8
D132303
 MRFU.HWEI.x30
122102
 MRFU.HWEI.x30
132102
 MRFU.HWEI.x3
A122102
 MRFU.HWEI.x3
A132000
 MRFU.HWEI.x3
A132102
 MRFU.HWEI.x3
C122102
 MRFU.HWEI.x3
C132102
 MRFU.HWEI.x3
D122102
 MRFU.HWEI.x3

Copyright © Huawei
BTS3900 V100R010C10SPC120

Update
Require
d
D132102
 MRFU.HWEI.x80
122102
 MRFU.HWEI.x80
132102
 MRFU.HWEI.x8
A122102
 MRFU.HWEI.x8
A122502
 MRFU.HWEI.x8
A132000
 MRFU.HWEI.x8
A132102
 MRFU.HWEI.x8
C122102
 MRFU.HWEI.x8
C122303
 MRFU.HWEI.x8
C132102
 MRFU.HWEI.x8
C132303
 MRFU.HWEI.x8
D122102
 MRFU.HWEI.x8
D122202
 MRFU.HWEI.x8
D122303
 MRFU.HWEI.x8
D122403
 MRFU.HWEI.x8
D132102
 MRFU.HWEI.x8
D132303
MRFUd 1E.03B.10.  MRFU.HWEI.x6 1C.206.10.019 No NA
009 A120000
 MRFU.HWEI.x6
A120W00
 MRFU.HWEI.x6
B120000
 MRFU.HWEI.x6
B120W00

Copyright © Huawei
BTS3900 V100R010C10SPC120

Update
Require
d
 MRFU.HWEI.x6
B121000
MRFUe 1E.03B.10.  MRFU.HWEI.x6 1C.206.10.019 No NA
009 A121000
 MRFU.HWEI.x6
A121W01
 MRFU.HWEI.x6
A122000
 MRFU.HWEI.x6
A122W00
 MRFU.HWEI.x6
B121000
 MRFU.HWEI.x6
B121W01
 MRFU.HWEI.x6
B122000
 MRFU.HWEI.x6
B122W00
WRFUd 1E.03B.10.  ARFU.HWEI.x6A 1C.206.10.019 No NA
009 130000
 ARFU.HWEI.x6A
130W00
WRFUa 1E.03B.10.  ARFU.HWEI.x6A 1C.211.10.019 No NA
009 135X00
UTRPa 300.005.10.  51 NA No NA
120  UTRP.PCB:33
WBBPf 200.017.10.  21760 01.001.01.015 No NA
120  21761
 21762
 21763
 21764
 WBBPb.PCB:550
0
 WBBPb.PCB:550
1
 WBBPb.PCB:550
2
 WBBPb.PCB:550
3

Copyright © Huawei
BTS3900 V100R010C10SPC120

Update
Require
d
 WBBPb.PCB:550
4
009 A12MX01
AAU3902 31.52D.10.  AAMU.HWEI.x 31.009.10.019 No NA
028 W0121W00
 AAMU.HWEI.x
W0121W0F
 AARU.HWEI.xV
A130W06
 AARU.HWEI.xV
A131W06
 AARU.HWEI.xV
A120W06
 AARU.HWEI.xV
A121W06
 AARU.HWEI.xV
A130Y06
 AARU.HWEI.xV
A120Y06
RXU06 1E.03B.10.  MRRU.HWEI.x5 1C.007.10.019 No NA
009 012RX00
 MRRU.HWEI.x5
012RX01
BBU3910 NA  NA NA No NA
UBBPd 300.005.10.  5376 00.010.01.001 No NA
120  5377
pRRU 19.362.60.0  MPRU.HWEI.x00 19.372.30.060 No NA
70 120000
 MPRU.HWEI.x00
120101
 MPRU.HWEI.x00
130000
 MPRU.HWEI.x00
130101
 MPRU.HWEI.x00
170000
 MPRU.HWEI.x00
170101

Copyright © Huawei
BTS3900 V100R010C10SPC120

Update
Require
d
RHUB 19.361.60.0  RHUB.HWEI.x30 19.371.30.060 No NA

70 120000
 RHUB.HWEI.x30
120002
UMDU 300.005.10.  5889 00.014.01.001 No NA
120
RRU3952 1J.53B.10.0  MRRU.HWEI.xA 1C.037.10.019 No NA
09 A122900
 MRRU.HWEI.xA
A12AJ00
09 A12A800
 MRRU.HWEI.xA
A12A600
AAU3920 1J.53B.10.0  MRRU.HWEI.xZ NA No NA
09 A12100F
 MRRU.HWEI.xZ
A121100
09 A127K00
 MRRU.HWEI.xA
A127C00
m 09 A12LM00
pRRU390 NA  MRRU.HWEI.x4 NA No NA
2 0120000
 MRRU.HWEI.x6
0120000
1.4 Related Product Versions

Product Version Remark
U2000 iManager U2000 V200R015C10SPC230 and later. -

iManager U2000 V200R015C10SPC230 is
recommended.

Copyright © Huawei
BTS3900 V100R010C10SPC120
Product Version Remark
CME iManager U2000-CME V200R015C10SPC230 and -

later.
iManager U2000-CME V200R015C10SPC230 is
recommended.
BSC6900 BSC6900 V900R017C10SPC500 and later. -
BSC6900 V900R017C10SPC500 is recommended.
BSC6910 BSC6910 V100R017C10SPC500 and later. -
BSC6910 V100R017C10SPC500 is recommended.
WA173DD- WA173DD-NE V100R006C00SPC010 or later. The Wi-Fi
NE WA173DD-NE V100R006C00SPC010 is daughter board
recommended. on the
pRRU3901
of a LampSite
base station
1.5 Related Documentation

Solution Product Version Documentation Website
Version
SRAN10.1 BTS3900 (For Customer)3900 For details, see "A

V100R010C10SPC1 Series Base Station Obtaining
20 Product Documentation"
Documentation(V100R
010C10_02)-EN
SRAN10.1 BTS3900 (For Customer)3900
V100R010C10SPC1 Series Base Station
00 Product
Documentation(V100R
010C10_01)-EN
V100R010C10SPC0 Series Base Station
50 Product
Documentation(V100R
010C10_Draft B)-EN
V100R010C10 Series Base Station
Product
Documentation(V100R
010C10_Draft A)-EN

Copyright © Huawei
BTS3900 V100R010C10SPC120
1.6 Virus Scan Result

This software package has been scanned by the Avira AntiVir Server,Symantec Endpoint
Protection,McAfee VirusScan Enterprise,TrendMicro OfficeScan antivirus software and no
risks were found. The following table lists the virus scan results.
Antivirus Antivirus Antivirus Time of Scan Result

Software Software Database
Name Version Version
Avira AntiVir 8.03.30.028 7.11.229.08 2015-05-07 Normal

Server 8
McAfee 5700:7163 7792:0 2015-05-07 Normal
VirusScan
Enterprise
Symantec 12.1.2015.2015 2015-05- 2015-05-07 Normal
Endpoint 04r37
Protection
TrendMicro 9.750.1007 1165100 2015-05-07 Normal
OfficeScan
1.7 Important Notes

None.

Copyright © Huawei
BTS3900 V100R010C10SPC120
(NodeB) Release Notes Version CompatibilityVersion Compatibility
2 Version Compatibility
2.1 Software Version Compatibility

The V100R010C10SPC120 Release version is compatible with all the V100R008 and later
product versions.
2.2 Hardware Version Compatibility

Table 2-1 describes compatibility between the hardware and the software versions.
Y: compatible; N: incompatible
Table 1.1 Hardware version compatibility

Module V100R010C10 V100R009C00 V100R008C00
Name
WMPT Y Y Y
UMPTa1 Y Y Y
UMPTa2 Y Y Y
UMPTb1 Y Y Y
UMPTb2 Y Y Y
UTRP2 Y Y Y
UTRP3 Y Y Y
UTRP4 Y Y Y
UTRP6 Y Y Y
UTRP9 Y Y Y
UTRPc Y Y Y

Copyright © Huawei
BTS3900 V100R010C10SPC120

Name
UTRPa Y Y N/A
WBBPa Y Y Y
WBBPb1 Y Y Y
WBBPb2 Y Y Y
WBBPb3 Y Y Y
WBBPb4 Y Y Y
WBBPd1 Y Y Y
WBBPd2 Y Y Y
WBBPd3 Y Y Y
BBU3900 Y Y Y
RRU3801E Y Y Y
RRU3804 Y Y Y
RRU3805 Y Y Y
RRU3806 Y Y Y
RRU3808 Y Y Y
RRU3824 Y Y Y
RRU3826 Y Y Y
RRU3828 Y Y Y
RRU3829 Y Y Y
RRU3832 Y Y Y
RRU3838 Y Y Y
RRU3841 Y Y Y
RRU3908 Y Y Y
V1
RRU3908 Y Y Y
V2
RRU3926 Y Y Y
RRU3928 Y Y Y
RRU3929 Y Y Y
RRU3936 Y Y Y
RRU3942 Y Y Y

Copyright © Huawei
BTS3900 V100R010C10SPC120

Name
RRU3961 Y Y Y
MRFU V1 Y Y Y
MRFU V2 Y Y Y
MRFUd Y Y Y
MRFUe Y Y Y
WRFU Y Y Y
WRFUd Y Y Y
WRFUe Y Y Y
WRFUa Y Y Y
UTRPa Y Y Y
WBBPf Y Y Y
RRU3938 Y Y Y
AAU3902 Y Y Y
pRRU Y Y Y
RHUB Y Y Y
UBBP Y Y Y
UMDU Y N/A N/A
RRU3952 Y N/A N/A
RRU3953 Y N/A N/A
AAU3920 Y N/A N/A
RRU3962 Y N/A N/A
RRU3952m Y N/A N/A
pRRU3902 Y N/A N/A

Copyright © Huawei
Changes from V100R010C10SPC100 to
BTS3900 V100R010C10SPC120 V100R010C10SPC120Changes from
(NodeB) Release Notes V100R010C10SPC100 to V100R010C10SPC120
3 Changes from V100R010C10SPC100 to

V100R010C10SPC120
3.1 Change Summary

Capacity and Performance
Compared with those in V100R010C10SPC100, capacity and performance remain unchanged
in V100R010C10SPC120. For details, see 3.1.1 Capacity and Performance.
Hardware
Compared with those in V100R010C10SPC100, no board types have been added to and no
board types have been modified in V100R010C10SPC120. For details, see 3.1.2 Hardware.
Features and Functions

Compared with those in V100R010C10SPC100, no features and functions have been added, 2
features and functions have been modified, and no features and functions have been deleted in
V100R010C10SPC120. 3.1.3 Features and Functions provides the following information
about new or modified features and functions:
 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 V100R010C10SPC100, 1 critical issues, 7 major issues, 7 minor
issues, and 11 suggestion-level issues have been resolved in V100R010C10SPC120. 3.1.4
Resolved Issues provides the following information about resolved issues:
 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

Copyright © Huawei
Operation and Maintenance

 Configuration Management
Compared with those in V100R010C10SPC100, configuration management functions
remain changed in V100R010C10SPC120. 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 V100R010C10SPC100, performance management functions
remain changed in V100R010C10SPC120. For details about counter changes, see 8.5
Counter Changes.
 Fault Management
Compared with those in V100R010C10SPC100, fault management functions remain
changed in V100R010C10SPC120. For details about alarm and event changes, see 8.3
Alarm Changes and 8.4 Event Changes, respectively.
 License Management
Compared with those in V100R010C10SPC100, license management functions remain
unchanged in V100R010C10SPC120. For details about license changes, see 8.6 License
Changes.
Related documentation
Compared with those in V100R010C10SPC100, document organization and document
templates have changed in V100R010C10SPC120. For details, see 3.1.6 Related
Documentation.
3.1.1 Capacity and Performance

Impact on Capacity and Performance
None.
3.1.2 Hardware
New Hardware
None.
Modified Hardware
None.
Deleted Hardware
None
3.1.3 Features and Functions

This section provides the following aspects of all feature and function changes from BTS3900
V100R010C10SPC120 to BTS3900 V100R010C10SPC100 :
 Change type

Copyright © Huawei
 Feature description
 Impact on capacity and performance
 (Optional) RAT
For details about these changes, see Summary of Feature and Function Changes in BTS3900
V100R010C10SPC120 (NodeB).xls.
For features changes in the Node, see 3.2.1 Feature and Function Changes.
For features changes in the NodeBFunction, see 3.3.1 Feature and Function Changes.
3.1.4 Resolved Issues

This section provides the following aspects of issues resolved in BTS3900
V100R010C10SPC120 but unresolved in BTS3900 V100R010C10SPC100 :
 Trouble ticket number
 Issue description
 Severity
 Solution impact
 Parameter control
 (Optional) RAT
For details about these issues, see Summary of Resolved Issues in BTS3900
For Resolved Issues in the Node, see 3.2.2 Resolved Issues.
For Resolved Issues in the NodeBFunction, see 3.3.2 Resolved Issues.
3.1.5 Operation and Maintenance

3.1.5.1 Configuration Management
Compared with those in V100R010C10SPC100, configuration management functions remain
unchanged in V100R010C10SPC120. For details about changes to MML commands and
parameters, see 8.1 MML Command Changes and 8.2 Parameter Changes.
3.1.5.2 Performance Management

Compared with those in V100R010C10SPC100, performance management functions remain
unchanged in V100R010C10SPC120. For details about counter changes, see 8.5 Counter
Changes.
3.1.5.3 Fault Management

unchanged in V100R010C10SPC120. For details about changes to alarms and events, see 8.3
Alarm Changes and 8.4 Event Changes.

Copyright © Huawei
3.1.5.4 License Management

unchanged in V100R010C10SPC120. For details about changes to license control items, see
8.6 License Changes.
3.1.6 Related Documentation

Change Description Change Reason Documentation
Version
Added Macro Base Illustrated macro base stations with (For Customer)3900
Station Technical figures. Series Base Station
Poster Product
Documentation(V100R01
Added BBU Technical Illustrated BBU with figures. 0C10_02)(HDX)-EN
Poster
Added Radio Illustrated RF modules with
Frequency Technical figures.
Poster
For details about documentation changes, see (For Customer)3900 Series Base Station
Product Documentation(V100R010C10_02)(HDX)-EN.
3.2 Node
3.2.1 Feature and Function Changes
3.2.1.1 New Features and Functions
None.
3.2.1.2 Modified Features and Functions

3.2.1.2.1 REQ493088 Optimizing Batch Query Results of Optical Modules
Description
The following items are added to the DSP SFP command output: upper receive power
threshold, lower receive power threshold, upper transmit power threshold, and lower transmit
power threshold.
Implementation
Add the following information to the DSP SFP command output:
 Receive Power Upper Threshold(0.1microwatt)
 Receive Power Lower Threshold(0.1microwatt)
 Transmit Power Upper Threshold(0.1microwatt)

Copyright © Huawei
 Transmit Power Lower Threshold(0.1microwatt)

 Receive Power Upper Threshold(0.01dBm)
 Receive Power Lower Threshold(0.01dBm)
 Transmit Power Upper Threshold(0.01dBm)
 Transmit Power Lower Threshold(0.01dBm)

 Impact on capacity
None
 Impact on 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
None
 Impact on configuration management
None
 Impact on performance management
None
 Impact on fault management
None
Impact on Other Features

 Prerequisite features
None
 Mutually exclusive features
None
 Impacted features
None

Copyright © Huawei
Related Operations
Run the following command to query the dynamic information of optical or electrical
modules in batches:
DSP SFP: CN=0, SRN=0, SN=0;
Trouble Ticket Number

None
Feature ID
None
3.2.1.3 Deleted Features and Functions

None.

3.2.2.1 Critical
3.2.2.1.1 UMTS cells served by different subracks are unavailable in scenarios of BBU
interconnection involving BBU3910.
Trouble DTS: DTS2015040901845

Ticket
Number
Description Condition:
 A UBBPd board is configured in a BBU3910 for BBU interconnection.
 Any of the following slot configurations apply to the BBU3910.
 The UBBPd board is configured in slot 2 or 3 and slot 0 is occupied.
 UMTS cells served by different subracks are configured.
Symptom: ALM-28203 Local Cell Unusable is reported with the specific
problem of "Downlink RF Resource Unavailable".
Impact: UMTS local cells become unavailable.
Severity Critical
Root Cause The EIA and IDX2 ports have the same ID.
Solution The EIA port ID has been changed to be different from the IDX2 port ID.
Solution None
Impact
Test Case ID ATP-2015040901845

Copyright © Huawei
3.2.2.2 Major
3.2.2.2.1 The CPU usage is high when pRRUs are fully configured and the served cells
are established but not activated in the LampSite solution.

Ticket
Number
Description Condition: In the LampSite solution, pRRUs are fully configured and the
served cells are established but not activated.
Symptom: The CPU usage approaches 30%.
Impact: Execution of commands related to the SECTOR,
SECTOREQM, and BASEBANDEQM MODs timed out.
Severity Major
Root Cause The licensed UMTS+LTE pRRUs will trigger cell reallocation upon
license status changes. The cell reallocation process, however, is time-
consuming.
The LampSite base station uses a defective internal mechanism to
determine license status. As a result, such pRRUs obtain incorrect license
status and trigger redundant cell reallocation processes, causing the
message queue to be fully occupied.
Solution The defective internal mechanism has been corrected to provide correct
license status.
Solution The CPU usage returns to a reasonable level. Commands related to the
Impact SECTOR, SECTOREQM, and BASEBANDEQM MOs are executed
successfully.
3.2.2.2.2 The base station deployment failure is caused by the incorrect gateway IP
address contained in the DHCP packet received by the base station.

Ticket
Number
Descriptio Condition: A DHCP relay is not on the same network segment as the base
n station. During the base station deployment, the base station receives a
DHCP packet in which the gateway IP address is not on the same network
segment as the interface IP address of the base station.
Symptom: After the base station receives the DHCP packet containing the
incorrect gateway IP address, the base station deployment is terminated.
Impact: The base station deployment fails.
Severity Major
Root Cause The base station does not check the DHCP packet in which the gateway IP

Copyright © Huawei
address is not on the same network segment as the interface IP address of

the base station.
Solution The mechanism of processing DHCP packets has been modified. During
base station deployment, the base station does not process DHCP packets in
which the gateway IP address is not on the same network segment as the
interface IP address of the base station, and waits for new DHCP packets.
Solution None
Impact
Test Case ATP-2015040700639
3.2.2.3 Minor
3.2.2.3.1 The counters indicating the maximum and average available uplink
bandwidths of a transport resource group return incorrect values.

Ticket
Number
Description Condition: The TX bandwidth of a transport resource group with the

bearer type of ATM is smaller than the physical port bandwidth.
Symptom: After the MOD RSCGRP command is executed to increase
the TX bandwidth of the transport resource group, values of the
following counters do not increase accordingly:
 VS.IUB.FlowCtrol.UL.AdjBW.LgcPort1.Avg
 VS.IUB.FlowCtrol.UL.AdjBW.LgcPort1.Max
 VS.IUB.FlowCtrol.UL.AdjBW.LgcPort2.Avg
 VS.IUB.FlowCtrol.UL.AdjBW.LgcPort2.Max
 VS.RscGroup.FlowCtrol.UL.AdjBW.Avg
 VS.RscGroup.FlowCtrol.UL.AdjBW.Max
Impact: The incorrect values returned by these counters affect user
experience.
Severity Minor
Root Cause The mechanism to collect information about bandwidth changes of the
transport resource group is defective.
Solution The defective mechanism has been corrected so that bandwidths of the
transport resource group are correctly obtained upon status changes.
Solution None
Impact

Copyright © Huawei
3.2.2.4 Suggestion
3.2.2.4.1 In certain scenarios, no alarm is reported to indicate a low access success rate.
Trouble iCare: 2962096

Ticket DTS: DTS2015030905737
Number
Description Condition: Some packets are lost, causing related UEs to fail to access
the network.
Symptom: The access success rate is low, but no alarm is reported.
Impact: Users cannot be promptly alerted, causing a delay in fault
handling.
Severity Suggestion
Root Cause In this instance, the transmission module is faulty.
Solution The NodeB now periodically collects statistics about the packets
transmitted and received by the transmission module and calculates the
packet loss rate on the transmission module. If the packet loss rate
reaches the pre-defined threshold of 1%, ALM-26200 Board Hardware
Fault or ALM-26215 Inter-Board Service Link Failure is reported,
depending on fault types.
Solution None
Impact
3.2.2.4.2 The name of the IPSECSWITCH parameter under associated MOs is inaccurate
in endpoint mode.

Ticket
Number
The following commands are executed:
 ADD SCTPHOST
 ADD SCTPPEER
 ADD USERPLANEHOST
 ADD USERPLANEPEER
Symptom: The name of the IPSECSWITCH parameter (IPsec switch)
is inaccurate, which is incorrectly considered as the IPsec function
switch.
Impact: The incorrect parameter name may mislead users.
Severity Suggestion
Root Cause The IPsec switch in the preceding MML commands indicates the IPsec

Copyright © Huawei
automatic configuration switch used to automatically configure

associated MOs such as IPSECBIND, IPSECPOLICY, IKEPEER,
ACL, and ACLRULE. However, this switch is incorrectly considered as
the IPsec function switch.
Solution The name of the IPSECSWITCH parameter is now changed to "IPsec
automatic configuration switch".
Solution None
Impact
Test Case ID ATP- 2015020606082
3.2.2.4.3 The DSP RRU command output shows that an MPMU is connected to two
Ethernet cables when it is connected to only one Ethernet cable in load-sharing
networking.

Ticket
Number
An MPMU is connected to only one Ethernet cable in load-sharing
networking.
The DSP RRU command is executed to query the connection direction of
the MPMU.
Symptom: The connection direction (specified by the Access Direction
parameter) of the MPMU is displayed as "Access from both ends of the
ring".
Impact: The displayed connection direction of the MPMU is incorrect.
Severity Suggestion
Root Cause If the CPRI_E port status on the RHUB is 0, the CPRI_E port does not
work properly.
If the port status is not 0, the port works properly.
The current default CPRI_E port status is 0xFFFFFFFF, which is
invalid.
The invalid value 0xFFFFFFFF is not 0. In this case, the NodeB
incorrectly considers that the CPRI_E port still works properly. As a
result, when the MPMU is connected to only one Ethernet cable, the DSP
RRU command output shows that "Access Direction" is "Access from
both ends of the ring".
Solution The default CPRI_E port status is now changed to 0.
Solution The DSP RRU command output shows that the connection direction of
Impact the MPMU is correct.

Copyright © Huawei
3.2.2.4.4 A UMTS cell on a LampSite base station fails to be activated, and the base
station reports ALM-28211 Cell Configuration Abnormal.

Ticket
Number
Description Condition: Two UMTS cells on a LampSite base station contain the same
pRRU, which has different cascading combination locations in the two
cells.
Symptom: The second UMTS cell cannot be activated, and the base
station reports ALM-28211 Cell Configuration Abnormal.
Impact: Services are not available on the second UMTS cell.
Severity Suggestion
Root Cause In versions earlier than BTS3900 V100R010C01SPC120, the following

limitation applies: A pRRU cannot have different cascading combination
locations in two cells.
Solution The software process has been modified to cancel the preceding limitation.
Solution None
Impact

ID
3.2.2.4.5 The value of the VS.IPPM.Peer.Peak.Pkts.RateRx counter is not correctly

displayed.
Trouble DTS2015031206654
Ticket
Number
Descriptio Condition: The reported value of the VS.IPPM.Peer.Peak.Pkts.RateRx

n counter consists of 13 digits (including 3 decimal places).
Symptom: The value of the VS.IPPM.Peer.Peak.Pkts.RateRx counter is not
correctly displayed.
Impact: The value of the VS.IPPM.Peer.Peak.Pkts.RateRx counter cannot
be viewed.
Severity Suggestion
Root Cause The value length of the VS.IPPM.Peer.Peak.Pkts.RateRx counter does not
meet the requirements.
Solution The value length of the VS.IPPM.Peer.Peak.Pkts.RateRx counter has been
changed to 20 digits.
Solution None
Impact

Copyright © Huawei
3.2.2.4.6 When the STR CFGCHK command is executed, ALM-26245 Configuration Data
Inconsistency that is reported because RF modules do not support settings of certain
parameters is incorrectly cleared.
Ticket DTS2015041402291
Number
Descriptio Condition: RF modules do not support the setting of the VSWR alarm
n post-processing switch, VSWR alarm threshold, RF Desensitivity, Low
Current Protect Switch, or PA Efficiency Improvement Switch
parameter. Alternatively, RF modules configured with the UMTS mode do
not support the value 1 of the ALD Reuse Flag parameter.
Symptom: After RF modules are started, ALM-26245 Configuration Data
Inconsistency is reported. After the STR CFGCHK command is executed,
Check Result in the command output is Consistent, and ALM-26245
Configuration Data Inconsistency is cleared.
Impact: ALM-26245 Configuration Data Inconsistency is incorrectly
cleared.
Severity Suggestion
Root Cause The mechanism of generating and clearing ALM-26245 Configuration Data
Inconsistency used during RF module startup is different from that used
during RF module configuration check.
Solution The mechanism of generating and clearing ALM-26245 Configuration Data
Inconsistency used during RF module configuration check has been
modified. If the VSWR alarm post-processing switch, VSWR alarm
threshold, RF Desensitivity, Low Current Protect Switch, PA Efficiency
Improvement Switch, and ALD Reuse Flag parameters are all set to the
default values, Check Result in the STR CFGCHK command output is set
to Consistent. If any of the preceding parameters is not set to the default
value, Check Result in the STR CFGCHK command output is set to
Inconsistent and ALM-26245 Configuration Data Inconsistency is
reported.
Solution After the STR CFGCHK command is executed, Check Result in the
Impact command output is set to Inconsistent and ALM-26245 Configuration Data
Inconsistency is still reported if the following conditions are met:
 RF modules do not support the setting of the VSWR alarm post-
processing switch, VSWR alarm threshold, RF Desensitivity, Low
Current Protect Switch, or PA Efficiency Improvement Switch
parameter, or RF modules configured with the UMTS mode do not
support the value 1 of the ALD Reuse Flag parameter.
 Any of the preceding parameters is not set to the default value.

Copyright © Huawei
3.2.2.4.7 After the STR RFTEST command is executed with Test Type set to
PIMON2TONE_2TONE or PIMON2TONE_SWEEP, the intermodulation interference
detection results do not contain IM Product Threshold
Trouble Ticket DTS2015042503102

Number
Description Condition: The STR RFTEST command is executed with Test Type
set to PIMON2TONE_2TONE or PIMON2TONE_SWEEP.
Symptom: The intermodulation interference detection results do not
contain IM Product Threshold.
Impact: Users cannot determine whether to adjust IM Product
Threshold based on the intermodulation interference detection results.
Severity Suggestion
Root Cause IM Product Threshold is not included in the intermodulation

interference detection results during code writing.
Solution IM Product Threshold has been added to the intermodulation
interference detection results.
Solution None
Impact
Trouble Ticket ATP-2015042503102

Number
3.2.2.4.8 No confirmation message is displayed after the ADD SYNCETH command is

executed on the U2000

Number
 On the U2000, the ADD SYNCETH command is executed with the
SyncEth Type parameter set to IN(Input).
 The synchronous Ethernet clock is connected to the 1000 Mbit/s
electrical port.
 On the peer equipment, the Clock Mode parameter in the E1/T1 MO
is set to SLAVE(Slave Mode).
Symptom: The clock is unavailable.
Impact: Services are interrupted.
Severity Suggestion
Root Cause When the ADD SYNCETH command is executed with the SyncEth
Type parameter set to IN(Input) on the U2000, the Clock Mode
parameter in the E1/T1 MO will be automatically set to SLAVE(Slave
Mode) if the synchronous Ethernet clock is connected to the 1000
Mbit/s electrical port. In this case, if the Clock Mode parameter in the
E1/T1 MO is set to SLAVE(Slave Mode) on the NE providing the

Copyright © Huawei
synchronous Ethernet clock, the clock will become unavailable. As a

result, services will be interrupted.
Solution The following confirmation message has been added for the ADD
SYNCETH command: "Ensure that the clock synchronization mode of
the peer equipment is correctly configured. Otherwise, services of the
base station will be interrupted or the OM channel will be disconnected.
Are you sure you want to continue?"
After the ADD SYNCETH command is executed, this message will be
displayed on the U2000 to prompt users to check whether the clock
synchronization mode of the peer equipment is correctly configured.
Solution None
Impact
3.2.2.4.9 The alarm cause for ALM-25900 IP PM Activation Failure is inaccurate if the
peer equipment of a base station does not support IPPM of a later version
Ticket
Number
Description Condition: The peer equipment of a base station does not support IP
performance monitoring (IPPM) of a later version (for example, version
15.0). The differentiated services code point (DSCP) of the IPPM
session packet is changed on the transport network between the base
station and the peer equipment.
Symptom: The base station reports ALM-25900 IP PM Activation
Failure, and Alarm Cause is Peer version is not supported or DSCP
modified.
Impact: The alarm cause for ALM-25900 IP PM Activation Failure is
inaccurate.
Severity Suggestion
Root Cause The base station refreshes causes for IPPM negotiation failures based on
IPPM negotiation results. However, the alarm cause reported at the time
the number of IPPM failures reaches the alarm generating threshold is
recorded as the alarm cause for ALM-25900 IP PM Activation Failure.
There are two alarm causes for an IPPM negotiation failure, and
therefore the alarm cause reported at the time the number of IPPM
failures reaches the alarm generating threshold is inaccurate.
Solution The mechanism of recording the alarm cause for ALM-25900 IP PM
Activation Failure has been modified. After receiving the Peer version
is not supported alarm cause from the peer equipment, a base station
initiates a new negotiation on IPPM of an earlier version. The base
station saves only the cause for a failure in the negotiation on IPPM of
the earliest version as the alarm cause for ALM-25900 IP PM Activation
Failure. For example, if the cause for a failure in the negotiation on
IPPM of the earliest version is DSCP modified, DSCP modified is

Copyright © Huawei
reported as the alarm cause for ALM-25900 IP PM Activation Failure.

Solution None
Impact
3.2.3 Known Issues

None.
3.3 NodeBFunction
None.

3.3.1.2.1 Licensed Capability Query for the UBBPd Board
Description
This feature enables users to query the licensed capability of the UBBPd board. Before this
feature is introduced, users can run the DSP BBPTC command to query the maximum
hardware capability of the UBBPd board but cannot use the command to query the licensed
capability.
Implementation
The DSP NODEBBBRES command is used to query the licensed capacity of the UBBPd
board.

None
None
Impact on NEs
This feature is implemented on the NodeB.

Copyright © Huawei
Impact on Hardware
None

None

This feature is not under license control.
The following MML command has been modified to accommodate this feature.
Chan MML Command NE Description
ge
Type
Modifi DSP NODEBBBRES NODEB This command now can be used

ed to query the number of uplink
and downlink CEs provided by a
baseband processing unit.
The following parameters have been added to accommodate this feature.
Change Parameter MML NE Description

Type ID Command
New UL CE DSP NodeB Indicates the number of uplink

NODEBBBRE CEs provided by a baseband
S processing unit.
New DL CE DSP NodeB Indicates the number of downlink
NODEBBBRE CEs provided by a baseband
S processing unit.

None
None

None
None

Copyright © Huawei
None
Related Operations
None

DTS2015021605023
Feature ID
None

None.

3.3.2.1 Critical
None.
3.3.2.2 Major
3.3.2.2.1 Base stations occasionally fail to be upgraded to RAN17.1.
Trouble iCare: 2367032 / 3186889

Number
Description Condition: Base stations configured with WMPT boards need to be

upgraded to RAN17.1.
Symptom: The upgrade occasionally fails.
Impact: Ongoing services carried on the base stations are affected.
Severity Major
Root Cause The WMPT board uses a defective CPLD link loading module during the
upgrade.
Solution A JTAG test is introduced for the WMPT board during online hardware
tests to check for faults on the CPLD link loading module. Specifically,
the STR HWOLTST command is executed to start the online hardware
test, and the DSP HWOLTSTRESULT command output shows the test
result. If the JTAG test result is displayed as "Fault", the WMPT board
needs to be replaced.
Solution None
Impact

Copyright © Huawei
3.3.2.2.2 In specific scenarios, UEs experience call drops.

Number
Description Condition: All local cells are removed from uplink baseband equipment.
Symptom: All UEs using CPU of boards in uplink baseband equipment
experience call drops.
Impact: The call drop rate increases.
Severity Major
Root Cause The NodeB uses a defective mechanism to remove all local cells from
uplink baseband equipment. As a result, UEs are unintentionally deleted
when local cells are removed.
Solution The defective mechanism has been corrected to prevent UEs from being
unintentionally deleted when all local cells are removed from uplink
baseband equipment.
Solution None
Impact
3.3.2.2.3 ALM-26532 RF Unit Hardware Fault is not reported when RRU hardware
experiences a failure.

Number
Description Condition: The Tantalum capacitor of an RF unit fails in hardware.

Symptom: No relevant alarm is reported.
Impact: Users are not alerted to the fault.
Severity Major
Root Cause There is a probability that downlink modulation deteriorates but the
transmit power of an RF unit remains normal if the RF unit fails in
hardware. In this situation, the original alarm detection mechanism only
checks for the transmit power and therefore ALM-26532 RF Unit
Hardware Fault is not reported.
Solution The following reserved parameters now are used to detect faults in the
Tantalum capacitor of an RF unit:
 NODEBRSVDPARA2.BIT32 in the SET NODEBRSVDPARA
command NODEBRSVDPARA2.BIT27 in the SET
NODEBRSVDPARA command
 NODEBRSVDPARA11 in the SET NODEBRSVDPARA command
By default, this solution is disabled (default values of these parameters:

Copyright © Huawei
0).
When detecting a fault in the Tantalum capacitor of an RF unit, the
NodeB reports ALM-26532 RF Unit Hardware Fault.
Solution None
Impact
3.3.2.2.4 In heavy traffic scenarios in parallel with frequent radio link setup and
removal, the UE access success rate decreases.

Ticket
Number
Description Condition: The WBBPb or WBBPd board provides resources for cells
and radio links are frequently added and removed for a large number of
UEs in heavy traffic scenarios.
Symptom: There is an extremely low probability that RRC connection
setup fails for the UEs.
Impact: The UE access success rate decreases.
Severity Major
Root Cause In heavy traffic scenarios, the WBBPb and WBBPd boards use a
defective mechanism to process frequent radio link setup and removal.
Solution The defective mechanism has been corrected.
Solution This solution causes load of DSP 2 to fluctuate in light traffic scenarios.
Impact
3.3.2.2.5 In certain scenarios, ALM-28206 Local Cell Capability Decline is reported when
it should not be and the alarm persists.

Ticket
Number
1. Users run the ADD NODEBMULTICELLGRPITEM command to
add only one cell to the DC-HSUPA cell group.
2. Users run the RMV NODEBMULTICELLGRPITEM command to
remove the cell.
Symptom:
1. ALM-28206 Local Cell Capability Decline is reported with the cause

Copyright © Huawei
value "DC-HSUPA not supported by the cell".

2. The alarm persists after users remove the cell.
Impact: The alarm is reported when it should not be and persists.
Severity Major
Root Cause The processing mechanism is defective in the preceding scenario.
Solution The defective processing mechanism has been corrected.
Solution None
Impact
3.3.2.3 Minor
3.3.2.3.1 In certain scenarios, the dynamic voltage adjustment function does not take
effect.

Number
Description Condition: A user runs the SET NODEBOPTDYNADJPARA

command, with the Dynamic Voltage Adjustment Switch parameter set
to ON and Start Time equal to End Time.
Symptom: The dynamic voltage adjustment function does not take
effect.
Impact: User experience is affected.
Severity Minor
Root Cause In the preceding situation, the NodeB uses a defective mechanism.
Specifically, if Start Time is equal to End Time, the Dynamic Voltage
Adjustment Switch parameter is modified to OFF.
Solution The defective mechanism has been corrected. Specifically, if Start Time
is equal to End Time, the dynamic voltage adjustment function remains
in effect for 24 hours.
Solution None
Impact
3.3.2.3.2 EVT-28200 Iub Common Procedure Failure Indication is reported with no detail
about the causes of the alarm triggering condition provided.


Copyright © Huawei
Number
Description Condition: 1. The total transmit power configured for all the cells
exceeds the RRU power specifications. 2. Frequency spacing between the
cells is beyond the range specific to the RRU.
Symptom: When either of the preceding conditions applies, logical cell
activation fails. Accordingly, EVT-28200 Iub Common Procedure Failure
Indication is reported, with the cause of "Cell Setup Failure" and the
specific problem of "Cell Procedure Abnormal".
Impact: No detail about the causes of the alarm triggering condition is
provided, confusing users.
Severity Minor
Root Cause The problem description is inadequately prepared.
Solution Missing information has been added to the problem description.

Specifically, the causes "Cell Power Exceeded RF Unit Power
Specification" and "Cell Frequency Configuration Failure" have been
added to EVT-28200 Iub Common Procedure Failure Indication.
Solution None
Impact
3.3.2.3.3 The VS.BTS.CnbapCap.UseRate counter returns a value smaller than expected

for a base station configured with the UBBPd5 board.

Ticket
Number
Description Condition: The UMPT board functions as the main control board and
baseband processing units in use include the UBBPd5 board.
Symptom: The VS.BTS.CnbapCap.UseRate counter returns a value
smaller than expected.
Symptom: The counter value is inaccurate.
Severity Minor
Root Cause CNBAP capabilities supported by theUBBPd5 board are incorrectly

counted into the VS.BTS.CnbapCap.UseRate counter.
Solution CNBAP capabilities supported by theUBBPd5 board are now correctly
counted into the VS.BTS.CnbapCap.UseRate counter.
Solution The value returned by the VS.BTS.CnbapCap.UseRate counter increases.
Impact

Copyright © Huawei
3.3.2.3.4 Benefits yielded by WRFD-170201 Seamless Crystal Voice and WRFD-171201

Crystal Voice in Deep Coverage decrease when WRFD-140202 Control Channel Parallel
Interference Cancellation (Phase 2) is enabled.

Ticket
Number
 All the three features are enabled: WRFD-170201 Seamless Crystal
Voice, WRFD-171201 Crystal Voice in Deep Coverage, and WRFD-
140202 Control Channel Parallel Interference Cancellation (Phase 2).
 The base station serves a large number of UEs.
Symptom: Benefits yielded by WRFD-170201 Seamless Crystal Voice
and WRFD-171201 Crystal Voice in Deep Coverage decrease.
Impact: Network KPIs do not deteriorate, but benefits yielded by
WRFD-170201 Seamless Crystal Voice and WRFD-171201 Crystal
Voice in Deep Coverage do not meet expectations.
Severity Minor
Root Cause The feature processing mechanism is defective. Specifically, if the

baseband processing unit becomes heavily loaded, the WRFD-140202
Control Channel Parallel Interference Cancellation (Phase 2) feature has
a higher priority than the two features WRFD-170201 Seamless Crystal
Voice and WRFD-171201 Crystal Voice in Deep Coverage, and the
NodeB suspends processing the two features, decreasing the feature
benefits.
Solution The defective mechanism has been corrected to ensure the three features
have the same priority if the baseband processing unit becomes heavily
loaded.
Solution If the baseband processing unit is heavily loaded, the benefits yielded by
Impact WRFD-140202 Control Channel Parallel Interference Cancellation
(Phase 2) will decrease when the NodeB processes the two features
WRFD-170201 Seamless Crystal Voice and WRFD-171201 Crystal
Voice in Deep Coverage.
3.3.2.3.5 DC-HSDPA services are reconfigured as SC-HSDPA services and radio link
reconfiguration fails if DC-HSDPA over Iur is enabled.

Ticket
Number
1. DC-HSDPA over Iur is enabled. An inter-Iur handover is triggered for
DC-HSDPA UEs.
2. The HSDPA serving link needs be changed and the secondary carrier

Copyright © Huawei
needs to be deleted.
Symptom: The radio link reconfiguration fails.
Impact: The radio link reconfiguration success rate
(VS.IUR.RL.RECFG.Succe.Rate) decreases.
Severity Minor
Root Cause The NodeB cannot process the simultaneous requests of changing the
HSDPA serving link and deleting the secondary carrier.
Solution The NodeB now can process the simultaneous requests.
Solution None
Impact
3.3.2.3.6 The counter indicating the number of uplink frames discarded by the Iub
logical port occasionally returns a larger value than expected after a handover.

Ticket
Number
Description Condition: Radio links for HSUPA UEs are reconfigured after a
handover.
Symptom: The VS.IUB.FlowCtrol.UL.DropNum.LgcPort1 counter
returns a larger value than expected.
Impact: The counter value is inaccurate.
Severity Minor
Root Cause In this instance, the mechanism for collecting statistics about the number
of uplink frames discarded by the Iub logical port is defective. Therefore,
some discarded uplink frames are also counted into the counter when
they should not be.
Solution None
Impact
3.3.2.4 Suggestion
3.3.2.4.1 In certain scenarios, ALM-28206 Local Cell Capability Decline is not reported
when it should be.

Ticket

Copyright © Huawei
Number
Description Condition: A multi-carrier HSDPA cell group has three or more local
cells, with one or two of them being enabled with 4C-HSDPA.
Symptom: The command output of DSP ULOCELL indicates that the
MC capability is available.
Impact: The queried MC capability is incorrect and ALM-28206 Local
Cell Capability Decline is not reported when it should be.
Severity Suggestion
Root Cause The mechanism for calculating MC capabilities of local cells is defective.
Solution ALM-28206 Local Cell Capability Decline is reported with the alarm
Impact cause of "4C-HSDPA/3C-HSDPA/Flexible Dual Carrier HSDPA not
supported by the cell".
3.3.2.4.2 The average ratio of DPCH and F-DPCH transmit power over different SF code
channels to the maximum downlink transmit power in a cell is less than expected.

Ticket
Number
Description Condition: The WBBPb, WBBPd, or WBBPf board provides downlink

baseband resources for a cell and serves DPCH or F-DPCH users.
Symptom: The average ratio of DPCH and F-DPCH transmit power over
different SF code channels to the maximum downlink transmit power in a
cell is less than expected.
VS.DlPwrRatio.SF256
VS.DlPwrRatio.SF128
VS.DlPwrRatio.SF64
VS.DlPwrRatio.SF32
VS.DlPwrRatio.SF16
VS.DlPwrRatio.SF8
Impact: Values returned by the preceding counters are less than
expected.
Severity Suggestion
Root Cause The downlink baseband processing unit uses a defective mechanism to
measure the average DPCH or F-DPCH transmit power.
Solution None
Impact

Copyright © Huawei
3.3.3 Known Issues

None.

Copyright © Huawei

V100R010C10SPC100
4.1 Change Summary

in V100R010C10SPC100. For details, see 4.1.1 Capacity and Performance.
Hardware
Compared with those in V100R010C10SPC050, 1 board types have been added to and no
board types have been modified in V100R010C10SPC100. For details, see 4.1.2 Hardware.

Compared with those in V100R010C10SPC050, no features and functions have been added, 3
Resolved issues
issues, and 8 suggestion-level issues have been resolved in V100R010C10SPC100. 4.1.4

Copyright © Huawei

remain changed in V100R010C10SPC100. For details about MML command and
parameter changes, ssee 8.1 MML Command Changes and 8.2 Parameter Changes,
respectively.
remain changed in V100R010C10SPC100. For details about counter changes, see 8.5
Counter Changes.
changed in V100R010C10SPC100. For details about alarm and event changes, see 8.3
Alarm Changes and 8.4 Event Changes, respectively.
Changes.
templates have changed in V100R010C10SPC100. For details, see 4.1.6 Related
Documentation.

None.
4.1.2 Hardware
New Hardware
Hardware Hardware Change Description
Type Name
Board pRRU3902 TX/RX mode: 2T2R (dual band)

Band: 1800 MHz to 2100 MHz
1800 MHz: UL: 1710~1785 MHz, DL: 1805~1880
MHz
2100 MHz: UL:1920~1980 MHz, DL: 2110~2170
MHz
RAT
1800 MHz: LO
2100 MHz: UO/LO/UL
Power specifications: 2 x 100 mW on each

Copyright © Huawei

Type Name
frequency band
Power supply: direct current
The pRRU3902 1.8 GHz + 2.1 GHz module uses
the following license:
1) LampSite First Mode First Band License for
Multi-Band RF Module (LTE FDD)
2) LampSite Multi-Mode Multi-Band License for
Multi-Band RF Module (LTE FDD)
3) LampSite First Mode First Band License for
Multi-Band RF Module (UMTS)
4) LampSite Multi-Mode Multi-Band License for
Multi-Band RF Module (UMTS)
Modified Hardware
None.
Deleted Hardware
None

V100R010C10SPC100 to V100R010C10SPC050 :
 Change type
 (Optional) RAT
For features changes in the NodeBFunction, see 4.3.1 Feature and Function Changes

V100R010C10SPC100 but unresolved in BTS3900 V100R010C10SPC050 :

Copyright © Huawei
 Severity
 Solution impact
 (Optional) RAT

parameters,see 8.1 MML Command Changes and 8.2 Parameter Changes.

Changes.

unchanged in V100R010C10SPC100. For details about changes to alarms and events, see 8.3
Alarm Changes and 8.4 Event Changes.

unchanged in V100R010C10SPC100. For details about changes to license control items, see
8.6 License Changes.

Version
Added RRU3952m This document describes the (For Customer)3900

Hardware Description. appearance, panels, LEDs, and Series Base Station
cables of the RRU3952m. Product
Documentation(V100R01
Added RRU3952m This document describes the 0C10_01)(HDX)-EN
Installation Guide. installation procedures and
methods of the RRU3952m.

Copyright © Huawei

Version
Added RRU3220E This document describes the

Hardware Description. appearance, panels, LEDs, and
cables of the RRU3220E.
Installation Guide. installation procedures and
methods of the RRU3220E.
Hardware Maintenance maintenance of the RRU3220E.
Guide.
Added eRAN This document describes how to
Troubleshooting Guide. diagnose and handle eRAN faults.
Combined eRAN This document describes
(FDD) Reconfiguration guidelines for eRAN
Guide and eRAN reconfiguration. eNodeB
(TDD) Reconfiguration reconfiguration consists of
Guide into eRAN capacity expansion and network
Reconfiguration Guide. reconstruction.
Product Documentation(V100R010C10_01)(HDX)-EN.
4.2 Node
None.

4.2.1.2.1 DSP SFP Command Output Optimization
Description
After this function is implemented, the values of power-related parameters and health check
results can be displayed in the unit of dBm.
Implementation
This function adds six parameters to the output of the MML command DSP SFP to improve
user experience:
 TX optical power(0.01dBm)

Copyright © Huawei
 RX optical power(0.01dBm)
 Receive Power Upper Threshold(0.01dBm)
 Receive Power Lower Threshold(0.01dBm)
 Transmit Power Upper Threshold(0.01dBm)
 Transmit Power Lower Threshold(0.01dBm)
In addition, the preceding parameters are also added to the results of the check item Check
the optical power of the optical module on the U2000.
System Capacity and Performance

None
None
Impact on NEs
None
Impact on Hardware
None

None

None
None
None
None

None
Related Operations
None

PIACR2015012032467

Copyright © Huawei
Feature ID
None

None.

4.2.2.1 Critical
4.2.2.1.1 A board where the certificate is installed occasionally restarts due to high
memory usage.

Ticket
Number
Description Condition: The NodeB version is V100R010C10. In the LST

CERTDEPLOY command output, DEPLOYTYPE is DEFAULT or
SPECIFIC.
Symptom: In the DSP MEMUSAGE command output, the memory
usage is high on the board where the certificate is installed.
Impact: The board occasionally restarts, interrupting ongoing services
carried on the board.
Severity Critical
Root Cause The board where the certificate is installed checks the IKE negotiation
status every 7 minutes. The board requests memory for the check but the
memory allocated to the board is not promptly released after the check is
completed. As a result, the memory usage increases gradually, resulting
in a board restart.
Solution The board now releases memory immediately after the IKE negotiation
status check is completed.
Solution None
Impact
4.2.2.2 Major
4.2.2.2.1 Hardware faults fail to be reported due to the absent FPGA check during the
running of a board
Trouble iCare: 4051369 / 3767637

Number

Copyright © Huawei
Descriptio Condition: The hardware of an LBBPd is faulty.

n Symptom: ALM-26230 BBU CPRI Optical Module Fault is reported on an
LBBPd in the live network of Canada Telus. The number of UEs abruptly
drops to 0 but ALM-26200 Board Hardware Fault has not been reported.
Impact: Services are interrupted.
Severity Major
Root The field programmable gate array (FPGA) hardware is faulty and no fault
Cause check is performed.
Solution The FPGA check is now performed during the running of a board, so that
ALM-26200 Board Hardware Fault is reported when a hardware fault
occurs.
Solution None
Impact
Test Case ATP_2015020903376
4.2.2.2.2 Hardware faults fail to be reported due to the absent CPLD check during the
running of a board
Ticket
Number
Descriptio Condition: The hardware of a UMPT is faulty.

n Symptom: After the UMPT software is upgraded in a site of Hong Kong
PCCW, the base station is disconnected from the network management
system, but ALM-26200 Board Hardware Fault has not been reported.
Impact: The UMPT hardware fault fails to be detected before the upgrade,
which leads to service interruption after the upgrade.
Severity Major
Root The complex programmable logical device (CPLD) hardware is faulty and
Cause no fault check is performed.
Solution The CPLD check is now performed during the running of a board, so that
ALM-26200 Board Hardware Fault is reported when a hardware fault
occurs.
Solution None
Impact
Test Case ATP_2015020601402

ID

Copyright © Huawei
4.2.2.2.3 The VPP component has a vulnerability
Ticket
Number
Descriptio Condition: There are two certificates that only differ in algorithm field.
n Symptom: The algorithm field of the non-signature information in a
certificate can be modified without changing the fingerprint information
(signature), because the non-signature information is not involved in the
certificate fingerprint calculation. As a result, different certificates may have
the same fingerprint (signature) information, and systems that identify
certificates only through fingerprint (signature) information may fail to
identify them. For example, if a system only checks fingerprint information,
instead of both the algorithm field and fingerprint information, different
certificates with the same fingerprint information will pass the check.
Impact: A base station considers certificates to be the same if their
fingerprint (signature) information is the same, regardless of their different
algorithm fields. This reduces the system security.
Severity Major
Root The Voice Protocol Platform (VPP) component used by a base station fails
Cause to check certificates thoroughly.
Solution The vulnerability of the VPP component has been rectified so that the
component can check certificates thoroughly.
Solution None
Impact
4.2.2.2.4 The result of traffic statistics at the IP layer is inaccurate.

Ticket
Number
Description Condition: A tunnel is configured on the main control board of a base

station by using the ADD TUNNEL command. The base station starts
counting the number of bytes or packets over the tunnel from zero after
the counted number reaches to the maximum value over a period of time.
Symptom: The counted number of bytes in the IP packets at the IP layer
is not returned as expected in a measurement period.
Impact: Users cannot obtain accurate values returned by the
VS.IP.TxBytes and VS.IP.RxBytes counters.
Severity Major
Root Cause The main control board of the base station uses a defective algorithm to
calculate the increased number of bytes in the IP packets at the IP layer.

Copyright © Huawei
Solution The defective algorithm has been corrected.
Solution None
Impact
4.2.2.2.5 NTP synchronization fails if the OM IP address and device IP address are the
same.

Number
Description Condition: A device IP address configured on a base station is the same

as the local IP address of the OM channel configured on the base station,
and the base station restarts.
Symptom: The base station fails to set up the synchronous socket for
time synchronization.
Impact: NTP synchronization fails on the base station.
Severity Major
Root Cause Two tasks are accessing an IP address configured for a base station board.
When one task is determining whether the IP address is configured for
the board, the IP address is deleted and has not been added in the other
task.
Solution This defect has been corrected to ensure NTP synchronization
availability. Now, during a socket binding setup for NTP synchronization,
the base station allows for multiple attempts to check whether an IP
address is configured for a base station board. In addition, after the
device IP address takes effect on the base station board, the base station
performs another socket binding with the IP address.
Solution None
Impact
4.2.2.3 Minor
4.2.2.3.1 The CSEC finds that the RC4 algorithm is prone to attacks
Ticket
Number
Descriptio Condition: A base station starts properly and the peer end uses the RC4
n algorithm.
Symptom: The base station and the peer end may negotiate the RC4

Copyright © Huawei
algorithm.
Impact: The negotiated RC4 algorithm is prone to attacks.
Severity Minor
Root The base station uses the RC4 algorithm to ensure compatibility with the
Cause peer end.
Solution The RC4 algorithm has been removed from the base station.
Solution None
Impact
4.2.2.3.2 No alarm is reported when a hard failure occurs in the FPGA of an RF module.
Ticket
Number
Description Condition: Internal status of the field programmable gate array (FPGA)
in a radio frequency (RF) module changes and cannot recover by reset.
This problem is called a hard failure and has a low probability of
occurring.
Symptom: Before an upgrade, no alarm is reported. After the upgrade,
the RF module becomes faulty and cannot provide services.
Impact: Maintenance personnel cannot identify the problem.
Severity Minor
Root Cause The BTS does not detect the hard failure of the FPGA in the RF module.
Solution A mechanism for the BTS to detect hard failures of the FPGA in the RF
module has been added. The BTS now reports ALM-26532 RF Unit
Hardware Fault in the preceding scenario.
Solution None
Impact
4.2.2.3.3 An RRU configured with cascaded optical modules incorrectly reports ALM-
26506 RF Unit Optical Interface Performance Degraded.

Ticket DTS2014021101602
Number
Description Condition: The BTS is configured with a cascaded RRU optical module
during the deployment.

Copyright © Huawei
Symptom: The cascaded RRU optical module may incorrectly report

ALM-26506 RF Unit Optical Interface Performance Degraded with
"Specific Problem" being "Reception Power too High".
Impact: Maintenance personnel cannot determine optical module status.
Severity Minor
Root Cause Measurement values of transmit and receive optical power of optical
modules have errors. If the transmit optical power of the peer optical
module is high and the error of the measured receive optical power of
the local optical module is large, the RRU incorrectly considers the
receive optical power as too high. As a result, the RRU reports ALM-
26506 RF Unit Optical Interface Performance Degraded.
Solution The RRU now reports ALM-26506 RF Unit Optical Interface
Performance Degraded with "Specific Problem" being "Reception Power
too High" only when the actual receive power of the optical module is
high and error codes occur.
Solution None
Impact
4.2.2.3.4 No alarm is reported when the RF module uses the Low-rate optical module as
a high rate.
Ticket
Number
Description Condition: The radio frequency (RF) module uses the Low-rate optical
module as a high rate.
Symptom: The ALM-26502 RF Unit Optical Module Type Mismatch
does not report.
Impact: Users can not accurately identify.
NOTE
This problem has been resolved in BTS3900 V100R010C10 and is described in
this version.
Severity Minor
Root Cause The BTS does not detect the RF module using the Low-rate optical
module as a high rate.
Solution ALM- 26502 RF Unit Optical Module Type Mismatch will be added to
identify the rate mismatch.
A mechanism for the BTS to detect the RF module using the Low-rate
optical module as a high rate has been added. The BTS now reports
ALM-26502 RF Unit Optical Module Type Mismatch in the preceding
scenario.
Solution None

Copyright © Huawei
Impact
4.2.2.3.5 The configured TMA attenuation value does not take effect.

Ticket DTS2014112904951
Number
This problem occurs when all of the following conditions are met:
 A radio frequency (RF) module reports ALM-26530 RF Unit ALD
Current Out of Range.
 ALD Power Switch is set to OFF(OFF) by running the MOD
ANTENNAPORT command and the antenna line device (ALD)
switch is manually turned off to clear this alarm.
 After the fault triggering this alarm is manually rectified, the ALD
switch is turned on.
Symptom: The received total wideband power (RTWP) obtained from
the tracing function on the local maintenance terminal (LMT) is
excessively high, but no alarms are reported.
Impact: The network noise floor measured by the BTS is incorrect,
decreasing the user access success rate.
NOTE
This problem has been resolved in BTS3900 V100R010C10 and is described in
this version.
Severity Minor
Root Cause The mechanism of clearing ALM-26530 RF Unit ALD Current Out of
Range does not consider the scenario of manual fault rectification. As a
result, the user-configured attenuation value is lost and therefore cannot
take effect after the faults are manually rectified.
Solution The scenario that faults are manually rectified is added to the
mechanism of clearing ALM-26530 RF Unit ALD Current Out of
Range. Now the user-configured attenuation value is recorded during the
manual fault rectification so that the attenuation value takes effect after
the alarm clearance.
Solution When ALD Power Switch is set to OFF(OFF) to clear ALM-26530 RF
Impact Unit ALD Current Out of Range, if the user-configured attenuation
value is not set to 0, the RTWP is excessively low.
4.2.2.3.6 Configuration check items do not pass health check on the RRU3801C.

Copyright © Huawei
Ticket
Number
Description Condition: The RRU3801C functions as the RF module.

Symptom: The STR CFGCHK command is executed to start
configuration check. The command execution fails and the error message
"Get RRU PA efficiency improvement capability fail.(0x420133ec)" is
displayed.
Impact: The health check on the RRU3801C fails, affecting user
experience.
Severity Minor
Root Cause The RRU3801C returns incorrect results when starting the configuration
check.
Solution The returned result has been corrected so that the configuration check can
be successfully performed.
Solution None
Impact
4.2.2.3.7 ALM-26245 Configuration Data Inconsistency is repeatedly reported and

cleared.

Ticket
Number
Description Condition: Configuration is successful but configuration data does not

take effect.
Symptom: ALM-26245 Configuration Data Inconsistency is repeatedly
reported and cleared.
Impact: Services are not affected.
Severity Minor
Root Cause The alarm detection mechanism is defective.
Solution The alarm detection mechanism has been optimized.
Solution None
Impact
4.2.2.3.8 Statistics on USERPLANEHOSTIP are inaccurate.

Copyright © Huawei
Ticket
Number
Description Condition: Statistics collection for USERPLANEHOSTIP is started on

the U2000.
Symptom: The maximum transmit and receive rates are greater than
expected.
Impact: The statistics are inaccurate, affecting service maintenance.
Severity Minor
Root Cause Time alignment is not performed in statistics collection. Specifically, the
sampling period is not corrected even when it is inaccurate.
Solution Two sampling period records are now used to calculate an average
sampling period.
Solution None
Impact
4.2.2.4 Suggestion
4.2.2.4.1 DSP faults occur on the WBBPd board but ALM-26200 Board Hardware Fault is
not reported.
Trouble iCare: 3688227 / 3747118

Number
Description Condition: DSP faults occur on the WBBPd board.

Symptom: WBBPd hardware is faulty but ALM-26200 Board Hardware
Fault is not reported.
Impact: Users cannot be promptly alerted, causing a delay in fault
handling.
Severity Suggestion
Root Cause The mechanism for the WBBPd board to check DSP faults is defective.
Solution None
Impact

Copyright © Huawei
4.2.2.4.2 In the engineering quality check on the RRU V1 and RRU V2, the PIM test
result is incorrect.

Ticket
Number
Description Condition: The RRU V1 and RRU V2 work together and they do not
support GSM.
Symptom: The engineering quality check on the U2000 returns an
incorrect PIM test result. (Relevant command: STR RFTEST: TSTTYPE
= PIMONTRAFFIC_ONLINE)
Impact: The PIM test result is incorrect in the site deployment report.
Severity Suggestion
Root Cause The Difference Threshold parameter in the engineering quality check
has a different unit from that in the STR RFTEST command. The
parameter unit is dB on the U2000 and 0.1 dB in the command. The unit
conversion for the parameter is not performed in the PIM test.
Solution The unit conversion for the Difference Threshold parameter now is
performed in the PIM test.
Solution None
Impact
4.2.2.4.3 The LST RRU command output on the U2000 is incomplete for a large-scale
LampSite network.

Ticket
Number
Description Condition: A large-scale LampSite network is deployed.

Symptom: The LST RRU command output on the U2000 does not
include information about all pRRUs. This fault always occurs if plenty
of pRRUs are configured.
Impact: The command output is incomplete, affecting user experience.
Severity Suggestion
Root Cause Each message returned by a command to the U2000 cannot exceed 32
KB. A message returned by the LST RRU command includes a
maximum of 100 pRRUs, which may exceed the message size limit.
Solution A message returned by the LST RRU command now includes a
maximum of 50 pRRUs.
Solution The number of pRRUs included in each message returned by the LST
Impact RRU command has been changed. This solution does not affect services

Copyright © Huawei
or the function of the LST RRU command.

4.2.2.4.4 The queried session status is incorrect during a certificate request process.

Ticket
Number
Description Condition: During a certificate request process, users run the STP
CMPSESSION command to stop a Certificate Management Protocol
(CMP) session if the session status is PENDING.
Symptom: The DSP CMPSESSION command output indicates that the
status of the CMP session is INITIAL, although the correct status is
STOPPED.
Impact: The queried session status is incorrect.
Severity Suggestion
Root Cause If a CMP session is manually stopped, the session status is incorrectly
set.
Solution If a CMP session is manually stopped, the session status now is set to
STOPPED.
Solution None
Impact
4.2.2.4.5 A UMTS cell established on multiple boards experiences access exceptions in a

certain scenario.

Ticket
Number
Description Condition: A UMTS cell is established on two or more of the UBRIb,

WBBPf, UBBPd, and LBBPd boards, and either of the following
conditions applies:
Users perform a hardware test (by running the STR HWTST command).
Users block a board (by running the BLK BRD command) on which the
UMTS cell is established, restart the blocked board, and then unblock it
(by running the UBL BLK command).
Symptom: If the sleeping cell detection switch is turned on (by running
the SET NODEBALGPARA command with
SLEEPINGCELLDETECTSW set to ON), the NodeB reports ALM-
28209 Cell No Traffic.
Impact: The UMTS cell established on multiple boards experiences

Copyright © Huawei
access exceptions.
Severity Suggestion
Root Cause The NodeB does not determine the block status of the board correctly
during a PBUS configuration, which results in PBUS configuration
failures.
Solution This defect has been corrected.
Solution None
Impact
4.2.2.4.6 Counters related to IP and ATM physical ports return inaccurate values.

Ticket
Number
Description Condition: Services are running normally on the NodeB.

Symptom: The average and maximum statistics of used uplink and
downlink bandwidths on the IP and ATM physical ports are inaccurate.
Impact: The inaccurate counter values hinder NodeB maintenance.
Severity Suggestion
Root Cause The NodeB uses a defective mechanism for correcting the average and
maximum statistics of used uplink and downlink bandwidths on the IP
and ATM physical ports. As a result, a measured value in a measurement
period is divided twice by the interval at which two samples are
collected.
Solution This defect has been corrected. Now, in a measurement period, the
NodeB divides only once a measured value of the average and maximum
statistics of the used uplink and downlink bandwidths on the IP and ATM
physical ports by the interval at which two samples are collected.
Solution None
Impact
4.2.3 Known Issues

None.

Copyright © Huawei
4.3 NodeBFunction
None.

4.3.1.2.1 Service Drop Rate Reduction for UEs Whose Downlink SRBs are Carried on
HSDPA Channels
Description
This function reduces the service drop rate for UEs whose downlink signaling radio bearers
(SRBs) are carried on HSDPA channels. Specifically, this function provides the following
algorithms:
 Optimized scheduling for UEs whose downlink SRBs are carried on HSDPA channels.
This algorithm includes the following:
− HARQ fast retransmissions for achieving HARQ combination gains
− HS-SCCH power control optimization in weak-coverage areas
 Automatic F-DPCH power appending on the NodeB when the serving cell changes.
This function is recommended when the service drop rate is high for UEs whose downlink
SRBs are carried on HSDPA channels.
Implementation
The SRBOVERHSDPAOPTSW and ExtraFDPCHPwr parameters in the SET
ULOCELLALGPARA command specify whether to enable this function.
When these parameters are both selected, the following algorithms take effect:
 Optimized scheduling for UEs whose downlink SRBs are carried on HSDPA channels
 Automatic F-DPCH power appending on the NodeB when the serving cell changes
When SRBOVERHSDPAOPTSW is selected and ExtraFDPCHPwr is cleared, optimized
scheduling for UEs whose downlink SRBs are carried on HSDPA channels takes effect and
automatic F-DPCH power appending on the NodeB when the serving cell changes does not
take effect.
These two algorithms do not take effect when SRBOVERHSDPAOPTSW is cleared.

None
This function reduces the service drop rate for UEs whose downlink SRBs are carried on
HSDPA channels.

Copyright © Huawei
Impact on NEs
This function is implemented on the NodeB.
Impact on Hardware
None

None

This function is part of the SRB over HSDPA feature, which is under license control on
the RNC.
The following command has been modified to accommodate this function.
ge
Type
Modifi SET ULOCELLALGPARA BTS3900 This command is used to set

ed the algorithm parameters of a
specific cell or all cells.

None
None

WRFD-010652 SRB over HSDPA
None
None
Related Operations
1. To enable the function, run the following command:
SET ULOCELLALGPARA: SRBOVERHSDPAOPTSW=1;
2. To disable the function, run the following command:
SET ULOCELLALGPARA: SRBOVERHSDPAOPTSW=0;

Copyright © Huawei
3. To enable the algorithm of automatic F-DPCH power appending on the NodeB when the
serving cell changes, run the following command:
SET ULOCELLALGPARA: SRBOVERHSDPAOPTSW=1, ExtraFDPCHPwr=1;
4. To disable the algorithm of automatic F-DPCH power appending on the NodeB when the
serving cell changes, run the following command:
SET ULOCELLALGPARA: SRBOVERHSDPAOPTSW=0, ExtraFDPCHPwr=0;

IR-RAN17.1-013
Feature ID
WRFD-010652
4.3.1.2.2 WRFD-171203 Uplink Control Channel OLPC
Description
This feature provides outer loop power control (OLPC) for HSUPA users based on the quality
of control channels. This feature further reduces the uplink load caused by control channels
when UEs have no data to transmit, improving uplink cell capacity.
Implementation
See Uplink Control Channel OLPC Feature Parameter Description in RAN feature
documentation.

This feature is applicable to the scenarios where HSUPA users with small traffic bursts
take the majority in traffic statistics and the uplink load is high. This feature increases
uplink capacity or reduces the RTWP by 5% to 10%.
None
Impact on NEs
Impact on Hardware
This feature is supported only by 3900 series of macro base stations that are configured with
the WBBPd/WBBPf/UBBPd in uplink and WBBPb/WBBPd/WBBPf/UBBPd in downlink.

None

Copyright © Huawei

A license control item "Uplink Control Channel OLPC (per Cell)" has been added for
this feature.
The following MML commands have been modified to accommodate this feature.
ge
Type
Modifi SET ULOCELLALGPARA BTS3900 This command is used to set the

ed algorithm parameters of a
specific cell or all cells.
Modifi SET NODEBALGPARA BTS3900 The command is used to modify
ed NodeB algorithm parameters.

None
None

WRFD-010612 HSUPA Introduction Package
WRFD-010610 HSDPA Introduction Package
WRFD-021350 Independent Demodulation of Signals from Multiple RRUs in One Cell
WRFD-141202 Independent Demodulation of Signals from Multiple Small Cell RRUs
in One Cell
WRFD-151208 Macro-Micro Multi RRUs in One Cell
− WRFD-020504 Inner Loop Power Control
In the inner-loop power control algorithm, TPC combination mode on the UE side
must be set to "Algorithm 1" to ensure prompt inner-loop power control. Otherwise,
Uplink Control Channel OLPC does not provide improvements or even has negative
effect. You can run the LST UFRC or SET UFRC command to query or set
algorithm 1 (parameter name: Power control algorithm selection).
− WRFD-010684 2x2 MIMO
Uplink Control Channel OLPC does not take effect for HSDPA MIMO users.
− WRFD-150204 Platinum User Prioritizing
Uplink Control Channel OLPC does not take effect for platinum users.
− WRFD-01061020 Improvement of User Experience in Low Traffic Service
Uplink Control Channel OLPC does not take effect for users enabled with
Improvement of User Experience in Low Traffic Service.

Copyright © Huawei
− WRFD-010686 CPC-DTX/DRX
Uplink Control Channel OLPC does not take effect for users with activated CPC.
− WRFD-150222 HSUPA Time Division Scheduling
Uplink Control Channel OLPC does not take effect for users involved in time-
division scheduling.
Related Operations
See "Engineering Guidelines" in Uplink Control Channel OLPC Feature Parameter
Description.

CR NP2616
Feature ID
WRFD-171203

None.

4.3.2.1 Critical
None.
4.3.2.2 Major
4.3.2.2.1 UEs on the UBBPd board occasionally experience call drops.

Ticket
Number
Description Condition: Uplink baseband equipment serving local cells includes the
UBBPd board.
Symptom: The call drop rate (as measured by Cell.Call.Drop.Rate)
increases for cells established on the UBBPd board and ALM-26203
Board Software Program Error is occasionally reported.
Impact: UEs served by the UBBPd board occasionally experience call
drops.
Severity Major
Root Cause In certain scenarios, the uplink user-plane processing procedure is

defective on dedicated links established on the UBBPd board. As a result,
the NodeB fails to report synchronization indication to the RNC.
Solution The defective procedure has been corrected.

Copyright © Huawei
Solution None
Impact
4.3.2.2.2 ALM-26242 Configuration File Damaged is reported in specific scenarios.

Ticket
Number
Description Condition: The NodeB is configured with a distributed cell, and the cell
is added to a power sharing group. A CB is saved and then activated by
running the MML commands CFM CB and ACT CB, respectively. The
configuration file is exported and then imported.
Symptom: In the output of the LST ULOCELL command, the cell
information is blank, and the NodeB reports ALM-26242 Configuration
File Damaged.
Impact: Cell information is lost. This does not affect ongoing services
but affects user experience.
Severity Major
Root Cause The NodeB uses a defective mechanism to check the configuration file
validity. As a result, the check fails when the CB is activated, triggering
ALM-26242 Configuration File Damaged.
Solution None
Impact
4.3.2.2.3 HSDPA throughput is low on a LampSite network.

Number
Description Condition: Multiple pRRUs on a LampSite network cover the same area
and these pRRUs serve the same cell. UEs located at the area can receive
signals of two or more of the pRRUs.
Symptom: The received signal quality is good, but the CQI and HSDPA
throughput are low.
Impact: The HSDPA throughput cannot reach the peak.
Severity Major
Root Cause Time is not aligned in the downlink for LampSite cells (UMTS). As a
result, the time differs greatly among the pRRUs serving the same cell,

Copyright © Huawei
resulting in multipath interference and a low CQI.

Solution Time is now aligned in the downlink for these LampSite cells so that all
the pRRUs serving the same cell achieve downlink time alignment.
Solution None
Impact
4.3.2.2.4 The performance counters related to the NodeB Iub logic port return greater
values than expected.

Number
Description Condition: The WBBPf or UBBPd board provides downlink baseband

resources and HSUPA services are running.
Symptom: The values returned by the following NodeB performance
counters are greater than expected:
 VS.IUB.FlowCtrol.UL.DelayVara.LgcPort1.Avg
 VS.IUB.FlowCtrol.UL.DelayVara.LgcPort1.Max
 VS.IUB.FlowCtrol.UL.DelayVara.LgcPort2.Avg
 VS.IUB.FlowCtrol.UL.DelayVara.LgcPort2.Max
 VS.IUB.FlowCtrol.UL.SendNum.LgcPort1
 VS.IUB.FlowCtrol.UL.SendNum.LgcPort2
 VS.IUB.FlowCtrol.UL.DropNum.LgcPort1
 VS.IUB.FlowCtrol.UL.DropNum.LgcPort2
Impact: The preceding counters return inaccurate values.
Severity Major
Root Cause The packet check mechanism needs to be optimized. Specifically, some
of the packets that fail the check are counted into these NodeB counters.
Solution The packet check mechanism has been optimized.
Solution None
Impact
4.3.2.2.5 HSDPA throughput of all cells on the WBBPb board is 0.

Number

Copyright © Huawei
Description Condition: The WBBPb board provides downlink baseband resources

for cells.
Symptom: There is an extremely low probability that all cells on the
WBBPb board have no HSDPA throughput. If this fault occurs, the block
error rate (BLER) is nearly 100%.
Impact: Cells on the WBBPb board cannot provide HSDPA services.
Severity Major
Root Cause Data migration on the WBBPb board using enhanced direct memory
access (EDMA) has defects. Consequently, data migration fails and HS-
PDSCH data cannot be transmitted over the air interface.
Solution The defects in data migration have been cleared.
Solution None
Impact
4.3.2.2.6 The counters measuring the number of UEs enabled with CPC return values
greater than expected.

Ticket
Number
Description Condition: Continuous packet connectivity (CPC) is enabled.

Symptom: The VS.CPC.DTXCfg.UserNum and
VS.CPC.DRXCfg.UserNum counters return values greater than expected.
Impact: These counters return inaccurate values.
Severity Major
Root Cause UEs enabled with CPC are repeatedly counted into these counters.
Solution UE statistics now are not repeatedly counted into these counters.
Solution None
Impact
4.3.2.2.7 In certain scenarios, counters related to service setup delay return values greater
than expected.

Ticket
Number

Copyright © Huawei
 Scenario 1: The NodeB is configured with a UMPT board.

 Scenario 2: The NodeB is configured with a WMPT board and a
UTRPc board, and the SET NODEBALGPARA command is
executed with CNBAP Capacity Extension Using UTRPc set to
ON.
Symptom: Counters related to service setup delay return values greater
than expected.
Impact: The service setup duration prolongs.
Severity Major
Root Cause The NodeB uses a defective mechanism for configuring communication
parameters for modules. As a result, the delay of interaction between
modules increases.
Solution The defective mechanism has been corrected. Specifically, the
interrupt+pollingmode is used to automatically adjust parameter settings
based on the system load.
Solution The CPU load increases for all boards configured in the NodeB.
Impact
4.3.2.2.8 HSDPA rates of single users fluctuate after handovers in ATM transmission
scenarios.

Ticket
Number
Description Condition: This fault occurs if both of the following conditions apply:
1. HSDPA services are carried on ATM transport channels and flow
control does not take effect on the RNC.
2. UEs are handed over between cells established on different WBBPf or
UBBP boards or between cells on the same WBBPf or UBBP board, and
the serving HSDPA links are changed.
Symptom: HSDPA rates of single UEs fluctuate.
Impact: User rates fluctuate after handovers.
Severity Major
Root Cause The downlink DSP obtains an incorrect flow control entity number if the
serving HSDPA link is changed during a handover process, resulting in
an abnormal bandwidth request.
Solution The downlink DSP now obtains a correct flow control entity number.
Solution The value returned by VS.IUB.FlowCtrol.DL.CongTime.LgcPort2

Impact increases.

Copyright © Huawei
4.3.2.3 Minor
4.3.2.3.1 If the NodeB serves DC-HSUPA and HSUPA users at the same time, the uplink
rate is higher than expected for DC-HSUPA users and widely fluctuates for HSUPA
users.

Ticket
Number
Description Transmission bandwidth is insufficient, and WRFD-01061212 HSUPA

Iub Flow Control in Case of Iub Congestion has taken effect on the
NodeB. HSUPA users are preceded by DC-HSUPA users to access cells
served by the NodeB.
Symptom: The uplink rate is higher than expected for DC-HSUPA users
and widely fluctuates for HSUPA users.
Impact: The uplink rate differentiation between DC-HSUPA and HSUPA
users cannot be achieved.
Severity Minor
Root Cause The mechanism for calculating the uplink rates of DC-HSUPA and
HSUPA users in the flow control scenario is defective.
Solution None
Impact
4.3.2.4 Suggestion
4.3.2.4.1 The ID of the HSUPA Scheduler Pool feature is incorrect in the parameter
reference.

Ticket
Number
Description Condition: None

Symptom: The feature ID of HSUPA Scheduler Pool listed in the
parameter reference is different from the feature ID in the feature list. To
be specific, the feature ID is WRFD-170205 in the feature list but
WRFD-170203 in the parameter reference.
Impact: The inconsistency causes confusion.
Severity Suggestion
Root Cause The feature ID of HSUPA Scheduler Pool is incorrectly displayed as

Copyright © Huawei
WRFD-170203 in the parameter reference.

Solution The feature ID has been changed to WRFD-170205 in the parameter
reference.
Solution None
Impact
4.3.2.4.2 The actual hardware capability of the UBBPd board cannot be queried.

Ticket
Number
Description Condition: The hardware capacity license is activated and hardware

capability enhancement is enabled for the UBBPd board.
Symptom: The DSP BBPTC command output still displays the
maximum hardware capability of the UBBPd board.
Impact: The actual hardware capability of the UBBPd board cannot be
queried.
Severity Suggestion
Root Cause The DSP BBPTC command can only be used to query the maximum
hardware capability of a board.
Solution The DSP NODEBBBRES command has been modified so that it can be
used to query the actual hardware capability of a board.
Solution None
Impact
4.3.3 Known Issues

None.

Copyright © Huawei
BTS3900 V100R010C10SPC120 Changes from V100R010C10 to V100R010C10SPC050
(NodeB) Release Notes Changes from V100R010C10 to V100R010C10SPC050
5 Changes from V100R010C10 to

V100R010C10SPC050
5.1 Change Summary

Compared with those in V100R010C10, capacity and performance remain unchanged in
V100R010C10SPC050. For details, see 5.1.1 Capacity and Performance.
Hardware
Compared with those in V100R010C10, no board types have been added to and no board
types have been modified in V100R010C10SPC050. For details, see 5.1.2 Hardware.

Compared with those in V100R010C10, one features and functions have been added, no
Resolved issues
Compared with those in V100R010C10, one critical issues, two major issues, three minor
issues, and one suggestion-level issues have been resolved in V100R010C10SPC050. 5.1.4

Copyright © Huawei

Compared with those in V100R010C10, configuration management functions remain
unchanged in V100R010C10SPC050. For details about MML command and parameter
changes, see 8.1 MML Command Changes and 8.2 Parameter Changes, respectively.
Compared with those in V100R010C10, performance management functions remain
Changes.
Compared with those in V100R010C10, fault management functions remain unchanged
in V100R010C10SPC050. For details about alarm and event changes, see 8.3 Alarm
Changes and 8.4 Event Changes, respectively.
Compared with those in V100R010C10, license management functions remain
Changes.
Compared with those in V100R010C10, document organization and document templates have
changed in V100R010C10SPC050. For details, see 5.1.6 Related Documentation.

None.
5.1.2 Hardware
New Hardware
None.
Modified Hardware
None.
Deleted Hardware
None

V100R010C10SPC050 to V100R010C10 :
 Change type

Copyright © Huawei

 (Optional) RAT

V100R010C10SPC050 but unresolved in BTS3900 V100R010C10 :
 Severity
 Solution impact
 (Optional) RAT

Compared with those in V100R010C10, configuration management functions remain
parameters, see 8.1 MML Command Changes and 8.2 Parameter Changes.

Compared with those in V100R010C10, performance management functions remain
Changes.

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

Copyright © Huawei

Compared with those in V100R010C10, license management functions remain unchanged in
V100R010C10SPC050. For details about changes to license control items, see 8.6 License
Changes.

Product Documentation(V100R010C10_Draft B)(HDX)-EN.
5.2 Node
5.2.1.1.1 IPSec NAT Traversal
Description
This feature enables IPSec tunnels to traverse the Network Address Translation (NAT)
gateway so that the IPSec function is supported when an NAT gateway is deployed.
Equipment complying with the Authentication Header (AH) protocol does not support NAT.
Implementation
The switch for the NAT traversal function is added in IPSec networking scenarios so that
IPSec tunnels can be established according to the NAT-Transfer protocol of IPSec to
implement IPSec encryption and decryption when an NAT gateway is deployed.

None
None
Impact on NEs
None
Impact on Hardware
None

None

Copyright © Huawei

None
− The NATTRAV parameter is added to the IKEPEER MO to control the NAT
traversal function. The NATTRAV parameter is used in the following MML
commands: ADD IKEPEER, MOD IKEPEER, DSP IKEPEER, LST IKEPEER,
and RMV IKEPEER.
− The NATKLI parameter is added to the IKECFG MO to control the interval for
sending NAT update packets. The NATKLI parameter is used in the DSP IKECFG
and LST IKECFG commands to query the interval for sending NAT update packets,
and used in the SET IKECFG command to set the interval.
None
None

None
Related Operations
 Run the MML command ADD IKEPEER with NATTRAV set to ENABLE to enable
the NAT traversal function.
 Run the MML command SET IKECFG to set the timer for NAT keepalive packets.

CR-MBTS10.1-079
Feature ID
None

None.

None.

5.2.2.1 Critical
5.2.2.1.1 Ports on the management plane can be scanned through all DEVIP addresses

Copyright © Huawei
Ticket
Number
Descriptio Condition: The "OM connection security policy" function is disabled.

n Symptom: Ports (6000, 6006, and 6007) on the management plane can be
scanned through all DEVIP addresses.
Impact: This problem violates the principle that ports on the management
plane cannot be scanned by the control and user planes when OMCH IP
addresses are correctly configured and used.
Severity Critical
Root When the "OM connection security policy" function is disabled, ports
Cause (6000, 6006, and 6007) on the management plane can be spoofed by IP
address 0, that is, spoofed by all IP addresses of the base station.
Solution The ONLYOMIP parameter is added to the GTRANSPARA MO. It can be
used in the MML command SET OMCONNPOLICY and the CME GUI to
enable the "OM connection security policy" function.
Solution The solution does not affect the existing sites. After an upgrade to a later
Impact version, the OM connection security policy remains unchanged.
For a newly deployed site in a later version, the "OM connection security
policy" function is enabled by default. Therefore, a correct OMCH IP
address must be configured using the ADD OMCH command and the
U2000 must be connected to the base station using the OMCH IP address.
5.2.2.2 Major
5.2.2.2.1 The GUI for offline intermodulation interference test is not user-friendly
Ticket
Number
Descriptio Condition: An offline intermodulation interference test is conducted.

n Symptom: There are a large number of parameters for offline
intermodulation interference test, which are not easy to use.
Impact: The usability is affected.
Severity Major
Root The GUI is not user-friendly and needs to be optimized.

Cause
Solution The GUI is optimized as follows:

The 3-Order IM product threshold, 5-Order IM product threshold, and
7-Order and above IM product threshold parameters are replaced by the
PIM Product Threshold parameter.
The Assistant Data field is added to the output information.

Copyright © Huawei
Solution None
Impact
5.2.2.3 Minor
5.2.2.3.1 Name extensions of files to be downloaded are not checked
Ticket
Number
Descriptio Condition: The attacker has authorities of a local user that is at a higher
n level than User or the attacker is a domain user and therefore can execute
the following commands: DLD FILE, DLD GENFILE, and DLD
CERTFILE.
Symptom: The attacker runs the DLD FILE, DLD GENFILE, or DLD
CERTFILE command to download an executable file to the base station
and executes it.
Impact: The attacker can harm security of the base station, for example, by
using trojan viruses.
Severity Minor
Root The type of files is not checked before uploading and downloading of the
Cause files.
Solution When the three commands are used for downloading files, the target files'
name extensions must be those of the file types that are supported by the
commands.
For example, the DLD CERTFILE command is used to download a
certificate file. The target file's name extension can only be the name
extension of a certificate file. Otherwise, the command cannot be executed.
Solution None
Impact
5.2.2.3.2 Board fault alarms fail to be displayed if board software detects faults on the
UTRP or UTRPc board.

Ticket
Number
Description Condition: The UTRP or UTRPc board is configured for a NodeB and
board software detects faults on the board.
Symptom: The following board fault alarms fail to be displayed on the

Copyright © Huawei
alarm console:
 ALM-26200 Board Hardware Fault
 ALM-26208 Board File System Damaged
 ALM-26106 Board Clock Input Unavailable
 ALM-26216 Board Not Securely Installed
 ALM-26203 Board Software Program Error
Impact: Users cannot be alerted to unavailability of the UTRP or UTRPc
board.
Severity Minor
Root Cause The device management module masks fault information sent from board
software.
Solution The alarm check mechanism used by the device management module has
been optimized so that the module does not mask fault information
reported by board software.
Solution If board software detects faults on the UTRP or UTRPc board, related
Impact alarms will be displayed on the alarm console to alert users to board
unavailability.
5.2.2.3.3 ALM-26200 Board Hardware Fault is not reported when the CPU port of a
UTRPc board is faulty.

Ticket
Number
Description Condition: Exceptions occur in packet sending and receiving on the CPU
port of a UTRPc board.
Symptom: The volume of data sent through the UTRPc board is reduced
by about 25%. The board software log shows that packets are sent
through the CPU port of the UTRPc board but are not received by the
peer end.
Impact: ALM-26200 Board Hardware Fault is not reported, leading to a
failure in prompt maintenance.
Severity Minor
Root Cause The mechanism for checking packets sent from and received by the CPU
port of the UTRPc board is defective. As a result, no alarm is reported
when exceptions occur in packet sending or receiving on the CPU port of
the UTRPc board.
Solution The defective mechanism has been corrected so that ALM-26200 Board
Hardware Fault is reported when exceptions occur in packet sending or
receiving on the CPU port of the UTRPc board.
Solution When exceptions occur in packet sending or receiving on the CPU port of

Copyright © Huawei
Impact the UTRPc board, ALM-26200 Board Hardware Fault is reported to alert
users to board faults.
5.2.2.4 Suggestion
5.2.2.4.1 VoLTE services that require transmission of large packets fail in scenarios
where IPSec encryption is used

Number
Description Condition: In IPSec encryption scenarios, a maximum transmission

unit (MTU) is used by the transmission equipment in the core
network (CN), which cannot be modified without permission, and
the plain text packets sent by the security gateway (SeGW) are
larger than the MTU.
Symptom:The large packets are discarded by the transmission
equipment in the CN.
Impact:Services requiring transmission of large packets fail.
Severity Suggestion
Root Cause After IPSec encryption, large packets exceed the size of the MTU.
Then the packets are fragmented and then reassembled by the
security GW. When being transmitted to the CN, the packets are
discarded by transmission equipment because the transmission
equipment uses a small MTU.
Solution Plain text is fragmented on the base station and the length of each
fragment is smaller than the MTU of the CN equipment.
The IPSECPREFRGSW parameter in the ADD IKEPEER and
MOD IKEPEER commands is used to control whether the plain
text will be fragmented before IPSec encryption. When
IPSECPREFRGSW is set to ON, the MTU parameter is used to
specify the size of each fragment. By default, this solution is
disabled for both deployment and upgrade scenarios.
Solution Impact If fragmentation is performed before IPSec encryption, the
reassembly work is taken over by the CN equipment. Performance
of the SeGW is improved, but performance of the CN equipment,
for example, the unified packet gateway (UGW), is deteriorated and
the transmission efficiency of the CN is deceased.
5.2.3 Known Issues

None.

Copyright © Huawei
5.3 NodeBFunction
None.

None.

None.

5.3.2.1 Critical
None.
5.3.2.2 Major
5.3.2.2.1 The RRC connection setup success rate slightly decreases for the cell
established on the WBBPb or WBBPd board.

Number
Description Condition: Uplink baseband equipment serving a local cell contains the
WBBPb or WBBPd board, and the WRFD-140212 CE Overbooking
feature is activated for the NodeB.
Symptom: The number of rejected RRC connection setup requests
caused by uplink CE congestion increases for the cell, which can be
indicated by the VS.RRC.Rej.ULCE.Cong counter.
Impact: The RRC connection setup success rate slightly decreases for the
cell established on the WBBPb or WBBPd board, which can be indicated
by the RRC.ConnEstab.Succ.Rate counter.
Severity Major
Root Cause If CE Overbooking is activated, the mechanism for measuring consumed

uplink CEs on the WBBPb or WBBPd board needs to be optimized.
Consequently, there is a low probability that the statistical value of
consumed uplink CEs is larger than expected. In this situation, uplink
CEs are considered as insufficient and therefore the RRC connection
setup success rate decreases.
Solution The mechanism has been optimized to correctly measure consumed
uplink CEs on the WBBPb or WBBPd board when CE Overbooking is
activated.

Copyright © Huawei
Solution None
Impact
5.3.2.3 Minor
None.
5.3.2.4 Suggestion
None.
5.3.3 Known Issues

None.

Copyright © Huawei
BTS3900 V100R010C10SPC120 Changes from V100R009C00SPC180 to V100R010C10
(NodeB) Release Notes Changes from V100R009C00SPC180 to V100R010C10

V100R010C10
6.1 Change Summary

in V100R010C10. For details, see 6.1.1 Capacity and Performance.
Hardware
Compared with those in V100R009C00SPC180, 9 board types have been added to and 3
board types have been modified in V100R010C10. For details, see 6.1.2 Hardware.

Compared with those in V100R009C00SPC180, 30 features and functions have been added,
24 features and functions have been modified, and 0 features and functions have been deleted
in V100R010C10. 6.1.3 Features and Functions provides the following information about new
or modified features and functions:
Resolved issues
issues, and 45 suggestion-level issues have been resolved in V100R010C10. 6.1.4 Resolved
Issues provides the following information about resolved issues:

Copyright © Huawei

remain unchanged in V100R010C10. For details about MML command and parameter
remain unchanged in V100R010C10. For details about counter changes, see 8.5 Counter
Changes.
unchanged in V100R010C10. For details about alarm and event changes, see 8.3 Alarm
unchanged in V100R010C10. For details about license changes, see 8.6 License
Changes.
templates have changed in V100R010C10. For details, see 6.1.6 Related Documentation.

Compared with that in RAN16.0, capacity increases in RAN17.1.
 The number of HSPA UEs served by a single cell established on the WBBPd or WBBPf
board increases from 128 to 192.
 The quantity of sector equipment supported by the UBBPd6 board increases from 6 to 12
when Independent Demodulation of Signals from Multiple RRUs in One Cell is
activated.
Compared with that in RAN16.0, performance improves in RAN17.1.
If uplink services of HSUPA UEs are carried on the WBBPf or UBBP board, peak RTWP
decreases, cell throughput increases, and system stability improves.
RTWP peaks are likely to occur in either of the following scenarios:
 A few HSUPA UEs are performing high-speed data transmissions in multipath
propagation.
 Multiple HSUPA UEs are simultaneously performing data transmissions and interference
occurs between the UEs.

Copyright © Huawei
6.1.2 Hardware
New Hardware
Hardware Hardware Function Description
Type Name
Board BBU3910A3 The BBU3910A is renamed BBU3910A3. The BOM

description is changed from "Function Module-BBU3910A-
WD2MUMDU-Outdoor Distributed Baseband Unit (DC-
48V)-with WIFI Module-including Engineering Installation
Kit" to "Function Module-BBU3910A3-WD2MUMDUa3-
Outdoor Distributed Baseband Unit (DC-48V)-Type A-
including Engineering Installation Kit."
Board RRU3952  TX/RX channel: 2T4R
 Frequency band: 850 MHz
 RX frequency band: 824 MHz to 849 MHz; TX frequency
band: 869 MHz to 894 MHz
 Working mode: GO, UO, LO, GU, GL, and UL
 Output power: 2x60 W
 Power supply type: DC
 TX/RX channel: 2T4R
Uplink: 1850 to 1910 MHz; downlink: 1930 to 1990
MHz
 Working modes: GO, UO, LO, GU, UL, and GUL
 Power: 2x60 W
Board RRU3953  TX/RX channel: 2T4R
 RX frequency band: 1850 MHz to 1910 MHz; TX
frequency band: 1930 MHz to 1990 MHz
 Working mode: GO, UO, LO, GU, UL, GL, and GUL
 Output power: a maximum of 2x80 W power is supported.
In GO mode, a maximum of 2x60 W power is supported.
Board AAU3920  TX/RX channel: 2T4R
 Frequency band: 1800 MHz+2100 MHz
− 1800 MHz: 1730 MHz to 1780 MHz in the uplink;
1825 MHz to 1875 MHz in the downlink
− 2100 MHz: 1920 MHz to 1980 MHz in the uplink;
2110 MHz to 2170 MHz in the downlink
 Working mode:
− 1800 MHz: LO and GL
− 2100 MHz: UO, LO, and UL

Copyright © Huawei

Type Name
 Output power: 2x80 W (1800 MHz+2100 MHz)
Subrack BBU3910A1 The BBU3910A1 is an outdoor multimode BBU. It supports
the minimum specifications among all outdoor BBUs. Its
maximum specifications are as follows:
 UMTS: UL: 512 CEs/DL: 768 CEs; six 2T2R or 2T4R
cells
 LTE FDD: 3x20 MHz 4T4R
 LTE TDD: 3x20 MHz 4T4R
 UL concurrency: UL: 256 CEs/DL: 384 CEs (in UMTS
mode)+3x20 MHz 2T2R (in LTE mode); six cells in
UMTS mode
Subrack BBU3910A2 The BBU3910A2 is an outdoor multimode BBU. Its
specifications are as follows:
 UMTS: UL: 768 CEs/DL: 768 CEs; six 2T2R or 2T4R
cells
 LTE FDD: 6x20 MHz 2T2R
 UL concurrency: UL: 384 CEs/DL: 512 CEs (in UMTS
mode)+3x20 MHz 2T2R (in LTE FDD mode); six cells
in UMTS mode
Board RRU3962  TX/RX mode: 2T4R (ports A and B are 1800 MHz TX
ports; ports C and D are 2100 MHz TX ports)
 Frequency band: 1800 MHz+2100 MHz dual-band
− 1800 MHz band: 1710 to 1785 MHz in the uplink
and 1920 to 1980 MHz in the downlink
 Working modes:
− 1800 MHz band: GO/LO/GL
− 2100 MHz band: UO/LO/UL
 Power: 2x80 W
Board RRU3952m  TX/RX channel: 2T4R
 Frequency band: 1800 MHz (both transmit and receive
channels), 2100 MHz (only receive channels)
 Working modes:

Copyright © Huawei

Type Name
 Power: 2x60 W
Board RRU3832m  TX/RX channel: 2T4R
 Frequency band: 2100 MHz (both TX and RX channels),
1800 MHz (only RX channels)
− 2100 MHz band: 1920 to 1980 MHz in the uplink;
2110 to 2170 MHz in the downlink
 Working modes:
 Power: 2x60 W
Module BBU3910A BBU3910A is an integrated outdoor BBU, which combines
main control, transmission, and baseband into one unit.
BBU3910A has the following specifications:
 Supports GSM, UMTS, LTE FDD, and LTE TDD.
 The baseband specifications are the same as those of the
UBBPd6.
 The transmission and signaling specifications are the
same as those of the UMPTb.
 Dimensions (H x W x D): 400 mm x 300 mm x 100 mm
 IP65 compliant
Compared with V100R009C00SPC180, V100R010C10 adds hardware types listed in
Table 1.1 New hardware types

Update Type Name
New BBU3910A
New UMDU
For details about the new hardware, see 3900 Series WCDMA Base Station Product
Description.
Modified Hardware
Type Name
Board UPEUd  Updated the silkscreen on the UPEUd board to make the

Copyright © Huawei

Type Name
panel information more intact.

 Modified the ejector levers to make them more smooth.
 Changed the board name from WD22UPEF to
WD22UPEG.
Board RRU3908 V2  TX/RX channel: 2T2R
− Uplink: 890 MHz to 915 MHz
− Downlink: 935 MHz to 960 MHz
 Working mode: GO, UO, LO, GU, and UL
 Change point: In addition to GO, UO, and GU modes,
the RRU3908 V2 operating in 900 MHz can also work
in LO and UL modes.
Board MRFU V2  TX/RX channel: 1T2R
− Uplink: 835 MHz to 849 MHz
− Downlink: 880 MHz to 894 MHz
 Working mode: GO, UO, LO, GU, and UL
 Change point: In addition to GO, UO, and GU modes,
the MRFU V2 operating in 850 MHz can also work in
LO and UL modes.
Subrack BBU3910 The BBU3910 supports the GTMUb, enabling the CPRI
cable to be led out from slot 6.
Board RHUB3908 Serves as a pRRU combiner and a power over Ethernet
(PoE) power module, which provides two CPRI optical
ports and eight CPRI electrical ports. The eight CPRI
electrical ports support power sourcing equipment (PSE).
Deleted Hardware
None

V100R010C10 to V100R009C00SPC180:
 Change type

Copyright © Huawei
 (Optional) RAT
V100R010C10 (NodeB).xlsx.

This section provides the following aspects of issues resolved in BTS3900 V100R010C10 but
unresolved in BTS3900 V100R009C00SPC180:
 Severity
 Solution impact
 (Optional) RAT
For details about these issues, see Summary of Resolved Issues in BTS3900 V100R010C10
(NodeB).xlsx.

unchanged in V100R010C10. For details about changes to MML commands and parameters,
see 8.1 MML Command Changes and 8.2 Parameter Changes.

unchanged in V100R010C10. For details about counter changes, see 8.5 Counter Changes.

unchanged in V100R010C10. For details about changes to alarms and events, see 8.3 Alarm

Copyright © Huawei

unchanged in V100R010C10. For details about changes to license control items, see 8.6
License Changes.

Version
Combined Parameter Redundant information was (For Customer)3900

Reference and MO removed from MO Reference and Series Base Station
Reference into MO and Parameter Reference. To help the Product
Parameter Reference. customer better understand the Documentation(V100R01
relationships between MOs and 0C10_Draft A)(HDX)-EN
parameters, the information is now
arranged as follows: first, MOM
views, and then descriptions of
relevant MOs, and finally details
about the parameters in each MO.
3900 Series Base This document provides
Station NodeBFunction information about the
Used Reserved Counter NodeBFunction used reserved
List has been added. counters, including the object type,
meaning, and measurement point
of each used reserved counter.
3900 Series Base This document provides
Station information about the
eNodeBFunction Used eNodeBFunction used reserved
Reserved Counter List counters, including the object type,
has been added. meaning, and measurement point
of each used reserved counter.
DBS3900(BBU3910A) This document describes how to
Installation Guide has install the cabinets, boards,
been added. modules, and cables for the
DBS3900 (BBU3910A) in outdoor
AC and outdoor DC scenarios. It
also provides checklists for
hardware installation.
RRU3952(850M) This document describes the
Hardware Description appearance, panels, LEDs, and
has been added. cables of the RRU3952(850M).
Installation Guide has installation procedures and
been added. methods of the RRU3952(850M).
RRU3668 Hardware This document describes the
Description has been appearance, panels, LEDs, and
added. cables of the RRU3668.

Copyright © Huawei

Version
RRU3668 Installation This document describes the

Guide has been added. installation procedures and
methods of the RRU3668.
Maintenance Guide has maintenance of the RRU3168.
been added.
AAU3911 Hardware This document describes the
added. cables of the AAU3911.
AAU3911 Installation This document describes the
methods of the AAU3911.
Maintenance Guide has maintenance of the AAU3911.
been added.
been added.
OPM50M User Guide This document describes the
has been added. exterior, function, ports, and
installation and maintenance
procedures of the OPM50M.

Copyright © Huawei

Version
Hybrid Cable Assembly A hybrid cable assembly is an

Deployment Guide has integrated cable consisting of
been added. optical cables and electrical cables.
In a distributed base station, the
BBU can connect to RRUs by
using hybrid cable assemblies to
transmit baseband signals, and the
DCDU-12B can connect to RRUs
by using hybrid cable assemblies
to provide power for RRUs. This
document describes the functions,
characteristics, structure, and
technical specifications of the
hybrid cable assembly. It serves as
a guidance in installing and
maintaining the hybrid cable
assembly.
Changed the name of The product name is changed.
LampSite Technical
Description to
DBS3900 LampSite
Technical Description.
Changed the name of
LampSite
Configuration
Principles to DBS3900
LampSite
Configuration
Principles.
Changed the name of
LampSite Hardware
Description to
DBS3900 LampSite
Hardware Description.
Changed the name of
LampSite Installation
Guide to DBS3900
Guide.
Changed the name of
LampSite Hardware
Maintenance Guide to
DBS3900 LampSite
Hardware Maintenance
Guide.

Copyright © Huawei

Version
DBS3900 LampSite This document describes the

Spare Parts Catalog details on the spare parts for
has been added. DBS3900 LampSite.
Outdoor Adjusted The Outdoor Adjusted Plinth
Plinth (Width of 600 (width of 600 mm) is no longer
mm) Installation Guide delivered and will be switched to
has been deleted. the OAP800.
Combined Parameter Redundant information was BTS3900 V100R010C10
Reference and MO removed from MO Reference and Reference-EN
Reference into MO and Parameter Reference. To help the
Parameter Reference. customer better understand the
relationships between MOs and
Changed the section The original Feature Changes BTS3900 V100R010C10
names in Release Notes section includes not only features Release Documents-EN
as follows: but also functions.
 Changed Feature
Changes into
Feature and
Function Changes.
 Changed New
Features into New
Features and
Functions.
 Changed Modified
Features into
Modified Features
and Functions.
 Changed Deleted
Features into
Deleted Features
and Functions.
 Changed Summary
of Feature Changes
into Summary of
Feature and
Function Changes.

Copyright © Huawei

Version
Changed the name of In the added or modified features

the Trouble Ticket and functions, some are triggered
Number field into by issues and others are triggered
Requirement/Trouble by requirements.
Ticket Number in the
RN template in the
Feature and Function
Changes section.
Added the Impact on The Impact on KPIs Before
KPIs Before Upgrade Upgrade field was added to
field to the Summary of optimize the Summary of Resolved
Resolved Issues template.
Issuestemplate.
Incorporated delta Reorganized the documents based
documents and disuse on the base station resource model
lists of the BTS3900, to present a clear view of
BTS3900 WCDMA, comparison between different
and BTS3900 LTE into types of NEs. You can choose to
one document. This view information of base stations
document contains four supporting one or multiple modes,
parts (Node, including G, U, L, GU, GL, UL,
GBTSFunction, and GUL, to easily compare
NodeBFunction, and different modes.
eNodeBFunction) and
the Applicable Mode
field is added to the
document for easy
identification.
Added the following  The change information about
columns to the MO and recommended values was
Parameter Changes provided for the customer to
template: adjust the configuration
Recommended Value according to the change in time.
(New), Recommended  The customer can learn about
Value (Old), Feature feature changes on a per feature
ID, and Feature Name. basis.

Copyright © Huawei

Version
 Divided the Change  The column was divided based
Description column on different customer groups,
into multiple so that different customer
columns by groups can quickly find the
category in the content they want.
Alarm Changes and  The meanings of the fields are
Event Changes clearer, which makes it easy for
templates. users to understand.
 Divided the Impact
on NBI Data
column into the
Involve the NBI
and Compatible
with the NBI
columns in the
Alarm Changes and
Event Changes
templates.
Divided the Impact on The meanings of the fields are
NBI Data column into clearer, which makes it easy for
the Involve the NBI users to understand.
and Compatible with
the NBI columns in the
Performance Counter
Changes template.
Added the Remarks Supplementary descriptions about
column to the following exceptions in disuse scenarios are
documents: Disuse added. For example, a parameter is
Parameter List, Disuse disused due to its deletion.
Alarm List, Disuse
Event List, and Disuse
Performance Counter
List

Copyright © Huawei
6.2 Node
6.2.1.1.1 Obtaining Information About the Reused TMA in Base Station Swapping
Scenarios
Description
In base station swapping scenarios where the antenna is to be reused, information about
whether to install the tower-mounted amplifier (TMA) and parameters of the TMA cannot be
completely obtained. Therefore, parameters related to the TMA cannot be correctly
configured for the base station, and the base station uplink coverage is affected.
With this feature, information about the reused TMA can be obtained by supplying power to
the antenna port, scanning, and deciding the uplink signal quality. In this way, the TMA
information can be correctly configured.
Implementation
 Identification of a smart tower-mounted amplifier (STMA)
The switch of power supply to the antenna port is turned on, and an antenna line device
(ALD) scan is performed to identify the STMA connected to RF modules of a base
station.
 Identification of a common TMA
The values of the received total wideband power (RTWP) or received signal strength
indicator (RSSI) before and after the switch of power supply to the antenna port is turned
on are compared to identify the common TMA connected to RF modules of a base
station.
 Identification of a third-party TMA
The uplink frequency is scanned to check whether the minimum RTWP value is close to
the background noise. If so, a third-party TMA is not installed or uplink interference
does not exist.

None
Impact on NEs
This feature must work with the U2000 and BSC of a matched version.
Impact on Hardware
RF modules other than the pRRU, MPMU, DRFU, DRRU, MTXU, and AAU support this
feature.

Copyright © Huawei

None

None
The MML command CFM TMA is added.
None
None

None
Related Operations
To check the connection of a common TMA, run the MML command CFM TMA.
Requirement/Trouble Ticket Number

IR-SRAN10.1-Sys-01-FeR01
Feature ID
None
6.2.1.1.2 Inter-frequency Mutual Aid of RF Modules
Description
The RRU3952m can be configured as a 1.8 GHz 2T2R+2.1 GHz 2R module and the
RRU3832m can be configured as a 2.1 GHz 2T2R+1.8 GHz 2R module.
This feature enables the RRU3952m and RRU3832m to serve the same sector and support
inter-frequency mutual aid when a 4-port antenna is used and no external combiner is
configured. In this scenario, these RRUs support the 1.8 GHz 2T4R+2.1 GHz 2T4R
configuration. This feature reduces the number of antennas and therefore decreases costs.
Implementation
Both the RRU3952m and RRU3832m use ports A and B when they work in inter-frequency
mutual aid mode. The switch for RX band mutual aid (the RxFreqBandMutalSw parameter)
is added. When this switch is turned on, inter-frequency RX mutual aid is enabled between
the modules. When this switch is turned off, these modules work as single-band 2T4R
modules.

Copyright © Huawei

None
When the inter-frequency mutual aid feature is enabled, an RF module working in G/U/L
mode supports four RX channels, which improves the uplink gain.
Impact on NEs
This feature needs to be supported by the CME, MBSC, and MBTS.
Impact on Hardware
Only the RRU3952m and RRU3832m support this feature.

None

None
− GBTS:
Added the RxFreqBandMutalSw parameter to the MML commands ADD
BTSRXUBRD, MOD BTSRXUBRD, and LST BTSRXUBRD in the
BTSRXUBRD MO.
− eGBTS/NodeB/eNodeB:
Added the RxFreqBandMutalSw parameter to the MML commands ADD RRU,
MOD RRU, and LST RRU in the RRU MO.
None
None

None
Related Operations
For the GBTS, run the MML command ADD BTSRXUBRD on the BSC with
RxFreqBandMutalSw set to ON.
For the NodeB, eNodeB, and eGBTS, run the MML command ADD RRU with
RxFreqBandMutalSw set to ON.

Copyright © Huawei

CR-SRAN10.1-RF-04R
Feature ID
None
6.2.1.1.3 Local Maintenance of the Outdoor BBU Through WLAN Wireless Network
Interface Card
Description
After this feature is enabled, the base station can be locally connected to and maintained
through the web LMT by using a WLAN wireless network interface card.
Implementation
The WLAN wireless network interface card is an external hot-swappable device and connects
to the BBU through a USB port. It provides the following functions:
1. Parameters of the WLAN wireless network interface card can be configured and queried
through MML commands.
2. Maintain the status and query port status of the WLAN wireless network interface card.
3. The WLAN wireless network interface card can work in parallel with the local
commissioning Ethernet port of the base station. They can use different IP addresses and
network segments.
4. Support the WPA2 security protocol.
5. MML commands can be used to configure the password for connecting to the WLAN
wireless network interface card and to enable or disable the WLAN wireless network
interface card.
The WLAN wireless network interface card can be automatically enabled after the OMCH is
disconnected, and can be enabled or disabled as required after the OMCH is recovered. This
ensures base station security.

None
None
Impact on NEs
Parameters related to the WLAN wireless network interface card can be configured through
the CME.
Impact on Hardware
By default, the WLAN wireless network interface card is delivered with the outdoor BBU
hardware.

Copyright © Huawei

None

None
The MML commands SET LOCALWAP, SET LOCALWAPSW, ADD WLOCALIP,
and SET LOCALWAPPWD and related parameters are added.
None
None

None
Related Operations
None

IR-SRAN10.1-Sys-02
Feature ID
None
6.2.1.1.4 Configurable TWAMP TCP Port Number
Description
To enhance compatibility with a third-party device, base stations running BTS3900
V1000R010C10SPC000 allow configuration of the TWAMP TCP port numbers. When the
base station serves as a TWAMP responder, the numbers of local listening TCP ports can be
configured. When the base station serves as a TWAMP controller, the numbers of peer
listening TCP ports can be configured.
Implementation
The parameter LOCPORT is added to the MO TWAMPRESPONDER to configure the
listening TCP port number of a specified control link at the local end. The parameter
PEERPORT is added to the MO TWAMPCLIENT to configure the listening TCP port
number of a specified control link at the peer end.

None
Copyright © Huawei
Impact on NEs
None
Impact on Hardware
None

None

None
The parameter LOCPORT is added to the MO TWAMPRESPONDER.
The parameter PEERPORT is added to the MO TWAMPCLIENT.
None
None

None
Related Operations
To configure the listening TCP port number for the peer TWAMP server when the base station
serves as a TWAMP controller, run the MML command ADD TWAMPCLIENT to set the
parameter PEERPORT.
To configure the listening TCP port number for the local TWAMP server when the base
station serves as a TWAMP responder, run the MML command ADD
TWAMPRESPONDER to set the parameter LOCALPORT.

IR-SRAN10.1-TRAN-08
Feature ID
None

Copyright © Huawei
6.2.1.1.5 Local Loop Detection
Description
In versions earlier than SRAN10.1, when services or the OMCH of a base station is
interrupted, the OM personnel cannot locally determine whether the interruption is caused by
loops.
This feature provides the local loopback detection function. When the base station reports
ALM-25879 Ethernet Port Broadcast Packets Exceeding Alarm, the number of broadcast
packets sent by the local MAC is calculated, which helps locate whether service or OMCH
interruption of the base station is caused by a loop.
Implementation
The alarm parameter Bc. Packets with Local MAC Addr Received Per Second is added to
ALM-25879 Ethernet Port Broadcast Packets Exceeding Alarm for specifying the number of
broadcast packets sent by ports with the local MAC address per second. When the base station
receives broadcast packets sent from the local MAC, a loop occurs.

None
Impact on NEs
None
Impact on Hardware
None

None

None
None
None
The alarm parameter Bc. Packets with Local MAC Addr Received Per Second is
added to ALM-25879 Ethernet Port Broadcast Packets Exceeding Alarm.

None

Copyright © Huawei
Related Operations
None

IR-SRAN10.1-TRAN-08
Feature ID
None
6.2.1.1.6 Adding an RRU/RFU/AAMU to a CPRI Chain or Ring Through the CME

Without Resetting the Base Station
Description
In versions earlier than V100R010C10, if an RRU/RFU/AAMU needs to be added to a CPRI
ring or a non-chain-tail position on a CPRI chain, the base station needs to be reset when it
receives RRU/RFU/AAMU data prepared using the CME.
After this feature is implemented, the base station does not need to be reset when an
RRU/RFU/AAMU is added to a CPRI chain or a CPRI ring through the CME.
Implementation
This feature is implemented by modifying the validation mode of the parameter PS for the
RRU/RFU/AAMU. However, if the position of an RRU/RFU/AAMU needs to be adjusted on
a CPRI chain, a breakpoint must be set before the position of the RRU/RFU/AAMU. If the
position of an RRU/RFU/AAMU needs to be adjusted on a CPRI ring, the CPRI ports on the
interface boards at the ring head and tail must be blocked. Before an RRU/RFU/AAMU is
added, data configuration related to setting breakpoints or blocking optical ports is delivered
to the base station. After an RRU/RFU/AAMU is added, breakpoints are removed or CPRI
ports are unblocked.

None
Impact on NEs
None
Impact on Hardware
None

None


Copyright © Huawei
None
None
None
None

None
Related Operations
None

IR-SRAN10.1-BBU-07
Feature ID
None
6.2.1.1.7 DHCP Relay Availability Detection on the Transport Network
Description
The Dynamic Host Configuration Protocol (DHCP) relay function is enabled in sites using IP
transmission for the following two reasons:
 When a base station is deployed through PnP, the DHCP is required for enabling the OM
channel. Therefore, the DHCP relay function must be enabled on the transport network
to allow the DHCP packets to reach the U2000.
 When boards need to be replaced during maintenance, the OM channel may be enabled
through PnP to obtain base station configuration.
However, in actual application scenarios, the DHCP relay function may be unavailable on the
transport network and a base station is deployed by locally delivering configuration files.
After the base station is successfully deployed, whether the DHCP relay is available is
unknown. If the DHCP is used to deploy the base station during maintenance, the deployment
may fail.
This feature implements the detection of DHCP relay availability on the IP transport network.
When the OMCH between a base station and the U2000 works properly, this feature can
check whether the DHCP relay function is available through the U2000.
Implementation
When the DHCP relay availability detection function is enabled, the base station sends
broadcast DHCP detection packets, which are relayed to the U2000 if the DHCP relay
function is enabled on the transport network. Then the U2000 returns a DHCP response
packet based on deployment configuration. If the base station receives the DHCP response

Copyright © Huawei
packet, the DHCP relay function is considered available on the transport network. If the
DHCP relay function is disabled on the transport network, the base station cannot receive the
DHCP response packet and the DHCP relay function is considered unavailable.
If L2 networking is used between the base station and the U2000, the base station can still receive the
DHCP response packet if the DHCP relay function is not enabled. However, L2 networking cannot be
used between the U2000 and the base station.

None
Impact on NEs
This feature is supported by GULT base stations, where G indicates eGBTS. Other NEs are
not affected.
Impact on Hardware
This feature is supported by all IP transmission boards, including Ethernet interface boards
and IP over E1/T1 interface boards.

Commands for enabling the DHCP relay availability detection function and for querying the
detection results are added to the southbound interface.

None
The commands STR DHCPRELAYTST and DSP DHCPRELAYTST are added.
None
None

Either of the following features is required:
− GBFD-118601 Abis over IP
− GBFD-118611 Abis IP over E1/T1
− WRFD-050402 IP Transmission Introduction on Iub Interface
− WRFD-050411 Fractional IP Function on Iub Interface
− LBFD-00300403/TDLBFD-00300403 ML-PPP/MC-PPP
None

Copyright © Huawei
None
Related Operations
 To enable the DHCP relay availability detection function, run the command STR
DHCPRELAYTST.
 To query the detection result, run the command DSP DHCPRELAYTST.

IR-SRAN10.1-TRAN-14
Feature ID
None
6.2.1.1.8 Mitigating the Risks of Violating Regulations by Adding an MOC that

Specifies the Authorized Downlink Frequency Band
Description
According to local regulations of some countries, the use of any function of Huawei
equipment should not cause interference to any other operator's adjacent frequencies.
Otherwise, complaints or legal issues may be raised. This regulation may be violated when
the customer performs OM on an RF module, including the offline VSWR test,
intermodulation test, crossed pair detection, and distance to fault (DTF) test.
To mitigate the risk of violating the regulation, the AUTHDLFREQRANGE MO has been
added. The customer can set the AUTHDLFREQRANGE parameter when maintaining an
RF module so that the OM operation takes effect only in the authorized frequency range and
does not affect adjacent frequencies of other operators.
Implementation
The customer may or may not specify frequencies during maintenance of an RF module.
 If no frequency is specified, the scope in which the maintenance takes effect depends on
whether the AUTHDLFREQRANGE parameter is configured:
− When the AUTHDLFREQRANGE parameter is configured, the maintenance takes
effect on the intersection of the frequencies supported by the RRU and the frequency
range specified by the AUTHDLFREQRANGE parameter.
− When the AUTHDLFREQRANGE parameter is not configured, the maintenance
takes effect on frequencies supported by the RRU.
 If frequencies are specified, the maintenance takes effect on the intersection of the
specified frequencies and the frequencies supported by the RRU. Neither the specified
frequencies nor the value of AUTHDLFREQRANGE needs to be verified.

None

Copyright © Huawei
None
Impact on NEs
This feature needs to be supported by the GBSC, CME, and MBTS.
Impact on Hardware
None

None

None
Added the AUTHDLFREQRANGE MO.
Added the following MML commands:
− ADD AUTHDLFREQRANGE
− LST AUTHDLFREQRANGE
− MOD AUTHDLFREQRANGE
− RMV AUTHDLFREQRANGE
None
None

None
Related Operations
Before performing maintenance on an RF module, run the MML command ADD
AUTHDLFREQRANGE or MOD AUTHDLFREQRANGE to set the
AUTHDLFREQRANGE parameter.

IR-SRAN10.1-OM-02
Feature ID
None

Copyright © Huawei
6.2.1.1.9 Multi-BBU Interconnection
Description
 In centralized Cloud BB scenarios, two UMPT_L boards for signaling load sharing are
configured in the BBU that is connected to the USU3910.
 In centralized Cloud BB scenarios where two BBUs are interconnected through the
UCIU, the primary BBU is connected to the USU3910 through the UMPT board, and
LTE main control boards must be configured in the same BBU subrack.
Implementation
 Two UMPT_L boards are configured for signaling load sharing in the BBU which is
interconnected with the USU3910.
 After two BBUs are interconnected through the UCIU, the primary BBU is
interconnected with the USU3910 through the UMPT board.

None
None
Impact on NEs
None
Impact on Hardware
None

None

None
None
None
None

None

Copyright © Huawei
Related Operations
None

CR-RAN10.1-BBU-04R
Feature ID
None
6.2.1.1.10 Four UMTS and LTE RX Channels Supported by the RRU3952 and RRU3942
Combined to Serve the Same Sector
Description
The RRU3942 and RRU3952 with the 2T2R+2R configuration can be combined to support
four UMTS and LTE RX channels.
Implementation
The RRU3942 and RRU3952 with the 2T2R+2R configuration are combined to support four
UMTS and LTE RX channels. In this scenario, a single RRU3942 or RRU3952 supports a
maximum of four 2T2R carriers and four 2R carriers. Therefore, two RRU3942s or
RRU3952s or one RRU3942 and one RRU3952 can be combined to support a maximum of
eight 2T4R carriers.

None
None
Impact on NEs
This feature needs to be supported by the MBTS.
Impact on Hardware
This feature is only applicable to the RRU3942 and RRU3952.

None

None

Copyright © Huawei
None
None
None

None
Related Operations
None

CR-SRAN10.1-RF-05R
Feature ID
None

6.2.1.2.1 Separate Removal of Electromagnetic Subracks Using an MML Command
Description
Before this feature is introduced, electromechanical subracks that are created on the CME but
are not configured with boards cannot be removed using an MML command. After this
feature is introduced, such electromechanical subracks can be removed separately using an
MML command, regardless of whether they are configured with boards.
Electromagnetic subracks are those equipped with the TCU, PMU, FMU, EMU, and CCU.
Implementation
The value range of the SRN parameter in the RMV SUBRACK command has been extended.
Users can specify the number of an electromagnetic subrack to remove this subrack.

None
None
Impact on NEs
None

Copyright © Huawei
Impact on Hardware
None

N/A

None
The value range of the SRN parameter in the RMV SUBRACK command is extended
from {{0~1}, {4~5}} to {{0~1}, {4~5}, {7}, {8}, {11~12}, {14}, {15}, {40~59}}.
None
None

None
None
None
Related Operations
Run the RMV SUBRACK command and specify the SRN parameter to remove the specified
electromagnetic subrack.

IS-05525
Feature ID
None
6.2.1.2.2 Supporting Up to 24 UMTS Cells by a LampSite Base Station
Description
A LampSite base station supports up to 24 UMTS cells. The support reduces the number of
BBUs to be used in demanding areas, such as stadiums, traffic hubs, exhibition centers, and
large-scale shopping malls.

Copyright © Huawei
Implementation
The maximum number of UMTS cells supported by a LampSite base station increases from
12 to 24, with the maximum number of total carriers on all pRRUs remaining 192.

None
None
Impact on NEs
None
Impact on Hardware
None

N/A

N/A
A maximum of 24 UMTS cells can be configured for a LampSite base station.
None
None

None
None
None
Related Operations
Run the ADD ULOCELL command to add a mixed-multi-RRU cell.

Copyright © Huawei

IREQ10004176
6.2.1.2.3 Configurable Status for Local Maintenance Ethernet Ports.
Description
An MML command is used to enable or disable local maintenance Ethernet ports in a base
station. In this way, local maintenance Ethernet ports that are not used can be disabled, which
enhances the security of the base station.
Implementation
The SWITCH parameter in the SET LOCALETHPORT command is used to control whether
to enable or disable local maintenance Ethernet ports in a base station.
When this parameter is set to ENABLE, all the local maintenance Ethernet ports in the base
station are enabled under all circumstances.
When this parameter is set to DISABLE, local maintenance Ethernet ports are automatically
enabled if the base station is disconnected from the U2000. In this way, maintenance
personnel can locate and troubleshoot faults through local maintenance Ethernet ports. If the
connection between the base station and the U2000 is recovered, the original status of the
local maintenance Ethernet ports is restored.

None
None
Impact on NEs
None
Impact on Hardware
Only the WMPT, UMPT, and LMPT boards support this function.

N/A

N/A
Added an MML command SET LOCALETHPORT.

Copyright © Huawei
Added a parameter SWITCH, which controls whether to enable or disable local

maintenance Ethernet ports in a base station. The value ENABLE indicates that this
switch is set to on. The value DISABLE indicates that this switch is set to off.
None
None

None
None
None
Related Operations
 To enable local maintenance Ethernet ports in a base station, run the following
command:
SET LOCALETHPORT: SWITCH=ENABLE;
 To disable local maintenance Ethernet ports in a base station, run the following
command:
SET LOCALETHPORT: SWITCH=DISABLE;

CR-MBTS18-492
6.2.1.2.4 Automatic Adjustment of RRUs' Intermediate Frequency Offset
Description
With this feature, an RRU can automatically adjust its intermediate frequency (IF) to avoid
interference from external signals of frequencies adjacent to the RRU's receive frequency and
improve the receive sensitivity of the system.
Implementation
Run the MML command MOD RRU with IFFREQ set to an appropriate value. The RRU
automatically calculates the optimal IF offset and accordingly adjusts the IF.

− If external interference exists, setting the IF offset may reduce the impact of the
interference to uplink capacity.
− If no interference exists, setting the IF offset may reduce the uplink capacity slightly.

Copyright © Huawei
− If external interference exists, setting the IF offset may reduce the impact of the
interference to uplink receive sensitivity.
− If no interference exists, setting the IF offset may deteriorate the uplink receive
performance slightly.
Impact on NEs
This feature needs to be supported by the CME and U2000.
Impact on Hardware
The following RF modules support this function: RRU3826, RRU3829, RRU3824/3826,
RRU3838, RRU3839, RRU3832, WRFUd, WRFUe, and WRFUa.

None

None
Added the IFFREQ parameter and deleted the IFOFFSET parameter.
None
None

None
Related Operations
If a cell is affected by interference of adjacent frequencies, run the MML command MOD
RRU for the corresponding RRU, with the IFFREQ parameter set to an appropriate value.

CR-SRAN10.1-BBU-03
Feature ID
None

Copyright © Huawei
6.2.1.2.5 Enhanced SSL Algorithms and Maintenance
Description
Some algorithms currently supported by Secure Socket Layer (SSL) have been cracked or
considered weak algorithms. During negotiation, the base station does not deny access of peer
devices supporting only weak algorithms, which poses security risks.
After this feature is implemented, the minimum strength level of algorithms can be configured
for the base station. The minimum strength level of algorithms can be low, medium, or high.
The strength level of algorithms to be negotiated must be higher than or equal to the
configured minimum strength level. If the local device uses a medium-level strength
algorithm, and the peer device supports only the low-level strength algorithms, the negotiation
will fail and the base station will deny access of the peer device, thereby improving network
security.
After this feature is enabled, statistical results of SSL renegotiation can be queried.
Implementation
1. The MML command SET SSLCONF is modified, which allows the configuration of the
minimum strength level of algorithms. The strength level of algorithms to be negotiated
must be higher than or equal to the configured minimum strength level.
2. The MML command SET SSLCS is added, which allows the configuration of the
algorithm suite corresponding to each algorithm strength level. This helps flexibly
handle changes in algorithm strength after the algorithm is cracked.
3. The MML command DSP SSLRENEGO is added to query the statistical results of SSL
renegotiation.

None
Impact on NEs
This feature must work with the U2000, web LMT, or CME of a matched version, which
allows the configuration of the minimum strength level of algorithms and that of algorithm
strength levels corresponding to the SSL algorithm suite.
Impact on Hardware
None

None

None
The parameter LOWESTCSLEVEL is added to the MML command SET SSLCONF.

Copyright © Huawei
The MML commands SET SSLCS and DSP SSLRENEGO are added.
None
None

None
Related Operations
 To configure the algorithm strength of different algorithm suites, run the MML command
SET SSLCS. This operation is optional. The algorithm strength corresponding to the
default algorithm suite meets the current application conditions. If the operator has
special application scenarios, the algorithm strength level can be adjusted by running this
command. If the algorithm is cracked and its strength level is reduced, this command can
also be used for adjustment.
 To set the minimum strength level of SSL algorithms, run the MML command SET
SSLCONF.
 To query the statistical results of SSL renegotiation, run the MML command DSP
SSLREGNO.

IR-SRAN10.1-Sec-03
Feature ID
None
6.2.1.2.6 Security Parameter Setting Added to Security Level Setting
Description
During security level setting, after selecting a security level based on the live network
conditions, security parameters of this security level can be configured.
In BTS3900 V100R010C10, some security parameters are added to security level setting. In
this way, these parameters do not need to be manually configured, thereby improving the
availability of security functions.
Implementation
The following security parameters are added to security level setting:
 Max Miss Times
This parameter indicates the maximum number of failed password attempts. A user
account will be locked if the number of failed password attempts exceeds the value of
this parameter.
For security level 1, the value of this parameter is 5; for security level 2, the value of this
parameter is 3.

Copyright © Huawei
 Weak Password Dictionary Checking Switch

This switch is used for checking whether a password is in the weak password dictionary
when a user adds or modifies a password. If the password is in the weak password
dictionary, this password cannot be used.
This switch must be turned on for each security level.
 Support State Firewall
This parameter indicates the state firewall is supported.
This parameter must be enabled for each security level.
 Renegotiation Switch
This switch can be turned off for security level 1.
This switch must be turned on for security level 2. The default number of allowed
renegotiation times is used for each measurement period.
 Switch
This switch can be turned on for security level 1 and must be turned off for security level
2.

None
Impact on NEs
None
Impact on Hardware
None

None

None
None
None
None

None

Copyright © Huawei
Related Operations
None

IR-SRAN10.1-Sec-06
Feature ID
None
6.2.1.2.7 Port Number Information Added to ACL Rules in End Point Configuration
Mode
Description
In original end point configuration mode, the ACL rules automatically generated for user and
control planes contain only source and destination IP addresses and do not contain port
number information. In this case, the security levels of firewalls configured for ports are low.
After this function is implemented, in end point configuration mode, the ACL rules
automatically generated for user and control planes during packet filtering also contain port
number information. In addition, data flow to be transmitted to the base station is strictly
controlled, thereby improving the security levels of firewalls configured for ports.
Implementation
In end point configuration mode, port number information is automatically added to ACL
rules for user and control planes during the automatic configuration of ACL-based packet
filtering.

None
Impact on NEs
None
Impact on Hardware
The UMPT, LMPT, and UTRPc must be configured for the base station.

None

None

Copyright © Huawei
None
None
None

None
Related Operations
None

IR-SRAN10.1-TRAN-10
Feature ID
None
6.2.1.2.8 Efficiency Improvement in Base Station Upgrade Risk Check
Description
When upgrading the software of a base station by using the U2000 Software Management
Expert, you can execute the upgrade risk check package by selecting either Check All Risks
or Check Key Risks.
If Check All Risks is selected, all risk items are checked. It is recommended that all risk
items be checked and checked problems be resolved in advance.
If Check Key Risks is selected, only key risk items are checked. If all risks have been
checked, you can check only key risks during an upgrade to ensure that all key problems that
may affect the upgrade have been resolved. This avoids spending too much time checking all
risk items.
Implementation
Upgrade risk items contained in the upgrade risk check package fall into two categories: key
items and non-key items. Key items refer to items that have severe impact on the upgrade,
such as items that may cause an upgrade failure and items that may interrupt or affect services
after the upgrade.
If you select Check Key Risks when executing the upgrade risk check package, only key
items are checked. Otherwise, all items are checked.

None

Copyright © Huawei
None
Impact on NEs
None
Impact on Hardware
None

None

None
None
None
None

None
Related Operations
When upgrading the software of a base station by using the U2000 Software Management
Expert, you can execute the upgrade risk check package by selecting either Check All Risks
or Check Key Risks. During an upgrade, if the upgrade risk check package needs to be
executed for multiple times, Check All Risks must be performed for at least one time.

IR-SRAN10.1-OM-01
Feature ID
None
6.2.1.2.9 Enhanced Switchover Mechanism for Active and Standby OM Channels
Description
This function remedies the defect in the switchover mechanism for active and standby OM
channels proposed by the Cyber Security Evaluation Centre (CSEC). The defect allows
attackers to forge User Datagram Protocol (UDP) packets and change the active OM channel

Copyright © Huawei
to the standby OM channel or the standby OM channel to the active OM channel, which
affects the operation and maintenance (OM) of the base station.
With this function, the authentication mechanism for the switchover command is added to the
switchover mechanism for active and standby OM channels, so as to prevent switchover
messages against replay attacks and ensure that attackers cannot forge UDP packets.
Implementation
This function is implemented as follows:
 Re-authentication needs to be performed on the switchover command between a base
station and U2000 to ensure that the command is not forged.
 During re-authentication, exchanged messages are protected by an anti-replay
mechanism to ensure that attackers cannot forge the switchover command.

None
Impact on NEs
This function involves U2000 modifications. Therefore, this function can take effect only
after the U2000 modifications are performed.
Impact on Hardware
None

None

None
None
None
None

None
Related Operations
None

Copyright © Huawei

IR-SRAN10.1-TRAN-13
Feature ID
None
6.2.1.2.10 User Experience Optimization Displayed on the ALD Management Interface
Description
 The Subunit Number, TMA Subunit Number, and RAE Subunit Number parameters
are changed to Number of Subunits, Number of TMA Subunits, and Number of RAE
Subunits, respectively. The Actual Subunit Number and Actual SubUnit Numbers
parameters are changed to Actual Number of Subunits.
 The Sector ID parameter is changed to AISG Sector ID, which facilitates differentiating
sectors in the AISG protocol from sectors in Huawei base station models.
 The Device Name and Subunit Name parameters are added to clearly show the
association between device data and specified devices.
Implementation
eGBTS/NodeB/e GBTS MML Parameter Name Parameter Name
NodeB MML Command Before After Modification
Command Modification
SCN ALD STR Subunit Number Number of Subunits

BTSALDSCAN
ADD/MOD/LST ADD /MOD/LST RET Subunit Number of RET
RET BTSRET Number or RET Subunits
SubUnit Number
ADD/MOD/LST ADD/MOD/LST TMA Subunit Number of TMA
TMA BTSTMA Number or TMA Subunits
SubUnit Number
ADD/MOD/LST N/A RAE Subunit Number of RAE
RAE Number Subunits
DSP RET DSP BTSRET Actual Subunit Actual Number of
Number or Actual Subunits
SubUnit Numbers
DSP TMA DSP BTSTMA Actual Subunit Actual Number of
SubUnit Numbers
DSP RAE N/A Actual Subunit Actual Number of
SubUnit Numbers

Copyright © Huawei
eGBTS UL MML GBTS MML Parameter Name Parameter

Command Command Before Name After
Modification Modification
MOD/LST/DSP MOD/LST Sector ID AISG Sector ID

RETDEVICEDATA BTSRETDEVICEDATA
MOD/LST/DSP MOD/LST Sector ID AISG Sector ID
TMADEVICEDATA BTSTMADEVICEDATA
MOD/LST/DSP N/A Sector ID AISG Sector ID
RAEDEVICEDATA
DSP RETSUBNIT N/A Sector ID Actual Sector
ID
eGBTS UL MML GBTS MML Command New Parameter

Command
DSP DSP Device Name

TMA/TMASUBUNIT/TM BTSTMA/BTSTMASUBUNIT/
ADEVICEDATA BTSTMADEVICEDATA
DSP N/A Device Name
RAE/RAESUBUNIT/RAE
DEVICEDATA
DSP DSP Device Name
RET/RETSUBUNIT/RET BTSRET/BTSRETSUBUNIT/B
DEVICEDATA TSRETDEVICEDATA
DSP N/A Subunit Name
RETSUBUNIT/RETDEVI
CEDATA
DSP N/A Subunit Name
RAESUBUNIT/RAEDEVI
CEDATA

None
None
Impact on NEs
This function must work with the U2000 of a matched version.

Copyright © Huawei
Impact on Hardware
None

None

None
The Subunit Number, TMA Subunit Number, and RAE Subunit Number parameters
are changed to Number of Subunits, Number of TMA Subunits, and Number of RAE
Subunits, respectively. The Actual Subunit Number and Actual SubUnit Numbers
parameters are changed to Actual Number of Subunits.
The Sector ID parameter is changed to AISG Sector ID.
The Device Name and Subunit Name parameters are added.
None
None

None
Related Operations
None

IR-SRAN10.1-BBU-11
Feature ID
None
6.2.1.2.11 Reporting the Electronic Label of the BBU Subrack to the U2000
Description
Customers need to check equipment according to serial numbers on the packing list and those
displayed on the U2000. However, serial numbers of some equipment cannot be displayed on
the U2000. This feature enables the serial numbers of BBU subracks to be displayed on the
U2000 to facilitate information query.

Copyright © Huawei
Implementation
The serial number of a BBU subrack is reported to the U2000 after the DSP ELABEL
command is executed.

None
Impact on NEs
This feature has impact on the U2000 and base stations and needs to be supported by the
U2000 and base stations.
Impact on Hardware
None

This feature is implemented on existing interfaces including the interface between the base
station and the U2000 and the northbound interface of the U2000.

None
Added the serial number of the BBU subrack.
None
None

None
Related Operations
The serial number of the BBU subrack is added to the output of the DSP ELABEL command.

IR-SRAN10.1-Sys-05
Feature ID
None

Copyright © Huawei
6.2.1.2.12 Enhanced Signature Algorithm for the Device Certificate
Description
The base station originally uses the SHA1 algorithm as the default signature algorithm for
digital certificates. However, the SHA1 algorithm is considered unsecure.
Therefore, the SHA256 algorithm is now used as the default signature algorithm for digital
certificates to improve security of base stations.
Implementation
The default value of the SIGNALG parameter in the MML command ADD CA is changed to
SHA256.

None
None
Impact on NEs
None
Impact on Hardware
None

None

None
None
None

None
Related Operations
None

Copyright © Huawei

CR-SRAN10.1-Sec-02
Feature ID
None
6.2.1.2.13 Optical Power Check on CPRI and Transmission Ports Supported in NE

Health Check
Description
In NE health check by the U2000, optical power is not detected. In this case, faults in fiber
optic cables, spliced fibers, and optical modules cannot be detected. Therefore, optical power
check on CPRI and transmission ports is added to the NE health check by the U2000.
Implementation
Based on optical module information in the output of the DSP SFP command reported by the
base station, the U2000 checks the status of the optical modules.

None
Impact on NEs
This function must work with the U2000 of a matched version. For a GBTS, this function
must work with the BSC of a matched version.
Impact on Hardware
None

None

None
None
None
None

Copyright © Huawei

None
Related Operations
None

CR-SRAN10.1-OM-06
Feature ID
None
6.2.1.2.14 RRU Remote Mode Presented in Base Station Configuration
Description
In previous versions, the remote identification information of the RRU cannot be obtained,
and users do not know whether an RRU is remotely installed, which is inconvenient for
maintenance. With this feature, the remote identification information is presented in the RRU
configuration, which can be queried by users.
Implementation
In the MO RRU, the parameter REMOTEFLAG is added for specifying whether an RRU is
remotely installed.

None
Impact on NEs
This feature works with the CME of a specific version.
Impact on Hardware
None

None

None
The parameter REMOTEFLAG is added.

Copyright © Huawei

None
None

None
Related Operations
Run the ADD RRU command to set the REMOTEFLAG parameter to REMOTE(Remote).

CR-SRAN10.1-OM-08
Feature ID
None
6.2.1.2.15 Supporting Independent Base Stations
Description
LampSite base stations, as an innovative indoor solution, require different deployment,
network planning, and maintenance from macro base stations. This feature adds base station
types specific to LampSite and separates LampSite base station from traditional macro base
stations. This allows for independent operation and maintenance of LampSite base stations.
Implementation
The following types of LampSite base stations (DBS3900) are added:
 DBS3900 LampSite (Co-MPT LampSite base stations)
 DBS3900 LampSite WCDMA (UMTS only LampSite base stations)
 DBS3900 LampSite LTE (LTE only LampSite base stations)

None
None
Impact on NEs
The CME and U2000 must be upgraded to a version that supports this feature.

Copyright © Huawei
Impact on Hardware
None

The interfaces between a LampSite base station and the CME or U2000 are affected.

None
DBS3900 LampSite, DBS3900 LampSite WCDMA, and DBS3900 LampSite LTE are
added as three new base station types specified by the PRODUCTTYPE parameter in
the Node MO.
The modification affects the northbound interface (NBI).
None
None

None
Related Operations
1. For a newly deployed LampSite base station, set the PRODUCTTYPE parameter to a
new base station type.
2. An existing base station after an upgrade retains the DBS3900 base station type by
default. To change the base station type to a new type, reconfigure the
PRODUCTTYPE parameter on the CME. The reconfiguration causes the base station to
reset, during which services are interrupted.

IR-Atom10.1-LampSite-015
Feature ID
None

Copyright © Huawei

6.2.2.1 Critical
6.2.2.1.1 In certain scenarios, the baseband processing unit fails to start.

Ticket
Number
Description Condition: The primary and secondary subracks are fully configured.
Symptom: The UBBPd board resets repeatedly.
Impact: The UBBPd board fails to start.
Severity Critical
Root Cause The UBBPd board uses a defective negotiation process.
Solution The defective negotiation process has been corrected.
Solution In full configuration, all the boards configured in the primary and
Impact secondary subracks can start successfully and do not repeatedly reset.
6.2.2.1.2 The UTRPa board occasionally restarts unexpectedly
Trouble Ticket iCare: 3755487

Number DTS: DTS2014112402395
Description Condition: Services deployed on the UTRPa board are transmitted out
of the NodeB through the UTRPa board.
Symptom: The UTRPa board restarts unexpectedly at an interval
varying from two to three hours to up to a couple of days.
Impact:
 The NodeB restarts unexpectedly.
 If OM messages are transmitted out of the NodeB through the
UTRPa board, the NodeB will be disconnected from the U2000.
Severity Critical
Root Cause The NodeB uses defective software to process shared memory for
service links that have been released. As a result, the software still
processes the shared memory that has been then allocated to other
modules, leading to software processing exceptions on these modules.
Solution The software defect has been corrected so that the software does not
process the shared memory for service links that have been released.
Solution None

Copyright © Huawei
Impact
6.2.2.1.3 There is a low probability that the WMPT board unexpectedly restarts

Ticket
Number
Description Condition: Delay-related MML commands are executed and the

execution progress is reported as scheduled.
Symptom: The WMPT board unexpectedly restarts.
Impact: Ongoing services carried on the WMPT board are interrupted
during the restart.
Severity Critical
Root Cause The WMPT board uses a defective multi-task processing mechanism,
causing ineffective protection for partial data. When multiple tasks are
simultaneously using the data, a switchover between tasks leads to a
board restart.
Solution The defective multi-task processing mechanism has been corrected to
enhance protection for global data.
Solution None
Impact
6.2.2.2 Major
6.2.2.2.1 IMA group- and IMA link-related alarms are reported when they should not
be.

Ticket
Number
Description Condition: IMA group- and IMA link-related alarms are displayed on the
maintenance console.
Symptom: IMA group- and IMA link-related alarms are not masked
when they should be.
Impact: IMA group- and IMA link-related alarms are reported when they
should not be, and there is no impact on ongoing services.
Severity Major
Root Cause The masking relationships for IMA group- and IMA link-related alarms

Copyright © Huawei
are incorrect.
Solution The masking relationships have been corrected for IMA group- and IMA
link-related alarms.
Solution None
Impact
6.2.2.2.2 In combined RRU configuration, the project quality check fails.

Ticket
Number
Description Condition: In RRU combined configuration, the project quality check is

enabled on the U2000 to check antenna installation quality issues.
NOTE
RRU combined configuration: Two RRUs with different cabinet/subrack/slot
configurations are combined to serve the same sector.
Symptom: During the project quality check, the commissioning task
status is abnormal. According to the deployment report, intermodulation
interference detection fails with an error message indicating that the
target port does not exist.
Impact: The project quality check fails.
Severity Major
Root Cause The channel ID is incorrect for the intermodulation interference

detection. As a result, the delivered channel ID does not exist on the
corresponding RRU.
Solution The channel ID is now correctly set for intermodulation interference
detection in combined RRU configuration.
Solution None
Impact
6.2.2.2.3 Users having common rights can run some MML commands defined only for
users having administrator rights.

Ticket
Number
Description Condition: The NodeB is configured with the WMPT board or the base
station works in UMTS Only mode.
Symptom: Users having common rights can run some MML commands

Copyright © Huawei
defined only for users having administrator rights. These commands

include the following:
 FOC CMCTRL
 FOC NECMCTRL
 RBK BATCHFILE
 REQ CMCTRL
 REQ NECMCTRL
 SET CMCTRLSW
 ULK CMCTRL
Impact: Some MML commands are not permission-controlled.
Severity Major
Root Cause The customization mechanism is defective.
Solution The defective customization mechanism has been corrected.
Solution The customer interface is changed, affecting user habits.

Impact
6.2.2.2.4 The access success rate decreases on the UBBPd board.

Ticket
Number
Description Condition: The NodeB is configured with the UBBPd.

Symptom: UEs occasionally cannot access the NodeB.
Impact: The access success rate decreases.
Severity Major
Root Cause The UBBPd board uses a defective mechanism to send messages. As a
result, the UBBPd board occasionally fails to send a message.
Solution The defective mechanism has been corrected on the UBBPd board.
Solution None
Impact
6.2.2.2.5 The STR RTWPRTTST command output shows only single-carrier RTWP
information


Copyright © Huawei
Number
 Multiple carriers are configured for an antenna.
 The RRU serves multiple cells.
 A user runs the STR RTWPRTTST command.
Symptom: The command output shows RTWP information for only one
carrier.
Impact: The RTWP routine test result is inaccurate.
Severity Major
Root Cause In the preceding instance, the carrier IDs are fixed at 0 (default value) in
the reported RTWP information. As a result, only RTWP for carrier 0 can
be obtained.
Solution The carrier IDs now are correctly set in the reported RTWP information
depending on configured carriers.
Solution None
Impact
6.2.2.2.6 There is a possibility that the RRC connection setup success rate decreases

Number
Description Condition: The NodeB is successfully restarted or upgraded.

Symptom: There is a possibility that the RRC connection setup success
rate decreases to 0 and cannot be recovered to a normal level.
Impact: UEs' access requests are rejected.
Severity Major
Root Cause In the preceding instance, the CPU usage initialization module has a
defect. As a result, the module uses the dirty data in the memory that has
not been initialized as the CPU usage during the restart. In this situation,
services are not allocated CPU resources, causing the RRC connection
setup success rate to decrease to 0.
Solution The defect in the CPU usage initialization module has been rectified so
that the requested memory can be initialized.
Solution None
Impact

Copyright © Huawei
6.2.2.3 Minor
6.2.2.3.1 The output of the DSP IPSECSA6 command is incomplete.

Ticket
Number
Description The DSP IPSECSA6 command output does not provide information
about remaining flows of an SA.
Severity Minor
Root Cause The output display mechanism for the DSP IPSECSA6 command is
defective.
Solution The DSP IPSECSA6 command output now provides information about
remaining flows of an SA.
Solution None
Impact
6.2.2.3.2 After a certificate expires, automatic certificate acquisition fails.

Ticket
Number
Description Condition: Certificate expiration triggers automatic certificate

application.
Symptom: Automatic certificate application succeeds, but the obtained
certificate fails to be loaded.
Impact: Automatic certificate acquisition fails.
Severity Minor
Root Cause After users run the ADD CERTMK and MOD APPCERT command,
the save path of the obtained certificate is incorrect. As a result, the target
certificate file cannot be located when it needs to be loaded.
Solution The certificate is saved in the correct directory to ensure that the
certificate file can be located.
Solution None
Impact

Copyright © Huawei
6.2.2.3.3 The device panel for the OMB (Ver.C) cabinet is incorrectly displayed.

Ticket
Number
Description Condition: A TCU is installed in the OMB (Ver.C) cabinet. The TCU
provides the panel file extracting capability.
Symptom: The device panel displays the old OMB cabinet panel.
Impact: The displayed board layout is incorrect.
Severity Minor
Root Cause A monitoring device obtains the device panel file of the OMB cabinet
and then updates the device panel. However the OMB (Ver.C) cabinet
does not provide device panel file.
Solution The panel display for the OMB (Ver.C) or APM (Ver.D) cabinet now does
not depend on the device panel file. If the cabinet type reported by the
monitoring device is OMB (Ver.C) or APM (Ver.D), the NMS refreshes
the device panel.
Solution The board layout on the device panel is modified.
Impact
6.2.2.3.4 If the main control boards work in active/standby mode, services carried in the
MP group are interrupted.

Ticket
Number
Description Condition: The main control boards work in active/standby mode. The
slot number for the active main control board is inconsistent with the
logical slot number. An MP group is configured on the active control
board and MP links are configured in the MP group.
Symptom: Negotiation fails between the MP group and MP link.
Impact: Services carried in the MP group are interrupted.
Severity Minor
Root Cause If the slot number for the active main control board is inconsistent with
the logical slot number, the mechanism for obtaining the internal E1/T1
status is defective.
Solution None
Impact

Copyright © Huawei
6.2.2.3.5 The deployment check fails occasionally.

Ticket
Number
Description Condition: Users use the CME to generate configuration files for a
LampSite base station to be deployed, and do not manually configure RF
information for pRRUs. Then, users deliver the configuration files to the
LampSite base station and start a deployment check.
Symptom: The deployment check fails occasionally. The probability of
check failures increases if a large number of pRRUs are deployed.
Impact: In the event of a deployment check failure, users are confused
about the deployment results, although the LampSite base station can
normally provide services.
Severity Minor
Root Cause The configuration files generated by the CME do not contain RF
information of pRRUs, but the LampSite base station automatically
configures and validates the RF information when executing
configuration files. If a deployment check is started before the RF
configuration takes effect, the check fails due to incomplete data
configuration.
Solution The deployment check scripts have been modified to check whether RF
configuration has taken effect.
Solution None
Impact
6.2.2.3.6 The links between pRRUs and the BBU in the LampSite solution become
faulty.

Ticket
Number
Description Condition: pRRUs are restarted.

Symptom: There is a low probability that ALM-26235 RF Unit
Maintenance Link Failure is reported.
Impact: Services are interrupted on the pRRUs for which is alarm is
reported.
Severity Minor
Root Cause In the event of clock signal fluctuation between the RHUBs and pRRUs,
code errors occur in the links between them, causing intermittent link
disconnections.

Copyright © Huawei
Solution The clock synchronization mechanism has been optimized to ensure the
link connectivity when clock signals fluctuate within a certain range.
Solution None
Impact

ID
6.2.2.4 Suggestion
6.2.2.4.1 The MML command description is incorrect.

Ticket
Number
Description Condition: The U2000 or WebLMT displays the English navigation tree.
Symptom: The RMV USERPLANEPEER command is incorrectly
described.
Impact: The GUI display misguides users.
Severity Suggestion
Root Cause The RMV USERPLANEPEER command is incorrectly interpreted as

"Remove User Plane Host." The correct interpretation is "Remove User
Plane Peer."
Solution The RMV USERPLANEPEER command is now interpreted as
"Remove User Plane Peer."
Solution None
Impact
6.2.2.4.2 If SSLv3 is used to encrypt data exchanged between a NodeB and the NMS, the
encrypted data may be cracked

Ticket
Number
Description Condition: A NodeB is under an SSLv3 attack.

Symptom: Encrypted data exchanged between the NodeB and the NMS
may be cracked.
Impact: A leakage of secret information may occur.
Severity Suggestion
Root Cause The SSLv3 protocol encounters security vulnerabilities.

Copyright © Huawei
Solution An SSL negotiation interface has been added to allow operators to

disable SSLv3.
Solution None
Impact
6.2.2.4.3 An inaccurate prompt message is displayed after TLS1.2 is disabled on the

CME.

Ticket
Number
Description Condition: TLS1.2 is disabled on the CME.

Symptom: An inaccurate prompt message is displayed.
Impact: Users cannot correctly configure the supported SSL version.
Severity Suggestion
Root Cause TLS1.2 must not be disabled. Therefore, if it is disabled, a message

indicating that TLS1.2 must not be disabled should be displayed.
However, an incorrect message reading "The value of TLS/SSL Version in
the SSL Configuration MO ranges from 8 to 15" is displayed after
TLS1.2 is disabled.
Solution The prompt message is now changed to "The TLS1.2 version cannot be
disabled for SSL::VERSION in the SSL MO".
Solution None
Impact
6.2.2.4.4 The traffic volume queried by running the DSP ETHTRK command or using
traffic statistics is different from the actual one in the trunk group.

Ticket
Number
 A trunk group is configured.
 The traffic volume in the trunk group is queried by running the DSP
ETHTRK command or using traffic statistics.
Symptom: The traffic volume queried by running the DSP ETHTRK
command or using traffic statistics is different from the actual one in the
trunk group.
Impact: The reported traffic volume of the trunk group is incorrect.

Copyright © Huawei
Severity Suggestion
Root Cause The CI port is included in calculation of member Ethernet ports in the
trunk group. However, the number of member Ethernet ports should not
contain the CI port.
Solution The CI port is now excluded from the number of member Ethernet ports.
Solution None
Impact
6.2.3 Known Issues

None
6.3 NodeBFunction
6.3.1.1.1 WRFD-171201 Crystal Voice in Deep Coverage
Description
This feature deploys a high-order channel decoding algorithm on the DEUa board of the RNC
to perform high-order channel decoding again on voice frames that experienced a low-order
channel decoding failure. This reduces the block error rate (BLER) and improves the voice
quality in deep coverage scenarios.
To improve the MOS of CS voice services, this feature deploys a high-order channel decoding
algorithm on the RNC to perform high-order channel decoding again on voice frames that
experienced a decoding failure. Therefore, this feature reduces the BLER and improves the
voice quality. This feature performs different actions depending on the application scenario:
In a non-soft handover area, this feature directly performs high-order decoding.
When the Seamless Crystal Voice feature is disabled in a soft handover area, the Crystal Voice
in Deep Coverage feature selects the best tributary on which high-order decoding is
performed for error voice frames after selective combining.
When the Seamless Crystal Voice feature is enabled in a soft handover area, the Crystal Voice
in Deep Coverage feature performs high-order decoding on voice frames whose BLER failed
to be corrected by the Seamless Crystal Voice feature.
Implementation
For details, seeCrystal Voice in Deep Coverage Feature Parameter Descriptionin the RAN
feature documentation package.

Copyright © Huawei

− After this feature is enabled, pre-decoding information is sent to the DEUa board for
high-order decoding. In this case, inter-subrack traffic increases and counters in the
following table are affected.
Counter Name Description NE
VS.Frame.Flux.Peak.TxRate HR9732a:Peak Inter-Subrack BSC6900

Transmitting Traffic and
BSC6910
VS.Frame.Flux.Mean.TxRate AR9732a:Average Inter-Subrack BSC6900
Transmitting Traffic and
BSC6910
− After this feature is enabled, the Iub/Iur bandwidth consumption increases. When the
Iub/Iur bandwidth is insufficient and the flow control function is not triggered, PS
throughput-related counters in the following table are affected.
VS.PS.BE.DCH.UL.SumTh Sum of Sampled Uplink BE BSC6900 and BSC6910

roughput Throughput of UEs with PS
Services over DCHs
VS.HSUPA.MeanChThroug Mean Uplink Throughput of BSC6900 and BSC6910
hput single HSUPA MAC-d Flow
for Cell
VS.HSUPA.MeanBitRate.W Average throughput of NodeB
ithData HSUPA users in a cell when
data is transmitted
− Impacts on the MOS are as follows:
In a poor-quality network:
− When the WRFD-140201 AMR Voice Quality Improvement Based on PLVA feature
is disabled, this feature increases the average MOS of AMR voice services by 0.1 to
0.5.
− When the WRFD-140201 AMR Voice Quality Improvement Based on PLVA feature
is enabled, this feature increases the average MOS of AMR voice services by 0.05 to
0.3.
In a high-quality network:
− This feature increases the proportion of AMR voice services with a high MOS by 5%
to 10%.
− This feature increases the end-to-end delay for voice services by less than 30 ms, but
does not affect network KPIs such as the call drop rate, access success rate, and
handover success rate.

Copyright © Huawei
When WRFD-170201 Seamless Crystal Voice is enabled, enabling this feature does not increase the
delay for voice services.
− After the uplink RMA optimization function is enabled, the current signal
interference ratio (SIR) converges at the target SIR more quickly. In this case, the
value of the VS.ULBler.AMR counter slightly increases, but the quality of voice
services is not affected.
VS.ULBler.AMR UL BLER of AMR Services BSC6900 and BSC6910

on DCH
Impact on NEs
This feature is implemented on the RNC and NodeB.
Impact on Hardware
 The RNC must be configured with the DEUa board.
 3900 series base stations do not support this feature when they only use WBBPa boards
as the baseband processing boards and support this feature when they use other types of
boards as the baseband processing boards.

On the user plane
 An information element (IE) is added to user-plane private control frames over the Iub or
Iur interface in the downlink for instructing the NodeB to report pre-decoding
information.
 Pre-decoding information is added to DCH data frames over the Iub or Iur interface in
the uplink.
On the control plane
 For the Iub interface:
− A proprietary IE "Crystal voice in deep coverage ability" is added to the AUDIT
RESPONSE message over the Iub interface. The NodeB uses this IE to inform the
RNC whether it supports this feature.
− A proprietary IE "Crystal voice in deep coverage Cap Indication" is added to the
RESOURCE STATUS INDICATION message over the Iub interface. The NodeB
uses this IE to inform the RNC whether the NodeB supports this feature.
− A proprietary IE "Crystal voice in deep coverage open Ind" is added to the RADIO
LINK SETUP REQUEST and RADIO LINK RECONFIGURATION PREPARE
messages over the Iub interface. The RNC uses this IE to inform the NodeB whether
the NodeB can use this feature.
 For the Iur interface:
− A proprietary IE "Crystal Voice In Deep Coverage Cap Req" is added to the RADIO
LINK SETUP REQUEST, RADIO LINK ADDITION REQUEST, and RADIO LINK
RECONFIGURATION PREPARE messages over the Iur interface. The SRNC uses
this IE to obtain the capability of the NodeB on the DRNC side.

Copyright © Huawei
− A proprietary IE "Crystal Voice In Deep Coverage Cap Indication" is added to the

RADIO LINK SETUP REQUEST, RADIO LINK ADDITION REQUEST, and
RADIO LINK RECONFIGURATION PREPARE messages over the Iur interface.
The DRNC uses this IE to inform the SRNC whether the NodeB supports this feature.

 Impact on license managemant
The following license control item has been added to accommodate this feature.
Feature ID Feature Name License NE Sales Unit
Control Item
WRFD-171201 Crystal Voice in Crystal Voice in BSC6900 and Per Erl

Deep Coverage Deep Coverage BSC6910
(Per Erl)

Type ID Command
New PROCESSS SET BSC690 Switch for the RNC-level Crystal

WITCH5: URRCTRLSWI 0 Voice in Deep Coverage
CRYSTAL_ TCH BSC691 function. This parameter controls
VOICE_DE 0 whether the RNC-level Crystal
EPCOVER_ Voice in Deep Coverage function
SWITCH takes effect. When this switch is
set to on, the RNC-level Crystal
Voice in Deep Coverage function
takes effect. When this switch is
set to off, the RNC-level Crystal
does not take effect.
New NodeBAlgo ADD BSC690 Switch for the NodeB-level
EnhSwitch: UNODEBALG 0 Crystal Voice in Deep Coverage
NODEB_CR OPARA BSC691 function.
YSTAL_VOI MOD 0 This parameter controls whether
CE_DEEPC UNODEBALG the NodeB-level Crystal Voice in
OVER_SWI OPARA Deep Coverage function takes
TCH effect. When this switch is set to
on, the NodeB-level Crystal
takes effect. When this switch is
set to off, the NodeB-level
Crystal Voice in Deep Coverage
function does not take effect.
New IurCrstVoice ADD UNRNC BSC690 Switch for controlling whether
DpCoverSup MOD UNRNC 0 the Iur interface supports the
pInd BSC691 Crystal Voice in Deep Coverage
0 function.

Copyright © Huawei

Type ID Command
When this switch is set to off, the

Iur interface does not support the
Crystal Voice in Deep Coverage
function. That is, the radio links
(RLs) added on the Iur interface
during a soft handover do not
participate in the processing of
Crystal Voice in Deep Coverage.
When this switch is set to on, the
Iur interface supports the Crystal
Voice in Deep Coverage
function. That is, the RLs added
on the Iur interface during a soft
handover participate in the
processing of Crystal Voice in
Deep Coverage.
New PerfEnhanc SET BSC690 Switch for the uplink RMA
eSwitch6: UCORRMPAR 0 optimization function.
PERFENH_ A BSC691 This parameter controls whether
VOICE_DE 0 the uplink RMA optimization
EPCOVER_ function takes effect when the
ULRMA_OP RNC-level Crystal Voice in Deep
T_SWITCH Coverage function is enabled.
When this switch is set to on, the
uplink RMA optimization
function takes effect. When this
switch is set to off, the uplink
RMA optimization function does
not take effect.

The following counters have been introduced to accommodate this feature.
Change Counter Function NE Description
Type Subset
New VS.AMR.Crs TRAFF.LOA BSC690 Equivalent Erlang of AMR

tVoiceDeepC D.RNC 0 Services Using Crystal Voice in
over.Erlang.E BSC691 Deep Coverage for RNC
quiv.RNC 0
New VS.AMR.Crs TRAFF.LOA BSC690 Maximum Equivalent Erlang of
tVoiceDeepC D.RNC 0 AMR Services Using Crystal
over.MaxErla BSC691 Voice in Deep Coverage for
ng.Equiv.RN 0 RNC
C
New VS.AMR.Crs TRAFF.LOA BSC690 Equivalent Erlang of AMR
tVoiceDeepC D.RNC 0 Services Using Crystal Voice in

Copyright © Huawei

Type Subset
over.Erlang.E BSC691 Deep Coverage for RNC (per

quiv.PLMN.R 0 Operator)
NC
New VS.AMR.Crs TRAFF.LOA BSC690 Maximum Equivalent Erlang of
tVoiceDeepC D.RNC 0 AMR Services Using Crystal
over.MaxErla BSC691 Voice in Deep Coverage for
ng.Equiv.PL 0 RNC (per Operator)
MN.RNC
New VS.EVQI.A EVQI.CELL BSC690 Average UL EVQI Value of
MRNB.UL.B 0 AMR-NB Services That
LERRank0.A BSC691 Correspond to BLER Level 0
verage 0
verage 0
verage 0
verage 0
verage 0
MRWB.UL.B 0 AMR-WB Services That
verage 0
verage 0
verage 0

Copyright © Huawei

Type Subset

verage 0
verage 0

No impact.

No impact.
No impact.
Related Operations
For details, see section "Engineering Guidelines" inCrystal Voice in Deep Coverage Feature
Parameter Descriptionin the RAN feature documentation package.

IR-RAN17.1-001
Feature ID
WRFD-171201
6.3.1.1.2 WRFD-150209 DB-HSDPA
Description
The Dual-Band HSDPA (DB-HSDPA) feature allows a single UE to simultaneously establish
connections with two inter-band same-coverage cells. With this feature, a single UE can use
the resources of two cells operating in different frequency bands, which increase the UE's
peak throughput.
 This feature is described as follows:
Primary/secondary carrier configuration in a DB-HSDPA cell group If a DB-HSDPA cell
group consists of two cells, 3GPP Release 9 specifies that a DB-HSDPA UE must: Use
the downlink frequency of one cell as the primary carrier and that of the other cell as the
secondary carrier. Use the uplink frequency of the cell corresponding to the primary
carrier only.

Copyright © Huawei
Two cells in a DB-HSDPA cell group are both configured with the P-CPICH, SCH, P-
CCPCH, S-CCPCH, and PRACH. In addition, this feature enables UEs to camp on and
initiate services in the two cells.
 Application scope
This feature does not apply to CS services, IP Multimedia Subsystem (IMS) signaling,
PS conversational services, or SRB signaling, because the gains provided by this feature
are not noticeable for services that have only a small amount of data to transmit. This
feature applies to services that may have a large amount of data to transmit, for example,
streaming or best effort (BE) services.
 Selection of DB-HSDPA or Dual-Carrier HSDPA (DC-HSDPA) cell groups
In a network supporting both DB-HSDPA and DC-HSDPA, the two features have the
same configuration priority because: A UE supporting DB-HSDPA also supports DC-
HSDPA. DB-HSDPA and DC-HSDPA provide similar gains. Therefore, the selection of
DB-HSDPA or DC-HSDPA cell groups depends on the traffic steering or load balancing
policy.
 Mobility management
The active set information and measurement results are based on the primary carrier
when a DB-HSDPA UE is being handed over. If the frequencies of the primary carrier
before and after the handover are the same, this handover is an intra-frequency handover.
Otherwise, this handover is an inter-frequency handover.
 RAN15.0 supports handovers between DB-HSDPA cells, between DB-HSDPA and DC-
HSDPA cells, between DB-HSDPA and Single-Carrier HSDPA (SC-HSDPA) cells, and
between DB-HSDPA and inter-RAT cells to ensure seamless roaming for DB-HSDPA
UEs. (RAT is short for radio access technology.)
 State transition for DB-HSDPA UEs
The state transition procedure for DB-HSDPA UEs is the same as that for non-DB-
HSDPA UEs.
 The following table lists the combinations of frequency bands supported by DB-HSDPA.
DB-HSDPA Combination of Uplink Frequency Downlink Frequency
Configuration Frequency Bands Band Band
1 I + VIII (2100 MHz I or VIII I and VIII
+ 900 MHz)
2 II + IV (1900 MHz II or IV II and IV
+ AWS)
3 I + V (2100 MHz + I or V I and V
850 MHz)
4 II + V (1900 MHz + II or V II and V
850 MHz)
Implementation
For details, see section "Change History" inDB-HSDPA Feature Parameter Descriptionin
RAN feature documentation.

Copyright © Huawei

The change in this feature has no impact.
Impact on NEs
The enhancement of this feature is implemented on the NodeB.
Impact on Hardware


A license control item has been added for this feature.
Feature ID Feature License License NE Sales Unit
Name Control Control
Item Name
WRFD- DB-HSDPA LQW9DBD DB-HSDPA NodeB per Cell

150209 PA01 Function(per
Cell)



Copyright © Huawei
Related Operations
For details, see chapter "Engineering Guidelines" inDB-HSDPA Feature Parameter
Descriptionin RAN feature documentation.

IR-RAN17.1-013
Feature ID
WRFD-150209
6.3.1.1.3 WRFD-150250 3C-HSDPA
Description
This feature was first specified by 3GPP Release 10. It uses three carriers for High Speed
Downlink Packet Access (HSDPA) transmission of a UE, thereby increasing the UE's
downlink throughput.
 This feature was first specified by 3GPP Release 10. This feature allows a UE to set up
HSDPA connections with three carriers that each use HSDPA and 64QAM. This enables
the UE to simultaneously receive data from multiple carriers, thereby increasing single-
user throughput.
 When 3C-HSDPA is configured, uplink data packets can be carried on the Dedicated
Channel (DCH), High Speed Uplink Packet Access (HSUPA), or Dual-Carrier HSUPA
(DC-HSUPA) channel. The signaling radio bearer (SRB) for the UE is carried over DCH
or HSDPA.
 The radio access network (RAN) schedules 3C-HSDPA UEs and other HSDPA UEs
jointly for fast resource allocation and load balancing among carriers. The joint
scheduling also increases UE throughput and improves fairness among UEs on different
carriers.
 The three carriers that are used for 3C-HSDPA must belong to the same NodeB and
cover the same area. The three carriers can operate in either the same or different
frequency bands. For details about the combinations of frequency bands that can be used
for 3C-HSDPA, see 3GPP Release 10 TS 25.104.
The following table describes the 3C-HSDPA configuration in single-band scenarios.
3C-HSDPA Configuration in Operating Band Number of Downlink
Single-Band Scenarios Carriers
I-3 I 3
The following table describes the 3C-HSDPA configuration in dualband scenarios.

3C-HSDPA Uplink Band Downlink Number of Downlink Number of
Configuratio Band A Downlink Band B Downlink
n in Carriers in Carriers in
Dualband Band A Band B
Scenarios
I-2-VIII-1 I or VIII I 2 VIII 1

Copyright © Huawei
II-1-IV-2 II or IV II 1 IV 2
II-2-IV-1 II or IV II 2 IV 1
I-1-V-2 I or V I 1 V 2
I-2-V-1 I or V I 2 V 1
The three carriers used for 3C-HSDPA must be adjacent.

 This feature applies to PS best effort (BE) services, streaming services, and combined
services that include PS BE or streaming services.
 This feature is not suitable for CS services, IP Multimedia Subsystem (IMS) signaling,
PS conversational services, or SRB signaling, because the benefits of this feature are
negligible for these services that have only a small amount of data to transmit.
Implementation
For details, see section "Change History" inMC-HSDPA Feature Parameter Descriptionin

Impact on NEs
The change in this feature is implemented on the RNC and NodeB.
Impact on Hardware


Item Name
WRFD- 3C-HSDPA LQW93CDP 3C-HSDPA NodeB per Cell

150250 A01 Function(per

Copyright © Huawei

Item Name
Cell)


The exclusiveness with the following features has been removed. That is, this feature can
now be used together with the following features:
− WRFD-010686 CPC-DTX/DRX
− WRFD-010687 CPC-HS-SCCH Less operation
− WRFD-010713 Traffic-Based Activation and Deactivation of the Supplementary
Carrier In Multi-carrier
Related Operations
For details, see the description about engineering guidelines for 3C-HSDPA inMC-HSDPA
Feature Parameter Descriptionin RAN feature documentation.

IR-RAN17.1-013
Feature ID
WRFD-150250
6.3.1.1.4 WRFD-150251 HSPA+ Downlink 63Mbit/s per User
Description
This feature uses 3C-HSDPA to increase the maximum downlink single-user data rate to 63
Mbit/s.

Copyright © Huawei
3GPP Release 10 defined the HSPA+ Downlink 63 Mbit/s per User feature, which allowed the
combination of 3C-HSDPA+64QAM to increase the maximum downlink single-user data rate
to 63 Mbps.
Implementation
For details, seeHSPA Evolution Feature Parameter Descriptionin RAN Feature
Documentation.

Impact on NEs
Impact on Hardware


Control Item
WRFD-150251 HSPA+ HSPA+ RNC Per kbps

Downlink Downlink
63Mbit/s per 63Mbit/s per
User User (per kbps)


Copyright © Huawei

− WRFD-150250 3C-HSDPA
− WRFD-010689 HSPA+ Downlink 42Mbps per User
None
None
Related Operations
For details, see "Engineering Guidelines" inHSPA Evolution Feature Parameter Descriptionof
RAN Feature Documentation.

IR-RAN17.1-013
Feature ID
WRFD-150251
6.3.1.1.5 WRFD-171207 Virtual CPC
Description
As the smartphone penetration rate and data transmission requirements increase, the
increasing HSUPA users on the live network causes the proportion of power consumption on
uplink control channels to increase. As a result, the uplink capacity is limited. To increase the
uplink capacity, Huawei introduces the virtual CPC feature in RAN17.1. This feature reduces
the transmit power of non-CPC terminals when there is no data transmission, further reducing
the overhead of control channel load on the air interface and improving the uplink capacity.
Huawei introduced the CPC - DTX/DRX feature in RAN11.0 to reduce the control channel
overhead for users performing burst services when there is no data transmission. However, the
proportion of CPC-capable UEs is low on the live network. The CPC - DTX/DRX feature
cannot significantly reduce the overhead of uplink control channels. Therefore, Huawei
introduces the virtual CPC feature based on the Turbo IC Phase 2 feature.
The Turbo IC Phase 2 feature introduces the single HARQ technology. For HSUPA users with
2 ms transmission time interval (TTI), only one process of the UE is activated for uplink data
transmission. This feature is intended for HSUPA users that use the single HARQ technology.
With this feature, power control is performed by differentiating active and inactive processes,
thereby decreasing the power of uplink control channels for inactive processes and increasing
uplink capacity. The details are as follows:
 For active processes, power control is performed using the SIRtarget before feature
introduction. Then, when the UE has burst data transmission, the NodeB can still ensure
the demodulation performance of data.
 For inactive processes, the NodeB can predict that the UE will not send uplink data.
Therefore, the NodeB can further reduce the UE's transmit power, thereby improving the
uplink capacity.

Copyright © Huawei
Implementation
For details, seeVirtual CPC Feature Parameter Description.

This feature can increase uplink capacity by 5%–15% in scenarios in which there are a
large number of HSUPA 2 ms TTI users and uplink power resources are insufficient. If a
large number of users access a cell, this feature can increase the number of radio links by
5%-15%.
No impact.
Impact on NEs
Impact on Hardware
BTS3911Es support this feature. 3900 series base stations and LampSite base stations support
this feature when meeting the following requirements:
 3900 series base stations are configured with the WBBPf or UBBPd board.
 LampSite base stations are configured with the WBBPf or UBBPd board.

No impact.

Control Item
WRFD-171207 Virtual CPC Virtual CPC NodeB Per Cell

The following parameter has been introduced to accommodate this feature.
Type ID Command
New VIRTUALC MOD NodeB This new parameter specifies

PC ULOCELL whether to enable the Virtual
CPC feature.

Copyright © Huawei

Type Name Subset
New VS.HSUPA.V HSUPA.LOC NodeB Average number of virtual CPC

irtualCPC.Us ELL users in a cell
erNum.Mean
New VS.HSUPA.V HSUPA.LOC NodeB Average SIRtarget decrease of
irtualCPC.SI ELL virtual CPC users in a cell
RTargetDec.
Mean

No impact.

− WRFD-160213 Turbo IC Phase 2
− WRFD-010636 SRB over HSUPA
− WRFD-010610 HSDPA Introduction Package
None
This feature requires that thePwrCtrlAlgparameter in the inner loop power control
algorithm be set toALGORITHM1. If this parameter is not set toALGORITHM1,
inner loop power control cannot be performed in time, which causes the power
control function of the Virtual CPC feature to not work properly. As a result, KPIs
deteriorate.
− WRFD-160205 CE Efficiency Improvement for HSUPA TTI 2ms
After the WRFD-160205 CE Efficiency Improvement for HSUPA TTI 2ms feature is
enabled, the Virtual CPC feature takes effect for more users.
Users using the following features do not support the Virtual CPC feature:
− WRFD-010684 2×2 MIMO
The Virtual CPC feature does not take effect for UEs using HSDPA MIMO.
The Virtual CPC feature does not take effect for platinum users.
− WRFD-010686 CPC - DTX / DRX
The Virtual CPC feature does not take effect for UEs using Discontinuous
Transmission (DTX)/Discontinuous Reception (DRX).
The Virtual CPC feature does not take effect for time-division scheduled UEs.
The Virtual CPC feature does not take effect for UEs using 3C-HSDPA.

Copyright © Huawei
The Virtual CPC feature does not take effect for UEs using 4C-HSDPA.
The Virtual CPC feature does not take effect for UEs performing low traffic services.
− WRFD-171209 Coverage Improvement for HSUPA 2ms TTI UEs
The Virtual CPC feature does not take effect for UEs using the WRFD-171209
Coverage Improvement for HSUPA 2ms TTI UEs feature.
Related Operations
See the section "Engineering Guidelines" inVirtual CPC Feature Parameter Description.

IR-RAN17.1-007
Feature ID
WRFD-171207
6.3.1.1.6 WRFD-171209 Coverage Improvement for HSUPA 2 ms TTI UEs
Description
Compared with that for HSUPA user with 2 ms TTI and R99 users, the coverage for HSUPA
user with 2 ms TTI is poor. As a result, the number of 2 ms TTI users is limited and the better
user experience provided by the 2 ms TTI cannot be achieved. In addition, there will be a
large number of switchovers between 2 ms TTI and 10 ms TTI, which affects user experience.
This feature uses the virtual power scaling technology. With this technology, the network side
controls the power ratio of control channels to data channels for HSUPA 2 ms TTI users,
thereby improving the coverage performance of HSUPA 2 ms TTI users.
If the UE's transmit power is limited in data transmission scenarios, performing outer loop
power control (OLPC) by adjusting the SIR Target based on the BLER leads to the following
problem: Abnormal data transmission first occurs while user signaling is normal. This feature
allows for OLPC by adjusting the SIR Target based on the UE's transmit power, thereby
reducing the number of call drops caused by abnormal data transmission in weak coverage
areas.
This feature applies to HSUPA 2 ms TTI users who have data to transmit. Using the optimal
DPCCH transmit power ratio as the target, the network side controls the UE's transmit power
by adjusting the SIR Target, thereby improving the coverage performance of HSUPA 2 ms
TTI users at the cell edge.
Implementation
For details, see the change history ofPower Control Feature Parameter Descriptionin RAN
Feature Documentation.

No impact.

Copyright © Huawei
This feature improves coverage for HSUPA 2 ms UEs performing data transmission. The
coverage performance can be improved by 1 to 5 dB for a single user, which decreases
the HSUPA call drop rate.
Impact on NEs
This feature needs the support from UEs of E-DCH Category 6 and later.
Impact on Hardware
The 3900 series base stations must be configured with the WBBPb, WBBPd, WBBPf, or
UBBPd board.

No impact.

Control Item
WRFD-171209 Coverage Coverage BSC6900 per Cell

Improvement Improvement BSC6910
for HSUPA 2 for HSUPA 2
ms UEs ms UEs

Type ID Command
New PcSwitch1: SET BSC690 Indicates whether to enable the

PC_HSUPA_ UCORRMALG 0 Coverage Improvement for
TTI_2MS_C OSWITCH BSC691 HSUPA 2 ms UEs feature. When
OVER_IMP 0 this switch is turned on, this
_SWITCH feature is enabled. When this
switch is turned off, this feature
is disabled.


Copyright © Huawei
Change Counter Functio NE Description

Type n
Subset
New VS.HSUPA.2msT HSUPA. NodeB Average Number of HSUPA 2

TI.VPSUserNum. LOCEL ms TTI UEs in the Virtual Power
Mean L Scaling State in a Cell
New VS.HSUPA.2msT HSUPA. NodeB Number of times UPH values
TI.UPH.0 LOCEL reported by HSUPA 2 ms TTI
L users in a cell are within interval
0
1
2
3

No impact.

− WRFD-01061403 HSUPA 2ms TTI
No impact.
− WRFD-010641 HSUPA Adaptive Transmission
This feature can improve the coverage performance. If the number of retransmissions
is large, the gains of WRFD-171209 Coverage Improvement for HSUPA 2 ms UEs
are small.
− WRFD-010690 TTI Switch for BE Services Based on Coverage
When the coverage-based TTI switch function is disabled and the number of HSUPA
2 ms UEs increases, the HSUPA call drop rate decreases noticeably after this feature
is enabled.
When the coverage-based TTI switch function is enabled, the feature gains are not
noticeable if the coverage-based TTI handover threshold is set to a large value and
the UE switches from HSUPA 2 ms to HSUPA 10 ms before the power becomes
insufficient; the HSUPA call drop rate decreases significantly after this feature is

Copyright © Huawei
enabled if the coverage-based TTI handover threshold is set to a small value and there
are a large number of HSUPA 2 ms UEs.
− WRFD-171207 Virtual CPC
Virtual CPC is not performed for UEs using WRFD-171209 Coverage Improvement
for HSUPA 2 ms UEs.
− WRFD-010695 UL Layer 2 Improvement
UEs using this feature do not support WRFD-171209 Coverage Improvement for
HSUPA 2 ms UEs.
− WRFD-140204 DC-HSUPA
DC-HSUPA UEs do not support WRFD-171209 Coverage Improvement for HSUPA
2 ms UEs.
UEs performing TDM do not support WRFD-171209 Coverage Improvement for
HSUPA 2 ms UEs.
− WRFD-020138 HSUPA Coverage Enhancement at UE Power Limitation
If this feature is enabled together with WRFD-171209 Coverage Improvement for
HSUPA 2 ms UEs, the gains of the former feature decrease.
Related Operations
See section "WRFD-171209 Coverage Improvement for HSUPA 2 ms UEs" in chapter
"Engineering Guidelines" ofPower Control Feature Parameter Descriptionin RAN Feature
Documentation.

IR-RAN17.1-006
Feature ID
WRFD-171209
6.3.1.1.7 WRFD-171204 DPCH Power Control Based on Radio Quality
Description
This feature reduces the transmit power of the associated DPCH for HSDPA users in a cell to
reduce the high non-HSPA power consumption, thereby increasing downlink cell capacity.
The HSDPA user-associated DPCH is used for signaling transmission and power control. In a
network with high penetration rate of smartphones, there are a large number of online users.
In this case, the associated DPCH consumes most of the downlink power load. Therefore, it is
necessary to decrease the transmit power of the associated DPCH and reduce the non-HSPA
power consumption, so as to improve the downlink capacity.
This feature sets the transmit power of the associated DPCH based on the UE's signal quality.
When the UE's signal quality is good, the associated DPCH uses low transmit power. When
the UE's signal quality is poor, the associated DPCH uses high transmit power. Setting the
transmit power of the associated DPCH to an appropriate value can reduce the non-HSPA
power consumption in a cell without compromising user experience, so as to provide
sufficient power resources for users who have data to transmit and improve the downlink cell
capacity.

Copyright © Huawei
On the other hand, setting the transmit power of the associated DPCH may affect the stability
of downlink performance for HSDPA users in the cell and slightly increase the call drop rate.
Implementation
For details, see the change history ofPower Control Feature Parameter Descriptionin RAN

When there are a large number of HSDPA UEs and the downlink non-HSPA power is
high, this feature can increase the downlink capacity of a cell by 10% to 20%, thereby
reducing the downlink non-HSPA power or increasing the downlink throughput.
− This feature can improve the access success rate of a cell during busy hours when the
downlink power of the cell is congested.
− When A-DPCH transmit power is reduced for HSDPA UEs, the Uu-interface
synchronization probability decreases. As a result, the HSDPA call drop rate
increases. This feature can decrease the downlink power consumption in a cell only
when the downlink non-HSPA power is severely congested, which may decrease the
HSDPA call drop rate.
Impact on NEs
This feature is implemented on the RNC and NodeB, and requires the support of UEs for
HSDPA.
Impact on Hardware
UBBPd board.

 Private data is added to the Dedicated Measurement Report message over the Iub
interface for carrying the maximum transmit power of the serving RL reported by the
NodeB to the RNC.
 Private data is added to the DL power Control Request message over the Iub interface for
transmitting the maximum transmit power of the non-serving RL delivered by the RNC
to the NodeB.

Control Item
WRFD-171204 DPCH Power DPCH Power NodeB Per Cell

Control Based Control Based
on Radio on Radio
Quality Quality(per

Copyright © Huawei

Control Item
Cell)

Cha Parameter ID MML Command NE Description
nge
Typ
e
New RADIOQUALITY SET NodeB Switch for controlling

DPCHPCSW ULOCELLALGP the DPCH Power
ARA Control Based on Radio
Quality feature. When
this switch is turned on,
this feature is enabled.
When this switch is
turned off, this feature
is disabled.
New RADIOQUALITY SET NodeB Indicates the load state
DPCHPCLOADST ULOCELLALGP for validating the
AT ARA DPCH Power Control
Based on Radio Quality
feature. When the load
state of downlink non-
HSPA power reaches
the load specified by
this parameter or
higher, the DPCH
power control algorithm
based on radio quality
is triggered.
New RADIOQUALITY SET NodeB Indicates the power
DPCHPCPO ULOCELLALGP offset increased by the
ARA DPCH power control
algorithm based on
signal quality for
adjusting the DPCH
maximum transmit
power.

Type Subset
New VS.RadioQua ALGO.LOCE NodeB Average Number of Users

Copyright © Huawei

Type Subset
lityDPCHPC. LL Enabled with DPCH Power

UserNum Control Based on Radio Quality
in a Cell

The following alarms have been introduced on the RNC side to accommodate this
feature.
Change Alarm/Event NE Description
Type
Modifie ALM-26811 Configured NodeB Added a case in which

d Capacity Limit Exceeding this alarm is reported.
Licensed Limit When the number of
cells configured with
WRFD-171204 DPCH
Power Control Based
on Radio Quality
exceeds the licensed
number, this alarm is
reported.

− WRFD-150235 DPCH Maximum Power Restriction
When this feature is enabled together with WRFD-150235 DPCH Maximum Power
Restriction when the downlink load is high, both features provide gains for the
downlink capacity. However, the HSDPA call drop rate may increase.
− WRFD-150230 DPCH Pilot Power Adjustment
If this feature is enabled together with WRFD-150230 DPCH Pilot Power Adjustment
when the downlink load is high, both features provide gains for the downlink
capacity. However, the maximum A-DPCH transmit power and transmit power of the
pilot field on the DPCCH also decrease. As a result, the estimated SIR becomes less
accurate, which may increase the HSDPA call drop rate.
Related Operations
See section "WRFD-171204 DPCH Power Control Based on Radio Quality" in chapter
"Engineering Guidelines" ofPower Control Feature Parameter Descriptionin RAN Feature
Documentation.

Copyright © Huawei

IR-RAN17.1-011
Feature ID
WRFD-171204
6.3.1.1.8 WRFD-160251 HSDPA Inter-Cell Power Sharing
Description
This feature enables HSDPA cells in a power sharing group (co-power amplifier and co-
sector) to dynamically share idle power to other HSDPA cells that do not have sufficient
power for data transmission. This improves the power resource usage of the power amplifier
(PA) and increases the HSDPA data rate, thereby improving user experience.
When multiple HSDPA cells use the same PA, this feature enables one or more HSDPA cells
to dynamically share the idle power resources of other HSDPA cells.
The following figure assumes that there are only two cells in a power sharing group: cells A
and B. If cell A has data transmission requirements but its power resources are insufficient
and cell B has available power resources, cell B shares its idle power resources to cell A. After
data transmission in cell A is complete, the RNC reclaims these power resources and returns
them to cell B. If users in cell A are using the shared power and cell B initiates data
transmission, the RNC immediately reclaims the shared power to ensure the experience of
uses in cell B. The sharing rules are the same if there are more than two cells in a power
sharing group. If multiple cells need to share the idle power resources of other cells, this
feature allocates the resources based on the history power the former cells. That is, cells with
higher history power will obtain a large proportion of idle power resources.

Copyright © Huawei
Figure 1.1 Power sharing between two HSDPA cells
Implementation
For details, see "Change History" inPower Sharing Feature Parameter Descriptionin RAN
feature documentation.

This feature is enhanced to support power sharing between multiple cells (that is, 2 to 4
cells), instead of two cells in earlier versions. When the maximum power sharing ratio is
set to the recommended value, this feature for multiple cells applies to a greater scope
compared with that for two cells previously, and the average user throughput increases
by 1% to 3%. For users with poor CQIs in the cells, the average throughput even
increases by 50% at most.
The enhancement of this feature has no impact on network performance.
Impact on NEs
The enhancement of this feature is implemented on the NodeB.
Impact on Hardware
The following RF modules have been added to accommodate this feature.

Copyright © Huawei
RF Module Type Feature Supported or Not
MRFUV2a Supported
RRU3839 Supported
RRU3961 Supported
WRFUa Supported

The enhancement of this feature has no impact on inter-NE interfaces.

Feature ID Feature License License NE Sales
Name Control Control Item Unit
Item ID
WRFD- HSDPA LQW9H2H HSDPA Inter- NodeB Per NodeB

160251 Inter-Cell PS01 Cell Power
Power Sharing (Per
Sharing NodeB)
This feature does not require a license when the WRFD-261103 AAS Vertical Multiple Sectors feature
takes effect.
The following parameters have been modified to accommodate this feature.
Type ID Command
New HTOHPWS SET NodeB Indicates the HSDPA inter-cell

HSW ULOCELLAL power sharing switch. If this
GPARA parameter is set toON, power
sharing groups are automatically
established between the cells that
have this switch turned on and
meet HSDPA inter-cell power
sharing requirements. The groups
allow for bidirectional power
sharing.
New SHARINGM SET NodeB Indicates the power sharing
ARGIN ULOCELLAL margin. The margin is used to
GPARA compensate for the required
power for R99 users due to

Copyright © Huawei

Type ID Command
delayed power sharing and

compensate for the power for the
burst services in the HSDPA cell
that provides power for sharing.
New MAXSHARI SET NodeB Indicates the maximum
NGRATIO ULOCELLAL proportion of the available power
GPARA that can be shared between two
cells. The proportion is the ratio
of the available power that a
local cell can provide or request
for sharing to the maximum
transmit power of the local cell.
Deleted PWSHM ADD NodeB PWSHM is replaced by
NODEBPAGR R99TOHPWSHSW.
P
RMV
NODEBPAGR
P
LST
NODEBPAGR
P
Deleted SLOCELL ADD NodeB The NodeB will flexibly select
NODEBPAGR the source cell and destination
P cell that meet the conditions for
RMV power sharing.
NODEBPAGR
P
LST
NODEBPAGR
P
Deleted DLOCELL ADD NodeB The NodeB will flexibly select
NODEBPAGR the source cell and destination
P cell that meet the conditions for
RMV power sharing.
NODEBPAGR
P
LST
NODEBPAGR
P
Deleted MAXSHRTO ADD NodeB MAXSHRTO is replaced by
NODEBPAGR MAXSHARINGRATIO.
P
RMV
NODEBPAGR
P

Copyright © Huawei

Type ID Command
LST
NODEBPAGR
P
Deleted SHMGN ADD NodeB SHMGN is replaced by
NODEBPAGR SHARINGMARGIN.
P
RMV
NODEBPAGR
P
LST
NODEBPAGR
P

The enhancement of this feature has no impact on performance management.
None

The enhancement of this feature has no impact on related features.
Related Operations
For details, see "WRFD-160251 HSDPA Inter-Cell Power Sharing" under chapter
"Engineering Guidelines" inPower Sharing Feature Parameter Descriptionin RAN feature
documentation.

IR-RAN17.1-010
Feature ID
WRFD-160251
6.3.1.1.9 WRFD-171212 Coverage Expansion Under Interference
Description
This feature enables cells with strong interference to use the resources of cells with weak or
no interference, thereby combining the links of multiple cells in the uplink. This enhances the
detection performance and improves the uplink coverage of cells with strong interference.
When strong interference (intra-frequency interference, with repeater configured) occurs in a
cell, this feature configures neighboring cells with weak or no interference as coordinating

Copyright © Huawei
cells, and combines the link of the current cell with that of the cell with strong interference to
improve the uplink cell coverage.
This feature mainly applies to UEs in the access state and connected state:
 Access state: As shown inFigure 6-2, if there is strong interference in a cell and a UE
accesses the cell edge, uplink multi-cell joint detection performance can be obtained by
combining the RACHs of the target cell and coordinating cell. At the same time, the
optimal downlink access performance can be obtained by using the optimal downlink
link, thereby improving the coverage during access.
 Connected state: As shown inFigure 6-3, after a UE access a cell with strong
interference, a physical link is established in the cell with an uplink coordinating link
maintained in a neighboring cell with weak or no interference. In addition, softer
combination is performed to improve user experience.
Figure 1.1 Coverage expansion for UEs in access state

Copyright © Huawei
Figure 1.2 Coverage expansion for UEs in connected state
Implementation
For details, see Coverage Expansion Under Interference Feature Parameter Description.

The NodeB establishes physical links in cells with strong interference and coordinating
links in neighboring cells with weak or no interference for users in connected mode, and
performs softer combination of signals. This improves UEs' demodulation performance,
reduces uplink interference, and improves cell uplink capacity.
The Coverage Expansion Under Interference feature improves the access performance of
CEUs in cells with strong interference and increases the number of online users.
Coordinating links in Coverage Expansion Under Interference consume uplink CE
resources. The number of CEs consumed by coordinating links depends on the number
of coordinating links.
In dual-antenna scenarios: a coordinating link for R99 UEs consumes one CE, a
coordinating link for HSUPA UEs consumes one CE by default when SRB over E-DCH
is enabled, and a coordinating link for HSUPA UEs consumes two CEs by default when
SRB over DCH is enabled.

Copyright © Huawei
Impact on NEs
This feature is mainly implemented on the NodeB. The NodeB cooperates with the RNC to
perform link establishment and mobility management.
Impact on Hardware
Only the 3900 series base stations support this feature. The uplink resource group must
contain the UBBPd board.

No impact.

Table 1.1 License management

Feature ID Feature Name License Control NE Sales Unit
Item
WRFD-171212 Coverage Coverage NodeB per Cell

Expansion Expansion Under
Under Interference (per
Interference Cell)

The following parameters have been modified on the NodeB side to accommodate this
feature.
Table 1.2 Parameter changes

Change Parameter ID MML NE Description
Type Command
Added ULCOVEXPCFG SET NodeB This parameter

MOD NODEBALGPA specifies how to
RA establish coordinating
LST cells after Coverage
NODEBALGPA Expansion Under
RA Interference is
enabled.
The default and
recommended
configuration is
AUTOMATIC.
It can also be set to
MANUAL.

Copyright © Huawei

Type Command
Added ULCOMP ADD NodeB Cell pair

NODEBULCOM configuration in UL
PGRP CoMP
DSP
NODEBULCOM
PGRP
LST
NODEBULCOM
PGRP
RMV
NODEBULCOM
PGRP
Added ULCOVEXP ADD NodeB Cell pair
NODEBULCOM configuration in
PGRP Coverage Expansion
DSP Under Interference
NODEBULCOM
PGRP
LST
NODEBULCOM
PGRP
RMV
NODEBULCOM
PGRP
Added ULCOVEXPANSI ADD ULOCELL NodeB Coverage Expansion
ON MOD ULOCELL Under Interference
LST ULOCELL
Modified HOSTLOCELLID ADD NodeB This parameter
NODEBULCOM specifies the host local
PGRP cell ID in an uplink
DSP joint reception cell
NODEBULCOM pair.
PGRP
LST
NODEBULCOM
PGRP
RMV
NODEBULCOM
PGRP
Modified NEIGHBOURLO ADD NodeB This parameter
CELLID NODEBULCOM specifies the neighbor
PGRP local cell ID in an
DSP uplink joint reception
NODEBULCOM cell pair.
PGRP

Copyright © Huawei

Type Command
LST
NODEBULCOM
PGRP
RMV
NODEBULCOM
PGRP
Modified NODEBID ADD NodeB This parameter
NODEBULCOM specifies the NodeB
PGRP ID for coordinating
DSP cells in a UL CoMP
NODEBULCOM cell pair.
PGRP
LST
NODEBULCOM
PGRP
RMV
NODEBULCOM
PGRP

The following counters have been modified to accommodate this feature.
Table 1.3 Counter changes

Change Counter Name Function NE Description
Type Subset
Added VS.TBNum.Succ.RA PRACH.LOCE NodeB The number of TBs

CH LL obtained by the host
cell from the
coordinating cells
with correct CRCs
over the RACH when
Coverage Expansion
Under Interference is
enabled
Added VS.TBNum.Total.R PRACH.LOCE NodeB The total number of
ACH LL TBs obtained by the
host cell from the
coordinating cells
over the RACH
Added VS.PositiveNum.AIC PRACH.LOCE NodeB The number of
H LL positive
acknowledgments in
the preamble
detection results of

Copyright © Huawei
Change Counter Name Function NE Description

Type Subset
the host cell that are

reported by
coordinating cells
over the RACH
Added VS.NegativeNum.AI PRACH.LOCE NodeB The number of
CH LL negative
acknowledgments in
the preamble
detection results of
the host cell that are
reported by
coordinating cells
over the RACH
Added VS.UlCovExpansion. ALGO.UULCO NodeB Average Number of
UserNum MPGROUP CoMP Users in a
CoMP Cell Pair
Enabled with
Coverage Expansion
Under Interference
Added VS.UlCovExpansion. ALGO.UULCO NodeB Maximum Number
MaxUserNum MPGROUP of CoMP Users in a
CoMP Cell Pair
Enabled with
Coverage Expansion
Under Interference

None

None
− WRFD-021350 Independent Demodulation of Signals from Multiple RRUs in One
Cell
− WRFD-010205 Cell Digital Combination and Split
− WRFD-021308 Extended Cell Coverage up to 200km
WRFD-171212 Coverage Expansion Under Interference is mutually exclusive with
WRFD-021308 Extended Cell Coverage up to 200km, including configuring remote
cell groups and extending cell radius to be greater than 30 km.
− WRFD-151205 Uplink CoMP (Joint Reception)
When cell pairs configured by WRFD-151205 Uplink CoMP (Joint Reception) and
WRFD-171212 Coverage Expansion Under Interference are consistent, coordination

Copyright © Huawei
links based on SIR are consistent. It is good practice to enable only one of the two
features.
− In cells with strong external interference, enable WRFD-171212 Coverage Expansion
Under Interference to increases the access success rate.
− In cells with little interference, enable WRFD-151205 Uplink CoMP (Joint
Reception) to improve uplink capacity.
− WRFD-010701 Uplink Enhanced CELL_FACH
When WRFD-140204 DC-HSUPA is enabled, if users are E-RACH users,
coordinating links cannot be established, and therefore users cannot benefit from
Coverage Expansion Under Interference.
Related Operations
For details, see "Engineering Guidelines" in Coverage Expansion Under Interference Feature
Parameter Description.

IR-RAN17.1-036
Feature ID
WRFD-171212
6.3.1.1.10 WRFD-171210 Radio-Aware Video Precedence
Description
This feature preferentially schedules HTTP video services during HSDPA scheduling in
network congestion scenarios, reduces the initial buffering delay of HTTP video services, and
reduces the proportion of users experiencing video freeze in a cell, thereby improving the user
experience of HTTP video services in the cell.
With the development of UMTS networks, there are more and more video applications. RAN
network congestion becomes increasingly frequent, and video service experience deteriorates
significantly. With this feature, the RNC informs the NodeB of HTTP video service
characteristics (information such as video initial buffer stage, video playing stage, and video
bit rate) detected by the RAN. The NodeB preferentially schedules video services during
HSDPA scheduling to make the initial buffer delay of video services reach the configured
target value. This increases the proportion of video services that do not experience video
freezing in the cell, thereby improving the video service experience in the cell.
During HSDPA scheduling, this feature preferentially ensures the guaranteed bit rate (GBR)
for all users. Then, this feature allocates the remaining resources first to video services, and
then to non-video services. Among video services, those that did not experience video
freezing take priority over those that did. For video services under poor coverage, this feature
may not guarantee their preferential scheduling, to reduce their impacts on cell throughput.
In addition to all video applications, this feature applies to platinum users or specified video
applications.

Copyright © Huawei
Implementation
For details, seeRadio-Aware Video Precedence Feature Parameter Descriptionin RAN feature
documentation.

This feature preferentially schedules video services. When video user CQIs deteriorate,
cell throughput decreases. The following table describes the impact of this feature on cell
throughput.
Table 1.1 Impact on cell throughput

Scenario Video Bit Rate Decrease in Cell
Throughput
There are 18 web users and 250 kbit/s About 10%

2 video users (average CQI
is 15) in a cell. 500 kbit/s About 20%
Cell throughput decreases more dramatically if there are more than 2 video users in the
cell or the average CQI of video users is lower than 15.
Cell throughput decreases more moderately if there are less than 2 video users in the cell
or the average CQI of video users is higher than 15.
When the average CQI of a video user is less than or equal toVIDEOCQITHD, video
precedence will not be performed on this user and the impact on cell throughput can be
mitigated. The larger the parameter value, the less the impact on cell throughput.
This feature affects both user experience and Iub transmission bandwidth:
− Impact on service experience
This feature preferentially schedules video services and therefore affects the
experience of other users. However, the GBR of all users can be guaranteed.
− Transmission bandwidth
Information about video services must be transmitted over the Iub interface, which
consumes an extra of y 1kbit/s to 15 kbit/s transmission bandwidth.
Impact on NEs
 Intra-RAT NEs
 Inter-RAT NEs
UE: This feature has no special requirements for the UE.
CN: This feature has no special requirements for the CN.
Impact on Hardware
 RNC hardware
BSC6900: The NIUa board must be installed.

Copyright © Huawei
BSC6910: The ENIUa board must be installed.

 NodeB hardware
For the BTS3900, BTS3900A, BTS3900C, BTS3900L, BTS3900AL, and DBS3900, the
WBBPb, WBBPd, WBBPf, and UBBPd boards support this feature, whereas the WBBPa
board does not.

This feature uses private FP control frames on the Iub user plane to transmit video service
information between the RNC and NodeB. The type of private FP control frames is 250.

Control Item
WRFD-171210 Radio-Aware Radio-Aware BSC6900 Video Traffic

Video Video BSC6910 for RNC
Precedence Precedence (Per
Kbps)

The following MML commands have been added on the RNC side to accommodate this
feature.
Chang MML Command NE Description
e Type
New ADD UAPPPROTID BSC690 These commands are used to

MOD UAPPPROTID 0 configure protocol IDs.
RMV UAPPPROTID BSC691
0
LST UAPPPROTID
The following parameters have been introduced to accommodate this feature.

Chang Parameter ID MML NE Description
e Type Command
New VideoStrStartDel SET BSC6900 Target initial buffer delay

ayTar UUPCTRLS BSC6910 for video streaming
WITCH services
LST
UUPCTRLS
WITCH
New VideoPriWithPro SET BSC6900 Whether the Radio-Aware
tIDSwitch UUPCTRLS BSC6910 Video Precedence feature

Copyright © Huawei
Chang Parameter ID MML NE Description

e Type Command
WITCH applies only to the video

LST applications that use a
UUPCTRLS specific protocol ID
WITCH
New CellConnAlgoSw ADD BSC6900 Switch controlling the
itch2:RADIO_A UCELLCON BSC6910 Radio-Aware Video
WARE_VIDEO_ NALGOPAR Precedence feature
PRE_SWITCH MOD
UCELLCON
NALGOPAR
A
RMVUCELL
CONNALGO
PARA
New VideoPriUserSel SET BSC6900 User selection for Radio-
URRCTRLS BSC6910 Aware Video Precedence
WITCH
LST
URRCTRLS
WITCH
New VIDEOCQITHD SET NodeB CQI threshold that must be
ULOCELLM guaranteed for video
ACHSPARA services
LST
ULOCELLM
ACHSPARA

Type Subset
New VS.HSDPA.V HSDPA2.LO NodeB Number of HSDPA Video Users

ideoUserNum CELL for Cell
.Mean
New VS.HSDPA.P HSDPA2.LO NodeB Number of Prioritized HSDPA
rioritizedVide CELL Video Service Users for Cell
oUserNum.M
ean
New VS.RadioAw TRAFF.LOA BSC690 Traffic of Video Services based
aredVideo.Th D.PLMN.RN 0 on RAN-Initiated Service
ruput.PLMN. C BSC691 Awareness for RNC (per
RNC 0 Operator)

Copyright © Huawei

Type Subset
New VS.RadioAw TRAFF.LOA BSC690 Traffic of Video Services based

aredVideo.Th D.RNC 0 on RAN-Initiated Service
ruput.RNC BSC691 Awareness for RNC
0
New VS.Video.Init VIDEO.CEL BSC690 Total Initial Buffering Delay of
Buf.TotalDela L 0 Video Services for Cell
y BSC691
0
New VS.Video.Init VIDEO.CEL BSC690 Total Initial Buffering Delay of
Buf.TotalDela L 0 Video Services for Platinum
y.Platinum BSC691 Users for Cell
0
New VS.Video.Init VIDEO.CEL BSC690 Number of Times the Initial
Buf.Succ L 0 Buffering of Video Services Is
BSC691 Successful for Cell
0
New VS.Video.Init VIDEO.CEL BSC690 Number of Times the Initial
Buf.Succ.Plat L 0 Buffering of Video Services Is
inum BSC691 Successful for Platinum Users
0 for Cell
New VS.Video.Pla VIDEO.CEL BSC690 Number of Video Playbacks for

y.Num L 0 Cell
BSC691
0
New VS.Video.Pla VIDEO.CEL BSC690 Number of Video Playbacks for
y.Num.Platin L 0 Platinum Users for Cell
um BSC691
0
New VS.Video.Re VIDEO.CEL BSC690 Number of Video Playbacks
BufPlay.Num L 0 With Stalls for Cell
BSC691
0
New VS.Video.Re VIDEO.CEL BSC690 Number of Video Playbacks with
BufPlay.Num L 0 Stalls for Platinum Users for Cell
.Platinum BSC691
0

None

Copyright © Huawei

Related Operations
For details, see chapter "Engineering Guidelines" inRadio-Aware Video Precedence Feature
Parameter Descriptionin RAN feature documentation.

IR-RAN17.1-032
Feature ID
WRFD-171210
6.3.1.1.11 WRFD-171221 NodeB Supporting IPsec Redirection
Description
This feature supports deploying the IPsec redirection function on the network. When the
IKEv2 redirection function is enabled for the NodeB and SeGW, the SeGW decides whether
to continue to provide services for the NodeB or initiate a redirection to a new SeGW
according to the redirection policy. If the NodeB receives a redirection packet from the
SeGW, the NodeB initiates IKE negotiation with a new SeGW and establishes a new IPsec
tunnel.
This feature allows redirecting a NodeB from the serving security gateway to the target one if
the load decision conditions are met or if maintenance is required, so as to improve IPsec
tunnel reliability.
This feature enables a NodeB to implement IKE negotiation with different SeGWs using the
same IKE configuration and to establish an IPsec tunnel, thereby simplifying SeGW network
configuration and reducing network configuration complexity. This feature has the following
characteristics:
 Compatible with the RFC 5685 protocol, the NodeB can only serve as an initiator.
 Supports initiating a redirection during the IKEv2 Initial exchange phase and
IKE_AUTH exchange phase for IKEv2.
 During the redirection, the NodeB supports indicating the target SeGW only through
IPV4.
 Supports setting the maximum number of redirections within five minutes so as to
eliminate the possibility that the NodeB cannot provide services normally because it is
repeatedly redirected due to a configuration error or a malicious attack.
 IPsec redirection is not supported when an IPsec link is established using DHCP.
Implementation
For details, see the change history ofIPsec Feature Parameter Descriptionin RAN Feature
Documentation.

Copyright © Huawei

No impact.
The IPsec redirection feature allows the SeGW connected to a base station to send a
redirection request to the base station based on whether the SeGW is overloaded or
faulty. After receiving the redirection request, the base station initiates an IKE
negotiation with a new SeGW. IPsec redirection helps balance load between SeGWs and
improve IPsec tunnel reliability. If the base station is redirected to the new SeGW,
communication between the base station and the source SeGW is affected: Voice calls
are dropped and data transmission rates are extremely low.
Impact on NEs
To support this feature, the SeGWs must meet the following requirements:
 The SeGWs must support the RFC 5685 IKEv2 Redirect function.
 The SeGWs can generate internal dynamic routing based on IPsec SAs.
 The initial SeGW can establish IPsec tunnels with the base station so that base station
deployment by plug and play (PnP) can be used.
Impact on Hardware
The NodeB must be configured with the UMPT, UMDU, or UTRPc board to support this
feature.

The following three fields have been added to IKE negotiation messages between the eNodeB
and the SeGW to accommodate this feature:
 Redirection capability (REDIRECT_SUPPORT)
 Redirection request (REDIRECT, New_GW_ID)
 Redirection information (REDIRECTED_FROM, Initial_IP_R)
For details, see RFC 5685.

An NodeB-level license control item has been added for this feature.
Control Item
WRFD-171221 NodeB NodeB NodeB per NodeB

Supporting supporting
IPsec IPSec
Redirection redirection (per
NodeB)

Copyright © Huawei

The following MML commands have been modified to accommodate this feature.
Change MML Command NE Description
Type
Modified DSP IKEMSGSTAT NodeB Added the following check result

parameters:
 Number of Successful IKEv2
Redirects
 Number of Failures in IKEv2
Redirects
 Number of Denied IKEv2 Redirects
Modified DSP DIAGNOSE NodeB Added the peer SeGW IP address to the
IKE SA negotiation result in this
command.
Parameters in the new MML commands are not listed in the following table.
Type ID Command
New REDIRECT ADD IKEPEER NodeB Set this parameter toON if the
SW RMV IKEPEER NodeB needs to support IPsec
redirection. Otherwise, set this
MOD IKEPEER parameter to OFF.
LST IKEPEER

N/A
The following alarms and events have been added or modified to accommodate this
feature.
Type
New EVT-25956 IKE Handover NodeB This event is generated when the
Event following conditions are met: The
IKEv2 redirect function is enabled
for an IKE peer, the IKE SA
corresponding to this IKE peer
exists, and redirections occur.
Modifie ALM-25891 IKE NodeB If IPsec redirection is enabled, this
d Negotiation Failure alarm is reported when an IKE

Copyright © Huawei

Type
negotiation with the peer end fails.

Modifie ALM-25950 Base Station NodeB This alarm is reported when a DOS
d Being Attacked attack occurs due to IPsec
redirection.

WRFD-140209 NodeB Integrated IPSec
No impact.
No impact.
Related Operations
For details, see "Deployment of Base Station Supporting IPsec Redirection" in engineering
guidelines ofIPsec Feature Parameter Descriptionin RAN Feature Documentation.

IR-SRAN10.1-Sec-01
Feature ID
WRFD-171221
6.3.1.1.12 WRFD-171220 NodeB Supporting Multi-operator PKI
Description
This feature applies to RAN Sharing scenarios so as to securely isolate the services of each
operator. After this feature is enabled, if each operator deploys its own PKI server, the NodeB
can load and manage the device certificates issued by multiple PKI servers. The NodeB
establishes an independent security tunnel for each operator based on their respective device
certificates, so as to achieve the secure isolation of each operator's services.
The NodeB supports loading and managing device certificates and CRL files issued by
multiple PKI servers. The following actions are involved:
 Certificate application: Each operator uses a Huawei-issued device certificate to apply to
its own PKI server for a certificate, and the NodeB establishes an independent IPsec
tunnel for each operator. As shown inFigure 6-4, operator A's PKI server issues
certificate A to the NodeB, and operator B's PKI server issues certificate B to the NodeB.
Then, the NodeB establishes IPsec tunnels A and B for operators A and B, respectively.
 Certificate update: Similarly, each operator's PKI server issues an updated certificate.
 Certificate revocation: Similarly, each operator's PKI server can revoke a certificate.

Copyright © Huawei
 CRL file management: Similarly, the NodeB can obtain the CRL file on each server. The
NodeB then independently manages each certificate file.
To securely isolate the services of operators, the NodeB can use their respective device
certificates to establish a dedicated IPsec tunnel for each operator.
Figure 1.1 NodeB supporting Multi-operator PKI
Implementation
For details, seeBase Station Supporting Multi-operator PKI Feature Parameter Descriptionin

No impact.
The duration of base station deployment is prolonged by 10s due to certificate
application for each operator.
Impact on NEs
This feature is implemented on the base station and requires support from the PKI server. This
feature takes effect only when the base station is configured with multiple PKIs.

Copyright © Huawei
Impact on Hardware
In multi-PKI scenarios, a base station supports a maximum of six operators' PKI servers.

No impact.

Control Item
WRFD-171220 NodeB NodeB NodeB per NodeB

Supporting supporting
Multi-operator Multi-operator
PKI PKI (per
NodeB)

The following MML command has been added to accommodate this feature.
Type
New MOD CERTMK NodeB Use this command to modify the

binding relationships between a
device certificate and a CA.
Parameters in the new MML command are not listed in the following table.
When theREQ DEVCERT command is executed to trigger a CMPv2-based certificate application, the
preconfigured Huawei-issued device certificate is used for certificate application by default, which saves
the trouble of running the MOD APPCERTcommand to change a configured device certificate to the
preconfigured Huawei-issued device certificate.
Chan Parameter ID MML NE Description
ge Command
Type
New CERTREQSW ADD CA NodeB Indicates the certificate request

RMV CA template used by the base station
to apply for a certificate from the
MOD CA CA. When this parameter is set
LST CA toDEFAULT, the certificate
request template configured in
the MOD CERTREQ command
is used. When this parameter is

Copyright © Huawei

ge Command
Type
set to USERDEFINE, a
customized certificate request
template is used.
New CERTREQSI ADD CA NodeB Indicates the signature algorithm
GNALG RMV CA for the certificate request file.
The signature algorithm can be
MOD CA SHA1, MD5, or SHA256.
LST CA SHA256 is recommended.
New CERTSOURC ADD IKEPEER NodeB Indicates the source of the
E RMV IKEPEER certificate used for IKE
negotiation in multi-PKI
MOD IKEPEER scenarios.
LST IKEPEER When this parameter is set
DSP IKEPEER toAPPCERT, the certificate
configured by the APPCERT
MO is used. When this
parameter is set to CERTMK,
the certificate configured by the
CERTMKMO is used.
The default value isAPPCERT.
New CERTNAME ADD IKEPEER NodeB Indicates the name of the
RMV IKEPEER certificate file used in the IKE
negotiation in multi-PKI
MOD IKEPEER scenarios. This parameter is valid
LST IKEPEER only whenCERTSOURCE is set
DSP IKEPEER to CERTMK.
New CERTREQPO CRE NodeB Indicates the policy used in the

LICY CERTREQFILE certificate request configuration
information in multi-PKI
scenarios.
When this parameter is set
toDEFAULT, the default
certificate request template
configured in MOD CERTREQ
is used. When this parameter is
set to CACERTREQ, the
certificate request template
specified by the CA is used.
The default value isDEFAULT.
New CANAME CRE NodeB Indicates the name of the CA
CERTREQFILE which specifies the certificate
request template in multi-PKI
scenarios. This parameter is valid
only whenCERTREQPOLICY is
set to CACERTREQ.

Copyright © Huawei

No impact.
CMP message tracing can be performed for multiple CAs on the LMT.

WRFD-050402 IP Transmission Introduction on Iub Interface
None
None
Related Operations
For details, see Engineering Guidelines inBase Station Supporting Multi-operator PKI
Feature Parameter Descriptionin RAN feature documentation.

IR-SRAN10.1-Sec-07
Feature ID
WRFD-171220
6.3.1.1.13 NodeB CHR Optimization
Description
Event block-based call history record (CHR) subscription now replaces level-based CHR
subscription to help provide more detailed NodeB CHRs. Additionally, NodeBs support
periodic CHR collection, facilitating data collection with finer granularity.
Implementation
 MML commands support event block-based CHR subscription.
 The network information collector (NIC) allows CHR subscription in batches.
 Automatic uploading is now enabled for CHR files in *.prd format. Specifically, CHR
files in the *.prd format are generated every five seconds for certain event blocks. These
files are packaged by NodeBs every five minutes and then uploaded to a specific server.
For other event blocks, CHR files are generated in the same way as in earlier versions.

 System capacity
None
 Network performance

Copyright © Huawei
None
Impact on NEs
This feature is implemented on the NodeB and U2000.
Impact on Hardware
The WBBPb board or a later version must be configured to support this feature.

New southbound interfaces to the U2000 are introduced, and some of them are modified.

None
The following table lists the changes to MML commands.
Change Type Command NE Description
Modified SET DBS3900 The command is

NODEBCHRLEVE used to specify event
L blocks in CHR
subscription.
New DSP DBS3900 This command is
NODEBCHRLEVE used to query, in real
L time, the level of
details provided in
CHRs.
Modified SET ATULDSW DBS3900 This command is
used to enable or
disable automatic
uploading for CHR
files.

None
None

None
None

Copyright © Huawei
None
Related Operations
None

IR-RAN17.0-017
Feature ID
IntFD-170002
6.3.1.1.14 WRFD-170108 Hitless Cell Rehoming
Description
To distribute the local cells on the NodeB appropriately to baseband boards and make full use
of hardware resources, reconfiguring cells between boards is required.
Before this feature is introduced, running the MML command STR REALLOCLOCELL
manually is required, which interrupts the services on specific or all cells.
After this feature is introduced, the MML command STR RESHUFFLELOCELL received by
the NodeB specifies the target cell and board for reconfiguration. The NodeB uses internal
link replication to re-deploy resources. Therefore, the UE will not experience call drops or
sense internal NE adjustments. The re-deployment is complete within five seconds.
Implementation
For details, see Hitless Cell Rehoming Feature Parameter Description.

 System capacity
No impact.
The cell rehoming procedure (which lasts within 5s) has the following impacts on
services:
− New users cannot be admitted to the cell to be rehomed.
− Online UEs do not experience call drops but they cannot initiate new Iub signaling
procedures. A small number of messages such as RL-SETUP-FAIL, RL-RECFG-
FAIL, and RL-ADD-FAIL may be traced over the Iub interface.
− Services of other cells are not affected.
During cell rehoming, packet loss and retransmission occur at the physical layer, which
has the following impacts:
− The uplink received total wideband power (RTWP) of the local cell increases
instantaneously and then returns to normal after cell rehoming.
− The data rates of UEs established on the local cell are reduced and then return to
normal after cell rehoming.

Copyright © Huawei
Impact on NEs
This feature is implemented on the NodeB and U2000.
Impact on Hardware
UBBPd board.
The BTS3902E, BTS3803E, and BTS3911E do not support this feature.
The WBBPa board does not support this feature, neither incoming nor outgoing cell
rehoming.

No impact.

An MML command has been added on the NodeB side to accommodate this feature, as
described in the following table.
Type
New STR RESHUFFLELOCELL NodeB This command is used to

specify the cell to be rehomed
and the target board to which
the cell is rehomed.

No impact.
No impact.

None
None
None

Copyright © Huawei
Related Operations
For details, see "Engineering Guidelines" in Hitless Cell Rehoming Feature Parameter
Description.

IR-RAN17.0-020
Feature ID
WRFD-170108
6.3.1.1.15 WRFD-170106 Iub Self-planning
Description
The Iub Self-planning feature applies to newly-deployed UMTS macro base stations. This
feature enables the NodeB to automatically establish control-plane Iub links with the RNC
and therefore simplifies the data planning and configuration on the control plane of the RNC.
With this feature, the control plane on the Iub interface uses self-configuration in end point
mode on the RNC side when the Iub interface uses IP transmission. In this case, only the
SCTP server data needs to be configured on the RNC, and SCTP link data and upper-layer
signaling data associated with the SCTP link do not need to be configured on the RNC.
During deployment, the NodeB obtains the IP address and port number of the SCTP server
either from the U2000 or by manual configuration and then initiates an SCTP negotiation
procedure. After an SCTP link is established, the NodeB sends its identity information to the
SCTP server. The SCTP server parses this information and then maps the SCTP link onto the
upper-layer signaling.
Implementation
For details, see Interface Self-planning Feature Parameter Description in the RAN feature
documentation package.

 System capacity
No impact.
This feature has the following impact on network performance:
− When a NodeB accesses the network and tries to establish a signaling link for the first
time, establishing a signaling link in end point mode takes about 5s to 10s more than
that in link mode. However, time required for establishing a signaling link in end
point mode is the same as that in link mode after a NodeB is reset.
− After a signaling link is automatically established, if the local SCTP IP address or
port number is modified on the NodeB, the system automatically modifies the
established signaling link accordingly.

Copyright © Huawei
Impact on NEs
Impact on Hardware
No impact.

This feature has the following impact on the NBAP RESET REQ message sent by the NodeB
to the RNC.
 Without this feature:
The IUB NODEB CHOSEN, IUB COMMUNIC CONTEXT CHOSEN, and IUB
COMMUNIC CTRL PORT CHOSEN information elements (IEs) are sent over the
NodeB control port (NCP) together.
 With this feature:
The IUB NODEB CHOSEN and IUB COMMUNIC CONTEXT CHOSEN IEs are sent
over the NCP together. The IUB COMMUNIC CTRL PORT CHOSEN IE is sent over
the communication control port (CCP).
This feature does not affect the NBAP RESET REQ message sent by the RNC to the NodeB.

The MML commands in the following table have been introduced on the RNC side to
accommodate this feature.
Change Command NE Description
Type
New ADD SCTPSRV BSC6900 Use this command to add a service

BSC6910 listening port to the SCTP server for
signaling plane Self-planning.
New MOD SCTPSRV BSC6900 Use this command to modify
BSC6910 information about a service listening
port on an SCTP server for
New RMV SCTPSRV BSC6900 Use this command to remove a
BSC6910 service listening port on an SCTP
server for signaling plane Self-
planning.
New LST SCTPSRV BSC6900 Use this command to query
BSC6910 information about a service listening
port on an SCTP server for
New ADD SCTPPROF BSC6900 Use this command to add an SCTP

Copyright © Huawei
Change Command NE Description

Type
BSC6910 profile.
New MOD SCTPPROF BSC6900 Use this command to modify
BSC6910 information in an SCTP profile.
New RMV SCTPPROF BSC6900 Use this command to remove an

BSC6910 SCTP profile.
New LST SCTPPROF BSC6900 Use this command to query

BSC6910 information in an SCTP profile.
New SET BSC6900 Use this command to configure the

SCTPSRVCTRL BSC6910 binding relationship between a
signaling subsystem and a link to an
SCTP server for signaling plane
Self-planning.
New DSP BSC6900 Use this command to query the
SCTPSRVFILTER BSC6910 blacklist of an SCTP server for
signaling Self-planning.
New CLR BSC6900 Use this command to remove the
SCTPSRVFILTER BSC6910 blacklist configured for an SCTP
server for signaling plane Self-
planning.
Parameters in the new MML commands are not listed in the following table.
The following parameters have been introduced or modified on the RNC side to
Type ID Command
New SCTPSPAGI SET BSC690 Aging period for a listening

NGTIME TNSOFTPAR 0 association for signaling plane
A BSC691 Self-planning.
0
New SCTPSPPU SET BSC690 Penalty period for a listening
NISHTIME TNSOFTPAR 0 association for signaling plane
A BSC691 Self-planning. Within the penalty
0 period, the peer end cannot
reconnect to the server. If this
parameter is set to 0, the penalty
is not implemented.
New SCTPSPFIL SET BSC690 Blacklist period for a listening
TERTIME TNSOFTPAR 0 association for signaling plane
A BSC691 Self-planning. Within the
0 blacklist period, the peer end

Copyright © Huawei

Type ID Command
cannot reconnect to the server. If

this parameter is set to 0, the
blacklist filtering function is not
performed.
New SCTPSPUP SET BSC690 Threshold for the number of
THRD TNSOFTPAR 0 temporary associations that are
A BSC691 set up between a remote port and
0 the local SCTP listening port for
New SCTPSPFC SET BSC690 Threshold for signaling plane
THRD TNSOFTPAR 0 Self-planning flow control. The
A BSC691 number of admitted SCTP
0 packets over an SCTP listening
port on the signaling subsystem
every second cannot exceed this
threshold.
New SCTPSPPSF SET BSC690 Threshold for admitted abnormal
CTHRD TNSOFTPAR 0 packet flow control for signaling
A BSC691 plane Self-planning. The number
0 of admitted abnormal SCTP
packets over an SCTP listening
port on the signaling subsystem
every second cannot exceed this
threshold.
New SCTPSRVFI CLR BSC690 Index of an SCTP server filter
LTERINDE SCTPSRVFIL 0 table, which uniquely identifies a
X TER BSC691 cell in the SCTP server filter
0 table.
New SignalCreate ADD BSC690 NodeB signaling plane creation

Type UNODEB 0 type. If this parameter is set to
MOD BSC691 USER_CREATE, the NodeB
UNODEB 0 control plane is manually created
by the user. The NodeB control
LST plane includes the NCP, CCP,
UNODEB and SCTP links carrying the NCP
and CCP. If this parameter is set
to SYS_CREATE, the NodeB
control plane is automatically
created by the Iub Self-planning
feature.
New SpecifyLOC ADD BSC690 Whether to specify a local port
PNFlag SCTPLNK 0 when an SCTP link works as the
MOD BSC691 SCTP server. This parameter
SCTPLNK 0 does not need to be specified.
Modifie LOCPN ADD BSC690  Before the change:

d SCTPLNK 0 When the MODE parameter

Copyright © Huawei

Type ID Command
MOD BSC691 is set to CLIENT, this

SCTPLNK 0 parameter must be specified.
 After the change:
When the MODE parameter
is set to CLIENT and the
SpecifyLOCPNFlag
parameter is set to YES, this
parameter must be specified.
Modifie LNKT DSP BSC690 The value SCTPSRV is added
d INTERWK 0 for this parameter.
BSC691
0

No impact.
The following alarms have been introduced on the RNC side to accommodate this
feature.
Type Name
New ALM-22244 BSC6900 The RNC determines the NodeB

Configuration BSC6910 object by matching the base
Between Related NE station name reported by the
Dismatch NodeB over the Iub interface
with the base station name
configured on the RNC. This
alarm is reported when the base
station name matching fails.
This alarm is cleared 5 minutes
after the base station name
matching succeeds.
New ALM-22245 NodeB BSC6900 This alarm is reported when the
Signaling Plane BSC6910 SCTP link configurations
Creation Failure conflict with each other, NCP
and CCPs cannot be
automatically generated due to
insufficient SCTP links, or
CCPs cannot be automatically
generated due to insufficient
CCP resources.
This alarm is cleared 5 minutes
after the system automatically
generates NCP and CCPs.

Copyright © Huawei
The function of tracing SCTP based on SCTPSRVID and the peer IP address is added to
the LMT for this feature.

This feature requires that the Iub interface use IP transmission and therefore this feature
depends on the following features:
When the BSC6900 is used:
− WRFD-140208 Iub Transmission Resource Pool in RNC
When the BSC6910 is used:
− WRFD-150243 Iub IP Transmission Based on Dynamic Load Balancing
None
None
Related Operations
For details, see section "WRFD-170106 Iub Self-planning" in chapter "Engineering
Guidelines" of Interface Self-planning Feature Parameter Description.

IR-SRAN10-TRAN-20
Feature ID
WRFD-170108
6.3.1.1.16 WRFD-170201 Seamless Crystal Voice
Description
To improve the MOS in the soft handover area, a channel decoder is deployed on the RNC.
The RNC then performs a softer combination on multiple soft handover tributaries to ensure
the MOS of voice services.
This feature can greatly improve the MOS of voice services, including narrowband AMR and
WB AMR voice, in the soft handover area. AMR12.2k service is taken as an example.
According to the uplink link simulation results, when the BLER is greater than 0.2%, the
gains in MOS can exceed 0.2. Generally, if the BLER in the soft handover area is large, the
gains that this feature provides for the MOS are great.
Implementation
For details, see Seamless Crystal Voice Feature Parameter Description in the RAN feature
documentation package.

Copyright © Huawei

 System capacity
− After this feature is enabled, values of CPU-related counters for the DPUb and DPUe
boards in the BSC6900 or the GPU board in the BSC6910 increase by 0 to 5%.
This effect is obtained from tests in the smartphone traffic model. In the smartphone traffic model,
services performed by smartphones are characterized by frequent control-plane signaling interactions
and small-size packets in the user plane.
Counter Name Counter Description NE
VS.DSP.UsageAvg Mean DSP Usage in Period BSC6900

VS.SUBSYS.CPULOAD.MEA AR9725: Average Subsystem CPU Usage BSC6910
N of the Board
− After this feature is enabled, the consumed bandwidth over the Iub or Iur interface
increases. When the bandwidth over the Iub interface is insufficient, values of PS
service-related counters will decrease.
Counter Name Counter Description NE
VS.PS.BE.DCH.UL.SumTh Sum of Sampled Uplink BE BSC6900/BSC6910

roughput Throughput of UEs with PS
Services over DCHs
VS.HSUPA.MeanChThroug Mean Uplink Throughput of BSC6900/BSC6910
hput single HSUPA MAC-d Flow
for Cell
VS.HSUPA.MeanBitRate.W Average throughput of NodeB
ithData HSUPA users in a cell when
data is transmitted
 In a poor-quality network, this feature increases the average MOS in soft handover areas
by 0.2 to 1. In a high-quality network, this feature increases the proportion of high MOS
in soft handover areas by about 20%.
 According to ITU-T P.862.1 (the standard for evaluating the MOS), a network where the average
MOS is less than 3.8 is a poor-quality network, a network where the average MOS is greater than or
equal to 3.8 is a high-quality network, and the proportion of high MOS is the proportion of MOS
that is greater than 4.
 According to ITU-T P.863.1 (the standard for evaluating the MOS), a network where the average
MOS is less than 2.8 is a poor-quality network, a network where the average MOS is greater than or
equal to 2.8 is a high-quality network, and the proportion of high MOS is the proportion of MOS
that is greater than 3.
 The MOS can be obtained by performing drive tests or checking the values of counters related to
enhanced voice quality indicator (EVQI).
 This feature increases the end-to-end delay for voice services by less than 30 ms, but
does not affect network KPIs such as the call drop rate and access success rate.

Copyright © Huawei
Impact on NEs
Impact on Hardware
 The RNC must be configured with the DEUa board.
 The 3900 series macro NodeBs must be configured with the WBBPb, WBBPd, WBBPf,
or UBBPd board.

This feature affects the Iub and Iur interfaces in the following ways:
 The Seamless Crystal Voice QE Threshold is added to the in-band signaling frames in the
downlink.
 Pre-decoding information is added to the data frames over the DCH in the uplink.

The following table lists the license control item added for this feature.
Description
WRFD-170201 Seamless Seamless BSC6900 Erlang

Crystal Voice Crystal Voice BSC6910

The following parameters have been introduced or modified on the RNC side to
Type ID Command
New NodeBAlgoE ADD BSC6900 Whether to enable the NodeB-

nhSwitch: UNODEBAL BSC6910 level seamless crystal voice
NODEB_SE GOPARA feature.
AMLESS_C MOD When this switch is set to on, the
RYSTAL_V UNODEBAL NodeB-level seamless crystal
OICE_SWIT GOPARA voice feature is enabled. When
CH this switch is set to off, the
NodeB-level seamless crystal
voice feature is disabled.
New IurSMLESS ADD BSC6900 Whether the Iur interface
CrstVoiceSup UNRNC BSC6910 supports the seamless crystal
pInd MOD voice feature.
UNRNC When this switch is set to off, the
Iur interface does not support the
seamless crystal voice feature.
That is, the radio links (RLs)

Copyright © Huawei

Type ID Command
added on the Iur interface during

a soft handover do not support
the seamless crystal voice
feature. When this switch is set
to on, the Iur interface supports
the seamless crystal voice
feature. That is, the RLs added
on the Iur interface during a soft
handover support the seamless
crystal voice feature.
New SMLESSCrst SET BSC6900 QE threshold of RLs that
VoiceQEThld UUPCTRLS BSC6910 participate in seamless crystal
WITCH voice processing.
When the QE of a soft-handover
RL is greater than or equal to this
threshold, the RL does not
participate in seamless crystal
voice processing. When the QE
of a soft-handover RL is less
than this threshold, the RL
participates in seamless crystal
voice processing.
New AMRPacketL SET BSC6900 Packet loss rate threshold for
ossRatioThld UDPUCFGD BSC6910 determining whether the uplink
ATA of a single AMR service is
congested.
This parameter is used together
with the
AMRPacketLossNumThld
parameter to determine whether
a single AMR service is
congested. When the packet loss
rate of a single AMR service is
greater than the value of
AMRPacketLossRatioThld and
the number of discarded packets
of the single AMR service is
AMRPacketLossNumThld, the
single AMR service is congested.
AMRPacketLossNumThld is
set by the SET
UDPUCFGDATA command.
New AMRPacketL SET BSC6900 Packet loss number threshold for
ossNumThld UDPUCFGD BSC6910 determining whether the uplink
ATA of a single AMR service is
congested.
This parameter is used together
with the

Copyright © Huawei

Type ID Command
AMRPacketLossRatioThld
parameter to determine whether
a single AMR service is
congested. When the packet loss
rate of a single AMR service is
AMRPacketLossRatioThld and
the number of discarded packets
of the single AMR service is
AMRPacketLossNumThld, the
single AMR service is congested.
AMRPacketLossRatioThld is
set by the SET
UDPUCFGDATA command.
New AMRTnlLate SET BSC6900 Delay variation threshold for
ncyThld UDPUCFGD BSC6910 AMR services.
ATA When the delay variation of an
AMR service is greater than the
value of AMRTnlLatencyThld,
the RNC determines that the
transport layer of the AMR
service is congested.
New SMLESSCrst SET BSC6900 Load sharing threshold of inter-
VoiceSharing UDPUCFGD BSC6910 subrack crystal voice processing.
Thd ATA When the crystal voice
processing resource consumption
in a subrack exceeds this
threshold, inter-subrack crystal
voice processing load sharing is
triggered.
New PROCESSS SET BSC6900 Whether to enable the RNC-level
WITCH5: URRCTRLS BSC6910 seamless crystal voice feature.
SEAMLESS WITCH When this switch is set to on, the
_CRYSTAL_ RNC-level seamless crystal
VOICE_SWI voice feature is enabled. When
TCH this switch is set to off, the RNC-
level seamless crystal voice
feature is disabled.
Modifie BRDTYPE ADD BRD BSC6900 Type of the board.
d BSC6910 An enumerated value DEUa is
added for this parameter.
Modifie LGCAPPTY ADD BRD BSC6900 Logical function type of the
d PE LOD BRD board.
DSP PATCH An enumerated value UUEP is

Copyright © Huawei

Type ID Command
RMV PATCH
CON PATCH
DEA PATCH
ACT PATCH
LST PATCH
LOD PATCH
Modifie LGCAPPTY CON PATCH BSC6910 Logical function type of the
d PE DEA PATCH board.
LOD PATCH An enumerated value UUEP is
DSP PATCH
ADD CPU
Modifie BT LOD BRD BSC6900 Type of the board.
d DSP PATCH An enumerated value DEUa is
RMV PATCH added for this parameter.
CON PATCH
DEA PATCH
ACT PATCH
LST PATCH
LOD PATCH
Modifie BT CON PATCH BSC6910 Type of the board.
d DEA PATCH An enumerated value DEUa is
DSP PATCH added for this parameter.
LOD PATCH
Modifie BRDCLASS ADD BRD BSC6900 Board class.
d BSC6910 An enumerated value DEU is
Modifie BRDCLASS SET BSC6900 Board class.
d CPUTHD BSC6910 An enumerated value DEU is
LST added for this parameter.
CPUTHD
SET
FCCOMMPA
RA
Modifie BRDCLASS SET BSC6910 Board class.
d FCCOMMPA An enumerated value DEU is
RA added for this parameter.
Modifie SUBSYSTY ADD BSC6910 Type of a subsystem.
d PE SUBSYS An enumerated value UUEP is

Copyright © Huawei

Type ID Command
LST SUBSYS added for this parameter.

Modifie SUBSYSTY DSP SUBSYS BSC6910 An enumerated value UUEP is
d PE added for this parameter.

The following counters have been introduced on the RNC side to accommodate this
feature.
Type Name Subset
New VS.AMR.SM TRAFF.LO BSC6900 Equivalent Erlang Consumed by

LESSCrstVoi AD.RNC BSC6910 AMR Voice Services Using the
ce.Erlang.Equ Seamless Crystal Voice Feature
iv.RNC for RNC
New VS.AMR.SM TRAFF.LO BSC6900 Maximum Equivalent Erlang
LESSCrstVoi AD.RNC BSC6910 Consumed by AMR Voice
ce.MaxErlang Services Using the Seamless
.Equiv.RNC Crystal Voice Feature for RNC
New VS.AMR.SM TRAFF.LO BSC6900 Equivalent Erlang Consumed by
LESSCrstVoi AD.PLMN. BSC6910 AMR Voice Services Using the
ce.Erlang.Equ RNC Seamless Crystal Voice Feature
iv.PLMN.RN for RNC (per Operator)
C
New VS.AMR.SM TRAFF.LO BSC6900 Maximum Equivalent Erlang
LESSCrstVoi AD.PLMN. BSC6910 Consumed by AMR Voice
ce.MaxErlang RNC Services Using the Seamless
.Equiv.PLMN Crystal Voice Feature for RNC
.RNC (per Operator)
New VS.SHO.EV EVQI.CELL BSC6900 Total Uplink EVQI of AMR-WB
QI.AMRWB. BSC6910 Services During Soft Handovers
UL.TotalValu
e
New VS.SHO.EV EVQI.CELL BSC6900 Number of Times the Uplink
QI.AMRWB. BSC6910 EVQI of AMR-WB Services
UL.Excellent. During Soft Handovers Is
Num EXCELLENT
UL.Good.Nu During Soft Handovers Is
m GOOD
UL.Accept.N During Soft Handovers Is

Copyright © Huawei

Type Name Subset
um ACCEPT
UL.Poor.Num During Soft Handovers Is POOR
UL.Bad.Num During Soft Handovers Is BAD
New VS.SHO.EV EVQI.CELL BSC6900 Total Uplink EVQI of AMR-NB
QI.AMRNB. BSC6910 Services During Soft Handovers
UL.TotalValu
e
QI.AMRNB. BSC6910 EVQI of AMR-NB Services
UL.Excellent. During Soft Handovers Is
Num EXCELLENT
UL.Good.Nu During Soft Handovers Is
m GOOD
UL.Accept.N During Soft Handovers Is
um ACCEPT
UL.Poor.Num During Soft Handovers Is POOR
UL.Bad.Num During Soft Handovers Is BAD
New VS.DEU.DSP DEUDSP BSC6900 Maximum DEU DSP Usage
.UsagePeak
New VS.DEU.DSP DEUDSP BSC6900 Average DEU DSP Usage
.UsageAvg
New VS.DEU.CP DEU BSC6900 Maximum CPU Usage of the
ULOAD.MA DEU
X
New VS.DEU.CP DEU BSC6900 Average CPU Usage of the DEU
ULOAD.ME
AN

Copyright © Huawei
The following alarms or events have been introduced or modified to accommodate this
feature.
Change Alarm/Event Name NE Description
Type
New ALM-22512 Insufficient BSC6900 None

Resources for Processing BSC6910
Enhanced Data
Modifie ALM-20258 Number of BSC6900 Value Seamless Crystal Voice
d Resources Used Reaching traffic over capacity is added for
Alarm Threshold Specified the Alarm Resource Item
by License parameter.
d Resources Used Exceeding traffic over capacity is added for
d Resources Used Reaching traffic over capacity is added for
d Resources Used Exceeding traffic over capacity is added for
Modifie ALM-20241 Board BSC6900 Value DEUa is added for the
d Unavailable Board Name parameter.
d Unavailable Board Name parameter.
d Subsystem Unavailable Board Name parameter.
Modifie EVT-22831 Board BSC6900 Value DEUa is added for the
d Subsystem Start Board Name parameter.
Modifie EVT-22831 Board BSC6910 Value DEUa is added for the
d Subsystem Start Board Name parameter.
Modifie EVT-22831 Board BSC6910 Value UUEP is added for the
d Subsystem Start Subsystem Type parameter.
d Blocked Board Name parameter.
d Blocked Board Name parameter.
Modifie EVT-22839 Board Self- BSC6900 Value DEUa is added for the
d Recovery Board Name parameter.
Modifie EVT-22839 Board Self- BSC6910 Value DEUa is added for the
d Recovery Board Name parameter.

Copyright © Huawei
Change Alarm/Event Name NE Description

Type
Modifie ALM-20242 Board BSC6910 Value UUEP is added for the

d Subsystem Unavailable Subsystem Type parameter.
Modifie ALM-20282 Subsystem BSC6910 Value UUEP is added for the
d Blocked Subsystem Type parameter.

None
None
None
Related Operations
For details, see chapter 7 "Engineering Guidelines" in Seamless Crystal Voice Feature
Parameter Description in the RAN feature documentation package.

IR-RAN17.0-001
Feature ID
WRFD-170201
6.3.1.1.17 WRFD-170203 HSUPA Scheduler Pool
Description
Each WBBP board has an HSUPA scheduler. If this feature is not supported, the same cell
must be served by the same scheduler. The multiple cells in the same scheduler can share
scheduler resources, but cannot utilize resources between different schedulers.
This feature enables the distributed deployment of one HSUPA cell across different HSUPA
schedulers. As shown in the following figure, in addition to the primary scheduling entity, a
cell can have a secondary scheduling entity. In this way, the UEs in the cell can be
dynamically distributed to two schedulers. To ensure optimal scheduling efficiency, HSDPA
and HSUPA schedulers must be bound to the same board. Therefore, the HSUPA Scheduler
Pool feature is dependent on the HSDPA Scheduler Pool feature.

Copyright © Huawei
After this feature is applied, the resource usage is balanced between different schedulers, so
that the overall utilization rate of HSUPA schedulers is improved.
Implementation
See HSUPA Scheduler Pool Feature Parameter Description.

 System capacity
This feature enables lightly loaded baseband processing boards to share the loads of
heavily loaded baseband processing boards and therefore improves the overall utilization
rate of HSUPA schedulers.
No impact.
Impact on NEs
Impact on Hardware
Only the 3900 series (excluding BTS3902E) base stations support this feature, and
WBBPa/WBBPb boards do not support this feature.
The BBU3910A does not support this feature.

No impact.


Copyright © Huawei

Feature ID Feature Name License Control NE Sales
Item Unit
WRFD-170205 HSUPA Scheduler HSUPA Scheduler NodeB NodeB

Pool Pool(per NodeB)

Type ID Command
New HsupaSch SET NodeB This new switch enables or

PoolSw NODEBALGP disables the HSUPA Scheduler
ARA Pool feature.

When the HSUPA Scheduler Pool feature is enabled, all baseband processing boards
supporting this feature form a resource pool. Each board in the pool records the ratio of
the number of online HSUPA UEs in the pool to the number of HSUPA UEs supported
by the pool.
Change Counter Name Measure NE Description
Type ment
Unit
New VS.BOARD.UsedHsup TRAFFIC. NodeB Average ratio of HSUPA

aUserRatio.Mean BOARD users on a board
New VS.BOARD.UsedHsup TRAFFIC. NodeB Maximum ratio of
aUserRatio.Max BOARD HSUPA users on a board

ALM-26811 Configured Capacity Limit Exceeding Licensed Limit is reported when the
HSUPA Scheduler Pool feature is enabled but the license file is not activated.

WRFD-150242 HSDPA Scheduler Pool
None
None

Copyright © Huawei
Related Operations
See the "Engineering Guidelines" chapter in HSUPA Scheduler Pool Feature Parameter
Description.

IR-RAN17.0-006
Feature ID
WRFD-170203
6.3.1.1.18 WRFD-170102 Instant Macro Diversity
Description
After receiving a period- or event-based inter-frequency measurement report, the RNC
determines whether a UE meets the trigger conditions of this feature based on the information
about the target cell and signal quality carried in the report. The difference between this
feature and conventional inter-frequency hard handover is the number of target cells for
handover. With this feature, the handover is intended for multiple target cells. With
conventional inter-frequency hard handover, the handover is intended for only one target cell.
Figure 6-5 and Figure 6-6 show the difference between this feature and conventional inter-
frequency hard handover.
Figure 1.1 Process of conventional inter-frequency hard handover

Copyright © Huawei
Figure 1.2 Process of this feature
This feature is not supported in downlink SRB OVER HSDPA scenarios.
Implementation
For details, see Instant Macro Diversity Feature Parameter Description in the RAN feature
documentation.

 System capacity
RAB setup requests for inter-frequency hard handovers only occupy a small proportion
(less than 10%) of all RAB setup requests, and inter-frequency hard handovers with
instant macro diversity also occupy a small proportion (about 20%) of all inter-frequency
hard handovers. Therefore, this feature does not have a great impact on system capacity,
including CE resource, code resource, and power resouce.
In downlink SRB OVER DCH scenarios, the inter-frequency hard handover success rate
can be increased by 10% to 20% after the Instant Macro Diversity feature is enabled.
Specific gains depend on the proportion of inter-frequency hard handovers that meet the
conditions for instant macro diversity among all inter-frequency hard handovers.
Impact on NEs
 NEs in the RAN
 NEs Outside the RAN
− UE: This feature does not have any special requirements for the UE.

Copyright © Huawei
− CN: If service awareness is implemented on the RAN, this feature does not have any
special requirements for the CN. If service awareness is implemented on the CN, the
DSCP field in the headers of IP packets from the CN must be able to help identify
video data packets.
Impact on Hardware
 RNC hardware
No impact.
 NodeB hardware
No impact.
 NodeB software
The NodeB version must be V100R010C00 or V100R017C00 or later.

No impact.

ge Command
Type
New CSIFFastMul SET BSC6900 Instant macro diversity switch

RLSetupSwitc UHOCOMM BSC6910 for inter-frequency CS hard
h handovers
New PSIFFastMulR SET BSC6900 Instant macro diversity switch
LSetupSwitch UHOCOMM BSC6910 for inter-frequency PS hard
handovers
New CSIFFastMul ADD/MOD BSC6900 Instant macro diversity switch
RLSetupSwitc UHOCOMM BSC6910 for inter-frequency CS hard
h handovers
New PSIFFastMulR ADD/MOD BSC6900 Instant macro diversity switch
LSetupSwitch UHOCOMM BSC6910 for inter-frequency PS hard
handovers
New UERelSupIFF SET BSC6900 Protocol version that the UE
astMulRL UHOCOMM BSC6910 must comply with to support the
M Instant Macro Diversity feature
New IFFastMulRLI ADD/MOD BSC6900 Offset for the initial power of
nitPwrPo UCELLCAC BSC6910 the RL in the non-best target
cell for the inter-frequency hard
handover with instant macro
diversity

Copyright © Huawei

ge Command
Type
New IFFastMulRL ADD/MOD BSC6900 Downlink admission threshold

DlThd UCELLCAC BSC6910 of the non-best target cell for
the inter-frequency hard
diversity
New IFFastMulRL ADD/MOD BSC6900 SF reserved as the uplink credit
UlCeResvSf UCELLCAC BSC6910 resource of the non-best target
cell for the inter-frequency hard
diversity
New IFFastMulRL ADD/MOD BSC6900 SF reserved as the downlink
DlCeCodeResv UCELLCAC BSC6910 credit resource and
Sf channelization code resource of
the non-best target cell for the
inter-frequency hard handover
with instant macro diversity
New IFFastMulRL SET BSC6900 Relative threshold for setting up
SetupRelThr UHOCOMM BSC6910 a new link during an inter-
M frequency hard handover with
instant macro diversity
New SPECUSER_I SET BSC6900 Switch for the UE blacklist of
FFASTMULR UHOCOMM BSC6910 the instant macro diversity
LSETUP_DIS M algorithm
ABLED_SWI
TCH
New IFFastMulRL SET BSC6900 Parameters for DL TPC pattern
SetupDlTpcPa UHOCOMM BSC6910 1 used during an inter-frequency
t M hard handover with instant
macro diversity
New RxTxUpperTh SET BSC6900 Upper threshold for the UE Rx-
d UHOCOMM BSC6910 Tx time difference
M
New RxTxLowerTh SET BSC6900 Lower threshold for the UE Rx-
d UHOCOMM BSC6910 Tx time difference
M

The following counters have been added to accommodate this feature.
Cha Counter Name Functio NE Description
nge n Subset
Type
New VS.HHO.AttInterFr HHO.Cel BSC6900 Number of attempts for outgoing

Copyright © Huawei
Cha Counter Name Functio NE Description

nge n Subset
Type
eqOut.FastMultRLS l BSC6910 inter-frequency CS hard

etup.CS handovers with instant macro
diversity
eqOut.FastMultRLS l BSC6910 inter-frequency PS hard
etup.PS handovers with instant macro
diversity
New VS.HHO.SuccInter HHO.Cel BSC6900 Number of successful attempts
FreqOut.FastMultR l BSC6910 for outgoing inter-frequency CS
LSetup.CS hard handovers with instant
macro diversity
New VS.HHO.SuccInter HHO.Cel BSC6900 Number of successful attempts
FreqOut.FastMultR lL BSC6910 for outgoing inter-frequency PS
LSetup.PS hard handovers with instant
macro diversity
New VS.HHO.InterFreq HHO.Cel BSC6900 Number of decisions indicating
Out.FastMultRLSet lL BSC6910 that the signal quality meet the
up.Prep.CS condition for an outgoing inter-
frequency CS hard handover with
instant macro diversity
eqOut.FastMultRLS l BSC6910 inter-frequency CS hard
etup.CS handovers with instant macro
diversity

This feature does not have any impact on fault management and maintenance.

This feature requires the following feature:
− WRFD-020302 Inter Frequency Hard Handover Based on Coverage
None
If asynchronous reconfiguration for inter-frequency hard handovers is enabled on the
existing network before this feature, the increase in the inter-frequency hard handover
success rate will be lower than 10% to 20%, because the former feature can also increase
the inter-frequency hard handover success rate by 10% to 20%.

Copyright © Huawei
Related Operations
For details, see chapter "Engineering Guidelines" of Instant Macro Diversity Feature
Parameter Description in the RAN feature documentation.

IR-RAN17.0-013
Feature ID
WRFD-170102
6.3.1.1.19 WRFD-170204 Radio Aware Video Shaping
Description
HTTP-based video streaming, one of the main data services in the mobile broadband (MBB)
network, is gaining popularity within the recent years. However, in radio networks where
multiple users are performing HTTP-based video streaming services simultaneously, the
associated DPCHs of HSDPA consume a large proportion of cell power. Consequently, the
available HSDPA power is small, and the experience of users performing HTTP-based video
streaming services is poor.
This feature uses the service awareness function deployed in the RAN or the PS domain of the
core network (CN) to identify the HTTP-based video streaming service. After identifying the
HTTP-based video streaming service, this feature employs the video traffic shaping technique
to convert the continuous data transmission of this service to the alternate data transmission of
burst and sleep. The data transmission time of all the UEs performing the HTTP-based video
streaming service is staggered at the cell level. Only a few of them are in the burst
transmission mode at a point of time and others are put to the sleep transmission mode by
state transition to CELL_FACH or CELL_PCH. In this way, the non-HSDPA power in the cell
is less consumed so that the available HSDPA power and cell throughput increase. The
following figure shows the working mechanism of video traffic shaping.
Figure 1.1 Working mechanism of video traffic shaping

Copyright © Huawei
Note that only 3GPP Release 8 UEs can have non-HSDPA power less consumed through
video traffic shaping because only these UEs can remain in the Cell_FACH or CELL_PCH
state when receiving an SCRI message in the sleep transmission mode.
This feature increases the number of state transitions of UEs performing video streaming
services, which may increase the call drop rate.
Implementation
For details, see Radio Aware Video Shaping Feature Parameter Description.

 System capacity
This feature reduces the amount of non-HSPA power consumed by the HTTP-based
video streaming service in high-load cells. The available HSDPA power is increased as a
result, and the cell HSDPA throughput is increased.
 Impact on the call drop rate
The number of state transitions increases in cells that have this feature enabled. The call
drop rate may increase with the number of state transitions.
 Impact on the access success rate
After this feature takes effect in a cell, some UEs that participate in video traffic shaping
stay in the CELL_FACH or CELL_PCH state. Therefore, the power load and number of
HSPA UEs in the cell are reduced, and the RRC connection setup success rate and RAB
setup success rate increase.
 Impact on service experience
As the RRC connection setup success rate and RAB setup success rate increase, the
number of service attempts (CS voice, web browsing, HTTP-based video streaming, or
other PS data services) increase. User experience may change with the number of service
attempts.
For UEs participating in video traffic shaping, if an inter-RNC hard handover, Direct
Signaling Connection Re-establishment (DSCR), or inter-RAT handover is triggered and
the RNC is not configured with the Iur interface, the TCP needs to be reset to reestablish
the HTTP connection for the video streaming service. The TCP reset indication,
however, may fail to be sent to these UEs. Even if UEs successfully receive the TCP
reset indication, some UEs may fail to initiate video streaming services again, and
consequently these UEs experience video service interruptions. Therefore, this feature is
not recommended for cells at the coverage edge of an RNC that is not configured with
the Iur interface.
For UEs participating in video traffic shaping, if the RNC is configured with the Iur
interface and does not support common channels, UEs in the sleep transmission mode
may experience unrecoverable video freezing during an SRNS relocation. Therefore, this
feature is not recommended for cells at the coverage edge of an RNC that is configured
with the Iur interface and does not support common channels.
In multi-carrier networking scenarios, if this feature is enabled in cells that are
configured to preferentially accommodate UEs in the CELL_FACH state or that are
configured not to accommodate UEs in the CELL_FACH state, the possibility of video
freezing increases. Therefore, this feature is not recommended for such cells.
When this feature takes effect, the counters measuring service experience will not
deteriorate in most cases. However, some counters may slightly deteriorate in some

Copyright © Huawei
cases. If a UE's rate is low in the initial acceleration phase, the UE may experience video
freezing before entering the burst transmission mode for the first time.
 Impact on RNC load
For the BSC6900, this feature increases the CPU load of the SPU by less than 5%. For
the BSC6910, this feature increases the control-plane load of the GPU by less than 5%.
Impact on NEs
 RAN NEs
 Other NEs
This feature requires support from the UE. The UE must send an SCRI message to the
RNC in compliance with 3GPP Release 8 or later. For UEs that do not send an SCRI
message to the RNC, if customers require these UEs to support video traffic shaping, run
the ADD UIMEITAC command to add the TACs of these UEs to the list of TACs that
support video traffic shaping.
If the service awareness function is performed by RAN, this feature has no special
requirements on the CN. If the service awareness function is performed by the PS
domain of the CN, the IP data packets sent to the UE must have the corresponding DSCP
value in their headers for identifying the video streaming service.
Impact on Hardware
 RNC
If the service awareness function is performed by RAN, the BSC6900 must be configured
with the NIUa board, and the BSC6910 must be configured with the ENIUa board.
If the service awareness function is performed by CN, there is no requirements on RNC
hardware.
 NodeB
The 3900 series base stations support this feature when configured with the WBBPb, WBBPd,
WBBPf, or UBBPd board. The WBBPa board does not support this feature. The BTS3902E,
BTS3803E, and BTS3911E support this feature.

The RNC uses a private FP control frame on the user plane of the Iub interface to notify the
NodeB of the start and end of the burst transmission of a UE. The private FP control frame
type is 250.

The following MML command has been introduced to accommodate this feature.

Copyright © Huawei

ge
Type
New SET UVIDEOSHAPING BSC690 This command is used to set the

0 algorithm parameters
BSC691
0
The following parameters have been added or modified to accommodate this feature.
ge Command
Type
New CellConnAlgoS ADD BSC690 Whether video traffic shaping is

witch1: UCELLCONN 0BSC69 enabled for video streaming
VIDEO_SHAP ALGOPARA 10 services in a cell. When this
E_SWITCH MOD switch is set to on, video traffic
UCELLCONN shaping is enabled for video
ALGOPARA streaming services on HSDPA
channels. When this switch is set
to off, video traffic shaping is
disabled in the cell.
Modif TAC_FUNC ADD BSC690 Added the Video_Shaping
ied UIMEITAC 0BSC69 value. If Video_Shaping is
MOD 10 selected, UEs using the specified
UIMEITAC TAC support the Radio Aware
Video Shaping feature. If the
RNC receives an SCRI message
from one of this type of UEs
during video traffic shaping, the
RNC keeps the UE in the
CELL_FACH, CELL_PCH, or
URA_PCH state without
releasing the UE's RRC
connection.

The following function subset has been modified to accommodate this feature.
Change Function NE Description
Type Subset
Modified VIDEO.CELL BSC6900 A measurement unit is renamed

BSC6910 VIDEO.CELL.

Copyright © Huawei
Cha Counter Function NE Description

nge Name Subset
Type
New VS.VideoSha VIDEO.CELL BSC6900 Number of D2F State Transition

pe.D2F.Att BSC6910 Attempts Triggered upon Video
Service Traffic Shaping for Cell
New VS.VideoSha VIDEO.CELL BSC6900 Number of Successful D2F State
pe.D2F.Succ BSC6910 Transitions Triggered upon
Video Service Traffic Shaping
for Cell
New VS.VideoSha VIDEO.CELL BSC6900 Number of D2P State Transition
pe.D2P.Att BSC6910 Attempts Triggered upon Video
New VS.VideoSha VIDEO.CELL BSC6900 Number of Successful D2P State
pe.D2P.Succ BSC6910 Transitions Triggered upon
for Cell
New VS.VideoSha VIDEO.CELL BSC6900 Number of F2D State Transition
pe.F2D.Att BSC6910 Attempts Triggered upon Video
New VS.VideoSha VIDEO.CELL BSC6900 Number of Successful F2D State
pe.F2D.Succ BSC6910 Transitions Triggered upon
for Cell
New VS.VideoSha VIDEO.CELL BSC6900 Number of P2D State Transition
pe.P2D.Att BSC6910 Attempts Triggered upon Video
New VS.VideoSha VIDEO.CELL BSC6900 Number of Successful P2D State
pe.P2D.Succ BSC6910 Transitions Triggered upon
for Cell
New VS.Video.UE. VIDEO.CELL BSC6900 Average Number of UEs Playing
Mean.Cell BSC6910 Online Video Services for cell
New VS.VideoSha VIDEO.CELL BSC6900 Average Number of Video
pe.UE.Burst. BSC6910 Shaping UEs in the Burst State
Mean.Cell for Cell
New VS.VideoSha VIDEO.CELL BSC6900 Average Number of Video
pe.UE.Sleep. BSC6910 Shaping UEs in the Sleep State
Mean.Cell for Cell
New VS.VideoSha VIDEO.CELL BSC6900 Total Number of Times That
pe.Burst.Num BSC6910 Video Shaping UEs Enter the
Burst State for Cell
New VS.VideoSha VIDEO.CELL BSC6900 Total Duration During Which
pe.Burst.Dura BSC6910 Video Shaping UEs Stay in the
tion Burst State for Cell

Copyright © Huawei
Cha Counter Function NE Description

nge Name Subset
Type
New VS.VideoSha VIDEO.CELL BSC6900 Total Data Volume Transmitted

pe.Burst.Data BSC6910 by Video Shaping UEs in the
Burst State for Cell
New VS.VideoSha VIDEO.CELL BSC6900 Total Number of Times That
pe.Sleep.Num BSC6910 Video Shaping UEs Enter the
Sleep State for Cell
New VS.VideoSha VIDEO.CELL BSC6900 Total Duration During Which
pe.Sleep.Dura BSC6910 Video Shaping UEs Stay in the
tion Sleep State for Cell

No impact.

− WRFD-010611 HSDPA Enhanced Package
− WRFD-170202 TCP Proxy
− WRFD-150252 Video Service Rate Adaption
If this feature is used together with the WRFD-150252 Video Service Rate Adaption
feature, only this feature takes effect.
− WRFD-020806 Differentiated Service Based on SPI Weight
− WRFD-150255 Differentiated Service Based on Terminal
If this feature is used together with the preceding two features, the differentiation
between different types of UEs is reduced to achieve the best bearer efficiency for UEs
participating in video traffic shaping.
− WRFD-150233 Differentiated Service Based on Resource Reservation
− WRFD-150254 Differentiated Service Based on Application Resource Reservation
If this feature is used together with the preceding two features, the power of video
service users cannot exceed the upper power threshold for resource groups.
− WRFD-020128 Quality Improvement for Subscribed Service
− WRFD-020132 Web Browsing Acceleration
− WRFD-020133 P2P Downloading Rate Control during Busy Hour
− WRFD-150253 VoIP Application Management
If video service users are also performing the services related to the preceding four
features, these UEs alternate between the burst and sleep transmission modes but cannot
perform state transitions. Consequently, the non-HSPA power consumption cannot be
reduced, and cell throughput cannot be increased.
− WRFD-010652 SRB over HSDPA

Copyright © Huawei
If the WRFD-010652 SRB over HSDPA feature is used, a video service user consumes
less non-HSPA power, and consequently the gain provided by this feature is decreased.
The gain may even be decreased to zero.
Related Operations
For details, see chapter "Engineering Guidelines" of Radio Aware Video Shaping Feature
Parameter Description

IR-RAN17.0-003
Feature ID
WRFD-170204
6.3.1.1.20 WRFD-171203 Uplink Control Channel OLPC
Description
Before this feature is introduced, the RNC performs OLPC based on the retransmission rate of
uplink data transmission of HSUPA users. The working principles are as follows:
 When there is data transmission, the RNC obtains the SIR target of OLPC based on the data
retransmission rate and the target data retransmission rate and ensures that the data
retransmission rate converges to the target value.
 When there is no data transmission, the SIRtarget is not adjusted.
 The NodeB performs inner loop power control based on the SIRtarget.
In practice, the SIRtarget can be further reduced when there is no data transmission. This feature
is thereby introduced to minimize the SIRtarget for HSUPA users without compromising the
quality of control channels when there is no data transmission, so as to reduce the uplink load
generated by control channels and improve uplink system capacity. The working principles of
this feature are as follows:
 When there is data transmission, the RNC obtains the SIR target of OLPC based on the data
retransmission rate and the target data retransmission rate. The NodeB performs inner
loop power control based on the obtained value and ensures that the data retransmission
rate converges to the target value.
 When there is no data transmission, the NodeB obtains the SIR target of OLPC based on the
quality of control channels and performs inner loop power control based on the obtained
value, so as to ensure the quality of control channels.
The SIRtarget of control channels is less than the SIRtarget calculated by the RNC. Therefore, this
feature can reduce the control channel load for HSUPA users with no data transmission and
improve uplink system capacity.
Implementation
For details, see Uplink Control Channel OLPC Feature Parameter Description.

 System capacity

Copyright © Huawei
This feature increases uplink capacity by 5%–10% or decreases the RTWP in scenarios
where a large number of HSUPA users are processing burst services and the uplink load
is high. For example, in a cell where 40 HSUPA users are processing burst services at an
average rate of 5 kbit/s and one user is performing full buffer services, this feature
increases uplink capacity by about 7%.
− None
Impact on NEs
Impact on Hardware
The 3900 series base stations must be configured with the uplink baseband processing board
WBBPd, WBBPf, or UBBPd and the downlink baseband processing board WBBPb, WBBPd,
WBBPf, or UBBPd.

No impact.

No impact.
Type ID Command
New ULCCHOLP SET NodeB Indicates whether to enable the

CSW ULOCELLAL Uplink Control Channel OLPC
GPARA feature.
New ULCCHOLP SET NodeB Indicates the minimum SIRtarget
CMINSIRTA NODEBALGP for the Uplink Control Channel
RGET ARA OLPC feature.
New ULCCHOLP SET NodeB Indicates the air interface high
CLOADHIG ULOCELLAL load threshold for the Uplink
HTHD GPARA Control Channel OLPC feature.
New ULCCHOLP SET NodeB Indicates the air interface low
CLOADLO ULOCELLAL load threshold for the Uplink
WTHD GPARA Control Channel OLPC feature.


Copyright © Huawei

Type Name Subset
New VS.HSUPA.1 HSUPA.LOC NodeB Average Number of 10 ms TTI

0msTTI.CCH ELL HSUPA UEs in the CCH OLPC
OLPC.UserN state in a Cell
um.Mean
New VS.HSUPA.2 HSUPA.LOC NodeB Average Number of 2 ms TTI
msTTI.CCH ELL HSUPA UEs in the CCH OLPC
OLPC.UserN state in a Cell
um.Mean
New VS.HSUPA.1 HSUPA.LOC NodeB Average SIRtarget decrease of 10
0msTTI.CCH ELL ms TTI HSUPA UEs in the CCH
OLPC.SIRTar OLPC state in a Cell
getDec.Mean
New VS.HSUPA.2 HSUPA.LOC NodeB Average SIRtarget decrease of 2
msTTI.CCH ELL ms TTI HSUPA UEs in the CCH
OLPC.SIRTar OLPC state in a Cell
getDec.Mean

No impact.

− WRFD-010612 HSUPA Introduction Package
− WRFD-010610 HSDPA Introduction Package
− WRFD-021350 Independent Demodulation of Signals from Multiple RRUs in One
Cell
− WRFD-141202 Independent Demodulation of Signals from Multiple Small Cell
RRUs in One Cell
− WRFD-151208 Macro-Micro multi RRUs in one cell
The UE must use algorithm 1 to interpret the received Transmit Power Control (TPC)
commands. Otherwise, the inner loop power control cannot be performed in time, and
this feature does not provide any gain or provides negative gains. The algorithm used
by the UE to interpret the TPC commands is specified by the PwrCtrlAlg parameter
in the SET UFRC command. To query this algorithm, run the LST UFRC command.
− WRFD-010684 2*2 MIMO
This feature does not take effect for UEs using MIMO.
This feature does not take effect for platinum users.

Copyright © Huawei
This feature does not take effect for UEs using the Improvement of User Experience
in Low Traffic Service feature.
− WRFD-010686 CPC - DTX / DRX
This feature does not take effect for UEs using Discontinuous Transmission
(DTX)/Discontinuous Reception (DRX).
This feature does not take effect for time-division scheduled UEs.
Related Operations
For details, see chapter "Engineering Guidelines" of Uplink Control Channel OLPC Feature

IR-RAN17.0-024
Feature ID
WRFD-171203

6.3.1.2.1 WRFD-01061009 HSDPA H-ARQ & Scheduling (MAX C/I, RR and PF)
Description
This feature is related to hybrid automatic repeat request (HARQ) and HSDPA scheduling
algorithms. Huawei provides multiple HSDPA scheduling algorithms such as Max C/I, RR,
PF, and EPF.
In RAN17.1, the following is true: If the ACK/NACK on the uplink feedback channel HS-
DPCCH falls into the compressed mode gap, the to-be-sent data of the user enters the
candidate set for scheduling. If the ACK/NACK on the downlink data transmission channel
falls into the compressed mode gap, the to-be-sent data of the user does not enter the
candidate set.
Implementation
For details, see section "Change History" inHSDPA Feature Parameter Descriptionin RAN

The change in this feature increases user throughput and cell throughput, thereby
improving user experience. The specific gains provided by this feature are affected by
the start of the compressed mode and the availability of resources for the data
transmission during compressed mode. Therefore, the gains provided by this feature
depend on the actual conditions and cannot be quantified.
None

Copyright © Huawei
Impact on NEs
The change in this feature is implemented on the NodeB.
Impact on Hardware


Change Parameter MML Command NE Description
Type ID
New HSDPAL2O SET NodeB Whether to enable the

PTSW ULOCELLMACHSP optimized HSDPA L2
ARA function. When this
LST switch is set to ON, the
ULOCELLMACHSP optimized HSDPA L2
ARA function is enabled. The
HSDPA resource
utilization and downlink
throughput are increased.


Related Operations
For details, see the description about the WRFD-01061009 HSDPA H-ARQ & Scheduling
(MAX C/I, RR and PF) feature in chapter "Engineering Guidelines" inHSDPA Feature
Parameter Descriptionin RAN Feature Documentation.

IR-RAN17.1-074

Copyright © Huawei
Feature ID
WRFD-01061009
6.3.1.2.2 WRFD-01061010 HSDPA Flow Control
Description
This feature enables resource information interaction between the RNC and NodeB to ensure
that the data to be transmitted by the UE matches the scheduled one. In addition, this feature
can minimize the buffer size and buffer time of the NodeB to avoid data loss probably caused
by overtime data buffering.
The enhanced HSDPA flow control function is introduced to RAN17.1. This function applies
to scenarios in which transmission bit errors occur on the Iub interface. The function can
avoid misjudging transmission bit errors as transmission congestion, which causes the cell
throughput to decrease. The enhanced HSDPA flow control function significantly improves
the cell throughput in these scenarios.
Implementation
For details, see section "Change History" inHSDPA Feature Parameter Descriptionin RAN

When packet loss caused by non-congestion reasons occurs in transmission networks
(for example, packet loss caused by erroneous bits), the change in this feature increases
user throughput and thereby improves user experience. The specific gains provided by
this feature depend on the occurrences of packet loss caused by non-congestion reasons
and Iub bandwidth. Therefore, the gains depend on the actual conditions and cannot be
quantified.
No impact.
Impact on NEs
Impact on Hardware



Copyright © Huawei

Type ID Command
New DLFLOWC ADD NodeB Whether to enable the enhanced

TRLENHS DLFLOWCT HSDPA flow control function.
W RLPARA When this switch is set to ON, a
RMV drastic decrease in the available
DLFLOWCT downlink bandwidth and
RLPARA downlink throughput can be
prevented when the packet loss
MOD is caused by non-congestion
DLFLOWCT reasons in transmission
RLPARA networks.
LST
DLFLOWCT
RLPARA


Related Operations
For details, see the description about the WRFD-010610 HSDPA Flow Control Feature in
chapter "Engineering Guidelines" ofHSDPA Feature Parameter Descriptionin RAN Feature
Documentation.

IR-RAN17.1-068
Feature ID
WRFD-01061010
6.3.1.2.3 WRFD-010713 Traffic-Based Activation and Deactivation of the Supplementary

Carrier In Multi-carrier
Description
This feature requires that the downlink service of a user be carried on multi-carrier HSDPA
and the uplink service be carried on DCH or SC-HSUPA. The feature can deactivate the
supplementary carrier of a UE when the traffic volume to be processed by the UE is low.
When the traffic volume rises, the supplementary carrier can then be reactivated and the user
becomes a dual-carrier user again.

Copyright © Huawei
In RAN17.1, this feature also applies to 3C-HSDPA and 4C-HSDPA users.
Implementation
For details, seeTraffic-Based Activation and Deactivation of the Supplementary Carrier In
Multi-carrier Feature Parameter Descriptionin RAN Feature Documentation.

When there are a large number of multi-carrier HSDPA users (3C-HSDPA or 4C-HSDPA
users) and downlink traffic is light, deactivating the supplementary carrier reduces uplink
load in the cell served by the primary carrier and increases the uplink capacity. This is
demonstrated in the increase of the cell uplink throughput or admitted number of users.
To improve user experience of web browsing services, the throughput threshold for
activating the supplementary carrier is reduced from 400 kbit/s to 200 kbit/s. As a result,
the number of HS-SCCH orders for activating the supplementary carrier increases, which
leads to a small increase in the consumption of HS-SCCH code words and power.
The change in this feature deactivates the supplementary carrier for 3C-HSDPA, 4C-
HSDPA users with low traffic volume, reducing the radio resources available for these
users. As a result, the service delay of these users may rise.
To improve user experience of web browsing services, the throughput threshold for
activating the supplementary carrier is reduced from 400 kbit/s to 200 kbit/s. As a result,
the value of the counter VS.HSDPA.DCCfg.SupCarrierDeact.TimeRatio decreases.
Impact on NEs
The feature enhancement is implemented on the NodeB. The change in this feature requires
the UE support 3C-HSDPA or 4C-HSDPA.
Impact on Hardware



Copyright © Huawei
Chang Counter Name Measure NE Description

e Type ment
Unit
New VS.HSDPA.MCCfg. HSDPA2. NodeB The preceding counter indicates

SupCarrierDeact.Tra LCell the ratio of the traffic-based
ffic.TimeRatio deactivation time of the
supplementary carrier to the
activation time for 3C-HSDPA
and 4C-HSDPA users whose
primary-carrier cell is the cell
where the counter is measured.
This counter is used to evaluate
the effect and benefits of the
function of downlink traffic-
based deactivation of the
supplementary carrier for 3C-
HSDPA and 4C-HSDPA users.


The change in this feature is dependent on the feature WRFD-150250 3C-HSDPA or
WRFD-150207 4C-HSDPA.
No impact.
No impact.
Related Operations
For details, see Engineering Guidelines in Traffic-Based Activation and Deactivation of the
Supplementary Carrier In Multi-carrier Feature Parameter Descriptionof RAN Feature
Documentation.

IR-RAN17.1-013
Feature ID
WRFD-010713

Copyright © Huawei
6.3.1.2.4 WRFD-150208 Flexible Dual Carrier HSDPA
Description
Flexible Dual Carrier HSDPA allows a UE to set up HSDPA connections with any two inter-
frequency same-coverage cells under a NodeB. A pair of these cells is a DC/DB-HSDPA
group. The RAN schedules services in all DC/DB-HSDPA groups, which improves the UE
data rate and system capacity.
A frequency in a DC/DB-HSDPA group can belong to two frequency bands. That is, a cell can
be used to perform DC-HSDPA and DB-HSDPA at the same time.
Implementation
For details, seeFlexible Dual Carrier HSDPA Feature Parameter Description.

This feature reduces the difference between the downlink load of cells in a multi-carrier
cell group. The effect of this feature depends on the number of DC-HSDPA or DB-
HSDPA UEs and their traffic volume. A larger number of DC-HSDPA or DB-HSDPA
UEs and a larger traffic volume results in smaller difference between the downlink load
of cells.
Cells in a multi-carrier cell group have the same time offset (specified by
theTCellparameter). When multiple cells (three or four) served by the same RRU in a
sector transmit data at full power, the peak-to-average ratio (PAR) of the RRU increases
if a higher-order modulation scheme is used in the downlink. As a result, cell throughput
may decrease. On live networks, cells in the same sector do not transmit data at full
power for a long period of time, and therefore cell throughput only slightly decreases.
After Flexible Dual Carrier HSDPA is activated in networks with a low load, the data
rates of DC-HSDPA UEs increase because UEs can fully utilize frequency resources. As
network load increases, the gain provided by this feature decreases. The difference
between the downlink load of cells in a multi-carrier cell group before this feature is
activated also affects the gain provided by this feature. A larger difference results in a
greater gain.
Impact on NEs
UEs must support the Flexible Dual Carrier HSDPA feature and must belong to HS-DSCH
category 21 or higher.
Impact on Hardware
 Dependency on RNC hardware
None
 Dependency on NodeB hardware
− The BTS3812A, BTS3812E, and BTS3812AE can be configured with a maximum of
three carriers. The BTS3812A, BTS3812E, and BTS3812AE must be configured with

Copyright © Huawei
the EBBI, EBOI, EDLP+EULP, or EDLP+EULPd boards. The HBBI and HDLP
boards do not support this feature.
− The DBS3800 can be configured with a maximum of three carriers. The DBS3800
must be configured with the EBBC or EBBCd board.
− Only the 3900 series base stations support 4C-HSDPA. Only the 3900 series base
stations can enable MIMO for frequencies where Flexible Dual Carrier HSDPA is
activated. The 3900 series base stations must be configured with the WBBPb,
WBBPd, WBBPf, or UBBPd board.
Table 6-6presents an example of the hardware configuration of a NodeB that is configured
with three sectors.
Table 1.1 Example of the hardware configuration of a NodeB that is configured with three sectors
Scenario Base Hardware Configuration
Station
Type
Three carriers DBS3800 The DBS3800 must be

configured with two
BBU3806s. The two
BBU3806s must be
interconnected, and each
must be configured with an
EBBC or EBBCd board.
BTS3812A, The BTS3812A, BTS3812E,
BTS3812E, and BTS3812AE must be
and configured with at least two
BTS3812AE EBBI or EBOI boards.
Alternatively, the
BTS3812A, BTS3812E, and
BTS3812AE must be
configured with two EDLP
boards and one EULP or
EULPd board.
3900 series The 3900 series base
base stations stations must be configured
with at least two WBBPb,
WBBPd, or WBBPf boards
(in any combination).
Three carriers (with DC-HSDPA+MIMO) 3900 series The 3900 series base
with at least two WBBPf
boards, three WBBPb
boards, three WBBPd
boards, or three boards that
can be any combination of
WBBPb, WBBPd, and
WBBPf boards.
Four carriers 3900 series The 3900 series base
with at least three WBBPb,

Copyright © Huawei
Scenario Base Hardware Configuration

Station
Type
WBBPd, or WBBPf boards

(in any combination).
Four carriers (with DC-HSDPA+MIMO) 3900 series The 3900 series base
with at least three WBBPd
or WBBPf boards (in any
combination).

The Flexible Dual Carrier HSDPA feature affects the Iub interface as follows:
 Affects the "Possible Secondary Serving Cell" information element (IE).
The NodeB sends an AUDIT RESPONSE or RESOURCE STATUS INDICATION
message to the RNC when one of the following occurs:
−The NodeB receives an AUDIT REQUEST message.
−A cell is established.
−The capability of a cell changes.
The AUDIT RESPONSE or RESOURCE STATUS INDICATION message includes the
"Multi Cell Capability Info" and "Dual Band Capability Info" IEs. Each of these two IEs
includes one or multiple "Possible Secondary Serving Cell" IEs. The "Possible
Secondary Serving Cell" IE carries the list of intra-band candidate secondary cells and
the list of inter-band candidate secondary cells.
 Adds a new IE "HS-DSCH FDD Secondary Serving Information".
The "HS-DSCH FDD Secondary Serving Information" IE is added to the RADIO LINK
SETUP REQUEST, RADIO LINK ADDITION REQUEST, RADIO LINK
RECONFIGURATION PREPARE, and RADIO LINK RECONFIGURATION
REQUEST messages. This IE notifies the NodeB of the secondary cell configuration.



Copyright © Huawei
If the cells in a multi-carrier cell group operate in the same frequency band, all these
cells must have the WRFD-010696 DC-HSDPA feature enabled.
If the cells in a multi-carrier cell group operate in two different frequency bands, all cells
must have the WRFD-010696 DC-HSDPA and WRFD-150209 DB-HSDPA features
enabled.
If the Flexible Dual Carrier HSDPA feature is used with the WRFD-010684 2×2 MIMO
feature, the Primary/Secondary common Pilot (PSP) mode must be used.
− RAN Sharing and MOCN
The Flexible Dual Carrier HSDPA feature can be enabled in RAN sharing or Multi-
Operator Core Network (MOCN) scenarios.
When the Flexible Dual Carrier HSDPA feature is enabled in RAN sharing or MOCN
scenarios, run the RNC MML commandSET UOPERATORSHARINGMODE to set
InterPlmnMultiCarrSwitch to Yes. This allows UEs to use cells belonging to different
operators, but each UE must use its operator's cell as the primary cell. The secondary cell
can belong to other operators. When InterPlmnMultiCarrSwitch is set to No, the UE
must use its operator's cells as the primary and secondary cells.
Related Operations
For details, see chapter 7 "Engineering Guidelines" inFlexible Dual Carrier HSDPA Feature

IR-RAN17.1-013
Feature ID
WRFD-150208
6.3.1.2.5 WRFD-01061212 HSUPA Iub Flow Control in Case of Iub Congestion
Description
This feature dynamically adjusts the uplink Uu throughput by monitoring Iub transmission
resources, thereby greatly improving resource utilization.
The feature enhancement in RAN17.1 applies to scenarios in which transmission bit errors
occur on the Iub interface. The enhancement can avoid misjudging transmission bit errors as
transmission congestion, which causes the cell throughput to decrease. The feature
enhancement can significantly improve the cell throughput in these scenarios.
Implementation
For details, seeTransmission Resource Management Feature Parameter Description in RAN
Feature Documentation. The specific sections are listed in the change history of the
document.

Copyright © Huawei

Impact on NEs
The feature enhancement is implemented on the NodeB.
Impact on Hardware



Related Operations
For details, see the engineering guidelines in Transmission Resource Management Feature
Parameter Description of the RAN feature documentation.

None.
Feature ID
WRFD-01061212
6.3.1.2.6 WRFD-140204 DC-HSUPA
Description
DC-HSUPA was introduced in 3GPP Release 9 as a wireless broadband standard based on
High Speed Packet Access (HSPA). DC-HSUPA achieves a smooth evolution of HSPA by
using uplink carrier aggregation. This feature enables a UE to perform E-DCH transmission
simultaneously in two cells on two intra-band adjacent carriers that provide the same

Copyright © Huawei
coverage, thereby increasing the uplink peak rate of a single user and the average throughput
of the cell.
In RAN17.1, a DC-HSUPA UE that is moving within the coverage of the RNC use separate
active sets on the primary and secondary carriers. That is, the RNC delivers measurement
information separately to the primary and secondary carriers and switches over the primary
and secondary carriers based on the measurement results reported by the UE.
The enhancement of this feature can reduce the interference that users' uplink services cause
to the intra-frequency neighboring cells of the secondary carrier. In addition, the enhancement
increases the number of DC-HSUPA soft handover users, enabling more users to enjoy
throughput gains provided by the DC-HSUPA technology.
Implementation
For details, see section "Change History" inDC-HSUPA Feature Parameter Descriptionin

Impact on NEs
The enhancement of this feature is implemented on the RNC and NodeB.
Impact on Hardware

 Information about neighboring cells of the uplink secondary carrier and about handover
parameters has been added to the MEASUREMENT CONTROL message over the air
interface.
 Private information elements (IEs) have been added to some messages over the Iub
interface.
− Added the "Secondary Uplink Frequency Active State Index" IE to the RADIO LINK
SETUP REQUEST and RADIO LINK ADDITION REQUEST messages. The value
of this IE is set based on the activation status of the secondary carrier.
− Added the "Secondary Uplink Frequency Radio Link Index" IE to the "RL
Information" IE in the RADIO LINK SETUP REQUEST and RADIO LINK
ADDITION REQUEST messages. This new IE indicates whether the RL added for a
DC-HSUPA UE is carried on the secondary carrier.
− Added the "NodeB Ability" IE to the AUDIT RESPONSE and RESOURCE STATUS
INDICATION messages. This IE indicates whether the NodeB supports the
independent active sets function.
− Added the "User Uplink Multiple Carrier Indicator" IE to the RADIO LINK
RECONFIGURATION PREPARE message. This IE indicates whether DC-HSUPA is
used after a reconfiguration.

Copyright © Huawei

Type ID Command
New HoSwitch2: SET BSC690 DC-HSUPA independent active

HO_DC_HS UCORRMALG 0 set algorithm switch
UPA_IND_T OSWITCH BSC691
WO_ACTIV 0
ESET
New SecPeriodM SET BSC690 1A to Periodic Report Number
RReportNum UINTRAFREQ 0 on Secondary Carrier
for1A HO BSC691
0
New SecReportInt SET BSC690 1A to Periodic Report Period on
ervalfor1A UINTRAFREQ 0 Secondary Carrier
HO BSC691
0
New SecIntraRelT SET BSC690 1A Relative Thld for PS on
hdFor1APS UINTRAFREQ 0 Secondary Carrier
HO BSC691
0
New SecHystFor1 SET BSC690 1A Hysteresis on Secondary
A UINTRAFREQ 0 Carrier
HO BSC691
0
New SecTrigTime SET BSC690 1A Triggering Delay on
1A UINTRAFREQ 0 Secondary Carrier
HO BSC691
0
New SecIntraRelT SET BSC690 1B Relative Thld for PS on
hdFor1BPS UINTRAFREQ 0 Secondary Carrier
HO BSC691
0
New SecHystFor1 SET BSC690 1B Hysteresis on Secondary
B UINTRAFREQ 0 Carrier
HO BSC691
0
New SecTrigTime SET BSC690 1B Triggering Delay on
1B UINTRAFREQ 0 Secondary Carrier
HO BSC691
0
New SecPeriodM SET BSC690 1C to Periodic Report Number

Copyright © Huawei

Type ID Command
RReportNum UINTRAFREQ 0 on Secondary Carrier

for1C HO BSC691
0
New SecReportInt SET BSC690 1C to Periodic Report Period on
ervalfor1C UINTRAFREQ 0 Secondary Carrier
HO BSC691
0
New SecHystFor1 SET BSC690 1C Hysteresis on Secondary
C UINTRAFREQ 0 Carrier
HO BSC691
0
New SecTrigTime SET BSC690 1C Triggering Delay on
1C UINTRAFREQ 0 Secondary Carrier
HO BSC691
0
New SecPeriodM ADD BSC690 1A to Periodic Report Number
RReportNum UCELLINTRA 0 on Secondary Carrier
for1A FREQHO BSC691
MOD 0
UCELLINTRA
FREQHO
New SecReportInt ADD BSC690 1A to Periodic Report Period on
ervalfor1A UCELLINTRA 0 Secondary Carrier
FREQHO BSC691
MOD 0
UCELLINTRA
FREQHO
New SecIntraRelT ADD BSC690 1A Relative Thld for PS on
hdFor1APS UCELLINTRA 0 Secondary Carrier
FREQHO BSC691
MOD 0
UCELLINTRA
FREQHO
New SecHystFor1 ADD BSC690 1A Hysteresis on Secondary
A UCELLINTRA 0 Carrier
FREQHO BSC691
MOD 0
UCELLINTRA
FREQHO
New SecTrigTime ADD BSC690 1A Triggering Delay on
1A UCELLINTRA 0 Secondary Carrier
FREQHO BSC691
MOD 0
UCELLINTRA

Copyright © Huawei

Type ID Command
FREQHO
New SecIntraRelT ADD BSC690 1B Relative Thld for PS on
hdFor1BPS UCELLINTRA 0 Secondary Carrier
FREQHO BSC691
MOD 0
UCELLINTRA
FREQHO
New SecHystFor1 ADD BSC690 1B Hysteresis on Secondary
B UCELLINTRA 0 Carrier
FREQHO BSC691
MOD 0
UCELLINTRA
FREQHO
New SecTrigTime ADD BSC690 1B Triggering Delay on
1B UCELLINTRA 0 Secondary Carrier
FREQHO BSC691
MOD 0
UCELLINTRA
FREQHO
New SecPeriodM ADD BSC690 1C to Periodic Report Number
RReportNum UCELLINTRA 0 on Secondary Carrier
for1C FREQHO BSC691
MOD 0
UCELLINTRA
FREQHO
New SecReportInt ADD BSC690 1C to Periodic Report Period on
ervalfor1C UCELLINTRA 0 Secondary Carrier
FREQHO BSC691
MOD 0
UCELLINTRA
FREQHO
New SecHystFor1 ADD BSC690 1C Hysteresis on Secondary
C UCELLINTRA 0 Carrier
FREQHO BSC691
MOD 0
UCELLINTRA
FREQHO
New SecTrigTime ADD BSC690 1C Triggering Delay on
1C UCELLINTRA 0 Secondary Carrier
FREQHO BSC691
MOD 0
UCELLINTRA
FREQHO
New SecIntraAblT SET BSC690 1F Absolute Ec/No Thld on

Copyright © Huawei

Type ID Command
hdFor1FEcN UINTRAFREQ 0 Secondary Carrier

o HO BSC691
0
New SecIntraAblT SET BSC690 1F Absolute RSCP Thld on
hdFor1FRSC UINTRAFREQ 0 Secondary Carrier
P HO BSC691
0
New SecHystFor1 SET BSC690 1F Hysteresis on Secondary
F UINTRAFREQ 0 Carrier
HO BSC691
0
New SecTrigTime SET BSC690 1F Triggering Delay on
1F UINTRAFREQ 0 Secondary Carrier
HO BSC691
0
New SecIntraAblT ADD BSC690 1F Absolute Ec/No Thld on
hdFor1FEcN UCELLINTRA 0 Secondary Carrier
o FREQHO BSC691
MOD 0
UCELLINTRA
FREQHO
New SecIntraAblT ADD BSC690 1F Absolute RSCP Thld on
hdFor1FRSC UCELLINTRA 0 Secondary Carrier
P FREQHO BSC691
MOD 0
UCELLINTRA
FREQHO
New SecHystFor1 ADD BSC690 1F Hysteresis on Secondary
F UCELLINTRA 0 Carrier
FREQHO BSC691
MOD 0
UCELLINTRA
FREQHO
New SecTrigTime ADD BSC690 1F Triggering Delay on
1F UCELLINTRA 0 Secondary Carrier
FREQHO BSC691
MOD 0
UCELLINTRA
FREQHO
New DCHsupaHR SET BSC690 DC-HSUPA Periodic Retry
etryPenaltyTi UCOIFTIMER 0 Penalty Timer
me BSC691
0

Copyright © Huawei

The following counters have been introduced on the RNC side to accommodate this
feature.
Chang Counter Measur NE Description
e Type Name ement
Unit
New VS.HSUPA.SH HSUPA. RN Number of Attempts to Add RLs on the

O.DC.SEC.Att Cell C Secondary Carrier for DC-HSUPA UEs
RLAdd During Soft and Softer Handovers for
Cell
New VS.HSUPA.SH HSUPA. RN Number of Times RLs on the Secondary
O.DC.SEC.Suc Cell C Carrier Are Successfully Added for DC-
cRLAdd HSUPA UEs During Soft and Softer
Handovers for Cell
New VS.HSUPA.SH HSUPA. RN Number of Attempts to Remove RLs on
O.DC.SEC.Att Cell C the Secondary Carrier for DC-HSUPA
RLDel UEs During Soft and Softer Handovers
for Cell
New VS.HSUPA.SH HSUPA. RN Number of Times RLs on the Secondary
O.DC.SEC.Suc Cell C Carrier Are Successfully Removed for
cRLDel DC-HSUPA UEs During Soft and Softer
Handovers for Cell
Modifie VS.SRNCIubB TRFFIC. RN The meaning of this counter is updated as
d ytesHSUPA.Rx Cell C follows:
This counter provides the number of UL
MAC PDU bytes (excluding UL signaling
data) received by the SRNC on the E-
DCH FP over the Iub interface. This
counter is measured in HSUPA cells in
the active set. For a DC-HSUPA UE, this
counter is measured only on the primary
carrier if the DC-HSUPA UE only uses
the primary carrier for data transmission.
If a DC-HSUPA UE uses both the primary
and secondary carriers for data
transmission, this counter measures the
total number of UL MAC PDU bytes
received by the SRNC on the E-DCH FP
over the Iub interface on the primary
carrier. If a DC-HSUPA only uses the
secondary carrier for data transmission,
this counter is measured only on the
secondary carrier.
Modifie VS.SRNCIubB TRFFIC. RN The meaning of this counter is updated as
d ytesEDCHSig. Cell C follows:
Rx This counter provides the number of UL
MAC PDU bytes received by the SRNC
on the E-DCH FP carrying signaling over
the Iub interface. This counter is

Copyright © Huawei
Chang Counter Measur NE Description

e Type Name ement
Unit
measured in HSUPA cells in the active

set. This counter does not include the E-
DCH FP carrying UL signaling when UEs
are in the enhanced CELL_FACH state.
For a DC-HSUPA UE, this counter is
measured only on the primary carrier if
the DC-HSUPA UE only uses the primary
carrier for data transmission. If a DC-
HSUPA UE uses both the primary and
secondary carriers for signaling
transmission, this counter measures the
total number of UL MAC PDU bytes
received by the SRNC on the E-DCH FP
over the Iub interface on the primary
carrier. If a DC-HSUPA only uses the
secondary carrier for signaling
transmission, this counter is measured
only on the secondary carrier.


Related Operations
For details, see chapter "Engineering Guidelines" inDC-HSUPA Feature Parameter
Descriptionin RAN feature documentation.

IR-RAN17.1-078
Feature ID
WRFD-140204

Copyright © Huawei
6.3.1.2.7 WRFD-021350 Independent Demodulation of Signals from Multiple RRUs in

One Cell
Description
With the Multiple RRUs in One Cell feature, a cell can be made up of areas that are covered
by multiple RRUs. In this case, the coverage of a cell is more flexible. The Independent
Demodulation of Signals from Multiple RRUs in One Cell feature implements independent
demodulation and combination of signals from multiple RRUs.
The Multiple RRUs in One Cell feature is used in distributed base stations. This feature
mainly applies to F1 tracks, high-speed railways, and highways.
The Independent Demodulation of Signals from Multiple RRUs in One Cell feature supports
configuring 12 pieces of sector equipment (UBBPd6 boards) to expand the coverage area of a
single cell.
Implementation
For details, seeMultiple RRUs in One Cell Feature Parameter Description in RAN Feature
Documentation.

Theoretically, this feature helps to increase the uplink cell capacity by N-fold if there are
N sets of sector equipment in a cell, compared with a common cell. For example,
RAN17.1 allows 12 RRUs to serve one cell, doubling the uplink capacity when
compared with 6-RRU cells.
Compared with deploying two 6-RRU cells, deploying one 12-RRU cell has the
following impact on network performance:
Impact on NEs
The change in this feature is implemented on the NodeB. This feature requires the CME.
Impact on Hardware
This feature depends on the UBBPd board and one of the following boards: BBU3900,
BBU3910, BBU3910A. The uplink resource group must be configured with UBBPd boards
(including at least one UBBPd6 board).



Copyright © Huawei


Related Operations
For details, see "Engineering Guidelines" inMultiple RRUs in One Cell Feature Parameter
Descriptionof the RAN Feature Documentation.

IR-RAN17.1-056
IR-RAN17.1-058
IR-RAN17.1-077
Feature ID
WRFD-021350
6.3.1.2.8 WRFD-140225 Narrowband Interference Suppression
Description
With Narrowband Interference Suppression, the NodeB scans the frequency spectrum within
the bandwidth of a UMTS carrier to rapidly identify stable narrowband interferences (with
millisecond-level changes in frequency or power) and dynamically configures a filter
stopband for the receiver to suppress narrowband interferences.
In RAN17.1, this feature also supports the U2100, U1900, and AWS frequency bands in
addition to U900 and U850.
In RAN17.1, the number of cells that support this feature within a single RRU is increased
and the ability to suppress fast-changing narrowband interference is enhanced.
Implementation
For details, seeNarrowband Interference Suppression Feature Parameter Description.

When no narrowband interference exists, the negative gain on uplink capacity decreases
from 10% to 5% when Narrowband Interference Suppression is enabled.

Copyright © Huawei
When no narrowband interference exists, the performance of uplink low-speed services

decreases from 0.4 dB to 0.3 dB and that of uplink high-speed services decreases from
1.8 dB to 0.6 dB.
Impact on NEs
Impact on Hardware
The changes in this feature have no impact.


For the RRU3952 and RRU3959, changes in performance management are listed in the
following table.
The following measurement units have been modified to accommodate this feature.
Change Measurement Unit NE Description
Type
New NBIS.LOCELL.SECTOREQ NodeB NBIS measurement for sector

M equipment in the local cell

Change Counter Measureme NE Description
Type Name nt Unit
New VS.NBISRati NBIS.LOCE NodeB Ratio of time when the

o.Locell.Sect LL.SECTOR Narrowband Interference
orEqm.Ant0 EQM Suppression feature takes effect
for antenna 0
for antenna 1
for antenna 2

Copyright © Huawei

Type Name nt Unit

for antenna 3


None
None
Related Operations
For details, seeNarrowband Interference Suppression Feature Parameter Description.

IR-RAN17.1-039
IR-RAN17.1-092
Feature ID
WRFD-140225
6.3.1.2.9 WRFD-050501 Clock Sync on Ethernet in NodeB
Description
This feature is introduced to provide a solution for clock synchronization in all-IP networking
mode. With this feature, the operator can keep clock synchronization for NodeBs without
changing the existing data network and adding QoS requirements of the transport network.
RAN17.1 supports the G.8275.1 time synchronization protocol, which was defined based on
IEEE 1588V2 in 2014 by ITU. NodeBs can connect to devices in other vendors' transport
networks if the standard protocol was supported by the networks.
Implementation
For details, see the RAN feature documentationSynchronization Feature Parameter
Description.

Copyright © Huawei

Impact on NEs
This feature is implemented on the NodeB. The transmission equipment connected to a
NodeB must support ITU-T G.8275.1.
Impact on Hardware


Type ID Command
New DSTMLTM ADD Node This parameter is added for

ACTYPE IPCLKLINK/LS B scenarios in which theProfile
T IPCLKLINK Typeparameter in the
IPCLKLNK MO is set to
G.8275.1.
Modifie PROFILET ADD Node This parameter specifies the
d YPE IPCLKLINK/LS B protocol used by an IP clock
T IPCLKLINK link. The valueG.8275.1is added
for this parameter.
Modifie DM ADD Node This parameter specifies the
d IPCLKLINK/LS B domain to which an IP clock link
T IPCLKLINK belongs. WhenProfile Typeis set
to G.8275.1, the value of this
parameter ranges from 24 to 43.
Modifie DELAYTYP ADD Node This parameter specifies the
d E IPCLKLINK/LS B delay compensation mechanism
T IPCLKLINK for the transmission between a
clock server and a base station.
WhenProfile Typeis set to
G.8275.1, this parameter can be
set only to E2E.

Copyright © Huawei


Related Operations
For details, see "Engineering Guidelines to NodeB Clock Synchronization" in the RAN
feature documentationSynchronization Feature Parameter Description.

IR-0000257369
Feature ID
WRFD-050501
6.3.1.2.10 Real-time HSDPA Cell Throughput Monitoring on the LMT
Description
The cell throughput monitoring function is enhanced by providing DL HSPA throughput
measurement, in addition to the measurement pertaining to UL throughput for R99 services,
UL HSPA throughput, and DL throughput for R99 services.
Implementation
Once cell throughput monitoring is started, the NodeB measures HSDPA Mac-d throughput
periodically. It then calculates HSDPA throughput based on the accumulative measurements
and reports HSDPA throughput to the LMT.

 System capacity
None
None

Copyright © Huawei
Impact on NEs
None
Impact on Hardware
None

None

None
None
None
None

None
Related Operations
None

IR: 10001695
Feature ID
None
6.3.1.2.11 WRFD-010696 DC-HSDPA
Description
The Dual-Cell HSDPA (DC-HSDPA) feature allows UEs to establish connections in two
adjacent inter-frequency same-coverage cells. With this feature, UEs can use the resources of
both cells under different carriers, increasing the peak throughput of UEs.
 RAN15.0
In RAN15.0, non-adjacent carriers at the same frequency band can be used for DC-
HSDPA.
 RAN17.0

Copyright © Huawei
In RAN17.0, DC-HSDPA can be deployed across boards.
Implementation
For details, see DC-HSDPA Feature Parameter Description.

 System capacity
The feature enhancement has no impact on system capacity.
The feature enhancement has no impact on network performance.
Impact on NEs
The feature enhancement is implemented on the NodeB.
Impact on Hardware
The feature enhancement has no impact on hardware.

The feature enhancement has no impact on inter-NE interfaces.

The parameter in the following table has been introduced on the NodeB side to
accommodate the feature enhancement.
Change Parameter MML NE Remarks
Type ID Command
New HSPAMCIN SET NodeB Indicates whether HSDPA multi-

TERBRDSC NODEBALGP carrier cells support inter-board
HSW ARA joint scheduling. If this
parameter is set to ON, HSDPA
multi-carrier cells support inter-
board joint scheduling, thereby
improving the balance of
baseband resources between
boards and reducing the number
of capability decline alarms for
the following features: DC-
HSDPA, DC-HSDPA+MIMO,
Flexible Dual Carrier HSDPA,
MC-HSDPA+MIMO, DB-
HSDPA+MIMO, DB-HSDPA,
3C-HSDPA, 4C-HSDPA, and
Macro-Micro DC-HSDPA.

Copyright © Huawei

The feature enhancement has no impact on performance management.
The feature enhancement has no impact on fault management.

The feature enhancement has no impact on other features.
Related Operations
For details, see chapter "Engineering Guidelines" of DC-HSDPA Feature Parameter
Description.

IR-RAN17.0-007
Feature ID
WRFD-010696
6.3.1.2.12 MRFD-221601 Multi-mode BS Common Reference Clock(NodeB)
Description
 GBTS and NodeB Common Reference Clock
From SRAN3.0, Huawei multimode base stations provide common reference clock for
GSM and UMTS that share one BBU.
 SRAN5.0:
− Common Ethernet reference clock from Iub interface
When common Ethernet reference clock is used, GSM can obtain the clock via the
BBU backplane from the WMPT or UTRP.
− Common IP network 1588V2 reference clock from Iub interface
When GSM and UMTS support the 1588V2 reference clock, only one 1588V2 clock
server and client are required. GSM can obtain the clock via the BBU backplane from
the WMPT or UTRP.
 SRAN10.0:
Common IP network 1588V2 reference clock for time synchronization from Iub
interface.
When GSM and UMTS support the 1588V2 reference clock for time synchronization,
only one 1588V2 clock server and one 1588V2 clock client are required. GSM can
obtain the reference clock for time synchronization via the BBU backplane from the
UMPT.
 NodeB and eNodeB Common Reference Clock
From SRAN5.0, Huawei multimode base stations provide common reference clock for
UMTS and LTE that share one BBU.
− SRAN10.0:

Copyright © Huawei
Common IP network 1588V2 reference clock for time synchronization from S1

interface.
When UMTS and LTE support the 1588V2 reference clock for time synchronization,
only one 1588V2 clock server and one 1588V2 clock client are required. UMTS can
obtain the reference clock for time synchronization via the BBU backplane from the
LMPT or UMPT_L.
 GBTS, NodeB and eNodeB Common Reference Clock
From SRAN7.0, Huawei multimode base station provides common reference clock for
GSM, UMTS, and LTE when the BBUs are interconnected.
− SRAN10.0:
Common IP network 1588V2 reference clock for time synchronization from S1
interface
When GSM, UMTS, and LTE support the 1588V2 reference clock for time
synchronization, only one 1588V2 clock server and one 1588V2 clock client are
required. GSM and UMTS can obtain the reference clock for time synchronization
via the BBU backplane from the LMPT or UMPT_L.
Implementation
See Common Clock Feature Parameter Description in RAN Feature Documentation.

 System capacity
Impact on NEs
Impact on Hardware
The WMPT, UTRP2, and UTRP9 do not support IEEE1588 V2 clock synchronization.



Copyright © Huawei

This feature is dependent on the following features:
− WRFD-050501 Clock Sync on Ethernet in NodeB
Related Operations
See the "Engineering Guidelines" chapter in Common Clock Feature Parameter Description
of RAN Feature Documentation.

IR-SRAN10-CLK-02
Feature ID
MRFD-221601

None

6.3.2.1 Critical
6.3.2.1.1 The call drop rate increases if the WRFD-170201 Seamless Crystal Voice feature
is activated.

Ticket
Number
Description Condition: The WRFD-170201 Seamless Crystal Voice feature has been
activated on the RNC.
Symptom: There is a high probability that the NodeB reports ALM-
26200 Board Hardware Fault and calls are frequently dropped within a
short period.
Severity Critical
Root Cause When the WRFD-170201 Seamless Crystal Voice feature is activated, the

Copyright © Huawei
NodeB incorrectly processes CS and PS combined services. As a result,

internal communication on the baseband processing unit becomes
abnormal.
Solution The NodeB now correctly processes CS and PS combined services.
Solution None
Impact
6.3.2.2 Major
6.3.2.2.1 If the MC Inter-Board Joint Scheduling Switch is turned on and a DC UE
accesses a cell in the handover area, there is a low probability that a board resets.

Ticket
Number
Description Condition: The MC Inter-Board Joint Scheduling Switch is turned on

and a DC UE accesses a cell in the handover area.
Symptom: There is a low probability that the UMPT board or baseband
processing unit resets.
Impact: Ongoing services are interrupted for a short period of time
during the reset.
Severity Major
Root Cause If the MC Inter-Board Joint Scheduling Switch is turned on, the radio
link reconfiguration procedure is defective.
Solution None
Impact
6.3.2.2.2 Activation, deactivation, or parameter modification of a logical cell fails.

Ticket
Number
Description Condition: A large number of neighboring cells are configured for a cell
on the RNC and the length of the
NBAP_SYS_INFO_UPDATE_REQUET message is too long.
Symptom: The NodeB returns an activation or deactivation failure in
response to activation, deactivation, or parameter modification of the
logical cell.

Copyright © Huawei
Impact: The logical cell is unavailable.

Severity Major
Root Cause In the preceding instance, the RNC fails to encode the
NBAP_SYS_INFO_UPDATE_REQUET message.
Solution The mechanism for processing the
NBAP_SYS_INFO_UPDATE_REQUET message has been corrected.
Solution None
Impact
6.3.2.2.3 HSDPA throughput is low and the PS service drop rate increases for a cell
when MC Inter-Board Joint Scheduling Switch is turned on.

Ticket
Number
Description Condition: MC Inter-Board Joint Scheduling Switch is turned on. The

WBBPd and WBBPf/UBBP boards provide downlink baseband resources
for an HSDPA multi-carrier cell group. A large number of DC-HSDPA
users access a cell in the group.
Symptom: Ongoing HSDPA services are abnormal and HSDPA
throughput of users decreases.
Impact: HSDPA throughput decreases and the PS service drop rate
increases for the cell.
Severity Major
Root Cause The NodeB incorrectly processes the supplementary carrier of DC-
HSDPA users. As a result, the bit error rate (BER) is high on the
supplementary carrier.
Solution The NodeB now correctly processes the supplementary carrier of DC-
HSDPA users.
Solution None
Impact
6.3.2.2.4 After KPI invisible fault detection is enabled, ALM-26203 Board Software
Program Error is reported when it should not be

Number

Copyright © Huawei
 The cell where HSUPA is activated serves a small number of HSUPA
UEs for four consecutive hours.
 KPI invisible fault detection is enabled.
Symptom: ALM-26203 Board Software Program Error is reported when
it should not be.
Impact: This alarm is reported when it should not be, but it does not
affect ongoing services.
Severity Major
Root Cause The KPI invisible fault detection algorithm is defective.
Solution None
Impact
6.3.2.2.5 After sleeping cell detection is enabled, ALM-26203 Board Software Program
Error is reported when it should not be

Number
 No UEs access a cell for four consecutive hours.
 Sleeping cell detection is enabled.
Symptom: ALM-26203 Board Software Program Error is reported when
it should not be.
Impact: This alarm is reported when it should not be, but it does not
affect ongoing services.
Severity Major
Root Cause Sleeping cell detection does not function well when no UEs access a cell.
Solution Sleeping cell detection now functions well when no UEs access a cell.
Solution None
Impact
6.3.2.2.6 Cells established on the UBBPd board occasionally experience a decrease in the
RRC connection setup success rate
Trouble iCare:3799522

Copyright © Huawei
Ticket
Description Condition: Uplink baseband equipment for local cells includes the
UBBPd board.
Symptom: For cells established on the UBBPd board, the RRC
connection setup success rate (indicated by the
RRC.ConnEstab.Succ.Rate counter) and RL setup success rate (indicated
by the VS.IUB.SuccRLSetup.Rate counter) decrease.
Impact: Cells established on the UBBPd board occasionally experience a
decrease in the RRC connection setup success rate.
Severity Major
Root Cause In specific scenarios, the uplink use-plane processing procedure is

defective on dedicated links established on the UBBPd board. As a result,
RRC connection setup fails.
Solution None
Impact
6.3.2.2.7 HSUPA UEs served by the WBBPf or UBBPd board experience low data rates if
flow control is triggered and the switch for correcting the SIR when the RTWP is
abnormal is turned on

Ticket
Number
 Uplink baseband equipment contains the WBBPf or UBBPd board.
 Flow control is triggered.
 The switch for correcting the SIR when the RTWP is abnormal
(specified by the ULINNERPCABNRISECTRLSW parameter) is
turned on for a NodeB.
Symptom: Outer loop power control (OLPC) does not function well for
HSUPA UEs and their data rates are low.
Impact: Data rates of these UEs are lower than expected.
Severity Major
Root Cause In the preceding instance, the Frame Protocol (FP) control frame does
not provide expected OLPC information. As a result, OLPC fails to
work on the RNC.
Solution The FP control frame now provides expected OLPC information.
Solution None

Copyright © Huawei
Impact
6.3.2.2.8 There is an extremely low probability that ongoing services carried on the
WBBPd or WBBPb board are interrupted

Ticket
Number
Description Condition: The WBBPd or WBBPb board receives an abnormal

message.
Symptom: The WBBPd or WBBPb board does not respond to the
message and fails to process UEs' services.
Impact: Ongoing services carried on the WBBPd or WBBPb board are
interrupted.
Severity Major
Root Cause The message processing mechanism is not robust. As a result, after
receiving an abnormal message, the WBBPd or WBBPb board fails to
process subsequent messages.
Solution The message processing mechanism used by the WBBPd and WBBPb
board has been improved to ensure robustness.
Solution None
Impact
6.3.2.2.9 There is a low probability that a cell fails to be established.

Ticket
Number
Description Condition: The uplink baseband equipment works in 4-channel

demodulation mode and serves cells. The WBBPd or WBBPb board in
the uplink baseband equipment is blocked and then unblocked.
Symptom: There is a low probability that a cell establishment fails.
Impact: Ongoing services carried on the WBBPd or WBBPb board are
interrupted.
Severity Major
Root Cause In 4-channel demodulation mode, the mechanism for checking

parameters during cell establishments is defective.

Copyright © Huawei
Solution None
Impact
6.3.2.2.10 If the Seamless Crystal Voice feature is enabled, there is an extremely low
probability that the WBBPf or UBBPd board resets unexpectedly.

Ticket
Number
Description Condition: The WBBPf or UBBPd board provides uplink baseband

resources and the Seamless Crystal Voice feature is enabled.
Symptom: There is an extremely low probability that the WBBPf or
UBBPd board resets unexpectedly, and ALM-26200 Board Hardware
Fault is reported.
Impact: Ongoing services carried on the WBBPf or UBBPd board are
interrupted for a short time.
Severity Major
Root Cause The Seamless Crystal Voice feature uses a defective algorithm.
Specifically, there is a low probability that the DSPs on the WBBPf and
UBBPd boards access incorrect addresses of data packets in the buffer.
Solution None
Impact
6.3.2.2.11 Verification of UL Frequency Channel Number and DL Frequency Channel

Number configured for a local cell is inaccurate.
Trouble DTS: CR-SEG-1264

Ticket
Number
Description Condition: A local cell is configured for a NodeB, with UL Frequency

Channel Number and DL Frequency Channel Number set to different
frequency bands.
Symptom: The local cell may be successfully configured but ALM-
28203 Local Cell Unusable is reported for the local cell.
Impact: The local cell setup fails.
Severity Major
Root Cause In the preceding instance, the NodeB does not allow UL Frequency
Channel Number and DL Frequency Channel Number configured for

Copyright © Huawei
the local cell to be at different frequency bands and it uses a defective

verification rule. As a result, the undesired UARFCN configurations
cannot be identified and local cell setup fails.
Solution The defective verification rule has been corrected.
Solution None
Impact
Test Case ID ATP-SEG-1264
6.3.2.2.12 The call drop rate of HSDPA users increases after the SRB over HSDPA
feature is enabled.
Trouble Ticket DTS: DTS2014100900899

Number
Description Condition: A NodeB is configured with an HSDPA cell, and the

WRFD-010652 SRB over HSDPA feature is enabled for this cell by
following instructions in HSDPA Feature Parameter Description.
Symptom: The call drop rate of SRB-over-HSDPA users is higher than
that of SRB-over-DCH users.
Impact: Massive deployment of the WRFD-010652 SRB over HSDPA
feature is hindered.
Severity Major
Root Cause When processing data for SRB-over-HSDPA users, the NodeB treats
these users as common HSDPA users when performing MAC layer
scheduling and HARQ retransmissions. As a result, the radio link
performance of SRB over HSDPA is less good than that of SRB over
DCH. Additionally, inner- and outer-loop power control optimization is
not performed on the F-DPCH channel of the serving cell.
Solution SRB-over-HSDPA scheduling has been optimized, and power control
on the F-DPCH channel has been also optimized.
Solution None
Impact
6.3.2.2.13 A remote cell reports ALM-28203 Local Cell Unusable if the remote cell and an
ordinary cell are served by the same uplink resource group.

Ticket
Number
Description Condition: A remote cell and an ordinary cell are served by the same
uplink resource group. The DC-HSDPA feature is not enabled for the

Copyright © Huawei
remote cell but enabled for the ordinary cell.

Symptom: The remote cell reports ALM-28203 Local Cell Unusable.
Impact: The remote cell is unusable.
Severity Major
Root Cause The resource allocation priority for remote cells is lower than that for
ordinary cells. Consequently, remote cells cannot be allocated baseband
resources.
Solution The resource allocation priority for remote cells now is higher than that
for ordinary cells so that remote cells can be allocated baseband
resources.
Solution None
Impact
6.3.2.2.14 The VS.HSUPA.AGCHCodeUtil.Mean counter returns an incorrect value if

the Turbo IC Phase 2 feature is enabled.

Ticket
Number
Description Condition: The UBBPd or WBBPf board functions as the baseband

processing unit and the Turbo IC Phase 2 feature is enabled.
Symptom: The value returned by VS.HSUPA.AGCHCodeUtil.Mean
increases significantly. At some sites, the counter value reaches 100%.
Impact: VS.HSUPA.AGCHCodeUtil.Mean returns an incorrect value.
Severity Major
Root Cause After Turbo IC Phase 2 is enabled, the E-AGCH is used too frequently,
affecting the measurement of VS.HSUPA.AGCHCodeUtil.Mean.
Solution In the preceding scenario, the NodeB does not send scheduling
information over the E-AGCH to the UEs once they have no data to
transmit. This solution does not adversely affect the performance of
Turbo IC Phase 2.
Solution None
Impact
6.3.2.2.15 The WBBPb board falsely reports that a local cell supports the EAI capability.

Ticket

Copyright © Huawei
Number
The WBBPb board provides downlink baseband resources to a local cell.
The Enhanced CELL_FACH and UL Layer 2 Improvement features are
activated for the cell.
Symptom: In the DSP ULOCELL command output, EAI Capability is
Enable.
NOTE
The DSP ULOCELL command is used to query the status of a local cell.
Impact: If the NodeB allocates EAIs to UEs using Uplink Enhanced
CELL_FACH, they fail to access the cell.
Severity Major
Root Cause The WBBPb board uses a defective mechanism to report EAI capability
support. As a result, it falsely reports EAI capability support.
Solution The defective mechanism has been corrected so that the WBBPb board
correctly reports EAI capability support.
Solution None
Impact
6.3.2.2.16 The NodeB performance counter VS.HSUPA.SingletoAllHARQNum returns a

smaller value than expected.

Ticket
Number
Description Condition: Turbo IC (Phase 2) is enabled.

Symptom: The value returned by the VS.HSUPA.SingletoAllHARQNum
counter is less than expected.
Impact: The value is inaccurate.
Severity Major
Root Cause When the downlink baseband processing unit performs transitions from
using a single HARQ process to using all HARQ processes, the
VS.HSUPA.SingletoAllHARQNum counter is not measured for some
users.
Solution The NodeB now accurately measures the
VS.HSUPA.SingletoAllHARQNum counter for all users in all scenarios.
Solution None
Impact

Copyright © Huawei
6.3.2.2.17 When the MOCN CE resource independent allocate(per cell) license expires,
the NodeB becomes unavailable and cannot be restored following a restart.

Ticket
Number
Description Condition: The MOCN CE resource independent allocate(per cell)

license is delivered to the NodeB and some private operators that adopt
MOCN use the same frequency. When this license expires, the NodeB is
restarted (for example, by means of an upgrade).
Symptom: The RNC reports the ALM-22214 NodeB Unavailable, and
the NodeB cannot process services in cells.
Impact: Services become unavailable.
Severity Major
Root Cause During the restart, the NodeB uses a defective mechanism for processing
the MOCN CE resource independent allocate(per cell) license that has
expired.
Solution None
Impact
6.3.2.2.18 The feature query results are incorrect in the scenario with specific NodeB
board configurations.

Ticket
Number
 The NodeB is configured with the WMPT and UTRPc boards.
 The UTRPCEXTCNBAPCAP parameter is set to ON.
 The feature query function is performed on the CME for the NodeB.
Symptom: The feature query results indicate that configuration
capabilities and licenses of all features are not supported.
Impact: The query results are incorrect.
Severity Major
Root Cause When the UTRPCEXTCNBAPCAP parameter is set to ON, the feature
query processing module is not configured on the UTRPc board. As a
result, the feature query messages cannot be correctly processed and
therefore the NodeB replies with messages indicating that feature
configuration capabilities and licenses are not supported.

Copyright © Huawei
Solution The feature query processing module is now configured on the UTRPc
board.
Solution None
Impact
6.3.2.2.19 There is a low probability that baseband processing units are restarted
because CDT tracing is terminated.

Ticket
Number
The UMPT functions as the main control board. After CDT tracing is
started, the user exits and stops CDT tracing at the same time.
Symptom: All baseband processing units serving UMTS cells report the
EVT-26213 NE Startup alarm.
Impact: Baseband processing units are restarted.
Severity Major
Root Cause When the user exits and stops CDT tracing at the same time, there is a
very low probability that internal data access encounters exceptions and
the UMPT process does not run properly. As a result, all the baseband
processing units are restarted.
Solution The operation reliability of stopping CDT tracing has been enhanced to
prevent baseband processing units from restarting unexpectedly.
Solution None
Impact
6.3.2.2.20 The service rate of DC-HSUPA UEs is lower than expected in certain
scenarios.

Ticket
Number
Description Condition: The DC-HSUPA primary and secondary cells are configured,
and the uplink resource group includes the WBBPf or UBBPd board.
Symptom: After the DC-HSUPA feature is enabled for a cell, the service
rate for DC-HSUPA UEs that have accessed the cell is lower than
expected.
Impact: DC-HSUPA user experience deteriorates.

Copyright © Huawei
Severity Major
Root Cause The NodeB uses a defective mechanism to activate the DC-HSUPA
supplementary carrier. Consequently, if the information about DC-
HSDPA UEs served by the supplementary carrier is incorrect, the
supplementary carrier activation module cannot determine the rate of the
DC-HSDPA UEs and therefore the supplementary carrier cannot be
activated.
Solution None
Impact
6.3.2.2.21 The configuration information about HSDPA supplementary carriers and

supplementary streams are incorrectly presented in the results of HSPA Monitoring.

Ticket
Number
Description Condition: HSDPA supplementary carriers and supplementary streams

are not configured.
Symptom: The information about the HSDPA supplementary carriers and
supplementary streams is displayed as 0 in the results of HSPA
Monitoring.
Impact: Users cannot obtain the actual configurations of HSDPA
supplementary carriers and supplementary streams.
Severity Major
Root Cause The downlink DSP incorrectly reports 0 for the monitoring result of
HSDPA supplementary carriers and supplementary streams if they are not
configured.
Solution The downlink DSP now reports N/A for the monitoring result of HSDPA
supplementary carriers and supplementary streams if they are not
configured.
Solution None
Impact
6.3.2.2.22 After CPC is enabled, the call drop rates of PS/HSDPA/HSUPA services
increase in scenarios of DRD, hard handovers, and F2D/P2D transitions.

Ticket

Copyright © Huawei
Number
Description After continuous packet connectivity (CPC) is enabled, the call drop
rates of PS/HSDPA/HSUPA services increase in scenarios of DRD, hard
handovers, F2D state transitions, and P2D state transitions.
NOTE
DRD: directed retry decision
F2D: state transition from CELL_FACH to CELL_DCH
P2D: state transition from CELL_PCH to CELL_DCH or URA_PCH to
CELL_DCH
Severity Major
Root Cause  In scenarios of DRD, hard handovers, F2D state transitions, and P2D
state transitions, the RNC sends an RB SETUP message to the UE
and an RL SETUP message to the NodeB. The RB SETUP message
includes Commit CFN but the RL SETUP message does not.
Enabling Delay takes effect on the UE according to the value of
Commit CFN. Therefore, CPC may take effect on the NodeB earlier
than on the UE. When CPC is enabled on the NodeB but not on the
UE, the UE still continuously transmits data on the DPCCH.
Consequently, out-of-synchronization occurs in the uplink.
 The virtual finger causes demodulation performance to deteriorate
when CPC is enabled.
Solution  CPC now takes effect on the NodeB and UE at the same time.
 Demodulation performance when CPC is enabled has been improved.
Specifically, demodulation performance improvement is controlled
by RSVDBIT8 under the NODEBRSVDPARA1 parameter in the
SET NODEBRSVDPARA command. Demodulation performance
improvement is disabled by default.
Solution None
Impact
6.3.2.2.23 The CPU usage is imbalanced between baseband processing units when the
UTRPc board is used to expand the signaling capacity

Number
Description Condition: The NodeB is configured with the WMPT and UTRPc
boards. The SET NODEBALGPARA command is executed with
CNBAP Capacity Extension Using UTRPc set to ON. Then, the NodeB
is reset, or the BLK BRD command is executed to block a baseband
processing unit and then the UBL BRD command is executed to unblock
the baseband processing unit.
Symptom: The monitoring result on the LMT shows that the CPU usage
is imbalanced between baseband processing units, or the value of the
VS.BBUBoard.CPULoad.Mean counter varies among baseband

Copyright © Huawei
processing units.
Impact: When a baseband processing unit is overloaded, the success rate
of user access decreases.
Severity Major
Root Cause In the preceding scenario, some baseband processing units obtain CPU
resources abnormally, and therefore the CPU usage balancing algorithm
fails to take effect when baseband resources are allocated for users.
Solution The CPU resources have been properly allocated for baseband processing
units.
Solution None
Impact
6.3.2.2.24 In heavy traffic scenarios in parallel with frequent radio link setup and
removal, the UE access success rate decreases.

Ticket
Number
Description Condition: The WBBPb or WBBPd board provides resources for cells
and radio links are frequently added and removed for a large number of
UEs in heavy traffic scenarios.
Symptom: There is an extremely low probability that RRC connection
setup fails for the UEs.
Impact: The UE access success rate decreases.
Severity Major
Root Cause In heavy traffic scenarios, the WBBPb and WBBPd boards use a
defective mechanism to process frequent radio link setup and removal.
Solution This solution increases instantaneous admitted UEs and occasionally

Impact causes CE usage to rise in heavy traffic scenarios.
6.3.2.3 Minor
6.3.2.3.1 The HSDPA service throughput of E-RACH UEs is low.

Ticket
Number

Copyright © Huawei
Description After the E-RACH and E-FACH features have been enabled for a cell,
the HSDPA service throughput of UEs using Uplink Enhanced
CELL_FACH (E-RACH UEs) is low.
Severity Minor
Root Cause The NodeB uses a defective mechanism for processing HSDPA services
of E-RACH UEs. Each E-RACH UE can transmit a maximum of one
Frame Protocol (FP) frame in each TTI when using the defective
mechanism.
Solution The defective mechanism for processing HSDPA services of E-RACH
UEs has been corrected so that the proper number of FP frames can be
transmitted.
Solution None
Impact
6.3.2.3.2 The VS.HSUPA.10msTTI.CCHOLPC.UserNum.Mean and

VS.HSUPA.2msTTI.CCHOLPC.UserNum.Mean counters return larger values than
expected for a 4-antenna cell.

Ticket
Number
Description Condition: The Uplink Control Channel OLPC feature is enabled for a
4-antenna cell.
Symptom: The VS.HSUPA.10msTTI.CCHOLPC.UserNum.Mean and
VS.HSUPA.2msTTI.CCHOLPC.UserNum.Mean counters return larger
values than expected.
Impact: The number of HSUPA 2 ms TTI users in the CCH OLPC state
and the number of HSUPA 10 ms TTI users in the CCH OLPC state are
greater than expected.
Severity Minor
Root Cause The number of users in the secondary cell is included in measurement of
users in the CCH OLPC state in a 4-antenna cell.
Solution The statistical method for the two counters has been corrected so that
only the number of users in the CCH OLPC state is counted for a cell.
Solution None
Impact
Test Case ID ATP-DTS2014081305181

Copyright © Huawei
6.3.2.3.3 Platinum users experience poor voice services when network congestion occurs.

Ticket
Number
Description Condition: The WRFD-150204 Platinum User Prioritizing feature has

been activated and network congestion occurs.
Symptom: Platinum users experience poor voice services.
Impact: Platinum user experience deteriorates.
Severity Minor
Root Cause When network congestion occurs, downlink interference becomes strong,
adversely affecting the voice service quality of the platinum users.
Solution The HSDPA transmit power has been reduced for non-platinum users in
the cell that serves the platinum users.
Solution The solution reduces downlink cell load and improves the voice service
Impact quality of the platinum users, but reduces HSDPA throughput of the cell.
6.3.2.3.4 If the UBBPd board serves a multi-RRU cell, there is a possibility that ongoing
services carried on the UBBPd board are temporarily interrupted during cell
reconfiguration

Ticket
Number
Description Condition: A multi-RRU cell (using three or more RRUs) is set up on the
UBBPd board, and the cell is being reconfigured.
Symptom: ALM-26200 Board Hardware Fault is reported.
Impact: Ongoing services carried on the UBBPd board are temporarily
interrupted.
Severity Minor
Root Cause The NodeB uses a defective software protection mechanism during cell
reconfiguration. As a result, a software exception occurs, interrupting
ongoing services.
Solution None
Impact

Copyright © Huawei
6.3.2.3.5 When the E-DPCCH Boosting feature is activated, HSUPA throughput

decreases on the WBBPd board.

Ticket
Number
Description Condition: The E-DPCCH Boosting feature is activated.

Symptom: HSUPA service throughput occasionally decreases after the E-
DPCCH Boosting feature is activated.
Impact: Enabling the E-DPCCH Boosting feature reduces the HSUPA
throughput.
Severity Minor
Root Cause In the preceding instance, the power control algorithm on the WBBPd
board is not robust and does not adapt to all radio channels.
Solution The power control algorithm has been optimized to increase the
robustness when the E-DPCCH Boosting feature is activated.
Solution None
Impact
6.3.2.3.6 The link performance for HSDPA data transmission of some DC-HSDPA UEs
is slightly poor

Ticket
Number
Description Condition: A cell simultaneously serves multiple HSDPA UEs, among

which DC-HSDPA UEs are running HSDPA data transmission.
Symptom: The link performance for HSDPA data transmission of some
DC-HSDPA UEs is slightly poor.
Impact: Throughput of these DC-HSDPA UEs is slightly low.
Severity Minor
Root Cause The link performance for data transmission varies with DC-HSDPA UEs,
and the link performance of some of these UEs is not optimal.
Solution Some DC-HSDPA UEs whose link performance for HSDPA data
transmission is poor have been added to a whitelist. The RNC identifies
these UEs by TAC and then notifies the NodeB of the identified UEs. The
NodeB enables link performance optimization for these UEs.
NOTE
For details about RNC-related modifications and descriptions, see trouble ticket
DTS2014111910125 in BSC6900 V900R016C00SPC650 Release Notes and
BSC6910 V100R016C00SPC650 Release Notes.

Copyright © Huawei
Solution HSDPA throughput of the DC-HSDPA UEs in the whitelist is improved,

Impact and the link performance of other online UEs is not affected.
6.3.2.3.7 Values of bandwidth counters are low when the adaptive traffic shaping flow
control algorithm is selected for HSDPA services.
Trouble DTS: CR-SEG-1303

Ticket
Number
Description Condition: The adaptive traffic shaping flow control algorithm is

selected for HSDPA services by running the following command:
ADD DLFLOWCTRLPARA: SWITCH =
BW_SHAPING_ONOFF_TOGGLE
Symptom: Values of flow control bandwidth counters are low:
VS.IUB.FlowCtrol.DL.AdjBW.LgcPort1.Max
VS.IUB.FlowCtrol.DL.AdjBW.LgcPort2.Max
VS.IUB.FlowCtrol.DL.AdjBW.LgcPort1.Min
VS.IUB.FlowCtrol.DL.AdjBW.LgcPort2.Min
VS.IUB.FlowCtrol.DL.AdjBW.LgcPort1.Avg
VS.IUB.FlowCtrol.DL.AdjBW.LgcPort2.Avg
VS.RscGroup.FlowCtrol.DL.AdjBW.Max
VS.RscGroup.FlowCtrol.DL.AdjBW.Min
VS.RscGroup.FlowCtrol.DL.AdjBW.Avg
Impact: Values of flow control bandwidth counters are low and therefore
cannot indicate the actual bandwidth size.
Severity Minor
Root Cause When the adaptive traffic shaping flow control algorithm is selected for
HSDPA services, the NodeB automatically selects either
DYNAMIC_BW_SHAPING or NO_BW_SHAPING during flow
congestion detection on a port.
The preceding bandwidth counters are obtained by periodically sampling
the port bandwidth.
When NO_BW_SHAPING is selected, the sampled bandwidth value is
0 that is involved in the calculation of the minimum and average
bandwidth values. Therefore, values of bandwidth counters are low.
Solution No sampling is performed for the bandwidth when NO_BW_SHAPING
is selected.
Solution The minimum, average, and maximum values of bandwidth counters may
Impact increase.
The counters can better reflect the actual available bandwidth.
Test Case ID ATP-SEG-1303

Copyright © Huawei
6.3.2.3.8 License sales units of NodeB licenses displayed on the U2000 are unavailable.

Ticket
Number
Description Condition: NodeB licenses are allocated on the license allocation page of
the U2000.
Symptom: The license sales units are unavailable for NodeB licenses
displayed on the license allocation page of the U2000, for example, the
Turbo IC Phase2 feature is displayed as "Turbo IC Phase2" without its
sales unit.
Impact: Licenses may be incorrectly allocated, for example, licenses
with a sales unit of per Cell are incorrectly allocated by the unit of per
NodeB. As a result, the allocated licenses are insufficient, which affects
activation of corresponding optional features.
Severity Minor
Root Cause From RAN15.0, new licenses displayed on the U2000 are in the format
"feature name" without sales units.
Solution In RAN15.0, sales units are now added for all new licenses. In versions
earlier than RAN15.0, sales units are added for licenses without the sales
unit of per NodeB.
The format of licenses displayed on the U2000 is changed to "feature
name (per XXXX)", for example, Turbo IC Phase2 (per Cell).
Solution None
Impact
6.3.2.3.9 The RTWP rises due to a large number of high-speed HSUPA users.

Ticket
Number
Description Condition: There is a large number of HSUPA users, among which some
users perform high-speed data transmission (for example, greater than 2
Mbit/s) in the cell.
Symptom: The RTWP increases, for example, the RTWP exceeds that
corresponding to the target load.
Impact: The RTWP reaches its peak value.
Severity Minor
Root Cause When a large number of users exist on the UMTS network, users
generate interference to each other. If interference occurs, the RTWP
increases alternately. If the service rate of certain users is high (for

Copyright © Huawei
example, higher than 2 Mbit/s), the peak RTWP rises suddenly and the
target SIR reaches the upper limit. Consequently, outer-loop power
control does no converge.
Solution SIR estimation is optimized to decrease interference generated during
high-speed data transmission performed by HSUPA users. This increases
cell throughput.
Solution None
Impact
6.3.2.3.10 The KPI invisible fault detection mechanism needs to be optimized.
Trouble iCare: 4302800 / 2827424

Number
Description Condition: Board hardware is faulty and UEs served by the board
Symptom: KPIs are abnormal and ALM-26203 Board Software Program
Error is not reported.
Symptom: ALM-26203 Board Software Program Error is not reported
when it should be.
Severity Minor
Root Cause The KPI invisible fault detection mechanism is defective. As a result,
ALM-26203 Board Software Program Error may not be reported even if
BER remains at an acceptable level but the call drop rate is abnormal.
Solution The KPI invisible fault detection mechanism has been optimized to allow
detection of abnormal call drop rates.
Solution None
Impact
6.3.2.3.11 The value of UL Required Load is smaller than expected.

Ticket
Number
Description Condition: A cell serves HSUPA UEs and cell RTWP monitoring is
enabled on the RNC WebLMT.
Symptom: UL Required Load returns an inaccurate value.
Impact: The value of UL Required Load is smaller than expected.

Copyright © Huawei
Severity Minor
Root Cause The method of calculating UL Required Load is defective. As a result,

the calculated load on the data channel of HSUPA UEs is smaller than
actual load.
Solution The defective calculation method has been corrected.
Solution None
Impact
6.3.2.3.12 In MOCN scenarios, if licenses for other features are insufficient, ALM-26811
Configured Capacity Limit Exceeding Licensed Limit is reported from NodeBs of
available operators when the alarm should not.

Ticket
Number
Description Condition: The MOCN feature is activated, but the licenses for other
features are insufficient.
Symptom: ALM-26811 Configured Capacity Limit Exceeding Licensed
Limit is reported on the alarm console from NodeBs of available
operators.
Impact: This alarm is reported when it should not.
Severity Minor
Root Cause The alarm reporting mechanism is defective when the NodeB is
processing the license-related alarms with the MOCN feature enabled.
Solution The defect is now rectified.
Solution None
Impact
6.3.2.3.13 The Uplink CoMP (Joint Reception) feature is unusable.

Ticket
Number
Description Condition: The Uplink CoMP (Joint Reception) feature is activated for a
NodeB, but UlCoMP Algorithms Switch is not turned on for the primary
cell. The uplink resource group serving the primary cell includes UBBPd
and non-UBBPd boards.
Symptom: The primary cell is set up on the non-UBBPd board and

Copyright © Huawei
reports ALM-28206 Local Cell Capability Decline with the cause value
"The NodeB ULCoMP Group to which the cell belongs is unavailable".
Impact: The Uplink CoMP (Joint Reception) feature is unusable.
Severity Minor
Root Cause When a cell is configured into a UL CoMP group but UlCoMP
Algorithms Switch is not turned on for the cell, the downlink resource
allocation algorithm is defective. As a result, the cell cannot be set up on
the UBBPd board, which provides required resources for the Uplink
CoMP (Joint Reception) feature.
Solution None
Impact
6.3.2.3.14 The VS.ERACH.Thruput and VS.EFACH.Thruput counters return

"OverFlow".

Ticket
Number
Description Condition: A NodeB serves E-RACH and E-FACH UEs, and the
statistical values for both the VS.ERACH.Thruput and
VS.EFACH.Thruput counters are greater than one billion.
NOTE
 VS.ERACH.Thruput: indicates the throughput of E-RACH UEs.
 VS.EFACH.Thruput: indicates the throughput of E-FACH UEs.

Symptom: On the U2000, the VS.ERACH.Thruput and
VS.EFACH.Thruput counters return "OverFlow".
Impact: Users cannot obtain the actual throughput of these UEs.
Severity Minor
Root Cause The scenario where the statistical value is greater than one billion is not
considered in counter design.
Solution The VS.ERACH.Thruput and VS.EFACH.Thruput counters are now
changed as overrun counters.
Solution None
Impact

Copyright © Huawei
6.3.2.3.15 In specific scenarios, the NodeB performance counters using units of dBm and
dB return an inaccurate value of 0.
Trouble DTS: CRNPC9124

Ticket
Number
Description Condition: A measurement object is configured but unavailable, or it is

configured and available but no conditions are met for counters to be
valid.
Symptom: The performance counters using units of dBm and dB return a
value of 0. Some of the counters include:
VS.MeanRTWP.Locell.SectorEqm.Ant0
VS.MinRTWP.Locell.SectorEqm.Ant0
VS.HSUPA.10msTTI.CCHOLPC.SIRTargetDec.Mean
VS.HSUPA.2msTTI.CCHOLPC.SIRTargetDec.Mean
Impact: The value 0 indicates 0 dBm or 0 dB, which is meaningful and
misguides users.
Severity Minor
Root Cause Counters using units of dBm and dB are not differentiated from those
using other units in specific scenarios.
Solution Counters using units of dBm and dB now return a value of NIL in
specific scenarios.
Solution None
Impact
Test Case ID ATP-NPC9124
6.3.2.3.16 The alarm cause for ALM-28203 Local Cell Unusable is inaccurate

Ticket
Number
Scenario 1: All downlink channels of the RF unit used by a local cell are
unavailable. The uplink frequency or both uplink and downlink
frequencies are not within the working frequency band of the RF unit.
Scenario 2: All uplink channels of the RF unit used by a local cell are

Copyright © Huawei
unavailable. The downlink frequency or both uplink and downlink

frequencies are not within the working frequency band of the RF unit.
Symptom:
Scenario 1: When the local cell becomes unavailable, the NodeB reports
one ALM-28203 Local Cell Unusable alarm with the cause value of
Downlink RF Resource Unavailable.
Scenario 2: When the local cell becomes unavailable, the NodeB reports
one ALM-28203 Local Cell Unusable alarm with the cause value of
Uplink RF Resource Unavailable.
Impact: In the preceding two scenarios, both the alarm causes are
inaccurate.
Severity Minor
Root Cause The NodeB incorrectly determines the cause value for ALM-28203 Local
Cell Unusable.
Solution The NodeB now correctly determines the cause value for ALM-28203
Local Cell Unusable.
Solution None
Impact
6.3.2.4 Suggestion
6.3.2.4.1 After the FDE feature is activated, throughput of UEs occasionally decreases.

Ticket
Number
Description Condition: The NodeB is configured with the WBBPf or UBBPd board,
and the FDE feature is activated for the NodeB.
Symptom: Throughput of HSUPA UEs occasionally decreases.
Impact: The FDE feature does not provide significant gains or even
causes adverse impacts.
Severity Suggestion
Root Cause FDE algorithm calculations on the WBBPf or UBBPd board are
incorrect. As a result, the FDE feature alternately takes effect and
becomes ineffective, causing user throughput to fluctuate.
Solution FDE algorithm calculations have been corrected on the WBBPf or
UBBPd board.
Solution None
Impact

Copyright © Huawei
6.3.2.4.2 If a DC UE accesses a cell in the handover area access time, there is a low
probability that radio link reconfiguration fails due to NodeB resource insufficiency.

Ticket
Number
Description Condition: The WBBPb board provides uplink baseband resources for a
DC UE, which accesses a cell in the handover area.
Symptom: Radio link reconfiguration fails due to NodeB resource
insufficiency.
Impact: The RAB assignment success rate decreases.
Severity Suggestion
Root Cause The radio link reconfiguration procedure is defective.
Solution None
Impact
6.3.2.4.3 Counters related to power performance in a MOCN network return incorrect

values.

Ticket
Number
Description Condition: The MOCN Introduction Package feature is enabled, but the
MOCN Cell Resource Demarcation feature (including HSDPA power
allocation and total downlink power allocation) is disabled.
Symptom:
The following counters all return 0:
 VS.HSDPAPwrRatio.SharedOperator0
 VS.DLDCHPwrRatio.SharedOperator0
Impact: MOCN performance cannot be accurately evaluated on a
preliminary basis.
Severity Suggestion

Copyright © Huawei
Root Cause In the preceding scenario, the NodeB does not support measurement of
counters related to power performance in a MOCN network.
Solution The NodeB now supports measurement of counters related to power
performance in a MOCN network.
Solution None
Impact
6.3.2.4.4 DC capability derating occasionally occurs after the NodeB is upgraded or

restarted, or a NodeB application is restarted.

Ticket
Number
Description Condition: The NodeB serves DC cells. After the NodeB is upgraded or
restarted, or a NodeB application is restarted, downlink recourses of DC
cells are provided by different baseband processing units.
Symptom: The NodeB reports ALM-28206 Local Cell Capability
Decline with the alarm cause "DC not supported by the cell."
Impact: The DC function fails.
Severity Suggestion
Root Cause In the preceding scenario, the NodeB allocates resources to local cells
when resources of some baseband processing units are unavailable.
Solution The NodeB now allocates resources to local cells when resources of all
baseband processing units are available to ensure that the downlink
resources of DC cells are provided by the same baseband processing unit.
Solution None
Impact
6.3.2.4.5 The WBBPd or WBBPb board reports ALM-28209 Cell No Traffic when it
should not.

Ticket
Number
Description Condition: The WBBPb or WBBPd board serves a cell.

Symptom: There is a low probability that ALM-28209 Cell No Traffic is
reported when it should not be.

Copyright © Huawei
Impact: Ongoing services are not affected.

Severity Suggestion
Root Cause A threshold of detecting the number of acquisition indications (AIs) is

not configured for no-traffic detection scenarios. As a result, the no-
traffic detection result is incorrect.
Solution The threshold of detecting the number of AIs has been added in no-traffic
detection scenarios.
Solution None
Impact
6.3.2.4.6 The interface values of parameters in the Dynamic Power Sharing in Multi-
Carriers feature are inconsistent with those of parameters in the HSDPA Inter-Cell
Power Sharing feature.

Ticket
Number
Description Interface values of parameters are inconsistent between the Dynamic

Power Sharing in Multi-Carriers feature and the HSDPA Inter-Cell Power
Sharing feature.
Severity Suggestion
Root Cause The parameter setting interface for the HSDPA Inter-Cell Power Sharing
feature is updated, which is different from that for the Dynamic Power
Sharing in Multi-Carriers feature.
Solution The parameter setting interface for the Dynamic Power Sharing in Multi-
Carriers feature is now modified to be consistent with that for the HSDPA
Inter-Cell Power Sharing feature.
Solution The parameter setting interface for the Dynamic Power Sharing in Multi-
Impact Carriers feature and the maximum power sharing ratio are adjusted.
6.3.2.4.7 The preemption success rate is low and the PS service drop rate is high when
the NodeB CE resource preemption function is enabled on the RNC.
Trouble Ticket DTS: CRNP2203A

Number
Description When the NodeB CE resource preemption function is enabled on the

RNC, the preemption success rate is low and the PS service drop
rate is high.

Copyright © Huawei
Severity Suggestion
Root Cause The NodeB CE resource preemption algorithm is defective.
Solution The NodeB CE resource preemption algorithm is now optimized.
Solution Impact The success rate of CE resource preemption increases and the PS
service drop rate decreases.
Test Case ID ATP-NP2203A
6.3.2.4.8 DSP load values of the WBBPd and WBBPf boards are different between
BTS3900 V100R010C10 and BTS3900 V100R010C00SPC010 when no service is running.

Number
Description When no service is running, the following DSP load values are
different between BTS3900 V100R010C10 and BTS3900
V100R010C00SPC010:
 DSP 0 and DSP 1 of the WBBPd board
 DSP 0 of the WBBPf board
Severity Suggestion
Root Cause In the preceding scenario, the preceding DSP load values are
optimized in BTS3900 V100R010C10.
Solution This issue does not affect services and no operations are required.
Solution Impact None
6.3.2.4.9 In specific scenarios, values are inconsistent between the performance counters
measuring the maximum, minimum, and average statistical values for a measurement
object.
Trouble DTS: CRNPC9124

Ticket
Number
Description Condition: A measurement object is configured but unavailable, or it is

configured and available but no conditions are met for counters to be
valid.
Symptom: For a measurement object, the counters measuring the
maximum and minimum statistical values are 0 but the counter
measuring average statistical value is NIL. Some counters encounter this
issue and the following are examples:
 VS.PdschCodeUsed.Max, VS.PdschCodeUsed.Min, and
VS.PdschCodeUsed.Mean

Copyright © Huawei
 VS.HSUPA.AGCHCodeUtil.Max and
VS.HSUPA.AGCHCodeUtil.Mean
 VS.DlCode.Used.Max and VS.DlCode.Used.Mean
Impact: Values are inconsistent between the performance counters
measuring the maximum, minimum, and average statistical values for a
measurement object.
Severity Suggestion
Root Cause In specific scenarios, the NodeB uses different mechanisms to process the
performance counters measuring the maximum, minimum, and average
statistical values for a measurement object.
Solution In specific scenarios, the maximum, minimum, and average statistical
values for the same measurement are NIL.
Solution None
Impact
Test Case ID ATP-NPC9124
6.3.2.4.10 The ULK USR command cannot be executed on the WebLMT.

Number
Description Condition: The WebLMT is used for login to the NodeB.

Symptom: A user cannot directly run the ULK USR command on the
WebLMT but can successfully run the command after modifying
source codes of the web page.
Impact: The ULK USR command cannot be executed.
Severity Suggestion
Root Cause This command is restricted for UMTS only base stations and therefore
cannot be delivered to the NodeB through the WebLMT.
Solution The ULK USR command is now added and applicable to UMTS only
base stations through the WebLMT.
Solution None
Impact
6.3.2.4.11 Some counters in the HSDPA function subset return incorrect values.

Ticket
Number
Description Condition: The Downlink Enhanced CELL_FACH or Enhanced

Copyright © Huawei
CELL_PCH feature is activated for a cell, and the cell serves E-FACH or
E-PCH UEs.
Symptom: In the HSDPA function subset, some counters return incorrect
values. Some of the counters include:
VS.HSDPA.All.ScheduledNum
VS.ScchCodeUtil.Mean.User
VS.ScchCodeUtil.Mean.Data
VS.DataDiscardRatio.Max
VS.DataDiscardRatio.Min
Impact: The counters return incorrect values.
Severity Suggestion
Root Cause When the Downlink Enhanced CELL_FACH or Enhanced CELL_PCH

feature is activated, E-FACH or E-PCH UEs are counted in the preceding
counters.
Solution The preceding counters now do not count E-FACH or E-PCH UEs when
the Downlink Enhanced CELL_FACH or Enhanced CELL_PCH feature
is activated.
Solution None
Impact
6.3.2.4.12 Some counters in the HSUPA function subset return incorrect values.

Ticket
Number
Description Condition: The Uplink Enhanced CELL_FACH feature is activated for a

cell and the cell serves E-RACH UEs.
Symptom: In the HSUPA function subset, some counters return incorrect
values. Some of the counters include:
VS.HSUPA.UnHappyUserNum
VS.HSUPA.UnHappyUserNumRatio
VS.HSUPA.DataTtiNum
VS.HSUPA.ACKTotal
VS.HSUPA.NACKTotal
Impact: The counters return incorrect values.
Severity Suggestion
Root Cause When the Uplink Enhanced CELL_FACH feature is activated, E-RACH
UEs are counted in the preceding counters.
Solution The preceding counters now do not count E-RACH UEs when the Uplink
Enhanced CELL_FACH feature is activated.

Copyright © Huawei
Solution None
Impact
6.3.3 Known Issues

None

Copyright © Huawei

V100R010C10
7.1 Change Summary

Compared with those in V100R008C00SPC300, capacity increases and performance
improves in V100R010C10 if the UBBPd board is used, and capacity and performance
remain unchanged in V100R010C10 if the UBBPd board is not used. For details, see 7.1.1
Capacity and Performance. In addition, V100R010C10 introduces the BBU3910 subrack,
which provides the same capacity and performance as the BBU3900 subrack.
Hardware
Compared with those in V100R008C00SPC300, 0 board types have been added to and 0
board types have been modified in V100R010C10. For details, see 7.1.2 Hardware.

Compared with those in V100R008C00SPC300, 0 features and functions have been added, 0
features and functions have been modified, and 0 features and functions have been deleted in
V100R010C10. 7.1.3 Features and Functions provides the following information about new
or modified features and functions:
Resolved issues
issues, and 48 suggestion-level issues have been resolved in V100R010C10. 7.1.4 Resolved
Issues provides the following information about resolved issues:

Copyright © Huawei


remain unchanged in V100R010C10. For details about MML command and parameter
remain unchanged in V100R010C10. For details about counter changes, see 8.5 Counter
Changes.
unchanged in V100R010C10. For details about alarm and event changes, see 8.3 Alarm
unchanged in V100R010C10. For details about license changes, see 8.6 License
Changes.
templates have changed in V100R010C10. For details, see 7.1.6 Related Documentation.

Compared with V100R008C00, V100R010C10 introduces the UBBPd board. The UBBPd
board can serve more cells and the new features specific to the UBBPd board provide
significant improvements in capacity and performance.
 Specification improvement
UBBPd1, UBBPd2, UBBPd3, UBBPd4, UBBPd5, and UBBPd6 boards are added. The
following table describes the number of cells, uplink CEs, and downlink CEs supported
by each board type. Note that the interface board must be one of the UBBPd series
boards when the UBBPd6 supports 12 2T cells.
Board Number of Cells Number of Uplink Number of

CEs Downlink CEs
UBBPd1 6 384 512

UBBPd2 6 512 768
UBBPd3 6 384 512

Copyright © Huawei
Board Number of Cells Number of Uplink Number of

CEs Downlink CEs
UBBPd4 6 512 768

UBBPd5 6 768 768
UBBPd6 12 1024 1024
UBBPd series boards each support a maximum of 192 HSPA users in a cell.
UBBPd series boards each support a maximum of 768 HSDPA or HSUPA users, as
described in the following table.
Board Number of Number of HSUPA Number of HSUPA

HSDPA Users Users (10 ms TTI) Users (2 ms TTI)
UBBPd1 288 288 288

UBBPd2 384 384 384
UBBPd3 288 288 288
UBBPd4 384 384 384
UBBPd5 512 512 512
UBBPd6 768 768 768
CE consumption improvement: If an uplink resource group uses 4 RX channels and the

spreading factor (SF) of users allocated to a UBBPd board is SF32, SF64, or SF128, the
same uplink CE consumption rules apply when 4 RX channels or 2 RX channels are used.
Therefore, using UBBP boards for capacity expansion and new site deployment of sites
with 4 RX channels help reduce uplink CE consumption.
Spreading Factor UBBPd (2 RX UBBPd (4 RX WBBPf (4 RX

Channels) Channels) Channels)
SF128 1 1 2
SF64 1 1 2
SF32 1 1 2

Only the UBBPd board supports interference cancellation, interference suppression,
multi-antenna combination, and decoding enhancement. The following features,

Copyright © Huawei
supported only on UBBPd boards, help improve uplink capacity and throughput.
Control Channel Parallel Interference Cancellation (Phase 3) (applicable to HS-DPCCH
and E-DPCCH IC scenarios)Uplink Interference Rejection CombiningUplink CoMP
(Joint Reception) Based on the UBBPTurbo IC Phase 2
7.1.2 Hardware
New Hardware
Compared with V100R008C00SPC300, V100R010C10 adds hardware types listed in Table 1-
1.
Hardwar Hardwar Function Description

e Type e Name
Subrack BBU3910  The BBU3910 subrack does not support D series RXU
modules.
 The BBU3910 subrack supports only the following: UMPTb,
UBBPd, USCU, UCIU, UTRPc, UBRIb, UTRPa, UEIU,
UPEU (650 W), fan module (9000 revolutions per minute)
and later boards.
 The BBU3910 subrack supports cabinets including the
BTS3900 (Ver.D), BTS3900A (Ver.D), BTS3900L (Ver.D),
APM30H (Ver.D), TMC11H (Ver.D), OMB (Ver.C), IMB03,
BTS3900C (Ver.C), BTS3900AL (Ver.A), and virtual cabinet
(VIRTUAL).
 Compared with the BBU3900 subrack, the BBU3910 is under
no restrictions on slots for proving CPRI ports and supports a
maximum of 36 CPRI optical ports.
Board UBBPd1 It is a multimode baseband processing unit featuring low
specifications and supports GO, UO, and GU.
Board UBBPd2 It is a multimode baseband processing unit featuring low
specifications and supports GO, UO, and GU.
Board UBBPd3 It is a multimode baseband processing unit featuring medium
specifications and supports GO, UO, FDD LO, GU, and GL.
In GL mode, the board supports both GSM and LTE FDD at the
same time.
specifications and supports GO, UO, FDD LO, TDD LO, GU,
and GL.
same time.
and GL.

Copyright © Huawei
Hardwar Hardwar Function Description

e Type e Name
same time.
Board UBBPd6 It is a multimode baseband processing unit featuring high
GL, UL, and GUL.
same time.
In UL mode, the board supports both UMTS and LTE FDD at
the same time.
In GUL mode, the board supports GSM, UMTS, and LTE FDD
at the same time.
Board UTRPa It provides eight E1/T1 ports, implements inverse multiplexing
and de-multiplexing of a single ATM cell flow over eight E1/T1
links, performs framing and deframing for High-Level Data Link
Control (HDLC) frames, and allocates and controls the 256
HDLC timeslot channels.
For more details, see section 8.2.5.
Board UMDU
Modified Hardware
None
Deleted Hardware
None

V100R010C10 to V100R008C00SPC300:
 Change type
 (Optional) RAT
V100R010C10 (NodeB).xlsx.
For features changes, see 7.2 Feature and Function Changes.

Copyright © Huawei

This section provides the following aspects of issues resolved in BTS3900 V100R010C10 but
unresolved in BTS3900 V100R008C00SPC300:
 Severity
 Solution impact
 (Optional) RAT
For details about these issues, see Summary of Resolved Issues in BTS3900 V100R010C10
(NodeB).xlsx
For Resolved Issues, see 7.3 Resolved Issues.

unchanged in V100R010C10. For details about changes to MML commands and parameters,
see 8.1 MML Command Changes and 8.2 Parameter Changes.

unchanged in V100R010C10. For details about counter changes, see 8.5 Counter Changes.

unchanged in V100R010C10. For details about changes to alarms and events, see 8.3 Alarm

unchanged in V100R010C10. For details about changes to license control items, see 8.6
License Changes.

Version
3900 Series Base This document describes the MO (For Customer)3900

Station MO and and parameter, related MML Series Base Station
Parameter Reference command, and value range. Product
has been added. Documentation(V100R01

Copyright © Huawei

Version
3900 Series Base 3900 Series Base Station 0C10_Draft A)(HDX)-EN

Station Parameter Parameter Reference is split into
Reference has been the 3900 Series Base Station MO
deleted. and Parameter Reference.
3900 Series Base 3900 Series Base Station MO
Station MO Reference Reference is split into the 3900
has been deleted. Series Base Station MO and
Parameter Reference.
DBS3900(BBU3910A) This document describes how to
Installation Guide has install the cabinets, boards,
been added. modules, and cables for the
DBS3900 (BBU3910A) in outdoor
AC and outdoor DC scenarios. It
also provides checklists for
hardware installation.
has been added. cables of the RRU3952(850M).
Installation Guide has installation procedures and
been added. methods of the RRU3952(850M).
RRU3953&RRU3953w This document describes the
has been added. cables of the
RRU3953&RRU3953w.
RRU3953&RRU3953w This document describes how to
Installation Guide has install the RRU3953&RRU3953w.
been added.
RRU3959&RRU3959w This document describes the
has been added. cables of the
RRU3959&RRU3959w.
RRU3959&RRU3959w This document describes how to
Installation Guide has install the RRU3959&RRU3959w.
been added.

Copyright © Huawei

Version

Maintenance Guide has maintenance of the RRU3168.
been added.
been added.
been added.
OPM50M User Guide This document describes the
has been added. exterior, function, ports, and
installation and maintenance
procedures of the OPM50M.

Copyright © Huawei

Version
Hybrid Cable Assembly A hybrid cable assembly is an

Deployment Guide has integrated cable consisting of
been added. optical cables and electrical cables.
In a distributed base station, the
BBU can connect to RRUs by
using hybrid cable assemblies to
transmit baseband signals, and the
DCDU-12B can connect to RRUs
by using hybrid cable assemblies
to provide power for RRUs. This
document describes the functions,
characteristics, structure, and
technical specifications of the
hybrid cable assembly. It serves as
a guidance in installing and
maintaining the hybrid cable
assembly.
Changed the name of The product name is changed.
LampSite Technical
Description to
DBS3900 LampSite
Technical Description.
Changed the name of
LampSite
Configuration
Principles to DBS3900
LampSite
Configuration
Principles.
Changed the name of
LampSite Hardware
Description to
DBS3900 LampSite
Hardware Description.
Changed the name of
Guide to DBS3900
Guide.
Changed the name of
LampSite Hardware
Maintenance Guide to
DBS3900 LampSite
Hardware Maintenance
Guide.

Copyright © Huawei

Version
DBS3900 LampSite This document describes the

Spare Parts Catalog details on the spare parts for
has been added. DBS3900 LampSite.
Outdoor Adjusted The Outdoor Adjusted Plinth
Plinth (Width of 600 (width of 600 mm) is no longer
mm) Installation Guide delivered and will be switched to
has been deleted. the OAP800.
Combined Parameter Redundant information was BTS3900 V100R010C10
Reference and MO removed from MO Reference and Reference-EN
Reference into MO and Parameter Reference. To help the
Parameter Reference. customer better understand the
relationships between MOs and
Incorporated the Reorganized the documents based
following documents of on the base station resource model
the BTS3900, BTS3900 to present a clear view of
WCDMA, and comparison between different
BTS3900 LTE into one types of NEs. You can choose to
document: MML view information of base stations
Command Reference, supporting one or multiple modes,
MO and Parameter including G, U, L, GU, GL, UL,
Reference, Alarm and GUL, to easily compare
Reference, Event different modes.
Reference, and
Performance Counter
Reference. This
document contains four
parts (Node,
GBTSFunction,
NodeBFunction, and
eNodeBFunction) and
the Applicable Mode
document for easy
identification.

Copyright © Huawei

Version
 Added Release Notes The readability of Release Notes BTS3900 V100R010C10
in CHM format. was enhanced. Release Documents-EN
 Added Summary of
Resolved Issues and
Summary of Feature
ChangesinExcel
format.
 Divided the Resolved
Issues section by
severity.
Incorporated delta Reorganized the documents based
documents and disuse on the base station resource model
lists of the BTS3900, to present a clear view of
BTS3900 WCDMA, comparison between different
and BTS3900 LTE into types of NEs. You can choose to
one document. This view information of base stations
document contains four supporting one or multiple modes,
parts (Node, including G, U, L, GU, GL, UL,
GBTSFunction, and GUL, to easily compare
NodeBFunction, and different modes.
eNodeBFunction) and
the Applicable Mode
document for easy
identification.
Added the following  The change information about
columns to the MO and recommended values was
Parameter Changes provided for the customer to
template: adjust the configuration
Recommended Value according to the change in time.
(New), Recommended  The customer can learn about
Value (Old), Feature feature changes on a per feature
ID, and Feature Name. basis.
Added Disuse Each parameter to be disused is
Parameter List, deleted described independently.
the disuse information Meanwhile, parameters to be
from MO and disused are clearly distinguished
Parameter Changes, from those to be deleted from delta
and deleted the Disuse documents.
Statement column
from Parameter
Reference.

Copyright © Huawei

Version
 Divided the Change  The column was divided based
Description column on different customer groups,
into multiple so that different customer
columns by groups can quickly find the
category in the content they want.
Alarm Changes and  The meanings of the fields are
Event Changes clearer, which makes it easy for
templates. users to understand.
 Divided the Impact
on NBI Data
column into the
Involve the NBI
and Compatible
with the NBI
columns in the
Alarm Changes and
Event Changes
templates.
Added Disuse Alarm Disuse alarms and events were
List and Disuse Event separately listed to clearly
List. Removed disuse distinguish from deleted alarms
information from and events in Delta documentation.
Alarm Changes and
Event Changes.
Divided the Impact on The meanings of the fields are
NBI Data column into clearer, which makes it easy for
the Involve the NBI users to understand.
and Compatible with
the NBI columns in the
Performance Counter
Changes template.
Added Disuse Disuse performance counter was
Performance Counter separately listed to clearly
List. Removed disuse distinguish from deleted
information from performance counter in Delta
Performance Counter documentation.
Changes.
7.2 Feature and Function Changes

Feature updates from V100R009C00SPC180 to V100R010C00SPC150, refer to section 6.1.3
Features and Functions.
Feature updates from V100R008C00SPC300 to V100R009C00SPC180, refer to section of
below:

Copyright © Huawei
7.2.1 New Features and Functions

7.2.1.1 UL CE Resource Pool for 12 Cells
Description
To cope with soaring traffic volume, operators have used a greater amount of UTRA absolute
radio frequency channel numbers (UARFCNs) and deployed three-carrier or four-carrier
sectors on UMTS networks. With a typical three-sector configuration, the NodeB can serve 9
or 12 cells. The original baseband processing unit of the NodeB provides an uplink resource
pool for a maximum of 6 cells. To serve more cells, the NodeB must be configured with
multiple uplink resource pools, but these pools cannot share channel elements (CEs).
Huawei presents a new baseband processing unit, the UBBPd, which provides an uplink CE
pool for a maximum of 12 cells.
Implementation
The UBBPd enables demodulation and decoding for 12 two-antenna cells on one board.
When using only the UBBPd board, an uplink resource group (uplink baseband equipment)
supports an uplink CE pool for a maximum of 12 cells.
When using both the UBBPd board and another type of baseband processing unit, an uplink
resource group (uplink baseband equipment) supports an uplink CE pool for a maximum of 6
cells. In this situation, activate the WRFD-151210 Inter-Dependence of BBU Uplink
Resource feature to enable the uplink baseband equipment to support an uplink CE pool for a
maximum of 12 cells.

The UL CE Resource Pool for 12 Cells feature promotes uplink CE sharing and reduces the
incidence of rejected access requests due to insufficient uplink CEs, thereby increasing the
radio access success rate. This feature also enables the UTRAN to serve more users provided
that other types of network resources are sufficient. The number of admitted users will not
change once this feature is activated because the number of users remains the same.
Impact on NEs
None
Impact on Hardware
This feature requires use of the UBBPd board.

None

 Impact on license
N/A

Copyright © Huawei
Run the ADD BRD command to add the UBBPd board. In this step, set the baseband
working mode to a combination that involves UMTS and configure relevant hardware
capabilities. Then run the ADD BASEBANDEQM command to add two or more
UBBPd boards to the uplink resource group (uplink baseband equipment). Establish
local cells in the uplink resource group, which supports an uplink CE pool for a
maximum of 12 cells.
N/A
If a WBBPa, WBBPb, WBBPd, or WBBPf board is added to an uplink resource group
(uplink baseband equipment) that has been configured with only the UBBPd board, the
UBBPd board will not be used, and ALM-28350 Board Configuration Inconsistent with
Resource Group Configuration will be reported.

None
Related Operations
None

IR-V100R009-043
7.2.1.2 Improved Downlink Throughput
Description
Improved downlink throughput includes two new functions: HSDPA inter-cell power sharing
and enhanced HSDPA code utilization.
 HSDPA inter-cell power sharing
When a power amplifier (PA) serves multiple HSDPA cells, an HSDPA cell can
dynamically use the available power resources of another HSDPA cell. This power
sharing mode increases PA utilization and HSDPA service rate, thereby improving user
experience.
 Enhanced HSDPA code utilization
The resource allocation policy is enhanced in the MAC-(e)hs scheduling entity;
specifically, the NodeB preferentially allocates codes on condition that cell capacity does
not decrease, thereby reducing power consumption. Enhanced HSDPA code utilization
lowers downlink load and improves downlink channel quality, and therefore improves
user experience. If the licensed HSDPA codes are insufficient, enabling the enhanced
HSDPA code utilization function may aggravate code resource congestion and reduce
cell capacity, even if the cell has remaining power resources. In this situation, it is good
practice to expand the capacity of licensed HSDPA codes and then enable the function.
Implementation

Copyright © Huawei
The implementation principle is shown in Figure 1-1. This example assumes that cell A
has HSDPA data to transmit with insufficient power resources while cell B has available
power resources. In this situation, cell B shares its power resources with cell A. When
HSDPA data transmission in cell A is complete, cell B reclaims the shared power
resources. If cell B has HSDPA data to transmit while HSDPA data transmission in cell A
is in progress, cell B will instantly reclaim the shared power resources to provide
continued user experience.
The power sharing groups (such as cell A and cell B) are configured using the ADD
NODEBPAGRP command. In the parameter settings, set the Power Share Method
parameter to HCELLTOHCELL. The Max Sharing Power Ratio parameter indicates
the maximum ratio of available power that can be shared to the maximum transmit
power of the cell. The Sharing Power Margin parameter indicates the proportion of
reserved power for sharing to the maximum transmit power in the source cell.
Figure 1.1 Dynamic power sharing between HSDPA cells

To enable the enhanced HSDPA code utilization function, run the SET
ULOCELLMACHSPARA command with the Resource Allocate Method parameter
set to POWERCODE_BAL and the Code Utilization Optimization Switch parameter
set to ON. This function requires HSDPA-capable UTRAN and UEs, but is not
applicable to MIMO-enabled UEs or UEs enabled with the HS-SCCH less operation
function.

Capacity

Copyright © Huawei
− If this function is used for cells with light traffic, both power resource utilization and
average user throughput are increased. When the Max Sharing Power Ratio
parameter is set to a value ranging from 40% to 50%, average user throughput is
increased by approximately 5% to 10% and average edge user throughput is
increased by greater than 10%.
− If this function is used for cells with heavy traffic, average user throughput does not
increase because such cells have high power resource utilization and few available
resources.
− It is recommended that this function be disabled for cells with long periods of traffic
imbalance. If this function is used between a cell with light traffic (cell A) and a cell
with heavy traffic (cell B) with long periods of traffic imbalance between the two,
cell A always shares power resources with cell B. In this situation, average user
throughput in cell A may deteriorate.
− This function does not yield gains for multi-carrier users when the power sharing cell
groups belong to the same multi-carrier cell group, because multi-carrier users can
use available resources of multiple carriers. Since the multi-carrier user penetration
rate has increased on live networks, gains yielded by this function have been
declining.
− It is recommended that this function be disabled for delay-sensitive services, such as
ping services. If this function is enabled for small-traffic services or ping services, the
data transmission duration is very short and therefore the shared power resources
cannot be reclaimed in a timely manner. As a result, the service rate on the air
interface is lowered and the delay is prolonged.
Performance
− This function increases the average HS-PSDCH data transmission power by
approximately 10% to 20% and the average cell load by 2% to 5%.
− The CS/PS call drop rate and CS/PS RAB setup success rate may deteriorate to some
extent due to increased downlink cell load and increased downlink inter-cell
interference. The rate of deterioration depends on user distribution and service
models on live networks. If the deterioration is greater than expected, lower the value
of the Max Sharing Power Ratio parameter. (Reference values: When the Max
Sharing Power Ratio parameter is set to 50%, the call drop rate increases by 0.01%
to 0.05% and the RAB setup success rate decreases by 0.03% to 0.05%.)
Capacity
− When code resources are sufficient, this function reduces downlink load and
downlink interference, thereby increasing downlink system capacity by
approximately 2% to 3%.
− When codes are insufficient for the NodeB (less than 10 codes per cell on average)
and code utilization for cells is high, this function may further increase code
utilization. In this situation, it is recommended that the capacity of licensed HSDPA
codes be expanded.
Performance
− Average HSDPA cell load is reduced by up to approximately 3%. When the HSDPA
user queue buffer has data to transmit, HS-PDSCH transmit power is reduced by
approximately 5% to 10%.
− When the HSDPA user queue buffer has data to transmit, HS-PDSCH code utilization
is increased by approximately 5% to 20%.
− The CS/PS call drop rate and CS/PS RAB setup success rate may increase slightly
due to the reduced downlink cell load.

Copyright © Huawei
Impact on NEs
None
Impact on Hardware
Dependency on NodeB hardware
3900 series base stations configured with the WBBPb, WBBPd, WBBPf, or UBBP board
support the enhanced HSDPA code utilization function.
The BTS3902E and BTS3803E support the enhanced HSDPA code utilization function.
The DBS3800, BTS3812E, BTS3812A, and BTS3812AE do not support the enhanced
HSDPA code utilization function.
3900 series base stations configured with the WBBPb, WBBPd, WBBPf, or UBBPd board
support the HSDPA inter-cell power sharing function. The following table describes RF units
that support this function:
RFU Radio Access Technology HSDPA Inter-cell Power

Sharing Support
WRFU UMTS Supported by BAND1 only

WRFUd UMTS Supported
WRFUe UMTS Supported
MRFU GSM, UMTS, LTE, GU, GL Not supported
MRFUd GSM, UMTS, LTE, GU, GL Supported
MRFUe GSM, UMTS, LTE, GU, GL Supported
RRU Radio Access Technology Power Sharing Support
RRU3804 UMTS Supported by BAND1 only

RRU3805 UMTS Not supported
RRU3806 UMTS Supported by BAND1 only
RRU3808 UMTS, LTE Not supported
RRU3824 UMTS Supported
RRU3832 UMTS, LTE, UL Supported

Copyright © Huawei
RRU Radio Access Technology Power Sharing Support
RRU3801E UMTS Supported by BAND1 only

RRU3908 GSM, UMTS, LTE, GU, GL Not supported
RRU3926 GSM, UMTS, GU Supported
RRU3928 GSM, UMTS, LTE, GU, GL Supported
RRU3929 GSM, UMTS, LTE, GU, GL, Supported
UL
RRU3942 GSM, UMTS, LTE, GU, GL, Supported
UL
The AAU3902 in the active antenna system (AAS) supports the HSDPA inter-cell power
sharing function.
The BTS3902E and BTS3803E support the HSDPA inter-cell power sharing function.
The DBS3800, BTS3812E, BTS3812A, and BTS3812AE do not support the HSDPA inter-
cell power sharing function.

None

Before enabling the HSDPA inter-cell power sharing function, run the LST ULOCELL
command to verify that the value of the GU Power Share Flag parameter is
FALSE(FALSE). If the parameter value is TRUE(TRUE), run the MOD ULOCELL
command with the GU Power Share Flag parameter set to FALSE(FALSE).
To enable the HSDPA inter-cell power sharing function, run the ADD NODEBPAGRP
command to configure the power sharing group. The following table describes the
parameters that must be set in the ADD NODEBPAGRP command:
Parameter Name Parameter ID Setting Notes
Power Share Method PWSHM Set this parameter to

HCELLTOHCELL(HS
DPA cell to HSDPA cell).
Source Local Cell ID SLOCELL Indicates the identity of
the source local cell that
enables bidirectional
power sharing with the

Copyright © Huawei
Parameter Name Parameter ID Setting Notes
local cell specified by the

Destination Local Cell
ID parameter. This
parameter takes effect
when the Power Share
Method parameter is set
to
HCELLTOHCELL(HS
Destination Local Cell ID DLOCELL Indicates the identity of
the destination local cell
that enables bidirectional
power sharing with the
local cell specified by the
Source Local Cell ID
parameter. This parameter
takes effect when the
Power Share Method
parameter is set to
HCELLTOHCELL(HS
Max Sharing Power Ratio MAXSHRTO Set this parameter to a
non-zero value. The
recommended value is 50.
Sharing Power Margin SHMGN Set this parameter to a
value greater than 10. The
recommended value is 15.
The source local cell and destination local cell specified in the parameters share available
power resources.
The SET ULOCELLMACHSPARA command on the NodeB side is used to configure the
enhanced HSDPA code utilization function. In this command, set the Resource Allocate
Method parameter to POWERCODE_BAL(Balance between Code and Power) and the
Code Utilization Optimization Switch parameter to ON(ON). The parameters are described
as follows:
No. MO NE Parameter Parameter ID

Name
1 ULOCELL NodeB Resource RSCALLOCM

MACHSPA Allocate
RA Method
2 ULOCELL NodeB Code CODEOPTSW
MACHSPA Utilization
RA Optimization
Switch

Copyright © Huawei

The new counter for the HSDPA inter-cell power sharing function is
VS.HSDPAPwrShare.TtiNum, indicating the number of TTIs when power sharing
persists between the HSDPA cells.
The new alarm for the HSDPA inter-cell power sharing function is as follows:
Alarm ID Alarm NE Feature ID Feature Name
Name
ALM-28207 Carrier Wave NodeB WRFD-010610 HSDPA Introduction

Share Failure Package

 HSDPA Inter-cell Power Sharing
Prerequisite Features
Mutually Exclusive Features
 WRFD-150236 Load Based Dynamic Adjustment of PCPICH
Do not enable the Load Based Dynamic Adjustment of PCPICH feature and the HSDPA
inter-cell power sharing function to work together. The Load Based Dynamic Adjustment
of PCPICH feature decreases the P-CPICH transmit power for cells with heavy traffic,
thereby increasing cell capacity. However, this feature reduces the Ec/No of users and
increases the call drop rate. The HSDPA inter-cell power sharing function increases the
maximum transmit power of cells with light traffic to improve user experience; however,
this function also reduces the Ec/No of users. If the Load Based Dynamic Adjustment of
PCPICH feature and the HSDPA inter-cell power sharing function are both enabled, the
call drop rate will deteriorate.
 WRFD-020116 Dynamic Power Sharing in Multi-Carriers
Do not enable the Dynamic Power Sharing in Multi-Carriers feature and the HSDPA
inter-cell power sharing function to work together.
 MRFD-221801 Multi-mode Dynamic Power Sharing(UMTS)
Do not enable the Multi-mode Dynamic Power Sharing(UMTS) feature and the HSDPA
inter-cell power sharing function to work together.
 WRFD-021304 RAN Sharing
The RAN Sharing feature is incompatible with the HSDPA inter-cell power sharing
function, because power sharing between two cells owned by different operators leads to
unfair power resource allocation.
Impacted Features
 WRFD-030010 CQI Adjustment Based on Dynamic BLER Target
The HSDPA inter-cell power sharing function causes variations in available HSDPA
resources. The CQI Adjustment Based on Dynamic BLER Target feature enables the
NodeB to dynamically select a proper BLER target for HSDPA users in a cell based on
available cell resources and channel quality fluctuations, thereby achieving optimal
throughput for HSDPA users. It is good practice to enable the HSDPA inter-cell power

Copyright © Huawei
sharing function and the CQI Adjustment Based on Dynamic BLER Target feature to
work together.
 WRFD-150235 DPCH Maximum Power Restriction
It is not recommended to configure the HSDPA inter-cell power sharing function and
DPCH Maximum Power Restriction feature to work together. When the cell load is high,
the DPCH Maximum Power Restriction feature restricts the downlink DPCH transmit
power and therefore users at the cell edge may experience downlink synchronization
failures. If the HSDPA inter-cell power sharing function and the DPCH Maximum Power
Restriction feature work together, the average cell load becomes even higher and users at
the cell edge are more likely to experience dropped calls.
 WRFD-010696 DC-HSDPA
 WRFD-150250 3C-HSDPA
 WRFD-150207 4C-HSDPA
The HSDPA inter-cell power sharing function does not yield gains for multi-carrier users
when the power sharing cell groups belong to the same multi-carrier cell group, because
multi-carrier users can use available resources of multiple carriers. Since the multi-
carrier user penetration rate has increased on live networks, gains yielded by this
function have been declining.
 WRFD-021311 MOCN
It is not recommended to configure the HSDPA inter-cell power sharing function and
MOCN feature to work together, because power sharing between two cells owned by
different operators leads to unfair power resource allocation.
 Enhanced HSDPA Code Utilization
None
Impacted Features
 WRFD-030011 MIMO Prime
 WRFD-010684 2x2 MIMO
 WRFD-010693 DL 64QAM+MIMO
 WRFD-010699 DC-HSDPA+MIMO
 WRFD-150223 4C-HSDPA+MIMO
 WRFD-150227 DB-HSDPA+MIMO
When one or more MIMO-related features are enabled and the last priority queue to be
scheduled is of the MIMO user type, the optimized HSDPA code utilization function
does not take effect. If the MIMO user proportion is high, gains yielded by the optimized
HSDPA code utilization function are decreased.
Related Operations
 HSDPA Inter-cell Power Sharing (Using MML Commands)
Step 1 Run the MOD ULOCELL command on the NodeB side with the GU Power Share Flag
parameter set to FALSE(FALSE).

Copyright © Huawei
Step 2 Run the MOD UCELLHSDPA command on the RNC side with the Offset of HSPA Total
Power parameter set to the recommended value.
Step 3 Run the SET ULOCELLMACHSPARA command on the NodeB side with the Power
Margin parameter set to the recommended value.
Step 4 Run the ADD NODEBPAGRP command on the NodeB side to configure the power sharing
group for the HSDPA inter-cell power sharing function. The following parameters must be
set: Power Share Method, Source Local Cell ID, Destination Local Cell ID, Max Sharing
Power Ratio, and Sharing Power Margin. The source local cell and destination local cell
specified in the parameters share available power resources.
----End
 Enhanced HSDPA Code Utilization (Using MML Commands)

Run the SET ULOCELLMACHSPARA command on the NodeB side with the Resource
Allocate Method parameter set to POWERCODE_BAL(Balance between Code and
Power) and the Code Utilization Optimization Switch parameter set to ON(ON).

IR-V100R009-077
7.2.1.3 Solution to Inconsistent License Sales and Control Strategies
Description
In versions earlier than V100R009, the licenses of some features are not verified. Because of
the wide use of features, V100R009 starts to verify the licenses of features. The features that
have been licensed are not affected. The features that have not been licensed require the
submission of purchase orders (POs) to obtain the required licensing. V100R009 adjusts the
feature license strategies as follows:
 If the license key file for versions earlier than V100R009 does not contain the required
license control item (such as WRFD-050501 Clock Sync on Ethernet in NodeB)or
control irrationality (such as,WRFD-030011 MIMO Prime), the feature license enters a
60-day grace period after an upgrade to V100R009 is complete. ALM-26811 Configured
Capacity Limit Exceeding Licensed Limit is reported during the grace period. When the
grace period expires, the feature fails.
 If a feature has a sales item but lacks the BBOM control item in a version earlier than
V100R009 (such as WRFD-040203 RRU Redundancy), the feature is still available after
an upgrade to V100R009 is complete. However, ALM-26811 Configured Capacity Limit
Exceeding Licensed Limit is reported prompting operators to supplement the required
license control item.
 If a feature is licensed on a per cell basis but available for all cells under a NodeB in
versions earlier than V100R009 (such as 2x2 MIMO), the feature is still available for all
cells under the NodeB after an upgrade to V100R009 is complete. In V100R009, ALM-
26811 Configured Capacity Limit Exceeding Licensed Limit is reported if the number of
local cells is greater than the licensed limit.
Implementation
WRFD-050501 Clock Sync on Ethernet in NodeB

Copyright © Huawei
The Clock Sync on Ethernet in NodeB feature is controlled by the "IP Clock Function(per
NodeB)" license. However, if the license key file for versions earlier than V100R009 does not
contain this license control item, the Clock Sync on Ethernet in NodeB feature is not under
license control. V100R009 strictly verifies licenses. If the license key file does not contain the
required license control item, the feature license enters a 60-day grace period after the
upgrade is complete. ALM-26811 Configured Capacity Limit Exceeding Licensed Limit is
reported during the grace period. If the Clock Sync on Ethernet in NodeB feature is enabled
and the licensed capacity for the feature is insufficient, apply for additional licenses through
the exception commercial license workflow (version upgrade and version control items are
incompatible). Marketing engineers and network design engineers will review the license
applications based on BOQ contract information. You can use the upgrade risk check package
on the U2000 to verify that the licensed capacity of "IP Clock Function(per NodeB)" is
sufficient.
WRFD-020119 Multi-Carrier Switch off Based on Power Backup
The Multi-Carrier Switch off Based on Power Backup feature is controlled by the "Multi-
Carrier Switch off Based on Power Backup(per NodeB)" license. However, if the license key
file in versions earlier than V100R009 does not contain this license control item, the Multi-
Carrier Switch off Based on Power Backup feature is not under license control. V100R009
strictly verifies licenses. If the license key file does not contain the required license control
item, the feature license enters a 60-day grace period after the upgrade is complete. ALM-
26811 Configured Capacity Limit Exceeding Licensed Limit is reported during the grace
period. If the Multi-Carrier Switch off Based on Power Backup feature is enabled and the
licensed capacity for the feature is insufficient, apply for additional licenses through the
exception commercial license workflow (version upgrade and version control items are
incompatible). Marketing engineers and network design engineers will review the license
applications based on BOQ contract information. You can use the upgrade risk check package
on the U2000 to verify that the licensed capacity of "Multi-Carrier Switch off Based on Power
Backup(per NodeB)" is sufficient.
GSM/UMTS Dual Mode Sector (per Sector)
The "GSM/UMTS Dual Mode Sector(per Sector)" license is a hardware license controlling
the number of sectors with the GSM/UMTS multimode function. However, if the license key
file in versions earlier than V100R009 does not contain this license control item, the number
of sectors with the GSM/UMTS multimode function is not under license control. V100R009
strictly verifies licenses. If the license key file does not contain the required license control
item, the feature license enters a 60-day grace period after the upgrade is complete. ALM-
26811 Configured Capacity Limit Exceeding Licensed Limit is reported during the grace
period. If the GSM/UMTS multimode sectors are enabled and the licensed capacity of
"GSM/UMTS Dual Mode Sector(per Sector)" is insufficient, apply for additional licenses
through the exception commercial license workflow (version upgrade and version control
items are incompatible). Marketing engineers and network design engineers will review the
license applications based on BOQ contract information. You can use the upgrade risk check
package on the U2000 to verify that the licensed capacity of "GSM/UMTS Dual Mode
Sector(per Sector)" is sufficient.
WRFD-010631 Dynamic Code Allocation Based on NodeB
The Dynamic Code Allocation Based on NodeB feature is controlled by the "HSDPA RRM
Package 1(per NodeB)" license. However, if the license key file in versions earlier than
V100R009 does not contain this license control item, the Dynamic Code Allocation Based on
NodeB feature is not under license control. V100R009 strictly verifies licenses. If the license
key file does not contain the required license control item, the feature license enters a 60-day
grace period after the upgrade is complete. ALM-26811 Configured Capacity Limit
Exceeding Licensed Limit is reported during the grace period. HSDPA throughput will

Copyright © Huawei
decline significantly if the licensed capacity of "HSDPA RRM Package 1(per NodeB)" is
insufficient for an HSDPA-enabled NodeB. In this situation, apply for additional licenses
through the exception commercial license workflow (version upgrade and version control
items are incompatible). Marketing engineers and network design engineers will review the
license applications based on BOQ contract information. You can use the upgrade risk check
package on the U2000 to verify that the licensed capacity of "HSDPA RRM Package 1(per
NodeB)" is sufficient.
Adding Licenses for Optional Features Without BBOM
The optional features without the base bill of material (BBOM) are listed as follows:
WRFD-040203 RRU Redundancy
WRFD-021308 Extended Cell Coverage up to 200 km
WRFD-050105 ATM Switching Based Hub NodeB
WRFD-010206 High Speed Access
WRFD-050425 Ethernet OAM
If one of the listed features is enabled in V100R009 and the licensed capacity for the feature is
insufficient, ALM-26811 Configured Capacity Limit Exceeding Licensed Limit is reported.
The feature is still available when the alarm is reported. In this situation, apply for additional
licenses through the exception commercial license workflow (version upgrade and version
control items are incompatible). Marketing engineers and network design engineers will
review the license applications based on BOQ contract information. You can use the upgrade
risk check package on the U2000 to verify that the licensed capacity for the feature is
sufficient.
WRFD-010684 2x2 MIMO
The 2x2 MIMO feature is controlled by the "MIMO Function(per Cell)" license. However, in
versions earlier than V100R009, the 2x2 MIMO feature is available for all cells if the value of
the "MIMO Function(per Cell)" license is greater than or equal to 1. In V100R009, ALM-
26811 Configured Capacity Limit Exceeding Licensed Limit is reported if the value of the
"MIMO Function(per Cell)" license is less than the number of local cells enabled with 2x2
MIMO. The 2x2 MIMO feature is still available when the alarm is reported. In this situation,
apply for additional licenses through the exception commercial license workflow (version
upgrade and version control items are incompatible). Marketing engineers and network design
engineers will review the license applications based on BOQ contract information. You can
use the upgrade risk check package on the U2000 to verify that the licensed capacity of
"MIMO Function(per Cell)" is sufficient.
WRFD-010700 Performance Improvement of MIMO and HSDPA Co-carrier
This feature is controlled by the Performance Improvement of HSDPA+MIMO Co-Carrier
Function(per Cell) license control item. In versions earlier than V100R009, if the licensed
value of this feature is greater than or equal to 1, all cells can use this feature. V100R009
change this license to depend on "WRFD-030011 MIMO Prime(per Cell)"license,and the
control item is "Intelligent Inteference Control IIC)" V100R009 compares the licensed value
of this feature with the number of cells that have “IIC” enabled,and the ALM-26811
Configured Capacity Limit Exceeding Licensed Limit is reported, with safe duration of 60
days in which the use of the feature is not restricted. If the "IIC" has been activated but the

Copyright © Huawei
License of "Performance Improvement of MIMO and HSDPA Co-carrier" is insufficient ,

customers need to add appropriate licenses before an upgrade.
WRFD-030011 MIMO Prime
This feature is controlled by the MIMO Prime(per Cell) license control item. In versions
earlier than V100R009, if the licensed value of this feature is greater than or equal to 1, all
cells within this NodeB can use this feature. V100R009 will change this control more strictly
based on each cell ,and change this license control item from MIMO Prime(per Cell) to the
depended "Virtual Antenna Mapping(VAM) "configuration on local cell.
V100R009 compares the licensed value of this feature with the number of cells that have
"Virtual Antenna Mapping(VAM)"enabled,and the ALM-26811 Configured Capacity Limit
Exceeding Licensed Limit is reported, with safe duration of 60 days in which the use of the
feature is not restricted. If the "Virtual Antenna Mapping(VAM) "has been activated but the
License of "MIMO Prime(per Cell)" is insufficient , customers need to add appropriate
licenses before an upgrade.
WRFD-140201 AMR Voice Quality Improvement Based on PLVA
The AMR Voice Quality Improvement Based on PLVA feature is controlled by the "AMR
Voice Quality Improvement Based on PLVA(per Cell)" license. However, in versions earlier
than V100R009, if the value of the "AMR Voice Quality Improvement Based on PLVA(per
Cell)" license is greater than or equal to 1, the AMR Voice Quality Improvement Based on
PLVA feature is available for all cells. In V100R009, ALM-26811 Configured Capacity Limit
Exceeding Licensed Limit is reported if the value of the "AMR Voice Quality Improvement
Based on PLVA(per Cell)" license is less than the number of local cells enabled with the
feature. The feature is still available when the alarm is reported. In this situation, apply for
additional licenses through the exception commercial license workflow (version upgrade and
version control items are incompatible). Marketing engineers and network design engineers
will review the license applications based on BOQ contract information. You can use the
upgrade risk check package on the U2000 to verify that the licensed capacity of "AMR Voice
Quality Improvement Based on PLVA(per Cell)" is sufficient.
Power License
The Independent Demodulation of Signals from Multiple RRUs in One Cell feature now
consumes power licenses in a different way. In versions earlier than V100R009, this feature
consumes power licenses based on the maximum transmit power configured for the local cell.
From V100R009 onwards, each RRU involved in this feature independently consumes power
licenses. After an upgrade, the license for this feature enters a grace period, which lasts 60
days. Services are not affected during the grace period. Therefore, if this feature is used,
check the license key for the NodeB before an upgrade. If the licensed value of this feature is
less than the value used, customers need to add appropriate licenses before the upgrade.
Multicarrier License
The Independent Demodulation of Signals from Multiple RRUs in One Cell feature now
consumes multicarrier licenses in a different way. In versions earlier than V100R009, each
cell with this feature enabled requires a multicarrier license (the license control item is named
local cell number). From V100R009 onwards, each RRU involved in this feature requires a
multicarrier license. After an upgrade, the license for this feature enters a grace period, which
lasts 60 days. Services are not affected during the grace period. Therefore, if this feature is
used, check the license key for the NodeB before an upgrade. If the licensed value of this
feature is less than the value used, customers need to add appropriate licenses before the
upgrade.
Flexible frequency bandwidth of UMTS carrier

Copyright © Huawei
After an upgrade to V100R009, if the minimum effective bandwidth is set to a value ranging
from 4.2 M to 4.8 M by running the SET FREQBWH command but the license for this
feature is not purchased, ALM-26811 Configured Capacity Limit Exceeding Licensed Limit is
reported before the appropriate licenses are added, and the feature enters a grace period,
which lasts 60 days. After the grace period expires, the minimum effective bandwidth does
not take effect, and the 5.0 MHz standard bandwidth is used.
Therefore, check the license key for the NodeB before an upgrade. If the licensed value of this
feature is less than the value used, customers need to add appropriate licenses before the
upgrade.

N/A
Impact on NEs
New licenses are allocated to NEs through the V100R009-compatible U2000.
Impact on Hardware
N/A

N/A

See Implementation.
N/A
N/A
N/A

See Implementation.
Related Operations
Use the upgrade risk check package on the U2000 to verify that the licensed capacity for
features is sufficient. If the licensed capacity is insufficient, obtain additional licenses and
distribute as necessary to NodeBs using the U2000.

IR-V100R009-099

Copyright © Huawei
7.2.1.4 Support for IKEv2 Reauthentication
Description
An IKEv2 reauthentication switch is added to the base station. If this switch is turned off, the
base station initiates IKEv2 reauthentication only when it receives a reauthentication
notification from the peer end. If this switch is turned on, the base station automatically
initiates IKEv2 reauthentication based on the smaller value between the configured
reauthentication period and the reauthentication period received from the peer end. In this
manner, the base station can periodically initiate IKEv2 reauthentication, improving the base
station security.
Implementation
The IKEv2 reauthentication switch and the reauthentication period parameters are added to
the base station.

None
Impact on NEs
None
Impact on Hardware
None

None

 License management
N/A
 Configuration management
The IKEv2 reauthentication switch and the reauthentication period parameters are added
to the base station.
 Performance management
None
 Fault management
None

None

Copyright © Huawei
Related Operations
When running the ADD IKEPROPOSAL command to add an IKE proposal during IPsec
configuration, set the REAUTH and REAUTHLT parameters to configure the IKEv2
reauthentication switch and period.

CR-SRAN90-01308141A
7.2.1.5 WRFD-160106 Fast Radio Bearer Setup
Description
When a UE is initiating service setup, the RNC initiates a fast RB setup procedure based on
the NodeB's capability cell load status during RB setup and sends an RB Setup message
instructs the UE to perform fast RB setup. Compared with the original RB setup procedure,
this feature reduces the RB setup delay by 100-300 ms.
Implementation
For details, see Fast Radio Bearer Setup Feature Parameter Description in RAN Feature
Documentation.

 Capacity
− CE resources, code resources, and power resources
During fast reconfiguration, original resources need to be retained when new
resources are occupied. Therefore, compared with synchronized reconfiguration, the
fast reconfiguration consumes one more set of CE resources, code resources, and
power resources from the time when a new link is successfully set up to the time
when the new link configurations take effect.
− Number of DCH, HSDPA, and HSUPA UEs
Compared with synchronized reconfiguration mode, fast reconfiguration mode retains
both the original and new link configurations. This indicates that two UEs are carried
on the NodeB.
− CNBAP resources
The NodeB retains both the original and new link configurations when triggering a
fast reconfiguration. As a result, fast reconfiguration mode doubles CNBAP resource
consumption compared with synchronized reconfiguration mode. For details about
the principles of CNBAP resource consumption, see NodeB Baseband Resource
Management Feature Parameter Description.
 Performance
The WRFD-160106 Fast Radio Bearer Setup feature reduces the RAB setup delay of a single
service by about 100 ms to 300 ms and the RAB setup delay of CS+PS combined services in
which the CS service is established after the PS service by about 100 ms to 500 ms. The
following factors affect the reduction in delays:
 SRB setup rate
 Downlink channel type

Copyright © Huawei
 Coverage area where a UE initiates a service

The better the coverage is, the more the delays are decreased.
 Size of a data package of the RADIO BEARER SETUP message caused by the type of
the service initiated by a UE
The larger the data package size is, the less the delays are decreased.
 Length of a data package of the RADIO BEARER SETUP message caused by the type
of the service initiated by a UE
In addition, compared with synchronized reconfiguration mode, the duration from the time
that the RNC sends the RADIO BEARER SETUP message to the time that the UE receives
the message is longer and the sending success rate is higher in weak coverage areas because
the UE can activate new link configurations upon receiving the RADIO BEARER SETUP
message. As a result, the RAB setup success rate increases. However, the RAB setup success
rate and the reduction in the RAB setup delay depend on the coverage.
Uplink data frames will not be sent if the UL FP Mode parameter of the typical signaling
radio bearer (SRB) is set to SILENT and no transport format indicator (TFI) exists for SRBs
over the Iub interface. In this case, only the uplink traffic over the Iub interface is reduced.
Impact on NEs
Impact on Hardware
UBBPd board.
The following base stations do not support this feature:
 BTS3812E
 BTS3812A
 BTS3812AE
 DBS3800 series base stations
 3900 series base stations in which the WBBPa board carries resource groups established
by cells

The Fast Reconfiguration Mode and Fast Reconfiguration Permission IEs are contained in the
RADIO LINK RECONFIGURATION PREPARE and RADIO LINK RECONFIGURATION
READY messages over the Iub interface, respectively.


Copyright © Huawei
Change Parameter ID MML Command NE Description

Type
New CellConnAlgoSwitc ADD RNC Fast RB Setup Switch

h=SINGLE_CS_RA UCELLCONNAL for a Single CS RAB
B_FAST_RB_SET GOPARA
UP_SWITCH MOD
UCELLCONNAL
GOPARA
h=SINGLE_PS_RA UCELLCONNAL for a Single PS RAB
B_FAST_RB_SET GOPARA
UP_SWITCH MOD
UCELLCONNAL
GOPARA
h=MULTI_RAB_F UCELLCONNAL for Combined Services
AST_RB_SETUP_ GOPARA
SWITCH MOD
UCELLCONNAL
GOPARA
New SpecUserFunction ADD UIMEITAC RNC Whether to enable the
Switch2=SPECUSE MOD UIMEITAC Fast Radio Bearer Setup
R_FAST_RBCFG_ feature for UEs using a
CMP_SWITCH certain TAC

Change Counter Name Measurement NE Description

Type Unit
New VS.RAB.AttEstabCS RAB.EstabCS.Cell RNC Number of CS

.FastSetup RAB Setup
Requests for Cell
(Fast Setup)
New VS.RAB.AttEstabPS. RAB.EstabPS.Cell RNC Number of PS
FastSetup RAB Setup
Requests for Cell
(Fast Setup)
New VS.MultiRAB.AttEst RAB.MultiRab.Cel RNC Number of CS
abCS.FastSetup l RAB Setup
Requests for
PS+CS Combined
Services for Cell
(Fast Setup)
New VS.RAB.SuccEstabC RAB.EstabCS.Cell RNC Number of

Copyright © Huawei

Type Unit
S.FastSetup Successful CS
RAB Setups for
Cell (Fast Setup)
New VS.RAB.SuccEstabP RAB.EstabPS.Cell RNC Number of
S.FastSetup Successful PS RAB
Setups for Cell
(Fast Setup)
New VS.MultiRAB.SuccE RAB.MultiRab.Cel RNC Number of
stabCS.FastSetup l Successful CS
RAB Setups for
PS+CS Combined
Services for Cell
(Fast Setup)

None

None
None
Impacted Features
 WRFD-010701 Uplink Enhanced CELL_FACH
As the WRFD-010701 Uplink Enhanced CELL_FACH feature consumes common
resources on the E-DCH and codes and signatures on the E-RGCH, the number of
HSUPA UEs supported in a cell is reduced. During the HSUPA service setup, the Fast
Radio Bearer Setup feature will also consume codes and signatures on the E-RGCH and
a set of dedicated resources on the E-DCH. Therefore, if the Uplink Enhanced
CELL_FACH feature is enabled, the fast RB setup application probability decreases in
scenarios where the E-DCH is used before and after the RB is set up. The threshold for
the fast RB setup application is 60% of the currently configured codes and signatures on
the E-RGCH. If more than 60% of codes and signatures on the E-RGCH are consumed,
fast reconfiguration mode is not supported. Fast reconfiguration mode can be supported
only after the proportion of consumed codes and signatures on the E-RGCH falls below
40%.
 WRFD-160103 Terminal Black List
When the WRFD-160103 Terminal Black List feature is enabled, the RNC can add some
UEs to the blacklist and prevent these UEs from using the Fast Radio Bearer Setup
feature.
 WRFD-140224 Fast CS Fallback Based on RIM

Copyright © Huawei
If the WRFD-140224 Fast CS Fallback Based on RIM feature is enabled during fast
radio bearer setup, the delay in RB setup can be reduced after the Fast Radio Bearer
Setup feature is activated, thereby reducing the access delay of CSFB UEs.
Related Operations
For details, see "Engineering Guidelines" in Fast Radio Bearer Setup Feature Parameter
Description of RAN Feature Documentation.

IR-V100R009-068
7.2.1.6 WRFD-160204 CS Voice Precise Power Contro
Description
This feature works as follows:
 ILPC optimization: This feature enhances multipath signal searching and optimizes
signal-to-interference ratio (SIR) estimation for more precise ILPC, thereby reducing the
demodulation threshold for uplink CS voice services and UE transmit power.
 OLPC optimization: This feature optimizes power control based on the bit error rate
(BER) and discontinuous transmission (DTX), so that power control during CS voice
service activation and deactivation is more adaptable to user behaviors and radio channel
conditions. This further reduces the demodulation threshold for uplink CS voice services
and for capacity improvement. Alternatively, this further reduces the uplink block error
rate (BLER), thereby improving the quality and capacity of CS voice services.
Implementation
For details, see CS Voice Precise Power Control Feature Parameter Description in RAN

 Capacity
This feature improves the mean opinion score (MOS) of voice services in a cell by 0.05
to 0.1 point or enhance the capacity of CS voice services in a cell by 5% to 10%.
 Performance
This feature improves the MOS of voice services in a cell by 0.05 to 0.1 point without
affecting network KPIs such as the call drop rate and access success rate.
Impact on NEs
 The optimized multipath searching and optimized SIR estimation, which belong to the
optimized ILPC, as well as the DTX power control, which belongs to the optimized
OLPC, are implemented on the NodeB.
 The OLPC based on BLER and BER, which belongs to the optimized OLPC, is
implemented on the RNC.

Copyright © Huawei
Impact on Hardware
For Macro and LampSite base stations,the optimized multipath searching function depends on
the UBBP board,the optimized SIR estimation function depends on the WBBPf board.

A proprietary interface is added to the Iub interface. A proprietary IE "ucSirDtxConst" is
added to the RADIO LINK SETUP REQEST, RADIO LINK ADDITION REQUEST, and
RADIO LINK RECONFIGURTION REQUEST messages transmitted from the RNC to the
NodeB.This IE is used for adjustment of SirTarget when the UE is in DTX mode.
No proprietary interface is added to the Iur interface. Therefore, these functions cannot be
implemented in inter-RNC scenarios.

This feature is subject to RNC-level license control on the RNC.
The MML commands in the following table have been introduced on the RNC side to
Change Type Command NE Description
New SET BSC6900 Use this command to

UCSVOICEPPC BSC6910 set parameters for
the CS voice precise
power control
feature of an RNC.
New LST BSC6900 Use this command to
UCSVOICEPPC BSC6910 query parameters for
the CS voice precise
power control
feature of an RNC.
The following table lists the new counters added on the RNC side.
Change Type Parameter ID MML Command Description
New LogicRncId(UMTS SET This new parameter

BSC6900,UMTS UCSVOICEPPC uniquely specifies a
BSC6910) LST logical RNC. A
UCSVOICEPPC logical RNC
identifier consists of
12 binary codes. It
ranges from 0 to
4095. The RNC is a
logical node in the
RNS, which utilizes
and allocates radio
resources.

Copyright © Huawei
During data
configuration, this
parameter must be
manually set if the
Load Sharing Type
field in the output of
the LST
URNCBASIC
command is
OVERFLOW or
BACKUP.
If the Load Sharing
Type and
Redundancy Type
fields in the output
of the LST
URNCBASIC
command are
MASTER, this
parameter does not
need to be manually
set. The system will
automatically obtain
the RNC ID.
New VoicePPCSwitch(U SET Switch for the CS
MTS UCSVOICEPPC Voice Precise Power
BSC6900,UMTS Control feature.
BSC6910) After this switch is
turned on, this
feature is activated.
Then, the Enhanced
BER-based OLPC
function and the
Enhanced ILPC
function that is
based on optimized
SIR estimation and
enhanced multipath
searching are
enabled.
New InitQeFactor(UMT SET Initial-target-QE
S BSC6900,UMTS UCSVOICEPPC adjustment factor for
BSC6910) OLPC involved in
the CS Voice Precise
Power Control
feature.
New InitQeConst(UMTS SET Initial-target-QE
BSC6900,UMTS UCSVOICEPPC adjustment constant
BSC6910) for OLPC involved
in the CS Voice

Copyright © Huawei
Precise Power
Control feature.
New QeFactor(UMTS SET Target-QE
BSC6900,UMTS UCSVOICEPPC adjustment factor for
Power Control
feature.
New QeStepSize(UMTS SET Target-QE
BSC6900,UMTS UCSVOICEPPC adjustment step for
Power Control
feature.
New SirDtxConst(UMTS SET Target-SIR
BSC6900,UMTS UCSVOICEPPC adjustment constant
BSC6910) for OLPC involved
in the CS Voice
Precise Power
Control feature. This
constant is used
during DTX.
New SirStepSize(UMTS SET Target-SIR
BSC6900,UMTS UCSVOICEPPC adjustment step for
Power Control
feature.

The following table lists the new counters added on the RNC side.
Change Type Counter Measurement Description
Unit
New VS.CSVoicePPC.Sin AMR.CELL This counter

gleRAB.VoiceFrmN provides the total
um number of voice
frames in a single
CS voice service
subject to CS voice
precise power
control.
New VS.CSVoicePPC.M AMR.CELL This counter
ultiRABs.VoiceFrm provides the total
Num number of voice
frames of combined
services subject to

Copyright © Huawei
Change Type Counter Measurement Description

Unit
CS voice precise
power control.

None.

None
The CS Voice Precise Power Control feature is a substitute for the conventional power control
feature. On the RNC, when the switch for this feature is set to on, the conventional power
control based on BLER no longer has effect; when the switch is set to off, the conventional
power control based on BLER takes effect.
Impacted Features
None.
Related Operations
For details, see "Engineering Guidelines" in CS Voice Precise Power Control Feature
Parameter Description of RAN Feature Documentation.

IR-V100R009-021
7.2.1.7 WRFD-160208 160 HSPA Users per Cell
Description
In V100R009, a single cell can simultaneously support a maximum of 160 HSPA users,
including the VoIP or other low-rate users.
If the load resources are limited, it is recommended that you use this feature together with the
WRFD-010712 Adaptive Configuration of Traffic Channel Power offset for HSUPA and
WRFD-010686 CPC - DTX / DRX features. If the available CE resources are insufficient, it
is recommended that you use this feature together with the WRFD-140212 CE Overbooking
feature.
Implementation
For details, see Management of HSPA Users per Cell Feature Parameter Description in RAN

Copyright © Huawei

 Capacity
 Performance
If the WRFD-140212 CE Overbooking feature is not enabled, more HSUPA UEs lead to
higher uplink CE resource consumption. The cause is as follows:
− After admitting an HSUPA UE with the 2 ms TTI, the NodeB allocates CEs based on
CE(OneRlcPdu) or CE(GBR), whichever is larger. The allocated minimum data rate
for HSUPA UEs is 160 kbit/s, and each of them consumes eight CEs. The allocated
minimum data rate for R99 UEs is 32 kbit/s, and each of them consumes one CE.
Therefore, each HSUPA UE with the 2 ms TTI consumes seven extra CEs.
− After admitting an HSUPA UE with the 10 ms TTI, the NodeB allocates CEs based
on CE(OneRlcPdu) or CE(GBR), whichever is larger. If the GBR is 32 kbit/s, each
signaling radio bearer (SRB) (over the DCH or E-DCH) consumes two CEs for
admitting such UEs. If the GBR is 64 kbit/s, each SRB (over the DCH) consumes
three CEs for admitting such UEs and each SRB (over the E-DCH) consumes four
CEs for admitting such UEs. Therefore, each HSUPA UE with the 10 ms TTI
consumes one to two extra CEs.
Impact on NEs
Impact on Hardware
The feature is available only for 3900 series base stations. 3900 series base stations must be
configured with the UBBPd.

None

An RNC-level license control item has been added to the RNC for this feature.
Table 1.1 License information for 160 HSPA Users per Cell
Feature ID Feature Name License Control Item NE Sales Unit
WRFD-160208 160 HSPA 160 HSPA User per Cell RNC per kbps
Users per Cell (per kbps)

Table 1.2 New NodeB Parameter

Change Type Parameter ID MML Command NE Description
New HSPAUSERNU ADD ULOCELL Node Indicates the

Copyright © Huawei
MEXT MOD ULOCELL B number of HSPA

LST ULOCELL users served in a
local cell. Value ON
indicates that a local
cell serves more
than 128 HSPA
users, and value
OFF indicates that a
local cell serves a
maximum of 128
HSPA users.

None
Change Alarm Name NE Description
Type
Modified ALM-28206 Local Cell NodeB The cause value 33 has been added.
Capability Decline This alarm is reported when a user
configures the HSPA user number
extend but the local cell does not
support this function.

 WRFD-010654 128 HSDPA Users per Cell
 WRFD-010670 128 HSUPA Users per Cell
None
Impacted Features
This feature can increase uplink or downlink load and CE resource consumption.
 When cell load is heavy, it is recommended that the following features be enabled to
increase the capacity of the Uu interface, thereby reducing the load and probability of
call drops.
− WRFD-010712 Adaptive Configuration of Traffic Channel Power offset for HSUPA
− WRFD-010210 Control Channel Parallel Interference Cancellation (CCPIC)
− WRFD-140202 Control Channel Parallel Interference Cancellation (Phase 2)
− WRFD-140215 Dynamic Configuration of HSDPA CQI Feedback Period
− WRFD-140211 Dynamic Target RoT Adjustment

Copyright © Huawei

− WRFD-150236 Load Based Dynamic Adjustment of PCPICH
 When the remaining CE resources are insufficient in a cell, activating the WRFD-140212
CE Overbooking feature improves the CE resource utilization.
Related Operations
For details, see "Engineering Guidelines" in Management of HSPA Users per Cell Feature

IR-V100R009-052
7.2.1.8 WRFD-160209 192 HSPA Users per Cell
Description
In V100R009, a single cell can simultaneously support a maximum of 192 HSPA users,
including the VoIP or other low-rate users.
If the load resources are limited, it is recommended that you use this feature together with the
WRFD-010712 Adaptive Configuration of Traffic Channel Power offset for HSUPA and
WRFD-010686 CPC - DTX / DRX features. If the available CE resources are insufficient, it
is recommended that you use this feature together with the WRFD-140212 CE Overbooking
feature.
Implementation
For details, see Management of HSPA Users per Cell Feature Parameter Description in RAN

 Capacity
 Performance
If the WRFD-140212 CE Overbooking feature is not enabled, more HSUPA UEs lead to
higher uplink CE resource consumption. The cause is as follows:
− After admitting an HSUPA UE with the 2 ms TTI, the NodeB allocates CEs based on
CE(OneRlcPdu) or CE(GBR), whichever is larger. The allocated minimum data rate
for HSUPA UEs is 160 kbit/s, and each of them consumes eight CEs. The allocated
minimum data rate for R99 UEs is 32 kbit/s, and each of them consumes one CE.
Therefore, each HSUPA UE with the 2 ms TTI consumes seven extra CEs.
− After admitting an HSUPA UE with the 10 ms TTI, the NodeB allocates CEs based
on CE(OneRlcPdu) or CE(GBR), whichever is larger. If the GBR is 32 kbit/s, each
signaling radio bearer (SRB) (over the DCH or E-DCH) consumes two CEs for
admitting such UEs. If the GBR is 64 kbit/s, each SRB (over the DCH) consumes
three CEs for admitting such UEs and each SRB (over the E-DCH) consumes four
CEs for admitting such UEs. Therefore, each HSUPA UE with the 10 ms TTI
consumes one to two extra CEs.

Copyright © Huawei
As the number of uplink and downlink HSPA users increases, load overheads increase on
control channels carrying services of online UEs, and the uplink load may increase,
consequently decreasing cell coverage. In heavy load scenarios, KPIs such as the access
success rate and call drop rate may be affected.
Impact on NEs
Impact on Hardware
The feature is available only for 3900 series base stations. 3900 series base stations must be
configured with the UBBPd.

None

An RNC-level license control item has been added to the RNC for this feature.
Table 1.1 License information for 192 HSPA Users per Cell
Feature ID Feature Name License Control Item NE Sales Unit
WRFD-160209 192 HSPA 192 HSPA User per Cell RNC per kbps
Users per Cell (per kbps)

Table 1.2 New NodeB Parameter

New HSPAUSERNU ADD ULOCELL Node Indicates the

MEXT MOD ULOCELL B number of HSPA
users served in a
LST ULOCELL local cell. Value ON
indicates that a local
cell serves more
than 128 HSPA
users, and value
OFF indicates that a
local cell serves a
maximum of 128
HSPA users.

Copyright © Huawei
None
Type
Modified ALM-28206 Local Cell NodeB The cause value 33 has been added.
Capability Decline This alarm is reported when a user
configures the HSPA user number
extend but the local cell does not
support this function.

 WRFD-160208 160 HSPA Users per Cell
None
Impacted Features
This feature can increase uplink or downlink load and CE resource consumption.
 When cell load is heavy, it is recommended that the following features be enabled to
increase the capacity of the Uu interface, thereby reducing the load and probability of
call drops.
− WRFD-010712 Adaptive Configuration of Traffic Channel Power offset for HSUPA
− WRFD-010210 Control Channel Parallel Interference Cancellation (CCPIC)
− WRFD-140202 Control Channel Parallel Interference Cancellation (Phase 2)
− WRFD-140215 Dynamic Configuration of HSDPA CQI Feedback Period
− WRFD-140211 Dynamic Target RoT Adjustment
− WRFD-150236 Load Based Dynamic Adjustment of PCPICH
 When the remaining CE resources are insufficient in a cell, activating the WRFD-140212
CE Overbooking feature improves the CE resource utilization.
Related Operations
For details, see "Engineering Guidelines" in Management of HSPA Users per Cell Feature

IR-V100R009-052

Copyright © Huawei
7.2.1.9 WRFD-160205 CE Efficiency Improvement for HSUPA TTI 2ms
Description
Before this feature was introduced, a 2 ms TTI HSUPA UE whose uplink data rate was less
than or equal to 20 kbit/s (according to Huawei uplink CE consumption principles) consumed
two CEs. With this feature, a 2 ms TTI UE activates only a single HARQ process and
optimizes scheduling to smooth the data transmission and increase the CE efficiency. Only
one CE is consumed by a 2 ms TTI HSUPA UE that has uplink data rate less than or equal to
20 kbit/s in a single HARQ process, increasing the CE efficiency by 100%.
Implementation
For details, see CE Efficiency Improvement for HSUPA TTI 2ms Feature Parameter
Description in RAN Feature Documentation.

 Capacity
 Performance
Impact on NEs
This feature is implemented on the RNC, NodeB, and U2000.
This feature requires support from the UE. The UE must be of HSUPA category 6 or higher.
Impact on Hardware
The DBS3800, BTS3812E, BTS3812A, BTS3812AE, and BTS3902E do not support CE
Efficiency Improvement for HSUPA TTI 2ms.

Private IEs have been added to the following messages for the NodeB to inform the RNC if
newly admitted HSUPA UEs with a 2 ms TTI support this feature:
 RL Setup Response
 RL Reconfiguration Response Ready
 RL ADD Response
 Common Measurement Reporting

A NodeB license control item has been added for this feature.
Control Item
WRFD-160205 CE Efficiency CE Efficiency NodeB Per NodeB

Improvement Improvement
for HSUPA TTI for HSUPA TTI

Copyright © Huawei

Control Item
2ms 2ms

Type ID
New CEIMPRO SET Node HSUPA 2ms CE Efficiency

VEMENT2 NODEBALGPARA B Improvement Switch
MSSW
New INITSING SET Node Initial Single HARQ Switch
LEHARQS NODEBALGPARA B for 2ms HSUPA Users
W

Type Name nt Unit
New VS.HSUPA.L HSUPA.LOC NodeB Average number of 2 ms TTI

owRateTTI2 ELL HSUPA users at a rate lower than
msUserNumb or equal to 23.25 kbit/s in a cell
er
New VS.HSUPA. HSUPA.LOC NodeB Number of transitions from using
AlltoSingleH ELL all HARQ processes to using a
ARQNum.CE single HARQ process due to
Cong limited CEs in the cell
New VS.HSUPA.S HSUPA.LOC NodeB Number of Transitions from
ingletoAllHA ELL Using A Single HARQ Process to
RQNum Using All HARQ Processes In
the Cell

None

 WRFD-010638 Dynamic CE Resource Management
 WRFD-140212 CE Overbooking

Copyright © Huawei
None
Impacted Features
 WRFD-010695 UL Layer 2 Improvement
When UL Layer 2 Improvement is enabled, the active HARQ process of a UE can use
SF8 at most and the minimum RLC rate can be further reduced to 15 kbit/s.
 Admission-CE-based dynamic TTI adjustment for a single BE service over HSUPA
When admission-CE-based dynamic TTI adjustment for a single BE service over
HSUPA is enabled, HSUPA UEs with a 10 ms TTI with services established on the
WBBPf or UBBPd board can be switched to use a 2 ms TTI if uplink CE resources
become insufficient. For HSUPA UEs with a 2 ms TTI and newly admitted UEs whose
services are established on the WBBPf or UBBPd board, 2ms-to-10ms TTI switching is
not performed if uplink CE resources become insufficient.
This is because the minimum rate of an HSUPA UE with a 2 ms TTI decreases from 160
kbit/s to 20 kbit/s at the RLC layer when CE Efficiency Improvement for HSUPA TTI
2ms is enabled, while the minimum rate of an HSUPA UE with a 10 ms TTI is 32 kbit/s.
Both HSUPA UEs with a 2 ms TTI and those with a 10 ms TTI occupy one CE to
transmit data. As a result, it is not necessary to perform 2ms-to-10ms TTI switching
when uplink CE resources are insufficient.
For more information about the admission-CE-based dynamic TTI adjustment for a
single BE service over HSUPA, see HSUPA TTI Selection Feature Parameter
Description.
Related Operations
For details, see "Engineering Guidelines" in CE Efficiency Improvement for HSUPA TTI 2ms
Feature Parameter Description of RAN Feature Documentation.

IR-V100R009-038
7.2.1.10 WRFD-160213 Turbo IC Phase2
Description
According to 3GPP TS 25.321, a 2 ms TTI HSUPA UE has eight HARQ processes that can be
activated separately. When all eight HARQ processes are activated, the minimum data rate is
160 kbps for a 2 ms TTI HSUPA UE that has non-zero scheduling grants (SGs). When the cell
load resources in the uplink are limited, only a few 2 ms TTI UEs can simultaneously transfer
data using non-zero SGs in the cell. If more 2 ms TTI UEs need to transfer data
simultaneously, these UEs can use a 10 ms TTI and reduce the minimum data rate to 32 kbps.
However, the involved reconfiguration processes increase the probability of call drops. Note
that a 10 ms TTI HSUPA UE has four HARQ processes that cannot be activated separately.
This feature uses only one HARQ process out of eight to transfer data if the cell load
resources in the uplink are insufficient for each 2 ms TTI UE to obtain an SG of 160 kbps.
This reduces the minimum data rate from 160 kbps to 20 kbps, enabling multiple 2 ms TTI
UEs to continue transferring data simultaneously. At the same time, Turbi IC technology is
used to reduce the interference between UEs, thereby more 2 ms TTI UEs can simultaneously
transfer data in a cell.

Copyright © Huawei
In addition, because there is no requirement to change the TTI from 2 ms to 10 ms, the
amount of signaling required for reconfigurations is reduced, thereby reducing the probability
of call drops.
If HSUPA UEs use a 2 ms TTI, the transmission delay of UEs that have low traffic is reduced
and the user experience is improved.
Implementation
For details, see HSUPA Data Channel Interference Cancellation Feature Parameter
Description in RAN Feature Documentation.

 Capacity
− Increased number of 2 ms TTI HSUPA UEs
Compared with Turbo IC, Turbo IC Phase2 significantly increases the number of full
buffer 2 ms TTI HSUPA UEs that are online simultaneously when the target Rise
Over Thermal (RoT) is 6 dB.
Note that full buffer UEs are those that have continuous and sufficient data
transmission.
If both the WBBPf/UBBP and WBBPa/WBBPb/WBBPd are configured in the uplink
resource group, the gains provided by Turbo IC Phase2 will be affected in the
following way:
The number of 2 ms TTI HSUPA UEs that can be admitted decreases because the
WBBPa, WBBPb, and WBBPd do not support Turbo IC Phase2.
 Performance
Impact on NEs
This feature is implemented on the RNC, NodeB, and U2000.
In addition, this feature requires that the UE must be of category 6 or above.
Impact on Hardware
The NodeB hardware must meet the following requirements:
 The 3900 series base stations must be configured with WBBPf or UBBP boards. In
addition, the cell's downlink services cannot be set up on a WBBPa and the uplink
resource group must contain WBBPf or UBBP boards.
 The BTS3803E supports this feature.
 The BTS3902E does not support this feature.
Run the NodeB MML command DSP ULOCELLRES to query which baseband processing
board the cell's downlink services are set up on.
Run the NodeB MML command LST BASEBANDEQM to query which baseband
processing boards are contained in the uplink resource group and run the NodeB MML
command DSP BRDMFRINFO to query the type of a baseband processing board.

Copyright © Huawei

The NodeB reports the RNC whether a newly admitted or reconfigured 2 ms TTI HSUPA UE
supports Turbo IC Phase2 using the proprietary information element (IE)
RtwpTtiEfficencyPrivate in the following messages:
 RL Setup Response message
 RL Reconfiguration Response Ready message
 RL ADD Response message
 Cell common measurement messages

A cell-level license control item has been added to the NodeB for this feature.
Type ID
New TURBOICP ADD ULOCELL NodeB Specifies whether a

HASE2 MOD ULOCELL cell supports Turbo
IC Phase2.
LST ULOCELL
DSP ULOCELL

Type nt Unit
New VS.HSUPA. HSUPA.LOC NodeB Number of transitions from using

AlltoSingleH ELL all HARQ processes to using a
ARQNum.RT single HARQ process due to
WPCong limited RTWP in the cell
New VS.HSUPA.S HSUPA.LOC NodeB Number of Transitions from
ingletoAllHA ELL Using A Single HARQ Process to
RQNum Using All HARQ Processes In the
Cell

The function of tracing the number of single-HARQ-process-scheduling UEs has been
introduced on the NodeB LMT to accommodate this feature.
The following alarms have been modified to accommodate this feature.

Copyright © Huawei
Change Alarm NE Description

Type
Modified ALM-28206 Local Cell NodeB Added the cause value " Turbo IC
Capability Decline Phase2 not supported by the cell."
Modified ALM-26811 Configured NodeB Added the cause value "Insufficient
Capacity Limit Exceeding license for Turbo IC Phase2."
Licensed Limit

 WRFD-150206 Turbo IC
None
Impacted Features
 WRFD-010695 UL Layer 2 Improvement
If the UL Layer 2 Improvement feature has been enabled, using the Turbo IC Phase2
feature further reduces the minimum rate of 2 ms TTI HSUPA UEs at the RLC layer to
10 kbit/s.
 WRFD-010690 TTI Switch for BE Services Based on Coverage
The TTI Switch for BE Services Based on Coverage feature expands network coverage
but reduces the number of2 ms TTI HSUPA UEs. That is, TTI Switch for BE Services
Based on Coverage reduces the Turbo IC Phase2's gains in the number of 2 ms TTI
HSUPA UEs.
 TTI Adjustment Based on Uu-interface Resources
Turbo IC Phase2 affects the function of differentiation-based dynamic TTI adjustment
for a single BE service over HSUPA in the following way:
If the function is triggered based on Uu-interface resources, 2 ms TTI HSUPA UEs
enabled with Turbo IC Phase2 will not be switched to 10 ms TTI when Uu-interface
resources are insufficient in the uplink. The reason is as follows:
The minimum rate of 10 ms TTI HSUPA UEs at the RLC layer is 32 kbit/s. Without
Turbo IC Phase2, the minimum rate of 2 ms TTI HSUPA UEs at the RLC layer is 160
kbit/s. When Uu-interface resources are insufficient, the TTI of 2 ms TTI HSUPA UEs
will be switched from 2 ms to 10 ms to reduce the power consumption and the possibility
of call drops. After Turbo IC Phase2 is enabled, the minimum rate of 2 ms TTI HSUPA
UEs at the RLC layer is 20 kbit/s and therefore TTI switching is not required.
The RNC determines whether to switch from 2 ms TTI to 10 ms TTI based on whether
the 2 ms TTI HSUPA UE supports Turbo IC Phase2.
The NodeB reports the RNC whether a newly admitted or reconfigured 2 ms TTI
HSUPA UE supports Turbo IC Phase2 using the proprietary information element (IE)
RtwpTtiEfficencyPrivate in the following messages:
− RL Setup Response message
− RL Reconfiguration Response Ready message
− RL ADD Response message

Copyright © Huawei
− Cell common measurement messages

The function of TTI adjustment based on the Uu-interface resources is enabled by setting
the ResourceOption parameter in the SET UEDCHTTIRECFG command to RTWP.
For details about this function, see section "Differentiation-based Dynamic TTI
Adjustment for a Single BE Service over HSUPA" in HSUPA TTI Selection Feature
 WRFD-160205 CE Efficiency Improvement for HSUPA TTI 2ms
It is recommended that the Turbo IC Phase2 feature be used together with the WRFD-
160205 CE Efficiency Improvement for HSUPA TTI 2ms feature. Otherwise, HSUPA
UEs will switch from 2 ms TTI to 10 ms TTI when CE resources are insufficient, which
will reduce the gains provided by the Turbo IC Phase2 feature.
 Uplink Admission Control Algorithm 2
After the Turbo IC Phase2 feature takes effect, more 2 ms TTI HSUPA UEs are admitted.
Turbo IC Phase2.
After the Turbo IC Phase2 feature takes effect in a cell, newly admitted 2 ms TTI
HSUPA UEs use only one HARQ process to transmit data when the Uu-interface
resources are insufficient and therefore consumes less equivalent number of users
(ENUs) than all-HARQ-process-scheduling UEs. This eliminates the probability of
ENU-based admission failure in the uplink.
For the ENUs that a 2 ms TTI HSUPA UE and a 10 ms TTI HSUPA UE consume in
typical scenarios, see Table 7-14 "ENU references in typical scenarios" in section 7.3.1
"ENU" of Call Admission Control Feature Parameter Description.
Related Operations
For details, see "Engineering Guidelines" in HSUPA Data Channel Interference Cancellation

IR-V100R009-005
7.2.1.11 WRFD-160201 Control Channel Parallel Interference Cancellation
Description
The Control Channel Parallel Interference Cancellation (Phase 2) feature performs
regeneration and cancellation on the dedicated physical control channel (DPCCH) to reduce
the interference in other channels caused by this channel, thereby improving the UE receive
performance and uplink cell capacity.
Similarly, the Control Channel Parallel Interference Cancellation (Phase 3) feature performs
regeneration and cancellation on the HS-DPCCH and E-DPCCH channels, which further
reduces the interference and improves the cell capacity. This feature works as follows:
 The detection module demodulates and decodes the received HS-DPCCH/E-DPCCH
signals.
 The regeneration module regenerates signals of UEs on their respective HS-DPCCH/E-
DPCCH by using information such as the demodulation, decoding, and channel
estimation results.
 The cancellation module removes the regenerated HS-DPCCH/E-DPCCH signals of the
UE from the total received signals.

Copyright © Huawei
Signals on the HS-DPDCH/E-DPDCH have gone through interference cancellation before

being demodulated and decoded, thereby enhancing UEs' reception performance and
improving cell capacity.
Implementation
For details, see Control Channel Interference Cancellation Feature Parameter Description in

 Capacity
Compared with CCPIC (Phase 2), CCPIC (Phase 3) also supports interference
regeneration and cancellation of the HS-DPCCH and E-DPCCH in addition to the
DPCCH, thereby improving uplink system capacity. Gains become more noticeable as
the load on the HS-DPCCH and E-DPCCH increases.
When all baseband processing units in the base station are UBBPd boards, CCPIC
(Phase 3) provides the following gains compared with CCPIC (Phase 2):
In a cell that has 8 to 12 full-buffer UEs (UEs transmitting data continuously), the uplink
cell throughput increases by 5% to 25%. If CCPIC was not enabled in the cell, the uplink
cell throughput increases by 10% to 35% after CCPIC (Phase 3) is enabled.
In a cell that has 2 full-buffer UEs and 20 to 30 burst UEs (UEs transmitting data
abruptly in a rather short period of time), the uplink cell throughput increases by 10% to
30%. If CCPIC was not enabled in the cell, the uplink cell throughput increases by 20%
to 40% after CCPIC (Phase 3) is enabled.
In a cell where there are only burst UEs and the load is heavy (RoT > Target RoT –
2), the maximum number of connections increases by 5% to 20%. If CCPIC was not
enabled in the cell, the uplink cell throughput increases by 10% to 40% after CCPIC
(Phase 3) is enabled.
Only the UBBPd boards support CCPIC (Phase 3). Therefore, when the UBBPd boards
are used together with other boards, the gains of CCPIC (Phase 3) compared with CCPIC
(Phase 2) will decrease.
 Performance
You are advised to replace the WBBPa or WBBPb board with a UBBPd board to
maximize the gains provided by CCPIC (Phase 3). The reason is as follows:
Assume that a WBBPa or WBBPb board and a UBBPd board form an uplink resource
group. To ensure that a WBBPa or WBBPb board can benefit from CCPIC (Phase 3)
gains provided by a UBBPd board, the INTERBOARDICSW parameter can be set to
FULL_IC. To improve the air interface capacity, the INTERBOARDICSW parameter is
recommended to be set to FULL_IC. However, UEs whose data channels are carried on
the WBBPa or WBBPb board must set up DPCCHs on the UBBPd board for power
control purposes. In addition, UEs whose downlink services are carried on HSDPA
channels must set up another HS-DPCCH on the UBBPd board. The new channels
consume extra resources, which reduces the total number of users supported by the
system and decreases the access success rate. To fully benefit from the inter-board IC
gains provided CCPIC (Phase 3), it is recommended that the WBBPa or WBBPb board
be replaced by a UBBPd board.
If the WBBPa or WBBPb board cannot be replaced, you are advised to set the
INTERBOARDICSW parameter to PART_IC.

Copyright © Huawei
Impact on NEs
Impact on Hardware
To implement this feature, the following requirements must be met:
 Only 3900 series base stations (except the BTS3902E) support this feature. The uplink
resource group of the base station must be configured with at least one UBBPd board.
 To enable a 3900 series base station to support inter-board sharing of the cancellation
result of CCPIC (Phase 3), at least one WBBPd, WBBPf, or UBBPd board must be
configured in slot 2 or 3 in the BBU of the 3900 series base station.
 The INTERBOARDICSW parameter must be set to FULL_IC(All board can share IC
gain) and inter-board data channels must be configured under the following conditions:
A 3900 series base station is configured with the WBBPa/WBBPb and UBBPd boards to
form a baseband resource pool and the WBBPa/WBBPb board needs to share the
interference cancellation gains with the UBBPd board.
This is because UEs that have set up data channels on the WBBPa/WBBPb must set up
control channels on the UBBPd board.

This feature does not have any special requirements for the Uu, Iub, Iur, or Iu interface.

This feature is controlled by a new NodeB-level license control item.
The following table describes the NodeB command and parameter required for this
feature.
Type ID Command
New CCPICPHA SET NodeB When CCPIC Phase3 Switch is

SE3 NODEBALGP set to CCPICPHASE3, CCPIC
ARA (Phase 3) is supported.

The following parameters have been introduced on the NodeB side to accommodate this
feature.
Type Name nt Unit
Modified VS.FirstStage ALGO.LOCE NodeB Average value of stage 1

IcEff.Mean LL interference cancellation
efficiency
When CCPIC (Phase 2) is
enabled, stage 1 interference

Copyright © Huawei

Type Name nt Unit
cancellation (IC) refers to IC of

the DPCCH. When both CCPIC
(Phase 2) and CCPIC (Phase 3)
are enabled, stage 1 IC refers to
IC of the DPCCH, HS-DPCCH,
and E-DPCCH.
Modified VS.FirstStage ALGO.LOCE NodeB Maximum value of stage 1
IcEff.Max LL interference cancellation
efficiency
New VS.CCPICPh ALGO.LOCE NodeB Average number of channels for
ase3.CodeNu LL CCPIC Phase 3 by users in a cell
m.Mean

None

 WRFD-010210 Control Channel Parallel Interference Cancellation (CCPIC)
 WRFD-140202 Control Channel Parallel Interference Cancellation (Phase 2)
None
Impacted Features
 WRFD-140215 Dynamic Configuration of HSDPA CQI Feedback Period
When Dynamic Configuration of HSDPA CQI Feedback Period is enabled, gains from
CCPIC (Phase 3) compared with CCPIC (Phase 2) decrease.
This is because CCPIC (Phase 3) increases system capacity by canceling interference
from the HS-DPCCH and E-DPCCH while Dynamic Configuration of HSDPA CQI
Feedback Period reduces the HS-DPCCH power and therefore leaves less interference
from the HS-DPCCH to be canceled. The system throughput produced when CCPIC
(Phase 3) and Dynamic Configuration of HSDPA CQI Feedback Period are both enabled
is greater than that produced when they are not both enabled.
 WRFD-010712 Adaptive Configuration of Traffic Channel Power offset for HSUPA
When CCPIC is enabled, gains from Adaptive Configuration of Traffic Channel Power
offset for HSUPA and HSUPA Adaptive Retransmission decrease. Likewise, when
Adaptive Configuration of Traffic Channel Power offset for HSUPA or HSUPA Adaptive
Retransmission is enabled, gains from CCPIC decrease. This is because CCPIC increase
system capacity by canceling interference from the DPCCH while Adaptive
Configuration of Traffic Channel Power offset for HSUPA and HSUPA Adaptive
Retransmission reduce the DPCCH power and therefore leave less interference from the
DPCCH to be canceled.

Copyright © Huawei
For a detailed description of Adaptive Configuration of Traffic Channel Power offset for
HSUPA, see Power Control Feature Parameter Description.
 WRFD-010641 HSUPA Adaptive Retransmission
System throughput is always greater when CCPIC is enabled together with Adaptive
Configuration of Traffic Channel Power offset for HSUPA or HSUPA Adaptive
Retransmission, as compared with when CCPIC is not enabled together with Adaptive
Configuration of Traffic Channel Power offset for HSUPA or HSUPA Adaptive
Retransmission or none of the features is enabled.
For a detailed description of HSUPA Adaptive Retransmission, see HSUPA Feature
 WRFD-160202 Flexible Power Control for Uplink Low Data Rate Transmission
When CCPIC (Phase 3) is enabled, gains from Flexible Power Control for Uplink Low
Data Rate Transmission decrease. Likewise, gains from CCPIC (Phase 3) decrease when
Flexible Power Control for Uplink Low Data Rate Transmission is enabled.
This is because CCPIC (Phase 3) increases system capacity by canceling interference
from the E-DPCCH and HS-DPCCH while Flexible Power Control for Uplink Low Data
Rate Transmission reduces the E-DPCCH power and therefore leaves less interference
from the E-DPCCH to be canceled. The system throughput produced when CCPIC
(Phase 3) and Dynamic Configuration of HSDPA CQI Feedback Period are both enabled
is greater than that produced when they are not both enabled.
For details about the Flexible Power Control for Uplink Low Data Rate Transmission
feature, see Flexible Power Control for Uplink Low Data Rate Transmission Feature
Related Operations
For details, see "Engineering Guidelines" in Control Channel Interference Cancellation

IR-V100R009-002
7.2.1.12 WRFD-151211 RNC IP Active Performance Measurement
Description
This feature monitors changes in QoS parameters related to the transport network based on
the TWAMP such as round-trip delay, one-way packet loss rate, and one-way jitter.
A measurement model is defined based on the TWAMP. The measurement model provides
functions of the Controller and the Responder. The Controller consists of the Session-Sender
and Control-Client, and the Responder consists of the Session-Reflector and Server.
TWAMP control packets are transmitted between the Control-Client and Server for
measurement task negotiation (also known as initialization), start, and stop. TWAMP control
packets are transmitted based on TCP, and the Server uses port 862.
TWAMP test packets are transmitted between the Session-Sender and Session-Reflector based
on UDP.
The following figure shows the working mechanism of the measurement model.

Copyright © Huawei
The Controller sends TWAMP packets over a negotiated stream based on the measurement
task negotiation result. The stream consists of the Controller IP address, Responder IP
address, UDP port number, and Type-P information. Type-P information can be the protocol
type, port number, packet length, or differentiated services code point (DSCP). A TWAMP test
packet contains the sending sequence number and sending timestamp. Based on the TWAMP
test packets, link performance indicators (such as one-way delay, one-way jitter, one-way
packet loss rate, and round-trip delay) can be calculated.
The Responder sends responses to the packets sent by the Controller. The Responder records
the receiving timestamp, obtains the sending sequence number and timestamp, and generates
a response packet. The response packet contains the receiving timestamp, sending sequence
number, and sending timestamp of each packet sent by the Controller, as well as the sending
sequence number and sending timestamp of each packet sent by the Session-Reflector.
This feature works in unacknowledged mode, and supports the functions of the Controller and
Responder.
This feature calculates the packet loss rate within a measurement period using the following
formulas:
 Packet loss rate in the direction from the Sender to the Reflector = (Number of packets
sent by the Sender – Number of packets sent by the Reflector)/Number of packets sent
by the Sender
 Packet loss rate in the direction from the Reflector to the Sender = (Number of packets
sent by the Reflector – Number packets received by the Sender)/Number of packets sent
by the Reflector
This feature calculates the round-trip time (RTT) using the following formula:
RTT = (T2 – T1) + (T4 – T3) = (T4 – T1) – (T3 – T2)
where
 T1: time that the Sender sends the packet
 T2: time that the Reflector receives the packet
 T3: time that the Reflector sends the response packet
 T4: time that the Sender receives the response packet
This feature calculates the one-way jitter based on the delay between adjacent packets.

Copyright © Huawei
Implementation
See IP Active Performance Measurement Feature Parameter Description.

 Capacity
Because TWAMP negotiation packet interaction occurs in the protocol stack and only a
small number of packets are involved, TWAMP has negligible impact on CPU
performance.
TWAMP test packets affect the user plane (UP) forwarding performance because they
are transmitted and received on the UP. The greater the transmit rate of test packets, the
greater the resource consumption of TWAMP forwarding. However, TWAMP forwarding
resource consumption still has negligible impact when compared with the base station
and base station controller's forwarding capabilities.
 Performance
TWAMP testing uses packet injection, which generates traffic in the transport network
and therefore occupies some bandwidth. The bandwidth consumption is related to the
transmit rate of test packets. Users can specify the transmit interval and packet length for
the packets to be transmitted.
In maintenance and testing scenarios, if you are not sure whether the transmit rate
(determined by the IP path, resource group, and port) on transmission links is close to the
planned bandwidth, transmitting a small number of packets at an appropriate interval
(low-traffic) is recommended for a TWAMP test. For example, if 80-byte packets are
continuously sent at a rate of 10 packets per second in a test stream, the bandwidth
consumption is 6.4 kbit/s.
In monitoring scenarios, it is recommended that you reserve bandwidth for the TWAMP
test so that involved packets can be sent continuously. If 80-byte packets are sent at a
rate of 10 packets per second in a test stream, the bandwidth consumption is 6.4 kbit/s.
You can monitor the test stream to check whether any transmission faults are occurring.
Impact on NEs
This feature is implemented on the RNC, BSC, eGBTS, NodeB, or eNodeB. All the NEs must
support the TWAMP Controller and Responder functions and the two functions can be
enabled independently on each NE.
If this feature is enabled between the RAN and CN, the RAN and router, the CN and router
must support the TWAMP functions.
Impact on Hardware
The base station controller must be configured with the FG2c/FG2d/GOUc/GOUd/EXOUa to
support TWAMP.
The base station must be configured with the WMPT/LMPT/UMPT/UTRPc to support
TWAMP.

None.

Copyright © Huawei

This feature is license-controlled on per site basis when being enabled on the eGBTS,
NodeB, or eNodeB side, on per TRX basis when being enabled on the BSC side, or on
per Elr&Mbps basis when being enabled on the RNC side.
The following table provides the MOs, parameters, and MML commands added to this
feature.
MO Parameters MML
TWAMPRESPONDER RESPONDERID ADD TWAMPRESPONDER

LOCALIP RMV TWAMPRESPONDER
VRFINDEX MOD TWAMPRESPONDER
SERVWAIT LST TWAMPRESPONDER
REFWAIT DSP TWAMPRESPONDER
DSP TWAMPRESPONDERSTA
TWAMPCLIENT CLIENTID ADD TWAMPCLIENT
LOCALIP RMV TWAMPCLIENT
PEERIP MOD TWAMPCLIENT
VRFINDEX LST TWAMPCLIENT
SP TWAMPCLIENT
TWAMPSENDER CLIENTID ADD TWAMPSENDER
SENDERID RMV TWAMPSENDER
DSCP MOD TWAMPSENDER
PKTSIZETYPE LST TWAMPSENDER
PKTSIZE SP TWAMPSENDER
PKTINTTYPE
PKTINT

This following table provides the measurement object added on the base station side.
Measureme Description
nt Object
BSTWAMP Measurement of BS TWAMP performance
This following table provides the measurement unit added on the base station side.

Copyright © Huawei
measureme Description
nt Unit
Transport.BS Measurement related to BSTWAMP

TWAMP
This following table provides the counters added on the base station side.
Counter Description
VS.BSTWAMP.Forward.DropRates. Average forward packet loss rate on

Mean the BSTWAMP
VS.BSTWAMP.Forward.DropRates. Peak forward packet loss rate on the
Max BSTWAMP
VS.BSTWAMP.Backward.DropRate Average backward packet loss rate on
s.Mean the BSTWAMP
VS.BSTWAMP.Backward.DropRate Peak backward packet loss rate on the
s.Max BSTWAMP
VS.BSTWAMP.RttDelay.Min Minimum RTT on the BSTWAMP
VS.BSTWAMP.RttDelay.Mean Average RTT on the BSTWAMP
VS.BSTWAMP.RttDelay.Max Maximum RTT on the BSTWAMP
VS.BSTWAMP.Forward.Jitter.Min Minimum forward jitter on the
BSTWAMP
VS.BSTWAMP.Forward.Jitter.Mean Average forward jitter on the
BSTWAMP
VS.BSTWAMP.Forward.Jitter.Max Maximum forward jitter on the
BSTWAMP
VS.BSTWAMP.Backward.Jitter.Min Minimum backward jitter on the
BSTWAMP
VS.BSTWAMP.Backward.Jitter.Mea Average backward jitter on the
n BSTWAMP
VS.BSTWAMP.Backward.Jitter.Ma Maximum backward jitter on the
x BSTWAMP
This following table provides the measurement object added on the base station
controller side.

Copyright © Huawei
Measureme Description
nt Object
TWAMP Measurement of TWAMP Performance
This following table provides the measurement unit added on the base station controller
side.
measureme Description
nt Unit
TransportLin Measurement related to TWAMP on BaseStation controller

k.TWAMP
This following table provides the counters added on the base station controller side.
Counter Description
VS.TWAMP.Forward.DropRate Average Forward Packet Loss Rates for TWAMP

s.Mean Measurement
VS.TWAMP.Forward.DropRate Peak Forward Packet Loss Rates for TWAMP
s.Max Measurement
VS.TWAMP.Backward.DropRa Average Backward Packet Loss Rates for TWAMP
tes.Mean Measurement
VS.TWAMP.Backward.DropRa Peak Backward Packet Loss Rates for TWAMP
tes.Max Measurement
VS.TWAMP.RttDelay.Min Minimum RTT for TWAMP Measurement
VS.TWAMP.RttDelay.Mean Average RTT for TWAMP Measurement
VS.TWAMP.RttDelay.Max Maximum RTT for TWAMP Measurement
VS.TWAMP.Forward.Jitter.Min Minimum Forward Delay Jitters for TWAMP
Measurement
VS.TWAMP.Forward.Jitter.Me Average Forward Delay Jitters for TWAMP
an Measurement
VS.TWAMP.Forward.Jitter.Ma Maximum Forward Delay Jitters for TWAMP
x Measurement
VS.TWAMP.Backward.Jitter.M Minimum Backward Delay Jitters for TWAMP
in Measurement
VS.TWAMP.Backward.Jitter.M Average Backward Delay Jitters for TWAMP
ean Measurement
VS.TWAMP.Backward.Jitter.M Maximum Backward Delay Jitters for TWAMP
ax Measurement

Copyright © Huawei

This feature adds the following alarm on the base station controller side:
− ALM-21354 IP Link Performance Measurement Fault
This feature adds the following alarm on the base station side:
− ALM-25904 IP Link Performance Measurement Fault

This feature is dependent on the WRFD-050402 IP Transmission Introduction on Iub Interface
feature.
None
Impacted Features
If the UDP loopback function is enabled on the base station side, UDP loopback cannot work
with TWAMP simultaneously to perform loopback tests on specified IP addresses or all IP
addresses.
The UDP loopback function affects TWAMP testing. If one TWAMP test end is enabled with
the loopback function and an IP address being looped back is the IP address used for TWAMP
testing, the test packets will be directly looped back, resulting in inaccurate statistics. If the
base station functions as the TWAMP Controller, the peer Responder's response packets will
be looped back. As a result, the UDP packets are retransmitted between the local end and peer
end (Responder), which increases network resource consumption.
Related Operations
See the "Engineering Guidelines" section in IP Active Performance Measurement Feature

IR-V100R009-099
7.2.1.13 WRFD-160274 IPSec Redundancy Among Multiple SeGWs
Description
This feature works as follows:
1. When a NodeB detects that an IPSec tunnel between it and the active SeGW is faulty, the
NodeB attempts to initiate an IKE negotiation with each standby SeGW, sequentially,
until the NodeB establishes a temporary IPSec tunnel. Then, the NodeB switches its
services to the temporary tunnel.
2. If the IPSec tunnel between the NodeB and the active SeGW is restored, the NodeB
switches the services back to the IPSec tunnel and removes the temporary tunnel.
This feature applies to intra- or inter-city secure networks.

Copyright © Huawei
Implementation
See IPsec Feature Parameter Description.

 Capacity
No impact.
 Performance
No impact.
Impact on NEs
E8000E and SeMG9811 support the deployment of SeGW.
Impact on Hardware
No impact.

No impact.

The following license control items have been added to accommodate this feature.
Control Item
GBFD-160209 IPSec IPSec BTS Per BTS

Redundancy Redundancy
Among Among Multiple
Multiple SeGWs
SeGWs
WRFD-160274 IPSec IPSec NodeB Per NodeB
Redundancy Redundancy
Multiple SeGWs
SeGWs
LOFD-070211 IPSec IPSec eNodeB (FDD) Per eNodeB
Redundancy Redundancy (FDD)
Multiple SeGWs
SeGWs
TDLOFD- IPSec IPSec eNodeB (TDD) Per eNodeB
070211 Redundancy Redundancy (TDD)
Multiple SeGWs
SeGWs

Copyright © Huawei

Type ID Command
New REDUND ADD BTS/N Indicates the attribute of current IKE

ANCYFL IKEPEER odeB/e peer. When this parameter is set to
AG NodeB None(Non-redundancy), the IPSec
redundancy function is disabled for the
current IKE peer. In the IPSec function,
the current IKE tunnel serves as a slave
IKE peer when any of the following
occurs:
1. IKE SA of slave IKE peer exists (you
can use DSP IKESA to query it).
2. The slave IKE peer is negotiating
(you can use the IKE trace to verify it).
Otherwise, the IKE tunnel serves as a
master IKE peer.
New MASTER ADD BTS/N Indicates the name of the master IKE
PEERNA IKEPEER odeB/e peer to which the current slave IKE peer
ME NodeB corresponds. This parameter takes effect
when the REDUNDANCYFLAG
parameter is set to SLAVE.
New PRIORIT ADD BTS/N Indicates the priority of the current
Y IKEPEER odeB/e slave IKE peer. A small value indicates
NodeB a high priority of the slave IKE peer.
This parameter takes effect when the
REDUNDANCYFLAG parameter is
set to SLAVE.
New IPSECSW SET BTS/N Indicates the switchover from slave IKE
ITCHBAC IKECFG odeB/e peer to master IKE peer after the master
K NodeB IKE peer negotiation recovers in IPSec
redundancy function. If this parameter
is set to OFF and the negotiation on the
master IKE peer fails, the system stops
the negotiation on the master IKE peer
after it performs a switchover from
master IKE peer to slave IKE peers and
one of the slave IKE peer's negotiation
succeeds. After the switchover, the
alarm related to IKE negotiation failure
on the master IKE peer persists. After
the negotiation of slave IKE peers
switch over from success to fail and the
negotiation fails on the IKE peer with
the lowest priority, the system starts the
negotiation on the master IKE peer
immediately even though this parameter

Copyright © Huawei

Type ID Command
is set to OFF, and after the IKE

succeeds, the system performs a
switchover from slave IKE peer to
master IKE peer and clears the alarm
related to IKE negotiation failure on the
master IKE peer.
If this parameter is set to ON and the
fails, the negotiation continues on the
master IKE peer even though the
system performs a switchover from
master IKE peer to slave IKE peer. In
this case, the alarm is cleared only when
the negotiation on the master IKE peer
succeeds. If the value of this parameter
is modified to OFF during a back
switchover via the command SET
IKECFG, the system will stop the
immediately.
New IPSECSB SET BTS/N Indicates the period before a switchover
WAITTIM IKECFG odeB/e from slave to master IKE peer after the
E NodeB IKE negotiation on the master IKE peer
succeeds in IPSec redundancy function.

No impact.
The following alarms have been introduced to accommodate this feature.
Type
Modified ALM-25891 IKE GBTS/NodeB/eNodeB The new alarm

Negotiation Failure parameter Specific
Problem specifies
whether the specific
problem that causes the
alarm is IKE
Negotiation Failure or
IKE Redundancy Loss.


Copyright © Huawei
None
None
Impacted Features
None
Related Operations
See the "Engineering Guidelines" section in IPsec Feature Parameter Description.

IR-V100R009-099
7.2.1.14 WRFD-151210 Inter-Dependence of BBU Uplink Resource
Description
In scenarios where multiple carriers serve the same coverage area, for carriers configured in
the same uplink resource group, each baseband processing board is configured with two
carriers, and every two baseband processing boards share a carrier in chain mode. Uplink CEs
of a baseband processing board serve a maximum of six cells. With the chain mode, uplink
CEs of a baseband processing board can be shared between any cells that are carried by the
baseband processing board, which improves uplink CE sharing.

Copyright © Huawei
Implementation
For details, see Control Channel Interference Cancellation Feature Parameter Description in

 Capacity
This feature improves network KPI performance, such as the RRC connection setup
success rate and RAB assignment success rate. However, if DRD is enabled, this feature
does not significantly improve network KPI performance but relieves imbalances in
traffic loads between carriers caused by uplink CE congestion.
How much this feature affects system capacity depends on the baseband board
configurations in an uplink resource group, number of carriers, and number of uplink
CEs required by carriers.
 Performance
This feature improves network KPI performance, such as the RRC connection setup
success rate and RAB assignment success rate. However, if DRD is enabled, this feature
does not significantly improve network KPI performance but relieves imbalances in
traffic loads between carriers caused by uplink CE congestion.
How much this feature affects network performance depends on the number of baseband
boards in an uplink resource group, number of carriers, and number of uplink CEs
required by carriers.
After this feature is enabled, the time for admission based on uplink CEs is different
between the RNC and NodeB. As a result, there is a low probability that the number of
CNBAP signaling messages received by the NodeB increases. This imposes little impact
on network performance and therefore can be ignored.
Impact on NEs
The RNC and NodeB must both be upgraded to accommodate Inter-Dependence of BBU
Uplink Resource.
Impact on Hardware
The WBBPa board does not support Inter-Dependence of BBU Uplink Resource.

Status information of the switch for controlling Inter-Dependence of BBU Uplink Resource is
added to the NBAP signaling messages that are transmitted over the Iub interface.

An NodeB license control item has been added for this feature.
Table 1.1 License information for the Inter-Dependence of BBU Uplink Resource feature
Item
WRFD-151210 Inter-Dependence Inter-dependence of NodeB per NodeB

Copyright © Huawei

Item
of BBU Uplink BBU uplink resource

Resource (per NodeB)

After Inter-Dependence of BBU Uplink Resource is activated, new cells may preempt
the baseband resources of existing cells. To prevent a large number of call drops, the
preemption is completed within three minutes. New cells become available only after
they preempt the baseband resources.
After Inter-Dependence of BBU Uplink Resource is activated, the cells that were set up
on a deleted baseband board may preempt the baseband resources allocated for cells on
other baseband boards.
Table2 NodeB parameter changes describes the parameter that has been added on the
NodeB side to accommodate Inter-Dependence of BBU Uplink Resource.
Table 1.2 NodeB parameter changes

New ULRESWORKMO SET This parameter specifies

DE(UMTS NODEBALGPARA the uplink resource
NodeB,UMTS allocation mode of a
Micro) NodeB. If the parameter
value is set to
NORMAL, the same
uplink resources are
allocated to all the
boards in a set of uplink
baseband equipment. If
the parameter value is
set to AUTO_CHAIN,
the uplink resources
allocated to a set of
uplink baseband
equipment are
connected as a chain to
improve resource
sharing. If the parameter
value is set to
MANUAL_CHAIN,
the uplink resources can
be manually specified
for the uplink baseband
equipment.

None

Copyright © Huawei
None

None
 WRFD-021308 Extended Cell Coverage up to 200km
If remote cells are configured by adding remote cell groups or changing the cell radius to
more than 30 km, Inter-Dependence of BBU Uplink Resource fails to take effect.
 WRFD-021350 Independent Demodulation of Signals from Multiple RRUs in One Cell
 WRFD-151208 Static Desensitization Based Multi RRUs in One Cell
If any of the mutually exclusive features is activated, cells cannot be deployed in chain mode.
Impacted Features
 WRFD-010209 4-Antenna Receive Diversity
If 4-Antenna Receive Diversity is activated, Inter-Dependence of BBU Uplink Resource
does not improve CE utilization.
 WRFD-020103 Inter Frequency Load Balance
If Inter-Dependence of BBU Uplink Resource is activated, the cell group-level credit
reshuffling algorithm in Inter Frequency Load Balance fails.
 WRFD-010691 HSUPA UL Interference Cancellation
If Inter-Dependence of BBU Uplink Resource is activated and the number of cells served
by the same baseband board exceeds the cancellation capability of the baseband board,
the interference cancellation (IC) function fails for the excess cells.
Related Operations
For details, see "Engineering Guidelines" in Inter-Dependence of BBU Uplink Resource

IR-RAN15.1-027
7.2.1.15 WRFD-151205 Uplink CoMP (Joint Reception)
Description
Uplink CoMP (Joint Reception) is dedicated to improve user experience by increasing users'
throughput. Signals from a UE are received by the uplink receive antennas of multiple cells,
and the received signals are then combined in the BBU. This method increases the signal-to-
noise ratio (SNR) of received signals and improves power efficiency. From ordinary users
perspective, Uplink CoMP (Joint Reception) makes full use of signals from UEs in
neighboring cells to increase system throughput. From power limited users perspective, the
resource saved by them will be used by themselves with high priority. Hence, their throughput
will be further improved compared to that of ordinary users.

Copyright © Huawei
Uplink CoMP (Joint Reception) provides gains in two scenarios: For intra-NodeB CoMP gain,
when a link in the same baseband resource pool as the serving link of a UE is not qualified for
soft or softer handover of the UE, Uplink CoMP (Joint Reception) may still combine the two
links to improve uplink reception quality. For inter-NodeB CoMP gain, while two cells are
belong to two different NodeB, they can be collected with each other by using USUs
(Universal Switching Unit). And with this modification, additional gain can be obtained
because of the extention of CoMP area. In order to obtain this additional gain, Uplink CoMP
(Joint Reception) Based on Coordinated BBU feature need to be actived.
To quickly select proper antennas, the NodeB needs to consume additional resources. In a
neighboring cell that provides a coordinating link for a UE, Uplink CoMP (Joint Reception)
does not set up downlink transmission for the UE, in contrast to the traditional approach of
setting up both uplink and downlink transmission. Therefore, no additional downlink code or
power resources are consumed in the neighboring cell (coordinating cell).
Base on previous description, Uplink CoMP (Joint Reception) performs the following
functions:
 Multiple antennas perform joint reception to improve reception quality.
 While interference cancellation (IC)/control channel parallel interference cancellation
(CCPIC) is enabled, the coordinating cell of a UE will performs IC/CCPIC to reduce the
UE's interference on the coordinating cell.
 The coordinating cell of an HSUPA UE performs MAC-e scheduling for the UE to
reduce the UE's interference on the coordinating cell.
Implementation
For details, see Uplink CoMP Feature Parameter Description in RAN Feature Documentation.

 Capacity
In macro-macro cells, UL CoMP increases the average uplink capacity by 3% to 7.8%
and uplink CEU throughput by 10% to 15%. When both WRFD-151205 Uplink CoMP
(Joint Reception) and WRFD-151207 Uplink CoMP (Joint Reception) based on
Coordinated BBU are enabled, cell information can be exchanged between a cell and
more neighboring cells. In this case, UL CoMP increases the average uplink capacity by
6% to 10% and uplink CEU throughput by 10% to 20%.
In macro-micro cells where the number of macro cells is equal to that of micro cells, UL
CoMP increases the average uplink capacity by around 3% to 5% and uplink CEU
throughput by around 16% to 45%.
 Performance
UL CoMP has no impact on network KPIs.
Coordinating links in UL CoMP consume uplink CE resources. The number of CEs
consumed by coordinating links depends on the number of coordinating links.
The CE consumption rules on coordinating links are as follows:
In four-antenna scenarios: a coordinating link for R99 UEs consumes two CEs, a
coordinating link for HSUPA UEs consumes two CEs by default when SRB over E-DCH

Copyright © Huawei
is enabled, and a coordinating link for HSUPA UEs consumes four CEs by default when
Impact on NEs
This feature is implemented on the NodeB, CME, and U2000.
Impact on Hardware
 WRFD-151205 Uplink CoMP (Joint Reception)
− This feature depends on the UBBPd board. If a cell set up on the UBBPd board
functions only as a coordinating cell, the cell will be counted as an ordinary cell that
is served by the UBBPd board.
− Only the 3900 series base stations support this feature.
 WRFD-151206 HetNet Uplink CoMP (Joint Reception)
is served by the WBBPf board.
 WRFD-151207 Uplink CoMP (Joint Reception) Based on Coordinated BBU
− This feature depends on the UBBPd board and the universal main processing and
transmission unit (UMPT) board.
− This feature depends on the USU.
− If WRFD-151207 Uplink CoMP (Joint Reception) Based on Coordinated BBU is
enabled, the host cell and the coordinating cell must both be configured with either
two or four antennas.

None

A NodeB-level license has been added for this feature to control cell-level or NodeB-
level functions.
Control Item
WRFD-151205 Uplink CoMP Uplink CoMP NodeB per Cell

(Joint (Joint
Reception) Reception) (per
Cell)
WRFD-151206 HetNet Uplink HetNet Uplink NodeB per cell
CoMP (Joint CoMP (Joint
Cell)
WRFD-151207 Uplink CoMP Uplink CoMP NodeB per NodeB

Copyright © Huawei

Control Item
(Joint (Joint
Reception) Reception)
Based on Based on
Coordinated Coordinated
BBU BBU (per
NodeB)

The following command has been introduced on the NodeB side to accommodate this
feature:
Change Type MML Command Description
New ADD Configure a UL CoMP cell

NODEBULCOMPGRP group
The following parameter has been introduced on the NodeB side to accommodate this
feature:
New ULCOMPSW(UMT ADD/MOD Indicates whether a

S NodeB,UMTS ULOCELL cell supports UL
Micro) CoMP. A cell can
serve as a
coordinating cell
only after this switch
is turned on.

The following counters have been introduced on the NodeB side to accommodate this
feature:
Change Type Counter Name Measurement Description
Unit
New VS.UUlCoMPGroup ALGO.UULCOMP Average Number of

.UserNum GROUP CoMP Users in a UL
CoMP Cell Pair
New VS.UUlCoMPGroup ALGO.UULCOMP Maximum Number
.MaxUserNum GROUP of CoMP Users in a
UL CoMP Cell Pair
New VS.ULCoMP.ULCE TRAFFIC.LOCELL Average Number of
.Mean.Shared UL CEs in a Shared
Group Consumed by
UL Coordinating

Copyright © Huawei

Unit
Links
New VS.ULCoMP.ULCE TRAFFIC.LOCELL Maximum Number
.Max.Shared of UL CEs in a
Shared Group
Consumed by UL
Coordinating Links
.Mean.Dedicated UL CEs in a
Dedicated Group
Consumed by UL
Coordinating Links
.Max.Dedicated of UL CEs in a
Dedicated Group
Consumed by UL
Coordinating Links
New VS.ULCoMP.LC.U TRAFFIC.OPERAT Average Number of
LMean.LicenseGrou OR UL CEs Configured
p for an Operator
Consumed by UL
Coordinating Links
New VS.ULCoMP.LC.U TRAFFIC.OPERAT Maximum Number
LMax.LicenseGroup OR of UL CEs
Configured for an
Operator Consumed
by UL Coordinating
Links
p.Shared for an Operator in a
Shared Group
Consumed by UL
Coordinating Links
.Shared Configured for an
Operator in a Shared
Group Consumed by
UL Coordinating
Links
New VS.ULCoMP.HSUP TRAFFIC.OPERAT Average Number of
A.LC.ULMean.Lice OR UL CEs Configured
nseGroup for an Operator
Consumed by UL
Coordinating Links
Carrying HSUPA

Copyright © Huawei

Unit
Services
New VS.ULCoMP.HSUP TRAFFIC.OPERAT Maximum Number
A.LC.ULMax.Licen OR of UL CEs
seGroup Configured for an
Operator Consumed
by UL Coordinating
Links Carrying
HSUPA Services
A.LC.ULMean.Lice OR UL CEs in a Shared
nseGroup.Shared Group Consumed by
UL Coordinating
Links Carrying
HSUPA Services
A.LC.ULMax.Licen OR of UL CEs in a
seGroup.Shared Shared Group
Consumed by UL
Coordinating Links
Carrying HSUPA
Services
New VS.ULCoMP.CE.U TRAFFIC.BOARD Average Number of
LMean.Board UL CEs Consumed
by UL Coordinating
Links on the
Baseband Board
New VS.ULCoMP.CE.U TRAFFIC.BOARD Maximum Number
LMax.Board of UL CEs
Consumed by UL
Coordinating Links
on the Baseband
Board
New VS.ULCoMP.CE.U TRAFFIC.ULGRO Average Number of
LMean.UlGroup UP UL CEs in a UL
Resource Group
Consumed by
Coordinating Links
for All Cells
New VS.ULCoMP.CE.U TRAFFIC.ULGRO Maximum Number
LMax.UlGroup UP of UL CEs in a UL
Resource Group
Consumed by
Coordinating Links
for All Cells

Copyright © Huawei

None

None
None
This feature depends on WRFD-151205 Uplink CoMP (Joint Reception) and WRFD-
151206 HetNet Uplink CoMP (Joint Reception).
− Macro-macro or micro-micro cells on different BBUs can obtain UL CoMP gains
only when both WRFD-151207 Uplink CoMP (Joint Reception) Based on
Coordinated BBU and WRFD-151205 Uplink CoMP (Joint Reception) are activated.
− Macro-micro cells on different BBUs can obtain UL CoMP gains only when both
WRFD-151207 Uplink CoMP (Joint Reception) Based on Coordinated BBU and
WRFD-151206 HetNet Uplink CoMP (Joint Reception) are activated.
WRFD-151205 Uplink CoMP (Joint Reception), WRFD-151206 HetNet Uplink CoMP (Joint
Reception), and WRFD-151207 Uplink CoMP (Joint Reception) Based on Coordinated BBU
are mutually exclusive with the following features:
Impacted Features
WRFD-150222 HSUPA Time-Division Scheduling: HSUPA time-division scheduling will not
take effect on UL CoMP (Joint Reception) UEs whose physical links and coordinating links
are on the same BBU.
− WRFD-150201 Macro & Micro Co-carrier Uplink Interference Control: In macro-
micro cells, WRFD-151206 HetNet Uplink CoMP (Joint Reception) and WRFD-
150201 Macro & Micro Co-carrier Uplink Interference Control have the opposite
effects on each other. Therefore, these two features are not advised to be enabled at
the same time for a cell. In addition, capacity gains of WRFD-151206 HetNet Uplink
CoMP (Joint Reception) are higher than that of WRFD-150201 Macro & Micro Co-
carrier Uplink Interference Control, so preferentially enable WRFD-151206 HetNet
Uplink CoMP (Joint Reception).
− WRFD-150222 HSUPA Time-Division Scheduling: HSUPA time-division scheduling
will not take effect on UL CoMP (Joint Reception) UEs whose physical links and
coordinating links are on the same BBU.
None

Copyright © Huawei
Related Operations
For details, see "Engineering Guidelines" in Uplink CoMP Feature Parameter Description of

IR-V100R009-018
7.2.1.16 WRFD-151206 HetNet Uplink CoMP (Joint Reception)
Description
HetNet Uplink CoMP (Joint Reception) is dedicated to improve user experience by increasing
users' throughput. Signals from a UE are received by the uplink receive antennas of multiple
cells, and the received signals are then combined in the BBU. This method increases the
signal-to-noise ratio (SNR) of received signals and improves power efficiency. From ordinary
users perspective, Uplink CoMP (Joint Reception) makes full use of signals from UEs in
neighboring cells to increase system throughput. From power limited users perspective, the
resource saved by them will be used by themselves with high priority. Hence, their throughput
will be further improved compared to that of ordinary users.
HetNet Uplink CoMP (Joint Reception) provides gains in two scenarios: For intra-NodeB
CoMP gain, when a link in the same baseband resource pool as the serving link of a UE is not
qualified for soft or softer handover of the UE, Uplink CoMP (Joint Reception) may still
combine the two links to improve uplink reception quality. For inter-NodeB CoMP gain,
while two cells are belong to two different NodeB, they can be collected with each other by
using USUs (Universal Switching Unit). And with this modification, additional gain can be
obtained because of the extention of CoMP area. In order to obtain this additional gain,
Uplink CoMP (Joint Reception) Based on Coordinated BBU feature need to be actived.
To quickly select proper antennas, the NodeB needs to consume additional resources. In a
neighboring cell that provides a coordinating link for a UE, HetNet Uplink CoMP (Joint
Reception) does not set up downlink transmission for the UE, in contrast to the traditional
approach of setting up both uplink and downlink transmission. Therefore, no additional
downlink code or power resources are consumed in the neighboring cell (coordinating cell).
Base on previous description, HetNet Uplink CoMP (Joint Reception) performs the following
functions:
 Multiple antennas perform joint reception to improve reception quality.
 While interference cancellation (IC)/control channel parallel interference cancellation
(CCPIC) is enabled, the coordinating cell of a UE will performs IC/CCPIC to reduce the
UE's interference on the coordinating cell.
 The coordinating cell of an HSUPA UE performs MAC-e scheduling for the UE to
reduce the UE's interference on the coordinating cell.
Implementation

 Capacity

Copyright © Huawei

 Performance
Impact on NEs
Impact on Hardware

Copyright © Huawei

None

level functions.
Control Item

(Joint (Joint
Cell)
Cell)
(Joint (Joint
Based on Based on
BBU BBU (per
NodeB)

feature:

feature:

serve as a
coordinating cell
is turned on.

Copyright © Huawei

feature:
Unit

CoMP Cell Pair
UL CoMP Cell Pair
Group Consumed by
UL Coordinating
Links
Shared Group
Consumed by UL
Coordinating Links
Dedicated Group
Consumed by UL
Coordinating Links
Dedicated Group
Consumed by UL
Coordinating Links
p for an Operator
Consumed by UL
Coordinating Links
Configured for an
Operator Consumed
by UL Coordinating
Links
Shared Group

Copyright © Huawei

Unit
Consumed by UL
Coordinating Links
Group Consumed by
UL Coordinating
Links
Consumed by UL
Coordinating Links
Carrying HSUPA
Services
Operator Consumed
by UL Coordinating
Links Carrying
HSUPA Services
UL Coordinating
Links Carrying
HSUPA Services
Consumed by UL
Coordinating Links
Carrying HSUPA
Services
by UL Coordinating
Links on the
Baseband Board
Consumed by UL
Coordinating Links
on the Baseband

Copyright © Huawei

Unit
Board
Resource Group
Consumed by
Coordinating Links
for All Cells
Resource Group
Consumed by
Coordinating Links
for All Cells

None

None
None
Impacted Features

Copyright © Huawei

None
Related Operations

IR-V100R009-018
7.2.1.17 WRFD-151207 Uplink CoMP (Joint Reception) Based on

Coordinated BBU
Description
Based on Multi-BBU Interconnection, this feature enables Uplink CoMP (Joint Reception)
and HetNet Uplink CoMP (Joint Reception) to work in cells under different BBUs. Therefore,
cell selection becomes more flexible.
Implementation

 Capacity

Copyright © Huawei
 Performance
Impact on NEs
Impact on Hardware

None


Copyright © Huawei
level functions.
Control Item

(Joint (Joint
Cell)
Cell)
(Joint (Joint
Based on Based on
BBU BBU (per
NodeB)

feature:

feature:

serve as a
coordinating cell
is turned on.

feature:

Copyright © Huawei

Unit

CoMP Cell Pair
UL CoMP Cell Pair
Group Consumed by
UL Coordinating
Links
Shared Group
Consumed by UL
Coordinating Links
Dedicated Group
Consumed by UL
Coordinating Links
Dedicated Group
Consumed by UL
Coordinating Links
p for an Operator
Consumed by UL
Coordinating Links
Configured for an
Operator Consumed
by UL Coordinating
Links
Shared Group
Consumed by UL
Coordinating Links

Copyright © Huawei

Unit

Group Consumed by
UL Coordinating
Links
Consumed by UL
Coordinating Links
Carrying HSUPA
Services
Operator Consumed
by UL Coordinating
Links Carrying
HSUPA Services
UL Coordinating
Links Carrying
HSUPA Services
Consumed by UL
Coordinating Links
Carrying HSUPA
Services
by UL Coordinating
Links on the
Baseband Board
Consumed by UL
Coordinating Links
on the Baseband
Board
Resource Group
Consumed by

Copyright © Huawei

Unit
Coordinating Links
for All Cells
Resource Group
Consumed by
Coordinating Links
for All Cells

None

None
None
Impacted Features

Copyright © Huawei

None
Related Operations

IR-V100R009-018
7.2.1.18 WRFD-151208 Macro-Micro Multi RRUs in One Cell
Description
After the Macro-Micro Multi RRUs in One Cell feature is activated in a multi-RRU cell with
uneven RRU power, the BBU automatically obtains the actual transmit power of each
antenna, noise factor, and uplink diversity gains of each RRU in the cell, and identifies high-
power and low-power RRUs. The BBU also calculates digital attenuation and desensitization
values for the low-power RRUs, sends the values to relevant RRUs, and implements digital
attenuation and desensitization on the uplink receive channel. During this process, 30 dB total
attenuation and desensitization are supported. Therefore, Macro-Micro Multi RRUs in One
Cell applies to cells in which the downlink inter-RRU power difference reaches 30 dB.
A multi-RRU cell with uneven RRU power
Digital attenuation decreases the received total wideband power (RTWP) of low-power RRUs
to which digital desensitization has been applied. This eliminates negative effects of low-
power RRUs on coverage and capacity of high-power RRUs.
Digital desensitization decreases the uplink signal-to-noise ratio (SNR) of low-power RRUs
by artificially increasing the background noise of these RRUs. This function reduces

Copyright © Huawei
interference from UEs served by high-power RRUs in a neighboring cell on low-power RRUs
in the current serving cell.
Implementation
For details, see Macro-Micro Multi RRUs in One Cell Feature Parameter Description in RAN

 Capacity
The Macro-Micro Multi RRUs in One Cell feature cancels uplink interference caused by
different RRU power in a cell. Compared with the deployment with only one RRU in
one cell, this feature increases or retains uplink capacity if UEs are unevenly distributed
to the RRUs in a cell.
Uplink capacity gains yielded by this feature for a multi-RRU cell vary depending on the
position, coverage area, power, neighboring cell relationships, and absorbed traffic
volume of each RRU, but the gains cannot be quantified
Compared with the deployment with only one RRU in one cell, this feature decreases the
downlink capacity.
 Performance
Performance gains yielded by this feature for a multi-RRU cell vary depending on the
position, coverage area, power, neighboring cell relationships, and absorbed traffic volume of
each RRU, but performance gains cannot be quantified.
Compared with the deployment with only one RRU in one cell, activating Macro-Micro Multi
RRUs in One Cell has the following impacts on network performance:
 Network KPIs
− Coverage: Ec/Io in downlink coverage improves due to a decrease in inter-cell
interference. Uplink coverage provided by high-power RRUs improves, and uplink
coverage provided by low-power RRUs may shrink because of desensitization.
− Call drop rate: It remains the same or slightly improves because of decreased inter-
cell interference.
− Access success rate: It remains the same or slightly improves because of decreased
inter-cell interference.
− Handover success rate: It remains the same or slightly improves because of decreased
inter-cell interference.
 Resource usage
− Power resources: The usage of power resources increases given that total RRU
throughput remains the same.
− Channel element (CE) resources: Uplink CE usage remains the same given that total
RRU throughput remains the same.
− Code resources: Code resource usage increases given that total RRU throughput
remains the same.
− Transport resources: Iub resource usage remains the same given that total RRU
throughput remains the same.
 User experience
User experience improves if the capacity is unlimited:
− Uplink user throughput increases or remains the same.

Copyright © Huawei
− Downlink user throughput increases.

 Others
Activating this feature sometimes decreases HSUPA throughput for cell edge users that
are served by low-power RRUs because digital desensitization deteriorates the uplink
SIR of low-power RRUs.
Impact on NEs
This feature is implemented on the NodeB. The license and switch for this feature must be
configured on both the U2000 and the CME.
Impact on Hardware
 Only the DBS3900 configured with the WBBPb, WBBPd, WBBPf, or UBBP board
supports this feature.
 The requirements for RRUs are as follows:
1. RRU3824, RRU3826, RRU3828, RRU3829, RRU3926, RRU3928, RRU3929,
RRU3938, and RRU3939 support digital attenuation and desensitization and therefore
can be configured as either high-power or low-power RRUs in a cell.
2. Other RRUs do not support digital attenuation or desensitization and therefore can be
configured only as high-power RRUs. If an RRU that does not support digital attenuation
or desensitization is configured as a low-power RRU, the RNC reports ALM-28206
Local Cell Capability Decline.
 The RRU3821E, RFU, and AAS do not support this feature.

None

An RRU- and cell-level license control item has been introduced on the NodeB side for
this feature.
Feature ID Feature Name License Name NE Sales Unit
WRFD-151208 Macro-Micro Macro-Micro NodeB per RRU per

Multi RRUs in multi RRUs in cell
One Cell one cell (per
Cell*RRU)

The following parameter has been added on the NodeB side to accommodate this feature.
New MULTIRRUSTATI ADD/MOD Indicates whether to

CDESSW(UMTS ULOCELL enable Macro-Micro
NodeB,UMTS Multi RRUs in One
Micro) Cell

Copyright © Huawei

None
None

The Macro-Micro Multi RRUs in One Cell feature depends on the feature WRFD-021350
Independent Demodulation of Signals from Multiple RRUs in One Cell.
This feature is mutually exclusive with the following features:
 WRFD-010203 Transmit Diversity
 WRFD-010209 4-Antenna Receive Diversity
 WRFD-010684 2x2 MIMO
 WRFD-010692 HSUPA FDE
 WRFD-010701 Uplink Enhanced CELL_FACH
 WRFD-010205 Cell Digital Combination and Split
 0.5/0.5 Configuration
In addition, it is good practice to maintain the default RF desensitization intensity (0 dB) after
this feature is deployed due to the following reasons:
 The RF desensitization intensity can be set only to 0 dB or 10 dB.
 Accuracy in RF desensitization is low.
 RF desensitization affects the noise factor and therefore negatively affects the
performance of this feature.
Impacted Features
None
Related Operations
For details, see "Engineering Guidelines" in Macro-Micro Multi RRUs in One Cell Feature

IR-RAN15.1-025
7.2.1.19 WRFD-151209 Macro-Micro DC-HSDPA
Description
 Configuration of primary and secondary cells

Copyright © Huawei
In scenarios where the Macro-Micro DC-HSDPA feature applies, the downlink

frequency of the micro cell serves as the primary carrier of each DC-HSDPA UE, and the
downlink frequency of the macro cell serves as the secondary carrier of each DC-HSDPA
UE. Only the uplink frequency of the micro cell serves as the uplink frequency of each
DC-HSDPA UE.
Both the macro and micro cells are configured with the PCPICH, SCH, PCCPCH,
SCCPCH, and PRACH. Both cells are configured with the common channels required
for camping and service initiation. A single-carrier (SC) UE can also camp and initiate
services in both the macro and micro cells.
 Differentiated service carrying policy
The differentiated service carrying policy is the same as that used by DC-HSDPA.
 Mobility management
The active set information and measurement reports are transmitted on the primary
carrier during the DC-HSDPA handover. If the frequency of the primary carrier is the
same as that of the neighboring cell, this handover is an intra-frequency handover. If not,
this handover is an inter-frequency handover.
To ensure seamless coverage for DC UEs, this feature enables handovers between DC
cells, between DC and SC cells, and between DC cells and inter-RAT cells.
 State transition for DC-HSDPA UEs
The state transition process is the same as that for SC-HSDPA UEs.
 Service steering
The service steering policy is the same as that used by DC-HSDPA.
The secondary carrier for Macro-Micro DC-HSDPA does not support space time transmit
diversity (STTD).
Implementation
For details, see Macro-Micro DC-HSDPA Feature Parameter Description in RAN Feature
Documentation.

 Capacity
Macro-Micro DC-HSDPA provides the following benefits:
− Single-user throughput
The downlink peak throughput of UEs increases. The amount of the increase depends
on the channel quality of the cell.
For the macro cell added when Macro-Micro DC-HSDPA is enabled, if the channel
quality indicator (CQI) of the macro cell is the same as or better than that of the
original micro cell when SC-HSDPA is enabled, the downlink peak throughput of
UEs increases by at least 100%.
After Macro-Micro DC-HSDPA is enabled, if 64QAM is used, the downlink peak
throughput of a UE in the center of a micro cell increases by 21 Mbit/s theoretically.
As a result, the transmission delay is reduced and user experience is improved.
− Cell throughput
Macro-Micro DC-HSDPA does not reduce the total throughput of two inter-frequency
cells, one of which is within the coverage of the other.

Copyright © Huawei
A DC-HSDPA UE has the HS-DPCCH only in its primary cell. Therefore, the uplink
load of a cell serving as a DC-HSDPA UE's primary cell is higher than that of a cell
serving as the SC-HSDPA cell.
If the DC-HSDPA UE penetration rate is 100% in the primary cell and the SC-
HSDPA UE penetration rate is 100% in the SC-HSDPA cell, the uplink load of the
primary cell is 5%-10% higher than that of the SC-HSDPA cell and the uplink
throughput decreases about 1%.
A DC-HSDPA UE consumes one more channel element (CE) than an SC-HSDPA UE.
 Performance
Macro-Micro DC-HSDPA has the same impact on the cell uplink load and cell downlink
load as DC-HSDPA. For details about the impact, see DC-HSDPA Feature Parameter
Description.
Impact on NEs
Macro-Micro DC-HSDPA is implemented on the RNC and NodeB.
Impact on Hardware
Macro-Micro DC-HSDPA requires that the downlink baseband resources of macro and micro
cells be provided by the same downlink resource group.
Only 3900 series base stations (except the BTS3902E) support this feature. To support this
feature, the base station must be configured with the WBBPb, WBBPd, WBBPf, or UBBP
board .

No impact.

A cell-level license control item has been added to the NodeB for this feature.
Feature ID Feature Name License Control Item NE Sales
Unit
WRFD-151209 Macro-Micro Macro-Micro DC-HSDPA NodeB Per cell

DC-HSDPA

The following parameter has been modified on the NodeB side to accommodate this
feature.
Change Type Parameter MML Change Description
ID Command
Modified ULOCELLRE ADD/RMV/LS The number of cells that can be

F T configured in a multi-carrier cell
NodeBMultiCel group increases to six.
lGrpItem

Copyright © Huawei

This feature inherits the counters of DC-HSDPA and has no impact on the counters on
the RNC or NodeB side.
This feature inherits the alarms of DC-HSDPA and has no impact on the alarms on the
RNC or NodeB side.

WRFD-010696 DC-HSDPA Introduction Package
WRFD-021308 Extended Cell Coverage up to 200 km
Impacted Features
Macro-Micro DC-HSDPA is affected by the following features:
 WRFD-010617 VoIP over HSPA/HSPA+
− Macro-Micro DC-HSDPA cannot be used for a single voice over IP (VoIP) service.
− Macro-Micro DC-HSDPA can be used for VoIP+PS BE or VoIP+streaming combined
services.
 WRFD-010619 CS voice over HSPA/HSPA+
− Macro-Micro DC-HSDPA cannot be used for a single CS service.
− Macro-Micro DC-HSDPA can be used for CS+PS BE or CS+streaming combined
services.
 WRFD-020134 Push to Talk
− Macro-Micro DC-HSDPA cannot be used for a single push to talk (PTT) service.
− Macro-Micro DC-HSDPA can be used for PTT+PS BE or PTT+streaming combined
services.
Macro-Micro DC-HSDPA affects the following feature:
 WRFD-150208 Flexible Dual Carrier HSDPA
When these two features are used together, a micro cell only serves as a candidate cell for
Flexible Dual Carrier HSDPA. Flexible Dual Carrier HSDPA supports only intra-band flexible
selection and does not support inter-band flexible selection.
Related Operations
For details, see "Engineering Guidelines" in Macro-Micro DC-HSDPA Feature Parameter
Description of RAN Feature Documentation.

IR-RAN15.1-026

Copyright © Huawei
7.2.1.20 WRFD-160250 Interference Rejection Combining
Description
For strong interference from neighboring cells or other external sources, this feature uses a
blind algorithm to estimate the spatial and temporal correlation between interfering signals.
The blind algorithm uses the maximum signal to interference plus noise ratio (SINR) instead
of the maximum signal-to-noise ratio (SNR) to mitigate the interference for better
demodulation performance, thereby improving the uplink cell capacity.
This feature consists of four steps: interference measurement, cell selection, UE selection, and
interference suppression and combination. This feature estimates the spatial and temporal
correlation between interfering signals in all cells, selects the target cells and UEs for
interference suppression and combination, and then performs interference suppression and
combination.
When the interference in a cell that is caused by its neighboring cells or other external sources
is slightly greater than or equal to half of the received total wideband power (RTWP) in the
cell, this feature can improve the cell throughput by 5% to 15%.
Implementation
For details, see Interference Rejection Combining Feature Parameter Description in RAN

 Capacity
This feature increases the cell throughput by 5% to 15% when the following conditions are
met:
 There is interference from neighboring cells or external interference.
 The interfering signal sources are less than or equal to two.
 The value of interference from neighboring cells or external interference divided by the
background noise is greater than or equal to 3 dB.
 UEs are experiencing full buffer traffic.
 Performance
None
Impact on NEs
Impact on Hardware
NodeBs must be configured with UBBPd boards.

None

Copyright © Huawei

None
Table 9-8 lists the parameter change in this feature.
Table 1.1 Parameter change

Change Type Parameter ID MML NE Description
Command
New IRCSW ADD RNC Switch for

ULOCELL controlling IRC
MOD
ULOCELL
LST
ULOCELLDS
P ULOCELL
Table 9-9 lists the counter change in this feature.
Table 1.2 Counter change

Change Type Counter Measurement NE Description
Name Unit
New VS.IRC.UserN ALGO.LOCEL NodeB Average

um L number of UEs
using IRC in a
cell

On the NodeB side, the following alarm reporting scenario is added to ALM-28206 Local Cell
Capability Decline for this feature: This alarm is reported when a user configures IRC but the
local cell does not support this function.

None
None
Impacted Features
IRC is not allowed when this feature is enabled.

Copyright © Huawei
 WRFD-010205 Cell Digital Combination and Split

IRC can be enabled but its algorithm does not take effect.
 WRFD-150206 Turbo IC
Turbo IC supports interference cancelation for multiple times. However, if both IRC and
Turbo IC are enabled, Turbo IC can perform interference cancelation for only once. If
there is no interference from neighboring cells or external interference but IRC is
mistakenly enabled, the gains of Turbo IC decrease.
 WRFD-140225 Narrowband Interference Suppression
Both IRC and Narrowband Interference Suppression can suppress narrowband
interference. When both features are enabled in areas with strong narrowband
interference, the gains of IRC decrease because Narrowband Interference Suppression
suppresses interference earlier than IRC does.
 WRFD-151205 Uplink CoMP (Joint Reception), WRFD-151206 HetNet Uplink CoMP
(Joint Reception), and WRFD-151207 Uplink CoMP (Joint Reception) Based on
Coordinated BBU
When UL CoMP is enabled, strong interfering signals from neighboring cells are
considered as the signals of the serving cell. These interfering signals contain effective
signals same as those sent to the serving cell. UL CoMP combines the effective signals
from neighboring cells and those from the serving cell, which achieves a better SINR of
the effective signals. However, IRC cannot combine both signals. Therefore, when both
features are enabled, the gains of IRC in suppressing interference from neighboring cells
decrease. The gains of IRC in suppressing external interference do not decrease.
Related Operations
For details, see "Engineering Guidelines" in Interference Rejection Combining Feature

IR-V100R009-003
7.2.2 Modified Features and Functions

7.2.2.1 Flexible Frequency Bandwidth of UMTS Carrier (GU Refarming 4.2
MHz)
Description
Scenario: Outdoor macro base stations 1900 MHz (UMTS 4.2 MHz) have been deployed.
Indoor LampSite network performance is mainly affected by interference between the
adjacent GSM 1900 MHz and UMTS 1900 MHz systems. Flexible frequency bandwidth of
UMTS carrier helps reduce inter-system interference and improve network.
Implementation
Optimizing pRRU receive downlink and uplink transmit filter improves interference between
the GSM 1900 MHz system and UMTS 1900 MHz system.

Copyright © Huawei

 Impacts on network capacity
Compared to the standard bandwidth 5.0 MHz, UMTS 4.2 MHz can save four GSM
frequencies, not only achieving UMTS HSPA coverage, but also increasing the number of
available GSM frequencies after refarming.
This feature allocates non-standard bandwidth of 4.2 MHz to UMTS, which reduces the GSM
network capacity. However, this feature significantly improves the capacity of GSM and
UMTS networks as a whole because UMTS has much higher spectral efficiency than GSM.
From the view of GU network overall capacity, the existing GSM network capacity has
improved significantly.
 Impacts on network performance
− The throughput of UMTS HSPA services decreases because the GSM and UMTS
networks interfere with each other and the UMTS network uses a 4.2 MHz static
filter. When the users covered by a neighboring frequency of the outdoor GSM macro
base stations enter the pRRU coverage area that has the smaller pathloss distance, the
UMTS overall network performance may deteriorate seriously.
− The throughput of GSM EDGE services decreases because of UMTS interference.
− The MOSs of GSM and UMTS decrease.
− GSM KPIs are adversely affected because the frequency reuse pattern for GSM may
become tight after this feature is deployed.
Impact on NEs
None
Impact on Hardware
 This feature depends on the pRRU3901 1900 MHz band.
 This feature does not support non-standard UMTS 4.2 MHz bandwidth in one UL RF
daughter board.
 This feature does not support dual non-standard UMTS 4.2 MHz bandwidth in one RF
daughter board.

None

This feature requires the license for WRFD-021001 flexible carrier bandwidth.
Run the MML command SET FREQBWH with FMBWH (the parameter name on the
CME is Frequency Min Bandwidth) set to 4200.
None
None

Copyright © Huawei

None
Related Operations
None

IR-0000282146
Feature ID
WRFD-021001
7.2.2.2 Deleted Mutual Exclusive Relationships Between the FDE Feature

and the Features Related to the Multi-RRU Cell or Mixed Multi-RRU Cell
Description
The NodeB deletes mutual exclusive relationships between the WRFD-010692 HSUPA FDE
feature and the following two features related to the multi-RRU cell or mixed multi-RRU cell:
 WRFD-141202 Independent Demodulation of Signals from Multiple Small Cell RRUs
in One Cell
This deletion allows the FDE feature to be used in multi-RRU cell or mixed multi-RRU cell
scenarios.
Implementation
The NodeB graphical user interface (GUI) is modified to allow operators to configure the
FDE feature for a multi-RRU cell or mixed multi-RRU cell.
For the Independent Demodulation of Signals from Multiple Small Cell RRUs in One Cell
feature, when the CELLTYPE parameter in the ADD ULOCELL or MOD ULOCELL
command is set to MIXED_MULTIRRU_CELL, the FDEMODE parameter is masked
under the associated branch parameters in an earlier version.
In this change, the FDEMODE parameter is added under the associated branch parameters so
that the FDE feature can be configured on the GUI.

The FDE feature effectively suppresses multipath interference. Therefore, enabling this
feature for a multi-RRU cell or mixed multi-RRU cell helps enhance the cell capacity and
coverage.
Multipath interference greatly affects the throughput of HSUPA high-speed users. Therefore,
enabling the FDE feature significantly increases the uplink throughput. In radio environments
with multipath propagation, this feature increases the uplink peak rate of HSUPA users by a
maximum of 20%.

Copyright © Huawei
Impact on NEs
This change is implemented on the NodeB, and therefore there is an impact on the NodeB.
Impact on Hardware
If the FDE feature is enabled for a multi-RRU cell (the CELLTYPE parameter is set to
MULTIRRU_CELL), the WBBPd (or WBBPf) and UBBPd (or UBBP) boards must be
configured.
If the FDE feature is enabled for a mixed multi-RRU cell (the CELLTYPE parameter is set to
MIXED_MULTIRRU_CELL), the WBBPf and UBBP boards must be configured.

None

N/A
The NodeB GUI is modified. Specifically, when the CELLTYPE parameter in the ADD
ULOCELL or MOD ULOCELL command is set to MIXED_MULTIRRU_CELL,
the FDEMODE parameter is added under the associated branch parameters. This
parameter can be set to FALSE or TRUE. By default, it is set to FALSE.
There is an impact on NodeB traffic statistics. Specifically, the statistical method for the
NodeB counter VS.HSUPA.FDE.UtilizeTimePermillage (related to the FDE feature) is
changed so that the measurement of this counter is also triggered in a multi-RRU cell
and mixed multi-RRU cell.
If a mixed multi-RRU cell served by a LampSite base station is allowed to be configured
with the FDE feature, related alarms are reported and cleared in the same way as that for
a multi-RRU cell served by a macro base station. Specifically, if the number of allocated
licenses for the FDE feature is insufficient, the multi-RRU cell experiences FDE
deterioration and reports ALM-26811 Configured Capacity Limit Exceeding Licensed
Limit.

None
Related Operations
 Activation
For the 3900 series base station (including the macro base station and LampSite base station),
if the cell is a multi-RRU cell or mixed multi-RRU cell, perform the following operation to
activate the FDE feature:
Run the MOD ULOCELL command with FDE set to TRUE.
MML command example:

Copyright © Huawei
MOD ULOCELL: ULOCELLID=1, FDEMODE=TRUE;

 Activation observation
1. Query the feature switch configuration.
For the 3900 series base station (including the macro base station and LampSite base
station), run the DSP ULOCELL command to query configurations of the local cell.
Excepted result: If FDE Capability is Enable, the feature switch configuration has
taken effect.
2. Observe the value of the NodeB counter VS.HSUPA.FDE.UtilizeTimePermillage.
If the counter has a none-zero valid value, this feature has been activated.
 Deactivation
For the 3900 series base station (including the macro base station and LampSite base station),
if the cell is a multi-RRU cell or mixed multi-RRU cell, perform the following operation to
deactivate the feature:
Run the MOD ULOCELL command with FDE set to FALSE.
MML command example:
MOD ULOCELL: ULOCELLID=1, FDEMODE=TRUE;

DTS: DTS2014012400606
7.2.2.3 Intelligently Out of Service
Description
The WRFD-031000 Intelligently Out of Service feature has been enhanced to enable the
NodeB pilot power to gradually increase when the local cell is unblocked. This feature
enables smooth handovers from neighboring GERAN or UTRAN cells to cells served by the
NodeB, and prevents the pilot power from directly rising to the maximum level. Direct rise of
the pilot power to the maximum level will cause interference and thereby lead to dropped
calls in neighboring UTRAN cells.
Implementation
When the local cell is unblocked, the pilot power gradually rises based on parameter settings
of the Intelligently Out of Service feature.

The Intelligently Out of Service feature prevents intra-frequency interference towards
neighboring cells when the local cell is unblocked, thereby reducing the interference-induced
dropped calls in the neighboring intra-frequency cells. This feature gradually raises the pilot
power, which increases the recovery time of services for the local cell.
Impact on NEs
None

Copyright © Huawei
Impact on Hardware
None

None

None
None
None
None

None
Related Operations
Same as operations for the Intelligently Out of Service feature in V100R008.

OR: 201303185428
7.2.2.4 Enhanced NodeB Maintenance and Test
Description
This feature streamlines the architecture of NodeB operation and maintenance (O&M) so that
the maintenance and test mechanism is more efficient and easier to use. This feature includes
the following:
 Enhanced GUI and mechanism for user tracing
Collecting and reading data involved in user tracing becomes easy. Data is still available
even during periods of network congestion.
 Streamlined structure of the call history record (CHR) logs
The data collecting capability is enhanced for CHR logs in default settings to improve
efficiency in locating faults.
Implementation
In V100R009,
 Enhanced GUI and mechanism for user tracing

Copyright © Huawei
− On the WebLMT GUI, four check boxes are added for operators to collect fault data
based on fault types.
− The frequently used trace items are renamed in compliance with 3GPP specifications.
− The trace items are separated into normal-level fields and detail-level fields. The
frequently used fields are defined in the normal-level trace items and comply with
3GPP specifications. The detailed fields are defined in the detail-level trace items.
− When the traffic load is high, operators can select only the normal-level trace items.
 Streamlined structure of CHR logs
− More contents are added to CHR logs in default settings to facilitate fault locating.
− The newly added CHR logs do not affect service performance.

 Capacity
None
 Performance
None
Impact on NEs
N/A
Impact on Hardware
The WBBPb and WBBPd boards support enhanced call detail trace (CDT).
The WBBPf and UBBPd boards do not support enhanced CDT.
The WBBPb, WBBPd, WBBPf, and UBBPd boards support enhanced CHR.

None

N/A
N/A
N/A
The GUI related to user tracing on the WebLMT has been changed.

None

Copyright © Huawei
Related Operations
1. On the Basic tab, the KPI SRB, KPI TRB, HSUPA, and HSDPA check boxes are
added. Operators can select multiple check boxes to trace specific fault types.
 When operators modify the settings of Fault Type on the Basic tab, the trace types
specified on the Iub and Uu tabs are automatically cleared, while the trace items are
automatically reselected based on the modified settings of Fault Type.
 If operators fine-tune the trace types on the Iub and Uu tabs after setting the Fault Type,
all of the Fault Type check boxes will be automatically cleared.
 If multiple check boxes are selected in the Fault Type pane, the trace results include all
faults of the corresponding fault types.
2. The trace items on the User Trace window are renamed in compliance with 3GPP
specifications to maintain industry standards.

Copyright © Huawei

IR-V100R009-102
7.2.2.5 New Parameter USERLABEL for SRAN MOs
Description
An optional parameter USERLABEL is added to the following MOs: OMCH, OMCH6,
RSCGRP, AAL2PATH, DEVIP, and DEVIP6. This parameter is used to label transmission
objects.
Implementation
The USERLABEL parameter is added to the following MOs: OMCH, OMCH6, RSCGRP,
AAL2PATH, DEVIP, and DEVIP6. The value of this parameter can be modified using an
ADD or MOD MML command and can be queried using an LST MML command. For
example, for the OMCH MO, the value of the USERLABEL parameter can be modified
using the ADD OMCH or MOD OMCH MML command and can be queried using the LST
OMCH MML command.

None.
Impact on NEs
None.
Impact on Hardware
None.

The USERLABEL parameter is added to the following MOs: OMCH, OMCH6, RSCGRP,
AAL2PATH, DEVIP, and DEVIP6. The MOD DEVIP command is added to the DEVIP MO
and the MOD DEVIP6 command is added to the DEVIP6 MO.

Copyright © Huawei
Impact on Operation and Maintenance.

N/A.
The USERLABEL parameter and the MOD DEVIP and MOD DEVIP6 commands are
added.
None.
None.

None.
Related Operations
None.

IR-SRAN90-OM-009
7.2.2.6 Optimized RET Management
Description
If an incorrect configuration file is loaded for an RET subunit, the actual and configured tilts
of this RET subunit will be inconsistent, which affects network coverage.
Before this feature is introduced, users can find out whether the loaded configuration file is
correct only by checking the file name in the corresponding download command in the RET
operation log.
After the introduction of this feature, the information about the latest successful download of
the configuration file is saved onto the base station. Therefore, users can find out whether the
loaded configuration file is correct simply by using an MML command, which improves RET
management efficiency.
Implementation
When a configuration file is successfully loaded for an RET subunit, the file name and load
time are saved on the base station.
 For the NodeB, eNodeB, and BTS3900, the saved file name and load time can be queried
using the DSP RETSUBUNIT command.
 For the GBTS, the saved file name and load time can be queried using the DSP
BTSRETSUBUNIT command.

Copyright © Huawei

None
Impact on NEs
None
Impact on Hardware
None

None
Impact on Operation and Maintenance.

N/A
None
None
None

None
Related Operations
To query the dynamic information about an RET subunit:
 For the NodeB, eNodeB, and BTS3900, run the DSP RETSUBUNIT command.
 For the GBTS, run the DSP BTSRETSUBUNIT command.

IR-SRAN90-OM-010
7.2.2.7 Support for More ACL Rules in an ACL
Description
The maximum number of ACL rules contained in an ACL for IPv4 increases from 128 to 512.

Copyright © Huawei
Implementation
The number of ACL rules supported by a UMPTa/UMPTb/LMPT/UTRPc in an
eGBTS/NodeB/eNodeB (FDD)/eNodeB (TDD) increases from 128 to 512.

The maximum number of ACL rules contained in an ACL for IPv4 increases from 128 to 512.
Impact on NEs
The maximum number of ACL rules supported by an eGBTS/NodeB/eNodeB (FDD)/eNodeB
(TDD) increases.
Impact on Hardware
The maximum number of ACL rules supported by a UMPTa/UMPTb/LMPT/UTRPc
increases.

None.

N/A.
None.
None.
None.

None.
Related Operations
Run the ADD ACLRULE command to add a maximum of 512 ACL rules.

CR-SRAN90-01306210A
7.2.2.8 SSL Transmission of Updated CRLs
Description
Updated CRLs now can be transmitted in SSL mode to enhance equipment security.

Copyright © Huawei
Implementation
From SRAN8.0 onwards, a base station supports FTP over SSL transmission of updated
CRLs.
From SRAN9.0 onwards, a base station supports LDAP over SSL transmission of updated
CRLs. The CONNMODE and AUTHMETHOD parameters are added to specify the
transmission mode and authentication mode, respectively. The parameters need to be set when
you create a CRL update task.

None.
Impact on NEs
None.
Impact on Hardware
None.

None.

N/A.
From SRAN8.0 onwards, a base station supports FTP over SSL transmission of updated
CRLs.
From SRAN9.0 onwards, a base station supports LDAP over SSL transmission of
updated CRLs. The CONNMODE and AUTHMETHOD parameters are added to
specify the transmission mode and authentication mode, respectively. The parameters
need to be set when you create a CRL update task.
None.
None.

None.
Related Operations
Run the MML command ADD CRLTSK with the CONNMODE and AUTHMETHOD
parameters set to appropriate values.

Copyright © Huawei

CR-SRAN90-201307040C
7.2.2.9 Optimized Mechanism of Reporting the Imminent Certificate Expiry

Alarm
Description
Without the optimization, ALM-26840 Imminent Certificate Expiry is reported only when the
automatic certificate updating mode is used.
With the optimization, ALM-26840 Imminent Certificate Expiry can also be reported when
the manual certificate updating mode is used. Moreover, the expiry time of the certificate is
now indicated in the alarm information.
Implementation
ALM-26840 Imminent Certificate Expiry is reported when the manual certificate updating
mode is used and the base station detects that the offset between the current time and the
expiry time exceeds the value of the alarm threshold ALMRNG.
The Expire time field in the alarm information indicates the time when the certificate will
expire.

None.
Impact on NEs
None.
Impact on Hardware
None.

None.

N/A.
To enable reporting of this alarm when the manual certificate updating mode is used, set
UPDATEMETHOD to MANUAL in the SET CERTCHKTSK command.
None.

Copyright © Huawei
The Expire time field in the alarm information indicates the time when the certificate
will expire.

None.
Related Operations
To enable reporting of this alarm when the manual certificate updating mode is used, set
UPDATEMETHOD to MANUAL in the SET CERTCHKTSK command.

CR-SRAN90-01308140A
7.2.2.10 Support for the Dormancy Status for PSUs
Description
After PSU intelligent shutdown is enabled, some PSUs will be shut down for energy saving.
With this feature, the status of these PSUs will be displayed as Dormancy when PSU
information is queried.
Implementation
The Running Status of the PSUs that are shut down is Dormancy in the DSP PSU command
output.

None
Impact on NEs
None
Impact on Hardware
None

None

N/A
None

Copyright © Huawei
None
None

None
Related Operations
None

CR-MBTS19-036
7.2.2.11 Removed the Restriction of Removing the Main Control Board of

the Peer Mode Before Deploying the UMTS Mode When the RNC
Operates as the BOOTP Server
Description
If each mode of a separate-MPT base station works in independent transmission mode, the
main control board of the peer mode does not need to be removed before deploying the
UMTS mode in the following condition: the UMTS adopts ATM-based transmission and the
UTRP provides a port connecting to the transport network.
Implementation
The NODEBCTRLSN parameter is added to the ADD/MOD UNODEBIP command to
specify the slot number of the main control board from which the BOOTP request is sent.

None
Impact on NEs
None
Impact on Hardware
None

None


Copyright © Huawei
N/A
The NODEBCTRLSN parameter is added to specify the slot number of the main control
board of the NodeB.
None
None

None
Related Operations
Run the ADD/MOD UNODEBIP command with the NODEBCTRLSN parameter set to the
slot number of the main control board of the NodeB.

CR-SRAN90-201309130B
7.2.2.12 Added an "Auto clear" Flag for ADMC Alarms
Description
An "Auto clear" flag is added to the following alarms to indicate whether the alarm needs to
be manually cleared after the fault is rectified:
 ALM-26242 Configuration File Damaged
 ALM-26255 Automatic Version Rollback
Implementation
If an alarm carries the "Auto clear" flag and the flag is set to No, the alarm is an
Automatically Detected and Manually Cleared (ADMC) alarm and needs to be manually
cleared after the fault is rectified. If an alarm does not carry the "Auto clear" flag, the alarm is
an Automatically Detected and Automatically Cleared (ADAC) alarm and will be
automatically cleared after the fault is rectified.

None
Impact on NEs
None
Impact on Hardware
None

Copyright © Huawei

The "Auto clear" flag is carried in alarm packets.

N/A
None
None
ADMC alarms need to be manually cleared after the faults are rectified.

None
Related Operations
None

CR-MBTS19-036
7.2.2.13 WRFD-140223 MOCN Cell Resource Demarcation
Description
 R99 Code Allocation Function
The percentage of downlink code resources assigned to R99 users (DL R99 code
resources for short) available to UEs of each MOCN-enabled operator is configurable at
the cell level.
When the total DL R99 code resource usage in a cell reaches a specified threshold, the
RNC allows a new UE to preempt resources occupied by a UE whose operator exceeds
the predefined resource percentage during admission control, based on the code resource
usage of each operator. As usual, the RNC preferentially selects the UE with the lowest
priority for preemption.
If the cell is congested, the RNC analyzes the cause of the congestion. If the congestion
is caused by insufficient DL R99 code resources, the RNC preferentially selects UEs
whose operator exceeds the predefined percentage of DL R99 code resources for load
reshuffling (LDR).
 HSDPA Power Allocation Function
The percentage of HSDPA power available to UEs of each MOCN-enabled operator is
configurable at the cell level. The RNC informs the NodeB of the percentage. The
NodeB calculates the HSDPA power usage of UEs of each operator and adjusts the
scheduling priority of UEs of this operator. The difference between the predefined
percentage and the HSDPA power usage of UEs of an operator increases with the
scheduling priority of the UEs of this operator.

Copyright © Huawei
When HSDPA power usage in a cell reaches a specified threshold, the RNC allows a new
UE to preempt resources occupied by a UE whose operator exceeds predefined HSDPA
power percentage during admission control, based on the guaranteed bit power (GBP)
usage of each operator.
Implementation
For details, see the change history of MOCN Feature Parameter Description in RAN Feature
Documentation.

 Capacity
None
 Performance
If the power resources consumed by an operator exceed the predefined percentage, the
number of resource preemptions increases when the cell load is high. This leads to an increase
in the call drop rate. In a cell with light load, however, this feature has no impact on network
performance because preemption is not triggered.
Impact on NEs
This feature is implemented on the RNC and the NodeB.
Impact on Hardware
The NodeB must be configured with a UBBP.

The RNC indicates indexes of MOCN operators, their predefined values for
DPAAvaiPwrRatio(UMTS BSC6900,UMTS BSC6910), and the index of the primary
operator in proprietary IEs "ucMocnoperatorIndex",
"ucMocnoperatordemarcationHpowerratio", and "ucPrimOperIndex", respectively. These IEs
are carried in the Physical Shared Channel Reconfiguration Request message.
When the function of allocating power resources to each operator, which is introduced in
V100R009, is enabled, the DLPwrRatio(UMTS BSC6900,UMTS BSC6910) parameter and
another proprietary IE "enMultiOpPwrDemarcType" are also carried in the Physical Shared
Channel Reconfiguration Request message besides the preceding proprietary IEs. The
proprietary IE "enMultiOpPwrDemarcType" indicates whether the percentage of power in the
Physical Shared Channel Reconfiguration Request message to the NodeB is the percentage of
HSDPA power or percentage of total downlink power.
The RNC indicates indexes of MOCN operators, their predefined values for
DPAAvaiPwrRatio, and the index of the primary operator in proprietary IEs
"ucMocnoperatorIndex", "ucMocnoperatordemarcationHpowerratio", and
"ucPrimOperIndex", respectively. These IEs are carried in the Physical Shared Channel
Reconfiguration Request message.
When the function of allocating power resources to each operator, which is introduced in
V100R009, is enabled, the DLPwrRatio parameter and another proprietary IE
"enMultiOpPwrDemarcType" are also carried in the Physical Shared Channel

Copyright © Huawei
Reconfiguration Request message besides the preceding proprietary IEs. The proprietary IE
"enMultiOpPwrDemarcType" indicates whether the percentage of power in the Physical
Shared Channel Reconfiguration Request message to the NodeB is the percentage of HSDPA
power or percentage of total downlink power.

The enhancement of MOCN Cell Resource Demarcation in V100R009 has no impact on the
license.
The following MML commands have been introduced on the RNC side to accommodate this
feature.

ge
Type
New ADD/MOD/RMV/LST BSC690 These commands are used to add,

UCELLMOCNPWRDEMAR 0 modify, remove, and query
BSC691 parameters related to the cell-
0 level MOCN power demarcation
ratios.
Modifi DSP UCELLCHK BSC690 The cell power demarcation
ed 0 status is added to the output
BSC691 information of this command.
0
The following parameters have been introduced on the RNC side to accommodate this
feature.

Type ID Command
New LogicRncId( ADD/MOD/R BSC691 ID of a logical RNC.

UMTS MV/LST 0
BSC6900,U UCELLMOC
MTS NPWRDEMA
BSC6910) R
New CellId(UMT ADD/MOD/R BSC690 Cell ID, which is defined by the
S MV/LST 0 operator to uniquely identify a
BSC6900,U UCELLMOC BSC691 cell in an RNC.
MTS NPWRDEMA 0
BSC6910) R
New CnOpIndex( ADD/MOD/R BSC690 Operator index.
UMTS MV 0
BSC6900,U UCELLMOC BSC691
MTS NPWRDEMA 0
BSC6910) R

Copyright © Huawei

Type ID Command
New DLPwrRatio ADD/MOD BSC690 Percentage of R99+HSDPA

(UMTS UCELLMOC 0 power allocated to an operator in
BSC6900,U NTOTALPW BSC691 an MOCN cell. This percentage is
MTS RDEMAR 0 delivered to the NodeB to ensure
BSC6910) that the R99+HSDPA power used
by each operator is close to this
percentage. In addition, the RNC
determines whether to perform
preemption on this operator based
on this percentage.
New LSTFORMA LST BSC690 Result list format
T UCELLMOC 0
NPWRDEMA BSC691
R 0
New DlPWRLdc ADD/MOD BSC690 Switch for selecting users to
UeSelSwitch UCELLALG 0 perform LDR actions when the
(UMTS OSWITCH BSC691 total power resources in a cell
BSC6900,U 0 enter the basic congestion state if
MTS the license for the MOCN Cell
BSC6910) Resource Demarcation feature is
activated and the DLPwrRatio
parameter is configured.
New CellMocnDe ADD/MOD BSC690 Resource demarcation switch for
marcSwitch( UCELLALG 0 operators in an MOCN cell.
UMTS OSWITCH BSC691
BSC6900,U 0
MTS
BSC6910)
New CellMocnDe ADD/MOD BSC690 Code (SF) resource demarcation
marcSwitch( UCELLALG 0 switch for operators in an MOCN
UMTS OSWITCH BSC691 cell.When this switch is set to on,
BSC6900,U 0 downlink SF resources in an
MTS MOCN cell are allocated based
BSC6910): on operators. In this way,
CELL_MO downlink SF resources actually
CN_DL_SF_ used by operators in this cell can
DEMARC_ approximate to the value
SWITCH specified by the DLAvaiSFRatio
parameter. When this switch is set
to off, downlink SF resources in
an MOCN cell are allocated
regardless of operators.
New CellMocnDe ADD/MOD BSC690 HSDPA power resource
marcSwitch( UCELLALG 0 demarcation switch for operators
UMTS OSWITCH BSC691 in an MOCN cell.When this
BSC6900,U 0 switch is set to on, HSDPA power
MTS in an MOCN cell is allocated
BSC6910): based on operators. In this way,

Copyright © Huawei

Type ID Command
CELL_MO the HSDPA power actually used

CN_DL_HS by operators in this cell can
DPAPWR_ approximate to the value
DEMARC_ specified by the
SWITCH DPAAvaiPwrRatio parameter.
When this switch is set to off,
HSDPA power in an MOCN cell
is allocated regardless of
operators.
New CellMocnDe ADD/MOD BSC690 Total downlink power resource
marcSwitch( UCELLALG 0 demarcation switch for operators
UMTS OSWITCH BSC691 in an MOCN cell.When this
BSC6900,U 0 switch is set to on, the total
MTS downlink power in an MOCN cell
BSC6910): is allocated based on operators. In
CELL_MO this way, the total downlink
CN_DL_TO power actually used by operators
TALPWR_ in this cell can approximate to the
DEMARC_ value specified by the
SWITCH DLPwrRatio parameter. When
this switch is set to off, the total
downlink power in an MOCN cell
is allocated regardless of
operators.

The following counters have been introduced on the NodeB side to accommodate this feature.

Type Name nt Unit
New VS.DLDCHP POWER.LO NodeB Average ratio of downlink DCH

wrRatio.Shar CELL transmit power occupied by
edOperator0 operator 0 in an MOCN network

Copyright © Huawei
None

This feature requires the WRFD-021311 MOCN Introduction Package feature.
In the same cell, the function of allocating HSDPA power resources to each operator cannot
take effect together with the function of allocating total downlink power resources to each
operator.
The function of allocating total downlink power resources to each operator cannot be
deployed in a cell that supports only R99 services but does not support HSDPA services.
Impacted Features
This feature cannot be used together with the function of inter-PLMN handover or the
function of setting up inter-PLMN multi-carriers. The reason is that the inter-PLMN
handover or inter-PLMN multi-carriers will result in the problem that the resources of a
dedicated cell of an operator are occupied by UEs of other operators, which affects cell
resource allocation and revenue division among operators.
It is recommended that the function of allocating total downlink power resources to each
operator be enabled together with the WRFD-020106 Load Reshuffling feature and the LDR
based on power resources function.
Related Operations
For details, see section "WRFD-140223 MOCN Cell Resource Demarcation" in chapter
"Engineering Guidelines" in MOCN Feature Parameter Description of RAN Feature
Documentation.

IR-V100R009-133
7.2.2.14 WRFD-050402 IP Transmission Introduction on Inb Interface
Description
Abis over IP allows operators to deploy an IP network between the BSC and the BTS.
In addition, this feature provides FE and GE ports and complies with the IPv4 protocol. The
BSC connects to the BTS through a LAN or WAN, depending on the location of the BSC and
the BTS.
Abis over IP ensures high reliability by implementing active/standby mode and load sharing
mode.
The GBSS adopts the following mechanisms to ensure end-to-end high QoS.
 Physical bandwidth shaping

Copyright © Huawei
Burst flow is controlled by the buffer and token bucket. If messages are transmitted at a
very high speed, the messages are buffered and transmitted at a uniform speed under the
control of the token bucket.
 Priority mapping
Messages are identified for different services, classified, and prioritized. They are then
associated with the corresponding flow control and resource allocation. According to the
load on the current network, a specific flow control action is taken.
 Congestion management
Congestion occurs when the rate at which data arrives at the port is higher than the rate
at which data is sent from the port. In this case, the voice quality deteriorates and the
data transmission rate decreases. The traffic statistics on the interface board show that
the number of discarded packets increases. As a result, congestion results in the increase
of the packet transmission delay and delay variation. An excessively long delay causes
packets to be retransmitted. If congestion increases, a large number of network resources
are wasted and improper resource allocation may lead to system deadlock or breakdown.
The challenge of network resource shortage can be taken up by increasing network
bandwidth. In addition, preventive mechanisms, such as tail drop and weighted random
early detection (WRED), are applied to avoid network congestion. When congestion
occurs, the priority queue (PQ) or weighted round robin (WRR) of queue scheduling is
used to handle congestion.
Implementation
See Equipment Security Feature Parameter Description.

 Capacity
No impact.
 Performance
No impact.
Impact on NEs
The GBTS does not support this feature.
Impact on Hardware
No impact.

No impact.

None
The following MML commands have been introduced to accommodate this feature.

Copyright © Huawei

Type
New MOD PACKERFILTER MBTS To modify a packet filter

New DSP ACLRULE MBTS To query the information about
the effective ACL rules

Type ID
New ACLAUTOS ADD PACKERFILTER MBTS Indicates whether to

WITCH MOD PACKERFILTER enable the advanced
ACL auto-setup
function for packet
filtering.

No impact.
No impact.

None
None
Impacted Features
None
Related Operations
None

IR-V100R009-099
7.2.2.15 MRFD-221901 Multi-RAT Carrier Joint Inrelligent Shutdown
Description
UMTS Cell Joint Shutdown in GU Scenarios

Copyright © Huawei
When GSM and UMTS base stations are co-sited and cover the same area, the two base
stations can use different RF units or different RF channels of the same RF units. During low-
traffic hours, related hardware modules for UMTS can be shut down to reduce power
consumption. The RNC determines whether a UMTS cell should be shut down based on
factors such as the load of the UMTS cell, the load of its co-coverage GSM cells, and user
priorities. If a UMTS cell meets shutdown conditions, the RNC hands over multimode UEs on
the UMTS network or reselects these UEs to the GSM network and then shuts down the
UMTS cell. After UMTS cells are shut down, GSM cells provide services for all UEs in the
area. When the GSM network load increases or the GSM network cannot meet the quality of
service (QoS) requirements of multimode UEs, the UMTS cell is restarted.
This feature is recommended for either of the following scenarios:

 The penetration rate of UMTS data services is high and the traffic volume is extremely
unbalanced at different times in a day. Examples include office buildings and shopping
malls.
 The penetration rate of UMTS data services is low. Examples include suburbs and rural
areas.
With the rapid development of mobile broadband networks, many users stay connected for 24
hours a day, downloading video, audio, and other types of files. The data service processing of
UMTS networks is superior to that in GSM networks. When a UMTS network is shut down,
the delay in downloading data will be prolonged due to a decreased download rate.
Differentiated services are therefore provided. When there is a high-priority user in a UMTS
cell, the UMTS cell is not shut down. If a high-priority user initiates services after the UMTS
cell is shut down, the UMTS cell is restarted in a timely manner to ensure quality service for
the high-priority user.
Carrier Joint Intelligent Shutdown in UL Scenarios
This feature is recommended for either of the following scenarios:
 Areas where the penetration rate of LTE data services is low and traffic volumes are
extremely unbalanced at different times in a day in the early phase of LTE network
deployment. Examples include shopping malls, office buildings, and stadiums.
 Rural areas where the LTE network provides only basic coverage, the penetration rate of
LTE terminals and data services is low, and the LTE network is lightly loaded most of the
day

Copyright © Huawei
When UMTS and LTE base stations cover the same area, the two base stations can use
different RF units or different RF channels of the same RF units. During low-traffic hours,
related hardware modules for LTE can be shut down to reduce power consumption. Before the
LTE cell shutdown, LTES services will be switched to its co-coverage UMTS cells, which
continue to provide services for all UEs in the area.
The eNodeB determines whether an LTE cell can be shut down based on the following
conditions: LTE cell load, co-sited UMTS cell load requested from the RNC through the RIM
procedure, cell shutdown period, shutdown of non-basic cells, online user number, and
whether emergent services are going on. When the preceding conditions are met, the eNodeB
switches multimode UEs in connected mode from the current cell to its co-coverage UMTS
cells and then shuts the LTE cell and the related hardware. When the cell shutdown period
ends or the RNC informs the eNodeB that the load of the co-coverage UMTS cells has
increased, the eNodeB restarts the LTE cell.
Carrier Joint Intelligent Shutdown in GUL Scenarios
In an area covered by co-sited GSM, UMTS, and LTE base stations, LTE cells are shut down
based on the description in Carrier Joint Intelligent Shutdown in UL Scenarios and UMTS
cells are shut down based on the description in Cell Joint Shutdown in GU Scenarios. When
UMTS and LTE cells are shut down, the LTE cell is dynamically shut down based on the
description in Carrier Joint Intelligent Shutdown in GL Scenarios. During low-traffic hours,
only GSM provides basic coverage and services for all UEs in the area. When the cell
shutdown period ends or the load of the co-coverage GSM cells has increased, the UMTS and
LTE cells are restarted.
Implementation
See Multi-RAT Carrier Joint Shutdown Feature Parameter Description.

 Capacity
No impact.
 Performance
 Peak rate of a single UE
In areas covered by GU, UL, GL, or GUL networks, few UEs in the LTE or UMTS cell
will be handed over to neighboring inter-frequency co-coverage cells after the LTE or
UMTS cell is shut down. As data service processing capability of neighboring inter-
frequency co-coverage cells is inferior to that of the LTE or UMTS cell that has been
shut down, the peak rate of a single UE is reduced, thereby affecting user experience in
data services. For example, data service processing capability of UMTS cells is inferior
to that of LTE cells, and data service processing capability of GSM cells is inferior to
that of UMTS cells.
 Service availability to single-mode UEs
In areas covered by GU, UL, GL, or GUL networks, LTE-only or UMTS-only UEs in
idle mode cannot initiate services after the LTE or UMTS cell is shut down.
 Number of inter-RAT handovers and cell reselections
This feature triggers the following handover or cell reselection interoperability
procedures between networks of different modes:
− After the LTE or UMTS cell is shut down, multimode UEs reselect or are handed
over to a UMTS or GSM cell. As a result, inter-RAT handovers and cell reselections
increase.

Copyright © Huawei
− After the LTE or UMTS cell is restarted, the multimode UEs reselect or are handed
over to the LTE or UMTS cell. As a result, inter-RAT handovers and cell reselections
increase.
 Call drop rate on the FACH
Before shutting down the UMTS cell in areas covered by GU networks, the RNC
releases the connections of UEs in the CELL_FACH state so that the UEs reselect a
GSM cell if DynShutDownCchUserSwitch(UMTS BSC6900,UMTS BSC6910) is set to
OFF. As a result, the call drop rate on the FACH increases.
 Access delay of UEs in idle mode and these UEs' dropping from the network
After the LTE or UMTS cell is shut down, multimode UEs in idle mode reselect a UMTS
or GSM cell. After the LTE or UMTS cell is restarted, the multimode UEs in idle mode
reselect the LTE or UMTS cell. During the cell reselection, the following possibilities
may occur:
− UEs in idle mode that have radio signal fluctuations or poor performance may drop
from the network for a short period of time after cell reselection.
− The routing areas of cells with different modes may be different, and the cell
reselection triggers location area (LA) updates. UEs in idle mode occupy access
channel resources during LA updates, thereby temporarily affecting access of other
UEs.
Impact on NEs
This feature is implemented on the GBSC, RNC, NodeB, eNodeB, and U2000.
Impact on Hardware
This feature requires GSM and UMTS network to exchange information. For non-MBSC
scenarios, a physical connection is required for the Iur-g interface between the BSC and RNC.

This feature requires setting up the Iur-g interface between the BSC and RNC in GU/GUL co-
coverage scenarios. Control information is transmitted using Huawei-defined messages. Iur-g
is Huawei-defined interface between the BSC and RNC.
This feature requires LTE and GSM/UMTS networks to exchange load information through
the RAN Information Management (RIM) procedure in GL/UL/GUL co-coverage scenarios.
The eNodeB, GBSC, or RNC must support transmitting load information through the RIM
procedure. The MME and SGSN must support message transmission through the RIM
procedure.

The following license control items have been added to accommodate this feature.
Control Item
MRFD-211901 Multi-RAT Multi-RAT BSC Per BTS

Carrier Joint Carrier Joint
Intelligent Intelligent
Shutdown Shutdown (BTS)

Copyright © Huawei

Control Item
(GBTS)
MRFD-221901 Multi-RAT Multi-RAT NodeB Per NodeB
Shutdown Shutdown
(NodeB) (NodeB)
MRFD-231901 Multi-RAT Multi-RAT eNodeB Per eNodeB
Shutdown Shutdown
(eNodeB) (eNodeB)

Type ID
New ShutDownTy MOD eNodeB This parameter

pe INTERRATCELLSHU indicates the type of
TDOWN the inter-RAT co-
coverage cell
shutdown.
New UtranCellDl MOD eNodeB This parameter
LoadThd INTERRATCELLSHU indicates the
TDOWN downlink load
threshold of a co-
coverage
neighboring
UTRAN cell for the
E-UTRAN cell to
enter inter-RAT co-
coverage cell
shutdown mode.
New UtranCellUl MOD eNodeB This parameter
LoadThd INTERRATCELLSHU indicates the uplink
TDOWN load threshold of a
co-coverage
neighboring
UTRAN cell for the
E-UTRAN cell to
enter inter-RAT co-
coverage cell
shutdown mode.
New UtranCellDl MOD eNodeB This parameter
LoadOffset INTERRATCELLSHU indicates the
TDOWN downlink load offset

Copyright © Huawei

Type ID
of a co-coverage
neighboring
UTRAN cell for
enabling the carrier
of the E-UTRAN
cell that has been
shut down.
New UtranCellUl MOD eNodeB This parameter
LoadOffset INTERRATCELLSHU indicates the uplink
TDOWN load offset of a co-
coverage
neighboring
UTRAN cell for
of the E-UTRAN
cell that has been
shut down.
New GeranCellLo MOD eNodeB This parameter
adThd INTERRATCELLSHU indicates the load
TDOWN threshold of a co-
coverage
neighboring
GERAN cell for the
E-UTRAN cell to
enter inter-RAT co-
coverage cell
shutdown mode.
New GeranCellLo MOD eNodeB This parameter
adOffset INTERRATCELLSHU indicates the load
TDOWN offset of a co-
coverage
neighboring
GERAN cell for
of the E-UTRAN
cell that has been
shut down.
New HighPriArpT MOD eNodeB This parameter
hd INTERRATCELLSHU indicates the
TDOWN allocation/retention
priority (ARP)
threshold for high-
priority services.
New OverlapInd ADD UTRANNCELL eNodeB This parameter
MOD UTRANNCELL indicates whether
the neighboring
UTRAN cell is
manually identified

Copyright © Huawei

Type ID
as a neighboring
cell overlapping the
E-UTRAN cell.
New OverlapInd ADD GERANNCELL eNodeB This parameter
MOD GERANNCELL indicates whether
the neighboring
GERAN cell
overlaps the E-
UTRAN cell.
Modified PROCESSS SET BSC6900 The
WITCH5 URRCTRLSWITCH INTERRAT_LOA
D_SINGLE_RPT_
FOR_LTE_SWIT
CH(RIM-based
and Request-based
Load Information
Sharing Switch) is
added to the
PROCESSSWITC
H5 parameter.

Type Unit
Modified L.ChMeas.DFEE. Duration of eNodeB This counter

CarrierOFF.Dur Energy Saving and provides the
Emission duration of
Reduction intelligent power-
off of carriers in
the same coverage,
intelligent power-
off of carriers in
the same coverage
of UMTS network,
or inter-RAT cell
shutdown in a cell.
Modified L.Cell.Unavail.Dur Duration of Cell eNodeB This counter
.EnergySaving Unavailability provides the
duration of cell
unavailability due
to energy saving.

Copyright © Huawei
None

When multiple inter-frequency co-coverage UMTS cells cover the same area as GSM cells,
the inter-frequency co-coverage UMTS cells of the current UMTS cell must have either of the
following features enabled:
 WRFD-020117 Multi-Carrier Switch off Based on Traffic Load
 WRFD-020122 Multi-Carrier Switch off Based on QoS
For details, see the RAN document Green BTS Feature Parameter Description. When the
traffic volume on the UMTS network decreases, the inter-frequency co-coverage UMTS cells
for the current UMTS cell are shut down.
When the traffic volume on the UMTS network further decreases and the current UMTS cell
is the only working UMTS cell, the current UMTS cell is shut down.
en-us_topic_0004206418.xml#EN-US_TOPIC_0004206418/en-us_topic_0004206418_en-
us_topic_0004185068_en-us_topic_0004185004_en-us_topic_0003680626_fig3327021
shows the feature application in UMTS multi-carrier scenarios.
Figure 1.1 Feature application in UMTS multi-carrier scenarios
 When single-carrier UMTS networks cover the same area as GSM networks, the Multi-
RAT Carrier Joint Shutdown feature does not require any of the following features:
− WRFD-020117 Multi-Carrier Switch off Based on Traffic Load
− WRFD-020122 Multi-Carrier Switch off Based on QoS
 When multicarrier LTE networks cover the same area as UMTS or GSM networks, the
Multi-RAT Carrier Joint Shutdown feature requires the LOFD-001042 Intelligent Power-
Off of Carriers in the Same Coverage feature. For details about the LOFD-001042

Copyright © Huawei
Intelligent Power-Off of Carriers in the Same Coverage feature, see the eRAN document
Energy Conservation and Emission Reduction Feature Parameter Description.
In multicarrier inter-frequency LTE networks, the LOFD-001042 Intelligent Power-Off
of Carriers in the Same Coverage feature must be enabled in capability cells and the
Multi-RAT Carrier Joint Shutdown feature must be enabled in basic cells. When the
traffic volume on the LTE network decreases, the inter-frequency co-coverage LTE cells
for the current LTE cell are shut down. That is, one or multiple capability LTE cells are
shut down. When the traffic volume on the LTE network further decreases and basic LTE
cells are the only working LTE cells, the basic LTE cells are shut down by using the UL
or GL cell joint intelligent shutdown function.
 When single-carrier LTE cells cover the same area as UMTS or GSM cells, the Multi-
RAT Carrier Joint Shutdown feature does not require the LOFD-001042 Intelligent
Power-Off of Carriers in the Same Coverage feature.
 In areas covered by GUL networks, features related to the Multi-RAT Carrier Joint
Shutdown feature are determined based on single-carrier UMTS or LTE cells, or
multicarrier UMTS or LTE cells.
Areas covered by GU networks
The Multi-RAT Carrier Joint Shutdown feature cannot be used together with the feature
MRFD-211802 GSM and UMTS Dynamic Spectrum Sharing. The application scenarios and
purposes of these two features are different. The GSM and UMTS Dynamic Spectrum Sharing
feature enables dynamic spectrum sharing (DSS) between a GSM network and a UMTS
network based on traffic load, improving data throughput. If both the two features are
enabled, the UMTS cell that uses a GSM frequency through DSS may be shut down, and the
traffic volume on the GSM network increases because the GSM cells carry all of the traffic in
the overlapping coverage area. The increase in the GSM traffic volume triggers spectrum
resource reclamation, and as a result the GSM and UMTS Dynamic Spectrum Sharing feature
becomes ineffective.
Impacted Features
It is recommended that operators enable the Multi-RAT Carrier Joint Shutdown feature
together with the following feature and function in areas covered by GU networks to achieve
superior performance:
 WRFD-031000 Intelligently Out of Service
The Intelligently Out of Service feature helps gradually reduce the cell pilot power to
enable UEs in the idle state to reselect GSM cells when the UMTS cell is shut down.
This avoids a great number of location area (LA) update requests caused by the
simultaneous cell reselections of UEs in the idle state, minimizing the possibility of
congestion on access channels.
For details, see the RAN document Intelligently Out of Service Feature Parameter
Description.
 Preferential Allocation of Channels on the BCCH TRX
The Preferential Allocation of Channels on the BCCH TRX function enables some
online users to perform services on the BCCH TRX to reduce power consumption.
For details, see the GBSS document Intelligent Power Consumption Decrease Feature
The Multi-RAT Carrier Joint Shutdown feature may impact the following feature in areas
covered by GU networks:

Copyright © Huawei
Related Operations
See the "Engineering Guidelines" section in Multi-RAT Carrier Joint Shutdown Feature

IR-V100R009-099
7.2.2.16 WRFD-01061203 HSUPA Power Control
Description
 V100R009
In V100R009, optimize the inner loop power control for high-speed upload services
(above 700 kbit/s) to reduce the signal-to-interference ratio (SIR) by 1dB-3dB, and
correct the inner loop power control when RTWP is above a specific threshold to
improve high speed user experience and system stability.
Correct the inner loop power control for QoS-insensitive low-speed services when
RTWP goes up abnormally to improve cell throughput and system stability.
Implementation
For details, see the change history of Power Control Feature Parameter Description in RAN

 Capacity
This function has the following impacts on system capacity:
 When HSUPA UEs are performing high-rate data transmission (such as higher than 2
Mbit/s) in the scenario with multipath effect (such as on the PB3 and VA30 channels),
this function optimizes the SIR estimations to increase the throughput by 2% to 25%
when the UE moves at a speed lower than 50 km/h and by 0 to 10% when the UE moves
at a speed higher than or equal to 50 km/h. When these UEs move from the cell center to
the cell edge, and if the uplink retransmissions decrease to the target number, the
throughput of these UEs increases by 2% to 10%.
 When HSUPA UEs are performing low-rate data transmission (such as lower than 200
kbit/s), interference among UEs leads to abnormal RTWP increases. This function
corrects the SIR estimations to decrease interference among low-rate UEs, decreases
RTWP peaks, and increases the cell throughput by 0~10%. The gains of this function are
more noticeable when a cell has more HSUPA UEs. For example, in a cell with a total of
40 UEs and over 40% of them are HSUPA UEs, the RTWP abnormally increases to a
value (such as greater than the RTWP corresponding to the target load). After this
function is enabled, the RTWP can be effectively decreased and the cell throughput can
be increased by over 2% to 10%.
 Performance
This function has the following impacts on network performance:
A UMTS network is a self-interference system, so the interference among multiple UEs leads
to alternative RTWP increase. When a small number of HSUPA UEs are performing high-rate
data transmission (such as higher than 2 Mbit/s) in the scenario with multipath effect,

Copyright © Huawei
instantaneous RTWP peaks frequently occur, and SIRtarget easily reaches the maximum SIRtarget
(MaxSirtarget(UMTS BSC6900,UMTS BSC6910)). As a result, the outer loop power control
does not take effect. This function decreases RTWP peaks and increases system stability.
Impact on NEs
This function is implemented by the NodeB.
Impact on Hardware
In 3900 series base stations, uplink services must be carried on the WBBPd, WBBPf, or
UBBP board, and downlink services must be carried on the WBBPb, WBBPd, WBBPf, or
UBBP board.

None

HSUPA Power Control Enhancement in V100R009 has no impact on the license.
Table 10-1 lists parameter changes in this function.
Table 1.1 Table 10-1Parameter changes

Type ID Command
Added ULINNERP SET NodeB Indicates the switch for

CABNRISE NODEBALGP correcting the SIR when the
CTRLSW ARA RTWP is abnormal.

None
None

 Prerequisite Features
None
 Mutually Exclusive Features
None
 Impacted Features
None

Copyright © Huawei
Related Operations
For details, see section "HSUPA Power Control Enhancement" in chapter "Engineering
Guidelines" in Power Control Feature Parameter Description of RAN Feature
Documentation.

IR-V100R009-004
7.2.2.17 Single BBU Supporting 24 RHUBs in the LampSite Solution
Description
Before the optimization, a BBU supports a maximum of 12 RHUBs and the number of
supported pRRUs cannot reach the upper limit (96) in the following scenarios:
 The number of pRRUs connected to each RHUB cannot reach eight due to actual site
limitations.
 A BBU supports a maximum of 48 pRRUs configured with two RF daughter boards,
because each RHUB can connect to four such pRRUs at most, each over two Ethernet
cables.
The BBU is now optimized to support up to 24 RHUBs. The optimization reduces the number
of required BBUs and deployment costs in the preceding scenarios.
Implementation
A BBU supports up to 24 RHUBs.

None
Impact on NEs
The maximum number of RHUBs that a BBU supports increases from 12 to 24.
Impact on Hardware
None

N/A

None
None

Copyright © Huawei
None
None

None
Related Operations
None

IR-C93-LampSite-04
Feature ID
None
7.2.3 Deleted Features and Functions

None
7.3 Resolved Issues

Resolved issues from V100R009C00SPC180 to V100R010C00SPC150, refer to section 6.1.4
Resolved Issues.
Resolved issues from V100R008C00SPC300 to V100R009C00SPC180, refer to section of
below:
7.3.1 Critical
7.3.1.1 The base station may reset after an IP clock is configured.
Trouble DTS:DTS2014031006527
Ticket
Number
Description After an IP clock complying with IEEE 1588V2 or Huawei proprietary

protocols is configured, the base station may reset, which interrupts the
ongoing services for a few minutes.
Severity Critical
Root Cause Other tasks are being performed during the ongoing hardware
disconnection, which interrupts the ongoing hardware disconnection and
violates system design requirements.
Solution The software bug has been rectified.

Copyright © Huawei
Solution None
Impact
7.3.2 Major
7.3.2.1 The RRU3804 (AC) and RRU3806 (AC) do not report ALM-26540 RF
Unit AC Input Power Failure when they should be
Number
Description Condition: An AC power outage occurs on the RRU3804 (AC) and

RRU3806 (AC) of the following BOM numbers:
 02310EAP
 02316949
 02316950
 02318748
 02318780
 02316863
 02316866
Symptom: The preceding RRUs do not report ALM-26540 RF Unit AC
Input Power Failure on the LMT.
Impact: O&M engineers cannot be alerted to an AC power outage.
Severity Major
Root Cause The RRUs use incorrect level setting for alarm detection and therefore
the RRUs do not report this alarm when an AC power outage occurs.
Solution The defective mechanism has been corrected so that ALM-26540 RF
Unit AC Input Power Failure is reported when an AC power outage
occurs on the RRU3804 and RRU3806.
Solution None
Impact
7.3.2.2 When the common transport channels fail to be established, there is

an extremely low probability that a cell becomes a sleeping cell.
Ticket
Number

Copyright © Huawei
Description Condition: After the NodeB restarts, the first logical cell is established
successfully and the common transport channels fail to be established for
the subsequent logical cells.
Symptom: The first logical cell carries no traffic on the RACH.
Impact: Ongoing services of the NodeB are interrupted and the first
logical cell becomes a sleeping cell.
Severity Major
Root Cause The timing for releasing transport resources is incorrect. As a result, the
NodeB unintentionally deletes the transport channels.
Solution The timing for releasing transport resources has been corrected to ensure
that the transport channels work properly.
Solution None
Impact
7.3.2.3 Inconsistent license sales and control strategies are present for the
UBBP board in RAN16.0.
Ticket
Number
Description Condition: The NodeB configured with the UBBP board is upgraded
from RAN15.0 to RAN16.0.
Symptom: After the upgrade, the UBBP board not licensed by "UBBP
Multi-Mode license for UMTS (per UBBP)" cannot function well.
Impact: The UBBP board fails to provide services.
Severity Major
Root Cause In RAN15.0, the "UBBP Multi-Mode license for UMTS (per UBBP)"
license control item is not required for use of the UBBP board. In
RAN16.0, the UBBP board must be licensed.
NOTE
The absence of license control on use of the UBBP boards eliminates the need to
upgrade the U2000 for license delivery.
Solution Use of the UBBP board is under license control in RAN16.0. After a
NodeB is upgraded to RAN16.0, the NodeB allows a 60-day grace period
and reports ALM-26811 Configured Capacity Limit Exceeding Licensed
Limit.
Solution If the UBBP board is configured and the license capacity is insufficient,
Impact required licenses must be supplemented. Operators can use the upgrade
risk check package on the U2000 to verify that the licensed capacity is
sufficient.

Copyright © Huawei
7.3.2.4 There is a low probability that the WBBPd board becomes

unavailable.
Ticket
Number
Description Condition: A BTS3900 V100R009C00SPC160 is configured with the

WBBPd board.
Symptom: When the WBBPd board provides baseband resources for the
local cells or the WBBPd board functions as the interface board, ALM-
28203 Local Cell Unusable is reported. When the baseband resource
group contains multiple baseband processing units, the local cells are
established on non-WBBPd boards, on which ALM-26202 Board
Overload is occasionally reported.
Impact: The WBBPd is unavailable.
Severity Major
Root Cause The downlink DSP on the WBBPd board uses a defective startup process.
Solution The defective startup process has been corrected.
Solution None
Impact
7.3.2.5 The value returned by VS.DlPwrRatio.SF256 is larger than expected.

Number
Description Condition: The WBBPb, WBBPd, or WBBPf board provides

downlink baseband resources for a cell, which serves F-DPCH users.
Symptom: The value returned by VS.DlPwrRatio.SF256 is larger
than expected.
NOTE
VS.DlPwrRatio.SF256: measures the average ratio of DPCH and F-DPCH
transmit power over SF256 downlink code channel to the maximum downlink
transmit power in a cell.
Impact: The counter value is inaccurate.
Severity Major
Root Cause The downlink DSP uses a defective mechanism to measure the
average F-DPCH power.

Copyright © Huawei
7.3.2.6 There is a low probability that a cell fails to be established.

Number
Description Condition: The uplink baseband equipment works in 4-channel

demodulation mode and serves cells. The WBBPd or WBBPb board
in the uplink baseband equipment is blocked and then unblocked.
Symptom: There is a low probability that a cell establishment fails.
Impact: Ongoing services carried on the WBBPd or WBBPb board
are interrupted.
Severity Major
Root Cause In 4-channel demodulation mode, the mechanism for checking

parameters during cell establishments is defective.
7.3.2.7 Cells served by the WBBPb or WBBPd board experience zero RRC
connection setup attempts if flow control is triggered.
Ticket
Number
Description Condition: The uplink baseband equipment includes the WBBPb or

WBBPd board and flow control is triggered.
Symptom: There is a low possibility that cells served by the WBBPb or
WBBPd board experience zero RRC connection setup attempts (indicated
by the VS.RRC.AttConnEstab.Sum counter).
Impact: The RRC connection fails to be set up.
Severity Major
Root Cause The WBBPb and WBBPd boards use a defective resource maintenance
mechanism in flow control. As a result, the chip- and cell-related
parameters are improperly set.
Solution The defective resource maintenance mechanism in flow control has been
corrected.
Solution None
Impact

Copyright © Huawei
7.3.2.8 All cells established on the WBBPd board occasionally experience a

low RRC connection setup success rate.
Ticket
Number
Description Condition: Baseband equipment for local cells includes the WBBPd
board.
Symptom: The WBBP board reports ALM-26203 Board Software
Program Error, and all cells established on the WBBPd board
occasionally experience a significant decrease in the RRC connection
setup success rate.
Impact: For all cells established on the WBBPd board, the following
KPIs are affected:
 The RRC connection setup success rate (indicated by the
RRC.ConnEstab.Succ.Rate counter) greatly decreases.
 The CS RAB setup success rate (indicated by the
VS.RAB.SuccEstabCS.Cell.Rate counter) decreases.
 The PS RAB setup success rate (indicated by the
VS.RAB.SuccEstabPS.Cell.Rate counter) decreases.
 The CS drop rate (indicated by the VS.CS.Call.Drop.Cell.Rate counter)
increases.
 The PS drop rate (indicated by the VS.PS.Call.Drop.Cell.Rate counter)
increases.
Severity Major
Root Cause Dedicated links are established on the WBBPd board. When the
dedicated links are reconfigured, the WBBPd board incorrectly maintains
the resources for dedicated link reconfiguration. Specifically, key
demodulation static parameters are modified unintendedly. As a result,
KPIs deteriorate.
Solution The exception in resource maintenance for dedicated link reconfiguration
has been rectified.
Solution None
Impact
7.3.2.9 In specific scenarios, the RAB assignment success rate decreases.

Ticket

Copyright © Huawei
Number
Description Condition: In a procedure of reconfiguring the radio link from over non-
DC-HSDPA to over DC-HSDPA, the RNC sends the NodeB a
reconfiguration cancellation (RADIO LINK RECONFIGURATION
CANCEL) message over the Iub interface.
Symptom: The radio link fails to be reconfigured.
Impact: The RAB assignment success rate (indicated by the
VS.RAB.SuccEstabPS.Cell.Rate counter and
VS.RAB.SuccEstabCS.Cell.Rate counters) decreases.
Severity Major
Root Cause In the preceding instance, the RNC sends the NodeB a reconfiguration
cancellation (RADIO LINK RECONFIGURATION CANCEL) message
in the reconfiguration procedure but the NodeB uses a defective
mechanism to process the message.
Solution None
Impact
7.3.2.10 FTP communication between a NodeB and the M2000 fails and
therefore NodeB software fails to be automatically supplemented.
Number
Description Condition: An intermediate device, such as a firewall or security

gateway (SeGW), is deployed between a NodeB and the M2000.
Passive (PASV) FTP mode or the FTP data ports (numbered from
16100 through 17099) are disabled on the intermediate device.
Symptom: After the NodeB is upgraded, automatic software
supplement fails, ALM-26253 Board Software Auto-Supply Failure is
reported, and the error code 0x40000004 "Processing on the FTP
client failed" is reported, indicating that FTP-related operations fail.
Impact: All the FTP functions are unavailable, including
configuration synchronization, traffic statistics reporting, certificate
upload (ULD CERTFILE), certificate download (DLD
CERTFILE), log acquisition (ULD FILE), configuration file upload
(ULD CFGFILE), certificate download (DLD CFGFILE).
Severity Major
Root Cause If the NodeB working in passive (PASV) FTP mode fails to establish
an FTP connection with the M2000 due to configurations of the
intermediate device, the NodeB does not switch to active (PORT)
FTP mode to reconnect to the M2000.
Solution The NodeB now switches to active (PORT) FTP mode to reconnect to

Copyright © Huawei
the M2000 in the preceding scenario.

7.3.2.11 In specific scenarios, RTWP-related counters all return a value 0.

Ticket
Number
Description Condition: The NodeB is configured with a WMPT board (active) and a
UMPT board (standby) or a WMPT board and a UTRPc board, and the
UMPT or UTRPc board serves as the signaling processing board.
Symptom: The following RTWP-related counters all return a value 0.
 VS.MeanRTWP.Locell.SectorEqm.Ant0
 VS.MinRTWP.Locell.SectorEqm.Ant0
Impact: The counter values are inaccurate.
Severity Major
Root Cause The RTWP-related counter reporting mechanism is defective.
Solution None
Impact
7.3.2.12 ALM-28206 Local Cell Capability Decline is not reported when it

should be.
Ticket
Number
Description Condition: The HSDPA multi-carrier cell group contains more than two
cells and at least one of the cells in the group is experiencing DC-HSDPA
capability derating.
NOTE

Copyright © Huawei
 To view the number of cells in an HSDPA multi-carrier cell group, run the LST
NODEBMULTICELLGRP or LST NODEBMULTICELLGRPITEM
command.
 To check for capability derating of a cell, run the DSP ULOCELL command.
Symptom: ALM-28206 Local Cell Capability Decline is not reported for
the cells that are configured with 3C-HSDPA, 4C-HSDPA, or Flexible
Dual Carrier HSDPA but fail to use them due to capability derating.
Impact: The alarm is not reported when it should be, affecting
troubleshooting.
Severity Major
Root Cause The NodeB incorrectly determines the capability of cells configured with
3C-HSDPA, 4C-HSDPA, or Flexible Dual Carrier HSDPA.
Consequently, alarm reporting malfunctions.
Solution The NodeB now correctly determines the capability of cells configured
with 3C-HSDPA, 4C-HSDPA, or Flexible Dual Carrier HSDPA, ensuring
normal alarm reporting.
Solution In the preceding scenario, ALM-28206 Local Cell Capability Decline is
Impact reported for the cells that are configured with 3C-HSDPA, 4C-HSDPA,
or Flexible Dual Carrier HSDPA but fail to use them due to capability
derating. The alarm cause is "4C-HSDPA/3C-HSDPA/Flexible Dual
Carrier HSDPA not supported by the cell."
7.3.2.13 If an exception occurs, there is a low probability that UEs served by

the WBBPd or WBBPb board experience service drops.
Number
Description Condition: The WBBPd or WBBPb board provides uplink baseband

resources. The NodeB receives an RADIO LINK DELETION
REQUEST message that contains unrecognized fields.
Symptom: The WBBPd or WBBPb board does not respond to any
subsequent messages.
Impact: There is a low probability that UEs served by the WBBPd or
WBBPb board experience service drops.
Severity Major
Root Cause The mechanism for processing the RADIO LINK DELETION
REQUEST message is not robust. As a result, the WBBPd or WBBPb
board fails to properly process the message that contains unrecognized
fields and subsequent messages.
Solution The RADIO LINK DELETION REQUEST message processing
mechanism used by the WBBPd and WBBPb board has been improved to
ensure robustness.

Copyright © Huawei
Solution None
Impact
7.3.2.14 RRUs are repetitively loaded due to configuration errors in a dual-

mode base station.
Description Condition: In a dual-mode base station implemented through BBU
interconnection, multimode RRUs are connected to the two main
control boards using the dual-star topology. The interconnection
cable is not installed for the two BBUs and one mode of the base
station is upgraded.
Symptom: RRUs are repetitively loaded and reset.
Impact: RRUs cannot work properly.
Severity Major
Root Cause The interconnection cable is not installed as required for the two
BBUs. After one mode is upgraded, the RRU versions of the two
modes become inconsistent. However, The loading control right is
not negotiated and RRUs are repetitively loaded.
Solution A risk check item is added to the upgrade risk check package to
instruct users to perform the upgrade after correcting the
configuration errors.
7.3.2.15 The capability of distributed cells declines.

Number
Description Condition: UMTS distributed cells have been configured. The ADD
ULOCELLSECTOREQM, RMV ULOCELLSECTOREQM, or
MOD ULOCELLSECTOREQM command is executed to add, delete,
or modify the sector equipment for local cells and the MOD
SECTOREQM command is executed to modify the sector equipment.
After the modification, the sector equipment serving distributed cells has
a single RX channel (using one RX antenna) and RRUs are distributed on
multiple RRU chains.
Symptom: The cell capability declines or the distributed cells become
unavailable.

Copyright © Huawei
Impact: The cell capability declines or the distributed cells become

unavailable.
Severity Major
Root Cause In the preceding scenario, CPRI resources are not completely released.
Solution CPRI resources have been released properly.
Solution None
Impact
7.3.2.16 The CPU usage is imbalanced between baseband processing units

when the UTRPc board is used to expand the signaling capacity.
Ticket
Number
Description Condition: The NodeB is configured with the WMPT and UTRPc
boards. On the WebLMT or the U2000, the SET NODEBALGPARA
command is executed to set CNBAP Capacity Extension Using UTRPc
to ON. Then, the NodeB is reset or the BLK BRD command is executed
to block a baseband processing unit and the UBL BRD command is
executed to unblock it.
Symptom: The CPU usage is imbalanced between baseband processing
units.
Impact: When a baseband processing unit is overloaded, the success rate
of user access decreases.
Severity Major
Root Cause In the preceding scenario, some baseband processing units obtain CPU
resources abnormally, and therefore the CPU usage balancing algorithm
fails to take effect when baseband resources are allocated for users.
Solution The CPU resources have been properly allocated for baseband processing
units.
Solution None
Impact
7.3.2.17 In certain scenarios, there is a high probability that the NodeB does
not report ALM-26200 Board Hardware Fault.
Ticket

Copyright © Huawei
Number
On the WebLMT, the SET NODEBALGPARA command is executed to
set KPI Fault Detection Switch to ON and KPI Fault auto Recover
Para to Intra-Baseband Board Resource Restart.
The NodeB reports EVT-28231 UMTS Traffic Abnormal Recovery with
"Recovery Cause" set to KPI and "Recovery Type" set to Intra-
Baseband Board Resource Restart.
On the NodeB, the block error rate (BLER) of R99 users, the BLER of
HSUPA users, and the proportion of abnormal users on a processing unit
are higher than R99 User Fault Detect Threshold, UPA User Fault
Detect Threshold, and Process Unit Fault Detect Threshold,
respectively.
Symptom: The NodeB does not report ALM-26200 Board Hardware
Fault.
Impact: Operators are not alerted to the fault.
Severity Major
Root Cause In the preceding scenario, the NodeB uses a defective mechanism to
obtain the board status, hindering alarm reporting.
Solution None
Impact
7.3.2.18 The output power of distributed cells is abnormal.

Ticket
Number
Description Condition: One or more multi-mode RF units serve both UMTS

distributed cells and non-UMTS cells.
Symptom: The output power of distributed cells is lower than expected.
Impact: The service rates decrease and users at the cell edge may
Severity Major
Root Cause In the preceding scenario, the NodeB incorrectly calculates the output
power of UMTS distributed cells.
Solution The NodeB now correctly calculates the output power of UMTS
distributed cells.
Solution None
Impact

Copyright © Huawei
7.3.2.19 RRU status modification for a sector and sector equipment on the
CME does not take effect.
Ticket
Number
Description Condition: On the Configuration Management Express (CME), users

replace RRUs for a sector and sector equipment.
Symptom: When usable RRUs are replaced with unusable RRUs, cells
served by the sector equipment are still available. When unusable RRUs
are replaced with usable RRUs, cells served by the sector equipment are
still unavailable.
Impact: The local cell status is abnormal.
Severity Major
Root Cause In the preceding scenario, the software of the cell resource management
module is defective. To be specific, the cell resource management
module does not check the RRU status of the corresponding sector and
sector equipment, so the RRU status change does not causes cell status
change in a timely manner.
Solution The defective software of the cell resource management module has been
corrected.
Solution None
Impact
7.3.2.20 The UTRPc board of RAN14.0 sometimes fails to be upgraded to

RAN16.0.
Ticket
Number
Description Condition: The UTRPc board of RAN14.0 is used in RAN16.0.

Symptom: There is a high probability that the UTRPc board resets
unexpectedly every two minutes after an upgrade to RAN16.0 starts.
Impact: The UTRPc board of RAN14.0 fails to be upgraded to RAN16.0.
Severity Major
Root Cause The UTRPc board uses a defective verification mechanism.
Solution The defective verification mechanism has been corrected.

Copyright © Huawei
Solution None
Impact
7.3.2.21 The RRU3804 or WRFU sometimes fails to be upgraded to

RAN16.0.
Number
Description Condition: The RRU3804 or WRFU is being upgraded to RAN16.0.

Symptom: There is a low probability that the RRU3804 or WRFU fails
to be upgraded to RAN16.0 and ALM-26254 Board Software
Synchronization Failure is reported.
Impact: The RRU3804 or WRFU can only be rolled back to the source
version.
Severity Major
Root Cause A new file whose name does not meet the naming rules is introduced for
the RRU3804 and WRFU in RAN16.0. As a result, the operating system
occasionally encounters errors and fails to create the file for the
RRU3804 and WRFU during an upgrade.
Solution The file names have been corrected to comply with the naming rules.
Solution None
Impact
7.3.2.22 There is a vulnerability from Heartbleed Security threats when the

FTP server downloaded from the LMT uses OpenSSL 1.0.1g.
Number
The Nessus scans the maintenance port of the base station.
Symptom:
The scanning report contains the CVE-2014-0224 vulnerability.
Impact:
An attacker can exploit this vulnerability to obtain user
information.
Severity Major

Copyright © Huawei
Root Cause The OpenSSL is used to set up an SSL connection to the

maintenance port of the base station. However, there is a software
bug in the OpenSSL. As a result, the CVE-2014-0224 vulnerability
is reported when the Nessus scans the maintenance port of the base
station.
Solution This vulnerability has been rectified in a later version of the
OpenSSL and will no longer be reported in base stations with the
software version V100R009C00SPC120 or later.
7.3.2.23 A barred cell is reestablished if the NodeB falsely determines that

the barred cell experiences exceptions in the RRC connection setup process.
Ticket
Number
Description Condition: A NodeB is configured with the WBBPb, WBBPd, WBBPf,

or UBBPd board and a cell under the NodeB is barred on the RNC side
so that UEs are prohibited from accessing the cell.
Symptom: The values returned by the VS.RAB.AbnormRel.CS.OM and
VS.RAB.AbnormRel.PS.OM counters increase.
Impact: The barred cell is reestablished, increasing call drops.
Severity Major
Root Cause Cell reestablishment is triggered for the barred cell if the NodeB falsely
determines that UEs access the barred cell.
Solution Software defects have been rectified so that cell reestablishment is not
triggered for the barred cell.
Solution None
Impact
7.3.2.24 When the UL CoMP and Multi-BBU Interconnection features are

activated, coordinating links cannot be added.
Ticket
Number
Description Condition: Cells with the Multi-BBU Interconnection feature activated

adopt the host cell/coordinating cell configuration and UEs are adding

Copyright © Huawei
uplink coordinating links.
The cell coordination relationship can be configured by using the ADD

NODEBULCOMPGRP command.
Symptom: The uplink coordinating links fail to be added.
Impact: The values of all the following counters related to UL CoMP
decrease:
 VS.UUlCoMPGroup.UserNum
 VS.UUlCoMPGroup.MaxUserNum
 VS.ULCoMP.ULCE.Mean.Shared
 VS.ULCoMP.ULCE.Max.Shared
 VS.ULCoMP.ULCE.Mean.Dedicated
 VS.ULCoMP.ULCE.Max.Dedicated
 VS.ULCoMP.LC.ULMean.LicenseGroup
 VS.ULCoMP.LC.ULMax.LicenseGroup
 VS.ULCoMP.LC.ULMean.LicenseGroup.Shared
 VS.ULCoMP.LC.ULMax.LicenseGroup.Shared
 VS.ULCoMP.HSUPA.LC.ULMean.LicenseGroup
 VS.ULCoMP.HSUPA.LC.ULMax.LicenseGroup
 VS.ULCoMP.HSUPA.LC.ULMean.LicenseGroup.Shared
 VS.ULCoMP.HSUPA.LC.ULMax.LicenseGroup.Shared
 VS.ULCoMP.CE.ULMean.Board
 VS.ULCoMP.CE.ULMax.Board
 VS.ULCoMP.CE.ULMean.UlGroup
 VS.ULCoMP.CE.ULMax.UlGroup
Severity Major
Root Cause The mechanism for processing uplink coordinating link addition is
defective.
Solution None
Impact
7.3.2.25 After the Queuing and Pre-Emption feature is activated, the RRC
connections fail to be set up.
Ticket
Number

Copyright © Huawei
Description Condition: CE-based user preemption on the NodeB side (controlled by

the PREEMPT_ENH_NODEB_PREEMPT_CE_SWITCH parameter)
is activated on the RNC. When NodeB resources are insufficient,
resource preemption is triggered during the RRC connection setup
procedure.
NOTE
CE-based user preemption on the NodeB side is activated by running the following
command:
SET UQUEUEPREEMPT: PreemptEnhSwitch =
PREEMPT_ENH_NODEB_PREEMPT_CE_SWITCH-1
Symptom: Resource preemption succeeds but RRC connections still fail
to be set up.
Impact: UEs fail to access the NodeB.
Severity Major
Root Cause In the preceding scenario, the NodeB uses a defective mechanism to save
the internal message related to RRC connection setup.
Solution None
Impact
7.3.2.26 After HSDPA UEs are handed over to another cell, their data rates
sometimes drop to 0 kbit/s.
Number
Description Condition: The NodeB working in ATM/IP transmission mode serves

HSDPA UEs. The HSDPA UEs are handed over between cells whose
downlink services are established on different baseband processing units.
Symptom: Data rates of the HSDPA UEs occasionally drop to 0 kbit/s
after handovers.
Impact: Data rates of the HSDPA UEs occasionally drop to 0 kbit/s.
Severity Major
Root Cause In the preceding scenario, the NodeB incorrectly manages the port for
downlink flow control. As a result, applications for transmission
bandwidths fail.
Solution The NodeB now correctly manages the port for downlink flow control.
Solution None
Impact

Copyright © Huawei
7.3.2.27 In ATM transmission mode, a NodeB configured with the UMPT

board resets unexpectedly.
Number
Description Condition: A NodeB works in ATM transmission mode, its services are
carried by AAL2 paths, and cells served by the NodeB are working
properly.
Symptom: Service disconnections of UEs seldom trigger ALM-26203
Board Software Program Error for the UMPT board.
Impact: The NodeB resets unexpectedly 10 minutes after the alarm is
reported.
Severity Major
Root Cause NodeB reliability protection is inadequate. As a result, if a NodeB in

ATM transmission mode receives a massive number of AAL2 errors and
out-of-order information elements (IEs), exceptions occur when the core
of the UMPT board processes data, causing a loss of handshake
messages between the UMPT board and other boards.
Solution NodeB reliability protection has been enhanced to protect against AAL2
errors and out-of-order IEs.
Solution None
Impact
7.3.2.28 Faults in the flash memory of a baseband processing unit cannot be

detected or reported before a NodeB upgrade.
Number
Description Condition: The software of the NodeB needs to be upgraded.

Symptom: The flash memory of a baseband processing unit rarely
becomes faulty but the fault is not detected or reported before the
upgrade.
Impact: The NodeB software fails to be upgraded.
Severity Major
Root Cause Detection or reporting of faults in the flash memory is not available
before software upgrades.
Solution The STR HWOLTST and DSP HWOLTSTRESULT commands have
been added to detect faults in the flash memory and query detection

Copyright © Huawei
results, respectively. It is good practice to run the commands before a

software upgrade.
Solution None
Impact
7.3.2.29 The WBBPf or UBBPd board occasionally resets after the Boosting
feature has been enabled.
Ticket
Number
Description Condition: The Boosting feature has been enabled, and the uplink
resource group contains the WBBPf or UBBPd board.
Symptom: The WBBPf or UBBPd board occasionally resets.
Impact: Ongoing services carried on the WBBPf or UBBPd board are
occasionally interrupted.
Severity Major
Root Cause The WBBPf or UBBPd board uses a defective mechanism for Boosting
resource management.
Solution The defective mechanism for Boosting resource management has been
corrected.
Solution None
Impact
7.3.2.30 The RAB setup success rate decreases during inter-RAT handovers.
Ticket
Number
Description Condition: An inter-RAT handover is performed.
RAT stands for radio access technology.

Symptom: The number of RL setup failures over Iub increases and the
radio access bearer (RAB) setup success rate decreases. Activating the
Fast Radio Bearer Setup feature makes this fault frequently occur.
Impact: The RAB setup success rate decreases.
Severity Major

Copyright © Huawei
Root Cause The NodeB uses a defective mechanism for processing the compressed
mode-related parameters during inter-RAT handovers. As a result, the
downlink DSP of the NodeB detects exceptions and returns an
NBAP_RL_FAIL_IND message, leading to abnormal RL releases.
Solution None
Impact
7.3.2.31 Cells excluding multi-RRU cells fail to use power control licenses
released by running the MOD ULOCELLSECTOREQM command.
Ticket
Number
Description Condition: The NodeB serves multi-RRU cells and other types of cells.
ALM-28203 Local Cell Unusable and ALM-26811 Configured Capacity
Limit Exceeding Licensed Limit are reported for other types of cells
because power control licenses are insufficient.
Symptom: Other cells fail to use power control licenses released by
running the MOD ULOCELLSECTOREQM command.
Impact: The two alarms persist.
Severity Major
Root Cause The NodeB uses a defective algorithm for allocating power control
licenses when multi-RRU cells and other types of cells coexist.
Solution None
Impact
7.3.2.32 When the MOCN feature is enabled, uplink CE-related counters

return inaccurate values.
Ticket
Number
Description Condition: The multi-operator core network (MOCN) feature is enabled

and the values of the operator index consist of discontinuously
increasing numbers.
Symptom: When the Dynamic CE feature is enabled (CE stands for

Copyright © Huawei
channel element), the following counters return inaccurate values on the

NodeB:
 VS.LC.ULMean.LicenseGroup
 VS.LC.ULMax.LicenseGroup
 VS.LC.ULMin.LicenseGroup
 VS.HSUPA.LC.ULMean.LicenseGroup
 VS.HSUPA.LC.ULMax.LicenseGroup
 VS.HSUPA.LC.ULMin.LicenseGroup
 VS.ULCoMP.LC.ULMean.LicenseGroup
 VS.ULCoMP.LC.ULMax.LicenseGroup
 VS.ULCoMP.HSUPA.LC.ULMean.LicenseGroup
 VS.ULCoMP.HSUPA.LC.ULMax.LicenseGroup
 VS.ULCE.Mean.Dedicated
 VS.ULCE.Max.Dedicated
 VS.ULCE.Mean.Shared
 VS.ULCE.Max.Shared
When the CE Overbooking feature is enabled, the following counters
return inaccurate values on the RNC:
 VS.NodeB.ULCreditUsed.Mean
 VS.NodeB.ULCreditUsed.Max
 VS.NodeB.ULCreditUsed.Min
 VS.NodeB.ULCreditUsed.Mean.PLMN
 VS.NodeB.ULCreditUsed.Max.PLMN
Impact:
 The service rate of HSUPA UEs does not increase as expected.
 When the CE Overbooking feature is enabled, CE admission functions
inaccurately on the RNC side.
Severity Major
Root Cause In the preceding scenario, the NodeB uses a defective mechanism for
managing uplink CEs.
Solution None
Impact
7.3.2.33 In ATM transmission mode, call drops sometimes occur due to

asynchronous reconfiguration in specific scenarios.
Ticket

Copyright © Huawei
Number
Description Condition: The Fast Radio Bearer Setup feature is activated for the
NodeB in ATM transmission mode. UEs are located in the handover area
and downlink services of the cells involved in handovers are not
deployed on the same baseband processing unit.
Symptom: UEs sometimes experience call drops unexpectedly.
Impact: UEs sometimes experience call drops unexpectedly.
Severity Major
Root Cause In the preceding scenario, the NodeB uses defective software for
information exchanges of transmission ports used by downlink channels,
leading to a transmission failure between the downlink channels and
RNC.
Solution The software defects have been rectified.
Solution None
Impact
7.3.2.34 Iub signaling messages seldom fail to be processed when IRC is

enabled on a UBBPd board.
Ticket
Number
Description Condition: Interference rejection combining (IRC) is enabled on a

UBBPd board.
Symptom: Iub signaling messages occasionally fail to be processed in a
certain period.
Impact: UEs served by the UBBPd board may experience unexpected
call drops.
Severity Major
Root Cause The UBBPd board uses defective software for updating IRC finger
parameters.
Solution None
Impact

Copyright © Huawei
7.3.2.35 There is a low probability that the main control board reports the
ALM-26202 Board Overload alarm.
Ticket
Number
Description There is a low probability that the main control board reports the ALM-
26202 Board Overload alarm during normal base station operation,
which may affect ongoing services or trigger abnormal base station
resets.
Severity Major
Root Cause The size of the linked lists is large and data processing consumes a lot of
time, which increases the CPU usage of the main control board.
Solution Codes are added to protect the main control board from being
overloaded.
Solution None
Impact
7.3.2.36 HSDPA users experience low data rates.

Ticket
Number
Description If the two or more HSDPA cells established on a UBBP board have
different T Cell configurations, the data rate of an HSDPA user is only
hundreds of kbit/s in one HSDPA cell.
Severity Major
Root Cause During an HSDPA physical shared channel reconfiguration, the resource
numbers allocated to HS-SCCHs of different cells may duplicate with
each other, which causes incorrect Uu data for HS-SCCHs.
Solution The software bug has been rectified so that resource numbers allocated
to HS-SCCHs of different cells during HSDPA physical shared channel
reconfiguration do not duplicate with each other.
Solution None
Impact

Copyright © Huawei
7.3.2.37 The local cell experiences intermittent ALM-28203 Local Cell

Unusable.
Ticket
Number
Description Condition: A NodeB is configured with the UMPT board and supports
UMTS services.
Symptom: The local cell experiences intermittent ALM-28203 Local
Cell Unusable.
Impact: The number of intermittent ALM-28203 Local Cell Unusable
increases.
Severity Major
Root Cause The UMPT board uses a defective smoothing mechanism for ALM-
28203 Local Cell Unusable.
Solution The defective alarm smoothing mechanism on the UMPT board has been
corrected.
Solution None
Impact
7.3.2.38 The local cell experiences intermittent ALM-28206 Local Cell

Capability Decline after a NodeB is upgraded to V100R009C00SPC010 or
V100R009C00SPC020.
Ticket
Number
Description Condition: A NodeB is upgraded to V100R009C00SPC010 or

V100R009C00SPC020, IC is enabled for the local cell, and IC resources
are insufficient.
Symptom: The local cell experiences intermittent ALM-28206 Local
Cell Capability Decline every 4.5 minutes.
Impact: The number of intermittent ALM-28206 Local Cell Capability
Decline increases.
Severity Major
Root Cause The time sequence for clearing ALM-28206 Local Cell Capability
Decline is incorrect, and therefore the alarm is cleared when it should
not be.
Solution The time sequence for clearing ALM-28206 Local Cell Capability
Decline has been corrected.

Copyright © Huawei
Solution None
Impact
7.3.2.39 The NodeB reports EVT-28200 Iub Common Procedure Failure

Indication.
Ticket
Number
Description Condition: The logical cell is activated, and the MOD

UAICHPWROFFSET command is executed to modify the AICH
power offset in a cell or the MOD UPRACH command is executed to
modify the basic PRACH configurations in a cell.
Symptom: The NodeB reports EVT-28200 Iub Common Procedure
Failure Indication.
Impact: Parameter modifications by running the MOD
UAICHPWROFFSET and MOD UPRACH commands fail to take
effect on the NodeB side.
Severity Major
Root Cause The NodeB uses a defective mechanism of AICH reconfigurations.
Solution The defective mechanism of AICH reconfigurations has been corrected.
Solution None
Impact
7.3.2.40 There is a low possibility that UEs fail to access multi-RRU cells if
Independent Demodulation of Signals from Multiple RRUs in One Cell is
enabled.
Number
Description If the uplink resource group serves both ordinary cells and multi-RRU
cells, there is a possibility that UEs fail to access multi-RRU cells when
RRUs suddenly fail and then recover automatically.
Severity Major
Root Cause Cells enabled with Independent Demodulation of Signals from Multiple
RRUs in One Cell use a defective mechanism for allocating time slices
for network access.

Copyright © Huawei
Solution None
Impact
7.3.2.41 The number of extended cells that can be set up on the WBBPf
board exceeds the publicized WBBPf specifications.
Ticket
Number
Description The number of extended cells that can be set up on the WBBPf board
exceeds the publicized specifications in Extended Cell Range Feature
Severity Major
Root Cause The number of extended cells that can be set up on the WBBPf board
was not controlled according to the publicized specifications.
Solution The number of extended cells that can be set up on the WBBPf board
now conforms to the publicized specifications.
Solution None
Impact
7.3.2.42 Cells enabled with Uplink Enhanced CELL_FACH fail to be

deleted in specific scenarios.
Ticket
Number
Description There is a possibility that cells enabled with Uplink Enhanced

CELL_FACH fail to be deleted. Consequently, such cells fail to be set
up again, or UEs fail to access a cell even though this cell has been set
up.
Severity Major
Root Cause The mechanism for deleting the physical random access channel
(PRACH) before deleting channels for Uplink Enhanced CELL_FACH
is defective.
Solution None

Copyright © Huawei
Impact
7.3.2.43 The Control Channel Parallel Interference Cancellation (phase 2)

feature does not depend on the CCPIC feature.
Ticket
Number
Description The output of the DSP LICENSE command on the WebLMT or U2000
shows that the license control item CCPIC function (per NodeB) is set to
0 or does not exist, and the license control item Control Channel Parallel
Interference Cancellation (Phase 2)(Per NodeB) is not set to 0. In this
situation, the output of the DSP ULOCELL command shows that the
Control Channel Parallel Interference Cancellation (phase 2)function is
disabled, but UEs can receive gains from this feature.
Severity Major
Root Cause The Control Channel Parallel Interference Cancellation (phase 2) feature
does not depend on the CCPIC feature.
Solution The Control Channel Parallel Interference Cancellation (phase 2) feature
now depends on the CCPIC feature.
Solution In the preceding scenario, after the NodeB is upgraded to V100R009,
Impact ALM-26811 Configured Capacity Limit Exceeding Licensed Limit is
reported with "Mismatched Control Item=CCPIC function (per NodeB)"
displayed in the alarm location information, and UEs no longer receive
gains from Control Channel Parallel Interference Cancellation (phase 2).
In addition, the values of the following two performances counters are 0:
VS.FirstStageIcEff.Mean
VS.FirstStageIcEff.Max
7.3.2.44 Downlink 64QAM occasionally becomes unavailable after the

NodeB is upgraded to V100R009 in specific scenarios.
Ticket
Number
Description When R99 cells and HSDPA cells use different carriers in hierarchical
cell networking, there is a possibility that downlink 64QAM licenses are
allocated only to R99 cells after the NodeB is upgraded to V100R009.
Severity Major

Copyright © Huawei
Root Cause The mechanism for allocating downlink 64QAM licenses is defective.
Consequently, downlink 64QAM licenses fail to be allocated to HSDPA
cells that are capable of downlink 64QAM.
Solution None
Impact
7.3.2.45 Loads on the UMPTa/UTRPc board and the baseband board are
unbalanced.
Ticket
Number
Description There is a possibility that CPU loads on the UMPTa/UTRPc board and
the baseband board are unbalanced when the UMPTa/UTRPc board is
configured on a heavily-loaded NodeB.
Severity Major
Root Cause The UMPTa/UTRPc board uses a defective deployment and allocation
algorithm for the Dedicated NodeB Application Part (DNBAP).
Solution If the UMPTa or UTRPc board is configured on a lightly-loaded NodeB,

Impact the CPU load on the baseband processing unit increases by about 3%
and that on the UMPTa or UTRPc board decreases slightly. However,
the Common NodeB Application Protocol (CNBAP) processing
capability of the NodeB does not decline.If the overall baseband load is
low on the NodeB, loads are imbalanced between baseband processing
units of different types, but the CNBAP processing capability of the
NodeB does not decline.If the UMPTb board serves as the main control
board and the service load is low, the CPU utilization on the UMPTb
board increases slightly and that on the baseband processing units
decreases. However, the CNBAP processing capability of the NodeB
does not decline.
7.3.2.46 The mode of a remote cell cannot be changed by using the MOD
ULOCELL command.
Trouble OR: OR-201303135719
Ticket
Number

Copyright © Huawei
Description When a user attempts to change the mode of a remote cell by using the
MML command MOD ULOCELL, there is no corresponding field on
the command interface.
Severity Major
Root Cause The Remote Cell Mode parameter (or RMTCM) is unavailable for the
MML command MOD ULOCELL.
Solution Parameters are added to the MOD ULOCELL command, so that users
can modify attributes of existing local cells and cells with activated
logical cells.
Solution Attributes modification will cause the local cell to be res-established. If
Impact this occurs, all UEs served by this cell will experience call drops.
7.3.2.47 After the CQI Adjustment Based on Dynamic BLER Target feature
is activated, downloading small-sized files by using HSDPA cannot reach
the expected rate in a short period of time.
Ticket
Number
Description After the CQI Adjustment Based on Dynamic BLER Target feature is
activated, FTP downloads for small-sized files over HSDPA cannot
reach the expected rate as quickly as expected.
Severity Major
Root Cause The CQI Adjustment Based on Dynamic BLER Target feature uses a
defective algorithm during the download of small-sized files.
Solution None
Impact
7.3.2.48 Counters related to adaptive retransmission return incorrect values

after the NodeB is upgraded or reset.
Ticket
Number
Description The MML command SET NODEBADPRETRANSSW is run with

ADPRETRANSSW set to OPEN for a NodeB. After the NodeB is

Copyright © Huawei
upgraded or reset, the following counters return value 0:

 VS.HSUPA.RsnSmall2Large.TTI2ms
 VS.HSUPA.RsnSmall2Large.TTI10ms
 VS.HSUPA.RsnLarge2Small.TTI2ms
 VS.HSUPA.RsnLarge2Small.TTI10ms
Meanwhile, the following counters return incorrect values:
 VS.HSUPA.NACKTotal
 VS.HSUPA.RetransPDUNum
Severity Major
Root Cause The configuration restoration module is defective, causing counters

related to adaptive retransmission to return value 0.
Solution The defective configuration restoration module has been corrected.
Solution None
Impact
7.3.2.49 If a NodeB is configured with 24 cells, running the DSP ULOCELL

command disconnects the Web LMT from the U2000.
Ticket
Number
Description The Web LMT is disconnected from the NodeB and displays the "server
internal error" message if all the following conditions apply:
 The NodeB is configured with 24 local cells.
 The logical cells are all activated.
 The DSP ULOCELL command is executed to query the status of all
local cells.
Severity Major
Root Cause When a NodeB is configured with 24 cells, the packet carrying the
output of the DSP ULOCELL command has a size greater than that
permitted by the Web LMT and U2000.
Solution If a NodeB is configured with 24 cells, the output of the DSP
ULOCELL command is segmented into multiple packets, each carrying
information about 12 cells at most.
Solution None
Impact

Copyright © Huawei
7.3.2.50 Uplink CE counters return incorrect values 0.

Ticket
Number
Description On SingleRAN networks, the following CE counters return incorrect

values 0 when no UTRAN cells are set up:
 VS.CE.ULAvailable.UlGroup
 VS.CE.ULMean.UlGroup
 VS.CE.ULMin.UlGroup
 VS.CE.ULMax.UlGroup
 VS.ULCoMP.CE.ULMean.UlGroup
 VS.ULCoMP.CE.ULMax.UlGroup
Severity Major
Root Cause The multi-mode baseband processing unit UBBPd is introduced in

V100R009C00. When the SingleRAN solution is used and the local cell
is not set up on the UBBPd board, the RNC cannot determine whether
the baseband resources are used by UTRAN cells.
Solution  The UBBPd board now can be configured into multiple sets of uplink
or downlink baseband equipment. If the board can be configured into
only one resource group, ALM-28350 Board Configuration
Inconsistent with Resource Group Configuration is reported.
 Traffic statistics about uplink CEs are reported only when the
baseband resources are used by UTRAN cells.
 The values of counters VS.HW.ULCreditAvailable and
VS.HW.DLCreditAvailable may decrease.
Solution Deleting the last local cell from the baseband equipment causes call
Impact drops to all UEs using CPU resources of baseband processing units
belonging to the baseband equipment. In addition, new admitted UEs
cannot use such CPU resources.
7.3.2.51 After the E-FACH feature is activated, the VS.EFACH.Thruput

counter returns an incorrect value.
Ticket
Number
Description After the E-FACH feature is activated, the VS.EFACH.Thruput counter

returns a value lower than the actual throughput.
Severity Major
Root Cause The mechanism for calculating the VS.EFACH.Thruput counter is

Copyright © Huawei
defective. Specifically, after the Cell E-FACH feature is activated, the

VS.EFACH.Thruput counter does not measure data on the broadcast
control channel (BCCH).
Solution The defective mechanism has been corrected, so that data on the BCCH
is also measured.
Solution None
Impact
7.3.2.52 The VS.HSUPA.TurboIC.Number counter returns an incorrect

value for the WBBPf board.
Ticket
Number
Description When the WBBPf board is used and the Turbo IC feature is activated,
the VS.HSUPA.TurboIC.Number counter returns an incorrect value.
Severity Major
Root Cause The WBBPf board uses a defective mechanism for measuring the
VS.HSUPA.TurboIC.Number counter.
Solution None
Impact
7.3.2.53 E-RACH user access fails in cells in economical 4-channel

demodulation mode.
Ticket
Number
Description When cells are set to work in economical 4-channel demodulation mode
and the Uplink Enhanced CELL_FACH feature is functional, UEs fail to
access the network.
Severity Major
Root Cause The mechanism for allocating E-RACH resources is defective in cells
working in economical 4-channel demodulation mode.

Copyright © Huawei
Solution None
Impact
7.3.2.54 The FDE feature yields insignificant gains when a WBBPd board is
used and RTWP imbalance occurs.
Ticket
Number
Description Compared with the rake receiver feature, the frequency domain
equalization (FDE) feature yields insignificant or even negative gains if
all the following conditions apply:
 The WBBPd board provides uplink baseband resources.
 The cell works in 2-antenna receive mode.
 The received total wideband power (RTWP) is imbalanced between
the two antennas.
Severity Major
Root Cause In the event of single-path propagation or RTWP imbalance, FDE

algorithms use a defective mechanism during user selection.
Solution None
Impact
7.3.2.55 An exported configuration file cannot be activated on a NodeB that

has been upgraded from V100R008 to V100R009.
Number
Description After a NodeB is upgraded from V100R008 to V100R009, a

configuration file is uploaded by running the ULD CFGFILE command
and then downloaded to the NodeB by running the DLD CFGFILE
command. The file fails to be activated by running the ACT CFGFILE
command.
Severity Major
Root Cause The configuration file for the source version contains incorrect
subordination relationships between managed objects and therefore fails
configuration rule checks when the ACT CFGFILE command is

Copyright © Huawei
executed.
Solution The subordination relationships are now modified during the upgrade so
that the upgraded eNodeB meets the configuration rules.
Solution None
Impact
7.3.2.56 The U2000 fails to collect cell RF data of a NodeB configured with
the UMPT.
Ticket
Number
Description Condition: The U2000 collects cell RF data of a NodeB configured with
the UMPT.
Symptom: Cell RF data collection fails.
Impact: The U2000 fails to collect cell RF data of the NodeB.
Severity Major
Root Cause The internal channel of the NodeB for RF data collection is incorrectly
configured.
Solution The internal channel is now correctly configured.
Solution None
Impact
7.3.2.57 ALM-28206 Local Cell Capability Decline is reported when it

should not be.
Ticket
Number
Description Condition: On the WebLMT, the SET ULOCELLMACHSPARA

command is executed with Secondary DC-HSDPA,DB-HSDPA Cell
Activation Switch set to ON. However, the local cell is not configured
with the DC-HSDPA or DB-HSDPA function or the local cell does not
support the function even though it has been configured with the
function.
Symptom: The local cell reports ALM-28206 Local Cell Capability
Decline, with the cause value of "Users have configured the activation
and deactivation capability for the supplementary carrier of a cell but

Copyright © Huawei
actually this capability of the supplementary carrier is not supported".

Impact: ALM-28206 Local Cell Capability Decline is falsely reported.
Severity Major
Root Cause The mechanism for the local cell to make a decision on the support of
this function is defective.
Solution The defective mechanism has been rectified. Specifically, ALM-28206
Local Cell Capability Decline is now not reported if the local cell is not
configured with this function or the local cell does not support the
function even though it has been configured with the function.
Solution None
Impact
7.3.2.58 There is a possibility that the RRU3804 and WRFU fail to be

upgraded.
Number
Description Condition: The O&M personnel attempt to upgrade the RRU3804 and
WRFU to BTS3900 V100R009C00SPC110 or BTS3900
V100R009C00SPC112.
Symptom: The RRU3804 and WRFU are always in the startup status.
ALM-26254 Board Software Synchronization Failure is reported.
Impact: The upgrade fails.
Severity Major
Root Cause The file creating mechanism for software upgrade is defective.
Solution The defective mechanism has been corrected to ensure reliable file
creation.
7.3.2.59 The U2000 fails to deliver a power license in specific scenarios.

Number
Description Condition: The license file on the NodeB contains only the license
control item named Power License (per 20W).
Symptom: The U2000 fails to deliver the following license control items

Copyright © Huawei
to the NodeB:
Local Cell Number in 430(0.1dBm)
Impact: The power license cannot be delivered to the NodeB on the
U2000.
Severity Major
Root Cause The NodeB uses a defective license management module for power
control.
Solution The defects in the license management module for power control have
been rectified.
Solution None
Impact
7.3.2.60 When HSUPA services are carried on the WBBPd board, inner loop
power control occasionally does not function well.
Ticket
Number
Description Condition: The uplink resource group includes the WBBPd board, which
carries HSUPA services, and the switch for correcting the SIR when the
RTWP is abnormal (controlled by ULINNERPCABNRISECTRLSW)
is turned off for the NodeB.
Symptom: The SIR for HSUPA users occasionally reaches the peak
value and cannot approximate to the target SIR. As a result, user
throughput decreases.
Impact: Inner loop power control does not function well on the physical
layer of the baseband chip.
Severity Major
Root Cause The NodeB uses defective software for implementing inner loop power
control. Specifically, if the switch for correcting the SIR when the RTWP
is abnormal is turned off and the HSUPA services switch between the
high-rate and low-rate states, the state switchover flag occasionally is not
promptly configured on the baseband chip.
Solution Software defects have been rectified.
Solution None
Impact

Copyright © Huawei
7.3.2.61 The NodeB performance counter

VS.HSUPA.Boosting.UtilizeTimeRatio returns an inaccurate value.
Ticket
Number
Description Condition: A cell supports the Boosting feature and serves Boosting-
enabled UEs.
Symptom: The NodeB performance counter
VS.HSUPA.Boosting.UtilizeTimeRatio returns a value larger than
expected.
Impact: The VS.HSUPA.Boosting.UtilizeTimeRatio counter returns an
inaccurate value.
Severity Major
Root Cause The downlink DSP uses a defective mechanism to measure the
VS.HSUPA.Boosting.UtilizeTimeRatio counter. Specifically, the
downlink DSP incorrectly determines whether UEs use Boosting
resources.
Solution None
Impact
7.3.2.62 The transmit power of a pRRU processing uplink and downlink

services at peak rates becomes 0 occasionally.
Ticket
Number
Description Condition: A cell is activated and a UE is configured to access a local

pRRU and then perform uplink and downlink peak services.
Symptom: There is a possibility that transmit power of a pRRU processing
services becomes 0.
Impact: Ongoing services are interrupted.
Severity Major
Root Cause The BBU and pRRU does not process link disconnection detection
synchronously. Therefore, there is possibility that the pRRU detects a link
disconnection that is unknown to the BBU. The pRRU disables the power
amplifier 5s after detecting a link disconnection. However, the BBU has

Copyright © Huawei
not detected the link disconnection and therefore does not perform the
follow-up procedure to reactivate the cell. Consequently, the power
amplifier remains disabled and the pRRU has no power output.
Solution The pRRU now disables the power amplifier 20s after detecting a link
disconnection.
Solution None
Impact

ID
7.3.2.63 A cell fails to be activated if a long Ethernet cable not in use is

connected to the RRU in the LampSite solution.
Ticket
Number
Description Condition: An unused Ethernet cable longer than 20 m is connected to

Port 1 on the RRU for a long time period.
Symptom: When users activate a cell, a message is displayed indicating
that some RRUs are successfully activated or RRU configuration fails.
Impact: The RRU experiencing an activation failure cannot provide
services.
Severity Major
Root Cause Signal loopback succeeds on Port 1 because of signal coupling.

Consequently, the RRU starts up and enters equipment mode.
Solution The criteria for an RRU to enter equipment mode have been modified.
Specifically, an RRU starts up and enters service mode when the software
version in the equipment zone is invalid.
Solution None
Impact

ID
7.3.2.64 The value returned by the VS.HSUPA.TTI2to10.Att counter is

larger than expected on the WBBPd board if the NodeB is upgraded from
V200R014C00 to V100R009C00SPC150 or an earlier V100R009C00.
Number

Copyright © Huawei
Description Condition: The NodeB is upgraded from V200R014C00 to

V100R009C00SPC150 or an earlier V100R009C00, HSUPA 2 ms TTI
users are served by the WBBPd board, and the maximum DSP occupancy
exceeds 80%.
Symptom: The value returned by the VS.HSUPA.TTI2to10.Att counter
increases on the WBBPd board.
Impact: The value returned by the VS.HSUPA.TTI2to10.Att counter on
the WBBPd board is larger compared with that in V200R014C00.
Severity Major
Root Cause Compared with V200R014C00, the current DSP occupancy of the
WBBPd board in V100R009C00SPC150 or an earlier V100R009C00 is
more likely to increase to over 80% and a switching from 2 ms TTI to 10
ms TTI is triggered as the number of admitted users increases.
Solution When the current DSP occupancy is about 80%, an improvement has
been made on the WBBPd board in V100R009C00SPC150 so that the
DSP occupancy is less likely to exceed 80% and a TTI switching is less
likely to be triggered.
Solution In the preceding scenario, V100R009C00SPC150 provides lower DSP
Impact occupancy on the WBBPd board compared with an earlier
V100R009C00 under the same conditions.
7.3.2.65 There is a low probability that the WBBPf board resets.

Number
Description Condition: The uplink resource group includes the WBBPf board, which
serves R99 users.
Symptom: There is a low probability that the WBBPf board resets.
Impact: Users served by the WBBPf board experience service drops.
Severity Major
Root Cause The WBBPf board uses a defective resource protection mechanism when
an exception occurs in post-decoding for R99 users. Specifically, there is
a low probability that the baseband resources for R99 users are not
completely released on the WBBPf board. If the baseband resources are
reused by HSUPA users, post-decoding for the R99 users keeps running
continuously.
Solution The WBBPf now uses an improved resource protection mechanism.
Solution None
Impact

Copyright © Huawei
7.3.2.66 The drop rate of PS services on the UBBPd board increases.

Ticket
Number
Description Condition: The UBBPd board is removed from a BBU subrack having a
main control board of an earlier software version and then is inserted to a
BBU subrack having a main control board of a later software version.
After the UBBPd starts, an inter-board softer handover is performed.
Symptom: UEs served by the UBBPd board experience service drops
during the softer handover.
Impact: The drop rate of PS services increases by about 20%.
Severity Major
Root Cause In the preceding scenario, exceptions occur in the internal packet
distribution table of the UBBPd board. As a result, softer handover-
related packets are lost.
Solution The internal packet distribution table of the UBBPd board has been
corrected to ensure that the softer handover-related packets are not lost in
the same condition.
Solution None
Impact
7.3.2.67 The maintenance link for an RRU3804 is disconnected after the

NodeB is upgraded to V200R014C00SPC350
Trouble iCare:1709952
Number
Description ALM-26235 RF Unit Maintenance Link Failure is reported after

RRU3804s with an incorrect startup path are upgraded to
V200R014SPC350. This alarm indicates that maintenance links are
disconnected.
Severity Major
Root Cause During manual commissioning before delivery, some RRU3804s had
their startup path incorrectly set. After these RRU3804s are upgraded,
they cannot load software from the flash drive during booting and then
start from the BootROM instead.
Version V200R014C00SPC350 provides different clock rates for startup
from the BootROM and from the flash drive. As a result, establishing
links fails at the common public radio interface (CPRI) when RRU3804s
attempt to start from the BootROM.

Copyright © Huawei
Solution The clock rate for startup from the BootROM has been changed to be the
same as that for startup from the flash drive.
Solution None
Impact
7.3.2.68 The call drop rate increases and the RRC connection setup success
rate decreases after the Uplink Enhanced CELL_FACH feature is activated
Ticket
Number
Description After the Uplink Enhanced CELL_FACH feature is activated in a cell

and the cell receives a PHYSICAL SHARED CHANNEL
RECONFIGURATION REQUEST message, UEs in the cell
occasionally experience more link establishment failures and unexpected
link removal. When this fault occurs, the PS/CS call drop rate increases
and the RRC connection setup success rate decreases.
Severity Major
Root Cause Channel reconfiguration associated with the Uplink Enhanced

CELL_FACH feature is defective.
Solution Channel reconfiguration associated with the Uplink Enhanced
CELL_FACH feature has been corrected.
Solution None
Impact
7.3.3 Minor
7.3.3.1 When VSWR tests are conducted on multiple frequencies, the
VSWR indicator cannot properly reflect the test result.
Number
Description Condition: The STR VSWRTEST command is executed to start VSWR

tests on multiple frequencies in offline mode.
Symptom: The VSWR indicator is on only when the last frequency's
VSWR exceeds a predefined threshold. The indicator is off even if a
preceding frequency's VSWR exceeds the threshold but the last frequency's
VSWR does not exceed the threshold. In the latter case, the indicator does

Copyright © Huawei
not properly reflect the test result.

Impact: Maintenance engineers cannot determine the VSWR status
according to the indicator.
Severity Minor
Root Cause During the offline VSWR test on multiple frequencies, a later test result
overwrites its previous test result. The VSWR indicator is turned on only
when the last frequency's VSWR exceeds the threshold.
Solution The VSWR indicator is no longer used to reflect offline VSWR test results.
Instead, the command output is now used for this purpose.
Solution None
Impact
7.3.3.2 HSDPA Inter-Cell Power Sharing fails to take effect.

Ticket
Number
Description Condition: HSDPA Inter-Cell Power Sharing is activated for HSDPA

cells. Downlink baseband resources for the power sharing cell group are
separately established on the WBBPd/WBBPb and WBBPf/UBBP
boards.
Symptom: The VS.HSDPAPwrShare.TtiNum counters return value 0.
NOTE
VS.HSDPAPwrShare.TtiNum: indicates the number of TTIs within which the
HSDPA cell uses shared power.
Impact: The HSDPA Inter-Cell Power Sharing feature fails to take effect.
Severity Minor
Root Cause The number of supported cells varies among the WBBPd/WBBPb and
WBBPf/UBBP boards and the NodeB uses a defective mechanism to
check the number of supported cells when processing the HSDPA Inter-
Cell Power Sharing feature.
Solution None
Impact

Copyright © Huawei
7.3.3.3 Counters related to full buffer HSDPA throughput return inaccurate

values for a cell.
Ticket
Number
Description Condition: An HSDPA cell serves low-throughput HSDPA users.

Symptom: Counters VS.HSDPA.FullBuffer.Throughput.SumNum.0
through VS.HSDPA.FullBuffer.Throughput.SumNum.10 return
inaccurate values.
NOTE
These counters measure the number of samples for HSDPA users in a full buffer at
different throughput intervals, reflecting the distribution of the single HSDPA user
throughput at these throughput intervals.
Impact: Throughput distribution of HSDPA users served by a cell in a
full buffer cannot be accurately evaluated.
Severity Minor
Root Cause The statistical method for the counters is defective. Specifically, the
counters include traffic of HSDPA users having no data to transmit in the
full buffer after scheduling.
Solution The defective statistical method has been corrected.
Solution None
Impact
7.3.3.4 There is an extremely low probability that the main control board
unexpectedly restarts.
Number
Description Condition: The "Cell Service Resource Query" monitoring item under
"UMTS Monitor" has been started and the NodeB is providing services
for UEs.
Symptom: There is an extremely low probability that the main control
board unexpectedly restarts.
Impact: Ongoing services carried on the NodeB are interrupted.
Severity Minor
Root Cause The mechanism for multiple tasks to simultaneously access a shared
resource is defective.

Copyright © Huawei
Solution None
Impact
7.3.3.5 ALM-26765 RHUB Hardware Fault is reported when it should not be

in the LampSite solution.
Ticket
Number
Description Condition: An RHUB is rolled back from a new version (BTS3900

V100R009C00SPC100 or later) to an old version (earlier than BTS3900
V100R009C00SPC100) or software of an old version runs on the latest
RHUB hardware.
Symptom: ALM-26765 RHUB Hardware Fault is occasionally reported
when it should not be.
Impact: User experience deteriorates, although services are properly
processed.
Severity Minor
Root Cause The output voltage of RHUBs in new versions is 57 V, and the voltage
threshold for reporting ALM-26765 RHUB Hardware Fault in old
versions is 58 V. In addition, the detected voltage may differ slightly from
the actual voltage. If the detected value exceeds 58 V, the alarm is
reported.
Solution The voltage threshold for reporting ALM-26765 RHUB Hardware Fault
is now changed from 58 V to 60 V.
Solution None
Impact
7.3.3.6 The upgrade and rollback process of a fully configured LampSite

base station is time-consuming.
Ticket
Number
Description Condition: The software version of a fully configured LampSite base

station is upgraded or rolled back.
Symptom: There is a low probability that pRRU activation takes more
than one hour.
Impact: The upgrade or rollback process is time-consuming.

Copyright © Huawei
Severity Minor
code errors occur in the links between them, causing loss of the
downloaded software package data. Consequently, data is retransmitted,
which prolongs the activation process.
link connectivity when clock signals fluctuate within a certain range. The
link connectivity prevents loss of the downloaded software package data.
Solution None
Impact
7.3.3.7 When DC-HSUPA UEs are at the cell edge or the secondary cells are
congested, the UE throughput decreases.
Ticket
Number
Description Condition: The DC-HSUPA feature is enabled.

Symptom: The throughputof DC-HSUPA UEs at the cell edge is lower
than that of SC-HSDPA UEs. The throughput of secondary cells
decreases.
Impact: User experience of DC-HSUPA UEs deteriorates and the service
rates of other UEs in secondary cells decrease.
Severity Minor
Root Cause DC-HSUPA uplink secondary carriers consume power resources for
transmission on the dedicated physical control channel (DPCCH).
However, secondary carriers cannot be used to transmit data for UEs at
the cell edge because the UE transmit power is limited, DPCCH power
waste of the secondary carrier.
When the secondary cell load is limited, the scheduling mode for online
DC-HSUPA UEs in the CELL_DCH state does not ensure authorization
for one RLC PDU. As a result, no data is transmitted on the secondary
carrier but the DPCCH consumes power, affecting the cell throughput.
Solution If the coverage is limited for DC-HSUPA UEs, deactivate the secondary
carriers to save the UE transmit power, thereby increasing the UE
throughput.
If congestion occurs on secondary carriers, deactivate secondary carriers
for DC-HSUPA UEs to reduce the uplink rise over thermal (ROT),
thereby increasing the cell throughput.
Solution The throughput of secondary cells increases.
Impact The throughputof DC-HSUPA UEs at the cell edge increases (to the SC-
HSUPA UE throughput).

Copyright © Huawei
The number of DC-HSUPA UEs whose secondary carriers are activated

is reduced.
7.3.3.8 Uplink FFT frequency scan on pRRUs in the LampSite solution

returns inaccurate interfering frequencies.
Ticket
Number
Description Condition: Uplink FFT frequency scan on pRRUs in the LampSite

solution is started.
Symptom: In the event of external interferences, the scan results display
inaccurate interfering frequencies.
Impact: Users cannot identify the exact interfering frequencies.
Severity Minor
Root Cause The LampSite solution uses a defective mechanism for calculating the
frequency of interfering signals.
Solution The defective mechanism has been rectified to ensure the accuracy of the
calculated interfering frequencies.
Solution None
Impact
7.3.3.9 ALM-26529 RF Unit VSWR Threshold Crossed is occasionally

reported when it should not be in the LampSite solution.
Ticket
Number
Description Condition: Cells of a LampSite base station are activated and providing
services properly.
Symptom: ALM-26529 RF Unit VSWR Threshold Crossed is
occasionally reported for some pRRUs.
Impact: These pRRUs cannot work properly.
Severity Minor
Root Cause Due to limited hardware capability of pRRUs, the VSWR measurement
accuracy does not satisfy the requirements for detecting ALM-26529 RF
Unit VSWR Threshold Crossed. As a result, this alarm is occasionally
reported when it should not be.

Copyright © Huawei
Solution The start conditions for detecting ALM-26529 RF Unit VSWR Threshold
Crossed have been modified and this alarm is not detected by default.
Solution None
Impact
7.3.3.10 Some pRRUs cannot be started after a LampSite base station is

upgraded or reset.
Ticket
Number
Description Condition: A LampSite base station is upgraded or reset.

Symptom: There is a low probability that some pRRUs report ALM-
26251 Board Type and Configuration Mismatch.
Impact: These pRRUs cannot provide services.
Severity Minor
Root Cause The LampSite base station uses a defective address allocation algorithm
that results in address overlapping when multiple pRRUs are configured.
As a result, pRRUs are incorrectly detected as RHUBs and cannot be
started.
Solution The LampSite base station now uses a correct address allocation
algorithm.
Solution None
Impact
7.3.3.11 The links between pRRUs and the BBU in the LampSite solution
become faulty.
Ticket
Number
Description Condition: pRRUs in the LampSite solution are restarted.

Symptom: There is a low probability that ALM-26235 RF Unit
Maintenance Link Failure is reported.
Impact: Services are interrupted on the pRRUs for which this alarm is
reported.
Severity Minor

Copyright © Huawei
code errors are generated in the links between the pRRUs and the BBU,
causing intermittent link disconnections.
link connectivity when clock signals fluctuate within a certain range.
Solution None
Impact
7.3.3.12 WRFD-01061212 HSUPA Iub Flow Control in Case of Iub

Congestion occasionally fails to take effect.
Ticket
Number
Description Condition: The bandwidth is limited on the NodeB and the HSUPA flow
control switch is turned on. The NodeB serves both HSUPA users and R99
users. A specific baseband processing unit in the uplink resource group
serves only HSUPA users.
Symptom: The rates of HSUPA users served by the baseband processing
unit drastically fluctuate or these HSUPA users experience call drops.
Impact: WRFD-01061212 HSUPA Iub Flow Control in Case of Iub
Congestion fails to take effect on the baseband processing unit.
Severity Minor
Root Cause The implementation mechanism of WRFD-01061212 HSUPA Iub Flow

Control in Case of Iub Congestion is not robust enough.
Solution The robustness of the implementation mechanism of WRFD-01061212
HSUPA Iub Flow Control in Case of Iub Congestion has been improved.
Solution None
Impact

ID
7.3.3.13 The mechanism for checking the verification code on the LMT
login page is incorrect after a base station upgrade.
Number
Description Condition: A user attempts to log in to the LMT after a base station
upgrade from a version earlier than BTS3900
V100R009C00SPC110 to BTS3900 V100R009C00SPC110 or

Copyright © Huawei
later.
Symptom: The user inputs the correct verification code on the
LMT login page but an error message "Enter a correct verification
code" is displayed and the login fails.
Impact: The user cannot use the LMT.
Severity Minor
Root Cause From BTS3900 V100R009C00SPC110 onwards, the verification

code for LMT login contains both digits and letters. In earlier
versions, however, the verification code contains only digits. When
a user attempts to log in to the LMT after a base station upgrade,
the browser still uses the original scripts locally buffered to verify
the new verification code. As a result, an error message "Enter a
correct verification code" is displayed.
Solution When the locally buffered scripts of a version earlier than BTS3900
V100R009C00SPC110 are used to check the verification code, a
verification code that contains only digits is displayed on the LMT
login page.
7.3.3.14 The RTWP reaches the peak value when UEs are moving at high
speeds.
Number
Description Condition: The uplink resource group includes the WBBPb or WBBPd
board, which serves high-speed UEs.
Symptom: Peak RTWP occurs in the cell serving the high-speed UEs.
Impact: The value returned by the VS.MaxRTWP increases for the cell.
Severity Minor
Root Cause In high-speed scenarios, adjustment of the search algorithm on the

WBBPb or WBBPd board cannot keep up with UEs' moving speeds. In
this case, the NodeB determines that the transmit power of the UEs is low
and instructs the UEs to increase their transmit power.
Solution The search algorithm has been optimized on the WBBPb and WBBPd
board to adapt to high-speed scenarios. Bit17 under the REVDPARA1
parameter in the SET NODEBRSVPP command controls whether to
optimize the search algorithm. When Bit17 is set to 1, the search
algorithm is optimized. The search algorithm is not optimized by default.
Solution None
Impact

Copyright © Huawei
7.3.3.15 Counters measuring HSUPA performance return inaccurate values.

Ticket
Number
Descriptio Condition: The uplink resource group includes the WBBPf or UBBPd
n board, which serves HSUPA users with data transmission.
Symptom: The following counters depending on the traffic of Mac-e/Mac-i
TRBs return incorrect values.
VS.HSUPA.TTI2msUserNumber.0~VS.HSUPA.TTI2msUserNumber.5
VS.HSUPA.TTI10msUserNumber.0~ VS.HSUPA.TTI10msUserNumber.7
VS.HSUPA.Thruput.ROTMor3
VS.HSUPA.LowRateTTI2msUserNumber
VS.HSUPA.Thruput.ROTAll
Impact: The preceding counters return inaccurate values.
Severity Minor
Root The downlink DSP uses a defective mechanism to measure the traffic of the
Cause Mac-e/Mac-i TRBs received from HSUPA users.
Solution The defective mechanism has been corrected to ensure that the downlink
DSP correctly measures the traffic of the Mac-e/Mac-i TRBs.
Solution None
Impact
Test Case ATP -2014061006481

ID
7.3.3.16 When the E-DPCCH Boosting feature is activated, HSUPA

throughput decreases on the WBBPd board.
Ticket
Number

Copyright © Huawei
Description Condition: The E-DPCCH Boosting feature is activated.

Symptom: HSUPA service throughput occasionally decreases after the
E-DPCCH Boosting feature is activated.
Impact: Enabling the E-DPCCH Boosting feature reduces the HSUPA
throughput.
Severity Minor
Root Cause In the preceding instance, the power control algorithm on the WBBPd
board is not robust and does not adapt to all radio channels.
Solution The power control algorithm has been optimized to increase the
robustness when the E-DPCCH Boosting feature is activated.
Solution None
Impact
7.3.3.17 The inter-frequency handover success rate decreases if the Huawei

RNC interworks with the RNC provided by a peer vendor.
Number
 The Huawei RNC interworks with the RNC provided by a peer
vendor.
 UEs are served by the WBBPb or WBBPd board.
 The inter-frequency handover is triggered, changing parameters
related to the compressed mode.
Symptom: The radio link fails to be added.
Impact: The inter-frequency handover success rate decreases.
Severity Minor
Root Cause The NodeB uses a defective mechanism to maintain parameters related
to the compressed mode.
Solution None
Impact

Copyright © Huawei
7.3.3.18 EVT-28200 Iub Common Procedure Failure Indication is frequently

reported in specific scenarios.
Number
Description Condition: A common signaling procedure fails over the Iub interface
and the RNC periodically initiates common signaling procedures.
Symptom: A large number of EVT-28200 Iub Common Procedure
Failure Indication events are reported.
Impact: Other alarm logs are overwritten and ongoing services are not
affected.
Severity Minor
Root Cause The RNC triggers periodic retries with an interval of 10s to 30s after a
common signaling procedure fails over the Iub interface.
Solution EVT-28200 Iub Common Procedure Failure Indication for each type of
common signaling procedure failure is reported only once within 10
minutes for a cell.
Solution None
Impact
7.3.3.19 The CE preemption rules for PS services need to be optimized.

Ticket
Number
Description Condition: The Platinum User Prioritizing feature is enabled for a

NodeB, which serves platinum users, and the uplink channel element
(CE) resources are insufficient.
Symptom: Platinum users occasionally experience PS preemption
failures.
Impact: Platinum users do not enjoy the highest service priority. When
uplink CE resources are insufficient, there is a probability that they fail to
access the network.
Severity Minor
Root Cause The preemption algorithm is defective. To be specific, only resources

occupied by users who are served by the specific board and are not
experiencing soft handovers can be preempted.
Solution The defective preemption algorithm has been modified so that platinum
users can preempt resources of users served by any board on the NodeB,
including users experiencing soft handovers.
Solution None

Copyright © Huawei
Impact
7.3.3.20 If baseband resources or RF resources for a local cell are

insufficient, the NodeB falsely reports alarms related to the local cell.
Ticket
Number
Description Condition: Baseband resources or RF resources for a local cell are

insufficient.
Symptom: The NodeB reports ALM-28211 Cell Configuration
Abnormal, ALM-28203 Local Cell Unusable, and ALM-28206 Local
Cell Capability Decline with inaccurate alarm causes.
Impact: The alarm causes do not indicate actual faults.
Severity Minor
Root Cause The mapping between fault symptoms and alarm cause values is
inaccurate.
Solution The inaccurate mapping has been corrected for baseband or RF resource-
related alarms to ensure that the alarms are reported with correct alarm
causes under the same condition.
Solution None
Impact
7.3.3.21 Deployment check on a LampSite base station fails.

Ticket
Number
Description Condition: A deployment check is started on a LampSite base station

serving LTE cells.
Symptom: The Test installation & deployment quality check item fails
to be executed.
Impact: The deployment check fails.
Severity Minor
Root Cause pRRUs do not support VSWR check.
Solution The scripts for deployment check have been modified so that the VSWR
check is not performed for pRRUs.

Copyright © Huawei
Solution None
Impact
7.3.3.22 In 0.5/0.5 configuration, some RRUs become unavailable when

CPRI resources are insufficient.
Ticket
Number
Description Condition: Service configurations exceed CPRI specifications.

Symptom: In 0.5/0.5 configuration, each RRU is derated to 1T1R
configuration in V200R015 and earlier versions; whereas in
V200R016C00, one RRU is not derated and the other RRU becomes
unavailable.
Impact: Ongoing services in the cell coverage area of the unavailable
RRU are interrupted.
Severity Minor
Root Cause The sequence of allocating CPRI resources to antennas serving the same
cell is incorrect.
Solution The sequence has been corrected.
Solution When service configurations exceed CPRI specifications and CPRI

Impact resources are insufficient, 1T1R derating occurs in the cell coverage areas
of the two RRUs.
7.3.3.23 The congestion detection algorithm needs to be optimized at the

transport layer for HSUPA services.
Ticket
Number
Description Condition: HSUPA services are running properly with data transmission.
The uplink Iub congestion control algorithm is enabled for a NodeB
carrying heavy traffic.
Symptom: There is an extremely low probability that the available
transmission bandwidth keeps decreasing and approximates to the
minimum UL available bandwidth of a logic port (specified by the
ULIUBMINBW parameter in the SET ULFLOWCTRLPARA
command).
Impact: HSUPA throughput is limited, and services are dropped due to a

Copyright © Huawei
TRB reset.
Severity Minor
Root Cause The uplink Iub congestion control algorithm needs to be optimized in
versions earlier than RAN15.1. Specifically, there is an extremely low
probability that the NodeB enabled with this algorithm incorrectly
determines that congestion occurs over the Iub interface and reduces the
available transmission bandwidth when detecting that a traced UE
experiences packet loss and other UEs do not.
NOTE
With the uplink Iub congestion control algorithm, the NodeB traces transmitted and
received FP packets for congestion detection.
Solution The uplink Iub congestion control algorithm has been optimized to
ensure accurate congestion detection results. Specifically, the NodeB now
considers transmitted and received FP packets of multiple UEs during
congestion detection.
Solution The downlink traffic over the Iub interface slightly increases, and the
Impact values returned by counters related to downlink traffic over the Iub
interface increase. Some of the counters include VS.IPPath.RxBytes (IP
transmission), VS.IPPath.RxPkts (IP transmission), and
VS.AAL2PATH.RxPkts (ATM transmission).
7.3.3.24 If the downlink baseband equipment includes a WBBPb board and

other baseband processing units, such as WBBPd, WBBPf, and UBBPd,
downlink cell resources are unevenly distributed among these boards.
Ticket
Number
Description Condition: The downlink baseband equipment includes a WBBPb board

and other baseband processing units, such as WBBPd, WBBPf, and
UBBPd. The local cell is enabled with any of the MIMO, ULL2,
UL16QM, FDE, or Boosting feature.
Symptom: Downlink cell resources are established on non-WBBPb
boards. As a result, downlink CEs are insufficient or the downlink DSP
becomes overloaded.
Impact: Downlink cell services are unevenly distributed among the
boards in the downlink baseband equipment.
Severity Minor
Root Cause The WBBPb board uses a defective baseband resource allocation
mechanism. Consequently, all cells are established on the non-WBBPb
boards in the preceding scenario.
Solution The defective baseband resource allocation mechanism on the WBBPb

Copyright © Huawei
board has been corrected.

Solution None
Impact
7.3.3.25 Incorrect software is loaded to RF modules that are not reset after a
hot swap of their fiber optic cables.
Description Condition: A user hot swapped the fiber optic cables of two RF
modules of different types but does not manually reset the two RF
modules.
Symptom: Incorrect software is loaded to the RF modules during
the base station upgrade.
Impact: The RF modules cannot be started.
Severity Minor
Root Cause The mechanism used to check the matching between the hardware
and software of RF modules is defective in upgrade scenarios.
Solution The mechanism used to check the matching between the hardware
and software of RF modules has been enhanced in upgrade
scenarios.
7.3.3.26 The RRU type cannot be modified by running MML commands.

Description The RRU type cannot be modified by running MML commands on
the base station LMT.
Severity Minor
Root Cause No MML command is available for modifying the RRU type.
Solution The RT parameter has been added to the MOD RRU command for
the user to modify the RRU type of
MRRU/LRRU/MRXU/PRRU/GRRU or
MRFU/WRFU/LRFU/MTXU/GRFU.
Solution Impact The RF module whose RRU type is modified will automatically

Copyright © Huawei
reset. If this RF module is carrying services, the carried services

will be interrupted. The RF module can provide services again only
after working properly.
7.3.3.27 The priority configured for OM packets does not take effect on the
LMT.
Number
Description Condition: The SET DIFPRI command is executed to set the

priority of OM packets to 34.
Symptom: The DSCP value of OM packets transmitted between
the base station and the U2000 is 34 while that of the OM packets
transmitted between the base station and the LMT is 0.
Impact: The DSCP value configured for OM packets does not take
effect on the LMT and the OM function of the LMT may be
unstable when transmission resources are congested.
Severity Minor
Root Cause The DSCP value configured by the SET DIFPRI command for
OM packets does not take effect on the LMT.
Solution The base station now sends the DSCP value configured by the SET
DIFPRI command for OM packets to the LMT and the configured
DSCP value takes effect after being received by the LMT.
7.3.3.28 The value range of Board RTWP is not properly set.

Number
Description Condition: The Board RTWP parameter is displayed using a vertical

coordinate on the WebLMT.
Symptom: The parameter value range in the vertical coordinate is
automatically configured from 0 to -2000, but the actual value range is
-500 to -1200.
Impact: User experience is affected.
Severity Minor
Root Cause The algorithm for automatically setting the parameter value range in the

Copyright © Huawei
vertical coordinate is defective.

Solution The defective algorithm has been rectified. Specifically, when the
parameter value approaches to the maximum value or minimum value in
the vertical coordinate, the parameter value range in the coordinate is
extended so that the value range is clearly and completely displayed.
Solution None
Impact
7.3.3.29 The value returned by the VS.HSUPA.TTI2to10.Att counter is

greater than expected if the NodeB is upgraded from V200R014C00 to
V100R009C00SPC120 or an earlier V100R009C00.
Ticket
Number
Description Condition: The NodeB is upgraded from V200R014C00 to

V100R009C00SPC120 or an earlier V100R009C00, there are HSUPA 2
ms TTI users, and the maximum DSP occupancy exceeds 80%.
Symptom: The value returned by the VS.HSUPA.TTI2to10.Att counter
is greater than expected.
Impact: The value returned by the VS.HSUPA.TTI2to10.Att counter is
greater compared with that in V200R014C00.
Severity Minor
Root Cause Compared with V200R014C00, the current DSP occupancy in

V100R009C00SPC120 or an earlier V100R009C00 is more likely to
increase to over 80% and a switching from 2 ms TTI to 10 ms TTI is
triggered as the number of admitted users increases.
Solution When the current DSP occupancy is about 80%, a specific improvement
has been made in V100R009C00SPC120 so that the DSP occupancy is
less likely to exceeds 80% and a TTI switching is less likely to be
triggered.
Solution Under the same conditions, V100R009C00SPC120 provides lower DSP
Impact occupancy compared with an earlier version.
7.3.3.30 There is an extremely low probability that an RL fails to be added

or reconfigured for UEs in an IC-capable cell in heavy traffic scenarios.
Ticket

Copyright © Huawei
Number
Description Condition: An IC-capable cell is established in the uplink resource group

that contains the WBBPa or WBBPb board and the cell serves a massive
number of UEs. The license control item "Dual-Threshold Scheduling
with IC Function(per Cell)" is activated for the cell.
Symptom: There is an extremely low probability that the UEs experience
failures in RL addition or reconfiguration.
Impact: KPI performance of the UEs deteriorates.
Severity Minor
Root Cause In the preceding scenario, the NodeB uses a defective mechanism to
allocate resources to UEs served by the IC-capable cell. Therefore,
exceptions occur in the resource allocation process.
Solution None
Impact
7.3.3.31 The alarm cause for ALM-28203 Local Cell Unusable is inaccurate.
Ticket
Number
Description Condition: The sector equipment used by a local cell includes an RF unit
that is not added by using the ADD RRU or ADD AAS command.
Symptom: When the local cell becomes unavailable, the NodeB reports
ALM-28203 Local Cell Unusable alarms twice whose cause values are
Uplink RF Resource Unavailable and Downlink RF Resource
Unavailable respectively.
Impact: Both the alarm causes are inaccurate.
Severity Minor
Root Cause In the preceding scenario, the NodeB incorrectly determines the cause
value for ALM-28203 Local Cell Unusable.
Solution The NodeB now correctly determines the cause value for ALM-28203
Local Cell Unusable. In the preceding scenario, the NodeB reports ALM-
28203 Local Cell Unusable alarm only once with the cause value of RF
Board Unavailable.
Solution None
Impact

Copyright © Huawei
7.3.3.32 When MOCN is enabled, counters related to CE consumption on

the WBBPf or UBBPd board return inaccurate values for some operators.
Ticket
Number
Description Condition: In a MOCN network, the RB is reconfigured for a UE served

by the WBBPf or UBBPd board and the operator ID changes after the
reconfiguration.
Symptom: Counters related to CE consumption of the related operators
return inaccurate values.
Impact: Counters related to CE consumption of the related operators
return incorrect values. Such counters include
VS.HSUPA.LC.ULMax.LicenseGroup and
VS.LC.ULMax.LicenseGroup.
Severity Minor
Root Cause The NodeB uses defective software to manage the ID of the operator that
serves the UE.
Solution None
Impact
7.3.3.33 After a NodeB is upgraded to V100R009, link interruption

occasionally occurs on a WRFU.
Ticket
Number
Description After a NodeB is upgraded to V100R009, a WRFU occasionally

experiences link interruption and reports ALM-26235 RF Unit
Maintenance Link Failure.
Severity Minor
Root Cause The CPRI initialization module is defective. CPRI stands for common
public radio interface.
Solution The defects in the CPRI initialization module have been rectified.
Solution None
Impact

Copyright © Huawei
7.3.3.34 When the NCP or CCP is configured with master and slave CP
bearers and CP Switch Flag is set to Disable, the NCP/CCP becomes
abnormal after the NodeB is upgraded or reset.
Number
Description The NodeB control port (NCP) or communication control port (CCP)
becomes abnormal if all of the following conditions are true:
 The NCP or CCP is configured with master and slave CP bearers.
 In the LST CPSWITCH command output, the value of CP Switch
Flag is Disable.
 The NodeB is reset or is upgraded to V100R009.
 In the output of the DSP IUBCP command executed after the NodeB
is upgraded, the value of Port Status is Fault.
 In the output of the DSP CPBEARER command executed after the
NodeB is upgraded, the values of Port Status and Used Status are
Normal and Unused, respectively.
Severity Minor
Root Cause In the preceding scenario, the CCP/NCP switches over to a faulty CP
bearer.
Solution The NCP/CCP now selects a functional CP bearer.
Solution Ongoing services are not affected.

Impact
7.3.3.35 No alarms are reported to inform operators of IP frame errors.

Ticket
Number
Description Condition: The micro engine or memory of the WMPT board

experiences soft failures owing to electromagnetic radiation.
Symptom: The RRC connection setup success rate is low and traffic
statistics of the NodeB show that a massive number of IP error frames
are discarded. However, no related alarms are generated to inform
operators of the fault.
Impact: The operators fail to be alerted promptly.
Severity Minor
Root Cause The NodeB does not report any alarms to inform operators of IP packet
discarding due to an IP header check error.

Copyright © Huawei
Solution The NodeB now reports ALM-25897 IP Excessive Frame Error Rate
upon detecting that IP packets are discarded due to an IP header check
error.
Solution None
Impact
7.3.3.36 UEs experience access failures due to WebLMT login

authentication.
Ticket
Number
Description Condition: The WMPT serves as the main control board of the NodeB
and the operator logs in to the NodeB through the WebLMT for the first
time after the NodeB is started.
Symptom: The CPU usage of the WMPT board increases significantly
and the high CPU usage lasts for tens of seconds to several minutes. As a
result, UEs cannot access the NodeB.
Impact: The RRC connection setup success rate and RAB setup success
rate decrease.
Severity Minor
Root Cause An extra calculation is required for login authentication during the first
login, causing the CPU usage of the WMPT board to increase
significantly due to limited hardware capabilities of the WMPT board.
Solution A mechanism is now available to control the impact of calculations for
login authentication on the CPU. To be specific, when the service load is
light, the login authentication process can occupy sufficient CPU
resources; when the service load is heavy, the login authentication
process releases CPU resources.
Solution The time required for the first login prolongs and the following message
Impact may be displayed: "Preparations are being made for security
authentication of the first login. Please try again 5 minutes later."
7.3.3.37 The OpenSSL is vulnerable to security threats.

Number
Description Condition: The operator downloads an FTP server on the WebLMT

and runs the FTP server.

Copyright © Huawei
Symptom: The OpenSSL version is 1.0.1e.

Impact: The OpenSSL is vulnerable to security threats.
Severity Minor
Root Cause There is a Heartbleed bug in OpenSSL 1.0.1e.
Solution The OpenSSL used by the FTP server has been upgraded to 1.0.1g.
7.3.3.38 The WBBPf or UBBPd board occasionally experiences a channel

reconfiguration failure for an uplink R99 user.
Ticket
Number
Description Condition: The uplink resource group contains the WBBPf or UBBPd
board, and transport channel 0 for an uplink R99 user experiences TTI
switching.
Symptom: Channel reconfiguration sometimes occurs on the Iub
interface.
Impact: Channel reconfiguration sometimes occurs on the Iub interface.
Severity Minor
Root Cause In the preceding scenario, channel reconfiguration for an uplink R99
user takes effect at an unexpected time.
Solution Channel reconfiguration for an uplink R99 user now takes effect at an
expected time.
Solution None
Impact
7.3.3.39 Values of the counters measuring IC on the WBBPf or UBBPd

board are less than those on the WBBPd board after both the IC and CCPIC
features have been enabled for a NodeB.
Ticket
Number
Description Condition: Both the IC and CCPIC features have been enabled for a
NodeB, and the uplink resource group contains the WBBPf or UBBPd

Copyright © Huawei
board and serves multiple users.

Symptom: Values of VS.FirstStageIcEff.Mean and
VS.FirstStageIcEff.Max are slightly less than expected.
Impact: If both the IC and CCPIC features have been enabled for a
NodeB, gains produced when the uplink resource group contains the
WBBPd and WBBPf or UBBPD board are less than gains produced
when the uplink resource group contains only the WBBPd board.
Severity Minor
Root Cause The WBBPd board and WBBPf board use a defective mechanism for
selecting CCPIC users, and therefore CCPIC does not take effect for
some users.
Solution None
Impact
7.3.3.40 The value range of Local Cell Radius is incorrect for a multi-RRU
cell.
Ticket
Number
Description Condition: Local Cell Type is set to MULTIRRU_CELL and Local

Cell Radius to be greater than 30 km by running the ADD ULOCELL
or MOD ULOCELL command on the WebLMT.
Symptom: The ADD ULOCELL or MOD ULOCELL command is
executed successfully. The output of the DSP ULOCELL command
shows that the multi-RRU cell is available.
Impact: The UE access success rate in the cell decreases. After a UE
accesses the cell, the cell throughput declines.
Severity Minor
Root Cause When Local Cell Type is set to MULTIRRU_CELL, the value range of
Local Cell Radius is incorrect.
Solution When Local Cell Type is set to MULTIRRU_CELL, the value range of
Local Cell Radius now ranges from 150 to 30000 m.
Solution None
Impact

Copyright © Huawei
7.3.3.41 There is a possibility that the access performance degrades in a cell

using four receiving antennas.
Ticket
Number
 Local Cell Type is set to NORMAL_CELL.
 The uplink baseband processing units use 2-channel demodulation.
 The cell uses two RRUs (four receiving antennas in total) of the sector
equipment.
 One of the two receiving antennas used by the cell is faulty.
Symptom: The NodeB reports ALM-28206 Local Cell Capability
Decline because the local cell cannot use any available uplink baseband
resources in the uplink resource group.
Impact: The local cell has to use single-channel demodulation and the
access performance in the cell degrades.
Severity Minor
Root Cause In the preceding scenario, the cell uses a defective algorithm for
selecting receiving antennas. Therefore, the cell fails to select other
functional receiving antennas.
Solution None
Impact
7.3.3.42 The counters measuring the average finger energy of antennas and
the average ratio of the number of valid antennas to the number of
configured antennas return incorrect values.
Ticket
Number
Description Condition: The sector equipment used by a cell includes two or more
receiving antennas and one or more of the receiving antennas are faulty.
Symptom: The values of the following counters are smaller than
expected:
 VS.MeanEgy.Locell.SectorEqm.Ant0
 VS.MeanEgy.Locell.SectorEqm.Ant1
 VS.MeanEgy.Locell.SectorEqm.Ant2S.MeanEgy.Locell.SectorEqm.A
nt3

Copyright © Huawei
 VS.ValidAntRatio.Mean
Impact: Traffic counters return incorrect values.
Severity Minor
Root Cause The NodeB uses a defective mechanism to judge whether the receiving
antennas are functional.
Solution None
Impact
7.3.3.43 HSDPA UEs performing a soft handover and delayed activation on

the uplink dedicated channel sometimes experience call drops on the the
WBBPf or UBBPd board.
Ticket
Number
Description Condition: When UEs served by the WBBPf or UBBPd board are
performing softer handovers and delayed activation takes effect on the
uplink dedicated channel, the second NBAP_RL_ADD_REQ message
sent over the Iub interface does not include any indication of HSDPA
parameter updates. HSDPA UEs served by the UBBPd board are
performing soft handovers and the downlink link number or the ID of the
serving cell changes.
Symptom: The NodeB incorrectly updates HSDPA reconfiguration
parameters, causing data inconsistency with the RNC.
Impact: HSDPA UEs may experience call drops.
Severity Minor
Root Cause The WBBPf or UBBPd board uses defective software for processing the
NBAP_RL_ADD_REQ message. As a result, the WBBPf or UBBPd
board updates HSDPA reconfiguration parameters without checking the
validity of the received HSDPA parameters. The UBBPd board uses
defective software for processing soft handover-related signaling
messages of HSDPA UEs.
Solution None
Impact

Copyright © Huawei
7.3.3.44 The formulas for calculating the

VS.UUlCoMPGroup.MaxUserNum,
VS.BOARD.UsedHsdpaUserRatio.Max, and
VS.BOARD.UsedHsupaUserRatio.Max counters are exported when they
should not be.
Ticket
Number

Symptom:
 The formulas for calculating the VS.UUlCoMPGroup.MaxUserNum,
VS.BOARD.UsedHsupaUserRatio.Max counters are mistakenly
exported in the northbound list.
 The methods for measuring the VS.UUlCoMPGroup.MaxUserNum,
VS.BOARD.UsedHsupaUserRatio.Max counters are incorrect in the
northbound list.
Impact: The formulas for calculating the three counters are displayed in
the northbound list when they should not be.
Severity Minor.
Root Cause  The parameters used to calculate the

VS.UUlCoMPGroup.MaxUserNum,
VS.BOARD.UsedHsupaUserRatio.Max counters are Huawei internal
parameters, and should not be displayed in the northbound list.
 The methods for measuring the VS.UUlCoMPGroup.MaxUserNum,
VS.BOARD.UsedHsupaUserRatio.Max counters are incorrect.
Solution  Incorrect display of the formulas for calculating the three counters has
been rectified.
 The incorrect methods for measuring the three counters have been
rectified.
Solution None
Impact
7.3.3.45 The NodeB reports an invalid value of performance counters

related to the uplink load after OLC event measurement is enabled on the
RNC side.

Copyright © Huawei
Ticket
Number
Description After the ADD UCELLALGOSWITCH command is executed on the

RNC side with OLC_EVENTMEAS set to OLC Event Meas
Algorithm, the RTWP Monitoring item in Cell Performance
Monitoring on the LMT shows that the value of UL Required Load
and UL Total Load reported by the NodeB is invalid.
Severity Minor
Root Cause When OLC event measurement is enabled on the RNC side, the NodeB
uses a defective mechanism for processing the uplink load data, thereby
reporting invalid values for UL Required Load and UL Total Load.
Solution The NodeB now correctly processes and reports the values of UL
Required Load and UL Total Load.
Solution In the preceding scenario, after the NodeB is upgraded to V100R009,
Impact values of the following performance counters on the RNC side are
affected:
 VS.MeanULTotalLoad
 VS.MaxULTotalLoad
 VS.MinULTotalLoad
 VS.MeanULRequiredLoad
 VS.MaxULRequiredLoad
 VS.MinULRequiredLoad
7.3.3.46 RRC connections fail to be set up because VLAN configurations of

the WBBPb board occasionally fail to take effect.
Ticket
Number
Description There is a low possibility that RRC connections fail to be set up for cells
served by the WBBPb board if the following two conditions apply:
 Downlink resource groups of local cells are set up on the WBBPb
board.
 The VLAN configurations of the NodeB are changed.
Severity Minor
Root Cause After resetting, the LAN switch on the WBBPb board uses a defective
mechanism for updating the VLAN configuration data.

Copyright © Huawei
Solution None
Impact
7.3.3.47 The performance of the WBBPf board is not high as expected when
it works with the WBBPa, WBBPb, or WBBPd board.
Ticket
Number
Description When the WBBPf board and other types of baseband boards are
configured in a subrack, users are preferentially served by the WBBPf
board in specific scenarios. In this situation, if a large number of R99
users are admitted on the WBBPf board, new HSUPA users cannot be
admitted on the WBBPf board. As a result, the performance of the
WBBPf board is not as high as would be expected.
Severity Minor
Root Cause The user deployment policy does not consider the scenario where the
NodeB can obtain better overall gains (for example, when the IC feature
has been activated) if HSUPA users are admitted on the WBBPf board.
Solution CEs are now reserved for HSUPA users. When the number of R99 users
admitted on the WBBPf board reaches a predefined threshold, new R99
users are admitted on other baseband boards.
Solution In the preceding scenario, the value of the VS.FirstStageIcEff.Mean
Impact counter may decrease slightly.
7.3.3.48 The uplink transmission delay variation over the Iub interface is
not measured accurately on the WBBPf board.
Ticket
Number
Description If the uplink resource group of the NodeB includes a WBBPf board and
the WBBPf board provides services, the values of the following counters
are greater than expected:
 NodeB-level performance counters
− VS.IUB.FlowCtrol.UL.DelayVara.LgcPort1.Max
− VS.IUB.FlowCtrol.UL.DelayVara.LgcPort1.Avg
− VS.IUB.FlowCtrol.UL.DelayVara.LgcPort2.Max
− VS.IUB.FlowCtrol.UL.DelayVara.LgcPort2.Avg

Copyright © Huawei
 Transmission resource group-level performance counters

− VS.RscGroup.FlowCtrol.UL.DelayVara.Max
− VS.RscGroup.FlowCtrol.UL.DelayVara.Avg
Severity Minor
Root Cause The WBBPf board uses a defective mechanism for measuring the uplink
transmission delay variation over the Iub interface.
Solution None.
Impact
7.3.3.49 The IC feature occasionally generates no gains for UEs served by a

WBBPf4 board.
Ticket
Number
Description When a WBBPf4 board is configured into two sets of uplink baseband
equipment, and the IC and Turbo IC features are activated in the cell, the
following issues occur:
 The value of Cell measured RTWP after interference cancellation is
the same as the value of Cell measured RTWP on the WebLMT.
 Counters VS.HSUPA.Ic.MeanEff and VS.HSUPA.Ic.MaxEff return
values smaller than the actual ones.
Severity Minor
Root Cause The method of calculating cell RTWP after IC is defective. RTWP is
short for received total wideband power.
Solution The defective calculating method has been corrected.
Solution None
Impact
7.3.3.50 UTRAN cells sometimes do not recover immediately after non-

UTRAN cells release RF or route resources.
Ticket
Number

Copyright © Huawei
Description When the SingleRAN solution is used, UTRAN cells become

unavailable if the RF or route resources are occupied by non-UTRAN
cells. However, the UTRAN cells sometimes do not recover immediately
after the non-UTRAN cells release RF or route resources.
Severity Minor
Root Cause After the non-UTRAN cells release RF or route resources, the status of
UTRAN cells is not promptly updated.
Solution Cell resource allocation policies are optimized on SingleRAN networks.
Therefore, UTRAN cells become available 5 minutes after non-UTRAN
cells release resources.
Solution None
Impact
7.3.3.51 Cells are occasionally not evenly distributed among baseband

processing units.
Ticket
Number
Description Output of the DSP ULOCELLRES command indicates that cells are
occasionally not evenly distributed among baseband processing units if
both of the following conditions apply:
 The downlink baseband equipment includes a WBBPf4 board.
 The Resource Allocate Rule parameter is set to Handover
Performance First Rule.
Severity Minor
Root Cause The downlink resources are not properly allocated.
Solution Downlink resource allocation has been optimized to provide better cell
distribution and to reduce the derating of dual- or multi-carrier cells.
Solution Cells are evenly distributed among baseband processing units.
Impact
7.3.3.52 The RNC perceives that a logical cell is still usable even though
frequencies or power is not properly configured for this cell.
Ticket

Copyright © Huawei
Number
Description Versions earlier than SRAN9.0 occasionally experience the issue that the
RNC and NodeB have different logical cell status perception of the same
cell. When the RNC instructs the NodeB to set up a logical cell, the
NodeB responds with a success message but reports that this logical cell
is unusable if this cell conflicts with other RAT cells in baseband or RF
resources. This issue is likely to occur on multi-mode base stations if RF
and baseband resources are not properly configured for resource sharing.
Severity Minor
Root Cause The logical cell setup procedure is defective. To be specific, the NodeB
notifies the RNC of successful cell setup before the logical cell is
actually set up.
Solution The defective cell setup procedure has been corrected. The NodeB
notifies the RNC of successful cell setup only after the logical cell is
properly configured.
Solution If baseband or RF resources conflict during logical cell setup, the NodeB
Impact notifies the RNC of logical cell setup failure. In this way, the RNC
obtains the correct status of this logical cell.
7.3.3.53 RF resources are not properly allocated after an RF unit is derated.

Ticket
Number
Description After an RF unit is derated due to high temperature or insufficient power

supply, new cells are still established on this RF unit, therefore
intensifying the derating level.
Severity Minor
Root Cause RF resources are not properly allocated.
Solution New cells are not established on a derated RF unit.
Solution None
Impact
7.3.3.54 The RTWP occasionally increases when UEs initially access a cell.
Ticket
Number

Copyright © Huawei
Description In the event of heavy traffic, the RTWP occasionally increases when
UEs initially access a cell.
Severity Minor
Root Cause When UEs initially access a cell, the WBBPb, WBBPd, and WBBPf
boards use a defective uplink synchronization mechanism.
Solution A quick synchronization mechanism is introduced to reduce the
synchronization time.
Solution The demodulation performance is improved, lowering the probability
Impact that RTWP increases.
7.3.3.55 Certain features are still available even though their licenses have
entered the emergency state.
Ticket
Number
Description Certain features are still available even though their licenses have
entered the emergency state.
Severity Minor
Root Cause The following licenses in the emergency state are assigned an incorrect
value Unlimited:
 HSUPA Time Division Scheduling (per cell)
 Flexible Dual Carrier HSDPA (per NodeB)
 Uplink CoMP (Joint Reception) (per Cell)
 HetNet Uplink CoMP(Joint Reception) (per Cell)
 Uplink CoMP (Joint Reception) Based on Coordinated BBU (per
NodeB)
 Macro-Micro DC-HSDPA (per Cell)
 Macro-Micro Multiple RRUs in One Cell (per Cell*RRU)
Solution The preceding licenses are assigned correct values once these licenses
enter the emergency state.
Solution None
Impact

Copyright © Huawei
7.3.3.56 No possible causes are reported for ALM-28203 Local Cell

Unusable.
Ticket
Number
Description GRRU modules are configured to serve UTRAN cells, but the licensed
capacity of RF GSM Multi-Mode license (per Module) is insufficient.
Consequently, UTRAN cells become unavailable. However, ALM-
28203 Local Cell Unusable reported by UTRAN cells provides the
specific problem "Uplink RF Resource Unavailable" or "Downlink RF
Resource Unavailable" but no possible causes.
Severity Minor
Root Cause No possible causes are reported for ALM-28203 Local Cell Unusable.
Solution In the preceding scenario, the possible cause "Multi-Mode License

Limitation" is reported for ALM-28203 Local Cell Unusable.
Solution None
Impact
7.3.3.57 In certain scenarios, ALM-28206 Local Cell Capability Decline is

not reported although it should be.
Ticket
Number
Description The capability of Turbo IC depends on the IC capability. After IC is

derated in a cell, Turbo IC is also derated.However, ALM-28206 Local
Cell Capability Decline is not reported for Turbo IC derating.
Severity Minor
Root Cause During the alarm reporting process, dependency between Turbo IC and
IC is not detected.
Solution Dependency between Turbo IC and IC has been added.
Solution None
Impact

Copyright © Huawei
7.3.3.58 The VS.HSDPCCH.POWER counter returns an incorrect value

when the WBBPf board is used.
Ticket
Number
Description The VS.HSDPCCH.POWER counter returns an incorrect value when the

WBBPf board is used.
Severity Minor
Root Cause Value of the VS.DPDCH.R99.POWER counter is mistakenly used as the

value of the VS.HSDPCCH.POWER counter.
Solution Correct methods are now used to measure the VS.HSDPCCH.POWER
counter.
Solution None
Impact
7.3.3.59 ALM-26203 Board Software Program Error is occasionally falsely

reported.
Ticket
Number
Description ALM-26203 Board Software Program Error is occasionally falsely

reported without affecting ongoing services.
Severity Minor
Root Cause The mechanism for detecting ALM-26203 Board Software Program
Error is defective.
Solution None
Impact
7.3.3.60 Root CSNs of parent and child alarms are not associated.
Ticket
Number
Description If two mutually associated alarms are generated on a NodeB, for

Copyright © Huawei
example, parent alarm ALM-26231 BBU CPRI Optical Module or

Electrical Port Not Ready and child alarm ALM-28203 Local Cell
Unusable, the root CSN of the child alarm is not associated with the
CSN of the parent alarm.
Severity Minor
Root Cause The root CSN association mechanism for alarms is defective. To be
specific, when the interval between two mutually associated are
generated reaches a specified threshold, root CSNs of the alarms cannot
be correctly associated.
Solution The defective root CSN association mechanism for alarms has been
corrected. To be specific, root CSNs of two mutually associated alarms
are still be correctly associated even if the interval between the alarms
are generated reaches a specified threshold.
Solution None
Impact
7.3.3.61 Names of measurement units, measurement objects, and

measurement clusters in GSM, UMTS, and LTE are normalized.
Trouble CR-SRAN90-2013042402
Ticket
Number
Description Names of measurement units, measurement objects, and measurement

clusters in GSM, UMTS, and LTE are normalized on counter-related
documents, U2000 interfaces, and performance report system (PRS)
interfaces.
Severity Minor
Root Cause Names of measurement units, measurement objects, and measurement

clusters in GSM, UMTS, and LTE are not uniformally designed.
Solution The new naming conventions are as follows:
Measurement object: Measurement of xxx Performance
Measurement unit: xxx Measurement [<per xxx>], for example, <per
Cell>
Measurement cluster: Measurements related to xxx
Solution The U2000 must support the new naming conventions.
Impact
Test Case ATP-CR-SRAN90-2013042402

Copyright © Huawei
7.3.3.62 Some faults in PnP deployment cannot be located.

Trouble IR-SRAN90-SITE-001
Ticket
Number
Description Many faults occurred during base station deployment are not recorded in
operation logs. When base station deployment fails, fault diagnosis
requires a significant amount of time.
Severity Minor
Root Cause Many faults occurred during base station deployment are not recorded in
operation logs. When base station deployment fails, faults cannot be
located.
Solution An operation log that records the PnP deployment process is added. In
addition, a log parsing tool is used to parse the information in the
operation log, making the fault information easier to understand.
Solution None
Impact
Test Case ATP-IR-SRAN90-SITE-001
7.3.3.63 An RF module is reset when its working mode is modified.

Trouble IR-SRAN90-SITE-003
Ticket
Number
Description When the working mode of an RF module is modified, the RF module is

reset and services carried on the RF module are interrupted.
Severity Minor
Root Cause When the working mode of an RF module is modified, the BBU sends a
soft reset command to the RF module.
Solution When the working mode of an RF module is modified, the RF module is
not reset and services carried on the RF module are not interrupted.
Solution None
Impact
Test Case ATP-IR-SRAN90-SITE-003
7.3.3.64 Base station deployment fails when two base stations are cascaded
by connecting FE/GE ports on the UTRP/WMPT/LMPT/UMPT boards to
form a VLAN in which each port uses multiple IP addresses.
Trouble CR-SRAN90-0137150C

Copyright © Huawei
Ticket
Number
Description When two base stations are cascaded by connecting FE/GE ports on the
UTRP/WMPT/LMPT/UMPT boards to form a VLAN in which each
port uses multiple IP addresses, the upper-level base station selects
incorrect gateway IP addresses. As a result, the plug-and-play (PnP)
deployment of the lower-level base station fails.
Severity Minor
Root Cause When two base stations are cascaded by connecting FE/GE ports on the
UTRP/WMPT/LMPT/UMPT boards to from a VLAN in which each
port uses multiple IP addresses and the upper-level base station serves as
a DHCP Relay agent for the lower-level base station, the upper-level
base station uses the first IP address (indicated by the Giaddr field)
configured for its FE/GE port. If this IP address does not belong to the
VLAN, packets are discarded during transmission. As a result, the PnP
deployment of the lower-level base station fails.
Solution When the upper-level base station receives a DHCP packet carrying a
VLAN tag from the lower-level base station, the upper-level base station
selects the OM IP address of itself and all the FE/GE port's IP addresses
that belong to the VLAN indicated by the VLAN tag as the gateway IP
addresses.
When the upper-level base station receives a DHCP packet not carrying
a VLAN tag from the lower-level base station, the upper-level base
station selects the OM IP address of itself and all the FE/GE port's IP
addresses that do not belong to any VLANs as the gateway IP addresses.
Solution None
Impact
Test Case ATP-CR-SRAN90-0137150C
7.3.3.65 The base station restarts and services are interrupted when clock
parameter settings are changed in batches through the CME.
Trouble CR-MBTS19-029
Ticket
Number
Description When clock parameter settings are changed in batches through the CME,
the base station restarts and services are interrupted for about five
minutes.
Severity Minor
Root Cause The TakeEffectType attribute of some parameters in the following MOs
is set to Rst sys: BITS, LINECLK, TOD, GPS, SYNCETH, and
IPCLKLINK. When the settings of these parameters are modified in
batches through the CME, the base station restarts.
Solution The TakeEffectType attribute of the following parameters is changed

Copyright © Huawei
from Rst sys to unmodifiable:

 BITS [CN, SRN, SN]
 LINECLK [CN, SRN, SN, PT, PN, PS]
 TOD [CN, SRN, SN, TYPE]
 GPS [CN, SRN, SN]
 SYNCETH [CN, SRN, SN, PN, TYPE]
 IPCLKLINK [CN, SRN, SN, ICPT, CIP, SIP, DM, CNM, IPMODE,
CIPV6, SIPV6, PREHOPIP, PDELAYREQFREQ]
Solution The TakeEffectType attribute of the parameters in the BITS,
Impact LINECLK, TOD, GPS, SYNCETH, and IPCLKLINK MOs is
changed.
Test Case ATP-CR-MBTS19-029
7.3.3.66 The upgrade risk check result incorrectly indicates that the
BootROM needs to be upgraded
Trouble iCare: 3849646/3849609
Number
Description Condition: Before a software upgrade is started, a user performs an

upgrade risk check using the upgrade risk check package.
Symptom: A message "For MRRU V3, there is a link failed risk if the
Bootrom version is older than 1C.178.10.019." is displayed, indicating
that the BootROM needs to be upgraded.
Impact: The message incorrectly indicates that an upgrade of a board's
BootROM is needed when it is not.
Severity Minor
Root Cause The upgrade risk check package contains BootROM-related check items
when it should not.
Solution The BootROM-related check items have been deleted from the upgrade
risk check package and BootROM upgrade descriptions have been
deleted from upgrade guides.
Solution None
Impact
7.3.3.67 Counters related to the Uplink Enhanced CELL_FACH feature

return incorrect values.

Copyright © Huawei
Ticket
Number
Description Counters VS.ERACH.OccupiedNum.Mean and

VS.ERACH.OccupiedNum.Max return values smaller than expected.
Severity Minor
Root Cause The accuracy in calculating counters VS.ERACH.OccupiedNum.Mean

and VS.ERACH.OccupiedNum.Max is not high. To be specific, the
calculation results are rounded down.
Solution These two counters use the floating-point computing method, with three
digits after the decimal point.
Solution None
Impact
7.3.4 Suggestion
7.3.4.1 RRU3826 (code: 02310UPA) and RRU3824 (code: 02310UNY) differ
from other RRU3826/RRU3824 units in postprocessing of ALM-26529 RF
Unit VSWR Threshold Crossed.
Ticket
Number
Description Condition: ALM-26529 RF Unit VSWR Threshold Crossed is reported,

indicating a high voltage standing wave ratio (VSWR) at RRU3826
(code: 02310UPA) and RRU3824 (code: 02310UNY).
In addition, the VSWR alarm post-processing switch parameter is set to
OFF for the RRUs.
Symptom: The eNodeB reduces the transmit power on RF channels to
minimize the impact of the high VSWR on the RRUs.
Impact: This VSWR alarm postprocessing mechanism differs from that
of other RRU3826/RRU3824 units.
Severity Suggestion
Root Cause RRU3826 (code: 02310UPA) and RRU3824 (code: 02310UNY) do not
inherit the VSWR alarm postprocessing mechanism of other
RRU3826/RRU3824 units.
Solution RRU3826 (code: 02310UPA) and RRU3824 (code: 02310UNY) now
inherit the VSWR alarm postprocessing mechanism of other
RRU3826/RRU3824 units. If the VSWR alarm post-processing switch
parameter is set to OFF for an RRU, the eNodeB does not take any
actions for the RRU.
Solution None

Copyright © Huawei
Impact
7.3.4.2 ALM-26522 RF Unit RX Channel RTWP/RSSI Unbalanced cannot be

cleared.
Description Condition: RF units experiencing from external interference report
ALM-26522 RF Unit RX Channel RTWP/RSSI Unbalanced, and the
RTWP returns normal after the external interference is cleared. The RF
units include:
 RRU3824: 02310KKP, 02310SXH, 02311AHQ, and 02310XGG
 RRU3826: 02310KKQ, 02310PRU, 02311AHM, 02310XFC, and
02310UWG
 MRFUV2: 02310KBP, 02310KBS, 02310KBT, 02310KBU,
02310MPA, 02310MPB, 02310KBH, 02310KBL, 02310KTD, and
02310KTE
 WRFUa: 02310LAL
Symptom: ALM-26522 RF Unit RX Channel RTWP/RSSI
Unbalanced cannot be cleared on the LMT.
Impact: The alarm information does not represent the actual RTWPs
of these RF units, misleading O&M engineers about the real time
status of RX channels.
Severity Suggestion
Root Cause The software uses a defective mechanism for clearing ALM-26522 RF
Unit RX Channel RTWP/RSSI Unbalanced.
Solution The defective mechanism has been corrected so that ALM-26522 RF
Unit RX Channel RTWP/RSSI Unbalanced can be properly triggered
and cleared.
7.3.4.3 ALM-26811 Configured Capacity Limit Exceeding Licensed Limit is

reported when it should not be in specific scenarios.
Ticket
Number
Description Condition: The WRFD-160251 HSDPA Inter-Cell Power Sharing feature

is activated for a NodeB and the "Power Sharing Function(per NodeB)"

Copyright © Huawei
license control item is not delivered to the NodeB.

Symptom: ALM-26811 Configured Capacity Limit Exceeding Licensed
Limit is reported when it should not be.
Impact: The alarm cannot be cleared as expected.
Severity Suggestion
Root Cause In the preceding instance, the HSDPA Inter-Cell Power Sharing feature is
not under license control but the NodeB incorrectly determines that the
feature is licensed by "Power Sharing Function(per NodeB)."
Solution The NodeB now determines that the HSDPA Inter-Cell Power Sharing
feature is not under license control.
Solution None
Impact
7.3.4.4 After a NodeB is upgraded to RAN16.0, the cause of ALM-28203

Local Cell Unusable changes
Number
 Both uplink and downlink baseband resources for a local cell are
unavailable. No baseband processing unit simultaneously provides
both the uplink and downlink baseband resources.
 Two ALM-28203 Local Cell Unusable alarms are reported with the
cause values "Downlink Baseband Resource Unavailable" and
"UplinkCommon Baseband Resource Unavailable" on the alarm
console.
Symptom: After a NodeB is upgraded to RAN16.0, only one ALM-
28203 Local Cell Unusable alarm is reported with the cause value
"Baseband Board Unavailable."
Impact: The alarm information changes after the upgrade, and the
change has no impact on ongoing services.
Severity Suggestion
Root Cause The mechanism for reporting ALM-28203 Local Cell Unusable is
defective.
Solution None
Impact

Copyright © Huawei
7.3.4.5 In BTS3900 V100R008C00SPC320 and later versions, the user

allocation policy for the UBBPd board requires modifications.
Ticket
Number
Description Condition: The uplink baseband equipment includes a WBBPf board and
a UBBPd board.
Symptom: After the NodeB is upgraded to BTS3900
V100R009C00SPC170, the values of the following counters vary:
 VS.CE.ULMean.Board
 VS.CE.ULMin.Board
 VS.CE.ULMax.Board
 VS.HSUPA.Ic.MeanEff
 VS.HSUPA.Ic.MaxEff
The former three counters indicate the board-level CE performance and
the latter two indicate the IC efficiency.
Impact: The number of UEs served by new features of BTS3900
V100R009C00 decreases on the UBBPd board.
Severity Suggestion
Root Cause In BTS3900 V100R008C00SPC320, the UBBPd and WBBPf boards

configured in the same baseband equipment use the same user allocation
policy. In BTS3900 V100R009C00, the user allocation policy requires
modifications because baseband resources must be reserved on the
UBBPd board to accommodate new features.
Solution In BTS3900 V100R008C00SPC320 and later versions, the user
allocation policy has been modified for the UBBPd board.
Solution None
Impact
7.3.4.6 The transmit power of pRRUs is reported as N/A occasionally in the

LampSite solution.
Ticket
Number
Description Condition: Cells served by pRRUs are activated and provide services
properly. The transmit power of the pRRUs is monitored through the
maintenance system (WebLMT or the U2000).
Symptom: The transmit power of the pRRUs is reported as N/A
occasionally.

Copyright © Huawei
Impact: User experience deteriorates, although services are properly

processed.
Severity Suggestion
Root Cause A defective mechanism is used for calculating the transmit power to be
reported. Consequently, the calculated transmit power is reported as an
invalid value N/A.
Solution The defective mechanism has been corrected to ensure the accuracy of
the reported pRRU transmit power.
Solution None
Impact
7.3.4.7 Rights management for the NIC tool is improper.

Number
Description Condition: A domain user uses the network information collector

(NIC) tool to collect network information.
Symptom: The domain user has no rights to some NIC functions
and NIC information collection fails.
Impact: The domain user needs to apply for the rights to some NIC
functions.
Severity Suggestion
Root Cause The domain user does not have the rights to some NIC functions.
Solution A G_NIC rights group is now added. Domain users that need to use
the NIC tool are only required to apply for the rights to G_NIC and
do not need to re-apply for rights after version upgrade.
7.3.4.8 Logs are lost when the OM link becomes faulty.

Number
Description Condition: The OM link on the base station side becomes faulty
and the base station is powered off or reset.
Symptom: Logs on the main control board are lost after the main
control board is powered off or reset.
Impact: The root cause for the OM link fault cannot be located

Copyright © Huawei
using logs.
Severity Suggestion
Root Cause Logs are not written into the flash of the main control board. After
the base station is powered off or reset due to an OM link fault, logs
on the main control board are lost.
Solution Debug logs are now written into the flash of the main control board
when the OM link keeps being faulty or becomes faulty.
7.3.4.9 In the parameter reference, parameters Execute Result, Fail Reason,

and Used Status are not associated with any MML command.
Ticket
Number

Symptom: In the parameter reference, no MML command is provided to
query or configure parameters Execute Result and Fail Reason under
the LOCELL MO and the Used Status parameter under the IUBCP MO.
Impact: The content of the parameter reference is incorrect.
Severity Suggestion
Root Cause Parameters Execute Result, Fail Reason, and Used Status have not
been used but have not been deleted from the parameter reference.
Solution Parameters Execute Result, Fail Reason, and Used Status have been
removed from the parameter reference.
Solution None
Impact
7.3.4.10 There is a low probability that alarms are incorrectly reported when
the optical power of optical modules is too high.
Number
Description Condition: Optical modules delivered by Huawei are used.

Symptom: There is a low probability that ALM-26232 BBU
Optical Module Transmit/Receive Fault or ALM-26506 RF Unit
Optical Interface Performance Degraded is frequently reported and

Copyright © Huawei
then cleared.
Impact: Users cannot determine whether the optical modules work
properly.
Severity Suggestion
Root Cause The conditions are improperly set for determining abnormal receive
and transmit power of optical modules delivered by Huawei.
Solution Error code detection is now performed alarms related to the optical
power are reported. If any error codes are detected, alarms will be
reported. If no error code is detected, no alarm will be reported.
7.3.4.11 The permission for uploading one-click logs is incorrectly

configured.
Number
Description Condition: Local users with a user-level account run the ULD
FILE command to upload one-click logs.
Symptom: The uploaded one-click logs contain security logs.
Impact: Local users with a user-level account have the permission
to view security logs that are exclusive to administrator-level users,
which poses security risks.
Severity Suggestion
Root Cause The one-click logs exported by local users with a user-lever
account contain security logs that are exclusive to administrator-
level users.
Solution Security logs have been removed from the one-click logs.
7.3.4.12 The UMTS or LTE side in a multimode base station incorrectly

reports an alarm ALM-26200 Board Hardware Fault.
Number
Description Condition: In a multimode base station, a multimode RRU is

added on the UMTS or LTE side, or the GSM main control board is
reset.

Copyright © Huawei
Symptom: The UMTS or LTE side reports an alarm ALM-26200

Board Hardware Fault and this alarm is cleared after about 5
seconds.
Impact: The alarm ALM-26200 Board Hardware Fault is
incorrectly reported.
Severity Suggestion
Root Cause In a multimode base station, the UMTS or LTE side locks the GSM
reference clock. After a multimode RRU is added on the UMTS or
LTE side, or the GSM main control board is reset, the UMTS or
LTE side switches the reference clocks, leading to clock jitter on
the UMTS or LTE main control board. As a result, service clocks
on the baseband processing boards become abnormal for a short
period of time and an alarm ALM-26200 Board Hardware Fault is
reported.
Solution The duration between alarm detecting and reporting has been
prolonged to prevent incorrect alarm reporting.
7.3.4.13 In certain scenarios, modifying the maximum transmit power of a

logical cell leads to abnormal cell output power.
Ticket
Number
Description Condition: When an RF module reports ALM-26529 RF Unit VSWR

Threshold Crossed and the VSWR alarm post-processing switch is turned
off, an operator modifies the maximum transmit power of a logical cell
on the RNC.
Symptom: The cell output power is abnormal.
Impact: Derating is not performed on the cell served by the RF module
and hardware of the RF module may be damaged.
Severity Suggestion
Root Cause In the preceding instance, the NodeB uses a defective derating
mechanism for the logical cell.
Solution The defective derating mechanism has been corrected.
Solution None
Impact

Copyright © Huawei
7.3.4.14 The statistical method for the performance counters

VS.HSUPA.PDUNum and VS.HSUPA.RetransPDUNum requires
optimization.
Ticket
Number
Description The method to measure the performance counters VS.HSUPA.PDUNum

and VS.HSUPA.RetransPDUNum requires optimization to achieve
complete HSUPA performance statistics and to facilitate estimation of the
BLER for the serving cell.
Severity Suggestion
Root Cause In the statistical process for the VS.HSUPA.PDUNum and

VS.HSUPA.RetransPDUNum counters, the NodeB does not differentiate
between the serving link and non-serving link.
Solution The NodeB now takes statistics only on the serving link to improve
HSUPA-related statistics.
Solution The counter values may decrease after the change.
Impact
7.3.4.15 The MO Counter Reference does not include descriptions about

MOs NODEBALGSIMLTTST and DLSIM.
Ticket
Number

Symptom: The MO Counter Reference does not include descriptions
about MOs NODEBALGSIMLTTST and DLSIM.
Impact: The MO Counter Reference does not match the MML
command reference.
Severity Suggestion
Root Cause Parameters under MOs NODEBALGSIMLTTST and DLSIM are not
written to the database but need to be displayed on the GUI and the MO
Counter Reference is inadequately prepared.
Solution Descriptions about MOs NODEBALGSIMLTTST and DLSIM have
been added to the MO reference.
Solution None
Impact

Copyright © Huawei
7.3.4.16 The transmission link is disconnected after the ADD SCTPPEER

command is executed to add an SCTP peer.
Number
Description Condition: The ADD SCTPPEER command is executed to add an

SCTP peer and the added SCTPPEERID is the same as that of an
existing transmission link.
Symptom: The transmission link is disconnected.
Impact: Base station services are interrupted.
Severity Suggestion
Root Cause The added SCTPPEERID is the same as that of an existing

transmission link and overwrites the SCTPPEERID of this
transmission link. Therefore, the IP address of the existing
transmission link is changed and this transmission link is
disconnected.
Solution A conflict check is now performed on the transmission objects
configured using MML commands. If the SCTPPEERID added by
the ADD SCTPPEER command is the same as that of an existing
transmission link, the added SCTPPEERID does not overwrite the
existing one.
7.3.4.17 ALM25955-SCTP Link IP Address Unreachable is reported when an

SCTP link that is configured with only a pair of IP addresses cannot
provide services.
Number
Description Condition: An SCTP link that is configured with only a pair of IP

addresses cannot provide services.
Symptom: ALM-25955 SCTP Link IP Address Unreachable is
reported and then is automatically cleared about 20 seconds later.
Impact: Services are not affected.
Severity Suggestion
Root Cause The base station does not check the number of peer IP addresses
configured for the SCTP link when reporting ALM-25955 SCTP
Link IP Address Unreachable. If only one peer IP address is
configured, ALM25955-SCTP Link IP Address Unreachable should
not be reported.

Copyright © Huawei
Solution The base station now checks the number of peer IP addresses
configured for the SCTP link that cannot provide services. If this
SCTP link is configured with only one peer IP address, ALM-25955
SCTP Link IP Address Unreachable is not reported.
7.3.4.18 When the NodeB serves remote cells, TP distribution is inaccurate.

Number
Description Condition: Radius of the cell is greater than 60 km.

Symptom: Transport Propagation Delay (TP) distribution for the cell is
smaller than expected.
Impact: TP distribution is inaccurate, but there is no impact on services.
Severity Suggestion
Root Cause In the preceding instance, the cell reports inaccurate TP.
Solution The cell now reports accurate TP.
Solution None
Impact
7.3.4.19 The NodeB fails to be upgraded to V100R009 or later versions in

certain scenarios.
Ticket
Number
Description Condition: Before the upgrade, no actual local cells are configured in the
following managed objects (MOs):
 R99ALGPARA
 MACEPARA
 MACHSPARA
 LOCELLRSVP
 RSCLMTPARA
 ALGOPARA
 NOACCESSALMPARA
Symptom: The NodeB fails to be upgraded to V100R009 or later

Copyright © Huawei
versions.
Impact: The NodeB upgrade fails.
Severity Suggestion
Root Cause The NodeB of a version earlier than V100R009 does not check the
parent-child relationship between MOs of a cell. Therefore, independent
MOs may exist on the NodeB. After the upgrade, the NodeB fails the
parent-child relationship check.
Solution During the upgrade, independent MOs are now automatically deleted to
ensure that the NodeB passes the parent-child relationship check.
Solution None
Impact
7.3.4.20 LRRUs and LRFUs of NodeBs earlier than V100R008 support

UMTS carriers with bandwidths narrower than 4.2 MHz.
Ticket
Number
Description LRRUs and LRFUs of NodeBs earlier than V100R008 support the
configuration of UMTS carriers with bandwidths narrower than 4.2
MHz. However, in V100R008, LRRUs and LRFUs do not support this
configuration.
Severity Suggestion
Root Cause LRRUs and LRFUs of NodeBs earlier than V100R008 do not check
whether the carrier bandwidth is narrower than 4.2 MHz.
Solution LRRUs and LRFUs of NodeBs earlier than V100R008 now check for
the carrier bandwidth narrower than 4.2 MHz using the risk check
package. LRRUs and LRFUs in V100R008 check for the carrier
bandwidth narrower than 4.2 MHz independently.
Solution During an upgrade to V100R009, the risk check package can identify
Impact invalid configurations and related risks.
7.3.4.21 The storage security of the PreShareKey Attribute for the

SECURITYTEMPLATE MO has been improved.
Ticket
Number

Copyright © Huawei
Description For the SECURITYTEMPLATE MO, the security type of the

PreShareKey attribute is General. The storage security of the
PreShareKey attribute needs to be improved.
Severity Suggestion
Root Cause The pre-shared key is sensitive data and therefore its storage security
needs to be improved.
Solution For the SECURITYTEMPLATE MO, the security type of the
PreShareKey attribute has been changed from General to Key.
Solution The attributes in the Key type are not displayed on the U2000.
Impact Therefore, operators can see that the PreShareKey attribute for the
SECURITYTEMPLATE MO is REMOVED on the U2000 after an
upgrade from SRAN8.x to SRAN9.0.
7.3.4.22 Parameter configuration for fault detection needs to be optimized.

Ticket
Number
Description Condition: The NodeB is configured with any of the WBBPb, WBBPd,
WBBPf, and UBBPd boards.
Symptom: Fault detection parameters cannot be configured using MML
commands.
Impact: Operator's requirements cannot be satisfied.
Severity Suggestion
Root Cause Fault detection parameters are not configurable.
Solution The SET NODEBKPIFAULTDETECTPARA command has been

added to configure fault detection parameters.
Solution None
Impact
7.3.4.23 No alarms are reported to inform operators of inconsistency

between RRU configurations and networking in specific scenarios.
Ticket
Number
Description Condition: For a distributed base station with RRU networking in a

chain topology, the last-level RRU is incorrectly connected to a

Copyright © Huawei
baseband processing unit of another base station and the link between
the last-level RRU and the original baseband processing unit becomes
disconnected.
Symptom: If the preceding fault is caused by a reset of the last-level
RRU, ALM-26235 RF Unit Maintenance Link Failure is reported. If the
preceding fault is not caused by a reset of the last-level RRU, no alarm is
reported.
Impact: The operator cannot be alerted promptly about inconsistency
between RRU configurations and networking that is not caused a reset of
the last-level RRU.
Severity Suggestion
Root Cause The NodeB uses a defective mechanism of detecting optical modules.
Solution The defective mechanism has been corrected. To be specific, ALM-

26504 RF Unit CPRI Interface Error has been added.
Solution None
Impact
7.3.4.24 Cells rarely become unavailable.

Ticket
Number
Description Condition: The WBBPb or WBBPd board of the NodeB is configured

with optical modules delivered by specific vendors.
Symptom: ALM-26232 BBU Optical Module Transmit/Receive Fault
and ALM-26233 BBU CPRI Optical Interface Performance Degraded
are reported.
Impact: CPRI links are intermittently disconnected and cells become
unavailable in severe cases.
Severity Suggestion
Root Cause The control channel processing mechanism is defective.
Solution None
Impact

Copyright © Huawei
7.3.4.25 When the CE Overbooking feature is activated and the uplink CE

usage of a baseband processing unit is high, UEs experience call drops
unexpectedly.
Ticket
Number
Description Condition: when HSUPA 2ms HSUPA users number is unbalance

between cells in a uplink resource group, the minimum Admission CE
for HSUPA 2ms user is not absolutely guaranteed based on parameter
CERSVFOR2MSUSER. And especially when traffic is high, admission
CE consumption is possible less than expected.
Symptom: UEs experience call drops unexpectedly.
Severity Suggestion
Root Cause the minimum number of CEs for admitting 2ms HSUPA users should be
guaranteed based on the parameter CERSVFOR2MSUSER for admitted
users'QoS when CE Overbooking is enabled. However because of
defective mechanism, the users' admitting CE in may lower than
CERSVFOR2MSUSER when HSUPA 2ms user number is high and
unbalance between cells.
Solution the minimum number of CEs for admitting 2ms HSUPA users should be
Impact absolutely guaranteed based on the parameter CERSVFOR2MSUSER
for admitted users, which would cause admission CE consumption rise
with low possibility.
7.3.4.26 The algorithm for a synchronization/asynchronization decision on

a UE using Uplink Enhanced CELL_FACH needs to be improved.
Ticket
Number
Description Call drop sometimes occurs when the Uplink Enhanced CELL_FACH
feature is enabled and channel quality is unfavorable. This symptom
increases the call drop rate.
Severity Suggestion
Root Cause When the Uplink Enhanced CELL_FACH feature is enabled, the
algorithm for a synchronization/asynchronization decision on a UE is
defective.
Solution An improvement has been made to the synchronization/asynchronization

Copyright © Huawei
decision algorithm.
Solution During an upgrade , the risk check package can identify invalid
Impact configurations and related risks.
7.3.4.27 Multi-RRU cells become unavailable due to insufficient licenses.

Ticket
Number
Description Condition: The NodeB version before upgrade is

V100R008C00SPC200. Multi-RRU cells are served by the NodeB.
Symptom: ALM-28203 Local Cell Unusable and ALM-26811
Configured Capacity Limit Exceeding Licensed Limit are reported
because power control licenses or quantity control licenses of local cells
are insufficient.
Impact: After the NodeB is upgraded, multi-RRU cells having
insufficient licenses become unavailable.
Severity Suggestion
Root Cause The NodeB V100R008C00SPC200 uses the strategy of consistency in

license sales and control for multi-RRU cells and does not provide a
grace period.
Solution In the preceding scenario, a grace period of 60 days is provided.
Solution None
Impact
7.3.4.28 The UMPT and SMPT boards abnormally reset in heavy traffic
scenarios.
Ticket
Number
Description The UMPT and SMPT boards abnormally reset in heavy traffic
scenarios, which affects ongoing services.
Severity Suggestion
Root Cause 1. In heavy traffic scenarios, the mechanism for recovering the
overloaded message processing unit becomes defective and therefore,
the UMPT and SMPT boards may abnormally reset.
2. In heavy traffic scenarios where the Linux SMP scheduling mode is

Copyright © Huawei
used, a single OS task is busy but the CPU of the OS is not

overloaded. However, the expt module (exception management
module) considers this situation abnormal and the UMPT board
abnormally resets.
Solution 1. If the message processing unit on a UMPT or SMPT board becomes
overloaded, the board determines whether the message processing
unit has recovered. If so, the board does not reset.
2. In heavy traffic scenarios where the Linux SMP scheduling mode is
used, the UMPT board abnormally resets if neither the CPU usage of
the OS nor the CPU usage of the current process is overloaded in the
following scenario: The message processing queue is full, the
resources of the message processing unit are exhausted, or the VBUS
queue is full. If either or both of the CPU usage of the OS and the
current process is overloaded, the UMPT board does not reset.
Solution None
Impact
7.3.4.29 The VS.DlCode.Used.Max and VS.DlCode.Used.Mean counters

return incorrect values.
Ticket
Number
Descrip Condition: The NodeB is upgraded to BTS3900 V100R009C00SPC020.

tion Symptom: The VS.DlCode.Used.Max counter returns 0 and the
VS.DlCode.Used.Mean counter return NIL.
Impact: The two counters return incorrect values.
Severity Suggestion
Root The NodeB uses a defective mechanism for reporting the cell-level code
Cause resource usage.
Solutio The defective mechanism has been corrected.

n
Solutio None
n
Impact
Test ATP-2014042301783
Case ID

Copyright © Huawei
7.3.4.30 The CCPIC efficiency of the Control Channel Parallel Interference

Cancellation (phase 2) feature configured on the WBBPd board is not
calculated accurately.
Ticket
Number
Description Condition: The Control Channel Parallel Interference Cancellation

(phase 2) feature is enabled on the WBBPd board.
Symptom: The value of the counter measuring the CCPIC (phase 2)
efficiency is smaller than expected.
Impact: The values of counters VS.FirstStageIcEff.Mean and
VS.FirstStageIcEff.Max are smaller than expected.
Severity Suggestion
Root Cause The mechanism for calculating the CCPIC efficiency of the Control
Channel Parallel Interference Cancellation (phase 2) feature is defective.
Solution The defective mechanism has been corrected to increase gains from
Control Channel Parallel Interference Cancellation (phase 2).
Solution The value of VS.FirstStageIcEff.Mean and VS.FirstStageIcEff.Max
Impact increases slightly.
7.3.4.31 Users are not alerted when they are removing multi-carrier cell
groups.
Ticket
Number
Description For an active logical cell, removing a multiple-carrier cell group by

using the RMV NODEBMULTICELLGRP command interrupts
services provided by the cell. Users are not alerted when they are
performing this operation.
Severity Suggestion
Root Cause No warning messages are displayed when a multicarrier cell group is
being removed.
Solution Users now are alerted when running the RMV
NODEBMULTICELLGRP command on the Web LMT or U2000.
Solution A confirmation dialog box is displayed when a user is running the MML
Impact command RMV NODEBMULTICELLGRP.

Copyright © Huawei
7.3.4.32 Sleeping cell-related alarm and event reporting is inaccurate.

Ticket
Number
Description If one of the two RX channels malfunctions in a multi-antenna cell, the

cell falsely reports ALM-28209 Cell No Traffic. This alarm indicates
that the cell is a sleeping cell.
After resolving a sleeping cell problem by using the self-healing method
specified by the AUTORCVRMTHD parameter in the LST
ULOCELLNOACCESSPARA command, the NodeB does not report
any events.
Severity Suggestion
Root Cause Sleeping cell-related alarm and event reporting is defective. Specifically,
when one of the RX channels malfunctions, ALM-28209 Cell No Traffic
is falsely reported, and no events are reported after a sleeping cell self-
heals.
Solution  A cell is considered a sleeping cell only when all channels have no
traffic in the cell, triggering ALM-28209 Cell No Traffic.
 Once resolving a sleeping cell problem by using a self-healing method,
the NodeB reports EVT-28231 UMTS Traffic Abnormal Recovery.
Solution None
Impact
7.3.4.33 One-click log export on the WebLMT provides fewer fields than
the MML command ULD FILE.
Ticket
Number
Description In the device management window of the WebLMT, one-click log export
for the main control board does not provide fields "IP Mode" or "Flow
Control Option". However, these fields are provided in the output of the
MML command ULD FILE.
Severity Suggestion
Root Cause New fields incorporated into the MML command ULD FILE are not
provided on the WebLMT.
Solution Fields "IP Mode" and "Flow Control Option" have been incorporated
into the WebLMT.
Solution None

Copyright © Huawei
Impact
7.3.4.34 Certain parameters for the MML command SET

NODEBSMTHPWRPARA are assigned incorrect default values.
Ticket
Number
Description The MML command SET NODEBSMTHPWRPARA is used to

activate the Intelligently Out of Service feature. However, services
cannot be migrated to other NodeBs if parameters Smart default step
and Smart default time ratio retain their default values.
Severity Suggestion
Root Cause Parameters Smart default step and Smart default time ratio in the
MML command SET NODEBSMTHPWRPARA are assigned
incorrect default values.
Solution The default values of Smart default step and Smart default time ratio
have been changed to 3 and 5, respectively. The MML online help and
parameter description are updated accordingly.
Solution None
Impact
7.3.4.35 The SLC detection algorithm requires optimization to avoid

incorrect detection results.
Ticket
Number
Description Condition: There is a big difference of traffic from a cell between days.
Symptom: The NodeB enabled with sleeping cell (SLC) detection
occasionally reports ALM-28209 Cell No Traffic when it should not.
Impact: This alarm is reported when it should not be, and there is no
impact on ongoing services.
Severity Suggestion
Root Cause The SLC detection algorithm is defective.
Solution The SLC detection algorithm has been optimized.
Solution The number of times the NodeB enabled with SLC detection falsely

Copyright © Huawei
Impact reports ALM-28209 Cell No Traffic due to incorrect SLC detection

results decreases.
Test Case ID AT-2014031801547
7.3.4.36 The NodeB falsely reports ALM-28230 Base Station Service

Overload.
Ticket
Number
Description Condition: The downlink resource group contains the WBBPb or

WBBPa board and HSDPA Scheduler Pool is enabled.
NOTE
HSDPA Scheduler Pool is enabled by running the SET NODEBALGPARA
command with the HSDPASCHPOOLSW parameter set to ON.
Symptom: The NodeB falsely reports ALM-28230 Base Station Service
Overload.
Impact: The NodeB falsely reports ALM-28230 Base Station Service
Overload.
Severity Suggestion
Root Cause Neither the WBBPb nor WBBPa board supports the HSDPA Scheduler
Pool function. In the preceding scenario, the NodeB falsely uses the
number of users supported by the downlink resource group rather than
the number of HSDPA users supported by the WBBPb or WBBPa board
to determine whether to report the alarm.
Solution The NodeB now uses the number of users supported by the WBBPb or
WBBPa board to determine whether to report the alarm.
Solution None
Impact
7.4 Known Issues

None.

Copyright © Huawei
BTS3900 V100R010C10SPC120 Operation and Maintenance ChangesOperation and
(NodeB) Release Notes Maintenance Changes
8 Operation and Maintenance Changes
8.1 MML Command Changes

For the MML command changes from BTS3900 V100R008C00SPC300 to BTS3900
V100R010C10, and from BTS3900 V100R009C00SPC180 to BTS3900 V100R010C10,see
BTS3900 V100R010C10 (NodeB) MML Command Changes.xls
The changes from BTS3900 V100R010C10 to BTS3900 V100R010C10SPC050 or later are
as follows:
For the changes related to equipment and transport, see
BTS3900 V100R010C10SPC120 Node MML Command Changes.xls
For the changes related to the radio part of NodeB, see
BTS3900 V100R010C10SPC120 NodeBFunction MML Command Changes.xls
8.2 Parameter Changes

For the Parameter changes from BTS3900 V100R008C00SPC300 to BTS3900
V100R010C10, and from BTS3900 V100R009C00SPC180 to BTS3900 V100R010C10, see
BTS3900 V100R010C10 (NodeB) MO and Parameter Changes.xls
as follows:
BTS3900 V100R010C10SPC120 Node MO and Parameter Changes.xls
BTS3900 V100R010C10SPC120 NodeBFunction MO and Parameter Changes.xls

Copyright © Huawei
8.3 Alarm Changes

For the Alarm changes from BTS3900 V100R008C00SPC300 to BTS3900 V100R010C10,
and from BTS3900 V100R009C00SPC180 to BTS3900 V100R010C10 , see
BTS3900 V100R010C10 (NodeB) Alarm Changes.xls
as follows:
BTS3900 V100R010C10SPC120 Node Alarm Changes.xls
BTS3900 V100R010C10SPC120 NodeBFunction Alarm Changes.xls
8.4 Event Changes

For the Event changes from BTS3900 V100R008C00SPC300 to BTS3900 V100R010C10,
and from BTS3900 V100R009C00SPC180 to BTS3900 V100R010C10 , see
BTS3900 V100R010C10 (NodeB) Event Changes.xls
as follows:
BTS3900 V100R010C10SPC120 Node Event Changes.xls
BTS3900 V100R010C10SPC120 NodeBFunction Event Changes.xls
8.5 Counter Changes

For the Counter changes from BTS3900 V100R008C00SPC300 to BTS3900 V100R010C10,
and from BTS3900 V100R009C00SPC180 to BTS3900 V100R010C10, see
BTS3900 V100R010C10 (NodeB) Performance Counter Changes.xls
as follows:
BTS3900 V100R010C10SPC120 Node Performance Counter Changes.xls
BTS3900 V100R010C10SPC120 NodeBFunction Performance Counter Changes.xls

Copyright © Huawei
8.6 License Changes

For the License changes , see
BTS3900 V100R010C10SPC120 (NodeB) License Changes.xls
8.7 Other Changes

8.7.1 The IP PM session function enabled on the UMTS network
is enhanced
Change Reason
The IP PM session function enabled on the UMTS network is enhanced. With the
enhancement, an IP PM session can be bound to an ANY-type IP path. Specifically,
 In RAN14.0, IP Path to which an IP PM session is bound is of the QoS type. With this
configuration, the IP PM session directly uses the DSCP value configured for the IP path.
 In V100R008, the IP path to which an IP PM session is bound can be of the ANY type.
With this configuration, no DSCP value is configured for the IP path and therefore the IP
PM session must be configured with a DSCP value.
As a result, when a four-tuples IP PM session is bound to an IP path, the IPPMDSCP
parameter must be visible to users.
Implementation
 In RAN14.0, if an IP PM session is bound to an IP path, the IPPMDSCP parameter is not
displayed on the GUI. In V100R008, if a four-tuples IP PM session is bound to an IP
path, the IPPMDSCP parameter is displayed on the GUI and its default value is 0.
Before the change:
After the change:
After a NodeB is upgraded from RAN14.0 to V100R009, the IPPMDSCP parameter value is
changed to 0 if a four-tuples IP PM session is bound to an IP path and the IPPMDSCP
parameter value is greater than 63.

Copyright © Huawei
Related Operations
None

None
8.7.2 Details of non-configuration parameters are displayed in the

Parameter Reference and MML Command Reference.
Change Reason
Details of non-configuration parameters are displayed in the Parameter Reference and MML
Command Reference.
Implementation
Non-configuration parameters are dynamic parameters in managed objects (MOs), for
example, IC Capability and DC Capability specify the effectiveness status of optional
features, and Cell ID is dynamically configured by the RNC for the NodeB through the Iub
interface. These dynamic parameters are not configured by users, and they only indicate the
operating status of NodeB functions or features. When a user queries a dynamic parameter by
running a DSP xxx command, details of the dynamic parameter can be viewed from the
Parameter Reference.
Related Operations
None

None
8.7.3 None NodeB service overload detection has been added

Change Reason
In V100R008, the 4C-HSDPA, DC-HSDPA, or DB-HSDPA function can be used together
with the MOCN function.
Implementation
The power of each carrier for a 4C-HSDPA, DC-HSDPA, or DB-HSDPA user is counted into
the operator-related power statistics counter. Therefore, MOCN-related power statistics
counters are affected. The involved counters are as follows:

Copyright © Huawei
Related Operations
None

None
8.7.4 The UDP port range for NodeB services changes

Change Reason
SRAN8.0 supports co-MPT GSM/UMTS/LTE multimode base stations. After the UDP port
range is allocated for each system, the port range for NodeB services changes.
Implementation
In V100R008, the UDP port for NodeB services ranges from 1024 to 17919. In RAN14.0, the
UDP port for NodeB services ranges from 1024 to 5823.
Related Operations
None

None
8.7.5 Data-related counters for the buffer of DC user queues may

change in each carrier
Change Reason
The DC scheduling algorithm changes.
Implementation
After the DC scheduling algorithm changes in V100R008, the information about queues of
DC users to be scheduled is invisible during the scheduling. Before the scheduling, the NodeB
MAC-ehs entity checks whether the statistics about data-related counters for the buffer of DC
user queues are collected in each carrier.
The following data-related counters may change:
 VS.DataRabNum.Mean
 VS.DataRabNum.Max
 VS.DataRabNum.Min
 VS.RabNumAve.UserData
 VS.DataOutput.RabData
 VS.DataTtiRatio.Mean
 VS.DataOutput.UserData

Copyright © Huawei
 VS.ScchPwrRatio.UserData
 VS.PdschPwrRatio.Data
 VS.PdschCodeUtil.Mean.Data
 VS.ScchCodeUtil.Mean.Data
 VS.HSDPA.InactiveDataTtiRatio.Mean
 VS.HSDPA.ScheInactiveDataTtiRatio.Mean
 VS.HSDPA.DataTtiNum.User
 VS.HSDPA.InactiveDataTtiNum.TRB
 VS.HSDPA.DataTtiNum.TRB
Related Operations
None

None
8.7.6 The AG collision function is deleted

Change Reason
The Absolute Grand (AG) collision function was introduced to the NodeB for commercial
trials and is proved to provide negligible gains during tests.
Implementation
Delete the AG collision function.
Related Operations
Delete value RSVDBIT18 from the REVDPARA1 parameter in the SET NODEBRSVP
command.

DTS: DTS2013042604207

Copyright © Huawei
BTS3900 V100R010C10SPC120
(NodeB) 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 On the Product Support tab page, enter BTS3900 WCDMA in the Search text box and click
the path automatically displayed.
Step 4 On the Product Documentation tab page, select a version from the Version Selection drop-
down list box to view or download the product document.
Step 5 Click a link in the Title column to view the document or to download the document.
----End

Copyright © Huawei
BTS3900 V100R010C10SPC120
(NodeB) Release Notes A Obtaining Documentation
 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
BTS3900 V100R010C10SPC120
(NodeB) Release Notes B Acronyms and Abbreviations
B Acronyms and Abbreviations
B
BBU BaseBand Unit
BSC Base Station Controller
BTS Base Transceiver Station
C
CPRI Common Public Radio Interface
CME Configuration Management Express
D
DRFU Double Radio Frequency Unit
DSCP DiffServ Code Point
DSP Destination Signaling Point
DSS Dynamic Spectrum Sharing
G
GPS Global Positioning System
GSM Global System for Mobile communications
GTMU Transmission, Timing, and Management Unit for
GTRU BTS

Copyright © Huawei
BTS3900 V100R010C10SPC120
IPSec IP Security
L
LAPD Link Access Protocol on the D channel
LMPT LTE Main Processing&Time Unit
LMT Local Maintenance Terminal
LTE Long Term Evolution
M
MLPPP Multi-Link Point-to-Point Protocol
MML Man-Machine Language
MRFU Multi-Mode Radio Frequency Unit
O
OCB Outdoor Cable Conversion Box
OM Operation and Maintenance
R
RNC Radio Network Controller
RRU Multi-mode Remote Radio Unit
S
SMT Site Maintenance Terminal
T
TDM Time Division Multiple
U
UMPT Universal Main Control and Transmission Unit
UMTS Universal Mobile Telecommunications System
USCU Universal Satellite card and Clock Unit
UTRP Universal Transmission Processing unit

Copyright © Huawei
BTS3900 V100R010C10SPC120
UMDU Universal Multimode Digital Unit
V
VLAN Virtual Local Area Network
W
WMPT WCDMA Main Processing&Time Unit

Copyright © Huawei

BTS3900 V100R010C10SPC120 (NodeB) Release Notes

Hochgeladen von

Dokumentinformationen

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

BTS3900 V100R010C10SPC120 (NodeB) Release Notes

Hochgeladen von

Copyright:

Verfügbare Formate

BTS3900 V100R010C10SPC120

(NodeB) Release Notes

HUAWEI TECHNOLOGIES CO., LTD.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Huawei Proprietary and Confidential

About This Document

Reviewed By Huang Tao/Wu Hongmei Date 2015-5-6

Tested By Kang Feng Date 2015-5-7

Approved By Li Huasong Date 2015-5-8

01 2015-5-8 Li Jiasui This issue is the first official

Issue 01 (2015-05-08) Huawei Proprietary and Confidential ii

− The feature summary includes information about capacity and performance,

Table 1 Section description

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 (2015-05-08) Huawei Proprietary and Confidential iii

− Known Issues: details known issues in this product version by severity.

Issue 01 (2015-05-08) Huawei Proprietary and Confidential iv

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

3 Changes from V100R010C10SPC100 to V100R010C10SPC120...........................................30

Issue 01 (2015-05-08) Huawei Proprietary and Confidential v

Issue 01 (2015-05-08) Huawei Proprietary and Confidential vi

4 Changes from V100R010C10SPC050 to V100R010C10SPC100...........................................55

Issue 01 (2015-05-08) Huawei Proprietary and Confidential vii

Issue 01 (2015-05-08) Huawei Proprietary and Confidential viii

4.3.3 Known Issues.............................................................................................................................................................83

5 Changes from V100R010C10 to V100R010C10SPC050.........................................................84

Issue 01 (2015-05-08) Huawei Proprietary and Confidential ix

6 Changes from V100R009C00SPC180 to V100R010C10.........................................................95

Issue 01 (2015-05-08) Huawei Proprietary and Confidential x

6.2.1.2.12 Enhanced Signature Algorithm for the Device Certificate..............................................................................138

Issue 01 (2015-05-08) Huawei Proprietary and Confidential xi

6.3.1.1.7 WRFD-171204 DPCH Power Control Based on Radio Quality.......................................................................172

Issue 01 (2015-05-08) Huawei Proprietary and Confidential xii

Issue 01 (2015-05-08) Huawei Proprietary and Confidential xiii

7 Changes from V100R008C00SPC300 to V100R010C10.......................................................293

Issue 01 (2015-05-08) Huawei Proprietary and Confidential xiv

7.2.1.3 Solution to Inconsistent License Sales and Control Strategies............................................................................313

Issue 01 (2015-05-08) Huawei Proprietary and Confidential xv

Issue 01 (2015-05-08) Huawei Proprietary and Confidential xvi

Issue 01 (2015-05-08) Huawei Proprietary and Confidential xvii

7.3.2.65 There is a low probability that the WBBPf board resets....................................................................................458

Issue 01 (2015-05-08) Huawei Proprietary and Confidential xviii

Issue 01 (2015-05-08) Huawei Proprietary and Confidential xix

Issue 01 (2015-05-08) Huawei Proprietary and Confidential xx

8 Operation and Maintenance Changes...................................................................................521

Issue 01 (2015-05-08) Huawei Proprietary and Confidential xxi

1.1 Product Version

Product BTS3900 WCDMA

1.2 Software Versions

LMT BTS3900 V100R010C10SPC120_NodeB(LMT)

Issue 01 (2015-05-08) Huawei Proprietary and Confidential 1

1.3 Hardware Versions

WMPT 200.017.10.  256 01.316.01.001 No NA

Issue 01 (2015-05-08) Huawei Proprietary and Confidential 2

Module Software Hardware BootROM BootRO Remark

WBBPb2 200.017.10.  17922 01.200.01.002 No NA

Issue 01 (2015-05-08) Huawei Proprietary and Confidential 3

Module Software Hardware BootROM BootRO Remark

RRU3804 1J.643.10.0  MRRU.HWEI.13 01.095.03.001 No NA

Issue 01 (2015-05-08) Huawei Proprietary and Confidential 4

Module Software Hardware BootROM BootRO Remark