huawei dc-hsdpa(ran13.0_02).pdf

7/14/2019 Huawei DC-HSDPA(RAN13.0_02).PDF

http://slidepdf.com/reader/full/huawei-dc-hsdparan13002pdf 1/39

DC-HSDPARAN13.0

Feature Parameter Description

Issue 02

Date 2011-06-30

HUAWEI TECHNOLOGIES CO., LTD.



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

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

written consent of Huawei Technologies Co., Ltd.

Trademarks and Permissions

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

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

holders.

Notice

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

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

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

information, and recommendations in this document are provided "AS IS" without warranties, guarantees or representations of any kind, either express or implied.

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

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

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

Huawei Technologies Co., Ltd.

Address: Huawei Industrial Base

Bantian, Longgang

Shenzhen 518129

People's Republic of China

Website: http://www.huawei.com

Email: [email protected]

http://www.huawei.com/


mailto:[email protected]






WCDMA RAN

DC-HSDPA Contents

Issue 02 (2011-06-30) Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd

ii

Contents

1 Introduction ................................................................................................................................ 1-1 1.1 Scope ............................................................................................................................................ 1-1 1.2 Intended Audience ........................................................................................................................ 1-1 1.3 Change History .............................................................................................................................. 1-1

2 Overview ..................................................................................................................................... 2-1 3 Basic Principle........................................................................................................................... 3-1

3.1 Overview ....................................................................................................................................... 3-1 3.2 Cell Configuration .......................................................................................................................... 3-1 3.3 Channel Mapping .......................................................................................................................... 3-3 3.4 UE Categories ............................................................................................................................... 3-3 3.5 NodeB MAC-ehs ........................................................................................................................... 3-4 3.6 Impact on Interfaces ...................................................................................................................... 3-5

4 Technical Description .............................................................................................................. 4-1 4.1 Overview ....................................................................................................................................... 4-1 4.2 Radio Bearers ............................................................................................................................... 4-1 4.3 State Transition .............................................................................................................................. 4-2 4.4 Mobility Management .................................................................................................................... 4-2 4.5 Load Control .................................................................................................................................. 4-4

4.5.1 RAB DRD ............................................................................................................................. 4-4 4.5.2 Call Admission Control ......................................................................................................... 4-5 4.5.3 Queuing and Preemption...................................................................................................... 4-6 4.5.4 Load Reshuffling and Overload Control ............................................................................... 4-7

4.6 Scheduling ..................................................................................................................................... 4-7 4.7 Activating or Deactivating Secondary Cell .................................................................................... 4-7

5 Engineering Guidelines........................................................................................................... 5-1 5.1 DC-HSDPA .................................................................................................................................... 5-1

5.1.1 When to Use DC-HSDPA ..................................................................................................... 5-1 5.1.2 Factors to Consider During Feature Deployment ................................................................. 5-1 5.1.3 Recommended Settings for Key Parameters ....................................................................... 5-1 5.1.4 Feature Monitoring ............................................................................................................... 5-2

5.2 Activating or Deactivating Secondary Cell .................................................................................... 5-2 6 Parameters ................................................................................................................................. 6-1 7 Counters...................................................................................................................................... 7-1 8 Glossary ...................................................................................................................................... 8-1 9 Reference Documents ............................................................................................................. 9-1



WCDMA RAN

DC-HSDPA 1 Introduction



1-1

1 Introduction

1.1 Scope

This document describes the feature Dual-Carrier High Speed Downlink Packet Access (WRFD-010696DC-HSDPA).

Before reading this document, you are advised to read the HSDPA Feature Parameter Description.

1.2 Intended Audience

This document is intended for:

Personnel who are familiar with WCDMA basics

Personnel who need to understand DC-HSDPA

Personnel who work with Huawei products

1.3 Change History

This section provides information on the changes in different document versions.

There are two types of changes, which are defined as follows:

Feature change: refers to the change in the DC-HSDPA feature.

Editorial change: refers to the change in wording or the addition of the information that was notdescribed in the earlier version.

Document Issues

The document issues are as follows:

02 (2011-06-30)

01 (2011-04-30)

Draft B (2011-03-30)

Draft A (2010-12-30)

02 (2011-06-30)

This is the document for the second commercial release of RAN13.0.

Compared with issue 01 (2011-04-30) of RAN13.0, this issue has the following changes.

Change Type Change Description Parameter Change

Feature change None. None.

Editorial change The engineering guideline about DC-HSDPA isadded. For details, see 5.1 “DC-HSDPA.”

None.

The engineering guideline about activating or deactivating secondary cell moved from 4.7

“ Activating or Deactivating Secondary Cell” to 5.2

“ Activating or Deactivating Secondary Cell.”

None.

http://localhost/var/www/apps/conversion/tmp/scratch_8/HSDPA.htm






WCDMA RAN

DC-HSDPA 1 Introduction



1-2

01 (2011-04-30)

This is the document for the first commercial release of RAN13.0.

Compared with issue Draft B (2011-03-30) of RAN13.0, this issue has no change.

Draft B (2011-03-30)

This is the draft of the document for RAN13.0.

Compared with issue Draft A (2010-12-30) of RAN13.0, this issue optimizes the information aboutactivating or deactivating secondary cell. For details, see 4.7 “ Activating or Deactivating SecondaryCell.”

Draft A (2010-12-30)

This is the draft of the document for RAN13.0.

Compared with issue 01 (2010-03-30) of RAN12.0, this issue adds the information about activating or

deactivating secondary cell. For details, see 4.7 “ Activating or Deactivating Secondary Cell.”



WCDMA RAN

DC-HSDPA 2 Overview



2-1

2 Overview

Similar to Long Term Evolution (LTE), the HSPA technology is also influenced by the multi-carrier aggregations. The performance and throughput of HSPA can be improved by using more bandwidth

provided by multi-carriers. The throughput of end users can be double or more as compared tosingle-carrier HSPA.

In 3GPP Release 8 or earlier, only a single carrier can be used for the HSDPA transmission of a UE. Thesingle carrier HSDPA is hereafter referred to as SC-HSDPA.

The first phase of Multi-Carrier HSPA (MC-HSPA) based on 3GPP R8 Technical Specifications (TSs)uses two consecutive carriers in the downlink to transmit data for one subscriber, which is named DualCarrier HSDPA (DC-HSDPA). 3GPP Release or later specifies the use of more than two carriers for asingle subscriber without the restrictions on the use of the same frequency band.

Figure 2-1 shows the 3GPP evolution of MC-HSDPA.

Figure 2-1 3GPP evolution of MC-HSDPA

The requirements of DC-HSDPA are listed in Table 2-1.

Table 2-1 Requirements of the DC-HSDPA

Item Requirement

CN The CN needs to support the downlink peak rate of 42 Mbit/s provided by downlink DC-HSDPA

with 64QAM.

RNC The RNC needs to support downlink enhanced L2.

The RNC provides the radio bearer scheme for DC-HSDPA.

NodeB DC-HSDPA requires NodeB to support MAC-ehs. A single MAC-ehs entity supports HS-DSCHtransmission in more than one cell served by the same Node-B (FDD only).

UE The UE can monitor a maximum of six HS-SCCHs in the two cells of DC-HSDPA. In each cell,the UE can monitor a maximum of three HS-SCCHs at the same time.

In 3GPP Release 8, HS-DSCH UE categories 21, 22, 23, and 24 are added to supportDC-HSDPA. In 3GPP Release 9 or later, more HS-DSCH UE categories support DC-HSDPA.



WCDMA RAN

DC-HSDPA 3 Basic Principle



3-1

3 Basic Principle

3.1 Overview

DC-HSDPA allows a UE to set up HSDPA connections with two inter-frequency synchronous cells thathave the same coverage. In the downlink, the UE can receive different data through HS-DSCHs from thetwo cells simultaneously. In the uplink, however, the UE sends data only through its primary cell.

Figure 3-1 DC-HSDPA principle

The two cells (primary cell and secondary cell) of DC-HSDPA follow the following restrictions:

The two cells belong to the same sector of a NodeB and are inter-frequency same-coverage cells.

The two cells are in the same downlink resource group of a NodeB.

The two cells operate on adjacent carriers with a frequency spacing less than or equal to 5 MHz in thesame frequency band.

The two cells have the same timing (Tcell).

The two cells support HSDPA and enhanced L2.

The two cells belong to the same operator. The dual cell transmission only applies to HSDPA physical channels.

The uplink of DC-HSDPA UE is in only the primary cell but not in the secondary cell.

DC-HSDPA improves the throughput and QoS of end users in the whole cell area even on the cell edges.Theoretically, DC-HSDPA with 64QAM can provide a peak rate of 42 Mbit/s in the downlink. This ratedoubles the peak rate provided by only 64QAM.

3.2 Cell Configuration

DC-HSDPA cell group consists of two cells: primary cell and secondary cell.

From the UE perspective:



WCDMA RAN




3-2

Primary cell (also called anchor cell) carries all the types of channel for a UE. Each UE has only oneprimary cell.

Secondary cell (also called supplementary cell) carries only three types of downlink (DL) channel for aUE. Each UE has only one secondary cell.

The three types of DL channel are as follows:− High-speed shared control channel (HS-SCCH)

− High-speed physical downlink shared channel (HS-PDSCH)

− Primary common pilot channel (P-CPICH)

Figure 3-2 shows the physical channels involved in DC-HSDPA for a UE.

Figure 3-2 Cell configuration from the UE perspective

From the RAN perspective, both the cells can work as primary cell and secondary cell. The two cells canbe deployed equivalently with the same configuration, as shown in Figure 3-3.

Figure 3-3 Equivalent deployment of primary cell and secondary cell

In equivalent deployment of primary and secondary cells, the RNC selects the primary cell for UEsbased on the load and radio bearer scheme. Both cells can work independently for non-DC-HSDPA UEsor legacy HSDPA UEs.

Alternatively, the primary cell is configured with all channels whereas the secondary cell is configuredwith only HS-DSCH and P-CPICH. The secondary cell cannot work independently. This is callednon-equivalent deployment. Non-equivalent deployment is not supported.



WCDMA RAN




3-3

3.3 Channel Mapping

Overview

Figure 3-4 Channel mapping of DC-HSDPA

A DC-HSDPA UE receives two HS-DSCH transport channels from two cells of the same NodeB. EachHS-DSCH is mapped to one HS-SCCH and several HS-PDSCH physical channels.

The uplink DCH or E-DCH of DC-HSDPA is carried only on the primary cell.

All dedicated physical control channels DPCCH and DPCH/F-DPCH in the uplink and downlink arecarried on the primary cell.

HS-SCCH

In 3GPP Release 8 or earlier, a UE can monitor a maximum of four HS-SCCHs at the same time,according to 3GPP TS 25.331. In DC-HSDPA cell group, the HS-SCCHs on the primary cell areindependent of those on the secondary cell. A UE can monitor a maximum of six HS-SCCHs at the sametime. In each cell, the UE can monitor a maximum of three HS-SCCHs at the same time.

There are three types of HS-SCCH, type 1 for common use, type 2 for HS-SCCH Less Operation, andtype 3 for MIMO. DC-HSDPA uses only HS-SCCH type 1. DC-HSDPA with HS-SCCH Less Operationuses HS-SCCH type 2.

HS-SCCH Less Operation applies only to the primary cell.

HS-DPCCH

The UE gives feedback on the CQIs and HARQ ACK/NACK about two cells on the HS-DPCCH channelto the primary cell. The HS-DPCCH uses a new frame format that enables it to carry CQI and HARQ ACK/NACK information of the two cells in a Transmission Time Interval (TTI).

3.4 UE Categories

In 3GPP Release 8, HS-DSCH UE categories 21, 22, 23, and 24 are added to support DC-HSDPA, aslisted in Table 3-1 (similar to that in 3GPP TS 25.306). In 3GPP Release 9 or later, more HS-DSCH UEcategories support DC-HSDPA.



WCDMA RAN




3-4

Table 3-1 FDD HS-DSCH physical layer categories 21 to 24

HS-DSCHCategory

MaximumNumber

of HS-DSCHCodesReceived

MinimumInter-TTIInterval

MaximumNumber of Bits of an

HS-DSCHTransportBlockReceivedWithin

an HS-DSCHTTI

TotalNumber of Soft

ChannelBits

SupportedModulation Without

MIMOOperationor DualCellOperation

SupportedModulationSimultaneo

us withMIMOOperationandWithoutDual CellOperation

SupportedModul

ationwithDualCellOperation

Category 21 15 1 23370 345600

- -

QPSK,16QAMCategory 22 15 1 27952 345600

Category 23 15 1 35280 518400 QPSK,16QAM,64Q AM

Category 24 15 1 42192 518400

The requirements for the UEs of different HS-DSCH categories when DC-HSDPA is not configured areas follows:

The UE of HS-DSCH category 21 needs to support at least one of the HS-DSCH categories 9, 10, 13,14, 15, 16, 17, and 18.

The UE of HS-DSCH category 22 needs to support at least one of the HS-DSCH categories 10, 14, 16,

and 18. The UE of HS-DSCH category 23 needs to support at least one of the HS-DSCH categories 13, 14, 17,

18, 19, and 20.

The UE of HS-DSCH category 24 needs to support at least one of the HS-DSCH categories 14, 18,and 20.

The peak rate can reach 42.192 Mbit/s (= 2 x TB_Size/TTI = 2 x 42192/2) at the MAC layer, supportedby the CN.

The DC-HSDPA UEs and MIMO UEs can co-exist in the same cell, but one UE cannot use MIMO andDC-HSDPA together.

3.5 NodeB MAC-ehsDC-HSDPA requires the NodeB to support MAC-ehs. A single MAC-ehs entity supports HS-DSCHtransmission in more than one cell served by the same NodeB (FDD only). Queues of a DC-HSDPA UEare common for the two cells. The scheduler in the NodeB arranges the data transmission of queues onthe two cells. DC-HSDPA transmissions can be regarded as independent transmissions over twoHS-DSCH channels. There will be a separate HARQ entity on each HS-DSCH channel, that is, oneHARQ process per TTI for single carrier transmission and two HARQ processes per TTI for dual carrier transmission.

MAC-ehs selects Transport Format and Resource Combination (TFRC) for the MAC-ehs Protocol DataUnits (PDUs) of each cell independently based on the available resources of the cells and the CQIreported by the UE.



WCDMA RAN




3-5

Figure 3-5 MAC-ehs architecture

In a NodeB, two MAC-ehs PDUs can be scheduled at the same time. Figure 3-6 shows an example of traffic flow to a DC-HSDPA UE.

Figure 3-6 Example of traffic flow to a DC-HSDPA UE

3.6 Impact on Interfaces

To support DC-HSDPA, new Information Elements (IEs) are added to signaling messages.

UEs and cells can report their capacity of DC-HSDPA to the RNC through the Iub and Uu interfaces. TheRNC instructs cells to set up or reconfigure radio links with DC-HSDPA through the Iub interface. TheRNC instructs UEs to set up or reconfigure radio bearers with DC-HSDPA through the Uu interface.



WCDMA RAN




3-6

Impact on Iub

When a cell receives the AUDIT REQUEST message or when a new cell is set up or a cell capability ischanged, the NodeB reports the cell capability to the RNC in Audit Response message or ResourceState Indication message

When a cell supports DC-HSDPA, the NodeB sets the Multi Cell Capability Info IE to Multi CellCapable for the cell in Audit Response and sends the message to the RNC.

If the cell is a primary serving cell, all the possible secondary serving cells in the same sector must belisted in the Possible Secondary Cell List IE.

When the RNC instructs a cell to set up a radio link with DC-HSDPA, the information of the secondaryserving cell is added to the Radio Link Setup procedure or Radio Link Addition procedure.

The Additional HS Cell Information RL Setup IE is added to the Radio Link SetupRequest/Response/Failure messages and Radio Link Addition Request/Response/Failure messages toindicate the usage of DC-HSDPA and associated parameters.

Impact on UuIn the RRC CONNECTION REQUEST message, the Multi cell support IE is added to indicate the UEcapability of supporting multiple cells.

In the RRC Connection Setup Complete and UE Capability Information message, the Physical ChannelCapability IE is extended to indicate the UE capability of DC-HSDPA.

The Downlink secondary cell info FDD IE in the following signaling messages indicates the usage of secondary serving cell and related parameters:

RRC CONNECTION SETUP

ACTIVE SET UPDATE

CELL UPDATE CONFIRM PHYSICAL CHANNEL RECONFIGURATION

TRANSPORT CHANNEL RECONFIGURATION

RADIO BEARER RECONFIGURATION

RADIO BEARER RELEASE

RADIO BEARER SETUP



WCDMA RAN

DC-HSDPA 4 Technical Description



4-1

4 Technical Description

4.1 Overview

This document describes only the functions that are different from those of SC-HSDPA.

These functions are as follows:

Radio Bearers

State transition

Mobility management

Load control

Scheduling

For details about other functions, see the HSDPA Feature Parameter Description.

4.2 Radio BearersWhen the downlink transport channel HS-DSCH is selected for streaming or BE services or combinedservice with streaming or BE, DC-HSDPA is applied. When there is only a CS service, PS conversationalservice, IMS signaling, or SRB signaling, DC-HSDPA is not applied because of small traffic volume andlow transmission delay.

Before using DC-HSDPA for a service, you need to configure the feature on both RNC and NodeB.

On the NodeB:

− You need to set up two cells to support DC-HSDPA. The two cells operate on adjacent carriers with afrequency spacing of 5 MHz or smaller in the same frequency band. The two carriers are specified byfrequency channel numbers (DLFREQ / ULFREQ ).

− The two cells are configured as a DC-HSDPA group (ADD DUALCELLGRP). The two cells arespecified by the parameters (FIRSTLOCELL, SECONDLOCELL).

On the RNC:

− You need to turn on the switches CfgSwitch : CFG_HSDPA_DC_SWITCH and HspaPlusSwitch : DC_HSDPA.

− The preferred feature should be set to DC_HSDPA in the parameter MIMO64QAMorDcHSDPASwitch .

− The timing (Tcell ) of the two cells needs to be set to the same value.

64QAM can be enabled in one or both cells in the DC-HSDPA cell group. DC-HSDPA and 64QAM canbe used at the same time.

The Continuous Packet Connectivity (CPC) function can be enabled in the DC-HSDPA cells with thefollowing limitations:

CPC DTX is applicable to primary cell only because there will be no uplink control channel for theDC-HSDPA UE on secondary cell

CPC HS-SCCH Less Operation is applicable to primary cell only and is not applicable to secondarycell.

CPC DRX for a DC-HSDPA UE on two carriers is similar to that for a UE on a single cell.

HSPA+ based on 3GPP Release 8 is optional for the operators to select DC-HSDPA or MIMO. However,in later 3GPP releases, the DC-HSDPA and MIMO should be deployed together.




http://localhost/var/www/apps/conversion/tmp/NodeBParaHtml/mml-mo-para/para/LOCELL-DlFreqNo.html



http://localhost/var/www/apps/conversion/tmp/NodeBParaHtml/mml-mo-para/para/LOCELL-UlFreqNo.html



http://localhost/var/www/apps/conversion/tmp/NodeBParaHtml/mml-mo-para/para/DUALCELLGRP-ulFirstLocalCellId.html



http://localhost/var/www/apps/conversion/tmp/NodeBParaHtml/mml-mo-para/para/DUALCELLGRP-ulSecondLocalCellId.html



http://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/ucorrmalgoswitch_cfgswitch.html



http://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/ucellalgoswitch_hspaplusswitch.html



http://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/ufrc_mimo64qamordchsdpaswitch.html


http://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/ucell_tcell.html














WCDMA RAN




4-2

In RAN12.0, a cell is enabled with the DC-HSDPA and MIMO functions at the same time but a UE canuse only one of the functions.

In RAN12.0, the two cells in a DC-HSDPA cell group cannot support MIMO at the same time. Only oneof them can support MIMO.

In RAN13.0, a cell is enabled with the DC-HSDPA and MIMO functions at the same time and both cellsin a DC-HSDPA cell group can support MIMO at the same time.

DC-HSDPA with 64QAM can reach a peak rate of 42 Mbit/s.

The Transmission Control Protocol (TCP) is widely used in data transmission. When a file is beingdownloaded, the TCP acknowledgement is sent in the uplink. The higher the rate of download is, thelarger the bandwidth is required in the uplink. If the download rate reaches up to 42 Mbit/s, the uplinkrate of TCP acknowledgement is much higher than 384 kbit/s, the highest supported by the DCH.HSUPA bearer is required to provide high bandwidth in the uplink to transmit TCP acknowledgementwithout delay. The downlink rate of 42 Mbit/s per user can be supported only when HSUPA is used.

4.3 State Transition

DC-HSDPA state transition, based on the SC-HSDPA state transition strategy, considers the primary cellduring state transition.

Assume that a DC-HSDPA UE preferentially selects F2 as the primary cell. Then, the DC-HSDPA statetransition strategy is as follows:

To move from the CELL_FACH, CELL_PCH, or URA_PCH state to the CELL_DCH state:

1. If the UE is allowed to access the F2 cell, the UE moves to the CELL_DCH state in this cell.

2. If the UE is not allowed to access the F2 cell, the UE attempts to access other DC-HSDPA cells in aDRD candidate cell set.

3. If the UE is allowed to access one of the candidate cells, the UE moves to the CELL_DCH state in

this cell.

4. If the UE is not allowed to access any of the candidate cells, the UE performs the followingoperations:

− If the UL service is carried on the HSUPA channel, the UL falls back to DCH:

If the UE is allowed to access the cell, the UE moves to the CELL_DCH state.

If the UE is not allowed to access the cell, the state transition fails and the UE stays in the originalstate.

− If the UL service is carried on the DCH, the state transition fails and the UE stays in the original state.

To move from the CELL_DCH state to the CELL_FACH state, the DC-HSDPA UE performs the samestate transition as an SC-HSDPA UE in the primary-carrier cell.

To move from the CELL_FACH state to the CELL_PCH state, the DC-HSDPA UE performs the samestate transition as an SC-HSDPA UE because the DC-HSDPA UE in the CELL_FACH state can use onlyone frequency.

4.4 Mobility Management

The introduction of DC-HSDPA has no impact on handover measurement triggering and handover decision processes. During a handover, however, the RNC needs to decide whether DC-HSDPA is usedafter the handover if the target cell supports DC-HSDPA, or whether non-DC-HSDPA is used after thehandover if the target cell does not support DC-HSDPA.

This section describes only the mobility management of DC-HSDPA. For other information about

handover, see the Handover Feature Parameter Description.

http://localhost/var/www/apps/conversion/tmp/scratch_8/Handover.htm






WCDMA RAN




4-3

Measurement Control

The active set is maintained for primary carriers only. For DC-HSDPA intra-frequency handover, only thesignal quality of the primary-carrier cell and its neighboring cells needs to be measured.

For DC-HSDPA inter-frequency handover, except for the signal quality of the primary-carrier cell and itsneighboring cells, the signal quality of the secondary-carrier cell also needs to be measured like aninter-frequency neighboring cell.

If the UE has a dual-frequency receiver, it can perform inter-frequency measurement without starting thecompressed mode if all of the following conditions are met:

The CmpSwi tch : CMP_UU_ADJACENT_FREQ_CM_SWITCH is turned on.

The value of the IE "Adjacent frequency measurements without compressed mode" reported by theUE is TRUE.

For the UE that supports DC-HSDPA:

− If the UE has a DC-HSDPA service, all the cells involved in inter-frequency measurement are at the

same frequency as the secondary carrier.− If the UE does not have a DC-HSDPA service, all the cells involved in inter-frequency measurementare at the same frequency, with a 5 MHz spacing from the current cell but within the same band asthe current cell.

Handover Between DC-HSDPA Cells

When receiving a measurement report indicating that the signal quality of a DC-HSDPA cell is better thanthat of the serving cell (a DC-HSDPA cell), the RNC decides whether to perform a DC-HSDPA handover to the target cell:

If the admission to the target cell is allowed and the radio link configuration is successful, the RNCperforms the handover.

If the admission to the target cell is allowed but the radio link configuration is unsuccessful, the RNCreconfigures the service on SC-HSDPA and then performs an SC-HSDPA handover.

If the admission to the target cell is not allowed, the RNC reconfigures the service on the DCH andperforms a DCH handover:

− If the DCH handover is allowed, the RNC performs the handover.

− Otherwise, the RNC does not perform the handover.

Handover from a DC-HSDPA Cell to a Non-DC-HSDPA Cell

When receiving a measurement report indicating that the signal quality of a non-DC-HSDPA cell is better than that of the serving cell (a DC-HSDPA cell), the RNC reconfigures the service to DCH or HSDPA and

continues to perform the handover procedure.

Handover from a Non-DC-HSDPA Cell to a DC-HSDPA Cell

When receiving a measurement report indicating that the signal quality of a DC-HSDPA cell is better thanthat of the serving cell (a non-HSDPA cell), the RNC performs a handover after which the HSPA+technologies supported by both the source cell and the target cell are used in the target cell. If suchHSPA+ technologies are ranked lower than some HSPA+ technologies supported by both the target celland the UE, the ChannelRetryHoTimerLen timer is started after the handover. When the timer expires,the RNC tries to reconfigure the traffic radio bearer (TRB) and signaling radio bearer (SRB) to enablethem to support the higher-ranked HSPA+ technologies.

http://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/ucorrmalgoswitch_cmpswitch.html



http://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/ucoiftimer_channelretryhotimerlen.html







WCDMA RAN




4-4

4.5 Load Control

4.5.1 RAB DRD

During the RB setup or state transition from CELL_FACH to CELL_DCH, the RNC makes DRDs toselect a DC-HSDPA cell group and then select a primary-carrier cell for the UE.

For details about DRD, see Directed Retry Decision Feature Parameter Description.

DRD Procedure

The procedure is as follows:

1. The RNC selects a set of candidate cells that meet the DRD quality requirements.

For details, see the Directed Retry Decision Feature Parameter Description.

2. The RNC selects a DC-HSDPA cell group according to the HSPA+ technological satisfaction.

The RNC selects a cell with the highest priority as the target cell according to the HSPA+ technological

satisfaction. Based on this cell, the RNC searches for the corresponding DC-HSPA cell group andtakes this group as the DC-HSPA cell group, and go to step 4. If there are multiple DC-HSPA cellgroups with the same HSPA+ technological satisfaction, the RNC performs step 3.

3. The RNC selects a DC-HSDPA cell group as follows:

If the parameter ServiceDif fDrdSwitch is on, the RNC selects a group with the highest servicepriority.

For details, see section "Cell Group Selection Based on Service Priorities."

If there are multiple DC-HSDPA cell groups with the same highest service priority, the RNC selects agroup based on DL load balancing between these groups.

4. The RNC selects a primary-carrier cell from the DC-HSDPA cell group as follows:

The RNC selects a primary-carrier according to HSPA+ technological satisfaction and cell servicepriority. If all the HSPA+ technological satisfaction, cell service priority and downlink load of the twocells are the same, the RNC performs the following steps:

a) If the ULLdbDRDSwitchDcHSDPA switch is turned on, the RNC selects a primary-carrier cellbased on UL load balancing between the two cells. For details, see section "Cell Selection Based onUL Load."

b) If the ULLdbDRDSwitchDcHSDPA switch is turned off, the RNC selects the cell randomly.

5. If the directed retry fails, the RNC repeats the RAB DRD procedure until the procedure is performedfor all the candidate cell groups.

Cell Group Selection Based on Service Priorities

If different DC-HSDPA cell groups support the same HSPA+ technology, these groups are ranked byservice priority.

The service priority of a DC-HSDPA cell group is determined by the highest service priority of the twocells in the group.

Table 4-1 lists the reference service priorities for different service bearers.

Table 4-1 Reference service priorities

UL and DL Service Bearers Reference Service Priority

DCH and DCH DCH service priority

DCH and HSDPA HSDPA service priority

http://localhost/var/www/apps/conversion/tmp/scratch_8/Directed%20Retry%20Decision.htm






http://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/ucelldrd_servicediffdrdswitch.html



http://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/ucelldrd_ulldbdrdswitchdchsdpa.html













WCDMA RAN




4-5

DCH and DC-HSDPA HSDPA service priority

HSUPA and DCH HSUPA service priority

HSUPA and HSDPA HSDPA service priority and then HSUPA service priority

Note:

The HSDPA service priority is used first for the ranking. If the HSDPA servicepriority is not enough for the ranking, the HSUPA service priority is used.

HSUPA and DC-HSDPA

Cell Selection Based on UL Load

If the ULLdbDRDSwitchDcHSDPA switch is turned on, the RNC determines the primary-carrier cellbased on UL load balancing between the two cells.

If the current serving cell is not in the target DC-HSDPA cell group, the RNC selects a primary cell withlower uplink load. Otherwise, the RNC checks whether the remaining UL load resource of the serving

cell is lower than or equal to the value of ULLdbDRDLoadRemainThdDCHSDPA:

If the remaining UL load is above the threshold, the RNC selects the serving cell as the primary-carrier cell because its UL load is lower.

If the remaining UL load is below the threshold, the RNC calculates the difference between the UL loadmargin of the serving cell and that of the target cell. Then,

− If the difference is greater than the value of ULLdbDRDOffsetDcHSDPA , the RNC selects the targetcell as the primary-carrier cell because its UL load is lower.

− Otherwise, the RNC selects the serving cell as the primary-carrier cell.

4.5.2 Call Admission Control

Overview

In terms of Call Admission Control (CAC) based on the code resource, CE resource, or Iub resource,DC-HSDPA CAC is not changed, compared with SC-HSDPA CAC.

In terms of CAC based on the DL power or equivalent number of users (ENU), DC-HSDPA CAC ischanged, that is, the resources of the DC-HSDPA cell group need to be considered.

CAC Based on the DL Power

Figure 4-1 shows the resource allocation in the two cells of a DC-HSDPA cell group. In this figure, the DLpower is taken as an example.




http://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/ucelldrd_ulldbdrdloadremainthddchsdpa.html



http://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-para/udrd_ulldbdrdoffsetdchsdpa.html








WCDMA RAN




4-6

Figure 4-1 DL power of a DC-HSDPA cell group

The variables in Figure 4-1 are described as follows:

Pmax: maximum DL power of a cell

Pnon-HSPA: DL power used for non-HSPA UEs in a cell

GBPSC-H: DL power required by the HS-PDSCHs to provide GBRs for SC-HSDPA UEs in a cell.

GBPDC-H: DL power required by the HS-PDSCHs to provide GBRs for the DC-HSDPA UEs in theDC-HSDPA cell group.

For a DC-HSDPA UE, the RNC performs CAC based on the total DL power margin of the DC-HSDPA cellgroup because the UE can use the DL power margin of any of the two cells after the admission.

For a non-DC-HSDPA UE, the RNC performs CAC based on the total DL power of the serving cell minusthe DL power used for the existing non-DC-HSDPA UEs in this cell. If the admission is successful, theRNC continues to perform the CAC based on the total DL power margin of the DC-HSDPA cell group.

CAC Based on the ENU

The CAC based on the Equivalent Number of Users (ENU) is similar to CAC based on the DL power.

For a DC-HSDPA UE, the RNC performs CAC based on the total ENU of the DC-HSDPA cell group.

For a non-DC-HSDPA UE, the RNC first performs CAC based on the ENU of the serving cell. If theadmission is successful, the RNC then continues to perform the CAC based on the ENU of theDC-HSDPA cell group.

CAC Based on the Number of HSDPA Users

The HSDPA services have to make admission decision based on the number of HSDPA users. TheDC-HSDPA costs only one HSDPA license user in the primary cell.

4.5.3 Queuing and Preemption

The UE requesting DC-HSDPA services will be queued in the selected primary cell. The queuingprinciple is the same as that described in the Load Control Feature Parameter Description.

http://localhost/var/www/apps/conversion/tmp/scratch_8/Load%20Control.htm






WCDMA RAN




4-7

For DC-HSDPA services, the RNC selects the primary cell in the DC-HSDPA cell group to performpreemption.

4.5.4 Load Reshuffling and Overload Control

The power of the cell group may trigger basic congestion and overload. If the load of non-HSPA power and GBP in the two cells is higher than or equal to the sum of the DL LDR/overload trigger threshold of the two cells, the cell group is in basic congestion state.

If the cell group is in the basic congestion or overload state, both cells are in the basic congestion or overload state. The operations to relieve congestion or overload are performed in each cell separately.The operations to relieve basic congestion are performed for inter-frequency and inter-RAT handover.The actions to relieve overload are the same as that of RAN11.0.

4.6 Scheduling

The NodeB selects the first cell from the two cells to perform the scheduling process. If the first cellcannot transmit all the data of a UE, the NodeB selects the second cell to provide services.

After determining the cell, the NodeB needs to determine the queuing of this UE and other UEs in thiscell.

The method of DC-HSDPA scheduling is similar to that of SC-HSDPA scheduling. For details, see theHSDPA Feature Parameter Description. This section describes only the difference between the twoscheduling methods.

The calculation of the scheduling priority of a DC-HSDPA queue needs to consider different CQIs and Uurates of the two carriers. In the proportional fair (PF) algorithm and enhanced proportional fair (EPF)algorithm, R/r used for DC-HSDPA is different from that used for SC-HSDPA:

For SC-HSDPA, R represents the throughput corresponding to the CQI reported by the UE for this

carrier, and r represents the throughput currently achieved by the UE. A greater R/r value indicates ahigher scheduling priority.

For DC-HSDPA, R represents the throughput corresponding to the CQI reported by the UE for thiscarrier, and r represents the total throughput currently achieved by the UE on the two carriers.

4.7 Activating or Deactivating Secondary Cell

This section describes the feature WRFD-010713 Traffic-Based Activation and Deactivation of theSupplementary Carrier In Multi-carrier.

The NodeB periodically monitors the traffic volume of a UE and decides whether to activate or deactivatethe secondary cell in the DC-HSDPA/DC-MIMO cell group through HS-SCCH order.

If data in MAC-ehs is insufficient and the throughput of MAC-ehs is low, the NodeB instructs the UE todeactivate the secondary cell.

If data in MAC-ehs is sufficient and the throughput of MAC-ehs is high, the NodeB instructs the UE toactivate the secondary cell.

The deactivation neither changes a DC-HSDPA cell to a non-DC-HSDPA cell nor changes the HS-DSCHUE category. After deactivation, the NodeB regards the UE as a SC-HSDPA UE, and after activation, theNodeB regards the UE as a DC-HSDPA UE.

The function is controlled by the SECCELLACTDEASW switch in the NodeB MML command SETMACHSPARA.



http://localhost/var/www/apps/conversion/tmp/NodeBParaHtml/mml-mo-para/para/MACHSPARA-SecCellActDeaOnDataSM.html







WCDMA RAN




4-8

The activation or deactivation is applicable to the UEs configured with DC-HSDPA, DC-MIMO, or DB-HSDPA in the downlink and to those configured with DCH or SC-HSUPA in the uplink. The function isnot applicable to DC-HSUPA because DC-HSUPA depends on DC-HSDPA.

The activation or deactivation of the UE takes effect after 12 timeslots when the UE receives the

HS-SCCH order. The activation or deactivation of the NodeB takes effect immediately after the NodeBreceives an ACK of HS-SCCH order from the UE. If the NodeB receives an DTX from the UE, the NodeBretransmits or discards the HS-SCCH order.



WCDMA RAN

DC-HSDPA 5 Engineering Guidelines



5-1

5 Engineering Guidelines

5.1 DC-HSDPA

5.1.1 When to Use DC-HSDPA

DC-HSDPA is recommended in the following situations:

The operator needs DC-HSDPA to provide two continuous absolute radio frequency channel numbers(ARFCNs) within the same frequency band and has adequate spectral resources to support this.

The traffic model on the network is close to a burst traffic model, in which case DC-HSDPA yieldsincreased gains in system throughput.

The network downlink load is light, in which case DC-HSDPA increases the peak data rate for usersand noticeably improves the experience of users at cell edges.

The network downlink load is heavy, in which case DC-HSDPA increases system throughput. The

system throughput increase is inversely related to the user number.If the network is heavily loaded with a large number of users, DC-HSDPA can be used but only yieldssubtle gains.

5.1.2 Factors to Consider During Feature Deployment

Consider the following factors when deploying HS-DSDPA:

Proportion of DC-HSDPA users on the network: A higher proportion of DC-HSDPA users results inbetter system throughput gains.

Uplink capabilities: If dedicated channels (DCHs) are used on the uplink, the downlink peak rates for DC-HSDPA users are restricted, resulting in decreased gains. HSUPA is recommended on the uplink

for DC-HSDPA. Bandwidth over the Iub interface: If the bandwidth over the Iub interface is inadequate, DC-HSDPA

cannot yield notable gains. An appropriate bandwidth is required over the Iub interface.

Packet loss rate on the core network: If the core network has a high packet loss rate, gains yielded byDC-HSDPA decrease during single-thread FTP sessions. An appropriate packet loss rate is requiredfor the core network.

5.1.3 Recommended Settings for Key Parameters

The following key parameters are involved in this feature:

MIMO64QAMorDCHSDPASwitch

This parameter specifies priorities for MIMO+64QAM and DC-HSDPA. If the network supports bothMIMO+64QAM and DC-HSDPA, consult with the operator to determine which technique takes priority.If the network load is heavy, set this parameter to MIMO+64QAM. Otherwise, set this parameter toDC-HSDPA.

CmpSwi tch : CMP_UU_ADJACENT_FREQ_CM_SWITCH

When this switch is turned on and the RNC needs to start inter-frequency measurement, the RNCconsiders whether to allow the UE not to use the compressed mode for ARFCNs within 5 MHz fromthe current ARFCN. If the UE is allowed to do so, the RNC starts inter-frequency measurement withoutrequiring the UE to use the compressed mode.

For a DC-HSDPA network, it is recommended that this switch be turned off, because the UE currentlycannot report whether it is allowed not to use the compressed mode for ARFCNs within 5 MHz from

the current ARFCN.









WCDMA RAN




5-2

5.1.4 Feature Monitoring

To determine the number of DC-HSDPA radio access bearers (RABs) or DC-HSDPA users in a cell,check the values of the following RNC counters:

VS.HSDPA.RAB.DC.AttEstab: number of attempts to set up DC-HSDPA RABs on the primary carrier in the DC-HSDPA cell

VS.HSDPA.RAB.DC.SuccEstab: number of successful DC-HSDPA RAB setups on the primarycarrier in the DC-HSDPA cell

VS.HSDPA.DC.PRIM.UE.Mean.Cell: average number of users that have chosen the current cell asthe primary-carrier cell

VS.HSDPA.DC.SEC.UE.Mean.Cell: average number of users that have chosen the current cell as thesecondary-carrier cell

To obtain the information about the scheduling of DC-HSDPA users under a NodeB, check the values of the following NodeB counters:

VS.HSDPA.DCCfg.AnchorCarrierActedNum: number of times during a measurement period thatthe current cell has performed scheduling for users that are configured with DC-HSDPA and havechosen the current cell as the primary-carrier cell, regardless of whether the secondary carrier hasperformed scheduling simultaneously. If the primary and secondary carriers have performedscheduling for a user simultaneously, only one time is counted.

VS.HSDPA.DCCfg.SupCarrierActedNum: number of times during a measurement period that thecurrent cell has performed scheduling for users that are configured with DC-HSDPA and have chosenthe current cell as the secondary-carrier cell, regardless of whether the primary carrier has performedscheduling at the same time. If the primary and secondary carriers have performed scheduling for auser simultaneously, only one time is counted.

VS.HSDPA.DCCfg.DualCarrierActedNum: number of times during a measurement period thatscheduling has been performed by the primary and secondary carriers at the same time for users thatare configured with DC-HSDPA and have chosen the current cell as the primary-carrier cell

DC-HSDPA increases cell throughput and peak rates for individual users. To determine the averageHSDPA throughput and total downlink throughput before and after DC-HSDPA is deployed, check thevalues of the following counters:

VS.HSDPA.MeanChThroughput: an RNC counter that measures the average downlink throughput of individual MAC-d flows for HSDPA in the cell.

The value of this counter is an average. The peak data rate per user can only be checked in drivetests.

VS.DataOutput.Mean: a NodeB counter that measures the average throughput at theMAC-hs/MAC-ehs layer in the cell during a measurement period.

5.2 Activating or Deactivating Secondary Cell

This function cuts overheads on the uplink control channels and reduces the uplink load. It isrecommended that this function be enabled if DC-HSDPA has been deployed.

For burst services such as web browsing, this feature slightly decreases the DC-HSDPA throughputduring service burst transmission. As a result, the delay increases slightly. In addition, this featureincreases the usage of HS-SCCH code resources.

You can check the value of the counter VS.HSDPA.DCCfg.SupCarrierDeact.TimeRatio to determinethe proportion of time during which supplementary carriers remained deactivated for DC-HSDPA usersand DC-HSDPA+MIMO users in a cell depending on the traffic volume.



WCDMA RAN




5-3

For a single DC-HSDPA user, this function reduces the uplink load only by a limited degree. If there are alarge number of DC-HSDPA users, this function reduces the uplink load significantly. Follow these stepsto calculate the uplink load gain for a cell:

1. With this function disabled, obtain the value of VS.MinRTWP when the cell is idle and the value of

VS.MeanRTWP when some DC-HSDPA users are camping on the cell. Then, calculate thedifference between the values of VS.MinRTWP and VS.MeanRTWP and record it as RTWPoff .

2. With this function enabled, obtain the value of VS.MinRTWP when the cell is idle and the value of VS.MeanRTWP when some DC-HSDPA users are camping on the cell. Then, calculate thedifference between the values of VS.MinRTWP and VS.MeanRTWP and record it as RTWPon.

3. Calculate the difference between the values of RTWPoff and RTWPon to obtain the uplink load gainyielded by this function.

The uplink load gain is easily affected by the number of DC-HSDPA users, the channel condition, andother users, and its absolute value is small. As a result, it is not easy to notice a stable uplink load gain.



WCDMA RAN

DC-HSDPA 6 Parameters



6-1

6 Parameters

Table 6-1 Parameter description

Parameter ID NE MML Command DescriptionCfgSwitch BSC6900 SET

UCORRMALGOSWITCH(Optional)

Meaning: Channel configuration strategy switch group.

1) CFG_DL_BLIND_DETECTION_SWITCH: When theswitch is on, the DL blind transport format detectionfunction is used for single SRB and AMR+SRB bearers.Note that the UE is only required to support the blindtransport format stipulated in 3GPP 25.212 section4.3.1.

2) CFG_HSDPA_64QAM_SWITCH: When the switch ison, 64QAM can be configured for the HSDPA service.

3) CFG_HSDPA_DC_SWITCH: When the switch is on,

DC can be configured for the HSDPA service.4) CFG_HSDPA_MIMO_SWITCH: When the switch ison, MIMO can be configured for the HSDPA service.

5) CFG_HSDPA_MIMO_WITH_64QAM_SWITCH:When the switch is on and the switches for 64QAM andMIMO are on, 64QAM+MIMO can be configured for theHSDPA service

6) CFG_HSPA_DTX_DRX_SWITCH: When the switchis on, DTX_DRX can be configured for the HSPAservice.

7) CFG_HSPA_HSSCCH_LESS_OP_SWITCH: When

the switch is on, HS-SCCH Less Operation can beconfigured for the HSPA service.

8) CFG_HSUPA_16QAM_SWITCH: When the switch ison, 16QAM can be configured for the HSUPA service.

9) CFG_IMS_SUPPORT_SWITCH: When the switch ison and the IMS license is activated, the RNC supportsIMS signaling.

10)CFG_LOSSLESS_DLRLC_PDUSIZECHG_SWITCH:When the switch is on, DL lossless RLC PDU sizechange is supported.

11) CFG_LOSSLESS_RELOC_CFG_SWITCH: Whenthe switch is on and the UE supports lossless relocation,the RNC configures lossless relocation for PDCPparameters if the requirements of RLC mode, discardmode, and sequential submission are met. Then,lossless relocation is used for the UE.

12) CFG_MULTI_RAB_SWITCH: When the switch is on,the RNC supports multi-RABs combinations such as2CS, 2CS+1PS, 1CS+2PS, and 2PS.

13) CFG_PDCP_IPV6_HEAD_COMPRESS_SWITCH:When the switch is on and the PDCP Header compression license is activated, the PDCP header



http://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-mml/set-ucorrmalgoswitch.html










WCDMA RAN




6-2

Parameter ID NE MML Command Description

compression algorithm for IPv6 is used at the RNC.

14) CFG_PDCP_RFC2507_HC_SWITCH: When theswitch is on and the PDCP Header compression licenseis activated, the PDCP RFC2507 header compressionalgorithm is used for the RNC.

15) CFG_PDCP_RFC3095_HC_SWITCH: When theswitch is on and the PDCP ROHC license is activated,the PDCP RFC3095 header compression algorithm isused for the RNC.

16) CFG_PTT_SWITCH: When this switch is on, theRNC identifies the PTT user based on the QoSattributes in the RAB assignment request message.Then, the PTT users are subject to special processing.

17) CFG_RAB_REL_RMV_HSPAPLUS_SWITCH:

When this switch is on and if an RAB release isperformed, the RNC decides whether to fall back acertain HSPA(HSPA+) feature based on the requirementof remaining traffic carried by the UE. That is, if anHSPA+ feature is required by the previously releasedRAB connection but is not required in the initial bearer policy of the remaining traffic, the RNC falls back thefeature to save the transmission resources. The HSPA+features that support the fallback are MIMO, 64QAM,MIMO+64QAM, UL 16QAM, DC-HSDPA, and UL TTI2ms.

18) CFG_EDPCCH_BOOSTING_SWITCH: When the

switch is on, Boosting can be configured for the HSUPAservice.

19) CFG_HSDPA_DCMIMO_SWITCH: When thisswitch is turned on, DC+MIMO can be configured for theHSDPA service.

20) CFG_FREE_USER_SWITCH: When this switch isturned on, special handling for free access user isenabled.

21) CFG_DC_MIMO_DYNAMIC_SELECT_SWITCH:When this switch is turned on, the RNC determineswhether to enable the DC-HSDPA or MIMO feature for a

newly admitted user based on the cell load and thenumber of HSDPA users.

GUI Value Range:CFG_DL_BLIND_DETECTION_SWITCH,CFG_HSDPA_64QAM_SWITCH,CFG_HSDPA_DC_SWITCH,CFG_HSDPA_MIMO_SWITCH,CFG_HSDPA_MIMO_WITH_64QAM_SWITCH,CFG_HSPA_DTX_DRX_SWITCH,CFG_HSPA_HSSCCH_LESS_OP_SWITCH,CFG_HSUPA_16QAM_SWITCH,CFG_IMS_SUPPORT_SWITCH,

CFG_LOSSLESS_DLRLC_PDUSIZECHG_SWITCH,



WCDMA RAN




6-3


CFG_LOSSLESS_RELOC_CFG_SWITCH,CFG_MULTI_RAB_SWITCH,CFG_PDCP_IPV6_HEAD_COMPRESS_SWITCH,

CFG_PDCP_RFC2507_HC_SWITCH,CFG_PDCP_RFC3095_HC_SWITCH,CFG_PTT_SWITCH,CFG_RAB_REL_RMV_HSPAPLUS_SWITCH,CFG_EDPCCH_BOOSTING_SWITCH,CFG_HSDPA_DCMIMO_SWITCH,CFG_FREE_USER_SWITCH,CFG_DC_MIMO_DYNAMIC_SELECT_SWITCH

Actual Value Range:CFG_DL_BLIND_DETECTION_SWITCH,CFG_HSDPA_64QAM_SWITCH,CFG_HSDPA_DC_SWITCH,

CFG_HSDPA_MIMO_SWITCH,CFG_HSDPA_MIMO_WITH_64QAM_SWITCH,CFG_HSPA_DTX_DRX_SWITCH,CFG_HSPA_HSSCCH_LESS_OP_SWITCH,CFG_HSUPA_16QAM_SWITCH,CFG_IMS_SUPPORT_SWITCH,CFG_LOSSLESS_DLRLC_PDUSIZECHG_SWITCH,CFG_LOSSLESS_RELOC_CFG_SWITCH,CFG_MULTI_RAB_SWITCH,CFG_PDCP_IPV6_HEAD_COMPRESS_SWITCH,CFG_PDCP_RFC2507_HC_SWITCH,CFG_PDCP_RFC3095_HC_SWITCH,

CFG_PTT_SWITCH,CFG_RAB_REL_RMV_HSPAPLUS_SWITCH,CFG_EDPCCH_BOOSTING_SWITCH,CFG_HSDPA_DCMIMO_SWITCH,CFG_FREE_USER_SWITCH,CFG_DC_MIMO_DYNAMIC_SELECT_SWITCH

Unit: None

Default Value: None

ChannelRetryHoTimerLen

BSC6900 SETUCOIFTIMER(Optional)

Meaning: This parameter specifies the value of thechannel retry handover timer.

When handover is performed and some higher HSPA or

HSPA plus technique is supported, UTRAN will trigger the reconfiguration for the higher techniques.

Pingpang will happen when the reconfiguration istriggered immediately when handover succeeds,because handover procedure is frequently.

In order to avoid the pingpang, this timer will start after handover procedure is performed, and thereconfiguration will not be triggered until the timer expires.

GUI Value Range: 0~999

Actual Value Range: 0~999




http://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-mml/set-ucoiftimer.html











WCDMA RAN




6-4


Unit: s

Default Value: 2

CmpSwitch BSC6900 SETUCORRMALGOSWITCH(Optional)

Meaning: Compatibility switch group.

1) CMP_IU_IMS_PROC_AS_NORMAL_PS_SWITCH:When the switch is on, the IMS signaling assigned bythe CN undergoes compatibility processing as anordinary PS service. When the switch is not on, nospecial processing is performed.

2)CMP_IU_QOS_ASYMMETRY_IND_COMPAT_SWITCH: When the Iu QoS Negotiation function is active andthe switch is on, IE RAB Asymmetry Indicator isSymmetric bidirectional, The uplink and downlink RNCnegotiation rate is asymmetric, RNC select the bigger rete as Iu QoS negotiation rate. When the switch is OFF,RNC select the less rate as Iu QoS negotiation rate.

3) CMP_IU_SYSHOIN_CMP_IUUP_FIXTO1_SWITCH:When the switch is on, the IUUP version can be rolledback to R99 when complete configurations are appliedduring inter-RAT handover.

4)CMP_IUR_H2D_FOR_LOWR5_NRNCCELL_SWITCH:When the switch is on, H2D is performed before aneighboring RNC cell whose version is earlier than R5 isadded to the active set; E2D is performed before a

neighboring RNC cell whose version is earlier than R6 isadded to the active set. If the DRNC is of a versionearlier than R5, DL services cannot be mapped on theHS-DSCH. If the DRNC is of a version earlier than R6,DL services cannot be mapped on the HS-EDCH.

5) CMP_IUR_SHO_DIVCTRL_SWITCH: When theswitch is on, the diversity combination over the Iur interface is configured on the basis of that of the localRNC. When the switch is not on, the diversitycombination over the Iur interface is configured on thebasis of services. The flag of diversity combination over the Iur interface can be set to MUST (for BE services) or

MAY (for other services).6) CMP_UU_ADJACENT_FREQ_CM_SWITCH: whenthe switch is on, the RNC initiates the inter-frequencymeasurement without activating the compressed mode if the following two conditions are met: the UE supportsthe non-compressed inter-frequency measurement, theinter-frequency neighboring cells work in a samefrequency which is within 5 MHz higher or lower than thecurrent frequency; when the switch is off, the RNCactivates the compressed mode before initiating theinter-frequency measurement.

7) CMP_UU_AMR_DRD_HHO_COMPAT_SWITCH:

When the switch is on, When SRB is set up on DCH,













WCDMA RAN




6-5


and RNC decides to setup the AMR through DRDprocedure, RNC will execute blind handover to thetarget cell, and then setup the AMR RBs on the target

cell.

8) CMP_UU_AMR_SID_MUST_CFG_SWITCH: For narrowband AMR services, when the switch is on, theSID frame is always configured; when the switch is noton, the SID frame is configured on the basis of CNassignment.

9) CMP_UU_FDPCH_COMPAT_SWITCH: When theswitch is OFF, if the information element that indicatesthe F-DPCH capability of UE exists in the message"RRC_CONNECT_REQ" or "RRC_CONNECT_SETUP_CMP", the F-DPCHcapability depends on that indicator. In other case, itmeans UE does not support F-DPCH. When the switchis ON, if the information element that indicates theF-DPCH capability of UE exists in the message"RRC_CONNECT_REQ" or "RRC_CONNECT_SETUP_CMP", the F-DPCHcapability depends on that indicator. If that informationelement does not exist, UE supports F-DPCH when allthe conditions meets: a) the version of UE is Release 6.b) UE supports HS-PDSCH.

10) CMP_UU_IGNORE_UE_RLC_CAP_SWITCH:When the switch is on, the RAB assignment request andthe subsequent RB setup procedure proceed if the RLC AM capabilities of the UE fail to meet the minimum RLCTX/RX window buffer requirement of the RAB to besetup. When the switch is not on, the RAB assignmentrequest is rejected.

11)CMP_UU_INTRA_FREQ_MC_BESTCELL_CIO_SWITCH: When this switch is on, the cell individual offset(CIO) of the best cell is always set to 0 in theINTRA-FREQUENCY MEASUREMENT CONTROLmessages. Otherwise, the CIO information of the bestcell is not carried in the INTRA-FREQUENCYMEASUREMENT CONTROL messages.

12)CMP_UU_IOS_CELL_SYNC_INFO_REPORT_SWITCH: When the switch is on, the cell synchronizationinformation traced by the IOS need to be reported duringthe RRC measurement period.

13)CMP_UU_SERV_CELL_CHG_WITH_ASU_SWITCH:When the switch is on, the active set update is in thesame procedure as the change of the serving cell. Whenthe switch is not on, the serving cell is changed after theUE updates the active set and delivers reconfiguration of

physical channels. This switch is applicable only to R6 or



WCDMA RAN




6-6


aboveUEs.

14)CMP_UU_SERV_CELL_CHG_WITH_RB_MOD_SWITCH: When the switch is on, channel transition is in thesame procedure as the change of the serving cell. Whenthe switch is not on, the serving cell is changed after theUE performs channel transition and deliversreconfiguration of physical channels.

15)CMP_UU_VOIP_UP_PROC_AS_NORMAL_PS_SWITCH: By default, the switch is on. In this case, the Alternative E-bit is not configured for L2.

16) CMP_F2F_RLC_ONESIDE_REBUILD_SWITCH:When the switch is set to ON, only uplink RLC or

downlink RLC can be re-established during the statetransition from CELL_FACH to CELL_FACH (F2F for short).

17) CMP_D2F_RLC_ONESIDE_REBUILD_SWITCH:When the switch is set to ON, only uplink RLC or downlink RLC can be re-established during the statetransition from CELL_DCH to CELL_FACH (D2F for short).

18) CMP_RAB_5_CFG_ROHC_SWITCH: When theswitch is set to ON, the service with RAB ID 5 can beconfigured with the Robust Header Compression(ROHC) function. When the switch is set to OFF, the

service with RAB ID 5 cannot be configured with theROHC function.

19) CMP_RAB_6_CFG_ROHC_SWITCH: When theswitch is set to ON, the service with RAB ID 6 can beconfigured with the ROHC function. When the switch isset to OFF, the service with RAB ID 6 cannot beconfigured with the ROHC function.




23) CMP_HSUPA_MACD_FLOW_MUL_SWITCH:

When the switch is set to ON, MAC-d flow can be



WCDMA RAN




6-7


multiplexed without any restrictions. When the switch isset to OFF, only MAC-d flows whose scheduling priorityis lower than that of the current MAC-d flow can be

multiplexed.

24) CMP_SMLC_RSLT_MODE_TYPE_SWITCH: If theClient Type of a positioning request is Value AddedService or Lawful Intercept Client, the positioning resultis reported by using the Ellipsoid Arc type. For other client types, the positioning result is reported by usingthe Ellipsoid point with uncertainty circle type.

GUI Value Range:CMP_IU_IMS_PROC_AS_NORMAL_PS_SWITCH,CMP_IU_QOS_ASYMMETRY_IND_COMPAT_SWITCH, CMP_IU_SYSHOIN_CMP_IUUP_FIXTO1_SWITCH,CMP_IUR_H2D_FOR_LOWR5_NRNCCELL_SWITCH,CMP_IUR_SHO_DIVCTRL_SWITCH,CMP_UU_ADJACENT_FREQ_CM_SWITCH,CMP_UU_AMR_DRD_HHO_COMPAT_SWITCH,CMP_UU_AMR_SID_MUST_CFG_SWITCH,CMP_UU_FDPCH_COMPAT_SWITCH,CMP_UU_IGNORE_UE_RLC_CAP_SWITCH,CMP_UU_INTRA_FREQ_MC_BESTCELL_CIO_SWITCH,CMP_UU_IOS_CELL_SYNC_INFO_REPORT_SWITCH,CMP_UU_SERV_CELL_CHG_WITH_ASU_SWITCH,CMP_UU_SERV_CELL_CHG_WITH_RB_MOD_SWIT

CH,CMP_UU_VOIP_UP_PROC_AS_NORMAL_PS_SWITCH, CMP_F2F_RLC_ONESIDE_REBUILD_SWITCH,CMP_D2F_RLC_ONESIDE_REBUILD_SWITCH,CMP_RAB_5_CFG_ROHC_SWITCH,CMP_RAB_6_CFG_ROHC_SWITCH,CMP_RAB_7_CFG_ROHC_SWITCH,CMP_RAB_8_CFG_ROHC_SWITCH,CMP_RAB_9_CFG_ROHC_SWITCH,CMP_HSUPA_MACD_FLOW_MUL_SWITCH,CMP_SMLC_RSLT_MODE_TYPE_SWITCH

Actual Value Range:

CMP_IU_IMS_PROC_AS_NORMAL_PS_SWITCH,CMP_IU_QOS_ASYMMETRY_IND_COMPAT_SWITCH, CMP_IU_SYSHOIN_CMP_IUUP_FIXTO1_SWITCH,CMP_IUR_H2D_FOR_LOWR5_NRNCCELL_SWITCH,CMP_IUR_SHO_DIVCTRL_SWITCH,CMP_UU_ADJACENT_FREQ_CM_SWITCH,CMP_UU_AMR_DRD_HHO_COMPAT_SWITCH,CMP_UU_AMR_SID_MUST_CFG_SWITCH,CMP_UU_FDPCH_COMPAT_SWITCH,CMP_UU_IGNORE_UE_RLC_CAP_SWITCH,CMP_UU_INTRA_FREQ_MC_BESTCELL_CIO_SWITCH,

CMP_UU_IOS_CELL_SYNC_INFO_REPORT_SWITC



WCDMA RAN




6-8


H,CMP_UU_SERV_CELL_CHG_WITH_ASU_SWITCH,CMP_UU_SERV_CELL_CHG_WITH_RB_MOD_SWIT

CH,CMP_UU_VOIP_UP_PROC_AS_NORMAL_PS_SWITCH, CMP_F2F_RLC_ONESIDE_REBUILD_SWITCH,CMP_D2F_RLC_ONESIDE_REBUILD_SWITCH,CMP_RAB_5_CFG_ROHC_SWITCH,CMP_RAB_6_CFG_ROHC_SWITCH,CMP_RAB_7_CFG_ROHC_SWITCH,CMP_RAB_8_CFG_ROHC_SWITCH,CMP_RAB_9_CFG_ROHC_SWITCH,CMP_HSUPA_MACD_FLOW_MUL_SWITCH,CMP_SMLC_RSLT_MODE_TYPE_SWITCH

Unit: None

Default Value: None

DLFREQ NodeB ADD LOCELL

MOD LOCELL

SET LOCELLPRI

Meaning: Indicates the downlink frequencies of the localcell. The downlink and uplink frequencies of the local cellmust stay within the same frequency band.Frequency(MHZ) = (Frequency Channel Number / 5) +Offset

Band1: Common Frequencies Channel Number:[10562-10838] Offset: 0 Special Frequencies ChannelNumber: none Offset: 0

Band2: Common Frequencies Channel Number:[9662-9938] Offset: 0 Special Frequencies ChannelNumber: (412, 437, 462, 487, 512, 537, 562, 587, 612,637, 662, 687) Offset: 1850.1


Band4: Common Frequencies Channel Number:[1537-1738] Offset: 1805 Special Frequencies ChannelNumber: (1887, 1912, 1937, 1962, 1987, 2012, 2037,2062, 2087) Offset: 1735.1

Band5: Common Frequencies Channel Number:[4357-4458] Offset: 0 Special Frequencies Channel

Number: (1007, 1012, 1032, 1037, 1062, 1087) Offset:670.1

Band6: Common Frequencies Channel Number:[4387-4413] Offset: 0 Special Frequencies ChannelNumber: (1037, 1062) Offset: 670.1

Band7: Common Frequencies Channel Number:[2237-2563] Offset: 2175 Special Frequencies ChannelNumber: (2587, 2612, 2637, 2662, 2687, 2712, 2737,2762, 2787, 2812, 2837, 2862, 2887, 2912) Offset:2105.1

Band8: Common Frequencies Channel Number:

[2937-3088] Offset: 340 Special Frequencies Channel



http://localhost/var/www/apps/conversion/tmp/NodeBMMLHtml/mml-mo-para/mml/add_locell.html


http://localhost/var/www/apps/conversion/tmp/NodeBMMLHtml/mml-mo-para/mml/mod_locell.html


http://localhost/var/www/apps/conversion/tmp/NodeBMMLHtml/mml-mo-para/mml/set_locellpri.html








WCDMA RAN




6-9


Number: none Offset: 0

Band9: Common Frequencies Channel Number:[9237-9387] Offset: 0 Special Frequencies ChannelNumber: none Offset: 0.

The frequency of the local cell must be the same as thatof the bearing logical cell.



Unit: None

Default Value: None

FIRSTLOCELL

NodeB ADDDUALCELLGRP

Meaning: Indicates the ID of local cell 1

.



Unit: None

Default Value: None

HspaPlusSwitch

BSC6900 ADDUCELLALGOSWITCH(Optional)

MODUCELLALGOSWITCH(Optional)

Meaning: This parameter is used to select a featurer elated to HSPA+.

If a feature is selected, it indicates that thecorresponding algorithm is enabled. If a feature is notselected, it indicates that the corresponding algorithm isdisabled. Note that other factors such as license and the

physical capability of NodeB restrict whether a featurecan be used even if this feature is selected. TheEFACH/MIMO switch determines whether the cellsupports the E-FACH/MIMO feature but does not affectthe establishment of the E-FACH and the MIMO cell.

GUI Value Range: 64QAM(Cell 64QAM FunctionSwitch), MIMO(Cell MIMO Function Switch),E_FACH(Cell E_FACH Function Switch),DTX_DRX(Cell DTX_DRX Function Switch),HS_SCCH_LESS_OPERATION(Cell HS_SCCH LESSOPERATION Function Switch), DL_L2ENHANCED(CellDL L2ENHANCED Function Switch),

64QAM_MIMO(Cell 64QAM+MIMO Function Switch),UL_16QAM(Cell UL 16QAM Function Switch),DC_HSDPA(Cell DC-HSDPA Function Switch),UL_L2ENHANCED(Cell UL L2ENHANCED FunctionSwitch), EDPCCH_BOOSTING(Cell E-DPCCH BoostingFunction Switch), DCMIMO_HSDPA(Cell DC-HSDPACombined with MIMO Function Switch),E_DRX(Enhanced Discontinuous Reception FunctionSwitch)

Actual Value Range: 64QAM, MIMO, E_FACH,DTX_DRX, HS_SCCH_LESS_OPERATION,DL_L2ENHANCED, 64QAM_MIMO, UL_16QAM,

DC_HSDPA, UL_L2ENHANCED,




http://localhost/var/www/apps/conversion/tmp/NodeBMMLHtml/mml-mo-para/mml/add_dualcellgrp.html






http://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-mml/add-ucellalgoswitch.html




http://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-mml/mod-ucellalgoswitch.html



















WCDMA RAN




6-10


EDPCCH_BOOSTING, DCMIMO_HSDPA, E_DRX

Unit: None

Default Value: None

MIMO64QAMorDCHSDPASwitch

BSC6900 SETUFRC(Optional)

Meaning: This switch is used to configure the priority of MIMO_64QAM or DC-HSDPA. According to differentprotocols, the following situations may occur: MIMO andDC-HSDPA cannot be used together; both 64QAM andDC-HSDPA are supported, but cannot be used together.In this case, "MIMO64QAMorDCHSDPASwitch" is usedto configure the priorities of the features. When thepriority of MIMO is higher than that of DC-HSDPA, thepriority of 64QAM is higher than that of DC-HSDPA.When the priority of DC-HSDPA is higher than that of MIMO, the priority of DC-HSDPA is higher than that of

64QAM.

GUI Value Range: MIMO_64QAM, DC_HSDPA

Actual Value Range: MIMO_64QAM, DC_HSDPA

Unit: None

Default Value: DC_HSDPA

SECCELLACTDEASW

NodeB SET MACHSPARA Meaning: This parameter specifies whether to activatetraffic-based DC-HSDPA carriers. If this parameter is setto ON, this function takes effect. If this parameter is setto Off, this function does not take effect.

GUI Value Range: ON(ON), OFF(OFF)

Actual Value Range: ON, OFF

Unit: None

Default Value: OFF(OFF)

SECONDLOCELL

NodeB ADDDUALCELLGRP

Meaning: Indicates the ID of local cell 2

.



Unit: None

Default Value: None

ServiceDiffDrdSwitch

BSC6900 ADDUCELLDRD(Optional)

MODUCELLDRD(Optional)

Meaning: Whether the service steering DRD algorithm isapplied.

GUI Value Range: ON, OFF


Unit: None

Default Value: OFF

TCell BSC6900 ADDUCELLSETUP(Mandatory)

ADD

Meaning: Difference between the System FrameNumber (SFN) and NodeB Frame Number (BFN) of theNodeB which the cell belongs to. It is recommended that

Tcell of difference cells under one NodeB should be





http://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-mml/set-ufrc.html






http://localhost/var/www/apps/conversion/tmp/NodeBMMLHtml/mml-mo-para/mml/set_machspara.html











http://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-mml/add-ucelldrd.html




http://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-mml/mod-ucelldrd.html






http://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-mml/add-ucellsetup.html




http://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-mml/add-ucellquicksetup.html

http://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-mml/add-ucellquicksetup.html



























WCDMA RAN




6-11


UCELLQUICKSETUP(Mandatory)

MODUCELLSETUP(Optional)

unique. For detailed information of this parameter, refer to 3GPP TS 25.433.

GUI Value Range: CHIP0, CHIP256, CHIP512,CHIP768, CHIP1024, CHIP1280, CHIP1536,CHIP1792, CHIP2048, CHIP2304

Actual Value Range: CHIP0, CHIP256, CHIP512,CHIP768, CHIP1024, CHIP1280, CHIP1536,CHIP1792, CHIP2048, CHIP2304

Unit: chip

Default Value: None

ULFREQ NodeB ADD LOCELL

MOD LOCELL

Meaning: Indicates the uplink frequencies of the localcell. The downlink and uplink frequencies of the local cellmust stay within the same frequency band.

Frequency(MHZ) = (Frequency Channel Number / 5) +Offset


Band2: Common Frequencies Channel Number:[9262-9538] Offset: 0 Special Frequencies ChannelNumber: (12, 37, 62, 87, 112, 137, 162, 187, 212, 237,262, 287) Offset: 1850.1


Band4: Common Frequencies Channel Number:[1312-1513] Offset: 1450 Special Frequencies ChannelNumber: (1662, 1687, 1712, 1737, 1762, 1787, 1812,1837, 1862) Offset: 1380.1

Band5: Common Frequencies Channel Number:[4132-4233] Offset: 0 Special Frequencies ChannelNumber: (782, 787, 807, 812, 837, 862) Offset: 670.1

Band6: Common Frequencies Channel Number:[4162-4188] Offset: 0 Special Frequencies ChannelNumber: (812, 837) Offset: 670.1 Band7: CommonFrequencies Channel Number: [2012-2338] Offset: 2100

Special Frequencies Channel Number: (2362, 2387,2412, 2437, 2462, 2487, 2512, 2537, 2562, 2587, 2612,2637, 2662, 2687) Offset: 2030.1


Band9: Common Frequencies Channel Number:[8762-8912] Offset: 0 Special Frequencies ChannelNumber: none Offset: 0.



http://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-mml/mod-ucellsetup.html


















WCDMA RAN




6-12


Unit: None

Default Value: None

ULLdbDRDLoadRemainThdDcHSDPA

BSC6900 ADDUCELLDRD(Optional)

MODUCELLDRD(Optional)

Meaning: This parameter specifies the threshold of triggering the uplink load balance for DC-HSDPA traffic.If the remaining number of equivalent users in the uplinkis less than the value of this parameter, uplink loadbalance for DC-HSDPA traffic is triggered.



Unit: %

Default Value: 25

ULLdbDRDOff

setDcHSDPA

BSC6900 SET

UDRD(Optional)

Meaning: If the difference of the remaining number of

equivalent users in the uplink between the target celland the serving cell is greater than the value of thisparameter, the target cell meets one of the qualificationsto be the candidate cell for directed retry.



Unit: %

Default Value: 10

ULLdbDRDSwitchDcHSDPA

BSC6900 ADDUCELLDRD(Option

al) MODUCELLDRD(Optional)

Meaning: This parameter specifies whether to enablethe uplink load balance for DC-HSDPA traffic. The uplink

load balance is performed on the basis of the equivalentnumber of users.

GUI Value Range: ON, OFF


Unit: None

Default Value: OFF


















http://localhost/var/www/apps/conversion/tmp/RNCParaHtml/mbsc/m-mml/set-udrd.html






































WCDMA RAN

DC-HSDPA 7 Counters



7-1

7 Counters

Table 7-1 Counter description

Counter ID Counter Name Counter Description Feature ID Feature Name

50331719 VS.HSDPA.DCCf g.AnchorCarrierActedNum

Number of times that all theusers configured in DC mode in acell are scheduled by AnchorCarrier during themeasurement period

WRFD-010610

WRFD-010689

WRFD-010696

HSDPA IntroductionPackage

HSPA+ Downlink42Mbps per User

DC-HSDPA

50331720 VS.HSDPA.DCCf

g.SupCarrierActedNum

Total number of times

DC-HSDPA-enabled users arescheduled by the supplementarycarrier

WRFD-010610

WRFD-010689

WRFD-010696

HSDPA Introduction

Package


DC-HSDPA

50331721 VS.HSDPA.DCCf g.DualCarrierActedNum

Total number of timesDC-HSDPA-enabled users arescheduled by the anchor andsupplementary carriers at the

same time

WRFD-010610

WRFD-010689

WRFD-010696

HSDPA IntroductionPackage


DC-HSDPA

50341702 VS.HSDPA.DCCf g.SupCarrierDeact.TimeRatio

The Ratio Of Dc Deact WRFD-010713 Traffic-Based Activation andDeactivation of theDC-HSDPASecondary Carrier

73403828 VS.HSDPA.RAB.DC.AttEstab

Number of DC-HSDPA RABSetup Requests in the primary

carrier of DC-HSDPA counted for cell

WRFD-010696 DC-HSDPA

73403829 VS.HSDPA.RAB.DC.SuccEstab

Number of DC-HSDPA RABsSetup Successfully in the primarycarrier of DC-HSDPA counted for cell


73403830 VS.HSDPA.RAB. AbnormRel.DC

Number of DC-HSDPA RABs Abnormal Released in theprimary carrier of DC counted for Cell(including RF Cause)


http://localhost/var/www/apps/conversion/tmp/NodeBCounterHtml/nodeb/b-nodeb-perf/Mt-50331719.html








http://localhost/var/www/apps/conversion/tmp/RNCCounterHtml/mbsc/m-perf/Mt-9761.html















WCDMA RAN

DC-HSDPA 7 Counters



7-2

Counter ID

Counter Name Counter Description Feature ID Feature Name

73403831 VS.HSDPA.RAB.NormRel.DC

Number of DC-HSDPA RABsNormal Released in the primarycarrier of DC counted for Cell


73410508 VS.HSDPA.DC.PRIM.UE.Mean.Cell

Average number of DC-HSDPAUEs in anchor carrier in a Cell


73410509 VS.HSDPA.DC.SEC.UE.Mean.Cell

Average number of DC-HSDPAUEs in supplementary carrier in aCell













WCDMA RAN

DC-HSDPA 8 Glossary



8-1

8 Glossary

For the acronyms, abbreviations, terms, and definitions, see the Glossary .

http://localhost/var/www/apps/conversion/tmp/scratch_8/Glossary.htm






WCDMA RAN

DC-HSDPA 9 Reference Documents

9 Reference Documents

[1] 3GPP TS 25.331, "Radio Resource Control (RRC)"

[2] 3GPP TS 25.306, "UE Radio Access capabilities"

[3] HSDPA Feature Parameter Description

[4] Radio Bearers Feature Parameter Description

[5] Load Control Feature Parameter Description

[6] Directed Retry Decision Feature Parameter Description

[7] Handover Feature Parameter Description

[8] Green BTS Feature Parameter Description



http://localhost/var/www/apps/conversion/tmp/scratch_8/Radio%20Bearers.htm








http://localhost/var/www/apps/conversion/tmp/scratch_8/Green%20BTS.htm






