BTS3900-BTS3900A-BTS3900L-DBS3900 WCDMA V200R011C01SPC752 Release Notes.doc

HUAWEI BTS3900-BTS3900A-BTS3900L-DBS3900 WCDMAV200R011C01SPC752

Release Notes

Issue 01

Date 2012-01-29

HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2011. All rights reserved.

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

Trademarks and Permissions

and other Huawei trademarks are the property 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: [email protected]

Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd.

mailto:[email protected]

http://www.huawei.com/

BTS3900-BTS3900A-BTS3900L-DBS3900 WCDMA V200R011C01SPC752 Release Notes About This Document

About This Document

Organization

Chapter Description

1 Version Mapping Provides the versions of the products and software for this release.

2 Version Compatibility Describes the compatibility with earlier product versions.

3 Version Changes Describes the changes in features, commands, parameters, alarms, counters, and licenses.

4 Solved Problems andUnsolved Problems

Describes the solved problems and unsolved problems.

5 Precautions Describes the precautions for this release.

6 Related Documents Describes how to obtain related documents.


BTS3900-BTS3900A-BTS3900L-DBS3900 WCDMA V200R011C01SPC752 Release Notes Contents

Contents

1 Version Mapping..........................................................................................................1-11.1 Product Version............................................................................................................................ 1-1

1.2 Software Versions........................................................................................................................ 1-1

1.3 Related Product Versions.............................................................................................................1-2

2 Version Compatibility..................................................................................................2-12.1 Compatibility with Earlier Product Versions..................................................................................2-1

3 Version Changes..........................................................................................................3-13.1 Changes from V200R011C01SPC751 to V200R011C01SPC752................................................3-1

3.1.1 Feature Changes................................................................................................................. 3-1

3.1.2 MML Command and Parameter Changes...........................................................................3-1

3.1.3 Alarm Changes....................................................................................................................3-1

3.1.4 Performance Counter Changes...........................................................................................3-1

3.1.5 License Changes.................................................................................................................3-1

3.2 Changes from V200R011C01SPC750 to V200R011C01SPC751................................................3-2

3.2.1 Feature Changes................................................................................................................. 3-2


3.2.3 Alarm Changes....................................................................................................................3-2


3.2.5 License Changes.................................................................................................................3-2


3.3.1 Feature Changes................................................................................................................. 3-2


3.3.3 Alarm Changes....................................................................................................................3-3


3.3.5 License Changes.................................................................................................................3-3


3.4.1 Feature Changes................................................................................................................. 3-3


3.4.3 Alarm Changes....................................................................................................................3-3


3.4.5 License Changes.................................................................................................................3-3



ContentsBTS3900-BTS3900A-BTS3900L-DBS3900 WCDMA

V200R011C01SPC752 Release Notes

3.5.1 Feature Changes................................................................................................................. 3-4


3.5.3 Alarm Changes....................................................................................................................3-4


3.5.5 License Changes.................................................................................................................3-4


3.6.1 Feature Changes................................................................................................................. 3-4


3.6.3 Alarm Changes....................................................................................................................3-7


3.6.5 License Changes.................................................................................................................3-7


3.7.1 Feature Changes................................................................................................................. 3-7


3.7.3 Alarm Changes....................................................................................................................3-7


3.7.5 License Changes.................................................................................................................3-7


3.8.1 Feature Changes................................................................................................................. 3-8


3.8.3 Alarm Changes....................................................................................................................3-8


3.8.5 License Changes.................................................................................................................3-8


3.9.1 Feature Changes................................................................................................................. 3-9


3.9.3 Alarm Changes....................................................................................................................3-9


3.9.5 License Changes.................................................................................................................3-9

3.10 Changes from V200R011C01SPC200 to V200R011C01SPC300..............................................3-9

3.10.1 Feature Changes...............................................................................................................3-9

3.10.2 MML Command and Parameter Changes.......................................................................3-10

3.10.3 Alarm Changes................................................................................................................3-10

3.10.4 Performance Counter Changes.......................................................................................3-10

3.10.5 License Changes.............................................................................................................3-10

3.11 Changes from V200R011C01SPC110 to V200R011C01SPC200............................................3-10

3.11.1 Feature Changes.............................................................................................................3-10

3.11.2 MML Command and Parameter Changes........................................................................3-10

3.11.3 Alarm Changes................................................................................................................3-10


3.11.5 License Changes.............................................................................................................3-10


viiiHuawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd.I


3.12.1 Feature Changes.............................................................................................................3-11

3.12.2 MML Command and Parameter Changes........................................................................3-11

3.12.3 Alarm Changes................................................................................................................3-11


3.12.5 License Changes.............................................................................................................3-11


3.13.1 Feature Changes.............................................................................................................3-11


3.13.3 Alarm Changes................................................................................................................3-12


3.13.5 License Changes.............................................................................................................3-12


3.14.1 Feature Changes.............................................................................................................3-12


3.14.3 Alarm Changes................................................................................................................3-12


3.14.5 License Changes.............................................................................................................3-12


3.15.1 Feature Changes.............................................................................................................3-13


3.15.3 Alarm Changes................................................................................................................3-13


3.15.5 License Changes.............................................................................................................3-13


3.16.1 Feature Changes.............................................................................................................3-13


3.16.3 Alarm Changes................................................................................................................3-14


3.16.5 License Changes.............................................................................................................3-14

3.17 Changes from V200R011C01 to V200R011C01SPC010.........................................................3-14

3.17.1 Feature Changes.............................................................................................................3-14


3.17.3 Alarm Changes................................................................................................................3-14


3.17.5 License Changes.............................................................................................................3-14

3.18 Changes from V200R011C00SPC200 to V200R011C01.........................................................3-15

3.18.1 Feature Changes.............................................................................................................3-15


3.18.3 Alarm Changes................................................................................................................3-18


3.18.5 License Changes.............................................................................................................3-19



ContentsBTS3900-BTS3900A-BTS3900L-DBS3900 WCDMA


3.19.1 Feature Changes.............................................................................................................3-19


3.19.3 Alarm Changes................................................................................................................3-20


3.19.5 License Changes.............................................................................................................3-21

3.20 Changes from V200R011C00 to V200R011C00SPC100.........................................................3-21

3.20.1 Feature Changes.............................................................................................................3-21


3.20.3 Alarm Changes................................................................................................................3-21


3.20.5 License Changes.............................................................................................................3-21

3.21 Changes from V200R010C01B053 to V200R011C00..............................................................3-22

3.21.1 Feature Changes.............................................................................................................3-22


3.21.3 Alarm Changes................................................................................................................3-34


3.21.5 License Changes.............................................................................................................3-34

3.22 Changes from V200R010B052 to V200R010C01B053............................................................3-34

3.22.1 Feature Changes.............................................................................................................3-34


3.22.3 Alarm Changes................................................................................................................3-35


3.22.5 License Changes.............................................................................................................3-35


3.23.1 Feature Changes.............................................................................................................3-35


3.23.3 Alarm Changes................................................................................................................3-35


3.23.5 License Changes.............................................................................................................3-35


3.24.1 Feature Changes.............................................................................................................3-36


3.24.3 Alarm Changes................................................................................................................3-36


3.24.5 License Changes.............................................................................................................3-37


3.25.1 Feature Changes.............................................................................................................3-37


3.25.3 Alarm Changes................................................................................................................3-40


3.25.5 License Changes.............................................................................................................3-40

3.26 Changes from V100R009C01B053 to V200R010C01B041.....................................................3-41

xHuawei Proprietary and Confidential



3.26.1 Feature Changes.............................................................................................................3-41


3.26.3 Alarm Changes................................................................................................................3-44


3.26.5 License Changes.............................................................................................................3-44

4 Solved Problems and Unsolved Problems................................................................4-14.1 Solved Problems.......................................................................................................................... 4-1

4.1.1 Improvements of V200R011C01SPC752 on V200R011C01 SPC751.................................4-1



4.1.4 Improvements of V200R011C01SPC740 on V200R011C01 SPC700...............................4-20



4.1.7 Improvements of V200R011C01SPC510 on V200R011C01SPC500................................4-59



4.1.10 Improvements of V200R011C01SPC300 on V200R011C01SPC200..............................4-69

4.1.11 Improvements of V200R011C01SPC200 on V200R011C01SPC110...............................4-70






4.1.17 Improvements of V200R011C01SPC010 on V200R011C01...........................................4-70

4.1.18 Improvements of V200R011C01 on V200R011C00SPC200...........................................4-71


4.1.20 Improvements of V200R011C00SPC100 on V200R011C00...........................................4-81

4.1.21 Improvements of V200R011C00 on V200R010C01B053................................................4-81

4.2 Unsolved Problems.................................................................................................................... 4-82

5 Precautions...................................................................................................................5-15.1 Precautions for BTS3900-BTS3900A-BTS3900L-DBS3900 WCDMA V200R011C01SPC752....5-1

6 Related Documents........................................................................................................6-1


BTS3900-BTS3900A-BTS3900L-DBS3900 WCDMAV200R011C01SPC752 Release Notes 6 Related Documents

1 Version Mapping

1.1 Product Version

Product Name Huawei BTS3900 WCDMA (hereinafter referred to as BTS3900)

Huawei BTS3900A WCDMA (hereinafter referred to as BTS3900A)

Huawei BTS3900L WCDMA (hereinafter referred to as BTS3900L)

Huawei DBS3900 WCDMA (hereinafter referred to as DBS3900)

Product Model BTS3900 WCDMA

BTS3900A WCDMA

DBS3900 WCDMA

BTS3900L WCDMA

Product Version V200R011C01SPC752

1.2 Software Versions

Software Type

Software Version Related Model

LMT NodeB V200R011C01SPC750 BTS3900-BTS3900A-BTS3900L-DBS3900

CME BPL BTS3900-BTS3900A-BTS3900L-DBS3900 WCDMA V200R011C01SPC700

BTS3900-BTS3900A-BTS3900L-DBS3900

Issue 01 (2011-11-15)Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd.1

4 Solved Problems and Unsolved ProblemsBTS3900-BTS3900A-BTS3900L-DBS3900 WCDMA


Software Type

Software Version Related Model

M2000 Mediation

iManagerM2000_NodeB3900WCDMA_2U_MATCH_ENG_V200R009C01SPC016

BTS3900-2U

iManagerM2000_NodeB3900AWCDMA_MATCH_ENG_V200R009C01SPC016

BTS3900A

iManagerM2000_NodeB3900LWCDMA_2U_MATCH_ENG_V200R009C01SPC016

BTS3900L

iManagerM2000_DBS3900WCDMA_2U_MATCH_ENG_V200R009C01SPC016

DBS3900-2U

1.3 Related Product Versions

Related Product

Version Remarks

RNC BSC6900V900R011C00SPC700 or later versions -

M2000 iManagerM2000V200R009C00SPC251 or later versions -

CME CME V200R009C00SPC240 or later versions -

NOTE

If the CME V200R009C02SPC240 is used, the CME component package BTS3900-BTS3900A-BTS3900L-DBS3900 WCDMA V200R011C01SPC700 must be installed. If the version is later than CME V200R009C02SPC240, the CME component package is not required.

2Huawei Proprietary and Confidential



2 Version Compatibility

2.1 Compatibility with Earlier Product VersionsThis version is compatible with all the history product versions.




3 Version Changes

3.1 Changes from V200R011C01SPC751 to V200R011C01SPC752

3.1.1 Feature Changes

New Features

None

Modified Features

None

Deleted Features

None

3.1.2 MML Command and Parameter ChangesNone

3.1.3 Alarm ChangesNone

3.1.4 Performance Counter ChangesNone

3.1.5 License ChangesNone







New Features

None

Modified Features

None

Deleted Features

None







New Features

None

Modified Features

None

Deleted Features

None










New Features

None

Modified Features

None

Deleted Features

None











New Features

None

Modified Features

None

Deleted Features

None

3.5.2 MML Command and Parameter ChangesFor details on MML command and parameter changes, see Appendix 1.






New Features

None




Modified Features

1. 2×2 MIMO

Description The primary and secondary pilot networking modes of the MIMO cell are supported since this version.

From this version, the Virtual Antenna Mapping (VAM) function is supported.

Improvement When the cell is configured in STTD mode, HSDPA services are adversely affected. Therefore, MIMO and HSDPA cannot co-exist in one cell. The problem can be resolved by adopting the primary and secondary pilot networking modes, and the VAM function enables balance of output power between two Power Amplifiers (PAs).

Implementation

In the primary and secondary pilot network, the secondary pilot dynamic switch is implemented to reduce the interference of the secondary pilot on the R99 and HSDPA services. In this way, the TX of the secondary pilot is automatically disabled when there are no MIMO users in the cell and automatically enabled when there are MIMO users in the cell.

The main and diversity signals output by the baseband are mapped to the two PAs respectively by using the virtual orthogonal matrix switch mode. In this way, each PA has the main and diversity signals, thus achieving balance in output power of the two PAs. In addition, an alpha multiplying factor is introduced to the baseband diversity output. The alpha factor can be timely adjusted according to the current network user distribution. Therefore, the interference of MIMO users on HSDPA users can be reduced.

Related Operation

None

PR Number OR-NB-MKT-01.1308

Feature ID WRFD-010684

2. Scheduling based on EPF and GBR is optimized.

Description GBR services of 1 Mbit/s or higher data rates are guaranteed, if sufficient radio resources and Iub-interface resources are available.

Improvement UEs can use the GBR services of 1 Mbit/s or higher data rates.

Implementation

In scheduling for HSDPA services, resources are preferentially allocated to UEs whose the GBR requirements are not met, rather than UEs that have no GBR requirements or UEs whose GBR requirements are already met.

Related Operation

No more operations compared with the related operations of the feature Scheduling based on EPF and GBR.

PR Number CMM: SYED67687, SYED67697

Feature ID WRFD-01061103





3. Performance counters related to HSPA flow control are added for evaluation of the HSPA flow control algorithm.

Description Performance counters related to the HSPA flow control algorithm are added to the NodeB. They are used to evaluate the HSPA flow control algorithm.

Improvement After the performance counters related to flow control are added, the HSPA flow control algorithm can be better evaluated.

Note: For the NodeB of the current version, performance counters related to flow control are defined on the northbound interface. These performance counters will be reported in later NodeB versions. The purpose is to prevent modification on the northbound interface and upgrade in mediation software in later NodeB versions.

Implementation

Performance counters related to flow control are added.

Related Operation

Same as the related operations for traffic statistics.

PR Number CMM: SYED68974, SYED68975, SYED68976, SYED68977

Feature ID WRFD-010637, WRFD-01061010

Deleted Features

None


3.6.3 Alarm ChangesFor details on alarm changes, see Appendix 2.








New Features

None

Modified Features

None

Deleted Features

None











New Features

1. New baseband board WBBPd3

Description A new baseband board WBBPd3 is introduced. The WBBPd3 supports the same features as the WBBPd2 but has a different capacity specification from the WBBPd2. One WBBPd3 supports 256 CEs in the uplink, 256 CEs in the downlink, and six cells.

Improvement The capacity configuration of the NodeB becomes more flexible.

Implementation

A new hardware type of baseband board is added.

Related Operation

All hardware installation and OM operations related to the WBBPd are applicable to the WBBPd3.

PR Number CMM: SYED68863

Function ID None

Modified Features

None

Deleted Features

None



3.8.4 Performance Counter ChangesFor details on performance counter changes, see Appendix 3.

3.8.5 License ChangesFor details on license changes, see Appendix 4.






New Features

None

Modified Features

None

Deleted Features

None







New Features

None

Modified Features

None

Deleted Features

None











New Features

None

Modified Features

None

Deleted Features

None










New Features

None

Modified Features

None

Deleted Features

None







New Features

None

Modified Features

None

Deleted Features

None











New Features

None

Modified Features

None

Deleted Features

None










New Features

None

Modified Features

None

Deleted Features

None







New Features

None

Modified Features

None

Deleted Features

None









3.17 Changes from V200R011C01 to V200R011C01SPC010


New Features

None

Modified Features

None

Deleted Features

None








3.18 Changes from V200R011C00SPC200 to V200R011C01


New Features

1. Single IP address for the NodeB

Description The IP addresses of the NodeB consist of the control plane IP address, user plane IP address, and NodeB OM IP address. Currently, typical application is that the control plane IP address and user plane IP address are configured to use the same port IP address. The OM IP address and user plane IP address should be assigned with two different IP addresses belonging to different IP subnets. Therefore, operators need to plan two sets of IP addresses and routing rules during network deployment. With the introduction of single IP address for the NodeB, the traffic channel and OM channel are enabled to share one IP address.

Improvement With the introduction of single IP address for the NodeB, the traffic channel and OM channel are enabled to share one IP address. In this way, more IP address resources are saved and IP route configuration is simplified when IP transport is adopted.

Implementation

When a BTS3900/BTS3900A/DBS3900 is configured with one WMPT and the WMPT provides one or more IP ports, the OM IP address can be the same as one of the port IP addresses. When using redundancy configuration for OM channels, the two OM IP addresses can be the same as those of the two ports provided by the WMPT.

When a BTS3900/BTS3900A/DBS3900 is configured with one WMPT and multiple UTRPs and the WMPT or UTRP provides one or more IP ports, the OM IP address of the NodeB can be the same as one of the port IP addresses. When using redundancy configuration for OM channels, the two OM IP addresses can be the same as those of the two IP ports provided by the WMPT. The two OM IP addresses are not allowed to be the same as those of two IP ports provided by the UTRP.

A BTS3900/BTS3900A/DBS3900 is configured with multiple ports (E1/T1/Ethernet), and the ports can be combined as one IP interface through Ethernet Trunk and MLPPP. If the IP port is located on the WMPT, the OM IP address can be the same as that of the combined IP port.

Related Operation

The ADD DEVIP command is used to configure the same IP address for the service channel and OM channel.


Function ID WRFD-021404





2. Management and monitoring of the solar equipment

Description The solar power system supplies the power produced by solar array to the load. The surplus power is stored in the batteries. The solar power system runs under the control of the solar controller.

Improvement This feature improves the operability and maintainability of the NodeB and solar equipment, which enables a much greener NodeB.

Implementation

The solar controller, like the traditional power monitoring device, is managed as the PMU. The configuration, maintenance, and status monitoring of the solar controller are performed through the 485 serial port by the NodeB.

Related Operation

The ADD PMU command is used to add the solar controller to the NodeB configurations. The commands for the PMU are used to configure and maintain the solar controller.



Modified Features

1. Compliance with the 3GPP R8 protocol

Description The 3GPP protocol is upgraded to the R8 protocol released in March, 2009.

Improvement None

Implementation

The 3GPP R8 protocol released in March, 2009 is supported.

Related Operation

None






2. NodeB software management

Description The OM channel carries high-priority services such as MML command operations and transmission of clock synchronization messages, as well as low-priority services such as file uploading and downloading of background services. The OM messages of different priorities identify different DSCP values and VLAN COS priorities. This avoids low-priority services occupying large service bandwidth and impact on the high-priority OM messages and services and ensures priority guarantee in end-to-end transmission.

Improvement The OM messages are differentiated by priorities. That is, messages of different priorities identify different DSCP values and VLAN COS priorities. This ensures priority guarantee in end-to-end transmission in L2 Ethernet or L3 IP route networking.

Implementation

The OM messages of different priorities are configured with the corresponding DSCP and VLAN COS fields. This ensures that OM messages of high priority take the precedence in transmission. In addition, in the case of limited bandwidth, OM messages of low priority do not affect the provision of messages and services of high priority.

Related Operation

The SET DIFPRI command is used to set the corresponding DSCP values for the OM messages of different priorities.

The SET VLANCLASS command is used to set the corresponding VLAN COS values for the OM messages of different priorities.







3. Intelligent shutdown

Description If the AC mains for the NodeB with the power backup system fails, intelligent shutdown of the cell, RF module, and NodeB can be enabled. The intelligent shutdown is implemented through powering off the cell, RF module, and the entire NodeB level by level. Users can set different DC voltage thresholds and NodeB and cell shutdown priorities. The intelligent shutdown of the NodeB and RF module is supported from RAN5.0. The intelligent shutdown of cells is available from this version.

Improvement The intelligent shutdown function saves the investment for battery backup system and meets customers’ requirements for energy saving and power consumption. The function is particularly beneficial to the NodeB which is a transmission center node. In this case, separate power backup systems for the NodeB and transmission equipment are not required. Longer duration of power supply is implemented through setting different shutdown thresholds.

Implementation

The NodeB supports setting priorities for shutting down cells. The cells are shut down in turn according to their priorities, thus extending power supply duration. After the mains power of the NodeB is shut down, batteries start supplying power. When the battery voltage decreases to a certain threshold, the NodeB enables the intelligent shutdown of cells to shut down the TRX of non-reserved cells. If the battery voltage keeps decreasing to another threshold, the NodeB shuts down the TRX of all the cells. If the battery voltage resumes to a certain threshold, the NodeB automatically open up all the cells whose TRX was shut down.

Related Operation

The SET ITELSHUTDOWN command is used to enable or disable the intelligent shutdown function.

The ADD LOCELL command is used to configure local cells as reserved cells.

PR Number OR-MM-MKT-01.0244


Deleted Features

None










1. 2 × 2 MIMO

Description 2 x 2 Multiple Input Multiple Output (MIMO) uses two transmit antennas at the NodeB to transmit orthogonal (parallel) data streams to the two receive antennas at the UEs.

Improvement Using two antennas and additional signal processing at the receiver and the transmitter, 2 x 2 MIMO can increase the system capacity and double user data rates without using additional bandwidth. 2 x 2 MIMO adopts different modes in the 3GPP protocols, with QPSK and 16QAM in R7, and later with 64QAM in R8. With dual-stream dual-antenna mode and16QAM modulation, the peak data rate per user is doubled to 28 Mbit/s and also the average throughput of the system is enhanced.

Implementation The 3GPP R7 protocols define the categories of the UEs that support MIMO, and add the information elements (IEs) that support MIMO in the reporting of local cell capability. The RNC determines whether the RL between the NodeB and the UE supports MIMO according to the local cell capability and UE capability reported by the NodeB. If the RL supports MIMO, the MAC-hs scheduler of the NodeB determines every 2 ms whether to use MIMO according to the following aspects: Channel Quality Indicator (CQI) reported by the UE Precoding Control Indication (PCI) HS-PDSCH code resources and power resources of the

NodeB

Related Operation

This function is controlled through a license. The function is available only when the operator purchases the license from Huawei.







2. HSUPA Adaptive Retransmission

Description With comprehensive considerations of cell uplink power load, CE resources, and limited uplink coverage, this feature enables the adaptive adjustment of the number of target uplink retransmissions to improve the throughput per user and cell uplink capacity.

Improvement In a limited uplink coverage scenario, a user’s uplink cell edge throughput can be increased, in order to enhance user experience. According to simulation results, single user throughput has been show to increase by 15%-60%.

In a scenario where the cell uplink power load is limited, increasing the retransmission number can improve cell throughput and cell uplink capacity. Simulation results have shown an increase of 53% in cell throughput under multi-user scenarios.

Implementation This feature is only effective in BE traffic. If a user, only has BE traffic (with the exception of SRB) on E-DCH, then dynamic adjustment of the target retransmission number is allowed. Adjusting the users target retransmission number to a relatively smaller value is permitted when the uplink power of all the cells belonging to the serving RLS is smaller than a certain threshold and the UE uplink power is not limited and/or uplink CE’s are limited. When the uplink power of any cell belonging to the serving RLS experiences congestion or UE’s uplink power is limited, then setting the users target retransmission number to a relatively larger value is permitted, as long as the uplink CE resources are sufficient.

Related Operation

This function can be enabled or disabled by SET ADPRETRANSSWTCH.

PR Number CR-PRD-156


Modified Features

None

Deleted Features

None








3.20 Changes from V200R011C00 to V200R011C00SPC100


New Features

None

Modified Features

None

Deleted Features

None









3.21 Changes from V200R010C01B053 to V200R011C00


New Features

1. Link Aggregation

Description The FE/GE interface board (UTRP2, UTRP9) is added from this issue. The Link aggregation enables teaming of two FE/GE ports which are on the same board. In this way, the two teamed FE/GE ports are regarded as one port in transmitting and receiving data.

Improvement The teaming of two FE/GE ports can improve the reliability: The trunk group which has all its links teamed can keep working properly in the case of a faulty FE/GE port. Moreover, the bandwidth can increase: The bandwidth of the trunk group which has all its links teamed is two times the bandwidth of the original FE/GE ports.

Implementation To allow teaming of two FE/GE ports on the same board, ensure that the two FE/GE ports are consistent in bandwidth as well as in mode (teaming of one FE/GE optical port and one FE/GE electrical port not allowed). The load sharing among links during data transmission are implemented based on the quaternion.

Related Operation

Use ADD ETHTRK command to add FE/GE port into a trunk group.

PR Number OR-TR-TRP-50.0033





2. Ethernet OAM

Description In compliance with the 802.3ah and 802.1ag protocols, the NodeB can manage and maintain the Ethernet links.

Improvement The NodeB can manage and maintain the Ethernet links. When an Ethernet link is faulty, the NodeB supports route switchover, enables users to ping the MAC address of layer 2, and collects the performance statistics through the management and maintenance of the Ethernet links.

Implementation The NodeB supports the loopback process described in the 802.3ah protocol and loopback and search processes described in the 802.1ag protocol.

Related Operation

Use ADD CFMMEP command to add maintenance endpoint.

PR Number OR-TR-OAM-07.0058


3. Downlink Enhanced L2

Description Before the Downlink Enhanced L2 is introduced, the NodeB supports only the RLC PDU with a fixed size. After the Downlink Enhanced L2 is introduced, the NodeB supports the RLC PDU with a flexible size and segmentation and reassembling of the data blocks on the MAC layer based on the capability over the air interface. In this way, the data transmission rate and service coverage are improved.

Improvement The HSDPA data transmission rate is increased. The downlink coverage of the HSDPA cell is enhanced.

Implementation The NodeB supports the reception and processing of the FP data frames in HS-DSCH data frame type 2 format.

The NodeB supports enhanced MAC-ehs function and enables the reassembling and segmentation of the data blocks on the MAC layer based on the capability over the air interface.

Related Operation

None







4. Uplink Macro Diversity Intelligent Receiving

Description The macro diversity has a small gain for the high speed non-real-time services and occupies much transmission bandwidth on the Iub interface. Therefore, the Uplink Macro Diversity Intelligent Receiving is introduced in R7 protocol. For the non-service links, the MAC-d flow of the service can be provided with an option of not establishing the transmission bearing.

Improvement The transmission bandwidth resources on the Iub interface are saved.

The resource usage is improved. The performance of the network is optimized.

Implementation If the Transport Bearer Not Requested Indicator IE is not included for a certain MAC-d flow, the NodeB performs the radio link setup procedure in a usual way.

If the Transport Bearer Not Requested Indicator IE is included for a certain MAC-d flow, and the value of the IE is set to Transport Bearer shall not be Established, the NodeB does not allocate the transmission resources for the MAC-d flow.

If the Transport Bearer Not Requested Indicator IE is included for a certain MAC-d flow, and the value of the cell is set to Transport Bearer may not be Established, the NodeB decides whether to allocate the transmission resources for the MAC-d based on the sufficiency of the current bandwidth resources.

Related Operation

None






5. Energy Efficiency Improved

Description The NodeB supports Energy Efficiency Improved, which enables dynamic adjustment of the PA parameters based on the actual load of the current PA. This prevents the PA from working at a level with the maximum load and saves the energy consumption of the equipment.

Improvement The energy usage is improved. The pollution to the environment is reduced.

Implementation The PA detects the current output power in real time and provides a set of suitable parameters to minimize the energy consumption.

Related Operation




6. Dynamic Power Sharing of Multi-Carriers

Description In multi-carriers mode, the carrier bearing the HSDPA services can dynamically share the power unused by another carrier. In this way, the power usage of the PA and HSDPA service rate can be improved.

Improvement The performance of the network and usage of the existing network devices is improved.

According to the emulation results, the capacity of the HSDPA cell is improved by 5% to 6% in two-carrier dynamic sharing mode.

Implementation Two-carrier power sharing is supported in RAN11.0. If there are an R99 carrier and an HSDPA carrier, the R99 carrier periodically sends the current excessive power for sharing to the HSDPA carrier according to the UE configuration and load of the current services. In this case, the HSDPA carrier uses the excessive power shared by the R99 carrier based on the original power allocation when performing the HSDPA service scheduling.

Related Operation


Before using the power sharing, the operator must run the ADD PAGRP command to add the power sharing group.







7. Synchronous Ethernet

Description The synchronous Ethernet technology that adopts Ethernet link code flows to recover clocks is a physical layer based clock synchronization.

Improvement The synchronous Ethernet technology is one of the key features in the solution for network over all IP solution. It is an economical, convenient solution.

Implementation A highly precise clock is used by the Ethernet physical layer (PHY) for data transmission. The receiving end extracts and recovers the clock from data stream, and the high precision can be maintained.

Related Operation

Use SET ETHPORT command to set the FE port whether be used by the Synchronous Ethernet for clock transmission or receipt.

Use SET CLKMODE command to set the Synchronous Ethernet to be the reference clock source for NodeB.

PR Number OR-TR-OTH-99.0042





8. Downlink 64QAM

Description 3GPP R5 introduces 16QAM to increase the peak rate per user and expands the system capacity, whereas 64QAM introduced in 3GPP R7 protocols is a further enhancement of 16QAM.

Improvement Downlink 64QAM increases the peak rate per user and improves the local cell capability.

If the bandwidth remains unchanged, 64QAM will increase the average throughput of the system by 7% to 16% and further improves the spectral efficiency of the system. In this way, the system provides users with higher throughput and ultimately increases operators' profits on the per bandwidth basis.

On the other hand, 64QAM also raises the peak rate per user and provides a higher download data rate for users. This not only improves user experience but also enhances operators' competitiveness.

Implementation The 3GPP R7 protocols define the categories of the UEs that support 64QAM, and add the information elements (IEs) that support 64QAM in the reporting of local cell capability. The RNC determines whether the RL between the NodeB and the UE supports 64QAM according to the local cell capability reported by the NodeB and the UE capability. If the RL supports 64QAM, the MAC-hs scheduler of the NodeB determines every 2 ms whether to use 64QAM according to the following aspects: Channel Quality Indicator (CQI) reported by the UE HS-PDSCH code resources and power resources of the

NodeB

Related Operation

None







9. Improved CE Mapping for E-DCH

Description With the 3900 NodeB WBBPb hardware it is possible to improve efficient Channel Element (CE) mapping for Enhanced Uplink users.

Improvement Improve the CE efficiency, decrease the configured CEs.

Implementation The Channel Element usage, in relation to Spreading Factor (SF), for ladder E and the previous ladders is noted in the table below.

Spreading Factor Former CE Mapping

Improved CE Mapping

SF64 1 1

SF32 1.5 1

SF16 3 2

SF8 5 4

SF4 10 8

2SF4 20 16

2SF2 32 32

2SF2+2SF4 48 48

Related Operation

None

PR Number CR-SEG-367





10. RRU Redundancy

Description In some rural area with adverse environment, the RRU maintains is very inconvenient. RRU redundancy provides the receiver and transmitter backup solution.

Improvement This feature improves the reliability and robustness of RAN and shortens the time of service interruption due to RRU failure. Thus, the quality of service is improved.

Implementation For non-transmit diversity cell, when active RRU is failure, the cells on the active RRU will block, and re-allocated to the standby RRU.

For transmit diversity or MIMO cell, when one transmit path of RRU failure, the cells on the RRU will re-setup with NON-transmit diversity or NON-MIMO mode. Meanwhile Node B will keep the same transmitter power as far as possible. The cell will attempt to switch on the cell with transmit diversity or MIMO mode until the transmit path fault is cleared.

The cell re-setup will bring service interruption, interruption time of less than 30s.

Related Operation

For RRU redundancy, two RRU should be configured by ADD LOCELL and ADD SECTOR.

PR Number CR-PRD-145


Modified Features

1. 3GPP R7 Protocol

Description The protocol version is updated to 3GPP R7 Protocol released in March, 2008.

Improvement None

Implementation The NodeB supports the 3GPP R7 Protocol released in March, 2008. It is recommended that the RNC connected to the NodeB be upgraded to support the same protocol version.

Related Operation

None







2. F5

Description Passive receiving of and response to F5 PM IEs are supported.

Improvement The NodeB can work with the RNC to enable F5 PM so that the RX and TX traffic and the status of a single PVC can be taken statistics on.

Implementation Passive receiving of and response to F5 PM IEs are supported. After the NodeB receives the PM IEs sent actively by the RNC, it fills the number of received IEs in the response IE and then sends this IE to the RNC.

Related Operation

None

PR Number OR-TR-OAM-07.0053


3. Flow Control

Description The HSUPA flow control algorithm is optimized. When the bandwidth on the Iub interface is limited, the equity and differentiation of the UE is further improved.

Improvement The equity and differentiation of the UE is improved when the bandwidth on the Iub interface is limited.

The Iub bandwidth efficiency is improved.

Implementation The NodeB performs the flow control on the transmission of the uplink data of the non-real-time services. When the bandwidth on the Iub interface is not congested, the received data is immediately sent. When the bandwidth on the Iub interface is congested, the NodeB adjusts the transmission rate for the uplink data of the UE based on the congestion status. The data that is not yet sent is temporarily saved in the NodeB. When the saved data of the UE reaches a threshold, the NodeB notifies the UE to decrease the service rate through the MAC-e scheduling.

Related Operation

None






4. HSUPA HARQ and Fast UL Scheduling in Node B

Description In RAN11.0, the optimization of the MAC-e scheduling algorithm is combined with the flow control algorithm.

Improvement The MAC-e scheduling algorithm combines with the flow control algorithm, further improving the bandwidth efficiency of each UE.

Implementation The flow control algorithm determines the basic rate and authorization indication for each UE according to the buffer status of each UE and the congestion indication returned by the RNC. The MAC-e scheduling algorithm performs the scheduling based on the basic rate and authorization indication.

Related Operation

None



5. FP MUX for IP Transmission

Description The FP MUX is the technology of the FP multiplexing. It collects multiple FP packets into a UDP packet for transmission.

Improvement If the FP packet is short, multiple FP packets can be collected into a UDP packet for transmission. This reduces the overhead of UDP headers, improves the transmission bandwidth usage, and requires less bandwidth.

Implementation The sender collects multiple FP packets on a specified UDP port for transmission, and the receiver resolves the FP packets from the multiplexed packet.

Related Operation

None

PR Number OR-TR-TRP-50.0015






6. Dynamic CE Resource Management

Description The dynamic CE resource management algorithm is optimized, shortening the adjustment period.

Improvement The period of the allocation and collection of the CE resources is shortened, and the CE resource efficiency is improved.

Implementation The dynamic CE resource management algorithm on the WBBPb board is improved. Each TTI performs allocation and collection of the CE resources of the UE.

Related Operation

None



7. Clock Synchronization on Ethernet in NodeB

Description The NodeB supports clock synchronization based on the 1588v2 protocol. The clock accuracy of this synchronization mode meets the requirements of the NodeB. At present, the NodeB supports the OC function. That is, the clock is obtained from the lines rather than provided for downstream equipment through the lines.

Improvement The clock is obtained based on the 1588v2 protocol, without the help of an external GPS clock, which reduces network construction cost.

The 1588v2 is a standard protocol, which can be supported by network equipment through upgrade in future. In this case, operators are required to have only the clock server instead of installing new equipment.

Implementation For the clock synchronization based on the 1588v2 protocol, the clock server regularly sends clock synchronization messages to the NodeB. After receiving the messages, the NodeB performs actions such de-jittering. Then, the clock is locked and acts as the reference clock source of the NodeB.

Related Operation

Run the ADD IPCLKLNK command to add clock links.

Run the SET CLKMODE command to set the reference clock source of the NodeB.

PR Number OR-TR-OTH-99.0042


Deleted Features

None








3.22 Changes from V200R010B052 to V200R010C01B053


New Features

1. Asymmetrical Power Configuration

Description of the Feature

Asymmetrical power configuration

Effect of Improvement

Asymmetrical configuration such as 20 W/40 W or 30 W/30 W for a 60 W RRU is supported.

Only the RRU3804 and WRFU support this function.

Implementation Modify the CFR algorithm. Modify the ALC level of the digital IF channel.

Related Operations

None

PR Number CR-NRF-029

Function ID None

Modified Features

None

Deleted Features

None











New Features

None

Modified Features

None

Deleted Features

None










New Features

None

Modified Features

1. Optimization for the Dynamic CE Resource Management

Description Optimization for the Dynamic CE Resource Management

Improvement 1. In the scenario of lack of CE resources, when processing CE resources among serving RLS for fairness, if RG Down is changed to AG Down, CE utilization rate can be improved greatly, also throughput can be increased about 22 percent.

2. If the lower limit of call back CE resources of serving RLS is changed to one RLC PDU, the waste due to call back CE resources of serving RLS to GBR can be decreased during no UL data to be transferred.

Implementation 1. Modify the method of decreasing a user's rate from RG Down to AG Down when processing CE resources among serving RLS for fairness.

2. Modify the lowered limit of call back CE resources of serving RLS to one RLC PDU.

Related Operation

None

PR Number CR-RPD-134


Deleted Features

None











New Features

1. SRB over HSDPA

Description From this release on, the F-DPCH is supported.

Improvement The F-DPCH carries only TPC bits. The application of F-DPCH helps decrease the power and code usage in the downlink. The F-DPCH is mainly applied to the service of SRB over HSDPA, such as VoIP.

Implementation Install the WBBPb, which supports the F-DPCH.

Related Operation

None

PR Number OR-MKT-011701


2. SRB over HSUPA

Description From this release on, the SRB over HSUPA feature is supported.

Improvement This feature helps achieve a higher signaling rate and reduce the call processing delay. Since the SRB is carried on HSUPA, the transmission resources can be saved compared with those for the SRB carried on the DCH.

Implementation Install the WBBPb, which supports the SRB over HSUPA feature.

Related Operation

None






3. HSUPA Phase 2

Description From this release on, the HSUPA Phase 2 is supported. The features in HSUPA Phase 2 include HSUPA E-AGCH power control (based on CQI or HS-SCCH), enhanced fast UL scheduling in the NodeB, HSUPA 2 ms TTI, HSUPA 2 ms/10 ms TTI handover, and HSUPA 5.74 Mbps per user.

Improvement HSUPA Phase 2 helps improve the performance of UMTS network by providing a higher rate and higher throughput for the uplink and providing higher capacity for the system.

Implementation Install the WBBPb, which supports HSUAP Phase 2.

Related Operation

MOD BRD

MOD DLGROUP

MOD ULGROUP



4. Dynamic CE Resource Management

Description From this release on, the dynamic CE resource management is supported.

Improvement The dynamic CE allocation can retrieve the CE resources promptly when the throughput of users decreases, thus saving the CE resources.

Implementation The NodeB retrieves the CE resources if the throughput of users decreases, allocates the CE resources during the radio link setup or reconfiguration, allocates the CE resources for the Absolute Grant (AG) UP users, and pre-empts the CE resources for the Relative Grant (RG) UP users.

Related Operation

None







5. Common Channel Parallel Interference Cancellation

Description From this release on, the Common Channel Parallel Interference Cancellation (CCPIC) is supported.

Improvement CCPIC is a simplified and practical application of MUD technology for base station receivers. It cancels the uplink control channel and thus decreases the uplink interference and improves the performance.

In the scenario of an urban macro cell, TU3 channel, and AMR 12.2 kbps user with a 50% load, the CCPIC will bring 11% capacity improvement; in the case of a 75% load, the capacity improvement is 18%.

Implementation The control channels are always active and they are a substantial sources of interference especially to those lower-data-rate and lower-activity services before 3GPP R7.

Because there are known slot formats of different users, the DPCCH pilot symbols of all users are clear to the receiver. With a high spreading factor, the TPC, TFCI, or FBI bits can be judged accurately. The demodulation performance of one user can be improved when the DPCCH signals received from the other users are reconstructed and canceled.

Related Operation

None



6. HS-DPCCH Preamble

Description From this release on, the HS-DPCCH preamble is supported.

Improvement The HS-DPCCH preamble mode enables the NodeB to distinguish between DTX and ACK/NACK without requiring high ACK transmit power.

The uplink coverage gain is about 0.2 dB to 0.9 dB for different associated DPCCH services.

Implementation Install the WBBPb, which supports the HS-DPCCH preamble.

Related Operation

None






Modified Features

1. Physical Channel Management

Description From this release on, the F-DPCH is supported.

Improvement The F-DPCH carries only TPC bits. The application of F-DPCH helps decrease the power and code usage in the downlink. The F-DPCH is mainly applied to the service of SRB over HSDPA, such as VoIP.

Implementation Install the WBBPb, which supports the F-DPCH.

Related Operation

None



Deleted Features

None









3.26 Changes from V100R009C01B053 to V200R010C01B041


New Features

1. System Improvement in the RAN10.0

Description The UMTS RAN10.0 introduces the new NodeB product portfolio (Uni BTS) that is based on the new hardware platform.

Improvement The Uni BTS is a multi-mode base station. Based on leading technologies of convergent platform, modular design and common CPRI interface, different-mode modules plugged in the same cabinet can support different mode, and different-mode modules can be inserted into the same cabinet to support dual mode. In addition, the open and universal architecture facilitates smooth evolution.

Implementation Developed based on a new hardware platform, the Uni BTS has improved architecture, high availability, low power consumption, and improved radio performance. Meanwhile the Uni BTS comes with new configurations, new output power options, and increased baseband capacity.

The Uni BTS consists of two physically separate parts: BB module (BBU3900) and RF module (WRFU or RRU3804). The two parts can be connected through electrical or optical cables on the CPRI interface. This facilitates site acquisition, device transportation, equipment room construction, and equipment installation.

Related Operation

None

PR Number 200705082360





Modified Features

1. 3GPP R6 Specifications

Description The protocol version is upgraded to the R6 issued in the March, 2007.

Improvement None

Implementation The R6 issued in the March, 2007 is used. It is recommended that the protocol that the RNC uses be upgraded to the same version.

Related Operation None

PR Number 200705082406


2. Fault Management

Description This feature supports the trace of UDP/SCTP packet contents.

Improvement The UDP/SCTP packet contents can be monitored during the maintenance operation. All data of a specific user or every user on the Iub interface can be monitored, thus facilitating analysis.

Implementation Three trace types can be used: tracing specific source and destination IP addresses/ tracing specific source and destination IP addresses and protocol types/ tracing specific source and destination IP addresses and specific UDP ports.

The NodeB can record the selected IP packets, and transfer the packet contents to the LMT.

Related Operation None

PR Number 200705082393






3. Security Management

Description The user authorization and management mechanism are provided to enhance the network security management.

Improvement None

Implementation Security Socket Layer (SSL) for data communication between the RAN and the OMC is supported. Therefore, all the remote maintenance communications are encrypted.

Related Operation

SET CERTFILE: Set the certificate file.

SET SSLAUTHMODE: Set the SSL authorization mode.

LST SSLCONF: List SSL configurations.

DSP SSLCPB: Display TLS/SSL capability.

PR Number 200612220283


4. HSDPA H-ARQ & Scheduling

Description The compressed-mode tracing is supported during scheduling.

Improvement If a TTI is overlapped with a UE’s compressed mode gap, this UE shall not be scheduled in this TTI. This feature can improve the air interface utilization ratio and cell throughput.

Implementation During the MAC-hs scheduling period in a TTI, the NodeB checks whether the UE receives the HSDPA data in a downlink compressed mode gap and whether the UE sends ACK/NACK messages in an uplink compressed mode gap. In either of the two cases, this UE shall not be scheduled in this TTI.

Related Operation

None

PR Number 200705082409





5. ATM/IP Dual-Stack NodeB

Description The secondary path type configuration can be used as mutual backup of transmission resources, especially in ATM and IP hybrid transmission solutions. That is, when IP transmission fails, the service can be mapped onto the secondary ATM path type to keep the services available or vice verse.

Improvement The reliability of the NodeB is improved.

Implementation If the user sets the signaling links to the backup mode, the NodeB receives data from all links and gives hand-shake response to the RNC. If the active link is failed, the RNC sends the switchover request to the NodeB. If the NodeB receives this request, the standby link changes to active, and the signaling will be sent on this link.

If the user sets the OM links to the backup mode, two independent OM links are established. These links work simultaneously and the M2000 decides to use which link and when to switch over.

Related Operation

None

PR Number 200705082368/200705082367


Deleted Features

None








4 Solved Problems and Unsolved

Problems

4.1 Solved Problems

4.1.1 Improvements of V200R011C01SPC752 on V200R011C01 SPC751

1. Results of SRRU/WRFU VSWR offline tests are inaccurate occasionally.

Description

Results of SRRU/WRFU VSWR offline tests are inaccurate occasionally.

Cause The procedure for VSWR offline tests is defective.

Impact VSWR values are incorrect in the VSWR offline test results.

Severity Minor

Solution The procedure for VSWR offline tests has been corrected.

PR Number iCare: 301545

DTS: DTS2011071904676

Test Case ID

ATP-2011071904676





2. The SRRU/WRFU upgrade fails occasionally.

Description

During the upgrade of the NodeB or SRRU/WRFU, the SRRU/WRFU fails to be upgraded occasionally.

Cause Oversized SRRU/WRFU log files occupy too much flash memory of the SRRU/WRFU.

Impact The SRRU/WRFU cannot be upgraded.

Severity Major

Solution The mechanism for managing SRRU/WRFU logs has been corrected to prevent oversized log files.

PR Number DTS: DTS2011082904052

Test Case ID

ATP-2011082904052

3. Services on the SRRU/WRFU are interrupted occasionally.

Description The alarm ALM-26538 RF Unit Clock Problem is occasionally reported for the SRRU/WRFU, and consequently the alarm ALM-28203 Local Cell Unusable is reported for the cells carried on the SRRU/WRFU. Then, services on the SRRU/WRFU are interrupted.

Cause The SRRU/WRFU internal clock has a weak drive capability, resulting in poor clock signal quality.

Impact Cell services are unavailable.

Severity Major

Solution The drive capability of the SRRU/WRFU internal clock has been enhanced to improve clock signal quality.


Test Case ID ATP-2011061605679




4. Maintenance link abnormal

Description On rare occasions, the NodeB with an extremely high traffic volume resets unexpectedly.

Cause The task scheduling mechanism is defective when a large number of UEs access the network simultaneously. As a result, the TICK task is incorrectly scheduled on rare occasions.

Impact Services are interrupted.

Severity Major

Solution The task scheduling mechanism has been corrected.




1. The M2000 fails to distribute a commercial license file to a multi-mode base station configured with a multi-mode RRU.

Description The M2000 fails to distribute a commercial license file to a multi-mode base station configured with a multi-mode RRU. An error message is displayed, indicating that the value of the Multi-Mode BTS control item is incorrect.

Cause The mechanism for processing license files is defective. As an effect of this, the Multi-Mode BTS control item is incorrectly processed if the multi-mode base station is configured with a multi-mode RRU.

Impact The M2000 fails to distribute a commercial license file to a multi-mode base station configured with a multi-mode RRU.

Severity Minor

Solution The defective mechanism for processing license files is corrected so that the Multi-Mode BTS control item can be correctly processed.








1. An ALM-26262 External Clock Reference Problem is reported when it should not be.

Description When the NodeB inventory management data is synchronized on the M2000 and the data volume is large (because of a large number of configured boards), an ALM-26262 External Clock Reference Problem is reported when it should not be. The alarm is automatically cleared after the data synchronization ends.

Cause The mechanism for detecting the alarm is defective. If the volume of NodeB inventory management data is large, alarm detection is delayed.

Impact The reported alarm can be automatically cleared and has no impact on services.

Severity Minor

Solution The defective mechanism for detecting the alarm is corrected so that the alarm can be reported correctly.

PR Number GCRMS: 5026320

DTS: DTS2011021603107


2. The fan speed is inaccurately adjusted in a multi-mode base station.

Description If an RF unit is faulty or is not configured in a multi-mode base station, the fan speed is inaccurately adjusted. Therefore, the temperature of the base station may exceed the preset threshold.

Cause The mechanism for adjusting the fan speed is defective.

Impact The temperature of the base station may exceed the preset threshold.

Severity Minor

Solution The defective mechanism for adjusting the fan speed is corrected.






3. The ALD link setup may fail.

Description When the NodeB uses the antenna line device (ALD) of AISG2.0, the ALD link setup may fail.

Cause The mechanism for scanning the ALD is defective. After the ALD of AISG2.0 is reset, its baud rate will be periodically changed. In this case, there is a low possibility that the ALD scanning fails.

Impact The maintenance link of the ALD is disconnected, which does not affect services.

Severity Major

Solution The defective mechanism for scanning the ALD is corrected.

PR Number DTS:DTS2011011304793


4. Memory access is abnormal when a NodeB collects statistics on the transmission quality.

Description When a NodeB collects statistics on the transmission quality, heap corruption may occur and the data of other modules in the memory is modified.

Cause The amount of memory allocated to the module collecting statistics on the transmission quality is smaller than what is actually required. As a result, the module has to violate the memory allocated to other modules.

Impact The NodeB memory experiences problems.

Severity Major

Solution The amount of memory allocated to the module collecting statistics on the transmission quality is adjusted.







5. The ALM-25898 IP Path Excessive Packet Loss Rate persists even if the fault is rectified.

Description The ALM-25898 IP Path Excessive Packet Loss Rate persists after packet loss on the transport network is rectified.

Cause The IP PM detection algorithm is defective. In the case of packet loss over the transport network, there is a possibility that the IP PATH is mistakenly set to "no packet loss." As a result, the NodeB does not clear the ALM-25898 IP Path Excessive Packet Loss Rate after packet loss is rectified.

Impact A misleading false alarm is reported but does not affect the services.

Severity Minor

Solution The IP PM detection algorithm is modified.


DTS: DTS2010101904015


6. Transmission-related traffic statistics are repeatedly reported.

Description Transmission-related traffic statistics of a physical port are repeatedly reported.

Cause Duplicate traffic statistics of the same physical port fail to be recognized during reporting of the traffic statistics.

Impact The traffic statistics reported to the M2000 contain redundant data of the same physical port. The services, however, are not affected.

Severity Minor

Solution The mechanism for reporting the traffic statistics is optimized to clear the redundant data.


DTS: DTS2010081600851





7. There is an extremely low possibility that the call drop rate increases when the WBBPd is used.

Description In certain scenarios where the WBBPd is used, the call drop rate increases because the Digital Signal Processing (DSP) resource management scheme is defective.

Cause The DSP resource management scheme of the WBBPd does not consider all application scenarios.

Impact In certain scenarios, the call drop rate increases.

Severity Minor

Solution The DSP resource management scheme of the WBBPd is completed.


DTS: DTS2011011301008


8. The success rate of RRC connection is low.

Description The success rate of RRC connection at the cell level decreases.

Cause The Digital Signal Processor (DSP) experiences a soft failure, which results in the uplink decoding failure. Therefore, the RRC Connection Setup Complete message fails to be reported.

Impact The success rate of RRC connection is affected.

Severity Minor

Solution The mechanism for recovering a DSP soft failure is optimized.


DTS: DTS2010112703701






9. There is a low probability that UEs fail to access the cell in an uplink resource group after a board is shifted from this group to another.

Description After a board is shifted from an uplink resource group to another, there is a low probability that UEs fail to access the cell in the source uplink resource group.

Cause When a board is shifted from an uplink resource group to another, the source uplink resource group reconfigures its cell channels. The reconfigurations may conflict with the existing cell channel configurations. As a result, the cell channels of the source uplink resource group become unavailable.

Impact UEs fail to access the cell.

Severity Minor

Solution The mechanism for channel processing is optimized.



10. There is a low probability that UEs fail to access the cell after the NodeB is started.

Description After the NodeB is started, there is a low probability that UEs fail to access the cell.

Cause When the started NodeB has not entered the stable state, the RF unit is connected to two baseband boards. After the NodeB enters the stable state, the RF unit is connected to only one baseband board. As a result, there is a low probability that the channel configuration fails.

Impact UEs fail to access the cell.

Severity Minor

Solution The mechanism for channel processing is optimized.






11. There is an extremely low possibility that the RRC connection success rate decreases in a special scenario.

Description After the operator runs the ADD UCELLACCESSSTRICT command and sets the IDLECELLBARRED parameter to BARRED, there are still a small number of users who attempt to access the barred cell. This happens when the cell is configured with multiple carriers, the scrambling codes in the sector are the same, and some residual channels exist. These users fail to access the barred cell and therefore the Radio Resource Control (RRC) connection success rate decreases.

Cause There is an extremely low possibility that there are residual RF channels in a barred cell. If multiple carriers are configured in the barred cell and the scrambling codes are the same in the sector, users might attempt to access the barred cell through the residual RF channels. The failed access attempts lead to a decreased RRC connection success rate.

Impact The RRC connection success rate decreases in a special scenario.

Severity Major

Solution Clear the residual RF channels.


DTS: DTS2010112901699


12. There is an extremely low possibility that UEs fail to access the cell.

Description There is an extremely low possibility that UEs fail to access the cell.

Cause During a cell setup process, there is a low possibility that the channel configuration fails. In this case, the NodeB implements channel reestablishment and there is an extremely low possibility that the NodeB mistakenly deletes the channels of other cells. Therefore, the uplink channels of other cells are unavailable and UEs fail to access the network.

Impact UEs fail to access the network.

Severity Major

Solution The mechanism for handling abnormal channels is optimized so that the NodeB correctly deletes the channels of other cells.


DTS: DTS2010120604701






13. When the NodeB is configured with a VLAN and the UTRP bears the maintenance link of the NodeB, there is a low possibility that the M2000 fails to manage the NodeB.

Description There is a low possibility that the M2000 fails to manage the NodeB configured with a VLAN if the UTRP bears the maintenance link of the NodeB and the O&M priority is not set to 0.

Cause The mechanism for the NodeB to obtain the Differentiated Services Code Point (DSCP) is defective, resulting in the link negotiation failure between the NodeB and the M2000.

Impact The M2000 fails to manage the NodeB. Services are not affected.

Severity Minor

Solution During link negotiation, the mechanism for the NodeB to obtain the DSCP is corrected.


DTS: DTS2010100901819


14. A user fails to log in to the NodeB on the LMT using the M2000 as a proxy.

Description The LMT interface turns gray when a user attempts to log in to the NodeB on the LMT using the M2000 as a proxy.

Cause The mechanism for parsing NodeB packets sent by the M2000 is defective. Therefore, there is a very low probability that the LMT incorrectly parses the packets.

Impact A user fails to log in to the NodeB on the LMT using the M2000 as a proxy.

Severity Minor

Solution The mechanism for parsing NodeB packets is corrected on the LMT.


DTS: DTS2011031501262





15. Some optical ports on the baseband board are not displayed on the LMT.

Description Of the six optical ports on the baseband board, only three are displayed on the LMT.

Cause The device panel is incorrectly displayed on the LMT.

Impact The other three of the optical ports on the baseband board fail to be displayed on the LMT.

Severity Minor

Solution The incorrect display of the device panel is corrected on the LMT.


DTS: DTS2011031500845


16. There is a very low probability that the RRC access success rate is zero.

Description The digital signal processor (DSP) cannot recover automatically in the case of a soft failure. Therefore, the RRC access success rate of the cell is zero.

Cause Detection of DSP soft failures is not applied to all DSP codes. As a result, the DSP self-recovery mechanism fails to take effect.

Impact There is a very low probability that UEs cannot access the cell.

Severity Minor

Solution Detection of DSP soft failures is applied to all DSP codes so that the DSP can recover automatically in the case of a soft failure.







17. KPIs deteriorate in high-traffic hours if the NodeB and the RNC of certain versions are used together.

Description There is a possibility that KPIs deteriorate in high-traffic hours, when the RNC of BSC6900 V900R012C01SPC500 or later versions works with the NodeB of DBS3900 V200R012C00SPC220 or later versions and the NodeB Call History Record (CHR) log level is NORMAL.

Cause When the NodeB receives a link deletion instruction from the RNC, there is a possibility that the memory information related to the CHR is exposed to potential risks.

Impact KPIs deteriorate.

Severity Major

Solution The memory information related to the CHR is protected from potential risks.


DTS: DTS2010112405065


18. The RRU3801C reports the alarm RF Unit TX Channel Gain Out of Range (alarm ID: 26520) or the alarm RF Unit PA Overcurrent (alarm ID: 26524).

Description After the RRU3801C operates for a long time, there is a low possibility that the alarm RF Unit TX Channel Gain Out of Range (alarm ID: 26520) is reported; in certain cases, the alarm RF Unit PA Overcurrent (alarm ID: 26524) is reported.

Cause After the RRU3801C operates for a long time, there is a low possibility that an RF-related message is processed improperly, resulting in abnormal downlink gain control.

Impact There is a low possibility that alarm RF Unit TX Channel Gain Out of Range (alarm ID: 26520) is reported. This alarm does not affect the services. If the alarm RF Unit PA Overcurrent (alarm ID: 26524) is reported, however, all services in the cells covered by the RRU are interrupted.

Severity Major

Solution The mechanism for processing the RF-related message is corrected.

PR Number GCRMS: 4864015,4831220

DTS: DTS2010110902602





19. The alarm RF Unit Optical Interface Performance Degraded (alarm ID: 26506) fails to be automatically cleared.

Description The alarm RF Unit Optical Interface Performance Degraded (alarm ID: 26506) fails to be automatically cleared.

Cause The alarm processing mechanism is defective.

Impact The alarm fails to be automatically cleared.

Severity Minor

Solution The alarm processing mechanism is corrected.



20. The RRU3908 reports a false alarm RF Unit VSWR Threshold Crossed (alarm ID: 26529).

Description The VSWR test result is incorrectly determined, resulting in a false alarm RF Unit VSWR Threshold Crossed (alarm ID: 26529).

Cause The mechanism for detecting the VSWR of an RRU is defective. An incorrect VSWR is reported, resulting in a false alarm RF Unit VSWR Threshold Crossed (alarm ID: 26529).

Impact A false alarm RF Unit VSWR Threshold Crossed (alarm ID: 26529) is reported.

Severity Minor

Solution The mechanism for detecting the VSWR is corrected.







21. The existing detection mechanism for the alarm RF Unit Optical Module or Electrical Port Not Ready (alarm ID: 26501) and the alarm RF Unit CPRI Interface Error (alarm ID: 26504) needs to be optimized.

Description The existing detection periods for the alarm RF Unit Optical Module or Electrical Port Not Ready (alarm ID: 26501) and the alarm RF Unit CPRI Interface Error (alarm ID: 26504) are both 100 ms.

Cause The alarm detection period is modified to increase the alarm detection accuracy and efficiency.

Impact The existing alarm detection period needs to be modified.

Severity Minor

Solution The detection period is changed to 3s for the alarm RF Unit Optical Module or Electrical Port Not Ready (alarm ID: 26501) and 10 ms for the alarm RF Unit CPRI Interface Error (alarm ID: 26504).



22. The alarm RF Unit RX Channel RTWP/RSSI Too Low (alarm ID: 26521) fails to be reported.

Description The alarm fails to be reported when the RTWP value is smaller than –120 dB.

Cause Conditions for determining alarm reporting are defective.

Impact The alarm fails to be reported. Services are not affected.

Severity Minor

Solution Defects in the conditions are corrected.






23. There is a possibility that the NodeB reports the alarm RF Unit ALD Current Out of Range (alarm ID: 26530) when the ALD power switch is turned on.

Description When the ALD power switch is turned on, there is a low possibility that the NodeB reports the alarm RF Unit ALD Current Out of Range (alarm ID: 26530).

Cause The corresponding alarm processing mechanism is defective.

Impact There is a low possibility that the alarm RF Unit ALD Current Out of Range (alarm ID: 26530) is mistakenly reported.

Severity Minor

Solution Defects in the corresponding alarm processing mechanism are corrected.



24. There is an extremely low possibility that the NodeB reports the alarm RF Unit Maintenance Link Failure (alarm ID: 26235).

Description When the RRU clock is abnormal, there is an extremely low possibility that the NodeB reports the alarm RF Unit Maintenance Link Failure (alarm ID: 26235).

Cause The internal processing mechanism of the logic unit is defective. Therefore, the maintenance link of the RRU is faulty when the RRU clock is abnormal.

Impact There is an extremely low possibility that the NodeB reports the alarm RF Unit Maintenance Link Failure (alarm ID: 26235). The services may be interrupted.

Severity Minor

Solution The internal processing mechanism of the logic unit of the RRU is optimized so that the logic unit can be recovered in the case of an abnormal RRU clock.







25. The NodeB fails to obtain the status of the ALD power switch.

Description When the NodeB reports the alarm RF Unit ALD Switch Configuration Mismatch (alarm ID: 26531), the status of the ALD power switch queried by using the LST ALDPWRSW command is inconsistent with the actual situation.

Cause The existing interface used to obtain the status of the ALD power switch is defective. Therefore, the correct status fails to be reported.

Impact When the alarm is reported, the correct status of the ALD power switch fails to be reported.

Severity Minor

Solution An interface is added so that the correct status of the ALD power switch is reported.



26. Intermittent connectivity frequently occurs on the maintenance link of an RRU and consequently the maintenance becomes faulty.

Description When intermittent connectivity frequently occurs on the maintenance link of the RRU over the CPRI port, the maintenance link between the RRU and the BTS becomes faulty and cannot be restored. In this case, the alarm RF Unit Maintenance Link Failure (alarm ID: 26235) is reported.

Cause The link detection algorithm is defective. A large amount of redundant data is generated if intermittent connectivity frequently occurs on the maintenance link. As a result, the link detection algorithm fails to be implemented and therefore the maintenance link cannot be restored.

Impact The RRU fails to be maintained and services carried on the RRU are unavailable.

Severity Major

Solution The link detection algorithm is corrected.






27. There is a low possibility that the RRU output power drops.

Description If the RTWP value is abnormal, there is a low possibility that the RRU output power drops and cannot be restored.

Cause An abnormal RTWP value triggers the internal data collection process of the RRU, which consumes the CPU resources.

Impact The RRU output power drops.

Severity Minor

Solution The data collection mechanism of the RRU is optimized. By default, the data collection function is disabled.



28. When a cell is established on the SRRU or WRFU, UEs using certain frequencies in the cell fail to access the network.

Description When a cell using the frequency band from 9820 to 9840 MHz is established on the SRRU or WRFU and has a radius of less than 5 km, UEs may fail to access the cell.

Cause The uplink delay is incorrectly calculated within the range of the preceding frequency band.

Impact UEs may fail to access the cell.

Severity Major

Solution The calculation of uplink delay in the preceding frequency band of the SRRU or WRFU is corrected.


Test Case ID ATP: 2010091602677





29. The RRU fails to be maintained if its CPU usage is high for a long period.

Description The RRU fails to be maintained remotely if its CPU usage is high for a long period. The fault cannot be rectified.

Cause Task scheduling on the RRU is abnormal, leading to high CPU usage for a long period. As a result, the remote RRU maintenance task fails to be scheduled.

Impact The RRU fails to be maintained remotely.

Severity Minor

Solution The mechanism for scheduling tasks on the RRU is optimized.



30. The alarm RF Unit Input Power Abnormal (alarm ID: 28329) is reported falsely.

Description The BTS reports the alarm RF Unit Input Power Abnormal (alarm ID: 28329) when the power supply to RRUs is normal.

Cause The alarm processing mechanism has a defect. As a result, the internal warning information is falsely reported as a major alarm.

Impact The alarm RF Unit Input Power Abnormal (alarm ID: 28329) is reported falsely, whereas there is no impact on services.

Severity Major

Solution The alarm processing mechanism is modified to ensure correct reporting of the alarm RF Unit Input Power Abnormal (alarm ID: 28329).


DTS: DTS2010102100928





31. There is an extremely low probability that the alarm ALD Maintenance Link Failure (alarm ID: 26541) is falsely reported during an ALD scan process.

Description There is an extremely low probability that the alarm ALD Maintenance Link Failure (alarm ID: 26541) is falsely reported during an ALD scan process.

Cause The ALD scan process has defects.

Impact The alarm is falsely reported and automatically cleared in one second.

Severity Minor

Solution The algorithm for ALD scan is modified.



32. The state of the ALD DC power switch cannot be obtained after a multi-wire cable is disconnected.

Description After a multi-wire cable is disconnected, the RRU switches off the ALD DC power switch. However, the query result displays that the state of the ALD DC power switch is ON.

Cause The processing mechanism for the state of the ALD DC power switch has defects and therefore the RRU cannot obtain the switch state promptly. As a result, the query result does not indicate the actual state of the ALD DC power switch.

Impact The query result of the state of the ALD DC power switch does not indicate the actual state.

Severity Warning

Solution The processing mechanism for the state of the ALD DC power switch is optimized.







33. The VSWR values are still reported after the power amplifiers of the SRRU shutdown.

Description After the power amplifiers of the SRRU are shut down, the VSWR values can still be queried by running the DSP VSWR command.

Cause After power amplifiers are shut down, the VSWR values should be invalid.

Impact There is no impact on services, but the GUI is affected.

Severity Warning

Solution The mechanism for reporting VSWR values is modified.

PR Number CMM: A17D33087

Test Case ID APT-33087


1. The cell is faulty because a false alarm RF Unit Clock Problem (alarm ID:26538) is reported.

Description When the WRFU is configured, there is a possibility that a false alarm RF Unit Clock Problem (alarm ID: 26538) is reported. As a result, the cell becomes faulty.

Cause The alarm detection mechanism is defective. Therefore, a false alarm RF Unit Clock Problem (alarm ID: 26538) is reported.

Impact The cell is unavailable.

Severity Major

Solution The related alarm detection mechanism is optimized so that the alarm RF Unit Clock Problem (alarm ID: 26538) is not reported.


DTS: DTS2010121001880






1. In the case of SRB over E-DCH and RRC connection over HSUPA, there is a possibility of call failures.

Description In the case of SRB over E-DCH and RRC connection over HSUPA, there is a possibility of call failures when services are set up on the WBBPd.

Cause There is a defect in the processing of DSPs in the preceding situation.

Impact There is a possibility of call failures.

Severity Major

Solution Optimizations are made to the processing of DSPs in the preceding situation.


DTS: DTS2010101100784


2. The CS call drop rate is relatively high.

Description When services are set up on the WBBPd, there is a low probability of a relatively high CS call drop rate.

Cause There is a defect in the algorithm of resource allocation within a DSP. As a result, there is a low probability of a resource conflict between a new service and an existing service in a DSP.

Impact The CS call drop rate is relatively high.

Severity Major

Solution The service setup and release procedures are optimized.

PR Number GCRMS: 4821041,4819796

DTS:DTS2010092800559






3. The RRC setup success rate drops to zero with a very low probability.

Description The RRC setup success rate of a cell drops to zero abruptly and then restores after the baseband board is reset.

Cause The part of the DSP memory storing codes becomes invalid. CRC check on FACH FP packets fails and FP packets are discarded. As a result, the RRC setup success rate of the cell drops to zero.

Impact There is a very low probability that users cannot access the network.

Severity Minor

Solution The mechanism for checking DSP memory invalidation is optimized so that the DSP memory becomes valid automatically upon invalidation.

PR Number GCRMS:4821482

DTS:DTS2010101801568


4. Statistics on the uplink channel element (CE) congestion are incorrect.

Description Uplink CE congestion is reported when uplink CEs are still available.

Cause When the maximum number of UEs supported by a baseband board is reached, new UEs cannot access the baseband board. In this case, uplink CE congestion is falsely reported.

Impact The traffic counter VS.RRC.Rej.UL.CE.Cong at the RNC is falsely used.

Severity Minor

Solution Another error code is used to collect the statistics on UE access failures when the maximum number of UEs supported by a baseband board is reached.


DTS: DTS2010092501875





5. The on-site software upgrade using the USB storage device lasts for a long period of time.

Description If the USB storage device is used for the on-site software upgrade, the upgrade lasts for a long period of time.

Cause The algorithm for upgrading the NodeB software through the USB storage device is of low efficiency, resulting in a relatively long duration.

Impact The duration of the NodeB software upgrade is relatively long, if the USB storage device is used for the upgrade.

Severity Major

Solution The algorithm for upgrading the NodeB software through the USB storage device is optimized and therefore the duration of the upgrade is shortened by about 25%.


DTS: DTS2010092700454


6. The Inter-System Monitoring Device Parameter Settings Conflict alarm (alarm ID: 26271) may not be reported, or is reported but cannot be cleared.

Description In MBTS, the Inter-System Monitoring Device Parameter Settings Conflict alarm (alarm ID: 26271) may not be reported, or is reported but cannot be cleared.

Cause The task that handles this alarm and the messaging about this alarm are not synchronized. As a result, the mechanism for generating and clearing the alarm becomes abnormal.

Impact The Inter-System Monitoring Device Parameter Settings Conflict alarm (alarm ID: 26271) may not be reported, or is reported but cannot be cleared. This has no impact on services.

Severity Minor

Solution Modifications are made to the synchronization mechanism between the task that handles this alarm and the messaging about this alarm. The synchronization is guaranteed.


DTS: DTS2010070102385

Test Case ID ATP- 2010070102385





7. The data rate of one type of commercial terminals drops to or approaches 0 kbit/s when processing HSDPA services.

Description The data rate of one type of commercial terminals drops to or approaches 0 kbit/s when processing High Speed Downlink Packet Access (HSDPA) services. PS call drops occur when the situation is critical.

Cause This type of terminals fails to decode the High Speed Shared Control Channel (HS-SCCH) with a high probability when it processes HSDPA services together with other types of terminals.

Impact The data rate of one type of commercial terminals drops to or approaches 0 kbit/s when processing HSDPA services. PS call drops occur when the situation is critical.

Severity Major

Solution The MAC-hs scheduling algorithm of the NodeB is optimized.


DTS:DTS2010101902359


8. The E1/T1 loopback test fails to be started.

Description After a positive value of Daylight Saving Time (DST) is set on the NodeB, the execution result of the STR E1T1RTTST command indicates "Starting timer failed".

Cause DST is not considered when the start time of the E1/T1 loopback test is processed, and therefore the start time is earlier than the current time of the NodeB.

Impact The E1/T1 loopback test function is not available.

Severity Minor

Solution Modifications are made to the algorithm related to the start time of the E1/T1 loopback test.


DTS:DTS2010090802634





9. There is a relatively low probability that a cell cannot be accessed by UEs after the associated RRU resets.

Description When an RRU is a long distance away from the baseband processing unit (WBBP), there is a relatively low probability that the cell served by the RRU cannot be accessed by UEs after the RRU resets. If RRUs are connected in cascade, the probability becomes larger as the number of RRUs increases.

Cause There is a defect in the algorithm of calculating the delay between the WBBP and each RRU. When an RRU is configured far away from the WBBP, this defect causes the RRU to report an incorrect delay during its resetting.

Impact The cell served by the RRU cannot be accessed by UEs.

Severity Minor

Solution Improvements are made to the algorithm of calculating the delay between the WBBP and each RRU.


DTS:DTS2010090901694


10. There is a very low possibility that the service drop occurs in the case of a softer handover.

Description After a softer handover is complete, a service drop occurs because of the synchronization loss in the uplink at a very low probability.

Cause In the softer handover, the algorithm for searching for new links is not proper. As a result, valid paths cannot be found on the new links at a very low probability.

Impact There is a very low possibility that a service drop occurs in the case of softer handover.

Severity Minor

Solution The algorithm for searching for new links is optimized in softer handovers so that valid paths can be found.


DTS:DTS2010090901699






11. The SCTP signaling packets over the Iub interface are discarded.

Description In scenarios with IP transmission and heavy traffic, the alarm SCTP Link Congestion (alarm ID: 21542) is reported on the RNC side and the cell is unavailable.

Cause When the number of SCTP signaling packets delivered by the RNC exceeds the reception buffer capacity of the NodeB, the data packets are discarded. Therefore, the RNC keeps retransmitting packets, leading to congestion.

Impact The cell is unavailable and services are interrupted in case of congestion.

Severity Minor

Solution The SCTP reception buffer capacity of the NodeB increases.


CMM: DTS2010071700835


12. The USB flash disk may fail to import software after the NodeB resets.

Description When a NodeB is initially configured at site by using a USB flash disk, there is a possibility that the USB flash disk will fail to import software into the NodeB after the NodeB resets.

Cause There is a defect in the resetting mechanism of the USB port on the NodeB. As a result, the USB port may become unreliable after the NodeB resets under certain circumstances.

Impact Importing software from the USB flash disk to the NodeB may fail. This problem can only be solved by manually pulling out and then plugging in the USB flash disk again.

Severity Minor

Solution Improvements are made to the resetting mechanism of the USB port on the NodeB to improve its reliability after the NodeB resets.


DTS:DTS2010082301156





13. The UPEU and UEIU of the V2 NodeB report the alarm Board Type and Configuration Mismatch (alarm ID: 26251).

Description When the board type actually matches the configuration, there is a low probability that the UPEU and UEIU of the V2 NodeB report the alarm Board Type and Configuration Mismatch (alarm ID: 26251).

Cause The alarm detecting mechanism on board type is not robust enough. There is a low probability that the type of the UPEU and UEIU cannot be correctly queried during board startup.

Impact A false alarm may be reported, and services are not affected.

Severity Minor

Solution The cyclic detection mechanism for the alarm of board type is used to prevent false alarms in exceptions.

PR Number GCRMS: 4849960DTS:DTS2010081801445


14. The External Clock Reference Problem alarm (alarm ID: 26262) is generated in an intermittent manner.

Description In MBTS, there is a possibility that the External Clock Reference Problem alarm (alarm ID: 26262) is generated in an intermittent manner. The reason is that the local end may not correctly identify the main control board of the peer end.

Cause There is a defect in the mechanism for the local end to detect the main control board of the peer end. This may cause the incorrect identification of this board at the local end, lead to the continual negotiation of clock references between the two ends, and ultimately induce the intermittent generation of the alarm.

Impact The External Clock Reference Problem alarm (alarm ID: 26262) is generated in an intermittent manner. Services are not impacted.

Severity Minor

Solution Improvements are made to the detecting mechanism to ensure the correct identification of the main control board of the peer end at the local end.


DTS:DTS2010101400790






15. The data processing performance of the WBBPd is not high enough.

Description There is room for optimization of the data processing performance of the WBBPd.

Cause The CPU configuration of the WBBPd is inappropriate, so that the data processing performance of the board is low.

Impact There is a high probability of overload on the WBBPd, resulting in UE access failure.

Severity Major

Solution The CPU hardware parameter configuration is optimized.



16. The NodeB is reset in the case of heavy traffic.

Description In the case of heavy traffic, there is a low probability that the NodeB is reset unexpectedly.

Cause There is a defect in the internal message processing mechanism, so that message processing tasks are not scheduled. In extreme cases, message resources are exhausted.

Impact The NodeB is reset unexpectedly.

Severity Minor

Solution The message processing mechanism is optimized so that message processing tasks are scheduled promptly.






17. The protocol type of IP clock is changed unexpectedly after a software upgrade.

Description After a software upgrade, the clock protocol type is changed from Huawei proprietary clock to Precision Time Protocol (PTP).

Cause The algorithm for software upgrades does not properly handle the smooth upgrade of the IP clock.

Impact The NodeB clock is abnormal. The alarm Clock Reference Abnormal (alarm ID: 26262) is reported.

Severity Major

Solution The defects in the algorithm for smoothing data in software upgrades are cleared.



18. In a specific WRFU/SRRU configuration, the downlink signal quality deteriorates.

Description When the carrier spacing of the WRFU/SRRU is 10 MHz and three carriers are configured, the downlink signal quality deteriorates.

Cause When the carrier spacing of the WRFU/SRRU is 10 MHz and three carriers are configured, the calculated clipping threshold is incorrect.

Impact The downlink signal quality deteriorates.

Severity Major

Solution The calculation method of clipping threshold is corrected.







19. The alarm LED is falsely ON when WRFUs are interconnected.

Description In the case of interconnected WRFUs in combined cabinets, there is no related alarm on the LMT but the alarm LED on the WRFU panel is falsely ON.

Cause There are defects in the internal alarm mechanism for interconnected WRFUs in combined cabinets.

Impact The alarm LED is falsely ON.

Severity Minor

Solution The internal alarm mechanism for WRFUs is modified.



20. The NodeB automatically clears the user-defined TMA attenuation value and sets it to the default one after the NodeB resets.

Description In MBTS, if the tower-mounted amplifier (TMA) attenuation and Radio Frequency (RF) desensitivity are configured for a Multi-mode Remote Radio Unit (MRRU) and then the MRRU is reset, the NodeB automatically clears the user-defined TMA attenuation value and sets it to the default one. As a result, TMA attenuation is not applied and the Received Total Wideband Power (RTWP) of the NodeB rises.

Cause In essence, TMA attenuation and RF desensitivity are mutually exclusive and therefore configuring only one of them for an MRRU is recommended. If both of them are configured and then the MRRU is reset, the NodeB automatically sets the TMA attenuation value to the default one despite the previous user-defined configuration.

Impact RTWP of the NodeB rises.

Severity Minor

Solution Improvements are made to maintain the user-defined value of TMA attenuation, after both TMA attenuation and RF desensitivity are configured for an MRRU and then the MRRU is reset.






21. An RF Unit PA Overcurrent alarm (alarm ID: ALM-26524) may be generated when the transmit power from the LRRU surges within a short period of time.

Description When the transmit power from a Long Time Evolution (LTE) Remote Radio Unit (LRRU) surges within a short period of time, an RF Unit PA Overcurrent alarm (alarm ID: ALM-26524) may be generated and then automatically cleared in a couple of seconds. This phenomenon may occur with a higher probability during cell re-establishing due to the sharply increased transmit power in the process.

Cause There is a defect in the mechanism for controlling the gain on the DL transmit power in the LRRU. As a result, the transmit power from the LRRU may increase to an amount that will induce the RF Unit PA Overcurrent alarm, when the transmit power surges within a short period of time.

Impact There is a relatively low probability that the power amplifier in the associated LRRU will be destroyed.

Severity Major

Solution Improvements are made to the gain control algorithm.



22. Logging in to the LMT through the M2000 times out.

Description No response is returned within a long period of time after users right-click a base station node and choose to start the LMT from the shortcut menu on the M2000 topology. Later, an error indicating that the execution of the LST NODEB command times out, as well as a login failure are reported.

Cause Excessive data is returned upon the execution of the LST NODEB command. The LMT cannot handle the data, and thus reports the errors.

Impact Users cannot log in to the LMT through the M2000.

Severity Minor

Solution The method of handing the data returned upon the execution of the LST NODEB command is optimized so that the LMT can handle a large amount of data properly.







23. BOOTP detection fails in GU co-transmission scenarios where the OM channel is carried on a PPP port.

Description The OM channel is carried on the Point-to-Point (PPP) port on the GSM side in GSM+UMTS co-transmission scenarios. In this situation, Bootstrap Protocol (BOOTP) detection fails.

Cause In GU co-transmission scenarios where the OM channel is carried on a PPP port on the GSM side, an error occurs when the BOOTP detection algorithm checks PPP links on the backplane.

Impact BOOTP detection fails for a newly deployed site, and hence the base station cannot be maintained remotely.

Severity Minor

Solution The BOOTP detection algorithm in GSM+UMTS co-transmission scenarios is optimized.



24. Uses fail to access the network because downlink CE resources are insufficient.

Description Some 64 kbit/s PS users in a cell fail to access the network because downlink Channel Element (CE) resources are insufficient.

Cause The downlink CE resource management mechanism of the NodeB is defective. When CE resources are insufficient, Iub link setup or reconfiguration fails. As a result, new 64 kbit/s PS users fail to access the network.

Impact Some 64 kbit/s PS users fail to access the network.

Severity Minor

Solution The downlink CE resource management mechanism of the NodeB is optimized.






25. When the WBBPa provides the downlink resources of the NodeB, HSUPA flow control fails.

Description When the WBBPa provides the downlink resources of the NodeB, HSUPA flow control is incorrectly processed and therefore fails.

Cause The internal flow control frames are incorrectly processed, and therefore the flow control frames cannot be sent.

Impact In case of congestion over the Iub interface, HSUPA flow control fails.

Severity Major

Solution The defects in flow control for the WBBPa are cleared.



26. If a NodeB is deployed with the pre-delivery configuration, the alarms of the NodeB cannot be reported.

Description The NodeB is deployed with the pre-delivery configuration, in which the default NodeB status is applied. Then, the alarms of the NodeB are not displayed on the M2000.

Cause In the pre-delivery configuration, the default NodeB status is Testing. When the NodeB is in Testing state, the M2000 masks all alarms of the NodeB. Therefore, the alarms of the NodeB are not displayed on the M2000 until the status is changed to Normal by running the SET NODEBSTATUS command.

Impact The alarms of the NodeB are not displayed on the M2000.

Severity Minor

Solution In the pre-delivery configuration file for the NodeB, the default NodeB status is changed to Normal.








1. The alarm Uplink Service Processing Channel Abnormal (alarm ID: 28300) is reported, with the fault code of 0 (CPU-DSP EMAC Interface Link Abnormal).

Description The alarm Uplink Service Processing Channel Abnormal (alarm ID: 28300) is reported, with the fault code of 0 (CPU-DSP EMAC Interface Link Abnormal).

Cause The DSP internal program processing has defects. Therefore, the DSP fails in special circumstances and the handshake between the DSP and the CPU stops. As a result, the NodeB reports the alarm Uplink Service Processing Channel Abnormal (alarm ID: 4002), with the fault code of 0 (CPU-DSP EMAC Interface Link Abnormal).

Impact The alarm Uplink Service Processing Channel Abnormal (alarm ID: 28300) is reported. The cell services are interrupted. The duration of the interruption is 30s to 60s.

Severity Major

Solution The DSP internal program processing is optimized to ensure that the DSP does not fail in special circumstances.



2. The clock cannot be obtained if the clock link is set up on the UTRP6.

Description If a line clock link is configured on the UTRP6 and the line clock is selected as the reference clock of the NodeB, the NodeB clock is lost and the alarm External Clock Reference Problem (alarm ID: 26262) is generated.

Cause The NodeB does not process the line clock link on the UTRP6.

Impact The NodeB cannot lock the line clock on the UTRP6.

Severity Minor

Solution The processing mechanism is added to the NodeB so that the NodeB supports the line clock link on the UTRP6.






3. In traffic statistics, the performance counters VS.HSUPA.MeanBitRate and VS.HSUPA.MeanBitRate.WithData are incorrect.

Description In traffic statistics, the values of the performance counters VS.HSUPA.MeanBitRate and VS.HSUPA.MeanBitRate.WithData are one tenth of their actual values.

Cause These two traffic counters are floating-point values with coefficients. When the NodeB calculates floating-point values, it does not take the coefficients into consideration. As a result, the calculated floating-point values are one tenth of their actual values.

Impact In traffic statistics, the performance counters VS.HSUPA.MeanBitRate and VS.HSUPA.MeanBitRate.WithData are incorrect.

The ongoing services are not affected.

Severity Minor

Solution When the NodeB calculates floating-point values, it takes coefficients into consideration.



4. The time of alarm clearance is earlier than the time of alarm generation for some alarms after the daylight saving time is enabled on the NodeB.

Description After the daylight saving time is set on the NodeB, the time of alarm clearance is earlier than the time of alarm generation for some alarms in the query results on the M2000.

Cause During alarm synchronization, the history NodeB alarms reported to the M2000 do not observe the daylight saving time.

Impact After the daylight saving time is enabled on the NodeB, the time of alarm clearance for some alarms is wrong. As a result, the time of alarm clearance is earlier than the time of alarm generation.

Severity Minor

Solution The reporting time of history NodeB alarms is changed to the daylight saving time if the daylight saving time is enabled on the NodeB.







5. If both the performance measurements with the 15-minute period and 60-minute period are started on the M2000, the performance statistics obtained from the 60-minute measurement are inaccurate.

Description If both the performance measurements with the 15-minute period and 60-minute period are started on the M2000, there is a low probability that the sum of the statistics obtained from four 15-minute measurements is inconsistent with the statistics obtained from the 60-minute measurement.

Cause If both the performance measurements with the 15-minute period and 60-minute period are started on the M2000, the NodeB misoperates the cell ID during the 60-minute measurement. As a result, the KPI statistics obtained from the 60-minute measurement are inaccurate.

Impact The KPI statistics with the 60-minute period on the M2000 are not accurate. Users can refer to the KPI statistics with the 60-minute period.


Severity Minor

Solution The processing of performance measurements is modified so that the cell ID is operated correctly.



6. The NodeB Call Data Tracing (CDT) time and the NodeB time are inconsistent after the daylight saving time is enabled.

Description The NodeB CDT time and the NodeB time are inconsistent after the daylight saving time is enabled.

Cause The NodeB CDT time does not observe the daylight saving time.

Impact The time displayed in the NodeB CDT and the NodeB time are inconsistent after the daylight saving time is enabled.

Severity Minor

Solution The daylight saving time is enabled when the NodeB CDT is reported.






7. A false alarm Board Type and Configuration Mismatch (alarm ID: 26251) is generated on the UEIU or UPEU after the NodeB resets.

Description There is a low probability that the alarm Board Type and Configuration Mismatch (alarm ID: 26251) is generated on the UEIU or UPEU after the NodeB resets.

Cause In the NodeB startup process, the mechanism for detecting the alarm Board Type and Configuration Mismatch (alarm ID: 26251) is not appropriate. As a result, the alarm detection is not triggered after the fault is rectified.

Impact A false alarm is reported.


Severity Warning

Solution The mechanism for alarm detection in the NodeB startup process is optimized so that the false alarm is not reported.



8. The alarm IP Path Excessive Packet Loss Rate (alarm ID: 25898) is not reported when the packet loss rate is excessive on the transport network.

Description The alarm IP Path Excessive Packet Loss Rate (alarm ID: 25898) is not reported when loss of packets is detected by the IPPM.

Cause The mechanism for alarm detection in loss of packets on the IP path has defects.

Impact Transport faults cannot be located quickly.

Severity Minor

Solution An MML command switch (ACT IPPM/DEA IPPM) is added to the mechanism for IPPM alarm detection. When the switch is enabled, loss of packets is detected on the IP path. If the packet loss rate reaches the alarm threshold, the alarm IP Path Excessive Packet Loss Rate (alarm ID: 25898) is reported.

In certain network scenarios where the intermediate transport device modifies the DSCP value of the packet, the IPPM alarm detection fails and a false alarm may be reported. In this case, you are advised to run the DEA IPPM command to disable the IPPM alarm detection.







9. The RTWP test malfunctions.

Description During the RTWP test on the LMT, the data reported in the first one minute is wrong.

Cause When the NodeB starts the RTWP test, data initialization has errors.

Impact The data reported in the first one minute of the RTWP test cannot be used for analysis.

Severity Minor

Solution The implementation of the RTWP test is modified so that data initialization is correct.



10. When the NodeB uses the STM-1 transport mode, loss of packets occurs if the downlink data rate exceeds 30 Mbit/s.

Description When the NodeB uses the STM-1 transport mode, loss of packets occurs and the data rate per UE fluctuates if the total downlink data rate exceeds 30 Mbit/s.

Cause The transport interface board has insufficient AAL2 data processing capabilities.

Impact When the UTRP6 is used as the transport interface board, loss of packets occurs and the data rate per UE fluctuates if the total downlink data rate exceeds 30 Mbit/s.

Severity Major

Solution The ATM cell processing capability of the UTRP6 is optimized.






11. When the numbers of CEs on multiple WBBPs are different, the CPU usage of different boards is imbalanced.

Description In high traffic hours, when two or more WBBPs with different numbers of CEs are used, the alarm Board CPU Overload (alarm ID: 3510) is frequently generated on the board with a larger number of CEs.

Cause The UEs are allocated to the WBBP with a larger number of CEs by default. As a result, most of UEs are allocated to the WBBP with a larger number of CEs, until the WBBP reports the alarm Board CPU Overload (alarm ID: 3510). After the alarm is reported, UEs are allocated to the WBBP with a smaller number of CEs.

Impact The alarm Board CPU Overload (alarm ID: 3510) is frequently generated.


Severity Minor

Solution The CPU usage check of the board is added to the UE allocation policy so that UEs are evenly distributed on multiple WBBPs.



12. The throughput of a single HSDPA user in the coverage of a cell with poor signal quality is low.

Description When a single HSDPA user is tested in the middle-to-far distance from the cell center, it is found that the throughput of the user is low.

Cause The TB size table is set improperly when the TFRC selection is used by the HSDPA user, causing a high BLER value when the user uses certain TB sizes.

Impact The throughput of a single HSDPA user in the coverage of a cell with poor signal quality is affected.

Severity Warning

Solution The TB size table is optimized for the HSDPA user to use the TFRC selection.







13. UMTS UEs fail to access MBTSs.

Description There is a low probability that UMTS UEs fail to access the MBTS after the transport network halts and recovers.

Cause The interruption of the transport network makes the clock in the site be in abnormal state in a short period. If the RRU links recover in this period, the related delay parameters of the RRU are calculated incorrectly. After the clock recovers, the parameters are not corrected.

Impact The UEs of the UMTS cell fail to access the MBTS.

Severity Major

Solution The MBTS calculates the related delay parameters of the RRU when the MBTS clock recovers.



14. Fluctuations in RTWP affect the call completion rate.

Description Fluctuations in RTWP affect the call completion rate.

Cause The RTWP-based filtering algorithm provided by the NodeB does not perform smooth filtering on the NodeB external interference, which leads to fluctuations in the RTWP values reported to the RNC.

Impact A small number of UEs fail to access the network.

Severity Minor

Solution The RTWP-based filtering algorithm is optimized so that smooth filtering can be performed on external interference.






15. The TP48300A power system is not supported.

Description The TP48300A power system is not supported.

The TP48300A power system is used for indoor power supply. Its cabinet can accommodate six PSUs, with no space for customer equipment.

Cause The TP48300A power system needs to be supported.

Impact The TP48300A power system cannot be monitored or maintained.

Severity Warning

Solution The configuration of the TP48300A power system is enabled, and six PSUs are added.



16. The patch area is not detailed in the help information about the LST SOFTWARE command.

Description The patch area is not detailed in the help information about the LST SOFTWARE command.

Cause The patch area is not explained in detail.

Impact The user experience is affected.

Severity Warning

Solution More details about the patch area are added to the help information about the LST SOFTWARE command.







17. Interference monitoring in GUI mode fails to be started after user login through a non-admin M2000 proxy.

Description Interference monitoring in GUI mode fails to be started after user login through a non-admin M2000 proxy.

Cause The functions of starting and stopping interference monitoring cannot be registered in the M2000 mediation layer. As a result, the functions cannot be authenticated by the M2000 after user login through a non-admin M2000 proxy.

Impact Interference monitoring in GUI mode fails to be started.

Severity Minor

Solution The functions of starting and stopping interference monitoring can be registered in the M2000 mediation layer.



18. An IP path or OM channel cannot be pinged when some certain device is deployed in the network.

Description In IP transport mode, a certain transport device in the network filters the packets of the specified DSCP value. As a result, an IP path or OM channel cannot be pinged.

Cause The ping packets for IP paths and OM channels use the default DSCP value 63 to ensure the priority of the ping packets. The transport equipment may filter out a packet that uses this default value.

Impact An IP path or OM channel may be regarded as disconnected by mistake. In this case, the IPPATH Fault Alarm (alarm ID: 2760) is reported.

Severity Warning

Solution The ping packets for IP path and OM channel use the configured DSCP values instead of the default DSCP value.






19. In compressed mode, bit errors occur in the uplink with a probability. As a result, the data rate of 64 kbit/s services is decreased by half.

Description In the case of compressed mode by spreading factor (SF) reduction by half, there is a probability that the data rate of 64 kbit/s services is decreased by half when the services are established on the WBBPb.

Cause There are defects in the decoding mechanism triggered by the specified block size in the case of compressed mode by SF reduction by half. As a result, data blocks are missing with a probability and thus the uplink data rate is decreased by half.

Impact This problem affects the R99 64 kbit/s services established on the WBBPb in the case of compressed mode by SF reduction by half.

Severity Minor

Solution Modify the mechanism for processing the data block with a specified size.



20. Application scenarios of the DSP VSWR command are not complete in the Help.

Description Application scenarios of the DSP VSWR command are not complete in the Help.

Cause The information related to the application scenarios of the DSP VSWR command is not complete in the Help.

Impact When running the DSP VSWR command to query the VSWR, a user cannot obtain the application scenarios of and precautions for the command in the Help.

Severity Warning

Solution Add the descriptions of the application scenarios of the DSP VSWR command to the Help.







21. The interconnection of MP groups fails because of incompatibility.

Description Negotiation fails during the interconnection of MP groups between the Huawei transmission device and some Alcatel-Lucent transmission devices. In this case, the transmission link fails.

Cause The MP group fails in negotiation because the negotiation value of the MRU of the peer device is 1600 but the limitation of the NodeB on the MRU is 1500.

Impact The transmission is interrupted.

Severity Minor

Solution The limitation on the maximum value of the MRU being 1500 is cancelled so that the peer parameters are compatible with the local parameters.

PR Number CMM: AN1D11900


22. The Board Startup Abnormal Alarm (alarm ID: 28381) is generated on the 2 x 60 W RRU.

Description The Board Startup Abnormal Alarm (alarm ID: 28381) is generated on the 2 x 60 W RRU after it is started.

Cause The 2 x 60 W RRU supports three carriers but the BBU software does not process the three carriers of the RRU correctly.

Impact The Board Startup Abnormal Alarm (alarm ID: 28381) is generated.


Severity Warning

Solution The BBU software is modified so that it processes the three carriers of the RRU correctly.






23. The success rate of the RRC connection setup decreases with a small probability in a specific scenario.

Description Uplink resources are established on the WBBPd, and the success rate of the RRC connection setup decreases with a low probability.

Cause The decoding delay on the uplink common channel becomes very large because of abnormal processing in the DSP module. In this case, the UE re-initiates an RRC connection request before receiving the RRC_CONN_SETUP message from the RNC. As a result, the RNC repeatedly measures the number of RRC connection setups and the success rate of the RRC connection setup decreases.

Impact The services are not affected, but the success rate of the RRC connection setup decreases.

Severity Minor

Solution The decoding procedure on the uplink common channel of the DSP module is optimized.



24. The service drop rate for 2 ms-based HSUPA users increases slightly after the SRB over EDCH switch is turned on.

Description The service drop rate for 2 ms-based HSUPA users increases slightly after the SRB over EDCH switch is turned on.

Cause Many users are carried on the WBBPb. After all CE resources are occupied, the data processing in the chip is abnormal with a probability lower than 1%. As a result, the HARQ failure is generated.

Impact The service drop rate for 2 ms-based HSUPA users carried on the WBBP increases slightly, but the service drop rate for non-2 ms-based users is not affected.

Severity Major

Solution The mechanism for coordination between the software and chip is optimized.


CMM: SYED69211






25. The maintenance link of the reused antenna line device (ALD) is abnormal.

Description The NodeB does not send special control frames to the reused tower mounted amplifier (TMA). Therefore, the alarm ALM-26541 ALD Maintenance Link Failure is reported to the NodeB configured with the reused TMA.

Cause The special control frames that are sent to the reused TMA help to prevent the TMA from sending a large number of data block links. However, the NodeB does not send such special control frames to the reused TMA. Therefore, the reused TMA causes interference to the maintenance link of the ALD and the ALD cannot be maintained.

Impact The services are not affected, but the ALD for the NodeB in which the reused TMA is not manufactured by Huawei cannot be maintained.

Severity Minor

Solution The NodeB sends special control frames to the reused TMA, and a switch is added to determine whether such frames must be sent.



26. The NodeB abnormally resets due to an incorrect number of external alarm ports on the TCU in the configuration file.

Description The configuration file contains an incorrect number of external alarm ports on the TCU. After the configuration file is delivered to the NodeB and the configuration takes effect, the NodeB resets abnormally.

Cause The protection mechanism is not applied to the number of external alarm ports on the TCU. As a result, the NodeB resets abnormally if the number is incorrect.

Impact The NodeB resets repeatedly and the services are interrupted.

Severity Major

Solution The protection mechanism is applied to the number of external alarm ports on the TCU so that the NodeB will not reset if the number is incorrect.


CMM: SYED69685





27. Cells become out of service one minute after an abnormal AC mains power alarm is reported.

Description In the case of abnormal AC mains power, the alarm Mains Input Out of Range (alarm ID: 25622) is reported and the cells become out of service in one minute.

Cause By default, the intelligent shutdown switch is set to ENABLE, and the level-1 shutdown delay is one minute, which is too short.

Impact Cells become out of service in one minute in the case of abnormal AC mains power.

Severity Major

Solution The intelligent shutdown switch is set to DISABLE by default. If the switch is set to ENABLE, a proper shutdown delay should be set according to the capacity of batteries configured for the NodeB.

PR Number CMM: BF5D01412


28. If a flow control parameter is set to a specific value, a software error occurs and therefore the rate of the HSDPA service fails to increase.

Description If a flow control parameter is set to a specific value, a software error occurs. In this case, radio link reconfiguration fails, and therefore the rate of the HSDPA service fails to increase.

Cause A software error occurs in the processing of the flow control parameter that is set to the specific value for radio link reconfiguration.

Impact The radio link reconfiguration fails, and therefore the rate of the HSDPA service fails to increase.

Severity Minor

Solution A modification is made to the processing of the flow control parameter in the software.







29. The upgrade of distributed cells to V200R011C01SPC5XX may fail.

Description If the configuration of distributed cells is performed on the CME, the upgrade of the cells to V200R011C01SPC5XX may fail.

Cause In the configuration file generated on the CME for distributed cells, the parameter settings of the cells do not meet the constraints defined in the NodeB software. Therefore, during the upgrade, the NodeB is incompatible with the configuration generated on the CME.

Impact The upgrade fails, and the NodeB cannot provide services.

Severity Major

Solution The NodeB code is modified so that the NodeB is compatible with the configuration generated on the CME.



30. The description of health check is incorrect in the 3900 series WCDMA NodeB V200R011C01SPC510 Upgrade Guide (M2000-Based).

Description The description of the Upgrade Preparations section in the 3900 series WCDMA NodeB V200R011C01SPC5XX Upgrade Guide (M2000-Based) is not proper. As a result, the NE health check function on the M2000 is unavailable.

Cause The NE health check function on the M2000 is supported only by the NodeB of V200R011C01SPC5XX or later versions.

Impact The NodeB of R11 or earlier versions fails in preparations before upgrade if the description in the 3900 series WCDMA NodeB V200R011C01SPC5XX Upgrade Guide (M2000-Based) is followed.

Severity Warning

Solution The version description of the NE health check function on the M2000 is added to the Upgrade Preparations section in the 3900 series WCDMA NodeB V200R011C01SPC5XX Upgrade Guide (M2000-Based). This ensures that NodeBs of different versions use different methods to perform health check.






31. There is a probability that the alarm ALD Maintenance Link Failure (alarm ID: 26541) is falsely generated on a certain antenna system.

Description When the maintenance link of an RRU fails, the alarm ALD Maintenance Link Failure (alarm ID: 26541) is falsely generated on the AISG2.0 antenna. The alarm may persist after the maintenance link of the RRU is restored.

Cause The mechanism for processing alarms of a certain antenna system has defects.

Impact The services are not affected, but the related antenna system cannot be maintained during the occurrence of the false alarm.

Severity Major

Solution The mechanism for processing alarms of the AISG2.0 antenna is optimized.



32. The bit error rate (BER) of HSDPA users over the air interface is 100% in the cell.

Description At the HSDPA-capable site, there is a low probability that the throughput of HSDPA users in the cell is zero and the BER over the air interface is 100%.

Cause The parameter settings of the HSDPA coding chip are incorrect. The chip has no output and cannot be restored automatically. In this case, the BER of HSDPA users over the air interface is 100% and the traffic radio bearers (TRB) for users are reset.

Impact The throughput of HSDPA users in the cell is zero.

Severity Major

Solution The configuration procedure is optimized to prevent incorrect parameter settings of the chip.

PR Number GCRMS: 4526721CMM: SYED69813






33. There is a probability that the data rate negotiation for RRUs fails in ring topology.

Description In ring topology, there is a probability that the data rate negotiation for RRUs fails.

Cause In ring topology, the mechanism of data rate negotiation for RRUs has a time sequence problem. In this case, there is a probability that the mechanism for rate negotiation between two RRUs fails and the RRU ring turns into the RRU chain. As a result, the alarm RRU Network Topology Type and Configuration Mismatch (alarm ID: 26238) is reported.

Impact The ongoing services are not affected, but the alarm RRU Network Topology Type and Configuration Mismatch (alarm ID: 26238) is reported.

Severity Major

Solution The mechanism of data rate negotiation for RRUs is optimized to enhance the protection on time sequence.


DTS: DTS2010062800244

Test Case ID ATP: 2010062800244

34. There is a probability that the downlink channel of the WBBPb is abnormal.

Description There is a probability that the downlink channel of the WBBPb fails and the alarm Board Downlink Service Processing Channel Abnormal (alarm ID: 28301) is reported.

Cause The CPU of the WBBPb is in busy state and leads to a failed maintenance link of the downlink channel. In this case, the alarm Board Downlink Service Processing Channel Abnormal (alarm ID: 28301) is reported.

Impact The downlink channel is abnormal and the ongoing services are interrupted.

Severity Major

Solution The self-healing mechanism of the CPU in busy state is optimized.


DTS: DTS2010070500503





35. There is a large delay in reporting the Burglar Alarm (alarm ID: 25672).

Description There is a large delay in reporting the Burglar Alarm (alarm ID: 25672). As a result, the real-time performance of the door control system deteriorates and the security of the door control system is affected.

Cause The process of the generation and reporting of the Burglar Alarm (alarm ID: 25672) on the M2000 takes a long time.

Impact The security of the door control system is affected.

Severity Minor

Solution The mechanism of the Burglar Alarm (alarm ID: 25672) is optimized so that the delay in reporting of the alarm is shortened.


Test Case ID ATP- DTS2010081702657

36. Solving the problem that the expected result of running a Ping command for the NodeB is not returned on the M2000

Description When a Ping command is executed for a NodeB on the M2000, the expected result is not returned. That is, some information, such as Time To Live(TTL) and delay, is not returned.

Cause The Ping result packets reported by the NodeB to the M2000 do not meet the format requirement of the M2000.

Impact Running the Ping command for the NodeB on the M2000 does not return the expected result.

Severity Minor

Solution Fix the bug so that the format of the packets generated by the Ping command meets the requirement of the M2000.


DTS2010072803300






37. Solving the problem that the total HSDPA throughput does not exceed 63 Mbit/s when only one path and one WBBP are configured

Description When only one path is configured for HSDPA services and only one WBBP is configured at the NodeB, the total HSDPA throughput of the WBBP is lower than the actually supported transmission bandwidth.

Cause The WBBP of the NodeB incorrectly handles the maximum available bandwidth on the single path for HSDPA services.

Impact The total HSDPA throughput of multiple users cannot exceed 63 Mbit/s.

Severity Warning

Solution Correct the fault in processing the maximum available bandwidth of a single path.


CMM: SYED68232


38. The WRFU/SRRU reports the alarm RF Unit TX Channel Gain Out of Range (alarm ID: 26520).

Description When strong interference exists in the radio network, the RTWP is too high and there is a possibility that the WRFU/SRRU reports the alarm RF Unit TX Channel Gain Out of Range (alarm ID: 26520).

Cause The algorithm for troubleshooting a high RTWP has defects, leading to a low probability of the alarm RF Unit TX Channel Gain Out of Range (alarm ID: 26520). Generally, the alarm is cleared in two minutes. In certain cases, the WRFU/SRRU is reset due to overcurrent.

Impact The TX power is low when the alarm RF Unit TX Channel Gain Out of Range (alarm ID: 26520) is reported.

Severity Major

Solution The algorithm of alarm processing is modified.


DTS: DTS2010081201944





39. Solving the problem that the WRFU is reset at a low probability

Description When the WRFU is reset at a low probability, call drops occur. After the reset, services recover.

Cause The mechanism for detecting digital circle gain is improper.

Impact Call drops occur.

Severity Major

Solution Optimize the mechanism for detecting digital circle gain to avoid abnormal reset of the WRFU.


CMM: A17D30215


40. Solving the problem that the GSM BBU is disconnected from the dual-mode RRU at a low probability

Description When the dual-mode RRU is connected to both a UMTS BBU and a GSM BBU, the maintenance link between the RRU and the UMTS BBU is normal but that between the RRU and the GSM BBU is unavailable at a low probability.

Cause The algorithm is improper, leading to incorrect dual-RRU parameter configuration.

Impact The GSM baseband services processed by the dual-RRU are unavailable.

Severity Minor

Solution Correct the algorithm to ensure that the dual-RRU parameter configuration is correct.







41. Solving the problem that a NodeB cannot be selected on the M2000 client when pre-upgrade health check is performed on the NodeB

Description A NodeB cannot be selected on the M2000 client when health check is performed on the NodeB.

Cause The mediation of the NodeB is improper.

Impact The pre-upgrade health check cannot be performed on the NodeB. This does not affect the upgrade or services.

Severity Major

Solution Correct the configuration data about the pre-upgrade health check to ensure that the pre-upgrade health check on the NodeB is successful.



42. Solving the problem that the configuration files on the main control boards of a certain batch are occasionally corrupted after the base station is upgraded and then reset

Description After the base station is upgraded and then reset, the Configuration File Damaged (alarm ID: 26242) is occasionally generated on the main control boards of a certain batch.

Cause There is a bug in the file backup mechanism. That is, when the flash or the file system is abnormal, the configuration files cannot be recovered after being corrupted.

Impact The configuration data is lost. As a result, the base station fails to provide services.

verity Warning

Solution Optimize the file backup mechanism to ensure that the configuration data is reliable.


DTS:DTS2010082402300





43. Solving the problem that a logical cell is occasionally unavailable

Description A logical cell is occasionally unavailable, and therefore users in the cell cannot access the network.

Cause The robustness of the information exchange mechanism between the BBU and RRU is not strong enough. Therefore, during the RRU startup, the configuration information regarding the downlink frequency of a cell is not retransmitted after being lost. As a result, the logical cell is occasionally unavailable.

Impact The logical cell is occasionally unavailable, and therefore users in the cell cannot access the network. This problem can be rectified after the RRU is reset.

Severity Minor

Solution Improve the robustness of the information exchange mechanism between the BBU and RRU.


DTS: DTS2010082302182


44. Solving the problem that the NodeB is abnormally reset

Description The NodeB is abnormally reset when an error occurs during radio link reconfiguration.

Cause The protection mechanism for saving array is improper during radio link reconfiguration, which leads to array overflow and therefore NodeB reset.

Impact The NodeB is reset occasionally.

Severity Major

Solution Modify the array protection mechanism.







45. Solving the problem that a cell cannot be reestablished because an error indication message is not successfully reported

Description An error occurs during channel configuration on the baseband side but occasionally the error indication message cannot be reported. As a result, the NodeB fails to reestablish a cell.

Cause The mechanism for reporting error indication messages is defective.

Impact Users cannot access the network.

Severity Major

Solution Rectify the fault in the mechanism for reporting error indication messages.


DTS:DTS2010082703041

Test Case ID ATP-DTS2010082703041

46. The NodeB reports the alarm Board Uplink Service Processing Channel Abnormal (alarm ID: 4018). As a result, the alarm Local Cell Unusable is reported and then cleared after a while.

Description The NodeB reports the alarm Board Uplink Service Processing Channel Abnormal (alarm ID: 4018). The fault code is 19 (CPU-DSP EMAC Interface Link Abnormal). If the cell is set up on the broken DSP, the alarm Local Cell Unusable is reported and then cleared after a while.

Cause The DSP internal processing is abnormal. Therefore, there is a low probability that the DSP does not respond to the internal signals of the CPU.

Impact After the uplink DSP reports the alarm, the services of the cell are interrupted for 30s.

Severity Minor

Solution The DSP internal processing is optimized to solve the problem of the broken link between the CPU and the DSP.

PR Number CMM:DTS2010072803405





47. There is low probability that BBU board maintenance link fails.

Description There is low probability that BBU board maintenance link fails and the alarm BBU Board Maintenance Link Failure (alarm ID: 26205) is reported. Several minutes later, the alarm is automatically cleared.

Cause In the case of a large traffic volume, an error occurs in the controller on the WBBP with low probability.

Impact Services are affected, and resume several minutes later.

Severity Major

Solution Optimization is made to the processing in the controller in the CPU on the WBBP.


DTS: DTS2010092602067


48. The cell is unavailable due to PA overcurrent of the RF unit.

Description In the case of full-power transmission, the alarm RF Unit PA Overcurrent (alarm ID: 26524) is reported on the RF unit. PA overcurrent protection shuts down the PA and therefore the cell is unavailable.

Cause Parameter settings of the RF unit are incorrect, resulting in PA overcurrent.

Impact The cell is unavailable and the PA overcurrent alarm is reported on the RF unit.

Severity Major

Solution Parameter settings of the RF unit are corrected.

PR Number CMM: SYQD04837






49. The ALD scanning fails.

Description The MML command for ALD scanning on the LMT fails because the ALD scanning times out.

Cause The data flag of the ALD is not cleared, resulting in ALD scanning timeout.

Impact The ALD is unavailable.

Severity Major

Solution The data flag is cleared before ALD scanning.

PR Number CMM: BF5D01272


50. The alarm BBU CPRI Interface Error is reported.

Description There is a probability that the WRFU is reset abnormally during startup and the alarm BBU CPRI Interface Error (alarm ID: 26234) is reported. In this case, there is a probability that the WRFU cannot work properly.

Cause Parameter settings of the WRFU are incorrect. Therefore, there is a probability that the WRFU is reset during startup.

Impact There is a probability that the WRFU cannot work properly and the alarm BBU CPRI Interface Error (alarm ID: 26234) is reported.

Severity Major

Solution Parameter settings of the WRFU are corrected.






4.1.7 Improvements of V200R011C01SPC510 on V200R011C01SPC500

1. The BOOTP detection fails due to a long time of negotiation between the NodeB and the peer end.

Description The NodeB detects the MP and PPP transmission during the BOOTP detection. The BOOTP detection fails due to a long time of negotiation with the peer end.

Cause During the BOOTP detection, the NodeB waits for 12 seconds to detect the MP and PPP transmission. If the time of negotiation exceeds 12 seconds, the BOOTP detection fails.

Impact The BOOT detection fails, and the remote maintenance channel is faulty.

Severity Major

Solution The time of negotiation between the NodeB and the peer end is changed to 60 seconds.

PR Number CMM: DTS2010072600750







1. The ALM-1100 RET Antenna Maintenance Link Abnormal Alarm is reported at a site.

Description The ALM-1100 RET Antenna Maintenance Link Abnormal Alarm is reported at a site

Cause When the NodeB and RET antenna work in half-duplex mode, data reception and transmission are implemented through the CPU of the RF module. In this case, there is a low probability that the switching between data reception and data transmission is delayed.

Impact The ALM-1100 RET Antenna Maintenance Link Abnormal Alarm is reported when the NodeB is running properly. This affects user experience but has no impact on service running.

Severity Minor

Solution The RF module uses the new design. That is, data reception and transmission are implemented through the logic units, which can prevent the delay in switching.



2. Bandwidth of NodeB counter for physical port is 0

Description When setting physical port type as LOOPINTF, VS.IPDlTotal, VS.IPDlMaxUsed and VS.IPDlAvgUsed is all 0.

Cause LOOPINTF port has no its own bandwidth for it's a virtual port. When NodeB report counter for bandwidth of physical port, NodeB uses bandwidth of LOOPINTF port, so IPDlTotal is 0. IPDlMaxUsed and IPDlAvgUsed mean actually used bandwidth, they cannot be larger than IPDlTotal, so they are also 0.

Impact Wrong counter value makes it impossible to monitor throughput rate of physical port

Severity Minor

Solution NodeB uses bandwidth of actual physical port instead of the LOOPINTF port.

PR Number CMM:SYED67139





3. The baseband board is reset because of long-time CPU overload.

Description When the traffic is heavy, CPU overload is prone to occur. If the CPU overload lasts for a long time, the baseband board is reset.

Cause The processing efficiency of the baseband board is low. Therefore, CPU overload is prone to occur during heavy traffic.

Impact Call drops occur for a lot of users, which affects KPIs.

Severity Major

Solution When the CPU is overloaded, the frequency of status check is modified and the RNC link setup failure response is not returned.



4. When physical resources are insufficient, the error code UL RADIO RESOURCES NOT AVAILABLE is falsely reported as NODEB_RESOURCES_UNAVAILABLE.

Description When physical resources are insufficient, the error code UL RADIO RESOURCES NOT AVAILABLE is falsely reported as NODEB_RESOURCES_UNAVAILABLE.

Cause When the RRC setup fails, the NodeB reports NODEB_RESOURCES_UNAVAILABLE instead of UL RADIO RESOURCES NOT AVAILABLE. This leads to incorrect CE congestion statistics on the RNC side.

Impact Incorrect CE congestion statistics affect KPI analysis.

Severity Minor

Solution When the encoding resources or modulation resources are insufficient, only the error code UL RADIO RESOURCES NOT AVAILABLE is reported.







5. When upgrading software of LAN switch, NodeB transmission trouble occurs.

Description After the LAN switch connected to the NodeB is upgraded, the transmission of the NodeB is intermittent and the services in the cells are unstable.

Cause Ethernet port's status changes when upgrading the LAN switch. When the Ethernet goes down, the NodeB limit port sending ability 300K successfully, but when the Ethernet up, NodeB set 1000M fails because of the maximum ability is 300M. So when running time, transaction trouble occurs.

Impact The cell status changes between in-service and out-of-service, and the services in the cells are unstable.

Severity Major

Solution NodeB limits port's sending ability using NodeB maximum ability value as upper limit.



6. When the software of the NodeB is being upgraded, the reset of the main control board requires a long time. This leads to repeated activation of the baseband board.

Description When the software of the NodeB is being upgraded, the reset of the main control board takes a long time. This leads to repeated activation of the baseband board.

Cause When the activation of the NodeB software packet is complete, the baseband board is reset before the main control board is reset. During the resetting of the main control board, the operation logs and configuration file are updated. Therefore, if the operation of the file takes a long time because the system is busy, the resetting of the main control board takes more time. If the baseband board starts working normally at this time, the main control board activates the baseband to the previous version.

Impact There is a small probability of slow reset of the main control board during the NodeB upgrade. This leads to long-time version upgrade.

Severity Minor

Solution The operation sequence is changed. In this way, the time-consuming file update is performed before the baseband and then the main control are reset.






7. The NodeB is reset because of the CPU overload on the main control board.

Description The CPU overload occurs in high probability when traffic is heavy. If the CPU overload persists for a long time, the main control board is reset.

Cause The processing efficiency of the main control board is low.

Impact All the users under the NodeB experiences call drops, and KPIs are affected.

Severity Major

Solution Flow control is performed in case of CPU overload, regarding the connection setup requests in the RNC



8. When the jitter of the IP clock source is severe, the NodeB may report the alarm Reference Clock Source Abnormal (alarm ID: ALM-1008).

Description When the jitter of the IP clock source is severe, the time of switching between IP clock links is not dynamically adjusted according to the current filtering parameter and sampling period in the IP clock link algorithm. Therefore, the NodeB may report the alarm Reference Clock Source Abnormal (alarm ID: ALM-1008).

Cause When the jitter of the IP clock source is severe, the switching time of the IP clock links is not dynamically adjusted after the filtering parameter and sampling period in the IP clock link algorithm are adjusted. Therefore, the clock fails to be locked or the clock links are incorrectly switched.

Impact The alarm Reference Clock Source Abnormal (alarm ID: ALM-1008) is reported.

Severity Warning

Solution The IP clock link algorithm is changed. In this way, the switching time of the IP clock links can be dynamically adjusted according to the current filtering parameter and sampling period of the IP clock algorithm.







9. When EDCH channel setup, slot format which is configured by NODEB is different from UE which sends, it takes a longer time in PDP activation.

Description Configured slot format at NODEB is different from UE which sends before EDCH channel delay activation. UE always sends information about DCH channel, however, the NODEB decodes data according to the EDCH channel before COMMIT CFN, so it is inevitable to get an error result.

Cause Configured slot format at NODEB is different from UE which sends before EDCH channel delay activation, so channel estimation is incorrect, eight retransmission occurred.

Impact PDP activation for a longer time

Severity Warning

Solution During EDCH channel setup, demodulation parameters are not effective until COMMIT CFN at NodeB.



10. The AAL2 path on the RNC side reports the alarms.

Description Six AAL2 paths, three SAAL links, and one OMCH are set up on both the RNC side and NodeB side. After that, each path and link establishes its own F5 entity to check the link status. However, the AAL2 path No.3 on the RNC side reports the CC Active Failed Alarm (ID: 404 F5) and the Path Unavailable (ID: 1711).

Cause The setup of F5 entity on the OMCH and that on the AAL2 path are two different tasks. On the NodeB side, however, the ATM F5 module is not configured with the protection against incompatible signal during the setup or removal of F5 entities. Therefore, two different tasks of setting up F5 entities at the same time leads to the disordered global data of F5 entities. As a result, the AAL2 path reports the CC Active Failed Alarm (ID: 404 F5).

Impact The RNC reports the CC Active Failed Alarm (ID: 404 F5), and the AAL2 path No. 3 fails to be activated. There is no other impact. Only the transmission alarm is displayed.

Severity Warning

Solution The codes of the ATM F5 module on the NodeB side for setting up and deleting F5 entities are modified, and the feature of protection against incompatible signal is added.






11. A Board Uplink Service Processing Channel Abnormal alarm is generated on the NodeB. The error code is 14 (CHIP Register Configuration Abnormal).

Description A Board Uplink Service Processing Channel Abnormal alarm is generated on the NodeB. The error code is 14 (CHIP Register Configuration Abnormal).

Cause The generation mechanism of the alarm is improper.

Impact After the uplink DSP reports the alarm, the services of the cell are interrupted for 4 to 5s.

Severity Major

Solution Modify the generation mechanism of the alarm.

PR Number CMM:SYED 68656


12. The alarm GPS Receiver Position Not Locked (ID: 1407) is reported.

Description When the user runs the DSP NGRU MML command to query the position information of the GSP reference receiver, the alarm GPS Receiver Position Not Locked (ID: 1407) is reported.

Cause The information of longitude and latitude automatically searched by the GPS reference receiver is in the unit of degree. However, the information is displayed in the format of degree/minute/second in the DSP NGRU packet, and has an accuracy to only second. This fails to meet the accuracy requirements of the GSP reference receiver.

Impact The information of the longitude and latitude of the NodeB is incorrect, and the alarm GPS Receiver Position Not Locked (ID: 1407) is reported.

Severity Warning

Solution The information of longitude and latitude automatically searched by the GPS reference receiver is in the unit of degree. The packet displayed on the MML interface directly displays the information in degree, and the conversion to the degree/minute/second format is not performed.







13. The release notes document does not provide the description about the following problem: When a two-antenna cell and a four-antenna cell coexist in a NodeB, the CEs consumed by the NodeB are overcounted.

Description The release notes document does not provide the description about the following problem: When a two-antenna cell and a four-antenna cell coexist in a NodeB, the CEs consumed by the NodeB are overcounted.

Cause The description about the preceding problem fails to be included in the release notes for the NodeB of V200R011C01.

Impact The description about the preceding problem cannot be found in the release notes.

Severity Warning

Solution The description about the preceding problem is added to the section "Improvements of V200R011C01 on V200R011C01SPC200" in the release notes.



14. Some counter IDs are incorrect in BTS3900-BTS3900A-BTS3900L-DBS3900 WCDMA V200R011C01SPC200 Performance Counter Changes.xls.

Description Some counter IDs are incorrect in BTS3900-BTS3900A-BTS3900L-DBS3900 WCDMA V200R011C01SPC200 Performance Counter Changes.xls.

Cause The IDs of some counters are incorrect.

Impact Performance statistics cannot be obtained based on the counter IDs.

Severity Warning

Solution In BTS3900-BTS3900A-BTS3900L-DBS3900 WCDMA V200R011C01SPC500 Performance Counter Changes.xls, the counter IDs in the V200R011C01SPC200 sheet are rectified.






15. The WRFU connected to optical port 1 on any WBBPd is reset repeatedly.

Description When a NodeB is configured with more than one WBBPd, the WRFU connected to optical port 1 on any WBBPd is reset repeatedly, and therefore the Local Cell Unusable alarm (alarm ID: 28203) is generated repeatedly. After the NodeB is reset, the problem disappears.

Cause There is an error in reading the electronic serial number of the connected WRFU, and therefore the NodeB issues a reset command to the WRFU.

Impact Services are affected.

Severity Major

Solution Optimization is made in a way that the NodeB does not issue a reset command to the WRFU when the NodeB detects that the electronic serial number of a WRFU changes.



16. The decrease of RRC connection success ratio on WBBPd due to not correctly dealing with uplink time slices resources.

Description To solve the problem of the decrease of KPI value (RRC connection success/failure ratio) when Board D runs for a period of time, due to not correctly dealing with uplink time slice resources.

Cause When the communication traffic capacity reaches some degree, RRC connection failure will occur due to uplink channel demodulation failures caused by the improper treatment with time slice resources.

Impact When the problem triggers, the KPI value will decrease for some degree.

Severity Major

Solution Make some modifications to the treatment of uplink time slice resources and it will make sure that uplink channel can be demodulated correctly.







17. The failure access on WBBPd occurs because of the abnormal interruption among DSP tasks.

Description The failure access on WBBPd occurs because of the abnormal interruption among DSP tasks.

Cause When multi DSP tasks are configuring the ASIC at the same time, and meanwhile if the abnormal interruption among DSP tasks is occurred, the ASIC will be written out of range. Then the ASIC deals with the public channel incorrectly, and the failure access occurs.

Impact User access fails at interrupted ASIC when the problem is triggered with a very low rate.

Severity Major

Solution Modifications are made to the scheduled mechanism of DSP tasks on WBBPd.




1. The RF Unit RX Channel RTWP/RSSI Too High alarm (Alarm ID: 26523) is disabled but it is still described in the alarm online help

Description The RF Unit RX Channel RTWP/RSSI Too High alarm (Alarm ID: 26523) is disabled but it is still described in the alarm online help.

Cause This alarm may be a false alarm and cannot help identify the interference effectively. In addition, this alarm is frequently reported after the software upgrade so the OM on the base station is affected. To solve this problem, this alarm is disabled. The alarm online help, however, still contains descriptions about this alarm.

Impact The alarm is disabled but it is still described in the alarm online help.

Severity Minor

Solution Descriptions about the RF Unit RX Channel RTWP/RSSI Too High alarm (Alarm ID: 26523) are removed from the alarm online help.






2. In RRU hot backup mode, UEs cannot access the cell.

Description The success rate of RRC connection setup becomes low after the NodeB is upgraded from V200R011C00SPC110 to V200R011C01.

Cause When the BBU sends the hot backup command, the hot backup mode does not take effect on the RRU. Thus, the configuration inconsistency exists between the BBU and the RRU, resulting in the RRC connection setup failure.

Impact UEs cannot access the cell. The ongoing services are interrupted.

Severity Major

Solution After the NodeB software is upgraded to V200R011C01SPC400, the hot backup mode takes effect on the RRU when the RRU receives the hot backup command from the BBU.



3. The reported RTWP at cell level of the mRRU (RRU3805) and MRFU is inconsistent with the theory value.

Description The reported RTWP at the cell level of the mRRU (RRU3805) and MRFU is incorrect and is inconsistent with the theory value.

Cause The channel gain calculation formula is incorrect. The formula does not consider the batch difference of the module channel gains and the channel gain discrete compensation.

Impact The services are not affected. The actual value of the RTWP at the cell level is inconsistent with the theory value.

Severity Minor

Solution The batch difference of the channel gains is added to the compensation range for the calculation formula of the RTWP at the cell level.




None






None


None


None


None


None


None

4.1.17 Improvements of V200R011C01SPC010 on V200R011C01None




4.1.18 Improvements of V200R011C01 on V200R011C00SPC2001. When a two-antenna cell and a four-antenna cell coexist in a NodeB, the CEs

consumed by the NodeB are overcounted.

Description The NodeB can be configured with only one antenna mode (two- or four-antenna configuration). When a two-antenna cell and a four-antenna cell coexist in a NodeB, the CEs consumed by the NodeB are overcounted because the two-antenna cell consumes CEs in four-antenna mode.

Cause The NodeB only allows site-level antenna configuration. If a four-antenna cell is configured, the NodeB has to operate in four-antenna mode. Therefore, the two-antenna cell in the NodeB consumes CEs in four-antenna mode.

Impact When a two-antenna cell and a four-antenna cell coexist in a NodeB, the CEs consumed by the NodeB are overcounted.

Severity Minor

Solution The implementation scheme is improved. The customer is allowed to set the antenna mode based on the uplink resource group. Cells of different antenna modes are configured in the corresponding resource groups. Thus, CE consumption can be calculated accurately.








1. UE suffers 8-times ReTx when the UE's EDCH data is later than scheduling time

Description In normal case, when UE choose the Tbsize which could not be demodulated by NodeB, a compelling ACK should be sent to UE. However, in some cases, when UE's data could not be demodulated timely, a wrong timing relationship exited which could cause the compelling ACK send failure.

Cause A timing wobbling within NodeB could cause calculation error in HICH timing. In this condition the sending of ACK signal from NodeB to UE could not satisfy the timing relationship, which could cause 8-times ReTX of UE on physical layer.

Impact The failure in sending ACK single could cause 8-times ReTX of UE on physical layer.

Severity Minor

Solution The method of timing calculation for HICH is to be modified to make sure the sending of ACK signal satisfied the timing relationship when the NodeB exists a timing wobbling.

PR Number SYED62087


2. The NodeB reports the System Exceed Capacity Limit of License alarm frequently.

Description After the NodeB enables the dynamic CE switch, the System Exceed Capacity Limit of License alarm (ID: 4021) is frequently reported if the number of actually used license CEs is greater than the value specified by the license.

Cause After the NodeB enables the dynamic CE switch, the NodeB detects the System Exceed Capacity Limit of License alarm (ID: 4021) every three seconds. The detection interval is very short, which leads to the frequent reporting of the alarm when the alarm reporting conditions are met.

Impact The alarm is frequently reported.

Severity Minor

Solution The detection interval of this alarm is changed to five minutes.

PR Number SYED60261





3. For HSDPA and HSUPA services, the call drop rates increase at some sites. The call drop rate of HSUPA is over 30%.

Description For HSDPA and HSUPA services, the call drop rates increase at some sites. The call drop rate of HSUPA is over 30%.

Cause If the NodeB admits multiple users and the load is high, an error occurs when the uplink processing unit is transferring data. The error leads to the abnormal update of the user searching information, thus resulting in call drops.

Impact For HSDPA and HSUPA services, the call drop rates increase.

Severity Minor

Solution The software of the uplink processing unit is modified, where data transfer by the uplink processing unit is optimized. This prevents abnormal update of the user searching information.

PR Number SYED59343


4. The RR scheduling algorithm cannot guarantee the rate fairness among multiple HSDPA users.

Description If the RR scheduling algorithm is used in the RAN and the cell has more than one HSDPA user, the rate fairness among the HSDPA users cannot be guaranteed. That is, under the same condition, the users scheduled earlier have higher data rate than those scheduled later.

Cause The RR scheduling takes into account only the fairness among scheduled users, without considering the fairness in cell resource allocation. In this case, the user admitted earlier preferentially obtains the cell resources whereas the user admitted later obtains only the remaining resources.

Impact When the RR scheduling algorithm is used in the RAN, the rate fairness among multiple HSDPA users in one cell cannot be guaranteed. The users admitted later have lower data rate than those admitted earlier.

Severity Major

Solution The RR scheduling algorithm is improved to ensure the fairness in cell resource allocation among multiple HSDPA users in one cell.

PR Number SYED60589






5. The modification of the TRLFAILURE parameter may lead to sharp decline of the RRC connection setup success rate.

Description Modification of the TRLFAILURE parameter of the logical cell may lead to sharp decline of the RRC connection setup success rate for the NodeB. This occurred at a site in Australia.

Cause When the signaling modules process the TRLFAILURE parameter modification in specific conditions, memory overflow may occur in the codes. This leads to faults in release of the link resources. That is, the remaining invalid users occupy most of the resources, which results in the decline of the RRC connection setup success rate.

Impact The RRC connection setup success rate declines.

Severity Minor

Solution The problem of memory overflow in the signaling module for processing the TRLFAILURE parameter modification is solved.

PR Number SYED61588


6. During board active/standby switchover, the system does not prompt the user that the switchover leads to NodeB resetting or service disruption.

Description When the SWP BRD command is executed on the LMT to switch over the main control board, the system only prompts the user that "Are you sure to Swap Board?" The system does not provide necessary information on the switchover, which leads to NodeB resetting.

Cause The impact of running the SWP BRD command is not provided.

Impact If the main control board is switched over, the NodeB is reset. If the UTRP is switched over, the service may be interrupted.

Severity Minor

Solution A dialog box prompting "Swapping Board will reset board, are you sure to continue?" is added during the execution of the SWP BRD command. In addition, the information of "The swapping of the WMPTs will reset NodeB, and that operation on UTRPs will probably cause service to be interrupted." That is, the impact of running this command is added in the MML Online Help.

PR Number SYED60986





7. A NodeB reports the Board Uplink Service Processing Channel Abnormal alarm.

Description A NodeB reports the Board Uplink Service Processing Channel Abnormal alarm (Alarm ID: 4018). The probability of generating this alarm is very low, and the alarm is cleared very quickly.

Cause This alarm is reported because a signal used in the uplink processing unit of the NodeB is accidentally lost.

Impact The alarms are affected, with small impact on services.

Severity Major

Solution Modify the DSP software to prevent signal loss in the uplink processing unit.

PR Number SYED61136


8. The RL SETUP fails when CDT tracing is enabled.

Description The RL SETUP success rate of cell 33011 dropped between 2009-5-27 13:00:00 and 2009-5-27 16:00:00.

The counters VS.RRC.Rej.RL.Fail and RLM.FailRLSetupIub.Cong indicate that RL SETUP failures occurred in cell 33011 during that period.

Cause The NodeB operation record indicates that CDT tracing is enabled between 2009-5-27 13:00:00 to 2009-5-27 16:00:00 at site 3301. The CDT tracing consumes the WMPT CPU when the CPU usage is reaching the threshold (75%), which leads to WMPT CPU overload. The CDT tracing is not disabled immediately because of the software bug in WMPT CPU flow control. In this case, some received RL SETUP requests are rejected in order to protect the system.

Impact The RL SETUP success rate drops when CPU is busy.

Severity Minor

Solution Enhance the CPU flow control function. This ensures that the CDT tracing is disabled immediately when the CPU overload occurs. In addition, the CDT tracing cannot be enabled in the case of CPU overload.

PR Number SYED61477






9. The HSDPA throughput decreased to tens of kilobits per second in pre-versions.

Description The HSDPA throughput decreased to less than 100 kbps in pre-versions.

Cause A signaling message in the NodeB changes in the RAN10.0 version. The HSDPA parameters of the downlink DSP are reconfigured during the link reconfiguration. This leads to a defect in the packet loss detection of the downlink DSP. That is, multiple packet losses are detected when actually there is no packet lost. Therefore, the NodeB throughput decreases in adaptive flow control mode.

Impact The HSDPA throughput decreases to tens of kilobits per second.

Severity Major

Solution When the switching time arrives, the current FSN is reserved in PING variable.

PR Number SYED60016


10. UPA RAB cannot be set up

Description On some of UEs, such as Huawei E272. The RB cannot be set up after the reconfiguration failure until the UE restarts.

Cause In versions earlier than RAN11.0, the messages of multiple links are responded during the code tree reorganization. To avoid this problem occurring in RAN11.0, the NodeB decides not to respond with the link messages on the Iub interface if the optional cells are not changed. In this case, problems are triggered because of the defects in the earlier versions of certain UEs, such as Huawei E272.

Impact The RB reconfiguration fails for the earlier versions of certain UEs, such as Huawei E272. In addition, the RB cannot be set up after the reconfiguration failure until the NodeB restarts.

Severity Major

Solution The NodeB rolls back to the version matching with the RAN10.0. In this case, optional cells can be carried in the RL response messages. The problem of the messages of multiple links responded with during the code tree reorganization is solved in the RNC of the version matching with the V200R011C00SPC120.

PR Number SYED60896





11. The NCP/CCP link is broken because of the limit rate of the physical port

Description Because of the HSUPA arithmetic, when the transmit network losing some packet, the arithmetic will drop the limit rate of the IUB physical port. This limit rate leads to lots of packets lost in the NodeB, and even broken NCP/CCP in severe cases.

Cause When the PRI of sig and R99 IP path are the same, because of the limit rate, the NCP/CCP sig packet is lost in the NodeB. This leads to the fact that the NCP/CCP is broken.

Impact NCP/CCP down and the KPI of this NodeB is poor.

Severity Major

Solution Mod the HSUPA arithmetic that will never drop the limit rate of the IUB physical port.

PR Number SYED61027


12. When the SRB over HSUPA is enabled, the HSUPA service access may occasionally fail due to the QAAL2 MOD FAIL message returned by the NodeB.

Description The test result finds that the HSUPA service access may occasionally fail due to the QAAL2 MOD FAIL message returned by the NodeB when the SRB over HSUPA is enabled.

Cause When the SRB over HSUPA is enabled, the RRC connection of the service is set up on the R99 channel. By default, the NodeB allocates resources to the H-type board. When the UPA service is set up upon receiving the RL RECFG message, the resources must be transferred to the E-type board because what is to set up is the SRB over HSUPA service, which belongs to the UPA service. During the resource transferring, no other operations are allowed in the NodeB. Therefore, when the RNC sends the QAAL2 MOD message to the NodeB during the resource transferring, the NodeB responds with the QAAL2 MOD FAIL message.

Impact The success rate for the HSUPA service access decreases when the SRB over HSUPA is enabled.

Severity Major

Solution Modify the codes to allow QAAL2 MOD operations during the resource transferring.

PR Number SYED60388






13. The HSDPA rate is low at the site in FE networking.

Description At the site adopting the FE networking, the HSDPA rate is very low if the HSDPA is established on the IP path with the DSCP value ranging from 0 to 7.

Cause If the DSCP value of the IP path ranges from 0 to 7, and the IP path is configured to the non-fully-sharing bandwidth mode, the queue values defined in APP and that in the BSP are inconsistent. This results in the failure in the high layer to obtain the correct traffic information of this IP path and only 100 kbit/s reserved bandwidth is assigned to the HSDPA users on this IP path. In such a case, the actual rates of the HSDPA users are very low.

Impact The HSDPA rate is very low at the site in FE networking.

Severity Major

Solution Modify the software to ensure that the queue values of the IP path used in the high layer and low layer are the same.

PR Number SYED59376


14. Numerous core files are generated on the M2000, which leads to insufficient space on the M2000.

Description A core file of 8 MB is generated every time the NodeB configuration is synchronized. Too many core files slow the maintenance of the M2000.

Cause The maximum number of the Ethernet ports configured for the board defined by the MMLSPY tool is inconsistent with that in the software, which leads to the memory copy overflow.

Impact The maintenance of the M2000 is slowed.

Severity Major

Solution Modify the MMLSPY Mediation tool to ensure that the specifications in the tool are consistent with those in the NodeB software.

PR Number SYED59704





15. In the scenario of the Iub interface configured with the VLAN group, the FP synchronization on the cell common channel fails.

Description In the scenario of the Iub interface configured with the VLAN group, the FP packet of the user plane does not tag VLAN. This leads to the FP synchronization on the cell common channel fails, and cells cannot be set up.

Cause The APP determines whether to configure the VLAN information for the BSP based on the VLAN tag in the VLANMAP configuration data. The field of VLAN tag, however, is invalid if VLAN groups are configured. In this case, the VLAN information sent by the high layer to the lower layer is incorrect and the packet does not tag the VLAN.

Impact The FP synchronization on the cell common channel fails and cells cannot be set up.

Severity Major

Solution Modify the software. This ensures the field is read only in the case of a single VLAN that is configured instead of the VLAN group.

PR Number SYED59596






16. Window shift errors occur with a probability of 0.3% during the search without knowing the delay TP.

Description The number of pilots of the ASIC is not properly configured, which leads to a 0.3% probability of window shift errors occurring during the search without knowing the delay Transmission Propagation (TP). This, then, results in call drops.

Cause For the SRB over HSUPA, the timeslot format is configured to 1 and the corresponding number of pilots is 8 in non-compressed mode. The maximum number of pilots for searching without knowing the TP in actual application is 6 because of restrictions on time slice resources. The correlation length is equal to the smaller value between the corresponding number of pilots and the actual number of pilots. Therefore, the correlation length is 6.

In software implementation, the maximum number of pilots for searching without knowing the TP is set to 8, which is inconsistent with the actual correlation length. This leads to errors in non-coherent accumulation, which causes generation of virtual fingers. The virtual fingers further result in call drops because of ALPHA window shift errors.

Impact The probability of window shift errors occurring because of virtual fingers generated during the search without knowing the TP increases.

Severity Minor

Solution Modify the software and properly configure the chip. This ensures normal search without knowing the TP.

PR Number SYED59662





4.1.20 Improvements of V200R011C00SPC100 on V200R011C001. The RTWP measured in real time on the NodeB side is inconsistent with that

reported on the RNC side.

Description The RTWP value measured on the NodeB side is increased by 10 dB after the setting of RF desensitization through the following command: SET RFDESPARAM: SRN=22, SN=0, RFDS=10.

The RTWP reported on the RNC side, however, is unchanged. That is, the RTWP reported on the RNC side is 10 dB lower than that reported on the NodeB side, which leads to inconsistency in the RTWP values on the two sides.

Cause The system design does not consider the impact of the RF desensitization on the RTWP reported by the NodeB to the RNC.

Impact This problem affects the RNC's control of both the number of admitted users and the UPA service.

Severity Major

Solution Add the gain due to RF desensitization to the RTWP reported on the RNC side.


CMM: SYED54664


4.1.21 Improvements of V200R011C00 on V200R010C01B0531. BBU emulation frames do not appear abnormal when pulled out the CPRI TX

port

Description BBU emulation frames do not appear abnormal when pulled out the CPRI TX port.

Cause Pull out the TX port and logic Unit cannot detect the CPRI PLL appear.

Impact Emulation frames do not work properly.

Severity Major

Solution FPGA drive notice OM that the CPRI is abnormal as soon as error (LOS LOF RAI) appears.

PR Number SYED55770

Test Case ID None





4.2 Unsolved ProblemsNone




5 Precautions

5.1 Precautions for BTS3900-BTS3900A-BTS3900L-DBS3900 WCDMA V200R011C01SPC752

No. Item Description

1 Time restriction None

2 Place/site restriction

Kazakstan Kar-tel.

3 Other restrictions None

4 Version termination

Replaced by a higher version according to the subsequent version policies.




6 Related Documents

The documents for this release are delivered with the software package. Huawei engineers can obtain these documents by downloading the software package and deliver them to the customer.



BTS3900-BTS3900A-BTS3900L-DBS3900 WCDMA V200R011C01SPC752 Release Notes.doc

Documents

Transcript of BTS3900-BTS3900A-BTS3900L-DBS3900 WCDMA V200R011C01SPC752 Release Notes.doc