Function Description of UMTS RAN10.0(Basic).pdf

Basic Feature Description of Huawei UMTS RAN10.0

Basic Function Description of Huawei UMTS RAN10.0

Huawei UMTS RAN Basic Function Description Document Version V1.0

Product Version RAN10.0

Huawei Technologies Co., Ltd. provides customers with comprehensive technical support and service. Please feel free to contact our local office or company headquarters.

Huawei Technologies Co., Ltd.

Address: Administration Building, Huawei Technologies Co., Ltd.,

Bantian, Longgang District, Shenzhen, P. R. China

Postal Code: 518129

Website: http://www.huawei.com

http://www.huawei.com


Copyright © 2007 Huawei Technologies Co., Ltd.

All Rights Reserved.

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

written consent of Huawei Technologies Co., Ltd.

Trademarks

and other Huawei trademarks are the trademarks or registered trademarks of Huawei

Technologies Co., Ltd. in the People’s Republic of China and certain other countries.

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

respective holders.

Notice

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

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

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


Commercial in Confidence i

Table of Contents

1 System Improvement Introduction...........................................................................................1 1.1 WRFD-000001 System Improvement in RAN5.1 ...............................................................1 1.2 WRFD-000002 System Improvement in RAN6.0 ...............................................................3 1.3 WRFD-000003 System Improvement in RAN6.1 ...............................................................5 1.4 WRFD-000004 System Improvement in RAN10.0 .............................................................7

2 Standards Compliance..............................................................................................................9 2.1 WRFD-010101 3GPP R6 Specifications............................................................................9 2.2 WRFD-010102 Operating Multi-band...............................................................................10 2.3 WRFD-010201 FDD Mode ..............................................................................................12

3 RABs and Services .................................................................................................................13 3.1 WRFD-010510 3.4/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release...................................................................................................13 3.2 WRFD-010501 Conversational QoS Class ......................................................................15 3.3 WRFD-010502 Streaming QoS Class..............................................................................17 3.4 WRFD-010503 Interactive QoS Class .............................................................................19 3.5 WRFD-010504 Background QoS Class...........................................................................20 3.6 WRFD-010609 Multiple RAB Introduction Package (PS RAB < 2) ...................................21

3.6.1 WRFD-01060901 Combination of Two CS Services (Except for Two AMR Speech Services) .......................................................................................................................22 3.6.2 WRFD-01060902 Combination of One CS Service and One PS Service ...............23 3.6.3 WRFD-01060903 Combination of Two CS Services and One PS Service (Except for Two AMR Speech Services) ..........................................................................................24

3.7 WRFD-021104 Emergency Call ......................................................................................25

4 RAN Architecture & Functions ...............................................................................................26 4.1 WRFD-010204 2-Antenna Receive Diversity ...................................................................26 4.2 WRFD-010205 Cell Digital Combination and Split ...........................................................27 4.3 WRFD-010208 Fast Power Congestion Control (FCC) ....................................................29 4.4 WRFD-010211 Active TX Chain Gain Calibration ............................................................30 4.5 WRFD-021301 Shared Network Support in Connected Mode..........................................31 4.6 WRFD-010202 UE State in Connected Mode (CELL-DCH, CELL-PCH, URA-PCH, CELL-FACH) ........................................................................................................................33 4.7 WRFD-010401 System Information Broadcasting............................................................35 4.8 WRFD-010301 Paging UE in Idle, CELL_PCH, URA_PCH State (Type 1).......................37 4.9 WRFD-010302 Paging UE in CELL_FACH, CELL_DCH State (Type 2)...........................38 4.10 WRFD-020900 Logical Channel Management...............................................................39 4.11 WRFD-021000 Transport Channel Management ...........................................................41


Commercial in Confidence ii

4.12 WRFD-022000 Physical Channel Management.............................................................42 4.13 WRFD-011401 Integrity Protection ................................................................................48 4.14 WRFD-011402 Encryption.............................................................................................49 4.15 WRFD-020501 Open Loop Power Control .....................................................................50 4.16 WRFD-020502 Downlink Power Balance.......................................................................52 4.17 WRFD-020503 Outer loop Power Control......................................................................53 4.18 WRFD-020504 Inner Loop Power Control .....................................................................54 4.19 WRFD-020101 Admission Control.................................................................................55 4.20 WRFD-020102 Load Measurement ...............................................................................58 4.21 WRFD-020106 Load Reshuffling...................................................................................60 4.22 WRFD-020107 Overload Control...................................................................................62 4.23 WRFD-020108 Code Resource Management................................................................63 4.24 WRFD-021101 Dynamic Channel Configuration Control (DCCC)...................................64 4.25 WRFD-021201 RNC Resource Sharing.........................................................................66 4.26 WRFD-020201 Intra NodeB Softer Handover ................................................................67 4.27 WRFD-020202 Intra RNC Soft Handover ......................................................................69 4.28 WRFD-020203 Inter RNC Soft Handover ......................................................................70 4.29 WRFD-020301 Intra Frequency Hard Handover ............................................................71 4.30 WRFD-010801 Intra RNC Cell Update...........................................................................72 4.31 WRFD-010802 Inter RNC Cell Update...........................................................................74 4.32 WRFD-010901 Intra RNC URA Update .........................................................................75 4.33 WRFD-010902 Inter RNC URA Update .........................................................................76 4.34 WRFD-021400 Direct Signaling Connection Re-establishment (DSCR) .........................77

5 Transmission...........................................................................................................................78 5.1 WRFD-050101 Star Topology .........................................................................................78 5.2 WRFD-050102 Chain Topology.......................................................................................79 5.3 WRFD-050103 Tree Topology.........................................................................................80 5.4 WRFD-050201 NodeB Clock...........................................................................................82 5.5 WRFD-050202 RNC Clock..............................................................................................84 5.6 WRFD-050301 ATM Transmission Introduction Package ................................................85

5.6.1 WRFD-05030101 ATM over E1T1 on Iub Interface................................................86 5.6.2 WRFD-05030102 ATM over Channelized STM-1/OC-3 on Iub Interface................88 5.6.3 WRFD-05030103 ATM over Non-channelized STM-1/OC-3c on Iub/Iu/Iur Interface90 5.6.4 WRFD-05030104 Dynamic AAL2 Connections on Iub/IuCS/Iur Interface...............92 5.6.5 WRFD-05030105 Permanent AAL5 Connections for Control Plane Traffic.............94 5.6.6 WRFD-05030106 Call Admission Based on Used AAL2 Path Bandwidth...............95 5.6.7 WRFD-05030107 CBR, rt-VBR, nrt-VBR, UBR ATM QoS Classes ........................96 5.6.8 WRFD-05030110 F5.............................................................................................97

5.7 WRFD-050304 IMA for E1T1 or Channelized STM-1/OC-3 on Iub Interface.....................98 5.8 WRFD-050305 UBR+ ATM QoS Class..........................................................................100


Commercial in Confidence iii

6 System Reliability..................................................................................................................101 6.1 WRFD-040100 Flow Control .........................................................................................101 6.2 WRFD-040201 System Redundancy .............................................................................103

7 RAN Operation & Maintenance.............................................................................................104 7.1 WRFD-030100 Performance Management....................................................................104 7.2 WRFD-030200 Fault Management ................................................................................106 7.3 WRFD-030300 Inventory management .........................................................................108 7.4 WRFD-030400 Configuration Management ...................................................................109 7.5 WRFD-030501 Security Management ...........................................................................111 7.6 WRFD-030601 Interface Tracing...................................................................................112 7.7 WRFD-030602 Call Tracing ..........................................................................................113 7.8 WRFD-030701 RNC Software Management..................................................................114 7.9 WRFD-030702 NodeB Software management ..............................................................116 7.10 WRFD-031100 BOOTP...............................................................................................118 7.11 WRFD-031101 DHCP .................................................................................................119 7.12 WRFD-030800 License Management..........................................................................120 7.13 WRFD-030900 High Efficiency DNBS OM...................................................................122 7.14 WRFD-031000 Intelligently Out of Service...................................................................123 7.15 WRFD-031200 OCNS.................................................................................................124 7.16 WRFD-031300 Documentation....................................................................................125

8 NodeB Antenna System Solution .........................................................................................127 8.1 WRFD-060001 Connection with TMA (Tower Mounted Amplifier) ..................................127 8.2 WRFD-060002 Remote Electrical Tilt ............................................................................129 8.3 WRFD-060003 Same Band Antenna Sharing Unit (900 MHz)........................................134


Commercial in Confidence Page 1 of 137

1 System Improvement Introduction

1.1 WRFD-000001 System Improvement in RAN5.1

Feature Number: WRFD-000001

Availability:

This feature is introduced in RAN5.1

Description

Compatibility with 3GPP Release 5

UMTS RAN5.1 is based on 3GPP Release 5, which adds a number of important functions for RAN as well as UEs. The major new feature is 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 CR's since then are implemented. HSDPA Phase 2 is enhancement of Phase 1 to provide 3.6Mbps/user downlink speed.

The 3GPP TR 25.933 IP transport in UTRAN is implemented in RAN5.1. RAN5.1 is the first version to provide Iub IP transmission. IP transmission provides new solution for last mile access of NodeB. It will bring cost saving for transmission.

Support of new products and configurations

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

I. RNC

l Supporting quakeproof cabinets that are suitable for scenarios of specific quakeproof requirements

II. NodeB

l DBS3800 supports 2carriers 40WRRU for Band II(1900 M)

l DBS3800 supports 2carriers 40WRRU for Band III(1800M) / IX (Japanese 1800M)

l New MTRU and RRU module support 40W output power on top of cabinet

l New transmission interface card NUTI supports FE ports

l BBU-interconnecting provides smooth expansion for DBS3800. The network can support evolution from 3x1 to 3x2.

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

Support high efficiency power amplifier

UMTS RAN5.1 introduced DPD + Doherty power amplifier.



The DPD (Digital pre-distortion) is linearity technology which features stability, wider signal band and ability to process multi-carrier signals. Doherty technology is to separately amplify the average part and the peak part of the input signal and then combine both to get high efficiency.

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

For NodeB BTS3812E/AE, the output power at the top of cabinet can be up to 40W. DBS3800, the output power at the top of cabinet can be up to 40W. Thanks to support two carriers and high output power for one RF module (MTRU or RRU), it is easy to smooth capacity expansion and no additional RF modules are required when single-carrier configuration is upgraded to dual-carrier configuration.

Enhancement

None.

Dependency

None.

Benefits

The benefits of the system improvements include:

l Wider product range, including new products and configurations

l Further improvements regarding stability and robustness, thanks to improved functions and algorithms

l Improved performance, including higher capacity

l Usability enhancements, reducing operating costs





Availability:


Description


UMTS RAN6.0 is based on 3GPP Release 6, which adds a number of important functions for RAN as well as UEs. The major new feature that is introduced in the 3GPP Release 6 is HSUPA. All relevant interfaces are updated according to the March 2006 version of Release 6.





l BTS3812E with support for 850 MHz and 900 MHz

l BTS3812A with support for850 MHz and 900 MHz

l DBS3800 with support for 850 MHz and 900 MHz

l iDBS3800, which is for indoor coverage.

l BTS3812AE, which is for outdoor coverage.

iDBS3800 is one of the best solutions for indoor coverage. iDBS3800 contains three parts: BBU (Base Band Unit), RHUB (Radio HUB) and Pico RRU (Pico Remote Radio Unit). The Pico RRU connected to the RHUB through CAT5 interface, and one RHUB can support maximum 8 Pico RRUs. The RHUB connected to the BBU through optic fiber, and the BBU can support maximum 24 RHUBs.

IDBS3800 supports multiple networking modes. It supports up to 192 RF front-end units. The RRU can be networked with PDAS or work as ADAS. The solution is applicable to requirements of buildings and districts at different scales.

IDBS3800 supports transmission over optic fibers or CAT 5 cables. The RHUB can also provide remote power supply to the Pico RRU. So it enjoys easy and fast deployment and reducing engineering cost.



Enhancement

None.

Dependency

None.

Benefits



l iDBS3800 is one of the best solutions for indoor coverage

l Usability enhancements, reducing operating costs





Availability:


Description





l BSC6810, new platform RNC based on IP switch for higher capacity with compact structure.

l Clock server, new equipment to provide synchronization signals for NodeB

l RRU3804C supports 60W TOC with A-Doherty 4 carrier in DBS3800 (2100MHz).

l DBS3800 supports UL 1700MHz / DL 2100MHz 40W TOC with Doherty 2 carrier PA

l 900MHz SASU（Same band Antenna Sharing Unit）, SASA（Same band Antenna Sharing Adapter）provide a solution for intra-band antenna system shared between GSM900 and UMTS900

l AISG version 2.0

RRU3804C is 4 carriers and high output power remote radio unit, 60W TOC. The RRU optimizes on mechanical layout, new slim shape lead to easy deployment. Due to natural heat dissipation, the RRU without fan improves the reliability and reduces the maintenance cost.

New features and enhancement

l IP transmission on Iu/Iur interface

IP transmission on Iu/Iur interface is introduced in RAN6.1, which will decrease the transport cost greatly compared with ATM transport cost.

l Iu flex enhancement

Iu flex enhancement includes enhanced load balancing and load re-distribution. This feature improves the performance and can meet the operator’s load distribution strategy in Iu flex networking scenario.



l RAN sharing phase2

In RAN sharing phase2, dedicated Iub transmission control is introduced, which refers to separated Iub transmission resource management for operators sharing the RAN. With this feature, operator’s differentiated QoS requirement is guaranteed.

l Other new features and enhancement

Please refer to the description and enhancement of following chapters and Optional Function Description of Huawei UMTS RAN6.1.

Enhancement

None.

Dependency

None.

Benefits



l BSC6810 provides higher capacity and tighter structure.

l New features and enhancement.





Availability:


Description

Compatibility with 3GPP Release 6 (2007-03)



l EBBI (Enhanced baseband Interface card) to support HSUPA Phase2 and more CEs. It can be mixed with all other boards in macro NodeB: BTS3812E/A, BTS3812AE.

l EBOI(Enhanced baseband optical interface card) to support RRU connection to macro NodeB: BTS3812E/A, BTS3812AE . EBOI also provide HSUPA phase2 and more CEs. It can be mixed with all other boards in macro NodeB.

l EULP (Enhanced uplink process card)to support HSUPA Phase2 and more CEs, used in macro NodeB:BTS3812, BTS3812A, BTS3812E, BTS3812AE. EULP can mix with other boards in macro NodeB.

l EBBC (Extension baseband card) to support HSUPA Phase2 and more CEs, used in distributed NodeB:BBU3806. The EBBC can be inserted to the BBU on site, with the BBU+EBBC, 6cells can be supported.

l GTPu re-array for unified interface board

l DBS3800 support 3carriers RRU for Band III(1800M) / IX (Japanese 1800M)

l New interface board in BSC6810 to support IP over channelized STM-1/OC-3 (CPOS)

New features and enhancement

l HSUPA Phase 2

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

- Peak rate: 5.76 Mbps/user (5.74 Mbps(MAC)/user)

- 2ms/10ms TTI

- Max users per cell : 60

- UL compress mode (10ms and 2ms)

- Enhanced fast UL scheduling

- SRB over HSUPA, etc.



l HSDPA Phase 4

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

- F-DPCH

- MBMS over HSDPA (PtP)

- HS-DPCCH preamble mode

- Peak rate: 14.4 Mbps/user (13.976 Mbps(MAC)/user)

- SRB over HSDPA, etc.

l HSPA over Iur

l VoIP over HSPA (trial)

l Enhanced MBMS broadcast

l RoHC (Robust Header Compression)

l Multi band HO based on service priority and band

l HS-DPCCH preamble

l AQM (Active Queue Management)

l IP transmission enhancement

Some new interface port are supported:

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

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

Enhancement for existing port:

- Backup between IP over E1 and IP over FE

- BFD and ARP checking, etc.

l Other new features and enhancement

Please refer to the description and enhancement of following chapters and Optional Function Description of Huawei UMTS RAN10.0.

Enhancement

None.

Dependency

None.

Benefits


l High output power amplifier for macro NodeB, extend the coverage and capacity. Fewer sites, better user experience.

l Higher throughput by support of HSUPA Phase 2 for faster UL speed and better possibility of introducing new applications.



2 Standards Compliance

2.1 WRFD-010101 3GPP R6 Specifications


Availability:


Description

RAN2.0 is compliant to 3GPP R4 and back compliant to R99.

RAN3.0/5.0 is compliant to 3GPP R5 and back compliant to R99 and R4.

Huawei RAN6.0/6.1 is compliant to 3GPP R6 2006-03+ CR and back compliant to R99, R4 and R5 simultaneously.

Huawei RAN10.0 is compliant to 3GPP R6 2007-03 and back compliant to R99, R4 and R5 simultaneously.

Enhancement

RAN10.0 is compliant to 3GPP R6 2007-03 and back compliant to R99, R4 and R5 simultaneously.

Dependency

For the features and IEs in the message introduced in Release6, CN node & UE are also required to be compliant to if they are related.

Benefits

With compliant to release6, the new features and enhancements introduced can be possible to support.



2.2 WRFD-010102 Operating Multi-band


Availability:

This feature is introduced in RAN 2.0.

Description

The following 3GPP defined UMTS frequency bands are supported.

Operating Band

UL Frequencies UE transmit, NodeB

receive

DL frequencies UE receive, NodeB

transmit Availability

I 1920 to 1980 MHz 2110 to 2170 MHz RAN2.0

II 1850 to 1910 MHz 1930 to 1990 MHz Macro:RAN5.0 RRU: RAN5.1

III 1710 to 1785 MHz 1805 to 1880 MHz Macro:RAN5.0 RRU: RAN5.1

V 824 to 849 MHz 869 to 894 MHz RAN6.0

VIII 880 to 915 MHz 925 to 960 MHz RAN6.0

IV 1710 to1755 MHz 2110 to 2155 MHz RRU: RAN6.1

IX 1749.9 to 1784.9 MHz 1844.9 to 1879.9 MHz RRU: RAN6.0

Macro NodeB BTS3812E/AE provides multi-band co-located in one cabinet. Since the flexibility design of Huawei NodeB architecture, multi-band only impact on the RF system. Base band modules including power, transmission, Channel cards are completely shared by different band. The operator can make use of the needed frequency segment; to save the footprint of the BTS, and improve the baseband usage.

The feature is implemented in the NodeB and RNC.

Different frequency band should be configured with different RF module. For macro NodeB BTS3812E/AE, the MAFU and MTRU with corresponding band should be configured. For DBS3800, the RRU with corresponding band should be configured.

Enhancement

In RAN5.0, Macro NodeB support 1900M and 1800M frequency band.

In RAN5.1, RRU support 1900M and 1800M frequency band.

In RAN6.0, 850M and 900M frequency band is supported by Macro NodeB and RRU.

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

Dependency

None.



Benefits

NodeB can be deployed widely according the operator’s brand license.

Multi-band supported NodeB can save the hardware investment.



2.3 WRFD-010201 FDD Mode


Availability:

This feature is introduced in RAN2.0.

Description

3GPP specification comprises Frequency Division Duplex (FDD) mode and Time Division Duplex (TDD) mode. FDD mode uses individual frequency band for the uplink and downlink. TDD mode uses the same frequency band for the uplink and downlink. Huawei RAN only supports FDD mode.

Enhancement

None

Dependency

Need related node elements to be compliant to the 3GPP specifications in FDD mode.

Benefits

This feature defines the mode supported by Huawei RAN.



3 RABs and Services

3.1 WRFD-010510 3.4/13.6/27.2Kbps RRC Connection and Radio Access Bearer Establishment and Release


Availability:


Description

3.4/13.6/27.2Kbps RRC connection and Radio Access Bearer Establishment and Release are supported to provide the services available. And RNC will map these RRC connection request and RAB assigned by CN to the corresponding radio parameters according to their QoS requirements.

l Channel type mapping

For RRC connection, operator can configure which channel type (CCH/DCH) should be used according to the cause in RRC setup REQUEST message.

For RAB connection, operator can configure which RAB should be setup on DCH while others on CCH.

l RAB parameters mapping

As soon as the channel type is decided, the corresponding transport channel and physical channel parameters will be allocated. Huawei RAN has a set of such parameters for each typical services supported. If no matching service found, the nearest RAB parameters will be chosen to use. Moreover, operator can add new service with new set of parameters configured. These features can maximize the service support capability of the system.

PS streaming/interactive/background RAB can also be setup on HS-DSCH or E-DCH channels, such feature belongs to the optional feature WRFD-010610 HSDPA Introduction Package, WRFD-010612 HSUPA Introduction Package, WRFD-010630 Streaming Traffic Class on HSDPA and WRFD-010632 Streaming Traffic Class on HSUPA.

Enhancement

In RAN3.0, 13.6Kbps RRC connection is supported.

In RAN6.1, 27.2Kbps RRC connection is supported.

Dependency



It is an essential feature for UMTS RAN.

Benefits

This feature is the base of service supports.



3.2 WRFD-010501 Conversational QoS Class


Availability:


Description

QoS classes also refer to traffic classes. There are four different QoS classes defined in 3GPP:

l Conversational class;

l Streaming class;

l Interactive class;

l Background class.

The main difference between these QoS classes is how delay sensitive the traffic is. Conversational class is meant for traffic which is very delay sensitive and mainly used to carry real time traffic flows. Fundamental characteristics for Real time conversation QoS class include:

l Preserve time relation (variation) between information entities of the stream;

l Conversational pattern (stringent and low delay).

There are conversational class services in both CS and PS domain. The most well known conversational traffic is speech and video phone services in CS domain and VoIP in PS domain.

Huawei RAN supports the following conversational services as fundamental features:

1. CS AMR speech services of 8 rates, including 12.2 kbit/s, 10.2 kbit/s, 7.95 kbit/s, 7.4 kbit/s, 6.7 kbit/s, 5.9 kbit/s, 5.15 kbit/s, and 4.75 kbit/s. RNC will select SF256 for AMRS services whose maximum rate is not higher than 7.95 kbit/s.

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

3. PS Bidirectional symmetric speech services at the rates of 64 kbit/s, 42.8 kbit/s, 32 kbit/s, 16 kbit/s, and 8 kbit/s.

Enhancement

None

Dependency

CN Node and UE should support the services at the same time.

Benefits



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



3.3 WRFD-010502 Streaming QoS Class


Availability:


Description

QoS classes also refer to traffic classes. There are four different QoS classes:


l Streaming class;


l Background class.

The main difference between these QoS classes is how delay sensitive the traffic is. Streaming class is one of the newcomers in data communication, raising a number of new requirements in both telecommunication and data communication systems. It is characterized by that the time relations (variation) between information entities (i.e. samples, packets) within a flow shall be preserved, although it does not have any requirements on low transfer delay. Fundamental characteristics for streaming QoS class include:

Preserve time relation (variation) between information entities of the stream.

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

Huawei RAN supports the following streaming services as fundamental feature:

1. CS transparent data services (streaming class) of 64 kbit/s.

2. CS nontransparent data services of 57.6 kbit/s, 28.8 kbit/s, and 14.4 kbit/s.

3. PS bidirectional symmetric or asymmetric streaming services at the rates of 384 kbit/s, 256 kbit/s, 144 kbit/s, 128 kbit/s, 64 kbit/s, 32 kbit/s, and 8 kbit/s.

4. PS unidirectional asymmetric streaming services at the rates of 384 kbit/s, 256 kbit/s, 144 kbit/s, 128 kbit/s, 64 kbit/s, 32 kbit/s, 8 kbit/s, and 0 kbit/s.

PS streaming service can also bear on HSDPA/HSUPA which is the optional features and described in WRFD-010610 HSDPA Service and WRFD-010612 HSUPA Service.

Enhancement

In RAN6.0, PS 384 kbit/s bidirectional symmetric or asymmetric streaming service is supported.

Dependency




Benefits

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



3.4 WRFD-010503 Interactive QoS Class


Availability:


Description



l Streaming class;


l Background class.

The main difference between these QoS classes is how delay sensitive the traffic is. Interactive class is the other classical data communication scheme that on an overall level is characterized by the request response pattern of the end-user. At the message destination there is an entity expecting the message (response) within a certain time. Round trip delay time is therefore one of the key attributes. Another characteristic is that the content of the packets shall be transparently transferred (with low bit error rate). Fundamental characteristics for Interactive QoS class include:

l Request response pattern.

l Preserve payload content.

There are interactive class services in PS domain while no application service in CS domain is obviously needed. The most well known interactive traffic is web browsing.

Huawei RAN supports the following interactive services as fundamental feature:

1. PS bidirectional symmetric or asymmetric interactive services at the rates of 384 kbit/s, 256 kbit/s, 144 kbit/s, 128 kbit/s, 64 kbit/s, 32 kbit/s, 16 kbit/s, and 8 kbit/s.

The higher rates can only be supported on HSDPA/HSUPA which are optional features and described in WRFD-010610 HSDPA Service and WRFD-010612 HSUPA Service

Enhancement

In RAN3.0, PS UL 384K bit/s service is supported.

Dependency


Benefits

Interactive QoS class support capability can provides upper layer corresponding services with QoS guaranteed.



3.5 WRFD-010504 Background QoS Class


Availability:


Description



l Streaming class;


l Background class.

The main difference between these QoS classes is how delay sensitive the traffic is. Background class is one of the classical data communication schemes that on an overall level is characterized by that the destination is not expecting the data within a certain time. The scheme is thus more or less delivery time insensitive. Another characteristic is that the content of the packets shall be transparently transferred (with low bit error rate). Fundamental characteristics for background QoS class include:

l The destination is not expecting the data within a certain time;

l Preserve payload content;

There are background class services in PS domain while no application service in CS domain is obviously needed. The most well known background traffic is background download or E-mails.

Huawei RAN supports the following background services as fundamental feature:

PS bidirectional symmetric or asymmetric background services at the rates of 384 kbit/s, 256 kbit/s, 144 kbit/s, 128 kbit/s, 64 kbit/s, 32 kbit/s, 16 kbit/s, and 8 kbit/s.

The higher rates can only be supported on HSDPA/HSUPA which are optional features and described in WRFD-010610 HSDPA Service and WRFD-010612 HSUPA Service

Enhancement

In RAN3.0, PS UL 384K bit/s service is supported.

Dependency


Benefits

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



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


Availability:


Description

Multi-RAB support capability can provide more abundant services supported simultaneously to the upper layer. In the case of multi-RAB with the number of PS RAB less than two, Huawei supports the following specifications:

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

l One CS service + one PS service

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

In all the combination above, the bit rates of CS and PS services are not limited. That is, any bit rate 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 channels, such feature will be supported with the optional feature WRFD-010610 HSDPA Introduction Package and WRFD-010612 HSUPA Introduction Package.

Enhancement

None

Dependency

CN node and UE must have the corresponding multi-RAB support capability.

Benefits

Multi-RAB support capability provides operator more choices for the service solution.



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


Availability:


Description

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

Enhancement

None

Dependency


Benefits




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


Availability:


Description

Huawei supports one CS service + one PS service.

Enhancement

None

Dependency


Benefits




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


Availability:


Description

Huawei supports two CS services + one PS service (except for two AMR speech services).

Enhancement

None

Dependency


Benefits




3.7 WRFD-021104 Emergency Call


Availability:


Description

When Emergency Call is triggered, “Establishment Cause” in the RRC Connection Request message is set to “Emergency Call”.

Emergency call always has higher priority than the normal calls. When there is no enough resource in the cell, pre-emption action to ordinary calls with lowest priority will be triggered to guarantee that the emergency call access into the network and be served.

Enhancement

None

Dependency

None

Benefits




4 RAN Architecture & Functions

4.1 WRFD-010204 2-Antenna Receive Diversity


Availability:


Description

Receive diversity refers to a technique of monitoring multiple frequencies from the same signal source, or multiple radios and antennas monitoring the same frequency, in order to combat signal fade and interference.

Receive diversity is one way to enhance the reception performance of uplink channels. It does not involve RNC or UE.

Huawei NodeBs support both RX diversity and no RX diversity. In RX diversity mode, the NodeB can be configured with 2 antenna (2-way) through the Antenna Magnitude parameter.

In RX diversity mode, the NodeB does not require additional devices and works with the same algorithms. Compared with 1-way no RX diversity, 2-way RX diversity requires twice the number of RX channels. The number of RX channels depends on the settings of the antenna connectors on the cabinet top.

Enhancement

None

Dependency

RX diversity requires the NodeB to provide enough RF channels and demodulation resources that can match the number of diversity antennas. It has no special requirements for RNC or UE.

Benefits

It can improve receiver sensitivity and uplink coverage, so that the CAPEX is reduced.



4.2 WRFD-010205 Cell Digital Combination and Split


Availability:


Description

In the indoor coverage, different antenna in different area should transmit and receive one cell signal which is called cell split. DBS3800 and iDBS3800 support cell digital combination and split.

The following figure shows the logical structure for cell digital combination and split. The downlink digital signal can be driven two RRUs, one is for this level RRU Tx Path, and one is for down level RRU. For uplink, this level RRU digital signal can be combined with the down level RRU signal and send to the up level RRU or baseband unit.

Each RRU or Pico RRU has independent antenna and it can cover different area, but several RRU digital signal can be combined to one cell in uplink and one cell signal can replicated to several RRU in RHUB, Pico RRU or macro RRU . It has same scramble code.

Huawei will introduce this feature to the Pico RRU and RRU, which is proposed to indoor coverage.

Enhancement

None

Dependency

RRU

Combined

RF Tx Path

RF Rx Path

Du

ple

xer

CPRI

Interface

CPRI

Interface

Slave

Uplink

Split

Master

Up level RRU or BB

Down level RRU



None

Benefits

Cell digital combination and split will not bring the additional noise and signal loss compared with the analog combination and split. It is benefit to get large capacity and coverage.



4.3 WRFD-010208 Fast Power Congestion Control (FCC)


Availability


Description

Fast congestion control (FCC) is an NodeB function that complements RNC congestion control. The function supervises the output power that users (all users) demand at the same time per slot, using the same time scale as the fast power control function.

Huawei provides DL ALC (Auto Level Control) function as the method of fast power congestion control in NodeB, in order to limit the output power and avoid PA saturation. ALC supervisor the signal strength to PA, When it reach to threshold, ALC can increase the TX channel attenuation loss to keep the output power lower than threshold to avoid PA saturation. The NodeB use the FCC to fast control the output power, the control Reaction time is 1024chip, which is to say it is fast enough to fully prevent saturation of the TX chain or overdriving of the power amplifier without the need for power margins.

Therefore, cell behavior remains robust at maximum load without running the risk of dropped cells or modulation inaccuracy. Furthermore, the RNC congestion and admission thresholds can be set to higher levels, increasing cell capacity without compromising overall quality of service.

Enhancement

None

Dependency

None

Benefits

This feature provides operator a method to enable dynamic power sharing in one carrier between R99 and HSDPA.



4.4 WRFD-010211 Active TX Chain Gain Calibration


Availability

This feature is available from RAN5.0

Description

The Active TX chain gain calibration reduces the required margin between the DL max output power and the nominal output power used for network planning.

There is Down Link Automatic Gain Control (DLAGC) loop in NodeB. DLAGC mechanism includes input power detector, output power detector, variable gain amplifier (VGA) and the controller. The controller can calculate downlink gain between the downlink input power and output power. If the calculated gain is different from target gain, the VGA will tune to compensate this difference.

Due to adjust the digital chain TX gain according the analog chain detector power, this calibration loop compensates for temperature drift, subsystem gain spread and time to keep the TX chain gain invariable. The smaller margin will increase the nominal output power and results in a higher utilization of the available DL power.

Enhancement

None

Dependence

None

Benefits

This feature reduces the required margin between the DL max output power and the nominal output power used for network planning



4.5 WRFD-021301 Shared Network Support in Connected Mode


Availability:


Description

Based on R99 specifications, when the UE is in Idle Mode, the CN+UTRAN have mechanisms available to provide UE-specific access restrictions for LA’s of the current PLMN and other PLMNs by using roaming agreement. But there is no mechanism to limit UE behavior in connected mode since UTRAN have not enough information to handle UE as CN does to UE 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, RNC obtains the parameters of the shared network support in connected mode from the messages and information elements (IE) which defined in 3GPP TS 25.413 and 25.423 including:

l The information of the PLMN/SNA that allows the UE to connect to, it is acquired from CN through RELOCATION REQUEST or COMMON ID message.

l The information of the SNAs that the LAs belong to from CN through INFORMATION TRANSFER message or from DRNC through RADIO LINK SETUP RESPONSE and UPLINK SIGNALING TRANSFER messages.

Each LA belongs to one or several shared network area (SNA) while one UE can belong to one or several SNAs. Based on the information, 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:

l Cell Update

When the UE initiates cell update in the destination cell, the RNC decides whether or not the UE is allowed to access the destination cell.

If the UE is not allowed to access the destination cell, the cell update fails.

l URA Update

The URA update is the same to the cell update.

l 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.

l Relocation

When the Target RNC (TRNC) receives a RELOCATION REQUEST message, it decides whether or not the UE is allowed to access the destination cell.

If the UE is not allowed to access the destination cell, the relocation failure procedure is triggered.

l Handling Common ID Message

The RNC obtains the IMSI information of the UE in the common ID message and decides whether or not the UE is allowed to access the current cell.

If the UE is not allowed to access the current cell, the RRC connection is released.

Enhancement

None

Dependency

CN mode must support this feature at the same time and when it is related to Iur interface, the RNC connected to should also support the feature.

Benefits

With this feature, RNC can prevent UE in connected mode from moving to an un-subscribed area and it can also be used as a supplement feature for implementing shared networks solutions.



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


Availability:


Description

In 3GPP, there are four RRC connected states for UE including URA_PCH, CELL_PCH, CELL_FACH and CELL_DCH. Huawei RAN supports all these 4 states.

URA_PCH/CELL_PCH: In these states, UE has neither DCCH nor DTCH available. When UE originates a call or receives paging from CN, CELL_UPDATE procedure will be triggered. Periodically URA UPDATE or CELL_UPDATE procedure can also be used to keep the connection with the network. Since no DTCH and DCCH allocated, UE in these states has nearly no resource occupation of the radio resources, thus no service can be available as a result.

CELL_FACH: In this state, UE has DCCH and DTCH mapping to the common channels which are used to bear RRC signaling and traffic data. UE also performs cell reselection with Cell Update procedure to camp on a proper cell. Since the common resources can be shared among different UEs, the service QoS such as transfer delay, bandwidth etc. can not be guaranteed.

CELL_DCH: In this state, UE has DCCH and DTCH mapping to the dedicated channels which are used to bear RRC signaling and traffic data. Since the dedicated resources are allocated, the traffic QoS can be guaranteed while the cell load is increased accordingly. When UE is using HSDPA and/or HSUPA, it also belongs to CELL_DCH state.

These four states can be transited according to the UE service characteristics and behaviors, such procedures are Channel type transition, for the detail, please refer to the feature WRFD-021101 Dynamic channel configuration Function (DCCC).

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 HSDPA feature deployment, UE in CELL_DCH (HS-DSCH) state is also supported.

In RAN 6.0 with HSUPA feature deployment, UE in CELL_DCH (E-DCH) state is also supported.

Dependency



None

Benefits

This feature makes it possible to put UE in the proper state according to the QoS requirements which can improve resource usage efficiency greatly and therefore, increase system capacity while not affecting the user’s feeling obviously. It is an essential feature for UMTS RAN system.



4.7 WRFD-010401 System Information Broadcasting


Availability:


Description

System information broadcasting provides UE with the Access Stratum and Non Access Stratum information which are needed by the UE for its operation within the network.

The system information is organized as a tree. 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 calculate the repetition period and position of each SIB segment for every SIB automatically based on its importance.

The key information of each SIB Huawei supported is as the table below.

System Information

Block Area

Scope Content

Master information block Cell SIB scheduling information

Scheduling block 1 Cell SIB scheduling information

Scheduling block 2 Cell SIB scheduling information.

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 used for UE in idle mode.

SIB4 Cell

Parameters of cell selection and reselection in connected mode. Parameters of Hierarchical cell used for UE in connected mode (CCH state)

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



System Information

Block Area

Scope Content

SIB6 Cell Parameters of common physical channel for UE in connected mode.

SIB7 Cell UL interference, Dynamical persistence level

SIB11 Cell Measurement control information for UE in idle mode.

SIB11 bis Cell Measurement control system information extension in addition to SIB11.

SIB12 Cell Measurement control information for UE in connected mode.

SIB18 Cell PLMN ID of neighboring cells

Enhancement

In RAN5.0, SIB 4, 6, 12 is supported.

In RAN10.0, SIB 11bis is implemented. The system information block type 11bis contains measurement control information to be used in the cell in addition to SIB11, including new intra-frequency cells, new inter-frequency cells and new inter-RAT cells.

Dependency

None

Benefits

This feature provides UE Access layer and Non access layer information which UE needs and controls UE behavior in the network.



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


Availability:


Description

Paging type 1 procedure is used to transmit paging information to the selected UEs in idle mode, CELL_PCH or URA_PCH state using the paging control channel (PCCH). With this feature, upper layers in the network can:

l Trigger UE establishing a RRC signaling connection.

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

l Trigger reading of updated system broadcast of UE in idle mode, CELL_PCH or URA_PCH state.

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

Enhancement

None

Dependency


Benefits

The network can control the UE in idle state, CELL_PCH or URA_PCH state which has no Dedicated Control Channel (DCCH) with paging type 1 procedure.



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


Availability:


Description

Paging type 2 procedure is used to transmit paging information to selected UE in CELL_DCH state or CELL_FACH state, and the PAGING TYPE 2 will be transferred on DCCH.

Enhancement

None

Dependency


Benefits

The network can control the UE in CELL_FACH or CELL_DCH state which has Dedicated Control Channel (DCCH) with paging type 2.



4.10 WRFD-020900 Logical Channel Management


Availability:


Description

A set of logical channel types is defined for different kinds of data transfer services as offered by MAC. Each logical channel type is defined by what type of information is transferred. A general classification of logical channels is into two groups:

l Control Channels (for the transfer of control plane information).

l Traffic Channels (for the transfer of user plane information).

Control channels are used for transfer of control plane information only including:

l Broadcast Control Channel (BCCH)

l Paging Control Channel (PCCH)

l Common Control Channel (CCCH)

l Dedicated Control Channel (DCCH)

Traffic channels are used for the transfer of user plane information only including:

l Dedicated Traffic Channel (DTCH)

l Common Traffic Channel (CTCH)

Mapping between logical channels and transport channels is as below

I. In Uplink,

l CCCH can be mapped to RACH;

l DCCH can be mapped to RACH;

l DCCH can be mapped to DCH;

l DTCH can be mapped to RACH;

l DTCH can be mapped to DCH;

l DTCH can be mapped to E-DCH;

II. Downlink,

l BCCH can be mapped to BCH;

l BCCH can be mapped to FACH;

l PCCH can be mapped to PCH;

l CCCH can be mapped to FACH;

l DCCH can be mapped to FACH;



l DCCH can be mapped to HS-DSCH;

l DCCH can be mapped to DCH;

l DTCH can be mapped to FACH;

l DTCH can be mapped to HS-DSCH;

l DTCH can be mapped to DCH;

l CTCH can be mapped to FACH;

The mapping between DTCH and HS-DSCH/E-DCH belong the optional feature WRFD-010610 HSDPA Introduction Package and WRFD-010612 HSUPA Introduction Package.

Enhancement

In RAN3.0, CTCH channel is supported with Cell Broad Service (CBS) feature Introduced.

Dependency


Benefits

This feature provides the base of data transfer and resource management algorithm.



4.11 WRFD-021000 Transport Channel Management


Availability:


Description

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

A general classification of transport channels is into two groups:

l Common transport channels

l Dedicated transport channels

Common transport channel types are:

l Random Access Channel (RACH)

l Forward Access Channel (FACH)

l Broadcast Channel (BCH)

l Paging Channel (PCH)

l High Speed Downlink Shared Channel (HS-DSCH)

Dedicated transport channel types are:

l Dedicated Channel (DCH)

l Enhanced Dedicated Channel (E-DCH)

Enhancement

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

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

Dependency


To support HSDPA transport channels, the HSDPA support downlink process board (HBBI or HDLP) should be added in NodeB and the optional feature WRFD-010610 HSDPA Service must be selected.

To support HSUPA transport channels, the optional feature WRFD-010612 HSUPA Service must be selected.

Benefits

This feature provides the base of data transfer and resource management algorithm.



4.12 WRFD-022000 Physical Channel Management


Availability


Description

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

The Coded Composite Transport Channel (CCTrCH) is defined as the multiplexing of several transport channels that can be supported by one or several physical channels on the radio interface. Some physical channels are used only by the physical layer of the radio interface, only the following physical channels may bear transport channels:

l P-CCPCH: Primary Common Control Physical Channel

l S-CCPCH: Secondary Common Control Physical Channel

l PRACH: Physical Random Access Channel

l DPDCH: Dedicated Physical Data Channel

l HS-PDSCH: High Speed Physical Downlink Shared Channel

l E-DPDCH: E-DCH Dedicated Physical Data Channel

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

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

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

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

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

The set of physical channels types supported by the Huawei NodeB is given in the tables below. The characteristics of these supported physical channels are compliant with 3GPP TS25.211. Physical channels are conveyed on the radio interface only until NodeB, but are managed by the RNC.

Channel Availability

Direction Characteristics

PRACH Physical Random Access Channel

RAN2.0 UL Common

PRACH is used to carry the RACH which carries random access info of the UE accessing the network. It consists of one or several preambles of length 4096 chips and a message of length 10 ms or 20 ms. The spreading factor may



range from 256 down to 32.

Uplink DPDCH Uplink Dedicated Physical Data Channel

RAN2.0 UL Dedicated

The uplink DPDCH is used to carry the DCH transport channel. There may be zero, one, or several uplink DPDCHs on each radio link. The spreading factor may range from 256 down to 4.

Uplink DPCCH Uplink Dedicated Physical control Channel

RAN2.0

UL Dedicated

The uplink DPCCH is used to carry control information generated at Layer 1. The Layer 1 control information consists of TFCI, TPC, Pilot bits, FBI, which is required to convey DPDCH. There is one and only one uplink DPCCH on each radio link. The spreading factor is always equal to 256.

P-CCPCH Primary Common Control Physical Channel

RAN2.0 DL Common

The Primary CCPCH is a fixed rate (30 kbps, SF=256) downlink physical channels used to carry the BCH transport channel which provides system and cell specific information. It is not transmitted during first 256 chips of each slot since time multiplexed with SCH.

S-CCPCH Secondary Common Control Physical Channel

RAN2.0 DL Common

The Secondary CCPCH is used to carry the FACH and PCH. The FACH and PCH can be mapped to the same or to separate Secondary CCPCHs. The spreading factor range is from 256 down to 4. No inner-loop power control. Not always transmitted.

P-SCH Primary Synchronization Channel

RAN2.0 DL Common

The P-SCH is used for cell search procedure (Slot synchronization). Not scrambled nor OVSF coded. Time multiplexed with P-CCPCH.

S-SCH Secondary Synchronization Channel

RAN2.0 DL Common

The S-SCH is used for cell search procedure (SC group identification). Not scrambled nor OVSF coded. Time multiplexed with P-CCPCH.

P-CPICH Primary Common Pilot Channel

RAN2.0 DL Common

The CPICH is a fixed rate (30 kbps, SF=256) downlink physical channel that carries a pre-defined bit sequence. The Primary CPICH is the phase reference for the following downlink channels: SCH, Primary CCPCH, Second CCPCH, AICH, PICH and DPCH. There is one and 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 Indication Channel

Common channel used to carry the paging indicators. The PICH is always associated with an S-CCPCH (mapped with PCH) to carry the Paging Indicators (PI) informing the UE that paging info is available on the SCCPCH.

AICH Acquisition Indicator Channel

RAN2.0 DL Common

The AICH is a fixed rate (SF=256) physical channel used to carry Acquisition Indicators (AI). Acquisition Indicator AIs corresponds to signature s on the PRACH, used by the network to confirm to the UE the reception of its access (PRACH).

Downlink DPCH Downlink Dedicated Physical Channel

RAN2.0 DL Dedicated

The downlink DPCH can be seen as a time multiplex of a downlink DPDCH and a downlink DPCCH. It carries dedicated data generated at Layer 2 and above (i.e. the dedicated transport channel DCH), with control information generated at Layer 1 (pilot bits, TPC commands, and TFCI). The spreading factor may range from 512 down to 4.

HS-DPCCH Dedicated Physical Control Channel for HS-DSCH

RAN5.0 UL Dedicated

The HS-DPCCH carries uplink feedback signaling related to downlink HS-DSCH transmission. It consists of HARQ-ACK, CQI. The spreading factor of the HS-DPCCH is 256

HS-SCCH Shared Control Channel for HS-DSCH

RAN5.0 DL Common

The HS-SCCH is a fixed rate (60 kbps, SF=128) downlink physical channel used to carry downlink signaling related to HS-DSCH transmission, including modulation mode, size of a transmission block, redundant version information, UE ID and HS-PDSCH channel code. HS-SCCH is aligned with the PCCPCH in timing and keeps fixed time offset with the HS-PDSCH. Its spreading factor is fixed as 128 and QPSK is the only modulation mode. The number of HS-SCCHs and the channel codes in the cell are decided by RNC, and are notified to the NodeB through the NBAP signaling message. When the NodeB sends the data to the UE through the HS-PDSCH, the UE can detect one to four HS-SCCHs that are specified by the NodeB at one time.

HS-PDSCH High Speed Physical Downlink Shared Channel

RAN5.0 DL Common

The HS- PDSCH is used to carry HS-DSCH. A HS-PDSCH corresponds to one channelization code of fixed spreading factor SF=16 from the set of channelization codes reserved for HS-DSCH transmission. Multi-code transmission is allowed, which translates to UE being assigned multiple



channelization codes in the same HS-PDSCH sub-frame, depending on its UE capability. The HS-PDSCH adopts the QPSK or 16QAM modulation mode.

E-DPDCH E-DCH Dedicated Physical Data Channel

RAN6.0 UL Dedicated

The E-DPDCH is used to carry the E-DCH transport channel. There may be zero, one, or several E-DPDCH on each radio link. Its spreading factor set is {SF256, SF128, SF64, SF32, SF16, SF8, SF4, 2×SF4, 2×SF2 and 2×SF2+2×SF4}. In RAN 6.0, spreading factor set {SF256, SF128, SF64, SF32, SF16, SF8, SF4, 2×SF4,} can be supported.

E-DPCCH E-DCH Dedicated Physical Control Channel

RAN6.0 UL Dedicated

The E-DPCCH is a physical channel used to transmit control information associated with the E-DCH. There is at most one E-DPCCH on each radio link. The spreading factor is always equal to 256.

E-AGCH E–DCH Absolute Grant Channel

RAN6.0 DL Common

E-AGCH is a common downlink physical channel, which carries the maximum power ratio of E-DPDCH/DPCCH that can be allowed to use by the UE, it is only sent from the serving cell that the serving radio link of the UE belongs to, an E-AGCH channel 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, fixed rate 30 kbps.

E-RGCH E-DCH Relative Grant Channel

RAN6.0 DL Dedicated

E-RGCH is a dedicated downlink physical channel, which carries the relative grant value for modifying power ratio of E-DPDCH/DPCCH, it is used to frequently adjust the UE uplink transmit power, which could happen per 2ms TTI. E-RGCH and E-HICH of a user shares the same channel code with spreading factor 128, and one channel code for E-RGCH and E-HICH can be spread again with 40 orthogonal signature sequences, which extends the usage of the downlink channel code.

E-HICH E-DCH Hybrid ARQ Indicator Channel

RAN6.0 DL Dedicated

E-HICH is a dedicated downlink physical channel, which carries the E-DCH hybrid ARQ acknowledgement indicator such as ACK/NACK, the acknowledgement indicator informs UE whether the data for a user process is received correctly or not in NodeB.



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

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

Dedicated Physical Data Channel (DPDCH) Dedicated Physical Control Channel (DPCCH) Fractional Dedicated Physical Channel (F-DPCH) E-DCH Dedicated Physical Data Channel (E-DPDCH) E-DCH Dedicated Physical Control Channel (E-DPCCH) E-DCH Absolute Grant Channel (E-AGCH) E-DCH Relative Grant Channel (E-RGCH) E-DCH Hybrid ARQ Indicator Channel (E-HICH) Physical Random Access Channel (PRACH) Common Pilot Channel (CPICH) Primary Common Control Physical Channel (P-CCPCH) Secondary Common Control Physical Channel (S-CCPCH) Synchronisation Channel (SCH) Acquisition Indicator Channel (AICH) Paging Indicator Channel (PICH) MBMS Notification Indicator Channel (MICH) High Speed Physical Downlink Shared Channel (HS-PDSCH) HS-DSCH-related Shared Control Channel (HS-SCCH) Dedicated Physical Control Channel (uplink) for HS-DSCH (HS-DPCCH)

Transport Channels

DCH

RACH

BCH

FACH

PCH

Physical Channels

HS-DSCH

E-DCH

Enhancement

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



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

l HS-SCCH, Shared Control Channel for HS-DSCH

l HS-PDSCH, High Speed Physical Downlink Shared Channel

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

l E-DPDCH, E-DCH Dedicated Physical Data Channel

l E-DPCCH, E-DCH Dedicated Physical Control Channel

l E-AGCH, E–DCH Absolute Grant Channel

l E-RGCH, E-DCH Relative Grant Channel

l E-HICH, E-DCH Hybrid ARQ Indicator Channel

l MICH, MBMS Indicator Channel

In RAN10.0, the F-DPCH is added

Dependency


To support HSDPA physical channels, the HSDPA support downlink process board (HBBI or HDLP) should be added in NodeB and the optional feature WRFD-010610 HSDPA Service must be selected.

To support HSUPA physical channels, the optional feature WRFD-010612 HSUPA Service must be selected.

To support F-DPCH, the macro NodeB BTS3812E/ BTS3812AE needs adding EBBI. or EBOI.BBU3806 needs adding the EBBC.

Benefits

With F-DPCH, more VoIP users can be supported.



4.13 WRFD-011401 Integrity Protection


Availability:


Description

The Integrity protection handles the control of integrity protection of signaling data and the co-ordination of integrity keys between different core networks (PS and CS). It enables receiving entity (UE or RNC) to verify if the signaling data is illegally changed. It encrypts and decrypts the signaling data using a certain integrity algorithm with an integrity key (IK).

Huawei RAN supports integrity algorithm UIA1.

Enhancement

None

Dependency


Benefits

The procedure enhances network and user data security, and protects the data and networks from illegal interception and changing.



4.14 WRFD-011402 Encryption


Availability:


Description

The Encryption Function handles the control of ciphering of data and signaling data and the co-ordination 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


Benefits

The procedure enhances network and user data security and protects the data and networks from illegal interception and changing.



4.15 WRFD-020501 Open Loop Power Control


Availability:


Description

Open-loop power control attempts to make a rough estimation of path loss by means of power measurements, network parameter setting and QoS requirement, then to provide a proper initial power used by the UE and the NodeB.

Open-loop power control is applied on the uplink PRACH and DPCH as well as the downlink DPCH. The other downlink common channel’s initial power is set fixed by the network.

For the PRACH, firstly, UE will calculate the initial PRACH preambles transmit power by estimation of downlink path loss, and other necessary information like UL inferences by the cell system broadcasting. The following ramping rule is also controlled by the network through parameters setting in broadcasting information. As soon as the positive acquisition indicator is received on AICH, the transmit power of PRACH message control part can be certain with the power offset to the last transmitted preamble. Meanwhile, the transmit power of data part can be calculated by gain factors for control & data part.

For the uplink DPCCH transmission, initial power is calculated the same way as PRACH, except the power offset is different which provided by RRC messages, moreover, uplink DPDCH transmit power can be calculated with the gain factors signaled by the network.

For the downlink DPCH, the DPDCH transmit power is firstly estimated by according to the RAB QoS assigned and the network configured parameters, the transmit power of each DPCCH part TFCI, TPC and Pilot can be calculated by the network controlled power offset (PO1/PO2/PO3) setting.

Open power control is used in the following scenarios which need an initial power on the new added radio link.

- RRC connection setup

- Radio link addition in soft handover

- Hard handover

- Relocation

- Channel type switching

Enhancement



None

Dependency

None

Benefits

The proper initial power setting can decrease the possibility of burst interference to the network and improve the performance of the inner power control.



4.16 WRFD-020502 Downlink Power Balance


Availability:


Description

During soft handover, the UL TPC command is demodulated in each RLS and due to demodulation errors, the difference between the initial transmit power of new added RL and existing one may lead to the drifting of transmit power. The more DL transmit power drifting is, the more loss to the macro-diversity gain is.

Downlink Power Balance is used to correct the transmit power drifting in such scenarios and improve soft handover performance accordingly.

In the downlink, NodeB will calculate the transmit power with considering TPC commands sent by UE as well as the reference power set by the network. When the drifting of transmit power is too much, the network will update the reference power to decrease the power difference of different RL.

Enhancement

None

Dependency

None

Benefits

Downlink Power Balance can decrease the transmit power drifting of different RL and improve soft handover performance accordingly.



4.17 WRFD-020503 Outer loop Power Control


Availability:


Description

Outer loop power control is to maintain the communication quality at the level required by the service bearer through adjustment of the SIR target. This control acts on each DCH belonging to the same RRC connection.

Outer loop power control comprises downlink & uplink part. For the downlink, it is to maintain the proper SIR target used in downlink inner loop power control and the algorithm depends on UE implementation, the downlink BLER requirements of each RB was signaled by the network for UE to consider. For the uplink, it is to maintain the proper SIR target used in uplink inner power control and set by the network.

For the uplink outer loop power control, SRNC gets the uplink quality after macro diversity selection combining firstly, and then 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, decreases. When BLER is not available, BER will be used instead. After adjusting the SIR target, the SRNC sends the new SIR target through FP frames to all NodeBs for uplink inner loop power control.

The initial SIR target provided by the RNC to the NodeB is service-dependent and it will be updated by the uplink quality measurement of each DCH in the following phases.

Enhancement

None

Dependency

None

Benefits

Outer loop power control is used to set the proper SIR target used for uplink inner loop power control and improve the uplink performance.



4.18 WRFD-020504 Inner Loop Power Control


Availability:


Description

Inner-loop power control is also called fast closed-loop power control and only applied to the dedicate channel. It controls the transmit power according to the information returned from the peer physical layer. The UE and the NodeB can adjust the transmit power according to the RX SIR of the peer end, to compensate 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 individually.

The uplink inner-loop power control is used to adjust the UE transmit power by receiving TPC commands from NodeB. There are fast and slow power control algorithm (PCA) defined by 3GPP protocol. PCA1 is the fast power control which UE adjust the power in one slot and PCA2 is slow power control which UE will adjust every 5 slots, which lower the power control frequency from 1500times/s to 300times/s maximally. Operator can control which PCA will be chosen in RRC messages.

The downlink inner-loop power control is used to adjust NodeB transmit power by receiving TPC commands from UE. There are 2 Downlink Power Control (DPC) modes which also controls the downlink power adjust frequency. That is, UE send TPC command every slot in DPC mode 0 while sending the same TPC command in 3 slots in DPC mode 1. Operator can control which DPC mode will be used by RRC signaling.

Enhancement

None

Dependency

None

Benefits

Inner Loop Power Control adjusts the uplink and downlink power to the minimum while ensuring the QoS, thus increases system capacity. It can also be used against shadow fading and fast fading.



4.19 WRFD-020101 Admission Control


Availability:


Description

Admission control is used to improve the resource usage efficiency and RRC/RAB setup successful rate. The following 4 type resource will be admitted:

l Cell available code resource

l Cell available power resource

l NodeB resource state, that is, NodeB credits

l 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 independently.

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

I. Code Resource

When a new service accesses the network, the code resource admission is successful if the code resources can be allocated to the service.

II. Power Resource

The following three algorithms are available for power resource:

l Algorithm 1

Power resource admission decision based on power or interference

Based on the current cell load (uplink load factor and downlink TCP) and the access request, the RNC decides whether the cell load will exceed the threshold or not if admitting a new call. If yes, the RNC rejects the request. If no, the RNC accepts the request.

l Algorithm 2

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

Based on the current equivalent number of users and the access request, the RNC decides whether the equivalent number of users will exceed the threshold or not if admitting a new call. If yes, the RNC rejects the request. If no, the RNC accepts the request.

l Algorithm 3

It is similar to algorithm 1, but the prediction of needed power of a new call will be set to zero.



Four basic load thresholds are used for admission decision. They are:

l Handover admission threshold

l AMR conversational service admission threshold

l Non AMR conversational service admission threshold

l Other service admission threshold

With these thresholds, the RNC can define the proportion between speech service and other services while ensuring handover preference.

III. NodeB Credit

NodeB credit admission includes the following:

l Local cell level admission decision

l local cell group level admission decision (if any)

l NodeB level admission decision

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

For details about local cell, local cell group, and capacity consumption law. Please refer to the 3GPP TS 25.433.

According to the common and dedicated channels capacity consumption laws, and the addition, removal, and reconfiguration of the common and dedicated channels, the Controlling RNC (CRNC) debits the amount of the credit resource consumed from or credits the amount to the Capacity credit of the local cell (and local cell group, if any) based on the spreading factor.

If the UL Capacity Credit and DL Capacity Credit are separate, the maintenance on the local cell (and local cell group, if any) is performed in UL and DL respectively.

If the UL Capacity Credit and DL Capacity Credit are not separate, the maintenance only 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 configurable and the detailed information please refers to the feature WRFD-021401 Transport Resource Management.

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

I. Each type of path can be configured with the total bandwidth of the physical port to which the path is connected. Thus, the total bandwidth of all paths that connect to the port may exceed the physical bandwidth of the port. Therefore, the following two levels of admission are necessary:

l Admission control on the path level



l 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 precedence over the secondary path during admission. The secondary path is tried after the admission attempt for the primary path fails.

For HSDPA/HSUPA, admission control also applies. Please refer to optional features WRFD-01061003 HSDPA Admission Control and WRFD-01061202 HSUPA Admission Control.

In the Admission Control procedure, some other features can be used to improve the access successful 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 admission failed, Queuing and Pre-Emption (WRFD-010505), DRD Introduction Package (WRFD-020400) can be used to maximum the possibility to access in the system.

Enhancement

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

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

In RAN6.0, resource reserved for handover is supported to decrease call drop due to admission fail during handover.

Dependency

None

Benefits

This feature maximizes system capacity while ensuring QoS requirements, and keeps the stability of the network.



4.20 WRFD-020102 Load Measurement


Availability:


Description

Algorithms such as OLC and CAC use load measurement values in the uplink and the downlink. A common Load Measurement (LDM) algorithm is required to control load measurement in the uplink and the downlink, which makes the algorithm relatively independent.

The LDM algorithm has the following functions:

- Triggering LDR and OLC algorithms

The LDM algorithm needs to decide whether the system works in basic congestion or overload congestion mode and to notify related algorithms for handling.

- Delay susceptibilities of PUC, CAC, LDR, and OLC to common measurement are different. When some or all the algorithms use the same common measurement, the LDM must apply different smoothed filter coefficients in order to get rippling and timely common measurement as required.

The major measurement quantities related are defined in 3GPP TS25.433 as below:

l Uplink RTWP (Received Total Wideband Power)

l Downlink TCP (Transmit Carrier Power)

l Transmitted carrier power of all codes not used for HS-PDSCH or HS-SCCH transmission

l Provided Bit Rate (PBR) on HS-DSCH

l Power Requirement for GBR (Guaranteed Bit Rate) on HS-DSCH.

The measurements above focus on radio power load, and for other resource load, the related measurements include:

l For Iub load: Iub used bandwidth rate on PVC level.

l For code resource: The maximum rate can be supported with the minimum available SF.

Enhancement

In RAN6.0, the load measurement of code resource is introduced, and therefore load reshuffling can also be triggered by code congestion.

Dependency

None



Benefits

Load measurements 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, operator can also control these strategies by configure load measurement parameters like measurement period, hysteresis, etc.



4.21 WRFD-020106 Load Reshuffling


Availability:


Description

When the usage of cell resource exceeds the congestion trigger threshold, the cell enters the basic congestion state. In this case, LDR is needed to reduce the cell load and increase the access success rate. When the load is lower than the congestion release trigger threshold, the system comes back to normal.

The resources that can trigger basic congestion of the cell include:

l Power resources

l Iub resources or Iub bandwidth

l Code resources

l NodeB credit resources

l Equivalent user number

Iub resources and credit resources congestion control in both uplink and downlink is NodeB oriented. Load trigger threshold and load release threshold are set for the uplink and the downlink, separately.

The function of LDR is to reduce the load of a cell when the available resource of the cell reaches the threshold. The purpose of LDR is to increase the access rate in the following ways:

l Inter-frequency load handover

l Code reshuffling

l BE service rate reduction

l Uncontrolled real-time traffic QoS renegotiation

l CS domain inter-RAT load handover

l PS domain inter-RAT load handover

l Downsizing the bit rate of AMR voice

l MBMS power downgrading

Among them, Best Effect service rate reduction and code reshuffling is the basic feature and the other actions belong to the optional features.

Enhancement



In RAN5.0, optional feature Iu re-negotiation is introduced as one of the load reshuffling strategies.

In RAN5.0, priority based load reshuffling is supported.

In RAN5.1, optional feature AMRC is introduced as one of the load reshuffling strategies.

In RAN6.0, Load Reshuffling is extended to other resource congestion besides radio power resources and Iub resources, that is, code resources, credit resources and equivalent user number.

In RAN6.0, Load Reshuffling can also be applied for HSDPA, HSUPA and MBMS services. In addition, gold user shall not be impacted during the actions of Load Reshuffling.

In RAN6.0, code reshuffling and MBMS power downgrading are added as new strategies of Load Reshuffling.

In RAN10.0, uplink load reshuffling triggered by power resources can be applied in a HSUPA cell. In addition, a switch is provided to control whether gold user could be selected during the actions of Load Reshuffling.

Dependency

None

Benefits

This feature decreases the cell load when resource load enters basic congestion state, and therefore, improves the stability and capability of the network.



4.22 WRFD-020107 Overload Control


Availability:


Description

The function of OLC is to reduce the cell load rapidly by restricting the transport format (TF) of the BE service or releasing UEs when the cell is overloaded. The purpose of OLC is to ensure the stability of the system and the QoS of most UEs.

Overload control are only aimed to radio power load overload scenario.

Enhancement

In RAN5.0, priority based overload control is supported.

Dependency

None

Benefits

Decreases cell load when entering overload state rapidly and ensures the system stable.



4.23 WRFD-020108 Code Resource Management


Availability:


Description

Code resource management comprises code allocation and code re-allocation features and it only applied to the downlink code tree resource.

To optimize the code usage efficiency, “left most” algorithm is adopted in code allocation procedure, that is, the code with minimum SF will be reserved to keep the continuously codes left.

When the assigned AMR speech bit rate less than 7.95Kbps, the allocated SF will be 256 instead of 128 so as to save the code resource, and therefore, increase the capacity.

Code reshuffling algorithm is also applied to be one of the load reshuffling strategies and be used to decrease the code fragments. That is, when RNC found the maximum supported bit rate is less than the threshold configured from the view of code, the code re-allocation action will be implemented to adjust the code use in the code tree and reduce the code fragment as much as possible.

Enhancement

In RAN6.0, allocation of code with SF 256 when the assigned AMR speech bit rate is less than 7.95Kbps is supported.

In RAN6.0, code re-allocation algorithm is introduced and as one of the load reshuffling strategies triggered by code congestion.

Dependency

None

Benefits

The code management algorithm can improve code usage efficiency, and optimize the code distributes when too much code fragments founded.



4.24 WRFD-021101 Dynamic Channel Configuration Control (DCCC)


Availability:


Description

Dynamic Channel Configuration Control (DCCC) is comprised of Rate Re-allocation and UE State Transition function:

l Rate Re-allocation

In the CELL_DCH RRC state, Rate Re-allocation can adjust bandwidth allocated for the best effort (BE) services (i.e. interactive and background services), in both uplink and downlink independent of each other.

I. Traffic volume based:

According to traffic volume measurement report receipt from UE, Rate Re-allocation can increase or decrease the uplink data rate to a proper value, to match the allocated resource to uplink throughout requirement.

According to traffic volume measurement report receipt from RNC itself, Rate Re-allocation can increase or decrease the downlink data rate to a proper value, to match the allocated resource to downlink throughout requirement.

II. Coverage based:

According to the downlink quality, including downlink transmit power and RLC status, Rate Re-allocation can decrease the downlink data rate, to reduce the negative impact by coverage.

According to the uplink quality, including UE Tx power, the RNC can have the ability to adapt the UL rate during the call by means of UL bit rate switching to adapt to UE power limitations,

III. Load based:

Rate Re-allocation can be triggered by load control. The load can be power load, code resource and Iub transmission load and the congestion thresholds are independent and configurable. Such feature is one strategy of WRFD-020106 Load Reshuffling.

l 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 also can be used to improve the efficiency of resource allocation between dedicated and common channel.



DCCC is also applied to HSDPA/HSUPA (rate re-allocation is not applied to HSDPA because the data scheduler located in NodeB). For detail, please refer to optional feature WRFD-01061111 HSDPA State Transition and WRFD-01061208 HSUPA DCCC.

Enhancement

In RAN3.0, Iub transmission load based DCCC is supported.

In RAN6.0, Code resource based DCCC is supported.

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

Dependency

None

Benefits

This feature can improve the efficiency of radio resource allocation and keep the stability of radio link.



4.25 WRFD-021201 RNC Resource Sharing


Availability:


Description

RNC resource sharing of BSC6810 includes user plane resource sharing and control plane resource sharing.

Control plane resources sharing consider CPU load and memory, etc. When the CPU load or memory of certain signaling process unit is overload, the new call can be shared by other signaling process unit with lower load.

User plane resources are shared dynamically within the RNC system based on resource pool and load sharing. If certain user plane process unit is overload, the new traffic can be allocated to other user plane process unit with lower load.

Control plane capacity and user plane capacity can be configured independently.

Enhancement

None

Dependency

None

Benefits

l Improve the resource usage efficiency and increase call success rate.

l Make it possible to use the installed SW/HW capacity up to the maximum contracted limit with the minimum service outage under variable traffic modes.



4.26 WRFD-020201 Intra NodeB Softer Handover


Availability:


Description

Soft handover is a category of handover procedures where the radio links are added and abandoned in such manner that the UE always keeps at least one radio link to the UTRAN. Soft handover only occurs within the intra-frequency cells. Since adjacent cells have the same frequency, UE can connect to the network through multiple radio links to improve the communication quality. UE can perform smooth handover from one cell to another without interrupting the communication with the original cell.

On the other side, soft handover may lead to the occupancy of Iub resource since multi radio link exist.

The size of active set can be up to six and can be configured. RNC can make decision about SHO according to either Ec/N0 or RSCP. The parameters set for SHO can be independent on CS and PS service. The parameter CIO can also be configured for different cells for event evaluation.

Intra NodeB softer handover is one kind of soft handover. It sets up RLs in the sectors within a NodeB and the data receipt on these RLs is combined in the NodeB using maximum-ratio combination before forwarded to RNC. Therefore, it will occupy no more Iub transmission resource compared to the one before handover.

RNC can control whether intra NodeB softer handover should be implemented by setting the IE in NBAP message RL ADDITION REQUEST.

Neighboring cell combination is supported, which means the neighboring cells to be measured are selected from all the neighboring cells of active set and the priority of the neighboring cell is configurable. Neighboring cell combination is applied in soft/softer handover, hard handover and inter-RAT handover.

Enhancement

In RAN5.1, neighboring cell combination is supported.

Dependency


Benefits

Soft handover provides seamless connection services for mobile users. Besides these, Intra NodeB softer handover uses maximum-ratio combination on the uplink in



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



4.27 WRFD-020202 Intra RNC Soft Handover


Availability:


Description

Intra RNC soft handover is one kind of soft handover. It sets up RLs in different NodeBs or in same NodeB within RNC. The difference between Intra NodeB softer handover and Intra RNC soft handover lies on where the combination is performed. Intra RNC soft handover performs macro diversity combination in RNC, which also means each RL will have its own transport bearer on Iub interface.

Enhancement


Dependency


Benefits

Intra RNC soft handover provides seamless connection services for mobile users within RNC.



4.28 WRFD-020203 Inter RNC Soft Handover


Availability:


Description

Inter RNC soft handover is one kind of soft handover. It setups RLs in different RNCs and the Macro diversity combination is completed through Iur interface by SRNC. The uplink data is transmitted from DRNC to SRNC. SRNC combines data from its own cells and cells of DRNC. This is the key difference to other soft handovers.

Enhancement


Dependency

None

Benefits

Inter RNC soft handover provides seamless connection services for mobile users, compared to other kind of soft handovers, it enlarges the range of soft handover to the RNCs which have Iur connections with a certain RNC.



4.29 WRFD-020301 Intra Frequency Hard Handover


Availability:


Description

Hard handover is characterized by the handover course in which the old connection is released before a new connection is set up. Intra frequency hard handover means hard handover between cells of same frequency. It is used in either of the following scenarios:

l No Iur interface between RNCs

In this case, soft handover between RNCs is unavailable, and hard handover with CN switching between the two RNCs occurs.

l No enough Iur interface transmission resource available

In this case, soft handover between RNCs is also unavailable, and hard handover with CN switching between the two RNCs occurs.

l High-speed BE service

For the high-speed BE service, intra-frequency hard handover could be used to save downlink capacity, compared with soft handover.

l Failure in intra-frequency soft handover while intra-frequency hard handover allowed

When intra-frequency soft handover is failed due to the target cell congestion, intra-frequency hard handover could be tried with lower service bits rate.

Enhancement


Dependency

None

Benefits

Intra frequency hard handover acts in the scenarios when Intra frequency soft handover can not be used.



4.30 WRFD-010801 Intra RNC Cell Update


Availability:


Description

Cell update is mainly used to update the UE information on the network side when the UE’s location or behavior is changed. Intra RNC cell update means cell update within RNC.

Cell update may be triggered by the following causes:

l Periodical Cell Update

UE will send Cell Update message to RNC periodically when it is in CELL_FACH or CELL_PCH state. This can be used by RNC to monitor the RRC connection.

l Cell Reselection

If a UE in CELL_FACH or CELL_PCH state reselects a new cell, it will initial the procedure, when receive the message CELL_UPDATE, RNC updates the UE camping cell information.

l Paging Response

If a UE in URA_PCH or CELL_PCH state receives a PAGING TYPE 1 message, it will initial the procedure. RNC then transits the UE’s state to CELL_FACH or CELL_DCH.

l Uplink Data Transmission.

If a UE is in URA_PCH or CELL_PCH state and has data to transmit, it will initial CELL UPDATE procedure to request for uplink data transmission. RNC will transit its state to CELL_FACH subsequently.

l Radio Link Failure

If a UE in CELL_DCH state detects that the criteria for radio link failure are met, it will initial the procedure. RNC will delete the current radio link and re-establish a new one.

l Re-entering Service Area

If a UE moves out of the service area, and then re-enters the service area, it will initial the procedure. Then RNC will update the camping cell of the UE.

l RLC Unrecoverable Error

If a UE detects an RLC unrecoverable error in an AM RLC entity, it will initial the procedure, RNC will release the RRC connection of the UE or re-establish the RB



according to attribute of the RB. If it belongs to signal RB, the RRC connection will be released.

Enhancement

None

Dependency


Benefits

Cell update enables UTRAN to manage a UE’s behavior and enables UE to update its state when its service or location changes.



4.31 WRFD-010802 Inter RNC Cell Update


Availability:


Description

Cell update is mainly used to update the UE information on the network side when the UE’s location or behavior is changed. Inter RNC cell update means Cell update between RNCs.

The cause of Inter RNC cell update is the same with Intra RNC cell update. The difference between them is that in inter RNC cell update, the CELL UPDATE message is firstly received by DRNC and forwarded to SRNC, SRNC then take some actions according to the cause in CELL UPDATE, for example, Relocation.

Enhancement

None

Dependency


Benefits

Cell update enables UTRAN to manage a UE’s behavior and enables UE to update its state when its service or location changes. Inter RNC cell update feature enlarges the range of Cell Update through Iur interface.



4.32 WRFD-010901 Intra RNC URA Update


Availability:


Description

URA update procedure updates the UTRAN registration area of a UE when a RRC connection exists and the position of the UE is known on URA level in the UTRAN. Intra RNC URA update means URA update within RNC.

URA update may be triggered by the following two causes:

- Periodical URA Update UE will send URA Update message to RNC periodically when it is in URA_PCH state. This can be used to monitor the RRC connection.

- URA Reselection

If UE in URA_PCH state enters a new URA, it will initial the procedure, and RNC updates the camping URA of the UE accordingly.

Enhancement

None

Dependency


Benefits

URA update enables UTRAN to monitor the RRC connection and manage behaviors of the UE in URA_PCH state.



4.33 WRFD-010902 Inter RNC URA Update


Availability:


Description

URA update procedure updates the UTRAN registration area of a UE when a RRC connection exists and the position of the UE is known on URA level in the UTRAN. Inter RNC URA update means URA update between RNCs. As the intra RNC URA update, a UE in URA_PCH state shall also initiate the URA update procedure in two cases, URA reselection and Periodic URA update. The difference between Intra RNC and Inter RNC URA update is that in inter RNC URA update, the URA UPDATE message is first receipt first by DRNC and forwarded to SRNC, SRNC then takes some actions according to the cause in URA UPDATE, for example, Relocation.

Enhancement

None

Dependency

It is the essential feature for UMTS RAN.

Benefits

URA update enables UTRAN to monitor the RRC connection and manage behaviors of the UE in URA_PCH state. Inter RNC URA update enlarges the range of URA Update through Iur interface.



4.34 WRFD-021400 Direct Signaling Connection Re-establishment (DSCR)


Availability:


Description

When UE moves to the cell controlled by DRNC, SRNS Relocation procedure (UE involved or UE not involved) can be implemented to keep services continued, but when there is no Iur interface or the relocation is not supported or relocation failed, the UE will drop. In such scenario, Direct Signaling Connection Re-establishment (DSCR) feature can be used to prevent call drop. That is, the DRNC will send a RRC CONNECTION RELEASE message with cause "Directed Signaling Connection re-establishment" when it is unable to contact the SRNC to validate the UE.

The UE shall perform a Route Area Update (RAU) procedure immediately on entering PMM-IDLE state when it has received a RRC Connection Release message with cause "Directed Signaling connection re-establishment" even if the RA has not changed since the last update.

Since DSCR is used to re-establish service by RAU procedure, this feature can only be applied to PS services, and it has no help to re-establish CS services.

Enhancement

None

Dependency

None

Benefits

This feature is an necessary supplement to relocation and it can help to keep PS service continued when no Iur interface available or relocation procedure failed.



5 Transmission

5.1 WRFD-050101 Star Topology


Availability:


Description

NodeBs can be connected in star topology.

It is applicable in most cases. Each NodeB is directly connected to the RNC by E1/T1. The networking structure is simple. It is convenient to implement maintenance and engineering. Signals are transferred directly between NodeBs and the RNC, so the link is quite reliable. This networking topology can be applied in densely populated areas. It is easy to expand the capacity, but a largest amount of transport lines are required.

NodeB

RNC

NodeB

NodeB

Enhancement

None

Dependency


Benefits

In this mode, each NodeB directly connects to the RNC. Therefore, the star networking features simplicity, convenience in maintenance and engineering and easy capacity expansion.

In this mode, signals travel through fewer nodes. Therefore, the transmission is more reliable.



5.2 WRFD-050102 Chain Topology


Availability:


Description

NodeBs can be connected in chain topology.

The line reliability is poor because signals are transferred across many intermediate systems. This networking topology is applicable to the strip-shape areas of sparse population, such as expressway and railway. In these areas, the chain topology can meet the requirements with much less transmission equipment. The cascade connection is limited to five levels.

NodeBRNC NodeBNodeB

Enhancement

None

Dependency

The feature is implemented in the NODEB and RNC.

Benefits

Chain networking can reduce costs in transmission equipment, engineering, construction and transmission link lease.



5.3 WRFD-050103 Tree Topology


Availability:


Description

NodeBs can be connected in tree topology.

In most scenes, the MW (Micro Wave) network is a typically tree topology. So it is suitable for MW network. Furthermore, in order to increase the efficiency, Hub NodeB based on tree topology is introduced in RAN5.1.

The consumption of transport lines is less than that of the star networking. At same time, the line is not so reliable because signals are transferred across many Intermediate systems. It is difficult to implement maintenance and engineering. A fault occurred in the upper-level NodeB may affect the operation of the lower-level NodeBs. This networking topology is applicable to a large area of sparse population. Capacity expansion may result in reconstruction of the network.

Note:

The clock of NodeB is obtained by phase lock of the upper-level network. A phase lock can decrease the quality of the clock. Therefore, the level of cascade must be limited no more than five.

NodeB

RNC

NodeB

NodeB

NodeB

Enhancement

None

Dependency


Benefits



It is suitable for Microwave transmission network.

HUB NodeB is based on tree topology.

Tree networking requires fewer transmission links than star networking.



5.4 WRFD-050201 NodeB Clock


Availability:


Description

In compliance with 3GPP protocols, the NodeB clock must have a higher clock precision. The frequency stability of the 10 MHz master of the NodeB is lower than ±0.05 ppm.

The NodeB can work in multiple clock synchronization modes to suit different clock topologies:

l Synchronization with the Iub clock (default mode)

The clock source of NodeB can be synchronized with the line clock sources of its upper-level NE such as RNC. The NodeB selects the reference clock source from one line for the NMPT, a main control and timing unit.

l Synchronization with GPS

The GPS card is optional unless the NodeB uses a GPS clock as its clock source.

The clock signals are processed and synchronized as follows: The GSP 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.

l Synchronization with the BITS

NodeB can synchronize its clocks with the 2 MHz clock signals from an external reference clock. The reference clock can be a BITS or a 2 MHz clock from the transmission equipment.

Through phase locking and frequency dividing, the main clock module converts the clock signals into various clock signals required by the NodeB, for example, F_CLK, CLK_4X, and BFN.

In addition to the three synchronization modes above, the NodeB internal clock can work in free-run mode to keep the NodeB running.

The enhanced stratum 3 OCXO with a high precision works as the master clock of the NodeB. The OCXO can keep the NodeB in normal service for up to 90 days.

Enhancement

None

Dependency



None

Benefits

The NodeB internal clocks can be synchronized either to the transport network and no auxiliary clock equipment to reduce the cost. The synchronized clock has the required accuracy to fulfill both radio frequency and transmission network requirements.



5.5 WRFD-050202 RNC Clock


Availability:


Description

RAN clocks must provide reliable clock sources for the NEs in the RAN system; thus meeting the specifications for clock accuracy stated in protocols.

When exceptions occur to clock sources, the RNC and the NodeB must report related alarms and start the backup scheme to ensure that the system is not affected

The RNC clock sources that can be selected are as follows:

l Building Integrated Timing Supply System (BITS) l Line clock extracted from the Iu interface l Global Positioning System (GPS)

In addition to the three clock resource above, RNC can also work with local oscillator.

The clock resource selected can be configured as needed and when one clock is unavailable, it will switch to the other available one to use.

Enhancement

None

Dependency

None

Benefits

This feature provides multi clock resources for the operator to select.



5.6 WRFD-050301 ATM Transmission Introduction Package


Availability:


Description

Huawei RAN supports ATM transport optional defined in 3GPP. ATM transmission feature include following sub-features:

- ATM over E1T1 in Iub interface

- ATM over channelized STM-1/OC-3 in Iub interface

- ATM over non-channelized STM-1/OC-3c in Iub/Iu/Iur interface

- IMA for E1T1 or channelized STM-1/OC-3 in Iub interface

- Dynamic AAL2 Connections in Iub/IuCS/Iur interface

- Permanent AAL5 Connections for Control Plane Traffic

- Call Admission based on used AAL2 path BW

- CBR, rt-VBR, nrt-VBR, UBR ATM QoS Classes

Enhancement

The enhancements of ATM Transmission Introduction Package please refer to the enhancement of the features in the package.

Dependency

None



5.6.1 WRFD-05030101 ATM over E1T1 on Iub Interface


Availability:


Description

Huawei RAN supports ATM over E1/T1 electrical interface.

RNC ATM over E1/T1 interface board:

l Support 32 ports (E1/T1) per board.

l Support UNI, IMA, Fractional ATM and Fractional IMA.

l Support 32 IMA group per board.

l One IMA group supports up to 32 E1/T1 ports.

Macro NodeB BTS3812E/AE support 3 slots for transmission interface boards in RAN 5.1 and 4 slots for transmission interface boards in RAN6.0. The Macro NodeB supports NDTI and NUTI interface board.

NDTI only for ATM:

l support 8 ports(E1/T1) per board,

l support IMA, CES, Fractional ATM

NUTI board was introduced in WCDMA RAN5.1. NUTI can be used for ATM or IP. It can expand the interface type through adding daughter board. The NUTI provide the following ATM interface:

l support 8 ports(E1/T1) per board,

l support IMA, CES, Fractional ATM

NUTI and HBBU are constructed by motherboard and daughterboard.

Huawei Distributed NodeB DBS3800 support 8 ports (E1/T1) and 2FE ports on HBBU, E1/T1 can be configured as ATM or IP. NUTI also can expand the transmission through daughterboard.

Transmission daughter board:



E1 daughterboard was introduced in WCDMA RAN5.1

l 8 ports(E1/T1) per board

Enhancement

In RAN2.0, NDTI board was introduced.

In RAN5.0, HBBU board was introduced.

In RAN5.1, NUTI board was introduced.

Dependency

None

Benefits

This feature enable to using Microwave network or PDH legacy network for Iub transmission.



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


Availability:


Description

Huawei RAN supports ATM over channelized STM-1 optical interface in Iub interface.

BSC6800 ATM over channelized STM-1 interface board:

l 1 x 155Mbps port per board.

l 63 x VC12 2Mbps flows per port.

l Support 63 UNI link, or 42 IMA group per port.

l At most 32 VC12 flows per IMA group.

l Support MSP 1:1 redundancy.

BSC6810 ATM over channelized STM-1/OC-3 interface board:


l 63 x VC12 2Mbps or 84 x VC11 1.5Mbps flows per port, configurable at initiation.

l Support 63 x 2Mbps UNI links, or 84 x 1.5Mbps UNI links, or 42 IMA group per port.

l At most 32 VC12/VC11 flows per IMA group.

l Support MSP 1:1 redundancy.

NUTI board was introduced in WCDMA RAN5.1. NUTI can be used for ATM or IP. It can expand the interface type through adding daughter board.



Channelized STM-1/OC-3 daughterboard was introduced in RAN6.0.


l 63 x VC12 2Mbps or VC11 1.5Mbps flows



l HW support for MSP1+1 link and equipment protection

Enhancement

In RAN6.0, Channelized STM-1/OC-3 daughterboard was introduced

Dependency

None

Benefits

This feature enable to using SDH network for Iub transmission.



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


Availability:


Description

Huawei RAN supports ATM over non-channelized STM-1/OC-3c optical interface on Iub/Iu/Iur ATM transmission.

BSC6800 ATM over non-channelized STM-1/OC-3c interface board:


l ATM full rate, VC4 150Mbps per port.

l Support MSP 1+1 redundancy.

BSC6810 ATM over non-channelized STM-1/OC-3 interface board:


l Support MSP 1+1 and MSP 1:1 redundancy.

l Up to 2000 VCs per board shared by each port.

l Full VPI/VCI address space (VPI: 0 – 255, VCI: 32 - 65535).

NUTI board was introduced in WCDMA RAN5.1. NUTI can be used for ATM or IP. It can expand the interface type through adding daughter board.



Non-channelized STM-1 daughterboard was introduced in WCDMA RAN5.1.

l 2 x 155Mbps ports per board.

Enhancement

In RAN5.1 the Non-channelized STM-1 daughter board is introduced

Dependency



None

Benefits

This feature enable to using SDH network or ATM network for Iub/Iu/Iur transmission.



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


Availability:


Description

Iub, Iur and IuCS interfaces are all specified with user plane traffic over AAL2 connections. The transport network control plane is used to set up dynamic AAL2 connections for Iub, Iur and IuCS interface using ITU Q.2630.1/Q.2630.2 signaling.

From RAN2.0, the AAL2 CAC can be configured to separate traffic into different type AAL2 path according traffic class. The AAL2 connections for RT (Real Time) service can be established on CBR/RT-VBR VCC, then, the AAL2 connections for NRT (Non-Real Time) service can be established on NRT-VBR VCC.

From RAN3.0, AAL2 path specified for HSDPA service was introduced. AAL2 path for HSDPA can use UBR VCC. From RAN6.0, AAL2 path specified for HSDPA/HSUPA service was introduced.

Secondary AAL2 path for each traffic class was introduced in RAN6.0, which provides resiliency mechanism for Iub hybrid transmission.

Enhancement

In RAN3.0, Q.2630.2 was introduced. It supports AAL2 modification procedure and supports QoS optimization for AAL type 2 connections over Iub and Iur.

In RAN3.0, AAL2 path specified for HSDPA service was introduced.

In RAN6.0, AAL2 path specified for HSDPA/HSUPA service was introduced.

In RAN6.0, Secondary AAL2 path for each traffic class was introduced, which provides resiliency mechanism for Iub hybrid transmission.

Dependency

None

Benefits

Huawei implementation of AAL2 enables:

l Separate traffic into different type AAL2 path according traffic class (Conversational, Streaming, Interactive and Background).

l Separate traffic into different type AAL2 path according R99 traffic, HSDPA traffic and HSUPA traffic.



l Efficient Iub transmission link usage when mixing delay sensitive traffic with non-delay sensitive traffic.

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



5.6.5 WRFD-05030105 Permanent AAL5 Connections for Control Plane Traffic


Availability:


Description

In ATM RAN, AAL5 connections are used to bearing Iub/Iur/ Iu signaling and Iub OAM traffic. By 3GPP specified UNI-SAAL is used for Iub control plane connections, and NNI-SAAL is used for Iur and Iu control plane connections. In Huawei RAN, AAL5 connections for Iub, Iur and Iu interface are all set up by configuration.

Enhancement

None

Dependency

None

Benefits

Permanent AAL5 Connections for Control Plane Traffic is part of 3GPP Iub, Iur and Iu specifications.



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


Availability:


Description

The purpose of AAL2 CAC (Call Admission Control) is to maintain the quality of service and at the same time maximize the transmission resource utilization. This is achieved by selectively admitting or rejecting request for resources.

AAL2 CAC request occur at establishment or modification of AAL2 connection on Iub, Iur and IuCS interface.

For CS services, PCR * Service Factor will be used to admit,

For PS service, GBR * Service Factor will be used to admit, since no GBR will be assigned for best effort services, such parameter can be configured by operator.

For HSDPA/HSUPA, GBR * Service Factor will be used to admit, since no GBR will be assigned for best effort services, such parameter can be configured by operator.

All the service factors mentioned can be configured according to the service class.

For the handover in users, all the transmission resource will be used to admit to minimum the possibility of existing call drop.

For the new access user, (100% - handover admission threshold) transmission resource will be used.

For the bit rate upgrade user, the transmission resource under congestion threshold will be used.

Enhancement

None

Dependency

None

Benefits

This feature

l Avoids transmission congestion

l Improves the transmission resource usage

l Increases the accessibility



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


Availability:


Description

Huawei RAN supports four ATM service categories (CBR, rt-VBR, nrt-VBR and UBR) specified in TM4.1 (ATM forum specification Traffic Management 4.1). The VCC supports shaping for egress traffic according the parameters (SCR, PCR and CDVT) of each ATM service category.

The four ATM service categories are used to differentiation service on ATM layer. Two ATM service categories are configured for R99 traffic and two ATM categories are configured for HSxPA. In general, DS (Delay Sensitive) traffic use rt-VBR, NDS (None Delay Sensitive) traffic use nrt-VBR, and NDS traffic mapping on HSxPA use UBR or nrt-VBR.

Enhancement

None

Dependency

None

Benefits

The feature supports:

l Full inter-operation between RAN and ATM equipment

l VC traffic shaping

l ATM traffic differentiation



5.6.8 WRFD-05030110 F5


Availability:

This feature is introduced in RAN2.0 in BSC6800.

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, Loopback), Performance Management (Forward Monitoring, Backward Reporting) and activation/deactivation are supported. The CC can be activated to monitor AAL2 path VCC and IuPS user plane VCC End-to-End. When one VCC for AAL2 path or IuPS GTPU is LOC (Loss of continuity), AIS or RDI, this VCC will be blocked. Then the service will be established on other alternative VCCs to prevent call drop.

BSC6810 does not support Performance-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.

Dependency

None

Benefits


l ATM VCC End-to-End continuity check.

l Supervision the AAL2 path, and block the fault AAL2 path.

l Supervision the IuPS GTPU path, and block the fault GTPU path.



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


Availability:


Description

The Inverse Multiplex on ATM (IMA) mode is an ATM transport mode in the TC sub layer of ATM physical layer.

In IMA mode, an ATM cell stream is distributed to several narrowband transport links. At the peer end, the data streams from these narrowband transport links are converged into the original ATM cell stream. IMA flexibly combines several narrowband transport links to transport high-speed ATM cell streams, which is referred as inverse multiplex on ATM. By this way the existing narrowband transport links, especially 2Mbit/s links, can serve broadband ATM transmission. IMA also enhances transmission reliability.

PHY

PHY

PHY

PHY

PHY

PHY

Physical I ink #0

Physical I ink #1

Physical I ink #2Single ATM cell stream from ATM layer

Original ATM cell stream to ATM layer

IMA virtual link

IMA group IMA group

There are several IMA links in one IMA group. If one link is broken, the service can be borne by other links, only the bandwidth is shrank. It provides more redundancy for the transmission.

Enhancement

None

Dependency

None

Benefits


l Peak Rates higher than the individual physical link rates, 1.5 Mbps for T1 or 2 Mbps for E1



l Simplification of the ATM O & M procedures, i.e. monitoring as one single ATM link instead of several separate links

Higher trunk level and statistical multiplexing gain



5.8 WRFD-050305 UBR+ ATM QoS Class


Availability:

This feature is introduced in RAN 6.1

Description

Huawei RAN supports UBR+ ATM service category. UBR+ is one enhance of UBR with MCR (Minimum Desired Cell Rate) indication. UBR+ is the best choice for Iub OAM channel. The MCR of UBR+ ensures the connectivity of OAM connection when Iub transmission resource congestion, while the best effort character of UBR+ full use the transmission bandwidth.

Enhancement

None

Dependency

None

Benefits

UBR+ ensures the connectivity of OAM connection and full utility the transmission bandwidth.



6 System Reliability

6.1 WRFD-040100 Flow Control


Availability:


Description

Flow control in the Radio Network Controller (RNC) is a set of mechanisms that the RNC uses to prevent the network from being overloaded by regulating the input rate transmissions.

The system determines specific flow control measures in compliance with the load on the following two resources:

- CPU Occupancy

The CPU is the core resource for the processing capability of the system. High CPU occupancy means risk of insufficient processing capability at present. In this situation, the flow control on corresponding functions should be started to ensure basic functions of the system. After the CPU occupancy is lower than the proper threshold, the previously-started functions are enabled.

- Message Block Occupancy

The message block is the core resource for internal communication between the RNC. High message block occupancy means risk of inefficient processing capability in the system at present. In this situation, the flow control on corresponding functions should be started to ensure basic functions of the system. After the message block occupancy is lower than a proper threshold, the previously-started functions are enabled.

The flow control item corresponds to a function in the system such as printing information, debug information or system log and service related RRC connection setup request, paging message etc. The system enables, disables, or partially disables the functions in compliance with the current resource load such as the CPU occupancy and the message block occupancy to ensure system stability and robustness.

- If a flow control item is controlled, the corresponding function is disabled or partially disabled.

- If a flow control item is restored, the corresponding function is enabled again



Enhancement

None

Dependency

None

Benefits

l Ensuring stability and robustness of the RNC.

l Ensuring that services with high priorities work properly upon high traffic.



6.2 WRFD-040201 System Redundancy


Availability:


Description

Methods for reliability design are used widely, including active/standby boards, load-sharing and redundant configuration.

Enhancement

None

Dependency

None

Benefits

This feature can improve the system stability and ensure the network performance as a result.



7 RAN Operation & Maintenance

7.1 WRFD-030100 Performance Management


Availability:


Description

Performance Management provides the operator performance overview of the network. Performance measurements give the detailed information of the network and make it possible to perform trouble-shooting and network optimization.

PM Administration

The Performance Management Administration feature provides the operator the means to manage the available measurements.

For new commissioning network elements (RNC, NodeB), pre-defined statistics will be started after initial start-up phase or restart completed. It is also possible to suspend and resume statistics manually.

The network elements (RNC, NodeB) provide a machine-machine interface allowing M2000 to collect the necessary statistic data and to set the related parameters including statistic counters and period.

The statistic data is fetched by M2000 in a binary format file format every statistic period. The result files are also stored in the Network Element itself for up to 24 hours (NodeB) or 10 days (RNC) as backup in case the data transfer failure and make it possible for M2000 to re-collect the lost data later.

2．PM Counters

The performance measurements include the key counters and other ones. The key counters are used to generate the Key Performance Indicator (KPI) of the network which defined in M2000, these counters are pre-defined and initialed as soon as the RNC or NodeB started. The KPI and related original counters and formula can be added, modified and deleted in M2000. Other counters reflect the other performance of the network and can also be started as needed.

The following counter areas are supported:

l Cell Measurement

l Neighboring Cell Measurement



l Inter-RAT Neighboring Cell Measurement

l RNC Overall Measurement

l ATM Transport Measurement

l IP Transport Measurement

l Standard Interface Measurement

l Network Element Hardware Measurement

1. PM real-time performance monitoring

This feature provides monitoring the performance of the network in a real-time and graphic way, therefore, it is more convenient and easier to do troubleshooting, road test or network optimization etc.

The monitoring tasks are managed with the network elements (RNC, NodeB) Local Management Terminal (LMT). The data monitored will be shown with curve while stored to a file automatically and can be reviewed later.

The following monitoring items are supported:

l Equipment performance monitoring: CPU occupancy, clock source quality etc.

l Connection performance monitoring: SIR measurement, UE TX Power etc.

l Cell performance monitoring: PCPICH TX Power, the Number of Cell Users etc.

l Link performance monitoring: IMA Group, UNI Link etc.

l Service performance monitoring: RF performance, UL channel scanning, and service resource occupancy

Enhancement

In RAN5.1, HSDPA related performance counters and monitoring items are supported.

In RAN6.0, HSUPA related performance counters and monitoring items are supported.

In RAN10.0, IP PATH real-time performance monitoring is supported.

Dependency

Performance Management is implemented with Huawei OMC M2000 except the real-time monitoring which managed with RNC LMT.

Benefits

The Performance Management provides efficient way to collect get the network and RNC & NodeB performance. Based on which, network troubleshooting or optimization can be implemented and it can be more efficient with the real-time performance monitoring feature.



7.2 WRFD-030200 Fault Management


Availability:


Description

Fault Management includes system self-test, fault testing, fault supervision and handling of the UTRAN. With these features, operator can be informed as soon as fault occurs in the network and take proper actions to prevent outage.

System hardware self-test will be initialed in the RNC or NodeB startup phase and health check of the system can also be started manually at anytime when they enters work state.

1. Fault testing

Fault testing includes physical layer testing, link layer testing, and other fault testing. Fault testing can be started manually and the operator can browse and save fault testing results.

2. Alarm Management

Operator can browse alarm information in real time, query history alarm information, and store alarm information. The online help can provide detailed troubleshooting methods for each alarm.

RNC can store the history alarm information generated in the past 90 days and at most 100,000 alarms.

3. Alarm Correlation Handling

A run-time alarm correlation handling mechanism is supported which will filter the most important alarms instead of all the related ones when fault occurs. The alarms can be greatly reduced by this way and make it easier to locate and fix the network problem. This mechanism is pre-defined and built in the network elements (RNC, NodeB) and operator can customize more alarm correlation handling rules by M2000.

Operator can filter the alarms of a special object. If an object is filtered, the system will not report the alarms of this object to the Alarm Management System.

Enhancement

In RAN5.1, HSDPA related alarms are supported.

In RAN6.0, HSUPA related alarms are supported.

In RAN6.0, E1/T1 BER testing is supported.

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



Dependency

Fault Management can be implemented with Huawei OMC M2000 or RNC/NodeB LMT.

Benefits

l Automatic supervision of equipment in the network elements. With active alarm lists and alarm logs the operator can at any time have a comprehensive view of the actual state of the network.

l Manual initiated board test that allows the operator to quickly verify suspicious boards regarding if they are faulty or not.



l

7.3 WRFD-030300 Inventory management


Availability:


Description

The function of inventory management helps the user to manage the asset and configuration information of the network. With this function, the asset and configuration data can be queried and managed on the M2000.

The objects which are managed by this function include physical objects (rack, frame, slot, board, ports, links, fan etc.) and the logic objects (cell, software, patch, etc.).

When requested from M2000, an asset and configuration information file with XML format generates and is sent to M2000. M2000 applications store the uploaded information to the network inventory database.

Enhancement

None

Dependency

The inventory information can only be viewed in Huawei OMC M2000.

Benefits

With this function, operator can get the timely and exact decision-making data for the existing network.



7.4 WRFD-030400 Configuration Management


Availability:


Description

Configuration Management provides operator the way to collect and management the Network Elements (RNC, NodeB) data. It can also controls the links between the NEs. The graphical user interfaces make it easy to implement the management.

The configuration of the network elements can be divided into five levels:

1. Initial configuration.

RNC and NodeB equipment specific configuration

2. Site basic configuration.

Configuration of the O&M communication between RNC, NodeB and M2000

3. Site external HW configuration in NodeB

Configuration of TMA data, antennas

4. Site-specific configuration in RNC and NodeB

Interfaces as Iu, Iub, Iur and transport network data

5. Cell Network configuration in RNC

Cells, channels and adjacent cells data

Level 1-3 are done at site either with the configuration tool via the graphical user interfaces or with LMT via executing pre-made configuration files. Levels 4-5 are easiest done from M2000, but can also be done using the configuration tool.

1. Online and Offline Data Configuration and Status Query

Offline data configuration makes configuration data stored only on the BAM server. The data is not sent to the host before being loaded to the host. Therefore, this mode can increase the efficiency of configuring a large quantity of data. RNC also supports offline configuration based on host sub-racks. Therefore, it allows capacity expansion without interrupting services.

Offline configuration supports directly modifying the interface board type and board active/standby mode, with the scenario of modification of ATM interface board into IP interface boards and vice versa excluded.

Online data configuration makes configuration data sent to the host immediately after the configuration. There is no need to reset the system and reload the data.



X.731 defines the status of objects. User can query the object status and obtain the time of last status change, such as the board or cell status.

2. Configuration Authority Control

Under configuration authority control, data can be configured on only the RNC/NodeB LMT or the M2000 client at any time. Moreover, only one user has the configuration right at any time. This function enhances the reliability of the system.

3. Configuration Rollback in RNC

When the equipment or network malfunctions due to improper data modification, the operator can perform the rollback operation to restore the system in a short period.

4. RNC Data Backup

The BAM servers work in the active/standby modes. The system synchronizes the data on the standby BAM server with that on the active.

RNC supports automatic backup and manual backup. It provides a data backup and restoration tool.

5. Network Parameter Setting

The radio network parameters include two types, RNC-oriented and cell-oriented parameters, which can adapt to different radio environments. RNC can check the integrity and consistency of configuration data, such as the data of a cell.

6. Missing Neighboring Cells Detection

Based on the measurement information from UE, the missing configured neighboring cells can be detected and reported. This can help operator to optimize the configuration of neighboring cells, and therefore, improve the network planning efficiency.

Enhancement

In RAN5.1, Directly modifying the interface board types and board active/standby mode in offline way is supported.

In RAN5.1, Query of the last status change time is supported.

In RAN10.0, NodeB state notification to M2000 is supported.

Dependency

Configuration Management can be implemented with Huawei OMC M2000 or RNC/NodeB LMT.

Benefits

l Good overview of the current status of the network.

l Support for fast installation, expansion and configuration of the network



7.5 WRFD-030501 Security Management


Availability:


Description

The security management includes the following functions to enhance system security level:

l User management: this mechanism allows the setting of the user account and authority, the related authorized command group and operation can also be managed.

l System data backup and restore.

l Applying Windows OS security policy to limit the BAM server IP connectivity ports to decrease potential threaten to the system.

l Support installing popular anti-virus software including Norton, Macfee and Officescan.

l Support collecting the database operation log and auditing security log.

l Support triggering alarms in case of detection of network attack or unauthorized access exceeds the configured threshold, etc.

l FTP over SSL (Security Socket Layer).

l Support SSL for data communication between RAN and OMC, therefore, all the remote maintenance communication will be encrypted.

Enhancement

In RAN6.0, FTP over SSL is supported.

In RAN10.0, SSL for data communication between RAN and OMC is supported.

Dependency

None

Benefits

This feature provides the user authorization and management mechanism to enhance network management security level. It also prevents the system from accessing by the unauthorized user.



7.6 WRFD-030601 Interface Tracing


Availability:


Description

This feature can be used to trace the interface message online or offline, and manage the equipment daily.

The operator can verify the configure data and fix the exception through the tracing and interpreting the messages of Iu, Iub, Iur, and Uu. After the configure data was set, the operator can confirm whether the signal links are correct through the tracing and interpreting the messages of Iu, Iub, Iur, and Uu. If something wrong, the operator can also fix the exception through the tracing and interpreting the messages of Iu, Iub, Iur, and Uu.

So tracing and interpreting the messages of Iu, Iub, Iur, and Uu can instead of the signal analyzer. It can be used to analyze the compatibility when the IOT between RNC and other network elements.

Based on this feature, the operator also can do the network optimization.

Enhancement

None

Dependency

None

Benefits

This integrated interface tracing feature can provide operator convenient way to monitor the signaling procedure on the radio and transport interface, and help network optimization and problem solving.



7.7 WRFD-030602 Call Tracing


Availability:


Description

This feature supports specific UE signaling tracing. This can be used to trace a specific UE to confirm the network status and based on which, the operator can do the network optimization.

Enhancement

None

Dependency

None

Benefits

This integrated user tracing feature can provide operator convenient way to monitor the specific UEs signaling procedure on the radio and transport interface, and help network optimization and problem solving.



7.8 WRFD-030701 RNC Software Management


Availability:


Description

RNC supports the software management feature. This feature could help operator to manage the software on RNC remotely and easily. Operator could finish the following items through MML commands.

l Support operators query the version and other running state information of software.

l Support operators upload, download and activate the software, like program files, patch files and license file. And also support operator backup the data files and log files to FTP server.

l Support all type files transmission, and also support the wildcard used.

l Support remote patch upgrade for RNC BAM server.

l RNC could be used like a transfer agent and support the file transferred between the M2000 and NodeB.

RNC also supports the operator uses the other standard FTP software to transfer files.

Besides, operator could control the products software (including program, patch, license, data, log, etc) from OMC, also the OMC support that the products software version could be matched and distinguished. The software management could improve the operators work efficient on products upgrade, data download, etc.

Enhancement

In RAN5.1, remote patch upgrade for RNC BAM server is supported.

In RAN6.1, the dual active/backup memory management is introduced in BSC6810 which allows the different software exists at the same time, but only one software version is activated, with this enhancement, software upgrade becomes more convenient and simple, and moreover, the roll back procedure can be also improved.

In RAN10.0, the uniform patch method of BAM and RBS is supported.

Dependency

None

Benefits

l Efficient and correct installation and upgrade of software packages.



l Pre-check of node to verify a successful software installation and upgrade.

l Automatic data conversion at software upgrade.



7.9 WRFD-030702 NodeB Software management


Availability:


Description

The NodeB software management includes the following functions:

l Efficient and correct installation and upgrade Software

l Compatibility checking on software and hardware versions to verify a successful software installation and upgrade

l Version management, for example, hardware and software version query

l Automatic data conversion at software upgrade

The process of upgrading software in a network element is divided into three sub-activities: Download the software package from the M2000 to the NodeB through the IPoA channel between the RNC and the NodeB. Executes the software activation command on the M2000 client. The NodeB automatically loads the software to its associated boards. The NodeB automatically switches between the active and standby directories.

The following is Enhancement feature of software management:

l UBR/UBR+ is supported on OM IPOA channel: If the traffic is busy, the IPOA channel is fixed in 64Kbps, and when the traffic is idle, the IPOA channel bandwidth will be automatically increased to ensure the high efficiency software download.

l Download software according to configuration: Download software according to configuration which can reduce 30% of the software package and shorten the download time. For adding board, system support only download the adding board software to improve the efficiency of software download.

l Resume software download: If network recovery during the period of 24 hours after network breakdown, system supports to resume software download to avoid the repeat of downloading.

l Download and active software in batches: The maximum 500 NodeBs can be select to download and active software in batches automatically. The default is 50 NodeBs in one batch.

l Hot patch online: Hot patch without the resetting of NodeB which is made with the aim of minimizing negative traffic impact.

Enhancement



In RAN5.1, the following NodeB enhancement features are introduced.

l UBR is support on OM IPOA channel

l Download software according to configuration

l Resume software download

l Download and active software in batches

l Online hot patch

Dependency

None

Benefits



7.10 WRFD-031100 BOOTP


Availability:


Description

NodeB supports BOOTP in Iub interface. NodeB can connect with RNC automatically with default O&M channel without data configured in system

When no data configuration file is loaded to NodeB, the default IPoA maintenance channel can be automatically set up between RNC and NodeB. Generally, NodeB only has software loaded rather than data configuration file after hardware installation. With this function, the maintenance personnel can load data and programs to the NodeB at the far end. The automatic setup function of default maintenance channel decreases the operation and maintenance costs and enhances network maintainability and maintenance quality.

Enhancement

None

Dependency

None

Benefits

The feature can enable the automatic setup of the default maintenance channel from the far end, so it enables maintainers to load data and software to the NodeB, enhances the maintainability of the network.



7.11 WRFD-031101 DHCP

Feature Number: WNFD-031101

Availability:


Description

In IP mode, the IP maintenance channel is automatically set up through the DHCP.

Dynamic Host Configuration Protocol (DHCP), based on BOOTP, dynamically provides configuration parameters for Internet terminals. The difference between BOOTP and DHCP is that the latter supports automatic allocation of network addresses. DHCP works in client/server mode. At the receipt of the request from a client, the server provides parameters such as IP address, gateway address, DNS server address for the client. DHCP simplifies IP address management and enables centralized IP address management. DHCP is implemented in compliance with RFC2131 and RFC2132.

During the DHCP procedure, the RNC works as the server and NodeBs work as clients. Through the DHCP procedure, the NodeB can automatically obtain the IP address for maintenance, set up the OM channel, and perform remote maintenance on the RNC LMT.

Enhancement

None

Dependency

None

Benefits

The feature can enable the automatic setup of the default maintenance channel from the far end, so it enables maintainers to load data and software to the NodeB, enhances the maintainability of the network.



7.12 WRFD-030800 License Management


Availability:


Description

License control is used to control the amount of capacity and what optional features can be used in the network.

RNC and NodeB have its own license file. The license file can be downloaded remotely to the node. Operator can manage and query the license content by LMT or M2000 client.

M2000

M2000

M2000

NodeB

RNC

RNS-1

M2000

M2000

NodeB

RNC

RNS-2

Characteristics of the NodeB license management are as follows:

l For all the NodeB under the one RNS, they have one license file. One RNS corresponds to one license file. Each license file records the total number of licenses used by all the NodeBs under one RNS.

l Licenses are distributed on the M2000 and are controlled on the NodeBs. The distribution results are sent to NodeB from the M2000.

l Licenses can be allocated between NodeBs, but they cannot be distributed between RNSs. The total number of licenses cannot exceed the recorded number in the license file.



New or updated license files can be customized and ordered from Huawei.

Enhancement

None

Dependency

None

Benefits

Fast expansion of capacity can be supported without a site visit, and therefore, decrease the cost in the initial cost of network construction.



7.13 WRFD-030900 High Efficiency DNBS OM


Availability:


Description

Distributed NodeB provides the following Enhancement feature of operation management:

l RRU test locally with test button and LED indicator: HUAWEI RRU provides visual indicators displaying status of operation are required. Furthermore, it supports near end performance test by test button and indicator which can provide the VSWR test, feeder system and CPRI interface loop test.

l Loop RRU network protection

l Optical module can be replaced on site

l RRU network topology scanning automatically.

Enhancement

In RAN6.0, RRU network topology can be scanned automatically,

Dependency

None

Benefits

Provide convenient O&M functionalities for DNBS to save OPEX for operator.



7.14 WRFD-031000 Intelligently Out of Service


Availability:


Description

Intelligently out of service will be trigged in the following cases:

l Voltage of the batteries is lower than a pre-set threshold after AC power shut down

l Software upgrade

l Reset NodeB

l Cell block

When the out of service is triggered, the PCPICH powers of the cells can be lowed step by step until the UEs are handover to other 2G or 3G cells. For example, the PCPICH powers can be lowed 1dB per 200ms. This allows the traffic to be handover to other 2G or 3G cells without dropping the calls before cell out of service.

Enhancement

None

Dependency

None

Benefits

This feature allows the traffic to be handover to other 2G or 3G cells without dropping the calls before cell out of service.



7.15 WRFD-031200 OCNS


Availability:


Description

NodeB integrates an orthogonal code noise simulator (OCNS). This feature enables the operator to perform radio load tests without the need of numerous UEs.

There are sixteen codes with spread factor of 128 being utilized in one cell, and any variation of the codes being utilized in OCNS is not permitted. OCNS function is very convenient. Whatever the purpose is, the user need only to configure the required OCNS load ratio by M2000. OCNS load ratio is expressed by the percentage of required simulation power over the maximum transmission power of a cell.

Enhancement

None

Dependency

None

Benefits

Provide an embedded function to simulate cell load in NodeB, it makes cell load test more convenient.



7.16 WRFD-031300 Documentation


Availability


Description

The RAN Customer Documentation includes following documents:

l RAN system-level documents l RNC documents l NodeB documents

The documents cover the planning, installation, commissioning, and maintenance of the RAN system.

RAN system-level documents mainly include the following information:

l Documentation guide: describes how to search and use the RAN documents. l Planning guide: describes how to plan the network, transport, hardware and OM

network. l Maintenance guide: gives the routine maintenance and emergency maintenance

methods and troubleshooting methods of the equipments. l Optimization guide: gives the radio network optimization principles and

suggestions, and the experiences for the future network expansion. l Reconfiguration guide: describes the operation procedures for RAN

reconfiguration.

RNC and NodeB documents introduce the function and features, technical indices, equipment components of the NE, and also tell how to maintain the equipments. The documents are basically classified into the following categories:

Document Categories Description

Product description

Introduces the key benefits, system architecture, services and functions, operation and maintenance network, reliability and technical specifications of the NE.

Hardware description Introduces the hardware of the NE, including cabinet, boards and cables.

Site preparation guide Introduces the preparation items before hardware installation of the NE.

Installation guide Introduces the installation procedures of the BTS3812E cabinet, the boards, the cables.

Initial configuration guide Introduces how to conduct the initial configuration of the NE.



Document Categories Description

Commissioning guide Introduces how to commission the NE, which helps you ensure that the new NE can access the WCDMA RAN system.

LMT user guide Introduces the installation, interfaces, functions, and routine operation and maintenance of the Local Maintenance Terminal (LMT).

Site maintenance guide Introduces the routine hardware maintenance item and the replacing procedures of the parts of the NE.

Reference

Including the following reference documents. ü MML command reference: introduces the

parameter value, suggest value, default value, etc of each command.

ü Alarm reference: introduces the meaning of the alarm and how to clear them.

ü Performance counter reference: introduces the meaning, measurement point, etc of each counter.

The online-help-type of these reference documents can also be obtained in the LMT.

l Well-navigated: RAN customer documentation is planned on the basis of network

life cycles and roles. All tasks are scenario-based to make the documentation practical.

l Complete RAN information: Both the system and content of RAN documentation are greatly improved.

l Topic-oriented: Based on the DITA technology, the information will be chunked into separate topics.

l Powerful search: The information can be searched by products and data types.

Enhancement

None

Dependency

The documentation will be delivered with the CD when the product delivered.

Benefits

Operator can get complete product information, technical description for supporting the daily equipment maintenance



8 NodeB Antenna System Solution

8.1 WRFD-060001 Connection with TMA (Tower Mounted Amplifier)


Availability:


Description

TMA is an optional equipment of antenna and feeder system. NodeB supports connection with TMA. It can increase the uplink coverage range and cell radius of uplink.

The TMA Huawei provided is dual TMA, which means that the TMA hosts 2 TX/RX branches in one unit, and only one TMA per sector is needed. TMA basic function diagram is described below. Each TMA include 2 branches and one LNA supervision and alarm generation unit. The function for both branch are same and one branch function is described as following. Rx channel of each branch includes two Rx filters and a low noise amplifier. Low noise amplifier can be auto passed when DC is faulty. There is a BIAS TEE in the BTS port of TMA. For SMART TMA, this bias tee is called smart bias tee. It can separate not only DC from the feeder and provide power supply to LNA, but also RET control signal to RCU. Tx channel includes a Tx filter.

Huawei support two kinds of TMA that the gain is 24dB and 12dB, and the typical noise figure is 1.4dB.



Enhancement

In RAN5.0, smart TMA is supported.

Dependency

None

Benefits

In uplink coverage limited network, the usage of TMA can improve the receiver sensitivity, enlarge the cell radius, reduce the number of NodeB and save the investment.



8.2 WRFD-060002 Remote Electrical Tilt


Availability:


Description

The Remote Electrical Tilt (RET) refers to an antenna system whose down tilt is controlled electrically.

After an antenna is installed, the down tilt of the antenna needs to be adjusted due to network optimization. In this situation, the phases of signals that reach the elements of the array antenna can be adjusted through electrical control. Then, the vertical pattern of antenna can be changed.

The phase shifter inside the antenna can be adjusted through the step motor outside the antenna, you can adjust the down tilt of the RET antenna when the system is powered on and monitor the real time down tilt. Therefore, remote precise adjustment of the antenna down tilt can be achieved.

The following figure shows the operating principle of the RET antenna.

RCU

Phase shifter

Pulling bar

Radome

Control cable

(DC+ control signals)

Operating principle of the RET antenna

A pulling bar connects the step motor and the phase shifter. When the step motor is started, the pulling bar moves and then the phase of the phase shifter changes through the gearing. In this situation, the phase of the signals arrived at each element



antenna inside the array changes regularly. Then, the direction of the main beam of the antenna changes accordingly. The down tilt of the antenna is adjusted.

The NodeB supplies DC power to the step motor and communicates with it through the AISG interface on the motor.

In Huawei's RET solution, the RET system can either be remotely controlled on the M2000 or be locally controlled on the NodeB Local Maintenance Terminal (LMT).

As shown in the following figure, the operating principle of the RET applied to the NodeB (BTS3812E/AE) is described as follows:

l A command is sent to the BTS3812E and BTS3812AE on the M2000 or the LMT.

l The NMON on the NodeB modulates that command to On-Off-Keying (OOK) signals and then supplies them to the MAFU through the control cables in the cabinet.

l The MAFUs transfer the DC power and the OOK signals to the STMA or the SBT through feeders from the connectors on top of the cabinet.

l The STMA or the SBT demodulates the OOK signals to RS485 signals and then supplies the RS485 signals and part of the DC power to the RCU.

RNC

Iub

LMT

RC

U

STMA STMA STMA

SBT SBT

BB Subrack

MA

FU 0

MA

FU1

MA

FU2

MA

FU3

MA

FU4

MA

FU5

TRU Subrack

RC

U

RC

U

RC

U

RC

U

RC

U

NMON

M2000

SBT

Operating principle of the RET applied to the BTS3812E and BTS3812AE



As shown in following figure, the RET applied to Huawei's DBS3800 support the following modes:

Direct connection through multi-core cables. In this mode, the distance between the RRU and the RCU is shorter than 20 m.

SBT mode. In this mode, the distance between the RRU and the RCU is longer than 20 m and the TMA is not required for the DBS3800.

STMA mode. In this mode, the distance between the RRU and the RCU is longer than 20 m and the TMA is required for the DBS3800.

Antenna

RC

U

BBU

Antenna

RC

USBT

BBU

Antenna

RC

U

BBU

STMA

Direct connectionthrough multi-core

SBT STMA

RRU

RRU RRU

RET applied to the DBS3800

l For the direct connection through multi-core cables. A command is sent to the BBU on the M2000 or the LMT, and then the BBU transfers that command to the RRU. The RRU modulates the command to RS485 signals, and then transfers the signals and the DC power to the RCU through multi-core cables.

l For the SBT mode. A command is sent to the BBU on the M2000 or the LMT, and then the BBU transfers that command to the RRU. The RRU transfer the DC power and the OOK signals to the SBT from the connector on top of the cabinet. The SBT demodulates the OOK signals to RS485 signals and then supplies the RS485 signals and part of the DC power to the RCU.



l For the STMA mode. A command is sent to the BBU on the M2000 or the LMT, and then the BBU transfers that command to the RRU. The RRU transfers the DC power and the OOK signals to the STMA from the connector on top of the cabinet. The STMA demodulates the OOK signals to RS485 signals and then supplies the RS485 signals and part of the DC power to the RCU.

HUAWEI RET solution supports 3G RET cascading control. Several 3G RET antennas can be cascaded and control signal comes from same control cable. The cascading helps you save costs of Smart Bias-Tees (SBTs).

HUAWEI RET solution supports 2G/3G RET cascading control. 3G RET antennas can be cascaded with 2G RET antennas. On the 3G Operation and Maintenance Center (OMC), you can control the down tilt of a 2G RET antenna. The cascading helps you save costs of Smart Bias-Tees (SBTs) and STMAs when 2G and 3G RET antennas are installed in the same place.

Antenna

BTS3812E

RC

U

SBT

Antenna

RC

U

Sector 1

Antenna

RC

U

Sector 2 Sector 3



Enhancement

In RAN6.0, 3G RET cascading control and 2G/3G RET cascading control is introduced.

Dependency

None

Benefits

Application of the RET can prominently improve work efficiency and minimize the O&M cost for adjusting the antenna down tilt. Application of the RET have the following benefits:

l The RET antennas at multiple sites can be adjusted remotely within a short period. This improves work efficiency and saves cost for network optimization.

l Adjusting of the RET antenna can be performed in all weather condition. l It is easy to operate the RET antennas located in some sites that are difficult to

access.

When the down tilt of the RET antenna is large, the coverage pattern keeps undistorted, signal strength is strong, and interference between neighboring cells is small.

BTS3812E 2G BTS

RC

U SBT

Dual Band Antenna

RC

U



8.3 WRFD-060003 Same Band Antenna Sharing Unit (900 MHz)


Availability:


Description

SASU900 can combine two same band signals into one with very low insertion loss when

the old system uses diversity antenna. Its basic guidance is as follows: Two different

systems’ downlink Tx signals use one dual polarity antenna’s two different antenna

channels, one uses main antenna and the other uses diversity antenna. So it will bring in

low Tx insertion loss. In terms of Rx signal, each antenna’s channel’s Rx signal is

separated into two paths, one is used as a system’s main Rx signal, and the other is used

as the other system’s diversity Rx signal. So the Rx splitter will bring in Rx insertion loss

which can be compensated by adding a LNA (lower Noise Amplifier).

The SASU900’s connection diagram in system is as follows:



The configuration of the SASU900 in the GSM900 and UMTS900 co-siting system

Note: We define ANT_M as UMTS system’s main antenna port, and ANT_D as UMTS system’s diversity antenna port. So ANT_D is GSM system’s main antenna, and ANT_M is GSM system’s diversity antenna port.

There is a limitation when using the SASU: GSM will only use one antenna branch.

To allow GSM 2 antenna use case, SASA (Same band Antenna Sharing Adapter) will be introduced. SASA mainly used to combine 2 branches GSM carriers to one antenna branch, and keep the combination/division loss as low as possible. When sharing the antenna with WCDMA, The GSM carriers are preferred to locate separately as “sandwich”



SASA function block.

The typical network diagram of sharing antenna is listed below:

Enhancement

None

Dependency

None

BTSGSMBTSGSM

SASASASA

NodeBUMTSNodeBUMTS

SASU Note : All the bands is shown as DL bands

DL BandDL Band

DL Band

DL Band



Benefits

To share the same band antenna, decrease the uplink division loss. Compared to traditional combiner and diplexer, it saves 3dB gain.

Function Description of UMTS RAN10.0(Basic).pdf

Documents

Transcript of Function Description of UMTS RAN10.0(Basic).pdf