Function Description of Huawei UMTS RAN10.0

Basic Function Description of
Huawei UMTS RAN10.0

Basic Function Description of Huawei UMTS RAN10.0
Huawei UMTS RAN

Basic Function Description
Document Version V1.7
Product Version RAN10.0
Huawei Technologies Co., Ltd. provides customers with comprehensive technical support
and service. Please feel free to contact our local office or company headquarters.
Huawei Technologies Co., Ltd.

Address: Administration Building, Huawei Technologies Co., Ltd.,
Bantian, Longgang District, Shenzhen, P. R. China
Postal Code: 518129
Website: http://www.huawei.com
第1章
Copyright © 2007 Huawei Technologies Co., Ltd.

All Rights Reserved.
No part of this manual may be reproduced or transmitted in any form or by any means without
prior written consent of Huawei Technologies Co., Ltd.
Trademarks
and other Huawei trademarks are the trademarks or registered trademarks of Huawei
Technologies Co., Ltd. in the People’s Republic of China and certain other countries.
All other trademarks and trade names mentioned in this document are the property of their
respective holders.
Notice
The information in this manual is subject to change without notice. Every effort has been made in
the preparation of this manual to ensure accuracy of the contents, but all statements, information,
and recommendations in this manual do not constitute the warranty of any kind, express or
implied.
第1章
Table of Contents
第1章 1 System Improvement Introduction.......................................................................1
第2章 1.1 WRFD-000001 System Improvement in RAN5.1..........................................1
第5章 1.4 WRFD-000004 System Improvement in RAN10.0........................................7
第6章 2 Standards Compliance........................................................................................ 10
第7章 2.1 WRFD-010101 3GPP R6 Specifications.....................................................10
第8章 2.2 WRFD-010102 Operating Multi-band..........................................................11
第9章 2.3 WRFD-010201 FDD Mode..........................................................................13
第10章 3 RABs and Services.......................................................................................... 14
第11章 3.1 WRFD-010510 3.4/13.6/27.2Kbps RRC Connection and Radio Access
Bearer Establishment and Release.......................................................................................... 14
第12章 3.2 WRFD-010501 Conversational QoS Class..............................................16
第13章 3.3 RFD-010502 Streaming QoS Class.........................................................18
第14章 3.4 WRFD-010503 Interactive QoS Class.....................................................20
第15章 3.5 WRFD-010504 Background QoS Class...................................................21
第16章 3.6 WRFD-010609 Multiple RAB Introduction Package (PS RAB < 2)..........22
第17章 3.6.1 WRFD-01060901 Combination of Two CS Services (Except for
Two AMR Speech Services)............................................................................................. 23
Commercial in Confidence i
第18章 3.6.2 WRFD-01060902 Combination of One CS Service and One PS
Service.............................................................................................................................. 24
第19章 3.6.3 WRFD-01060903 Combination of Two CS Services and One PS
Service (Except for Two AMR Speech Services)..............................................................25
第20章 3.7 WRFD-021104 Emergency Call...............................................................26
第21章 4 RAN Architecture & Functions........................................................................27
第22章 4.1 WRFD-010204 2-Antenna Receive Diversity...........................................27
第23章 4.2 WRFD-010205 Cell Digital Combination and Split...................................28
第24章 4.3 WRFD-010208 Fast Power Congestion Control (FCC)...........................30
第25章 4.4 WRFD-010211 Active TX Chain Gain Calibration....................................31
第26章 4.5 WRFD-021301 Shared Network Support in Connected Mode.................32
第27章 4.6 WRFD-010202 UE State in Connected Mode (CELL-DCH, CELL-PCH,
URA-PCH, CELL-FACH).......................................................................................................... 34
第28章 4.7 WRFD-010401 System Information Broadcasting...................................36
第29章 4.8 WRFD-010301 Paging UE in Idle, CELL_PCH, URA_PCH State (Type 1)
................................................................................................................................................. 38
第30章 4.9 WRFD-010302 Paging UE in CELL_FACH, CELL_DCH State (Type 2). 39
第31章 4.10 WRFD-020900 Logical Channel Management......................................40
第32章 4.11 WRFD-021000 Transport Channel Management..................................42
第33章 4.12 WRFD-022000 Physical Channel Management....................................43
第34章 4.13 WRFD-011401 Integrity Protection........................................................50
第35章 4.14 WRFD-011402 Encryption.....................................................................51
Commercial in Confidence ii
第36章 4.15 WRFD-020501 Open Loop Power Control.............................................52
第37章 4.16 WRFD-020502 Downlink Power Balance..............................................54
第38章 4.17 WRFD-020503 Outer loop Power Control..............................................55
第39章 4.18 WRFD-020504 Inner Loop Power Control.............................................56
第40章 4.19 WRFD-020101 Admission Control.........................................................57
第41章 4.20 WRFD-020102 Load Measurement.......................................................60
第42章 4.21 WRFD-020106 Load Reshuffling...........................................................62
第43章 4.22 WRFD-020107 Overload Control...........................................................64
第44章 4.23 WRFD-020108 Code Resource Management.......................................65
第45章 4.24 WRFD-021101 Dynamic Channel Configuration Control (DCCC).........66
第46章 4.25 WRFD-021201 RNC Resource Sharing.................................................68
第47章 4.26 WRFD-020201 Intra NodeB Softer Handover........................................69
第48章 4.27 WRFD-020202 Intra RNC Soft Handover..............................................71
第49章 4.28 WRFD-020203 Inter RNC Soft Handover..............................................72
第50章 4.29 WRFD-020301 Intra Frequency Hard Handover....................................73
第51章 4.30 WRFD-010801 Intra RNC Cell Update..................................................74
第52章 4.31 WRFD-010802 Inter RNC Cell Update..................................................76
第53章 4.32 WRFD-010901 Intra RNC URA Update.................................................77
第54章 4.33 WRFD-010902 Inter RNC URA Update.................................................78
第55章 4.34 WRFD-021400 Direct Signaling Connection Re-establishment (DSCR)
................................................................................................................................................. 79
Commercial in Confidence iii

第56章 5 Transmission.................................................................................................... 80
第57章 5.1 WRFD-050101 Star Topology..................................................................80
第58章 5.2 WRFD-050102 Chain Topology...............................................................81
第59章 5.3 WRFD-050103 Tree Topology.................................................................82
第60章 5.4 WRFD-050201 NodeB Clock...................................................................84
第61章 5.5 WRFD-050202 RNC Clock......................................................................86
第62章 5.6 WRFD-050301 ATM Transmission Introduction Package........................87
第63章 5.6.1 WRFD-05030101 ATM over E1T1 on Iub Interface.......................88
第64章 5.6.2 WRFD-05030102 ATM over Channelized STM-1/OC-3 on Iub
Interface............................................................................................................................ 89
第65章 5.6.3 WRFD-05030103 ATM over Non-channelized STM-1/OC-3c on
Iub/Iu/Iur Interface............................................................................................................. 90
第66章 5.6.4 WRFD-05030104 Dynamic AAL2 Connections on Iub/IuCS/Iur
Interface............................................................................................................................ 92
第67章 5.6.5 WRFD-05030105 Permanent AAL5 Connections for Control Plane
Traffic................................................................................................................................ 94
第68章 5.6.6 WRFD-05030106 Call Admission Based on Used AAL2 Path
Bandwidth......................................................................................................................... 95
第69章 5.6.7 WRFD-05030107 CBR, rt-VBR, nrt-VBR, UBR ATM QoS Classes
.......................................................................................................................................... 96
第70章 5.6.8 WRFD-05030110 F5.....................................................................97
第71章 5.7 WRFD-050304 IMA for E1T1 or Channelized STM-1/OC-3 on Iub
Interface................................................................................................................................... 98
第72章 5.8 WRFD-050305 UBR+ ATM QoS Class..................................................100
Commercial in Confidence iv
第73章 6 System Reliability........................................................................................... 101
第74章 6.1 WRFD-040100 Flow Control..................................................................101
第75章 6.2 WRFD-040201 System Redundancy.....................................................103
第76章 6.3 WRFD-040301 Operate System Security Management........................104
第77章 7 RAN Operation & Maintenance.....................................................................105
第78章 7.1 WRFD-030100 Performance Management............................................105
第79章 7.2 WRFD-030200 Fault Management........................................................107
第80章 7.3 WRFD-030300 Inventory management.................................................109
第81章 7.4 WRFD-030400 Configuration Management...........................................110
第82章 7.5 WRFD-030501 Security Management...................................................112
第83章 7.6 WRFD-030601 Interface Tracing...........................................................113
第84章 7.7 WRFD-030602 Call Tracing...................................................................114
第85章 7.8 WRFD-030701 RNC Software Management.........................................115
第86章 7.9 WRFD-030702 NodeB Software Management......................................116
第87章 7.10 WRFD-030703 NodeB Software USB Download.................................118
第88章 7.11 WRFD-031100 BOOTP.......................................................................119
第89章 7.12 WRFD-031101 DHCP..........................................................................120
第90章 7.13 WRFD-030800 License Management..................................................121
第91章 7.14 WRFD-030900 DBS Topology Maintenance.......................................123
第92章 7.15 WRFD-031000 Intelligently Out of Service..........................................124
Commercial in Confidence v
第93章 7.16 WRFD-031200 OCNS.........................................................................125
第94章 7.17 WRFD-031300 Documentation............................................................126
第95章 8 NodeB Antenna System Solution.................................................................128
第96章 8.1 WRFD-060001 Connection with TMA (Tower Mounted Amplifier).........128
第97章 8.2 WRFD-060002 Remote Electrical Tilt....................................................130
第98章 8.3 WRFD-060003 Same Band Antenna Sharing Unit (900 MHz)...............133
Commercial in Confidence vi
99 System Improvement Introduction
1.1 WRFD-000001 System Improvement in RAN5.1

Feature Number: WRFD-000001
Availability
This feature is available from RAN5.1.
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 as well as UEs. 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 are implemented since then. 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 NodeB. It will save the cost of the
transmission.
Support of new products and configurations
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. NodeB
 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
Commercial in Confidence Page 1 of 154

 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.
Support of high efficiency power amplifier
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 to
separately amplify the average part and the peak part of the input signal and then
combine both to get high efficiency.
The efficiency of Huawei DPD + Doherty PA is 33% and above.
For the NodeB 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. Thanks to the support of two carriers and high output power for one
RF module (MTRU or RRU), it is easy to 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
Benefits
The benefits of the system improvements include:
 Wider product range, including new products and configurations
 Further improvements regarding stability and robustness, thanks to improved
functions and algorithms.
 Improved performance, including higher capacity
 Usability enhancements, reducing operating costs


Availability
Description
important 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 Ⅴ (850 MHz) MTRU, 2 carriers 40 W
 D BTS3812E/AE supports Band VIII (900 MHz) MTRU, 2 carriers 40 W
 DBS3800 supports Band Ⅴ (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, an new outdoor macro Node B, improve 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. So it enjoys easy
and fast deployment and reducing the engineering cost.

Enhancement
None
Dependency
None
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


Availability
Description
important functions for RAN as well as UEs. 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
NodeB
 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 RRU3804 is four carriers and high output power remote radio unit, 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
 IP transmission on the Iu/Iur interface
IP transmission on the Iu/Iur interface is introduced in RAN6.1, which will
decrease the transport cost greatly compared with the ATM transport cost.
 Iu flex enhancement
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 following
chapters and Optional Function Description of Huawei UMTS RAN6.1.
Enhancement
None
Dependency
None
Benefits
 Wider product range, including new products and configurations
 The BSC6810 provides higher capacity and tighter structure.
 New features and enhancement.


Availability
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
NodeBs BTS3812E, BTS3812A, and BTS3812AE.
 The enhanced baseband optical interface (EBOI) card is used to support the
RRU connection to the macro NodeBs: BTS3812E, BTS3812A and BTS3812AE.
EBOI also supports HSUPA phase2 and more CEs. It can be co-configured with
all other boards in the macro NodeB.
 The enhanced uplink process (EULP) card is used to support the HSUPA
Phase2 and more CEs, used in the macro NodeBs: BTS3812, BTS3812A,
BTS3812E, and BTS3812AE. The EULP can be co-configured with other boards
in the macro NodeB.
 The extension base band card (EBBC) is used to support the HSUPA Phase2
and more CEs in distributed the NodeB BBU3806. The EBBC can support hot
plugging. With the BBU+EBBC, 6 cells can be supported.
 BTS3812E/AE supports WRFU (WCDMA radio frequency unit), a more compact
RF module, integrated the MTRU function and MAFU function. The WRFU
supports 80W maximum output power and 4 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)
The UMTS RAN10.0 introduces the new NodeB product portfolio based on new
hardware platform.
 Indoor baseband unit BBU3900.

 Indoor radio filter unit WRFU. The WRFU provides four carriers and 80-W
nominal output power. B It can support 1carrier to 4 carrier configurations. 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. It can support 1carrier to 4 carrier configurations.
Band 1 (2100 MHz) ，Band II (1900 MHz) ，Band IV (1700 MHz / DL 2100
MHz) and Band Ⅴ (850 MHz) RRU3804 will be released in RAN10.0
 Different combinations of the units and auxiliary devices compose the following
3900 series NodeBs： DBS3900/BTS3900/BTS3900A can support up to 24 cell
carriers. There can be configured as Omni directional, 2-sector, 3-sector and 6-
sector configurations. The BTS3900 supports a smooth capacity expansion from
1 x 1 to 6 x 4 or 3 x 8. The maximum capacity of the BTS3900 is up to UL 1536
CEs and DL 1536 CEs. The capacity can be expanded simply through additional
modules or license upgrade.
New features and enhancement

 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
Some 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
Benefits
 High output power amplifier for the macro NodeB extends the coverage and
capacity, saves the number of the sites, and gets better user experience.
 Higher throughput by supporting of the HSUPA Phase 2 helps to get faster UL
speed and the possibility of introducing more new applications.

2 Standards Compliance
2.1 WRFD-010101 3GPP R6 Specifications

Availability
Description
RAN2.0 is compliant with the 3GPP R4 and back compliant with the R99.
RAN3.0/5.0 is compliant with the 3GPP R5 and back compliant with the R99 and R4.
Huawei RAN6.0/6.1 is compliant with the 3GPP R6 2006-03+ CR and back compliant
with the R99, R4 and R5 simultaneously.
Huawei RAN10.0 is compliant with the 3GPP R6 2007-03 and back compliant with
the R99, R4 and R5 simultaneously.
Enhancement
RAN10.0 is compliant with the 3GPP R6 2007-03 and back compliant with the R99,
R4 and R5 simultaneously.
Dependency
For the features and IEs in the messages introduced in Release6, CN nodes and UE
are also required to be compliant with the specification if they are related.
Benefits
With compliance to release 6, the new features and enhancements introduced in this
version can be possibly supported.

2.2 WRFD-010102 Operating Multi-band

Availability
This feature is available from RAN 2.0.
Description
The following 3GPP defined UMTS frequency bands are supported.
UL Frequencies DL frequencies
Operating
UE transmit, NodeB UE receive, NodeB Availability
Band
receive transmit
I 1920 to 1980 MHz 2110 to 2170 MHz RAN2.0
Macro:RAN5.0
II 1850 to 1910 MHz 1930 to 1990 MHz
RRU: RAN5.1
Macro:RAN5.0
III 1710 to 1785 MHz 1805 to 1880 MHz
RRU: RAN5.1
V 824 to 849 MHz 869 to 894 MHz RAN6.0
VIII 880 to 915 MHz 925 to 960 MHz RAN6.0
IV 1710 to 1755 MHz 2110 to 2155 MHz RRU: RAN6.1
IX 1749.9 to 1784.9 MHz 1844.9 to 1879.9 MHz RRU: RAN6.0
The macro NodeBs provide multi-band co-located in one cabinet. Since the flexibility
design of Huawei NodeB architecture, the multi-band only impact on the RF system.
The baseband modules including power, transmission, channel cards are completely
shared by different bands. The operators can make use of the needed frequency
segments to save the footprint of the BTS and improve the baseband usage.
The feature is implemented in the NodeB and RNC.
Different frequency bands should be configured with different RF modules.
Enhancement
In RAN5.0, the macro NodeB supports the 1900 M and 1800 M frequency band.
In RAN5.1, the RRU supports the 1900 M and 1800 M frequency band.
In RAN6.0, the 850 M and 900 M frequency band is supported by the macro NodeB
and RRU.

In RAN6.1, the AWS (UL 1700 MHz / DL 2100 MHz) frequency band is supported by
the RRU.
BTS3900/BTS3900A only support Band1 2100M in RAN10.0.
Dependency
None
Benefits
The NodeBs can be deployed widely according to the operator’s frequency
requirement.
The multi-band supported NodeB can save the cost of the hardware investment.

2.3 WRFD-010201 FDD Mode

Availability
Description
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
Need related node elements to be compliant with the 3GPP specifications in FDD
mode.
Benefits
This feature defines the mode supported by Huawei RAN.

3 RABs and Services
3.1 WRFD-010510 3.4/13.6/27.2Kbps RRC Connection and

Radio Access Bearer Establishment and Release
Availability
This feature is available from RAN2.0;
This feature is introduced in 3GPP R99
Description
3.4/13.6/27.2Kbps RRC connection and Radio Access Bearer Establishment and
Release are supported to provide the services available. And the RNC will map these
RRC connection request and RAB assigned by CN to the corresponding radio
parameters according to their QoS requirements.
 Channel type mapping
For RRC connection, operators can configure which channel type (CCH/DCH)
should be used according to the cause in RRC setup REQUEST message.
For RAB connection, operators can configure which RAB should be set up on
DCH while others on CCH.
 RAB parameters mapping
As soon as the channel type is decided, the corresponding transport channel
and physical channel parameters will be allocated. Huawei RAN has a set of
such parameters for each supported typical service. If no matching service is
found, the nearest RAB parameters will be used. Moreover, operators can add
new services with new sets of parameters configured. These features can
maximize the service support capability of the system.
PS streaming/interactive/background RAB can also be set up on HS-DSCH or E-
DCH, such features belong to the optional feature WRFD-010610 HSDPA
Introduction Package, WRFD-010612 HSUPA Introduction Package, WRFD-
010630 Streaming Traffic Class on HSDPA and WRFD-010632 Streaming Traffic
Class on HSUPA.
Enhancement
In RAN3.0, 13.6Kbps RRC connection is supported.
In RAN6.1, 27.2Kbps RRC connection is supported.

Dependency
UE should support the rates at the same time
Benefits
This feature is the base of service support.

3.2 WRFD-010501 Conversational QoS Class

Availability
Description
QoS classes also refer to traffic classes. There are four different QoS classes defined
in 3GPP:
 Conversational class;
 Streaming class;
 Interactive class;
 Background class.
The main difference between these QoS classes is how delay sensitive the traffic is.
Conversational class is meant for traffic which is very delay sensitive and mainly used
to carry real time traffic flows. Fundamental characteristics for Real time
conversational QoS class include:
 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 domain. 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:
1. 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 will select SF256
for AMRS services whose maximum rate is not higher than 7.95 kbit/s.
2. CS transparent data services (conversational class) with 64 kbit/s, 56 kbit/s, 32
kbit/s and 28.8 kbit/s.
3. 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
CN Node and UE should support the services at the same time.
Benefits

Conversational QoS class support capability can provide upper layer corresponding
services with QoS guaranteed.

3.3 RFD-010502 Streaming QoS Class

Availability
This feature is introduced in 3GPP R99.
Description
QoS classes also refer to traffic classes. There are four different QoS classes:
Streaming class is one of the newcomers in data communication, raising a number of
new requirements in both telecommunication and data communication systems. It is
characterized by that the time relations (variation) between information entities (i.e.
samples, packets) of the stream should be preserved, although it does not have any
requirements on low transfer delay. Fundamental characteristics for streaming QoS
class include:
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:
1. CS transparent data services (streaming class) of 64 kbit/s.
2. CS nontransparent data services of 57.6 kbit/s, 28.8 kbit/s, and 14.4 kbit/s.
3. 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.
4. 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, and 0 kbit/s.
PS streaming service can also be carried on HSDPA/HSUPA which is the optional
features and described in WRFD-010610 HSDPA Service and WRFD-010612 HSUPA
Service.
Enhancement
In RAN6.0, PS 384 kbit/s bidirectional symmetric or asymmetric streaming service is
supported.

Dependency
Benefits
Streaming QoS class support capability can provide upper layer corresponding

3.4 WRFD-010503 Interactive QoS Class

Availability
Description
Interactive class is another typical data communication scheme that on an overall
level 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 content of the packets shall be transparently transferred (with
low bit error rate). Fundamental characteristics for Interactive QoS class include:
 Request response pattern.
 Preserve payload content.
There are interactive class services in PS domain while no application service in CS
domain is obviously needed. The most well known interactive traffic is web browsing.
Huawei RAN supports the following interactive services as fundamental features:
1. 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, and 8 kbit/s.
The higher rates can only be supported on HSDPA/HSUPA which are optional
Service
Enhancement
In RAN3.0, PS UL 384 kbit/s service is supported.
Dependency
Benefits

Interactive QoS class support capability can provides upper layer corresponding

3.5 WRFD-010504 Background QoS Class

Availability
Description
第100章 The main difference between these QoS classes is how delay
sensitive the traffic is. Background class is one of the typical data communication
schemes. It is characterized by that the destination is not expecting the data within a
certain time. The scheme is thus more or less delivery time insensitive. Another
characteristic is that the content of the packets shall be transparently transferred (with
low bit error rate). Fundamental characteristics for background QoS class include:
 The destination is not expecting the data within a certain time;
 Preserved payload content;
There are background class services in PS domain while no application service in CS
domain is obviously needed. 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, and 8 kbit/s.
The higher rates can only be supported on HSDPA/HSUPA which are optional
Service
Enhancement
In RAN3.0, PS UL 384 kbit/s service is supported.
Dependency

Benefits
Background QoS class provides upper layer corresponding services with QoS
guaranteed.

3.6 WRFD-010609 Multiple RAB Introduction Package (PS

RAB < 2)
Availability
Description
Multi-RAB can provide more abundant services simultaneously to the upper layer. In
the case of multi-RAB with the number of PS RAB less than two, 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 combination above, 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; such features will be supported in the optional
features WRFD-010610 HSDPA Introduction Package and WRFD-010612 HSUPA
Introduction Package.
Enhancement
None
Dependency
CN node and UE must have the corresponding multi-RAB support capability.
Benefits
Multi-RAB support capability provides operators with more service solution choices.

3.6.1 WRFD-01060901 Combination of Two CS Services (Except for Two

AMR Speech Services)

Availability
Description
Huawei supports combination of two CS services (except for two AMR speech
services).
Enhancement
None
Dependency
Benefits

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

Availability
Description
Huawei supports one CS service + one PS service.
Enhancement
None
Dependency
Benefits

3.6.3 WRFD-01060903 Combination of Two CS Services and One PS Service

(Except for Two AMR Speech Services)

Availability
Description
Huawei supports two CS services + one PS service (except for two AMR speech
services).
Enhancement
None
Dependency
Benefits

3.7 WRFD-021104 Emergency Call

Availability
Description
When 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 there is no enough
resources in the cell, pre-emption action to ordinary calls with lowest priority will be
triggered to guarantee that the emergency call have access to the network and be
served.
Enhancement
None
Dependency
None
Benefits
It is an essential feature for UMTS RAN.

4 RAN Architecture & Functions
4.1 WRFD-010204 2-Antenna Receive Diversity

Availability
Description
Receiving diversity refers to a technique of monitoring multiple frequencies from the
same signal source, or multiple radios and antennas monitoring the same frequency,
in order to combat signal fade and interference.
Receive diversity is one way to enhance the reception of uplink channels.
Huawei NodeBs support both RX diversity and no RX diversity.
In RX diversity mode, the NodeB does not require additional devices and works with
the same algorithms. Compared with 1-way no RX diversity, 2-way RX diversity
requires twice the number of RX channels. The number of RX channels depends on
the settings of the antenna connectors on the cabinet top.
Enhancement
None
Dependency
RX diversity requires the NodeB to provide enough RF channels and demodulation
resources that can match the number of diversity antennas. It has no special
requirements for RNC or UE.
Benefits
It can improve receiver sensitivity and uplink coverage, so that the CAPEX is
reduced.

4.2 WRFD-010205 Cell Digital Combination and Split

Availability
Description
In the indoor coverage, different antenna in different area should transmit and receive
one cell signal which is called cell split. DBS3800 and iDBS3800 support cell digital
combination and split.
The following figure shows the logical structure for cell digital combination and split.
The downlink digital signal can be driven into two RRUs, one is for this level RRU Tx
Path, and one is for lower level RRU. For uplink, this level RRU digital signal can be
combined with the lower level RRU signal and send to the upper level RRU or
baseband unit.
Upper level RRU or BB
Slave RRU
CPRI
Interface Split RF Tx Path Du
ple
xer
Combined RF Rx Path
Uplink
CPRI
Interface
Master
lower level RRU
Each RRU or Pico RRU has an independent antenna and it can cover different areas,
but several RRU digital signals can be combined to one cell in uplink and one cell
signal can replicated to several RRU in RHUB, Pico RRU or macro RRU . It has same
scramble code.
Huawei introduces this feature to the Pico RRU and RRU, which is assigned to indoor
coverage.
Enhancement
None

Dependency
None
Benefits
Cell digital combination and split will not bring additional noises and signal losses
compared with the analog combination and split. It can provide larger capacity and
wider coverage.

4.3 WRFD-010208 Fast Power Congestion Control (FCC)

Availability
Description
Fast power congestion control (FCC) is a NodeB 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 the
fast power congestion control in the NodeB, in order to limit the output power and
avoid the PA saturation. The ALC supervise the signal strength to the PA. When it
reaches to the threshold, the ALC can increase the TX channel attenuated signals to
keep the output power lower than the threshold to avoid the PA saturation.
The NodeB uses the FCC to fast 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. Furthermore, 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
Benefits
This feature enables full utilization of Power Amplifiers for traffic load especially for
dynamic power sharing in one carrier between R99 and HSDPA. .

4.4 WRFD-010211 Active TX Chain Gain Calibration

Availability
Description
The active TX chain gain calibration increases the RF output power accuracy, reduce
margins required in network dimensioning, all power can be used for traffic.
All radio HW has a natural spread in characteristics. RF components such as TRX,
MCPA, cables connector and filters have a spread in gain over time, temperature and
individual variations. This spread in gain will add up on system level and can result in
variations of output power of 1.5-2 dB on NodeB level.
The active TX chain gain calibration compensates for these variations and maintains
a high accuracy during all conditions. The actual transmitted power is measured and
the level is compared with the digital input signal. Based on these values the gain in
the TX chain is calibrated by a SW algorithm. This calibration is done constant during
traffic，compensates for temperature drift, subsystem gain spread and time to
guarantee the accuracy of the output power.
This feature enables an output power accuracy of +/- 0.6 dB for BTS3900 and
reduces needed cell planning margins to a minimum. All available power can be used
for traffic.
Enhancement
None
Dependence
None
Benefits
This feature provides high output power accuracy for the NodeB, and reduces the
margins required in network dimensioning; all power can be used for traffic.

4.5 WRFD-021301 Shared Network Support in Connected

Mode
Availability
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
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) while 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 or not 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 to 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 or not 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 or not 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 mode must support this feature at the same time and when it is related to Iur
interface, the RNC connected to should also support the feature.
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.

4.6 WRFD-010202 UE State in Connected Mode (CELL-

DCH, CELL-PCH, URA-PCH, CELL-FACH)
Availability
Description
In 3GPP, there are four RRC connected states for UE including URA_PCH,
CELL_PCH, CELL_FACH and CELL_DCH. Huawei RAN supports all these 4 states.
URA_PCH/CELL_PCH: In these states, UE has neither DCCH nor DTCH available.
When UE originates a call or receives paging from CN, CELL_UPDATE procedure
will be triggered. Periodically URA UPDATE or CELL_UPDATE procedure can also be
used to keep the connection with the network. Since no DTCH or DCCH is allocated,
UE in these states nearly occupies no radio resources, thus no service is available as
a result.
CELL_FACH: In this state, UE has DCCH and DTCH mapping to the common
channels which are used to bear RRC signaling and traffic data. UE also performs
cell reselection with Cell Update procedure to camp on a proper cell. Since the
common resources can be shared among different UEs, the traffic QoS such as
transfer delay, bandwidth can not be guaranteed.
CELL_DCH: In this state, UE has DCCH and DTCH mapping to the dedicated
channels which are used to bear RRC signaling and traffic data. Since the dedicated
resources are allocated, the traffic QoS can be guaranteed while the cell load is
increased accordingly. When UE is using HSDPA and/or HSUPA, it also belongs to
CELL_DCH state.
These four states can be transformed according to the UE service characteristics and
behaviors, such procedures are channel type transition. For details, please refer to
the feature WRFD-021101 Dynamic Channel Configuration Function (DCCC).
For the channel transition between CELL_DCH (HS-DSCH) and other states, please
refer to the optional feature WRFD-01061111 HSDPA State Transition.
Enhancement
In RAN2.0, the basic four states and transition algorithms are implemented.
In RAN5.0, with the deployment of HSDPA feature, UE in CELL_DCH (HS-DSCH)
state is also supported.

In RAN 6.0 with the deployment of HSUPA feature, UE in CELL_DCH (E-DCH) state
is also supported.
Dependency
UE should support the states.
Benefits
This feature makes it possible to put UE in the proper state according to the QoS
requirements. Thus, it improves the resources usage efficiency and increases the
system capacity without obvious user experience degradation. It is an essential
feature for UMTS RAN system.

4.7 WRFD-010401 System Information Broadcasting

Availability
Description
System information broadcasting which is needed 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 as a tree-type. 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 table below.
System
Area
Information Content
Scope
Block
Master information
Cell SIB scheduling information
block
Scheduling block
1
Scheduling block
2
NAS information and timers used by UE in

SIB1 PLMN
connected mode and idle mode
SIB2 Cell URA Id
Parameters of cell selection and reselection in

SIB3 Cell idle mode
Parameters of hierarchical cell in idle mode

System
Area
Information Content
Scope
Block
Parameters of cell selection and reselection in

connected mode
SIB4 Cell
Parameters of Hierarchical cell in connected
mode (CCH state)
Parameters of common physical channels for

SIB5 Cell UE in idle mode(PRACH, AICH, PICH, S-
CCPCH)
Parameters of common physical channel in

SIB6 Cell
connected mode
SIB7 Cell UL interference, dynamical persistence level
SIB11 Cell Measurement control information in idle mode
Measurement control information in connected

SIB12 Cell
mode
SIB18 Cell PLMN ID of neighboring cells
Enhancement
In RAN5.0, SIB 4, SIB 6, and SIB 12 are supported.
Dependency
None
Benefits
This feature provides UE access layer and non access layer with information which
UE needs and controls UE behavior in the network.

4.8 WRFD-010301 Paging UE in Idle, CELL_PCH, URA_PCH

State (Type 1)
Availability
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 paging control channel (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.
Benefits
The network can control the UE in idle mode, CELL_PCH or URA_PCH state which
has no Dedicated Control Channel (DCCH) with paging type 1 procedure.

4.9 WRFD-010302 Paging UE in CELL_FACH, CELL_DCH

State (Type 2)
Availability
Description
Paging type 2 procedure is used to transmit paging information to selected UEs in
CELL_DCH or CELL_FACH state, and the paging type 2 will be transferred on
DCCH.
Enhancement
None
Dependency
None.
Benefits
The network can control the UE in CELL_FACH or CELL_DCH state which has
dedicated control channel (DCCH) with paging type 2 procedure.

4.10 WRFD-020900 Logical Channel Management

Availability
Description
A set of logical channel types are defined for different kinds of data transfer services
as offered by MAC. Each logical channel type is defined by what type of information is
transferred. A general classification of logical channels is into 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 including:
 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 including:
 Dedicated Traffic Channel (DTCH)
 Common Traffic Channel (CTCH)
Mapping between logical channels and transport channels is as below
I. In Uplink,
 CCCH can be mapped to RACH;
 DCCH can be mapped to RACH;
 DCCH can be mapped to 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;
The mapping between DTCH 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, CTCH supported with cell broad service (CBS) feature is introduced.
Dependency
None.
Benefits
This feature provides the base of data transfer and resource management algorithm.

4.11 WRFD-021000 Transport Channel Management

Availability
Description
Transport channel is used to offer information transfer services to MAC and higher
layers.
A general classification of transport channels is into two groups:
 Common transport channels
 Dedicated transport channels
Common transport channel types are:
 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:
 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
To support the HSDPA transport channels, the HSDPA supported downlink process
board (HBBI or HDLP) should be added in the NodeB and the optional feature
WRFD-010610 HSDPA Service must be selected.
To support the HSUPA transport channels, the optional feature WRFD-010612
HSUPA Service must be selected.
Benefits
This feature provides the base of data transfer and resource management algorithm.

4.12 WRFD-022000 Physical Channel Management

Availability
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 NodeB is given in the
tables below. The characteristics of these supported physical channels are compliant
with 3GPP TS25.211. Physical channels are carried on the radio interface only in the
NodeB of the UTRAN, but are managed by the RNC.

Channel Availability Direction Characteristics
PRACH is used to carry the RACH

which carries random access
PRACH
information of the UE accessing the
Physical UL network.
Random RAN2.0
Common It consists of one or several preambles
Access
of length 4096 chips and a message of
Channel
length 10 ms or 20 ms. The spreading
factor may range from 256 down to 32.
Uplink
The uplink DPDCH is used to carry the
DPDCH
DCH transport channel. There may be
Uplink UL zero, one, or several uplink DPDCHs on
Dedicated RAN2.0
Dedicated each radio link.
Physical
The spreading factor may range from
Data
256 down to 4.
Channel
The uplink DPCCH is used to carry

Uplink control information generated at Layer
DPCCH 1. The Layer 1 control information
Uplink consists of TFCI, TPC, Pilot bits, FBI,
UL
Dedicated RAN2.0 which is required to convey DPDCH.
Dedicated There is one and only one uplink
Physical
Control DPCCH on each radio link.
Channel Generally, the spreading factor is equal
to 256.
The Primary CCPCH is a fixed rate (30

P-CCPCH kbps, SF=256) downlink physical
Primary channel used to carry the BCH transport
Common DL channel which provides system and cell
RAN2.0
Control Common specific information.
Physical It is not transmitted during first 256
Channel chips of each slot since time multiplexed
with SCH.

The Secondary CCPCH is used to carry

S-CCPCH
the FACH and PCH. The FACH and
Secondary PCH can be mapped to the same or
Common DL
RAN2.0 separate Secondary CCPCHs.
Control Common
The spreading factor range is from 256
Physical
down to 4. It has no inner-loop power
Channel
control and is not always transmitted.
The P-SCH is used for cell search

P-SCH
procedure (Slot synchronization).
Primary DL
RAN2.0 This channel has no scrambled or
Synchroniza Common
OVSF coded. It is time multiplexed with
tion Channel
P-CCPCH.
S-SCH The S-SCH is used for cell search

Secondary DL procedure (SC group identification).
RAN2.0
Synchroniza Common Not scrambled nor OVSF coded. Time
tion Channel multiplexed with P-CCPCH.
The CPICH is a fixed rate (30 kbps,

SF=256) downlink physical channel that
carries a pre-defined bit sequence.
P-CPICH The Primary CPICH is the phase
Primary reference for the following downlink
DL
Common RAN2.0 channels: SCH, Primary CCPCH,
Common
Pilot Second CCPCH, AICH, PICH and
Channel DPCH.
There is one and only one P-CPICH per
cell. It is always scrambled by the
Primary SC.
The PICH is a fixed rate (SF=256)

physical channel used to carry the
PICH paging indicators. The PICH is always
Page DL associated with an S-CCPCH (mapped
RAN2.0
Indication Common with PCH) to carry the Paging Indicators
Channel (PI) informing the UE that paging
information is available on the
SCCPCH.

The AICH is a fixed rate (SF=256)

physical channel used to carry
AICH
Acquisition Indicators (AI). Acquisition
Acquisition DL
RAN2.0 Indicators corresponding to signatures
Indicator Common
on the PRACH are used by the network
Channel
to confirm to the UE the reception of its
access (PRACH).
The downlink DPCH can be seen as a

time multiplex of a downlink DPDCH
Downlink and a downlink DPCCH. It carries
DPCH dedicated data generated at Layer 2
Downlink DL and above (i.e. the dedicated transport
RAN2.0
Dedicated Dedicated channel DCH), with control information
Physical generated at Layer 1 (pilot bits, TPC
Channel commands, and TFCI).
The spreading factor may range from
512 down to 4.
HS-DPCCH The HS-DPCCH carries uplink feedback

Dedicated signaling related to downlink HS-DSCH
Physical UL transmission. It consists of HARQ-ACK
RAN5.0
Control Dedicated and CQI.
Channel for The spreading factor of the HS-DPCCH
HS-DSCH is 256

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
HS-SCCH in timing and keeps fixed time offset
Shared with the HS-PDSCH. Its spreading
DL
Control RAN5.0 factor is fixed as 128 and QPSK is the
Common
Channel for only modulation mode.
HS-DSCH The number of HS-SCCHs and the
channel codes in the cell are
determined by the RNC, and are
notified to the NodeB through the NBAP
signaling message. When the NodeB
sends the data to the UE through the
HS-PDSCH, the UE can detect one to
four HS-SCCHs that are specified by
the NodeB at one time.
The HS- PDSCH is used to carry HS-

DSCH.
A HS-PDSCH corresponds to one
channelization code of fixed spreading
HS-PDSCH factor SF16 from a set of channelization
High Speed codes reserved for HS-DSCH
Physical DL transmission. Multi-code transmission
RAN5.0
Downlink Common is allowed, which means in one HS-
Shared PDSCH sub-frame multiple
Channel channelization codes could be used for
one UE. It depends on UE’s capability
also.
The HS-PDSCH adopts the QPSK or
16QAM modulation mode.

The E-DPDCH is used to carry the E-

DCH transport channel. There may be
E-DPDCH zero, one, or several E-DPDCHs on
each radio link.
E-DCH
UL Its spreading factor set is {SF256,
Dedicated RAN6.0
Physical Dedicated SF128, SF64, SF32, SF16, SF8, SF4,
Data 2×SF4, 2×SF2 and 2×SF2+2×SF4}. In
Channel RAN 6.0, spreading factor set {SF256,
SF128, SF64, SF32, SF16, SF8, SF4,
2×SF4,} can be supported.
E-DPCCH The E-DPCCH is a physical channel

E-DCH used to transmit control information
Dedicated UL associated with the E-DCH. There is at
RAN6.0
Physical Dedicated most one E-DPCCH on each radio link.
Control The spreading factor is always equal to
Channel 256.
E-AGCH is a common downlink

physical channel, which carries the
maximum power ratio of E-
DPDCH/DPCCH that can be allowed to
E-AGCH use by the UE, it is only sent from the
E–DCH serving cell that the serving radio link of
DL
Absolute RAN6.0 the UE belongs to. An E-AGCH is
Common shared by many users in time
Grant
Channel 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 is a dedicated downlink

physical channel, which carries the
relative grant value for modifying power
ratio of E-DPDCH/DPCCH, it is used to
frequently adjust the UE uplink transmit
E-RGCH
power, which could happen per 2ms
E-DCH DL TTI.
Relative RAN6.0
Dedicated E-RGCH and E-HICH of a user shares
Grant
the same channel code with spreading
Channel
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 is a dedicated downlink

E-HICH physical channel, which carries the E-
E-DCH DCH hybrid ARQ acknowledgement
DL
Hybrid ARQ RAN6.0 indicator such as ACK/NACK, the
Dedicated
Indicator acknowledgement indicator informs UE
Channel whether the data for a user process is
received correctly or not in the NodeB.
The MBMS Indicator Channel (MICH) is

a fixed rate (SF=256) physical channel
DL used to carry the MBMS notification
MICH RAN6.0
Common indicators. The MICH is always
associated with an S-CCPCH to which a
FACH transport channel is mapped.
F-DPCH is a shared channel which only

carries the UE specific TPC bits, so the
A-DCH can be replaced by shared
F-DPCH RAN10.0 channel to save the code and power
resource.
Replacing A-DPCH with F-DPCH will
boost the capacity for VoIP traffic in DL.

The following figure summarizes the mapping of transport channels onto physical
channels.
Transport Channels Physical Channels
DCH Dedicated Physical Data Channel (DPDCH)

Dedicated Physical Control Channel (DPCCH)
Fractional Dedicated Physical Channel (F-DPCH)
E-DCH 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)
RACH Physical Random Access Channel (PRACH)
Common Pilot Channel (CPICH)

BCH Primary Common Control Physical Channel (P-CCPCH)
FACH Secondary Common Control Physical Channel (S-CCPCH)
PCH
Synchronisation Channel (SCH)
Acquisition Indicator Channel (AICH)
Paging Indicator Channel (PICH)
MBMS Notification Indicator Channel (MICH)
HS-DSCH 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)
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
To support HSDPA physical channels, the HSDPA enabled downlink process board
(HBBI or HDLP) should be added in the NodeB and the optional feature WRFD-
010610 HSDPA Service must be selected.
To support HSUPA physical channels, the optional feature WRFD-010612 HSUPA
Service must be selected.
To support F-DPCH, the macro NodeB BTS3812E or BTS3812AE needs to add EBBI
or EBOI, and the distributed NodeB BBU3806 needs to add the EBBC.
Benefits
With F-DPCH, more VoIP users can be supported.

4.13 WRFD-011401 Integrity Protection

Availability
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 illegally
changed. 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
Benefits
The procedure enhances network and user data security, and protects the data and
networks from illegal interception and modifying.

4.14 WRFD-011402 Encryption

Availability
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.
Benefits
The procedure enhances network and user data security and protects the data and
networks from illegal interception and modifying.

4.15 WRFD-020501 Open Loop Power Control

Availability
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, then to
provide a proper initial power used by the UE and the NodeB.
Open-loop power control is applied on the uplink PRACH and DPCH as well as the
downlink DPCH. The other downlink common channel’s initial power is set fixed by
the network.
For the PRACH, firstly, UE will calculate the initial PRACH preambles transmit power
by estimation of downlink path loss, and other necessary information like UL
inferences by the cell system broadcasting. The following ramping rule is also
controlled by the network through parameters setting in broadcasting information. As
soon as the positive acquisition indicator is received on AICH, the transmit power of
PRACH message control part can be certain with the power offset to the last
transmitted preamble. Meanwhile, the transmit power of data part can be calculated
by gain factors for control and data part.
For the uplink DPCCH transmission, initial power is calculated in the same way as
PRACH, except the power offset is different which provided by RRC messages.
Moreover, uplink DPDCH transmit power can be calculated with the gain factors
signaled by the network.
For 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 need an initial power on
the new added radio link.
- RRC connection setup
- Radio link addition in soft handover
- Hard handover
- Relocation
- Channel type switching

Enhancement
None
Dependency
None
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.

4.16 WRFD-020502 Downlink Power Balance

Availability
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 new added
RL and existing one may lead to the drifting of transmit power. The more DL transmit
power drifting is, the less macro-diversity gain is.
Downlink power balance is used to correct the transmit power drifting in such
scenarios and improve soft handover performance accordingly.
In the downlink, the NodeB will calculate the transmit power with considering TPC
commands sent by UE as well as the reference power set by the network. When the
drifting of transmit power is too much, the network will update the reference power to
decrease the power difference of different RLs.
Enhancement
None
Dependency
None
Benefits
Downlink power balance can decrease the transmit power drifting of different RLs and
improve soft handover performance accordingly.

4.17 WRFD-020503 Outer loop Power Control

Availability
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 control acts
on each DCH belonging to the same RRC connection.
Outer loop power control comprises downlink and uplink outer loop power control. For
the downlink, it is to maintain the proper SIR target used in downlink inner loop power
control and the algorithm depends on UE implementation, the downlink BLER
requirements of each RB was signaled by the network for UE to consider. For the
uplink, it is to maintain the proper SIR target used in uplink inner power control and
set by the network.
For the uplink outer loop power control, the SRNC gets the uplink quality after macro
diversity selection combining firstly, 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. When BLER is not available, BER will be
used instead. After adjusting the SIR target, the SRNC sends the new SIR target
through FP frames to all NodeBs for uplink inner loop power control.
The initial SIR target provided by the RNC to the NodeB is service-dependent and it
will be updated by the uplink quality measurement of each DCH in the following
phases.
Enhancement
None
Dependency
None
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.

4.18 WRFD-020504 Inner Loop Power Control

Availability
Description
Inner loop power control is also called fast closed-loop power control and only applied
to the dedicate channel. It controls the transmit power according to the information
returned from the peer physical layer. The UE and the NodeB 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 and downlink inner-loop power control, and
they work individually.
The uplink inner-loop power control is used to adjust the UE transmit power by
receiving TPC commands from the NodeB. There are fast and slow power control
algorithm (PCA) defined by 3GPP protocol. The PCA1 is the fast power control in
which the UE adjusts the power in one slot and the PCA2 is the slow power control in
which the UE adjusts every 5 slots. It lowers the power control frequency from 1500
times/s to 300 times/s maximally. The operators decide which PCA will be chosen in
the RRC messages.
The downlink inner-loop power control is used to adjust the NodeB transmit power by
receiving TPC commands from UE. There are two downlink power control (DPC)
modes which also control the downlink power adjust frequency. That is, the UE sends
the TPC command every slot in the DPC mode 0 while sending the same TPC
command in 3 slots in the DPC mode 1. The operators decide which DPC mode will
be used by RRC signaling.
Enhancement
None
Dependency
None.
Benefits
Inner loop power control adjusts the uplink and downlink power to the minimum while
ensuring the QoS, thus increases system capacity. It can also be used to prevent
shadow fading and fast fading.

4.19 WRFD-020101 Admission Control

Availability
Description
Admission control is used to improve the resource usage efficiency and RRC/RAB
setup success rate. The following 4 types of resources will be admitted:
 Cell available code resource
 Cell available power resource
 NodeB resource state, that is, NodeB 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
Based on the current cell load (uplink load factor and downlink TCP) and the
access request, the RNC decides whether the cell load will exceed the threshold
or not if admitting a new call. If yes, the RNC rejects the request. If no, the RNC
accepts the request.
 Algorithm 2
Power resource admission decision based on the equivalent number of users.
Based on the current equivalent number of users and the access request, the
RNC decides whether the equivalent number of users will exceed the threshold
or not if admitting a new call. If yes, the RNC rejects the request. If no, the RNC
accepts the request.
 Algorithm 3
It is similar to algorithm 1, but the prediction of needed power of a new call will
be set to zero.

Four basic load thresholds are used for admission decision. They are:
 Handover admission threshold
 AMR conversational service admission threshold
 Non AMR conversational service admission threshold
 Other service admission threshold
With these thresholds, the RNC can define the proportion between speech service
and other services while ensuring handover preference.
III. NodeB credit
The NodeB credit admission includes the following:
 Local cell level admission decision
 Local cell group level admission decision (if any)
 NodeB level admission decision
Services can access the network only after all admission decisions are passed
For details about local cell, local cell group, and capacity consumption law, please
refer to the 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 from
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.
For HSDPA/HSUPA, the admission control also applies. 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 added.
In RAN6.0, resource reserved for handover is supported to decrease the call failure
due to the admission failure during the handover.
Dependency
None
Benefits
This feature maximizes system capacity while ensuring QoS requirements, and
improves the stability of the network.

4.20 WRFD-020102 Load Measurement

Availability
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 in order
to get rippling and timely common measurement as required.
The major related measurement quantities are defined in 3GPP TS25.433 as below:
 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 measurements above focus on radio power load. For other resource load, the
related measurements include:
 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

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 configure
load measurement parameters like measurement period, hysteresis, and so on.

4.21 WRFD-020106 Load Reshuffling

Availability
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 needed 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
 NodeB credit resource
 Equivalent user number
The Iub resource and credit resource congestion control in both uplink and downlink
is NodeB 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 above, 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, uplink load reshuffling triggered by power resource can be applied in a
HSUPA cell. In addition, a switch is provided to control whether gold user could be
selected during the load reshuffling.
Dependency
None
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.

4.22 WRFD-020107 Overload Control

Availability
Description
The function of OLC is to reduce the cell load rapidly by restricting the transport
format (TF) of the BE service or releasing UEs when the cell is overloaded. The
purpose of OLC is to ensure the stability of the system and the QoS of most UEs.
Overload control is only aimed at radio power overload scenario.
Enhancement
In RAN5.0, priority based overload control is supported.
Dependency
None
Benefits
This feature decreases cell load when the cell resources enter the overload state
rapidly and ensures the system stability.

4.23 WRFD-020108 Code Resource Management

Availability
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, “left most” algorithm is adopted in code
allocation procedure, that is, the code with minimum SF will be reserved to keep the
continuously codes left.
When the assigned AMR speech bit rate is less than 7.95 Kbit/s, the allocated SF will
be 256 instead of 128 so as 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 the RNC found the maximum
supported bit rate is less than the threshold configured from the view of code, the
code re-allocation action will be implemented to adjust the code use in the code tree
and reduce the code fragment as much as possible.
Enhancement
In RAN6.0, allocation of code with SF 256 when the assigned AMR speech bit rate is
less than 7.95Kbps is supported.
In RAN6.0, code re-allocation algorithm is introduced as one of the load reshuffling
strategies triggered by code congestion.
Dependency
None
Benefits
The code management algorithm can improve code usage efficiency, and optimize
the code allocation when too much code fragments founded.

4.24 WRFD-021101 Dynamic Channel Configuration

Control (DCCC)
Availability
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
by 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, code
resource and Iub transmission load. The congestion thresholds are independent and
configurable. This feature is a strategy of WRFD-020106 Load Reshuffling.
IV. Throughput based
According to the throughput, rate re-allocation can adjust the uplink/downlink data
rate during the call period, to use system resources in more efficient way.
 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 NodeB). For details, please refer to
optional features WRFD-01061111 HSDPA State Transition and WRFD-01061208
HSUPA DCCC.
Enhancement
In RAN3.0, the Iub transmission load based DCCC is supported.
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
Benefits
This feature can improve the efficiency of radio resource allocation and keep the
stability of radio link.

4.25 WRFD-021201 RNC Resource Sharing

Availability
Description
The RNC resource sharing provided by BSC6810 includes user plane resource
sharing and control plane resource sharing.
Control plane resource sharing is applied to CPU load and memory, etc. When the
CPU or memory of certain signaling process unit is overloaded, the new call can be
shared by other signaling process unit with lower load.
User plane resources are shared dynamically within the RNC system based on
resource pool and load sharing. If certain user plane process unit is overloaded, the
new traffic can be allocated to other user plane process unit with lower load.
Control plane capacity and user plane capacity can be configured independently.
Enhancement
None
Dependency
None
Benefits
The RNC resource sharing can improve the resource usage efficiency and increase
call success rate. It can also use the installed SW/HW capacity up to the maximum
contracted limit with the minimum service outage under variable traffic modes.

4.26 WRFD-020201 Intra NodeB Softer Handover

Availability
Description
Soft handover is a kind of handover procedures where the radio links are added and
abandoned in such a manner that the UE always keeps at least one radio link to the
UTRAN. Soft handover only occurs 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 side, soft handover may lead to the occupancy of Iub resource since
multi 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 on CS and PS services. The parameter CIO can also be configured for
different cells for event evaluation.
The intra NodeB softer handover is a kind of soft handover. It sets up RLs in the
sectors within a NodeB and the data receipt on these RLs is combined in the NodeB
using maximum-ratio combination before forwarded to the RNC. Therefore, it will
occupy no more Iub transmission resource compared to the one before the handover.
The RNC can control whether the intra NodeB softer handover should be
implemented by setting the IE in NBAP message RL ADDITION REQUEST.
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.
Benefits
Soft handover provides seamless connection services for mobile users. Besides
these, the intra NodeB softer handover uses maximum-ratio combination on the

uplink in the NodeB to increase the gain of combination. It also saves Iub bandwidth
resources with no more transmission resource needed.

4.27 WRFD-020202 Intra RNC Soft Handover

Availability
Description
The intra RNC soft handover is a kind of soft handover. It sets up RLs in different
NodeBs or in the same NodeB within the RNC. The difference between the intra
NodeB 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 will have its own transport bearer on
Iub interface.
Enhancement
In RAN5.1, neighboring cell combination is supported.
Dependency
None.
Benefits
The intra RNC soft handover provides seamless connection services for mobile users
within the RNC.

4.28 WRFD-020203 Inter RNC Soft Handover

Availability
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
Dependency
The neighbouring RNC should support Iur interface.
Benefits
The inter RNC soft handover provides seamless connection services for mobile
users. Compared with other kinds of soft handovers, it increases the range of soft
handover to the RNCs which have Iur connections with a certain RNC.

4.29 WRFD-020301 Intra Frequency Hard Handover

Availability
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.
 No 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 could be used to
save downlink capacity, compared with soft handover.
 Intra-frequency soft handover fails while intra-frequency hard handover is
allowed
When intra-frequency soft handover fails due to the target cell congestion, intra-
frequency hard handover could be tried with lower service bits rate.
Enhancement
Dependency
None
Benefits
Intra frequency hard handover acts in the scenarios when intra frequency soft
handover can not be used.

4.30 WRFD-010801 Intra RNC Cell Update

Availability
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 will send 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, it will initial 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,
it will initial 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, it will initial
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,
it will initial the procedure. RNC will delete the current radio link and re-establish
a new one.
 Re-entering service area
If a UE moves out of the service area, and then re-enters the service area, it will
initial the procedure. Then RNC will update the camping cell of the UE.
 RLC unrecoverable error

If a UE detects an RLC unrecoverable error in an AM RLC entity, it will initial the

procedure, the RNC will release the RRC connection of the UE or re-establish
the RB according to the attributes of the RB. If it belongs to signal RB, the RRC
connection will be released.
Enhancement
None
Dependency
None.
Benefits
Cell update enables UTRAN to manage a UE’s behavior and enables UE to update
its state when its service or location changes.

4.31 WRFD-010802 Inter RNC Cell Update

Availability
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 with the intra RNC cell update.
The difference between them is that in the inter RNC cell update, the CELL UPDATE
message is firstly received by the DRNC and forwarded to the SRNC, the SRNC then
take some actions according to the cause in CELL UPDATE, for example, relocation.
Enhancement
None
Dependency
The neigbbour RNC should support Iur interface.
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.

4.32 WRFD-010901 Intra RNC URA Update

Availability
Description
User registration area (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 intra RNC URA update means URA update within the RNC.
URA update may be triggered by the following two causes:
 Periodical URA update
UE will send 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, it will initial the procedure, and
the RNC updates the camping URA of the UE accordingly.
Enhancement
None
Dependency
Benefits
URA update enables UTRAN to monitor the RRC connection and manage the
behaviors of the UE in URA_PCH state.

4.33 WRFD-010902 Inter RNC URA Update

Availability
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. As 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 firstly receipted by the DRNC and forwarded to the SRNC, the
SRNC then takes some actions according to the cause of the URA update, for
example, relocation.
Enhancement
None
Dependency
The neighbouring RNC should support Iur interface.
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.

4.34 WRFD-021400 Direct Signaling Connection Re-

establishment (DSCR)
Availability
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 will fail. In such scenario, direct signaling connection
re-establishment (DSCR) feature can be used to prevent the connection from
interrupted. That is, the DRNC will send a 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.
Since DSCR is used to re-establish services by RAU procedure, this feature can only
be applied to PS services, and it is of no help to re-establish CS services.
Enhancement
None
Dependency
None.
Benefits
This feature is a necessary supplement to relocation and it can help to keep PS
services continuous when no Iur interface available or relocation procedure fails.

5 Transmission
5.1 WRFD-050101 Star Topology

Availability
Description
NodeBs can be connected in star topology.
It is applicable in most cases. Each NodeB 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 NodeBs 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.
RNC
NodeB NodeB
NodeB
Enhancement
None
Dependency
The feature is implemented in the NodeB and the RNC.
Benefits
In this mode, each NodeB directly connects to the RNC. Therefore, the star
networking 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.

5.2 WRFD-050102 Chain Topology

Availability
Description
NodeBs 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 of 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.
RNC NodeB NodeB NodeB
Enhancement
None
Dependency
Benefits
Chain networking can reduce costs of transmission equipment, engineering,
construction and transmission link lease.

5.3 WRFD-050103 Tree Topology

Availability
Description
NodeBs can be connected in tree topology.
In most scenarios, the MW (Micro Wave) network is a typically tree topology. It is
suitable for the MW network. In order to increase the efficiency, the hub NodeB
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 occurred in the upper-level NodeB may affect the operation of the lower-level
NodeBs. This networking topology is applicable to a large area of sparse population.
Capacity expansion may result in reconstruction of the network.
Note:
The clock of the NodeB 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
limited to no more than five.
NodeB
NodeB NodeB
RNC
NodeB
Enhancement
None
Dependency
Benefits

It is suitable for microwave transmission network. The hub NodeB is based on the
tree topology. The tree networking requires fewer transmission links than star
networking.

5.4 WRFD-050201 NodeB Clock

Availability
Description
In compliance with 3GPP, the NodeB clock must have a higher clock precision. The
frequency stability of the 10 MHz master clock of the NodeB is lower than ±0.05 ppm.
The NodeB can work in multiple clock synchronization modes to suit different clock
topologies:
 Synchronization with the Iub clock (default mode)
The clock source of the NodeB can be synchronized with the line clock sources
of its upper-level NE such as the RNC. The NodeB selects the reference clock
source from one line for the NMPT, a main control and timing unit.
 Synchronization with GPS
The GPS card is optional unless the NodeB 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
The NodeB can synchronize its clocks with the 2 MHz clock signals from an
external reference clock. The reference clock can be a BITS 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 NodeB, for example,
F_CLK, CLK_4X, and BFN.
In addition to the three synchronization modes above, the NodeB internal clock
can work in free-run mode to keep the NodeB running.
The enhanced stratum 3 OCXO with a high precision works as the master clock
of the NodeB. The OCXO can keep the NodeB in normal service for up to 90
days.
Enhancement

None
Dependency
None
Benefits
The NodeB internal clock can be synchronized to the transport network and no
auxiliary clock equipment is needed to reduce the cost. The synchronized clock has
the required accuracy to meet both radio frequency and transmission network
requirements.

5.5 WRFD-050202 RNC Clock

Availability
Description
RAN clocks must provide reliable clock sources for the NEs in the RAN system to
meet the specifications for the clock accuracy stated in protocols.
When unexpected events occur to the clock sources, the RNC and the NodeB must
report related alarms and start the standby scheme to ensure that the system is not
affected.
The RNC clock sources that can be selected are as follows:
 Building integrated timing supply system (BITS)
 Line clock extracted from the Iu interface
 Global positioning system (GPS)
 External 8 kHz clock provided by an external device
In addition to the four clock sources above, the RNC can also work with the local
oscillator.
The clock sources selected can be configured as needed and when one clock fails, it
will switch to the other one available.
Enhancement
None
Dependency
None
Benefits
This feature provides operators with multi clock sources.

5.6 WRFD-050301 ATM Transmission Introduction Package

Availability
Description
Huawei RAN supports ATM transport optional feature defined in 3GPP. ATM
transmission feature includes 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, please refer to the enhancement of sub-features in ATM
Transmission Introduction Package
Dependency
None

5.6.1 WRFD-05030101 ATM over E1T1 on Iub Interface

Availability
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
The Node B (Uni BTS, BBU3900) ATM over E1/T1 interface board (WMPT) supports:
The Node B (Uni BTS, BBU3900) ATM over E1/T1 interface board (UTRP) supports:
Enhancement
In RAN2.0, NDTI board is introduced.
In RAN5.0, HBBU board is introduced.
In RAN5.1, NUTI board is introduced.
In RAN10.0, WMPT and UTRP（E1 interface） are introduced in Uni BTS.
Dependency
None
Benefits

This feature enables the use of microwave network or PDH legacy network for Iub
transmission.

5.6.2 WRFD-05030102 ATM over Channelized STM-1/OC-3 on Iub Interface

Availability
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.
BSC6810 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, DBS3800) channelized STM-1/OC-3
daughterboard is introduced.
Dependency
None
Benefits
This feature enables the use of SDH network for Iub transmission.

5.6.3 WRFD-05030103 ATM over Non-channelized STM-1/OC-3c on Iub/Iu/Iur

Interface

Availability
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.
BSC6810 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 (Uni BTS, BBU3900) on-channelized STM-1/OC-3 interface board
(UTRP) supports:
Enhancement
In RAN5.1, the Node B (BTS3812E/AE, DBS3800) non-channelized STM-1/OC-3
daughterboard is introduced.
Dependency
None
Benefits

This feature enables the use of SDH network or ATM network for Iub/Iu/Iur
transmission.

5.6.4 WRFD-05030104 Dynamic AAL2 Connections on Iub/IuCS/Iur Interface

Availability
Description
Iub, Iur and IuCS interfaces are all specified with user plane traffic over AAL2
connections. The transport network control plane is used to set up dynamic AAL2
connections for Iub, Iur and IuCS interface using ITU Q.2630.1/Q.2630.2 signaling.
From RAN2.0, the AAL2 CAC can be configured to separate traffic into different types
AAL2 path according to traffic classes. The AAL2 connections for RT (Real Time)
service can be established on CBR/RT-VBR VCC, then, the AAL2 connections for
NRT (Non-Real Time) service can be established on NRT-VBR VCC.
From RAN3.0, AAL2 path specified for HSDPA service is introduced. AAL2 path for
HSDPA can use UBR VCC. From RAN6.0, AAL2 path specified for HSDPA/HSUPA
service is introduced.
Secondary AAL2 path for each traffic class is available from RAN6.0, which provides
resiliency mechanism for Iub hybrid transmission.
Enhancement
In RAN3.0, Q.2630.2 is introduced. It supports AAL2 modification procedure and QoS
optimization for AAL type 2 connections over Iub and Iur.
In RAN3.0, AAL2 path specified for HSDPA service is introduced.
In RAN6.0, AAL2 path specified for HSDPA/HSUPA service is introduced.
In RAN6.0, secondary AAL2 path for each traffic class is introduced, which provides
resiliency mechanism for Iub hybrid transmission.
Dependency
None
Benefits
Huawei implementation of AAL2 enables:
 Separating traffic into different type AAL2 path according to traffic classes
(Conversational, Streaming, Interactive and Background).
 Separating traffic into different type AAL2 path according to R99, HSDPA and
HSUPA traffic.
 Efficient Iub transmission link usage when integrating delay sensitive traffic with
non-delay sensitive traffic.

 Dynamic allocation of physical link bandwidth between delay sensitive traffic and
non-delay sensitive traffic.

5.6.5 WRFD-05030105 Permanent AAL5 Connections for Control Plane

Traffic

Availability
Description
In ATM RAN, AAL5 connections are used to bear Iub/Iur/ Iu signaling and Iub OAM
traffic. 3GPP specified UNI-SAAL is used for Iub control plane connections, and NNI-
SAAL is used for Iur and Iu control plane connections. In Huawei RAN, AAL5
connections for Iub, Iur and Iu interfaces are all set up by configuration.
Enhancement
None
Dependency
None
Benefits
Permanent AAL5 connections for control plane traffic are part of 3GPP Iub, Iur and Iu
specifications.

5.6.6 WRFD-05030106 Call Admission Based on Used AAL2 Path Bandwidth

Availability
Description
The purpose of AAL2 CAC (Call Admission Control) is to maintain the quality of
service and at the same time maximize the transmission resource utilization. This is
achieved by selectively admitting or rejecting request for resources.
AAL2 CAC request occurs at the establishment or modification of AAL2 connection on
Iub, Iur and Iu-CS interfaces.
For CS services, PCR * service factor will be used to admit,
For PS services, GBR * service factor will be used to admit, since no GBR will be
assigned for best effort services, such parameters can be configured by operators.
For HSDPA/HSUPA, GBR * service factor will be used to admit, since no GBR will be
assigned for best effort services, such parameters can be configured by operators.
All the service factors mentioned above can be configured according to the service
classes.
For the handover in users, all the transmission resources will be used to admit to
minimize the possibility of the failure of an existing call.
For the new access user, (100% - handover admission threshold) transmission
resources will be used.
For the bit rate upgrade users, the transmission resources under congestion
threshold will be used.
Enhancement
None
Dependency
None
Benefits
This feature helps to
 Avoid transmission congestion.
 Improve the transmission resource usage.
 Increase the accessibility.

5.6.7 WRFD-05030107 CBR, rt-VBR, nrt-VBR, UBR ATM QoS Classes

Availability
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 differentiation service on 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
Benefits
The feature supports:
 Full inter-operation between RAN and ATM equipment
 VC traffic shaping
 ATM traffic differentiation

5.6.8 WRFD-05030110 F5

Availability
Description
Huawei RNC 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 will be blocked. Then the service will be established on other alternative VCCs
to prevent the failure of the call.
BSC6810 only supports the fault management feature.
Enhancement
In RAN5.1, ATM OAM F5 flows on IuPS user plane VCC is supported by BSC6800.
In RAN10.0, this feature is introduced in BSC6810.
Dependency
None
Benefits
 ATM VCC End-to-End continuity check.
 Supervision of the AAL2 path, and block of the fault AAL2 path.
 Supervision of the IuPS GTPU path, and block of the fault GTPU path.

5.7 WRFD-050304 IMA for E1T1 or Channelized STM-1/OC-3

on Iub Interface
Availability
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 as inverse multiplex on ATM. By this way the existing narrowband transport
links, especially 2 Mbit/s links, can serve broadband ATM transmission. IMA also
enhances transmission reliability.
IMA group IMA group

PHY Ph ysi cal I in k # 0 PHY
Ph ysi cal I in k # 1
PHY PHY
Single ATM c ell stream Original ATM cel l
from ATM la yer Ph ysi cal I in k # 2 stream to ATM la yer
PHY PHY
IMA v irtual l ink
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
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.

5.8 WRFD-050305 UBR+ ATM QoS Class

Availability
Description
Huawei RAN supports UBR+ ATM service class. UBR+ is an enhancement of UBR
with MCR (Minimum Desired Cell Rate) indication. UBR+ is the best choice for Iub
OAM channel. The MCR of UBR+ ensures the connectivity of OAM connection in the
case of Iub transmission resource congestion, while the best effort service of UBR+
fully uses the transmission bandwidth.
Enhancement
None
Dependency
None
Benefits
UBR+ ensures the connectivity of OAM connection and full use of the transmission
bandwidth.

6 System Reliability
6.1 WRFD-040100 Flow Control

Availability
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 the risk of current 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, or system log and service related RRC
connection setup request, paging message. 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
Benefits
The feature ensures the stability and robustness of the RNC, and also ensures that
services with high priorities work properly upon high traffic.

6.2 WRFD-040201 System Redundancy

Availability
Description
Methods for reliability design are used widely, including on the active/standby boards,
in load-sharing and redundant configuration.
Enhancement
None
Dependency
None
Benefits
This feature can improve the system stability and ensure the network performance as
a result.

6.3 WRFD-040301 Operate System Security Management

Availability
This feature is available from RAN10.0; it is only applicable for BSC6810.
Description
The Operate System (OS) Security Management provides customized security policy
and security patches management for operate system in OAM board.
Customized Security for Operating System:
It enhances the operate system to avoid security threats and vulnerabilities by
implementing customized security policy. It can be used to Windows NT4.0 Server,
Windows 2000 Server, Windows XP and Windows 2003 Server.
It can set a series of security policies and then execute them to protect the operation
system. The main functions include executing security policies, restoring the system
state, backup current state of a policy, saving policy settings, exporting policy
settings, importing policy settings, and so on.
The patches management for Operation System:
According to the type of OS, compatibility test of patches will be done timely to ensure
the validity. The list of corresponding OS patches will be provided biannual at least.
Enhancement
None
Dependency
None
Benefits
This feature enhances the reliability of the system, avoids security threats and
vulnerabilities to the OS.

7 RAN Operation & Maintenance
7.1 WRFD-030100 Performance Management

Availability
Description
Performance management provides the overview of the network operation
performance. Performance measurement gives the detailed information of the
network and makes it possible to perform trouble-shooting and network optimization.
1. PM administration
The performance management administration provides operators with a means to
manage the available measurements.
For the new commissioning network elements (RNC, NodeB), pre-defined
performance statistics will start after initial start-up phase or restart completely. The
performance statistics can also be suspended and resumed manually.
The network elements (RNC, NodeB) provide machine-machine interfaces, allowing
the OMC M2000 to collect the necessary statistic data and to set the related
parameters including statistic counters and period.
The statistic data is obtained by the OMC M2000 in binary format files in every
statistic period. The result files are also stored in the network element for up to 24
hours (NodeB) or 10 days (RNC) as backups in case the data transfer fails, which
makes it possible for the OMC M2000 to re-collect the lost data later.
2. PM counters
The performance measurement counters include key counters and other counters.
The key counters are used to generate the key performance indicators (KPIs) of the
network which are defined on the OMC M2000, and these counters are pre-defined
and initialized as soon as the RNC or NodeB starts. The KPIs, related original
counters and formula can be added, modified and deleted on the OMC M2000. Other
counters reflecting the other performances of the network can also start when
needed.
The following counter areas are supported:
 Cell measurement
 Neighboring cell measurement

 Inter-RAT neighboring cell measurement

 RNC overall measurement
 ATM transport measurement
 IP transport measurement
 Standard interface measurement
 Network element hardware measurement
3. PM real-time performance monitoring
This feature provides the monitoring of the real-time and graphic performance of the
network. Therefore, it is more convenient for troubleshooting, road test or network
optimization ,and so on.
The monitoring tasks are managed by the network element (RNC, NodeB) local
management terminal (LMT). The data monitored will be shown with curve while
stored in a file automatically for later review.
The following monitoring items are supported:
 Equipment performance monitoring: CPU occupancy rate, clock source quality,
and so on.
 Connection performance monitoring: SIR measurement, UE TX power, and so
on.
 Cell performance monitoring: PCPICH TX power, the number of cell users, and
so on.
 Link performance monitoring: IMA group, UNI link, and so on.
 Service performance monitoring: RF performance, UL channel scanning, and
service resource occupancy rate.
Enhancement
In RAN5.1, HSDPA related performance counters and monitoring items are
supported.
In RAN6.0, HSUPA related performance counters and monitoring items are
supported.
In RAN10.0, IP PATH real-time performance monitoring is supported.
Dependency
Performance management is implemented by Huawei OMC M2000 except the real-
time monitoring which is managed by the RNC LMT.
Benefits
The performance management provides an efficient way to monitor the network
performance so that network troubleshooting and optimization can be implemented,
And the real-time performance monitoring is a more efficient feature.

7.2 WRFD-030200 Fault Management

Availability
Description
Fault management includes system self-test, fault test, fault supervision and the
handling of UTRAN. With these features, operators can be informed as soon as the
fault occurs in the network and take proper actions to prevent the interruption.
System hardware self-test is initiated in the RNC or NodeB startup phase and health
check of the system can also be activated manually at any time when it enters the
working state.
I. Fault testing
Fault testing includes physical layer testing, link layer testing, and other fault testing.
Fault testing can be activated manually and the operators can browse and save fault
testing results.
II. Alarm management
The operators can browse real-time alarm information, query history alarm
information, and store alarm information. The online help can provide detailed
troubleshooting methods for each alarm.
The RNC can store the history alarm information generated in the past 90 days and at
most 100,000 alarms.
III. Alarm correlation handling
Fault management supports a run-time alarm correlation handling mechanism and
makes it possible to keep the most important alarms instead of all the related ones
when a fault occurs. The number of alarm can be greatly reduced in this way, which
makes it easier to locate and fix the network problems. This mechanism is pre-
defined and built in the network elements (RNC, NodeB) and operators can
customize more alarm correlation handling rules on the OMC M2000.
Operators can filter the alarms of a special object. If a filter is set for an object, the
system will not report the alarms of this object to the alarm management system.
Enhancement
In RAN5.1, HSDPA related alarms are supported.
In RAN6.0, HSUPA related alarms are supported.
In RAN6.0, E1/T1 BER testing is supported.

In RAN10.0, IP PATH fault diagnosis is supported.

In RAN10.0, MSC pool status reporting is supported.
Dependency
Fault management can be implemented with Huawei OMC M2000 or the RNC/NodeB
LMT.
Benefits
The feature enables the automatic supervision of the equipments in the network
elements. With active alarm lists and alarm logs, operators can have a
comprehensive view of the actual state of the network at any time. Operators can also
manually initiate the board testing, which allows the operators to quickly verify the
faulty boards.

7.3 WRFD-030300 Inventory management

Availability
Description
The inventory management helps operators to manage the assets and the
configuration information of the network. With this function, the assets and the
configuration data can be queried and managed on the OMC M2000.
The objects which are managed by this function include physical objects (rack, frame,
slot, board, ports, links, fan etc.) and the logic objects (cell, software, patch, etc.).
When requested from the OMC M2000, an asset and configuration information files
with XML format generate and are sent to the OMC M2000. The OMC M2000
applications store the uploaded information in the network inventory database.
Enhancement
None
Dependency
The inventory information can only be viewed in Huawei OMC M2000.
Benefits
With this function, operators can get the timely and accurate decision-making data for
the existing network.

7.4 WRFD-030400 Configuration Management

Availability
Description
Configuration management provides operators with a means to collect and manage
the network elements (RNC, NodeB) data. It can also control the links between the
NEs. The graphical user interface makes it easy to implement the management.
The configuration of the network elements can be divided into five levels:
1. Initial configuration
The initial configuration of the specific RNC and the NodeB
2. Site basic configuration
Configuration of the OM communication between the RNC, NodeB and the OMC
M2000
3. Site external handware configuration at the NodeB
Configuration of TMA data and antennas
4. Site-specific configuration at the RNC and NodeB
Configuration of Iu, Iub, and Iur interfaces, and the transport networks
5. Cell network configuration at the RNC
Configuration of cells, channels and neighboring cells data
Level 1-3 are done either with the configuration tool through the graphical user
interfaces or with the LMT through executing pre-made configuration files. Levels 4-5
are easily done by OMC M2000, and can also be done by using the configuration
tool.
 Online and offline data configuration and status query
Offline data configuration makes configuration data stored only on the BAM
server. The configuration data will not be sent to the host until the operator loads
it to the host. Therefore, this mode can enhance the efficiency of configuring a
large quantity of data. The RNC supports offline configuration based on host
subracks. Therefore, it allows capacity expansion without interrupting the
services.
Offline configuration supports direct modification of the interface board type and
the board active/standby mode, in the scenarios of replacing ATM interface
boards with IP interface boards or the reverse replacement.

Online data configuration makes data to be sent to the host immediately after the
configuration. There is no need to reset the system and reload the data.
X.731 defines the status of objects. Operators can query the object status (such
as the board or cell status) and obtain the time of last status change.
 Configuration authority control
Under the configuration authority control, data can be configured only on the
RNC/NodeB LMT or the OMC M2000 client at any time. Moreover, only one
operator has the configuration authority at any time. This function enhances the
reliability of the system.
 Configuration rollback at the RNC
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.
 RNC data backup
The two BAM servers work in the active/standby mode. The system
synchronizes the data on the standby BAM server with that on the active BAM
server.
The RNC supports automatic backup and manual backup. It provides a data
backup and restoration tool.
 Network parameter setting
The radio network parameters include two types, the RNC-oriented and cell-
oriented parameters, adapting to different radio environments. The RNC can
check the integrity and consistency of configuration data, such as the data of a
cell.
 Missing neighboring cells detection
Based on the measurement information from UE, the missing configured
neighboring cells can be detected and reported. This can help operators
optimize the configuration of the neighboring cells, and therefore, improve the
network planning efficiency.
Enhancement
In RAN5.1, direct modification of the interface board type and board active/standby
mode in offline way is supported.
In RAN5.1, query of the last status change time is supported.
In RAN10.0, the NodeB state notification to the OMC M2000 is supported.
Dependency

Configuration management can be implemented with Huawei OMC M2000 or the

RNC/NodeB LMT.
Benefits
The feature provides good overview of the current status of the network, and supports
fast installation, expansion and configuration of the network

7.5 WRFD-030501 Security Management

Availability
Description
The security management includes the following functions to enhance system
security level:
 User management: this mechanism allows the setting of the user account and
authority, and the related authorized command group and operation can also be
managed.
 System data backup and restoration
 Applying Windows OS security policy to limit the BAM server IP connectivity
ports to decrease potential risk to the system.
 Supporting the installation of popular anti-virus software including Norton,
Macfee and Officescan.
 Supporting the collecting function of the database operation log and auditing
security log.
 Supporting the triggering of alarms in case of detection of network attack or
unauthorized access exceeding the configured threshold, and so on.
 FTP over the SSL (Security Socket Layer).
 Supporting SSL for data communication between RAN and the OMC. Therefore,
all the remote maintenance communication will be encrypted.
Enhancement
In RAN6.0, FTP over the SSL is supported.
In RAN10.0, the SSL for data communication between RAN and the OMC is
supported.
Dependency
None
Benefits
This feature provides the user authorization and management mechanism to enhance
the network security management.

7.6 WRFD-030601 Interface Tracing

Availability
Description
This feature can be used to trace the interface message online or offline, and manage
the equipment daily.
The operators can verify the configuration data and fix the exceptions by tracing and
interpreting the messages of Iu, Iub, Iur, and Uu. After the configuration data is set,
the operators can confirm whether the signal links are correct by tracing and
interpreting the messages of Iu, Iub, Iur, and Uu. If there are exceptions, the
operators can also fix the exceptions.
So tracing and interpreting the messages of Iu, Iub, Iur, and Uu can take the place of
the signal analyzer. It can be used to analyze the compatibility with the IOT between
the RNC and other network elements.
Based on this feature, the operators also can optimize the network.
Enhancement
None
Dependency
None
Benefits
This integrated interface tracing feature can provide operators with a convenient way
to monitor the signaling procedure on the radio and transport interface, and help the
network optimization and problem solving.

7.7 WRFD-030602 Call Tracing

Availability
Description
This feature supports specific UE signaling tracing. This can be used to trace a
specific UE to confirm the network status. Based on it, the operators can optimize the
network.
Enhancement
None
Dependency
None
Benefits
This integrated user tracing feature can provide the operators with a easy way to
monitor the specific UEs signals on the radio and transport interfaces, and help
network optimization and problem solving.

7.8 WRFD-030701 RNC Software Management

Availability
Description
The RNC supports the software management feature. This feature could help the
operators manage the software on the RNC remotely and easily. Through the MML
commands, the operators could perform the following: with the software
management:
 Querying the version and other running status information of the software.
 Uploading, downloading and activating the software, such as program files,
patch files and the license files. And also the backup of the data files and log files
to the FTP server.
 All types of files transmission, and also the wildcard used.
 Remote patch upgrade for the RNC BAM server.
 File transfer between the OMC M2000 and NodeB as a transfer medium.
The RNC also supports the other standard FTP software.
Besides, the operators could control the products software (including programs,
patches, licenses, data, logs, and so on) from the OMC. The OMC also supports
matching and distinguishing the products software versions. The software
management could improve the efficiency on the products upgrade, data download,
and so on.
Enhancement
In RAN5.1, the remote patch upgrade for the RNC BAM server is supported.
In RAN6.1, the dual active/backup memory management is introduced in BSC6810
which allows the different software exists at the same time, but only one software
version is activated. With this enhancement, software upgrade becomes more
convenient and simple, and moreover, the roll back procedure can be also improved.
In RAN10.0, the uniform patch method of BAM and FAM is supported.
Dependency
None
Benefits
 Efficient and correct installation and upgrade of software packages
 Pre-check of node to verify a successful software installation and upgrade on it.

 Automatic data conversion on the software upgrade.

7.9 WRFD-030702 NodeB Software Management

Availability
Description
The NodeB supports the software management feature. This feature could help the
operators manage the software on the NodeB remotely and easily. Through the MML
commands, the operators could perform the following: with the software
management:
 Querying the version and other running status information of the software.
 Uploading, downloading and activating the software, such as program files,
patch files and the license files. And also the backup of the data files and log files
to the FTP server.
The following is the enhancement features of the software management:
 UBR/UBR+ is supported on the OM IPoA channel: If the traffic is busy, the IPoA
channel is fixed at 64 kbit/s. And when the traffic is idle, the IPoA channel
bandwidth will be automatically increased to ensure the high efficiency software
download.
 Software downloading according to configuration can reduce 30% of the
software package and shorten the downloading time. For adding a board, the
system supports only the software downloading for the board to improve the
efficiency of the software download.
 If the network recovers in 24 hours after the network breakdown, the system
supports resuming the software downloading to avoid the repetition of the
software downloading.
 A maximum of 500 NodeBs can be selected to download and activate the
software in batches automatically. The default value is 50 NodeBs in one batch.
 Hot patch without resetting the NodeB is made with the aim of minimizing
negative traffic impact.
Enhancement
In RAN5.1, the following NodeB enhancement features are introduced.
 UBR supported on the OM IPoA channel
 Downloading software according to the configuration
 Resuming the software download
 Downloading and activating the software in batches
 Online hot patch
Dependency

None
Benefits
The NodeB software management enables the efficient and correct software
installation, upgrade, and version management.

7.10 WRFD-030703 NodeB Software USB Download

Availability
Description
3900 series NodeB provides one USB port to download and activate the host
software. After the NodeB hardware installation, insert the USB disk and the NodeB
system can download and activate the host software automatically.
This feature enables upgrade software locally through the USB instead of through a
PC. With the USB, software upgrade is independent of IUB transmission ready, which
saving time for upgrade. So it benefits fast deployment and low deployment cost.
When system is running after software activated，hardware fault can be detected
according the indicator on BBU. So the fault can be removed in the earliest time and
avoid the staff second access. More convenient remote software commissioning for
NodeB can be supported.
Enhancement
None
Dependency
This feature depends on 3900 series NodeB.
Benefits
Software upgrade is independent of IUB transmission ready, fast deployment.
Avoid the staff second access. More convenient remote software commissioning for
NodeB can be supported.

7.11 WRFD-031100 BOOTP

Availability
Description
Generally, the NodeB only has the host software rather than the data configuration file
after the hardware installation. The feature enables NodeB automatically setup OM
channel without data configured in the system. The maintenance staff can download
the data and software to the NodeB through the OMCH at the far end. The feature
decreases the operation and maintenance costs and enhances the network
maintainability and maintenance quality.
NodeB will automatically setup the O&M channel using the BOOTP protocol. Also,
NodeB will supervisor the O&M channel .when the O&M channel is broken, NodeB
can rebuild it.
Enhancement
None
Dependency
None
Benefits
The feature enables the automatic setup of the default maintenance channel from the
far end. And it enables maintenance personnel to load the data and software to the
NodeB, enhancing the maintainability of the network.

7.12 WRFD-031101 DHCP

Feature Number: WNFD-031101
Availability
Description
In IP mode, the IP maintenance channel is automatically set up through the DHCP.
The dynamic host configuration protocol (DHCP), based on the BOOTP, and
dynamically provides configuration parameters for the internet terminals. The
difference between the BOOTP and the DHCP is that the latter supports automatic
allocation of network addresses. The DHCP works in client/server mode. At the
receipt of the request from a client, the server provides parameters such as IP
addresses, gateway addresses, DNS server addresses for the client. The DHCP
simplifies the IP address management and enables centralization of the IP address
management. The DHCP is implemented in compliance with RFC2131 and
RFC2132.
During the DHCP procedure, the RNC works as the server and the NodeBs work as
clients. Through the DHCP procedure, the NodeBs can automatically obtain the IP
addresses for maintenance, set up the OM channels, and perform the remote
maintenance on the RNC LMT.
Enhancement
None
Dependency
None
Benefits
The feature enables the automatic setup of the default maintenance channel from the
far end. And it enables the maintenance personnel to load the data and software to
the NodeB, enhancing the maintainability of the network.

7.13 WRFD-030800 License Management

Availability
Description
License control is used to control the amount of capacity and what optional features
can be used in the network.
The RNC and the NodeB have their own license files. The license files can be
downloaded remotely to the node. The operators can manage and query the license
contents by the LMT or the OMC M2000 client.
M2000
RNS-1 RNS-2
RNC RNC
NodeB
M200 NodeB
M200
M200
0 M200
0
0 0
Characteristics of the NodeB license management are as follows:

 For all the NodeB under one RNS, it has one license file. One RNS corresponds
to one license file. Each license file records the total number of licenses used by
all the NodeBs under one RNS.
 Licenses are distributed on the OMC M2000 and are controlled on the NodeBs.
The distribution results are sent to the NodeB from the OMC M2000.

 Licenses can be allocated between NodeBs, but they cannot be distributed

between RNSs. The total number of licenses cannot exceed the recorded
number in the license file.
New or updated license files can be customized and ordered from Huawei.
Enhancement
None
Dependency
None
Benefits
The feature enables the fast expansion of capacity without a site visit, and therefore,
decreasing the initial cost of the network construction.

7.14 WRFD-030900 DBS Topology Maintenance

Availability
Description
The distributed NodeB provides RRU network topology scanning automatically. LMT
provides distributed Node B topology management function:
- Display the current networking architecture
- Different legend (in colors) to show the link status of BBU, RRU and CPRI
- Click on the components for monitoring and maintenance
Enhancement
In RAN6.0, the RRU network topology can be scanned automatically,
Dependency
None
Benefits
The feature provides convenient OM functions for DBS to save OPEX for the
operators.

7.15 WRFD-031000 Intelligently Out of Service

Availability
Description
The state of out of service will be 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 NodeB
 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
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.

7.16 WRFD-031200 OCNS

Availability
Description
In system performance tests, due to the number of UE and test environment
restrictions, it is difficult to use many UE to construct a certain level of interference
radio transmission environment,
The NodeB integrates the orthogonal code noise simulator (OCNS). This feature
enables the operators to perform radio load tests without a large number of UEs.
All analog channels are used mutually orthogonal code, the channel adopts the PN9
random code. All analog channel using the different power, but the the power
proportion for different channel is fixed, which is used to simulate the code signal
interference and signal PAR in the real environment. The total power of all analog
channel can be set up, which is used to simulate different downlink interference
(load), to facilitate assessment of the real system performance in different downlink
load.
The OCNS function is very convenient. It can be operated by the OMC. More cells
can operate OCNS function in same time.
Enhancement
None
Dependency
None
Benefits
The feature provides an embedded function to simulate the cell load in the NodeB. It
makes the cell load test more convenient.

7.17 WRFD-031300 Documentation

Availability
Description
The RAN customer documentation includes the following documents:
 RAN system-level documents
 RNC documents
 NodeB documents
The documents cover the planning, installation, commissioning, and maintenance of
the RAN system.
The RAN system-level documents mainly include the following information:
 Documentation guide that describes how to search and use the RAN documents.
 Planning guide that describes how to plan the network, transport, hardware and
OM network.
 Maintenance guide that gives the routine and emergency maintenance methods
and also the troubleshooting methods of the equipments.
 Optimization guide that gives the radio network optimization principles and
suggestions, and the experiences for the future network expansion.
 Reconfiguration guide that describes the operation procedures for the RAN
reconfiguration.
The RNC and NodeB documents introduce the function and features, technical
indices, equipment components of the NE, and also tell how to maintain the
equipments. The documents are basically classified into the following categories:
Document Categories Description
Introduces the key benefits, system architecture,

services and functions, operation and maintenance
Product description
network, reliability and technical specifications of the
NE.
Introduces the hardware of the NE, including the

Hardware description
cabinet, boards, and cables.
Introduces the preparation items before the hardware

Site preparation guide
installation of the NE.

Document Categories Description
Introduces the installation procedures of the

Installation guide
BTS3812E cabinet, boards, and cables.
Introduces how to conduct the initial configuration of

Initial configuration guide
the NE.
Introduces how to commission the NE, which helps

Commissioning guide you ensure that the new NE can access to the
WCDMA RAN system.
Introduces the installation, interfaces, functions, and

LMT user guide routine operation and maintenance of the local
maintenance terminal (LMT).
Introduces the routine hardware maintenance items

Site maintenance guide
and the replacing procedures of the parts of the NE.
Including the following reference documents.

 MML command reference: introduces the
parameter value, suggest value, default value,
and others of each command.
 Alarm reference: introduces the meanings of the
Reference alarms and how to clear them.
 Performance counter reference: introduces the
meaning, measurement point, and others of each
counter.
The online-help-type of these reference documents
can also be obtained in the LMT.
 Well-navigated: RAN customer documentation is planned on the basis of the

network life cycles and roles. All tasks are scenario-based to make the
documentation practical.
 Complete RAN information: Both the system and the contents of the RAN
documentation are greatly improved.
 Topic-oriented: Based on the DITA technology, the information will be chunked
into separate topics.
 Powerful search: The information can be searched by products and data types.
Enhancement
None

Dependency
The documentation will be delivered with the CD as the product delivered.
Benefits
With the feature, the operators can get complete product information, technical
description for supporting the daily equipment maintenance.

8 NodeB Antenna System Solution
8.1 WRFD-060001 Connection with TMA (Tower Mounted

Amplifier)
Availability
Description
The TMA is an optional equipment of the antenna and feeder system. It can
compensate the feeder loss caused by long feeders to increase the uplink coverage
range and cell radius of uplink.
Huawei Node Bs support for 3rd party TMA, including AISG TMA. Huawei Node Bs
complies with AISG1.1 protocol and AISG2.0 protocol.
The TMA is power supplied from NODE B and control by Node B. Huawei Node B
can provide 10-13V output to support the TMA. All the operation management and
alarm can be configured in Node B. 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 one.
For AISG TMA, RET control signal, power, and RF signal can be transmitted via the
RF feeder cable and thus it is easy to install and maintenance. Smart bias tee can
separate DC from the feeder to power supply for LNA, and RET control signal for
RCU. In RAN5.0, Node B support TMA which is compliant with AISG1.1 specification.
In RAN6.1, AISG2.0 TMA can be supported.
Huawei provides dual TMA, which means that the TMA includes two TX/RX branches
in one unit, and only one TMA is needed in each sector. The basic function of the
TMA is described as follows. Each TMA includes two TX/RX branches and one LNA
supervision and alarm generation unit. The functions of both branches are the same
and the function of one branch is described as follows. The Rx channel of each
branch includes two Rx filters and a low noise amplifier. The low noise amplifier can
be automatically passed 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. It can

separate the DC from the feeder, and provide not only power supply to the LNA, but
the RET control signal to the RCU. The Tx channel includes a Tx filter.
Huawei support two kinds of TMA with the gain of 24 dB and 12 dB.
Enhancement
In RAN5.0, Node B support TMA which is compliant with AISG1.1 specification.
In RAN6.1, AISG2.0 TMA can be supported.
Dependency
None
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 NodeBs, and save the cost
of the investment.

8.2 WRFD-060002 Remote Electrical Tilt

Availability
Description
The remote electrical tilt (RET) refers to an antenna system whose down tilt is
controlled electrically.
After an antenna is installed, the down tilt of the antenna needs to be adjusted to
optimize the network. In this situation, the phases of signals that reach the elements
of the array antenna can be adjusted through the electrical control. Then, the vertical
pattern of the antenna can be changed.
The phase shifter inside the antenna can be adjusted through the step motor outside
the antenna, you can adjust the down tilt of the RET antenna when the system is
powered on and monitor the real time down tilt. Therefore, the remote precise
adjustment of the down tilt of the antenna can be achieved.
The following figure shows the operating principle of the RET antenna.
Figure 1.1 Operating principle of the RET antenna
Radome
Phase shifter
Pulling bar
RCU
Control cable
(DC+ control signals)
A pulling bar connects the step motor and the phase shifter. When the step motor is
triggered, the pulling bar moves and then the phase of the phase shifter changes

through the gearing. In this situation, the phase of the signals that arrive in each
element antenna inside the array changes regularly. Then, the direction of the main
beam of the antenna changes accordingly. The down tilt of the antenna is adjusted.
The NodeB supplies the DC power to the step motor and communicates with it
through the AISG interface on the motor.
In the Huawei RET solution, the RET system can either be remotely controlled on the
M2000 or locally controlled on the NodeB Local Maintenance Terminal (LMT). A
command is sent to the Node B on the M2000 or the LMT.
The Node B modulates that command to the On-Off-Keying (OOK) signals and RF
module transfers the DC power and the OOK signals to the STMA or the SBT through
the feeders. The STMA or the SBT demodulates the OOK signals to RS485 signals
and then supplies the RS485 signals and part of the DC power to the RCU. No
additional control cable should be added.
The HUAWEI RET solution supports the 3G RET cascading control. Several 3G RET
antennas can be cascaded and control the signal coming from the same control
cable. The cascading helps save the costs of the smart bias tees (SBTs).
Sector 1 Sector 2 Sector 3
Antenna Antenna Antenna

RCU
RCU
RCU
SBT
BTS
The HUAWEI RET solution supports the 2G/3G RET cascading control. The 3G RET
antennas can be cascaded with the 2G RET antennas. On the 3G operation and
maintenance center (OMC), you can control the down tilt of the 2G RET antenna. The
cascading helps save the costs of smart bias tees (SBTs) and STMAs when the 2G
and 3G RET antennas are installed in the same place.

Dual Band Antenna
2G
RCU
RCU
3G SBT
3G Node B 2G BTS
Enhancement
In RAN6.0, the 3G RET cascading control and 2G/3G RET cascading control is
introduced.
In RAN6.1, AISG2.0 specification can be supported.
Dependency
None
Benefits
The application of the RET can prominently improve the efficiency and minimize the
OM cost for adjusting the down tilt of the antenna. The application of the RET have
the following benefits:
 The RET antennas at multiple sites can be adjusted remotely within a short
period. This improves the efficiency and saves the cost of the network
optimization.
 Adjusting of the RET antenna can be performed in all weather conditions.
 It is easy to operate the RET antennas located in some sites that are difficult to
access.

8.3 WRFD-060003 Same Band Antenna Sharing Unit (900

MHz)
Availability
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 polarity antenna, One uses the main antenna and the other uses the
diversity antenna. So it will bring in low Tx insertion loss. In terms of the Rx signal, the
Rx signal of each antenna channel is separated into two paths. One is used as the
main Rx signal of the system, and the other is used as the diversity Rx signal of the
other system. So the Rx splitter will bring in Rx insertion loss which can be
compensated by adding a LNA (Lower Noise Amplifier).
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. But the ANT_D is the main antenna port of
the GSM, and the ANT_M is the diversity antenna port of the GSM.
There is a limitation when using the SASU: The GSM will only use one antenna
branch.
To allow GSM two antennas to use cases, the SASA (Same Band Antenna Sharing
Adapter) is introduced. The SASA is mainly used to combine 2 branches GSM
carriers to 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 1.2 SASA function block
The typical network diagram of sharing antenna is described as follows:
SASU Note : All the bands is

shown as DL bands
SASA
DL Band
DL Band
NodeB
UMTS
DL Band
BTS
GSM
DL Band
Enhancement
None

Dependency
None
Benefits
The feature helps to share the same band antenna and decrease the uplink division
loss. Compared with the traditional combiner and diplexer, it gets 3 dB gains.

Function Description of Huawei UMTS RAN10.0

Caricato da

Informazioni sul documento

Descrizione originale:

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

Function Description of Huawei UMTS RAN10.0

Caricato da

Copyright:

Formati disponibili

Basic Function Description of

Huawei UMTS RAN10.0

Huawei UMTS RAN

Document Version V1.7

Product Version RAN10.0

Huawei Technologies Co., Ltd.

Copyright © 2007 Huawei Technologies Co., Ltd.

prior written consent of Huawei Technologies Co., Ltd.

第1章 1 System Improvement Introduction.......................................................................1

第2章 1.1 WRFD-000001 System Improvement in RAN5.1..........................................1

第3章 1.2 WRFD-000002 System Improvement in RAN6.0..........................................3

第4章 1.3 WRFD-000003 System Improvement in RAN6.1..........................................5

第5章 1.4 WRFD-000004 System Improvement in RAN10.0........................................7

第6章 2 Standards Compliance........................................................................................ 10

第7章 2.1 WRFD-010101 3GPP R6 Specifications.....................................................10

第8章 2.2 WRFD-010102 Operating Multi-band..........................................................11

第9章 2.3 WRFD-010201 FDD Mode..........................................................................13

第10章 3 RABs and Services.......................................................................................... 14

第11章 3.1 WRFD-010510 3.4/13.6/27.2Kbps RRC Connection and Radio Access

Bearer Establishment and Release.......................................................................................... 14

第12章 3.2 WRFD-010501 Conversational QoS Class..............................................16

第13章 3.3 RFD-010502 Streaming QoS Class.........................................................18

第14章 3.4 WRFD-010503 Interactive QoS Class.....................................................20

第15章 3.5 WRFD-010504 Background QoS Class...................................................21

第17章 3.6.1 WRFD-01060901 Combination of Two CS Services (Except for

Two AMR Speech Services)............................................................................................. 23

第18章 3.6.2 WRFD-01060902 Combination of One CS Service and One PS

第19章 3.6.3 WRFD-01060903 Combination of Two CS Services and One PS

Service (Except for Two AMR Speech Services)..............................................................25

第20章 3.7 WRFD-021104 Emergency Call...............................................................26

第21章 4 RAN Architecture & Functions........................................................................27

第22章 4.1 WRFD-010204 2-Antenna Receive Diversity...........................................27

第23章 4.2 WRFD-010205 Cell Digital Combination and Split...................................28

第24章 4.3 WRFD-010208 Fast Power Congestion Control (FCC)...........................30

第25章 4.4 WRFD-010211 Active TX Chain Gain Calibration....................................31

第26章 4.5 WRFD-021301 Shared Network Support in Connected Mode.................32

第27章 4.6 WRFD-010202 UE State in Connected Mode (CELL-DCH, CELL-PCH,

第28章 4.7 WRFD-010401 System Information Broadcasting...................................36

第29章 4.8 WRFD-010301 Paging UE in Idle, CELL_PCH, URA_PCH State (Type 1)

第30章 4.9 WRFD-010302 Paging UE in CELL_FACH, CELL_DCH State (Type 2). 39

第31章 4.10 WRFD-020900 Logical Channel Management......................................40

第32章 4.11 WRFD-021000 Transport Channel Management..................................42

第33章 4.12 WRFD-022000 Physical Channel Management....................................43

第34章 4.13 WRFD-011401 Integrity Protection........................................................50

第35章 4.14 WRFD-011402 Encryption.....................................................................51

第36章 4.15 WRFD-020501 Open Loop Power Control.............................................52

第37章 4.16 WRFD-020502 Downlink Power Balance..............................................54

第38章 4.17 WRFD-020503 Outer loop Power Control..............................................55

第39章 4.18 WRFD-020504 Inner Loop Power Control.............................................56

第40章 4.19 WRFD-020101 Admission Control.........................................................57

第41章 4.20 WRFD-020102 Load Measurement.......................................................60

第42章 4.21 WRFD-020106 Load Reshuffling...........................................................62

第43章 4.22 WRFD-020107 Overload Control...........................................................64

第44章 4.23 WRFD-020108 Code Resource Management.......................................65

第45章 4.24 WRFD-021101 Dynamic Channel Configuration Control (DCCC).........66

第46章 4.25 WRFD-021201 RNC Resource Sharing.................................................68

第47章 4.26 WRFD-020201 Intra NodeB Softer Handover........................................69

第48章 4.27 WRFD-020202 Intra RNC Soft Handover..............................................71

第49章 4.28 WRFD-020203 Inter RNC Soft Handover..............................................72

第50章 4.29 WRFD-020301 Intra Frequency Hard Handover....................................73

第51章 4.30 WRFD-010801 Intra RNC Cell Update..................................................74

第52章 4.31 WRFD-010802 Inter RNC Cell Update..................................................76

第53章 4.32 WRFD-010901 Intra RNC URA Update.................................................77