RAN13.0 Network Impact Report 06(PDF)-En

RAN13.0

Network Impact Report

Issue

06

Date

2012-11-30

HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2012. 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 contract made between Huawei and the customer. All or part of the products, services and features described in this document may not be within the purchase scope or the usage scope. Unless otherwise specified in 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 a 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]

Issue 06 (2012-11-30)

Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd

i

RAN13.0 Network Impact Report

Contents

Contents 1 Introduction.................................................................................................................................... 1 1.1 Purpose ............................................................................................................................................................. 1 1.2 Intended Audience ............................................................................................................................................ 2 1.3 Change History................................................................................................................................................. 2

2 Overview......................................................................................................................................... 4 2.1 Capacity and Performance ............................................................................................................................... 4 2.2 Hardware .......................................................................................................................................................... 5 2.3 Implementation ................................................................................................................................................ 6 2.4 Inter-NE Interface ............................................................................................................................................ 7 2.5 Operation and Maintenance ............................................................................................................................. 7

3 Summary of Feature Impacts ...................................................................................................... 8 3.1 New and Enhanced RAN13.0 Features ............................................................................................................ 8 3.2 Dependency on Other Features ...................................................................................................................... 11 3.3 Dependency on NEs ....................................................................................................................................... 14

4 Impacts of RAN13.0 Features on RAN12.0 ............................................................................. 28 4.1 WRFD-000008 System Improvement for RAN13.0 (New/Basic) ................................................................. 28 4.2 WRFD-010101 3GPP R9 Specifications (Enhanced/Basic)........................................................................... 29 4.3 MRFD-210303 Inventory Management (Enhanced/Basic) ............................................................................ 29 4.4 MRFD-210305 Security Management (Enhanced/Basic) .............................................................................. 30 4.5 MRFD-210801 Interface Tracing (Enhanced/Basic) ...................................................................................... 31 4.6 MRFD-210401 RNC Software Management (Enhanced/Basic) .................................................................... 32 4.7 MRFD-210310 NodeB Software USB Download (Enhanced/Basic) ............................................................ 32 4.8 WRFD-020406 Intelligent Power Measurement (New/Basic) ....................................................................... 33 4.9 WRFD-010699 DC-HSDPA+MIMO (Trial) (New/Optional) ........................................................................ 34 4.10 WRFD-010703 HSPA+ Downlink 84Mbit/s per User (Trial) (New/Optional) ............................................ 35 4.11 WRFD-01061002 HSDPA UE Category 1 to 28 (Enhanced/Optional) ........................................................ 36 4.12 WRFD-020138 HSUPA Coverage Enhancement at UE Power Limitation (New/Optional) ........................ 37 4.13 WRFD-010712 Adaptive Configuration of Traffic Channel Power Offset for HSUPA (New/Optional) ..... 38 4.14 WRFD-010701 Uplink Enhanced CELL_FACH (New/Optional) ............................................................... 39 4.15 WRFD-010702 Enhanced DRX (New/Optional) ......................................................................................... 42 4.16 WRFD-010704 Flexible HSPA+ Technology Selection (New/Optional) .................................................... 43

Issue 06 (2012-11-30)


ii


Contents

4.17 WRFD-020137 Dual-Threshold Scheduling with HSUPA Interference Cancellation (New/Optional) ....... 44 4.18 WRFD-020136 Anti-Interference Scheduling for HSUPA (New/Optional) ................................................. 45 4.19 WRFD-010697 E-DPCCH Boosting (New/Optional).................................................................................. 46 4.20 WRFD-010698 HSPA+ Uplink 11.5Mbit/s per User (New/Optional) ......................................................... 47 4.21 WRFD-010713 Traffic-Based Activation and Deactivation of the Supplementary Carrier In Multi-carrier (New/Optional) .................................................................................................................................................... 48 4.22 WRFD-020806 Differentiated Service Based on SPI Weight (Enhanced/Optional) .................................... 49 4.23 WRFD-020132 Web Page Access Acceleration (New/Optional) ................................................................. 51 4.24 WRFD-020133 P2P Downloading Rate Control during Busy Hour (New/Optional) .................................. 52 4.25 WRFD-020135 Intelligent Inter-Carrier UE Layered Management (New/Optional) ................................... 53 4.26 WRFD-020129 Service-Based PS Service Redirection from UMTS to LTE (Trial) (New/Optional) ......... 54 4.27 WRFD-020130 Videophone Service Restriction (New/Optional) ............................................................... 56 4.28 WRFD-020131 Optimization of R99 and HSUPA Users Fairness (New/Optional) ..................................... 57 4.29 WRFD-020122 Multi-Carrier Switch off Based on QoS (New/Optional) ................................................... 59 4.30 WRFD-020121 Intelligent Power Management (New/Optional) ................................................................. 60 4.31 WRFD-02131106 Routing Roaming UEs in Proportion (New/Optional) .................................................... 61 4.32 WRFD-050402 IP Transmission Introduction on Iub Interface (Enhanced/Optional) ................................. 63 4.33 WRFD-050409 IP Transmission Introduction on Iu Interface (Enhanced/Optional) ................................... 64 4.34 WRFD-050410 IP Transmission Introduction on Iur Interface (Enhanced/Optional) .................................. 64 4.35 WRFD-021350 Independent Demodulation of Signals from Multiple RRUs in One Cell (New/Optional) 64 4.36 WRFD-020134 Push to Talk (New/Optional) .............................................................................................. 66 4.37 WRFD-012001 RNC offload (Trial) (New/Optional) .................................................................................. 68 4.38 WRFD-030010 CQI Adjustment Based on Dynamic BLER Target (New/Optional)................................... 70 4.39 WRFD-030011 MIMO Prime (New/Optional) ............................................................................................ 71 4.40 MRFD-221802 GSM and UMTS Dynamic Spectrum Sharing(UMTS) (New/Optional) ............................ 73 4.41 MRFD-221703 2.0MHz Central Frequency point separation between GSM and UMTS mode(UMTS) (New/Optional) .................................................................................................................................................... 74

A Acronyms and Abbreviations .................................................................................................. 76

Issue 06 (2012-11-30)


iii


1 Introduction

1

Introduction

This document describes the impacts of new and enhanced RAN13.0 features on RAN12.0. Table 1-1 lists the products and versions involved in RAN13.0. Table 1-1 Products and versions involved in RAN13.0 Product

Version

M2000

iManager M2000-II V200R011

CME

iManager M2000-II V200R011

RNC

BSC6900 V900R013

NodeB



BTS3812E V100R013



BTS3812AE V100R013



DBS3800 V100R013



DBS3900 WCDMA V200R013



BTS3900 WCDMA V200R013



BTS3900A WCDMA V200R013



BTS3900L WCDMA V200R013



BTS3902E WCDMA V200R013

1.1 Purpose This document provides information for network planning personnel and operation and maintenance (OM) personnel to plan software upgrades to RAN13.0. This document is for reference only, and is subject to change during the development of this new release.

Issue 06 (2012-11-30)


1


1 Introduction

1.2 Intended Audience This document is intended for: 

Network planning engineers



System engineers



Network operators

1.3 Change History 06 (2012-11-30) This is the sixth commercial release for RAN13.0. Compared with issue 05 (2012-05-30), this issue incorporates the following changes: Delete the two dependency features WRFD-010652 SRB over HSDPA and WRFD-010636 SRB over HSUPA of WRFD-010701 in Table 3-2.

05 (2012-05-30) This is the fifth commercial release for RAN13.0. Compared with issue 04 (2011-12-30), this issue incorporates the following changes: 

WRFD-010701 Uplink Enhanced CELL_FACH: updates the dependency on the NodeB hardware, as described in Table 3-3.



WRFD-010703 HSPA+ Downlink 84Mbit/s per User (Trial): updates the dependency on the RNC hardware, as described in Table 3-3.



WRFD-020137 Dual-Threshold Scheduling with HSUPA Interference Cancellation: updates the dependency on the NodeB hardware, as described in Table 3-3.



WRFD-010699 DC-HSDPA+MIMO (Trial) (N/O): updates section 4.9.2 "Capacity and Performance."



WRFD-020131 Optimization of R99 and HSUPA Users Fairness: updates section 4.28.2 "Capacity and Performance."

04 (2011-12-30) This is the document for the fourth commercial release of RAN13.0. Compared with issue 03 (2011-10-30), this issue updates the description of hardware dependency for the following features: 

WRFD-020137 Dual-Threshold Scheduling with HSUPA Interference Cancellation



WRFD-050402 IP Transmission Introduction on Iub Interface



WRFD-050409 IP Transmission Introduction on Iu Interface



WRFD-050410 IP Transmission Introduction on Iur Interface

03 (2011-10-30) This is the document for the third commercial release of RAN13.0.

Issue 06 (2012-11-30)


2


1 Introduction

Compared with 02 (2011-06-30), this issue incorporates editorial changes.

02 (2011-06-30) This is the document for the second commercial release of RAN13.0. Compared with 01 (2011-04-30), this issue incorporates the following changes: 



Added the following features: −

WRFD-030010 CQI Adjustment Based on Dynamic BLER Target (New/Optional)

−

WRFD-030011 MIMO Prime (New/Optional)

Made editorial changes to descriptions

01 (2011-04-30) This is the document for the first commercial release of RAN13.0. Compared with Draft A (2011-03-30), this issue incorporates the following changes: 

Added a new NodeB hardware model: BTS3902E



Made editorial changes to descriptions

Draft A (2011-03-30) This is the initial draft for RAN13.0.

Issue 06 (2012-11-30)


3


2 Overview

2

Overview

2.1 Capacity and Performance 2.1.1 RNC BSC6900 is the RNC model for RAN13.0. Compared with RAN12.0 BSC6900, RAN13.0 BSC6900 provides improved capacity: 

Busy Hour Call Attempt (BHCA)



Traffic volume (Erlang)



PS throughput (UL+DL) (Mbit/s)

Table 2-1 describes the RAN13.0 BSC6900 capacity. For more information, see the RAN13.0 BSC6900 Product Description. Table 2-1 RAN13.0 BSC6900 capacity Item

Specification

BHCA (K)

3720 (using the balanced traffic model in Table 2-2)

Traffic volume (Erlang)

100,500

PS throughput (UL+DL) (Mbit/s)

24,000

The preceding specifications of the RAN13.0 BSC6900 are based on the condition that HW69 R13 hardware is configured. Note that traffic volume and PS throughput cannot reach the maximum at the same time. PS throughput is based on UL rate of 64 kbit/s and DL rate of 384 kbit/s.

Table 2-2 describes the balanced traffic model for the RAN13.0 BSC6900 UMTS.

Issue 06 (2012-11-30)


4


2 Overview

Table 2-2 Balanced traffic model for the BSC6900 UMTS (per user in busy hours) Parameter

Value

Description

CS voice traffic

20 mE

AMR speech service, 0.96 BHCA per user

CS data traffic

1.5 mE

UL: 64 kbit/s, DL: 64 kbit/s, CS data service, 0.04 BHCA per user

PS throughput

4500 bit/s

UL: 25 kbit/s, DL: 145 kbit/s, 2 BHCAs per user

Proportion of soft handovers

30%

Proportion of calls (in percentage) with two handover connections

Handover times per CS call

8

Average number of handovers per CS call

Handover times per PS call

5

Average number of handovers per PS call

NAS times

3.6

Including all signaling messages between the CN and the UE: LA update, IMSI attach/detach, RA update, GPRS attach/detach, SMS

2.1.2 NodeB Compared with RAN 12.0, 3900 series base stations of RAN 13.0 have improved in capacity specifications. DBS3900, BTS3900, BTS3900A, and BTS3900L of RAN 13.0 support a maximum of 2304 CEs, increased by 50% as compared with 1536 CEs supported by RAN12.0.

2.1.3 M2000 RAN13.0 M2000 can manage up to 50,000 UMTS cells, the same amount as RAN12.0 M2000.

2.2 Hardware 2.2.1 RNC RAN13.0 BSC6900 introduces the following new boards: 

OMUc



SCUb



NIUa

Table 2-3 briefly describes the functions of the OMUc, SCUb and NIUa.

Issue 06 (2012-11-30)


5


2 Overview

Table 2-3 RAN13.0 BSC6900 new boards Board Name

Board Type

Function

OMUc

Operation and maintenance board



Provides configuration management, performance management, fault management, security management, and loading management functions for the BSC6900



Provides an OM interface for communication between the LMT/M2000 and the BSC6900.



Provides online help information. One OMUc occupies only one slot and can be configured with one hard disk.

SCUb

Switching control board



Enables MAC switching and GE switching, supporting both ATM and IP networks



Provides data switching channels



Provides configuration and maintenance for a subrack or BSC6900



Distributes clock signals for the BSC6900 The SCUb provides a switching capacity of 240 Gbit/s, which is a 400% increase over the capacity of the SCUa.

NIUa

Service identification board



Provides the service identification function



Works with the service processing boards to schedule different types of services

2.2.2 NodeB A new hardware model BTS3902E is added to RAN13.0 NodeB family.

2.2.3 M2000 The M2000 compatible with RAN13.0 is iManager M2000-II V200R011. For a commercial network, iManager M2000-II V200R010 is upgraded to iManager M2000II V200R011 without changing the hardware. For a newly deployed network, iManager M2000-II V200R011 is used and its hardware configuration is slightly different from iManager M2000-II V200R010. For details, see the network impact report of iManager M2000-II V200R011.

2.3 Implementation Before upgrading from RAN12.0 to RAN13.0, ensure that all required hardware is installed and associated licenses are obtained. Perform the upgrade in the following order:

Issue 06 (2012-11-30)


6


2 Overview

1.

Upgrade the M2000 to iManager M2000-II V200R011.

2.

Upgrade the CME to iManager M2000-II V200R011.

3.

Upgrade the RNC to BSC6900 V900R013.

4.

Upgrade the NodeB to the RAN13.0 version according to Table 1-1.

2.4 Inter-NE Interface Iu, Iub, Iur, and Uu interfaces in RAN13.0 comply with 3GPP Release 9 and earlier releases. For the impact of each feature on these interfaces, see chapter 4 "Impacts of RAN13.0 Features on RAN12.0."

2.5 Operation and Maintenance RAN13.0 introduces new and enhanced features, and therefore MML commands, parameters, performance counters, alarms, events, and licenses have changed. For information about impacts of each feature on operation and maintenance, see chapter 4 "Impacts of RAN13.0 Features on RAN12.0." The operation and maintenance changes of the RNC and NodeB are highly related to the software version. For detailed changes in a specific software version, see the corresponding performance counter changes, MML command and parameter changes, alarm changes, event changes, and license changes documents, which are included in the RNC and NodeB releases documentations.

Issue 06 (2012-11-30)


7


3 Summary of Feature Impacts

3

Summary of Feature Impacts

This chapter describes the new and enhanced features in RAN13.0 and the dependencies of these features on other features, hardware, and network elements (NEs). The RAN products must meet these requirements before feature activation. For detailed information about impacts of each feature, see chapter 4 "Impacts of RAN13.0 Features on RAN12.0."

3.1 New and Enhanced RAN13.0 Features Table 3-1 lists the new and enhanced features of RAN13.0. A feature impact is classified as "Major" in the following situations: 

The feature requires new or additional hardware.



The feature requires additional UE capability.

All other types of impact are classified as "Minor". Table 3-1 New and enhanced features of RAN13.0 Feature ID

Feature Name

Impact

New or Enhanced

Basic or Optional

WRFD-000008

System Improvement for RAN13.0

Minor

New

Basic

WRFD-010101

3GPP R9 Specifications

Minor

Enhanced

Basic

MRFD-210303

Inventory Management

Minor

Enhanced

Basic

MRFD-210305

Security Management

Minor

Enhanced

Basic

MRFD-210801

Interface Tracing

Minor

Enhanced

Basic

MRFD-210401

RNC Software Management

Minor

Enhanced

Basic

MRFD-210310

NodeB Software USB Download

Minor

Enhanced

Basic

Issue 06 (2012-11-30)


8



Feature ID

Feature Name

Impact

New or Enhanced

Basic or Optional

WRFD-020406

Intelligent Power Measurement

Minor

New

Basic

WRFD01061002

HSDPA UE Category 1 to 28

Major

Enhanced

Optional

WRFD-020138

HSUPA Coverage Enhancement at UE power limitation

Major

New

Optional

WRFD-010712

Adaptive Configuration of Traffic Channel Power offset for HSUPA

Minor

New

Optional

WRFD-010701

Uplink Enhanced CELL_FACH

Major

New

Optional

WRFD-010702

Enhanced DRX

Major

New

Optional

WRFD-010703

HSPA+ Downlink 84Mbit/s per User (Trial)

Major

New

Optional

WRFD-010704

Flexible HSPA+ Technology Selection

Minor

New

Optional

WRFD-020137

Dual-Threshold Scheduling with HSUPA Interference Cancellation

Minor

New

Optional

WRFD-020136

Anti-Interference Scheduling for HSUPA

Minor

New

Optional

WRFD-010697

E-DPCCH Boosting

Major

New

Optional

WRFD-010698

HSPA+ Uplink 11.5Mbit/s per User

Major

New

Optional

WRFD-010713

Traffic-Based Activation and Deactivation of the Supplementary Carrier In Multi-carrier

Minor

New

Optional

WRFD-010699

DC-HSDPA+MIMO (Trial)

Major

New

Optional

WRFD-020806

Differentiated Service Based on SPI Weight

Minor

Enhanced

Optional

WRFD-020132

Web Page Access Acceleration

Major

New

Optional

WRFD-020133

P2P Downloading Rate Control during Busy Hour

Major

New

Optional

WRFD-020135

Intelligent Inter-Carrier UE Layered Management

Minor

New

Optional

Issue 06 (2012-11-30)


9



Feature ID

Feature Name

Impact

New or Enhanced

Basic or Optional

WRFD-020129

Service-Based PS Service Redirection from UMTS to LTE (Trial)

Minor

New

Optional

WRFD-020130

Videophone Service Restriction

Minor

New

Optional

WRFD-020131

Optimization of R99 and HSUPA Users Fairness

Minor

New

Optional

WRFD-020122

Multi-Carrier Switch off Based on QoS

Minor

New

Optional

WRFD-020121

Intelligent Power Management

Minor

New

Optional

WRFD02131106

Routing Roaming UEs in Proportion

Minor

New

Optional

Minor

Enhanced

Optional

WRFD-050402

IP Transmission Introduction on Iub Interface

Minor

Enhanced

Optional

WRFD-050409

IP Transmission Introduction on Iu Interface

Minor

Enhanced

Optional

WRFD-050410

IP Transmission Introduction on Iur Interface

WRFD-021350

Independent Demodulation of Signals from Multiple RRUs in One Cell

Minor

New

Optional

WRFD-020134

Push to Talk

Major

New

Optional

WRFD-012001

RNC offload (Trial)

Major

New

Optional

MRFD-221802

GSM and UMTS Dynamic Spectrum Sharing(UMTS)

Minor

New

Optional

WRFD-030010

CQI Adjustment Based on Dynamic BLER Target

Minor

New

Optional

WRFD-030011

MIMO Prime

Minor

New

Optional

MRFD-221703

2.0MHz Central Frequency point separation between GSM and UMTS mode(UMTS)

Minor

New

Optional

Issue 06 (2012-11-30)


10



In most cases, optional features are license controlled. Basic features are not license controlled.

3.2 Dependency on Other Features If there are any discrepancies between the pre-sales Feature Description and this section, the Feature Description will prevail as the most current information.

Table 3-2 describes the dependency of each new and enhanced RAN13.0 feature on other features. Table 3-2 Dependency of each new and enhanced RAN13.0 feature on other features Feature ID

Feature Name

Dependency

WRFD-000008


N/A

WRFD-010101


N/A

MRFD-210303


N/A

MRFD-210305

Security Management

N/A

MRFD-210801

Interface Tracing

N/A

MRFD-210401


N/A

MRFD-210310


N/A

WRFD-020406


N/A

WRFD-01061002


WRFD-010610 HSDPA Introduction Package

WRFD-020138


WRFD-010612 HSUPA Introduction Package

WRFD-010712



WRFD-010701


WRFD-010688 Enhanced CELL_FACH WRFD-010695 UL Layer 2 Improvement

WRFD-010702

Enhanced DRX

WRFD-010688 Enhanced CELL_FACH

WRFD-010703


WRFD-010689 HSPA+ Downlink 42Mbps per User WRFD-010693 Downlink 64QAM+MIMO WRFD-010699 DCHSDPA+MIMO (Trial)

Issue 06 (2012-11-30)


11



Feature ID

Feature Name

Dependency

WRFD-010704

Flexible HSPA+ Technology Selection

WRFD-010696 DC-HSDPA

Dual-Threshold Scheduling with HSUPA Interference Cancellation


WRFD-020137

WRFD-010684 2x2 MIMO

WRFD-010691 HSUPA UL Interference Cancellation WRFD-020136

Anti-Interference Scheduling for HSUPA


WRFD-010697

E-DPCCH Boosting


WRFD-010698

HSPA+ Uplink 11.5Mbit/s per User

WRFD-010694 UL 16QAM WRFD-010614 HSUPA Phase 2 WRFD-010697 E-DPCCH Boosting

WRFD-010713

Traffic-Based Activation and Deactivation of the Supplementary Carrier In Multi-carrier

WRFD-010696 DC-HSDPA

WRFD-010699

DC-HSDPA+MIMO (Trial)

WRFD-010696 DC-HSDPA WRFD-010684 2x2 MIMO

WRFD-020806


When applied in the downlink on the Uu interface, this feature depends on the feature WRFD01061103 Scheduling based on EPF and GBR. When applied in the uplink on the Uu interface, this feature depends on the feature WRFD01061402 Enhanced Fast UL Scheduling or WRFD-010638 Dynamic CE Resource Management. When this feature is enabled together with the feature WRFD01061402 Enhanced Fast UL Scheduling, only the uplink Uu interface resources can be differentially scheduled. When this feature is enabled together with the feature WRFD010638 Dynamic CE Resource Management, both the uplink Uu interface resources and CE resources can be differentially scheduled. When applied in the downlink on

Issue 06 (2012-11-30)


12



Feature ID

Feature Name

Dependency the Iub interface, this feature depends on the features WRFD010610 HSDPA Introduction Package and WRFD-050405 Overbooking on ATM Transmission, or the features WRFD-010610 HSDPA Introduction Package and WRFD-050408 Overbooking on IP Transmission. When applied in the uplink on the Iub interface, this feature depends on the feature WRFD010637 HSUPA Iub Flow Control in Case of Iub Congestion.

WRFD-020132


N/A

WRFD-020133


N/A

WRFD-020135

Intelligent Inter-Carrier UE Layered Management

WRFD-020400 DRD Introduction Package

WRFD-020129


N/A

WRFD-020130


N/A

WRFD-020131


WRFD-010612 HSUPA Introduction Package WRFD-021101 Dynamic Channel Configuration Control (DCCC)

WRFD-020122



WRFD-020121


N/A

WRFD-02131106


WRFD-021311 MOCN Introduction Package

WRFD-050402


N/A

WRFD-050409


N/A

WRFD-050410

IP Transmission Introduction on Iur Interface

N/A

Issue 06 (2012-11-30)


13



Feature ID

Feature Name

Dependency

WRFD-021350

Independent Demodulation of Signals from Multiple RRUs in One Cell

N/A

WRFD-020134

Push to Talk

WRFD-010612 HSUPA Introduction Package WRFD-010610 HSDPA Introduction Package WRFD-010688 Downlink Enhanced CELL_FACH WRFD-010636 SRB over HSUPA

WRFD-012001

RNC offload (Trial)

N/A

WRFD-030010

CQI Adjustment Based on Dynamic BLER Target


WRFD-030011

MIMO Prime


MRFD-221802

GSM and UMTS Dynamic Spectrum Sharing(UMTS)

On the dynamic spectrum shared carrier, this feature cannot be used together with MRFD211703 2.0MHz Central Frequency point separation between GSM and UMTS mode(GSM) and MRFD-221703 2.0MHz Central Frequency point separation between GSM and UMTS mode(UMTS). This feature cannot be used together with GBFD-117002 IBCA (Interference Based Channel Allocation) or GBFD117001 Flex MAIO.

MRFD-221703


GBFD-114801 Discontinuous Transmission (DTX) Downlink GBFD-117601 HUAWEI III Power Control Algorithm GBFD-117602 Active Power Control

3.3 Dependency on NEs If there are any discrepancies between the pre-sales Feature Description and this section, the Feature Description will prevail as the most current information.

Issue 06 (2012-11-30)


14



Table 3-3 describes the dependency of each new and enhanced RAN13.0 feature on the RNC, NodeB, UE, CN, and other NEs. Table 3-3 Dependency of each new and enhanced RAN13.0 feature on NEs Feature ID

Feature Name

Dependency RNC

NodeB

UE

Other NEs

CN

WRFD000008


N/A

N/A

N/A

N/A

N/A

WRFD010101


N/A

N/A

The associated interfaces must be upgraded to 3GPP Release 9 to support new and enhanced features introduced in 3GPP Release 9.



MRFD210303


N/A

N/A

N/A

Inventory information can be queried only on the M2000, which requires a license for this feature.

N/A

MRFD210305

Security Management

N/A

N/A

N/A

N/A

N/A

MRFD210801

Interface Tracing

N/A

N/A

N/A

N/A

N/A

MRFD210401


N/A

N/A

N/A

N/A

N/A

MRFD210310


N/A

Only 3900 series base stations support this feature.

N/A

N/A

N/A

WRFD020406


N/A

Only 3900 series base stations support this feature.

N/A

The M2000 must support this feature.

N/A

Issue 06 (2012-11-30)


15



Feature ID

Feature Name

Dependency RNC

NodeB

UE

Other NEs

CN

WRFD010610 02


N/A

N/A

N/A

N/A

N/A

WRFD020138


N/A

N/A

The UE must support 3GPP Release 8 or later and improved EUL power control at the UE power limit.

N/A

N/A

WRFD010712


N/A

N/A

N/A

N/A

N/A

WRFD010701


N/A

1. The BTS3812E, BTS3812A and BTS3812AE must be configured with the EULPd, EBBI, EBOI or EULP board. The downlink services must be set up on the EBBI, EBOI, or EULP board. The E-AI is not supported.

The UE must support 3GPP Release 8 or later. It also must support the uplink enhanced CELL_FAC H state.

N/A

N/A

2. The DBS3800 must be configured with the EBBC or EBBCd board. The downlink services must be set up on the EBBC or EBBCd board. To support the E-AI, the DBS3800 must be configured with the EBBCd board. 3. The 3900 series base station must be configured with

Issue 06 (2012-11-30)


16


Feature ID

Feature Name


Dependency RNC

NodeB

UE

Other NEs

CN

The UE must support 3GPP Release 8 or later. It also must support enhanced DRX.

N/A

N/A

The UE must be of HSDPA category 28.

N/A

The CN must support the downlink rate of 84 Mbit/s or higher per user.

N/A

N/A

the WBBPb or WBBPd board. The downlink services must be set up on the WBBPb or WBBPd board. To support the E-AI, the 3900 series base station must be configured with the WBBPd board. WRFD010702

Enhanced DRX

1. The BTS3812E, BTS3812A, and BTS3812AE must be configured with the EULPd, EBBI, EBOI, or EULP board.

N/A

2. The BBU3806 must be configured with the EBBC or EBBCd board; the BBU3806C must be configured with the EBBM board. 3. The BBU3900 must be configured with the WBBPb or WBBPd board. WRFD010703


1. The RNC must be configured with the DPUe board. 2. The RNC must be configured with the FG2a (providing GE ports), FG2c (providing GE ports), GOUa, or GOUc interface board.

WRFD010704

Flexible HSPA+ Technology

Issue 06 (2012-11-30)

N/A

1. The BTS3812AE, BTS3812E, and DBS3800 do not support this feature. 2. The 3900 series base stations must be configured with the WBBPd/WBBPb3/ WBBPb4 board.

1. The BTS3812E, BTS3812A, and BTS3812AE must

The UE must be of HSDPA


17


Feature ID

Feature Name


Dependency RNC

Selection

NodeB

UE

be configured with the EBBI, EBOI, and EDLP board. In addition, uplink services cannot be established on the HBBI or HULP.

category 21, 22, 23, 24, 25, 26, 27, or 28.

Other NEs

CN

N/A

N/A

2. The BBU3806 of the DBS3800 must be configured with the EBBC or EBBCd board; the BBU3806C must be configured with the EBBM board. 3. The 3900 series base stations must be configured with the WBBPb or WBBPd board. 4. Huawei BTS RF modules support only one transmission channel. MIMO requires interconnection of two RF modules. WRFD020137

DualThreshold Scheduling with HSUPA Interference Cancellation

N/A

1. The BTS3812E and BTS3812AE must be configured with the EULPd board.

N/A

2. The DBS3800 must be configured with the EBBCd board. 3. The 3900 series base stations must be configured with the WBBPd board in the UL resource pool that supports this feature, and slots 2 and 3 must be configured with at least one WBBPd board. 4. The 20 W

Issue 06 (2012-11-30)


18


Feature ID

Feature Name


Dependency RNC

NodeB

UE

Other NEs

CN

N/A

N/A

N/A

The UE must support 3GPP Release 7 or later. It also must support EDPCCH Boosting.

N/A

CN supports data bit rate of 11.5Mbit/s or above.

The UE

N/A

The CN

RRU3801C and the MTRU for the BTS3812E and BTS3812AE do not support this feature. WRFD020136

AntiInterference Scheduling for HSUPA

N/A

1. The BTS3812E and BTS3812AE must be configured with the HBBI, HULP, EBBI, EBOI, EULP, or EULPd board. Downlink services can be established only on the EBBI, EBOI, and EDLP boards. 2. The BBU3806 must be configured with the EBBC or EBBCd board; the BBU3806C must be configured with the EBBM board. 3. The BBU3900 must be configured with the WBBPb or WBBPd board.

WRFD010697

E-DPCCH Boosting

N/A

1. The BTS3812E and BTS3812AE must be configured with the EULPd board. Downlink services cannot be established on the HBBI or HDLP/NDLP board. 2. The DBS3800 must be configured with the EBBCd board. 3. The 3900 series base stations must be configured with the WBBPd board.

WRFD-

HSPA+

Issue 06 (2012-11-30)

N/A

1. The BTS3812E


19


Feature ID

Feature Name

010698

Uplink 11.5Mbit/s per User


Dependency RNC

NodeB

UE

and BTS3812AE must be configured with the EULPd board. Downlink services cannot be established on the HBBI or HDLP/NDLP board.

must support EDPCCH boosting. The UE must be of HSUPA category 7, 8, or 9.

Other NEs

CN must support the uplink rate of 11.5 Mbit/s or higher per user.

2. The DBS3800 must be configured with the EBBCd board. 3. The 3900 series base stations must be configured with the WBBPd board. WRFD010713

Traffic-Based Activation and Deactivation of the Supplementar y Carrier In Multi-carrier

N/A

N/A

The UE must be of HS-DSCH category 21, 22, 23, or 24 to support DCHSDPA.

N/A

N/A

N/A

N/A

The UE must be of HS-DSCH category 25, 26, 27, or 28 to support DCHSDPA+M IMO. WRFD010699

DCHSDPA+MIM O (Trial)

N/A

1. The BTS3812E and BTS3812AE must be configured with the EBBI or EDLP board. Uplink services cannot be established on the HBBI or HULP board.

The UE must be of HSDPA category 25, 26, 27, or 28.

2. The DBS3800 must be configured with the EBBC or EBBCd board. The DBS3800 allows

Issue 06 (2012-11-30)


20


Feature ID

Feature Name


Dependency RNC

NodeB

UE

Other NEs

CN

only one cell of the DC group to be configured with MIMO. 3. The 3900 series base stations must be configured with the WBBPb or WBBPd board. WRFD020806


N/A

N/A

N/A

N/A

N/A

WRFD020132


The RNC must be configured with the NIUa board.

1. The BTS3812E and BTS3812AE must be configured with the EBBI or EDLP board. The HBBI and HDLP boards do not support this feature.

N/A

N/A

N/A

N/A

N/A

N/A

2. The DBS3800 must be configured with the EBBC or EBBCd board. The HBBU board does not support this feature. 3. The 3900 series base stations must be configured with the WBBPb or WBBPd board. The WBBPa board does not support this feature. WRFD020133


The RNC must be configured with the NIUa board.

1. The BTS3812E and BTS3812AE must be configured with the EBBI or EDLP board. The HBBI and HDLP boards do not support this feature. 2. The DBS3800 must be configured with the EBBC or

Issue 06 (2012-11-30)


21


Feature ID

Feature Name


Dependency RNC

NodeB

UE

Other NEs

CN

This feature requires operators to separately allocate IMSI ranges to UEs and data cards.

EBBCd board. The HBBU board does not support this feature. 3. The 3900 series base stations must be configured with the WBBPb or WBBPd board. The WBBPa board does not support this feature. WRFD020135

Intelligent Inter-Carrier UE Layered Management N/A

N/A

N/A

N/A

WRFD020129


N/A

N/A

The UE must support both UMTS and LTE and support 3GPP Release 8 or later.

N/A

The CN must support interworking between UMTS and LTE.

WRFD020130


N/A

N/A

N/A

N/A

N/A

WRFD020131


N/A

1. The BTS3812E and BTS3812AE must be configured with the EBBI, EULP, or EULPd board. The HBBI and HULP boards do not support this feature.

N/A

N/A

N/A

2. The DBS3800 must be configured with the EBBC or EBBCd board. The BBU3806 does not support this

Issue 06 (2012-11-30)


22


Feature ID

Feature Name


Dependency RNC

NodeB

UE

Other NEs

CN

feature. The BBU3806C must be configured with the EBBM board. 3. The 3900 series base stations must be configured with the WBBPb or WBBPd board. The WBBPa board does not support this feature. WRFD020122


N/A

N/A

N/A

N/A

N/A

WRFD020121


N/A

Only the BTS3900A and DBS3900 configured with the APM30 and batteries support this feature.

N/A

N/A

N/A

WRFD021311 06


N/A

N/A

N/A

N/A

The CN must support the MOCN function. If the CN detects the initial registration of a roaming UE, it must request CS/PS coordinatio n and send the IMSI of the UE to the RNC.

IP header compression must be supported by the PEUa, POUa, and POUc boards.

The BTS3812E or BTS3812AE must be configured with the NUTI board.

N/A

N/A

N/A

WRFD050402


Issue 06 (2012-11-30)

Only the 3900 series NodeB supports inter-


23


Feature ID

Feature Name


Dependency RNC

NodeB

Only the Dopra Linux operating system supports the RNC integrated firewall for the OM interface.

board ML-PPP.

UE

Other NEs

CN

N/A

N/A

The CN must support IP transmission.

Only the FG2c and GOUc boards support the RNC integrated firewall for the Iub, Iur, and Iu interfaces. To support BFD, the BSC6900 must be configured with the FG2a, GOUa, FG2c, and GOUc boards. Only the Dopra Linux operating system supports the RNC integrated firewall for the OM interface.

N/A

Only the FG2c and GOUc boards support the RNC integrated firewall for the Iub, Iur, and Iu interfaces.

WRFD050409


Issue 06 (2012-11-30)

To support BFD, the BSC6900 must be configured with the FG2a, GOUa, FG2c, and GOUc boards.


24


Feature ID

Feature Name


Dependency RNC

NodeB

UE

Other NEs

CN

Only the Dopra Linux operating system supports the RNC integrated firewall for the OM interface.

N/A

N/A

The neighboring RNC must support IP transmissio n over the Iur interface.

N/A

1. Only the DBS3900 supports this feature. The DBS3900 must be configured with the WBBPb or WBBPd board.

N/A

N/A

N/A

Only the FG2c and GOUc boards support the RNC integrated firewall for the Iub, Iur, and Iu interfaces.

WRFD050410 WRFD021350

IP Transmission Introduction on Iur Interface Independent Demodulation of Signals from Multiple RRUs in One Cell

To support BFD, the BSC6900 must be configured with the FG2a, GOUa, FG2c, and GOUc boards. N/A

2. The BTS3902E does not support this feature. WRFD020134

Push to Talk

N/A

N/A

The UE must support this feature.

N/A

The CN must support this feature.

WRFD012001

RNC offload (Trial)

Only the FG2c and GOUc boards support the Gi interface between the RNC and the Internet.

N/A

N/A

N/A

N/A

WRFD030010

CQI Adjustment

N/A

1. The BTS3812E and BTS3812AE

N/A

N/A

N/A

Issue 06 (2012-11-30)


25


Feature ID

Feature Name


Dependency RNC

Based on Dynamic BLER Target

NodeB

UE

Other NEs

CN

N/A

N/A

N/A

must be configured with the EBBI, EBOI, or EDLP board. 2. The BBU3806 must be configured with the EBBC or EBBCd board; the BBU3806C must be configured with the EBBM board. 3. The BBU3900 must be configured with the WBBPb or WBBPd board.

WRFD030011

MIMO Prime

N/A

1. This feature is supported only by the 40 W RRU3801C, RRU3804, RRU3806, RRU3808, WRFU, RRU3805, WRFUd, RRU3828, RRU3829, RRU3928, RRU3929, MRFUd, and MRFUe as well as the RRU3908 V1 operating in 850 MHz, 900 MHz, and 1900 MHz. 2. For RF modules providing only one transmit channel, two such RF modules need to be interconnected to support this feature. 3. The BBU3900 must be configured with the WBBPb or WBBPd board. 4. The BTS3812E and BTS3812AE do not support this

Issue 06 (2012-11-30)


26


Feature ID

Feature Name


Dependency RNC

NodeB

UE

Other NEs

CN

N/A

The M2000 must be upgraded to iManager M2000-II V200R011.

N/A

N/A

It is recommend ed that Huawei professional services be ordered when using this feature.

N/A

feature. 5. The DBS3800 does not support this feature. MRFD221802

MRFD221703

GSM and UMTS Dynamic Spectrum Sharing(UMT S)

N/A


N/A

Only the 900M MRFU/MRRU supports this feature. GSM and UMTS sharing PA configuration is requested. UMTS: 900M MRRU V1/ V2/V3 900M MRFU V2/V3 850M MRRU V2 GSM: NULL

Issue 06 (2012-11-30)


27


4

4 Impacts of RAN13.0 Features on RAN12.0

Impacts of RAN13.0 Features on RAN12.0 This chapter describes how the new and enhanced features in RAN13.0 affect RAN12.0 in terms of capacity and performance, interfaces, and operation and maintenance. For information about how these features depend on other features, hardware, and NEs, see chapter 3 "Summary of Feature Impacts."

4.1 WRFD-000008 System Improvement for RAN13.0 (New/Basic) 4.1.1 Description This feature is new in RAN13.0. This feature provides the following system enhancements and improvements to RAN13.0: 

Support for new features specified in 3GPP Release 9 (March 2010)



Improved RNC interface processing and board processing capabilities



Improved maintainability, including enhanced troubleshooting and real-time tracing functions



Increased power efficiency, enabling operators to reduce operational expenditure

4.1.2 Capacity and Performance System Capacity The processing capability of the DPUe board is increased from 500 Mbit/s to 800 Mbit/s.

Network Performance No impact.

4.1.3 Inter-NE Interface No impact.

Issue 06 (2012-11-30)


28



4.1.4 Operation and Maintenance This feature is not under license control.

4.2 WRFD-010101 3GPP R9 Specifications (Enhanced/Basic) 4.2.1 Description RAN13.0 complies with 3GPP Release 9. RAN13.0 helps operators provide enriched services with higher performance, enhancing operators' competitive edge. RAN13.0 allows for interconnection with NEs that comply with 3GPP Release 9 and earlier releases, protecting operators' investments.

4.2.2 Capacity and Performance System Capacity No impact.


4.2.3 Inter-NE Interface The Uu, Iub, Iur, and Iu interfaces must be upgraded to support new features introduced in 3GPP Release 9.


4.3 MRFD-210303 Inventory Management (Enhanced/Basic) 4.3.1 Description This feature helps report information about the physical and logical objects of the NEs to the M2000. The M2000 then manages the reported information. RAN13.0 enables NodeBs to report the information on Remote Electrical Tilt (RET) electronic tags to the M2000.


Issue 06 (2012-11-30)


29





4.3.4 Operation and Maintenance This feature is not under license control. Inventory information can be queried only on the M2000, which requires a license for this feature. Enhancement of the feature does not impact the MML commands or parameters. The information on remote electrical tilt (RET) electronic tags is added to the device file, which can be generated by using the command EXP DEVFILE. After NodeB components are changed, the updated device file can be exported by using the command EXP DEVFILE and then uploaded to the M2000 by using the command ULD DEVFILE.

4.4 MRFD-210305 Security Management (Enhanced/Basic) 4.4.1 Description This feature enhances network security management by providing various user authorization and management mechanisms. Security management enhances system security in the following ways: 

Facilitates user management such as management of user accounts, user rights, and user command groups.



Supports the backup and restoration of system data.



Adopts the Windows security policies for IP services of the Back Administration Module (BAM) to protect the system from cyber attacks.



Supports the installation of antivirus software such as Norton, McAfee, and Officescan.



Collects database operation logs and audit logs.



Reports corresponding alarms when cyber attacks are detected or the number of unauthorized access attempts exceeds the threshold.



Supports FTP over the Security Socket Layer (SSL).



Supports SSL for the communication between the GBSS/RAN and the Operation and Maintenance Center (OMC). This enables the encryption of all transmitted data.



Adds authority control for the binary interface between the GBSS/RAN and the OMC.



Records information about the operation logs for the binary interface between the GBSS/RAN and the OMC.

This feature is enhanced in RAN13.0 and includes new security alarm and security log functions. Security alarms will be reported and related entries will be recorded into the log in the following cases: 

The number of failed login attempts of a local user exceeds the specified limit.



The digital certificate is about to expire.

Issue 06 (2012-11-30)


30





The digital certificate has expired or been corrupted.



The number of received illegal packets exceeds the specified limit.





4.5 MRFD-210801 Interface Tracing (Enhanced/Basic) 4.5.1 Description This feature is used for interface message tracing in online/offline mode and routine equipment management. With this feature, maintenance personnel can trace messages in real time, stop refreshing, save tracing messages, review tracing results, and check when messages are sent so that maintenance personnel can accurately locate and solve problems. In addition, all the interfaces can perform condition filtering. Maintenance personnel can reduce the number of traced messages through condition filtering to increase tracing accuracy. This feature is enhanced in RAN13.0 to locate internal communication errors within the RNC for debugging purposes. The errors include communication interruption and packet loss. With the enhancement, signaling packets, cell common channel packets, and single-user packets that are processed by the interface boards are traced and then compared with the packets processed by signaling and traffic processing boards to check if faults exist in the RNC.



Issue 06 (2012-11-30)


31




4.5.4 Operation and Maintenance This feature is not under license control. To use this feature, the LMT needs to be used to start signaling tracing tasks.

4.6 MRFD-210401 RNC Software Management (Enhanced/Basic) 4.6.1 Description This feature provides software installation, software upgrade, and patch installation functions for the RNC. This facilitates remote management of RNC software. RAN13.0 introduces a software integrity check that verifies digital signatures of the RNC software before the software installation.





4.7 MRFD-210310 NodeB Software USB Download (Enhanced/Basic) 4.7.1 Description With this feature, users or maintenance personnel can download and activate NodeB software through a USB storage device without using a laptop. This allows for quick and easy setup of the NodeB.

Issue 06 (2012-11-30)


32



RAN13.0 enhances this feature by adding an encryption mechanism to software packages in the USB storage device. This protects software packages from unauthorized possession or malicious modification. Software packages can be decrypted on the NodeB side.





4.8 WRFD-020406 Intelligent Power Measurement (New/Basic) 4.8.1 Description This feature is a new RAN13.0 feature. The NodeB reports the power consumption status to the EMS. Through the EMS, the change in power consumption of the NodeB can be monitored by the operator, and a report on the power consumption can be generated.





Issue 06 (2012-11-30)


33



Power consumption of the equipment, which is powered by the Power Supply Unit (PSU) and managed by the Power and Environment Monitoring Unit (PMU) can be queried on the M2000.

4.9 WRFD-010699 DC-HSDPA+MIMO (Trial) (New/Optional) 4.9.1 Description This trial feature is new in RAN13.0. 3GPP Release 9 introduces Dual Carrier (DC)-HSDPA+MIMO, which combines DC-HSDPA (introduced in 3GPP Release 8) and MIMO (introduced in 3GPP Release 7). DCHSDPA+MIMO allows a NodeB to send HSDPA data to a UE over two adjacent carriers on the same frequency band within the same coverage area by using MIMO. By using the dual-carrier and multi-antenna techniques together, DC-HSDPA+MIMO improves spectral efficiency, and therefore significantly increases single-user peak throughput, the throughput of users at the cell edge, and cell capacity. Figure 4-1 shows the basic principles of DC-HSDPA+MIMO. Figure 4-1 Basic principles of DC-HSDPA+MIMO

This feature allows one or both carriers to be configured with MIMO for 64QAM users. When one carrier is configured with 64QAM and MIMO, the theoretical peak rate reaches 63 Mbit/s. When both carriers are configured with 64QAM and MIMO, the theoretical peak rate reaches 84 Mbit/s. DC-HSDPA+MIMO applies to PS streaming services and best effort (BE) services. DC-HSDPA+MIMO applies the same principles as DC-HSDPA in load control and mobility management.

4.9.2 Capacity and Performance System Capacity DC-HSDPA+MIMO increases spectral efficiency and increases system throughput by 10% to 20%, as indicated in emulation results.

Issue 06 (2012-11-30)


34



Network Performance 

Increased peak throughput per single user Compared with DC-HSDPA, DC-HSDPA+MIMO provides spatial multiplexing gain by using multiple antennas. Compared with MIMO, DC-HSDPA+MIMO enables the simultaneous use of two carriers. DC-HSDPA+MIMO increases the single-user peak rate from 28 Mbit/s to 56 Mbit/s (without 64QAM) and from 42 Mbit/s to 84 Mbit/s (with 64QAM).



Increased throughput of users at the cell edge DC-HSDPA+MIMO uses two carriers, and therefore doubles the throughput as compared with SC-MIMO.

4.9.3 Inter-NE Interface The RNC determines whether the NodeB supports DC-HSDPA+MIMO through the Audit or Resource Status Indication procedures on the Iub interface. The NodeB replies with the DCHSDPA+MIMO capability and inter-frequency cell information of the cell. The UE informs the RNC of whether the UE supports DC-HSDPA+MIMO through the RRC CONNECTION SETUP COMPLETE, UE CABILITY INFORMATION, and CELL UPDATE messages.

4.9.4 Operation and Maintenance This feature is under license control. This feature can be activated only when DC-HSDPA and MIMO features are activated. New switches are added to the RNC and NodeB: 

CFG_HSDPA_DCMIMO_SWITCH is added to the parameter CfgSwitch in the RNC command SET UCORRMALGOSWITCH. To enable this feature at the RNC level, the parameter CfgSwitch must be set to CFG_HSDPA_DCMIMO_SWITCH-1.



DCMIMO_HSDPA is added to the parameter HspaPlusSwitch in the RNC command ADD UCELLALGOSWITCH. To enable this feature in a cell, the parameter HspaPlusSwitch must be set to DCMIMO_HSDPA-1.



The parameter DC_MIMO is added to the NodeB commands ADD LOCELL and MOD LOCELL. To enable this feature in a local cell, the parameter DC_MIMO must be set to TRUE.

New counters are added to measure the number of DC-HSDPA+MIMO service setups, releases, completions, and abnormal releases.

4.10 WRFD-010703 HSPA+ Downlink 84Mbit/s per User (Trial) (New/Optional) 4.10.1 Description This trial feature is a new RAN13.0 feature. As stipulated in 3GPP Release 9, DC-HSDPA and MIMO can be used together. With 64QAM, DC-HSDPA+MIMO allows for a maximum rate of 84 Mbit/s for a single user in the downlink.

Issue 06 (2012-11-30)


35



4.10.2 Capacity and Performance This feature is developed to help control feature licensing. This feature is based on DC-HSDPA+MIMO. For information about how DCHSDPA+MIMO affects the system, see section 4.9 "WRFD-010699 DC-HSDPA+MIMO (Trial) (New/Optional)."

4.10.3 Inter-NE Interface This feature is developed to help control feature licensing. This feature is based on DC-HSDPA+MIMO. For information about how DCHSDPA+MIMO affects the inter-NE interfaces, see section 4.9 "WRFD-010699 DCHSDPA+MIMO (Trial) (New/Optional)."

4.10.4 Operation and Maintenance This feature is under license control. For information about how DC-HSDPA+MIMO affects operation and maintenance, see section 4.9 "WRFD-010699 DC-HSDPA+MIMO (Trial) (New/Optional)."

4.11 WRFD-01061002 HSDPA UE Category 1 to 28 (Enhanced/Optional) 4.11.1 Description This feature supports HSDPA UE categories 1 through 28. The maximum rate of a UE depends on its category. RAN13.0 adds support for HSDPA UE categories 25 through 28.




4.11.4 Operation and Maintenance This feature is under license control.

Issue 06 (2012-11-30)


36



New counters are added to measure the number of times that HSDPA UEs of categories 25 through 28 access the network.

4.12 WRFD-020138 HSUPA Coverage Enhancement at UE Power Limitation (New/Optional) 4.12.1 Description This feature is new in RAN13.0. HSUPA Coverage Enhancement at UE Power Limitation ensures uplink transmission continuity and improves coverage by increasing the minimum power-scaling ratio of the EDCH Dedicated Physical Data Channel (E-DPDCH) to the Dedicated Physical Control Channel (DPCCH). This new feature is based on the enhanced HSUPA power scaling technique specified in 3GPP Release 8. As indicated in 3GPP specifications, when the transmit power of an HSUPA UE transmitting uplink data at a minimum rate is limited, the UE enters power-scaling mode. In this mode, the E-DPDCH power is reduced by decreasing the power offset of the E-DPDCH relative to the DPCCH. After the power-scaling ratio reaches the minimum, the transmit power of each uplink physical channel is scaled proportionally. With the traditional power-scaling technique, the power offset of the E-DPDCH relative to the DPCCH is not of an optimum value. After the scaling, the power of the E-DPDCH may be too low to transmit data, affecting the cell coverage. The enhanced HSUPA power scaling technique solves this problem by increasing the minimum power-scaling ratio of the E-DPDCH relative to the DPCCH. This guarantees the power of the E-DPDCH. This technique also optimizes the transport block size, improving the HSUPA coverage at the cell edge.


Network Performance This feature improves coverage of HSUPA services at the cell edge for BE services and voice services. Emulation results show that coverage of HSUPA services increases by about 10%.

4.12.3 Inter-NE Interface This feature affects messages on the Uu interface. The RNC sends the UE the minimum power ratio of E-DPDCH/DPCCH through the RRC signaling such as the messages RADIO BEARER SETUP, RADIO BEARER CONFIGURATION, TRANSPORTATION CHANNEL RECONFIGURATION, and PHYSICAL CHANNEL RECONFIGURATION.


Issue 06 (2012-11-30)


37



A new switch PC_HSUPA_COVER_EN_AT_POLIMIT_SWITCH is added to the parameter PcSwitch in the RNC command SET UCORRMALGOSWITCH. To enable this feature, the parameter PcSwitch must be set to PC_HSUPA_COVER_EN_AT_POLIMIT_SWITCH-1.

4.13 WRFD-010712 Adaptive Configuration of Traffic Channel Power Offset for HSUPA (New/Optional) 4.13.1 Description This feature is new in RAN13.0. This new feature is applicable to the HSUPA 10 ms Transmission Timing Interval (TTI) Best Effort (BE) service. When an HSUPA 10 ms TTI UE has a small target number of retransmissions (known as small retransmissions), this feature dynamically configures an optimal power offset for the traffic channel based on the changes in uplink load and throughput. This feature helps maintain the power of such a UE on the uplink DPCCH at an optimal level, thereby increasing the capacity of HSUPA cells with multiple HSUPA 10 ms TTI UEs. This feature significantly improves the capacity of HSUPA cells in a live network, where the feature WRFD-010641 HSUPA Adaptive Transmission is unavailable or UEs in HSUPA adaptive transmission mode cannot perform a large number of retransmissions (known as large retransmissions) due to insufficient channel elements (CEs). UEs in HSUPA adaptive transmission mode require twice the CEs. The offset of E-DPDCH power relative to DPCCH power is one of the major factors that determine the DPCCH power in the uplink. For an HSUPA 10 ms TTI UE in the small retransmission state, if the data rate is low, a high offset can be configured. This decreases the DPCCH power and reduces the DPCCH load. After the load is reduced, UEs can transmit more data in the uplink, thereby increasing the capacity of HSUPA cells. If the data rate is high, a low offset can be configured. This increases the DPCCH power, thereby meeting the power requirements of multipath searching and channel estimation and ensuring high performance of HSUPA services. When the feature WRFD-010641 HSUPA Adaptive Transmission enables HSUPA 10 ms TTI UEs to be in the large retransmission state, the offset of the E-DPDCH power relative to the DPCCH power is not adjusted. In such a case, the gain of HSUPA adaptive transmission is not affected. The feature WRFD-010641 HSUPA Adaptive Transmission increases cell capacity at the cost of more CE consumption. In contrast, this feature does not require more CE consumption to increase the cell capacity. This feature and the feature WRFD-010641 HSUPA Adaptive Transmission are independent from each other, but they can be used together. This feature is not applicable to 2 ms HSUPA services because in commercial networks 10 ms UEs account for the majority of HSUPA UEs and 2 ms UEs can be reconfigured as 10 ms UEs in heavily loaded networks.

Issue 06 (2012-11-30)


38



4.13.2 Capacity and Performance System Capacity This feature significantly increases the HSUPA capacity of cells that have a large number of HSUPA UEs processing low-speed uplink services. When there are twenty to thirty 10 ms TTI UEs processing data services in hot spots during busy hours, this feature increases the HSUPA capacity of the cell by 5% to 20%, without increasing the cell load. This capacity improvement is indicated by the increase in average cell throughput, in the number of UEs that can simultaneously perform data transmission in the uplink, and in the decrease in Received Total Wideband Power (RTWP).



4.13.4 Operation and Maintenance This feature is under license control. A new switch PC_HSUPA_DATA_CH_PO_ADAPTIVE_ADJ_SWITCH is added to the parameter PcSwitch in the RNC command SET UCORRMALGOSWITCH. To enable this feature, the parameter PcSwitch must be set to PC_HSUPA_DATA_CH_PO_ADAPTIVE_ADJ_SWITCH-1.

4.14 WRFD-010701 Uplink Enhanced CELL_FACH (New/Optional) 4.14.1 Description This feature is new in RAN13.0. Uplink enhanced CELL_FACH, introduced in 3GPP Release 8, allows UEs in the CELL_FACH state to use the E-DPDCH instead of the PRACH to achieve higher data rates in the uplink. The E-DPDCH provides higher data rates because it uses 2 ms TTI or 10 ms TTI. In contrast, the PRACH uses 20 ms TTI, providing a data rate of 8 kbit/s. Uplink enhanced CELL_FACH uses the E-AI to make better use of the signatures for random access. In the uplink enhanced CELL_FACH state, there is a lower possibility of uplink channel collision, allowing for smoother data transmission.

4.14.2 Capacity and Performance System Capacity In RAN13.0, cells allow a limited number of UEs in the uplink enhanced CELL_FACH state to transmit data simultaneously. This does not affect the system capacity. One reason is that Issue 06 (2012-11-30)


39



uplink enhanced CELL_FACH, which provides significantly higher data rates, enables quick resource allocation and release. Also, there are currently a small number of UEs in the uplink enhanced CELL_FACH state in commercial networks. This feature reduces uplink interference in the case of continuous data transmission because uplink enhanced CELL_FACH requires less physical random access procedures than nonenhanced uplink CELL_FACH. Uplink enhanced CELL_FACH can further improve uplink system capacity if more UEs can be configured in the CELL_FACH state.

Network Performance This feature has the following impacts on network performance: 

Shorter service setup delay The delay for a UE to switch from idle mode to the CELL_DCH state to establish services is shortened.



Shorter state transition delay The delay for a UE to switch from the CELL_FACH state to CELL_DCH state is shortened.



Higher uplink data rates The theoretical peak rate reaches 5.76 Mbit/s.

This feature has the following impacts on coverage: 

When used together with uplink enhanced layer 2, this feature provides better coverage for signaling and traffic when using the 10 ms TTI in the enhanced uplink CELL_FACH state than in the uplink non-enhanced CELL_FACH state.



When using the 2 ms TTI in the enhanced uplink CELL_FACH state, this feature provides smaller coverage for signaling than in the uplink non-enhanced CELL_FACH state. The coverage for traffic is not affected.

4.14.3 Inter-NE Interface This feature affects messages on the Uu and Iub interfaces. The RNC learns whether a NodeB supports uplink enhanced CELL_FACH during the Audit or Resource Status Indicator procedures. If the NodeB supports uplink enhanced CELL_FACH, the RNC informs the NodeB of the uplink enhanced CELL_FACH configuration using the PHYSICAL CHANNEL RECONFIGURATION REQUEST message. The NodeB informs the RNC of EDCH resource usage using the COMMON MEASUREMENT REPORT message. The RNC informs the NodeB to release one or more E-DCH Radio Network Temporary Identifiers (E-RNTIs) to the UE in the CELL_FACH state using the UE STATUS UPDATE COMMAND message. The UE informs the RNC of its uplink enhanced CELL_FACH capabilities using the corresponding indicators in the RRC CONNECTION REQUEST message. The UE CAPABILITY INFORMATION and CELL UPDATE messages also include the corresponding indicators. The RNC informs the UE of whether the cell supports uplink enhanced CELL_FACH using the SIB5 or 5bis system information message.

Issue 06 (2012-11-30)


40



4.14.4 Operation and Maintenance This feature is under license control. RNC switches are modified as follows: 

The parameter EFachSwitch in the commands SET URRCESTCAUSE and SET USUBRRCESTCAUSE is extended to specify whether to enable uplink enhanced CELL_FACH and downlink enhanced CELL_FACH during RRC setup.



The following switches of the parameter MapSwitch in the commands SET UCORRMALGOSWITCH and SET USUBCORRMALGOSWITCH are extended: −

MAP_PS_BE_ON_E_FACH_ SWITCH: specifies whether BE services use uplink enhanced CELL_FACH.

−

MAP_PS_STREAM_ON_E_FACH_ SWITCH: specifies whether streaming services use downlink enhanced CELL_FACH.

New RNC commands are added as follows: 

ADD UERACHASC, MOD UERACHASC, RMV UERACHASC, and LST UERACHASC: used to configure the access service classes for uplink enhanced CELL_FACH.



ADD UERACHACTOASCMAP, MOD UERACHACTOASCMAP, RMV UERACHACTOASCMAP, and LST UERACHACTOASCMAP: used to configure the mapping between the access classes and access service classes for uplink enhanced CELL_FACH.



ADD UERACHBASIC, MOD UERACHBASIC, RMV UERACHBASIC, and LST UERACHBASIC: used to configure the basic information of uplink enhanced CELL_FACH, including the common E-DCH TTI, available preamble signatures, available access sub-channels, and preamble constant value.

New RNC parameters are added as follows: 

ERACHUL: added to the commands ADD TRMFACTOR and MOD TRMFACTOR to specify the channel activity factor in the uplink enhanced CELL_FACH state.



MaxERACHUserNum: added to the commands ADD UCELLCAC and MOD UCELLCAC to specify the maximum number of users configured in the uplink enhanced CELL_FACH state in a cell.

A new NodeB parameter is added as follows: 

ERACH: added to the commands ADD LOCELL and MOD LOCELL to specify whether a local cell supports uplink enhanced CELL_FACH.

New counters are added to measure the following items: 

Number of RRC setups in the uplink enhanced CELL_FACH state



Number of RAB setups and releases in the downlink enhanced CELL_FACH state



Number of users, delay, and traffic volume in the uplink enhanced CELL_FACH state

Issue 06 (2012-11-30)


41



4.15 WRFD-010702 Enhanced DRX (New/Optional) 4.15.1 Description This feature is new in RAN13.0. 3GPP Release 7 introduced continuous packet connectivity (CPC), which incorporates the discontinuous reception (DRX) technique that saves power for HSPA UEs in the CELL_DCH state. 3GPP Release 8 introduces downlink enhanced DRX, which saves power for UEs in the enhanced CELL_FACH state. Enhanced DRX enables UEs in the enhanced CELL_FACH state to receive data from the high-speed downlink shared channel (HS-DSCH) discontinuously. With this feature, the UTRAN and a UE in the enhanced CELL_FACH state transmit and receive data at specified times. The UE monitors the High Speed Shared Control Channel (HS-SCCH) at regular intervals instead of monitoring the HS-SCCH continuously. When there is no data to transmit, the UE shuts down its receiver, reducing power consumption.


Network Performance This feature reduces the power consumption of the receivers of UEs in the enhanced CELL_FACH state. The power consumption reduction depends on parameter settings, the amount of transmitted data, and specific implementation of UE manufacturers. With enhanced DRX, the UTRAN sends data to UEs in the enhanced CELL_FACH state only at user-specified times, which leads to a slight increase in transmission delay.

4.15.3 Inter-NE Interface This feature affects messages on the Uu and Iub interfaces. The RNC learns whether a NodeB supports enhanced DRX during Audit or Resource Status Indicator procedures. If the NodeB supports enhanced DRX, the RNC informs the NodeB of the enhanced DRX configuration using the PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST message. The RNC uses the SIB5 or 5bis system information message to inform the UE of whether the cell supports enhanced DRX. The UE informs the RNC of its enhanced DRX capabilities using the corresponding indicators in the RRC CONNECTION SETUP COMPLETE message. The UE CAPABILITY INFORMATION and CELL UPDATE messages also include the corresponding indicators.

4.15.4 Operation and Maintenance This feature is under license control. A new RNC switch E_DRX is added to the parameter HspaPlusSwitch in the command ADD UCELLALGOSWITCH.

Issue 06 (2012-11-30)


42



A new RNC command ADD UCELLEDRX is added to configure the following enhanced DRX-related parameters: 

EDRXT321: specifies the timer T321 for DRX in the CELL_FACH state.



EDRXCycle: specifies the DRX cycle in the CELL_FACH state.



EDRXBurst: specifies the DRX burst length in the CELL_FACH state.



EDRXInterruptbyHSDSCHData: specifies whether DRX can be interrupted by HSDSCH data.

A new counter is added to measure the mean number of UEs using enhanced DRX on the EFACH in a cell.

4.16 WRFD-010704 Flexible HSPA+ Technology Selection (New/Optional) 4.16.1 Description This feature is new in RAN13.0. This feature allows admitted HSDPA users to dynamically select between DC-HSDPA and MIMO. Selections are made based on the number of HSDPA users (including SC-HSDPA and DC-HSDPA users) and the downlink load on the two DC-HSDPA cells. This feature enables the services of HSDPA users to always be carried by the appropriate HSPA+ technique in DC-HSDPA cells with one or both cells configured with MIMO. This allows for a higher downlink throughput. When the number of HSDPA users is small and the DC-HSDPA cell load is low, services are carried by DC-HSDPA. When the number of HSDPA users is large and the DC-HSDPA cell load is high, services are carried by MIMO.

4.16.2 Capacity and Performance System Capacity This feature increases the total downlink throughput in MIMO-capable DC-HSDPA cells.



4.16.4 Operation and Maintenance This feature is under license control. A new RNC switch CFG_DC_MIMO_DYNAMIC_SELECT_SWITCH is added to the parameter CfgSwitch in the command SET UCORRMALGOSWITCH. To enable this feature, this switch must be turned on. The following RNC parameters are added to the command SET UFRC:

Issue 06 (2012-11-30)


43





SecCellTcpThd: specifies the downlink transmit power threshold for a DC-HSDPA secondary cell. A larger value results in a lower possibility that services of HSDPA users are carried by MIMO. A smaller value results in a higher possibility that services of HSDPA users are carried by MIMO.



SecCellHUserNumThd: specifies the threshold for the number of downlink HSDPA users in a DC-HSDPA secondary cell. A larger value indicates a lower possibility that services of HSDPA users are carried by MIMO. A smaller value indicates a higher possibility that services of HSDPA users are carried by MIMO.

4.17 WRFD-020137 Dual-Threshold Scheduling with HSUPA Interference Cancellation (New/Optional) 4.17.1 Description This feature is new in RAN13.0. This feature is applicable to cells enabled with WRFD-010691 HSUPA UL Interference Cancellation. With this feature, scheduling is based on Received Total Wideband Power (RTWP) thresholds before and after interference cancellation (IC). This feature also raises the RTWP target value before IC. This can increase the HSUPA throughput of the cell.

4.17.2 Capacity and Performance System Capacity This feature further increases the HSUPA throughput of cells enabled with HSUPA UL Interference Cancellation by around 5 to 15%.

Network Performance 

Impact on network coverage The RTWP threshold after IC remains the same as that before the IC feature is introduced and therefore this feature does not have negative impact on the cell coverage. The neighboring cells, controlled by the RTWP threshold, do not affect the cell coverage either, regardless of whether they are enabled with IC or not.



Impact on network capacity This feature increases the RTWP before IC, thereby causing stronger interference to the neighboring cells. If the neighboring cells are enabled with this feature and the parameters are set to the same value as the serving cell, the neighboring cell capacity will not be affected. If the neighboring cells are not enabled with this feature no matter whether they are enabled with IC or not, the neighboring cell capacity will decrease because of the stronger interference from the serving cell.

It is recommended that this feature be enabled for contiguous areas. The capacity of neighboring cells at the edge of the areas must not be limited.


Issue 06 (2012-11-30)


44



4.17.4 Operation and Maintenance This feature is under license control. It is recommended that this feature be enabled in a number of contiguous cells, whose neighboring cells are not capacity-limited. A new parameter MaxDeltaOfTargetRoT is added to the NodeB command SET MACEPARA. The parameter is used to set the difference between the RTWP thresholds before and after IC and must be set to a proper value to reduce interference to neighboring cells.

4.18 WRFD-020136 Anti-Interference Scheduling for HSUPA (New/Optional) 4.18.1 Description This feature is new in RAN13.0. Sites in commercial networks experience strong and random external uplink interference. This interference significantly reduces HSUPA throughput in the cells of those sites and negatively affects the user experience. Anti-interference Scheduling for HSUPA counteracts this interference, thereby ensuring high HSUPA throughput and improving the user experience. This feature offers more noticeable gains when interference reaches 3 dB or above. With this feature, scheduling is performed on HSUPA UEs based on not only the RTWP of the cell but also the traffic volume of the R99 and HSUPA UEs in the cell with strong uplink interference. As long as the traffic volume remains lower than the guaranteed percentage of uplink load, sufficient resources can be ensured for the R99 and HSUPA UEs even if the RTWP of the cell increases to a very high level. This ensures high HSUPA throughput for the cell. The actual throughput improvement from this feature depends on the strength of the interference and parameter configuration.

4.18.2 Capacity and Performance System Capacity This feature increases the HSUPA capacity of cells experiencing strong interference. Under optimal conditions, this feature can protect the HSUPA capacity of such cells from deteriorating at all.

Network Performance In cells experiencing strong interference, the uplink load increases, leading to decreased coverage. This feature ensures basic coverage by keeping the uplink load under a predefined upper limit.


Issue 06 (2012-11-30)


45



4.18.4 Operation and Maintenance This feature is under license control. New NodeB parameters are added to the command SET MACEPARA: 

OUTERSYSINTERSCHSW: specifies whether to enable Anti-Interference Scheduling for HSUPA.



OWNCELLULLOADRATIO: specifies the guaranteed percentage of uplink load in a cell.



LOADTHRESH4MINULCOV: specifies the uplink load threshold of minimum cell coverage.

To enable this feature, the NodeB parameter OUTERSYSINTERSCHSW must be set to ON. Besides, either of the following conditions must be met: 

The RNC parameter NBMLdcAlgoSwitch must be set to UL_UU_OLC-0 and the parameter NBMUlCacAlgoSelSwitch must be set to ALGORITHM_OFF or ALGORITHM_SECOND.



The RNC parameter NBMCacAlgoSwitch must be set to RTWP_RESIST_DISTURB1.

The previous two RNC parameters can be set by using the command ADD UCELLALGOSWITCH or MOD UCELLALGOSWITCH.

4.19 WRFD-010697 E-DPCCH Boosting (New/Optional) 4.19.1 Description This feature is new in RAN13.0. 3GPP Release 7 introduces E-DCH Dedicated Physical Control Channel (E-DPCCH) Boosting, a prerequisite for uplink 16QAM to increase uplink rates because higher rates require more accurate channel estimation. Before this feature is introduced, the DPCCH is used as the reference channel for channel estimation. The DPCCH, however, cannot meet the requirements of high-speed traffic bursts in the uplink. This is because of the longer delay when outer loop power control adjusts the DPCCH power and the limited maximum Signalto-Interference Ratio (SIR) target value of the DPCCH. The E-DPCCH boosting technique increases the transmit power of the E-DPCCH and uses the E-DPCCH as the reference channel for channel estimation. E-DPCCH Boosting lowers the requirements on the DPCCH SIR, providing more accurate channel estimation and improved reception quality for uplink high-speed services.


Issue 06 (2012-11-30)


46



Network Performance E-DPCCH Boosting helps increase the maximum throughput in the uplink. When used together with uplink 16QAM, E-DPCCH Boosting allows for a maximum uplink rate of 11.5 Mbit/s.

4.19.3 Inter-NE Interface This feature affects messages on the Uu and Iub interfaces. The UE informs the RNC of its E-DPCCH Boosting capabilities using the corresponding indicators in the RRC CONNECTION SETUP COMPLETE message. The NodeB informs the RNC of its E-DPCCH Boosting capabilities using the AUDIT RESPONSE and RESOURCE STATUS INDICATION messages. The RNC informs the UE of whether E-DPCCH Boosting can be used by sending RRC messages such as RADIO BEAR SETUP or ACTIVE SET UPDATE. The RNC also informs the UE of the NodeB decision using the RADIO LINK SETUP REQUEST, RADIO LINK ADDITION REQUEST, and RADIO LINK RECONFIGURATION PREPARE messages.

4.19.4 Operation and Maintenance This feature is under license control. New RNC switches are added: 

CFG_EDPCCH_BOOSTING_SWITCH: added to the parameter CfgSwitch in the command SET UCORRMALGOSWITCH. This switch is used to enable E_DPCCH Boosting at the RNC level.



EDPCCH_BOOSTING: added to the parameter RetryCapability in the command SET UFRC. This switch is used to enable E_DPCCH Boosting retry at the RNC level.



EDPCCH_BOOSTING: added to the parameter HspaPlusSwitch in the commands ADD UCELLALGOSWITCH and MOD UCELLALGOSWITCH. This switch is used to enable E_DPCCH Boosting at the cell level.

A new NodeB parameter BOOST is added to the commands ADD LOCELL and MOD LOCELL to specify whether the local cell supports E_DPCCH Boosting. New counters are added to measure the following items: 

Average number of UEs in the cell applying this feature



Number of RAB setups and releases when applying this feature



Percentage of time, during which this feature is enabled in a cell

4.20 WRFD-010698 HSPA+ Uplink 11.5Mbit/s per User (New/Optional) 4.20.1 Description With the Uplink 16QAM and E-DPCCH Boosting features, the maximum data transmission rate of a single user reaches 11.5 Mbit/s in the uplink.

Issue 06 (2012-11-30)


47



4.20.2 Capacity and Performance This feature is developed to help control feature licensing, and therefore does not affect capacity or performance. For information about the impacts of E-DPCCH Boosting, see section 4.19 "WRFD-010697 E-DPCCH Boosting." Uplink 16QAM is a new feature in RAN12.0, and it is not included in this document.

System Capacity No impact.




4.21 WRFD-010713 Traffic-Based Activation and Deactivation of the Supplementary Carrier In Multicarrier (New/Optional) 4.21.1 Description This feature is new in RAN13.0. The NodeB decides whether to deactivate the secondary carrier of a UE based on the amount of data to be transmitted by the UE and the throughput of the UE. Given a small amount of data and low throughput, the NodeB deactivates the secondary carrier and sends an HS-SCCH order to notify the UE of the deactivation. When the data amount or the throughput becomes high, the NodeB reactivates the secondary carrier and sends an HS-SCCH order to notify the UE of the reactivation.

4.21.2 Capacity and Performance System Capacity In scenarios with a large number of downlink multi-carrier users, such as DC-HSDPA users, and with low traffic in the downlink, this feature increases cell throughput and the number of admitted users in the uplink.

Issue 06 (2012-11-30)


48



Network Performance After the secondary carrier of a UE is deactivated, the UE only needs to demodulate the signals transmitted on the primary carrier, and the transmit power of the UE on the HSDPCCH can be reduced by about 2 dB. Therefore, the uplink load of the cell is lightened. For example, in scenarios with many DC-HSDPA users and low traffic in the downlink, deactivating the secondary carrier can reduce the uplink load of the cell by 5% to 10% when the penetration rate of DC-HSDPA UEs reaches 100%.

4.21.3 Inter-NE Interface This feature affects messages on the Uu interface.

4.21.4 Operation and Maintenance This feature is under license control. A new NodeB parameter SECCELLACTDEASW is added to the command SET MACHSPARA. The parameter is used to specify whether the cell is enabled with the feature. A counter VS.HSDPA.DCCfg.SupCarrierDeact.TimeRatio is added to measure the ratio of the time for traffic-based deactivation of secondary carriers to the time for DC-HSDPA and DCHSDPA+MIMO users existing in primary-carrier cells.

4.22 WRFD-020806 Differentiated Service Based on SPI Weight (Enhanced/Optional) 4.22.1 Description HSPA users share Uu interface resources, CE resources, and Iub interface resources. If these resources cannot provide the maximum bit rate (MBR) for all online HSPA users, differentiated resource allocation can be performed on users according to their user priorities or requested service type (interactive or background). The differentiation in resource allocation is controlled by Scheduling Priority Indicator (SPI) weight. With this feature, the service quality of high-priority users is preferentially ensured and high-priority services are preferentially processed when resources are insufficient. This meets the requirements for both guaranteed bit rate (GBR) and differentiation proportion. This feature enables telecom operators to provide differentiated services. In RAN13.0, SPI weight can also be configured according to UE HS-DSCH categories and EDCH categories or user-subscribed MBR. Telecom operators will have the ability to adopt more flexible promotion strategies to increase revenue.

4.22.2 Capacity and Performance System Capacity The impacts on downlink capacity are as follows: 

Issue 06 (2012-11-30)

Differentiated services in HSDPA scheduling on the Uu interface and flow control on the Iub interface are based on SPI weight. Large-SPI-weight users can have more power and code resources on the Uu interface and higher Iub bandwidth than small-SPI-weight


49



users, thereby achieving higher downlink throughput. If the data source is sufficient for the two types of users with similar conditions (for example, configured with the same GBR and location) -- the ratio of their throughput approximates to the ratio of their SPI weight. 

Increasing the SPI weight of users in weak coverage areas will increase the opportunity of scheduling, reduce the cell resource usage, and decrease the cell throughput. On the contrary, increasing the SPI weight of users in the areas with strong signals will increase the opportunity of scheduling, the cell resource usage, and the cell throughput.

The impacts on uplink capacity are as follows: 

Differentiated services in HSUPA scheduling on the Uu interface, flow control on the Iub interface, and CE scheduling are based on SPI weight. Large-SPI-weight users can have more load resources on the Uu interface, Iub bandwidth, and CE resources than smallSPI-weight users, thereby achieving higher uplink throughput.



If the service rate is not limited in conditions such as user data source, transmit power, user capability, and QoS-related configurations, for example, GBR and MBR, the ratio of uplink throughput approximates to the ratio of SPI weight.

With the same number of users and configuration conditions, the uplink throughput of the system configured with service differentiation is higher than that of the system configured with service fairness.



4.22.4 Operation and Maintenance This feature is under license control. The following RNC commands are added: 

ADD UOPERCAPARATERANGE, MOD UOPERCAPARATERANGE, RMV UOPERCAPARATERANGE, and LST UOPERCAPARATERANGE: used for adding, modifying, deleting, or querying telecom operator-oriented uplink/downlink rate references and rate thresholds.



SET UCAPARATERANGE and LST UCAPARATERANGE: used for setting or querying RNC-oriented uplink/downlink rate references and rate thresholds.

The following RNC parameters are added to the commands ADD UOPERSPIWEIGHT, MOD UOPERSPIWEIGHT and SET USPIWEIGHT: 

RateRangeSPIWeightInd: indicates whether to configure SPI weight by differentiating HSPA rate ranges.



DlRateRange1SPIWeight to DlRateRange10SPIWeight: specify SPI weight for the downlink rate, ranging from 1 to 10.



UlRateRange1SPIWeight to UlRateRange10SPIWeight: specify SPI weight for the uplink rate, ranging from 1 to 10.

To enable this feature, it must be determined in advance whether to distinguish SPI weightbased differentiated services provided by telecom operators.

Issue 06 (2012-11-30)


50



If SPI weight-related parameters have been configured for telecom operators, telecom operator-oriented commands take precedence over RNC-oriented commands. If such parameters are not configured, the RNC-oriented commands can be used.

4.23 WRFD-020132 Web Page Access Acceleration (New/Optional) 4.23.1 Description This feature is new in RAN13.0. Web browsing is one of the most popular data services. Users expect web pages to load quickly, anytime and anywhere. In traditional mobile telecommunication systems, multiple services coexist and equally compete for limited bandwidth resources. Bandwidth is not allocated preferentially to web page access, making it difficult for users to enjoy high-quality, low-delay web browsing. During busy hours, web access is frequently impacted by other services, resulting in prolonged delays in web-page loading. This feature recognizes web page access by using the packet resolving function and then preferentially allocates higher bandwidth to these services. As a result, the load time for web pages decreases and the user experience improves. This feature is applicable to web page access acceleration where HSDPA users take priority over other users and combined services take priority over other services.

4.23.2 Capacity and Performance System Capacity This feature does not affect system capacity; however, if resources are insufficient, it schedules Hypertext Transfer Protocol (HTTP) packets preferentially. The difference between traffic models might slightly affect system capacity.

Network Performance This feature decreases the delay in web-page loading, significantly improving the user experience. The delay of FTP and P2P services, however, is prolonged because this feature increases the round trip time (RTT) of these services. FTP and P2P services are not delaysensitive; therefore, the user experience is subtly affected. This feature adjusts Scheduling Priority Indicator (SPI) weight for different services and affects the differentiated fairness of users accordingly. However, users using the same type of services are not affected. This feature is applicable only when the RNC must be configured with the NIUa board.



Issue 06 (2012-11-30)


51



A new counter is added to measure the number of downlink HTTP data bytes received by the RNC over the Iu-PS interface.

4.24 WRFD-020133 P2P Downloading Rate Control during Busy Hour (New/Optional) 4.24.1 Description This feature is new in RAN13.0. As high-bandwidth mobile telecommunication systems grow rapidly, more and more users use P2P services to download music and video. Due to its high volume and long duration, P2P traffic consumes a large amount of system resources. This significantly increases operating costs and adversely affects the quality of other delay-sensitive services. This feature recognizes the common types of P2P download traffic by using the packet resolving function. When the system load is high, rate restriction rapidly limits the rate of P2P download services to release the occupied resources for other services. When the system load is low, resources for P2P are unrestricted and P2P services are still able to engage in high speed downloads. This allows multiple users and services to fully utilize network resources. This feature is applicable to P2P rate restrictions where HSDPA users take priority over other users and combined services take priority over other services.


Network Performance This feature limits the P2P service rate, significantly improving the user experience of delaysensitive services. This feature increases the delay of P2P services while decreasing the RTT of other services. This feature adjusts SPI weight for different services based on the system congestion status, thereby affecting the differentiated fairness of users accordingly. This feature is applicable only when the RNC must be configured with the NIUa board.


4.24.4 Operation and Maintenance This feature is under license control. A new counter is added to measure the number of downlink P2P data bytes received by the RNC over the Iu-PS interface.

Issue 06 (2012-11-30)


52



4.25 WRFD-020135 Intelligent Inter-Carrier UE Layered Management (New/Optional) 4.25.1 Description This feature is new in RAN13.0. As mobile broadband continues to grow rapidly, more and more people use data cards to access the Internet. Data card services are characterized by long durations and high traffic volumes. They increase operators' profits but also increase network load. Other services from the same carrier may be negatively affected. Using separate carriers for data card services allows efficient utilization of carriers and prevents data card traffic from affecting other services. This helps operators formulate flexible billing policies, develop large-scale data card services, and establish mobile broadband (MBB) brands. This feature allows the UTRAN to intelligently distinguish data cards from UEs in multicarrier scenarios and to separately establish services on different carriers based on priority configurations. This feature works during the access procedure and in connected mode. Intelligent Inter-Carrier UE Layered Management requires operators to allocate different IMSI ranges to UEs and data cards. The RNC determines the terminal type based on the IMSI of the terminal and preset rules. Each carrier is assigned a priority corresponding to a terminal type. During a RAB setup, the RNC performs DRDs and chooses the carrier with the highest priority for the terminal type to access. This achieves the hierarchical assignment of terminals to specific carriers. After RAB setup, periodic DRD based on the terminal type can be performed to hand the terminal over to the highest-priority carrier.

4.25.2 Capacity and Performance System Capacity This feature lets telecom operators develop data card services at attractive prices without compromising the experience of high-end subscribers. When there is a large amount of data card services in the network, this feature increases the system throughput if the carriers are planned and the parameters are set in a reasonable way.

Network Performance The following description assumes that two carriers (carrier1 and carrier2) are used to carry UE services and data card services respectively. This feature impacts network performance in the following ways: 

The RAB setup success rate may decrease. Assume that the parameter is set to allow data card services to be carried only by carrier2 to reduce impact on UE services. If carrier2 denies the admission request for data card services, the services cannot initiate RAB setup attempts on carrier1.



The call drop rate may increase. Assume that R99 services and HSPA services are carried separately on carrier1 and carrier2 before this feature is applied. After this feature is applied, R99 services and HSPA services share one carrier (carrier1), and the high traffic volume of HSPA services will increase the carrier load and pose stronger interference on R99 services, which may increase the call drop rate of R99 services.

Issue 06 (2012-11-30)


53





The DRD-based access success rate may be lower than the non-DRD-based access success rate. UEs are assigned different carriers by blind-handover-based DRD, which slightly decreases the DRD-based access success rate.



The CPU load of the RNC may increase. Since the RNC needs to check the IMSI in each RAB setup procedure and periodic DRD procedure, the CPU load of the RNC increases when the IMSI ranges are complicated.



DPGDRDSwitch: added to the command SET UDRD to specify whether to enable this feature at the RNC level.



DPGDRDSwitch: added to the commands ADD UCELLDR and MOD UCELLDR to specify whether to enable this feature at the cell level.

New RNC commands are added: 

ADD UDEVICETYPEIMSI, RMV UDEVICETYPEIMSI, and LST UDEVICETYPEIMSI: used for adding, deleting and querying the IMSI range for data cards.



ADD UDEVICETYPEPRIOGROUP, MOD UDEVICETYPEPRIOGROUP, RMV UDEVICETYPEPRIOGROUP, and LST UDEVICETYPEPRIOGROUP: used for adding, modifying, deleting, and querying a priority group for a terminal type. The commands set different priorities for different terminal types to achieve traffic steering based on terminal type.

A new RNC parameter is added: 

DPGId: added to the commands ADD UCELLSETUP, ADD UCELLQUICKSETUP, and MOD UCELL to specify the priority of a terminal type in a cell.

4.26 WRFD-020129 Service-Based PS Service Redirection from UMTS to LTE (Trial) (New/Optional) 4.26.1 Description This trial feature is new in RAN13.0. If a UMTS/LTE dual-mode UE establishes services in a UMTS network, this feature allows the RNC to redirect the UE to an LTE network when the UE establishes the PS services only or the CS and PS combined services with CS services completed but PS services not. In a UMTS/LTE hybrid network where PS handover from UMTS to LTE is not supported this feature redirects the UEs that process only PS services from the UMTS network to the LTE network. To enable the UE to be directed from UMTS to LTE, the following conditions must be met:

Issue 06 (2012-11-30)


54





The conditions for PS handover from UMTS to LTE are met.



The UE supports both UMTS and LTE.



The UE is processing only PS services. The RAB assignment message from the SGSN does not indicate that PS services cannot be handed over to the LTE network.

The RNC carries the LTE frequency information in the RRC CONNECTION RELEASE message and directs the UE to the LTE network.


Network Performance This feature provides an alternative to PS handover. In a UMTS/LTE hybrid network that does not support PS handover from UMTS to LTE, this functionality redirects the UEs that process only PS services from the UMTS network to the LTE network. This improves the user experience of PS services.

4.26.3 Inter-NE Interface This feature is associated with messages on the Uu interface. The RNC informs the UE of the LTE carrier information through the RRC CONNECTION RELEASE message. Since a measurement of the LTE network is required before the redirection, this feature is associated with the measurement control message that carries LTE carrier information and the UE measurement report message that carries LTE network signal quality. This feature is also associated with messages on the Iu interface. Through the IE "E-UTRAN Service Handover" in the RAB ASSIGNMENT REQUEST message, the SGSN informs the RNC of the RABs that cannot be established on the LTE side.


HO_LTE_PS_OUT_SWITCH and HO_LTE_SERVICE_PS_OUT_SWITCH: added to the parameter HoSwitch in the command SET UCORRMALGOSWITCH. These two switches are used for outgoing PS handover from UMTS to LTE and service-based handover from UMTS to LTE, respectively.

A new RNC parameter is added: 

EUTRANSHIND: added to the commands ADD UTYPRABBASIC and MOD UTYPRABBASIC. The parameter specifies whether the PS services can be handed over to the LTE network. When EUTRANSHIND is set to HO_TO_EUTRAN_SHOULD_BE_PERFORM, the services can be handed over to the LTE network; otherwise, they cannot be handed over to the LTE network.


Issue 06 (2012-11-30)

Commands for configuring the non-coverage-based UMTS/LTE handover measurement algorithm at the RNC level:


55








4 Impacts of RAN13.0 Features on RAN12.0 −

SET UU2LTEHONCOV: used for specifying settings of the non-coverage-based UMTS/LTE handover measurement algorithm at the RNC level.

−

LST UU2LTEHONCOV: used for querying settings of the non-coverage-based UMTS/LTE handover measurement algorithm at the RNC level.

Commands for configuring LTE cell information: −

ADD ULTECELL: used for adding a new LTE cell in the RNC

−

MOD ULTECELL: used for modifying information about an existing LTE cell in the RNC

−

RMV ULTECELL: used for removing an existing LTE cell from the RNC

−

LST ULTECELL: used for querying an existing LTE cell in the RNC

Commands for configuring LTE neighboring cell information: −

ADD ULTENCELL: used for adding a new LTE neighboring cell in the RNC

−

RMV ULTENCELL: used for removing an existing LTE neighboring cell from the RNC

−

MOD ULTENCELL: used for modifying the neighboring relationship between the RNC cell and the LTE cell in the RNC

−

LST ULTENCELL: used for querying an existing LTE neighboring cell in the RNC

Commands for configuring the non-coverage-based UMTS/LTE handover measurement algorithm at the cell level: −

ADD UCELLU2LTEHONCOV: used for adding settings of the non-coverage-based UMTS/LTE handover measurement algorithm at the cell level.

−

MOD UCELLU2LTEHONCOV: used for modifying settings of the non-coveragebased UMTS/LTE handover measurement algorithm at the cell level.

−

RMV UCELLU2LTEHONCOV: used for removing settings of the non-coveragebased UMTS/LTE handover measurement algorithm at the cell level.

−

LST UCELLU2LTEHONCOV: used for querying settings of the non-coveragebased UMTS/LTE handover measurement algorithm at the cell level.

A new counter is added to measure the number of service-based redirections to LTE through the RRC release procedure.

4.27 WRFD-020130 Videophone Service Restriction (New/Optional) 4.27.1 Description This feature is new in RAN13.0. In restricted areas such as military management areas and sensitive laboratories, the use of videophone (VP) may lead to information leakage. To meet the security requirements in these areas, the RNC supports the prohibition of VP services at the cell level. Implementation of this feature involves the following aspects: 

Prohibiting VP service setup during service establishment



Releasing VP services in the case of an incoming handover when the UE has multiple concurrent services to process

Issue 06 (2012-11-30)


56






4.27.4 Operation and Maintenance This feature is under license control. The following existing RNC switches are used for this feature: 

VPLimitInd in the commands ADD UCELLSETUP, ADD UCELLQUICKSETUP, and MOD UCELLSETUP: used to specify whether to prohibit VP services. When the VPLimitInd parameter is set to TRUE, the VP service prohibition switch is turned on and therefore the VP services of the cell are prohibited.



VPLimitInd in the commands ADD UEXT3GCELL and MOD UEXT3GCELL: used to specify whether a neighboring RNC cell restricts the VP services. When the VPLimitInd parameter is set to TRUE, the neighboring RNC cell prohibits VP services and such services cannot be handed over to this neighboring RNC cell.

No counter has been added for this feature. Users can use the relevant counters introduced in earlier versions for performance measurement.

4.28 WRFD-020131 Optimization of R99 and HSUPA Users Fairness (New/Optional) 4.28.1 Description This feature is new in RAN13.0. In scenarios where R99 users and HSUPA users share the same carrier, this feature enables telecom operators to improve the HSUPA user experience by considering the satisfaction degree of R99 and HSUPA users. The satisfaction degree equals the valid rate divided by the GBR. With the increase in the commercial use of HSUPA, the HSUPA user experience has become more and more important. The original policy dictates that R99 users take precedence over other users. This policy does not lead to an improved HSUPA user experience. Therefore, in scenarios where R99 users and HSUPA users share the same carrier, the throughput of R99 users might be higher than that of HSUPA users with the same priority. This feature enables the periodic comparison of the satisfaction degree between R99 and HSUPA users. The downlink of these R99 users could be R99 or HSDPA. The comparison

Issue 06 (2012-11-30)


57



considers the ratio of actual service rates of users to the GBR values. If the satisfaction degree of R99 users is higher than that of HSUPA users and reaches a certain preset threshold, the rate decrease of high-rate R99 BE services is triggered and the rate increase of low-rate R99 BE services is limited.

4.28.2 Capacity and Performance System Capacity In scenarios where R99 and HSUPA users share the same carrier, this feature increases the throughput of HSUPA BE users. The HSUPA throughput may double in some of these scenarios. Although this feature raises the throughput and satisfaction of HSUPA users, it reduces the average rate of R99 BE users and therefore affects user experience. In addition, this feature slightly reduces the overall uplink throughput of a cell because the uplink power efficiency of R99 users is slightly higher than that of HSUPA users in low-rate scenarios(for example, the user rates are below 100kbit/s). Therefore, operators should enable this feature only when necessary.

Network Performance This feature may reduce CE resource consumption because the HSUPA service with higher CE resource utilization consumes less CE resources than the R99 service at the same rate. When this feature works, the CE resource consumption will decrease. In addition, this feature makes it less likely that a cell is in the load reshuffling (LDR) state and an LDR action is performed. This is because this feature triggers rate reduction for R99 BE users before the cell enters the LDR state.


4.28.4 Operation and Maintenance This feature is under license control. A new RNC switch is added: 

BERateReduceOnFairnessSwitch: added to the commands ADD UCELLALGOSWITCH and MOD UCELLALGOSWITCH. When the parameter is set to ON, the RNC periodically compares the satisfaction degree between R99 and HSUPA users in a cell and triggers the rate decrease of BE services based on load types.

New RNC parameters are added: 

FairnessPeriodTimerLen: added to the command SET ULDCPERIOD to configure the fairness period. Within a fairness period, the RNC makes fairness decisions and determines whether to trigger the rate decrease of R99 BE services to improve user fairness.



Issue 06 (2012-11-30)

FairnessThd: added to the commands ADD UCELLLDM and MOD UCELLLDM to configure the fairness throughput threshold. Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd

58



If the ratio of the satisfaction of R99 BE services to HSUPA BE services exceeds this threshold, the HSUPA services are considered unfair. New counters are added to measure the following items: 

Number of times that HSUPA and PS R99 BE services are in the unfair state in an HSUPA cell



Number of requests for triggering the rate decrease of BE services

4.29 WRFD-020122 Multi-Carrier Switch off Based on QoS (New/Optional) 4.29.1 Description This feature is new in RAN13.0. According to an estimate on power consumption in mobile networks, power consumption and carbon dioxide emission from the UTRAN, especially NodeBs, account for the major part of total consumption. Telecom operators expect that carriers with the same coverage be shut down during low-traffic hours (for example, at midnight) to reduce costs. However, with the rapid development of mobile broadband networks, an increasing number of low ARPU users often stay connected 24 hours a day to download video or audio files. Since their real-time rate is always ensured, the actual network load is still heavy even at midnight, which prevents same-coverage carriers from shutting down. After this feature is introduced, the real-time rates of DCH and high ARPU HSPA users are ensured, whereas only the GBR is ensured for low ARPU HSPA users. As long as the total load based on this requirement is below the specified threshold, carriers with the same coverage can be shut down. For multiple carriers with the same coverage, when the preconfigured time segment begins, the users in the serving carrier (F2 in Figure 4-2) are handed over to the same-coverage neighboring carrier (F1 in Figure 4-2). This can happen only when the available resources plus non-GBR resources of low ARPU HSPA users in F1 meet the load requirements of the real-time rates of DCH and high ARPU HSPA users as well as the GBR of low ARPU HSPA users in F2. Then, the F2 can be shut down. Figure 4-2 takes two carriers (F1 and F2) with the same coverage as an example. Figure 4-2 Two carriers (F1 and F2) with the same coverage

The high ARPU and low ARPU users are configured by telecom operators based on the SPI.

Issue 06 (2012-11-30)


59




Network Performance Although this feature saves power, it may have the following impacts on network performance: 

The risk of call drops and handover failures may increase because UEs must be handed over from a cell by using blind handover before the cell can be shut down.



Low-priority user experience may deteriorate.



Although the real-time rates of high-priority users in a new cell are ensured in the handover decision process, the handover users are scheduled in normal priority order. Therefore, if the number of users continues to increase, the rate of high-priority users may decrease because the number of carriers decreases.


4.29.4 Operation and Maintenance This feature is under license control. New RNC parameters are added to the commands ADD UCELLDYNSHUTDOWN and MOD UCELLDYNSHUTDOWN: 

DynShutDownType: added to configure the QoS-based carrier shutdown switch.



HighPriSPI: added to configure the SPI for high-priority users. The QoS-based carrier shutdown function takes effect only when the GBP measurement switch of both the serving cell and the inter-frequency same-coverage neighboring cell is turned on.

4.30 WRFD-020121 Intelligent Power Management (New/Optional) 4.30.1 Description This feature is new in RAN13.0. This feature introduces Power Supply Unit (PSU) intelligent shutdown. With this feature, certain PSUs can be powered on or off according to the power consumption of the NodeB, thereby reducing power consumption.

Issue 06 (2012-11-30)


60




Network Performance PSU intelligent shutdown reduces NodeB power consumption.


4.30.4 Operation and Maintenance This feature is under license control. This feature is configured on the NodeB. The command SET PSUISS is added on the NodeB side to enable or disable this feature.

4.31 WRFD-02131106 Routing Roaming UEs in Proportion (New/Optional) 4.31.1 Description This feature is new in RAN13.0. Sometimes an RNC is shared by several operators that support the Multi-Operator Core Network (MOCN) and have a roaming agreement with each other. In this case, when UEs of another RNC enter the coverage area of this RNC, this RNC routes these UEs to the CNs of different operators according to the predefined routing proportion. In a shared RNC, roaming relationships can be configured between the operators who share the RNC and other operators who do not. For the UEs of an operator that enter the coverage area of the shared RNC, the allocation proportions among the operators who share the RNC can also be configured. When UEs of other operators roam into the area served by the shared RNC, and the UEs do not support network sharing (as specified in the optional feature WRFD-02131101Carrier Sharing Among Operators), the RNC randomly routes these UEs to a CN if the RNC does not receive the messages carrying IMSI information. If the CN rejects the UE access requests or indicates that CS/PS coordination is required, the CN returns the UE IMSI to the RNC. The RNC then obtains the PLMN from the IMSI and routes the UEs to the CN of the operators who share the RNC according to the predefined roaming relationships and proportions. This feature does not apply to roaming UEs that support network sharing.

Issue 06 (2012-11-30)


61




Network Performance The revenue from roaming services can be fairly allocated between telecom operators because roaming UEs are allocated proportionally.


4.31.4 Operation and Maintenance This feature is under license control. It shares the license with WRFD-021311 MOCN Introduction Package. This feature is configured on the RNC. A new RNC command ADD UROAMMAP is added to configure the roaming relationships and proportions. A new counter VS.ROAM.MOCN.NUM is added to measure the number of times that roaming UEs successfully register in the MOCN of local telecom operators who have signed the roaming agreement.

Issue 06 (2012-11-30)


62



4.32 WRFD-050402 IP Transmission Introduction on Iub Interface (Enhanced/Optional) 4.32.1 Description This feature is enhanced in RAN13.0. RNC internal firewall and NodeB internal firewall are added. The NodeB internal firewall, added to the FE interface of the NodeB, protects the Iub interface of the NodeB in the IP transport network from cyber attacks. The NodeB internal firewall inspects the incoming IP data, including the maintenance, control plane, and user plane data. The NodeB internal firewall provides the following functions: 

White-listing: With this function, only data sent from allowed peer IP addresses, at allowed ports, and in allowed protocols can access the NodeB. White-listing can also implement the ping denial function. White-listing enables the NodeB to discard Internet Control Message Protocol (ICMP) packets. White-listing applies to the maintenance, control plane, and user plane data of 3900 series base stations and to the maintenance and control plane data of BTS3812E, BTS3812AE, and DBS3800.



Safeguard against Address Resolution Protocol (ARP) flooding and ICMP flooding



Broadcast-message speed limiting

The RNC internal firewall includes the following functions: 



The RNC internal firewall scans all incoming IP data over the O&M interface and provides the following functions: −

IP address filter: This function only allows IP data from permissible IP addresses and network segments.

−

Safeguard against ICMP ping, IP fragmentation, low TTL, smurf, and DDoS attacks.

−

Safeguard against TCP sequence prediction and SYN flood attacks.

The RNC internal firewall scans all incoming IP data over the Iub interface and provides the following functions: −

Intelligent white-listing: With this function, only data sent from allowed peer IP addresses, at allowed ports, and in allowed protocols can access the RNC.

−

Safeguard against ARP flooding and ICMP flooding

−

Interworking Function (IWF) filtering

−

Broadcast-message speed limiting


Network Performance The internal firewall is disabled by default and therefore has no impact on system upgrades or capacity expansions. The packet transmission speed limiting function is always enabled and therefore has no impact on system upgrade.

Issue 06 (2012-11-30)


63




4.32.4 Operation and Maintenance This feature is under license control. New RNC commands are added: 

SET IPGUARD and LST IPGUARD: used for configuring policies for safeguards against IP attacks.



DSP INVALIDPKTINFO: used for querying logs related to illegal packet.

New NodeB commands are added: 

ADD ACL, RMV ACL, and LST ACL: used for configuring an ACL.



ADD ACLRULE, RMV ACLRULE, and LST ACLRULE: used for configuring ACL rules.



ADD PACKETFILTER, RMV PACKETFILTER, and DSP PACKETFILTER: used for configuring parameters related to packet filters. A packet filter binds an ACL to a physical port so that IP packets received on the physical port can be filtered by the ACL.

4.33 WRFD-050409 IP Transmission Introduction on Iu Interface (Enhanced/Optional) This feature is enhanced in RAN13.0. RNC internal firewall is added. For details about the impact of RNC internal firewall, see section 4.32 "WRFD-050402 IP Transmission Introduction on Iub Interface (Enhanced/Optional)."

4.34 WRFD-050410 IP Transmission Introduction on Iur Interface (Enhanced/Optional) This feature is enhanced in RAN13.0. RNC internal firewall is added. For details about the impact of RNC internal firewall, see section 4.32 "WRFD-050402 IP Transmission Introduction on Iub Interface (Enhanced/Optional)."

4.35 WRFD-021350 Independent Demodulation of Signals from Multiple RRUs in One Cell (New/Optional) 4.35.1 Description This feature is new in RAN13.0.

Issue 06 (2012-11-30)


64



Independent demodulation of signals from multiple RRUs in one cell enables the signals from multiple RRUs to be demodulated independently and combined within a BBU. This feature effectively reduces the number of handovers between cells. In the uplink, the NodeB performs independent demodulation and combination of signals from multiple RRUs within a BBU. In the downlink, the NodeB multiplexes the signals of a cell to multiple RRUs. Each cell is split into multiple coverage areas, and each coverage area is independently covered by an RRU. Multiple RRUs belonging to one cell possess the same scrambling code.

Because baseband combination technology is used, combining signals from multiple RRUs does not introduce background noise or influence uplink receive sensitivity. This feature is suitable for coverage in special locations with high-speed motion such as highways, railroad tracks, or racetracks. Base stations configured with TX diversity or MIMO cannot use this feature. When using this feature, the following features cannot be supported: 

WRFD-010209 4-Antenna Receive Diversity



WRFD-010203 Transmit Diversity



WRFD-010684 2x2 MIMO



WRFD-010692 HSUPA FDE



WRFD-010701 Uplink Enhanced CELL_FACH



WRFD-021308 Extended Cell Coverage up to 200km


Network Performance This feature introduces independent demodulation of signals from multiple RRUs in one cell. Different RRU coverage areas in the same cell can reduce the number of handovers between cells and increase cell capacity and throughput. Multiple RRU coverage areas can also flexibly form linear coverage areas. As a result, a relatively small number of cells can meet the coverage requirements of transportation routes. Issue 06 (2012-11-30)


65



This feature multiplexes downlink signals on multiple RRUs for transmission. This is known as baseband multiplexing. The WBBPd board supports a maximum of six two-way receive RRUs in one cell, and the WBBPb board supports a maximum of three two-way receive RRUs in one cell.


4.35.4 Operation and Maintenance This feature is under license control. This feature is configured on the NodeB. An enumeration value MULTIRRU_SECTOR is added to the parameter SECT in the NodeB commands ADD SEC and ADD LOCELL.

4.36 WRFD-020134 Push to Talk (New/Optional) 4.36.1 Description This feature is new in RAN13.0. Push to Talk (PTT) allows for conversations on half-duplex and point-to-point or point-tomultipoint communication lines. A PTT connection starts instantly without ringing after a subscriber simply presses a key. In addition, a caller can speak to a group of people by pressing only one button. Therefore, PTT is characterized by quick call setup and convenient group communication. The following figure shows an application of PTT in a UMTS network. Figure 4-3 Application of PTT in a UMTS network

This feature is a part of end-to-end PTT solution. PTT needs support from the UE, RAN, CN, and PTT servers. In this feature, the RAN identifies PTT services and implements technologies to reduce the delay of PTT services. PTT services consist of a start-up process and a call setup process: 

Issue 06 (2012-11-30)

Start-up process


66



After a UE starts the PTT client, the start-up process begins. The process includes the following actions: −

PTT UE registration In this process, a UE registers itself on the PTT server by message exchange.

−

PTT UE identification In this process, the RNC identifies the PTT UE when receiving a RAB ASSIGNMENT message with special QoS parameters and then keeps the UE in the CELL_PCH/URA_PCH state.



Call setup process After a subscriber presses the PTT button, the call setup process begins. The network sets up channels for PTT services. The delay of PTT call setup should be short. To reduce end-to-end delay, the following technologies are used in the call setup process. −

Always On The RNC retains the UE in the CELL_PCH/URA_PCH state when there is no data to transmit, that is, the UE is always active in the RNC. The CN also has a mechanism to keep UEs constantly active. The Always On state allows the CN and the RNC to perform fast scheduling on the UEs without re-establishing the RRC connection or performing the activation procedure.

−

PCH to DCH (P2D) direct state transition A PTT UE directly switches from the CELL_PCH/URA_PCH state to the CELL_DCH state. This reduces PTT transmission delay and improves PTT call setup performance.

−

Preferred paging The RNC prioritizes PTT paging over the paging of other lower priority applications to improve PTT call setup delay performance.

−

Early Reception and Transmission The RAN supports the reception of PTT user data on the E-DCH before receiving the CELL UPDATE CONFIRM RESPONSE message from the PTT UE. To reduce delay, the RAN also supports sending messages to the PTT UE over the HS-DSCH without waiting for the CELL UPDATE CONFIRM RESPONSE message.

−

Fast L1 synchronization The TS 25.331 in 3GPP Release 6 introduces the "Post-verification period" IE to indicate whether a UE uses fast L1 synchronization. This IE is included in the RADIO BEARER RECONFIGURATION and CELL UPDATE CONFIRM messages. Fast L1 synchronization allows PTT UEs to perform uplink and downlink L1 synchronization concurrently, reducing PTT call setup delay for PTT UEs in the CELL_PCH/URA_PCH state at the start of the call.

−

Scheduling PTT services are carried over HSPA. The NodeB schedules PTT as VoIP in the downlink, and the NodeB applies the non-scheduling policy for PTT in the uplink.

−

E-PCH Enhanced PCH enables signaling exchange between PTT UEs in the CELL_PCH state and the RAN. This reduces cell update signaling for UEs to switch from CELL_PCH to CELL_DCH, and further reduces the initial call setup delay of UEs in the CELL_PCH state.

Issue 06 (2012-11-30)


67



4.36.2 Capacity and Performance System Capacity According to an estimate based on the TU3 channel, each cell supports approximately 80 PTT UEs using point-to-point services.

Network Performance PTT UEs carried on HSPA each uses SF32 in the uplink (consuming one CE) and SF256 in the downlink.


4.36.4 Operation and Maintenance This feature is under license control. This feature is configured on the RNC. The RNC parameters are modified as follows: 

An enumeration value CFG_PTT_SWITCH is added to the parameter CfgSwitch in the command SET UCORRMALGOSWITCH, used for enabling the PTT feature.



An enumeration value PTT is added to the parameter TrafficClass in the command ADD UOPERUSERGBR, used for configuring the GBR of PTT services.

New counters are added to measure the following items: 

Number of PTT service setup attempts



Number of PTT service release attempts



Number of successful PTT service setups



Number of successful PTT service releases



Average number of UEs in the CELL_DCH/CELL_FACH/CELL_PCH/URA_PCH state in a cell



Number of PTT paging attempts



Number of successful PTT paging attempts



Number of abnormal PTT service releases



Number of PTT UE state transitions



Uplink and downlink data volumes of PTT UEs in a cell

4.37 WRFD-012001 RNC offload (Trial) (New/Optional) 4.37.1 Description This trial feature is new in RAN13.0.

Issue 06 (2012-11-30)


68



This feature enables the RNC to send PS data directly to the Internet through an offload Gi interface instead of through the Iu-PS interface, SGSN, backbone, GGSN and Gi interface. This reduces the traffic passing through the SGSN, GGSN and backbone and shortens the transmission delay. This reduces the cost of deploying the backbone, SGSN, and GGSN.

In RAN13.0, the RNC offload adopts the Network Address Translation (NAT) technique. In a real network, the downlink PS data is the main part of the PS data. NAT enables the RNC to offload some downlink PS data by controlling the uplink PS data. The RNC analyzes the uplink PS data and selects the data that allows RNC offload. NAT changes the source IP address of uplink PS data to the external IP address of the offload Gi interface before the RNC sends the selected uplink PS data. This enables the downlink PS data to directly arrive at the RNC without passing through the GGSN. Users can configure the usage scope of this feature by specifying the IMSI range, cell ID, service type, Access Point Name (APN), and destination IP address. This feature is configured on the RNC and only the FG2c and GOUc boards support the offload Gi interface.


Network Performance This feature shortens the end-to-end transmission delay by connecting the RNC to the Internet over the offload Gi interface directly.

4.37.3 Inter-NE Interface This feature does not affect the Iub, Iur, or Iu signaling. The offload Gi interface is a standard IP-based interface.

4.37.4 Operation and Maintenance This feature is under license control. This feature is configured on the RNC. A new RNC switch is added: 

Issue 06 (2012-11-30)

OffloadSwitch: added to the commands ADD UCELLALGOSWITCH and MOD UCELLALGOSWITCH to be used as a cell-level switch for RNC offload.


69




ADD UOFFLOAD, MOD UOFFLOAD, RMV UOFFLOAD, and LST UOFFLOAD: used for adding, modifying, deleting, and querying the basic parameters related to RNC offload.



ADD UOFFLOADRAB, MOD UOFFLOADRAB, RMV UOFFLOADRAB, and LST UOFFLOADRAB: used for adding, modifying, deleting, and querying the RAB types that RNC offload needs to be performed on.



ADD UOFFLOADIMSI, RMV UOFFLOADIMSI, and LST UOFFLOADIMSI: used for adding, deleting, and querying the IMSI ranges that allow RNC offload.



ADD UUNOFFLOADIP, RMV UUNOFFLOADIP, and LST UUNOFFLOADIP: used for adding, deleting, and querying the host IP addresses or host network segments that prohibit RNC offload.



ADD UOFFLOADIMEITAC, RMV UOFFLOADIMEITAC, and LST UOFFLOADIMEITAC: used for adding, deleting, and querying the type approval code (TAC) for RNC offload.

4.38 WRFD-030010 CQI Adjustment Based on Dynamic BLER Target (New/Optional) 4.38.1 Description This feature is new in RAN13.0. The channel quality of live networks fluctuates constantly. To achieve the highest possible downlink throughput, an appropriate Block Error Rate (BLER) target is required. Without this feature, the NodeB determines a transmission block size (TBS) based on the channel quality indicator (CQI) reported by the UE, system resources, and the transport format and resource combination (TFRC) policy. If the reported CQI and related conditions remain the same, the NodeB does not change the TBS because it does not consider the everchanging radio environments. The constant changes in radio environments, caused by multipath effects and UE mobility, lead to fluctuating channel quality. Under these circumstances, choosing a TBS based on the reported CQI makes it difficult to always achieve the optimum downlink throughput. With this feature, the NodeB monitors the channel quality fluctuations for HSDPA users in a cell in real time and dynamically selects a proper BLER target based on the monitoring result. The NodeB then uses the BLER target to adjust the CQI reported by the UE. Based on the adjusted CQI, the NodeB determines an appropriate TBS to achieve higher downlink throughput for HSDPA users and higher cell throughput. The required BLER target may be high in some radio environments; therefore this feature is not recommended for networks that limit the BLER target. This feature requires that both the network and UE support HSDPA. In RAN13.0, this feature is applicable only to non-MIMO users.

Issue 06 (2012-11-30)


70



4.38.2 Capacity and Performance System Capacity This feature increases the downlink throughput for HSDPA users and cells by up to 10%.

Network Performance Calculation for adjusting the CQI increases the downlink load of the NodeB DSP slightly.


4.38.4 Operation and Maintenance This feature is under license control. A new NodeB switch CQI_ADJ_BY_DYN_BLER is added to the parameter CQIADJALGOFNONCON in the SET MACHSPARA command. To enable this feature, this switch must be turned on. No counter has been added for this feature.

4.39 WRFD-030011 MIMO Prime (New/Optional) 4.39.1 Description This feature is new in RAN13.0. MIMO Prime is a Huawei proprietary performance algorithm. MIMO Prime uses dualtransmission RF modules to greatly increase spectrum utilization and network capacity. MIMO Prime is based on virtual antenna mapping (VAM), which applies matrix processing to the original signal before sending it out over the antennas. Each original signal is split into two and transmitted by two antennas with balanced power. The two split signals, however, have a certain phase difference at the receive end, which weakens the signal strength when they are combined again. To solve this problem, MIMO Prime automatically performs phase adjustment based on the signal environment, which increases the UE receive quality and consequently its throughput. Figure 4-4 shows the principles of MIMO Prime.

Issue 06 (2012-11-30)


71



Figure 4-4 Principles of MIMO Prime

MIMO Prime is applicable to non-MIMO cells. MIMO Prime does not have any special requirements for the UE and is applicable to various services including HSDPA and 64QAM. Furthermore, it does not affect the performance of traditional UEs.

4.39.2 Capacity and Performance System Capacity MIMO Prime increases the throughput of cells in which MIMO has not been implemented. The increase in the overall cell throughput depends on the cell traffic model, which includes the UE number, behavior, and location. The feature gain is noticeable for UEs in medium or bad radio conditions.



4.39.4 Operation and Maintenance This feature is under license control. A new NodeB parameter MIMOPRIMESW is added to the command SET MACHSPARA. To enable this feature, this parameter must be set to OPEN. Before this feature can be activated, the parameter VAM in the NodeB command ADD LOCELL must be set to TRUE. No counter has been added for this feature.

Issue 06 (2012-11-30)


72



4.40 MRFD-221802 GSM and UMTS Dynamic Spectrum Sharing(UMTS) (New/Optional) 4.40.1 Description This feature is a new multi-mode feature in RAN13.0. GSM and UMTS Dynamic Spectrum Sharing is hereafter referred to as DSS. To achieve high spectrum efficiency, this feature enables dynamic sharing of spectrum resources between GSM and UMTS networks based on service loads. When the GSM service load is below the specified threshold, some idle GSM spectrum resources can be allocated to the UMTS network. When the GSM traffic load is above the specified threshold, these spectrum resources can be taken back by the GSM network.

4.40.2 Capacity and Performance System Capacity DSS between GSM and UMTS increases network throughput and reduces the total cost of data services because UMTS has higher spectrum efficiency than GSM.

Network Performance Dynamically allocating GSM spectrum resources to UMTS causes the GSM spectrum to become narrower and the GSM KPIs to deteriorate.


4.40.4 Operation and Maintenance The DSS feature is under license control of both GSM and UMTS sides. The DSS is effective only when both GSM and UMTS are enabled with the DSS feature. New RNC commands are added as follows: 

New commands SET UDSSPARA and LST UDSSPARA are added to set and query DSS-related parameters, respectively.

New RNC parameters are added as follows: 

DSSFlag: added to the commands ADD UNODEB and MOD UNODEB. This parameter is configured on the RNC side to specify whether the NodeB supports DSS.



DSSFlag: added to the commands ADD UCELLSETUP, MOD UCELLSETUP, and ADD UCELLQUICKSETUP. This parameter specifies whether the cell supports DSS.



DSSSmallCovMaxTxPower: added to the commands ADD UCELLSETUP, ADD UCELLQUICKSETUP, and MOD UCELL. This parameter specifies the maximum transmit power of the DSS cell.



DSSSmallCovPCPICHPower: added to the commands ADD UPCPICH, MOD UPCPICH, ADD UCELLQUICKSETUP, and MOD UCELL. This parameter specifies the maximum transmit power of the PCPICH in the DSS cell.

Issue 06 (2012-11-30)


73



On the UMTS side, new counters are added to measure the number of times and the duration that a DSS cell is activated or deactivated in the NodeB. GUIs are added to the M2000 for managing DSS cell relationships and DSS-enabled NodeBs in a contiguous area. The implementation of the DSS on the GSM side is not described in this document. For details, see the corresponding GSM documentation. To enable the DSS, the GSM, UMTS, and M2000 nodes must be operated and configured separately. For details, see the RAN Feature Activation Guide. The GU power sharing function needs to be disabled for the DSS carriers.

4.41 MRFD-221703 2.0MHz Central Frequency point separation between GSM and UMTS mode(UMTS) (New/Optional) 4.41.1 Description This feature is a new multi-mode feature in RAN13.0. The propagation performance of the 900 MHz or 850 MHz band is better than that of the 2100 MHz band, but the spectrum resources of the 900 MHz or 850 MHz band are much less than those of the 2100 MHz band. Because of this, a conflict exists between the increasing demand for GSM services and the limited spectrum resources. Some telecom operators are unable to reserve the 5 MHz bandwidth from the 850 MHz or 900 MHz band for UMTS services. To maintain competitiveness, operators still expect to deploy new UMTS services on the 850 MHz or 900 MHz band. They use a non-standard bandwidth such as 3.8 MHz for UMTS carriers and 2.0 MHz frequency spacing between GSM and UMTS carriers. This method may cause network KPIs to deteriorate. For these operators, the competitive advantages brought by using non-standard bandwidth and small frequency spacing can compensate for the lower KPIs. Figure 4-5 shows the application of 3.8 MHz bandwidth for the UMTS network and 2.0 MHz frequency spacing shared by GSM and UMTS networks. Figure 4-5 Network application of the feature

Issue 06 (2012-11-30)


74



With this new feature, the GSM network interferes with the uplink of the UMTS network. To mitigate any adverse effect of neighboring GSM frequencies on UMTS frequencies, the Huawei NodeB provides a 3.8 MHz bandwidth filter. This feature does not support HSPA+ services.

4.41.2 Capacity and Performance System Capacity This feature improves network throughput because UMTS has higher spectrum efficiency than GSM. Instead of providing 5 MHz bandwidth dedicated to UMTS services, this feature allocates the 3.8 MHz bandwidth to UMTS and reserves 1.2 MHz bandwidth for GSM. This helps expand GSM network capacity.

Network Performance This feature reduces the frequency spacing between GSM and UMTS networks and has the following impacts on network performance: 

The throughput of UMTS HSPA services decreases because the GSM and UMTS networks interfere with each other and the UMTS network uses a 3.8 MHz bandwidth filter.



The throughput of GSM EDGE services decreases because UMTS interferes with GSM. The mean opinion scores (MOSs) of GSM and UMTS decrease.



In scenarios with limited spectrum resources, KPIs of the GSM network may deteriorate because the 3.8 MHz GSM bandwidth is allocated to UMTS.


4.41.4 Operation and Maintenance This feature is a multi-mode feature and is under license control of both GSM and UMTS sides. The value range of the parameter FMBWH in the command SET FREQBWH is extended on the NodeB side. The implementation of this feature on the GSM side is not described in this document. For details, see the corresponding GSM documentation. To enable this feature, the GSM BSC and UMTS NodeB must be operated and configured separately. For details, see the RAN Feature Activation Guide.

Issue 06 (2012-11-30)


75


A Acronyms and Abbreviations

A

Acronyms and Abbreviations

A ACL

Access Control List

APN

Access Point Name

ARP

Address Resolution Protocol

ARPU

Average Revenue Per User

ATM

Asynchronous Transfer Mode

B BAM

Back Administration Module

BCCH

Broadcast Control Channel

BE

Best Effort

BHCA

Busy Hour Call Attempt

BSC

Base Station Controller

C CE

Channel Element

CME

Configuration Management Express

CN

Core Network

CPC

Continuous Packet Connection

CPU

Central Processing Unit

CQI

Channel Quality Indicator

D DCCC

Dynamic Channel Configuration Control

DCH

Dedicated Channel

DPCCH

Dedicated Physical Control Channel

DPUe

Data Processing Unit REV:e

Issue 06 (2012-11-30)


76



DRD

Directed Retry Decision

DRX

Discontinuous Reception

DSCP

DiffServ Code Point

DTX

Discontinuous Transmission

E E-AI

Extended AI

EBBC

HBBU Enhanced Baseband processing Card

EBBI

Enhanced BaseBand processing and Interface unit

E-DCH

Enhanced Dedicated Channel

EDGE

Enhanced Data rates for GSM Evolution

E-DPCCH

E-DCH Dedicated Physical Control Channel

E-DPDCH

E-DCH Dedicated Physical Data Channel

E-FACH

Enhanced CELL_FACH

E-RNTI

E-DCH Radio Network Temporary Identifier

F FACH

Forward Access Channel

FE

Fast Ethernet

FG2c

12-port FE or 4-port electronic GE interface unit REV:c

G GA

General Availability

GE

Gigabit Ethernet

GOUc

4-port packet over GE Optical interface Unit REV:c

GSM

Global System for Mobile communications

GUI

Graphic User Interface

H HBBI

NodeB HSDPA Baseband processing and Interface unit

HBBU

NodeB HSDPA Supported Baseband Unit

HDLP

High-Level Data Link Control

HSDPA

High Speed Downlink Packet Access

HS-DPCCH

High Speed Dedicated Physical Control Channel

HS-DSCH

High Speed Downlink Shared Channel

HSPA

High Speed Packet Access

HS-SCCH

High Speed Shared Control Channel

Issue 06 (2012-11-30)


77



HSUPA

High Speed Uplink Packet Access

HTTP

Hypertext Transfer Protocol

HULP

NodeB HSDPA supported Uplink Processing Unit

I ICMP

Internet Control Message Protocol

IMSI

International Mobile Subscriber Identity

IP

Internet Protocol

Iu

Iu Interface

Iub

Iub Interface

Iu-PS

Iu interface of Packet Service

Iur

Iur Interface

K KPI

Key Performance Index

L L1

Layer 1 (physical layer)

LDR

Load Reshuffling

LMT

Local Maintenance Terminal

LTE

Long Term Evolution

M MAC

Media Access Control

MBR

Maximum Bit Rate

MIMO

Multi-Input Multi-Output

MML

Man Machine Language

MOCN

Multi-Operator Core Network

MOS

Mean Opinion Score

N NBAP

Node B Application Part

NIUa

Smart Service Unit REV:a.

O OM

Operation and Maintenance

OMC

Operation and Maintenance Center

OMUa

Operation and Maintenance Unit REV:a

P

Issue 06 (2012-11-30)


78



P2P

point to point service

PCH

Paging Channel

PCPICH

Physical Common Pilot Channel

PLMN

Public Land Mobile Network

PMU

Power and Environment Monitoring Unit

PRACH

Packet Random Access Channel

PSU

Power Supply Unit

PTT

Push to Talk

Q QoS

Quality of Service

R R99

Release 1999

RAB

Radio Access Bearer

RACH

Random Access Channel

RAN

Radio Access Network

RB

Radio Bearer

RET

Remote Electrical Tilt

RNC

Radio Network Controller

RRC

Radio Resource Control

RTWP

Received Total Wideband Power

S SGSN

Serving GPRS Support Node

SIR

Signal-to-Interference Ratio

SPI

Scheduling Priority Indicator

SRB

Signaling Radio Bearer

T TBS

Transport Block Size

TFRC

Transport Format and Resource Combination

TTI

Transmission Timing Interval

U UE

User Equipment

UMTS

Universal Mobile Telecommunications System

URA

User Registration Area

Issue 06 (2012-11-30)


79



USB

Universal Serial Bus

UTRAN

Universal Terrestrial Radio Access Network

Uu

Uu Interface

V VAM

Virtual Antenna Mapping

VoIP

Voice over IP

VP

Videophone

W WBBPb

WCDMA BaseBand Process unit

WCDMA

Wideband Code Division Multiple Access

Issue 06 (2012-11-30)


80

RAN13.0 Network Impact Report 06(PDF)-En

Recommend Documents