RAN15.0 Network Impact Report Draft A(PDF)-EN.pdf

Network Impact Report RAN15.0

Feature Parameter Description

Issue Draft A

Date 2013-01-30

HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2013. 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 the warranty of any kind, express or implied.

Huawei Technologies Co., Ltd.

Address: Huawei Industrial Base

Bantian, Longgang

Shenzhen 518129

People's Republic of China

Website: http://www.huawei.com

Email: [email protected]

http://www.huawei.com/

mailto:[email protected]

RAN15.0

Network Impact Report 1 About This Document

Draft A (2013-01-30) Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd.

ii

Contents

1 About This Document .............................................................................................................. 1-1

1.1 Purpose ......................................................................................................................................... 1-1

1.2 Intended Audience......................................................................................................................... 1-1

1.3 Change History .............................................................................................................................. 1-1

1.4 Document Versions ....................................................................................................................... 1-1

2 General Impact........................................................................................................................... 2-1

2.1 Version Requirements ................................................................................................................... 2-1

2.2 Capacity and Performance ............................................................................................................ 2-1

2.2.1 RNC ...................................................................................................................................... 2-1

2.2.2 NodeB ................................................................................................................................... 2-4

2.2.3 M2000 ................................................................................................................................... 2-4

2.3 Hardware ....................................................................................................................................... 2-4

2.3.1 RNC ...................................................................................................................................... 2-4

2.3.2 NodeB ................................................................................................................................... 2-7

2.3.3 M2000 ................................................................................................................................... 2-8

2.4 Implementation .............................................................................................................................. 2-8

2.4.1 Upgrade Path ....................................................................................................................... 2-8

2.4.2 Upgrade from RAN14.0 to RAN15.0 .................................................................................... 2-8

2.4.3 Upgrade from RAN13.0 to RAN15.0 .................................................................................... 2-8

2.5 License .......................................................................................................................................... 2-8

2.5.1 Changes in License Control Items ....................................................................................... 2-8

2.5.2 Changes in License Control Modes ................................................................................... 2-11

2.6 Inter-NE Interfaces ...................................................................................................................... 2-17

2.7 Operation and Maintenance ........................................................................................................ 2-18

2.8 Other NEs .................................................................................................................................... 2-18

3 Summary of Feature Impacts ................................................................................................. 3-1

4 Impacts of RAN15.0 Features on RAN14.0 ......................................................................... 4-1

4.1 WRFD-141101 System Improvement for RAN15.0 (New/Basic) .................................................. 4-1

4.1.1 Feature Description .............................................................................................................. 4-1

4.1.2 System Capacity and Network Performance ........................................................................ 4-1

4.1.3 NEs ....................................................................................................................................... 4-1

4.1.4 Hardware .............................................................................................................................. 4-1

4.1.5 Inter-NE Interfaces ............................................................................................................... 4-1

4.1.6 Operation and Maintenance ................................................................................................. 4-1

4.1.7 Impact on Other Features ..................................................................................................... 4-2

4.2 WRFD-150230 DPCH Pilot Power Adjustment (New/Basic) ........................................................ 4-2

4.2.1 Feature Description .............................................................................................................. 4-2

4.2.2 System Capacity and Network Performance ........................................................................ 4-2

RAN15.0




iii

4.2.3 NEs ....................................................................................................................................... 4-2

4.2.4 Hardware .............................................................................................................................. 4-2

4.2.5 Inter-NE Interfaces ............................................................................................................... 4-2



4.3 WRFD-141102 RNC User Plane and Control Plane Static Sharing (New/Basic) ......................... 4-4

4.3.1 Description ............................................................................................................................ 4-4

4.3.2 Capacity and Performance ................................................................................................... 4-5

4.3.3 Impact on NEs ...................................................................................................................... 4-5

4.3.4 Impact on Hardware ............................................................................................................. 4-6

4.3.5 Inter-NE Interface ................................................................................................................. 4-6



4.4 WRFD-141103 Automatic NodeB and Cell Allocation in the RNC(New/Basic)............................. 4-7

4.4.1 Description ............................................................................................................................ 4-7

4.4.2 Capacity and Performance ................................................................................................... 4-8

4.4.3 Impact on NEs ...................................................................................................................... 4-8

4.4.4 Impact on Hardware ............................................................................................................. 4-8

4.4.5 Inter-NE Interface ................................................................................................................. 4-8


4.4.7 Impact on Other Features ................................................................................................... 4-10

4.5 WRFD-010101 Compliance with 3GPP Specifications (Enhanced /Basic) ................................ 4-10

4.5.1 Feature Description ............................................................................................................ 4-10

4.5.2 System Capacity and Network Performance ...................................................................... 4-11

4.5.3 NEs ..................................................................................................................................... 4-11

4.5.4 Hardware ............................................................................................................................ 4-11

4.5.5 Inter-NE Interfaces ............................................................................................................. 4-11

4.5.6 Operation and Maintenance ............................................................................................... 4-11


4.6 WRFD-031103 NodeB Self-test (Enhanced /Basic) .................................................................... 4-11


4.6.2 System Capacity and Network Performance ...................................................................... 4-12

4.6.3 NEs ..................................................................................................................................... 4-12

4.6.4 Hardware ............................................................................................................................ 4-12

4.6.5 Inter-NE Interfaces ............................................................................................................. 4-12



4.7 MRFD-210101 System Redundancy (Enhanced /Basic) ............................................................ 4-12

4.7.1 Description .......................................................................................................................... 4-12

4.7.2 Capacity and Performance ................................................................................................. 4-14

4.7.3 Impact on NEs .................................................................................................................... 4-14

4.7.4 Impact on Hardware ........................................................................................................... 4-14

RAN15.0




iv

4.7.5 Inter-NE Interface ............................................................................................................... 4-14



4.8 WRFD-141201 RNC User Plane and Control Plane Dynamic Sharing (New/Optional) ............. 4-15

4.8.1 Description .......................................................................................................................... 4-15

4.8.2 Capacity and Performance ................................................................................................. 4-15

4.8.3 Impact on NEs .................................................................................................................... 4-16

4.8.4 Impact on Hardware ........................................................................................................... 4-16




4.9 WRFD-150201 Macro & Micro Co-carrier Uplink Interference Control (New/Optional) .............. 4-16


4.9.2 System Capacity and Network Performance (for Scenarios Where Some Cells Operate at

the Same Frequency Band) ......................................................................................................... 4-19

4.9.3 System Capacity and Network Performance (for Scenarios Where All Cells Operate at the

Same Frequency Band) ............................................................................................................... 4-21

4.9.4 NEs ..................................................................................................................................... 4-22

4.9.5 Hardware ............................................................................................................................ 4-22




4.10 WRFD-15020101 Macro & Micro Joint Inter-frequency Redirection (New/Optional) ............... 4-24

4.10.1 Feature Description .......................................................................................................... 4-24

4.10.2 System Capacity and Network Performance .................................................................... 4-24

4.10.3 NEs ................................................................................................................................... 4-24

4.10.4 Hardware .......................................................................................................................... 4-24

4.10.5 Inter-NE Interface ............................................................................................................. 4-24

4.10.6 Operation and Maintenance ............................................................................................. 4-24

4.10.7 Impact on Other Features ................................................................................................. 4-26

4.11 WRFD-15020102 Macro & Micro Joint Inter-frequency Handover (New/Optional) .................. 4-26



4.11.3 NEs ................................................................................................................................... 4-26

4.11.4 Hardware .......................................................................................................................... 4-26




4.12 WRFD-15020103 Micro Cell Dynamic Rx Sensitivity Control (New/Optional) ......................... 4-29



4.12.3 NEs ................................................................................................................................... 4-30

RAN15.0




v

4.12.4 Hardware .......................................................................................................................... 4-30




4.13 WRFD-150204 Platinum User Prioritizing (New/Optional)........................................................ 4-33



4.13.3 NEs ................................................................................................................................... 4-34

4.13.4 Hardware .......................................................................................................................... 4-34

4.13.5 Inter-NE Interfaces ........................................................................................................... 4-34


4.13.7 Impact on other Features ................................................................................................. 4-37

4.14 WRFD-150205 Layered Paging in Idle Mode (New/Optional) .................................................. 4-38



4.14.3 NEs ................................................................................................................................... 4-38

4.14.4 Hardware .......................................................................................................................... 4-38




4.15 WRFD-150206 Turbo IC (New/Optional) .................................................................................. 4-41

4.15.1 Description ........................................................................................................................ 4-41


4.15.3 NEs ................................................................................................................................... 4-41

4.15.4 Hardware .......................................................................................................................... 4-42



4.15.7 Related Features .............................................................................................................. 4-45

4.16 WRFD-150207 4C-HSDPA (New/Optional) .............................................................................. 4-45



4.16.3 NEs ................................................................................................................................... 4-46

4.16.4 Hardware .......................................................................................................................... 4-46




4.17 WRFD-150208 Flexible DC/DB-HSDPA (New/Optional) .......................................................... 4-53



4.17.3 NEs ................................................................................................................................... 4-54

4.17.4 Hardware .......................................................................................................................... 4-54


RAN15.0




vi



4.18 WRFD-150209 DB-HSDPA (New/Optional) .............................................................................. 4-58



4.18.3 NEs ................................................................................................................................... 4-59

4.18.4 Hardware .......................................................................................................................... 4-59




4.19 WRFD-150211 RNC in Pool Load Sharing (New/Optional) ...................................................... 4-63



4.19.3 NEs ................................................................................................................................... 4-65

4.19.4 Hardware .......................................................................................................................... 4-65




4.20 WRFD-150212 RNC in Pool Node Redundancy (New/Optional) ............................................. 4-71



4.20.3 NEs ................................................................................................................................... 4-73

4.20.4 Hardware .......................................................................................................................... 4-73




4.21 WRFD-150240 RNC in Pool Multiple Logical RNCs (New/Optional) ........................................ 4-78



4.21.3 NEs ................................................................................................................................... 4-78

4.21.4 Hardware .......................................................................................................................... 4-78




4.22 WRFD-150213 MOCN Independent Iub Transmission Resource Allocation (New/Optional) .. 4-80



4.22.3 NEs ................................................................................................................................... 4-80

4.22.4 Hardware .......................................................................................................................... 4-80




RAN15.0




vii

4.23 WRFD-150214 MOCN Independent CE Resource Allocation (New/Optional) ......................... 4-82



4.23.3 NEs ................................................................................................................................... 4-82

4.23.4 Hardware .......................................................................................................................... 4-83




4.24 WRFD-150215 SRVCC from LTE to UMTS with PS Handover (New/Optional) ....................... 4-83



4.24.3 NEs ................................................................................................................................... 4-84

4.24.4 Hardware .......................................................................................................................... 4-84




4.25 WRFD-150216 Load Based PS Redirection from UMTS to LTE (New/Optional) ..................... 4-85



4.25.3 NEs ................................................................................................................................... 4-86

4.25.4 Hardware .......................................................................................................................... 4-86




4.26 WRFD-150217 Load Based PS Handover from UMTS to LTE (New/Optional) ....................... 4-88



4.26.3 NEs ................................................................................................................................... 4-88

4.26.4 Hardware .......................................................................................................................... 4-89




4.27 WRFD-150219 Coverage Based PS Redirection from UMTS to LTE (New/Optional) ............. 4-91



4.27.3 NEs ................................................................................................................................... 4-91

4.27.4 Hardware .......................................................................................................................... 4-91



4.27.7 Impact on Other Features ............................................................................................... 4-108

4.28 WRFD-150220 Coverage Based PS Handover from UMTS to LTE (New/Optional) .............. 4-108

4.28.1 Feature Description ........................................................................................................ 4-108

RAN15.0




viii

4.28.2 System Capacity and Network Performance .................................................................. 4-108

4.28.3 NEs ................................................................................................................................. 4-108

4.28.4 Hardware ........................................................................................................................ 4-108

4.28.5 Inter-NE Interfaces ......................................................................................................... 4-109

4.28.6 Operation and Maintenance ........................................................................................... 4-109


4.29 WRFD-150222 HSUPA Time Division Scheduling (New/Optional) ......................................... 4-124



4.29.3 NEs ................................................................................................................................. 4-124

4.29.4 Hardware ........................................................................................................................ 4-125



4.30 WRFD-150231 RIM Based UMTS Target Cell Selection for LTE (New/Optional) .................. 4-126



4.30.3 NEs ................................................................................................................................. 4-126

4.30.4 Hardware ........................................................................................................................ 4-127




4.31 WRFD-150216 Load Based PS Redirection from UMTS to LTE (New/Optional) ................... 4-128



4.31.3 NEs ................................................................................................................................. 4-128

4.31.4 Hardware ........................................................................................................................ 4-128




4.32 WRFD-150232 Multiband Direct Retry Based on UE Location (New/Optional) ..................... 4-130



4.32.3 NEs ................................................................................................................................. 4-131

4.32.4 Hardware ........................................................................................................................ 4-131




4.33 WRFD-150233 Differentiated Service Based on Resource Reservation (New/Optional) ...... 4-134



4.33.3 NEs ................................................................................................................................. 4-134

4.33.4 Hardware ........................................................................................................................ 4-135

RAN15.0




ix




4.34 WRFD-150235 DPCH Maximum Power Restriction (New/Optional) ...................................... 4-137


4.34.2 System Capacity and Network Impact ........................................................................... 4-137

4.34.3 NEs ................................................................................................................................. 4-137

4.34.4 Hardware ........................................................................................................................ 4-137




4.35 WRFD-150236 Load Based Dynamic Adjustment of PCPICH (New/Optional) ...................... 4-139



4.35.3 NEs ................................................................................................................................. 4-140

4.35.4 Hardware ........................................................................................................................ 4-140




4.36 WRFD-140225 Narrowband Interference Suppression (New/Optional) ................................. 4-143



4.36.3 NEs ................................................................................................................................. 4-143

4.36.4 Hardware ........................................................................................................................ 4-143




4.37 MRFD-211901/ MRFD-221901 Multi-RAT Carrier Joint Shutdown(Optional/New) ................ 4-145



4.37.3 NEs ................................................................................................................................. 4-146

4.37.4 Hardware ........................................................................................................................ 4-146




4.38 WRFD-010612 HSUPA Introduction Package (Enhanced/Optional) ...................................... 4-149

4.39 WRFD-01061209 HSUPA HARQ and Fast UL Scheduling in NodeB (Enhanced/Optional) .. 4-149

4.39.2 Capacity and Performance ............................................................................................. 4-149

4.40 WRFD-010696 DC-HSDPA (Enhanced/Optional) ................................................................... 4-152



4.40.3 NEs ................................................................................................................................. 4-152

RAN15.0




x

4.40.4 Hardware ........................................................................................................................ 4-153




4.41 WRFD-010703 HSPA+Downlink 84Mbit/s per User (Enhanced/Optional) ............................. 4-153



4.41.3 NEs ................................................................................................................................. 4-153

4.41.4 Hardware ........................................................................................................................ 4-154




4.42 WRFD-010712 Adaptive Configuration of Traffic Channel Power offset for HSUPA

(Enhanced/Optional) ....................................................................................................................... 4-154



4.42.3 NEs ................................................................................................................................. 4-155

4.42.4 Hardware ........................................................................................................................ 4-155




4.43 WRFD-020119 Multi-Carrier Switch off Based on Power Backup (Enhanced/Optional) ........ 4-156


4.43.2 NEs ................................................................................................................................. 4-156

4.43.3 Hardware ........................................................................................................................ 4-156




4.44 WRFD-020129 PS Service Redirection from UMTS to LTE (Enhanced/Optional) ................. 4-161



4.44.3 NEs ................................................................................................................................. 4-161

4.44.4 Hardware ........................................................................................................................ 4-161




4.45 WRFD-140218 Service-Based PS Handover from UMTS to LTE (Enhanced/Optional) ........ 4-165



4.45.3 NEs ................................................................................................................................. 4-165

4.45.4 Hardware ........................................................................................................................ 4-166


RAN15.0




xi



4.46 WRFD-140219 Micro NodeB Self-Planning (Enhanced/Optional) .......................................... 4-167

4.46.1 Introduction ..................................................................................................................... 4-167

4.46.2 Capacity and Performance ............................................................................................. 4-167

4.46.3 NEs ................................................................................................................................. 4-167

4.46.4 Hardware ........................................................................................................................ 4-167

4.46.5 Inter-NE Interface ........................................................................................................... 4-168



4.47 MRFD-211501/MRFD-221501/MRFD-231501 IP-Based Multi-mode Co-Transmission on BS side

(Optional/Enhanced) ....................................................................................................................... 4-168



4.47.3 NEs ................................................................................................................................. 4-169

4.47.4 Hardware ........................................................................................................................ 4-169




4.48 WRFD-150223 4C-HSDPA+MIMO (New/Try) ......................................................................... 4-170



4.48.3 NEs ................................................................................................................................. 4-171

4.48.4 Hardware ........................................................................................................................ 4-171




4.49 WRFD-150224 HSPA+Downlink 168 Mbit/s per User (New/Try)............................................ 4-174



4.49.3 NEs ................................................................................................................................. 4-174

4.49.4 Hardware ........................................................................................................................ 4-175




4.50 WRFD-150227 DB-HSDPA+MIMO (New/Try) ........................................................................ 4-176



4.50.3 NEs ................................................................................................................................. 4-176

4.50.4 Hardware ........................................................................................................................ 4-176



RAN15.0




xii


5 Glossary ...................................................................................................................................... 5-1

6 References .................................................................................................................................. 6-1

RAN15.0




1-1

1 About This Document

1.1 Purpose

This document describes the impacts of new and enhanced RAN15.0 features on RAN14.0 and provides information that network planning personnel and operation and maintenance (O&M) personnel need to prepare for upgrades to RAN15.0.

Information in this document is for reference only and is subject to change during the development of this new release.

1.2 Intended Audience

This document is intended for:

Network planning engineers

System engineers

Network operators

1.3 Change History

Changes between document versions are cumulative. The latest document version contains all the changes in earlier versions.

1.4 Document Versions

Draft A (2013-01-30)

Draft A (2013-01-30)

This is a draft for RAN15.0.

RAN15.0

Network Impact Report 2 General Impact



2-1

2 General Impact

2.1 Version Requirements

Table 2-1 lists the products versions required for RAN15.0.

Table 2-1 Product versions required for RAN15.0

Product Version

RNC BSC6900 V900R015C00

BSC6910 V900R015C00

NodeB 3812 series base stations:

BTS3812E: BTS3812E V100R015C00

BTS3812A: BTS3812A V100R015C00

BTS3812AE: BTS3812AE V100R015C00

DBS3800: DBS3800 V100R015C00

3900 series base stations:

BTS3900: BTS3900 WCDMA V200R015C00

BTS3900A: BTS3900A WCDMA V200R015C00

BTS3900C: BTS3900C WCDMA V200R015C00

BTS3900L: BTS3900L WCDMA V200R015C00

BTS3900AL: BTS3900AL WCDMA V200R015C00

BTS3902E: BTS3902E WCDMA V200R015C00

BTS3803E: BTS3803E WCDMA V200R015C00

DBS3900: DBS3900 WCDMA V200R015C00

DBS3900 (supporting the WBBPf board): DBS3900 WCDMA V200R015C00

M2000 iManager M2000 V200R013C00

CME iManager M2000-CME V200R013C00

2.2 Capacity and Performance

2.2.1 RNC

The RNC models for RAN15.0 are BSC6900 and BSC6910.

BSC6900

Resource optimization on the user plane and control plane

During service access, to improve the RNC reliability and utilization of resources on the control plane and user

plane, the DSP for carrying user-plane services and SPU sub-system for carrying control-plane services are

optimized in terms of the following aspects:

RAN15.0




2-2

− Resource management on the control plane and user plane: Resources on the control plane and user plane are

allocated based on the capacity of each SPU sub-system rather than centralized management of the MPU.

− DSP selection algorithm based on load balancing: The DSP is selected based on the actual CPU usage rather

than the GBR capability consumption.

− Inter-subrack load sharing algorithm: Load sharing in the control-plane and user-plane resource pools is

performed based on the physical subracks rather than the logical subracks managed by the MPU. The inter-

subrack load on the user plane is calculated using the average DSP CPU usage rather than the average GBR

capability consumption and average DSP CPU usage.

− The load sharing threshold for the inter-subrack user-plane resource pool is set to 50% by default so that

loads are evenly allocated among the subracks.

− Resource management on the user plane does not depend on GBR admission.

Impact on Capacity and Performance

− The CPU usage of the MPU sub-system declines.

− The DPU CPU usage slightly increases and its absolute value does not exceed 2%.

− The SPU's or DSP's CPU usage changes when the SPU or DPU and the bound MPU are installed in different

physical subracks because inter-subrack load sharing is performed based on the physical subrack. If both DPUb

and DPUe boards are installed in a physical subrack, the DSP loads will be evenly distributed between the DPUb

and DPUe boards.

− If the DSP CPU usage is low, service access failures have no correlation with the failure of GBR capability

admission.

BSC6910

The BSC6910, a new-generation BSC product, is introduced in RAN15.0. Compared with the BSC6900, the BSC6910 has a higher system capacity and improved networking capability.

Improved system capacity

RAN15.0 BSC6910 uses new cabinets, subracks, and boards to greatly improve capacity specifications, as listed in Table 2-2.

Table 2-2 RAN15.0 BSC6910 capacity specifications

Item Specifications

BHCA (K) 64,000

BHCA (K) (SMS included) 70,000

PS (UL+DL) throughput (Mbit/s) 120,000

CS traffic volume (Erlang) 250,000

NOTE

In Table 2-2:

RAN15.0




2-3

BHCA and CS traffic volume can be reached only in the Huawei traffic model for smartphones.

PS throughput can be reached only in the Huawei high-PS traffic model.

CS and PS capacities cannot reach the maximum specifications simultaneously.

The BSC6910 can reach its maximum capacity specifications only when it is configured with two cabinets and six subracks. The actual BSC6910 capacity varies depending on the traffic model and hardware configurations.

The following describes the maximum BSC6910 capacity specifications in typical traffic models:

Huawei high-PS traffic model

This traffic model is applicable to networks where data cards account for a large proportion of the total number of admitted terminals. Table 2-3 provides the BSC6910 capacity specifications in the Huawei high-PS traffic model.

Table 2-3 BSC6910 capacity specifications in the Huawei high-PS traffic model

Online Users

CS Traffic Volume (Erlang)

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

BHCA (K) BHCA (K) (SMS Included)

Configuration

1,380,000 5700 59,500 4300 5600 1 cabinet and 3 subracks

2,760,000 11,400 120,000 8600 11,400 2 cabinets and 6 subracks

NOTE

In the Huawei high-PS traffic model, the BHCA, CS traffic volume, and PS throughput can reach the maximum specifications simultaneously.

Huawei traffic model for smartphones

In this traffic model, the average PS throughput is low and the number of calls is high. Table 2-4 provides the BSC6910 capacity specifications in the Huawei traffic model for smartphones.

Table 2-4 BSC6910 capacity specifications in the Huawei traffic model for smartphones

Number of Users

CS Traffic Volume (Erlang)

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

BHCA (K) BHCA (K) (SMS Included)

Configuration

3,830,000 124,000 4500 31,900 34,900 1 cabinet and 3 subracks

7,660,000 250,000 9100 64,000 70,000 2 cabinets and 6 subracks

NOTE

In the Huawei traffic model for smartphones, the BHCA, CS traffic volume, and PS throughput can reach the maximum specifications simultaneously.

Improved networking capability

The following table compares the BSC6910 with the BSC6900 in terms of networking capability.

RAN15.0




2-4

Networking Specifications BSC6900 BSC6910

Number of NodeBs 3060 10,000

Number of cells 5100 20,000

Number of MGW/MSC servers 32 64

Number of SGSNs 32 64

Number of neighboring RNCs 50 128

Number of neighboring GSM cells 163,200 64,000

Number of neighboring LTE cells 163,200 64,000

Number of intra-frequency neighboring UMTS cells 239,700 64,000

Number of inter-frequency neighboring UMTS cells 326,400 64,000

NOTE

For detailed specifications of the BSC6910, see BSC6910 Product Description.

2.2.2 NodeB

The capacity and performance specifications of the RAN15.0 NodeB are the same as those of the RAN14.0 NodeB except that the maximum number of HSUPA users served by a WBBPd2 board of the RAN15.0 NodeB increases from 96 to 114.

2.2.3 M2000

Compared with iManager M2000 V200R012, iManager M2000 V200R013C00 improves management capability as follows:

For the M2000 multi-server load-sharing system (SLS) running on ATAE servers, the maximum management capability increases from 800 equivalent network elements (NEs) (40,000 cells) to 1200 equivalent NEs (60,000 cells).

For the M2000 running on Sun servers, the maximum management capability remains unchanged (50,000 UMTS cells).

For the M2000 running on HP servers, the maximum management capability remains unchanged. The M2000 manages a maximum of 280 equivalent NEs (14,000 cells).

For the M2000 running on IBM servers, the maximum management capability remains unchanged. The M2000 manages a maximum of 70 equivalent NEs (350 cells).

The performance specifications of iManager M2000 V200R013C00 are the same as those of iManager M2000 V200R012.

2.3 Hardware

2.3.1 RNC

BSC6900

Compared with RAN14.0 BSC6900, RAN15.0 BSC6900 has a new interface board, as described in Table 2-5.

RAN15.0




2-5

Table 2-5 New BSC6900 board

Board Type Board Name Full Name Function

Interface processing board

PEUc 32-port Packet over E1/T1 interface Unit REV:c

Provides 32 channels of IP over E1/T1.

Extracts clock signals and sends the signals to the GCUa/GCGa board.

BSC6910

The BSC6910 is introduced in RAN15.0.

Cabinets

The BSC6910 uses the Huawei N68E-22 cabinet or earthquake-proof N68E-21-N cabinet. The BSC6910 cabinets are not interchangeable with the BSC6900 cabinets because each subrack in a BSC6910 cabinet is independently powered.

Subracks

The BSC6910 uses new-generation Platform of Advanced Radio Controller REV:b (PARCb) subracks. The PARCb subrack has a standard width of 19 inches, which complies with IEC60297. The height of each subrack is 12 U. Boards are installed on the front and rear sides of the backplane, which is positioned in the center of the subrack. The PARCb subrack provides powerful power supply and heat dissipation capabilities for the BSC6910. The PARCb subrack differs from the PARC subrack used in the BSC6900 in terms of power supply, cable layout, and heat dissipation methods. For details, see BSC6910 Hardware Description for RAN15.0.

Boards

For RAN15.0, BSC6910 uses the same boards as BSC6900. BSC6910 also uses additional boards exclusively.

Table 2-6 describes the boards used by both RAN15.0 BSC6910 and RAN15.0 BSC6900.

Table 2-6 Boards used by both BSC6910 and BSC6900

Board Type Board Name

Full Name Function

Switching processing board

SCUb GE Switching network and Control Unit REV:b

Provides MAC/GE switching and enables the convergence of ATM and IP networks. (MAC is short for Media Access Control and ATM is short for asynchronous transfer mode.)

Provides data switching channels.

Provides system-level or subrack-level configuration and maintenance.

Distributes clock signals for the BSC6910 and BSC6900.

Clock processing board

GCUa General Clock Unit REV:a

Obtains the system clock, performs the functions of phase-lock and holdover, and provides clock signals.

Unlike the GCUa board, the GCGa board can receive and process GPS signals.

GCGa General Clock unit with GPS REV:a

RAN15.0




2-6


Full Name Function


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

Provides 12 FE electrical ports or 4 GE electrical ports.

Supports IP over FE/GE.

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

Provides 4 GE optical ports.

Supports IP over GE.

AOUc 4-port ATM over channelized Optical STM-1/OC-3 interface Unit REV:c

Provides four ATM over channelized STM-1/OC-3 optical ports.

Supports ATM over E1/T1 over SDH/SONET.

Provides 252 E1s or 336 T1s.


UOIc 8-port ATM over Unchannelized Optical STM-1/OC-3 Interface unit REV:c

Provides eight unchannelized STM-1/OC-3c optical ports.

Supports ATM over SDH/SONET.


Table 2-7 describes the boards used exclusively by RAN15.0 BSC6910. For details about the boards, see BSC6910 Hardware Description for RAN15.0. BSC6910 boards are the general processing board, O&M board, service identification board, interface processing board, switching processing board, and clock processing board.

Table 2-7 New BSC6910 boards


Full Name Function

General processing board

EGPUa Evolved General Processing Unit REV:a

Manages user plane and control plane resource pools.

Processes user plane and control plane services for GSM and UMTS.

O&M board EOMUa Evolved Operation and Maintenance Unit REV:a

Performs configuration management, performance management, fault management, security management, and loading management for the BSC6910.

Works as the O&M agent of the LMT/M2000 to provide the BSC6910 O&M interface for the LMT/M2000 and to enable communication between the BSC6910 and LMT/M2000.

Provides the interface for web-based online help.

RAN15.0




2-7


Full Name Function

ESAUa Evolved Service Aware Unit REV:a

Collects call history record (CHR) data and pre-processes the collected data.

Filters and summarizes BSC6910 raw data required by the Nastar and uploads the pre-processed data to the Nastar through the M2000 for analysis.

Service identification board

ENIUa Evolved Network Intelligence Unit REV:a

Provides the service identification function and works with service processing boards to schedule services based on priorities.


EXOUa Evolved 2-port 10GE Optical interface Unit REV:a

Provides two 10 GE optical ports.

Supports IP over GE.

2.3.2 NodeB

RAN15.0 NodeB includes the following hardware changes:

No new boards

Added a NodeB model, as listed in Table 2-8

Added hardware modules, as listed in Table 2-9

Table 2-8 New NodeB model

Change Type NodeB Model NodeB Name

New Micro base station BTS3803E

Table 2-9 New hardware modules

Change Type Module Type Module Name

New RF module MRFUV2

New RF module RRU3841




New RF module WRFUa

New AAS AAU3910

RAN15.0




2-8

2.3.3 M2000

The hardware of iManager M2000 V200R013C00 is the same as that of iManager M2000 V200R012.

2.4 Implementation

2.4.1 Upgrade Path

In live networks, RAN13.0 and RAN14.0 can be upgraded to RAN15.0.

2.4.2 Upgrade from RAN14.0 to RAN15.0

Before performing an upgrade from RAN14.0 to RAN15.0, ensure that all required hardware has been installed and you have obtained the licenses that allow the required network capacity.

Perform the upgrade in the following order:

1. Upgrade the M2000 to iManager M2000 V200R013C00.

2. Upgrade the CME to iManager M2000-CMEV200R013C00.

3. Upgrade the BSC6900 to BSC6900 V900R015C00.

4. Upgrade the NodeB to a corresponding RAN15.0 version listed in Table 2-1.

NOTE

The BSC6910 is introduced in RAN15.0 and therefore no upgrade from RAN14.0 is involved.

2.4.3 Upgrade from RAN13.0 to RAN15.0

Before performing an upgrade from RAN13.0 to RAN15.0, ensure that all required hardware has been installed and you have obtained the licenses that allow the required network capacity.

Perform the upgrade in the following order:

1. Upgrade the M2000 to iManager M2000 V200R013C00.

2. Upgrade the CME to iManager M2000-CMEV200R013C00.

3. Upgrade the BSC6900 to BSC6900 V900R015C00.

4. Upgrade the NodeB to a corresponding RAN15.0 version listed in Table 2-1.

NOTE

The BSC6910 is introduced in RAN15.0 and therefore no upgrade from RAN13.0 is involved.

2.5 License

2.5.1 Changes in License Control Items

Compared with RAN14.0, RAN15.0 incorporates the following changes in license control items:

Deleted the license control items described in Table 2-10.

Table 2-10 License control items deleted from RAN15.0

Feature ID

Feature Name License Change

WRFD-050422

Dynamic Bandwidth Control of Iub IP

This feature is incorporated into the WRFD-050402 IP Transmission Introduction on Iub Interface feature.

RAN15.0




2-9

Feature ID

Feature Name License Change

WRFD-050106

AAL2 Switching Based Hub Node B

This feature is incorporated into the WRFD-050105 ATM Switching Based Hub NodeB feature. In addition, WRFD-050105 ATM Switching Based Hub NodeB is renamed WRFD-050105 ATM/AAL2 Switching Based Hub Node B.

WRFD-011501

PDCP Header Compression (RoHC)

This feature is incorporated into the WRFD-010617 VoIP over HSPA/HSPA+ feature.

WRFD-020802

OTDOA Based LCS This feature has been changed from an optional feature to a basic feature.

WRFD-020307

Video Telephony Fallback to Speech (AMR) for Inter-RAT HO

This feature is incorporated into the following features:

WRFD-020303 Inter-RAT Handover Based on Coverage

WRFD-020305 Inter-RAT Handover Based on Service

WRFD-020306 Inter-RAT Handover Based on Load

WRFD-021200 HCS (Hierarchical Cell Structure)

WRFD-020104

Intra Frequency Load Balance

This feature has been changed from an optional feature to a basic feature.

Added license control items for the RAN15.0 new features described in Table 2-11.

Table 2-11 License control items added for RAN15.0 new features

Feature ID Feature Name License Configured on…

License Control Item Sales Unit

WRFD-141201

RNC User Plane and Control Plane Dynamic Sharing

RNC RNC User Plane and Control Plane Dynamic Sharing

RNC

WRFD-150201

Macro & Micro Co-carrier Uplink Interference Control

RNC Macro & Micro Co-carrier Uplink Interference Control (per Cell)

per Cell

WRFD-150204

Platinum User Prioritizing

RNC Platinum User Prioritizing (per Erl)

Platinum User Prioritizing (per kbps)

Erl+Mbps

WRFD-150205

Layered Paging in Idle Mode

RNC Layered Paging in Idle mode (per Erl)

Layered Paging in Idle mode (per kbps)

Erl+Mbps

WRFD-150206

Turbo IC NodeB Turbo IC Function (per Cell) per Cell

WRFD-150207

4C-HSDPA NodeB 4C-HSDPA Function (per Cell)

per Cell

RAN15.0




2-10



WRFD-150208

Flexible DC/DB-HSDPA

NodeB Flexible DC/DB-HSDPA Function (per NodeB)

per NodeB

WRFD-150209

DB-HSDPA NodeB DB-HSDPA Function (per Cell)

per Cell

WRFD-150211

RNC in Pool Load Sharing

RNC RNC in Pool Load Sharing (per Active User)

per 500 Active user

WRFD-150212

RNC in Pool Node Redundancy

RNC RNC in Pool Node Redundancy (per NodeB)

per NodeB

WRFD-150240

RNC in Pool Multiple Logical RNCs

RNC RNC in Pool Multiple Logic RNCs (per RNC)

per Logical RNC

WRFD-150213

MOCN Independent Iub Transmission Resource Allocation

RNC MOCN Independent Iub Transmission Resource Allocation (per NodeB)

per NodeB

WRFD-150214

MOCN Independent CE Resource Allocation

RNC MOCN CE resource independent allocate (per cell)

per Cell

WRFD-150215

SRVCC from LTE to UMTS with PS Handover

RNC SRVCC from LTE to UMTS with PS Handover (per Erl)

SRVCC from LTE to UMTS with PS Handover (per kbps)

Erl+Mbps

WRFD-150216

Load Based PS Redirection from UMTS to LTE

RNC Load based PS Redirection from UMTS to LTE (per kbps)

Mbps

WRFD-150217

Load Based PS Handover from UMTS to LTE

RNC Load based PS Handover from UMTS to LTE (per kbps)

Mbps

WRFD-150219

Coverage Based PS Redirection from UMTS to LTE

RNC Coverage based PS Redirection from UMTS to LTE (per kbps)

Mbps

WRFD-150220

Coverage Based PS Handover from UMTS to LTE

RNC Coverage based PS Handover from UMTS to LTE (per kbps)

Mbps

WRFD-150222

HSUPA Time Division Scheduling

NodeB HSUPA Time Division Scheduling Function (per Cell)

per Cell

WRFD-150231

RIM Based UMTS Target Cell Selection for LTE

RNC RIM based UMTS Target Cell Selection for LTE (per cell)

per Cell

WRFD-150232

Multiband Direct Retry Based on UE Location

RNC Multiband Direct Retry Based on UE Location (per Cell)

per Cell

RAN15.0




2-11



WRFD-150233

Differentiated Service Based on Resource Reservation

RNC Differentiated Service based on Resource Reservation (per kbps)

Mbps

WRFD-150235

DPCH Maximum Power Restriction

NodeB DPCH Maximum Power Restriction (per Cell)

per Cell

WRFD-150236

Load Based Dynamic Adjustment of PCPICH

RNC Load Based Dynamic Adjustment of PCPICH (per cell)

per Cell

WRFD-140225

Narrowband Interference Suppression

NodeB Narrowband Interference Suppression (per Cell)

per Cell

Added license control items for the RAN15.0 optional features, changed from RAN14.0 try features, as described in Table 2-12.

Table 2-12 License control items added for RAN15.0 optional features changed from RAN14.0 try features



WRFD-140222 Adaptive Adjustment of HSUPA Small Target Retransmissions

RNC Adaptive Adjustment of HSUPA Small Target Retransmissions (per kbps)

Mbps

WRFD-140226 Fast Return from UMTS to LTE

RNC Fast Return from UMTS to LTE (per Erl)

Fast Return from UMTS to LTE (per kbps)

Erl+Mbps

2.5.2 Changes in License Control Modes

Table 2-13 and Table 2-14 describe the changes in the RNC and NodeB license control modes, respectively.

Table 2-13 Changes in the RNC license control modes

Feature ID

License Configured on…

Feature Name Change Description

None RNC Capacity redundancy

1. CS calls:

If the consumed CS Erlangs reach 105% of the licensed value, the RNC rejects the access requests of CS calls except emergency calls. Obtain sufficient CS Erlang licenses to solve this

RAN15.0




2-12

Feature ID



problem.

2. PS services:

The RNC reduces the data rates of admitted PS users if the following condition is met:

PS throughput in use + Throughput converted from the CS Erlangs in use > (Licensed PS throughput + Throughput converted from licensed CS Erlangs) x 105%

However, the rate reduction affects user experience. Obtain sufficient PS throughput licenses to solve this problem.

3. HSDPA/HSUPA services:

The RNC reduces the data rates of admitted HSDPA/HSUPA users if the following condition is met:

HSDPA/HSUPA throughput in use > Licensed HSDPA/HSUPA throughput x 105%

However, the rate reduction affects user experience. Obtain sufficient HSDPA/HSUPA throughput licenses to solve this problem.

WRFD-010652

RNC SRB over HSDPA

In the DSP LICUSAGE command output, the license information has been changed from LQW1HSDPA14 SRB over HSDPA (per Mbps) to DLQW1HSDPA14RES SRB over HSDPA (per Mbps).

In the LST LICENSE command output, the license information has been changed from SRB over HSDPA=ON to SRB over HSDPA (per kbps)=xxx.

To enable the SRB over HSDPA feature together with the MOCN or RAN Sharing feature, you need to set the SRBoverHSDPA parameter in the SET LICENSE command.

When the license expires, it enters a 60-day grace period. When the grace period elapses, PS services will be limited to use the SRB over HSDPA feature.

WRFD-010685

RNC Downlink Enhanced L2

In the DSP LICUSAGE command output, the license information has been changed from LQW1DLE01 Downlink Enhanced L2 (per Mbps) to LQW1DLE01RES Downlink Enhanced L2 (per Mbps).

In the LST LICENSE command output, the license information has been changed from Downlink Enhanced L2=ON to Downlink Enhanced L2 (per kbps)=xxxx.

RAN15.0




2-13

Feature ID



To enable the Downlink Enhanced L2 feature together with the MOCN or RAN Sharing feature, you need to set the DownlinkEnhancedL2 parameter in the SET LICENSE command.

When the license expires, it enters a 60-day grace period. When the grace period elapses, PS services will be limited to use the Downlink Enhanced L2 feature.

WRFD-020806

RNC Differentiated Service Based on SPI Weight

In the DSP LICUSAGE command output, the license information has been changed from LQW1DSSPI01 Differentiated Service Based on SPI Weight (per Mbps) to LQW1DSSPI01RES Differentiated Service Based on SPI Weight (per Mbps).

In the LST LICENSE command output, the license information has been changed from Differentiated Service Based on SPI Weight =ON to Differentiated Service Based on SPI Weight (per kbps)=xxxx.

To enable the Differentiated Service Based on SPI Weight feature together with the MOCN or RAN Sharing feature, you need to set the DifferServiceonSPI parameter in the SET LICENSE command.

When the license expires, it enters a 60-day grace period. When the grace period elapses, PS services will be limited to use the Differentiated Service Based on SPI Weight feature.

WRFD-020132

RNC Web Browsing Acceleration

In the DSP LICUSAGE command output, the license information has been changed from LQW1DSSPI01 Web Browsing Acceleration (per PS Active User) to LQW1WPAA01 Web Browsing Acceleration (per PS Active User).

In the LST LICENSE command output, the license information has been changed from Web Browsing Acceleration=ON to Web Browsing Acceleration (per PS Active User)=xxxx.

To enable the Web Browsing Acceleration feature together with the MOCN or RAN Sharing feature, you need to set the WebPSActiveUsers parameter in the SET LICENSE command.

When the license expires, it enters a 60-day grace period. When the grace period elapses, PS services will be limited to use the Web

RAN15.0




2-14

Feature ID



Browsing Acceleration feature.

WRFD-020133

RNC P2P Downloading Rate Control during Busy Hour

In the DSP LICUSAGE command output, the license information has been changed from LQW1P2PRR01 P2P Rate Control (per PS Active User) to LQW1WPAA01 P2P Rate Control (per PS Active User).

In the LST LICENSE command output, the license information has been changed from P2P Rate Control=ON to P2P Rate Control (per PS Active User)=xxxx.

To enable the P2P Downloading Rate Control during Busy Hour feature together with the MOCN or RAN Sharing feature, you need to set the P2PPSActiveUsers parameter in the SET LICENSE command.

When the license expires, it enters a 60-day grace period. When the grace period elapses, PS services will be limited to use the P2P Downloading Rate Control during Busy Hour feature.

WRFD-020123

RNC TCP Accelerator In the DSP LICUSAGE command output, the license information has been changed from LQW1TCPACC01 TCP Accelerator (per Mbps) to LQW1TCPACC01RES TCP Accelerator (per Mbps).

In the LST LICENSE command output, the license information has been changed from TCP Accelerator (per kbps)=ON to TCP Accelerator (per kbps)=xxxx.

To enable the TCP Accelerator feature together with the MOCN or RAN Sharing feature, you need to set the TCPAccelerator parameter in the SET LICENSE command.

When the license expires, it enters a 60-day grace period. When the grace period elapses, PS services will be limited to use the TCP Accelerator feature.

WRFD-020128

RNC Quality Improvement for Subscribed Service

In the DSP LICUSAGE command output, the license information has been changed from LQW1QIFSS01 Quality Improvement for Subscribed Service (per Mbps) to LQW1QIFSS01RES Quality Improvement for Subscribed Service (per Mbps).

In the LST LICENSE command output, the license information has been changed from Quality Improvement for Subscribed Service (per kbps)=ON to Quality Improvement for

RAN15.0




2-15

Feature ID



Subscribed Service (per kbps)=xxxx.

To enable the Quality Improvement for Subscribed Service feature together with the MOCN or RAN Sharing feature, you need to set the SubscribedServiceImprove parameter in the SET LICENSE command.

When the license expires, it enters a 60-day grace period. When the grace period elapses, PS services will be limited to use the Quality Improvement for Subscribed Service feature.

WRFD-021311

RNC MOCN Introduction Package

In the DSP LICUSAGE command output, a new resource item LQW1MOCN01RES MOCN Introduction Package (per Cell) has been added.

In the LST LICENSE command output, a new resource item MOCN Introduction Package (per

Cell)=xxx has been added.

To activate the MOCN feature, run either of the following commands:

ADD UCELLLICENSE: FuncSwitch1=MOCN_INTRODUCE_PACK_SWITCH-1;

SET LICENSE: SETOBJECT=UMTS, OperatorType=PRIM, FUNCTIONSWITCH4=MOCN_PACKAGE-1;

WRFD-140205

RNC Voice Service Experience Improvement for Weak Reception UEs

In the DSP LICUSAGE command output, the license information has been changed from LQW1IVEI01 Voice Service Experience Improvement for Weak Reception Ues (per Erl) to LQW1IVEI01RES Voice Service Experience Improvement for Weak Reception Ues (per Erl).

In the LST LICENSE command output, the license information has been changed from Voice Service Experience Improvement for Weak Reception Ues (per Erl)=ON to Voice Service Experience Improvement for Weak Reception Ues (per Erl)=xxxx.

To enable the Voice Service Experience Improvement for Weak Reception UEs feature together with the MOCN or RAN Sharing feature, you need to set the VoiceExperienceImprove parameter in the SET LICENSE command.

When the license expires, it enters a 60-day grace period. When the grace period elapses, PS services will be limited to use the Voice Service Experience Improvement for Weak

RAN15.0




2-16

Feature ID



Reception UEs feature.

WRFD-140206

RNC Layered Paging in URA_PCH

In the DSP LICUSAGE command output, the license information has been changed from LQW1LPURA01 Layered Paging in URA_PCH (per Mbps) and LQW1LPURA01 Layered Paging in URA_PCH (per Erl) to LQW1LPURA01RESM Layered Paging in URA_PCH (per Mbps) and LQW1LPURA01RESE Layered Paging in URA_PCH (per Erl), respectively.

In the LST LICENSE command output, the license information has been changed from Layered Paging in URA_PCH (per kbps)=ON to Layered Paging in URA_PCH (per Erl)=xxxx.

To enable the Layered Paging in URA_PCH feature together with the MOCN or RAN Sharing feature, you need to set the URAPCHLayeredPagingErl and URAPCHLayeredPagingKbps parameters in the SET LICENSE command.

When the license expires, it enters a 60-day grace period. When the grace period elapses, PS services will be limited to use the Layered Paging in URA_PCH feature.

WRFD-020135

RNC Intelligent Inter-Carrier UE Layered Management

After the RNC is upgraded to RAN15.0, if the RNC detects that the number of cells enabled with one of these features is greater than the corresponding licensed value, ALM-20743 Insufficient License Resources is reported and the license enters a 60-day grace period.

When the grace period elapses, if the number of cells is still greater than the licensed value, ALM-20741 Configuration Data Exceeding License Capacity is reported and the following cell-level commands cannot be executed:

ADD ULOCELL (to add a local cell)

ADD UCELLQUICKSETUP (to add a cell quickly)

ADD UCELLSETUP (to add basic information about a cell)

Deactivate the feature in some cells or obtain sufficient licenses to solve this problem.

WRFD-140211

RNC Dynamic Target ROT Adjustment

WRFD-140215

RNC Dynamic Configuration of HSDPA CQI Feedback Period

WRFD-140216

RNC Load-based Uplink Target BLER Configuration

WRFD-140223

RNC MOCN Cell Resource Demarcation

WRFD-140217

RNC Inter-Frequency Load Balance Based on Configurable Load Threshold

RAN15.0




2-17

Table 2-14 Changes in the NodeB license control modes

Feature ID License Configured on…

Feature Name

Change Description

None NodeB HSDPA Code If there is no HSDPA code control item in the NodeB license file, HSDPA services cannot be processed by the NodeBs under the RNC.

Before upgrading a NodeB to RAN15.0, check whether there is an HSDPA code control item in the NodeB license file. If there is no HSDPA code control item but HSDPA services are required, add the HSDPA code control item before the upgrade. Otherwise, HSDPA services cannot be established under the RNC and ALM-22217 UMTS Cell HSDPA Function Fault is reported after the upgrade.

None NodeB Power License

A new resource item Power License (per 20W) has been added. One local cell can use multiple Power License (per 20W) resource items. This enables flexible use of power licenses. The power licenses in earlier versions can still be used in RAN15.0. The new resource item Power License (per 20W) can be used only in RAN15.0.

None NodeB UL CE License

When the number of uplink CEs used for UE admission in a NodeB reaches 105% of the licensed value, the RNC rejects access requests of new users. This problem can be solved by increasing the number of uplink CEs.

None NodeB DL CE License

When the number of downlink CEs used for UE admission in a NodeB reaches 105% of the licensed value, the RNC rejects access requests of new users. This problem can be solved by increasing the number of downlink CEs.

WRFD-010683

NodeB Downlink 64QAM

A new cell-level downlink 64QAM switch has been added. If the total number of cells enabled with downlink 64QAM is greater than the licensed value in the NodeB license file, reduce the number of cells enabled with downlink 64QAM or obtain sufficient licenses. Otherwise, after the NodeB is upgraded to RAN15.0, ALM-26811 Configured Capacity Limit Exceeding Licensed Limit is reported and downlink 64QAM cannot be used in some cells.

2.6 Inter-NE Interfaces

In RAN15.0, interfaces between each RNC and other NEs and between each NodeB and UEs comply with 3rd Generation Partnership Project (3GPP) Release 10 and are backward compatible with 3GPP Releases 9, 8, 7, 6, 5, 4, and 99. These interfaces are Iu, Iub, Iur, and Uu.

RAN15.0




2-18

In addition, RAN15.0 introduces the Iur-p interface, which is a Huawei proprietary interface used in the RNC in Pool feature. The Iur-p interface is used to transmit control plane signaling between different physical RNCs.

For the impacts of each feature on these interfaces, see chapter 4 "Impacts of RAN15.0 Features on RAN14.0."

2.7 Operation and Maintenance

RAN15.0 introduces new and enhanced features and internal system optimizations. Therefore, MML commands, parameters, performance counters, alarms, events, and licenses have changed. For the impacts of each new and enhanced feature on operation and maintenance, see chapter 4 "Impacts of RAN15.0 Features on RAN14.0." The operation and maintenance changes for the RNC and NodeB are closely related to the software version. For detailed changes in a specific software version, see the following change documents in the RNC and NodeB release documentation:

MML command and parameter changes

Performance counter changes

Alarm changes

Event changes

License changes

2.8 Other NEs

For the impacts of each new and enhanced feature on other NEs, see chapter 4 "Impacts of RAN15.0 Features on RAN14.0."

RAN15.0

Network Impact Report 3 Summary of Feature Impacts



3-1

3 Summary of Feature Impacts

Table 3-1 through Table 3-9 list the impact severity of new and enhanced features in RAN15.0. For details about the impacts of each new and enhanced feature, see chapter 4 "Impacts of RAN15.0 Features on RAN14.0."

Feature impacts are categorized as "Major" when either of the following conditions is met:

The feature requires new or additional hardware.

The feature impacts RAN14.0 features or NEs.

All other impacts are categorized as "Minor."

Table 3-1 Impact severity of new/basic features in RAN15.0

Feature ID Feature Name Impact Severity

WRFD-141101 System Improvement for RAN15.0 Minor

WRFD-150230 DPCH Pilot Power Adjustment Minor

WRFD-141102 RNC User Plane and Control Plane Static Sharing Minor

WRFD-141103 Automatic NodeB and Cell Allocation in the RNC Major

Table 3-2 Impact severity of enhanced/basic features in RAN15.0


WRFD-010101 Compliance with 3GPP Specifications Minor

WRFD-031103 NodeB Self-test Minor

MRFD-210101 System Redundancy Minor

Table 3-3 Impact severity of new/optional features in RAN15.0


WRFD-141201 RNC User Plane and Control Plane Dynamic Sharing Major

WRFD-150201 Macro & Micro Co-carrier Uplink Interference Control Minor

WRFD-15020101 Macro & Micro Joint Inter-frequency Redirection Minor

WRFD-15020102 Macro & Micro Joint Inter-frequency Handover Minor

WRFD-15020103 Micro Cell Dynamic Rx Sensitivity Control Minor

WRFD-150204 Platinum User Prioritizing Minor

WRFD-150205 Layered Paging in Idle Mode Minor

WRFD-150206 Turbo IC Major

WRFD-150207 4C-HSDPA Minor

RAN15.0




3-2


WRFD-150208 Flexible DC/DB-HSDPA Minor

WRFD-150209 DB-HSDPA Minor

WRFD-150211 RNC in Pool Load Sharing Major

WRFD-150212 RNC in Pool Node Redundancy Major

WRFD-150240 RNC in Pool Multiple Logical RNCs Major

WRFD-150213 MOCN Independent Iub Transmission Resource Allocation Minor

WRFD-150214 MOCN Independent CE Resource Allocation Minor

WRFD-150215 SRVCC from LTE to UMTS with PS Handover Major

WRFD-150216 Load Based PS Redirection from UMTS to LTE Minor

WRFD-150217 Load Based PS Handover from UMTS to LTE Major

WRFD-150219 Coverage Based PS Redirection from UMTS to LTE Minor

WRFD-150220 Coverage Based PS Handover from UMTS to LTE Major

WRFD-150222 HSUPA Time Division Scheduling Major

WRFD-150231 RIM Based UMTS Target Cell Selection for LTE Major

WRFD-150232 Multiband Direct Retry Based on UE Location Minor

WRFD-150233 Differentiated Service Based on Resource Reservation Minor

WRFD-150235 DPCH Maximum Power Restriction Minor

WRFD-150236 Load Based Dynamic Adjustment of PCPICH Minor

WRFD-140225 Narrowband Interference Suppression Major

MRFD-211901 Multi-RAT Carrier Joint Intelligent Shutdown( NodeB) Minor

Table 3-4 Impact severity of enhanced/optional features in RAN15.0


WRFD-010612 HSUPA Introduction Package Minor

WRFD-01061209

HSUPA HARQ and Fast UL Scheduling in Node B Minor

WRFD-010696 DC-HSDPA Minor

WRFD-010703 HSPA+Downlink 84Mbit/s per User Minor

WRFD-010712 Adaptive Configuration of Traffic Channel Power offset for HSUPA

Minor

WRFD-020119 Multi-Carrier Switch off Based on Power Backup Minor

RAN15.0




3-3


WRFD-020129 PS Service Redirection from UMTS to LTE Minor

WRFD-140218 Service-Based PS Handover from UMTS to LTE Minor

WRFD-140219 Micro NodeB Self-Planning Minor

MRFD-221501 IP-Based Multi-mode Co-Transmission on BS side(NodeB) Minor

Table 3-5 Impact severity of new/try features in RAN15.0


WRFD-150223 4C-HSDPA+MIMO Minor

WRFD-150224 HSPA+Downlink 168 Mbit/s per User Minor

WRFD-150227 DB-HSDPA+MIMO Minor

Table 3-6 Features deleted from RAN15.0

Feature ID Feature Name

License Change

WRFD-012001

RNC offload This is a try feature in RAN14.0. RAN15.0 does not support this feature.

Table 3-7 RAN15.0 basic features changed from RAN14.0 optional features

Feature ID Feature Name Change Description

WRFD-020104

Intra Frequency Load Balance

This feature has been changed from an optional feature to a basic feature.

Table 3-8 RAN15.0 optional features changed from RAN14.0 try features

Feature ID Feature Name Change Description

WRFD-140222

Adaptive Adjustment of HSUPA Small Target Retransmissions

This feature has been changed from a try feature to an optional feature.

WRFD-140226

Fast Return from UMTS to LTE This feature has been changed from a try feature to an optional feature.

RAN15.0




3-4

Table 3-9 Features incorporated into other features in RAN15.0

Feature ID


WRFD-050422

Dynamic Bandwidth Control of Iub IP

This feature is incorporated into the WRFD-050402 IP Transmission Introduction on Iub Interface feature.

WRFD-050106

AAL2 Switching Based Hub Node B

This feature is incorporated into the WRFD-050105 ATM Switching Based Hub NodeB feature. In addition, WRFD-050105 ATM Switching Based Hub NodeB is renamed WRFD-050105 ATM/AAL2 Switching Based Hub Node B.

WRFD-011501

PDCP Header Compression (RoHC)

This feature is incorporated into the WRFD-010617 VoIP over HSPA/HSPA+ feature.

WRFD-020307

Video Telephony Fallback to Speech (AMR) for Inter-RAT HO

This feature is incorporated into the following features:

WRFD-020303 Inter-RAT Handover Based on Coverage

WRFD-020305 Inter-RAT Handover Based on Service

WRFD-020306 Inter-RAT Handover Based on Load

WRFD-021200 HCS (Hierarchical Cell Structure)

RAN15.0

Network Impact Report 4 Impacts of RAN15.0 Features on RAN14.0



4-1

4 Impacts of RAN15.0 Features on RAN14.0

4.1 WRFD-141101 System Improvement for RAN15.0 (New/Basic)

4.1.1 Feature Description

This feature is available from RAN15.0.

RAN15.0 has the following system improvements compared with RAN14.0:

Supports new features specified in 3GPP Release 10 (March 2012).

Uses a new type of base station controller BSC6910, which provides higher system capacity and stronger service processing capability.

Supports the RNC in Pool solution.

Enhances system maintainability.

4.1.2 System Capacity and Network Performance

System Capacity

See section 2.2 "Capacity and Performance."

Network Performance

See section 2.2 "Capacity and Performance."

4.1.3 NEs

This feature is implemented on the RNC, NodeB, and M2000.

4.1.4 Hardware

See section 2.3 "Hardware."

4.1.5 Inter-NE Interfaces

See section 2.6 "Inter-NE Interface."

4.1.6 Operation and Maintenance

License

This feature is not under license control.

Configuration Management

No impact.

Performance Management

No impact.

Fault Management

No impact.

RAN15.0




4-2

4.1.7 Impact on Other Features

No impact.

4.2 WRFD-150230 DPCH Pilot Power Adjustment (New/Basic)


This is a trial feature.

When the downlink non-HSDPA transmit power in a cell is high, this feature reduces the downlink DPCH power consumption. The saved power can admit more UEs or promote HSDPA throughput.


System Capacity

When the downlink load in a cell is heavy, this feature reduces downlink DPCH power consumption by configuring a shorter bit length and smaller power offset for the pilot field. Ultimately, this feature reduces the power requirements of each UE in this cell. If HSDPA UEs are in the majority in this cell, the mean transmit power of the downlink DPCH carrying HSDPA UEs is estimated to decrease by 5% to 20%. The saved power can admit 5% to 10% extra UEs if non-HSPA load remains unchanged. This capacity gain is affected by the proportion of UEs processing real-time services. The higher this proportion is, the less the gain this feature provides.

Network Performance

Because the saved power can admit more UEs or increase the downlink throughput of a cell, this feature positively affects network performance as follows:

When the number of UEs in a cell remains unchanged and the traffic volume in this cell is sufficient, more power will be saved to increase downlink cell throughput.

When potential UEs attempt to access a cell in the case of downlink power congestion, this feature increases the access success rate during busy hours.

This feature also has negative impact on network performance. If the power offset or bit length of the pilot field is reduced, SIR estimations will become less accurate and Uu-interface synchronization probability is reduced. This increases the call drop rate. Calls drops become more noticeable in lightly loaded cells.

4.2.3 NEs

This feature is implemented on the RNC.

4.2.4 Hardware

No impact.


No impact.


License

No impact.

RAN15.0




4-3


The following parameters have been introduced on the RNC side.

Table 4-1 New parameters

Change Type

Parameter ID MML Command

Description

New PcSwitch: PC_PILOT_PO_OPTI_SWITCH

SET UCORRMALGOSWITCH

When this switch is turned on and the cell downlink non-HSPA power is exceeds the value of LoadStateForPilotPwrAdj, the power offset configured in the pilot domain on the DL DPCH is NonCsOptiPilotPo(SET UFRC) or CsOptiPilotPo(SET UFRC). When the spreading factor (SF) is 256, the number for bits of pilot bits of the DPCH is DlDpchSf256OptiPilotBit(SET UFRC). Regardless of the switch state, if the downlink non-HSPA power for the cell is smaller than or equals to the threshold for the downlink non-HSPA power, the pilot power offset for the DPCH is PilotPo(SET UFRC). If the SF is 256, the number for bits of pilot bits over the DPCH is DlDpchSf256PilotBit(SET UFRC).

New NonCsOptiPilotPo SET UFRC This parameter specifies the optimized pilot-field power offset for the downlink DPCH not carrying CS services if downlink non-HSPA transmit power in a cell is limited.

New CsOptiPilotPo SET UFRC This parameter specifies the optimized pilot-field power offset for the downlink DPCH carrying CS services if downlink non-HSPA transmit power in a cell is limited.

New DlDpchSf256OptiPilotBit

SET UFRC This parameter specifies the optimized pilot-field bit length for the downlink DPCH with a spreading factor of 256 if downlink non-HSPA transmit power in a cell is limited.

New LoadStateForPilotPwrAdj

SET UFRC This parameter specifies the RNC-level initial load state after the DPCH Pilot Power Adjustment feature takes effect. This feature takes effect on the downlink DPCH when non-HSPA power load in a cell is equal to or larger than the value of this parameter.

New LoadStateForPilotPwrAdj

ADD UCELLFRC

This parameter specifies the cell-level initial load state after the DPCH Pilot Power Adjustment feature takes effect. This feature takes effect on the downlink DPCH when non-HSPA power load in a cell is equal to or larger than the value of this parameter.

../RNCParaHtml/mbsc/m-para/ucorrmalgoswitch_pcswitch.html

../RNCParaHtml/mbsc/m-para/ucellfrc_loadstateforpilotpwradj.html

../RNCParaHtml/mbsc/m-para/ufrc_noncsoptipilotpo.html

../RNCParaHtml/mbsc/m-para/ufrc_csoptipilotpo.html

../RNCParaHtml/mbsc/m-para/ufrc_dldpchsf256optipilotbit.html

../RNCParaHtml/mbsc/m-para/ufrc_pilotpo.html

../RNCParaHtml/mbsc/m-para/ufrc_dldpchsf256pilotbit.html

../RNCParaHtml/mbsc/m-para/ufrc_noncsoptipilotpo.html

../RNCParaHtml/mbsc/m-para/ufrc_csoptipilotpo.html







RAN15.0




4-4


The following counters have been introduced on the RNC side.

Table 4-2 New counters

Change Type

Counter Name Measurement Unit

Description

New VS.DL.DPCH.OptiPilotPOAttNum

ALGO2.Cell Number of Pilot PO Optimization Attempts in the DL DPCH for Cell

New VS.DL.DPCH.NormalPilotPOAttNum

ALGO2.Cell Number of Normal Pilot PO Attempts in the DL DPCH for Cell

Fault Management

No impact.


Prerequisite Features

None

Mutually Exclusive Features

None

Impacted Features

This feature can be activated together with the WRFD-010652 SRB over HSDPA feature. However, when the SRB over HSDPA feature is activated, downlink signaling will not be transmitted on the downlink DPCH. As a result, the application scope of the DPCH Pilot Power Adjustment feature is narrowed.

The cell capacity gains provided by this feature have a negative correlation with the number of UEs using the SRB over HSDPA feature in the cell.

4.3 WRFD-141102 RNC User Plane and Control Plane Static Sharing (New/Basic)

4.3.1 Description

The EGPUa boards in a BSC6910 form two resource pools: the UP pool for processing UP data and the CP pool for processing CP data. Operators can set the ratio of resources allocated to process UP data and that to process CP data (referred to as the UP/CP ratio in this document) based on the traffic model. For example, when the CP central processing unit (CPU) usage is above a specified threshold, a certain amount of resources in the UP pool are reallocated to the CP. Figure 4-1 shows the resource reallocation between the CP and UP.

RAN15.0




4-5

Figure 4-1 Resource reallocation between the CP and UP

This feature reduces the operator's purchasing and maintenance costs because fewer board types are needed. It also improves the hardware usage because operators can adjust the UP/CP ratio based on the traffic model. However, ongoing services on the adjusted processing units are interrupted during the adjustment.

4.3.2 Capacity and Performance

System Capacity

This feature improves system capacity in the following ways:

If CP resources are insufficient and UP resources are sufficient, a certain amount of hardware resources in the UP pool are reallocated to the CP. This increases BHCA capacity.

If UP resources are insufficient and CP resources are sufficient, a certain amount of hardware resources in the CP pool are reallocated to the UP.

Network Performance

This feature balances the load between the CP and UP to prevent critical CP/UP overload. This improves system reliability. When the UP/CP ratio is changed, ongoing processes are stopped and then new processes are started. Therefore, this feature has the following impact on ongoing services during resource reallocation between the CP and UP:

NodeBs, cells, transmission links, and signaling links controlled by the adjusted process are redistributed. This causes some NodeBs to go out of service for about 20 seconds.

Services allocated to the adjusted process are interrupted, increasing the call drop rate. PS services are reestablished after being interrupted.

If the UP/CP ratio is set inappropriately, a large number of NodeBs and cells may not be allocated suitable CP and UP resources. This results in network disconnection and alarm reporting. To prevent this problem, operators must set the ratio to a proper value based on the board specifications and the number of configured boards.

Setting the UP/CP ratio may have severe negative effects. Therefore, this operation should be performed during off-peak hours. When adjusting the ratio, do not drastically change the settings. Make moderate changes to avoid impacting ongoing services.

4.3.3 Impact on NEs


RAN15.0




4-6

4.3.4 Impact on Hardware

Only the BSC6910 supports this feature.

4.3.5 Inter-NE Interface

No impact.


License



The amount of available CP and UP resources and the effect of ratio adjustment change when both of the following are true:

Before the ratio adjustment, a board is not installed or a board is faulty.

After the ratio adjustment, a board is added or the faulty board recovers or is replaced.

Therefore, resolve any related problems before adjusting the ratio. After adding or replacing a board, check the resource usage of the CP and UP pools and determine whether to readjust the ratio.

Table 4-3 describes the new RNC MML commands related to this feature.

Table 4-3 New RNC MML commands related to this feature

Change Type MML Command Description

New SET UCPUPFLEXCFG Use this command to set the following parameters related to the WRFD-141102 RNC User Plane and Control Plane Sharing and WRFD-141201 RNC User Plane and Control Plane Dynamic Sharing features:

FlexCfgMode

FlexCfgPeriod

Flex Cfg Act Time

New LST UCPUPFLEXCFG Use this command to query the parameters related to the WRFD-141102 RNC User Plane and Control Plane Sharing and WRFD-141201 RNC User Plane and Control Plane Dynamic Sharing features.

New DSP UCPUPFLEXCFG

Use this command to query dynamic RNC information about the WRFD-141102 RNC User Plane and Control Plane Sharing and WRFD-141201 RNC User Plane and Control Plane Dynamic Sharing features.

New DSP URSVCAP Use this command to query the number of NodeBs and cells that can be added.

Table 4-4 describes the new RNC parameters related to ALM-22015 Resource Overload on the Control Plane.

RAN15.0




4-7

Table 4-4 New RNC parameters related to ALM-22015 Resource Overload on the Control Plane

Change Type Parameter ID MML Command Description

New CtrlPlnCPUAlmThd

SET UALMTHD Average CP CPU usage threshold at which ALM-22015 Resource Overload on the Control Plane is reported

New CtrlPlnCPUClrThd

SET UALMTHD Average CP CPU usage threshold at which ALM-22015 Resource Overload on the Control Plane is cleared


No new counters related to this feature have been added. The DSP UCPUPFLEXCFG command has been added to monitor the CP and UP CPU usages before and after resource reallocation.

Fault Management

Two alarms related to transmission resource pools have been added on the RNC side:

ALM-22015 Resource Overload on the Control Plane

ALM- 22016 Restricted Flexible Deployment


No impact.

4.4 WRFD-141103 Automatic NodeB and Cell Allocation in the RNC(New/Basic)

4.4.1 Description

When an operator configures NodeBs, cells, NodeB Control Ports (NCPs), and Communication Control Ports (CCPs), the BSC6910 automatically allocates the NodeBs, cells, NCPs, and CCPs to CP subsystems of the EGPUa boards. Operators no longer need to specify the subrack No., slot No., or subsystem No..

The BSC6910 monitors the traffic load on the EGPUa boards. If the traffic load becomes unbalanced due to heavy traffic, the BSC6910 dynamically redistributes the NodeBs, cells, NCPs, and CCPs among CP subsystems of the EGPUa boards. The BSC6910 implements the dynamic redistribution by means of:

Periodic redistribution

Periodic redistribution applies to NodeBs, cells, NCPs, and CCPs, and balances NodeB/cell/NCP/CCP resource management load. Periodic redistribution should be performed in the early morning when the traffic is light.

Immediate redistribution

Immediate redistribution applies only to cells and balances cell resource management load when heavy traffic bursts occur in a subsystem.

../RNCParaHtml/6910/mbsc/m-para/ualmthd_ctrlplncpualmthd.html

../RNCParaHtml/6910/mbsc/m-para/ualmthd_ctrlplncpualmthd.html

../RNCParaHtml/6910/mbsc/m-para/ualmthd_ctrlplncpuclrthd.html

../RNCParaHtml/6910/mbsc/m-para/ualmthd_ctrlplncpuclrthd.html

RAN15.0




4-8


System Capacity

This feature allows NodeB/cell/NCP/CCP resource management load to be shared among CP subsystems. This balances CP load and improves system capacity.

Network Performance

This feature automatically allocates NodeBs, cells, NCPs, and CCPs, and dynamically redistributes them based on the load. This reduces manual maintenance and configuration workload. However, load-based dynamic redistribution affects ongoing services as follows:

During immediate redistribution, which takes about 10 seconds, UEs in the cell cannot initiate a call.

NOTE

UEs in the CELL_DCH, CELL_FACH, CELL_PCH, or URA_PCH state do not drop from the network. UEs in idle mode continue to camp on the cell.

During periodic redistribution:

− UEs in the CELL_DCH, CELL_FACH, CELL_PCH, or URA_PCH state drop from the network.

− UEs in idle mode may temporarily drop from the network.

− Cells are automatically reestablished. A NodeB with 12 cells will be out of service for about 20 seconds.

NOTE

During either immediate or periodic redistribution, NodeBs, cells, NCPs, and CCPs will be removed and then reestablished. Therefore, the values of the performance counters for monitoring the NodeBs, cells, NCPs, and CCPs may be inaccurate.

4.4.3 Impact on NEs

This feature is implemented on the RNC and M2000.




No impact.


License

This feature is a basic feature and is not under license control.


Table 4-5 describes the new RNC MML commands related to this feature.

RAN15.0




4-9

Table 4-5 New and modified RNC MML commands related to this feature

Change Type

MML Command Description

New SET UCELLAUTOHOMING

Use this command to set the following parameters related to load-based dynamic redistribution:

SchedHomingSwitch

ImmdHomingSwitch

SchedAssignOutCpuThd

SchedAssignInCpuThd

SchedAssignInCpuThd

ImmdAssignInCpuThd

SchedHomingMode

New LST UCELLAUTOHOMING

Use this command to query the parameters related to load-based dynamic redistribution.

New ACT UNODEB Use this command to activate a NodeB.

Table 4-6 describes the modified RNC parameters related to this feature.

Table 4-6 Modified RNC parameters related to this feature

Change Type

Parameter ID


Added value

DSPT DSP UCELL A value BYHOMELESSCELL is added to this parameter. If this parameter is set to BYHOMELESSCELL, the Homeless Cell table is queried.

Added value

DSPT DSP UNODEB A value BYHOMELESSCELL is added to this parameter. If this parameter is set to BYHOMELESSCELL, the Homeless NodeB table is queried.

Added value

IDTYPE DSP UIUBCP A value BYHOMELESSIUBCP is added to this parameter. If this parameter is set to BYHOMELESSIUBCP, the Homeless IubCp table is queried.


Table 4-7 describes the new RNC counters related to this feature.

Table 4-7 New RNC counters related to this feature

Change Type Counter Measurement Unit Meaning

New VS.AutoHoming.AttNodeB

ALGO.RNC This counter measures the number of attempts to dynamically redistribute NodeBs from one subsystem to another.

../NodeBParaHtml/comm/para/IKEPEER-LocalIDType.html

RAN15.0




4-10

New VS.AutoHoming.SuccNodeB

ALGO.RNC This counter measures the number of successful attempts to dynamically redistribute NodeBs from one subsystem to another.

New VS.AutoHoming.AttCell

ALGO.RNC This counter measures the number of attempts to dynamically redistribute cells from one subsystem to another.

New VS.AutoHoming.SuccCell

ALGO.RNC This counter measures the number of successful attempts to dynamically redistribute cells from one subsystem to another.

New VS.AutoHoming.AttIubcp

ALGO.RNC This counter measures the number of attempts to dynamically redistribute NCPs/CCPs from one subsystem to another.

New VS.AutoHoming.SuccIubcp

ALGO.RNC This counter measures the number of successful attempts to dynamically redistribute NCPs/CCPs from one subsystem to another.

Fault Management

This feature enables dynamic redistribution of NodeBs, cells, NCPs, and CCPs based on the board status and system resource usage. The Subrack No., slot No., and subsystem No. do not need to be specified. Therefore, alarms related to the NodeBs, cells, NCPs, and CCPs do not provide information about subracks, slots, or subsystems.

The cause value CP Congestion is added to four alarms:

ALM-21511 CCP Faulty

ALM-22202 UMTS Cell Unavailable

ALM-22214 NodeB Unavailable

ALM-21510 NCP Faulty


No impact.

4.5 WRFD-010101 Compliance with 3GPP Specifications (Enhanced /Basic)


RAN15.0 complies with 3GPP Release 10 (March 2012). The new features and enhanced functions in RAN15.0 provide more high-performance services and increases operators' competitiveness.

This feature enables interconnection with other NEs that comply with 3GPP R99/R4/R5/R6/R7/R8/R9/R10 specifications, protecting operators' investment.

RAN15.0




4-11


System Capacity

No impact.

Network Performance

No impact.

4.5.3 NEs


Some new features in RAN15.0 require the UE and CN to support 3GPP Release 10. For details, see the impacts of each feature.

4.5.4 Hardware

No impact.


The CN and subscriber interfaces must be upgraded to support 3GPP Release 10.


License



No impact.


No impact.

Fault Management

No impact.


No impact.

4.6 WRFD-031103 NodeB Self-test (Enhanced /Basic)


The engineering quality check has been enhanced for the NodeB Self-test feature in RAN15.0:

Software commissioning, fault diagnosis, and service verification have been removed.

Voltage standing wave ratio (VSWR) testing, crossed-pair connection detection, and intermodulation interference testing have been added. These enhancements help commissioning engineers quickly detect engineering problems.

RAN15.0




4-12


System Capacity

No impact.

Network Performance

No impact.

4.6.3 NEs

This feature is implemented on the NodeB. Only the 3900 series base stations support this feature.

The M2000 must support this feature.

4.6.4 Hardware

No impact.


No impact.


License



No impact.


No impact.

Fault Management

No impact.


No impact.

4.7 MRFD-210101 System Redundancy (Enhanced /Basic)

4.7.1 Description

This feature is an enhancement to the MRFD-210101 System Redundancy feature.

RAN15.0




4-13

The BSC6910 uses all-IP switching. The switching boards, clock boards, interface boards, and resource management boards work in active/standby mode. That is, the boards of the same type in two adjacent slots are a pair of active and standby boards.

Figure 4-2 shows the active and standby boards in the BSC6910.

Figure 4-2 Active and standby boards in the BSC6910

The EGPUa boards in the BSC6910 form a transmission resource pool. In the pool, CP processes of the EGPUa boards work in backup mode to improve CP reliability. The CP processes of different EGPUa boards can work in active/standby mode, as shown in Figure 4-3. When a process is faulty, cells and established calls are not affected.

RAN15.0




4-14

Figure 4-3 CP processes in backup mode


System Capacity

No impact.

Network Performance

No impact.

4.7.3 Impact on NEs



No impact.


No impact.


License

No impact.


The EGPUa board can provide multiple logical functions. If the EGPUa board is used to manage system resources, it works in 1+1 backup mode. If the EGPUa board is used to process services, it works in resource pool mode.

RAN15.0




4-15


No impact.

Fault Management

No impact.


No impact.

4.8 WRFD-141201 RNC User Plane and Control Plane Dynamic Sharing (New/Optional)

4.8.1 Description

The BSC6910 automatically monitors the CP and UP load. When the difference between them reaches a specified threshold during busy hours, the BSC6910 automatically adjusts the UP/CP ratio. Figure 4-4 shows the automatic UP/CP ratio adjustment.

Figure 4-4 Automatic UP/CP ratio adjustment

When the UP/CP ratio is adjusted, services on the processing units involved are interrupted.

Operators can set the time at which the UP/CP ratio is automatically adjusted. The adjustment should be performed during off-peak hours to reduce the impact on ongoing services.

This feature reduces maintenance costs and increases the hardware usage by automatically adjusting the UP/CP ratio based on the traffic model.


System Capacity

For details, see section 4.3.2 "Capacity and Performance."

Network Performance

For details, see section 4.3.2 "Capacity and Performance."

RAN15.0




4-16

The impact of this feature on ongoing services can be reduced by setting the following parameters:

CPOverUPDeltaThd

UPOverCPDeltaThd

FlexCfgPeriod

FlexCfgActTime

Setting FlexCfgActTime to an off-peak time (for example, in the early morning) prevents frequent adjustments.

4.8.3 Impact on NEs





No impact.


License

An RNC-level license for this feature has been added on the RNC side.


For details, see section 4.3.6 "Operation and Maintenance."



Fault Management



No impact.

4.9 WRFD-150201 Macro & Micro Co-carrier Uplink Interference Control (New/Optional)


On macro-micro co-carrier networks, a macro cell generally transmits at a maximum power of 20 W and a micro cell transmits at a maximum power of 1 W or 5 W. This results in a difference of 13 dB or 6 dB in the downlink pilot power between the macro cell and micro cell. The difference also produces two problem areas: a soft handover (SHO) area and a non-SHO area, as shown in Figure 4-5.

RAN15.0




4-17

Figure 4-5 Macro-micro problem areas

SHO Area

An SHO area has the following characteristics:

The best cell for a UE is a macro cell.

The link between the UE and the micro cell is added to the active set.

In an SHO area, both the macro cell and micro cell perform uplink inner-loop power control on the UE. Inner-loop power control performed by the micro cell plays the leading role because the SIR on the DPCCH received in the micro cell is greater than that received in the macro cell. This affects the HSDPA or HSUPA throughput for the macro cell and the radio link for the macro cell may be out-of-synchronization in the uplink.

Non-SHO Area

A non-SHO area has the following characteristics:

The best cell for a UE is a macro cell.

The link between the UE and the micro cell is not added to the active set.

The uplink path loss of the UE is smaller for the micro cell than for the macro cell.

The UE is closer to the micro cell than to the macro cell. Therefore, the UE's signal reception is greater in the micro cell, but the UE also causes greater interference to the micro cell.

The Macro & Micro Co-carrier Uplink Interference Control feature resolves the proceeding problems by using the following three sub-features:

Macro & Micro Joint Inter-frequency Redirection

Macro & Micro Joint Inter-frequency Handover

Micro Cell Dynamic Rx Sensitivity Control

The first two sub-features redirect the UEs in the RRC connection setup procedure to an inter-frequency macro cell that has no intra-frequency neighboring micro cells. If the UEs are in connected mode, the two sub-features hand over these UEs to an inter-frequency macro cell that has no intra-frequency neighboring micro cells. In this way, few UEs will be implementing services in macro-micro problem areas. This prevents HSPA throughput drops in the macro cell and minimizes the uplink interference to the micro cell caused by UEs in the macro cell.

Upon detecting a UE in macro-micro problem area, the Micro Cell Dynamic Rx Sensitivity Control sub-feature is used to reduce the receive sensitivity for the micro cell to eliminate the differences between the uplink boundary and the downlink boundary for both the macro and micro cells. This mitigates the uplink interference to the micro cell caused when a UE is in the macro cell and increases the HSPA throughput for UEs in the problem areas. When no UE is detected in macro-micro problem areas, Micro

RAN15.0




4-18

Cell Dynamic Rx Sensitivity Control restores the receive sensitivity for the micro cell, excising a post-desensitization uplink interference to the macro cell.

Using the three sub-features together is ideal for the target macro cell that meets the UE transfer requirements. Specifically, use the first two sub-features to transfer UEs in macro-micro problem areas. If the transmission fails, use the third sub-feature to reduce the receive sensitivity for the micro cell to restore it after the UEs leave the problem areas or their connections have been released.

Figure 4-6 Desensitization after a UE transfer failure

Use the Micro Cell Dynamic Rx Sensitivity Control feature only if there is no target macro cell meets the UE transfer requirements. This applies to the scenarios where a single-carrier macro cell is configured with only intra-frequency neighboring micro cells or a multi-carrier macro cell is configured with only intra-frequency neighboring micro cells.

RAN15.0




4-19

Figure 4-7 Desensitization when users are detected in problem areas

4.9.2 System Capacity and Network Performance (for Scenarios Where Some Cells Operate at the Same Frequency Band)

As shown in Figure 4-8, when only part of the cells operate at the same frequency band, at least one macro cell is not configured with intra-frequency neighboring micro cells. For example, in a macro cell operating at multiple frequencies, at least two frequencies are configured for the same NodeB and serve two co-coverage cells. The two cells are mutually neighboring cells for blind handovers, but only one of them has an intra-frequency neighboring micro cell.

Figure 4-8 Some cells operating at the same frequency band

System Capacity

As shown in Figure 4-8, the NodeB is configured with two frequencies for macro cells: F1 and F2. F1 is configured for macro and micro cells operating at the same frequency band, whereas F2 is configured for macro cells only. In this scenario, the total system capacity equals the F1 cell capacity plus the F2 cell capacity.

RAN15.0




4-20

On networks where macro and micro cells operate at the same frequency band, the maximum transmit power of the macro cell is 20 W and that of the micro cell is 5 W, and the difference in the downlink P-CPRICH pilot power between the macro cell and micro cell is 6 dB. When all of the three sub-features described in section 4.9.1 "Feature Description" are enabled, the impact on the system capacity varies depending on the scenario as follows:

Scenario: The micro cell is initially activated and the Macro & Micro Co-carrier Uplink Interference Control feature is enabled when all intra-frequency cells on the macro-micro network are updated to RAN15.0 or later. In this scenario, this feature adds benefits to those of the micro cell deployment. Compared with the macro dual-carrier networking mode, this feature has the following impacts on the system capacity:

Positive impacts

− Increases the overall system capacity when micro cells are deployed. The capacity increment cannot be quantified because it depends on the number of micro cells, the location of the micro cell, and the traffic absorption volume.

− Eliminates the difference between the uplink boundary and the downlink boundary for the macro and micro cells to enable micro cell deployment through micro cell desensitization:

Micro cell desensitization mitigates interferences to the micro cell caused by worst users, and enhances the stability and uplink capacity in the micro cell.

Micro cell desensitization minimizes the chance of HSPA throughput drops in the micro cell caused by micro cell–initiated power control in problem areas 1A to 1D.

NOTE

In this scenario, the benefits of this feature blend with those of the micro cell deployment and therefore cannot be evaluated separately. Therefore, the system capacity should be evaluated by comparing with the macro dual-carrier networking mode when all the three sub-features are enabled at one time. Each sub-feature in this scenario will not be evaluated separately.

Network Performance

As shown in Figure 4-8, on macro-micro co-carrier networks, the maximum transmit power of the macro cell is 20 W and that of the micro cell is 5 W, and the difference in the downlink P-CPRICH pilot power between the macro cell and micro cell is 6 dB. When all of the three sub-features are enabled, the impact on the network performance varies depending on the scenario as follows:


Positive impacts

When the micro cell is used to strengthen the network coverage, it brings the following benefits:

− Decreases the service drop rate. The KPI values depend on live network factors and cannot be quantified.

− Increases the access success rate. The KPI values depend on live network factors and cannot be quantified.

When the micro cell is used to absorb hot spot traffic, it has the following impacts:

Positive impacts: Decreases the service load in the macro cell with no or little increase in overall KPIs. The KPI values depend on live network factors and cannot be quantified.

Negative impacts

− Extends the soft handover–applied zone and increases the number of soft handover attempts on macro-micro co-carrier networks.

RAN15.0




4-21

− Decreases the inter-frequency handover success rate. The blind handover triggered by Macro & Micro Joint Inter-frequency Handover reduces the hard handover success rate between inter-frequency cells. The KPI values depend on live network factors and cannot be quantified.

4.9.3 System Capacity and Network Performance (for Scenarios Where All Cells Operate at the Same Frequency Band)

In this scenario, all macro cells have neighboring micro cells operating at the same frequency band, as shown in Figure 4-9. For example, a single-carrier macro cell has an intra-frequency neighboring micro cell.

Figure 4-9 All cells operating at the same frequency band

However, if the macro cell uses multiple carriers on macro-micro co-carrier networks, sub-features Macro & Micro Joint Inter-frequency Redirection and Macro & Micro Joint Inter-frequency Handover cannot be enabled in the following two scenarios:

The macro cell has no inter-frequency neighboring macro cells.

The macro cell is not configured with inter-frequency neighboring macro cells.

Therefore, only the Micro Cell Dynamic Rx Sensitivity Control sub-feature can be separately used in these two scenarios. When this sub-feature is enabled, all micro cells are desensitized if the RNC detects UEs in macro-micro problem areas. Compared with the combined use of all the three sub-features, this sub-feature alone provides similar system capacity, network performance, and handover success rate. However, the chance of global desensitization for micro cells will increases because detected UEs are not transferred out of the problem area.

System Capacity

On macro-micro co-carrier networks, the maximum transmit power of the macro cell is 20 W and that of the micro cell is 5 W, and the difference in the downlink P-CPRICH pilot power between the macro cell and micro cell is 6 dB. In this scenario, the total system capacity equals the F1 cell capacity plus the F2 cell capacity.


Positive impacts

− Increases the overall system capacity when micro cells are deployed. The capacity increment cannot be quantified because it depends on the number of micro cells, the location of the micro cell, and the traffic absorption volume.

− Eliminates the difference between the uplink boundary and the downlink boundary for the macro and micro cells to enable micro cell deployment through micro cell desensitization:

− Micro cell desensitization mitigates interferences to the micro cell caused by worst users, and enhances the stability and uplink capacity in the micro cell.

RAN15.0




4-22

− Micro cell desensitization minimizes the chance of HSPA throughput drops in the micro cell caused by micro cell–initiated power control in problem areas.

Negative impacts

Extends the soft handover–applied zone and increases the number of soft handover attempts on macro-micro co-carrier networks.

Network Performance

As shown in Figure 4-9, on macro-micro co-carrier networks, the maximum transmit power of the macro cell is 20 W and that of the micro cell is 5 W, and the difference in the downlink P-CPRICH pilot power between the macro cell and micro cell is 6 dB.

Scenario: The micro cell is initially activated and the Macro & Micro Co-carrier Uplink Interference Control feature is enabled when all intra-frequency cells on the macro-micro network are updated to RAN15.0 or later. In this situation, the benefits of this feature blend with those of the micro cell deployment. Compared with the macro-only networking mode, this feature has the following network performance impacts:

Positive impacts

When the micro cell is used to strengthen the network coverage, it brings the following benefits:

− Decreases the service drop rate. The KPI values depend on live network factors and cannot be quantified.

− Increases the access success rate. The KPI values depend on live network factors and cannot be quantified.

When the micro cell is used to absorb hot spot traffic, it has the following impacts:

Positive impacts

− Decreases the service load in the macro cell with no or little increase in overall KPIs. The KPI values depend on live network factors and cannot be quantified.

Negative impacts

Extends the soft handover–applied zone and increases the number of soft handover attempts on macro-micro co-carrier networks.

4.9.4 NEs

For details, see sub-features WRFD-15020101 Macro & Micro Joint Inter-frequency Redirection, WRFD-15020102 Macro & Micro Joint Inter-frequency Handover for inter-band handovers, and WRFD-15020103 Micro Cell Dynamic Rx Sensitivity Control.

4.9.5 Hardware




RAN15.0




4-23


License

A new license item has been introduced on the RNC to control this feature at the cell level.

Feature ID Feature Name License Control Item NE Sales Unit

WRFD-150201

WRFD-150201 Macro & Micro Co-carrier Uplink Interference Control


RNC per micro cell





Fault Management






None

Impacted Features


RAN15.0




4-24

4.10 WRFD-15020101 Macro & Micro Joint Inter-frequency Redirection (New/Optional)


On a macro multi-carrier network where some macro cells have intra-frequency neighboring micro cells, this feature is used to check whether there are UEs setting up PS services in problem areas during the RRC connection. The RNC checks the signal quality difference between the macro and micro cells carried in the RRC connection request sent from the UE. If a UE is detected in problem areas, it is redirected to a macro cell that has no intra-frequency neighboring micro cells. In this way, this feature protects UEs from call drops or throughput decreases caused by the difference between the uplink boundary and the downlink boundary for the macro and micro cells.


System Capacity

For details, see section 4.9.2 "System Capacity and Network Performance (for Scenarios Where Some Cells Operate at the Same Frequency Band)."

Network Performance


4.10.3 NEs

This feature is implemented on the RNC, NodeB, M2000, and CME.

4.10.4 Hardware

No impact.


No impact.


License



WRFD-150201 WRFD-150201 Macro & Micro Co-carrier Uplink Interference Control

Macro & Micro Co-carrier Uplink Interference Control (Per Cell)

RNC per cell


The following table lists the parameter that has been added on the RNC for this feature.

RAN15.0




4-25


New COMacroMicroIFRedirSwitch

SET/LST UDRD Specifies whether to make the inter-frequency redirection algorithm in macro-micro problem areas to take effect. When this parameter is set to ON, macro and micro correlative inter-frequency redirection is enabled. Otherwise, the inter-frequency redirection algorithm in macro-micro problem areas is disabled.

New MicroCellFlag ADD/RMV/MOD/LST UCELLDESENSE

Specifies whether the current cell is a micro cell. If this parameter is set to True, the current cell is a micro cell. Otherwise, the current cell is a macro cell.

New Macro2MicroUlDiff

ADD/RMV/MOD/LST UCELLDESENSE

Specifies the uplink receiving capacity different between the macro cell and micro cell. The value of this parameter depends on the number of antennas in the macro and micro cells and tower mounted amplifier (TMA). This parameter is set to 3 dB in the following conditions:

The macro cell uses four antennas.

The micro cell uses two antennas.


New Total2PartDesenseDiff


Specifies the difference between global desensitization intensity and partial desensitization intensity of a micro cell.

Partial desensitization intensity = Full desensitization intensity – Total2PartDesenseDiff


This feature has an impact on the following RNC counters:

Change Type Counter Name Measurement Unit Description

New VS.RRC.Rej.Redir.CoMacroMicro

RRC.SetupFail.Cell Specifies the number of outgoing macro & micro joint inter-frequency redirections.

This feature has no impact on the NodeB counters.

Fault Management

No impact.

../RNCParaHtml/mbsc/m-para/udrd_comacromicroifredirswitch.html

../RNCParaHtml/mbsc/m-para/udrd_comacromicroifredirswitch.html

../RNCParaHtml/mbsc/m-para/ucelldesense_microcellflag.html

../RNCParaHtml/mbsc/m-para/ucelldesense_macro2microuldiff.html


../RNCParaHtml/mbsc/m-para/ucelldesense_total2partdesensediff.html


RAN15.0




4-26



This feature depends on the following features:

WRFD-020400 DRD Introduction Package



None

Impacted Features

None

4.11 WRFD-15020102 Macro & Micro Joint Inter-frequency Handover (New/Optional)


On a macro multi-carrier network where some macro cells have intra-frequency neighboring micro cells, this feature is used to check whether there are UEs in connected mode setting up HSUPA or HSDPA services in problem areas. The RNC checks the signal quality difference between the macro and micro cells reported from the UE. If a UE is detected in problem areas, it is blindly redirected to an inter-frequency macro cell that has no intra-frequency neighboring micro cells. In this way, this feature protects UEs from call drops or throughput drops caused by the difference between the uplink boundary and the downlink boundary for the macro and micro cells, thereby minimizing the uplink interference in the micro cell.


System Capacity


Network Performance


4.11.3 NEs

This feature is implemented on the RNC, NodeB, M2000, and CME.

4.11.4 Hardware

No impact.


No impact.

RAN15.0




4-27


License





RNC per cell



Change Type

Parameter ID MML Command Description

New HoSwitch1:HO_COMACROMICRO_INTER_FREQ_OUT_SWITCH

SET/LST UCORRMALGOSWITCH

Specifies whether the sub-feature Macro & Micro Joint Inter-frequency Handover is enabled. When this parameter is set to ON, the sub-feature is enabled. When this parameter is set to OFF, the sub-feature is disabled.

This feature checks whether UEs are located in problem areas of intra-frequency networks with macro and micro cells. Then, the feature instructs these UEs to move to other cells through blind inter-frequency handovers.

New ReportIntervalfor1APre

SET/LST UHOCOMM Specifies the interval between the reports that are triggered by event 1A' in macro-micro problem areas.

New MacroMicro1APreMeasSwitch

SET/LST UHOCOMM

ADD/RMV/MOD/LST UCELLHOCOMM

Specifies whether to send the event 1A' measurement control message. If the parameter is set to ON, the RNC sends the event 1A' measurement control message to identify users in the macro-micro problem areas 1A'-1A. If the parameter is set to OFF, the RNC does not send the event 1A' measurement control message.

When a user whose best cell is the macro cell moves to an area near to the micro cell and its link to the micro cell has not been added to the active set, the user causes large interference to the micro cell in the uplink. This type of area is referred to as the macro-micro problem area and event 1A' is added to

../RNCParaHtml/mbsc/m-para/ucorrmalgoswitch_hoswitch1.html

../RNCParaHtml/mbsc/m-para/uhocomm_reportintervalfor1apre.html


../RNCParaHtml/mbsc/m-para/ucellhocomm_macromicro1apremeasswitch.html


RAN15.0




4-28

Change Type


identify this type of users.

Event 1A' is reported when a user moves to the macro-micro problem area and ReportIntervalfor1APre specifies the interval of periodic reports. Events 1A and 1APre have the same measurement reports and their only difference lies in measurement IDs. That is, the RNC differentiates between event 1A and event 1A' only by the measurement ID.

When the Micro Cell Dynamic Rx Sensitivity Control feature is enabled in the micro cell, the event 1APre threshold is the value of Total2PartDesenseDiff in the ADD UCELLDESENSE command. Otherwise, the event 1A' threshold is equal to the global desensitization intensity.


Specifies whether the current cell is a micro cell. If this parameter is set to True, the current cell is a micro cell. Otherwise, the current cell is a macro cell.

New Macro2MicroUlDiff ADD/RMV/MOD/LST UCELLDESENSE

Specifies the uplink receiving capacity different between the macro cell and micro cell. The value of this parameter depends on the number of antennas in the macro and micro cells and tower mounted amplifier (TMA). This parameter is set to 3 dB in the following conditions:







Partial desensitization intensity = Full desensitization intensity – Total2PartDesenseDiff







RAN15.0




4-29

Change Type Counter Name Measurement Unit

Description

New VS.HHO.AttInterFreqOut.PS.CoMacroMicro

HHO.Cell Specifies the number of outgoing macro & micro joint inter-frequency handover attempts in PS domain for cell.

New VS.HHO.SuccInterFreqOut.PS.CoMacroMicro

HHO.Cell Specifies the number of successful outgoing macro & micro joint inter-frequency handovers in PS domain for cell.


Fault Management

No impact.



This feature depends on the following features:

WRFD-020110 Multi Frequency Band Networking Management



None

Impacted Features

None

4.12 WRFD-15020103 Micro Cell Dynamic Rx Sensitivity Control (New/Optional)


With this feature enabled, the micro cell adjusts its receive sensitivity by implementing desensitization. Desensitization is a process in which the micro NodeB fills in the white noise to the RRU receive channel. The micro NodeB makes the uplink boundary coincide with the downlink boundary by adjusting desensitization intensity to eliminate the difference in the uplink between the macro and micro cells.

Reducing the receive sensitivity of the micro cell raises the uplink transmit power for all UEs in the micro cell. Therefore, worst users in the micro cell, which are close to the macro cell, cause more interference to the macro cell. To minimize the interference, the receive sensitivity for the micro cell is reduced only if there are UEs in the macro-micro problem area. If a UE is detected in the macro-micro problem area, the RNC instructs the micro cell to implement desensitization to reduce the receive

RAN15.0




4-30

sensitivity. If all UEs move out of the macro-micro problem area or their RRC connections are released, the micro cell cancels desensitization to restore the receive sensitivity.


Independent use of WRFD-15020103 Micro Cell Dynamic Rx Sensitivity Control will affect the system capacity and network performance as follows.

System Capacity

For details, see section 4.9.3 "System Capacity and Network Performance (for Scenarios Where All Cells Operate at the Same Frequency Band)."

Network Performance

For details, see section 4.9.3 "System Capacity and Network Performance (for Scenarios Where All Cells Operate at the Same Frequency Band)."

4.12.3 NEs

This feature is implemented on the RNC, NodeB, M2000, and Configuration Management Express (CME).

4.12.4 Hardware

No impact.


An information element (IE) has been added for this feature.

A private IE DesensPower has been added in the Physical Shared Channel Reconfiguration Request IE. The DesensPower IE indicates the absolute value of the current desensitization power in the unit of dBm.


License





RNC per cell




New COMacroMicroDesenseSwitch

ADD/RMV/MOD/LST

Specifies whether the current cell supports macro-micro correlative

../RNCParaHtml/mbsc/m-para/ucelldesense_comacromicrodesenseswitch.html

../RNCParaHtml/mbsc/m-para/ucelldesense_comacromicrodesenseswitch.html

RAN15.0




4-31


UCELLDESENSE desensitization. When this parameter is set to ON, the current cell supports macro-micro correlative desensitization. When this parameter is set to OFF, the current cell does not support macro-micro correlative desensitization.

Only BTS3902E of RAN15.0 or later allows this parameter setting to ON. Otherwise the throughput rate in the micro cell is abnormal.

New ReportIntervalfor1APre

SET/LST UHOCOMM

Specifies the interval between the reports that are triggered by event 1A' in macro-micro problem areas.

New TotalDesensCancelTimeLen


Specifies the length of a timer for periodically canceling global desensitization. Each time when this timer expires, the RNC determines whether to cancel the global desensitization on the current micro cell. After the global desensitization cancelation, the current micro cell enters the partial desensitization state.


Specifies whether to set the current cell as a micro cell. If this parameter is set to True, the current cell is a micro cell. Otherwise, it is a macro cell.

New Macro2MicroUlDiff


Specifies the uplink receiving capacity different between the macro cell and micro cell. The value of this parameter depends on the number of antennas in the macro and micro cells and tower mounted amplifier (TMA). For example, this parameter is set to 3 dB in the following conditions:







Partial desensitization intensity = Full desensitization intensity – Total2PartDesenseDiff.

New MacroMicro1APreMeasSwitch

SET/LST UHOCOMM ADD/RMV/MOD/LST

Specifies whether to send the event 1A' measurement control message. If the parameter is set to ON, the RNC sends the event 1A' measurement control



../RNCParaHtml/mbsc/m-para/ucelldesense_totaldesenscanceltimelen.html

../RNCParaHtml/mbsc/m-para/ucelldesense_totaldesenscanceltimelen.html








RAN15.0




4-32


UCELLHOCOMM message to identify users in the macro-micro problem areas 1A'-1A. If the parameter is set to OFF, the RNC does not send the event 1A' measurement control message.

When a user whose best cell is the macro cell moves to an area near to the micro cell and its link to the micro cell has not been added to the active set, the user causes large interference to the micro cell in the uplink. This type of area is referred to as the macro-micro problem area and event 1A' is added to identify this type of users. Event 1A' is reported when a user moves to the macro-micro problem area and ReportIntervalfor1APre specifies the interval of periodic reports.

Events 1A and 1APre have the same measurement reports and their only difference lies in measurement IDs. That is, the RNC differentiates between event 1A and event 1A' only by the measurement ID.

When the Micro Cell Dynamic Rx Sensitivity Control feature is enabled in the micro cell, the event 1APre threshold is the value of Total2PartDesenseDiff in the ADD UCELLDESENSE command. Otherwise, the event 1A' threshold is equal to the global desensitization intensity.




Description

New VS.TotalDesense.Num ALGO.Cell Specifies the total number of times a micro cell transits to the total desensitization state.

New VS.TotalDesense.Time ALGO.Cell Specifies the duration of the total desensitization state for a micro cell.

New VS.MeanDesensePwr ALGO.Cell Specifies the average desensitization intensity for a micro cell.

RAN15.0




4-33


Fault Management

No impact.





None

Impacted Features

Working with WRFD-020136 Anti-Interference Scheduling for HSUPA, the Micro Cell Dynamic Rx Sensitivity Control feature can raise the received total wideband power (RTWP) and reduce uplink coverage of the micro cell.

Working with WRFD-140211 Dynamic Target RoT Adjustment, the Micro Cell Dynamic Rx Sensitivity Control feature can reduce uplink capacity gains generated by the WRFD-140211 Dynamic Target RoT Adjustment feature for the micro cell.

Working with Auto-Adaptive Background Noise Update Switch, the Micro Cell Dynamic Rx Sensitivity Control feature can reduce the number of times for which the switch takes effect.

When enabled, the Micro Cell Dynamic Rx Sensitivity Control feature disables the static desensitization function and annuls the configured desensitization intensity. When this feature is disabled, the static desensitization function needs to be reconfigured before it is available again.

NOTE

To specify a desensitization intensity, run SET ULOCELLDESENS: DI on the NodeB. Once specified, the intensity will not change.

4.13 WRFD-150204 Platinum User Prioritizing (New/Optional)


If network congestion occurs during, for example, large gatherings, sports events, or festivals, it can become difficult for users to access the network. With the Platinum User Prioritizing feature, the RNC allows platinum users to preferentially access the network during network congestion. In addition, this feature improves voice quality for platinum users and increases their HSPA throughput when downlink coverage is weak.


System Capacity

The maximum downlink transmit power for platinum users' conversational services is 3 dB higher than that for common users. When platinum users are located in weak coverage areas, the downlink load of the network increases. As a result, the power available to other services, such as HSPA services, decreases. This reduces cell throughput.

../NodeBParaHtml/comm/para/ULoCell-desensitizationIntensity.html

RAN15.0




4-34

If the proportion of platinum users is low in a cell, the impact on network capacity is very small and can be hardly noticed.

If the proportion of platinum users is high in a cell, RLC retransmission rates and service establishment delay increase.

Network Performance

RRC Connection Setup Success Rate for Cell

After the Platinum User Prioritizing feature is enabled, the RRC connection setup success rate in a cell may increase. This is because the RRC connection setup success rate of platinum users increases. However, if platinum users account for only a small proportion of the total users in a cell, this feature has only a small impact on the RRC connection setup success rate.

RAB Setup Success Rate for Cell

After the Platinum User Prioritizing feature is enabled, the RAB setup success rate in a cell may increase. This is because the RAB setup success rate of platinum users increases. However, if platinum users account for only a small proportion of the total users in a cell, this feature has only a small impact on the RAB setup success rate.

CS call drop rate for Cell

Platinum users preempt the resources of common users, which increases the CS call drop rate. However, if there are a large number of PS services in the cell, the probability that the resources of CS services are preempted is low, and therefore the impact of this feature on the CS call drop rate is small.

If downlink weak coverage is the major reason for call drops, the call drop rate of platinum users decreases because NodeBs increase the maximum downlink transmit power for platinum users' conversational services by 3 dB. Therefore, the CS call drop rate in the cell decreases. If the proportion of platinum users is low and signal quality in the network is good, the impact of this feature on the CS call drop rate is not obvious.

PS call drop rate for Cell

When congestion occurs, platinum users preempt the resources of PS services, increasing the PS call drop rate. The larger the proportion of platinum users and the severer the congestion, the higher the PS call drop rate.

4.13.3 NEs

No impact.

4.13.4 Hardware

No impact.


No impact.


License

Two RNC-level license control items have been added to the RNC for the Platinum User Prioritizing feature.

RAN15.0




4-35


WRFD-150204 Platinum User Prioritizing

Platinum User Prioritizing (per Erl)

Platinum User Prioritizing (per kbps)

RNC Erl+Mbps


The following parameters and MML commands have been introduced or modified to accommodate the Platinum User Prioritizing feature.

Change Type


New parameter

PlatinumIMSI ADD/RMV/LST UPLATINUMIMSI

This new parameter specifies the IMSIs of platinum users. A maximum of 1000 platinum users can be configured.

New parameter

PlatinumUserPriErl

SET/LST LICENSE

This new parameter specifies the Erlangs that can be used by an operator for this feature.

The sum of the Erlangs configured for all the operators cannot exceed the licensed Erlangs for this feature.

New parameter

PlatinumUserPriKbps

SET/LST LICENSE

This new parameter specifies the PS throughput that can be used by an operator for this feature.

The sum of the PS throughput configured for all the operators cannot exceed the licensed PS throughput for this feature.

Modified parameter

PROCESSSWITCH: PTUSER_IDENTIFY_SWITCH

SET/LST URRCTRLSWITCH

When this switch is turned on, the RNC identifies platinum users and preferentially processes their service requests.

When this switch is turned off, the RNC does not identify platinum users nor preferentially process their service requests.

../RNCParaHtml/mbsc/m-para/uplatinumimsi_platinumimsi.html

../RNCParaHtml/mbsc/m-para/urrctrlswitch_processswitch.html


RAN15.0




4-36

Change Type


New parameter

PtUserAbsolutePriority

SET/LST UQUEUEPREEMPT

This new parameter specifies whether the RNC preferentially processes the PS service requests from platinum users when the PriorityReference parameter in the SET UUSERPRIORITY command is set to TrafficClass. When this new parameter is set to True, platinum users' non-conversational (including streaming, interactive, and background) services first preempt the resources occupied by common users' non-conversational services and then conversational services. When this new parameter is set to False, platinum users' non-conversational services can preempt the resources occupied by common users' non-conversational services but cannot preempt the resources for common user' conversational services.

Modified command

None DSP UCELLCHK This modified command is used to display the number of current platinum users in a cell.


The following counters have been introduced on the RNC side to accommodate the Platinum User Prioritizing feature.

Change Type

Counter Name Measurement Unit Description

New RRC.AttConnEstab.Conv.Platinum

RRC.Setup.Cell Number of RRC Connection Setup Requests for Platinum UEs Performing Conversational Services

New RRC.AttConnEstab.Platinum

RRC.Setup.Cell Number of RRC Connection Setup Requests for Platinum UEs Performing Services

New RRC.SuccConnEstab.Conv.Platinum

RRC.Setup.Cell Number of Successful RRC Connection Setups for Platinum UEs Performing Conversational Services

New RRC.SuccConnEstab.Platinum

RRC.Setup.Cell Number of Successful RRC Connection Setups for Platinum UEs

New VS.RAB.AttEstabCS.Platinum

RAB.EstabCS.Cell Number of CS RAB Setup Requests for Platinum UEs

New VS.RAB.AttEstabCS.Conv.Platinum

RAB.EstabCS.Cell Number of CS RAB Setup Requests for Platinum UEs Performing Conversational Services

../RNCParaHtml/mbsc/m-para/uqueuepreempt_ptuserabsolutepriority.html

../RNCParaHtml/mbsc/m-para/uqueuepreempt_ptuserabsolutepriority.html

../RNCParaHtml/mbsc/m-para/uuserpriority_priorityreference.html

RAN15.0




4-37

Change Type


New VS.RAB.AttEstabPS.Platinum

RAB.EstabPS.Cell Number of PS RAB Setup Requests for Platinum UEs

New VS.RAB.AttEstabPS.Conv.Platinum

RAB.EstabPS.Cell Number of PS RAB Setup Requests for Platinum UEs Performing Conversational Services

New VS.RAB.SuccEstabCS.Platinum

RAB.EstabCS.Cell Number of Successful CS RAB Setups for Platinum UEs

New VS.RAB.SuccEstabCS.Conv.Platinum

RAB.EstabCS.Cell Number of Successful CS RAB Setups for Platinum UEs Performing Conversational Services

New VS.RAB.SuccEstabPS.Platinum

RAB.EstabPS.Cell Number of Successful PS RAB Setups for Platinum UEs

New VS.RAB.SuccEstabPS.Conv.Platinum

RAB.EstabPS.Cell Number of Successful PS RAB Setups for Platinum UEs Performing Conversational Services

Fault Management

No impact.

4.13.7 Impact on other Features


None


None

Impacted Features

The Platinum User Prioritizing feature affects other features as follows:

The initial SPI weight of platinum users is set to the highest value, 100%, which cannot be increased. Therefore, the performance of the following features related to SPI weight adjustment may be affected: WRFD-020132 Web Browsing Acceleration, WRFD-020133 P2P Downloading Rate Control during Busy Hour, and WRFD-140221 HSDPA Scheduling Based on UE Location.

The initial SPI weight of platinum users is set to 100% regardless of whether the Scheduling Based on UE Location function in the WRFD-01061209 HSUPA HARQ and Fast UL Scheduling in NodeB feature is enabled.

When WRFD-021103 Access Class Restriction, WRFD-020114 Domain Specific Access Control (DSAC), or WRFD-140213 Intelligent Access Class Control is enabled, users of access classes 0 through 9 are barred by turns and therefore cannot initiate services. If a platinum user is of access class 0 to 9, user experience will deteriorate. However, during the period when the access class of the platinum user is allowed to access the network, the RNC preferentially processes service requests from the platinum user.

RAN15.0




4-38

4.14 WRFD-150205 Layered Paging in Idle Mode (New/Optional)


The Layered Paging in Idle Mode feature is new in RAN15.0.

Due to the rapid rise of smartphone use in recent years, packet switched (PS) paging messages have accounted for an increasingly large proportion of paging messages. Conventionally, PS paging messages are sent to the entire location area (LA) or routing area (RA) because the RNC does not know on which cell a UE in idle mode camps. Due to the large paging area, the conventional paging mechanism causes high Uu-interface paging load and even PCH congestion.

To address this issue, the Layered Paging in Idle Mode feature has been introduced. This feature enables the RNC to perform layered paging on a UE in idle mode as follows:

1. First-layer paging: The RNC first pages the UE in the last camped-on cell and the cell's neighboring cells under the same RNC.

2. Second-layer paging: If the first-layer paging fails, the RNC pages the UE in the entire LA or RA.

Layered Paging in Idle Mode reduces the system paging load and prevents PCH congestion.


System Capacity

This feature reduces the paging load of UEs in idle mode and increases the system paging capacity.

Network Performance

If the second-layer paging is initiated, the end-to-end service establishment delay increases. The length of the increased delay depends on the length of the layered paging timer.

4.14.3 NEs


4.14.4 Hardware

No impact.


No impact.


License

An RNC-level license for this feature is added on the RNC side. Table 4-8 lists the license information for Layered Paging in Idle Mode.

Table 4-8 License information for Layered Paging in Idle Mode


WRFD-150205 Layered Paging Layered Paging in Idle RNC Mbps+Erlang

RAN15.0




4-39

in Idle Mode Mode


Layered Paging in Idle Mode introduces the following RNC-level parameters and MML commands.

Change Type


Modified parameter

PROCESSSWITCH: IDLE_LAYERED_PAGING_NRT_SWITCH

SET URRCTRLSWITCH

This parameter specifies whether to activate Layered Paging in Idle Mode for non-real-time services.

Modified parameter

PROCESSSWITCH: IDLE_LAYERED_PAGING_RT_SWITCH

SET URRCTRLSWITCH

This parameter specifies whether to activate Layered Paging in Idle Mode for real-time services.

New parameter

UsrLocInfoAgingTmr SET USTATETIMER

This parameter is an aging timer for subscriber information in the UE location information table.

New parameter

IdleLayeredPagingErl SET LICENSE This parameter specifies the licensed volume of CS traffic using Layered Paging in Idle Mode for an operator. The parameter unit is Erlang. When RAN Sharing is applied, the sum of the licensed volumes of CS traffic using Layered Paging in Idle Mode for all operators cannot exceed the CS traffic volume specified in the license for Layered Paging in Idle Mode.

New parameter

IdleLayeredPagingKbps

SET LICENSE This parameter specifies the licensed volume of PS traffic using Layered Paging in Idle Mode for an operator. The parameter unit is Kbit/s. When RAN Sharing is applied, the sum of the licensed volumes of PS traffic using Layered Paging in Idle Mode for all operators cannot exceed the PS traffic volume specified in the license for Layered Paging in Idle Mode.

New command

None ADD UUNIDLELAYERPGCELL

This command is used to add blacklisted cells where Layered Paging in Idle Mode is disabled.

New command

None RMV

UUNIDLELAYERPGCELL

This command is used to remove blacklisted cells where Layered Paging in Idle Mode is disabled.

New command

None LST

UUNIDLELAYERPGCELL

This command is used to query blacklisted cells where Layered Paging in Idle Mode is disabled.



../RNCParaHtml/mbsc/m-para/ustatetimer_usrlocinfoagingtmr.html

RAN15.0




4-40


Layered Paging in Idle Mode introduces the following RNC counters.

Change Type Counter ID Measurement Unit

Remarks

New VS.Paging1.Att1.Idle.NoneRealTime.Cell

PAGE.CELL Number of first-layer paging attempts for non-real-time services with Layered Paging in Idle Mode enabled

New VS.Paging1.Succ1.Idle.NoneRealTime.Cell

PAGE.CELL Number of successful first-layer paging attempts for non-real-time services with Layered Paging in Idle Mode enabled

New VS.Paging1.Att1.Idle.RealTime.Cell

PAGE.CELL Number of first-layer paging attempts for real-time services with Layered Paging in Idle Mode enabled

New VS.Paging1.Succ1.Idle.RealTime.Cell

PAGE.CELL Number of successful first-layer paging attempts for real-time services with Layered Paging in Idle Mode enabled

Fault Management

No impact.



None


None

Impacted Features

The Layered Paging in Idle Mode feature can work with the WRFD-140206 Layered Paging in URA_PCH feature to relieve PCH congestion on the network:

WRFD-140206 Layered Paging in URA_PCH reduces the Uu-interface paging load of UEs in the URA_PCH state.

Layered Paging in Idle Mode reduces the Uu-interface paging load of UEs in idle mode.

RAN15.0




4-41

4.15 WRFD-150206 Turbo IC (New/Optional)

4.15.1 Description

Turbo IC achieves high IC efficiency by implementing multiple-stage regeneration and cancellation based on the uplink E-DPDCH decoding result for HSUPA 2 ms TTI UEs. Turbo IC improves the demodulation SNR, which increases the uplink system capacity.


System Capacity

Turbo IC increases the uplink system capacity by improving E-DPDCH IC efficiency for HSUPA 2 ms TTI UEs. Gains from Turbo IC are noticeable when HSUPA 2 ms TTI UEs with continuous data transmission account for a large proportion of UEs in a cell or when HSUPA 2 ms TTI UEs with high throughput exist in a cell. In either of these cases, Turbo IC further increases the uplink system capacity compared with the gains from HSUPA UL Interference Cancellation. When the Independent

Demodulation of Signals from Multiple RRUs in One Cell feature is used, gains from Turbo IC are noticeable only if all UEs and services in each area covered by the RRUs are in either of the preceding cases.

Gains from Turbo IC depend on the scenario. There are two types of typical scenarios:

WBBPf boards form an uplink resource group.

− In scenarios where there are 4 full buffer HSUPA 2 ms TTI UEs, Turbo IC increases the uplink cell throughput by 10% to 30% compared with HSUPA UL Interference Cancellation and 30% to 70% compared with scenarios in which IC is not enabled. Full buffer UEs are UEs that perform continuous data transmission and have a large amount of data to be transmitted.

− In scenarios where there are 12 full buffer HSUPA 2 ms TTI UEs, Turbo IC increases the uplink cell throughput by 15% to 30% compared with HSUPA UL Interference Cancellation and 30% to 60% compared with scenarios in which IC is not enabled.

WBBPf boards and other boards form an uplink resource group.



Network Performance

Replace the WBBPa or WBBPb board with a WBBPf board to maximize the gains provided by Turbo IC. The reason is as follows:

Assume that a WBBPa or WBBPb board and a WBBPf board form an uplink resource group. When the INTERBOARDICSW parameter is set to FULL_IC for a WBBPa or WBBPb board to benefit from Turbo IC gains provided by a WBBPf board, UEs whose data channels are carried on the WBBPa or WBBPb board must set up DPCCHs on the WBBPf board for power control purposes. In addition, UEs whose downlink services are carried on HSDPA channels must set up another HS-DPCCH on the WBBPf board. The new channels consume extra resources, which reduces the total number of users supported by the system and decreases the access success rate.

4.15.3 NEs

Turbo IC is implemented on the NodeB.

../NodeBParaHtml/comm/para/NodeBAlgPara-icMode.html

RAN15.0




4-42

4.15.4 Hardware

Turbo IC has the following hardware requirements for the NodeB:

3900 series base stations (except the BTS3902E) and BTS3803E base stations must be configured with the WBBPf board to support Turbo IC.

To support inter-board IC, 3900 series base stations (except the BTS3902E) and BTS3803E base stations must be configured with the WBBPf board and at least one WBBPd or WBBPf board must be configured in slot 2 or 3. To support inter-board Turbo IC, all boards in the uplink resource group must be configured as WBBPf boards.

UEs with their data channels carried on a WBBPa or WBBPb board can share the IC gains from a WBBPd or WBBPf board only when the following conditions are met:

− The WBBPa or WBBPb board and the WBBPd or WBBPf board are installed in one BBU to form an uplink resource group.

− INTERBOARDICSW is set to FULL_IC.

− Inter-board data channels are configured for the UEs to set up control channels on the WBBPd or WBBPf board.


Turbo IC does not affect the Uu, Iub, Iur, or Iu interface.


License

A cell-level license control item has been added to the NodeB for this feature.


The following parameter has been introduced on the NodeB side to accommodate this feature.

Change Type Parameter ID


New TURBOIC ADD ULOCELL /MOD ULOCELL

This new cell-level switch controls whether to enable Turbo IC for a cell. When this switch is turned on in a cell, the cell supports Turbo IC.


The following counters have been introduced on the NodeB side to accommodate this feature.


Description

New VS.HSUPA.Thruput.ROTAll

HSUPA.LOCELL Total HSUPA user throughput in a cell when the Uu interface load varies within the allowed range

../NodeBParaHtml/comm/para/NodeBAlgPara-icMode.html

../NodeBParaHtml/comm/para/ULoCell-turboIC.html

RAN15.0




4-43


Description

New VS.HSUPA.Thruput.ROTMor3

HSUPA.LOCELL HSUPA user throughput in a cell when the Uu interface load is 3 dB or higher













New VS.HSUPA.DataTtiNum.ROTMor3

HSUPA.LOCELL Number of TTIs in which HSUPA users in a cell have data to transmit when the Uu interface load is 3 dB or higher









RAN15.0




4-44


Description





New VS.HSUPA.TurboIC. Number

HSUPA.LOCELL Average number of users with Turbo IC enabled in a cell

New VS.HSUPA.TTI2 msUserNumber.0

HSUPA.LOCELL Average number of HSUPA 2 ms TTI UEs whose average rate is less than 150 kbit/s in a cell


HSUPA.LOCELL Average number of HSUPA 2 ms TTI UEs whose average rate is greater than or equal to 150 kbit/s but less than 700 kbit/s in a cell








HSUPA.LOCELL Average number of HSUPA 2 ms TTI UEs whose average rate is greater than or equal to 4000 kbit/s but less than 12,000 kbit/s in a cell

Fault Management

After Turbo IC is enabled, an alarm indicating that Turbo IC cannot be used will be reported if any of the following occurs:

The license for Turbo IC has not been obtained.

HSUPA UL IC has not been activated.

No WBBPf board exists in the uplink resource group.

RAN15.0




4-45

4.15.7 Related Features


This feature requires the WRFD-01061403 HSUPA 2 ms TTI and WRFD-010691 HSUPA UL Interference Cancellation features.


None

Impacted Features

When Turbo IC is enabled, gains from HSUPA Time Division Scheduling decrease. Likewise, when HSUPA Time Division Scheduling is enabled, gains from Turbo IC decrease. This is because Turbo IC improves demodulation performance by canceling MUI while the HSUPA Time Division Scheduling feature prevents MUI wherever possible by enabling the signals of UEs to be transmitted during different time divisions. When there is less MUI or multipath interference to be canceled, there are fewer gains from Turbo IC.

4.16 WRFD-150207 4C-HSDPA (New/Optional)


4C-HSDPA was introduced by 3GPP Release 10. 4C-HSDPA uses three or four carriers enabled with 64QAM for the HSDPA transmission of a UE, which increases the UE data rate.

When PS best effort (BE) services, streaming services, or combined services that include PS BE or streaming services are carried on the HS-DSCH, these services can use 4C-HSDPA. In the uplink, the UE can use DCH, HSUPA, or DC-HSUPA. The signaling radio bearer (SRB) for the UE is carried over DCH, HSDPA, or HSUPA.

4C-HSDPA does not apply to CS services, IP Multimedia Subsystem (IMS) signaling, PS conversational services, or SRB signaling, because the gains provided by this feature are not noticeable for services that have only a small amount of data to transmit and have low transmission delay requirements.


System Capacity

4C-HSDPA increases the cell load in the uplink, consumes more channel element (CE) resources, and affects the number of multi-carrier HSDPA UEs supported by baseband processing boards.

4C-HSDPA slightly increases the cell load in the uplink. The cell load increase is represented by an increase in the uplink RTWP.

The increase in the uplink RTWP varies depending on the number of online 4C-HSDPA UEs. When the number of online 4C-HSDPA UEs increases, the HS-DPCCH has more data to transmit in the uplink and consequently requires more power resources. Uplink interference increases as a result. The Dynamic Configuration of HSDPA CQI Feedback Period feature can be enabled to reduce the uplink RTWP.

For details about the Dynamic Configuration of HSDPA CQI Feedback Period feature, see Dynamic Configuration Based on the Uplink Load Feature Parameter Description.

4C-HSDPA UEs consume one CE more than SC-HSDPA UEs.

A baseband processing board supports more SC-HSDPA UEs than 4C-HSDPA UEs.

Dynamic%20Configuration%20Based%20on%20the%20Uplink%20Load.htm

Dynamic%20Configuration%20Based%20on%20the%20Uplink%20Load.htm

RAN15.0




4-46

Network Performance

4C-HSDPA increases the single-user downlink throughput and deteriorates the uplink cell edge coverage.

Increased single-user downlink throughput

The single-user downlink throughput of 4C-HSDPA is close to four times that of SC-HSDPA. The increase in the single-user downlink throughput is noticeable even at the cell edge.

However, the increase in the single-user downlink throughput varies depending on the load of other 4C-HSDPA cells in the same sector. For example, when other 4C-HSDPA cells in the same sector have heavy loads, the gain provided by 4C-HSDPA is small. This is because the NodeB considers the rate fairness among 4C-HSDPA and SC-HSDPA UEs when the load is heavy and the downlink resources (such as power resources and code resources) are insufficient. In this case, the throughput of 4C-HSDPA UEs is not significantly higher than that of SC-HSDPA or DC-HSDPA UEs.

Deteriorated uplink cell edge coverage

4C-HSDPA slightly deteriorates the uplink cell edge coverage because 4C-HSDPA UEs need to report the CQI information about all serving cells and consequently require higher uplink power.

4.16.3 NEs

This feature is implemented on the NodeB and RNC.

This feature requires support from the UE. The UE must belong to HS-DSCH category 29 or higher.

4.16.4 Hardware

Dependency on RNC hardware

None

Dependency on NodeB hardware

− The BTS3812A, BTS3812E, and BTS3812AE must be configured with the EBBI, EBOI, EDLP+EULP, or EDLP+EULPd boards to supporta maximum of three carriers for the HSDPA transmission of a UE. The three carriers must operate in the same frequency band. The HBBI and HDLP boards do not support 4C-HSDPA.

− The DBS3800 must be configured with the EBBC or EBBCd board to support a maximum of three carriers for the HSDPA transmission of a UE. The three carriers can operate in different frequency bands.

− The 3900 series base stations must be configured with the WBBPb, WBBPd, or WBBPf board to support 3C-HSDPA and must be configured with the WBBPd or WBBPf board to support 4C-HSDPA.

− The BTS3902E and BTS3803E do not support 4C-HSDPA.

Table 4-9 presents an example of the hardware configuration of a NodeB configured with three sectors.

Table 4-9 Example of the hardware configuration of a NodeB configured with three sectors

Scenario Base Station Type Hardware Configuration

3C-HSDPA DBS3800 The DBS3800 must be configured with two interconnected BBU3806s, and each BBU must be configured with an EBBC or EBBCd board.

BTS3812A, BTS3812E, and BTS3812AE

Each NodeB of these types must be configured either with at least two EBBI or EBOI boards or with two EDLP boards and one EULP or EULPd board.

RAN15.0




4-47


3900 series base stations (excluding the BTS3902E)

Each 3900 series base station must be configured with two WBBPb, two WBBPd, or two WBBPf boards.

4C-HSDPA 3900 series base stations Each 3900 series base station must be configured with three WBBPd or WBBPf boards (in any combination).


4C-HSDPA adds new information elements (IEs) to or enhances the existing IEs in certain signaling messages over the Iub and Uu interfaces.

Iub

The NodeB sends an AUDIT RESPONSE or RESOURCE STATUS INDICATION message to the RNC when one of the following occurs:

The NodeB receives an AUDIT REQUEST message.

A cell is established.

The capability of a cell changes.

The AUDIT RESPONSE or RESOURCE STATUS INDICATION message includes the "Local Cell Information" IE, which carries the multi-carrier HSDPA capability of a cell. IEs in the "Local Cell Information" IE have been enhanced as follows:

"Multi Cell Capability Info" IE

This IE notifies the RNC of the multi-carrier HSDPA capability of a cell and of the intra-band secondary cells that can form a cell group with this cell.

"Dual Band Capability Info" IE

This IE notifies the RNC of the multi-band capability of a cell and of the inter-band secondary cells that can form a cell group with this cell.

"Cell Capability Container" IE

This IE notifies the RNC of whether a cell supports 3C-HSDPA or 4C-HSDPA.

In certain signaling messages used during the radio link setup procedure, IEs carrying information about secondary cells have been modified, as described in Table 4-10.

Table 4-10 Impact on signaling messages used during the radio link setup procedure

Signaling Message Impacted IE Description

RADIO LINK ADDITION REQUEST

Additional HS Cell Information RL Addition

Now, these IEs report information about a maximum of three secondary cells.

RADIO LINK ADDITION RESPONSE

RADIO LINK ADDITION FAILURE

HS-DSCH Secondary Serving Cell Change Information Response

RADIO LINK RECONFIGURATION

Additional HS Cell Information RL Reconf Prep

RAN15.0




4-48


PREPARE

RADIO LINK RECONFIGURATION READY

Additional HS Cell Information Response

Uu

Table 4-11 describes the Uu messages and IEs affected by 4C-HSDPA.

Table 4-11 Uu messages and IEs affected by 4C-HSDPA


RRC CONNECTION SETUP COMPLETE

UE CAPABILITY INFORMATION

UE radio access capability

The "Radio Access Capability Band Combination List" IE has been added to this IE. The new IE specifies the combination of frequency bands supported by a UE and the number of frequencies in each frequency band.

Physical channel capability

The "HS-DSCH physical layer category extension 4" and "HS-DSCH physical layer category extension 5" IEs have been added to this IE. The "HS-DSCH physical layer category extension 4" IE specifies whether a UE belongs to HS-DSCH category 29 or 30. The "HS-DSCH physical layer category extension 5" IE specifies whether a UE belongs to HS-DSCH category 31 or 32.

UE radio access capability extension

The "Additional Secondary Cells" and "Non-contiguous multi-cell" IEs have been added to this IE. These IEs specify the numbers of intra-band adjacent frequencies and intra-band non-adjacent frequencies supported by a UE, respectively.

RADIO BEARER SETUP

RADIO BEARER RECONFIGURATION

RADIO BEARER RELEASE

PHYSICAL CHANNEL RECONFIGURATION

CELL UPDATE CONFIRM

TRANSPORT CHANNEL RECONFIGURATION

INTER RAT HANDOVER INFO

None The "Additional downlink secondary cell info list FDD" IE has been added. This IE includes a maximum of two "Downlink secondary cell info FDD" IEs, which carry information about the 2nd and 3rd secondary cells.

"DPCH compressed mode info" IE in the "Downlink information common for all radio links" IE

The "Frequency specific compressed mode" IE has been added to the "DPCH compressed mode info" IE. The new IE specifies whether to perform measurements in compressed mode in cells operating in specified frequencies.

RAN15.0




4-49


ACTIVE SET UPDATE

MEASUREMENT CONTROL

Inter-frequency measurement

The "Frequency index list for enhanced measurement" IE has been added to this IE. The new IE specifies the frequencies that need to be measured in non-compressed mode during the inter-frequency handover.

DPCH Compressed Mode Status Info

The "Frequency specific compressed mode" IE has been added to this IE. The new IE specifies the frequencies that need to be measured in compressed mode.


License



The following parameters and switches have been introduced on the RNC side to accommodate this feature.

Table 4-12 New RNC parameters and switches

Parameter and Switch Changes

Parameter ID Switch Name MML Command

New parameter

SecCellLdbDrdChoice - SET UDRD

New parameter

SecCellLdbDrdChoice - ADD UCELLDRD

MOD UCELLDRD

New parameter

DCMIMOor4CHSDPASwitch - SET UFRC

New parameter

InterPlmnMultiCarrSwitch - SET UOPERATORSHARINGMODE

New parameter

McHsdpaUserNumThd - ADD UCELLDYNSHUTDOWN

MOD UCELLDYNSHUTDOWN

New parameter

DlHghRateMacdSizeAdjSwitch

- SET UDPUCFGDATA

New parameter

MacPduMaxSizeForDlHighRate

- SET UFRC

New parameter

MbrThdForDlHighRate - SET UFRC

../RNCParaHtml/mbsc/m-para/ucelldrd_seccellldbdrdchoice.html


../RNCParaHtml/mbsc/m-para/ufrc_dcmimoor4chsdpaswitch.html

../RNCParaHtml/mbsc/m-para/uoperatorsharingmode_interplmnmulticarrswitch.html

../RNCParaHtml/mbsc/m-para/ucelldynshutdown_mchsdpausernumthd.html

../RNCParaHtml/mbsc/m-para/udpucfgdata_dlhghratemacdsizeadjswitch.html

../RNCParaHtml/mbsc/m-para/udpucfgdata_dlhghratemacdsizeadjswitch.html

../RNCParaHtml/mbsc/m-para/ufrc_macpdumaxsizefordlhighrate.html

../RNCParaHtml/mbsc/m-para/ufrc_macpdumaxsizefordlhighrate.html

../RNCParaHtml/mbsc/m-para/ufrc_mbrthdfordlhighrate.html

RAN15.0




4-50



New switch CfgSwitch CFG_HSDPA_4C_SWITCH


New switch HspaPlusSwitch HSDPA_4C ADD UCELLALGOSWITCH

MOD UCELLALGOSWITCH

New switch RetryCapability HSDPA_4C SET UFRC

NOTE

The hyphen (-) in Table 4-12 indicates that a parameter, not a switch, has been introduced.

The following MML commands have been introduced on the NodeB side to accommodate this feature.

Table 4-13 New NodeB MML commands


ADD NODEBMULTICELLGRP

RMV NODEBMULTICELLGRP

LST NODEBMULTICELLGRP

These commands are used to add, query, or remove a multi-carrier cell group, respectively.

ADD NODEBMULTICELLGRPITEM

RMV NODEBMULTICELLGRPITEM

These commands are used to add a cell to a multi-carrier cell group or remove a cell from a multi-carrier cell group, respectively.

The following MML commands have been removed from the NodeB side.

Table 4-14 Removed NodeB MML commands


ADD DLDUALCELLGRP

LST DLDUALCELLGRP

RMV DLDUALCELLGRP

These commands are used to add, query, or remove a DC-HSDPA group, respectively.

ADD ULDUALCELLGRP

LST ULDUALCELLGRP

RMV ULDUALCELLGRP

These commands are used to add, query, or remove a DC-HSUPA group, respectively.

NOTE

After RAN has been upgraded to RAN15.0, DC-HSDPA and DC-HSUPA groups are configured and adjusted through the ADD NODEBMULTICELLGRP, LST NODEBMULTICELLGRP, and RMV NODEBMULTICELLGRP commands. Existing

DC-HSDPA and DC-HSDUPA groups automatically become multi-carrier cell groups.

../RNCParaHtml/mbsc/m-para/ucorrmalgoswitch_cfgswitch.html

../RNCParaHtml/mbsc/m-para/ucellalgoswitch_hspaplusswitch.html

../RNCParaHtml/mbsc/m-para/ufrc_retrycapability.html

RAN15.0




4-51


The following counters have been introduced on the RNC side to accommodate this feature. No counters have been introduced on the NodeB side.

Table 4-15 New counters for 4C-HSDPA


Description

VS.HSDPA.UE.Mean.CAT29

HSDPA.Cell Average number of Category 29 HSDPA users in a cell



VS.HSDPA.UE.Max.CAT29

HSDPA.Cell Maximum number of Category 29 HSDPA users in a cell



VS.HSDPA.RAB.3C.AttEstab

HSDPA.Cell Number of RAB Setup Attempts for Cell When 3C-HSDPA Applied

VS.HSDPA.RAB.3C.SuccEstab

HSDPA.Cell Number of Successful RAB Setups for Cell When 3C-HSDPA Applied

VS.HSDPA.RAB.AbnormRel.3C

HSDPA.Cell Number of Abnormally Released RABs for Cell When 3C-HSDPA Applied (RF Exceptions Considered)

VS.HSDPA.RAB.NormRel.3C

HSDPA.Cell Number of Normally Released RABs for Cell When 3C-HSDPA Applied

VS.HSDPA.RAB.4C.AttEstab

HSDPA.Cell Number of RAB Setup Attempts for Cell When 4C-HSDPA Applied

VS.HSDPA.RAB.4C.SuccEstab

HSDPA.Cell Number of Successful RAB Setups for Cell When 4C-HSDPA Applied

VS.HSDPA.RAB.AbnormRel.4C

HSDPA.Cell Number of Abnormal Released RABs for Cell When 4C-HSDPA Applied (RF Exceptions Considered)

VS.HSDPA.RAB.NormRel.4C

HSDPA.Cell Number of Normally Released RABs for Cell When 4C-HSDPA Applied

VS.HSDPA.4C.PRIM.UE.Mean.Cell

HSDPA.Cell Average Number of 4C-HSDPA UEs Using This Cell as the Primary Carrier Cell

VS.HSDPA.3C.PRIM.UE.Mean.Cell

HSDPA.Cell Average Number of 3C-HSDPA UEs Using This Cell as the Primary Carrier Cell

VS.HSDPA.MC.SEC.UE.Mean.Cell

HSDPA.Cell Average Number of 4C-HSDPA/DB-HSDPA/DC-HSDPA UEs Using This Cell as the Secondary Carrier Cell

VS.MeanTCP.HSDPA.MC

RTWPTCP.Cell Average DL Transmit Power of 4C-HSDPA/DB-HSDPA/DC-HSDPA UEs for Cell

VS.MaxTCP.HSDPA.MC RTWPTCP.Cell Maximum DL Transmit Power of 4C-HSDPA/DB-HSDPA/DC-HSDPA UEs for Cell

RAN15.0




4-52


Description

VS.MinTCP.HSDPA.MC RTWPTCP.Cell Minimum DL Transmit Power of 4C-HSDPA/DB-HSDPA/DC-HSDPA UEs for Cell

Fault Management

4C-HSDPA adds a new alarm on the RNC side: ALM-UMTS Cell MC-HSDPA Function Fault.

The Iub and Uu interface trace functions on the LMT support 4C-HSDPA UEs.



WRFD-150208 Flexible DC/DB-HSDPA

WRFD-010683 Downlink 64 QAM

WRFD-150209 DB-HSDPA

If the 4C-HSDPA cells in a multi-carrier cell group operate in two different frequency bands, all 4C-HSDPA cells must have DB-HSDPA enabled.

WRFD-010696 DC-HSDPA

If multiple 4C-HSDPA cells in a multi-carrier cell group operate in the same frequency band, all of these cells must have DC-HSDPA enabled.


WRFD-010686 CPC-DTX/DRX

WRFD-010687 CPC-HS-SCCH Less Operation

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

WRFD-021308 Extended Cell Coverage up to 200km

Impacted Features

4C-HSDPA is affected when the following features are enabled:

WRFD-010617 VoIP over HSPA/HSPA+

− 4C-HSDPA cannot be used for voice over IP (VoIP) services.

− 4C-HSDPA can be used for VoIP services in VoIP+PS BE or VoIP+streaming combined services.

WRFD-010619 CS voice over HSPA/HSPA+

− 4C-HSDPA cannot be used for CS services.

− 4C-HSDPA can be used for CS services in CS+PS BE or CS+streaming combined services.

WRFD-020134 Push to Talk

− 4C-HSDPA cannot be used for push to talk (PTT) services.

− 4C-HSDPA can be used for PTT services in PTT+PS BE or PTT+streaming combined services.

4C-HSDPA affects the following features:

WRFD-140217 Inter-Frequency Load Balancing Based on Configurable Load Threshold

RAN15.0




4-53

− When the number of 4C-HSDPA UEs and their traffic volume are small, 4C-HSDPA does not affect the Inter-Frequency Load Balancing Based on Configurable Load Threshold feature.

− When the number of 4C-HSDPA UEs and their traffic volume are large, the gain provided by the Inter-Frequency Load Balancing Based on Configurable Load Threshold feature decreases.

NOTE

4C-HSDPA uses joint scheduling to balance the load across different carriers. The load balancing effect depends on the number of 4C-HSDPA UEs and the traffic volume. When the number of 4C-HSDPA UEs and the traffic volume are large, the load balancing effect is noticeable, but the gain provided by the Inter-Frequency Load Balancing Based on Configurable Load Threshold feature decreases.

WRFD-140215 Dynamic Configuration of HSDPA CQI Feedback Period

4C-HSDPA can be used with the Dynamic Configuration of HSDPA CQI Feedback Period feature.

When these two features are used together, the gain (RTWP reduction) provided by the Dynamic Configuration of HSDPA CQI Feedback Period feature slightly increases, compared with when SC-HSDPA and Dynamic Configuration of HSDPA CQI Feedback Period are used together. The uplink CQI feedback overhead for 4C-HSDPA is slightly greater than that for SC-HSDPA, so the received total wideband power (RTWP) of 4C-HSDPA is higher than that of SC-HSDPA. The Dynamic Configuration of HSDPA CQI Feedback Period feature helps reduce the RTWP.

WRFD-021304 RAN Sharing Introduction Package, WRFD-021305 RAN Sharing Phase 2, and WRFD-021311 MOCN Introduction Package

In RAN sharing and multioperator core network (MOCN) scenarios, the RNC determines whether to use cells belonging to different operators for the HSDPA transmission of a 4C-HSDPA UE based on the parameter settings.

WRFD-010703 HSPA+ Downlink 84Mbit/s per User

After 4C-HSDPA is introduced, the HSPA+ Downlink 84Mbit/s per User feature can depend on the following features:

− WRFD-010689 HSPA+ Downlink 42Mbps per User

− WRFD-150207 4C-HSDPA

4.17 WRFD-150208 Flexible DC/DB-HSDPA (New/Optional)


The Flexible DC/DB-HSDPA feature allows any inter-frequency co-coverage cells that meet certain requirements to form a multi-carrier cell group. Working in resource pool mode, cells in the multi-carrier cell group can dynamically form DC-HSDPA, DB-HSDPA, 4C-HSDPA, DC-HSDPA+MIMO, DB-HSDPA+MIMO, and 4C-HSDPA+MIMO groups, which fulfills the service requirements of different UEs.


System Capacity

This feature reduces the difference between the downlink load of cells in a multi-carrier cell group. The effect of this feature depends on the number of DC-HSDPA, DB-HSDPA, and 4C-HSDPA UEs and their traffic volume. A larger number of DC-HSDPA, DB-HSDPA, and 4C-HSDPA UEs and a larger traffic volume results in smaller difference between the downlink load of cells.

Network Performance

Cells in a multi-carrier cell group have the same time offset (specified by the Tcell parameter). When multiple cells (three or four) served by the same RRU in a sector transmit data at full power, the peak-to-average ratio (PAR) of the RRU increases if a higher-order modulation scheme is used in the

../RNCParaHtml/mbsc/m-para/ucell_tcell.html

RAN15.0




4-54

downlink. As a result, cell throughput may decrease. On live networks, cells in the same sector do not transmit data at full power for a long period of time, and therefore cell throughput only slightly decreases.

After Flexible DC/DB-HSDPA is activated in networks with a low load, the data rates of DC-HSDPA, DB-HSDPA, and 4C-HSDPA UEs increase because UEs can fully utilize frequency resources. As network load increases, the gain provided by this feature decreases. The difference between the downlink load of cells in a multi-carrier cell group before this feature is activated also affects the gain provided by this feature. A larger difference results in a greater gain.

4.17.3 NEs


This feature requires support from the UE. The UE must belong to HS-DSCH category 21 or higher.

4.17.4 Hardware


None


− The BTS3812A, BTS3812E, and BTS3812AE can be configured with a maximum of three carriers that operate in the same frequency band. The BTS3812A, BTS3812E, and BTS3812AE must be configured with the EBBI, EBOI, EDLP+EULP, or EDLP+EULPd boards. The HBBI and HDLP boards do not support this feature.

− The DBS3800 can be configured with a maximum of three carriers and the carriers can operate in different frequency bands. The DBS3800 must be configured with the EBBC or EBBCd board.

− The 3900 series base stations (excluding the BTS3902E) support Flexible DC/DB-HSDPA. Only the 3900 series base stations support 4C-HSDPA. Only the 3900 series base stations can enable MIMO for frequencies where Flexible DC/DB-HSDPA is activated. The 3900 series base stations must be configured with the WBBPb, WBBPd, or WBBPf board.

− The BTS3803E does not support Flexible DC/DB-HSDPA.

Table 4-16 presents an example of the hardware configuration of a NodeB that is configured with three sectors.

Table 4-16 Example of the hardware configuration of a NodeB that is configured with three sectors


Three carriers (with 4C-HSDPA)

DBS3800 The DBS3800 must be configured with two BBU3806s. The two BBU3806s must be interconnected, and each must be configured with an EBBC or EBBCd board.

BTS3812A, BTS3812E, and BTS3812AE

The BTS3812A, BTS3812E, and BTS3812AE must be configured with at least two EBBI or EBOI boards. Alternatively, the BTS3812A, BTS3812E, and BTS3812AE must be configured with two EDLP boards and one EULP or EULPd board.

3900 series base stations (excluding the 3902E)

The 3900 series base stations (excluding the BTS3902E) must be configured with at least two WBBPb, WBBPd, or WBBPf boards (in any combination).

Three carriers (with 3900 series base The 3900 series base stations (excluding the

RAN15.0




4-55

DC/DB/4C-HSDPA+MIMO)

stations (excluding the 3902E)

BTS3902E) must be configured with at least two WBBPf boards, three WBBPb boards, three WBBPd boards, or three boards that can be any combination of WBBPb, WBBPd, and WBBPf boards.

Four carriers 3900 series base stations (excluding the 3902E)

The 3900 series base stations (excluding the BTS3902E) must be configured with at least three WBBPb, WBBPd, or WBBPf boards (in any combination).

Four carriers (with DC/DB/4C-HSDPA+MIMO)

3900 series base stations (excluding the 3902E)

The 3900 series base stations (excluding the BTS3902E) must be configured with at least three WBBPd or WBBPf boards (in any combination).


The Flexible DC/DB-HSDPA feature affects the Iub interface as follows:

Affects the "Possible Secondary Serving Cell" information element (IE).

The NodeB sends an AUDIT RESPONSE or RESOURCE STATUS INDICATION message to the RNC when one of the following occurs:

− The NodeB receives an AUDIT REQUEST message.

− A cell is established.

− The capability of a cell changes.

The AUDIT RESPONSE or RESOURCE STATUS INDICATION message includes the "Multi Cell Capability Info" and "Dual Band Capability Info" IEs. Each of these two IEs includes one or multiple "Possible Secondary Serving Cell" IEs. The "Multi Cell Capability Info" IE carries the list of intra-band candidate secondary cells and the "Dual Band Capability Info" IE carries the list of inter-band candidate secondary cells.

Adds a new IE "HS-DSCH FDD Secondary Serving Information".

The "HS-DSCH FDD Secondary Serving Information" IE is added to the radio link setup messages and radio link reconfiguration messages. This IE notifies the NodeB of the secondary cell configuration.


License

A NodeB-level license control item has been added to the NodeB for this feature.


The following parameters have been introduced on the RNC side to accommodate this feature.

Table 4-17 New RNC parameters


SecCellLdbDrdChoice

SET UDRD Load factor that the RNC considers when selecting a secondary cell. This is an RNC-level parameter.

When this parameter is set to UserNumber, the RNC selects a secondary cell based on the number of HSDPA users in the secondary cell. When this parameter is set to Power, the

../RNCParaHtml/mbsc/m-para/udrd_seccellldbdrdchoice.html

../RNCParaHtml/mbsc/m-para/udrd_seccellldbdrdchoice.html

RAN15.0




4-56


RNC selects a secondary cell based on the downlink power of the secondary cell.

SecCellLdbDrdChoice

ADD UCELLDRD

MOD UCELLDRD

Load factor that the RNC considers when selecting a secondary cell. This is a cell-level parameter.

When this parameter is set to UserNumber, the RNC selects a secondary cell based on the number of HSDPA users in the secondary cell. When this parameter is set to Power, the RNC selects a secondary cell based on the downlink power of the secondary cell.

InterPlmnMultiCarrSwitch

SET UOPERATORSHARINGMODE

Whether to allow a DC-HSDPA, DB-HSDPA, or 4C-HSDPA user to use cells belonging to different operators for HSDPA transmission.

When this parameter is set to YES, the user can use cells belonging to different operators for HSDPA transmission. When this parameter is set to NO, the user cannot use cells belonging to different operators for HSDPA transmission, and the user can use only its operator's cell for HSDPA transmission.

McHsdpaUserNumThd

ADD UCELLDYNSHUTDOWN

MOD UCELLDYNSHUTDOWN

Multi-carrier HSDPA user number threshold.

When the number of DC-HSDPA, DB-HSDPA, and 4C-HSDPA users in a cell is less than or equal to this threshold, the cell can be dynamically shut down if other conditions are met.

The following commands have been introduced on the NodeB side to accommodate this feature.

Table 4-18 New NodeB commands


ADD NODEBMULTICELLGRP

LST NODEBMULTICELLGRP

RMV NODEBMULTICELLGRP

These commands are used to add, query, or remove a multi-carrier cell group.

ADD NODEBMULTICELLGRPITEM

RMV NODEBMULTICELLGRPITEM

These commands are used to add a cell to or remove a cell from a multi-carrier cell group.


The following counters have been introduced on the RNC side to accommodate this feature.

Table 4-19 New RNC counters

Counter ID Measurement Unit Description

VS.MeanTCP.HSDPA.MC

RTWPTCP.Cell Average DL Transmit Power of DC-HSDPA/DB-HSDPA/4C-HSDPA/DB-HSDPA+MIMO/DC-







RAN15.0




4-57

Counter ID Measurement Unit Description

HSDPA+MIMO/4C-HSDPA+MIMO UEs for Cell

VS.MaxTCP.HSDPA.MC

RTWPTCP.Cell Maximum DL Transmit Power of DC-HSDPA/DB-HSDPA/4C-HSDPA/DB-HSDPA+MIMO/DC-HSDPA+MIMO/4C-HSDPA+MIMO UEs for Cell

VS.MinTCP.HSDPA.MC

RTWPTCP.Cell Minimum DL Transmit Power of DC-HSDPA/DB-HSDPA/4C-HSDPA/DB-HSDPA+MIMO/DC-HSDPA+MIMO/4C-HSDPA+MIMO UEs for Cell

This feature has no impact on NodeB counters.

Fault Management

This feature affects the following alarms on the NodeB side:

ALM-28206 Local Cell Capability Decline

A new trigger condition is added for this alarm. When a cell in a multi-carrier cell group does not support the Flexible DC/DB-HSDPA feature due to hardware limitations and the multi-carrier cell group consists of more than two cells, this alarm is reported for all cells in the multi-carrier cell group.

ALM-26811 Configured Capacity Limit Exceeding Licensed Limit

A new trigger condition is added for this alarm. When a multi-carrier cell group consists of more than two cells and the license for the Flexible DC/DB-HSDPA feature is not activated, this alarm is reported.



If multiple cells in a multi-carrier cell group operate in the same frequency band, the cells that operate in the same frequency band must have the WRFD-010696 DC-HSDPA feature enabled.

If cells in a multi-carrier cell group operate in different frequency bands, all cells in the group must have the WRFD-150209 DB-HSDPA feature enabled.


If the Flexible DC/DB-HSDPA feature is used with the WRFD-010684 2×2 MIMO feature in a cell, the Primary/Secondary common Pilot (PSP) mode must be used for the MIMO. For details, see MIMO Feature Parameter Description.

Impacted Features

RAN Sharing and MOCN

The Flexible DC/DB-HSDPA feature can be enabled in RAN sharing or Multi-Operator Core Network (MOCN) scenarios.

When the Flexible DC/DB-HSDPA feature is enabled in RAN sharing or MOCN scenarios, run the RNC MML command SET UOPERATORSHARINGMODE to set InterPlmnMultiCarrSwitch to YES. This allows UEs to use cells belonging to different operators as primary and secondary cells, but each UE must use its operator's cell as the primary cell. The secondary cell can belong to other operators. When InterPlmnMultiCarrSwitch is set to NO, the UE must use its operator's cells as the primary and secondary cells.

MIMO.htm

MIMO.htm



RAN15.0




4-58

DC-HSUPA

The Flexible DC/DB-HSDPA feature does not affect the configuration of DC-HSUPA.

When the Flexible DC/DB-HSDPA feature is used with DC-HSUPA, a DC-HSDPA UE can use DC-HSUPA only when the DC-HSUPA group is the same as the DC-HSDPA group.

Figure 4-10 shows an example of using the Flexible DC/DB-HSDPA feature and DC-HSUPA together.

Figure 4-10 Example of using the Flexible DC/DB-HSDPA feature and DC-HSUPA together

Figure 4-10 assumes that a multi-carrier cell group has three cells (F1, F2, and F3) and the Flexible DC/DB-HSDPA feature is activated in the cells. If F1 and F2 are configured as a DC-HSUPA group, only DC-HSDPA UEs that use F1 and F2 as the primary and secondary cells can establish DC-HSUPA connections in the uplink, and other DC-HSDPA UEs cannot establish DC-HSUPA connections in the uplink.

4.18 WRFD-150209 DB-HSDPA (New/Optional)


DB-HSDPA is an optional feature and is available from RAN15.0. It allows UEs to simultaneously establish connections in two inter-band co-coverage cells. With DB-HSDPA, UEs can use the resources of two cells operating on different frequency bands, which increases the peak UE throughput.


System Capacity

DB-HSDPA increases the single-user throughput and cell throughput in multi-band networks.

Increased single-user throughput

DB-HSDPA doubles single-user throughput both in the cell center and at the cell edge. Specifically, DB-HSDPA can provide up to 42 Mbit/s single-user throughput in the cell center with 64QAM enabled.

DB-HSDPA also increases average single-user throughput. The throughput gain is inversely proportional to DB-HSDPA cell loads and is directly proportional to the ratio of UEs supporting DB-HSDPA and the amount of data for a single UE to transmit in the downlink.

Increased cell throughput

DB-HSDPA increases cell throughput by 5% to 10%. The throughput gain is related to the number of UEs performing data transmission or the proportion of UEs supporting DB-HSDPA in the cell. When the number of UEs performing data transmission increases or the proportion of UEs supporting DB-HSDPA decreases in the cell, the throughput gain decreases.

Similar to DC-HSDPA and 4C-HSDPA UEs, a DB-HSDPA UE consumes one CE more than a SC-HSDPA UE.

RAN15.0




4-59

Network Performance

DB-HSDPA UEs report the CQI and hybrid automatic repeat request (HARQ) ACK/NACK information about the primary and secondary cells to the RNC in the primary cell. As a result, the uplink load of the primary cell is increased and the uplink coverage of DB-HSDPA UEs is reduced. In addition, DB-HSDPA UEs consume more CPU resources than SC-HSDPA UEs. The impact of DB-HSDPA on uplink load, uplink coverage, and CPU usage can be minimized by the Traffic-Based Activation and Deactivation of the Supplementary Carrier In Multi-carrier feature. This feature shuts down the secondary carrier when the traffic volume is low.

DB-HSDPA improves spectral efficiency and consequently slightly improves network KPIssuch as the access success rate and call drop rate.

4.18.3 NEs


This feature requires support from the UE:

The UE must belong to HS-DSCH category 21 or higher.

The UE notifies the RNC that it supports DB-HSDPA.

4.18.4 Hardware

The RF modules must support the frequency bands serving the cells in a DB-HSDPA group. Currently, Huawei RF modules do not support Band XI. Therefore, DB-HSDPA does not support the frequency band combination of 2100 MHz+1500 MHz in RAN15.0.

The hardware requirements of DB-HSDPA are as follows:

The BTS3812A, BTS3812E and BTS3812AE do not support DB-HSDPA.

The BTS3803E does not support DB-HSDPA.

The DBS3800 must be configured with a BBU3806 to support DB-HSDPA. In addition, the BBU3806 must be configured with the EBBC or EBBCd board. The BBU3806C does not support DB-HSDPA.

The 3900 series base stations (excluding the BTS3902E) must be configured with the WBBPb3, WBBPb4, WBBPd, or WBBPf board.


Iub

When the NodeB receives an AUDIT REQUEST message, the NodeB sends an AUDIT RESPONSE or RESOURCE STATUS INDICATION message to the RNC, notifying the RNC of the capability of a cell. DB-HSDPA adds a new IE, "Dual Band Capability Info", to the AUDIT RESPONSE and RESOURCE STATUS INDICATION messages. This new IE specifies the DB-HSDPA capability of a cell and the list of candidate secondary cells that can form a DB-HSDPA group with the cell. The "Dual Band Capability Info" IE includes the following IEs:

"Dual Band Capability": The value of this IE is Dual Band Capable when a cell supports DB-HSDPA.

"Possible Secondary Serving Cell List": This IE lists all the candidate secondary cells that can form a DB-HSDPA group with the current cell.

When the RNC uses the Radio Link Setup or Radio Link Addition procedure to establish a DB-HSDPA radio link (RL), the existing "Additional HS Cell Information RL Reconf Req" IE carries information about the secondary cell.

RAN15.0




4-60

Uu

DB-HSDPA has modified the "Physical Channel Capability" IE in the RRC CONNECTION SETUP COMPLETE and UE CAPABILITY INFORMATION messages:

Added a new IE "Radio Access Capability Band Combination List"

The new IE carries frequency bands supported by a UE.

Added a new IE "Inter-band Frequency measurements without compressed mode" to the "Measurement capability" IE

The new IE specifies the inter-frequency measurement capability of a UE.

The existing IE "Downlink secondary cell info FDD" in the following messages carry information about the secondary cell:

RRC CONNECTION SETUP

ACTIVE SET UPDATE

CELL UPDATE CONFIRM




RADIO BEARER RELEASE

RADIO BEARER SETUP


License



The following parameters have been introduced or modified on the RNC side to accommodate this feature.

Table 4-20 New and modified RNC parameters

Change Type


Description

New InterPlmnMultiCarrSwitch

SET UOPERATORSHARINGMODE

This parameter specifies whether to allow a UE to use cells belonging to different operators for HSDPA transmission.

Modified CfgSwitch SET UCORRMALGOSWITCH

An RNC-level DB-HSDPA function switch, CFG_HSDPA_DB_SWITCH, is added to this parameter.

Modified HspaPlusSwitch

ADD/MOD UCELLALGOSWITCH

A cell-level DB-HSDPA function switch, DB_HSDPA, is added to this parameter.






RAN15.0




4-61

Change Type


Description

Modified RetryCapability

SET UFRC An RNC-level DB-HSDPA DRD switch, DB_HSDPA, is added to this parameter.

Modified CmpSwitch: CMP_UU_ADJACENT_FREQ_CM_SWITCH


CMP_UU_ADJACENT_FREQ_CM_SWITCH is redefined. Earlier, this switch specifies whether the RNC activates the compressed mode before initiating an inter-frequency measurement on a neighboring frequency. Now, this switch specifies whether the RNC activates the compressed mod before initiating an inter-frequency measurement on a DC-HSDPA, DB-HSDPA, or 4C-HSDPA UE..

The following MML commands and parameters have been introduced on the NodeB side to accommodate this feature.

Table 4-21 New NodeB MML commands and parameters

MML Command and Parameter Changes


New command

- ADD/LST /RMV NODEBMULTICELLGRP

These commands are used to add, query, or remove a multi-carrier cell group.

New command and

- ADD/LST/RMV NODEBMULTICELLGRPITEM

These commands are used to add a cell to, query the cells in, or remove a cell from a multi-carrier cell group.

New parameter

multiCellGrpId ADD/RMV/LST NODEBMULTICELLGRP

This parameter uniquely identifies a multi-carrier cell group under a NodeB.

New parameter

multiCellGrpType

ADD/RMV/LST NODEBMULTICELLGRP

This parameter specifies the type of a multi-carrier cell group.

New parameter

uLoCellId ADD/RMV NODEBMULTICELLGRPITEM

This parameter specifies the ID of a local cell in a multi-carrier cell group.

NOTE

The hyphen (-) in Table 4-21 indicates that an MML command, not a parameter, is added.





../RNCParaHtml/mbsc/m-para/ucorrmalgoswitch_cmpswitch.html

../NodeBParaHtml/comm/para/NodeBMultiCellGrp-multiCellGrpId.html

../NodeBParaHtml/comm/para/NodeBMultiCellGrp-multiCellGrpType.html

../NodeBParaHtml/comm/para/NodeBMultiCellGrp-multiCellGrpType.html

RAN15.0




4-62


Change Type


Description

New VS.HSDPA.RAB.DB.AttEstab

HSDPA.Cell Number of RAB Setup Attempts for Cell When DB-HSDPA Applied

New VS.HSDPA.RAB.DB.SuccEstab

HSDPA.Cell Number of Successful RAB Setups for Cell When DB-HSDPA Applied

New VS.HSDPA.RAB.AbnormRel.DB

HSDPA.Cell Number of Abnormally Released RABs for Cell When DB-HSDPA Applied (RF Exceptions Considered)

New VS.HSDPA.RAB.NormRel.DB

HSDPA.Cell Number of Normally Released RABs for Cell When DB-HSDPA Applied

New VS.HSDPA.MC.SEC.UE.Mean.Cell


New VS.HSDPA.DB.PRIM.UE.Mean.Cell

HSDPA.Cell Average Number of DB-HSDPA UEs Using This Cell as the Primary Carrier Cell

New VS.MeanTCP.HSDPA.MC

RTWPTCP.Cell Average DL Transmit Power of 4C-HSDPA/DB-HSDPA/DC-HSDPA UEs for Cell

New VS.MaxTCP.HSDPA.MC RTWPTCP.Cell

Maximum DL Transmit Power of 4C-HSDPA/DB-HSDPA/DC-HSDPA UEs for Cell

New VS.MinTCP.HSDPA.MC RTWPTCP.Cell

Minimum DL Transmit Power of 4C-HSDPA/DB-HSDPA/DC-HSDPA UEs for Cell

New VS.HSDPA.MC.SEC.UE.Mean.Cell


The following counter has been introduced on the NodeB side to accommodate this feature.

Table 4-23 New NodeB counter

Change Type


Description

New VS.DataOutput.DBHSDPA.Traffic

HSDPA.LOCELL

MAC-ehs traffic volume of DB-HSDPA/DB-HSDPA+MIMO users

Fault Management

On the RNC side

RAN15.0




4-63

− ALM-22241 UMTS Cell MC-HSDPA Function Fault is added. This alarm is reported when the establishment of a DB-HSDPA cell fails.

− The trace item Cell User Number of the Cell Performance Monitoring function on the RNC LMT counts the DB-HSDPA/DB-HSDPA+MIMO users in the cell.

On the NodeB side

− A new trigger condition is added for ALM-26811 Configured Capacity Limit Exceeding Licensed Limit: This alarm is reported when the number of configured DB-HSDPA cells exceeds the number allowed by the license.

A new trigger condition is added for ALM-28206 Local Cell Capability Decline: This alarm is reported when a cell that does not support DB-HSDPA/DB-HSDPA+MIMO is enabled with DB-HSDPA/DB-HSDPA+MIMO.



WRFD-010610 HSDPA Introduction Package

WRFD-010685 Downlink Enhanced L2

WRFD-010629 DL 16QAM Modulation


None

Impacted Features

It is recommended that STTD be disabled in DB-HSDPA cells. STTD can be disabled by setting the TxDiversityInd parameter to FALSE. For details, see TX Diversity and RX Diversity Feature Parameter Description.

4.19 WRFD-150211 RNC in Pool Load Sharing (New/Optional)


This feature enables an RNC (known as the overflow RNC) to take over signaling related to RRC connections during UE access from another RNC (known as the master RNC). This occurs in a pool where the RNCs are connected over the Iur-p interface. The takeover is triggered when the average CPU load of the master RNC exceeds a specified threshold. This feature allows load sharing between existing RNCs and an added RNC, which facilitates smooth RNC capacity expansion.

../RNCParaHtml/mbsc/m-para/ucell_txdiversityind.html

TX%20Diversity%20and%20RX%20Diversity.htm

TX%20Diversity%20and%20RX%20Diversity.htm

RAN15.0




4-64

Figure 4-11 RNC in Pool load sharing


System Capacity

Control-plane load sharing increases the busy hour call attempts (BHCA) of a logical RNC. The increased number depends on the resources of the signaling processing board on the overflow RNC. For example, if a BSC6910 functions as the overflow RNC for three BSC6900s and the feature WRFD-150240 RNC in Pool Multiple Logical RNCs is enabled, the resources of the signaling processing board are shared by the three logical RNCs mapped on the BSC6910 and each BSC6900, respectively.

Network Performance

User signaling delay for UEs whose signaling is processed by the overflow RNC increases. This is because cross-Iur-p communication is required between the signaling processing module on the overflow RNC and the user-plane data processing module and transmission processing module on the master RNC.

The delay increase depends on the transmission delay over the Iur-p interface. If the one-way delay over the Iur-p interface is 10 ms (the maximum allowed value), the delay for a UE in idle mode to set up a CS call increases by 400 ms.

New counters have been introduced to measure the increase in signaling delay for UEs whose signaling is processed by the overflow RNC. Table 4-26 lists the new counters.

The CPU load affects the user signaling delay of CS call setups. When the CPU load on the master RNC is high and that on the overflow RNC is low, the user signaling delay of CS call setups for UEs on the master RNC is prolonged. After load sharing is performed, the user signaling delay of CS call setups for UEs whose signaling is taken over by the overflow RNC will decrease, compared with UEs whose signaling is processed by the master RNC.

The changes in user signaling delay affect KPIs as follows:

The increase in user signaling delay means a prolonged period of resource occupation. If radio resources are about to be insufficient before load sharing is performed, the user signaling delay increase will lead to more access denials due to insufficient codes, power, and channel elements (CEs), and also a decreased number of online users in congested cells.

RAN15.0




4-65

The decrease in user signaling delay means a shortened period of resource occupation. If radio resources are insufficient before load sharing is performed, the user signaling delay decrease will lead to fewer access denials due to insufficient codes, power, and CEs, and also an increased number of online users in congested cells.

To reduce the impact of the user signaling delay increase on the KPIs, you are advised to:

Ensure that the demands for the Iur-p interface are met. The one-way transmission delay must be no more than 10 ms, the transmission jitter must be no more than 5 ms, and the packet loss rate must be less than 0.01%.

Set the CpLoadShareRltCpuThd parameter to a larger value. A larger value helps decrease the user signaling delay.

4.19.3 NEs

This feature is implemented on the RNC, CME, and M2000.

All RNCs within a pool must be connected to the same M2000. The M2000 is used to manage the logical and physical RNCs involved in RNC in Pool.

Parameters for a logical RNC are configured on the LMT of its master RNC. The parameter settings are then synchronized to the overflow RNC through CME. Users can configure logical RNC parameters for multiple physical RNCs on the CME.

4.19.4 Hardware

To enhance Iur-p interface reliability, multiple Iur-p links must be configured. As a result, the number of RNC interface boards and ports will increase.

If the master RNC is configured with the SAU or GCG and uses them, the overflow RNC must also be configured with the SAU or GCG. Otherwise, functions provided by the boards cannot be used after the signaling is taken over by the overflow RNC.

The BSC6900 must be configured with IP interface board GOUc or FG2c to support Iur-p interface.

The BSC6910 must be configured with IP interface board GOUc, FG2c or EXOUa to support Iur-p interface.


An Iur-p interface connecting two physical RNCs, on which a logical RNC is mapped, has been introduced.


License

This feature affects the license as follows:

The license for a BSC6900 that functions as the master RNC covers both software license and hardware license. A BSC6900 is under the control of only one license.

A BSC6910 is under the control of only one license. When functioning as the master RNC, the license is a software license. When functioning as the overflow RNC, the license is a hardware license.

This feature affects the license control item as follows:

The following new license control item has been added.

RAN15.0




4-66

Feature ID Feature Name License Control Item

NE Sales Unit

WRFD-150211 RNC in Pool Load Sharing

RNC in Pool Load Sharing (per Active User)

RNC (BSC6900/BSC6910)

per 500 active users

When a network is shared by multiple operators, the preceding license control item is not operator-specific. This is because this feature applies to all operators configured on an RNC. The license usage of the primary operator indicates the license usage of all operators.


The following commands have been introduced on the RNC side to accommodate this feature.

Table 4-24 New RNC commands


New ADD/MOD/RMV/LST URNCMAP

These new commands are used to add, modify, remove, or query the mapping relationship between a logical RNC on a physical RNC and another physical RNC.

New SET/LST UPOOLLOADSHAREPARA

These new commands are used to set or query the parameters related to load sharing, including sharing type and threshold.

New SET/LST URNCPOOLCFGCTRL

These new commands are used to set or query the synchronization mode of logical RNC parameters between the master RNC and the overflow RNC.

New DSP URNCPOOLDATASYNC

This new command is used to query the synchronization status of logical RNC parameters between the master RNC and the overflow RNC.

New ADD/MOD/RMV/LST/DSP IURPLKS

These new commands are used to add, modify, remove, or query the Iur-p link set parameters.

New LST/DSP IURPLNK These new commands are used to query the parameters related to or status of the Iur-p links.

New SET/LST NODE These new commands are used to set or query a local physical RNC.

New ADD/ MOD/RMV/LST EXTNODE

These commands are used to add, modify, remove, or query an external physical RNC for a logical RNC.


RAN15.0




4-67



New LoadSharingType

ADD URNCBASIC This new parameter specifies the load sharing type for a physical RNC.

New NI

ADD/MOD UCNNODE

This new parameter specifies the network ID.

New OPCSPDF

ADD/MOD UCNNODE

This new parameter specifies the data format of the originating signaling point (OSP).

New DPCSPDF

ADD/MOD UCNNODE

This new parameter specifies the data format of the destination signaling point (DSP).

New SPC

ADD/MOD UCNNODE

This new parameter specifies the OSP code expressed in digits.

New SPCDNF

ADD/MOD UCNNODE

This new parameter specifies the OSP code expressed in segments.

New DPC

ADD/MOD UCNNODE

This new parameter specifies the DSP code expressed in digits.

New DPCDNF

ADD/MOD UCNNODE

This new parameter specifies the DSP code expressed in segments.

New SUPPORTRNCINPOOL

SET SYS This new parameter specifies whether RNC in Pool is supported.

New POOLNAME SET SYS This new parameter specifies the name of a pool.

New NI ADD/MOD UNRNC


New OPCSPDF ADD/MOD UNRNC

This new parameter specifies the data format of the OSP.

New DPCSPDF ADD/MOD UNRNC

This new parameter specifies the data format of the DSP.

New SPC ADD/MOD UNRNC


New SPCDNF ADD/MOD UNRNC


New DPC ADD/MOD UNRNC


New DPCDNF ADD/MOD UNRNC


New SCTPLNKID ADD/MOD UNCP

This new parameter specifies the SCTP link ID.

../RNCParaHtml/mbsc/m-para/urncbasic_loadsharingtype.html

../RNCParaHtml/mbsc/m-para/urncbasic_loadsharingtype.html

../RNCParaHtml/mbsc/m-para/ucnnode_ni.html

../RNCParaHtml/mbsc/m-para/ucnnode_opcspdf.html

../RNCParaHtml/mbsc/m-para/ucnnode_dpcspdf.html

../RNCParaHtml/mbsc/m-para/ucnnode_spc.html

../RNCParaHtml/mbsc/m-para/ucnnode_spcdnf.html

../RNCParaHtml/mbsc/m-para/ucnnode_dpc.html

../RNCParaHtml/mbsc/m-para/ucnnode_dpcdnf.html

../RNCParaHtml/mbsc/m-para/sys_supportrncinpool.html


../RNCParaHtml/mbsc/m-para/sys_poolname.html

../RNCParaHtml/mbsc/m-para/unrnc_ni.html

../RNCParaHtml/mbsc/m-para/unrnc_opcspdf.html

../RNCParaHtml/mbsc/m-para/unrnc_dpcspdf.html

../RNCParaHtml/mbsc/m-para/unrnc_spc.html

../RNCParaHtml/mbsc/m-para/unrnc_spcdnf.html

../RNCParaHtml/mbsc/m-para/unrnc_dpc.html

../RNCParaHtml/mbsc/m-para/unrnc_dpcdnf.html

../RNCParaHtml/mbsc/m-para/uncp_sctplnkid.html

RAN15.0




4-68


New SCTPLNKID ADD/MOD UCCP


New LogicRncId Commands for UMTS service configuration and maintenance management

This new parameter specifies the ID of a logical RNC. This parameter is used to set parameters for a logical RNC on the BSC6910.




Change Type


Description

New VS.LoadSharedActiveUEs.NodeShare

RRC.NODESHARE

Number of UEs Whose Load Is Shared Between Physical RNC Nodes

New VS.RRC.AttConnEstab.NodeShare

RRC.NODESHARE

Number of RRC Connection Requests Sent by UEs Whose Load Is Shared Between Physical RNC Nodes

New VS.RRC.SuccConnEstab.NodeShare

RRC.NODESHARE

Number of Successful RRC Connection Requests Sent by UEs Whose Load Is Shared Between Physical RNC Nodes

New VS.RRC.ConnEstabTimeMax.CellDCH.NodeShare

RRC.NODESHARE

Maximum Delay in Setting Up RRC Connection for UEs in CELL_DCH State Whose Load Is Shared Between Physical RNC Nodes

New VS.RRC.ConnEstabTimeMean.CellDCH.NodeShare

RRC.NODESHARE

Average Delay in Setting Up RRC Connection for UEs in CELL_DCH State Whose Load Is Shared Between Physical RNC Nodes

New VS.RRC.ConnEstabTimeMax.CellFACH.NodeShare

RRC.NODESHARE

Maximum Delay in Setting Up RRC Connection for UEs in CELL_FACH State Whose Load Is Shared Between Physical RNC Nodes

New VS.RRC.ConnEstabTimeMean.CellFACH.NodeShare

RRC.NODESHARE

Average Delay in Setting Up RRC Connection for UEs in CELL_FACH State Whose Load Is Shared Between Physical RNC Nodes

New VS.RAB.AttEstabCS

.Conv.NodeShare

RRC.NODESHARE

Number of CS RAB Assignment Requests for UEs Whose Load Is Shared Between Physical RNC Nodes (Conversational Service)

New VS.RAB.SuccEstab

CS.Conv.NodeShar

e

RRC.NODESHARE

Number of Successful CS RAB Assignment Requests for UEs Whose Load Is Shared Between Physical RNC Nodes (Conversational Service)

../RNCParaHtml/mbsc/m-para/uccp_sctplnkid.html

../RNCParaHtml/6910/mbsc/m-para/urncmap_logicrncid.html

RAN15.0




4-69

Change Type


Description

New VS.RAB.AttEstabPS

.Bkg.NodeShare

RRC.NODESHARE

Number of PS RAB Assignment Requests for UEs Whose Load Is Shared Between Physical RNC Nodes (Background Service)

New VS.RAB.AttEstabPS

.Int.NodeShare

RRC.NODESHARE

Number of PS RAB Assignment Requests for UEs Whose Load Is Shared Between Physical RNC Nodes (Interactive Service)


PS.Bkg.NodeShare

RRC.NODESHARE

Number of Successful PS RAB Assignment Requests for UEs Whose Load Is Shared Between Physical RNC Nodes (Background Service)


PS.Int.NodeShare

RRC.NODESHARE

Number of Successful PS RAB Assignment Requests for UEs Whose Load Is Shared Between Physical RNC Nodes (Interactive Service)

New VS.RAB.AbnormRel.CS.RF.NodeShare

RRC.NODESHARE

Number of CS RABs Released Abnormally due to Radio Link Failure for UEs Whose Load Is Shared Between Physical RNC Nodes

New VS.RAB.AbnormRel.PS.RF.NodeShare

RRC.NODESHARE

Number of PS RABs Released Abnormally due to Radio Link Failure for UEs Whose Load Is Shared Between Physical RNC Nodes

New VS.RAB.AbnormRel.CS.NodeShare

RRC.NODESHARE

Number of CS RABs Released Abnormally for UEs Whose Load Is Shared Between Physical RNC Nodes

New VS.RAB.AbnormRel.PS.NodeShare

RRC.NODESHARE

Number of PS RABs Released Abnormally for UEs Whose Load Is Shared Between Physical RNC Nodes

New VS.RAB.NormRel.CS.NodeShare

RAB.NODESHARE

Number of CS RABs Released Normally for UEs Whose Load Is Shared Between Physical RNC Nodes

New VS.RAB.NormRel.PS.NodeShare

RAB.NODESHARE

Number of PS RABs Released Normally for UEs Whose Load Is Shared Between Physical RNC Nodes

New VS.IURPLNK.TX.PKGNUM

IURPLNK Number of Packets Sent on the IURP Link

New VS.IURPLNK.RX.PKGNUM

IURPLNK Number of Packets Received on the IURP Link

New VS.IURPLNK.TX.MAXPKGNUM

IURPLNK Maximum Number of Packets Sent on the IURP Link

New VS.IURPLNK.RX.MAXPKGNUM

IURPLNK Maximum Number of Packets Received on the IURP Link

New VS.IURPLNK.TX.BYTES

IURPLNK Number of IP Bytes Sent on the IURP Link

RAN15.0




4-70

Change Type


Description

New VS.IURPLNK.RX.BYTES

IURPLNK Number of IP Bytes Received on the IURP Link

New VS.IURPLNK.TX.MAXBYTES

IURPLNK Maximum Number of IP Bytes Sent on the IURP Link

New VS.IURPLNK.RX.MAXBYTES

IURPLNK Maximum Number of IP Bytes Received on the IURP Link

New VS.IURPLNK.SERVICE.INTERVAL

IURPLNK Service Duration of the IURP Link

New VS.IURPLNK.CONGESTION

IURPLNK Number of Congestions on the IURP Link

New VS.IURPLNK.CONGESTION.INTERVAL

IURPLNK Congestion Duration of the IURP Link

New VS.IURPLNK.OVERLOAD

IURPLNK Number of Overloads on the IURP Link

New VS.IURPLNK.OVERLOAD.INTERVAL

IURPLNK Overload Duration of the IURP Link

New VS.IURPLNK.RETX.PKGNUM

IURPLNK Number of Packets Resent on the IURP Link

Counters related to logical RNC services are reported on the master RNC. Counters related to services taken over by the overflow RNC are transmitted over the Iur-p interface to and reported on the master RNC.

This feature does not affect counters on the NodeB side.

Fault Management

The following alarms have been introduced on the RNC side to accommodate this feature.

ALM-20759 POOL license information synchronization failure

ALM-22307 RNC in Pool Function Unavailable

ALM-21607 External Node Unreachable Alarm

ALM-21606 IURP Link Fault

ALM-21608 IURP Link Congestion Alarm

Message Tracing and Performance Monitoring

You can specify the ID of the logical RNC on the starting GUI of message tracing and performance monitoring. If you do not specify the RNC ID, the messages and performance of the logical RNC on the master RNC will be traced or monitored. The RNC ID does not need to be specified when only load sharing is used, because message tracing and performance monitoring cannot be performed on the overflow RNC.

RAN15.0




4-71

The master RNC is responsible for user tracing and monitoring of logical RNCs, as well as interface tracing for all interfaces including Iur-p. The overflow RNC can perform only the Iur-p interface tracing.



None


This feature is mutually exclusive to WRFD-010660 MBMS Phase 2.

If being shared between RNCs, Multimedia Broadcast Multicast Service (MBMS) data in point-to-point (P2P) mode will experience out-of-synchronization, which leads to broadcast service performance deterioration.

Impacted Features

When this feature is used together with WRFD-020134 Push to Talk, the push to talk (PTT) access delay of UEs whose signaling is shared between RNCs will increase. As a result, the key performance indicators (KPIs) of the Push to Talk feature cannot meet requirements.

The overflow RNC does not support the Iur-g interface. The following features do not apply to UEs whose signaling is taken over by the overflow RNC. UEs whose signaling is processed by the master RNC can use the following features:

WRFD-070004 Load Based GSM and UMTS Handover Enhancement Based on Iur-g

WRFD-070005 NACC Procedure Optimization Based on Iur-g

WRFD-070006 GSM and UMTS Load Balancing Based on Iur-g

WRFD-070007 GSM and UMTS Traffic Steering Based on Iur-g

Serving Radio Network System (SRNS) relocation and directed signaling connection re-establishment (DSCR) due to Iur transmission resource congestion cannot be performed on UEs whose signaling is taken over by the overflow RNC. This happens when the following features are used:

WRFD-02060501 SRNS Relocation (UE Not Involved)

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

If the feature WOFD-192300 Event-based Counter - WRAN is used on the M2000, the event-based counters (EBCs) cannot be applied or reported for the UEs whose signaling is taken over by the overflow RNC.

4.20 WRFD-150212 RNC in Pool Node Redundancy (New/Optional)


This feature prevents massive service disruption caused by RNC failure by making a physical RNC a backup (known as the backup RNC) for another physical RNC (known as the master RNC) in a pool. The master RNC and the backup RNC are connected over the Iur-p interface. A dual-homed NodeB is connected to both RNCs over two Iub interfaces, as shown in Figure 4-12. In normal situations, the master RNC provides services for the dual-homed NodeBs. If the master RNC is faulty or when otherwise necessary, the control rights of the dual-homed NodeBs (NodeB control for short) can be switched over to the backup RNC by running MML commands. After a NodeB control switchover, services of dual-homed NodeBs are resumed on the backup RNC.

RAN15.0




4-72

Figure 4-12 RNC in Pool node redundancy


System Capacity

If the feature WRFD-150240 RNC in Pool Multiple Logical RNCs is not used, the hardware capacity planning for the backup RNC is based on the hardware capacity of the master RNC. If the feature WRFD-150240 RNC in Pool Multiple Logical RNCs is used, the hardware capacity of the backup RNC must be planned. The following uses a pool where one BSC6910 functions as the backup RNC for three BSC6900s as an example.

When planning the hardware capacity for the BSC6910, users must first ensure that the BSC6910 is capable of processing the services from its own logical RNC. If users require the BSC6910 to take over services from all three BSC6900s when necessary, the hardware capacity equal to the capacity sum of the three BSC6900s must be added.

If users require the BSC6910 to take over services from any of the BSC6900s when necessary, the hardware capacity equal to the largest capacity of the three BSC6900s must be added. In this scenario, if more than one BSC6900 is faulty and services must be taken over by the BSC6910, service congestion may occur due to insufficient hardware resources. This will affect the quality of experience (QoE).

Network Performance

This feature allows NodeB control switchovers between physical RNCs. A switchover leads to service drops for UEs in connected mode, which affects the KPIs.

After a NodeB control switchover, the KPIs of the related logical RNC may be different from those before the switchover. This is because user-plane and transmission parameters may be inconsistent on the master RNC and the backup RNC, and the load of the two RNCs is different. Before each NodeB control switchover, run the LST UDPUCFGDATA command on the master RNC and the backup RNC to check whether the parameters are consistent. If not, run the SET UDPUCFGDATA command on the backup RNC with the related parameters set to the same values as those on the master RNC.

The service resumption time for all dual-homed NodeBs after the NodeB control switchover is no longer than 100 seconds.

RAN15.0




4-73

4.20.3 NEs

To use this feature, NodeBs must be configured with two Iub interfaces connecting to two physical RNCs. The CN must be configured with the control-plane and user-plane Iu interface to the backup RNC, and a neighboring RNC must be configured with the control-plane and user-plane Iur interface to the backup RNC.

After the control rights of dual-homed NodeBs are switched over from the master RNC to the backup RNC, the Iur-g, Iu-BC, and Iupc interfaces cannot be restored on the backup RNC. As a result, features related to the interfaces are not applicable until the control rights of dual-homed NodeBs are switched back from the backup RNC to the master RNC.

This feature is implemented on the RNC, CME, and M2000. The M2000 is used to manage the logical and physical RNCs involved in RNC in Pool.

Parameters for a logical RNC are configured on the LMT of its master RNC. The parameter settings are then synchronized to the backup RNC through CME. Users can configure logical RNC parameters for multiple physical RNCs on the CME.

4.20.4 Hardware

To enhance Iur-p interface reliability, multiple Iur-p links must be configured. As a result, the number of RNC interface boards and ports will increase.

If the master RNC is configured with the SAU, NIU, or GCG and uses them, the backup RNC must also be configured with the SAU, NIU, or GCG. Otherwise, functions provided by the boards cannot be used after the services are resumed on the backup RNC.

The BSC6900 must be configured with IP interface board GOUc or FG2c to support Iur-p interface.


Only the 3900 series base stations and 3803E support this feature.


An Iur-p interface connecting two physical RNCs, on which a logical RNC is mapped, has been introduced. This feature also affects the Iu interface. A private message NBAP_RNC_POOL_PRIVATE, heartbeat messages, and control rights negotiation messages have been introduced.

To enable the master RNC and backup RNC to negotiate with one another on the NodeB control if either of them is reset, they must use periodic heartbeat messages and inform the peer RNC of its status. The heartbeat messages are sent over the Iur-p interface between the RNCs. When the Iur-p interface is faulty, the heartbeat messages are sent over the Iub interface. The message transmission period is 5 seconds. The message is of small size and therefore hardly affects the control plane of the Iub interface.

The NodeB control switchover can be performed on either the master RNC or the master RNC by running MML commands. To instruct the peer RNC to participate in the NodeB control switchover, messages need to be sent over the Iub interface. The messages hardly affect the control plane of the Iub interface because they are sent only when the NodeB control switchover needs to be performed.


License


RAN15.0




4-74


A BSC6910 is under the control of only one license. When functioning as the master RNC, the license is a software license. When functioning as the backup RNC, the license is a hardware license.




WRFD-150212 RNC in Pool Node Redundancy

RNC in Pool Node Redundancy (per NodeB)

RNC (BSC6900/BSC6910)

per NodeB



The following commands have been introduced on the RNC side to accommodate this feature.



New ADD/MOD/RMV/LST URNCMAP

These new commands are used to add, modify, remove, or query the mapping relationship between a logical RNC on a physical RNC and another physical RNC.

New SET/LST URNCPOOLCFGCTRL

These new commands are used to set or query the synchronization mode of logical RNC parameters between the master RNC and the backup RNC.

New DSP URNCPOOLDATASYNC

This new command is used to query the synchronization status of logical RNC parameters between the master RNC and the backup RNC.

New FOC/REL/DSP UHOSTRNC

These new commands are used to preempt, release, or query the NodeB control on a local physical RNC.

New ADD/MOD/RMV/LST/DSP IURPLKS

These new commands are used to add, modify, remove, or query the Iur-p link set parameters.

New LST/DSP IURPLNK These new commands are used to query the parameters related to or status of the Iur-p links.

New SET/LST NODE These new commands are used to set or query a local physical RNC.

New ADD/ MOD/RMV/LST These commands are used to add, modify, remove, or

RAN15.0




4-75


EXTNODE query an external physical RNC for a logical RNC.




New RedundancyType ADD URNCBASIC This new parameter specifies the node redundancy type for a physical RNC.

New NI ADD/MOD UCNNODE


New OPCSPDF ADD/MOD UCNNODE

This new parameter specifies the data format of the OSP.

New DPCSPDF ADD/MOD UCNNODE

This new parameter specifies the data format of the DSP.

New SPC ADD/MOD UCNNODE


New SPCDNF

ADD/MOD UCNNODE


New DPC ADD/MOD UCNNODE


New DPCDNF

ADD/MOD UCNNODE


New SUPPORTRNCINPOOL

SET SYS This new parameter specifies whether RNC in Pool is supported.

New POOLNAME SET SYS This new parameter specifies the name of a pool.

New NI ADD/MOD UNRNC This new parameter specifies the network ID.

New OPCSPDF ADD/MOD UNRNC This new parameter specifies the data format of the OSP.

New DPCSPDF ADD/MOD UNRNC This new parameter specifies the data format of the DSP.

New SPC ADD/MOD UNRNC This new parameter specifies the OSP code expressed in digits.

New SPCDNF ADD/MOD UNRNC This new parameter specifies the OSP code expressed in

../RNCParaHtml/mbsc/m-para/urncbasic_redundancytype.html

../RNCParaHtml/mbsc/m-para/ucnnode_ni.html

../RNCParaHtml/mbsc/m-para/ucnnode_opcspdf.html

../RNCParaHtml/mbsc/m-para/ucnnode_dpcspdf.html

../RNCParaHtml/mbsc/m-para/ucnnode_spc.html

../RNCParaHtml/mbsc/m-para/ucnnode_spcdnf.html

../RNCParaHtml/mbsc/m-para/ucnnode_dpc.html

../RNCParaHtml/mbsc/m-para/ucnnode_dpcdnf.html



../RNCParaHtml/mbsc/m-para/sys_poolname.html

../RNCParaHtml/mbsc/m-para/unrnc_ni.html

../RNCParaHtml/mbsc/m-para/unrnc_opcspdf.html

../RNCParaHtml/mbsc/m-para/unrnc_dpcspdf.html

../RNCParaHtml/mbsc/m-para/unrnc_spc.html

../RNCParaHtml/mbsc/m-para/unrnc_spcdnf.html

RAN15.0




4-76


segments.

New DPC ADD/MOD UNRNC This new parameter specifies the DSP code expressed in digits.

New DPCDNF ADD/MOD UNRNC


New SCTPLNKID ADD/MOD UNCP


New SCTPLNKID ADD/MOD UCCP


New LogicRncId Commands for UMTS service configuration and maintenance management

This new parameter specifies the ID of a logical RNC. This parameter is used to set parameters for a logical RNC on the BSC6910.

If the BSC6910 uses the feature WRFD-150240 RNC in Pool Multiple Logical RNCs and the NodeB control is switched over to this RNC, the RNC ID must be specified when configuring logical RNC parameters.



Change Type


Description

New VS.IURPLNK.RX.PKGNUM

IURPLNK Number of Packets Received on the IURP Link

New VS.IURPLNK.TX.MAXPKGNUM

IURPLNK Maximum Number of Packets Sent on the IURP Link

New VS.IURPLNK.RX.MAXPKGNUM

IURPLNK Maximum Number of Packets Received on the IURP Link

New VS.IURPLNK.TX.BYTES

IURPLNK Number of IP Bytes Sent on the IURP Link

New VS.IURPLNK.RX.BYTES

IURPLNK Number of IP Bytes Received on the IURP Link

New VS.IURPLNK.TX.MAXBYTES

IURPLNK Maximum Number of IP Bytes Sent on the IURP Link

New VS.IURPLNK.RX.MAXBYTES

IURPLNK Maximum Number of IP Bytes Received on the IURP Link

New VS.IURPLNK.SER IURPLNK Service Duration of the IURP Link

../RNCParaHtml/mbsc/m-para/unrnc_dpc.html

../RNCParaHtml/mbsc/m-para/unrnc_dpcdnf.html

../RNCParaHtml/mbsc/m-para/uncp_sctplnkid.html

../RNCParaHtml/mbsc/m-para/uccp_sctplnkid.html

../RNCParaHtml/6910/mbsc/m-para/urncmap_logicrncid.html

RAN15.0




4-77

Change Type


Description

VICE.INTERVAL

New VS.IURPLNK.CONGESTION

IURPLNK Number of Congestions on the IURP Link

New VS.IURPLNK.CONGESTION.INTERVAL

IURPLNK Congestion Duration of the IURP Link

New VS.IURPLNK.OVERLOAD

IURPLNK Number of Overloads on the IURP Link

New VS.IURPLNK.OVERLOAD.INTERVAL

IURPLNK Overload Duration of the IURP Link

New VS.IURPLNK.RETX.PKGNUM

IURPLNK Number of Packets Resent on the IURP Link

If the BSC6910 uses the feature WRFD-150240 RNC in Pool Multiple Logical RNCs, the counters related to calls of each logical RNC on the BSC6910 are reported to the M2000 by their respective RNC ID. All counters related to device performance are reported by the BSC6910.

Fault Management

The following alarms have been introduced on the RNC side to accommodate this feature.

ALM-20759 POOL license information synchronization failure

ALM-22307 RNC in Pool Function Unavailable

ALM-21607 External Node Unreachable Alarm

ALM-22235 Dual-Homed NodeB Configuration Incorrect

ALM-21606 IURP Link Fault

ALM-21608 IURP Link Congestion Alarm

Message Tracing and Performance Monitoring

After the logical RNC services are resumed on the backup RNC, message tracing and performance monitoring are started on the backup RNC. When the feature WRFD-150240 RNC in Pool Multiple Logical RNCs is used, multiple logical RNCs may be carried by the backup RNC. In this case, you should specify the ID of the logical RNC on the GUI. Once an RNC ID is specified, the messages and performance of only the related RNC will be traced or monitored, respectively. If you do not specify the RNC ID, the messages and performance of the logical RNC on the master RNC will be traced or monitored.



None


None

RAN15.0




4-78

Impacted Features

After the control rights of dual-homed NodeBs are switched over from the master RNC to the backup RNC, the following features are not applicable because the Iur-g, Iu-BC, and Iupc interfaces cannot be restored on the backup RNC:

WRFD-070004 Load Based GSM and UMTS Handover Enhancement Based on Iur-g

WRFD-070005 NACC Procedure Optimization Based on Iur-g

WRFD-070006 GSM and UMTS Load Balancing Based on Iur-g

WRFD-070007 GSM and UMTS Traffic Steering Based on Iur-g

WRFD-020807 Iupc Interface for LCS service

WRFD-011000 Cell Broadcast Service

Features not supported by the BSC6910 are not applicable after services of a logical RNC are resumed on the backup RNC. If the feature WOFD-192300 Event-based Counter - WRAN is used on the M2000, the values of such counters are not trustworthy within a measurement period where the NodeB control is switched over.

4.21 WRFD-150240 RNC in Pool Multiple Logical RNCs (New/Optional)


This feature needs to be used together with the feature WRFD-150211 RNC in Pool Load Sharing or WRFD-150212 RNC in Pool Node Redundancy. With this feature, a BSC6910 can carry multiple logical RNCs and provide load sharing or node redundancy functions for one BSC6910 or multiple BSC6900s. Apart from the logical RNCs used in load sharing or node redundancy, the BSC6910 can also carry its own logical RNC.


If this feature is used together with the feature WRFD-150211 RNC in Pool Load Sharing, see section 4.19.2 "System Capacity and Network Performance."

If this feature is used together with the feature WRFD-150212 RNC in Pool Node Redundancy, see section 4.20.2 "System Capacity and Network Performance."

4.21.3 NEs

No impact.

4.21.4 Hardware

The BSC6900 does not support this feature.



No impact.

RAN15.0




4-79


License



A BSC6910 is under the control of only one license. When functioning as the master RNC, the license is a software license. When functioning as the overflow or backup RNC, the license is a hardware license.



Feature ID Feature Name

License Control Item

NE Sales Unit

WRFD-150240

RNC in Pool Multiple Logical RNCs

RNC in Pool Multiple Logic RNC (per RNC)

RNC (BSC6910) per logical RNC



If this feature is used together with WRFD-150211 RNC in Pool Load Sharing, see section 4.19.6 "Operation and Maintenance."

If this feature is used together with WRFD-150212 RNC in Pool Node Redundancy, see section 4.20.6 "Operation and Maintenance."




Fault Management





This feature requires WRFD-150211 RNC in Pool Load Sharing or WRFD-150212 RNC in Pool Node Redundancy.

RAN15.0




4-80


None

Impacted Features

None

4.22 WRFD-150213 MOCN Independent Iub Transmission Resource Allocation (New/Optional)


The MOCN Independent Iub Transmission Resource Allocation feature allocates user-plane Iub transmission resources to operators in MOCN scenarios, which prevents one operator from occupying excess user-plane Iub transmission resources and ensures that each operator retains independent user-plane Iub transmission resources.

To allocate user-plane bandwidths to each operator independently, the RNC is configured with multiple logical ports, where each logical port corresponds to one operator. After identifying the UE's serving operator, the RNC sends the UE's user-plane data to the corresponding logical port.


System Capacity

This feature has no impact on system capacity when the Iub transmission resources allocated to each operator are sufficient.

If the resources are not properly allocated among operators, system capacity decreases. For example, if a total of 10 Mbit/s bandwidth is equally allocated to operators A and B who require 6 Mbit/s and 4 Mbit/s, respectively, only 9 Mbit/s bandwidth is utilized, with a 10% decrease in system capacity.

Network Performance

Before you deploy this feature, allocate Iub transmission resources to operators based on their traffic requirements. For example, allocate the Iub transmission resources equally if all operators have almost the same traffic requirements.

This feature has no impact on network performance when the Iub transmission resources allocated to each operator are sufficient.

If the Iub transmission resources are not properly allocated among operators, network performance deteriorates. For example, if a total of 10 Mbit/s bandwidth is equally allocated to operators A and B who require 6 Mbit/s and 4 Mbit/s, respectively, resource utilization and access success rate decrease by 10%. The throughput of a single HSDPA user decreases as follows:

100% x (1 – Minimum bandwidth allocated to an operator/Min(Bandwidth obtained before service activation, Maximum bandwidth required by an UE))

4.22.3 NEs


4.22.4 Hardware

No impact.

RAN15.0




4-81


No impact.


License

A NodeB-level license control item has been introduced to accommodate this feature.


The following parameters have been introduced to accommodate this feature.

Table 4-29 New parameters on the RNC side


New CchCnOpIndex ADD UCELLSETUP

MOD UCELLSETUP

ADD UCELLQUICKSETUP

This new parameter specifies the operator that provides bandwidth for common channels of a shared cell.

The default value 255 indicates that the primary operator provides bandwidth.

If there is no primary operator, the first operator listed in the operator group provides bandwidth.

New NodeBId ADD UNODEBLICENSE

MOD UNODEBLICENSE

RMV UNODEBLICENSE

LST UNODEBLICENSE

This new parameter specifies the NodeB to which a feature applies.

New FuncSwitch1 ADD UNODEBLICENSE

MOD UNODEBLICENSE

This new parameter specifies the function switch for a NodeB-level license.


No impact.

Fault Management

No impact.

../RNCParaHtml/mbsc/m-para/ucell_cchcnopindex.html

../RNCParaHtml/mbsc/m-para/unodeblicense_nodebid.html

../RNCParaHtml/mbsc/m-para/unodeblicense_funcswitch1.html

RAN15.0




4-82



This feature requires the WRFD-021311 MOCN Introduction Package feature.


This feature cannot be used with the feature WRFD-140208 Iub Transmission Resource Pool in RNC.

Impacted Features

None.

4.23 WRFD-150214 MOCN Independent CE Resource Allocation (New/Optional)


The MOCN Independent CE Resource Allocation feature allocates a NodeB's uplink and downlink CE resources to operators in MOCN scenarios. With this feature, the M2000 allocates resources by configuring private and common groups, and UEs consume CE resources allocated to their serving operators. If the available CE resources for an operator are insufficient, the RNC relieves CE congestion for this operator by reducing the BE service rate or switching the TTI from 2 ms to 10 ms.


System Capacity

This feature has no impact on system capacity when the CE resources allocated to each operator are sufficient.

If the resources are not properly allocated among operators, system capacity decreases. For example, if a total of 100 CEs are equally allocated to operators A and B who require 60 and 40 CEs, respectively, only 90 CEs are utilized, with a 10% decrease in system capacity.

Network Performance

Before you deploy this feature, allocate CE resources to operators based on their traffic requirements. For example, allocate the CE resources equally if all operators have almost the same traffic requirements.

This feature has no impact on network performance when the CE resources allocated to each operator are sufficient.

If the CE resources are not properly allocated among operators, network performance deteriorates. For example, if a total of 100 CEs are equally allocated to operators A and B who require 60 and 40 CEs, respectively, network performance deteriorates, with a 10% decrease in resource utilization, cell HSUPA throughput, R99 PS throughput, and access success rate.

4.23.3 NEs


RAN15.0




4-83

4.23.4 Hardware

Only 3900 series base stations configured with the WBBPb, WBBPd, or WBBPf board support this feature.


No impact.


License

A NodeB-level license control item has been introduced to accommodate this feature.


No impact.


The following measurement unit has been added on the RNC side.

Measurement Unit Description

PLMN.NodeB Indicates NodeB-level performance counters collected by the RNC for each operator.

Fault Management

The ALM-26812 System Dynamic Traffic Exceeding Licensed Limit alarm has been added on the NodeB to accommodate this feature.



This feature requires the WRFD-021311 MOCN Introduction Package feature.


This feature cannot be used with the WRFD-021304 RAN Sharing Introduction Package feature.

Impacted Features

None.

4.24 WRFD-150215 SRVCC from LTE to UMTS with PS Handover (New/Optional)


The LTE network supports voice over IP (VoIP) services after the IP multimedia subsystem (IMS) is deployed. When a UMTS/LTE dual-mode UE processing a VoIP service on the LTE network moves to

RAN15.0




4-84

the UMTS coverage area, the single radio voice call continuity (SRVCC) feature works to hand over the VoIP service to the CS domain of the UMTS network. This feature ensures voice service continuity.


System Capacity

No impact.

Network Performance

Compared with the PS handover of the VoIP service, this feature enables the VoIP service in LTE to be carried in the CS domain, which improves the voice quality.

Compared with the CS only SRVCC handover of the PS service, this feature reduces the interruption duration of the PS service.

4.24.3 NEs


This feature requires support from the UE. The UE must support 3GPP Release 8 or later and also support SRVCC.

The CN must support LTE-to-UMTS PS handovers and SRVCC.

4.24.4 Hardware

No Impact.


No Impact.


License

An RNC-level license control item has been added to the RNC for this feature.


The following switch has been introduced on the RNC side, as described in Table 4-30. No switch has been introduced on the NodeB side.

Table 4-30 New RNC switch

Change Type

MO Switch Name

Parameter ID

MML Command

Description

New URRCTRLSWITCH

L2USRVCCwithPSHOSwitch

L2USRVCCwithPSHOSwitch (PROCESSSWITCH)

SET URRCTRLSWITCH

This new switch enables SRVCC from LTE to UMTS with PS Handover.

RAN15.0




4-85


The following counters have been introduced on the RNC side to accommodate this feature, as described in Table 4-31.


Change Type

Counter Name

Measurement Unit

Description

New VS.SRVCC.L2U.AttInCSPS

INTRAT.HO.Cell Number of Incoming L2U CS+PS Handover Attempts Triggered by SRVCC for VoIP Services for Cell

New VS.SRVCC.L2U.SuccInCSPS

INTRAT.HO.Cell Number of Successful Incoming L2U CS+PS Handovers Triggered by SRVCC for VoIP Services for Cell

New VS.SRVCC.L2U.AttRelocPrepInCSPS

INTRAT.HO.Cell Number of Preparation Attempts for Incoming L2U CS+PS Handovers Triggered by SRVCC for VoIP Services for Cell

New VS.SRVCC.L2U.SuccRelocPrepInCSPS

INTRAT.HO.Cell Number of Successful Preparations for Incoming L2U CS+PS Handovers Triggered by SRVCC for VoIP Services for Cell

Fault Management

No impact.


Impacted Features

UEs served by the LTE network can be handed over to the UMTS network through the SRVCC only when the LOFD-001022 SRVCC to UTRAN feature is enabled.

4.25 WRFD-150216 Load Based PS Redirection from UMTS to LTE (New/Optional)


This feature enables a UE served by a heavily loaded cell to be shifted from UMTS to LTE through a redirection, which reduces the load of the serving UMTS cell.

RAN15.0




4-86


System Capacity

No impact.

Network Performance

This feature allows UEs in congested UMTS cells to be redirected to LTE cells when UMTS cells are moderately congested. This method relieves the congestion in the current UMTS cell and decreases user access failures. As a result, the overall UMTS and LTE network performance is enhanced. For example, the RRC congestion rate declines.

4.25.3 NEs


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

4.25.4 Hardware

No impact.


No impact.


License



The following parameters have been introduced on the RNC side to accommodate this feature, as described in Table 4-32. No parameter has been introduced on the NodeB side.


Change Type

MO Parameter ID MML Command Description

New UCELLLDR

DlLdrEleventhAction

ADD UCELLLDR(Optional) MOD UCELLLDR(Optional)

This new parameter specifies a different action from that specified by DlLdrFirstAction.

New UCELLLDR

UlLdrNinthAction


This new parameter specifies a different action from that specified by UlLdrFirstAction.

RAN15.0




4-87

Change Type


New UCELLLDR

UlPSU2LHOUeNum


This new parameter specifies the number of UEs for performing uplink UMTS-to-LTE PS handovers. The parameter value can be set based on the ratio of high-speed UEs to PS UEs. If the ratio is high, this parameter can be set to a smaller value. Otherwise, the parameter value can be changed to a larger one. The load reshuffling (LDR) algorithm aims to slowly reduce cell loads. Therefore, this parameter is set to a small value.

New UCELLLDR

DlPSU2LHOUeNum


This new parameter specifies the number of UEs for performing downlink UMTS-to-LTE PS handovers.


The following counters have been introduced on the NodeB side to accommodate this feature, as described in Table 4-33. No counter has been introduced on the RNC side.

Table 4-33 New NodeB counters

Change Type


Description

New VS.U2LTEHO.RRCRelease.Load

U2LTE.HO.CELL

Number of Measurement-based U2L PS Redirections Triggered by LDR for Cell

RAN15.0




4-88

Change Type


Description

New VS.U2LTEHO.RRCRelease.Load.Blind

U2LTE.HO.CELL

Number of LDR-triggered U2L PS Blind Redirections for Cell

Fault Management

No impact.


Impacted Features

This feature affects the following RAN features:

WRFD-020106 Load Reshuffling

WRFD-150217 Load Based PS Handover from UMTS to LTE

4.26 WRFD-150217 Load Based PS Handover from UMTS to LTE (New/Optional)


This feature enables a UE served by a heavily loaded cell to be shifted from UMTS to LTE through a handover, which reduces the load of the serving UMTS cell.


System Capacity

No impact.

Network Performance

This feature allows UEs in congested UMTS cells to be handed over to LTE cells when UMTS cells are moderately congested. In this way, this method relieves the current UMTS cell and decreases user access failures. As a result, the overall UMTS and LTE network performance is enhanced. For example, the RRC congestion rate declines.

4.26.3 NEs


This feature requires support from the UE. The UE must support 3GPP Release 8 or later, UMTS-to-LTE PS handovers, and LTE network measurements in connected mode.

The eNodeB and MME must support UMTS-to-LTE PS handovers.

The SGSN must support UMTS-to-LTE PS handovers.

RAN15.0




4-89

4.26.4 Hardware

No impact.


No impact.


License





Change Type


New UCELLLDR DlLdrEleventhAction ADD UCELLLDR(Optional) MOD UCELLLDR(Optional)


New UCELLLDR UlLdrNinthAction ADD UCELLLDR(Optional) MOD UCELLLDR(Optional)


New UCELLLDR UlPSU2LHOUeNum ADD UCELLLDR(Optional) MOD UCELLLDR(Optional)

This new parameter specifies the number of UEs for performing uplink UMTS-to-LTE PS handovers.

RAN15.0




4-90

Change Type


New UCELLLDR DlPSU2LHOUeNum ADD UCELLLDR(Optional) MOD UCELLLDR(Optional)





Change Type


Description

New VS.U2LTEHO.AttOutPS.Load

U2LTE.HO.CELL Number of LDR-triggered U2L PS Handover Attempts for Cell

New VS.U2LTEHO.SuccOutPS.Load

U2LTE.HO.CELL Number of Successful LDR-triggered U2L PS Handovers for Cell

Fault Management

No impact.


Impacted Features




RAN15.0




4-91

4.27 WRFD-150219 Coverage Based PS Redirection from UMTS to LTE (New/Optional)


This feature enables the RNC to redirect a UMTS/LTE dual-mode UE processing only PS services to the LTE network when:

The UE is located in the hybrid network coverage of UMTS and LTE.

The UMTS signal quality received at the UE is poor.

The LTE signal quality received at the UE is good.

When the UMTS signal quality received at the UE is very poor, the RNC can redirect the UE to the LTE network through blind redirection.

This feature provides the following benefits:

This feature provides an alternative to the PS handover. When UEs, the UMTS network, or the LTE network does not support the UMTS-to-LTE PS handover, this feature enables PS redirection to the LTE network.

When the UMTS signal quality is poor but the LTE signal quality is good, this feature allows the UE to be redirected to the LTE network, which ensures the continuity of PS services.

When the UMTS signal quality is very poor, this feature allows blind redirection to the LTE network, reducing service drops.

During UE redirection to the LTE network, this feature allows the RNC to obtain the LTE frequency from the system information or from the neighboring LTE cell. If the RNC obtains the LTE frequency from the system information, operators can eliminate the workload for configuring the neighboring LTE cell.


System Capacity

No impact.

Network Performance

When the UMTS signal quality is poor but the LTE signal quality is good, this feature allows the UE to be redirected to the LTE network, which ensures the continuity of PS services.

Compared with PS handover, PS redirection shortens the duration of service interruptions.

When the blind redirection switch is turned on in an area with poor LTE network coverage, call drops may occur.

4.27.3 NEs


This feature requires support from the UE. The UE must support UMTS and LTE and support 3GPP Release 8 or later.

4.27.4 Hardware

No impact.

RAN15.0




4-92


No impact.


License



The following MML commands have been introduced on the RNC side to accommodate this feature, as described in Table 4-36. No MML command has been introduced on the NodeB side.

Table 4-36 RNC MML commands

Change Type

MO MML Command Description

New UU2LTEHOCOV

SET UU2LTEHOCOV

This new command is used to set the RNC-level UMTS-to-LTE handover or redirection measurement algorithm parameters.

Coverage-based handovers and redirections are triggered by any event except event 2D, event 2F and event 1F.

The event-triggered reporting mode and periodical reporting mode are both available to measurement reporting for the coverage-based handover to LTE.

New UU2LTEHOCOV

LST UU2LTEHOCOV

This new command is used to list the RNC-level UMTS-to-LTE handover or redirection measurement algorithm parameters.

RAN15.0




4-93

Change Type


New UU2LTEHOCOV

ADD UCELLU2LTEHOCOV

This new command is used to add cell-level measurement algorithm parameters for coverage-based UMTS-to-LTE handovers and redirections.



New UU2LTEHOCOV

MOD UCELLU2LTEHOCOV

This new command is used to modify cell-level measurement algorithm parameters for coverage-based UMTS-to-LTE handovers and redirections.



New UU2LTEHOCOV

RMV UCELLU2LTEHOCOV

This new command is used to remove cell-level measurement algorithm parameters for coverage-based UMTS-to-LTE handovers and redirections.

New UU2LTEHOCOV

LST UCELLU2LTEHOCOV

This new command is used to list cell-level measurement algorithm parameters for coverage-based UMTS-to-LTE handovers and redirections.


RAN15.0




4-94


Change Type


New UCORRMALGOSWITCH

HO_U2L_COV_PS_REDIRECT_SWITCH (HoSwitch1)


This new parameter specifies whether to enable a coverage-based UMTS-to-LTE PS redirection. When the switch is turned on, the RNC allows the coverage-based UMTS-to-LTE PS redirection procedure.

New UU2LTEHOCOV

LTEThd2DEcN0

SET UU2LTEHOCOV/ADD UCELLU2LTEHOCOV/MOD UCELLU2LTEHOCOV

This new parameter specifies the Ec/N0 threshold for a UE to start LTE cell measurements.

When the measured Ec/N0 is below the threshold, the UE reports event 2D. Then, the RNC sends a signaling message to enable the compressed mode and the UE starts LTE cell measurements. Event 2D and event 2F are triggered to enable and disable the compressed mode respectively. To enable the compressed mode earlier, increase the threshold of triggering event 2D; otherwise, decrease the threshold of triggering event 2D. To prevent frequent ping-pong handovers at intervals between enabling and disabling the compressed mode, increase the difference between the thresholds of triggering event 2D and event 2F. Thresholds of triggering event 2D and event 2F are unique for inter-frequency UMTS cells, GSM cells, and LTE cells.

When LTE cells and inter-frequency UMTS cells coexist, use the

RAN15.0




4-95

Change Type


thresholds of triggering event 2D and event 2F in UMTS.

When LTE cells and GSM cells coexist, use the thresholds of triggering event 2D and event 2F in GSM.

When inter-frequency UMTS cells, GSM cells, and LTE cells coexist, use the thresholds based on the value of CoexistMeasThdChoice in the ADD UCELLHOCOMM/SET UHOCOMM command.

When only LTE cells exist, use thresholds of triggering event 2D and event 2F in LTE.

New UU2LTEHOCOV

LTEThd2FEcN0


This new parameter specifies the Ec/N0 threshold for a UE to stop LTE cell measurements.

When the measured Ec/N0 is above the threshold, the UE reports event 2D. Then, the RNC sends a signaling message to enable the compressed mode and the UE stops LTE cell measurements. Event 2D and event 2F are triggered to enable and disable the compressed mode respectively. To enable the compressed mode earlier, increase the threshold of triggering event 2D; otherwise, decrease the threshold of triggering event 2D. To prevent frequent ping-pong handovers at intervals between enabling and disabling the compressed mode, increase the difference

RAN15.0




4-96

Change Type


between the thresholds of triggering event 2D and event 2F. Thresholds of triggering event 2D and event 2F are unique for inter-frequency UMTS cells, GSM cells, and LTE cells.

When LTE cells and inter-frequency UMTS cells coexist, use the thresholds of triggering event 2D and event 2F in UMTS.




New UU2LTEHOCOV

LTEThd2DRSCP


This new parameter specifies the RSCP threshold for a UE to start LTE cell measurements.

When the measured RSCP is below the threshold, the UE reports event 2D. Then, the RNC sends a signaling message to enable the compressed mode and the UE starts LTE cell measurements. Event 2D and event 2F are triggered to enable and disable the compressed mode respectively. To enable

RAN15.0




4-97

Change Type


the compressed mode earlier, increase the threshold of triggering event 2D; otherwise, decrease the threshold of triggering event 2D. To prevent frequent ping-pong handovers at intervals between enabling and disabling the compressed mode, increase the difference between the thresholds of triggering event 2D and event 2F. Thresholds of triggering event 2D and event 2F are unique for inter-frequency UMTS cells, GSM cells, and LTE cells.


New UU2LTEHOCOV

LTEThd2FRSCP


This new parameter specifies the RSCP threshold for a UE to stop LTE cell measurements.

When the measured RSCP is above the threshold, the UE reports event 2D. Then, the RNC sends a signaling message to enable the compressed mode and the UE stops LTE cell measurements. Event 2D and event 2F are triggered to enable and disable the compressed mode respectively. To enable the compressed mode earlier, increase the threshold of triggering event 2D; otherwise, decrease the threshold of triggering event 2D. To prevent frequent ping-

RAN15.0




4-98

Change Type


pong handovers at intervals between enabling and disabling the compressed mode, increase the difference between the thresholds of triggering event 2D and event 2F. Thresholds of triggering event 2D and event 2F are unique for inter-frequency UMTS cells, GSM cells, and LTE cells.





New UU2LTEHOCOV

LTEReportMode


This new parameter specifies the mode for a UE to report LTE cell measurement results.

When the parameter is set to PERIODICAL_REPORTING, report measurement results periodically. When this parameter is set to EVENT_TRIGGER, report measurement results by

RAN15.0




4-99

Change Type


triggering an event. For details about measurement reporting modes, see 3GPP TS 25.331.

In EVENT_TRIGGER mode, event 3A is used to decide whether to trigger a UMTS-to-LTE handover to prevent ping-pong effect of the UMTS-to-LTE handover. In this mode, the signaling transmission and processing load reduces, and the number of ping-pong handovers decreases based on the relative signal quality of the current frequency and the LTE frequency. However, measurement results are reported only once. No mechanism is provided for changing this mode to the PERIODICAL_REPORTING mode. If the handover fails, periodic retries can be triggered only by the internal timer.

In PERIODICAL_REPORTING mode, a UMTS-to-LTE handover or redirection starts when the reported LTE cell quality meets the requirements for triggering a UMTS-to-LTE handover or redirection. If the handover fails, handover or redirection retries are performed based on the periodical LTE measurement report. In this mode, handover retries can be performed in a cell based on the periodical measurement report after the handover fails. Therefore, the subsequent algorithm can

RAN15.0




4-100

Change Type


be expanded flexibly. However, the Uu load and signaling processing load increase. The reporting mode is selected as required. Currently, the traditional PERIODICAL_REPORTING mode is used.

New UU2LTEHOCOV

UsedFreqThdRSCP


This new parameter specifies the RSCP threshold of the used frequency. One necessary condition for triggering event 3A is that the quality of the used frequency is lower than the threshold. The other necessary condition is that the quality of the target cell is higher than the corresponding decision threshold (TargetRatThdRSRP). Event 3A is triggered only when the two conditions are met.

New UU2LTEHOCOV

UsedFreqThdEcNo


This new parameter specifies the Ec/N0 threshold of the used frequency. One necessary condition for triggering event 3A is that the quality of the used frequency is lower than the threshold. The other necessary condition is that the quality of the target cell is higher than the corresponding decision threshold (TargetRatThdRSRP). Event 3A is triggered only when the two conditions are met.

New UU2LTEHOCOV

LTEMeasQuanOf3A

SET UU2LTEHOCOV/ADD UCELLU2LTEHOCOV/MOD UCELLU2LTEH

This new parameter specifies the measurement quantity of the target LTE network reported in Event 3A for a coverage-based

RAN15.0




4-101

Change Type


OCOV handover.

RSRP indicates the average signal power received at all REs carrying reference signals in a symbol.

RSRQ is equal to RSRP divided by RSSI. A factor (N) is used to adjust the ratio if the bandwidths used for measuring RSRP and RSSI are different. That is, RSRQ = N x RSRP/RSSI.

New UU2LTEHOCOV

Hystfor3A SET UU2LTEHOCOV/ADD UCELLU2LTEHOCOV/MOD UCELLU2LTEHOCOV

This new parameter specifies the hysteresis for reporting event 3A. For details, see 3GPP TS 25.331.

New UU3LTEHOCOV

TrigTime3A SET UU2LTEHOCOV/ADD UCELLU2LTEHOCOV/MOD UCELLU2LTEHOCOV


New UU2LTEHOCOV

U2LTEFilterCoef


This new parameter specifies the layer 3 filtering coefficient for LTE cell measurements.

The RNC delivers the layer 3 filtering coefficient to a UE to smooth measurement results based on the following formula:

Fn = (1-a) x Fn-1 + a x Mn

where

a = 1/(2^(k/2))

k refers to the layer 3 filtering coefficient.

Fn-1 refers to the measurement result after the filtering of the preceding time.

RAN15.0




4-102

Change Type


Mn refers to the latest measurement result.

Fn refers to the measurement result after filtering for this time.

For details, see 3GPP TS 25.331.

New UU2LTEHOCOV

U2LTEMeasTime


This new parameter specifies the length of a timer for LTE cell measurements.

The RNC starts the timer to perform LTE cell measurements. If a handover to the LTE network is not triggered after the timer expires, the RNC stops LTE cell measurements and compressed mode. If this parameter is set to 0, the RNC does not start the timer for LTE cell measurements.

New UU2LTEHOCOV

TargetRatThdRSRP


This new parameter specifies the reference signal received power (RSRP) threshold for LTE cell measurements of event 3A.

When coverage-based UMTS-to-LTE handover measurements are reported by events and RSRP is used for the measurement of event 3A, the RNC triggers event 3A in the following conditions:

The cell quality of the target system is greater than the threshold.

The quality of the used frequency is lower than the decision threshold. When coverage-based UMTS-to-LTE handover measurements are reported periodically, this

RAN15.0




4-103

Change Type


parameter is set to estimate inter-RAT coverage handovers on the RNC side.


New UU2LTEHOCOV

TargetRatThdRSRQ


This new parameter specifies the threshold for reference signal received quality (RSRQ) for LTE cell measurements of event 3A.

When coverage-based UMTS-to-LTE handover measurements are reported by events and RSRQ is used for the measurement of event 3A, the RNC triggers event 3A in the following conditions:


The current frequency quality is lower than the decision threshold. When coverage-based UMTS-to-LTE handover measurements are reported periodically, this parameter is set to estimate inter-RAT coverage handovers on the RNC side.


New UU2LTEHOCOV

LTEPeriodReportInterval


This new parameter specifies the interval at which a UE periodically reports LTE cell measurements to the RNC. In this case, the UE periodically reports the LTE cell measurement result to the RNC at the interval.

If LTEReportMode is set to

RAN15.0




4-104

Change Type


NON_PERIODIC_REPORT, the UE cannot periodically report LTE cell measurements.

New UU2LTEHOCOV

HystforPeriodLTE


This new parameter specifies the hysteresis for periodically reporting LTE signal quality. When LTE cell measurements are periodically reported and the target frequency quality meets the following requirement, the UE performs handovers or redirections:

Mother_RAT is greater than or equal to Tother_RAT plus HystforPeriodLTE/2

where

Mother_RAT refers to the LTE cell measurement result.

Tother_RAT refers to the threshold for RSRP or RSRQ decision of the LTE system for PS services. Setting this parameter reduces the error decision rate caused by signal jitter.

According to simulation results, the shadow fading variance of high-speed cells covering highways is small due to flat ground and few barriers. Therefore, decrease the parameter value to 1.5 dB.

The shadow fading variance of low-speed cells covering many high buildings is large. Therefore, increase the parameter value to 3.0 dB.

New None LstFormat LST UU2LTEHOCOV/LST

This new parameter specifies the result is listed horizontally or

RAN15.0




4-105

Change Type


UCELLU2LTEHOCOV

vertically.

Format in which the result is listed.

- HORIZONTAL: to list the result horizontally

- VERTICAL: to list the result vertically.

New UU2LTEHOCOV

CellId ADD UCELLU2LTEHOCOV/LST UCELLU2LTEHOCOV/MOD UCELLU2LTEHOCOV/RMV UCELLU2LTEHOCOV

This new parameter specifies the unique ID of a cell.

New UTGPSCP

DeltaCFN3 SET UTGPSCP This new parameter specifies the difference between the transmission gap connection frame numbers (TGCFN) of compressed mode style sequences. If CmMeasType is set to CMCF_MEAS_TYPE_FDD_LTE_GSM, this parameter specifies the difference between the TGCFN when [Compressed mode purpose] is GSM_INITIAL_BSIC_IDENTIFICATION and that when [Compressed mode purpose] is GSM_CARRIER_RSSI_MEASUREMENT.

Modified UTGPSCP

DeltaCFN1 SET UTGPSCP/LST UTGPSCP

When CmMeasType is set to CMCF_MEAS_TYPE_FDD_LTE or CMCF_MEAS_TYPE_FDD_LTE_GSM, this parameter specifies the difference between the TGCFN when [Compressed mode purpose] is E_UTRA_MEASUREMEN

RAN15.0




4-106

Change Type


T and that when [Compressed mode purpose] is FDD_MEASUREMENT.

When CmMeasType is set to CMCF_MEAS_TYPE_LTE_GSM, this parameter specifies the difference between the TGCFN when [Compressed mode purpose] is GSM_CARRIER_RSSI_MEASUREMENT and that when [Compressed mode purpose] is E_UTRA_MEASUREMENT.

Modified UTGPSCP


When CmMeasType is set to CMCF_MEAS_TYPE_LTE_GSM, this parameter specifies the difference between the TGCFN when [Compressed mode purpose] is GSM Initial BSIC identification and that when [Compressed mode purpose] is GSM carrier RSSI measurement.

When CmMeasType is set to CMCF_MEAS_TYPE_FDD_LTE_GSM, this parameter specifies the difference between the TGCFN when [Compressed mode purpose] is GSM carrier RSSI measurement and that when [Compressed mode purpose] is E_UTRA_MEASUREMENT.

Modified UTGPSCP

CMMeasType SET UTGPSCP/LST UTGPSCP

If this parameter is set to CMCF_MEAS_TYPE_FDD_GSM, the compressed mode sequence is used for inter-frequency and

RAN15.0




4-107

Change Type


GERAN measurements.

If this parameter is set to CMCF_MEAS_TYPE_LTE_GSM, the compressed mode sequence is used for GERAN and E-UTRAN measurements.

If this parameter is set to CMCF_MEAS_TYPE_FDD_LTE, the compressed mode sequence is used for inter-frequency and E-UTRAN measurements.

If this parameter is set to CMCF_MEAS_TYPE_FDD_LTE_GSM, the compressed mode sequence is used for inter-frequency, GERAN, and E-UTRAN measurements.


The following counters have been introduced on the RNC side to accommodate this feature, as described in Table 4-38. No counter has been introduced on the NodeB side.


Change Type


Description

New VS.U2LTEHO.RRCRelease.Coverage

U2LTE.HO.Cell Number of Measurement-based U2L PS Redirection Attempts Triggered by Poor Coverage for Cell

New VS.U2LTEHO.RRCRelease.Coverage.EmergBlind

U2LTE.HO.Cell Number of Emergency Blind U2L PS Redirection Attempts Triggered by Event 1F for Cell

Fault Management

No impact.

RAN15.0




4-108


No impact.

4.28 WRFD-150220 Coverage Based PS Handover from UMTS to LTE (New/Optional)


This feature enables the RNC to hand over a UMTS/LTE dual-mode UE processing only PS services to the LTE network when:

The UE is located in the hybrid network coverage of UMTS and LTE.

The UMTS signal quality received at the UE is poor.

The LTE signal quality received at the UE is good.

When the UMTS signal quality is poor and the LTE signal quality is good, this feature allows the UE to be handed over to the LTE network to ensure the continuity of PS services and avoid service drops. Compared with PS redirection, PS handover shortens the service interruption duration, improving user experience.


System Capacity

No impact.

Network Performance

When the UMTS signal quality is poor but the LTE signal quality is good, this feature allows the UE to be handed over to the LTE network, which ensures the continuity of PS services.

Compared with PS redirection, the PS handover shortens the duration of service interruptions but has more requirements for the CN.

4.28.3 NEs


This feature requires support from the UE, SGSN, eNodeB, and MME.

The UE must support:

Both UMTS and LTE

3GPP Release 8 or later

UMTS-to-LTE PS handovers

Measurements on the neighboring LTE cell in connected mode



4.28.4 Hardware

No impact.

RAN15.0




4-109


No impact.


License



The following MML commands have been introduced on the RNC side to accommodate this feature, as described in Table 4-39. No MML command has been introduced on the NodeB side.


Change Type


New UU2LTEHOCOV

SET UU2LTEHOCOV

This new command is used to set the RNC-level UMTS-to-LTE handover or redirection measurement algorithm parameters.



New UU2LTEHOCOV

LST UU2LTEHOCOV

This new command is used to list the RNC-level UMTS-to-LTE handover or redirection measurement algorithm parameters.

New UU2LTEHOCOV

ADD UCELLU2LTEHOCOV

This new command is used to add cell-level measurement algorithm parameters for coverage-based UMTS-to-LTE handovers and redirections.



RAN15.0




4-110

Change Type


New UU2LTEHOCOV

MOD UCELLU2LTEHOCOV

This new command is used to modify cell-level measurement algorithm parameters for coverage-based UMTS-to-LTE handovers and redirections.



New UU2LTEHOCOV

RMV UCELLU2LTEHOCOV

This new command is used to remove cell-level measurement algorithm parameters for coverage-based UMTS-to-LTE handovers and redirections.

New UU2LTEHOCOV

LST UCELLU2LTEHOCOV

This new command is used to list cell-level measurement algorithm parameters for coverage-based UMTS-to-LTE handovers and redirections.



Change Type

MO Parameter ID



HO_U2L_COV_PS_HO_SWITCH (HoSwitch1)


This new parameter specifies whether to enable a coverage-based UMTS-to-LTE PS handover. When the switch is turned on, the RNC allows the coverage-based UMTS-to-LTE PS handover procedure.

New UU2LTEHOCOV

LTEThd2DEcN0


This new parameter specifies the Ec/N0 threshold for a UE to start LTE cell measurements.

When the measured Ec/N0 is below the threshold, the UE reports event 2D. Then, the RNC sends a signaling

RAN15.0




4-111

Change Type

MO Parameter ID


message to enable the compressed mode and the UE starts LTE cell measurements. Event 2D and event 2F are triggered to enable and disable the compressed mode respectively. To enable the compressed mode earlier, increase the threshold of triggering event 2D; otherwise, decrease the threshold of triggering event 2D. To prevent frequent ping-pong handovers at intervals between enabling and disabling the compressed mode, increase the difference between the thresholds of triggering event 2D and event 2F. Thresholds of triggering event 2D and event 2F are unique for inter-frequency UMTS cells, GSM cells, and LTE cells.





New UU2L LTEThd2F SET This new parameter

RAN15.0




4-112

Change Type

MO Parameter ID


TEHOCOV

EcN0 UU2LTEHOCOV/ADD UCELLU2LTEHOCOV/MOD UCELLU2LTEHOCOV

specifies the Ec/N0 threshold for a UE to start LTE cell measurements.

When the measured Ec/N0 is below the threshold, the UE reports event 2D. Then, the RNC sends a signaling message to enable the compressed mode and the UE starts LTE cell measurements. Event 2D and event 2F are triggered to enable and disable the compressed mode respectively. To enable the compressed mode earlier, increase the threshold of triggering event 2D; otherwise, decrease the threshold of triggering event 2D. To prevent frequent ping-pong handovers at intervals between enabling and disabling the compressed mode, increase the difference between the thresholds of triggering event 2D and event 2F. Thresholds of triggering event 2D and event 2F are unique for inter-frequency UMTS cells, GSM cells, and LTE cells.



When inter-frequency UMTS cells, GSM cells, and LTE cells coexist, use the thresholds based on the value of CoexistMeasThdChoice in the ADD UCELLHOCOMM/SET

RAN15.0




4-113

Change Type

MO Parameter ID


UHOCOMM command.


New UU2LTEHOCOV

LTEThd2DRSCP


This new parameter specifies the RSCP threshold for a UE to start LTE cell measurements.

When the measured RSCP is below the threshold, the UE reports event 2D. Then, the RNC sends a signaling message to enable the compressed mode and the UE starts LTE cell measurements. Event 2D and event 2F are triggered to enable and disable the compressed mode respectively. To enable the compressed mode earlier, increase the threshold of triggering event 2D; otherwise, decrease the threshold of triggering event 2D. To prevent frequent ping-pong handovers at intervals between enabling and disabling the compressed mode, increase the difference between the thresholds of triggering event 2D and event 2F. Thresholds of triggering event 2D and event 2F are unique for inter-frequency UMTS cells, GSM cells, and LTE cells.



When inter-frequency UMTS

RAN15.0




4-114

Change Type

MO Parameter ID


cells, GSM cells, and LTE cells coexist, use the thresholds based on the value of CoexistMeasThdChoice in the ADD UCELLHOCOMM/SET UHOCOMM command.


New UU2LTEHOCOV

LTEThd2FRSCP


This new parameter specifies the RSCP threshold for a UE to stop LTE cell measurements.

When the measured RSCP is above the threshold, the UE reports event 2D. Then, the RNC sends a signaling message to enable the compressed mode and the UE stops LTE cell measurements. Event 2D and event 2F are triggered to enable and disable the compressed mode respectively. To enable the compressed mode earlier, increase the threshold of triggering event 2D; otherwise, decrease the threshold of triggering event 2D. To prevent frequent ping-pong handovers at intervals between enabling and disabling the compressed mode, increase the difference between the thresholds of triggering event 2D and event 2F. Thresholds of triggering event 2D and event 2F are unique for inter-frequency UMTS cells, GSM cells, and LTE cells.

When LTE cells and inter-frequency UMTS cells coexist, use the thresholds of triggering event 2D and

RAN15.0




4-115

Change Type

MO Parameter ID


event 2F in UMTS.




New UU2LTEHOCOV

LTEReportMode


This new parameter specifies the mode for a UE to report LTE cell measurement results.

When the parameter is set to PERIODICAL_REPORTING, report measurement results periodically. When this parameter is set to EVENT_TRIGGER, report measurement results by triggering an event. For details about measurement reporting modes, see 3GPP TS 25.331.

In EVENT_TRIGGER mode, event 3A is used to decide whether to trigger a UMTS-to-LTE handover to prevent ping-pong effect of the UMTS-to-LTE handover. In this mode, the signaling transmission and processing load reduces, and the number of ping-pong handovers decreases based on the relative signal quality of the current frequency and the LTE frequency. However, measurement

RAN15.0




4-116

Change Type

MO Parameter ID


results are reported only once. No mechanism is provided for changing this mode to the PERIODICAL_REPORTING mode. If the handover fails, periodic retries can be triggered only by the internal timer.

In PERIODICAL_REPORTING mode, a UMTS-to-LTE handover or redirection starts when the reported LTE cell quality meets the requirements for triggering a UMTS-to-LTE handover or redirection. If the handover fails, handover or redirection retries are performed based on the periodical LTE measurement report. In this mode, handover retries can be performed in a cell based on the periodical measurement report after the handover fails. Therefore, the subsequent algorithm can be expanded flexibly. However, the Uu load and signaling processing load increase. The reporting mode is selected as required. Currently, the traditional PERIODICAL_REPORTING mode is used.

New UU2LTEHOCOV

UsedFreqThdRSCP


This new parameter specifies the RSCP threshold of the used frequency. One necessary condition for triggering event 3A is that the quality of the used frequency is lower than the threshold. The other necessary condition is that the quality of the target cell is higher than the corresponding decision threshold (TargetRatThdRSRP).

RAN15.0




4-117

Change Type

MO Parameter ID


Event 3A is triggered only when the two conditions are met.

New UU2LTEHOCOV

UsedFreqThdEcNo


This new parameter specifies the Ec/N0 threshold of the used frequency. One necessary condition for triggering event 3A is that the quality of the used frequency is lower than the threshold. The other necessary condition is that the quality of the target cell is higher than the corresponding decision threshold (TargetRatThdRSRP). Event 3A is triggered only when the two conditions are met.

New UU2LTEHOCOV

LTEMeasQuanOf3A


This new parameter specifies the measurement quantity of the target LTE network reported in Event 3A for a coverage-based handover.

RSRP indicates the average signal power received at all REs carrying reference signals in a symbol.

RSRQ is equal to RSRP divided by RSSI. A factor (N) is used to adjust the ratio if the bandwidths used for measuring RSRP and RSSI are different. That is, RSRQ = N x RSRP/RSSI.

New UU2LTEHOCOV

Hystfor3A SET UU2LTEHOCOV/ADD UCELLU2LTEHOCOV/MOD UCELLU2LTEHOCOV


New UU3LTEHOCOV

TrigTime3A

SET UU2LTEHOCOV/ADD UCELLU2LTEHOCOV/MOD

This new parameter specifies the time-to-trigger for reporting event 3A. The value of this parameter is related to slow fading. For

RAN15.0




4-118

Change Type

MO Parameter ID


UCELLU2LTEHOCOV

details, see 3GPP TS 25.331.

New UU2LTEHOCOV

U2LTEFilterCoef


This new parameter specifies the layer 3 filtering coefficient for LTE cell measurements.

The RNC delivers the layer 3 filtering coefficient to a UE to smooth measurement results based on the following formula:

Fn = (1-a) x Fn-1 + a x Mn

where

a = 1/(2^(k/2))

k refers to the layer 3 filtering coefficient.

Fn-1 refers to the measurement result after the filtering of the preceding time.

Mn refers to the latest measurement result.

Fn refers to the measurement result after filtering for this time.


New UU2LTEHOCOV

U2LTEMeasTime


This new parameter specifies the length of a timer for LTE cell measurements.

The RNC starts the timer to perform LTE cell measurements. If a handover to the LTE network is not triggered after the timer expires, the RNC stops LTE cell measurements and compressed mode. If this parameter is set to 0, the RNC does not start the timer for LTE cell measurements.

New UU2LTEHOCOV

TargetRatThdRSRP

SET UU2LTEHOCOV/ADD UCELLU2LTEH

This new parameter specifies the reference signal received power (RSRP) threshold for LTE

RAN15.0




4-119

Change Type

MO Parameter ID


OCOV/MOD UCELLU2LTEHOCOV

cell measurements of event 3A.

When coverage-based UMTS-to-LTE handover measurements are reported by events and RSRP is used for the measurement of event 3A, the RNC triggers event 3A in the following conditions:


The quality of the used frequency is lower than the decision threshold. When coverage-based UMTS-to-LTE handover measurements are reported periodically, this parameter is set to estimate inter-RAT coverage handovers on the RNC side.


New UU2LTEHOCOV

TargetRatThdRSRQ


This new parameter specifies the threshold for reference signal received quality (RSRQ) for LTE cell measurements of event 3A.

When coverage-based UMTS-to-LTE handover measurements are reported by events and RSRQ is used for the measurement of event 3A, the RNC triggers event 3A in the following conditions:


The current frequency quality is lower than the decision threshold. When coverage-based UMTS-to-LTE handover measurements are reported periodically, this parameter is set to estimate inter-RAT

RAN15.0




4-120

Change Type

MO Parameter ID


coverage handovers on the RNC side.


New UU2LTEHOCOV

LTEPeriodReportInterval


This new parameter specifies the interval at which a UE periodically reports LTE cell measurements to the RNC. In this case, the UE periodically reports the LTE cell measurement result to the RNC at the interval.

If LTEReportMode is set to NON_PERIODIC_REPORT, the UE cannot periodically report LTE cell measurements.

New UU2LTEHOCOV

HystforPeriodLTE


This new parameter specifies the hysteresis for periodically reporting LTE signal quality. When LTE cell measurements are periodically reported and the target frequency quality meets the following requirement, the UE performs handovers or redirections:

Mother_RAT is greater than or equal to Tother_RAT plus HystforPeriodLTE/2

where

Mother_RAT refers to the LTE cell measurement result.

Tother_RAT refers to the threshold for RSRP or RSRQ decision of the LTE system for PS services. Setting this parameter reduces the error decision rate caused by signal jitter.

New None LstFormat LST UU2LTEHOCOV/LST UCELLU2LTEHOCOV

This new parameter specifies the result is listed horizontally or vertically.

Format in which the result is

RAN15.0




4-121

Change Type

MO Parameter ID


listed.

- HORIZONTAL: to list the result horizontally

- VERTICAL: to list the result vertically.

New UU2LTEHOCOV

CellId ADD UCELLU2LTEHOCOV/LST UCELLU2LTEHOCOV/MOD UCELLU2LTEHOCOV/RMV UCELLU2LTEHOCOV

This new parameter specifies the unique ID of a cell.

New UTGPSCP

DeltaCFN3 SET UTGPSCP This new parameter specifies the difference between the transmission gap connection frame numbers (TGCFN) of compressed mode style sequences. If CmMeasType is set to CMCF_MEAS_TYPE_FDD_LTE_GSM, this parameter specifies the difference between the TGCFN when [Compressed mode purpose] is GSM_INITIAL_BSIC_IDENTIFICATION and that when [Compressed mode purpose] is GSM_CARRIER_RSSI_MEASUREMENT.

Modified UTGPSCP


When CmMeasType is set to CMCF_MEAS_TYPE_FDD_LTE or CMCF_MEAS_TYPE_FDD_LTE_GSM, this parameter specifies the difference between the TGCFN when [Compressed mode purpose] is E_UTRA_MEASUREMENT and that when [Compressed mode purpose] is FDD_MEASUREMENT.

When CmMeasType is set

RAN15.0




4-122

Change Type

MO Parameter ID


to CMCF_MEAS_TYPE_LTE_GSM, this parameter specifies the difference between the TGCFN when [Compressed mode purpose] is GSM_CARRIER_RSSI_MEASUREMENT and that when [Compressed mode purpose] is E_UTRA_MEASUREMENT.

Modified UTGPSCP


When CmMeasType is set to CMCF_MEAS_TYPE_LTE_GSM, this parameter specifies the difference between the TGCFN when [Compressed mode purpose] is GSM Initial BSIC identification and that when [Compressed mode purpose] is GSM carrier RSSI measurement.

When CmMeasType is set to CMCF_MEAS_TYPE_FDD_LTE_GSM, this parameter specifies the difference between the TGCFN when [Compressed mode purpose] is GSM carrier RSSI measurement and that when [Compressed mode purpose] is E_UTRA_MEASUREMENT.

Modified UTGPSCP

CMMeasType

SET UTGPSCP/LST UTGPSCP

If this parameter is set to CMCF_MEAS_TYPE_FDD_GSM, the compressed mode sequence is used for inter-frequency and GERAN measurements.

If this parameter is set to CMCF_MEAS_TYPE_LTE_GSM, the compressed mode sequence is used for GERAN and E-UTRAN measurements.

If this parameter is set to

RAN15.0




4-123

Change Type

MO Parameter ID


CMCF_MEAS_TYPE_FDD_LTE, the compressed mode sequence is used for inter-frequency and E-UTRAN measurements.

If this parameter is set to CMCF_MEAS_TYPE_FDD_LTE_GSM, the compressed mode sequence is used for inter-frequency, GERAN, and E-UTRAN measurements.


The following counters have been introduced on the RNC side to accommodate this feature, as described in Table 4-41. No counter has been introduced on the NodeB side.


Change Type


Description

New VS.U2LHO.AttOutPS.Coverage

U2LTE.HO.Cell Number of Measurement-based U2L PS Handover Attempts Triggered by Poor Coverage for Cell

New VS.U2LHO.SuccOutPS.Coverage

U2LTE.HO.Cell Number of Successful Measurement-based U2L PS Handovers Triggered by Poor Coverage in a Cell

New VS.U2LHO.AttRelocPrepOutPS.Coverage

U2LTE.HO.Cell Number of Preparation Attempts for Outgoing Coverage-triggered U2L PS Handovers for Cell

New VS.U2LHO.SuccRelocPrepOutPS.Coverage

U2LTE.HO.Cell Number of Successful Preparations for Outgoing Coverage-triggered U2L PS Handovers for Cell

Fault Management

No impact.

RAN15.0




4-124


No impact.

4.29 WRFD-150222 HSUPA Time Division Scheduling (New/Optional)


The WRFD-150222 HSUPA Time Division Scheduling feature applies to scenarios in which multiple HSUPA 2 ms TTI UEs perform uplink data transmission at a high speed in a cell. This feature reduces interference between UEs and increases the cell uplink throughput. If the data transmission time of the UEs overlaps, the gains from this feature are affected. UE mobility causes the data transmission time of the UEs to partially overlap and therefore UEs performing soft handovers are not suitable for time division scheduling. Indoor UEs are less likely to perform soft handovers than outdoor UEs in a network using macro base stations and more likely to be selected for time division scheduling. Therefore, gains from this feature are more noticeable indoors.

This feature does not apply to scenarios in which multiple RRUs are in the same cell because Uu interface resources are not shared across the RRUs.


System Capacity

The HSUPA Time Division Scheduling feature increases the cell uplink throughput in scenarios in which multiple HSUPA 2 ms TTI UEs perform uplink data transmission at a high speed in a cell.

If the WRFD-010691 HSUPA UL Interference Cancellation feature is not activated, gains from the HSUPA Time Division Scheduling feature are as follows:

In single-antenna scenarios, the maximum gains (10%-90%) are achieved when all UEs in the cell are time-division scheduled UEs. There are few or no gains from this feature when few or no UEs are time-division scheduled UEs.

In double-antenna scenarios, gains from this feature are less considerable than those in single-antenna scenarios.

If the WRFD-010691 HSUPA UL Interference Cancellation feature is activated, gains from the HSUPA Time Division Scheduling feature are less considerable.

With the HSUPA Time Division Scheduling feature, some HSUPA UEs have their timing aligned by chip offset configurations. The timing alignment, however, leads to DL DPCCH pilot bit alignment and TPC bit alignment and increases the transmit power PAR of RRUs. When downlink transmit power of carriers in a cell is insufficient, which usually occurs during busy hours, this feature causes HSDPA throughput in the cell to reduce by approximately 10%.

Network Performance

With this feature, some HSUPA UEs have their timing aligned by chip offset configurations. The timing alignment, however, leads to DL DPCCH pilot bit alignment and TPC bit alignment and increases the transmit power PAR of RRUs. When downlink transmit power of carriers in a cell is insufficient, the access success rate and call drop rate in the cell may slightly deteriorate.

4.29.3 NEs

This feature is implemented on the RNC and NodeB and requires the UEs to be HSUPA UE category 6 or above. This feature does not affect the CN.

RAN15.0




4-125

4.29.4 Hardware

BTS 3803E and 3900 series WCDMA base stations except the BTS3902E support this feature. 3900 series WCDMA base stations must be configured with the WBBPf board and downlink services in the cell cannot be set up on the WBBPa board.


The proprietary IE TDM schedule information is added in Iub interface messages AUDIT RESPONSE and RESOURCE STATUS INDICATION. This IE helps the RNC determine whether the HSUPA Time Division Scheduling feature has been activated and how many HSUPA UEs need to have their timing aligned.


License



The following cell-level parameters have been introduced in the NodeB MML command SET ULOCELLMACEPARA:

HSUPATDSCHSW: switch for HSUPA time division scheduling

HSUPATDALIGNUENUM: number of HSUPA UEs to have their timing aligned for HSUPA time division scheduling


The following counters have been introduced on the NodeB side to accommodate this feature.

Counter Name Description

VS.HSUPA.TDMUserNum.Mean Average number of valid time-division scheduling users in a cell

VS.HSUPA.TDMSch.ActRatio Time-division scheduling algorithm validity probability in a cell

Fault Management

None



WRFD-01061403 HSUPA 2ms TTI

WRFD-010636 SRB over HSUPA


None

../NodeBParaHtml/comm/para/ULoCellMacePara-hsupaTdSchSw.html

../NodeBParaHtml/comm/para/ULoCellMacePara-hsupaTdAlignUeNum.html

RAN15.0




4-126

Impacted Features

WRFD-150206 Turbo IC

Gains from Turbo IC are reduced when the HSUPA Time Division Scheduling feature is enabled because some UEs are configured to meet the timing alignment requirement.

WRFD-010638 Dynamic CE Resource Management

Use the WRFD-010638 Dynamic CE Resource Management feature with the HSUPA Time Division Scheduling feature.

If the Dynamic CE Resource Management feature is not used with the HSUPA Time Division Scheduling feature but the WRFD-021101 Dynamic Channel Configuration Control (DCCC) feature is, the maximum UE rate is limited when DCCC rate reduction is triggered. The UEs will not be selected for time division scheduling.

4.30 WRFD-150231 RIM Based UMTS Target Cell Selection for LTE (New/Optional)


In versions earlier than RAN15.0, load information cannot be shared between UMTS and LTE when UMTS and LTE coverage overlaps. The following problems will occur when load information cannot be shared:

The CS fallback (CSFB) from LTE to UMTS may fail when the target UMTS cell becomes congested because the load of the target UMTS cell was not considered.

The load-based LTE-to-UMTS handover may fail without considering the load state of the target UMTS cell. This affects the success rate of the handover from LTE to UMTS, increases system signaling message exchanges, and delays the handover.

This feature is introduced in UMTS and LTE products to address the preceding problems. It enables the eNodeB to obtain the load information of the UMTS cells through the RIM procedure during the CSFB and load-based LTE-to-UMTS handover procedure. When UMTS and LTE coverage overlaps, the eNodeB is able to select the proper target UMTS cell according to the cell load before the handover from LTE to UMTS. This increases the success rate of LTE-to-UMTS handovers and reduces inter-RAT ping-pong handovers.


System Capacity

No impact.

Network Performance

This feature improves the CS fallback from LTE to UMTS when the UMTS cell is congested or overloaded, increases the preparation success rate of load-based LTE-to-UMTS handovers, and reduces inter-RAT ping-pong handovers.

4.30.3 NEs


RAN15.0




4-127

This feature requires support from the CN. The SGSN or MME must support load information transmission between UMTS and LTE through the RIM procedure.

4.30.4 Hardware

No impact.


No impact.


License



The following switch has been introduced on the RNC side, as described in Table 4-42. No switch has been introduced on the NodeB side.

Table 4-42 New RNC switch

Chang

e Type

MO Switch Name Parameter

ID

MML

Command

Description

New URRCTRLSWITCH

INTERRAT_LOAD_REPORT_FOR_LTE_SWITCH

PROCESSSWITCH

SET URRCTRLSWITCH

This new switch enables inter-RAT load report for LTE based on RIM.


No impact.

Fault Management

No impact.



The LTE feature LOFD-001033 CS Fallback to UTRAN or LOFD-001044 Inter-RAT Load Sharing to UTRAN has been activated.

WRFD-020106 Load Reshuffling feature

WRFD-020107 Overload Control feature

RAN15.0




4-128

4.31 WRFD-150216 Load Based PS Redirection from UMTS to LTE (New/Optional)


This feature enables a UE served by a heavily loaded cell to be shifted from UMTS to LTE through a redirection, which reduces the load of the serving UMTS cell.


System Capacity

No impact.

Network Performance

This feature allows UEs in congested UMTS cells to be redirected to LTE cells when UMTS cells are moderately congested. This method relieves the congestion in the current UMTS cell and decreases user access failures. As a result, the overall UMTS and LTE network performance is enhanced. For example, the RRC congestion rate declines.

4.31.3 NEs


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

4.31.4 Hardware

No impact.


No impact.


License




RAN15.0




4-129


Change Type


New UCELLLDR

DlLdrEleventhAction



New UCELLLDR

UlLdrNinthAction



New UCELLLDR

UlPSU2LHOUeNum


This new parameter specifies the number of UEs for performing uplink UMTS-to-LTE PS handovers. The parameter value can be set based on the ratio of high-speed UEs to PS UEs. If the ratio is high, this parameter can be set to a smaller value. Otherwise, the parameter value can be changed to a larger one. The load reshuffling (LDR) algorithm aims to slowly reduce cell loads. Therefore, this parameter is set to a small value.

RAN15.0




4-130

Change Type


New UCELLLDR

DlPSU2LHOUeNum






Change Type


Description

New VS.U2LTEHO.RRCRelease.Load

U2LTE.HO.CELL

Number of Measurement-based U2L PS Redirections Triggered by LDR for Cell

New VS.U2LTEHO.RRCRelease.Load.Blind

U2LTE.HO.CELL

Number of LDR-triggered U2L PS Blind Redirections for Cell

Fault Management

No impact.


Impacted Features




4.32 WRFD-150232 Multiband Direct Retry Based on UE Location (New/Optional)


During service establishment or reconfiguration, this feature performs the following actions on UEs based on UE path loss:

Enables UEs in the cell center to access a high-frequency cell.

Enables UEs at the cell edge to access a low-frequency cell.

This feature implements UE steering and load sharing between high- and low-frequency cells.

RAN15.0




4-131

With this feature, the UMTS 900 MHz band can cover the cell edge, thereby improving intensive coverage and increasing the total number of UEs in UMTS900 and UMTS2100 cells.


System Capacity

Enabling this feature may increase the number of admitted UEs in UMTS850 and UMTS900 cells if the cells meet the following condition during busy hours before this feature is enabled:

10 x Log (VS.MeanTCP - MaxTxPower/10) > 60%

Network Performance

In UMTS850 and UMTS900 cells, enabling this feature may decrease the access success rate and cell throughput and increase the call drop rate due to the increased proportion of CEUs. In UMTS1900 and UMTS2100 cells, enabling this feature may increase the access success rate and cell throughput and decrease the call drop rate.

Additionally, this feature increases the number of inter-frequency handovers due to more DRDs.

4.32.3 NEs


New counters on the M2000 must be configured consistently with those on the RNC. New parameters on the Configuration Management Express (CME) must be configured consistently with those on the RNC.

4.32.4 Hardware

No impact.


No impact.


License

A cell-level license for this feature is added on the RNC side.

Feature ID Feature Name License Control Item License Configured on…

Sales Unit

WRFD-150232 Multiband Direct Retry Based on UE Location

Multiband Direct Retry Based on UE Location

RNC per Cell


This feature adds the following parameters to the RNC.

../RNCParaHtml/mbsc/m-para/ucell_maxtxpower.html

RAN15.0




4-132

Change Type Parameter ID MML Command

Description

New FuncSwitch2: BASED_UE_LOC_DRD_SWITCH

ADD/MOD UCELLLICENSE

Whether to activate the license for the Multiband Direct Retry Based on UE Location feature. The RNC instructs the CCUs in a low-frequency cell to preferentially access a high-frequency neighboring cell through a blind handover and instructs the CEUs in a high-frequency cell to preferentially access a low-frequency neighboring cell through a blind handover if the following conditions are met:

The license is activated.

BasedUELocDRDSwitch is turned on.

The path loss requirement is met.

New BasedUELocDRDSwitch

SET UDRD

ADD/MOD UCELLDRD

Whether to enable the Multiband Direct Retry Based on UE Location feature. This feature implements UE steering between the high- and low-frequency bands based on UE path loss during service setup or reconfiguration. The CEUs in a high-frequency cell are instructed to preferentially access a co-sector and co-sited low-frequency cell through a blind handover. The CCUs in a low-frequency cell are instructed to preferentially access a co-sector and co-sited high-frequency cell through a blind handover.

If this parameter is configured at both the RNC and cell levels, the cell-level setting prevails.

New TraffTypeForBasedUELoc

SET UDRD

ADD/MOD UCELLDRD

Types of service to which the Multiband Direct Retry Based on UE Location feature applies. When this parameter is set to RT, this feature applies to real-time services. When this parameter is set to NRT, this feature applies to non-real-time services.


New PathlossThdForEdge

SET UDRD

ADD/MOD UCELLDRD

Path loss threshold for CEUs. If a UE is accessing a high-frequency cell and the UE path loss is greater than or equal to this threshold, the RNC determines that the UE is at the cell edge and triggers the Multiband Direct Retry Based on UE Location feature.


New PathlossThdForCenter

SET UDRD

ADD/MOD UCELLDRD

Path loss threshold for CCUs. If a UE is accessing a low-frequency cell and the UE path loss is less than or equal to this threshold, the RNC determines that the UE is in the cell center and triggers the Multiband Direct Retry Based on UE Location feature.

../RNCParaHtml/mbsc/m-para/ucelllicense_funcswitch2.html

../RNCParaHtml/mbsc/m-para/ucelldrd_baseduelocdrdswitch.html

../RNCParaHtml/mbsc/m-para/udrd_baseduelocdrdswitch.html

../RNCParaHtml/mbsc/m-para/udrd_baseduelocdrdswitch.html

../RNCParaHtml/mbsc/m-para/ucelldrd_trafftypeforbasedueloc.html

../RNCParaHtml/mbsc/m-para/ucelldrd_trafftypeforbasedueloc.html

../RNCParaHtml/mbsc/m-para/ucelldrd_pathlossthdforedge.html

../RNCParaHtml/mbsc/m-para/ucelldrd_pathlossthdforedge.html

../RNCParaHtml/mbsc/m-para/ucelldrd_pathlossthdforcenter.html

../RNCParaHtml/mbsc/m-para/ucelldrd_pathlossthdforcenter.html

RAN15.0




4-133


Description


New BasedUELocDRDRemainThd

SET UDRD

ADD/MOD UCELLDRD

Available load threshold. The Multiband Direct Retry Based on UE Location feature is allowed in a neighboring cell only when the available load of the neighboring cell is greater than or equal to this threshold.



This feature adds the following counters to the RNC.

Change Type Counter ID Measurement Unit

Description

New VS.UELocation.MultiBand.DRD.AttIn

RB.Cell Number of Incoming Inter-Frequency DRD Attempts Triggered by Multiband Direct Retry Based on UE Location for Cell

New VS.UELocation.MultiBand.DRD.SuccIn

RB.Cell Number of Successful Incoming Inter-Frequency DRDs Triggered by Multiband Direct Retry Based on UE Location for Cell

New VS.UELocation.MultiBand.DRD.AttOut

RB.Cell Number of Outgoing Inter-Frequency DRD Attempts Triggered by Multiband Direct Retry Based on UE Location for Cell

New VS.UELocation.MultiBand.DRD.SuccOut

RB.Cell Number of Successful Outgoing Inter-Frequency DRDs Triggered by Multiband Direct Retry Based on UE Location for Cell

This feature does not affect the counters on the NodeB side.

Fault Management

None



WRFD-020400 DRD Introduction Package

WRFD-010610 HSDPA Introduction Package

../RNCParaHtml/mbsc/m-para/ucelldrd_baseduelocdrdremainthd.html

../RNCParaHtml/mbsc/m-para/ucelldrd_baseduelocdrdremainthd.html

RAN15.0




4-134

WRFD-020110 Multi Frequency Band Networking Management


None

Impacted Features

This feature takes precedence over the WRFD-02040004 Traffic Steering and Load Sharing During RAB Setup feature (algorithm name: Inter-Frequency DRD for Load Balancing). When both features are enabled, load balance between frequency bands may be affected.

This feature does not take effect for UEs that are always online, because such UEs initiate services in the CELL_PCH or CELL_FACH state.

4.33 WRFD-150233 Differentiated Service Based on Resource Reservation (New/Optional)


When downlink power resources become insufficient on networks, the Differentiated Service Based on Resource Reservation feature limits the amount of downlink resources consumed by low-priority users to reserve more power for high-priority users. In this way, high-priority users experience improved service


System Capacity

Cell capacity changes if the following conditions are met:

When users in both resource groups A and B need to transmit data and users in A have better signal quality than users in B, the amount of downlink power resources available to group A is limited if the downlink power consumed by A reaches the configured ratio. Then downlink power resources are allocated to users in resource group B, decreasing the cell throughput.

When users in both resource groups A and B need to transmit data and users in B have better signal quality than users in A, the amount of downlink power resources available to group A is limited if the downlink power consumed by A reaches the configured ratio. Then downlink power resources are allocated to users in resource group B, increasing the cell throughput.

Network Performance

In the scenarios of insufficient downlink power resources, the data rates of users in a resource group may be lower than the guaranteed bit rate (GBR) if the resource group contains excessive users or the configured maximum HSDPA power ratio for the resource group is low. In severe conditions, low-priority users in the resource group may experience call drops because they are not scheduled for a long period of time.

4.33.3 NEs

Differentiated Service Based on Resource Reservation is implemented on the RNC, NodeB, and CME.

Differentiated Service Based on Resource Reservation has no impact on users or on the core network (CN).

RAN15.0




4-135

4.33.4 Hardware

NodeB hardware

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

− The DBS3800 series base stations must be configured with the EBBC, EBBM, or EBBCd board.

− The 3900 series base stations including the BTS3900, DBS3900, BTS3900C, and BTS3902E must be configured with the WBBPb, WBBPd, or WBBPf board.

RNC hardware

None


The NodeB Application Part (NBAP) signaling message Physical Shared Channel Reconfiguration sent to the NodeB contains a proprietary information element (IE), which carries information about resource groups in a cell.

The NBAP signaling message Radio Link Setup, Radio Link Addition, or Radio Link Reconfiguration sent to the NodeB contains a proprietary IE, which carries information about resource groups that users belong to.


License

An RNC-level license control item has been introduced to accommodate this feature. Operators need to purchase the license before deploying the feature.


The following command has been introduced on the RNC side to accommodate this feature.

Table 4-45 New RNC command


New ADD UCELLRESGRP

Used to add resource reservation parameters for a cell.

The following parameter has been introduced on the RNC side to accommodate this feature.

Table 4-46 New RNC parameter


New ResGroupId ADD UUSERGRPSPIMAP Used to specify the resource group that SPI users belong to.


The following counters have been introduced on the NodeB side to accommodate this feature:

../RNCParaHtml/mbsc/m-para/uusergrpspimap_resgroupid.html

RAN15.0




4-136


Change Type Counter Name Measurement Unit Description

New VS.HSDPAPwrRatio.Mean.ResG0

HSDPA.LOCELL Average Transmit Power Ratio for HSDPA Users In Resource Group 0







Fault Management

None



WRFD-010611 HSDPA Enhanced Package


None

Impacted Features

WRFD-140223 MOCN Cell Resource Demarcation

Differentiated Service Based on Resource Reservation cannot take effect in cells where MOCN Cell Resource Demarcation has been activated.

WRFD-020806 Differentiated Service Based on SPI Weight

Differentiated Service Based on SPI Weight provides differentiated services by adjusting SPI weights based on user priorities. However, Differentiated Service Based on Resource Reservation limits the amount of power resources available to users based on user priorities during busy hours. If Differentiated Service Based on Resource Reservation is used with Differentiated Service Based on SPI Weight, the maximum HSDPA power ratio configured in the former feature affects user differences in the latter feature when downlink power resources are insufficient.

WRFD-020128 Quality Improvement for Subscribed Service

WRFD-020132 Web Browsing Acceleration

WRFD-020133 P2P Downloading Rate Control during Busy Hour

The above three features introduce the differentiated service management function. If these features are used with the Differentiated Service Based on Resource Reservation feature, service differentiation becomes less obvious.


RAN15.0




4-137

Platinum users are not grouped into any resource group based on SPIs, and therefore limitations on HSDPA power consumption do not apply to them. The Differentiated Service Based on Resource Reservation feature is also not applicable to platinum users.

4.34 WRFD-150235 DPCH Maximum Power Restriction (New/Optional)


This feature is an optional feature in RAN15.0.

When non-HSPA power consumption in a cell is high, this feature increases downlink cell capacity by reducing the maximum transmit power of the A-DPCH carrying HSDPA UEs.

4.34.2 System Capacity and Network Impact

System Capacity

When non-HSPA power consumption is high, this feature saves downlink power resources by reducing the maximum transmit power of the A-DPCH carrying HSDPA UEs. If the number of HSDPA UEs is large in a cell and downlink non-HSPA power is high, this feature reduces downlink non-HSPA power by 5% to 15%. The saved power can admit 5% to 15% extra UEs in this cell when non-HSPA power consumption in this cell remains unchanged.

Network Impact

This feature positively affects network performance as follows:

When the number of UEs in a cell remains unchanged and the traffic volume in this cell is sufficient, more power will be saved to increase downlink cell throughput.

When potential UEs attempt to access a cell in the case of downlink power congestion, this feature increases the access success rate during busy hours.

This feature also has negative impact on network performance. If the maximum transmit power of the A-DPCH is reduced, Uu-interface synchronization probability will decrease, which increases the call drop rate for HSDPA UEs. However, this feature causes call drops only for cell-edge HSDPA UEs. If a large number of HSPDA UEs camp on the cell edge, this feature saves more downlink power but triggers more call drops for these HSDPA UEs.

4.34.3 NEs

This feature is implemented on the NodeB.

4.34.4 Hardware

This feature has the following impacts on NodeB hardware:

The BTS3812E, BTS3812A, or BTS3812AE must be configured with the EBBI or EBOI board. Alternatively, these base stations must be configured with the EULP and EDLP boards, or the EULPd and EDLP boards. Downlink services must be established on the EBBI or EBOI, or the EDLP board (The EDLP board processes HSPA services).

The DBS3800 must be configured with the EBBC or EBBCd board, and downlink services must be established on the EBBC or EBBCd board. The BBU3806C must be configured with the EBBM board, and downlink services must be established on the EBBM board.

RAN15.0




4-138

3900 series base stations must be configured with the WBBPb, WBBPd, or WBBPf board, and downlink services must be established on the WBBPb, WBBPd, or WBBPf board.


No impact.


License

Table 4-48 License information for DPCH Maximum Power Restriction


WRFD-150235

DPCH Maximum Power Restriction

DPCH Maximum Power Restriction (per Cell)

NodeB per cell


Two parameters have been added on the NodeB side, as described in Table 4-49.

Table 4-49 New parameters

Change Type


Description

New dpchMaxTxPwrRestrSw

SET ULOCELLALGPARA

This parameter specifies whether to enable the DPCH Maximum Power Restriction feature.

When this switch is turned on, the NodeB configures the maximum transmit power of the A-DPCH according to whether signaling messages are transmitted on the A-DPCH.

When this switch is turned off, the maximum transmit power of the downlink A-DPCH is set to the value of RlMaxDlPwr and remains unchanged.

New dpchMaxPwrRtrLoadStat

SET ULOCELLALGPARA

This parameter specifies the load state after the DPCH Maximum Power Restriction feature takes effect.

This feature is triggered only when the downlink non-HSPA power load is heavier than the sum of threshold corresponding to

dpchMaxPwrRtrLoadStat and 10%.


The following counter has been added on the NodeB side.

../NodeBParaHtml/comm/para/ULoCellAlgPara-dpchMaxTxPwrRestrSw.html

../NodeBParaHtml/comm/para/ULoCellAlgPara-dpchMaxTxPwrRestrSw.html

../RNCParaHtml/mbsc/m-para/ucellrlpwr_rlmaxdlpwr.html

../NodeBParaHtml/comm/para/ULoCellAlgPara-dpchMaxPwrRtrLoadStat.html



RAN15.0




4-139

Table 4-50 New counter

Change Type


New VS.HSDPA.DpchMaxPwrRestr.ActRatio

HSDPA.LOCELL Maximum DPCH power restriction algorithm validity probability

Fault Management

No impact.



This feature requires the WRFD-010610 HSDPA Introduction Package feature.


None

Impacted Features

WRFD-150230 DPCH Pilot Power Adjustment

This feature can be activated together with the WRFD-150230 DPCH Pilot Power Adjustment feature for a cell. For HSDPA UEs, the WRFD-150230 DPCH Pilot Power Adjustment feature reduces the transmit power of the pilot field on the A-DPCH. The WRFD-150235 DPCH Maximum Power Restriction feature reduces the maximum transmit power of the A-DPCH.

When downlink load in a cell is heavy, the two features can be used together to provide more noticeable power reduction gains. However, this may reduce the accuracy of SIR estimations and increase the call drop rate for HSDPA UEs.

WRFD-010652 SRB over HSDPA

This feature can be activated together with the WRFD-010652 SRB over HSDPA feature for a cell. When the SRB over HSDPA feature is activated, downlink power will be controlled using the F-DPCH. As a result, the application scope of this feature is narrowed. This feature does not take effect on UEs using the SRB over HSDPA feature.

4.35 WRFD-150236 Load Based Dynamic Adjustment of PCPICH (New/Optional)


This feature reduces the P-CPICH transmit power when downlink non-HSPA load in a cell is heavy. This reduces downlink non-HSPA cell load and therefore improves cell downlink capacity. When downlink non-HSPA load in a cell is light, this feature restores the P-CPICH transmit power to ensure service quality for online UEs.

RAN15.0




4-140


System Capacity

This feature reduces the P-CPICH transmit power when downlink non-HSPA load in a cell is heavy. This reduces power consumption of common channels and cell coverage. In this situation, cell-edge UEs are handed over to neighboring cells, which reduces downlink non-HSPA load and increases downlink capacity of the current cell. For example, the value for PCPICHPower is 10% of the value for MaxTxPower and the maximum P-CPICH power reduction is 3 dB. If downlink non-HSPA load in a cell is extremely high and the number of UEs in this cell is large, this feature saves 10% to 15% of downlink non-HSPA cell power. The saved power can admit 10% to 15% extra UEs or increase at least 5% of the average cell throughput.

The P-CPICH transmit power can be higher than the value for PCPICHPower. In this case, cell coverage will increase but the available HSDPA power will decrease. This reduces average HSDPA throughput if there are data transmission requirements.

Network Performance

This feature reduces the P-CPICH transmit power when downlink non-HSPA load in a cell is heavy. As result, downlink non-HSPA cell load is reduced. When downlink power resources are congested, this feature increases the access success rate during busy hours.

However, after the reduction of P-CPICH transmit power, cell coverage shrinks, leading to coverage holes. Coverage holes cause the access success rate and the call drop rate for cell-edge UEs to deteriorate. This increases the number of handovers. In multi-carrier scenarios, cells that have the same coverage now may have different coverage. This affects the camping policy and increases the blind-handover failure probability (Blind handovers here include blind-handover-based DRD and LDR inter-frequency handovers). Ultimately, the performance of service steering will be affected.

The impact on network performance is determined by the actual cell coverage and the distribution of cell-edge UEs.

If cell coverage is good and the number of cell-edge UEs is small, handovers and the call drop rate will decrease.

If cell coverage is bad and the number of cell-edge UEs is large, handovers and the call drop rate will increase.

After the power adjustment, if more cells that have the same coverage now have different coverage, the probability of blind-handover failures will increase.

4.35.3 NEs


4.35.4 Hardware

No impact.


No impact.

../RNCParaHtml/mbsc/m-para/upcpich_pcpichpower.html

RAN15.0




4-141


License

Table 4-51 lists the license information for this feature

Table 4-51 License information for this feature

Feature ID Feature Name License Description NE Sales Unit

WRFD-150236

Load Based Dynamic Adjustment of PCPICH

Load Based Dynamic Adjustment of PCPICH (per cell)

RNC per cell


The following parameters have been modified or added on the NodeB side, as described in Table 4-52.

Table 4-52 New and modified parameters

Change Type


Change Description

Modified NBMLdcAlgoSwitch: DLLOAD_BASED_PCPICH_PWR_ADJ_SWITCH

ADD UCELLALGOSWITCH

This parameter controls the load-based dynamic adjustment of PCPICH algorithm.

This algorithm takes effect when this parameter is set to ON and the license for this algorithm is activated. In this situation, the enabled TCP-based intra-frequency load balancing algorithm becomes disabled.

New PcpichPwrDownDlLoadState

ADD UCELLLDM

This parameter specifies the downlink non-HSPA load state. This parameter is used by the load-based dynamic adjustment of PCPICH algorithm to determine whether to reduce the P-CPICH transmit power.

If downlink non-HSPA load is equal to or heavier than the load specified in this parameter, the load-based dynamic adjustment of PCPICH algorithm reduces the P-CPICH transmit power according to the step specified in the PCPICHPowerPace parameter.

New PcpichPwrUpDlLoadState

ADD UCELLLDM

This parameter specifies the downlink non-HSPA load state. This parameter is used by the load-based dynamic adjustment of PCPICH algorithm to determine whether to increase P-CPICH transmit power.

If downlink non-HSPA load is equal to or lighter than the load specified in this parameter, the load-based dynamic adjustment of PCPICH algorithm increases P-CPICH transmit power according to the step specified in the PCPICHPowerPace parameter.

../RNCParaHtml/mbsc/m-para/ucellalgoswitch_nbmldcalgoswitch.html

../RNCParaHtml/mbsc/m-para/ucellalgoswitch_nbmldcalgoswitch.html

../RNCParaHtml/mbsc/m-para/ucellldm_pcpichpwrdowndlloadstate.html

../RNCParaHtml/mbsc/m-para/ucellldm_pcpichpwrdowndlloadstate.html

../RNCParaHtml/mbsc/m-para/ucellldb_pcpichpowerpace.html

../RNCParaHtml/mbsc/m-para/ucellldm_pcpichpwrupdlloadstate.html

../RNCParaHtml/mbsc/m-para/ucellldm_pcpichpwrupdlloadstate.html

../RNCParaHtml/mbsc/m-para/ucellldb_pcpichpowerpace.html

RAN15.0




4-142

Change Type


Change Description

Modified FuncSwitch2: LOAD_BASED_PCPICH_PWR_ADJ

ADD UCELLLICENSE

This parameter is the license control item for the load-based dynamic adjustment of PCPICH algorithm.


The following parameters have been modified on the NodeB side, as described in Table 4-53.

Table 4-53 Modified counters

Change Type


Modified VS.CellBreath.CPICHMin.Time

ALGO.Cell In versions earlier than RAN15.0, the measurement is based on the TCP-based intra-frequency load balancing algorithm.

In RAN15.0, the measurement is based on the load-based dynamic adjustment of PCPICH algorithm.

Modified VS.CellBreath.CPICHMax.Time

ALGO.Cell

Modified VS.CellBreath.CPICHUp

ALGO.Cell

Modified VS.CellBreath.CPICHDown

ALGO.Cell

Fault Management

No impact.



None


None

Impacted Features

After this feature is activated, the TCP-based intra-frequency load balancing and uplink intra-frequency load balancing functions are disabled.

../RNCParaHtml/mbsc/m-para/ucelllicense_funcswitch2.html

RAN15.0




4-143

4.36 WRFD-140225 Narrowband Interference Suppression (New/Optional)


The Narrowband Interference Suppression feature is introduced to address increasingly severe problems caused by narrowband interferences on UMTS 900/850 commercial networks. With this feature, the NodeB scans the frequency spectrum within the receive bandwidth of a UMTS carrier to rapidly identify stable narrowband interferences (with millisecond-level changes in frequency or power) and dynamically configures a filter stopband for the receiver to suppress narrowband interferences.


System Capacity

When narrowband interferences exist within the receive bandwidth of a carrier, enabling Narrowband Interference Suppression improves the system capacity as follows:

Reduces the uplink RTWP by 7 dB to 35 dB

Enhances the uplink coverage capability

Increases the uplink capacity

The benefits provided by this feature are significant when the narrowband interference is strong and the interference bandwidth is low.

When no narrowband interference exists, the narrowband interference suppression algorithm itself has no negative impact on system capability. However, the suppression increases the uplink processing delay and may have certain negative impacts on the uplink demodulation function of some attenuated channels (for example, the PA3 channel). Gaussian channels are not affected. Therefore, enabling this feature may decrease the uplink capacity by a maximum of 5% when no narrowband interference exists.

The performance of this feature is subject to service types, narrowband interference strength, and narrowband interference bandwidth. Therefore, the performance of this feature cannot be quantized but depends on live network environments.

Network Performance

When narrowband interferences exist within the receive bandwidth of a carrier, enabling Narrowband Interference Suppression increases the access success rate and decreases the call drop rate without impacting other KPIs.

When no narrowband interference exists, enabling Narrowband Interference Suppression decreases the performance of low-rate services by a maximum of 0.4 dB and high-rate services by a maximum of 1.8 dB.

4.36.3 NEs

No impact.

4.36.4 Hardware

The Narrowband Interference Suppression feature is supported only by NodeB 3900 series (expect 3902E) configured with any of the RF modules that support UMTS 850/900 frequency bands. These RF modules include MRFUd, RRU3928, RRU3929, MRFUe, RRU3926, and RRU3942.

RAN15.0




4-144


No impact.


No impact.

License

The existing license for the Narrowband Interference Suppression feature is still applicable on a per cell basis.


The following parameters have been added on the NodeB side to accommodate this feature.

Change Type Parameter ID


New NBIS ADD ULOCELL, MOD ULOCELL

This new parameter specifies whether to enable the Narrowband Interference Suppression feature.


No impact.

Fault Management

Change Type

Alarm Name Description

Modified Local Cell Capability Decline

The cause value 25 has been added. The alarm with cause value 25 is generated when a cell is enabled with the Narrowband Interference Suppression feature but does not support the feature.



None


None

Impacted Features

After the Narrowband Interference Suppression feature is enabled, all the RTWP values used are those measured after narrowband interference suppression. Therefore, this feature affects all the following features that use RTWP values:

WRFD-020101 Admission Control

WRFD-01061202 HSUPA Admission Control

../NodeBParaHtml/comm/para/ULoCell-nbis.html

RAN15.0




4-145

WRFD-020136 Anti-Interference Scheduling for HSUPA

WRFD-01061209 HSUPA HARQ and Fast UL Scheduling in Node B

WRFD-01061402 Enhanced Fast UL Scheduling

For details, see section 10.6.1 "System Capacity and Network Performance" in Load Control Feature Parameter Description.

4.37 MRFD-211901/ MRFD-221901 Multi-RAT Carrier Joint Shutdown(Optional/New)


This multi-mode feature is new in SRAN8.0. It includes the following on the GBSS15.0, RAN15.0:

MRFD-211901 Multi-RAT Carrier Joint Shutdown (GBTS)

MRFD-221901 Multi-RAT Carrier Joint Shutdown (NodeB)

With the development of mobile broadband services, areas covered by GSM and UMTS networks are increasing at great speeds. The Multi-RAT Carrier Joint Shutdown feature applies to these areas. With this feature, a UMTS cell can be intelligently shut down or restarted depending on the traffic volume. When the traffic volumes of both the GSM and UMTS cells are low, the UMTS cell is shut down and GSM cells provide services for all UEs in the area. When the traffic volumes of the GSM cells increase, the UMTS cell is restarted to meet the traffic requirements. By intelligently shutting down the UMTS cell, this feature reduces the overall power consumption of the GSM and UMTS networks and implements energy conservation and emission reduction, reducing the operating expense (OPEX).


System Capacity

No impact.

Network Performance

This feature affects the UE peak rates, call drop rate on the FACH, and service availability to UEs supporting only UMTS as follows:

UE peak rates

If there are multi-mode terminals on the UMTS network, the multi-mode terminals are handed over or reselected to the GSM network after the UMTS cell is shut down. These multi-mode terminals can initiate services only on the GSM network before the UMTS cell is restarted. Therefore, the peak rates of and experience in data services for these multi-mode terminals are negatively affected.

Call drop rate on the FACH

Before shutting down the UMTS cell, the RNC releases the connections of UEs in the CELL_FACH state. This is to enable the UEs to reselect a GSM cell if there are UEs in the CELL_FACH state in the UMTS cell and DynShutDownCchUserSwitch is set to OFF. As a result, the call drop rate on the FACH increases.

Service availability to UEs supporting only UMTSAfter the UMTS cell is shut down, UEs supporting only UMTS cannot initiate services.

This feature may also affect the inter-RAT handover and cell reselection success rates, prolong the access delay, and cause UEs in the idle state to drop from the network. Details are as follows:

Inter-RAT handover and cell reselection success rates

Load%20Control.htm

Load%20Control.htm

../RNCParaHtml/mbsc/m-para/ucelldynshutdown_dynshutdowncchuserswitch.html

RAN15.0




4-146

This feature triggers the following handover or cell reselection interoperability procedures between the GSM and UMTS networks:

− Before the UMTS cell is shut down, the online multi-mode UEs on the UMTS network are handed over or reselected to the GSM network.

− After the UMTS cell is restarted, the online multi-mode UEs are reselected to the UMTS network.

As the number of inter-RAT handovers and cell reselections increase, the inter-RAT handover and cell reselection success rates may be affected.

Access delay and UEs in the idle state dropping from the network

After the UMTS cell is shut down, the multi-mode terminals in the idle state are reselected to a GSM cell. After the UMTS cell is restarted, the multi-mode terminals in the idle state are reselected to the UMTS cell. During the cell reselection, the following cases may occur:

− The multi-mode terminals in the idle state may drop from the network after cell reselection.

− The routing areas of GSM and UMTS cells may be different, and the cell reselection triggers LA updates. The multi-mode terminals in the idle state occupy access channel resources during the LA updates, temporarily affecting the access of other UEs.

4.37.3 NEs

This feature is implemented on the BSC, RNC, NodeB, and M2000.

UEs must support both GSM and UMTS.

4.37.4 Hardware

This feature requires information exchange between the GSM and UMTS networks. If the base station controllers are a BSC and an RNC, the physical connections for the Iur-g interface between the BSC and the RNC must be added.


The Iur-g interface must be configured between the BSC and the RNC. The Iur-g interface is a Huawei proprietary interface and enables control information exchange between the BSC and the RNC by Huawei proprietary messages.


License

A site-level license for this feature is added on the BSC side.

A site-level license for this feature is added on the NodeB side.


This feature introduces the following RNC-level parameters.

Change Type


New IRATCommonMeasSwitch

SET UMBSCCRRM Whether to enable the Multi-RAT Carrier Joint Intelligent Shutdown feature

../RNCParaHtml/mbsc/m-para/umbsccrrm_iratcommonmeasswitch.html

../RNCParaHtml/mbsc/m-para/umbsccrrm_iratcommonmeasswitch.html

RAN15.0




4-147

Change Type


New IRATShutdownDLLoadThd

ADD/MOD UCELLDYNSHUTDOWN

Downlink load threshold for triggering UMTS cell intelligent shutdown

New IRATShutdownULLoadThd


Uplink load threshold for triggering UMTS cell intelligent shutdown

New IRATshutdownGSMLoadThd


Neighboring GSM load threshold for triggering UMTS cell intelligent shutdown

New IRATshutdownGSMLoadHyst


Neighboring GSM load hysteresis for UMTS cell restart

New IRATSwitchOnHystTimeLen

SET URNCCELLSHUTDOWNPARA

Time latency for UMTS cell restart. A UMTS cell can be restarted only after its shutdown period is longer than the value specified by this parameter.

New IRATshutdownAdjTime

SET URNCCELLSHUTDOWNPARA

Period for cell shutdown decision. When a UMTS cell has met shutdown conditions for a period longer than this parameter value, the UMTS cell is shut down.

New NIRATOverLap

ADD/MOD U2GNCELL

Overlapping coverage flag. When this parameter is set to YES, one or multiple neighboring GSM cells cover the same area as a UMTS cell.

Modified DynShutDownType


Type of cell shutdown.

This feature introduces the following BSC-level parameters.

../RNCParaHtml/mbsc/m-para/ucelldynshutdown_iratshutdowndlloadthd.html



../RNCParaHtml/mbsc/m-para/ucelldynshutdown_iratshutdownulloadthd.html



../RNCParaHtml/mbsc/m-para/ucelldynshutdown_iratshutdowngsmloadthd.html



../RNCParaHtml/mbsc/m-para/ucelldynshutdown_iratshutdowngsmloadhyst.html



../RNCParaHtml/mbsc/m-para/urnccellshutdownpara_iratswitchonhysttimelen.html



../RNCParaHtml/mbsc/m-para/urnccellshutdownpara_iratshutdownadjtime.html

../RNCParaHtml/mbsc/m-para/urnccellshutdownpara_iratshutdownadjtime.html

../RNCParaHtml/mbsc/m-para/u2gncell_niratoverlap.html

../RNCParaHtml/mbsc/m-para/u2gncell_niratoverlap.html

../RNCParaHtml/mbsc/m-para/ucelldynshutdown_dynshutdowntype.html

../RNCParaHtml/mbsc/m-para/ucelldynshutdown_dynshutdowntype.html

RAN15.0




4-148

Change Type


New IRATHighPriSwitch

SET GCELLSOFT Whether the priorities of data services performed by multi-mode UEs are considered in the Multi-RAT Carrier Joint Intelligent Shutdown feature. When this switch is turned on, the priorities of data services performed by multi-mode UEs are considered to meet the differentiated service requirements.

New IRATShutdownSwitch

SET GCELLSOFT Whether to enable the Multi-RAT Carrier Joint Intelligent Shutdown feature


This feature does not add any new performance counters. The performance of this feature is monitored by existing counters of cell-level cell shutdown duration, cell shutdown times, and cell restart times.

Fault Management

No impact.



When multiple inter-frequency same-coverage UMTS cells cover the same area as GSM cells, the inter-frequency same-coverage UMTS cells of the current UMTS cell must have either of the following features enabled:

WRFD-020117 Multi-Carrier Switch off Based on Traffic Load

WRFD-020122 Multi-Carrier Switch off Based on QoS

If one UMTS cell covers the same area as GSM cells, the Multi-RAT Carrier Joint Intelligent Shutdown feature does not depend on the preceding features.


The Multi-RAT Carrier Joint Intelligent Shutdown feature cannot be used together with the feature MRFD-211802 GSM and UMTS Dynamic Spectrum Sharing.

Impacted Features

Operators are advised to enable this feature together with the following feature and function to achieve superior performance:

WRFD-031000 Intelligently Out of Service

Preferential Allocation of Channels on the BCCH TRX

RAN15.0




4-149

This feature may impact the following feature:

GBFD-111602 TRX Power Amplifier Intelligent Shutdown

4.38 WRFD-010612 HSUPA Introduction Package (Enhanced/Optional)

This feature is enhanced due to the enhancement of the sub-feature WRFD-01061209 HSUPA HARQ and Fast UL Scheduling in NodeB. For details, see section 4.39 “WRFD-01061209 HSUPA HARQ and Fast UL Scheduling in NodeB (Enhanced/Optional).”

4.39 WRFD-01061209 HSUPA HARQ and Fast UL Scheduling in NodeB (Enhanced/Optional)

The HSUPA Scheduling Based on UE Location function is introduced in RAN15.0 and this function is the enhancement of the WRFD-01061209 HSUPA HARQ and Fast UL Scheduling in NodeB feature. This section describes the impact brought by this function.


This function decreases the SPI weight of HSUPA BE UEs in soft handover areas of a cell to reduce the interference from these UEs on other UEs in the same cell and on UEs in neighboring cells and to ultimately expand the uplink cell capacity.


Impact on System Capacity

In the cell where this function is enabled, this function proportionally lowers the SPI weight of an HSUPA BE UE when the UE is performing a soft handover and the cells that have a radio link connected to the UE support this function. When the uplink load of the cell is close to the value for MaxTargetUlLoadFactor, this function decreases the data rate of the UE.

By decreasing the data rate, this function:

Enables the cell to admit more UEs, which increases the number of uplink UEs for the cell

Increases the uplink throughput for the cell if HSUPA UEs in the cell center are engaged in uploading data

This function helps increase the uplink cell throughput by around 2% to 7% for cells where more than 30% UEs perform soft handovers, all the uplink services are carried over HSUPA channels and are using the FTP, and the data rate of UEs performing soft handovers is not lower than the GBR. If all the uplink services are traffic bursts, this function increases the uplink cell throughput by less than 2%.

The amount of capacity gains is positively correlated with the number and data rate of HSUPA BE UEs in soft handover areas.

Impact on Network Performance

Delay

This function prolongs the delay for HSUPA BE UEs in soft handover areas of a cell because this function decreases their data rate when the uplink cell load exceeds the value for MaxTargetUlLoadFactor. This function can shorten the delay for UEs not performing soft handovers because this function reduces uplink interference.

Data rate

../RNCParaHtml/mbsc/m-para/ucellhsupa_maxtargetulloadfactor.html

../RNCParaHtml/mbsc/m-para/ucellhsupa_maxtargetulloadfactor.html

RAN15.0




4-150

− In the cell center, HSUPA BE UEs of different priorities still have different data rates when CE and Iub-interface bandwidth resources are sufficient.

− The ratio of the data rate of HSUPA BE UEs of a certain priority in soft handover areas to the data rate of HSUPA BE UEs of the same priority in the cell center correlates strongly with their SPI weight adjustment factors.

− The data rate of high-priority UEs in soft handover areas may be lower than the data rate of low-priority UEs in the cell center. However, you can configure related parameters to guarantee the data rate of high-priority UEs in soft handover areas.

Iub-interface load

Adjusting the SPI weight of HSUPA BE UEs in soft handover areas increases the Iub-interface load. Because such adjustments are not frequent, the Iub-interface load will not greatly increase.

4.39.3 Impact on NEs

The function is implemented on the RNC and NodeB.


The BTS3812A, BTS3812AE, and BTS3812E must be configured with the EBBI, EBOI, EULP, or EULPd board. Downlink services must be established on the EBBI, EBOI, EDLP, or EDLPd board.

The DBS3800 must be configured with the EBBC or EBBCd board. Downlink services must be established on the EBBC or EBBCd board.

3900 series base stations must be configured with the WBBPb, WBBPd, or WBBPf board. Downlink services must be established on the WBBPb, WBBPd, or WBBPf board.

4.39.5 Impact on Inter-NE Interfaces

This function does not affect the Uu, Iub, Iur, or Iu interface.


License

This function is not under the license control and therefore no new license is introduced.


Table 4-54 lists the RNC-level switch and RNC-level parameters that are added to control and configure the HSUPA Scheduling Based on UE Location function.

Table 4-54 RNC-level switch and RNC-level parameters that are added to control and configure this function

Change Type

Parameter ID

MML Command

Setting Notes

New DftSpiWtFactorForHsupaSho

SET UFRC This parameter specifies the SPI weight adjustment factor for HSUPA BE UEs performing soft handovers when the Differentiated Service Based on SPI Weight feature is deactivated. The default value of this parameter is 70%.

../RNCParaHtml/mbsc/m-para/ufrc_dftspiwtfactorforhsupasho.html



RAN15.0




4-151

Change Type

Parameter ID

MML Command

Setting Notes

New SpiWtFactorForHsupaSho

SET USPIWEIGHT

This parameter specifies the SPI weight adjustment factor for HSUPA BE UEs performing soft handovers when the Differentiated Service Based on SPI Weight feature is activated and MOCN is not applied. The default value of this parameter is 70%.

New SpiWtFactorForHsupaSho

SET UOPERSPIWEIGHT

This parameter specifies the SPI weight adjustment factor for HSUPA BE UEs that are performing soft handovers and register services provided by different operators when the Differentiated Service Based on SPI Weight feature is activated and MOCN is applied. The default value of this parameter is 70%.

New PerfEnhanceSwitch

SET UCORRMPARA

This switch controls the HSUPA Scheduling Based on UE Location function.


No new counters are added.

Fault Management

None


During off-peak hours, power resources are sufficient and this function does not decrease the data rate of UEs performing soft handovers. In this case, this function does not affect other HSUPA-related features.

During peak hours, power resources are likely to be insufficient. Under certain conditions, this function decreases the data rate of HSUPA BE UEs performing soft handovers. The data rate fluctuation of these UEs will trigger other features and related adjustments. This increases the number of reconfiguration messages. Call drops will occur if these UEs do not respond to these reconfiguration messages in time. The following are features that are likely to be triggered by the data rate fluctuation:

WRFD-010690 TTI Switch for BE Services Based on Coverage

WRFD-01061208 HSUPA DCCC

WRFD-010712 Adaptive Configuration of Traffic Channel Power


Service Awareness-based QoS Management

The preceding features have their own high data rate threshold and low data rate threshold. If any threshold is exceeded, these features will be triggered.

../RNCParaHtml/mbsc/m-para/uspiweight_spiwtfactorforhsupasho.html






../RNCParaHtml/mbsc/m-para/ucorrmpara_perfenhanceswitch.html



RAN15.0




4-152

TTI Switch for BE Services Based on Coverage

One triggering condition of the TTI Switch for BE Services Based on Coverage feature is the data rate of HSUPA UEs. When the HSUPA HARQ and Fast UL Scheduling in Node B feature and the TTI Switch for BE Services Based on Coverage feature are activated, the data rate of HSUPA BE UEs changes if these UEs enter or exit the soft handover state and uplink cell resources are insufficient. This results in TTI switching and the increase in the number of radio bear (RB) reconfiguration messages. Call drops occur if these UEs do not respond to these messages in time.

HSUPA DCCC

When the HSUPA HARQ and Fast UL Scheduling in Node B feature and the HSUPA DCCC feature are activated, data rate increases of HSUPA UEs in non-soft handover areas and data rate decreases of these UEs in soft-handover areas will frequently trigger the HSUPA DCCC feature and consequently increase the number of reconfiguration messages.

Adaptive Configuration of Traffic Channel Power offset for HSUPA

When the HSUPA HARQ and Fast UL Scheduling in Node B feature and the Adaptive Configuration of Traffic Channel Power offset for HSUPA feature are activated, the number of adaptive power offset adjustments on HSUPA traffic channels may increase as well as the number of RB reconfiguration messages.


This function does not adjust the SPI weights of platinum users.

Service Awareness-based QoS Management

The HSUPA Scheduling Based on UE Location function is to expand the uplink cell capacity but the Service Awareness-based QoS Management function is to improve UE experience for specific services. If the functions are both enabled, the mutual impact between them will cause them to be unable to provide expected gains.

4.40 WRFD-010696 DC-HSDPA (Enhanced/Optional)


The DC-HSDPA feature enhancement in RAN15.0 enables UEs to use two non-adjacent frequencies at the same frequency band for HSDPA transmission.


System Capacity

No impact.

Network Performance

No impact.

4.40.3 NEs

This feature is implemented on the RNC and NodeB.

UEs must support both DC-HSDPA and non-adjacent frequencies.

RAN15.0




4-153

4.40.4 Hardware

No impact.


The "Non-contiguous multi-cell" IE is added to the "UE radio access capability extension" IE to specify whether the UE supports non-adjacent frequencies and indicate the UE's capability to support non-adjacent frequencies.


License

This feature operates under a NodeB-level license, which is the same as that used in RAN12.0.


No impact.


No impact.

Fault Management

No impact.


No impact.

4.41 WRFD-010703 HSPA+Downlink 84Mbit/s per User (Enhanced/Optional)


The HSPA+ Downlink 84 Mbit/s per User feature is enhanced in RAN15.0 by allowing 4C-HSDPA UEs to have a peak downlink rate of 84 Mbit/s.


System Capacity

No impact.

Network Performance

No impact.

4.41.3 NEs

No impact.

RAN15.0




4-154

4.41.4 Hardware

No impact.


The "Non-contiguous multi-cell" IE is added to the "UE radio access capability extension" IE to specify whether the UE supports non-adjacent carriers and indicate the UE's capability to support non-adjacent carriers.


License

This feature operates under a NodeB-level license, which is the same as that used in RAN13.0.


No impact.


No impact.

Fault Management

No impact.


No impact.

4.42 WRFD-010712 Adaptive Configuration of Traffic Channel Power offset for HSUPA (Enhanced/Optional)


This feature adaptively configures the HARQ power offset for 2 ms TTI HSUPA UEs based on the uplink data rate of UEs and the uplink network load. For 2 ms TTI UEs in the low-rate little retransmission state, a larger value of the HARQ power offset can reduce the DPCCH transmit power. For 2 ms TTI UEs in the high-rate little retransmission state, a smaller value of the HARQ power offset can ensure normal uplink data transmission.


System Capacity

This feature adaptively configures HARQ power offsets for 2 ms TTI HSUPA UEs. It configures lower DPCCH transmit power for UEs in the low-rate small retransmission state, which increases HSUPA capacity when the number of HSUPA UEs is large and the Uu-interface transmission rate is low. This capacity improvement is indicated by the increase in average HSUPA throughput in a cell, the increase in the number of UEs that can transmit data simultaneously in the uplink, or the RTWP reduction.

Network Performance

None

RAN15.0




4-155

4.42.3 NEs


4.42.4 Hardware

No impact.


No impact.


License

Table 4-55 provides license information for Adaptive Configuration of Traffic Channel Power offset for HSUPA.

Table 4-55 License information for Adaptive Configuration of Traffic Channel Power offset for HSUPA


WRFD-010712



RNC Mbit/s (HSUPA throughput)


No impact.


No impact.

Fault Management

No impact.



This feature requires the WRFD-010612 HSUPA Introduction Package feature.


None

Impacted Features

None

RAN15.0




4-156

4.43 WRFD-020119 Multi-Carrier Switch off Based on Power Backup (Enhanced/Optional)

If base stations are configured with storage batteries, the storage batteries provide backup power for the base stations in the case of a mains power failure. However, storage batteries provide limited backup power. To prolong the operating duration of base stations when powered by storage batteries, some carriers can be shut down or the transmit power of the carriers can be reduced. The IDs and names of the corresponding features for GSM, UMTS, and LTE-FDD are as follows:

GBFD-111605 Active Backup Power Control

WRFD-020119 Multi-Carrier Switch off Based on Power Backup

LOFD-001040 Low Power Consumption Mode

In versions earlier than SRAN8.0, this feature is supported only when base stations are configured with Huawei power cabinets (for example, APM30, EPS4890, or ETP) in a GSM network and an LTE-FDD network.

In SRAN8.0, the preceding feature is enhanced. That is, this feature can be used even if the base stations are configured with power cabinets from other vendors in a GSM network and an LTE-FDD network. Therefore, this feature can apply to more scenarios.


System Capacity

No impact.

Network Performance

No impact.

4.43.2 NEs

This feature is implemented on the GBSC, GBTS, eGBTS, NodeB, eNodeB, M2000, and CME.

Power subsystems from other vendors must be capable of generating the dry contact alarm if they are used to provide backup power for base stations.

4.43.3 Hardware

When base stations are powered by power systems from other vendors, the base stations must provide one vacant Boolean input port for reporting dry contact alarms.


No impact.


License

The existing license for this feature is still applicable. The enhancement of this feature has no impact on the license.

A carrier-level license control item has been added to the eGBTS for this feature.

RAN15.0




4-157




No MML command or parameter has been added on the GBSC, GBTS, and RNC sides.

The following MML command has been introduced on the eGBTS, NodeB, and eNodeB sides to accommodate this feature, as described in Table 4-56.

Table 4-56 New MML command on the eGBTS, NodeB, and eNodeB sides

Change Type


New MAINSALARMBIND

MOD NMSABIND(eGBTS/NodeB/eNodeB)

This new command is used to modify the binding of the input port to the dry contact alarm.

The following parameters have been introduced on the eGBTS and eNodeB sides to accommodate this feature, as described in Table 4-57.

Table 4-57 New parameters on the eGBTS and eNodeB sides

Change Type


New MAINSALARMBIND

ISDSWITCH MOD NMSABIND(eGBTS/eNodeB)

This new parameter specifies the dry contact alarm flag.

New MAINSALARMBIND

NMSACN MOD NMSABIND(eGBTS/eNodeB)

This new parameter specifies Almport Cabinet No. of the dry contact alarm.

New MAINSALARMBIND

NMSASRN MOD NMSABIND(eGBTS/eNodeB)

This new parameter specifies Almport Subrack No. of the dry contact alarm.

New MAINSALARMBIND

NMSASN MOD NMSABIND(eGBTS/eNodeB)

This new parameter specifies Almport Slot No. of the dry contact alarm.

RAN15.0




4-158

Change Type


New MAINSALARMBIND

NMSAPN MOD NMSABIND(eGBTS/eNodeB)

This new parameter specifies Almport Port No. of the dry contact alarm.

New NODEBPOWEROUTAGE

bakPwrSavPolicy

SET NODEBPOWEROUTAGE(NodeB)

This new parameter specifies the standby power saving policy when storage batteries provide backup power in the case of a mains power failure. When different policies are used, level 1 shutdown delay and level 2 shutdown delay are automatically configured as follows: If this parameter is set to POLICY3, level 1 shutdown delay is 1800s and level 2 shutdown is 36000s. If this parameter is set to POLICY2, level 1 shutdown delay is 1800s and level 2 shutdown is 7200s. If this parameter is set to POLICY1, level 1 shutdown delay and level 2 shutdown delay are 60s. If this parameter is set to CUSTOMIZED, level 1 shutdown delay and level 2 shutdown delay are customized.

New CELLLOWPOWER

bakPwrSavPolicy

MOD CELLLOWPOW

This new parameter specifies the

RAN15.0




4-159

Change Type


ER(eNodeB) backup power saving policy of the eNodeB when storage batteries provide backup power in the case of a mains power failure.

The degradation duration in each policy is automatically configured as follows:

If this parameter is set to POLICY3, the duration of service power degradation and that of reference signal power degradation are both 120 minutes, and the maximum duration of RF channel intelligent shutdown is 1440 minutes.

If this parameter is set to POLICY2, the duration of service power degradation, reference signal power degradation, and RF channel intelligent shutdown is all 120 minutes.

If this parameter is set to POLICY1, the duration of service power degradation, that of reference signal power degradation, and that of RF channel intelligent shutdown are all 0

RAN15.0




4-160

Change Type


minutes.

If this parameter is set to POLICY1, POLICY2 or POLICY3, the ratio of available service power to total service power is 50%, the adjustment offset for reference signal power is -1 dB, and the wait time for entering the low power consumption mode is 5 minutes.

If this parameter is set to CUSTOMIZED, you can customize the duration of power degradation, the ratio of available service power to total service power, the adjustment offset for reference signal power, and the wait time for entering the low power consumption mode.


No impact.

Fault Management

No impact.


No impact.

RAN15.0




4-161

4.44 WRFD-020129 PS Service Redirection from UMTS to LTE (Enhanced/Optional)


If a UMTS/LTE dual-mode UE establishes services in the UMTS network, this feature allows the RNC to redirect the UE to the LTE network when both UMTS and LTE coverage is available and the UE establishes only PS services.

In a UMTS/LTE multi-layer network where PS handover from UMTS to LTE is not supported by UE or network, this feature redirects the UEs that process only PS services from the UMTS network to the LTE network, improving user experience for PS service users.

In RAN15.0, the following functions are added:

Triggering redirection when the best cell changes

Support for blind redirection

Added frequency information in the SIB19 message for redirection or blind redirection.


System Capacity

No impact.

Network Performance

When UEs or the network does not support PS handovers from UMTS to LTE, this feature redirects the UMTS/LTE dual-mode UEs to LTE. The redirection brings about the following benefits:

Improved user experience

Reduced loads on the UMTS network

Reduced call drop rate

However, the compressed mode must be started during the LTE measurement, which increases the call drop rate. Multiple UEs initiating LTE measurements at the same time also results in an increased call drop rate.

Compared with PS handover, PS redirection shortens the duration of service interruptions.


4.44.3 NEs


The CN must support UMTS-to-LTE interoperation. The UE must support UMTS and LTE and support 3GPP Release 8 or later.

4.44.4 Hardware

No impact.

RAN15.0




4-162


No impact.


License





Change Type

MO Parameter ID

MML Command

Description

New UCELLU2LTEHONCOV

BestCellTrigLTEMeasSwitch

ADD UCELLU2LTEHONCOV/SET UU2LTEHONCOV

This new parameter specifies whether the RNC triggers service-based LTE cell measurements when the best cell that a UE camps on changes.

When the switch is turned on and the best cell changes, the RNC enables the compressed mode to measure the neighboring LTE cell. If the quality of the neighboring LTE cell meets the requirements, the UE performs a handover or redirection.

When the switch is turned off and the best cell that the UE camps on changes, the RNC does not trigger service-based LTE cell measurements.

RAN15.0




4-163

Change Type

MO Parameter ID

MML Command

Description

New UCELLHOCOMM

U2LBlindRedirSwitch

ADD UCELLHOCOMM

This new parameter specifies whether the RNC supports a UMTS-to-LTE blind redirection.

When the switch is turned on and the UE does not support LTE cell measurements, the RNC directly performs a UMTS-to-LTE redirection, without measuring the LTE cell. The EARFCN for the redirection is configured for the neighboring LTE cell or the LTE EARFCN configured in SIB19.

When the switch is turned off, the RNC measures the LTE cell and then accordingly selects the EARFCN for a cell to perform a UMTS-to-LTE redirection. If the UE does not support LTE cell measurements, the RNC cannot perform a UMTS-to-LTE redirection.

New ULTENCELL BlindFlag ADD ULTENCELL

This new parameter specifies the ID of the neighboring LTE cell for blind redirections. When the UE does not support measurements in connected mode and performs a blind redirection based on the frequency of a blind neighboring cell, the frequency of the blind neighboring cell serves as the frequency indicated by this parameter.

RAN15.0




4-164

Change Type

MO Parameter ID

MML Command

Description


HO_U2L_REDIR_BASED_ABSOLUTE_FREQ_SWITCH


During a redirection or blind redirection procedure:

When this switch is turned on, the UE performs the redirection or blind redirection based on the frequency in the system information block (SIB) 19 carried in the RRC Connection Release message.

When this switch is turned off, the UE performs the redirection or blind redirection based on the frequency for the neighboring cell or blind neighboring cell carried in the RRC Connection Release message.


The following counter has been introduced on the RNC side to accommodate this feature, as described in Table 4-59. No counter has been introduced on the NodeB side.

Table 4-59 New RNC counter

Change Type


Description

New VS.U2LTEHO.RRCRelease.Sevice.Blind

U2LTE.HO.CELL

Number of Serviced-based U2L Blind Redirections Through the RRC Connection Release Message for Cell

Fault Management

No impact.


No impact.

RAN15.0




4-165

4.45 WRFD-140218 Service-Based PS Handover from UMTS to LTE (Enhanced/Optional)


Summary

In RAN15.0, the UMTS-to-LTE PS handover can be triggered when the best cell changes.

This feature allows the RNC to hand over a UE and its PS service to the LTE network in either of the following scenarios:

The UE in the UMTS and LTE overlapping coverage area originates a PS service in the UMTS network.

For a UE in the UMTS and LTE overlapping coverage area that is handed over from the LTE network to the UMTS network due to a CSFB, after the UE terminates the CS voice service in the UMTS network, the UE still has ongoing PS services.

Benefits

The benefits of this feature are as follows:

Improved user experience for PS services

Reduced service interruption time compared with redirection

Increased LTE network utilization


System Capacity

No impact.

Network Performance

With this feature, UMTS/LTE dual-mode UEs are handed over to LTE. This brings about the following benefits:

Improved user experience

Reduced loads on the UMTS network

Reduced call drop rate

However, the compressed mode must be started during the LTE measurement, which increases the call drop rate. Multiple UEs initiating LTE measurements at the same time also results in an increased call drop rate.


4.45.3 NEs


This feature requires support from the UE. The UE must support 3GPP Release 8 or later, UMTS-to-LTE PS handovers, and LTE network measurements in connected mode.

RAN15.0




4-166



4.45.4 Hardware

No impact.


No impact.


License



The following parameter has been introduced on the RNC side to accommodate this feature, as described in Table 4-60. No parameter has been introduced on the NodeB side.

Table 4-60 New RNC parameter

Change Type

MO Parameter ID

MML Command

Description

New UCELLU2LTEHONCOV

BestCellTri

gLTEMeasS

witch

ADD UCELLU2LTEHONCOV/SET UU2LTEHONCOV

This new parameter specifies whether the RNC triggers service-based LTE cell handovers or redirections when the best cell that a UE camps on changes. The switch can be a cell-level or RNC-level switch.

When the switch is turned on, the RNC triggers service-based LTE cell handovers or redirections after the best cell changes. If the quality of the neighboring LTE cell meets the requirements, the UE performs a handover or redirection. When the switch is turned off and the best cell that the UE camps on changes, the RNC does not trigger service-based LTE cell measurements.

../RNCParaHtml/mbsc/m-para/ucellu2ltehoncov_bestcelltrigltemeasswitch.html



RAN15.0




4-167


No impact.

Fault Management

No impact.


No impact.

4.46 WRFD-140219 Micro NodeB Self-Planning (Enhanced/Optional)

4.46.1 Introduction

The feature is enhanced in RAN15.0.

In UMTS RAN14.0, this feature works only in single-carrier scenarios. That is, the UARFCN, scrambling code,

neighbor relationships with intra-frequency neighboring cells, inter-frequency neighboring cells, and neighboring

GSM cells, LAC, RAC, and SAC can be self-planned when only one carrier is configured on a micro NodeB. In

UMTS RAN15.0, this feature is enhanced and the preceding site parameters can be also self-planned when two

carriers are configured on a micro NodeB. Besides, the self-planning of the neighbor relationship with

neighboring LTE cells and URAs is supported in both single- and dual-carrier scenarios.


System Capacity

None.

Network Performance

If several micro NodeBs do not have shared neighboring cells, self-planned scrambling codes may cause co-channel interference, leading to mutual interference among the cells under the micro NodeB. As a result, counters, such as the call drop rate, connection success rate, and throughput may be affected.

If a micro NodeB fails to search out neighboring macro cells, the micro NodeB uses default LAC/RAC/URA. However, if the micro cell and neighboring cells do not share the default LAC/RAC/URA, additional LAU procedures are required, which increases network load.

4.46.3 NEs

This feature is implemented on the BTS3902E, BTS3803E, and M2000 and requires support from the RNC,

GBSC, and eNodeB.

4.46.4 Hardware

This feature has the following requirements for the BTS3902E and BTS3803E:

The micro NodeB must be configured with an SON receiver.

The SON receiver must be configured with an antenna:

RAN15.0




4-168

- If the micro NodeB is configured with a built-in antenna, the SON receiver shares an antenna with the micro NodeB. An individual antenna for the SON receiver is not required.

- If the micro NodeB is configured with an external antenna, an individual antenna for the SON receiver is required.


The scanning results of self-planning and the automatic configuration data are delivered through the OM

channel between the M2000 and Micro NodeB.

The automatic configuration data is delivered through the OM channel between the M2000 and RNC.

The automatic configuration data is delivered through the OM channel between the M2000 and GBSC.

The automatic configuration data is delivered through the OM channel between the M2000 and eNodeB.


License

This feature is optional and the license file for this feature is required.


None.


None.

Fault Management

None.


None.

4.47 MRFD-211501/MRFD-221501/MRFD-231501 IP-Based Multi-mode Co-Transmission on BS side (Optional/Enhanced)


This multi-mode feature is new in SRAN8.0. It includes the following on the GBSS15.0, RAN15.0, and eRAN6.0:

MRFD-211501 IP-Based Multi-mode Co-Transmission on BS side (GBTS)

MRFD-221501 IP-Based Multi-mode Co-Transmission on BS side (NodeB)

MRFD-231501 IP-Based Multi-mode Co-Transmission on BS side (eNodeB)

MRFD-211501/MRFD-221501/MRFD-231501 IP-Based Multi-mode Co-Transmission on BS side is a feature in which multiple modes of a GU, GL, UL, or GUL multimode base station share transmission ports and the transport network.

RAN15.0




4-169

This feature provides the following benefits:

Sharing transmission ports reduces transmission bearer links.

Sharing the transport network simplifies transmission configuration and maintenance.

A smooth evolution from GSM to UMTS or LTE can be achieved with less transport network adjustments.

In summary, this feature reduces the capital expenditure (CAPEX) and operating expense (OPEX) and simplifies transport network maintenance.

This feature is enhanced in SRAN 8.0 and supports co-transmission in a co-MPT multimode base station.

Different modes of a co-MPT multimode base station share one UMPT board and the co-transmission port (FE/GE or E1/T1) on the board. Only co-MPT GU multimode base stations support sharing an E1/T1 port.

A co-MPT multimode base station supports the following UTRP boards: UTRP2, UTRP3, UTRP4, and UTRP9 (not the UTRPb4). These UTRPs carry only UMTS services.


System Capacity

No impact.

Network Performance

No impact.

4.47.3 NEs

This feature is implemented on the GBTS, eGBTS, NodeB, eNodeB, and M2000.

4.47.4 Hardware

To implement co-transmission through backplane interconnection, the UMPT, LMPT, or UTRPc must be configured.


No impact.


License

The existing license on the multimode base station side for this feature is still applicable. The enhancement of this feature has no impact on the license.

The existing license on the multimode base station controller side for this feature is still applicable. The enhancement of this feature has no impact on the license.


No impact.

RAN15.0




4-170


No impact.

Fault Management

No impact.



GBSS features

GBFD-118601 Abis over IP

RAN features

WRFD-050402 Transmission Introduction on Iub Interface

WRFD-050302 Fractional ATM Function on Iub Interface

WRFD-050411 Fractional IP Function on Iub Interface

eRAN features

None

4.48 WRFD-150223 4C-HSDPA+MIMO (New/Try)


4C-HSDPA+MIMO was introduced in 3GPP Release 10. 4C-HSDPA+MIMO uses three or four carriers enabled with MIMO+64QAM for the HSDPA transmission of a UE, which increases the UE data rate and system capacity.

A primary common pilot channel (P-CPICH) and a secondary common pilot channel (S-CPICH) must be configured in cells that use 4C-HSDPA+MIMO.

When PS BE services, streaming services, or combined services that include PS BE or streaming services are carried on the HS-DSCH, these services can use 4C-HSDPA+MIMO. In the uplink, the UE can use DCH, HSUPA, or DC-HSUPA. The SRB for the UE is carried over DCH, HSDPA, or HSUPA.

4C-HSDPA+MIMO does not apply to CS services, IMS signaling, PS conversational services, or SRB signaling, because the gains provided by this feature are not noticeable for services that have only a small amount of data to transmit and have low transmission delay requirements.


System Capacity

4C-HSDPA+MIMO increases the cell load in the uplink, consumes more CE resources, and affects the number of multi-carrier HSDPA UEs supported by baseband processing boards.

4C-HSDPA+MIMO slightly increases the cell load in the uplink. The cell load increase is represented by an increase in the uplink RTWP.

The increase in the uplink RTWP varies depending on the number of online 4C-HSDPA+MIMO UEs. 4C-HSDPA+MIMO UEs use the HS-DPCCH to provide feedback in the uplink, and the HS-DPCCH uses the spreading factor SF128. As a result, 4C-HSDPA+MIMO requires more power resources and

RAN15.0




4-171

uplink interference increases. The Dynamic Configuration of HSDPA CQI Feedback Period feature can be enabled to reduce the uplink RTWP.

4C-HSDPA+MIMO UEs require one CE more than SC-HSDPA+MIMO UEs.

A baseband processing board supports more SC-HSDPA+MIMO UEs than 4C-HSDPA+MIMO UEs.

Network Performance

4C-HSDPA+MIMO increases the single-user downlink throughput and deteriorates the uplink cell edge coverage.

Increased single-user downlink throughput

4C-HSDPA+MIMO increases the single-user downlink throughput by about 300% compared with SC-HSDPA+MIMO. The increase in the single-user downlink throughput is noticeable even at the cell edge.

However, the increase in the single-user downlink throughput varies depending on the load of other 4C-HSDPA+MIMO cells in the same sector. For example, when other 4C-HSDPA+MIMO cells in the same sector have heavy loads, the gain provided by 4C-HSDPA+MIMO is small. This is because the NodeB considers the rate fairness among 4C-HSDPA+MIMO and SC-HSDPA+MIMO UEs when the load is heavy and the downlink resources (such as power resources and code resources) are insufficient. In this case, the throughput of 4C-HSDPA+MIMO UEs is not significantly higher than that of SC-HSDPA+MIMO or DC-HSDPA+MIMO UEs.

Deteriorated uplink cell edge coverage

4C-HSDPA+MIMO deteriorates the uplink cell edge coverage because 4C-HSDPA+MIMO UEs need to report the CQI information about all serving cells and therefore require higher uplink power.

4.48.3 NEs


This feature requires support from the UE. The UE must belong to HS-DSCH category 30, 32, or higher.

4.48.4 Hardware


None


Only the 3900 series base stations support this feature. The 3900 series base stations must be configured with the WBBPd or WBBPf board to support 3C-HSDPA and must be configured with the WBBPd or WBBPf board to support 4C-HSDPA+MIMO. If MIMO is deployed in two or more 4C-HSDPA cells, the WBBPf4 board must be configured to support 4C-HSDPA+MIMO. The BTS3902E and BTS3803E do not support 4C-HSDPA+MIMO.

Table 4-61 presents an example of the hardware configuration of a NodeB configured with three sectors.

Table 4-61 Example of the hardware configuration of a NodeB configured with three sectors


3C-HSDPA+MIMO

3900 series WCDMA base station

If MIMO is deployed in one 4C-HSDPA cell, each 3900 series base station must be configured with two WBBPf boards or three WBBPb, WBBPd, or WBBPf boards (in any combination).

4C- 3900 series WCDMA base If MIMO is deployed in one 4C-HSDPA cell, each

RAN15.0




4-172

HSDPA+MIMO

station 3900 series base station must be configured with three WBBPd or WBBPf boards (in any combination).

If MIMO is deployed in two 4C-HSDPA cell, each 3900 series base station must be configured with three WBBPf4 boards.


The impact of 4C-HSDPA+MIMO on Iub and Uu interfaces is the same as that of 4C-HSDPA. For details, see section 4.16.5 "Inter-NE Interfaces."


License

4C-HSDPA+MIMO is a try feature and is not under license control.


The following parameters and switches have been introduced on the RNC side to accommodate this feature.

Table 4-62 New RNC parameters and switches



New parameter

DCMIMOor4CHSDPASwitch

- SET UFRC

New switch CfgSwitch CFG_HSDPA_4C_MIMO_SWITCH


New switch HspaPlusSwitch HSDPA_4C_MIMO ADD/MOD UCELLALGOSWITCH

New switch RetryCapability HSDPA_4C_MIMO SET UFRC

NOTE

The hyphen (-) in Table 4-62 indicates that a parameter, not a switch, has been introduced.

The following parameters have been introduced on the NodeB side to accommodate this feature.

Table 4-63 New NodeB parameters


New HSDPA4CMIMO ADD ULOCELL

New HSDPA4CMIMO MOD ULOCELL






../NodeBParaHtml/comm/para/ULoCell-hsdpa4cMimo.html

../NodeBParaHtml/comm/para/ULoCell-hsdpa4cMimo.html

RAN15.0




4-173


The following counters have been introduced on the RNC side to accommodate this feature. No counters have been introduced on the NodeB side.

Table 4-64 New counters for 4C-HSDPA+MIMO










VS.HSDPA.RAB.3CMIMO.AttEstab

HSDPA.Cell Number of RAB Setup Attempts for Cell When 3C-HSDPA with MIMO Applied

VS.HSDPA.RAB.3CMIMO.SuccEstab

HSDPA.Cell Number of Successful RAB Setups for Cell When 3C-HSDPA with MIMO Applied

VS.HSDPA.RAB.AbnormRel.3CMIMO

HSDPA.Cell Number of Abnormally Released RABs for Cell When 3C-HSDPA with MIMO Applied (RF Exceptions Considered)

VS.HSDPA.RAB.NormRel.3CMIMO

HSDPA.Cell Number of Normally Released RABs for Cell When 3C-HSDPA with MIMO Applied

VS.HSDPA.RAB.4CMIMO.AttEstab

HSDPA.Cell Number of RAB Setup Attempts for Cell Where 4C-HSDPA with MIMO Applied

VS.HSDPA.RAB.4CMIMO.SuccEstab

HSDPA.Cell Number of Successful RAB Setups for Cell When 4C-HSDPA with MIMO Applied

VS.HSDPA.RAB.AbnormRel.4CMIMO

HSDPA.Cell Number of Abnormally Released RABs for Cell When 4C-HSDPA with MIMO Applied (RF Exceptions Considered)

VS.HSDPA.RAB.NormRel.4CMIMO

HSDPA.Cell Number of Normally Released RABs for Cell When 4C-HSDPA with MIMO Applied

Fault Management

The Iub and Uu interface trace functions on the LMT support 4C-HSDPA+MIMO UEs.



WRFD-150207 4C-HSDPA

RAN15.0




4-174

WRFD-010693 DL 64QAM+MIMO

DB-HSDPA+MIMO

If the 4C-HSDPA+MIMO cells in a multi-carrier cell group operate in two different frequency bands, all 4C-HSDPA+MIMO cells must have DB-HSDPA+MIMO enabled.

DC-HSDPA+MIMO

If multiple 4C-HSDPA+MIMO cells in a multi-carrier cell group operate in the same frequency band, all of these cells must have DC-HSDPA+MIMO enabled.


WRFD-010686 CPC-DTX/DRX

WRFD-010687 CPC-HS-SCCH Less Operation

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

WRFD-021308 Extended Cell Coverage up to 200km

Impacted Features

4C-HSDPA+MIMO is affected by the same features that affect 4C-HSDPA. 4C-HSDPA+MIMO affects the same features that 4C-HSDPA affects. For details, see section 4.16.7 "Impact on Other Features."

4.49 WRFD-150224 HSPA+Downlink 168 Mbit/s per User (New/Try)


The HSPA+ Downlink 168 Mbit/s per User feature uses a combination of 4C-HSDPA and 64QAM+MIMO to increase the maximum downlink single-user data rate to 168 Mbit/s.


System Capacity

Only one 4C-HSDPA+MIMO UE can have the maximum downlink single-user data rate of 168 Mbit/s in each sector at one time.

Network Performance

The HSPA+ Downlink 168 Mbit/s per User feature increases the uplink rise over thermal (RoT) of the primary cell.

To reach the maximum downlink single-user data rate of 168 Mbit/s, a UE must have satisfactory channel conditions, consume all transmit power of four 4C-HSDPA+MIMO cells, and consume 15 HS-PDSCH codes in each cell.

The 4C-HSDPA+MIMO UE uses HSUPA 2-ms TTIs in the primary cell, which increases the uplink RoT in the cell.

4.49.3 NEs


This feature requires support from the UE and CN.


RAN15.0




4-175

The CN must support 3GPP Release 7 or later and also support a subscribed rate of 168 Mbit/s.

4.49.4 Hardware


For the BSC6900:

− The BSC6900 must be configured with the DPUe board.

− The BSC6900 interface board must be the GOUa, GOUc, FG2a, or FG2c.

For the BSC6910:

− The BSC6910 must be configured with the EGPUa board.

− The BSC6910 interface board must be the GOUc, FG2c, or EXOUa.


Only the 3900 series base stations support this feature. The 3900 series base stations must be configured with the WBBPf4 and UMPT boards (UMPT can be replaced by WMPT+transmission processing board).

The transmission processing board can be UTRP2, UTRP9, or UTRPc.

The BTS3902E does not support this feature.

For example, a NodeB that is configured with three sectors must be configured with the following boards to support the HSPA+ Downlink 168 Mbit/s per User feature:

− Three WBBPf4 boards

− One UMPT board or one WMPT board+one UTRP2/UTRP9/UTRPc board


No impact.


License

4C-HSDPA+MIMO is a try feature and is not under license control.


No impact.


No impact.

Fault Management

No impact.



WRFD-010703 HSPA+ Downlink 84Mbit/s per User

WRFD-150223 4C-HSDPA+MIMO

WRFD-010614 HSUPA Phase 2

RAN15.0




4-176


None

Impacted Features

None

4.50 WRFD-150227 DB-HSDPA+MIMO (New/Try)


DB-HSDPA+MIMO is a try feature and is available from RAN15.0.

DB-HSDPA+MIMO is first specified by 3GPP Release 10. It is a combination of DB-HSDPA (specified by 3GPP Release 9) and MIMO (specified by 3GPP Release 7). This feature allows a NodeB to use the carriers on two different frequency bands and the MIMO technique so that the carriers can simultaneously transmit HSDPA data to UEs.


This feature improves spectral efficiency to achieve the following benefits:

Increased single-user peak rate

Compared with DB-HSDPA, DB-HSDPA+MIMO uses two antennas to produce a spatial multiplexing gain and maximally doubles the single-user peak rate:

− Without 64QAM: from 28 Mbit/s to 56 Mbit/s

− With 64QAM: from 42 Mbit/s to 84 Mbit/s

Compared with single-carrier MIMO, DB-HSDPA+MIMO uses the resources of two carriers to maximally double the single-user peak rate:

− Without 64QAM: from 28 Mbit/s to 56 Mbit/s

− With 64QAM: from 42 Mbit/s to 84 Mbit/s

Increased cell capacity

Compared with DB-HSDPA, DB-HSDPA+MIMO improves spectral efficiency for carriers on two different frequency bands. According to simulation results, system throughput is increased by about 10%-20%.

Similar to DC-HSDPA and 4C-HSDPA UEs, a DB-HSDPA UE consumes one CE more than a SC-HSDPA UE.

4.50.3 NEs


This feature requires support from the UE.


The UE notifies the RNC that it supports DB-HSDPA+MIMO.

4.50.4 Hardware


None


RAN15.0




4-177

− The DBS3800 must be configured with a BBU3806 to support DB-HSDPA+MIMO. In addition, the BBU3806 must be configured with the EBBC or EBBCd board. The BBU3806C does not support DB-HSDPA+MIMO.

− The 3900 series base stations (excluding the BTS3902E) must be configured with the WBBPb3, WBBPb4, WBBPd, or WBBPf board.

− The BTS3812A, BTS3812E, and BTS3812AE do not support DB-HSDPA+MIMO.

− The BTS3803E does not support DB-HSDPA.


Iub

DB-HSDPA+MIMO does not affect the Iub interface.

Table 4-65 describes the messages and IEs used to carry DB-HSDPA+MIMO information over the Iub interface.

Table 4-65 Messages and IEs used to carry DB-HSDPA+MIMO information over the Iub interface

Message IE Description

AUDIT RESPONSE

RESOURCE STATUS INDICATION

Cell Capability Container

The NodeB uses bit 12 of this IE to report the DB-HSDPA+MIMO capability of a local cell to the RNC.

RADIO LINK SETUP REQUEST

HS-DSCH FDD Secondary Serving Information

The RNC uses this IE to instruct the NodeB to or not to establish DB-HSDPA+MIMO RLs.

Uu

DB-HSDPA+MIMO adds a new IE, "Support for dual cell with MIMO operation in different bands", to the "UE radio access capability" IE in the RRC CONNECTION SETUP COMPLETE and UE CAPABILITY INFORMATION messages.

DB-HSDPA+MIMO adds a new IE "Secondary cell MIMO parameters" to the following messages:

CELL UPDATE CONFIRM




The new IE specifies whether DB-HSDPA+MIMO is enabled. Alternatively, existing IEs "MIMO parameters" and "Downlink secondary cell info FDD", not the new IE, are used to specify whether DB-HSDPA+MIMO is enabled.


License

DB-HSDPA+MIMO is a try feature and is not under license control.


The following parameters have been modified on the RNC side to accommodate this feature.

RAN15.0




4-178

Table 4-66 Modified RNC parameters

Change Type


Modified CfgSwitch SET UCORRMALGOSWITCH

An RNC-level DB-HSDPA+MIMO function switch, CFG_HSDPA_DBMIMO_SWITCH, is added to this parameter.

Modified HspaPlusSwitch ADD/MOD UCELLALGOSWITCH

A cell-level DB-HSDPA+MIMO function switch, DB_HSDPA+MIMO, is added to this parameter.

Modified RetryCapability SET UFRC A new switch, DB_HSDPA+MIMO, is added to this parameter for specifying whether UEs can periodically perform DRD to use DB-HSDPA+MIMO.

The following parameter has been introduced on the NodeB side to accommodate this feature.

Table 4-67 New NodeB parameter

Change Type

Parameter ID


New HSDPADBMIMO

3900 series base stations: ADD/MOD ULOCELL

DBS3800: ADD/MOD LOCELL

This parameter specifies the DB-HSDPA+MIMO capability of a cell.




Change Type


Description

New VS.HSDPA.RAB.DBMIMO.AttEstab

HSDPA.Cell

Number of RAB Setup Attempts for Cell When DB-HSDPA with MIMO Applied

This counter is measured only in the primary cell.

New

VS.HSDPA.RAB.DBMIMO.SuccEstab

HSDPA.Cell

Number of Successful RAB Setups for Cell When DB-HSDPA with MIMO Applied


New

VS.HSDPA.RAB.AbnormRel.DBMIMO

HSDPA.Cell

Number of Abnormal Released RABs for Cell When DB-HSDPA with MIMO Applied (RF Exceptions Considered)





../NodeBParaHtml/comm/para/ULoCell-hsdpaDbMimo.html

../NodeBParaHtml/comm/para/ULoCell-hsdpaDbMimo.html

RAN15.0




4-179

Change Type


Description

New

VS.HSDPA.RAB.NormRel.DBMIMO

HSDPA.Cell

Number of Normally Released RABs for Cell When DB-HSDPA with MIMO Applied


The following counter has been introduced on the NodeB side to accommodate this feature. This counter is also used to monitor the performance of DB-HSDPA.

Table 4-69 New NodeB counter

Change Type


Description

New VS.DataOutput.DBHSDPA.Traffic

HSDPA.LOCELL

MAC-ehs traffic volume of DB-HSDPA/DB-HSDPA+MIMO users

Fault Management

On the RNC side

The trace item Cell User Number of the Cell Performance Monitoring function on the RNC LMT counts the DB-HSDPA/DB-HSDPA+MIMO users in the cell.

On the NodeB side

A new trigger condition is added for ALM-28206 Local Cell Capability Decline: This alarm is reported when a cell that does not support DB-HSDPA/DB-HSDPA+MIMO is enabled with DB-HSDPA/DB-HSDPA+MIMO.



WRFD-150209 DB-HSDPA

WRFD-010684 2×2 MIMO


None

Impacted Features

None

RAN15.0

Network Impact Report 5 Glossary



5-1

5 Glossary

A

AC AP Controller

ARP Allocation/Retention Priority

B

BCCH Broadcast Control Channel

BSC Base Station Controller

C

CME CM Express

CPU Central Processing Unit

CQI Channel Quality Indication

CSFB CS FallBack

D

DB-HSDPA Dual Band HSDPA

DPC Destination Point Code

DRD Directed Retry Decision

DSP Destination Signaling Point

F

FTP File Transfer Protocol

RAN15.0




5-2

G

GBR Guaranteed Bit Rate

GPRS General Packet Radio Service

GPS Global Positioning System

GSM Global System for Mobile communications

GTP-U GPRS Tunneling Protocol-User plane

H

HSDPA High Speed Downlink Packet Access

HS-DPCCH High Speed Downlink Physical Control Channel

I

IMSI International Mobile Subscriber Identity

IP Internet Protocol

K

KPI Key Performance Indication

L

LA Location Area

LDR Load Reshuffling

LMT Local Maintenance Terminal

RAN15.0




5-3

M

MAC Media Access Control

MC-HSDPA Multiple Cell HSDPA

MGW Media Gateway

MIMO Multiple Input Multiple Output

MML Man-machine Language

MO Managed Object

MOCN Multiple Operator Core Network

MSC Mobile Switching Center

N

NBAP NodeB Application Part

NI Network Indicator

NodeB NodeB

P

PARC Platform of Advanced Radio Controller

PDCH Packet Data Channel

PDCP Packet Data Convergence Protocol

PS Packet Switched

Q

RAN15.0




5-4

QoS Quality of Service

R

RA Routing Area

RAB Radio Access Bearer

RB Radio Bearer

RIM RAN Information Management

RL Radio Link

RLC Radio Link Control

RNC Radio Network Controller

S

SCTP Streaming Control Transmission Protocol

SDH Synchronous Digital Hierarchy

SGSN Serving GPRS Support Node

SHO Soft Handover

SIR Signal/Interference Ratio

SPC Source Point Code

SPI Scheduling Priority Indicator

SRVCC Single Radio Voice Call Continuity (SRVCC)

T

TDM Time Division Multiplexing

RAN15.0




5-5

U

UE User Equipment

UMTS Universal Mobile Telecommunications System/Universal Mobile Telecommunication System/Universal Mobile Telecommunication Services

UP User Plane

URA User Registration Area

RAN15.0

Network Impact Report 6 References



6-1

6 References

[1] RAN15.0 Feature List

[2] RAN15.0 Feature Description

[3] SRAN8.0&GBSS15.0&RAN15.0&eRAN6.0 DBS3900 Configuration Principle

[4] RAN15.0 BTS3900C WCDMA Product Description

[5] RAN15.0 BSC6900 Product Description

[6] BSC6900 V9R015 UMTS Release Notes (for a specific patch)

[7] 3900 Series WCDMA NodeB V200R015 Release Notes (for a specific patch)

[8] BSC6900 UMTS Product Documentation

[9] 3900 Series WCDMA NodeB Product Documentation

[10] RAN15.0 Feature Documentation

[11] M2000 V200R013 Network Impact Report

[12] M2000 Product Documentation

RAN15.0 Network Impact Report Draft A(PDF)-EN.pdf

Documents

Transcript of RAN15.0 Network Impact Report Draft A(PDF)-EN.pdf