RAN15 New and Enhnced feature list

RAN15.0 New and Enhanced Feature Description

Issue Draft A

Date 2012-7-5

HUAWEI TECHNOLOGIES CO., LTD.

Issue 0.1 (2012-5-85) Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd.

i

Copyright © Huawei Technologies Co., Ltd. 2012. All rights reserved.

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

written consent of Huawei Technologies Co., Ltd.

Trademarks and Permissions

and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.

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

holders.

Notice

The purchased products, services and features are stipulated by the contract made between Huawei and

the customer. All or part of the products, services and features described in this document may not be

within the purchase scope or the usage scope. Unless otherwise specified in the contract, all statements,

information, and recommendations in this document are provided "AS IS" without warranties, guarantees or

representations of any kind, either express or implied.

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

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

recommendations in this document do not constitute a warranty of any kind, express or implied.

Huawei Technologies Co., Ltd.

Address: Huawei Industrial Base

Bantian, Longgang

Shenzhen 518129

People's Republic of China

Website: http://www.huawei.com

Email: [email protected]

RAN15.0 New and Enhanced Feature Description Contents



ii

Contents

1 Basic Features ................................................................................................................................. 1

1.1 WRFD-150101 System Improvement for RAN15.0 ........................................................................................ 1

1.1 WRFD-141102 RNC User Plane and Control Plane Static Sharing ................................................................. 2

1.2 WRFD-141103 Automatic NodeB and Cell Allocation in the RNC ................................................................ 3

1.3 MRFD-210101 System Redundancy ................................................................................................................ 5

2 Optional Features .......................................................................................................................... 7

2.1 WRFD-150201 Micro Cell Dynamic Rx Sensitivity Control .......................................................................... 7

2.2 WRFD-150204 Platinum User Experience Guarantee ................................................................................... 10

2.3 WRFD-150205 Layered Paging in Idle Mode ............................................................................................... 11

2.4 WRFD-150206 Turbo IC................................................................................................................................ 13

2.5 WRFD-150207 4C-HSDPA ........................................................................................................................... 14

2.6 WRFD-150208 Flexible DC/DB-HSDPA ...................................................................................................... 16

2.7 WRFD-150209 DB-HSDPA .......................................................................................................................... 17

2.8 WRFD-150211 Load Balancing Among RNCs in Pool ................................................................................. 20

2.9 WRFD-150212 Node Redundancy for RNCs in Pool .................................................................................... 21

2.10 WRFD-150213 MOCN Independent Iub Transmission Resource Allocation .............................................. 23

2.11 WRFD-150214 MOCN Independent CE Resource Allocation .................................................................... 25

2.12 WRFD-150215 SRVCC from LTE to UMTS with PS Handover ................................................................ 26

2.13 WRFD-150216 Load Based PS Redirection from UMTS to LTE ............................................................... 28

2.14 WRFD-150217 Load Based PS Handover from UMTS to LTE .................................................................. 29

2.15 WRFD-150218 Camping Strategy Management Based on SPID ................................................................ 31

2.16 WRFD-150219 Coverage Based PS Redirection from UMTS to LTE ........................................................ 32

2.17 WRFD-150220 Coverage Based PS Handover from UMTS to LTE ........................................................... 34

2.18 WRFD-150222 HSUPA Time Division Scheduling ..................................................................................... 35

2.19 WRFD-150228 NodeB Support IPSec Bypass ............................................................................................ 37

2.20 WRFD-150229 Intelligent Wi-Fi Searching and Selection .......................................................................... 39

2.21 WRFD-150231 RIM Based UMTS Target Cell Selection for LTE .............................................................. 40

2.22 WRFD-150232 Path Loss Based Inter-Frequency Direct Retry................................................................... 41

2.23 WRFD-141201 RNC User Plane and Control Plane Dynamic Sharing ....................................................... 43

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

2.25 WRFD-010703 HSPA+ Downlink 84 Mbit/s per User ................................................................................ 46

2.26 WRFD-010699 DC-HSDPA+MIMO ........................................................................................................... 47

RAN15.0 New and Enhanced Feature Description Contents



iii

2.27 WRFD-010696 DC-HSDPA ........................................................................................................................ 49

2.28 WRFD-010701 Uplink Enhanced CELL_FACH ......................................................................................... 51

2.29 WRFD-010713 Traffic-Based Activation and Deactivation of the Supplementary Carrier In Multi-carrier 53

2.30 WRFD-020119 Multi-Carrier Switch off Based on Power Backup ............................................................. 54

2.31 WRFD-050402 IP Transmission Introduction on Iub Interface ................................................................... 56

2.32 WRFD-050409 IP Transmission Introduction on Iu Interface ..................................................................... 60

2.33 WRFD-050410 IP Transmission Introduction on Iur Interface .................................................................... 62

2.34 WRFD-050425 Ethernet OAM .................................................................................................................... 65

2.35 WRFD-140210 NodeB PKI Support ............................................................................................................ 67

2.36 WRFD-020129 Service-Based PS Service Redirection from UMTS to LTE ............................................... 69

2.37 WRFD-140218 Service-Based PS Handover from UMTS to LTE .............................................................. 70

2.38 WRFD-140219 Micro NodeB Self-Planning ............................................................................................... 72

3 Try Features .................................................................................................................................. 74

3.1 WRFD-150223 4C-HSDPA+MIMO .............................................................................................................. 74

3.2 WRFD-150224 HSPA+ Downlink 168 Mbit/s per User ................................................................................ 76

3.3 WRFD-150225 HSUPA Scheduling Based on UE Location .......................................................................... 77

3.4 WRFD-150227 DB-HSDPA+MIMO ............................................................................................................. 78

3.5 WRFD-150230 Load Based DPCH Power Saving ........................................................................................ 80

4 Notes .............................................................................................................................................. 81

RAN15.0 New and Enhanced Feature Description 1 Basic Features



1

1 Basic Features 1.1 WRFD-150101 System Improvement for RAN15.0

Availability

This feature is available from RAN15.0.

Summary

This feature provides the following system improvements for RAN15.0:

� Supports 3GPP Release 10, which was published in March 2012.

� A new base station controller BSC6910 is introduced to provide higher system capacity

and stronger service processing capability.

� Provides the RNC in Pool solution.

� Enhances system maintainability.

Benefits

This feature provides customers with the following benefits:

� Improved user experience and increased system capacity by implementing new features

� The higher system capacity and stronger service processing capability of the BSC6910

can better meet future network capacity requirements. By adopting the new 10 GE

interface boards, the BSC6910 helps simplify networking and reduce operating expense

(OPEX).

� Larger system capacity and stronger processing capability provided by the RNC pool

� Lower operation and maintenance costs due to system maintainability enhancements

� Enhanced network security

Description

The details are as follows:

� Compliance with 3GPP Release 10

RAN15.0 is based on 3GPP Release 10, which introduced a series of new features to the

radio access network (RAN) and the UE. RAN15.0 supports 4C-HSDPA specified by

this release. All relevant interfaces are updated according to 3GPP Release 10.




2

� New base station controller BSC6910 with higher system capacity and stronger service

processing capability

− The BSC6910 supports a maximum of 64,000,000 busy hour call attempts (BHCA)

and 120 Gbit/s throughput. The actual specifications depend on the traffic model.

− The BSC6910 uses the PARCb subrack, which provides higher backplane bandwidth,

stronger power supply, and superior heat dissipation.

− The BSC6910 supports 10 GE interface boards, providing expanded capacity,

improved specifications, and simplified networking. This reduces the OPEX.

� RNC in Pool solution

When a large amount of signaling needs to be processed due to heavy traffic, this

solution enables an operator's multiple RNCs to form a resource pool. All RNCs in the

pool can communicate through a private interface to share hardware processing load or

implement RNC node redundancy.

� Enhanced system maintainability

Enhancement

None

Dependency

None

1.1 WRFD-141102 RNC User Plane and Control Plane Static

Sharing

Availability


Summary

A new service processing board Evolved General Processing Unit REV:a (EGPUa) is

introduced in the BSC6910 to simultaneously process user-plane data and control-plane data.

Users can set the ratio of resources split between processing user-plane data and control-plane

data.

Benefits

This feature reduces the operator's purchasing and maintenance costs because fewer board

types are needed. It can also improve the hardware usage because users can adjust the ratio of

resources split between processing user-plane data and control-plane data based on the traffic

model.

Description

The EGPUa boards in an RNC form two resource pools: the UP pool for user-plane data

processing and the CP pool for control-plane data processing. The operator can adjust the ratio




3

of CPU resources used for the UP pool to those used for the CP pool to based on the traffic

model. This improves the hardware usage.

The services on the CPU resources adjusted will drop from the network.

The RNC can also automatically adjust the ratio of resources split between processing

user-plane data and control-plane data. This belongs to the optional feature WRFD-141201

RNC User Plane and Control Plane Dynamic Sharing.

Enhancement

None

Dependency

Dependency on RNC hardware

Only the BSC6910 supports this feature.

Dependency on NodeB hardware

None

Dependency on UE

None

Dependency on other NEs

None

Dependency on the CN

None

Dependency on other RAN features

None

1.2 WRFD-141103 Automatic NodeB and Cell Allocation in

the RNC

Availability





4

Summary

The BSC6910 automatically allocates the control planes of NodeBs and cells to subsystems of

the EGPUa boards. Users no longer need to specify the subrack No., slot No., or subsystem

No.. In addition, the BSC6910 will adjust the allocation based on the traffic load.

Benefits

The operator's operation and maintenance costs are reduced.

Description

When a user configures NodeBs and cells, the BSC6910 automatically allocates the control

planes of NodeBs and cells to subsystems of the EGPUa boards. Users no longer need to

specify the subrack No., slot No., or subsystem No..

When the traffic load on EGPUa boards is unbalanced, the BSC6910 reallocates the control

planes of the NodeBs and cells.

During the dynamic reallocation of a cell, UEs in the CELL_DCH state in the cell will not

drop from the network. During the reallocation of the NodeB, UEs controlled by the NodeB

experience call drops.

The dynamic reallocation can be enabled or disabled by the operator. The operator can also

specify the time for reallocation of NodeBs. It is recommended to perform the dynamic

reallocation of NodeB during off-peak hours to minimize the impact on services.

Enhancement

None

Dependency




None

Dependency on UE

None


None


None


None




5

1.3 MRFD-210101 System Redundancy

Availability

This feature is available from GBSS6.1 and RAN2.0.

Summary

This feature provides the reliability designs such as the active/standby mode, load sharing,

and redundancy configuration, improving the system reliability.

Benefits

This feature improves the system stability and ensures the network performance.

Description

To ensure the reliable operation of the system, reliability designs such as the active/standby

mode, load sharing, and redundancy configuration are widely used in Huawei GBSS/RAN.

In resource pool mode, the load sharing is performed among processing units in the pool. The

processing unit is not backed up. When one or multiple processing units are faulty, the

ongoing services are disrupted, and the new services requests are allocated to other normal

processing units in the resource pool.

In active/standby mode, the active board processes services while the standby board acts as a

backup of the active one. When the active board is faulty or needs to be replaced, the services

can be switched over to the standby board. In this way, the system can work continuously.

There are two types of switchover. One is automatic switchover. That is, the services are

automatically switched over from the active board to the standby board when the active board

is faulty. The other one is manual switchover. That is, the maintenance engineer performs the

board switchover on the LMT. If the active/standby switchover is allowed, a dedicated

maintenance module instructs the relevant boards to perform the switchover after the

maintenance engineer sends an immediate switchover command to the system.

To perform the active/standby switchover successfully, the following conditions must be met:

� The standby board must be in position and work normally.

� No major or critical alarm is reported.

When the standby board is switched over to the active one, the previously active board will be

reset automatically. If this board restarts normally, it becomes the standby one. In this way, the

boards still work in active/standby mode.

Redundancy configuration consists of the following units: boards, transmission interfaces,

power, and fans. The software version and important data configuration file are backed up to

ensure that the system works normally even if exception occurs in the file or data.

The BSC6900 supports both IP and TDM switching, and both the control plane and the user

plane uses the resource pool design. For the service processing boards, the resource pool is

adopted. That is, load-sharing is performed in the resource pool. For other boards, the backup

mode is adopted. That is, the boards of the same type in two neighboring slots work in

active/standby mode. The resource pool is independently established within the GSM or

UMTS.




6

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 active and standby boards. The service processing boards work

in resource pool mode. The control-plane processes of these boards work in backup mode to

ensure system reliability and improve system resource usage.

Huawei BTS/NodeB supports board-level backup. Two boards of the same type work in

active/standby mode. When the active board is faulty, the standby board becomes active.

For the interface board, the board backup mode is adopted. Some interface boards support the

standard backup modes specified in protocols, such as MSP 1+1 or MSP 1:1.When detecting

that the board is faulty, the system re-establishes the transmission of the ongoing services on

the standby board by adopting an active/standby switchover. When detecting that the active

channel is damaged, the system enables the transmission of the ongoing services to recover on

the standby channel by adopting an active/standby switchover.

Enhancement

Since RAN15.0, the control-plane processes of the service processing boards in the BSC6910

work in backup mode to ensure system reliability and improve system resource usage.

Dependency

Dependency on MBSC hardware

None.

Dependency on MBTS hardware

The BTS3902E cannot support this feature.

Dependency on other features of the GBSS/RAN

None.


None.

RAN15.0 New and Enhanced Feature Description 2 Optional Features



7

2 Optional Features

2.1 WRFD-150201 Micro Cell Dynamic Rx Sensitivity Control

Availability


Summary

This feature applies to the following typical scenario:

� A macro cell and its neighboring micro cell use the same frequency.

� The maximum transmit power of the macro cell is 20 W.

� The maximum transmit power of the micro cell is 5 W or 1 W.

� The difference in the downlink pilot power between the macro cell and micro cell is 6 dB

or 13 dB.

The difference in pilot power causes two problematic areas:

� Soft handover (SHO) area

� Non-SHO area

Non-SHO Area

In the non-SHO area, the best cell for a UE is the macro cell, and the UE is closer to the micro

cell than to the macro cell. The UE causes greater interference to the micro cell than to the

macro cell.

SHO Area

In the SHO area, the best cell for a UE is the macro cell, and the UE is also connected to the

micro cell. In this case, both the macro cell and micro cell perform uplink inner-loop power

control on this UE. Inner-loop power control performed by the micro cell plays the leading

role because the uplink Signal-to-Interference Ratio (SIR) on the dedicated physical control

channel (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. The following figure shows

the two problematic areas.




8

This feature provides the following functions:

� Inter-frequency redirection in the problematic areas

� Inter-frequency handover in the problematic areas

� Macro and micro cells joint desensitization

Benefits

This feature provides the following benefits:

� Decreases the call drop rate.

� Increases the HSDPA or HSUPA throughput for a UE in the problematic areas.

� Reduces strong uplink interference the micro cell suffers from UEs in the macro cell.

Description

When you enable this feature, the system performs the following three steps to solve the

problem:

1. Partially desensitizes the micro cell on the basis of the macro and micro cells joint

desensitization algorithm, increases the background noise, and reduces the receive

sensitivity for the micro cell. These actions prevent the UEs carried on the macro cell's

RACH from blocking the uplink of the micro cell, and they narrow the difference in the

uplink between the macro and micro cells.

2. Redirects or hands over the UEs in the problematic areas to an inter-frequency macro

cell that has no intra-frequency neighboring micro cells. This action is based on the

problematic-area inter-frequency redirection algorithm and the problematic-area

inter-frequency handover algorithm. This avoids call drops or throughout drops caused

by the difference in the uplink between the macro and micro cells. The following figure

shows that UEs in the problematic areas are handed over to another inter-frequency

macro cell.




9

3. If some UEs remain in the problematic areas, the system totally desensitizes the micro

cell based on the macro and micro cells joint desensitization algorithm to increase the

background noise and reduce the receive sensitivity for the micro cell until the uplink

SIR on the DPCCH received in the macro cell is the same as that received in the micro

cell when a UE is at the downlink boundary. This eliminates the difference in the uplink

between the macro and micro cells, reduces the call drop rate in the problematic areas,

and improves the throughput for the UEs in the problematic areas. The following figure

shows that the two problematic areas are eliminated.

Enhancement

None

Dependency


None


Only the 3900 series and 3902E base stations support this feature.




10

Dependency on UEs

None


None


None


� Inter-frequency redirection in the problematic areas depends on the WRFD-020400 DRD

Introduction Package feature.

� Inter-frequency handover in the problematic areas depends on the WRFD-020110 Multi

Frequency Band Networking Management feature.

2.2 WRFD-150204 Platinum User Experience Guarantee

Availability


Summary

This feature improves user experience for platinum users by:

� Allocating a high admission priority to them when network congestion occurs

� Allocating the highest High Speed Packet Access (HSPA) service scheduling priority to

them

� Enhancing voice quality for them when downlink coverage is weak

Benefits

This feature provides the following benefits for platinum users:

� Increased access success rate and HSPA throughput

� Improved voice quality

Description

If network congestion occurs during gatherings, sports events, and festivals, it is difficult for

platinum users (for example, policemen and firefighters) to access the network.

With this feature, the RNC preferentially allows platinum users to access the network during

radio resource control (RRC) connection setup or radio access bearer (RAB) setup. A list of

platinum users is saved on the RNC and the list is configurable.

Circuit switched (CS) services initiated by platinum users have the highest admission priority,

and packet switched (PS) services initiated by common users have the lowest admission

priority. The admission priority of PS services initiated by platinum users and the admission

priority of CS services initiated by common users are configurable.




11

When downlink coverage is weak, this feature improves voice quality for platinum users.

Additionally, this feature enables the RNC to allocate the highest HSPA service scheduling

priority to platinum users, increasing their HSPA throughput.

Enhancement

None

Dependency


None


None

Dependency on UEs

None


None


None


None

2.3 WRFD-150205 Layered Paging in Idle Mode

Availability


Summary

With the increasing penetration rate of smartphones, UE paging is triggered more and more

by applications.

Conventionally, the RNC directly pages a UE in idle mode in the entire location area (LA) or

routing area (RA). This results in a large number of unnecessary Uu-interface paging

messages, which increases PCH congestion.

With this feature, the RNC first pages a UE in idle mode in the last camped-on cell and its

neighboring cells. If no response is received from the UE, the RNC then pages the UE in the

entire LA or RA.




12

Benefits


� Fewer Uu-interface paging messages

� Lower PCH congestion probability

� Eliminates the need to manually divide or split the LA or RA

For example, if there are 1200 cells in an LA or RA and the average number of neighboring

cells configured for each cell is 43, this feature reduces the number of Uu-interface paging

messages by 30% to 70% if the first-layer paging success rate is 90%.

Description

With the increasing penetration rate of smartphones, UE paging is triggered more and more

by applications. However, the RNC must page a UE in idle mode in the entire LA or RA

because the RNC does not know which cell the UE camps on. This results in a large number

of unnecessary Uu-interface paging messages, which increases PCH congestion.

To solve this problem, Huawei introduces the Layered Paging in IDLE Mode feature based on

the mobility characteristics of UEs in idle mode.

With this feature, the RNC first pages a UE in idle mode in the last camped-on cell and its

neighboring cells, which is called first-layer paging. If no response is received from the UE,

the RNC then pages the UE in the entire LA or RA. This process is second-layer paging.

Enhancement

None

Dependency


None


None

Dependency on UEs

None


None


None


None




13

2.4 WRFD-150206 Turbo IC

Availability


Summary

Turbo Interference Cancellation (IC) improves IC efficiency by regenerating decoded signals

from the E-DPDCH. This feature also supports uplink E-DPCCH IC, improving the

signal-to-noise ratio (SNR) for demodulation and increasing system capacity in the uplink.

This feature supports High Speed Uplink Packet Access (HSUPA) UEs using the 2 ms

transmission time interval (TTI) only.

Benefits

This feature improves IC efficiency and increases system capacity in the uplink.

In addition to the uplink IC gains provided by HSUPA, this feature further increases the

uplink system capacity by a maximum of about 10% in the following scenarios:

� A large number of UEs use the 2 ms TTI for continuous data transmission in the serving

cell.

� The throughput of HSUPA 2 ms TTI UEs is high.

Description

UMTS, which is based on the code division multiple access (CDMA) technology, is a

self-interfering system. A UMTS UE experiences interference from other UEs' signals and the

serving cell's background noise. In HSUPA, uplink interference increases along with the

growing data rates and is now the main bottleneck for increasing UMTS uplink capacity.

Turbo IC addresses this issue. This feature improves IC performance by regenerating decoded

signals from the E-DPDCH to obtain more accurate signals. Turbo IC also supports uplink

E-DPCCH IC. That is, this feature reduces the interference from regenerated signals on the

E-DPDCH and E-DPCCH, decreasing the total interference in the serving cell and improving

uplink system capacity.

This feature:

� Supports HUSPA UEs using the 2 ms TTI only

� Consumes no additional channel element (CE) resources

� Supports uplink IC resource groups:

− If all the boards configured in the uplink resource groups support Turbo IC,

inter-board UEs can share centralized IC gains.

− If only a few boards configured in the uplink resource groups support Turbo IC,

inter-board UEs can share only the HSUPA uplink IC gains and intra-board UEs can

share Turbo IC gains only for the boards supporting Turbo IC.

Enhancement

None




14

Dependency


None


The NodeB 3900 series base stations DBS3900, BTS3900, BTS3900A, and BTS3900L must

be configured with the WBBPf board.

If the NodeB needs to support inter-board IC sharing, a minimum of one WBBPd or WBBPf

board must be configured in slot 2 or 3 for an uplink resource group that supports inter-board

IC sharing.

Dependency on UEs

The UEs must be of category 6 or higher.


None


None


� WRFD-01061403 HSUPA 2ms TTI

� WRFD-010691 HSUPA UL Interference Cancellation

2.5 WRFD-150207 4C-HSDPA

Availability


Summary

This feature, four-carrier HSDPA (4C-HSDPA), uses three or four carriers for the High Speed

Downlink Packet Access (HSDPA) transmission of a UE, which increases the UE downlink

throughput.

Benefits

This feature increases the single-user throughput by about 300% compared with HSDPA. The

increase in the single-user throughput is noticeable even at the cell edge.

Description

This feature was first specified by 3GPP Release 10.

This feature allows a UE to set up HSDPA connections with three or four carriers that use

HSDPA and 64QAM. In the downlink, the UE simultaneously receives data from different

carriers, increasing the single-user throughput. In the uplink, the UE uses Dedicated Channel




15

(DCH), High Speed Uplink Packet Access (HSUPA), or Dual-Carrier HSUPA (DC-HSUPA).

The signaling radio bearer (SRB) for the UE is carried over DCH or HSDPA.

The radio access network (RAN) schedules 4C-HSDPA UEs and other HSDPA UEs jointly

for fast resource allocation and load balancing among carriers. The joint scheduling also

increases the UE throughput and the fairness among UEs on different carriers.

When a UE uses four carriers for HSDPA transmission, the four carriers must belong to one

NodeB, cover the same area, and operate at two frequency bands. For details about the

frequency bands that can be used for the HSDPA transmission of a UE, see 3GPP TS 25.104.

When a UE uses three carriers for HSDPA transmission, the three carriers can operate either at

one frequency band or at two frequency bands. Two of the three carriers must be adjacent, as

shown in the following figure:

64QAM 64QAM 64QAM

Band a

N x 5 MHz

This feature applies to PS best effort (BE) services, streaming services, and combined services

that include PS BE or streaming services.

This feature 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.

Enhancement

None

Dependency


None


� The BTS3812E, BTS3812AE, and BTS3812A must be configured with the EBBI,

EDLP+EULP, or EDLP+EULPd boards to support 3C-HSDPA. The three carriers must

operate at the same frequency band.

� The DBS3800 must be configured with the EBBC or EBBCd board to support

3C-HSDPA. The three carriers can operate at different frequency bands.

� The 3900 series base stations (excluding the BTS3902E) 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.

Dependency on UEs

The UEs must belong to HSDPA category 29, 30, 31, or 32.


� WRFD-150208 Flexible DC/DB-HSDPA

� WRFD-010683 Downlink 64 QAM




16

� WRFD-150209 DB-HSDPA

In a cell group that uses 4C-HSDPA, if one cell in the group operates at a different

frequency band from other cells, all cells in the group must support DB-HSDPA. (DB is

short for dual band.)

� WRFD-010696 DC-HSDPA

In a cell group that uses 4C-HSDPA, if multiple cells in the group operate at the same

frequency band, all these cells must support DC-HSDPA.

2.6 WRFD-150208 Flexible DC/DB-HSDPA

Availability


Summary

Flexible DC/DB-HSDPA allows UEs to set up HSDPA connections with any two

inter-frequency same-coverage cells under a NodeB. A pair of these cells is a DC/DB-HSDPA

group. The RAN schedules services in all DC/DB-HSDPA groups, which improves the UE

data rate and system capacity.

Benefits

This feature enables cells to form as many DC/DB-HSDPA groups as possible. The

DC/DB-HSDPA groups dynamically use instantaneous idle frequency resources in a cell,

increasing the UE data rate and system capacity. In the case of three carriers, this feature

increases the UE data rate by about 20% when UEs are processing burst services.

This feature supports smooth evolution to future technologies.

Description

This feature enables cells to form as many overlapping DC/DB-HSDPA groups as possible.

With this feature, some cells may simultaneously belong to multiple DC-HSDPA groups, as

shown in the following figure:

64QAM

64QAM

64QAM

DC-HSDPA

DB-HSDPA

F1 900 MHz

F2 2.1 GHZMIMO

64QAM

64QAMDC-HSDPA

DC-HSDPA

F1

F1 and F2 form a DC-HSDPA group.

F2 and F3 form a DC-HSDPA group.

F1 forms a DB-HSDPA group either

with F2 or with F3. F2 and F3 form a

DC-HSDPA group. Therefore, F2 or F3

belongs to DB-HSDPA and DC-HSDPA

groups simultaneously.

MIMO

64QAM

64QAM

DC-HSDPA

DC-HSDPA

F3

F1

F2

MIMODC-MIMO

4 carrier evolution

F2

F3

F4

F3 2.1 GHz

This feature applies to scenarios where one of the following features or any combination of

them is enabled: DC-HSDPA, DB-HSDPA, or DC-HSDPA+MIMO.




17

This feature has the same requirements for frequencies, bandwidths, and frequency bands as

DC-HSDPA, DB-HSDPA, and DC-HSDPA+MIMO.

This feature supports up to four carriers, which can operate at a maximum of two frequency

bands. The four carriers may include a maximum of two adjacent MIMO carriers.

The MAC-ehs entity on the RAN side jointly schedules DC/DB-HSDPA UEs. Based on the

load of carriers in a DC/DB-HSDPA group, the MAC-ehs entity assigns as many resources of

the lightly loaded carrier as possible to double-carrier UEs. In this way, more resources of the

heavily loaded carrier are assigned to single-carrier UEs. The joint scheduling achieves fast

resource allocation among carriers and prevents a temporary heavy load on a carrier from

affecting UE experience, which increases system resource utilization and system capacity.

Enhancement

None

Dependency


None


� The BTS3812E, BTS3812AE, and BTS3812A must be configured with the EBBI,

EDLP+EULP, or EDLP+EULPd boards to support a maximum of three carriers. The

three carriers must operate at the same frequency band.

� The DBS3800 must be configured with the EBBC or EBBCd board to support a

maximum of three carriers. The three carriers can operate at different frequency bands.


WBBPb, WBBPd, or WBBPf board to support a maximum of four carriers and MIMO.

Dependency on UEs

The UEs must belong to HSDPA category 21 or higher.


� WRFD-150209 DB-HSDPA

In a cell group that uses Flexible DC/DB-HSDPA, if one cell in the group operates at a

different frequency band from other cells, all cells in the group must support

DB-HSDPA.


In a cell group that uses Flexible DC/DB-HSDPA, if multiple cells in the group operate

at the same frequency band, all these cells must support DC-HSDPA.

2.7 WRFD-150209 DB-HSDPA

Availability


It was first specified by 3GPP Release 9.




18

Summary

The Dual-Band HSDPA (DB-HSDPA) feature allows UEs to simultaneously establish

connections in two inter-band same-coverage cells. With this feature, UEs can use the

resources of two cells operating at different frequency bands, which increase the peak

throughput of UEs.

Benefits

This feature provides the following benefits to multi-band networks:

� Increased single-user throughput

This feature doubles single-user throughput for multi-band networks. Specifically, this

feature can provide a maximum single-user throughput of 42 Mbit/s in the cell center

with 64QAM enabled. The increase in single-user throughput reduces transmission delay,

which improves user experience.

� Increased cell throughput

This feature increases cell throughput by 5% to 10% for multi-band networks. The

throughput gain is inversely proportional to the number of UEs that have data to send in

the cell.

Description

This feature is described as follows:

� Primary/secondary carrier configuration in a DB-HSDPA cell group

If a DB-HSDPA cell group consists of two cells, 3GPP Release 9 specifies that a

DB-HSDPA UE must:

− Use the downlink frequency of one cell as the primary carrier and that of the other

cell as the secondary carrier.

− Use the uplink frequency of the cell corresponding to the primary carrier only.

Two cells in a DB-HSDPA cell group are both configured with the P-CPICH, SCH,

P-CCPCH, S-CCPCH, and PRACH. In addition, this feature enables UEs to camp on

and initiate services in the two cells.

� Application scope

This feature 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. This

feature applies to services that may have a large amount of data to transmit, for example,

streaming or best effort (BE) services.

� Selection of DB-HSDPA or Dual-Carrier HSDPA (DC-HSDPA) cell groups

In a network supporting both DB-HSDPA and DC-HSDPA, the two features have the

same configuration priority because:

− A UE supporting DB-HSDPA also supports DC-HSDPA.

− DB-HSDPA and DC-HSDPA provide similar gains.

Therefore, the selection of DB-HSDPA or DC-HSDPA cell groups depends on the traffic

steering or load balancing policy.

� Mobility management

The active set information and measurement results are based on the primary carrier

when a DB-HSDPA UE is being handed over. If the frequencies of the primary carrier




19

before and after the handover are the same, this handover is an intra-frequency handover.

Otherwise, this handover is an inter-frequency handover.

RAN15.0 supports handovers between DB-HSDPA cells, DB-HSDPA and DC-HSDPA

cells, DB-HSDPA and Single-Carrier HSDPA (SC-HSDPA) cells, and DB-HSDPA and

inter-RAT cells to ensure seamless roaming for DB-HSDPA UEs. (RAT is short for radio

access technology.)

� State transition for DB-HSDPA UEs

The state transition procedure for DB-HSDPA UEs is the same as that for

non-DB-HSDPA UEs.

DB-HSDPA cannot be used with space time transmit diversity (STTD).

Enhancement

None

Dependency


None


The requirements for radio frequency (RF) modules are as follows:

The RF modules must support the frequency bands on which DB-HSDPA carrier groups

operate. The mapping between the frequency bands and Huawei RF modules that support

those bands is as follows:

� Band1: RRU3806, RRU3808, RRU3828, WRFU, WRFUd

� Band2: RRU3804, RRU3942

� Band4: RRU3804, RRU3808

� Band5: RRU3908V2, RRU3805

� Band8: RRU3908V2, RRU3929, MRFU V2, MRFUd

� Band11: None

The requirements for baseband modules are as follows:

� The 3900 series base stations must be configured with the WBBPb, WBBPd, or WBBPf

board.

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

� The BBU3806C does not support DB-HSDPA.

� The BTS3812AE and BTS3812E series base stations do not support DB-HSDPA.

Dependency on UEs

The UEs must be of HSDPA category 25 or higher and must support DB-HSDPA.

Dependency on other features

� WRFD-010610 HSDPA Introduction Package

� WRFD-010685 Downlink Enhanced L2

� WRFD-010629 DL 16QAM Modulation




20

2.8 WRFD-150211 Load Balancing Among RNCs in Pool

Availability


Summary

This feature enables load sharing among RNCs in an RNC pool.

Benefits

RNC hardware capacity expansion may not meet signaling capacity requirements because of

the sharp increase in smartphones.

Without this feature, operators must split the RNC, which may require complex network

reconstruction and affect ongoing services.

With this feature, RNCs in an RNC pool can share the control-plane load.

This feature reduces operators' capital expenditure by:

� Reducing the possibility that network KPIs will decrease

� Minimizing the need for RNC hardware capacity expansion

� Balancing traffic among RNCs that have different busy hours

Description

This feature enables RNCs in an RNC pool to share the control-plane load. When the average

CPU load on the control plane of an RNC exceeds a specified threshold, this feature allocates

new services from this RNC to other RNCs in the pool. The RNCs communicate with each

other over the Iur-p interface, which is private.

This feature does not affect other NEs or interfaces.




21

Enhancement

None

Dependency


None


None

Dependency on UEs

None


Parameters must be configured consistently on the CME for the RNCs. When configuring one

RNC on the LMT, you must synchronize the configuration to other RNCs using the CME.


None


None

2.9 WRFD-150212 Node Redundancy for RNCs in Pool

Availability


Summary

This feature enables RNC redundancy in an RNC pool. When an RNC in the pool fails, the

backup RNC takes over the services.

Benefits

Without this feature, if an RNC fails, all NodeBs under that RNC stop providing services.

RNCs may fail because of natural disasters, power outages, and software and hardware faults.

This feature solves this problem and improves service reliability.

Description

This feature enables RNCs in an RNC pool to work as backups for each other. The RNCs

communicate with each other over the Iur-p interface, which is private.




22

The backup mechanism is as follows:

In RNC pool networking, a NodeB that requires a backup RNC is configured with

transmission links to the master and backup RNCs. In normal situations, the master RNC

provides services for the NodeB, and the backup RNC periodically checks the running status

of the master RNC. Once the master RNC fails, the backup RNC takes over the NodeB

services.

A BSC6910 in the pool can work as the master RNC for some NodeBs and as the backup

RNC for other NodeBs simultaneously.

If the master RNC fails and the idle hardware capacity of the backup RNC is less than the hardware

capacity of the master RNC, the quality of services that are taken over by the backup RNC may

deteriorate.

Enhancement

None

Dependency


None


The NodeB must be configured with two Iub interfaces to connect the master and backup

RNCs.

Dependency on UEs

None


Parameters must be configured consistently on the CME for the RNCs.




23


A route from the backup RNC to the master RNC must be configured on the CN.


None

2.10 WRFD-150213 MOCN Independent Iub Transmission Resource Allocation

Availability


Summary

This feature allocates Iub user-plane transmission resources to operators in multi-operator

core network (MOCN) scenarios.

Benefits

This feature prevents one operator from occupying excess Iub user-plane transmission

resources in MOCN scenarios and ensures that operators retain independent Iub user-plane

transmission resources.

Description

Iub transmission resources can be logically divided into user- and control-plane transmission

resources.

In MOCN scenarios, this feature allocates user-plane bandwidth to each operator

independently and enables operators to share control-plane bandwidth and the common

channel bandwidth in a shared cell. The following figure shows the details.




24

To allocate user-plane bandwidth to each operator independently, the RNC is configured with

different logical ports, with each logical port corresponding to one operator; after identifying

the UE's operator, the RNC sends the UE's user-plane data to the corresponding logical port.

This feature applies to the following scenarios:

Scenario 1: Operators share one physical link over the Iub interface.

Scenario 2: Each operator uses a dedicated physical link over the Iub interface.

Enhancement

None

Dependency


This feature does not support BSC6910 IP transmission.


None

Dependency on UEs

None


None




25


None


This feature depends on WRFD-021311 MOCN Introduction Package. This feature cannot be

used with WRFD-02130501 Dedicated Iub Transmission Control or WRFD-140208 Iub

Transmission Resource Pool in RNC.

2.11 WRFD-150214 MOCN Independent CE Resource Allocation

Availability


Summary

This feature allocates a NodeB's uplink and downlink channel element (CE) resources to

operators in MOCN scenarios.

Benefits

This feature prevents one operator from occupying excess CE resources in MOCN scenarios.

This ensures that each operator retains independent CE resources.

Description

This feature provides the following functions:

� The M2000 allocates a NodeB's uplink and downlink CE resources to operators.

When distributing CE licenses, the M2000 allocates a NodeB's uplink and downlink CE

resources by configuring private and common groups. The CE resources in a private

group belong to only one operator. The CE resources in the common group can be shared

by all operators. The following figure shows the details.

� After identifying a UE's operator, the NodeB allocates the CE resources in the operator's

private group to the UE.

After dividing the CE resources into different groups and identifying a UE's operator, the

NodeB allocates the CE resources in this operator's private group to the UE. An operator

can use the CE resources in the common group only after the CE resources in its private




26

group are used up. The CE resources in the common group are used on a first come, first

served basis.

� The RNC relieves CE congestion for each operator separately.

If the available CE resources for an operator are insufficient, the RNC relieves CE

congestion for this operator by reducing the BE service rate for some users or adjusting

the transmission time interval (TTI) for HSUPA users from 2 ms to 10 ms.

Enhancement

None

Dependency


None


Only the 3900 series base stations configured with the WBBPb, WBBPd, or WBBPf board

support this feature.

Dependency on UEs

None


None


None


This feature depends on WRFD-021311 MOCN Introduction Package. This feature cannot be

used with WRFD-021304 RAN Sharing Introduction Package.

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

Availability


Summary

This feature is part of the UMTS/LTE interoperability solution. This feature must be

supported by the UEs, radio access network, and core network.

Benefits

This feature supports single radio voice call continuity (SRVCC) from the RAN side.




27

This feature ensures voice service continuity by allocating VoIP services and PS services (or

default PS bearers) from the LTE network to the UMTS network.

Description

IP Multimedia Subsystem (IMS) is not deployed at the early stage of LTE network

deployment. Therefore, IMS VoIP cannot be used to provide normal voice services and

emergency call services. UEs performing normal voice services and emergency call services

should be handed over to the UMTS network through Circuit Switch FallBack (CSFB) and PS

handover.

After an LTE network is deployed with IMS, the LTE network can support VoIP services.

When a UE performing VoIP services on the LTE network moves out of the LTE coverage, if

there is UMTS coverage, the UE should be handed over to the UMTS network for voice

service continuity. When a UE is performing VoIP services on the LTE network, there must be

at least one PS bearer. The reason is that there must be a default PS bearer for a UE in

connected mode on the LTE network, even if the UE is not performing PS services. When

SRVCC from LTE to UMTS is being performed, the PS bearers will also be handed over to

the UMTS network.

Based on network configuration, the LTE network selects one handover scheme to perform an

LTE-to-UMTS handover. Candidate handover schemes are as follows:

� If UMTS supports VoIP, a PS handover is performed on VoIP. This process is an

inter-RAT PS handover, which does not involve the switchover from the PS domain to

the CS domain.

� CS-only SRVCC, which is called SRVCC from LTE to UMTS without PS handover.

That is, VoIP services are first handed over to the CS domain of the UMTS network

through the switchover of the core network, while PS bearers are transferred to the

UMTS network through a routing area update (RAU) procedure. From the perspective of

UMTS RAN, the process is only an inter-RAT CS handover.

� PS+CS SRVCC, which is called SRVCC from LTE to UMTS with PS handover. That is,

through the switchover of the core network, VoIP and PS services are handed over to the

CS and PS domains of the UMTS network, respectively. From the perspective of UMTS

RAN, the process is an inter-RAT CS+PS handover.

The first two handover schemes have already been supported by Huawei RAN. The last

handover scheme will be implemented by this feature.

Enhancement

None

Dependency


None


None

Dependency on UEs

The UEs must be of 3GPP Release 8 or later and must support SRVCC.




28


The eRAN must support SRVCC.


The CN must support SRVCC.


None

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

Availability


Summary

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 and the serving UMTS cell is in the basic congestion state.

Benefits

This feature reduces the possibility of congestion for a UMTS network by allowing more UEs

in the UMTS network to be redirected to the LTE network. In addition, this feature helps

improve the LTE network resource utilization at the early stage of LTE network deployment.

Description

In the hybrid network coverage of UMTS and LTE, if UEs, the UMTS network, or the LTE

network does not support the UMTS-to-LTE PS handover, operators can use this feature to

redirect UEs to the LTE network where UEs will reestablish their PS services. This feature is

applicable only when the following conditions are met:

� The serving UMTS cell meets the conditions for load reshuffling (LDR).

� The UE to be redirected supports both UMTS and LTE.

� The UE to be redirected processes only PS services, and all the processed PS services

can be established on the LTE network. In the RAB assignment message sent from the

SGSN, there is no indication that the PS services processed by the UE cannot be

established on the LTE network.

Redirection is categorized into blind redirection and measurement-based redirection. If the

UE in connected mode does not support measurements on the neighboring LTE cell and

allows blind redirection to the LTE network, the RRC Connection Release message sent from

the RNC to the UE will include the LTE frequency information, instructing the UE to

implement redirection. If the UE in connected mode supports measurements on the

neighboring LTE cell, the RNC instructs the UE to enter the compressed mode for

measurements and the RRC Connection Release message will include the frequency of the

neighboring LTE cell that was reported by the UE.




29

Enhancement

None

Dependency


None


None

Dependency on UEs

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


None


None


None

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

Availability


Summary

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 and the serving UMTS cell is in the basic congestion state.

Benefits

This feature reduces the possibility of congestion for a UMTS network by allowing more UEs

in the UMTS network to be handed over to the LTE network. Compared with PS redirection,

PS handover shortens the service interruption duration, improving user experience. In

addition, this feature helps improve the LTE network resource utilization at the early stage of

LTE network deployment.

Description

In the hybrid network coverage of UMTS and LTE, if UEs, the UMTS network, and the LTE

network support the UMTS-to-LTE PS handover, operators can use this feature to hand over




30

UEs to the LTE network. This feature is applicable only when the following conditions are

met:

� The serving UMTS cell meets the conditions for LDR.

� The UE to be handed over supports both UMTS and LTE.

� The UE to be handed over processes only PS services, and all the processed PS services

can be established on the LTE network. In the RAB assignment message sent from the

SGSN, there is no indication that the PS services processed by the UE cannot be

established on the LTE network.

� The neighboring LTE cell meets the conditions for the UMTS-to-LTE handover.

The procedure for the UMTS-to-LTE PS handover is briefed as follows:

1. The RNC sends the SGSN a Relocation Required message, which contains the

information about the target LTE cell.

2. The SGSN forwards the Relocation Required message to the MME.

3. After the LTE network is ready for the inter-RAT handover, the MME instructs the

SGSN to send a Relocation Response message to the RNC.

4. Upon receipt of the Relocation Response message from the SGSN, the RNC instructs the

UE to be handed over to the target eNodeB.

Enhancement

None

Dependency


None


None

Dependency on UEs

The UEs must support:

� 3GPP Release 8 or later

� UMTS-to-LTE PS handover

� Measurements on the neighboring LTE cell in connected mode


The eNodeB and MME must support the UMTS-to-LTE PS handover.


The SGSN must support the UMTS-to-LTE PS handover.


None




31

2.15 WRFD-150218 Camping Strategy Management Based on SPID

Availability


Summary

This feature enables operators to allocate Subscriber Profile IDs for RAT/Frequency Priority

(SPIDs) to subscribers so that subscribers camp on different networks based on their cell

reselection priorities. Cell reselection priorities are based on SPIDs and are configured on the

RNC.

Benefits

Operators configure different camping strategies for subscribers with different SPIDs. This

enables each subscriber to use a unique camping strategy in GSM, UMTS, and LTE networks

and avoids ping-pong cell reselections.

Description

The SPID is an index for RAT and frequency priorities. The SPID value depends on the

operator's camping strategy.

The RNC performs mobility management for UEs in idle mode based on the SPID values and

the corresponding RAT/frequency priorities.

When a subscriber is initiating a service or routing area update, the RNC obtains the SPID

from the core network (CN). When a subscriber is being handed over, the RNC obtains the

SPID from the source cell.

After obtaining the SPID, the RNC sends the UE a UTRAN Mobility Information message,

indicating the subscriber's priority. The UE then selects a proper cell to camp on based on the

priority.

When a subscriber has released a connection in the UMTS network, if a subscriber's SPID

indicates that the LTE network takes precedence over the UMTS or GSM network, a fast

return process is triggered to switch the subscriber to the LTE network.

This feature is recommended for LTE subscribers who mostly initiate voice services, because

preferentially camping on the UMTS or GSM network reduces the access delay by 1 to 2

seconds, improving user experience.

Enhancement

None

Dependency


None





32

None

Dependency on UEs

The UEs must support 3GPP Release 8 or later.


None


The SGSN must support SPID delivery and configuration.


WRFD-020126 Mobility Between UMTS and LTE Phase 1

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

Availability


Summary

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.

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 and the LTE signal quality is good, this feature

allows the UE to be redirected to the LTE network to ensure 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.




33

Description � When the UMTS signal quality is poor and the LTE signal quality is good, the RNC

decides whether to initiate measurements on the neighboring LTE cell and whether to

redirect a UE to the LTE network by considering the UE capabilities and the redirection

switch status. This feature is applicable only when the following conditions are met:

− The UE to be redirected supports both UMTS and LTE and supports measurements

on the neighboring LTE cell.

− The UE to be redirected processes only PS services, and all the processed PS services

can be established on the LTE network.

With this feature, the RNC sends the UE an RRC Connection Release message to

instruct the UE to access the LTE network. This message includes the LTE frequency

information. The RNC obtains the LTE frequency information from the system

information or the neighboring LTE cell, depending on the redirection switch status.

� When the UMTS signal quality is very poor, the RNC redirects the UE to the LTE

network through blind redirection without measurements on the neighboring LTE cell.

This feature is applicable only when the following conditions are met:

− The UE to be redirected supports both UMTS and LTE.

− The UE to be redirected processes only PS services, and all the processed PS services


With this feature, the RNC sends the UE an RRC Connection Release message to

instruct the UE to access the LTE network. This message includes the LTE frequency

information. The RNC obtains the LTE frequency information from the system

information or the neighboring LTE cell, depending on the redirection switch status.

Enhancement

None

Dependency


None


None

Dependency on UEs

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


None


None


None




34

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

Availability


Summary

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.

Benefits

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.

Description

When the UMTS signal quality is poor and the LTE signal quality is good, the RNC decides

whether to initiate measurements on the neighboring LTE cell and whether to hand over a UE

to the LTE network by considering the UE capabilities and the handover switch status. This

feature is applicable only when the following conditions are met:

� The UE to be handed over supports both UMTS and LTE and supports measurements on

the neighboring LTE cell.

� The UE to be handed over processes only PS services, and all the processed PS services


The procedure for the UMTS-to-LTE PS handover is briefed as follows:

1. The RNC sends the SGSN a Relocation Required message, which contains the

information about the target LTE cell.

2. The SGSN forwards the Relocation Required message to the MME.

3. After the LTE network is ready for the inter-RAT handover, the MME instructs the

SGSN to send a Relocation Response message to the RNC.

4. Upon receipt of the Relocation Response message from the SGSN, the RNC instructs the

UE to be handed over to the target eNodeB.

Enhancement

None

Dependency





35

None


None

Dependency on UEs

The UEs must support:

� Both UMTS and LTE

� 3GPP Release 8 or later

� UMTS-to-LTE PS handover

� Measurements on the neighboring LTE cell in connected mode


The eNodeB and MME must support the UMTS-to-LTE PS handover.


The SGSN must support the UMTS-to-LTE PS handover.


None

2.18 WRFD-150222 HSUPA Time Division Scheduling

Availability


Summary

In a cell with multiple high-speed 2 ms TTI HSUPA UEs, this feature performs time division

scheduling on these UEs to reduce interference caused by simultaneous data transmission of

the UEs. This improves the uplink throughput for this cell.

Benefits

This feature enables a cell to provide a high HSUPA throughput, even when multiple 2 ms

TTI HSUPA UEs are simultaneously performing high-speed data transmission in the cell.

With this feature, the throughput of the cell with two to eight 2 ms TTI HSUPA UEs is nearly

the same as that of the cell with only one 2 ms TTI HSUPA UE in optimal situations. For

example, all UEs are static and time division scheduled and are performing stable and

high-speed uploading services.

This feature helps increase the cell uplink throughput by 15% if:

� A cell has two receive antennas.

� Eight UEs are performing continuous FTP uploading in the cell.

� The cell is enabled with the WRFD-010691 HSUPA UL Interference Cancellation

feature.




36

Description

WCDMA is a self-interfering system. Any UE in this system is an interference source for

other UEs. The higher the data rate of a UE, the greater the interference this UE imposes on

the uplink channels of the cell. When a cell has multiple high-speed 2 ms TTI HSUPA UEs,

the uplink channel interference is the main bottleneck for the cell uplink capacity.

This feature applies to a cell with multiple high-speed 2 ms TTI HSUPA UEs, especially a

one-antenna cell where Uu-interface resources are insufficient. This feature allocates the eight

Hybrid Automatic Repeat Request (HARQ) processes of 2 ms TTI HSUPA to different UEs to

perform data transmission. During each 2 ms TTI, only one UE is transmitting data. This

reduces the interference caused by simultaneous data transmission of the UEs and improves

the cell uplink throughput.

The following figure compares code division scheduling and time division scheduling.

The gain provided by this feature depends on the UE traffic model. A static UE performing

stable and high-speed uploading has the highest gain. If all UEs in a cell are time division

scheduled and transmit data using different HARQ processes, this feature provides the highest

gain in cell throughput. As the number of time division scheduled UEs increases, however, the

load of the uplink DPCCH increases. This reduces the available resources on the E-DPDCH,

which slightly decreases cell throughput.

The gain provided by this feature also depends on whether the transmitting intervals overlap.

This feature does not apply to UEs performing soft handovers because mobility will cause the

transmitting intervals to overlap. This feature provides higher gains in indoor environments

than in outdoor environments because soft handover is less likely to occur in indoor

environments and more UEs can be scheduled in time division mode.

This feature does not apply to a cell served by multiple RRUs because Uu-interface resources

are not shared by different RRUs.

Enhancement

None

Dependency


None





37

Only the 3900 series base stations (except the BTS3902E) configured with the WBBPf board

support this feature. The downlink of the cell cannot be set up on the WBBPa board.

Dependency on UEs

The UEs must be of HSUPA category 6, 7, 8, or 9.


None


None


� WRFD-01061403 HSUPA 2ms TTI

� WRFD-010636 SRB over HSUPA

2.19 WRFD-150228 NodeB Support IPSec Bypass

Availability


Summary

When an IPSec tunnel in IPSec networking is faulty, this feature reduces the service

interruption duration by using the IPSec emergency bypass function to switch data flows from

the IPSec tunnel to a non-IPSec tunnel.

Benefits

This feature improves the user experience through:

� Enhanced operation and maintenance (O&M) capability

� Lower maintenance costs

� Shorter service interruption duration

Description

If the IPSec tunnel for a NodeB is faulty, services carried by the NodeB are manually

switched to a non-IPSec tunnel. When the IPSec tunnel is recovered, the services are

manually switched back to the IPSec tunnel. The following figure shows the working

principle of this feature.




38

Enhancement

None

Dependency


None


Only the BTS3900 series base stations support this feature, and the base stations must be

configured with the UTRPc or UMPT board.

Dependency on UEs

None


The security gateway must support IPSec.

The M2000 must provide the configuration for activating IPSec bypass.


None


� WRFD-050402 IP Transmission Introduction on Iub Interface

� WRFD-140209 NodeB Integrated IPSec




39

2.20 WRFD-150229 Intelligent Wi-Fi Searching and Selection

Availability


Summary

This feature uses a UMTS macro network to help the user equipment (UE) detect Wireless

Fidelity (Wi-Fi) hotspots. If the cell load in the macro network reaches a specified threshold

and a nearby Wi-Fi Access Point (AP) is available, this feature redistributes the data flows of

the UE to the Wi-Fi network. This feature must be supported by UEs and the radio access

network.

Benefits


� Reduced manual operations due to automatic detection of and access to Wi-Fi hotspots

� Reduced power consumption for UEs and improved user experience with Wi-Fi

� Increased usage of Wi-Fi hotspots due to cooperation between the macro and Wi-Fi

networks

� Maximized resource usage due to convergence of the macro and Wi-Fi networks

Description

Existing Wi-Fi networks are not fully utilized, probably because subscribers do not always

know the location of Wi-Fi hotspots and therefore do not always open the Wi-Fi function to

reduce the power consumption of UEs. To address this issue, this feature helps UEs detect

Wi-Fi hotspots and enables UEs to access Wi-Fi hotspots.

This feature has the following functions:

� Intelligent detection and selection of Wi-Fi hotspots

When a UE initiates a data service, if the cell load reaches a specified threshold and a

nearby Wi-Fi AP is available, the network informs the UE of the detected hotspots and

instructs the UE to switch its data service to the Wi-Fi network.

� Access to the Wi-Fi network

After a UE receives a message indicating a detected Wi-Fi hotspot, it can switch its data

service to the Wi-Fi network.

� Interface between macro and micro cells

An interface connects the RNC and the Wi-Fi Access Controller (AC). This interface

transmits Wi-Fi AP availability information, based on which the RNC determines

whether to switch UEs to the Wi-Fi network.

Enhancement

None




40

Dependency


� The BSC6900 must be configured with SPUb boards.

� The BSC6910 must be configured with EGPUa boards.


None

Dependency on UEs

The required application software must be installed on the UEs.


None


None


None

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

Availability


Summary

This feature enables the eNodeB to obtain the load information of the UMTS cells through the

RAN Information Management (RIM) procedure and select the target UMTS cell base on the

cell load during redirection or handover from LTE to UMTS. This can increase the success

rate of redirection and handover from LTE to UMTS and reduce inter-RAT ping-pong

handover.

Benefits

This feature can increase the success rate of redirection and handover from LTE to UMTS and

reduce inter-RAT ping-pong handover.

Description

The redirection or handover from LTE to UMTS, such as CS fallback or LTE to UMTS PS

handover based on load, may fail when the target UMTS cell is congested. This will impact

the success rate of redirection and handover from LTE to UMTS, bring unnecessary signaling

process for handover preparing in eNodeB and delay the handover.




41

This feature enables the eNodeB to obtain the load information of the UMTS cells through the

RIM procedure. Thus the eNodeB is able to select the proper target UMTS cell according to

the cell load.

Upon receiving a RIM request for the UMTS cells load information from the eNodeB, the

RNC sends the UMTS cells load information to the eNodeB through the RIM procedure. If

the UMTS cell load changes, the RNC sends the updated cell load information to the LTE

network through the RIM update procedure.

Enhancement

None

Dependency


None


None

Dependency on UEs

None


None


The CN must support the RIM procedure in 3GPP release 9.


None

2.22 WRFD-150232 Path Loss Based Inter-Frequency Direct Retry

Availability


Summary

During radio access bearer (RAB) setup, this feature performs the following actions on UEs

based on UE path loss:

� Enables UEs in the center of a low-frequency cell to access a high-frequency

neighboring cell.

� Enables UEs at the edge of a high-frequency cell to access a low-frequency neighboring

cell.




42

This feature achieves load sharing between high- and low-frequency cells.

Benefits

In a UMTS multiband network, this feature preferentially helps ensure capacity for

high-frequency carriers and helps ensure coverage for low-frequency carriers.

Description

This feature consists of the following phases:

1. After a UE sets up a radio resource control (RRC) connection, the RNC starts periodic

intra-frequency measurement control over the UE.

2. The RNC obtains measurement reports from the UE.

3. Upon receiving the RAB ASSIGNMENT REQUEST message from the CN, the RNC

calculates the UE path loss based on the measurement results. Then, the RNC performs

Directed Retry Decisions (DRDs) based on the UE path loss to select a suitable

frequency band for the UE:

− If the UE accesses a low-frequency cell and the UE path loss is lower than a specified

threshold, the RNC determines that the UE is located in the cell center. Then, the

RNC instructs the UE to preferentially access a high-frequency neighboring cell

through a blind handover.

− If the UE accesses a high-frequency cell and the UE path loss is higher than a

specified threshold, the RNC determines that the UE is located at the cell edge. Then,

the RNC instructs the UE to preferentially access a low-frequency neighboring cell

through a blind handover.

This feature improves user experience in the following ways:

� UEs at the edge of high-frequency cells are handed over to lower-frequency cells

because low frequency band has good propagation performance.

� In certain scenarios, UEs in the center of lower-frequency cells are handed over to

high-frequency cells to prevent data rate loss. For example, in a UMTS 900 MHz

network with 3.8 MHz bandwidth (2.0 MHz central frequency spacing between GSM

and UMTS networks, or 3.8 MHz central frequency spacing between UMTS networks),

UEs in the cell center experience data rate loss caused by interference. If these UEs are

handed over to UMTS 2100 MHz/1900 MHz cells, their maximum data rates can be

guaranteed.

This feature is based on blind handovers and applies to scenarios where high- and

low-frequency carriers are under the same NodeB and cover the same area. During RAB setup,

this feature takes precedence over other DRD algorithms.

Enhancement

None

Dependency


None





43

None

Dependency on UEs

The UEs must support both high- and low-frequency bands.


None


None


� WRFD-020400 DRD Introduction Package

� WRFD-020110 Multi Frequency Band Networking Management

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

Availability


Summary

A new service processing board Evolved General Processing Unit REV:a (EGPUa) is

introduced in the BSC6910 to simultaneously process user-plane data and control-plane data.

The RNC can automatically adjust the ratio of resources split between processing user-plane

data and control-plane data.

Benefits

This feature increases the hardware usage and reduces the maintenance cost.

Description

The RNC automatically monitors the user-plane load and control-plane load. When the

difference between user-plane load and control-plane load reaches a specified threshold, the

RNC automatically adjusts the ratio of resources split between processing user-plane data and

control-plane data.




44

The services on the CPU resources adjusted will drop from the network.

The operator can specify the time for automatic adjustment. It is recommended to perform the

automatic adjustment during off-peak hours to minimize the impact on services.

Enhancement

None

Dependency




None

Dependency on UE

None


The M2000 and CME versions must be compatible with the BSC6910.


None


None

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

Availability





45

Summary

This feature is applicable to the HSUPA Best Effort (BE) service. When an HSUPA UE is in

the small retransmission state, this feature dynamically configures an optimal power offset for

the data channel based on the changes in uplink load and throughput. This feature helps

maintain the power of such UE on the uplink DPCCH at an optimal level, thereby increasing

the capacity of an HSUPA cell with multiple HSUPA UEs.

Benefits

This feature significantly improves the capacity of HSUPA cells in a live network, where the

feature WRFD-010641 HSUPA Adaptive Transmission is unavailable or UEs cannot enter the

large retransmission state due to CE limitation.

This feature significantly increases the HSUPA capacity of cells where a large number of

HSUPA UEs are processing low-speed uplink services. When there are a large number of UEs

processing data services in hot spots in busy hours, this feature improves the HSUPA capacity

of the cell by 5% to 20%, without increasing the cell load. This capacity improvement is

indicated by the increase in average cell throughput, in the number of UEs that can

simultaneously perform data transmission in the uplink, or in the decrease in Received Total

Wideband Power (RTWP).

Description

The offset of E-DPDCH power relative to DPCCH power is one of the major factors that

determine DPCCH power in the uplink. For an HSUPA UE in the small retransmission state,

if the data rate is low, a high offset can be configured for the E-DPDCH. This decreases the

power on the DPCCH and reduces the load on the uplink control channel. After the load is

reduced, UEs can transmit more data in the uplink, thereby increasing the capacity of HSUPA

cells. If the data rate is high, a low offset can be configured for the E-DPDCH. This increases

the power on the DPCCH, thereby meeting the power requirements of multipath searching

and channel estimation and ensuring the performance of HSUPA services.

When the feature WRFD-010641 HSUPA Adaptive Transmission is enabled, the offset of the

E-DPDCH power relative to the DPCCH power is not adjusted. In such a case, the gain of the

HSUPA Adaptive Transmission feature is not affected. Because the feature WRFD-010641

HSUPA Adaptive Transmission enables HSUPA UEs to adjust to the large retransmission state,

the capacity of the cell will be greatly increased, but with more CE consumption.

This feature is independent from the feature WRFD-010641 HSUPA Adaptive Transmission,

but these two features can be enabled together. Using these features together further increases

the uplink capacity of the cell.

Enhancement

Before RAN15.0, this feature is only applicable to the HSUPA 10 ms BE service. In RAN15.0,

this feature is applicable to both HSUPA 10 ms BE service and HSUPA 2 ms BE service.

Dependency


None





46

None


WRFD-010612 HSUPA Introduction Package


None

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

Availability


Summary

This feature provides a downlink peak rate of 84 Mbit/s for a single user through the

simultaneous use of 64QAM, multiple-input multiple output (MIMO), and dual-cell HSDPA

(DC-HSDPA).

Benefits

This feature enables end users to enjoy high-speed data services.

Description

3GPP Release 9 defines the scenario where MIMO and DC-HSDPA are used together. When

the techniques 64QAM, MIMO, and DC-HSDPA are jointly used, a peak downlink rate of 84

Mbit/s can be achieved for a single user.

Enhancement

In RAN15.0, the downlink peak rate of 84 Mbit/s for a single user can be achieved by using

4C-HSDPA technique.

Dependency


� To enable this feature on a BSC6900, the DPUe board must be configured for the data

plane and the interface board FG2a (GE port), FG2c (GE port), GOUa, or GOUc must be

configured.

� To enable this feature on a BSC6910, the interface board FG2c (GE port), GOUc, or

EXOUa must be configured.


� The BTS3812AE/BTS3812E and DBS3800 cannot provide the downlink peak rate of 84

Mbit/s per user.

� The 3900 series base station must be configured with the WBBPd/WBBPb3/WBBPb4

board.




47

Dependency on UE

The UE must be of category 28, 31 or 32 to support 84 Mbit/s in the downlink, according to

3GPP Release 9.

Dependency on other NE

None

Dependency on other CN

CN support user rate of 84Mbit/s or above.


� WRFD-010689 HSPA+ Downlink 42Mbit/s per User

� WRFD-010693 Downlink 64QAM+MIMO

� WRFD-010699 DC-HSDPA+MIMO

Or

� WRFD-010689 HSPA+ Downlink 42Mbit/s per User

� WRFD-150207 4C-HSDPA

2.26 WRFD-010699 DC-HSDPA+MIMO

Availability


Summary

DC-HSDPA+MIMO is introduced in 3GPP Release 9. This feature combines DC-HSDPA

(introduced in 3GPP Release 8) and MIMO (introduced in 3GPP Release 7). This feature

allows the NodeB to send HSDPA data to a UE simultaneously over two adjacent carriers on

the same frequency band within the same coverage area by using MIMO.

Benefits

This feature fully utilizes the advantages of dual-carrier and dual-antenna techniques of

DC-HSDPA and MIMO respectively. It improves the spectrum efficiency and significantly

increases the single-user peak throughput, cell-edge-user throughput, and cell capacity.

� Increasing the single user peak throughput

DC-HSDPA+MIMO achieves higher spatial multiplexing gain than DC-HSDPA. This

feature doubles the single-user peak rate from 28 Mbit/s to 56 Mbit/s (When using

16QAM modulation) or from 42 Mbit/s to 84 Mbit/s (with 64QAM).

DC-HSDPA+MIMO uses two carriers simultaneously while SC-HSDPA uses only one

carrier. This feature doubles the single-user peak rate, as mentioned previously.

� Increasing the cell-edge-user throughput

DC-HSDPA+MIMO achieves closed-loop transmit diversity gain on the cell edge,

compared with DC-HSDPA.




48

DC-HSDPA+MIMO use two carriers and doubles the throughput, compared with

SC-HSDPA+MIMO.

� Increasing the cell capacity

DC-HSDPA+MIMO improve the spectrum efficiency within 10 MHz bandwidth and

Huawei simulation test shows that it can increase the system throughput by 10% to 20 %,

compared with DC-HSDPA.

Description

The following figure shows the basic principles of DC-HSDPA+MIMO.

The DC-HSDPA+MIMO feature brings together the performance enhancement benefits of the

two different technologies DC-HSDPA and MIMO.

RAN13.0 supports the configuration of MIMO on one or two carriers to reach the theoretical

peak rate of 63 Mbit/s or 84 Mbit/s respectively.

The PS best effort services are carried over DC-HSDPA+MIMO.

DC-HSDPA+MIMO apply the same principles as DC-HSDPA in load control and mobility

management.

Enhancement

In RAN15.0, the non adjacent carriers on the same frequency band can be used for

DC-HSDPA.

Dependency


None


� The BTS3812E and BTS3812AE must be configured with the EBBI or EDLP board, and

the uplink services cannot be set up on HBBI/HULP board.

� The DBS3800 must be configured with the EBBC or EBBCd board. In addition, the

DBS3800 supports a maximum of DC+MIMOx1, that is, only one frequency in the

DC-HSDPA cell can be configured with the MIMO feature.

� The 3900 series base station must be configured with the WBBPb or WBBPd board.





49


� WRFD-010684 2x2 MIMO


� The UE must be of HS-DSCH category 25, 26, 27, or 28.

� Differentiated Service Management

2.27 WRFD-010696 DC-HSDPA

Availability


Summary

The Dual Cell-HSDPA (DC-HSDPA) feature allows the UE to establish connections to two

adjacent inter-frequency same-coverage cells. With this feature, the UE can use the resources

in both cells that perform an operation on different carriers, increasing the peak throughput of

the UE.

Benefits

This feature improves the single-user throughput and the cell throughput.

� Single-user throughput

After DC-HSDPA is introduced, the throughput is doubled at the center and border of the cell.

Theoretically, DC-HSDPA in 64QAM mode can provide a peak throughput of 42 Mbit/s at the

center of the cell. The gain also shortens the data transmission delay and improves user

experience.

� Cell throughput

After DC-HSDPA is introduced, DC-HSDPA has the cell throughput gain of 5%–10% relative

to the total throughput of the two inter-frequency co-coverage cells. The gain is inversely

proportional to the number of UEs in a cell.

Description � Configuration of primary and secondary carriers

When two frequencies, for example, f1 and f2 are used in DC-HSDPA, one DL frequency

serves as the primary carrier and the other as the secondary carrier, which is defined in 3GPP

TR25.825. In the UL, only one frequency is used, which serves as the primary carrier.

Both DC-HSDPA cells are configured with the PCPICH, SCH, PCCPCH, SCCPCH, and

PRACH. Both cells have the basic common channel (CCH) configuration for retaining and

initiating services. The single carrier (SC) UEs can camp or originate a call in each cell.

� DC-HSDPA differentiated bearer policy




50

The CS service, IMS signaling, SRB signaling, or PS conversational service is carried on a

single carrier instead of DC-HSDPA because the amount of data is small and the gain is

insignificant when DC-HSDPA is used.

The BE or streaming service can be carried over the DC-HSDPA. The BE/streaming

combined service is carried over the DC-HSDPA preferentially.

� Mobility management

The active set information and measurement reports are sent on the primary carrier during the

handover of DC users. Whether to perform an intra-frequency or inter-frequency handover

depends on the frequencies of the primary carrier and the neighboring cell.

RAN12.0 supports handovers between DC cells, between the DC cell and the SC cell, and

between the DC cell and the system using the other RAT, to ensure seamless roaming of DC

terminals.

� State transition in DC-HSDPA

The UE state transition in DC-HSDPA is performed in the same way as the state transition in

SC mode.

� Traffic steering in DC-HSDPA

In the original network, R99 services preferentially use f1 and HSPA services use f2. After

DC-HSDPA is introduced, both f1 and f2 can be used for DL DC-HSDPA, and f2 is preferred

for HSUPA. In this way, the UL load on f1 is reduced, without disrupting R99 services.

If the R99 and HSPA services have the same priority on f1 and f2 in the original network,

traffic steering is kept the same as that of HSPA after DC-HSDPA is introduced.

STTD mode is not supported when activate DC-HSDPA.

Enhancement

In RAN15.0, the non adjacent carriers on the same frequency band can be used for

DC-HSDPA.

Dependency


None


� The HBBI and HDLP of the BTS3812E AND BTS3812AE do not support DC-HSDPA.

To support DC-HSDPA, the EBBI or EDLP board must be configured.

� The BBU3806 configured with the EBBC or EBBCd board supports this feature.

� The 3900 series base station supports the function when the WBBPb or WBBPd is

configured.

Dependency on UE

The HS-DSCH capabilities are classified into category 21, 22, 23, 24, 25, 26, 27, 28.


None




51


None


� WRFD-010610 HSDPA Introduction Package

� WRFD-010685 Downlink Enhanced L2

� WRFD-010629 DL 16QAM Modulation

2.28 WRFD-010701 Uplink Enhanced CELL_FACH

Availability


Summary

This feature maps the random access channel (RACH) onto the E-DCH Dedicated Physical

Data Control Channel (E-DPDCH). With this feature, UEs in the CELL_FACH state can

transmit uplink data at higher rates.

Benefits

This feature improves the "always online" experience for users by:

� Providing high-speed uplink data transmission for UEs in the CELL_FACH state

� Reducing the following by more than 50% in favorable radio environments:

− UE service setup delay from idle mode to CELL_DCH state

− State transition delay from CELL_FACH to CELL_DCH

Description

This feature was first specified by 3GPP Release 8.

This feature enables UEs in the CELL_FACH state to use the E-DPDCH instead of the

physical random access channel (PRACH) in the uplink. The PRACH provides a data rate of

8 to 16 kbit/s when it uses the 20 ms TTI. The E-DPDCH provides a maximum data rate of

5.76 Mbit/s when it uses the 2 ms or 10 ms TTI.

This feature uses Extended AI (EAI) to fully utilize the signatures for random access. This

reduces the probability of uplink channel collision to make data transmission smoother.

Enhancement

The feature enhancement in RAN15.0 allows UEs in the CELL_FACH state to send feedback

on High Speed Downlink Shared Channel (HS-DSCH) data transmission to NodeBs during

simultaneous uplink and downlink data transmission. The UEs send ACK/NACK responses

and channel quality indicator (CQI) information to the NodeBs over the High Speed

Dedicated Physical Control Channel (HS-DPCCH). This improves the downlink average

throughput for the WRFD-010688 Downlink Enhanced CELL_FACH feature (the FACH is

mapped onto the HS-DSCH).




52

Before this feature is enhanced, data is retransmitted to the NodeBs on the HS-DSCH

regardless of whether the data is received. UEs only report the "Measured results on RACH"

in the uplink, which is insufficient for evaluating downlink HS-DSCH transmission quality.

After this feature is enhanced, UEs promptly report downlink channel transmission changes to

NodeBs. This greatly improves data transmission efficiency in favorable channel

environments.

According to 3GPP protocols, the feature enhancement enables UEs in the CELL_FACH state

to transmit data at a peak rate of 1.8 Mbit/s in the downlink.

The feature enhancement improves the downlink average throughput by 60% to 360% for a

cell with UEs in the CELL_FACH state if the following conditions are met:

� The power is sufficient.

� The data source is sufficient.

� The channel environment is favorable with the reported CQI greater than 13.

� The percentage of the period during which data is transmitted in the uplink and downlink

simultaneously is 50% to 80% for UEs in the CELL_FACH state.

Dependency


None


� The BTS3812E, BTS3812A, and BTS3812AE must be configured with the EULPd,

EBBI, EBOI, or EULP board. Downlink services must be established on the EBBI,

EBOI, or EULP board. The BTS3812E, BTS3812A, and BTS3812AE do not support

EAI.

� The DBS3800 must be configured with the EBBC or EBBCd board. Downlink services

must be established on the EBBC or EBBCd board. To support EAI, the DBS3800 must

be configured with the EBBCd board.

� The 3900 series base station must be configured with the WBBPb, WBBPd, or WBBPf

board. The downlink services must be established on the WBBPb, WBBPd, or WBBPf

board. To support EAI, the 3900 series base station must be configured with the WBBPd

or WBBPf board.


� WRFD-010652 SRB over HSDPA

� WRFD-010636 SRB over HSUPA

� WRFD-010695 UL Layer 2 Improvement

� WRFD-010688 Downlink Enhanced CELL_FACH

Dependency on UEs

The UEs must be of 3GPP Release 8 or later and must support this feature.




53

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

Availability


Summary

This feature applies to scenarios where a UE is served by DC-HSDPA or DC-HSDPA+MIMO

in the downlink and by DCH or SC-HSUPA in the uplink.

When the UE's traffic volume is low, this feature deactivates the downlink secondary carrier

of the UE so that the UE becomes a single-carrier UE. When the UE's traffic volume increases,

this feature reactivates the secondary carrier so that the UE becomes a dual-carrier UE again.

SC-HSUPA is short for singe-carrier HSUPA.

Benefits

In single-carrier transmission, UEs only demodulate data received by the primary carrier. This

reduces the transmit power on the High Speed Dedicated Physical Control Channel

(HS-DPCCH) and decreases the cell power load in the uplink.

For example, the cell power load in the uplink is decreased by 5% to 10% when the following

conditions are met:

� The secondary carrier is deactivated.

� There are a large number of DC-HSDPA UEs in the cell.

� The traffic volume in the downlink is low.

Description

The NodeB decides whether to activate or deactivate the UE's secondary carrier based on the

UE data source and UE throughput as follows:

� When the UE data source is insufficient and UE throughput is low, the NodeB sends an

HS-SCCH order to the UE to deactivate the secondary carrier.

� When the data source is sufficient and UE throughput is high, the NodeB sends an

HS-SCCH order to the UE to activate the secondary carrier.

Enhancement

This feature applies to DB-HSDPA and DB-HSDPA+MIMO users after DB-HSDPA and

DB-HSDPA+MIMO are introduced in RAN15.0.

Dependency


None




54


None


WRFD-010696 DC-HSDPA

Dependency on UEs

The UEs must be in one of the following HS-DSCH categories:

� HS-DSCH category 21, 22, 23, or 24: to support DC-HSDPA

� HS-DSCH category 25, 26, 27, or 28: to support DC-HSDPA+MIMO

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

Availability


Summary

In case of mains failure, the backup power system starts to operate. In this case, this feature

can achieve hierarchical carrier shutdown based on the shutdown duration and cell priority.

Benefits

This feature can reduce the NodeB power consumption and extend the up time of running

batteries in case of mains failure. For batteries, long-time running leads to aging, decreasing

the power backup time. This feature, however, can extend the up time of batteries, so that the

aged batteries still meet the requirements of the NodeB for power backup time. In other words,

the service life of batteries is prolonged.

Description

After this feature is enabled, the NodeB can assign priorities to carriers and then shut down

carriers by priority. In case of mains failure, the batteries start to operate. Then, the NodeB is

triggered to shut down the non-reserved and reserved local cells based on the preset shutdown

durations (T1, T2). After the mains failure is rectified, the NodeB automatically restores all

the cells that were shut down.




55

Enhancement

In RAN 15.0, a parameter is added for the RAT-specific power backup and energy saving

policy. Based on the parameter settings, a multi-mode base station uses a specific set of

shutdown durations. Here RAT stands for radio access technology.

Dependency


None


The BTS3902E does notsupport this feature.

Dependency on UE

None


None


None


None




56

2.31 WRFD-050402 IP Transmission Introduction on Iub Interface

Availability


This feature is introduced in 3GPP R5.

Summary

This feature enables the Iub interface to be carried on the IP network.

Benefits

This feature provides a new Iub transport solution for operator. With IP transmission,

transport cost will decrease greatly with HSDPA/HSUPA service compared with ATM

transport cost.

Description

Huawei RNC provides the following physical port types on Iub IP transmission solution to

support different networking requirements:

� E1/T1

� FE

� GE (with LAN Switch in BSC6800)

� STM-1/OC-3c(POS (Packet Over SDH), BSC6900 only)

� Channelized STM-1/OC-3(CPOS (Channelized POS), BSC6900 only)

Huawei NodeB provides the following physical port types on Iub IP transmission solution to

support different networking requirements:

� E1/T1

� Electrical FE

� Optical FE (3900 NodeB only)

� Electrical GE (3900 NodeB only)

� Optical GE (3900 NodeB only)

The following features are also included:

� Compliant with 3GPP R5 TR25.933

� Support GE/FE/E1/T1/channelized STM-1/channelized OC-3/STM-1/OC-3c physical

interface

� Support Diffserv mechanism and IEEE802.1P

� Support IPV4

� Support IP head compression

� Support ML-PPP and MC-PPP, RAN11.0 NodeB support ML-PPP combined two

transmission card

� Support DHCP, PPP Mux and VLAN




57

� Support 1+1 and 1:1 MSP

The following figure shows the IP networking on the Iub Interface.

NodeBNodeB RNCE1/STM-1 E1/STM-1RNLUDP/SCTPIPPPP/HDLCPHY PHYRNLUDP/SCTPIPPHYPHY PPP/HDLC

SDH/PDHADM ADM

NodeBNodeB

RNC

L2 NetworkFE FERNL

UDP/SCTP

IP

MAC(L2)

PHY

MAC(L2)

PHY

RNL

UDP/SCTP

IP

MAC(L2)

PHY

MAC(L2)

PHY

LAN Switch LAN Switch

Besides the transport layer change (for example, M3UA, SCTP), the Iub IP brings about some

changes in CAC as well as service differentiation.

IP PATH is defined as the connection between RNC and NodeB. Each IP PATH is configured

with a maximum DL PATH bandwidth and a maximum UL PATH bandwidth, which are

configurable for operators. When a new call is coming, the RNC compares the required

service bandwidth with the available IP PATH bandwidth for UL and DL. If the IP PATH

bandwidth available for use is insufficient, the call is rejected. If the call is admitted, RNC

will reserve the bandwidth and mark it as being used.

The Iub IP adopts the DiffServ for QoS differentiation, similar to the differentiated ATM PVC.

PHB is defined according to the traffic type, each PHB having a DSCP (DiffServ Code Point)

and priority.




58

BEPS Background

AF1PS Interactive

AF3PS Streaming

AF4PS Conversational

EFCS

EFSRB

EFCommon Channels

PHB(Per Hop Behavior)Traffic Type

BEPS Background

AF1PS Interactive

AF3PS Streaming

AF4PS Conversational

EFCS

EFSRB

EFCommon Channels

PHB(Per Hop Behavior)Traffic Type

6B'000000BE

5B'001010AF1

4B'010010AF2

3B'011110AF3

2B'100110AF4

1B'101110EF

Prior Queue #DSCPPHB

6B'000000BE

5B'001010AF1

4B'010010AF2

3B'011110AF3

2B'100110AF4

1B'101110EF

Prior Queue #DSCPPHB

RAN14.0 supports the whitelist, VLAN-based packet filtering, and malformed packet attack

defense functions.

Enhancement

In RAN10.0, the BSC6810 supports the POS/CPOS interface (UOIa and POUa).

RAN10.0, when the gateway or peer entity is faulty, this feature enables the RNC to detect the

link fault and then trigger IP re-route or board switch, avoiding packet loss and call drop.

RAN11.0 NodeB support ML-PPP combined two transmission card.

RAN13.0 Iub support RNC and NodeB integrated firewall

RNC integrated firewall include the following factions:

The internal firewall inspects the incoming IP data over the OM interface and provides the

following functions:

IP address filter. This technique allows only the IP data from authorized IP addresses and

network segments.

Safeguard against attacks of ICMP ping, IP fragments, low TTL, smurf, and DDos.

Safeguard against attacks of TCP sequence prediction, and SYN flood.

The internal firewall inspects the incoming IP data over the Iub, Iur, and Iu interfaces and

provides the following functions:

Intelligent white-listing: With this function, only data from permissible peer IP addresses and

ports and data of permissible protocol types can access the RNC.

Safeguard against ARP and ICMP flood

Safeguard against malformed packets

Limiting speed of the broadcast messages




59

NodeB integrated firewall include the following functions:

The internal firewall inspects incoming all the IP data including maintenance data, control

plane data and user plane data and provides the following functions:

� White-listing: With this function, only data from permissible peer IP addresses and ports

and data of permissible protocol types can access the NodeB. Ping denial function will

be supported; NodeB will drop the ICMP packets in this mode.

Maintenance data, control plane data and user plane data of 3900 series NodeB and

Maintenance data and control plane data of BTS3812E/AE and DBS3800 will filter by

White-listing function.

� Safeguard against Address Resolution Protocol (ARP) and Internet Control Message

Protocol (ICMP) flood

� Since RAN14.0, white-listing, VLAN packet filtering, and tool-based protection against

malformed packets are supported.

� Broadcast-message speed limiting

� Since RAN15.0, 10 GE interface boards are supported by the BSC6910.

� Since RAN15.0, the transmission network configuration can be simplified. That is, IP

PATH is not necessary to be configured. If the IP PATH is not configured, each adjacent

node is configured with a transmit bandwidth and a receive bandwidth, which are

configurable for operators. When a new call is coming, the RNC compares the required

service bandwidth with the available transmit bandwidth and receive bandwidth of the

adjacent node. If the bandwidth available for use is insufficient, the call is rejected. If the

call is admitted, RNC reserves the bandwidth and mark it as being used.

Dependency


BSC6900

� Only the PEUa, POUa, and POUc boards support IP head compression.

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

interface.

� Only the FG2c and GOUc boards support the RNC integrated firewall for the Iub, Iur,

and Iu interfaces.

� Only the FG2a, GOUa, FG2c, and GOUc boards support BFD.

� 10 GE interface boards are not supported.

BSC6910

� All IP interface boards support the RNC integrated firewall and BFD.

� 10 GE interface boards are supported.

� IP head compression is not supported.

� IP path and IP-path-based bandwidth configuration are not supported.

� IP over E1 is not supported.


� NUTI board is needed with BTS3812E/AE to support this feature.




60

� Only the 3900 series NodeB supports inter-board ML-PPP.

Dependency on UE

None


None


None


None

2.32 WRFD-050409 IP Transmission Introduction on Iu Interface

Availability



Summary

This feature enables the Iu interface to be carried on the IP network.

Benefits

This feature provides a new Iu transport solution for operator. With IP transmission, transport

cost will decrease greatly compared with ATM transport cost.

Description

This feature provides Iu over IP transport solution including the following features:

� Compliance with 3GPP R5 TR25.933

� Support IP over FE electrical interface

� Support IP over GE electrical interface and GE optical interface

� Support IP over STM-1/OC-3c optical interface (POS (Packet Over SDH)) (BSC6900

only)

� Support IP over channelized STM-1/OC-3 optical interface(CPOS (Channelized POS))

(BSC6900 only)

� Support IuCS over IP over E1/T1 physical interface (BSC6900 only)


� Support IPV4


� Support ML-PPP and MC-PPP




61

� Support PPP Mux and VLAN

� Support FE/GE 1+1 backup redundancy

� Support FE/GE load share redundancy

� Support STM-1/OC-3c 1+1 and 1:1 MSP

� Support channelized STM-1/OC-3 1+1 and 1:1 MSP

IP networking solution can be L1, L2, L3 networking on Iu interface similar to that on the Iub

Interface.

Besides the transport layer change, Iu IP brings some changes in CAC as well as service

differentiation

IP PATH is defined as the connection between RNC and CN. Each IP PATH is configured

with a maximum DL PATH bandwidth and maximum UL PATH bandwidth, which is

configurable by operator. When a new call is coming, RNC will compare the required service

bandwidth with the available IP PATH bandwidth for UL and DL. If available IP PATH

bandwidth is insufficient, the call is rejected. If the call is admitted, RNC will reserve the

bandwidth and mark it as being used.

Enhancement

In RAN10.0, the BSC6810 supports the POS/CPOS interface (UOIa and POUa).

In RAN10.0, when the gateway or peer entity is faulty, this feature enables the RNC to detect

the link fault and then trigger IP re-route or board switch, avoiding packet loss and call drop.

In RAN13.0, RNC integrated firewall is supported, which include the following functions:




network segments.










Since RAN15.0, 10 GE interface boards are supported by the BSC6910.

Since RAN15.0, the transmission network configuration can be simplified. That is, IP PATH

is not necessary to be configured. If the IP PATH is not configured, each adjacent node is

configured with a transmit bandwidth and a receive bandwidth, which are configurable for

operators. When a new call is coming, the RNC compares the required service bandwidth

with the available transmit bandwidth and receive bandwidth of the adjacent node. If the


reserves the bandwidth and mark it as being used.




62

Dependency


BSC6900


interface.


and Iu interfaces.



BSC6910




� PPP, MC-PPP, and PPP MUX are not supported.



None

Dependency on UE

None


None


� CN should support IP transportation.


None

2.33 WRFD-050410 IP Transmission Introduction on Iur Interface

Availability






63

Summary

This feature enables the Iur interface to be carried on the IP network.

Benefits

This feature provides a new Iur transport solution for operator. With IP transmission, transport

cost will decrease greatly compared with ATM transport cost.

Description

This feature provides Iur over IP transport solution including the following features:

� Compliant with 3GPP R5 TR25.933

� Support GE/FE/E1/T1 physical interface

� Support IP over FE electrical interface

� Support IP over GE electrical interface and GE optical interface (BSC6900 only)

� Support IP over STM-1/OC-3c optical interface (POS (Packet Over SDH)) (BSC6900

only)

� Support IP over channelized STM-1/OC-3 optical interface(CPOS (Channelized POS))

(BSC6900 only)

� Support IP over E1/T1 physical interface (BSC6900 only)


� Support IPV4


� Support ML-PPP and MC-PPP

� Support DHCP, PPP Mux and VLAN

� Support FE/GE 1+1 backup redundancy

� Support FE/GE load share redundancy

� Support STM-1/OC-3c 1+1 and 1:1 MSP

� Support channelized STM-1/OC-3 1+1 and 1:1 MSP

IP networking solution can be L1, L2, L3 networking on Iur interface similar to that on the

Iub Interface.

Besides the transport layer change, Iur IP brings some changes in CAC as well as service

differentiation.

IP PATH is defined as the connection between SRNC and DRNC. Each IP PATH is configured

with a maximum DL PATH bandwidth and maximum UL PATH bandwidth, which is

configurable by operator. When a new call is coming, RNC will compare the required service

bandwidth with the available IP PATH bandwidth for UL and DL. The call will be rejected if

no enough IP PATH bandwidth is available. After the call is admitted, RNC will reserve

bandwidth as in use.

The Iur IP adopts the DiffServ for QoS differentiation, similar to the differentiated ATM PVC.

PHB is defined according to the traffic type, each PHB having a DSCP (DiffServ Code Point)

and priority.




64

Enhancement

In RAN10.0, packet over STM-1/OC-3c is supported.

In RAN10.0, packet over channelized STM-1/OC-3 is supported.

In RAN10.0, when the gateway or peer entity is faulty, this feature enables the RNC to detect

the link fault and then trigger IP re-route or board switch, avoiding packet loss and call drop.

In RAN13.0, RNC integrated firewall is supported, which include the following functions:




network segments.










Since RAN15.0, 10 GE interface boards are supported by the BSC6910.

Since RAN15.0, the transmission network configuration can be simplified. That is, IP PATH

is not necessary to be configured. If the IP PATH is not configured, each adjacent node is

configured with a transmit bandwidth and a receive bandwidth, which are configurable for

operators. When a new call is coming, the RNC compares the required service bandwidth

with the available transmit bandwidth and receive bandwidth of the adjacent node. If the


reserves the bandwidth and mark it as being used.

Dependency


BSC6900


interface.


and Iu interfaces.



BSC6910





65



� PPP, MC-PPP, and PPP MUX are not supported.



None

Dependency on UE

None


The neighboring RNC should also support IP transportation.


None


None

2.34 WRFD-050425 Ethernet OAM

Availability

This feature is available from RAN11.0 and is only applicable to the BSC6900.

Summary

This feature is related to point-to-point and end-to-end Ethernet OAM. It provides an effective

solution for Ethernet link management and fault detection.

Benefits � The Ethernet OAM helps the operator to manage user access in terms of detection,

monitoring, and rectification of Ethernet faults.

� This feature achieves reliability and high availability of Ethernet services, enables the

service provider to provide economical and efficient advanced Ethernet services, and

ensures that the services have high quality and reliability that are required by

telecommunications services.

� This feature is implemented at the RAN equipment, minimizing the impact of Ethernet

bandwidth fluctuation or faults on RAN.

Description

With the introduction of IP RAN to the WCDMA system, the Ethernet as a type of transport

bearer is widely applied. As a L2 protocol, Ethernet OAM can report the status of the network

at the data link layer, monitoring and managing the network more effectively.




66

The functions of Ethernet OAM consist of fault detection, notification, verification and

identification. The faults involve the hard faults that can be detected by the physical layer,

such as broken links, and the soft faults that cannot be detected by the physical layer, such as

memory bridging unit damage. Ethernet OAM plays a significant role in reducing

CAPEX/OPEX and complying with the Service Level Agreement (SLA).

RAN supports two types of Ethernet OAM: point-to-point Ethernet OAM (802.3ah) and

end-to-end Ethernet OAM (802.1ag). The two types are described as follows:

� Point-to-point Ethernet OAM

The point-to-point Ethernet OAM complies with IEEE 802.3ah. What the point-to-point

Ethernet OAM takes into consideration is the last mile, rather than the specific services.

The OAM implements point-to-point maintenance of the Ethernet through mechanisms

such as OAM discovery, loopback, link monitoring, and fault detection.

� End-to-end Ethernet OAM

The end-to-end Ethernet OAM complies with IEEE 802.7ag. With regard to the OAM

domain as a whole, it establishes end-to-end detection to perform maintenance of the

Ethernet based on the services.

Enhancement

RAN12.0 the end-to-end Ethernet OAM complies with IEEE 802.8ag.

In RAN 15.0, ITU-T Y.1731 is supported by NodeB, which has incorporated the following

functions specified by IEEE 802.1ag:

� Continuity check

� Loopback test

� Link tracing

� End-to-end monitoring on packet loss, delay, and delay variation

Therefore, when the ITU-T Y.1731 is used, do not use IEEE 802.1ag.

Dependency


The RNC does not support ITU-T Y.1731.


� RAN11.0, BTS3812E/AE and DBS3800 can only support IEEE 802.1ag draft 7; 3900

series NodeB can support IEEE 802.3ah and IEEE 802.1ag draft 7.




67

� RAN12.0, BTS3812E/AE, DBS3800, 3900 series NodeB can support both IEEE 802.3ah

and IEEE 802.1ag draft 8.

� Only UMPT board and UTRPc board support the enhancement in RAN15.0.

Dependency on UE

None


None


None


� WRFD-050402 IP Transmission Introduction on the Iub Interface, or

� WRFD-050409 IP Transmission Introduction on the Iu Interface, or

� WRFD-050410 IP Transmission Introduction on the Iur Interface

2.35 WRFD-140210 NodeB PKI Support

Availability


Summary

This feature enables the NodeB on a live network to use the Certificate Management Protocol

version 2 (CMPv2) to automatically obtain a device digital certificate signed by the operator's

certificate authority (CA). With the device digital certificate, the NodeB and other network

elements authenticate each other according to IPSec and Secure Sockets Layer (SSL).

Benefits

This feature enables network elements to authenticate each other and ensures network

security.

Description

PKI is the foundation and core of contemporary network security construction and provides

information security based on the asymmetric cryptographic algorithm. A digital certificate

identifies a piece of equipment and authenticates the equipment identity during network

communication. The digital certificate includes the following information:

� Equipment information

� Validity period of the certificate

� Public key




68

Digital signature of the organization that issues the certificate A trusted certificate authority

(CA) digitally signs the equipment information and public key to create a digital certificate.

During digital certificate authentication, asymmetric keys are used to authenticate equipment

identity. The sender uses a private key to sign data, and the receiver uses the public key in the

certificate to check signature validity.

Huawei base stations support PKI-based certificate management solutions, which include the

certificate-preconfiguration phase, deployment phase, and operation phase. This phased

approach facilitates use of the certificates. Certificates in Huawei base stations are managed

by using Certificate Management Protocol (CMPv2).

For Huawei products, digital certificates are applicable in either of the following scenarios:

� Authentication during the setup of an IPSec tunnel between a base station and a SeGW in

a radio bearer network

� Authentication during the setup of an SSL-encrypted operation and maintenance (O&M)

channel between a base station and the M2000

To use this feature, the peer device, such as a SeGW, must also support the PKI function.

Enhancement

In RAN15.0, the certificate revocation function is enhanced so that the original PKI certificate

can be automatically revoked when a NodeB transmission board is replaced or another

certificate is requested. This ensures the certificate security.

This enhancement involves the NodeB, M2000, and the operator's PKI system. The details are

as follows:

The M2000 manages and monitors certificates for all NodeBs. When a NodeB transmission

board is replaced or a NodeB is deployed, the M2000 exports the list of certificates to be

revoked and periodically reports the list to the operator's PKI system. The PKI system then

revokes certificates recorded in the list.

Dependency


None





69

The 3900 series base station must be configured with the UTRPc or UMPT board to support

this feature.

Dependency on UE

None


The operator's CA must be deployed in the network.


None


None

2.36 WRFD-020129 Service-Based PS Service Redirection from UMTS to LTE

Availability


Summary

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.

Benefits

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.

Description

In a UMTS/LTE multi-layer network, if UE or network does not support the handover from

UMTS to LTE, then the UE will be redirected from UMTS to LTE, the following conditions

must be met:

1. The conditions for PS handover from UMTS to LTE are met and the UE or the network

cannot support the handover from UMTS to LTE.

2. The UE supports both UMTS and LTE.

3. The UE is processing only the PS services. The RAB assignment message from the SGSN

does not indicate that the PS services cannot be handed over to the LTE network.

The RNC carries the LTE frequency information in the RRC Connection Release message and

directs the UE to access the LTE network.




70

Enhancement

In RAN15.0, the following functions are added:

1. The redirection may be triggered when the best cell changes.

2. The blind redirection is supported.

3. The frequency is added in SIB9 for redirection and blink redirection.

Dependency


None


None


None


CN should support cooperation from UMTS to LTE.


The UE must support 3GPP Release 8 (Sept. 2008) or later. It also must support both UMTS

and LTE.

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

Availability


Summary

If a UMTS and LTE dual-mode UE in a UMTS and LTE overlapping coverage area processes

only PS services in the UMTS network, Service-Based PS Handover from UMTS to LTE

allows the RNC to hand over the PS services to the LTE network.

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




71

Description

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 CS fallback (CSFB), after the UE

terminates the CS voice service in the UMTS network, the UE still has ongoing PS

services.

The implementation is as follows:

1. The RNC sends the SGSN a Relocation Required message, which contains the information

about the target LTE cell.

2. The SGSN forwards the relocation request to the MME.

3. After the LTE side has made preparations for the inter-RAT handover, the MME instructs

the SGSN to send a Relocation Response message to the RNC.

4. Upon receipt of the Relocation Command message forwarded by the SGSN from the MME,

the RNC instructs the UE to hand over to the target eNodeB.

To use this feature, both the UMTS network and the UE must support LTE measurement and

UMTS-to-LTE PS handovers.

This feature supports interoperability between the UMTS network and the TDD LTE network

and between the UMTS network and the FDD LTE network. The TDD LTE and FDD LTE

networks, however, cannot coexist.

When the MOCN feature is enabled in the target LTE network, Service-Based PS Handover

from UMTS to LTE must not be enabled if the UMTS and LTE networks do not share the

same PLMN. Otherwise, call drops may occur.

Enhancement

In RAN15.0, the handover may be triggered when the best cell changes.

Dependency


None


None

Dependency on UE

The UE must comply with 3GPP Release 8 or later and support UMTS-to-LTE PS handovers

and LTE measurement.


The eNodeB and MME must support UMTS-to-LTE PS handovers.





72

The SGSN must support UMTS-to-LTE PS handovers.


None

2.38 WRFD-140219 Micro NodeB Self-Planning

Availability


Summary

This feature automatically plans the following information for micro NodeBs:

� Available UTRA Absolute Radio Frequency Channel Numbers (UARFCNs)

� Scrambling codes

� Intra-frequency neighboring cells

� Inter-frequency neighboring cells

� Inter-RAT neighboring cells between UMTS and GSM,

� Inter-RAT neighboring cells between UMTS and LTE,

� LAC/SAC/RAC/URA parameters

Benefits

With this feature, the system automatically scans the radio environment around a micro

NodeB and sets the radio parameters such as UARFCNs and scrambling codes. This feature

simplifies micro NodeB network planning while also making it more efficient and reducing

the cost.

Description

Network planning is mandatory for WCDMA network deployment. WCDMA network

planning, including site survey and network dimensioning, is generally performed manually,

which results in a high cost and a lengthy deployment schedule.

To improve network planning efficiency and meet the customers' requirements of automatic

micro NodeB deployment, this feature automatically determines available UARFCNs,

scrambling codes, intra-frequency neighboring cells, inter-frequency neighboring cells,

inter-RAT neighboring cells between UMTS and GSM, inter-RAT neighboring cells between

UMTS and LTE, and LAC/SAC/RAC/URA parameters for micro NodeBs. With this feature,

the system automatically performs the following functions:

� Scans the radio environment around a micro NodeB to collect raw data.

� Sets radio parameters by using radio parameter planning algorithms.

� Configures radio parameters on network elements (NEs) through the operation and

maintenance (O&M) channel.




73

Enhancement

In RAN15.0, the following functions are added:

1. Self-planning for micro NodeB of dual-carrier.

2. Automatic planning of camping, mobility and load control parameters.

3. Automatic planning of inter-RAT neighboring cells between UMTS and LTE and URA

parameters.

Dependency


The RNC version must be RAN13.0 or later, and the RNC data can be configured and

modified on the M2000.


Only the BTS3902E supports this feature.

The BTS3902E must be configured with a self-organizing network (SON) receiver and a SON

receiver antenna.

Dependency on UE

None


� The NodeB auto deployment function is enabled on the M2000 side.

� The M2000 must support BTS3902E WCDMA self-planning.

� The GBSC version must be GBSS 14.0 or later to support remote configuration by the

M2000.


None


� WRFD-031101 NodeB Self-Discovery Based on IP Route

� WRFD-031102 NodeB Remote Self-configuration

RAN15.0 New and Enhanced Feature Description 3 Try Features



74

3 Try Features 3.1 WRFD-150223 4C-HSDPA+MIMO

Availability


Summary

4C-HSDPA+MIMO uses a maximum of four carriers enabled with MIMO+64QAM for the

HSDPA transmission of a UE, which increases the UE data rate and system capacity.

Benefits

This feature improves spectral efficiency to achieve the following benefits:

� Increased UE data rate

Compared with 4C-HSDPA, 4C-HSDPA+MIMO produces a spatial multiplexing gain

and increases the single-user peak rate from 84 Mbit/s to 168 Mbit/s.

Compared with single-carrier MIMO, 4C-HSDPA+MIMO increases the UE data rate by

a maximum of 300%.

� Increased cell capacity

Compared with 4C-HSDPA, 4C-HSDPA+MIMO improves the spectral efficiency of the

20 MHz bandwidth and improves system throughput by about 7% according to

simulation results.

Description

This feature was first specified by 3GPP Release 10. It allows a combination of 4C-HSDPA

and MIMO+64QAM, that is, a UE can set up HSDPA connections with three or four carriers

that are enabled with MIMO+64QAM. In the downlink, the UE simultaneously receives data

from different carriers, increasing the single-user throughput.

The following figure shows the basic principles of this feature.




75

NodeB

F 1

F 2

UEBand a

DL: DPCH/F-DPCH

UL: DCCH/HS-DPCCH

HS-DSCH (with or without MIMO) Primary carrier

F3

HS-DSCH (with or without MIMO) Secondary carrier 1



Band b

F 4

In the uplink, the UE uses DCH, HSUPA, or DC-HSUPA. The SRB for the UE is carried over

DCH or HSDPA.

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.

This feature applies to PS BE services, streaming services, and combined services that include

PS BE or streaming services.

This feature 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.

Enhancement

None

Dependency


None


Only the 3900 series base stations (excluding the BTS3902E) support this feature and the

3900 series base stations must be configured with the WBBPd or WBBPf board.

Dependency on UEs

The UEs must belong to HSDPA category 30 or 32.


� WRFD-150207 4C-HSDPA

� WRFD-010693 DL 64QAM+MIMO

� WRFD-150227 DB-HSDPA+MIMO

In a cell group that uses 4C-HSDPA+MIMO, if one cell in the group operates at a

different frequency band from other cells, all cells in the group must support

DB-HSDPA+MIMO.

� WRFD-010699 DC-HSDPA+MIMO




76

In a cell group that uses 4C-HSDPA+MIMO, if multiple cells in the group operate at the

same frequency band, all these cells must support DC-HSDPA+MIMO.

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

Availability


Summary

This feature uses four-carrier High Speed Downlink Packet Access (4C-HSDPA) and

multiple-input multiple-output (MIMO) to increase the maximum downlink single-user data

rate to 168 Mbit/s.

Benefits

This feature provides high speed data services for UEs.

Description

3GPP Release 10 defined 4C-HSDPA+MIMO, which allowed the combination of

64QAM+MIMO and 4C-HSDPA. If four carriers are aggregated in the downlink and each of

them uses 64QAM+MIMO, the maximum downlink single-user data rate can reach 168

Mbit/s.

Enhancement

None

Dependency


� The BSC6900 user plane needs the support from the DPUe board.

� The BSC6900 interface board must be GOUa, GOUc, FG2a (GE port), or FG2c (GE

port).

� The BSC6910 interface board must be GOUc, FG2c, or EXOUa.


� The BTS3812E/BTS3812AE and DBS3800 do not support this feature.


WBBPf board to support this feature.

Dependency on UEs

The UEs must comply with 3GPP Release 10 and belong to category 32.


None




77


The CN must comply with 3GPP Release 7, which allows a maximum downlink data rate

of168 Mbit/s.


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

� WRFD-150223 4C-HSDPA+MIMO

� WRFD-010614 HSUPA Phase 2

3.3 WRFD-150225 HSUPA Scheduling Based on UE Location

Availability


Summary

This feature lowers the scheduling priority index (SPI) weight of HSUPA UEs performing

best effort (BE) services in soft handover state to increase spectral efficiency and uplink cell

capacity.

Benefits

Based on the full buffer traffic model, this feature increases cell capacity by 2% to 7% when

the soft handover area occupies approximately 30% of the total coverage area.

Description

In most cases, HSUPA UEs performing BE services in soft handover (excluding softer

handover) state are located at the cell edge. This feature lowers the SPI weight of these UEs

so that they are less likely to be scheduled in the soft handover area. This reduces the uplink

interference of these UEs on cells and saves uplink Uu resources for cell center users (CCUs).

Therefore, the total uplink cell capacity is increased.

Enabling this feature adversely affects the WRFD-020806 Differentiated Service Based on

SPI Weight feature. Operators can set parameters to ensure that the performance of gold and

platinum users in soft handover areas is not affected.

Gains produced by this feature are noticeable in large soft handover areas with high received

total wideband power (RTWP).

Enhancement

None

Dependency





78

None


� The BTS3812E, BTS3812A, and BTS3812AE must be configured with the EULPd,

EBBI, EBOI, or EULP board. Downlink services must be established on the EULPd,

EBBI, EBOI, or EULP board.

� The DBS3800 must be configured with the EBBC or EBBCd board. Downlink services

must be established on the EBBC or EBBCd board.

� The 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.

Dependency on UEs

None


None


None


� WRFD-010612 HSUPA Introduction Package

� WRFD-020806 Differentiated Service Based on SPI Weight

3.4 WRFD-150227 DB-HSDPA+MIMO

Availability


Summary

DB-HSDPA+MIMO was 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 to simultaneously transmit HSDPA data to UEs.

Benefits

This feature improves spectral efficiency to achieve the following benefits:

� Increased single-user peak rate

Compared with DB-HSDPA, DB-HSDPA+MIMO produces a spatial multiplexing gain and

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




79

Compared with single-carrier MIMO, DB-HSDPA+MIMO uses the resources of two carriers

to 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 throughput for cell edge users

Compared with DB-HSDPA, DB-HSDPA+MIMO produces a performance gain of

closed-loop transmit diversity at the cell edge.

Compared with single-carrier MIMO, DB-HSDPA+MIMO uses the resources of two carriers

to double the data rate for cell edge users.

� Increased cell capacity

Compared with DB-HSDPA, DC-HSDPA+MIMO improves spectral efficiency for carriers on

two different frequency bands. According to simulation results, system throughput can be

improved by about 10%-20%.

Description

The following figure shows the basic principles of this feature.

NodeB

F 1

F 2

UE

Primary Carrier

Secondary Carrier

HS-DSCH with MIMO (w/wo 64QAM)

DL:DPCH/F-DPCH

UL:DCCH,HS-DPCCH


NodeBNodeB

F 1

F 2

UEUE

Primary Carrier

Secondary Carrier


DL:DPCH/F-DPCH

UL:DCCH,HS-DPCCH


This feature integrates DB-HSDPA and MIMO and obtains the technical advantages of the

two techniques.

In RAN15.0, this feature supports the following configurations:

� If only one carrier is configured to support MIMO, the theoretical peak rate is 63 Mbit/s.

� If both carriers are configured to support MIMO, the theoretical peak rate is 84 Mbit/s.

This feature is recommended for PS streaming services and BE services, which have a large

amount of data to transmit.

This feature uses the same load control and mobility management principles as DB-HSDPA.

Enhancement

None

Dependency





80

None


� The DBS3800 must be configured with the EBBC or EBBCd board to support this

feature.

� The BTS3900/BTS3900A, DBS3900, and BTS3900C must be configured with the

WBBPb, WBBPd, or WBBPf board to support this feature.

� The BTS3812E, BTS3812A, BTS3812AE, iDBS3900, and BTS3902E do not support

this feature.

Dependency on UEs

The UEs must support inter-band DB-HSDPA and belong to HS-DSCH category 25, 26, 27,

28, 30, 32, 34, or 36.


None


None


� WRFD- 150209 DB-HSDPA

� WRFD-010684 2x2 MIMO

3.5 WRFD-150230 Load Based DPCH Power Saving

Availability


Summary

When traffic is heavy on downlink R99 channels in a cell, this feature reduces the transmit

power on downlink dedicated physical channels (DPCHs) allocated to new users. This

increases the number of online users on the downlink or the HSDPA throughput.

Benefits

In a heavily loaded cell, this feature reduces the transmit power on the downlink DPCH by

approximately 20% for new users initiating PS services and by approximately 5% for new

users initiating CS services. This reduces the total transmit power on downlink R99 channels

in the cell. The amount of total transmit power reduced is related to the number of online

users and the proportion of different service types they use.

Description

The timeslot format of downlink DPCHs consists of data and control fields. The control field

contains pilot bits, which are used for channel estimation and radio link

out-of-synchronization decisions. Generally, pilot bits can be received if the transmit power

RAN15.0 New and Enhanced Feature Description 4 Notes



81

for pilot bits is the same as that for data bits. If the transmit power for pilot bits is set higher

than that for data bits, channel estimation and radio link out-of-synchronization decisions

become more accurate.

Without this feature, when a cell has light traffic, the transmit power for pilot bits and the

number of pilot bits can be set to large values to increase the synchronization probability.

However, if there are a large number of online users, downlink R99 channels consume a large

amount of power. As a result, new users cannot be admitted or HSDPA throughput will be low

due to downlink power congestion.

To solve this problem, this feature reduces the transmit power for pilot bits and the number of

pilot bits, thereby reducing the transmit power on DPCHs. This increases the DPCH power

usage to admit more new users or enhances the HSDPA throughput.

Gains produced by this feature are noticeable in cells with a large number of online users.

Enhancement

None

Dependency


None


None


None


None

4 Notes

The try features mean no need to pay for their license fee in this version, when in next version,

if the try features are change to optional feature, then the license fee for them is needed.

Customers need to sign a paper of MOU to agree the organization as above.

Documents

RAN15 New and Enhnced feature list