dc-hsdpa(ran13.0_04)

8/13/2019 DC-HSDPA(RAN13.0_04)

http://slidepdf.com/reader/full/dc-hsdparan13004 1/51

DC-HSDPARAN13.0

Feature Parameter Description

Issue 0 4

Date 201 3 -01 -30

HUAWEI TECHNOLOGIES CO., LTD.

8/13/2019 DC-HSDPA(RAN13.0_04)


Copyright © Huawei Technologies Co., Ltd. 201 2 . All rights reserved.No part of this document may be reproduced or transmitted in any form or by any means without priorwritten 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 respectiveholders.

NoticeThe purchased products, services and features are stipulated by the contract made between Huawei andthe customer. All or part of the products, services and features described in this document may not bewithin 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 orrepresentations of any kind, either express or implied.

The information in this document is subject to change without notice. Every effort has been made in thepreparation of this document to ensure accuracy of the contents, but all statements, information, andrecommendations 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]




8/13/2019 DC-HSDPA(RAN13.0_04)


WCDMA RANDC-HSDPA Contents

Issue 04 (2013-01-30) Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd

ii

Contents1 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-2

3.3 Channel Mapping .......................................................................................................................... 3-3

3.4 UE Categories ............................................................................................................................... 3-4

3.5 NodeB MAC-ehs ........................................................................................................................... 3-4 3.6 Impact on Interfaces ...................................................................................................................... 3-6

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 Impact on the Network ............................................................................................................. 5-1


6 Engineering Guidelines ........................................................................................................... 6-1

6.1 DC-HSDPA .................................................................................................................................... 6-1

6.1.1 When to Use DC-HSDPA ..................................................................................................... 6-1

6.1.2 Factors to Consider During Feature Deployment ................................................................. 6-1

6.1.3 Recommended Settings for Key Parameters ....................................................................... 6-1

6.1.4 Feature Deployment ............................................................................................................. 6-2

6.1.5 Feature Monitoring ............................................................................................................... 6-2


6.2.1 When to Use Traffic-Based Activation and Deactivation of the Supplementary Carrier InMulti-carrier .................................................................................................................................... 6-2

6.2.2 Information to Be Collected .................................................................................................. 6-3

6.2.3 Feature Deployment ............................................................................................................. 6-3

8/13/2019 DC-HSDPA(RAN13.0_04)


WCDMA RANDC-HSDPA Contents


iii

6.2.4 Feature Monitoring ............................................................................................................... 6-3

7 Parameters .................................................................................................................................. 7-1

8 Counters ...................................................................................................................................... 8-1

9 Glossary ...................................................................................................................................... 9-1

10 Reference Documents ......................................................................................................... 10-1

8/13/2019 DC-HSDPA(RAN13.0_04)


WCDMA RANDC-HSDPA 1 Introduction


1-1

1 Introduction1.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 AudienceThis 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 HistoryThis 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:

04 (2013-01-30) 03 (2012-05-30) 02 (2011-06-30) 01 (2011-04-30) Draft B (2011-03-30) Draft A (2010-12-30)

04 (2012-01-30)

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

Compared with issue 03 (2012-05-30) of RAN13.0, this issue has the following changes.

Change Type Change Description Parameter Change

Feature change None. None.

Editorial change Optimized the description in section 6.2.1 "When to UseTraffic-Based Activation and Deactivation of theSupplementary Carrier In Multi-carrier. "

None.

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




8/13/2019 DC-HSDPA(RAN13.0_04)


WCDMA RANDC-HSDPA 1 Introduction


1-2

03 (2012-05-30)

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




Editorial change The following chapter is added: 5 Impact on the Network

None.

The engineering guideline is optimized. For details, see6 "Engineering Guidelines. "

None.

02 (2011-06-30)This is the document for the second commercial release of RAN13.0.




Editorial change The engineering guideline about DC-HSDPA isadded. For details, see 6.1 "DC-HSDPA. "

None.

The engineering guideline about activating ordeactivating secondary cell moved from 4.7"Activating or Deactivating Secondary Cell" to 6.2"Activating or Deactivating Secondary Cell. "

None.

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 ordeactivating secondary cell. For details, see 4.7 "Activating or Deactivating Secondary Cell. "

8/13/2019 DC-HSDPA(RAN13.0_04)


WCDMA RANDC-HSDPA 2 Overview


2-1

2 OverviewSimilar to Long Term Evolution (LTE), the HSPA technology is also influenced by the multi-carrieraggregations. 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.

8/13/2019 DC-HSDPA(RAN13.0_04)


WCDMA RANDC-HSDPA 3 Basic Principle


3-1

3 Basic Principle3.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. For distributed cells, two local cells in a DC-HSDPA cell group must belong to one RRU. Fornon-distributed cells, if two local cells in a DC-HSDPA cell group belong to two RRUs, the RRUs adopta star or chain topology.

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.

8/13/2019 DC-HSDPA(RAN13.0_04)




3-2

3.2 Cell ConfigurationDC-HSDPA cell group consists of two cells: primary cell and secondary cell.

From the UE perspective:

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.

8/13/2019 DC-HSDPA(RAN13.0_04)




3-3

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.

3.3 Channel MappingOverview

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, and

type 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).

8/13/2019 DC-HSDPA(RAN13.0_04)




3-4

3.4 UE CategoriesIn 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.

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

HS-DSCHCategory

MaximumNumberofHS-DSCHCodesReceived

MinimumInter-TTIInterval

MaximumNumber ofBits of anHS-DSCHTransportBlockReceivedWithinan HS-DSCH

TTI

TotalNumberof SoftChannelBits

SupportedModulation WithoutMIMOOperationor DualCellOperation

SupportedModulationSimultaneous withMIMOOperationandWithoutDual CellOperation

SupportedModulationwithDualCellOperation

Category 21 15 1 23370 345600

- -

QPSK,16QAMCategory 22 15 1 27952 345600

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

AMCategory 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, one

8/13/2019 DC-HSDPA(RAN13.0_04)




3-5

HARQ process per TTI for single carrier transmission and two HARQ processes per TTI for dual carriertransmission.

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 CQI

reported by the UE.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 oftraffic flow to a DC-HSDPA UE.

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

8/13/2019 DC-HSDPA(RAN13.0_04)




3-6

3.6 Impact on InterfacesTo 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.

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 Uu

In 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 ofsecondary 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

8/13/2019 DC-HSDPA(RAN13.0_04)


WCDMA RANDC-HSDPA 4 Technical Description


4-1

4 Technical Description4.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 a

frequency 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












8/13/2019 DC-HSDPA(RAN13.0_04)




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 TransitionDC-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 a

DRD 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 following

operations:− 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 ManagementThe introduction of DC-HSDPA has no impact on handover measurement triggering and handoverdecision 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_6/Handover.htm




8/13/2019 DC-HSDPA(RAN13.0_04)




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 measurement

are 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 handoverto 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 betterthan 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. If the reconfiguration fails, the RNC starts theretry timer (ChannelRetryTimerLen ) for periodic retry attempts. The HSPA+ technologies that can beretried are specified by the parameter RetryCapabili ty .

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



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



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







8/13/2019 DC-HSDPA(RAN13.0_04)




4-4

Handover Between RNC

The current version does not support the handover between different RNCs for DC-HSDPA users.

During the handover, if the target cell is from different RNC, the DC-HSDPA user falls back to downlink

enhanced L2 and then the handover is performed.Upon completion of the handover, if DC-HSDPA is included in HSPA technologies that can be retried byUEs (that is, DC-HSDPA under the RetryCapabili ty parameter is turned on) and the handover target cellsupports DC-HSDPA, the RNC will attempt to switch the services on DC-HSDPA RABs.

4.5 Load Control

4.5.1 RAB DRDDuring 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+ technologicalsatisfaction. 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 cell

groups 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 ServiceDiffDrdSwitch 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.




http://localhost/var/www/apps/conversion/tmp/scratch_6/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












8/13/2019 DC-HSDPA(RAN13.0_04)




4-5

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 prioritiesUL and DL Service Bearers Reference Service Priority

DCH and DCH DCH service priority

DCH and HSDPA HSDPA service priority

DCH and DC-HSDPA HSDPA service priority

HSUPA and DCH HSUPA service priority

HSUPA and HSDPA HSDPA service priority and then HSUPA service priorityNote:

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 servingcell 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-carriercell 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 target

cell 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






8/13/2019 DC-HSDPA(RAN13.0_04)




4-6

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

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

P max : maximum DL power of a cell P non-HSPA : DL power used for non-HSPA UEs in a cell GBP SC-H : DL power required by the HS-PDSCHs to provide GBRs for SC-HSDPA UEs in a cell. GBP DC-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 PreemptionThe 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_6/Load%20Control.htm




8/13/2019 DC-HSDPA(RAN13.0_04)




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 powerand GBP in the two cells is higher than or equal to the sum of the DL LDR/overload trigger threshold ofthe 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 oroverload 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 SchedulingThe 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 CellThis 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 the throughput at the MAC-ehs layer is lower than 100 kbit/s and the data in an MAC-ehs queue is80% likely to be completely sent within a short time, the NodeB instructs the UE to deactivate thesecondary cell.

If the throughput at the MAC-ehs layer is higher than 400 kbit/s and the data in an MAC-ehs queue is20% likely to be completely sent within a short time, the NodeB instructs the UE to activate thesecondary cell.

The preceding thresholds are not configurable.

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.




8/13/2019 DC-HSDPA(RAN13.0_04)




4-8

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

The activation or deactivation is applicable to the UEs configured with DC-HSDPA, DC-MIMO, orDB-HSDPA in the downlink and to those configured with DCH or SC-HSUPA in the uplink.

The activation or deactivation of the UE takes effect after 12 timeslots when the UE receives theHS-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.

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




8/13/2019 DC-HSDPA(RAN13.0_04)


WCDMA RANDC-HSDPA 5 Impact on the Network


5-1

5 Impact on the Network5.1 Activating or Deactivating Secondary Cell

Impact on System CapacityThis feature helps increase the uplink throughput of a cell or number of UEs that can be admitted whenboth of the following conditions are met:

There is a large number of multi-carrier (MC) UEs (for example, DC-HSDPA UEs) in the downlink. The downlink traffic is light.

Impact on Network Performance

By deactivating secondary carriers, this feature helps decrease the uplink load of cells. Compared withDC-HSDPA UEs, SC-HSUPA UEs demodulate only the data received on primary carriers. In addition,the transmit power of the HS-DPCCH allocated to SC UEs is 2 dB lower than that of the HS-DPCCHallocated to DC UEs.

For example:

In a cell, when the DC-HSDPA UE penetration rate is 100% and the downlink traffic is light, this featurecan reduce the uplink load of cells by 5% to 10%.

8/13/2019 DC-HSDPA(RAN13.0_04)


WCDMA RANDC-HSDPA 6 Engineering Guidelines


6-1

6 Engineering Guidelines6.1 DC-HSDPA

6.1.1 When to Use DC-HSDPADC-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.

6.1.2 Factors to Consider During Feature DeploymentConsider the following factors when deploying DC-HSDPA.

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 forDC-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-HSDPAcannot 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.

6.1.3 Recommended Settings for Key ParametersThe 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_SWITCHWhen 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.







8/13/2019 DC-HSDPA(RAN13.0_04)




6-2

6.1.4 Feature DeploymentFor details on how to activate, verify, and deactivate this feature, see Configuring DC-HSDPA in theFeature Activation Guide .

6.1.5 Feature MonitoringTo 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 carrierin 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 ofthe 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 chosen

the 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 ofindividual 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.

6.2 Activating or Deactivating Secondary Cell

6.2.1 When to Use Traffic-Based Activation and Deactivation of theSupplementary Carrier In Multi-carrierThis feature provides the following positive and negative gains:

http://localhost/var/www/apps/conversion/tmp/FAGHtml/mbsc/m-bsc-reconfiguration-guide/WRFD-010696.html




8/13/2019 DC-HSDPA(RAN13.0_04)




6-3

Reduced uplink load on RAN Reduced power consumption for the UEs, which depends on the UEs Longer delay in burst services for DC-HSDPA users, which affects the user experience

Therefore, you are advised to enable this feature on heavily loaded networks. For lightly loadednetworks, the operator can decide whether to use this feature as follows:

Disable this feature if the transmission delay of burst services needs to be reduced. Enable this feature if UE power needs to be saved.

6.2.2 Information to Be CollectedCollect the following information before deploying this feature:

MC UE penetration rateMC UEs include DC-HSDPA UEs and DC-HSDPA+MIMO UEs.The larger the ratio of VS.HSDPA.DC.PRIM.UE.Mean.Cell to VS.HSDPA.UE.Mean.Cell, the moregains this feature brings.

Mean UE throughputThe smaller the value is for VS.HSDPA.MeanChThroughput, the more gains this feature brings.

6.2.3 Feature DeploymentFor details on how to activate, verify, and deactivate this feature, see Configuring Traffic-Based

Activation and Deactivation of the Supplementary Carrier In Multi-carrier in the Feature Activation Guide .

6.2.4 Feature Monitoring

The ratio of the throughput-based secondary cell active time over the user-existence time ofDC-HSDPA&DC-HSDPA+MIMO users can be monitored by the NodeB counterVS.HSDPA.DCCfg.SupCarrierDeact.TimeRatio .

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 ofVS.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 RTWP off .

2. With this function enabled, obtain the value of VS.MinRTWP when the cell is idle and the value ofVS.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 RTWP on .

3. Calculate the difference between the values of RTWP off and RTWP on 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.







8/13/2019 DC-HSDPA(RAN13.0_04)


WCDMA RANDC-HSDPA 7 Parameters


7-1

7 ParametersTable 7-1 Parameter description

Parameter ID NE MML Command Feature ID FeatureName Description

CfgSwitch BSC6900 SETUCORRMALGOSWITCH(Optional)

WRFD-010615

WRFD-01061501

WRFD-01061502

WRFD-01061503

WRFD-01061504

WRFD-010683

WRFD-010684

WRFD-010686

WRFD-010687

WRFD-011500

WRFD-011501

WRFD-02060504

WRFD-010697

WRFD-010699

WRFD-010693

WRFD-010694

WRFD-010696

MultipleRABPackage

Combination of TwoPSServices

Combinati

on of OneCSServiceand TwoPSServices

Combination ofThree PSServices

Combinati

on of OneCSServiceand ThreePSServices

Downlink64 QAM

2 x 2MIMO

CPC -DTX /DRX

CPC -HS-SCCHlessoperation

PDCPHeaderCompression(RFC2507

Meaning:Channel configurationstrategy switch group.

1)CFG_DL_BLIND_DETECTION_ SWITCH: When the switch is on,the DL blind transport formatdetection function is used forsingle SRB and AMR+SRBbearers. Note that the UE is only

required to support the blindtransport format stipulated in3GPP 25.212 section 4.3.1.

2)CFG_HSDPA_64QAM_SWITCH:When the switch is on, 64QAMcan be configured for the HSDPAservice.

3) CFG_HSDPA_DC_SWITCH:When the switch is on, DC can beconfigured for the HSDPA

service.4)CFG_HSDPA_MIMO_SWITCH:When the switch is on, MIMO canbe configured for the HSDPAservice.

5)CFG_HSDPA_MIMO_WITH_64Q

AM_SWITCH: When the switch ison and the switches for 64QAMand MIMO are on, 64QAM+MIMO

can be configured for the HSDPAservice

6)CFG_HSPA_DTX_DRX_SWITCH: When the switch is on,DTX_DRX can be configured forthe HSPA service.

7)CFG_HSPA_HSSCCH_LESS_OP_SWITCH: When the switch ison, HS-SCCH Less Operation

can be configured for the HSPA



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








8/13/2019 DC-HSDPA(RAN13.0_04)




7-2

Parameter ID NE MML Command Feature ID FeatureName

Description

)

PDCPHeaderCompression (RoHC)

LosslessSRNSRelocation

E-DPCCHBoosting

DC-HSDP A+MIMO

DL64QAM+MIMO

UL16QAM

DC-HSDP A

service.

8)CFG_HSUPA_16QAM_SWITCH:When the switch is on, 16QAMcan be configured for the HSUPAservice.

9)CFG_IMS_SUPPORT_SWITCH:When the switch is on and theIMS license is activated, the RNCsupports IMS signaling.

10)

CFG_LOSSLESS_DLRLC_PDUSIZECHG_SWITCH: When theswitch is on, DL lossless RLCPDU size change is supported.

11)CFG_LOSSLESS_RELOC_CFG

_SWITCH: When the switch is onand the UE supports losslessrelocation, the RNC configureslossless relocation for PDCPparameters if the requirements ofRLC mode, discard mode, andsequential submission are met.Then, lossless relocation is usedfor the UE.

12) CFG_MULTI_RAB_SWITCH:When the switch is on, the RNCsupports multi-RABscombinations such as 2CS,2CS+1PS, 1CS+2PS, and 2PS.

13)CFG_PDCP_IPV6_HEAD_COMPRESS_SWITCH: When theswitch is on and the PDCPHeader compression license isactivated, the PDCP headercompression algorithm for IPv6 isused at the RNC.

14)CFG_PDCP_RFC2507_HC_SWITCH: When the switch is on andthe PDCP Header compressionlicense is activated, the PDCPRFC2507 header compressionalgorithm is used for the RNC.

8/13/2019 DC-HSDPA(RAN13.0_04)




7-3


Description

15)CFG_PDCP_RFC3095_HC_SWITCH: When the switch is on andthe PDCP ROHC license isactivated, the PDCP RFC3095header compression algorithm isused for the RNC.

16) CFG_PTT_SWITCH: Whenthis switch is on, the RNCidentifies the PTT user based onthe QoS attributes in the RABassignment request message.Then, the PTT users are subjectto special processing.

17)CFG_RAB_REL_RMV_HSPAPLUS_SWITCH: When this switch ison and if an RAB release isperformed, the RNC decideswhether to fall back a certainHSPA(HSPA+) feature based onthe requirement of remainingtraffic carried by the UE. That is, ifan HSPA+ feature is required bythe previously released RAB

connection but is not required inthe initial bearer policy of theremaining traffic, the RNC fallsback the feature to save thetransmission resources. TheHSPA+ features that support thefallback are MIMO, 64QAM,MIMO+64QAM, UL 16QAM,DC-HSDPA, and UL TTI 2ms.

18)CFG_EDPCCH_BOOSTING_SWITCH: When the switch is on,Boosting can be configured forthe HSUPA service.

19)CFG_HSDPA_DCMIMO_SWITCH: When this switch is turned on,DC+MIMO can be configured forthe HSDPA service.

20)CFG_FREE_USER_SWITCH:When this switch is turned on,special handling for free access

8/13/2019 DC-HSDPA(RAN13.0_04)




7-4


Description

user is enabled.

21)CFG_DC_MIMO_DYNAMIC_SELECT_SWITCH: When thisswitch is turned on, the RNCdetermines whether to enable theDC-HSDPA or MIMO feature for anewly admitted user based on thecell load and the number ofHSDPA users.

GUI ValueRange:CFG_DL_BLIND_DETECTION_SWITCH,CFG_HSDPA_64QAM_SWITCH,CFG_HSDPA_DC_SWITCH,CFG_HSDPA_MIMO_SWITCH,CFG_HSDPA_MIMO_WITH_64Q

AM_SWITCH,CFG_HSPA_DTX_DRX_SWITCH,CFG_HSPA_HSSCCH_LESS_OP_SWITCH,CFG_HSUPA_16QAM_SWITCH,CFG_IMS_SUPPORT_SWITCH,CFG_LOSSLESS_DLRLC_PDU

SIZECHG_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

Actual ValueRange:CFG_DL_BLIND_DETECTION_SWITCH,CFG_HSDPA_64QAM_SWITCH,CFG_HSDPA_DC_SWITCH,CFG_HSDPA_MIMO_SWITCH,

CFG_HSDPA_MIMO_WITH_64Q

8/13/2019 DC-HSDPA(RAN13.0_04)


8/13/2019 DC-HSDPA(RAN13.0_04)




7-6


Description

WRFD-010687

WRFD-021101

WRFD-021200

CPC -DTX /DRX


DynamicChannelConfiguration Control(DCCC)

HCS(Hierarchical CellStructure)

GUI Value Range:0~999

Actual Value Range:0~999Unit:s

Default Value:2

ChannelRetryTimerLen

BSC6900 SETUCOIFTIMER(Optional)

WRFD-01061008

WRFD-01061112

WRFD-01061206

WRFD-01061403

WRFD-010630

WRFD-010632

WRFD-010636

WRFD-010652

WRFD-010683

WRFD-010684

WRFD-010685

WRFD-010686

WRFD-01

InteractiveandBackground TrafficClass onHSDPA

HSDPADRD

InteractiveandBackground TrafficClass onHSUPA

HSUPA2ms TTI

StreamingTrafficClass onHSDPA

StreamingTrafficClass onHSUPA

SRB overHSUPA

SRB over

HSDPA

Meaning:This parameter specifiesthe value of the channel retrytimer. The timer will start whentraffic is set up or reconfiguredand some higher technique is notconfigured by some reasonexcept for the capability of UE or

cell. Channel retry will beperformed after this timer expires.


Actual Value Range:0~180

Unit:s

Default Value:5




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









8/13/2019 DC-HSDPA(RAN13.0_04)


8/13/2019 DC-HSDPA(RAN13.0_04)




7-8


Description

_FIXTO1_SWITCH: When theswitch is on, the IUUP versioncan be rolled back to R99 whencomplete configurations areapplied during inter-RAThandover.

4)CMP_IUR_H2D_FOR_LOWR5_ NRNCCELL_SWITCH: When theswitch is on, H2D is performedbefore a neighboring RNC cellwhose version is earlier than R5is added to the active set; E2D isperformed before a neighboringRNC cell whose version is earlierthan R6 is added to the active set.If the DRNC is of a version earlierthan R5, DL services cannot bemapped on the HS-DSCH. If theDRNC is of a version earlier thanR6, DL services cannot bemapped on the HS-EDCH.

5)CMP_IUR_SHO_DIVCTRL_SWITCH: When the switch is on, the

diversity combination over the Iurinterface is configured on thebasis of that of the local RNC.When the switch is not on, thediversity combination over the Iurinterface is configured on thebasis of services. The flag ofdiversity combination over the Iurinterface can be set to MUST (forBE services) or MAY (for otherservices).

6)CMP_UU_ADJACENT_FREQ_CM_SWITCH: when the switch ison, the RNC initiates theinter-frequency measurementwithout activating thecompressed mode if the followingtwo conditions are met: the UEsupports the non-compressedinter-frequency measurement,the inter-frequency neighboringcells work in a same frequencywhich is within 5 MHz higher or

lower than the current frequency;

8/13/2019 DC-HSDPA(RAN13.0_04)




7-9


Description

when the switch is off, the RNCactivates the compressed modebefore initiating theinter-frequency measurement.

7)CMP_UU_AMR_DRD_HHO_COMPAT_SWITCH: When the switchis on, When SRB is set up onDCH, and RNC decides to setupthe AMR through DRD procedure,RNC will execute blind handoverto the target cell, and then setupthe AMR RBs on the target cell.

8)CMP_UU_AMR_SID_MUST_CFG_SWITCH: For narrowband

AMR services, when the switch ison, the SID frame is alwaysconfigured; when the switch is noton, the SID frame is configuredon the basis of CN assignment.

9)CMP_UU_FDPCH_COMPAT_SWITCH: When the switch is OFF,if the information element thatindicates the F-DPCH capabilityof UE exists in the message"RRC_CONNECT_REQ" or"RRC_CONNECT_SETUP_CMP", the F-DPCH capability dependson that indicator. In other case, itmeans UE does not supportF-DPCH. When the switch is ON,if the information element thatindicates the F-DPCH capabilityof UE exists in the message"RRC_CONNECT_REQ" or"RRC_CONNECT_SETUP_CMP", the F-DPCH capability dependson that indicator. If thatinformation element does notexist, UE supports F-DPCH whenall the conditions meets: a) theversion of UE is Release 6. b) UEsupports HS-PDSCH.

10)CMP_UU_IGNORE_UE_RLC_C

AP_SWITCH: When the switch ison, the RAB assignment requestand the subsequent RB setup

8/13/2019 DC-HSDPA(RAN13.0_04)




7-10


Description

procedure proceed if the RLC AMcapabilities of the UE fail to meetthe minimum RLC TX/RX windowbuffer requirement of the RAB tobe setup. When the switch is noton, the RAB assignment requestis rejected.

11)CMP_UU_INTRA_FREQ_MC_BESTCELL_CIO_SWITCH: Whenthis switch is on, the cellindividual offset (CIO) of the bestcell is always set to 0 in theINTRA-FREQUENCYMEASUREMENT CONTROLmessages. Otherwise, the CIOinformation of the best cell is notcarried in theINTRA-FREQUENCYMEASUREMENT CONTROLmessages.

12)CMP_UU_IOS_CELL_SYNC_INFO_REPORT_SWITCH: Whenthe switch is on, the cell

synchronization informationtraced by the IOS need to bereported during the RRCmeasurement period.

13)CMP_UU_SERV_CELL_CHG_WITH_ASU_SWITCH: When theswitch is on, the active set updateis in the same procedure as thechange of the serving cell. Whenthe switch is not on, the servingcell is changed after the UEupdates the active set anddelivers reconfiguration ofphysical channels. This switch isapplicable only to R6 oraboveUEs.

14)CMP_UU_SERV_CELL_CHG_WITH_RB_MOD_SWITCH: Whenthe switch is on, channeltransition is in the sameprocedure as the change of theserving cell. When the switch isnot on, the serving cell is

8/13/2019 DC-HSDPA(RAN13.0_04)


8/13/2019 DC-HSDPA(RAN13.0_04)




7-12


Description

TCH: When the switch is set toON, the service with RAB ID 7can be configured with the ROHCfunction. When the switch is setto OFF, the service with RAB ID 7cannot be configured with theROHC function.

21)CMP_RAB_8_CFG_ROHC_SWITCH: When the switch is set toON, the service with RAB ID 8can be configured with the ROHCfunction. When the switch is setto OFF, the service with RAB ID 8cannot be configured with theROHC function.

22)CMP_RAB_9_CFG_ROHC_SWITCH: When the switch is set toON, the service with RAB ID 9can be configured with the ROHCfunction. When the switch is setto OFF, the service with RAB ID 9cannot be configured with theROHC function.

23)CMP_HSUPA_MACD_FLOW_MUL_SWITCH: When the switch isset to ON, MAC-d flow can bemultiplexed without anyrestrictions. When the switch isset to OFF, only MAC-d flowswhose scheduling priority is lowerthan that of the current MAC-dflow can be multiplexed.

24)

CMP_SMLC_RSLT_MODE_TYPE_SWITCH: If the Client Type ofa positioning request is Value

Added Service or Lawful InterceptClient, the positioning result isreported by using the Ellipsoid

Arc type. For other client types,the positioning result is reportedby using the Ellipsoid point withuncertainty circle type.

GUI ValueRange:CMP_IU_IMS_PROC_AS

_NORMAL_PS_SWITCH,

8/13/2019 DC-HSDPA(RAN13.0_04)




7-13


Description

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_C

AP_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_SWITCH,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 ValueRange:CMP_IU_IMS_PROC_AS

_NORMAL_PS_SWITCH,CMP_IU_QOS_ASYMMETRY_IND_COMPAT_SWITCH,CMP_IU_SYSHOIN_CMP_IUUP

8/13/2019 DC-HSDPA(RAN13.0_04)




7-14


Description

_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_C

AP_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_SWITCH,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

None None Meaning:Indicates the downlinkfrequencies of the local cell. Thedownlink and uplink frequenciesof the local cell must stay withinthe same frequency band.



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






8/13/2019 DC-HSDPA(RAN13.0_04)


8/13/2019 DC-HSDPA(RAN13.0_04)




7-17


Description

0695

WRFD-010696

WRFD-010697

WRFD-010699

64QAM+MIMO

UL16QAM

UL Layer 2Improvement

DC-HSDP A

E-DPCCHBoosting

DC-HSDP A+MIMO

HS_SCCH_LESS_OPERATION(Cell HS_SCCH LESSOPERATION Function Switch),DL_L2ENHANCED(Cell DLL2ENHANCED Function Switch),64QAM_MIMO(Cell64QAM+MIMO Function Switch),UL_16QAM(Cell UL 16QAMFunction Switch),DC_HSDPA(Cell DC-HSDPAFunction Switch),UL_L2ENHANCED(Cell ULL2ENHANCED Function Switch),EDPCCH_BOOSTING(Cell

E-DPCCH Boosting FunctionSwitch), DCMIMO_HSDPA(CellDC-HSDPA Combined with MIMOFunction Switch),E_DRX(Enhanced DiscontinuousReception Function Switch)

Actual Value Range:64QAM,MIMO, E_FACH, DTX_DRX,HS_SCCH_LESS_OPERATION,DL_L2ENHANCED,64QAM_MIMO, UL_16QAM,DC_HSDPA, UL_L2ENHANCED,EDPCCH_BOOSTING,DCMIMO_HSDPA, E_DRX

Unit:None

Default Value:None

MIMO64QAMor DCHSDPASwitch

BSC6900 SETUFRC(Optional)

WRFD-010680

WRFD-010681

WRFD-010696

HSPA+Downlink28Mbpsper User

HSPA+Downlink21Mbpsper User

DC-HSDP A

Meaning:This switch is used toconfigure the priority ofMIMO_64QAM or DC-HSDPA.

According to different protocols,the following situations mayoccur: MIMO and DC-HSDPAcannot be used together; both64QAM and DC-HSDPA aresupported, but cannot be usedtogether. In this case,"MIMO64QAMorDCHSDPASwitch" is used to configure thepriorities of the features. Whenthe priority of MIMO is higher thanthat of DC-HSDPA, the priority of64QAM is higher than that ofDC-HSDPA. When the priority ofDC-HSDPA is higher than that ofMIMO, the priority of DC-HSDPA





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








8/13/2019 DC-HSDPA(RAN13.0_04)




7-18


Description

is higher than that of 64QAM.

GUI Value Range:MIMO_64QAM,DC_HSDPA

Actual ValueRange:MIMO_64QAM,DC_HSDPA

Unit:None

Default Value:DC_HSDPA

RetryCapability BSC6900 SETUFRC(Optional)

WRFD-010652

WRFD-01061403

WRFD-010636

WRFD-010685

WRFD-010683

WRFD-01

0684WRFD-010686

WRFD-010687

WRFD-010697

WRFD-010699

WRFD-010693

WRFD-010694

WRFD-010695

WRFD-010696

SRB overHSDPA

HSUPA2ms TTI

SRB overHSUPA

DownlinkEnhancedL2

Downlink64 QAM

2 x 2MIMO

CPC -DTX /DRX


E-DPCCHBoosting

DC-HSDP A+MIMO

DL64QAM+MIMO

UL16QAM

UL Layer 2Improvem

ent

Meaning:This parameter specifieswhich HSPA technologies can be

retried by UEs. When the HSPAtechnologies are selected andcurrently UE is not using them,RNC will initiate these HSPAtechnologies retry for UE.

GUI ValueRange:SRB_OVER_HSDPA,SRB_OVER_HSUPA, TTI_2MS,MIMO, 64QAM,DL_L2_ENHANCE, DTX_DRX,HSSCCH_LESS_OPERATION,MIMO_64QAM, DC_HSDPA,UL_L2_ENHANCE, UL_16QAM,EDPCCH_BOOSTING,DCMIMO_HSDPA

Actual ValueRange:SRB_OVER_HSDPA,SRB_OVER_HSUPA, TTI_2MS,MIMO, 64QAM,DL_L2_ENHANCE, DTX_DRX,HSSCCH_LESS_OPERATION,MIMO_64QAM, DC_HSDPA,UL_L2_ENHANCE, UL_16QAM,EDPCCH_BOOSTING,DCMIMO_HSDPA

Unit:None

Default Value:None









8/13/2019 DC-HSDPA(RAN13.0_04)




7-19


Description

DC-HSDP A

SECCELLACTDEASW

NodeB SET MACHSPARA WRFD-010713

Traffic-Based

ActivationandDeactivation of theSupplementaryCarrier InMulti-carrier

Meaning:This parameter specifieswhether to enable Traffic-Based

Activation and Deactivation of theDC-HSDPA Secondary Carrier. Ifthis parameter is set to ON, thisfunction takes effect. If thisparameter is set to OFF, thisfunction does not take effect.When the switch is turned on, thisalgorithm can lower the uplinkload and extend the battery lifefor UEs.

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

Actual Value Range:ON, OFF

Unit:None

Default Value:OFF(OFF)

SECONDLOCELL

NodeB ADDDUALCELLGRP

WRFD-010696

DC-HSDP A

Meaning:Indicates the ID of localcell 2

.


Actual ValueRange:0~268435455

Unit:None

Default Value:None

ServiceDiffDrdSwitch

BSC6900 ADDUCELLDRD(Optional)

MODUCELLDRD(Optional)

WRFD-020120

WRFD-02040004

ServiceSteeringand LoadSharing inRRCConnection Setup

TrafficSteeringand LoadSharingDuringRAB

Setup

Meaning:Whether the servicesteering DRD algorithm isapplied.

GUI Value Range:ON, OFF


Unit:None

Default Value:OFF




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





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-ucelldrd.html




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



















8/13/2019 DC-HSDPA(RAN13.0_04)




7-20


Description

TCell BSC6900 ADD

UCELLSETUP(Mandatory)

ADDUCELLQUICKSETUP(Mandatory)

MODUCELLSETUP(Optional)

WRFD-02

2000

Physical

ChannelManagement

Meaning:Difference between the

System Frame Number (SFN)and NodeB Frame Number (BFN)of the NodeB which the cellbelongs to. It is recommendedthat Tcell of difference cells underone NodeB should be unique. Fordetailed information of thisparameter, refer to 3GPP TS25.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

None None Meaning:Indicates the uplinkfrequencies of the local cell. Thedownlink and uplink frequenciesof the local cell must stay withinthe same frequency band.Frequency(MHZ) = (FrequencyChannel Number / 5) + Offset

Band1: Common FrequenciesChannel Number: [9612-9888]Offset: 0 Special FrequenciesChannel Number: none Offset: 0

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


Band4: Common FrequenciesChannel Number: [1312-1513]



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/mod-ucellsetup.html























8/13/2019 DC-HSDPA(RAN13.0_04)




7-21


Description

Offset: 1450 Special FrequenciesChannel Number: (1662, 1687,1712, 1737, 1762, 1787, 1812,1837, 1862) Offset: 1380.1

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

Band6: Common FrequenciesChannel Number: [4162-4188]Offset: 0 Special FrequenciesChannel Number: (812, 837)Offset: 670.1 Band7: CommonFrequencies Channel Number:[2012-2338] Offset: 2100 SpecialFrequencies Channel Number:(2362, 2387, 2412, 2437, 2462,2487, 2512, 2537, 2562, 2587,2612, 2637, 2662, 2687) Offset:2030.1


Band9: Common FrequenciesChannel Number: [8762-8912]Offset: 0 Special FrequenciesChannel Number: none Offset: 0.



Unit:None

Default Value:None

ULLdbDRDLoadRemainThdDcHSDPA



WRFD-02040002

InterSystemDirectRetry

Meaning:This parameter specifiesthe threshold of triggering theuplink load balance forDC-HSDPA traffic. If theremaining number of equivalentusers in the uplink is less than thevalue of this parameter, uplinkload balance for DC-HSDPAtraffic is triggered.
























8/13/2019 DC-HSDPA(RAN13.0_04)




7-22


Description

Unit:%

Default Value:25

ULLdbDRDOffsetDcHSDPA

BSC6900 SETUDRD(Optional)

WRFD-02040002


Meaning:If the difference of theremaining number of equivalentusers in the uplink between thetarget cell and the serving cell isgreater than the value of thisparameter, the target cell meetsone of the qualifications to be thecandidate cell for directed retry.



Unit:%

Default Value:10

ULLdbDRDSwitchDcHSDPA



WRFD-02040002


Meaning:This parameter specifieswhether to enable the uplink loadbalance for DC-HSDPA traffic.The uplink load balance isperformed on the basis of theequivalent number 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


























8/13/2019 DC-HSDPA(RAN13.0_04)


WCDMA RANDC-HSDPA 8 Counters


8-1

8 CountersTable 8-1 Counter description

Counter ID Counter Name Counter Description NE Feature ID Feature Name50331719 VS.HSDPA.DCCfg.An

chorCarrierActedNumNumber of times that allthe users configured inDC mode in a cell arescheduled by

AnchorCarrier duringthe measurementperiod

NodeB WRFD-010610

WRFD-010689

WRFD-010696

HSDPAIntroductionPackage

HSPA+Downlink42Mbps perUser

DC-HSDPA

50331720 VS.HSDPA.DCCfg.SupCarrierActedNum

Total number of timesDC-HSDPA-enabledusers are scheduled bythe supplementarycarrier

NodeB WRFD-010610

WRFD-010689

WRFD-010696



DC-HSDPA

50331721 VS.HSDPA.DCCfg.DualCarrierActedNum

Total number of timesDC-HSDPA-enabledusers are scheduled bythe anchor andsupplementary carriersat the same time

NodeB WRFD-010610

WRFD-010689

WRFD-010696



DC-HSDPA

50341702 VS.HSDPA.DCCfg.SupCarrierDeact.TimeRatio

The Ratio Of Dc Deact NodeB WRFD-010713 Traffic-Based Activation andDeactivation ofthe DC-HSDPASecondaryCarrier

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












8/13/2019 DC-HSDPA(RAN13.0_04)


WCDMA RANDC-HSDPA 8 Counters


8-2

Counter ID Counter Name Counter Description NE Feature ID Feature Name

73403828 VS.HSDPA.RAB.DC.AttEstab

Number of DC-HSDPARAB Setup Requests in

the primary carrier ofDC-HSDPA counted forcell

BSC6900 WRFD-010696 DC-HSDPA

73403829 VS.HSDPA.RAB.DC.SuccEstab

Number of DC-HSDPARABs SetupSuccessfully in theprimary carrier ofDC-HSDPA counted forcell


73403830 VS.HSDPA.RAB.AbnormRel.DC

Number of DC-HSDPARABs AbnormalReleased in the primarycarrier of DC countedfor Cell(including RFCause)


73403831 VS.HSDPA.RAB.NormRel.DC

Number of DC-HSDPARABs Normal Releasedin the primary carrier ofDC counted for Cell


73410508 VS.HSDPA.DC.PRIM.UE.Mean.Cell Average number ofDC-HSDPA UEs inanchor carrier in a Cell


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

Average number ofDC-HSDPA UEs insupplementary carrier ina Cell


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


















8/13/2019 DC-HSDPA(RAN13.0_04)


WCDMA RANDC-HSDPA 9 Glossary


9-1

9 GlossaryFor the acronyms, abbreviations, terms, and definitions, see the Glossary .

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




8/13/2019 DC-HSDPA(RAN13.0_04)


WCDMA RANDC-HSDPA 10 Reference Documents

10 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_6/Radio%20Bearers.htm








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






