basic feature description of huawei umts ran11.1 v1.1(20090910)

Basic Feature Description of Huawei UMTS RAN11.0

Contents

Basic Feature Description of Huawei UMTS RAN11.1

IssueV1.1

Date2009-9-10

HUAWEI TECHNOLOGIES CO., LTD.

Copyright Huawei Technologies Co., Ltd. 2009. All rights reserved.No part of this document may be reproduced or transmitted in any form or by any means without prior written consent of Huawei Technologies Co., Ltd.

Trademarks and Permissions and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd. All other trademarks and trade names mentioned in this document are the property of their respective holders.

Notice

The purchased products, services and features are stipulated by the commercial contract made between Huawei and the customer. All or partial products, services and features described in this document may not be within the purchased scope or the usage scope. Unless otherwise agreed by the contract, all statements, information, and recommendations in this document are provided AS IS without warranties, guarantees or representations of any kind, either express or implied.The information in this document is subject to change without notice. Every effort has been made in the preparation of this document to ensure accuracy of the contents, but all statements, information, and recommendations in this document do not constitute the warranty of any kind, express or implied.

Huawei Technologies Co., Ltd.

Address:Huawei Industrial Base

Bantian, Longgang

Shenzhen 518129

People's Republic of China

Website:http://www.huawei.com

Email:[email protected]

Telephone:0755-28560000 4008302118

Fax:0755-28560111

Contents71 System Improvement

71.1 WRFD-000001 System Improvement for RAN5.1






172 Standards Compliance

172.1 WRFD-010101 3GPP R7 Specifications

182.2 WRFD-010102 Operating Multi-band

192.3 WRFD-010201 FDD Mode

203 RABs and Services

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

213.2 WRFD-010501 Conversational QoS Class

223.3 WRFD-010502 Streaming QoS Class

233.4 WRFD-010503 Interactive QoS Class

243.5 WRFD-010504 Background QoS Class

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

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

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

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

283.7 WRFD-021104 Emergency Call

304 RAN Architecture & Functions

304.1 MRFD-210604 2-Way Antenna Receive Diversity

314.2 WRFD-010205 Cell Digital Combination and Split

324.3 WRFD-010208 Fast Power Congestion Control (FCC)

334.4 WRFD-010211 Active TX Chain Gain Calibration

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

354.6 WRFD-010401 System Information Broadcasting

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

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

395 Channel Resource Management

395.1 WRFD-020900 Logical Channel Management

405.2 WRFD-021000 Transport Channel Management

425.3 WRFD-022000 Physical Channel Management

485.4 WRFD-021101 Dynamic Channel Configuration Control (DCCC)

496 Network Security

496.1 WRFD-011401 Integrity Protection

506.2 WRFD-011402 Encryption

527 Power Control

527.1 WRFD-020501 Open Loop Power Control

537.2 WRFD-020502 Downlink Power Balance

547.3 WRFD-020503 Outer Loop Power Control

557.4 WRFD-020504 Inner Loop Power Control

578 Cell Management

578.1 WRFD-020101 Admission Control

598.2 WRFD-020102 Load Measurement

608.3 WRFD-020106 Load Reshuffling

628.4 WRFD-020107 Overload Control

638.5 WRFD-020108 Code Resource Management

659 Network Sharing

659.1 WRFD-021301 Shared Network Support in Connected Mode

669.2 MRFD-210104 BSC/RNC Resource Sharing

6810 Mobility Management

6810.1 WRFD-020201 Intra Node B Softer Handover

6910.2 WRFD-020202 Intra RNC Soft Handover

7010.3 WRFD-020203 Inter RNC Soft Handover

7010.4 WRFD-020301 Intra Frequency Hard Handover

7110.5 WRFD-010801 Intra RNC Cell Update

7210.6 WRFD-010802 Inter RNC Cell Update

7310.7 WRFD-010901 Intra RNC URA Update

7410.8 WRFD-010902 Inter RNC URA Update

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

7711 Node B Networking Modes

7711.1 WRFD-050101 Star Topology

7811.2 WRFD-050102 Chain Topology

7911.3 WRFD-050103 Tree Topology

8112 Clock

8112.1 MRFD-210501 BTS/NodeB Clock

8212.2 MRFD-210502 BSC/RNC Clock

8513 ATM Transmission Introduction Package

8513.1 WRFD-050301 ATM Transmission Introduction Package

8613.1.1 WRFD-05030101 ATM over E1T1 on Iub Interface

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

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

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

9013.1.5 WRFD-05030105 Permanent AAL5 Connections for Control Plane Traffic

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

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

9313.1.8 WRFD-05030110 F5

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

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

9615 UBR+ATM QoS Class

9615.1 WRFD-050305 UBR+ ATM QoS Class

9716 Link Aggregation

9716.1 MRFD-210103 Link Aggregation

9917 System Reliability

9917.1 WRFD-040100 Flow Control

10017.2 MRFD-210101 System Redundancy

10117.3 MRFD-210102 Operate System Security Management

10418 RAN Operation & Maintenance

10418.1 MRFD-210301 Configuration Management

10618.2 MRFD-210302 Performance Management

10918.3 MRFD-210303 Inventory Management

11118.4 MRFD-210304 Faulty Management

11418.5 MRFD-210305 Security Management

11619 Message Tracing

11619.1 MRFD-210801 Interface Message Tracing

11719.2 MRFD-210802 User Signaling Tracing

11920 Software Management

11920.1 MRFD-210401 BSC/RNC Software Management

12020.2 MRFD-210402 BTS/NodeB Software Management

12220.2.2 MRFD-210310 BTS/NodeB Software USB Download

12320.3 WRFD-031100 BOOTP

12320.4 WRFD-031101 DHCP

12521 License Management

12521.1 MRFD-210403 License Management

12822 Basic Node B Functions

12822.1 MRFD-210309 DBS Topology Maintenance

13022.2 WRFD-031000 Intelligently Out of Service

13122.3 WRFD-031200 OCNS

13122.4 WRFD-010212 Improved CE Mapping for E-DCH

13323 Documentation

13323.1 MRFD-210701 Documentation

13524 Node B Antenna System Solution

13524.1 MRFD-210601 Connection with TMA (Tower Mounted Amplifier)

13724.2 MRFD-210602 Remote Electrical Tilt

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

14425 Acronyms and Abbreviations

1 System Improvement1.1 WRFD-000001 System Improvement for RAN5.1

AvailabilityThis feature is available from RAN5.1.Summary

This feature is based on 3GPP R5 with a series of newly introduced RAN products and functions, which meets a wider range of customer requirements and improves the performance of the product.Benefits

The benefits of the system improvements include the following:

Wider product range, including new products and configurations

Improvement in stability and robustness due to improved functions and algorithms

Improved performance, including higher capacity Enhanced usability, and reduced operating costsDescriptionCompatibility with 3GPP Release 5

The UMTS RAN5.1 is based on the 3GPP Release 5, which adds a number of important functions for RAN and UE. The major new feature is the high speed downlink packet access (HSDPA), introduced in the 3GPP Release 5. All relevant interfaces are updated according to the June 2004 version of Release 5, and all essential 3GPP Release 5 CRs since then have been implemented. The HSDPA Phase 2 is the enhancement of Phase 1, which provides 3.6 Mbit/s per user downlink speed.

The 3GPP TR 25.933 IP transport in the UTRAN is implemented in RAN5.1. RAN5.1 is the first version to provide the Iub IP transmission. The IP transmission provides new solutions to the last mile access to the Node B. Thus, it saves the cost of the transmission.New products and configurations supportedThe UMTS RAN5.1 supports the following new products and configurations:I. RNC

Supporting quakeproof cabinets that are suitable for the scenarios with specific quakeproof requirementsII. Node B DBS3800 supports Band 1 (2100 MHz) RRU, 2 carriers 40 W DBS3800 supports Band II (1900 MHz) RRU, 2 carriers 20 W DBS3800 supports Band III (1800 M) / IX (Japanese 1800 M) RRU, 2 carriers 20 W

BTS3812E/A supports Band 1 (2100 MHz) new MTRU, 2 carriers 40 W with Doherty PA for Band I (2100 M) BTS3812E/A supports Band II (1900 MHz) MTRU, 2 carriers 40 W BTS3812E/A supports Band III (1800 MHz) MTRU, 2 carriers 40 W The new transmission interface card NUTI supports the FE ports

The BBU-interconnecting provides smooth expansion for the DBS3800. The network can support the evolution from 3 x 1 to 3 x 2.

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

High efficiency power amplifier supportedThe UMTS RAN5.1 introduced the DPD + Doherty power amplifier.

The digital pre-distortion (DPD) is linearity technology which features stability, wider signal band and ability to process multi-carrier signals. The Doherty technology is used to separately amplify the average part and the peak part of the input signal and then combine both to achieve high efficiency. The efficiency of Huawei DPD + Doherty PA is 33% and above.

For the Node B BTS3812E and BTS3812AE, the output power at the Node B antenna port can be up to 40 W. DBS3800, the output power at the Node B antenna port can be up to 40 W. The support provided by two carriers and high output power for one RF module (MTRU or RRU) facilitates smooth capacity expansion, and no additional RF modules are required when the single-carrier configuration is upgraded to the dual-carrier configurationEnhancementNone.DependencyNone.1.2 WRFD-000002 System Improvement for RAN6.0

AvailabilityThis feature is available from RAN6.0.Summary



Wider product ranges, including new products and configurations The iDBS3800 is one of the best solutions for indoor coverage. Usability enhancements, reducing operating costsDescriptionCompatibility with 3GPP Release 6The UMTS RAN6.0 is based on the 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 the high speed uplink packet access (HSUPA). All relevant interfaces are updated according to the March 2006 version of Release 6. New products and configurations supportedThe UMTS RAN6.0 supports the following new products and configurations:

BTS3812E/AE supports Band V (850 MHz) MTRU, 2 carriers 40 W BTS3812E/AE supports Band VIII (900 MHz) MTRU, 2 carriers 40 W DBS3800 supports Band V (850 MHz) RRU, 2 carriers 40 W DBS3800 supports Band VIII (900 MHz) RRU, 2 carriers 40 W iDBS3800, which is for indoor coverage. BTS3812AE, a new outdoor macro Node B, improves the outdoor cabinet compared with BTS3812A.The iDBS3800 is one of the best solutions for indoor coverage. The iDBS3800 contains three parts: the Base Band Unit (BBU), the Radio HUB (RHUB) and the Pico Remote Radio Unit (Pico RRU). The Pico RRU connects to the RHUB through the CAT5 interface, and one RHUB can support a maximum of 8 Pico RRUs. The RHUB connects to the BBU through the optic fibers, and the BBU can support a maximum of 24 RHUBs. The iDBS3800 supports multiple networking modes. It supports up to 192 RF front-end units. The RRU can be networked with the passive distributed antenna system (PDAS) or work as the active distributed antenna system (ADAS). The solution is applicable to the requirements of buildings and districts on different scales.

The iDBS3800 supports the transmission over optic fibers or the CAT 5 cables. The RHUB can also provide the remote power supply to the Pico RRU. Thus, the iDBS3800 can be deployed easily and quickly, thus reducing the engineering cost.

EnhancementNone.DependencyNone.1.3 WRFD-000003 System Improvement for RAN6.1

AvailabilityThis feature is available from RAN 6.1.Summary

This feature is based on 3GPP R6 with a series of newly introduced RAN products and functions, which meets a wider range of customer requirements, improves the performance of the product, and enhances some features.Benefits


Wider product range, including new products and configurations The BSC6810 provides higher capacity and tighter structure. New features and enhancement.DescriptionCompatibility with 3GPP Release 6The UMTS RAN6.1 is based on the 3GPP Release 6, which adds a number of important functions for RAN and UE. The major new feature that is introduced in the 3GPP Release 6 is the HSUPA. All relevant interfaces are updated according to the March 2006 version of Release 6. New products and configurations supportedThe UMTS RAN6.1 supports the following new products and configurations:

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

Clock server, the new equipment to provide synchronization signals for the Node B A new RRU module RRU3804 is introduced in DBS3800 (2100 MHz). RRU3804 supports 60W TOC with A-Doherty 4 carrier. DBS3800 supports Band IV (1700 MHz / DL 2100 MHz) RRU, 2 carriers 40 W

900 MHz Same band Antenna Sharing Unit (SASU), Same band Antenna Sharing Adapter (SASA) provide a solution for the intra-band antenna system shared between the GSM900 and UMTS900 The Node B supports the AISG2.0 protocol.

The RRU3804 is a high output power remote radio unit with four carriers; the output power at the antenna port is 60W. The RRU optimizes the mechanical layout, the new slim shape leads to easy deployment. Due to the natural heat dissipation, the RRU without fan improves the reliability and reduces the maintenance cost.

New features and enhancement supported IP transmission on the Iu/Iur interfaceIP transmission on the Iu/Iur interface is available from RAN6.1, which decreases the transport cost to a great extent compared with the ATM transport cost.

Iu flex enhancementThe Iu flex enhancement includes enhanced load balancing and load re-distribution. This feature improves the performance and meets the operators load distribution strategy in the Iu flex networking scenario. RAN sharing phase2

In RAN sharing phase2, the dedicated Iub transmission control is introduced, which refers to the separated Iub transmission resource management for the operators sharing the RAN. With this feature, the operators differentiated QoS requirement is guaranteed. Other new features and enhancement

For details, please refer to the description and enhancement of the following chapters and Optional Function Description of Huawei UMTS RAN6.1.EnhancementNone.DependencyNone.1.4 WRFD-000004 System Improvement for RAN10.0




New generation Node Bs based on the modular structure and multi-mode platform enhance the adaptability and the evolution capability. High output power amplifier for the macro Node B extends the coverage and capacity, saves the number of the sites, and provides better user experience.

Higher throughput by supporting the HSUPA Phase 2, that helps to get faster UL speedDescriptionCompatibility with the 3GPP Release 6 (2007-03)

New products and configurations supportedThe UMTS RAN10.0 supports the following new boards and configurations in existing products:

The enhanced base band interface (EBBI) card is used to support the HSUPA Phase2 and more CEs. It can be co-configured with all other boards in the macro Node Bs BTS3812E, BTS3812A, and BTS3812AE. The enhanced baseband optical interface (EBOI) card is used to support the RRU connection to the macro Node Bs: BTS3812E, BTS3812A, and BTS3812AE. EBOI also supports HSUPA phase2 and more CEs. It can be co-configured with all other boards in the macro Node B. The enhanced uplink process (EULP) card is used to support the HSUPA Phase2 and more CEs, used in the macro Node Bs: BTS3812, BTS3812A, BTS3812E, and BTS3812AE. The EULP can be co-configured with other boards in the macro Node B. The extension base band card (EBBC) is used to support the HSUPA Phase2 and more CEs in the BBU3806. The EBBC can support hot plugging. With the BBU+EBBC, six cells are supported.

The BTS3812E/AE supports the WCDMA Radio Frequency Unit (WRFU), a high compact RF module integrated with MTRU functions and MAFU functions. The WRFU supports 80W maximum output power and four carriers. With the WRFU, BTS3812E/AE can expand configuration to support 3 sectors * 6 carriers or 3 sectors * 8carries. The GTPu is re-arrayed for the unified interface board. The POUa board of the BSC6810 supports IP over channelized STM-1/OC-3 (CPOS)Based on the new hardware platform, the UMTS RAN10.0 introduces the new Node B product portfolio as follows:

Indoor baseband unit BBU3900. Indoor radio filter unit WRFU. The WRFU provides four carriers and 80-W nominal output power. Only Band 1 (2100 MHz) WRFU will be released in RAN10.0. Outdoor remote radio unit RRU3804. The RRU3804 provides four carriers and 60-W nominal output power. Band 1 (2100 MHz), Band II (1900 MHz), Band IV (1700 MHz / DL 2100 MHz), and Band V (850 MHz) RRU3804 will be released in RAN10.0 Different combinations of the units and auxiliary devices compose the following 3900 series Node Bs: DBS3900/BTS3900/BTS3900A can support up to 24 cell carriers. They support Omni directional, 2-sector, 3-sector, or 6-sector configuration. The maximum capacity of the 3900 series Node B is 1536 CEs in the uplink and 1536 CEs in the downlink.

New features and enhancement supported HSUPA Phase 2

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

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

2 ms / 10 ms TTI

Max users per cell : 60

UL compress mode (10 ms and 2 ms)

Enhanced fast UL scheduling

SRB over HSUPA, etc.

HSDPA Phase 4

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

F-DPCH

MBMS over HSDPA (PtP)

HS-DPCCH preamble mode

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

SRB over HSDPA, and so on HSPA over Iur

VoIP over HSPA (trial)

Enhanced MBMS broadcast

Robust header compression (RoHC) Multi band HO based on service priority and band

Active queue management (AQM) IP transmission enhancement

The following new interface ports are supported: IP over STM-1/OC-3c (POS)

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

Enhancement for the existing port:

Backup between IP over E1 and IP over FE

BFD and ARP checking, etc.

Other new features and enhancement

For details, please refer to the Description and Enhancement in the following chapters and the Optional Function Description of Huawei UMTS RAN10.0.EnhancementNone.DependencyNone.1.5 WRFD-000005 System Improvement for RAN11.0


This feature is based on 3GPP R7 with a series of newly introduced RAN products and functions, thus meeting the customers requirements in a wider range and improving product performance.Benefits

HSPA+ Phase 1 provides higher bandwidth and shorter delay: Provides higher throughput and improves the system capacity greatly. This enables the operator to make more profits. Provides a higher peak rate for users and a higher speed of data downloading for the UE.

Improves user experience and provides comprehensive functions for operators.

With the optimization of capacity and performance of VoIP over HSPA/HSPA+, this feature meets the commercial deployment requirement of VoIP and improves the competitiveness of operators. The high throughput of the RNC meets operators' requirements for constructing wideband radio networks based on HSPA and HSPA+. It can also effectively adapt to the fast development of data services.DescriptionRAN11.0 introduces HSPA+ to meet the increasing demand of subscribers for the bandwidth. HSPA+ provides higher bit rates and shorter delay. RAN11.0 supports HSPA+ Phase 1, e.g. 64QAM, 2 x 2MIMO, and CPC.

RAN11.0 optimizes the capacity and performance of VoIP over HSPA/HSPA+, and provides comprehensive functions for the commercial deployment of VoIP over HSPA/HSPA+. In compliance with the 3GPP R7 2008-03, RAN11.0 provides the following new features and enhancements:

HSPA+ Phase 1:

64QAM (downlink): provides a higher peak rate of 21 Mbit/s and increases the downlink capacity through high order modulation.

2 x 2MIMO: provides a higher peak rate of 28.8 Mbit/s and increases the downlink capacity through parallel downlink bit streams.

Enhanced layer 2: provides flexible RLC PDU size, as the basis for 64QAM, MIMO, and the enhanced CELL_FACH function.

CPC: reduces user access time, increases the air interface capacity, and lowers UE power consumption (prolongs the battery service life).

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

Commercial deployment of VoIP over HSPA/HSPA+: improves the capacity and performance of VoIP over HSPA/HSPA+, and fully meets the requirement for commercial deployment.

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

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

Newly added board: The BTS3812E/AE has a new downlink baseband processing unit, namely, EDLP. The EDLP provides a downlink processing capacity of six cells, 384 CEs, and DL 64QAM and MIMO of HSPA+.EnhancementNone.DependencyNone.1.6 WRFD-000006 System Improvement for RAN11.1 Availability

This feature is available from RAN 11.1.Summary

This feature is based on new boards in RNC, which meet the customers requirements in a wider range and improve product performance.Benefits

New boards are introduced in RAN11.1. With these new boards, the operators are benefited by the merits list below: The RNC capacity increases. The PS throughput doubles compared to that with legacy boards.

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

With new boards, the spare hardware number also saved.

Description

RAN11.1 introduces several boards, they are: SPUb board: charge in control plane service processing DPUe board: charge in user plane data processing AOUc: ATM interface board with 4 CSTM-1 exports

UOIc: ATM interface board with 8 STM-1 exports

POUc: IP interface board with 4 STM-1 exports

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

GOUc: IP interface board with 4 GE exportsWith the new boards, the RNC capacity increases.Enhancement

NoneDependency

None2 Standards Compliance2.1 WRFD-010101 3GPP R7 SpecificationsAvailabilityThis feature is available from RAN11.0.Summary

RAN11.0 complies with 3GPP R7 (2008-03). The functions, compatibility, and standardization of the system are improved.Benefits

In compliance with the 3GPP R7 protocol, RAN11.0 provides the basis for new features and enhanced functions, with which high-performance services and comprehensive functions are provided for subscribers.This feature also provides the following benefits:

Improves operator's competitiveness

Enables the interconnection with other Network Elements (NEs) that comply with the 3GPP R99, R4, R5, R6, or R7 protocol, thus protecting the operator's investmentDescriptionRAN2.0 complies with the 3GPP R99/R4.

RAN3.0/5.0 complies with the 3GPP R99/R4/R55.

RAN6.0/6.1 complies with the 3GPP R99/R4 /R5/R6 2006-03+CR.

RAN10.0 complies with the 3GPP R99/R4 /R5/R6 2007-03.

RAN11.0 complies with the 3GPP R99/R4 /R5/R6/R7 2008-03.EnhancementNone.DependencyDependency on other NEs

For the new features introduced in R7 and the enhancements of the standard interfaces, the standard interfaces and user interfaces at the CN should also be upgraded to ensure compliance with the protocols.2.2 WRFD-010102 Operating Multi-bandAvailabilityThis feature is available from RAN 2.0.Summary

This feature meets the requirement of the operators for use of different frequency bands in different regions. In addition, the Node B supports the co-cabinet of different frequency bands, thus saving the deployment cost for the operators and meeting the space requirement.Benefits

The Node Bs can be deployed widely according to the operators frequency requirement.

The multi-band supported Node B can save the cost of the hardware investment.DescriptionThe following 3GPP defined UMTS frequency bands are supported.Operating BandUL Frequencies

UE transmit, Node B receiveDL frequencies

UE receive, Node B transmit

Band I (2100M)19201980 MHz21102170MHz

Band III/IX (1800M)17101785 MHz18051880 MHz

Band II (1900M)18501910 MHz19301990MHz

Band V/VI (850M)824849MHz869894MHz

Band VIII (900M)880915 MHz925960 MHz

Band IV(1.7/2.1G)17101755 MHz21102155 MHz

The macro Node Bs provide multi-band co-located in one cabinet. Due to the flexible design of Huawei Node B architecture, the multi-band only has impact on the RF system. The baseband modules including power, transmission, and channel cards are shared by different bands. The operators can use the required frequency segments to save the footprint of the Node B and improve the baseband usageThe feature is implemented in the Node B and RNC.

Different frequency bands should be configured with different RF modules.EnhancementIn RAN5.0, the macro Node B supports the 1900M and 1800M frequency bands.

In RAN5.1, the RRU supports the 1900M and 1800M frequency bands.In RAN6.0, the 850M and 900M frequency bands are supported by the macro Node B and RRU.

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

The BTS3900/BTS3900A only supports Band1 2100M and 850M in RAN10.0.DependencyNone.2.3 WRFD-010201 FDD ModeAvailabilityThis feature is available from RAN2.0.Summary

Huawei RAN supports the FDD mode.Benefits

This feature defines the mode supported by Huawei RAN.DescriptionThe 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.EnhancementNone.DependencyDependency on other NEs

The relevant NEs should comply with the 3GPP specifications in FDD mode. 3 RABs and Services3.1 WRFD-010510 3.4/6.8/13.6/27.2 kbit/s RRC Connection and RAB AssignmentAvailabilityThis feature is available from RAN2.0.Summary

This feature supports the RRC connection/release of different rates and RAB assignment to meet the QoS requirements for different services.Benefits

This is an essential feature for the UMTS RAN.DescriptionRAN11.0 supports the 3.4/6.8/13.6/27.2 kbit/s RRC connection and Radio Access Bearer (RAB) assignment. The RNC will map the RRC connection request and the RAB assigned by the CN according to different QoS requirements. Mapping of channel typesFor RRC connection, the operators can decide which channel type (CCH/DCH) should be configured according to the RRC SETUP REQUEST message.

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

Mapping of RAB parametersThe associated transport channel and physical channel parameters are configured based on the channel types. Huawei RAN provides different sets of configuration parameters for typical services. These parameters are supported by each typical service. If no service class matches the feature, choose the most approximate parameters. Moreover, the operators can add new service classes and configure associated parameters. These features can fully utilize the services supported by the system.The PS streaming/interactive/background RAB can also be set up on the HS-DSCH or E-DCH. These features include the following optional features:

WRFD-010610 HSDPA Introduction Package WRFD-010612 HSUPA Introduction Package WRFD-010630 Streaming Traffic Class on HSDPA WRFD-010632 Streaming Traffic Class on HSUPASRB always occupies SF 256 at the rate of 3.4 kbit/s or 6.8 kbit/s. It can increase the signaling transmission speed and shorten the delay at the rate of 6.8 kbit/s. Therefore, if all the downlink services of the UE are set up on the HS-DSCH and the SRB is carried on the DCH in the downlink, the SRB has a rate of 6.8 kbit/s.EnhancementRAN3.0 supports RRC connection of 13.6 kbit/s.RAN6.1 supports RRC connection of 27.2 kbit/s.RAN11.0 supports RRC connection of 6.8 kbit/s and the retainment of SRB of 6.8 kbit/s.DependencyNone.3.2 WRFD-010501 Conversational QoS ClassAvailabilityThis feature is available from RAN2.0.

It is introduced in 3GPP R99.Summary

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

The QoS-supported conversational services provide guaranteed QoS for upper-layer services.DescriptionQoS classes also refer to traffic classes. The following four QoS classes are defined in 3GPP:

Conversational class Streaming class Interactive class Background classThe main difference between the preceding QoS classes lies in the extent to which the traffic is delay sensitive. Conversational class is meant for traffic which is very delay sensitive and is mainly used to carry real time traffic flows. Fundamental characteristics for real time conversational QoS class include the following: Preserved time relations (variation) between information entities of the stream. Conversational pattern (stringent and low delay).There are conversational class services in both CS and PS domains. The most well known conversational traffic is speech and video phone services in CS domain and VoIP in PS domain.Huawei RAN supports the following conversational services as fundamental features: CS AMR speech services of 8 rates, including 12.2 kbit/s, 10.2 kbit/s, 7.95 kbit/s, 7.4 kbit/s, 6.7 kbit/s, 5.9 kbit/s, 5.15 kbit/s, and 4.75 kbit/s. The RNC selects SF256 for AMRS services whose maximum rate is lower than 7.95 kbit/s. CS transparent data services (conversational class) with 64 kbit/s, 56 kbit/s, 32 kbit/s, and 28.8 kbit/s. PS bidirectional symmetric speech services at the rates of 64 kbit/s, 42.8 kbit/s, 32 kbit/s, 16 kbit/s, and 8 kbit/s.EnhancementNone.DependencyDependency on other NEs

Both CN and UE should support this service.3.3 WRFD-010502 Streaming QoS ClassAvailabilityThis feature is available from RAN2.0.

It is introduced in 3GPP R99.Summary

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

The QoS-supported steaming services provide guaranteed QoS for upper-layer services.DescriptionQoS classes also refer to traffic classes. The following four QoS classes are defined in 3GPP:

Conversational class Streaming class Interactive class Background classThe main difference between the preceding QoS classes lies in the extent to which the traffic is delay sensitive. Streaming class is new to data communication, thus it raises a number of new requirements in both telecommunication and data communication systems. Streaming class is characterized by the time relations (variation) between information entities (i.e. samples, packets) of the stream that should be preserved, although it does not have strict requirements on transfer delay. Fundamental characteristics of streaming QoS class include the following: Preserved time relations (variation) between information entities of the stream: There are streaming class services in both CS and PS domain. The most well known streaming traffic is FAX in CS domain and streaming video in PS domain.

Huawei RAN supports the following streaming services as fundamental features: CS transparent data services (streaming class) of 64 kbit/s. CS nontransparent data services of 57.6 kbit/s, 28.8 kbit/s, and 14.4 kbit/s. PS bidirectional symmetric or asymmetric streaming services at the rates of 384 kbit/s, 256 kbit/s, 144 kbit/s, 128 kbit/s, 64 kbit/s, 32 kbit/s, and 8 kbit/s. PS unidirectional asymmetric streaming services at the rates of 384 kbit/s, 256 kbit/s, 144 kbit/s, 128 kbit/s, 64 kbit/s, 32 kbit/s, 8 kbit/s, and 0 kbit/s.PS streaming service can also be carried on HSDPA and HSUPA which are optional features and described in WRFD-010610 HSDPA Service and WRFD-010612 HSUPA Service.EnhancementRAN6.0 supports PS 384 kbit/s bidirectional symmetric or asymmetric streaming service. DependencyDependency on other NEs

Both CN and UE should support this service.3.4 WRFD-010503 Interactive QoS ClassAvailabilityThis feature is available from RAN2.0.It is introduced in 3GPP R99.Summary

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

The QoS-supported interactive services provide guaranteed QoS for upper-layer services.DescriptionQoS classes also refer to traffic classes. The following four QoS classes are defined in 3GPP:

Conversational class Streaming class Interactive class Background classThe main difference between the preceding QoS classes lies in the extent to which the traffic is delay sensitive. Interactive class is another typical data communication scheme that is characterized by the request response pattern of the end-user. At the message destination, there is an entity expecting the message (response) within a certain time. Round trip delay time is therefore one of the key attributes. Another characteristic is that the contents of the packets are transparently transferred (with low bit error rate). Fundamental characteristics of Interactive QoS class include the following:

Request response pattern.

Preserve payload content.Interactive class services apply only to the PS domain. The most well known interactive traffic is web browsing.

Huawei RAN supports the following interactive services as fundamental features:PS bidirectional symmetric or asymmetric interactive services at the rates of 384 kbit/s, 256 kbit/s, 144 kbit/s, 128 kbit/s, 64 kbit/s, 32 kbit/s, 16 kbit/s, and 8 kbit/s.The higher rates can only be supported on HSDPA and HSUPA which are optional features and described in WRFD-010610 HSDPA Service and WRFD-010612 HSUPA Service.EnhancementRAN3.0 supports UL PS service of 384 kbit/s.DependencyDependency on other NEs

Both CN and UE should support this service.3.5 WRFD-010504 Background QoS ClassAvailabilityThis feature is available from RAN2.0.It is introduced in 3GPP R99.Summary

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

The QoS-supported background services provide guaranteed QoS for upper-layer services.DescriptionQoS classes also refer to traffic classes. The following four QoS classes are defined in 3GPP:

Conversational class Streaming class Interactive class Background classThe main difference between the preceding QoS classes lies in the extent to which the traffic is delay sensitive. Background class is one of the typical data communication schemes. It is characterized by the fact that the destination does not expect the data within a certain time. The scheme is thus more or less insensitive to the delivery time. Another characteristic is that the contents of the packets are transparently transferred (with low bit error rate). Fundamental characteristics of background QoS class include the following: The destination does not expect the data within a certain time. The payload content is preserved.Background class services apply only to the PS domain. The most well known background traffic is background download or E-mails.

Huawei RAN supports the following background services as fundamental features:PS bidirectional symmetric or asymmetric background services at the rates of 384 kbit/s, 256 kbit/s, 144 kbit/s, 128 kbit/s, 64 kbit/s, 32 kbit/s, 16 kbit/s, and 8 kbit/s.The higher rates can only be supported on HSDPA and HSUPA which are optional features and described in WRFD-010610 HSDPA Service and WRFD-010612 HSUPA Service.EnhancementRAN3.0 supports UL PS service of 384 kbit/s.DependencyDependency on other NEs

Both CN and UE should support this service.3.6 WRFD-010609 Multiple RAB Introduction Package (PS RAB < 2)AvailabilityThis feature is available from RAN2.0.It is introduced in 3GPP R99.Summary

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

Multi-RAB support capability provides operators with more service solution choices.DescriptionMulti-RAB can provide more abundant services simultaneously to the upper layer. In the case of multi-RAB that has less than two PS RABs, Huawei supports the following specifications: Combination of two CS services (except for two AMR speech services)

One CS service + one PS service

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

In all the preceding combinations, the bit rates of CS and PS services are not limited. That is, any bit rates of CS and PS services defined in WRFD-010501 Conversational QoS Class, WRFD-010502 Streaming QoS Class, WRFD-010503 Interactive QoS Class, and WRFD-010501 Background QoS Class can be selected in the combination.

The PS conversational/streaming/interactive/background services can also be mapped to HS-DSCH or E-DCH. These features need the support of the optional features WRFD-010610 HSDPA Introduction Package and WRFD-010612 HSUPA Introduction Package.Enhancement

None.DependencyDependency on other NEs

Both CN and UE should support the specifications for multiple RABs.3.6.2 WRFD-01060901 Combination of Two CS Services (Except for Two AMR Speech Services)AvailabilityThis feature is available from RAN2.0.Summary

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

Multi-RAB support capability provides operators with more service solution choices.DescriptionHuawei supports combination of two CS services (except for two AMR speech services).EnhancementNone.DependencyDependency on other NEs

Both CN and UE should support the specifications for multiple RABs.3.6.3 WRFD-01060902 Combination of One CS Service and One PS ServiceAvailabilityThis feature is available from RAN2.0.Summary

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

Multi-RAB support capability provides operators with more service solution choices.DescriptionHuawei RAN supports the combination of one CS service and one PS service.EnhancementNone.DependencyDependency on other NEs

Both CN and UE should support the specifications for multiple RABs.3.6.4 WRFD-01060903 Combination of Two CS Services and One PS Service (Except for Two AMR Speech Services)AvailabilityThis feature is available from RAN2.0.Summary

Huawei RAN supports the combination of two CS services and one PS service (except for two AMR speech services).Benefits

Multi-RAB support capability provides operators with more service solution choices.DescriptionHuawei RAN supports the combination of two CS services and one PS service (except for two AMR speech services).EnhancementNone.DependencyDependency on other NEs

Both CN and UE should support the specifications for multiple RABs.3.7 WRFD-021104 Emergency CallAvailabilityThis feature is available from RAN2.0.It is introduced in 3GPP R99.Summary

This feature provides the emergency call a higher priority over common calls to ensure that the emergency call gets preference to access the network.Benefits

It is an essential feature for UMTS RAN. It enables the emergency call to have a higher priority over other services in resource allocation. DescriptionWhen an emergency call is triggered, Establishment Cause in the RRC Connection Request message is set to Emergency Call.

Emergency call always has priority over the ordinary calls. When enough resources are not present in the cell, pre-emptive action is triggered on ordinary calls with lowest priority to guarantee that the emergency call can access the network and be served.EnhancementNone.DependencyNone.4 RAN Architecture & Functions4.1 MRFD-210604 2-Way Antenna Receive Diversity

Availability

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

Summary

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

Benefits

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

Description

With this feature, the same signal is received by two antennas. Then the two ways of signals on the two antennas are combined after being processed. Thus, the signal attenuation is reduced.

This feature enhances the RX capability of uplink channels. Huawei MBTS supports both receive diversity and none receive diversity.

With this feature, the MBTS does not require additional devices and algorithms. Compared with one-way none receive diversity, this feature requires twice the number of RX channels. In typical scenarios, the receiver sensitivity can be improved by 2 to 3 dB.

Enhancement

None.

Dependency

Impacts on the hardware of the MBSC

None.

Impacts on the hardware of the MBTS

In receive diversity mode, the Node B should provide sufficient RF channels and demodulation resources to meet the requirements for the number of antenna diversities.Dependency on other features of the GBSS/RAN

None.Dependency on other NEs

None.4.2 WRFD-010205 Cell Digital Combination and SplitAvailabilityThis feature is available from RAN6.0.Summary

This feature enables multiple sectors to use the resources in the same cell, thus improving system spectrum efficiency and resource utilization. The DBS3800, DBS3900, iDBS3800, and iDBS3900 support this feature.

Benefits

Compared with the analog combination and split, the digital combination and split can provide larger capacity and wider coverage without bringing additional noises and signal losses. In this manner, cell distribution can be adjusted through software to adapt to actual traffic distribution and changes, thus improving CE resource utilization and operation benefits.

DescriptionCell split means that a cell in the Node B is split into multiple sectors through the digital combination and split and the sectors can cover multiple areas. Cell split applies to scenarios such as indoor coverage and high-speed railway or expressway coverage. Based on cell split, the antennas in different sectors can transmit and receive signals from the same cell. When expanding the capacity or adjusting the network, you can flexibly configure the mapping between the RRU and cell through software without changing the hardware. The DBS3800, DBS3900, iDBS3800, and iDBS3900 support cell split and digital combination and split.

The following figure shows the logical structure of the digital combination and split. The downlink digital split means that a downlink signal is split into two signals, that is, the downlink signal from the upper-level RRU or baseband unit is simultaneously sent to the RF Tx path of the RRU and the lower-level RRU. The uplink digital combination means that two uplink signals are combined into one signal, that is, the uplink signals from the RF Tx path of the RRU and the lower-level RRU are combined and then sent to the upper-level RRU or baseband unit.

Each RRU or pRRU has an independent antenna that covers different sectors. One cell can be set for multiple RRUs so that they have the same scrambling code.

This feature is introduced to Huawei pRRU and RRU, and it can be applied to scenarios such as indoor coverage and along high-speed railway or expressway coverage.EnhancementNone.DependencyNone.4.3 WRFD-010208 Fast Power Congestion Control (FCC)AvailabilityThis feature is available from RAN5.0.Summary

Fast power congestion control (FCC) is implemented on the Node B side. This feature aims to quickly rectify system overload to prevent the output power from exceeding the maximum power allowed by hardware.

Benefits

This feature enables full utilization of Power Amplifiers for traffic load, especially for dynamic power sharing in one carrier between R99 and HSDPA.DescriptionFCC is a Node B function that complements the RNC congestion control. The function supervises the output power per slot that users (all users) demand at the same time, using the same time scale as the fast power control function. Huawei provides the DL automatic level control (ALC) function as the method of fast power congestion control in the Node B, in order to limit the output power and avoid the PA saturation. The ALC supervises the transmit power in real time. When the input power reaches or exceeds the predefined threshold, the ALC can increase the TX channel attenuated signals to keep the output power lower than the threshold, thus avoiding the PA saturation. The Node B uses the FCC to quickly control the output power, the control Reaction time is 1024chip, which is fast enough to fully prevent saturation of the TX chain or overdriving of the power amplifier without the need for power margins.Therefore, cell behavior remains robust at maximum load without running the risk of dropped cells or modulation inaccuracy. In addition, the RNC congestion and admission thresholds can be set to higher levels, which increase cell capacity without compromising overall quality of service.EnhancementNone.DependencyDependency on Node B hardwareOnly DBS3800/DBS3900 and iDBS3800/iDBS3900 support this feature.4.4 WRFD-010211 Active TX Chain Gain CalibrationAvailabilityThis feature is available from RAN5.0.Summary

This feature enables the monitoring and adjustment of digital channel gains, thus ensuring stable output power.

Benefits

This feature provides high output power accuracy for the Node B, and reduces the margins required in network dimensioning. Thus, the entire power can be used for traffic.DescriptionThe active TX chain gain calibration can increase the accuracy of the downlink transmit power (for example, the power accuracy of the 3900 series Node B is +/- 0.6 dB), thus reducing the protection band reserved for power calculation in network planning and improving the utilization of transmit power.

Performance drift occurs on all RF hardware. An RF part (for example, TRX, PA, RF connector, or duplexer) has a different gain due to different temperatures, frequencies, and lot numbers. Such a gain difference leads to a 1.5 dB to 2 dB error in the Node B transmit power.

The active TX chain gain calibration can reduce the changes in analog channel gains caused by different temperatures, frequencies, and lot numbers, thus ensuring a stable total gain of links. The active TX chain gain calibration calculates the difference between the downlink input power and transmit power and then adjusts digital channel gains according to the transmit power on the analog channel. Gain control is performed in real time, thus ensuring the accuracy of transmit power.EnhancementNone.DependencyNone.4.5 WRFD-010202 UE State in Connected Mode (CELL-DCH, CELL-PCH, URA-PCH, CELL-FACH)AvailabilityThis feature is available from RAN2.0.Summary

Huawei RAN supports four UE states in connected mode: URA_PCH, CELL_PCH, CELL_FACH, and CELL_DCH. This feature enables radio resources to be saved effectively.Benefits

This feature makes it possible to put UE in the proper state according to the QoS requirements. Thus, it improves the resources usage efficiency and increases the system capacity without degrading user experience. It is an essential feature of UMTS RAN system.DescriptionIn 3GPP, there are four RRC connected states for UE including URA_PCH, CELL_PCH, CELL_FACH, and CELL_DCH. Huawei RAN supports all these four states.URA_PCH/CELL_PCH: In these states, there is no DCCH or DTCH available for the UE. When UE originates a call or receives paging from CN, CELL_UPDATE procedure is triggered. Periodically URA UPDATE or CELL_UPDATE procedure can also be used to maintain the connection with the network. No DTCH or DCCH is allocated Hence, UE in these states do not occupy any radio resources, and no service is available.CELL_FACH: In this state, UE has DCCH and DTCH mapping to the common channels which are used to bear RRC signaling and traffic data. UE also performs cell reselection to camp on a proper cell through the Cell Update procedure. Since the common resources can be shared among different UEs, the traffic QoS such as transfer delay, bandwidth, and so on cannot be guaranteed.CELL_DCH: In this state, UE has DCCH and DTCH mapping to the dedicated channels which are used to bear RRC signaling and traffic data. The dedicated resources are allocated. Hence, the traffic QoS is guaranteed when the cell load is increased accordingly. When UE uses HSDPA and/or HSUPA, it also belongs to CELL_DCH state.The preceding four states can be transformed according to the UE service characteristics and behaviors, such procedures are called channel type transition. For details, please refer to the feature WRFD-021101 Dynamic Channel Configuration Function (DCCC).For the channel transition between CELL_DCH (HS-DSCH) and other states, please refer to the optional feature WRFD-01061111 HSDPA State Transition.EnhancementIn RAN2.0, the basic four states and transition algorithms are implemented.

In RAN5.0, with the deployment of HSDPA feature, UE in CELL_DCH (HS-DSCH) state is also supported.In RAN 6.0 with the deployment of HSUPA feature, UE in CELL_DCH (E-DCH) state is also supported.DependencyDependency on other NEs

The UE must support related states.

4.6 WRFD-010401 System Information BroadcastingAvailabilityThis feature is available from RAN2.0.Summary

This feature supports system information as stipulated in multiple protocols. Based on the system information, the network can provide UEs with rich access layer and non access layer information required for running UEs on the network, and the information that controls UE behavior.BenefitsThis feature provides UEs with rich access layer and non access layer information required for running UEs on the network, and the information that controls UE behavior.

DescriptionSystem information broadcasting which is required by the UE for its operation in the network provides UE with the Access Stratum and Non Access Stratum information.

The system information is organized in a tree-type manner. A master information block gives references and scheduling information to a number of system information blocks in a cell. The system information blocks contain the actual system information.Scheduling of system information blocks is performed by the RRC layer in UTRAN. RRC can automatically calculate the repetition period and position of each SIB segment based on its importance.The key information of each SIB Huawei supported is listed in the following table.System Information BlockArea ScopeContent

Master information blockCellSIB scheduling information

Scheduling block 1CellSIB scheduling information

Scheduling block 2CellSIB scheduling information

SIB1PLMNNAS information and timers used by UE in connected mode and idle mode

SIB2CellURA Id

SIB3CellParameters of cell selection and reselection in idle modeParameters of hierarchical cell in idle mode

SIB4CellParameters of cell selection and reselection in connected modeParameters of Hierarchical cell in connected mode (CCH state)

SIB5CellParameters of common physical channels for UE in idle mode(PRACH, AICH, PICH, S-CCPCH)

SIB6CellParameters of common physical channel in connected mode

SIB7CellUL interference, dynamical persistence level

SIB11CellMeasurement control information in idle mode

SIB12CellMeasurement control information in connected mode

SIB18CellPLMN ID of neighboring cells

EnhancementRAN5.0 supports SIB4, SIB6, and SIB12.

RAN10.0 supports SIB11 bis. SIB11 bis contains cell measurement control information, new intra-frequency cell information, new inter-frequency information, and new inter-RAT cell information.

DependencyNone.4.7 WRFD-010301 Paging UE in Idle, CELL_PCH, URA_PCH State (Type 1)AvailabilityThis feature is available from RAN2.0.Summary

This feature supports paging type 1. UTRAN sends a paging message to the UE in idle, CELL_PCH, or URA_PCH state through the paging control channel (PCCH).

BenefitsWhen an UE is in idle, CELL_PCH, or URA_PCH state, UTRAN sends a paging message to the UE through the PCCH.

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

Trigger UE establishing a RRC signaling connection. Trigger CELL UPDATE procedure of UE in CELL_PCH or URA_PCH state. Trigger reading of updated system broadcast of UE in idle mode, CELL_PCH or URA_PCH state. Trigger releasing signaling connection of UE in CELL_PCH or URA_PCH state.EnhancementNone.DependencyNone.

4.8 WRFD-010302 Paging UE in CELL_FACH, CELL_DCH State (Type 2)AvailabilityThis feature is available from RAN2.0.Summary

This feature supports paging type 2. The network can control the UE in CELL_FACH or CELL_DCH state through the dedicated control channel (DCCH).

BenefitsThe network can control the UE in CELL_FACH or CELL_DCH state which has DCCH with paging type 2 procedures.DescriptionIn paging type 2, UTRAN sends a paging message to the UE in CELL_FACH or CELL_DCH state through the DCH or FACH.

EnhancementNone.DependencyNone.5 Channel Resource Management5.1 WRFD-020900 Logical Channel ManagementAvailabilityThis feature is available from RAN2.0.Summary

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

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

CCCH can be mapped to RACH; DCCH can be mapped to RACH; DCCH can be mapped to DCH or E-DCH; DTCH can be mapped to RACH; DTCH can be mapped to DCH; DTCH can be mapped to E-DCH;II. In Downlink,

BCCH can be mapped to BCH; BCCH can be mapped to FACH; PCCH can be mapped to PCH; CCCH can be mapped to FACH; DCCH can be mapped to FACH; DCCH can be mapped to HS-DSCH; DCCH can be mapped to DCH; DTCH can be mapped to FACH; DTCH can be mapped to HS-DSCH; DTCH can be mapped to DCH; CTCH can be mapped to FACH; MTCH can be mapped to FACH;

MCCH can be mapped to FACH;The mapping between DTCH/DCCH and HS-DSCH/E-DCH belongs to the optional features WRFD-010610 HSDPA Introduction Package and WRFD-010612 HSUPA Introduction Package.EnhancementIn RAN3.0, the CTCH supporting the cell broadcast service (CBS) feature is introduced.In RAN6.0, the MTCH and MCCH are introduced.DependencyNone.

5.2 WRFD-021000 Transport Channel ManagementAvailabilityThis feature is available from RAN2.0.This feature is introduced in 3GPP R99/R5/R6.Summary

This feature enables Huawei RAN to support the common transport channel and dedicated transport channel as stipulated in 3GPP R6. This feature is a basic feature of RAN.

Benefits

This feature provides the basis for data transfer and resource management algorithm.DescriptionTransport channel is used to offer information transfer services to MAC and higher layers. It is generally classified into the following two groups: Common transport channels Dedicated transport channelsCommon transport channel types are as follows: Random Access Channel (RACH) Forward Access Channel (FACH) Broadcast Channel (BCH) Paging Channel (PCH) High Speed Downlink Shared Channel (HS-DSCH)Dedicated transport channel types are as follows: Dedicated Channel (DCH) Enhanced Dedicated Channel (E-DCH)EnhancementIn RAN5.0, HS-DSCH supported with HSDPA feature is introduced.In RAN6.0, E-DCH supported with HSUPA feature is introduced.DependencyDependency on Node B hardware

NDLP and NBBI do not support the Management of HSUPA or HSDPA transport channel.Dependency on other UTRAN software functions

To support the HSUPA transport channel Management, the optional feature WRFD-010612 HSUPA Introduction Package should be configured.To support the HSDPA transport channel Management, the optional feature WRFD-010610 HSDPA Introduction Package should be configured.5.3 WRFD-022000 Physical Channel ManagementAvailabilityThis feature is available from RAN2.0.This feature is introduced in 3GPP R99/R5/R6.Summary

This feature enables Huawei RAN to support the physical channel and the mapping between the transport channel and physical channel as stipulated in 3GPP R6. This feature is a basic feature of RAN.

Benefits

In compliance with the definition and requirements of the physical channel as stipulated in 3GPP specifications, this feature supports HSDPA and HSUPA services and enables the F-DPCH to support more VoIP subscribers.

DescriptionA physical channel may bear several transport channels and a transport channel may be borne by several physical channels.The Coded Composite Transport Channel (CCTrCH) is defined as the multiplexing of several transport channels that can be supported by one or several physical channels on the radio interface. Some physical channels are used only by the physical layer of the radio interface. Only the following physical channels may bear transport channels: P-CCPCH: Primary Common Control Physical Channel S-CCPCH: Secondary Common Control Physical Channel PRACH: Physical Random Access Channel DPDCH: Dedicated Physical Data Channel HS-PDSCH: High Speed Physical Downlink Shared Channel E-DPDCH: E-DCH Dedicated Physical Data Channel

The following 3GPP Standards define the main characteristics of the FDD Physical Channels:[1] TS25.211 Physical channels and mapping of transport channels onto physical channels (FDD)[2] TS25.212 Multiplexing and channel coding (FDD)[3] TS25.213 Spreading and modulation (FDD)[4] TS25.214 Physical layer procedures (FDD)The set of physical channels types supported by the Huawei Node B is described in the following tables. The characteristics of these supported physical channels are compliant with 3GPP TS25.211. Physical channels are carried on the radio interface only in the Node B of the UTRAN, but are managed by the RNC.ChannelAvailabilityDirectionCharacteristics

PRACHPhysical Random Access ChannelRAN2.0ULCommonPRACH is used to carry the RACH which carries random access information of the UE accessing the network. It consists of one or several preambles of length 4096 chips and a message of length 10 ms or 20 ms. The spreading factor may range from 256 to 32.

Uplink DPDCHUplink Dedicated Physical Data ChannelRAN2.0ULDedicatedThe uplink DPDCH is used to carry the DCH transport channel. There may be zero, one, or several uplink DPDCHs on each radio link.The spreading factor may range from 256 to 4.

Uplink DPCCHUplink Dedicated Physical Control ChannelRAN2.0ULDedicatedThe uplink DPCCH is used to carry control information generated at Layer 1. The Layer 1 control information consists of TFCI, TPC, Pilot bits, FBI, which is required to convey DPDCH. There is one and only one uplink DPCCH on each radio link.Generally, the spreading factor is equal to 256.

P-CCPCHPrimary Common Control Physical ChannelRAN2.0DLCommonThe Primary CCPCH is a fixed rate (30 kbps, SF=256) downlink physical channel used to carry the BCH transport channel which provides system and cell specific information.It is not transmitted during the first 256 chips of each timeslot because P-CCPCH is multiplexed with SCH.

S-CCPCHSecondary Common Control Physical ChannelRAN2.0DLCommonThe Secondary CCPCH is used to carry the FACH and PCH. The FACH and PCH can be mapped to the same or separate Secondary CCPCHs.The spreading factor range is from 256 to 4. It has no inner-loop power control and is not always transmitted.

P-SCHPrimary Synchronization ChannelRAN2.0DLCommonThe P-SCH is used for cell search procedure (Slot synchronization).This channel has no scrambles or OVSF codes. It is multiplexed with P-CCPCH.

S-SCHSecondary Synchronization ChannelRAN2.0DLCommonThe S-SCH is used for cell search procedure (SC group identification).Not scrambled nor OVSF coded. It is multiplexed with P-CCPCH.

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

PICHPage Indication ChannelRAN2.0DLCommonThe PICH is a fixed rate (SF=256) physical channel used to carry the paging indicators. The PICH is always associated with an S-CCPCH (mapped with PCH) to carry the Paging Indicators (PI) informing the UE that paging information is available on the SCCPCH.

AICHAcquisition Indicator ChannelRAN2.0DLCommonThe AICH is a fixed rate (SF=256) physical channel used to carry Acquisition Indicators (AI). Acquisition Indicators corresponding to signatures on the PRACH are used by the network to confirm to the UE the reception of its access (PRACH).

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

HS-DPCCHDedicated Physical Control Channel for HS-DSCH RAN5.0ULDedicatedThe HS-DPCCH carries uplink feedback signaling related to downlink HS-DSCH transmission. It consists of HARQ-ACK and CQI.

The spreading factor of the HS-DPCCH is 256

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

HS-PDSCHHigh Speed Physical Downlink Shared ChannelRAN5.0DLCommonThe HS- PDSCH is used to carry HS-DSCH.One HS-PDSCH corresponds to one channelization code with a fixed spreading factor of SF16. The HS-PDSCH supports multi-code transmission. This means that in one HS-PDSCH sub-frame, multiple channelization codes can be used for one UE. It also depends on the UEs capability.The HS-PDSCH adopts the QPSK or 16QAM modulation mode.

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

E-DPCCHE-DCH Dedicated Physical Control ChannelRAN6.0ULDedicatedThe 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-AGCHEDCH Absolute Grant ChannelRAN6.0DLCommonE-AGCH is a common downlink physical channel, which carries the maximum power ratio of E-DPDCH/DPCCH that can be used by the UE. It is only sent from the serving cell that the serving radio link of the UE belongs to. An E-AGCH is shared by many users in time dimension and the adjustment procedure is usually at slow speed.The spreading factor of E-AGCH is 256, and the fixed rate of E-AGCH is 30 kbit/s.

E-RGCHE-DCH Relative Grant ChannelRAN6.0DLDedicatedE-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 share the same channel code with spreading factor 128, and one channel code for E-RGCH and E-HICH can be spread again with 40 orthogonal signature sequences, which extends the usage of the downlink channel code.

E-HICHE-DCH Hybrid ARQ Indicator ChannelRAN6.0DLDedicatedE-HICH is a dedicated downlink physical channel, which carries the E-DCH hybrid ARQ acknowledgement indicator such as ACK/NACK; the acknowledgement indicator informs UE whether the data for a user process is received correctly or not in the Node B.

MICHRAN6.0DLCommonThe MBMS Indicator Channel (MICH) is a fixed rate (SF=256) physical channel used to carry the MBMS notification indicators. The MICH is always associated with an S-CCPCH to which a FACH transport channel is mapped.

F-DPCHRAN10.0/RAN11.0F-DPCH is a shared channel which only carries the UE specific TPC bits so that the A-DCH can be replaced by a shared channel to save the code and power resource.

Replacing A-DPCH with F-DPCH will boost the capacity for VoIP traffic in DL. RAN11.0 supports Rel-7 F-DPCH, so UE can receive the TPC bits in different F-DPCH channels in soft handover status, to maximize the user capacity in F-DPCH.

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

Enhancement

In RAN5.0, HSDPA is supported, and the following channels are added: HS-DPCCH, Dedicated Physical Control Channel for HS-DSCH

HS-SCCH, Shared Control Channel for HS-DSCH HS-PDSCH, High Speed Physical Downlink Shared ChannelIn RAN6.0, HSUPA is supported, and the following channels are added: E-DPDCH, E-DCH Dedicated Physical Data Channel E-DPCCH, E-DCH Dedicated Physical Control Channel E-AGCH, EDCH Absolute Grant Channel

E-RGCH, E-DCH Relative Grant Channel

E-HICH, E-DCH Hybrid ARQ Indicator Channel MICH, MBMS Indicator ChannelIn RAN10.0, the F-DPCH is added.DependencyDependency on Node B hardware

NDLP and NBBI do not support the HSUPA or HSDPA physical channel. To support the F-DPCH, the macro Node B (BTS3812E or BTS3812AE) should be configured with the EBBI or EBOI and the distributed Node B (BBU3806) should be configured with the EBBC.Dependency on other UTRAN software functions

To support HSUPA physical channel, the optional feature WRFD-010612 HSUPA Introduction Package should be configured.To support HSDPA physical channel, the optional feature WRFD-010610 HSDPA Introduction Package should be configured.5.4 WRFD-021101 Dynamic Channel Configuration Control (DCCC)AvailabilityThis feature is available from RAN2.0.Summary

This feature provides dynamic rate re-allocation and UE state transition that can be triggered by multiple sources, thus ensuring QoS and improving resource utilization.

Benefits

This feature can improve the efficiency of radio resource allocation and maintain the stability of radio link.DescriptionDynamic channel configuration control (DCCC) consists of rate re-allocation and UE state transition function: Rate Re-allocationWhen UE is in the CELL_DCH RRC state, rate re-allocation can adjust the bandwidth allocated for the best effort (BE) services (interactive and background services), in both uplink and downlink respectively.I. Traffic volume basedAccording to the traffic volume measurement report received from UE, rate re-allocation can increase or decrease the uplink data rate to a proper value to match the allocated resource to uplink.According to the traffic volume measurement report received from the RNC itself, rate re-allocation can increase or decrease the downlink data rate to a proper value to match the allocated resource to downlink.II. Coverage basedAccording to the downlink quality, including downlink transmit power and RLC status, rate re-allocation can decrease the downlink data rate, to reduce the negative impact concerned with coverage.According to the uplink quality, including UE Tx power, the RNC can adjust the UL rate during the call by means of UL bit rate switching to adapt to UE power limitations. III. Load basedRate re-allocation can be triggered by load control. The load can be power load and code resource. The congestion thresholds are independent and configurable. This feature is a strategy of WRFD-020106 Load Reshuffling. UE State TransitionUE state transition is supported between the CELL_DCH, CELL_FACH, and CELL_PCH/URA_PCH state according to both uplink and downlink traffic volume measurement. It can also be used to improve the efficiency of resource allocation between dedicated and common channels.DCCC is also applied to HSDPA/HSUPA (rate re-allocation is not applied to HSDPA because the data scheduler locates in the Node B). For details, please refer to optional features WRFD-01061111 HSDPA State Transition and WRFD-01061208 HSUPA DCCC.EnhancementIn RAN6.0, the code resource based DCCC is supported.In RAN10.0, the UL bit rate downsizing due to the UE power limitation is supported.In RAN10.0, the UL/DL bit rate downsizing based on DCH throughput is supported.DependencyNone.6 Network Security6.1 WRFD-011401 Integrity ProtectionAvailabilityThis feature is available from RAN2.0.It is introduced in 3GPP R99.Summary

This feature is concerned with integrity protection. The integrity protection mechanism can ensure the security of the network and user data and protect them from being monitored and modified illegally.

Benefits

This feature enhances network and user data security, and protects the data and networks from being intercepted and modified illegally.DescriptionThe Integrity protection handles the control of integrity protection of signaling data and the co-ordination of integrity keys between different core networks (PS and CS). It enables receiving entity (the UE or the RNC) to verify if the signaling data is changed illegally. It encrypts and decrypts the signaling data using a certain integrity algorithm with an integrity key (IK).Huawei RAN supports integrity algorithm UIA1.EnhancementNone.DependencyNone.6.2 WRFD-011402 EncryptionAvailabilityThis feature is available from RAN2.0.Summary

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

Benefits

This feature enhances network and user data security, and protects the data and networks from being intercepted and modified illegally.DescriptionThe Encryption function handles the control of ciphering of data and signaling data and the coordination encryption keys between different core networks (PS and CS). It encrypts and decrypts data and signaling using a certain encryption algorithm with a cipher key (CK).Huawei RAN supports encryption algorithm UEA0 and UEA1.EnhancementNone.DependencyNone.7 Power Control7.1 WRFD-020501 Open Loop Power ControlAvailabilityThis feature is available from RAN2.0.It is introduced in 3GPP R99.Summary

This feature is concerned with open loop power control as defined in 3GPP specifications. Open loop power control roughly estimates the path loss through power measurements, network parameter settings, and QoS requirements and then provides a proper initial transmit power for the UE and Node B.

Benefits

The proper initial power setting can decrease the possibility of burst interference to the network and improve the performance of the inner power control.DescriptionOpen loop power control attempts to make a rough estimation of path loss by means of power measurements, network parameter setting, and QoS requirement, and to provide a proper initial power used by the UE and Node B.Open loop power control is applied on the uplink PRACH and DPCH and the downlink DPCH. The other downlink common channels initial power is set by the network.In the case of the PRACH, the UE calculates the initial transmit power of PRACH preamble by estimating the downlink path loss and using the uplink inference within the cell broadcast information. In the case of the uplink DPCCH transmission, the initial power is calculated in the same manner as PRACH, except that the power offset is different and is provided by RRC message. In addition, uplink DPDCH transmit power can be calculated with the gain factors signaled by the network.

In the case of the downlink DPCH, the DPDCH transmit power is firstly estimated according to the RAB QoS assigned and the network configured parameters, the transmit power of each DPCCH part TFCI, TPC and pilot can be calculated by the network controlled power offset (PO1/PO2/PO3) setting.Open power control is used in the following scenarios which require an initial power on the newly added radio link. RRC connection setup Radio link addition in soft handover Hard handover Relocation Channel type switchingEnhancementNone.DependencyNone.7.2 WRFD-020502 Downlink Power BalanceAvailabilityThis feature is available from RAN2.0.It is introduced in 3GPP R99.Summary

This feature is related to downlink power balance as defined in 3GPP specifications. Downlink power balance can solve the problem of downlink power drift caused by TPC bit errors and link power imbalance in soft handover state to obtain the optimal gain of soft handover.Benefits

Downlink power balance can decrease the transmit power drifting of different RLs and improve soft handover performance accordingly.DescriptionDuring soft handover, the UL TPC command is demodulated in each RLS and due to demodulation errors, the difference between the initial transmit power of newly added RL and existing RL may lead to the drifting of transmit power. The more DL transmit power drifting, the less the macro-diversity gain.

Downlink power balance is used to correct the transmit power drifting in such scenarios and improve soft handover performance accordingly.In the downlink, the Node B calculates the transmit power after considering TPC commands sent by UE and the reference power set by the network. When the drifting of transmit power is too much, the network updates the reference power to decrease the power difference of different RLs.EnhancementNone.DependencyNone.7.3 WRFD-020503 Outer Loop Power ControlAvailabilityThis feature is available from RAN2.0.It is introduced in 3GPP R99.Summary

This feature is related to outer loop power control as defined in 3GPP specifications. Outer loop power control is used to maintain the communication quality to the level required by the service bearer through adjustment of the SIR target of the inner loop power control.

Benefits

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

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

Benefits

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

Downlink inner loop control involves the following two modes:

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

DPC1 mode: In DPC1 mode, the UE sends TPC commands for three timeslots. The operator can decide which DPC mode is used by RRC signaling.

EnhancementNone.DependencyNone.8 Cell Management8.1 WRFD-020101 Admission ControlAvailabilityThis feature is available from RAN2.0.Summary

This feature can combine multiple resources to perform admission control over R99 service requests, thus ensuring QoS and system resource allocation.

Benefits

This feature maximizes system capacity while ensuring QoS requirements and improves network stability.

DescriptionAdmission control is used to improve the resource usage efficiency and RRC/RAB setup success rate. The following four types of resources are admitted: Cell available code resource

Cell available power resource

Node B resource state, that is, Node B credits

Available Iub transport layer resource, that is, Iub transmission bandwidthOnly when all of these resources are available can a call be admitted and the admission procedure applies to the uplink and downlink separately.Note: This part of admission control is only applied to R99 services

I. Code Resource

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

The following three algorithms are available for power resource:

Algorithm 1Power resource admission decision based on power or interference

The RNC decides whether the cell load exceeds the threshold or not when admitting a new call based on the current cell load (uplink load factor and downlink TCP) and the access request. If the cell load exceeds the threshold, the RNC rejects the request. If the cell load does not exceed the threshold, the RNC accepts the request. Algorithm 2Power resource admission decision based on the equivalent number of users.

The RNC decides whether the equivalent number of users exceeds the threshold or not when admitting a new call based on the current equivalent number of users and the access request. If the equivalent number of users exceeds the threshold, the RNC rejects the request. If the equivalent number of users does not exceed the threshold, the RNC accepts the request.

Algorithm 3It is similar to algorithm 1, but the predicted required power of a new call is set to zero.Four basic load thresholds are used to decide the admission. They are as follows:

Handover admission threshold AMR conversational service admission threshold

Non AMR conversational service admission threshold

Other service admission threshold

With the preceding thresholds, the RNC can define the proportion between speech service and other services with the handover preference guaranteed.III. Node B credit

The Node B credit admission includes the following:

Local cell level admission decision

Local cell group level admission decision (if any)

Node B level admission decision

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

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

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

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

If the UL capacity credit and DL capacity credit are not separate, only the maintenance on the global capacity credit is performed for the local cell (and local cell group, if any).IV. Iub transport layer resource

Different services have different QoS requirements. Therefore, differentiated transmission must be applied according to the service QoS requirements. The mapping relation between service and transport resources can be configured.The principles of Iub bandwidth admission control are described as follows:

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

Admission control on the path level

Admission control on the port level

II. Traffic congestion and bearer congestion are considered. For admission, the only factor that needs to be considered is the Iub resources corresponding to the traffic class.III. The primary path takes priority over the secondary path during admission. The secondary path is tried when the admission attempt for the primary path fails.The admission control also applies to HSDPA/HSUPA. Please refer to optional features WRFD-01061003 HSDPA Admission Control and WRFD-01061202 HSUPA Admission Control.

In the admission control procedure, some other features can be used to improve the access success rate. That is, the feature Rate Negotiation at Admission Control (WRFD-010507) can be used to decide the proper resource request based on the cell load. When the admission fails, Queuing and Pre-Emption (WRFD-010505), DRD Introduction Package (WRFD-020400) can be used to maximize the possibility of access to the system.

Enhancement

In RAN5.0, AMR and Non-AMR threshold for power load admission is divided.In RAN6.0, algorithm 3 for power load admission is introduced.In RAN6.0, resource reserved for handover is supported to decrease the call failure due to the admission failure during the handover. In RAN10.0, The PS service is admitted by judging the resource for GBR while in the previous version the MBR is employed. By this means, the cell resources are better utilized.DependencyNone.8.2 WRFD-020102 Load MeasurementAvailabilityThis feature is available from RAN2.0.This feature is introduced in 3GPP R99.Summary

This feature is related to load measurement for load control.

Benefits

Load measurement is the base of the related load control features including admission control, load reshuffling, overload control, and potential user control features. On the other hand, operators can also control these strategies by configuring load measurement parameters like measurement period, hysteresis, and so on.DescriptionAlgorithms such as OLC and CAC use load measurement values in the uplink and the downlink. A common load measurement (LDM) algorithm is required to control load measurement in the uplink and downlink, which makes the algorithm relatively independent.

The LDM algorithm has the following functions:

Triggering LDR and OLC algorithms

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

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

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

Uplink RTWP (Received Total Wideband Power)

Downlink TCP (Transmit Carrier Power)

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

Provided bit rate (PBR) on HS-DSCH

Power requirement f

basic feature description of huawei umts ran11.1 v1.1(20090910)

Documents