RAN12.0 Basic Feature Description V1.6(20100830)

RAN12.0 Basic Feature Description

Issue 1.6

Date 2010-08-30

HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2010. 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 commercial contract made

between Huawei and the customer. All or partial products, services and features described in this

document may not be within the purchased scope or the usage scope. Unless otherwise agreed by

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 the 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]

Telephone: 0755-28560000 4008302118

Fax: 0755-28560111

http://www.huawei.com/

mailto:[email protected]


Issue 1.5 (2010-06-10) Commercial in Confidence Page 3 of 159

Contents

1 System Improvement ................................................................................................................... 7

1.1 WRFD-000001 System Improvement for RAN5.1 .......................................................................................... 7

1.2 WRFD-000002 System Improvement for RAN6.0 .......................................................................................... 8

1.3 WRFD-000003 System Improvement for RAN6.1 ........................................................................................ 10

1.4 WRFD-000004 System Improvement for RAN10.0 ...................................................................................... 11




2 Standards Compliance ............................................................................................................... 19

2.1 WRFD-010101 3GPP R8 Specifications ........................................................................................................ 19

2.2 WRFD-010102 Operating Multi-band ........................................................................................................... 20

2.3 WRFD-010201 FDD Mode ............................................................................................................................ 21

3 RABs and Services ...................................................................................................................... 23

3.1 WRFD-010510 3.4/6.8/13.6/27.2 kbit/s RRC Connection and RAB Assignment ......................................... 23

3.2 WRFD-010501 Conversational QoS Class .................................................................................................... 24

3.3 WRFD-010502 Streaming QoS Class ............................................................................................................ 25

3.4 WRFD-010503 Interactive QoS Class ........................................................................................................... 26

3.5 WRFD-010504 Background QoS Class ......................................................................................................... 27

3.6 WRFD-010609 Multiple RAB Introduction Package (PS RAB < 2) ............................................................. 29

3.6.1 WRFD-01060901 Combination of Two CS Services (Except for Two AMR Speech Services) ........... 29

3.6.2 WRFD-01060902 Combination of One CS Service and One PS Service ............................................. 30

3.6.3 WRFD-01060903 Combination of Two CS Services and One PS Service (Except for Two AMR

Speech Services) ............................................................................................................................................ 31

3.7 WRFD-021104 Emergency Call..................................................................................................................... 31

4 RAN Architecture & Functions ................................................................................................ 33

4.1 MRFD-210604 2-Way Antenna Receive Diversity ........................................................................................ 33

4.2 WRFD-010205 Cell Digital Combination and Split ...................................................................................... 34

4.3 WRFD-010208 Fast Power Congestion Control (FCC) ................................................................................. 35

4.4 WRFD-010211 Active TX Chain Gain Calibration ....................................................................................... 36

4.5 WRFD-010202 UE State in Connected Mode (CELL-DCH, CELL-PCH, URA-PCH, CELL-FACH) ........ 37

4.6 WRFD-010401 System Information Broadcasting ........................................................................................ 39

4.7 WRFD-010301 Paging UE in Idle, CELL_PCH, URA_PCH State (Type 1) ................................................ 40



4.8 WRFD-010302 Paging UE in CELL_FACH, CELL_DCH State (Type 2) .................................................... 41

5 Channel Resource Management .............................................................................................. 43

5.1 WRFD-020900 Logical Channel Management .............................................................................................. 43

5.2 WRFD-021000 Transport Channel Management ........................................................................................... 44

5.3 WRFD-022000 Physical Channel Management ............................................................................................. 46

5.4 WRFD-021101 Dynamic Channel Configuration Control (DCCC) ............................................................... 52

6 Network Security ........................................................................................................................ 53

6.1 WRFD-011401 Integrity Protection ............................................................................................................... 53

6.2 WRFD-011402 Encryption ............................................................................................................................ 54

7 Power Control .............................................................................................................................. 56

7.1 WRFD-020501 Open Loop Power Control .................................................................................................... 56

7.2 WRFD-020502 Downlink Power Balance ..................................................................................................... 57

7.3 WRFD-020503 Outer Loop Power Control ................................................................................................... 58

7.4 WRFD-020504 Inner Loop Power Control .................................................................................................... 59

8 Cell Management ........................................................................................................................ 61

8.1 WRFD-020101 Admission Control ................................................................................................................ 61

8.2 WRFD-020102 Load Measurement ............................................................................................................... 63

8.3 WRFD-020106 Load Reshuffling .................................................................................................................. 64

8.4 WRFD-020107 Overload Control .................................................................................................................. 66

8.5 WRFD-020108 Code Resource Management ................................................................................................ 67

9 Network Sharing ......................................................................................................................... 69

9.1 WRFD-021301 Shared Network Support in Connected Mode ...................................................................... 69

9.2 MRFD-210104 BSC/RNC Resource Sharing ................................................................................................ 70

10 Mobility Management ............................................................................................................. 72

10.1 WRFD-020201 Intra Node B Softer Handover ............................................................................................ 72

10.2 WRFD-020202 Intra RNC Soft Handover ................................................................................................... 73

10.3 WRFD-020203 Inter RNC Soft Handover ................................................................................................... 74

10.4 WRFD-020301 Intra Frequency Hard Handover ......................................................................................... 74

10.5 WRFD-010801 Intra RNC Cell Update ....................................................................................................... 75

10.6 WRFD-010802 Inter RNC Cell Update ....................................................................................................... 76

10.7 WRFD-010901 Intra RNC URA Update ...................................................................................................... 77

10.8 WRFD-010902 Inter RNC URA Update ...................................................................................................... 78

10.9 WRFD-021400 Direct Signaling Connection Re-establishment (DSCR) .................................................... 79

11 NodeB Network Structure ....................................................................................................... 81

11.1 MRFD-210204 Star Topology ...................................................................................................................... 81

11.2 MRFD-210205 Chain Topology ................................................................................................................... 82

11.3 MRFD-210206 Tree Topology ..................................................................................................................... 83

12 Clock ............................................................................................................................................ 85

12.1 MRFD-210501 BTS/NodeB Clock .............................................................................................................. 85



12.2 MRFD-210502 BSC/RNC Clock ................................................................................................................. 86

13 ATM Transmission Introduction Package ........................................................................... 89

13.1 WRFD-050301 ATM Transmission Introduction Package ........................................................................... 89

13.1.1 WRFD-05030101 ATM over E1T1 on Iub Interface .......................................................................... 90

13.1.2 WRFD-05030102 ATM over Channelized STM-1/OC-3 on Iub Interface ......................................... 91

13.1.3 WRFD-05030103 ATM over Non-channelized STM-1/OC-3c on Iub/Iu/Iur Interface ...................... 92

13.2 WRFD-05030104 Dynamic AAL2 Connections in Iub/IuCS/Iur Interface ................................................. 93

13.3 WRFD-05030105 Permanent AAL5 Connections for Control Plane Traffic ............................................... 95

13.3.2 WRFD-05030106 Call Admission Based on Used AAL2 Path Bandwidth ........................................ 96

13.3.3 WRFD-05030107 CBR, rt-VBR, nrt-VBR, UBR ATM QoS Classes ................................................. 97

13.3.4 WRFD-05030110 F5 ........................................................................................................................... 97

14 IMA Transmission for E1/T1 or Channelized STM-1/OC-3 on Iub Interface ............. 100

14.1 WRFD-050304 IMA Transmission for E1T1 or Channelized STM-1/OC-3 on Iub Interface ................... 100

15 UBR+ATM QoS Class ............................................................................................................ 102

15.1 WRFD-050305 UBR+ ATM QoS Class ..................................................................................................... 102

16 Link Aggregation .................................................................................................................... 103

16.1 MRFD-210103 Link Aggregation .............................................................................................................. 103

17 System Reliability ................................................................................................................... 105

17.1 WRFD-040100 Flow Control ..................................................................................................................... 105

17.2 WRFD-040101 DPU Board Replaced without Service Interruption in RNC ............................................ 106

17.3 MRFD-210101 System Redundancy .......................................................................................................... 107

17.4 MRFD-210102 Operate System Security Management ............................................................................. 109

18 RAN Operation & Maintenance ........................................................................................... 111

18.1 MRFD-210301 Configuration Management .............................................................................................. 111

18.2 MRFD-210302 Performance Management ................................................................................................ 113

18.3 MRFD-210303 Inventory Management ..................................................................................................... 116

18.4 MRFD-210304 Faulty Management .......................................................................................................... 118

18.5 MRFD-210305 Security Management ....................................................................................................... 121

19 Message Tracing ...................................................................................................................... 123

19.1 MRFD-210801 Interface Message Tracing ................................................................................................ 123

19.2 MRFD-210802 User Signaling Tracing ..................................................................................................... 124

20 Software Management ........................................................................................................... 126

20.1 MRFD-210401 BSC/RNC Software Management .................................................................................... 126

20.2 MRFD-210402 BTS/NodeB Software Management ................................................................................. 127

20.3 MRFD-210310 BTS/NodeB Software USB Download ............................................................................. 129

21 Node B Configuration and Commissioning ...................................................................... 131

21.1 WRFD-031100 BOOTP ............................................................................................................................. 131

21.2 WRFD-031101 Node B Self-discovery Based on IP Mode........................................................................ 132



21.3 WRFD-031102 Node B Remote Self-configuration .................................................................................. 133

21.4 WRFD-031103 Node B Self-test ................................................................................................................ 134

22 License Management .............................................................................................................. 135

22.1 MRFD-210403 License Management ........................................................................................................ 135

23 Basic Node B Functions ......................................................................................................... 138

23.1 MRFD-210309 DBS Topology Maintenance ............................................................................................. 138

23.2 WRFD-031000 Intelligently Out of Service .............................................................................................. 140

23.3 WRFD-031200 OCNS ............................................................................................................................... 141

23.4 WRFD-031400 Power off the equipment level by level ............................................................................ 141

23.5 WRFD-031500 Solar Power Device Management..................................................................................... 143

23.6 WRFD-021404 Single IP Address for Node B ........................................................................................... 144

23.7 WRFD-010212 Improved CE Mapping for E-DCH .................................................................................. 145

24 Documentation ........................................................................................................................ 147

24.1 MRFD-210701 Documentation .................................................................................................................. 147

25 Node B Antenna System Solution ....................................................................................... 149

25.1 MRFD-210601 Connection with TMA (Tower Mounted Amplifier) ......................................................... 149

25.2 MRFD-210602 Remote Electrical Tilt ....................................................................................................... 151

25.3 WRFD-060003 Same Band Antenna Sharing Unit (900 MHz) ................................................................. 154

26 Acronyms and Abbreviations ............................................................................................... 158



1 System Improvement

1.1 WRFD-000001 System Improvement for RAN5.1

Availability

This feature is available from RAN5.1.

Summary

This feature is based on 3GPP R5 with a series of newly introduced RAN products and

functions, which meets a wider range of customer requirements and improves the

performance of the product.

Benefits

The benefits of the system improvements include the following:

Wider product range, including new products and configurations

Improvement in stability and robustness due to improved functions and algorithms

Improved performance, including higher capacity

Enhanced usability, and reduced operating costs

Description

Compatibility with 3GPP Release 5

The UMTS RAN5.1 is based on the 3GPP Release 5, which adds a number of important

functions for RAN and UE. The major new feature is the high speed downlink packet access

(HSDPA), introduced in the 3GPP Release 5. All relevant interfaces are updated according to

the June 2004 version of Release 5, and all essential 3GPP Release 5 CRs since then have

been implemented. The HSDPA Phase 2 is the enhancement of Phase 1, which provides 3.6

Mbit/s per user downlink speed.

The 3GPP TR 25.933 IP transport in the UTRAN is implemented in RAN5.1. RAN5.1 is the

first version to provide the Iub IP transmission. The IP transmission provides new solutions to

the last mile access to the Node B. Thus, it saves the cost of the transmission.

New products and configurations supported

The UMTS RAN5.1 supports the following new products and configurations:



I. RNC

Supporting quakeproof cabinets that are suitable for the scenarios with specific

quakeproof requirements

II. Node B

DBS3800 supports Band 1 (2100 MHz) RRU, 2 carriers 40 W

DBS3800 supports Band II (1900 MHz) RRU, 2 carriers 20 W

DBS3800 supports Band III (1800 M) / IX (Japanese 1800 M) RRU, 2 carriers 20 W

BTS3812E/A supports Band 1 (2100 MHz) new MTRU, 2 carriers 40 W with Doherty

PA for Band I (2100 M)

BTS3812E/A supports Band II (1900 MHz) MTRU, 2 carriers 40 W

BTS3812E/A supports Band III (1800 MHz) MTRU, 2 carriers 40 W

The new transmission interface card NUTI supports the FE ports

The BBU-interconnecting provides smooth expansion for the DBS3800. The network

can support the evolution from 3 x 1 to 3 x 2.

Thus, the WCDMA RAN5.1 enables a larger variety of radio access networks to be deployed.

High efficiency power amplifier supported

The UMTS RAN5.1 introduced the DPD + Doherty power amplifier.

The digital pre-distortion (DPD) is linearity technology which features stability, wider signal

band and ability to process multi-carrier signals. The Doherty technology is used to separately

amplify the average part and the peak part of the input signal and then combine both to

achieve high efficiency.

The efficiency of Huawei DPD + Doherty PA is 33% and above.

For the Node B BTS3812E and BTS3812AE, the output power at the Node B antenna port

can be up to 40 W. DBS3800, the output power at the Node B antenna port can be up to 40 W.

The support provided by two carriers and high output power for one RF module (MTRU or

RRU) facilitates smooth capacity expansion, and no additional RF modules are required when

the single-carrier configuration is upgraded to the dual-carrier configuration

Enhancement

None.

Dependency

None.


Availability




Summary




Benefits


Wider product ranges, including new products and configurations

The iDBS3800 is one of the best solutions for indoor coverage.

Usability enhancements, reducing operating costs

Description



functions for RAN as well as UEs. The major new feature that is introduced in the 3GPP

Release 6 is the high speed uplink packet access (HSUPA). All relevant interfaces are updated

according to the March 2006 version of Release 6.



BTS3812E/AE supports Band V (850 MHz) MTRU, 2 carriers 40 W

BTS3812E/AE supports Band VIII (900 MHz) MTRU, 2 carriers 40 W

DBS3800 supports Band V (850 MHz) RRU, 2 carriers 40 W

DBS3800 supports Band VIII (900 MHz) RRU, 2 carriers 40 W

iDBS3800, which is for indoor coverage.

BTS3812AE, a new outdoor macro Node B, improves the outdoor cabinet compared

with BTS3812A.

The iDBS3800 is one of the best solutions for indoor coverage. The iDBS3800 contains three

parts: the Base Band Unit (BBU), the Radio HUB (RHUB) and the Pico Remote Radio Unit

(Pico RRU). The Pico RRU connects to the RHUB through the CAT5 interface, and one

RHUB can support a maximum of 8 Pico RRUs. The RHUB connects to the BBU through the

optic fibers, and the BBU can support a maximum of 24 RHUBs.

The iDBS3800 supports multiple networking modes. It supports up to 192 RF front-end units.

The RRU can be networked with the passive distributed antenna system (PDAS) or work as

the active distributed antenna system (ADAS). The solution is applicable to the requirements

of buildings and districts on different scales.

The iDBS3800 supports the transmission over optic fibers or the CAT 5 cables. The RHUB

can also provide the remote power supply to the Pico RRU. Thus, the iDBS3800 can be

deployed easily and quickly, thus reducing the engineering cost.



Enhancement

None.

Dependency

None.


Availability

This feature is available from RAN 6.1.

Summary


functions, which meets a wider range of customer requirements, improves the performance of

the product, and enhances some features.

Benefits


Wider product range, including new products and configurations

The BSC6810 provides higher capacity and tighter structure.

New features and enhancement.

Description



functions for RAN and UE. The major new feature that is introduced in the 3GPP Release 6 is

the HSUPA. All relevant interfaces are updated according to the March 2006 version of

Release 6.





BSC6810, the new platform RNC based on IP switch for higher capacity with compact

structure.

Clock server, the new equipment to provide synchronization signals for the Node B

A new RRU module RRU3804 is introduced in DBS3800 (2100 MHz). RRU3804

supports 60W TOC with A-Doherty 4 carrier.

DBS3800 supports Band IV (1700 MHz / DL 2100 MHz) RRU, 2 carriers 40 W

900 MHz Same band Antenna Sharing Unit (SASU), Same band Antenna Sharing

Adapter (SASA) provide a solution for the intra-band antenna system shared between the

GSM900 and UMTS900

The Node B supports the AISG2.0 protocol.

The RRU3804 is a high output power remote radio unit with four carriers; the output

power at the antenna port is 60W. The RRU optimizes the mechanical layout, the new

slim shape leads to easy deployment. Due to the natural heat dissipation, the RRU

without fan improves the reliability and reduces the maintenance cost.

New features and enhancement supported

IP transmission on the Iu/Iur interface

IP transmission on the Iu/Iur interface is available from RAN6.1, which decreases the

transport cost to a great extent compared with the ATM transport cost.

Iu flex enhancement

The Iu flex enhancement includes enhanced load balancing and load re-distribution. This

feature improves the performance and meets the operators’ load distribution strategy in

the Iu flex networking scenario.

RAN sharing phase2

In RAN sharing phase2, the dedicated Iub transmission control is introduced, which

refers to the separated Iub transmission resource management for the operators sharing

the RAN. With this feature, the operators’ differentiated QoS requirement is guaranteed.

Other new features and enhancement

For details, please refer to the description and enhancement of the following chapters and

Optional Function Description of Huawei UMTS RAN6.1.

Enhancement

None.

Dependency

None.


Availability




Summary




Benefits


New generation Node Bs based on the modular structure and multi-mode platform

enhance the adaptability and the evolution capability. High output power amplifier for

the macro Node B extends the coverage and capacity, saves the number of the sites, and

provides better user experience.

Higher throughput by supporting the HSUPA Phase 2, that helps to get faster UL speed

Description

Compatibility with the 3GPP Release 6 (2007-03)


The UMTS RAN10.0 supports the following new boards and configurations in existing

products:

The enhanced base band interface (EBBI) card is used to support the HSUPA Phase2 and

more CEs. It can be co-configured with all other boards in the macro Node Bs

BTS3812E, BTS3812A, and BTS3812AE.

The enhanced baseband optical interface (EBOI) card is used to support the RRU

connection to the macro Node Bs: BTS3812E, BTS3812A, and BTS3812AE. EBOI also

supports HSUPA phase2 and more CEs. It can be co-configured with all other boards in

the macro Node B.

The enhanced uplink process (EULP) card is used to support the HSUPA Phase2 and

more CEs, used in the macro Node Bs: BTS3812, BTS3812A, BTS3812E, and

BTS3812AE. The EULP can be co-configured with other boards in the macro Node B.

The extension base band card (EBBC) is used to support the HSUPA Phase2 and more

CEs in the BBU3806. The EBBC can support hot plugging. With the BBU+EBBC, six

cells are supported.

The BTS3812E/AE supports the WCDMA Radio Frequency Unit (WRFU), a high

compact RF module integrated with MTRU functions and MAFU functions. The WRFU

supports 80W maximum output power and four carriers. With the WRFU,

BTS3812E/AE can expand configuration to support 3 sectors * 6 carriers or 3 sectors *

8carries.

The GTPu is re-arrayed for the unified interface board.

The POUa board of the BSC6810 supports IP over channelized STM-1/OC-3 (CPOS)

Based on the new hardware platform, the UMTS RAN10.0 introduces the new Node B

product portfolio as follows:

Indoor baseband unit BBU3900.

Indoor radio filter unit WRFU. The WRFU provides four carriers and 80-W nominal

output power. Only Band 1 (2100 MHz) WRFU will be released in RAN10.0.



Outdoor remote radio unit RRU3804. The RRU3804 provides four carriers and 60-W

nominal output power. Band 1 (2100 MHz), Band II (1900 MHz), Band IV (1700 MHz /

DL 2100 MHz), and Band V (850 MHz) RRU3804 will be released in RAN10.0

Different combinations of the units and auxiliary devices compose the following 3900

series Node Bs: DBS3900/BTS3900/BTS3900A can support up to 24 cell carriers. They

support Omni directional, 2-sector, 3-sector, or 6-sector configuration. The maximum

capacity of the 3900 series Node B is 1536 CEs in the uplink and 1536 CEs in the

downlink.

New features and enhancement supported

HSUPA Phase 2

This feature is the enhancement of the HSUPA Phase 1. The main enhancement includes:

− Peak rate: 5.76 Mbit/s per user (5.74 Mbit/s (MAC) per user)

− 2 ms / 10 ms TTI

− Max users per cell : 60

− UL compress mode (10 ms and 2 ms)

− Enhanced fast UL scheduling

− SRB over HSUPA, etc.

HSDPA Phase 4

This feature is the enhancement of the HSDPA Phase 3. The main enhancement includes:

− F-DPCH

− MBMS over HSDPA (PtP)

− HS-DPCCH preamble mode

− Peak rate: 14.4 Mbit/s per user (13.976 Mbit/s (MAC) per user)

− SRB over HSDPA, and so on

HSPA over Iur

VoIP over HSPA (trial)

Enhanced MBMS broadcast

Robust header compression (RoHC)

Multi band HO based on service priority and band

Active queue management (AQM)

IP transmission enhancement

The following new interface ports are supported:

− IP over STM-1/OC-3c (POS)

− IP over channelized STM-1/OC-3 (CPOS)

Enhancement for the existing port:

− Backup between IP over E1 and IP over FE

− BFD and ARP checking, etc.

Other new features and enhancement

For details, please refer to the Description and Enhancement in the following chapters

and the Optional Function Description of Huawei UMTS RAN10.0.

Enhancement

None.



Dependency

None.


Availability


Summary


functions, thus meeting the customer’s requirements in a wider range and improving product

performance.

Benefits

HSPA+ Phase 1 provides higher bandwidth and shorter delay:

Provides higher throughput and improves the system capacity greatly. This enables the

operator to make more profits.

Provides a higher peak rate for users and a higher speed of data downloading for the UE.

Improves user experience and provides comprehensive functions for operators.

With the optimization of capacity and performance of VoIP over HSPA/HSPA+, this feature

meets the commercial deployment requirement of VoIP and improves the competitiveness of

operators.

The high throughput of the RNC meets operators' requirements for constructing wideband

radio networks based on HSPA and HSPA+. It can also effectively adapt to the fast

development of data services.

Description

RAN11.0 introduces HSPA+ to meet the increasing demand of subscribers for the bandwidth.

HSPA+ provides higher bit rates and shorter delay. RAN11.0 supports HSPA+ Phase 1, e.g.

64QAM, 2 x 2MIMO, and CPC.

RAN11.0 optimizes the capacity and performance of VoIP over HSPA/HSPA+, and provides

comprehensive functions for the commercial deployment of VoIP over HSPA/HSPA+.

In compliance with the 3GPP R7 2008-03, RAN11.0 provides the following new features and

enhancements:

HSPA+ Phase 1:

− 64QAM (downlink): provides a higher peak rate of 21 Mbit/s and increases the

downlink capacity through high order modulation.

− 2 x 2MIMO: provides a higher peak rate of 28.8 Mbit/s and increases the downlink

capacity through parallel downlink bit streams.

− Enhanced layer 2: provides flexible RLC PDU size, as the basis for 64QAM, MIMO,

and the enhanced CELL_FACH function.



− CPC: reduces user access time, increases the air interface capacity, and lowers UE

power consumption (prolongs the battery service life).

− Enhanced CELL_FACH: provides a higher peak rate of 1 Mbit/s in CELL_FACH

state.

Commercial deployment of VoIP over HSPA/HSPA+: improves the capacity and

performance of VoIP over HSPA/HSPA+, and fully meets the requirement for

commercial deployment.

DSAC

Optimized RNC upgrade: shortens the upgrade time and reduces the negative impact on

services.

Improved RNC capacity: improves the BSC6810 throughput to 3.91G.

Newly added board: The BTS3812E/AE has a new downlink baseband processing unit,

namely, EDLP. The EDLP provides a downlink processing capacity of six cells, 384 CEs,

and DL 64QAM and MIMO of HSPA+.

Enhancement

None.

Dependency

None.


Availability


Summary

This feature is based on new boards in RNC, which meet the customer’s requirements in a

wider range and improve product performance.

Benefits

New boards are introduced in RAN11.1. With these new boards, the operators are benefited

by the merits list below:

The RNC capacity increases. The PS throughput doubles compared to that with legacy

boards.

The operators can use less hardware to reach the capacity requirement. The CAPEX is

reduced.

With new boards, the spare hardware number also saved.



Description

RAN11.1 introduces several boards, they are:

SPUb board: charge in control plane service processing

DPUe board: charge in user plane data processing

AOUc: ATM interface board with 4 CSTM-1 exports

UOIc: ATM interface board with 8 STM-1 exports

POUc: IP interface board with 4 STM-1 exports

FG2c: IP interface board with 12 FE or 4 GE exports

GOUc: IP interface board with 4 GE exports

With the new boards, the RNC capacity increases.

Enhancement

None

Dependency

None


Availability


Summary

This feature provides the following functions:

Complies with the 3GPP Release 8 specifications (March 2009).

Adds new hardware to the Node B to meet operators' requirements for capacity

expansion and function improvement.

Increases system energy efficiency and supports green energy.

Enhances system maintainability.

Benefits

Operators benefit from the following aspects of this feature:

Complies with the 3GPP Release 8 specifications, improves user experience, and

increases system capacity.

Supports higher uplink rate and larger system capacity by adding new hardware to the

Node B.

Increases system energy efficiency, supports green energy, and thus reduces operators'

OPEX.

Enhances maintainability and thus reduces operation and maintenance (OM) costs.



Description Complying with the 3GPP Release 8 specifications (March 2009)

The RAN12.0 features are developed in compliance with the 3GPP Release 8

specifications. In 3GPP Release 8, a new series of important functions concerning the

radio access network and UEs are introduced. These features include UL Layer 2

Improvement, DL 64QAM+MIMO, and Dual Cell-HSDPA (DC-HSDPA), which are

supported by Huawei RAN12.0. In addition, all relevant interfaces are updated according

to the 3GPP R8 specifications (March 2009).

Adding new hardware to the Node B to meet operators' requirements for capacity

expansion and function improvement

With PS services growing rapidly, the demand for uplink data rates from users increases.

The features such as UL 16QAM, Interference Cancellation (IC), and Frequency Domain

Equalization (FDE) further improve the uplink single user throughput and cell

throughput, and shorten file upload delay for PS users.

The existing baseband boards do not support UL 16QAM, IC, FDE. In this case, the

Node B needs to be configured with the following new baseband boards to meet

operators' requirements for capacity expansion and function improvement:

− WBBPd for the BBU3900, which is responsible for the enhanced uplink and

downlink channels user plane processing;

− EBBCd for the BBU3806, which responsible for the enhanced uplink and downlink

channels user plane processing;

− EULPd for the BTS3812E/BTS3812AE, which responsible for the enhanced uplink

channels user plane processing.

− New RF unit: RRU3806 for DBS3800/DBS3900

The more descriptions of these boards can be obtained in Node B product description.

Increasing system energy efficiency and supporting green energy

Currently, energy saving, emission reduction, and green energy become operators' major

concerns. RAN12.0 further optimizes the algorithm of Energy Efficiency Improved and

improves PA efficiency when the system is lightly loaded. In addition, the system

provides the functions of monitoring and managing green energy e.g. solar energy, and

diesel power.

Enhancing system maintainability

− Node B hardware self-diagnosis: The boards perform the self-diagnosis function to

determine whether the fault on the live network is a board fault.

− Optimized software management: In the uplink, different Differentiated Service Code

Point (DSCP) values and Virtual Local Area Network (VLAN) Class of Service (COS)

values can be set for OM services of different characteristics. The VLAN COS values

indicate the priorities of traffic streams. In the downlink, limitation is applied to the

speed of download by FTP and downlink windows are properly arranged so that

services are not affected by FTP.

− Improved transmission maintainability and testability: Transmission maintainability

and testability are improved for both ATM and IP transport through the support PVC,

CID (for ATM) or UDP (for IP) loopback functions. They are used to identify

transmission link faults accurately. The transport layer implements 24-hour online

testing/counting functions, including measurements of packet loss ratio, delay, and

jitter. Users can obtain statistical information only through one command.



Enhancement

None.

Dependency

None.



2 Standards Compliance

2.1 WRFD-010101 3GPP R8 Specifications

Availability


Summary

The UTRAN system software of RAN12.0 complies with the 3GPP Release 8 specifications

(March 2009).

Benefits

The compliance with 3GPP Release 8 provides a basis for implementing the new features and

enhanced functions defined in 3GPP Release 8. This also enables the provision of more

high-performance services and thus increases operators' competitive edge.

This feature enables the interconnection with other network elements (NEs) that comply with

3GPP Release 99, Release 4, Release 5, Release 6, Release 7, or Release 8, thus protecting

operators' investment.

Description

RAN2.0 complies with 3GPP Release 99/Release 4.

RAN3.0 and RAN5.0 comply with 3GPP Release 99/Release 4/Release 55.

RAN6.0 and RAN6.1 comply with 3GPP Release 99/Release 4 /Release 5/Release 6 (March

2006) and CR.

RAN10.0 complies with 3GPP Release 99/Release 4 /Release 5/Release 6 (March 2007).

RAN11.0 complies with 3GPP Release 99/Release 4 /Release 5/Release 6/Release 7 (March

2008).

RAN12.0 complies with 3GPP Release 99/Release 4/Release 5/Release 6/Release 7/Release 8

(March 2009). In Release 8 features such as DC-HSDPA and 64QAM+MIMO are available

which offers higher data rate for single user. Other features like fast dormancy are also

introduced in Release 8.



Enhancement

None.

Dependency

Dependency on RNC hardware

None.

Dependency on Node B hardware

None.

Dependency on other RAN features

None.

Dependency on other NEs

For the new features introduced in 3GPP Release 8 and the enhanced features of interfaces,

the core network interfaces and user interfaces also need to be upgraded to ensure compliance

with the protocols.

2.2 WRFD-010102 Operating Multi-band

Availability


Summary

This feature meets the requirement of the operators for use of different frequency bands in

different regions. In addition, the Node B supports the co-cabinet of different frequency bands,

thus saving the deployment cost for the operators and meeting the space requirement.

Benefits

The Node Bs can be deployed widely according to the operator’s frequency requirement.

The multi-band supported Node B can save the cost of the hardware investment.

Description

The following 3GPP defined UMTS frequency bands are supported.

Operating Band UL Frequencies

UE transmit, Node

B receive

DL frequencies

UE receive, Node B

transmit

Band I (2100M) 1920–1980 MHz 2110–2170MHz

Band III/IX (1800M) 1710–1785 MHz 1805–1880 MHz

Band II (1900M) 1850–1910 MHz 1930–1990MHz



Band V/VI (850M) 824–849MHz 869–894MHz

Band VIII (900M) 880–915 MHz 925–960 MHz

Band IV(1.7/2.1G) 1710–1755 MHz 2110–2155 MHz

The macro Node Bs provide multi-band co-located in one cabinet. Due to the flexible design

of Huawei Node B architecture, the multi-band only has impact on the RF system. The

baseband modules including power, transmission, and channel cards are shared by different

bands. The operators can use the required frequency segments to save the footprint of the

Node B and improve the baseband usage

The feature is implemented in the Node B and RNC.

Different frequency bands should be configured with different RF modules.

Enhancement

In RAN5.0, the macro Node B supports the 1900M and 1800M frequency bands.

In RAN5.1, the RRU supports the 1900M and 1800M frequency bands.

In RAN6.0, the 850M and 900M frequency bands are supported by the macro Node B and

RRU.

In RAN6.1, the AWS (UL 1700M/DL 2100M) frequency band is supported by the RRU.

The BTS3900/BTS3900A only supports Band1 2100M and 850M in RAN10.0.

Dependency

None.

2.3 WRFD-010201 FDD Mode

Availability


Summary

Huawei RAN supports the FDD mode.

Benefits

This feature defines the mode supported by Huawei RAN.

Description

The 3GPP specification comprises Frequency Division Duplex (FDD) mode and Time

Division Duplex (TDD) mode. FDD mode uses individual frequency band for the uplink and



downlink. TDD mode uses the same frequency band for the uplink and downlink. Huawei

RAN only supports FDD mode.

Enhancement

None.

Dependency


The relevant NEs should comply with the 3GPP specifications in FDD mode.



3 RABs and Services

3.1 WRFD-010510 3.4/6.8/13.6/27.2 kbit/s RRC Connection and RAB Assignment

Availability


Summary

This feature supports the RRC connection/release of different rates and RAB assignment to

meet the QoS requirements for different services.

Benefits

This is an essential feature for the UMTS RAN.

Description

RAN11.0 supports the 3.4/6.8/13.6/27.2 kbit/s RRC connection and Radio Access Bearer

(RAB) assignment. The RNC will map the RRC connection request and the RAB assigned by

the CN according to different QoS requirements.

Mapping of channel types

For RRC connection, the operators can decide which channel type (CCH/DCH) should

be configured according to the RRC SETUP REQUEST message.

For RAB assignment, the operators can decide in which cell the RAB should be set up.

Mapping of RAB parameters

The associated transport channel and physical channel parameters are configured based

on the channel types. Huawei RAN provides different sets of configuration parameters

for typical services. These parameters are supported by each typical service. If no service

class matches the feature, choose the most approximate parameters. Moreover, the

operators can add new service classes and configure associated parameters. These

features can fully utilize the services supported by the system.

The PS streaming/interactive/background RAB can also be set up on the HS-DSCH or

E-DCH. These features include the following optional features:

− WRFD-010610 HSDPA Introduction Package



− WRFD-010612 HSUPA Introduction Package

− WRFD-010630 Streaming Traffic Class on HSDPA

− WRFD-010632 Streaming Traffic Class on HSUPA

SRB always occupies SF 256 at the rate of 3.4 kbit/s or 6.8 kbit/s. It can increase the signaling

transmission speed and shorten the delay at the rate of 6.8 kbit/s. Therefore, if all the

downlink services of the UE are set up on the HS-DSCH and the SRB is carried on the DCH

in the downlink, the SRB has a rate of 6.8 kbit/s.

Enhancement

RAN3.0 supports RRC connection of 13.6 kbit/s.

RAN6.1 supports RRC connection of 27.2 kbit/s.

RAN11.0 supports RRC connection of 6.8 kbit/s and the retainment of SRB of 6.8 kbit/s.

Dependency

None.

3.2 WRFD-010501 Conversational QoS Class

Availability


It is introduced in 3GPP R99.

Summary

The RNC supports the conversational services of CS and PS domains issued from the CN and

sets up appropriate RABs based on the QoS.

Benefits

The QoS-supported conversational services provide guaranteed QoS for upper-layer services.

Description

QoS classes also refer to traffic classes. The following four QoS classes are defined in 3GPP:

Conversational class

Streaming class

Interactive class

Background class

The main difference between the preceding QoS classes lies in the extent to which the traffic

is delay sensitive. Conversational class is meant for traffic which is very delay sensitive and is

mainly used to carry real time traffic flows. Fundamental characteristics for real time

conversational QoS class include the following:



Preserved time relations (variation) between information entities of the stream.

Conversational pattern (stringent and low delay).

There are conversational class services in both CS and PS domains. The most well known

conversational traffic is speech and video phone services in CS domain and VoIP in PS

domain.

Huawei RAN supports the following conversational services as fundamental features:

CS AMR speech services of 8 rates, including 12.2 kbit/s, 10.2 kbit/s, 7.95 kbit/s, 7.4

kbit/s, 6.7 kbit/s, 5.9 kbit/s, 5.15 kbit/s, and 4.75 kbit/s. The RNC selects SF256 for

AMRS services whose maximum rate is lower than 7.95 kbit/s.

CS transparent data services (conversational class) with 64 kbit/s, 56 kbit/s, 32 kbit/s,

and 28.8 kbit/s.

PS bidirectional symmetric speech services at the rates of 64 kbit/s, 42.8 kbit/s, 32 kbit/s,

16 kbit/s, and 8 kbit/s.

Enhancement

None.

Dependency


Both CN and UE should support this service.

3.3 WRFD-010502 Streaming QoS Class

3.4 WRFD-010502 Streaming QoS Class

Availability



Summary

The RNC supports the streaming services of CS and PS domains issued from the CN and sets

up appropriate RABs based on the QoS.

Benefits

The QoS-supported steaming services provide guaranteed QoS for upper-layer services.

Description





Streaming class

Interactive class

Background class


is delay sensitive. Streaming class is new to data communication, thus it raises a number of

new requirements in both telecommunication and data communication systems. Streaming

class is characterized by the time relations (variation) between information entities (i.e.

samples, packets) of the stream that should be preserved, although it does not have strict

requirements on transfer delay. Fundamental characteristics of streaming QoS class include

the following:

Preserved time relations (variation) between information entities of the stream:

There are streaming class services in both CS and PS domain. The most well known

streaming traffic is FAX in CS domain and streaming video in PS domain.

Huawei RAN supports the following streaming services as fundamental features:

CS nontransparent data services of 57.6 kbit/s.

PS bidirectional symmetric or asymmetric streaming services at the rates of 384 kbit/s,

256 kbit/s, 144 kbit/s, 128 kbit/s, 64 kbit/s, 32 kbit/s, and 8 kbit/s.

PS unidirectional asymmetric streaming services at the rates of 384 kbit/s, 256 kbit/s,

144 kbit/s, 128 kbit/s, 64 kbit/s, 32 kbit/s, 8 kbit/s.

PS streaming service can also be carried on HSDPA and HSUPA which are optional features

and described in WRFD-010610 HSDPA Service and WRFD-010612 HSUPA Service.

Enhancement

RAN6.0 supports PS 384 kbit/s bidirectional symmetric or asymmetric streaming service.

Dependency



3.5 WRFD-010503 Interactive QoS Class

Availability



Summary

The RNC supports the interactive services of CS and PS domains issued from the CN and sets

up appropriate RABs based on the QoS.



Benefits

The QoS-supported interactive services provide guaranteed QoS for upper-layer services.

Description



Streaming class

Interactive class

Background class


is delay sensitive. Interactive class is another typical data communication scheme that is

characterized by the request response pattern of the end-user. At the message destination,

there is an entity expecting the message (response) within a certain time. Round trip delay

time is therefore one of the key attributes. Another characteristic is that the contents of the

packets are transparently transferred (with low bit error rate). Fundamental characteristics of

Interactive QoS class include the following:

Request response pattern.

Preserve payload content.

Interactive class services apply only to the PS domain. The most well known interactive

traffic is web browsing.

Huawei RAN supports the following interactive services as fundamental features:

PS bidirectional symmetric or asymmetric interactive services at the rates of 384 kbit/s, 256

kbit/s, 144 kbit/s, 128 kbit/s, 64 kbit/s, 32 kbit/s, 16 kbit/s, 8 kbit/s and 0kbit/s.

The higher rates can only be supported on HSDPA and HSUPA which are optional features


Enhancement

RAN3.0 supports UL PS service of 384 kbit/s.

Dependency



3.6 WRFD-010504 Background QoS Class

Availability





Summary

The RNC supports the background services of CS and PS domains issued from the CN and

sets up appropriate RABs based on the QoS.

Benefits

The QoS-supported background services provide guaranteed QoS for upper-layer services.

Description



Streaming class

Interactive class

Background class


is delay sensitive. Background class is one of the typical data communication schemes. It is

characterized by the fact that the destination does not expect the data within a certain time.

The scheme is thus more or less insensitive to the delivery time. Another characteristic is that

the contents of the packets are transparently transferred (with low bit error rate). Fundamental

characteristics of background QoS class include the following:

The destination does not expect the data within a certain time.

The payload content is preserved.

Background class services apply only to the PS domain. The most well known background

traffic is background download or E-mails.

Huawei RAN supports the following background services as fundamental features:

PS bidirectional symmetric or asymmetric background services at the rates of 384 kbit/s, 256

kbit/s, 144 kbit/s, 128 kbit/s, 64 kbit/s, 32 kbit/s, 16 kbit/s, 8 kbit/s and 0kbit/s.

The higher rates can only be supported on HSDPA and HSUPA which are optional features


Enhancement

RAN3.0 supports UL PS service of 384 kbit/s.

Dependency





3.7 WRFD-010609 Multiple RAB Introduction Package (PS RAB < 2)

Availability



Summary

This feature provides multi-service combinations to meet the request for concurrent services.

Benefits

Multi-RAB support capability provides operators with more service solution choices.

Description

Multi-RAB can provide more abundant services simultaneously to the upper layer. In the case

of multi-RAB that has less than two PS RABs, Huawei supports the following specifications:

Combination of two CS services (except for two AMR speech services)

One CS service + one PS service

Two CS services + one PS service (except for two AMR speech services)

In all the preceding combinations, the bit rates of CS and PS services are not limited. That is,

any bit rates of CS and PS services defined in WRFD-010501 Conversational QoS Class,

WRFD-010502 Streaming QoS Class, WRFD-010503 Interactive QoS Class, and

WRFD-010501 Background QoS Class can be selected in the combination.

The PS conversational/streaming/interactive/background services can also be mapped to

HS-DSCH or E-DCH. These features need the support of the optional features WRFD-010610

HSDPA Introduction Package and WRFD-010612 HSUPA Introduction Package.

Enhancement

None.

Dependency


Both CN and UE should support the specifications for multiple RABs.

3.7.1 WRFD-01060901 Combination of Two CS Services (Except for Two AMR Speech Services)

Availability




Summary

Huawei supports combination of two CS services (except for two AMR speech services).

Benefits


Description

Huawei supports combination of two CS services (except for two AMR speech services).

Enhancement

None.

Dependency



3.7.2 WRFD-01060902 Combination of One CS Service and One PS Service

Availability


Summary

Huawei RAN supports the combination of one CS service and one PS service.

Benefits


Description

Huawei RAN supports the combination of one CS service and one PS service.

Enhancement

None.

Dependency





3.7.3 WRFD-01060903 Combination of Two CS Services and One PS Service (Except for Two AMR Speech Services)

Availability


Summary

Huawei RAN supports the combination of two CS services and one PS service (except for

two AMR speech services).

Benefits


Description

Huawei RAN supports the combination of two CS services and one PS service (except for

two AMR speech services).

Enhancement

None.

Dependency



3.8 WRFD-021104 Emergency Call

Availability



Summary

This feature provides the emergency call a higher priority over common calls to ensure that

the emergency call gets preference to access the network.

Benefits

It is an essential feature for UMTS RAN. It enables the emergency call to have a higher

priority over other services in resource allocation.



Description

When an emergency call is triggered, “Establishment Cause” in the RRC Connection Request

message is set to “Emergency Call”.

Emergency call always has priority over the ordinary calls. When enough resources are not

present in the cell, pre-emptive action is triggered on ordinary calls with lowest priority to

guarantee that the emergency call can access the network and be served.

Enhancement

None.

Dependency

None.



4 RAN Architecture & Functions

4.1 MRFD-210604 2-Way Antenna Receive Diversity

Availability

This feature is available from GBSS6.1 and RAN 2.0.

Summary

This feature is a technique for improving the receive performance of the uplink channels.

Benefits

This feature improves receiver sensitivity and uplink coverage, thus reducing the CAPEX.

Description

With this feature, the same signal is received by two antennas. Then the two ways of signals

on the two antennas are combined after being processed. Thus, the signal attenuation is

reduced.

This feature enhances the RX capability of uplink channels. Huawei MBTS supports both

receive diversity and none receive diversity.

With this feature, the MBTS does not require additional devices and algorithms. Compared

with one-way none receive diversity, this feature requires twice the number of RX channels.

In typical scenarios, the receiver sensitivity can be improved by 2 to 3 dB.

Enhancement

None.

Dependency

Impacts on the hardware of the MBSC

None.

Impacts on the hardware of the MBTS

In receive diversity mode, the Node B should provide sufficient RF channels and

demodulation resources to meet the requirements for the number of antenna diversities.



Dependency on other features of the GBSS/RAN

None.


None.

4.2 WRFD-010205 Cell Digital Combination and Split

Availability


Summary

This feature enables multiple sectors to use the resources in the same cell, thus improving

system spectrum efficiency and resource utilization. The DBS3800, DBS3900, iDBS3800,

and iDBS3900 support this feature.

Benefits

Compared with the analog combination and split, the digital combination and split can

provide larger capacity and wider coverage without bringing additional noises and signal

losses. In this manner, cell distribution can be adjusted through software to adapt to actual

traffic distribution and changes, thus improving CE resource utilization and operation

benefits.

Description

Cell split means that a cell in the Node B is split into multiple sectors through the digital

combination and split and the sectors can cover multiple areas. Cell split applies to scenarios

such as indoor coverage and high-speed railway or expressway coverage. Based on cell split,

the antennas in different sectors can transmit and receive signals from the same cell. When

expanding the capacity or adjusting the network, you can flexibly configure the mapping

between the RRU and cell through software without changing the hardware. The DBS3800,

DBS3900, iDBS3800, and iDBS3900 support cell split and digital combination and split.

The following figure shows the logical structure of the digital combination and split. The

downlink digital split means that a downlink signal is split into two signals, that is, the

downlink signal from the upper-level RRU or baseband unit is simultaneously sent to the RF

Tx path of the RRU and the lower-level RRU. The uplink digital combination means that two

uplink signals are combined into one signal, that is, the uplink signals from the RF Tx path of

the RRU and the lower-level RRU are combined and then sent to the upper-level RRU or

baseband



unit.

Each RRU or pRRU has an independent antenna that covers different sectors. One cell can be

set for multiple RRUs so that they have the same scrambling code.

This feature is introduced to Huawei pRRU and RRU, and it can be applied to indoor

coverage scenario.

Enhancement

None.

Dependency


Only DBS3800/DBS3900 and iDBS3800/iDBS3900 support this feature, RRU3801c cannot

support this feature.

4.3 WRFD-010208 Fast Power Congestion Control (FCC)

Availability


Summary

Fast power congestion control (FCC) is implemented on the Node B side. This feature aims to

quickly rectify system overload to prevent the output power from exceeding the maximum

power allowed by hardware.

RRU

Combined

RF Tx Path

RF Rx Path

Du

ple

xer

CPRI

Interface

CPRI

Interface

Slave

Uplink

Split

Master

Upper-level RRU or BBU

Lower-level RRU



Benefits

This feature enables full utilization of Power Amplifiers for traffic load, especially for

dynamic power sharing in one carrier between R99 and HSDPA.

Description

FCC is a Node B function that complements the RNC congestion control. The function

supervises the output power per slot that users (all users) demand at the same time, using the

same time scale as the fast power control function.

Huawei provides the DL automatic level control (ALC) function as the method of fast power

congestion control in the Node B, in order to limit the output power and avoid the PA

saturation. The ALC supervises the transmit power in real time. When the input power reaches

or exceeds the predefined threshold, the ALC can increase the TX channel attenuated signals

to keep the output power lower than the threshold, thus avoiding the PA saturation.

The Node B uses the FCC to quickly control the output power, the control Reaction time is

1024chip, which is fast enough to fully prevent saturation of the TX chain or overdriving of

the power amplifier without the need for power margins.

Therefore, cell behavior remains robust at maximum load without running the risk of dropped

cells or modulation inaccuracy. In addition, the RNC congestion and admission thresholds can

be set to higher levels, which increase cell capacity without compromising overall quality of

service.

Enhancement

None.

Dependency

None.

4.4 WRFD-010211 Active TX Chain Gain Calibration

Availability


Summary

This feature enables the monitoring and adjustment of digital channel gains, thus ensuring

stable output power.

Benefits

This feature provides high output power accuracy for the Node B, and reduces the margins

required in network dimensioning. Thus, the entire power can be used for traffic.



Description

The active TX chain gain calibration can increase the accuracy of the downlink transmit

power (for example, the power accuracy of the 3900 series Node B is +/- 0.6 dB), thus

reducing the protection band reserved for power calculation in network planning and

improving the utilization of transmit power.

Performance drift occurs on all RF hardware. An RF part (for example, TRX, PA, RF

connector, or duplexer) has a different gain due to different temperatures, frequencies, and lot

numbers. Such a gain difference leads to a 1.5 dB to 2 dB error in the Node B transmit power.

The active TX chain gain calibration can reduce the changes in analog channel gains caused

by different temperatures, frequencies, and lot numbers, thus ensuring a stable total gain of

links. The active TX chain gain calibration calculates the difference between the downlink

input power and transmit power and then adjusts digital channel gains according to the

transmit power on the analog channel. Gain control is performed in real time, thus ensuring

the accuracy of transmit power.

Enhancement

None.

Dependency

None.

4.5 WRFD-010202 UE State in Connected Mode (CELL-DCH, CELL-PCH, URA-PCH, CELL-FACH)

Availability


Summary

Huawei RAN supports four states of the UE in connected mode: URA_PCH, CELL_PCH,

CELL_FACH, and CELL_DCH. This feature can save radio resources effectively.

Benefits

This feature enables UEs to select associated states according to the QoS requirements. It

increases the utilization of resources and system capacity, and users do not feel the degrade of

network performance. This feature is a mandatory feature of the UMTS RAN.

Description

The 3GPP specifications define four states of the UE in connected mode: CELL_DCH,

CELL_PCH, URA_PCH, and CELL_FACH. Huawei RAN supports these four UE states.

URA_PCH/CELL_PCH



In the URA_PCH/CELL_PCH state, the UE has no available DCCH or DTCH. When

the UE initiates a call or receives a paging message from the core network, it starts the

CELL_UPDATE procedure. It can also use the periodic URA UPDATE or

CELL_UPDATE procedure to maintain the connection with the network. The UE is not

assigned the DCCH or DTCH. Therefore, the UE does not consume radio resources, and

no service is available.

CELL_FACH

In the CELL_FACH state, the UE maps the DCCH and DTCH to the common channel

that carries RRC signaling and traffic data. The UE also performs cell reselection

through the Cell Update procedure to camp on an appropriate cell. Different UEs can

share common resources. Therefore, the QoS of some services, for example,

transmission delay and bandwidth, cannot be ensured.

CELL_DCH

In the CELL_DCH state, the UE maps the DCCH and DTCH to the dedicated channel

that carries RRC signaling and traffic data. When the cell load increases, the QoS of

services can be ensured because dedicated resources are allocated. When the UE uses the

HSDPA or HSUPA services, it stays in the CELL_DCH state.

These four states can change according to the characteristics of services used by the UE. This

process is called channel type switching. For details, see WRFD-021101 Dynamic Channel

Conversion Configuration (DCCC).

For details on the channel type switching in the HS-DSCH state and other states, see

WRFD-01061111 HSDPA State Transition.

RAN12.0 supports the Fast Dormancy procedure of the UE. The process for enabling UEs

whose version are below 3GPP R8 to enter the power saving mode is controlled by the

inactive timer delivered by the network side, which takes a lot of time. Currently, some UEs

of 3GPP Release 8 support the Fast Dormancy function defined in 3GPP TS 25.331 CR3483.

When the UE performs only PS services and the PS data transfer is complete, the UE

immediately sends the RNC the SIGNALLING CONNECTIONI RELEASE INDICATION

message, which carries the cause value "UE Requested PS Data session end." Upon receiving

the message, the RNC releases the RRC connection of the UE and enables the UE to rapidly

enter the power saving mode.

Enhancement

In RAN2.0, the four states and transition algorithm are implemented.

RAN5.0 introduces the HSDPA feature and thus supports UEs in the CELL_DCH (HS-DSCH)

state.

RAN6.0 introduces the HSUPA feature and thus supports UEs in the CELL_DCH (E-DCH)

state.

RAN12.0 supports the Fast Dormancy procedure of the UE.

Dependency

Dependency on the RNC hardware

None.

Dependency on the Node B hardware

None.




None.


UEs must support associated states.

The Fast Dormancy procedure of the UE must comply with 3GPP TS 25.331 CR3483.

4.6 WRFD-010401 System Information Broadcasting

Availability


Summary

This feature supports system information as stipulated in multiple protocols. Based on the

system information, the network can provide UEs with rich access layer and non access layer

information required for running UEs on the network, and the information that controls UE

behavior.

Benefits

This feature provides UEs with rich access layer and non access layer information required

for running UEs on the network, and the information that controls UE behavior.

Description

System information broadcasting which is required by the UE for its operation in the network

provides UE with the Access Stratum and Non Access Stratum information.

The system information is organized in a tree-type manner. A master information block gives

references and scheduling information to a number of system information blocks in a cell. The

system information blocks contain the actual system information.

Scheduling of system information blocks is performed by the RRC layer in UTRAN. RRC

can automatically calculate the repetition period and position of each SIB segment based on

its importance.

The key information of each SIB Huawei supported is listed in the following table.

System Information Block

Area Scope

Content

Master information

block

Cell SIB scheduling information

Scheduling block 1 Cell SIB scheduling information

Scheduling block 2 Cell SIB scheduling information



System Information Block

Area Scope

Content

SIB1 PLMN NAS information and timers used by UE in connected

mode and idle mode

SIB2 Cell URA Id

SIB3 Cell Parameters of cell selection and reselection in idle

mode

Parameters of hierarchical cell in idle mode

SIB4 Cell Parameters of cell selection and reselection in

connected mode

Parameters of Hierarchical cell in connected mode

(CCH state)

SIB5 Cell Parameters of common physical channels for UE in

idle mode(PRACH, AICH, PICH, S-CCPCH)

SIB6 Cell Parameters of common physical channel in connected

mode

SIB7 Cell UL interference, dynamical persistence level

SIB11 Cell Measurement control information in idle mode

SIB12 Cell Measurement control information in connected mode

SIB18 Cell PLMN ID of neighboring cells

Enhancement

RAN5.0 supports SIB4, SIB6, and SIB12.

RAN10.0 supports SIB11 bis. SIB11 bis contains cell measurement control information, new

intra-frequency cell information, new inter-frequency information, and new inter-RAT cell

information.

Dependency

None.

4.7 WRFD-010301 Paging UE in Idle, CELL_PCH, URA_PCH State (Type 1)

Availability




Summary

This feature supports paging type 1. UTRAN sends a paging message to the UE in idle,

CELL_PCH, or URA_PCH state through the paging control channel (PCCH).

Benefits

When an UE is in idle, CELL_PCH, or URA_PCH state, UTRAN sends a paging message to

the UE through the PCCH.

Description

Paging type 1 procedure is used to transmit paging information to the selected UEs in idle

mode, CELL_PCH or URA_PCH state using the PCCH. With this feature, upper layers in the

network can:

Trigger UE establishing a RRC signaling connection.

Trigger CELL UPDATE procedure of UE in CELL_PCH or URA_PCH state.

Trigger reading of updated system broadcast of UE in idle mode, CELL_PCH or

URA_PCH state.

Trigger releasing signaling connection of UE in CELL_PCH or URA_PCH state.

Enhancement

None.

Dependency

None.

4.8 WRFD-010302 Paging UE in CELL_FACH, CELL_DCH State (Type 2)

Availability


Summary

This feature supports paging type 2. The network can control the UE in CELL_FACH or

CELL_DCH state through the dedicated control channel (DCCH).

Benefits

The network can control the UE in CELL_FACH or CELL_DCH state which has DCCH with

paging type 2 procedures.



Description

In paging type 2, UTRAN sends a paging message to the UE in CELL_FACH or CELL_DCH

state through the DCH or FACH.

Enhancement

None.

Dependency

None.



5 Channel Resource Management

5.1 WRFD-020900 Logical Channel Management

Availability


Summary

This feature supports multiple logical channels to carry data transfer services offered by

MAC.

Benefits

This feature provides the basis for data transfer and resource management algorithm.

Description

A set of logical channel types are defined for different kinds of data transfer services offered

by MAC. Each logical channel type is defined by what type of information is transferred.

Generally, logical channels are classified into the following two groups:

Control channels (for the transfer of control plane information).

Traffic channels (for the transfer of user plane information).

Control channels are used for the transfer of control plane information. They are as follows:

Broadcast Control Channel (BCCH)

Paging Control Channel (PCCH)

Common Control Channel (CCCH)

Dedicated Control Channel (DCCH)

Traffic channels are used for the transfer of user plane information. They are as follows:

Dedicated Traffic Channel (DTCH)

Common Traffic Channel (CTCH)

MBMS Traffic Channel (MTCH)

Mapping between logical channels and transport channels is as follows:

I. In Uplink,



CCCH can be mapped to RACH;

DCCH can be mapped to RACH;

DCCH can be mapped to DCH or E-DCH;

DTCH can be mapped to RACH;

DTCH can be mapped to DCH;

DTCH can be mapped to E-DCH;

II. In Downlink,

BCCH can be mapped to BCH;

BCCH can be mapped to FACH;

PCCH can be mapped to PCH;

CCCH can be mapped to FACH;

DCCH can be mapped to FACH;

DCCH can be mapped to HS-DSCH;

DCCH can be mapped to DCH;

DTCH can be mapped to FACH;

DTCH can be mapped to HS-DSCH;

DTCH can be mapped to DCH;

CTCH can be mapped to FACH;

MTCH can be mapped to FACH;

MCCH can be mapped to FACH;

The mapping between DTCH/DCCH and HS-DSCH/E-DCH belongs to the optional features

WRFD-010610 HSDPA Introduction Package and WRFD-010612 HSUPA Introduction

Package.

Enhancement

In RAN3.0, the CTCH supporting the cell broadcast service (CBS) feature is introduced.

In RAN6.0, the MTCH and MCCH are introduced.

Dependency

None.

5.2 WRFD-021000 Transport Channel Management

Availability


This feature is introduced in 3GPP R99/R5/R6.



Summary

This feature enables Huawei RAN to support the common transport channel and dedicated

transport channel as stipulated in 3GPP R6. This feature is a basic feature of RAN.

Benefits

This feature provides the basis for data transfer and resource management algorithm.

Description

Transport channel is used to offer information transfer services to MAC and higher layers.

It is generally classified into the following two groups:

Common transport channels

Dedicated transport channels

Common transport channel types are as follows:

Random Access Channel (RACH)

Forward Access Channel (FACH)

Broadcast Channel (BCH)

Paging Channel (PCH)

High Speed Downlink Shared Channel (HS-DSCH)

Dedicated transport channel types are as follows:

Dedicated Channel (DCH)

Enhanced Dedicated Channel (E-DCH)

Enhancement

In RAN5.0, HS-DSCH supported with HSDPA feature is introduced.

In RAN6.0, E-DCH supported with HSUPA feature is introduced.

Dependency


NDLP and NBBI do not support the Management of HSUPA or HSDPA transport channel.

Dependency on other UTRAN software functions

To support the HSUPA transport channel Management, the optional feature WRFD-010612

HSUPA Introduction Package should be configured.

To support the HSDPA transport channel Management, the optional feature WRFD-010610

HSDPA Introduction Package should be configured.



5.3 WRFD-022000 Physical Channel Management

Availability


This feature is introduced in 3GPP R99/R5/R6.

Summary

This feature enables Huawei RAN to support the physical channel and the mapping between

the transport channel and physical channel as stipulated in 3GPP R6. This feature is a basic

feature of RAN.

Benefits

In compliance with the definition and requirements of the physical channel as stipulated in

3GPP specifications, this feature supports HSDPA and HSUPA services and enables the

F-DPCH to support more VoIP subscribers.

Description

A physical channel may bear several transport channels and a transport channel may be borne

by several physical channels.

The Coded Composite Transport Channel (CCTrCH) is defined as the multiplexing of several

transport channels that can be supported by one or several physical channels on the radio

interface. Some physical channels are used only by the physical layer of the radio interface.

Only the following physical channels may bear transport channels:

P-CCPCH: Primary Common Control Physical Channel

S-CCPCH: Secondary Common Control Physical Channel

PRACH: Physical Random Access Channel

DPDCH: Dedicated Physical Data Channel

HS-PDSCH: High Speed Physical Downlink Shared Channel

E-DPDCH: E-DCH Dedicated Physical Data Channel

The following 3GPP Standards define the main characteristics of the FDD Physical Channels:

[1] TS25.211 Physical channels and mapping of transport channels onto physical channels

(FDD)

[2] TS25.212 Multiplexing and channel coding (FDD)

[3] TS25.213 Spreading and modulation (FDD)

[4] TS25.214 Physical layer procedures (FDD)

The set of physical channels types supported by the Huawei Node B is described in the

following tables. The characteristics of these supported physical channels are compliant with

3GPP TS25.211. Physical channels are carried on the radio interface only in the Node B of the

UTRAN, but are managed by the RNC.



Channel Availability Direction Characteristics

PRACH

Physical

Random

Access

Channel

RAN2.0 UL

Common

PRACH is used to carry the RACH which

carries random access information of the UE

accessing the network.

It consists of one or several preambles of

length 4096 chips and a message of length 10

ms or 20 ms. The spreading factor may range

from 256 to 32.

Uplink

DPDCH

Uplink

Dedicated

Physical

Data

Channel

RAN2.0 UL

Dedicated

The uplink DPDCH is used to carry the DCH

transport channel. There may be zero, one, or

several uplink DPDCHs on each radio link.

The spreading factor may range from 256 to

4.

Uplink

DPCCH

Uplink

Dedicated

Physical

Control

Channel

RAN2.0 UL

Dedicated

The uplink DPCCH is used to carry control

information generated at Layer 1. The Layer

1 control information consists of TFCI, TPC,

Pilot bits, FBI, which is required to convey

DPDCH. There is one and only one uplink

DPCCH on each radio link.

Generally, the spreading factor is equal to

256.

P-CCPCH

Primary

Common

Control

Physical

Channel

RAN2.0 DL

Common

The Primary CCPCH is a fixed rate (30 kbps,

SF=256) downlink physical channel used to

carry the BCH transport channel which

provides system and cell specific information.

It is not transmitted during the first 256 chips

of each timeslot because P-CCPCH is

multiplexed with SCH.

S-CCPCH

Secondary

Common

Control

Physical

Channel

RAN2.0 DL

Common

The Secondary CCPCH is used to carry the

FACH and PCH. The FACH and PCH can be

mapped to the same or separate Secondary

CCPCHs.

The spreading factor range is from 256 to 4.

It has no inner-loop power control and is not

always transmitted.

P-SCH

Primary

Synchroniz

ation

Channel

RAN2.0 DL

Common

The P-SCH is used for cell search procedure

(Slot synchronization).

This channel has no scrambles or OVSF

codes. It is multiplexed with P-CCPCH.

S-SCH

Secondary

Synchroniz

ation

Channel

RAN2.0 DL

Common

The S-SCH is used for cell search procedure

(SC group identification).

Not scrambled nor OVSF coded. It is

multiplexed with P-CCPCH.




P-CPICH

Primary

Common

Pilot

Channel

RAN2.0 DL

Common

The CPICH is a fixed rate (30 kbps, SF=256)

downlink physical channel that carries a

pre-defined bit sequence.

The Primary CPICH is the phase reference

for the following downlink channels: SCH,

Primary CCPCH, Second CCPCH, AICH,

PICH, and DPCH.

There is only one P-CPICH per cell. It is

always scrambled by the Primary SC.

PICH

Page

Indication

Channel

RAN2.0 DL

Common

The PICH is a fixed rate (SF=256) physical

channel used to carry the paging indicators.

The PICH is always associated with an

S-CCPCH (mapped with PCH) to carry the

Paging Indicators (PI) informing the UE that

paging information is available on the

SCCPCH.

AICH

Acquisition

Indicator

Channel

RAN2.0 DL

Common

The AICH is a fixed rate (SF=256) physical

channel used to carry Acquisition Indicators

(AI). Acquisition Indicators corresponding to

signatures on the PRACH are used by the

network to confirm to the UE the reception of

its access (PRACH).

Downlink

DPCH

Downlink

Dedicated

Physical

Channel

RAN2.0 DL

Dedicated

The downlink DPCH can be regarded as a

time multiplex of a downlink DPDCH and a

downlink DPCCH. It carries dedicated data

generated at Layer 2 and above (i.e. the

dedicated transport channel DCH), with

control information generated at Layer 1

(pilot bits, TPC commands, and TFCI).

The spreading factor may range from 512 to

4.

HS-DPCC

H

Dedicated

Physical

Control

Channel for

HS-DSCH

RAN5.0 UL

Dedicated

The HS-DPCCH carries uplink feedback

signaling related to downlink HS-DSCH

transmission. It consists of HARQ-ACK and

CQI.

The spreading factor of the HS-DPCCH is

256

HS-SCCH

Shared

Control

Channel for

HS-DSCH

RAN5.0 DL

Common

The HS-SCCH is a fixed rate (60 kbps,

SF=128) downlink physical channel used to

carry downlink signaling related to

HS-DSCH transmission, including

modulation mode, size of a transmission

block, redundant version information, UE ID,

and HS-PDSCH code.

HS-SCCH is aligned with the PCCPCH in

timing and keeps a fixed time offset with the

HS-PDSCH. Its spreading factor is fixed as




128 and QPSK is the only modulation mode.

The number of HS-SCCHs and the channel

codes in the cell are determined by the RNC,

and are notified to the Node B through the

NBAP signaling message. When the Node B

sends the data to the UE through the

HS-PDSCH, the UE can detect one to four

HS-SCCHs that are specified by the Node B

at one time.

HS-PDSCH

High Speed

Physical

Downlink

Shared

Channel

RAN5.0 DL

Common

The HS- PDSCH is used to carry HS-DSCH.

One HS-PDSCH corresponds to one

channelization code with a fixed spreading

factor of SF16.

The HS-PDSCH supports multi-code

transmission. This means that in one

HS-PDSCH sub-frame, multiple

channelization codes can be used for one UE.

It also depends on the UE’s capability.

The HS-PDSCH adopts the QPSK or 16QAM

modulation mode.

E-DPDCH

E-DCH

Dedicated

Physical

Data

Channel

RAN6.0 UL

Dedicated

The E-DPDCH is used to carry the E-DCH

transport channel. There may be zero, one, or

several E-DPDCHs on each radio link.

Its spreading factor set is {SF256, SF128,

SF64, SF32, SF16, SF8, SF4, 2×SF4, 2×SF2

and 2×SF2+2×SF4}. In RAN 6.0, spreading

factor set {SF256, SF128, SF64, SF32, SF16,

SF8, SF4, 2×SF4,} can be supported.

E-DPCCH

E-DCH

Dedicated

Physical

Control

Channel

RAN6.0 UL

Dedicated

The E-DPCCH is a physical channel used to

transmit control information associated with

the E-DCH. There is at most one E-DPCCH

on each radio link.

The spreading factor is always equal to 256.

E-AGCH

E–DCH

Absolute

Grant

Channel

RAN6.0 DL

Common

E-AGCH is a common downlink physical

channel, which carries the maximum power

ratio of E-DPDCH/DPCCH that can be used

by the UE. It is only sent from the serving

cell that the serving radio link of the UE

belongs to. An E-AGCH is shared by many

users in time dimension and the adjustment

procedure is usually at slow speed.

The spreading factor of E-AGCH is 256, and

the fixed rate of E-AGCH is 30 kbit/s.

E-RGCH

E-DCH

Relative

RAN6.0 DL

Dedicated

E-RGCH is a dedicated downlink physical

channel, which carries the relative grant value

for modifying power ratio of




Grant

Channel

E-DPDCH/DPCCH, it is used to frequently

adjust the UE uplink transmit power, which

could happen per 2ms TTI.

E-RGCH and E-HICH of a user share the

same channel code with spreading factor 128,

and one channel code for E-RGCH and

E-HICH can be spread again with 40

orthogonal signature sequences, which

extends the usage of the downlink channel

code.

E-HICH

E-DCH

Hybrid

ARQ

Indicator

Channel

RAN6.0 DL

Dedicated

E-HICH is a dedicated downlink physical

channel, which carries the E-DCH hybrid

ARQ acknowledgement indicator such as

ACK/NACK; the acknowledgement indicator

informs UE whether the data for a user

process is received correctly or not in the

Node B.

MICH RAN6.0 DL

Common

The MBMS Indicator Channel (MICH) is a

fixed rate (SF=256) physical channel used to

carry the MBMS notification indicators. The

MICH is always associated with an

S-CCPCH to which a FACH transport

channel is mapped.

F-DPCH RAN10.0/RA

N11.0

F-DPCH is a shared channel which only

carries the UE specific TPC bits so that the

A-DCH can be replaced by a shared channel

to save the code and power resource.

Replacing A-DPCH with F-DPCH will boost

the capacity for VoIP traffic in DL.

RAN11.0 supports Rel-7 F-DPCH, so UE can

receive the TPC bits in different F-DPCH

channels in soft handover status, to maximize

the user capacity in F-DPCH.

The following figure summarizes the mapping of transport channels onto physical channels.



Dedicated Physical Data Channel (DPDCH)

Dedicated Physical Control Channel (DPCCH)

Fractional Dedicated Physical Channel (F-DPCH)

E-DCH Dedicated Physical Data Channel (E-DPDCH)

E-DCH Dedicated Physical Control Channel (E-DPCCH)

E-DCH Absolute Grant Channel (E-AGCH)

E-DCH Relative Grant Channel (E-RGCH)

E-DCH Hybrid ARQ Indicator Channel (E-HICH)

Physical Random Access Channel (PRACH)

Common Pilot Channel (CPICH)

Primary Common Control Physical Channel (P-CCPCH)

Secondary Common Control Physical Channel (S-CCPCH)

Synchronisation Channel (SCH)

Acquisition Indicator Channel (AICH)

Paging Indicator Channel (PICH)

MBMS Notification Indicator Channel (MICH)

High Speed Physical Downlink Shared Channel (HS-PDSCH)

HS-DSCH-related Shared Control Channel (HS-SCCH)

Dedicated Physical Control Channel (uplink) for HS-DSCH (HS-DPCCH)

Transport Channels

DCH

RACH

BCH

FACH

PCH

Physical Channels

HS-DSCH

E-DCH

Enhancement

In RAN5.0, HSDPA is supported, and the following channels are added:

HS-DPCCH, Dedicated Physical Control Channel for HS-DSCH

HS-SCCH, Shared Control Channel for HS-DSCH

HS-PDSCH, High Speed Physical Downlink Shared Channel

In RAN6.0, HSUPA is supported, and the following channels are added:

E-DPDCH, E-DCH Dedicated Physical Data Channel

E-DPCCH, E-DCH Dedicated Physical Control Channel

E-AGCH, E–DCH Absolute Grant Channel

E-RGCH, E-DCH Relative Grant Channel

E-HICH, E-DCH Hybrid ARQ Indicator Channel

MICH, MBMS Indicator Channel

In RAN10.0, the F-DPCH is added.

Dependency




NDLP and NBBI do not support the HSUPA or HSDPA physical channel.

To support the F-DPCH, the macro Node B (BTS3812E or BTS3812AE) should be

configured with the EBBI or EBOI and the distributed Node B (BBU3806) should be

configured with the EBBC.


To support HSUPA physical channel, the optional feature WRFD-010612 HSUPA

Introduction Package should be configured.

To support HSDPA physical channel, the optional feature WRFD-010610 HSDPA

Introduction Package should be configured.

5.4 WRFD-021101 Dynamic Channel Configuration Control (DCCC)

Availability


Summary

This feature provides dynamic rate re-allocation and UE state transition that can be triggered

by multiple sources, thus ensuring QoS and improving resource utilization.

Benefits

This feature can improve the efficiency of radio resource allocation and maintain the stability

of radio link.

Description

Dynamic channel configuration control (DCCC) consists of rate re-allocation and UE state

transition function:

Rate Re-allocation

When UE is in the CELL_DCH RRC state, rate re-allocation can adjust the bandwidth

allocated for the best effort (BE) services (interactive and background services), in both

uplink and downlink respectively.

I. Traffic volume based

According to the traffic volume measurement report received from UE, rate re-allocation can

increase or decrease the uplink data rate to a proper value to match the allocated resource to

uplink.

According to the traffic volume measurement report received from the RNC itself, rate

re-allocation can increase or decrease the downlink data rate to a proper value to match the

allocated resource to downlink.

II. Coverage based



According to the downlink quality, including downlink transmit power and RLC status, rate

re-allocation can decrease the downlink data rate, to reduce the negative impact concerned

with coverage.

According to the uplink quality, including UE Tx power, the RNC can adjust the UL rate

during the call by means of UL bit rate switching to adapt to UE power limitations.

III. Load based

Rate re-allocation can be triggered by load control. The load can be power load and code

resource. The congestion thresholds are independent and configurable. This feature is a

strategy of WRFD-020106 Load Reshuffling.

UE State Transition

UE state transition is supported between the CELL_DCH, CELL_FACH, and

CELL_PCH/URA_PCH state according to both uplink and downlink traffic volume

measurement. It can also be used to improve the efficiency of resource allocation between

dedicated and common channels.

DCCC is also applied to HSDPA/HSUPA (rate re-allocation is not applied to HSDPA because

the data scheduler locates in the Node B). For details, please refer to optional features

WRFD-01061111 HSDPA State Transition and WRFD-01061208 HSUPA DCCC.

Enhancement

In RAN6.0, the code resource based DCCC is supported.

In RAN10.0, the UL bit rate downsizing due to the UE power limitation is supported.

In RAN10.0, the UL/DL bit rate downsizing based on DCH throughput is supported.

Dependency

None.

6 Network Security

6.1 WRFD-011401 Integrity Protection

Availability





Summary

This feature is concerned with integrity protection. The integrity protection mechanism can

ensure the security of the network and user data and protect them from being monitored and

modified illegally.

Benefits

This feature enhances network and user data security, and protects the data and networks from

being intercepted and modified illegally.

Description

The Integrity protection handles the control of integrity protection of signaling data and the

co-ordination of integrity keys between different core networks (PS and CS). It enables

receiving entity (the UE or the RNC) to verify if the signaling data is changed illegally. It

encrypts and decrypts the signaling data using a certain integrity algorithm with an integrity

key (IK).

Huawei RAN supports integrity algorithm UIA1.

Enhancement

None.

Dependency

None.

6.2 WRFD-011402 Encryption

Availability


Summary

This feature supports the encryption algorithms (UEA0 and UEA1) as defined in 3GPP

specifications.

Benefits

This feature enhances network and user data security, and protects the data and networks from

being intercepted and modified illegally.



Description

The Encryption function handles the control of ciphering of data and signaling data and the

coordination encryption keys between different core networks (PS and CS). It encrypts and

decrypts data and signaling using a certain encryption algorithm with a cipher key (CK).

Huawei RAN supports encryption algorithm UEA0 and UEA1.

Enhancement

None.

Dependency

None.



7 Power Control

7.1 WRFD-020501 Open Loop Power Control

Availability



Summary

This feature is concerned with open loop power control as defined in 3GPP specifications.

Open loop power control roughly estimates the path loss through power measurements,

network parameter settings, and QoS requirements and then provides a proper initial transmit

power for the UE and Node B.

Benefits

The proper initial power setting can decrease the possibility of burst interference to the

network and improve the performance of the inner power control.

Description

Open loop power control attempts to make a rough estimation of path loss by means of power

measurements, network parameter setting, and QoS requirement, and to provide a proper

initial power used by the UE and Node B.

Open loop power control is applied on the uplink PRACH and DPCH and the downlink

DPCH. The other downlink common channel’s initial power is set by the network.

In the case of the PRACH, the UE calculates the initial transmit power of PRACH preamble

by estimating the downlink path loss and using the uplink inference within the cell broadcast

information.

In the case of the uplink DPCCH transmission, the initial power is calculated in the same

manner as PRACH, except that the power offset is different and is provided by RRC message.

In addition, uplink DPDCH transmit power can be calculated with the gain factors signaled by

the network.

In the case of the downlink DPCH, the DPDCH transmit power is firstly estimated according

to the RAB QoS assigned and the network configured parameters, the transmit power of each

DPCCH part TFCI, TPC and pilot can be calculated by the network controlled power offset

(PO1/PO2/PO3) setting.



Open power control is used in the following scenarios which require an initial power on the

newly added radio link.

RRC connection setup

Radio link addition in soft handover

Hard handover

Relocation

Channel type switching

Enhancement

None.

Dependency

None.

7.2 WRFD-020502 Downlink Power Balance

Availability



Summary

This feature is related to downlink power balance as defined in 3GPP specifications.

Downlink power balance can solve the problem of downlink power drift caused by TPC bit

errors and link power imbalance in soft handover state to obtain the optimal gain of soft

handover.

Benefits

Downlink power balance can decrease the transmit power drifting of different RLs and

improve soft handover performance accordingly.

Description

During soft handover, the UL TPC command is demodulated in each RLS and due to

demodulation errors, the difference between the initial transmit power of newly added RL and

existing RL may lead to the drifting of transmit power. The more DL transmit power drifting,

the less the macro-diversity gain.

Downlink power balance is used to correct the transmit power drifting in such scenarios and

improve soft handover performance accordingly.

In the downlink, the Node B calculates the transmit power after considering TPC commands

sent by UE and the reference power set by the network. When the drifting of transmit power

is too much, the network updates the reference power to decrease the power difference of

different RLs.



Enhancement

None.

Dependency

None.

7.3 WRFD-020503 Outer Loop Power Control

Availability



Summary

This feature is related to outer loop power control as defined in 3GPP specifications. Outer

loop power control is used to maintain the communication quality to the level required by the

service bearer through adjustment of the SIR target of the inner loop power control.

Benefits

Outer loop power control is used to set the proper SIR target used for uplink inner loop power

control and improve the uplink performance.

Description

Outer loop power control is to maintain the communication quality at the level required by the

service bearer through adjustment of the SIR target. This operation is performed on each DCH

belonging to the same RRC connection.

Outer loop power control consists of downlink outer loop power control and uplink outer loop

power control. The purpose of downlink power control is to maintain the proper SIR target

used in the downlink inner loop power control, based on the implementation of UE algorithms.

The power of the UE must meet the requirement for the downlink BLER of the RB. The

purpose of the uplink power control is to maintain the proper SIR target used in the uplink

inner power control.

In the case of uplink outer loop power control, the SRNC first gets the uplink quality after

macro diversity selection combining, and then the SRNC compares the RX BLER with the

BLER target. If the RX BLER is higher than the BLER target, the SRNC increases the SIR

target; otherwise, it decreases the SIR target. If BLER is not available, BER is used. After

adjusting the SIR target, the SRNC sends the new SIR target through FP frames to all Node

Bs for uplink inner loop power control.

The initial SIR target provided by the RNC to the Node B is service-dependent and it is

updated by the uplink quality measurement of each DCH in the following phases.

Enhancement

None.



Dependency

None.

7.4 WRFD-020504 Inner Loop Power Control

Availability



Summary

Inner loop power control enables the Node B and UE to adjust their transmit powers in time.

Inner loop power control consists of uplink power control and downlink power control.

Benefits

Inner loop power control adjusts the uplink power and downlink power so that they are

minimum while the QoS is guaranteed, thus increasing the system capacity. It can also be

used to prevent shadow fading and fast fading.

Description

Inner loop power control is also called fast closed-loop power control and applied to only the

dedicated channel. It controls the transmit power according to the information returned from

the peer physical layer. The UE and the Node B can adjust the transmit power according to

the RX SIR of the peer end to compensate for the fading of radio links.

Inner loop power control consists of uplink inner loop power control and downlink inner loop

power control, and they work independently.

The uplink inner loop power control is used to adjust the UE transmit power by TPC

commands received from the Node B. The fast and slow power control algorithms (PCAs) are

defined in 3GPP specifications. PCA1 is the fast power control through which the UE adjusts

the transmit power for each timeslot. PCA2 is the slow power control through which the UE

adjusts the transmit power for five timeslots. PCA2 can lower the power control frequency

from 1500 times/s to 300 times/s maximally. The operator can decide which PCA is chosen in

the RRC messages. The downlink inner loop power control is used to adjust the Node B

transmit power by TPC commands received from the UE.

Downlink inner loop control involves the following two modes:

DPC0 mode: In DPC0 mode, the UE sends TPC commands for each timeslot.

DPC1 mode: In DPC1 mode, the UE sends TPC commands for three timeslots. The operator

can decide which DPC mode is used by RRC signaling.

Enhancement

None.



Dependency

None.



8 Cell Management

8.1 WRFD-020101 Admission Control

Availability


Summary

This feature can combine multiple resources to perform admission control over R99 service

requests, thus ensuring QoS and system resource allocation.

Benefits

This feature maximizes system capacity while ensuring QoS requirements and improves

network stability.

Description

Admission control is used to improve the resource usage efficiency and RRC/RAB setup

success rate. The following four types of resources are admitted:

Cell available code resource

Cell available power resource

Node B resource state, that is, Node B credits

Available Iub transport layer resource, that is, Iub transmission bandwidth

Only when all of these resources are available can a call be admitted and the admission

procedure applies to the uplink and downlink separately.

Note: This part of admission control is only applied to R99 services

I. Code Resource

When a new service accesses the network, the code resource admission is successful if the

code resource can be allocated to the service.

II. Power Resource

The following three algorithms are available for power resource:

Algorithm 1

Power resource admission decision based on power or interference



The RNC decides whether the cell load exceeds the threshold or not when admitting a

new call based on the current cell load (uplink load factor and downlink TCP) and the

access request. If the cell load exceeds the threshold, the RNC rejects the request. If the

cell load does not exceed the threshold, the RNC accepts the request.

Algorithm 2

Power resource admission decision based on the equivalent number of users.

The RNC decides whether the equivalent number of users exceeds the threshold or not

when admitting a new call based on the current equivalent number of users and the

access request. If the equivalent number of users exceeds the threshold, the RNC rejects

the request. If the equivalent number of users does not exceed the threshold, the RNC

accepts the request.

Algorithm 3

It is similar to algorithm 1, but the predicted required power of a new call is set to zero.

Four basic load thresholds are used to decide the admission. They are as follows:

− Handover admission threshold

− AMR conversational service admission threshold

− Non AMR conversational service admission threshold

− Other service admission threshold

With the preceding thresholds, the RNC can define the proportion between speech service and

other services with the handover preference guaranteed.

III. Node B credit

The Node B credit admission includes the following:

Local cell level admission decision

Local cell group level admission decision (if any)

Node B level admission decision

Services can access the network only after all admission decisions are taken

For details about local cell, local cell group, and capacity consumption law, see 3GPP TS

25.433.

According to the common and dedicated channels capacity consumption laws, and the

addition, removal, and reconfiguration of the common and dedicated channels, the controlling

RNC (CRNC) debits the amount of the credit resource consumed or credits the amount to the

capacity credit of the local cell (and local cell group, if any) based on the spreading factor.

If the UL capacity credit and DL capacity credit are separate, the maintenance on the local cell

(and local cell group, if any) is performed in UL and DL respectively.

If the UL capacity credit and DL capacity credit are not separate, only the maintenance on the

global capacity credit is performed for the local cell (and local cell group, if any).

IV. Iub transport layer resource

Different services have different QoS requirements. Therefore, differentiated transmission

must be applied according to the service QoS requirements. The mapping relation between

service and transport resources can be configured.

The principles of Iub bandwidth admission control are described as follows:

I. Each type of path can be configured with the total bandwidth of the physical port to which

the path is connected. Thus, the total bandwidth of all paths that connect to the port may



exceed the physical bandwidth of the port. Therefore, the following two levels of admission

are necessary:

Admission control on the path level

Admission control on the port level

II. Traffic congestion and bearer congestion are considered. For admission, the only factor

that needs to be considered is the Iub resources corresponding to the traffic class.

III. The primary path takes priority over the secondary path during admission. The secondary

path is tried when the admission attempt for the primary path fails.

The admission control also applies to HSDPA/HSUPA. Please refer to optional features

WRFD-01061003 HSDPA Admission Control and WRFD-01061202 HSUPA Admission

Control.

In the admission control procedure, some other features can be used to improve the access

success rate. That is, the feature Rate Negotiation at Admission Control (WRFD-010507) can

be used to decide the proper resource request based on the cell load. When the admission fails,

Queuing and Pre-Emption (WRFD-010505), DRD Introduction Package (WRFD-020400)

can be used to maximize the possibility of access to the system.

Enhancement

In RAN5.0, AMR and Non-AMR threshold for power load admission is divided.

In RAN6.0, algorithm 3 for power load admission is introduced.

In RAN6.0, resource reserved for handover is supported to decrease the call failure due to the

admission failure during the handover.

In RAN10.0, The PS service is admitted by judging the resource for GBR while in the

previous version the MBR is employed. By this means, the cell resources are better utilized.

Dependency

None.

8.2 WRFD-020102 Load Measurement

Availability


This feature is introduced in 3GPP R99.

Summary

This feature is related to load measurement for load control.

Benefits

Load measurement is the base of the related load control features including admission control,

load reshuffling, overload control, and potential user control features. On the other hand,



operators can also control these strategies by configuring load measurement parameters like

measurement period, hysteresis, and so on.

Description

Algorithms such as OLC and CAC use load measurement values in the uplink and the

downlink. A common load measurement (LDM) algorithm is required to control load

measurement in the uplink and downlink, which makes the algorithm relatively independent.

The LDM algorithm has the following functions:

Triggering LDR and OLC algorithms

The LDM algorithm needs to decide whether the system works in basic congestion or

overload congestion mode and to notify related algorithms for handling.

Delay susceptibilities of PUC, CAC, LDR, and OLC to common measurement are

different. When some or all the algorithms use the same common measurement, the

LDM must apply different smoothed filter coefficients to get rippling and timely

common measurement as required.

The major related measurement quantities are defined in 3GPP TS25.433 as follows:

Uplink RTWP (Received Total Wideband Power)

Downlink TCP (Transmit Carrier Power)

Transmitted carrier power of all codes not used for HS-PDSCH or HS-SCCH

transmission

Provided bit rate (PBR) on HS-DSCH

Power requirement for GBR (Guaranteed Bit Rate) on HS-DSCH.

The preceding measurements focus on radio power load. For other resource load, the related

measurements include the following:

For Iub load: Iub used bandwidth rate on PVC level.

For code resource: The maximum rate can be supported with the minimum available SF

Enhancement

In RAN6.0, the load measurement of code resource is introduced, and therefore load

reshuffling can also be triggered by code congestion.

Dependency

None.

8.3 WRFD-020106 Load Reshuffling

Availability




Summary

This feature provides multiple load reshuffling policies for the cell in basic congestion state to

decrease the cell load and increase the access success rate.

Benefits

This feature decreases the cell load when resource load enters the basic congestion state, and

therefore, improves the stability and capability of the network.

Description

When the usage of cell resource exceeds the congestion trigger threshold, the cell enters the

basic congestion state. In this case, LDR (Load Reshuffling) is required to reduce the cell load

and increase the access success rate. When the load is lower than the congestion release

trigger threshold, the system returns to normal.

The resources that can trigger basic congestion of the cell include:

Power resource

Iub resource or Iub bandwidth

Code resource

Node B credit resource

Equivalent user number

The Iub resource and credit resource congestion control in both uplink and downlink is Node

B oriented. Load trigger threshold and load release threshold are set for the uplink and

downlink separately.

The function of the LDR is to reduce the load of a cell when the available resource of the cell

reaches the threshold. The introduction of the LDR is to increase the access success rate in the

following ways:

Inter-frequency load handover

Code reshuffling

BE service rate reduction

Uncontrolled real-time traffic QoS renegotiation

CS domain inter-RAT load handover

PS domain inter-RAT load handover

Downsizing the bit rate of AMR voice

MBMS power downgrading

Among the preceding features, the best effort service rate reduction and code reshuffling are

the basic features, and the others belong to the optional features.

Enhancement

In RAN5.0, optional feature Iu re-negotiation is introduced as one of the load reshuffling

strategies.

In RAN5.0, priority based load reshuffling is supported.

In RAN5.1, optional feature AMRC is introduced as one of the load reshuffling strategies.



In RAN6.0, besides radio power resource and Iub resource, load reshuffling is extended to

other resource congestion including code resource, credit resource, and equivalent user

number.

In RAN6.0, load reshuffling can also be applied to HSDPA, HSUPA, and MBMS services. In

addition, gold user should not be affected during the load reshuffling.

In RAN6.0, code reshuffling and MBMS power downgrading are added as new strategies of

load reshuffling.

In RAN10.0, the feature is enhanced by the following:

Uplink load reshuffling triggered by power resource can be applied in an HSUPA cell.

Inter-frequency load balancing triggered by CE resource and Iub transmission resource

congestion are canceled in RAN10.0. The reason is that the target cell is probably under

the same Node B and in this condition the handover cannot alleviate the congestion.

When the cell is under LDR status, the PS services whose data rate is above GBR are

forbidden to increase the data rate while the services whose data rate is below GBR are

allowed to increase their data rate to GBR.

A switch is provided to control whether gold user is selected during the load reshuffling.

Dependency

None.

8.4 WRFD-020107 Overload Control

Availability


Summary

This feature provides multiple load adjustment means for the cell in overloaded state to fast

decrease the cell load.

Benefits

Overload control guarantees system stability:

The cell overload control quickly reduces cell load when the power resource is

overloaded in the cell.

Overload control of Iub transmission avoids the lack of Qos protection for current

services caused by Iub transmission overload after a sudden decrease of bandwidth.

Description

Overload control (OLC) is a way to rapidly reduce the cell load when a cell is overloaded. For

the overloaded cell, the cell load exceeds the overload threshold. In this case, overload control

can effectively decrease the cell load and maintain system stability. The OLC action stops

when the cell load is lower than the overload recovery threshold.

The resources used to trigger overload control include power and Iub transmission bandwidth.



1. Power

When the power resource of a cell is overloaded, OLC performs the following functions:

Restricts the transport format of BE service

Send some BE services from DCH to Cell FACH

Releases some UEs

2. Iub transmission bandwidth

When the RNC detects Iub transmission overload caused by the change of Iub transmission

bandwidth (for example, IMA link fault of the IMA group in ATM mode), overload control

releases some UEs to quickly reduce the Iub traffic flow.

Overload control chooses the UEs in the sequence of lower-to-higher priorities.

Enhancement

RAN5.0 supports priority-based overload control.

RAN11.0 supports control of Iub transmission overload caused by the change of Iub

transmission bandwidth.

Dependency

None.

8.5 WRFD-020108 Code Resource Management

Availability


Summary

This feature provides the allocation and reshuffling of downlink code tree resources. Code

resource management enables the proper allocation of code resources, thus improving

resource utilization.

Benefits

The code management algorithm can improve code usage efficiency, and optimize the code

allocation when too much code fragments are founded.

Description

Code resource management consists of code allocation and code re-allocation features and it

is only applied to the downlink code tree resource.

To optimize the code usage efficiency, the “left most” algorithm is adopted in code allocation

procedure, that is, the code with minimum SF is reserved to ensure that the codes are

available for use continuously.



When the assigned AMR speech bit rate is less than 7.95 Kbit/s, the allocated SF is 256

instead of 128 to save the code resource, and therefore, the capacity is increased.

Code reshuffling algorithm is also used as one of the load reshuffling strategies and is used to

decrease the code fragments. That is, when detecting that the maximum coding rate is lower

than the threshold, the RNC reallocates the codes in the code tree to reduce code fragments as

many as possible.

Enhancement

In RAN6.0, allocation of code with SF 256 when the assigned AMR speech bit rate is less

than 7.95 Kbit/s is supported.

In RAN6.0, code re-allocation algorithm is introduced as one of the load reshuffling strategies

triggered by code congestion.

Dependency

None.


9 Network Sharing

9.1 WRFD-021301 Shared Network Support in Connected Mode

Availability



Summary

This feature enables the RNC to obtain shared network parameters and work with the CN to

apply the access control over the UE in connected mode to the specified location area. This

feature can support operation applications for network sharing solutions.

Benefits

With this feature, the RNC can prevent UE in connected mode from moving to an

un-subscribed area. It is also a supplement feature for implementing shared networks

solutions.

Description

Based on R99 specifications, when the UE is in idle mode, the CN+UTRAN have

mechanisms available to provide UE-specific access restrictions for LAs of the current PLMN

and other PLMNs by using roaming agreement. But there is no mechanism to restrict UE

behavior in connected mode, since UTRAN does not have enough information to handle the

UE as CN does to UE in idle mode. Accordingly, this feature is introduced in 3GPP R5 and

used to provide an access restriction mechanism for UE in connected mode.

To support this function, the RNC obtains the parameters of the shared network support in

connected mode from the messages and information elements (IE), which are defined in

3GPP TS 25.413 and 25.423 including:

The information of the PLMN/SNA that allows the UE to connect to, which is acquired

from CN through RELOCATION REQUEST or COMMON ID message.

The information of the SNAs that the LAs belong to, which is from CN through

INFORMATION TRANSFER message or from DRNC through RADIO LINK SETUP

RESPONSE and UPLINK SIGNALING TRANSFER messages.



Each LA belongs to one or several shared network area (SNA), and one UE can belong to one

or several SNAs. Based on the information, the RNC decides whether the UE is allowed to

get services in the new network or not according to the information.

The following procedures have connection with this feature:

Cell update

When the UE initiates cell update in the destination cell, the RNC decides whether the

UE is allowed to access the destination cell.

If the UE is not allowed to access the destination cell, the cell update fails.

URA update

The URA update is the same as the cell update.

Handover

During the soft handover or the hard handover, the RNC does not send measurement

control indication if the UE is not allowed to access a cell. Therefore, the UE does not

trigger a measurement report of that cell. As a result, the UE cannot be handed over to

that cell.

Relocation

When the target RNC (TRNC) receives a RELOCATION REQUEST message, it decides

whether the UE is allowed to access the destination cell.

If the UE is not allowed to access the destination cell, the relocation failure procedure is

triggered.

Handling common ID message

The RNC obtains the IMSI information of the UE in the common ID message and

decides whether the UE is allowed to access the current cell. If the UE is not allowed to

access the current cell, the RRC connection is released.

Enhancement

None.

Dependency


CN must support this feature. When the Iur interface is used, the RNC connected over the

interface must also support this feature.

9.2 MRFD-210104 BSC/RNC Resource Sharing

Availability

This feature is available from GBSS9.0 and RAN10.0.

Summary

This feature provides the resource sharing of the user plane and control plane in the MBSC by

adopting the intra-subrack/inter-subrack load sharing mechanism of boards.



Benefits

This feature improves the resource utilization and increases the call success rate. It also

maximizes the capacity usage in different traffic modes.

Description

The BSC/RNC Resource Sharing feature is classified into user plane resource sharing and

control plane resource sharing.

Control plane resource sharing applies to CPU usage and memory. When the CPU usage of a

certain signaling processing unit is too high or when the memory of a certain signaling

process unit is insufficient, the new call is transferred to other signaling processing unit with a

low load.

User plane resources are shared dynamically within the system based on resource pool and

load sharing. If a certain user plane processing unit is overloaded, the new traffic can be

allocated to other user plane processing unit with lower load.

For the MBSC, the service type-based resource pools are as follows: GSM control plane

resource, GSM user plane resource, UMTS control plane resource, and UMTS user plane

resource. The resource sharing within the pool is supported, but the resource sharing between

pools is not supported.

Enhancement

None.

Dependency


None.


None.


None.


None.



10 Mobility Management

10.1 WRFD-020201 Intra Node B Softer Handover

Availability



Summary

This feature is concerned with intra-Node B softer handover. The intra-Node B softer

handover can provide a higher combination gain (maximum combination) and reduce the

occupation of transmission resources on the Iub interface.

Benefits

Soft handover provides seamless connection services for mobile users. Besides these, the intra

Node B softer handover uses maximum-ratio combination on the uplink in the Node B to

increase the gain of combination. It also saves Iub bandwidth resources.

Description

Soft handover is a procedure in which at least one radio link is maintained between the UE

and UTRAN when the setup or release of radio links are being performed. Soft handover

occurs only within the intra-frequency cells. Since adjacent cells have the same frequency, UE

can connect to the network through multiple radio links to improve the communication quality.

UE can perform smooth handover from one cell to another without interrupting the

communication with the original cell.

On the other hand, soft handover may lead to the occupancy of Iub resource since multiple

radio links exist.

The size of active set can be up to six and can be configured. The RNC can decide SHO

according to either Ec/N0 or RSCP. The parameters set for SHO can be independent of CS

and PS services. The parameter CIO can also be configured for different cells for event

evaluation.

The intra Node B softer handover is a kind of soft handover. It sets up RLs in the sectors

within a Node B and the data received on these RLs is combined in the Node B using

maximum-ratio combination before being forwarded to the RNC. Therefore, softer handover

will occupy no more Iub transmission resource compared with soft handover.



The RNC can control whether the intra Node B softer handover should be implemented by

setting the RL ADDITION REQUEST in the NBAP message.

Neighboring cell combination is supported, which means the neighboring cells to be

measured are selected from all the neighboring cells of active set and the priority of the

neighboring cell is configurable. Neighboring cell combination is applied to soft/softer

handover, hard handover, and inter-RAT handover.

Enhancement

In RAN5.1, the neighboring cell combination is supported.

Dependency

None.

10.2 WRFD-020202 Intra RNC Soft Handover

Availability



Summary

This feature is concerned with intra-RNC soft handover. Compared with the intra-Node B

softer handover, the intra-RNC soft handover has a wider application scope. The intra-RNC

soft handover enables macro diversity combination and each RL has its own transport bearer

on the Iub interface.

Benefits

The intra-RNC soft handover provides seamless connection services for mobile users within

the RNC.

Description

The intra RNC soft handover is a kind of soft handover. It sets up RLs in different Node Bs or

in the same Node B within the RNC. The difference between the intra-Node B softer

handover and the intra-RNC soft handover lies on where the combination is performed. The

intra-RNC soft handover performs macro diversity combination in the RNC, which means

each RL has its own transport bearer on Iub interface.

Enhancement

In RAN5.1, neighboring cell combination is supported.

Dependency

None.



10.3 WRFD-020203 Inter RNC Soft Handover

Availability



Summary

This feature is concerned with inter-RNC soft handover. The inter-RNC soft handover enables

the establishment of an RL on the DRNC and the macro diversity combination on the SRNC

through the Iur interface.

Benefits

The inter RNC soft handover provides seamless connection services for mobile users.

Compared with other kinds of soft handovers, the inter RNC soft handover increases the

range of soft handover to the RNCs which have Iur connections with a certain RNC.

Description

The inter RNC soft handover is a kind of soft handover. It sets up RLs in different RNCs and

the macro diversity combination is completed through Iur interface by the SRNC. The uplink

data is transmitted from the DRNC to the SRNC. The SRNC combines data from its own cells

and cells of the DRNC. This is the key difference from other soft handovers.

Enhancement

RAN5.1 supports the neighboring cell combination.

Dependency


The Iur interface is configured between adjacent RNCs.

10.4 WRFD-020301 Intra Frequency Hard Handover

Availability



Summary

This feature is concerned with intra-frequency hard handover. When the soft handover fails,

the RNC enables the UE to move between cells through hard handover.



Benefits

Intra frequency hard handover applies in the scenarios where intra frequency soft handover

can not be used.

Description

Hard handover is characterized by the handover procedure in which the old connection is

released before a new connection is set up. Intra frequency hard handover means hard

handover between cells of the same frequency. It is used in any of the following scenarios:

No Iur interface between RNCs

In this case, the soft handover between RNCs is unavailable, and the hard handover with

CN switching between the two RNCs occurs.

Not enough Iur interface transmission resource available

In this case, the soft handover between RNCs is also unavailable, and the hard handover

with CN switching between the two RNCs occurs.

High-speed BE service

For the high-speed BE service, intra-frequency hard handover can be used to save

downlink capacity, compared with soft handover.

Intra-frequency soft handover fails and intra-frequency hard handover is allowed

When intra-frequency soft handover fails due to the target cell congestion,

intra-frequency hard handover can be tried with lower service bits rate.

Enhancement

In RAN5.1, neighboring cell combination is supported.

Dependency

None.

10.5 WRFD-010801 Intra RNC Cell Update

Availability



Summary

This feature is related to intra-RNC cell update as stipulated in 3GPP specifications. The

intra-RNC cell update procedure can be triggered by events.

Benefits

Cell update enables UTRAN to manage a UE’s behavior and enables UE to update its state

when its service or location changes.



Description

Cell update is mainly used to update the UE information on the network side when the UE’s

location or behavior is changed. The intra RNC cell update means cell update within the

RNC.

Cell update may be triggered by the following causes:

Periodical cell update

UE sends Cell Update message to RNC periodically when it is in CELL_FACH or

CELL_PCH state. This can be used by RNC to monitor the RRC connection.

Cell reselection

If a UE in CELL_FACH or CELL_PCH state reselects a new cell, the UE starts the

procedure. When receiving the message CELL_UPDATE, RNC updates the UE camping

cell information.

Paging response

If a UE in URA_PCH or CELL_PCH state receives a PAGING TYPE 1 message, the UE

starts the procedure. RNC then transmits the UE’s state to CELL_FACH or CELL_DCH.

Uplink data transmission.

If a UE is in URA_PCH or CELL_PCH state and has data to transmit, the UE starts the

CELL UPDATE procedure to request for uplink data transmission. The RNC will

transmit its state to CELL_FACH subsequently.

Radio link failure

If a UE in CELL_DCH state detects that the criteria for radio link failure are met, the UE

starts the procedure. The RNC deletes the current radio link and re-establishes a new

one.

Re-entering service area

If a UE moves out of the service area, and then re-enters the service area, the UE starts

the procedure. Then RNC updates the camping cell of the UE.

RLC unrecoverable error

If a UE detects an RLC unrecoverable error in an AM RLC entity, the UE starts the

procedure. The RNC releases the RRC connection of the UE or re-establishes the RB

according to the attributes of the RB. If it belongs to signal RB, the RRC connection is

released.

Enhancement

None.

Dependency

None.

10.6 WRFD-010802 Inter RNC Cell Update

Availability





Summary

This feature is related to inter-RNC cell update as stipulated in 3GPP specifications. The

inter-RNC cell update procedure can be triggered by events.

Benefits

Cell update enables UTRAN to manage a UE’s behavior and enables UE to update its state

when its service or location changes. The inter RNC cell update feature increases the range of

cell update through Iur interface.

Description

Cell update is mainly used to update the UE information on the network side when the UE’s

location or behavior is changed. The inter RNC cell update means cell update between RNCs.

The cause of the inter RNC cell update is the same as the intra RNC cell update. The

difference between them is that in the inter RNC cell update, the CELL UPDATE message is

first received by the DRNC and forwarded to the SRNC, the SRNC then takes necessary

actions according to the cause within CELL UPDATE, for example, relocation.

Enhancement

None.

Dependency



10.7 WRFD-010901 Intra RNC URA Update

Availability



Summary

This feature is concerned with intra-RNC URA update as stipulated in 3GPP specifications.

The intra-RNC URA update procedure can be triggered by events.

Benefits

URA update enables UTRAN to monitor the RRC connection and manage the behaviors of

the UE in URA_PCH state.



Description

User registration area (URA) update procedure updates the UTRAN registration area of a UE

when an RRC connection exists and the position of the UE is known on URA level in the

UTRAN. The intra RNC URA update means URA update within the RNC.

URA update may be triggered by the following two causes:

Periodical URA update

The UE sends the URA update message to the RNC periodically when it is in URA_PCH

state. This can be used to monitor the RRC connection.

URA reselection

If the UE in URA_PCH state enters a new URA, the UE starts the procedure, and the

RNC updates the camping URA of the UE accordingly.

Enhancement

None.

Dependency

None.

10.8 WRFD-010902 Inter RNC URA Update

Availability



Summary

This feature is related to inter-RNC URA update as stipulated in 3GPP specifications. The

inter-RNC URA update procedure can be triggered by events.

Benefits

The URA update enables UTRAN to monitor the RRC connection and manage the behaviors

of the UE in URA_PCH state. The inter RNC URA update increases the range of URA

Update through Iur interface.

Description

URA update procedure updates the UTRAN registration area of a UE when a RRC connection

exists and the position of the UE is known on URA level in the UTRAN. The inter RNC URA

update means the URA update between RNCs. Similar to the intra RNC URA update, a UE in

URA_PCH state also initiates the URA update procedure in two cases, URA reselection and

periodic URA update. The difference between the intra RNC and the inter RNC URA updates

is that in the inter RNC URA update, the URA UPDATE message is first received by the

DRNC and forwarded to the SRNC, the SRNC then takes necessary actions according to the

cause of the URA update, for example, relocation.



Enhancement

None.

Dependency



10.9 WRFD-021400 Direct Signaling Connection Re-establishment (DSCR)

Availability



Summary

This feature is related to the direct signaling connection re-establishment procedure of the UE

at the intersection of RNCs. When the UE moves between RNCs, this feature can prevent PS

services from being disrupted even if the relocation fails.

Benefits

This feature is a supplement to relocation. When the resources on the Iur interface are

insufficient or the relocation fails, this feature can prevent PS services from being disrupted.

Description

When the UE moves to the cell controlled by the DRNC, the SRNS relocation procedure (the

UE involved or not involved) can be implemented to keep services continuous. But when

there is no Iur interface or the relocation is not supported or relocation fails, UE connection

fails. In such scenarios, direct signaling connection re-establishment (DSCR) feature can be

used to prevent the connection from being interrupted. That is, the DRNC sends an RRC

connection release message with the cause of direct signaling connection re-establishment

when it is unable to contact the SRNC to validate the UE.

The UE should perform a route area update (RAU) procedure immediately on entering

PMM-IDLE state when it has received a RRC connection release message with the cause of

directed signaling connection re-establishment even if the RA has not changed since the last

update.

DSCR is used to re-establish services by RAU procedure. Hence, this feature can only be

applied to PS services, and it is of no help in re-establishing CS services.

Enhancement

None.



Dependency

None.



11 NodeB Network Structure

11.1 MRFD-210204 Star Topology

Availability


Summary

This feature is related to the star topology. The star topology is characterized by simple

networking and easy maintenance.

Benefits

In this mode, each Node B directly connects to the RNC. Therefore, the star topology features

simplicity, convenience in maintenance and engineering, and easy capacity expansion.

In this mode, signals travel through fewer nodes. Therefore, the transmission is more reliable.

Description

Node Bs can be connected in star topology.

It is applicable in most cases. Each Node B is directly connected to the RNC by E1/T1. The

networking structure is simple. It is convenient to implement maintenance and engineering.

Signals are transferred directly between the Node Bs and the RNC, so the link is quite reliable.

This networking topology can be applied in densely populated areas. It is easy to expand the

capacity, but a large amount of transport lines are required.

NodeB

RNC

NodeB

NodeB



Enhancement

None.

Dependency

None.

11.2 MRFD-210205 Chain Topology

Availability


Summary

This feature is related to the chain topology. The chain topology is characterized by

cost-effective networking.

Benefits

Chain networking can reduce costs of transmission equipment, engineering, construction and

transmission link lease.

Description

Node Bs can be connected in chain topology.

The line reliability is poor because signals are transferred across many intermediate systems.

This networking topology is applicable to the strip-shape areas having sparse population, such

as expressway and railway. In these areas, the chain topology can meet the requirements with

much less transmission equipment. The cascading connection is limited to five levels.

NodeBRNC NodeBNodeB

Enhancement

None.

Dependency

None.



11.3 MRFD-210206 Tree Topology

Availability


Summary

This feature related to the tree topology. The tree topology is a combination of star topology

and chain topology and provides more flexible networking.

Benefits

It is suitable for microwave transmission network. The hub Node B is based on the tree

topology. The tree networking requires fewer transmission links than star networking.

Description

Node Bs can be connected in tree topology.

In most scenarios, the MW (Micro Wave) network is a typical tree topology. It is suitable for

the MW network. In order to increase the efficiency, the hub Node B based on the tree

topology is available from RAN5.1.

The consumption of transport lines is less than that of the star networking. But at the same

time, the connection is not so reliable because signals are transferred across many

Intermediate systems. It is difficult to implement maintenance and engineering. A fault occurs

in the upper-level Node B may affect the operation of the lower-level Node Bs. This

networking topology is applicable to a large area having sparse population. Capacity

expansion may result in reconstruction of the network.

Note:

The clock of the Node B is obtained by phase lock of the upper-level network. A phase lock

can degrade the quality of the clock. Therefore, the cascading level must be not more than

five.

NodeB

RNC

NodeB

NodeB

NodeB

Enhancement

None.



Dependency

None.


12 Clock

12.1 MRFD-210501 BTS/NodeB Clock

Availability


Summary

The synchronization of the MBTS clock provides the basis for the frame synchronization. The

MBTS uses this feature to obtain the reference clock sources for the internal frame

synchronization. The MBTS supports three clock synchronization modes: synchronization

with the Iub/Abis clock, synchronization with the BITS clock, and synchronization with GPS

clock. In addition, the MBTS internal clock can work in free-run mode to temporarily provide

reference source.

Benefits

With this feature, the internal clock can be synchronized with the transmission network

without using the auxiliary equipment, thus saving the cost. In addition, the precision of the

synchronized clock meets the requirements of the radio transmission network and frequencies.

Description

In compliance with the 3GPP specifications, the frequency stability of the master clock of the

MBTS must be between –0.05 ppm and +0.05 ppm. The MBTS can work in multiple clock

synchronization modes to suit different clock topologies:

Synchronization with the Iub/Abis clock (default mode)

The clock source of the MBTS is synchronized with the line clock sources of its

upper-level NE such as the MBSC.

Synchronization with GPS

The GPS card is optional unless the MBTS uses a GPS clock as its clock source.

The clock signals are processed and synchronized as follows:

The GPS antenna and feeder system receives GPS signals at 1575.42 MHz, and then

transmits the signals to the GPS card. The system can trace up to eight (normally three or

four) satellites simultaneously. The GPS card processes the signals and transmits them to

the main clock module.

Synchronization with the BITS clock



The MBTS can synchronize its clocks with the 2 MHz clock signals from an external

reference clock. The reference clock can be a BITS clock or a 2 MHz clock from the

transmission equipment.

Through phase locking and frequency dividing, the main clock module converts the

clock signals into various clock signals required by the MBTS, for example, F_CLK,

CLK_4X, and BFN.

In addition to the preceding three synchronization modes, the MBTS internal clock can work

in free-run mode to keep the MBTS running.

The enhanced stratum 3 OCXO with a high precision works as the master clock of the MBTS.

The OCXO can guarantee the normal operation of the MBTS for up to 90 days.

Enhancement

None.

Dependency


None.


1) BTS

The BTS3006C and BTS3002E do not support the GPS clock input.

2) NodeB

None.

3) MBTS

None.


None.


None

12.2 MRFD-210502 BSC/RNC Clock

Availability


Summary

With this feature, five types of clock sources are supported. Each clock source supports

functions such as 1+1 backup, management of the clock source, query of the clock status, and

maintenance of the link clock.



Benefits

This feature provides various clock input schemes for operators.

The clock source backup function prevents the primary clock faults from affecting services.

Description

MBSC clock provides reliable clock sources for the MBSC to meet the requirements of the

clock precision defined in the 3GPP specifications. Every type of clock source supports 1+1

backup.

The MBSC clock subsystem consists of the clock processing board GCUa/GCGa and the

clock processing unit in each subrack. The external reference clock signals are transmitted to

the GCUa/GCGa. After a phase lock on the GCUa/GCGa, the clock signals are changed to 8

KHz clock signals. The signals are then transmitted to the SCUa in the same subrack through

the backplane and to the SCUa in the EPS through clock signal cables. Then, the 8 KHz clock

signals on the SCUa are transmitted to other boards in the same subrack through the

backplane.

When the clock source is faulty, the MBSC reports the related alarms and starts the 1+1

backup scheme to ensure the normal operation of the system.

The MBSC clock sources are as follows:

Building integrated timing supply system (BITS)

Line clock extracted from the A/Iu interface

Global positioning system (GPS) satellite synchronization clock

8 KHz clock provided by an external device

Local oscillator clock

The MBSC provides the clock control setting functions, including management of the clock

source, query of the clock status, and maintenance of the line clock. The MBSC requires only

one clock source, and the clock source can work in automatic, manual, or self-oscillation

mode.

Automatic

In automatic mode, you need not specify a clock source for the current clock. The system

automatically selects a clock source with the highest priority.

Manual

In manual mode, you need to manually specify a clock source for the current clock. The

system does not automatically switch to another clock source even if this clock source is

faulty.

Self-oscillation

The self-oscillation mode is the default clock working mode of the system.

Enhancement

None.



Dependency


The GCGa should be configured if the GPS satellite synchronization clock is used.


None.


None.


None.



13 ATM Transmission Introduction Package

13.1 WRFD-050301 ATM Transmission Introduction Package

Availability



Summary

This feature is related to ATM transmission introduction for the operator. ATM transmission is

one of the major WCDMA networking solutions. Huawei RAN provides ATM transmission

interfaces and related functions.

Benefits

This feature package provides support for ATM transmission.

Description

Huawei RAN supports ATM transport optional feature defined in 3GPP specifications. ATM

transmission feature includes the following sub-features:

ATM over E1/T1 on Iub interface

ATM over channelized STM-1/OC-3 on Iub interface

ATM over non-channelized STM-1/OC-3c on Iub/Iu/Iur interface

IMA for E1T1 or channelized STM-1/OC-3 on Iub interface

Dynamic AAL2 connections on Iub/IuCS/Iur interface

Permanent AAL5 connections for control plane traffic

Call admission based on AAL2 path BW

CBR, rt-VBR, nrt-VBR, UBR ATM QoS classes



Enhancement

For the enhancement, refer to the enhancement of sub-features in ATM Transmission

Introduction Package.

Dependency

None.

13.1.1 WRFD-05030101 ATM over E1T1 on Iub Interface

Availability


Summary

This feature is related to ATM over E1/T1 on the Iub interface. The boards capable of this

feature include the ATM transmission interface board on the RNC side and the NUTI, HBBU,

WMPT, and UTRP on the Node B side.

Benefits

This feature enables the use of microwave network or PDH legacy network for Iub

transmission.

Description

Huawei RAN supports ATM over E1/T1 electrical interface.

The RNC ATM over E1/T1 interface board supports:

32 ports (E1/T1) per board

UNI, IMA, Fractional ATM, and Fractional IMA

32 IMA group per board

One IMA group supports up to 32 E1/T1 ports

The Node B (BTS3812E/AE, DBS3800) ATM over E1/T1 interface board (NUTI, HBBU)

supports:


UNI, IMA, Fractional ATM

4 IMA groups per board


The Node B (3900 Series Node B) ATM over E1/T1 interface board (WMPT) supports:



2 IMA groups per board


The Node B (3900 Series Node B) ATM over E1/T1 interface board (UTRP) supports:





4 IMA group per board


Enhancement

In RAN2.0, the NDTI board is introduced.

In RAN5.0, the HBBU board is introduced.

In RAN5.1, the NUTI board is introduced.

In RAN10.0, the WMPT and UTRP (E1 interface) boards are introduced in 3900 series Node

B.

Dependency

None.

13.1.2 WRFD-05030102 ATM over Channelized STM-1/OC-3 on Iub Interface

Availability


Summary

This feature is related to ATM over channelized STM-1/OC-3 on the Iub interface. The boards

capable of this feature include the ATM transmission interface board based on channelized

STM-1 on the RNC side and the NUTI and HBBU on the Node B side.

Benefits

This feature enables the use of SDH network for Iub transmission.

Description

Huawei RAN supports ATM over channelized STM-1 optical interface on Iub interface.

BSC6800 ATM over channelized STM-1 interface board supports:

1 x 155 Mbps port per board.

63 x VC12 2 Mbps flows per port.

63 UNI link, or 42 IMA group per port.

At most 32 VC12 flows per IMA group.

MSP 1:1 redundancy.

BSC6900 ATM over channelized STM-1/OC-3 interface board supports:

2 x 155 Mbps port per board

63 x VC12 2 Mbps or 84 x VC11 1.5 Mbps flows per port, configurable at initiation



63 x 2 Mbps UNI links, or 84 x 1.5 Mbps UNI links, or 42 IMA group per port

At most 32 VC12/VC11 flows per IMA group

MSP 1:1 redundancy

The Node B (BTS3812E/AE, DBS3800) channelized STM-1 interface board (NUTI, HBBU)

supports:


63 x VC12 2 Mbps flows per port.

Enhancement

In RAN6.0, the Node B (BTS3812E/AE and DBS3800) supports the transmission interface

board based on channelized STM-1/OC-3.

Dependency


Only BTS3812E/AE and DBS3800 can provide the ports based on channelized STM-1/OC-3.

13.1.3 WRFD-05030103 ATM over Non-channelized STM-1/OC-3c on Iub/Iu/Iur Interface

Availability


Summary

This feature is related to ATM over non-channelized STM-1/OC-3 on the Iub interface. The

boards capable of this feature include the ATM transmission interface board based on

non-channelized STM-1 on the RNC side and the NUTI, HBBU, and UTRP on the Node B

side.

Benefits

This feature enables the use of SDH network or ATM network for Iub/Iu/Iur transmission.

Description

Huawei RAN supports ATM over non-channelized STM-1/OC-3c optical interface on

Iub/Iu/Iur ATM transmission.

BSC6800 ATM over non-channelized STM-1/OC-3c interface board supports:


ATM full rate, VC4 150 Mbps per port.

MSP 1+1 redundancy.

BSC6900 ATM over non-channelized STM-1/OC-3 interface board supports:




MSP 1+1 and MSP 1:1 redundancy.

Up to 2000 VCs per board shared by each port.

Full VPI/VCI address space (VPI: 0 – 255, VCI: 32 - 65535).

The Node B (BTS3812E/AE, DBS3800) non-channelized STM-1/OC-3 interface board

(NUTI, HBBU) supports:



The Node B (3900 series NodeB) on-channelized STM-1/OC-3 interface board (UTRP)

supports:



Enhancement

In RAN5.1, the Node B (BTS3812E/AE and DBS3800) supports the transmission interface

board based on non-channelized STM-1/OC-3.

In RAN10.0, the 3900 series Node B supports the UTRP transmission board based on

non-channelized STM-1.

Dependency

None.

13.2 WRFD-05030104 Dynamic AAL2 Connections in Iub/IuCS/Iur Interface

Availability


Summary

This feature supports the establishment of dynamic AAL2 connections on the Iub, Iur, and

Iu-CS interfaces.

Benefits

Huawei AAL2 bearer solution provides the following functions:

Provides corresponding AAL2 path types according to service types such as the voice

service, streaming service, interactive service, and background service.

Provides corresponding AAL2 path types according to the R99, HSDPA, and HSUPA

services.

Makes efficient use of Iub transmission links when delay-sensitive services and

delay-insensitive services are available at the same time.



Allocates physical bandwidth dynamically to delay-sensitive services and

delay-insensitive services.

Description

The user plane data flows on the Iub, Iur, and Iu-CS interfaces are carried on the specified

AAL2 connections.

The control plane on the transport network establishes dynamic AAL2 connections for the Iub,

Iur, and Iu-CS interfaces through ITU Q.2630.1/Q.2630.2 signaling.

RAN2.0 supports the configuration of AAL2 CAC. Services of different types can be

distributed to different AAL2 paths. The AAL2 connections for real-time services can be

established on the CBR/RT-VBR VCC, and those for non-real-time services can be

established on the NRT-VBR VCC.

RAN3.0 introduces Q.2630.2 and thus supports AAL2 adjustment and QoS optimization

based on the Iub and Iur interfaces. RAN3.0 introduces the AAL2 path especially for HSDPA

services. The AAL2 connections for HSDPA services can be established on the UBR VCC.

RAN6.0 introduces the AAL2 path especially for HSDPA/HSUPA services. RAN6.0

introduces the secondary AAL2 path for each type of service and provides flexible

mechanisms for hybrid transmission on the Iub interface.

Enhancement

RAN3.0 introduces Q.2630.2 and thus supports AAL2 adjustment and QoS optimization

based on the Iub and Iur interfaces.

RAN3.0 introduces the AAL2 path especially for HSDPA services.

RAN6.0 introduces the AAL2 path especially for HSDPA/HSUPA services.

RAN6.0 introduces the secondary AAL2 path for each type of service and provides flexible

mechanisms for hybrid transmission on the Iub interface.

Dependency


None.


None.


None.


None.



13.3 WRFD-05030105 Permanent AAL5 Connections for Control Plane Traffic

Availability


Summary

This feature supports the establishment of permanent AAL5 connections for control plane

services on the Iub/Iur/Iu interface.

Benefits

The permanent AAL5 connections for control plane services comply with 3GPP Iub/Iur/Iu

interface specifications.

Description

In the ATM RAN, AAL5 connections are used to carry the signaling on the Iub/Iur/Iu

interface and the OAM traffic on the Iub interface. As defined in the 3GPP specifications,

UNI-SAAL is used for control plane connections on the Iub interface, and NNI-SAAL is used

for control plane connections on the Iur and Iu interfaces. The AAL5 connections on the

Iub/Iur/Iu interface of Huawei RAN are established through configuration.

Enhancement

None.

Dependency


None.


None.


None.


None.



13.3.2 WRFD-05030106 Call Admission Based on Used AAL2 Path Bandwidth

Availability


Summary

This feature is related to the call admission control (CAC) based on AAL2 path bandwidth.

The AAL2 CAC is used to selectively accept or reject some access requests to maximize the

utilization of transmission resources without compromising QoS.

Benefits

This feature helps to:

Avoid transmission congestion

Improve the transmission resource usage

Increase the accessibility

Description

The purpose of AAL2 CAC (Call Admission Control) is to maintain the quality of service and

at the same time maximize the utilization of transmission resources. This is achieved by

selectively admitting or rejecting request for resources.

AAL2 CAC request occurs when the AAL2 connection is established or modified on Iub, Iur,

and Iu-CS interfaces.

In the case of CS services, PCR * service factor is used for admission decision.

In the case of PS services, GBR * service factor is used for admission decision. No GBR is

assigned for best effort services. Hence, such parameters can be configured by operators.

In the case of HSDPA/HSUPA service, GBR * service factor is used for admission decision.

No GBR is assigned for best effort services. Hence, such parameters can be configured by

operators.

All the preceding service factors can be configured according to the service classes.

For the UE handover, all the transmission resources can be used for admission to minimize

the possibility of the failure of an existing call.

For the newly accessed UE, (100% - handover admission threshold) transmission resources

are used.

For the bit rate upgrade UE, the transmission resources below congestion threshold are used.

Enhancement

None.



Dependency

None.

13.3.3 WRFD-05030107 CBR, rt-VBR, nrt-VBR, UBR ATM QoS Classes

Availability


Summary

This feature is concerned with four ATM service classes: CBR, rt-VBR, nrt-VBR, and UBR.

The four ATM service classes are used to differentiate services at the ATM layer.

Benefits

The feature supports:

Full inter-operation between RAN and ATM equipment

VC traffic shaping

ATM traffic differentiation

Description

Huawei RAN supports four ATM service classes (CBR, rt-VBR, nrt-VBR, and UBR)

specified in TM4.1 (ATM forum specification Traffic Management 4.1). The VCC supports

shaping for existing traffic according to the parameters (SCR, PCR, and CDVT) of each ATM

service class.

The four ATM service classes are used to differentiate services at the ATM layer. Two ATM

service classes are configured for R99 traffic and two are configured for HSxPA. In general,

DS (Delay Sensitive) traffic uses rt-VBR, NDS (None Delay Sensitive) traffic uses nrt-VBR,

and NDS traffic mapping on HSxPA uses UBR or nrt-VBR.

Enhancement

None.

Dependency

None.

13.3.4 WRFD-05030110 F5

Availability




Summary

This feature is related to end-to-end ATM OAM F5 flows defined in ITU I.610.

Benefits


ATM VCC End-to-End continuity check.

Supervision of the AAL2 path, and blocking of the fault AAL2 path.

Supervision of the Iu-PS GTPU path, and blocking of the fault GTPU path

Transmits delay information in the LB IE and detects delay on the AAL2 link offers

convenience on transport network maintenance.

Description

Huawei RAN supports ATM OAM F5 end-to-end flows specified in ITU I.610. Fault

management (AIS: Alarm Indication Signal, RDI: Remote Defect Indication, CC: Continuity

Check and Loopback), performance management (forward monitoring and backward

reporting) and activation/deactivation are supported. The CC can be activated to monitor

AAL2 path VCC and Iu-PS user plane VCC end-to-end. When one VCC for AAL2 path or

Iu-PS GTPU is LOC (Loss of continuity), AIS, or RDI, this VCC is blocked. Then the service

is established on other alternative VCCs to prevent the failure of the call.

The BSC6900 only supports the fault management feature.

RAN12.0 introduces Huawei proprietary delay detection scheme. When an NE receives a

detection start command from the NMS, it starts detecting delay on the current AAL2 link or

AAL5 link and periodically reports the delay to the NMS. Huawei RAN uses the 8-byte

reserved IE (LB IE) in the loopback message to store the message transmission time. When an

NE receives the loopback message, it calculates the delay based on the time difference

between transmission and reception. This function provides enough information for

identifying transmission faults.

Enhancement

In RAN5.1, ATM OAM F5 flows on IuPS user plane VCC is introduced in BSC6800.

In RAN10.0, this feature is introduced in BSC6810.

In RAN11.0, this feature is introduced in 3900 series Node B, BTS3812E/AE and DBS3800

which support passive check.

RAN12.0 introduces Huawei proprietary delay detection scheme and thus provides more

transmission fault information.

Dependency


Only BSC6900 does not support the latency detection based on IE LB.


Only 3900 series Base Station supports the latency detection based on IE LB.




None.


None.



14 IMA Transmission for E1/T1 or Channelized STM-1/OC-3 on Iub Interface

14.1 WRFD-050304 IMA Transmission for E1T1 or Channelized STM-1/OC-3 on Iub Interface

Availability


Summary

This feature is concerned with IMA transmission for E1/T1 or channelized STM-1/OC-3 on

the Iub interface. This feature enables inverse multiplexing on ATM to improve transmission

reliability.

Benefits


Peak rates higher than the individual physical link rates, 1.5 Mbit/s for T1 or 2 Mbit/s for

E1.

Simplification of the ATM OM procedures, like monitoring one single ATM link instead

of several separate links.

Higher trunk level and statistical multiplexing gain.

Description

The inverse multiplex on ATM (IMA) mode is an ATM transport mode in the TC sub-layer of

the ATM physical layer.

In IMA mode, an ATM cell stream is distributed to several narrowband transport links. At the

peer end, the data streams from these narrowband transport links are converged into the

original ATM cell stream. IMA flexibly combines several narrowband transport links to

transport high-speed ATM cell streams, which is referred to as inverse multiplex on ATM. In

this manner, the existing narrowband transport links, especially 2 Mbit/s links, can serve

broadband ATM transmission. IMA also enhances transmission reliability.



PHY

PHY

PHY

PHY

PHY

PHY

Physical I ink #0

Physical I ink #1

Physical I ink #2

Single ATM cell stream

from ATM layer

Original ATM cell

stream to ATM layer

IMA virtual link

IMA group IMA group

There are several IMA links in one IMA group. If one link is broken, the service can be borne

by other links, and only the bandwidth shrinks. It provides more redundancy for the

transmission.

Enhancement

None.

Dependency

None.


15 UBR+ATM QoS Class

15.1 WRFD-050305 UBR+ ATM QoS Class

Availability


Summary

UBR+ ensures the connectivity of OAM connection and full use of the transmission

bandwidth.

Benefits

This feature ensures reliable OAM connections and full use of the transmission bandwidth.

Description

Huawei RAN supports UBR+ ATM service class. UBR+ is an enhancement of UBR with

MCR (Minimum Desired Cell Rate) indication. UBR+ is the most suitable for Iub OAM

channel. The MCR of UBR+ ensures the connectivity of OAM connection in the case of Iub

transmission resource congestion, and the best effort service of UBR+ uses the transmission

bandwidth completely.

Enhancement

None.

Dependency

None.



16 Link Aggregation

16.1 MRFD-210103 Link Aggregation

Availability


Summary

This feature supports the transmission of multiple FEs or GEs binding, thus improving the

reliability of FE transmission and meeting the requirements of higher data flow.

Benefits

This feature provides the method for improving the transmission reliability.

Description

Huawei GBSS/RAN implements the link aggregation based on IEEE802.3ad, thus improving

the system reliability and providing higher bandwidth.

This feature applies to the scenario where high reliability is required, for example, on the

ports of the MBSC and the hub NodeB where links are bundled together.

Figure 16-1 Networking for Link Aggregation

Interface board 1

Interface board 2

Router 1 RNC

Interface board 1

Interface board 2

Router 2 Hub NODEB

Bearer

network

Interface board 1

Interface board 2

Interface board 1

Interface board 2

Enhancement

None.

Dependency


None.




This feature applies only to the 3900 series base station.


None.


None.


17 System Reliability

17.1 WRFD-040100 Flow Control

Availability


Summary

This feature provides a series of mechanisms that can prevent the network or system from

being overloaded to ensure that the services with high priorities are handled properly even

when the traffic is busy.

Benefits

The feature ensures the stability and robustness of the RNC, and also ensures that services

with high priorities work properly during high traffic.

Description

Flow control in the radio network controller (RNC) is a set of mechanisms that the RNC uses

to prevent the network from being overloaded by regulating the input rate transmissions.

The system determines specific flow control measures in compliance with the load on the

following two resources:

CPU occupancy

The CPU is the core resource of the processing capability of the system. High CPU

occupancy means the current risk of insufficient processing capability. In this situation,

the flow control on corresponding functions should be triggered to ensure basic functions

of the system. After the CPU occupancy is lower than the proper threshold, the

previously-triggered functions are enabled.

Message block occupancy

The message block is the core resource for internal communication between the RNC.

High message block occupancy means there is the risk of inefficient processing

capability in the system. In this situation, the flow control on corresponding functions

should be triggered to ensure basic functions of the system. After the message block

occupancy is lower than a proper threshold, the previously-triggered functions are

enabled.

The flow control item corresponds to a function in the system, such as printing

information, debug information, system log, service-related RRC connection setup



request, paging message, and so on. The system enables, disables, or partially disables

the functions in compliance with the current resource load such as the CPU occupancy

and the message block occupancy to ensure system stability and robustness.

If a flow control item is controlled, the corresponding function is disabled or partially

disabled. If a flow control item is restored, the corresponding function is enabled again.

Enhancement

None.

Dependency

None.

17.2 WRFD-040101 DPU Board Replaced without Service Interruption in RNC

Availability


Summary

This feature enables the replacement of a partially faulty user plane processing board (DPUb

or DPUe) in the RNC, while minimizing the possible impact to existing calls.

Benefits

Operators benefit from the following aspects:

Maintenance personnel can replace a faulty board in time without waiting until the traffic

is light (generally in the early morning).

The ongoing services on the faulty board can be ensured to the maximum extent. The

impact on the real-time services is reduced, thus reducing user complaints.

Description

When the DPU board is faulty, for example, one or more processors in the board are faulty,

the general solution is to replace the board. To avoid call drops during the replacement, shift

operation can be arranged only in the early morning when the traffic is light. In this case,

maintenance personnel need to wait for several hours before replacing the board. This feature

enables maintenance personnel to replace the board immediately after the fault occurs by

disabling the board. This shortens the waiting time. The operation is as follows:

When a DSP fault alarm or DPUb/DPUe board alarm is reported, maintenance personnel

can replace the faulty DPUb/DPUe board after disabling the board by running an MML

command. The disabling operation using the MML command consists of disabling all

DSPs in the DPUb/DPUe board and disabling the DPUb/DPUe board directly. At this

moment, new services are established another normal DPUb/DPUe board, and the cell



common channel established on the faulty board is also re-established on another board

functioning normally. The faulty board processes only the ongoing services.

Maintenance personnel can query the user number on the DPU board by MML command, if

the number is lower than an acceptable value, the DPU board can be replaced.

Enhancement

None.

Dependency


BSC6800 does not support this feature.


None.


None.


None.

17.3 MRFD-210101 System Redundancy

Availability


Summary

This feature provides the reliability designs such as the active/standby mode, load sharing,

and redundancy configuration, thus improving the system reliability.

Benefits

This feature improves the system stability and thus ensures the network performance.

Description

To ensure the reliable operation of the system, reliability designs such as the active/standby

mode, load sharing, and redundancy configuration are widely used in Huawei GBSS/RAN.

In resource pool mode, the load sharing is performed among processing units in the pool. The

processing unit is not backed up. When one or multiple processing units are faulty, the

ongoing services are disrupted, and the new services requests are allocated to other normal

processing units in the resource pool.



In active/standby mode, the active board processes services while the standby board acts as a

backup of the active one. When the active board is faulty or needs to be replaced, the services

can be switched over to the standby board. In this way, the system can work continuously.

There are two types of switchover. One is automatic switchover. That is, the services are

automatically switched over from the active board to the standby board when the active board

is faulty. The other one is manual switchover. That is, the maintenance engineer performs the

board switchover on the LMT. If the active/standby switchover is allowed, a dedicated

maintenance module instructs the relevant boards to perform the switchover after the

maintenance engineer sends an immediate switchover command to the system.

To perform the active/standby switchover successfully, the following conditions must be met:

The standby board must be in position and work normally.

No major or critical alarm is reported.

When the standby board is switched over to the active one, the previously active board will be

reset automatically. If this board restarts normally, it becomes the standby one. In this way,

the boards still work in active/standby mode.

Redundancy configuration consists of the following units: boards, transmission interfaces,

power, and fans. The software version and important data configuration file are backed up to

ensure that the system works normally even if exception occurs in the file or data.

For the BSC6900, the dual-switching system of the control plane and user plane is applied. In

addition, the resource pool of control plane and user plane is designed. For the service

processing boards, the resource pool is adopted. That is, load-sharing is performed in the

resource pool. For other boards, the backup mode is adopted. That is, the boards of the same

type in two neighboring slots work in active/standby mode. The resource pool is

independently established within the GSM or UMTS.

Huawei BTS/NodeB supports the board-level backup. Two boards of the same type work in

active/standby mode. When the active board is faulty, an active/standby switchover is

performed and the previously standby board works in active mode.

For the interface board, the board backup mode is adopted. Some interface boards support the

standard backup modes specified in protocols, such as MSP 1+1 or MSP 1:1.When detecting

that the board is faulty, the system re-establishes the transmission of the ongoing services on

the standby board by adopting an active/standby switchover. When detecting that the active

channel is damaged, the system enables the transmission of the ongoing services to recover on

the standby channel by adopting an active/standby switchover.

Enhancement

None.

Dependency


None.


None.


None.




None.

17.4 MRFD-210102 Operate System Security Management

Availability


Summary

This feature provides the customized security policy and patch management for the operating

system on the OMU.

Benefits

This feature ensures system reliability and prevents the security threats and attacks on the

operating system.

Description

This feature provides the customized security policy and patch management for the operating

system on the OMU.

Customized security management of the operating system:

The customized security policy protects the operating system from being attacked and thus

enhances the security of the operating system. This feature can be applied to the Windows

2003 Server and the Linux operating system. The customize security policies are as follows:

Execution policy

You can execute one or more policies and record the execution results in log files.

Rollback policy

After executing a security policy, if you want to restore the system to the previous state

or customize the policy again, then you can restore the executed policy.

Generating backup files

You can save the current status of a policy into a file. This file can be used as a backup

for rollback.

Saving settings

You can save the current policy settings.

Exporting settings

You can export the current policy settings to another file.

Importing settings

You can import the file containing the policy settings into the system. In this way, the

system has the same settings.

Importing the configuration file of the earlier version

You can import the configuration file of the earlier version to the SetWin.

Reloading the configuration file



The SetWin has an inherent configuration file. You can reload this configuration file to

the SetWin. (for Windows OS only)

Patch management of the operating system:

Based on the type of the operating system, you can timely perform the patch compatibility

test to ensure that the patch is valid. The patch list corresponding to the operating system is

provided at least twice a year.

Anti-Virus:

When Windows 2003 Server is employed, Anti-Virus solution is available as following:

Integrate with TrendMicro Officescan 7.3 with one year of warranty

To deploying an OfficeScan 7.3 server in OSS network, it can protect all the BAM/OMU

from infected by antivirus with installing OfficeScan client program on BAM/OMU.

Enhancement

RAN11.0 supports Anti-virus security solution.

Dependency


None.


None.


None.


None.


18 RAN Operation & Maintenance

18.1 MRFD-210301 Configuration Management

Availability


Summary

This feature provides operators with the method for collecting and managing the information

about NEs (MBSC and MBTS). It can control the links between the NEs. The graphic user

interface (GUI) makes it easy for configuration management.

Benefits

This feature provides a descriptive overview of the current status of the network and supports

fast installation, capacity expansion, and data configuration of the network.

Description

This feature provides operators with the method for collecting and managing the information

about NEs (MBSC and MBTS). It can control the links between the NEs. The graphic user

interface (GUI) makes it easy to for configuration management.

The NE configuration can be classified into five levels:

Initial configuration

Design the initial configuration of the MBSC and MBTS.

Basic site configuration

Configuration of the O&M communication between the MBSC, MBTS, and the M2000

External site hardware configuration on the MBTS side

Configuration of TMA data and antennas

MBTS configuration and site-specific configuration on the MBTS side

Data configuration of the A/Iu interface, Abis/Iub interface, Iur-g/Iur interface, and the

transport network

Cell/TRX configuration on the MBSC side

Data configuration of cells, channels, and neighboring cells



Configuration from level 1 to level 3 can be implemented either with the GUI of the

configuration tool or with the pre-defined configuration files on the LMT. Configuration of

level 4 and level 5 can be implemented either through the M2000 or through the configuration

tool.

Online/Offline data configuration and status query

The configuration data is not sent to the host until it takes effect. This improves the

efficiency of configuring a large quantity of data. The MBSC supports offline

configuration based on host subracks. Therefore, the services are not interrupted during

capacity expansion.

During the switchover of the IP interface board and the ATM/TDM interface board,

offline configuration supports the modification of the interface board type and the

switchover of the active/standby boards.

Online data configuration enables the data to be sent to the host immediately after the

configuration. There is no need to reset the system or reload the data.

ITU-T Recommendation X.731 defines the object status. The operators can query the

object status such as the board status or cell status and the time of the latest status

change.

Configuration right control

With the configuration right control, data can be configured only on the LMT of the

MBSC/MBTS or the M2000 client. In addition, the operators always have the

configuration right. This improves the reliability of the system.

Configuration rollback on the MBSC side

When the equipment or network malfunctions due to improper data modification,

operators can perform the rollback operation to restore the system in a short time.

MBSC data backup

Two OMUs work in active/standby mode. The system synchronizes the data on the

standby OMU with that on the active OMU.

The MBSC supports automatic backup and manual backup. It provides a data backup

and restoration tool.

Setting of network parameters

The radio network parameters are of two types: MBSC-oriented parameters and

cell-oriented parameters, which are used in different radio conditions. The MBSC can

check the integrity and consistency of configuration data such as the data of a cell.

Detection of missing neighboring cell

Based on the measurement information from the user equipment (UE), the neighboring

cells missed for configuration can be detected and reported. This helps the operators

optimize the configuration of neighboring cells and thus improves the network planning

efficiency.

Enhancement

RAN5.1 supports the modification of the interface board type and active/standby state of

boards in offline mode.

RAN5.1 supports the query of the time when the latest status changes.

RAN10.0 supports the reporting of MBTS status to the M2000.

GBSS9.0&RAN11.1



Web LMT: The operation and maintenance GUI of the MBSC uses the Web LMT based on

the browser/server mode. The configuration GUI uses the CME. The MML client is

incorporated in the Web LMT and thus the configuration and maintenance for the MBSC can

be carried out through the MML commands. After the Web LMT is used, there is no need to

install the LMT software on the local PC. The configuration and maintenance for the MBSC

can be carried out through the Web browser. In addition, the upgrade of the software on the

local PC is not required when the MBSC software is upgraded, and thus the operation

efficiency is significantly improved.

Dependency


None.


None.


None.


Configuration management is implemented through the M2000 or the LMT.

18.2 MRFD-210302 Performance Management

Availability


Summary

This feature periodically takes samples of counters about the management objects, bearer

resources, and services. The sampled data is then collected, saved, monitored, and analyzed.

In this way, the operating status of the network can be obtained. Thus, this feature helps

operators quickly locate and solve problems and optimize the network.

Benefits

This feature provides an efficient method for monitoring the network performance and

facilitates the network troubleshooting and optimization. The real-time performance

monitoring is a more effective feature.

Description

Performance management helps collect the measurable performance data to obtain the

network operating status, thus helping the operators quickly locate and solve problems and

optimize the network.

Performance measurement management



This feature provides operators with a method for managing the measurable performance

data.

For the new commissioning NEs (MBSC and MBTS), the pre-defined performance statistics

completely starts after the initial start-up or restart. The performance statistics can be

suspended or restored manually.

The MBSC and MBTS provide the interfaces between them and the M2000, allowing the

M2000 to collect necessary statistic data and to configure the related parameters including

statistic counters and periods.

The statistic data is saved on the M2000 in binary-formatting files in every statistic period.

The result files are saved on the MBTS for up to 24 hours or on the MBSC for up to 10 days.

If a fault occurs in data transmission, you can obtain the lost data through the M2000.

Performance measurement counter

The performance measurement counters include key counters and other counters. The key

counters are used to generate the KPIs of the network which are defined on the M2000, and

these pre-defined counters are initialized immediately after the MBSC and the MBTS start.

The KPIs, related original counters, and formula can be added, modified, and deleted on the

M2000. Other counters indicating the network performance can also be added as required.

In the UMTS network, the following measurement objects are supported:

Cell measurement

Neighboring cell measurement

Inter-RAT neighboring cell measurement

RNC overall measurement

ATM transport measurement

IP transport measurement

Standard interface measurement

NE hardware measurement

Real-time performance monitoring

This feature supports the real-time performance monitoring and displays the details of the

monitoring result in the GUI. Thus, it facilitates the troubleshooting, drive test, network

optimization, and other operations.

The monitoring tasks are managed by the LMT of the NE (RNC and NodeB). The data

monitored is displayed in curve and stored in a file automatically for later review.

The following items can be monitored in real time:

Equipment performance: CPU usage, clock source quality, and so on.

Connection performance: SIR measurement, UE transmits power, and so on.

Cell performance: PCPICH transmit power, number of UEs in the cell, and so on.

Link performance: IMA group, UNI link, and so on.

Service performance: RF performance, UL channel scanning, and resource usage.

In the GSM network, the following performance counters are supported:

The measurements can be classified into the following types according to the measurement

object:

BSC measurement



Cell measurement

TRX measurement

Neighboring cell measurement

The measurements can be classified into the following types according to the MS status:

Paging

Call

Measurement report

Channel allocation

Enhanced performance measurement:

Measurement of incoming and outgoing cell handovers

This measurement provides data about the incoming and outgoing cell handovers. The

collected measurement data assists the operators in network adjustment and

optimization.

Undefined adjacent cell measurement

This measurement provides BSIC, BCCH frequency, average signal strength, number of

MRs of adjacent cells that are included in the BA list but not included in the adjacent cell

relation table. The collected measurement data assists the operators in network

adjustment and optimization.

Defined adjacent cell measurement

This measurement provides BSIC, BCCH frequency, average signal strength, number of

MRs of the defined adjacent cell. The collected measurement data assists the operators in

network adjustment and optimization.

Uplink and downlink balance measurement

This measurement provides the data about the balance between the uplink and downlink

of TCHs. The uplink and downlink balance level is graded according to the receive

levels in the uplink and downlink. The collected measurement data assists the operators

in network adjustment and optimization.

Call drop measurement

This measurement provides the average level and quality in the uplink and downlink,

and also the average TA value of SDCCH call drops and TCH call drops. The collected

measurement data assists the operators in network adjustment and optimization.

BTS out-of-service measurement

This measurement is provided by the performance management of the BSC together with

the M2000. This measurement provides the start time of BTS out-of-service, end time of

BTS out-of-service (or service recovery time), and the duration of BTS out-of-service.

Enhancement

UMTS

RAN5.1 supports HSDPA-related counters and monitoring items.

RAN6.0 supports HSUPA-related counters and monitoring items.

RAN10.0 supports the real-time performance monitoring on the IP patch.

GBSS



GBSS8.0 supports the real-time performance monitoring and the counter measurement

related to the built-in PCU.

GBSS8.1 supports real-time traffic measurement, enhanced IP performance

measurement, and measurement period of 24 hours. In addition, it supports the

measurement of traffic statistics of group call and group broadcast on the BSC level and

cell level.

Dependency


None.


None.


None.


Performance management is implemented by the M2000, and the real-time performance

monitoring is implemented by the LMT.

18.3 MRFD-210303 Inventory Management

Availability


Summary

This feature assists in reporting the information about the physical and logical objects of the

NEs to the M2000, and also assists in managing this information on the M2000.

Benefits

As a large number of devices are deployed on networks, it becomes difficult to manage

equipment. For ease of equipment management, operators need to obtain the information

about the physical device and some important logical information. With this feature, the

information can be reported to the M2000, thus facilitating the asset management. In addition,

operators can obtain the accurate decision-making data of the existing networks in time.

Description

The inventory management helps operators to manage the network assets and configuration

data. With this function, network assets and configuration data can be managed on the

M2000.

The objects that are managed by this function include physical objects (such as rack, frame,

slot, board, and fan) and logic objects (such as cell, software, and patch).



Upon a request from the M2000, the information about the network assets and configuration

data are generated in an .xml file and then are sent to the M2000. The M2000 saves the

uploaded information in the network inventory database.

Upon a request from the M2000, the MBSC reports its information about the assets and

configuration to the M2000. In terms of the method of collecting and reporting the

information about the base station, the UMTS network is different from the GSM network.

In the UMTS network, the NodeB works as an independent NE and supports the reporting of

its inventory information to the M2000.

In the GSM network, the inventory of the BTS is jointly controlled by the BSC and the BTS.

The BTS inventory management system is deployed on the M2000. The M2000 sends the

required inventory information command to the BSC through the southbound interface. On

reception of this command, the BSC queries the inventory information about all the BTSs,

generates files, and sends the files to the M2000. Then, the M2000 interprets the files and

saves them in the database. Some inventory information can be imported through the manual

input or other files. The M2000 supports the query, synchronization, modification, export, and

import of the BTS inventory information.

The BTS supports the reporting of the information about the electronic label, software version,

and hardware version of the BTS boards as well as the information about the manufacturer of

the heat exchanger. In addition, the BTS also supports the input and reporting of the bar code

of the BTS cabinet.

As the ID of a board, the electronic label provides the basis for board replacement, presents a

traceable mark in the entire lifecycle of the board, and supplies the data required for the

management, tracing, and maintenance of the board. The information about the electronic

label of the BTS board includes: the board model, bar code, BOM code, description,

production date, name of the manufacturer, and release number.

The M2000 provides the import or modification function for the inventory information that is

not supported by the BTS. That is, the information can be manually entered. The information



includes the information about the BTS antenna, electronic label of the board that fails to

report the electronic label (mainly purchased parts), and the ultimate service time of the board

information area. This information is not sent to the BTS for storage but is saved only in the

inventory management system on the M2000.

In addition, no storage part is available in the BTS cabinet, and thus the bar code of the

cabinet needs to be manually entered on the M2000 or the LMT. The BTS supports the input

of this information and also the storage of it in the main control board of the BTS. Then, the

BTS sends the information to the BSC through the inventory management interface.

Enhancement UMTS

None.

GSM

GBSS8.0 supports the reporting of the electronic label of the BTS board according to

electronic label standards 3.0.

GBSS8.1 adds the reporting of the information about the software and hardware versions

of the BTS boards, manufacturer of the heat exchanger, electronic labels of the BBU

backplane, fan board, and power monitoring board, and the input and query of the

electronic bar code of the cabinet.

Dependency


None.


None.


None.


Inventory information can be queried only on the M2000. Therefore, the M2000 should

support the inventory management feature.

18.4 MRFD-210304 Faulty Management

Availability


Summary

This feature involves various fault management functions such as system auto test, fault

detection, fault monitoring, and fault rectification of the UTRAN. This enables the operators

to learn about the network fault timely and take proper measures to avoid service interruption.



Benefits

This feature provides the following benefits:

Enables the automatic monitoring of the network equipment.

Enables the operators to learn about the actual state of the network timely and

comprehensively by querying the active alarm list and alarm log.

Facilitates the manual board test, with which the operators can identify the faulty board

timely.

Description

The fault management involves system auto test, fault detection, fault monitoring, and fault

rectification. This enables the operators to learn about the network fault timely and take

proper measures to avoid service interruption.

The automatic hardware test of the system is performed during the startup of the MBSC or

MBTS. When the MBSC or MBTS is in operation, the system status monitoring can also be

started manually if required.

Fault detection

This involves the fault detection of the physical layer, transmission link layer, and others.

The fault detection can be started manually. Operators can either browse the monitoring

result online or save the monitoring result as files.

Alarm management

Operators can browse the real-time alarm information, query the history alarm

information, and save the alarm information as required. The online help provides

detailed methods for clearing alarms.

Alarm correlation processing

Based on certain built-in mechanism, the alarm correlation handling mechanism enables

the system to keep the most important alarms instead of all the related alarms when a

fault occurs. The number of alarms can be greatly reduced in this way and network

problems can be easily identified and handled. This mechanism is pre-defined and

incorporated in the NEs such as MBSC and MBTS. More alarm correlation processing

mechanisms can be defined by the operators on the M2000.

The operators may also filter the alarms of an object. The alarms of this object, if filtered, are

not reported.

The alarms of the access network include MBSC alarm and MBTS alarm.

MBSC alarm

The MBSC alarm system provides two types of alarm output devices: alarm console and

alarm box. The alarm box provides visual and audible alarms. The alarm console is a part of

the OMC. It provides detailed alarm information, recovery suggestion, and alarm box control.

The MBSC alarm system is composed of the BAM alarm module, centralized network

management alarm database, alarm console, and alarm box. Alarm system accurately provides

the fault information detected by the MBSC system to the maintenance personnel through

alarm information. The maintenance personnel can then rectify the fault accordingly.

Alarm severity



According to the severity and influence of the alarms, there are four alarm severities:

critical, major, minor, and warning. Different severity of alarms is presented in different

manner, such as color and sound.

Alarm classification

According to its subsystem and subsystem type, alarms can be classified into fault alarm

and event alarm. Clearance alarms are provided for fault alarms. Event alarm has no

corresponding clearance alarm.

According to the cause of alarms, alarms can be classified into inter-module

communication alarm, signaling subsystem alarm, clock subsystem alarm, and power

supply subsystem alarm. These alarms help the maintenance engineers quickly locate the

faults. This feature also provides alarm about software running, such as CPU overload

alarm and GBAM hard disk capacity alarm.

Alarm location and recovery suggestions

The alarm console provides detailed alarm information, including the ID of the board for

which the alarm is generated, the potential cause and possible consequence of the alarm,

and the recovery suggestion.

Alarm box control

The alarm box control provides manual control of the alarm box. You can mute the alarm

sound or turn off the LED for the alarm box manually on the OMC alarm console. The

alarms can be printed in real time. The alarm parameters data can be configured and

modified. Based on the configuration, the MBSC can automatically control where the

alarms will be sent, such as to alarm box or to OMC alarm console. This enables flexible

alarm control.

Alarm query

The alarms can be queried in various conditions. You can browse the fault alarm,

emergency event alarm, or other event alarms in real time on the alarm console. You can

also query the history fault alarm, recovery alarm, and event alarm according to alarm

serial number, alarm ID, date and time of alarm, alarm module number, function number,

or alarm level. The queried history alarms can be saved.

Environment monitoring unit

Each subrack of the BSC6900 can connect to an environment monitoring unit (EMU)

through the serial ports. The EMU has four types of ports: fixed analog ports (four) used

for receiving –48 V voltage, –24 V voltage, temperature, and humidity alarms; extended

external analog ports (four); fixed external Boolean ports (four) used for receiving water,

smoke, infrared, and door status alarms; and extended external Boolean ports (32).

Alarm information is stored on the M2000. MBSC has buffer capability. A maximum of

300 thousand history alarm records can be stored.

MBTS alarm

MBTS alarms can be queried according to the site number, cell number, or TRX number

(applicable to BTS) so as to confirm the failure and clearance sates.

MBTS alarms can be queried and displayed on both the alarm console at the remote end and

the Site Maintenance System at the local end.

The MBTS alarm supports the input interface of the environment alarm. The environment

alarms supported by the MBTS are fire, smoke, temperature, humidity, door control, and main

supply alarms. The ranges of alarms can be controlled by alarm threshold setting on the

MBSC. The MBTS also supports the function of clearing environment alarms to provide

flexible clearance of the alarms.



Enhancement

UMTS

RAN5.1 supports the handling of HSDPA related alarms.

RAN6.0 supports the handling of HSUPA related alarms.

RAN6.0 supports the E1/T1 BER measurement.

RAN10.0 supports the fault diagnosis of the IP path.

RAN10.0 supports the reporting of the status of the MSC resource pool.

In RAN11.0, the RNC supports the alarms of external AC power.

GSM

The GBSS8.0 supports the clearance of PS-related alarms, including device alarms and

service alarms.

The GBSS8.1 supports suppression of the intermittent and repeated alarms, alarm

correlation processing, and enhanced alarm positioning information.

Dependency


None.


None.


None.


The fault management is implemented through the M2000 or the MBSC/MBTS LMT.

18.5 MRFD-210305 Security Management

Availability


Summary

This feature enhances the network security management by providing various user

authorization and management mechanisms.

Benefits

This feature provides user authorization and management mechanism, thus enhancing the

network security management.



Description

Security management enhances the system security in terms of the following aspects:

Facilitates user management such as the management of user accounts, user rights, and

user command groups.

Supports the backup and restore of the system data.

Adopts the Windows security policies for the IP services of the BAM to protect the

system from network attacks.

Supports the installation of antivirus software such as Norton, Macfee, and Officescan.

Collects the database operation logs and auditing logs.

Reports corresponding alarms when network attacks are detected or the number of

unauthorized accesses exceeds the threshold.

Supports FTP over the Security Socket Layer (SSL).

Supports SSL for the communication between the OMC and the GBSS/RAN. This

enables the encryption of all transmitted data.

Adds authority control for the binary interface between the GBSS/RAN and the OMC.

Records the information about the operation logs for the binary interface between the

GBSS/RAN and the OMC.

Enhancement

UMTS

RAN6.0 supports the SSL encryption of the FTP transmission.

RAN10.0 supports the SSL encryption of the data transmitted between the GBSS/RAN

and the OMC.

RAN11.0 supports the authority control and log recording for the binary interface

between the GBSS/RAN and the OMC.

GSM

None.

Dependency


None.


None.


None.


None.


19 Message Tracing

19.1 MRFD-210801 Interface Message Tracing

Availability


Summary

This feature is used for interface message tracing in online/offline mode, tracing result review,

and routine equipment management.

Benefits

This feature simplifies the process of monitoring the signaling over the radio transmission

interfaces and facilitates network optimization and fault rectification.

Description

This feature is used for interface message tracing in online/offline mode and routine

equipment management.

With this feature, the GBSS/RAN can trace messages in real time, stop updating, save the

tracing messages, review the tracing result, and check the time when the message is sent. In

this way, the maintenance personnel can accurately locate and solve problems. In addition, all

the interfaces have the condition filtering function. Therefore, the maintenance personnel can

reduce the number of traced messages through condition filtering, thus improving the tracing

accuracy.

In the case of the GBSS system:

The BSSAP, MTP2, MTP3, and SCCP messages can be traced over the A interface as

required. The BSSAP messages can be filtered according to the message types such as the

BSSMAP, paging messages, and DTAP messages. You can also select the traced messages

according to the cell.

The RSL, OML, and LAPD messages can be traced over the Abis interface. The LAPD

messages can be filtered according to the site and TRX number. The RSL messages can be

filtered according to the message type, such as the measurement report, paging, and channel

request. The OML messages can also be filtered according to the message type.

The application layer messages and the LAPD messages can be traced over the Pb interface.

The LAPD message can be selected and traced according to the timeslot number. The



application layer messages can be traced according to the site number and the message types

such as paging.

In the case of the RAN system:

The operator can verify the configuration data, locate and solve problems by tracing the

messages over the Iu, Iub, Iur, and Uu interfaces. After the configuration data is set, the

operator can determine the correctness of the signaling links by tracing and interpreting the

messages over the Iu, Iub, Iur, and Uu interfaces. The operators can also locate exceptions

when exceptions occur.

Therefore, tracing and interpreting the messages over the Iu, Iub, Iur, and Uu interfaces can

take the place of the signal analyzer to perform the interoperability test between the RNC and

other network elements.

All the interfaces can filter the messages according to the message layer or the logical object.

In this way, the number of traced maintenance signaling can be greatly reduced. Thus, the

tracing accuracy is improved and the problem location speed is accelerated.

Operators can also use this feature to optimize the network.

Enhancement

UMTS

None.

GSM

The GBSS8.0 supports the tracing over the Gb interface and the packet message tracing

over the Um interface.

GBSS8.1 supports the tracing of the VGCS/VBS messages

Dependency


None.


None.


None.


None.

19.2 MRFD-210802 User Signaling Tracing

Availability




Summary

With this feature, the signaling of an MS can be traced on the GBSS/RAN side. In a tracing

window, all the signaling of an MS in the GBSS/RAN can be traced. In addition, you can

manage the tracing task, save the messages, and review the tracing result.

Benefits

This feature facilitates the monitoring of the radio signals and transmission interfaces of

specified MSs and thus facilitates network optimization and fault rectification.

Description

With this feature, the characteristic words of the called MS are entered on the LMT for tracing

the signaling of the calling MS. The characteristic words include IMSI, TMSI, MSISDN, and

IMEI. The host decodes the signaling of each call. If the information of the MS matches the

characteristic words of the MS to be traced, the signaling of this call is returned to the LMT

for display. This feature traces the signaling of an MS on various interfaces, saves the

messages, and reviews the tracing result. In this way, the message tracing on each interface

can be avoided, thus improving the troubleshooting efficiency and facilitating the problem

locating of an MS.

With this feature, the signaling of the specified MS is traced to evaluate the network status,

based on which operators can perform network optimization.

Enhancement

UMTS

None.

GSM

GBSS8.1 supports the PS single user tracing and VGCS/VBS message tracing.

Dependency


None.


None.


None.


None.


20 Software Management

20.1 MRFD-210401 BSC/RNC Software Management

Availability


Summary

This feature provides functions of software installation, software upgrade, and patch

installation of the MBSC. This facilitates the remote management of the MBSC software.

Benefits

This feature provides functions of software installation, software upgrade, and patch

installation of the MBSC, thus reducing the O&M cost for operators.

Description

The MBSC supports the software management. This feature facilitates the remote

management of the MBSC software. The operators can run the MML commands to:

Query the information about the software version and other information about the

running system.

Upload, download, and activate the program file, patch file, and license file, and copy

the data files and log files to the FTP server.

Use the BAM server of the MBSC as the FTP server and transmit files such as program

file and patch file by using the wildcard between the FTP server and the FTP client.

Perform the remote patch upgrade of the BAM server of the MBSC.

Use the MBSC as the transmission medium to transmit files between the M2000 and the

MBTS.

In addition, the operators can control the product software through the operation and

maintenance center (OMC), including the program, patch, license, data, and log. The OMC

can identify and match the product software version. In this way, the efficiency of product

upgrade and data downloading is improved.

Enhancement

UMTS



RAN5.1 supports the remote patch upgrade of the RNC BAM.

RAN6.1 supports the software management based on two versions, thus facilitating the

upgrade and rollback of versions.

RAN10.0 supports the combined patch management functions of the BAM and RBS.

RAN11.0 supports the validity check of the configuration scripts before upgrade and

supports the verification of the system configuration after upgrade. This reduces manual

intervention during upgrade and improves the upgrade efficiency and reliability.

RAN11.0 significantly shortens the duration of service disruption caused by the upgrade

of a fully-configured RNC. In this way, the upgrade with a minimal loss, which is

applicable only to the BSC6810, is achieved.

GSM

GBSS8.1 supports the remote upgrade of the BSC and BTS software.

Dependency


None.


None.


None.


None.

20.2 MRFD-210402 BTS/NodeB Software Management

Availability


Summary

This feature enables the operator to remotely manage the software installation and upgrade of

the MBTS. This feature supports enhanced functions such as automatic change of the

signaling bandwidth, software downloading based on the configuration, software

downloading resumption, downloading and activation of software in batches, and hot

patching.

Benefits

This feature provides efficient and accurate software installation, software upgrade, and

software version management.



Description

This feature helps the operator to remotely manage the MBTS software. The operator can

perform the following operations through MML commands:

Upgrade the software of the network element: Download the software package from the

OMC M2000 to the MBTS through the OMCH. And then run the software activation

command on the OMC M2000 client. At last the MBTS automatically loads the software

to the corresponding board and switches over the active and standby directories on the

MBTS.

File management involves downloading and uploading data configuration files.

including operation log files, monitoring log files, board log files. UMTS configuration

files also include RTWP routine test logs, and CAN log files.

Software version management includes software version query, software/hardware

version consistency check, software download, software activation, and software version

synchronization. In addition, it involves license file query (only supported by UMTS)

and hot patch management.

UMTS can downloading and uploading data configuration files. The user can download

data configuration files from the FTP server to the Node B to overwrite the original data

configuration files or upload data configuration files from the Node B to the FTP server.

Enhancement

In RAN5.1, the following enhancement features are introduced in UMTS:

OMCH UBR+ (Unspecified Bit Rate+): This allows the configuration of a minimum

bandwidth (e.g. 64kbps) of the backhaul allocated to the OMC channel, even when the

traffic is heavy. On the other hand, when the traffic is light, the OMC channel can use

automatically a greater bandwidth, which improves the software download efficiency.

This is especially useful for example during network upgrades, to minimize the time

required to download the new software to the Node B, which can be done during the

night, in low traffic period.

Software download is configuration-based. That is, the user only needs to download the

board version files required for the current physical configuration of NEs. The

configuration-based software download can reduce 30% software package download

volume, thus speeding up the download process. For a newly added board, the system

only downloads the software corresponding to the board, thus improving download

efficiency.

If the network breaks down and then resumes within 24 hours, the system supports

resumable software download to prevent a repetition of downloads.

A maximum of 500 Node Bs can be selected concurrently to download and activate

software in batches. By default, 50 Node Bs per batch are selected.

RAN12.0 supports Node B hot patching without resetting the Node B, thus greatly

reducing the impact on the ongoing services.

In RAN12.0, the following enhancement features are introduced in UMTS:

Configuration of OMCH service priorities

If the OM stream has only one priority, its priority is set to the lowest level, namely, Best

Effort (BE); if the network is congested, the OM data and commands in the OM stream

may be delayed or discarded. If the OM priority is set to the highest level, namely,

Expedited Forwarding (EF), a large number of loaded and uploaded files of the Node B

occupy the network bandwidth, thus affecting other services.



RAN12.0 supports the configuration of OMCH service priorities in ATM or IP transport

of Iub. Different OM services can identify different DSCPs and different VLAN COS

priorities. The OM stream that has high real-time requirements and occupies a small

bandwidth can be identified as the highest level (EF). The OM stream that has low

real-time requirements and occupies a large bandwidth to download or upload files can

be identified as the lowest level (BE).

Upgrading with combination software

The function can reduce the number of upgrading and resetting NodeB. The basic software,

cold patch and hot patch can be combined to be downloaded at a time.

In GBSS6.1, the following enhancement features are introduced in GBSS:

UBR supported on the OMCH

Software downloading based on the configuration

Software downloading resumption

Downloading and activation of the software in batches

In GBSS9.0, the following enhancement features are introduced in GBSS:

Hot patching without restarting BTS.

Dependency


None.


None.


None.


None.

20.3 MRFD-210310 BTS/NodeB Software USB Download

Availability


Summary

With this feature, the user or the maintenance personnel can download and activate the MBTS

software through the USB without using the laptop. Thus, the MBTS can be set up easily and

quickly.



Benefits

With this feature, the software upgrade is independent of Abis/Iub transmission. Thus, the

upgrade is shortened and the MBTS can be set up quickly with a low cost. In addition, the

maintenance personnel need not enter the site again because they can perform the software

commissioning remotely.

Description

The 3900 series MBTSs provide the USB port to download and activate the host software.

After the MBTS hardware is installed, the system automatically upgrades the software when

the USB disk is inserted.

This feature enables the software upgrade to be performed through the USB without using a

laptop. With this feature, the software upgrade is independent of Abis/Iub transmission. Thus,

the upgrade is shortened and the MBTS can be set up quickly with a low cost. After the

software is activated and the system begins to operate, the hardware fault can be detected

according to the indicator on the BBU panel so that the fault is rectified in the shortest time.

In addition, the maintenance personnel need not enter the site again because they can perform

the software commissioning remotely.

Enhancement

None.

Dependency

Impact on the hardware of the MBSC

None.

Impact on the hardware of the MBTS

This feature should be supported by the 3900 series MBTSs.


None.


None.



21 Node B Configuration and Commissioning

21.1 WRFD-031100 BOOTP

Availability


Summary

The bootstrap protocol (BOOTP) enables the IP addresses to be obtained through the server

automatically. In ATM transmission mode, the Node B capable of BOOTP can automatically

create an O&M channel to the RNC, thus saving the O&M cost at the near end. This feature

describes the method of implementing the Node B BOOTP.

Benefits

This feature enables the automatic setup of the default maintenance channel from the far end.

It also enables maintenance personnel to load the data and software to the Node B, thereby

facilitating the maintenance of the network.

Description

Generally, after the hardware installation, the Node B only has the host software rather than

the data configuration file. This feature enables Node B to set up the OM channel to the RNC

automatically without configuration data. The maintenance staff can download the data and

software to the Node B through the OMCH at the far end. The feature decreases the operation

and maintenance costs and enhances the network maintainability and maintenance quality.

Node B will automatically set up the O&M channel using the BOOTP protocol. In addition,

Node B monitors the O&M channel. When the O&M channel is broken, Node B can rebuild

it.

Enhancement

None.

Dependency

None.



21.2 WRFD-031101 Node B Self-discovery Based on IP Mode

Availability


Summary

In IP transport mode, Node B self-discovery refers to the process in which the Node B

automatically obtains the IP address, VLAN information, and M2000 IP address. Through

self-discovery, the Node B can automatically establish an OM channel between itself and the

M2000.

Benefits

This feature supports remote automatic establishment of the default OM channel.

Maintenance personnel can remotely load data and software for the Node B through the

automatically established OM channel. This improves the network maintainability and saves

the costs of local maintenance.

Description

In IP transport mode, Huawei Node B supports two self-discovery modes: DHCP and

DHCP+AACP. In practice, the RAN starts different self-discovery modes according to actual

scenarios.

DHCP

In DHCP mode, the server (M2000) provides the IP address, gateway, and VLAN

information to the Node B after receiving the DHCP request from the Node B.

In DHCP mode, the requests and response messages sent by the Node B are all broadcast

messages. Therefore, they cannot be transferred between different IP subnets. When the

Node B and the DHCP server belong to different IP subnets, a DHCP relay is required to

transfer the DHCP messages to the server. After the network equipment with the DHCP

relay function in the network receives the DHCP broadcast request from the physical

subnet, it encapsulates the request according to the requirements defined in the DHCP

relay protocol and transfers it in unicast message format to the specified DHCP server.

Messages can be transferred between the Node B and the DHCP server that belong to

different IP subnets through the DHCP relay.

The DHCP function complies with RFC2131 and RFC2132.

DHCP+AACP

The difference between DHCP+AACP and DHCP is that DHCP+AACP configures the

Node B as the DHCP relay but DHCP requires the transmission equipment at the access

network side to provide the DHCP relay function.

For the IP RAN, the network equipment in some networks does not have the DHCP relay

function. For such networks, Huawei RAN introduces the DHCP+AACP combined

self-discovery mechanism.

In AACP mode, the server (M2000) sends IP probe packets to the Node B, and the Node

B obtains the gateway IP address, network segment mask, and VLAN information

through the general Address Resolution Protocol (ARP) procedure.



If the access gateway in the network does not support DHCP relay, Huawei RAN

remotely assigns a temporary IP address to a Node B belonging to the network segment

through the AACP. The Node B can obtain a formal IP address through the temporary IP

address. After the formal IP address is configured, the Node B can be configured as the

DHCP relay in the subnet. Then, the Node B can help other Node Bs in the subnet to

perform the self-discovery function through the DHCP mechanism.

The DHCP+AACP function is applicable only to the Ethernet transport.

Enhancement

RAN6.0 introduces the DHCP function.

RAN12.0 introduces the DHCP+AACP function.

Dependency


None.


Only the 3900 series Node Bs support DHCP+AACP.

Dependency on other features of the RAN

None.


M2000 should support Node B Auto Deployment function.

21.3 WRFD-031102 Node B Remote Self-configuration

Availability


Summary

With this feature, Node B software can be downloaded and activated automatically and

remotely. Therefore, there is no need to start a Node B locally.

Benefits

Maintenance personnel need not take any equipment to activate a Node B. This simplifies the

Node B start procedure and reduces the operation requirements and workload.

Description

During site deployment, after the hardware installation is complete, the Node B automatically

establishes an OM channel between itself and the M2000 through the BOOTP (ATM

transport), DHCP (IP transport), or DHCP+AACP (IP transport). The M2000 can



automatically download the Node B configuration data and related software and activate the

Node B remotely through the OM channel.

In RAN10.0, the Node B supports USB disk-based Node B start. After remote

self-configuration is introduced, the probability that USB disk-based Node B start and remote

self-configuration are used simultaneously is increased. In this case, the negotiation

mechanism is required. That is, when the software version loaded in the USB disk conflicts

with the remotely detected software version, the negotiation mechanism preferentially

chooses remote downloading. This avoids ping-pong effect of Node B software downloading.

Enhancement

None.

Dependency


None.


Only 3900 series Base station can support this feature.


None.


M2000 should support NodeB Auto Deployment function.

21.4 WRFD-031103 Node B Self-test

Availability


Summary

RAN12.0 introduces Node B self-test. This feature is applicable to the Node B start scenario.

During Node B start, after the software and configuration data are downloaded, the Node B

automatically performs software commissioning, fault diagnosis and service verification so

that it can operate normally.

Benefits

This feature reduces workload of commissioning. .

Description

After the software and configuration data are downloaded during Node B start, to ensure

normal operation, the Node B needs to perform the following functions:



Software commissioning: The Node B tests the interfaces and ports, OM channel, antenna

system, and boards. The Node B and RNC check the commissioning results and reports the

detected faults to the M2000. M2000 represents the faults as graphic interface.

Fault diagnosis: The M2000 requests the Node B and RNC to perform fault diagnosis on the

boards, antenna system, and E1 transmission links. This helps maintenance personnel to

identify faults accurately and rectify faults rapidly.

Service verification: The service verification is performed to check whether the traffic links

are successfully established. The RNC collects the performance statistics after the dial-up test

and then reports the statistics to the M2000. M2000 will check the statistics and output a

report about the status of the service verification.

Enhancement

None.

Dependency


None.


Only the 3900 series Node Bs support this feature.


None.


M2000 should support NodeB Auto Deployment function.

22 License Management

22.1 MRFD-210403 License Management

Availability




Summary

This feature involves the MBSC license control and MBTS license control.

Benefits

With this feature, the operators can purchase the license based on the network development,

thus reducing the initial cost of the network deployment.

Description

The license file is used to determine whether the optional features are available and how

many optional features are available.

The MBSC and the BTS share one license file. The NodeB uses its own license file. The

license files can be downloaded remotely to the MBSC and NodeB. The operators can

manage and query the contents in the license file through the LMT or the M2000 client.

The characteristics of the MBSC license management are as follows:

The MBSC and BTS share one license file.

The license file is downloaded from the M2000 and is controlled and activated on the

MBSC side.

The license can be used within one MBSC but not between the MBSCs.

The characteristics of the NodeB license management are as follows:

All the NodeBs under one RNC share one license file. That is, one RNS corresponds to

one license file. Each license file records the license information about all NodeBs in the

RNS.



The license is distributed on the M2000 and is controlled by the NodeB. The distribution

results are sent to the NodeB from the M2000.

The license information can be distributed between NodeBs but not between RNCs. The

total number of a control item cannot exceed the number recorded in the license file.

New or upgraded license files can be ordered from Huawei.

Enhancement

None.

Dependency


None.


None.


None.


None.



23 Basic Node B Functions

23.1 MRFD-210309 DBS Topology Maintenance

Availability

This feature is available from GBSS8.0 in the GSM and RAN 5.0 in the UMTS.

Summary

The LMT provides the topology maintenance for the distributed base station, and thus

facilitates the maintenance operations.

Benefits

This feature provides convenient O&M functions for the distributed base station, thus

reducing the O&M expenditure of the operators.

Description

The distributed base station supports the automatic scan of the RRU topology. The LMT

provides the topology maintenance for the distributed base station. The functions that

supported by this feature are as follows:

The networking structure of the distributed base station is displayed in a visualized way.

Different colors are used to mark the status of each BBU, RRU, and CRPI link.

The BBU or RRU can be selected directly from the displayed topology for maintenance.



Figure 23-1 UMTS NodeB topology

Figure 23-2 GSM base station topology

Enhancement

The RAN6.0 supports the automatic scan of the RRU topology.

Dependency


None.


None.




None.


None.

23.2 WRFD-031000 Intelligently Out of Service

Availability


Summary

This feature is introduced to prevent service disruption caused by insufficient battery voltage,

Node B reset, or cell blocking. When the preceding problems occur, this feature enables the

Node B to automatically reduce the pilot transmit power and hand over the UE to other 2G or

3G cells, thus preventing call drops.

Benefits

This feature allows the traffic to be switched to other 2G or 3G cells without dropping the

calls before the cell is out of service.

Description

The state of out of service is automatically triggered in the following cases:

Voltage of the batteries is lower than the pre-set threshold after the AC power is shut

down

Reset of the Node B

Cell block

When the state of out of service is triggered, the PCPICH power of the cells can be lowered

step by step until the UEs are switched to other 2G or 3G cells. For example, the PCPICH

power can be lowered to 1dB per 200ms. This allows the traffic to be switched to other 2G or

3G cells without dropping the calls before the cell is out of service.

Enhancement

None.

Dependency

None.



23.3 WRFD-031200 OCNS

Availability


Summary

In the system performance test, considering the limitations to the number of UEs and the

complexity of the test environment, it is difficult to use multiple UEs to construct a radio

transmission environment with certain interference. This feature enables the setup of multiple

downlink analog channels on the Uu interface to simulate the interference of multiple codes,

thus implementing the downlink load test of a cell.

Benefits

The feature provides an embedded function to simulate the cell load in the Node B. It makes

the cell load test more convenient.

Description

When the orthogonal code noise simulator (OCNS) is used, all analog channels use mutually

orthogonal channel codes and each channel code adopts irrelevant PN9 random data. All

analog channels use different powers, but the power proportion between channels is fixed.

This feature is used to simulate the signal interference between channel codes and signal PAR

in the real environment. The total power of all analog channels can be set to simulate different

downlink interference (load) levels, which facilitates the operator to evaluate the system

performance of a real UE in different downlink load levels.

This feature is performed on the OMC, and the cell load test of multiple Node Bs can be

started simultaneously.

Enhancement

None.

Dependency

None.

23.4 WRFD-031400 Power off the equipment level by level

Availability


Summary

After a mains failure, the operator can power off the equipment level by level by setting

different DC voltage thresholds to implement intelligent shutdown of RF modules and sites.

The battery capacity is sufficient for the system to work for a longer period of time.



Benefits

The intelligent power management function can reduce the investment in the battery backup

system and meet the customers' requirement for power saving. In particular at the hub Node B,

this function enables the Node B to set different shutdown thresholds without configuring

separate power backup systems for the Node B and the transmission devices. Thus, the

transmission devices can provide longer power backup.

Description

After a mains failure, for the site equipped with the battery backup system, the user can power

off the equipment level by level by setting different DC voltage thresholds to implement

intelligent shutdown of RF modules and sites, as shown in the following figure.

RF module intelligent shutdown

The Node B disables the RF module and keeps the baseband module and transmission

device working properly until the voltage decreases to a threshold (G2, load shutdown

voltage).

This function ensures long-time power backup for baseband modules and transmission

devices. In particular at the hub Node B.

Site intelligent shutdown

After the RF module intelligent shutdown, the Node B and all its modules are powered

off when the voltage decreases to a threshold (G3, battery shutdown voltage).

This function can save investment in the battery backup system. After a mains failure,

the system can work for a longer period of time, and in particular the transmission device

achieves longer power backup.

Enhancement

None

Dependency

NodeB must be configured with APM30/APM100/APM200 (the type of outdoor NodeB

cabinet for AC input) to support the function.



23.5 WRFD-031500 Solar Power Device Management

Availability


Summary

The solar power controller communicates with the Node B through dry contracts and serial

ports, and in this way the solar power controller monitors and manages the solar power

devices.

Benefits

This feature improves the operability and maintainability of the solar power devices.

Description

As a green energy, solar power is increasingly used in Node B equipment. The solar power

supply system work together with the power supply device, solar power controller, batteries,

and Node B. The solar power supply system uses solar power arrays to feed power to loads

and at the same time stores the surplus power in batteries. The entire solar power supply

system operates under the control of the solar power controller. In addition, Huawei solar

power controller supports diesel power input as the backup of solar power input or to

implement solar-diesel hybrid power supply to meet the differentiated requirements of

customers.

The solar power controller, which is replaceable and easy to manage, communicates with the

Node B through the RS485 serial port. The Node B supports the configuration, monitoring,

and alarm functions of the solar power devices.

The Node B supports the configuration of the power supply device and solar power

device.

− Configuring the capacity of batteries

− Configuring the parameters of the solar power controller, including the overvoltage

threshold, undervoltage threshold, and overtemperature threshold.

− Configuring the parameters concerning diesel power management, including the

diesel generator power and intelligent control enabling.



The Node B provides the function of querying the solar power array current, diesel

power current, and the running statistics of power supply.

The Node B supports fault alarms of power supply devices. The solar power controller

supports alarm reporting through the serial port.

The Node B provides the function of diesel generator testing. This function supports

manual or automatic testing of the diesel generator and the configuration of associated

parameters. During automatic testing, if the diesel generator fails to start, a failure alarm

is reported.

Enhancement

None.

Dependency

Only 3900 series Node Bs support this feature.

23.6 WRFD-021404 Single IP Address for Node B

Availability


Summary

The Node B single IP address function enables the Node B traffic channel and OM channel to

share one IP address, thus reducing the occupancy of resources and simplifying the

configuration of IP addresses. The Node B is configured with the OM IP saving mode.

Benefits

In IP transport, the Node B traffic channel and OM channel share one IP address, which

reduces the occupancy of resources and simplifies the configuration of IP addresses.

Description

The Node B IP address planning involves signaling plane address, user plane address, and

Node B maintenance address. Currently the typical application is to combine the signaling

plane address with the user plane address and to use the IP address of a port. The OM IP

address and IP address of a port, however, must belong to two different IP address, and

therefore operators need to plan two sets of IP addresses and routes during network

deployment. The Node B single IP address function enables the Node B traffic channel and

OM channel to share one IP address.

This function supports the following configurations:

The 3900 series Node B is configured with one WMPT board. The WMPT board has one

or more IP ports, and the OM IP address of the Node B can be the same as the IP

addresses of one of the ports. If the Node B has active and standby OM IP addresses,

they can be the same as the IP addresses of the two ports on the WMPT board.



The 3900 series Node B is configured with one WMPT board and one UTRP board,

either of which has one or more IP ports. The OM IP address of the Node B can be the

same as the IP address of one of the ports on the WMPT board. If the Node B has active

and standby OM IP addresses, they can be the same as the IP addresses of the two ports

on the UTRP board. However, it is prohibited that the OM IP address of the Node B is

the same as the IP address of the ports on the UTRP board.

Enhancement

None.

Dependency

The BTS3900, BTS3900A, and DBS3900 support this feature.

The BTS3812, BTS3812E, BTS3812AE, and DBS3800 do not support this feature.

23.7 WRFD-010212 Improved CE Mapping for E-DCH

Availability


Summary

This feature improves the uplink processing capability of the WBBPb board and makes

HSUPA services occupy less CE resources, thus improving the CE efficiency of the Node B

and saving the investment cost of the operator.

Benefits

Improve the CE efficiency, decrease the configured CEs.

Description

With the improved uplink processing capability of the WBBPb, HSUPA services occupy less

CE resources. The following table lists the occupation of CE resources.

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



Spreading Factor Former CE Mapping Improved CE Mapping

2SF2+2SF4 48 48

Enhancement

None.

Dependency


Only the 3900 series Node B supports this feature. And the 3900 series Node B must

configure WBBPb/WBBPd.


WRFD-010612 HSUPA Introduction Package


24 Documentation

24.1 MRFD-210701 Documentation

Availability


Summary

The feature describes the available documentation of the products.

Benefits

With this feature, the operators can obtain the product information and can perform

maintenance operations accordingly.

Description

The customer documentation includes the following documents:

MBSC documents

NodeB documents

BTS documents

The documentation covers the hardware description, installation, commissioning, operation,

and maintenance of the MBSC and MBTS.

The following table describes the documents:

Document Category Description

Product Description Describes the architecture, hardware configuration,

operation and maintenance, and technical specifications of

the product.

Hardware Description Describes the hardware of NEs, such as the cabinet, board,

and cable.

Installation Guide Describes the procedures for installing the cabinet, boards,

and cables.

Initial Configuration Guide Describes how to perform the initial configuration of NEs.



Document Category Description

Commissioning Guide Describes how to commission the NE to ensure that the

new NE can gain access to the BSS/RAN system.

LMT User Guide Describes the GUI, functions, and operations of the LMT.

Site Maintenance Guide Describes the hardware maintenance items and the

component replacement procedures

Routine Maintenance Guide Describes the routine maintenance methods of the MBSC

and MBTS.

Reconfiguration Guide Describes the common tasks and methods of data

reconfiguration of the MBSC and MBTS.

Reference The reference documents are as follows:

MML command reference: describes the information

about meanings, recommended values, and default values

of the parameters of each command.

Alarm reference: describes the information about

meanings of the alarms and how to clear them.

Performance counter reference: describes the information

about meanings and measurement points of each counter.

The documents have the following characteristics:

Topic-oriented: Based on the DITA technology, the information is provided under

separate topics.

Powerful advanced search: The information can be searched according to products or

data types.

Enhancement

None.

Dependency


None.


None.


The documentation CD-ROM is delivered with the product.


None.



25 Node B Antenna System Solution

25.1 MRFD-210601 Connection with TMA (Tower Mounted Amplifier)

Availability


Summary

This feature provides a solution to the TMA connection. Huawei MBTS complies with the

AISG1.1 and AISG2.0 protocols.

Benefits

In the uplink coverage-limited network, the use of the TMA can improve the receiver

sensitivity, enlarge the cell radius, reduce the number of MBTSs, and save the cost.

Description

The TMA is used to amplify the uplink signals. It is an optional device for the antenna and

feeder system. The TMA can compensate the feeder loss caused by long feeders. Thus, the

uplink sensitivity is increased and the uplink coverage capability is improved.

Huawei MBTS supports the third-party TMA, including AISG TMA.

The MBTS supplies power to and controls the TMA. Huawei MBTS can provide 10 V to 13

V output voltage to the TMA. When a major alarm related to the TMA is reported, the system

automatically sets the attenuation value of the RX channel to 0. After the alarm is cleared, the

system automatically sets the attenuation value of the RX channel to the configured value.

In the case of the AISG TMA, the RET control signal, power, and RF signal are transmitted

through the feeder cable. Thus, operation and maintenance of the AISG TMA is easy. Smart

bias tee (SBT) provides power supply to the TMA and the RET control signal to the RCU

through the feeder cable.

Huawei provides dual TMAs. Each TMA consists of two TX/RX branches, and only one

TMA is required in each sector. Each TMA includes also a supervision and alarm unit in the

low noise amplifier (LNA). The functions of both branches are the same and the function of

one pair of branches is described as follows.



The RX channel of each branch consists of two RX filters and an LNA. The LNA can be

automatically bypassed when the DC is faulty. There is a bias tee in the BTS port of the TMA.

For the SMART TMA, this bias tee is called the smart bias tee. Bias tee can separate the DC

current from the RF signals and provide power supply to the LNA and the RET control signal

to the RCU. The TX channel includes a TX filter.

Huawei MBTS supports two kinds of TMA with the gain of 24 dB and 12 dB.

Enhancement

GSM

The GBSS6.1 complies with the AISG1.1 protocol.

UMTS

The RAN5.0 supports STMA and complies with the AISG1.1 protocol.

The RAN6.1 supports STMA and complies with the AISG2.0 protocol.

Dependency


None.


None.


None.


None.



25.2 MRFD-210602 Remote Electrical Tilt

Availability


Summary

The feature provides a solution to remote adjustment of the antenna tilt. The user can adjust

the remote electrical tilt (RET) antenna tilt on the M2000 or LMT.

Benefits

This feature provides the following benefits:

The RET antennas in multiple sites can be remotely adjusted, thus the efficiency of

adjusting the antenna tilt is improved and the cost of network optimization is reduced.

The adjustment of the RET antenna is not affected by the weather.

It is easy to adjust the RET antenna of a site that is difficult to reach.

Description

The tilt of the RET antenna can be adjusted remotely.

After an antenna is installed, the antenna tilt needs to be adjusted to optimize the network.

The antenna tilt can be remotely adjusted through the electrical control.

The phase shifter of the antenna can be controlled by the stepper motor outside the antenna.

You can adjust the antenna tilt when the system is powered on and monitor the tilt in real time.

Therefore, the precise remote adjustment of the antenna tilt can be achieved.

The following figure shows the operating principle of the RET antenna.

Figure 25-1 Working principle of the RET antenna

RCU

Phase shifter

Pulling bar

Radome

Control cable

(DC+ control signals)



Remote Control Unit (RCU) is the driving motor of the phase shifter of the RET antenna. The

RCU receives and executes the control commands from the MBTS to drive the stepper motor.

A pulling bar connects the stepper motor and the phase shifter. When the stepper motor is

triggered, the pulling bar moves and then the phase of the phase shifter changes through the

gears. In this situation, the phase of each element of the array antenna changes regularly. Then,

the direction of the main beam of the antenna changes accordingly. Thus, the antenna tilt is

adjusted.

The MBTS supplies the DC power to the stepper motor and communicates with it through the

AISG interface on the motor.

In the Huawei RET solution, the RET antenna can be controlled remotely or locally through a

command sent from the M2000 or LMT.

The MBTS modulates that command to the On-Off-Keying (OOK) signals. The RF module

transfers the DC power and the OOK signals to the STMA or the SBT through the feeder

cables. The STMA or the SBT demodulates the OOK signals to RS485 signals and then sends

the RS485 signals and part of the DC power to the RCU. No additional control cable is

required.

The Huawei RET solution supports the RET cascading control. Several cascading RET

antennas can be controlled by the signals coming from the same control cable. The cascading

solution helps save the cost of the SBTs.

Ant enna

MBTS

RC

U SBT

Ant enna

RC

U

Sect or 1

Ant enna

RC

U

Sect or 2 Sect or 3

The Huawei RET solution supports the 2G/3G RET cascading control. The 3G RET antennas

can be cascaded with the 2G RET antennas. At the OMC of the 2G RET antenna, you can

control the tilt of the 3G RET antenna. Meanwhile, at the OMC of the 3G RET antenna, you

can control the tilt of the 2G RET antenna. The cascading helps save the cost of SBTs and

STMAs when the 2G and 3G RET antennas are installed in the same place.



3G/2G NodeB 2G/3G BTS

RC

U

SBT

Dual - band Ant enna

RC

U 2G 3G

Enhancement

GSM

None.

UMTS

In RAN6.0, the 3G RET cascading control and 2G/3G RET cascading control are

supported.

RAN6.1 complies with the AISG2.0 protocol.

Dependency


None.


1) BTS

This feature is supported by the all types of BTSs except for the BTS3600C and BTS3002E.

2) Node B

None.

3) MBTS

None.




None.


None.

25.3 WRFD-060003 Same Band Antenna Sharing Unit (900 MHz)

Availability


Summary

This feature enables UMTS900 and GSM900 to share the same band antenna. The description

of this feature focuses on the working principle and configuration of the SASU900.

Benefits

This feature helps to share the same band antenna and decrease the uplink division loss.

Compared with the traditional combiner and diplexer, it achieves3 dB gains.

Description

SASU900 can combine two same band signals into one with very low insertion loss when the

old system uses diversity antennas. Its basic guidance is as follows:

The downlink Tx signals in two different systems use two different antenna channels of one

dual-polarized antenna. One signal uses the main antenna and the other signal uses the

diversity antenna. Hence, there is less Tx insertion loss. In terms of the Rx signal, the Rx

signal of each antenna channel is separated into two paths. One signal is used as the main Rx

signal of the system, and the other signal is used as the diversity Rx signal of the other system.

Hence, the Rx splitter results in Rx insertion loss, which can be compensated by adding a

Lower Noise Amplifier (LNA).

The SASU900’s connection diagram in the system is as follows:



The configuration of the SASU900 in the GSM900 and UMTS900 co-site system

Note: We define the ANT_M as the main antenna port of the UMTS, and the ANT_D as the

diversity antenna port of the UMTS. In GSM, the ANT_D is the main antenna port and the

ANT_M is the diversity antenna port.

There is a limitation when using the SASU: The GSM uses only one antenna branch.

To allow GSM two antennas, the SASA (Same Band Antenna Sharing Adapter) is introduced.

The SASA is mainly used to combine two branches of GSM carriers into one antenna branch,

and keep the combination/division loss as low as possible. When sharing the antenna with

WCDMA, the GSM carriers prefer to be located separately as a “sandwich”.



Figure 25-2 SASA function block

The typical network diagram of sharing antenna is described as follows:

Enhancement

None.

BTS

GSM

BTS

GSM

SASASASA

NodeB

UMTS

NodeB

UMTS

SASU Note : All the bands is

shown as DL bands

DL Band

DL Band

DL Band

DL Band



Dependency

None.



26 Acronyms and Abbreviations

3G The Third Generation

AP Access Point

APM Advanced Power Module

AQM Active Queue Management

BBU Baseband Unit

BITS Building Integrated Timing Supply System

BTS Base Station

CBS Cell Broadcast Service

CPC Continuous Packet Connectivity

CPE Customer Premises Equipment

DNBS Distributed Node B System

DSAC Domain Specific Access Control

ETSI European Telecommunications Standards Institute

FTP File Transfer Protocol

GIS Geographical Information System

GA General Available

GBR Guaranteed Bit Rate

GLONASS GLObal Navigation Satellite System

GPS Global Position System

HCS hierarchical Cell Structure

HSDPA High Speed Downlink Packet Access

HSUPA High Speed Uplink Packet Access

LCS Location Service



LTE Long Term Evolution

MBMS Multimedia Broadcast Multicast Service

MIMO Multi-Input Multi-Output

NACC Network Assisted Cell Change

PA Power Amplifier

PARC Platform Advanced Radio Control

PPS Pulse Per Second

QAM Quadrature Amplitude Modulation

RAN Radio Access Network

RET Remote Electrical Antenna

RNC Radio Network Controller

ROHC Robust Header Compression

RRM Radio Resource Management

SAE System Architecture Evolution

SASA Same Band Antenna Sharing Adapter

SASU Same Band Antenna Sharing Unit

SNA Shared Network Area

TGW Transmission Gateway

VoIP Voice over IP

WCDMA Wideband Code Division Multiple Access

Documents

RAN12.0 Basic Feature Description V1.6(20100830)