Wcdma Nodeb Release Notes(Dbs3800 v100r009c01b053)

7/31/2019 Wcdma Nodeb Release Notes(Dbs3800 v100r009c01b053)

http://slidepdf.com/reader/full/wcdma-nodeb-release-notesdbs3800-v100r009c01b053 1/83

E

Release Notes

WCDMA NodeB(DBS3800)V100R009C01B053

Issue 01

Date 2008-06-03

HUAWEI TECHNOLOGIES CO., LTD.



Huawei Technologies Co., Ltd. provides customers with comprehensive technical support and service.

Please feel free to contact our local office or company headquarters.

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]

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

No part of this document may be reproduced or transmitted in any form or by any means without prior written

consent of Huawei Technologies Co., Ltd.

Trademarks and Permissions

and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.

All other trademarks and trade names mentioned in this document are the property of their respective

holders.

Notice

The information in this document is subject to change without notice. Every effort has been made in the

preparation of this document to ensure accuracy of the contents, but all statements, information, and

recommendations in this document do not constitute the warranty of any kind, express or implied.

Issue 01 (2008-06-03) Huawei Proprietary and Confidential of 83

http://www.huawei.com/

mailto:[email protected]

http://www.huawei.com/

mailto:[email protected]



WCDMA NodeB(DBS3800) V100R009C01B053

Release Notes

About This Document

Author

Prepared by Yu Panfeng, Li Xingzhong, Feng

Bicheng, Ren Wei, Xu Xuhua,

Liu Wei,Ye Shixin

Date 2008-05-22

Reviewedby

Liang Zhong, Jin Zhi, Ding Yong,

Chen Yunming, Yu Panfeng, RenWei, Fang Xiang

Date 2008-05-26

Approvedby

Ye Shixin Date 2008-06-03

SummaryRead this release notes before using the DBS3800 V100R009C01. This document includes the

following contents.

Chapter Details

Chapter 1 Version Matching Describes the version mapping of DBS3800

V100R009C01B053

Chapter 2 Compatibility Notes Describes the compatibility notes (Flash and BootROM)

of DBS3800 V100R009C01B053

Chapter 3 New Features Describes the modification of feature, MML, ALARM of the different DBS3800 V100R009 version

Chapter 4 Feature Summary Describes the feature summary, command line and performance counter of the different DBS3800

V100R009 version

Chapter 5 Fixed Bugs and

Known Anomalies

Describes the Bugs fixed and known anomalies of the

different DBS3800 V100R009 version.

Chapter 6 Notes and Cautions Describes notes and cautions of the different DBS3800

V100R009 version

Chapter 7 Related Documents Describes related documentation of the DBS3800


http://var/www/apps/conversion/current/tmp/scratch_4/???????(??).doc#Chapter1









Release Notes

Chapter 8 Technical Support Describes how to get technical support

History

Issue

Details Date Author Approvedby

01 First issue 2008-06-03 Yu Panfeng, LiXingzhong, Feng

Bicheng, Ren Wei, Xu

Xuhua, Liu Wei,YeShixin

Yeshixin





Release Notes

Contents

1 Version Matching............................................................................8

1.1 Product Version........................................................................................................................................................8

1.2 Software Version......................................................................................................................................................8

1.3 Related Product Version ............................................................................................................................... ......... .9

1.4 Functional Module Version......................................................................................................................................9

2 Compatibility Notes......................................................................11

2.1 Compatibility with History Product Versions...................................................................................................... ..11

2.2 Compatibility with History BootROM Versions...................................................................................... ......... ....12

3 New Features...............................................................................14

3.1 V100R009C01B053..............................................................................................................................................14

3.1.1 New Features................................................................................................................................................ ...14

3.1.2 Optimized Features..........................................................................................................................................15

3.1.3 Deleted Features.......................................................................................................................................... ....15

3.1.4 Changes in MML.............................................................................................................................................15

3.1.5 Changes in Alarms...........................................................................................................................................16

3.1.6 Changes in Performance Counters...................................................................................................................16

3.2 V100R009C01B052SPH001.................................................................................................................................16

3.2.1 New Features................................................................................................................................................ ...16



3.2.4 Changes in MML.............................................................................................................................................17

3.2.5 Changes in Alarms...........................................................................................................................................173.2.6 Changes in Performance Counters...................................................................................................................17

3.3 V100R009C01B052..............................................................................................................................................17

3.3.1 New Features................................................................................................................................................ ...17


3.3.3 Deleted Features......................................................................................................................................... .....18

3.3.4 Changes in MML.............................................................................................................................................19



3.4 V100R009C01B051..............................................................................................................................................19

3.4.1 New Features................................................................................................................................................ ...19





Release Notes


3.4.3 Deleted Features......................................................................................................................................... .....20

3.4.4 Changes in MML.............................................................................................................................................20



3.5 V100R009C01B050..............................................................................................................................................21

3.5.1 New Features............................................................................................................................................... ....21



3.5.4 Changes in MML.............................................................................................................................................24

3.5.5 Changes in Alarm................................................................................................................................... .........24

3.5.6 Changes in Performance Counter....................................................................................................................24

4 Feature Summary.........................................................................25

4.1 Feature List......................................................................................................................................................... ...25

4.1.1 V100R009........................................................................................................................................................25

4.1.2 V100R008........................................................................................................................................................25

4.1.3 V100R007........................................................................................................................................................26

5 Fixed Bugs and Known Anomalies..................................................29

5.1 V100R009C01B053..............................................................................................................................................29

5.1.1 Fixed bugs.......................................................................................................................................................29

5.1.2 Known Anomalies.................................................................................................................................. .........37

5.2 V100R009C01B052SPH001.................................................................................................................................38

5.2.1 Fixed Bugs.......................................................................................................................................................38

5.2.2 Known Anomalies.................................................................................................................................. .........38

5.3 V100R009C01B052..............................................................................................................................................39

5.3.1 Bugs fixed........................................................................................................................................................39

5.3.2 Known Anomalies.................................................................................................................................. .........70

5.4 V100R009C01B051..............................................................................................................................................70

5.4.1 Fixed Bugs.......................................................................................................................................................70

5.4.2 Known Anomalies.................................................................................................................................. .........74

6 Notes and Cautions.......................................................................777 Related Documents.......................................................................78

8 Technical Support.........................................................................79

8.1 Support.huawei.com..............................................................................................................................................79

8.2 Technical Support Hotline........................................................................................................................... ......... .79

Figure 1.1 Acronyms and Abbreviations.............................................80





Release Notes

Tables

Product version.................................................................................8

Software version................................................................................8

Related product version.....................................................................9

Functional module version..................................................................9

Compatibility with history product versions.......................................11

History BootROM versions................................................................12

Main new features in the V100R009..................................................25

Main new features in the V100R008..................................................25

Main features in the V100R007.........................................................26

Notes and cautions for the DBS3800 V100R009C01B053.....................77





Release Notes

1.3 Related Product Version

Figure 1.3 Related product version

RelatedProduct

Version Remarks

RNC BSC6800V100R008C01B050 and later versions Only supporting features

in UMTS6.0

BSC6810V200R009C01B072 and later versions Only supporting features

in UMTS6.1

M2000 iManagerM2000V200R003C01B061SP02 and later

versions

Only supporting features

in UMTS5.1

iManagerM2000V200R005C01B012 and later

versions

Only supporting features

in UMTS6.0

iManagerM2000V200R006C01B060SP03 and later versions

Only supporting featuresin UMTS6.1

CME WRAN CME V100R003C01B093SPC001 None

1.4 Functional Module Version

Figure 1.4 Functional module version

FunctionalModule

Version Remarks

DBS3800 Product DBS3800 V100R009C01B053 None

Flash DBS3800 V100R009C01B053 None

BootROM DBS3800 V100R009C01B052 None

LMT BBU3806-BBU3806C V100R009C01B053 None

CME BPL WRAN CME (DBS3800 V100R009C01B053 BPL) NoneM2000 Mediation iManagerM2000_DBS3800_MATCH_ENG_V200R0

05C01B053

BBU3806

iManagerM2000_DBS3800_MATCH_ENG_V200R0

05C01B054

BBU3806C





Release Notes

Note

The CME BPL (Borland Package Library) is a component of CME, released with the version of the NodeB. Each CME BPL corresponds to only one version of the NodeB.. The CME BPL supports the dataconfiguration on the NodeB of the matched version. Before installing the CME BPL, ensure that the CME

of the version listed in the matched list is already installed. When installing the CME BPL, refer to the

upgrade guide released with the CME BPL.





Release Notes

2 Compatibility Notes

This chapter introduces the following information:

Compatibility of the DBS3800 V100R009C01B053 with history versions of the product,

NE software and board software

Board software versions compatible with the NE software

2.1 Compatibility with History ProductVersions

2.1 lists the compatibility with history product versions. If the NodeB current version is not any

version in this table, please upgrade the NodeB to any version of this table first.

Figure 1.5 Compatibility with history product versions

Product Version ReleaseDate

Remarks

DBS3800

V100R009C01B052SPH0012008-04-21

Compatible with the earlier versions

excluding new features

DBS3800 V100R009C01B052 2008-04-10



DBS3800 V100R009C01B051 2008-03-03Compatible with the earlier versions


DBS3800

V100R009C01B050SPC0032008-04-15



DBS3800V100R009C01B050SPC002

2008-03-12Compatible with the earlier versionsexcluding new features

DBS3800V100R009C01B050SPC001






Release Notes

DBS3800V100R009C01B050SPH001




DBS3800

V100R008C01B072SPC0022008-02-29



DBS3800

V100R008C01B072SPC0012008-01-25



DBS3800

V100R008C01B072SPH0022008-01-25



DBS3800

V100R008C01B072SPH0012008-01-07



DBS3800 V100R008C01B072 2008-01-04 Compatible with the earlier versionsexcluding new features

DBS3800V100R008C01B062SPC001


DBS3800V100R008C01B062SPH001




2.2 Compatibility with History BootROMVersions

2.2 lists the compatibility with history BootROM versions. If the NodeB current version is not

any version in this table, please upgrade the NodeB to any version of this table first.

Figure 1.6 History BootROM versions

BootROM Version Upgrade

Requirement

Remarks

DBS3800 V100R009C01B052 No No need to upgrade the BootROM



DBS3800 V100R008C01B072 Yes Need to upgrade the BootROM, and after





Release Notes

the NodeB using the BootROM packagereleased with the version

V100R009C01B053 is upgraded, the

BootROM version will be

V100R008C01B052.

DBS3800 V100R008C01B050 Yes





Release Notes

3 New Features

This chapter highlights new features of different versions of the WCDMA NodeB DBS3800.

3.1 V100R009C01B053

3.1.1 New Features

Supporting ANDREW E15S08P14 TMA and Powerwave7033.00RCU.

Descriptionof theFeature

Supporting ANDREW E15S08P14 TMA and Powerwave7033.00 RCU.

Effect of Improvement

Newly-added RCU: Powerwave7033.00 RCU

Newly-added TMA: ANDREW E15S08P14 TMA (as non-AISG TMA)

Implementation

Distribute special HDLC address 0x08 to the special Powerwave7033.00

RCU, and send special handshake mode with the ANDREW E15S08P14TMA.

RelatedOperations

Run the ADD ALD command to configure the Powerwave7033.00 RCU.

TestDescription

Run the ADD ALD command to configure the RCU, and then check whether the NodeB can control the RCU.

PR Number CR-NMN-255





Release Notes

Adding the TREELNKPVC label and TSCROSS label and indicatethe NodeB name to which the PVC belongs.

Description

of theFeature

Adding the TREELNKPVC label and TSCROSS label and indicating the

NodeB name to which the PVC belongs.


Indicating the NodeB name to which the PVC belongs

Implementation

The parameter DESCRI is added in the ADD TREELNKPVC and ADD

TSCROSS commands.

RelatedOperations

Run the ADD TREELNKPVC or ADD TSCROSS command.

TestDescription

Run the ADD TREELNKPVC or ADD TSCROSS command, and then enter the parameter DESCRI.

PR Number CR-SEG-240

3.1.2 Optimized Features

None.

3.1.3 Deleted Features

None.

3.1.4 Changes in MML

V100R009C01B053 compared with the V100R009C01B052

MML Change


MML Change


MML Change






Release Notes

MML Change


MML Change

3.1.5 Changes in Alarms


Al armChange


Al armChange


Al armChange


Al armChange


Al armChange

3.1.6 Changes in Performance Counters None.

3.2 V100R009C01B052SPH001

3.2.1 New Features

None.





Release Notes


None.

3.2.3 Deleted Features None.


None.


None.

3.2.6 Changes in Performance Counters None.

3.3 V100R009C01B052

3.3.1 New Features

License control enabled

Description of the Feature

From this release, license control of the NodeB is enabled.

Effect of

Improvement

For the NodeBs in which license control is enabled, there is no impact on the

service.

For the NodeBs in which license control is not enabled, the license control

function is enabled automatically after the NodeB is upgraded to this

release. The originally-supported features before upgrade are still supported, but the features supported in new release are controlled by license.

If license control is enabled, the default CE number is 16. Users must

distribute licenses for newly-installed NodeBs on the M2000.

Implementation License control is automatically enabled in the NodeB.If license control is enabled, the default CE number is 16. Operators must

apply for or distribute licenses for newly-installed NodeBs on the M2000.

Related

Operations

Distribute NodeB licenses on the M2000.

Test Description For the NodeB in service, test the new feature in this release after upgrade.

PR Number SYED45695





Release Notes

Default value of the parameter DR used in flow control algorithmis optimized.

Description of

the Feature

From this release, the default value of the parameter DR used in flow controlalgorithm is changed to 5%.

Effect of

Improvement

When the default value of the parameter DR is changed to 5%, the HSDPA

throughput at the NodeBs with poor transmission quality can be improved.

The tolerance of the NodeB HSDPA service for poor transmission quality is

improved.

If operators configure the parameter DR , the configured DR is used in flowcontrol algorithm.

Implementation In adaptive flow control algorithm, the parameter DR is set to 5% by default.

If the adaptive flow control algorithm is not used, this change has no impact.

Related

Operations

None.


PR Number

Supporting the configuration of IMA clock mode including the ITCand CTC modes

Description of

the Feature

Supporting the configuration of IMA clock mode, including the ITC and CTC

modes.

Effect of

Improvement

The IMA clock mode can be configured, so the NodeBs can be connected to

the transmission equipment which supports only the CTC mode.

Implementation The IMA clock mode is ITC by default.

Related

Operations

Modify the MML command ADD IMAGRP; add the CLKM parameter for

clock mode configuration.


PR Number


None.


None.





Release Notes



None.


None.


MML Change


MML Change



None.


None.


Al armChange


Al armChange

3.3.6 Changes in Performance Counters

Perf ormanceCounter Change

3.4 V100R009C01B051

3.4.1 New Features

None





Release Notes


None.

3.4.3 Deleted Features None.



None.


MML Change


MML Change



None.


Al armChange


Al armChange

3.4.6 Changes in Performance Counters






Release Notes

3.5 V100R009C01B050

3.5.1 New Features

Clock over IP


Providing a synchronization solution for IP RAN. The NodeB can obtain

the clock source from the IP packet with timestamp.


The NodeB can obtain the system clock directly from the FE interface,

not from the external line clock source such as E1 and GPE. It reduces the

complexity and cost of the network.

Implementation

Through only upgrading the software, the NodeB supports clock over IP

as a client which receives the IP packet with timestamp sent from the

clock server. The clock server is a standalone device.

RelatedOperations

Run the ADD IPCLKLNK or RMV IPCLKLNK command to configurethe IP clock.

TestDescription

Run the DSP CLKSTAT command to check whether the system capturesthe clock source.

Run the DSP IPCLKLNK command to check the status of clock link.

Run the LST IPCLKLNK command to check the configuration of the IPclock.

PR Number Basic feature

MBMS FACH sharing


If multiple cells broadcast on the identical channel, the bandwidth of only

one channel is carried on the Iub interface and the NodeB distributes this

stream to all cells that need this channel program.


This feature can save the bandwidth on the Iub interface and reduceOPEX on transmission.

Implementation

The implementation feature complies with the 3GPP standard.

RelatedOperations None.

TestDescription

Establish three cells in the NodeB.

Configure FACHs carrying MBMS of the three cells to share the

transmission channels of one FACH among three FACHs.

Observe the bandwidth on the Iub interface for all FACHs equaling the

bandwidth used by one FACH.






Release Notes

RAN sharing phase 2: transmission sharing

Description of the Feature

Providing a transmission sharing solution for operators. Up to four operatorscan share one RAN system.


Operators can share the transmission resources of one RAN system. It reducesthe cost of the network.

Implementation

Through only upgrading the software, the NodeB supports transmissionsharing.

RelatedOperations

Run the ADD RSCGRP or RMV RSCGRP commands to configure the

resource group. Each resource group corresponds to one operator.

TestDescription

Test the throughput of different cells of different operators.


1800M/1900 MHz 40 W RRU3801C

Description of

the Feature

New frequency band of the RRU3801C

Effect of

Improvement

Supporting the frequency band of 1800 MHz/1900 MHz

Implementation Install the new 1800 MHz/1900 MHz RRU3801C.

Related

Operations

Run the ADD RRU or RMV RRU command to configure the RRU3801C

Test Description Run the ADD RRU command and install the RRU3801C.


RRU3804

Description of

the Feature

New remote radio module with four carriers and 60 W output power

Effect of

Improvement

The RRU3804 supports more carriers, higher amplifier efficiency, and higher reliability.

Implementation Provide the new RRU3804.

Related

Operations

Run the ADD RRU or RMV RRU command to configure the RRU3804.

Run the SET SEMMODE or DSP SEMMODE command to switch on or switch off SEM-MODE of the RRU3804.

Test Description Run the ADD RRU command, and install the RRU3804.






Release Notes

F(SPI) considered in HSDPA Iub flow control

Description of

the Feature

In HSDPA Iub flow control, the bandwidth allocated to the UE firstly aims at

GBR satisfaction, then the remained bandwidth is allocated with the F(SPI)considered. In previous version, the remained bandwidth is first allocated to

the UE with high SPI.

Effect of

Improvement

With the bandwidth of UEs for GBR guaranteed, the bandwidth allocated to

UEs shows the F(SPI) characteristics. The UE with higher SPI obtains higher bandwidth than the UE with lower SPI.

The bandwidth of UE1/F(SPI1) = the bandwidth of UE2/F(SPI2).

F(SPI)= SPI weight. The SPI weight can be set on the NodeB LMT.

Implementation The F(SPI) is modified in the way the same as Mac-hs scheduling.

Related

Operations

None.

Test Description Test the throughput of UEs in the same cell. The throughput of UEs is related

to the SPI.


Modifying F(SPI) in HSUPA Mac-e schedule

Description of

the Feature

In Mac-e schedule module, the SPI is taken in account. The function of the SPI

in Mac-e schedule is not the same as in Mac-hs schedule. For example, twoUEs with different SPIs are in the same cell and all other conditions are the

same. According to the Mac schedule, the throughput of the two UEs satisfythe following formula:

Throughput of UE1/F(SPI1) = Throughput of UE2/F(SPI2)

But in Mac-e schedule, the F(SPI) is defined as: F(SPI)= SPI+1; While in

Mac-hs schedule, the F(SPI) is defined as: F(SPI)= SPI weight and the SPI

weight can be set on the NodeB LMT.Therefore, this feature requires that the F(SPI) in Mac-e schedule is the sameas that in Mac-hs schedule.

Effect of

Improvement

The throughputs of UEs with different SPIs in the uplink carried on E-DCHshould be proper.

Implementation The F(SPI) is modified in the way the same as Mac-hs scheduling.

Related

Operations

None.

Test Description Test the throughput of UEs in the same cell. The throughput of UEs is relatedto the SPI.





Release Notes



None.


None.



MML Change


MML change

3.5.5 Changes in Alarm


Al armChange


Al armChange

3.5.6 Changes in Performance Counter






Release Notes

4 Feature Summary

This chapter outlines the features of the DBS3800 V100R009C01. For details, refer to the

documents such as DBS3800 System Description and DBS3800 Hardware Description

4.1 Feature List

4.1.1 V100R009

Figure 1.1 Main new features in the V100R009

No. Feature Name

1 Clock over IP

2 AISG 2.0

3 MBMS FACH sharing

4 RAN sharing pahse2: transmission sharing

5 1800 MHz/1900 MHz 40 W RRU3801C

6 RRU3804

4.1.2 V100R008

Figure 1.2 Main new features in the V100R008

No. Feature Name

1 Multi-band applications

2 Dual stack transport

ATM

IP RAN





Release Notes

3 HSUPA

4 Access of high speed UEs

4.1.3 V100R007

Figure 1.3 Main features in the V100R007

No. Feature Name Description

1 Voice service Supporting eight types of AMR voice service and silence

2 Data service Non-transparent data service

Transparent data service

Packet data service

3 Combined service Voice + data service

Data + data service

4 Location service Location service based on cell ID

5 Receive diversity 2-way receive diversity

4-way receive diversity

6 Transmit diversity Open loop transmit diversity: TSTD and STTD

Closed loop transmit diversity: Model 1 and Model 2

7 Softer handover Intra-frequency handover between adjacent sectors in the

NodeB can be realized.

8 Soft handover Inter-NodeB handover can be realized in the RNC.

9 Hard handover Inter-frequency handover

Handover between RNCs without Iur interface

Handover between different CNs

Handover between GSM and WCDMA

10 PDH transmission In E1/T1 mode. The link layer adopts ATM protocol.

11 SDH transmission STM-1 optical transmission. The link layer adopts ATM

protocol.

12 Sharing transmission

equipment with 2Gequipment

In Fractional ATM mode

13 Star topology Basic network type

14 Tree topology Maximum levels of cascading can be five or more.

15 Chain topology Maximum levels cascading can be five or more.





Release Notes

16 Ring topology Connected to the transmission equipment

17 Combinednetworking with 2G

equipment

Networking in Fractional ATM mode

18 Networking in the

RNS

Forming Intranet in the RNS to facilitate OM

19 Upper-level clock

synchronization

Extracting clock from Iub interface by default

20 GPS synchronization Optional

21 External input clock

synchronization such

as BITS

Optional

22 Free-run mode Guaranteeing that the DBS3800 can work properly for 90days or longer.

23 Uu interfaceconfiguration

The DBS3800 supports omni-directional 3-sector configurations. Each sector supports up to two carriers.

Supporting OTSR

The number of carriers in different sectors may be different.

The transmit power of different cells may be different.

24 Cell breathing Changing cell transmit power by adjusting the static gain

according to the network plan, thus changing the coverage

25 user-friendly OM Providing the Local Maintenance Terminal (LMT) and

M2000 integrated maintenance console

26 Maintenance modes Intranet maintenance: In a WCDMA intranet system, theoperator can perform OM on any NodeB in the system

through any network element by using the maintenance

terminal if he is authorized.

Local maintenance: The operator can use the LMT to

maintain the equipment through the local network port.

Remote maintenance: The operator can use the remote

dialing function to perform remote and integrated OM on theentire network through the M2000 client software if he is

authorized.

Dialing access by modem: This mode is used to maintain the

DBS3800 by dialing if the transmission is disrupted.

27 Powerful OM

function

Providing security management, alarm management,

configuration management, maintenance management, performance management and environment monitoring.

28 Convenient and practical Online Help

Abundant, complete and instructive contents of Online Helpgreatly improve the operability of the system.





Release Notes

29 IP Transport on theIub Interface

The Iub interface supports IP transport.

30Enhanced HSDPA

On the basis of the NodeB V100R006, the HSDPA functions

are enhanced or optimized.

31 Supporting 40 W

RRU

The RRU supports 40 W output power on the cabinet top.

32 Supporting new

frequency bands

On the basis of the supported frequency bands of the

V100R006, the MTRU and RRU3801C of the V100R007

support multiple new frequency bands to meet the frequency band requirements in different countries and regions.

33Supporting high

speed cells

The NodeB supports high speed cells. When the UE ismoving at a speed of no lower than 200 km/h, it can

normally access the cell and be provided with services. The

maximum speed of the movement can be 400 km/h.

34 Supporting hot

patches

When the hot patches are loaded, the board does not need to

be reset and the services are not affected.

35 Supporting performance

measurement

The NodeB supports performance measurement and relatedmeasurement items.

36Supporting theRRU3802C

When the RRU3802C is connected to the BBU through the

CPRI interfaces, the RRU3802C can be used in the

DBS3800.

37 Supporting the STM-

1 interface function

The BBU3806 supports the unchannelized STM-1 interface

function.





Release Notes

5 Fixed Bugs and Known

Anomalies

This chapter describes the fixed bugs and known anomalies of this version and each history

version.

5.1 V100R009C01B053

5.1.1 Fixed bugs

List of solved online problemsOnlineProblemSheetNo.

OfficeWhereProblemsOccur

Severity

ProblematicVersion

Problem Description

SYED48327 Hong

Kong

Critical V100R009C01B040 After the NodeB was upgraded to

V19C01B040 in Hong Kong, the rateof call drops increases obviously.

SYED45410 Hungary Critical V100R008C01B072 Setting the CHR level to NORMAL or

DETAIL makes the decoded DSPcollapse.

SYED49339 Spanish Critical V100R009C01B052 The NodeB reports the Cell Output

Power Too Low alarm, and the cell is

out of service.

SYED50552 Critical V100R009C01B052 The LMT cannot be connected to the

NodeB when sending a batch of MMLcommands to the NodeB quickly.

SYED50211 Japan Major V100R009C01B050 Low HSDPA rate because of busyRxBD





Release Notes

SYED50164 Japan Critical V100R009C01B050 The CPRI is disconnected because of SFP read error.

SYED49431 South

Africa

Major V100R009C01B050 The ALD communication link is

abnormal when the ALD is connected

to the RRU3804.

SYED50155 South

Africa

Critical V100R009C01B050 The RRU3804 communication is

disrupted for some days after the

NodeB is upgraded to DBS3800V100R009C01B050SPC005.

SYED49583 Australia Critical V100R009C01B050 The RRU communication is disrupted

possibly when the RRU BootROM is

upgraded.

SYED49884 Australia Major V100R009C01B050 The RRU cannot be used for a minute

after the RRU BootROM is upgraded.





Release Notes

After the NodeB was upgraded to V19C01B040 in Hong Kong, therate of call drops increases obviously





Release Notes

Description

After the NodeB was upgraded to V19C01B040 in Hong Kong, the rate of call drops increases obviously.

RootCauseAnalysis

In the current RNC version, the DPB (multi-RLs indicator) switch is OFF,thus the demodulating DSP cannot distinguish multiple or single RLs

currently due to lack of multi-RLs update indicator and sending no finger

power control pattern with an increase of 50 dB per second. In some cases,

the combined TPC works at UE side may drop, leading to signal degradingand call drops.

Impact The rate of call drops increases obviously.

SeverityLevel

Critical

Solution Modify the DSP software to solve this problem. To initialize no finger power

control pattern with and increase of 1500 dB per second (all up) no matter

what the multi-RLs indicator is. After receiving multi-Rls indicator, DSPmaintains all up pattern if the indicator indicates multi-RLs, or changes to 50dB per second increase if it indicates a single RL.

TestDescription

Test the rate of call drops under the two cases:

1. The RNC DPB switch is ON.

2. The RNC DPB switch is OFF.

The rate of call drops in both cases should return to normal.

PRNumber

SYED48327

Setting the CHR level to NORMAL or DETAIL possibly makes thedecoded DSP collapse

Description

Setting the CHR level to NORMAL or DETAIL possibly makes the decodedDSP collapse.

RootCauseAnalysis

The bug of the TI optimizer marked by SDSCM24634 generates the CHR-

related codes to access the unexpected address, which lead to the collapse of the DSP.

Impact The cell on this decoded DSP is out of service.

SeverityLevel

Critical

Solution Rewrite the code to avoid the defect of the T1 optimizer.

TestDescription

None.

PRNumber

SYED45410





Release Notes

The NodeB reports the Cell Output Power Too Low alarm, and thecell is out of service

Description

The NodeB reports the Cell Output Power Too Low alarm, and the cell isout of service.

RootCauseAnalysis

When the CPRI link is switched over, the state of the RRU is not reported tothe SIG module.

Impact The output power of the local cell is zero after the RRU CPRI link is

switched over.

SeverityLevel

Critical

Solution Modify the software to report the state of the RRU to the SIG module after

the RRU CPRI link is switched over, so the status of RRU and cell will be

correct after CPRI link is switched over.

TestDescription

None.

PRNumber

SYED49339





Release Notes

Low HSDPA rate because of busy RxBD

Description

Low HSDPA rate because of busy RxBD

RootCauseAnalysis

By checking the memory used for RxBDs in the BBU, it is found that some bytes of the memory are abnormal. The memory with a problem may causethat the ATM cannot receive properly and it rises from exception, for

example, multiple busy RxBD and uncompleted SDU errors. These errors

lead to the discarding of the received data, so the HSDPA rate is low.

Impact The memory with a problem will cause that the ATM receiving runs

abnormally and the data is discarded.

SeverityLevel

Major

Solution When busy RxBD occurs, the NodeB resets the CID automatically to avoid

that the data transmission is affected.

TestDescription

Run the HSDPA operation and check whether the HSDPA rate is low and

cannot resume.

PRNumber

SYED50211

The CPRI is disconnected because of SFP read error

Description

The CPRI is disconnected because of SFP read error

RootCauseAnalysis

Most optical transceivers support both MSA and NMSA protocols when

performing a read operation, but a new type of optical transceiver only

supports the read operation by using MSA protocol. When the NMSA protocol is used to read this type of optical transceiver, abnormal data is

obtained.

Impact Random read command stream with STOP and START not specified by MSA

may result in abnormal data.

Severity

Level

Critical

Solution Do not use a STOP condition followed by a START condition after dummy

write of random read (do not use NMSA protocol, but use MSA protocol).

TestDescription

Check the CPRI link and check whether the CPRI link is disconnected.

PRNumber

SYED50164





Release Notes

The ALD communication link is abnormal when the ALD isconnected to the RRU3804.

Description

The ALD communication link is abnormal when the ALD connected to theRRU3804.

RootCauseAnalysis

The ALD communication link is half-duplex, and the RRU3804 cannot sendand receive data at the same time. For the RRU3804, the receive path of the

UART is closed when sending data, and the data from the ALD will be

discarded. In this situation, the ALD communication abnormal alarm will be

reported

Impact The RRU3804 may fail to communication with the ALD for a short time.

SeverityLevel

Major

Solution Modify the way of the half-duplex by resetting receive FIFO of UARTinstead of closing the receive path in the RRU3804 BSP software.

Testdescription

None.

PRNumber

SYED49431

The RRU3804 communication is disrupted for some days afterthe NodeB is upgraded to DBS3800V100R009C01B050SPC003

Description

The RRU3804 communication is disrupted for some days after the NodeB isupgraded to DBS3800V100R009C01B050SPC003.

RootCauseAnalysis

When the NodeB receives error data from the TMA, the protection functionfor the global array is unavailable in the data receiving function, which

results in communication task abnormal, so the RRU3804 communication is

disrupted.

Impact The RRU3804 communication is disrupted.

SeverityLevel

Critical

Solution Modify the protection function for the global memory to avoid the

modification of the other memories in the RRU3804 BSP software.

TestDescription

None.

PRNumber

SYED50155





Release Notes

The RRU communication is disrupted possibly when the RRUBootROM is upgraded

Description

The RRU communication is disrupted possibly when the RRU BootROM isupgraded.

RootCauseAnalysis

There is a software bug in RRU BootROM upgrading. When upgrading theBootROM software, the RRU resets automatically. Therefore, the BootROM

is destroyed and the RRU cannot start.

Impact When upgrading the RRU BootROM to version earlier than

V100R009C01B053, the BootROM may be destroyed and the RRU

communication is disrupted.

SeverityLevel

Critical

Solution Modify the software bug in the RRU BootROM upgrading mechanism.

TestDescription

None.

PRNumber

SYED49583

The RRU cannot be used for a minute after the RRU BootROM isupgraded

Descriptio

n

The RRU cannot be used for a minute after the RRU BootROM is upgraded.

RootCauseAnalysis

There is a software bug in RRU BootROM upgrading. When upgrading theBootROM software, the RRU resets automatically and the RRU cannot be

used when the RRU is resetting.

Impact The RRU cannot be used for a minute and is recovers automatically.

SeverityLevel

Major

Solution Modify the software bug in the RRU BootROM upgrading mechanism.

TestDescription

None.

PRNumber

SYED49884





Release Notes

Internal fixed bug list

OnlineProblemSheet

No.

Severity

ProblematicVersion

Problem Description

SYED50552 Critical V100R009C01B052 The LMT cannot be connected to the NodeB when sending a batch of MML commands to the NodeB quickly.

The LMT cannot be connected to the NodeB when sending abatch of MML commands to the NodeB quickly

Description The LMT cannot be connected to the NodeB when sending a batch of MMLcommands to the NodeB quickly.

Root CauseAnalysis

There is a bug in software that the SHELL function is abnormal when the valueof the related command is over 20.

Impact The LMT cannot be connected to the NodeB.

SeverityLevel

Critical

Solution Modify the software bug in the SHELL function.

TestDescription

None.

PR Number SYED50552

5.1.2 Known Anomalies

None.





Release Notes

5.2 V100R009C01B052SPH001

5.2.1 Fixed Bugs

List of solved online problems

OnlineProblemSheetNo.


Severity

ProblematicVersion

Problem Description

SYED49339 Spanish Critical DBS3800V100R00

9C01B052

After RRU optical/electrical port

switchover, there will be no output

power for the local cell.

After RRU optical/electrical port switchover, there will be nooutput power for the local cell.

Description

After RRU optical/electrical port switchover, there will be no output power for the local.

RootCauseAnalysis

When the RRU is in ring networking, if the master CPRI port is down, the

CPRI is automatically switched over to the slave. After the CPRI portswitchover, the local cell should be re-created. While due to the software bug,

the local cell was not re-created after the RRU CPRI port switchover.

Impact After the RRU optical/electrical port switchover, the local cell re-created on

the RRU has no output power, which results in the service abnormality.

SeverityLevel

Critical

Solution After CPRI port switchover, the local cell was recreated and all will be

normal.

TestDescription

Set RRU chain break point on the RRU ring. When the RRU

optical/electrical port is switched over, power of the local cell related to theRRU was normal.

PR

Number

SYED49339

List of Fixed Internal Bugs

None.


None.





Release Notes

5.3 V100R009C01B052

5.3.1 Bugs fixed

List of Solved Online Problems

OnlineProblemSheetNo.


Severity

ProblematicVersion

Problem Description

SYED44073 South

Africa

Critical DBS3800V100R00

9C01B051

Solve the problem that BBU reboot

randomly.

SYED42395 Spain Critical DBS3800V100R00

9C01B050

The RTWP value of a cell reported by

the Node B to the RNC is 3db less thanthe correct value.

SYED46406 Japan Critical DBS3800V100R008C01B072

When the number of Pico RRUs on the3rd chain (connect to the 3rd CPRI port)

is more than six, the 6th Pico RRU link

will be interrupted.

SYED48436 France Critical DBS3800V100R00

9C01B050

When 8 E1s are connected to one BBU,

the 6th E1 abnormal alarm will bereported.

SYED45472 Brazil Critical DBS3800V100R00

9C01B050

Supply Node B software for a long time

and unable to transfer any other fileuntil it finish

SYED44857 Japan Critical iDBS3800V100R00

9C01B050

The Pico RRU configuration failure

alarm is reported.

South

Africa

Critical DBS3800V100R00

9C01B050

RRU reports VSWR abnormal alarm

SouthAfrica

Critical DBS3800V100R009C01B050

The RRU has no output power.

SouthAfrica

Critical DBS3800V100R009C01B050

The RRU reports clock abnormalalarm.


9C01B051

The HSDPA rate declines after the

PCPICH Power is changed.


9C01B050

HSUPA flow control is disabled when

DCCC is used.

Spain Critical DBS3800V100R00

9C01B051

The QAAL2 fails to be established.





Release Notes

Solving the problem that BBU reboots randomly





Release Notes

Description

The BBU reboots randomly

RootCauseAnalysis

There is a software bug in memory allocation, which will cause CPUexception.

Impact The BBU reboots randomly.

SeverityLevel

Critical

Solution Fix the software bug in memory allocation.

TestDescription

None.





Release Notes

PRNumber

SYED44073





Release Notes

Solving the problem that the RTWP value of reported by theNodeB report to the RNC is wrong





Release Notes

Description

The RTWP value of a cell reported by the NodeB to the RNC is 3db less thanthe correct value.

RootCauseAnalysis

When the RRU connected to first fiber interface of BBU and a cell which isconfigured with two receive channels uses this RRU, only one received

channel is configured correctly.

Impact The RTWP value of a cell reported by the NodeB to the RNC is 3db less than

the correct value.

SeverityLevel

Critical

Solution Fix the software bug.

TestDescription

When the RRU connected to first optical interface of BBU and a cell

configured with two receive channels uses this RRU, check if the RTWPvalue of a cell reported by the Node B to the RNC is right.





Release Notes

PRNumber

SYED42395





Release Notes

Solving the problem that the 6th Pico RRU on the 3rd CPRI chainbe disrupted





Release Notes

Description When the number of Pico RRUs on the 3rd chain (connected to the 3rd CPRI port) is more than six, the 6th Pico RRU link will be interrupted.

Root CauseAnalysis

There is a FPGA code bug in HDLC control of Pico RRU.

Impact The 6th Pico RRU connected to the 3rd CPRI port was abnormal.

SeverityLevel

Critical

Solution Fix the FPGA code bug of HDLC control.

TestDescription

None.





Release Notes

PR Number SYED46406





Release Notes

Solving the problem that the 6th E1 abnormal alarm reportedwhen 8 E1s are connected to one BBU





Release Notes

Description When 8 E1s are connected to one BBU, the 6 th E1 abnormal alarm will be

reported.

Root Cause

AnalysisThe root cause is the 6th E1 pin of FPGA collides with another signal.

Impact The service on the 6th E1 is abnormal.

SeverityLevel

Critical

Solution Modify the FPGA constraint file and clear the pin collision.

TestDescription

None.





Release Notes

PR Number SYED48436





Release Notes

Solving the inability to transfer any other file because NodeBsoftware is supplying





Release Notes

Description

Supply Node B software for a long time and unable to transfer any other fileuntil it finish

RootCauseAnalysis

When supplying the Node B software, it will try 1 time from local FTP whichneed 2 minute, and 6 time from M2000 server, which need 3 minutes every

time, so we need to wait about 20 minutes to supply the Node B software and

unable to transfer any other file until it finish.

Impact It lasts for a long time to supply Node B software and we are unable to

transfer any other file between Node B and FTP termination

SeverityLevel

Critical

Solution Reduce the times when supplying the Node B software

TestDescriptio

n

Before improvement: 3(min) * 6(times) + 2(min) * 1(time)=20(min)

After improvement: 1.5(min)* 3(times) + 1(min) * 1(time) = 4.5(min)





Release Notes

PRNumber

SYED45472





Release Notes

Solving the problem that Pico RRU configuration failure alarmreported





Release Notes

Description

The Pico RRU configuration failure alarm is reported.

RootCauseAnalysis

Pico RRU has only one receive unit, but the NodeB software is configuredwith two receive unit, which results in the configure failure after the Pico

RRU starts up. In such a case, the alarm will be reported.

Impact The Pico RRU configuration failure alarm will be reported.

SeverityLevel

Critical

Solution Configure only one receive unit for Pico RRU on the NodeB software..

TestDescription

Reset the Pico RRU and the alarm is cleared.





Release Notes

PRNumber

SYED44857





Release Notes

Solving the problem that the VSWR abnormal alarm is reported





Release Notes

Description

The RRU reports VSWR abnormal alarm.

RootCauseAnalysis

There is a software bug in VSWR defecting mechanism.

Impact If this alarm occurs and operator has the current VSWR value is higher than

that threshold value set for automatic TX channel switch off, the RRU will

switch off TX channel automatically. Thus, downlink service is interrupted.

SeverityLevel

Critical

Solution Fix the software bug in VSWR defecting mechanism.

TestDescriptio

n

None.





Release Notes

PRNumber





Release Notes

Solving the problem that the RRU has no output power





Release Notes

Description

The RRU has no output power.

RootCauseAnalysis

PAR of input power of RRU is too high, which in the meantime increase theinput power of PA and destroys it.

There is a bug in PAR control in RRU. When the input power of RRU is toohigh, the input power will exceed the tolerance of PA, and PA will be fault.

Impact RRU has no output power, which results in the downlink service interruption.

SeverityLevel

Critical

Solution Modify the software of PAR control.

TestDescriptio

n

None.





Release Notes

PRNumber





Release Notes

Solving the problem that the RRU reports clock abnormal alarm





Release Notes

Description

The RRU reports clock abnormal alarm.

RootCauseAnalysis

There is a software bug in RRU clock detection.

Impact When this alarm occurs, RRU has no output power. Downlink service is

interrupted.

SeverityLevel

Critical

Solution Fix the software bug in RRU clock alarm detection.

TestDescription

None.





Release Notes

PRNumber





Release Notes

Solving the problem that HSDPA Rate declined after PCPICHPower changing





Release Notes

Description

HSDPA rate declines after PCPICH power is changed.

RootCauseAnalysis

There is software bug in the downlink DSP which concerns cellreconfiguration.

Impact In such a case, the air interface quality of the certain cell decreases, which

will affect the service performance temporarily. However, the service will be

recovered after the high power DCH disconnected.

SeverityLevel

Critical

Solution Modify the downlink DSP software to correct the cell reconfiguration

procedure. This ensures the TFCI offset validity.

Test

Description

None.





Release Notes

PRNumber

SYED48542

Solving the problem that HSUPA flow control is disabled becauseof using DCCC

Description

HSUPA Flow Control is disabled because of using DCCC

RootCauseAnalysis

The issue is from a error made by downlink DSP, which wrongly maintained

the relation between the FP and path group when concerning Signal of RadioLink Reconfigure

Impact When the DCCC is used, the HSUPA flow control is disabled, and the servicewould be temporarily affected.

SeverityLevel

Critical

Solution Modify the radio link reconfiguration procedure in downlink DSP to ensurethe correct relation between FP and path group.

TestDescription

None.

PRNumber

SYED48438

Solving the problem that QAAL2 fails to be established

Description

The QAAL2 fails to be established.

RootCauseAnalysis

The QAAL2 component can only audit A2SECCBID for one time. If

A2SECCBID is leaked, the resource will be exhausted. Thus, the QAAL2fails to be established.

Impact The RRC success ratio is very low.

Severity

Level

Critical

Solution Modify the software of QAAL2 component to support repeated auditing for

A2SECCBID.

TestDescription

None.

PRNumber





Release Notes

List of fixed internal bugs

None.

5.3.2 Known Anomalies None.

5.4 V100R009C01B051

5.4.1 Fixed Bugs

List of solved online problemsOnlineProblemSheetNo.


Severity

ProblematicVersion

Problem Description

PR162/SYED46129

France Critical DBS3800V100R008C01B072

After upgrade to V100R008C01B072,the NodeB reports ALM-2700 IMA

Link Loss of Frame alarm, which

results in the fluctuation of DPA speed.

SYED47601 Romania Major DBS3800V100R008C01B072 There are many Chinese characterswhen the MIT tree is used on theM2000 client after the NodeB version

is upgraded to

DBS3800V100R008C01B072

SYED45256 Belgium Major V100R008C01B072 One Type of KATHERIN TMAs fails to

be scanned.





Release Notes

Solving the problem that after upgrade to V100R008C01B072,NodeB reports ALM-2700 IMA Link Loss of Frame, which resultsin the fluctuation of DPA speed

Description DBS3800V100R008C01B072 has alarm of ALM-2700 IMA Link Loss Of Frame, and this result in the fluctuation of DPA speed, which bored on this

E1 route.

RootCauseAnalysis

The FPGA logic of the clock to chip 7340 is generated from a combinationalcircuit. There might be a place and route risk to generate the burr in the clock.

In the previous versions, a delay unit is used to avoid a burr in the clock, but

this method depends on the delay of FGPA place and route. Different FPGA

routes can make different delays. The FPGA route of release B072 generatesthe burr in the fifth E1 (4BBU FPGA release) and the burr in the sixth E1

(2BBU FPGA release), which results in error frames.

Impact DBS3800V100R008C01B072 has the ALM-2700 IMA Link Loss Of Frame

alarm, which results in the fluctuation of DPA speed bored on this E1 route.

SeverityLevel

Critical

Solution Remove the E1 routes with alarm from IMA group (RMV IMALNK);

Replace the faulty E1 routes with normal E1 routes.

TestDescription

None.

PR

Number

PR162/SYED46129





Release Notes

Solving the problem that there are many Chinese characterswhen the MIT tree is used on the M2000 client after the NodeBversion is upgraded to DBS3800V100R008C01B072

Description There are many Chinese characters when using the MIT tree on the M2000client after the NodeB version is upgraded to DBS3800V100R008C01B072.

RootCauseAnalysis

When building M2000 Mediation of DBS3800, there is an error link of MML

command file which is in Chinese version instead of English version.

Impact When the MIT tree is used on the M2000 client, there are many Chinesecharacters cannot be displayed normally.

SeverityLevel

Major

Solution Rebuild the M2000 mediation of DBS3800 and confirm the MML commandfile in the right version (English version).

TestDescription

There is no Chinese character when the MIT tree is used on the M2000 client.

PRNumber

SYED47601





Release Notes

Solving the problem that one type of KATHERIN TMA fails to bescanned

Description

One Type of KATHERIN TMA fails to display the serial number of

UniqueID in the scanning list on LMT.

RootCauseAnalysis

The KATHERIN TMA works with the NACP and MRRU.

Impact When reporting the scanning result to LMT, the serial number of

UniqueID will be nullssince the KATHERIN TMA has ‘\0’ between vendor

code and serial number. The NodeB software uses ‘strcpy’ to copy the

UniqueID, which will regard ‘\0’ as the end of UniqueID. Thus the serial

number of UniqueID is null.

Severity

Level

Major

Solution Modify the NodeB software configuration. Use the ‘memcpy’ to copy the

UniqueID.

TestDescription

After modification, the MRRU or NCAP can properly scan the serial number and vendor code of KATHERIN TMA. This has no impact on the TMA of

other types or antennas.

PRNumber

SYED45256

List of Fixed Internal Bugs

None.





Release Notes


The RRU link interrupted randomly if a break point is made

between RRU and BBUDefect ID SYED46406

Description In some DBS3800 sites configured with two RRUs and two BBUs, the RRU

connect to the master BBU and slave BBU and make a loop. When thecustomer makes a break point between RRU and BBU, the RRU will become

abnormal probability.

TriggerCondition

In the case of BBUs (master and slave) + RRU ring networking, when the

customer makes a break point between RRU and BBU, the RRU link may be

interrupted..

Impact The cells on the abnormal RRU fail to be set up.

PreventiveMeasure

Don’t make any break point between RRU and BBU. Don’t connect RRU tothe master BBU and slave BBU to form the ring networking.

SolutionProgress

Under modification and test

The NodeB reports only 2 carriers’ RTWP value to the LMT forRRU which supports 4 carriers.

Defect ID SYED47376

Description For the RRU which supports 4 carriers, Node B reports only 2 carriers’

RTWP value to LMT.

Triggercondition

The RRU with 4 carriers is used.

Impact Only the RTWP value of RRU which supports 4 carriers reported to LMT.

Only 2 carriers’ RTWP value is reported to the LMT, and the other carriers’

RTWP value can’t be reported to the LMT.

PreventiveMeasure

None.

SolutionProgress






Release Notes

The ALD link interrupted in ROB when configuring ALDimmediately in ROB after configured ALD in ROA in RRU3804

Defect ID SYED45724

Description In RRU3804, if user configures ALD link in ROB immediately after configuring ALD link in ROA, the ALD link in ROB will be interrupted.

Triggercondition

The ALD link in ROB is configured immediately after the ALD link is

configured in ROA in RRU3804

Impact The ALD link in ROB will be interrupted.

PreventiveMeasure

After configuring ALD link in ROA, wait a minute. Do not configure the

ALD link in ROB until the response is reported.

SolutionProgress


RRU3804 report the RRU Clock Abnormal alarm randomly

Defect ID SYED46218

Description The RRU3804 reports the RRU Clock Abnormal alarm randomly and localcell cannot be used. This alarm will be automatically cleared in 5 seconds.

TriggerCondition

The RRU3804 is used.

Impact The RRU3804 reports the RRU Clock Abnormal alarm randomly and thelocal cell cannot be used. This alarm will be automatically cleared in 5

seconds.

PreventiveMeasure

None.

SolutionProgress






Release Notes

The Configure Date Error alarm reported by the NodeB that isupgraded from V100R008C01B072 to V100R009C01B050

Defect ID SYED46424

Description The NodeB reports Configure Date Error Alarm after upgraded fromV100R008C01B072 to V100R009C01B050.

TriggerCondition

The NodeB adds a node in the Configure Date file both in

V100R008C01B072 and V100R009C01B050. Because the

V100R009C01B050 version has different nodes from the

V100R008C01B072, when ALD equipment is added and the ADD ALDcommand is executed, the NodeB reports Configure Date Error alarm after

upgraded from V100R008C01B072 to V100R009C01B050.

Impact When adding the ALD equipment, the update from V100R008C01B072 to

V100R009C01B050 will fail.

PreventiveMeasure

Don’t execute ADD ALD command after upgrade to V100R009C01B050.

SolutionProgress






Release Notes

6 Notes and Cautions

Figure 1.1 Notes and cautions for the DBS3800 V100R009C01B053

No.

Item Description

1 Time restriction None

2 Place/site restriction Released, only for Greece Vodafone, Australia

3 Other restrictions None

4 Version termination Replaced by a later version according to the subsequent

version policies





Release Notes

7 Related Documents

The package of documents is delivered with the product of this version. While downloading the

software package, Huawei engineers will download the package of documents and deliver themto the customer.





Release Notes

8 Technical Support

This chapter describes how to obtain technical support from Huawei Technologies Co., Ltd.

8.1 Support.huawei.comSupport.huawei.com provides an efficient and real-time communication platform, on which youcan obtain technical documents, submit technical consultation, service requests and faults

online, and feed back the advice on improving our products.

You can access support.huawei.com by visiting http://support.huawei.com.

8.2 Technical Support Hotline

In the case of an urgent fault, you can turn to the technical support hotline for help.

Technical support hotline:

+86-755-28560000


http://support.huawei.com/

http://support.huawei.com/




Release Notes

Figure 1.1Acronyms andAbbreviations

Numeric Full Name

3

3GPP 3rd Generation Partnership Project

A

AC Alternating Current

A-GPS Network-Assisted GPS

AISG Antenna Interface Standard Group

AMR Adaptive Multi-Rate

ANSI American National Standard Institute

ATM Asynchronous Transfer Mode

B

BITS Building Integrated Timing Supply system

BTS Base Transceiver Station

C

CE Channel Element

CES Circuit Emulation Service

CMB Cell Multimedia BroadcastCN Core Network

CPRI Common Public Radio Interface

CPU Center Processing Unit

CS Circuit Service

D

DAGC Digit Automatic Gain Control

DC Direct Current





Release Notes

DSP Digital Signal Processor

E

EMC Electro Magnetic Compatibility

ETS European Telecommunication Standards

ETSI European Telecommunications Standards Institute

F

FACH Forward Access Channel

FDD Frequency Division Duplex

FLASH FLASH memory

G

GPS Global Positioning System

GSM Global System for Mobile Communications

GUI Graphic User Interface

H

HARQ Hybrid Automatic Repeat Request

HSDPA High Speed Downlink Packet Access

HSUPA High Speed Uplink Packet Access

I

IEC International Electro technical Commission

IMA Inverse Multiplexing on ATM

Iu Interconnection point between an RNC and a Core Network. It is also

considered as a reference point.

Iub Interface between an RNC and a Node B

Iur A logical interface between two RNC

IP Internet Protocol

IPoA IP Over ATMIPoE IP over Ethernet

ITU International Telecommunications Union

L

LMT Local Maintenance Terminal

LNA Low Noise Amplifier

M

MBMS Multimedia Broadcast and Multicast Service





Release Notes

MML Man Machine Language

MUD Multi-user Detection

N

NodeB A logical node responsible for radio transmission / reception in one or more

cells to/from the User Equipment. Terminates the Iub interface towards theRNC.

O

OMC Operation and Maintenance Center

OTDOA Observed Time Difference of Arrival

P

PA Power Amplifier

PS Packet Switched

R

RCU Remote Control Unit

RET Remote Electrical Tilt

RF Radio Frequency

RH Relative Humidity

RNC Radio Network Controller

S

SA Smart Antenna

SCCPCH Secondary common control physical channel

SGSN Serving GPRS Support Node

STMA Smart Tower Mounted Amplifier

STM-1 Synchronous Transport Mode-1

STTD Space Time Transmit Diversity

T

TMA Tower Mount Amplifier

TSTD Time Switched Transmit Diversity

TTI Transmission Time Interval

U

UE User Equipment

UMTS Universal Mobile Telecommunications System

UNI User-Network Interface

UTRAN UMTS Terrestrial radio access network





Release Notes

Uu The Radio interface between UTRAN and the User Equipment

V

VLAN Virtual LAN

W

WCDMA Wideband Code Division Multiple Access

Wcdma Nodeb Release Notes(Dbs3800 v100r009c01b053)

Documents

Transcript of Wcdma Nodeb Release Notes(Dbs3800 v100r009c01b053)