Basic Feature Description of Huawei UMTS RAN11.1 V1.1

Basic Feature Description of Huawei
UMTS RAN11.1
Issue V1.1
Date 2009-9-10
HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2009. All rights reserved.
No part of this document may be reproduced or transmitted in any form or by any means without
prior written consent of Huawei Technologies Co., Ltd.
Trademarks and Permissions
and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd. All other
trademarks and trade names mentioned in this document are the property of their respective
holders.
Notice
The purchased products, services and features are stipulated by the commercial contract made
between Huawei and the customer. All or partial products, services and features described in this
document may not be within the purchased scope or the usage scope. Unless otherwise agreed by
the contract, all statements, information, and recommendations in this document are provided “AS
IS” without warranties, guarantees or representations of any kind, either express or implied.
The information in this document is subject to change without notice. Every effort has been made in
the preparation of this document to ensure accuracy of the contents, but all statements, information,
and recommendations in this document do not constitute the warranty of any kind, express or
implied.
Huawei Technologies Co., Ltd.

Address: Huawei Industrial Base
Bantian, Longgang
Shenzhen 518129
People's Republic of China
Website: http://www.huawei.com
Email: support@huawei.com
Telephone: 0755-28560000 4008302118

Fax: 0755-28560111
Basic Feature Description of Huawei UMTS RAN11.1
Contents
1 System Improvement ...................................................................................................................7

1.1 WRFD-000001 System Improvement for RAN5.1 .......................................................................................... 7
1.2 WRFD-000002 System Improvement for RAN6.0 .......................................................................................... 8
1.3 WRFD-000003 System Improvement for RAN6.1 ........................................................................................ 10
1.4 WRFD-000004 System Improvement for RAN10.0 ...................................................................................... 11
2 Standards Compliance ...............................................................................................................17

2.1 WRFD-010101 3GPP R7 Specifications........................................................................................................ 17
2.2 WRFD-010102 Operating Multi-band ........................................................................................................... 18
2.3 WRFD-010201 FDD Mode............................................................................................................................ 19
3 RABs and Services ......................................................................................................................20

3.1 WRFD-010510 3.4/6.8/13.6/27.2 kbit/s RRC Connection and RAB Assignment ......................................... 20
3.2 WRFD-010501 Conversational QoS Class .................................................................................................... 21
3.3 WRFD-010502 Streaming QoS Class ............................................................................................................ 22
3.4 WRFD-010503 Interactive QoS Class ........................................................................................................... 23
3.5 WRFD-010504 Background QoS Class......................................................................................................... 24
3.6 WRFD-010609 Multiple RAB Introduction Package (PS RAB < 2)............................................................. 25
3.6.1 WRFD-01060901 Combination of Two CS Services (Except for Two AMR Speech Services)........... 26
3.6.2 WRFD-01060902 Combination of One CS Service and One PS Service............................................. 27
3.6.3 WRFD-01060903 Combination of Two CS Services and One PS Service (Except for Two AMR
Speech Services) ............................................................................................................................................ 27
3.7 WRFD-021104 Emergency Call .................................................................................................................... 28
4 RAN Architecture & Functions ................................................................................................30

4.1 MRFD-210604 2-Way Antenna Receive Diversity........................................................................................ 30
4.2 WRFD-010205 Cell Digital Combination and Split ...................................................................................... 31
4.3 WRFD-010208 Fast Power Congestion Control (FCC)................................................................................. 32
4.4 WRFD-010211 Active TX Chain Gain Calibration........................................................................................ 33
4.5 WRFD-010202 UE State in Connected Mode (CELL-DCH, CELL-PCH, URA-PCH, CELL-FACH) ........ 34
4.6 WRFD-010401 System Information Broadcasting ........................................................................................ 35
4.7 WRFD-010301 Paging UE in Idle, CELL_PCH, URA_PCH State (Type 1) ................................................ 37
4.8 WRFD-010302 Paging UE in CELL_FACH, CELL_DCH State (Type 2).................................................... 37
Huawei Proprietary and Confidential

Issue V1.71 (2009-09-10) Page 3 of 145
Copyright © Huawei Technologies Co., Ltd
5 Channel Resource Management ..............................................................................................39

5.1 WRFD-020900 Logical Channel Management.............................................................................................. 39
5.2 WRFD-021000 Transport Channel Management........................................................................................... 40
5.3 WRFD-022000 Physical Channel Management............................................................................................. 42
5.4 WRFD-021101 Dynamic Channel Configuration Control (DCCC)............................................................... 48
6 Network Security ........................................................................................................................49

6.1 WRFD-011401 Integrity Protection ............................................................................................................... 49
6.2 WRFD-011402 Encryption ............................................................................................................................ 50
7 Power Control ..............................................................................................................................52

7.1 WRFD-020501 Open Loop Power Control.................................................................................................... 52
7.2 WRFD-020502 Downlink Power Balance ..................................................................................................... 53
7.3 WRFD-020503 Outer Loop Power Control ................................................................................................... 54
7.4 WRFD-020504 Inner Loop Power Control .................................................................................................... 55
8 Cell Management ........................................................................................................................57

8.1 WRFD-020101 Admission Control................................................................................................................ 57
8.2 WRFD-020102 Load Measurement ............................................................................................................... 59
8.3 WRFD-020106 Load Reshuffling .................................................................................................................. 60
8.4 WRFD-020107 Overload Control .................................................................................................................. 62
8.5 WRFD-020108 Code Resource Management ................................................................................................ 63
9 Network Sharing .........................................................................................................................65

9.1 WRFD-021301 Shared Network Support in Connected Mode ...................................................................... 65
9.2 MRFD-210104 BSC/RNC Resource Sharing ................................................................................................ 66
10 Mobility Management .............................................................................................................68

10.1 WRFD-020201 Intra Node B Softer Handover............................................................................................ 68
10.2 WRFD-020202 Intra RNC Soft Handover ................................................................................................... 69
10.3 WRFD-020203 Inter RNC Soft Handover ................................................................................................... 70
10.4 WRFD-020301 Intra Frequency Hard Handover ......................................................................................... 70
10.5 WRFD-010801 Intra RNC Cell Update ....................................................................................................... 71
10.6 WRFD-010802 Inter RNC Cell Update ....................................................................................................... 72
10.7 WRFD-010901 Intra RNC URA Update...................................................................................................... 73
10.8 WRFD-010902 Inter RNC URA Update...................................................................................................... 74
10.9 WRFD-021400 Direct Signaling Connection Re-establishment (DSCR) .................................................... 75
11 Node B Networking Modes ....................................................................................................77

11.1 WRFD-050101 Star Topology...................................................................................................................... 77
11.2 WRFD-050102 Chain Topology................................................................................................................... 78
11.3 WRFD-050103 Tree Topology ..................................................................................................................... 79
12 Clock ............................................................................................................................................81
12.1 MRFD-210501 BTS/NodeB Clock .............................................................................................................. 81
12.2 MRFD-210502 BSC/RNC Clock................................................................................................................. 82

Issue V1.71 (2009-09-10) Page 4 of 145
13 ATM Transmission Introduction Package ...........................................................................85

13.1 WRFD-050301 ATM Transmission Introduction Package........................................................................... 85
13.1.1 WRFD-05030101 ATM over E1T1 on Iub Interface .......................................................................... 86
13.1.2 WRFD-05030102 ATM over Channelized STM-1/OC-3 on Iub Interface ......................................... 87
13.1.3 WRFD-05030103 ATM over Non-channelized STM-1/OC-3c on Iub/Iu/Iur Interface...................... 88
13.1.4 WRFD-05030104 Dynamic AAL2 Connections on Iub/IuCS/Iur Interface ....................................... 89
13.1.5 WRFD-05030105 Permanent AAL5 Connections for Control Plane Traffic...................................... 90
13.1.6 WRFD-05030106 Call Admission Based on Used AAL2 Path Bandwidth ........................................ 91
13.1.7 WRFD-05030107 CBR, rt-VBR, nrt-VBR, UBR ATM QoS Classes................................................. 92
13.1.8 WRFD-05030110 F5........................................................................................................................... 93
14 IMA Transmission for E1/T1 or Channelized STM-1/OC-3 on Iub Interface...............94

14.1 WRFD-050304 IMA Transmission for E1T1 or Channelized STM-1/OC-3 on Iub Interface ..................... 94
15 UBR+ATM QoS Class ..............................................................................................................96

15.1 WRFD-050305 UBR+ ATM QoS Class....................................................................................................... 96
16 Link Aggregation ......................................................................................................................97

16.1 MRFD-210103 Link Aggregation ................................................................................................................ 97
17 System Reliability.....................................................................................................................99
17.1 WRFD-040100 Flow Control....................................................................................................................... 99
17.2 MRFD-210101 System Redundancy.......................................................................................................... 100
17.3 MRFD-210102 Operate System Security Management ............................................................................. 101
18 RAN Operation & Maintenance...........................................................................................104

18.1 MRFD-210301 Configuration Management .............................................................................................. 104
18.2 MRFD-210302 Performance Management ................................................................................................ 106
18.3 MRFD-210303 Inventory Management ..................................................................................................... 109
18.4 MRFD-210304 Faulty Management .......................................................................................................... 111
18.5 MRFD-210305 Security Management ....................................................................................................... 114
19 Message Tracing......................................................................................................................116
19.1 MRFD-210801 Interface Message Tracing ................................................................................................ 116
19.2 MRFD-210802 User Signaling Tracing ..................................................................................................... 117
20 Software Management ...........................................................................................................119

20.1 MRFD-210401 BSC/RNC Software Management .................................................................................... 119
20.2 MRFD-210402 BTS/NodeB Software Management ................................................................................. 120
20.2.2 MRFD-210310 BTS/NodeB Software USB Download.................................................................... 122
20.3 WRFD-031100 BOOTP ............................................................................................................................. 123
20.4 WRFD-031101 DHCP................................................................................................................................ 123
21 License Management..............................................................................................................125
21.1 MRFD-210403 License Management ........................................................................................................ 125
22 Basic Node B Functions .........................................................................................................128

Issue V1.71 (2009-09-10) Page 5 of 145
22.1 MRFD-210309 DBS Topology Maintenance............................................................................................. 128

22.2 WRFD-031000 Intelligently Out of Service .............................................................................................. 130
22.3 WRFD-031200 OCNS ............................................................................................................................... 131
22.4 WRFD-010212 Improved CE Mapping for E-DCH .................................................................................. 131
23 Documentation ........................................................................................................................133
23.1 MRFD-210701 Documentation.................................................................................................................. 133
24 Node B Antenna System Solution .......................................................................................135

24.1 MRFD-210601 Connection with TMA (Tower Mounted Amplifier)......................................................... 135
24.2 MRFD-210602 Remote Electrical Tilt ....................................................................................................... 137
24.3 WRFD-060003 Same Band Antenna Sharing Unit (900 MHz) ................................................................. 140
25 Acronyms and Abbreviations...............................................................................................144

Issue V1.71 (2009-09-10) Page 6 of 145
1 System Improvement
1.1 WRFD-000001 System Improvement for RAN5.1

Availability
This feature is available from RAN5.1.
Summary
This feature is based on 3GPP R5 with a series of newly introduced RAN products and
functions, which meets a wider range of customer requirements and improves the
performance of the product.
Benefits
The benefits of the system improvements include the following:
z Wider product range, including new products and configurations
z Improvement in stability and robustness due to improved functions and algorithms
z Improved performance, including higher capacity
z Enhanced usability, and reduced operating costs
Description
Compatibility with 3GPP Release 5
The UMTS RAN5.1 is based on the 3GPP Release 5, which adds a number of important
functions for RAN and UE. The major new feature is the high speed downlink packet access
(HSDPA), introduced in the 3GPP Release 5. All relevant interfaces are updated according to
the June 2004 version of Release 5, and all essential 3GPP Release 5 CRs since then have
been implemented. The HSDPA Phase 2 is the enhancement of Phase 1, which provides 3.6
Mbit/s per user downlink speed.
The 3GPP TR 25.933 IP transport in the UTRAN is implemented in RAN5.1. RAN5.1 is the
first version to provide the Iub IP transmission. The IP transmission provides new solutions to
the last mile access to the Node B. Thus, it saves the cost of the transmission.
New products and configurations supported
The UMTS RAN5.1 supports the following new products and configurations:

Issue V1.71 (2009-09-10) Page 7 of 145
I. RNC
z Supporting quakeproof cabinets that are suitable for the scenarios with specific
quakeproof requirements
II. Node B
z DBS3800 supports Band 1 (2100 MHz) RRU, 2 carriers 40 W
z DBS3800 supports Band II (1900 MHz) RRU, 2 carriers 20 W
z DBS3800 supports Band III (1800 M) / IX (Japanese 1800 M) RRU, 2 carriers 20 W
z BTS3812E/A supports Band 1 (2100 MHz) new MTRU, 2 carriers 40 W with Doherty
PA for Band I (2100 M)
z BTS3812E/A supports Band II (1900 MHz) MTRU, 2 carriers 40 W
z BTS3812E/A supports Band III (1800 MHz) MTRU, 2 carriers 40 W
z The new transmission interface card NUTI supports the FE ports
z The BBU-interconnecting provides smooth expansion for the DBS3800. The network
can support the evolution from 3 x 1 to 3 x 2.
Thus, the WCDMA RAN5.1 enables a larger variety of radio access networks to be deployed.
High efficiency power amplifier supported
The UMTS RAN5.1 introduced the DPD + Doherty power amplifier.
The digital pre-distortion (DPD) is linearity technology which features stability, wider signal
band and ability to process multi-carrier signals. The Doherty technology is used to separately
amplify the average part and the peak part of the input signal and then combine both to
achieve high efficiency.
The efficiency of Huawei DPD + Doherty PA is 33% and above.
For the Node B BTS3812E and BTS3812AE, the output power at the Node B antenna port
can be up to 40 W. DBS3800, the output power at the Node B antenna port can be up to 40 W.
The support provided by two carriers and high output power for one RF module (MTRU or
RRU) facilitates smooth capacity expansion, and no additional RF modules are required when
the single-carrier configuration is upgraded to the dual-carrier configuration
Enhancement
None.
Dependency
None.

Availability

Issue V1.71 (2009-09-10) Page 8 of 145
Summary
Benefits
z Wider product ranges, including new products and configurations
z The iDBS3800 is one of the best solutions for indoor coverage.
z Usability enhancements, reducing operating costs
Description
functions for RAN as well as UEs. The major new feature that is introduced in the 3GPP
Release 6 is the high speed uplink packet access (HSUPA). All relevant interfaces are updated
according to the March 2006 version of Release 6.
z BTS3812E/AE supports Band V (850 MHz) MTRU, 2 carriers 40 W
z BTS3812E/AE supports Band VIII (900 MHz) MTRU, 2 carriers 40 W
z DBS3800 supports Band V (850 MHz) RRU, 2 carriers 40 W
z DBS3800 supports Band VIII (900 MHz) RRU, 2 carriers 40 W
z iDBS3800, which is for indoor coverage.
z BTS3812AE, a new outdoor macro Node B, improves the outdoor cabinet compared
with BTS3812A.
The iDBS3800 is one of the best solutions for indoor coverage. The iDBS3800 contains three
parts: the Base Band Unit (BBU), the Radio HUB (RHUB) and the Pico Remote Radio Unit
(Pico RRU). The Pico RRU connects to the RHUB through the CAT5 interface, and one
RHUB can support a maximum of 8 Pico RRUs. The RHUB connects to the BBU through the
optic fibers, and the BBU can support a maximum of 24 RHUBs.
The iDBS3800 supports multiple networking modes. It supports up to 192 RF front-end units.
The RRU can be networked with the passive distributed antenna system (PDAS) or work as
the active distributed antenna system (ADAS). The solution is applicable to the requirements
of buildings and districts on different scales.
The iDBS3800 supports the transmission over optic fibers or the CAT 5 cables. The RHUB
can also provide the remote power supply to the Pico RRU. Thus, the iDBS3800 can be
deployed easily and quickly, thus reducing the engineering cost.

Issue V1.71 (2009-09-10) Page 9 of 145
Enhancement
None.
Dependency
None.

Availability
This feature is available from RAN 6.1.
Summary
functions, which meets a wider range of customer requirements, improves the performance of
the product, and enhances some features.
Benefits
z Wider product range, including new products and configurations
z The BSC6810 provides higher capacity and tighter structure.
z New features and enhancement.
Description
functions for RAN and UE. The major new feature that is introduced in the 3GPP Release 6 is
the HSUPA. All relevant interfaces are updated according to the March 2006 version of
Release 6.

Issue V1.71 (2009-09-10) Page 10 of 145
z BSC6810, the new platform RNC based on IP switch for higher capacity with compact
structure.
z Clock server, the new equipment to provide synchronization signals for the Node B
z A new RRU module RRU3804 is introduced in DBS3800 (2100 MHz). RRU3804
supports 60W TOC with A-Doherty 4 carrier.
z DBS3800 supports Band IV (1700 MHz / DL 2100 MHz) RRU, 2 carriers 40 W
z 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
z The Node B supports the AISG2.0 protocol.
z The RRU3804 is a high output power remote radio unit with four carriers; the output
power at the antenna port is 60W. The RRU optimizes the mechanical layout, the new
slim shape leads to easy deployment. Due to the natural heat dissipation, the RRU
without fan improves the reliability and reduces the maintenance cost.
New features and enhancement supported
z IP transmission on the Iu/Iur interface
IP transmission on the Iu/Iur interface is available from RAN6.1, which decreases the
transport cost to a great extent compared with the ATM transport cost.
z Iu flex enhancement
The Iu flex enhancement includes enhanced load balancing and load re-distribution. This
feature improves the performance and meets the operators’ load distribution strategy in
the Iu flex networking scenario.
z 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.
z Other new features and enhancement
For details, please refer to the description and enhancement of the following chapters and
Optional Function Description of Huawei UMTS RAN6.1.
Enhancement
None.
Dependency
None.

Availability

Issue V1.71 (2009-09-10) Page 11 of 145
Summary
Benefits
z New generation Node Bs based on the modular structure and multi-mode platform
enhance the adaptability and the evolution capability. High output power amplifier for
the macro Node B extends the coverage and capacity, saves the number of the sites, and
provides better user experience.
z Higher throughput by supporting the HSUPA Phase 2, that helps to get faster UL speed
Description
Compatibility with the 3GPP Release 6 (2007-03)
The UMTS RAN10.0 supports the following new boards and configurations in existing
products:
z The enhanced base band interface (EBBI) card is used to support the HSUPA Phase2 and
more CEs. It can be co-configured with all other boards in the macro Node Bs
BTS3812E, BTS3812A, and BTS3812AE.
z The enhanced baseband optical interface (EBOI) card is used to support the RRU
connection to the macro Node Bs: BTS3812E, BTS3812A, and BTS3812AE. EBOI also
supports HSUPA phase2 and more CEs. It can be co-configured with all other boards in
the macro Node B.
z The enhanced uplink process (EULP) card is used to support the HSUPA Phase2 and
more CEs, used in the macro Node Bs: BTS3812, BTS3812A, BTS3812E, and
BTS3812AE. The EULP can be co-configured with other boards in the macro Node B.
z The extension base band card (EBBC) is used to support the HSUPA Phase2 and more
CEs in the BBU3806. The EBBC can support hot plugging. With the BBU+EBBC, six
cells are supported.
z The BTS3812E/AE supports the WCDMA Radio Frequency Unit (WRFU), a high
compact RF module integrated with MTRU functions and MAFU functions. The WRFU
supports 80W maximum output power and four carriers. With the WRFU,
BTS3812E/AE can expand configuration to support 3 sectors * 6 carriers or 3 sectors *
8carries.
z The GTPu is re-arrayed for the unified interface board.
z The POUa board of the BSC6810 supports IP over channelized STM-1/OC-3 (CPOS)
Based on the new hardware platform, the UMTS RAN10.0 introduces the new Node B
product portfolio as follows:
z Indoor baseband unit BBU3900.
z Indoor radio filter unit WRFU. The WRFU provides four carriers and 80-W nominal
output power. Only Band 1 (2100 MHz) WRFU will be released in RAN10.0.

Issue V1.71 (2009-09-10) Page 12 of 145
z Outdoor remote radio unit RRU3804. The RRU3804 provides four carriers and 60-W
nominal output power. Band 1 (2100 MHz), Band II (1900 MHz), Band IV (1700 MHz /
DL 2100 MHz), and Band V (850 MHz) RRU3804 will be released in RAN10.0
z Different combinations of the units and auxiliary devices compose the following 3900
series Node Bs: DBS3900/BTS3900/BTS3900A can support up to 24 cell carriers. They
support Omni directional, 2-sector, 3-sector, or 6-sector configuration. The maximum
capacity of the 3900 series Node B is 1536 CEs in the uplink and 1536 CEs in the
downlink.
New features and enhancement supported
z 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.
z 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
z HSPA over Iur
z VoIP over HSPA (trial)
z Enhanced MBMS broadcast
z Robust header compression (RoHC)
z Multi band HO based on service priority and band
z Active queue management (AQM)
z IP transmission enhancement
The following new interface ports are supported:
− IP over STM-1/OC-3c (POS)
− IP over channelized STM-1/OC-3 (CPOS)
Enhancement for the existing port:
− Backup between IP over E1 and IP over FE
− BFD and ARP checking, etc.
z 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.

Issue V1.71 (2009-09-10) Page 13 of 145
Dependency
None.

Availability
Summary
functions, thus meeting the customer’s requirements in a wider range and improving product
performance.
Benefits
HSPA+ Phase 1 provides higher bandwidth and shorter delay:
z Provides higher throughput and improves the system capacity greatly. This enables the
operator to make more profits.
z Provides a higher peak rate for users and a higher speed of data downloading for the UE.
z Improves user experience and provides comprehensive functions for operators.
With the optimization of capacity and performance of VoIP over HSPA/HSPA+, this feature
meets the commercial deployment requirement of VoIP and improves the competitiveness of
operators.
The high throughput of the RNC meets operators' requirements for constructing wideband
radio networks based on HSPA and HSPA+. It can also effectively adapt to the fast
development of data services.
Description
RAN11.0 introduces HSPA+ to meet the increasing demand of subscribers for the bandwidth.
HSPA+ provides higher bit rates and shorter delay. RAN11.0 supports HSPA+ Phase 1, e.g.
64QAM, 2 x 2MIMO, and CPC.
RAN11.0 optimizes the capacity and performance of VoIP over HSPA/HSPA+, and provides
comprehensive functions for the commercial deployment of VoIP over HSPA/HSPA+.
In compliance with the 3GPP R7 2008-03, RAN11.0 provides the following new features and
enhancements:
z HSPA+ Phase 1:
− 64QAM (downlink): provides a higher peak rate of 21 Mbit/s and increases the
downlink capacity through high order modulation.
− 2 x 2MIMO: provides a higher peak rate of 28.8 Mbit/s and increases the downlink
capacity through parallel downlink bit streams.
− Enhanced layer 2: provides flexible RLC PDU size, as the basis for 64QAM, MIMO,
and the enhanced CELL_FACH function.

Issue V1.71 (2009-09-10) Page 14 of 145
− CPC: reduces user access time, increases the air interface capacity, and lowers UE
power consumption (prolongs the battery service life).
− Enhanced CELL_FACH: provides a higher peak rate of 1 Mbit/s in CELL_FACH
state.
z Commercial deployment of VoIP over HSPA/HSPA+: improves the capacity and
performance of VoIP over HSPA/HSPA+, and fully meets the requirement for
commercial deployment.
z DSAC
z Optimized RNC upgrade: shortens the upgrade time and reduces the negative impact on
services.
z Improved RNC capacity: improves the BSC6810 throughput to 3.91G.
z Newly added board: The BTS3812E/AE has a new downlink baseband processing unit,
namely, EDLP. The EDLP provides a downlink processing capacity of six cells, 384 CEs,
and DL 64QAM and MIMO of HSPA+.
Enhancement
None.
Dependency
None.

Availability
Summary
This feature is based on new boards in RNC, which meet the customer’s requirements in a
wider range and improve product performance.
Benefits
New boards are introduced in RAN11.1. With these new boards, the operators are benefited
by the merits list below:
z The RNC capacity increases. The PS throughput doubles compared to that with legacy
boards.
z The operators can use less hardware to reach the capacity requirement. The CAPEX is
reduced.
With new boards, the spare hardware number also saved.

Issue V1.71 (2009-09-10) Page 15 of 145
Description
RAN11.1 introduces several boards, they are:
z SPUb board: charge in control plane service processing
z DPUe board: charge in user plane data processing
z AOUc: ATM interface board with 4 CSTM-1 exports
z UOIc: ATM interface board with 8 STM-1 exports
z POUc: IP interface board with 4 STM-1 exports
z FG2c: IP interface board with 12 FE or 4 GE exports
z GOUc: IP interface board with 4 GE exports
With the new boards, the RNC capacity increases.
Enhancement
None
Dependency
None

Issue V1.71 (2009-09-10) Page 16 of 145
2 Standards Compliance
2.1 WRFD-010101 3GPP R7 Specifications

Availability
Summary
RAN11.0 complies with 3GPP R7 (2008-03). The functions, compatibility, and
standardization of the system are improved.
Benefits
In compliance with the 3GPP R7 protocol, RAN11.0 provides the basis for new features and
enhanced functions, with which high-performance services and comprehensive functions are
provided for subscribers.
This feature also provides the following benefits:
z Improves operator's competitiveness
z Enables the interconnection with other Network Elements (NEs) that comply with the
3GPP R99, R4, R5, R6, or R7 protocol, thus protecting the operator's investment
Description
RAN2.0 complies with the 3GPP R99/R4.
RAN3.0/5.0 complies with the 3GPP R99/R4/R55.
RAN6.0/6.1 complies with the 3GPP R99/R4 /R5/R6 2006-03+CR.
RAN10.0 complies with the 3GPP R99/R4 /R5/R6 2007-03.
RAN11.0 complies with the 3GPP R99/R4 /R5/R6/R7 2008-03.
Enhancement
None.

Issue V1.71 (2009-09-10) Page 17 of 145
Dependency
Dependency on other NEs
For the new features introduced in R7 and the enhancements of the standard interfaces, the
standard interfaces and user interfaces at the CN should also be upgraded to ensure
compliance with the protocols.
2.2 WRFD-010102 Operating Multi-band

Availability
Summary
This feature meets the requirement of the operators for use of different frequency bands in
different regions. In addition, the Node B supports the co-cabinet of different frequency bands,
thus saving the deployment cost for the operators and meeting the space requirement.
Benefits
The Node Bs can be deployed widely according to the operator’s frequency requirement.
The multi-band supported Node B can save the cost of the hardware investment.
Description
The following 3GPP defined UMTS frequency bands are supported.
Operating Band UL Frequencies DL frequencies

UE transmit, Node UE receive, Node B
B receive transmit
Band I (2100M) 1920–1980 MHz 2110–2170MHz
Band III/IX (1800M) 1710–1785 MHz 1805–1880 MHz
Band II (1900M) 1850–1910 MHz 1930–1990MHz
Band V/VI (850M) 824–849MHz 869–894MHz
Band VIII (900M) 880–915 MHz 925–960 MHz
Band IV(1.7/2.1G) 1710–1755 MHz 2110–2155 MHz
The macro Node Bs provide multi-band co-located in one cabinet. Due to the flexible design
of Huawei Node B architecture, the multi-band only has impact on the RF system. The
baseband modules including power, transmission, and channel cards are shared by different
bands. The operators can use the required frequency segments to save the footprint of the
Node B and improve the baseband usage
The feature is implemented in the Node B and RNC.

Issue V1.71 (2009-09-10) Page 18 of 145
Different frequency bands should be configured with different RF modules.
Enhancement
In RAN5.0, the macro Node B supports the 1900M and 1800M frequency bands.
In RAN5.1, the RRU supports the 1900M and 1800M frequency bands.
In RAN6.0, the 850M and 900M frequency bands are supported by the macro Node B and
RRU.
In RAN6.1, the AWS (UL 1700M/DL 2100M) frequency band is supported by the RRU.
The BTS3900/BTS3900A only supports Band1 2100M and 850M in RAN10.0.
Dependency
None.
2.3 WRFD-010201 FDD Mode

Availability
Summary
Huawei RAN supports the FDD mode.
Benefits
This feature defines the mode supported by Huawei RAN.
Description
The 3GPP specification comprises Frequency Division Duplex (FDD) mode and Time
Division Duplex (TDD) mode. FDD mode uses individual frequency band for the uplink and
downlink. TDD mode uses the same frequency band for the uplink and downlink. Huawei
RAN only supports FDD mode.
Enhancement
None.
Dependency
The relevant NEs should comply with the 3GPP specifications in FDD mode.

Issue V1.71 (2009-09-10) Page 19 of 145
3 RABs and Services
3.1 WRFD-010510 3.4/6.8/13.6/27.2 kbit/s RRC Connection

and RAB Assignment
Availability
Summary
This feature supports the RRC connection/release of different rates and RAB assignment to
meet the QoS requirements for different services.
Benefits
This is an essential feature for the UMTS RAN.
Description
RAN11.0 supports the 3.4/6.8/13.6/27.2 kbit/s RRC connection and Radio Access Bearer
(RAB) assignment. The RNC will map the RRC connection request and the RAB assigned by
the CN according to different QoS requirements.
z Mapping of channel types
For RRC connection, the operators can decide which channel type (CCH/DCH) should
be configured according to the RRC SETUP REQUEST message.
For RAB assignment, the operators can decide in which cell the RAB should be set up.
z Mapping of RAB parameters
The associated transport channel and physical channel parameters are configured based
on the channel types. Huawei RAN provides different sets of configuration parameters
for typical services. These parameters are supported by each typical service. If no service
class matches the feature, choose the most approximate parameters. Moreover, the
operators can add new service classes and configure associated parameters. These
features can fully utilize the services supported by the system.
The PS streaming/interactive/background RAB can also be set up on the HS-DSCH or
E-DCH. These features include the following optional features:
− WRFD-010610 HSDPA Introduction Package

Issue V1.71 (2009-09-10) Page 20 of 145
− WRFD-010612 HSUPA Introduction Package

− WRFD-010630 Streaming Traffic Class on HSDPA
− WRFD-010632 Streaming Traffic Class on HSUPA
SRB always occupies SF 256 at the rate of 3.4 kbit/s or 6.8 kbit/s. It can increase the signaling
transmission speed and shorten the delay at the rate of 6.8 kbit/s. Therefore, if all the
downlink services of the UE are set up on the HS-DSCH and the SRB is carried on the DCH
in the downlink, the SRB has a rate of 6.8 kbit/s.
Enhancement
RAN3.0 supports RRC connection of 13.6 kbit/s.
RAN6.1 supports RRC connection of 27.2 kbit/s.
RAN11.0 supports RRC connection of 6.8 kbit/s and the retainment of SRB of 6.8 kbit/s.
Dependency
None.
3.2 WRFD-010501 Conversational QoS Class

Availability
It is introduced in 3GPP R99.
Summary
The RNC supports the conversational services of CS and PS domains issued from the CN and
sets up appropriate RABs based on the QoS.
Benefits
The QoS-supported conversational services provide guaranteed QoS for upper-layer services.
Description
QoS classes also refer to traffic classes. The following four QoS classes are defined in 3GPP:
z Conversational class
z Streaming class
z Interactive class
z Background class
The main difference between the preceding QoS classes lies in the extent to which the traffic
is delay sensitive. Conversational class is meant for traffic which is very delay sensitive and is
mainly used to carry real time traffic flows. Fundamental characteristics for real time
conversational QoS class include the following:

Issue V1.71 (2009-09-10) Page 21 of 145
z Preserved time relations (variation) between information entities of the stream.

z Conversational pattern (stringent and low delay).
There are conversational class services in both CS and PS domains. The most well known
conversational traffic is speech and video phone services in CS domain and VoIP in PS
domain.
Huawei RAN supports the following conversational services as fundamental features:
z CS AMR speech services of 8 rates, including 12.2 kbit/s, 10.2 kbit/s, 7.95 kbit/s, 7.4
kbit/s, 6.7 kbit/s, 5.9 kbit/s, 5.15 kbit/s, and 4.75 kbit/s. The RNC selects SF256 for
AMRS services whose maximum rate is lower than 7.95 kbit/s.
z CS transparent data services (conversational class) with 64 kbit/s, 56 kbit/s, 32 kbit/s,
and 28.8 kbit/s.
z PS bidirectional symmetric speech services at the rates of 64 kbit/s, 42.8 kbit/s, 32 kbit/s,
16 kbit/s, and 8 kbit/s.
Enhancement
None.
Dependency
Both CN and UE should support this service.
3.3 WRFD-010502 Streaming QoS Class

Availability
Summary
The RNC supports the streaming services of CS and PS domains issued from the CN and sets
up appropriate RABs based on the QoS.
Benefits
The QoS-supported steaming services provide guaranteed QoS for upper-layer services.
Description
z Streaming class
z Interactive class
z Background class

Issue V1.71 (2009-09-10) Page 22 of 145
is delay sensitive. Streaming class is new to data communication, thus it raises a number of
new requirements in both telecommunication and data communication systems. Streaming
class is characterized by the time relations (variation) between information entities (i.e.
samples, packets) of the stream that should be preserved, although it does not have strict
requirements on transfer delay. Fundamental characteristics of streaming QoS class include
the following:
z Preserved time relations (variation) between information entities of the stream:
z 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:
z CS transparent data services (streaming class) of 64 kbit/s.
z CS nontransparent data services of 57.6 kbit/s, 28.8 kbit/s, and 14.4 kbit/s.
z 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.
z 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 and HSUPA which are optional features
and described in WRFD-010610 HSDPA Service and WRFD-010612 HSUPA Service.
Enhancement
RAN6.0 supports PS 384 kbit/s bidirectional symmetric or asymmetric streaming service.
Dependency
3.4 WRFD-010503 Interactive QoS Class

Availability
Summary
The RNC supports the interactive services of CS and PS domains issued from the CN and sets
up appropriate RABs based on the QoS.
Benefits
The QoS-supported interactive services provide guaranteed QoS for upper-layer services.

Issue V1.71 (2009-09-10) Page 23 of 145
Description
z Streaming class
z Interactive class
z Background class
is delay sensitive. Interactive class is another typical data communication scheme that is
characterized by the request response pattern of the end-user. At the message destination,
there is an entity expecting the message (response) within a certain time. Round trip delay
time is therefore one of the key attributes. Another characteristic is that the contents of the
packets are transparently transferred (with low bit error rate). Fundamental characteristics of
Interactive QoS class include the following:
z Request response pattern.
z Preserve payload content.
Interactive class services apply only to the PS domain. The most well known interactive
traffic is web browsing.
Huawei RAN supports the following interactive services as fundamental features:
PS bidirectional symmetric or asymmetric interactive services at the rates of 384 kbit/s, 256
kbit/s, 144 kbit/s, 128 kbit/s, 64 kbit/s, 32 kbit/s, 16 kbit/s, and 8 kbit/s.
The higher rates can only be supported on HSDPA and HSUPA which are optional features
Enhancement
RAN3.0 supports UL PS service of 384 kbit/s.
Dependency
3.5 WRFD-010504 Background QoS Class

Availability
Summary
The RNC supports the background services of CS and PS domains issued from the CN and
sets up appropriate RABs based on the QoS.

Issue V1.71 (2009-09-10) Page 24 of 145
Benefits
The QoS-supported background services provide guaranteed QoS for upper-layer services.
Description
z Streaming class
z Interactive class
z Background class
is delay sensitive. Background class is one of the typical data communication schemes. It is
characterized by the fact that the destination does not expect the data within a certain time.
The scheme is thus more or less insensitive to the delivery time. Another characteristic is that
the contents of the packets are transparently transferred (with low bit error rate). Fundamental
characteristics of background QoS class include the following:
z The destination does not expect the data within a certain time.
z The payload content is preserved.
Background class services apply only to the PS domain. The most well known background
traffic is background download or E-mails.
Huawei RAN supports the following background services as fundamental features:
PS bidirectional symmetric or asymmetric background services at the rates of 384 kbit/s, 256
kbit/s, 144 kbit/s, 128 kbit/s, 64 kbit/s, 32 kbit/s, 16 kbit/s, and 8 kbit/s.
The higher rates can only be supported on HSDPA and HSUPA which are optional features
Enhancement
RAN3.0 supports UL PS service of 384 kbit/s.
Dependency
3.6 WRFD-010609 Multiple RAB Introduction Package (PS

RAB < 2)
Availability

Issue V1.71 (2009-09-10) Page 25 of 145
Summary
This feature provides multi-service combinations to meet the request for concurrent services.
Benefits
Multi-RAB support capability provides operators with more service solution choices.
Description
Multi-RAB can provide more abundant services simultaneously to the upper layer. In the case
of multi-RAB that has less than two PS RABs, Huawei supports the following specifications:
z Combination of two CS services (except for two AMR speech services)
z One CS service + one PS service
z Two CS services + one PS service (except for two AMR speech services)
In all the preceding combinations, the bit rates of CS and PS services are not limited. That is,
any bit rates of CS and PS services defined in WRFD-010501 Conversational QoS Class,
WRFD-010502 Streaming QoS Class, WRFD-010503 Interactive QoS Class, and
WRFD-010501 Background QoS Class can be selected in the combination.
The PS conversational/streaming/interactive/background services can also be mapped to
HS-DSCH or E-DCH. These features need the support of the optional features WRFD-010610
HSDPA Introduction Package and WRFD-010612 HSUPA Introduction Package.
Enhancement
None.
Dependency
Both CN and UE should support the specifications for multiple RABs.
3.6.1 WRFD-01060901 Combination of Two CS Services (Except

for Two AMR Speech Services)
Availability
Summary
Huawei supports combination of two CS services (except for two AMR speech services).
Benefits

Issue V1.71 (2009-09-10) Page 26 of 145
Description
Huawei supports combination of two CS services (except for two AMR speech services).
Enhancement
None.
Dependency
3.6.2 WRFD-01060902 Combination of One CS Service and One

PS Service
Availability
Summary
Huawei RAN supports the combination of one CS service and one PS service.
Benefits
Description
Huawei RAN supports the combination of one CS service and one PS service.
Enhancement
None.
Dependency
3.6.3 WRFD-01060903 Combination of Two CS Services and One

PS Service (Except for Two AMR Speech Services)
Availability

Issue V1.71 (2009-09-10) Page 27 of 145
Summary
Huawei RAN supports the combination of two CS services and one PS service (except for
two AMR speech services).
Benefits
Description
Huawei RAN supports the combination of two CS services and one PS service (except for
two AMR speech services).
Enhancement
None.
Dependency
3.7 WRFD-021104 Emergency Call

Availability
Summary
This feature provides the emergency call a higher priority over common calls to ensure that
the emergency call gets preference to access the network.
Benefits
It is an essential feature for UMTS RAN. It enables the emergency call to have a higher
priority over other services in resource allocation.
Description
When an emergency call is triggered, “Establishment Cause” in the RRC Connection Request
message is set to “Emergency Call”.
Emergency call always has priority over the ordinary calls. When enough resources are not
present in the cell, pre-emptive action is triggered on ordinary calls with lowest priority to
guarantee that the emergency call can access the network and be served.

Issue V1.71 (2009-09-10) Page 28 of 145
Enhancement
None.
Dependency
None.

Issue V1.71 (2009-09-10) Page 29 of 145
4 RAN Architecture & Functions
4.1 MRFD-210604 2-Way Antenna Receive Diversity

Availability
This feature is available from GBSS6.1 and RAN 2.0.
Summary
This feature is a technique for improving the receive performance of the uplink channels.
Benefits
This feature improves receiver sensitivity and uplink coverage, thus reducing the CAPEX.
Description
With this feature, the same signal is received by two antennas. Then the two ways of signals
on the two antennas are combined after being processed. Thus, the signal attenuation is
reduced.
This feature enhances the RX capability of uplink channels. Huawei MBTS supports both
receive diversity and none receive diversity.
With this feature, the MBTS does not require additional devices and algorithms. Compared
with one-way none receive diversity, this feature requires twice the number of RX channels.
In typical scenarios, the receiver sensitivity can be improved by 2 to 3 dB.
Enhancement
None.
Dependency
Impacts on the hardware of the MBSC
None.
Impacts on the hardware of the MBTS
In receive diversity mode, the Node B should provide sufficient RF channels and
demodulation resources to meet the requirements for the number of antenna diversities.

Issue V1.71 (2009-09-10) Page 30 of 145
Dependency on other features of the GBSS/RAN

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

Availability
Summary
This feature enables multiple sectors to use the resources in the same cell, thus improving
system spectrum efficiency and resource utilization. The DBS3800, DBS3900, iDBS3800,
and iDBS3900 support this feature.
Benefits
Compared with the analog combination and split, the digital combination and split can
provide larger capacity and wider coverage without bringing additional noises and signal
losses. In this manner, cell distribution can be adjusted through software to adapt to actual
traffic distribution and changes, thus improving CE resource utilization and operation
benefits.
Description
Cell split means that a cell in the Node B is split into multiple sectors through the digital
combination and split and the sectors can cover multiple areas. Cell split applies to scenarios
such as indoor coverage and high-speed railway or expressway coverage. Based on cell split,
the antennas in different sectors can transmit and receive signals from the same cell. When
expanding the capacity or adjusting the network, you can flexibly configure the mapping
between the RRU and cell through software without changing the hardware. The DBS3800,
DBS3900, iDBS3800, and iDBS3900 support cell split and digital combination and split.
The following figure shows the logical structure of the digital combination and split. The
downlink digital split means that a downlink signal is split into two signals, that is, the
downlink signal from the upper-level RRU or baseband unit is simultaneously sent to the RF
Tx path of the RRU and the lower-level RRU. The uplink digital combination means that two
uplink signals are combined into one signal, that is, the uplink signals from the RF Tx path of
the RRU and the lower-level RRU are combined and then sent to the upper-level RRU or
baseband

Issue V1.71 (2009-09-10) Page 31 of 145
unit.
Upper-level RRU or BBU
Slave
RRU
CPRI
Split RF Tx Path Du
Interface
ple
xer
Combined RF Rx Path
Uplink
CPRI
Interface
Master
Lower-level RRU
Each RRU or pRRU has an independent antenna that covers different sectors. One cell can be
set for multiple RRUs so that they have the same scrambling code.
This feature is introduced to Huawei pRRU and RRU, and it can be applied to scenarios such
as indoor coverage and along high-speed railway or expressway coverage.
Enhancement
None.
Dependency
None.
4.3 WRFD-010208 Fast Power Congestion Control (FCC)

Availability
Summary
Fast power congestion control (FCC) is implemented on the Node B side. This feature aims to
quickly rectify system overload to prevent the output power from exceeding the maximum
power allowed by hardware.
Benefits
This feature enables full utilization of Power Amplifiers for traffic load, especially for
dynamic power sharing in one carrier between R99 and HSDPA.

Issue V1.71 (2009-09-10) Page 32 of 145
Description
FCC is a Node B function that complements the RNC congestion control. The function
supervises the output power per slot that users (all users) demand at the same time, using the
same time scale as the fast power control function.
Huawei provides the DL automatic level control (ALC) function as the method of fast power
congestion control in the Node B, in order to limit the output power and avoid the PA
saturation. The ALC supervises the transmit power in real time. When the input power reaches
or exceeds the predefined threshold, the ALC can increase the TX channel attenuated signals
to keep the output power lower than the threshold, thus avoiding the PA saturation.
The Node B uses the FCC to quickly control the output power, the control Reaction time is
1024chip, which is fast enough to fully prevent saturation of the TX chain or overdriving of
the power amplifier without the need for power margins.
Therefore, cell behavior remains robust at maximum load without running the risk of dropped
cells or modulation inaccuracy. In addition, the RNC congestion and admission thresholds can
be set to higher levels, which increase cell capacity without compromising overall quality of
service.
Enhancement
None.
Dependency
Dependency on Node B hardware
Only DBS3800/DBS3900 and iDBS3800/iDBS3900 support this feature.
4.4 WRFD-010211 Active TX Chain Gain Calibration

Availability
Summary
This feature enables the monitoring and adjustment of digital channel gains, thus ensuring
stable output power.
Benefits
This feature provides high output power accuracy for the Node B, and reduces the margins
required in network dimensioning. Thus, the entire power can be used for traffic.
Description
The active TX chain gain calibration can increase the accuracy of the downlink transmit
power (for example, the power accuracy of the 3900 series Node B is +/- 0.6 dB), thus
reducing the protection band reserved for power calculation in network planning and
improving the utilization of transmit power.

Issue V1.71 (2009-09-10) Page 33 of 145
Performance drift occurs on all RF hardware. An RF part (for example, TRX, PA, RF
connector, or duplexer) has a different gain due to different temperatures, frequencies, and lot
numbers. Such a gain difference leads to a 1.5 dB to 2 dB error in the Node B transmit power.
The active TX chain gain calibration can reduce the changes in analog channel gains caused
by different temperatures, frequencies, and lot numbers, thus ensuring a stable total gain of
links. The active TX chain gain calibration calculates the difference between the downlink
input power and transmit power and then adjusts digital channel gains according to the
transmit power on the analog channel. Gain control is performed in real time, thus ensuring
the accuracy of transmit power.
Enhancement
None.
Dependency
None.
4.5 WRFD-010202 UE State in Connected Mode

(CELL-DCH, CELL-PCH, URA-PCH, CELL-FACH)
Availability
Summary
Huawei RAN supports four UE states in connected mode: URA_PCH, CELL_PCH,
CELL_FACH, and CELL_DCH. This feature enables radio resources to be saved effectively.
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
degrading user experience. It is an essential feature of UMTS RAN system.
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 four states.
URA_PCH/CELL_PCH: In these states, there is no DCCH or DTCH available for the UE.
When UE originates a call or receives paging from CN, CELL_UPDATE procedure is
triggered. Periodically URA UPDATE or CELL_UPDATE procedure can also be used to
maintain the connection with the network. No DTCH or DCCH is allocated Hence, UE in
these states do not occupy any radio resources, and no service is available.
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 to
camp on a proper cell through the Cell Update procedure. Since the common resources can be

Issue V1.71 (2009-09-10) Page 34 of 145
shared among different UEs, the traffic QoS such as transfer delay, bandwidth, and so on
cannot 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. The dedicated resources are allocated.
Hence, the traffic QoS is guaranteed when the cell load is increased accordingly. When UE
uses HSDPA and/or HSUPA, it also belongs to CELL_DCH state.
The preceding four states can be transformed according to the UE service characteristics and
behaviors, such procedures are called 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
The UE must support related states.
4.6 WRFD-010401 System Information Broadcasting

Availability
Summary
This feature supports system information as stipulated in multiple protocols. Based on the
system information, the network can provide UEs with rich access layer and non access layer
information required for running UEs on the network, and the information that controls UE
behavior.
Benefits
This feature provides UEs with rich access layer and non access layer information required
for running UEs on the network, and the information that controls UE behavior.
Description
System information broadcasting which is required by the UE for its operation in the network
provides UE with the Access Stratum and Non Access Stratum information.

Issue V1.71 (2009-09-10) Page 35 of 145
The system information is organized in a tree-type manner. A master information block gives
references and scheduling information to a number of system information blocks in a cell. The
system information blocks contain the actual system information.
Scheduling of system information blocks is performed by the RRC layer in UTRAN. RRC
can automatically calculate the repetition period and position of each SIB segment based on
its importance.
The key information of each SIB Huawei supported is listed in the following table.
System Area Content

Information Scope
Block
Master information Cell SIB scheduling information

block
Scheduling block 1 Cell SIB scheduling information
Scheduling block 2 Cell SIB scheduling information
SIB1 PLMN NAS information and timers used by UE in connected

mode and idle mode
SIB2 Cell URA Id
SIB3 Cell Parameters of cell selection and reselection in idle
mode
Parameters of hierarchical cell in idle mode
SIB4 Cell Parameters of cell selection and reselection in
connected mode
Parameters of Hierarchical cell in connected mode
(CCH state)
SIB5 Cell Parameters of common physical channels for UE in
idle mode(PRACH, AICH, PICH, S-CCPCH)
SIB6 Cell Parameters of common physical channel in connected
mode
SIB7 Cell UL interference, dynamical persistence level
SIB11 Cell Measurement control information in idle mode
SIB12 Cell Measurement control information in connected mode
SIB18 Cell PLMN ID of neighboring cells
Enhancement
RAN5.0 supports SIB4, SIB6, and SIB12.
RAN10.0 supports SIB11 bis. SIB11 bis contains cell measurement control information, new
intra-frequency cell information, new inter-frequency information, and new inter-RAT cell
information.

Issue V1.71 (2009-09-10) Page 36 of 145
Dependency
None.
4.7 WRFD-010301 Paging UE in Idle, CELL_PCH,

URA_PCH State (Type 1)
Availability
Summary
This feature supports paging type 1. UTRAN sends a paging message to the UE in idle,
CELL_PCH, or URA_PCH state through the paging control channel (PCCH).
Benefits
When an UE is in idle, CELL_PCH, or URA_PCH state, UTRAN sends a paging message to
the UE through the PCCH.
Description
Paging type 1 procedure is used to transmit paging information to the selected UEs in idle
mode, CELL_PCH or URA_PCH state using the PCCH. With this feature, upper layers in the
network can:
z Trigger UE establishing a RRC signaling connection.
z Trigger CELL UPDATE procedure of UE in CELL_PCH or URA_PCH state.
z Trigger reading of updated system broadcast of UE in idle mode, CELL_PCH or
URA_PCH state.
z Trigger releasing signaling connection of UE in CELL_PCH or URA_PCH state.
Enhancement
None.
Dependency
None.
4.8 WRFD-010302 Paging UE in CELL_FACH, CELL_DCH

State (Type 2)
Availability

Issue V1.71 (2009-09-10) Page 37 of 145
Summary
This feature supports paging type 2. The network can control the UE in CELL_FACH or
CELL_DCH state through the dedicated control channel (DCCH).
Benefits
The network can control the UE in CELL_FACH or CELL_DCH state which has DCCH with
paging type 2 procedures.
Description
In paging type 2, UTRAN sends a paging message to the UE in CELL_FACH or CELL_DCH
state through the DCH or FACH.
Enhancement
None.
Dependency
None.

Issue V1.71 (2009-09-10) Page 38 of 145
5 Channel Resource Management
5.1 WRFD-020900 Logical Channel Management

Availability
Summary
This feature supports multiple logical channels to carry data transfer services offered by
MAC.
Benefits
This feature provides the basis for data transfer and resource management algorithm.
Description
A set of logical channel types are defined for different kinds of data transfer services offered
by MAC. Each logical channel type is defined by what type of information is transferred.
Generally, logical channels are classified into the following two groups:
z Control channels (for the transfer of control plane information).
z Traffic channels (for the transfer of user plane information).
Control channels are used for the transfer of control plane information. They are as follows:
z Broadcast Control Channel (BCCH)
z Paging Control Channel (PCCH)
z Common Control Channel (CCCH)
z Dedicated Control Channel (DCCH)
Traffic channels are used for the transfer of user plane information. They are as follows:
z Dedicated Traffic Channel (DTCH)
z Common Traffic Channel (CTCH)
z MBMS Traffic Channel (MTCH)
Mapping between logical channels and transport channels is as follows:
I. In Uplink,

Issue V1.71 (2009-09-10) Page 39 of 145
z CCCH can be mapped to RACH;

z DCCH can be mapped to RACH;
z DCCH can be mapped to DCH or E-DCH;
z DTCH can be mapped to RACH;
z DTCH can be mapped to DCH;
z DTCH can be mapped to E-DCH;
II. In Downlink,
z BCCH can be mapped to BCH;
z BCCH can be mapped to FACH;
z PCCH can be mapped to PCH;
z CCCH can be mapped to FACH;
z DCCH can be mapped to FACH;
z DCCH can be mapped to HS-DSCH;
z DCCH can be mapped to DCH;
z DTCH can be mapped to FACH;
z DTCH can be mapped to HS-DSCH;
z DTCH can be mapped to DCH;
z CTCH can be mapped to FACH;
z MTCH can be mapped to FACH;
z MCCH can be mapped to FACH;
The mapping between DTCH/DCCH and HS-DSCH/E-DCH belongs to the optional features
WRFD-010610 HSDPA Introduction Package and WRFD-010612 HSUPA Introduction
Package.
Enhancement
In RAN3.0, the CTCH supporting the cell broadcast service (CBS) feature is introduced.
In RAN6.0, the MTCH and MCCH are introduced.
Dependency
None.
5.2 WRFD-021000 Transport Channel Management

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

Issue V1.71 (2009-09-10) Page 40 of 145
Summary
This feature enables Huawei RAN to support the common transport channel and dedicated
transport channel as stipulated in 3GPP R6. This feature is a basic feature of RAN.
Benefits
This feature provides the basis for data transfer and resource management algorithm.
Description
Transport channel is used to offer information transfer services to MAC and higher layers.
It is generally classified into the following two groups:
z Common transport channels
z Dedicated transport channels
Common transport channel types are as follows:
z Random Access Channel (RACH)
z Forward Access Channel (FACH)
z Broadcast Channel (BCH)
z Paging Channel (PCH)
z High Speed Downlink Shared Channel (HS-DSCH)
Dedicated transport channel types are as follows:
z Dedicated Channel (DCH)
z Enhanced Dedicated Channel (E-DCH)
Enhancement
In RAN5.0, HS-DSCH supported with HSDPA feature is introduced.
In RAN6.0, E-DCH supported with HSUPA feature is introduced.
Dependency
NDLP and NBBI do not support the Management of HSUPA or HSDPA transport channel.
Dependency on other UTRAN software functions
To support the HSUPA transport channel Management, the optional feature WRFD-010612
HSUPA Introduction Package should be configured.
To support the HSDPA transport channel Management, the optional feature WRFD-010610
HSDPA Introduction Package should be configured.

Issue V1.71 (2009-09-10) Page 41 of 145
5.3 WRFD-022000 Physical Channel Management

Availability
This feature is introduced in 3GPP R99/R5/R6.
Summary
This feature enables Huawei RAN to support the physical channel and the mapping between
the transport channel and physical channel as stipulated in 3GPP R6. This feature is a basic
feature of RAN.
Benefits
In compliance with the definition and requirements of the physical channel as stipulated in
3GPP specifications, this feature supports HSDPA and HSUPA services and enables the
F-DPCH to support more VoIP subscribers.
Description
A physical channel may bear several transport channels and a transport channel may be borne
by several physical channels.
The Coded Composite Transport Channel (CCTrCH) is defined as the multiplexing of several
transport channels that can be supported by one or several physical channels on the radio
interface. Some physical channels are used only by the physical layer of the radio interface.
Only the following physical channels may bear transport channels:
z P-CCPCH: Primary Common Control Physical Channel
z S-CCPCH: Secondary Common Control Physical Channel
z PRACH: Physical Random Access Channel
z DPDCH: Dedicated Physical Data Channel
z HS-PDSCH: High Speed Physical Downlink Shared Channel
z E-DPDCH: E-DCH Dedicated Physical Data Channel
The following 3GPP Standards define the main characteristics of the FDD Physical Channels:
[1] TS25.211 Physical channels and mapping of transport channels onto physical channels
(FDD)
[2] TS25.212 Multiplexing and channel coding (FDD)
[3] TS25.213 Spreading and modulation (FDD)
[4] TS25.214 Physical layer procedures (FDD)
The set of physical channels types supported by the Huawei Node B is described in the
following tables. The characteristics of these supported physical channels are compliant with
3GPP TS25.211. Physical channels are carried on the radio interface only in the Node B of the
UTRAN, but are managed by the RNC.

Issue V1.71 (2009-09-10) Page 42 of 145
Channel Availability Direction Characteristics
PRACH RAN2.0 UL PRACH is used to carry the RACH which

Physical Common carries random access information of the UE
Random accessing the network.
Access It consists of one or several preambles of
Channel length 4096 chips and a message of length 10
ms or 20 ms. The spreading factor may range
from 256 to 32.
Uplink RAN2.0 UL The uplink DPDCH is used to carry the DCH
DPDCH Dedicated transport channel. There may be zero, one, or
Uplink several uplink DPDCHs on each radio link.
Dedicated The spreading factor may range from 256 to
Physical 4.
Data
Channel
Uplink RAN2.0 UL The uplink DPCCH is used to carry control
DPCCH Dedicated information generated at Layer 1. The Layer
Uplink 1 control information consists of TFCI, TPC,
Dedicated Pilot bits, FBI, which is required to convey
Physical DPDCH. There is one and only one uplink
Control DPCCH on each radio link.
Channel Generally, the spreading factor is equal to
256.
P-CCPCH RAN2.0 DL The Primary CCPCH is a fixed rate (30 kbps,
Primary Common SF=256) downlink physical channel used to
Common carry the BCH transport channel which
Control provides system and cell specific information.
Physical It is not transmitted during the first 256 chips
Channel of each timeslot because P-CCPCH is
multiplexed with SCH.
S-CCPCH RAN2.0 DL The Secondary CCPCH is used to carry the
Secondary Common FACH and PCH. The FACH and PCH can be
Common mapped to the same or separate Secondary
Control CCPCHs.
Physical The spreading factor range is from 256 to 4.
Channel It has no inner-loop power control and is not
always transmitted.
P-SCH RAN2.0 DL The P-SCH is used for cell search procedure
Primary Common (Slot synchronization).
Synchroniz This channel has no scrambles or OVSF
ation codes. It is multiplexed with P-CCPCH.
Channel
S-SCH RAN2.0 DL The S-SCH is used for cell search procedure
Secondary Common (SC group identification).
Synchroniz Not scrambled nor OVSF coded. It is
ation multiplexed with P-CCPCH.
Channel

Issue V1.71 (2009-09-10) Page 43 of 145
P-CPICH RAN2.0 DL The CPICH is a fixed rate (30 kbps, SF=256)

Primary Common downlink physical channel that carries a
Common pre-defined bit sequence.
Pilot The Primary CPICH is the phase reference
Channel for the following downlink channels: SCH,
Primary CCPCH, Second CCPCH, AICH,
PICH, and DPCH.
There is only one P-CPICH per cell. It is
always scrambled by the Primary SC.
PICH RAN2.0 DL The PICH is a fixed rate (SF=256) physical
Page Common channel used to carry the paging indicators.
Indication The PICH is always associated with an
Channel S-CCPCH (mapped with PCH) to carry the
Paging Indicators (PI) informing the UE that
paging information is available on the
SCCPCH.
AICH RAN2.0 DL The AICH is a fixed rate (SF=256) physical
Acquisition Common channel used to carry Acquisition Indicators
Indicator (AI). Acquisition Indicators corresponding to
Channel signatures on the PRACH are used by the
network to confirm to the UE the reception of
its access (PRACH).
Downlink RAN2.0 DL The downlink DPCH can be regarded as a
DPCH Dedicated time multiplex of a downlink DPDCH and a
Downlink downlink DPCCH. It carries dedicated data
Dedicated generated at Layer 2 and above (i.e. the
Physical dedicated transport channel DCH), with
Channel control information generated at Layer 1
(pilot bits, TPC commands, and TFCI).
The spreading factor may range from 512 to
4.
HS-DPCC RAN5.0 UL The HS-DPCCH carries uplink feedback
H Dedicated signaling related to downlink HS-DSCH
Dedicated transmission. It consists of HARQ-ACK and
Physical CQI.
Control The spreading factor of the HS-DPCCH is
Channel for 256
HS-DSCH
HS-SCCH RAN5.0 DL The HS-SCCH is a fixed rate (60 kbps,
Shared Common SF=128) downlink physical channel used to
Control carry downlink signaling related to
Channel for HS-DSCH transmission, including
HS-DSCH modulation mode, size of a transmission
block, redundant version information, UE ID,
and HS-PDSCH code.
HS-SCCH is aligned with the PCCPCH in
timing and keeps a fixed time offset with the
HS-PDSCH. Its spreading factor is fixed as

Issue V1.71 (2009-09-10) Page 44 of 145

128 and QPSK is the only modulation mode.
The number of HS-SCCHs and the channel
codes in the cell are determined by the RNC,
and are notified to the Node B through the
NBAP signaling message. When the Node B
sends the data to the UE through the
HS-PDSCH, the UE can detect one to four
HS-SCCHs that are specified by the Node B
at one time.
HS-PDSCH RAN5.0 DL The HS- PDSCH is used to carry HS-DSCH.
High Speed Common One HS-PDSCH corresponds to one
Physical channelization code with a fixed spreading
Downlink factor of SF16.
Shared The HS-PDSCH supports multi-code
Channel transmission. This means that in one
HS-PDSCH sub-frame, multiple
channelization codes can be used for one UE.
It also depends on the UE’s capability.
The HS-PDSCH adopts the QPSK or 16QAM
modulation mode.
E-DPDCH RAN6.0 UL The E-DPDCH is used to carry the E-DCH
E-DCH Dedicated transport channel. There may be zero, one, or
Dedicated several E-DPDCHs on each radio link.
Physical Its spreading factor set is {SF256, SF128,
Data SF64, SF32, SF16, SF8, SF4, 2×SF4, 2×SF2
Channel and 2×SF2+2×SF4}. In RAN 6.0, spreading
factor set {SF256, SF128, SF64, SF32, SF16,
SF8, SF4, 2×SF4,} can be supported.
E-DPCCH RAN6.0 UL The E-DPCCH is a physical channel used to
E-DCH Dedicated transmit control information associated with
Dedicated the E-DCH. There is at most one E-DPCCH
Physical on each radio link.
Control The spreading factor is always equal to 256.
Channel
E-AGCH RAN6.0 DL E-AGCH is a common downlink physical
E–DCH Common channel, which carries the maximum power
Absolute ratio of E-DPDCH/DPCCH that can be used
Grant by the UE. It is only sent from the serving
Channel cell that the serving radio link of the UE
belongs to. An E-AGCH is shared by many
users in time dimension and the adjustment
procedure is usually at slow speed.
The spreading factor of E-AGCH is 256, and
the fixed rate of E-AGCH is 30 kbit/s.
E-RGCH RAN6.0 DL E-RGCH is a dedicated downlink physical
E-DCH Dedicated channel, which carries the relative grant value
Relative for modifying power ratio of

Issue V1.71 (2009-09-10) Page 45 of 145

Grant E-DPDCH/DPCCH, it is used to frequently
Channel adjust the UE uplink transmit power, which
could happen per 2ms TTI.
E-RGCH and E-HICH of a user share the
same channel code with spreading factor 128,
and one channel code for E-RGCH and
E-HICH can be spread again with 40
orthogonal signature sequences, which
extends the usage of the downlink channel
code.
E-HICH RAN6.0 DL E-HICH is a dedicated downlink physical
E-DCH Dedicated channel, which carries the E-DCH hybrid
Hybrid ARQ acknowledgement indicator such as
ARQ ACK/NACK; the acknowledgement indicator
Indicator informs UE whether the data for a user
Channel process is received correctly or not in the
Node B.
MICH RAN6.0 DL The MBMS Indicator Channel (MICH) is a
Common fixed rate (SF=256) physical channel used to
carry the MBMS notification indicators. The
MICH is always associated with an
S-CCPCH to which a FACH transport
channel is mapped.
F-DPCH RAN10.0/RA F-DPCH is a shared channel which only
N11.0 carries the UE specific TPC bits so that the
A-DCH can be replaced by a shared channel
to save the code and power resource.
Replacing A-DPCH with F-DPCH will boost
the capacity for VoIP traffic in DL.
RAN11.0 supports Rel-7 F-DPCH, so UE can
receive the TPC bits in different F-DPCH
channels in soft handover status, to maximize
the user capacity in F-DPCH.
The following figure summarizes the mapping of transport channels onto physical channels.

Issue V1.71 (2009-09-10) Page 46 of 145
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:
z HS-DPCCH, Dedicated Physical Control Channel for HS-DSCH
z HS-SCCH, Shared Control Channel for HS-DSCH
z HS-PDSCH, High Speed Physical Downlink Shared Channel
In RAN6.0, HSUPA is supported, and the following channels are added:
z E-DPDCH, E-DCH Dedicated Physical Data Channel
z E-DPCCH, E-DCH Dedicated Physical Control Channel
z E-AGCH, E–DCH Absolute Grant Channel
z E-RGCH, E-DCH Relative Grant Channel
z E-HICH, E-DCH Hybrid ARQ Indicator Channel
z MICH, MBMS Indicator Channel
In RAN10.0, the F-DPCH is added.
Dependency

Issue V1.71 (2009-09-10) Page 47 of 145
NDLP and NBBI do not support the HSUPA or HSDPA physical channel.
To support the F-DPCH, the macro Node B (BTS3812E or BTS3812AE) should be
configured with the EBBI or EBOI and the distributed Node B (BBU3806) should be
configured with the EBBC.
To support HSUPA physical channel, the optional feature WRFD-010612 HSUPA
Introduction Package should be configured.
To support HSDPA physical channel, the optional feature WRFD-010610 HSDPA
Introduction Package should be configured.
5.4 WRFD-021101 Dynamic Channel Configuration

Control (DCCC)
Availability
Summary
This feature provides dynamic rate re-allocation and UE state transition that can be triggered
by multiple sources, thus ensuring QoS and improving resource utilization.
Benefits
This feature can improve the efficiency of radio resource allocation and maintain the stability
of radio link.
Description
Dynamic channel configuration control (DCCC) consists of rate re-allocation and UE state
transition function:
z 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

Issue V1.71 (2009-09-10) Page 48 of 145
According to the downlink quality, including downlink transmit power and RLC status, rate
re-allocation can decrease the downlink data rate, to reduce the negative impact concerned
with coverage.
According to the uplink quality, including UE Tx power, the RNC can adjust the UL rate
during the call by means of UL bit rate switching to adapt to UE power limitations.
III. Load based
Rate re-allocation can be triggered by load control. The load can be power load and code
resource. The congestion thresholds are independent and configurable. This feature is a
strategy of WRFD-020106 Load Reshuffling.
z UE State Transition
UE state transition is supported between the CELL_DCH, CELL_FACH, and
CELL_PCH/URA_PCH state according to both uplink and downlink traffic volume
measurement. It can also be used to improve the efficiency of resource allocation between
dedicated and common channels.
DCCC is also applied to HSDPA/HSUPA (rate re-allocation is not applied to HSDPA because
the data scheduler locates in the Node B). For details, please refer to optional features
WRFD-01061111 HSDPA State Transition and WRFD-01061208 HSUPA DCCC.
Enhancement
In RAN6.0, the code resource based DCCC is supported.
In RAN10.0, the UL bit rate downsizing due to the UE power limitation is supported.
In RAN10.0, the UL/DL bit rate downsizing based on DCH throughput is supported.
Dependency
None.
6 Network Security
6.1 WRFD-011401 Integrity Protection

Availability

Issue V1.71 (2009-09-10) Page 49 of 145
Summary
This feature is concerned with integrity protection. The integrity protection mechanism can
ensure the security of the network and user data and protect them from being monitored and
modified illegally.
Benefits
This feature enhances network and user data security, and protects the data and networks from
being intercepted and modified illegally.
Description
The Integrity protection handles the control of integrity protection of signaling data and the
co-ordination of integrity keys between different core networks (PS and CS). It enables
receiving entity (the UE or the RNC) to verify if the signaling data is changed illegally. It
encrypts and decrypts the signaling data using a certain integrity algorithm with an integrity
key (IK).
Huawei RAN supports integrity algorithm UIA1.
Enhancement
None.
Dependency
None.
6.2 WRFD-011402 Encryption

Availability
Summary
This feature supports the encryption algorithms (UEA0 and UEA1) as defined in 3GPP
specifications.
Benefits
This feature enhances network and user data security, and protects the data and networks from
being intercepted and modified illegally.

Issue V1.71 (2009-09-10) Page 50 of 145
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.

Issue V1.71 (2009-09-10) Page 51 of 145
7 Power Control
7.1 WRFD-020501 Open Loop Power Control

Availability
Summary
This feature is concerned with open loop power control as defined in 3GPP specifications.
Open loop power control roughly estimates the path loss through power measurements,
network parameter settings, and QoS requirements and then provides a proper initial transmit
power for the UE and Node B.
Benefits
The proper initial power setting can decrease the possibility of burst interference to the
network and improve the performance of the inner power control.
Description
Open loop power control attempts to make a rough estimation of path loss by means of power
measurements, network parameter setting, and QoS requirement, and to provide a proper
initial power used by the UE and Node B.
Open loop power control is applied on the uplink PRACH and DPCH and the downlink
DPCH. The other downlink common channel’s initial power is set by the network.
In the case of the PRACH, the UE calculates the initial transmit power of PRACH preamble
by estimating the downlink path loss and using the uplink inference within the cell broadcast
information.
In the case of the uplink DPCCH transmission, the initial power is calculated in the same
manner as PRACH, except that the power offset is different and is provided by RRC message.
In addition, uplink DPDCH transmit power can be calculated with the gain factors signaled by
the network.
In the case of the downlink DPCH, the DPDCH transmit power is firstly estimated according
to the RAB QoS assigned and the network configured parameters, the transmit power of each
DPCCH part TFCI, TPC and pilot can be calculated by the network controlled power offset
(PO1/PO2/PO3) setting.

Issue V1.71 (2009-09-10) Page 52 of 145
Open power control is used in the following scenarios which require an initial power on the
newly added radio link.
z RRC connection setup
z Radio link addition in soft handover
z Hard handover
z Relocation
z Channel type switching
Enhancement
None.
Dependency
None.
7.2 WRFD-020502 Downlink Power Balance

Availability
Summary
This feature is related to downlink power balance as defined in 3GPP specifications.
Downlink power balance can solve the problem of downlink power drift caused by TPC bit
errors and link power imbalance in soft handover state to obtain the optimal gain of soft
handover.
Benefits
Downlink power balance can decrease the transmit power drifting of different RLs and
improve soft handover performance accordingly.
Description
During soft handover, the UL TPC command is demodulated in each RLS and due to
demodulation errors, the difference between the initial transmit power of newly added RL and
existing RL may lead to the drifting of transmit power. The more DL transmit power drifting,
the less the macro-diversity gain.
Downlink power balance is used to correct the transmit power drifting in such scenarios and
improve soft handover performance accordingly.
In the downlink, the Node B calculates the transmit power after considering TPC commands
sent by UE and the reference power set by the network. When the drifting of transmit power
is too much, the network updates the reference power to decrease the power difference of
different RLs.

Issue V1.71 (2009-09-10) Page 53 of 145
Enhancement
None.
Dependency
None.
7.3 WRFD-020503 Outer Loop Power Control

Availability
Summary
This feature is related to outer loop power control as defined in 3GPP specifications. Outer
loop power control is used to maintain the communication quality to the level required by the
service bearer through adjustment of the SIR target of the inner loop power control.
Benefits
Outer loop power control is used to set the proper SIR target used for uplink inner loop power
control and improve the uplink performance.
Description
Outer loop power control is to maintain the communication quality at the level required by the
service bearer through adjustment of the SIR target. This operation is performed on each DCH
belonging to the same RRC connection.
Outer loop power control consists of downlink outer loop power control and uplink outer loop
power control. The purpose of downlink power control is to maintain the proper SIR target
used in the downlink inner loop power control, based on the implementation of UE algorithms.
The power of the UE must meet the requirement for the downlink BLER of the RB. The
purpose of the uplink power control is to maintain the proper SIR target used in the uplink
inner power control.
In the case of uplink outer loop power control, the SRNC first gets the uplink quality after
macro diversity selection combining, and then the SRNC compares the RX BLER with the
BLER target. If the RX BLER is higher than the BLER target, the SRNC increases the SIR
target; otherwise, it decreases the SIR target. If BLER is not available, BER is used. After
adjusting the SIR target, the SRNC sends the new SIR target through FP frames to all Node
Bs for uplink inner loop power control.
The initial SIR target provided by the RNC to the Node B is service-dependent and it is
updated by the uplink quality measurement of each DCH in the following phases.
Enhancement
None.

Issue V1.71 (2009-09-10) Page 54 of 145
Dependency
None.
7.4 WRFD-020504 Inner Loop Power Control

Availability
Summary
Inner loop power control enables the Node B and UE to adjust their transmit powers in time.
Inner loop power control consists of uplink power control and downlink power control.
Benefits
Inner loop power control adjusts the uplink power and downlink power so that they are
minimum while the QoS is guaranteed, thus increasing the system capacity. It can also be
used to prevent shadow fading and fast fading.
Description
Inner loop power control is also called fast closed-loop power control and applied to only the
dedicated channel. It controls the transmit power according to the information returned from
the peer physical layer. The UE and the Node B can adjust the transmit power according to
the RX SIR of the peer end to compensate for the fading of radio links.
Inner loop power control consists of uplink inner loop power control and downlink inner loop
power control, and they work independently.
The uplink inner loop power control is used to adjust the UE transmit power by TPC
commands received from the Node B. The fast and slow power control algorithms (PCAs) are
defined in 3GPP specifications. PCA1 is the fast power control through which the UE adjusts
the transmit power for each timeslot. PCA2 is the slow power control through which the UE
adjusts the transmit power for five timeslots. PCA2 can lower the power control frequency
from 1500 times/s to 300 times/s maximally. The operator can decide which PCA is chosen in
the RRC messages. The downlink inner loop power control is used to adjust the Node B
transmit power by TPC commands received from the UE.
Downlink inner loop control involves the following two modes:
DPC0 mode: In DPC0 mode, the UE sends TPC commands for each timeslot.
DPC1 mode: In DPC1 mode, the UE sends TPC commands for three timeslots. The operator
can decide which DPC mode is used by RRC signaling.
Enhancement
None.

Issue V1.71 (2009-09-10) Page 55 of 145
Dependency
None.

Issue V1.71 (2009-09-10) Page 56 of 145
8 Cell Management
8.1 WRFD-020101 Admission Control

Availability
Summary
This feature can combine multiple resources to perform admission control over R99 service
requests, thus ensuring QoS and system resource allocation.
Benefits
This feature maximizes system capacity while ensuring QoS requirements and improves
network stability.
Description
Admission control is used to improve the resource usage efficiency and RRC/RAB setup
success rate. The following four types of resources are admitted:
z Cell available code resource
z Cell available power resource
z Node B resource state, that is, Node B credits
z 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:
z Algorithm 1
Power resource admission decision based on power or interference

Issue V1.71 (2009-09-10) Page 57 of 145
The RNC decides whether the cell load exceeds the threshold or not when admitting a
new call based on the current cell load (uplink load factor and downlink TCP) and the
access request. If the cell load exceeds the threshold, the RNC rejects the request. If the
cell load does not exceed the threshold, the RNC accepts the request.
z Algorithm 2
Power resource admission decision based on the equivalent number of users.
The RNC decides whether the equivalent number of users exceeds the threshold or not
when admitting a new call based on the current equivalent number of users and the
access request. If the equivalent number of users exceeds the threshold, the RNC rejects
the request. If the equivalent number of users does not exceed the threshold, the RNC
accepts the request.
z Algorithm 3
It is similar to algorithm 1, but the predicted required power of a new call is set to zero.
Four basic load thresholds are used to decide the admission. They are as follows:
− Handover admission threshold
− AMR conversational service admission threshold
− Non AMR conversational service admission threshold
− Other service admission threshold
With the preceding thresholds, the RNC can define the proportion between speech service and
other services with the handover preference guaranteed.
III. Node B credit
The Node B credit admission includes the following:
z Local cell level admission decision
z Local cell group level admission decision (if any)
z Node B level admission decision
Services can access the network only after all admission decisions are taken
For details about local cell, local cell group, and capacity consumption law, see 3GPP TS
25.433.
According to the common and dedicated channels capacity consumption laws, and the
addition, removal, and reconfiguration of the common and dedicated channels, the controlling
RNC (CRNC) debits the amount of the credit resource consumed or credits the amount to the
capacity credit of the local cell (and local cell group, if any) based on the spreading factor.
If the UL capacity credit and DL capacity credit are separate, the maintenance on the local cell
(and local cell group, if any) is performed in UL and DL respectively.
If the UL capacity credit and DL capacity credit are not separate, only the maintenance on the
global capacity credit is performed for the local cell (and local cell group, if any).
IV. Iub transport layer resource
Different services have different QoS requirements. Therefore, differentiated transmission
must be applied according to the service QoS requirements. The mapping relation between
service and transport resources can be configured.
The principles of Iub bandwidth admission control are described as follows:
I. Each type of path can be configured with the total bandwidth of the physical port to which
the path is connected. Thus, the total bandwidth of all paths that connect to the port may

Issue V1.71 (2009-09-10) Page 58 of 145
exceed the physical bandwidth of the port. Therefore, the following two levels of admission
are necessary:
z Admission control on the path level
z Admission control on the port level
II. Traffic congestion and bearer congestion are considered. For admission, the only factor
that needs to be considered is the Iub resources corresponding to the traffic class.
III. The primary path takes priority over the secondary path during admission. The secondary
path is tried when the admission attempt for the primary path fails.
The admission control also applies to HSDPA/HSUPA. Please refer to optional features
WRFD-01061003 HSDPA Admission Control and WRFD-01061202 HSUPA Admission
Control.
In the admission control procedure, some other features can be used to improve the access
success rate. That is, the feature Rate Negotiation at Admission Control (WRFD-010507) can
be used to decide the proper resource request based on the cell load. When the admission fails,
Queuing and Pre-Emption (WRFD-010505), DRD Introduction Package (WRFD-020400)
can be used to maximize the possibility of access to the system.
Enhancement
In RAN5.0, AMR and Non-AMR threshold for power load admission is divided.
In RAN6.0, algorithm 3 for power load admission is introduced.
In RAN6.0, resource reserved for handover is supported to decrease the call failure due to the
admission failure during the handover.
In RAN10.0, The PS service is admitted by judging the resource for GBR while in the
previous version the MBR is employed. By this means, the cell resources are better utilized.
Dependency
None.
8.2 WRFD-020102 Load Measurement

Availability
This feature is introduced in 3GPP R99.
Summary
This feature is related to load measurement for load control.
Benefits
Load measurement is the base of the related load control features including admission control,
load reshuffling, overload control, and potential user control features. On the other hand,

Issue V1.71 (2009-09-10) Page 59 of 145
operators can also control these strategies by configuring load measurement parameters like
measurement period, hysteresis, and so on.
Description
Algorithms such as OLC and CAC use load measurement values in the uplink and the
downlink. A common load measurement (LDM) algorithm is required to control load
measurement in the uplink and downlink, which makes the algorithm relatively independent.
The LDM algorithm has the following functions:
z 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.
z Delay susceptibilities of PUC, CAC, LDR, and OLC to common measurement are
different. When some or all the algorithms use the same common measurement, the
LDM must apply different smoothed filter coefficients to get rippling and timely
common measurement as required.
The major related measurement quantities are defined in 3GPP TS25.433 as follows:
z Uplink RTWP (Received Total Wideband Power)
z Downlink TCP (Transmit Carrier Power)
z Transmitted carrier power of all codes not used for HS-PDSCH or HS-SCCH
transmission
z Provided bit rate (PBR) on HS-DSCH
z Power requirement for GBR (Guaranteed Bit Rate) on HS-DSCH.
The preceding measurements focus on radio power load. For other resource load, the related
measurements include the following:
z For Iub load: Iub used bandwidth rate on PVC level.
z For code resource: The maximum rate can be supported with the minimum available SF
Enhancement
In RAN6.0, the load measurement of code resource is introduced, and therefore load
reshuffling can also be triggered by code congestion.
Dependency
None.
8.3 WRFD-020106 Load Reshuffling

Availability

Issue V1.71 (2009-09-10) Page 60 of 145
Summary
This feature provides multiple load reshuffling policies for the cell in basic congestion state to
decrease the cell load and increase the access success rate.
Benefits
This feature decreases the cell load when resource load enters the basic congestion state, and
therefore, improves the stability and capability of the network.
Description
When the usage of cell resource exceeds the congestion trigger threshold, the cell enters the
basic congestion state. In this case, LDR (Load Reshuffling) is required to reduce the cell load
and increase the access success rate. When the load is lower than the congestion release
trigger threshold, the system returns to normal.
The resources that can trigger basic congestion of the cell include:
z Power resource
z Iub resource or Iub bandwidth
z Code resource
z Node B credit resource
z Equivalent user number
The Iub resource and credit resource congestion control in both uplink and downlink is Node
B oriented. Load trigger threshold and load release threshold are set for the uplink and
downlink separately.
The function of the LDR is to reduce the load of a cell when the available resource of the cell
reaches the threshold. The introduction of the LDR is to increase the access success rate in the
following ways:
z Inter-frequency load handover
z Code reshuffling
z BE service rate reduction
z Uncontrolled real-time traffic QoS renegotiation
z CS domain inter-RAT load handover
z PS domain inter-RAT load handover
z Downsizing the bit rate of AMR voice
z MBMS power downgrading
Among the preceding features, the best effort service rate reduction and code reshuffling are
the basic features, and the others belong to the optional features.
Enhancement
In RAN5.0, optional feature Iu re-negotiation is introduced as one of the load reshuffling
strategies.
In RAN5.0, priority based load reshuffling is supported.
In RAN5.1, optional feature AMRC is introduced as one of the load reshuffling strategies.

Issue V1.71 (2009-09-10) Page 61 of 145
In RAN6.0, besides radio power resource and Iub resource, load reshuffling is extended to
other resource congestion including code resource, credit resource, and equivalent user
number.
In RAN6.0, load reshuffling can also be applied to HSDPA, HSUPA, and MBMS services. In
addition, gold user should not be affected during the load reshuffling.
In RAN6.0, code reshuffling and MBMS power downgrading are added as new strategies of
load reshuffling.
In RAN10.0, the feature is enhanced by the following:
z Uplink load reshuffling triggered by power resource can be applied in an HSUPA cell.
z Inter-frequency load balancing triggered by CE resource and Iub transmission resource
congestion are canceled in RAN10.0. The reason is that the target cell is probably under
the same Node B and in this condition the handover cannot alleviate the congestion.
z When the cell is under LDR status, the PS services whose data rate is above GBR are
forbidden to increase the data rate while the services whose data rate is below GBR are
allowed to increase their data rate to GBR.
z A switch is provided to control whether gold user is selected during the load reshuffling.
Dependency
None.
8.4 WRFD-020107 Overload Control

Availability
Summary
This feature provides multiple load adjustment means for the cell in overloaded state to fast
decrease the cell load.
Benefits
Overload control guarantees system stability:
z The cell overload control quickly reduces cell load when the power resource is
overloaded in the cell.
z Overload control of Iub transmission avoids the lack of Qos protection for current
services caused by Iub transmission overload after a sudden decrease of bandwidth.
Description
Overload control (OLC) is a way to rapidly reduce the cell load when a cell is overloaded. For
the overloaded cell, the cell load exceeds the overload threshold. In this case, overload control
can effectively decrease the cell load and maintain system stability. The OLC action stops
when the cell load is lower than the overload recovery threshold.
The resources used to trigger overload control include power and Iub transmission bandwidth.

Issue V1.71 (2009-09-10) Page 62 of 145
1. Power
When the power resource of a cell is overloaded, OLC performs the following functions:
z Restricts the transport format of BE service
z Send some BE services from DCH to Cell FACH
z Releases some UEs
2. Iub transmission bandwidth
When the RNC detects Iub transmission overload caused by the change of Iub transmission
bandwidth (for example, IMA link fault of the IMA group in ATM mode), overload control
releases some UEs to quickly reduce the Iub traffic flow.
Overload control chooses the UEs in the sequence of lower-to-higher priorities.
Enhancement
RAN5.0 supports priority-based overload control.
RAN11.0 supports control of Iub transmission overload caused by the change of Iub
transmission bandwidth.
Dependency
None.
8.5 WRFD-020108 Code Resource Management

Availability
Summary
This feature provides the allocation and reshuffling of downlink code tree resources. Code
resource management enables the proper allocation of code resources, thus improving
resource utilization.
Benefits
The code management algorithm can improve code usage efficiency, and optimize the code
allocation when too much code fragments are founded.
Description
Code resource management consists of code allocation and code re-allocation features and it
is only applied to the downlink code tree resource.
To optimize the code usage efficiency, the “left most” algorithm is adopted in code allocation
procedure, that is, the code with minimum SF is reserved to ensure that the codes are
available for use continuously.

Issue V1.71 (2009-09-10) Page 63 of 145
When the assigned AMR speech bit rate is less than 7.95 Kbit/s, the allocated SF is 256
instead of 128 to save the code resource, and therefore, the capacity is increased.
Code reshuffling algorithm is also used as one of the load reshuffling strategies and is used to
decrease the code fragments. That is, when detecting that the maximum coding rate is lower
than the threshold, the RNC reallocates the codes in the code tree to reduce code fragments as
many as possible.
Enhancement
In RAN6.0, allocation of code with SF 256 when the assigned AMR speech bit rate is less
than 7.95 Kbit/s is supported.
In RAN6.0, code re-allocation algorithm is introduced as one of the load reshuffling strategies
triggered by code congestion.
Dependency
None.

Issue V1.71 (2009-09-10) Page 64 of 145
9 Network Sharing
9.1 WRFD-021301 Shared Network Support in Connected

Mode
Availability
Summary
This feature enables the RNC to obtain shared network parameters and work with the CN to
apply the access control over the UE in connected mode to the specified location area. This
feature can support operation applications for network sharing solutions.
Benefits
With this feature, the RNC can prevent UE in connected mode from moving to an
un-subscribed area. It is also a supplement feature for implementing shared networks
solutions.
Description
Based on R99 specifications, when the UE is in idle mode, the CN+UTRAN have
mechanisms available to provide UE-specific access restrictions for LAs of the current PLMN
and other PLMNs by using roaming agreement. But there is no mechanism to restrict UE
behavior in connected mode, since UTRAN does not have enough information to handle the
UE as CN does to UE in idle mode. Accordingly, this feature is introduced in 3GPP R5 and
used to provide an access restriction mechanism for UE in connected mode.
To support this function, the RNC obtains the parameters of the shared network support in
connected mode from the messages and information elements (IE), which are defined in
3GPP TS 25.413 and 25.423 including:
z 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.
z The information of the SNAs that the LAs belong to, which is from CN through
INFORMATION TRANSFER message or from DRNC through RADIO LINK SETUP
RESPONSE and UPLINK SIGNALING TRANSFER messages.
Each LA belongs to one or several shared network area (SNA), and one UE can belong to one
or several SNAs. Based on the information, the RNC decides whether the UE is allowed to
get services in the new network or not according to the information.
The following procedures have connection with this feature:
z Cell update
When the UE initiates cell update in the destination cell, the RNC decides whether the
UE is allowed to access the destination cell.
If the UE is not allowed to access the destination cell, the cell update fails.
z URA update
The URA update is the same as the cell update.
z 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.
z Relocation
When the target RNC (TRNC) receives a RELOCATION REQUEST message, it decides
whether the UE is allowed to access the destination cell.
If the UE is not allowed to access the destination cell, the relocation failure procedure is
triggered.
z Handling common ID message
The RNC obtains the IMSI information of the UE in the common ID message and
decides whether the UE is allowed to access the current cell. If the UE is not allowed to
access the current cell, the RRC connection is released.
Enhancement
None.
Dependency
CN must support this feature. When the Iur interface is used, the RNC connected over the
interface must also support this feature.
9.2 MRFD-210104 BSC/RNC Resource Sharing

Availability
This feature is available from GBSS9.0 and RAN10.0.
Summary
This feature provides the resource sharing of the user plane and control plane in the MBSC by
adopting the intra-subrack/inter-subrack load sharing mechanism of boards.

Issue V1.71 (2009-09-10) Page 66 of 145
Benefits
This feature improves the resource utilization and increases the call success rate. It also
maximizes the capacity usage in different traffic modes.
Description
The BSC/RNC Resource Sharing feature is classified into user plane resource sharing and
control plane resource sharing.
Control plane resource sharing applies to CPU usage and memory. When the CPU usage of a
certain signaling processing unit is too high or when the memory of a certain signaling
process unit is insufficient, the new call is transferred to other signaling processing unit with a
low load.
User plane resources are shared dynamically within the system based on resource pool and
load sharing. If a certain user plane processing unit is overloaded, the new traffic can be
allocated to other user plane processing unit with lower load.
For the MBSC, the service type-based resource pools are as follows: GSM control plane
resource, GSM user plane resource, UMTS control plane resource, and UMTS user plane
resource. The resource sharing within the pool is supported, but the resource sharing between
pools is not supported.
Enhancement
None.
Dependency
None.
None.
None.
None.

Issue V1.71 (2009-09-10) Page 67 of 145
10 Mobility Management
10.1 WRFD-020201 Intra Node B Softer Handover

Availability
Summary
This feature is concerned with intra-Node B softer handover. The intra-Node B softer
handover can provide a higher combination gain (maximum combination) and reduce the
occupation of transmission resources on the Iub interface.
Benefits
Soft handover provides seamless connection services for mobile users. Besides these, the intra
Node B softer handover uses maximum-ratio combination on the uplink in the Node B to
increase the gain of combination. It also saves Iub bandwidth resources.
Description
Soft handover is a procedure in which at least one radio link is maintained between the UE
and UTRAN when the setup or release of radio links are being performed. Soft handover
occurs only within the intra-frequency cells. Since adjacent cells have the same frequency, UE
can connect to the network through multiple radio links to improve the communication quality.
UE can perform smooth handover from one cell to another without interrupting the
communication with the original cell.
On the other hand, soft handover may lead to the occupancy of Iub resource since multiple
radio links exist.
The size of active set can be up to six and can be configured. The RNC can decide SHO
according to either Ec/N0 or RSCP. The parameters set for SHO can be independent of CS
and PS services. The parameter CIO can also be configured for different cells for event
evaluation.
The intra Node B softer handover is a kind of soft handover. It sets up RLs in the sectors
within a Node B and the data received on these RLs is combined in the Node B using
maximum-ratio combination before being forwarded to the RNC. Therefore, softer handover
will occupy no more Iub transmission resource compared with soft handover.

Issue V1.71 (2009-09-10) Page 68 of 145
The RNC can control whether the intra Node B softer handover should be implemented by
setting the RL ADDITION REQUEST in the NBAP message.
Neighboring cell combination is supported, which means the neighboring cells to be
measured are selected from all the neighboring cells of active set and the priority of the
neighboring cell is configurable. Neighboring cell combination is applied to soft/softer
handover, hard handover, and inter-RAT handover.
Enhancement
In RAN5.1, the neighboring cell combination is supported.
Dependency
None.
10.2 WRFD-020202 Intra RNC Soft Handover

Availability
Summary
This feature is concerned with intra-RNC soft handover. Compared with the intra-Node B
softer handover, the intra-RNC soft handover has a wider application scope. The intra-RNC
soft handover enables macro diversity combination and each RL has its own transport bearer
on the Iub interface.
Benefits
The intra-RNC soft handover provides seamless connection services for mobile users within
the RNC.
Description
The intra RNC soft handover is a kind of soft handover. It sets up RLs in different Node Bs or
in the same Node B within the RNC. The difference between the intra-Node B softer
handover and the intra-RNC soft handover lies on where the combination is performed. The
intra-RNC soft handover performs macro diversity combination in the RNC, which means
each RL has its own transport bearer on Iub interface.
Enhancement
In RAN5.1, neighboring cell combination is supported.
Dependency
None.

Issue V1.71 (2009-09-10) Page 69 of 145
10.3 WRFD-020203 Inter RNC Soft Handover

Availability
Summary
This feature is concerned with inter-RNC soft handover. The inter-RNC soft handover enables
the establishment of an RL on the DRNC and the macro diversity combination on the SRNC
through the Iur interface.
Benefits
The inter RNC soft handover provides seamless connection services for mobile users.
Compared with other kinds of soft handovers, the inter RNC soft handover increases the
range of soft handover to the RNCs which have Iur connections with a certain RNC.
Description
The inter RNC soft handover is a kind of soft handover. It sets up RLs in different RNCs and
the macro diversity combination is completed through Iur interface by the SRNC. The uplink
data is transmitted from the DRNC to the SRNC. The SRNC combines data from its own cells
and cells of the DRNC. This is the key difference from other soft handovers.
Enhancement
RAN5.1 supports the neighboring cell combination.
Dependency
The Iur interface is configured between adjacent RNCs.
10.4 WRFD-020301 Intra Frequency Hard Handover

Availability
Summary
This feature is concerned with intra-frequency hard handover. When the soft handover fails,
the RNC enables the UE to move between cells through hard handover.

Issue V1.71 (2009-09-10) Page 70 of 145
Benefits
Intra frequency hard handover applies in the scenarios where intra frequency soft handover
can not be used.
Description
Hard handover is characterized by the handover procedure in which the old connection is
released before a new connection is set up. Intra frequency hard handover means hard
handover between cells of the same frequency. It is used in any of the following scenarios:
z 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.
z Not enough Iur interface transmission resource available
In this case, the soft handover between RNCs is also unavailable, and the hard handover
with CN switching between the two RNCs occurs.
z High-speed BE service
For the high-speed BE service, intra-frequency hard handover can be used to save
downlink capacity, compared with soft handover.
z Intra-frequency soft handover fails and intra-frequency hard handover is allowed
When intra-frequency soft handover fails due to the target cell congestion,
intra-frequency hard handover can be tried with lower service bits rate.
Enhancement
In RAN5.1, neighboring cell combination is supported.
Dependency
None.
10.5 WRFD-010801 Intra RNC Cell Update

Availability
Summary
This feature is related to intra-RNC cell update as stipulated in 3GPP specifications. The
intra-RNC cell update procedure can be triggered by events.
Benefits
Cell update enables UTRAN to manage a UE’s behavior and enables UE to update its state
when its service or location changes.

Issue V1.71 (2009-09-10) Page 71 of 145
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:
z Periodical cell update
UE sends Cell Update message to RNC periodically when it is in CELL_FACH or
CELL_PCH state. This can be used by RNC to monitor the RRC connection.
z Cell reselection
If a UE in CELL_FACH or CELL_PCH state reselects a new cell, the UE starts the
procedure. When receiving the message CELL_UPDATE, RNC updates the UE camping
cell information.
z Paging response
If a UE in URA_PCH or CELL_PCH state receives a PAGING TYPE 1 message, the UE
starts the procedure. RNC then transmits the UE’s state to CELL_FACH or CELL_DCH.
z Uplink data transmission.
If a UE is in URA_PCH or CELL_PCH state and has data to transmit, the UE starts the
CELL UPDATE procedure to request for uplink data transmission. The RNC will
transmit its state to CELL_FACH subsequently.
z Radio link failure
If a UE in CELL_DCH state detects that the criteria for radio link failure are met, the UE
starts the procedure. The RNC deletes the current radio link and re-establishes a new
one.
z Re-entering service area
If a UE moves out of the service area, and then re-enters the service area, the UE starts
the procedure. Then RNC updates the camping cell of the UE.
z RLC unrecoverable error
If a UE detects an RLC unrecoverable error in an AM RLC entity, the UE starts the
procedure. The RNC releases the RRC connection of the UE or re-establishes the RB
according to the attributes of the RB. If it belongs to signal RB, the RRC connection is
released.
Enhancement
None.
Dependency
None.
10.6 WRFD-010802 Inter RNC Cell Update

Availability

Issue V1.71 (2009-09-10) Page 72 of 145
Summary
This feature is related to inter-RNC cell update as stipulated in 3GPP specifications. The
inter-RNC cell update procedure can be triggered by events.
Benefits
Cell update enables UTRAN to manage a UE’s behavior and enables UE to update its state
when its service or location changes. The inter RNC cell update feature increases the range of
cell update through Iur interface.
Description
Cell update is mainly used to update the UE information on the network side when the UE’s
location or behavior is changed. The inter RNC cell update means cell update between RNCs.
The cause of the inter RNC cell update is the same as the intra RNC cell update. The
difference between them is that in the inter RNC cell update, the CELL UPDATE message is
first received by the DRNC and forwarded to the SRNC, the SRNC then takes necessary
actions according to the cause within CELL UPDATE, for example, relocation.
Enhancement
None.
Dependency
10.7 WRFD-010901 Intra RNC URA Update

Availability
Summary
This feature is concerned with intra-RNC URA update as stipulated in 3GPP specifications.
The intra-RNC URA update procedure can be triggered by events.
Benefits
URA update enables UTRAN to monitor the RRC connection and manage the behaviors of
the UE in URA_PCH state.

Issue V1.71 (2009-09-10) Page 73 of 145
Description
User registration area (URA) update procedure updates the UTRAN registration area of a UE
when an RRC connection exists and the position of the UE is known on URA level in the
UTRAN. The intra RNC URA update means URA update within the RNC.
URA update may be triggered by the following two causes:
z Periodical URA update
The UE sends the URA update message to the RNC periodically when it is in URA_PCH
state. This can be used to monitor the RRC connection.
z URA reselection
If the UE in URA_PCH state enters a new URA, the UE starts the procedure, and the
RNC updates the camping URA of the UE accordingly.
Enhancement
None.
Dependency
None.
10.8 WRFD-010902 Inter RNC URA Update

Availability
Summary
This feature is related to inter-RNC URA update as stipulated in 3GPP specifications. The
inter-RNC URA update procedure can be triggered by events.
Benefits
The URA update enables UTRAN to monitor the RRC connection and manage the behaviors
of the UE in URA_PCH state. The inter RNC URA update increases the range of URA
Update through Iur interface.
Description
URA update procedure updates the UTRAN registration area of a UE when a RRC connection
exists and the position of the UE is known on URA level in the UTRAN. The inter RNC URA
update means the URA update between RNCs. Similar to the intra RNC URA update, a UE in
URA_PCH state also initiates the URA update procedure in two cases, URA reselection and
periodic URA update. The difference between the intra RNC and the inter RNC URA updates
is that in the inter RNC URA update, the URA UPDATE message is first received by the
DRNC and forwarded to the SRNC, the SRNC then takes necessary actions according to the
cause of the URA update, for example, relocation.

Issue V1.71 (2009-09-10) Page 74 of 145
Enhancement
None.
Dependency
10.9 WRFD-021400 Direct Signaling Connection

Re-establishment (DSCR)
Availability
Summary
This feature is related to the direct signaling connection re-establishment procedure of the UE
at the intersection of RNCs. When the UE moves between RNCs, this feature can prevent PS
services from being disrupted even if the relocation fails.
Benefits
This feature is a supplement to relocation. When the resources on the Iur interface are
insufficient or the relocation fails, this feature can prevent PS services from being disrupted.
Description
When the UE moves to the cell controlled by the DRNC, the SRNS relocation procedure (the
UE involved or not involved) can be implemented to keep services continuous. But when
there is no Iur interface or the relocation is not supported or relocation fails, UE connection
fails. In such scenarios, direct signaling connection re-establishment (DSCR) feature can be
used to prevent the connection from being interrupted. That is, the DRNC sends an RRC
connection release message with the cause of direct signaling connection re-establishment
when it is unable to contact the SRNC to validate the UE.
The UE should perform a route area update (RAU) procedure immediately on entering
PMM-IDLE state when it has received a RRC connection release message with the cause of
directed signaling connection re-establishment even if the RA has not changed since the last
update.
DSCR is used to re-establish services by RAU procedure. Hence, this feature can only be
applied to PS services, and it is of no help in re-establishing CS services.
Enhancement
None.

Issue V1.71 (2009-09-10) Page 75 of 145
Dependency
None.

Issue V1.71 (2009-09-10) Page 76 of 145
11 Node B Networking Modes
11.1 WRFD-050101 Star Topology

Availability
Summary
This feature is related to the star topology. The star topology is characterized by simple
networking and easy maintenance.
Benefits
In this mode, each Node B directly connects to the RNC. Therefore, the star topology features
simplicity, convenience in maintenance and engineering, and easy capacity expansion.
In this mode, signals travel through fewer nodes. Therefore, the transmission is more reliable.
Description
Node Bs can be connected in star topology.
It is applicable in most cases. Each Node B is directly connected to the RNC by E1/T1. The
networking structure is simple. It is convenient to implement maintenance and engineering.
Signals are transferred directly between the Node Bs and the RNC, so the link is quite reliable.
This networking topology can be applied in densely populated areas. It is easy to expand the
capacity, but a large amount of transport lines are required.
RNC
NodeB NodeB
NodeB

Issue V1.71 (2009-09-10) Page 77 of 145
Enhancement
None.
Dependency
None.
11.2 WRFD-050102 Chain Topology

Availability
Summary
This feature is related to the chain topology. The chain topology is characterized by
cost-effective networking.
Benefits
Chain networking can reduce costs of transmission equipment, engineering, construction and
transmission link lease.
Description
Node Bs can be connected in chain topology.
The line reliability is poor because signals are transferred across many intermediate systems.
This networking topology is applicable to the strip-shape areas having sparse population, such
as expressway and railway. In these areas, the chain topology can meet the requirements with
much less transmission equipment. The cascading connection is limited to five levels.
RNC NodeB NodeB NodeB
Enhancement
None.
Dependency
None.

Issue V1.71 (2009-09-10) Page 78 of 145
11.3 WRFD-050103 Tree Topology

Availability
Summary
This feature related to the tree topology. The tree topology is a combination of star topology
and chain topology and provides more flexible networking.
Benefits
It is suitable for microwave transmission network. The hub Node B is based on the tree
topology. The tree networking requires fewer transmission links than star networking.
Description
Node Bs can be connected in tree topology.
In most scenarios, the MW (Micro Wave) network is a typical tree topology. It is suitable for
the MW network. In order to increase the efficiency, the hub Node B based on the tree
topology is available from RAN5.1.
The consumption of transport lines is less than that of the star networking. But at the same
time, the connection is not so reliable because signals are transferred across many
Intermediate systems. It is difficult to implement maintenance and engineering. A fault occurs
in the upper-level Node B may affect the operation of the lower-level Node Bs. This
networking topology is applicable to a large area having sparse population. Capacity
expansion may result in reconstruction of the network.
Note:
The clock of the Node B is obtained by phase lock of the upper-level network. A phase lock
can degrade the quality of the clock. Therefore, the cascading level must be not more than
five.
NodeB
NodeB NodeB
RNC
NodeB
Enhancement
None.

Issue V1.71 (2009-09-10) Page 79 of 145
Dependency
None.

Issue V1.71 (2009-09-10) Page 80 of 145
12 Clock
12.1 MRFD-210501 BTS/NodeB Clock

Availability
Summary
The synchronization of the MBTS clock provides the basis for the frame synchronization. The
MBTS uses this feature to obtain the reference clock sources for the internal frame
synchronization. The MBTS supports three clock synchronization modes: synchronization
with the Iub/Abis clock, synchronization with the BITS clock, and synchronization with GPS
clock. In addition, the MBTS internal clock can work in free-run mode to temporarily provide
reference source.
Benefits
With this feature, the internal clock can be synchronized with the transmission network
without using the auxiliary equipment, thus saving the cost. In addition, the precision of the
synchronized clock meets the requirements of the radio transmission network and frequencies.
Description
In compliance with the 3GPP specifications, the frequency stability of the master clock of the
MBTS must be between –0.05 ppm and +0.05 ppm. The MBTS can work in multiple clock
synchronization modes to suit different clock topologies:
z Synchronization with the Iub/Abis clock (default mode)
The clock source of the MBTS is synchronized with the line clock sources of its
upper-level NE such as the MBSC.
z Synchronization with GPS
The GPS card is optional unless the MBTS uses a GPS clock as its clock source.
The clock signals are processed and synchronized as follows:
The GPS antenna and feeder system receives GPS signals at 1575.42 MHz, and then
transmits the signals to the GPS card. The system can trace up to eight (normally three or
four) satellites simultaneously. The GPS card processes the signals and transmits them to
the main clock module.
z Synchronization with the BITS clock
The MBTS can synchronize its clocks with the 2 MHz clock signals from an external
reference clock. The reference clock can be a BITS clock or a 2 MHz clock from the
transmission equipment.
Through phase locking and frequency dividing, the main clock module converts the
clock signals into various clock signals required by the MBTS, for example, F_CLK,
CLK_4X, and BFN.
In addition to the preceding three synchronization modes, the MBTS internal clock can work
in free-run mode to keep the MBTS running.
The enhanced stratum 3 OCXO with a high precision works as the master clock of the MBTS.
The OCXO can guarantee the normal operation of the MBTS for up to 90 days.
Enhancement
None.
Dependency
None.
1) BTS
The BTS3006C and BTS3002E do not support the GPS clock input.
2) NodeB
None.
3) MBTS
None.
None.
None
12.2 MRFD-210502 BSC/RNC Clock

Availability
Summary
With this feature, five types of clock sources are supported. Each clock source supports
functions such as 1+1 backup, management of the clock source, query of the clock status, and
maintenance of the link clock.

Issue V1.71 (2009-09-10) Page 82 of 145
Benefits
This feature provides various clock input schemes for operators.
The clock source backup function prevents the primary clock faults from affecting services.
Description
MBSC clock provides reliable clock sources for the MBSC to meet the requirements of the
clock precision defined in the 3GPP specifications. Every type of clock source supports 1+1
backup.
The MBSC clock subsystem consists of the clock processing board GCUa/GCGa and the
clock processing unit in each subrack. The external reference clock signals are transmitted to
the GCUa/GCGa. After a phase lock on the GCUa/GCGa, the clock signals are changed to 8
KHz clock signals. The signals are then transmitted to the SCUa in the same subrack through
the backplane and to the SCUa in the EPS through clock signal cables. Then, the 8 KHz clock
signals on the SCUa are transmitted to other boards in the same subrack through the
backplane.
When the clock source is faulty, the MBSC reports the related alarms and starts the 1+1
backup scheme to ensure the normal operation of the system.
The MBSC clock sources are as follows:
z Building integrated timing supply system (BITS)
z Line clock extracted from the A/Iu interface
z Global positioning system (GPS) satellite synchronization clock
z 8 KHz clock provided by an external device
z Local oscillator clock
The MBSC provides the clock control setting functions, including management of the clock
source, query of the clock status, and maintenance of the line clock. The MBSC requires only
one clock source, and the clock source can work in automatic, manual, or self-oscillation
mode.
z Automatic
In automatic mode, you need not specify a clock source for the current clock. The system
automatically selects a clock source with the highest priority.
z Manual
In manual mode, you need to manually specify a clock source for the current clock. The
system does not automatically switch to another clock source even if this clock source is
faulty.
z Self-oscillation
The self-oscillation mode is the default clock working mode of the system.
Enhancement
None.

Issue V1.71 (2009-09-10) Page 83 of 145
Dependency
The GCGa should be configured if the GPS satellite synchronization clock is used.
None.
None.
None.

Issue V1.71 (2009-09-10) Page 84 of 145
13 ATM Transmission Introduction

Package
13.1 WRFD-050301 ATM Transmission Introduction

Package
Availability
Summary
This feature is related to ATM transmission introduction for the operator. ATM transmission is
one of the major WCDMA networking solutions. Huawei RAN provides ATM transmission
interfaces and related functions.
Benefits
This feature package provides support for ATM transmission.
Description
Huawei RAN supports ATM transport optional feature defined in 3GPP specifications. ATM
transmission feature includes the following sub-features:
z ATM over E1/T1 on Iub interface
z ATM over channelized STM-1/OC-3 on Iub interface
z ATM over non-channelized STM-1/OC-3c on Iub/Iu/Iur interface
z IMA for E1T1 or channelized STM-1/OC-3 on Iub interface
z Dynamic AAL2 connections on Iub/IuCS/Iur interface
z Permanent AAL5 connections for control plane traffic
z Call admission based on AAL2 path BW
z CBR, rt-VBR, nrt-VBR, UBR ATM QoS classes

Issue V1.71 (2009-09-10) Page 85 of 145
Enhancement
For the enhancement, refer to the enhancement of sub-features in ATM Transmission
Introduction Package.
Dependency
None.
13.1.1 WRFD-05030101 ATM over E1T1 on Iub Interface

Availability
Summary
This feature is related to ATM over E1/T1 on the Iub interface. The boards capable of this
feature include the ATM transmission interface board on the RNC side and the NUTI, HBBU,
WMPT, and UTRP on the Node B side.
Benefits
This feature enables the use of microwave network or PDH legacy network for Iub
transmission.
Description
Huawei RAN supports ATM over E1/T1 electrical interface.
The RNC ATM over E1/T1 interface board supports:
z 32 ports (E1/T1) per board
z UNI, IMA, Fractional ATM, and Fractional IMA
z 32 IMA group per board
z 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:
z UNI, IMA, Fractional ATM
z 4 IMA groups per board
The Node B (3900 Series Node B) ATM over E1/T1 interface board (WMPT) supports:
z 2 IMA groups per board
The Node B (3900 Series Node B) ATM over E1/T1 interface board (UTRP) supports:

Issue V1.71 (2009-09-10) Page 86 of 145

z 4 IMA group per board
Enhancement
In RAN2.0, the NDTI board is introduced.
In RAN5.0, the HBBU board is introduced.
In RAN5.1, the NUTI board is introduced.
In RAN10.0, the WMPT and UTRP (E1 interface) boards are introduced in 3900 series Node
B.
Dependency
None.
13.1.2 WRFD-05030102 ATM over Channelized STM-1/OC-3 on

Iub Interface
Availability
Summary
This feature is related to ATM over channelized STM-1/OC-3 on the Iub interface. The boards
capable of this feature include the ATM transmission interface board based on channelized
STM-1 on the RNC side and the NUTI and HBBU on the Node B side.
Benefits
This feature enables the use of SDH network for Iub transmission.
Description
Huawei RAN supports ATM over channelized STM-1 optical interface on Iub interface.
BSC6800 ATM over channelized STM-1 interface board supports:
z 1 x 155 Mbps port per board.
z 63 x VC12 2 Mbps flows per port.
z 63 UNI link, or 42 IMA group per port.
z At most 32 VC12 flows per IMA group.
z MSP 1:1 redundancy.
BSC6810 ATM over channelized STM-1/OC-3 interface board supports:
z 2 x 155 Mbps port per board
z 63 x VC12 2 Mbps or 84 x VC11 1.5 Mbps flows per port, configurable at initiation

Issue V1.71 (2009-09-10) Page 87 of 145
z 63 x 2 Mbps UNI links, or 84 x 1.5 Mbps UNI links, or 42 IMA group per port
z At most 32 VC12/VC11 flows per IMA group
z MSP 1:1 redundancy
The Node B (BTS3812E/AE, DBS3800) channelized STM-1 interface board (NUTI, HBBU)
supports:
z 63 x VC12 2 Mbps flows per port.
Enhancement
In RAN6.0, the Node B (BTS3812E/AE and DBS3800) supports the transmission interface
board based on channelized STM-1/OC-3.
Dependency
Only BTS3812E/AE and DBS3800 can provide the ports based on channelized STM-1/OC-3.
13.1.3 WRFD-05030103 ATM over Non-channelized STM-1/OC-3c

on Iub/Iu/Iur Interface
Availability
Summary
This feature is related to ATM over non-channelized STM-1/OC-3 on the Iub interface. The
boards capable of this feature include the ATM transmission interface board based on
non-channelized STM-1 on the RNC side and the NUTI, HBBU, and UTRP on the Node B
side.
Benefits
This feature enables the use of SDH network or ATM network for Iub/Iu/Iur transmission.
Description
Huawei RAN supports ATM over non-channelized STM-1/OC-3c optical interface on
Iub/Iu/Iur ATM transmission.
BSC6800 ATM over non-channelized STM-1/OC-3c interface board supports:
z ATM full rate, VC4 150 Mbps per port.
z MSP 1+1 redundancy.
BSC6810 ATM over non-channelized STM-1/OC-3 interface board supports:

Issue V1.71 (2009-09-10) Page 88 of 145
z MSP 1+1 and MSP 1:1 redundancy.

z Up to 2000 VCs per board shared by each port.
z Full VPI/VCI address space (VPI: 0 – 255, VCI: 32 - 65535).
The Node B (BTS3812E/AE, DBS3800) non-channelized STM-1/OC-3 interface board
(NUTI, HBBU) supports:
The Node B (3900 series NodeB) on-channelized STM-1/OC-3 interface board (UTRP)
supports:
Enhancement
In RAN5.1, the Node B (BTS3812E/AE and DBS3800) supports the transmission interface
board based on non-channelized STM-1/OC-3.
In RAN10.0, the 3900 series Node B supports the UTRP transmission board based on
non-channelized STM-1.
Dependency
None.
13.1.4 WRFD-05030104 Dynamic AAL2 Connections on

Iub/IuCS/Iur Interface
Availability
Summary
This feature is related to the establishment of dynamic AAL2 connections on the Iub, Iur, and
Iu-CS interfaces.
Benefits
Huawei implementation of AAL2 enables:
z Separating traffic into different type AAL2 path according to traffic classes
(Conversational, Streaming, Interactive, and Background).
z Separating traffic into different types of AAL2 paths according to R99, HSDPA, and
HSUPA traffic.
z Efficient Iub transmission link usage when integrating delay sensitive traffic with
non-delay sensitive traffic.
z Dynamic allocation of physical link bandwidth between delay sensitive traffic and
non-delay sensitive traffic.

Issue V1.71 (2009-09-10) Page 89 of 145
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 of
AAL2 paths 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 RAN5.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.
13.1.5 WRFD-05030105 Permanent AAL5 Connections for Control

Plane Traffic
Availability
Summary
This feature is concerned with the establishment of permanent AAL5 connections for control
plane traffic on the Iub, Iur, and Iu interfaces.
Benefits
Permanent AAL5 connections for control plane traffic are part of 3GPP Iub, Iur, and Iu
specifications.
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

Issue V1.71 (2009-09-10) Page 90 of 145
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.
13.1.6 WRFD-05030106 Call Admission Based on Used AAL2 Path

Bandwidth
Availability
Summary
This feature is related to the call admission control (CAC) based on AAL2 path bandwidth.
The AAL2 CAC is used to selectively accept or reject some access requests to maximize the
utilization of transmission resources without compromising QoS.
Benefits
This feature helps to:
z Avoid transmission congestion
z Improve the transmission resource usage
z Increase the accessibility
Description
The purpose of AAL2 CAC (Call Admission Control) is to maintain the quality of service and
at the same time maximize the utilization of transmission resources. This is achieved by
selectively admitting or rejecting request for resources.
AAL2 CAC request occurs when the AAL2 connection is established or modified on Iub, Iur,
and Iu-CS interfaces.
In the case of CS services, PCR * service factor is used for admission decision.
In the case of PS services, GBR * service factor is used for admission decision. No GBR is
assigned for best effort services. Hence, such parameters can be configured by operators.
In the case of HSDPA/HSUPA service, GBR * service factor is used for admission decision.
No GBR is assigned for best effort services. Hence, such parameters can be configured by
operators.
All the preceding service factors can be configured according to the service classes.
For the UE handover, all the transmission resources can be used for admission to minimize
the possibility of the failure of an existing call.

Issue V1.71 (2009-09-10) Page 91 of 145
For the newly accessed UE, (100% - handover admission threshold) transmission resources
are used.
For the bit rate upgrade UE, the transmission resources below congestion threshold are used.
Enhancement
None.
Dependency
None.
13.1.7 WRFD-05030107 CBR, rt-VBR, nrt-VBR, UBR ATM QoS

Classes
Availability
Summary
This feature is concerned with four ATM service classes: CBR, rt-VBR, nrt-VBR, and UBR.
The four ATM service classes are used to differentiate services at the ATM layer.
Benefits
The feature supports:
z Full inter-operation between RAN and ATM equipment
z VC traffic shaping
z ATM traffic differentiation
Description
Huawei RAN supports four ATM service classes (CBR, rt-VBR, nrt-VBR, and UBR)
specified in TM4.1 (ATM forum specification Traffic Management 4.1). The VCC supports
shaping for existing traffic according to the parameters (SCR, PCR, and CDVT) of each ATM
service class.
The four ATM service classes are used to differentiate services at the ATM layer. Two ATM
service classes are configured for R99 traffic and two are configured for HSxPA. In general,
DS (Delay Sensitive) traffic uses rt-VBR, NDS (None Delay Sensitive) traffic uses nrt-VBR,
and NDS traffic mapping on HSxPA uses UBR or nrt-VBR.
Enhancement
None.
Dependency
None.

Issue V1.71 (2009-09-10) Page 92 of 145
13.1.8 WRFD-05030110 F5
Availability
Summary
This feature is related to end-to-end ATM OAM F5 flows defined in ITU I.610.
Benefits
z ATM VCC End-to-End continuity check.
z Supervision of the AAL2 path, and blocking of the fault AAL2 path.
z Supervision of the Iu-PS GTPU path, and blocking of the fault GTPU path
Description
Huawei RAN supports ATM OAM F5 end-to-end flows specified in ITU I.610. Fault
management (AIS: Alarm Indication Signal, RDI: Remote Defect Indication, CC: Continuity
Check and Loopback), performance management (forward monitoring and backward
reporting) and activation/deactivation are supported. The CC can be activated to monitor
AAL2 path VCC and Iu-PS user plane VCC end-to-end. When one VCC for AAL2 path or
Iu-PS GTPU is LOC (Loss of continuity), AIS, or RDI, this VCC is blocked. Then the service
is established on other alternative VCCs to prevent the failure of the call.
The BSC6810 only supports the fault management feature.
Enhancement
In RAN5.1, ATM OAM F5 flows on IuPS user plane VCC is introduced in BSC6800.
In RAN10.0, this feature is introduced in BSC6810.
In RAN11.0, this feature is introduced in 3900 series Node B, BTS3812E/AE and DBS3800
which support passive check..
Dependency
None.

Issue V1.71 (2009-09-10) Page 93 of 145
14 IMA Transmission for E1/T1 or

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

Channelized STM-1/OC-3 on Iub Interface
Availability
Summary
This feature is concerned with IMA transmission for E1/T1 or channelized STM-1/OC-3 on
the Iub interface. This feature enables inverse multiplexing on ATM to improve transmission
reliability.
Benefits
z Peak rates higher than the individual physical link rates, 1.5 Mbit/s for T1 or 2 Mbit/s for
E1.
z Simplification of the ATM OM procedures, like monitoring one single ATM link instead
of several separate links.
z Higher trunk level and statistical multiplexing gain.
Description
The inverse multiplex on ATM (IMA) mode is an ATM transport mode in the TC sub-layer of
the ATM physical layer.
In IMA mode, an ATM cell stream is distributed to several narrowband transport links. At the
peer end, the data streams from these narrowband transport links are converged into the
original ATM cell stream. IMA flexibly combines several narrowband transport links to
transport high-speed ATM cell streams, which is referred to as inverse multiplex on ATM. In
this manner, the existing narrowband transport links, especially 2 Mbit/s links, can serve
broadband ATM transmission. IMA also enhances transmission reliability.

Issue V1.71 (2009-09-10) Page 94 of 145
IMA group IMA group

PHY Physical I ink #0 PHY
Physical I ink #1
PHY PHY
Single ATM cell stream Original ATM cell
from ATM layer Physical I ink #2 stream to ATM laye
PHY PHY
IMA virtual link
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.

Issue V1.71 (2009-09-10) Page 95 of 145
15 UBR+ATM QoS Class
15.1 WRFD-050305 UBR+ ATM QoS Class

Availability
Summary
UBR+ ensures the connectivity of OAM connection and full use of the transmission
bandwidth.
Benefits
This feature ensures reliable OAM connections and full use of the transmission bandwidth.
Description
Huawei RAN supports UBR+ ATM service class. UBR+ is an enhancement of UBR with
MCR (Minimum Desired Cell Rate) indication. UBR+ is the most suitable for Iub OAM
channel. The MCR of UBR+ ensures the connectivity of OAM connection in the case of Iub
transmission resource congestion, and the best effort service of UBR+ uses the transmission
bandwidth completely.
Enhancement
None.
Dependency
None.
16 Link Aggregation
16.1 MRFD-210103 Link Aggregation

Availability
Summary
This feature supports the transmission of multiple FEs or GEs binding, thus improving the
reliability of FE transmission and meeting the requirements of higher data flow.
Benefits
This feature provides the method for improving the transmission reliability.
Description
Huawei GBSS/RAN implements the link aggregation based on IEEE802.3ad, thus improving
the system reliability and providing higher bandwidth.
This feature applies to the scenario where high reliability is required, for example, on the
ports of the MBSC and the hub NodeB where links are bundled together.
Figure 16-1 Networking for Link Aggregation
Enhancement
None.
Dependency
None.

Issue V1.71 (2009-09-10) Page 97 of 145

This feature applies only to the 3900 series base station.
None.
None.

Issue V1.71 (2009-09-10) Page 98 of 145
17 System Reliability
17.1 WRFD-040100 Flow Control

Availability
Summary
This feature provides a series of mechanisms that can prevent the network or system from
being overloaded to ensure that the services with high priorities are handled properly even
when the traffic is busy.
Benefits
The feature ensures the stability and robustness of the RNC, and also ensures that services
with high priorities work properly during high traffic.
Description
Flow control in the radio network controller (RNC) is a set of mechanisms that the RNC uses
to prevent the network from being overloaded by regulating the input rate transmissions.
The system determines specific flow control measures in compliance with the load on the
following two resources:
z 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.
z Message block occupancy
The message block is the core resource for internal communication between the RNC.
High message block occupancy means there is the risk of inefficient processing
capability in the system. In this situation, the flow control on corresponding functions
should be triggered to ensure basic functions of the system. After the message block
occupancy is lower than a proper threshold, the previously-triggered functions are
enabled.
The flow control item corresponds to a function in the system, such as printing
information, debug information, system log, service-related RRC connection setup
request, paging message, and so on. The system enables, disables, or partially disables
the functions in compliance with the current resource load such as the CPU occupancy
and the message block occupancy to ensure system stability and robustness.
z If a flow control item is controlled, the corresponding function is disabled or partially
disabled. If a flow control item is restored, the corresponding function is enabled again.
Enhancement
None.
Dependency
None.
17.2 MRFD-210101 System Redundancy

Availability
Summary
This feature provides the reliability designs such as the active/standby mode, load sharing,
and redundancy configuration, thus improving the system reliability.
Benefits
This feature improves the system stability and thus ensures the network performance.
Description
To ensure the reliable operation of the system, reliability designs such as the active/standby
mode, load sharing, and redundancy configuration are widely used in Huawei GBSS/RAN.
In resource pool mode, the load sharing is performed among processing units in the pool. The
processing unit is not backed up. When one or multiple processing units are faulty, the
ongoing services are disrupted, and the new services requests are allocated to other normal
processing units in the resource pool.
In active/standby mode, the active board processes services while the standby board acts as a
backup of the active one. When the active board is faulty or needs to be replaced, the services
can be switched over to the standby board. In this way, the system can work continuously.
There are two types of switchover. One is automatic switchover. That is, the services are
automatically switched over from the active board to the standby board when the active board
is faulty. The other one is manual switchover. That is, the maintenance engineer performs the
board switchover on the LMT. If the active/standby switchover is allowed, a dedicated
maintenance module instructs the relevant boards to perform the switchover after the
maintenance engineer sends an immediate switchover command to the system.
To perform the active/standby switchover successfully, the following conditions must be met:
z The standby board must be in position and work normally.

Issue V1.71 (2009-09-10) Page 100 of 145
z No major or critical alarm is reported.

When the standby board is switched over to the active one, the previously active board will be
reset automatically. If this board restarts normally, it becomes the standby one. In this way,
the boards still work in active/standby mode.
Redundancy configuration consists of the following units: boards, transmission interfaces,
power, and fans. The software version and important data configuration file are backed up to
ensure that the system works normally even if exception occurs in the file or data.
For the BSC6900, the dual-switching system of the control plane and user plane is applied. In
addition, the resource pool of control plane and user plane is designed. For the service
processing boards, the resource pool is adopted. That is, load-sharing is performed in the
resource pool. For other boards, the backup mode is adopted. That is, the boards of the same
type in two neighboring slots work in active/standby mode. The resource pool is
independently established within the GSM or UMTS.
Huawei BTS/NodeB supports the board-level backup. Two boards of the same type work in
active/standby mode. When the active board is faulty, an active/standby switchover is
performed and the previously standby board works in active mode.
For the interface board, the board backup mode is adopted. Some interface boards support the
standard backup modes specified in protocols, such as MSP 1+1 or MSP 1:1.When detecting
that the board is faulty, the system re-establishes the transmission of the ongoing services on
the standby board by adopting an active/standby switchover. When detecting that the active
channel is damaged, the system enables the transmission of the ongoing services to recover on
the standby channel by adopting an active/standby switchover.
Enhancement
None.
Dependency
None.
None.
None.
None.
17.3 MRFD-210102 Operate System Security Management

Availability

Issue V1.71 (2009-09-10) Page 101 of 145
Summary
This feature provides the customized security policy and patch management for the operating
system on the OMU.
Benefits
This feature ensures system reliability and prevents the security threats and attacks on the
operating system.
Description
This feature provides the customized security policy and patch management for the operating
system on the OMU.
Customized security management of the operating system:
The customized security policy protects the operating system from being attacked and thus
enhances the security of the operating system. This feature can be applied to the Windows
2003 Server and the Linux operating system. The customize security policies are as follows:
z Execution policy
You can execute one or more policies and record the execution results in log files.
z Rollback policy
After executing a security policy, if you want to restore the system to the previous state
or customize the policy again, then you can restore the executed policy.
z Generating backup files
You can save the current status of a policy into a file. This file can be used as a backup
for rollback.
z Saving settings
You can save the current policy settings.
z Exporting settings
You can export the current policy settings to another file.
z Importing settings
You can import the file containing the policy settings into the system. In this way, the
system has the same settings.
z Importing the configuration file of the earlier version
z You can import the configuration file of the earlier version to the SetWin.
z Reloading the configuration file
The SetWin has an inherent configuration file. You can reload this configuration file to the
SetWin.
Patch management of the operating system:
Based on the type of the operating system, you can timely perform the patch compatibility
test to ensure that the patch is valid. The patch list corresponding to the operating system is
provided at least twice a year.
Anti-Virus:
When Windows 2003 Server is employed, Anti-Virus solution is available as following:

Issue V1.71 (2009-09-10) Page 102 of 145
Integrate with TrendMicro Officescan 7.3 with one year of warranty

To deploying an OfficeScan 7.3 server in OSS network, it can protect all the BAM/OMU
from infected by antivirus with installing OfficeScan client program on BAM/OMU.
Enhancement
RAN11.0 supports Anti-virus security solution.
Dependency
None.
None.
None.
None.

Issue V1.71 (2009-09-10) Page 103 of 145
18 RAN Operation & Maintenance
18.1 MRFD-210301 Configuration Management

Availability
Summary
This feature provides operators with the method for collecting and managing the information
about NEs (MBSC and MBTS). It can control the links between the NEs. The graphic user
interface (GUI) makes it easy for configuration management.
Benefits
This feature provides a descriptive overview of the current status of the network and supports
fast installation, capacity expansion, and data configuration of the network.
Description
This feature provides operators with the method for collecting and managing the information
about NEs (MBSC and MBTS). It can control the links between the NEs. The graphic user
interface (GUI) makes it easy to for configuration management.
The NE configuration can be classified into five levels:
z Initial configuration
Design the initial configuration of the MBSC and MBTS.
z Basic site configuration
Configuration of the O&M communication between the MBSC, MBTS, and the M2000
z External site hardware configuration on the MBTS side
Configuration of TMA data and antennas
z MBTS configuration and site-specific configuration on the MBTS side
Data configuration of the A/Iu interface, Abis/Iub interface, Iur-g/Iur interface, and the
transport network
z Cell/TRX configuration on the MBSC side
Data configuration of cells, channels, and neighboring cells
Configuration from level 1 to level 3 can be implemented either with the GUI of the
configuration tool or with the pre-defined configuration files on the LMT. Configuration of
level 4 and level 5 can be implemented either through the M2000 or through the configuration
tool.
z Online/Offline data configuration and status query
The configuration data is not sent to the host until it takes effect. This improves the
efficiency of configuring a large quantity of data. The MBSC supports offline
configuration based on host subracks. Therefore, the services are not interrupted during
capacity expansion.
During the switchover of the IP interface board and the ATM/TDM interface board,
offline configuration supports the modification of the interface board type and the
switchover of the active/standby boards.
Online data configuration enables the data to be sent to the host immediately after the
configuration. There is no need to reset the system or reload the data.
ITU-T Recommendation X.731 defines the object status. The operators can query the
object status such as the board status or cell status and the time of the latest status
change.
z Configuration right control
With the configuration right control, data can be configured only on the LMT of the
MBSC/MBTS or the M2000 client. In addition, the operators always have the
configuration right. This improves the reliability of the system.
z Configuration rollback on the MBSC side
When the equipment or network malfunctions due to improper data modification,
operators can perform the rollback operation to restore the system in a short time.
z MBSC data backup
Two OMUs work in active/standby mode. The system synchronizes the data on the
standby OMU with that on the active OMU.
The MBSC supports automatic backup and manual backup. It provides a data backup
and restoration tool.
z Setting of network parameters
The radio network parameters are of two types: MBSC-oriented parameters and
cell-oriented parameters, which are used in different radio conditions. The MBSC can
check the integrity and consistency of configuration data such as the data of a cell.
z Detection of missing neighboring cell
Based on the measurement information from the user equipment (UE), the neighboring
cells missed for configuration can be detected and reported. This helps the operators
optimize the configuration of neighboring cells and thus improves the network planning
efficiency.
Enhancement
RAN5.1 supports the modification of the interface board type and active/standby state of
boards in offline mode.
RAN5.1 supports the query of the time when the latest status changes.
RAN10.0 supports the reporting of MBTS status to the M2000.
GBSS9.0&RAN11.1

Issue V1.71 (2009-09-10) Page 105 of 145
Web LMT: The operation and maintenance GUI of the MBSC uses the Web LMT based on
the browser/server mode. The configuration GUI uses the CME. The MML client is
incorporated in the Web LMT and thus the configuration and maintenance for the MBSC can
be carried out through the MML commands. After the Web LMT is used, there is no need to
install the LMT software on the local PC. The configuration and maintenance for the MBSC
can be carried out through the Web browser. In addition, the upgrade of the software on the
local PC is not required when the MBSC software is upgraded, and thus the operation
efficiency is significantly improved.
Dependency
None.
None.
None.
Configuration management is implemented through the M2000 or the LMT.
18.2 MRFD-210302 Performance Management

Availability
Summary
This feature periodically takes samples of counters about the management objects, bearer
resources, and services. The sampled data is then collected, saved, monitored, and analyzed.
In this way, the operating status of the network can be obtained. Thus, this feature helps
operators quickly locate and solve problems and optimize the network.
Benefits
This feature provides an efficient method for monitoring the network performance and
facilitates the network troubleshooting and optimization. The real-time performance
monitoring is a more effective feature.
Description
Performance management helps collect the measurable performance data to obtain the
network operating status, thus helping the operators quickly locate and solve problems and
optimize the network.
Performance measurement management

Issue V1.71 (2009-09-10) Page 106 of 145
This feature provides operators with a method for managing the measurable performance
data.
For the new commissioning NEs (MBSC and MBTS), the pre-defined performance statistics
completely starts after the initial start-up or restart. The performance statistics can be
suspended or restored manually.
The MBSC and MBTS provide the interfaces between them and the M2000, allowing the
M2000 to collect necessary statistic data and to configure the related parameters including
statistic counters and periods.
The statistic data is saved on the M2000 in binary-formatting files in every statistic period.
The result files are saved on the MBTS for up to 24 hours or on the MBSC for up to 10 days.
If a fault occurs in data transmission, you can obtain the lost data through the M2000.
Performance measurement counter
The performance measurement counters include key counters and other counters. The key
counters are used to generate the KPIs of the network which are defined on the M2000, and
these pre-defined counters are initialized immediately after the MBSC and the MBTS start.
The KPIs, related original counters, and formula can be added, modified, and deleted on the
M2000. Other counters indicating the network performance can also be added as required.
In the UMTS network, the following measurement objects are supported:
z Cell measurement
z Neighboring cell measurement
z Inter-RAT neighboring cell measurement
z RNC overall measurement
z ATM transport measurement
z IP transport measurement
z Standard interface measurement
z NE hardware measurement
Real-time performance monitoring
This feature supports the real-time performance monitoring and displays the details of the
monitoring result in the GUI. Thus, it facilitates the troubleshooting, drive test, network
optimization, and other operations.
The monitoring tasks are managed by the LMT of the NE (RNC and NodeB). The data
monitored is displayed in curve and stored in a file automatically for later review.
The following items can be monitored in real time:
z Equipment performance: CPU usage, clock source quality, and so on.
z Connection performance: SIR measurement, UE transmits power, and so on.
z Cell performance: PCPICH transmit power, number of UEs in the cell, and so on.
z Link performance: IMA group, UNI link, and so on.
z Service performance: RF performance, UL channel scanning, and resource usage.
In the GSM network, the following performance counters are supported:
The measurements can be classified into the following types according to the measurement
object:
z BSC measurement

Issue V1.71 (2009-09-10) Page 107 of 145
z Cell measurement
z TRX measurement
z Neighboring cell measurement
The measurements can be classified into the following types according to the MS status:
z Paging
z Call
z Measurement report
z Channel allocation
Enhanced performance measurement:
z Measurement of incoming and outgoing cell handovers
This measurement provides data about the incoming and outgoing cell handovers. The
collected measurement data assists the operators in network adjustment and
optimization.
z Undefined adjacent cell measurement
This measurement provides BSIC, BCCH frequency, average signal strength, number of
MRs of adjacent cells that are included in the BA list but not included in the adjacent cell
relation table. The collected measurement data assists the operators in network
adjustment and optimization.
z Defined adjacent cell measurement
This measurement provides BSIC, BCCH frequency, average signal strength, number of
MRs of the defined adjacent cell. The collected measurement data assists the operators in
network adjustment and optimization.
z Uplink and downlink balance measurement
This measurement provides the data about the balance between the uplink and downlink
of TCHs. The uplink and downlink balance level is graded according to the receive
levels in the uplink and downlink. The collected measurement data assists the operators
in network adjustment and optimization.
z Call drop measurement
This measurement provides the average level and quality in the uplink and downlink,
and also the average TA value of SDCCH call drops and TCH call drops. The collected
measurement data assists the operators in network adjustment and optimization.
z BTS out-of-service measurement
This measurement is provided by the performance management of the BSC together with
the M2000. This measurement provides the start time of BTS out-of-service, end time of
BTS out-of-service (or service recovery time), and the duration of BTS out-of-service.
Enhancement
UMTS
z RAN5.1 supports HSDPA-related counters and monitoring items.
z RAN6.0 supports HSUPA-related counters and monitoring items.
z RAN10.0 supports the real-time performance monitoring on the IP patch.
GBSS

Issue V1.71 (2009-09-10) Page 108 of 145
z GBSS8.0 supports the real-time performance monitoring and the counter measurement
related to the built-in PCU.
z GBSS8.1 supports real-time traffic measurement, enhanced IP performance
measurement, and measurement period of 24 hours. In addition, it supports the
measurement of traffic statistics of group call and group broadcast on the BSC level and
cell level.
Dependency
None.
None.
None.
Performance management is implemented by the M2000, and the real-time performance
monitoring is implemented by the LMT.
18.3 MRFD-210303 Inventory Management

Availability
Summary
This feature assists in reporting the information about the physical and logical objects of the
NEs to the M2000, and also assists in managing this information on the M2000.
Benefits
As a large number of devices are deployed on networks, it becomes difficult to manage
equipment. For ease of equipment management, operators need to obtain the information
about the physical device and some important logical information. With this feature, the
information can be reported to the M2000, thus facilitating the asset management. In addition,
operators can obtain the accurate decision-making data of the existing networks in time.
Description
The inventory management helps operators to manage the network assets and configuration
data. With this function, network assets and configuration data can be managed on the
M2000.
The objects that are managed by this function include physical objects (such as rack, frame,
slot, board, and fan) and logic objects (such as cell, software, and patch).

Issue V1.71 (2009-09-10) Page 109 of 145
Upon a request from the M2000, the information about the network assets and configuration
data are generated in an .xml file and then are sent to the M2000. The M2000 saves the
uploaded information in the network inventory database.
Upon a request from the M2000, the MBSC reports its information about the assets and
configuration to the M2000. In terms of the method of collecting and reporting the
information about the base station, the UMTS network is different from the GSM network.
In the UMTS network, the NodeB works as an independent NE and supports the reporting of
its inventory information to the M2000.
In the GSM network, the inventory of the BTS is jointly controlled by the BSC and the BTS.
The BTS inventory management system is deployed on the M2000. The M2000 sends the
required inventory information command to the BSC through the southbound interface. On
reception of this command, the BSC queries the inventory information about all the BTSs,
generates files, and sends the files to the M2000. Then, the M2000 interprets the files and
saves them in the database. Some inventory information can be imported through the manual
input or other files. The M2000 supports the query, synchronization, modification, export, and
import of the BTS inventory information.
The BTS supports the reporting of the information about the electronic label, software version,
and hardware version of the BTS boards as well as the information about the manufacturer of
the heat exchanger. In addition, the BTS also supports the input and reporting of the bar code
of the BTS cabinet.
As the ID of a board, the electronic label provides the basis for board replacement, presents a
traceable mark in the entire lifecycle of the board, and supplies the data required for the
management, tracing, and maintenance of the board. The information about the electronic
label of the BTS board includes: the board model, bar code, BOM code, description,
production date, name of the manufacturer, and release number.
The M2000 provides the import or modification function for the inventory information that is
not supported by the BTS. That is, the information can be manually entered. The information

Issue V1.71 (2009-09-10) Page 110 of 145
includes the information about the BTS antenna, electronic label of the board that fails to
report the electronic label (mainly purchased parts), and the ultimate service time of the board
information area. This information is not sent to the BTS for storage but is saved only in the
inventory management system on the M2000.
In addition, no storage part is available in the BTS cabinet, and thus the bar code of the
cabinet needs to be manually entered on the M2000 or the LMT. The BTS supports the input
of this information and also the storage of it in the main control board of the BTS. Then, the
BTS sends the information to the BSC through the inventory management interface.
Enhancement
z UMTS
None.
z GSM
GBSS8.0 supports the reporting of the electronic label of the BTS board according to
electronic label standards 3.0.
GBSS8.1 adds the reporting of the information about the software and hardware versions
of the BTS boards, manufacturer of the heat exchanger, electronic labels of the BBU
backplane, fan board, and power monitoring board, and the input and query of the
electronic bar code of the cabinet.
Dependency
None.
None.
None.
Inventory information can be queried only on the M2000. Therefore, the M2000 should
support the inventory management feature.
18.4 MRFD-210304 Faulty Management

Availability
Summary
This feature involves various fault management functions such as system auto test, fault
detection, fault monitoring, and fault rectification of the UTRAN. This enables the operators
to learn about the network fault timely and take proper measures to avoid service interruption.

Issue V1.71 (2009-09-10) Page 111 of 145
Benefits
This feature provides the following benefits:
z Enables the automatic monitoring of the network equipment.
z Enables the operators to learn about the actual state of the network timely and
comprehensively by querying the active alarm list and alarm log.
z Facilitates the manual board test, with which the operators can identify the faulty board
timely.
Description
The fault management involves system auto test, fault detection, fault monitoring, and fault
rectification. This enables the operators to learn about the network fault timely and take
proper measures to avoid service interruption.
The automatic hardware test of the system is performed during the startup of the MBSC or
MBTS. When the MBSC or MBTS is in operation, the system status monitoring can also be
started manually if required.
z Fault detection
This involves the fault detection of the physical layer, transmission link layer, and others.
The fault detection can be started manually. Operators can either browse the monitoring
result online or save the monitoring result as files.
z Alarm management
Operators can browse the real-time alarm information, query the history alarm
information, and save the alarm information as required. The online help provides
detailed methods for clearing alarms.
z Alarm correlation processing
Based on certain built-in mechanism, the alarm correlation handling mechanism enables
the system to keep the most important alarms instead of all the related alarms when a
fault occurs. The number of alarms can be greatly reduced in this way and network
problems can be easily identified and handled. This mechanism is pre-defined and
incorporated in the NEs such as MBSC and MBTS. More alarm correlation processing
mechanisms can be defined by the operators on the M2000.
The operators may also filter the alarms of an object. The alarms of this object, if filtered, are
not reported.
The alarms of the access network include MBSC alarm and MBTS alarm.
MBSC alarm
The MBSC alarm system provides two types of alarm output devices: alarm console and
alarm box. The alarm box provides visual and audible alarms. The alarm console is a part of
the OMC. It provides detailed alarm information, recovery suggestion, and alarm box control.
The MBSC alarm system is composed of the BAM alarm module, centralized network
management alarm database, alarm console, and alarm box. Alarm system accurately provides
the fault information detected by the MBSC system to the maintenance personnel through
alarm information. The maintenance personnel can then rectify the fault accordingly.
z Alarm severity

Issue V1.71 (2009-09-10) Page 112 of 145
According to the severity and influence of the alarms, there are four alarm severities:
critical, major, minor, and warning. Different severity of alarms is presented in different
manner, such as color and sound.
z Alarm classification
According to its subsystem and subsystem type, alarms can be classified into fault alarm
and event alarm. Clearance alarms are provided for fault alarms. Event alarm has no
corresponding clearance alarm.
According to the cause of alarms, alarms can be classified into inter-module
communication alarm, signaling subsystem alarm, clock subsystem alarm, and power
supply subsystem alarm. These alarms help the maintenance engineers quickly locate the
faults. This feature also provides alarm about software running, such as CPU overload
alarm and GBAM hard disk capacity alarm.
z Alarm location and recovery suggestions
The alarm console provides detailed alarm information, including the ID of the board for
which the alarm is generated, the potential cause and possible consequence of the alarm,
and the recovery suggestion.
z Alarm box control
The alarm box control provides manual control of the alarm box. You can mute the alarm
sound or turn off the LED for the alarm box manually on the OMC alarm console. The
alarms can be printed in real time. The alarm parameters data can be configured and
modified. Based on the configuration, the MBSC can automatically control where the
alarms will be sent, such as to alarm box or to OMC alarm console. This enables flexible
alarm control.
z Alarm query
The alarms can be queried in various conditions. You can browse the fault alarm,
emergency event alarm, or other event alarms in real time on the alarm console. You can
also query the history fault alarm, recovery alarm, and event alarm according to alarm
serial number, alarm ID, date and time of alarm, alarm module number, function number,
or alarm level. The queried history alarms can be saved.
z Environment monitoring unit
Each subrack of the BSC6900 can connect to an environment monitoring unit (EMU)
through the serial ports. The EMU has four types of ports: fixed analog ports (four) used
for receiving –48 V voltage, –24 V voltage, temperature, and humidity alarms; extended
external analog ports (four); fixed external Boolean ports (four) used for receiving water,
smoke, infrared, and door status alarms; and extended external Boolean ports (32).
Alarm information is stored on the M2000. MBSC has buffer capability. A maximum of
300 thousand history alarm records can be stored.
MBTS alarm
MBTS alarms can be queried according to the site number, cell number, or TRX number
(applicable to BTS) so as to confirm the failure and clearance sates.
MBTS alarms can be queried and displayed on both the alarm console at the remote end and
the Site Maintenance System at the local end.
The MBTS alarm supports the input interface of the environment alarm. The environment
alarms supported by the MBTS are fire, smoke, temperature, humidity, door control, and main
supply alarms. The ranges of alarms can be controlled by alarm threshold setting on the
MBSC. The MBTS also supports the function of clearing environment alarms to provide
flexible clearance of the alarms.

Issue V1.71 (2009-09-10) Page 113 of 145
Enhancement
UMTS
z RAN5.1 supports the handling of HSDPA related alarms.
z RAN6.0 supports the handling of HSUPA related alarms.
z RAN6.0 supports the E1/T1 BER measurement.
z RAN10.0 supports the fault diagnosis of the IP path.
z RAN10.0 supports the reporting of the status of the MSC resource pool.
z In RAN11.0, the RNC supports the alarms of external AC power.
GSM
z The GBSS8.0 supports the clearance of PS-related alarms, including device alarms and
service alarms.
z The GBSS8.1 supports suppression of the intermittent and repeated alarms, alarm
correlation processing, and enhanced alarm positioning information.
Dependency
None.
None.
None.
The fault management is implemented through the M2000 or the MBSC/MBTS LMT.
18.5 MRFD-210305 Security Management

Availability
Summary
This feature enhances the network security management by providing various user
authorization and management mechanisms.
Benefits
This feature provides user authorization and management mechanism, thus enhancing the
network security management.

Issue V1.71 (2009-09-10) Page 114 of 145
Description
Security management enhances the system security in terms of the following aspects:
z Facilitates user management such as the management of user accounts, user rights, and
user command groups.
z Supports the backup and restore of the system data.
z Adopts the Windows security policies for the IP services of the BAM to protect the
system from network attacks.
z Supports the installation of antivirus software such as Norton, Macfee, and Officescan.
z Collects the database operation logs and auditing logs.
z Reports corresponding alarms when network attacks are detected or the number of
unauthorized accesses exceeds the threshold.
z Supports FTP over the Security Socket Layer (SSL).
z Supports SSL for the communication between the OMC and the GBSS/RAN. This
enables the encryption of all transmitted data.
z Adds authority control for the binary interface between the GBSS/RAN and the OMC.
z Records the information about the operation logs for the binary interface between the
GBSS/RAN and the OMC.
Enhancement
UMTS
z RAN6.0 supports the SSL encryption of the FTP transmission.
z RAN10.0 supports the SSL encryption of the data transmitted between the GBSS/RAN
and the OMC.
z RAN11.0 supports the authority control and log recording for the binary interface
between the GBSS/RAN and the OMC.
GSM
None.
Dependency
None.
None.
None.
None.

Issue V1.71 (2009-09-10) Page 115 of 145
19 Message Tracing
19.1 MRFD-210801 Interface Message Tracing

Availability
Summary
This feature is used for interface message tracing in online/offline mode, tracing result review,
and routine equipment management.
Benefits
This feature simplifies the process of monitoring the signaling over the radio transmission
interfaces and facilitates network optimization and fault rectification.
Description
This feature is used for interface message tracing in online/offline mode and routine
equipment management.
With this feature, the GBSS/RAN can trace messages in real time, stop updating, save the
tracing messages, review the tracing result, and check the time when the message is sent. In
this way, the maintenance personnel can accurately locate and solve problems. In addition, all
the interfaces have the condition filtering function. Therefore, the maintenance personnel can
reduce the number of traced messages through condition filtering, thus improving the tracing
accuracy.
In the case of the GBSS system:
The BSSAP, MTP2, MTP3, and SCCP messages can be traced over the A interface as
required. The BSSAP messages can be filtered according to the message types such as the
BSSMAP, paging messages, and DTAP messages. You can also select the traced messages
according to the cell.
The RSL, OML, and LAPD messages can be traced over the Abis interface. The LAPD
messages can be filtered according to the site and TRX number. The RSL messages can be
filtered according to the message type, such as the measurement report, paging, and channel
request. The OML messages can also be filtered according to the message type.
The application layer messages and the LAPD messages can be traced over the Pb interface.
The LAPD message can be selected and traced according to the timeslot number. The
application layer messages can be traced according to the site number and the message types
such as paging.
In the case of the RAN system:
The operator can verify the configuration data, locate and solve problems by tracing the
messages over the Iu, Iub, Iur, and Uu interfaces. After the configuration data is set, the
operator can determine the correctness of the signaling links by tracing and interpreting the
messages over the Iu, Iub, Iur, and Uu interfaces. The operators can also locate exceptions
when exceptions occur.
Therefore, tracing and interpreting the messages over the Iu, Iub, Iur, and Uu interfaces can
take the place of the signal analyzer to perform the interoperability test between the RNC and
other network elements.
All the interfaces can filter the messages according to the message layer or the logical object.
In this way, the number of traced maintenance signaling can be greatly reduced. Thus, the
tracing accuracy is improved and the problem location speed is accelerated.
Operators can also use this feature to optimize the network.
Enhancement
UMTS
None.
GSM
z The GBSS8.0 supports the tracing over the Gb interface and the packet message tracing
over the Um interface.
z GBSS8.1 supports the tracing of the VGCS/VBS messages
Dependency
None.
None.
None.
None.
19.2 MRFD-210802 User Signaling Tracing

Availability

Issue V1.71 (2009-09-10) Page 117 of 145
Summary
With this feature, the signaling of an MS can be traced on the GBSS/RAN side. In a tracing
window, all the signaling of an MS in the GBSS/RAN can be traced. In addition, you can
manage the tracing task, save the messages, and review the tracing result.
Benefits
This feature facilitates the monitoring of the radio signals and transmission interfaces of
specified MSs and thus facilitates network optimization and fault rectification.
Description
With this feature, the characteristic words of the called MS are entered on the LMT for tracing
the signaling of the calling MS. The characteristic words include IMSI, TMSI, MSISDN, and
IMEI. The host decodes the signaling of each call. If the information of the MS matches the
characteristic words of the MS to be traced, the signaling of this call is returned to the LMT
for display. This feature traces the signaling of an MS on various interfaces, saves the
messages, and reviews the tracing result. In this way, the message tracing on each interface
can be avoided, thus improving the troubleshooting efficiency and facilitating the problem
locating of an MS.
With this feature, the signaling of the specified MS is traced to evaluate the network status,
based on which operators can perform network optimization.
Enhancement
UMTS
None.
GSM
GBSS8.1 supports the PS single user tracing and VGCS/VBS message tracing.
Dependency
None.
None.
None.
None.

Issue V1.71 (2009-09-10) Page 118 of 145
20 Software Management
20.1 MRFD-210401 BSC/RNC Software Management

Availability
Summary
This feature provides functions of software installation, software upgrade, and patch
installation of the MBSC. This facilitates the remote management of the MBSC software.
Benefits
This feature provides functions of software installation, software upgrade, and patch
installation of the MBSC, thus reducing the O&M cost for operators.
Description
The MBSC supports the software management. This feature facilitates the remote
management of the MBSC software. The operators can run the MML commands to:
z Query the information about the software version and other information about the
running system.
z Upload, download, and activate the program file, patch file, and license file, and copy
the data files and log files to the FTP server.
z Use the BAM server of the MBSC as the FTP server and transmit files such as program
file and patch file by using the wildcard between the FTP server and the FTP client.
z Perform the remote patch upgrade of the BAM server of the MBSC.
z Use the MBSC as the transmission medium to transmit files between the M2000 and the
MBTS.
In addition, the operators can control the product software through the operation and
maintenance center (OMC), including the program, patch, license, data, and log. The OMC
can identify and match the product software version. In this way, the efficiency of product
upgrade and data downloading is improved.
Enhancement
UMTS

Issue V1.71 (2009-09-10) Page 119 of 145
z RAN5.1 supports the remote patch upgrade of the RNC BAM.

z RAN6.1 supports the software management based on two versions, thus facilitating the
upgrade and rollback of versions.
z RAN10.0 supports the combined patch management functions of the BAM and RBS.
z RAN11.0 supports the validity check of the configuration scripts before upgrade and
supports the verification of the system configuration after upgrade. This reduces manual
intervention during upgrade and improves the upgrade efficiency and reliability.
z RAN11.0 significantly shortens the duration of service disruption caused by the upgrade
of a fully-configured RNC. In this way, the upgrade with a minimal loss, which is
applicable only to the BSC6810, is achieved.
GSM
z GBSS8.1 supports the remote upgrade of the BSC and BTS software.
Dependency
None.
None.
None.
None.
20.2 MRFD-210402 BTS/NodeB Software Management

Availability
Summary
This feature enables the operator to remotely manage the software installation and upgrade of
the MBTS. This feature supports enhanced functions such as automatic change of the
signaling bandwidth, software downloading based on the configuration, software
downloading resumption, downloading and activation of software in batches, and hot
patching.
Benefits
This feature provides efficient and accurate software installation, software upgrade, and
software version management.

Issue V1.71 (2009-09-10) Page 120 of 145
Description
This feature helps the operator to remotely manage the MBTS software. The operator can
perform the following operations through MML commands:
z Efficient and correct installation and upgrade of the software
z Check on compatibility of the software and hardware versions to ensure successful
software installation and upgrade
z Version management, for example, the hardware and software version query
z Automatic data conversion during the software upgrade
The process of upgrading the software of the network element is as follows:
z Download the software package from the OMC M2000 to the MBTS through the
OMCH.
z Run the software activation command on the OMC M2000 client.
z The MBTS automatically loads the software to the corresponding board and switches
over the active and standby directories on the MBTS.
The following are the enhancement features of the MBTS software management:
z UBR/UBR+ is supported on the OMCH. When the traffic is heavy, the OMCH rate is
fixed at 64 Kbit/s. When the traffic is light, the OMCH bandwidth is automatically
increased to increase the software downloading efficiency.
z Software downloading based on the configuration can reduce 30% of the software
package and shorten the downloading time. When a board is added, the system supports
only the software downloading for the corresponding board to improve the downloading
efficiency.
z If the network recovers in 24 hours after the network breakdown, the system supports
software downloading resumption to avoid that the software is downloaded repeatedly.
z A maximum of 500 MBTSs can be selected to download and activate the software in
batches automatically. The default value is 50 MBTSs in one batch.
z Hot patching without resetting the MBTS is supported to minimize the negative impact
on the traffic.
Enhancement
In RAN5.1, the following enhancement features are introduced:
z UBR supported on the OMCH
z Software downloading based on the configuration
z Software downloading resumption
z Downloading and activation of the software in batches
z Hot patching
Dependency
None.
None.

Issue V1.71 (2009-09-10) Page 121 of 145

None.
None.
20.2.2 MRFD-210310 BTS/NodeB Software USB Download

Availability
Summary
With this feature, the user or the maintenance personnel can download and activate the MBTS
software through the USB without using the laptop. Thus, the MBTS can be set up easily and
quickly.
Benefits
With this feature, the software upgrade is independent of Abis/Iub transmission. Thus, the
upgrade is shortened and the MBTS can be set up quickly with a low cost. In addition, the
maintenance personnel need not enter the site again because they can perform the software
commissioning remotely.
Description
The 3900 series MBTSs provide the USB port to download and activate the host software.
After the MBTS hardware is installed, the system automatically upgrades the software when
the USB disk is inserted.
This feature enables the software upgrade to be performed through the USB without using a
laptop. With this feature, the software upgrade is independent of Abis/Iub transmission. Thus,
the upgrade is shortened and the MBTS can be set up quickly with a low cost. After the
software is activated and the system begins to operate, the hardware fault can be detected
according to the indicator on the BBU panel so that the fault is rectified in the shortest time.
In addition, the maintenance personnel need not enter the site again because they can perform
the software commissioning remotely.
Enhancement
None.
Dependency
Impact on the hardware of the MBSC
None.
Impact on the hardware of the MBTS
This feature should be supported by the 3900 series MBTSs.

Issue V1.71 (2009-09-10) Page 122 of 145
None.
None.
20.3 WRFD-031100 BOOTP

Availability
Summary
The bootstrap protocol (BOOTP) enables the IP addresses to be obtained through the server
automatically. In ATM transmission mode, the Node B capable of BOOTP can automatically
create an O&M channel to the RNC, thus saving the O&M cost at the near end. This feature
describes the method of implementing the Node B BOOTP.
Benefits
This feature enables the automatic setup of the default maintenance channel from the far end.
It also enables maintenance personnel to load the data and software to the Node B, thereby
facilitating the maintenance of the network.
Description
Generally, after the hardware installation, the Node B only has the host software rather than
the data configuration file. This feature enables Node B to set up the OM channel to the RNC
automatically without configuration data. The maintenance staff can download the data and
software to the Node B through the OMCH at the far end. The feature decreases the operation
and maintenance costs and enhances the network maintainability and maintenance quality.
Node B will automatically set up the O&M channel using the BOOTP protocol. In addition,
Node B monitors the O&M channel. When the O&M channel is broken, Node B can rebuild
it.
Enhancement
None.
Dependency
None.
20.4 WRFD-031101 DHCP

Availability

Issue V1.71 (2009-09-10) Page 123 of 145
Summary
The Node B obtains the IP address of the FE port and the OMCH addresses of the gateway
and equipment through the dynamic host configuration protocol (DHCP). In IP transmission
mode, the Node B capable of DHCP can automatically create an O&M channel to the RNC,
thus saving the O&M cost at the near end. This feature describes the implementation method
of the Node B DHCP.
Benefits
This feature enables the automatic setup of the default maintenance channel from the far end.
It also enables maintenance personnel to load the data and software to the Node B, thereby
facilitating the maintenance of the network
Description
In IP mode, the IP maintenance channel is automatically set up through the DHCP.
The dynamic host configuration protocol (DHCP) is 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, and 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 Node Bs work as clients.
Through the DHCP procedure, the Node Bs 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.

Issue V1.71 (2009-09-10) Page 124 of 145
21 License Management
21.1 MRFD-210403 License Management

Availability
Summary
This feature involves the MBSC license control and MBTS license control.
Benefits
With this feature, the operators can purchase the license based on the network development,
thus reducing the initial cost of the network deployment.
Description
The license file is used to determine whether the optional features are available and how
many optional features are available.
The MBSC and the BTS share one license file. The NodeB uses its own license file. The
license files can be downloaded remotely to the MBSC and NodeB. The operators can
manage and query the contents in the license file through the LMT or the M2000 client.
The characteristics of the MBSC license management are as follows:

z The MBSC and BTS share one license file.
z The license file is downloaded from the M2000 and is controlled and activated on the
MBSC side.
z The license can be used within one MBSC but not between the MBSCs.
The characteristics of the NodeB license management are as follows:
z All the NodeBs under one RNC share one license file. That is, one RNS corresponds to
one license file. Each license file records the license information about all NodeBs in the
RNS.
z The license is distributed on the M2000 and is controlled by the NodeB. The distribution
results are sent to the NodeB from the M2000.
z The license information can be distributed between NodeBs but not between RNCs. The
total number of a control item cannot exceed the number recorded in the license file.
New or upgraded license files can be ordered from Huawei.
Enhancement
None.
Dependency
None.

Issue V1.71 (2009-09-10) Page 126 of 145
None.
None.
None.

Issue V1.71 (2009-09-10) Page 127 of 145
22 Basic Node B Functions
22.1 MRFD-210309 DBS Topology Maintenance

Availability
This feature is available from GBSS8.0 in the GSM and RAN 5.0 in the UMTS.
Summary
The LMT provides the topology maintenance for the distributed base station, and thus
facilitates the maintenance operations.
Benefits
This feature provides convenient O&M functions for the distributed base station, thus
reducing the O&M expenditure of the operators.
Description
The distributed base station supports the automatic scan of the RRU topology. The LMT
provides the topology maintenance for the distributed base station. The functions that
supported by this feature are as follows:
z The networking structure of the distributed base station is displayed in a visualized way.
z Different colors are used to mark the status of each BBU, RRU, and CRPI link.
z The BBU or RRU can be selected directly from the displayed topology for maintenance.

Issue V1.71 (2009-09-10) Page 128 of 145
Figure 22-1 UMTS NodeB topology
Figure 22-2 GSM base station topology
Enhancement
The RAN6.0 supports the automatic scan of the RRU topology.
Dependency
None.
None.

Issue V1.71 (2009-09-10) Page 129 of 145

None.
None.
22.2 WRFD-031000 Intelligently Out of Service

Availability
Summary
This feature is introduced to prevent service disruption caused by insufficient battery voltage,
Node B reset, or cell blocking. When the preceding problems occur, this feature enables the
Node B to automatically reduce the pilot transmit power and hand over the UE to other 2G or
3G cells, thus preventing call drops.
Benefits
This feature allows the traffic to be switched to other 2G or 3G cells without dropping the
calls before the cell is out of service.
Description
The state of out of service is automatically triggered in the following cases:
z Voltage of the batteries is lower than the pre-set threshold after the AC power is shut
down
z Reset of the Node B
z 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.

Issue V1.71 (2009-09-10) Page 130 of 145
22.3 WRFD-031200 OCNS

Availability
Summary
In the system performance test, considering the limitations to the number of UEs and the
complexity of the test environment, it is difficult to use multiple UEs to construct a radio
transmission environment with certain interference. This feature enables the setup of multiple
downlink analog channels on the Uu interface to simulate the interference of multiple codes,
thus implementing the downlink load test of a cell.
Benefits
The feature provides an embedded function to simulate the cell load in the Node B. It makes
the cell load test more convenient.
Description
When the orthogonal code noise simulator (OCNS) is used, all analog channels use mutually
orthogonal channel codes and each channel code adopts irrelevant PN9 random data. All
analog channels use different powers, but the power proportion between channels is fixed.
This feature is used to simulate the signal interference between channel codes and signal PAR
in the real environment. The total power of all analog channels can be set to simulate different
downlink interference (load) levels, which facilitates the operator to evaluate the system
performance of a real UE in different downlink load levels.
This feature is performed on the OMC, and the cell load test of multiple Node Bs can be
started simultaneously.
Enhancement
None.
Dependency
None.
22.4 WRFD-010212 Improved CE Mapping for E-DCH

Availability
Summary
This feature improves the uplink processing capability of the WBBPb board and makes
HSUPA services occupy less CE resources, thus improving the CE efficiency of the Node B
and saving the investment cost of the operator.

Issue V1.71 (2009-09-10) Page 131 of 145
Benefits
Improve the CE efficiency, decrease the configured CEs.
Description
With the improved uplink processing capability of the WBBPb, HSUPA services occupy less
CE resources. The following table lists the occupation of CE resources.
Spreading Factor Former CE Mapping Improved CE Mapping
SF64 1 1
SF32 1.5 1
SF16 3 2
SF8 5 4
SF4 10 8
2SF4 20 16
2SF2 32 32
2SF2+2SF4 48 48
Enhancement
None.
Dependency
Only the 3900 series Node B supports this feature. And the 3900 series Node B must
configure WBBPa.
WRFD-010612 HSUPA Introduction Package

Issue V1.71 (2009-09-10) Page 132 of 145
23 Documentation
23.1 MRFD-210701 Documentation

Availability
Summary
The feature describes the available documentation of the products.
Benefits
With this feature, the operators can obtain the product information and can perform
maintenance operations accordingly.
Description
The customer documentation includes the following documents:
z MBSC documents
z NodeB documents
z BTS documents
The documentation covers the hardware description, installation, commissioning, operation,
and maintenance of the MBSC and MBTS.
The following table describes the documents:
Document Category Description
Product Description Describes the architecture, hardware configuration,

operation and maintenance, and technical specifications of
the product.
Hardware Description Describes the hardware of NEs, such as the cabinet, board,
and cable.
Installation Guide Describes the procedures for installing the cabinet, boards,
and cables.
Initial Configuration Guide Describes how to perform the initial configuration of NEs.
Document Category Description
Commissioning Guide Describes how to commission the NE to ensure that the

new NE can gain access to the BSS/RAN system.
LMT User Guide Describes the GUI, functions, and operations of the LMT.
Site Maintenance Guide Describes the hardware maintenance items and the
component replacement procedures
Routine Maintenance Guide Describes the routine maintenance methods of the MBSC
and MBTS.
Reconfiguration Guide Describes the common tasks and methods of data
reconfiguration of the MBSC and MBTS.
Reference The reference documents are as follows:
z MML command reference: describes the information
about meanings, recommended values, and default values
of the parameters of each command.
z Alarm reference: describes the information about
meanings of the alarms and how to clear them.
z Performance counter reference: describes the information
about meanings and measurement points of each counter.
The documents have the following characteristics:

z Topic-oriented: Based on the DITA technology, the information is provided under
separate topics.
z Powerful advanced search: The information can be searched according to products or
data types.
Enhancement
None.
Dependency
None.
None.
The documentation CD-ROM is delivered with the product.
None.

Issue V1.71 (2009-09-10) Page 134 of 145
24 Node B Antenna System Solution
24.1 MRFD-210601 Connection with TMA (Tower

Mounted Amplifier)
Availability
Summary
This feature provides a solution to the TMA connection. Huawei MBTS complies with the
AISG1.1 and AISG2.0 protocols.
Benefits
In the uplink coverage-limited network, the use of the TMA can improve the receiver
sensitivity, enlarge the cell radius, reduce the number of MBTSs, and save the cost.
Description
The TMA is used to amplify the uplink signals. It is an optional device for the antenna and
feeder system. The TMA can compensate the feeder loss caused by long feeders. Thus, the
uplink sensitivity is increased and the uplink coverage capability is improved.
Huawei MBTS supports the third-party TMA, including AISG TMA.
The MBTS supplies power to and controls the TMA. Huawei MBTS can provide 10 V to 13
V output voltage to the TMA. When a major alarm related to the TMA is reported, the system
automatically sets the attenuation value of the RX channel to 0. After the alarm is cleared, the
system automatically sets the attenuation value of the RX channel to the configured value.
In the case of the AISG TMA, the RET control signal, power, and RF signal are transmitted
through the feeder cable. Thus, operation and maintenance of the AISG TMA is easy. Smart
bias tee (SBT) provides power supply to the TMA and the RET control signal to the RCU
through the feeder cable.
Huawei provides dual TMAs. Each TMA consists of two TX/RX branches, and only one
TMA is required in each sector. Each TMA includes also a supervision and alarm unit in the
low noise amplifier (LNA). The functions of both branches are the same and the function of
one pair of branches is described as follows.

Issue V1.7 (2009-04-15) Page 135 of 145
The RX channel of each branch consists of two RX filters and an LNA. The LNA can be
automatically bypassed when the DC is faulty. There is a bias tee in the BTS port of the TMA.
For the SMART TMA, this bias tee is called the smart bias tee. Bias tee can separate the DC
current from the RF signals and provide power supply to the LNA and the RET control signal
to the RCU. The TX channel includes a TX filter.
Huawei MBTS supports two kinds of TMA with the gain of 24 dB and 12 dB.
Enhancement
GSM
z The GBSS6.1 complies with the AISG1.1 protocol.
UMTS
z The RAN5.0 supports STMA and complies with the AISG1.1 protocol.
z The RAN6.1 supports STMA and complies with the AISG2.0 protocol.
Dependency
None.
None.
None.
None.

Issue V1.71 (2009-09-10) Page 136 of 145
24.2 MRFD-210602 Remote Electrical Tilt

Availability
Summary
The feature provides a solution to remote adjustment of the antenna tilt. The user can adjust
the remote electrical tilt (RET) antenna tilt on the M2000 or LMT.
Benefits
This feature provides the following benefits:
z The RET antennas in multiple sites can be remotely adjusted, thus the efficiency of
adjusting the antenna tilt is improved and the cost of network optimization is reduced.
z The adjustment of the RET antenna is not affected by the weather.
z It is easy to adjust the RET antenna of a site that is difficult to reach.
Description
The tilt of the RET antenna can be adjusted remotely.
After an antenna is installed, the antenna tilt needs to be adjusted to optimize the network.
The antenna tilt can be remotely adjusted through the electrical control.
The phase shifter of the antenna can be controlled by the stepper motor outside the antenna.
You can adjust the antenna tilt when the system is powered on and monitor the tilt in real time.
Therefore, the precise remote adjustment of the antenna tilt can be achieved.
The following figure shows the operating principle of the RET antenna.
Figure 24-1 Working principle of the RET antenna
Radome
Phase shifter
Pulling bar
RCU
Control cable
(DC+ control signals)

Issue V1.71 (2009-09-10) Page 137 of 145
Remote Control Unit (RCU) is the driving motor of the phase shifter of the RET antenna. The
RCU receives and executes the control commands from the MBTS to drive the stepper motor.
A pulling bar connects the stepper motor and the phase shifter. When the stepper motor is
triggered, the pulling bar moves and then the phase of the phase shifter changes through the
gears. In this situation, the phase of each element of the array antenna changes regularly. Then,
the direction of the main beam of the antenna changes accordingly. Thus, the antenna tilt is
adjusted.
The MBTS supplies the DC power to the stepper motor and communicates with it through the
AISG interface on the motor.
In the Huawei RET solution, the RET antenna can be controlled remotely or locally through a
command sent from the M2000 or LMT.
The MBTS modulates that command to the On-Off-Keying (OOK) signals. The RF module
transfers the DC power and the OOK signals to the STMA or the SBT through the feeder
cables. The STMA or the SBT demodulates the OOK signals to RS485 signals and then sends
the RS485 signals and part of the DC power to the RCU. No additional control cable is
required.
The Huawei RET solution supports the RET cascading control. Several cascading RET
antennas can be controlled by the signals coming from the same control cable. The cascading
solution helps save the cost of the SBTs.
Sector 1 Sector 2 Sector 3
Antenna Antenna Antenna

RCU
RCU
RCU
SBT
MBTS
The Huawei RET solution supports the 2G/3G RET cascading control. The 3G RET antennas
can be cascaded with the 2G RET antennas. At the OMC of the 2G RET antenna, you can
control the tilt of the 3G RET antenna. Meanwhile, at the OMC of the 3G RET antenna, you
can control the tilt of the 2G RET antenna. The cascading helps save the cost of SBTs and
STMAs when the 2G and 3G RET antennas are installed in the same place.

Issue V1.71 (2009-09-10) Page 138 of 145
Dual-band Antenna
RCU
RCU
2G
3G SBT
3G/2G NodeB 2G/3G BTS
Enhancement
GSM
None.
UMTS
z In RAN6.0, the 3G RET cascading control and 2G/3G RET cascading control are
supported.
z RAN6.1 complies with the AISG2.0 protocol.
Dependency
None.
1) BTS
This feature is supported by the all types of BTSs except for the BTS3600C and BTS3002E.
2) Node B
None.
3) MBTS
None.

Issue V1.71 (2009-09-10) Page 139 of 145

None.
None.
24.3 WRFD-060003 Same Band Antenna Sharing Unit (900

MHz)
Availability
Summary
This feature enables UMTS900 and GSM900 to share the same band antenna. The description
of this feature focuses on the working principle and configuration of the SASU900.
Benefits
This feature helps to share the same band antenna and decrease the uplink division loss.
Compared with the traditional combiner and diplexer, it achieves3 dB gains.
Description
SASU900 can combine two same band signals into one with very low insertion loss when the
old system uses diversity antennas. Its basic guidance is as follows:
The downlink Tx signals in two different systems use two different antenna channels of one
dual-polarized antenna. One signal uses the main antenna and the other signal uses the
diversity antenna. Hence, there is less Tx insertion loss. In terms of the Rx signal, the Rx
signal of each antenna channel is separated into two paths. One signal is used as the main Rx
signal of the system, and the other signal is used as the diversity Rx signal of the other system.
Hence, the Rx splitter results in Rx insertion loss, which can be compensated by adding a
Lower Noise Amplifier (LNA).
The SASU900’s connection diagram in the system is as follows:

Issue V1.71 (2009-09-10) Page 140 of 145
The configuration of the SASU900 in the GSM900 and UMTS900 co-site system
Note: We define the ANT_M as the main antenna port of the UMTS, and the ANT_D as the
diversity antenna port of the UMTS. In GSM, the ANT_D is the main antenna port and the
ANT_M is the diversity antenna port.
There is a limitation when using the SASU: The GSM uses only one antenna branch.
To allow GSM two antennas, the SASA (Same Band Antenna Sharing Adapter) is introduced.
The SASA is mainly used to combine two branches of GSM carriers into one antenna branch,
and keep the combination/division loss as low as possible. When sharing the antenna with
WCDMA, the GSM carriers prefer to be located separately as a “sandwich”.

Issue V1.71 (2009-09-10) Page 141 of 145
Figure 24-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.

Issue V1.71 (2009-09-10) Page 142 of 145
Dependency
None.

Issue V1.71 (2009-09-10) Page 143 of 145
25 Acronyms and Abbreviations
Table 25-1 Acronyms and Abbreviations
Acronym and Abbreviation Expansion
3G The Third Generation

AP Access Point
APM Advanced Power Module
AQM Active Queue Management
BBU Baseband Unit
BITS Building Integrated Timing Supply System
BTS Base Station
CBS Cell Broadcast Service
CPC Continuous Packet Connectivity
CPE Customer Premises Equipment
DNBS Distributed Node B System
DSAC Domain Specific Access Control
ETSI European Telecommunications Standards Institute
FTP File Transfer Protocol
GIS Geographical Information System
GA General Available
GBR Guaranteed Bit Rate
GLONASS GLObal Navigation Satellite System
GPS Global Position System
HCS hierarchical Cell Structure
HSDPA High Speed Downlink Packet Access

Issue V1.7 (2009-04-15) Page 144 of 145
Acronym and Abbreviation Expansion
HSUPA High Speed Uplink Packet Access

LCS Location Service
LTE Long Term Evolution
MBMS Multimedia Broadcast Multicast Service
MIMO Multi-Input Multi-Output
NACC Network Assisted Cell Change
PA Power Amplifier
PARC Platform Advanced Radio Control
PPS Pulse Per Second
QAM Quadrature Amplitude Modulation
RAN Radio Access Network
RET Remote Electrical Antenna
RNC Radio Network Controller
ROHC Robust Header Compression
RRM Radio Resource Management
SAE System Architecture Evolution
SASA Same Band Antenna Sharing Adapter
SASU Same Band Antenna Sharing Unit
SNA Shared Network Area
TGW Transmission Gateway
VoIP Voice over IP
WCDMA Wideband Code Division Multiple Access

Issue V1.71 (2009-09-10) Page 145 of 145

Basic Feature Description of Huawei UMTS RAN11.1 V1.1

Diunggah oleh

Informasi Dokumen

Hak Cipta

Format Tersedia

Bagikan dokumen Ini

Bagikan atau Tanam Dokumen

Opsi Berbagi

Apakah menurut Anda dokumen ini bermanfaat?

Apakah konten ini tidak pantas?

Hak Cipta:

Format Tersedia

Basic Feature Description of Huawei UMTS RAN11.1 V1.1

Diunggah oleh

Hak Cipta:

Format Tersedia

Basic Feature Description of Huawei

HUAWEI TECHNOLOGIES CO., LTD.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Telephone: 0755-28560000 4008302118

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

2 Standards Compliance ...............................................................................................................17

3 RABs and Services ......................................................................................................................20

4 RAN Architecture & Functions ................................................................................................30

Huawei Proprietary and Confidential

5 Channel Resource Management ..............................................................................................39

6 Network Security ........................................................................................................................49

7 Power Control ..............................................................................................................................52

8 Cell Management ........................................................................................................................57

9 Network Sharing .........................................................................................................................65

10 Mobility Management .............................................................................................................68

11 Node B Networking Modes ....................................................................................................77

Huawei Proprietary and Confidential

13 ATM Transmission Introduction Package ...........................................................................85

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

15 UBR+ATM QoS Class ..............................................................................................................96

16 Link Aggregation ......................................................................................................................97

18 RAN Operation & Maintenance...........................................................................................104

20 Software Management ...........................................................................................................119

22 Basic Node B Functions .........................................................................................................128

Huawei Proprietary and Confidential

22.1 MRFD-210309 DBS Topology Maintenance............................................................................................. 128

24 Node B Antenna System Solution .......................................................................................135

25 Acronyms and Abbreviations...............................................................................................144

Huawei Proprietary and Confidential

1.1 WRFD-000001 System Improvement for RAN5.1

Huawei Proprietary and Confidential

1.2 WRFD-000002 System Improvement for RAN6.0

Huawei Proprietary and Confidential

Huawei Proprietary and Confidential

1.3 WRFD-000003 System Improvement for RAN6.1

Huawei Proprietary and Confidential

1.4 WRFD-000004 System Improvement for RAN10.0

Huawei Proprietary and Confidential

Huawei Proprietary and Confidential

Huawei Proprietary and Confidential

1.5 WRFD-000005 System Improvement for RAN11.0

Huawei Proprietary and Confidential

1.6 WRFD-000006 System Improvement for RAN11.1

Huawei Proprietary and Confidential

Huawei Proprietary and Confidential

2.1 WRFD-010101 3GPP R7 Specifications

Huawei Proprietary and Confidential

2.2 WRFD-010102 Operating Multi-band

Operating Band UL Frequencies DL frequencies

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

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

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

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

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

Huawei Proprietary and Confidential

Different frequency bands should be configured with different RF modules.

2.3 WRFD-010201 FDD Mode

Huawei Proprietary and Confidential

3 RABs and Services

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

Huawei Proprietary and Confidential

− WRFD-010612 HSUPA Introduction Package

3.2 WRFD-010501 Conversational QoS Class